diff --git a/product/en/docs-mogdb/v3.0/about-mogdb/MogDB-compared-to-openGauss.md b/product/en/docs-mogdb/v3.0/about-mogdb/MogDB-compared-to-openGauss.md
new file mode 100644
index 0000000000000000000000000000000000000000..845973ceef44c8e84eafb45619cc7c370542f09d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/about-mogdb/MogDB-compared-to-openGauss.md
@@ -0,0 +1,124 @@
+---
+title: Comparison Between MogDB and openGauss
+summary: Comparison Between MogDB and openGauss
+author: Guo Huan
+date: 2021-04-02
+---
+
+# Comparison Between MogDB and openGauss
+
+## Relationship Between MogDB and openGauss
+
+MogDB is an enterprise database that is packaged and improved on the basis of openGauss open source kernel and it is more friendly to enterprise applications. On the basis of openGauss kernel, MogDB adds the MogHA component for automatic management and high availability under the primary-standby architecture, which is crucial for enterprise applications. At the same time, MogDB Manager includes backup and recovery, monitoring, automatic installation and other components for enterprise-level ease of use requirements.
+
+MogDB is a commercial product that is sold according to an established license pricing system and is supported by Enmo's professional services.
+
+## Introduction to openGauss
+
+openGauss is an open source relational database management system. The kernel of openGauss is derived from PostgreSQL and is distributed under Mulan PSL v2. openGauss kernel is open source, anyone and any organization can download the source code for compilation and installation without any cost; The openGauss community also regularly releases compiled binary installation files, and the current release strategy is to release one stable frequently supported version per year (end of March each year) and one radical version with new features (end of September each year).
+
+openGauss is a standalone database. It has the basic features of relational databases as well as enhanced features.
+
+For more details, please visit openGauss official website: <https://opengauss.org>
+
+### Basic Features
+
+- Standard SQLs
+
+  Supports SQL92, SQL99, SQL2003, and SQL2011 standards, GBK and UTF-8 character sets, SQL standard functions and analytic functions, and SQL Procedural Language.
+
+- Database storage management
+
+  Supports tablespaces where different tables can be stored in different locations.
+
+- Primary/standby deployment
+
+  Supports the ACID properties, single-node fault recoveries, primary/standby data synchronization, and primary/standby switchover.
+
+- APIs
+
+  Supports standard JDBC 4.0 and ODBC 3.5.
+
+- Management tools
+
+  Provides installation and deployment tools, instance start and stop tools, and backup and restoration tools.
+
+- Security management
+
+  Supports SSL network connections, user permission management, password management, security auditing, and other functions, to ensure data security at the management, application, system, and network layers.
+
+### Enhanced Features
+
+- Data Partitioning
+
+  Data partitioning is a general function for most database products. In openGauss, data is partitioned horizontally with a user-specified policy. This operation splits a table into multiple partitions that are not overlapped.
+
+- Vectorized Executor and Hybrid Row-Column Storage Engine
+
+  In a wide table containing a huge amount of data, a query usually only involves certain columns. In this case, the query performance of the row-store engine is poor. For example, a single table containing the data of a meteorological agency has 200 to 800 columns. Among these columns, only ten of them are frequently accessed. In this case, a vectorized executor and column-store engine can significantly improve performance by saving storage space.
+
+- High Availability (HA) Transaction Processing
+
+  openGauss manages transactions and guarantees the ACID properties. openGauss provides a primary/standby HA mechanism to reduce the service interruption time when the primary node is faulty. It protects key user programs and continuously provides external services, minimizing the impact of hardware, software, and human faults on services to ensure service continuity.
+
+- High Concurrency and High Performance
+
+  openGauss supports 10,000 concurrent connections through server thread pools. It supports thread nucleophilicity and millions of tpmC using the NUMA-based kernel data structure, manages TB-level large memory buffers through efficient hot and cold data elimination, achieves multi-version access without read/write blocks using CSN-based snapshots, and avoids performance fluctuation caused by full-page writes using incremental checkpoints.
+
+- SQL Self-Diagnosis
+
+  To locate performance issues of a query, you can use **EXPLAIN PERFORMANCE** to query its execution plan. However, this method produces many logs, requires to modify service logic, and depends on expertise to locate problems. SQL self-diagnosis enables users to locate performance issues more efficiently.
+
+- Equality Query in a Fully-encrypted Database
+
+  The encrypted database allows the client to encrypt sensitive data within the client application. During the query period, the entire service data flow exists in the form of ciphertext during data processing. It has the following advantages:
+
+  - Protects data privacy and security throughout the lifecycle on the cloud.
+  - Resolves trust issues by making the public cloud, consumer cloud, and development users keep their own keys.
+  - Enables partners to better comply with personal privacy protection laws and regulations with the help of the full encryption capability.
+
+- Memory Table
+
+  With memory tables, all data access is lock-free and concurrent, optimizing data processing and meeting real-time requirements.
+
+- Primary/Standby Deployment
+
+  The primary/standby deployment mode supports synchronous and asynchronous replication. Applications are deployed based on service scenarios. For synchronous replication, one primary node and two standby nodes are deployed. This ensures reliability but affects performance. For asynchronous replication, one primary node and one standby node are deployed. This has little impact on performance, but data may be lost when exceptions occur. openGauss supports automatic recovery of damaged pages. When a page on the primary node is damaged, the damaged page can be automatically recovered on the standby node. Besides, openGauss supports concurrent log recovery on the standby node to minimize the service unavailability time when the primary node is down.
+
+  In addition, in primary/standby deployment mode, if the read function of the standby node is enabled, the standby node supports read operations instead of write operations (such as table creation, data insertion, and data deletion), reducing the pressure on the primary node.
+
+- AI Capabilities
+
+  - Automatic parameter optimization
+  - Slow SQL discovery
+  - Index recommendation
+  - Time series prediction and exception detection
+  - DB4AI function
+  - SQL execution time prediction
+  - Database monitoring
+
+- Logical Log Replication
+
+  In logical replication, the primary database is called the source database, and the standby database is called the target database. The source database parses the WAL file based on the specified logical parsing rules and parses the DML operations into certain logical change information (standard SQL statements). The source database sends standard SQL statements to the target database. After receiving the SQL statements, the target database applies them to implement data synchronization. Logical replication involves only DML operations. Logical replication can implement cross-version replication, heterogeneous database replication, dual-write database replication, and table-level replication.
+
+- Automatic WDR Performance Analysis Report
+
+  Periodically and proactively analyzes run logs and WDR reports (which are automatically generated in the background and can be triggered by key indicator thresholds such as the CPU usage, memory usage, and long SQL statement proportions) and generates reports in HTML and PDF formats. The performance report can be automatically generated. The WDR generates a performance report between two different time points based on the system performance snapshot data at two different time points. The report is used to diagnose database kernel performance faults.
+
+- Incremental Backup and Restoration (beta)
+
+  Supports full backup and incremental backup of the database, manages backup data, and views the backup status. Supports combination of incremental backups and deletion of expired backups. The database server dynamically tracks page changes, and when a relational page is updated, the page is marked for backup. The incremental backup function requires that the GUC parameter enable_cbm_tracking be enabled to allow the server to track the modification page.
+
+- Point-In-Time Recovery
+
+  Point-in-time recovery (PITR) uses basic hot backup, write-ahead logs (WALs), and archived WALs for backup and recovery. Replaying a WAL record can be stopped at any point of time, so that there is a consistent snapshot of the database at any point of time. That is, you can restore the database to the state at any time since the backup starts. During recovery, you can specify a recovery stop point with a terminal ID (TID), time, and license serial number (LSN).
+
+## Advantages of MogDB
+
+openGauss is a standalone database where data is stored on a single physical node and data access tasks are pushed to service nodes. In this way, high concurrency of servers enables quick data processing. In addition, data can be copied to the standby server through log replication, ensuring high reliability and scalability.
+
+openGauss is a stand-alone database. To use openGauss in formal commercial projects, you need to build complete tool chain capabilities such as database monitoring and primary/standby switchover.
+
+At the product level, MogDB adds MogHA enterprise-class high availability components and feature-rich graphical management tool MogDB Manager to the original functions of openGauss, and continuously enhances the openGauss kernel along the established route. MogDB can maximize the high-availability deployment capabilities of multiple machine rooms, and can reach 2.5 million tpmC on 4-CPU server. MogDB Manager contains a variety of practical components, such as MTK database migration, MIT performance monitoring, RWT performance pressure testing, PTK automated deployment, etc., which greatly makes up the shortcomings of openGauss open source database and enriches various enterprise-class functions.
+
+At the service level, Enmo has decades of experience in database operation and maintenance, and can provide complete services to ensure a more stable database, smoother application transformation, and less risk, making up for the disadvantages of openGauss open source database human operation and maintenance shortage, while reducing maintenance costs.
diff --git a/product/en/docs-mogdb/v3.0/about-mogdb/mogdb-release-notes.md b/product/en/docs-mogdb/v3.0/about-mogdb/mogdb-release-notes.md
new file mode 100644
index 0000000000000000000000000000000000000000..dfcd9a086bb0b1108b178ffb6a9e33cb6b74515e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/about-mogdb/mogdb-release-notes.md
@@ -0,0 +1,355 @@
+---
+title: MogDB 2.1 Release Notes
+summary: MogDB 2.1 Release Notes
+author: Guo Huan
+date: 2021-12-06
+---
+
+# MogDB 2.1 Release Notes
+
+## 1. Version Description
+
+MogDB version 2.1 is further enhanced based on MogDB version 2.0 and incorporates the new features of openGauss 2.1.0.
+
+> Note: MogDB 2.1 is the Preview version, and the life cycle of this version is half a year.
+
+## 2. New Features
+
+### 2.1 Incorporate new features of openGauss 2.1.0
+
+- The stored procedure compatibility is enhanced.
+- The SQL engine capability is enhanced.
+- The Ustore storage engine is supported.
+- Segment-page storage is supported.
+- High availability is based on the Paxos distributed consistency protocol.
+- AI4DB and DB4AI competitiveness is continuously built.
+- The log framework and error codes are modified.
+- JDBC client load is balanced and read and write are isolated.
+- The CMake script compilation is supported.
+- The column-store table supports the primary key constraint and unique key constraint.
+- The jsonb data type is supported.
+- Automatic elimination of unique SQL statements is supported.
+- The UCE fault detection is supported.
+- The GB18030 character set is supported.
+- The standby server catch is optimized.
+- The client tool gsql supports automatic supplement of the readline command.
+- The dynamic data masking is supported.
+- The State Cryptography Administration (SCA) algorithms are supported.
+- The tamper-proof ledger database is supported.
+- The built-in role and permission management mechanism is supported.
+- The transparent encryption is supported.
+- The fully-encrypted database is enhanced.
+- The dblink is supported.
+- The Ubuntu system is supported.
+- The hash index is supported.
+- UPSERT supports subqueries.
+- The MIN/MAX function supports the IP address type.
+- The array_remove, array_replace, first, and last functions are added.
+- The Data Studio client tool adapts the kernel features.
+
+### 2.2 Performance Optimization for x86 Architecture
+
+Optimize the multi-core performance on x86 architecture. The performance of TPC-C under high concurrency is 1.5-5 times that of PostgreSQL 14. The main optimization points are:
+
+- Support NUMA binding
+- Unlocked WAL
+- Cache friendly data structure
+
+### 2.3 Create and Rebuild Indexes Concurrently
+
+Supports specifying the CONCURRENTLY option when executing create index and reindex index to create and rebuild indexes without blocking the execution of DML statements, improving index maintainability. Supports creating and rebuilding of indexes on ordinary tables and global indexes on partitioned tables concurrently.
+
+Compared with ordinary index creation and rebuilding, creating and rebuilding concurrently may take longer to complete.
+
+Indexes on column-store tables, local indexes on partitioned tables, and indexes on temporary tables do not support concurrent index creation and rebuilding.
+
+**Related Topics**
+
+- [CREATE INDEX](50-CREATE-INDEX#CONCURRENTLY)
+- [REINDEX](117-REINDEX#CONCURRENTLY)
+
+### 2.4 Enhanced Oracle compatibility
+
+#### 2.4.1 Support for Orafce plugin
+
+> Note: Users need to download the plugin package and install it manually.
+
+By integrating the orafce plugin, the following Oracle compatible syntax is supported:
+
+- SQL Queries
+  - DUAL table
+- SQL Functions
+  - Mathematical functions
+    - BITAND
+    - COSH
+    - SINH
+    - TANH
+  - String functions
+    - INSTR
+    - LENGTH
+    - LENGTHB
+    - LPAD
+    - LTRIM
+    - NLSSORT
+    - REGEXP_COUNT
+    - REGEXP_INSTR
+    - REGEXP_LIKE
+    - REGEXP_SUBSTR
+    - REGEXP_REPLACE
+    - RPAD
+    - RTRIM
+    - SUBSTR
+    - SUBSTRB
+  - Date/time functions
+    - ADD_MONTHS
+    - DBTIMEZONE
+    - LAST_DAY
+    - MONTHS_BETWEEN
+    - NEXT_DAY
+    - ROUND
+    - SESSIONTIMEZONE
+    - SYSDATE
+    - TRUNC
+  - Data type formatting functions
+    - TO_CHAR
+    - TO_DATE
+    - TO_MULTI_BYTE
+    - TO_NUMBER
+    - TO_SINGLE_BYTE
+  - Conditional expressions
+    - DECODE
+    - LNNVL
+    - NANVL
+    - NVL
+    - NVL2
+  - Aggregate functions
+    - LISTAGG
+    - MEDIAN
+  - Functions that return internal information
+    - DUMP
+- SQL Operators
+  - Datetime operator
+- Packages
+  - DBMS_ALERT
+  - DBMS_ASSERT
+  - DBMS_OUTPUT
+  - DBMS_PIPE
+  - DBMS_RANDOM
+  - DBMS_UTILITY
+  - UTL_FILE
+
+**Related Topics**
+
+- [orafce](orafce-user-guide)
+
+#### 2.4.2 Support CONNECT BY Syntax
+
+Provide Oracle-compatible **connect by** syntax, implement level data query control, and display levels, loops, starting levels, etc.
+
+Provides an oracle-compatible level query function, which can display data content, data levels, paths, etc. in a tree-like structure according to the specified connection relationship, starting conditions, etc.
+
+Specify the root row of the level query through the start with condition, and perform a recursive query based on these rows to obtain all sub-rows, sub-rows of sub-rows, etc.
+
+The relationship between the parent row and the child row between the levels is specified by the connect by condition to determine all the child rows of each row that meet the condition.
+
+If there is a connection, whether it is a connection statement, or in the from or where clause, the result set after the connection is obtained first, and then the level query is performed.
+
+If there is a where filter condition in the statement, execute the level query first and then filter the result set, instead of filtering out unsatisfied rows and all its sub-rows.
+
+You can view the level of the row through the level pseudo column, **sys_connect_by_path** to view the path from the root row to the row, and **connect_by_root** to view auxiliary functions such as the root row.
+
+**Related Topics**
+
+- [CONNECT BY](139-CONNECT-BY)
+
+#### 2.4.3 Updatable View
+
+Supports updatable views. Users can perform Insert/Update/Delete operations on the view, and the update operation will directly affect the base table corresponding to the view.
+
+Not all views can be updated. There must be a one-to-one correspondence between the rows in the view and the rows in the base table, that is, the content of the view cannot be created based on aggregates or window functions.
+
+For a view connected by multiple tables, if the primary key (unique key) of a base table can be used as the primary key (unique key) of the view, the view also supports updating, and the update result applies to the base table from which the primary key is derived.
+
+**Related Topics**
+
+- [Updatable-views Supported](overview-of-system-catalogs-and-system-views#updatable-views-supported)
+
+#### 2.4.4 Alter Columns When Rebuilding View
+
+When the view is rebuilt, it supports the operations of reducing columns and changing column names. This command is only valid for non-materialized views.
+
+**Related Topics**
+
+- [CREATE VIEW](70-CREATE-VIEW#replace)
+
+#### 2.4.5 Support systimestamp Function
+
+Returns the current system date and time of the server where the database is located, as well as time zone information.
+
+**Related Topics**
+
+- [Date and Time Processing Functions and Operators](8-date-and-time-processing-functions-and-operators#systimestamp)
+
+#### 2.4.6 Support sys_guid Function
+
+The system generates and returns a 16-byte globally unique identifier based on the current time and machine code.
+
+**Related Topics**
+
+- [System Information Functions](23-system-information-functions#sys_guid)
+
+### 2.5 Support PostgreSQL Plugins
+
+> Note: Users need to download the plugin package and install it manually.
+
+- [pg_repack](pg_repack-user-guide): Through the trigger mechanism, it provides the function of rebuilding the table online, which is mainly used to reduce the size of the free space in the table online.
+- [wal2json](wal2json-user-guide): Through the logical replication mechanism, continuous data changes are provided in the form of json, which are mainly used for heterogeneous replication and other situations.
+- [pg_trgm](pg_trgm-user-guide): Implement the trgm word segmentation algorithm to achieve better full-text retrieval capabilities.
+- [pg_prewarm](pg_prewarm-user-guide): Pre-cache the specified data table in shared memory to speed up data access.
+- [pg_bulkload](pg_bulkload-user-guide): The data is directly loaded into the data file without going through the shared memory, which speeds up the batch import of the database.
+
+### 2.6 Support Read Extensibility
+
+> Note: Comes with ShardingSphere 5.1.0 and later versions, which need to be downloaded and installed manually by the user.
+
+MogDB supports read extensibility by integrating with ShardingSphere's Proxy.
+
+- Read and write transactions are automatically routed to the primary library for execution, and read-only transactions are automatically routed to the backup library for execution; in scenarios with higher read consistency requirements, read-only transactions can also be routed to the primary library for execution through hint control.
+
+- Support for automatic identification and configuration of read and write nodes, without the need to configure primary and secondary roles, and automatic discovery of the primary and secondary libraries in the configuration list.
+
+- Support for automatic identification of primary and backup roles after switching, with no additional operation required to automatically identify the new primary and backup roles and route them correctly.
+
+- Support automatic load balancing of backup nodes: when the backup library is down and recovered or when a new backup library is added, it will be automatically added to the read load balancing after the replication status of the backup library is normal.
+
+### 2.7 Others
+
+- The nlssort function supports sorting by pinyin for the GBK character set of rare characters
+
+  **Related Topics**: [SELECT](125-SELECT#nlssort)
+
+- ALTER SEQUENCE supports modification of increment
+
+  **Related Topics**: [ALTER SEQUENCE](16-ALTER-SEQUENCE#increment)
+
+- For TIMESTAMP WITH TIME ZONE type, you can use TZH, TZM, TZD, TZR parameters in TO_CHAR to output time zone information
+
+  **Related Topics**: [Type Conversion Functions](9-type-conversion-functions#to_char)
+
+### 2.8 Preview Features
+
+> Note: Preview features need to be enabled manually.
+>
+> ```sql
+> alter system set enable_poc_feature = on;
+> -- or
+> alter system set enable_poc_feature to on;
+> -- Or add ‘enable_poc_feature = on’ to the postgresql.conf file in the MogDB data directory
+> -- Take effect after restart
+> ```
+
+#### 2.8.1 Row-store Table Compression
+
+Supports specifying whether a row-store table (astore) is a compressed table when it is created. For a compressed row-store table, the system compresses the table data automatically to save storage space. When writing data to the compressed table, the system automatically selects the appropriate compression algorithm according to the characteristics of each column, and the user can also specify the compression algorithm used for each column directly.
+
+There is a strong correlation between the actual compression ratio and the data content, and the compression ratio can reach 50% in the typical scenario, and the performance loss is less than 5% in the typical TPC-C model, the actual performance impact depends on the actual system load.
+
+For the non-compressed table, you can also use `Alter Table` to change the table to a compressed table, subsequent new write data will be automatically compressed.
+
+**Related Topics**
+
+- [CREATE TABLE](60-CREATE-TABLE#COMPRESSION)
+- [ALTER TABLE](22-ALTER-TABLE#COMPRESS)
+
+#### 2.8.2 SubPartition
+
+Support to create subpartition table, data automatically partition storage according to the partition mode, to improve the storage and query efficiency of large data volumes. The supported subpartition combinations include:
+
+- List-List
+- List-Range
+- List-Hash
+- Range-List
+- Range-Range
+- Range-Hash
+
+Support querying a single Partition and SubPartition;
+
+Supports partition pruning for Partition Key, SubPartition Key or their combined conditions to further optimize partition query efficiency;
+
+Supports truncate and vacuum operations on partition tables or first-level partitions;
+
+During Update operation, data movement across partitions is supported (Partition/SubPartition Key is not supported as List or Hash partition type);
+
+Backup and restore of subpartition are supported.
+
+**Related Topics**
+
+- [CREATE TABLE SUBPARTITION](62.1-CREATE-TABLE-SUBPARTITION)
+- [ALTER TABLE SUBPARTITION](23.1-ALTER-TABLE-SUBPARTITION)
+
+<br/>
+
+## 3. Modified Defects
+
+### 3.1 Incorporate openGauss 2.1.0 Modified Defects
+
+- [I435UP](https://gitee.com/opengauss/openGauss-server/issues/I435UP) An error is reported when the EXPLAIN statement is executed.
+- [I44QS6](https://gitee.com/opengauss/openGauss-server/issues/I44QS6) When the **select get_local_active_session() limit 1 ;** function is executed, the database breaks down.
+- [I4566H](https://gitee.com/opengauss/openGauss-server/issues/I4566H) After UPDATE GLOBAL INDEX is performed on a partition of a partitioned table, the query result is inconsistent with the master version.
+- [I45822](https://gitee.com/opengauss/openGauss-server/issues/I45822) An error occurs when the GPC global plan cache information is queried in the global temporary table.
+- [I442TY](https://gitee.com/opengauss/openGauss-server/issues/I442TY) Failed to recover to the timestamp specified by PITR.
+- [I45T7A](https://gitee.com/opengauss/openGauss-server/issues/I45T7A) Remote backup is abnormal when the database is installed in environment variable separation mode.
+- [I464G5](https://gitee.com/opengauss/openGauss-server/issues/I464G5) Failed to use **gs_ctl build** to rebuild a specified non-instance directory on a standby node. The error information is inconsistent.
+- [I45TTB](https://gitee.com/opengauss/openGauss-server/issues/I45TTB) The foreign table is successfully created for the file type that is not supported by file_fdw, but no error is reported.
+- [I491CN](https://gitee.com/opengauss/openGauss-server/issues/I491CN) When the subnet mask of the network address of the cidr type is 32, an error is reported when the MAX function is called.
+- [I496VN](https://gitee.com/opengauss/openGauss-server/issues/I496VN) After a large number of Xlogs are stacked on the standby node, the archiving address is corrected. As a result, the archiving fails.
+- [I49HRV](https://gitee.com/opengauss/openGauss-server/issues/I49HRV) When the standby node archiving is enabled, the standby node archiving is slow. After the switchover, the new primary node is abnormal.
+- [I492W4](https://gitee.com/opengauss/openGauss-server/issues/I492W4) When operations related to the mysql_fdw and oracle_fdw foreign tables are performed on the database installed using the OM, a core dump occurs in the database.
+- [I498QT](https://gitee.com/opengauss/openGauss-server/issues/I498QT) In the maximum availability mode, when the synchronous standby parameter is ANY2 and the primary server is under continuous pressure, running the **kill-9** command to stop one synchronous standby server causes transaction congestion on the primary server for 2s.
+- [I49L15](https://gitee.com/opengauss/openGauss-server/issues/I49L15) Two standby nodes are enabled for archiving. After one node is scaled in and out, the archiving of the other node is abnormal.
+- [I43MTG](https://gitee.com/opengauss/openGauss-server/issues/I43MTG) The developer guide does not contain information related to new functions.
+- [I42YW8](https://gitee.com/opengauss/openGauss-server/issues/I42YW8) The UPSERT subquery information is not supplemented.
+- [I45WDH](https://gitee.com/opengauss/openGauss-server/issues/I45WDH) file_fdw does not support the fixed format. The related description needs to be deleted from the developer guide.
+- [I484J0](https://gitee.com/opengauss/openGauss-server/issues/I484J0) The **gs_initdb -T** parameter is not verified, and the value is incorrect after being set according to the guide.
+- [I471CS](https://gitee.com/opengauss/openGauss-server/issues/I471CS) When **pgxc_node_name** contains hyphens (-), the database exits abnormally. If residual temporary tables are not cleared, automatic clearance and vacuum cannot be performed.
+- [I40QM1](https://gitee.com/opengauss/openGauss-server/issues/I40QM1) When gs_basebackup is executed, an exception occurs on the standby node. As a result, the gs_basebackup process is blocked and cannot exit.
+- [I3RTQK](https://gitee.com/opengauss/openGauss-server/issues/I3RTQK) The standby node fails to be backed up using gs_basebackup, and the message "could not fetch mot checkpoint info:, status:7" is displayed.
+
+### 3.2 MogDB 2.1.0 Modified Defects
+
+- It prompts **which doesn't support recovery_target_lsn** when **gs_probackup** restores the database
+
+- **Statement_history** table cannot be cleaned up
+
+- Abnormal database downtime caused by schema cascade delete operation
+
+- **\d** in gsql cannot query the field information of the table or view corresponding to the synonym
+
+- The **lengthb** function does not support large object fields such as blob
+
+- After enabling sha256 authentication, the original md5 encrypted users can still successfully login through md5 authentication
+
+- The output of **raise** inside nested stored procedures in MogDB is too detailed
+
+### MogDB 2.1.1 Modified Defects
+
+MogDB 2.1.1 is the patch version of MogDB 2.1.0, released on 2022.03.22. Based on MogDB 2.1.0, the following fixes are made:
+
+- Fixed the defect of coredump caused by parameter overflow in **pg_encoding_to_char()** function
+
+- Fixed the defect of coredump generated when **connect by** statement is used as query clause
+
+- Fixed the bug that the order of query data in the connect by statement order by level is inconsistent on the x86 platform
+
+## 4. Compatibility
+
+This version supports the following operating system and CPU architecture combinations.
+
+| OS                 | CPU Architecture                                   |
+| ------------------ | -------------------------------------------------- |
+| CentOS 7.x         | X86_64 (Intel, AMD, Hygon, ZHAOXIN)                |
+| Redhat 7.x         | X86_64 (Intel, AMD, Hygon, ZHAOXIN)                |
+| openEuler 20.03LTS | ARM (Kunpeng), X86_64 (Intel, AMD, Hygon, ZHAOXIN) |
+| Kylin V10          | ARM (Kunpeng), X86_64 (Intel, AMD, Hygon, ZHAOXIN) |
+| UOS V20-D / V20-E  | ARM (Kunpeng), X86_64 (Intel, AMD, Hygon, ZHAOXIN) |
+| UOS V20-A          | X86_64 (Intel, AMD, Hygon, ZHAOXIN)                |
diff --git a/product/en/docs-mogdb/v3.0/about-mogdb/open-source-components/1-enhanced-opengauss-kernel.md b/product/en/docs-mogdb/v3.0/about-mogdb/open-source-components/1-enhanced-opengauss-kernel.md
new file mode 100644
index 0000000000000000000000000000000000000000..ac7a28ef8cfbb457901397299607e0261a0968bd
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/about-mogdb/open-source-components/1-enhanced-opengauss-kernel.md
@@ -0,0 +1,12 @@
+---
+title: Enhanced openGauss Kernel
+summary: Enhanced openGauss Kernel
+author: Liuxu
+date: 2021-06-09
+---
+
+# Enhanced openGauss Kernel
+
+<br/>
+
+MogDB is an enterprise-level database which is more friendly to enterprise applications, encapsulated and improved on the basis of openGauss open source kernel. Based on the openGauss kernel, MogDB adds MogHA, TimeSeries (for IoT scenarios), Distributed (realize each data node as an openGauss kernel distributed environment), Oracle view compatibility (DBA and V$ views) and other plug-ins. The MogHA plug-in is used for automated HA management in the primary/standby architecture, which is crucial for enterprise applications. At the same time, MogDB Manager management software is developed, which includes backup and recovery, performance monitoring, health check toolkit, automated deployment, database migration, data synchronization, compatibility analysis, performance pressure test and data recovery from a corrupted database for a variety of enterprise-level usability requirements.
diff --git a/product/en/docs-mogdb/v3.0/about-mogdb/open-source-components/2-docker-based-mogdb.md b/product/en/docs-mogdb/v3.0/about-mogdb/open-source-components/2-docker-based-mogdb.md
new file mode 100644
index 0000000000000000000000000000000000000000..97d398f1d05f9c8608670dd6a97a99867621bc56
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/about-mogdb/open-source-components/2-docker-based-mogdb.md
@@ -0,0 +1,37 @@
+---
+title: Container-based MogDB
+summary: Container-based MogDB
+author: Liuxu
+date: 2021-06-09
+---
+
+# Container-based MogDB
+
+<br/>
+
+## Features
+
+- As the version of MogDB changes, release the image of the new version as soon as possible.
+- The container version of the database image has built-in configuration of initialization parameters for best practices.
+- The container version database supports both x86 and ARM CPU architectures.
+- MogDB 2.1 container version supports the latest version of compat-tools and plugin functions.
+
+**Currently, x86-64 and ARM64 architectures are supported. Please get the corresponding container image according to the machine architecture of your host.**
+
+Starting from version 2.0 (including version 2.0)
+
+- MogDB of the x86-64 architecture is run on the [Ubuntu 18.04 operating system](https://ubuntu.com/).
+- MogDB of the ARM64 architecture is run on the [Debian 10 operating system](https://www.debian.org/).
+
+Before version 1.1.0 (including version 1.1.0)
+
+- MogDB of the x86-64 architecture is run on the [CentOS7.6 operating system](https://www.centos.org/).
+- MogDB of the ARM64 architecture is run on the [openEuler 20.03 LTS operating system](https://openeuler.org/en/).
+
+<br/>
+
+## How to Use an Image?
+
+For details, visit the following website:
+
+[Installation Guide - Container-based Installation](docker-installation)
diff --git a/product/en/docs-mogdb/v3.0/about-mogdb/open-source-components/5-wal2json-extention-for-mogdb&opengauss.md b/product/en/docs-mogdb/v3.0/about-mogdb/open-source-components/5-wal2json-extention-for-mogdb&opengauss.md
new file mode 100644
index 0000000000000000000000000000000000000000..88e2d0aa7a814ae9bebad1f11f63c1047674a9bd
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/about-mogdb/open-source-components/5-wal2json-extention-for-mogdb&opengauss.md
@@ -0,0 +1,125 @@
+---
+title: wal2json Extention for MogDB&openGauss
+summary: wal2json Extention for MogDB&openGauss
+author: Guo Huan
+date: 2021-06-02
+---
+
+# wal2json Extention for MogDB&openGauss
+
+## How to Get the Component
+
+<https://gitee.com/enmotech/wal2json>
+
+<br/>
+
+## Logical Decoding (wal2json)
+
+With the wal2json plug-in of MogDB and openGauss, you can export logical log files in the JSON format.
+
+<br/>
+
+## Prerequisites
+
+You have set **wal_level** to **logical**.
+
+<br/>
+
+## Background Information
+
+wal2json is a logical decoding plug-in. It can be used for accessing tuples generated by INSERT and UPDATE and parsing WAL logs.
+
+wal2json generates a JSON object in each transaction. JSON provides all new and old tuples as well as other optional properties, such as transaction timestamp, qualified schema, data type, and transaction ID.
+
+<br/>
+
+## Obtaining JSON Objects Using SQL
+
+1. Log in to the MogDB database.
+
+2. Run the following commands to create tables and initialize the plug-in.
+
+   ```sql
+   --Open a new session and run the following:
+   pg_recvlogical -d mogdb --slot test_slot --create-slot -P wal2json
+   pg_recvlogical -d mogdb --slot test_slot --start -o pretty-print=1 -f -
+   --Perform the following basic DML operations:
+   CREATE TABLE test_table (
+       id char(10) NOT NULL,
+       code        char(10),
+       PRIMARY KEY (id)
+   );
+   mogdb=# INSERT INTO test_table (id, code) VALUES('id1', 'code1');
+   INSERT 0 1
+   mogdb=# update test_table set code='code2' where id='id1';
+   UPDATE 1
+   mogdb=# delete from test_table where id='id1';
+   DELETE 1
+   ```
+
+   DML output:
+
+   **INSERT**
+
+   ```json
+   {
+     "change": [
+       {
+         "kind": "insert",
+         "schema": "mdmv2",
+         "table": "test_table",
+         "columnnames": ["id", "code"],
+         "columntypes": ["character(10)", "character(10)"],
+         "columnvalues": ["id1       ", "code1     "]
+       }
+     ]
+   }
+   ```
+
+   **UPDATE**
+
+   ```json
+   {
+     "change": [
+       {
+         "kind": "update",
+         "schema": "mdmv2",
+         "table": "test_table",
+         "columnnames": ["id", "code"],
+         "columntypes": ["character(10)", "character(10)"],
+         "columnvalues": ["id1       ", "code2     "],
+         "oldkeys": {
+           "keynames": ["id"],
+           "keytypes": ["character(10)"],
+           "keyvalues": ["id1       "]
+         }
+       }
+     ]
+   }
+   ```
+
+   **DELETE**
+
+   ```json
+   {
+     "change": [
+       {
+         "kind": "delete",
+         "schema": "mdmv2",
+         "table": "test_table",
+         "oldkeys": {
+           "keynames": ["id"],
+           "keytypes": ["character(10)"],
+           "keyvalues": ["id1       "]
+         }
+       }
+     ]
+   }
+   ```
+
+   REPLICA IDENTITY can determine the details of the exported logical logs when the UPDATE and DELETE operations are performed on a table.
+
+   - DEFAULT: A logical log includes the original values of the primary key columns when the value is updated or deleted.
+   - NOTHING: A logical log does not include any update or delete information.
+   - FULL: A logical log include original information of the whole row to which the value belongs when the value in a table is updated or deleted.
+   - USING INDEX: includes only original values of all columns in specified indexes.
diff --git a/product/en/docs-mogdb/v3.0/about-mogdb/open-source-components/DBMS-RANDOM.md b/product/en/docs-mogdb/v3.0/about-mogdb/open-source-components/DBMS-RANDOM.md
new file mode 100644
index 0000000000000000000000000000000000000000..9464e7f1128c56530ddf672e97f858240148046b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/about-mogdb/open-source-components/DBMS-RANDOM.md
@@ -0,0 +1,531 @@
+---
+title: DBMS_RANDOM - Generating Random Data (Numbers, Strings and Dates) in MogDB with compat-tools
+summary: DBMS_RANDOM - Generating Random Data (Numbers, Strings and Dates) in MogDB with compat-tools
+author: Zhang Cuiping
+date: 2021-08-30
+---
+
+# DBMS_RANDOM - Generating Random Data (Numbers, Strings and Dates) in MogDB with compat-tools
+
+<br/>
+
+## Introduction to compat-tools
+
+Compat-tools is a set of compatibility tools. It aims to provide compatibility for necessary functions and system views tha are created for OSs migrated from other asynchronous databases to MogDB, thereby facilitating the follow-up system maintenance and application modification.
+
+<br/>
+
+## compat-tools Download
+
+To install compat-tools, please download the tool of the latest version from [https://gitee.com/enmotech/compat-tools](https://gitee.com/enmotech/compat-tools).
+
+<br/>
+
+## Features of compat-tools
+
+1. runMe.sql: General scheduling script
+2. Oracle_Views.sql: Compatible with Oracle database data dictionaries and views
+3. Oracle_Functions.sql: Compatible with Oracle database functions
+4. Oracle_Packages.sql: Compatible with Oracle database packages
+5. MySQL_Views.sql: Compatible with MySQL database data dictionaries and views //TODO
+6. MySQL_Functions.sql: Compatible with MySQL database functions //TODO
+
+<br/>
+
+## MogDB Versions Supported By compat-tools
+
+- MogDB 2.0
+- MogDB 1.1
+
+<br/>
+
+## Installing and Using compat-tools
+
+1. Download compat-tools: <https://gitee.com/enmotech/compat-tools>
+2. Store the downloaded files to a customized directory (**/opt/compat-tools-0902** is taken as an example in this article).
+
+   ```bash
+   [root@mogdb-kernel-0005 compat-tools-0902]# pwd
+   /opt/compat-tools-0902
+   [root@mogdb-kernel-0005 compat-tools-0902]# ls -l
+   total 228
+   -rw-r--r-- 1 root root   9592 Sep  2 14:40 LICENSE
+   -rw-r--r-- 1 root root      0 Sep  2 14:40 MySQL_Functions.sql
+   -rw-r--r-- 1 root root      0 Sep  2 14:40 MySQL_Views.sql
+   -rw-r--r-- 1 root root  41652 Sep  2 14:40 Oracle_Functions.sql
+   -rw-r--r-- 1 root root  34852 Sep  2 14:40 Oracle_Packages.sql
+   -rw-r--r-- 1 root root 125799 Sep  2 14:40 Oracle_Views.sql
+   -rw-r--r-- 1 root root   4708 Sep  2 14:40 README.md
+   -rw-r--r-- 1 root root    420 Sep  2 14:40 runMe.sql
+   ```
+
+3. Switch to user `omm`.
+
+   ```bash
+   su - omm
+   ```
+
+4. Run the following command (26000 is the port for connnecting the database).
+
+   ```bash
+   gsql -d mogdb -p 26000 -f /opt/compat-tools-0902/runMe.sql
+   ```
+
+<br/>
+
+## Testing DBMS_RANDOM
+
+### Log In to the mogdb Database
+
+```sql
+[omm@mogdb-kernel-0005 ~]$ gsql -d mogdb -p 26000
+gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+Non-SSL connection (SSL connection is recommended when requiring high-security)
+Type "help" for help.
+
+mogdb=#
+```
+
+<br/>
+
+- [SEED](#seed)
+- [VALUE](#value)
+- [STRING](#string)
+- [NORMAL](#normal)
+- [RANDOM](#random)
+- [Generating Random Dates](#generating-random-dates)
+- [Generating Random Data](#generating-random-data)
+
+<br/>
+
+## SEED
+
+The `SEED` procedure allows you to seed the pseudo-random number generator, making it more random. `SEED` is limited to  binary integers or strings up to 2000 characters. If you want to consistently generate the same set of pseudo-random numbers, always use the same seed.
+
+```sql
+declare
+BEGIN
+  DBMS_OUTPUT.put_line('Run 1 : seed=0');
+  DBMS_RANDOM.seed (val => 0);
+  FOR i IN 1 ..5 LOOP
+    DBMS_OUTPUT.put_line('i=' || i || ' : value=' || DBMS_RANDOM.value(low => 1, high => 10));
+  END LOOP;
+
+  DBMS_OUTPUT.put_line('Run 2 : seed=0');
+  DBMS_RANDOM.seed (val => 0);
+  FOR i IN 1 ..5 LOOP
+    DBMS_OUTPUT.put_line('i=' || i || ' : value=' || DBMS_RANDOM.value(low => 1, high => 10));
+  END LOOP;
+
+END;
+/
+NOTICE:  Run 1 : seed=0
+CONTEXT:  SQL statement "CALL dbms_output.put_line('Run 1 : seed=0')"
+PL/pgSQL function inline_code_block line 3 at PERFORM
+NOTICE:  i=1 : value=2.53745232429355
+CONTEXT:  SQL statement "CALL dbms_output.put_line('i=' || i || ' : value=' || DBMS_RANDOM.value(low => 1, high => 10))"
+PL/pgSQL function inline_code_block line 6 at PERFORM
+NOTICE:  i=2 : value=7.749117821455
+CONTEXT:  SQL statement "CALL dbms_output.put_line('i=' || i || ' : value=' || DBMS_RANDOM.value(low => 1, high => 10))"
+PL/pgSQL function inline_code_block line 6 at PERFORM
+NOTICE:  i=3 : value=1.86734489817172
+CONTEXT:  SQL statement "CALL dbms_output.put_line('i=' || i || ' : value=' || DBMS_RANDOM.value(low => 1, high => 10))"
+PL/pgSQL function inline_code_block line 6 at PERFORM
+NOTICE:  i=4 : value=8.83418704243377
+CONTEXT:  SQL statement "CALL dbms_output.put_line('i=' || i || ' : value=' || DBMS_RANDOM.value(low => 1, high => 10))"
+PL/pgSQL function inline_code_block line 6 at PERFORM
+NOTICE:  i=5 : value=6.19573155790567
+CONTEXT:  SQL statement "CALL dbms_output.put_line('i=' || i || ' : value=' || DBMS_RANDOM.value(low => 1, high => 10))"
+PL/pgSQL function inline_code_block line 6 at PERFORM
+NOTICE:  Run 2 : seed=0
+CONTEXT:  SQL statement "CALL dbms_output.put_line('Run 2 : seed=0')"
+PL/pgSQL function inline_code_block line 9 at PERFORM
+NOTICE:  i=1 : value=2.53745232429355
+CONTEXT:  SQL statement "CALL dbms_output.put_line('i=' || i || ' : value=' || DBMS_RANDOM.value(low => 1, high => 10))"
+PL/pgSQL function inline_code_block line 12 at PERFORM
+NOTICE:  i=2 : value=7.749117821455
+CONTEXT:  SQL statement "CALL dbms_output.put_line('i=' || i || ' : value=' || DBMS_RANDOM.value(low => 1, high => 10))"
+PL/pgSQL function inline_code_block line 12 at PERFORM
+NOTICE:  i=3 : value=1.86734489817172
+CONTEXT:  SQL statement "CALL dbms_output.put_line('i=' || i || ' : value=' || DBMS_RANDOM.value(low => 1, high => 10))"
+PL/pgSQL function inline_code_block line 12 at PERFORM
+NOTICE:  i=4 : value=8.83418704243377
+CONTEXT:  SQL statement "CALL dbms_output.put_line('i=' || i || ' : value=' || DBMS_RANDOM.value(low => 1, high => 10))"
+PL/pgSQL function inline_code_block line 12 at PERFORM
+NOTICE:  i=5 : value=6.19573155790567
+CONTEXT:  SQL statement "CALL dbms_output.put_line('i=' || i || ' : value=' || DBMS_RANDOM.value(low => 1, high => 10))"
+PL/pgSQL function inline_code_block line 12 at PERFORM
+ANONYMOUS BLOCK EXECUTE
+mogdb=#
+```
+
+<br/>
+
+## VALUE
+
+The `VALUE` function is used to produce random numbers with a specified range. When called without parameters it produce a number greater than or equal to 0 and less than 1, with 38 digit precision.
+
+```sql
+DECLARE
+BEGIN
+  FOR cur_rec IN 1 ..5 LOOP
+    DBMS_OUTPUT.put_line('value= ' || DBMS_RANDOM.value());
+  END LOOP;
+END;
+/
+NOTICE:  value= .785799258388579
+CONTEXT:  SQL statement "CALL dbms_output.put_line('value= ' || DBMS_RANDOM.value())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  value= .692194153089076
+CONTEXT:  SQL statement "CALL dbms_output.put_line('value= ' || DBMS_RANDOM.value())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  value= .368766269646585
+CONTEXT:  SQL statement "CALL dbms_output.put_line('value= ' || DBMS_RANDOM.value())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  value= .87390407640487
+CONTEXT:  SQL statement "CALL dbms_output.put_line('value= ' || DBMS_RANDOM.value())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  value= .745095098391175
+CONTEXT:  SQL statement "CALL dbms_output.put_line('value= ' || DBMS_RANDOM.value())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+ANONYMOUS BLOCK EXECUTE
+```
+
+If the parameters are used, the resulting number will be greater than or equal to the low value and less than the high value, with the precision restricted by the size of the high value.
+
+```sql
+declare
+BEGIN
+  FOR cur_rec IN 1 ..5 LOOP
+    DBMS_OUTPUT.put_line('value(1,100)= ' || DBMS_RANDOM.value(1,100));
+  END LOOP;
+END;
+/
+
+NOTICE:  value(1,100)= 45.158544998616
+CONTEXT:  SQL statement "CALL dbms_output.put_line('value(1,100)= ' || DBMS_RANDOM.value(1,100))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  value(1,100)= 36.0190920610912
+CONTEXT:  SQL statement "CALL dbms_output.put_line('value(1,100)= ' || DBMS_RANDOM.value(1,100))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  value(1,100)= 73.5194435422309
+CONTEXT:  SQL statement "CALL dbms_output.put_line('value(1,100)= ' || DBMS_RANDOM.value(1,100))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  value(1,100)= 26.7619780991226
+CONTEXT:  SQL statement "CALL dbms_output.put_line('value(1,100)= ' || DBMS_RANDOM.value(1,100))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  value(1,100)= 40.035083710216
+CONTEXT:  SQL statement "CALL dbms_output.put_line('value(1,100)= ' || DBMS_RANDOM.value(1,100))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+ANONYMOUS BLOCK EXECUTE
+mogdb=#
+```
+
+Use `TRUNC` or `ROUND` to alter the precision as required. For example, to produce random integer values between 1 and 10 truncate the output and add 1 to the upper boundary.
+
+```sql
+mogdb=# select TRUNC(DBMS_RANDOM.value(1,11)) ;
+
+ trunc
+-------
+
+     6
+
+(1 row)
+
+mogdb=#
+```
+
+<br/>
+
+## STRING
+
+The `STRING` function returns a string of random characters of the specified length. The `OPT` parameter determines the type of string produced as follows:
+
+- 'u', 'U' - uppercase alpha characters
+- 'l', 'L' - lowercase alpha characters
+- 'a', 'A' - mixed case alpha characters
+- 'x', 'X' - uppercase alpha-numeric characters
+- 'p', 'P' - any printable characters
+
+The `LEN` parameter, not surprisingly, specifies the length of the string returned.
+
+```sql
+declare
+BEGIN
+  FOR i IN 1 .. 5 LOOP
+    DBMS_OUTPUT.put_line('string(''x'',10)= ' || DBMS_RANDOM.string('x',10));
+  END LOOP;
+END;
+/
+
+NOTICE:  string('x',10)= i5S6XOZxrA
+CONTEXT:  SQL statement "CALL dbms_output.put_line('string(''x'',10)= ' || DBMS_RANDOM.string('x',10))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  string('x',10)= HGvRm75w19
+CONTEXT:  SQL statement "CALL dbms_output.put_line('string(''x'',10)= ' || DBMS_RANDOM.string('x',10))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  string('x',10)= N9WsQGJl6l
+CONTEXT:  SQL statement "CALL dbms_output.put_line('string(''x'',10)= ' || DBMS_RANDOM.string('x',10))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  string('x',10)= hDlPevVgRb
+CONTEXT:  SQL statement "CALL dbms_output.put_line('string(''x'',10)= ' || DBMS_RANDOM.string('x',10))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  string('x',10)= ZdSd8x8RKx
+CONTEXT:  SQL statement "CALL dbms_output.put_line('string(''x'',10)= ' || DBMS_RANDOM.string('x',10))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+ANONYMOUS BLOCK EXECUTE
+mogdb=#
+```
+
+Combine the `STRING` and `VALUE` functions to get variable length strings.
+
+```sql
+declare
+BEGIN
+  FOR i IN 1 .. 5 LOOP
+    DBMS_OUTPUT.put_line('string(''L'',?)= ' || DBMS_RANDOM.string('L',TRUNC(DBMS_RANDOM.value(10,21))));
+  END LOOP;
+END;
+/
+
+NOTICE:  string('L',?)= kcyzowdxqbyzu
+CONTEXT:  SQL statement "CALL dbms_output.put_line('string(''L'',?)= ' || DBMS_RANDOM.string('L',TRUNC(DBMS_RANDOM.value(10,21))))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  string('L',?)= ohzpljyatsplqtbbus
+CONTEXT:  SQL statement "CALL dbms_output.put_line('string(''L'',?)= ' || DBMS_RANDOM.string('L',TRUNC(DBMS_RANDOM.value(10,21))))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  string('L',?)= hbrjsfeevoi
+CONTEXT:  SQL statement "CALL dbms_output.put_line('string(''L'',?)= ' || DBMS_RANDOM.string('L',TRUNC(DBMS_RANDOM.value(10,21))))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  string('L',?)= lfsapmytdamvwcw
+CONTEXT:  SQL statement "CALL dbms_output.put_line('string(''L'',?)= ' || DBMS_RANDOM.string('L',TRUNC(DBMS_RANDOM.value(10,21))))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  string('L',?)= pcvtxnwzomkqwpfzes
+CONTEXT:  SQL statement "CALL dbms_output.put_line('string(''L'',?)= ' || DBMS_RANDOM.string('L',TRUNC(DBMS_RANDOM.value(10,21))))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+ANONYMOUS BLOCK EXECUTE
+mogdb=#
+```
+
+<br/>
+
+## NORMAL
+
+The `NORMAL` function returns random numbers in a normal distribution.
+
+```sql
+declare
+BEGIN
+  FOR cur_rec IN 1 ..5 LOOP
+    DBMS_OUTPUT.put_line('normal= ' || DBMS_RANDOM.normal());
+  END LOOP;
+END;
+/
+
+NOTICE:  normal= .838851847718988
+CONTEXT:  SQL statement "CALL dbms_output.put_line('normal= ' || DBMS_RANDOM.normal())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  normal= -.523612260373397
+CONTEXT:  SQL statement "CALL dbms_output.put_line('normal= ' || DBMS_RANDOM.normal())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  normal= -.241931681458075
+CONTEXT:  SQL statement "CALL dbms_output.put_line('normal= ' || DBMS_RANDOM.normal())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  normal= -.120847761874286
+CONTEXT:  SQL statement "CALL dbms_output.put_line('normal= ' || DBMS_RANDOM.normal())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  normal= .360125112757284
+CONTEXT:  SQL statement "CALL dbms_output.put_line('normal= ' || DBMS_RANDOM.normal())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+ANONYMOUS BLOCK EXECUTE
+mogdb=#
+```
+
+<br/>
+
+## RANDOM
+
+```sql
+declare
+BEGIN
+  FOR i IN 1 .. 5 LOOP
+    DBMS_OUTPUT.put_line('random= ' || DBMS_RANDOM.random());
+  END LOOP;
+END;
+/
+NOTICE:  This function is deprecated with Release 11gR1, although currently supported, it should not be used.
+CONTEXT:  SQL statement "CALL dbms_output.put_line('random= ' || DBMS_RANDOM.random())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  random= -1023930867
+CONTEXT:  SQL statement "CALL dbms_output.put_line('random= ' || DBMS_RANDOM.random())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  This function is deprecated with Release 11gR1, although currently supported, it should not be used.
+CONTEXT:  SQL statement "CALL dbms_output.put_line('random= ' || DBMS_RANDOM.random())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  random= 1068572119
+CONTEXT:  SQL statement "CALL dbms_output.put_line('random= ' || DBMS_RANDOM.random())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  This function is deprecated with Release 11gR1, although currently supported, it should not be used.
+CONTEXT:  SQL statement "CALL dbms_output.put_line('random= ' || DBMS_RANDOM.random())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  random= 95361253
+CONTEXT:  SQL statement "CALL dbms_output.put_line('random= ' || DBMS_RANDOM.random())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  This function is deprecated with Release 11gR1, although currently supported, it should not be used.
+CONTEXT:  SQL statement "CALL dbms_output.put_line('random= ' || DBMS_RANDOM.random())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  random= -712638729
+CONTEXT:  SQL statement "CALL dbms_output.put_line('random= ' || DBMS_RANDOM.random())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  This function is deprecated with Release 11gR1, although currently supported, it should not be used.
+CONTEXT:  SQL statement "CALL dbms_output.put_line('random= ' || DBMS_RANDOM.random())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  random= -1251059926
+CONTEXT:  SQL statement "CALL dbms_output.put_line('random= ' || DBMS_RANDOM.random())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+ANONYMOUS BLOCK EXECUTE
+mogdb=#
+```
+
+<br/>
+
+## Generating Random Dates
+
+There are no specific functions for generating random dates currently, but we can add random numbers to an existing date to make it random. The following example generates random dates over the next year.
+
+```sql
+declare
+BEGIN
+  FOR i IN 1 .. 5 LOOP
+    DBMS_OUTPUT.put_line('date= ' || TRUNC(SYSDATE + DBMS_RANDOM.value(0,366)));
+  END LOOP;
+END;
+/
+
+NOTICE:  date= 2021-10-06 00:00:00
+CONTEXT:  SQL statement "CALL dbms_output.put_line('date= ' || TRUNC(SYSDATE + DBMS_RANDOM.value(0,366)))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  date= 2022-05-09 00:00:00
+CONTEXT:  SQL statement "CALL dbms_output.put_line('date= ' || TRUNC(SYSDATE + DBMS_RANDOM.value(0,366)))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  date= 2022-04-07 00:00:00
+CONTEXT:  SQL statement "CALL dbms_output.put_line('date= ' || TRUNC(SYSDATE + DBMS_RANDOM.value(0,366)))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  date= 2021-11-29 00:00:00
+CONTEXT:  SQL statement "CALL dbms_output.put_line('date= ' || TRUNC(SYSDATE + DBMS_RANDOM.value(0,366)))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  date= 2022-06-04 00:00:00
+CONTEXT:  SQL statement "CALL dbms_output.put_line('date= ' || TRUNC(SYSDATE + DBMS_RANDOM.value(0,366)))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+ANONYMOUS BLOCK EXECUTE
+mogdb=#
+```
+
+By doing the correct divisions, we can add random numbers of hours, seconds or minutes to a date.
+
+```sql
+DECLARE
+  l_hours_in_day NUMBER := 24;
+  l_mins_in_day  NUMBER := 24*60;
+  l_secs_in_day  NUMBER := 24*60*60;
+BEGIN
+  FOR i IN 1 .. 5 LOOP
+    DBMS_OUTPUT.put_line('hours= ' || (TRUNC(SYSDATE) + (TRUNC(DBMS_RANDOM.value(0,1000))/l_hours_in_day)));
+  END LOOP;
+  FOR i IN 1 .. 5 LOOP
+    DBMS_OUTPUT.put_line('mins = ' || (TRUNC(SYSDATE) + (TRUNC(DBMS_RANDOM.value(0,1000))/l_mins_in_day)));
+  END LOOP;
+  FOR i IN 1 .. 5 LOOP
+    DBMS_OUTPUT.put_line('secs = ' || (TRUNC(SYSDATE) + (TRUNC(DBMS_RANDOM.value(0,1000))/l_secs_in_day)));
+  END LOOP;
+END;
+/
+NOTICE:  hours= 2021-10-13 22:00:00
+CONTEXT:  SQL statement "CALL dbms_output.put_line('hours= ' || (TRUNC(SYSDATE)+ (TRUNC(DBMS_RANDOM.value(0,1000))/l_hours_in_day)))"
+PL/pgSQL function inline_code_block line 6 at PERFORM
+NOTICE:  hours= 2021-10-10 00:00:00
+CONTEXT:  SQL statement "CALL dbms_output.put_line('hours= ' || (TRUNC(SYSDATE)+ (TRUNC(DBMS_RANDOM.value(0,1000))/l_hours_in_day)))"
+PL/pgSQL function inline_code_block line 6 at PERFORM
+NOTICE:  hours= 2021-09-07 02:00:00
+CONTEXT:  SQL statement "CALL dbms_output.put_line('hours= ' || (TRUNC(SYSDATE)+ (TRUNC(DBMS_RANDOM.value(0,1000))/l_hours_in_day)))"
+PL/pgSQL function inline_code_block line 6 at PERFORM
+NOTICE:  hours= 2021-09-26 11:00:00
+CONTEXT:  SQL statement "CALL dbms_output.put_line('hours= ' || (TRUNC(SYSDATE)+ (TRUNC(DBMS_RANDOM.value(0,1000))/l_hours_in_day)))"
+PL/pgSQL function inline_code_block line 6 at PERFORM
+NOTICE:  hours= 2021-09-19 22:00:00
+CONTEXT:  SQL statement "CALL dbms_output.put_line('hours= ' || (TRUNC(SYSDATE)+ (TRUNC(DBMS_RANDOM.value(0,1000))/l_hours_in_day)))"
+PL/pgSQL function inline_code_block line 6 at PERFORM
+NOTICE:  mins = 2021-09-04 00:01:00
+CONTEXT:  SQL statement "CALL dbms_output.put_line('mins = ' || (TRUNC(SYSDATE)+ (TRUNC(DBMS_RANDOM.value(0,1000))/l_mins_in_day)))"
+PL/pgSQL function inline_code_block line 9 at PERFORM
+NOTICE:  mins = 2021-09-04 11:56:00
+CONTEXT:  SQL statement "CALL dbms_output.put_line('mins = ' || (TRUNC(SYSDATE)+ (TRUNC(DBMS_RANDOM.value(0,1000))/l_mins_in_day)))"
+PL/pgSQL function inline_code_block line 9 at PERFORM
+NOTICE:  mins = 2021-09-04 00:53:00
+CONTEXT:  SQL statement "CALL dbms_output.put_line('mins = ' || (TRUNC(SYSDATE)+ (TRUNC(DBMS_RANDOM.value(0,1000))/l_mins_in_day)))"
+PL/pgSQL function inline_code_block line 9 at PERFORM
+NOTICE:  mins = 2021-09-04 00:21:00
+CONTEXT:  SQL statement "CALL dbms_output.put_line('mins = ' || (TRUNC(SYSDATE)+ (TRUNC(DBMS_RANDOM.value(0,1000))/l_mins_in_day)))"
+PL/pgSQL function inline_code_block line 9 at PERFORM
+NOTICE:  mins = 2021-09-04 12:38:00
+CONTEXT:  SQL statement "CALL dbms_output.put_line('mins = ' || (TRUNC(SYSDATE)+ (TRUNC(DBMS_RANDOM.value(0,1000))/l_mins_in_day)))"
+PL/pgSQL function inline_code_block line 9 at PERFORM
+NOTICE:  secs = 2021-09-04 00:10:28
+CONTEXT:  SQL statement "CALL dbms_output.put_line('secs = ' || (TRUNC(SYSDATE)+ (TRUNC(DBMS_RANDOM.value(0,1000))/l_secs_in_day)))"
+PL/pgSQL function inline_code_block line 12 at PERFORM
+NOTICE:  secs = 2021-09-04 00:15:31
+CONTEXT:  SQL statement "CALL dbms_output.put_line('secs = ' || (TRUNC(SYSDATE)+ (TRUNC(DBMS_RANDOM.value(0,1000))/l_secs_in_day)))"
+PL/pgSQL function inline_code_block line 12 at PERFORM
+NOTICE:  secs = 2021-09-04 00:09:07
+CONTEXT:  SQL statement "CALL dbms_output.put_line('secs = ' || (TRUNC(SYSDATE)+ (TRUNC(DBMS_RANDOM.value(0,1000))/l_secs_in_day)))"
+PL/pgSQL function inline_code_block line 12 at PERFORM
+NOTICE:  secs = 2021-09-04 00:06:54
+CONTEXT:  SQL statement "CALL dbms_output.put_line('secs = ' || (TRUNC(SYSDATE)+ (TRUNC(DBMS_RANDOM.value(0,1000))/l_secs_in_day)))"
+PL/pgSQL function inline_code_block line 12 at PERFORM
+NOTICE:  secs = 2021-09-04 00:06:32
+CONTEXT:  SQL statement "CALL dbms_output.put_line('secs = ' || (TRUNC(SYSDATE)+ (TRUNC(DBMS_RANDOM.value(0,1000))/l_secs_in_day)))"
+PL/pgSQL function inline_code_block line 12 at PERFORM
+ANONYMOUS BLOCK EXECUTE
+mogdb=#
+```
+
+<br/>
+
+## Generating Random Data
+
+The `DBMS_RANDOM` package is useful for generating random test data. You can generate large amounts quickly by combining it into a query.
+
+```sql
+mogdb=# CREATE TABLE random_data (
+  id           NUMBER,
+  small_number NUMBER(5),
+  big_number   NUMBER,
+  short_string VARCHAR2(50),
+  long_string  VARCHAR2(400),
+  created_date DATE,
+  CONSTRAINT random_data_pk PRIMARY KEY (id)
+);
+NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index "random_data_pk" for table "random_data"
+CREATE TABLE
+mogdb=#
+```
+
+```sql
+mogdb=# INSERT INTO random_data
+SELECT generate_series(1,29999),
+       TRUNC(DBMS_RANDOM.value(1,5)) AS small_number,
+       TRUNC(DBMS_RANDOM.value(100,10000)) AS big_number,
+       DBMS_RANDOM.string('L',TRUNC(DBMS_RANDOM.value(10,50))) AS short_string,
+       DBMS_RANDOM.string('L',TRUNC(DBMS_RANDOM.value(100,400))) AS long_string,
+       TRUNC(SYSDATE + DBMS_RANDOM.value(0,366)) AS created_date;
+INSERT 0 29999
+mogdb=#
+mogdb=#  select count(*) from random_data;
+ count
+-------
+ 29999
+(1 row)
+
+mogdb=#
+```
diff --git a/product/en/docs-mogdb/v3.0/about-mogdb/open-source-components/compat-tools.md b/product/en/docs-mogdb/v3.0/about-mogdb/open-source-components/compat-tools.md
new file mode 100644
index 0000000000000000000000000000000000000000..cf4fa7b631183ddd2b60d4792e6a59a636664fac
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/about-mogdb/open-source-components/compat-tools.md
@@ -0,0 +1,18 @@
+---
+title: compat-tools
+summary: compat-tools
+author: Zhang Cuiping
+date: 2021-07-14
+---
+
+# compat-tools
+
+This project is a set of compatibility tools. It aims to provide compatibility for necessary functions and system views created for OSs migrated from other asynchronous databases to MogDB, thereby facilitating the follow-up system maintenance and application modification.
+
+The script is executed based on the version information. When you execute the script, it will be executed in terms of the following three situations:
+
+1. If the object to be created does not exist in the target database, it will be directly created.
+2. If the version of the object to be created is later than that of the object in the target database, the target database will be upgraded and has the object re-created.
+3. If the version of the object to be created is earlier than that of the object in the target database, the creation operation will be skipped.
+
+Please refer to [compat-tools repository page](https://gitee.com/enmotech/compat-tools) for details on how to obtain and use component.
diff --git a/product/en/docs-mogdb/v3.0/about-mogdb/open-source-components/mog_filedump.md b/product/en/docs-mogdb/v3.0/about-mogdb/open-source-components/mog_filedump.md
new file mode 100644
index 0000000000000000000000000000000000000000..cdc52654a6599f98cd0606ef9537822c4bf51120
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/about-mogdb/open-source-components/mog_filedump.md
@@ -0,0 +1,106 @@
+---
+title: mog_filedump User Guide
+summary: mog_filedump User Guide
+author: Guo Huan
+date: 2021-11-15
+---
+
+
+
+# mog_filedump User Guide
+
+## Introduction
+
+mog_filedump is a tool for parsing data files ported to MogDB based on the improved compatibility of the pg_filedump tool, which is used to convert MogDB heap/index/control files into user-readable format content. This tool can parse part of the fields in the data columns as needed, and can also dump the data content directly in binary format. The tool can automatically determine the type of the file by the data in the blocks of the file. The **-c** option must be used to format the pg_control file.
+
+<br/>
+
+## Principle
+
+The implementation steps are divided into three main steps.
+
+1. Reads a data block from a data file.
+
+2. Parse the data of the corresponding type with the callback function of the corresponding data type.
+
+3. Call the output of the corresponding data type function to print the data content.
+
+<br/>
+
+## Enmo's Improvements
+
+1. Compatibility porting to MogDB.
+
+2. Fix official bug: parsing bug of data type **char**.
+
+3. Fix official bug: In the multi-field scenario, parsing the data file, the data type name will cause a data length mismatch bug.
+
+<br/>
+
+## Installation
+
+Visit [MogDB official website download page](https://www.mogdb.io/en/downloads/mogdb/) to download the corresponding version of the toolkit, and put the tool in the **bin** directory of the MogDB installation path. As shown below, toolkits-xxxxxx.tar.gz is the toolkit that contains mog_filedump.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/about-mogdb/open-source-components-2.png)
+
+<br/>
+
+## How to Use
+
+```
+mog_filedump [-abcdfhikxy] [-R startblock [endblock]] [-D attrlist] [-S blocksize] [-s segsize] [-n segnumber] file
+```
+
+Valid options for **heap** and **index** files are as follows:
+
+| options | function                                                 |
+| ---- | ------------------------------------------------------------ |
+| -a   | show absolute path                               |
+| -b   | output a range of binary block images |
+| -d   | output file block content                      |
+| -D   | The data type of the table.<br/>Currently supported data types are: bigint, bigserial, bool, charN, date, float, float4, float8, int, json, macaddr, name, oid, real, serial, smallint, smallserial, text, time, timestamp, timetz, uuid, varchar, varcharN, xid, xml, ~. <br/>'~' means ignore all the following data types, for example, the tuple has 10 columns, `-D first three column data types, ~` means that only the first three columns of the table tuple are parsed. |
+| -f   | Output and parse the content of the data block |
+| -h   | Display instructions and help information |
+| -i   | Output and parse item details (including XMIN, XMAX, Block Id, linp Index, Attributes, Size, infomask) |
+| -k   | Verify the checksum of the data block      |
+| -R   | Parse and output the data file contents for the specified LSN range, e.g. **-R startblock [endblock]**. If only has **startblock** and no **endblock**, only output a single data block content |
+| -s   | Set segment size                             |
+| -n   | Set the number of segments                   |
+| -S   | Set data block size                           |
+| -x   | Parse and output block items as index item format (included by default) |
+| -y   | Parse and output block items as heap item format (included by default) |
+
+The options available for the control file are as follows:
+
+| options | function                                       |
+| ------- | ---------------------------------------------- |
+| -c      | List of directories for parsing control files  |
+| -f      | Output and parse the content of the data block |
+| -S      | Sets the block size that controls file parsing |
+
+You can combine the **-i** and **-f** parameters to get more effective data to help operation and maintenance personnel analyze and refer to.
+
+<br/>
+
+## Examples
+
+The test table basically covers the data types contained in mog_filedump.
+
+Here is a use case to show the data parsing function. Please add other parameters according to actual needs.
+
+```sql
+-- Create table test:
+create table test(serial serial, smallserial smallserial, bigserial bigserial, bigint bigint, bool bool, char char(3), date date, float float, float4 float4, float8 float8, int int, json json, macaddr macaddr, name name, oid oid, real real, smallint smallint, text text, time time, timestamp timestamp, timetz timetz, uuid uuid, varchar varchar(20), xid xid, xml xml);
+
+-- Insert data:
+insert into test(bigint, bool, char, date, float, float4, float8, int, json, macaddr, name, oid, real, smallint, text, time, timestamp, timetz, uuid, varchar, xid, xml) values(123456789, true, 'abc', '2021-4-02 16:45:00', 3.1415926, 3.1415926, 3.14159269828412, 123456789, '{"a":1, "b":2, "c":3}'::json, '04-6C-59-99-AF-07', 'lvhui', 828243, 3.1415926, 12345, 'text', '2021-04-02 16:48:23', '2021-04-02 16:48:23', '2021-04-02 16:48:23', 'a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11', 'adsfghkjlzc', '9973::xid', '<title>Book0001</title>');
+
+-- The directory where the data files of the query table test are located. The data directory specified by gs_initdb here is db_p. So the table test data file is in db_p/base/15098/32904
+mogdb=# select pg_relation_filepath('test');
+base/15098/32904 (1 row)
+
+-- Use the mog_filedump tool to parse the data file content:
+./mog_filedump -D serial,smallserial,bigserial,bigint,bool,charN,date,float,float4,float8,int,json,macaddr,name,oid,real,smallint,text,time,timestamp,timetz,uuid,varchar,xid,xml db_p/base/15098/32904
+```
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/reference-guide/mog_filedump.png)
diff --git a/product/en/docs-mogdb/v3.0/about-mogdb/open-source-components/mog_xlogdump.md b/product/en/docs-mogdb/v3.0/about-mogdb/open-source-components/mog_xlogdump.md
new file mode 100644
index 0000000000000000000000000000000000000000..e11969cad7d6d758af17a7dbdb7bc6a27e6891c6
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/about-mogdb/open-source-components/mog_xlogdump.md
@@ -0,0 +1,319 @@
+---
+title: mog_xlogdump User Guide
+summary: mog_xlogdump User Guide
+author: Guo Huan
+date: 2021-11-15
+---
+
+# mog_xlogdump User Guide
+
+## Introduction
+
+mog_xlogdump is an offline parsing tool for wal logs independently developed by Enmo. It is mainly used in the active-standby cluster scenario, when the database is permanently down and cannot be recovered, reversely analyze the database that cannot be started, and then recover the data that is not synchronized at the end of the wal log in the cluster.
+
+<br/>
+
+## R&D Background
+
+In MogDB primary/standby high availability cluster with one primary database and multiple standby databases, using asynchronous logical replication scenario, when the primary shuts down and its transaction is committed, the data of the transaction operation has been written to the wal log. After the primary is down, the standby will generate incomplete data segment logs because it cannot send to the standby. Therefore, after the primary is down, there is data loss and no logical alignment between the standby and the primary. So there is a risk of data loss in the primary/standby cluster composed of its standby databases and the data in the actual business.
+
+During the recovery of the primary database, the cluster composed of the standby database will have business data written. At this time, when the primary database is restored immediately, the segment number, start and end position of the incomplete data segment at the end of the wal log of the primary database are the same as those in the standby database. The inconsistency will also cause the data lost when the primary database shuts down and cannot be restored to the standby database.
+
+<br/>
+
+## Scenario
+
+In a MogDB high-availability cluster, when the primary database is down, the walbuffer is triggered to write to the wal log when the walbuffer is filled with a certain percentage, or when the checkpoint or commit occurs. Due to the database downtime, the logically synchronized WalSender thread stops sending logs, and the standby database receives incomplete data segment wal logs. At this time, you need to use the falshback tool to read the data blocks in the wal log of the primary database, and decode the SQL statement corresponding to the data operation, so that the DBA can analyze whether the data is valuable and restore it to the standby database.
+
+<br/>
+
+## Principle
+
+The tool uses two mechanisms, one is the header parsing of the wal log, and the other is the logical replication mechanism.
+
+The implementation steps are mainly divided into three steps:
+
+1. Read the wal log file and parse the header.
+
+2. Read the data in turn, and de-decode the data.
+
+3. According to the different data types of the data, different types of function outputs are called back.
+
+<br/>
+
+## Supported Table Types for Parsing
+
+Partitioned and normal tables are currently supported.
+
+<br/>
+
+## Supported Data Types for Parsing
+
+bool, bytea, char, name, int8, int2, int, text, oid, tid, xid, cid, xid32, clob, float4, float8, money, inet, varchar, numeric, int4;
+
+> 注意：Note: Since mog_xlogdump is an offline wal parsing tool, it does not currently support large data types (clob, etc.) that require toast data. The next version will support offline parsing of toast table files.
+
+<br/>
+
+## Installation
+
+Visit [MogDB official website download page](https://www.mogdb.io/en/downloads/mogdb/) to download the corresponding version of the toolkit, and put the tool in the **bin** directory of the MogDB installation path. As shown below, toolkits-xxxxxx.tar.gz is the toolkit that contains mog_xlogdump.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/about-mogdb/open-source-components-2.png)
+
+<br/>
+
+## Instructions for Use
+
+mog_xlogdump is a tool for parsing and displaying MogDB-2.1 Wal logs. Auxiliary tool designed to help DBAs analyze and debug database problems.
+
+The mog_xlogdump parsing tool currently does not support column table. (The research found that the column-stored table will generate two corresponding CUDesc and delta tables in cstore mode. CUDesc is the metadata of the column-stored table, and delta is the temporary table of the column-stored table, which is a row-stored table. These two tables (CUDesc, delta) will be written in the wal log. Although the wal log can parse the corresponding delta table, the table is controlled by the table attribute threshold deltarow_threshold. The default is 100, that is, less than 100 pieces of data will be written in the delta table. Write directly to the cu file)
+
+> Note: To write the delta table in the column-store table, you need to enable the parameter **enable_delta_store = on** in postgres.conf.
+
+<br/>
+
+## How to Use
+
+```
+mog_xlogdump [OPTION]... [STARTSEG [ENDSEG]]
+```
+
+<br/>
+
+## Options
+
+- -b, --bkp-details 
+
+  Details of output file blocks. (By default, the id of the block, rel, fork, blk, and lastlsn is displayed, and this parameter will display the Block Image)
+
+- -B, --bytea_output
+
+  Specify the display format of bytea type decoding output, there are binary and character formats
+
+- -c --connectinfo
+
+  Specify a connect string URL, such as postgres://user:password@ip:port/dbname
+
+- -e, --end=RECPTR       
+
+  Specify the end position for parsing the wal log, LSN number
+
+- -f, --follow               
+
+  Indicates that when the specified wal log is parsed to the end, continue parsing to the next file
+
+- -n, --limit=N             
+
+  Specify the number of output data records
+
+- -o, --oid=OID            
+
+  Specifies the OID of the inverse decoding table
+
+- -p, --path=PATH         
+
+  Specify the wal log storage directory
+
+- -R, --Rel=Relation       
+
+  Specifies the data type of the inverse decoding table
+
+- -r, --rmgr=RMGR        
+
+  Show only the contents of records generated by the explorer
+
+- -s, --start=RECPTR      
+
+  Specify the starting position for parsing the wal log, LSN number
+
+- -T, --CTimeZone_ENV    
+
+  Specify the time zone, the default is UTC.
+
+- -t, --timeline=TLI        
+
+  Specify the timeline to start reading the wal log
+
+- -V, --version             
+
+  show version number
+
+- -w, --write-FPW         
+
+  Display the information written on the full page, use with -b
+
+- -x, --xid=XID             
+
+  Output the record with the specified transaction ID
+
+- -z, --stats                
+
+  Output statistics of inserted records
+
+- -v, --verbose             
+
+  show verbose
+
+- -?, --help                
+
+  show help information and exit
+
+<br/>
+
+## Use Case 1
+
+### Scenario
+
+When the primary database is down and cannot be recovered, the standby database can be connected normally. At this time, the wal log sent by the primary database may contain tens of thousands of table data operations, and the mog_xlogdump tool needs to start and end according to the specified -s, -e (starting and the ending lsn position), parse out all data operations of the table.
+
+### Instruction
+
+```
+mog_xlogdump -c <Standby connect string> -s <starting lsn> -e <ending lsn> <primary node wal log file>
+```
+
+### Parse Settings
+
+Note: The main purpose is to record old data in the wal log, that is, the data tuple before the update operation is modified, and the data deleted by the delete operation.
+
+1. Set the **wal_level** in the database configuration file postgres.conf to the **logical** level.
+2. Alter table: `alter table table_name replica identity full;`
+
+### Result
+
+Output the wal log data parsing result in json format. The tuple display format is `'column name':'data'`
+
+```json
+{'table_name':'xxx','schema_name':'yyy','action':'insert','tuple':{'name':'xx','id':'ss'}}
+```
+
+### Example
+
+![fe1b12d080accfb9e54f857e79baebc](https://cdn-mogdb.enmotech.com/docs-media/mogdb/reference-guide/mog_xlogdump-1.png)
+
+The red box is the old data that will be parsed according to the parsing settings. If there is no setting, the old data of update and delete will not be parsed.
+
+The standby connect URL after -c is `postgres://test:Test123456@172.16.0.44:5003/postgres`
+
+- postgres://
+
+  connect string tag header
+
+- test
+
+  connect username
+
+- Test123456
+
+  The password of the connect user
+
+- 172.16.0.44
+
+  The IP address of the standby node
+
+- 5003
+
+  Standby connect port
+
+- postgres
+
+  The database name of the connect standby node
+
+- db_p/pg_xlog/000000010000000000000004
+
+  The wal log file of primary node
+
+ <br/>
+
+## Use Case 2
+
+### Scenario
+
+When the primary database is down and cannot be recovered, and the standby database can be connected normally, the user may only pay attention to a few tables (individual tables) in the database. The mog_xlogdump tool can parse the table data of the specified oid according to the parameters -o and -R. For example, -o specifies the oid of the table, and -R specifies the field type of the table.
+
+### Instruction
+
+Create a table, write data and modify it, and use the mog_xlogdump tool to parse the Wal log.
+
+```sql
+create table t2(id int, money money,inet inet,bool bool,numeric numeric ,text text);
+insert into t2 values(1, 24.241, '192.168.255.132', true, 3.1415926, 'ljfsodfo29892ifj');
+insert into t2 values(2, 928.8271, '10.255.132.101', false, 3.1415926, 'vzvzcxwf2424@');
+update t2 set id=111, money=982.371 where id =2;
+delete from t2 where id=1;
+
+postgres=# select * from t2;
+ id | money |   inet    | bool | numeric |    text    
+----+---------+-----------------+------+-----------+------------------
+ 1 | $24.24 | 192.168.255.132 | t  | 3.1415926 | ljfsodfo29892ifj
+ 2 | $928.83 | 10.255.132.101 | f  | 3.1415926 | vzvzcxwf2424@
+(2 rows)
+
+postgres=# update t2 set id=111, money=982.371 where id =2;
+Postgres=# delete from t2 where id=1;
+postgres=# select * from t2;
+ id |  money  |   inet   | bool | numeric |   text   
+-----+-------------+----------------+------+-----------+---------------
+ 111 | $982,371.00 | 10.255.132.101 | f  | 3.1415926 | vzvzcxwf2424@
+ 
+(1 rows)
+```
+
+### Parse Settings
+
+Same as use case 1, set wal_level and alter table.
+
+### Result
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/reference-guide/mog_xlogdump-2.png)
+
+```json
+./mog_xlogdump -o 16394 -R int,money,inet,bool,numeric,text ./db_p/pg_xlog/000000010000000000000004 
+'insert','tuple':{'(null)':'1','(null)':'$24.24','(null)':'192.168.255.132','(null)':true,'(null)':'3.1415926','(null)':'ljfsodfo29892ifj'}}
+'insert','tuple':{'(null)':'2','(null)':'$928.83','(null)':'10.255.132.101','(null)':false,'(null)':'3.1415926','(null)':'vzvzcxwf2424@'}}
+'update','old_tuple':{'(null)':'2','(null)':'$928.83','(null)':'10.255.132.101','(null)':false,'(null)':'3.1415926','(null)':'vzvzcxwf2424@'},'new_tuple':{'(null)':'111','(null)':'$982,371.00','(null)':'10.255.132.101','(null)':false,'(null)':'3.1415926','(null)':'vzvzcxwf2424@'}}
+'delete','tuple':{'(null)':'1','(null)':'$24.24','(null)':'192.168.255.132','(null)':true,'(null)':'3.1415926','(null)':'ljfsodfo29892ifj'}}
+```
+
+> Note: Due to the change of the output format, the table name, schema name and column name are queried on the standby node according to the -c connect string, but because the original -o, -R designation of the table oid and field type is completely offline, Therefore, information such as table name, schema name, and column name cannot be obtained, so use -o and -R to parse offline. The table name and schema name are not displayed, and the column name is displayed as null.
+
+```
+mog_xlogdump -o <table OID> -R <the data type of the table> -s <starting LSN> -e <ending LSN> Wal log file
+```
+
+The tool also retains the original functionality of pg_xlogdump.
+
+<br/>
+
+## Use Case 3
+
+### Scenario
+
+If you want to see the header data content of the wal log, or to count some related information of the wal log, please use the mog_xlogdump original function.
+
+### Instruction
+
+1. header information
+
+   ```
+   ./mog_xlogdump -n 10 <wal log file>
+   ```
+
+   -n 10 indicates that only 10 rows of data are displayed.
+
+2. Statistics
+
+   ```
+   ./mog_xlogdump -z <wal log file>
+   ```
+
+### Results
+
+- Result 1
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/reference-guide/mog_xlogdump-3.png)
+
+- Result 2
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/reference-guide/mog_xlogdump-4.png)
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/about-mogdb/open-source-components/mogdb-monitor.md b/product/en/docs-mogdb/v3.0/about-mogdb/open-source-components/mogdb-monitor.md
new file mode 100644
index 0000000000000000000000000000000000000000..b5ae7c9fa118df1b1b12a725fc28e81870a3fb00
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/about-mogdb/open-source-components/mogdb-monitor.md
@@ -0,0 +1,27 @@
+---
+title: mogdb-monitor
+summary: mogdb-monitor
+author: Guo Huan
+date: 2022-04-14
+---
+
+# mogdb-monitor
+
+mogdb-monitor is a MogDB database cluster monitoring and deployment tool, with the help of the current very popular open source monitoring system prometheus framework, combined with the opengauss_exporter developed by Enmo database team, you can achieve a full range of detection of MogDB database.
+
+The core monitoring component opengauss_exporter has the following features.
+
+- Support all versions of MogDB/openGauss database
+- Support for monitoring database clusters
+- Support primary and standby database judgment within a cluster
+- Support for automatic database discovery
+- Support for custom query
+- Supports online loading of configuration files
+- Support for configuring the number of concurrent threads
+- Support data collection information caching
+
+In terms of grafana display, Enmo also provide a complete set of dashboard, both an instance-level dashboard showing detailed information of each instance and a display big screen showing summary information of all instances, which, combined with the alertmanager component, can trigger alerts that meet the rules to relevant personnel in the first place.
+
+<br/>
+
+Please refer to [mogdb-monitor repository page](https://gitee.com/enmotech/mogdb-monitor) for details on how to obtain and use component.
diff --git a/product/en/docs-mogdb/v3.0/about-mogdb/roadmap.md b/product/en/docs-mogdb/v3.0/about-mogdb/roadmap.md
new file mode 100644
index 0000000000000000000000000000000000000000..321b2788e05facbd361337ed9de494797ce383bb
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/about-mogdb/roadmap.md
@@ -0,0 +1,81 @@
+---
+title: Roadmap
+summary: Roadmap
+author: Guo Huan
+date: 2021-06-15
+---
+
+# Roadmap
+
+This document introduces the roadmap for MogDB 2.0.1.
+
+<table>
+    <tr>
+        <th>Components</th>
+        <th>Unmerged content</th>
+    </tr>
+    <tr>
+        <td rowspan="4">MogHA</td>
+        <td>Support for automatic restart of primary instance</td>
+    </tr>
+    <tr>
+        <td>Support for database CPU usage limit setting</td>
+    </tr>
+    <tr>
+        <td>Support for customization of HA switching</td>
+    </tr>
+    <tr>
+        <td>Support for WEB interface, API and so on, facilitating small-scale deployment (EA phase)</td>
+    </tr>
+    <tr>
+        <td rowspan="10">MogDB Server</td>
+        <td>Support setting the primary node to global read-only, which can prevent brain-split in the case of network isolation</td>
+    </tr>
+    <tr>
+        <td>Support for pg trgm plugin (full-text indexing plugin)</td>
+    </tr>
+    <tr>
+        <td>Support for custom operators and custom operator classes</td>
+    </tr>
+    <tr>
+        <td>Reduce resource consumption for database metrics collection</td>
+    </tr>
+    <tr>
+        <td>Optimize partition creation syntax</td>
+    </tr>
+     <tr>
+        <td>Support sorting of CJK (East Asian character set), with better performance for sorting large data volumes</td>
+    </tr>
+     <tr>
+        <td>Support for xid-based flashback queries</td>
+    </tr>
+     <tr>
+        <td>Support for sub partitions</td>
+    </tr>
+     <tr>
+        <td>Support for citus plug-in, enable scale-out to enhance distributed capacity</td>
+    </tr>
+     <tr>
+        <td>Support for online reindex without locking tables</td>
+    </tr>
+    <tr>
+        <td rowspan="2">MogDB Client</td>
+        <td>Go client: support for the SHA256 encryption algorithm</td>
+    </tr>
+    <tr>
+        <td>Python client: support for the SHA256 encryption algorithm and support for automatic identification of the primary node</td>
+    </tr>
+    <tr>
+        <td rowspan="4">MogDB plugin</td>
+        <td>Compatibility support for wal2json plug-in used for the export and heterogeneous replication of the current logical log </td>
+    </tr>
+    <tr>
+        <td>Support for pg_dirtyread plug-in used for data recovery and query under special circumstances</td>
+    </tr>
+    <tr>
+        <td>Support for walminer plug-in used for online WAL log parsing (no reliance on logical logs)</td>
+    </tr>
+    <tr>
+        <td>Support for db_link plug-in used for connecting to PostgreSQL databases from MogDB</td>
+    </tr>
+</table>
diff --git a/product/en/docs-mogdb/v3.0/about-mogdb/terms-of-use.md b/product/en/docs-mogdb/v3.0/about-mogdb/terms-of-use.md
new file mode 100644
index 0000000000000000000000000000000000000000..4d6b1b0e8cbf657dd9b9fad24d592c840788a0ce
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/about-mogdb/terms-of-use.md
@@ -0,0 +1,22 @@
+---
+title: Terms of Use
+summary: Terms of Use
+author: Guo Huan
+date: 2021-06-01
+---
+
+# Terms of Use
+
+**Copyright © 2009-2022 Yunhe Enmo (Beijing) Information Technology Co., Ltd. All rights reserved.**
+
+Your replication, use, modification, and distribution of this document are governed by the Creative Commons License Attribution-ShareAlike 4.0 International Public License (CC BY-SA 4.0). You can visit <https://creativecommons.org/licenses/by-sa/4.0/> to view a human-readable summary of (and not a substitute for) CC BY-SA 4.0. For the complete CC BY-SA 4.0, visit <https://creativecommons.org/licenses/by-sa/4.0/legalcode>.
+
+Certain document contents on this website are from the official openGauss website (<https://opengauss.org/en/docs/1.1.0/docs/Quickstart/Quickstart.html>)。
+
+**Trademarks and Permissions**
+
+MogDB is a trademark of Yunhe Enmo (Beijing) Information Technology Co., Ltd. All other trademarks and registered trademarks mentioned in this document are the property of their respective holders.
+
+**Disclaimer**
+
+This document is used only as a guide. Unless otherwise specified by applicable laws or agreed by both parties in written form, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, including but not limited to non-infringement, timeliness, and specific purposes.
diff --git a/product/en/docs-mogdb/v3.0/about-mogdb/test-report/ha/1-database-server-exception-testing.md b/product/en/docs-mogdb/v3.0/about-mogdb/test-report/ha/1-database-server-exception-testing.md
new file mode 100644
index 0000000000000000000000000000000000000000..d799f1af3b37587385b0cef961d1b20f7e5d49e4
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/about-mogdb/test-report/ha/1-database-server-exception-testing.md
@@ -0,0 +1,194 @@
+---
+title: MogDB Database Server Exception Testing
+summary: MogDB Database Server Exception Testing
+author: Liu Xu
+date: 2021-03-04
+---
+
+# MogDB Database Server Exception Testing
+
+## Test Objective
+
+The test aims to test the MogDB availability and stability in the scenarios where only one of the primary, standby, and arbitration MogDB nodes crashes, both primary and standby MogDB nodes crash, both primary and arbitration MogDB nodes crash, or both standby and arbitration MogDB nodes crash.
+
+## Test Environment
+
+| Category    |     Server Configuration     | Client Configuration | Quantity |
+| ----------- | :--------------------------: | :------------------: | :------: |
+| CPU         |         Kunpeng 920          |     Kunpeng 920      |   128    |
+| Memory      |        DDR4,2933MT/s         |    DDR4,2933MT/s     | 2048 GB  |
+| Hard disk   |          Nvme 3.5T           |       Nvme 3T        |    4     |
+| File system |             Xfs              |         Xfs          |    4     |
+| OS          |    openEuler 20.03 (LTS)     |      Kylin V10       |          |
+| Database    | MogDB 1.1.0 software package |                      |          |
+| Test tool   |           pgbench            |                      |          |
+
+## The Primary Database Node Crashes Abnormally
+
+Test solution:
+
+1. Restart the primary database node.
+2. Monitor the TPS change.
+3. Add a new standby node.
+4. Monitor the cluster status and TPS change.
+
+Test procedure:
+
+1. Restart the primary database node.
+
+   ```bash
+   reboot
+   ```
+
+2. Make the original primary database node work as a standby database node in the cluster.
+
+   ```bash
+   gs_ctl -b full build -D /gaussdata/openGauss/db1
+   ```
+
+3. Synchronize logs to the new standby database node until the synchronization is complete.
+
+Test result:
+
+- After the primary database node is shut down,  TPS drops from 9000 to 0, which lasts for 50s or so. After a VIP is added to the new primary database node (node 2), TPS increases from 0 to 13000 or so.
+- When the old primary database node is added to the cluster working as a new standby database node and operated for data synchronization, TPS drops from 13000 to 0. As the synchronization is complete, TPS is restored to 9000.
+
+## The Standby Database Node Crashes Abnormally
+
+Test solution:
+
+1. Restart the standby database node.
+
+2. Monitor the TPS change.
+
+3. Add the standby database node to the cluster.
+
+4. Monitor the cluster status and TPS change.
+
+Test procedure:
+
+1. Restart the standby database node.
+
+   ```
+   reboot
+   ```
+
+2. Add the standby database node to the cluster.
+
+   ```
+   gs_ctl start -D /gaussdata/openGauss/db1 -M standby
+   ```
+
+3. Synchronize data to the standby database node until the synchronization is complete.
+
+   ```
+   Standby Catchup
+   ```
+
+Test result:
+
+- After the standby database node is shut down, TPS increases from 9000 or so to 13000 or so.
+- After the standby database node is added to the cluster and operated for data synchronization, TPS drops from 13000 to 0. As the synchronization is complete, TPS is restored to 9000.
+
+## The Arbitration Node Crashes Abnormally
+
+Test solution:
+
+1. Add a VIP to the value of the **ping_list** parameter in the **node.conf** file.
+2. Simulate the scenario where the arbitration node crashes.
+
+Test procedure:
+
+1. Add a VIP to the server IP addresses.
+
+   ```
+   ifconfig ens160:1 192.168.122.111 netmask 255.255.255.0
+   ```
+
+2. Add a VIP to the value of the **ping_list** parameter in the **node.conf** file. Synchronize the configuration file between the primary and standby database nodes and restart the monitor script.
+
+3. When the monitor script is running normally, disconnect the VIP of the simulated arbitration node and then observe the change.
+
+   ```
+   ifconfig ens160:1 down
+   ```
+
+4. Manually connect the VIP of the simulated arbitration node and observe the change.
+
+Test result:
+
+- The monitor script of the primary and standby database nodes reports that the VIP of the arbitration node fails the ping operation. no other change occurs.
+- TPS does not change.
+
+## Both Primary and Standby Database Nodes Crash Abnormally
+
+Test solution:
+
+1. Restart both the primary and standby database nodes.
+2. Start the **node_run** scripts of the primary and standby database nodes.
+3. Manually enable the primary and standby databases.
+
+Test procedure:
+
+1. Restart both the primary and standby database nodes.
+
+   ```
+   reboot
+   reboot
+   ```
+
+2. Start the **node_run** scripts of the primary and standby database nodes.
+
+3. Manually enable the primary and standby databases.
+
+Test result:
+
+When the database is disabled, TPS drops to 0. After 15s the cluster is started, TPS increases to 9000.
+
+## Both Primary and Arbitration Nodes Crash Abnormally
+
+Test solution:
+
+Shut down the primary database node and disconnect the IP address of the arbitration node.
+
+Test procedure:
+
+1. Shut down the primary database node and disconnect the IP address of the arbitration node.
+
+2. Check the status of the standby database node.
+
+3. Start the primary database node and its monitor script.
+
+   ```
+   gs_ctl start -D /gaussdata/openGauss/db1 -M primary
+   ```
+
+4. Check the cluster status.
+
+Test result:
+
+- After the primary database node and arbitration node are shut down, TPS drops from 9000 to 0.
+
+- When the primary database node restores, TPS increases to 9000.
+
+## Both Standby and Arbitration Nodes Crash Abnormally
+
+Test solution:
+
+Shut down the standby database node and disconnect the IP address of the arbitration node.
+
+Test procedure:
+
+1. Shut down the standby database node and disconnect the IP address of the arbitration node.
+
+2. Check the status of the primary database node.
+
+   No change occurs.
+
+3. After the standby database node restores, start the monitor script of the standby database node.
+
+   The error reported by the monitor script of the primary database node disappears.
+
+4. Start the standby database node.
+
+5. Check the cluster status.
diff --git a/product/en/docs-mogdb/v3.0/about-mogdb/test-report/ha/2-network-exception-testing.md b/product/en/docs-mogdb/v3.0/about-mogdb/test-report/ha/2-network-exception-testing.md
new file mode 100644
index 0000000000000000000000000000000000000000..50b695b52400152bfa92fb43f1689d8352ba72f1
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/about-mogdb/test-report/ha/2-network-exception-testing.md
@@ -0,0 +1,177 @@
+---
+title: MogDB Network Exception Testing
+summary: MogDB Network Exception Testing
+author: Liu Xu
+date: 2021-03-04
+---
+
+# MogDB Network Exception Testing (Need to Be Reviewed Later)
+
+## Test Scope
+
+- The service NIC of the primary node is abnormal.
+
+- The heartbeat NIC of the primary node is abnormal.
+
+- Both the service and heartbeat NICs of the primary node are abnormal.
+
+- The service NIC of the standby node is abnormal.
+
+- The heartbeat NIC of the standby node is abnormal.
+
+- The VIP of the primary node is disconnected.
+
+## Test Environment
+
+| Category    |    Server Configuration     | Client Configuration | Quantity |
+| ----------- | :-------------------------: | :------------------: | :------: |
+| CPU         |         Kunpeng 920         |     Kunpeng 920      |   128    |
+| Memory      |        DDR4,2933MT/s        |    DDR4,2933MT/s     | 2048 GB  |
+| Hard disk   |          Nvme 3.5T          |       Nvme 3T        |    4     |
+| File system |             Xfs             |         Xfs          |    4     |
+| OS          |    openEuler 20.03 (LTS)    |      Kylin V10       |          |
+| Database    | MogDB1.1.0 software package |                      |          |
+| Test tool   |           pgbench           |                      |          |
+
+## The Service NIC of the Primary Database Node Is Abnormal
+
+Test solution:
+
+1. Disable the heartbeat NIC and then enable it.
+2. Observe the database status.
+
+Test procedure:
+
+1. Record the original cluster status.
+
+2. Disable the heartbeat NIC and then enable it.
+
+3. Observe the status of the standby database node.
+
+   The standby database node cannot be connected to the primary database node.
+
+4. Query the cluster status.
+
+   No primary/standby switchover occurs.
+
+Test result:
+
+1. No primary/standby switchover occurs.
+2. When the network of the primary database node restores, the status of the standby database node becomes normal.
+3. When the service NIC of the primary database node is abnormal, TPS decreases from 9000 to 0. After 15s when the service NIC is enabled, TPS increases from 0 to 9000.
+
+## The Heartbeat NIC of the Primary Database Node Is Abnormal
+
+Test solution:
+
+1. Disable the heartbeat NIC and then enable it.
+2. Observe the database status.
+
+Test procedure:
+
+1. Observe the database status.
+
+2. Disable the heartbeat NIC and then enable it.
+
+3. Observe the database status.
+
+   No primary/standby switchover occurs.
+
+4. Observe the cluster status.
+
+Test result:
+
+1. No primary/standby switchover occurs.
+
+2. TPS does not change.
+
+## Both the Service and Heartbeat NICs of the Primary Database Node Are Abnormal
+
+Test solution:
+
+1. Disable the heartbeat NIC and then enable it.
+
+2. Observe the database status.
+
+Test procedure:
+
+1. Observe the original database status.
+
+2. Disable the heartbeat NIC and then enable it.
+
+   The primary database node is normal.
+
+Test result:
+
+1. No primary/standby switchover occurs.
+
+2. When the service NIC is disconnected, TPS drops from 9000 to 0. After the service NIC is restored to normal, TPS increases to 9000.
+
+## The Service NIC of the Standby Database Node Is Abnormal
+
+Test solution:
+
+1. Disable the heartbeat NIC and then enable it.
+
+2. Observe the database status.
+
+Test procedure:
+
+1. Record the original cluster status.
+
+2. Disable the heartbeat NIC and then enable it.
+
+3. Observe the status of the primary database node.
+
+4. Ping the IP address of the service NIC of the standby database node.
+
+   The IP address cannot be pinged.
+
+   No primary/standby switchover occurs.
+
+Test result:
+
+1. The monitor script of the standby database node reports the heartbeat error indicating that no primary/standby switchover occurs.
+
+2. When the service NIC of the standby database node is abnormal, TPS of the primary database node increases to 13000. After the service NIC of the standby database node is restored to normal, TPS of the primary database node is restored to 9000.
+
+## The Heartbeat NIC of the Standby Database Node Is Abnormal
+
+Test solution:
+
+1. Disable the heartbeat NIC 60s and then enable it.
+
+2. Observe the database status.
+
+Test procedure:
+
+1. Observe the original database status.
+
+2. Disable the heartbeat NIC 60s and then enable it.
+
+3. After the script is executed, observe the database status.
+   No primary/standby switchover occurs. The monitor script of the primary database node reports an error that the IP address of the service NIC of the standby database node cannot be pinged.
+
+Test result:
+
+No primary/standby switchover occurs.
+
+## The VIP of the Primary Database Node Is Disconnected
+
+Test solution:
+
+Disable the NIC **bond0:1** and then enable it.
+
+Test procedure:
+
+1. Disable the NIC **bond0:1** and then enable it.
+
+2. Observe the database status.
+
+3. Observe the VIP of the primary database node.
+
+Test result:
+
+1. The VIP of the primary database node is automatically connected.
+
+2. When the VIP is disconnected and then connected, the TPS status is restored to normal.
diff --git a/product/en/docs-mogdb/v3.0/about-mogdb/test-report/ha/3-routine-maintenance-testing.md b/product/en/docs-mogdb/v3.0/about-mogdb/test-report/ha/3-routine-maintenance-testing.md
new file mode 100644
index 0000000000000000000000000000000000000000..d50a8f807f6607bd89a1c2b875c121fb9c76f3fc
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/about-mogdb/test-report/ha/3-routine-maintenance-testing.md
@@ -0,0 +1,133 @@
+---
+title: Routine Maintenance Testing
+summary: Routine Maintenance Testing
+author: Guo Huan
+date: 2021-04-25
+---
+
+# Routine Maintenance Testing
+
+## Test Scope
+
+1. HA tool used for the switchover test
+2. gs_ctl used for the switchover test
+3. HA tool used for the failover test
+4. gs_ctl used for the failover test
+5. gs_ctl and HA contradiction test
+6. Split-brain test for avoiding deploying two primary database nodes
+
+## Test Environment
+
+| Category    | Server Configuration  | Client Configuration | Quantity |
+| ----------- | :-------------------: | :------------------: | :------: |
+| CPU         |      Kunpeng 920      |     Kunpeng 920      |   128    |
+| Memory      |     DDR4,2933MT/s     |    DDR4,2933MT/s     |  2048G   |
+| Hard disk   |       Nvme 3.5T       |       Nvme 3T        |    4     |
+| File system |          Xfs          |         Xfs          |    4     |
+| OS          | openEuler 20.03 (LTS) |      Kylin V10       |          |
+| Database    |      MogDB1.1.0       |                      |          |
+| Tool        |        pgbench        |                      |          |
+
+## HA Tool Used for the Switchover Test
+
+Test procedure:
+
+1. Query the status of databases.
+
+2. Run the switch command on the standby database, and then query the database status.
+
+    ```bash
+    /home/omm/venv/bin/python3 /home/omm/openGaussHA_standlone/switch.py -config /home/omm/openGaussHA_standlone/node.conf --switchover
+    ```
+
+3. Query the VIP of the new primary database node.
+
+Test result:
+
+The primary/standby switchover is normal.
+
+## gs_ctl Used for the Switchover Test
+
+Test procedure:
+
+1. Query the database status.
+2. Run the command to perform the switchover operation and query the status when finished.
+3. Query the VIP.
+
+Test result:
+
+The primary/standby switchover is normal.
+
+## HA Tool Used for the Failover Test
+
+Test procedure:
+
+1. Query the current status of the database.
+
+2. Run the HA failover command.
+
+3. Observe the cluster status.
+
+4. The original standby database node works as a new primary database node.
+
+Test result:
+
+1. The original standby database node becomes the new primary database node with a VIP.
+
+2. The original primary database node is killed.
+
+3. TPS increases from 6000 to 13000 in about 10s after failover.
+
+## gs_ctl Used for the Failover Test
+
+Test procedure:
+
+1. Query the current status of the database.
+2. Run the gs_ctl failover command.
+3. Query the status of the new primary database node.
+4. Query the status of the original primary database node.
+5. Observe script changes.
+
+Test result:
+
+1. The new primary database node waits for 10s and then automatically shuts down, the original primary database node is not affected, and the VIP is still attached to the original primary database node.
+2. About 5s or 6s after failover of the standby database node, the TPS increases from 9000 to 13000. No other changes occur except fluctuations.
+
+## gs_ctl and HA Contradiction Test
+
+Test procedure:
+
+1. Record the cluster status.
+
+2. Stop the primary and standby database nodes at the same time.
+
+3. Use gs_ctl to start the primary and standby database nodes. Designate the original standby database node as the primary database node, vice versa.
+
+4. Observe the script and cluster status.
+
+Test result:
+
+1. HA configuration is adjusted according to the actual situation.
+2. TPS drops from 9000 to 0 after the primary and standby database nodes are shut down. At this time, HA detects the cluster configuration change and attaches the VIP to the new primary database node within 10s. After about 5s or 6s, TPS rises from 0 to 13000.
+
+## Split-Brain Test for Avoiding Deploying Two Primary Database Nodes
+
+Test procedure:
+
+1. Query the current status of the cluster.
+
+2. Use the gs_ctl command to restart the standby database node to make it work as the primary database node.
+
+Test result:
+
+1. After timeout for 10s, the primary database node that was restarted by an abnormal operation is killed by the monitoring script.
+
+2. Repair the standby database node and add it to the cluster.
+
+    ```bash
+    gs_ctl build -b full -D /gaussdata/openGauss/db1
+    ```
+
+3. TPS increases from 6000 to 13000 after the standby database is restarted to work as the primary database node.
+
+4. TPS drops from 13000 to 9000 (same as that in the primary/standby deployment scenario) after the standby database node is added to the cluster.
diff --git a/product/en/docs-mogdb/v3.0/about-mogdb/test-report/ha/4-service-exception-testing.md b/product/en/docs-mogdb/v3.0/about-mogdb/test-report/ha/4-service-exception-testing.md
new file mode 100644
index 0000000000000000000000000000000000000000..119b5875829cbd534eb533e50542ac8fe74fecaa
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/about-mogdb/test-report/ha/4-service-exception-testing.md
@@ -0,0 +1,84 @@
+---
+title: MogDB Service Exception Testing
+summary: MogDB Service Exception Testing
+author: Guo Huan
+date: 2021-04-25
+---
+
+# MogDB Service Exception Testing
+
+## Test Scope
+
+1. Database process exception for the standby node
+
+2. Monitor script exception for the standby node
+
+3. File system exception for the primary node (affecting HA process)
+
+## Test Environment
+
+| Category    | Server Configuration  | Client Configuration | Quantity |
+| ----------- | :-------------------: | :------------------: | :------: |
+| CPU         |      Kunpeng 920      |     Kunpeng 920      |   128    |
+| Memory      |     DDR4,2933MT/s     |    DDR4,2933MT/s     |  2048G   |
+| Hard Disk   |       Nvme 3.5T       |       Nvme 3T        |    4     |
+| File system |          Xfs          |         Xfs          |    4     |
+| OS          | openEuler 20.03 (LTS) |      Kylin V10       |          |
+| Database    |      MogDB1.1.0       |                      |          |
+| Tool        |        pgbench        |                      |          |
+
+## Database process exception for the standby node
+
+Test procedure:
+
+Kill the database process.
+
+Test result:
+
+1. Observe the cluster status.
+
+2. The script of the standby database node shows the heartbeat exception.
+
+3. No switchover occurs.
+
+4. Run the command on the standby database node.
+
+    ```bash
+    gs_ctl start -D /gaussdata/openGauss/db1 -M standby
+    ```
+
+5. The cluster is restored to normal and no switchover has occurred since then.
+
+6. When the standby database process is killed, TPS of the primary database node rises from 9000 to 13000.
+
+7. No primary/standby switchover occurs.
+
+## Monitor script exception for the standby node
+
+Test procedure:
+
+Kill the monitor script of the primary database node.
+
+Test result:
+
+1. Observe the cluster status.
+2. No switchover occurs.
+3. The monitor script of the primary database node reports script exception of the standby database node.
+4. Restore the monitor script of the standby database node.
+5. TPS maintains at 9000.
+
+## File system exception for the primary node (affecting HA process)
+
+Test procedure:
+
+Modify the permission of the primary database script called by HA, such as gs_ctl.
+
+Test result:
+
+1. After modifying the **rwx** permission of gs_ctl, the monitoring script of the primary database node reports heartbeat exception.
+
+2. The instance status cannot be detected.
+
+3. Query the current cluster status.
+
+4. After waiting about two minutes, no switchover occurs.
diff --git a/product/en/docs-mogdb/v3.0/about-mogdb/test-report/ha/MogDB-ha-test-report.md b/product/en/docs-mogdb/v3.0/about-mogdb/test-report/ha/MogDB-ha-test-report.md
new file mode 100644
index 0000000000000000000000000000000000000000..1ad5c7de3fff55835ff2319899739b5bd56d5160
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/about-mogdb/test-report/ha/MogDB-ha-test-report.md
@@ -0,0 +1,36 @@
+---
+title: HA Test
+summary: HA Test
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# HA Test
+
+## Test Objective
+
+Database HA (high availability) test aims at providing users with high-quality services, avoiding service interruption caused by such faults as server crash. Its HA lies in not only whether a database can provide services consistently but whether a database can ensure data consistency.
+
+## Test Environment
+
+| Category    |  Server Configuration   | Client Configuration | Quantity |
+| ----------- | :---------------------: | :------------------: | :------: |
+| CPU         |       Kunpeng 920       |     Kunpeng 920      |   128    |
+| Memory      |     DDR4, 2933MT/s      |    DDR4, 2933MT/s    | 2048 GB  |
+| Hard disk   |       NVME 3.5 TB       |      NVME 3 TB       |    4     |
+| File system |           Xfs           |         Xfs          |    4     |
+| OS          |  openEuler 20.03 (LTS)  |      Kylin V10       |          |
+| Database    | MogDB  software package |                      |          |
+| Test tool   |         pgbench         |                      |          |
+
+## HA and Scalability Test
+
+| No.  | Test Item                             | Description                                                  |
+| ---- | ------------------------------------- | ------------------------------------------------------------ |
+| 1    | Cluster with read-write separation    | Supports separate routing of read and write requests and separate distribution of read and write tasks. |
+| 2    | Capacity expansion/capacity reduction | In load scenarios, adding or reducing a physical device does not make a front-end application service interrupted. |
+| 3    | Shared storage cluster                | Supports two nodes sharing a storage cluster, automatic failover, and load balancing of concurrent transactions. |
+| 4    | Service exception test                | Guarantees the availability of an application in scenarios where the process of the standby database, the monitoring script of the standby database, and the file system of the primary database are abnormal. |
+| 5    | Routine maintenance test              | Supports the switchover feature provided by gs_ctl (database service control tool) and the failover feature provided by MogHA (HA component). |
+| 6    | Database server exception test        | Maximizes the availability and stability of an application when the primary node, standby node, or arbitration node crashes, or both the primary and standby nodes, or both the primary and arbitration nodes crash. |
+| 7    | Network exception test                | Maximizes the availability of an application when the service or heartbeat NIC of the primary node is abnormal, both the service and heartbeat NICs of the primary node are abnormal, the service NIC of the standby node is abnormal, or the VIP of the host is abnormal. |
diff --git a/product/en/docs-mogdb/v3.0/about-mogdb/test-report/performance/1-performance-test-overview.md b/product/en/docs-mogdb/v3.0/about-mogdb/test-report/performance/1-performance-test-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..d6a786378b0381b8075acc952699df1a7924370e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/about-mogdb/test-report/performance/1-performance-test-overview.md
@@ -0,0 +1,90 @@
+---
+title: Performance Test Overview
+summary: Performance Test Overview
+author: Liu Xu
+date: 2021-04-27
+---
+
+# Performance Test Overview
+
+## Test Indicators
+
+### Data Volume
+
+Each repository contains 70 MB of data. To simulate the actual data environment, 1000 repositories are created during initiation. After related indexes are added, the total size of data reaches 100 GB or so.
+
+### Number of Concurrent Requests
+
+This is to simulate the real user behavior and make the number of online user requests from the clients reach a certain number.
+
+### Average System Workload
+
+System workload indicates how busy the system CPU is, for example, how many processes are there waiting for being scheduled by the CPU, which reflects the pressure of the whole system. However, average system workload indicates the average number of processes in run queues in a specified time period, generally 1, 5, or 10 minutes.
+
+### CPU Usage
+
+CPU usage indicates the quantity of CPU resources occupied by the running programs, that is, the quantity of running programs on a server at a time point. High CPU usage indicates that a server runs a plenty of programs and vice versa. Whether the CPU usage is high or low is directly related to the CPU performance. CPU usage can determine whether a CPU reaches its bottleneck.
+
+### IOPS
+
+IOPS (Input/Output Operations Per Second) is a method for measuring the performance of a computer storage device, such as HDDs, SSDs, or SANs. It refers to the number of write/read times per second, which is one of the major indicators for measuring the disk performance. IOPS indicates the number of I/O requests that can be processed by the system in unit time. The I/O requests usually refer to data write/read requests.
+
+### IO Latency
+
+IO latency is also called IO response time, referring the time period from the time when the OS kernel sends a write/read command to the time when the OS kernel receives the IO response. Time for operating single IO indicates only the time of processing single IO in a disk. However, IO latency includes even the time of waiting for being processed for an IO in a queue.
+
+### tpmC
+
+TPC-C uses three performance and price metrics. TPC-C is used to measure performance with the unit of tpmC (Transactions Per Minute). C refers to the C benchmark program of TPC. tpmC indicates the number of new orders that are processed by the system per minute.
+
+## Test Program Preparation
+
+### Test Tools
+
+BenchmarkSQL is a typical open source database test tool with a built-in TPC-C test script which can be directly used for testing PostgreSQL, MySQL, Oracle, and SQL Server databases. It is used for testing TPC-C of OLTP (Online Transaction Processing) via JDBC (Java Database Connectivity).
+
+### Test Specifications
+
+TPC-C offers OLTP system test specifications and tests an OLTP system using a merchandising model. Transactions are divided into five categories, the content and characteristics of which are described as follows:
+
+- **NewOrder - Generation of new orders**
+
+  Transaction content: For any one client, select 5 to 15 commodities from a specified repository and create new orders with 1% of the orders that fails the operation and requires rollback.
+
+  Main characteristics: middleweight, frequent write/read operations, and high response speed
+
+- **Payment - Payment of order**
+
+  Transaction content: For any one client, select a region and customers there from a specified repository randomly, pay an order with a random amount of money, and record this operation.
+
+  Main characteristics: lightweight, frequent write/read operations, and high response speed。
+
+- **OrderStatus - Query of latest orders**
+
+  Transaction content: For any one client, select a region and customers there from a specified repository randomly, read the last order, and display the status of each commodity in the order.
+
+  Main characteristics: middleweight, low read-only frequency, and high response speed
+
+- **Delivery - Delivery of packages**
+
+  Transaction content: For any one client, select a delivery package randomly, update the account balance of the user whose order is being processed, and delete the order from the new order list.
+
+  Main characteristics: 1 to 10 concurrent orders in a batch, low write/read frequency, and loose response time
+
+- **StockLevel - Analysis of stock status**
+
+  Transaction content: For any one client, select the last 20 orders from a specified repository of a region, check the stock of all commodities of the order list, and calculate and display the stock of all commodities with its stock level lower than the threshold generated randomly.
+
+  Main characteristics: heavyweight, low read-only frequency, and loose response time
+
+### Test Rules
+
+Before the test, TPC-C Benchmark specifies the initial status of a database, that is, the rule of data being generated in the database. The ITEM table includes a fixed number (100,000) of commodities. The number of warehouses can be adjusted. The initialized WAREHOUSE table includes 1000 records in this test.
+
+- The STOCK table contains 1000 x 100,000 records. (Each warehouse contains 100,000 commodities.)
+- The DISTRICT table contains 1000 x 10 records. (Each warehouse provides services for 10 regions.)
+- The CUSTOMER table contains 1000 x 10 x 3000 records. (There are 3000 customers in each region.)
+- The HISTORY table contains 1000 x 10 x 3000 records. (Each customer has one transaction history.)
+- The ORDER table contains 1000 x 10 x 3000 records (there are 3000 orders in each region). The last 900 orders generated are added to the NEW-ORDER table. Each order generates 5 to 15 ORDER-LINE records.
+
+> TPC-C uses tpmC to measure the maximum qualified throughput. The number of transactions depends on that of the new order transactions, that is, the number of new orders processed per minute.
diff --git a/product/en/docs-mogdb/v3.0/about-mogdb/test-report/performance/2-mogdb-on-kunpeng-performance-test-report.md b/product/en/docs-mogdb/v3.0/about-mogdb/test-report/performance/2-mogdb-on-kunpeng-performance-test-report.md
new file mode 100644
index 0000000000000000000000000000000000000000..2cbe9addd4623fa01565bade74c9e49170186f97
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/about-mogdb/test-report/performance/2-mogdb-on-kunpeng-performance-test-report.md
@@ -0,0 +1,401 @@
+---
+title: Performance Test for MogDB on a Kunpeng Server
+summary: Performance Test for MogDB on a Kunpeng Server
+author: Liu Xu
+date: 2021-03-04
+---
+
+# Performance Test for MogDB on Kunpeng Servers
+
+## Test Objective
+
+This document describes the test of MogDB 2.0.0 on Kunpeng servers in scenarios where MogDB is deployed on a single node, one primary node and one standby node, or one primary node and two standby nodes (one synchronous standby and one asynchronous standby).
+
+## Test Environment
+
+### Environment Configuration
+
+|  Category   |     Server Configuration     | Client Configuration | Quantity |
+| :---------: | :--------------------------: | :------------------: | :------: |
+|     CPU     |         Kunpeng 920          |     Kunpeng 920      |   128    |
+|   Memory    |        DDR4,2933MT/s         |    DDR4,2933MT/s     | 2048 GB  |
+|  Hard disk  |          Nvme 3.5T           |       Nvme 3T        |    4     |
+| File system |             Xfs              |         Xfs          |    4     |
+|     OS      |    openEuler 20.03 (LTS)     |      Kylin V10       |          |
+|  Database   | MogDB 1.1.0 software package |                      |          |
+
+### Test Tool
+
+|       Name       | Function                                                     |
+| :--------------: | :----------------------------------------------------------- |
+| BenchmarkSQL 5.0 | Open-source BenchmarkSQL developed based on Java is used for TPC-C test of OLTP database. It is used to evaluate the database transaction processing capability. |
+
+## Test Procedure
+
+### MogDB Database Operation
+
+1. Obtain the database installation package.
+
+2. Install the database.
+
+3. Create TPCC test user and database.
+
+   ```sql
+   create user [username] identified by ‘passwd’;
+   grant [origin user] to [username];
+   create database [dbname];
+   ```
+
+4. Disable the database and modify the **postgresql.conf** database configuration file by adding configuration parameters at the end of the file.
+
+   For example, add the following parameters in the single node test:
+
+   ```bash
+   max_connections = 4096
+
+   allow_concurrent_tuple_update = true
+
+   audit_enabled = off
+
+   checkpoint_segments = 1024
+
+   cstore_buffers =16MB
+
+   enable_alarm = off
+
+   enable_codegen = false
+
+   enable_data_replicate = off
+
+   full_page_writes  = off
+
+   max_files_per_process = 100000
+
+   max_prepared_transactions = 2048
+
+   shared_buffers = 350GB
+
+   use_workload_manager = off
+
+   wal_buffers = 1GB
+
+   work_mem = 1MB
+
+   log_min_messages  = FATAL
+
+   transaction_isolation = 'read committed'
+
+   default_transaction_isolation = 'read committed'
+
+   synchronous_commit = on
+
+   fsync  = on
+
+   maintenance_work_mem = 2GB
+
+   vacuum_cost_limit = 2000
+
+   autovacuum = on
+
+   autovacuum_mode = vacuum
+
+   autovacuum_max_workers = 5
+
+   autovacuum_naptime = 20s
+
+   autovacuum_vacuum_cost_delay =10
+
+   xloginsert_locks = 48
+
+   update_lockwait_timeout =20min
+
+   enable_mergejoin = off
+
+   enable_nestloop = off
+
+   enable_hashjoin = off
+
+   enable_bitmapscan = on
+
+   enable_material = off
+
+   wal_log_hints = off
+
+   log_duration = off
+
+   checkpoint_timeout = 15min
+
+   enable_save_datachanged_timestamp =FALSE
+
+   enable_thread_pool = on
+
+   thread_pool_attr =  '812,4,(cpubind:0-27,32-59,64-91,96-123)'
+
+   enable_double_write = on
+
+   enable_incremental_checkpoint = on
+
+   enable_opfusion = on
+
+   advance_xlog_file_num = 10
+
+   numa_distribute_mode = 'all'
+
+   track_activities = off
+
+   enable_instr_track_wait = off
+
+   enable_instr_rt_percentile = off
+
+   track_counts =on
+
+   track_sql_count = off
+
+   enable_instr_cpu_timer = off
+
+   plog_merge_age = 0
+
+   session_timeout = 0
+
+   enable_instance_metric_persistent = off
+
+   enable_logical_io_statistics = off
+
+   enable_user_metric_persistent =off
+
+   enable_xlog_prune = off
+
+   enable_resource_track = off
+
+   instr_unique_sql_count = 0
+
+   enable_beta_opfusion = on
+
+   enable_beta_nestloop_fusion = on
+
+   autovacuum_vacuum_scale_factor = 0.02
+
+   autovacuum_analyze_scale_factor = 0.1
+
+   client_encoding = UTF8
+
+   lc_messages = en_US.UTF-8
+
+   lc_monetary = en_US.UTF-8
+
+   lc_numeric = en_US.UTF-8
+
+   lc_time = en_US.UTF-8
+
+   modify_initial_password = off
+
+   ssl = off
+
+   enable_memory_limit = off
+
+   data_replicate_buffer_size = 16384
+
+   max_wal_senders = 8
+
+   log_line_prefix = '%m %u %d %h %p %S'
+
+   vacuum_cost_limit = 10000
+
+   max_process_memory = 12582912
+
+   recovery_max_workers = 1
+
+   recovery_parallelism = 1
+
+   explain_perf_mode = normal
+
+   remote_read_mode = non_authentication
+
+   enable_page_lsn_check = off
+
+   pagewriter_sleep = 100
+   ```
+
+### BenchmarkSQL Operation
+
+1. Modify the configuration file.
+
+   Open the BenchmarkSQL installation directory and find the **[config file]** configuration file in the **run** directory.
+
+   ```
+   db=postgres
+
+   driver=org.postgresql.Driver
+
+   conn=jdbc:postgresql://[ip:port]/tpcc?prepareThreshold=1&batchMode=on&fetchsize=10
+
+   user=[user]
+
+   password=[passwd]
+
+   warehouses=1000
+
+   loadWorkers=80
+
+   terminals=812
+
+   //To run specified transactions per terminal- runMins must equal zero
+
+   runTxnsPerTerminal=0
+
+   //To run for specified minutes- runTxnsPerTerminal must equal zero
+
+   runMins=30
+
+   //Number of total transactions per minute
+
+   limitTxnsPerMin=0
+
+   //Set to true to run in 4.x compatible mode. Set to false to use the
+
+   //entire configured database evenly.
+
+   terminalWarehouseFixed=false  #true
+
+   //The following five values must add up to 100
+
+   //The default percentages of 45, 43, 4, 4 & 4 match the TPC-C spec
+
+   newOrderWeight=45
+
+   paymentWeight=43
+
+   orderStatusWeight=4
+
+   deliveryWeight=4
+
+   stockLevelWeight=4
+
+   // Directory name to create for collecting detailed result data.
+
+   // Comment this out to suppress.
+
+   //resultDirectory=my_result_%tY-%tm-%td_%tH%tM%tS
+
+   //osCollectorScript=./misc/os_collector_linux.py
+
+   //osCollectorInterval=1
+
+   //osCollectorSSHAddr=tpcc@127.0.0.1
+
+   //osCollectorDevices=net_eth0 blk_sda blk_sdg blk_sdh blk_sdi blk_sdj
+   ```
+
+2. Run **runDataBuild.sh** to generate data.
+
+   ```
+   ./runDatabaseBuild.sh [config file]
+   ```
+
+3. Run **runBenchmark.sh** to test the database.
+
+   ```
+   ./runBenchmark.sh [config file]
+   ```
+
+### OS Configuration
+
+1. Modify **PAGESIZE** of the OS kernel (required only in EulerOS).
+
+    **Install kernel-4.19.36-1.aarch64.rpm (*).**
+
+   ```
+   # rpm -Uvh --force --nodeps kernel-4.19.36-1.aarch64.rpm
+
+   *: This file is based on the kernel package of linux 4.19.36. You can acquire it from the following directory:
+
+   10.44.133.121 (root/Huawei12#$)
+
+   /data14/xy_packages/kernel-4.19.36-1.aarch64.rpm
+   ```
+
+    **Modify the boot options of the root in the OS kernel configuration file.**
+
+   ```
+   \# vim /boot/efi/EFI/euleros/grubenv  //Back up the grubenv file before modification.
+
+   \# GRUB Environment Block
+
+   saved_entry=EulerOS (4.19.36) 2.0 (SP8)   -- Changed to 4.19.36
+   ```
+
+### File System
+
+1. Change the value of **blocksize** to **8K** in the XFS file system.
+
+   #Run the following commands to check the attached NVME disks:
+
+   ```
+   # df -h | grep nvme
+
+   /dev/nvme0n1         3.7T  2.6T  1.2T  69% /data1
+
+   /dev/nvme1n1         3.7T  1.9T  1.8T  51% /data2
+
+   /dev/nvme2n1         3.7T  2.2T  1.6T  59% /data3
+
+   /dev/nvme3n1         3.7T  1.4T  2.3T  39% /data4
+
+   Run the xfs_info command to query information about NVME disks.
+
+   \# xfs_info /data1
+   ```
+
+2. Back up the required data.
+
+3. Format the disk.
+
+   ```
+   Use the /dev/nvme0n1 disk and /data1 load point as an example and run the folowing commands:
+
+   umount /data1
+
+   mkfs.xfs -b size=8192 /dev/nvme0n1 -f
+
+   mount /dev/nvme0n1 /data1
+   ```
+
+## Test Items and Conclusions
+
+### Test Result Summary
+
+|               Test Item                | Data Volume | Concurrent Transactions | Average CPU Usage | IOPS   | IO Latency | Write Ahead Logs | tpmC       | Test Time (Minute) |
+| :------------------------------------: | ----------- | ----------------------- | ----------------- | ------ | ---------- | ---------------- | ---------- | :----------------: |
+|              Single node               | 100 GB      | 500                     | 77.49%            | 17.96K | 819.05 us  | 13260            | 1567226.12 |         10         |
+| One primary node and one standby node  | 100 GB      | 500                     | 57.64%            | 5.31K  | 842.78 us  | 13272            | 1130307.87 |         10         |
+| One primary node and two standby nodes | 100 GB      | 500                     | 60.77%            | 5.3K   | 821.66 us  | 14324            | 1201560.28 |         10         |
+
+### Single Node
+
+- tpmC
+
+  ![mogdb-on-kunpeng-1](https://cdn-mogdb.enmotech.com/docs-media/mogdb/about-mogdb/mogdb-on-kunpeng-1.png)
+
+- System data
+
+  ![mogdb-on-kunpeng-2](https://cdn-mogdb.enmotech.com/docs-media/mogdb/about-mogdb/mogdb-on-kunpeng-2.png)
+
+### One Primary Node and One Standby Node
+
+- tpmC
+
+  ![mogdb-on-kunpeng-3](https://cdn-mogdb.enmotech.com/docs-media/mogdb/about-mogdb/mogdb-on-kunpeng-3.png)
+
+- System data
+
+  ![mogdb-on-kunpeng-4](https://cdn-mogdb.enmotech.com/docs-media/mogdb/about-mogdb/mogdb-on-kunpeng-4.png)
+
+### One Primary Node and Two Standby Nodes
+
+- tpmC
+
+  ![mogdb-on-kunpeng-5](https://cdn-mogdb.enmotech.com/docs-media/mogdb/about-mogdb/mogdb-on-kunpeng-5.png)
+
+- System data
+
+  ![mogdb-on-kunpeng-6](https://cdn-mogdb.enmotech.com/docs-media/mogdb/about-mogdb/mogdb-on-kunpeng-6.png)
diff --git a/product/en/docs-mogdb/v3.0/about-mogdb/test-report/performance/3-mogdb-on-x86-performance-test-report.md b/product/en/docs-mogdb/v3.0/about-mogdb/test-report/performance/3-mogdb-on-x86-performance-test-report.md
new file mode 100644
index 0000000000000000000000000000000000000000..94644b1bd75005bd4887cf27cdc2002e79821993
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/about-mogdb/test-report/performance/3-mogdb-on-x86-performance-test-report.md
@@ -0,0 +1,654 @@
+---
+title: Performance Test for MogDB on x86 Servers
+summary: Performance Test for MogDB on x86 Servers
+author: Liu Xu
+date: 2021-03-04
+---
+
+# Performance Test for MogDB on x86 Servers
+
+## Test Objective
+
+This document describes the test of MogDB 2.0.0 on x86 servers in scenarios where MogDB is deployed on a single node, one primary node and one standby node, or one primary node and two standby nodes (one synchronous standby and one asynchronous standby).
+
+## Test Environment
+
+### Environment Configuration
+
+| Server Type |                Fit Server                |                NFS5280M5                 |
+| :---------: | :--------------------------------------: | :--------------------------------------: |
+|     CPU     | 144cIntel® Xeon(R) Gold 6240 CPU@2.60GHz | 64cIntel® Xeon(R) Gold 5218 CPU @2.30GHz |
+|   Memory    |                   768G                   |                   128G                   |
+|  Hard disk  |                 SAS SSD                  |                 SAS SSD                  |
+|     NIC     |                   10GE                   |                   10GE                   |
+
+### Test Tool
+
+| Name            | Function                                                     |
+| :-------------- | :----------------------------------------------------------- |
+| Benchmarksql5.0 | Open-source BenchmarkSQL developed based on Java is used for TPC-C test of OLTP database. It is used to evaluate the database transaction processing capability. |
+
+## Test Procedure
+
+### MogDB Database Operation
+
+1. Obtain the database installation package.
+
+2. Install the database.
+
+3. Create TPCC test user and database.
+
+   ```
+   create user [username] identified by ‘passwd’;
+   grant [origin user] to [username];
+   create database [dbname];
+   ```
+
+4. Disable the database and modify the **postgresql.conf** database configuration file by adding configuration parameters at the end of the file.
+
+   For example, add the following parameters in the single node test:
+
+   ```
+   max_connections = 4096
+
+   allow_concurrent_tuple_update = true
+
+   audit_enabled = off
+
+   checkpoint_segments = 1024
+
+   cstore_buffers =16MB
+
+   enable_alarm = off
+
+   enable_codegen = false
+
+   enable_data_replicate = off
+
+   full_page_writes  = off
+
+   max_files_per_process = 100000
+
+   max_prepared_transactions = 2048
+
+   shared_buffers = 350GB
+
+   use_workload_manager = off
+
+   wal_buffers = 1GB
+
+   work_mem = 1MB
+
+   log_min_messages  = FATAL
+
+   transaction_isolation = 'read committed'
+
+   default_transaction_isolation = 'read committed'
+
+   synchronous_commit = on
+
+   fsync  = on
+
+   maintenance_work_mem = 2GB
+
+   vacuum_cost_limit = 2000
+
+   autovacuum = on
+
+   autovacuum_mode = vacuum
+
+   autovacuum_max_workers = 5
+
+   autovacuum_naptime = 20s
+
+   autovacuum_vacuum_cost_delay =10
+
+   xloginsert_locks = 48
+
+   update_lockwait_timeout =20min
+
+   enable_mergejoin = off
+
+   enable_nestloop = off
+
+   enable_hashjoin = off
+
+   enable_bitmapscan = on
+
+   enable_material = off
+
+   wal_log_hints = off
+
+   log_duration = off
+
+   checkpoint_timeout = 15min
+
+   enable_save_datachanged_timestamp =FALSE
+
+   enable_thread_pool = on
+
+   thread_pool_attr =  '812,4,(cpubind:0-27,32-59,64-91,96-123)'
+
+   enable_double_write = on
+
+   enable_incremental_checkpoint = on
+
+   enable_opfusion = on
+
+   advance_xlog_file_num = 10
+
+   numa_distribute_mode = 'all'
+
+   track_activities = off
+
+   enable_instr_track_wait = off
+
+   enable_instr_rt_percentile = off
+
+   track_counts =on
+
+   track_sql_count = off
+
+   enable_instr_cpu_timer = off
+
+   plog_merge_age = 0
+
+   session_timeout = 0
+
+   enable_instance_metric_persistent = off
+
+   enable_logical_io_statistics = off
+
+   enable_user_metric_persistent =off
+
+   enable_xlog_prune = off
+
+   enable_resource_track = off
+
+   instr_unique_sql_count = 0
+
+   enable_beta_opfusion = on
+
+   enable_beta_nestloop_fusion = on
+
+   autovacuum_vacuum_scale_factor = 0.02
+
+   autovacuum_analyze_scale_factor = 0.1
+
+   client_encoding = UTF8
+
+   lc_messages = en_US.UTF-8
+
+   lc_monetary = en_US.UTF-8
+
+   lc_numeric = en_US.UTF-8
+
+   lc_time = en_US.UTF-8
+
+   modify_initial_password = off
+
+   ssl = off
+
+   enable_memory_limit = off
+
+   data_replicate_buffer_size = 16384
+
+   max_wal_senders = 8
+
+   log_line_prefix = '%m %u %d %h %p %S'
+
+   vacuum_cost_limit = 10000
+
+   max_process_memory = 12582912
+
+   recovery_max_workers = 1
+
+   recovery_parallelism = 1
+
+   explain_perf_mode = normal
+
+   remote_read_mode = non_authentication
+
+   enable_page_lsn_check = off
+
+   pagewriter_sleep = 100
+   ```
+
+### BenchmarkSQL Operation
+
+1. Modify the configuration file.
+
+   Open the BenchmarkSQL installation directory and find the **[config file]** configuration file in the **run** directory.
+
+   ```
+   db=postgres
+
+   driver=org.postgresql.Driver
+
+   conn=jdbc:postgresql://[ip:port]/tpcc?prepareThreshold=1&batchMode=on&fetchsize=10
+
+   user=[user]
+
+   password=[passwd]
+
+   warehouses=1000
+
+   loadWorkers=80
+
+   terminals=812
+
+   //To run specified transactions per terminal- runMins must equal zero
+
+   runTxnsPerTerminal=0
+
+   //To run for specified minutes- runTxnsPerTerminal must equal zero
+
+   runMins=30
+
+   //Number of total transactions per minute
+
+   limitTxnsPerMin=0
+
+   //Set to true to run in 4.x compatible mode. Set to false to use the
+
+   //entire configured database evenly.
+
+   terminalWarehouseFixed=false  #true
+
+   //The following five values must add up to 100
+
+   //The default percentages of 45, 43, 4, 4 & 4 match the TPC-C spec
+
+   newOrderWeight=45
+
+   paymentWeight=43
+
+   orderStatusWeight=4
+
+   deliveryWeight=4
+
+   stockLevelWeight=4
+
+   // Directory name to create for collecting detailed result data.
+
+   // Comment this out to suppress.
+
+   //resultDirectory=my_result_%tY-%tm-%td_%tH%tM%tS
+
+   //osCollectorScript=./misc/os_collector_linux.py
+
+   //osCollectorInterval=1
+
+   //osCollectorSSHAddr=tpcc@127.0.0.1
+
+   //osCollectorDevices=net_eth0 blk_sda blk_sdg blk_sdh blk_sdi blk_sdj
+   ```
+
+2. Run **runDataBuild.sh** to generate data.
+
+   ```
+   ./runDatabaseBuild.sh [config file]
+   ```
+
+3. Run **runBenchmark.sh** to test the database.
+
+   ```
+   ./runBenchmark.sh [config file]
+   ```
+
+### OS Parameters
+
+```
+vm.dirty_background_ratIO=5
+
+vm.dirty_ratIO=10
+
+kernel.sysrq=0
+
+net.ipv4.ip_forward=0
+
+net.ipv4.conf.all.send_redirects=0
+
+net.ipv4.conf.default.send_redirects=0
+
+net.ipv4.conf.all.accept_source_route=0
+
+net.ipv4.conf.default.accept_source_route=0
+
+net.ipv4.conf.all.accept_redirects=0
+
+net.ipv4.conf.default.accept_redirects=0
+
+net.ipv4.conf.all.secure_redirects=0
+
+net.ipv4.conf.default.secure_redirects=0
+
+net.ipv4.icmp_echo_ignore_broadcasts=1
+
+net.ipv4.icmp_ignore_bogus_error_responses=1
+
+net.ipv4.conf.all.rp_filter=1
+
+net.ipv4.conf.default.rp_filter=1
+
+net.ipv4.tcp_syncookies=1
+
+kernel.dmesg_restrict=1
+
+net.ipv6.conf.all.accept_redirects=0
+
+net.ipv6.conf.default.accept_redirects=0
+
+net.core.rmem_max = 21299200
+
+net.core.rmem_default = 21299200
+
+net.core.somaxconn = 65535
+
+net.ipv4.tcp_tw_reuse = 1
+
+net.sctp.sctp_mem = 94500000 915000000 927000000
+
+net.ipv4.tcp_max_tw_buckets = 10000
+
+net.ipv4.tcp_rmem = 8192 250000 16777216
+
+kernel.sem = 250 6400000 1000 25600
+
+net.core.wmem_default = 21299200
+
+kernel.shmall = 1152921504606846720
+
+net.core.wmem_max = 21299200
+
+net.sctp.sctp_rmem = 8192 250000 16777216
+
+net.core.netdev_max_backlog = 65535
+
+kernel.shmmax = 18446744073709551615
+
+net.sctp.sctp_wmem = 8192 250000 16777216
+
+net.ipv4.tcp_keepalive_intvl = 30
+
+net.ipv4.tcp_keepalive_time = 30
+
+net.ipv4.tcp_wmem = 8192 250000 16777216
+
+net.ipv4.tcp_max_syn_backlog = 65535
+
+vm.oom_panic_on_oom=0
+
+kernel.nmi_watchdog=0
+
+kernel.nmi_watchdog=0
+
+kernel.nmi_watchdog=0
+
+kernel.nmi_watchdog=0
+
+kernel.nmi_watchdog=0
+
+net.ipv4.tcp_timestamps = 1
+
+net.ipv4.tcp_tso_win_divisor = 30
+
+net.sctp.path_max_retrans = 10
+
+net.sctp.max_init_retransmits = 10
+
+net.ipv4.tcp_retries1 = 5
+
+net.ipv4.tcp_syn_retries = 5
+
+net.ipv4.tcp_synack_retries = 5
+
+kernel.core_uses_pid=1
+
+kernel.core_pattern=/home/core/core-%e-%u-%s-%t-%p
+
+kernel.nmi_watchdog=0
+
+kernel.nmi_watchdog=0
+
+kernel.nmi_watchdog=0
+
+kernel.nmi_watchdog=0
+
+kernel.core_pattern=/home/core/core-%e-%u-%s-%t-%h
+
+net.core.netdev_max_backlog = 65535
+
+net.core.rmem_default = 21299200
+
+net.core.rmem_max = 21299200
+
+net.core.somaxconn = 65535
+
+net.core.wmem_default = 21299200
+
+net.core.wmem_max = 21299200
+
+net.ipv4.conf.all.accept_redirects = 0
+
+net.ipv4.conf.all.rp_filter = 1
+
+net.ipv4.conf.all.secure_redirects = 0
+
+net.ipv4.conf.all.send_redirects = 0
+
+net.ipv4.conf.default.accept_redirects = 0
+
+net.ipv4.conf.default.accept_source_route = 0
+
+net.ipv4.conf.default.rp_filter = 1
+
+net.ipv4.conf.default.secure_redirects = 0
+
+net.ipv4.conf.default.send_redirects = 0
+
+net.ipv4.conf.enp135s0.accept_redirects = 0
+
+net.ipv4.conf.enp135s0.accept_source_route = 0
+
+net.ipv4.conf.enp135s0.forwarding = 1
+
+net.ipv4.conf.enp135s0.rp_filter = 1
+
+net.ipv4.conf.enp135s0.secure_redirects = 0
+
+net.ipv4.conf.enp135s0.send_redirects = 0
+
+net.ipv4.tcp_keepalive_intvl = 30
+
+net.ipv4.tcp_keepalive_time = 30
+
+net.ipv4.tcp_max_syn_backlog = 65535
+
+net.ipv4.tcp_max_tw_buckets = 10000
+
+net.ipv4.tcp_mem = 362715 483620 725430
+
+\#net.ipv4.tcp_mem = 94500000 915000000 927000000
+
+net.ipv4.tcp_retries1 = 5
+
+net.ipv4.tcp_rmem = 8192     250000  16777216
+
+net.ipv4.tcp_syn_retries = 5
+
+net.ipv4.tcp_tso_win_divisor = 30
+
+net.ipv4.tcp_tw_reuse = 1
+
+net.ipv4.tcp_wmem = 8192     250000  16777216
+
+net.ipv4.udp_mem = 725430    967240  1450860
+
+\#net.ipv4.tcp_max_orphans = 3276800
+
+\#net.ipv4.tcp_fin_timeout = 60
+
+\#net.ipv4.ip_local_port_range = 26000 65535
+
+net.ipv4.tcp_retries2 = 80
+
+\#net.ipv4.ip_local_reserved_ports = 20050-30007
+
+vm.min_free_kbytes = 40140150
+```
+
+### Database Parameters
+
+| Parameter                         | MogDB                                          |
+| :-------------------------------- | :--------------------------------------------- |
+| listen_addresses                  | Specific IP address                            |
+| port                              | 26000                                          |
+| max_connectIOns                   | 4096                                           |
+| wal_level                         | hot_standby                                    |
+| archive_mode                      | on                                             |
+| archive_command                   | /bin/ture                                      |
+| max_wal_senders                   | 16                                             |
+| wal_keep_segments                 | 16                                             |
+| max_replicatIOn_slots             | 8                                              |
+| hot_standby                       | on                                             |
+| logging_collector                 | on                                             |
+| log_directory                     | Specify the directory of the installation tool |
+| log_filename                      | PostgreSQL-%Y-%m-%d_%H%M%S.log                 |
+| log_min_duratIOn_statement        | 1800000                                        |
+| log_line_prefix                   | %m%c%d%p%a%x%n%e                               |
+| log_timezone                      | PRC                                            |
+| datestyle                         | iso,mdy                                        |
+| timezone                          | PRC                                            |
+| default_text_search_config        | pg_catalog.english                             |
+| applicatIOn_name                  | dn_6001                                        |
+| max_prepared_transactIOns         | 2048                                           |
+| shared_buffers                    | 350 GB                                         |
+| wal_buffers                       | 1 GB                                           |
+| work_mem                          | 64 MB                                          |
+| log_min_messages                  | FATAL                                          |
+| synchronous_commit                | on                                             |
+| fsync                             | on                                             |
+| maintenance_work_mem              | 2 GB                                           |
+| autovacuum                        | on                                             |
+| autovacuum_max_workers            | 5                                              |
+| autovacuum_naptime                | 20s                                            |
+| autovacuum_vacuum_cost_delay      | 10                                             |
+| enable_mergejoin                  | off                                            |
+| enable_nestloop                   | off                                            |
+| enable_hashjoin                   | off                                            |
+| enable_bitmapscan                 | on                                             |
+| enable_material                   | off                                            |
+| wal_log_hints                     | off                                            |
+| log_duratIOn                      | off                                            |
+| checkpoint_timeout                | 15 min                                         |
+| track_activities                  | off                                            |
+| track_counts                      | on                                             |
+| autovacuum_vacuum_scale_factor    | 0.02                                           |
+| autovacuum_analyze_scale_factor   | 0.1                                            |
+| ssl                               | off                                            |
+| local_bind_address                | Specific IP address                            |
+| max_inner_tool_connectIOns        | 10                                             |
+| password_encryptIOn_type          | 0                                              |
+| comm_tcp_mode                     | on                                             |
+| comm_quota_size                   | 1024 KB                                        |
+| max_process_memory                | 700 GB                                         |
+| bulk_write_ring_size              | 2 GB                                           |
+| checkpoint_segments               | 1024                                           |
+| incremental_checkpoint_timeout    | 60s                                            |
+| archive_dest                      | /log/archive                                   |
+| enable_slot_log                   | off                                            |
+| data_replicate_buffer_size        | 128 MB                                         |
+| walsender_max_send_size           | 8 MB                                           |
+| enable_kill_query                 | off                                            |
+| connectIOn_alARM_rate             | 0.9                                            |
+| alARM_report_interval             | 10                                             |
+| alARM_component                   | /opt/huawei/snas/bin/snas_cm_cmd               |
+| lockwait_timeout                  | 1200s                                          |
+| pgxc_node_name                    | xxx                                            |
+| audit_directory                   | Specify the directory of the installation tool |
+| explain_perf_mode                 | pretty                                         |
+| job_queue_processes               | 10                                             |
+| default_storage_nodegroup         | installatIOn                                   |
+| expected_computing_nodegroup      | query                                          |
+| replicatIOn_type                  | 1                                              |
+| recovery_max_workers              | 4                                              |
+| available_zone                    | AZ1                                            |
+| allow_concurrent_tuple_update     | TRUE                                           |
+| audit_enabled                     | off                                            |
+| cstore_buffers                    | 16 MB                                          |
+| enable_alARM                      | off                                            |
+| enable_codegen                    | FALSE                                          |
+| enable_data_replicate             | off                                            |
+| max_file_per_process              | 10000                                          |
+| use_workload_manager              | off                                            |
+| xloginsert_locks                  | 48                                             |
+| update_lockwait_timeout           | 20 min                                         |
+| enable_save_datachanged_timestamp | FALSE                                          |
+| enable_thread_pool                | off                                            |
+| enable_double_write               | on                                             |
+| enable_incremental_checkpoint     | on                                             |
+| advance_xlog_file_num             | 10                                             |
+| enable_instr_track_wait           | off                                            |
+| enable_instr_rt_percentile        | off                                            |
+| track_sql_count                   | off                                            |
+| enable_instr_cpu_timer            | off                                            |
+| plog_merge_age                    | 0                                              |
+| sessIOn_timeout                   | 0                                              |
+| enable_instance_metric_persistent | off                                            |
+| enable_logical_IO_statistics      | off                                            |
+| enable_user_metric_persistent     | off                                            |
+| enable_xlog_prune                 | off                                            |
+| enable_resource_track             | off                                            |
+| instr_unique_sql_count            | 0                                              |
+| enable_beta_opfusIOn              | on                                             |
+| enable_bete_netsloop_fusIOn       | on                                             |
+| remote_read_mode                  | non_authenticatIOn                             |
+| enable_page_lsn_check             | off                                            |
+| pagewriter_sleep                  | 2s                                             |
+| enable_opfusIOn                   | on                                             |
+| max_redo_log_size                 | 100 GB                                         |
+| pagewrite_thread_num              | 1                                              |
+| bgwrite_thread_num                | 1                                              |
+| dirty_page_percent_max            | 1                                              |
+| candidate_buf_percent_target      | 01                                             |
+
+## Test Items and Conclusions
+
+### Test Result Summary
+
+| Test Item                              | Data Volume | Concurrent Transactions | Average CPU Usage | IOPS  | IO Latency | Write Ahead Logs | tpmC     | Test Time (Minute) |
+| -------------------------------------- | ----------- | ----------------------- | ----------------- | ----- | ---------- | ---------------- | -------- | ------------------ |
+| Single node                            | 100 GB      | 500                     | 29.39%            | 6.50K | 1.94 ms    | 3974             | 520896.3 | 10                 |
+| One primary node and one standby node  | 100 GB      | 500                     | 30.4%             | 5.31K | 453.2 us   | 3944             | 519993.5 | 10                 |
+| One primary node and two standby nodes | 100 GB      | 500                     | 26.35%            | 7.66K | 531.9 us   | 3535             | 480842.2 | 10                 |
+
+### Single Node
+
+- tpmC
+
+  ![mogdb-on-x86-1](https://cdn-mogdb.enmotech.com/docs-media/mogdb/about-mogdb/mogdb-on-x86-1.png)
+
+  System data
+
+  ![mogdb-on-x86-2](https://cdn-mogdb.enmotech.com/docs-media/mogdb/about-mogdb/mogdb-on-x86-2.png)
+
+### One Primary Node and One Standby Node
+
+- tpmC
+
+  ![mogdb-on-x86-3](https://cdn-mogdb.enmotech.com/docs-media/mogdb/about-mogdb/mogdb-on-x86-3.png)
+
+- System data
+
+  ![mogdb-on-x86-4](https://cdn-mogdb.enmotech.com/docs-media/mogdb/about-mogdb/mogdb-on-x86-4.png)
+
+### One Primary Node and Two Standby Nodes
+
+- tpmC
+
+  ![mogdb-on-x86-5](https://cdn-mogdb.enmotech.com/docs-media/mogdb/about-mogdb/mogdb-on-x86-5.png)
+
+- System data
+
+  ![mogdb-on-x86-6](https://cdn-mogdb.enmotech.com/docs-media/mogdb/about-mogdb/mogdb-on-x86-6.png)
diff --git a/product/en/docs-mogdb/v3.0/about-mogdb/usage-limitations.md b/product/en/docs-mogdb/v3.0/about-mogdb/usage-limitations.md
new file mode 100644
index 0000000000000000000000000000000000000000..84ea10ed57bb6548e1b19f1771cb49b4a0213799
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/about-mogdb/usage-limitations.md
@@ -0,0 +1,27 @@
+---
+title: Usage Limitations
+summary: Usage Limitations
+author: Guo Huan
+date: 2021-06-01
+---
+
+# Usage Limitations
+
+This document describes the common usage limitations of MogDB.
+
+| Item                                      | Upper limit                                          |
+| ----------------------------------------- | ---------------------------------------------------- |
+| Database capacity                         | Depend on operating systems and hardware             |
+| Size of a single table                    | 32 TB                                                |
+| Size of a single row                      | 1 GB                                                 |
+| Size of a single field in a row           | 1 GB                                                 |
+| Number of rows in a single table          | 281474976710656 (2^48^)                              |
+| Number of columns in a single table       | 250~1600 (Varies depending on different field types) |
+| Number of indexes in a single table       | Unlimited                                            |
+| Number of columns in a compound index     | 32                                                   |
+| Number of constraints in a single table   | Unlimited                                            |
+| Number of concurrent connections          | 10000                                                |
+| Number of partitions in a partition table | 32768 (Range partition)/64 (HASH/List partition)     |
+| Size of a single partition                | 32 TB                                                |
+| Number of rows in a single partition      | 2^55^                                                |
+| Maximum length of SQL text                | 1048576 bytes (1MB)                                  |
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/br/1-1-br.md b/product/en/docs-mogdb/v3.0/administrator-guide/br/1-1-br.md
new file mode 100644
index 0000000000000000000000000000000000000000..0ecfdd3338cdd205b6c54c05f6c4c83fb5bc6ef1
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/br/1-1-br.md
@@ -0,0 +1,93 @@
+---
+title: Overview
+summary: Overview
+author: Guo Huan
+date: 2021-04-27
+---
+
+# Overview
+
+For database security purposes, MogDB provides three backup types, multiple backup and restoration solutions, and data reliability assurance mechanisms.
+
+Backup and restoration can be classified into logical backup and restoration, physical backup and restoration, and flashback.
+
+- Logical backup and restoration: backs up data by logically exporting data. This method can dump data that is backed up at a certain time point, and restore data only to this backup point. A logical backup does not back up data processed between failure occurrence and the last backup. It applies to scenarios where data rarely changes. Such data damaged due to misoperation can be quickly restored using a logical backup. To restore all the data in a database through logical backup, rebuild a database and import the backup data. Logical backup is not recommended for databases requiring high data availability because it takes a long time for data restoration. Logical backup is a major approach to migrate and transfer data because it can be performed on any platform.
+
+- Physical backup and restoration: copies physical files in the unit of disk blocks from the primary node to the standby node to back up a database. A database can be restored using backup files, such as data files and archive log files. Physical backup is usually used for full backup, quickly backing up and restoring data at a low cost if properly planned.
+
+- Flashback: This function is used to restore dropped tables from the recycle bin. Like in a Window OS, dropped table information is stored in the recycle bin of databases. The MVCC mechanism is used to restore data to a specified point in time or change sequence number (CSN).
+
+  The three data backup and restoration solutions supported by MogDB are as follows. Methods for restoring data in case of an exception differ for different backup and restoration solutions.
+
+  **Table 1** Comparison of three backup and restoration types
+
+  <table>
+    <tr>
+        <td><b>Backup Type</b></td>
+        <td><b>Application Scenario</b></td>
+        <td><b>Media</b></td>
+        <td><b>Tool Name</b></td>
+        <td><b>Recovery Time</b></td>
+        <td><b>Advantage and Disadvantage</b></td>
+    </tr>
+      <tr>
+        <td rowspan="2">Logical backup and restoration</td>
+          <td rowspan="2">Small volume of data needs to be processed.<br/>You can back up a single table, multiple tables, a single database, or all databases. The backup data needs to be restored using gsql or gs_restore. When the data volume is large, the restoration takes a long time.</td>
+          <td rowspan="6"> - Disk <br/>- SSD</td>
+          <td>gs_dump</td>
+           <td>It takes a long time to restore data in plain-text format. It takes a long time to restore data in archive format.</td>
+          <td>This tool is used to export database information. Users can export a database or its objects (such as schemas, tables, and views). The database can be the default postgres database or a user-specified database. The exported file can be in plain-text format or archive format. Data in plain-text format can be restored only by using gsql, which takes a long time. Data in archive format can be restored only by using gs_restore. The restoration time is shorter than that of the plain-text format.</td>
+    </tr>
+    <tr>
+    <td>gs_dumpall</td>
+           <td>Long data recovery time</td>
+          <td>This tool is used to export all information of the openGauss database, including the data of the default postgres database, data of user-specified databases, and global objects of all openGauss databases.<br/>Only data in plain-text format can be exported. The exported data can be restored only by using gsql, which takes a long time.</td>
+    </tr>
+      <tr>
+        <td rowspan="3">Physical backup and restoration</td>
+          <td rowspan="3">Huge volume of data needs to be processed. It is mainly used for full backup and restoration as well as the backup of all WAL archive and run logs in the database.</td>
+        <td>gs_backup</td>
+        <td>Small data volume and fast data recovery</td>
+        <td>The OM tool for exporting database information can be used to export database parameter files and binary files. It helps the openGauss to back up and restore important data, and display help and version information. During the backup, you can select the type of the backup content. During the restoration, ensure that the backup file exists in the backup directory of each node. During cluster restoration, the cluster information in the static configuration file is used for restoration. It takes a short time to restore only parameter files.</td>
+      </tr>
+      <tr>
+       <td>gs_basebackup</td>
+        <td>During the restoration, you can directly copy and replace the original files, or directly start the database on the backup database. The restoration takes a short time.</td>
+        <td>This too is used to fully copy the binary files of the server database. Only the database at a certain time point can be backed up. With PITR, you can restore data to a time point after the full backup time point.</td>
+        </tr>
+         <tr>
+       <td>gs_probackup</td>
+        <td>Data can be directly restored to a backup point and the database can be started on the backup database. The restoration takes a short time.</td>
+        <td>gs_probackup is a tool used to manage openGauss database backup and restoration. It periodically backs up openGauss instances. It supports the physical backup of a standalone database or a primary database node in a cluster. It supports the backup of contents in external directories, such as script files, configuration files, log files, and dump files. It supports incremental backup, periodic backup, and remote backup. The time required for incremental backup is shorter than that for full backup. You only need to back up the modified files. Currently, the data directory is backed up by default. If the tablespace is not in the data directory, you need to manually specify the tablespace directory to be backed up. Currently, data can be backed up only on the primary node.</td>
+  </tr>
+          <tr>
+          <td>Flashback</td>
+          <td>Applicable to:<br/>1) A table is deleted by mistake.<br/>2) Data in the tables needs to be restored to a specified time point or CSN.</td>
+          <td>None</td>
+          <td>You can restore a table to the status at a specified time point or before the table structure is deleted within a short period of time.</td>
+          <td>Flashback can selectively and efficiently undo the impact of a committed transaction and recover from a human error. Before the flashback technology is used, the committed database modification can be retrieved only by means of restoring backup or PITR. The restoration takes several minutes or even hours. After the flashback technology is used, it takes only seconds to restore the committed data before the database is modified. The restoration time is irrelevant to the database size.<br/>Flashback supports two recovery modes:<br/>- Multi-version data restoration based on MVCC: applicable to the query and restoration of data that is deleted, updated, or inserted by mistake. You can configure the retention period of the old version and run the corresponding query or restoration command to query or restore data to a specified time point or CSN.<br/>- Recovery based on the recycle bin (similar to that on Windows OS): This method is applicable to the recovery of tables that are dropped or truncated by mistake. You can configure the recycle bin switch and run the corresponding restoration command to restore the tables that are dropped or truncated by mistake.</td>
+      </tr>
+  </table>
+
+While backing up and restoring data, take the following aspects into consideration:
+
+- Whether the impact of data backup on services is acceptable
+
+- Database restoration efficiency
+
+  To minimize the impact of database faults, try to minimize the restoration duration, achieving the highest restoration efficiency.
+
+- Data restorability
+
+  Minimize data loss after the database is invalidated.
+
+- Database restoration cost
+
+  There are many factors that need to be considered while you select a backup policy on the live network, such as backup objects, data volume, and network configuration. Table 2 lists available backup policies and applicable scenarios for each backup policy.
+
+  **Table 2** Backup policies and scenarios
+
+  | Backup Policy            | Key Performance Factor                                       | Typical Data Volume                                        | Performance Specifications                                   |
+  | :----------------------- | :----------------------------------------------------------- | :--------------------------------------------------------- | :----------------------------------------------------------- |
+  | Database instance backup | - Data amount<br/>- Network configuration                    | Data volume: PB level<br/>Object quantity: about 1 million | Backup:<br/>- Data transfer rate on each host: 80 Mbit/s (NBU/EISOO+Disk)<br/>- Disk I/O rate (SSD/HDD): about 90% |
+  | Table backup             | - Schema where the table to be backed up resides<br/>- Network configuration (NBU) | Data volume: 10 TB level                                   | Backup: depends on query performance rate and I/O rate<br/>NOTE:<br/>For multi-table backup, the backup time is calculated as follows:<br/>`Total time = Number of tables x Starting time + Total data volume/Data backup speed`<br/>In the preceding information:<br/>- The starting time of a disk is about 5s. The starting time of an NBU is longer than that of a disk (depending on the NBU deployment).<br/>- The data backup speed is about 50 MB/s on a single node. (The speed is evaluated based on the backup of a 1 GB table from a physical host to a local disk.)<br/>The smaller the table is, the lower the backup performance will be. |
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/br/1-2-br.md b/product/en/docs-mogdb/v3.0/administrator-guide/br/1-2-br.md
new file mode 100644
index 0000000000000000000000000000000000000000..ed50d65f3e6af5df3fe7d7f467a7d5096aef46e6
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/br/1-2-br.md
@@ -0,0 +1,904 @@
+---
+title: Physical Backup and Restoration
+summary: Physical Backup and Restoration
+author: Guo Huan
+date: 2021-04-27
+---
+
+# Physical Backup and Restoration
+
+## gs_basebackup
+
+### Background
+
+After MogDB is deployed, problems and exceptions may occur during database running. **gs_basebackup**, provided by MogDB, is used to perform basic physical backup. **gs_basebackup** copies the binary files of the database on the server using a replication protocol. To remotely execute **gs_basebackup**, you need to use the system administrator account. **gs_basebackup** supports hot backup and compressed backup.
+
+**NOTE:**
+
+- **gs_basebackup** supports only full backup.
+- **gs_basebackup** supports hot backup and compressed backup.
+- **gs_basebackup** cannot back up tablespaces containing absolute paths on the same server. This is because the absolute path is unique on the same machine, and brings about conflicts. However, it can back up tablespaces containing absolute paths on different machines.
+- If the functions of incremental checkpoint and dual-write are enabled, **gs_basebackup** also backs up dual-write files.
+- If the **pg_xlog** directory is a soft link, no soft link is created during backup. Data is directly backed up to the **pg_xlog** directory in the destination path.
+- If the backup permission is revoked during the backup, the backup may fail or the backup data may be unavailable.
+- MogDB does not support version upgrade.
+
+### Prerequisites
+
+- The MogDB database can be connected.
+- User permissions are not revoked during the backup.
+- In the **pg_hba.conf** file, the replication connection is allowed and the connection is established by a system administrator.
+- If the Xlog transmission mode is **stream**, the number of **max_wal_senders** must be configured to at least one.
+- If the Xlog transmission mode is **fetch**, the **wal_keep_segments** parameter must be set to a large value so that logs are not removed before the backup ends.
+- During the restoration, backup files exist in the backup directory on all the nodes. If backup files are lost on any node, them to it from another node.
+
+### Syntax
+
+- Display help information.
+
+  ```
+  gs_basebackup -? | --help
+  ```
+
+- Display version information.
+
+  ```
+  gs_basebackup -V | --version
+  ```
+
+### Parameter Description
+
+The **gs_basebackup** tool can use the following types of parameters:
+
+- -D directory
+
+Directory for storing backup files. This parameter is mandatory.
+
+- Common parameters
+
+  - -c, -checkpoint=fast|spread
+
+  Sets the checkpoint mode to **fast** or **spread** (default).
+
+  - -l, -label=LABEL
+
+  Adds tags for the backup.
+
+  - -P, -progress
+
+  Enables the progress report.
+
+  - -v, -verbose
+
+  Enables the verbose mode.
+
+  - -V, -version
+
+  Prints the version and exits.
+
+  - -?, -help
+
+  Displays **gs_basebackup** command parameters.
+
+  - -T, -tablespace-mapping=olddir=newdir
+
+  During the backup, the tablespace in the **olddir** directory is relocated to the **newdir** directory. For this to take effect, **olddir** must exactly match the path where the tablespace is located (but it is not an error if the backup does not contain the tablespaces in **olddir**). **olddir** and **newdir** must be absolute paths. If a path happens to contain an equal sign (=), you can escape it with a backslash (). This option can be used multiple times for multiple tablespaces.
+
+  - -F, -format=plain|tar
+
+  Sets the output format to **plain** (default) or **tar**. If this parameter is not set, the default value **-format=plain** is used. The plain format writes the output as a flat file, using the same layout as the current data directory and tablespace. When the cluster has no extra tablespace, the entire database is placed in the target directory. If the cluster contains additional tablespaces, the primary data directory will be placed in the target directory, but all other tablespaces will be placed in the same absolute path on the server. The tar mode writes the output as a tar file in the target directory. The primary data directory is written to a file named **base.tar**, and other tablespaces are named after their OIDs. The generated .tar package must be decompressed using the **gs_tar** command.
+
+  - -X, -xlog-method=fetch|stream
+
+  Sets the Xlog transmission mode. If this parameter is not set, the default value **-xlog-method=stream** is used. The required write-ahead log files (WALs) are included in the backup. This includes all WALs generated during the backup. In fetch mode, WAL files are collected at the end of the backup. Therefore, the **wal_keep_segments** parameter must be set to a large value so that logs are not removed before the backup ends. If it has been rotated when the log is to be transmitted, the backup fails and is unavailable. In stream mode, WALs are streamed when a backup is created. This will open a second connection to the server and start streaming WALs while the backup is running. Therefore, it will use up to two connections configured by the **max_wal_senders** parameter. As long as the client can receive WALs, no additional WALs need to be stored on the host.
+
+  - -x, -xlog
+
+  Equivalent to using **-X** with the fetch method.
+
+  - -Z -compress=level
+
+  Enables gzip compression for the output of the tar file and sets the compression level (0 to 9, where 0 indicates no compression and 9 indicates the best compression). The compression is available only when the tar format is used. The suffix .gz is automatically added to the end of all .tar file names.
+
+  - -z
+
+  Enables gzip compression for tar file output and uses the default compression level. The compression is available only when the tar format is used. The suffix .gz is automatically added to the end of all .tar file names.
+
+  - -t, -rw-timeout
+
+  Sets the checkpoint time limit during backup. The default value is 120s. If the full checkpoint of the database is time-consuming, you can increase the value of **rw-timeout**.
+
+- Connection parameters
+
+  - -h, -host=HOSTNAME
+
+  Specifies the host name of the machine on which the server is running or the directory for the Unix-domain socket.
+
+  - -p, -port=PORT
+
+  Specifies the port number of the database server.
+
+  You can modify the default port number using this parameter.
+
+  - -U, -username=USERNAME
+
+  Specifies the user that connects to the database.
+
+  - -s, -status-interval=INTERVAL
+
+  Specifies the time for sending status packets to the server, in seconds.
+
+  - -w,-no-password
+
+  Never issues a password prompt.
+
+  - -W, -password
+
+  Issues a password prompt when the **-U** parameter is used to connect to a local or remote database.
+
+### Example
+
+```bash
+gs_basebackup -D /home/test/trunk/install/data/backup -h 127.0.0.1 -p 21233
+INFO:  The starting position of the xlog of the full build is: 0/1B800000. The slot minimum LSN is: 0/1B800000.
+```
+
+### Restoring Data from Backup Files
+
+If a database is faulty, restore it from backup files. **gs_basebackup** backs up the database in binary mode. Therefore, you can directly and replace the original files or start the database on the backup database.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+
+- If the current database instance is running, a port conflict may occur when you start the database from the backup file. In this case, you need to modify the port parameter in the configuration file or specify a port when starting the database.
+- If the current backup file is a primary/standby database, you may need to modify the replication connections between the master and slave databases. That is, **replconninfo1** and **replconninfo2** in the **postgresql.conf** file.
+
+To restore the original database, perform the following steps:
+
+1. Stop the database server. For details, see *Administrator Guide*.
+2. the original database and all tablespaces to another location for future use.
+3. Delete all or part of the files from the original database.
+4. Use the database system user rights to restore the required database files from the backup.
+5. If a link file exists in the database, modify the link file so that it can be linked to the correct file.
+6. Restart the database server and check the database content to ensure that the database is restored to the required status.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+
+- Incremental restoration from backup files is not supported.
+- After the restoration, check that the link file in the database is linked to the correct file.
+
+## gs_probackup
+
+### Background
+
+**gs_probackup** is a tool used to manage MogDB database backup and restoration. It periodically backs up the MogDB instances so that the server can be restored when the database is faulty.
+
+- It supports the physical backup of a standalone database or a primary node in a database.
+- It supports the backup of contents in external directories, such as script files, configuration files, log files, and dump files.
+- It supports incremental backup, periodic backup, and remote backup.
+- It supports settings on the backup retention policy.
+
+### Prerequisites
+
+- The MogDB database can be connected.
+- To use PTRACK incremental backup, manually add **enable_cbm_tracking = on** to **postgresql.conf**.
+
+### Important Notes
+
+- The backup must be performed by the user who runs the database server.
+- The major version number of the database server to be backed up must be the same as that of the database server to be restored.
+- To back up a database in remote mode using SSH, install the database of the same major version on the local and remote hosts, and run the **ssh-copy-id remote_user@remote_host** command to set an SSH connection without a password between the local host backup user and the remote host database user.
+- In remote mode, only the subcommands **add-instance**, **backup**, and **restore** can be executed.
+- Before running the **restore** subcommand, stop the mogdb process.
+- When there is a user-defined tablespace, the **--external-dirs** parameter should be added when backing up, otherwise, the tablespace will not be backed up.
+- When the scale of the backup is relatively large, in order to prevent timeout from occurring during the backup process, please adjust the parameters **session_timeout**, **wal_sender_timeout** of the **postgres.conf** file appropriately. And adjust the value of the parameter **--rw-timeout** appropriately in the command line parameters of the backup.
+- When restoring, when using the **-T** option to redirect the external directory in the backup to a new directory, please specify the parameter **--external-mapping** at the same time.
+- After the incremental backup is restored, the previously created logical replication slot is unavailable and needs to be deleted and rebuilt.
+
+### Command Description
+
+- Print the **gs_probackup** version.
+
+  ```bash
+  gs_probackup -V|--version
+  gs_probackup version
+  ```
+
+- Display brief information about the **gs_probackup** command. Alternatively, display details about parameters of a specified subcommand of **gs_probackup**.
+
+  ```bash
+  gs_probackup -?|--help
+  gs_probackup help [command]
+  ```
+
+- Initialize the backup directory in **backup-path**. The backup directory stores the contents that have been backed up. If the **backup-path** backup path exists, it must be empty.
+
+  ```bash
+  gs_probackup init -B backup-path [--help]
+  ```
+
+- Initialize a new backup instance in the backup directory of **backup-path** and generate the **pg_probackup.conf** configuration file, which saves the **gs_probackup**settings of the specified data directory **pgdata-path**.
+
+  ```bash
+  gs_probackup add-instance -B backup-path -D pgdata-path --instance=instance_name
+  [-E external-directories-paths]
+  [remote_options]
+  [--help]
+  ```
+
+- Delete the backup content related to the specified instance from the **backup-path** directory.
+
+  ```bash
+  gs_probackup del-instance -B backup-path --instance=instance_name
+  [--help]
+  ```
+
+- Add the specified connection, compression, and log-related settings to the **pg_probackup.conf** configuration file or modify the existing settings. You are not advised to manually edit the **pg_probackup.conf** configuration file.
+
+  ```bash
+  gs_probackup set-config -B backup-path --instance=instance_name
+  [-D pgdata-path] [-E external-directories-paths] [--archive-timeout=timeout]
+  [--retention-redundancy=retention-redundancy] [--retention-window=retention-window] [--wal-depth=wal-depth]
+  [--compress-algorithm=compress-algorithm] [--compress-level=compress-level]
+  [-d dbname] [-h hostname] [-p port] [-U username]
+  [logging_options] [remote_options]
+  [--help]
+  ```
+
+- Add the backup-related settings to the **backup.control** configuration file or modify the settings.
+
+  ```bash
+  gs_probackup set-backup -B backup-path --instance=instance_name -i backup-id
+  [--note=text] [pinning_options]
+  [--help]
+  ```
+
+- Display the content of the **pg_probackup.conf** configuration file in the backup directory. You can specify **-format=json** to display the information in JSON format. By default, the plain text format is used.
+
+  ```bash
+  gs_probackup show-config -B backup-path --instance=instance_name
+  [--format=plain|json]
+  [--help]
+  ```
+
+- Display the contents of the backup directory. If **instance_name** and **backup_id** are specified, detailed information about the backup is displayed. You can specify **-format=json** to display the information in JSON format. By default, the plain text format is used.
+
+  ```bash
+  gs_probackup show -B backup-path
+  [--instance=instance_name [-i backup-id]] [--archive] [--format=plain|json]
+  [--help]
+  ```
+
+- Create a backup for a specified database instance.
+
+  ```bash
+  gs_probackup backup -B backup-path --instance=instance_name -b backup-mode
+  [-D pgdata-path] [-C] [-S slot-name] [--temp-slot] [--backup-pg-log] [-j threads_num] [--progress]
+  [--no-validate] [--skip-block-validation] [-E external-directories-paths] [--no-sync] [--note=text]
+  [--archive-timeout=timeout] [-t rwtimeout]
+  [logging_options] [retention_options] [compression_options]
+  [connection_options] [remote_options] [pinning_options]
+  [--help]
+  ```
+
+- Restore a specified instance from the backup copy in the **backup-path** directory. If an instance to be restored is specified, **gs_probackup** will look for its latest backup and restore it to the specified recovery target. Otherwise, the latest backup of any instance is used.
+
+  ```bash
+  gs_probackup restore -B backup-path --instance=instance_name
+  [-D pgdata-path] [-i backup_id] [-j threads_num] [--progress] [--force] [--no-sync] [--no-validate] [--skip-block-validation]
+  [--external-mapping=OLDDIR=NEWDIR] [-T OLDDIR=NEWDIR] [--skip-external-dirs] [-I incremental_mode]
+  [recovery_options] [remote_options] [logging_options]
+  [--help]
+  ```
+
+- Merge all incremental backups between the specified incremental backup and its parent full backup into the parent full backup. The parent full backup will receive all merged data, while the merged incremental backup will be deleted as redundancy.
+
+  ```bash
+  gs_probackup merge -B backup-path --instance=instance_name -i backup_id
+  [-j threads_num] [--progress] [logging_options]
+  [--help]
+  ```
+
+- Delete a specified backup or delete backups that do not meet the current retention policy.
+
+  ```bash
+  gs_probackup delete -B backup-path --instance=instance_name
+  [-i backup-id | --delete-expired | --merge-expired | --status=backup_status]
+  [--delete-wal] [-j threads_num] [--progress]
+  [--retention-redundancy=retention-redundancy] [--retention-window=retention-window]
+  [--wal-depth=wal-depth] [--dry-run]
+  [logging_options]
+  [--help]
+  ```
+
+- Verify that all files required for restoring the database exist and are not damaged. If **instance_name**is not specified, **gs_probackup**verifies all available backups in the backup directory. If **instance_name**is specified and no additional options are specified, **gs_probackup**verifies all available backups for this backup instance. If both **instance_name** and **backup-id**or recovery objective-related options are specified, **gs_probackup**checks whether these options can be used to restore the database.
+
+  ```bash
+  gs_probackup validate -B backup-path
+  [--instance=instance_name] [-i backup-id]
+  [-j threads_num] [--progress] [--skip-block-validation]
+  [--recovery-target-time=time | --recovery-target-xid=xid | --recovery-target-lsn=lsn | --recovery-target-name=target-name]
+  [--recovery-target-inclusive=boolean]
+  [logging_options]
+  [--help]
+  ```
+
+### Parameter Description
+
+**Common parameters**
+
+- command
+
+  Specifies subcommands except **version** and **help**: **init**, **add-instance**, **del-instance**, **set-config**, **set-backup**, **show-config**, **show**, **backup**, **restore**, **merge**, **delete**, and **validate**.
+
+- -?, -help
+
+  Displays help information about the command line parameters of **gs_probackup** and exits.
+
+  Only **-help** can be used in subcommands; **-?** is forbidden.
+
+- -V, -version
+
+  Prints the **gs_probackup** version and exits.
+
+- -B *backup-path*, -backup-path=*backup-path*
+
+  Backup path.
+
+  System environment variable: *$BACKUP_PATH*
+
+- -D *pgdata-path*, -pgdata=*pgdata-path*
+
+  Path of the data directory.
+
+  System environment variable: *$PGDATA*
+
+- -instance=*instance_name*
+
+  Instance name.
+
+- -i *backup-id*, -backup-id=*backup-id*
+
+  Unique identifier of a backup.
+
+- -format=*format*
+
+  Specifies format of the backup information to be displayed. The plain and JSON formats are supported.
+
+  Default value: **plain**
+
+- -status=*backup_status*
+
+  Deletes all backups in a specified state. The states are as follows:
+
+  - **OK**: Backup is complete and valid.
+
+  - **DONE**: Backup has been completed but not verified.
+  - **RUNNING**: Backup is in progress.
+  - **MERGING**: Backups are being merged.
+  - **DELETING**: Backup is being deleted.
+  - **CORRUPT**: Some backup files are damaged.
+  - **ERROR**: Backup fails due to an unexpected error.
+  - **ORPHAN**: Backup is invalid because one of its parent backups is corrupted or lost.
+  - -j *threads_num*, -threads=*threads_num*
+
+  Sets the number of concurrent threads for the backup, restoration, and combination processes.
+
+- -archive
+
+  Displays WAL archiving information.
+
+- -progress
+
+  Displays progress.
+
+- -note=*text*
+
+  Adds a note to the backup.
+
+**Backup-related parameters**
+
+- -b *backup-mode*, -backup-mode=*backup-mode*
+
+  Specifies the backup mode. The value can be **FULL** or **PTRACK**.
+
+  **FULL**: creates a full backup. The full backup contains all data files.
+
+  **PTRACK**: creates a PTRACK incremental backup.
+
+- -C, -smooth-checkpoint
+
+  Expands checkpoints within a period of time. By default, **gs_probackup** attempts to complete checkpoints as soon as possible.
+
+- -S *slot-name*, -slot=*slot-name*
+
+  Specifies the replication slot for WAL stream processing.
+
+- -temp-slot
+
+  Creates a temporary physical replication slot for WAL stream processing in the backup instance to ensure that all required WAL segments are still available during the backup.
+
+  The default slot name is **pg_probackup_slot**, which can be changed using the **-slot/-S** option.
+
+- -backup-pg-log
+
+  Includes the log directory in the backup. This directory typically contains log messages. By default, the log directory is included, but log files are not included. If the default log path is changed, you can use the  **-E**  parameter to back up log files. The following describes how to use the  **-E**  parameter.
+
+- -E *external-directories-paths*, -external-dirs=*external-directories-paths*
+
+  Includes the specified directory in the backup. This option is useful for backing up scripts in external data directories, sql dumps, and configuration files. To back up multiple external directories, use colons (:) to separate their paths in Unix.
+
+  Example: -E /tmp/dir1:/tmp/dir2
+
+- -skip-block-validation
+
+  Disables block-level verification to speed up backup.
+
+- -no-validate
+
+  Skips the automatic verification when the backup is complete.
+
+- -no-sync
+
+  Disables backup file synchronization to the disk.
+
+- -archive-timeout=*timeout*
+
+  Specifies timeout interval for streaming processing, in seconds.
+
+  Default value: **300**
+
+- -t rwtimeout
+
+  Specifies timeout interval for a connection, in seconds.
+
+  Default value: **120**
+
+**Restoration-related parameters**
+
+- -I, -incremental-mode=none|checksum|lsn
+
+  Reuses the valid pages available in PGDATA if they are not modified.
+
+  Default value: **none**
+
+- -external-mapping=*OLDDIR=NEWDIR*
+
+  During restoration, the external directory contained in the backup is moved from **OLDDIR** to **NEWDIR**. **OLDDIR** and **NEWDIR** must be absolute paths. If the path contains an equal sign (=), use a backslash () to escape. This option can be specified for multiple directories.
+
+- -T *OLDDIR=NEWDIR*, -tablespace-mapping=*OLDDIR=NEWDIR*
+
+  Relocates the tablespace from the **OLDDIR** directory to the **NEWDIR** directory during the restoration. **OLDDIR** and **NEWDIR** must be absolute paths. If the path contains an equal sign (=), use a backslash () to escape. This parameter can be specified multiple times for multiple tablespaces. This parameter must be used together with **-external-mapping**.
+
+- -skip-external-dirs
+
+  Skips the external directories in the backup that are specified using the **-external-dirs** option. The contents of these directories will not be restored.
+
+- -skip-block-validation
+
+  Skips block-level verification to speed up verification. During the automatic verification before the restoration, only file-level verification is performed.
+
+- -no-validate
+
+  Skips the backup verification.
+
+- -force
+
+  Specifies the invalid state that allows ignoring backup. This flag can be used if data needs to be restored from a damaged or invalid backup. Exercise caution when using it.
+
+**Recovery objective-related parameters (recovery_options)**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** Currently, continuous WAL archiving PITR cannot be configured. Therefore, parameter usage is restricted as follows: To use continuously archived WAL logs for PITR, perform the following steps:
+>
+> 1. Replace the target database directory with the physical backup files.
+> 2. Delete all files in the database directory **pg_xlog/**.
+> 3. Copy the archived WAL log file to the **pg_xlog** file. (Or you can configure **restore_command** in the **recovery.conf** file to skip this step.)
+> 4. Create the recovery command file **recovery.conf** in the database directory and specify the database recovery degree.
+> 5. Start the database.
+> 6. Connect to the database and check whether the database is recovered to the expected status. If the expected status is reached, run the **pg_xlog_replay_resume()** command so that the primary node can provide services externally.
+
+- -recovery-target-lsn=*lsn*
+
+  Specifies LSN to be restored. Currently, only the backup stop LSN can be specified.
+
+- -recovery-target-name=*target-name*
+
+  Specifies named savepoint to which data is restored. You can obtain the savepoint by viewing the recovery-name column in the backup.
+
+- -recovery-target-time=*time*
+
+  Specifies time to which data is restored. Currently, only recovery-time can be specified.
+
+- -recovery-target-xid=*xid*
+
+  Specifies transaction ID to which data is restored. Currently, only recovery-xid can be specified.
+
+- -recovery-target-inclusive=*boolean*
+
+  When this parameter is set to **true**, the recovery target will include the specified content.
+
+  When this parameter is set to **false**, the recovery target will not include the specified content.
+
+  This parameter must be used together with **-recovery-target-name**, **-recovery-target-time**, **-recovery-target-lsn**, or **-recovery-target-xid**.
+
+**Retention-related parameters (retention_options)**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The following parameters can be used together with the **backup** and **delete** commands.
+
+- -retention-redundancy=*retention-redundancy*
+
+  Number of full backups retained in the data directory. The value must be a positive integer. The value **0** indicates that the setting is disabled.
+
+  Default value: **0**
+
+- -retention-window=*retention-window*
+
+  Specifies the retention period. The value must be a positive integer. The value **0** indicates that the setting is disabled.
+
+  Default value: **0**
+
+- -wal-depth=*wal-depth*
+
+  Latest number of valid backups that must be retained on each timeline to perform the PITR capability. The value must be a positive integer. The value **0** indicates that the setting is disabled.
+
+  Default value: **0**
+
+- -delete-wal
+
+  Deletes unnecessary WAL files from any existing backup.
+
+- -delete-expired
+
+  Deletes the backups that do not comply with the retention policy defined in the **pg_probackup.conf** configuration file.
+
+- -merge-expired
+
+  Merges the oldest incremental backup that meets the retention policy requirements with its expired parent backup.
+
+- -dry-run
+
+  Displays the status of all available backups. Expired backups will not be deleted or merged.
+
+**Fixed backup-related parameters (pinning_options)**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** To exclude certain backups from the established retention policy, you can use the following parameters with the **backup** and **set-backup** commands.
+
+- -ttl=interval
+
+  Specifies a fixed amount of time to back up data from the restoration time. The value must be a positive integer. The value **0** indicates that the backup is canceled.
+
+  Supported unit: ms, s, min, h, d (default value: **s**)
+
+  For example, **-ttl=30d**.
+
+- -expire-time=time
+
+  Specifies the timestamp when the backup is invalid. The time stamp must comply with the ISO-8601 standard.
+
+  For example, **-expire-time='2020-01-01 00:00:00+03'**.
+
+**Log-related parameters (logging_options)**
+
+Log levels: **verbose**, **log**, **info**, **warning**, **error**, and **off**.
+
+- -log-level-console=log-level-console
+
+  Sets the level of logs to be sent to the console. Each level contains all the levels following it. A higher level indicates fewer messages sent. If this parameter is set to **off**, the log recording function of the console is disabled.
+
+  Default value: **info**
+
+- -log-level-file=log-level-file
+
+  Sets the level of logs to be sent to the log file. Each level contains all the levels following it. A higher level indicates fewer messages sent. If this parameter is set to **off**, the log file recording function is disabled.
+
+  Default value: **off**
+
+- -log-filename=log-filename
+
+  Specifies the name of the log file to be created. The file name can use the strftime mode. Therefore, **%-escapes** can be used to specify the file name that changes with time.
+
+  For example, if the **pg_probackup-%u.log** mode is specified, pg_probackup generates a log file each day of the week, with **%u** replaced by the corresponding decimal number, that is, **pg_probackup-1.log**indicates Monday.**pg_probackup-2.log** indicates Tuesday, and so on.
+
+  This parameter is valid if the **-log-level-file** parameter is specified to enable log file recording.
+
+  Default value: **"pg_probackup.log"**
+
+- -error-log-filename=error-log-filename
+
+  Specifies the name of the log file that is used only for error logs. The specifying method is the same as that of the **-log-filename** parameter.
+
+  It is used for troubleshooting and monitoring.
+
+- -log-directory=log-directory
+
+  Specifies the directory where log files are created. The value must be an absolute path. This directory is created when the first log is written.
+
+  Default value: **$BACKUP_PATH/log**
+
+- -log-rotation-size=log-rotation-size
+
+  Specifies the maximum size of a log file. If the maximum size is reached, the log file will be circulated after the **gs_probackup** command is executed. The **help** and **version** commands will not lead to a log file circulation. The value **0** indicates that the file size-based loop is disabled.
+
+  The unit can be KB, MB, GB, or TB. The default unit is **KB**.
+
+  Default value: **0**
+
+- -log-rotation-age=log-rotation-age
+
+  Maximum life cycle of a log file. If the maximum size is reached, the log file will be circulated after the **gs_probackup** command is executed. The **help** and **version** commands will not lead to a log file circulation. The **$BACKUP_PATH/log/log_rotation** directory saves the time of the last created log file. The value **0** indicates that the time-based loop is disabled.
+
+  Supported unit: ms, s, min, h, d (default value: **min**)
+
+  Default value: **0**
+
+**Connection-related parameters (connection_options)**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The following parameters can be used together with the **backup** command.
+
+- -d *dbname*, -pgdatabase=dbname
+
+  Specifies the name of the database to connect to. This connection is only used to manage the backup process. Therefore, you can connect to any existing database. If this parameter is not specified in the command line, the *PGDATABASE* environment variable, or the **pg_probackup.conf** configuration file, **gs_probackup** attempts to obtain the value from the *PGUSER* environment variable. If the *PGUSER* variable is not set, the value is obtained from the current user name.
+
+  System environment variable: $PGDATABASE
+
+- -h *hostname*, -pghost=hostname
+
+  Specifies the host name of the system on which the server is running. If the value begins with a slash (/), it is used as the directory for the UNIX domain socket.
+
+  System environment variable: $PGHOST
+
+  Default value: **local socket**
+
+- -p *port*, -pgport=_p_*ort*
+
+  Specifies the TCP port or local Unix domain socket file name extension on which the server is listening for connections.
+
+  System environment variable: $PGPORT
+
+  Default value: **5432**
+
+- -U *username*, -pguser=username
+
+  Specifies the username of the host to be connected.
+
+  System environment variable: $PGUSER
+
+- -w, -no-password
+
+  Never issues a password prompt. The connection attempt fails if the host requires password verification and the password is not provided in other ways. This parameter is useful in batch jobs and the scripts that require no user password.
+
+- -W *password*, -password=password
+
+  User password for database connection. If the host uses the trust authentication policy, the administrator does not need to enter the **-W** parameter. If the **-W** parameter is not provided and you are not a system administrator, the system will ask you to enter a password.
+
+**Compression-related parameters (compression_options)**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif)**NOTE:** The following parameters can be used together with the **backup** command.
+
+- -compress-algorithm=compress-algorithm
+
+  Specifies the algorithm used to compress data file.
+
+  The value can be **zlib**, **pglz**, or **none**. If **zlib** or **pglz** is set, compression is enabled. By default, the compression function is disabled.
+
+  Default value: **none**
+
+- -compress-level=compress-level
+
+  Specifies the compression level. Value range: 0-9
+
+  - **0** indicates no compression.
+  - **1** indicates that the compression ratio is the lowest and processing speed the fastest.
+  - **9** indicates that the compression ratio is the highest and processing speed the slowest.
+  - This parameter can be used together with **-compress-algorithm**.
+
+  Default value: **1**
+
+- -compress
+
+  Compresses with **-compress-algorithm=zlib** and **-compress-level=1**.
+
+**Remote mode-related parameters (remote_options)**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif)**NOTE:** The following are parameters that remotely run **gs_probackup** through SSH, and can be used together with the **add-instance**, **set-config**, **backup**, and **restore** commands.
+
+- -remote-proto=protocol
+
+  Specifies the protocol used for remote operations. Currently, only the SSH protocol is supported. Valid value:
+
+  **ssh**: enables the remote backup mode through SSH. This is the default.
+
+  **none**: The remote mode is disabled explicitly.
+
+  If **-remote-host** is specified, this parameter can be omitted.
+
+- -remote-host=destination
+
+  Specifies the IP address or host name of the remote host to be connected.
+
+- -remote-port=port
+
+  Specifies the port number of the remote host to be connected.
+
+  Default value: **22**
+
+- -remote-user=*username*
+
+  Specifies the remote host user for SSH connection. If this parameter is not specified, the user who initiates the SSH connection is used.
+
+  Default value: the current user.
+
+- -remote-path=path
+
+  Specifies the installation directory of **gs_probackup** in the remote system.
+
+  Default value: current path
+
+  - --remote-lib=_libpath_
+
+    Specifies the lib directory installed by **gs_probackup** in the remote system.
+
+- -ssh-options=*ssh_options*
+
+  Specifies the character string of the SSH command line parameter.
+
+  Example: -ssh-options='-c cipher_spec -F configfile'
+
+>**NOTE:**
+>
+>* If the server does not respond due to a temporary network fault,  **gs_probackup**will exit after waiting for **archive-timeout** seconds (300 seconds is set by default).
+>* If the LSN of the standby server is different from that of the primary server, the database continuously updates the following log information. In this case, you need to rebuild the standby server.
+>
+>```bash
+>LOG: walsender thread shut down
+>LOG: walsender thread started
+>LOG: received wal replication command: IDENTIFY_VERSION
+>LOG: received wal replication command: IDENTIFY_MODE
+>LOG: received wal replication command: IDENTIFY_SYSTEM
+>LOG: received wal replication command: IDENTIFY_CONSISTENCE 0/D0002D8
+>LOG: remote request lsn/crc: [xxxxx] local max lsn/crc: [xxxxx]
+>```
+
+### Backup Process
+
+1. Initialize the backup directory. Create the  **backups/**  and  **wal/**  subdirectories in the specified directory to store backup files and WAL files respectively.
+
+   ```bash
+   gs_probackup init -B backup_dir
+   ```
+
+2. Add a new backup instance. **gs_probackup** can store backups of multiple database instances in the same backup directory.
+
+   ```bash
+   gs_probackup add-instance -B backup_dir -D data_dir -instance instance_name
+   ```
+
+3. Create a backup for a specified database instance. Before performing an incremental backup, you must create at least one full backup.
+
+   ```bash
+   gs_probackup backup -B backup_dir -instance instance_name -b backup_mode
+   ```
+
+4. Restore data from the backup of a specified instance.
+
+   ```bash
+   gs_probackup restore -B backup_dir -instance instance_name -D pgdata-path -i backup_id
+   ```
+
+### Troubleshooting
+
+| Problem Description                                          | Cause and Solution                                           |
+| :----------------------------------------------------------- | :----------------------------------------------------------- |
+| ERROR: query failed: ERROR: canceling statement due to conflict with recovery<br /> | Cause: The operation performed on the standby node is accessing the storage row. The corresponding row is modified or deleted on the primary node, and the Xlog is replayed on the standby node. As a result, the operation is canceled on the standby node.<br />Solution: <br />1. Increase the values of the following parameters: <br />max_standby_archive_delaymax_standby_streaming_delay<br />2. Add the following configuration item:<br />hot_standby_feedback = on |
+
+## PITR Recovery
+
+### Background
+
+When a database breaks down or needs to be rolled back to a previous state, the point-in-time recovery (PITR) function of MogDB can be used to restore the database to any point in time after the backup and archive data is generated.
+
+**NOTE:**
+
+- PITR can only be restored to a point in time after the physical backup data is generated.
+- Only the primary node can be restored using PITR. The standby node needs to be fully built to synchronize data with the primary node.
+
+### Prerequisites
+
+- Full data files have been physically backed up.
+- WAL log files have been archived.
+
+### PITR Recovery Process
+
+1. Replace the target database directory with the physical backup files.
+2. Delete all files in the database directory **pg_xlog/**.
+3. the archived WAL log file to the **pg_xlog** file. (Or you can configure **restore_command** in the **recovery.conf** file to skip this step.)
+4. Create the recovery command file **recovery.conf** in the database directory and specify the database recovery degree.
+5. Start the database.
+6. Connect to the database and check whether the database is recovered to the expected status.
+7. If the expected status is reached, run the **pg_xlog_replay_resume()** command so that the primary node can provide services externally.
+
+### Configuring the recovery.conf File
+
+**Archive Recovery Configuration**
+
+- restore_command = string
+
+  The **shell** command is used to obtain the archived WAL files among the WAL file series. Any %f in the string is replaced by the name of the file to retrieve from the archive, and any %p is replaced by the path name to it to on the server. Any %r is replaced by the name of the file containing the last valid restart point.
+
+  For example:
+
+  ```bash
+  restore_command = 'cp /mnt/server/archivedir/%f %p'
+  ```
+
+- archive_cleanup_command = string
+
+  This option parameter declares a **shell** command that is executed each time the system is restarted. **archive_cleanup_command** provides a mechanism for deleting unnecessary archived WAL files from the standby database. Any %r is replaced by the name of the file containing the last valid restart point. That is the earliest file that must be kept to allow recovery to be restartable, so all files older than %r can be safely removed.
+
+  For example:
+
+  ```bash
+  archive_cleanup_command = 'pg_archivecleanup /mnt/server/archivedir %r'
+  ```
+
+  If multiple standby servers need to be recovered from the same archive path, ensure that WAL files are not deleted from any standby server before the recovery.
+
+- recovery_end_command = string
+
+  This parameter is optional and is used to declare a **shell** command that is executed only when the recovery is complete. **recovery_end_command** provides a cleanup mechanism for future replication and recovery.
+
+**Recovery Object Configuration**
+
+- recovery_target_name = string
+
+  This parameter declares that the name is recovered to a recovery point created using pg_create_restore_point().
+
+  For example:
+
+  ```bash
+  recovery_target_name = 'restore_point_1'
+  ```
+
+- recovery_target_time = timestamp
+
+  This parameter declares that the name is recovered to a specified timestamp.
+
+  For example:
+
+  ```bash
+  recovery_target_time = '2020-01-01 12:00:00'
+  ```
+
+- recovery_target_xid = string
+
+  This parameter declares that the name is recovered to a transaction ID.
+
+  For example:
+
+  ```bash
+  recovery_target_xid = '3000'
+  ```
+
+- recovery_target_lsn = string
+
+  This parameter declares that the name is recovered to the LSN specified by log.
+
+  For example:
+
+  ```bash
+  recovery_target_lsn = '0/0FFFFFF'
+  ```
+
+- recovery_target_inclusive = boolean
+
+  This parameter declares whether to stop the recovery after the recovery target is specified (**true**) or before the recovery target is specified (**false**). This declaration supports only the recovery targets **recovery_target_time**, **recovery_target_xid**, and **recovery_target_lsn**.
+
+  For example:
+
+  ```bash
+  recovery_target_inclusive = true
+  ```
+
+**NOTE:**
+
+- Only one of the four configuration items **recovery_target_name**, **recovery_target_time**, **recovery_target_xid**, and **recovery_target_lsn** can be used at a time.
+- If no recovery targets are configured or the configured target does not exist, data is recovered to the latest WAL log point by default.
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/br/1-3-br.md b/product/en/docs-mogdb/v3.0/administrator-guide/br/1-3-br.md
new file mode 100644
index 0000000000000000000000000000000000000000..6803a980f248053a6f03c6dd4d698cdc98434e30
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/br/1-3-br.md
@@ -0,0 +1,1311 @@
+---
+title: Logical Backup and Restoration
+summary: Logical Backup and Restoration
+author: Guo Huan
+date: 2021-04-27
+---
+
+# Logical Backup and Restoration
+
+## gs_dump
+
+### Background
+
+gs_dump, provided by MogDB, is used to export database information. You can export a database or its objects (such as schemas, tables, and views). The database can be the default mogdb database or a user-specified database.
+
+**gs_dump** is executed by OS user **omm**.
+
+When **gs_dump** is used to export data, other users can still access (read and write) MogDB databases.
+
+**gs_dump** can export complete, consistent data. For example, if **gs_dump** is started to export database A at T1, data of the database at that time point will be exported, and modifications on the database after that time point will not be exported.
+
+**gs_dump** can export database information to a plain-text SQL script file or archive file.
+
+- Plain-text SQL script: It contains the SQL statements required to restore the database. You can use gsql to execute the SQL script. With only a little modification, the SQL script can rebuild a database on other hosts or database products.
+- Archive file: It contains data required to restore the database. It can be a tar-, directory-, or custom-format archive. For details, see Table 1. The export result must be used with **gs_restore**to restore the database. The system allows users to select or even to sort the content to be imported.
+
+### Functions
+
+**gs_dump** can create export files in four formats, which are specified by **-F** or **-format=**, as listed in Table 1.
+
+**Table 1** Formats of exported files
+
+<table>
+    <tr>
+        <th>Format</th>
+        <th>Value of -F</th>
+        <th>Description</th>
+        <th>Suggestion</th>
+        <th>Corresponding Import Tool</th>
+    </tr>
+    <tr>
+        <td>Plain-text</td>
+        <td>p</td>
+        <td>A plain-text script file containing SQL statements and commands. The commands can be executed on gsql, a command line terminal, to recreate database objects and load table data.</td>
+        <td>You are advised to use plain-text exported files for small databases.</td>
+        <td>Before using gsql to restore database objects, you can use a text editor to edit the plain-text export file as required.</td>
+    </tr>
+    <tr>
+        <td>Custom</td>
+        <td>c</td>
+        <td>A binary file that allows the restoration of all or selected database objects from an exported file.</td>
+        <td>You are advised to use custom-format archive files for medium or large database.</td>
+        <td rowspan="3">You can use gs_restore to import database objects from a custom-format archive.</td>
+    </tr>
+    <tr>
+        <td>Directory</td>
+        <td>d</td>
+        <td>A directory containing directory files and the data files of tables and BLOB objects.</td>
+        <td>-</td>
+    </tr>
+    <tr>
+        <td>.tar</td>
+        <td>t</td>
+        <td>A tar-format archive that allows the restoration of all or selected database objects from an exported file. It cannot be further compressed and has an 8-GB limitation on the size of a single table.</td>
+        <td>-</td>
+    </tr>
+</table>
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+To reduce the size of an exported file, you can use **gs_dump** to compress it to a plain-text file or custom-format file. By default, a plain-text file is not compressed when generated. When a custom-format archive is generated, a medium level of compression is applied by default. Archived exported files cannot be compressed using **gs_dump**. When a plain-text file is exported in compressed mode, **gsql** fails to import data objects.
+
+### Precautions
+
+Do not modify an exported file or its content. Otherwise, restoration may fail.
+
+To ensure the data consistency and integrity, **gs_dump** acquires a share lock on a table to be dumped. If another transaction has acquired a share lock on the table, **gs_dump** waits until this lock is released and then locks the table for dumping. If the table cannot be locked within the specified time, the dump fails. You can customize the timeout duration to wait for lock release by specifying the **-lock-wait-timeout** parameter.
+
+### Syntax
+
+```bash
+gs_dump [OPTION]... [DBNAME]
+```
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+**DBNAME** does not follow a short or long option. It specifies the database to be connected.
+For example:
+Specify **DBNAME** without a **-d** option preceding it.
+
+```bash
+gs_dump -p port_number  mogdb -f dump1.sql
+```
+
+or
+
+```
+export PGDATABASE=mogdb
+gs_dump -p port_number -f dump1.sql
+```
+
+Environment variable:**PGDATABASE**
+
+### Parameter Description
+
+Common parameters
+
+- -f, -file=FILENAME
+
+  Sends the output to the specified file or directory. If this parameter is omitted, the standard output is generated. If the output format is **(-F c/-F d/-F t)**, the **-f** parameter must be specified. If the value of the **-f** parameter contains a directory, the current user must have the read and write permissions on the directory, and the directory cannot be an existing one.
+
+- -F, -format=c|d|t|p
+
+    Selects the exported file format. The format can be:
+
+  - **p|plain**: Generates a text SQL script file. This is the default value.
+
+  - **c|custom**: Outputs a custom-format archive as a directory to be used as the input of **gs_restore**. This is the most flexible output format in which users can manually select it and reorder the archived items during restoration. An archive in this format is compressed by default.
+
+  - **d|directory**: Creates a directory containing directory files and the data files of tables and BLOBs.
+
+  - **t|tar**: Outputs a .tar archive as the input of **gs_restore**. The .tar format is compatible with the directory format. Extracting a .tar archive generates a valid directory-format archive. However, the .tar archive cannot be further compressed and has an 8-GB limitation on the size of a single table. The order of table data items cannot be changed during restoration.
+
+    A .tar archive can be used as input of **gsql**.
+
+- -v, -verbose
+
+  Specifies the verbose mode. If it is specified, **gs_dump** writes detailed object comments and the number of startups/stops to the dump file, and progress messages to standard error.
+
+- -V, -version
+
+  Prints the **gs_dump** version and exits.
+
+- -Z, -compress=0-9
+
+    Specifies the used compression level.
+
+    Value range: 0-9
+
+  - **0** indicates no compression.
+  - **1** indicates that the compression ratio is the lowest and processing speed the fastest.
+  - **9** indicates that the compression ratio is the highest and processing speed the slowest.
+
+    For the custom-format archive, this option specifies the compression level of a single table data segment. By default, data is compressed at a medium level. The plain-text and .tar archive formats do not support compression currently.
+
+- -lock-wait-timeout=TIMEOUT
+
+  Do not keep waiting to obtain shared table locks since the beginning of the dump. Consider it as failed if you are unable to lock a table within the specified time. The timeout period can be specified in any of the formats accepted by **SET statement_timeout**.
+
+- -?, -help
+
+  Displays help about **gs_dump** parameters and exits.
+
+Dump parameters:
+
+- -a, -data-only
+
+  Generates only the data, not the schema (data definition). Dump the table data, big objects, and sequence values.
+
+- -b, -blobs
+
+  Specifies a reserved port for function expansion. This parameter is not recommended.
+
+- -c, -clean
+
+  Before writing the command of creating database objects into the backup file, writes the command of clearing (deleting) database objects to the backup files. (If no objects exist in the target database, **gs_restore** probably displays some error information.)
+
+  This parameter is used only for the plain-text format. For the archive format, you can specify the option when using **gs_restore**.
+
+- -C, -create
+
+  The backup file content starts with the commands of creating the database and connecting to the created database. (If the command script is executed in this mode, you can specify any database to run the command for creating a database. The data is restored to the created database instead of the specified database.)
+
+  This parameter is used only for the plain-text format. For the archive format, you can specify the option when using **gs_restore**.
+
+- -E, -encoding=ENCODING
+
+  Creates a dump file in the specified character set encoding. By default, the dump file is created in the database encoding. (Alternatively, you can set the environment variable **PGCLIENTENCODING** to the required dump encoding.)
+
+- -n, -schema=SCHEMA
+
+    Dumps only schemas matching the schema names. This option contains the schema and all its contained objects. If this option is not specified, all non-system schemas in the target database will be dumped. Multiple schemas can be selected by specifying multiple **-n** options. The schema parameter is interpreted as a pattern according to the same rules used by the **\d** command of **gsql**. Therefore, multiple schemas can also be selected by writing wildcard characters in the pattern. When you use wildcard characters, quote the pattern to prevent the shell from expanding the wildcard characters.
+
+    ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+
+  - If **-n** is specified, **gs_dump** does not dump any other database objects which the selected schemas might depend upon. Therefore, there is no guarantee that the results of a specific-schema dump can be automatically restored to an empty database.
+  - If **-n** is specified, the non-schema objects are not dumped.
+
+    Multiple schemas can be dumped. Entering **-n schemaname** multiple times dumps multiple schemas.
+
+    For example:
+
+    ```bash
+    gs_dump -h host_name -p port_number mogdb -f backup/bkp_shl2.sql -n sch1 -n sch2
+    ```
+
+  In the preceding example, **sch1** and **sch2** are dumped.
+
+- -N, -exclude-schema=SCHEMA
+
+  Does not dump any schemas matching the schemas pattern. The pattern is interpreted according to the same rules as for **-n**. **-N** can be specified multiple times to exclude schemas matching any of the specified patterns.
+
+  When both **-n** and **-N** are specified, the schemas that match at least one **-n** option but no **-N** is dumped. If **-N** is specified and **-n** is not, the schemas matching **-N** are excluded from what is normally dumped.
+
+  Dump allows you to exclude multiple schemas during dumping.
+
+  Specify **-N exclude schema name** to exclude multiple schemas during dumping.
+
+  For example:
+
+  ```bash
+  gs_dump -h host_name -p port_number mogdb -f backup/bkp_shl2.sql -N sch1 -N sch2
+  ```
+
+  In the preceding example, **sch1** and **sch2** will be excluded during the dumping.
+
+- -o, -oids
+
+  Dumps object identifiers (OIDs) as parts of the data in each table. Use this option if your application references the OID columns in some way. If the preceding situation does not occur, do not use this parameter.
+
+- -O, -no-owner
+
+  Do not output commands to set ownership of objects to match the original database. By default, **gs_dump** issues the **ALTER OWNER** or **SET SESSION AUTHORIZATION** statement to set ownership of created database objects. These statements will fail when the script is running unless it is started by a system administrator (or the same user that owns all of the objects in the script). To make a script that can be stored by any user and give the user ownership of all objects, specify **-O**.
+
+  This parameter is used only for the plain-text format. For the archive format, you can specify the option when using **gs_restore**.
+
+- -s, -schema-only
+
+  Dumps only the object definition (schema) but not data.
+
+- -S, -sysadmin=NAME
+
+  Specifies a reserved port for function expansion. This parameter is not recommended.
+
+- -t, -table=TABLE
+
+    Specifies a list of tables, views, sequences, or foreign tables to be dumped. You can use multiple **-t** parameters or wildcard characters to specify tables.
+
+    When you use wildcard characters, quote patterns to prevent the shell from expanding the wildcard characters.
+
+    The **-n** and **-N** options have no effect when **-t** is used, because tables selected by using **-t** will be dumped regardless of those options.
+
+    ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+
+  - The number of **-t** parameters must be less than or equal to 100.
+  - If the number of **-t** parameters is greater than 100, you are advised to use the **-include-table-file** parameter to replace some **-t** parameters.
+  - If **-t** is specified, **gs_dump** does not dump any other database objects which the selected tables might depend upon. Therefore, there is no guarantee that the results of a specific-table dump can be automatically restored to an empty database.
+  - **-t tablename** only dumps visible tables in the default search path. **-t '\*.tablename'** dumps *tablename* tables in all the schemas of the dumped database. **-t schema.table** dumps tables in a specific schema.
+  - **-t tablename** does not export trigger information from a table.
+
+    For example:
+
+    ```bash
+    gs_dump -h host_name -p port_number mogdb -f backup/bkp_shl2.sql -t schema1.table1 -t schema2.table2
+    ```
+
+  In the preceding example, **schema1.table1** and **schema2.table2** are dumped.
+
+- -include-table-file=FILENAME
+
+  Specifies the table file to be dumped.
+
+- -T, -exclude-table=TABLE
+
+  Specifies a list of tables, views, sequences, or foreign tables not to be dumped. You can use multiple **-T** parameters or wildcard characters to specify tables.
+
+  When **-t** and **-T** are input, the object will be stored in **-t** list not **-T** table object.
+
+  For example:
+
+  ```bash
+  gs_dump -h host_name -p port_number mogdb -f backup/bkp_shl2.sql -T table1 -T table2
+  ```
+
+  In the preceding example, **table1** and **table2** are excluded from the dumping.
+
+- -exclude-table-file=FILENAME
+
+  Specifies the table files that do not need to be dumped.
+
+  ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  Same as **-include-table-file**, the content format of this parameter is as follows:
+  schema1.table1 schema2.table2 ……
+
+- -x, -no-privileges|-no-acl
+
+  Prevents the dumping of access permissions (grant/revoke commands).
+
+- -binary-upgrade
+
+  Specifies a reserved port for function expansion. This parameter is not recommended.
+
+- -binary-upgrade-usermap="USER1=USER2"
+
+  Specifies a reserved port for function expansion. This parameter is not recommended.
+
+- -column-inserts|-attribute-inserts
+
+  Exports data by running the **INSERT** command with explicit column names **{INSERT INTO table (column, …) VALUES …}**. This will cause a slow restoration. However, since this option generates an independent command for each row, an error in reloading a row causes only the loss of the row rather than the entire table content.
+
+- -disable-dollar-quoting
+
+  Disables the use of dollar sign ($) for function bodies, and forces them to be quoted using the SQL standard string syntax.
+
+- -disable-triggers
+
+  Specifies a reserved port for function expansion. This parameter is not recommended.
+
+- -exclude-table-data=TABLE
+
+  Does not dump data that matches any of table patterns. The pattern is interpreted according to the same rules as for **-t**.
+
+  **-exclude-table-data** can be entered more than once to exclude tables matching any of several patterns. When you need the specified table definition rather than data in the table, this option is helpful.
+
+  To exclude data of all tables in the database, see -schema-only.
+
+- -inserts
+
+  Dumps data by the **INSERT** statement (rather than **COPY**). This will cause a slow restoration.
+
+  However, since this option generates an independent command for each row, an error in reloading a row causes only the loss of the row rather than the entire table content. The restoration may fail if you rearrange the column order. The **-column-inserts** option is unaffected against column order changes, though even slower.
+
+- -no-security-labels
+
+  Specifies a reserved port for function expansion. This parameter is not recommended.
+
+- -no-tablespaces
+
+  Does not issue commands to select tablespaces. All the objects will be created during restoration, no matter which tablespace is selected when using this option.
+
+  This parameter is used only for the plain-text format. For the archive format, you can specify the option when using **gs_restore**.
+
+- -no-unlogged-table-data
+
+  Specifies a reserved port for function expansion. This parameter is not recommended.
+
+- -non-lock-table
+
+  Specifies a reserved port for function expansion. This parameter is not recommended.
+
+- -include-alter-table
+
+  Dumps deleted columns of tables. This option records deleted columns.
+
+- -quote-all-identifiers
+
+  Forcibly quotes all identifiers. This parameter is useful when you dump a database for migration to a later version, in which additional keywords may be introduced.
+
+- -section=SECTION
+
+  Specifies dumped name sections (pre-data, data, or post-data).
+
+- -serializable-deferrable
+
+  Uses a serializable transaction for the dump to ensure that the used snapshot is consistent with later database status. Perform this operation at a time point in the transaction flow, at which everything is normal. This ensures successful transaction and avoids serialization failures of other transactions, which requires serialization again.
+
+  This option has no benefits for disaster recovery. During the upgrade of the original database, loading a database as a report or loading other shared read-only dump is helpful. If the option does not exist, dump reveals a status which is different from the submitted sequence status of any transaction.
+
+  This option will make no difference if there are no active read-write transactions when **gs_dump** is started. If the read-write transactions are in active status, the dump start time will be delayed for an uncertain period.
+
+- -use-set-session-authorization
+
+  Specifies that the standard SQL **SET SESSION AUTHORIZATION** command rather than **ALTER OWNER** is returned to ensure the object ownership. This makes dumping more standard. However, if a dump file contains objects that have historical problems, restoration may fail. A dump using **SET SESSION AUTHORIZATION** requires the system administrator permissions, whereas **ALTER OWNER** requires lower permissions.
+
+- -with-encryption=AES128
+
+  Specifies that dumping data needs to be encrypted using AES128.
+
+- -with-key=KEY
+
+  Specifies that the key length of AES128 must be 16 bytes.
+
+**NOTE:**
+
+When using the gs_dump tool for encrypted export, only plain format export is supported. The data exported through -F plain needs to be imported through the gsql tool, and if it is imported through encryption, the -with-key parameter must be specified when importing through gsql.
+
+- -include-depend-objs
+
+  Includes information about the objects that depend on the specified object in the backup result. This parameter takes effect only if the **-t** or **-include-table-file** parameter is specified.
+
+- -exclude-self
+
+  Excludes information about the specified object from the backup result. This parameter takes effect only if the **-t** or **-include-table-file** parameter is specified.
+
+- -dont-overwrite-file
+
+  The existing files in plain-text, .tar, and custom formats will be overwritten. This option is not used for the directory format.
+
+  For example:
+
+  Assume that the **backup.sql** file exists in the current directory. If you specify **-f backup.sql** in the input command, and the **backup.sql** file is generated in the current directory, the original file will be overwritten.
+
+  If the backup file already exists and **-dont-overwrite-file** is specified, an error will be reported with the message that the dump file exists.
+
+  ```bash
+  gs_dump -p port_number mogdb -f backup.sql -F plain --dont-overwrite-file
+  ```
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+
+- The **-s/-schema-only** and **-a/-data-only** parameters do not coexist.
+- The **-c/-clean** and **-a/-data-only** parameters do not coexist.
+- **-inserts/-column-inserts** and **-o/-oids** do not coexist, because **OIDS** cannot be set using the **INSERT** statement.
+- **-role** must be used in conjunction with **-rolepassword**.
+- **-binary-upgrade-usermap** must be used in conjunction with **-binary-upgrade**.
+- **-include-depend-objs** or **-exclude-self** takes effect only when **-t** or **-include-table-file** is specified.
+- **-exclude-self** must be used in conjunction with **-include-depend-objs**.
+
+Connection parameters:
+
+- -h, -host=HOSTNAME
+
+  Specifies the host name. If the value begins with a slash (/), it is used as the directory for the UNIX domain socket. The default value is taken from the **PGHOST** environment variable (if available). Otherwise, a Unix domain socket connection is attempted.
+
+  This parameter is used only for defining names of the hosts outside MogDB. The names of the hosts inside MogDB must be 127.0.0.1.
+
+  Example:**host name**
+
+  Environment variable:**PGHOST**
+
+- -p, -port=PORT
+
+  Specifies the host port number. If the thread pool function is enabled, you are advised to use **pooler port**, that is, the host port number plus 1.
+
+  Environment variable:**PGPORT**
+
+- -U, -username=NAME
+
+  Specifies the username of the host to be connected.
+
+  If the username of the host to be connected is not specified, the system administrator is used by default.
+
+  Environment variable:**PGUSER**
+
+- -w, -no-password
+
+  Never issues a password prompt. The connection attempt fails if the host requires password verification and the password is not provided in other ways. This parameter is useful in batch jobs and scripts in which no user password is required.
+
+- -W, -password=PASSWORD
+
+  Specifies the user password for connection. If the host uses the trust authentication policy, the administrator does not need to enter the **-W** option. If the **-W** option is not provided and you are not a system administrator, the Dump Restore tool will ask you to enter a password.
+
+- -role=ROLENAME
+
+  Specifies a role name to be used for creating the dump. If this option is selected, the **SET ROLE** command will be issued after the database is connected to **gs_dump**. It is useful when the authenticated user (specified by **-U**) lacks the permissions required by **gs_dump**. It allows the user to switch to a role with the required permissions. Some installations have a policy against logging in directly as a super administrator. This option allows dumping data without violating the policy.
+
+- -rolepassword=ROLEPASSWORD
+
+  Specifies the password for a role.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+
+If any local additions need to be added to the template1 database in MogDB, restore the output of **gs_dump** into an empty database with caution. Otherwise, you are likely to obtain errors due to duplicate definitions of the added objects. To create an empty database without any local additions, data from template0 rather than template1. Example:
+
+```
+CREATE DATABASE foo WITH TEMPLATE template0;
+```
+
+The .tar file size must be smaller than 8 GB. (This is the .tar file format limitations.) The total size of a .tar archive and any of the other output formats are not limited, except possibly by the OS.
+
+The dump file generated by **gs_dump** does not contain the statistics used by the optimizer to make execution plans. Therefore, you are advised to run **ANALYZE** after restoring from a dump file to ensure optimal performance. The dump file does not contain any **ALTER DATABASE … SET** commands. These settings are dumped by **gs_dumpall**, along with database users and other installation settings.
+
+### Examples
+
+Use **gs_dump** to dump a database as a SQL text file or a file in other formats.
+
+In the following examples, **Bigdata@123** indicates the password for the database user. **backup/MPPDB_backup.sql** indicates an exported file where **backup** indicates the relative path of the current directory. **37300** indicates the port number of the database server. **mogdb** indicates the name of the database to be accessed.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** Before exporting files, ensure that the directory exists and you have the read and write permissions on the directory.
+
+Example 1: Use **gs_dump** to export the full information of the mogdb database. The exported **MPPDB_backup.sql** file is in plain-text format.
+
+```bash
+gs_dump -U omm -W Bigdata@123 -f backup/MPPDB_backup.sql -p 37300 mogdb -F p
+gs_dump[port='37300'][mogdb][2018-06-27 09:49:17]: The total objects number is 356.
+gs_dump[port='37300'][mogdb][2018-06-27 09:49:17]: [100.00%] 356 objects have been dumped.
+gs_dump[port='37300'][mogdb][2018-06-27 09:49:17]: dump database mogdb successfully
+gs_dump[port='37300'][mogdb][2018-06-27 09:49:17]: total time: 1274  ms
+```
+
+Use **gsql** to import data from the exported plain-text file.
+
+Example 2: Use **gs_dump** to export the full information of the mogdb database. The exported **MPPDB_backup.tar** file is in .tar format.
+
+```bash
+gs_dump -U omm -W Bigdata@123 -f backup/MPPDB_backup.tar -p 37300 mogdb -F t
+gs_dump[port='37300'][mogdb][2018-06-27 10:02:24]: The total objects number is 1369.
+gs_dump[port='37300'][mogdb][2018-06-27 10:02:53]: [100.00%] 1369 objects have been dumped.
+gs_dump[port='37300'][mogdb][2018-06-27 10:02:53]: dump database mogdb successfully
+gs_dump[port='37300'][mogdb][2018-06-27 10:02:53]: total time: 50086  ms
+```
+
+Example 3: Use **gs_dump** to export the full information of the mogdb database. The exported **MPPDB_backup.dmp** file is in custom format.
+
+```bash
+gs_dump -U omm -W Bigdata@123 -f backup/MPPDB_backup.dmp -p 37300 mogdb -F c
+gs_dump[port='37300'][mogdb][2018-06-27 10:05:40]: The total objects number is 1369.
+gs_dump[port='37300'][mogdb][2018-06-27 10:06:03]: [100.00%] 1369 objects have been dumped.
+gs_dump[port='37300'][mogdb][2018-06-27 10:06:03]: dump database mogdb successfully
+gs_dump[port='37300'][mogdb][2018-06-27 10:06:03]: total time: 36620  ms
+```
+
+Example 4: Use **gs_dump** to export the full information of the mogdb database. The exported **MPPDB_backup** file is in directory format.
+
+```bash
+gs_dump -U omm -W Bigdata@123 -f backup/MPPDB_backup -p 37300  mogdb -F d
+gs_dump[port='37300'][mogdb][2018-06-27 10:16:04]: The total objects number is 1369.
+gs_dump[port='37300'][mogdb][2018-06-27 10:16:23]: [100.00%] 1369 objects have been dumped.
+gs_dump[port='37300'][mogdb][2018-06-27 10:16:23]: dump database mogdb successfully
+gs_dump[port='37300'][mogdb][2018-06-27 10:16:23]: total time: 33977  ms
+```
+
+Example 5: Use **gs_dump** to export the information of the mogdb database, excluding the information of the table specified in the **/home/MPPDB_temp.sql** file. The exported **MPPDB_backup.sql** file is in plain-text format.
+
+```bash
+gs_dump -U omm -W Bigdata@123 -p 37300 mogdb --exclude-table-file=/home/MPPDB_temp.sql -f backup/MPPDB_backup.sql
+gs_dump[port='37300'][mogdb][2018-06-27 10:37:01]: The total objects number is 1367.
+gs_dump[port='37300'][mogdb][2018-06-27 10:37:22]: [100.00%] 1367 objects have been dumped.
+gs_dump[port='37300'][mogdb][2018-06-27 10:37:22]: dump database mogdb successfully
+gs_dump[port='37300'][mogdb][2018-06-27 10:37:22]: total time: 37017  ms
+```
+
+Example 6: Use **gs_dump** to export only the information about the views that depend on the **testtable** table. Create another **testtable** table, and then restore the views that depend on it.
+
+- Back up only the views that depend on the **testtable** table.
+
+  ```bash
+  gs_dump -s -p 37300 mogdb -t PUBLIC.testtable --include-depend-objs --exclude-self -f backup/MPPDB_backup.sql -F p
+  gs_dump[port='37300'][mogdb][2018-06-15 14:12:54]: The total objects number is 331.
+  gs_dump[port='37300'][mogdb][2018-06-15 14:12:54]: [100.00%] 331 objects have been dumped.
+  gs_dump[port='37300'][mogdb][2018-06-15 14:12:54]: dump database mogdb successfully
+  gs_dump[port='37300'][mogdb][2018-06-15 14:12:54]: total time: 327  ms
+  ```
+
+- Change the name of the **testtable** table.
+
+  ```
+  gsql -p 37300 mogdb -r -c "ALTER TABLE PUBLIC.testtable RENAME TO testtable_bak;"
+  ```
+
+- Create another **testtable** table.
+
+  ```
+  CREATE TABLE PUBLIC.testtable(a int, b int, c int);
+  ```
+
+- Restore the views for the new **testtable** table.
+
+  ```
+  gsql -p 37300 mogdb -r -f backup/MPPDB_backup.sql
+  ```
+
+## gs_dumpall
+
+### Background
+
+**gs_dumpall**, provided by MogDB, is used to export all MogDB database information, including data of the default database mogdb, user-defined databases, and common global objects of all MogDB databases.
+
+**gs_dumpall** is executed by OS user **omm**.
+
+When **gs_dumpall** is used to export data, other users can still access (read and write) MogDB databases.
+
+**gs_dumpall** can export complete, consistent data. For example, if **gs_dumpall** is started to export MogDB database at T1, data of the database at that time point will be exported, and modifications on the database after that time point will not be exported.
+
+**gs_dumpall** exports all MogDB databases in two parts:
+
+- **gs_dumpall** exports all global objects, including information about database users and groups, tablespaces, and attributes (for example, global access permissions).
+- **gs_dumpall** invokes **gs_dump** to export SQL scripts from each MogDB database, which contain all the SQL statements required to restore databases.
+
+The exported files are both plain-text SQL scripts. Use gsql to execute them to restore MogDB databases.
+
+### Precautions
+
+- Do not modify an exported file or its content. Otherwise, restoration may fail.
+- To ensure the data consistency and integrity, **gs_dumpall** acquires a share lock on a table to be dumped. If another transaction has acquired a share lock on the table, **gs_dumpall** waits until this lock is released and then locks the table for dumping. If the table cannot be locked within the specified time, the dump fails. You can customize the timeout duration to wait for lock release by specifying the **-lock-wait-timeout** parameter.
+- During an export, **gs_dumpall** reads all tables in a database. Therefore, you need to connect to the database as an MogDB administrator to export a complete file. When you use **gsql** to execute SQL scripts, cluster administrator permissions are also required to add users and user groups, and create databases.
+
+### Syntax
+
+```bash
+gs_dumpall [OPTION]...
+```
+
+### Parameter Description
+
+Common parameters:
+
+- -f, -filename=FILENAME
+
+  Sends the output to the specified file. If this parameter is omitted, the standard output is generated.
+
+- -v, -verbose
+
+  Specifies the verbose mode. If it is specified, **gs_dumpall** writes detailed object comments and number of startups/stops to the dump file, and progress messages to standard error.
+
+- -V, -version
+
+  Prints the **gs_dumpall** version and exits.
+
+- -lock-wait-timeout=TIMEOUT
+
+  Do not keep waiting to obtain shared table locks at the beginning of the dump. Consider it as failed if you are unable to lock a table within the specified time. The timeout period can be specified in any of the formats accepted by **SET statement_timeout**.
+
+- -?, -help
+
+  Displays help about **gs_dumpall** parameters and exits.
+
+Dump parameters:
+
+- -a, -data-only
+
+  Dumps only the data, not the schema (data definition).
+
+- -c, -clean
+
+  Runs SQL statements to delete databases before rebuilding them. Statements for dumping roles and tablespaces are added.
+
+- -g, -globals-only
+
+  Dumps only global objects (roles and tablespaces) but no databases.
+
+- -o, -oids
+
+  Dumps object identifiers (OIDs) as parts of the data in each table. Use this parameter if your application references the OID columns in some way. If the preceding situation does not occur, do not use this parameter.
+
+- -O, -no-owner
+
+  Do not output commands to set ownership of objects to match the original database. By default, **gs_dumpall** issues the **ALTER OWNER** or **SET SESSION AUTHORIZATION** command to set ownership of created schema objects. These statements will fail when the script is running unless it is started by a system administrator (or the same user that owns all of the objects in the script). To make a script that can be stored by any user and give the user ownership of all objects, specify **-O**.
+
+- -r, -roles-only
+
+  Dumps only roles but not databases or tablespaces.
+
+- -s, -schema-only
+
+  Dumps only the object definition (schema) but not data.
+
+- -S, -sysadmin=NAME
+
+  Name of the system administrator during the dump.
+
+- -t, -tablespaces-only
+
+  Dumps only tablespaces but not databases or roles.
+
+- -x, -no-privileges
+
+  Prevents the dumping of access permissions (grant/revoke commands).
+
+- -column-inserts|-attribute-inserts
+
+  Exports data by running the **INSERT** command with explicit column names **{INSERT INTO table (column, …) VALUES …}**. This will cause a slow restoration. However, since this option generates an independent command for each row, an error in reloading a row causes only the loss of the row rather than the entire table content.
+
+- -disable-dollar-quoting
+
+  Disables the use of dollar sign ($) for function bodies, and forces them to be quoted using the SQL standard string syntax.
+
+- -disable-triggers
+
+  Specifies a reserved port for function expansion. This parameter is not recommended.
+
+- -inserts
+
+  Dumps data by the **INSERT** statement (rather than **COPY**). This will cause a slow restoration. The restoration may fail if you rearrange the column order. The **-column-inserts** option is unaffected against column order changes, though even slower.
+
+- -no-security-labels
+
+  Specifies a reserved port for function expansion. This parameter is not recommended.
+
+- -no-tablespaces
+
+  Does not generate output statements to create tablespaces or select tablespaces for objects. All the objects will be created during the restoration process, no matter which tablespace is selected when using this option.
+
+- -no-unlogged-table-data
+
+  Specifies a reserved port for function expansion. This parameter is not recommended.
+
+- -quote-all-identifiers
+
+  Forcibly quotes all identifiers. This parameter is useful when you dump a database for migration to a later version, in which additional keywords may be introduced.
+
+- -dont-overwrite-file
+
+  Does not overwrite the current file.
+
+- -use-set-session-authorization
+
+  Specifies that the standard SQL **SET SESSION AUTHORIZATION** command rather than **ALTER OWNER** is returned to ensure the object ownership. This makes dumping more standard. However, if a dump file contains objects that have historical problems, restoration may fail. A dump using **SET SESSION AUTHORIZATION** requires the system administrator rights, whereas **ALTER OWNER** requires lower permissions.
+
+- -with-encryption=AES128
+
+  Specifies that dumping data needs to be encrypted using AES128.
+
+- -with-key=KEY
+
+  Specifies that the key length of AES128 must be 16 bytes.
+
+- -include-templatedb
+
+  Includes template databases during the dump.
+
+- -binary-upgrade
+
+  Specifies a reserved port for function expansion. This parameter is not recommended.
+
+- -binary-upgrade-usermap="USER1=USER2"
+
+  Specifies a reserved port for function expansion. This parameter is not recommended.
+
+- -tablespaces-postfix
+
+  Specifies a reserved port for function expansion. This parameter is not recommended.
+
+- -parallel-jobs
+
+  Specifies the number of concurrent backup processes. The value range is 1-1000.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+
+- The **-g/-globals-only** and **-r/-roles-only** parameters do not coexist.
+- The **-g/-globals-only** and **-t/-tablespaces-only** parameters do not coexist.
+- The **-r/-roles-only** and **-t/-tablespaces-only** parameters do not coexist.
+- The **-s/-schema-only** and **-a/-data-only** parameters do not coexist.
+- The **-r/-roles-only** and **-a/-data-only** parameters do not coexist.
+- The **-t/-tablespaces-only** and **-a/-data-only** parameters do not coexist.
+- The **-g/-globals-only** and **-a/-data-only** parameters do not coexist.
+- **-tablespaces-postfix** must be used in conjunction with **-binary-upgrade**.
+- **-binary-upgrade-usermap** must be used in conjunction with **-binary-upgrade**.
+- **-parallel-jobs** must be used in conjunction with **-f/-file**.
+
+Connection parameters:
+
+- -h, -host
+
+  Specifies the host name. If the value begins with a slash (/), it is used as the directory for the UNIX domain socket. The default value is taken from the PGHOST environment (if variable). Otherwise, a Unix domain socket connection is attempted.
+
+  This parameter is used only for defining names of the hosts outside MogDB. The names of the hosts inside MogDB must be 127.0.0.1.
+
+  Environment Variable:**PGHOST**
+
+- -l, -database
+
+  Specifies the name of the database connected to dump all objects and discover other databases to be dumped. If this parameter is not specified, the **mogdb** database will be used. If the **mogdb** database does not exist, **template1** will be used.
+
+- -p, -port
+
+  TCP port or the local Unix-domain socket file extension on which the server is listening for connections. The default value is the *PGPORT* environment variable.
+
+  If the thread pool function is enabled, you are advised to use **pooler port**, that is, the listening port number plus 1.
+
+  Environment variable:**PGPORT**
+
+- -U, -username
+
+  Specifies the user name to connect to.
+
+  Environment variable:**PGUSER**
+
+- -w, -no-password
+
+  Never issues a password prompt. The connection attempt fails if the host requires password verification and the password is not provided in other ways. This parameter is useful in batch jobs and scripts in which no user password is required.
+
+- -W, -password
+
+  Specifies the user password for connection. If the host uses the trust authentication policy, the administrator does not need to enter the **-W** option. If the **-W** option is not provided and you are not a system administrator, the Dump Restore tool will ask you to enter a password.
+
+- -role
+
+  Specifies a role name to be used for creating the dump. This option causes **gs_dumpall** to issue the **SET ROLE** statement after connecting to the database. It is useful when the authenticated user (specified by **-U**) lacks the permissions required by the **gs_dumpall**. It allows the user to switch to a role with the required permissions. Some installations have a policy against logging in directly as a system administrator. This option allows dumping data without violating the policy.
+
+- -rolepassword
+
+  Specifies the password of the specific role.
+
+### Notice
+
+**gs_dumpall** internally invokes **gs_dump**. For details about the diagnosis information, see gs_dump.
+
+Once **gs_dumpall** is restored, run ANALYZE on each database so that the optimizer can provide useful statistics.
+
+**gs_dumpall** requires all needed tablespace directories to exit before the restoration. Otherwise, database creation will fail if the databases are in non-default locations.
+
+### Examples
+
+Use **gs_dumpall** to export all MogDB databases at a time.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** **gs_dumpall** supports only plain-text format export. Therefore, only **gsql** can be used to restore a file exported using **gs_dumpall**.
+
+```bash
+gs_dumpall -f backup/bkp2.sql -p 37300
+gs_dump[port='37300'][dbname='mogdb'][2018-06-27 09:55:09]: The total objects number is 2371.
+gs_dump[port='37300'][dbname='mogdb'][2018-06-27 09:55:35]: [100.00%] 2371 objects have been dumped.
+gs_dump[port='37300'][dbname='mogdb'][2018-06-27 09:55:46]: dump database dbname='mogdb' successfully
+gs_dump[port='37300'][dbname='mogdb'][2018-06-27 09:55:46]: total time: 55567  ms
+gs_dumpall[port='37300'][2018-06-27 09:55:46]: dumpall operation successful
+gs_dumpall[port='37300'][2018-06-27 09:55:46]: total time: 56088  ms
+```
+
+## gs_restore
+
+### Background
+
+**gs_restore**, provided by MogDB, is used to import data that was exported using **gs_dump**. It can also be used to import files exported by **gs_dump**.
+
+**gs_restore** is executed by OS user **omm**.
+
+It has the following functions:
+
+- Importing data to the database
+
+  If a database is specified, data is imported to the database. For parallel import, the password for connecting to the database is required.
+
+- Importing data to the script file
+
+  If the database storing imported data is not specified, a script containing the SQL statement to recreate the database is created and written to a file or standard output. This script output is equivalent to the plain text output format of **gs_dump**.
+
+### Command Format
+
+```
+gs_restore [OPTION]... FILE
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - **FILE** does not have a short or long parameter. It is used to specify the location for the archive files.
+> - The **dbname** or **-l** parameter is required as prerequisites. Users cannot enter **dbname** and **-l** parameters at the same time.
+> - **gs_restore** incrementally imports data by default. To prevent data exceptions caused by multiple import operations, you are advised to use the **-c** parameter during the import. Before recreating database objects, delete the database objects that already exist in the database to be restored.
+> - There is no option to control log printing. To hide logs, redirect the logs to the log file. If a large amount of table data needs to be restored, the table data will be restored in batches. Therefore, the log indicating that the table data has been imported is generated for multiple times.
+
+### Parameter Description
+
+Common parameters
+
+- -d, -dbname=NAME
+
+  Connects to the **dbname** database and imports data to the database.
+
+- -f, -file=FILENAME
+
+  Specifies the output file for the generated script, or uses the output file in the list specified using **-l**.
+
+  The default is the standard output.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  > **-f** cannot be used in conjunction with **-d**.
+
+- -F, -format=c|d|t
+
+    Specifies the format of the archive. The format does not need to be specified because the **gs_restore** determines the format automatically.
+
+    Value range:
+
+  - **c/custom**: The archive form is the customized format in gs_dump.
+  - **d/directory**: The archive form is a directory archive format.
+  - **t/tar**: The archive form is a .tar archive format.
+
+- -l, -list
+
+  Lists the forms of the archive. The operation output can be used for the input of the **-L** parameter. If filtering parameters, such as **-n** or **-t**, are used together with **-l**, they will restrict the listed items.
+
+- -v, -verbose
+
+  Specifies the verbose mode.
+
+- -V, -version
+
+  Prints the **gs_restore** version and exits.
+
+- -?, -help
+
+  Displays help information about the parameters of **gs_restore** and exits.
+
+Parameters for importing data
+
+- -a, -data-only
+
+  Imports only the data, not the schema (data definition). **gs_restore** incrementally imports data.
+
+- -c, -clean
+
+  Cleans (deletes) existing database objects in the database to be restored before recreating them.
+
+- -C, -create
+
+  Creates the database before importing data to it. (When this parameter is used, the database specified by **-d** is used to issue the initial **CREATE DATABASE** command. All data is imported to the created database.)
+
+- -e, -exit-on-error
+
+  Exits if an error occurs when you send the SQL statement to the database. If you do not exit, the commands will still be sent and error information will be displayed when the import ends.
+
+- -I, -index=NAME
+
+  Imports only the definition of the specified index. Multiple indexes can be imported. Enter **-I** _index_ multiple times to import multiple indexes.
+
+  For example:
+
+  ```
+  gs_restore -h host_name -p port_number -d mogdb -I Index1 -I Index2 backup/MPPDB_backup.tar
+  ```
+
+  In this example, **Index1** and **Index2** will be imported.
+
+- -j, -jobs=NUM
+
+  Specifies the number of concurrent, the most time-consuming jobs of **gs_restore** (such as loading data, creating indexes, or creating constraints). This parameter can greatly reduce the time to import a large database to a server running on a multiprocessor machine.
+
+  Each job is one process or one thread, depending on the OS; and uses a separate connection to the server.
+
+  The optimal value for this option depends on the server hardware setting, the client, the network, the number of CPU cores, and disk settings. It is recommended that the parameter be set to the number of CPU cores on the server. In addition, a larger value can also lead to faster import in many cases. However, an overly large value will lead to decreased performance because of thrashing.
+
+  This parameter supports custom-format archives only. The input file must be a regular file (not the pipe file). This parameter can be ignored when you select the script method rather than connect to a database server. In addition, multiple jobs cannot be used in conjunction with the **-single-transaction** parameter.
+
+- -L, -use-list=FILENAME
+
+  Imports only archive elements that are listed in **list-file** and imports them in the order that they appear in the file. If filtering parameters, such as **-n** or **-t**, are used in conjunction with **-L**, they will further limit the items to be imported.
+
+  **list-file** is normally created by editing the output of a previous **-l** parameter. File lines can be moved or removed, and can also be commented out by placing a semicolon (;) at the beginning of the row.
+
+- -n, -schema=NAME
+
+  Restores only objects that are listed in schemas.
+
+  This parameter can be used in conjunction with the **-t** parameter to import a specific table.
+
+  Entering **-n schemaname** multiple times can import multiple schemas.
+
+  For example:
+
+  ```
+  gs_restore -h host_name -p port_number -d mogdb -n sch1 -n sch2 backup/MPPDB_backup.tar
+  ```
+
+  In this example, **sch1** and **sch2** will be imported.
+
+- -O, -no-owner
+
+  Do not output commands to set ownership of objects to match the original database. By default, **gs_restore** issues the **ALTER OWNER** or **SET SESSION AUTHORIZATION** statement to set ownership of created schema elements. Unless the system administrator or the user who has all the objects in the script initially accesses the database. Otherwise, the statement will fail. Any user name can be used for the initial connection using **-O**, and this user will own all the created objects.
+
+- -P, -function=NAME(args)
+
+  Imports only listed functions. You need to correctly spell the function name and the parameter based on the contents of the dump file in which the function exists.
+
+  Entering **-P** alone means importing all function-name(args) functions in a file. Entering **-P** with **-n** means importing the function-name(args) functions in a specified schema. Entering **-P** multiple times and using **-n** once means that all imported functions are in the **-n** schema by default.
+
+  You can enter **-n schema-name -P 'function-name(args)'** multiple times to import functions in specified schemas.
+
+  For example:
+
+  ```
+  gs_restore -h host_name -p port_number -d mogdb -n test1 -P 'Func1(integer)' -n test2 -P 'Func2(integer)' backup/MPPDB_backup.tar
+  ```
+
+  In this example, both **Func1 (i integer)** in the **test1** schema and **Func2 (j integer)** in the **test2** schema will be imported.
+
+- -s, -schema-only
+
+  Imports only schemas (data definitions), instead of data (table content). The current sequence value will not be imported.
+
+- -S, -sysadmin=NAME
+
+  Specifies a reserved port for function expansion. This parameter is not recommended.
+
+- -t, -table=NAME
+
+  Imports only listed table definitions or data, or both. This parameter can be used in conjunction with the **-n** parameter to specify a table object in a schema. When **-n** is not entered, the default schema is PUBLIC. Entering **-n schemaname -t tablename** multiple times can import multiple tables in a specified schema.
+
+  For example:
+
+  Import **table1** in the **PUBLIC** schema.
+
+  ```
+  gs_restore -h host_name -p port_number -d mogdb -t table1 backup/MPPDB_backup.tar
+  ```
+
+  Import **test1** in the **test1** schema and **test2** in the **test2** schema.
+
+  ```
+  gs_restore -h host_name -p port_number -d mogdb -n test1 -t test1 -n test2 -t test2 backup/MPPDB_backup.tar
+  ```
+
+  Import **table1** in the **PUBLIC** schema and **test1** in the **test1** schema.
+
+  ```
+  gs_restore -h host_name -p port_number -d mogdb -n PUBLIC -t table1 -n test1 -t table1 backup/MPPDB_backup.tar
+  ```
+
+- -T, -trigger=NAME
+
+  This parameter is reserved for extension.
+
+- -x, -no-privileges/-no-acl
+
+  Prevents the import of access permissions (**GRANT**/**REVOKE** commands).
+
+- -1, -single-transaction
+
+  Executes import as a single transaction (that is, commands are wrapped in **BEGIN**/**COMMIT**).
+
+  This parameter ensures that either all the commands are completed successfully or no application is changed. This parameter means **-exit-on-error**.
+
+- -disable-triggers
+
+  Specifies a reserved port for function expansion. This parameter is not recommended.
+
+- -no-data-for-failed-tables
+
+  By default, table data will be imported even if the statement to create a table fails (for example, the table already exists). Data in such table is skipped using this parameter. This operation is useful if the target database already contains the desired table contents.
+
+  This parameter takes effect only when you import data directly into a database, not when you output SQL scripts.
+
+- -no-security-labels
+
+  Specifies a reserved port for function expansion. This parameter is not recommended.
+
+- -no-tablespaces
+
+  Tablespaces excluding specified ones All objects will be created during the import process no matter which tablespace is selected when using this option.
+
+- -section=SECTION
+
+  Imports the listed sections (such as pre-data, data, or post-data).
+
+- -use-set-session-authorization
+
+  Is used for plain-text backup.
+
+  Outputs the **SET SESSION AUTHORIZATION** statement instead of the **ALTER OWNER** statement to determine object ownership. This parameter makes dump more standards-compatible. If the records of objects in exported files are referenced, import may fail. Only administrators can use the **SET SESSION AUTHORIZATION** statement to dump data, and the administrators must manually change and verify the passwords of exported files by referencing the **SET SESSION AUTHORIZATION** statement before import. The **ALTER OWNER** statement requires lower permissions.
+
+- -with-key=KEY
+
+  Specifies that the key length of AES128 must be 16 bytes.
+
+  ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** If the dump is encrypted, enter the **-with-key=KEY** parameter in the **gs_restore** command. If it is not entered, you will receive an error message. Enter the same key while entering the dump. When the dump format is **c** or **t**, the dumped content has been processed, and therefore the input is not restricted by the encryption.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif)**NOTICE:**
+
+- If any local additions need to be added to the template1 database during the installation, restore the output of **gs_restore** into an empty database with caution. Otherwise, you are likely to obtain errors due to duplicate definitions of the added objects. To create an empty database without any local additions, data from template0 rather than template1. Example:
+
+  ```
+  CREATE DATABASE foo WITH TEMPLATE template0;
+  ```
+
+- **gs_restore** cannot import large objects selectively. For example, it can only import the objects of a specified table. If an archive contains large objects, all large objects will be imported, or none of them will be restored if they are excluded by using **-L**, **-t**, or other parameters.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> 1. The **-d/-dbname** and **-f/-file** parameters do not coexist.
+> 2. The **-s/-schema-only** and **-a/-data-only** parameters do not coexist.
+> 3. The **-c/-clean** and **-a/-data-only** parameters do not coexist.
+> 4. When **-single-transaction** is used, **-j/-jobs** must be a single job.
+> 5. **-role** must be used in conjunction with **-rolepassword**.
+
+Connection parameters:
+
+- -h, -host=HOSTNAME
+
+  Specifies the host name. If the value begins with a slash (/), it is used as the directory for the UNIX domain socket. The default value is taken from the *PGHOST* environment variable. If it is not set, a UNIX domain socket connection is attempted.
+
+  This parameter is used only for defining names of the hosts outside MogDB. The names of the hosts inside MogDB must be 127.0.0.1.
+
+- -p, -port=PORT
+
+  TCP port or the local Unix-domain socket file extension on which the server is listening for connections. The default value is the *PGPORT* environment variable.
+
+  If the thread pool function is enabled, you are advised to use **pooler port**, that is, the listening port number plus 1.
+
+- -U, -username=NAME
+
+  Specifies the user name to connect to.
+
+- -w, -no-password
+
+  Never issues a password prompt. The connection attempt fails if the host requires password verification and the password is not provided in other ways. This parameter is useful in batch jobs and scripts in which no user password is required.
+
+- -W, -password=PASSWORD
+
+  User password for database connection. If the host uses the trust authentication policy, the administrator does not need to enter the **-W** parameter. If the **-W** parameter is not provided and you are not a system administrator, **gs_restore** will ask you to enter a password.
+
+- -role=ROLENAME
+
+  Specifies a role name for the import operation. If this parameter is selected, the **SET ROLE** statement will be issued after **gs_restore** connects to the database. It is useful when the authenticated user (specified by **-U**) lacks the permissions required by **gs_restore**. This parameter allows the user to switch to a role with the required permissions. Some installations have a policy against logging in directly as the initial user. This parameter allows data to be imported without violating the policy.
+
+- -rolepassword=ROLEPASSWORD
+
+  Role password.
+
+### Example
+
+Special case: Execute the **gsql** tool. Run the following commands to import the **MPPDB_backup.sql** file in the export folder (in plain-text format) generated by **gs_dump**/**gs_dumpall** to the **mogdb** database:
+
+```bash
+gsql -d mogdb -p 5432 -W Bigdata@123 -f /home/omm/test/MPPDB_backup.sql
+SET
+SET
+SET
+SET
+SET
+ALTER TABLE
+ALTER TABLE
+ALTER TABLE
+ALTER TABLE
+ALTER TABLE
+CREATE INDEX
+CREATE INDEX
+CREATE INDEX
+SET
+CREATE INDEX
+REVOKE
+REVOKE
+GRANT
+GRANT
+total time: 30476  ms
+```
+
+**gs_restore** is used to import the files exported by **gs_dump**.
+
+Example 1: Execute the **gs_restore** tool to import the exported **MPPDB_backup.dmp** file (custom format) to the **mogdb** database.
+
+```bash
+gs_restore -W Bigdata@123 backup/MPPDB_backup.dmp -p 5432 -d mogdb
+gs_restore: restore operation successful
+gs_restore: total time: 13053  ms
+```
+
+Example 2: Execute the **gs_restore** tool to import the exported **MPPDB_backup.tar** file (.tar format) to the **mogdb** database.
+
+```bash
+gs_restore backup/MPPDB_backup.tar -p 5432 -d mogdb
+gs_restore[2017-07-21 19:16:26]: restore operation successful
+gs_restore[2017-07-21 19:16:26]: total time: 21203  ms
+```
+
+Example 3: Execute the **gs_restore** tool to import the exported **MPPDB_backup** file (directory format) to the **mogdb** database.
+
+```bash
+gs_restore backup/MPPDB_backup -p 5432 -d mogdb
+gs_restore[2017-07-21 19:16:26]: restore operation successful
+gs_restore[2017-07-21 19:16:26]: total time: 21003  ms
+```
+
+Example 4: Execute the **gs_restore** tool and run the following commands to import the **MPPDB_backup.dmp** file (in custom format). Specifically, import all the object definitions and data in the **PUBLIC** schema. Existing objects are deleted from the target database before the import. If an existing object references to an object in another schema, you need to manually delete the referenced object first.
+
+```bash
+gs_restore backup/MPPDB_backup.dmp -p 5432 -d mogdb -e -c -n PUBLIC
+gs_restore: [archiver (db)] Error while PROCESSING TOC:
+gs_restore: [archiver (db)] Error from TOC entry 313; 1259 337399 TABLE table1 gaussdba
+gs_restore: [archiver (db)] could not execute query: ERROR:  cannot drop table table1 because other objects depend on it
+DETAIL:  view t1.v1 depends on table table1
+HINT:  Use DROP ... CASCADE to drop the dependent objects too.
+    Command was: DROP TABLE public.table1;
+```
+
+Manually delete the referenced object and create it again after the import is complete.
+
+```bash
+gs_restore backup/MPPDB_backup.dmp -p 5432 -d mogdb -e -c -n PUBLIC
+gs_restore[2017-07-21 19:16:26]: restore operation successful
+gs_restore[2017-07-21 19:16:26]: total time: 2203  ms
+```
+
+Example 5: Execute the **gs_restore** tool and run the following commands to import the **MPPDB_backup.dmp** file (in custom format). Specifically, import only the definition of **table1** in the **PUBLIC** schema.
+
+```bash
+gs_restore backup/MPPDB_backup.dmp -p 5432 -d mogdb -e -c -s -n PUBLIC -t table1
+gs_restore[2017-07-21 19:16:26]: restore operation successful
+gs_restore[2017-07-21 19:16:26]: total time: 21000  ms
+```
+
+Example 6: Execute the **gs_restore** tool and run the following commands to import the **MPPDB_backup.dmp** file (in custom format). Specifically, import only the data of **table1** in the **PUBLIC** schema.
+
+```bash
+gs_restore backup/MPPDB_backup.dmp -p 5432 -d mogdb -e -a -n PUBLIC -t table1
+gs_restore[2017-07-21 19:16:26]: restore operation successful
+gs_restore[2017-07-21 19:16:26]: total time: 20203  ms
+```
+
+## gs_backup
+
+### Background
+
+After MogDB is deployed, problems and exceptions may occur during database running. **gs_backup**, provided by MogDB, is used to help MogDB backup, restore important data, display help information and version information.
+
+### Prerequisites
+
+- The MogDB database can be connected.
+- During the restoration, backup files exist in the backup directory on all the nodes. If backup files are lost on any node, copy them to it from another node. For binary files, you need to change the node name in the file name.
+- You need to execute **gs_backup** command as OS user **omm**.
+
+### Syntax
+
+- Backup database host
+
+  ```bash
+  gs_backup -t backup --backup-dir=BACKUPDIR [-h HOSTNAME] [--parameter] [--binary] [--all] [-l LOGFILE]
+  ```
+
+- Restore database host
+
+  ```bash
+  gs_backup -t restore --backup-dir=BACKUPDIR [-h HOSTNAME] [--parameter] [--binary] [--all] [-l LOGFILE]
+  ```
+
+- Display help information
+
+  ```bash
+  gs_backup -? | --help
+  ```
+
+- Display version information
+
+  ```bash
+  gs_backup -V | --version
+  ```
+
+### Parameter Description
+
+The **gs_backup** tool can use the following types of parameters:
+
+- Backup database host parameters:
+
+  - -h
+
+    Specifies the name of the host where the backup file is stored.
+
+    Range of values: host name. If the host name is not specified, it is distributed to MogDB.
+
+  - -backup-dir=BACKUPDIR
+
+    The path to save the backup file.
+
+  - -parameter
+
+    Back up the parameter file, only the parameter file is backed up by default if the **-parameter**, **-binary** and **-all** parameters are not specified.
+
+  - -binary
+
+    Back up the binary file.
+
+  - -all
+
+    Back up binary and parameter files.
+
+  - -l
+
+    Specify the log file and its storage path.
+
+    Default value: $GAUSSLOG/om/gs_backup-YYYY-MM-DD_hhmmss.log
+
+- Restore database host parameters:
+
+  - -h
+
+    Specify the name of the host to be recovered.
+
+    Range of values: host name. If no host is specified, MogDB is restored.
+
+  - -backup-dir=BACKUPDIR
+
+    Recover file extraction path.
+
+  - -parameter
+
+    Recover the parameter file, only the parameter file is recovered by default if the **-parameter**, **-binary** and **-all** parameters are not specified.
+
+  - -binary
+
+    Recover the binary file.
+
+  - -all
+
+    Recover binary and parameter files.
+
+  - -l
+
+    Specify the log file and its storage path.
+
+    Default value: $GAUSSLOG/om/gs_backup-YYYY-MM-DD_hhmmss.log
+
+- Other parameters:
+
+  - -?, -help
+
+    Display help information.
+
+  - -V, -version
+
+    Display version information.
+
+### Examples
+
+- Use the **gs_backup** script to backup the database host.
+
+  ```bash
+  gs_backup -t backup --backup-dir=/opt/software/mogdb/backup_dir -h plat1 --parameter
+  Backing up MogDB.
+  Parsing configuration files.
+  Successfully parsed the configuration file.
+  Performing remote backup.
+  Remote backup succeeded.
+  Successfully backed up MogDB.
+  ```
+
+- Use the **gs_backup** script to restore the database host.
+
+  ```bash
+  gs_backup -t restore --backup-dir=/opt/software/mogdb/backup_dir -h plat1 --parameter
+  Restoring MogDB.
+  Parsing the configuration file.
+  Successfully parsed configuration files.
+  Performing remote restoration.
+  Remote restoration succeeded.
+  Successfully restored MogDB.
+  ```
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/br/1-4-br.md b/product/en/docs-mogdb/v3.0/administrator-guide/br/1-4-br.md
new file mode 100644
index 0000000000000000000000000000000000000000..b8f94a31ff72cbb402220878a7dffd47d496cbcb
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/br/1-4-br.md
@@ -0,0 +1,203 @@
+---
+title: Flashback Restoration
+summary: Flashback Restoration
+author: Guo Huan
+date: 2021-10-12
+---
+
+# Flashback Restoration
+
+Flashback restoration is a part of the database recovery technology. It can be used to selectively cancel the impact of a committed transaction and restore data from incorrect manual operations. Before the flashback technology is used, the committed database modification can be retrieved only by means of restoring backup and PITR. The restoration takes several minutes or even hours. After the flashback technology is used, it takes only seconds to restore the submitted data before the database is modified. The restoration time is irrelevant to the database size.
+
+**Flashback supports two restoration modes:**
+
+- MVCC-based multi-version data restoration (only Ustore is supported): It is suitable for query and restoration of data deleted, updated and inserted by mistake. Users can configure the retention time of the old version and execute the corresponding query or restore command to query or restore data to Specified point in time or CSN point.
+- Restoration based on database recycle bin (only Astore is supported): It is suitable for the restoration of tables that are DROP and TRUNCATE by mistake. By configuring the recycle bin switch and executing the corresponding restore command, the user can retrieve the tables that were erroneously DROP and TRUNCATE.
+
+**Related parameters:**
+
+- undo_zone_count=16384
+
+  The number of undo zones that can be allocated in the memory, 0 means to disable the undo and Ustore tables, the recommended value is max_connections*4
+
+- enable_default_ustore_table=on
+
+  Enable default support for Ustore storage engine
+
+- version_retention_age=10000
+
+  The number of transactions retained by the old version, the old version that exceeds the number of transactions will be recycled and cleaned up
+
+- enable_recyclebin=on
+
+  enable recycle bin
+
+- recyclebin_retention_time=15min
+
+  Set the recycle bin object retention time, and the recycle bin objects that exceed this time will be automatically cleaned up
+
+<br/>
+
+## Flashback Query
+
+### Context
+
+Flashback query enables you to query a snapshot of a table at a certain time point in the past. This feature can be used to view and logically rebuild damaged data that is accidentally deleted or modified. The flashback query is based on the MVCC mechanism. You can retrieve and query the old version to obtain the data of the specified old version.
+
+### Syntax
+
+```ebnf+diagram
+FlashBack ::= {[ ONLY ] table_name [ * ] [ partition_clause ] [ [ AS ] alias [ ( column_alias [, ...] ) ] ]
+[ TABLESAMPLE sampling_method ( argument [, ...] ) [ REPEATABLE ( seed ) ] ]
+[TIMECAPSULE { TIMESTAMP | CSN } expression ]
+|( select ) [ AS ] alias [ ( column_alias [, ...] ) ]
+|with_query_name [ [ AS ] alias [ ( column_alias [, ...] ) ] ]
+|function_name ( [ argument [, ...] ] ) [ AS ] alias [ ( column_alias [, ...] | column_definition [, ...] ) ]
+|function_name ( [ argument [, ...] ] ) AS ( column_definition [, ...] )
+|from_item [ NATURAL ] join_type from_item [ ON join_condition | USING ( join_column [, ...] ) ]}
+```
+
+In the syntax tree,  **TIMECAPSULE {TIMESTAMP | CSN} expression**  is a new expression for the flashback function.  **TIMECAPSULE**  indicates that the flashback function is used.  **TIMESTAMP**  and  **CSN**  indicate that the flashback function uses specific time point information or commit sequence number (CSN) information.
+
+### Parameter Description
+
+- TIMESTAMP
+  - Specifies a history time point of the table data to be queried.
+- CSN
+  - Specifies a logical commit time point of the data in the entire database to be queried. Each CSN in the database represents a consistency point of the entire database. To query the data under a CSN means to query the data related to the consistency point in the database through SQL statements.
+
+### Examples
+
+- Example 1:
+
+  ```sql
+  SELECT * FROM t1 TIMECAPSULE TIMESTAMP to_timestamp ('2020-02-11 10:13:22.724718', 'YYYY-MM-DD HH24:MI:SS.FF');
+  ```
+
+- Example 2:
+
+  ```sql
+  SELECT * FROM t1 TIMECAPSULE CSN 9617;
+  ```
+
+- Example 3:
+
+  ```sql
+  SELECT * FROM t1 AS t TIMECAPSULE TIMESTAMP to_timestamp ('2020-02-11 10:13:22.724718', 'YYYY-MM-DD HH24:MI:SS.FF');
+  ```
+
+- Example 4:
+
+  ```sql
+  SELECT * FROM t1 AS t TIMECAPSULE CSN 9617;
+  ```
+
+## Flashback Table
+
+### Context
+
+Flashback table enables you to restore a table to a specific point in time. When only one table or a group of tables are logically damaged instead of the entire database, this feature can be used to quickly restore the table data. Based on the MVCC mechanism, the flashback table deletes incremental data at a specified time point and after the specified time point and retrieves the data deleted at the specified time point and the current time point to restore table-level data.
+
+### Syntax
+
+```ebnf+diagram
+FlashBack ::= TIMECAPSULE TABLE table_name TO { TIMESTAMP | CSN } expression
+```
+
+### Examples
+
+```sql
+TIMECAPSULE TABLE t1 TO TIMESTAMP to_timestamp ('2020-02-11 10:13:22.724718', 'YYYY-MM-DD HH24:MI:SS.FF');
+TIMECAPSULE TABLE t1 TO CSN 9617;
+```
+
+## Flashback DROP/TRUNCATE
+
+### Context
+
+Flashback drop enables you to restore tables that are dropped by mistake and their auxiliary structures, such as indexes and table constraints, from the recycle bin. Flashback drop is based on the recycle bin mechanism. You can restore physical table files recorded in the recycle bin to restore dropped tables.
+
+Flashback truncate enables you to restore tables that are truncated by mistake and restore the physical data of the truncated tables and indexes from the recycle bin. Flashback truncate is based on the recycle bin mechanism. You can restore physical table files recorded in the recycle bin to restore truncated tables.
+
+### Prerequisites
+
+- The  **enable_recyclebin**  parameter has been set for enabling the recycle bin.
+- The  **recyclebin_retention**  parameter has been set for specifying the retention period of objects in the recycle bin. The objects will be automatically deleted after the retention period expires.
+
+### Syntax
+
+- Drop a table.
+
+  ```ebnf+diagram
+  DropTable ::= DROP TABLE table_name [PURGE]
+  ```
+
+- Purge objects in the recycle bin.
+
+  ```ebnf+diagram
+  PurgeRecyclebin ::= PURGE { TABLE { table_name }
+  | INDEX { index_name }
+  | RECYCLEBIN
+  }
+  ```
+
+- Flash back a dropped table.
+
+  ```ebnf+diagram
+  TimecapsuleTable ::= TIMECAPSULE TABLE { table_name } TO BEFORE DROP [RENAME TO new_tablename]
+  ```
+
+- Truncate a table.
+
+  ```ebnf+diagram
+  TruncateTable ::= TRUNCATE TABLE { table_name } [ PURGE ]
+  ```
+
+- Flash back a truncated table.
+
+  ```ebnf+diagram
+  TimecapsuleTable ::= TIMECAPSULE TABLE { table_name } TO BEFORE TRUNCATE
+  ```
+
+### Parameter Description
+
+- DROP/TRUNCATE TABLE table_name PURGE
+  - Purges table data in the recycle bin by default.
+- PURGE RECYCLEBIN
+  - Purges objects in the recycle bin.
+- **TO BEFORE DROP**
+
+Retrieves dropped tables and their subobjects from the recycle bin.
+
+You can specify either the original user-specified name of the table or the system-generated name assigned to the object when it was dropped.
+
+- System-generated recycle bin object names are unique. Therefore, if you specify the system-generated name, the database retrieves that specified object. To see the contents of your recycle bin, run  **select  \* from pg_recyclebin;**.
+- If you specify the user-specified name and the recycle bin contains more than one object of that name, the database retrieves the object that was moved to the recycle bin most recently. If you want to retrieve an older version of the table, then do one of these things:
+  - Specify the system-generated recycle bin name of the table you want to retrieve.
+  - Run  **TIMECAPSULE TABLE ... TO BEFORE  DROP**  statements until you retrieve the table you want.
+  - When a dropped table is restored, only the base table name is restored, and the names of other subobjects remain the same as those in the recycle bin. You can run the DDL command to manually change the names of subobjects as required.
+  - The recycle bin does not support write operations such as DML, DCL, and DDL, and does not support DQL query operations (supported in later versions).
+- **RENAME TO**
+
+Specifies a new name for the table retrieved from the recycle bin.
+
+- **TO BEFORE TRUNCATE**
+
+Flashes back to the point in time before the TRUNCATE operation.
+
+### Syntax Example
+
+```sql
+DROP TABLE t1 PURGE;
+
+PURGE TABLE t1;
+PURGE TABLE "BIN$04LhcpndanfgMAAAAAANPw==$0";
+PURGE INDEX i1;
+PURGE INDEX "BIN$04LhcpndanfgMAAAAAANPw==$0";
+PURGE RECYCLEBIN;
+
+TIMECAPSULE TABLE t1 TO BEFORE DROP;
+TIMECAPSULE TABLE t1 TO BEFORE DROP RENAME TO new_t1;
+TIMECAPSULE TABLE "BIN$04LhcpndanfgMAAAAAANPw==$0" TO BEFORE DROP;
+TIMECAPSULE TABLE "BIN$04LhcpndanfgMAAAAAANPw==$0" TO BEFORE DROP RENAME TO new_t1;
+```
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/column-store-tables-management.md b/product/en/docs-mogdb/v3.0/administrator-guide/column-store-tables-management.md
new file mode 100644
index 0000000000000000000000000000000000000000..8e210216c483c34a7d97c478cc2b4d389ada9701
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/column-store-tables-management.md
@@ -0,0 +1,386 @@
+---
+title: Column-store Tables Management
+summary: Column-store Tables Management
+author: Guo Huan
+date: 2021-04-09
+---
+
+# Column-store Tables Management
+
+## What is Column-store
+
+Row-store stores tables to disk partitions by row, and column-store stores tables to disk partitions by column. By default, a row-store table is created. For details about differences between row storage and column storage, see Figure 1.
+
+**Figure 1** Differences between row storage and column storage
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/column-store-tables-management.png)
+
+In the preceding figure, the upper left part is a row-store table, and the upper right part shows how the row-store table is stored on a disk; the lower left part is a column-store table, and the lower right part shows how the column-store table is stored on a disk. From the above figure, you can clearly see that the data of a row-store table are put together, but they are kept separately in column-store table.
+
+## Advantages and Disadvantages of Row-store and Column-store Tables and Their Usage Scenario
+
+Both storage models have benefits and drawbacks.
+
+| Storage Model  | Benefit                                                      | Drawback                                                     |
+| :------------- | :----------------------------------------------------------- | :----------------------------------------------------------- |
+| Row storage    | Record data is stored together. Data can be easily inserted and updated. | All the columns of a record are read after the **SELECT** statement is executed even if only certain columns are required. |
+| Column storage | Only the columns involved in a query are read. Projections are efficient. Any column can serve as an index. | The selected columns need to be reconstructed after the **SELECT** statement is executed. Data cannot be easily inserted or updated. |
+
+Generally, if a table contains many columns (called a wide table) and its query involves only a few columns, column storage is recommended. Row storage is recommended if a table contains only a few columns and a query involves most of the fields.
+
+| Storage Model  | Application Scenarios                                        |
+| :------------- | :----------------------------------------------------------- |
+| Row storage    | Point queries (simple index-based queries that only return a few records)Scenarios requiring frequent addition, deletion, and modification |
+| Column storage | Statistical analysis queries (requiring a large number of association and grouping operations)Ad hoc queries (using uncertain query conditions and unable to utilize indexes to scan row-store tables) |
+
+MogDB supports hybrid row storage and column storage. Each storage model applies to specific scenarios. Select an appropriate model when creating a table. Generally, MogDB is used for transactional processing databases. By default, row storage is used. Column storage is used only when complex queries in large data volume are performed.
+
+## Selecting a Storage Model
+
+- Update frequency
+
+  If data is frequently updated, use a row-store table.
+
+- Data insertion frequency
+
+  If a small amount of data is frequently inserted each time, use a row-store table.
+
+- Number of columns
+
+  If a table is to contain many columns, use a column-store table.
+
+- Number of columns to be queried
+
+  If only a small number of columns (less than 50% of the total) is queried each time, use a column-store table.
+
+- Compression ratio
+
+  The compression ratio of a column-store table is higher than that of a row-store table. High compression ratio consumes more CPU resources.
+
+## Constraints of Column-store Table
+
+- The column-store table does not support arrays.
+- The number of column-store tables is recommended to be no more than 1000.
+- The table-level constraints of the column-store table only support **PARTIAL CLUSTER KEY**, and do not support table-level constraints such as primary and foreign keys.
+- The field constraints of the column-store table only support **NULL**, **NOT NULL** and **DEFAULT** constant values.
+- The column-store table does not support the **alter** command to modify field constraints.
+- The column-store table supports the delta table, which is controlled by the parameter **enable_delta_store** whether to enable or not, and the threshold value for entering the delta table is controlled by the parameter **deltarow_threshold**.
+
+## Related Parameters
+
+- cstore_buffers
+
+  The size of the shared buffer used by the column-store, the default value: 32768KB.
+
+- partition_mem_batch
+
+  Specify the number of caches. In order to optimize the batch insertion of column-store partition tables, the data will be cached during the batch insertion process and then written to disk in batches. Default value: 256.
+
+- partition_max_cache_size
+
+  Specify the size of the data buffer area. In order to optimize the batch insertion of column-store partition tables, the data will be cached during the batch insertion process and then written to disk in batches. Default value: 2GB.
+
+- enable_delta_store
+
+  In order to enhance the performance of single data import in column-store and solve the problem of disk redundancy, whether it is necessary to enable the function of column-store delta table and use it in conjunction with the parameter **DELTAROW_THRESHOLD**. Default value: off.
+
+## Create Table Commands
+
+MogDB creates normal tables as uncompressed row-store tables by default.
+
+```
+mogdb=# \dt
+No relations found.
+mogdb=# create table test_t(id serial primary key ,col1 varchar(8),col2 decimal(6,2),create_time timestamptz not null default now());
+NOTICE:  CREATE TABLE will create implicit sequence "test_t_id_seq" for serial column "test_t.id"
+NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index "test_t_pkey" for table "test_t"
+CREATE TABLE
+mogdb=# \dt+
+                                     List of relations
+ Schema |  Name  | Type  | Owner |  Size   |             Storage              | Description
+--------+--------+-------+-------+---------+----------------------------------+-------------
+ public | test_t | table | omm   | 0 bytes | {orientation=row,compression=no} |
+(1 row)
+
+mogdb=#
+```
+
+To create a column-store table, you need to specify **orientation=column**, the default compression level is **low**.
+
+```
+mogdb=# create table column_t(id serial,col1 varchar(8),col2 decimal(6,2),create_time timestamptz not null default now()) with (orientation=column );
+NOTICE:  CREATE TABLE will create implicit sequence "column_t_id_seq" for serial column "column_t.id"
+CREATE TABLE
+mogdb=# \dt+
+                                        List of relations
+ Schema |   Name   | Type  | Owner |  Size   |               Storage                | Description
+--------+----------+-------+-------+---------+--------------------------------------+-------------
+ public | column_t | table | omm   | 16 kB   | {orientation=column,compression=low} |
+ public | test_t   | table | omm   | 0 bytes | {orientation=row,compression=no}     |
+(2 rows)
+
+mogdb=# \d+ column_t
+                                                        Table "public.column_t"
+   Column    |           Type           |                       Modifiers                       | Storage  | Stats target | Description
+-------------+--------------------------+-------------------------------------------------------+----------+--------------+-------------
+ id          | integer                  | not null default nextval('column_t_id_seq'::regclass) | plain    |              |
+ col1        | character varying(8)     |                                                       | extended |              |
+ col2        | numeric(6,2)             |                                                       | main     |              |
+ create_time | timestamp with time zone | not null default now()                                | plain    |              |
+Has OIDs: no
+Options: orientation=column, compression=low
+```
+
+Add partial clustered storage columns to the column-store table.
+
+```
+mogdb=# \d+ column_t
+                                                        Table "public.column_t"
+   Column    |           Type           |                       Modifiers                       | Storage  | Stats target | Description
+-------------+--------------------------+-------------------------------------------------------+----------+--------------+-------------
+ id          | integer                  | not null default nextval('column_t_id_seq'::regclass) | plain    |              |
+ col1        | character varying(8)     |                                                       | extended |              |
+ col2        | numeric(6,2)             |                                                       | main     |              |
+ create_time | timestamp with time zone | not null default now()                                | plain    |              |
+Has OIDs: no
+Options: orientation=column, compression=low
+
+mogdb=# alter table column_t add PARTIAL CLUSTER KEY(id);
+ALTER TABLE
+mogdb=# \d+ column_t
+                                                        Table "public.column_t"
+   Column    |           Type           |                       Modifiers                       | Storage  | Stats target | Description
+-------------+--------------------------+-------------------------------------------------------+----------+--------------+-------------
+ id          | integer                  | not null default nextval('column_t_id_seq'::regclass) | plain    |              |
+ col1        | character varying(8)     |                                                       | extended |              |
+ col2        | numeric(6,2)             |                                                       | main     |              |
+ create_time | timestamp with time zone | not null default now()                                | plain    |              |
+Partial Cluster :
+    "column_t_cluster" PARTIAL CLUSTER KEY (id)
+Has OIDs: no
+Options: orientation=column, compression=low
+
+mogdb=#
+```
+
+Create column-store tables with partial clustered storage directly.
+
+```
+mogdb=# create table column_c(id serial,col1 varchar(8),col2 decimal(6,2),create_time timestamptz not null default now(),PARTIAL CLUSTER KEY(id)) with (orientation=column );
+NOTICE:  CREATE TABLE will create implicit sequence "column_c_id_seq" for serial column "column_c.id"
+CREATE TABLE
+mogdb=# \d+ column_c
+                                                        Table "public.column_c"
+   Column    |           Type           |                       Modifiers                       | Storage  | Stats target | Description
+-------------+--------------------------+-------------------------------------------------------+----------+--------------+-------------
+ id          | integer                  | not null default nextval('column_c_id_seq'::regclass) | plain    |              |
+ col1        | character varying(8)     |                                                       | extended |              |
+ col2        | numeric(6,2)             |                                                       | main     |              |
+ create_time | timestamp with time zone | not null default now()                                | plain    |              |
+Partial Cluster :
+    "column_c_cluster" PARTIAL CLUSTER KEY (id)
+Has OIDs: no
+Options: orientation=column, compression=low
+
+mogdb=#
+```
+
+Please refer to **Supported Data Types** &gt; **Data Types Supported by Column-store Tables** under the **Reference Guide** for the data types supported by column-store tables.
+
+## Column-store versus Row-store
+
+**Used disk space**
+
+- The default size of the column-store table is 16K, the compression level is **low**.
+
+- The default size of the row-store table is 0bytes, the compression level is **no**.
+
+- Insert 1 million pieces of data into the two tables separately , and compare the occupied disk size.
+
+  ```
+  mogdb=# \dt+
+                                        List of relations
+  Schema |   Name    | Type  | Owner |  Size   |                 Storage                 | Description
+  --------+-----------+-------+-------+---------+-----------------------------------------+-------------
+  public | column_t  | table | omm   | 16 kB   | {orientation=column,compression=low}    |
+  public | column_th | table | omm   | 16 kB   | {orientation=column,compression=high}   |
+  public | column_tm | table | omm   | 16 kB   | {orientation=column,compression=middle} |
+  public | row_tc    | table | omm   | 0 bytes | {orientation=row,compression=yes}       |
+  public | test_t    | table | omm   | 0 bytes | {orientation=row,compression=no}        |
+  (5 rows)
+
+  mogdb=# insert into column_t select generate_series(1,1000000),left(md5(random()::text),8),random()::numeric(6,2);
+  INSERT 0 1000000
+  Time: 11328.880 ms
+  mogdb=# insert into column_th select generate_series(1,1000000),left(md5(random()::text),8),random()::numeric(6,2);
+  INSERT 0 1000000
+  Time: 10188.634 ms
+  mogdb=# insert into column_tm select generate_series(1,1000000),left(md5(random()::text),8),random()::numeric(6,2);
+  INSERT 0 1000000
+  Time: 9802.739 ms
+  mogdb=# insert into test_t select generate_series(1,1000000),left(md5(random()::text),8),random()::numeric(6,2);
+  INSERT 0 1000000
+  Time: 17404.945 ms
+  mogdb=# insert into row_tc select generate_series(1,1000000),left(md5(random()::text),8),random()::numeric(6,2);
+  INSERT 0 1000000
+  Time: 12394.866 ms
+  mogdb=# \dt+
+                                         List of relations
+  Schema |   Name    | Type  | Owner |   Size   |                 Storage                 | Description
+  --------+-----------+-------+-------+----------+-----------------------------------------+-------------
+  public | column_t  | table | omm   | 12 MB    | {orientation=column,compression=low}    |
+  public | column_th | table | omm   | 8304 kB  | {orientation=column,compression=high}   |
+  public | column_tm | table | omm   | 10168 kB | {orientation=column,compression=middle} |
+  public | row_tc    | table | omm   | 58 MB    | {orientation=row,compression=yes}       |
+  public | test_t    | table | omm   | 58 MB    | {orientation=row,compression=no}        |
+  (5 rows)
+
+  mogdb=#
+  ```
+
+- The higher the compression level of the column-store table is, the less the disk space it uses.
+
+- After the row-store table is compressed, the size of the disk space dose not decrease significantly.
+
+- Column-store table take up nearly 6 times less disk space than row-store table.
+
+**DML Comparison**
+
+Search for a single column:
+
+```
+---
+---Search by range, column-store is nearly 20 times faster than row-store
+---
+mogdb=# select col1 from test_t where id>=100010 and id<100020;
+   col1
+----------
+ 4257a3f3
+ 3d397284
+ 64343438
+ 6eb7bdb7
+ d1c9073d
+ 6aeb037c
+ 1d424974
+ 223235ab
+ 329de235
+ 2f02adc1
+(10 rows)
+
+Time: 77.341 ms
+mogdb=# select col1 from column_t where id>=100010 and id<100020;
+   col1
+----------
+ d4837c30
+ 87a46f7a
+ 2f42a9c9
+ 4481c793
+ 68800204
+ 613b9205
+ 9d8f4a0a
+ 5cc4ff9e
+ f948cd10
+ f2775cee
+(10 rows)
+
+Time: 3.884 ms
+
+---
+---Search Randomly, column-store is nearly 35 times faster than row-store
+---
+
+mogdb=# select col1 from test_t limit 10;
+   col1
+----------
+ c2780d93
+ 294be14d
+ 4e53b761
+ 2c10f8a2
+ ae776743
+ 7d683c66
+ b3b40054
+ 7e56edf9
+ a7b7336e
+ ea3d47d9
+(10 rows)
+
+Time: 249.887 ms
+mogdb=# select col1 from column_t limit 10;
+   col1
+----------
+ a745d77b
+ 4b6df494
+ 76fed9c1
+ 70c9664d
+ 3384de8a
+ 4158f3bf
+ 5d1c3b9f
+ 341876bb
+ f396f4ed
+ abfd78bb
+(10 rows)
+
+Time: 7.738 ms
+```
+
+Search for all the data:
+
+```
+---
+---Row-store is 30% faster than column-store search
+---
+mogdb=# select * from test_t limit 10;
+ id |   col1   | col2 |          create_time
+----+----------+------+-------------------------------
+  1 | c2780d93 |  .37 | 2020-10-26 14:27:33.304108+08
+  2 | 294be14d |  .57 | 2020-10-26 14:27:33.304108+08
+  3 | 4e53b761 |  .98 | 2020-10-26 14:27:33.304108+08
+  4 | 2c10f8a2 |  .27 | 2020-10-26 14:27:33.304108+08
+  5 | ae776743 |  .97 | 2020-10-26 14:27:33.304108+08
+  6 | 7d683c66 |  .58 | 2020-10-26 14:27:33.304108+08
+  7 | b3b40054 |  .44 | 2020-10-26 14:27:33.304108+08
+  8 | 7e56edf9 |  .43 | 2020-10-26 14:27:33.304108+08
+  9 | a7b7336e |  .31 | 2020-10-26 14:27:33.304108+08
+ 10 | ea3d47d9 |  .42 | 2020-10-26 14:27:33.304108+08
+(10 rows)
+
+Time: 6.822 ms
+
+mogdb=# select * from column_t limit 10;
+ id |   col1   | col2 |          create_time
+----+----------+------+-------------------------------
+  1 | a745d77b |  .33 | 2020-10-26 14:28:20.633253+08
+  2 | 4b6df494 |  .42 | 2020-10-26 14:28:20.633253+08
+  3 | 76fed9c1 |  .73 | 2020-10-26 14:28:20.633253+08
+  4 | 70c9664d |  .74 | 2020-10-26 14:28:20.633253+08
+  5 | 3384de8a |  .48 | 2020-10-26 14:28:20.633253+08
+  6 | 4158f3bf |  .59 | 2020-10-26 14:28:20.633253+08
+  7 | 5d1c3b9f |  .63 | 2020-10-26 14:28:20.633253+08
+  8 | 341876bb |  .97 | 2020-10-26 14:28:20.633253+08
+  9 | f396f4ed |  .73 | 2020-10-26 14:28:20.633253+08
+ 10 | abfd78bb |  .30 | 2020-10-26 14:28:20.633253+08
+(10 rows)
+
+Time: 9.982 ms
+```
+
+Update data:
+
+```
+---
+---Update a field directly, column-store is nearly 7 times faster than row-store
+---
+mogdb=# update test_t set col1=col1;
+UPDATE 1000000
+Time: 19779.978 ms
+mogdb=# update column_t set col1=col1;
+UPDATE 1000000
+Time: 2702.339 ms
+```
+
+## Conclusion
+
+1. The Column-store table saves nearly 6 times the disk space usage compared to the row-store table.
+2. When searching for the specified field,  the column-store table is about 20-35 times faster than the row-store table.
+3. When searching for all the data, the column-store table is 30% slower than the row-store table.
+4. When importing data in batches in the default compression mode, and column-store table is 40% faster than the row-store table.
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/exporting-data/1-using-gs_dump-and-gs_dumpall-to-export-data-overview.md b/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/exporting-data/1-using-gs_dump-and-gs_dumpall-to-export-data-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..3ade33a59d28689d3b013c72729a7e9cb0659501
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/exporting-data/1-using-gs_dump-and-gs_dumpall-to-export-data-overview.md
@@ -0,0 +1,91 @@
+---
+title: Using gs_dump and gs_dumpall to Export Data Overview
+summary: Using gs_dump and gs_dumpall to Export Data Overview
+author: Guo Huan
+date: 2021-03-04
+---
+
+# Using gs_dump and gs_dumpall to Export Data Overview
+
+MogDB provides **gs_dump** and **gs_dumpall** to export required database objects and related information. You can use a tool to import the exported data to a target database for database migration. **gs_dump** exports a single database or its objects. **gs_dumpall** exports all databases or global objects in MogDB. For details, see [Table 1](#Scenarios).
+
+**Table 1** Scenarios<a id="Scenarios"> </a>
+
+<table>
+    <tr>
+        <th>Application Scenario</th>
+        <th>Export Granularity</th>
+        <th>Export Format</th>
+        <th>Import Method</th>
+    </tr>
+    <tr>
+        <td rowspan="3">Exporting a single database</td>
+        <td>Database-level export<br/>
+            - Export full information of a cluster.<br/>You can use the exported information to create a database containing the same data as the current one.<br/>
+            - Export all object definitions of a database, including the definitions of the database, functions, schemas, tables, indexes, and stored procedures.
+            <br/>You can use the exported object definitions to quickly create a database that is the same as the current one, except that the new database does not have data.<br/>
+            - Export data of a cluster.</td>
+        <td rowspan="3">
+            - Plaintext<br/>
+            - Custom<br/>
+            - Directory<br/>
+            - .tar
+        </td>
+        <td rowspan="3">
+            - For details about how to import data files in text format, see Using a gsql Meta-Command to Import Data.<br/>
+            - For details about how to import data files in .tar, directory, or custom format, see Using gs_restore to Import Data.</td>
+    </tr>
+    <tr>
+        <td>Schema-level export<br/>
+            - Export full information of a schema.<br/>
+            - Export data of a schema.<br/>
+            - Export all object definitions of a schema, including the definitions of tables, stored procedures, and indexes.
+        </td>
+    </tr>
+    <tr>
+        <td>Table-level export<br/>
+            - Export full information of a table.<br/>
+            - Export data of a table.<br/>
+            - Export the definition of a table.
+        </td>
+    </tr>
+    <tr>
+        <td rowspan="2">Exporting all databases</td>
+        <td>Database-level export<br/>
+            - Export full information of a cluster.<br/>You can use the exported information to create a host environment containing the same databases, global objects, and data as the current one.<br/>
+            - Export all object definitions of a database, including the definitions of tablespaces, databases, functions, schemas, tables, indexes, and stored procedures.<br/>
+            You can use the exported object definitions to quickly create a host environment that is the same as the current one, containing the same databases and tablespaces but no data.<br/>
+            - Export data only.</td>
+        <td rowspan="2">Plaintext</td>
+        <td rowspan="2">For details about how to import data files, see Using a gsql Meta-Command to Import Data.</td>
+    </tr>
+    <tr>
+        <td>Global object export<br/>
+- Export tablespaces.<br/>
+- Export roles.<br/>
+- Export tablespaces and roles.</td>
+    </tr>
+</table>
+
+**gs_dump** and **gs_dumpall** use **-U** to specify the user that performs the export. If the specified user does not have the required permissions, data cannot be exported. In this case, you can set **-role** in the **gs_dump** or **gs_dumpall** command to the role that has the permissions. Then, **gs_dump** or **gs_dumpall** uses the specified role to export data. See Table 1 for application scenarios and [Data Export By a User Without Required Permissions](4-data-export-by-a-user-without-required-permissions) for operation details.
+
+**gs_dump** and **gs_dumpall** encrypt the exported data files. These files are decrypted before being imported. In this way, data disclosure is prevented, protecting database security.
+
+When **gs_dump** or **gs_dumpall** is used to export data from a cluster, other users can still access (read and write) databases in MogDB.
+
+**gs_dump** and **gs_dumpall** can export complete, consistent data. For example, if **gs_dump** is executed to export database A or **gs_dumpall** is executed to export all databases from MogDB at T1, data of database A or all databases in MogDB at that time point will be exported, and modifications on the databases after that time point will not be exported.
+
+**Precautions**
+
+- Do not modify an exported file or its content. Otherwise, restoration may fail.
+
+- If there are more than 500,000 objects (data tables, views, and indexes) in a database, you are advised to use **gs_guc** to set the following parameters for database nodes. This operation is not required if the parameter values are greater than the recommended ones.
+
+  ```bash
+  gs_guc set -N all -I all -c 'max_prepared_transactions = 1000'
+  gs_guc set -N all -I all -c 'max_locks_per_transaction = 512'
+  ```
+
+- For data consistency and integrity, **gs_dump** and **gs_dumpall** set a share lock for a table to dump. If a share lock has been set for the table in other transactions, **gs_dump** and **gs_dumpall** lock the table after it is released. If the table cannot be locked within the specified time, the dump fails. You can customize the timeout duration to wait for lock release by specifying the **-lock-wait-timeout** parameter.
+
+- During an export, **gs_dumpall** reads all tables in a database. Therefore, you need to connect to the database as a MogDB administrator to export a complete file. When you use **gsql** to execute SQL scripts, cluster administrator permissions are also required to add users and user groups, and create databases.
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/exporting-data/2-exporting-a-single-database.md b/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/exporting-data/2-exporting-a-single-database.md
new file mode 100644
index 0000000000000000000000000000000000000000..39539c96601eae9d7485f4f1a2209c868ce8f20d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/exporting-data/2-exporting-a-single-database.md
@@ -0,0 +1,288 @@
+---
+title: Exporting a Single Database
+summary: Exporting a Single Database
+author: Guo Huan
+date: 2021-03-04
+---
+
+# Exporting a Single Database
+
+## Exporting a Database
+
+You can use **gs_dump** to export data and all object definitions of a database from MogDB. You can specify the information to export as follows:
+
+- Export full information of a database, including its data and all object definitions.
+
+  You can use the exported information to create a database containing the same data as the current one.
+
+- Export all object definitions of a database, including the definitions of the database, functions, schemas, tables, indexes, and stored procedures.
+
+  You can use the exported object definitions to quickly create a database that is the same as the current one, except that the new database does not have data.
+
+- Export data of a database.
+
+### Procedure
+
+1. Log in as the OS user **omm** to the primary node of the database.
+
+2. Use **gs_dump** to export data of the **userdatabase** database.
+
+   ```bash
+   gs_dump -U jack -f /home/omm/backup/userdatabase_backup.tar -p 8000 postgres -F t
+   Password:
+   ```
+
+   **Table 1** Common parameters
+
+   | Parameter | Description                                                  | Example Value                               |
+   | :-------- | :----------------------------------------------------------- | :------------------------------------------ |
+   | -U        | Username for database connection.<br/>NOTE:<br/>If the username is not specified, the initial system administrator created during installation is used for connection by default. | -U jack                                     |
+   | -W        | User password for database connection.<br/>- This parameter is not required for database administrators if the trust policy is used for authentication.<br/>- If you connect to the database without specifying this parameter and you are not a database administrator, you will be prompted to enter the password. | -W abcd@123                                 |
+   | -f        | Folder to store exported files. If this parameter is not specified, the exported files are stored in the standard output. | -f /home/omm/backup/**postgres**_backup.tar |
+   | -p        | TCP port or local Unix-domain socket file extension on which the server is listening for connections. | -p 8000                                     |
+   | dbname    | Name of the database to export.                              | postgres                                    |
+   | -F        | Select the format of file to export. The values of **-F** are as follows:<br/>- **p**: plaintext<br/>- **c**: custom<br/>- **d**: directory<br/>- **t**: .tar | -F t                                        |
+
+   For details about other parameters, see "Tool Reference > Server Tools > [gs_dump](5-gs_dump)" in the **Reference Guide**.
+
+### Examples
+
+Example 1: Run **gs_dump** to export full information of the **postgres** database. The exported files are in .sql format.
+
+```bash
+gs_dump -f /home/omm/backup/postgres_backup.sql -p 8000 postgres -F p
+Password:
+gs_dump[port='8000'][postgres][2017-07-21 15:36:13]: dump database postgres successfully
+gs_dump[port='8000'][postgres][2017-07-21 15:36:13]: total time: 3793  ms
+```
+
+Example 2: Run **gs_dump** to export data of the **postgres** database, excluding object definitions. The exported files are in a custom format.
+
+```bash
+gs_dump -f /home/omm/backup/postgres_data_backup.dmp -p 8000 postgres -a -F c
+Password:
+gs_dump[port='8000'][postgres][2017-07-21 15:36:13]: dump database postgres successfully
+gs_dump[port='8000'][postgres][2017-07-21 15:36:13]: total time: 3793  ms
+```
+
+Example 3: Run **gs_dump** to export object definitions of the **postgres** database. The exported files are in .sql format.
+
+```bash
+gs_dump -f /home/omm/backup/postgres_def_backup.sql -p 8000 postgres -s -F p
+Password:
+gs_dump[port='8000'][postgres][2017-07-20 15:04:14]: dump database postgres successfully
+gs_dump[port='8000'][postgres][2017-07-20 15:04:14]: total time: 472 ms
+```
+
+Example 4: Run **gs_dump** to export object definitions of the **postgres** database. The exported files are in text format and are encrypted.
+
+```bash
+gs_dump -f /home/omm/backup/postgres_def_backup.sql -p 8000 postgres --with-encryption AES128 --with-key 1234567812345678 -s -F p
+Password:
+gs_dump[port='8000'][postgres][2018-11-14 11:25:18]: dump database postgres successfully
+gs_dump[port='8000'][postgres][2018-11-14 11:25:18]: total time: 1161  ms
+```
+
+## Exporting a Schema
+
+You can use **gs_dump** to export data and all object definitions of a schema from MogDB. You can export one or more specified schemas as needed. You can specify the information to export as follows:
+
+- Export full information of a schema, including its data and object definitions.
+- Export data of a schema, excluding its object definitions.
+- Export the object definitions of a schema, including the definitions of tables, stored procedures, and indexes.
+
+### Procedure
+
+1. Log in as the OS user **omm** to the primary node of the database.
+
+2. Run **gs_dump** to export the **hr** and **public** schemas.
+
+   ```bash
+   gs_dump -W Bigdata@123 -U jack -f /home/omm/backup/MPPDB_schema_backup -p 8000 human_resource -n hr -n public -F d
+   ```
+
+   **Table 1** Common parameters
+
+   | Parameter | Description                                                  | Example Value                                                |
+   | :-------- | :----------------------------------------------------------- | :----------------------------------------------------------- |
+   | -U        | Username for database connection.                            | -U jack                                                      |
+   | -W        | User password for database connection.<br/>- This parameter is not required for database administrators if the trust policy is used for authentication.<br/>- If you connect to the database without specifying this parameter and you are not a database administrator, you will be prompted to enter the password. | -W Bigdata@123                                               |
+   | -f        | Folder to store exported files. If this parameter is not specified, the exported files are stored in the standard output. | -f /home/omm/backup/MPPDB*_*schema_backup                    |
+   | -p        | TCP port or local Unix-domain socket file extension on which the server is listening for connections. | -p 8000                                                      |
+   | dbname    | Name of the database to export.                              | human_resource                                               |
+   | -n        | Names of schemas to export. Data of the specified schemas will also be exported.<br/>- Single schema: Enter **-n** **schemaname**.<br/>- Multiple schemas: Enter **-n** **schemaname** for each schema. | - Single schemas:**-n hr**<br/>- Multiple schemas:**-n hr -n public** |
+   | -F        | Select the format of file to export. The values of **-F** are as follows:<br/>- **p**: plaintext<br/>- **c**: custom<br/>- **d**: directory<br/>- **t**: .tar | -F d                                                         |
+
+   For details about other parameters, see "Tool Reference > Server Tools > [gs_dump](5-gs_dump)" in the **Reference Guide**.
+
+### Examples
+
+Example 1: Run **gs_dump** to export full information of the **hr** schema. The exported files stored in text format.
+
+```bash
+gs_dump -W Bigdata@123 -f /home/omm/backup/MPPDB_schema_backup.sql -p 8000 human_resource -n hr -F p
+gs_dump[port='8000'][human_resource][2017-07-21 16:05:55]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2017-07-21 16:05:55]: total time: 2425  ms
+```
+
+Example 2: Run **gs_dump** to export data of the **hr** schema. The exported files are in .tar format.
+
+```bash
+gs_dump -W Bigdata@123 -f /home/omm/backup/MPPDB_schema_data_backup.tar -p 8000 human_resource -n hr -a -F t
+gs_dump[port='8000'][human_resource][2018-11-14 15:07:16]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2018-11-14 15:07:16]: total time: 1865  ms
+```
+
+Example 3: Run **gs_dump** to export the object definitions of the **hr** schema. The exported files are stored in a directory.
+
+```bash
+gs_dump -W Bigdata@123 -f /home/omm/backup/MPPDB_schema_def_backup -p 8000 human_resource -n hr -s -F d
+gs_dump[port='8000'][human_resource][2018-11-14 15:11:34]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2018-11-14 15:11:34]: total time: 1652  ms
+```
+
+Example 4: Run **gs_dump** to export the **human_resource** database excluding the **hr** schema. The exported files are in a custom format.
+
+```bash
+gs_dump -W Bigdata@123 -f /home/omm/backup/MPPDB_schema_backup.dmp -p 8000 human_resource -N hr -F c
+gs_dump[port='8000'][human_resource][2017-07-21 16:06:31]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2017-07-21 16:06:31]: total time: 2522  ms
+```
+
+Example 5: Run **gs_dump** to export the object definitions of the **hr** and **public** schemas. The exported files are in .tar format.
+
+```bash
+gs_dump -W Bigdata@123 -f /home/omm/backup/MPPDB_schema_backup1.tar -p 8000 human_resource -n hr -n public -s -F t
+gs_dump[port='8000'][human_resource][2017-07-21 16:07:16]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2017-07-21 16:07:16]: total time: 2132  ms
+```
+
+Example 6: Run **gs_dump** to export the **human_resource** database excluding the **hr** and **public** schemas. The exported files are in a custom format.
+
+```bash
+gs_dump -W Bigdata@123 -f /home/omm/backup/MPPDB_schema_backup2.dmp -p 8000 human_resource -N hr -N public -F c
+gs_dump[port='8000'][human_resource][2017-07-21 16:07:55]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2017-07-21 16:07:55]: total time: 2296  ms
+```
+
+Example 7: Run **gs_dump** to export all tables (views, sequences, and foreign tables are also included) in the **public** schema and the **staffs** table in the **hr** schema, including data and table definition. The exported files are in a custom format.
+
+```bash
+gs_dump -W Bigdata@123 -f /home/omm/backup/MPPDB_backup3.dmp -p 8000 human_resource -t public.* -t hr.staffs -F c
+gs_dump[port='8000'][human_resource][2018-12-13 09:40:24]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2018-12-13 09:40:24]: total time: 896  ms
+```
+
+## Exporting a Table
+
+You can use **gs_dump** to export data and definition of a table-level object from MogDB. Views, sequences, and foreign tables are special tables. You can export one or more specified tables as needed. You can specify the information to export as follows:
+
+- Export full information of a table, including its data and definition.
+- Export data of a table.
+- Export the definition of a table.
+
+### Procedure
+
+1. Log in as the OS user **omm** to the primary node of the database.
+
+2. Run **gs_dump** to export the **hr.staffs** and **hr.employments** tables.
+
+   ```bash
+   gs_dump -W Bigdata@123 -U jack -f /home/omm/backup/MPPDB_table_backup -p 8000 human_resource -t hr.staffs -t hr.employments -F d
+   ```
+
+   **Table 1** Common parameters
+
+   | Parameter | Description                                                  | Example Value                                                |
+   | :-------- | :----------------------------------------------------------- | :----------------------------------------------------------- |
+   | -U        | Username for database connection.                            | -U jack                                                      |
+   | -W        | User password for database connection.<br/>- This parameter is not required for database administrators if the trust policy is used for authentication.<br/>- If you connect to the database without specifying this parameter and you are not a database administrator, you will be prompted to enter the password. | -W Bigdata@123                                               |
+   | -f        | Folder to store exported files. If this parameter is not specified, the exported files are stored in the standard output. | -f /home/omm/backup/MPPDB_table_backup                       |
+   | -p        | TCP port or local Unix-domain socket file extension on which the server is listening for connections. | -p 8000                                                      |
+   | dbname    | Name of the database to export.                              | human_resource                                               |
+   | -t        | Table (or view, sequence, foreign table) to export. You can specify multiple tables by listing them or using wildcard characters. When you use wildcard characters, quote wildcard patterns with single quotation marks (") to prevent the shell from expanding the wildcard characters.<br/>- Single table: Enter **-t** **schema.table**.<br/>- Multiple tables: Enter **-t** **schema.table** for each table. | - Single table: **-t hr.staffs**<br/>- **Multiple tables:**-t hr.staffs -t hr.employments** |
+   | -F        | Select the format of file to export. The values of **-F** are as follows:<br/>- **p**: plaintext<br/>- **c**: custom<br/>- **d**: directory<br/>- **t**: .tar | -F d                                                         |
+
+   For details about other parameters, see "Tool Reference > Server Tools > [gs_dump](5-gs_dump)" in the **Reference Guide**.
+
+### Examples
+
+Example 1: Run **gs_dump** to export full information of the **hr.staffs** table. The exported files are in text format.
+
+```bash
+gs_dump -W Bigdata@123 -f /home/omm/backup/MPPDB_table_backup.sql -p 8000 human_resource -t hr.staffs -F p
+gs_dump[port='8000'][human_resource][2017-07-21 17:05:10]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2017-07-21 17:05:10]: total time: 3116  ms
+```
+
+Example 2: Run **gs_dump** to export data of the **hr.staffs** table. The exported files are in .tar format.
+
+```bash
+gs_dump -W Bigdata@123 -f /home/omm/backup/MPPDB_table_data_backup.tar -p 8000 human_resource -t hr.staffs -a -F t
+gs_dump[port='8000'][human_resource][2017-07-21 17:04:26]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2017-07-21 17:04:26]: total time: 2570  ms
+```
+
+Example 3: Run **gs_dump** to export the definition of the **hr.staffs** table. The exported files are stored in a directory.
+
+```bash
+gs_dump -W Bigdata@123 -f /home/omm/backup/MPPDB_table_def_backup -p 8000 human_resource -t hr.staffs -s -F d
+gs_dump[port='8000'][human_resource][2017-07-21 17:03:09]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2017-07-21 17:03:09]: total time: 2297  ms
+```
+
+Example 4: Run **gs_dump** to export the **human_resource** database excluding the **hr.staffs** table. The exported files are in a custom format.
+
+```bash
+gs_dump -W Bigdata@123 -f /home/omm/backup/MPPDB_table_backup4.dmp -p 8000 human_resource -T hr.staffs -F c
+gs_dump[port='8000'][human_resource][2017-07-21 17:14:11]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2017-07-21 17:14:11]: total time: 2450  ms
+```
+
+Example 5: Run **gs_dump** to export the **hr.staffs** and **hr.employments** tables. The exported files are in text format.
+
+```bash
+gs_dump -W Bigdata@123 -f /home/omm/backup/MPPDB_table_backup1.sql -p 8000 human_resource -t hr.staffs -t hr.employments -F p
+gs_dump[port='8000'][human_resource][2017-07-21 17:19:42]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2017-07-21 17:19:42]: total time: 2414  ms
+```
+
+Example 6: Run **gs_dump** to export the **human_resource** database excluding the **hr.staffs** and **hr.employments** tables. The exported files are in text format.
+
+```bash
+gs_dump -W Bigdata@123 -f /home/omm/backup/MPPDB_table_backup2.sql -p 8000 human_resource -T hr.staffs -T hr.employments -F p
+gs_dump[port='8000'][human_resource][2017-07-21 17:21:02]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2017-07-21 17:21:02]: total time: 3165  ms
+```
+
+Example 7: Run **gs_dump** to export data and definition of the **hr.staffs** table, and the definition of the **hr.employments** table. The exported files are in .tar format.
+
+```bash
+gs_dump -W Bigdata@123 -f /home/omm/backup/MPPDB_table_backup3.tar -p 8000 human_resource -t hr.staffs -t hr.employments --exclude-table-data hr.employments -F t
+gs_dump[port='8000'][human_resource][2018-11-14 11:32:02]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2018-11-14 11:32:02]: total time: 1645  ms
+```
+
+Example 8: Run **gs_dump** to export data and definition of the **hr.staffs** table, encrypt the exported files, and store them in text format.
+
+```bash
+gs_dump -W Bigdata@123 -f /home/omm/backup/MPPDB_table_backup4.sql -p 8000 human_resource -t hr.staffs --with-encryption AES128 --with-key 1212121212121212 -F p
+gs_dump[port='8000'][human_resource][2018-11-14 11:35:30]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2018-11-14 11:35:30]: total time: 6708  ms
+```
+
+Example 9: Run **gs_dump** to export all tables (views, sequences, and foreign tables are also included) in the **public** schema and the **staffs** table in the **hr** schema, including data and table definition. The exported files are in a custom format.
+
+```bash
+gs_dump -W Bigdata@123 -f /home/omm/backup/MPPDB_table_backup5.dmp -p 8000 human_resource -t public.* -t hr.staffs -F c
+gs_dump[port='8000'][human_resource][2018-12-13 09:40:24]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2018-12-13 09:40:24]: total time: 896  ms
+```
+
+Example 10: Run **gs_dump** to export the definition of the view referencing to the **test1** table in the **t1** schema. The exported files are in a custom format.
+
+```bash
+gs_dump -W Bigdata@123 -U jack -f /home/omm/backup/MPPDB_view_backup6 -p 8000 human_resource -t t1.test1 --include-depend-objs --exclude-self -F d
+gs_dump[port='8000'][jack][2018-11-14 17:21:18]: dump database human_resource successfully
+gs_dump[port='8000'][jack][2018-11-14 17:21:23]: total time: 4239  ms
+```
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/exporting-data/3-exporting-all-databases.md b/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/exporting-data/3-exporting-all-databases.md
new file mode 100644
index 0000000000000000000000000000000000000000..f730f0f7e678147399fd673f96735af305fd20c6
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/exporting-data/3-exporting-all-databases.md
@@ -0,0 +1,121 @@
+---
+title: Exporting All Databases
+summary: Exporting All Databases
+author: Guo Huan
+date: 2021-03-04
+---
+
+# Exporting All Databases
+
+## Exporting All Databases
+
+You can use **gs_dumpall** to export full information of all databases in MogDB, including information about each database and global objects in MogDB. You can specify the information to export as follows:
+
+- Export full information of all databases, including information about each database and global objects (such as roles and tablespaces) in MogDB.
+
+  You can use the exported information to create a host environment containing the same databases, global objects, and data as the current one.
+
+- Export data of all databases, excluding all object definitions and global objects.
+
+- Export all object definitions of all databases, including the definitions of tablespaces, databases, functions, schemas, tables, indexes, and stored procedures.
+
+  You can use the exported object definitions to quickly create a host environment that is the same as the current one, containing the same databases and tablespaces but no data.
+
+### Procedure
+
+1. Log in as the OS user **omm** to the primary node of the database.
+
+2. Run **gs_dumpall** to export full information of all databases.
+
+   ```bash
+   gs_dumpall -W Bigdata@123 -U omm -f /home/omm/backup/MPPDB_backup.sql -p 8000
+   ```
+
+   **Table 1** Common parameters
+
+   | Parameter | Description                                                  | Example Value                        |
+   | :-------- | :----------------------------------------------------------- | :----------------------------------- |
+   | -U        | Username for database connection. The user must be an MogDB administrator. | -U omm                               |
+   | -W        | User password for database connection.<br/>- This parameter is not required for database administrators if the trust policy is used for authentication.<br/>- If you connect to the database without specifying this parameter and you are not a database administrator, you will be prompted to enter the password. | -W Bigdata@123                       |
+   | -f        | Folder to store exported files. If this parameter is not specified, the exported files are stored in the standard output. | -f /home/omm/backup/MPPDB_backup.sql |
+   | -p        | TCP port or local Unix-domain socket file extension on which the server is listening for connections. | -p 8000                              |
+
+   For details about other parameters, see "Tool Reference > Server Tools > [gs_dumpall](6-gs_dumpall)" in the **Reference Guide**.
+
+### Examples
+
+Example 1: Run **gs_dumpall** as the cluster administrator **omm** to export full information of all databases in a cluster. After the command is executed, a large amount of output information will be displayed. **total time** will be displayed at the end of the information, indicating that the backup is successful. In this example, only relative output information is included.
+
+```bash
+gs_dumpall -W Bigdata@123 -U omm -f /home/omm/backup/MPPDB_backup.sql -p 8000
+gs_dumpall[port='8000'][2017-07-21 15:57:31]: dumpall operation successful
+gs_dumpall[port='8000'][2017-07-21 15:57:31]: total time: 9627  ms
+```
+
+Example 2: Run **gs_dumpall** as the cluster administrator **omm** to export object definitions of all databases in a cluster. The exported files are in text format. After the command is executed, a large amount of output information will be displayed. **total time** will be displayed at the end of the information, indicating that the backup is successful. In this example, only relative output information is included.
+
+```bash
+gs_dumpall -W Bigdata@123 -U omm -f /home/omm/backup/MPPDB_backup.sql -p 8000 -s
+gs_dumpall[port='8000'][2018-11-14 11:28:14]: dumpall operation successful
+gs_dumpall[port='8000'][2018-11-14 11:28:14]: total time: 4147  ms
+```
+
+Example 3: Run **gs_dumpall** to export data of all databases in a cluster, encrypt the exported files, and store them in text format. After the command is executed, a large amount of output information will be displayed. **total time** will be displayed at the end of the information, indicating that the backup is successful. In this example, only relative output information is included.
+
+```bash
+gs_dumpall -f /home/omm/backup/MPPDB_backup.sql -p 8000 -a --with-encryption AES128 --with-key 1234567812345678
+gs_dumpall[port='8000'][2018-11-14 11:32:26]: dumpall operation successful
+gs_dumpall[port='8000'][2018-11-14 11:23:26]: total time: 4147  ms
+```
+
+## Exporting Global Objects
+
+You can use **gs_dumpall** to export global objects, including database users, user groups, tablespaces, and attributes (for example, global access permissions), from MogDB.
+
+### Procedure
+
+1. Log in as the OS user **omm** to the primary node of the database.
+
+2. Run **gs_dumpall** to export global tablespaces.
+
+   ```bash
+   gs_dumpall -W Bigdata@123 -U omm -f /home/omm/backup/MPPDB_tablespace.sql -p 8000 -t
+   ```
+
+   **Table 1** Common parameters
+
+   | Parameter | Description                                                  | Example Value                                |
+   | :-------- | :----------------------------------------------------------- | :------------------------------------------- |
+   | -U        | Username for database connection. The user must be an MogDB administrator. | -U omm                                       |
+   | -W        | User password for database connection.<br/>- This parameter is not required for database administrators if the trust policy is used for authentication.<br/>- If you connect to the database without specifying this parameter and you are not a database administrator, you will be prompted to enter the password. | -W Bigdata@123                               |
+   | -f        | Folder to store exported files. If this parameter is not specified, the exported files are stored in the standard output. | -f /home/omm/backup/**MPPDB_tablespace**.sql |
+   | -p        | TCP port or local Unix-domain socket file extension on which the server is listening for connections. | -p 8000                                      |
+   | -t        | Dumps only tablespaces. You can also use **-tablespaces-only** alternatively. | -                                            |
+
+   For details about other parameters, see "Tool Reference > Server Tools > [gs_dumpall](6-gs_dumpall)" in the **Reference Guide**.
+
+### Examples
+
+Example 1: Run **gs_dumpall** as the cluster administrator **omm** to export global tablespaces and users of all databases. The exported files are in text format.
+
+```bash
+gs_dumpall -W Bigdata@123 -U omm -f /home/omm/backup/MPPDB_globals.sql -p 8000 -g
+gs_dumpall[port='8000'][2018-11-14 19:06:24]: dumpall operation successful
+gs_dumpall[port='8000'][2018-11-14 19:06:24]: total time: 1150  ms
+```
+
+Example 2: Run **gs_dumpall** as the cluster administrator **omm** to export global tablespaces of all databases, encrypt the exported files, and store them in text format.
+
+```bash
+gs_dumpall -W Bigdata@123 -U omm -f /home/omm/backup/MPPDB_tablespace.sql -p 8000 -t --with-encryption AES128 --with-key 1212121212121212
+gs_dumpall[port='8000'][2018-11-14 19:00:58]: dumpall operation successful
+gs_dumpall[port='8000'][2018-11-14 19:00:58]: total time: 186  ms
+```
+
+Example 3: Run **gs_dumpall** as the cluster administrator **omm** to export global users of all databases. The exported files are in text format.
+
+```bash
+gs_dumpall -W Bigdata@123 -U omm -f /home/omm/backup/MPPDB_user.sql -p 8000 -r
+gs_dumpall[port='8000'][2018-11-14 19:03:18]: dumpall operation successful
+gs_dumpall[port='8000'][2018-11-14 19:03:18]: total time: 162  ms
+```
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/exporting-data/4-data-export-by-a-user-without-required-permissions.md b/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/exporting-data/4-data-export-by-a-user-without-required-permissions.md
new file mode 100644
index 0000000000000000000000000000000000000000..025caa51aa7788f04405068e20e3645c30191d42
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/exporting-data/4-data-export-by-a-user-without-required-permissions.md
@@ -0,0 +1,82 @@
+---
+title: Data Export By a User Without Required Permissions
+summary: Data Export By a User Without Required Permissions
+author: Guo Huan
+date: 2021-03-04
+---
+
+# Data Export By a User Without Required Permissions
+
+**gs_dump** and **gs_dumpall** use **-U** to specify the user that performs the export. If the specified user does not have the required permissions, data cannot be exported. In this case, you need to assign the permission to a user who does not have the permission, and then set the **-role** parameter in the export command to specify the role with the permission. Then, **gs_dump** or **gs_dumpall** uses the **-role** parameter to specify a role to export data.
+
+## Procedure
+
+1. Log in as the OS user **omm** to the primary node of the database.
+
+2. Use **gs_dump** to export data of the **human_resource** database.
+
+   User **jack** does not have the permissions to export data of the **human_resource** database and the role **role1** has this permission. To export data of the **human_resource** database, you need to assign the permission of **role1** to **jack** and set **-role** to **role1** in the export command. The exported files are in .tar format.
+
+   ```bash
+   gs_dump -U jack -f /home/omm/backup/MPPDB_backup.tar -p 8000 human_resource --role role1 --rolepassword  abc@1234 -F t
+   Password:
+   ```
+
+   **Table 1** Common parameters
+
+   | Parameter     | Description                                                  | Example Value                        |
+   | :------------ | :----------------------------------------------------------- | :----------------------------------- |
+   | -U            | Username for database connection.                            | -U jack                              |
+   | -W            | User password for database connection.<br/>- This parameter is not required for database administrators if the trust policy is used for authentication.<br/>- If you connect to the database without specifying this parameter and you are not a database administrator, you will be prompted to enter the password. | -W Bigdata@123                       |
+   | -f            | Folder to store exported files. If this parameter is not specified, the exported files are stored in the standard output. | -f /home/omm/backup/MPPDB_backup.tar |
+   | -p            | TCP port or local Unix-domain socket file extension on which the server is listening for connections. | -p 8000                              |
+   | dbname        | Name of the database to export.                              | human_resource                       |
+   | -role         | Role name for the export operation. After this parameter is set, the **SET ROLE** command will be issued after **gs_dump** or **gs_dumpall** connects to the database. It is useful when the user specified by **-U** does not have the permissions required by **gs_dump** or **gs_dumpall**. This parameter allows you to switch to a role with the required permissions. | -r role1                             |
+   | -rolepassword | Role password.                                               | -rolepassword abc@1234               |
+   | -F            | Select the format of file to export. The values of **-F** are as follows:<br/>- **p**: plaintext<br/>- **c**: custom<br/>- **d**: directory<br/>- **t**: .tar | -F t                                 |
+
+   For details about other parameters, see "Tool Reference > Server Tools > [gs_dump](5-gs_dump)" or "[gs_dumpall](6-gs_dumpall)" in the **Reference Guide**.
+
+## Examples
+
+Example 1: User **jack** does not have the permissions required to export data of the **human_resource** database using **gs_dump** and the role **role1** has the permissions. To export data of the **human_resource** database, you can set **-role** to **role1** in the **gs_dump** command. The exported files are in .tar format.
+
+```bash
+$ human_resource=# CREATE USER jack IDENTIFIED BY "1234@abc";
+CREATE ROLE
+human_resource=# GRANT role1 TO jack;
+GRANT ROLE
+
+$ gs_dump -U jack -f /home/omm/backup/MPPDB_backup11.tar -p 8000 human_resource --role role1 --rolepassword abc@1234 -F t
+Password:
+gs_dump[port='8000'][human_resource][2017-07-21 16:21:10]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2017-07-21 16:21:10]: total time: 4239  ms
+```
+
+Example 2: User **jack** does not have the permissions required to export the **public** schema using **gs_dump** and the role **role1** has the permissions. To export the **public** schema, you can set **-role** to **role1** in the **gs_dump** command. The exported files are in .tar format.
+
+```bash
+$ human_resource=# CREATE USER jack IDENTIFIED BY "1234@abc";
+CREATE ROLE
+human_resource=# GRANT role1 TO jack;
+GRANT ROLE
+
+$ gs_dump -U jack -f /home/omm/backup/MPPDB_backup12.tar -p 8000 human_resource -n public --role role1 --rolepassword abc@1234 -F t
+Password:
+gs_dump[port='8000'][human_resource][2017-07-21 16:21:10]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2017-07-21 16:21:10]: total time: 3278  ms
+```
+
+Example 3: User **jack** does not have the permissions required to export all databases in a cluster using **gs_dumpall** and the role **role1** (cluster administrator) has the permissions. To export all the databases, you can set **-role** to **role1** in the **gs_dumpall** command. The exported files are in text format.
+
+```bash
+$ human_resource=# CREATE USER jack IDENTIFIED BY "1234@abc";
+CREATE ROLE
+human_resource=# GRANT role1 TO jack;
+GRANT ROLE
+
+$ gs_dumpall -U jack -f /home/omm/backup/MPPDB_backup.sql -p 8000 --role role1 --rolepassword abc@1234
+Password:
+gs_dumpall[port='8000'][human_resource][2018-11-14 17:26:18]: dumpall operation successful
+gs_dumpall[port='8000'][human_resource][2018-11-14 17:26:18]: total time: 6437  ms
+```
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/1-import-modes.md b/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/1-import-modes.md
new file mode 100644
index 0000000000000000000000000000000000000000..db486ed377a2bcd89e66e9230e8246f825bea0f0
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/1-import-modes.md
@@ -0,0 +1,18 @@
+---
+title: Import Modes
+summary: Import Modes
+author: Guo Huan
+date: 2021-03-04
+---
+
+# Import Modes
+
+You can use **INSERT**, **COPY**, or **\copy** (a **gsql** meta-command) to import data to the MogDB database. The methods have different characteristics. For details, see Table 1.
+
+**Table 1** Import modes<a id="Import modes"> </a>
+
+| Mode                               | Characteristics                                              |
+| :--------------------------------- | :----------------------------------------------------------- |
+| INSERT                             | Insert one or more rows of data, or insert data from a specified table. |
+| COPY                               | Run the **COPY FROM STDIN** statement to write data into the MogDB database.<br/>Service data does not need to be stored in files when it is written from other databases to the MogDB database through the CopyManager interface driven by JDBC. |
+| **\copy**, a **gsql** meta-command | Different from the SQL **COPY** statement, the **\copy** command can read data from or write data into only local files on a **gsql** client.<br/>NOTE:<br/>**\copy** applies only to small-scale data import in good format. It does not preprocess invalid characters or provide error tolerance. Therefore, **\copy** cannot be used in scenarios where abnormal data exists. **COPY** is preferred for data import. |
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/10-managing-concurrent-write-operations.md b/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/10-managing-concurrent-write-operations.md
new file mode 100644
index 0000000000000000000000000000000000000000..5cd138eb7682d54bc9a971ad82b2a167dcd9eb39
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/10-managing-concurrent-write-operations.md
@@ -0,0 +1,177 @@
+---
+title: Managing Concurrent Write Operations
+summary: Managing Concurrent Write Operations
+author: Guo Huan
+date: 2021-03-04
+---
+
+# Managing Concurrent Write Operations
+
+## Transaction Isolation
+
+MogDB manages transactions based on MVCC and two-phase locks, avoiding conflicts between read and write operations. SELECT is a read-only operation, whereas UPDATE and DELETE are read/write operations.
+
+- There is no conflict between read/write and read-only operations, or between read/write operations. Each concurrent transaction creates a snapshot when it starts. Concurrent transactions cannot detect updates made by each other.
+  - At the **READ COMMITTED** level, if transaction T1 is committed, transaction T2 can see changes made by T1.
+  - At the **REPEATABLE READ** level, if T2 starts before T1 is committed, T2 will not see changes made by T1 even after T1 is committed. The query results in a transaction are consistent and unaffected by other transactions.
+- Read/Write operations use row-level locks. Different transactions can concurrently update the same table but not the same row. A row update transaction will start only after the previous one is committed.
+  - **READ COMMITTED**: At this level, a transaction can access only committed data. This is the default level.
+  - **REPEATABLE READ**: Only data committed before transaction start is read. Uncommitted data or data committed in other concurrent transactions cannot be read.
+
+## Write and Read/Write Operations
+
+Statements for write-only and read/write operations are as follows:
+
+- **INSERT**, used to insert one or more rows of data into a table
+- **UPDATE**, used to modify existing data in a table
+- **DELETE**, used to delete existing data from a table
+- **COPY**, used to import data
+
+INSERT and COPY are write-only operations. Only one of them can be performed at a time. If INSERT or COPY of transaction T1 locks a table, INSERT or COPY of transaction T2 needs to wait until T1 unlocks the table.
+
+UPDATE and DELETE operations are read/write operations. They need to query for the target rows before modifying data. Concurrent transactions cannot see changes made by each other, and UPDATE and DELETE operations read snapshots of data committed before their transactions start. Write operations use row-level locks. If T2 starts after T1 and is to update the same row as T1 does, T2 waits for T1 to finish update. If T1 is not complete within the specified timeout duration, T2 will time out. If T1 and T2 update different rows in a table, they can be concurrently executed.
+
+## Potential Deadlocks During Concurrent Write
+
+Whenever transactions involve updates of more than one table, there is always the possibility that concurrently running transactions become deadlocked when they both try to write to the same set of tables. A transaction releases all of its locks at once when it either commits or rolls back; it does not relinquish locks one at a time. For example, transactions T1 and T2 start at roughly the same time.
+
+- If T1 starts writing to table A and T2 starts writing to table B, both transactions can proceed without conflict. However, if T1 finishes writing to table A and needs to start writing to the same rows as T2 does in table B, it will not be able to proceed because T2 still holds the lock on B. Conversely, if T2 finishes writing to table B and needs to start writing to the same rows as T1 does in table A, it will not be able to proceed either because T1 still holds the lock on A. In this case, a deadlock occurs. If T1 is committed and releases the lock within the lock timeout duration, subsequent update can proceed. If a lock times out, an error is reported and the corresponding transaction exits.
+- If T1 updates rows 1 to 5 and T2 updates rows 6 to 10 in the same table, the two transactions do not conflict. However, if T1 finishes the update and proceeds to update rows 6 to 10, and T2 proceeds to update rows 1 to 5, neither of them can continue. If either of the transactions is committed and releases the lock within the lock timeout duration, subsequent update can proceed. If a lock times out, an error is reported and the corresponding transaction exits.
+
+## Concurrent Write Examples
+
+This section uses the **test** table as an example to describe how to perform concurrent **INSERT** and **DELETE** in the same table, concurrent **INSERT** in the same table, concurrent **UPDATE** in the same table, and concurrent import and queries.
+
+```sql
+CREATE TABLE test(id int, name char(50), address varchar(255));
+```
+
+### Concurrent INSERT and DELETE in the Same Table
+
+Transaction T1:
+
+```sql
+START TRANSACTION;
+INSERT INTO test VALUES(1,'test1','test123');
+COMMIT;
+```
+
+Transaction T2:
+
+```sql
+START TRANSACTION;
+DELETE test WHERE NAME='test1';
+COMMIT;
+```
+
+Scenario 1:
+
+T1 is started but not committed. At this time, T2 is started. After **INSERT** of T1 is complete, **DELETE** of T2 is performed. In this case, **DELETE 0** is displayed, because T1 is not committed and T2 cannot see the data inserted by T1.
+
+Scenario 2:
+
+- **READ COMMITTED** level
+
+  T1 is started but not committed. At this time, T2 is started. After **INSERT** of T1 is complete, T1 is committed and **DELETE** of T2 is executed. In this case, **DELETE 1** is displayed, because T2 can see the data inserted by T1.
+
+- **REPEATABLE READ** level
+
+  T1 is started but not committed. At this time, T2 is started. After **INSERT** of T1 is complete, T1 is committed and **DELETE** of T2 is executed. In this case, **DELETE 0** is displayed, because the data obtained in queries is consistent in a transaction.
+
+### Concurrent INSERT in the Same table
+
+Transaction T1:
+
+```sql
+START TRANSACTION;
+INSERT INTO test VALUES(2,'test2','test123');
+COMMIT;
+```
+
+Transaction T2:
+
+```sql
+START TRANSACTION;
+INSERT INTO test VALUES(3,'test3','test123');
+COMMIT;
+```
+
+Scenario 1:
+
+T1 is started but not committed. At this time, T2 is started. After **INSERT** of T1 is complete, **INSERT** of T2 is executed and succeeds. At the **READ COMMITTED** and **REPEATABLE READ** levels, the **SELECT** statement of T1 cannot see data inserted by T2, and a query in T2 cannot see data inserted by T1.
+
+Scenario 2:
+
+- **READ COMMITTED** level
+
+  T1 is started but not committed. At this time, T2 is started. After **INSERT** of T1 is complete, T1 is committed. In T2, a query executed after **INSERT** can see the data inserted by T1.
+
+- **REPEATABLE READ** level
+
+  T1 is started but not committed. At this time, T2 is started. After **INSERT** of T1 is complete, T1 is committed. In T2, a query executed after **INSERT** cannot see the data inserted by T1.
+
+### Concurrent UPDATE in the Same Table
+
+Transaction T1:
+
+```sql
+START TRANSACTION;
+UPDATE test SET address='test1234' WHERE name='test1';
+COMMIT;
+```
+
+Transaction T2:
+
+```sql
+START TRANSACTION;
+UPDATE test SET address='test1234' WHERE name='test2';
+COMMIT;
+```
+
+Transaction T3:
+
+```sql
+START TRANSACTION;
+UPDATE test SET address='test1234' WHERE name='test1';
+COMMIT;
+```
+
+Scenario 1:
+
+T1 is started but not committed. At this time, T2 is started. **UPDATE** of T1 and then T2 starts, and both of them succeed. This is because the **UPDATE** operations use row-level locks and do not conflict when they update different rows.
+
+Scenario 2:
+
+T1 is started but not committed. At this time, T3 is started. **UPDATE** of T1 and then T3 starts, and **UPDATE** of T1 succeeds. **UPDATE** of T3 times out. This is because T1 and T3 update the same row and the lock is held by T1 at the time of the update.
+
+### Concurrent Data Import and Queries
+
+Transaction T1:
+
+```sql
+START TRANSACTION;
+COPY test FROM '...';
+COMMIT;
+```
+
+Transaction T2:
+
+```sql
+START TRANSACTION;
+SELECT * FROM test;
+COMMIT;
+```
+
+Scenario 1:
+
+T1 is started but not committed. At this time, T2 is started. **COPY** of T1 and then **SELECT** of T2 starts, and both of them succeed. In this case, T2 cannot see the data added by **COPY** of T1.
+
+Scenario 2:
+
+- **READ COMMITTED** level
+
+  T1 is started but not committed. At this time, T2 is started. **COPY** of T1 is complete and T1 is committed. In this case, T2 can see the data added by **COPY** of T1.
+
+- **REPEATABLE READ** level
+
+  T1 is started but not committed. At this time, T2 is started. **COPY** of T1 is complete and T1 is committed. In this case, T2 cannot see the data added by **COPY** of T1.
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/2-running-the-INSERT-statement-to-insert-data.md b/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/2-running-the-INSERT-statement-to-insert-data.md
new file mode 100644
index 0000000000000000000000000000000000000000..9149247c9a26027cae83556801d74e8124cc959f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/2-running-the-INSERT-statement-to-insert-data.md
@@ -0,0 +1,20 @@
+---
+title: Running the INSERT Statement to Insert Data
+summary: Running the INSERT Statement to Insert Data
+author: Guo Huan
+date: 2021-03-04
+---
+
+# Running the INSERT Statement to Insert Data
+
+Run the **INSERT** statement to write data into the MogDB database in either of the following ways:
+
+- Use the client tool provided by the MogDB database to write data into MogDB.
+
+  For details, see Inserting Data to Tables.
+
+- Connect to the database using the JDBC or ODBC driver and run the **INSERT** statement to write data into the MogDB database.
+
+  For details, see Connecting to a Database.
+
+You can add, modify, and delete database transactions for the MogDB database. **INSERT** is the simplest way to write data and applies to scenarios with small data volume and low concurrency.
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/3-running-the-COPY-FROM-STDIN-statement-to-import-data.md b/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/3-running-the-COPY-FROM-STDIN-statement-to-import-data.md
new file mode 100644
index 0000000000000000000000000000000000000000..ba2053c3b65c3091c635a0aa28b0cdba6b3c339d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/3-running-the-COPY-FROM-STDIN-statement-to-import-data.md
@@ -0,0 +1,318 @@
+---
+title: Running the COPY FROM STDIN Statement to Import Data
+summary: Running the COPY FROM STDIN Statement to Import Data
+author: Guo Huan
+date: 2021-03-04
+---
+
+# Running the COPY FROM STDIN Statement to Import Data
+
+<br/>
+
+## Data Import Using COPY FROM STDIN
+
+Run the **COPY FROM STDIN** statement to import data to MogDB in either of the following ways:
+
+- Write data into the MogDB database by typing. For details, see COPY.
+- Import data from a file or database to MogDB through the CopyManager interface driven by JDBC. You can use any parameters in the **COPY** syntax.
+
+<br/>
+
+## Introduction to the CopyManager Class
+
+CopyManager is an API class provided by the JDBC driver in MogDB. It is used to import data to the MogDB database in batches.
+
+<br/>
+
+### Inheritance Relationship of CopyManager
+
+The CopyManager class is in the **org.postgresql.copy** package and inherits the java.lang.Object class. The declaration of the class is as follows:
+
+```java
+public class CopyManager
+extends Object
+```
+
+<br/>
+
+### Construction Method
+
+```java
+public CopyManager(BaseConnection connection)
+throws SQLException
+```
+
+<br/>
+
+### Common Methods
+
+**Table 1** Common methods of CopyManager
+
+| Return Value | Method                                               | Description                                                  | throws                   |
+| :----------- | :--------------------------------------------------- | :----------------------------------------------------------- | :----------------------- |
+| CopyIn       | copyIn(String sql)                                   | -                                                            | SQLException             |
+| long         | copyIn(String sql, InputStream from)                 | Uses **COPY FROM STDIN** to quickly import data to tables in a database from InputStream. | SQLException,IOException |
+| long         | copyIn(String sql, InputStream from, int bufferSize) | Uses **COPY FROM STDIN** to quickly import data to tables in a database from InputStream. | SQLException,IOException |
+| long         | copyIn(String sql, Reader from)                      | Uses **COPY FROM STDIN** to quickly import data to tables in a database from Reader. | SQLException,IOException |
+| long         | copyIn(String sql, Reader from, int bufferSize)      | Uses **COPY FROM STDIN** to quickly import data to tables in a database from Reader. | SQLException,IOException |
+| CopyOut      | copyOut(String sql)                                  | -                                                            | SQLException             |
+| long         | copyOut(String sql, OutputStream to)                 | Sends the result set of **COPY TO STDOUT** from the database to the OutputStream class. | SQLException,IOException |
+| long         | copyOut(String sql, Writer to)                       | Sends the result set of **COPY TO STDOUT** from the database to the Writer class. | SQLException,IOException |
+
+<br/>
+
+## Handling Import Errors
+
+### Scenarios
+
+Handle errors that occurred during data import.
+
+### Querying Error Information
+
+Errors that occur when data is imported are divided into data format errors and non-data format errors.
+
+- Data format errors
+
+  When creating a foreign table, specify **LOG INTO error_table_name**. Data format errors during data import will be written into the specified table. You can run the following SQL statement to query error details:
+
+  ```sql
+  mogdb=# SELECT * FROM error_table_name;
+  ```
+
+  Table 1 lists the columns of the *error_table_name* table.
+
+  **Table 1** Columns in the error information table
+
+  | Column Name | Type                     | Description                                                  |
+  | :---------- | :----------------------- | :----------------------------------------------------------- |
+  | nodeid      | integer                  | ID of the node where an error is reported                    |
+  | begintime   | timestamp with time zone | Time when a data format error was reported                   |
+  | filename    | character varying        | Name of the source data file where a data format error occurs |
+  | rownum      | bigint                   | Number of the row where a data format error occurs in a source data file |
+  | rawrecord   | text                     | Raw record of a data format error in the source data file    |
+  | detail      | text                     | Error details                                                |
+
+- Non-data format errors
+
+  A non-data format error leads to the failure of an entire data import task. You can locate and troubleshoot a non-data format error based on the error message displayed during data import.
+
+### Handling Data Import Errors
+
+Troubleshoot data import errors based on obtained error information and descriptions in the following table.
+
+**Table 2** Handling data import errors
+
+| Error Message                                                | Cause                                                        | Solution                                                     |
+| :----------------------------------------------------------- | :----------------------------------------------------------- | :----------------------------------------------------------- |
+| missing data for column "r_reason_desc"                      | 1. The number of columns in the source data file is less than that in the foreign table.<br/>2. In a TEXT-format source data file, an escape character (for example, ) leads to delimiter or quote mislocation.<br/>**Example:** The target table contains three columns, and the following data is imported. The escape character () converts the delimiter (\|) into the value of the second column, causing the value of the third column to lose.<br/>`BE|Belgium|1` | 1. If an error is reported due to missing columns, perform the following operations:<br/>- Add the value of the **r_reason_desc** column to the source data file.<br/>- When creating a foreign table, set the parameter **fill_missing_fields** to **on**. In this way, if the last column of a row in the source data file is missing, it will be set to **NULL** and no error will be reported.<br/>2. Check whether the row where an error is reported contains the escape character (). If the row contains such a character, you are advised to set the parameter **noescaping** to **true** when creating a foreign table, indicating that the escape character () and the characters following it are not escaped. |
+| extra data after last expected column                        | The number of columns in the source data file is greater than that in the foreign table. | - Delete extra columns from the source data file.<br/>- When creating a foreign table, set the parameter **ignore_extra_data** to **on**. In this way, if the number of columns in the source data file is greater than that in the foreign table, the extra columns at the end of rows will not be imported. |
+| invalid input syntax for type numeric: "a"                   | The data type is incorrect.                                  | In the source data file, change the data type of the columns to import. If this error information is displayed, change the data type to **numeric**. |
+| null value in column "staff_id" violates not-null constraint | The not-null constraint is violated.                         | In the source data file, add values to the specified columns. If this error information is displayed, add values to the **staff_id** column. |
+| duplicate key value violates unique constraint "reg_id_pk"   | The unique constraint is violated.                           | - Delete duplicate rows from the source data file.<br/>- Run the **SELECT** statement with the **DISTINCT** keyword to ensure that all imported rows are unique.<br/>`mogdb=# INSERT INTO reasons SELECT DISTINCT * FROM foreign_tpcds_reasons;` |
+| value too long for type character varying(16)                | The column length exceeds the upper limit.                   | In the source data file, change the column length. If this error information is displayed, reduce the column length to no greater than 16 bytes (VARCHAR2). |
+
+<br/>
+
+## Example 1: Importing and Exporting Data Through Local Files
+
+When the JAVA language is used for secondary development based on MogDB, you can use the CopyManager interface to export data from the database to a local file or import a local file to the database by streaming. The file can be in CSV or TEXT format.
+
+The sample program is as follows. Load the MogDB JDBC driver before executing it.
+
+```java
+import java.sql.Connection;
+import java.sql.DriverManager;
+import java.io.IOException;
+import java.io.FileInputStream;
+import java.io.FileOutputStream;
+import java.sql.SQLException;
+import org.postgresql.copy.CopyManager;
+import org.postgresql.core.BaseConnection;
+
+public class Copy{
+
+     public static void main(String[] args)
+     {
+      String urls = new String("jdbc:postgresql://localhost:8000/postgres"); // URL of the database
+      String username = new String("username");            // Username
+      String password = new String("passwd");             // Password
+      String tablename = new String("migration_table"); // Table information
+      String tablename1 = new String("migration_table_1"); // Table information
+      String driver = "org.postgresql.Driver";
+      Connection conn = null;
+
+      try {
+          Class.forName(driver);
+          conn = DriverManager.getConnection(urls, username, password);
+      } catch (ClassNotFoundException e) {
+           e.printStackTrace(System.out);
+      } catch (SQLException e) {
+           e.printStackTrace(System.out);
+      }
+
+      // Export data from the migration_table table to the d:/data.txt file.
+      try {
+          copyToFile(conn, "d:/data.txt", "(SELECT * FROM migration_table)");
+      } catch (SQLException e) {
+          // TODO Auto-generated catch block
+          e.printStackTrace();
+      } catch (IOException e) {
+          // TODO Auto-generated catch block
+          e.printStackTrace();
+      }
+      // Import data from the d:/data.txt file to the migration_table_1 table.
+      try {
+          copyFromFile(conn, "d:/data.txt", tablename1);
+      } catch (SQLException e) {
+          // TODO Auto-generated catch block
+          e.printStackTrace();
+      } catch (IOException e) {
+          // TODO Auto-generated catch block
+          e.printStackTrace();
+      }
+
+      // Export data from the migration_table_1 table to the d:/data1.txt file.
+      try {
+          copyToFile(conn, "d:/data1.txt", tablename1);
+      } catch (SQLException e) {
+          // TODO Auto-generated catch block
+          e.printStackTrace();
+      } catch (IOException e) {
+          // TODO Auto-generated catch block
+          e.printStackTrace();
+      }
+  }
+
+  public static void copyFromFile(Connection connection, String filePath, String tableName)
+         throws SQLException, IOException {
+
+     FileInputStream fileInputStream = null;
+
+     try {
+         CopyManager copyManager = new CopyManager((BaseConnection)connection);
+         fileInputStream = new FileInputStream(filePath);
+         copyManager.copyIn("COPY " + tableName + " FROM STDIN with (" + "DELIMITER"+"'"+ delimiter +  "'" + "ENCODING " + "'" + encoding + "')", fileInputStream);
+     } finally {
+         if (fileInputStream != null) {
+             try {
+                 fileInputStream.close();
+             } catch (IOException e) {
+                 e.printStackTrace();
+             }
+         }
+     }
+ }
+     public static void copyToFile(Connection connection, String filePath, String tableOrQuery)
+          throws SQLException, IOException {
+
+      FileOutputStream fileOutputStream = null;
+
+      try {
+          CopyManager copyManager = new CopyManager((BaseConnection)connection);
+          fileOutputStream = new FileOutputStream(filePath);
+          copyManager.copyOut("COPY " + tableOrQuery + " TO STDOUT", fileOutputStream);
+      } finally {
+          if (fileOutputStream != null) {
+              try {
+                  fileOutputStream.close();
+              } catch (IOException e) {
+                  e.printStackTrace();
+              }
+          }
+      }
+  }
+}
+```
+
+<br/>
+
+## Example 2: Migrating Data from a MySQL Database to the MogDB Database
+
+The following example shows how to use CopyManager to migrate data from MySQL to the MogDB database.
+
+```java
+import java.io.StringReader;
+import java.sql.Connection;
+import java.sql.DriverManager;
+import java.sql.ResultSet;
+import java.sql.SQLException;
+import java.sql.Statement;
+
+import org.postgresql.copy.CopyManager;
+import org.postgresql.core.BaseConnection;
+
+public class Migration{
+
+    public static void main(String[] args) {
+        String url = new String("jdbc:postgresql://localhost:8000/postgres"); // URL of the database
+        String user = new String("username");            // MogDB database user name
+        String pass = new String("passwd");             // MogDB database password
+        String tablename = new String("migration_table_1"); // Table information
+        String delimiter = new String("|");              // Delimiter
+        String encoding = new String("UTF8");            // Character set
+        String driver = "org.postgresql.Driver";
+        StringBuffer buffer = new StringBuffer();       // Buffer to store formatted data
+
+        try {
+            // Obtain the query result set of the source database.
+            ResultSet rs = getDataSet();
+
+            // Traverse the result set and obtain records row by row.
+            // The values of columns in each record are separated by the specified delimiter and end with a linefeed, forming strings.
+            // Add the strings to the buffer.
+            while (rs.next()) {
+                buffer.append(rs.getString(1) + delimiter
+                        + rs.getString(2) + delimiter
+                        + rs.getString(3) + delimiter
+                        + rs.getString(4)
+                        + "\n");
+            }
+            rs.close();
+
+            try {
+                // Connect to the target database.
+                Class.forName(driver);
+                Connection conn = DriverManager.getConnection(url, user, pass);
+                BaseConnection baseConn = (BaseConnection) conn;
+                baseConn.setAutoCommit(false);
+
+                // Initialize the table.
+                String sql = "Copy " + tablename + " from STDIN with (DELIMITER " + "'" + delimiter + "'" +","+ " ENCODING " + "'" + encoding + "'");
+
+                // Commit data in the buffer.
+                CopyManager cp = new CopyManager(baseConn);
+                StringReader reader = new StringReader(buffer.toString());
+                cp.copyIn(sql, reader);
+                baseConn.commit();
+                reader.close();
+                baseConn.close();
+            } catch (ClassNotFoundException e) {
+                e.printStackTrace(System.out);
+            } catch (SQLException e) {
+                e.printStackTrace(System.out);
+            }
+
+        } catch (Exception e) {
+            e.printStackTrace();
+        }
+    }
+
+    //********************************
+    // Return the query result set from the source database.
+    //*********************************
+    private static ResultSet getDataSet() {
+        ResultSet rs = null;
+        try {
+            Class.forName("com.MY.jdbc.Driver").newInstance();
+            Connection conn = DriverManager.getConnection("jdbc:MY://10.119.179.227:3306/jack?useSSL=false&allowPublicKeyRetrieval=true", "jack", "Gauss@123");
+            Statement stmt = conn.createStatement();
+            rs = stmt.executeQuery("select * from migration_table");
+        } catch (SQLException e) {
+            e.printStackTrace();
+        } catch (Exception e) {
+            e.printStackTrace();
+        }
+        return rs;
+    }
+}
+```
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/4-using-a-gsql-meta-command-to-import-data.md b/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/4-using-a-gsql-meta-command-to-import-data.md
new file mode 100644
index 0000000000000000000000000000000000000000..2215c6858e3499faa37d2eb157d1994e6f1ce453
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/4-using-a-gsql-meta-command-to-import-data.md
@@ -0,0 +1,207 @@
+---
+title: Using a gsql Meta-Command to Import Data
+summary: Using a gsql Meta-Command to Import Data
+author: Guo Huan
+date: 2021-03-04
+---
+
+# Using a gsql Meta-Command to Import Data
+
+The **gsql** tool provides the **\copy** meta-command to import data.
+
+**\copy Command**
+
+## Syntax
+
+```
+\copy { table [ ( column_list ) ] |
+
+( query ) } { from | to } { filename |
+
+stdin | stdout | pstdin | pstdout }
+
+[ with ] [ binary ] [ delimiter
+
+[ as ] 'character' ] [ null [ as ] 'string' ]
+
+[ csv [ header ] [ quote [ as ]
+
+'character' ] [ escape [ as ] 'character' ]
+
+[ force quote column_list | * ] [ force
+
+not null column_list ] ]
+```
+
+You can run this command to import or export data after logging in to a database on any gsql client. Different from the **COPY** statement in SQL, this command performs read/write operations on local files rather than files on database servers. The accessibility and permissions of the local files are restricted to local users.
+
+> **NOTE:**
+>
+> **\copy** applies only to small-scale data import in good format. It does not preprocess invalid characters or provide error tolerance. Therefore, **\copy** cannot be used in scenarios where abnormal data exists. **GDS** or **COPY** is preferred for data import.
+
+**Parameter Description**
+
+- table
+
+  Specifies the name (possibly schema-qualified) of an existing table.
+
+  Value range: an existing table name
+
+- column_list
+
+  Specifies an optional list of columns to be copied.
+
+  Value range: any field in the table. If no column list is specified, all columns of the table will be copied.
+
+- query
+
+  Specifies that the results are to be copied.
+
+  Value range: a **SELECT** or **VALUES** command in parentheses
+
+- filename
+
+  Specifies the absolute path of a file. To run the **COPY** command, the user must have the write permission for this path.
+
+- stdin
+
+  Specifies that input comes from the standard input.
+
+- stdout
+
+  Specifies that output goes to the standard output.
+
+- pstdin
+
+  Specifies that input comes from the gsql client.
+
+- pstout
+
+- Specifies that output goes to the gsql client.
+
+- binary
+
+  Specifies that data is stored and read in binary mode instead of text mode. In binary mode, you cannot declare **DELIMITER**, **NULL**, or **CSV**. After **binary** is specified, CSV, FIXED, and TEXT cannot be specified through **option** or **copy_option**.
+
+- delimiter [ as ] 'character'
+
+    Specifies the character that separates columns within each row (line) of the file.
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+    >
+    > - The value of **delimiter** cannot be **\r** or **\n**.
+    > - A delimiter cannot be the same as the null value. The delimiter for the CSV format cannot be same as the **quote** value.
+    > - The delimiter of TEXT data cannot contain any of the following characters: \\.abcdefghijklmnopqrstuvwxyz0123456789.
+    > - The data length of a single row should be less than 1 GB. A row that has many columns using long delimiters cannot contain much valid data.
+    > - You are advised to use multi-character delimiters or invisible delimiters. For example, you can use multi-characters (such as $^&) and invisible characters (such as 0x07, 0x08, and 0x1b).
+
+    Value range: a multi-character delimiter within 10 bytes
+
+    Default value:
+
+  - A tab character in TEXT format
+  - A comma (,) in CSV format
+  - No delimiter in FIXED format
+
+- null [ as ] 'string'
+
+    Specifies the string that represents a null value.
+
+    Value range:
+
+  - A null value cannot be **\\r** or **\\n**. The maximum length is 100 characters.
+  - A null value cannot be the same as the **delimiter** or **quote** value.
+
+    Default value:
+
+  - The default value for the CSV format is an empty string without quotation marks.
+  - The default value for the TEXT format is **\\N**.
+
+- header
+
+  Specifies whether a file contains a header with the names of each column in the file. **header** is available only for CSV and FIXED files.
+
+  When data is imported, if **header** is **on**, the first row of the data file will be identified as the header and ignored. If **header** is **off**, the first row will be identified as a data row.
+
+  When data is exported, if header is **on**, **fileheader** must be specified. **fileheader** specifies the content in the header. If **header** is **off**, an exported file does not contain a header.
+
+  Value range:**true/on** and **false/off**
+
+  Default value: false
+
+- quote [ as ] 'character'
+
+  Specifies a quoted character string for a CSV file.
+
+  Default value: a double quotation mark (")
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > - The value of **quote** cannot be the same as that of the **delimiter** or null parameter.
+  > - The value of **quote** must be a single-byte character.
+  > - Invisible characters are recommended, such as 0x07, 0x08, and 0x1b.
+
+- escape [ as ] 'character'
+
+  Specifies an escape character for a CSV file. The value must be a single-byte character.
+
+  Default value: a double quotation mark (") If the value is the same as that of **quote**, it will be replaced by **\0**.
+
+- force quote column_list | *
+
+  In **CSV COPY TO** mode, forces quotation marks to be used for all non-null values in each specified column. Null values are not quoted.
+
+  Value range: an existing column name
+
+- force not null column_list
+
+  Assigns a value to a specified column in **CSV COPY FROM** mode.
+
+  Value range: an existing column name
+
+**Examples**
+
+1. Create a target table **a**.
+
+   ```sql
+   mogdb=# CREATE TABLE a(a int);
+   ```
+
+2. Import data.
+
+   Copy data from **stdin** to table **a**.
+
+   ```sql
+   mogdb=# \copy a from stdin;
+   ```
+
+   When the **>>** characters are displayed, enter data. To end your input, enter a backslash and a period (\.).
+
+   ```sql
+   Enter data to be copied followed by a newline.
+   End with a backslash and a period on a line by itself.
+   >> 1
+   >> 2
+   >> \.
+   ```
+
+   Query data imported to table **a**.
+
+   ```sql
+   mogdb=# SELECT * FROM a;
+    a
+   ---
+    1
+    2
+   (2 rows)
+   ```
+
+3. Copy data from a local file to table **a**. The following assumes that the local file is **/home/omm/2.csv**.
+
+   - Commas (,) are used as delimiters.
+
+   - If the number of columns defined in a source data file is greater than that in a foreign table, extra columns will be ignored during import.
+
+     ```sql
+     mogdb=# \copy a FROM '/home/omm/2.csv' WITH (delimiter',',IGNORE_EXTRA_DATA 'on');
+     ```
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/5-using-gs_restore-to-import-data.md b/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/5-using-gs_restore-to-import-data.md
new file mode 100644
index 0000000000000000000000000000000000000000..576040d27756e5093bcc9e5219c04b53d950d6af
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/5-using-gs_restore-to-import-data.md
@@ -0,0 +1,263 @@
+---
+title: Using gs_restore to Import Data
+summary: Using gs_restore to Import Data
+author: Guo Huan
+date: 2021-03-04
+---
+
+# Using gs_restore to Import Data
+
+## Scenarios
+
+**gs_restore** is an import tool provided by the MogDB database. You can use **gs_restore** to import the files exported by **gs_dump** to a database. **gs_restore** can import the files in .tar, custom, or directory format.
+
+**gs_restore** can:
+
+- Import data to a database.
+
+  If a database is specified, data is imported to the database. If multiple databases are specified, the password for connecting to each database also needs to be specified.
+
+- Import data to a script.
+
+  If no database is specified, a script containing the SQL statement to recreate the database is created and written to a file or standard output. This script output is equivalent to the plain text output of **gs_dump**.
+
+You can specify and sort the data to import.
+
+## Procedure
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> **gs_restore** incrementally imports data by default. To prevent data exception caused by consecutive imports, use the **-e** and **-c** parameters for each import. **-c** indicates that existing data is deleted from the target database before each import. **-e** indicates that the system ignores the import task with an error (error message is displayed after the import process is complete) and proceeds with the next by default. Therefore, you need to exit the system if an error occurs when you send the SQL statement to the database.
+
+1. Log in as the OS user **omm** to the primary node of the database.
+
+2. Use **gs_restore** to import all object definitions from the exported file of the entire **mogdb** database to the **backupdb** database.
+
+   ```bash
+   $ gs_restore -U jack /home/omm/backup/MPPDB_backup.tar -p 8000 -d backupdb -s -e -c
+   Password:
+   ```
+
+   **Table 1** Common parameters
+
+   | Parameters | Description                                                  | Example Value |
+   | :--------- | :----------------------------------------------------------- | :------------ |
+   | -U         | Username for database connection.                            | -U jack       |
+   | -W         | User password for database connection.<br/>- This parameter is not required for database administrators if the trust policy is used for authentication.<br/>- If you connect to the database without specifying this parameter and you are not a database administrator, you will be prompted to enter the password. | -W abcd@123   |
+   | -d         | Database to which data will be imported.                     | -d backupdb   |
+   | -p         | TCP port or local Unix-domain socket file extension on which the server is listening for connections. | -p 8000       |
+   | -e         | Exits if an error occurs when you send the SQL statement to the database. Error messages are displayed after the import process is complete. | -             |
+   | -c         | Cleans existing objects from the target database before the import. | -             |
+   | -s         | Imports only object definitions in schemas and does not import data. Sequence values will also not be imported. | -             |
+
+   For details about other parameters, see "Tool Reference > Server Tools > [gs_restore](9-gs_restore)" in the **Reference Guide**.
+
+## Examples
+
+Example 1: Run **gs_restore** to import data and all object definitions of the **mogdb** database from the **MPPDB_backup.dmp** file (custom format).
+
+```bash
+$ gs_restore backup/MPPDB_backup.dmp -p 8000 -d backupdb
+Password:
+gs_restore[2017-07-21 19:16:26]: restore operation successful
+gs_restore: total time: 13053  ms
+```
+
+Example 2: Run **gs_restore** to import data and all object definitions of the **mogdb** database from the **MPPDB_backup.tar** file.
+
+```bash
+$ gs_restore backup/MPPDB_backup.tar -p 8000 -d backupdb
+gs_restore[2017-07-21 19:21:32]: restore operation successful
+gs_restore[2017-07-21 19:21:32]: total time: 21203  ms
+```
+
+Example 3: Run **gs_restore** to import data and all object definitions of the **mogdb** database from the **MPPDB_backup** directory.
+
+```bash
+$ gs_restore backup/MPPDB_backup -p 8000 -d backupdb
+gs_restore[2017-07-21 19:26:46]: restore operation successful
+gs_restore[2017-07-21 19:26:46]: total time: 21003  ms
+```
+
+Example 4: Run **gs_restore** to import all object definitions of the database from the **MPPDB_backup.tar** file to the **backupdb** database. Table data is not imported.
+
+```bash
+$ gs_restore /home/omm/backup/MPPDB_backup.tar -p 8000 -d backupdb -s -e -c
+Password:
+gs_restore[2017-07-21 19:46:27]: restore operation successful
+gs_restore[2017-07-21 19:46:27]: total time: 32993  ms
+```
+
+Example 5: Run **gs_restore** to import data and all definitions in the **PUBLIC** schema from the **MPPDB_backup.dmp** file. Existing objects are deleted from the target database before the import. If an existing object references to an object in another schema, manually delete the referenced object first.
+
+```bash
+$ gs_restore backup/MPPDB_backup.dmp -p 8000 -d backupdb -e -c -n PUBLIC
+gs_restore: [archiver (db)] Error while PROCESSING TOC:
+gs_restore: [archiver (db)] Error from TOC entry 313; 1259 337399 TABLE table1 gaussdba
+gs_restore: [archiver (db)] could not execute query: ERROR:  cannot drop table table1 because other objects depend on it
+DETAIL:  view t1.v1 depends on table table1
+HINT:  Use DROP ... CASCADE to drop the dependent objects too.
+Command was: DROP TABLE public.table1;
+```
+
+Manually delete the referenced object and create it again after the import is complete.
+
+```bash
+$ gs_restore backup/MPPDB_backup.dmp -p 8000 -d backupdb -e -c -n PUBLIC
+gs_restore[2017-07-21 19:52:26]: restore operation successful
+gs_restore[2017-07-21 19:52:26]: total time: 2203  ms
+```
+
+Example 6: Run **gs_restore** to import the definition of the **hr.staffs** table in the **hr** schema from the **MPPDB_backup.dmp** file. Before the import, the **hr.staffs** table does not exist.
+
+```bash
+$ gs_restore backup/MPPDB_backup.dmp -p 8000 -d backupdb -e -c -s -n hr -t hr.staffs
+gs_restore[2017-07-21 19:56:29]: restore operation successful
+gs_restore[2017-07-21 19:56:29]: total time: 21000  ms
+```
+
+Example 7: Run **gs_restore** to import data of the **hr.staffs** table in **hr** schema from the **MPPDB_backup.dmp** file. Before the import, the **hr.staffs** table is empty.
+
+```bash
+$ gs_restore backup/MPPDB_backup.dmp -p 8000 -d backupdb -e -a -n hr -t hr.staffs
+gs_restore[2017-07-21 20:12:32]: restore operation successful
+gs_restore[2017-07-21 20:12:32]: total time: 20203  ms
+```
+
+Example 8: Run **gs_restore** to import the definition of the **hr.staffs** table. Before the import, the **hr.staffs** table already exists.
+
+```sql
+human_resource=# select * from hr.staffs;
+ staff_id | first_name  |  last_name  |  email   |    phone_number    |      hire_date      | employment_id |  salary  | commission_pct | manager_id | section_id
+----------+-------------+-------------+----------+--------------------+---------------------+---------------+----------+----------------+------------+------------
+      200 | Jennifer    | Whalen      | JWHALEN  | 515.123.4444       | 1987-09-17 00:00:00 | AD_ASST       |  4400.00 |                |        101 |         10
+      201 | Michael     | Hartstein   | MHARTSTE | 515.123.5555       | 1996-02-17 00:00:00 | MK_MAN        | 13000.00 |                |        100 |         20
+
+$ gsql -d human_resource -p 8000
+
+gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+Non-SSL connection (SSL connection is recommended when requiring high-security)
+Type "help" for help.
+
+human_resource=# drop table hr.staffs CASCADE;
+NOTICE:  drop cascades to view hr.staff_details_view
+DROP TABLE
+
+$ gs_restore /home/omm/backup/MPPDB_backup.tar -p 8000 -d human_resource -n hr -t staffs -s -e
+restore operation successful
+total time: 904  ms
+
+human_resource=# select * from hr.staffs;
+ staff_id | first_name | last_name | email | phone_number | hire_date | employment_id | salary | commission_pct | manager_id | section_id
+----------+------------+-----------+-------+--------------+-----------+---------------+--------+----------------+------------+------------
+(0 rows)
+```
+
+Example 9: Run **gs_restore** to import data and definitions of the **staffs** and **areas** tables. Before the import, the **staffs** and **areas** tables do not exist.
+
+```sql
+human_resource=# \d
+                                 List of relations
+ Schema |        Name        | Type  |  Owner   |             Storage
+--------+--------------------+-------+----------+----------------------------------
+ hr     | employment_history | table | omm | {orientation=row,compression=no}
+ hr     | employments        | table | omm | {orientation=row,compression=no}
+ hr     | places             | table | omm | {orientation=row,compression=no}
+ hr     | sections           | table | omm | {orientation=row,compression=no}
+ hr     | states             | table | omm | {orientation=row,compression=no}
+(5 rows)
+
+$ gs_restore /home/mogdb/backup/MPPDB_backup.tar -p 8000 -d human_resource -n hr -t staffs -n hr -t areas
+restore operation successful
+total time: 724  ms
+
+human_resource=# \d
+                                 List of relations
+ Schema |        Name        | Type  |  Owner   |             Storage
+--------+--------------------+-------+----------+----------------------------------
+ hr     | areas              | table | omm | {orientation=row,compression=no}
+ hr     | employment_history | table | omm | {orientation=row,compression=no}
+ hr     | employments        | table | omm | {orientation=row,compression=no}
+ hr     | places             | table | omm | {orientation=row,compression=no}
+ hr     | sections           | table | omm | {orientation=row,compression=no}
+ hr     | staffs             | table | omm | {orientation=row,compression=no}
+ hr     | states             | table | omm | {orientation=row,compression=no}
+(7 rows)
+
+human_resource=# select * from hr.areas;
+ area_id |       area_name
+---------+------------------------
+       4 | Middle East and Africa
+       1 | Europe
+       2 | Americas
+       3 | Asia
+(4 rows)
+```
+
+Example 10: Run **gs_restore** to import data and all object definitions in the **hr** schema.
+
+```bash
+$ gs_restore /home/omm/backup/MPPDB_backup1.dmp 8000 -d backupdb -n hr -e -c
+restore operation successful
+total time: 702  ms
+```
+
+Example 11: Run **gs_restore** to import all object definitions in the **hr** and **hr1** schemas to the **backupdb** database.
+
+```bash
+$ gs_restore /home/omm/backup/MPPDB_backup2.dmp -p 8000 -d backupdb -n hr -n hr1 -s
+restore operation successful
+total time: 665  ms
+```
+
+Example 12: Run **gs_restore** to decrypt the files exported from the **human_resource** database and import them to the **backupdb** database.
+
+```sql
+mogdb=# create database backupdb;
+CREATE DATABASE
+
+$ gs_restore /home/omm/backup/MPPDB_backup.tar -p 8000 -d backupdb --with-key=1234567812345678
+restore operation successful
+total time: 23472  ms
+
+$ gsql -d backupdb -p 8000 -r
+
+gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+Non-SSL connection (SSL connection is recommended when requiring high-security)
+Type "help" for help.
+
+backupdb=# select * from hr.areas;
+ area_id |       area_name
+---------+------------------------
+       4 | Middle East and Africa
+       1 | Europe
+       2 | Americas
+       3 | Asia
+(4 rows)
+```
+
+Example 13: **user 1** does not have the permission to import data from an exported file to the **backupdb** database and **role1** has this permission. To import the exported data to the **backupdb** database, you can set **-role** to **role1** in the **gs_restore** command.
+
+```sql
+human_resource=# CREATE USER user1 IDENTIFIED BY "1234@abc";
+CREATE ROLE role1 with SYSADMIN IDENTIFIED BY "abc@1234";
+
+$ gs_restore -U user1 /home/omm/backup/MPPDB_backup.tar -p 8000 -d backupdb --role role1 --rolepassword abc@1234
+Password:
+restore operation successful
+total time: 554  ms
+
+$ gsql -d backupdb -p 8000 -r
+
+gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+Non-SSL connection (SSL connection is recommended when requiring high-security)
+Type "help" for help.
+
+backupdb=# select * from hr.areas;
+ area_id |       area_name
+---------+------------------------
+       4 | Middle East and Africa
+       1 | Europe
+       2 | Americas
+       3 | Asia
+(4 rows)
+```
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/6-updating-data-in-a-table.md b/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/6-updating-data-in-a-table.md
new file mode 100644
index 0000000000000000000000000000000000000000..d1a64607026b303845f0533fe68e5b040ec2a16a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/6-updating-data-in-a-table.md
@@ -0,0 +1,166 @@
+---
+title: Updating Data in a Table
+summary: Updating Data in a Table
+author: Guo Huan
+date: 2021-03-04
+---
+
+# Updating Data in a Table
+
+## Updating a Table by Using DML Statements
+
+In MogDB, you can update a table by running DML statements.
+
+### Procedure
+
+There is a table named **customer_t** and the table structure is as follows:
+
+```sql
+CREATE TABLE customer_t
+( c_customer_sk             integer,
+  c_customer_id             char(5),
+  c_first_name              char(6),
+  c_last_name               char(8)
+) ;
+```
+
+You can run the following DML statements to update data in the table.
+
+- Run the **INSERT** statement to insert data into the table.
+
+  - Insert a row to the **customer_t** table.
+
+    ```sql
+    INSERT INTO customer_t (c_customer_sk, c_customer_id, c_first_name,c_last_name) VALUES (3769, 5, 'Grace','White');
+    ```
+
+  - Insert multiple rows to the **customer_t** table.
+
+    ```sql
+    INSERT INTO customer_t (c_customer_sk, c_customer_id, c_first_name,c_last_name) VALUES
+    (6885, 1, 'Joes', 'Hunter'),
+    (4321, 2, 'Lily','Carter'),
+    (9527, 3, 'James', 'Cook'),
+    (9500, 4, 'Lucy', 'Baker');
+    ```
+
+    For details on how to use **INSERT**, see Inserting Data to Tables.
+
+- Run the **UPDATE** statement to update data in the table. Change the value of the **c_customer_id** column to **0**.
+
+  ```sql
+  UPDATE customer_t SET c_customer_id = 0;
+  ```
+
+  For details on how to use **UPDATE**, see UPDATE.
+
+- Run the **DELETE** statement to delete rows from the table.
+
+  You can use the **WHERE** clause to specify the rows whose data is to delete. If you do not specify it, all rows in the table are deleted and only the data structure is retained.
+
+  ```sql
+  DELETE FROM customer_t WHERE c_last_name = 'Baker';
+  ```
+
+  For details on how to use **DELETE**, see DELETE.
+
+- Run the **TRUNCATE** statement to delete all rows from the table.
+
+  ```sql
+  TRUNCATE TABLE customer_t;
+  ```
+
+  For details on how to use **TRUNCATE**, see TRUNCATE.
+
+  The **DELETE** statement deletes a row of data each time whereas the **TRUNCATE** statement deletes data by releasing the data page stored in the table. Therefore, data can be deleted more quickly by using **TRUNCATE** than using **DELETE**.
+
+  **DELETE** deletes table data but does not release table storage space. **TRUNCATE** deletes table data and releases table storage space.
+
+## Updating and Inserting Data by Using the MERGE INTO Statement
+
+To add all or a large amount of data in a table to an existing table, you can run the **MERGE INTO** statement in MogDB to merge the two tables so that data can be quickly added to the existing table.
+
+The **MERGE INTO** statement matches data in a source table with that in a target table based on a join condition. If data matches, **UPDATE** will be executed on the target table. Otherwise, **INSERT** will be executed. This statement is a convenient way to combine multiple operations and avoids multiple **INSERT** or **UPDATE** statements.
+
+### Prerequisites
+
+You have the **INSERT** and **UPDATE** permissions for the target table and the **SELECT** permission for the source table.
+
+### Procedure
+
+1. Create a source table named **products** and insert data.
+
+   ```sql
+   mogdb=# CREATE TABLE products
+   ( product_id INTEGER,
+     product_name VARCHAR2(60),
+     category VARCHAR2(60)
+   );
+
+   mogdb=# INSERT INTO products VALUES
+   (1502, 'olympus camera', 'electrncs'),
+   (1601, 'lamaze', 'toys'),
+   (1666, 'harry potter', 'toys'),
+   (1700, 'wait interface', 'books');
+   ```
+
+2. Create a target table named **newproducts** and insert data.
+
+   ```sql
+   mogdb=# CREATE TABLE newproducts
+   ( product_id INTEGER,
+     product_name VARCHAR2(60),
+     category VARCHAR2(60)
+   );
+
+   mogdb=# INSERT INTO newproducts VALUES
+   (1501, 'vivitar 35mm', 'electrncs'),
+   (1502, 'olympus ', 'electrncs'),
+   (1600, 'play gym', 'toys'),
+   (1601, 'lamaze', 'toys'),
+   (1666, 'harry potter', 'dvd');
+   ```
+
+3. Run the **MERGE INTO** statement to merge data in the source table **products** into the target table **newproducts**.
+
+   ```sql
+   MERGE INTO newproducts np
+   USING products p
+   ON (np.product_id = p.product_id )
+   WHEN MATCHED THEN
+    UPDATE SET np.product_name = p.product_name, np.category = p.category
+   WHEN NOT MATCHED THEN
+    INSERT VALUES (p.product_id, p.product_name, p.category) ;
+   ```
+
+   For details on parameters in the statement, see [Table 1](#Parameters in the MERGE INTO statement). For more information, see MERGE INTO.
+
+   **Table 1** Parameters in the MERGE INTO statement<a id="Parameters in the MERGE INTO statement"> </a>
+
+   | Parameter                   | Description                                                  | Example Value                                                |
+   | :-------------------------- | :----------------------------------------------------------- | :----------------------------------------------------------- |
+   | **INTO** clause             | Specifies a target table that is to be updated or has data to be inserted.<br/>A table alias is supported. | Value: newproducts np<br/>The table name is **newproducts** and the alias is **np**. |
+   | **USING** clause            | Specifies a source table. A table alias is supported.<br/>If the target table is a replication table, the source table must also be a replication table. | Value: products p<br/>The table name is **products** and the alias is **p**. |
+   | **ON** clause               | Specifies a join condition between a target table and a source table.<br/>Columns in the join condition cannot be updated. | Value: np.product_id = p.product_id<br/>The join condition is that the **product_id** column in the target table **newproducts** has equivalent values as the **product_id** column in the source table **products**. |
+   | **WHEN MATCHED** clause     | Performs **UPDATE** if data in the source table matches that in the target table based on the condition.<br/>- Only one **WHEN MATCHED** clause can be specified.<br/>- The **WHEN MATCHED** clause can be omitted. If it is omitted, no operation will be performed on the rows that meet the condition in the **ON** clause.<br/>- Columns involved in the distribution key of the target table cannot be updated. | Value: WHEN MATCHED THEN UPDATE SET np.product_name = p.product_name, np.category = p.category<br/>When the condition in the **ON** clause is met, the values of the **product_name** and **category** columns in the target table **newproducts** are replaced with the values in the corresponding columns in the source table **products**. |
+   | **WHEN NOT MATCHED** clause | Performs **INSERT** if data in the source table does not match that in the target table based on the condition.<br/>- Only one **WHEN NOT MATCHED** clause can be specified.<br/>- The **WHEN NOT MATCHED** clause can be omitted.<br/>- An **INSERT** clause can contain only one **VALUES**.<br/>- The **WHEN MATCHED** and **WHEN NOT MATCHED** clauses can be exchanged in sequence. One of them can be omitted, but they cannot be omitted at the same time. | Value: WHEN NOT MATCHED THEN INSERT VALUES (p.product_id, p.product_name, p.category)<br/>Insert rows in the source table **products** that do not meet the condition in the **ON** clause into the target table **newproducts**. |
+
+4. Query the target table **newproducts** after the merge.
+
+   ```sql
+   SELECT * FROM newproducts;
+   ```
+
+   The command output is as follows:
+
+   ```sql
+    product_id |  product_name  | category
+   ------------+----------------+-----------
+         1501 | vivitar 35mm   | electrncs
+         1502 | olympus camera | electrncs
+         1666 | harry potter   | toys
+         1600 | play gym       | toys
+         1601 | lamaze         | toys
+         1700 | wait interface | books
+   (6 rows)
+   ```
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/7-deep-copy.md b/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/7-deep-copy.md
new file mode 100644
index 0000000000000000000000000000000000000000..15c0a82b53c13c648683e7e9b918441c7aa8f608
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/7-deep-copy.md
@@ -0,0 +1,116 @@
+---
+title: Deep Copy
+summary: Deep Copy
+author: Guo Huan
+date: 2021-03-04
+---
+
+# Deep Copy
+
+After data is imported, you can perform a deep copy to modify a partition key, change a row-store table to a column-store table, or add a partial cluster key. A deep copy re-creates a table and batch inserts data into the table.
+
+MogDB provides three deep copy methods.
+
+## Performing a Deep Copy by Using the CREATE TABLE Statement
+
+Run the **CREATE TABLE** statement to create a copy of the original table, batch insert data of the original table into the copy, and rename the copy to the name of the original table.
+
+When creating the copy, you can specify table and column attributes, such as the primary key.
+
+**Procedure**
+
+Perform the following operations to carry out a deep copy for the **customer_t** table:
+
+1. Run the **CREATE TABLE** statement to create the copy **customer_t_copy** of the **customer_t** table.
+
+   ```sql
+   CREATE TABLE customer_t_copy
+   ( c_customer_sk             integer,
+     c_customer_id             char(5),
+     c_first_name              char(6),
+     c_last_name               char(8)
+   ) ;
+   ```
+
+2. Run the **INSERT INTO…SELECT** statement to batch insert data of the original table into the copy.
+
+   ```sql
+   INSERT INTO customer_t_copy (SELECT * FROM customer_t);
+   ```
+
+3. Delete the original table.
+
+   ```sql
+   DROP TABLE customer_t;
+   ```
+
+4. Run the **ALTER TABLE** statement to rename the copy to the name of the original table.
+
+   ```sql
+   ALTER TABLE customer_t_copy RENAME TO customer_t;
+   ```
+
+## Performing a Deep Copy by Using the CREATE TABLE LIKE Statement
+
+Run the **CREATE TABLE LIKE** statement to create a copy of the original table, batch insert data of the original table into the copy, and rename the copy to the name of the original table. This method does not inherit the primary key attributes of the original table. You can use the **ALTER TABLE** statement to add them.
+
+**Procedure**
+
+1. Run the **CREATE TABLE LIKE** statement to create the copy **customer_t_copy** of the **customer_t** table.
+
+   ```sql
+   CREATE TABLE customer_t_copy (LIKE customer_t);
+   ```
+
+2. Run the **INSERT INTO…SELECT** statement to batch insert data of the original table into the copy.
+
+   ```sql
+   INSERT INTO customer_t_copy (SELECT * FROM customer_t);
+   ```
+
+3. Delete the original table.
+
+   ```sql
+   DROP TABLE customer_t;
+   ```
+
+4. Run the **ALTER TABLE** statement to rename the copy to the name of the original table.
+
+   ```sql
+   ALTER TABLE customer_t_copy RENAME TO customer_t;
+   ```
+
+## Performing a Deep Copy by Creating a Temporary Table and Truncating the Original Table
+
+Run the **CREATE TABLE ….** **AS** statement to create a temporary table for the original table, truncate the original table, and batch insert data of the temporary data into the original table.
+
+When creating the temporary table, retain the primary key attributes of the original table. This method is recommended if the original table has dependency items.
+
+**Procedure**
+
+1. Run the **CREATE TABLE AS** statement to create a temporary table **customer_t_temp** for the **customer_t** table.
+
+   ```sql
+   CREATE TEMP TABLE customer_t_temp AS SELECT * FROM customer_t;
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+   > Compared with the use of permanent tables, the use of temporary tables can improve performance but may incur data loss. A temporary table is automatically deleted at the end of the session where it is located. If data loss is unacceptable, use a permanent table.
+
+2. Truncate the original table **customer_t**.
+
+   ```sql
+   TRUNCATE customer_t;
+   ```
+
+3. Run the **INSERT INTO…SELECT** statement to batch insert data of the temporary table into the original table.
+
+   ```sql
+   INSERT INTO customer_t (SELECT * FROM customer_t_temp);
+   ```
+
+4. Delete the temporary table **customer_t_temp**.
+
+   ```sql
+   DROP TABLE customer_t_temp;
+   ```
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/8-ANALYZE-table.md b/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/8-ANALYZE-table.md
new file mode 100644
index 0000000000000000000000000000000000000000..ba0ef2e9b65b6f8fef54cb416354c81fc746ed3d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/8-ANALYZE-table.md
@@ -0,0 +1,46 @@
+---
+title: ANALYZE Table
+summary: ANALYZE Table
+author: Guo Huan
+date: 2021-03-04
+---
+
+# ANALYZE Table
+
+The execution plan generator needs to use table statistics to generate the most effective query execution plan to improve query performance. After data is imported, you are advised to run the **ANALYZE** statement to update table statistics. The statistics are stored in the system catalog **PG_STATISTIC**.
+
+## ANALYZE Table
+
+**ANALYZE** supports row-store and column-store tables. **ANALYZE** can also collect statistics about specified columns of a local table. For details on **ANALYZE**, see [ANALYZE | ANALYSE](32-ANALYZE-ANALYSE).
+
+Update table statistics.
+
+Do **ANALYZE** to the **product_info** table.
+
+```sql
+ANALYZE product_info;
+```
+
+```sql
+ANALYZE
+```
+
+## autoanalyze
+
+MogDB provides the GUC parameter autovacuum to specify whether to enable the autovacuum function of the database.
+
+If **autovacuum** is set to **on**, the system will start the autovacuum thread to automatically analyze tables when the data volume in the table reaches the threshold. This is the autoanalyze function.
+
+- For an empty table, when the number of rows inserted to it is greater than 50, **ANALYZE** is automatically triggered.
+- For a table containing data, the threshold is 50 + 10% x **reltuples**, where **reltuples** indicates the total number of rows in the table.
+
+The autovacuum function also depends on the following two GUC parameters in addition to **autovacuum**:
+
+- track_counts: This parameter must be set to **on** to enable statistics collection about the database.
+- autovacuum_max_workers: This parameter must be set to a value greater than **0** to specify the maximum number of concurrent autovacuum threads.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - The autoanalyze function supports the default sampling mode but not percentage sampling.
+> - The autoanalyze function does not collect multi-column statistics, which only supports percentage sampling.
+> - The autoanalyze function supports row-store and column-store tables and does not support foreign tables, temporary tables, unlogged tables, and TOAST tables.
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/9-doing-VACUUM-to-a-table.md b/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/9-doing-VACUUM-to-a-table.md
new file mode 100644
index 0000000000000000000000000000000000000000..06de9a0db25db95529fbef3049d539a5294a90e2
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/9-doing-VACUUM-to-a-table.md
@@ -0,0 +1,22 @@
+---
+title: Doing VACUUM to a Table
+summary: Doing VACUUM to a Table
+author: Guo Huan
+date: 2021-03-04
+---
+
+# Doing VACUUM to a Table
+
+If a large number of rows were updated or deleted during import, run **VACUUM FULL** before **ANALYZE**. A large number of UPDATE and DELETE operations generate huge disk page fragments, which reduces query efficiency. **VACUUM FULL** can restore disk page fragments and return them to the OS.
+
+Run the **VACUUM FULL** statement.
+
+Do **VACUUM FULL** to the **product_info** table.
+
+```sql
+VACUUM FULL product_info
+```
+
+```sql
+VACUUM
+```
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/1-introducing-mot/1-mot-introduction.md b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/1-introducing-mot/1-mot-introduction.md
new file mode 100644
index 0000000000000000000000000000000000000000..4d56487bfd6dcf6b5058fceb5f4aa6bf19cb9e8d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/1-introducing-mot/1-mot-introduction.md
@@ -0,0 +1,33 @@
+---
+title: MOT Introduction
+summary: MOT Introduction
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# MOT Introduction
+
+MogDB introduces Memory-Optimized Tables (MOT) storage engine - a transactional row-based store (rowstore), that is optimized for many-core and large memory servers. MOT is a state-of-the-art production-grade feature (Beta release) of the MogDB database that provides greater performance for transactional workloads. MOT is fully ACID compliant and includes strict durability and high availability support. Businesses can leverage MOT for mission-critical, performance-sensitive Online Transaction Processing (OLTP) applications in order to achieve high performance, high throughput, low and predictable latency and high utilization of many-core servers. MOT is especially suited to leverage and scale-up when run on modern servers with multiple sockets and many-core processors, such as Huawei Taishan servers with ARM/Kunpeng processors and x86-based Dell or similar servers.
+
+**Figure 1** Memory-Optimized Storage Engine Within MogDB <a id="memoryoptimized"></a>
+
+![memory-optimized-storage-engine-within-opengauss](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-introduction-2.png)
+
+[Figure 1](#memoryoptimized) presents the Memory-Optimized Storage Engine component (in green) of MogDB database and is responsible for managing MOT and transactions.
+
+MOT tables are created side-by-side regular disk-based tables. MOT's effective design enables almost full SQL coverage and support for a full database feature-set, such as stored procedures and user-defined functions (excluding the features listed in **MOT SQL Coverage and Limitations** section).
+
+With data and indexes stored totally in-memory, a Non-Uniform Memory Access (NUMA)-aware design, algorithms that eliminate lock and latch contention and query native compilation, MOT provides faster data access and more efficient transaction execution.
+
+MOT's effective almost lock-free design and highly tuned implementation enable exceptional near-linear throughput scale-up on many-core servers - probably the best in the industry.
+
+Memory-Optimized Tables are fully ACID compliant, as follows:
+
+- **Atomicity -** An atomic transaction is an indivisible series of database operations that either all occur or none occur after a transaction has been completed (committed or aborted, respectively).
+- **Consistency -** Every transaction leaves the database in a consistent (data integrity) state.
+- **Isolation -** Transactions cannot interfere with each other. MOT supports repeatable-reads and read-committed isolation levels. In the next release, MOT will also support serializable isolation. See the **MOT Isolation Levels** section for more information.
+- **Durability -** The effects of successfully completed (committed) transactions must persist despite crashes and failures. MOT is fully integrated with the WAL-based logging of MogDB. Both synchronous and asynchronous logging options are supported. MOT also uniquely supports synchronous + group commit with NUMA-awareness optimization. See the **MOT Durability Concepts** section for more information.
+
+The MOT Engine was published in the VLDB 2020 (an International Conference on ‘Very Large Data Bases" or VLDB):
+
+**Industrial-Strength OLTP Using Main Memory and Many Cores**, VLDB 2020 vol. 13 - [Paper](http://www.vldb.org/pvldb/vol13/p3099-avni.pdf), [Video on youtube](https://www.youtube.com/watch?v=xcAbww6x8wo), [Video on bilibili](https://www.bilibili.com/video/BV1MA411n7ef?p=97).
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/1-introducing-mot/2-mot-features-and-benefits.md b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/1-introducing-mot/2-mot-features-and-benefits.md
new file mode 100644
index 0000000000000000000000000000000000000000..1713c463ebe20e1f1b972747b3cee069dc6de4ec
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/1-introducing-mot/2-mot-features-and-benefits.md
@@ -0,0 +1,22 @@
+---
+title: MOT Features and Benefits
+summary: MOT Features and Benefits
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# MOT Features and Benefits
+
+MOT provide users with significant benefits in performance (query and transaction latency), scalability (throughput and concurrency) and in some cases cost (high resource utilization) -
+
+- **Low Latency -** Provides fast query and transaction response time
+- **High Throughput -** Supports spikes and constantly high user concurrency
+- **High Resource Utilization -** Utilizes hardware to its full extent
+
+Using MOT, applications are able to achieve more 2.5 to 4 times (2.5x - 4x) higher throughput. For example, in our TPC-C benchmarks (interactive transactions and synchronous logging) performed both on Huawei Taishan Kunpeng-based (ARM) servers and on Dell x86 Intel Xeon-based servers, MOT provides throughput gains that vary from 2.5x on a 2-socket server to 3.7x on a 4-socket server, reaching 4.8M (million) tpmC on an ARM 4-socket 256-cores server.
+
+The lower latency provided by MOT reduces transaction speed by 3x to 5.5x, as observed in TPC-C benchmarks.
+
+Additionally, MOT enables extremely high utilization of server resources when running under high load and contention, which is a well-known problem for all leading industry databases. Using MOT, utilization reaches 99% on 4-socket server, compared with much lower utilization observed when testing other industry leading databases.
+
+This abilities are especially evident and important on modern many-core servers.
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/1-introducing-mot/3-mot-key-technologies.md b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/1-introducing-mot/3-mot-key-technologies.md
new file mode 100644
index 0000000000000000000000000000000000000000..3bf4108c17a46edc1a760b6734314a8939a4dea6
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/1-introducing-mot/3-mot-key-technologies.md
@@ -0,0 +1,24 @@
+---
+title: MOT Key Technologies
+summary: MOT Key Technologies
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# MOT Key Technologies
+
+The following key MOT technologies enable its benefits:
+
+- **Memory Optimized Data Structures -** With the objective of achieving optimal high concurrent throughput and predictable low latency, all data and indexes are in memory, no intermediate page buffers are used and minimal, short-duration locks are used. Data structures and all algorithms have been specialized and optimized for in-memory design.
+- **Lock-free Transaction Management -** The MOT storage engine applies an optimistic approach to achieving data integrity versus concurrency and high throughput. During a transaction, an MOT table does not place locks on any version of the data rows being updated, thus significantly reducing contention in some high-volume systems. Optimistic Concurrency Control (OCC) statements within a transaction are implemented without locks, and all data modifications are performed in a part of the memory that is dedicated to private transactions (also called *Private Transaction Memory*). This means that during a transaction, the relevant data is updated in the Private Transaction Memory, thus enabling lock-less reads and writes; and a very short duration lock is only placed at the Commit phase. For more details, see the **MOT Concurrency Control Mechanism** section.
+- **Lock-free Index -** Because database data and indexes stored totally in-memory, having an efficient index data structure and algorithm is essential. The MOT Index is based on state-of-the-art Masstree a fast and scalable Key Value (KV) store for multi-core systems, implemented as a Trie of B+ trees. In this way, excellent performance is achieved on many-core servers and during high concurrent workloads. This index applies various advanced techniques in order to optimize performance, such as an optimistic lock approach, cache-line awareness and memory prefetching.
+- **NUMA-aware Memory Management -** MOT memory access is designed with Non-Uniform Memory Access (NUMA) awareness. NUMA-aware algorithms enhance the performance of a data layout in memory so that threads access the memory that is physically attached to the core on which the thread is running. This is handled by the memory controller without requiring an extra hop by using an interconnect, such as Intel QPI. MOT's smart memory control module with pre-allocated memory pools for various memory objects improves performance, reduces locks and ensures stability. Allocation of a transaction's memory objects is always NUMA-local. Deallocated objects are returned to the pool. Minimal usage of OS malloc during transactions circumvents unnecessary locks.
+- **Efficient Durability - Logging and Checkpoint -** Achieving disk persistence (also known as *durability*) is a crucial requirement for being ACID compliant (the **D** stands for Durability). All current disks (including the SSD and NVMe) are significantly slower than memory and thus are always the bottleneck of a memory-based database. As an in-memory storage engine with full durability support, MOT's durability design must implement a wide variety of algorithmic optimizations in order to ensure durability, while still achieving the speed and throughput objectives for which it was designed. These optimizations include -
+  - Parallel logging, which is also available in all MogDB disk tables
+  - Log buffering per transaction and lock-less transaction preparation
+  - Updating delta records, meaning only logging changes
+  - In addition to synchronous and asynchronous, innovative NUMA-aware group commit logging
+  - State-of-the-art database checkpoints (CALC) enable the lowest memory and computational overhead.
+- **High SQL Coverage and Feature Set -** By extending and relying on the PostgreSQL Foreign Data Wrappers (FDW) + Index support, the entire range of SQL is covered, including stored procedures, user-defined functions and system function calls. You may refer to the **MOT SQL Coverage and Limitations** section for a list of the features that are not supported.
+- **Queries Native Compilation using PREPARE Statements -** Queries and transaction statements can be executed in an interactive manner by using PREPARE client commands that have been precompiled into a native execution format (which are also known as *Code-Gen* or *Just-in-Time [JIT]* compilation). This achieves an average of 30% higher performance. Compilation and Lite Execution are applied when possible, and if not, applicable queries are processed using the standard execution path. A Cache Plan module (that has been optimized for OLTP) re-uses compilation results throughout an entire session (even using different bind settings), as well as across different sessions.
+- **Seamless Integration of MOT and MogDB Database -** The MOT operates side by side the disk-based storage engine within an integrated envelope. MOT's main memory engine and disk-based storage engines co-exist side by side in order to support multiple application scenarios, while internally reusing database auxiliary services, such as a Write-Ahead Logging (WAL) Redo Log, Replication, Checkpointing, Recovery, High Availability and so on. Users benefit from the unified deployment, configuration and access of both disk-based tables and MOT tables. This provides a flexible and cost-efficient choice of which storage engine to use according to specific requirements. For example, to place highly performance-sensitive data that causes bottlenecks into memory.
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/1-introducing-mot/4-mot-usage-scenarios.md b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/1-introducing-mot/4-mot-usage-scenarios.md
new file mode 100644
index 0000000000000000000000000000000000000000..ef56b9ec8f19f87d2a511506afaed5bbae603f48
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/1-introducing-mot/4-mot-usage-scenarios.md
@@ -0,0 +1,22 @@
+---
+title: MOT Usage Scenarios
+summary: MOT Usage Scenarios
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# MOT Usage Scenarios
+
+MOT can significantly speed up an application's overall performance, depending on the characteristics of the workload. MOT improves the performance of transaction processing by making data access and transaction execution more efficient and minimizing redirections by removing lock and latch contention between concurrently executing transactions.
+
+MOT's extreme speed stems from the fact that it is optimized around concurrent in-memory usage management (not just because it is in memory). Data storage, access and processing algorithms were designed from the ground up to take advantage of the latest state of the art enhancements in in-memory and high-concurrency computing.
+
+MogDB enables an application to use any combination of MOT tables and standard disk-based tables. MOT is especially beneficial for enabling your most active, high-contention and performance-sensitive application tables that have proven to be bottlenecks and for tables that require a predictable low-latency access and high throughput.
+
+MOT tables can be used for a variety of application use cases, which include:
+
+- **High-throughput Transactions Processing -** This is the primary scenario for using MOT, because it supports large transaction volume that requires consistently low latency for individual transactions. Examples of such applications are real-time decision systems, payment systems, financial instrument trading, sports betting, mobile gaming, ad delivery and so on.
+- **Acceleration of Performance Bottlenecks -** High contention tables can significantly benefit from using MOT, even when other tables are on disk. The conversion of such tables (in addition to related tables and tables that are referenced together in queries and transactions) result in a significant performance boost as the result of lower latencies, less contention and locks, and increased server throughput ability.
+- **Elimination of Mid-Tier Cache -** Cloud and Mobile applications tend to have periodic or spikes of massive workload. Additionally, many of these applications have 80% or above read-workload, with frequent repetitive queries. To sustain the workload spikes, as well to provide optimal user experience by low-latency response time, applications sometimes deploy a mid-tier caching layer. Such additional layers increase development complexity and time, and also increase operational costs. MOT provides a great alternative, simplifying the application architecture with a consistent and high performance data store, while shortening development cycles and reducing CAPEX and OPEX costs.
+- **Large-scale Data Streaming and Data Ingestion -** MOT tables enables large-scale streamlined data processing in the Cloud (for Mobile, M2M and IoT), Transactional Processing (TP), Analytical Processing (AP) and Machine Learning (ML). MOT tables are especially good at consistently and quickly ingesting large volumes of data from many different sources at the same time. The data can be later processed, transformed and moved in slower disk-based tables. Alternatively, MOT enables the querying of consistent and up-date data that enable real-time conclusions. In IoT and cloud applications with many real-time data streams, it is common to have special data ingestion and processing triers. For instance, an Apache Kafka cluster can be used to ingest data of 100,000 events/sec with a 10msec latency. A periodic batch processing task enriches and converts the collected data into an alternative format to be placed into a relational database for further analysis. MOT can support such scenarios (while eliminating the separate data ingestion tier) by ingesting data streams directly into MOT relational tables, ready for analysis and decisions. This enables faster data collection and processing, MOT eliminates costly tiers and slow batch processing, increases consistency, increases freshness of analyzed data, as well as lowers Total Cost of Ownership (TCO).
+- **Lower TCO -** Higher resource efficiency and mid-tier elimination can save 30% to 90%.
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/1-introducing-mot/5-mot-performance-benchmarks.md b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/1-introducing-mot/5-mot-performance-benchmarks.md
new file mode 100644
index 0000000000000000000000000000000000000000..5a113129038e098d2736fb5b33db0614799e3493
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/1-introducing-mot/5-mot-performance-benchmarks.md
@@ -0,0 +1,189 @@
+---
+title: MOT Performance Benchmarks
+summary: MOT Performance Benchmarks
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# MOT Performance Benchmarks
+
+Our performance tests are based on the TPC-C Benchmark that is commonly used both by industry and academia.
+
+Ours tests used BenchmarkSQL (see **MOT Sample TPC-C Benchmark**) and generates the workload using interactive SQL commands, as opposed to stored procedures.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** Using the stored procedures approach may produce even higher performance results because it involves significantly less networking roundtrips and database envelope SQL processing cycles.
+
+All tests that evaluated the performance of MogDB MOT vs DISK used synchronous logging and its optimized **group-commit=on** version in MOT.
+
+Finally, we performed an additional test in order to evaluate MOT's ability to quickly and ingest massive quantities of data and to serve as an alternative to a mid-tier data ingestion solutions.
+
+All tests were performed in June 2020.
+
+The following shows various types of MOT performance benchmarks.
+
+## MOT Hardware
+
+The tests were performed on servers with the following configuration and with 10Gbe networking -
+
+- ARM64/Kunpeng 920-based 2-socket servers, model Taishan 2280 v2 (total 128 Cores), 800GB RAM, 1TB NVMe disk. For a detailed server specification, see - <https://e.huawei.com/en/products/servers/taishan-server/taishan-2480-v2> OS: openEuler
+
+- ARM64/Kunpeng 960-based 4-socket servers, model Taishan 2480 v2 (total 256 Cores), 512GB RAM, 1TB NVMe disk. For a detailed server specification, see - <https://e.huawei.com/en/products/servers/taishan-server/taishan-2480-v2> OS: openEuler
+
+- x86-based Dell servers, with 2-sockets of Intel Xeon Gold 6154 CPU @ 3GHz with 18 Cores (72 Cores, with hyper-threading=on), 1TB RAM, 1TB SSD OS: CentOS 7.6
+
+- x86-based SuperMicro server, with 8-sockets of Intel(R) Xeon(R) CPU E7-8890 v4 @ 2.20GHz 24 cores (total 384 Cores, with hyper-threading=on), 1TB RAM, 1.2TB SSD (Seagate 1200 SSD 200GB, SAS 12Gb/s). OS: Ubuntu 16.04.2 LTS
+
+- x86-based Huawei server, with 4-sockets of Intel(R) Xeon(R) CPU E7-8890 v4 2.2Ghz (total 96 Cores, with hyper-threading=on), 512GB RAM, SSD 2TB OS: CentOS 7.6
+
+## MOT Results - Summary
+
+MOT provides higher performance than disk-tables by a factor of 2.5x to 4.1x and reaches 4.8 million tpmC on ARM/Kunpeng-based servers with 256 cores. The results clearly demonstrate MOT's exceptional ability to scale-up and utilize all hardware resources. Performance jumps as the quantity of CPU sockets and server cores increases.
+
+MOT delivers up to 30,000 tpmC/core on ARM/Kunpeng-based servers and up to 40,000 tpmC/core on x86-based servers.
+
+Due to a more efficient durability mechanism, in MOT the replication overhead of a Primary/Secondary High Availability scenario is 7% on ARM/Kunpeng and 2% on x86 servers, as opposed to the overhead in disk tables of 20% on ARM/Kunpeng and 15% on x86 servers.
+
+Finally, MOT delivers 2.5x lower latency, with TPC-C transaction response times of 2 to 7 times faster.
+
+## MOT High Throughput
+
+The following shows the results of various MOT table high throughput tests.
+
+### ARM/Kunpeng 2-Socket 128 Cores
+
+**Performance**
+
+The following figure shows the results of testing the TPC-C benchmark on a Huawei ARM/Kunpeng server that has two sockets and 128 cores.
+
+Four types of tests were performed -
+
+- Two tests were performed on MOT tables and another two tests were performed on MogDB disk-based tables.
+- Two of the tests were performed on a Single node (without high availability), meaning that no replication was performed to a secondary node. The other two tests were performed on Primary/Secondary nodes (with high availability), meaning that data written to the primary node was replicated to a secondary node.
+
+MOT tables are represented in orange and disk-based tables are represented in blue.
+
+**Figure 1** ARM/Kunpeng 2-Socket 128 Cores - Performance Benchmarks
+
+![arm-kunpeng-2-socket-128-cores-performance-benchmarks](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-performance-benchmarks-10.png)
+
+The results showed that:
+
+- As expected, the performance of MOT tables is significantly greater than of disk-based tables in all cases.
+- For a Single Node - 3.8M tpmC for MOT tables versus 1.5M tpmC for disk-based tables
+- For a Primary/Secondary Node - 3.5M tpmC for MOT tables versus 1.2M tpmC for disk-based tables
+- For production grade (high-availability) servers (Primary/Secondary Node) that require replication, the benefit of using MOT tables is even more significant than for a Single Node (without high-availability, meaning no replication).
+- The MOT replication overhead of a Primary/Secondary High Availability scenario is 7% on ARM/Kunpeng and 2% on x86 servers, as opposed to the overhead of disk tables of 20% on ARM/Kunpeng and 15% on x86 servers.
+
+**Performance per CPU core**
+
+The following figure shows the TPC-C benchmark performance/throughput results per core of the tests performed on a Huawei ARM/Kunpeng server that has two sockets and 128 cores. The same four types of tests were performed (as described above).
+
+**Figure 2** ARM/Kunpeng 2-Socket 128 Cores - Performance per Core Benchmarks
+
+![arm-kunpeng-2-socket-128-cores-performance-per-core-benchmarks](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-performance-benchmarks-11.png)
+
+The results showed that as expected, the performance of MOT tables is significantly greater per core than of disk-based tables in all cases. It also shows that for production grade (high-availability) servers (Primary/Secondary Node) that require replication, the benefit of using MOT tables is even more significant than for a Single Node (without high-availability, meaning no replication).
+
+### ARM/Kunpeng 4-Socket 256 Cores
+
+The following demonstrates MOT's excellent concurrency control performance by showing the tpmC per quantity of connections.
+
+**Figure 3** ARM/Kunpeng 4-Socket 256 Cores - Performance Benchmarks
+
+![arm-kunpeng-4-socket-256-cores-performance-benchmarks](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-performance-benchmarks-12.png)
+
+The results show that performance increases significantly even when there are many cores and that peak performance of 4.8M tpmC is achieved at 768 connections.
+
+### x86-based Servers
+
+- **8-Socket 384 Cores**
+
+The following demonstrates MOT’s excellent concurrency control performance by comparing the tpmC per quantity of connections between disk-based tables and MOT. This test was performed on an x86 server with eight sockets and 384 cores. The orange represents the results of the MOT table.
+
+**Figure 4** x86 8-Socket 384 Cores - Performance Benchmarks
+
+![x86-8-socket-384-cores-performance-benchmarks](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-performance-benchmarks-13.png)
+
+The results show that MOT tables significantly outperform disk-based tables and have very highly efficient performance per core on a 386 core server, reaching over 3M tpmC / core.
+
+- **4-Socket 96 Cores**
+
+3.9 million tpmC was achieved by MOT on this 4-socket 96 cores server. The following figure shows a highly efficient MOT table performance per core reaching 40,000 tpmC / core.
+
+**Figure 5** 4-Socket 96 Cores - Performance Benchmarks
+
+![4-socket-96-cores-performance-benchmarks](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-performance-benchmarks-14.png)
+
+## MOT Low Latency
+
+The following was measured on ARM/Kunpeng 2-socket server (128 cores). The numbers scale is milliseconds (ms).
+
+**Figure 1** Low Latency (90th%) - Performance Benchmarks
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-performance-benchmarks-15.png)
+
+MOT's average transaction speed is 2.5x, with MOT latency of 10.5 ms, compared to 23-25ms for disk tables.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The average was calculated by taking into account all TPC-C 5 transaction percentage distributions. For more information, you may refer to the description of TPC-C transactions in the **MOT Sample TPC-C Benchmark** section.
+
+**Figure 2** Low Latency (90th%, Transaction Average) - Performance Benchmarks
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-performance-benchmarks-16.png)
+
+## MOT RTO and Cold-Start Time
+
+### High Availability Recovery Time Objective (RTO)
+
+MOT is fully integrated into MogDB, including support for high-availability scenarios consisting of primary and secondary deployments. The WAL Redo Log's replication mechanism replicates changes into the secondary database node and uses it for replay.
+
+If a Failover event occurs, whether it is due to an unplanned primary node failure or due to a planned maintenance event, the secondary node quickly becomes active. The amount of time that it takes to recover and replay the WAL Redo Log and to enable connections is also referred to as the Recovery Time Objective (RTO).
+
+**The RTO of MogDB, including the MOT, is less than 10 seconds.**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The Recovery Time Objective (RTO) is the duration of time and a service level within which a business process must be restored after a disaster in order to avoid unacceptable consequences associated with a break in continuity. In other words, the RTO is the answer to the question: "How much time did it take to recover after notification of a business process disruption?"
+
+In addition, as shown in the **MOT High Throughput** section in MOT the replication overhead of a Primary/Secondary High Availability scenario is only 7% on ARM/Kunpeng servers and 2% on x86 servers, as opposed to the replication overhead of disk-tables, which is 20% on ARM/Kunpeng and 15% on x86 servers.
+
+### Cold-Start Recovery Time
+
+Cold-start Recovery time is the amount of time it takes for a system to become fully operational after a stopped mode. In memory databases, this includes the loading of all data and indexes into memory, thus it depends on data size, hardware bandwidth, and on software algorithms to process it efficiently.
+
+Our MOT tests using ARM servers with NVMe disks demonstrate the ability to load **100 GB of database checkpoint in 40 seconds (2.5 GB/sec)**. Because MOT does not persist indexes and therefore they are created at cold-start, the actual size of the loaded data + indexes is approximately 50% more. Therefore, can be converted to **MOT cold-start time of Data + Index capacity of 150GB in 40 seconds,** or **225 GB per minute (3.75 GB/sec)**.
+
+The following figure demonstrates cold-start process and how long it takes to load data into a MOT table from the disk after a cold start.
+
+**Figure 1** Cold-Start Time - Performance Benchmarks
+
+![cold-start-time-performance-benchmarks](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-performance-benchmarks-17.png)
+
+- **Database Size -** The total amount of time to load the entire database (in GB) is represented by the blue line and the **TIME (sec)** Y axis on the left.
+- **Throughput -** The quantity of database GB throughput per second is represented by the orange line and the **Throughput GB/sec** Y axis on the right.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The performance demonstrated during the test is very close to the bandwidth of the SSD hardware. Therefore, it is feasible that higher (or lower) performance may be achieved on a different platform.
+
+## MOT Resource Utilization
+
+The following figure shows the resource utilization of the test performed on a x86 server with four sockets, 96 cores and 512GB RAM server. It demonstrates that a MOT table is able to efficiently and consistently consume almost all available CPU resources. For example, it shows that almost 100% CPU percentage utilization is achieved for 192 cores and 3.9M tpmC.
+
+- **tmpC -** Number of TPC-C transactions completed per minute is represented by the orange bar and the **tpmC** Y axis on the left.
+- **CPU % Utilization -** The amount of CPU utilization is represented by the blue line and the **CPU %** Y axis on the right.
+
+**Figure 1** Resource Utilization - Performance Benchmarks
+
+![resource-utilization-performance-benchmarks](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-performance-benchmarks-18.png)
+
+## MOT Data Ingestion Speed
+
+This test simulates realtime data streams arriving from massive IoT, cloud or mobile devices that need to be quickly and continuously ingested into the database on a massive scale.
+
+- The test involved ingesting large quantities of data, as follows -
+
+  - 10 million rows were sent by 500 threads, 2000 rounds, 10 records (rows) in each insert command, each record was 200 bytes.
+  - The client and database were on different machines. Database server - x86 2-socket, 72 cores.
+
+- Performance Results
+
+  - **Throughput - 10,000** Records/Core or **2** MB/Core.
+  - **Latency - 2.8ms per a 10 records** bulk insert (includes client-server networking)
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **CAUTION:** We are projecting that multiple additional, and even significant, performance improvements will be made by MOT for this scenario. Click **MOT Usage Scenarios** for more information about large-scale data streaming and data ingestion.
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/1-using-mot-overview.md b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/1-using-mot-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..a54764d553c93fc863a8b68b0005e8abd5bab3ce
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/1-using-mot-overview.md
@@ -0,0 +1,18 @@
+---
+title: Using MOT Overview
+summary: Using MOT Overview
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# Using MOT Overview
+
+MOT is automatically deployed as part of openGauss. You may refer to the **MOT Preparation** section for a description of how to estimate and plan required memory and storage resources in order to sustain your workload. The **MOT Deployment** section describes all the configuration settings in MOT, as well as non-mandatory options for server optimization.
+
+Using MOT tables is quite simple. The syntax of all MOT commands is the same as for disk-based tables and includes support for most of standard PostgreSQL SQL, DDL and DML commands and features, such as Stored Procedures. Only the create and drop table statements in MOT differ from the statements for disk-based tables in openGauss. You may refer to the **MOT Usage** section for a description of these two simple commands, to learn how to convert a disk-based table into an MOT table, to get higher performance using Query Native Compilation and PREPARE statements and for a description of external tool support and the limitations of the MOT engine.
+
+The **MOT Administration** section describes how to perform database maintenance, monitoring and analysis of logs and reported errors. Lastly, the **MOT Sample TPC-C Benchmark** section describes how to perform a standard TPC-C benchmark.
+
+- Read the following topics to learn how to use MOT -
+
+  ![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/using-mot-overview-2.png)
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/2-mot-preparation.md b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/2-mot-preparation.md
new file mode 100644
index 0000000000000000000000000000000000000000..3cceb8b2a61ef33fce7dd877b24daca2f1e19efb
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/2-mot-preparation.md
@@ -0,0 +1,206 @@
+---
+title: MOT Preparation
+summary: MOT Preparation
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# MOT Preparation
+
+The following describes the prerequisites and the memory and storage planning to perform in order to prepare to use MOT.
+
+## MOT Prerequisites
+
+The following specifies the hardware and software prerequisites for using MogDB MOT.
+
+### Supported Hardware
+
+MOT can utilize state-of-the-art hardware, as well as support existing hardware platforms. Both x86 architecture and ARM by Huawei Kunpeng architecture are supported.
+
+MOT is fully aligned with the hardware supported by the MogDB database. For more information, see the *MogDB Installation Guide*.
+
+### CPU
+
+MOT delivers exceptional performance on many-core servers (scale-up). MOT significantly outperforms the competition in these environments and provides near-linear scaling and extremely high resource utilization.
+
+Even so, users can already start realizing MOT's performance benefits on both low-end, mid-range and high-end servers, starting from one or two CPU sockets, as well as four and even eight CPU sockets. Very high performance and resource utilization are also expected on very high-end servers that have 16 or even 32 sockets (for such cases, we recommend contacting Enmo support).
+
+### Memory
+
+MOT supports standard RAM/DRAM for its data and transaction management. All MOT tables’ data and indexes reside in-memory; therefore, the memory capacity must support the data capacity and still have space for further growth. For detailed information about memory requirements and planning, see the **MOT Memory and Storage Planning** section.
+
+### Storage IO
+
+MOT is a durable database and uses persistent storage (disk/SSD/NVMe drive[s]) for transaction log operations and periodic checkpoints.
+
+We recommend using a storage device with low latency, such as SSD with a RAID-1 configuration, NVMe or any enterprise-grade storage system. When appropriate hardware is used, the database transaction processing and contention are the bottleneck, not the IO.
+
+For detailed memory requirements and planning, see the **MOT Memory and Storage Planning** section.
+
+Supported Operating Systems
+
+MOT is fully aligned with the operating systems supported by MogDB.
+
+MOT supports both bare-metal and virtualized environments that run the following operating systems on a bare-metal server or virtual machine -
+
+- **x86 -** CentOS 7.6 and EulerOS 2.0
+- **ARM -** openEuler and EulerOS
+
+### OS Optimization
+
+MOT does not require any special modifications or the installation of new software. However, several optional optimizations can enhance performance. You may refer to the **MOT Server Optimization - x86** and **MOT Server Optimization - ARM Huawei Taishan 2P/4P** sections for a description of the optimizations that enable maximal performance.
+
+## MOT Memory and Storage Planning
+
+This section describes the considerations and guidelines for evaluating, estimating and planning the quantity of memory and storage capacity to suit your specific application needs. This section also describes the various data aspects that affect the quantity of required memory, such as the size of data and indexes for the planned tables, memory to sustain transaction management and how fast the data is growing.
+
+### MOT Memory Planning
+
+MOT belongs to the in-memory database class (IMDB) in which all tables and indexes reside entirely in memory.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** Memory storage is volatile, meaning that it requires power to maintain the stored information. Disk storage is persistent, meaning that it is written to disk, which is non-volatile storage. MOT uses both, having all data in memory, while persisting (by WAL logging) transactional changes to disk with strict consistency (in synchronous logging mode).
+
+Sufficient physical memory must exist on the server in order to maintain the tables in their initial state, as well as to accommodate the related workload and growth of data. All this is in addition to the memory that is required for the traditional disk-based engine, tables and sessions that support the workload of disk-based tables. Therefore, planning ahead for enough memory to contain them all is essential.
+
+Even so, you can get started with whatever amount of memory you have and perform basic tasks and evaluation tests. Later, when you are ready for production, the following issues should be addressed.
+
+- **Memory Configuration Settings**
+
+  Similar to standard PG , the memory of the MogDB database process is controlled by the upper limit in its max_process_memory setting, which is defined in the postgres.conf file. The MOT engine and all its components and threads, reside within the MogDB process. Therefore, the memory allocated to MOT also operates within the upper boundary defined by max_process_memory for the entire MogDB database process.
+
+  The amount of memory that MOT can reserve for itself is defined as a portion of max_process_memory. It is either a percentage of it or an absolute value that is less than it. This portion is defined in the mot.conf configuration file by the _mot__memory settings.
+
+  The portion of max_process_memory that can be used by MOT must still leave at least 2 GB available for the PG (MogDB) envelope. Therefore, in order to ensure this, MOT verifies the following during database startup -
+
+  ```
+  (max_mot_global_memory + max_mot_local_memory) + 2GB < max_process_memory
+  ```
+
+  If this limit is breached, then MOT memory internal limits are adjusted in order to provide the maximum possible within the limitations described above. This adjustment is performed during startup and calculates the value of MOT max memory accordingly.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** MOT max memory is a logically calculated value of either the configured settings or their adjusted values of (max_mot_global_memory + max_mot_local_memory).
+
+  In this case, a warning is issued to the server log, as shown below -
+
+  **Warning Examples**
+
+  Two messages are reported - the problem and the solution.
+
+  The following is an example of a warning message reporting the problem -
+
+  ```
+  [WARNING] <Configuration> MOT engine maximum memory definitions (global: 9830 MB, local: 1843 MB, session large store: 0 MB, total: 11673 MB) breach GaussDB maximum process memory restriction (12288 MB) and/or total system memory (64243 MB). MOT values shall be adjusted accordingly to preserve required gap (2048 MB).
+  ```
+
+  The following is an example of a warning message indicating that MOT is automatically adjusting the memory limits -
+
+  ```
+  [WARNING] <Configuration> Adjusting MOT memory limits: global = 8623 MB, local = 1617 MB, session large store = 0 MB, total = 10240 MB
+  ```
+
+  This is the only place that shows the new memory limits.
+
+  Additionally, MOT does not allow the insertion of additional data when the total memory usage approaches the chosen memory limits. The threshold for determining when additional data insertions are no longer allowed, is defined as a percentage of MOT max memory (which is a calculated value, as described above). The default is 90, meaning 90%. Attempting to add additional data over this threshold returns an error to the user and is also registered in the database log file.
+
+- **Minimum and Maximum**
+
+  In order to secure memory for future operations, MOT pre-allocates memory based on the minimum global and local settings. The database administrator should specify the minimum amount of memory required for the MOT tables and sessions to sustain their workload. This ensures that this minimal memory is allocated to MOT even if another excessive memory-consuming application runs on the same server as the database and competes with the database for memory resources. The maximum values are used to limit memory growth.
+
+- **Global and Local**
+
+    The memory used by MOT is comprised of two parts -
+
+  - **Global Memory -** Global memory is a long-term memory pool that contains the data and indexes of MOT tables. It is evenly distributed across NUMA-nodes and is shared by all CPU cores.
+  - **Local Memory -** Local memory is a memory pool used for short-term objects. Its primary consumers are sessions handling transactions. These sessions are storing data changes in the part of the memory dedicated to the relevant specific transaction (known as *transaction private memory*). Data changes are moved to the global memory at the commit phase. Memory object allocation is performed in NUMA-local manner in order to achieve the lowest possible latency.
+
+    Deallocated objects are put back in the relevant memory pools. Minimal use of operating system memory allocation (malloc) functions during transactions circumvents unnecessary locks and latches.
+
+    The allocation of these two memory parts is controlled by the dedicated **min/max_mot_global_memory** and **min/max_mot_local_memory** settings. If MOT global memory usage gets too close to this defined maximum, then MOT protects itself and does not accept new data. Attempts to allocate memory beyond this limit are denied and an error is reported to the user.
+
+- **Minimum Memory Requirements**
+
+  To get started and perform a minimal evaluation of MOT performance, there are a few requirements.
+
+  Make sure that the **max_process_memory** (as defined in **postgres.conf**) has sufficient capacity for MOT tables and sessions (configured by **mix/max_mot_global_memory** and **mix/max_mot_local_memory**), in addition to the disk tables buffer and extra memory. For simple tests, the default **mot.conf** settings can be used.
+
+- **Actual Memory Requirements During Production**
+
+  In a typical OLTP workload, with 80:20 read:write ratio on average, MOT memory usage per table is 60% higher than in disk-based tables (this includes both the data and the indexes). This is due to the use of more optimal data structures and algorithms that enable faster access, with CPU-cache awareness and memory-prefetching.
+
+  The actual memory requirement for a specific application depends on the quantity of data, the expected workload and especially on the data growth.
+
+- **Max Global Memory Planning - Data + Index Size**
+
+  To plan for maximum global memory -
+
+  1. Determine the size of a specific disk table (including both its data and all its indexes). The following statistical query can be used to determine the data size of the **customer** table and the **customer_pkey** index size -
+     - **Data size -** select pg_relation_size(‘customer');
+     - **Index -** select pg_relation_size('customer_pkey');
+  2. Add 60%, which is the common requirement in MOT relative to the current size of the disk-based data and index.
+  3. Add an additional percentage for the expected growth of data. For example -
+
+  5% monthly growth = 80% yearly growth (1.05^12). Thus, in order to sustain a year's growth, allocate 80% more memory than is currently used by the tables.
+
+  This completes the estimation and planning of the max_mot_global_memory value. The actual setting can be defined either as an absolute value or a percentage of the Postgres max_process_memory. The exact value is typically finetuned during deployment.
+
+- **Max Local Memory Planning - Concurrent Session Support**
+
+  Local memory needs are primarily a function of the quantity of concurrent sessions. The typical OLTP workload of an average session uses up to 8 MB. This should be multiplied by the quantity of sessions and then a little bit extra should be added.
+
+  A memory calculation can be performed in this manner and then finetuned, as follows -
+
+  ```
+  SESSION_COUNT * SESSION_SIZE (8 MB) + SOME_EXTRA (100MB should be enough)
+  ```
+
+  The default specifies 15% of Postgres's max_process_memory, which by default is 12 GB. This equals 1.8 GB, which is sufficient for 230 sessions, which is the requirement for the max_mot_local memory. The actual setting can be defined either in absolute values or as a percentage of the Postgres max_process_memory. The exact value is typically finetuned during deployment.
+
+  **Unusually Large Transactions**
+
+  Some transactions are unusually large because they apply changes to a large number of rows. This may increase a single session's local memory up to the maximum allowed limit, which is 1 GB. For example -
+
+  ```
+  delete from SOME_VERY_LARGE_TABLE;
+  ```
+
+  Take this scenario into consideration when configuring the max_mot_local_memory setting, as well as during application development.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** You may refer to the **MEMORY (MOT)** section for more information about configuration settings.
+
+### Storage IO
+
+MOT is a memory-optimized, persistent database storage engine. A disk drive(s) is required for storing the Redo Log (WAL) and a periodic checkpoint.
+
+It is recommended to use a storage device with low latency, such as SSD with a RAID-1 configuration, NVMe or any enterprise-grade storage system. When appropriate hardware is used, the database transaction processing and contention are the bottleneck, not the IO.
+
+Since the persistent storage is much slower than RAM memory, the IO operations (logging and checkpoint) can create a bottleneck for both an in-memory and memory-optimized databases. However, MOT has a highly efficient durability design and implementation that is optimized for modern hardware (such as SSD and NVMe). In addition, MOT has minimized and optimized writing points (for example, by using parallel logging, a single log record per transaction and NUMA-aware transaction group writing) and has minimized the data written to disk (for example, only logging the delta or updated columns of the changed records and only logging a transaction at the commit phase).
+
+### Required Capacity
+
+The required capacity is determined by the requirements of checkpointing and logging, as described below -
+
+- **Checkpointing**
+
+  A checkpoint saves a snapshot of all the data to disk.
+
+  Twice the size of all data should be allocated for checkpointing. There is no need to allocate space for the indexes for checkpointing
+
+  Checkpointing = 2x the MOT Data Size (rows only, index is not persistent).
+
+  Twice the size is required because a snapshot is saved to disk of the entire size of the data, and in addition, the same amount of space should be allocated for the checkpoint that is in progress. When a checkpoint process finishes, the previous checkpoint files are deleted.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** In the next MogDB release, MOT will have an incremental checkpoint feature, which will significantly reduce this storage capacity requirement.
+
+- **Logging**
+
+  MOT table log records are written to the same database transaction log as the other records of disk-based tables.
+
+  The size of the log depends on the transactional throughput, the size of the data changes and the time between checkpoints (at each time checkpoint the Redo Log is truncated and starts to expand again).
+
+  MOT tables use less log bandwidth and have lower IO contention than disk-based tables. This is enabled by multiple mechanisms.
+
+  For example, MOT does not log every operation before a transaction has been completed. It is only logged at the commit phase and only the updated delta record is logged (not full records like for disk-based tables).
+
+  In order to ensure that the log IO device does not become a bottleneck, the log file must be placed on a drive that has low latency.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** You may refer to the **STORAGE (MOT)** section for more information about configuration settings.
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/3-mot-deployment.md b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/3-mot-deployment.md
new file mode 100644
index 0000000000000000000000000000000000000000..1bf1320b9f6b91492427e40529ee6ffe2eb1c133
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/3-mot-deployment.md
@@ -0,0 +1,660 @@
+---
+title: MOT Deployment
+summary: MOT Deployment
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# MOT Deployment
+
+The following sections describe various mandatory and optional settings for optimal deployment.
+
+## MOT Server Optimization - x86
+
+Generally, databases are bounded by the following components -
+
+- **CPU -** A faster CPU speeds up any CPU-bound database.
+- **Disk -** High-speed SSD/NVME speeds up any I/O-bound database.
+- **Network -** A faster network speeds up any **SQL\\Net**-bound database.
+
+In addition to the above, the following general-purpose server settings are used by default and may significantly affect a database's performance.
+
+MOT performance tuning is a crucial step for ensuring fast application functionality and data retrieval. MOT can utilize state-of-the-art hardware, and therefore it is extremely important to tune each system in order to achieve maximum throughput.
+
+The following are optional settings for optimizing MOT database performance running on an Intel x86 server. These settings are optimal for high throughput workloads -
+
+### BIOS
+
+- Hyper Threading - ON
+
+  Activation (HT=ON) is highly recommended.
+
+  We recommend turning hyper threading ON while running OLTP workloads on MOT. When hyper-threading is used, some OLTP workloads demonstrate performance gains of up to40%.
+
+### OS Environment Settings
+
+- NUMA
+
+  Disable NUMA balancing, as described below. MOT performs its own memory management with extremely efficient NUMA-awareness, much more than the default methods used by the operating system.
+
+  ```
+  echo 0 > /proc/sys/kernel/numa_balancing
+  ```
+
+- Services
+
+  Disable Services, as described below -
+
+  ```
+  service irqbalance stop           # MANADATORY
+  service sysmonitor stop           # OPTIONAL, performance
+  service rsyslog stop       # OPTIONAL, performance
+  ```
+
+- Tuned Service
+
+  The following section is mandatory.
+
+  The server must run the throughput-performance profile -
+
+  ```
+  [...]$ tuned-adm profile throughput-performance
+  ```
+
+  The **throughput-performance** profile is broadly applicable tuning that provides excellent performance across a variety of common server workloads.
+
+  Other less suitable profiles for MogDB and MOT server that may affect MOT's overall performance are - balanced, desktop, latency-performance, network-latency, network-throughput and powersave.
+
+- Sysctl
+
+    The following lists the recommended operating system settings for best performance.
+
+  - Add the following settings to /etc/sysctl.conf and run sysctl -p
+
+    ```bash
+    net.ipv4.ip_local_port_range = 9000 65535
+    kernel.sysrq = 1
+    kernel.panic_on_oops = 1
+    kernel.panic = 5
+    kernel.hung_task_timeout_secs = 3600
+    kernel.hung_task_panic = 1
+    vm.oom_dump_tasks = 1
+    kernel.softlockup_panic = 1
+    fs.file-max = 640000
+    kernel.msgmnb = 7000000
+    kernel.sched_min_granularity_ns = 10000000
+    kernel.sched_wakeup_granularity_ns = 15000000
+    kernel.numa_balancing=0
+    vm.max_map_count = 1048576
+    net.ipv4.tcp_max_tw_buckets = 10000
+    net.ipv4.tcp_tw_reuse = 1
+    net.ipv4.tcp_tw_recycle = 1
+    net.ipv4.tcp_keepalive_time = 30
+    net.ipv4.tcp_keepalive_probes = 9
+    net.ipv4.tcp_keepalive_intvl = 30
+    net.ipv4.tcp_retries2 = 80
+    kernel.sem = 250 6400000 1000 25600
+    net.core.wmem_max = 21299200
+    net.core.rmem_max = 21299200
+    net.core.wmem_default = 21299200
+    net.core.rmem_default = 21299200
+    #net.sctp.sctp_mem = 94500000 915000000 927000000
+    #net.sctp.sctp_rmem = 8192 250000 16777216
+    #net.sctp.sctp_wmem = 8192 250000 16777216
+    net.ipv4.tcp_rmem = 8192 250000 16777216
+    net.ipv4.tcp_wmem = 8192 250000 16777216
+    net.core.somaxconn = 65535
+    vm.min_free_kbytes = 26351629
+    net.core.netdev_max_backlog = 65535
+    net.ipv4.tcp_max_syn_backlog = 65535
+    #net.sctp.addip_enable = 0
+    net.ipv4.tcp_syncookies = 1
+    vm.overcommit_memory = 0
+    net.ipv4.tcp_retries1 = 5
+    net.ipv4.tcp_syn_retries = 5
+    ```
+
+  - Update the section of /etc/security/limits.conf to the following -
+
+    ```bash
+    <user> soft nofile 100000
+    <user> hard nofile 100000
+    ```
+
+    The **soft** and a **hard** limit settings specify the quantity of files that a process may have opened at once. The soft limit may be changed by each process running these limits up to the hard limit value.
+
+- Disk/SSD
+
+  The following describes how to ensure that disk R/W performance is suitable for database synchronous commit mode.
+
+  To do so, test your disk bandwidth using the following
+
+  ```
+  [...]$ sync; dd if=/dev/zero of=testfile bs=1M count=1024; sync
+  1024+0 records in
+  1024+0 records out
+  1073741824 bytes (1.1 GB) copied, 1.36034 s, 789 MB/s
+  ```
+
+  In case the disk bandwidth is significantly below the above number (789 MB/s), it may create a performance bottleneck for MogDB, and especially for MOT.
+
+### Network
+
+Use a 10Gbps network or higher.
+
+To verify, use iperf, as follows -
+
+```
+Server side: iperf -s
+Client side: iperf -c <IP>
+```
+
+- rc.local - Network Card Tuning
+
+  The following optional settings have a significant effect on performance -
+
+  1. Copy set_irq_affinity.sh from <https://gist.github.com/SaveTheRbtz/8875474> to /var/scripts/.
+
+  2. Put in /etc/rc.d/rc.local and run chmod in order to ensure that the following script is executed during boot -
+
+     ```bash
+     chmod +x /etc/rc.d/rc.local
+     var/scripts/set_irq_affinity.sh -x all <DEVNAME>
+     ethtool -K <DEVNAME> gro off
+     ethtool -C <DEVNAME> adaptive-rx on adaptive-tx on
+     Replace <DEVNAME> with the network card, i.e. ens5f1
+     ```
+
+## MOT Server Optimization - ARM Huawei Taishan 2P/4P
+
+The following are optional settings for optimizing MOT database performance running on an ARM/Kunpeng-based Huawei Taishan 2280 v2 server powered by 2-sockets with a total of 256 Cores and Taishan 2480 v2 server powered by 4-sockets with a total of 256 Cores.
+
+Unless indicated otherwise, the following settings are for both client and server machines -
+
+### BIOS
+
+Modify related BIOS settings, as follows -
+
+1. Select **BIOS** - **Advanced** - **MISC Config**. Set **Support Smmu** to **Disabled**.
+
+2. Select **BIOS** - **Advanced** - **MISC Config**. Set **CPU Prefetching Configuration** to **Disabled**.
+
+   ![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-deployment-1.png)
+
+3. Select **BIOS** - **Advanced** - **Memory Config**. Set **Die Interleaving** to **Disabled**.
+
+   ![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-deployment-2.png)
+
+4. Select **BIOS** - **Advanced** - **Performance Config**. Set **Power Policy** to **Performance**.
+
+   ![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-deployment-3.png)
+
+### OS - Kernel and Boot
+
+- The following operating system kernel and boot parameters are usually configured by a sysadmin.
+
+  Configure the kernel parameters, as follows -
+
+  ```bash
+  net.ipv4.ip_local_port_range = 9000 65535
+  kernel.sysrq = 1
+  kernel.panic_on_oops = 1
+  kernel.panic = 5
+  kernel.hung_task_timeout_secs = 3600
+  kernel.hung_task_panic = 1
+  vm.oom_dump_tasks = 1
+  kernel.softlockup_panic = 1
+  fs.file-max = 640000
+  kernel.msgmnb = 7000000
+  kernel.sched_min_granularity_ns = 10000000
+  kernel.sched_wakeup_granularity_ns = 15000000
+  kernel.numa_balancing=0
+  vm.max_map_count = 1048576
+  net.ipv4.tcp_max_tw_buckets = 10000
+  net.ipv4.tcp_tw_reuse = 1
+  net.ipv4.tcp_tw_recycle = 1
+  net.ipv4.tcp_keepalive_time = 30
+  net.ipv4.tcp_keepalive_probes = 9
+  net.ipv4.tcp_keepalive_intvl = 30
+  net.ipv4.tcp_retries2 = 80
+  kernel.sem = 32000 1024000000      500     32000
+  kernel.shmall = 52805669
+  kernel.shmmax = 18446744073692774399
+  sys.fs.file-max = 6536438
+  net.core.wmem_max = 21299200
+  net.core.rmem_max = 21299200
+  net.core.wmem_default = 21299200
+  net.core.rmem_default = 21299200
+  net.ipv4.tcp_rmem = 8192 250000 16777216
+  net.ipv4.tcp_wmem = 8192 250000 16777216
+  net.core.somaxconn = 65535
+  vm.min_free_kbytes = 5270325
+  net.core.netdev_max_backlog = 65535
+  net.ipv4.tcp_max_syn_backlog = 65535
+  net.ipv4.tcp_syncookies = 1
+  vm.overcommit_memory = 0
+  net.ipv4.tcp_retries1 = 5
+  net.ipv4.tcp_syn_retries = 5
+  ##NEW
+  kernel.sched_autogroup_enabled=0
+  kernel.sched_min_granularity_ns=2000000
+  kernel.sched_latency_ns=10000000
+  kernel.sched_wakeup_granularity_ns=5000000
+  kernel.sched_migration_cost_ns=500000
+  vm.dirty_background_bytes=33554432
+  kernel.shmmax=21474836480
+  net.ipv4.tcp_timestamps = 0
+  net.ipv6.conf.all.disable_ipv6=1
+  net.ipv6.conf.default.disable_ipv6=1
+  net.ipv4.tcp_keepalive_time=600
+  net.ipv4.tcp_keepalive_probes=3
+  kernel.core_uses_pid=1
+  ```
+
+- Tuned Service
+
+  The following section is mandatory.
+
+  The server must run a throughput-performance profile -
+
+  ```
+  [...]$ tuned-adm profile throughput-performance
+  ```
+
+  The **throughput-performance** profile is broadly applicable tuning that provides excellent performance across a variety of common server workloads.
+
+  Other less suitable profiles for MogDB and MOT server that may affect MOT's overall performance are - balanced, desktop, latency-performance, network-latency, network-throughput and powersave.
+
+- Boot Tuning
+
+  Add **iommu.passthrough=1** to the **kernel boot arguments**.
+
+  When operating in **pass-through** mode, the adapter does require **DMA translation to the memory,** which improves performance.
+
+## MOT Configuration Settings
+
+MOT is provided preconfigured to creating working MOT Tables. For best results, it is recommended to customize the MOT configuration (defined in the file named mot.conf) according to your application's specific requirements and your preferences.
+
+This file is read-only upon server startup. If you edit this file while the system is running, then the server must be reloaded in order for the changes to take effect.
+
+The mot.conf file is located in the same folder as the postgres.conf configuration file.
+
+Read the **General Guidelines** section and then review and configure the following sections of the mot.conf file, as needed.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The topics listed above describe each of the setting sections in the mot.conf file. In addition to the above topics, for an overview of all the aspects of a specific MOT feature (such as Recovery), you may refer to the relevant topic of this user manual. For example, the mot.conf file has a Recovery section that contains settings that affect MOT recovery and this is described in the **MOT Recovery** section that is listed above. In addition, for a full description of all aspects of Recovery, you may refer to the **MOT Recovery** section of the Administration chapter of this user manual. Reference links are also provided in each relevant section of the descriptions below.
+
+The following topics describe each section in the mot.conf file and the settings that it contains, as well as the default value of each.
+
+### General Guidelines
+
+The following are general guidelines for editing the mot.conf file.
+
+- Each setting appears with its default value as follows -
+
+  ```
+  # name = value
+  ```
+
+- Blank/white space is acceptable.
+
+- Comments are indicated by placing a number sign (#) anywhere on a line.
+
+- The default values of each setting appear as a comment throughout this file.
+
+- In case a parameter is uncommented and a new value is placed, the new setting is defined.
+
+- Changes to the mot.conf file are applied only at the start or reload of the database server.
+
+Memory Units are represented as follows -
+
+- KB - Kilobytes
+- MB - Megabytes
+- GB - Gigabytes
+- TB - Terabytes
+
+If no memory units are specified, then bytes are assumed.
+
+Some memory units are represented as a percentage of the **max_process_memory** setting that is configured in **postgresql.conf**. For example - **20%**.
+
+Time units are represented as follows -
+
+- us - microseconds (or micros)
+- ms - milliseconds (or millis)
+- s - seconds (or secs)
+- min - minutes (or mins)
+- h - hours
+- d - days
+
+If no time units are specified, then microseconds are assumed.
+
+### REDO LOG (MOT)
+
+- **enable_group_commit = false**
+
+  Specifies whether to use group commit.
+
+  This option is only relevant when MogDB is configured to use synchronous commit, meaning only when the synchronous_commit setting in postgresql.conf is configured to any value other than off.
+
+- **group_commit_size = 16**
+
+- **group_commit_timeout = 10 ms**
+
+  This option is only relevant when the MOT engine has been configured to **Synchronous Group Commit** logging. This means that the synchronous_commit setting in postgresql.conf is configured to true and the enable_group_commit parameter in the mot.conf configuration file is configured to true.
+
+  Defines which of the following determines when a group of transactions is recorded in the WAL Redo Log -
+
+  **group_commit_size** - The quantity of committed transactions in a group. For example, **16** means that when 16 transactions in the same group have been committed by their client application, then an entry is written to disk in the WAL Redo Log for each of the 16 transactions.
+
+  **group_commit_timeout** - A timeout period in ms. For example, **10** means that after 10 ms, an entry is written to disk in the WAL Redo Log for each of the transactions in the same group that have been committed by their client application in the lats 10 ms.
+
+  A commit group is closed after either the configured number of transactions has arrived or after the configured timeout period since the group was opened. After the group is closed, all the transactions in the group wait for a group flush to complete execution and then notify the client that each transaction has ended.
+
+  You may refer to **MOT Logging - WAL Redo Log** section for more information about the WAL Redo Log and synchronous group commit logging.
+
+### CHECKPOINT (MOT)
+
+- **checkpoint_dir =**
+
+  Specifies the directory in which checkpoint data is to be stored. The default location is in the data folder of each data node.
+
+- **checkpoint_segsize = 16 MB**
+
+  Specifies the segment size used during checkpoint. Checkpoint is performed in segments. When a segment is full, it is serialized to disk and a new segment is opened for the subsequent checkpoint data.
+
+- **checkpoint_workers = 3**
+
+  Specifies the number of workers to use during checkpoint.
+
+  Checkpoint is performed in parallel by several MOT engine workers. The quantity of workers may substantially affect the overall performance of the entire checkpoint operation, as well as the operation of other running transactions. To achieve a shorter checkpoint duration, a larger number of workers should be used, up to the optimal number (which varies based on the hardware and workload). However, be aware that if this number is too large, it may negatively impact the execution time of other running transactions. Keep this number as low as possible to minimize the effect on the runtime of other running transactions, but at the cost of longer checkpoint duration.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** You may refer to the **MOT Checkpoints** section for more information about configuration settings.
+
+### RECOVERY (MOT)
+
+- **checkpoint_recovery_workers = 3**
+
+  Specifies the number of workers (threads) to use during checkpoint data recovery. Each MOT engine worker runs on its own core and can process a different table in parallel by reading it into memory. For example, while the default is three-course, you might prefer to set this parameter to the number of cores that are available for processing. After recovery these threads are stopped and killed.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** You may refer to the **MOT Recovery** section for more information about configuration settings.
+
+### STATISTICS (MOT)
+
+- **enable_stats = false**
+
+  Configures periodic statistics for printing.
+
+- **print_stats_period = 10 minute**
+
+  Configures the time period for printing a summary statistics report.
+
+- **print_full_stats_period = 1 hours**
+
+  Configures the time period for printing a full statistics report.
+
+  The following settings configure the various sections included in the periodic statistics report. If none of them are configured, then the statistics report is suppressed.
+
+- **enable_log_recovery_stats = false**
+
+  Log recovery statistics contain various Redo Log recovery metrics.
+
+- **enable_db_session_stats = false**
+
+  Database session statistics contain transaction events, such commits, rollbacks and so on.
+
+- **enable_network_stats = false**
+
+  Network statistics contain connection/disconnection events.
+
+- **enable_log_stats = false**
+
+  Log statistics contain details regarding the Redo Log.
+
+- **enable_memory_stats = false**
+
+  Memory statistics contain memory-layer details.
+
+- **enable_process_stats = false**
+
+  Process statistics contain total memory and CPU consumption for the current process.
+
+- **enable_system_stats = false**
+
+  System statistics contain total memory and CPU consumption for the entire system.
+
+- **enable_jit_stats = false**
+
+  JIT statistics contain information regarding JIT query compilation and execution.
+
+### ERROR LOG (MOT)
+
+- **log_level = INFO**
+
+  Configures the log level of messages issued by the MOT engine and recorded in the Error log of the database server. Valid values are PANIC, ERROR, WARN, INFO, TRACE, DEBUG, DIAG1 and DIAG2.
+
+- **Log.COMPONENT.LOGGER.log_level=LOG_LEVEL**
+
+  Configures specific loggers using the syntax described below.
+
+  For example, to configure the TRACE log level for the ThreadIdPool logger in system component, use the following syntax -
+
+  ```
+  Log.System.ThreadIdPool.log_level=TRACE
+  ```
+
+  To configure the log level for all loggers under some component, use the following syntax -
+
+  ```
+  Log.COMPONENT.log_level=LOG_LEVEL
+  ```
+
+  For example -
+
+  ```
+  Log.System.log_level=DEBUG
+  ```
+
+### MEMORY (MOT)
+
+- **enable_numa = true**
+
+  Specifies whether to use NUMA-aware memory allocation.
+
+  When disabled, all affinity configurations are disabled as well.
+
+  MOT engine assumes that all the available NUMA nodes have memory. If the machine has some special configuration in which some of the NUMA nodes have no memory, then the MOT engine initialization and hence the database server startup will fail. In such machines, it is recommended that this configuration value be set to false, in order to prevent startup failures and let the MOT engine to function normally without using NUMA-aware memory allocation.
+
+- **affinity_mode = fill-physical-first**
+
+    Configures the affinity mode of threads for the user session and internal MOT tasks.
+
+    When a thread pool is used, this value is ignored for user sessions, as their affinity is governed by the thread pool. However, it is still used for internal MOT tasks.
+
+    Valid values are **fill-socket-first**, **equal-per-socket**, **fill-physical-first** and **none** -
+
+  - **Fill-socket-first** attaches threads to cores in the same socket until the socket is full and then moves to the next socket.
+  - **Equal-per-socket** spreads threads evenly among all sockets.
+  - **Fill-physical-first** attaches threads to physical cores in the same socket until all physical cores are employed and then moves to the next socket. When all physical cores are used, then the process begins again with hyper-threaded cores.
+  - **None** disables any affinity configuration and lets the system scheduler determine on which core each thread is scheduled to run.
+
+- **lazy_load_chunk_directory = true**
+
+  Configures the chunk directory mode that is used for memory chunk lookup.
+
+  **Lazy** mode configures the chunk directory to load parts of it on demand, thus reducing the initial memory footprint (from 1 GB to 1 MB approximately). However, this may result in minor performance penalties and errors in extreme conditions of memory distress. In contrast, using a **non-lazy** chunk directory allocates an additional 1 GB of initial memory, produces slightly higher performance and ensures that chunk directory errors are avoided during memory distress.
+
+- **reserve_memory_mode = virtual**
+
+  Configures the memory reservation mode (either **physical** or **virtual**).
+
+  Whenever memory is allocated from the kernel, this configuration value is consulted to determine whether the allocated memory is to be resident (**physical**) or not (**virtual**). This relates primarily to preallocation, but may also affect runtime allocations. For **physical** reservation mode, the entire allocated memory region is made resident by forcing page faults on all pages spanned by the memory region. Configuring **virtual** memory reservation may result in faster memory allocation (particularly during preallocation), but may result in page faults during the initial access (and thus may result in a slight performance hit) and more sever errors when physical memory is unavailable. In contrast, physical memory allocation is slower, but later access is both faster and guaranteed.
+
+- **store_memory_policy = compact**
+
+  Configures the memory storage policy (**compact** or **expanding**).
+
+  When **compact** policy is defined, unused memory is released back to the kernel, until the lower memory limit is reached (see **min_mot_memory** below). In **expanding** policy, unused memory is stored in the MOT engine for later reuse. A **compact** storage policy reduces the memory footprint of the MOT engine, but may occasionally result in minor performance degradation. In addition, it may result in unavailable memory during memory distress. In contrast, **expanding** mode uses more memory, but results in faster memory allocation and provides a greater guarantee that memory can be re-allocated after being de-allocated.
+
+- **chunk_alloc_policy = auto**
+
+    Configures the chunk allocation policy for global memory.
+
+    MOT memory is organized in chunks of 2 MB each. The source NUMA node and the memory layout of each chunk affect the spread of table data among NUMA nodes, and therefore can significantly affect the data access time. When allocating a chunk on a specific NUMA node, the allocation policy is consulted.
+
+    Available values are **auto**, **local**, **page-interleaved**, **chunk-interleaved** and **native** -
+
+  - **Auto** policy selects a chunk allocation policy based on the current hardware.
+  - **Local** policy allocates each chunk on its respective NUMA node.
+  - **Page-interleaved** policy allocates chunks that are composed of interleaved memory 4-kilobyte pages from all NUMA nodes.
+  - **Chunk-interleaved** policy allocates chunks in a round robin fashion from all NUMA nodes.
+  - **Native** policy allocates chunks by calling the native system memory allocator.
+
+- **chunk_prealloc_worker_count = 8**
+
+  Configures the number of workers per NUMA node participating in memory preallocation.
+
+- **max_mot_global_memory = 80%**
+
+  Configures the maximum memory limit for the global memory of the MOT engine.
+
+  Specifying a percentage value relates to the total defined by **max_process_memory** configured in **postgresql.conf**.
+
+  The MOT engine memory is divided into global (long-term) memory that is mainly used to store user data and local (short-term) memory that is mainly used by user sessions for local needs.
+
+  Any attempt to allocate memory beyond this limit is denied and an error is reported to the user. Ensure that the sum of **max_mot_global_memory** and **max_mot_local_memory** do not exceed the **max_process_memory** configured in **postgresql.conf**.
+
+- **min_mot_global_memory = 0 MB**
+
+  Configures the minimum memory limit for the global memory of the MOT engine.
+
+  Specifying a percentage value relates to the total defined by the **max_process_memory** configured in **postgresql.conf**.
+
+  This value is used for the preallocation of memory during startup, as well as to ensure that a minimum amount of memory is available for the MOT engine during its normal operation. When using **compact** storage policy (see **store_memory_policy** above), this value designates the lower limit under which memory is not released back to the kernel, but rather kept in the MOT engine for later reuse.
+
+- **max_mot_local_memory = 15%**
+
+  Configures the maximum memory limit for the local memory of the MOT engine.
+
+  Specifying a percentage value relates to the total defined by the **max_process_memory** configured in **postgresql.conf**.
+
+  MOT engine memory is divided into global (long-term) memory that is mainly used to store user data and local (short-term) memory that is mainly used by user session for local needs.
+
+  Any attempt to allocate memory beyond this limit is denied and an error is reported to the user. Ensure that the sum of **max_mot_global_memory** and **max_mot_local_memory** do not exceed the **max_process_memory** configured in **postgresql.conf**.
+
+- **min_mot_local_memory = 0 MB**
+
+  Configures the minimum memory limit for the local memory of the MOT engine.
+
+  Specifying a percentage value relates to the total defined by the **max_process_memory** configured in **postgresql.conf**.
+
+  This value is used for preallocation of memory during startup, as well as to ensure that a minimum amount of memory is available for the MOT engine during its normal operation. When using compact storage policy (see **store_memory_policy** above), this value designates the lower limit under which memory is not released back to the kernel, but rather kept in the MOT engine for later reuse.
+
+- **max_mot_session_memory = 0 MB**
+
+  Configures the maximum memory limit for a single session in the MOT engine.
+
+  Typically, sessions in the MOT engine can allocate as much local memory as needed, so long as the local memory limit is not exceeded. To prevent a single session from taking too much memory, and thereby denying memory from other sessions, this configuration item is used to restrict small session-local memory allocations (up to 1,022 KB).
+
+  Make sure that this configuration item does not affect large or huge session-local memory allocations.
+
+  A value of zero denotes no restriction on any session-local small allocations per session, except for the restriction arising from the local memory allocation limit configured by **max_mot_local_memory**.
+
+  Note: Percentage values cannot be set for this configuration item.
+
+- **min_mot_session_memory = 0 MB**
+
+  Configures the minimum memory reservation for a single session in the MOT engine.
+
+  This value is used to preallocate memory during session creation, as well as to ensure that a minimum amount of memory is available for the session to perform its normal operation.
+
+  Note: Percentage values cannot be set for this configuration item.
+
+- **session_large_buffer_store_size = 0 MB**
+
+  Configures the large buffer store for sessions.
+
+  When a user session executes a query that requires a lot of memory (for example, when using many rows), the large buffer store is used to increase the certainty level that such memory is available and to serve this memory request more quickly. Any memory allocation for a session exceeding 1,022 KB is considered as a large memory allocation. If the large buffer store is not used or is depleted, such allocations are treated as huge allocations that are served directly from the kernel.
+
+  Note: Percentage values cannot be set for this configuration item.
+
+- **session_large_buffer_store_max_object_size = 0 MB**
+
+  Configures the maximum object size in the large allocation buffer store for sessions.
+
+  Internally, the large buffer store is divided into objects of varying sizes. This value is used to set an upper limit on objects originating from the large buffer store, as well as to determine the internal division of the buffer store into objects of various size.
+
+  This size cannot exceed 1⁄8 of the **session_large_buffer_store_size**. If it does, it is adjusted to the maximum possible.
+
+  Note: Percentage values cannot be set for this configuration item.
+
+- **session_max_huge_object_size = 1 GB**
+
+  Configures the maximum size of a single huge memory allocation made by a session.
+
+  Huge allocations are served directly from the kernel and therefore are not guaranteed to succeed.
+
+  This value also pertains to global (meaning not session-related) memory allocations.
+
+  Note: Percentage values cannot be set for this configuration item.
+
+### GARBAGE COLLECTION (MOT)
+
+- **enable_gc = true**
+
+  Specifies whether to use the Garbage Collector (GC).
+
+- **reclaim_threshold = 512 KB**
+
+  Configures the memory threshold for the garbage collector.
+
+  Each session manages its own list of to-be-reclaimed objects and performs its own garbage collection during transaction commitment. This value determines the total memory threshold of objects waiting to be reclaimed, above which garbage collection is triggered for a session.
+
+  In general, the trade-off here is between un-reclaimed objects vs garbage collection frequency. Setting a low value keeps low levels of un-reclaimed memory, but causes frequent garbage collection that may affect performance. Setting a high value triggers garbage collection less frequently, but results in higher levels of un-reclaimed memory. This setting is dependent upon the overall workload.
+
+- **reclaim_batch_size = 8000**
+
+  Configures the batch size for garbage collection.
+
+  The garbage collector reclaims memory from objects in batches, in order to restrict the number of objects being reclaimed in a single garbage collection pass. The intent of this approach is to minimize the operation time of a single garbage collection pass.
+
+- **high_reclaim_threshold = 8 MB**
+
+  Configures the high memory threshold for garbage collection.
+
+  Because garbage collection works in batches, it is possible that a session may have many objects that can be reclaimed, but which were not. In such situations, in order to prevent garbage collection lists from becoming too bloated, this value is used to continue reclaiming objects within a single pass, even though that batch size limit has been reached, until the total size of the still-waiting-to-be-reclaimed objects is less than this threshold, or there are no more objects eligible for reclamation.
+
+### JIT (MOT)
+
+- **enable_mot_codegen = true**
+
+  Specifies whether to use JIT query compilation and execution for planned queries.
+
+  JIT query execution enables JIT-compiled code to be prepared for a prepared query during its planning phase. The resulting JIT-compiled function is executed whenever the prepared query is invoked. JIT compilation usually takes place in the form of LLVM. On platforms where LLVM is not natively supported, MOT provides a software-based fallback called Tiny Virtual Machine (TVM).
+
+- **force_mot_pseudo_codegen = false**
+
+  Specifies whether to use TVM (pseudo-LLVM) even though LLVM is supported on the current platform.
+
+  On platforms where LLVM is not natively supported, MOT automatically defaults to TVM.
+
+  On platforms where LLVM is natively supported, LLVM is used by default. This configuration item enables the use of TVM for JIT compilation and execution on platforms on which LLVM is supported.
+
+- **enable_mot_codegen_print = false**
+
+  Specifies whether to print emitted LLVM/TVM IR code for JIT-compiled queries.
+
+- **mot_codegen_limit = 100**
+
+  Limits the number of JIT queries allowed per user session.
+
+### Default mot.conf
+
+The minimum settings and configuration specify to point the **postgresql.conf** file to the location of the **mot.conf** file -
+
+```
+postgresql.conf
+mot_config_file = '/tmp/gauss/mot.conf'
+```
+
+Ensure that the value of the max_process_memory setting is sufficient to include the global (data and index) and local (sessions) memory of MOT tables.
+
+The default content of **mot.conf** is sufficient to get started. The settings can be optimized later.
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/4-mot-usage.md b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/4-mot-usage.md
new file mode 100644
index 0000000000000000000000000000000000000000..29124b8864c6fe5daf92407a5c77ac1f5d4be8a8
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/4-mot-usage.md
@@ -0,0 +1,496 @@
+---
+title: MOT Usage
+summary: MOT Usage
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# MOT Usage
+
+Using MOT tables is quite simple and is described in the few short sections below.
+
+MogDB enables an application to use of MOT tables and standard disk-based tables. You can use MOT tables for your most active, high-contention and throughput-sensitive application tables or you can use MOT tables for all your application's tables.
+
+The following commands describe how to create MOT tables and how to convert existing disk-based tables into MOT tables in order to accelerate an application's database-related performance. MOT is especially beneficial when applied to tables that have proven to be bottlenecks.
+
+The following is a simple overview of the tasks related to working with MOT tables:
+
+- Granting User Permissions
+- Creating/Dropping an MOT Table
+- Creating an Index for an MOT Table
+- Converting a Disk Table into an MOT Table
+- Query Native Compilation
+- Retrying an Aborted Transaction
+- MOT External Support Tools
+- MOT SQL Coverage and Limitations
+
+## Granting User Permissions
+
+The following describes how to assign a database user permission to access the MOT storage engine. This is performed only once per database user, and is usually done during the initial configuration phase.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The granting of user permissions is required because MOT is integrated into the MogDB database by using and extending the Foreign Data Wrapper (FDW) mechanism, which requires granting user access permissions.
+
+To enable a specific user to create and access MOT tables (DDL, DML, SELECT) -
+
+Run the following statement only once -
+
+```sql
+GRANT USAGE ON FOREIGN SERVER mot_server TO <user>;
+```
+
+All keywords are not case sensitive.
+
+## Creating/Dropping an MOT Table
+
+Creating a Memory Optimized Table (MOT) is very simple. Only the create and drop table statements in MOT differ from the statements for disk-based tables in MogDB. The syntax of **all other** commands for SELECT, DML and DDL are the same for MOT tables as for MogDB disk-based tables.
+
+- To create an MOT table -
+
+  ```sql
+  create FOREIGN table test(x int) [server mot_server];
+  ```
+
+- Always use the FOREIGN keyword to refer to MOT tables.
+
+- The [server mot_server] part is optional when creating an MOT table because MOT is an integrated engine, not a separate server.
+
+- The above is an extremely simple example creating a table named **test** with a single integer column named **x**. In the next section (**Creating an Index**) a more realistic example is provided.
+
+- MOT tables cannot be created if incremental checkpoint is enabled in postgresql.conf. So please set enable_incremental_checkpoint to off before creating the MOT.
+
+- To drop an MOT table named test -
+
+  ```sql
+  drop FOREIGN table test;
+  ```
+
+For a description of the limitations of supported features for MOT tables, such as data types, see the **MOT SQL Coverage and Limitations** section.
+
+## Creating an Index for an MOT Table
+
+Standard PostgreSQL create and drop index statements are supported.
+
+For example -
+
+```sql
+create index  text_index1 on test(x) ;
+```
+
+The following is a complete example of creating an index for the ORDER table in a TPC-C workload -
+
+```sql
+create FOREIGN table bmsql_oorder (
+  o_w_id       integer      not null,
+  o_d_id       integer      not null,
+  o_id         integer      not null,
+  o_c_id       integer not null,
+  o_carrier_id integer,
+  o_ol_cnt     integer,
+  o_all_local  integer,
+  o_entry_d    timestamp,
+  primarykey (o_w_id, o_d_id, o_id)
+);
+
+create index  bmsql_oorder_index1 on bmsql_oorder(o_w_id, o_d_id, o_c_id, o_id) ;
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** There is no need to specify the **FOREIGN** keyword before the MOT table name, because it is only created for create and drop table commands.
+
+For MOT index limitations, see the Index subsection under the _SQL Coverage and Limitations_ section.
+
+## Converting a Disk Table into an MOT Table
+
+The direct conversion of disk tables into MOT tables is not yet possible, meaning that no ALTER TABLE statement yet exists that converts a disk-based table into an MOT table.
+
+The following describes how to manually perform a few steps in order to convert a disk-based table into an MOT table, as well as how the **gs_dump** tool is used to export data and the **gs_restore** tool is used to import data.
+
+### Prerequisite Check
+
+Check that the schema of the disk table to be converted into an MOT table contains all required columns.
+
+Check whether the schema contains any unsupported column data types, as described in the _Unsupported Data Types_ section.
+
+If a specific column is not supported, then it is recommended to first create a secondary disk table with an updated schema. This schema is the same as the original table, except that all the unsupported types have been converted into supported types.
+
+Afterwards, use the following script to export this secondary disk table and then import it into an MOT table.
+
+### Converting
+
+To covert a disk-based table into an MOT table, perform the following -
+
+1. Suspend application activity.
+2. Use **gs_dump** tool to dump the table’s data into a physical file on disk. Make sure to use the **data only**.
+3. Rename your original disk-based table.
+4. Create an MOT table with the same table name and schema. Make sure to use the create FOREIGN keyword to specify that it will be an MOT table.
+5. Use **gs_restore** to load/restore data from the disk file into the database table.
+6. Visually/manually verify that all the original data was imported correctly into the new MOT table. An example is provided below.
+7. Resume application activity.
+
+**IMPORTANT Note** **-** In this way, since the table name remains the same, application queries and relevant database stored-procedures will be able to access the new MOT table seamlessly without code changes. Please note that MOT does not currently support cross-engine multi-table queries (such as by using Join, Union and sub-query) and cross-engine multi-table transactions. Therefore, if an original table is accessed somewhere in a multi-table query, stored procedure or transaction, you must either convert all related disk-tables into MOT tables or alter the relevant code in the application or the database.
+
+### Conversion Example
+
+Let's say that you have a database name **benchmarksql** and a table named **customer** (which is a disk-based table) to be migrated it into an MOT table.
+
+To migrate the customer table into an MOT table, perform the following -
+
+1. Check your source table column types. Verify that all types are supported by MOT, refer to section *Unsupported Data Types*.
+
+   ```sql
+   benchmarksql-# \d+ customer
+                          Table "public.customer"
+    Column |  Type   | Modifiers | Storage | Stats target | Description
+   --------+---------+-----------+---------+--------------+-------------
+    x      | integer |           | plain   |              |
+    y      | integer |           | plain   |              |
+   Has OIDs: no
+   Options: orientation=row, compression=no
+   ```
+
+2. Check your source table data.
+
+   ```sql
+   benchmarksql=# select * from customer;
+    x | y
+   ---+---
+    1 | 2
+    3 | 4
+   (2 rows)
+   ```
+
+3. Dump table data only by using **gs_dump**.
+
+   ```sql
+   $ gs_dump -Fc benchmarksql -a --table customer -f customer.dump
+   gs_dump[port='15500'][benchmarksql][2020-06-04 16:45:38]: dump database benchmarksql successfully
+   gs_dump[port='15500'][benchmarksql][2020-06-04 16:45:38]: total time: 332  ms
+   ```
+
+4. Rename the source table name.
+
+   ```sql
+   benchmarksql=# alter table customer rename to customer_bk;
+   ALTER TABLE
+   ```
+
+5. Create the MOT table to be exactly the same as the source table.
+
+   ```sql
+   benchmarksql=# create foreign table customer (x int, y int);
+   CREATE FOREIGN TABLE
+   benchmarksql=# select * from customer;
+    x | y
+   ---+---
+   (0 rows)
+   ```
+
+6. Import the source dump data into the new MOT table.
+
+   ```sql
+   $ gs_restore -C -d benchmarksql customer.dump
+   restore operation successful
+   total time: 24  ms
+   Check that the data was imported successfully.
+   benchmarksql=# select * from customer;
+    x | y
+   ---+---
+    1 | 2
+    3 | 4
+   (2 rows)
+
+   benchmarksql=# \d
+                                   List of relations
+    Schema |    Name     |     Type      | Owner  |             Storage
+   --------+-------------+---------------+--------+----------------------------------
+    public | customer    | foreign table | aharon |
+    public | customer_bk | table         | aharon | {orientation=row,compression=no}
+   (2 rows)
+   ```
+
+## Query Native Compilation
+
+An additional feature of MOT is the ability to prepare and parse *pre-compiled full queries* in a native format (using a PREPARE statement) before they are needed for execution.
+
+This native format can later be executed (using an EXECUTE command) more efficiently. This type of execution is much quicker because the native format bypasses multiple database processing layers during execution and thus enables better performance.
+
+This division of labor avoids repetitive parse analysis operations. In this way, queries and transaction statements are executed in an interactive manner. This feature is sometimes called *Just-In-Time (JIT)* query compilation.
+
+### Query Compilation - PREPARE Statement
+
+To use MOT’s native query compilation, call the PREPARE client statement before the query is executed. This instructs MOT to pre-compile the query and/or to pre-load previously pre-compiled code from a cache.
+
+The following is an example of PREPARE syntax in SQL -
+
+```sql
+PREPARE name [ ( data_type [, ...] ) ] AS statement
+```
+
+PREPARE creates a prepared statement in the database server, which is a server-side object that can be used to optimize performance.
+
+### Execute Command
+
+When an EXECUTE command is subsequently issued, the prepared statement is parsed, analyzed, rewritten and executed. This division of labor avoids repetitive parse analysis operations, while enabling the execution plan to depend on specific provided setting values.
+
+The following is an example of how to invoke a PREPARE and then an EXECUTE statement in a Java application.
+
+```sql
+conn = DriverManager.getConnection(connectionUrl, connectionUser, connectionPassword);
+
+// Example 1: PREPARE without bind settings
+String query = "SELECT * FROM getusers";
+PreparedStatement prepStmt1 = conn.prepareStatement(query);
+ResultSet rs1 = pstatement.executeQuery())
+while (rs1.next()) {…}
+
+// Example 2: PREPARE with bind settings
+String sqlStmt = "SELECT * FROM employees where first_name=? and last_name like ?";
+PreparedStatement prepStmt2 = conn.prepareStatement(sqlStmt);
+prepStmt2.setString(1, "Mark"); // first name "Mark"
+prepStmt2.setString(2, "%n%"); // last name contains a letter "n"
+ResultSet rs2 = prepStmt2.executeQuery())
+while (rs2.next()) {…}
+```
+
+The following describes the supported and unsupported features of MOT compilation.
+
+### Supported Queries for Lite Execution
+
+The following query types are suitable for lite execution -
+
+- Simple point queries -
+  - SELECT (including SELECT for UPDATE)
+  - UPDATE
+  - DELETE
+- INSERT query
+- Range UPDATE queries that refer to a full prefix of the primary key
+- Range SELECT queries that refer to a full prefix of the primary key
+- JOIN queries where one or both parts collapse to a point query
+- JOIN queries that refer to a full prefix of the primary key in each joined table
+
+### Unsupported Queries for Lite Execution
+
+Any special query attribute disqualifies it for Lite Execution. In particular, if any of the following conditions apply, then the query is declared as unsuitable for Lite Execution. You may refer to the Unsupported Queries for Native Compilation and Lite Execution section for more information.
+
+It is important to emphasize that in case a query statement does not fit
+
+native compilation and lite execution, no error is reported to the client and the query will still be executed in a normal and standard manner.
+
+For more information about MOT native compilation capabilities, see either the section about Query Native Compilation or a more detailed information in the Query Native Compilation (JIT) section.
+
+## Retrying an Aborted Transaction
+
+In Optimistic Concurrency Control (OCC) (such as the one used by MOT) during a transaction (using any isolation level) no locks are placed on a record until the COMMIT phase. This is a powerful advantage that significantly increases performance. Its drawback is that an update may fail if another session attempts to update the same record. This results in an entire transaction that must be aborted. These so called *Update Conflicts* are detected by MOT at the commit time by a version checking mechanism.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** A similar abort happens on engines using pessimistic concurrency control, such as standard PG and the MogDB disk-based tables, when SERIALIZABLE or REPEATABLE-READ isolation level are used.
+
+Such update conflicts are quite rare in common OLTP scenarios and are especially rare in our experience with MOT. However, because there is still a chance that they may happen, developers should consider resolving this issue using transaction retry code.
+
+The following describes how to retry a table command after multiple sessions attempt to update the same table simultaneously. You may refer to the OCC vs 2PL Differences by Example section for more detailed information. The following example is taken from TPC-C payment transaction.
+
+```java
+int commitAborts = 0;
+
+while (commitAborts < RETRY_LIMIT) {
+
+    try {
+        stmt =db.stmtPaymentUpdateDistrict;
+        stmt.setDouble(1, 100);
+        stmt.setInt(2, 1);
+        stmt.setInt(3, 1);
+        stmt.executeUpdate();
+
+        db.commit();
+
+        break;
+    }
+    catch (SQLException se) {
+        if(se != null && se.getMessage().contains("could not serialize access due to concurrent update")) {
+            log.error("commmit abort = " + se.getMessage());
+            commitAborts++;
+            continue;
+        }else {
+            db.rollback();
+        }
+
+        break;
+    }
+}
+```
+
+## MOT External Support Tools
+
+The following external MogDB tools have been modified in order to support MOT. Make sure to use the most recent version of each. An overview describing MOT-related usage is provided below. For a full description of these tools and their usage, refer to the MogDB Tools Reference document.
+
+### gs_ctl (Full and Incremental)
+
+This tool is used to create a standby server from a primary server, as well as to synchronize a server with another copy of the same server after their timelines have diverged.
+
+At the end of the operation, the latest MOT checkpoint is fetched by the tool, taking into consideration the **checkpoint_dir** configuration setting value.
+
+The checkpoint is fetched from the source server's **checkpoint_dir** to the destination server's **checkpoint_dir**.
+
+Currently, MOT does not support an incremental checkpoint. Therefore, the gs_ctl incremental build does not work in an incremental manner for MOT, but rather in FULL mode. The Postgres (disk-tables) incremental build can still be done incrementally.
+
+### gs_basebackup
+
+gs_basebackup is used to prepare base backups of a running server, without affecting other database clients.
+
+The MOT checkpoint is fetched at the end of the operation as well. However, the checkpoint's location is taken from **checkpoint_dir** in the source server and is transferred to the data directory of the source in order to back it up correctly.
+
+### gs_dump
+
+gs_dump is used to export the database schema and data to a file. It also supports MOT tables.
+
+### gs_restore
+
+gs_restore is used to import the database schema and data from a file. It also supports MOT tables.
+
+## MOT SQL Coverage and Limitations
+
+MOT design enables almost complete coverage of SQL and future feature sets. For example, standard Postgres SQL is mostly supported, as well common database features, such as stored procedures and user defined functions.
+
+The following describes the various types of SQL coverages and limitations -
+
+### Unsupported Features
+
+The following features are not supported by MOT -
+
+- Engine Interop - No cross-engine (Disk+MOT) queries, views or transactions. Planned for 2021.
+- MVCC, Isolation - No snapshot/serializable isolation. Planned for 2021.
+- Native Compilation (JIT) - Limited SQL coverage. Also, JIT compilation of stored procedures is not supported.
+- LOCAL memory is limited to 1 GB. A transaction can only change data of less than 1 GB.
+- Capacity (Data+Index) is limited to available memory. Anti-caching + Data Tiering will be available in the future.
+- No full-text search index.
+- Do not support Logical copy.
+
+In addition, the following are detailed lists of various general limitations of MOT tables, MOT indexes, Query and DML syntax and the features and limitations of Query Native Compilation.
+
+### MOT Table Limitations
+
+The following lists the functionality limitations of MOT tables -
+
+- Partition by range
+- AES encryption
+- Stream operations
+- User-defined types
+- Sub-transactions
+- DML triggers
+- DDL triggers
+- Collations other than "C" or "POSIX"
+
+### Unsupported Table DDLs
+
+- Alter table
+- Create table, like including
+- Create table as select
+- Partition by range
+- Create table with no-logging clause
+- DEFERRABLE primary key
+- Reindex
+- Tablespace
+- Create schema with subcommands
+
+### Unsupported Data Types
+
+- UUID
+- User-Defined Type (UDF)
+- Array data type
+- NVARCHAR2(n)
+- Clob
+- Name
+- Blob
+- Raw
+- Path
+- Circle
+- Reltime
+- Bit varying(10)
+- Tsvector
+- Tsquery
+- JSON
+- Box
+- Text
+- Line
+- Point
+- LSEG
+- POLYGON
+- INET
+- CIDR
+- MACADDR
+- Smalldatetime
+- BYTEA
+- Bit
+- Varbit
+- OID
+- Money
+- Any unlimited varchar/character varying
+- HSTORE
+
+### UnsupportedIndex DDLs and Index
+
+- Create index on decimal/numeric
+
+- Create index on nullable columns
+
+- Create index, index per table > 9
+
+- Create index on key size > 256
+
+  The key size includes the column size in bytes + a column additional size, which is an overhead required to maintain the index. The below table lists the column additional size for different column types.
+
+  Additionally, in case of non-unique indexes an extra 8 bytes is required.
+
+  Thus, the following pseudo code calculates the **key size**:
+
+  ```java
+  keySize =0;
+
+  for each (column in index){
+        keySize += (columnSize + columnAddSize);
+  }
+  if (index is non_unique) {
+        keySize += 8;
+  }
+  ```
+
+  | Column Type | Column Size | Column Additional Size |
+  | :---------- | :---------- | :--------------------- |
+  | varchar     | N           | 4                      |
+  | tinyint     | 1           | 1                      |
+  | smallint    | 2           | 1                      |
+  | int         | 4           | 1                      |
+  | bigint      | 8           | 1                      |
+  | float       | 4           | 2                      |
+  | float8      | 8           | 3                      |
+
+  Types that are not specified in above table, the column additional size is zero (for instance timestamp).
+
+### Unsupported DMLs
+
+- Merge into
+- Select into
+- Lock table
+- Copy from table
+- Upsert
+
+### Unsupported Queries for Native Compilation and Lite Execution
+
+- The query refers to more than two tables
+- The query has any one of the following attributes -
+  - Aggregation on non-primitive types
+  - Window functions
+  - Sub-query sub-links
+  - Distinct-ON modifier (distinct clause is from DISTINCT ON)
+  - Recursive (WITH RECURSIVE was specified)
+  - Modifying CTE (has INSERT/UPDATE/DELETE in WITH)
+
+In addition, the following clauses disqualify a query from lite execution -
+
+- Returning list
+- Group By clause
+- Grouping sets
+- Having clause
+- Windows clause
+- Distinct clause
+- Sort clause that does not conform to native index order
+- Set operations
+- Constraint dependencies
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/5-mot-administration.md b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/5-mot-administration.md
new file mode 100644
index 0000000000000000000000000000000000000000..5b2171fe07ada57ec189d6b63e0a420bb9c4c604
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/5-mot-administration.md
@@ -0,0 +1,419 @@
+---
+title: MOT Administration
+summary: MOT Administration
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# MOT Administration
+
+The following describes various MOT administration topics.
+
+## MOT Durability
+
+Durability refers to long-term data protection (also known as *disk persistence*). Durability means that stored data does not suffer from any kind of degradation or corruption, so that data is never lost or compromised. Durability ensures that data and the MOT engine are restored to a consistent state after a planned shutdown (for example, for maintenance) or an unplanned crash (for example, a power failure).
+
+Memory storage is volatile, meaning that it requires power to maintain the stored information. Disk storage, on the other hand, is non-volatile, meaning that it does not require power to maintain stored information, thus, it can survive a power shutdown. MOT uses both types of storage - it has all data in memory, while persisting transactional changes to disk **MOT Durability** and by maintaining frequent periodic **MOT Checkpoints** in order to ensure data recovery in case of shutdown.
+
+The user must ensure sufficient disk space for the logging and Checkpointing operations. A separated drive can be used for the Checkpoint to improve performance by reducing disk I/O load.
+
+You may refer to the **MOT Key Technologies** section for an overview of how durability is implemented in the MOT engine.
+
+**To configure durability -**
+
+To ensure strict consistency, configure the synchronous_commit parameter to **On** in the postgres.conf configuration file.
+
+**MOTs WAL Redo Log and Checkpoints enable durability, as described below -**
+
+### MOT Logging - WAL Redo Log
+
+To ensure Durability, MOT is fully integrated with the MogDB's Write-Ahead Logging (WAL) mechanism, so that MOT persists data in WAL records using MogDB's XLOG interface. This means that every addition, update, and deletion to an MOT table’s record is recorded as an entry in the WAL. This ensures that the most current data state can be regenerated and recovered from this non-volatile log. For example, if three new rows were added to a table, two were deleted and one was updated, then six entries would be recorded in the log.
+
+MOT log records are written to the same WAL as the other records of MogDB disk-based tables.
+
+MOT only logs an operation at the transaction commit phase.
+
+MOT only logs the updated delta record in order to minimize the amount of data written to disk.
+
+During recovery, data is loaded from the last known or a specific Checkpoint; and then the WAL Redo log is used to complete the data changes that occur from that point forward.
+
+The WAL (Redo Log) retains all the table row modifications until a Checkpoint is performed (as described above). The log can then be truncated in order to reduce recovery time and to save disk space.
+
+**Note** - In order to ensure that the log IO device does not become a bottleneck, the log file must be placed on a drive that has low latency.
+
+### MOT Logging Types
+
+Two synchronous transaction logging options and one asynchronous transaction logging option are supported (these are also supported by the standard MogDB disk engine). MOT also supports synchronous Group Commit logging with NUMA-awareness optimization, as described below.
+
+According to your configuration, one of the following types of logging is implemented -
+
+- **Synchronous Redo Logging**
+
+  The **Synchronous Redo Logging** option is the simplest and most strict redo logger. When a transaction is committed by a client application, the transaction redo entries are recorded in the WAL (Redo Log), as follows -
+
+  1. While a transaction is in progress, it is stored in the MOT's memory.
+  2. After a transaction finishes and the client application sends a Commit command, the transaction is locked and then written to the WAL Redo Log on the disk. This means that while the transaction log entries are being written to the log, the client application is still waiting for a response.
+  3. As soon as the transaction's entire buffer is written to the log, the changes to the data in memory take place and then the transaction is committed. After the transaction has been committed, the client application is notified that the transaction is complete.
+
+  **Summary**
+
+  The **Synchronous Redo Logging** option is the safest and most strict because it ensures total synchronization of the client application and the WAL Redo log entries for each transaction as it is committed; thus ensuring total durability and consistency with absolutely no data loss. This logging option prevents the situation where a client application might mark a transaction as successful, when it has not yet been persisted to disk.
+
+  The downside of the **Synchronous Redo Logging** option is that it is the slowest logging mechanism of the three options. This is because a client application must wait until all data is written to disk and because of the frequent disk writes (which typically slow down the database).
+
+- **Group Synchronous Redo Logging**
+
+  The **Group Synchronous Redo Logging** option is very similar to the **Synchronous Redo Logging** option, because it also ensures total durability with absolutely no data loss and total synchronization of the client application and the WAL (Redo Log) entries. The difference is that the **Group Synchronous Redo Logging** option writes _groups of transaction_r edo entries to the WAL Redo Log on the disk at the same time, instead of writing each and every transaction as it is committed. Using Group Synchronous Redo Logging reduces the amount of disk I/Os and thus improves performance, especially when running a heavy workload.
+
+  The MOT engine performs synchronous Group Commit logging with Non-Uniform Memory Access (NUMA)-awareness optimization by automatically grouping transactions according to the NUMA socket of the core on which the transaction is running.
+
+  You may refer to the **NUMA Awareness Allocation and Affinity** section for more information about NUMA-aware memory access.
+
+  When a transaction commits, a group of entries are recorded in the WAL Redo Log, as follows -
+
+  1. While a transaction is in progress, it is stored in the memory. The MOT engine groups transactions in buckets according to the NUMA socket of the core on which the transaction is running. This means that all the transactions running on the same socket are grouped together and that multiple groups will be filling in parallel according to the core on which the transaction is running.
+
+     Writing transactions to the WAL is more efficient in this manner because all the buffers from the same socket are written to disk together.
+
+     **Note** - Each thread runs on a single core/CPU which belongs to a single socket and each thread only writes to the socket of the core on which it is running.
+
+  2. After a transaction finishes and the client application sends a Commit command, the transaction redo log entries are serialized together with other transactions that belong to the same group.
+
+  3. After the configured criteria are fulfilled for a specific group of transactions (quantity of committed transactions or timeout period as describes in the **REDO LOG (MOT)** section), the transactions in this group are written to the WAL on the disk. This means that while these log entries are being written to the log, the client applications that issued the commit are waiting for a response.
+
+  4. As soon as all the transaction buffers in the NUMA-aware group have been written to the log, all the transactions in the group are performing the necessary changes to the memory store and the clients are notified that these transactions are complete.
+
+  **Summary**
+
+  The **Group Synchronous Redo Logging** option is a an extremely safe and strict logging option because it ensures total synchronization of the client application and the WAL Redo log entries; thus ensuring total durability and consistency with absolutely no data loss. This logging option prevents the situation where a client application might mark a transaction as successful, when it has not yet been persisted to disk.
+
+  On one hand this option has fewer disk writes than the **Synchronous Redo Logging** option, which may mean that it is faster. The downside is that transactions are locked for longer, meaning that they are locked until after all the transactions in the same NUMA memory have been written to the WAL Redo Log on the disk.
+
+  The benefits of using this option depend on the type of transactional workload. For example, this option benefits systems that have many transactions (and less so for systems that have few transactions, because there are few disk writes anyway).
+
+- **Asynchronous Redo Logging**
+
+  The **Asynchronous Redo Logging** option is the fastest logging method, However, it does not ensure no data loss, meaning that some data that is still in the buffer and was not yet written to disk may get lost upon a power failure or database crash. When a transaction is committed by a client application, the transaction redo entries are recorded in internal buffers and written to disk at preconfigured intervals. The client application does not wait for the data being written to disk. It continues to the next transaction. This is what makes asynchronous redo logging the fastest logging method.
+
+  When a transaction is committed by a client application, the transaction redo entries are recorded in the WAL Redo Log, as follows -
+
+  1. While a transaction is in progress, it is stored in the MOT's memory.
+  2. After a transaction finishes and the client application sends a Commit command, the transaction redo entries are written to internal buffers, but are not yet written to disk. Then changes to the MOT data memory take place and the client application is notified that the transaction is committed.
+  3. At a preconfigured interval, a redo log thread running in the background collects all the buffered redo log entries and writes them to disk.
+
+  **Summary**
+
+  The Asynchronous Redo Logging option is the fastest logging option because it does not require the client application to wait for data being written to disk. In addition, it groups many transactions redo entries and writes them together, thus reducing the amount of disk I/Os that slow down the MOT engine.
+
+  The downside of the Asynchronous Redo Logging option is that it does not ensure that data will not get lost upon a crash or failure. Data that was committed, but was not yet written to disk, is not durable on commit and thus cannot be recovered in case of a failure. The Asynchronous Redo Logging option is most relevant for applications that are willing to sacrifice data recovery (consistency) over performance.
+
+### Configuring Logging
+
+Two synchronous transaction logging options and one asynchronous transaction logging option are supported by the standard MogDB disk engine.
+
+To configure logging -
+
+1. The determination of whether synchronous or asynchronous transaction logging is performed is configured in the synchronous_commit **(On = Synchronous)** parameters in the postgres.conf configuration file.
+
+If a synchronous mode of transaction logging has been selected (synchronous_commit = **On**, as described above), then the enable_group_commit parameter in the mot.conf configuration file determines whether the **Group Synchronous Redo Logging** option or the **Synchronous Redo Logging** option is used. For **Group Synchronous Redo Logging**, you must also define in the mot.conf file which of the following thresholds determine when a group of transactions is recorded in the WAL
+
+- group_commit_size **-** The quantity of committed transactions in a group. For example, **16** means that when 16 transactions in the same group have been committed by a client application, then an entry is written to disk in the WAL Redo Log for all 16 transactions.
+
+- group_commit_timeout - A timeout period in ms. For example, **10** means that after 10 ms, an entry is written to disk in the WAL Redo Log for each of the transactions in the same group that have been committed by their client application in the last 10 ms.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** You may refer to the **REDO LOG (MOT)** for more information about configuration settings.
+
+### MOT Checkpoints
+
+A Checkpoint is the point in time at which all the data of a table's rows is saved in files on persistent storage in order to create a full durable database image. It is a snapshot of the data at a specific point in time.
+
+A Checkpoint is required in order to reduce a database's recovery time by shortening the quantity of WAL (Redo Log) entries that must be replayed in order to ensure durability. Checkpoint's also reduce the storage space required to keep all the log entries.
+
+If there were no Checkpoints, then in order to recover a database, all the WAL redo entries would have to be replayed from the beginning of time, which could take days/weeks depending on the quantity of records in the database. Checkpoints record the current state of the database and enable old redo entries to be discarded.
+
+Checkpoints are essential during recovery scenarios (especially for a cold start). First, the data is loaded from the last known or a specific Checkpoint; and then the WAL is used to complete the data changes that occurred since then.
+
+For example - If the same table row is modified 100 times, then 100 entries are recorded in the log. When Checkpoints are used, then even if a specific table row was modified 100 times, it is recorded in the Checkpoint a single time. After the recording of a Checkpoint, recovery can be performed on the basis of that Checkpoint and only the WAL Redo Log entries that occurred since the Checkpoint need be played.
+
+## MOT Recovery
+
+The main objective of MOT Recovery is to restore the data and the MOT engine to a consistent state after a planned shutdown (for example, for maintenance) or an unplanned crash (for example, after a power failure).
+
+MOT recovery is performed automatically with the recovery of the rest of the MogDB database and is fully integrated into MogDB recovery process (also called a *Cold Start*).
+
+MOT recovery consists of two stages -
+
+**Checkpoint Recovery -** First, data must be recovered from the latest Checkpoint file on disk by loading it into memory rows and creating indexes.
+
+**WAL Redo Log Recovery -** Afterwards, the recent data (which was not captured in the Checkpoint) must be recovered from the WAL Redo Log by replaying records that were added to the log since the Checkpoint that was used in the Checkpoint Recovery (described above).
+
+The WAL Redo Log recovery is managed and triggered by MogDB.
+
+- To configure recovery.
+
+- While WAL recovery is performed in a serial manner, the Checkpoint recovery can be configured to run in a multi-threaded manner (meaning in parallel by multiple workers).
+
+- Configure the **Checkpoint_recovery_workers** parameter in the **mot.conf** file, which is described in the **RECOVERY (MOT)** section.
+
+## MOT Replication and High Availability
+
+Since MOT is integrated into MogDB and uses/supports its replication and high availability, both synchronous and asynchronous replication are supported out of the box.
+
+The MogDB gs_ctl tool is used for availability control and to operate the cluster. This includes gs_ctl switchover, gs_ctl failover, gs_ctl build and so on.
+
+You may refer to the MogDB Tools Reference document for more information.
+
+- To configure replication and high availability.
+- Refer to the relevant MogDB documentation.
+
+## MOT Memory Management
+
+For planning and finetuning, see the **MOT Memory and Storage Planning** and **MOT Configuration Settings** sections.
+
+## MOT Vacuum
+
+Use VACUUM for garbage collection and optionally to analyze a database, , as follows -
+
+- [PG]
+
+  In Postgress (PG), the VACUUM reclaims storage occupied by dead tuples. In normal PG operation, tuples that are deleted or that are made obsolete by an update are not physically removed from their table. They remain present until a VACUUM is done. Therefore, it is necessary to perform a VACUUM periodically, especially on frequently updated tables.
+
+- [MOT Extension]
+
+  MOT tables do not need a periodic VACUUM operation, since dead/empty tuples are re-used by new ones. MOT tables require VACUUM operations only when their size is significantly reduced and they do not expect to grow to their original size in the near future.
+
+  For example, an application that periodically (for example, once in a week) performs a large deletion of a table/tables data while inserting new data takes days and does not necessarily require the same quantity of rows. In such cases, it makes sense to activate the VACUUM.
+
+  The VACUUM operation on MOT tables is always transformed into a VACUUM FULL with an exclusive table lock.
+
+- Supported Syntax and Limitations
+
+  Activation of the VACUUM operation is performed in a standard manner.
+
+  ```sql
+  VACUUM [FULL | ANALYZE] [ table ];
+  ```
+
+  Only the FULL and ANALYZE VACUUM options are supported. The VACUUM operation can only be performed on an entire MOT table.
+
+  The following PG vacuum options are not supported:
+
+  - FREEZE
+  - VERBOSE
+  - Column specification
+  - LAZY mode (partial table scan)
+
+    Additionally, the following functionality is not supported
+
+  - AUTOVACUUM
+
+## MOT Statistics
+
+Statistics are intended for performance analysis or debugging. It is uncommon to turn them ON in a production environment (by default, they are OFF). Statistics are primarily used by database developers and to a lesser degree by database users.
+
+There is some impact on performance, particularly on the server. Impact on the user is negligible.
+
+The statistics are saved in the database server log. The log is located in the data folder and named **postgresql-DATE-TIME.log**.
+
+Refer to **STATISTICS (MOT)** for detailed configuration options.
+
+## MOT Monitoring
+
+All syntax for monitoring of PG-based FDW tables is supported. This includes Table or Index sizes (as described below). In addition, special functions exist for monitoring MOT memory consumption, including MOT Global Memory, MOT Local Memory and a single client session.
+
+### Table and Index Sizes
+
+The size of tables and indexes can be monitored by querying pg_relation_size.
+
+For example
+
+**Data Size**
+
+```sql
+select pg_relation_size('customer');
+```
+
+**Index**
+
+```sql
+select pg_relation_size('customer_pkey');
+```
+
+### MOT GLOBAL Memory Details
+
+Check the size of MOT global memory, which includes primarily the data and indexes.
+
+```sql
+select * from mot_global_memory_detail();
+```
+
+Result -
+
+```sql
+numa_node  | reserved_size        | used_size
+----------------+----------------+-------------
+-1            | 194716368896      | 25908215808
+0             | 446693376         | 446693376
+1             | 452984832         | 452984832
+2             | 452984832         | 452984832
+3             | 452984832         | 452984832
+4             | 452984832         | 452984832
+5             | 364904448         | 364904448
+6             | 301989888         | 301989888
+7             | 301989888         | 301989888
+```
+
+Where -
+
+- -1 is the total memory.
+- 0..7 are NUMA memory nodes.
+
+### MOT LOCAL Memory Details
+
+Check the size of MOT local memory, which includes session memory.
+
+```sql
+select * from mot_local_memory_detail();
+```
+
+Result -
+
+```sql
+numa_node  | reserved_size      | used_size
+----------------+----------------+-------------
+-1            | 144703488       | 144703488
+0             | 25165824        | 25165824
+1             | 25165824        | 25165824
+2             | 18874368        | 18874368
+3             | 18874368        | 18874368
+4             | 18874368        | 18874368
+5             | 12582912        | 12582912
+6             | 12582912        | 12582912
+7             | 12582912        | 12582912
+```
+
+Where -
+
+- -1 is the total memory.
+- 0..7 are NUMA memory nodes.
+
+### Session Memory
+
+Memory for session management is taken from the MOT local memory.
+
+Memory usage by all active sessions (connections) is possible using the following query -
+
+```sql
+select * from mot_session_memory_detail();
+```
+
+Result -
+
+```sql
+sessid                   | total_size | free_size | used_size
+----------------------------------------+-----------+----------+----------
+1591175063.139755603855104 | 6291456    | 1800704   | 4490752
+
+```
+
+Legend -
+
+- **total_size -** is allocated for the session
+- **free_size -** not in use
+- **used_size -** In actual use
+
+The following query enables a DBA to determine the state of local memory used by the current session -
+
+```sql
+select * from mot_session_memory_detail()
+ where sessid = pg_current_sessionid();
+```
+
+Result -
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-administration-1.png)
+
+## MOT Error Messages
+
+Errors may be caused by a variety of scenarios. All errors are logged in the database server log file. In addition, user-related errors are returned to the user as part of the response to the query, transaction or stored procedure execution or to database administration action.
+
+- Errors reported in the Server log include - Function, Entity, Context, Error message, Error description and Severity.
+- Errors reported to users are translated into standard PostgreSQL error codes and may consist of an MOT-specific message and description.
+
+The following lists the error messages, error descriptions and error codes. The error code is actually an internal code and not logged or returned to users.
+
+### Errors Written the Log File
+
+All errors are logged in the database server log file. The following lists the errors that are written to the database server log file and are **not** returned to the user. The log is located in the data folder and named **postgresql-DATE-TIME.log**.
+
+**Table 1** Errors Written Only to the Log File
+
+| Message in the Log                  | Error Internal Code              |
+| :---------------------------------- | :------------------------------- |
+| Error code denoting success         | MOT_NO_ERROR 0                   |
+| Out of memory                       | MOT_ERROR_OOM 1                  |
+| Invalid configuration               | MOT_ERROR_INVALID_CFG 2          |
+| Invalid argument passed to function | MOT_ERROR_INVALID_ARG 3          |
+| System call failed                  | MOT_ERROR_SYSTEM_FAILURE 4       |
+| Resource limit reached              | MOT_ERROR_RESOURCE_LIMIT 5       |
+| Internal logic error                | MOT_ERROR_INTERNAL 6             |
+| Resource unavailable                | MOT_ERROR_RESOURCE_UNAVAILABLE 7 |
+| Unique violation                    | MOT_ERROR_UNIQUE_VIOLATION 8     |
+| Invalid memory allocation size      | MOT_ERROR_INVALID_MEMORY_SIZE 9  |
+| Index out of range                  | MOT_ERROR_INDEX_OUT_OF_RANGE 10  |
+| Error code unknown                  | MOT_ERROR_INVALID_STATE 11       |
+
+### Errors Returned to the User
+
+The following lists the errors that are written to the database server log file and are returned to the user.
+
+MOT returns PG standard error codes to the envelope using a Return Code (RC). Some RCs cause the generation of an error message to the user who is interacting with the database.
+
+The PG code (described below) is returned internally by MOT to the database envelope, which reacts to it according to standard PG behavior.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** %s, %u and %lu in the message are replaced by relevant error information, such as query, table name or another information. - %s - String - %u - Number - %lu - Number
+
+**Table 2** Errors Returned to the User and Logged to the Log File
+
+| Short and Long Description Returned to the User       | PG Code                         | Internal Error Code                      |
+| :---------------------------------------------------- | :------------------------------ | :------------------------------ |
+| Success.Denotes success                                      | ERRCODE_SUCCESSFUL_COMPLETIONCOMPLETION                     | RC_OK = 0                           |
+| FailureUnknown error has occurred.                           | ERRCODE_FDW_ERROR                                           | RC_ERROR = 1                        |
+| Unknown error has occurred.Denotes aborted operation.        | ERRCODE_FDW_ERROR                                           | RC_ABORT                            |
+| Column definition of %s is not supported.Column type %s is not supported yet. | ERRCODE_INVALID_COLUMN_DEFINITION                           | RC_UNSUPPORTED_COL_TYPE             |
+| Column definition of %s is not supported.Column type Array of %s is not supported yet. | ERRCODE_INVALID_COLUMN_DEFINITION                           | RC_UNSUPPORTED_COL_TYPE_ARR         |
+| Column size %d exceeds max tuple size %u.Column definition of %s is not supported. | ERRCODE_FEATURE_NOT_SUPPORTED                               | RC_EXCEEDS_MAX_ROW_SIZE             |
+| Column name %s exceeds max name size %u.Column definition of %s is not supported. | ERRCODE_INVALID_COLUMN_DEFINITION                           | RC_COL_NAME_EXCEEDS_MAX_SIZE        |
+| Column size %d exceeds max size %u.Column definition of %s is not supported. | ERRCODE_INVALID_COLUMN_DEFINITION                           | RC_COL_SIZE_INVLALID                |
+| Cannot create table.Cannot add column %s; as the number of declared columns exceeds the maximum declared columns. | ERRCODE_FEATURE_NOT_SUPPORTED                               | RC_TABLE_EXCEEDS_MAX_DECLARED_COLS  |
+| Cannot create index.Total column size is greater than maximum index size %u. | ERRCODE_FDW_KEY_SIZE_EXCEEDS_MAX_ALLOWED                    | RC_INDEX_EXCEEDS_MAX_SIZE           |
+| Cannot create index.Total number of indexes for table %s is greater than the maximum number of indexes allowed %u. | ERRCODE_FDW_TOO_MANY_INDEXES                                | RC_TABLE_EXCEEDS_MAX_INDEXES        |
+| Cannot execute statement.Maximum number of DDLs per transaction reached the maximum %u. | ERRCODE_FDW_TOO_MANY_DDL_CHANGES_IN_TRANSACTION_NOT_ALLOWED | RC_TXN_EXCEEDS_MAX_DDLS             |
+| Unique constraint violationDuplicate key value violates unique constraint \"%s\"".Key %s already exists. | ERRCODE_UNIQUE_VIOLATION                                    | RC_UNIQUE_VIOLATION                 |
+| Table \"%s\" does not exist.                                 | ERRCODE_UNDEFINED_TABLE                                     | RC_TABLE_NOT_FOUND                  |
+| Index \"%s\" does not exist.                                 | ERRCODE_UNDEFINED_TABLE                                     | RC_INDEX_NOT_FOUND                  |
+| Unknown error has occurred.                                  | ERRCODE_FDW_ERROR                                           | RC_LOCAL_ROW_FOUND                  |
+| Unknown error has occurred.                                  | ERRCODE_FDW_ERROR                                           | RC_LOCAL_ROW_NOT_FOUND              |
+| Unknown error has occurred.                                  | ERRCODE_FDW_ERROR                                           | RC_LOCAL_ROW_DELETED                |
+| Unknown error has occurred.                                  | ERRCODE_FDW_ERROR                                           | RC_INSERT_ON_EXIST                  |
+| Unknown error has occurred.                                  | ERRCODE_FDW_ERROR                                           | RC_INDEX_RETRY_INSERT               |
+| Unknown error has occurred.                                  | ERRCODE_FDW_ERROR                                           | RC_INDEX_DELETE                     |
+| Unknown error has occurred.                                  | ERRCODE_FDW_ERROR                                           | RC_LOCAL_ROW_NOT_VISIBLE            |
+| Memory is temporarily unavailable.                           | ERRCODE_OUT_OF_LOGICAL_MEMORY                               | RC_MEMORY_ALLOCATION_ERROR          |
+| Unknown error has occurred.                                  | ERRCODE_FDW_ERROR                                           | RC_ILLEGAL_ROW_STATE                |
+| Null constraint violated.NULL value cannot be inserted into non-null column %s at table %s. | ERRCODE_FDW_ERROR                                           | RC_NULL_VIOLATION                   |
+| Critical error.Critical error: %s.                           | ERRCODE_FDW_ERROR                                           | RC_PANIC                            |
+| A checkpoint is in progress - cannot truncate table.         | ERRCODE_FDW_OPERATION_NOT_SUPPORTED                         | RC_NA                               |
+| Unknown error has occurred.                                  | ERRCODE_FDW_ERROR                                           | RC_MAX_VALUE                        |
+| &lt;recovery message&gt;                                     | -                                                           | ERRCODE_CONFIG_FILE_ERROR           |
+| &lt;recovery message&gt;                                     | -                                                           | ERRCODE_INVALID_TABLE_DEFINITION    |
+| Memory engine - Failed to perform commit prepared.           | -                                                           | ERRCODE_INVALID_TRANSACTION_STATE   |
+| Invalid option &lt;option name&gt;                           | -                                                           | ERRCODE_FDW_INVALID_OPTION_NAME     |
+| Invalid memory allocation request size.                      | -                                                           | ERRCODE_INVALID_PARAMETER_VALUE     |
+| Memory is temporarily unavailable.                           | -                                                           | ERRCODE_OUT_OF_LOGICAL_MEMORY       |
+| Could not serialize access due to concurrent update.         | -                                                           | ERRCODE_T_R_SERIALIZATION_FAILURE   |
+| Alter table operation is not supported for memory table.Cannot create MOT tables while incremental checkpoint is enabled.Re-index is not supported for memory tables. | -                                                           | ERRCODE_FDW_OPERATION_NOT_SUPPORTED |
+| Allocation of table metadata failed.                         | -                                                           | ERRCODE_OUT_OF_MEMORY               |
+| Database with OID %u does not exist.                         | -                                                           | ERRCODE_UNDEFINED_DATABASE          |
+| Value exceeds maximum precision: %d.                         | -                                                           | ERRCODE_NUMERIC_VALUE_OUT_OF_RANGE  |
+| You have reached a maximum logical capacity %lu of allowed %lu. | -                                                           | ERRCODE_OUT_OF_LOGICAL_MEMORY       |
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/6-mot-sample-tpcc-benchmark.md b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/6-mot-sample-tpcc-benchmark.md
new file mode 100644
index 0000000000000000000000000000000000000000..e0fb87fe182d30dd8e48c27573f27c42bab06efc
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/6-mot-sample-tpcc-benchmark.md
@@ -0,0 +1,116 @@
+---
+title: MOT Sample TPC-C Benchmark
+summary: MOT Sample TPC-C Benchmark
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# MOT Sample TPC-C Benchmark
+
+## TPC-C Introduction
+
+The TPC-C Benchmark is an industry standard benchmark for measuring the performance of Online Transaction Processing (OLTP) systems. It is based on a complex database and a number of different transaction types that are executed on it. TPC-C is both a hardware-independent and a software-independent benchmark and can thus be run on every test platform. An official overview of the benchmark model can be found at the tpc.org website here - <http://www.tpc.org/default5.asp>.
+
+The database consists of nine tables of various structures and thus also nine types of data records. The size and quantity of the data records varies per table. A mix of five concurrent transactions of varying types and complexities is executed on the database, which are largely online or in part queued for deferred batch processing. Because these tables compete for limited system resources, many system components are stressed and data changes are executed in a variety of ways.
+
+**Table 1** TPC-C Database Structure
+
+| Table      | Number of Entries                        |
+| :--------- | :--------------------------------------- |
+| Warehouse  | n                                        |
+| Item       | 100,000                                  |
+| Stock      | n x 100,000                              |
+| District   | n x 10                                   |
+| Customer   | 3,000 per district, 30,000 per warehouse |
+| Order      | Number of customers (initial value)      |
+| New order  | 30% of the orders (initial value)        |
+| Order line | ~ 10 per order                           |
+| History    | Number of customers (initial value)      |
+
+The transaction mix represents the complete business processing of an order - from its entry through to its delivery. More specifically, the provided mix is designed to produce an equal number of new-order transactions and payment transactions and to produce a single delivery transaction, a single order-status transaction and a single stock-level transaction for every ten new-order transactions.
+
+**Table 2** TPC-C Transactions Ratio
+
+| Transaction Level ≥ 4% | Share of All Transactions |
+| :--------------------- | :------------------------ |
+| TPC-C New order        | ≤ 45%                     |
+| Payment                | ≥ 43%                     |
+| Order status           | ≥ 4%                      |
+| Delivery               | ≥ 4% (batch)              |
+| Stock level            | ≥ 4%                      |
+
+There are two ways to execute the transactions - **as stored procedures** (which allow higher throughput) and in **standard interactive SQL mode**.
+
+**Performance Metric - tpm-C**
+
+The tpm-C metric is the number of new-order transactions executed per minute. Given the required mix and a wide range of complexity and types among the transactions, this metric most closely simulates a comprehensive business activity, not just one or two transactions or computer operations. For this reason, the tpm-C metric is considered to be a measure of business throughput.
+
+The tpm-C unit of measure is expressed as transactions-per-minute-C, whereas "C" stands for TPC-C specific benchmark.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The official TPC-C Benchmark specification can be accessed at - <http://www.tpc.org/tpc_documents_current_versions/pdf/tpc-c_v5.11.0.pdf>. Some of the rules of this specification are generally not fulfilled in the industry, because they are too strict for industry reality. For example, Scaling rules - (a) tpm-C / Warehouse must be >9 and <12.86 (implying that a very high warehouses rate is required in order to achieve a high tpm-C rate, which also means that an extremely large database and memory capacity are required); and (b) 10x terminals x Warehouses (implying a huge quantity of simulated clients).
+
+## System-Level Optimization
+
+Follow the instructions in the **MOT Server Optimization - x86** section. The following section describes the key system-level optimizations for deploying the MogDB database on a Huawei Taishan server and on a Euler 2.8 operating system for ultimate performance.
+
+## BenchmarkSQL - An Open-Source TPC-C Tool
+
+For example, to test TPCC, the **BenchmarkSQL** can be used, as follows -
+
+- Download **benchmarksql** from the following link - <https://osdn.net/frs/g_redir.php?m=kent&f=benchmarksql%2Fbenchmarksql-5.0.zip>
+- The schema creation scripts in the **benchmarksql** tool need to be adjusted to MOT syntax and unsupported DDLs need to be avoided. The adjusted scripts can be directly downloaded from the following link - <https://opengauss.obs.cn-south-1.myhuaweicloud.com/1.1.0/MOT-TPCC-Benchmark.tar.gz>. The contents of this tar file includes sql.common.mogdb.mot folder and jTPCCTData.java file as well as a sample configuration file postgresql.conf and a TPCC properties file props.mot for reference.
+- Place the sql.common.mogdb.mot folder in the same level as sql.common under run folder and replace the file src/client/jTPCCTData.java with the downloaded java file.
+- Edit the file runDatabaseBuild.sh under run folder to remove **extraHistID** from **AFTER_LOAD** list to avoid unsupported alter table DDL.
+- Replace the JDBC driver under lib/postgres folder with the MogDB JDBC driver available from the following link - <https://opengauss.org/en/download.html>.
+
+The only change done in the downloaded java file (compared to the original one) was to comment the error log printing for serialization and duplicate key errors. These errors are normal in case of MOT, since it uses Optimistic Concurrency Control (OCC) mechanism.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The benchmark test is executed using a standard interactive SQL mode without stored procedures.
+
+## Running the Benchmark
+
+Anyone can run the benchmark by starting up the server and running the **benchmarksql** scripts.
+
+To run the benchmark -
+
+1. Go to the **benchmarksql** run folder and rename sql.common to sql.common.orig.
+2. Create a link sql.common to sql.common.mogdb.mot in order to test MOT.
+3. Start up the database server.
+4. Configure the props.pg file in the client.
+5. Run the benchmark.
+
+## Results Report
+
+- Results in CLI
+
+  BenchmarkSQL results should appear as follows -
+
+  ![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-sample-tpcc-benchmark-1.jpg)
+
+  Over time, the benchmark measures and averages the committed transactions. The example above benchmarks for two minutes.
+
+  The score is **2.71M tmp-C** (new-orders per-minute), which is 45% of the total committed transactions, meaning the **tpmTOTAL**.
+
+- Detailed Result Report
+
+  The following is an example of a detailed result report -
+
+  **Figure 1** Detailed Result Report
+
+  ![detailed-result-report](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-sample-tpcc-benchmark-2.png)
+
+  ![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-sample-tpcc-benchmark-3.png)
+
+  BenchmarkSQL collects detailed performance statistics and operating system performance data (if configured).
+
+  This information can show the latency of the queries, and thus expose bottlenecks related to storage/network/CPU.
+
+- Results of TPC-C of MOT on Huawei Taishan 2480
+
+  Our TPC-C benchmark dated 01-May-2020 with an MogDB database installed on Taishan 2480 server (a 4-socket ARM/Kunpeng server), achieved a throughput of 4.79M tpm-C.
+
+  A near linear scalability was demonstrated, as shown below -
+
+  **Figure 2** Results of TPC-C of MOT on Huawei Taishan 2480
+
+  ![results-of-tpc-c-of-mot-on-huawei-taishan-2480](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-sample-tpcc-benchmark-4.png)
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-1.md b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-1.md
new file mode 100644
index 0000000000000000000000000000000000000000..3b0a39a439eda8d332f6527826490c6da449b2f3
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-1.md
@@ -0,0 +1,90 @@
+---
+title: MOT Scale-up Architecture
+summary: MOT Scale-up Architecture
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# MOT Scale-up Architecture
+
+To **scale up** means to add additional cores to the *same machine* in order to add computing power. To scale up refers to the most common traditional form of adding computing power in a machine that has a single pair of controllers and multiple cores. Scale-up architecture is limited by the scalability limits of a machine’s controller.
+
+## Technical Requirements
+
+MOT has been designed to achieve the following -
+
+- **Linear Scale-up -** MOT delivers a transactional storage engine that utilizes all the cores of a single NUMA architecture server in order to provide near-linear scale-up performance. This means that MOT is targeted to achieve a direct, near-linear relationship between the quantity of cores in a machine and the multiples of performance increase.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The near-linear scale-up results achieved by MOT significantly outperform all other existing solutions, and come as close as possible to achieving optimal results, which are limited by the physical restrictions and limitations of hardware, such as wires.
+
+- **No Maximum Number of Cores Limitation -** MOT does not place any limits on the maximum quantity of cores. This means that MOT is scalable from a single core up to 1,000s of cores, with minimal degradation per additional core, even when crossing NUMA socket boundaries.
+
+- **Extremely High Transactional Throughout -** MOT delivers a transactional storage engine that can achieve extremely high transactional throughout compared with any other OLTP vendor on the market.
+
+- **Extremely Low Transactional Latency -** MOT delivers a transactional storage engine that can reach extremely low transactional latency compared with any other OLTP vendor on the market.
+
+- **Seamless Integration and Leveraging with/of MogDB -** MOT integrates its transactional engine in a standard and seamless manner with the MogDB product. In this way, MOT reuses maximum functionality from the MogDB layers that are situated on top of its transactional storage engine.
+
+## Design Principles
+
+To achieve the requirements described above (especially in an environment with many-cores), our storage engine's architecture implements the following techniques and strategies -
+
+- **Data and indexes only reside in memory**.
+- **Data and indexes are not laid out with physical partitions** (because these might achieve lower performance for certain types of applications).
+- Transaction concurrency control is based on **Optimistic Concurrency Control (OCC)** without any centralized contention points. See the **MOT Concurrency Control Mechanism** section for more information about OCC.
+- **Parallel Redo Logs (ultimately per core)** are used to efficiently avoid a central locking point.
+- **Indexes are lock-free**. See the **MOT Indexes** section for more information about lock-free indexes.
+- **NUMA-awareness memory allocation** is used to avoid cross-socket access, especially for session lifecycle objects. See the **NUMA Awareness Allocation and Affinity** section for more information about NUMA-awareness.
+- **A customized MOT memory management allocator** with pre-cached object pools is used to avoid expensive runtime allocation and extra points of contention. This dedicated MOT memory allocator makes memory allocation more efficient by pre-accessing relatively large chunks of memory from the operation system as needed and then divvying it out to the MOT as needed.
+
+## Integration using Foreign Data Wrappers (FDW)
+
+MOT complies with and leverages MogDB's standard extensibility mechanism - Foreign Data Wrapper (FDW), as shown in the following diagram.
+
+The PostgreSQL Foreign Data Wrapper (FDW) feature enables the creation of foreign tables in an MOT database that are proxies for some other data source, such as Oracle, MySQL, PostgreSQL and so on. When a query is made on a foreign table, the FDW queries the external data source and returns the results, as if they were coming from a table in your database.
+
+MogDB relies on the PostgreSQL Foreign Data Wrappers (FDW) and Index support so that SQL is entirely covered, including stored procedures, user defined functions, system functions calls.
+
+**Figure 1** MOT Architecture
+
+![mot-architecture](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-scale-up-architecture-2.png)
+
+In the diagram above, the MOT engine is represented in green, while the existing MogDB (based on Postgres) components are represented in the top part of this diagram in blue. As you can see, the Foreign Data Wrapper (FDW) mediates between the MOT engine and the MogDB components.
+
+**MOT-Related FDW Customizations**
+
+Integrating MOT through FDW enables the reuse of the most upper layer MogDB functionality and therefore significantly shortened MOT's time-to-market without compromising SQL coverage.
+
+However, the original FDW mechanism in MogDB was not designed for storage engine extensions, and therefore lacks the following essential functionalities -
+
+- Index awareness of foreign tables to be calculated in the query planning phase
+- Complete DDL interfaces
+- Complete transaction lifecycle interfaces
+- Checkpoint interfaces
+- Redo Log interface
+- Recovery interfaces
+- Vacuum interfaces
+
+In order to support all the missing functionalities, the SQL layer and FDW interface layer were extended to provide the necessary infrastructure in order to enable the plugging in of the MOT transactional storage engine.
+
+## Result - Linear Scale-up
+
+The following shows the results achieved by the MOT design principles and implementation described above.
+
+To the best of our knowledge, MOT outperforms all existing industry-grade OLTP databases in transactional throughput of ACID-compliant workloads.
+
+MogDB and MOT have been tested on the following many-core systems with excellent performance scalability results. The tests were performed both on x86 Intel-based and ARM/Kunpeng-based many-core servers. You may refer to the **MOT Performance Benchmarks** section for more detailed performance review.
+
+Our TPC-C benchmark dated June 2020 tested an MogDB MOT database on a Taishan 2480 server. A 4-socket ARM/Kunpeng server, achieved throughput of 4.8 M tpmC. The following graph shows the near-linear nature of the results, meaning that it shows a significant increase in performance correlating to the increase of the quantity of cores -
+
+**Figure 2** TPC-C on ARM (256 Cores)
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-performance-benchmarks-12.png)
+
+The following is an additional example that shows a test on an x86-based server also showing CPU utilization.
+
+**Figure 3** tpmC vs CPU Usage
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-performance-benchmarks-18.png)
+
+The chart shows that MOT demonstrates a significant performance increase correlation with an increase of the quantity of cores. MOT consumes more and more of the CPU correlating to the increase of the quantity of cores. Other industry solutions do not increase and sometimes show slightly degraded performance, which is a well-known problem in the database industry that affects customers’ CAPEX and OPEX expenses and operational efficiency.
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-2.md b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-2.md
new file mode 100644
index 0000000000000000000000000000000000000000..aab31c2a03baeef5b1ebf3c8cc0b8fbbe8e77365
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-2.md
@@ -0,0 +1,179 @@
+---
+title: MOT Concurrency Control Mechanism
+summary: MOT Concurrency Control Mechanism
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# MOT Concurrency Control Mechanism
+
+After investing extensive research to find the best concurrency control mechanism, we concluded that SILO based on OCC is the best ACID-compliant OCC algorithm for MOT. SILO provides the best foundation for MOT's challenging requirements.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** MOT is fully Atomicity, Consistency, Isolation, Durability (ACID)-compliant, as described in the **MOT Introduction** section.
+
+The following topics describe MOT's concurrency control mechanism -
+
+## MOT Local and Global Memory
+
+SILO manages both a local memory and a global memory, as shown in Figure 1.
+
+- **Global** memory is long-term shared memory is shared by all cores and is used primarily to store all the table data and indexes
+- **Local** memory is short-term memory that is used primarily by sessions for handling transactions and store data changes in a primate to transaction memory until the commit phase.
+
+When a transaction change is required, SILO handles the copying of all that transaction's data from the global memory into the local memory. Minimal locks are placed on the global memory according to the OCC approach, so that the contention time in the global shared memory is extremely minimal. After the transaction’ change has been completed, this data is pushed back from the local memory to the global memory.
+
+The basic interactive transactional flow with our SILO-enhanced concurrency control is shown in the figure below -
+
+**Figure 1** Private (Local) Memory (for each transaction) and a Global Memory (for all the transactions of all the cores)
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-concurrency-control-mechanism-2.png)
+
+For more details, refer to the Industrial-Strength OLTP Using Main Memory and Many-cores document [**Comparison - Disk vs. MOT**].
+
+## MOT SILO Enhancements
+
+SILO in its basic algorithm flow outperformed many other ACID-compliant OCCs that we tested in our research experiments. However, in order to make it a product-grade mechanism, we had to enhance it with many essential functionalities that were missing in the original design, such as -
+
+- Added support for interactive mode transactions, where transactions are running SQL by SQL from the client side and not as a single step on the server side
+- Added optimistic inserts
+- Added support for non-unique indexes
+- Added support for read-after-write in transactions so that users can see their own changes before they are committed
+- Added support for lockless cooperative garbage collection
+- Added support for lockless checkpoints
+- Added support for fast recovery
+- Added support for two-phase commit in a distributed deployment
+
+Adding these enhancements without breaking the scalable characteristic of the original SILO was very challenging.
+
+## MOT Isolation Levels
+
+Even though MOT is fully ACID-compliant (as described in the section), not all isolation levels are supported in MogDB 2.1. The following table describes all isolation levels, as well as what is and what is not supported by MOT.
+
+**Table 1** Isolation Levels
+
+| Isolation Level  | Description                                                  |
+| :--------------- | :----------------------------------------------------------- |
+| READ UNCOMMITTED | **Not supported by MOT.**                                    |
+| READ COMMITTED   | **Supported by MOT.**<br/>The READ COMMITTED isolation level that guarantees that any data that is read was already committed when it was read. It simply restricts the reader from seeing any intermediate, uncommitted or dirty reads. Data is free to be changed after it has been read so that READ COMMITTED does not guarantee that if the transaction re-issues the read, that the same data will be found. |
+| SNAPSHOT         | **Not supported by MOT.**<br/>The SNAPSHOT isolation level makes the same guarantees as SERIALIZABLE, except that concurrent transactions can modify the data. Instead, it forces every reader to see its own version of the world (its own snapshot). This makes it very easy to program, plus it is very scalable, because it does not block concurrent updates. However, in many implementations this isolation level requires higher server resources. |
+| REPEATABLE READ  | **Supported by MOT.**<br/>REPEATABLE READ is a higher isolation level that (in addition to the guarantees of the READ COMMITTED isolation level) guarantees that any data that is read cannot change. If a transaction reads the same data again, it will find the same previously read data in place, unchanged and available to be read.<br/>Because of the optimistic model, concurrent transactions are not prevented from updating rows read by this transaction. Instead, at commit time this transaction validates that the REPEATABLE READ isolation level has not been violated. If it has, this transaction is rolled back and must be retried. |
+| SERIALIZABLE     | **Not supported by MOT**.<br/>Serializable isolation makes an even stronger guarantee. In addition to everything that the REPEATABLE READ isolation level guarantees, it also guarantees that no new data can be seen by a subsequent read.<br/>It is named SERIALIZABLE because the isolation is so strict that it is almost a bit like having the transactions run in series rather than concurrently. |
+
+The following table shows the concurrency side effects enabled by the different isolation levels.
+
+**Table 2** Concurrency Side Effects Enabled by Isolation Levels
+
+| Isolation Level  | Description | Non-repeatable Read | Phantom |
+| :--------------- | :---------- | :------------------ | :------ |
+| READ UNCOMMITTED | Yes         | Yes                 | Yes     |
+| READ COMMITTED   | No          | Yes                 | Yes     |
+| REPEATABLE READ  | No          | No                  | Yes     |
+| SNAPSHOT         | No          | No                  | No      |
+| SERIALIZABLE     | No          | No                  | No      |
+
+In the near future release, MogDB MOT will also support both SNAPSHOT and SERIALIZABLE isolation levels.
+
+## MOT Optimistic Concurrency Control
+
+The Concurrency Control Module (CC Module for short) provides all the transactional requirements for the Main Memory Engine. The primary objective of the CC Module is to provide the Main Memory Engine with support for various isolation levels.
+
+### Optimistic OCC vs. Pessimistic 2PL
+
+The functional differences of Pessimistic 2PL (2-Phase Locking) vs. Optimistic Concurrency Control (OCC) involve pessimistic versus optimistic approaches to transaction integrity.
+
+Disk-based tables use a pessimistic approach, which is the most commonly used database method. The MOT Engine use an optimistic approach.
+
+The primary functional difference between the pessimistic approach and the optimistic approach is that if a conflict occurs -
+
+- The pessimistic approach causes the client to wait.
+- The optimistic approach causes one of the transactions to fail, so that the failed transaction must be retried by the client.
+
+**Optimistic Concurrency Control Approach (Used by MOT)**
+
+The **Optimistic Concurrency Control (OCC)** approach detects conflicts as they occur, and performs validation checks at commit time.
+
+The optimistic approach has less overhead and is usually more efficient, partly because transaction conflicts are uncommon in most applications.
+
+The functional differences between optimistic and pessimistic approaches is larger when the REPEATABLE READ isolation level is enforced and is largest for the SERIALIZABLE isolation level.
+
+**Pessimistic Approaches (Not used by MOT)**
+
+The **Pessimistic Concurrency Control** (2PL or 2-Phase Locking) approach uses locks to block potential conflicts before they occur. A lock is applied when a statement is executed and released when the transaction is committed. Disk-based row-stores use this approach (with the addition of Multi-version Concurrency Control [MVCC]).
+
+In 2PL algorithms, while a transaction is writing a row, no other transaction can access it; and while a row is being read, no other transaction can overwrite it. Each row is locked at access time for both reading and writing; and the lock is released at commit time. These algorithms require a scheme for handling and avoiding deadlock. Deadlock can be detected by calculating cycles in a wait-for graph. Deadlock can be avoided by keeping time ordering using TSO or by some kind of back-off scheme.
+
+**Encounter Time Locking (ETL)**
+
+Another approach is Encounter Time Locking (ETL), where reads are handled in an optimistic manner, but writes lock the data that they access. As a result, writes from different ETL transactions are aware of each other and can decide to abort. It has been empirically verified that ETL improves the performance of OCC in two ways -
+
+- First, ETL detects conflicts early on and often increases transaction throughput. This is because transactions do not perform useless operations, because conflicts discovered at commit time (in general) cannot be solved without aborting at least one transaction.
+- Second, encounter-time locking Reads-After-Writes (RAW) are handled efficiently without requiring expensive or complex mechanisms.
+
+**Conclusion**
+
+OCC is the fastest option for most workloads. This finding has also been observed in our preliminary research phase.
+
+One of the reasons is that when every core executes multiple threads, a lock is likely to be held by a swapped thread, especially in interactive mode. Another reason is that pessimistic algorithms involve deadlock detection (which introduces overhead) and usually uses read-write locks (which are less efficient than standard spin-locks).
+
+We have chosen Silo because it was simpler than other existing options, such as TicToc, while maintaining the same performance for most workloads. ETL is sometimes faster than OCC, but it introduces spurious aborts which may confuse a user, in contrast to OCC which aborts only at commit.
+
+### OCC vs 2PL Differences by Example
+
+The following shows the differences between two user experiences - Pessimistic (for disk-based tables) and Optimistic (MOT tables) when sessions update the same table simultaneously.
+
+In this example, the following table test command is run -
+
+```
+table "TEST" - create table test (x int, y int, z int, primary key(x));
+```
+
+This example describes two aspects of the same test - user experience (operations in the example) and retry requirements.
+
+**Example Pessimistic Approach - Used in Disk-based Tables**
+
+The following is an example of the Pessimistic approach (which is not Mot). Any Isolation Level may apply.
+
+The following two sessions perform a transaction that attempts to update a single table.
+
+A WAIT LOCK action occurs and the client experience is that session #2 is *stuck* until Session #1 has completed a COMMIT. Only afterwards, is Session #2 able to progress.
+
+However, when this approach is used, both sessions succeed and no abort occurs (unless SERIALIZABLE or REPEATABLE-READ isolation level is applied), which results in the entire transaction needing to be retried.
+
+**Table 1** Pessimistic Approach Code Example
+
+|      | Session 1                        | Session 2                                                    |
+| :--- | :------------------------------- | :----------------------------------------------------------- |
+| t0   | Begin                            | Begin                                                        |
+| t1   | update test set y=200 where x=1; |                                                              |
+| t2   | y=200                            | Update test set y=300 where x=1; - Wait on lock              |
+| t4   | Commit                           |                                                              |
+|      |                                  | Unlock                                                       |
+|      |                                  | Commit(in READ-COMMITTED this will succeed, in SERIALIZABLE it will fail) |
+|      |                                  | y = 300                                                      |
+
+**Example Optimistic Approach - Used in MOT**
+
+The following is an example of the Optimistic approach.
+
+It describes the situation of creating an MOT table and then having two concurrent sessions updating that same MOT table simultaneously -
+
+```
+create foreign table test (x int, y int, z int, primary key(x));
+```
+
+- The advantage of OCC is that there are no locks until COMMIT.
+- The disadvantage of using OCC is that the update may fail if another session updates the same record. If the update fails (in all supported isolation levels), an entire SESSION #2 transaction must be retried.
+- Update conflicts are detected by the kernel at commit time by using a version checking mechanism.
+- SESSION #2 will not wait in its update operation and will be aborted because of conflict detection at commit phase.
+
+**Table 2** Optimistic Approach Code Example - Used in MOT
+
+|      | Session 1                        | Session 2                        |
+| :--- | :------------------------------- | :------------------------------- |
+| t0   | Begin                            | Begin                            |
+| t1   | update test set y=200 where x=1; |                                  |
+| t2   | y=200                            | Update test set y=300 where x=1; |
+| t4   | Commit                           | y = 300                          |
+|      |                                  | Commit                           |
+|      |                                  | ABORT                            |
+|      |                                  | y = 200                          |
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-3.md b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-3.md
new file mode 100644
index 0000000000000000000000000000000000000000..3af831038f8bfda7238c36d37d0f6be5afea3f97
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-3.md
@@ -0,0 +1,59 @@
+---
+title: Extended FDW and Other MogDB Features
+summary: Extended FDW and Other MogDB Features
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# Extended FDW and Other MogDB Features
+
+MogDB is based on PostgreSQL, which does not have a built-in storage engine adapter, such as MySQL handlerton. To enable the integration of the MOT storage engine into MogDB, we have leveraged and extended the existing Foreign Data Wrapper (FDW) mechanism. With the introduction of FDW into PostgreSQL 9.1, externally managed databases can now be accessed in a way that presents these foreign tables and data sources as united, locally accessible relations.
+
+In contrast, the MOT storage engine is embedded inside MogDB and its tables are managed by it. Access to tables is controlled by the MogDB planner and executor. MOT gets logging and checkpointing services from MogDB and participates in the MogDB recovery process in addition to other processes.
+
+We refer to all the components that are in use or are accessing the MOT storage engine as the *Envelope*.
+
+The following figure shows how the MOT storage engine is embedded inside MogDB and its bi-directional access to database functionality.
+
+**Figure 1** MOT Storage Engine Embedded inside MogDB - FDW Access to External Databases
+
+![mot-architecture](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-scale-up-architecture-2.png)
+
+We have extended the capabilities of FDW by extending and modifying the FdwRoutine structure in order to introduce features and calls that were not required before the introduction of MOT. For example, support for The following new features was added - Add Index, Drop Index/Table, Truncate, Vacuum and Table/Index Memory Statistics. A significant emphasis was put on integration with MogDB logging, replication and checkpointing mechanisms in order to provide consistency for cross-table transactions through failures. In this case, the MOT itself sometimes initiates calls to MogDB functionality through the FDW layer.
+
+## Creating Tables and Indexes
+
+In order to support the creation of MOT tables, standard FDW syntax was reused.
+
+For example, create FOREIGN table.
+
+The MOT FDW mechanism passes the instruction to the MOT storage engine for actual table creation. Similarly, we support index creation (create index …). This feature was not previously available in FDW, because it was not needed since its tables are managed externally.
+
+To support both in MOT FDW, the **ValidateTableDef** function actually creates the specified table. It also handles the index creation of that relation, as well as DROP TABLE and DROP INDEX, in addition to VACUUM and ALTER TABLE, which were not previously supported in FDW.
+
+## Index Usage for Planning and Execution
+
+A query has two phases - **Planning** and **Execution**. During the Planning phase (which may take place once per multiple executions), the best index for the scan is chosen. This choice is made based on the matching query's WHERE clauses, JOIN clauses and ORDER BY conditions. During execution, a query iterates over the relevant table rows and performs various tasks, such as update or delete, per iteration. An insert is a special case where the table adds the row to all indexes and no scanning is required.
+
+- **Planner -** In standard FDW, a query is passed for execution to a foreign data source. This means that index filtering and the actual planning (such as the choice of indexes) is not performed locally in the database, rather it is performed in the external data source. Internally, the FDW returns a general plan to the database planner. MOT tables are handled in a similar manner as disk tables. This means that relevant MOT indexes are filtered and matched, and the indexes that minimize the set of traversed rows are selected and are added to the plan.
+- **Executor -** The Query Executor uses the chosen MOT index in order to iterate over the relevant rows of the table. Each row is inspected by the MogDB envelope, and according to the query conditions, an update or delete is called to handle the relevant row.
+
+## Durability, Replication and High Availability
+
+A storage engine is responsible for storing, reading, updating and deleting data in the underlying memory and storage systems. The logging, checkpointing and recovery are not handled by the storage engine, especially because some transactions encompass multiple tables with different storage engines. Therefore, in order to persist and replicate data, the high-availability facilities from the MogDB envelope are used as follows -
+
+- **Durability -** In order to ensure Durability, the MOT engine persists data by Write-Ahead Logging (WAL) records using the MogDB's XLOG interface. This also provides the benefits of MogDB's replication capabilities that use the same APIs. You may refer to the **MOT Durability Concepts** for more information.
+- **Checkpointing -** A MOT Checkpoint is enabled by registering a callback to the MogDB Checkpointer. Whenever a general database Checkpoint is performed, the MOT Checkpoint process is called as well. MOT keeps the Checkpoint's Log Sequence Number (LSN) in order to be aligned with MogDB recovery. The MOT Checkpointing algorithm is highly optimized and asynchronous and does not stop concurrent transactions. You may refer to the **MOT Checkpoint Concepts** for more information.
+- **Recovery -** Upon startup, MogDB first calls an MOT callback that recovers the MOT Checkpoint by loading into memory rows and creating indexes, followed by the execution of the WAL recovery by replaying records according to the Checkpoint's LSN. The MOT Checkpoint is recovered in parallel using multiple threads - each thread reads a different data segment. This makes MOT Checkpoint recovery quite fast on many-core hardware, though it is still potentially slower compared to disk-based tables where only WAL records are replayed. You may refer to the **MOT Recovery Concepts** for more information.
+
+## VACUUM and DROP
+
+In order to maximize MOT functionality, we added support for VACUUM, DROP TABLE and DROP INDEX. All three execute with an exclusive table lock, meaning without allowing concurrent transactions on the table. The system VACUUM calls a new FDW function to perform the MOT vacuuming, while DROP was added to the ValidateTableDef() function.
+
+## Deleting Memory Pools
+
+Each index and table tracks all the memory pools that it uses. A DROP INDEX command is used to remove metadata. Memory pools are deleted as a single consecutive block. The MOT VACUUM only compacts used memory, because memory reclamation is performed continuously in the background by the epoch-based Garbage Collector (GC). In order to perform the compaction, we switch the index or the table to new memory pools, traverse all the live data, delete each row and insert it using the new pools and finally delete the pools as is done for a drop.
+
+## Query Native Compilation (JIT)
+
+The FDW adapter to MOT engine also contains a lite execution path that employs Just-In-Time (JIT) compiled query execution using the LLVM compiler. More information about MOT Query Native Compilation can be found in the **Query Native Compilation (JIT)** section.
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-4.md b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-4.md
new file mode 100644
index 0000000000000000000000000000000000000000..0194a6b5c0ca52d4ddac1cb6ecc1fff8bd75f2b5
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-4.md
@@ -0,0 +1,22 @@
+---
+title: NUMA Awareness Allocation and Affinity
+summary: NUMA Awareness Allocation and Affinity
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# NUMA Awareness Allocation and Affinity
+
+Non-Uniform Memory Access (NUMA) is a computer memory design used in multiprocessing, where the memory access time depends on the memory location relative to the processor. Under NUMA, a processor can take advantage of NUMA by preferring to access its own local memory (which is faster), rather than accessing non-local memory (meaning that it will prefer **not** to access the local memory of another processor or memory shared between processors).
+
+MOT memory access has been designed with NUMA awareness. This means that MOT is aware that memory is not uniform and achieves best performance by accessing the quickest and most local memory.
+
+The benefits of NUMA are limited to certain types of workloads, particularly on servers where the data is often strongly associated with certain tasks or users.
+
+In-memory database systems running on NUMA platforms face several issues, such as the increased latency and the decreased bandwidth when accessing remote main memory. To cope with these NUMA-related issues, NUMA awareness must be considered as a major design principle for the fundamental architecture of a database system.
+
+To facilitate quick operation and make efficient use of NUMA nodes, MOT allocates a designated memory pool for rows per table and for nodes per index. Each memory pool is composed from 2 MB chunks. A designated API allocates these chunks from a local NUMA node, from pages coming from all nodes or in a round-robin fashion, where each chunk is allocated on the next node. By default, pools of shared data are allocated in a round robin fashion in order to balance access, while not splitting rows between different NUMA nodes. However, thread private memory is allocated from a local node. It must also be verified that a thread always operates in the same NUMA node.
+
+**Summary**
+
+MOT has a smart memory control module that has preallocated memory pools intended for various types of memory objects. This smart memory control improves performance, reduces locks and ensures stability. The allocation of the memory objects of a transaction is always NUMA-local, ensuring optimal performance for CPU memory access and resulting in low latency and reduced contention. Deallocated objects go back to the memory pool. Minimized use of OS malloc functions during transactions circumvents unnecessary locks.
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-5.md b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-5.md
new file mode 100644
index 0000000000000000000000000000000000000000..016a23dd0c18a64b8c7ced456d9edc851899fa95
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-5.md
@@ -0,0 +1,41 @@
+---
+title: MOT Indexes
+summary: MOT Indexes
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# MOT Indexes
+
+MOT Index is a lock-free index based on state-of-the-art Masstree, which is a fast and scalable Key Value (KV) store for multicore systems, implemented as tries of B+ trees. It achieves excellent performance on many-core servers and high concurrent workloads. It uses various advanced techniques, such as an optimistic lock approach, cache-awareness and memory prefetching.
+
+After comparing various state-of-the-art solutions, we chose Masstree for the index because it demonstrated the best overall performance for point queries, iterations and modifications. Masstree is a combination of tries and a B+ tree that is implemented to carefully exploit caching, prefetching, optimistic navigation and fine-grained locking. It is optimized for high contention and adds various optimizations to its predecessors, such as OLFIT. However, the downside of a Masstree index is its higher memory consumption. While row data consumes the same memory size, the memory per row per each index (primary or secondary) is higher on average by 16 bytes - 29 bytes in the lock-based B-Tree used in disk-based tables vs. 45 bytes in MOT's Masstree.
+
+Our empirical experiments showed that the combination of the mature lock-free Masstree implementation and our robust improvements to Silo have provided exactly what we needed in that regard.
+
+Another challenge was making an optimistic insertion into a table with multiple indexes.
+
+The Masstree index is at the core of MOT memory layout for data and index management. Our team enhanced and significantly improved Masstree and submitted some of the key contributions to the Masstree open source. These improvements include -
+
+- Dedicated memory pools per index - Efficient allocation and fast index drop
+- Global GC for Masstree - Fast, on-demand memory reclamation
+- Masstree iterator implementation with access to an insertion key
+- ARM architecture support
+
+We contributed our Masstree index improvements to the Masstree open-source implementation, which can be found here - <https://github.com/kohler/masstree-beta>.
+
+MOT's main innovation was to enhance the original Masstree data structure and algorithm, which did not support Non-Unique Indexes (as a Secondary index). You may refer to the **Non-unique Indexes** section for the design details.
+
+MOT supports both Primary, Secondary and Keyless indexes (subject to the limitations specified in the **Unsupported Index DDLs and Index**section).
+
+## Non-unique Indexes
+
+A non-unique index may contain multiple rows with the same key. Non-unique indexes are used solely to improve query performance by maintaining a sorted order of data values that are used frequently. For example, a database may use a non-unique index to group all people from the same family. However, the Masstree data structure implementation does not allow the mapping of multiple objects to the same key. Our solution for enabling the creation of non-unique indexes (as shown in the figure below) is to add a symmetry-breaking suffix to the key, which maps the row. This added suffix is the pointer to the row itself, which has a constant size of 8 bytes and a value that is unique to the row. When inserting into a non-unique index, the insertion of the sentinel always succeeds, which enables the row allocated by the executing transaction to be used. This approach also enable MOT to have a fast, reliable, order-based iterator for a non-unique index.
+
+**Figure 1** Non-unique Indexes
+
+![non-unique-indexes](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-indexes-2.png)
+
+The structure of an MOT table T that has three rows and two indexes is depicted in the figure above. The rectangles represent data rows, and the indexes point to sentinels (the elliptic shapes) which point to the rows. The sentinels are inserted into unique indexes with a key and into non-unique indexes with a key + a suffix. The sentinels facilitate maintenance operations so that the rows can be replaced without touching the index data structure. In addition, there are various flags and a reference count embedded in the sentinel in order to facilitate optimistic inserts.
+
+When searching a non-unique secondary index, the required key (for example, the family name) is used. The fully concatenated key is only used for insert and delete operations. Insert and delete operations always get a row as a parameter, thereby making it possible to create the entire key and to use it in the execution of the deletion or the insertion of the specific row for the index.
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-6.md b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-6.md
new file mode 100644
index 0000000000000000000000000000000000000000..9f4b3ea27c7c53f0a5f2c8c27275ee0a142c853d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-6.md
@@ -0,0 +1,204 @@
+---
+title: MOT Durability Concepts
+summary: MOT Durability Concepts
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# MOT Durability Concepts
+
+Durability refers to long-term data protection (also known as *disk persistence*). Durability means that stored data does not suffer from any kind of degradation or corruption, so that data is never lost or compromised. Durability ensures that data and the MOT engine are restored to a consistent state after a planned shutdown (for example, for maintenance) or an unplanned crash (for example, a power failure).
+
+Memory storage is volatile, meaning that it requires power to maintain the stored information. Disk storage, on the other hand, is non-volatile, meaning that it does not require power to maintain stored information, thus, it can survive a power shutdown. MOT uses both types of storage - it has all data in memory, while persisting transactional changes to disk **MOT Durability** and by maintaining frequent periodic **MOT Checkpoints** in order to ensure data recovery in case of shutdown.
+
+The user must ensure sufficient disk space for the logging and Checkpointing operations. A separated drive can be used for the Checkpoint to improve performance by reducing disk I/O load.
+
+You may refer to **MOT Key Technologies** section__for an overview of how durability is implemented in the MOT engine.
+
+MOTs WAL Redo Log and checkpoints enabled durability, as described below -
+
+- **MOT Logging - WAL Redo Log Concepts**
+- **MOT Checkpoint Concepts**
+
+## MOT Logging - WAL Redo Log Concepts
+
+### Overview
+
+Write-Ahead Logging (WAL) is a standard method for ensuring data durability. The main concept of WAL is that changes to data files (where tables and indexes reside) are only written after those changes have been logged, meaning only after the log records that describe the changes have been flushed to permanent storage.
+
+The MOT is fully integrated with the MogDB envelope logging facilities. In addition to durability, another benefit of this method is the ability to use the WAL for replication purposes.
+
+Three logging methods are supported, two standard Synchronous and Asynchronous, which are also supported by the standard MogDB disk-engine. In addition, in the MOT a Group-Commit option is provided with special NUMA-Awareness optimization. The Group-Commit provides the top performance while maintaining ACID properties.
+
+To ensure Durability, MOT is fully integrated with the MogDB's Write-Ahead Logging (WAL) mechanism, so that MOT persists data in WAL records using MogDB's XLOG interface. This means that every addition, update, and deletion to an MOT table's record is recorded as an entry in the WAL. This ensures that the most current data state can be regenerated and recovered from this non-volatile log. For example, if three new rows were added to a table, two were deleted and one was updated, then six entries would be recorded in the log.
+
+- MOT log records are written to the same WAL as the other records of MogDB disk-based tables.
+
+- MOT only logs an operation at the transaction commit phase.
+
+- MOT only logs the updated delta record in order to minimize the amount of data written to disk.
+
+- During recovery, data is loaded from the last known or a specific Checkpoint; and then the WAL Redo log is used to complete the data changes that occur from that point forward.
+
+- The WAL (Redo Log) retains all the table row modifications until a Checkpoint is performed (as described above). The log can then be truncated in order to reduce recovery time and to save disk space.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** In order to ensure that the log IO device does not become a bottleneck, the log file must be placed on a drive that has low latency.
+
+### Logging Types
+
+Two synchronous transaction logging options and one asynchronous transaction logging option are supported (these are also supported by the standard MogDB disk engine). MOT also supports synchronous Group Commit logging with NUMA-awareness optimization, as described below.
+
+According to your configuration, one of the following types of logging is implemented:
+
+- **Synchronous Redo Logging**
+
+  The **Synchronous Redo Logging** option is the simplest and most strict redo logger. When a transaction is committed by a client application, the transaction redo entries are recorded in the WAL (Redo Log), as follows -
+
+  1. While a transaction is in progress, it is stored in the MOT’s memory.
+  2. After a transaction finishes and the client application sends a **Commit** command, the transaction is locked and then written to the WAL Redo Log on the disk. This means that while the transaction log entries are being written to the log, the client application is still waiting for a response.
+  3. As soon as the transaction's entire buffer is written to the log, the changes to the data in memory take place and then the transaction is committed. After the transaction has been committed, the client application is notified that the transaction is complete.
+
+- **Technical Description**
+
+  When a transaction ends, the SynchronousRedoLogHandler serializes its transaction buffer and write it to the XLOG iLogger implementation.
+
+  **Figure 1** Synchronous Logging
+
+  ![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-durability-concepts-6.png)
+
+  **Summary**
+
+  The **Synchronous Redo Logging** option is the safest and most strict because it ensures total synchronization of the client application and the WAL Redo log entries for each transaction as it is committed; thus ensuring total durability and consistency with absolutely no data loss. This logging option prevents the situation where a client application might mark a transaction as successful, when it has not yet been persisted to disk.
+
+  The downside of the **Synchronous Redo Logging** option is that it is the slowest logging mechanism of the three options. This is because a client application must wait until all data is written to disk and because of the frequent disk writes (which typically slow down the database).
+
+- **Group Synchronous Redo Logging**
+
+  The **Group Synchronous Redo Logging** option is very similar to the **Synchronous Redo Logging** option, because it also ensures total durability with absolutely no data loss and total synchronization of the client application and the WAL (Redo Log) entries. The difference is that the **Group Synchronous Redo Logging** option writes _groups of transaction_redo entries to the WAL Redo Log on the disk at the same time, instead of writing each and every transaction as it is committed. Using Group Synchronous Redo Logging reduces the amount of disk I/Os and thus improves performance, especially when running a heavy workload.
+
+  The MOT engine performs synchronous Group Commit logging with Non-Uniform Memory Access (NUMA)-awareness optimization by automatically grouping transactions according to the NUMA socket of the core on which the transaction is running.
+
+  You may refer to the **NUMA Awareness Allocation and Affinity** section for more information about NUMA-aware memory access.
+
+  When a transaction commits, a group of entries are recorded in the WAL Redo Log, as follows -
+
+  1. While a transaction is in progress, it is stored in the memory. The MOT engine groups transactions in buckets according to the NUMA socket of the core on which the transaction is running. This means that all the transactions running on the same socket are grouped together and that multiple groups will be filling in parallel according to the core on which the transaction is running.
+
+     > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+     >
+     > Each thread runs on a single core/CPU which belongs to a single socket and each thread only writes to the socket of the core on which it is running.
+
+  2. After a transaction finishes and the client application sends a Commit command, the transaction redo log entries are serialized together with other transactions that belong to the same group.
+
+  3. After the configured criteria are fulfilled for a specific group of transactions (quantity of committed transactions or timeout period as describes in the **REDO LOG (MOT)** section), the transactions in this group are written to the WAL on the disk. This means that while these log entries are being written to the log, the client applications that issued the commit are waiting for a response.
+
+  4. As soon as all the transaction buffers in the NUMA-aware group have been written to the log, all the transactions in the group are performing the necessary changes to the memory store and the clients are notified that these transactions are complete.
+
+     Writing transactions to the WAL is more efficient in this manner because all the buffers from the same socket are written to disk together.
+
+     **Technical Description**
+
+     The four colors represent 4 NUMA nodes. Thus each NUMA node has its own memory log enabling a group commit of multiple connections.
+
+     **Figure 2** Group Commit - with NUMA-awareness
+
+     ![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-durability-concepts-7.png)
+
+     **Summary**
+
+     The **Group Synchronous Redo Logging** option is a an extremely safe and strict logging option because it ensures total synchronization of the client application and the WAL Redo log entries; thus ensuring total durability and consistency with absolutely no data loss. This logging option prevents the situation where a client application might mark a transaction as successful, when it has not yet been persisted to disk.
+
+     On one hand this option has fewer disk writes than the **Synchronous Redo Logging** option, which may mean that it is faster. The downside is that transactions are locked for longer, meaning that they are locked until after all the transactions in the same NUMA memory have been written to the WAL Redo Log on the disk.
+
+     The benefits of using this option depend on the type of transactional workload. For example, this option benefits systems that have many transactions (and less so for systems that have few transactions, because there are few disk writes anyway).
+
+- **Asynchronous Redo Logging**
+
+  The **Asynchronous Redo Logging** option is the fastest logging method, However, it does not ensure no data loss, meaning that some data that is still in the buffer and was not yet written to disk may get lost upon a power failure or database crash. When a transaction is committed by a client application, the transaction redo entries are recorded in internal buffers and written to disk at preconfigured intervals. The client application does not wait for the data being written to disk. It continues to the next transaction. This is what makes asynchronous redo logging the fastest logging method.
+
+  When a transaction is committed by a client application, the transaction redo entries are recorded in the WAL Redo Log, as follows -
+
+  1. While a transaction is in progress, it is stored in the MOT's memory.
+  2. After a transaction finishes and the client application sends a Commit command, the transaction redo entries are written to internal buffers, but are not yet written to disk. Then changes to the MOT data memory take place and the client application is notified that the transaction is committed.
+  3. At a preconfigured interval, a redo log thread running in the background collects all the buffered redo log entries and writes them to disk.
+
+  **Technical Description**
+
+  Upon transaction commit, the transaction buffer is moved (pointer assignment - not a data copy) to a centralized buffer and a new transaction buffer is allocated for the transaction. The transaction is released as soon as its buffer is moved to the centralized buffer and the transaction thread is not blocked. The actual write to the log uses the Postgres walwriter thread. When the walwriter timer elapses, it first calls the AsynchronousRedoLogHandler (via registered callback) to write its buffers and then continues with its logic and flushes the data to the XLOG.
+
+  **Figure 3** Asynchronous Logging
+
+  ![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-durability-concepts-8.png)
+
+  **Summary**
+
+  The Asynchronous Redo Logging option is the fastest logging option because it does not require the client application to wait for data being written to disk. In addition, it groups many transactions redo entries and writes them together, thus reducing the amount of disk I/Os that slow down the MOT engine.
+
+  The downside of the Asynchronous Redo Logging option is that it does not ensure that data will not get lost upon a crash or failure. Data that was committed, but was not yet written to disk, is not durable on commit and thus cannot be recovered in case of a failure. The Asynchronous Redo Logging option is most relevant for applications that are willing to sacrifice data recovery (consistency) over performance.
+
+  Logging Design Details
+
+  The following describes the design details of each persistence-related component in the In-Memory Engine Module.
+
+  **Figure 4** Three Logging Options
+
+  ![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-durability-concepts-9.png)
+
+  The RedoLog component is used by both by backend threads that use the In-Memory Engine and by the WAL writer in order to persist their data. Checkpoints are performed using the Checkpoint Manager, which is triggered by the Postgres checkpointer.
+
+- **Logging Design Overview**
+
+  Write-Ahead Logging (WAL) is a standard method for ensuring data durability. WAL's central concept is that changes to data files (where tables and indexes reside) are only written after those changes have been logged, meaning after the log records that describe these changes have been flushed to permanent storage.
+
+  The MOT Engine uses the existing MogDB logging facilities, enabling it also to participate in the replication process.
+
+- **Per-transaction Logging**
+
+  In the In-Memory Engine, the transaction log records are stored in a transaction buffer which is part of the transaction object (TXN). The transaction buffer is logged during the calls to addToLog() - if the buffer exceeds a threshold it is then flushed and reused. When a transaction commits and passes the validation phase (OCC SILO**[Comparison - Disk vs. MOT] validation)** or aborts for some reason, the appropriate message is saved in the log as well in order to make it possible to determine the transaction's state during a recovery.
+
+  **Figure 5** Per-transaction Logging
+
+  ![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-durability-concepts-10.png)
+
+  Parallel Logging is performed both by MOT and disk engines. However, the MOT engine enhances this design with a log-buffer per transaction, lockless preparation and a single log record.
+
+- **Exception Handling**
+
+  The persistence module handles exceptions by using the Postgres error reporting infrastructure (ereport). An error message is recorded in the system log for each error condition. In addition, the error is reported to the envelope using Postgres’s built-in error reporting infrastructure.
+
+  The following exceptions are reported by this module -
+
+  **Table 1** Exception Handling
+
+  | Exception Condition                  | Exception Code                 | Scenario                                                     | Resulting Outcome      |
+  | :----------------------------------- | :----------------------------- | :----------------------------------------------------------- | :--------------------- |
+  | WAL write failure                    | ERRCODE_FDW_ERROR              | On any case the WAL write fails                              | Transaction terminates |
+  | File IO error: write, open and so on | ERRCODE_IO_ERROR               | Checkpoint - Called on any file access error                 | FATAL - process exists |
+  | Out of Memory                        | ERRCODE_INSUFFICIENT_RESOURCES | Checkpoint - Local memory allocation failures                | FATAL - process exists |
+  | Logic, DB errors                     | ERRCODE_INTERNAL_ERROR         | Checkpoint: algorithm fails or failure to retrieve table data or indexes. | FATAL - process exists |
+
+## MOT Checkpoint Concepts
+
+In MogDB, a Checkpoints is a snapshot of a point in the sequence of transactions at which it is guaranteed that the heap and index data files have been updated with all information written before the checkpoint.
+
+At the time of a Checkpoint, all dirty data pages are flushed to disk and a special checkpoint record is written to the log file.
+
+The data is stored directly in memory. The MOT does not store its data it the same way as MogDB so that the concept of dirty pages does not exist.
+
+For this reason, we have researched and implemented the CALC algorithm, which is described in the paper named Low-Overhead Asynchronous Checkpointing in Main-Memory Database Systems, SIGMOND 2016 from Yale University.
+
+Low-overhead asynchronous checkpointing in main-memory database systems.
+
+### CALC Checkpoint Algorithm - Low Overhead in Memory and Compute
+
+The checkpoint algorithm provides the following benefits -
+
+- **Reduced Memory Usage -** At most two copies of each record are stored at any time. Memory usage is minimized by only storing a single physical copy of a record while it is live and stable versions are equal or when no checkpoint is actively being recorded.
+- **Low Overhead -** CALC's overhead is smaller than other asynchronous checkpointing algorithms.
+- **Uses Virtual Points of Consistency -** CALC does not require quiescing of the database in order to achieve a physical point of consistency.
+
+### Checkpoint Activation
+
+MOT checkpoints are integrated into MogDB's envelope's Checkpoint mechanism. The Checkpoint process can be triggered manually by executing the **CHECKPOINT;** command or automatically according to the envelope's Checkpoint triggering settings (time/size).
+
+Checkpoint configuration is performed in the mot.conf file - see the **CHECKPOINT (MOT)** section.
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-7.md b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-7.md
new file mode 100644
index 0000000000000000000000000000000000000000..51d26498ba1d6d6eced781cf922dd5f0e8411cd9
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-7.md
@@ -0,0 +1,24 @@
+---
+title: MOT Recovery Concepts
+summary: MOT Recovery Concepts
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# MOT Recovery Concepts
+
+The MOT Recovery Module provides all the required functionality for recovering the MOT tables data. The main objective of the Recovery module is to restore the data and the MOT engine to a consistent state after a planned (maintenance for example) shut down or an unplanned (power failure for example) crash.
+
+MogDB database recovery, which is also sometimes called a *Cold Start*, includes MOT tables and is performed automatically with the recovery of the rest of the database. The MOT Recovery Module is seamlessly and fully integrated into the MogDB recovery process.
+
+MOT recovery has two main stages - Checkpoint Recovery and WAL Recovery (Redo Log).
+
+MOT checkpoint recovery is performed before the envelope's recovery takes place. This is done only at cold-start events (start of a PG process). It recovers the metadata first (schema) and then inserts all the rows from the current valid checkpoint, which is done in parallel by checkpoint_recovery_workers, each working on a different table. The indexes are created during the insert process.
+
+When checkpointing a table, it is divided into 16MB chunks, so that multiple recovery workers can recover the table in parallel. This is done in order to speed-up the checkpoint recovery, it is implemented as a multi-threaded procedure where each thread is responsible for recovering a different segment. There are no dependencies between different segments therefore there is no contention between the threads and there is no need to use locks when updating table or inserting new rows.
+
+WAL records are recovered as part of the envelope's WAL recovery. MogDB envelope iterates through the XLOG and performs the necessary operation based on the xlog record type. In case of entry with record type MOT, the envelope forwards it to MOT RecoveryManager for handling. The xlog entry will be ignored by MOT recovery, if it is 'too old' - its LSN is older than the checkpoint's LSN (Log Sequence Number).
+
+In an active-standby deployment, the standby server is always in a Recovery state for an automatic WAL recovery process.
+
+The MOT recovery parameters are set in the mot.conf file explained in the **[MOT Recovery](5-mot-administration#mot-recovery)** section.
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-8.md b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-8.md
new file mode 100644
index 0000000000000000000000000000000000000000..661cac1f9337f39acb9c6093215b9d02c18de05e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-8.md
@@ -0,0 +1,73 @@
+---
+title: MOT Query Native Compilation (JIT)
+summary: MOT Query Native Compilation (JIT)
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# MOT Query Native Compilation (JIT)
+
+MOT enables you to prepare and parse *pre-compiled full queries* in a native format (using a **PREPARE** statement) before they are needed for execution.
+
+This native format can later be executed (using an **EXECUTE** command) more efficiently. This type of execution is much more efficient because during execution the native format bypasses multiple database processing layers. This division of labor avoids repetitive parse analysis operations. The Lite Executor module is responsible for executing **prepared** queries and has a much faster execution path than the regular generic plan performed by the envelope. This is achieved using Just-In-Time (JIT) compilation via LLVM. In addition, a similar solution that has potentially similar performance is provided in the form of pseudo-LLVM.
+
+The following is an example of a **PREPARE** syntax in SQL:
+
+```
+PREPARE name [ ( data_type [, ...] ) ] AS statement
+```
+
+The following is an example of how to invoke a PREPARE and then an EXECUTE statement in a Java application -
+
+```
+conn = DriverManager.getConnection(connectionUrl, connectionUser, connectionPassword);
+
+// Example 1: PREPARE without bind settings
+String query = "SELECT * FROM getusers";
+PreparedStatement prepStmt1 = conn.prepareStatement(query);
+ResultSet rs1 = pstatement.executeQuery())
+while (rs1.next()) {…}
+
+// Example 2: PREPARE with bind settings
+String sqlStmt = "SELECT * FROM employees where first_name=? and last_name like ?";
+PreparedStatement prepStmt2 = conn.prepareStatement(sqlStmt);
+prepStmt2.setString(1, "Mark"); // first name "Mark"
+prepStmt2.setString(2, "%n%"); // last name contains a letter "n"
+ResultSet rs2 = prepStmt2.executeQuery())
+while (rs2.next()) {…}
+```
+
+## Prepare
+
+**PREPARE** creates a prepared statement. A prepared statement is a server-side object that can be used to optimize performance. When the **PREPARE** statement is executed, the specified statement is parsed, analyzed and rewritten.
+
+If the tables mentioned in the query statement are MOT tables, the MOT compilation takes charge of the object preparation and performs a special optimization by compiling the query into IR byte code based on LLVM.
+
+Whenever a new query compilation is required, the query is analyzed and a proper tailored IR byte code is generated for the query using the utility GsCodeGen object and standard LLVM JIT API (IRBuilder). After byte-code generation is completed, the code is JIT-compiled into a separate LLVM module. The compiled code results in a C function pointer that can later be invoked for direct execution. Note that this C function can be invoked concurrently by many threads, as long as each thread provides a distinct execution context (details are provided below). Each such execution context is referred to as *JIT Context*.
+
+To improve performance further, MOT JIT applies a caching policy for its LLVM code results, enabling them to be reused for the same queries across different sessions.
+
+## Execute
+
+When an EXECUTE command is issued, the prepared statement (described above) is planned and executed. This division of labor avoids repetitive parse analysis work, while enabling the execution plan to depend on the specific setting values supplied.
+
+When the resulting execute query command reaches the database, it uses the corresponding IR byte code which is executed directly and more efficiently within the MOT engine. This is referred to as *Lite Execution*.
+
+In addition, for availability, the Lite Executor maintains a preallocated pool of JIT sources. Each session preallocates its own session-local pool of JIT context objects (used for repeated executions of precompiled queries).
+
+For more details you may refer to the Supported Queries for Lite Execution and Unsupported Queries for Lite Execution sections.
+
+## JIT Compilation Comparison - MogDB Disk-based vs. MOT Tables
+
+Currently, MogDB contains two main forms of JIT / CodeGen query optimizations for its disk-based tables -
+
+- Accelerating expression evaluation, such as in WHERE clauses, target lists, aggregates and projections.
+- Inlining small function invocations.
+
+These optimizations are partial (in the sense they do not optimize the entire interpreted operator tree or replace it altogether) and are targeted mostly at CPU-bound complex queries, typically seen in OLAP use cases. The execution of queries is performed in a pull-model (Volcano-style processing) using an interpreted operator tree. When activated, the compilation is performed at each query execution. At the moment, caching of the generated LLVM code and its reuse across sessions and queries is not yet provided.
+
+In contrast, MOT JIT optimization provides LLVM code for entire queries that qualify for JIT optimization by MOT. The resulting code is used for direct execution over MOT tables, while the interpreted operator model is abandoned completely. The result is *practically* handwritten LLVM code that has been generated for an entire specific query execution.
+
+Another significant conceptual difference is that MOT LLVM code is only generated for prepared queries during the PREPARE phase of the query, rather than at query execution. This is especially important for OLTP scenarios due to the rather short runtime of OLTP queries, which cannot allow for code generation and relatively long query compilation time to be performed during each query execution.
+
+Finally, in PostgreSQL the activation of a PREPARE implies the reuse of the resulting plan across executions with different parameters in the same session. Similarly, the MOT JIT applies a caching policy for its LLVM code results, and extends it for reuse across different sessions. Thus, a single query may be compiled just once and its LLVM code may be reused across many sessions, which again is beneficial for OLTP scenarios.
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-9.md b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-9.md
new file mode 100644
index 0000000000000000000000000000000000000000..6aac4a5c5884d754728cbc0b9b253ee0aeae0d2e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-9.md
@@ -0,0 +1,69 @@
+---
+title: Comparison - Disk vs. MOT
+summary: Comparison - Disk vs. MOT
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# Comparison - Disk vs. MOT
+
+The following table briefly compares the various features of the MogDB disk-based storage engine and the MOT storage engine.
+
+**Table 1** Comparison - Disk-based vs. MOT
+
+| Feature                      | MogDB Disk Store    | MogDB MOT Engine              |
+| :--------------------------- | :------------------ | :---------------------------- |
+| Intel x86 + Kunpeng ARM      | Yes                 | Yes                           |
+| SQL and Feature-set Coverage | 100%                | 98%                           |
+| Scale-up (Many-cores, NUMA)  | Low Efficiency      | High Efficiency               |
+| Throughput                   | High                | Extremely High                |
+| Latency                      | Low                 | Extremely Low                 |
+| Distributed (Cluster Mode)   | Yes                 | Yes                           |
+| Isolation Levels             | RC+SIRRSerializable | RCRRRC+SI (in V2 release)     |
+| Concurrency Control          | Pessimistic         | Optimistic                    |
+| Data Capacity (Data + Index) | Unlimited           | Limited to DRAM               |
+| Native Compilation           | No                  | Yes                           |
+| Replication, Recovery        | Yes                 | Yes                           |
+| Replication Options          | 2 (sync, async)     | 3 (sync, async, group-commit) |
+
+**Legend -**
+
+- RR = Repeatable Reads
+- RC = Read Committed
+- SI = Snapshot Isolation
+
+## Appendices
+
+## References
+
+[1] Y. Mao, E. Kohler, and R. T. Morris. Cache craftiness for fast multicore key-value storage. In Proc. 7th ACM European Conference on Computer Systems (EuroSys), Apr. 2012.
+
+[2] K. Ren, T. Diamond, D. J. Abadi, and A. Thomson. Low-overhead asynchronous checkpointing in main-memory database systems. In Proceedings of the 2016 ACM SIGMOD International Conference on Management of Data, 2016.
+
+[3] <https://e.huawei.com/en/products/servers/taishan-server/taishan-2280-v2>.
+
+[4] <https://e.huawei.com/en/products/servers/taishan-server/taishan-2480-v2>.
+
+[5] Tu, S., Zheng, W., Kohler, E., Liskov, B., and Madden, S. Speedy transactions in multicore in-memory databases. In Proceedings of the Twenty-Fourth ACM Symposium on Operating Systems Principles (New York, NY, USA, 2013), SOSP ’13, ACM, pp. 18-32.
+
+[6] H. Avni at al. Industrial-Strength OLTP Using Main Memory and Many-cores, VLDB 2020.
+
+[7] Bernstein, P. A., and Goodman, N. Concurrency control in distributed database systems. ACM Comput. Surv. 13, 2 (1981), 185-221.
+
+[8] Felber, P., Fetzer, C., and Riegel, T. Dynamic performance tuning of word-based software transactional memory. In Proceedings of the 13th ACM SIGPLAN Symposium on Principles and Practice of Parallel Programming, PPOPP 2008, Salt Lake City, UT, USA, February 20-23, 2008 (2008),
+
+pp. 237-246.
+
+[9] Appuswamy, R., Anadiotis, A., Porobic, D., Iman, M., and Ailamaki, A. Analyzing the impact of system architecture on the scalability of OLTP engines for high-contention workloads. PVLDB 11, 2 (2017),
+
+121-134.
+
+[10] R. Sherkat, C. Florendo, M. Andrei, R. Blanco, A. Dragusanu, A. Pathak, P. Khadilkar, N. Kulkarni, C. Lemke, S. Seifert, S. Iyer, S. Gottapu, R. Schulze, C. Gottipati, N. Basak, Y. Wang, V. Kandiyanallur, S. Pendap, D. Gala, R. Almeida, and P. Ghosh. Native store extension for SAP HANA. PVLDB, 12(12):
+
+2047-2058, 2019.
+
+[11] X. Yu, A. Pavlo, D. Sanchez, and S. Devadas. Tictoc: Time traveling optimistic concurrency control. In Proceedings of the 2016 International Conference on Management of Data, SIGMOD Conference 2016, San Francisco, CA, USA, June 26 - July 01, 2016, pages 1629-1642, 2016.
+
+[12] V. Leis, A. Kemper, and T. Neumann. The adaptive radix tree: Artful indexing for main-memory databases. In C. S. Jensen, C. M. Jermaine, and X. Zhou, editors, 29th IEEE International Conference on Data Engineering, ICDE 2013, Brisbane, Australia, April 8-12, 2013, pages 38-49. IEEE Computer Society, 2013.
+
+[13] S. K. Cha, S. Hwang, K. Kim, and K. Kwon. Cache-conscious concurrency control of main-memory indexes on shared-memory multiprocessor systems. In P. M. G. Apers, P. Atzeni, S. Ceri, S. Paraboschi, K. Ramamohanarao, and R. T. Snodgrass, editors, VLDB 2001, Proceedings of 27th International Conference on Very Large Data Bases, September 11-14, 2001, Roma, Italy, pages 181-190. Morga Kaufmann, 2001.
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/4-appendix/1-references.md b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/4-appendix/1-references.md
new file mode 100644
index 0000000000000000000000000000000000000000..4055b8f1162ff4f4b79927bdb5d3fcb2172f3c85
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/4-appendix/1-references.md
@@ -0,0 +1,40 @@
+---
+title: References
+summary: References
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# References
+
+[1] Y. Mao, E. Kohler, and R. T. Morris. Cache craftiness for fast multicore key-value storage. In Proc. 7th ACM European Conference on Computer Systems (EuroSys), Apr. 2012.
+
+[2] K. Ren, T. Diamond, D. J. Abadi, and A. Thomson. Low-overhead asynchronous checkpointing in main-memory database systems. In Proceedings of the 2016 ACM SIGMOD International Conference on Management of Data, 2016.
+
+[3] <https://e.huawei.com/en/products/servers/taishan-server/taishan-2280-v2>.
+
+[4] <https://e.huawei.com/en/products/servers/taishan-server/taishan-2480-v2>.
+
+[5] Tu, S., Zheng, W., Kohler, E., Liskov, B., and Madden, S. Speedy transactions in multicore in-memory databases. In Proceedings of the Twenty-Fourth ACM Symposium on Operating Systems Principles (New York, NY, USA, 2013), SOSP ’13, ACM, pp. 18-32.
+
+[6] H. Avni at al. Industrial-Strength OLTP Using Main Memory and Many-cores, VLDB 2020.
+
+[7] Bernstein, P. A., and Goodman, N. Concurrency control in distributed database systems. ACM Comput. Surv. 13, 2 (1981), 185-221.
+
+[8] Felber, P., Fetzer, C., and Riegel, T. Dynamic performance tuning of word-based software transactional memory. In Proceedings of the 13th ACM SIGPLAN Symposium on Principles and Practice of Parallel Programming, PPOPP 2008, Salt Lake City, UT, USA, February 20-23, 2008 (2008),
+
+pp. 237-246.
+
+[9] Appuswamy, R., Anadiotis, A., Porobic, D., Iman, M., and Ailamaki, A. Analyzing the impact of system architecture on the scalability of OLTP engines for high-contention workloads. PVLDB 11, 2 (2017),
+
+121-134.
+
+[10] R. Sherkat, C. Florendo, M. Andrei, R. Blanco, A. Dragusanu, A. Pathak, P. Khadilkar, N. Kulkarni, C. Lemke, S. Seifert, S. Iyer, S. Gottapu, R. Schulze, C. Gottipati, N. Basak, Y. Wang, V. Kandiyanallur, S. Pendap, D. Gala, R. Almeida, and P. Ghosh. Native store extension for SAP HANA. PVLDB, 12(12):
+
+2047-2058, 2019.
+
+[11] X. Yu, A. Pavlo, D. Sanchez, and S. Devadas. Tictoc: Time traveling optimistic concurrency control. In Proceedings of the 2016 International Conference on Management of Data, SIGMOD Conference 2016, San Francisco, CA, USA, June 26 - July 01, 2016, pages 1629-1642, 2016.
+
+[12] V. Leis, A. Kemper, and T. Neumann. The adaptive radix tree: Artful indexing for main-memory databases. In C. S. Jensen, C. M. Jermaine, and X. Zhou, editors, 29th IEEE International Conference on Data Engineering, ICDE 2013, Brisbane, Australia, April 8-12, 2013, pages 38-49. IEEE Computer Society, 2013.
+
+[13] S. K. Cha, S. Hwang, K. Kim, and K. Kwon. Cache-conscious concurrency control of main-memory indexes on shared-memory multiprocessor systems. In P. M. G. Apers, P. Atzeni, S. Ceri, S. Paraboschi, K. Ramamohanarao, and R. T. Snodgrass, editors, VLDB 2001, Proceedings of 27th International Conference on Very Large Data Bases, September 11-14, 2001, Roma, Italy, pages 181-190. Morga Kaufmann, 2001.
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/4-appendix/2-glossary.md b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/4-appendix/2-glossary.md
new file mode 100644
index 0000000000000000000000000000000000000000..f2d1576038d266439c9d9238fcf119133a52ce34
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/mot-engine/4-appendix/2-glossary.md
@@ -0,0 +1,59 @@
+---
+title: Glossary
+summary: Glossary
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# Glossary
+
+| Acronym | Definition/Description                                       |
+| :------ | :----------------------------------------------------------- |
+| 2PL     | 2-Phase Locking                                              |
+| ACID    | Atomicity, Consistency, Isolation, Durability                |
+| AP      | Analytical Processing                                        |
+| ARM     | Advanced RISC Machine, a hardware architecture alternative to x86 |
+| CC      | Concurrency Control                                          |
+| CPU     | Central Processing Unit                                      |
+| DB      | Database                                                     |
+| DBA     | Database Administrator                                       |
+| DBMS    | Database Management System                                   |
+| DDL     | Data Definition Language. Database Schema management language |
+| DML     | Data Modification Language                                   |
+| ETL     | Extract, Transform, Load or Encounter Time Locking           |
+| FDW     | Foreign Data Wrapper                                         |
+| GC      | Garbage Collector                                            |
+| HA      | High Availability                                            |
+| HTAP    | Hybrid Transactional-Analytical Processing                   |
+| IoT     | Internet of Things                                           |
+| IM      | In-Memory                                                    |
+| IMDB    | In-Memory Database                                           |
+| IR      | Intermediate Representation of a source code, used in compilation and optimization |
+| JIT     | Just In Time                                                 |
+| JSON    | JavaScript Object Notation                                   |
+| KV      | Key Value                                                    |
+| LLVM    | Low-Level Virtual Machine, refers to a compilation code or queries to IR |
+| M2M     | Machine-to-Machine                                           |
+| ML      | Machine Learning                                             |
+| MM      | Main Memory                                                  |
+| MO      | Memory Optimized                                             |
+| MOT     | Memory Optimized Tables storage engine (SE), pronounced as /em/ /oh/ /tee/ |
+| MVCC    | Multi-Version Concurrency Control                            |
+| NUMA    | Non-Uniform Memory Access                                    |
+| OCC     | Optimistic Concurrency Control                               |
+| OLTP    | Online Transaction Processing                                |
+| PG      | PostgreSQL                                                   |
+| RAW     | Reads-After-Writes                                           |
+| RC      | Return Code                                                  |
+| RTO     | Recovery Time Objective                                      |
+| SE      | Storage Engine                                               |
+| SQL     | Structured Query Language                                    |
+| TCO     | Total Cost of Ownership                                      |
+| TP      | Transactional Processing                                     |
+| TPC-C   | An On-Line Transaction Processing Benchmark                  |
+| Tpm-C   | Transactions-per-minute-C. A performance metric for TPC-C benchmark that counts new-order transactions. |
+| TVM     | Tiny Virtual Machine                                         |
+| TSO     | Time Sharing Option                                          |
+| UDT     | User-Defined Type                                            |
+| WAL     | Write Ahead Log                                              |
+| XLOG    | A PostgreSQL implementation of transaction logging (WAL - described above) |
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/primary-and-standby-management.md b/product/en/docs-mogdb/v3.0/administrator-guide/primary-and-standby-management.md
new file mode 100644
index 0000000000000000000000000000000000000000..b4db2942936e716277a950a4dd71d2f395faac75
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/primary-and-standby-management.md
@@ -0,0 +1,126 @@
+---
+title: Primary and Standby Management
+summary: Primary and Standby Management
+author: Guo Huan
+date: 2021-03-11
+---
+
+# Primary and Standby Management
+
+## Scenarios
+
+During MogDB database running, the database administrator needs to manually perform an primary/standby switchover on the database node. For example, after a primary/standby database node failover, you need to restore the original primary/standby roles, or you need to manually perform a primary/standby switchover due to a hardware fault. A cascaded standby server cannot be directly switched to a primary server. You must perform a switchover or failover to change the cascaded standby server to a standby server, and then to a primary server.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - The primary/standby switchover is a maintenance operation. Ensure that the MogDB database is normal and perform the switchover after all services are complete.
+> - When the ultimate RTO is enabled, cascaded standby servers are not supported. The standby server cannot be connected when the ultimate RTO is enabled. As a result, the cascaded standby server cannot synchronize data.
+
+## Procedure
+
+1. Log in to any database node as the OS user **omm** and run the following command to check the primary/standby status:
+
+   ```bash
+   gs_om -t status --detail
+   ```
+
+2. Log in to the standby node to be switched to the primary node as the OS user **omm** and run the following command:
+
+   ```bash
+   gs_ctl switchover -D /home/omm/cluster/dn1/
+   ```
+
+   **/home/omm/cluster/dn1/** is the data directory of the standby database node.
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** For the same database, you cannot perform a new primary/standby switchover if the previous switchover has not completed. If a switchover is performed when the host thread is processing services, the thread cannot stop, and switchover timeout will be reported. Actually, the switchover is ongoing in the background and will complete after the thread finishes service processing and stops. For example, when a host is deleting a large partitioned table, it may fail to respond to the switchover request.
+
+3. After the switchover is successful, run the following command to record the information about the current primary and standby nodes:
+
+   ```bash
+   gs_om -t refreshconf
+   ```
+
+## Examples
+
+Run the following command to switch the standby database instance to the primary database instance:
+
+1. Queries database status.
+
+   ```bash
+   $ gs_om -t status --detail
+   [   Cluster State   ]
+
+   cluster_state   : Normal
+   redistributing  : No
+   current_az      : AZ_ALL
+
+   [  Datanode State   ]
+
+       node             node_ip         port      instance                            state
+   --------------------------------------------------------------------------------------------------
+   1  pekpopgsci00235  10.244.62.204    5432      6001 /home/omm/cluster/dn1/   P Primary Normal
+   2  pekpopgsci00238  10.244.61.81     5432      6002 /home/omm/cluster/dn1/   S Standby Normal
+   ```
+
+2. Log in to the standby node and perform a primary/standby switchover. In addition, after a cascaded standby node is switched over, the cascaded standby server becomes a standby server, and the original standby server becomes a cascaded standby server.
+
+   ```bash
+   $ gs_ctl switchover -D /home/omm/cluster/dn1/
+   [2020-06-17 14:28:01.730][24438][][gs_ctl]: gs_ctl switchover ,datadir is -D "/home/omm/cluster/dn1"
+   [2020-06-17 14:28:01.730][24438][][gs_ctl]: switchover term (1)
+   [2020-06-17 14:28:01.768][24438][][gs_ctl]: waiting for server to switchover............
+   [2020-06-17 14:28:11.175][24438][][gs_ctl]: done
+   [2020-06-17 14:28:11.175][24438][][gs_ctl]: switchover completed (/home/omm/cluster/dn1)
+   ```
+
+3. Save the information about the primary and standby nodes in the database.
+
+   ```bash
+   $ gs_om -t refreshconf
+   Generating dynamic configuration file for all nodes.
+   Successfully generated dynamic configuration file.
+   ```
+
+## Troubleshooting
+
+If a switchover fails, troubleshoot the problem according to the log information. For details, see [Log Reference](11-log-reference).
+
+## Exception Handling
+
+Exception handling rules are as follows:
+
+- A switchover takes a long time under high service loads. In this case, no further operation is required.
+
+- When standby nodes are being built, a primary node can be demoted to a standby node only after sending logs to one of the standby nodes. As a result, the primary/standby switchover takes a long time. In this case, no further operation is required. However, you are not advised to perform a primary/standby switchover during the build process.
+
+- During a switchover, due to network faults and high disk usage, it is possible that the primary and standby instances are disconnected, or two primary nodes exist in a single pair. In this case, perform the following steps:
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-warning.gif) **WARNING:** After two primary nodes appear, perform the following steps to restore the normal primary/standby state: Otherwise, data loss may occur.
+
+1. Run the following commands to query the current instance status of the database:
+
+   ```bash
+   gs_om -t status --detail
+   ```
+
+   The query result shows that the status of two instances is **Primary**, which is abnormal.
+
+2. Determine the node that functions as the standby node and run the following command on the node to stop the service:
+
+   ```bash
+   gs_ctl stop -D /home/omm/cluster/dn1/
+   ```
+
+3. Run the following command to start the standby node in standby mode:
+
+   ```bash
+   gs_ctl start -D /home/omm/cluster/dn1/ -M standby
+   ```
+
+4. Save the information about the primary and standby nodes in the database.
+
+   ```bash
+   gs_om -t refreshconf
+   ```
+
+5. Check the database status and ensure that the instance status is restored.
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/0-starting-and-stopping-mogdb.md b/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/0-starting-and-stopping-mogdb.md
new file mode 100644
index 0000000000000000000000000000000000000000..f3119e28321f8ee75f64a8e35624acb8479d0841
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/0-starting-and-stopping-mogdb.md
@@ -0,0 +1,65 @@
+---
+title: Starting and Stopping MogDB
+summary: Starting and Stopping MogDB
+author: Guo Huan
+date: 2021-06-24
+---
+
+# Starting and Stopping MogDB
+
+## Starting MogDB
+
+1. Log in as the OS user **omm** to the primary node of the database.
+
+2. Run the following command to start MogDB:
+
+   ```bash
+   gs_om -t start
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** An HA cluster must be started in HA mode. If the cluster is started in standalone mode, you need to restore the HA relationship by running the **gs_ctl build** command. For details about how to use the **gs_ctl** tool, see [gs_ctl](4-gs_ctl).
+
+## Stopping MogDB
+
+1. Log in as the OS user **omm** to the primary node of the database.
+
+2. Run the following command to stop MogDB:
+
+   ```bash
+   gs_om -t stop
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** For details about how to start and stop nodes and availability zones (AZs), see [gs_om](8-gs_om).
+
+## Examples
+
+Start MogDB:
+
+```bash
+gs_om -t start
+Starting cluster.
+=========================================
+=========================================
+Successfully started.
+```
+
+Stop MogDB:
+
+```bash
+gs_om -t stop
+Stopping cluster.
+=========================================
+Successfully stopped cluster.
+=========================================
+End stop cluster.
+```
+
+## Troubleshooting
+
+If starting or stopping MogDB fails, troubleshoot the problem based on log information. For details, see [Log Reference](11-log-reference).
+
+If the startup fails due to timeout, you can run the following command to set the startup timeout interval, which is 300s by default:
+
+```bash
+gs_om -t start --time-out=300
+```
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/1-routine-maintenance-check-items.md b/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/1-routine-maintenance-check-items.md
new file mode 100644
index 0000000000000000000000000000000000000000..dd068915ad840f3d7216da7eaa0f437b646888d7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/1-routine-maintenance-check-items.md
@@ -0,0 +1,165 @@
+---
+title: 日常运维
+summary: 日常运维
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# Routine Maintenance Check Items
+
+## Checking MogDB Status
+
+MogDB provides tools to check database and instance status, ensuring that databases and instances are running properly to provide data services.
+
+- Check instance status.
+
+  ```bash
+  gs_check -U omm -i CheckClusterState
+  ```
+
+- Check parameters.
+
+  ```sql
+  mogdb=# SHOW parameter_name;
+  ```
+
+  In the above command, **parameter_name** needs to be replaced with a specific parameter name.
+- Modify parameters.
+
+  ```bash
+  gs_guc reload  -D /mogdb/data/dbnode -c "paraname=value"
+  ```
+
+## Checking Lock Information
+
+The lock mechanism is an important method to ensure data consistency. Information check helps learn database transactions and database running status.
+
+- Query lock information in the database.
+
+  ```sql
+  mogdb=# SELECT * FROM pg_locks;
+  ```
+
+- Query the status of threads waiting to acquire locks.
+
+  ```sql
+  mogdb=# SELECT * FROM pg_thread_wait_status WHERE wait_status = 'acquire lock';
+  ```
+
+- Kill a system process.
+
+  Search for a system process that is running and run the following command to end the process:
+
+  ```
+  ps ux
+  kill -9 pid
+  ```
+
+## Collecting Event Statistics
+
+Long-time running of SQL statements will occupy a lot of system resources. You can check event occurrence time and occupied memory to learn about database running status.
+
+- Query the time points about an event.
+
+  Run the following command to query the thread start time, transaction start time, SQL start time, and status change time of the event:
+
+  ```sql
+  mogdb=# SELECT backend_start,xact_start,query_start,state_change FROM pg_stat_activity;
+  ```
+
+- Query the number of sessions on the current server.
+
+  ```sql
+  mogdb=# SELECT count(*) FROM pg_stat_activity;
+  ```
+
+- Collect system-level statistics.
+
+  Run the following command to query information about the session that uses the maximum memory:
+
+  ```sql
+  mogdb=# SELECT * FROM pv_session_memory_detail() ORDER BY usedsize desc limit 10;
+  ```
+
+## Checking Objects
+
+Tables, indexes, partitions, and constraints are key storage objects of a database. A database administrator needs to routinely maintain key information and these objects.
+
+- View table details.
+
+  ```sql
+  mogdb=# \d+ table_name
+  ```
+
+- Query table statistics.
+
+  ```sql
+  mogdb=# SELECT * FROM pg_statistic;
+  ```
+
+- View index details.
+
+  ```sql
+  mogdb=# \d+ index_name
+  ```
+
+- Query partitioned table information.
+
+  ```sql
+  mogdb=# SELECT * FROM pg_partition;
+  ```
+
+- Collect statistics.
+
+  Run the **ANALYZE** statement to collect related statistics on the database.
+
+  Run the **VACUUM** statement to reclaim space and update statistics.
+
+- Query constraint information.
+
+  ```sql
+  mogdb=# SELECT * FROM pg_constraint;
+  ```
+
+## Checking an SQL Report
+
+Run the **EXPLAIN** statement to view execution plans.
+
+## Backing Up Data
+
+Never forget to back up data. During the routine work, the backup execution and backup data validity need to be checked to ensure data security and encryption security.
+
+- Export a specified user.
+
+  ```bash
+  gs_dump dbname -p port -f out.sql -U user_name -W password
+  ```
+
+- Export a schema.
+
+  ```bash
+  gs_dump dbname -p port -n schema_name -f out.sql
+  ```
+
+- Export a table.
+
+  ```bash
+  gs_dump dbname -p port -t table_name -f out.sql
+  ```
+
+## Checking Basic Information
+
+Basic information includes versions, components, and patches. Periodic database information checks and records are important for database life cycle management.
+
+- Check version information.
+
+  ```sql
+  mogdb=# SELECT version();
+  ```
+
+- Check table size and database size.
+
+  ```sql
+  mogdb=# SELECT pg_table_size('table_name');
+  mogdb=# SELECT pg_database_size('database_name');
+  ```
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/10-data-security-maintenance-suggestions.md b/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/10-data-security-maintenance-suggestions.md
new file mode 100644
index 0000000000000000000000000000000000000000..210a1641747139b252c816d9c04e17b3bf2c5472
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/10-data-security-maintenance-suggestions.md
@@ -0,0 +1,29 @@
+---
+title: 日常运维
+summary: 日常运维
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# Data Security Maintenance Suggestions
+
+To ensure data security in MogDB Kernel and prevent accidents, such as data loss and illegal data access, read this section carefully.
+
+**Preventing Data Loss**
+
+You are advised to plan routine physical backup and store backup files in a reliable medium. If a serious error occurs in the system, you can use the backup files to restore the system to the state at the backup point.
+
+**Preventing Illegal Data Access**
+
+- You are advised to manage database users based on their permission hierarchies. A database administrator creates users and grants permissions to the users based on service requirements to ensure users properly access the database.
+- You are advised to deploy MogDB Kernel servers and clients (or applications developed based on the client library) in trusted internal networks. If the servers and clients must be deployed in an untrusted network, enable SSL encryption before services are started to ensure data transmission security. Note that enabling the SSL encryption function compromises database performance.
+
+**Preventing System Logs from Leaking Personal Data**
+
+- Delete personal data before sending debug logs to others for analysis.
+
+   **NOTE:** The log level **log_min_messages** is set to **DEBUG**x (*x* indicates the debug level and the value ranges from 1 to 5). The information recorded in debug logs may contain personal data.
+
+- Delete personal data before sending system logs to others for analysis. If the execution of a SQL statement fails, the error SQL statement will be recorded in a system log by default. SQL statements may contain personal data.
+
+- Set **log_min_error_statement** to **PANIC** to prevent error SQL statements from being recorded in system logs. However, once the function is disabled, it is difficult to locate fault causes if faults occur.
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/11-log-reference.md b/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/11-log-reference.md
new file mode 100644
index 0000000000000000000000000000000000000000..8ed5bd8cb699791e23428997bf3aa4087c236cd5
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/11-log-reference.md
@@ -0,0 +1,137 @@
+---
+title: Log Reference
+summary: Log Reference
+author: Guo Huan
+date: 2021-06-24
+---
+
+# Log Reference
+
+## Log Overview
+
+During database running, a large number of logs are generated, including write-ahead logs (WALs, also called Xlogs) for ensuring database security and reliability and run logs and operation logs for daily database maintenance. If the database is faulty, you can refer to these logs to locate the fault and restore the database.
+
+**Log Type**
+
+The following table describes details about log types.
+
+**Table 1** Log types
+
+| Type            | Description                                                  |
+| :-------------- | :----------------------------------------------------------- |
+| System log      | Logs generated during database running. They are used to record abnormal process information. |
+| Operation log   | Logs generated when a client tool (such as **gs_guc**) is operating databases. |
+| Trace log       | Logs generated after the database debug switch is enabled. They are used to analyze database exceptions. |
+| Black box log   | Logs generated when the database system breaks down. You can analyze the process context when the fault occurs based on the heap and stack information in the logs to facilitate fault locating. A black box dumps stack, heap, and register information about processes and threads when a system breaks down. |
+| Audit log       | Logs used to record some of the database user operations after the database audit function is enabled. |
+| WAL             | Logs used to restore a damaged database. They are also called redo logs. You are advised to routinely back up WALs. |
+| Performance log | Logs used to record the status of physical resources and the performance of access to external resources (such as disks, OBS and Hadoop clusters). |
+
+## System Logs
+
+System logs include those generated by database nodes when MogDB is running, and those generated when MogDB is deployed. If an error occurs during MogDB running, you can locate the cause and troubleshoot it based on system logs.
+
+**Log Storage Directory**
+
+Run logs of database nodes are stored in the corresponding folders in the **/var/log/mogdb/username/pg_log** directory.
+
+Logs generated during OM MogDB installation and uninstallation are stored in the **/var/log/mogdb/username/om** directory.
+
+**Log Naming Rules**
+
+The name format of database node run logs is:
+
+**postgresql-creation time.log**
+
+By default, a new log file is generated at 0:00 every day, or when the latest log file exceeds 16 MB or a database instance (database node) is restarted.
+
+**Log Content Description**
+
+Content of a line in a database node log:
+
+Date+Time+Time zone+Username+Database name+Session ID+Log level+Log content
+
+## Operation Logs
+
+Operation logs are generated when database tools are used by a database administrator or invoked by a cluster. If the cluster is faulty, you can backtrack user operations on the database and reproduce the fault based on the operation logs.
+
+**Log Storage Directory**
+
+The default path is **\$GAUSSLOG/bin**. If the environmental variable **$GAUSSLOG** does not exist or its value is empty, the log information generated for a tool will be displayed, but not recorded in the log file of the tool.
+
+The default value of **$GAUSSLOG** is **/var/log/mogdb/username**.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** If a database is deployed using the OM script, the log path is **/var/log/mogdb/username**.
+
+**Log Naming Rules**
+
+The log file name format is as follows:
+
+- **tool name-log creation time.log**
+- **tool name-log creation time-current.log**
+
+**tool name-log creation time.log** is a historical log file, and **tool name-log creation time-current.log** is a current log file.
+
+If the size of a log file exceeds 16 MB, the next time the tool is invoked, the log file is renamed in the historical log file name format, and a new log file is generated at the current time point.
+
+For example, **gs_guc-2015-01-16_183728-current.log** is renamed as **gs_guc-2015-01-16_183728.log**, and **gs_guc-2015-01-17_142216-current.log** is generated.
+
+**Maintenance Suggestions**
+
+You are advised to dump expired logs periodically to save disk space and prevent important logs from being lost.
+
+## Audit Logs
+
+After the audit function is enabled, a large number of audit logs will be generated, which occupy large storage space. You can customize an audit log maintenance policy based on the size of available storage space.
+
+For details, see "Database Security Management > Configuring Database Audit > Maintaining Audit Logs" in the *Developer Guide*.
+
+## WALs
+
+In a system using write-ahead logs (WALs or Xlogs), all data file modifications are written to a log before they are applied. That is, the corresponding log must be written into a permanent memory before a data file is modified. You can use WALs to restore the cluster if the system crashes.
+
+**Log Storage Directory**
+
+Take a DN as an example. Its WALs are stored in the **/mogdb/data/data_dn/pg_xlog** directory.
+
+**/mogdb/data/data_dn** is the data directory of a node in the cluster.
+
+**Log Naming Rules**
+
+Log files are saved as segment files. Each segment is 16 MB and is divided into multiple 8 KB pages. The name of a WAL file consists of 24 hexadecimal characters. Each name has three parts, with each part having eight hexadecimal characters. The first part indicates the time line, the second part indicates the log file identifier, and the third part indicates the file segment identifier. A time line starts from 1, and a log file identifier and a file segment identifier start from 0.
+
+For example, the name of the first transaction log is **000000010000000000000000**.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The numbers in each part are used in ascending order in succession. Exhausting all available numbers takes a long time, and the numbers will start from zero again after they reach the maximum.
+
+**Log Content Description**
+
+The content of WALs depends on the types of recorded transactions. WALs can be used to restore a system after the system breaks down.
+
+By default, MogDB Kernal reads WALs for system restoration during each startup.
+
+**Maintenance Suggestions**
+
+WALs are important for database restoration. You are advised to routinely back up WALs.
+
+## Performance Logs
+
+Performance logs focus on the access performance of external resources. Performance logs are used to record the status of physical resources and the performance of access to external resources (such as disks, OBS and Hadoop clusters). When a performance issue occurs, you can locate the cause using performance logs, which greatly improves troubleshooting efficiency.
+
+**Log Storage Directory**
+
+The performance logs of database are stored in the directories under **$GAUSSLOG/gs_profile**.
+
+**Log Naming Rules**
+
+The name format ofdatabase performance logs is:
+
+**postgresql-creation time.prf**
+
+By default, a new log file is generated at 0:00 every day, or when the latest log file exceeds 20 MB or a database instance (CN or DN) is restarted.
+
+**Log Content Description**
+
+Content of a line in a database log:
+
+**Host name+Date+Time+Instance name+Thread number+Log content**
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/2-checking-os-parameters.md b/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/2-checking-os-parameters.md
new file mode 100644
index 0000000000000000000000000000000000000000..29132b31d7177ad64fc80925c402ca0bf0f9a511
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/2-checking-os-parameters.md
@@ -0,0 +1,178 @@
+---
+title: 日常运维
+summary: 日常运维
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# Checking OS Parameters
+
+## Check Method
+
+Use the **gs_checkos** tool provided by MogDB to check the OS status.
+
+**Prerequisites**
+
+- The hardware and network are working properly.
+- The trust relationship of user **root** among the hosts is normal.
+- Only user **root** is authorized to run the **gs_checkos** command.
+
+**Procedure**
+
+1. Log in to a server as user **root**.
+
+2. Run the following command to check OS parameters of servers where the MogDB nodes are deployed:
+
+   ```
+   gs_checkos -i A
+   ```
+
+   Check the OS parameters to ensure that MogDB has passed the pre-installation check and can efficiently operate after it is installed.
+
+**Examples**
+
+Before running the **gs_checkos** command, execute pre-processing scripts by running **gs_preinstall** to prepare the environment. The following uses parameter **A** as an example:
+
+```
+gs_checkos -i A
+Checking items:
+    A1. [ OS version status ]                                   : Normal
+    A2. [ Kernel version status ]                               : Normal
+    A3. [ Unicode status ]                                      : Normal
+    A4. [ Time zone status ]                                    : Normal
+    A5. [ Swap memory status ]                                  : Normal
+    A6. [ System control parameters status ]                    : Normal
+    A7. [ File system configuration status ]                    : Normal
+    A8. [ Disk configuration status ]                           : Normal
+    A9. [ Pre-read block size status ]                          : Normal
+    A10.[ IO scheduler status ]                                 : Normal
+    A11.[ Network card configuration status ]                   : Normal
+    A12.[ Time consistency status ]                             : Warning
+    A13.[ Firewall service status ]                             : Normal
+    A14.[ THP service status ]                                  : Normal
+Total numbers:14. Abnormal numbers:0. Warning number:1.
+```
+
+The following uses parameter **B** as an example:
+
+```
+gs_checkos -i B
+Setting items:
+    B1. [ Set system control parameters ]                       : Normal
+    B2. [ Set file system configuration value ]                 : Normal
+    B3. [ Set pre-read block size value ]                       : Normal
+    B4. [ Set IO scheduler value ]                              : Normal
+    B5. [ Set network card configuration value ]                : Normal
+    B6. [ Set THP service ]                                     : Normal
+    B7. [ Set RemoveIPC value ]                                 : Normal
+    B8. [ Set Session Process ]                                 : Normal
+Total numbers:6. Abnormal numbers:0. Warning number:0.
+```
+
+## Exception Handling
+
+If you use the **gs_checkos** tool to check the OS and the command output shows **Abnormal**, run the following command to view detailed error information:
+
+```
+gs_checkos -i A --detail
+```
+
+The **Abnormal** state cannot be ignored because the OS in this state affects cluster installation. The **Warning** state does not affect cluster installation and thereby can be ignored.
+
+- If the check result for OS version status (**A1**) is **Abnormal**, replace OSs out of the mixed programming scope with those within the scope.
+
+- If the check result for kernel version status (**A2**) is **Warning**, the platform kernel versions in the cluster are inconsistent.
+
+- If the check result for Unicode status (**A3**) is **Abnormal**, set the same character set for all the hosts. You can add **export LANG=***unicode* to the **/etc/profile** file.
+
+  ```
+  vim /etc/profile
+  ```
+
+- If the check result for time zone status (**A4**) is **Abnormal**, set the same time zone for all the hosts. You can copy the time zone file in the **/usr/share/zoneinfo/** directory as the **/etc/localtime** file.
+
+  ```
+  cp /usr/share/zoneinfo/$primary time zone/$secondary time zone /etc/localtime
+  ```
+
+- If the check result for swap memory status (**A5**) is **Abnormal**, a possible cause is that the swap memory is larger than the physical memory. You can troubleshoot this issue by reducing the swap memory or increasing the physical memory.
+
+- If the check result for system control parameter status (**A6**) is **Abnormal**, troubleshoot this issue in either of the following two ways:
+
+  - Run the following command:
+
+    ```
+    gs_checkos -i B1
+    ```
+
+  - Modify the **/etc/sysctl.conf** file based on the error message and run **sysctl -p** to make it take effect.
+
+    ```
+    vim /etc/sysctl.conf
+    ```
+
+- If the check result for file system configuration status (**A7**) is **Abnormal**, run the following command to troubleshoot this issue:
+
+  ```
+  gs_checkos -i B2
+  ```
+
+- If the check result for disk configuration status (**A8**) is **Abnormal**, set the disk mounting format to **rw,noatime,inode64,allocsize=16m**.
+
+  Run the **man mount** command to mount the XFS parameter:
+
+  ```
+  rw,noatime,inode64,allocsize=16m
+  ```
+
+  You can also set the XFS parameter in the **/etc/fstab** file. For example:
+
+  ```
+  /dev/data /data xfs rw,noatime,inode64,allocsize=16m 0 0
+  ```
+
+- If the check result for pre-read block size status (**A9**) is **Abnormal**, run the following command to troubleshoot this issue:
+
+  ```
+  gs_checkos -i B3
+  ```
+
+- If the check result for I/O scheduling status (**A10**) is **Abnormal**, run the following command to troubleshoot this issue:
+
+  ```
+  gs_checkos -i B4
+  ```
+
+- If the check result for NIC configuration status (**A11**) is **Warning**, run the following command to troubleshoot this issue:
+
+  ```
+  gs_checkos -i B5
+  ```
+
+- If the check result for time consistency status (**A12**) is **Abnormal**, verify that the NTP service has been installed and started and has synchronized time from the NTP clock.
+
+- If the check result for firewall status (**A13**) is **Abnormal**, disable the firewall. Run the following commands:
+
+  - SUSE:
+
+    ```
+    SuSEfirewall2 stop
+    ```
+
+  - RedHat7:
+
+    ```
+    systemctl disable firewalld
+    ```
+
+  - RedHat6:
+
+    ```
+    service iptables stop
+    ```
+
+- If the check result for THP service status (**A14**) is **Abnormal**, run the following command to troubleshoot this issue:
+
+  ```
+  gs_checkos -i B6
+  ```
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/3-checking-mogdb-health-status.md b/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/3-checking-mogdb-health-status.md
new file mode 100644
index 0000000000000000000000000000000000000000..a9195068419d5e15303786dd892327848ac2eb98
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/3-checking-mogdb-health-status.md
@@ -0,0 +1,645 @@
+---
+title: Checking MogDB Health Status
+summary: Checking MogDB Health Status
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# Checking MogDB Health Status
+
+## Check Method
+
+Use the **gs_check** tool provided by MogDB to check the MogDB health status.
+
+**Precautions**
+
+- Only user **root** is authorized to check new nodes added during cluster scale-out. In other cases, the check can be performed only by user **omm**.
+- Parameter **-i** or **-e** must be set. **-i** specifies a single item to be checked, and **-e** specifies an inspection scenario where multiple items will be checked.
+- If **-i** is not set to a **root** item or no such items are contained in the check item list of the scenario specified by **-e**, you do not need to enter the name or password of user **root**.
+- You can run **-skip-root-items** to skip **root** items.
+- Check the consistency between the new node and existing nodes. Run the **gs_check** command on an existing node and specify the **-hosts** parameter. The IP address of the new node needs to be written into the **hosts** file.
+
+**Procedure**
+
+Method 1:
+
+1. Log in as the OS user **omm** to the primary node of the database.
+
+2. Run the following command to check the MogDB database status:
+
+   ```bash
+   gs_check -i CheckClusterState
+   ```
+
+   In the command, **-i** indicates the check item and is case-sensitive. The format is **-i CheckClusterState**, **-i CheckCPU** or **-i CheckClusterState,CheckCPU**.
+
+   Checkable items are listed in "Table 1 MogDB status checklist" in "Tool Reference > Server Tools > [gs_check](1-gs_check)". You can create a check item as needed.
+
+Method 2:
+
+1. Log in as the OS user **omm** to the primary node of the database.
+
+2. Run the following command to check the MogDB database health status:
+
+   ```bash
+   gs_check -e inspect
+   ```
+
+   In the command, **-e** indicates the inspection scenario and is case-sensitive. The format is **-e inspect** or **-e upgrade**.
+
+   The inspection scenarios include **inspect** (routine inspection), **upgrade** (inspection before upgrade), **Install** (install inspection ), **binary_upgrade** (inspection before in-place upgrade), **slow_node** (node inspection), **longtime** (time-consuming inspection) and **health** (health inspection). You can create an inspection scenario as needed.
+
+The MogDB inspection is performed to check MogDB status during MogDB running or to check the environment and conditions before critical operations, such as upgrade or scale-out. For details about the inspection items and scenarios, see "Server Tools > gs_check > MogDB status checks" in the *MogDB Tool Reference*.
+
+**Examples**
+
+Check result of a single item:
+
+```bash
+perfadm@lfgp000700749:/opt/huawei/perfadm/tool/script> gs_check -i CheckCPU
+Parsing the check items config file successfully
+Distribute the context file to remote hosts successfully
+Start to health check for the cluster. Total Items:1 Nodes:3
+
+Checking...               [=========================] 1/1
+Start to analysis the check result
+CheckCPU....................................OK
+The item run on 3 nodes.  success: 3
+
+Analysis the check result successfully
+Success. All check items run completed. Total:1  Success:1  Failed:0
+For more information please refer to /opt/mogdb/tools/script/gspylib/inspection/output/CheckReport_201902193704661604.tar.gz
+```
+
+Local execution result:
+
+```bash
+perfadm@lfgp000700749:/opt/huawei/perfadm/tool/script> gs_check -i CheckCPU -L
+
+2017-12-29 17:09:29 [NAM] CheckCPU
+2017-12-29 17:09:29 [STD] Check the CPU usage of the host. If the value of idle is greater than 30% and the value of iowait is less than 30%, this item passes the check. Otherwise, this item fails the check.
+2017-12-29 17:09:29 [RST] OK
+
+2017-12-29 17:09:29 [RAW]
+Linux 4.4.21-69-default (lfgp000700749)  12/29/17  _x86_64_
+
+17:09:24        CPU     %user     %nice   %system   %iowait    %steal     %idle
+17:09:25        all      0.25      0.00      0.25      0.00      0.00     99.50
+17:09:26        all      0.25      0.00      0.13      0.00      0.00     99.62
+17:09:27        all      0.25      0.00      0.25      0.13      0.00     99.37
+17:09:28        all      0.38      0.00      0.25      0.00      0.13     99.25
+17:09:29        all      1.00      0.00      0.88      0.00      0.00     98.12
+Average:        all      0.43      0.00      0.35      0.03      0.03     99.17
+```
+
+Check result of a scenario:
+
+```bash
+[perfadm@SIA1000131072 Check]$ gs_check -e inspect
+Parsing the check items config file successfully
+The below items require root privileges to execute:[CheckBlockdev CheckIOrequestqueue CheckIOConfigure CheckCheckMultiQueue CheckFirewall CheckSshdService CheckSshdConfig CheckCrondService CheckBootItems CheckFilehandle CheckNICModel CheckDropCache]
+Please enter root privileges user[root]:root
+Please enter password for user[root]:
+Please enter password for user[root] on the node[10.244.57.240]:
+Check root password connection successfully
+Distribute the context file to remote hosts successfully
+Start to health check for the cluster. Total Items:57 Nodes:2
+
+Checking...               [                         ] 21/57
+Checking...               [=========================] 57/57
+Start to analysis the check result
+CheckClusterState...........................OK
+The item run on 2 nodes.  success: 2
+
+CheckDBParams...............................OK
+The item run on 1 nodes.  success: 1
+
+CheckDebugSwitch............................OK
+The item run on 2 nodes.  success: 2
+
+CheckDirPermissions.........................OK
+The item run on 2 nodes.  success: 2
+
+CheckReadonlyMode...........................OK
+The item run on 1 nodes.  success: 1
+
+CheckEnvProfile.............................OK
+The item run on 2 nodes.  success: 2  (consistent)
+The success on all nodes value:
+GAUSSHOME        /usr1/mogdb/app
+LD_LIBRARY_PATH  /usr1/mogdb/app/lib
+PATH             /usr1/mogdb/app/bin
+
+
+CheckBlockdev...............................OK
+The item run on 2 nodes.  success: 2
+
+CheckCurConnCount...........................OK
+The item run on 1 nodes.  success: 1
+
+CheckCursorNum..............................OK
+The item run on 1 nodes.  success: 1
+
+CheckPgxcgroup..............................OK
+The item run on 1 nodes.  success: 1
+
+CheckDiskFormat.............................OK
+The item run on 2 nodes.  success: 2
+
+CheckSpaceUsage.............................OK
+The item run on 2 nodes.  success: 2
+
+CheckInodeUsage.............................OK
+The item run on 2 nodes.  success: 2
+
+CheckSwapMemory.............................OK
+The item run on 2 nodes.  success: 2
+
+CheckLogicalBlock...........................OK
+The item run on 2 nodes.  success: 2
+
+CheckIOrequestqueue.....................WARNING
+The item run on 2 nodes.  warning: 2
+The warning[host240,host157] value:
+On device (vdb) 'IO Request' RealValue '256' ExpectedValue '32768'
+On device (vda) 'IO Request' RealValue '256' ExpectedValue '32768'
+
+CheckMaxAsyIOrequests.......................OK
+The item run on 2 nodes.  success: 2
+
+CheckIOConfigure............................OK
+The item run on 2 nodes.  success: 2
+
+CheckMTU....................................OK
+The item run on 2 nodes.  success: 2  (consistent)
+The success on all nodes value:
+1500
+
+CheckPing...................................OK
+The item run on 2 nodes.  success: 2
+
+CheckRXTX...................................NG
+The item run on 2 nodes.  ng: 2
+The ng[host240,host157] value:
+NetWork[eth0]
+RX: 256
+TX: 256
+
+
+CheckNetWorkDrop............................OK
+The item run on 2 nodes.  success: 2
+
+CheckMultiQueue.............................OK
+The item run on 2 nodes.  success: 2
+
+CheckEncoding...............................OK
+The item run on 2 nodes.  success: 2  (consistent)
+The success on all nodes value:
+LANG=en_US.UTF-8
+
+CheckFirewall...............................OK
+The item run on 2 nodes.  success: 2
+
+CheckKernelVer..............................OK
+The item run on 2 nodes.  success: 2  (consistent)
+The success on all nodes value:
+3.10.0-957.el7.x86_64
+
+CheckMaxHandle..............................OK
+The item run on 2 nodes.  success: 2
+
+CheckNTPD...................................OK
+host240: NTPD service is running, 2020-06-02 17:00:28
+host157: NTPD service is running, 2020-06-02 17:00:06
+
+
+CheckOSVer..................................OK
+host240: The current OS is centos 7.6 64bit.
+host157: The current OS is centos 7.6 64bit.
+
+CheckSysParams..........................WARNING
+The item run on 2 nodes.  warning: 2
+The warning[host240,host157] value:
+Warning reason: variable 'net.ipv4.tcp_retries1' RealValue '3' ExpectedValue '5'.
+Warning reason: variable 'net.ipv4.tcp_syn_retries' RealValue '6' ExpectedValue '5'.
+
+CheckTHP....................................OK
+The item run on 2 nodes.  success: 2
+
+CheckTimeZone...............................OK
+The item run on 2 nodes.  success: 2  (consistent)
+The success on all nodes value:
++0800
+
+CheckCPU....................................OK
+The item run on 2 nodes.  success: 2
+
+CheckSshdService............................OK
+The item run on 2 nodes.  success: 2
+
+Warning reason: UseDNS parameter is not set; expected: no
+
+CheckCrondService...........................OK
+The item run on 2 nodes.  success: 2
+
+CheckStack..................................OK
+The item run on 2 nodes.  success: 2  (consistent)
+The success on all nodes value:
+8192
+
+CheckSysPortRange...........................OK
+The item run on 2 nodes.  success: 2
+
+CheckMemInfo................................OK
+The item run on 2 nodes.  success: 2  (consistent)
+The success on all nodes value:
+totalMem: 31.260929107666016G
+
+CheckHyperThread............................OK
+The item run on 2 nodes.  success: 2
+
+CheckTableSpace.............................OK
+The item run on 1 nodes.  success: 1
+
+CheckSysadminUser...........................OK
+The item run on 1 nodes.  success: 1
+
+
+CheckGUCConsistent..........................OK
+All DN instance guc value is consistent.
+
+CheckMaxProcMemory..........................OK
+The item run on 1 nodes.  success: 1
+
+CheckBootItems..............................OK
+The item run on 2 nodes.  success: 2
+
+CheckHashIndex..............................OK
+The item run on 1 nodes.  success: 1
+
+CheckPgxcRedistb............................OK
+The item run on 1 nodes.  success: 1
+
+CheckNodeGroupName..........................OK
+The item run on 1 nodes.  success: 1
+
+CheckTDDate.................................OK
+The item run on 1 nodes.  success: 1
+
+CheckDilateSysTab...........................OK
+The item run on 1 nodes.  success: 1
+
+CheckKeyProAdj..............................OK
+The item run on 2 nodes.  success: 2
+
+CheckProStartTime.......................WARNING
+host157:
+STARTED COMMAND
+Tue Jun  2 16:57:18 2020 /usr1/dmuser/dmserver/metricdb1/server/bin/mogdb --single_node -D /usr1/dmuser/dmb1/data -p 22204
+Mon Jun  1 16:15:15 2020 /usr1/mogdb/app/bin/mogdb -D /usr1/mogdb/data/dn1 -M standby
+
+
+CheckFilehandle.............................OK
+The item run on 2 nodes.  success: 2
+
+CheckRouting................................OK
+The item run on 2 nodes.  success: 2
+
+CheckNICModel...............................OK
+The item run on 2 nodes.  success: 2  (consistent)
+The success on all nodes value:
+version: 1.0.1
+model: Red Hat, Inc. Virtio network device
+
+
+CheckDropCache..........................WARNING
+The item run on 2 nodes.  warning: 2
+The warning[host240,host157] value:
+No DropCache process is running
+
+CheckMpprcFile..............................NG
+The item run on 2 nodes.  ng: 2
+The ng[host240,host157] value:
+There is no mpprc file
+
+Analysis the check result successfully
+Failed. All check items run completed. Total:57   Success:50   Warning:5   NG:2
+For more information please refer to /usr1/mogdb/tool/script/gspylib/inspection/output/CheckReport_inspect611.tar.gz
+```
+
+## Exception Handling
+
+Troubleshoot exceptions detected in the inspection by following instructions in this section.
+
+**Table 1** Check of MogDB running status
+
+<table>
+    <tr>
+        <td>Check Item    </td>
+        <td>  Abnormal Status  </td>
+        <td> Solution   </td>
+     </tr>
+    <tr>
+        <td rowspan="2"> CheckClusterState (Checks the MogDB status.)   </td>
+        <td>  MogDB or MogDB instances are not started.  </td>
+        <td>  Run the following command to start MogDB and instances:<br /><br />gs_om -t start  </td>
+     </tr>
+    <tr>
+        <td> The status of MogDB or MogDB instances is abnormal.  </td>
+        <td>  Check the status of hosts and instances. Troubleshoot this issue based on the status information.<br />gs_check -i CheckClusterState </td>
+     </tr>
+    <tr>
+        <td>  CheckDBParams (Checks database parameters.)  </td>
+        <td>  Database parameters have incorrect values.  </td>
+        <td>   Use the <b>gs_guc</b> tool to set the parameters to specified values. </td>
+     </tr>
+    <tr>
+        <td>  CheckDebugSwitch (Checks debug logs.)  </td>
+        <td>  The log level is incorrect. </td>
+        <td>  Use the <b>gs_guc</b> tool to set <b>log_min_messages</b> to specified content.  </td>
+     </tr>
+    <tr>
+        <td>  CheckDirPermissions (Checks directory permissions.)  </td>
+        <td>  The permission for a directory is incorrect.  </td>
+        <td>   Change the directory permission to a specified value (<b>750</b> or <b>700</b>).<br />chmod 750 DIR </td>
+     </tr>
+    <tr>
+        <td>  CheckReadonlyMode (Checks the read-only mode.)  </td>
+        <td>  The read-only mode is enabled.  </td>
+        <td> Verify that the usage of the disk where database nodes are located does not exceed the threshold (60% by default) and no other O&M operations are performed.<br />gs_check -i CheckDataDiskUsage ps ux<br />Use the <b>gs_guc</b> tool to disable the read-only mode of MogDB.<br />gs_guc reload -N all -I all -c 'default_transaction_read_only = off'     </td>
+     </tr>
+    <tr>
+        <td> CheckEnvProfile (Checks environment variables.)   </td>
+        <td>  Environment variables are inconsistent. </td>
+        <td> Update the environment variable information.   </td>
+     </tr>
+    <tr>
+        <td>  CheckBlockdev (Checks pre-read blocks.)  </td>
+        <td> The size of a pre-read block is not 16384 KB.  </td>
+        <td> Use the <b>gs_checkos</b> tool to set the size of the pre-read block to 16384 KB and write the setting into the auto-startup file.<br />gs_checkos -i B3  </td>
+     </tr>
+    <tr>
+        <td> CheckCursorNum (Checks the number of cursors.)   </td>
+        <td>   The number of cursors fails to be checked. </td>
+        <td>  Check whether the database is properly connected and whether the MogDB status is normal.  </td>
+     </tr>
+    <tr>
+        <td>  CheckPgxcgroup (Checks the data redistribution status.) </td>
+        <td>  There are <b>pgxc_group</b> tables that have not been redistributed.  </td>
+        <td>  Proceed with the redistribution.<br />gs_expand、gs_shrink </td>
+     </tr>
+    <tr>
+        <td> CheckDiskFormat (Checks disk configurations.)  </td>
+        <td>  Disk configurations are inconsistent between nodes. </td>
+        <td>  Configure disk specifications to be consistent between nodes.  </td>
+     </tr>
+    <tr>
+        <td> CheckSpaceUsage (Checks the disk space usage.)  </td>
+        <td>  Disk space is insufficient. </td>
+        <td> Clear or expand the disk for the directory.  </td>
+     </tr>
+    <tr>
+        <td>   CheckInodeUsage (Checks the disk index usage.) </td>
+        <td>  Disk indexes are insufficient.  </td>
+        <td>  Clear or expand the disk for the directory.  </td>
+     </tr>
+    <tr>
+        <td>  CheckSwapMemory (Checks the swap memory.)  </td>
+        <td>  The swap memory is greater than the physical memory.  </td>
+        <td>  Reduce or disable the swap memory.  </td>
+     </tr>
+    <tr>
+        <td>  CheckLogicalBlock (Checks logical blocks.)  </td>
+        <td> The size of a logical block is not 512 KB. </td>
+        <td>  Use the <b>gs_checkos</b> tool to set the size of the logical block to 512 KB and write the setting into the auto-startup file.<br />gs_checkos -i B4  </td>
+     </tr>
+    <tr>
+        <td>  CheckIOrequestqueue (Checks I/O requests.) </td>
+        <td>  The requested I/O is not <b>32768</b>. </td>
+        <td>  Use the <b>gs_checkos</b> tool to set the requested I/O to <b>32768</b> and write the setting into the auto-startup file.<br />gs_checkos -i B4  </td>
+     </tr>
+    <tr>
+        <td> CheckCurConnCount (Checks the number of current connections.)  </td>
+        <td>  The number of current connections exceeds 90% of the allowed maximum number of connections. </td>
+        <td>  Break idle primary database node connections.  </td>
+     </tr>
+    <tr>
+        <td>  CheckMaxAsyIOrequests (Checks the maximum number of asynchronous requests.)  </td>
+        <td>  The maximum number of asynchronous requests is less than 104857600 or (Number of database instances on the current node x 1048576). </td>
+        <td>  Use the <b>gs_checkos</b> tool to set the maximum number of asynchronous requests to the larger one between 104857600 and (Number of database instances on the current node x 1048576).<br />gs_checkos -i B4  </td>
+     </tr>
+    <tr>
+        <td> CheckMTU (Checks MTU values.)  </td>
+        <td>  MTU values are inconsistent between nodes.  </td>
+        <td> Set the MTU value on each node to <b>1500</b> or <b>8192</b>.<br />ifconfig eth* MTU 1500  </td>
+     </tr>
+      <tr>
+        <td> CheckIOConfigure (Checks I/O configurations.) </td>
+          <td>  The I/O mode is not <b>deadline</b>.  </td>
+          <td>   Use the <b>gs_checkos</b> tool to set the I/O mode to <b>deadline</b> and write the setting into the auto-startup file.<br />gs_checkos -i B4 </td>
+     </tr>
+      <tr>
+        <td>   CheckRXTX (Checks the RX/TX value.) </td>
+          <td>  The NIC RX/TX value is not <b>4096</b>.  </td>
+          <td>  Use the <b>checkos</b> tool to set the NIC RX/TX value to <b>4096</b> for MogDB.<br />gs_checkos -i B5  </td>
+     </tr>
+      <tr>
+        <td>   CheckPing (Checks whether the network connection is normal.) </td>
+        <td>    There are MogDB IP addresses that cannot be pinged.</td>
+        <td>  Check the network settings, network status, and firewall status between the abnormal IP addresses.  </td>
+     </tr>
+      <tr>
+        <td> CheckNetWorkDrop (Checks the network packet loss rate.)  </td>
+        <td>The network packet loss rate is greater than 1%.  </td>
+        <td>  Check the network load and status between the corresponding IP addresses.  </td>
+     </tr>
+      <tr>
+        <td> CheckMultiQueue (Checks the NIC multi-queue function.)  </td>
+        <td>   Multiqueue is not enabled for the NIC, and NIC interruptions are not bound to different CPU cores. </td>
+        <td>  Enable multiqueue for the NIC, and bind NIC interruptions to different CPU cores. </td>
+     </tr>
+      <tr>
+        <td>  CheckEncoding (Checks the encoding format.)  </td>
+        <td>  Encoding formats are inconsistent between nodes.  </td>
+          <td>  Write the same encoding format into <b>/etc/profile</b> for each node.<br />echo "export LANG=XXX" >> /etc/profile  </td>
+     </tr>
+      <tr>
+        <td>  CheckActQryCount (Checks the archiving mode.)  </td>
+        <td>  The archiving mode is enabled, and the archiving directory is not under the primary database node directory.  </td>
+        <td>    Disable archiving mode or set the archiving directory to be under the primary database node directory.</td>
+     </tr>
+      <tr>
+        <td>  CheckFirewall (Checks the firewall.)  </td>
+        <td>  The firewall is enabled. </td>
+        <td>  Disable the firewall.<br />systemctl disable firewalld.service   </td>
+     </tr>
+      <tr>
+        <td>  CheckKernelVer (Checks kernel versions.)  </td>
+        <td> Kernel versions are inconsistent between nodes.  </td>
+        <td>    </td>
+     </tr>
+      <tr>
+        <td>  CheckMaxHandle (Checks the maximum number of file handles.) </td>
+        <td>  The maximum number of handles is less than 1000000. </td>
+          <td>  Set the soft and hard limits in the <b>91-nofile.conf</b> or <b>90-nofile.conf</b> file to <b>1000000</b>.<br />gs_checkos -i B2  </td>
+     </tr>
+      <tr>
+        <td>  CheckNTPD (Checks the time synchronization service.)  </td>
+        <td>  The NTPD service is disabled or the time difference is greater than 1 minute.  </td>
+        <td>   Enable the NTPD service and set the time to be consistent. </td>
+     </tr>
+      <tr>
+        <td>  CheckSysParams (Checks OS parameters.) </td>
+        <td>  OS parameter settings do not meet requirements.  </td>
+          <td>  Use the <b>gs_checkos</b> tool or manually set parameters to values meeting requirements.<br />gs_checkos -i B1 vim /etc/sysctl.conf  </td>
+     </tr>
+      <tr>
+        <td>   CheckTHP (Checks the THP service.) </td>
+        <td>  The THP service is disabled.  </td>
+          <td>   Use the <b>gs_checkos</b> to enable the THP service.<br />gs_checkos -i B6</td>
+     </tr>
+      <tr>
+        <td>  CheckTimeZone (Checks time zones.) </td>
+        <td> Time zones are inconsistent between nodes.  </td>
+        <td>  Set time zones to be consistent between nodes.<br />cp /usr/share/zoneinfo/\$primary time zone/$secondary time zone\ /etc/localtime  </td>
+     </tr>
+      <tr>
+        <td>   CheckCPU (Checks the CPU.) </td>
+        <td>   CPU usage is high or I/O waiting time is too long. </td>
+        <td>   Upgrade CPUs or improve disk performance. </td>
+     </tr>
+      <tr>
+        <td>  CheckSshdService (Checks the SSHD service.)  </td>
+        <td> The SSHD service is disabled.  </td>
+        <td>  Enable the SSHD service and write the setting into the auto-startup file.<br />service sshd start echo "server sshd start" >> initFile  </td>
+     </tr>
+      <tr>
+        <td>CheckSshdConfig (Checks SSHD configurations.)   </td>
+        <td>  The SSHD service is incorrectly configured.  </td>
+        <td> Reconfigure the SSHD service.<br />PasswordAuthentication=no; MaxStartups=1000; UseDNS=yes; ClientAliveInterval=10800/ClientAliveInterval=0<br />Restart the service.<br />server sshd start   </td>
+     </tr>
+      <tr>
+        <td>  CheckCrondService (Checks the Crond service.)  </td>
+        <td> The Crond service is disabled.   </td>
+        <td>  Install and enable the Crond service.  </td>
+     </tr>
+      <tr>
+        <td>   CheckStack (Checks the stack size.) </td>
+        <td>   The stack size is less than 3072. </td>
+          <td>   Use the <b>gs_checkos</b> tool to set the stack size to <b>3072</b> and restart the processes with a smaller stack size.<br /> gs_checkos -i B2 </td>
+     </tr>
+      <tr>
+        <td>   CheckSysPortRange (Checks OS port configurations.) </td>
+        <td>  OS IP ports are not within the required port range or MogDB ports are within the OS IP port range.  </td>
+          <td>  Set the OS IP ports within <b>26000</b> to <b>65535</b> and set the MogDB ports beyond the OS IP port range.<br />vim /etc/sysctl.conf  </td>
+     </tr>
+      <tr>
+        <td>  CheckMemInfo (Checks the memory information.)  </td>
+        <td>  Memory sizes are inconsistent between nodes.  </td>
+        <td>  Use physical memory of the same specifications between nodes.  </td>
+     </tr>
+      <tr>
+        <td>  CheckHyperThread (Checks the hyper-threading.)  </td>
+        <td>  The CPU hyper-threading is disabled.  </td>
+        <td>  Enable the CPU hyper-threading.  </td>
+     </tr>
+      <tr>
+        <td> CheckTableSpace (Checks tablespaces.)   </td>
+        <td>  The tablespace path is nested with the MogDB path or nested with the path of another tablespace.  </td>
+        <td>  Migrate tablespace data to the tablespace with a valid path.  </td>
+     </tr>
+</table>
+
+## Querying Status
+
+### Background
+
+MogDB allows you to view the status of the entire MogDB. The query result shows whether the database or a single host is running properly.
+
+### Prerequisites
+
+The database has started.
+
+### Procedure
+
+1. Log in as the OS user **omm** to the primary node of the database.
+
+2. Run the following command to query the database status:
+
+   ```bash
+   $ gs_om -t status --detail
+   ```
+
+   Table 1 describes parameters in the query result.
+
+   To query the instance status on a host, add **-h** to the command. For example:
+
+   ```bash
+   $ gs_om -t status -h plat2
+   ```
+
+   **plat2** indicates the name of the host to be queried.
+
+### Parameter Description
+
+**Table 1** Node role description
+
+| Field         | Description                                                  | Value                                                        |
+| :------------ | :----------------------------------------------------------- | :----------------------------------------------------------- |
+| cluster_state | The database status, which indicates whether the entire database is running properly. | **Normal**: The database is available and the data has redundancy backup. All the processes are running and the primary/standby relationship is normal.**Unavailable**: The database is unavailable.**Degraded**: The database is available and faulty database nodes and primary database nodes exist. |
+| node          | Host name.                                                   | Specifies the name of the host where the instance is located. If multiple AZs exist, the AZ IDs will be displayed. |
+| node_ip       | Host IP Address.                                             | Specifies the IP address of the host where the instance is located. |
+| instance      | Instance ID.                                                 | Specifies the instance ID.                                   |
+| state         | Instance role                                                | **Normal**: a single host instance.**Primary**: The instance is a primary instance.**Standby**: The instance is a standby instance.**Cascade Standby**: The instance is a cascaded standby instance.**Secondary**: The instance is a secondary instance.**Pending**: The instance is in the quorum phase.**Unknown**: The instance status is unknown.**Down**: The instance is down.**Abnormal**: The node is abnormal.**Manually stopped**: The node has been manually stopped. |
+
+Each role has different states, such as startup and connection. The states are described as follows:
+
+**Table 2** Node state description
+
+| State          | Description                                                  |
+| :------------- | :----------------------------------------------------------- |
+| Normal         | The node starts up normally.                                 |
+| Need repair    | The node needs to be restored.                               |
+| Starting       | The node is starting up.                                     |
+| Wait promoting | The node is waiting for upgrade. For example, after the standby node sends an upgrade request to the primary node, the standby node is waiting for the response from the primary node. |
+| Promoting      | The standby node is being upgraded to the primary node.      |
+| Demoting       | The node is being downgraded, for example, the primary node is being downgraded to the standby node. |
+| Building       | The standby node fails to be started and needs to be rebuilt. |
+| Catchup        | The standby node is catching up with the primary node.       |
+| Coredump       | The node program breaks down.                                |
+| Unknown        | The node status is unknown.                                  |
+
+If a node is in **Need repair** state, you need to rebuild the node to restore it. Generally, the reasons for rebuilding a node are as follows:
+
+**Table 3** Node rebuilding causes
+
+| State                 | Description                                                  |
+| :-------------------- | :----------------------------------------------------------- |
+| Normal                | The node starts up normally.                                 |
+| WAL segment removed   | WALs of the primary node do not exist, and logs of the standby node are later than those of the primary node. |
+| Disconnect            | Standby node cannot be connected to the primary node.        |
+| Version not matched   | The binary versions of the primary and standby nodes are inconsistent. |
+| Mode not matched      | Nodes do not match the primary and standby roles. For example, two standby nodes are connected. |
+| System id not matched | The database system IDs of the primary and standby nodes are inconsistent. The system IDs of the primary and standby nodes must be the same. |
+| Timeline not matched  | The log timelines are inconsistent.                          |
+| Unknown               | Unknown cause.                                               |
+
+## Examples
+
+View the database status details, including instance status.
+
+```bash
+$ gs_om -t status --detail
+[   Cluster State   ]
+
+cluster_state   : Normal
+redistributing  : No
+current_az      : AZ_ALL
+
+[  Datanode State   ]
+
+    node             node_ip         port      instance                                   state
+-----------------------------------------------------------------------------------------------------
+1  pekpopgsci00235  10.244.62.204    5432      6001 /opt/mogdb/cluster/data/dn1   P Primary Normal
+2  pekpopgsci00238  10.244.61.81     5432      6002 /opt/mogdb/cluster/data/dn1   S Standby Normal
+```
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/4-checking-database-performance.md b/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/4-checking-database-performance.md
new file mode 100644
index 0000000000000000000000000000000000000000..716235a4f6ecfa79477eb0bc7bfb364be6feed21
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/4-checking-database-performance.md
@@ -0,0 +1,83 @@
+---
+title: 日常运维
+summary: 日常运维
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# Checking Database Performance
+
+## Check Method
+
+Use the **gs_checkperf** tool provided by MogDB to check hardware performance.
+
+**Prerequisites**
+
+- MogDB is running properly.
+- Services are running properly on the database.
+
+**Procedure**
+
+1. Log in as the OS user **omm** to the primary node of the database.
+
+2. Run the following command to check the MogDB database performance:
+
+   ```
+   gs_checkperf
+   ```
+
+For details about performance statistical items, see "Table 1 Performance check items" in "Tool Reference > Server Tools > [gs_checkperf](3-gs_checkperf)".
+
+**Examples**
+
+Simple performance statistical result is displayed on the screen as follows:
+
+```
+gs_checkperf -i pmk -U omm
+Cluster statistics information:
+    Host CPU busy time ratio                     :    1.43       %
+    MPPDB CPU time % in busy time                :    1.88       %
+    Shared Buffer Hit ratio                      :    99.96      %
+    In-memory sort ratio                         :    100.00     %
+    Physical Reads                               :    4
+    Physical Writes                              :    25
+    DB size                                      :    70         MB
+    Total Physical writes                        :    25
+    Active SQL count                             :    2
+    Session count                                :    3
+```
+
+## Exception Handling
+
+After you use the **gs_checkperf** tool to check the cluster performance, if the performance is abnormal, troubleshoot the issue by following instructions in this section.
+
+**Table 1** Cluster-level performance status
+
+| Abnormal Status                    | Solution                                                     |
+| ---------------------------------- | ------------------------------------------------------------ |
+| High CPU usage of hosts            | 1. Add high-performance CPUs, or replace current CPUs with them.2. Run the **top** command to check which system processes cause high CPU usage, and run the **kill** command to stop unused processes.<br />`top` |
+| High CPU usage of MogDB Kernel     | 1. Add high-performance CPUs, or replace current CPUs with them.<br />2. Run the **top** command to check which database processes cause high CPU usage, and run the **kill** command to stop unused processes.<br />`top`<br />3. Use the **gs_expand** tool to add new hosts to lower the CPU usage. |
+| Low hit ratio of the shared memory | 1. Expand the memory.<br />2. Run the following command to check the OS configuration file **/etc/sysctl.conf** and increase the value of **kernel.shmmax**.<br />`vim /etc/sysctl.conf` |
+| Low in-memory sort ratio           | Expand the memory.                                           |
+| High I/O and disk usage            | 1. Replace current disks with high-performance ones.<br />2. Adjust the data layout to evenly distribute I/O requests to all the physical disks.<br />3. Run **VACUUM FULL** for the entire database.<br />`vacuum full;`<br />4. Clean up the disk space.<br />5. Reduce the number of concurrent connections. |
+| Transaction statistics             | Query the **pg_stat_activity** system catalog and disconnect unnecessary connections. (Log in to the database and run the **mogdb=# \d+ pg_stat_activity;** command.) |
+
+**Table 2** Node-level performance status
+
+| Abnormal Status   | Solution                                                     |
+| ----------------- | ------------------------------------------------------------ |
+| High CPU usage    | 1. Add high-performance CPUs, or replace current CPUs with them.<br />2. Run the **top** command to check which system processes cause high CPU usage, and run the **kill** command to stop unused processes.<br />`top` |
+| High memory usage | Expand or clean up the memory.                               |
+| High I/O usage    | 1. Replace current disks with high-performance ones.<br />2. Clean up the disk space.<br />3. Use memory read/write to replace as much disk I/O as possible, putting frequently accessed files or data in the memory. |
+
+**Table 3** Session/process-level performance status
+
+| Abnormal Status                 | Solution                                                     |
+| ------------------------------- | ------------------------------------------------------------ |
+| High CPU, memory, and I/O usage | Check which processes cause high CPU, memory, or I/O usage. If they are unnecessary processes, kill them; otherwise, analyze the specific cause of high usage. For example, if SQL statement execution occupies much memory, check whether the SQL statements need optimization. |
+
+**Table 4** SSD performance status
+
+| Abnormal Status      | Solution                                                     |
+| -------------------- | ------------------------------------------------------------ |
+| SSD read/write fault | Run the following command to check whether SSD is faulty. If yes, analyze the specific cause.<br />`gs_checkperf -i SSD -U omm` |
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/5-checking-and-deleting-logs.md b/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/5-checking-and-deleting-logs.md
new file mode 100644
index 0000000000000000000000000000000000000000..92358a20f3da94e394a7aa98ac21cd2daf2bb51d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/5-checking-and-deleting-logs.md
@@ -0,0 +1,160 @@
+---
+title: Checking and Deleting Logs
+summary: Checking and Deleting Logs
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# Checking and Deleting Logs
+
+You are advised to check OS logs and database run logs monthly for monitoring system status and troubleshooting, and to delete database run logs monthly for saving disk space.
+
+## Checking OS Logs
+
+You are advised to monthly check OS logs to detect and prevent potential OS problems.
+
+**Procedure**
+
+Run the following command to check OS log files:
+
+```
+vim /var/log/messages
+```
+
+(Pay attention to words like **kernel**, **error**, and **fatal** in logs generated within the last month and handle the problems based on the alarm information.)
+
+## Checking MogDB Run Logs
+
+A database can still run when errors occur during the execution of some operations. However, data may be inconsistent before and after the error occurrences. Therefore, you are advised to monthly check MogDB run logs to detect potential problems in time.
+
+**Prerequisites**
+
+- The host used for collecting logs is running properly, and the network connection is normal. Database installation users trust each other.
+- An OS tool (for example, **gstack**) that the log collection tool requires has been installed. If it is not installed, an error message is displayed, and this collection item is skipped.
+
+**Procedure**
+
+1. Log in as the OS user **omm** to the primary node of the database.
+
+2. Run the following command to collect database logs:<a id="2"> </a>
+
+   ```
+   gs_collector --begin-time="20160616 01:01" --end-time="20160616 23:59"
+   ```
+
+   In the command, **20160616 01:01** indicates the start time of the log and **20160616 23:59** indicates the end time of the log.
+
+3. Based on command output in [2](#2), access the related log collection directory, decompress collected database logs, and check these logs.
+
+   Assume that collected logs are stored in **/opt/mogdb/tmp/gaussdba_mppdb/collector_20160726_105158.tar.gz**.
+
+   ```
+   tar -xvzf /opt/mogdb/tmp/gaussdba_mppdb/collector_20160726_105158.tar.gz
+   cd /opt/mogdb/tmp/gaussdba_mppdb/collector_20160726_105158
+   ```
+
+**Examples**
+
+- Run the **gs_collector** command together with parameters **-begin-time** and **-end-time**:
+
+  ```bash
+  gs_collector --begin-time="20160616 01:01" --end-time="20160616 23:59"
+  ```
+
+  If information similar to the following is displayed, the logs have been archived:
+
+  ```
+  Successfully collected  files
+  All results are stored in /tmp/gaussdba_mppdb/collector_20160616_175615.tar.gz.
+  ```
+
+- Run the **gs_collector** command together with parameters **-begin-time**, **-end-time**, and **-h**:
+
+  ```bash
+  gs_collector --begin-time="20160616 01:01" --end-time="20160616 23:59" -h plat2
+  ```
+
+  If information similar to the following is displayed, the logs have been archived:
+
+  ```
+  Successfully collected  files
+  All results are stored in /tmp/gaussdba_mppdb/collector_20160616_190225.tar.gz.
+  ```
+
+- Run the **gs_collector** command together with parameters **-begin-time**, **-end-time**, and **-f**:
+
+  ```bash
+  gs_collector --begin-time="20160616 01:01" --end-time="20160616 23:59" -f /opt/software/mogdb/output
+  ```
+
+  If information similar to the following is displayed, the logs have been archived:
+
+  ```
+  Successfully collected  files
+  All results are stored in /opt/software/mogdb/output/collector_20160616_190511.tar.gz.
+  ```
+
+- Run the **gs_collector** command together with parameters **-begin-time**, **-end-time**, and **-keyword**:
+
+  ```bash
+  gs_collector --begin-time="20160616 01:01" --end-time="20160616 23:59" --keyword="os"
+  ```
+
+  If information similar to the following is displayed, the logs have been archived:
+
+  ```
+  Successfully collected files.
+  All results are stored in /tmp/gaussdba_mppdb/collector_20160616_190836.tar.gz.
+  ```
+
+- Run the **gs_collector** command together with parameters **-begin-time**, **-end-time**, and **-o**:
+
+  ```bash
+  gs_collector --begin-time="20160616 01:01" --end-time="20160616 23:59" -o /opt/software/mogdb/output
+  ```
+
+  If information similar to the following is displayed, the logs have been archived:
+
+  ```
+  Successfully collected files.
+  All results are stored in /opt/software/mogdb/output/collector_20160726_113711.tar.gz.
+  ```
+
+- Run the **gs_collector** command together with parameters **-begin-time**, **-end-time**, and **-l** (the file name extension must be .log):
+
+  ```bash
+  gs_collector --begin-time="20160616 01:01" --end-time="20160616 23:59" -l /opt/software/mogdb/logfile.log
+  ```
+
+  If information similar to the following is displayed, the logs have been archived:
+
+  ```
+  Successfully collected files.
+  All results are stored in /opt/software/mogdb/output/collector_20160726_113711.tar.gz.
+  ```
+
+## Cleaning Run Logs
+
+A large number of run logs will be generated during database running and occupy huge disk space. You are advised to delete expired run logs and retain logs generated within one month.
+
+**Procedure**
+
+1. Log in as the OS user **omm** to any host in the MogDB Kernel cluster.
+
+2. Clean logs.
+
+   a. Back up logs generated over one month ago to other disks.
+
+   b. Access the directory where logs are stored.
+
+   ```
+   cd $GAUSSLOG
+   ```
+
+   c. Access the corresponding sub-directory and run the following command to delete logs generated one month ago:
+
+   ```
+   rm log name
+   ```
+
+   The naming convention of a log file is **mogdb-**year*-*month*-*day_**HHMMSS**.
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/6-checking-time-consistency.md b/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/6-checking-time-consistency.md
new file mode 100644
index 0000000000000000000000000000000000000000..52090c929f44951f2426a79667402e65da2c4e05
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/6-checking-time-consistency.md
@@ -0,0 +1,52 @@
+---
+title: Checking Time Consistency
+summary: Checking Time Consistency
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# Checking Time Consistency
+
+Database transaction consistency is guaranteed by a logical clock and is not affected by OS time. However, OS time inconsistency will lead to problems, such as abnormal backend O&M and monitoring functions. Therefore, you are advised to monthly check time consistency among nodes.
+
+**Procedure**
+
+1. Log in as the OS user **omm** to any host in the MogDB Kernel cluster.
+
+2. Create a configuration file for recording each cluster node. (You can specify the *mpphosts* file directory randomly. It is recommended that the file be stored in the **/tmp** directory.)
+
+   ```bash
+   vim /tmp/mpphosts
+   ```
+
+   Add the host name of each node.
+
+   ```
+   plat1
+   plat2
+   plat3
+   ```
+
+3. Save the configuration file.
+
+   ```
+   :wq!
+   ```
+
+4. Run the following command and write the time on each node into the **/tmp/sys_ctl-os1.log** file:
+
+   ```
+   for ihost in `cat /tmp/mpphosts`; do ssh -n -q $ihost "hostname;date"; done > /tmp/sys_ctl-os1.log
+   ```
+
+5. Check time consistency between the nodes based on the command output. The time difference should not exceed 30s.
+
+   ```
+   cat /tmp/sys_ctl-os1.log
+   plat1
+   Thu Feb  9 16:46:38 CST 2017
+   plat2
+   Thu Feb  9 16:46:49 CST 2017
+   plat3
+   Thu Feb  9 16:46:14 CST 2017
+   ```
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/7-checking-the-number-of-application-connections.md b/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/7-checking-the-number-of-application-connections.md
new file mode 100644
index 0000000000000000000000000000000000000000..f5f77f016e8644dfe1729ae93bf5b9de1bab1ba8
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/7-checking-the-number-of-application-connections.md
@@ -0,0 +1,130 @@
+---
+title: 日常运维
+summary: 日常运维
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# Checking the Number of Application Connections
+
+If the number of connections between applications and the database exceeds the maximum value, new connections cannot be established. You are advised to daily check the number of connections, release idle connections in time, or increase the allowed maximum number of connections.
+
+**Procedure**
+
+1. Log in as the OS user **omm** to the primary node of the database.
+
+2. Run the following command to connect to the database:
+
+   ```
+   gsql -d mogdb -p 8000
+   ```
+
+   **mogdb** is the name of the database to be connected, and **8000** is the port number of the database primary node.
+
+   If information similar to the following is displayed, the connection succeeds:
+
+   ```
+   gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+   Non-SSL connection (SSL connection is recommended when requiring high-security)
+   Type "help" for help.
+
+   mogdb=#
+   ```
+
+3. Run the following SQL statement to check the number of connections:
+
+   ```
+   mogdb=# SELECT count(*) FROM (SELECT pg_stat_get_backend_idset() AS backendid) AS s;
+   ```
+
+   Information similar to the following is displayed. **2** indicates that two applications are connected to the database.
+
+   ```
+   count
+   -------
+        2
+   (1 row)
+   ```
+
+4. View the allowed maximum connections.
+
+   ```
+   mogdb=# SHOW max_connections;
+   ```
+
+   Information similar to the following is displayed. **200** indicates the currently allowed maximum number of connections.
+
+   ```
+    max_connections
+   -----------------
+    200
+   (1 row)
+   ```
+
+## Exception Handling
+
+If the number of connections in the command output is close to the value of **max_connections** of the database, delete existing connections or change the upper limit based on site requirements.
+
+1. Run the following SQL statement to view information about connections whose **state** is set to **idle**, and **state_change** column is not updated for a long time.
+
+   ```
+   mogdb=# SELECT * FROM pg_stat_activity where state='idle' order by state_change;
+   ```
+
+   Information similar to the following is displayed:
+
+   ```
+    datid | datname  |       pid       | usesysid | usename  | application_name |  client_addr
+    | client_hostname | client_port |         backend_start         | xact_start |          quer
+   y_start          |         state_change          | waiting | enqueue | state | resource_pool
+   |                    query
+   -------+----------+-----------------+----------+----------+------------------+---------------
+   -+-----------------+-------------+-------------------------------+------------+--------------
+   -----------------+-------------------------------+---------+---------+-------+---------------
+   +----------------------------------------------
+    13626 | mogdb | 140390162233104 |       10 | gaussdba |                  |
+    |                 |          -1 | 2016-07-15 14:08:59.474118+08 |            | 2016-07-15 14
+   :09:04.496769+08 | 2016-07-15 14:09:04.496975+08 | f       |         | idle  | default_pool
+   | select count(group_name) from pgxc_group;
+    13626 | mogdb | 140390132872976 |       10 | gaussdba | cn_5002          | 10.180.123.163
+    |                 |       48614 | 2016-07-15 14:11:16.014871+08 |            | 2016-07-15 14
+   :21:17.346045+08 | 2016-07-15 14:21:17.346095+08 | f       |         | idle  | default_pool
+   | SET SESSION AUTHORIZATION DEFAULT;RESET ALL;
+   (2 rows)
+   ```
+
+2. Release idle connections.
+
+   Check each connection and release them after obtaining approval from the users of the connections. Run the following SQL command to release a connection using **pid** obtained in the previous step:
+
+   ```
+   mogdb=# SELECT pg_terminate_backend(140390132872976);
+   ```
+
+   Information similar to the following is displayed:
+
+   ```
+   mogdb=# SELECT pg_terminate_backend(140390132872976);
+    pg_terminate_backend
+   ----------------------
+    t
+   (1 row)
+   ```
+
+   If no connections can be released, go to the next step.
+
+3. Increase the maximum number of connections.
+
+   ```
+   gs_guc set -D /mogdb/data/dbnode -c "max_connections= 800"
+   ```
+
+   **800** is the new maximum value.
+
+4. Restart database services to make the new settings take effect.
+
+   >  **NOTE:** The restart results in operation interruption. Properly plan the restart to avoid affecting users.
+
+   ```
+   gs_om -t stop && gs_om -t start
+   ```
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/8-routinely-maintaining-tables.md b/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/8-routinely-maintaining-tables.md
new file mode 100644
index 0000000000000000000000000000000000000000..e99aeb3acb4adde43e4ac875e1a4a08978bd6b58
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/8-routinely-maintaining-tables.md
@@ -0,0 +1,111 @@
+---
+title: 日常运维
+summary: 日常运维
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# Routinely Maintaining Tables
+
+To ensure proper database running, after insert and delete operations, you need to routinely run **VACUUM FULL** and **ANALYZE** as appropriate for customer scenarios and update statistics to obtain better performance.
+
+**Related Concepts**
+
+You need to routinely run **VACUUM**, **VACUUM FULL**, and **ANALYZE** to maintain tables, because:
+
+- **VACUUM FULL** can be used to reclaim disk space occupied by updated or deleted data and combine small-size data files.
+- **VACUUM** can be used to maintain a visualized mapping for each table to track pages that contain arrays visible to other active transactions. A common index scan uses the mapping to obtain the corresponding arrays and check whether the arrays are visible to the current transaction. If the arrays cannot be obtained, capture a batch of arrays to check the visibility. Therefore, updating the visualized mapping of a table can accelerate unique index scans.
+- Running **VACUUM** can avoid original data loss caused by duplicate transaction IDs when the number of executed transactions exceeds the database threshold.
+- **ANALYZE** can be used to collect statistics on tables in databases. The statistics are stored in the system catalog **PG_STATISTIC**. Then the query optimizer uses the statistics to work out the most efficient execution plan.
+
+**Procedure**
+
+1. Run the **VACUUM** or **VACUUM FULL** command to reclaim disk space.
+
+   - **VACUUM**:
+
+     Run **VACUUM** for a table.
+
+     ```
+     mogdb=# VACUUM customer;
+     ```
+
+     ```
+     VACUUM
+     ```
+
+     This statement can be concurrently executed with database operation commands, including **SELECT**, **INSERT**, **UPDATE**, and **DELETE**; excluding **ALTER TABLE**.
+
+     Run **VACUUM** for the table partition.
+
+     ```
+     mogdb=# VACUUM customer_par PARTITION ( P1 );
+     ```
+
+     ```
+     VACUUM
+     ```
+
+   - **VACUUM FULL**:
+
+     ```
+     mogdb=# VACUUM FULL customer;
+     ```
+
+     ```
+     VACUUM
+     ```
+
+     During the command running, exclusive locks need to be added to the table and all other database operations need to be suspended.
+
+2. Run **ANALYZE** to update statistics.
+
+   ```
+   mogdb=# ANALYZE customer;
+   ```
+
+   ```
+   ANALYZE
+   ```
+
+   Run **ANALYZE VERBOSE** to update statistics and display table information.
+
+   ```
+   mogdb=# ANALYZE VERBOSE customer;
+   ```
+
+   ```
+   ANALYZE
+   ```
+
+   You can run **VACUUM ANALYZE** at the same time to optimize the query.
+
+   ```
+   mogdb=# VACUUM ANALYZE customer;
+   ```
+
+   ```
+   VACUUM
+   ```
+
+   >  **NOTE:** **VACUUM** and **ANALYZE** cause a substantial increase in I/O traffic, which may affect other active sessions. Therefore, you are advised to set the cost-based vacuum delay feature by specifying the **vacuum_cost_delay** parameter. For details, see "GUC Parameters > Resource Consumption > Cost-based Vacuum Delay" in the *Developer Guide*.
+
+3. Delete a table.
+
+   ```
+   mogdb=# DROP TABLE customer;
+   mogdb=# DROP TABLE customer_par;
+   mogdb=# DROP TABLE part;
+   ```
+
+   If the following information is displayed, the tables have been deleted:
+
+   ```
+   DROP TABLE
+   ```
+
+**Maintenance Suggestions**
+
+- Routinely run **VACUUM FULL** for large tables. If the database performance deteriorates, run **VACUUM FULL** for the entire database. If the database performance is stable, you are advised to run **VACUUM FULL** monthly.
+- Routinely run **VACUUM FULL** on system catalogs, especially **PG_ATTRIBUTE**.
+- Enable automatic vacuum processes (**AUTOVACUUM**) in the system. The processes automatically run the **VACUUM** and **ANALYZE** statements to reclaim the record space marked as the deleted state and update statistics in the table.
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md b/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md
new file mode 100644
index 0000000000000000000000000000000000000000..cfa38546f63ac7c8e1dd8d508e74e86c15c59190
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md
@@ -0,0 +1,68 @@
+---
+title: 日常运维
+summary: 日常运维
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# Routinely Recreating an Index
+
+## **Background**
+
+When data deletion is repeatedly performed in the database, index keys will be deleted from the index pages, resulting in index bloat. Recreating an index routinely improves query efficiency.
+
+The database supports B-tree indexes. Recreating a B-tree index routinely helps improve query efficiency.
+
+- If a large amount of data is deleted, index keys on the index pages will be deleted. As a result, the number of index pages reduces and index bloat occurs. Recreating an index helps reclaim wasted space.
+- In a newly created index, pages with adjacent logical structures tend to have adjacent physical structures. Therefore, a new index achieves a higher access speed than an index that has been updated for multiple times.
+
+**Methods**
+
+Use either of the following two methods to recreate an index:
+
+- Run the **DROP INDEX** statement to delete the index and run the **CREATE INDEX** statement to create an index.
+
+  When you delete an index, a temporary exclusive lock is added in the parent table to block related read/write operations. During index creation, the write operation is locked, whereas the read operation is not locked and can use only sequential scans.
+
+- Run **REINDEX** to recreate an index.
+
+  - When you run the **REINDEX TABLE** statement to recreate an index, an exclusive lock is added to block related read/write operations.
+  - When you run the **REINDEX INTERNAL TABLE** statement to recreate an index for a **desc** table (such as column-store **cudesc** table), an exclusive lock is added to block related read/write operations on the table.
+
+**Procedure**
+
+Assume the ordinary index **areaS_idx** exists in the **area_id** column of the imported table **areaS**. Use either of the following two methods to recreate an index:
+
+- Run the **DROP INDEX** statement to delete the index and run the **CREATE INDEX** statement to create an index.
+
+  1. Delete the index.
+
+     ```
+     mogdb=# DROP INDEX areaS_idx;
+     DROP INDEX
+     ```
+
+  2. Create an index
+
+     ```
+     mogdb=# CREATE INDEX areaS_idx ON areaS (area_id);
+     CREATE INDEX
+     ```
+
+- Run **REINDEX** to recreate an index.
+
+  - Run **REINDEX TABLE** to recreate an index.
+
+    ```
+    mogdb=# REINDEX TABLE areaS;
+    REINDEX
+    ```
+
+  - Run **REINDEX INTERNAL TABLE** to recreate an index for a **desc** table (such as column-store **cudesc** table).
+
+    ```
+    mogdb=# REINDEX INTERNAL TABLE areaS;
+    REINDEX
+    ```
+
+> **NOTE:** Before you recreate an index, you can increase the values of **maintenance_work_mem** and **psort_work_mem** to accelerate the index recreation.
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/using-the-gsql-client-for-connection.md b/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/using-the-gsql-client-for-connection.md
new file mode 100644
index 0000000000000000000000000000000000000000..b63da74edcbfb683a7104550b704f18daa6eb249
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/routine-maintenance/using-the-gsql-client-for-connection.md
@@ -0,0 +1,212 @@
+---
+title: Using the gsql Client for Connection
+summary: Using the gsql Client for Connection
+author: Zhang Cuiping
+date: 2021-04-14
+---
+
+# Using the gsql Client for Connection
+
+## Confirming Connection Information
+
+You can use a client tool to connect a database through the primary node of the database. Before the connection, obtain the IP address of the primary node of the database and the port number of the server where the primary node of the database is deployed.
+
+1. Log in to the primary node of the database as the OS user **omm**.
+
+2. Run the **gs_om -t status --detail** command to query instances in the MogDB cluster.
+
+   ```bash
+   gs_om -t status --detail
+
+   [  Datanode State   ]
+
+   node                 node_ip         instance                state
+   ---------------------------------------------------------------------------------
+   1  mogdb-kernel-0005 172.16.0.176    6001 /mogdb/data/db1 P Primary Normal
+   ```
+
+   For example, the server IP address where the primary node of the database is deployed is 172.16.0.176. The data path of the primary node of the database is **/mogdb/data/db1**.
+
+3. Confirm the port number of the primary node of the database.
+
+   View the port number in the **postgresql.conf** file in the data path of the primary database node obtained in step 2. The command is as follows:
+
+   ```bash
+   cat /mogdb/data/db1/postgresql.conf | grep port
+
+   port = 26000    # (change requires restart)
+   #comm_sctp_port = 1024   # Assigned by installation (change requires restart)
+   #comm_control_port = 10001  # Assigned by installation (change requires restart)
+         # supported by the operating system:
+         # e.g. 'localhost=10.145.130.2 localport=12211 remotehost=10.145.130.3 remoteport=12212, localhost=10.145.133.2 localport=12213 remotehost=10.145.133.3 remoteport=12214'
+         # e.g. 'localhost=10.145.130.2 localport=12311 remotehost=10.145.130.4 remoteport=12312, localhost=10.145.133.2 localport=12313 remotehost=10.145.133.4 remoteport=12314'
+         #   %r = remote host and port
+   alarm_report_interval = 10
+   support_extended_features=true
+   ```
+
+   **26000** in the first line is the port number of the primary database node.
+
+<br/>
+
+### Installing the gsql Client
+
+On the host, upload the client tool package and configure environment variables for the **gsql** client.
+
+1. Log in to the host where the client resides as any user.
+
+2. Run the following command to create the **/opt/mogdb/tools** directory:
+
+   ```bash
+   mkdir /opt/mogdb/tools
+   ```
+
+3. Obtain the file **MogDB-x.x.x-openEuler-64bit-tools.tar.gz** from the software installation package and upload it to the **/opt/mogdb/tools** directory.
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+   >
+   > - The software package is located where you put it before installation. Set it based on site requirements.
+   > - The tool package name may vary in different OSs. Select the tool package suitable for your OS.
+
+4. Run the following commands to decompress the package:
+
+   ```bash
+   cd /opt/mogdb/tools
+   tar -zxvf MogDB-x.x.x-openEuler-64bit-tools.tar.gz
+   ```
+
+5. Set environment variables.
+
+   Run the following command to open the **~/.bashrc** file:
+
+   ```bash
+   vi ~/.bashrc
+   ```
+
+   Enter the following content and run **:wq!** to save and exit.
+
+   ```bash
+   export PATH=/opt/mogdb/tools/bin:$PATH
+   export LD_LIBRARY_PATH=/opt/mogdb/tools/lib:$LD_LIBRARY_PATH
+   ```
+
+6. Run the following command to make the environment variables take effect:
+
+   ```bash
+   source ~/.bashrc
+   ```
+
+<br/>
+
+## Connecting to a Database Using gsql
+
+<br/>
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - By default, if a client is idle state after connecting to a database, the client automatically disconnects from the database in the duration specified by **session_timeout**. To disable the timeout setting, set **session_timeout** to **0**.
+
+<br/>
+
+### Connecting to a Database Locally
+
+1. Log in as the OS user **omm** to the primary node of the database.
+
+2. Connect to a database.
+
+   After the database is installed, a database named **postgres** is generated by default. When connecting to a database for the first time, you can connect to this database.
+
+   Run the following command to connect to the **postgres** database:
+
+   ```bash
+   gsql -d postgres -p 26000
+   ```
+
+   **postgres** is the name of the database to be connected, and **26000** is the port number of the database primary node. Replace the values as required.
+
+   If information similar to the following is displayed, the connection succeeds:
+
+   ```sql
+   gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+   Non-SSL connection (SSL connection is recommended when requiring high-security)
+   Type "help" for help.
+
+   postgres=#
+   ```
+
+   User **omm** is the administrator, and **postgres=#** is displayed. If you log in to and connect to the database as a common user, **postgres=&gt;** is displayed.
+
+   **Non-SSL connection** indicates that the database is not connected in SSL mode. If high security is required, connect to the database in SSL mode.
+
+3. Exit the database.
+
+   ```sql
+   postgres=# \q
+   ```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - When connecting to the database locally as user **omm**, no password is required. This is due to the default setting in the **pg_hba.conf** file that allows the local machine to connect in the **trust** way.
+> - For details about the client authentication methods, see the [Client Access Authentication](1-client-access-authentication) chapter.
+
+<br/>
+
+## Connecting to a Database Remotely
+
+<br/>
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - Due to security restrictions, you can not remotely connect to the database as user **omm**.
+
+<br/>
+
+### Configuring a Whitelist Using gs_guc (Update pg_hba.conf)
+
+1. Log in as the OS user **omm** to the primary node of the database.
+
+2. Configure the client authentication mode and enable the client to connect to the host as user **jack**. User **omm** cannot be used for remote connection.
+
+   Assume you are to allow the client whose IP address is **172.16.0.245** to access the current host.
+
+   ```sql
+   gs_guc set -N all -I all -h "host all jack 172.16.0.245/24 sha256"
+   ```
+
+   **NOTICE:**
+
+   - Before using user **jack**, connect to the database locally and run the following command in the database to create user **jack**:
+
+     ```sql
+     postgres=# CREATE USER jack PASSWORD 'Test@123';
+     ```
+
+   - **-N all**  indicates all hosts in MogDB.
+
+   - **-I all**  indicates all instances on the host.
+
+   - **-h**  specifies statements that need to be added in the  **pg_hba.conf**  file.
+
+   - **all**  indicates that a client can connect to any database.
+
+   - **jack**  indicates the user that accesses the database.
+
+   - **172.16.0.245/24**  indicates that only the client whose IP address is  **172.16.0.245**  can connect to the host. The specified IP address must be different from those used in MogDB.  **24**  indicates that there are 24 bits whose value is 1 in the subnet mask. That is, the subnet mask is 255.255.255.0.
+
+   - **sha256**  indicates that the password of user  **jack**  is encrypted using the SHA-256 algorithm.
+
+   This command adds a rule to the  **pg_hba.conf**  file corresponds to the primary node of the database. The rule is used to authenticate clients that access primary node.
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+   >
+   > + For details about the client authentication methods, see the [Client Access Authentication](1-client-access-authentication) chapter.
+
+3. Connect to a database.
+
+   After the database is installed, a database named **postgres** is generated by default. When connecting to a database for the first time, you can connect to this database.
+
+   ```bash
+   gsql -d postgres -h 172.16.0.176 -U jack -p 26000 -W Test@123
+   ```
+
+   **postgres** is the name of the database, **172.16.0.176** is the IP address of the server where the primary node of the database resides, **jack** is the user of the database, **26000** is the port number of the CN, and **Test@123** is the password of user **jack**.
diff --git a/product/en/docs-mogdb/v3.0/administrator-guide/upgrade-guide.md b/product/en/docs-mogdb/v3.0/administrator-guide/upgrade-guide.md
new file mode 100644
index 0000000000000000000000000000000000000000..3bd3f29a6e15d8c7f443f890e691de2148f04833
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/administrator-guide/upgrade-guide.md
@@ -0,0 +1,347 @@
+---
+title: Upgrade Guide
+summary: Upgrade Guide
+author: Zhang Cuiping
+date: 2021-09-27
+---
+
+# Upgrade Guide
+
+## Overview
+
+This document provides guidance on version upgrade and rollback process. It also offers common problem resolving and troubleshooting methods.
+
+## Intended Audience
+
+This document is mainly intended for upgrade operators. They must have the following experience and skills:
+
+- Be familiar with the networking of the current network and versions of related NEs (network elements).
+- Have maintenance experience of the related devices and be familiar with their operation and maintenance methods.
+
+## Upgrade Scheme
+
+This section provides guidance on selection of the upgrade modes.
+
+The user determines whether to upgrade the current system according to the new features of MogDB and database situations.
+
+The supported upgrade modes include in-place upgrade and gray upgrade. The upgrade strategies include major upgrade and minor upgrade.
+
+After the upgrade mode is determined, the system will automatically determine and choose the suitable upgrade strategy.
+
+* In-place upgrade: All services need to be stopped during the upgrade. All nodes are upgraded at a time.
+
+* Gray upgrade: supports full-service operations. All nodes are also upgraded at a time. (Currently, only the gray upgrade from version 1.1.0 to 2.0 and above is supported.)
+
+## Version Requirements Before the Upgrade (Upgrade Path)
+
+[Table 1](#biaoyi) lists the MogDB upgrade version requirements.
+
+**Table 1**  Version requirements before the upgrade (upgrade path)
+
+| Version              | Description                                                  |
+| -------------------- | ------------------------------------------------------------ |
+| MogDB 1.1.0 or later | Be able to be upgraded to any version later than MogDB 1.1.0. |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** You can run the following command to check the version before the upgrade:
+>
+> ```bash
+> gsql -V | --version
+> ```
+
+## Impact and Constraints
+
+The following precautions need to be considered during the upgrade:
+
+- The upgrade cannot be performed with capacity expansion and reduction concurrently.
+- VIP (virtual IP) is not supported.
+- During the upgrade, you are not allowed to modify the **wal_level**, **max_connections**, **max_prepared_transactions**, and **max_locks_per_transaction** GUC parameters. Otherwise, the instance will be started abnormally after rollback.
+- It is recommended that the upgrade is performed when the database system is under the light workload. You can determine the off-peak hours according to your experience, such as holidays and festivals.
+- Before the upgrade, make sure that the database is normal. You can run the **gs_om -t status** command to check the database status. If the returned value of **cluster_state** is **Normal**, the database is normal.
+- Before the upgrade, make sure that mutual trust is established between database nodes. You can run the **ssh hostname** command on any node to connect to another node to verify whether the mutual trust has been established. If mutual connection between any two nodes does not require a password, the mutual trust is normal. (Generally, when the database status is normal, mutual trust is normal.)
+- Before and after the upgrade, the database deployment mode must be kept consistent. Before the upgrade, the database deployment mode will be verified. If it is changed after the upgrade, an error will occur.
+- Before the upgrade, make sure that the OS is normal. You can check the OS status using the **gs_checkos** tool.
+- In-place upgrade requires stopping of services. Gray upgrade supports full-service operations.
+- The database is running normally and the data of the primary domain name (DN) is fully synchronized to the standby DN.
+- During the upgrade, the kerberos is not allowed to be enabled.
+- You are not allowed to modify the **version.cfg** file decompressed from the installation package.
+- During the upgrade, if an error causes upgrade failure, you need to perform rollback operations manually. The next upgrade can be performed only after the rollback is successful.
+- After the rollback, if the next upgrade is successful, GUC parameters set before the upgrade is submitted will become invalid.
+- During the upgrade, you are not allowed to set GUC parameters manually.
+- During the gray upgrade, service interruption will occur and lasts less than 10s.
+- During the upgrade, OM operations can be performed only when the kernel and OM versions are consistent. This consistency refers that the kernel code and OM code are from the same software package. If the pre-installation script of the installation package is executed but the upgrade is not performed, or the pre-installation script of the baseline package after the rollback is not  performed, the kernel code will be inconsistent with the OM code.
+- During the upgrade, if new fields are added to a system table but they cannot be found by running the **\d** command after the upgrade, you can run the **select** command to check the new fields.
+- The upgrade is allowed only when the value of **enable_stream_replication** is **on**.
+- During the gray upgrade, the number of concurrent read/write services must be less than 200.
+- If the MOT is used in MogDB 1.1.0, MogDB 1.1.0 cannot be upgraded to MogDB 2.1.
+
+## Upgrade Process
+
+This section describes the upgrade process.
+
+**Figure 1**  Upgrade process
+
+![21](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/upgrade-guide-2.png)
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif)**NOTE:** The time listed in the following table is for reference only. The actual time required depends on the upgrade environment.
+
+**Table 2**  Estimated upgrade efficiency
+
+<table> <tr> <td>  Procedure</td> <td>  Recommended Start Time</td> <td> Time Required (Day/Hour/Minute) </td> <td> Service Interruption Time </td> <td>  Remarks </td> </tr> <tr> <td>Perform the pre-upgrade preparations and check operations. </td> <td>  One day before the upgrade</td> <td> About 2 to 3 hours </td> <td> No impact on services </td> <td> Pre-upgrade check, data backup, and software package verification </td> </tr> <tr> <td> Perform the upgrade. </td> <td> Off-peak hours </td> <td>  The time is mainly spent in starting and stopping the database and modifying the system table of each database. The upgrade usually takes less than 30 minutes. </td> <td> The service interruption time is the same as the upgrade time. Generally, the time taken is not greater than 30 minutes.  </td> <td>  Performed based on the <i>Upgrade Guide</i></td> </tr> <tr> <td> Verify the upgrade.</td> <td> Off-peak hours</td> <td> About 30 minutes  </td> <td> The service interruption time is the same as the upgrade verification time, about 30 minutes.  </td> <td> - </td> </tr> <tr> <td> Submit the upgrade. </td> <td> Off-peak hours </td> <td>  The upgrade submission usually takes less than 10 minutes. </td> <td> The service interruption time is the same as the upgrade submission time. Generally, the time taken is not greater than 10 minutes.  </td> <td> - </td> </tr> <tr> <td>Roll back the upgrade.  </td> <td> Off-peak hours</td> <td> The rollback usually takes less than 30 minutes.  </td> <td> The service interruption time is the same as the rollback time. Generally, the time taken is not greater than 30 minutes.  </td> <td> - </td> </tr> </table>
+
+## Pre-Upgrade Preparations and Check
+
+### Pre-Upgrade Preparations and Checklist
+
+**Table 3**  Pre-upgrade preparations and checklist
+
+<table> <tr> <td>  No.</td> <td>  Item to Be Prepared for the Upgrade</td> <td> Preparation Content </td> <td> Recommended Start Time </td> <td>  Time Required (Day/Hour/Minute) </td> </tr> <tr> <td>1  </td> <td>    Collect node information. </td> <td>   Obtain the name, IP address, and passwords of users <b>root</b> and <b>omm</b> of related database nodes  </td> <td>One day before the upgrade </td> <td> 1 hour </td> </tr> <tr> <td> 2 </td> <td>   Set remote login as user <b>root</b>. </td> <td>  Set the configuration file that allows remote login as user <b>root</b></td> <td>One day before the upgrade </td> <td>  2 hours</td> </tr> <tr> <td>3 </td> <td> Back up data. </td> <td>  For details, see the <b>Backup and Restoration</b> section in the <i>Administrator Guide</i>.   </td> <td> One day before the upgrade </td> <td>The time taken varies depends on the volume of data to be backed up and the backup strategy.  </td> </tr> <tr> <td>4 </td> <td> Obtain and verify the installation package.  </td> <td>  Obtain the installation package and verify the package integrity. </td> <td>   One day before the upgrade </td> <td>0.5 hour </td> </tr> <tr> <td>5 </td> <td> Perform the health check. </td> <td> Check the OS status using the gs_checkos tool  </td> <td> One day before the upgrade </td> <td>   0.5 hour </td> </tr> <tr> <td>6 </td> <td>  Check the disk usage of each database node. </td> <td>  Check the disk usage by running the <b>df</b> command. </td> <td>   One day before the upgrade</td> <td> 0.5 hour</td> </tr> <tr> <td>7 </td> <td> Check the database status.  </td> <td> Check the database status using the <b>gs_om</b> tool. </td> <td> One day before the upgrade </td> <td>   0.5 hour </td> </tr> </table>
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif)**NOTE:** **Time Required** varies depends on the environment, including data volume, server performance, and other factors.
+
+### Collecting Node Information
+
+You can contact the system administrator to obtain the environment information, such as name, IP address, and passwords of users **root** and **omm** of the database node.
+
+**Table 4**  Node information <a id="biaosi"> </a>
+
+<table>
+<tr>
+<td>  No.</td>
+<td>  Node Name</td>
+<td> IP Address of the Node </td>
+<td>
+Password of User root</td>
+<td>  Password of User omm</td>
+<td> Remarks </td>
+</tr>
+<tr>
+<td>1  </td>
+<td>
+-</td>
+<td>
+- </td>
+<td>  -</td>
+<td>  -</td>
+<td> - </td>
+</tr>
+</table>
+
+### Backing Up Data
+
+Once the upgrade fails, services will be affected. Therefore, you need to back up data in advance so that services can be quickly restored once the risk occurs.
+
+For details about data backup, see the **Backup and Restoration** section in the *Administrator Guide*.
+
+### Obtaining the Installation Package
+
+You can obtain the installation package from [this website](https://www.mogdb.io/en/downloads/mogdb/).
+
+### Performing the Health Check
+
+The **gs_checkos** tool can be used to check the OS status.
+
+**Prerequisites**
+
+- The current hardware and network environment is normal.
+- The mutual trust between the **root** users of all hosts is normal.
+- The **gs_checkos** command can be executed only as user **root**.
+
+**Procedure**
+
+1. Log in to the primary database node as user **root**.
+
+2. Run the following command to check the server OS parameters:
+
+   ```
+   # gs_checkos -i A
+   ```
+
+   Checking the OS parameters aims to ensure that the database can be pre-installed normally and can be run safely and efficiently after being installed.
+
+#### Checking the Disk Usage of the Database Node
+
+It is recommended that the upgrade is performed when the disk usage of the database node is less than 80%.
+
+#### Checking the Database Status
+
+This section introduces how to check the database status.
+
+**Procedure**
+
+1. Log in to the primary database node as user **omm** and run the **source** command to reload environment variables.
+
+   ```
+   # su - omm
+   $ source /home/omm/.bashrc
+   ```
+
+2. Run the following command to check the database status:
+
+   ```bash
+   gs_om -t status
+   ```
+
+3. Ensure that the database status is normal.
+
+## Upgrade Procedure
+
+This section introduces details about in-place upgrade and gray upgrade.
+
+**Procedure**
+
+1. Log in to the primary database node as user **root**.
+
+2. Create a directory for storing the new package.
+
+   ```
+   # mkdir -p /opt/software/mogdb_upgrade
+   ```
+
+3. Upload the new package to the **/opt/software/mogdb_upgrade** directory and decompress the package.
+
+4. Found the **script** file.
+
+   ```
+   # cd /opt/software/mogdb_upgrade/script
+   ```
+
+5. Before the in-place or gray upgrade, execute the pre-installation script by running the **gs_preinstall** command. <a id="qianzhijiaoben"> </a>
+
+   ```
+   # ./gs_preinstall -U omm -G dbgrp  -X /opt/software/mogdb/clusterconfig.xml
+   ```
+
+6. Switch to user **omm**.
+
+   ```
+   # su - omm
+   ```
+
+7. After ensuring that the database status is normal, run the required command to perform the in-place upgrade or gray upgrade.
+
+   Example one: Execute the **gs_upgradectl** script to perform the in-place upgrade.
+
+   ```bash
+   gs_upgradectl -t auto-upgrade -X /opt/software/mogdb/clusterconfig.xml
+   ```
+
+   Example two: Execute the **gs_upgradectl** script to perform the gray upgrade.
+
+   ```bash
+   gs_upgradectl -t auto-upgrade -X /opt/software/mogdb/clusterconfig.xml --grey
+   ```
+
+## Upgrade Verification
+
+This section introduces upgrade verification and provides detailed use cases and operations.
+
+### Verifying the Checklist of the Project
+
+**Table 5**  Verification item checklist
+
+<table> <tr> <td>  No.</td> <td>    Verification Item</td> <td>  Check Standard</td> <td>    Check Result</td> </tr> <tr> <td>1  </td> <td>    Version check</td> <td>  Check whether the version is correct after the upgrade. </td> <td>  -</td> </tr> <tr> <td>2 </td> <td>    Health check</td> <td>   Use the <b>gs_checkos</b> tool to check the OS status. </td> <td>  -</td> </tr> <tr> <td>3  </td> <td>    Database status</td> <td>   Use the <b>gs_om</b> tool to check the database status. </td> <td>  -</td> </tr> </table>
+
+### Querying the Upgrade Version
+
+This section introduces how to check the version.
+
+**Procedure**
+
+1. Log in to the primary database node as user **omm** and run the **source** command to reload environment variables.
+
+   ```
+   # su - omm
+   $ source /home/omm/.bashrc
+   ```
+
+2. Run the following command to check the version information of all nodes:
+
+   ```bash
+   gs_ssh -c "gsql -V"
+   ```
+
+### Checking the Database Status
+
+This section introduces how to check the database status.
+
+**Procedure**
+
+1. Log in to the primary database node as user **omm**.
+
+   ```
+   # su - omm
+   ```
+
+2. Run the following command to check the database status:
+
+   ```bash
+   gs_om -t status
+   ```
+
+   If the value of **cluster_state** is **Normal**, the database is normal.
+
+## Upgrade Submission
+
+After the upgrade, if the verification is successful, the subsequent operation is to submit the upgrade.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** Once the upgrade is submitted, it cannot be rolled back.
+
+**Procedure**
+
+1. Log in to the primary database node as user **omm**.
+
+   ```
+   # su - omm
+   ```
+
+2. Run the following command to submit the upgrade:
+
+   ```bash
+   gs_upgradectl -t commit-upgrade  -X /opt/software/mogdb/clusterconfig.xml
+   ```
+
+## Version Rollback
+
+This section introduces how to roll back the upgrade.
+
+**Procedure**
+
+1. Log in to the primary database node as user **omm**.
+
+   ```
+   # su - omm
+   ```
+
+2. Run the following command to perform the rollback operation (rolling back the kernel code). After the rollback, if you need to keep the versions of the kernel code and OM code consistent, execute the pre-installation script in the old package. (For details, see the [execute the pre-installtion script](#qianzhijiaoben) step.)
+
+   ```bash
+   gs_upgradectl -t auto-rollback  -X /opt/software/mogdb/clusterconfig.xml
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** If the database is abnormal, run the following command to perform the forcible rollback operation:
+   >
+   > ```bash
+   >    gs_upgradectl -t auto-rollback -X /opt/software/mogdb/clusterconfig.xml   --force
+   > ```
+
+3. Check the version after the rollback.
+
+   ```bash
+   gs_om -V | --version
+   ```
+
+   If the upgrade fails, perform the following operations to resolve the issue:
+
+   a. Check whether the environment is abnormal.
+
+   For example, the disk is fully occupied, the network is faulty, or the installation package or upgrade version is incorrect. After the problem is located and resolved, try to perform the upgrade again.
+
+   b. If no environment issue is found or the upgrade fails again, collect related logs and contact technical engineers.
+
+   Run the following command to collect logs:
+
+   ```bash
+   gs_collector -begin-time='20200724 00:00' -end-time='20200725 00:00'
+   ```
+
+   If permitted, you are advised to retain the environment.
diff --git a/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/1-core-dump-occurs-due-to-full-disk-space.md b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/1-core-dump-occurs-due-to-full-disk-space.md
new file mode 100644
index 0000000000000000000000000000000000000000..abd30c482ce2a2bdca8c4fa5d27d1c13ca2b654f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/1-core-dump-occurs-due-to-full-disk-space.md
@@ -0,0 +1,22 @@
+---
+title: Core Dump Occurs due to Full Disk Space
+summary: Core Dump Occurs due to Full Disk Space
+author: Guo Huan
+date: 2021-05-24
+---
+
+# Core Dump Occurs due to Full Disk Space
+
+## Symptom
+
+When TPC-C is running, the disk space is full during injection. As a result, a core dump occurs on the MogDB process, as shown in the following figure.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/core-dump-occurs-due-to-full-disk-space.png)
+
+## Cause Analysis
+
+When the disk is full, Xlog logs cannot be written. The program exits through the panic log.
+
+## Procedure
+
+Externally monitor the disk usage and periodically clean up the disk.
diff --git a/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/2-core-dump-occurs-due-to-incorrect-settings-of-guc-parameter-log-directory.md b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/2-core-dump-occurs-due-to-incorrect-settings-of-guc-parameter-log-directory.md
new file mode 100644
index 0000000000000000000000000000000000000000..2a20343f1a3807a7fc5d06ddba0470b1d22c3b53
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/2-core-dump-occurs-due-to-incorrect-settings-of-guc-parameter-log-directory.md
@@ -0,0 +1,20 @@
+---
+title: Core Dump Occurs Due to Incorrect Settings of GUC Parameter log_directory
+summary: Core Dump Occurs Due to Incorrect Settings of GUC Parameter log_directory
+author: Guo Huan
+date: 2021-05-24
+---
+
+# Core Dump Occurs Due to Incorrect Settings of GUC Parameter log_directory
+
+## Symptom
+
+After the database process is started, a core dump occurs and no log is recorded.
+
+## Cause Analysis
+
+The directory specified by GUC parameter **log_directory** cannot be read or you do not have permissions to access this directory. As a result, the verification fails during the database startup, and the program exits through the panic log.
+
+## Procedure
+
+Set **log_directory** to a valid directory. For details, see [log_directory](1-logging-destination#log_directory).
diff --git a/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/3-core-dump-occurs-when-removeipc-is-enabled.md b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/3-core-dump-occurs-when-removeipc-is-enabled.md
new file mode 100644
index 0000000000000000000000000000000000000000..cb04b6b8901602d143d16484b6965a77c0740eaf
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/3-core-dump-occurs-when-removeipc-is-enabled.md
@@ -0,0 +1,24 @@
+---
+title: Core Dump Occurs when RemoveIPC Is Enabled
+summary: Core Dump Occurs when RemoveIPC Is Enabled
+author: Guo Huan
+date: 2021-05-24
+---
+
+# Core Dump Occurs when RemoveIPC Is Enabled
+
+## Symptom
+
+The **RemoveIPC** parameter in the OS configuration is set to **yes**. The database breaks down during running, and the following log information is displayed:
+
+```
+FATAL: semctl(1463124609, 3, SETVAL, 0) failed: Invalid argument
+```
+
+## Cause Analysis
+
+If **RemoveIPC** is set to **yes**, the OS deletes the IPC resources (shared memory and semaphore) when the corresponding user exits. As a result, the IPC resources used by the MogDB server are cleared, causing the database to break down.
+
+## Procedure
+
+Set **RemoveIPC** to **no**. For details, see [Modifying OS Configuration](3-modifying-os-configuration) in the *Installation Guide*.
diff --git a/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/4-core-dump-occurs-after-installation-on-x86.md b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/4-core-dump-occurs-after-installation-on-x86.md
new file mode 100644
index 0000000000000000000000000000000000000000..0258da542e7bfc06585c3b580c02d35d6b3e2a8d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/4-core-dump-occurs-after-installation-on-x86.md
@@ -0,0 +1,26 @@
+---
+title: Core Dump Occurs After Installation on x86
+summary: Core Dump Occurs After Installation on x86
+author: Guo Huan
+date: 2021-12-09
+---
+
+# Core Dump Occurs After Installation on x86
+
+## Symptom
+
+The core dump occurs after the installation of MogDB on x86 architecture machine is completed, and the error in the following figure displays
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/core-dump-occurs-after-installation-on-x86-1.png)
+
+## Cause Analysis
+
+The x86 architecture does not include the rdtscp instruction set, and the deployment of MogDB fails. This problem is common in the case of virtualized installation of Linux server on local windows system, but the virtualization version is too low.
+
+## Procedure
+
+Run the `lscpu | grep rdtscp` command to see if the rdtscp instruction set is supported.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/core-dump-occurs-after-installation-on-x86-2.png)
+
+Support for this instruction set can be enabled through the host's admin side settings. Set the cloud host CPU mode to **host-passthrough**, and then reboot.
diff --git a/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/10-disk-space-usage-reaches-the-threshold.md b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/10-disk-space-usage-reaches-the-threshold.md
new file mode 100644
index 0000000000000000000000000000000000000000..0e7ce312879f0bd51cc8211964064716025083a8
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/10-disk-space-usage-reaches-the-threshold.md
@@ -0,0 +1,58 @@
+---
+title: Disk Space Usage Reaches the Threshold and the Database Becomes Read-only
+summary: Disk Space Usage Reaches the Threshold and the Database Becomes Read-only
+author: Guo Huan
+date: 2021-05-24
+---
+
+# Disk Space Usage Reaches the Threshold and the Database Becomes Read-only
+
+## Symptom
+
+The following error is reported when a non-read-only SQL statement is executed:
+
+```
+ERROR: cannot execute %s in a read-only transaction.
+```
+
+An error is reported when some non-read-only SQL statements (such as insert, update, create table as, create index, alter table, and copy from) are executed:
+
+```
+canceling statement due to default_transaction_read_only is on.
+```
+
+## Cause Analysis
+
+After the disk space usage reaches the threshold, the database enters the read-only mode. In this mode, only read-only statements can be executed.
+
+## Procedure
+
+1. Use either of the following methods to connect to the database in maintenance mode:
+
+   - Method 1
+
+     ```
+     gsql -d mogdb -p 8000 -r -m
+     ```
+
+   - Method 2
+
+     ```
+     gsql -d mogdb -p 8000 -r
+     ```
+
+     After the connection is successful, run the following command:
+
+     ```
+     set xc_maintenance_mode=on;
+     ```
+
+2. Run the **DROP** or **TRUNCATE** statement to delete user tables that are no longer used until the disk space usage falls below the threshold.
+
+   Deleting user tables can only temporarily relieve the insufficient disk space. To permanently solve the problem, expand the disk space.
+
+3. Disable the read-only mode of the database as user **omm**.
+
+   ```
+   gs_guc reload -D /mogdb/data/dbnode -c "default_transaction_read_only=off"
+   ```
diff --git a/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/11-slow-response-to-a-query-statement.md b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/11-slow-response-to-a-query-statement.md
new file mode 100644
index 0000000000000000000000000000000000000000..822bcaccf015e99f44753af86dfd2b5e5f78993c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/11-slow-response-to-a-query-statement.md
@@ -0,0 +1,48 @@
+---
+title: Slow Response to a Query Statement
+summary: Slow Response to a Query Statement
+author: Guo Huan
+date: 2021-05-24
+---
+
+# Slow Response to a Query Statement
+
+## Symptom
+
+After a query statement has been executed, no response is returned for a long time.
+
+## Cause Analysis
+
+- The query statement is complex and requires a long time for execution.
+- The query statement is blocked.
+
+## Procedure
+
+1. Log in to the host as the OS user **omm**.
+
+2. Run the following command to connect to the database:
+
+   ```
+   gsql -d mogdb -p 8000
+   ```
+
+   **mogdb** is the name of the database, and **8000** is the port number.
+
+3. Check for the query statements that are executed for a long time in the system.
+
+   ```
+   SELECT timestampdiff(minutes, query_start, current_timestamp) AS runtime, datname, usename, query FROM pg_stat_activity WHERE state != 'idle' ORDER BY 1 desc;
+   ```
+
+   Query statements are returned, sorted by execution time length in descending order. The first record is the query statement that takes the long time for execution.
+
+   Alternatively, you can use the [TIMESTAMPDIFF](8-date-and-time-processing-functions-and-operators) function to set **current_timestamp** and **query_start** to be greater than a threshold to identify query statements that are executed for a duration longer than this threshold. The first parameter of **timestampdiff** is the time difference unit. For example, execute the following statement to query the statements whose execution lasts more than 2 minutes:
+
+   ```
+   SELECT query FROM pg_stat_activity WHERE timestampdiff(minutes, query_start, current_timestamp) > 2;
+   ```
+
+4. Analyze the status of the query statements that were run for a long time.
+
+   - If the query statement is normal, wait until the execution of the query statement is complete.
+   - If the query statement is blocked, rectify the fault by referring to [Analyzing Whether a Query Statement Is Blocked](14-analyzing-whether-a-query-statement-is-blocked).
diff --git a/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/12-analyzing-the-status-of-a-query-statement.md b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/12-analyzing-the-status-of-a-query-statement.md
new file mode 100644
index 0000000000000000000000000000000000000000..08a8c1b897a07b5d2bdb0eb4650356f8df914a10
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/12-analyzing-the-status-of-a-query-statement.md
@@ -0,0 +1,57 @@
+---
+title: Analyzing the Status of a Query Statement
+summary: Analyzing the Status of a Query Statement
+author: Guo Huan
+date: 2021-05-24
+---
+
+# Analyzing the Status of a Query Statement
+
+## Symptom
+
+Some query statements are executed for an excessively long time in the system. You need to analyze the status of the query statements.
+
+## Procedure
+
+1. Log in to the host as the OS user **omm**.
+
+2. Run the following command to connect to the database:
+
+   ```
+   gsql -d mogdb -p 8000
+   ```
+
+   **mogdb** is the name of the database, and **8000** is the port number.
+
+3. Set the parameter **track_activities** to **on**.
+
+   ```
+   SET track_activities = on;
+   ```
+
+   The database collects the running information about active queries only if the parameter is set to **on**.
+
+4. View the running query statements. The **pg_stat_activity** view is used as an example here.
+
+   ```
+   SELECT datname, usename, state, query FROM pg_stat_activity;
+   datname  | usename | state  | query
+   ----------+---------+--------+-------
+   mogdb     | omm     | idle   |
+   mogdb     | omm     | active |
+   (2 rows)
+   ```
+
+   If the **state** column is **idle**, the connection is idle and requires a user to enter a command. To identify only active query statements, run the following command:
+
+   ```
+   SELECT datname, usename, state, query FROM pg_stat_activity WHERE state != 'idle';
+   ```
+
+5. Analyze whether a query statement is in the active or blocked state. Run the following command to view a query statement in the block state:
+
+   ```
+   SELECT datname, usename, state, query FROM pg_stat_activity WHERE waiting = true;
+   ```
+
+   The query statement is displayed. It is requesting a lock resource that may be held by another session, and is waiting for the lock resource to be released by the session.
diff --git a/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/13-forcibly-terminating-a-session.md b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/13-forcibly-terminating-a-session.md
new file mode 100644
index 0000000000000000000000000000000000000000..6b04991aafec8b6a6c13c082500bde2b7abc7fee
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/13-forcibly-terminating-a-session.md
@@ -0,0 +1,62 @@
+---
+title: Forcibly Terminating a Session
+summary: Forcibly Terminating a Session
+author: Guo Huan
+date: 2021-05-24
+---
+
+# Forcibly Terminating a Session
+
+## Symptom
+
+In some cases, the administrator must forcibly terminate abnormal sessions to keep the system healthy.
+
+## Procedure
+
+1. Log in to the host as the OS user **omm**.
+
+2. Run the following command to connect to the database:
+
+   ```
+   gsql -d mogdb -p 8000
+   ```
+
+   **mogdb** is the name of the database, and **8000** is the port number.
+
+3. Find the thread ID of the faulty session from the current active session view.
+
+   ```
+   SELECT datid, pid, state, query FROM pg_stat_activity;
+   ```
+
+   A command output similar to the following is displayed, where the pid value indicates the thread ID of the session.
+
+   ```
+   datid |       pid       | state  | query
+   -------+-----------------+--------+------
+   13205 | 139834762094352 | active |
+   13205 | 139834759993104 | idle   |
+   (2 rows)
+   ```
+
+4. Terminate the session using its thread ID.
+
+   ```
+   SELECT pg_terminate_backend(139834762094352);
+   ```
+
+   If information similar to the following is displayed, the session is successfully terminated:
+
+   ```
+   pg_terminate_backend
+   ---------------------
+   t
+   (1 row)
+   ```
+
+   If a command output similar to the following is displayed, a user is attempting to terminate the session, and the session will be reconnected rather than being terminated.
+
+   ```
+   FATAL:  terminating connection due to administrator command
+   FATAL:  terminating connection due to administrator command The connection to the server was lost. Attempting reset: Succeeded.
+   ```
diff --git a/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/14-analyzing-whether-a-query-statement-is-blocked.md b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/14-analyzing-whether-a-query-statement-is-blocked.md
new file mode 100644
index 0000000000000000000000000000000000000000..226fa3ff060dd542d60b36b79093a86c2d24054f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/14-analyzing-whether-a-query-statement-is-blocked.md
@@ -0,0 +1,56 @@
+---
+title: Analyzing Whether a Query Statement Is Blocked
+summary: Analyzing Whether a Query Statement Is Blocked
+author: Guo Huan
+date: 2021-05-24
+---
+
+# Analyzing Whether a Query Statement Is Blocked
+
+## Symptom
+
+During database running, query statements are blocked in some service scenarios. As a result, the query statements are executed for an excessively long time.
+
+## Cause Analysis
+
+A query statement uses a lock to protect the data objects that it wants to access. If the data objects have been locked by another session, the query statement will be blocked and wait for the session to complete operation and release the lock resource. The data objects requiring locks include tables and tuples.
+
+## Procedure
+
+1. Log in to the host as the OS user **omm**.
+
+2. Run the following command to connect to the database:
+
+   ```
+   gsql -d mogdb -p 8000
+   ```
+
+   **mogdb** is the name of the database, and **8000** is the port number.
+
+3. Find the thread ID of the faulty session from the current active session view.
+
+   ```
+   SELECT w.query AS waiting_query, w.pid AS w_pid, w.usename AS w_user, l.query AS locking_query, l.pid AS l_pid, l.usename AS l_user, t.schemaname || '.' || t.relname AS tablename FROM pg_stat_activity w JOIN pg_locks l1 ON w.pid = l1.pid AND NOT l1.granted JOIN pg_locks l2 ON l1.relation = l2.relation AND l2.granted JOIN pg_stat_activity l ON l2.pid = l.pid JOIN pg_stat_user_tables t ON l1.relation = t.relid WHERE w.waiting = true;
+   ```
+
+4. Terminate the session using its thread ID.
+
+   ```
+   SELECT pg_terminate_backend(139834762094352);
+   ```
+
+   If information similar to the following is displayed, the session is successfully terminated:
+
+   ```
+   pg_terminate_backend
+   ---------------------
+   t
+   (1 row)
+   ```
+
+   If a command output similar to the following is displayed, a user is attempting to terminate the session, and the session will be reconnected rather than being terminated.
+
+   ```
+   FATAL:  terminating connection due to administrator command
+   FATAL:  terminating connection due to administrator command The connection to the server was lost. Attempting reset: Succeeded.
+   ```
diff --git a/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/15-low-query-efficiency.md b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/15-low-query-efficiency.md
new file mode 100644
index 0000000000000000000000000000000000000000..479c9e35dc1ba78b9fe3a2238afa62cdb4a1c7e1
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/15-low-query-efficiency.md
@@ -0,0 +1,32 @@
+---
+title: Low Query Efficiency
+summary: Low Query Efficiency
+author: Guo Huan
+date: 2021-05-24
+---
+
+# Low Query Efficiency
+
+## Symptom
+
+A query task that used to take a few milliseconds to complete is now requiring several seconds, and that used to take several seconds is now requiring even half an hour.
+
+## Procedure
+
+Perform the following procedure to locate the cause.
+
+1. Run the **analyze** command to analyze the database.
+
+   Run the **analyze** command to update statistics such as data sizes and attributes in all tables. You are advised to perform the operation with light job load. If the query efficiency is improved or restored after the command execution, the **autovacuum** process does not function well that requires further analysis.
+
+2. Check whether the query statement returns unnecessary information.
+
+   For example, if a query statement is used to query all records in a table with the first 10 records being used, then it is quick to query a table with 50 records. However, if a table contains 50000 records, the query efficiency decreases. If an application requires only a part of data information but the query statement returns all information, add a LIMIT clause to the query statement to restrict the number of returned records. In this way, the database optimizer can optimize space and improve query efficiency.
+
+3. Check whether the query statement still has a low response even when it is solely executed.
+
+   Run the query statement when there are no or only a few other query requests in the database, and observe the query efficiency. If the efficiency is high, the previous issue is possibly caused by a heavily loaded host in the database system or
+
+4. Check the same query statement repeatedly to check the query efficiency.
+
+   One major cause of low query efficiency is that the required information is not cached in the memory or is replaced by other query requests due to insufficient memory resources. This can be verified by running the same query statement repeatedly and the query efficiency increases gradually.
diff --git a/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/16-lock-wait-timeout-is-displayed.md b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/16-lock-wait-timeout-is-displayed.md
new file mode 100644
index 0000000000000000000000000000000000000000..1944729224a8780c1a0ac7da777588ae5fc7d96a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/16-lock-wait-timeout-is-displayed.md
@@ -0,0 +1,25 @@
+---
+title: Lock wait timeout Is Displayed When a User Executes an SQL Statement
+summary: Lock wait timeout Is Displayed When a User Executes an SQL Statement
+author: Guo Huan
+date: 2021-05-24
+---
+
+# "Lock wait timeout" Is Displayed When a User Executes an SQL Statement
+
+## Symptom
+
+"Lock wait timeout" is displayed when a user executes an SQL statement.
+
+```
+ERROR:  Lock wait timeout: thread 140533638080272 waiting for ShareLock on relation 16409 of database 13218 after 1200000.122 ms ERROR:  Lock wait timeout: thread 140533638080272 waiting for AccessExclusiveLock on relation 16409 of database 13218 after 1200000.193 ms
+```
+
+## Cause Analysis
+
+Lock waiting times out in the database.
+
+## Procedure
+
+- After detecting such errors, the database automatically retries the SQL statements. The number of retries is controlled by **max_query_retry_times**.
+- To analyze the cause of the lock wait timeout, find the SQL statements that time out in the **pg_locks** and **pg_stat_activity** system catalogs.
diff --git a/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/17-table-size-does-not-change.md b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/17-table-size-does-not-change.md
new file mode 100644
index 0000000000000000000000000000000000000000..ce32f744d1816aee73e45f868e0120127061d697
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/17-table-size-does-not-change.md
@@ -0,0 +1,39 @@
+---
+title: Table Size Does not Change After VACUUM FULL Is Executed on the Table
+summary: Table Size Does not Change After VACUUM FULL Is Executed on the Table
+author: Guo Huan
+date: 2021-05-24
+---
+
+# Table Size Does not Change After VACUUM FULL Is Executed on the Table
+
+## Symptom
+
+A user runs the **VACUUM FULL** command to clear a table, the table size does not change.
+
+## Cause Analysis
+
+Assume the table is named **table_name**. Possible causes are as follows:
+
+- No data has been deleted from the **table_name** table. Therefore, the execution of **VACUUM FULL table_name** does not cause the table size to change.
+- Concurrent transactions exist during the execution of **VACUUM FULL table_name**. As a result, recently deleted data may be skipped when clearing the table.
+
+## Procedure
+
+For the second possible cause, use either of the following methods:
+
+- Wait until all concurrent transactions are complete, and run the **VACUUM FULL table_name** command again.
+
+- If the table size still does not change, ensure no service operations are performed on the table, and then execute the following SQL statements to query the active transaction list status:
+
+  ```
+  select txid_current();
+  ```
+
+  The current XID is obtained. Then, run the following command to check the active transaction list:
+
+  ```
+  select txid_current_snapshot();
+  ```
+
+  If any XID in the active transaction list is smaller than the current transaction XID, stop the database and then start it. Run **VACUUM FULL** to clear the table again.
diff --git a/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/18-an-error-is-reported-when-the-table-partition-is-modified.md b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/18-an-error-is-reported-when-the-table-partition-is-modified.md
new file mode 100644
index 0000000000000000000000000000000000000000..c5710586803c4dbb5d8c1ff210fb0c31e7b1c3ae
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/18-an-error-is-reported-when-the-table-partition-is-modified.md
@@ -0,0 +1,46 @@
+---
+title: An Error Is Reported When the Table Partition Is Modified
+summary: An Error Is Reported When the Table Partition Is Modified
+author: Guo Huan
+date: 2021-05-24
+---
+
+# An Error Is Reported When the Table Partition Is Modified
+
+## Symptom
+
+When **ALTER TABLE PARTITION** is performed, the following error message is displayed:
+
+```
+ERROR:start value of partition "XX" NOT EQUAL up-boundary of last partition.
+```
+
+## Cause Analysis
+
+If the **ALTER TABLE PARTITION** statement involves both the DROP PARTITION operation and the ADD PARTITION operation, MogDB always performs the DROP PARTITION operation before the ADD PARTITION operation regardless of their orders. However, performing DROP PARTITION before ADD PARTITION causes a partition gap. As a result, an error is reported.
+
+## Procedure
+
+To prevent partition gaps, set **END** in DROP PARTITION to the value of **START** in ADD PARTITION. The following is an example:
+
+```
+-- Create a partitioned table partitiontest.
+mogdb=#  CREATE TABLE partitiontest
+(
+c_int integer,
+c_time TIMESTAMP WITHOUT TIME ZONE
+)
+PARTITION BY range (c_int)
+(
+partition p1 start(100)end(108),
+partition p2 start(108)end(120)
+);
+-- An error is reported when the following statements are used:
+mogdb=#  ALTER TABLE partitiontest ADD PARTITION p3 start(120)end(130), DROP PARTITION p2;
+ERROR:  start value of partition "p3" NOT EQUAL up-boundary of last partition.
+mogdb=#  ALTER TABLE partitiontest DROP PARTITION p2,ADD PARTITION p3 start(120)end(130);
+ERROR:  start value of partition "p3" NOT EQUAL up-boundary of last partition.
+-- Change them as follows:
+mogdb=#  ALTER TABLE partitiontest ADD PARTITION p3 start(108)end(130), DROP PARTITION p2;
+mogdb=#  ALTER TABLE partitiontest DROP PARTITION p2,ADD PARTITION p3 start(108)end(130);
+```
diff --git a/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/19-different-data-is-displayed.md b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/19-different-data-is-displayed.md
new file mode 100644
index 0000000000000000000000000000000000000000..2a916055ec0340fb50fb590742c8e98e5b69eafb
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/19-different-data-is-displayed.md
@@ -0,0 +1,32 @@
+---
+title: Different Data Is Displayed for the Same Table Queried By Multiple Users
+summary: Different Data Is Displayed for the Same Table Queried By Multiple Users
+author: Guo Huan
+date: 2021-05-24
+---
+
+# Different Data Is Displayed for the Same Table Queried By Multiple Users
+
+## Symptom
+
+Two users log in to the same database human_resource and run the following statement separately to query the areas table, but obtain different results.
+
+```
+select count(*) from areas;
+```
+
+## Cause Analysis
+
+1. Check whether tables with same names are really the same table. In a relational database, a table is identified by three elements: **database**, **schema**, and **table**. In this issue, **database** is **human_resource** and **table** is **areas**.
+2. Check whether schemas of tables with the same name are consistent. Log in as users **omm** and **user01** separately. It is found that **search_path** is **public** and **$user**, respectively. As **omm** is the cluster administrator, a schema having the same name as user **omm** will not be created by default. That is, all tables will be created in **public** if no schema is specified. However, when a common user, such as **user01**, is created, the same-name schema (**user01**) is created by default. That is, all tables are created in **user01** if the schema is not specified.
+3. If different users access different data in the same table, check whether objects in the table have different access policies for different users.
+
+## Procedure
+
+- For the query of tables with the same name in different schemas, add the schema reference to the queried table. The format is as follows:
+
+  ```
+  schema.table
+  ```
+
+- If different access policies result in different query results of the same table, you can query the **pg_rlspolicy** system catalog to determine the specific access rules.
diff --git a/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/2-when-the-tpcc-is-running.md b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/2-when-the-tpcc-is-running.md
new file mode 100644
index 0000000000000000000000000000000000000000..bd1a3f9de1fcf92473c9d87a263152cf3f727fe3
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/2-when-the-tpcc-is-running.md
@@ -0,0 +1,20 @@
+---
+title: When the TPC-C is running and a disk to be injected is full, the TPC-C stops responding.
+summary: When the TPC-C is running and a disk to be injected is full, the TPC-C stops responding.
+author: Guo Huan
+date: 2021-05-24
+---
+
+# When the TPC-C is running and a disk to be injected is full, the TPC-C stops responding
+
+## Symptom
+
+When the TPC-C is running and a disk to be injected is full, the TPC-C stops responding. After the fault is rectified, the TPC-C automatically continues to run.
+
+## Cause Analysis
+
+When the disk where the performance log (**gs_profile**) is located is full, the database cannot write data and enters the infinite waiting state. As a result, the TPC-C stops responding. After the disk space insufficiency fault is rectified, performance logs can be properly written, and the TPC-C is restored.
+
+## Procedure
+
+Externally monitor the disk usage and periodically clean up the disk.
diff --git a/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/20-when-a-user-specifies-only-an-index-name.md b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/20-when-a-user-specifies-only-an-index-name.md
new file mode 100644
index 0000000000000000000000000000000000000000..58f381dd29aaef3d3b2e076f04919f108f66d6ec
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/20-when-a-user-specifies-only-an-index-name.md
@@ -0,0 +1,47 @@
+---
+title: When a User Specifies Only an Index Name to Modify the Index, A Message Indicating That the Index Does Not Exist Is Displayed
+summary: When a User Specifies Only an Index Name to Modify the Index, A Message Indicating That the Index Does Not Exist Is Displayed
+author: Guo Huan
+date: 2021-05-24
+---
+
+# When a User Specifies Only an Index Name to Modify the Index, A Message Indicating That the Index Does Not Exist Is Displayed
+
+## Symptom
+
+When a User Specifies Only an Index Name to Modify the Index, A Message Indicating That the Index Does Not Exist Is Displayed The following provides an example:
+
+```
+-- Create a partitioned table index HR_staffS_p1_index1, without specifying index partitions.
+CREATE INDEX HR_staffS_p1_index1 ON HR.staffS_p1 (staff_ID) LOCAL;
+-- Create a partitioned table index HR_staffS_p1_index2, with index partitions specified.
+CREATE INDEX HR_staffS_p1_index2 ON HR.staffS_p1 (staff_ID) LOCAL
+(
+PARTITION staff_ID1_index,
+PARTITION staff_ID2_index TABLESPACE example3,
+PARTITION staff_ID3_index TABLESPACE example4
+) TABLESPACE example;
+-- Change the tablespace of index partition staff_ID2_index to example1. A message is displayed, indicating that the index does not exist.
+ALTER INDEX HR_staffS_p1_index2 MOVE PARTITION staff_ID2_index TABLESPACE example1;
+```
+
+## Cause Analysis
+
+The possible reason is that the user is in the public schema instead of the hr schema.
+
+```
+-- Run the following command to validate the inference. It is found that the calling is successful.
+ALTER INDEX hr.HR_staffS_p1_index2 MOVE PARTITION staff_ID2_index TABLESPACE example1;
+-- Change the schema of the current session to hr.
+ALTER SESSION SET CURRENT_SCHEMA TO hr;
+-- Run the following command to modify the index:
+ALTER INDEX HR_staffS_p1_index2 MOVE PARTITION staff_ID2_index TABLESPACE example1;
+```
+
+## Procedure
+
+Add a schema reference to a table, index, or view. The format is as follows:
+
+```
+schema.table
+```
diff --git a/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/21-reindexing-fails.md b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/21-reindexing-fails.md
new file mode 100644
index 0000000000000000000000000000000000000000..d8920008ea20e994d71b262654841aa64d36719f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/21-reindexing-fails.md
@@ -0,0 +1,29 @@
+---
+title: Reindexing Fails
+summary: Reindexing Fails
+author: Guo Huan
+date: 2021-05-24
+---
+
+# Reindexing Fails
+
+## Symptom
+
+When an index of the desc table is damaged, a series of operations cannot be performed. The error information may be as follows:
+
+```
+index \"%s\" contains corrupted page at block
+ %u" ,RelationGetRelationName(rel),BufferGetBlockNumber(buf), please reindex it.
+```
+
+## Cause Analysis
+
+In actual operations, indexes may break down due to software or hardware faults. For example, if disk space is insufficient or pages are damaged after indexes are split, the indexes may be damaged.
+
+## Procedure
+
+If the table is a column-store table named **pg_cudesc_xxxxx_index**, the desc index table is damaged. Find the OID and table corresponding to the primary table based on the desc index table name, and run the following statement to recreate the cudesc index.
+
+```
+REINDEX INTERNAL TABLE name;
+```
diff --git a/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/22-an-error-occurs-during-integer-conversion.md b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/22-an-error-occurs-during-integer-conversion.md
new file mode 100644
index 0000000000000000000000000000000000000000..e353708426e46193c8907c0aee48a18e075beac9
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/22-an-error-occurs-during-integer-conversion.md
@@ -0,0 +1,24 @@
+---
+title: An Error Occurs During Integer Conversion
+summary: An Error Occurs During Integer Conversion
+author: Guo Huan
+date: 2021-05-24
+---
+
+# An Error Occurs During Integer Conversion
+
+## Symptom
+
+The following error is reported during integer conversion:
+
+```
+Invalid input syntax for integer: "13."
+```
+
+## Cause Analysis
+
+Some data types cannot be converted to the target data type.
+
+## Procedure
+
+Gradually narrow down the range of SQL statements to determine the data types that cannot be converted.
diff --git a/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/23-too-many-clients-already.md b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/23-too-many-clients-already.md
new file mode 100644
index 0000000000000000000000000000000000000000..59e5b1d1fdd39c625a12458087e634f1266b8ef6
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/23-too-many-clients-already.md
@@ -0,0 +1,50 @@
+---
+title: too many clients already Is Reported or Threads Failed To Be Created in High Concurrency Scenarios
+summary: too many clients already Is Reported or Threads Failed To Be Created in High Concurrency Scenarios
+author: Guo Huan
+date: 2021-05-24
+---
+
+# "too many clients already" Is Reported or Threads Failed To Be Created in High Concurrency Scenarios
+
+## Symptom
+
+When a large number of SQL statements are concurrently executed, the error message "sorry, too many clients already" is displayed or an error is reported, indicating that threads cannot be created or processes cannot be forked.
+
+## Cause Analysis
+
+These errors are caused by insufficient OS threads. Check **ulimit -u** in the OS. If the value is too small (for example, less than 32768), the errors are caused by the OS limitation.
+
+## Procedure
+
+Run **ulimit -u** to obtain the value of **max user processes** in the OS.
+
+```
+[root@MogDB36 mnt]# ulimit -u
+unlimited
+```
+
+Use the following formula to calculate the minimum value:
+
+```
+value=max (32768, number of instances x 8192)
+```
+
+The number of instances refers to the total number of instances on the node.
+
+To set the minimum value, add the following two lines to the **/etc/security/limits.conf** file:
+
+```
+* hard nproc [value]
+* soft nproc [value]
+```
+
+The file to be modified varies based on the OS. For versions later than CentOS6, modify the **/etc/security/limits.d/90-nofile.conf** file in the same way.
+
+Alternatively, you can run the following command to change the value. However, the change becomes invalid upon OS restart. To solve this problem, you can add **ulimit -u [value]** to the global environment variable file **/etc/profile**.
+
+```
+ulimit -u [values]
+```
+
+In high concurrency mode, enable the thread pool to control thread resources in the database.
diff --git a/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/24-b-tree-index-faults.md b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/24-b-tree-index-faults.md
new file mode 100644
index 0000000000000000000000000000000000000000..c04a36d92e7b877ab9f758e8b740cc85e5f90ac1
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/24-b-tree-index-faults.md
@@ -0,0 +1,68 @@
+---
+title: B-tree Index Faults
+summary: B-tree Index Faults
+author: Guo Huan
+date: 2021-05-24
+---
+
+# B-tree Index Faults
+
+## Symptom
+
+The following error message is displayed, indicating that the index is lost occasionally.
+
+```
+ERROR: index 'xxxx_index' contains unexpected zero page
+Or
+ERROR: index 'pg_xxxx_index' contains unexpected zero page
+Or
+ERROR: compressed data is corrupt
+```
+
+## Cause Analysis
+
+This type of error is caused by the index fault. The possible causes are as follows:
+
+- The index is unavailable due to software bugs or hardware faults.
+- The index contains many empty pages or almost empty pages.
+- During concurrent DDL execution, the network is intermittently disconnected.
+- The index failed to be created when indexes are concurrently created.
+- A network fault occurs when a DDL or DML operation is performed.
+
+## Procedure
+
+Run the REINDEX command to rebuild the index.
+
+1. Log in to the host as the OS user **omm**.
+
+2. Run the following command to connect to the database:
+
+   ```
+   gsql -d mogdb -p 8000 -r
+   ```
+
+3. Rebuild the index.
+
+   - During DDL or DML operations, if index problems occur due to software or hardware faults, run the following command to rebuild the index:
+
+     ```
+     REINDEX TABLE tablename;
+     ```
+
+   - If the error message contains **xxxx_index**, the index of a user table is faulty. **xxxx** indicates the name of the user table. Run either of the following commands to rebuild the index:
+
+     ```
+     REINDEX INDEX indexname;
+     ```
+
+     Or
+
+     ```
+     REINDEX TABLE tablename;
+     ```
+
+   - If the error message contains **pg_xxxx_index**, the index of the system catalog is faulty. Run the following command to rebuild the index:
+
+     ```
+     REINDEX SYSTEM databasename;
+     ```
diff --git a/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/3-standby-node-in-the-need-repair-state.md b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/3-standby-node-in-the-need-repair-state.md
new file mode 100644
index 0000000000000000000000000000000000000000..0859df7e1d3750689a73209ac8ee0d20ad6240b0
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/3-standby-node-in-the-need-repair-state.md
@@ -0,0 +1,20 @@
+---
+title: Standby Node in the Need Repair (WAL) State
+summary: Standby Node in the Need Repair (WAL) State
+author: Guo Huan
+date: 2021-05-24
+---
+
+# Standby Node in the **Need Repair (WAL)** State
+
+## Symptom
+
+The **Need Repair (WAL)** fault occurs on a standby node of the MogDB.
+
+## Cause Analysis
+
+The primary and standby DB instances are disconnected due to network faults or insufficient disk space. As a result, logs are not synchronized between the primary and standby DB instances, and the database cluster fails to start.
+
+## Procedure
+
+Run the **gs_ctl build -D** command to rebuild the faulty node. For details, see the [build parameter](4-gs_ctl#6) in the *MogDB Tool Reference*.
diff --git a/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/4-insufficient-memory.md b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/4-insufficient-memory.md
new file mode 100644
index 0000000000000000000000000000000000000000..1bdc8300c9e4d89c03ef3de875625d05f261ee43
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/4-insufficient-memory.md
@@ -0,0 +1,20 @@
+---
+title: Insufficient Memory
+summary: Insufficient Memory
+author: Guo Huan
+date: 2021-05-24
+---
+
+# Insufficient Memory
+
+## Symptom
+
+The client or logs contain the error message **memory usage reach the max_dynamic_memory**.
+
+## Cause Analysis
+
+The possible cause is that the value of the GUC parameter **max_process_memory** is too small. This parameter limits the maximum memory that can be used by an MogDB instance.
+
+## Procedure
+
+Use the **gs_guc** tool to adjust the value of **max_process_memory**. Note that you need to restart the instance for the modification to take effect.
diff --git a/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/5-service-startup-failure.md b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/5-service-startup-failure.md
new file mode 100644
index 0000000000000000000000000000000000000000..ee94999f57c8d23d931e9cd8b3994580ce93337d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/5-service-startup-failure.md
@@ -0,0 +1,88 @@
+---
+title: Service Startup Failure
+summary: Service Startup Failure
+author: Guo Huan
+date: 2021-05-24
+---
+
+# Service Startup Failure
+
+## Symptom
+
+The service startup failed.
+
+## Cause Analysis
+
+- Parameters are set to improper values, resulting in insufficient system resources in the database cluster, or parameter settings do not meet the internal restrictions in the cluster.
+- The status of some DNs is abnormal.
+- Permissions to modify directories are insufficient. For example, users do not have sufficient permissions for the **/tmp** directory or the data directory in the cluster.
+- The configured port has been occupied.
+- The system firewall is enabled.
+- The trust relationship between servers of the database in the cluster is abnormal.
+
+## Procedure
+
+- Check whether the parameter configurations are improper or meet internal constraints.
+
+  - Log in to the node that cannot be started. Check the run logs and check whether the resources are insufficient or whether the parameter configurations meet internal constraints. For example, if the message "Out of memory" or the following error information is displayed, the resources are insufficient, the startup fails, or the configuration parameters do not meet the internal constraints.
+
+    ```
+    FATAL: hot standby is not possible because max_connections = 10 is a lower setting than on the master server (its value was 100)
+    ```
+
+  - Check whether the GUC parameters are set to proper values. For example, check parameters, such as **shared_buffers**, **effective_cache_size**, and **bulk_write_ring_size** that consume much resources, or parameter **max_connections** that cannot be easily set to a value that is less than its last value. For details about how to view and set GUC parameters, see Configuring Running Parameters.
+
+- Check whether the status of some DNs is abnormal. Check the status of each primary and standby instances in the current cluster using **gs_om -t status -detail**.
+
+  - If the status of all the instances on a host is abnormal, replace the host.
+
+  - If the status of an instance is **Unknown**, **Pending**, or **Down**, log in to the node where the instance resides as a cluster user to view the instance log and identify the cause. For example:
+
+    ```
+    2014-11-27 14:10:07.022 CST 140720185366288 FATAL:  database "postgres" does not exist 2014-11-27 14:10:07.022 CST 140720185366288 DETAIL:  The database subdirectory "base/ 13252" is missing.
+    ```
+
+    If the preceding information is displayed in a log, files stored in the data directory where the DN resides are damaged, and the instance cannot be queried. You cannot execute normal queries to this instance.
+
+- Check whether users have sufficient directory permissions. For example, users do not have sufficient permissions for the **/tmp** directory or the data directory in the cluster.
+
+  - Determine the directory for which users have insufficient permissions.
+  - Run the **chmod** command to modify directory permissions as required. The database user must have read/write permissions for the **/tmp** directory. To modify permissions for data directories, refer to the settings for data directories with sufficient permissions.
+
+- Check whether the configured ports have been occupied.
+
+  - Log in to the node that cannot be started and check whether the instance process exists.
+
+  - If the instance process does not exist, view the instance log to check the exception reasons. For example:
+
+    ```
+    2014-10-17 19:38:23.637 CST 139875904172320 LOG:  could not bind IPv4 socket at the 0 time: Address already in use 2014-10-17 19:38:23.637 CST 139875904172320 HINT:  Is another postmaster already running on port 40005? If not, wait a few seconds and retry.
+    ```
+
+    If the preceding information is displayed in a log, the TCP port on the DN has been occupied, and the instance cannot be started.
+
+    ```
+    2015-06-10 10:01:50 CST 140329975478400 [SCTP MODE] WARNING: (sctp bind)         bind(socket=9, [addr:0.0.0.0,port:1024]):Address already in use  --  attempt 10/10 2015-06-10 10:01:50 CST 140329975478400 [SCTP MODE] ERROR: (sctp bind)   Maximum bind() attempts. Die now...
+    ```
+
+    If the preceding information is displayed in a log, the SCTP port on the DN has been occupied, and the instance cannot be started.
+
+- Run **sysctl -a** to view the **net.ipv4.ip_local_port_range** parameter. If this port configured for this instance is within the range of the port number randomly occupied by the system, modify the value of **net.ipv4.ip_local_port_range**, ensuring that all the instance port numbers in the XML file are beyond this range. Check whether a port has been occupied:
+
+  ```
+  netstat -anop | grep Port number
+  ```
+
+  The following is an example:
+
+  ```
+  [root@MogDB36 ~]# netstat -anop | grep 15970
+  tcp        0      0 127.0.0.1:15970         0.0.0.0:*               LISTEN      3920251/mogdb      off (0.00/0/0)
+  tcp6       0      0 ::1:15970               :::*                    LISTEN      3920251/mogdb      off (0.00/0/0)
+  unix  2      [ ACC ]     STREAM     LISTENING     197399441 3920251/mogdb      /tmp/.s.PGSQL.15970
+  unix  3      [ ]         STREAM     CONNECTED     197461142 3920251/mogdb      /tmp/.s.PGSQL.15970
+  ```
+
+- Check whether the system firewall is enabled.
+
+- Check whether the mutual trust relationship is abnormal. Reconfigure the mutual trust relationship between servers in the cluster.
diff --git a/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/6-error-no-space-left-on-device-is-displayed.md b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/6-error-no-space-left-on-device-is-displayed.md
new file mode 100644
index 0000000000000000000000000000000000000000..e87b496e6a84ebfce718b53fc29c53f8f1753a5a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/6-error-no-space-left-on-device-is-displayed.md
@@ -0,0 +1,64 @@
+---
+title: Error:No space left on device Is Displayed
+summary: Error:No space left on device Is Displayed
+author: Guo Huan
+date: 2021-05-24
+---
+
+# "Error:No space left on device" Is Displayed
+
+## Symptom
+
+The following error message is displayed when the cluster is being used:
+
+```
+Error:No space left on device
+```
+
+## Cause Analysis
+
+The disk space is insufficient.
+
+## Procedure
+
+- Run the following command to check the disk usage. The **Avail** column indicates the available disk space, and the **Use%** column indicates the percentage of disk space that has been used.
+
+    ```
+    [root@openeuler123 mnt]# df -h
+    Filesystem                  Size  Used Avail Use% Mounted on
+    devtmpfs                    255G     0  255G   0% /dev
+    tmpfs                       255G   35M  255G   1% /dev/shm
+    tmpfs                       255G   57M  255G   1% /run
+    tmpfs                       255G     0  255G   0% /sys/fs/cgroup
+    /dev/mapper/openeuler-root  196G  8.8G  178G   5% /
+    tmpfs                       255G  1.0M  255G   1% /tmp
+    /dev/sda2                   9.8G  144M  9.2G   2% /boot
+    /dev/sda1                    10G  5.8M   10G   1% /boot/efi
+    ```
+
+    The demand for remaining disk space depends on the increase in service data. Suggestions:
+
+  - Check the disk space usage status, ensuring that the remaining space is sufficient for the growth of disk space for over one year.
+  - If the disk space usage exceeds 60%, you must clear or expand the disk space.
+
+- Run the following command to check the size of the data directory.
+
+  ```
+   du --max-depth=1 -h /mnt/
+  ```
+
+  The following information is displayed. The first column shows the sizes of directories or files, and the second column shows all the sub-directories or files under the **/mnt/** directory.
+
+  ```
+  [root@MogDB36 mnt]# du --max-depth=1 -h /mnt
+  83G /mnt/data3
+  71G /mnt/data2
+  365G    /mnt/data1
+  518G    /mnt
+  ```
+
+- Clean up the disk space. You are advised to periodically back up audit logs to other storage devices. The recommended log retention period is one month. **pg_log** stores database process run logs which help database administrators locate faults. You can delete error logs if you view them every day and handle errors in time.
+
+- Delete useless data. Back up data that is not used frequently or used for a certain period of time to storage media with lower costs, and clean the backup data to free up disk space.
+
+- If the disk space is still insufficient, expand the disk capacity.
diff --git a/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/7-after-you-run-the-du-command.md b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/7-after-you-run-the-du-command.md
new file mode 100644
index 0000000000000000000000000000000000000000..e2e8d4fabff6f1c8be852b6b410f681780b2f1b3
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/7-after-you-run-the-du-command.md
@@ -0,0 +1,32 @@
+---
+title: After You Run the du Command to Query Data File Size In the XFS File System, the Query Result Is Greater than the Actual File Size
+summary: After You Run the du Command to Query Data File Size In the XFS File System, the Query Result Is Greater than the Actual File Size
+author: Guo Huan
+date: 2021-05-24
+---
+
+# After You Run the du Command to Query Data File Size In the XFS File System, the Query Result Is Greater than the Actual File Size
+
+## Symptom
+
+After you run the **du** command to query data file size in the cluster, the query result is probably greater than the actual file size.
+
+```
+ du -sh file
+```
+
+## Cause Analysis
+
+The XFS file system has a pre-assignment mechanism. The file size is determined by the **allocsize** parameter. The file size displayed by the **du** command includes the pre-assigned disk space.
+
+## Procedure
+
+- Select the default value (64 KB) for the XFS file system mount parameter allocsize to eliminate the problem.
+
+- Add the **-apparent-size** parameter when using the **du** command to query the actual file size.
+
+  ```
+  du -sh file --apparent-size
+  ```
+
+- If the XFS file system reclaims the pre-assigned space of a file, the **du** command displays the actual file size.
diff --git a/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/8-file-is-damaged-in-the-xfs-file-system.md b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/8-file-is-damaged-in-the-xfs-file-system.md
new file mode 100644
index 0000000000000000000000000000000000000000..8b1f081fc8cfd54c85e9604e83e75f1aa420ec57
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/8-file-is-damaged-in-the-xfs-file-system.md
@@ -0,0 +1,22 @@
+---
+title: File Is Damaged in the XFS File System
+summary: File Is Damaged in the XFS File System
+author: Guo Huan
+date: 2021-05-24
+---
+
+# File Is Damaged in the XFS File System
+
+## Symptom
+
+When a cluster is in use, error reports such as an input/output error or the structure needs cleaning generally do not occur in the XFS file system.
+
+## Cause Analysis
+
+The XFS file system is abnormal.
+
+## Procedure
+
+Try to mount or unmount the file system to check whether the problem can be solved.
+
+If the problem recurs, refer to the file system document, such as **xfs_repair**, and ask the system administrator to restore the file system. After the file system is repaired, run the **gs_ctl build** command to restore the damaged DNs.
diff --git a/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/9-primary-node-is-hung-in-demoting.md b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/9-primary-node-is-hung-in-demoting.md
new file mode 100644
index 0000000000000000000000000000000000000000..36409ffe18838895b4fc9ae61c93f7622c57b37b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/9-primary-node-is-hung-in-demoting.md
@@ -0,0 +1,24 @@
+---
+title: Primary Node Is Hung in Demoting During a Switchover
+summary: Primary Node Is Hung in Demoting During a Switchover
+author: Guo Huan
+date: 2021-05-24
+---
+
+# Primary Node Is Hung in Demoting During a Switchover
+
+## Symptom
+
+In a cluster deployed with one primary and multiple standby DNs, if system resources are insufficient and a switchover occurs, a node is hung in demoting.
+
+## Cause Analysis
+
+If system resources are insufficient, the third-party management thread cannot be created. As a result, the managed sub-threads cannot exit and the primary node is hung in demoting.
+
+## Procedure
+
+Run the following command to stop the process of the primary node so that the standby node can be promoted to primary: Perform the following operations only in the preceding scenario.
+
+```
+ kill -9 PID
+```
diff --git a/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-methods.md b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-methods.md
new file mode 100644
index 0000000000000000000000000000000000000000..8f5c488c81e86c202774b2e3aed4f48a85cb860d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-methods.md
@@ -0,0 +1,283 @@
+---
+title: Common Fault Locating Methods
+summary: Common Fault Locating Methods
+author: Guo Huan
+date: 2021-05-24
+---
+
+# Common Fault Locating Methods
+
+## **Locating OS Faults**
+
+If all instances on a node are abnormal, an OS fault may have occurred.
+
+Use one of the following methods to check whether any OS fault occurs:
+
+- Log in to the node using SSH or other remote login tools. If the login fails, run the **ping** command to check the network status.
+
+  - If no response is returned, the server is down or being restarted, or its network connection is abnormal.
+
+    The restart takes a long time (about 20 minutes) if the system crashes due to an OS kernel panic. Try to connect the host every 5 minutes. If the connection failed 20 minutes later, the server is down or the network connection is abnormal. In this case, contact the administrator to locate the fault on site.
+
+  - If ping operations succeed but SSH login fails or commands cannot be executed, the server does not respond to external connections possibly because system resources are insufficient (for example, CPU or I/O resources are overloaded). In this case, try again. If the fault persists within 5 minutes, contact the administrator for further fault locating on site.
+
+- If login is successful but responses are slow, check the system running status, such as collecting system information as well as checking system version, hardware, parameter setting, and login users. The following are common commands for reference:
+
+  - Use the **who** command to check online users.
+
+    ```
+    [root@MogDB36 ~]# who
+    root     pts/0        2020-11-07 16:32 (10.70.223.238)
+    wyc      pts/1        2020-11-10 09:54 (10.70.223.222)
+    root     pts/2        2020-10-10 14:20 (10.70.223.238)
+    root     pts/4        2020-10-09 10:14 (10.70.223.233)
+    root     pts/5        2020-10-09 10:14 (10.70.223.233)
+    root     pts/7        2020-10-31 17:03 (10.70.223.222)
+    root     pts/9        2020-10-20 10:03 (10.70.220.85)
+    ```
+
+  - Use the **cat /etc/openEuler-release** and **uname -a** commands to check the system version and kernel information.
+
+    ```
+    [root@MogDB36 ~]# cat /etc/openEuler-release
+    openEuler release 20.03 (LTS)
+    [root@MogDB36 ~]# uname -a
+    Linux MogDB36 4.19.90-2003.4.0.0036.oe1.aarch64 #1 SMP Mon Mar 23 19:06:43 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux
+    [root@MogDB36 ~]#
+    ```
+
+  - Use the **sysctl -a** (run this command as user **root**) and **cat /etc/sysctl.conf** commands to obtain system parameter information.
+
+  - Use the **cat /proc/cpuinfo** and **cat /proc/meminfo** commands to obtain CPU and memory information.
+
+    ```
+    [root@MogDB36 ~]# cat /proc/cpuinfo
+    processor   : 0
+    BogoMIPS    : 200.00
+    Features    : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm jscvt fcma dcpop asimddp asimdfhm
+    CPU implementer : 0x48
+    CPU architecture: 8
+    CPU variant : 0x1
+    CPU part    : 0xd01
+    CPU revision    : 0
+    [root@MogDB36 ~]# cat /proc/meminfo
+    MemTotal:       534622272 kB
+    MemFree:        253322816 kB
+    MemAvailable:   369537344 kB
+    Buffers:         2429504 kB
+    Cached:         253063168 kB
+    SwapCached:            0 kB
+    Active:         88570624 kB
+    Inactive:       171801920 kB
+    Active(anon):    4914880 kB
+    Inactive(anon): 67011456 kB
+    Active(file):   83655744 kB
+    Inactive(file): 104790464 kB
+    ```
+
+  - Use the **top -H** command to query the CPU usage and check whether the CPU usage is high due to a specific process. If it is, use the **gdb** or **gstack** command to print the stack trace of this process and check whether this process is in an infinite loop.
+
+  - Use the **iostat -x 1 3** command to query the I/O usage and check whether the I/O usage of the current disk is full. View the ongoing jobs to determine whether to handle the jobs with high I/O usage.
+
+  - Use the **vmstat 1 3** command to query the memory usage in the current system and use the **top** command to obtain the processes with unexpectedly high memory usage.
+
+  - View the OS logs (**/var/log/messages**) or dmseg information as user **root** to check whether errors have occurred in the OS.
+
+  - The watchdog of an OS is a mechanism to ensure that the OS runs properly or exits from the infinite loop or deadlock state. If the watchdog times out (the default value is 60s), the system resets.
+
+## **Locating Network Faults**
+
+When the database runs normally, the network layer is transparent to upper-layer users. However, during the long-term operation of a database cluster, network exceptions or errors may occur. Common exceptions caused by network faults are as follows:
+
+- Network error reported due to database startup failure.
+- Abnormal status, for example, all instances on a host are in the **UnKnown** state, or all services are switched over to standby instances.
+- Network connection failure.
+- Network disconnection reported during database sql query.
+- Process response failures during database connection or query execution. When a network fault occurs in a database, locate and analyze the fault by using network-related Linux command tools (such as **ping**, **ifconfig**, **netstat**, and **lsof**) and process stack viewers (such as **gdb** and **gstack**) based on database log information. This section lists common network faults and describes how to analyze and locate faults.
+
+Common faults are as follows:
+
+- Network error reported due to a startup failure
+
+  **Symptom 1**: The log contains the following error information. The port may be listened on by another process.
+
+  ```
+  LOG: could not bind socket at the 10 time, is another postmaster already running on port 54000?
+  ```
+
+  **Solution**: Run the following command to check the process that listens on the port. Replace the port number with the actual one.
+
+  ```
+  [root@MogDB36 ~]# netstat -anop | grep 15970
+  tcp        0      0 127.0.0.1:15970         0.0.0.0:*               LISTEN      3920251/mogdb      off (0.00/0/0)
+  tcp6       0      0 ::1:15970               :::*                    LISTEN      3920251/mogdb      off (0.00/0/0)
+  unix  2      [ ACC ]     STREAM     LISTENING     197399441 3920251/mogdb      /tmp/.s.PGSQL.15970
+  unix  3      [ ]         STREAM     CONNECTED     197461142 3920251/mogdb      /tmp/.s.PGSQL.15970
+
+  ```
+
+  Forcibly stop the process that is occupying the port or change the listening port of the database based on the query result.
+
+  **Symptom 2**: When the **gs_om -t status -detail** command is used to query status, the command output shows that the connection between the primary and standby nodes is not established.
+
+  **Solution**: In openEuler, run the **systemctl status firewalld.service** command to check whether the firewall is enabled on this node. If it is enabled, run the **systemctl stop firewalld.service** command to disable it.
+
+  ```
+  [root@MogDB36 mnt]# systemctl status firewalld.service
+  ●firewalld.service - firewalld - dynamic firewall daemon
+     Loaded: loaded (/usr/lib/systemd/system/firewalld.service; disabled; vendor preset: enabled)
+     Active: inactive (dead)
+       Docs: man:firewalld(1)
+  ```
+
+  The command varies according to the operating system. You can run the corresponding command to view and modify the configuration.
+
+- The database is abnormal.
+
+  **Symptom**: The following problems occur on a node:
+
+  - All instances are in the **Unknown** state.
+  - All primary instances are switched to standby instances.
+  - Errors "Connection reset by peer" and "Connection timed out" are frequently displayed.
+
+  **Solution**
+
+  - If you cannot connect to the faulty server through SSH, run the **ping** command on other servers to send data packages to the faulty server. If the ping operation succeeds, connection fails because resources such as memory, CPUs, and disks, on the faulty server are used up.
+
+  - Connect to the faulty server through through SSH and run the **/sbin/ifconfig eth ?** command every other second (replace the question mark (?) with the number indicating the position of the NIC). Check value changes of **dropped** and **errors**. If they increase rapidly, the NIC or NIC driver may be faulty.
+
+    ```
+    [root@MogDB36 ~]# ifconfig enp125s0f0
+    enp125s0f0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
+            inet 10.90.56.36  netmask 255.255.255.0  broadcast 10.90.56.255
+            inet6 fe80::7be7:8038:f3dc:f916  prefixlen 64  scopeid 0x20<link>
+            ether 44:67:47:7d:e6:84  txqueuelen 1000  (Ethernet)
+            RX packets 129344246  bytes 228050833914 (212.3 GiB)
+            RX errors 0  dropped 647228  overruns 0  frame 0
+            TX packets 96689431  bytes 97279775245 (90.5 GiB)
+            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
+    ```
+
+  - Check whether the following parameters are correctly configured:
+
+    ```
+    net.ipv4.tcp_retries1 = 3
+    net.ipv4.tcp_retries2 = 15
+    ```
+
+- Network connection failure.
+
+  **Symptom 1**: A node fails to connect to other nodes, and the "Connection refused" error is reported in the log.
+
+  **Solution**
+
+  - Check whether the port is incorrectly configured, resulting in that the port used for connection is not the listening port of the peer end. Check whether the port number recorded in the **postgresql.conf** configuration file of the faulty node is the same as the listening port number of the peer end.
+  - Check whether the peer listening port is normal (for example, by running the **netstat -anp** command).
+  - Check whether the peer process exists.
+
+  **Symptom 2**: When SQL operations are performed on the database, the connection descriptor fails to be obtained. The following error information is displayed:
+
+  ```
+  WARNING:  29483313: incomplete message from client:4905,9
+  WARNING:  29483313: failed to receive connDefs at the time:1.
+  ERROR:  29483313: failed to get pooled connections
+  ```
+
+  In logs, locate and view the log content before the preceding error messages, which are generated due to incorrect active and standby information. Error details are displayed as follows.
+
+  ```
+  FATAL:  dn_6001_6002: can not accept connection in pending mode.
+  FATAL:  dn_6001_6002: the database system is starting up
+  FATAL:  dn_6009_6010: can not accept connection in standby mode.
+  ```
+
+  **Solution**
+
+  - Run the **gs_om -t status -detail** command to query the status and check whether an primary/standby switchover has occurred. Reset the instance status.
+  - In addition, check whether a core dump or restart occurs on the node that fails to be connected. In the om log, check whether restart occurs.
+
+- Network disconnection reported during database sql query.
+
+  **Symptom 1**: The query fails, and the following error information is displayed:
+
+  ```
+  ERROR:  dn_6065_6066: Failed to read response from Datanodes. Detail: Connection reset by peer. Local: dn_6065_6066 Remote: dn_6023_6024
+  ERROR: Failed to read response from Datanodes Detail: Remote close socket unexpectedly
+  ERROR: dn_6155_6156: dn_6151_6152: Failed to read vector response from Datanodes
+  ```
+
+  If the connection fails, the error information may be as follows:
+
+  ```
+  ERROR:  Distribute Query unable to connect 10.145.120.79:14600 [Detail:stream connect connect() fail: Connection timed out
+  ERROR: Distribute Query unable to connect 10.144.192.214:12600 [Detail:receive accept response fail: Connection timed out
+  ```
+
+  **Solution**
+
+  1. Use **gs_check** to check whether the network configuration meets requirements. For network check, see "Tool Reference &gt; Server Tools &gt; [gs_check](1-gs_check)" in the *Reference Guide*.
+  2. Check whether a process core dump, restart, or switchover occurs.
+  3. If problems still exist, contact network technical engineers.
+
+## **Locating Disk Faults**
+
+Common disk faults include insufficient disk space, bad blocks of disks, and unmounted disks. Disk faults such as unmount of disks damage the file system. The cluster management mechanism identifies this kind of faults and stops the instance, and the instance status is **Unknown**. However, disk faults such as insufficient disk space do not damage the file system. The cluster management mechanism cannot identify this kind of faults and service processes exit abnormally when accessing a faulty disk. Failures cover database startup, checksum verification, page read and write operation, and page verification.
+
+- For faults that result in file system damages, the instance status is **Unknown** when you view the host status. Perform the following operations to locate the disk fault:
+
+  - Check the logs. If the logs contain information similar to "data path disc writable test failed", the file system is damaged.
+
+  - The possible cause of file system damage may be unmounted disks. Run the **ls -l** command and you can view that the disk directory permission is abnormal, as shown in the following:
+
+  - Another possible cause is that the disk has bad blocks. In this case, the OS rejects read and write operations to protect the file system. You can use a bad block check tool, for example, **badblocks**, to check whether bad blocks exist.
+
+    ```
+    [root@openeuler123 mnt]# badblocks /dev/sdb1 -s -v
+    Checking blocks 0 to 2147482623
+    Checking for bad blocks (read-only test): done
+    Pass completed, 0 bad blocks found. (0/0/0 errors)
+    ```
+
+- For faults that do not damage the file system, the service process will report an exception and exit when it accesses the faulty disk. Perform the following operations to locate the disk fault:
+
+  View logs. The log contains read and write errors, such as "No space left on device" and "invalid page header n block 122838 of relation base/16385/152715". Run the **df -h** command to check the disk space. If the disk usage is 100% as shown below, the read and write errors are caused by insufficient disk space:
+
+  ```
+  [root@openeuler123 mnt]# df -h
+  Filesystem                  Size  Used Avail Use% Mounted on
+  devtmpfs                    255G     0  255G   0% /dev
+  tmpfs                       255G   35M  255G   1% /dev/shm
+  tmpfs                       255G   57M  255G   1% /run
+  tmpfs                       255G     0  255G   0% /sys/fs/cgroup
+  /dev/mapper/openeuler-root  196G  8.8G  178G   5% /
+  tmpfs                       255G  1.0M  255G   1% /tmp
+  /dev/sda2                   9.8G  144M  9.2G   2% /boot
+  /dev/sda1                    10G  5.8M   10G   1% /boot/efi
+  /dev/mapper/openeuler-home  1.5T   69G  1.4T   5% /home
+  tmpfs                        51G     0   51G   0% /run/user/0
+  tmpfs                        51G     0   51G   0% /run/user/1004
+  /dev/sdb1                   2.0T  169G  1.9T   9% /data
+  ```
+
+## **Locating Database Faults**
+
+- Logs. Database logs record the operations (starting, running, and stopping) on servers. Database users can view logs to quickly locate fault causes and rectify the faults accordingly.
+
+- View. A database provides different views to display its internal status. When locating a fault, you can use:
+
+  - **pg_stat_activity**: shows the status of each session on the current instance.
+  - **pg_thread_wait_status**: shows the wait events of each thread on the current instance.
+  - **pg_locks**: shows the status of locks on the current instance.
+
+- Core files. Abnormal termination of a database process will trigger a core dump. A core dump file helps locate faults and determine fault causes. Once a core dump occurs during process running, collect the core file immediately for further analyzing and locating the fault.
+
+  - The OS performance is affected, especially when errors occur frequently.
+
+  - The OS disk space will be occupied by core files. Therefore, after core files are discovered, locate and rectify the errors as soon as possible. The OS is delivered with a core dump mechanism. If this mechanism is enabled, core files are generated for each core dump, which has an impact on the OS performance and disk space.
+
+  - Set the path for generating core files. Modify the **/proc/sys/kernel/core_pattern** file.
+
+    ```
+    [root@openeuler123 mnt]# cat /proc/sys/kernel/core_pattern
+    /data/jenkins/workspace/MogDBInstall/dbinstall/cluster/corefile/core-%e-%p-%t
+    ```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/1-1-stored-procedure.md b/product/en/docs-mogdb/v3.0/developer-guide/1-1-stored-procedure.md
new file mode 100644
index 0000000000000000000000000000000000000000..8ca0fae50f048d3a248f97b320dd97f7722446d2
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/1-1-stored-procedure.md
@@ -0,0 +1,16 @@
+---
+title: Stored Procedure
+summary: Stored Procedure
+author: Guo Huan
+date: 2021-03-04
+---
+
+# Stored Procedure
+
+In MogDB, business rules and logics are saved as stored procedures.
+
+A stored procedure is a combination of SQL and PL/pgSQL. Stored procedures can move the code that executes business rules from applications to databases. Therefore, the code storage can be used by multiple programs at a time.
+
+For details about how to create and call a stored procedure, see [CREATE PROCEDURE](53-CREATE-PROCEDURE).
+
+The application methods for PL/pgSQL functions mentioned in [User-defined Functions](user-defined-functions) are similar to those for stored procedures. For details, please refer to [PL/pgSQL-SQL Procedural Language](1-1-plpgsql-overview) section, unless otherwise specified, the contents apply to stored procedures and user-defined functions.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/1-AI-features-overview.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/1-AI-features-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..23509eddd8b0c8b2a2151688327c2465b85849ef
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/1-AI-features-overview.md
@@ -0,0 +1,13 @@
+---
+title: Overview
+summary: Overview
+author: Guo Huan
+date: 2021-05-19
+---
+
+# Overview
+
+The history of artificial intelligence (AI) can be dated back to as early as the 1950s, even longer than the history of the database development. However, the AI technology has not been applied on a large scale for a long time due to various objective factors, and even experienced several obvious troughs. With the further development of information technologies in recent years, factors that restrict the AI development have been gradually weakened, and the AI, big data, and cloud computing (ABC) technologies are born. The combination of AI and databases has been a trending research topic in the industry in recent years. Our database team has participated in the exploration of this domain earlier and achieved phased achievements. The AI feature submodule **dbmind** is more independent than other database components. It can be divided into AI4DB and DB4AI.
+
+- AI4DB uses AI technologies to optimize database execution performance as well as achieve autonomy and O&M free. It includes self-tuning, self-diagnosis, self-security, self-O&M, and self-healing.
+- DB4AI streamlines the E2E process from databases to AI applications and unifies the AI technology stack to achieve out-of-the-box, high performance, and cost saving. For example, you can use SQL-like statements to use functions such as recommendation system, image retrieval, and time series forecasting to maximize the advantages of MogDB, such as high parallelism and column store.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-1-ai-query-time-forecasting-overview.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-1-ai-query-time-forecasting-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..feecfb2dcb7c94ed003e23d3a1a36c2bae5e29f4
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-1-ai-query-time-forecasting-overview.md
@@ -0,0 +1,12 @@
+---
+title: Overview
+summary: Overview
+author: Guo Huan
+date: 2021-05-19
+---
+
+# Overview
+
+Predictor is a query time prediction tool that leverages machine learning and has online learning capability. By continuously learning the historical execution information collected in the database, Predictor can predict the execution time of a plan.
+
+To use this tool, you must start the Python process AI Engine for model training and inference.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-2-environment-deployment.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-2-environment-deployment.md
new file mode 100644
index 0000000000000000000000000000000000000000..ecfc23a2e893ec55250e68dd225f6daf16eeef70
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-2-environment-deployment.md
@@ -0,0 +1,203 @@
+---
+title: Environment Deployment
+summary: Environment Deployment
+author: Guo Huan
+date: 2021-05-19
+---
+
+# Environment Deployment
+
+## Prerequisites
+
+MogDB is in the normal state. The user has logged in to MogDB with an authenticated identity. The executed SQL syntax is correct and no error is reported. In the historical performance data window, the number of MogDB concurrent tasks is stable, the structure and number of tables remain unchanged, the data volume changes smoothly, and the GUC parameters related to query performance remain unchanged. During prediction, the model has been trained and converged. The running environment of the AIEngine is stable.
+
+## Request Example
+
+The AIEngine process communicates with the kernel process using HTTPS. An example request is as follows:
+
+```bash
+curl -X POST -d '{"modelName":"modelname"}' -H 'Content-Type: application/json' 'https://IP-address:port/request-API'
+```
+
+**Table 1** AIEngine external APIs
+
+| Request API    | Description                                 |
+| :------------- | :------------------------------------------ |
+| /check         | Checks whether a model is properly started. |
+| /configure     | Sets model parameters.                      |
+| /train         | Trains a model.                             |
+| /track_process | Views model training logs.                  |
+| /setup         | Loads historical models.                    |
+| /predict       | Predicts a model.                           |
+
+## Generating Certificates
+
+Before using the prediction function, you need to use OpenSSL to generate certificates required for authentication between the communication parties, ensuring communication security.
+
+1. Set up a certificate generation environment. The certificate file is stored in **$GAUSSHOME/CA**.
+
+   - Copy the certificate generation script and related files.
+
+   ```bash
+   cp path_to_predictor/install/ssl.sh $GAUSSHOME/
+   cp path_to_predictor/install/ca_ext.txt $GAUSSHOME/
+   ```
+
+   - Copy the configuration file **openssl.cnf** to **$GAUSSHOME**.
+
+   ```bash
+   cp $GAUSSHOME/share/om/openssl.cnf  $GAUSSHOME/
+   ```
+
+   - Modify the configuration parameters in **openssl.conf**.
+
+   ```bash
+   dir  = $GAUSSHOME/CA/demoCA
+   default_md      = sha256
+   ```
+
+   - The certificate generation environment is ready.
+
+2. Generate a certificate and private key.
+
+   ```bash
+   cd $GAUSSHOME
+   sh ssl.sh
+   ```
+
+   - Set the password as prompted, for example, **Test@123**.
+
+   - The password must contain at least eight characters of at least three different types.
+
+   ```bash
+   Please enter your password:
+   ```
+
+   - Set the options as prompted.
+
+   ```bash
+   Certificate Details:
+           Serial Number: 1 (0x1)
+           Validity
+               Not Before: May 15 08:32:44 2020 GMT
+               Not After : May 15 08:32:44 2021 GMT
+           Subject:
+               countryName               = CN
+               stateOrProvinceName       = SZ
+               organizationName          = HW
+               organizationalUnitName    = GS
+               commonName                = CA
+           X509v3 extensions:
+               X509v3 Basic Constraints:
+                   CA:TRUE
+   Certificate is to be certified until May 15 08:32:44 2021 GMT (365 days)
+   Sign the certificate? [y/n]:y
+   1 out of 1 certificate requests certified, commit? [y/n]y
+   ```
+
+   - Enter the IP address for starting the AIEngine, for example, **127.0.0.1**.
+
+   ```bash
+   Please enter your aiEngine IP: 127.0.0.1
+   ```
+
+   - Set the options as prompted.
+
+   ```bash
+   Certificate Details:
+           Serial Number: 2 (0x2)
+           Validity
+               Not Before: May 15 08:38:07 2020 GMT
+               Not After : May 13 08:38:07 2030 GMT
+           Subject:
+               countryName               = CN
+               stateOrProvinceName       = SZ
+               organizationName          = HW
+               organizationalUnitName    = GS
+               commonName                = 127.0.0.1
+           X509v3 extensions:
+               X509v3 Basic Constraints:
+                   CA:FALSE
+   Certificate is to be certified until May 13 08:38:07 2030 GMT (3650 days)
+   Sign the certificate? [y/n]:y
+   1 out of 1 certificate requests certified, commit? [y/n]y
+   ```
+
+   - Enter the IP address for starting MogDB, for example, **127.0.0.1**.
+
+   ```bash
+   Please enter your mog IP: 127.0.0.1
+   ```
+
+   - Set the options as prompted.
+
+   ```bash
+   Certificate Details:
+           Serial Number: 3 (0x3)
+           Validity
+               Not Before: May 15 08:41:46 2020 GMT
+               Not After : May 13 08:41:46 2030 GMT
+           Subject:
+               countryName               = CN
+               stateOrProvinceName       = SZ
+               organizationName          = HW
+               organizationalUnitName    = GS
+               commonName                = 127.0.0.1
+           X509v3 extensions:
+               X509v3 Basic Constraints:
+                   CA:FALSE
+   Certificate is to be certified until May 13 08:41:46 2030 GMT (3650 days)
+   Sign the certificate? [y/n]:y
+   1 out of 1 certificate requests certified, commit? [y/n]y
+   ```
+
+   - The related certificate and key have been generated. The content in **$GAUSSHOME/CA** is as follows:
+
+   ![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/environment-deployment-1.png)
+
+## Setting Up the Environment
+
+1. Copy the tool code folder to the target environment.
+
+   - Assume that the installation directory is **$INSTALL_FOLDER**.
+
+   - Assume that the destination directory is **/home/ai_user**.
+
+   ```bash
+   scp -r $INSTALL_FOLDER/bin/dbmind/predictor  ai_user@127.0.0.1:path_to_Predictor
+   ```
+
+2. Copy the CA certificate folder to a directory in the AIEngine environment.
+
+   ```bash
+   cp -r $GAUSSHOME/CA  ai_user@127.0.0.1:path_to_CA
+   ```
+
+3. Install the **predictor/install/requirements(-gpu).txt** tool.
+
+   ```bash
+   With GPU: pip install -r requirements-gpu.txt
+   Without GPU: pip install -r requirements.txt
+   ```
+
+## Starting AIEngine
+
+1. Switch to the AIEngine environment (that is, copy the target environment **ai_user** of the predictor).
+
+   Set parameters in **predictor/python/settings.py**.
+
+   ```bash
+   DEFAULT_FLASK_SERVER_HOST = '127.0.0.1' (running IP address of AIEngine)
+   DEFAULT_FLASK_SERVER_PORT = '5000' (running port number of AIEngine)
+   PATH_SSL = "path_to_CA" (CA folder path)
+   ```
+
+2. Run the startup script of AIEngine.
+
+   ```bash
+   python path_to_Predictor/python/run.py
+   ```
+
+   In this case, the AIEngine keeps enabled on the corresponding port and waits for the request of the time prediction function from the kernel.
+
+   For details about how to initiate a time prediction command from the kernel, see the [Usage Guide](2-3-usage-guide).
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-3-usage-guide.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-3-usage-guide.md
new file mode 100644
index 0000000000000000000000000000000000000000..03e412ac9a9968c21f47cb2a5be4808c9e3adc0a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-3-usage-guide.md
@@ -0,0 +1,214 @@
+---
+title: Usage Guide
+summary: Usage Guide
+author: Guo Huan
+date: 2021-05-19
+---
+
+# Usage Guide
+
+## Data Collection
+
+1. Enable data collection.
+
+   a. Set parameters related to the ActiveSQL operator.
+
+      ```bash
+      enable_resource_track=on
+      resource_track_level=operator
+      enable_resource_record=on
+      resource_track_cost=10 (The default value is 100000.)
+      ```
+
+      > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+      >
+      > - The value of **resource_track_cost** must be smaller than the total query cost of the information to be collected. Only the information that meets the requirements can be collected.
+      > - Cgroup functions are available.
+
+   b. Collect information.
+
+      Execute the service query statement.
+
+      View data collected in real time.
+
+      ```sql
+      select * from gs_wlm_plan_operator_history;
+      ```
+
+      Expected result: All jobs that meet **resource_track_duration** and **resource_track_cost** are collected.
+
+2. Disable data collection.
+
+   a. Set any of the following parameters related to the ActiveSQL operator.
+
+      ```bash
+      enable_resource_track=off
+      resource_track_level=none
+      resource_track_level=query
+      ```
+
+   b. Execute the service query statement.
+
+      Wait for 3 minutes and check the data on the current node.
+
+      ```sql
+      select * from gs_wlm_plan_operator_info;
+      ```
+
+      Expected result: No new data is added to the tables and views.
+
+3. Persist data.
+
+   a. Set parameters related to the ActiveSQL operator.
+
+      ```bash
+      enable_resource_track=on
+      resource_track_level=operator
+      enable_resource_record=on
+      resource_track_duration=0 (The default value is 60s.)
+      resource_track_cost=10 (The default value is 100000.)
+      ```
+
+      > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+      >
+      > - The value of **resource_track_cost** must be smaller than the total query cost of the information to be collected. Only the information that meets the requirements can be collected.
+      > - Cgroup functions are available.
+
+   b. Execute the service query statement.
+
+      Wait for 3 minutes and check the data on the current node.
+
+      ```sql
+      select * from gs_wlm_plan_operator_info;
+      ```
+
+      Expected result: All jobs that meet **resource_track_duration** and **resource_track_cost** are collected.
+
+## Model Management (System Administrators)
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> Model management operations can be performed only when the database is normal.
+
+1. Add a new model.
+
+   INSERT INTO gs_opt_model values('……');
+
+   Example:
+
+   ```sql
+   INSERT INTO gs_opt_model values('rlstm', 'model_name', 'datname', '127.0.0.1', 5000, 2000, 1, -1, 64, 512, 0 , false, false, '{S, T}', '{0,0}', '{0,0}', 'Text');
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+   >
+   > - For details about model parameter settings, see [GS_OPT_MODEL](GS_OPT_MODEL).
+   > - Currently, only **rlstm** is supported in the **template_name** column.
+   > - The values in the **datname** column must be the same as those in the database used for model usage and training. Otherwise, the model cannot be used.
+   > - The values in the **model_name** column must meet the **unique** constraint.
+   > - For details about other parameter settings, see [Best Practices](2-4-best-practices).
+
+2. Modify model parameters.
+
+   ```sql
+   UPDATE gs_opt_model SET <attribute> = <value> WHERE model_name = <target_model_name>;
+   ```
+
+3. Delete a model.
+
+   ```sql
+   DELETE FROM gs_opt_model WHERE model_name = <target_model_name>;
+   ```
+
+4. Query the existing model and its status.
+
+   ```sql
+   SELECT * FROM gs_opt_model;
+   ```
+
+## Model Training (System Administrators)
+
+1. Add models and modify model parameters by following the steps in Model Management (System Administrators).
+
+   Example:
+
+   Add a mode.
+
+   ```sql
+   INSERT INTO gs_opt_model values('rlstm', 'default', 'postgres', '127.0.0.1', 5000, 2000, 1, -1, 64, 512, 0 , false, false, '{S, T}', '{0,0}', '{0,0}', 'Text');
+   ```
+
+   Modify training parameters.
+
+   ```sql
+   UPDATE gs_opt_model SET <attribute> = <value> WHERE model_name = <target_model_name>;
+   ```
+
+2. Check that the database status is normal and historical data is collected properly before you perform the following operations:
+
+   Delete the original encoding data.
+
+   ```sql
+   DELETE FROM gs_wlm_plan_encoding_table;
+   ```
+
+   To encode data, specify the database name.
+
+   ```sql
+   SELECT gather_encoding_info('postgres');
+   ```
+
+   Start training.
+
+   ```sql
+   SELECT model_train_opt('rlstm', 'default');
+   ```
+
+3. View the model training status.
+
+   ```sql
+   SELECT * FROM track_model_train_opt('rlstm', 'default');
+   ```
+
+   The URL used by TensorBoard is returned.
+
+   ![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/usage-guide-1.png)
+
+   Access the URL to view the model training status.
+
+   ![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/usage-guide-2.png)
+
+## Model Prediction
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - Model prediction can be performed only when the database status is normal and the specified model has been trained and converged.
+> - Currently, the labels of model training parameters must contain the **S** label so that the **p-time** value can be displayed in **EXPLAIN**.
+>   Example: INSERT INTO gs_opt_model values('rlstm', 'default', 'postgres', '127.0.0.1', 5000, 1000, 1, -1, 50, 500, 0 , false, false, '{**S**, T}', '{0,0}', '{0,0}', 'Text');
+
+Call EXPLAIN.
+
+   ```sql
+   explain (analyze on, predictor <model_name>)
+   SELECT ...
+   ```
+
+Expected result:
+
+   ```bash
+   Example: Row Adapter  (cost=110481.35..110481.35 rows=100 p-time=99..182 width=100) (actual time=375.158..375.160 rows=2 loops=1)
+   The p-time column indicates the predicted value of the label.
+   ```
+
+## Other Functions
+
+1. Check whether the AI Engine can be connected.
+
+   ```sql
+   mogdb=# select check_engine_status('aiEngine-ip-address',running-port);
+   ```
+
+2. Check the path for storing model logs on the AI Engine.
+
+   ```sql
+   mogdb=# select track_model_train_opt('template_name', 'model_name');
+   ```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-4-best-practices.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-4-best-practices.md
new file mode 100644
index 0000000000000000000000000000000000000000..40dcde4dcfdf188e5fd28d70891e5532a6deeeb3
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-4-best-practices.md
@@ -0,0 +1,32 @@
+---
+title: Best Practices
+summary: Best Practices
+author: Guo Huan
+date: 2021-05-19
+---
+
+# Best Practices
+
+For details about the parameters, see [GS_OPT_MODEL](GS_OPT_MODEL).
+
+**Table 1**
+
+| Model Parameter  | Recommended Value                                            |
+| :--------------- | :----------------------------------------------------------- |
+| template_name    | rlstm                                                        |
+| model_name       | The value can be customized, for example, **open_ai**. The value must meet the unique constraint. |
+| datname          | Name of the database to be served, for example, **postgres**. |
+| ip               | IP address of the AI Engine, for example, **127.0.0.1**.     |
+| port             | AI Engine listening port number, for example, **5000**.      |
+| max_epoch        | Iteration times. A large value is recommended to ensure the convergence effect, for example, **2000**. |
+| learning_rate    | (0, 1] is a floating-point number. A large learning rate is recommended to accelerate convergence. |
+| dim_red          | Number of feature values to be reduced.<br/>**-1**: Do not use PCA for dimension reduction. All features are supported.<br/>Floating point number in the range of (0, 1]: A smaller value indicates a smaller training dimension and a faster convergence speed, but affects the training accuracy. |
+| hidden_units     | If the feature value dimension is high, you are advised to increase the value of this parameter to increase the model complexity. For example, set this parameter to **64**, **128**, and so on. |
+| batch_size       | You are advised to increase the value of this parameter based on the amount of encoded data to accelerate model convergence. For example, set this parameter to **256**, **512**, and so on. |
+| Other parameters | See [GS_OPT_MODEL](GS_OPT_MODEL).                            |
+
+Recommended parameter settings:
+
+```sql
+INSERT INTO gs_opt_model values('rlstm', 'open_ai', 'postgres', '127.0.0.1', 5000, 2000, 1, -1, 64, 512, 0, false, false, '{S, T}', '{0,0}', '{0,0}', 'Text');
+```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-5-faqs.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-5-faqs.md
new file mode 100644
index 0000000000000000000000000000000000000000..79a7dd5a453a7cf947d0346b2822d5551e6d8336
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-5-faqs.md
@@ -0,0 +1,35 @@
+---
+title: FAQs
+summary: FAQs
+author: Guo Huan
+date: 2021-05-19
+---
+
+# FAQs
+
+## AI Engine Configuration
+
+- **AI Engine failed to be started**: Check whether the IP address and port are available and whether the CA certificate path exists.
+- **AI Engine does not respond**: Check whether the CA certificates of the two communication parties are consistent.
+- **Training and test failure**: Check whether the path for saving the model files exists and whether the training prediction file is correctly downloaded.
+- **Changing the AI Engine IP address**: Regenerate the certificate by following the steps in [Generating Certificates](2-2-environment-deployment#generating-certificates). Enter the new IP address in Generate a certificate and private key.
+
+## Database Internal Errors
+
+Problem: AI Engine connection failed.
+
+```
+ERROR:  AI engine connection failed.
+CONTEXT:  referenced column: model_train_opt
+```
+
+Solution: Check whether the AI Engine is started or restarted properly. Check whether the CA certificates of the communication parties are consistent. Check whether the IP address and port number in the model configuration match.
+
+Problem: The model does not exist.
+
+```
+ERROR:  OPT_Model not found for model name XXX
+CONTEXT:  referenced column: track_model_train_opt
+```
+
+Solution: Check whether [GS_OPT_MODEL](GS_OPT_MODEL) contains the model specified in the **model_name** column in the statement. If the error is reported when the prediction function is used, check whether the model has been trained.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-1-x-tuner-overview.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-1-x-tuner-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..118476296311abb940f5b068d87f16ad6bbb4f81
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-1-x-tuner-overview.md
@@ -0,0 +1,10 @@
+---
+title: Overview
+summary: Overview
+author: Guo Huan
+date: 2021-05-19
+---
+
+# Overview
+
+X-Tuner is a parameter tuning tool integrated into databases. It uses AI technologies such as deep reinforcement learning and global search algorithms to obtain the optimal database parameter settings without manual intervention. This function is not forcibly deployed with the database environment. It can be independently deployed and run without the database installation environment.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-2-preparations.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-2-preparations.md
new file mode 100644
index 0000000000000000000000000000000000000000..25a6791024ed4d764d878c9cb3e9e44c0f1ccdef
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-2-preparations.md
@@ -0,0 +1,227 @@
+---
+title: Preparations
+summary: Preparations
+author: Guo Huan
+date: 2021-10-21
+---
+
+# Preparations
+
+<br/>
+
+## Prerequisites and Precautions
+
+- The database status is normal; the client can be properly connected; and data can be imported to the database. As a result, the optimization program can perform the benchmark test for optimization effect.
+- To use this tool, you need to specify the user who logs in to the database. The user who logs in to the database must have sufficient permissions to obtain sufficient database status information.
+- If you log in to the database host as a Linux user, add **$GAUSSHOME/bin** to the **PATH** environment variable so that you can directly run database O&M tools, such as gsql, gs_guc, and gs_ctl.
+- The recommended Python version is Python 3.6 or later. The required dependency has been installed in the operating environment, and the optimization program can be started properly. You can install a Python 3.6+ environment independently without setting it as a global environment variable. You are not advised to install the tool as the root user. If you install the tool as the root user and run the tool as another user, ensure that you have the read permission on the configuration file.
+- This tool can run in three modes. In **tune** and **train** modes, you need to configure the benchmark running environment and import data. This tool will iteratively run the benchmark to check whether the performance is improved after the parameters are modified.
+- In **recommend** mode, you are advised to run the command when the database is executing the workload to obtain more accurate real-time workload information.
+- By default, this tool provides benchmark running script samples of TPC-C, TPC-H, TPC-DS, and sysbench. If you use the benchmarks to perform pressure tests on the database system, you can modify or configure the preceding configuration files. To adapt to your own service scenarios, you need to compile the script file that drives your customized benchmark based on the **template.py** file in the **benchmark** directory.
+
+<br/>
+
+## Principles
+
+The tuning program is a tool independent of the database kernel. The usernames and passwords for the database and instances are required to control the benchmark performance test of the database. Before starting the tuning program, ensure that the interaction in the test environment is normal, the benchmark test script can be run properly, and the database can be connected properly.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** If the parameters to be tuned include the parameters that take effect only after the database is restarted, the database will be restarted multiple times during the tuning. Exercise caution when using **train** and **tune** modes if the database is running jobs.
+
+X-Tuner can run in any of the following modes:
+
+- **recommend**: Log in to the database using the specified user name, obtain the feature information about the running workload, and generate a parameter recommendation report based on the feature information. Report improper parameter settings and potential risks in the current database. Output the currently running workload behavior and characteristics. Output the recommended parameter settings. In this mode, the database does not need to be restarted. In other modes, the database may need to be restarted repeatedly.
+- **train**: Modify parameters and execute the benchmark based on the benchmark information provided by users. The reinforcement learning model is trained through repeated iteration so that you can load the model in **tune** mode for optimization.
+- **tune**: Use an optimization algorithm to tune database parameters. Currently, two types of algorithms are supported: deep reinforcement learning and global search algorithm (global optimization algorithm). The deep reinforcement learning mode requires **train** mode to generate the optimized model after training. However, the global search algorithm does not need to be trained in advance and can be directly used for search and optimization.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** If the deep reinforcement learning algorithm is used in **tune** mode, a trained model must be available, and the parameters for training the model must be the same as those in the parameter list (including max and min) for tuning.
+
+**Figure 1** X-Tuner structure
+
+![x-tuner-structure](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/preparations-1.png)
+
+Figure 1 X-Tuner architecture shows the overall architecture of the X-Tuner. The X-Tuner system can be divided into the following parts:
+
+- DB: The DB_Agent module is used to abstract database instances. It can be used to obtain the internal database status information and current database parameters and set database parameters. The SSH connection used for logging in to the database environment is included on the database side.
+- Algorithm: algorithm package used for optimization, including global search algorithms (such as Bayesian optimization and particle swarm optimization) and deep reinforcement learning (such as DDPG).
+- X-Tuner main logic module: encapsulated by the environment module. Each step is an optimization process. The entire optimization process is iterated through multiple steps.
+- benchmark: a user-specified benchmark performance test script, which is used to run benchmark jobs. The benchmark result reflects the performance of the database system.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** Ensure that the larger the benchmark script score is, the better the performance is. For example, for the benchmark used to measure the overall execution duration of SQL statements, such as TPC-H, the inverse value of the overall execution duration can be used as the benchmark score.
+
+<br/>
+
+## Installing and Running X-Tuner
+
+You can run the X-Tuner in two ways. One is to run the X-Tuner directly through the source code. The other is to install the X-Tuner on the system through the Python setuptools, and then run the **gs_xtuner** command to call the X-Tuner. The following describes two methods of running the X-Tuner.
+
+Method 1: Run the source code directly.
+
+1. Switch to the **xtuner** source code directory. For the openGauss community code, the path is **openGauss-server/src/gausskernel/dbmind/tools/xtuner**. For an installed database system, the source code path is *$GAUSSHOME***/bin/dbmind/xtuner**.
+
+2. You can view the **requirements.txt** file in the current directory. Use the pip package management tool to install the dependency based on the **requirements.txt** file.
+
+   ```bash
+   pip install -r requirements.txt
+   ```
+
+3. After the installation is successful, add the environment variable PYTHONPATH, and then run **main.py**. For example, to obtain the help information, run the following command:
+
+   ```bash
+   cd tuner # Switch to the directory where the main.py entry file is located.
+   export PYTHONPATH='..'  # Add the upper-level directory to the path for searching for packages.
+   python main.py --help  # Obtain help information. The methods of using other functions are similar.
+   ```
+
+Method 2: Install the X-Tuner in the system.
+
+1. You can use the **setup.py** file to install the X-Tuner to the system and then run the **gs_xtuner** command. You need to switch to the root directory of **xtuner**. For details about the directory location, see the preceding description.
+
+2. Run the following command to install the tool in the Python environment using Python setuptools:
+
+   ```bash
+   python setup.py install
+   ```
+
+   If the **bin** directory of Python is added to the *PATH* environment variable, the **gs_xtuner** command can be directly called anywhere.
+
+3. For example, to obtain the help information, run the following command:
+
+   ```bash
+   gs_xtuner --help
+   ```
+
+<br/>
+
+## Description of the X-Tuner Configuration File
+
+Before running the X-Tuner, you need to load the configuration file. The default path of the configuration file is tuner/xtuner.conf. You can run the **gs_xtuner -help** command to view the absolute path of the configuration file that is loaded by default.
+
+```
+...
+ -x TUNER_CONFIG_FILE, --tuner-config-file TUNER_CONFIG_FILE
+                        This is the path of the core configuration file of the
+                        X-Tuner. You can specify the path of the new
+                        configuration file. The default path is /path/to/xtuner/xtuner.conf.
+                        You can modify the configuration file to control the
+                        tuning process.
+...
+```
+
+You can modify the configuration items in the configuration file as required to instruct the X-Tuner to perform different actions. For details about the configuration items in the configuration file, see Table 2 in [Command Reference](3-5-command-reference). If you need to change the loading path of the configuration file, you can specify the path through the **-x** command line option.
+
+<br/>
+
+## Benchmark Selection and Configuration
+
+The benchmark drive script is stored in the benchmark subdirectory of the X-Tuner. X-Tuner provides common benchmark driver scripts, such as TPC-C and TPC-H. The X-Tuner invokes the **get_benchmark_instance()** command in the benchmark/__init__.py file to load different benchmark driver scripts and obtain benchmark driver instances. The format of the benchmark driver script is described as follows:
+
+- Name of the driver script: name of the benchmark. The name is used to uniquely identify the driver script. You can specify the benchmark driver script to be loaded by setting the **benchmark_script** configuration item in the configuration file of the X-Tuner.
+- The driver script contains the *path* variable, *cmd* variable, and the **run** function.
+
+The following describes the three elements of the driver script:
+
+1. *path*: path for saving the benchmark script. You can modify the path in the driver script or specify the path by setting the **benchmark_path** configuration item in the configuration file.
+
+2. *cmd*: command for executing the benchmark script. You can modify the command in the driver script or specify the command by setting the **benchmark_cmd** configuration item in the configuration file. Placeholders can be used in the text of cmd to obtain necessary information for running cmd commands. For details, see the TPC-H driver script example. These placeholders include:
+
+   - {host}: IP address of the database host machine
+   - {port}: listening port number of the database instance
+   - {user}: user name for logging in to the database
+   - {password}: password of the user who logs in to the database system
+   - {db}: name of the database that is being optimized
+
+3. **run** function: The signature of this function is as follows:
+
+   ```
+   def run(remote_server, local_host) -> float:
+   ```
+
+   The returned data type is float, indicating the evaluation score after the benchmark is executed. A larger value indicates better performance. For example, the TPC-C test result tpmC can be used as the returned value, the inverse number of the total execution time of all SQL statements in TPC-H can also be used as the return value. A larger return value indicates better performance.
+
+   The *remote_server* variable is the shell command interface transferred by the X-Tuner program to the remote host (database host machine) used by the script. The *local_host* variable is the shell command interface of the local host (host where the X-Tuner script is executed) transferred by the X-Tuner program. Methods provided by the preceding shell command interface include:
+
+   ```
+   exec_command_sync(command, timeout)
+   Function: This method is used to run the shell command on the host.
+   Parameter list:
+   command: The data type can be str, and the element can be a list or tuple of the str type. This parameter is optional.
+   timeout: The timeout interval for command execution in seconds. This parameter is optional.
+   Return value:
+   Returns 2-tuple (stdout and stderr). stdout indicates the standard output stream result, and stderr indicates the standard error stream result. The data type is str.
+   ```
+
+   ```
+   exit_status
+   Function: This attribute indicates the exit status code after the latest shell command is executed.
+   Note: Generally, if the exit status code is 0, the execution is normal. If the exit status code is not 0, an error occurs.
+   ```
+
+Benchmark driver script example:
+
+1. TPC-C driver script
+
+   ```bash
+   from tuner.exceptions import ExecutionError
+
+   # WARN: You need to download the benchmark-sql test tool to the system,
+   # replace the PostgreSQL JDBC driver with the openGauss driver,
+   # and configure the benchmark-sql configuration file.
+   # The program starts the test by running the following command:
+   path = '/path/to/benchmarksql/run' # Path for storing the TPC-C test script benchmark-sql
+   cmd = "./runBenchmark.sh props.gs"  # Customize a benchmark-sql test configuration file named props.gs.
+
+   def run(remote_server, local_host):
+       # Switch to the TPC-C script directory, clear historical error logs, and run the test command.
+        # You are advised to wait for several seconds because the benchmark-sql test script generates the final test report through a shell script. The entire process may be delayed.
+       # To ensure that the final tpmC value report can be obtained, wait for 3 seconds.
+       stdout, stderr = remote_server.exec_command_sync(['cd %s' % path, 'rm -rf benchmarksql-error.log', cmd, 'sleep 3'])
+       # If there is data in the standard error stream, an exception is reported and the system exits abnormally.
+       if len(stderr) > 0:
+           raise ExecutionError(stderr)
+
+       # Find the final tpmC result.
+       tpmC = None
+       split_string = stdout.split()  # Split the standard output stream result.
+       for i, st in enumerate(split_string):
+            # In the benchmark-sql of version 5.0, the value of tpmC is the last two digits of the keyword (NewOrders). In normal cases, the value of tpmC is returned after the keyword is found.
+           if "(NewOrders)" in st:
+               tpmC = split_string[i + 2]
+               break
+       stdout, stderr = remote_server.exec_command_sync(
+           "cat %s/benchmarksql-error.log" % path)
+       nb_err = stdout.count("ERROR:")  # Check whether errors occur during the benchmark running and record the number of errors.
+       return float(tpmC) - 10 * nb_err  # The number of errors is used as a penalty item, and the penalty coefficient is 10. A higher penalty coefficient indicates a larger number of errors.
+
+   ```
+
+2. TPC-H driver script
+
+   ```bash
+   import time
+
+   from tuner.exceptions import ExecutionError
+
+   # WARN: You need to import data into the database and SQL statements in the following path will be executed.
+   # The program automatically collects the total execution duration of these SQL statements.
+   path = '/path/to/tpch/queries'  # Directory for storing SQL scripts used for the TPC-H test
+   cmd = "gsql -U {user} -W {password} -d {db} -p {port} -f {file}"  # The command for running the TPC-H test script. Generally, gsql -f script file is used.
+
+   def run(remote_server, local_host):
+       # Traverse all test case file names in the current directory.
+       find_file_cmd = "find . -type f -name '*.sql'"
+       stdout, stderr = remote_server.exec_command_sync(['cd %s' % path, find_file_cmd])
+       if len(stderr) > 0:
+           raise ExecutionError(stderr)
+       files = stdout.strip().split('\n')
+       time_start = time.time()
+       for file in files:
+           # Replace {file} with the file variable and run the command.
+           perform_cmd = cmd.format(file=file)
+           stdout, stderr = remote_server.exec_command_sync(['cd %s' % path, perform_cmd])
+           if len(stderr) > 0:
+               print(stderr)
+       # The cost is the total execution duration of all test cases.
+       cost = time.time() - time_start
+       # Use the inverse number to adapt to the definition of the run function. The larger the returned result is, the better the performance is.
+       return - cost
+   ```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-3-examples.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-3-examples.md
new file mode 100644
index 0000000000000000000000000000000000000000..311ccc689907c8df58c134dce8f0bda0b2fcae8d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-3-examples.md
@@ -0,0 +1,151 @@
+---
+title: Examples
+summary: Examples
+author: Guo Huan
+date: 2021-05-19
+---
+
+# Examples
+
+X-Tuner supports three modes: recommend mode for obtaining parameter diagnosis reports, train mode for training reinforcement learning models, and tune mode for using optimization algorithms. The preceding three modes are distinguished by command line parameters, and the details are specified in the configuration file.
+
+## Configuring the Database Connection Information
+
+Configuration items for connecting to a database in the three modes are the same. You can enter the detailed connection information in the command line or in the JSON configuration file. Both methods are described as follows:
+
+1. Entering the connection information in the command line
+
+   Input the following options: **-db-name -db-user -port -host -host-user**. The **-host-ssh-port** is optional. The following is an example:
+
+   ```
+   gs_xtuner recommend --db-name postgres --db-user omm --port 5678 --host 192.168.1.100 --host-user omm
+   ```
+
+2. Entering the connection information in the JSON configuration file
+
+   Assume that the file name is **connection.json**. The following is an example of the JSON configuration file:
+
+   ```
+   {
+     "db_name": "postgres",  # Database name
+     "db_user": "dba",       # Username for logging in to the database
+     "host": "127.0.0.1",    # IP address of the database host
+     "host_user": "dba",     # Username for logging in to the database host
+     "port": 5432,           # Listening port number of the database
+     "ssh_port": 22          # SSH listening port number of the database host
+   }
+   ```
+
+   Input **-f connection.json**.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** To prevent password leakage, the configuration file and command line parameters do not contain password information by default. After you enter the preceding connection information, the program prompts you to enter the database password and the OS login password in interactive mode.
+
+## Example of Using recommend Mode
+
+The configuration item **scenario** takes effect for recommend mode. If the value is **auto**, the workload type is automatically detected.
+
+Run the following command to obtain the diagnosis result:
+
+```
+
+gs_xtuner recommend -f connection.json
+
+```
+
+The diagnosis report is generated as follows:
+
+**Figure 1** Report generated in recommend mode
+
+![report-generated-in-recommend-mode](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/examples-1.png)
+
+In the preceding report, the database parameter configuration in the environment is recommended, and a risk warning is provided. The report also generates the current workload features. The following features are for reference:
+
+- **temp_file_size**: number of generated temporary files. If the value is greater than 0, the system uses temporary files. If too many temporary files are used, the performance is poor. If possible, increase the value of **work_mem**.
+- **cache_hit_rate**: cache hit ratio of **shared_buffer**, indicating the cache efficiency of the current workload.
+- **read_write_ratio**: read/write ratio of database jobs.
+- **search_modify_ratio**: ratio of data query to data modification of a database job.
+- **ap_index**: AP index of the current workload. The value ranges from 0 to 10. A larger value indicates a higher preference for data analysis and retrieval.
+- **workload_type**: workload type, which can be AP, TP, or HTAP based on database statistics.
+- **checkpoint_avg_sync_time**: average duration for refreshing data to the disk each time when the database is at the checkpoint, in milliseconds.
+- **load_average**: average load of each CPU core in 1 minute, 5 minutes, and 15 minutes. Generally, if the value is about 1, the current hardware matches the workload. If the value is about 3, the current workload is heavy. If the value is greater than 5, the current workload is too heavy. In this case, you are advised to reduce the load or upgrade the hardware.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** In recommend mode, information in the **pg_stat_database** and **pg_stat_bgwriter**system catalogs in the database is read. Therefore, the database login user must have sufficient permissions. (You are advised to own the administrator permission which can be granted to username using **alter user username sysadmin**.) Some system catalogs keep recording statistics, which may affect load feature identification. Therefore, you are advised to clear the statistics of some system catalogs, run the workload for a period of time, and then use recommend mode for diagnosis to obtain more accurate results. To clear the statistics, run the following command: select pg_stat_reset_shared('bgwriter'); select pg_stat_reset();
+
+## Example of Using train Mode
+
+This mode is used to train the deep reinforcement learning model. The configuration items related to this mode are as follows:
+
+- **rl_algorithm**: algorithm used to train the reinforcement learning model. Currently, this parameter can be set to  **ddpg**.
+
+- **rl_model_path**: path for storing the reinforcement learning model generated after training.
+
+- **rl_steps**: maximum number of training steps in the training process.
+
+- **max_episode_steps**: maximum number of steps in each episode.
+
+- **scenario**: specifies the workload type. If the value is  **auto**, the system automatically determines the workload type. The recommended parameter tuning list varies according to the mode.
+
+- **tuning_list**: specifies the parameters to be tuned. If this parameter is not specified, the list of parameters to be tuned is automatically recommended based on the workload type. If this parameter is specified,  **tuning_list**indicates the path of the tuning list file. The following is an example of the content of a tuning list configuration file.
+
+  ```
+   {
+          "work_mem": {
+             "default": 65536,
+             "min": 65536,
+             "max": 655360,
+             "type": "int",
+             "restart": false
+           },
+           "shared_buffers": {
+             "default": 32000,
+             "min": 16000,
+             "max": 64000,
+             "type": "int",
+             "restart": true
+           },
+           "random_page_cost": {
+             "default": 4.0,
+             "min": 1.0,
+             "max": 4.0,
+             "type": "float",
+             "restart": false
+           },
+           "enable_nestloop": {
+             "default": true,
+             "type": "bool",
+             "restart": false
+           }
+         }
+  ```
+
+After the preceding configuration items are configured, run the following command to start the training:
+
+```
+
+gs_xtuner train -f connection.json
+
+```
+
+After the training is complete, a model file is generated in the directory specified by the  **rl_model_path**configuration item.
+
+## Example of Using tune Mode
+
+The tune mode supports a plurality of algorithms, including a DDPG algorithm based on reinforcement learning (RL), and a Bayesian optimization algorithm and a particle swarm algorithm (PSO) which are both based on a global optimization algorithm (GOP).
+
+The configuration items related to tune mode are as follows:
+
+- **tune_strategy**: specifies the algorithm to be used for optimization. The value can be  **rl**(using the reinforcement learning model),  **gop**(using the global optimization algorithm), or  **auto**(automatic selection). If this parameter is set to  **rl**, RL-related configuration items take effect. In addition to the preceding configuration items that take effect in train mode, the  **test_episode**configuration item also takes effect. This configuration item indicates the maximum number of episodes in the tuning process. This parameter directly affects the execution time of the tuning process. Generally, a larger value indicates longer time consumption.
+- **gop_algorithm**: specifies a global optimization algorithm. The value can be  **bayes** or  **pso**.
+- **max_iterations**: specifies the maximum number of iterations. A larger value indicates a longer search time and better search effect.
+- **particle_nums**: specifies the number of particles. This parameter is valid only for the PSO algorithm.
+- For details about  **scenario** and  **tuning_list**, see the description of train mode.
+
+After the preceding items are configured, run the following command to start tuning:
+
+```
+
+gs_xtuner tune -f connection.json
+
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **CAUTION:** Before using tune and train modes, you need to import the data required by the benchmark, check whether the benchmark can run properly, and back up the current database parameters. To query the current database parameters, run the following command: select name, setting from pg_settings;
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-4-obtaining-help-information.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-4-obtaining-help-information.md
new file mode 100644
index 0000000000000000000000000000000000000000..12f32ef275085145a39b65474fc5e50fb90cb69e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-4-obtaining-help-information.md
@@ -0,0 +1,51 @@
+---
+title: Obtaining Help Information
+summary: Obtaining Help Information
+author: Guo Huan
+date: 2021-05-19
+---
+
+# Obtaining Help Information
+
+Before starting the tuning program, run the following command to obtain help information:
+
+```bash
+python main.py --help
+```
+
+The command output is as follows:
+
+```bash
+usage: main.py [-h] [-m {train,tune}] [-f CONFIG_FILE] [--db-name DB_NAME]
+[--db-user DB_USER] [--port PORT] [--host HOST]
+[--host-user HOST_USER] [--host-ssh-port HOST_SSH_PORT]
+[--scenario {ap,tp,htap}] [--benchmark BENCHMARK]
+[--model-path MODEL_PATH] [-v]
+
+X-Tuner: a self-tuning toolkit for MogD.
+
+optional arguments:
+-h, --help            show this help message and exit
+-m {train,tune}, --mode {train,tune}
+train a reinforcement learning model or tune by your
+trained model.
+-f CONFIG_FILE, --config-file CONFIG_FILE
+you can pass a config file path or you should manually
+set database information.
+--db-name DB_NAME     database name.
+--db-user DB_USER     database user name.
+--port PORT           database connection port.
+--host HOST           where did your database install on?
+--host-user HOST_USER
+user name of the host where your database installed
+on.
+--host-ssh-port HOST_SSH_PORT
+host ssh port.
+--scenario {ap,tp,htap}
+--benchmark BENCHMARK
+--model-path MODEL_PATH
+the place where you want to save model weights to or
+load model weights from.
+-v, --version
+show version.
+```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-5-command-reference.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-5-command-reference.md
new file mode 100644
index 0000000000000000000000000000000000000000..b91dcea4663c9e5f376972215258148d1f932fc4
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-5-command-reference.md
@@ -0,0 +1,50 @@
+---
+title: Command Reference
+summary: Command Reference
+author: Guo Huan
+date: 2021-05-19
+---
+
+# Command Reference
+
+**Table 1** Command-line Parameter
+
+| Parameter              | Description                                                  | Value Range            |
+| :--------------------- | :----------------------------------------------------------- | :--------------------- |
+| mode                   | Specifies the running mode of the tuning program.            | train, tune, recommend |
+| -tuner-config-file, -x | Path of the core parameter configuration file of X-Tuner. The default path is **xtuner.conf** under the installation directory. | -                      |
+| -db-config-file, -f    | Path of the connection information configuration file used by the optimization program to log in to the database host. If the database connection information is configured in this file, the following database connection information can be omitted. | -                      |
+| -db-name               | Specifies the name of a database to be tuned.                | -                      |
+| -db-user               | Specifies the user account used to log in to the tuned database. | -                      |
+| -port                  | Specifies the database listening port.                       | -                      |
+| -host                  | Specifies the host IP address of the database instance.      | -                      |
+| -host-user             | Specifies the username for logging in to the host where the database instance is located. The database O&M tools, such as **gsql** and **gs_ctl**, can be found in the environment variables of the username. | -                      |
+| -host-ssh-port         | Specifies the SSH port number of the host where the database instance is located. This parameter is optional. The default value is **22**. | -                      |
+| -help, -h              | Returns the help information.                                | -                      |
+| -version, -v           | Returns the current tool version.                            | -                      |
+
+**Table 2** Parameters in the configuration file
+
+| Parameter             | Description        | Value Range          |
+| :-------------------- | :----------------- | :------------------- |
+| logfile               | Path for storing generated logs.                             | -                             |
+| output_tuning_result  | (Optional) Specifies the path for saving the tuning result.  | -                             |
+| verbose               | Whether to print details.                                    | on, off                       |
+| recorder_file         | Path for storing logs that record intermediate tuning information. | -                             |
+| tune_strategy         | Specifies a strategy used in tune mode.                      | rl, gop, auto                 |
+| drop_cache            | Whether to perform drop cache in each iteration. Drop cache can make the benchmark score more stable. If this parameter is enabled, add the login system user to the **/etc/sudoers** list and grant the NOPASSWD permission to the user. (You are advised to enable the NOPASSWD permission temporarily and disable it after the tuning is complete.) | on, off                       |
+| used_mem_penalty_term | Penalty coefficient of the total memory used by the database. This parameter is used to prevent performance deterioration caused by unlimited memory usage. The greater the value is, the greater the penalty is. | Recommended value: 0 ~ 1      |
+| rl_algorithm          | Specifies the RL algorithm.                                  | ddpg                          |
+| rl_model_path         | Path for saving or reading the RL model, including the save directory name and file name prefix. In train mode, this path is used to save the model. In tune mode, this path is used to read the model file. | -                             |
+| rl_steps              | Number of training steps of the deep reinforcement learning algorithm | -                             |
+| max_episode_steps     | Maximum number of training steps in each episode             | -                             |
+| test_episode          | Number of episodes when the RL algorithm is used for optimization | -                             |
+| gop_algorithm         | Specifies a global optimization algorithm.                   | bayes, pso, auto              |
+| max_iterations        | Maximum number of iterations of the global search algorithm. (The value is not fixed. Multiple iterations may be performed based on the actual requirements.) | -                             |
+| particle_nums         | Number of particles when the PSO algorithm is used           | -                             |
+| benchmark_script      | Benchmark driver script. This parameter specifies the file with the same name in the benchmark path to be loaded. Typical benchmarks, such as TPC-C and TPC-H, are supported by default. | tpcc, tpch, tpcds, sysbench … |
+| benchmark_path        | Path for saving the benchmark script. If this parameter is not configured, the configuration in the benchmark drive script is used. | -                             |
+| benchmark_cmd         | Command for starting the benchmark script. If this parameter is not configured, the configuration in the benchmark drive script is used. | -                             |
+| benchmark_period      | This parameter is valid only for **period benchmark**. It indicates the test period of the entire benchmark. The unit is second. | -                             |
+| scenario              | Type of the workload specified by the user.                  | tp, ap, htap                  |
+| tuning_list           | List of parameters to be tuned. For details, see the **share/knobs.json.template** file. | -                             |
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-6-Troubleshooting.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-6-Troubleshooting.md
new file mode 100644
index 0000000000000000000000000000000000000000..df96e0c7367c2bb6ec000afe1d48bfb28d021f51
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-6-Troubleshooting.md
@@ -0,0 +1,14 @@
+---
+title: Troubleshooting
+summary: Troubleshooting
+author: Guo Huan
+date: 2021-05-19
+---
+
+# Troubleshooting
+
+- Failure of connection to the database instance: Check whether the database instance is faulty or the security permissions of configuration items in the **pg_hba.conf** file are incorrectly configured.
+- Restart failure: Check the health status of the database instance and ensure that the database instance is running properly.
+- Dependency installation failure: Upgrade the pip package management tool by running the **python -m pip install -upgrade pip** command.
+- Poor performance of TPC-C jobs: In high-concurrency scenarios such as TPC-C, a large amount of data is modified during pressure tests. Each test is not idempotent, for example, the data volume in the TPC-C database increases, invalid tuples are not cleared using VACUUM FULL, checkpoints are not triggered in the database, and drop cache is not performed. Therefore, it is recommended that the benchmark data that is written with a large amount of data, such as TPC-C, be imported again at intervals (depending on the number of concurrent tasks and execution duration). A simple method is to back up the $PGDATA directory.
+- When the TPC-C job is running, the TPC-C driver script reports the error "TypeError: float() argument must be a string or a number, not 'NoneType'" (**none** cannot be converted to the float type). This is because the TPC-C pressure test result is not obtained. There are many causes for this problem, manually check whether TPC-C can be successfully executed and whether the returned result can be obtained. If the preceding problem does not occur, you are advised to set the delay time of the **sleep** command in the command list in the TPC-C driver script to a larger value.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-1-overview.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-1-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..1fbef2fbfabf26873fa17e2558fbea4e8a7328e4
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-1-overview.md
@@ -0,0 +1,16 @@
+---
+title: Overview
+summary: Overview
+author: Guo Huan
+date: 2021-05-19
+---
+
+# Overview
+
+SQLdiag is a framework for predicting the execution duration of SQL statements in MogDB. The existing prediction technologies are mainly based on model prediction of execution plans. These prediction solutions are applicable only to jobs whose execution plans can be obtained in the OLAP scenarios, and are not useful for quick query such as OLTP or HTAP. Different from the preceding solutions, SQLdiag focuses on the historical SQL statements of databases. Because the execution duration of the database SQL statements in a short time does not vary greatly, SQLdiag can detect instruction sets similar to the entered instructions from the historical data, and predict the SQL statement execution duration based on the SQL vectorization technology and the time series prediction algorithm. This framework has the following benefits:
+
+1. Execution plans do not require instructions. This has no impact on database performance.
+2. The framework is widely used, unlike many other well-targeted algorithms in the industry, for example, they may applicable only to OLTP or OLAP.
+3. The framework is robust and easy to understand. Users can design their own prediction models by simply modifying the framework.
+
+SQLdiag is an SQL statement execution time prediction tool. It predicts the execution time of SQL statements based on the statement logic similarity and historical execution records without obtaining the SQL statement execution plan using a template.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-2-usage-guide.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-2-usage-guide.md
new file mode 100644
index 0000000000000000000000000000000000000000..fdc1f70712e0ec2de44a10016d3f25c9df972430
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-2-usage-guide.md
@@ -0,0 +1,107 @@
+---
+title: Usage Guide
+summary: Usage Guide
+author: Guo Huan
+date: 2021-11-24
+---
+
+# Usage Guide
+
+## Prerequisites
+
+- Ensure that users provide training data.
+- If the user collects training data through the tools provided, the WDR function needs to be enabled, and the parameters involved are **track_stmt_stat_level** and **log_min_duration_statement**, as described in the following section.
+- To ensure the prediction accuracy, the historical statement logs provided by users should be as comprehensive and representative as possible.
+- The Python 3.6+ environment and dependencies have been configured as required.
+
+## Environment Configuration
+
+This function requires Python 3.6+ to run. The required third-party dependency packages are recorded in the **requirements.txt** file, and the dependencies can be installed via the **pip install** command, for example:
+
+```bash
+pip install requirements.txt
+```
+
+## Collecting SQL Statements
+
+This tool requires the user to prepare the data in advance, and the training data are in the following format, with each sample separated by a newline character.
+
+```bash
+SQL,EXECUTION_TIME
+```
+
+The format of the predicted data is as follows:
+
+```bash
+SQL
+```
+
+**SQL** denotes the text of SQL statement and **EXECUTION_TIME** denotes the execution time of SQL statement. Sample data are shown in **train.csv** and **predict.csv** in **sample_data**.
+
+Users can collect training data by themselves in the required format, and the tool also provides a script for automatic collection (load_sql_from_rd), which obtains SQL information based on WDR reports and involves parameters such as **log\_min\_duration\_statement** and **track_stmt_stat_level**.
+
+- **log_min_duration_statement** indicates the slow SQL threshold, if 0 then the full amount is collected (in milliseconds).
+- **track_stmt_stat_level** indicates the level of information capture, it is recommended to set track_stmt_stat_level='L0,L0'
+
+If this parameter is enabled, a certain amount of system resources may be occupied but the usage is generally low. Continuous high-concurrency scenarios may generate less than 5% performance loss. If the database concurrency is low, the performance loss can be ignored.
+
+```bash
+# Use the script to get the training data:
+load_sql_from_wdr.py [-h] --port PORT --start_time START_TIME
+                            --finish_time FINISH_TIME [--save_path SAVE_PATH]
+# For example:
+    python load_sql_from_wdr.py --start_time "2021-04-25 00:00:00" --finish_time "2021-04-26 14:00:00" --port 5432  --save_path ./data.csv
+```
+
+## Procedure
+
+1. Provide historical logs for model training.
+
+2. Perform training and prediction.
+
+   ```bash
+   # Training and prediction based on template:
+       python main.py [train, predict] -f FILE --model template --model-path template_model_path
+   # Training and prediction based on DNN:
+       python main.py [train, predict] -f FILE --model dnn --model-path dnn_model_path
+   ```
+
+## Examples
+
+In the root directory of this tool, run the following commands to achieve the corresponding functions.
+
+Use the provided test data for template training:
+
+```bash
+python main.py train -f ./sample_data/train.csv --model template --model-path ./template
+```
+
+Use the provided test data to make templated predictions:
+
+```bash
+python main.py predict -f ./sample_data/predict.csv --model template --model-path ./template --predicted-file ./result/t_result
+```
+
+Use the provided test data to update the templated model:
+
+```bash
+python main.py finetune -f ./sample_data/train.csv --model template --model-path ./template
+```
+
+Use the provided test data for DNN training:
+
+```bash
+python main.py train -f ./sample_data/train.csv --model dnn --model-path ./dnn_model
+```
+
+Use the provided test data to make DNN predictions:
+
+```bash
+python main.py predict -f ./sample_data/predict.csv --model dnn --model-path ./dnn_model --predicted-file
+```
+
+Use the provided test data to update the DNN model:
+
+```bash
+python main.py finetune -f ./sample_data/train.csv --model dnn --model-path ./dnn_model
+```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-3-obtaining-help-information.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-3-obtaining-help-information.md
new file mode 100644
index 0000000000000000000000000000000000000000..91ec920b59292ec46d0fa019964d1a7261f267a9
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-3-obtaining-help-information.md
@@ -0,0 +1,49 @@
+---
+title: Obtaining Help Information
+summary: Obtaining Help Information
+author: Guo Huan
+date: 2021-05-19
+---
+
+# Obtaining Help Information
+
+Before using the SQLdiag tool, run the following command to obtain help information:
+
+```
+python main.py --help
+```
+
+The command output is as follows:
+
+```
+usage: main.py [-h] [-f CSV_FILE] [--predicted-file PREDICTED_FILE]
+               [--model {template,dnn}] --model-path MODEL_PATH
+               [--config-file CONFIG_FILE]
+               {train,predict,finetune}
+
+SQLdiag integrated by openGauss.
+
+positional arguments:
+  {train,predict,finetune}
+                        The training mode is to perform feature extraction and
+                        model training based on historical SQL statements. The
+                        prediction mode is to predict the execution time of a
+                        new SQL statement through the trained model.
+
+optional arguments:
+  -h, --help            show this help message and exit
+  -f CSV_FILE, --csv-file CSV_FILE
+                        The data set for training or prediction. The file
+                        format is CSV. If it is two columns, the format is
+                        (SQL statement, duration time). If it is three
+                        columns, the format is (timestamp of SQL statement
+                        execution time, SQL statement, duration time).
+  --predicted-file PREDICTED_FILE
+                        The file path to save the predicted result.
+  --model {template,dnn}
+                        Choose the model model to use.
+  --model-path MODEL_PATH
+                        The storage path of the model file, used to read or
+                        save the model file.
+  --config-file CONFIG_FILE
+```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-4-command-reference.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-4-command-reference.md
new file mode 100644
index 0000000000000000000000000000000000000000..56c792569e2b7e04d90a87d1600012587e839ce0
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-4-command-reference.md
@@ -0,0 +1,17 @@
+---
+title: Command Reference
+summary: Command Reference
+author: Guo Huan
+date: 2021-05-19
+---
+
+# Command Reference
+
+**Table 1** Command-line options
+
+| Parameter       | Description                          | Value Range   |
+| :-------------- | :----------------------------------- | :------------ |
+| -f              | Training or prediction file location |               |
+| -predicted-file | Prediction result location           |               |
+| -model          | Model selection                      | template, dnn |
+| -model-path     | Location of the training model       |               |
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-5-troubleshooting.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-5-troubleshooting.md
new file mode 100644
index 0000000000000000000000000000000000000000..442f8d1d07449da92ea7ca5ac3d6c860a438ac6b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-5-troubleshooting.md
@@ -0,0 +1,11 @@
+---
+title: Troubleshooting
+summary: Troubleshooting
+author: Guo Huan
+date: 2021-05-19
+---
+
+# Troubleshooting
+
+- Failure in the training scenario: Check whether the file path of historical logs is correct and whether the file format meets the requirements.
+- Failure in the prediction scenario: Check whether the model path is correct. Ensure that the format of the load file to be predicted is correct.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-1-overview.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-1-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..ce372de191ffea93172541dc73f20e1fff2c43b8
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-1-overview.md
@@ -0,0 +1,14 @@
+---
+title: Overview
+summary: Overview
+author: Guo Huan
+date: 2021-05-19
+---
+
+# Overview
+
+anomaly_detection is an AI tool integrated into MogDB. It can be used to collect database metrics, forecast metric trend changes, analyze root causes of slow SQL statements, and detect and diagnose exceptions. It is a component in the DBMind suite. The information that can be collected consists of **os_exporter**,**database_exporter**, and **wdr**. **os_exporter**includes I/O read, I/O write, I/O wait, CPU usage, memory usage, and disk space occupied by the database data directories.**database_exporter** includes QPS, some key GUC parameters (**work_mem**,**shared_buffers**, and **max_connections**), temporary database files, external processes, and external connections.**wdr**includes the slow SQL text, SQL execution start time, and SQL execution end time. In terms of exception detection, anomaly_detection can forecast the change trend of multiple metrics such as**IO_Read**, **IO_Write**,**IO_Wait**, **CPU_Usage**,**Memory_Usage**, and **Disk_Space**. When detecting that a metric exceeds the manually set threshold in a certain period or at a certain moment in the future, the tool generates an alarm through logs. In terms of slow SQL root cause analysis, the tool periodically obtains slow SQL information from WDR reports, diagnoses the root causes of slow SQL statements, and saves the diagnosis result to log files. In addition, the tool supports interactive slow SQL diagnosis, that is, the tool analyzes the root causes of slow SQL statements entered by users, and sends the result to the user.
+
+anomaly_detection consists of the agent and detector modules. The agent and MogDB database are deployed on the same server. The agent module provides the following functions: 1. Periodically collect database metric data and store the collected data in the buffer queue. 2. Periodically send the data in the buffer queue to the collector submodule of the detector module.
+
+The detector module consists of collector and monitor. The collector submodule communicates with the agent module through HTTP or HTTPS, receives data pushed by the agent module, and stores the data locally. The monitor submodule forecasts the metric change trend and generates alarms based on the local data. In addition, the monitor submodule analyzes the root cause of slow SQL statements based on related information such as the system and WDR reports.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-2-preparations.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-2-preparations.md
new file mode 100644
index 0000000000000000000000000000000000000000..3f0a9a70ad13e42246089b6eb7fe0fa49104a088
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-2-preparations.md
@@ -0,0 +1,173 @@
+---
+title: Preparations
+summary: Preparations
+author: Guo Huan
+date: 2021-05-19
+---
+
+# Preparations
+
+## Prerequisites and Precautions
+
+- The database is running properly.
+- During the running of the tool, if the system time is tampered with, the slow SQL data collection may fail.
+- The tool does not support data collection on the standby node.
+- If you log in to the database host as a Linux user, add **$GAUSSHOME/bin** to the **PATH** environment variable so that you can directly run database O&M tools, such as gsql, gs_guc, and gs_ctl.
+- The recommended Python version is Python 3.6 or later. The required dependency has been installed in the operating environment, and the optimization program can be started properly.
+- This tool consists of the agent and detector. Data is transmitted between the agent and detector in HTTP or HTTPS mode. Therefore, ensure that the agent server can communicate with the detector server properly.
+- The detector module runs the collector and monitor services, which need to be started separately.
+- If HTTPS is used for communication, you need to prepare the CA certificate, and certificates and keys of the agent and detector, and save them to **ca**, **agent**, and **collector** in the **root** directory of the project, respectively. In addition, you need to save the key encryption password to **pwf** of the certificate, and set the permission to **600** to prevent other users from performing read and write operations. You can also use the script in the **share** directory to generate certificates and keys.
+- You are advised to configure your own Python environment to avoid affecting other functions (for example, using miniconda).
+- To analyze the root cause of slow SQL statements, you need the WDR report. In this case, you need to set **track_stmt_stat_level** to **'OFF,L1'** and **log_min_duration_statement** to **3000** (slow SQL threshold, which can be set as required). The unit is ms.
+- If the detecor and database are deployed on the same server, the service port of the collector cannot be the same as the local port of the database. Otherwise, the process cannot be started.
+
+## Principles
+
+**Figure 1** anomaly_detection structure
+
+![anomaly_detection-structure](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/5-2-preparations-1.png)
+
+anomaly_detection is a tool independent of the database kernel. Figure 1 shows the anomaly_detection structure. The anomaly_detection tool consists of the agent and detector modules.
+
+- Agent: data agent module, which consists of the source, channel, and sink. It collects metrics in the database and sends the metrics to the remote detector in HTTP or HTTPS mode.
+- Detector: collects and stores data pushed by the agent, monitors and detects database metrics based on algorithms such as time series forecast and exception detection, and provides root cause analysis on slow SQL statements.
+
+## Running and Installation of anomaly_detection
+
+1. Switch to the **anomaly_detection** directory. For the openGauss community code, the path is **openGauss-server/src/gausskernel/dbmind/tools/anomaly_detection**. For an installed database system, the source code path is **$GAUSSHOME/bin/dbmind/anomaly_detection**.
+
+2. You can view the **requirements.txt** file in the current directory. Use the pip package management tool to install the dependency based on the **requirements.txt** file.
+
+   ```
+   pip install -r requirements.txt
+   ```
+
+3. After the installation is successful, run **main.py**. For example, to obtain the help information, run the following command:
+
+   ```
+   python main.py --help # Obtain help information. The methods of using other functions are similar.
+   ```
+
+## Certificate Generation
+
+When using https to communicate, the user needs to provide a certificate, anomaly_detection also provides a certificate generation tool.
+
+1. To generate the CA root certificate, run the following command in the **share** directory of anomaly_detection:
+
+   ```
+   sh gen_ca_certificate.sh
+   ```
+
+The script will create a certificate directory under the root directory of anomaly_detection, which includes three subdirectories of **ca**, **server**, and **agent**. The root certificate **ca.crt** and the key file **ca.key** are stored in **ca**.
+
+1. To generate the server-side certificate and key file, run the following command in the **share** directory of anomaly_detection:
+
+   ```
+   sh gen_certificate.sh
+
+   # please input the basename of ssl certificate: ../certificate/server
+
+   # please input the filename of ssl certificate: server
+
+   # please input the local host: 127.0.0.1
+
+   # please input the password of ca and ssl separated by space:
+   ```
+
+This script requires the user to input the storage directory of the generated certificate and key file, the name of the certificate and key file, the IP address of the detector server, the CA certificate password, and the current certificate password (separated by spaces). The script will finally generate **server.crt** and **server.key** under the server of the certificate.
+
+1. To generate the agent certificate key and file, run the following command in the **share** directory of anomaly_detection:
+
+   ```
+   sh gen_certificate.sh
+
+   # please input the basename of ssl certificate: ../certificate/agent
+
+   # please input the filename of ssl certificate: agent
+
+   # please input the local host: 127.0.0.1
+
+   # please input the password of ca and ssl separated by space:
+   ```
+
+This script requires the user to input the directory where the generated certificate and key file are stored, the name of the certificate and key file, the agent server IP address, the CA certificate password, and the current certificate password (separated by spaces). The script will finally generate **agent.crt** and **agent.key** under the certificate's agent.
+
+## Description of the anomaly_detection Configuration File
+
+The **a-detection.conf** and **metric\_task.conf**configuration files need to be loaded before **anomaly_detection** is executed. You can run the **python main.py -help** command to view the configuration file path.
+
+**a-detection.conf** contains six sections: agent, server, database, security, forecast, and log. The parameters are described as follows:
+
+```
+[database]
+storage_duration = 12H  # Data storage duration. The default value is 12 hours.
+database_dir = ./data  # Data storage directory
+
+[security]
+tls = False
+ca = ./certificate/ca/ca.crt
+server_cert = ./certificate/server/server.crt
+server_key = ./certificate/server/server.key
+agent_cert = ./certificate/agent/agent.crt
+agent_key = ./certificate/agent/agent.key
+
+[server]
+host = 0.0.0.0  # IP address of the server
+listen_host = 0.0.0.0
+listen_port = 8080
+white_host = 0.0.0.0  # IP address whitelist
+white_port = 8000  # Port number whitelist
+
+[agent]
+source_timer_interval = 10S  #  Agent data collection frequency
+sink_timer_interval = 10S  # Agent data sending frequency
+channel_capacity = 1000  # Maximum length of the buffer queue
+db_host = 0.0.0.0  # IP address of the agent node
+db_port = 8080  # Port number of the agent node
+db_type = single # Agent node type. The value can be single (single node), cn (CN), or dn (DN).
+
+[forecast]
+forecast_alg = auto_arima  # Time series prediction algorithm. The value can be auto_arima or fbprophet (You need to install by yourself).
+[log]
+log_dir = ./log  # Log file location
+```
+
+**metric\_task.conf**: This configuration file contains three sections: **detector_method**, **os_exporter**, and **trend_parameter**. The parameters are described as follows:
+
+```
+[detector_method]
+trend = os_exporter # Name of the table used for time series prediction
+slow_sql = wdr # Name of the table for slow SQL diagnosis
+
+[os_exporter]
+cpu_usage_minimum = 1 # Lower limit of CPU usage
+cpu_usage_maximum = 10 # Upper limit of CPU usage
+memory_usage_minimum = 1 # Lower limit of memory usage
+memory_usage_maximum = 10 # Upper limit of memory usage
+io_read_minimum = 1
+io_read_maximum = 10
+io_write_minimum = 1
+io_write_maximum = 10
+io_wait_minimum = 1
+io_wait_maximum = 10
+disk_space_minimum = 1
+disk_space_maximum = 10
+
+[common_parameter]
+data_period = 1000S # Length of historical data used for time series forecast. The value can be an integer plus the time unit (for example, 100S, 2M, and 10D).
+interval = 20S # Monitoring interval
+freq = 3S # Trend forecast frequency
+period = 2 # Trend forecast period
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - The following time units are supported:
+>   - **'S'**: second
+>   - **'M'**: minute
+>   - **'H'**: hour
+>   - **'D'**: day
+>   - **'W'**: week
+> - At least one of **minimum** and **maximum** must be provided.
+> - **freq** and **period** determine the time series forecast result. For example, if **freq** is set to **2S** and **period** is set to **5**, the values of future 2s, 4s, 6s, 8s, and 10s will be forecasted.
+> - Ensure that the training data length is greater than the forecasting length. Otherwise, the forecasting effect will be affected.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-3-adding-monitoring-parameters.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-3-adding-monitoring-parameters.md
new file mode 100644
index 0000000000000000000000000000000000000000..c947be3d39e390852e0ce719b09a804089888692
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-3-adding-monitoring-parameters.md
@@ -0,0 +1,40 @@
+---
+title: Adding Monitoring Parameters
+summary: Adding Monitoring Parameters
+author: Guo Huan
+date: 2021-05-19
+---
+
+# Adding Monitoring Parameters
+
+The tool performs trend prediction and threshold exception detection only for metrics in **os_exporter**. You can add new monitoring parameters. The procedure is as follows:
+
+1. Compile a function for obtaining metrics in **os_exporter** of **task/os_exporter.py**, and add the function to the output result list. For example:
+
+   ```
+   @staticmethod
+   def new_metric():
+       return metric_value
+
+   def output(self):
+       result = [self.cpu_usage(), self.io_wait(), self.io_read(),
+                 self.io_write(), self.memory_usage(), self.disk_space(), self.new_metric()]
+       return result
+
+   ```
+
+2. In **os_exporter** of **table.json**, add the **new_metric** field to **CREATE table** and add the field type information to **INSERT**. For example:
+
+   ```
+   "os_exporter": {
+     "create_table": "create table  os_exporter(timestamp bigint, cpu_usage text, io_wait text, io_read text, io_write text, memory_usage text, disk_space text, new_metric text);",
+     "insert": "insert into os_exporter values(%d, \"%s\", \"%s\", \"%s\", \"%s\", \"%s\", \"%s\", \"%s\");",
+   ```
+
+3. Add the upper or lower limit of the metric to the **task/metric_task.conf** file. For example:
+
+   ```
+   [os_exporter]
+   new_metric_minimum = 0
+   new_metric_maximum = 10
+   ```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-4-obtaining-help-information.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-4-obtaining-help-information.md
new file mode 100644
index 0000000000000000000000000000000000000000..e51719cd4ea2ad1f1eb136fb9d0c25fa1ec572be
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-4-obtaining-help-information.md
@@ -0,0 +1,78 @@
+---
+title: Obtaining Help Information
+summary: Obtaining Help Information
+author: Guo Huan
+date: 2021-05-19
+---
+
+# Obtaining Help Information
+
+Before starting the tuning program, run the following command to obtain help information:
+
+```
+Source code mode: python main.py --help
+```
+
+The command output is as follows:
+
+```
+usage:
+    python main.py start [--role {{agent,collector,monitor}}] # start local service.
+    python main.py stop [--role {{agent,collector,monitor}}] # stop local service.
+    python main.py start [--user USER] [--host HOST] [--project-path PROJECT_PATH] [--role {{agent,collector,monitor}}]
+    # start the remote service.
+    python main.py stop [--user USER] [--host HOST] [--project-path PROJECT_PATH] [--role {{agent,collector,
+    monitor}}] # stop the remote service.
+    python main.py deploy [--user USER] [--host HOST] [--project-path PROJECT_PATH] # deploy project in remote host.
+    python main.py diagnosis [--query] [--start_time] [--finish_time] # rca for slow SQL.
+    python main.py show_metrics # display all monitored metrics(can only be executed on 'detector' machine).
+    python main.py forecast [--metric-name METRIC_NAME] [--period] [--freq]
+     [--forecast-method {{auto_arima, fbprophet}}] [--save-path SAVE_PATH] # forecast future trend of
+     metric(can only be executed on 'detector' machine).
+
+Anomaly-detection: a time series forecast and anomaly detection tool.
+
+positional arguments:
+  {start,stop,deploy,show_metrics,forecast,diagnosis}
+
+optional arguments:
+  -h, --help            show this help message and exit
+  --user USER           User of remote server.
+  --host HOST           IP of remote server.
+  --project-path PROJECT_PATH
+                        Project location in remote server.
+  --role {agent,collector,monitor}
+                        Run as 'agent', 'collector', 'monitor'. Notes: ensure
+                        the normal operation of the openGauss in agent.
+  --metric-name METRIC_NAME
+                        Metric name to be predicted, you must provide an specified metric name.
+.
+  --query QUERY         target sql for RCA.
+                        Currently, the join operator is not supported, and the accuracy of the result
+                        is not guaranteed for SQL syntax containing "not null and".
+  --start_time START_TIME
+                        start time of query
+  --finish_time FINISH_TIME
+                        finish time of query
+  --period PERIOD       Forecast periods of metric, it should be integernotes:
+                        the specific value should be determined to the
+                        trainnig data.if this parameter is not provided, the
+                        default value '100S' will be used.
+  --freq FREQ           forecast gap, time unit: S: Second, M: Minute, H:
+                        Hour, D: Day, W: Week.
+  --forecast-method FORECAST_METHOD
+                        Forecast method, default method is 'auto_arima',if
+                        want to use 'fbprophet', you should install fbprophet
+                        first.
+  --save-path SAVE_PATH
+                        Save the results to this path using csv format, if
+                        this parameter is not provided,, the result wil not be
+                        saved.
+  -v, --version         show program's version number and exit
+
+epilog:
+     the 'a-detection.conf' and 'metric_task.conf' will be read when the program is running,
+     the location of them is:
+     a-detection.conf: /openGauss-server/src/gausskernel/dbmind/tools/anomaly_detection/a-detection.conf.
+     metric_config: /openGauss-server/src/gausskernel/dbmind/tools/anomaly_detection/task/metric_task.conf.
+```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-5-command-reference.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-5-command-reference.md
new file mode 100644
index 0000000000000000000000000000000000000000..c177845c2e2551e88a7ae95d57e4c104b1ff7e00
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-5-command-reference.md
@@ -0,0 +1,26 @@
+---
+title: Command Reference
+summary: Command Reference
+author: Guo Huan
+date: 2021-05-19
+---
+
+# Command Reference
+
+**Table 1** Command-line parameters
+
+| Parameter         | Description                                                  | Value Range                                                  |
+| :---------------- | :----------------------------------------------------------- | :----------------------------------------------------------- |
+| mode              | Specified running mode                                       | **start**, **stop**, **forecast**, **show_metrics**, **deploy**, and **diagnosis** |
+| -user             | Remote server user                                           | -                                                            |
+| -host             | IP address of the remote server                              | -                                                            |
+| -project-path     | Path of the **anomaly_detection** project on the remote server | -                                                            |
+| -role             | Start role                                                   | **agent**, **collector**, and **monitor**                    |
+| -metric-name      | Metric name                                                  | -                                                            |
+| -query            | Root cause analysis (RCA) target query                       |                                                              |
+| -start_time       | Time when the query starts                                   |                                                              |
+| -finish_time      | Time when the query ends                                     |                                                              |
+| -forecast-periods | Forecast period                                              | Integer + Time unit, for example, '100S', '3H'.<br/>The time unit can be **S** (second), **M** (minute), **H** (hour), **D** (day), and **W** (week). |
+| -forecast-method  | Forecasting method                                           | **auto_arima** and **fbprophet**                             |
+| -save-path        | Path for storing the forecasting result                      | -                                                            |
+| -version, -v      | Current tool version                                         | -                                                            |
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-6-examples.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-6-examples.md
new file mode 100644
index 0000000000000000000000000000000000000000..a639ae6ca93add92e772347d62705385eb1f9a1f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-6-examples.md
@@ -0,0 +1,102 @@
+---
+title: Examples
+summary: Examples
+author: Guo Huan
+date: 2021-05-19
+---
+
+# Examples
+
+To help users understand the deployment process, assume that the current database node information is as follows:
+
+```
+IP: 10.90.110.130
+PORT: 8000
+type: single
+```
+
+The detector server information is as follows:
+
+```
+IP: 10.90.110.131
+listen_host = 0.0.0.0
+listen_port = 8080
+```
+
+The deployment startup process is as follows.
+
+## Modifying the Configuration File
+
+Modify the **a-detection.conf** configuration file. The following two sessions are involved:
+
+```
+[database]
+storage_duration = 12H  # Data storage duration. The default value is 12 hours.
+database_dir = ./data  # Data storage directory
+
+[security]
+tls = False
+ca = ./certificate/ca/ca.crt
+server_cert = ./certificate/server/server.crt
+server_key = ./certificate/server/server.key
+agent_cert = ./certificate/agent/agent.crt
+agent_key = ./certificate/agent/agent.key
+
+[server]
+host = 10.90.110.131
+listen_host = 0.0.0.0
+listen_port = 8080
+white_host =  10.90.110.130
+white_port = 8000
+[agent]
+source_timer_interval = 10S
+sink_timer_interval = 10S
+channel_capacity = 1000
+db_host =  10.90.110.130
+db_port = 8080
+db_type = single
+
+[forecast]
+forecast_alg = auto_arima
+
+[log]
+log_dir = ./log
+```
+
+## Starting and Stopping Services
+
+Start the local agent service.
+
+```
+python main.py start --role agent
+```
+
+Stop the local agent service.
+
+```
+python main.py stop --role agent
+```
+
+Start the local collector service.
+
+```
+python main.py start --role collector
+```
+
+Stop the local collector service.
+
+```
+python main.py stop --role collector
+```
+
+Start the local monitor service.
+
+```
+python main.py start --role monitor
+```
+
+Stop the local monitor service.
+
+```
+python main.py stop --role monitor
+```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-7-ai-server.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-7-ai-server.md
new file mode 100644
index 0000000000000000000000000000000000000000..80c282eb4411a2f3cf55eacbc54ffd2cbffbf10b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-7-ai-server.md
@@ -0,0 +1,72 @@
+---
+title: AI_SERVER
+summary: AI_SERVER
+author: Guo Huan
+date: 2021-10-21
+---
+
+# AI_SERVER
+
+AI_SERVER is an independent from the anomaly_detection feature. In addition to the data collection function of the anomaly_detection feature, the collection type, collection item, and data storage mode are added to the AI_SERVER feature. The AI_SERVER feature is used only for data collection and will be integrated into the anomaly_detection feature in the future. This feature includes the server and agent components. The agent must be deployed on the database node for data collection, while the server is deployed on an independent node for data collection and storage.
+
+The data storage modes include **sqlite**, **mongodb**, and **influxdb**.
+
+Table 1 describes the collection items.
+
+**Table 1** Collection items
+
+<table>
+    <tr>
+        <th>Collection Type</th>
+        <th>Collection Item</th>
+        <th>Description</th>
+    </tr>
+    <tr>
+        <td rowspan=5>database</td>
+        <td>work_mem</td>
+        <td>GUC parameter related to the database memory. This parameter is used to check whether the allocated space is sufficient for SQL statements involving sorting tasks.</td>
+    </tr>
+    <tr>
+        <td>shared_buffers</td>
+        <td>GUC parameter related to the database memory. Improper setting of shared_buffer will deteriorate the database performance.</td>
+    </tr>
+    <tr>
+        <td>max_connections</td>
+        <td>Maximum number of database connections.</td>
+    </tr>
+    <tr>
+        <td>current connections</td>
+        <td>Number of current database connections.</td>
+    </tr>
+    <tr>
+        <td>qps</td>
+        <td>Database performance metrics:</td>
+    </tr>
+    <tr>
+        <td rowspan=6>os</td>
+        <td>cpu usage</td>
+        <td>CPU usage.</td>
+    </tr>
+    <tr>
+        <td>memory usage</td>
+        <td>Memory usage.</td>
+    </tr>
+    <tr>
+        <td>io wait</td>
+        <td>I/O wait event.</td>
+    </tr>
+    <tr>
+        <td>io write</td>
+        <td>Data disk write throughput.</td>
+    </tr>
+    <tr>
+        <td>io read</td>
+        <td>Data disk read throughput.</td>
+    </tr>
+    <tr>
+        <td>disk used</td>
+        <td>Size of the used disk space.</td>
+    </tr>
+</table>
+
+For details about the deployment mode, see [AI_MANAGER](5-8-ai-manager).
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-8-ai-manager.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-8-ai-manager.md
new file mode 100644
index 0000000000000000000000000000000000000000..654fc54fd27157d351c974e11411e03c4b84e225
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-8-ai-manager.md
@@ -0,0 +1,82 @@
+---
+title: AI_MANAGER
+summary: AI_MANAGER
+author: Guo Huan
+date: 2021-10-22
+---
+
+# AI_MANAGER
+
+AI_MANAGER is an AI feature deployment tool. It aims to provide automatic, efficient, and convenient deployment and uninstallation of AI features. You can specify the module name, operation type, and parameter file to automatically deploy and uninstall AI features, implementing version management, operation logging, log management, installation information recording. In addition, it supports feature-level horizontal expansion. Currently, this tool supports only the installation and uninstallation of AI_SERVER.
+
+## Preparations
+
+- The project deployment path is **/dbs/AI-tools**. Ensure that the path exists and you have the read, write, and execute permissions on the path. The content in the path will be cleared during installation or uninstallation. Do not save other files in this path.
+- You need to install the Python3 environment and the Python library required by the feature. For details about the dependent library, see the **requirements.txt** file in the package.
+- If HTTPS is enabled, you need to prepare the corresponding root certificate, key file, and password.
+- The MogDB database has been started on the agent node.
+- You need to install the agent node as a cluster user.
+- If the **-/.bashrc** file of the cluster user on the agent node does not contain the correct **PGHOST** configuration, configure the **PGHOST** configuration in the **/dbs/AI-tools/ai_env** file.
+
+## Examples
+
+An example of the installation command is as follows:
+
+```bash
+python3 ai_manager --module anomaly_detection --action install --param-file opengauss.json
+```
+
+An example of the uninstallation command is as follows:
+
+```bash
+python3 ai_manager --module anomaly_detection--action uninstall --param-file opengauss.json
+```
+
+The following is an example of the parameter file:
+
+```json
+{
+  "scene": "mogdb",                                       # Scenario. Both the server and agent modules are installed for mogdb, and only the server module is installed for HUAWEI CLOUD.
+  "module": "anomaly_detection",                              # Module (feature) name. Currently, only anomaly_detection is supported.
+  "action": "install",                                        # Operation type. The value can be install or uninstall.
+  "ca_info": {
+    "ca_cert_path": "/home/Ruby/CA_AI/ca.crt",                # Path of the root certificate
+    "ca_key_path": "/home/Ruby/CA_AI/ca.crt.key",             # Path of the root certificate key
+    "ca_password": "GHJAyusa241~"                             # Root certificate password
+  },
+  "agent_nodes": [
+    {
+      "node_ip": "10.000.00.000",                             # IP address of the agent node
+      "username": "Ruby",                                     # User of the agent node
+      "password": "password"                                  # Password for logging in to the agent node
+    }
+  ],
+  "config_info": {
+    "server": {
+      "host": "10.000.00.000",                                # IP address of the node where server is deployed (execution node)
+      "listen_host": "0.0.0.0",                               # Server listening IP address
+      "listen_port": "20060",                                 # Server listening port number
+      "pull_kafka": "False"                                   # Specifies whether to pull Kafka data. Currently, data cannot be pulled.
+    },
+    "database": {
+       "name": "sqlite",                                       # Data storage mode. sqlite, mongodb, and influxdb are supported.
+      "host": "127.0.0.1",                                    # Database IP address
+      "port": "2937",                                         # Database port number
+      "user": "Ruby",                                         # Database user
+      "size": "175000000",                                    # Maximum storage capacity in mongodb mode
+      "max_rows": "1000000"                                   # Maximum number of stored records in mongodb mode
+    },
+    "agent": {
+      "cluster_name": "my_cluster",                           # Name of the collection database
+      "collection_type": "os",                                # Collection type. The value can be os, database, or all.
+      "collection_item": [["dn", "10.000.00.000", "33700"]],  # Type of data collected by the agent node (DN/CN), IP address of the collection node, and port number
+      "channel_capacity": "1000",                             # Queue capacity
+      "source_timer_interval": "5S",                          # Collection Interval
+      "sink_timer_interval": "5S"                             # Sending interval
+    },
+    "security": {
+      "tls": "True"                                           # Specifies whether to enable HTTPS.
+    }
+  }
+}
+```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/6-index-advisor-index-recommendation/6-1-single-query-index-recommendation.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/6-index-advisor-index-recommendation/6-1-single-query-index-recommendation.md
new file mode 100644
index 0000000000000000000000000000000000000000..ea47de36d76b6a67f064224df74ff0668de2e638
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/6-index-advisor-index-recommendation/6-1-single-query-index-recommendation.md
@@ -0,0 +1,59 @@
+---
+title: Single-query Index Recommendation
+summary: Single-query Index Recommendation
+author: Guo Huan
+date: 2021-05-19
+---
+
+# Single-query Index Recommendation
+
+The single-query index recommendation function allows users to directly perform operations in the database. This function generates recommended indexes for a single query statement entered by users based on the semantic information of the query statement and the statistics of the database. This function involves the following interfaces:
+
+**Table 1** Single-query index recommendation interfaces
+
+| Function Name   | Parameter            | Description                                                  |
+| :-------------- | :------------------- | :----------------------------------------------------------- |
+| gs_index_advise | SQL statement string | Generates a recommendation index for a single query statement. |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - This function supports only a single SELECT statement and does not support other types of SQL statements.
+> - Partitioned tables, column-store tables, segment-paged tables, common views, materialized views, global temporary tables, and encrypted databases are not supported.
+
+## Application Scenarios
+
+Use the preceding function to obtain the recommendation index generated for the query. The recommendation result consists of the table name and column name of the index.
+
+For example:
+
+```sql
+mogdb=> select "table", "column" from gs_index_advise('SELECT c_discount from bmsql_customer where c_w_id = 10');
+     table      |  column
+----------------+----------
+ bmsql_customer | (c_w_id)
+(1 row)
+```
+
+The preceding information indicates that an index should be created on the **c_w_id** column of the **bmsql_customer** table. You can run the following SQL statement to create an index:
+
+```sql
+CREATE INDEX idx on bmsql_customer(c_w_id);
+```
+
+Some SQL statements may also be recommended to create a join index, for example:
+
+```sql
+mogdb=# select "table", "column" from gs_index_advise('select name, age, sex from t1 where age >= 18 and age < 35 and sex = ''f'';');
+ table | column
+-------+------------
+ t1    | (age, sex)
+(1 row)
+```
+
+The preceding statement indicates that a join index **(age, sex)** needs to be created in the **t1** table. You can run the following command to create a join index:
+
+```sql
+CREATE INDEX idx1 on t1(age, sex);
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** Parameters of the system function **gs_index_advise()** are of the text type. If the parameters contain special characters such as single quotation marks ('), you can use single quotation marks (') to escape the special characters. For details, see the preceding example.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/6-index-advisor-index-recommendation/6-2-virtual-index.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/6-index-advisor-index-recommendation/6-2-virtual-index.md
new file mode 100644
index 0000000000000000000000000000000000000000..4d6cd4168804fde4c3b17cedc26d968087243ba0
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/6-index-advisor-index-recommendation/6-2-virtual-index.md
@@ -0,0 +1,123 @@
+---
+title: Virtual Index
+summary: Virtual Index
+author: Guo Huan
+date: 2021-05-19
+---
+
+# Virtual Index
+
+The virtual index function allows users to directly perform operations in the database. This function simulates the creation of a real index to avoid the time and space overhead required for creating a real index. Based on the virtual index, users can evaluate the impact of the index on the specified query statement by using the optimizer.
+
+This function involves the following interfaces:
+
+**Table 1** Virtual index function interfaces
+
+| Function Name        | Parameter                                               | Description                                                  |
+| :------------------- | :------------------------------------------------------ | :----------------------------------------------------------- |
+| hypopg_create_index  | Character string of the statement for creating an index | Creates a virtual index.                                     |
+| hypopg_display_index | None                                                    | Displays information about all created virtual indexes.      |
+| hypopg_drop_index    | OID of the index                                        | Deletes a specified virtual index.                           |
+| hypopg_reset_index   | None                                                    | Clears all virtual indexes.                                  |
+| hypopg_estimate_size | OID of the index                                        | Estimates the space required for creating a specified index. |
+
+This function involves the following GUC parameters:
+
+**Table 2** GUC parameters of the virtual index function
+
+| Parameter         | Description                                   | Default Value |
+| :---------------- | :-------------------------------------------- | :------------ |
+| enable_hypo_index | Whether to enable the virtual index function. | off           |
+
+## Procedure
+
+1. Use the **hypopg_create_index** function to create a virtual index. For example:
+
+   ```sql
+   mogdb=> select * from hypopg_create_index('create index on bmsql_customer(c_w_id)');
+    indexrelid |              indexname
+   ------------+-------------------------------------
+        329726 | <329726>btree_bmsql_customer_c_w_id
+   (1 row)
+   ```
+
+2. Enable the GUC parameter **enable_hypo_index**. This parameter controls whether the database optimizer considers the created virtual index when executing the EXPLAIN statement. By executing EXPLAIN on a specific query statement, you can evaluate whether the index can improve the execution efficiency of the query statement based on the execution plan provided by the optimizer. For example:
+
+   ```sql
+   mogdb=> set enable_hypo_index = on;
+   SET
+   ```
+
+   Before enabling the GUC parameter, run **EXPLAIN** and the query statement.
+
+   ```sql
+   mogdb=> explain SELECT c_discount from bmsql_customer where c_w_id = 10;
+                                 QUERY PLAN
+   ----------------------------------------------------------------------
+    Seq Scan on bmsql_customer  (cost=0.00..52963.06 rows=31224 width=4)
+      Filter: (c_w_id = 10)
+   (2 rows)
+   ```
+
+   After enabling the GUC parameter, run **EXPLAIN** and the query statement.
+
+   ```sql
+   mogdb=> explain SELECT c_discount from bmsql_customer where c_w_id = 10;
+                                                       QUERY PLAN
+   ------------------------------------------------------------------------------------------------------------------
+    [Bypass]
+    Index Scan using <329726>btree_bmsql_customer_c_w_id on bmsql_customer  (cost=0.00..39678.69 rows=31224 width=4)
+      Index Cond: (c_w_id = 10)
+   (3 rows)
+   ```
+
+   By comparing the two execution plans, you can find that the index may reduce the execution cost of the specified query statement. Then, you can consider creating a real index.
+
+3. (Optional) Use the **hypopg_display_index** function to display all created virtual indexes. For example:
+
+   ```sql
+   mogdb=> select * from hypopg_display_index();
+                    indexname                  | indexrelid |     table      |      column
+   --------------------------------------------+------------+----------------+------------------
+    <329726>btree_bmsql_customer_c_w_id        |     329726 | bmsql_customer | (c_w_id)
+    <329729>btree_bmsql_customer_c_d_id_c_w_id |     329729 | bmsql_customer | (c_d_id, c_w_id)
+   (2 rows)
+   ```
+
+4. (Optional) Use the **hypopg_estimate_size** function to estimate the space (in bytes) required for creating a virtual index. For example:
+
+   ```sql
+   mogdb=> select * from hypopg_estimate_size(329730);
+    hypopg_estimate_size
+   ----------------------
+                15687680
+   (1 row)
+   ```
+
+5. Delete the virtual index.
+
+   Use the **hypopg_drop_index** function to delete the virtual index of a specified OID. For example:
+
+   ```sql
+   mogdb=> select * from hypopg_drop_index(329726);
+    hypopg_drop_index
+   -------------------
+    t
+   (1 row)
+   ```
+
+   Use the **hypopg_reset_index** function to clear all created virtual indexes at a time. For example:
+
+   ```sql
+   mogdb=> select * from hypopg_reset_index();
+    hypopg_reset_index
+   --------------------
+
+   (1 row)
+   ```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - Running **EXPLAIN ANALYZE** does not involve the virtual index function.
+> - The created virtual index is at the database instance level and can be shared by sessions. After a session is closed, the virtual index still exists. However, the virtual index will be cleared after the database is restarted.
+> - This function does not support common views, materialized views, and column-store tables.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/6-index-advisor-index-recommendation/6-3-workload-level-index-recommendation.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/6-index-advisor-index-recommendation/6-3-workload-level-index-recommendation.md
new file mode 100644
index 0000000000000000000000000000000000000000..409d1c1643699a00f5cef4b611b98d4d8c5e07cd
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/6-index-advisor-index-recommendation/6-3-workload-level-index-recommendation.md
@@ -0,0 +1,105 @@
+---
+title: Workload-level Index Recommendation
+summary: Workload-level Index Recommendation
+author: Guo Huan
+date: 2021-05-19
+---
+
+# Workload-level Index Recommendation
+
+For workload-level indexes, you can run scripts outside the database to use this function. This function uses the workload of multiple DML statements as the input to generate a batch of indexes that can optimize the overall workload execution performance. In addition, it provides the function of extracting service data SQL statements from logs.
+
+## Prerequisites
+
+- The database is normal, and the client can be connected properly.
+
+- The **gsql** tool has been installed by the current user, and the tool path has been added to the **PATH** environment variable.
+
+- The Python 3.6+ environment is available.
+
+- To use the service data extraction function, you need to set the GUC parameters of the node whose data is to be collected as follows:
+
+  - log_min_duration_statement = 0
+
+  - log_statement= 'all'
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** After service data extraction is complete, you are advised to restore the preceding GUC parameters. Otherwise, log files may be expanded.
+
+## Procedure for Using the Service Data Extraction Script
+
+1. Set the GUC parameters according to instructions in the prerequisites.
+
+2. Run the Python script **extract_log.py**:
+
+   ```
+   ython extract_log.py [l LOG_DIRECTORY] [f OUTPUT_FILE] [-d DATABASE] [-U USERNAME][--start_time] [--sql_amount] [--statement] [--json]
+   ```
+
+   The input parameters are as follows:
+
+   - **LOG_DIRECTORY**: directory for storing **pg_log**.
+   - **OUTPUT_PATH**: path for storing the output SQL statements, that is, path for storing the extracted service data.
+   - **DATABASE** (optional): database name. If this parameter is not specified, all databases are selected by default.
+   - **USERNAME** (optional): username. If this parameter is not specified, all users are selected by default.
+   - **start_time** (optional): start time for log collection. If this parameter is not specified, all files are collected by default.
+   - **sql_amount** (optional): maximum number of SQL statements to be collected. If this parameter is not specified, all SQL statements are collected by default.
+   - **statement** (optional): Collects the SQL statements starting with **statement** in **pg_log log**. If this parameter is not specified, the SQL statements are not collected by default.
+   - **json**: Specifies that the collected log files are stored in JSON format after SQL normalization. If the default format is not specified, each SQL statement occupies a line.
+
+   An example is provided as follows.
+
+   ```
+   python extract_log.py $GAUSSLOG/pg_log/dn_6001 sql_log.txt -d postgres -U omm --start_time '2021-07-06 00:00:00' --statement
+   ```
+
+3. Change the GUC parameter values set in step 1 to the values before the setting.
+
+## Procedure for Using the Index Recommendation Script
+
+1. Prepare a file that contains multiple DML statements as the input workload. Each statement in the file occupies a line. You can obtain historical service statements from the offline logs of the database.
+
+2. Run the Python script **index_advisor_workload.py**:
+
+   ```
+   python index_advisor_workload.py [p PORT] [d DATABASE] [f FILE] [--h HOST] [-U USERNAME] [-W PASSWORD][--schema SCHEMA][--max_index_num MAX_INDEX_NUM][--max_index_storage MAX_INDEX_STORAGE] [--multi_iter_mode] [--multi_node]  [--json] [--driver] [--show_detail]
+   ```
+
+   The input parameters are as follows:
+
+   - **PORT**: port number of the connected database.
+   - **DATABASE**: name of the connected database.
+   - **FILE**: file path that contains the workload statement.
+   - **HOST** (optional): ID of the host that connects to the database.
+   - **USERNAME** (optional): username for connecting to the database.
+   - **PASSWORD** (optional): password for connecting to the database.
+   - **SCHEMA**: schema name.
+   - **MAX_INDEX_NUM** (optional): maximum number of recommended indexes.
+   - **MAX_INDEX_STORAGE** (optional): maximum size of the index set space.
+   - **multi_node** (optional): specifies whether the current instance is a distributed database instance.
+   - **multi_iter_mode** (optional): algorithm mode. You can switch the algorithm mode by setting this parameter.
+   - **json** (optional): Specifies the file path format of the workload statement as JSON after SQL normalization. By default, each SQL statement occupies one line.
+   - **driver** (optional): Specifies whether to use the Python driver to connect to the database. By default, **gsql** is used for the connection.
+   - **show_detail** (optional): Specifies whether to display the detailed optimization information about the current recommended index set.
+
+   Example:
+
+   ```
+   python index_advisor_workload.py 6001 postgres tpcc_log.txt --schema public --max_index_num 10 --multi_iter_mode
+   ```
+
+   The recommendation result is a batch of indexes, which are displayed on the screen in the format of multiple create index statements. The following is an example of the result.
+
+   ```sql
+   create index ind0 on public.bmsql_stock(s_i_id,s_w_id);
+   create index ind1 on public.bmsql_customer(c_w_id,c_id,c_d_id);
+   create index ind2 on public.bmsql_order_line(ol_w_id,ol_o_id,ol_d_id);
+   create index ind3 on public.bmsql_item(i_id);
+   create index ind4 on public.bmsql_oorder(o_w_id,o_id,o_d_id);
+   create index ind5 on public.bmsql_new_order(no_w_id,no_d_id,no_o_id);
+   create index ind6 on public.bmsql_customer(c_w_id,c_d_id,c_last,c_first);
+   create index ind7 on public.bmsql_new_order(no_w_id);
+   create index ind8 on public.bmsql_oorder(o_w_id,o_c_id,o_d_id);
+   create index ind9 on public.bmsql_district(d_w_id);
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The value of the **multi_node** parameter must be specified based on the current database architecture. Otherwise, the recommendation result is incomplete, or even no recommendation result is generated.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/7-deepsql/7-1-overview.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/7-deepsql/7-1-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..8fafac892f6e80088328cd9b5d454ebdf7664cd0
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/7-deepsql/7-1-overview.md
@@ -0,0 +1,108 @@
+---
+title: Overview
+summary: Overview
+author: Guo Huan
+date: 2021-05-19
+---
+
+# Overview
+
+The DeepSQL feature is compatible with the MADLib framework and can implement AI algorithms in the database. A complete set of SQL-based machine learning, data mining, and statistics algorithms is provided. Users can directly use SQL statements to perform machine learning. Deep SQL can abstract the end-to-end R&D process from data to models. With the bottom-layer engine and automatic optimization, technical personnel with basic SQL knowledge can complete most machine learning model training and prediction tasks. The entire analysis and processing are running in the database engine. Users can directly analyze and process data in the database without transferring data between the database and other platforms. This avoids unnecessary data movement between multiple environments.
+
+DeepSQL is an enhancement to MogDB DB4AI, allowing data analysts or developers who are familiar with MADLib to easily migrate data to MogDB. DeepSQL encapsulates common machine learning algorithms into SQL statements and supports more than 60 general algorithms, including regression algorithms (such as linear regression, logistic regression, and random forest), classification algorithms (such as KNN), and clustering algorithms (such as K-means). In addition to basic machine learning algorithms, graph-related algorithms are also included, such as algorithms about the shortest path and graph diameter. Also, it supports data processing (such as PCA), sparse vectors, common statistical algorithms (such as covariance and Pearson coefficient calculation), training set and test set segmentation, and cross validation.
+
+**Table 1** Supported machine learning algorithms: regression algorithms
+
+| Algorithm Name                      | Abbreviation | Application Scenario                                         |
+| :---------------------------------- | :----------- | :----------------------------------------------------------- |
+| Logistic regression                 | -            | For example, find the risk factors of a disease, or evaluate enterprises for financial and commercial institutions.<br/>Prediction: Use a model to predict the occurrence probabilities of a disease or situation under different independent variables.<br/>Judgment: Use a model to determine the probability that a person has certain diseases or be in certain situations. |
+| Cox proportional hazards regression | -            | The model takes the survival result and the survival time as dependent variables, can analyze the influence of many factors on the survival time simultaneously, and can analyze the data with the truncated survival time, without the need of estimating the distribution type of the data. Because of the preceding excellent properties, this model has been widely used in medical research since its inception, and is the most widely used multi-factor analysis method in survival analysis. |
+| Elastic net regularization          | -            | Elastic regression is a hybrid technique of ridge regression and lasso regression, which uses L2 and L1 regularization at the same time. When there are multiple related features, the lasso regression is likely to randomly select one of them, while the elastic regression is likely to select all of them. |
+| Generalized linear model            | -            | In some practical problems, the relationship between variables is not always linear. In this case, curves should be used for fitting. |
+| Marginal effect                     | -            | Calculation of marginal effects.                             |
+| Multinomial regression              | -            | If there are more than two target categories, multinomial regression is required. For example, evaluate the curative effect with "ineffective", "effective", and "cured". |
+| Ordinal regression                  | -            | In statistics, ordinal regression is a regression analysis used to predict ordinal variables. That is, the values of variables are within any range, and the metric distances between different values are different. It can be considered as an issue between regression and classification. Examples include the severity of illness (levels 1, 2, 3, and 4), the pain scale (no pain, mild, moderate, and severe), and the drug dose-response effects (ineffective, less effective, effective, and very effective). The differences between levels are not necessarily equal, for example, the difference between no pain and mild is not necessarily equal to the difference between moderate and severe. |
+| Clustered variance                  | -            | The clustered variance module adjusts the standard error of clustering. For example, when a dataset is copied 100 times, precision of parameter estimation should not be increased, but execution of this process in compliance with an independent identically distributed (IID) assumption actually improves precision. |
+| Robust variance                     | -            | The functions in the robust variance module are used to compute the robust variance (Huber-White estimator) of linear regression, logistic regression, multinomial logistic regression, and Cox proportional hazard regression (Huber-White estimation). They can be used to compute differences of data in datasets with potential anomalous noises. |
+| Support vector machine              | SVM          | Compared with traditional query optimization schemes, SVM can obtain higher query accuracy for text and hypertext classification and image classification. This also applies to image segmentation systems. |
+| Linear regression                   | -            | This is widely used in economics and finance.                |
+
+**Table 2** Supported machine learning algorithms: other supervised learning
+
+| Algorithm Name           | Abbreviation | Application Scenario                                         |
+| :----------------------- | :----------- | :----------------------------------------------------------- |
+| Decision tree            | -            | It is one of the most widely used inductive inference algorithms. It handles the classification and prediction problems of category or continuous variables. The model can be represented by graphs and if-then rules, which is highly readable. |
+| Random forest            | RF           | Random forest is a kind of combinatorial method specially designed for decision tree classifier. It combines multiple decision trees to make predictions. |
+| Conditional random field | CRF          | CRF is a discriminant graphic model with undirected probability. A linear chain CRF is a special type of CRF that assumes that the current state depends only on the previous state. Good results have been obtained in sequence annotation tasks such as word segmentation, part-of-speech tagging, and named entity recognition. |
+| Naive Bayes              | -            | Classification by calculating probabilities can be used to deal with multi-classification issues, such as spam filters. |
+| Neural network           | -            | It has a wide range of application scenarios, such as speech recognition, image recognition, and machine translation. It is a standard supervised learning algorithm in the domain of pattern recognition, and continues to be a research subject in the domain of computational neurology. MLP has been proved to be a general function approximation method, which can be used to fit complex functions or solve classification problems. |
+| k-nearest neighbors      | -            | In the k-nearest neighbor classification method, a distance between each training sample and a to-be-classified sample is computed, and **K** training samples that are closest to the to-be-classified sample are selected. If training samples of a category in the **K** samples accounts for a majority, the to-be-classified tuple belongs to the category.<br/>It can be used for text recognition, facial recognition, gene pattern recognition, customer churn prediction, and fraud detection. |
+
+**Table 3** Supported machine learning algorithms: data processing algorithms
+
+| Algorithm Name                                            | Abbreviation | Application Scenario                                         |
+| :-------------------------------------------------------- | :----------- | :----------------------------------------------------------- |
+| Array operation                                           | -            | Array and vector operations, including basic addition, subtraction, multiplication, and division, exponentiation, root extraction, cos, sin, absolute value, and variance. |
+| Principal component analysis for dimensionality reduction | PCA          | This is used to reduce dimensions and compute the principal component. |
+| Encoding categorical variable                             | -            | Currently, the one-hot and dummy encoding technologies are supported.<br/>When a specific group of prediction variables need to be compared with another group of prediction variables, dummy coding is usually used, and a group of variables compared with the group of prediction variables is referred to as a reference group. One-hot encoding is similar to dummy encoding, and a difference lies in that the one-hot encoding establishes a numeric type 0/1 indication column for each classification value. In each row of data (corresponding to one data point), a value of only one classification code column can be **1**. |
+| Matrix operation                                          | -            | Using matrix decomposition to decompose a large matrix into the product form of a simple matrix can greatly reduce the difficulty and volume of computation.<br/>Matrix addition, subtraction, multiplication, and division, extremum, mean, rank calculation, inversion, matrix decomposition (QR, LU, Cholesky), and feature extraction. |
+| Norms and distance functions                              | -            | This is used to compute the norm, cosine similarity, and distance between vectors. |
+| Sparse vector                                             | -            | This is used to implement the sparse vector type. If there are a large number of repeated values in the vector, the vector can be compressed to save space. |
+| Pivot                                                     | -            | Pivot tables are used to meet common row and column transposition requirements in OLAP or report systems. The pivot function can perform basic row-to-column conversion on data stored in a table and output the aggregation result to another table. It makes row and column conversion easier and more flexible. |
+| Path                                                      | -            | It performs regular pattern matching on a series of rows and extracts useful information about pattern matching. The useful information can be a simple match count or something more involved, such as an aggregate or window function. |
+| Sessionize                                                | -            | The sessionize function performs time-oriented session rebuilding on a dataset that includes an event sequence. The defined inactive period indicates the end of a session and the start of the next session.<br/>It can be used for network analysis, network security, manufacturing, finance, and operation analysis. |
+| Conjugate gradient                                        | -            | A method for solving numerical solutions of linear equations whose coefficient matrices are symmetric positive definite matrices. |
+| Stemming                                                  | -            | Stemming is simply to find the stem of a word. It can be used to, for example, establish a topic-focused search engine.<br/>The optimization effect is obvious on English websites, which can be a reference for websites in other languages. |
+| Train-Test Split                                          | -            | It is used to split a dataset into a training set and a test set. The train set is used for training, and the test set is used for verification. |
+| Cross validation                                          | -            | It is used to perform cross validation.                      |
+| Prediction metric                                         | -            | It is used to evaluate the quality of model prediction, including the mean square error, AUC value, confusion matrix, and adjusted R-square. |
+| Mini-batch preprocessor                                   | -            | It is used to pack the data into small parts for training. The advantage is that the performance is better than that of the stochastic gradient descent (the default MADlib optimizer), and the convergence is faster and smoother. |
+
+**Table 4** Supported machine learning algorithms: graph
+
+| Algorithm Name                 | Abbreviation | Application Scenario                                         |
+| :----------------------------- | :----------- | :----------------------------------------------------------- |
+| All pairs shortest path        | APSP         | APSP finds the length (summed weight) of the shortest path between all pairs of vertices to minimize the sum of the path edge weights. |
+| Breadth-first search           | -            | This algorithm traverses paths.                              |
+| Hyperlink-induced topic search | HITS         | HITS outputs the authority score and hub score of each vertex, where authority estimates the value of the content of the page and hub estimates the value of its links to other pages. |
+| Average path length            | -            | This function computes the average value of the shortest paths between each pair of vertices. The average path length is based on the "reachable target vertexes", so it ignores infinite-length paths between unconnected vertices. |
+| Closeness centrality           | -            | The closeness measures are the inverse of the sum, the inverse of the average, and the sum of inverses of the shortest distances to all reachable target vertices (excluding the source vertex). |
+| Chart diameter                 | -            | The diameter is defined as the longest of all the shortest paths in the graph. |
+| In-Out degree                  | -            | This algorithm computes the in-degree and out-degree of each node. The node in-degree is the number of edges pointing in to the node and node out-degree is the number of edges pointing out of the node. |
+| PageRank                       | -            | Given a graph, the PageRank algorithm outputs a probability distribution representing the likelihood that a person randomly traversing the graph will arrive at any particular vertex. |
+| Single source shortest path    | SSSP         | Given a graph and a source vertex, the SSSP algorithm finds a path from the source vertex to every other vertex in the graph to minimize the sum of the weights of the path edges. |
+| Weakly connected component     | -            | Given a directed graph, the WCC is a subgraph of the original graph, where all vertices are connected to each other through a path, ignoring the direction of the edges. In the case of an undirected graph, the WCC is also a strongly connected component. This module also includes many auxiliary functions that run on the WCC output. |
+
+**Table 5** Supported machine learning algorithms: time series
+
+| Algorithm Name                                 | Abbreviation | Application Scenario                                         |
+| :--------------------------------------------- | :----------- | :----------------------------------------------------------- |
+| Autoregressive integrated moving average model | ARIMA        | Time series forecasting, which is used to understand and forecast future values in the series.<br/>For example, international air traveler data can be used to forecast the number of passengers. |
+
+**Table 6** Supported machine learning algorithms - sampling
+
+| Algorithm Name      | Abbreviation | Application Scenario                                         |
+| :------------------ | :----------- | :----------------------------------------------------------- |
+| Sample              | -            | Sampling.                                                    |
+| Stratified sampling | -            | Stratified random sampling, also known as type random sampling, is used to divide the overall units into various types (or layers) according to a certain standard. Then, according to the ratio of the number of units of each type to the total number of units, the number of units extracted from each type is determined. Finally, samples are extracted from each type according to the random principle. |
+| Balanced sampling   | -            | Some classification algorithms only perform optimally when the number of samples in each class is roughly the same. Highly skewed datasets are common in many domains (such as fraud detection), so resampling to offset this imbalance can produce better decision boundaries. |
+
+**Table 7** Supported machine learning algorithms: statistics
+
+| Algorithm Name                   | Abbreviation | Application Scenario                                         |
+| :------------------------------- | :----------- | :----------------------------------------------------------- |
+| Summary                          | -            | This algorithm generates summary statistics for any data table. |
+| Correlation and covariance       | -            | Descriptive statistics, one of which computes the Pearson coefficient and correlation coefficient, and the other outputs covariance. This help us understand the characteristics of the data amount that is statistically reflected so that we can better understand the data to be mined. |
+| CountMin (Cormode-Muthukrishnan) | -            | This algorithm counts the occurrence frequency of an element in a real-time data stream, and is ready to response to the occurrence frequency of an element at any time. No accurate counting is required. |
+| Flajolet-Martin                  | FM           | This algorithm is used to obtain the number of different values in a specified column, and find the number of unique numbers in the number set. |
+| Most frequent values             | MFV          | This algorithm is used to compute frequent values.           |
+| Hypothesis test                  | -            | This algorithm includes F-test and chi2-test.                |
+| Probability functions            | -            | The probability functions module provides cumulative distribution, density/mass, and quantile functions for various probability distributions. |
+
+**Table 8** Supported machine learning algorithms: other algorithms
+
+| Algorithm Name              | Abbreviation | Application Scenario                                         |
+| :-------------------------- | :----------- | :----------------------------------------------------------- |
+| k-means clustering          | -            | This algorithm is used in the clustering scenario.           |
+| Latent Dirichlet allocation | LDA          | LDA plays an important role in the topic model and is often used for text classification. |
+| Apriori algorithm           | -            | Apriori algorithm is used to discover the association between data item sets, such as the typical "beer and diaper" association. |
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/7-deepsql/7-2-environment-deployment.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/7-deepsql/7-2-environment-deployment.md
new file mode 100644
index 0000000000000000000000000000000000000000..bc3bc927cf35efb7759ecf9a8420b289d17c08c3
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/7-deepsql/7-2-environment-deployment.md
@@ -0,0 +1,115 @@
+---
+title: Environment Deployment
+summary: Environment Deployment
+author: Guo Huan
+date: 2021-05-19
+---
+
+# Environment Deployment
+
+The DeepSQL environment consists of two parts: compiling the database and installing the algorithm library.
+
+## Prerequisites
+
+- Python 2.7.12 or later has been installed.
+- The database supports the PL/Python stored procedure.
+- You have the administrator permission to install the algorithm library.
+
+## Procedure
+
+1. Check the Python deployment environment.
+
+   Before the installation, check the Python version installed in the system. Currently, DeepSQL requires Python 2.7.12 or later.
+
+   - If the Python version is later than 2.7.12, you can directly install the **python-devel** package.
+   - If the version is too early or the **python-devel** package cannot be installed, download the latest Python 2 source code, manually configure and compile Python 2, and configure environment variables.
+
+   In the algorithm library, some algorithms, such as NumPy and pandas, call Python packages. You can install the following Python libraries:
+
+   ```
+   pip install numpy
+   pip install pandas
+   pip install scipy
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+   >
+   > - If you compile Python by yourself, you need to add the **-enable-shared** option when executing the **configure** script.
+   > - If Python 2 in the system uses the UCS4 code, you need to add the **-enable-unicode=ucs4** option when compiling Python 2. You can run the **import sys; print sys.maxunicode** command in the built-in Python 2 and view the result. If the result is **65535**, the system uses the UCS2 code by default. If the result is **1114111**, the system uses the UCS4 code.
+   > - If the built-in Python 2 uses UCS4, the gdb and gstack in the system also depend on UCS4. Therefore, when configuring Python 2, you need to add **-enable-unicode=ucs4**. Otherwise, an error is reported when gdb or gstack is used.
+
+2. Compile and deploy the database.
+
+   The database supports the PL/Python stored procedure. The database is compiled by default, and this module is not included. Therefore, you need to add the **-with-python** option in the **configure** phase when compiling the database.
+
+   Other compilation steps remain unchanged.
+
+   After the compilation is complete, run the **gs_initdb** command again.
+
+   By default, the PL/Python stored procedure module is not loaded. Run **CREATE EXTENSION plpythonu** to load the module.
+
+3. Compile and install the algorithm library.
+
+   The algorithm library uses the open-source MADlib machine learning framework. The source code package and patch can be obtained from the code repository of the third-party library. The installation commands are as follows:
+
+   ```bash
+   tar -zxf apache-madlib-1.17.0-src.tar.gz
+   cp madlib.patch apache-madlib-1.17.0-src
+   cd apache-madlib-1.17.0-src/
+   patch -p1 < madlib.patch
+   ```
+
+   The compilation commands are as follows:
+
+   ```bash
+   ./configure -DCMAKE_INSTALL_PREFIX={YOUR_MADLIB_INSTALL_FOLDER}
+   -DPOSTGRESQL_EXECUTABLE=$GAUSSHOME/bin/
+   -DPOSTGRESQL_9_2_EXECUTABLE=$GAUSSHOME/bin/
+   -DPOSTGRESQL_9_2_CLIENT_INCLUDE_DIR=$GAUSSHOME/bin/
+   -DPOSTGRESQL_9_2_SERVER_INCLUDE_DIR=$GAUSSHOME/bin/
+   # The preceding commands are all configure commands.
+   make
+   make install
+   ```
+
+   Replace **{YOUR_MADLIB_INSTALL_FOLDER}** with the actual installation path.
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** When MADlib is compiled, the dependency software is downloaded online. If the network cannot be connected, you need to manually download the dependency packages **PyXB-1.2.6.tar.gz**, **eigen-branches-3.2.tar.gz**, and **boost_1_61_0.tar.gz** to the local host. The **configure** commands are as follows:
+   >
+   > ```bash
+   > ./configure -DCMAKE_INSTALL_PREFIX={YOUR_MADLIB_INSTALL_FOLDER}                  # your install folder
+   > -DPYXB_TAR_SOURCE={YOUR_DEPENDENCY_FOLDER}/PyXB-1.2.6.tar.gz                     # change to your local folder
+   > -DEIGEN_TAR_SOURCE={YOUR_DEPENDENCY_FOLDER}/eigen-branches-3.2.tar.gz      # change to your local folder
+   > -DBOOST_TAR_SOURCE={YOUR_DEPENDENCY_FOLDER}/boost_1_61_0.tar.gz              # change to your local folder
+   > -DPOSTGRESQL_EXECUTABLE=$GAUSSHOME/bin/
+   > -DPOSTGRESQL_9_2_EXECUTABLE=$GAUSSHOME/bin/
+   > -DPOSTGRESQL_9_2_CLIENT_INCLUDE_DIR=$GAUSSHOME/bin/
+   > -DPOSTGRESQL_9_2_SERVER_INCLUDE_DIR=$GAUSSHOME/bin/
+   > ```
+
+4. Install the algorithm library in the database.
+
+   a. Go to the **{YOUR_MADLIB_INSTALL_FOLDER}** directory.
+
+   b. Go to the **bin** directory.
+
+   c. Run the following command:
+
+      ```bash
+      ./madpack -s <SCHEMA_NAME> -p opengauss -c <USER_NAME>@127.0.0.1:<PORT>/<DATABASE_NAME> install
+      ```
+
+      The options in the command are described as follows:
+
+      - **-s**: specifies the name of a schema.
+      - **-p**: database platform, which can be **mogdb**.
+      - **-c**: specifies parameters for connecting to the database, including the username, @, IP address, port number, and target database name.
+
+      **install** is the installation command. Besides, you can run the **reinstall** or **uninstall** commands.
+
+      > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+      >
+      > - The destination database must exist.
+      > - Use 127.0.0.1 instead of localhost as the IP address.
+      > - Operations such as installation and uninstallation of a large number of PL/Python stored procedures need to be performed by the database administrator. Common users do not have the permission to create or modify PL/Python stored procedures. They can only call the stored procedures.
+      > - The recommended database compatibility is B. The processing of empty and NULL values varies according to the database compatibility. B compatibility is recommended. Example: `CREATE DATABASE dbcompatibility='B'`.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/7-deepsql/7-3-usage-guide.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/7-deepsql/7-3-usage-guide.md
new file mode 100644
index 0000000000000000000000000000000000000000..722755de90b4473939ff171b98897b12e778fa32
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/7-deepsql/7-3-usage-guide.md
@@ -0,0 +1,226 @@
+---
+title: Usage Guide
+summary: Usage Guide
+author: Guo Huan
+date: 2021-05-19
+---
+
+# Usage Guide
+
+## PL/Python Stored Procedure
+
+Currently, the PL/Python stored procedure uses Python 2 by default.
+
+Functions in PL/Python are declared through the standard CREATE FUNCTION.
+
+```sql
+CREATE FUNCTION funcname (argument-list)
+RETURNS return-type
+AS $$
+# PL/Python function body
+$$ LANGUAGE plpythonu;
+```
+
+The function body is a simple Python script. When the function is called, its arguments are input as the elements of the list **args**. Named arguments are also input to the Python script as common variables. Named arguments are usually easier to read. The result is returned from Python code as usual using **return** or **yield** (in the case of a result set statement). If no return value is provided, Python returns **None** by default. PL/Python considers **None** in Python as the SQL NULL value.
+
+For example, the function that returns the larger of two integers is defined as follows:
+
+```sql
+CREATE FUNCTION pymax(a integer, b integer) RETURNS integer AS $$
+if a > b:
+    return a
+return b
+$$ LANGUAGE plpythonu;
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **CAUTION:**
+>
+> - In the PL/Python function, the suffix is **plpythonu**. **u** indicates that the stored procedure is of the untrusted type.
+> - **Trusted**: This language cannot be used to access unauthorized data. For example, files of the database server and internal database (including direct access to the shared memory).
+> - **Untrusted**: This language has no restrictions and allows access to any data (including files, networks, and shared libraries). It is hazardous but has more powerful functions.
+> - PL/Python is an untrusted stored procedure language. Currently, only administrators can create and modify PL/Python. Common users can only use PL/Python.
+> - When defining PL/Python stored procedures, do not define the risky statement execution such as **import os; os.system("rm -rf /")**. Users with administrator permission need to create such PL/Python stored procedures with caution.
+
+## Processing of NULL, None, and Empty Strings in the Database
+
+If an SQL NULL value is input to the function, the parameter value is displayed as **None** in Python. In the database, empty strings are treated as NULL due to different compatibility.
+
+The performance of the same function varies depending on the compatibility.
+
+```sql
+CREATE FUNCTION quote(t text, how text) RETURNS text AS $$
+if how == "literal":
+    return plpy.quote_literal(t)
+elif how == "nullable":
+    return plpy.quote_nullable(t)
+elif how == "ident":
+    return plpy.quote_ident(t)
+else:
+    raise plpy.Error("unrecognized quote type %s" % how)
+$$ LANGUAGE plpythonu;
+```
+
+**Example 1:**
+
+```sql
+SELECT quote(t, 'literal') FROM (VALUES ('abc'),('a''bc'),('''abc'''),(''),(''''),('xyzv')) AS v(t);
+```
+
+Results of different database compatibility are as follows:
+
+- If the compatibility is A, the returned result is as follows:
+
+  ```sql
+  ERROR:  TypeError: argument 1 must be string, not None
+  CONTEXT:  Traceback (most recent call last):
+  PL/Python function "quote", line 3, in <module>
+  return plpy.quote_literal(t)
+  referenced column: quote
+  ```
+
+- If the compatibility is B, the returned result is as follows:
+
+  ```sql
+  quote
+  -----------
+  'abc'
+  'a''bc'
+  '''abc'''
+  ''
+  ''''
+  'xyzv'
+  (6 rows)
+  ```
+
+**Example 2:**
+
+```sql
+SELECT quote(t, 'nullable') FROM (VALUES ('abc'),('a''bc'),('''abc'''),(''),(''''),(NULL)) AS v(t);
+```
+
+Results of different database compatibility are as follows:
+
+- If the compatibility is A, the returned result is as follows:
+
+  ```sql
+  quote
+  -----------
+  'abc'
+  'a''bc'
+  '''abc'''
+  NULL
+  ''''
+  NULL
+  (6 rows)
+  ```
+
+- If the compatibility is B, the returned result is as follows:
+
+  ```sql
+  quote
+  -----------
+  'abc'
+  'a''bc'
+  '''abc'''
+  ''
+  ''''
+  NULL
+  (6 rows)
+  ```
+
+In the preceding examples, the empty string is regarded as NULL when the compatibility is A.
+
+## Triggers
+
+Currently, the PL/Python stored procedure does not support triggers.
+
+## Anonymous Block of Code
+
+PL/Python also supports anonymous block of code declared by DO:
+
+```sql
+DO $$
+# PL/Python code
+$$ LANGUAGE plpythonu;
+```
+
+An anonymous block of code does not accept parameters and discards values they return.
+
+## Sharing Data
+
+Each function gets its own execution environment in the Python interpreter.
+
+The global dictionary SD is used to store data between function calls. These variables are private static data. Each function has its own SD space. The global data and parameters of function A cannot be used by function B.
+
+The global dictionary GD is public data. In a gsql session, all Python functions can be accessed and changed. Exercise caution when using the global dictionary.
+
+When gsql is disconnected or exited, the sharing data is released.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **CAUTION:**
+>
+> - When running the DeepSQL or PL/Python stored procedure, you need to disable the parameters related to the thread pool. Otherwise, the functions such as sharing data (GD and SD) in the PL/Python stored procedure are invalid.
+> - In the database, when the thread pool function is disabled, a new thread is started in the database for each connected gsql. In gsql, if the PL/Python stored procedure is called, the Python parser module is initialized in this thread, including initializing the sharing space such as GD and SD.
+> - When the thread pool function is enabled, an idle thread executes the gsql command. Each execution may be allocated to a different thread. As a result, the sharing data is disordered.
+
+## Database Access
+
+The PL/Python language module automatically imports a Python module called plpy.
+
+The plpy module provides several functions to execute database commands, such as plpy.execute and plpy.prepare.
+
+The plpy module also provides the following functions: plpy.debug(msg), plpy.log(msg), plpy.info(msg), plpy.notice(msg), plpy.warning(msg), plpy.error(msg), and plpy.fatal(msg). The plpy.error and plpy.fatal throw a Python exception, which causes the current transaction or sub-transaction to exit.
+
+Another set of useful functions is plpy.quote_literal(string), plpy.quote_nullable(string), and plpy.quote_ident(string).
+
+## Audit
+
+PL/Python stored procedures support the audit function. For details, see [Auditing](1-audit-switch).
+
+## Concurrent Execution
+
+Currently, PL/Python stored procedures are not friendly to concurrent execution. You are advised to execute them in serial mode.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** Due to the MogDB multi-thread architecture and the restriction of GlobalInterpreter Lock (GIL) in C-python, multiple threads can only be executed alternately in Python, and concurrent operations cannot be implemented.
+
+## Algorithms in the Library
+
+For details about algorithms in the library and how to use them, see the official [MADlib document](http://madlib.apache.org/docs/latest/index.html).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - Currently, only the machine learning algorithm is supported. The deep learning module is not supported.
+> - The current database does not support XML files. Therefore, the pmml module and related functions are not supported.
+> - The database does not support the jsonb module, and the model export function in JSON format is not supported.
+
+## Other Supported Algorithms
+
+In addition to the algorithms provided by MADlib, MogDB provides the following three algorithms:
+
+**Table 1** Additional modules
+
+| Algorithm Name                    | Abbreviation     |
+| :-------------------------------- | :--------------- |
+| Gradient boosted tree             | gbdt             |
+| Gradient boosting                 | xgboost          |
+| Time series forecasting algorithm | facebook_prophet |
+
+You need to install Python libraries which the preceding algorithms depend on as follows:
+
+- If the prophet algorithm is used:
+
+  ```bash
+  pip install pystan
+  pip install holidays==0.9.8
+  pip install fbprophet==0.3.post2
+  ```
+
+- If the xgboost algorithm is used:
+
+  ```bash
+  pip install xgboost
+  pip install scikit-learn
+  ```
+
+- The gbdt algorithm does not require library installation.
+
+For details, see [Best Practices](7-4-best-practices).
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/7-deepsql/7-4-best-practices.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/7-deepsql/7-4-best-practices.md
new file mode 100644
index 0000000000000000000000000000000000000000..d7aea6eea1d39e676ff2e0848d154fa3a1240509
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/7-deepsql/7-4-best-practices.md
@@ -0,0 +1,888 @@
+---
+title: Best Practices
+summary: Best Practices
+author: Guo Huan
+date: 2021-05-19
+---
+
+# Best Practices
+
+This section describes how to use certain algorithms, including the classification, regression, clustering, gbdt, xgboost, and prohpet algorithms.
+
+Create a database and install an algorithm.
+
+```
+create database test1 dbcompatibility='B';
+./madpack -s madlib -p mogdb -c opg@127.0.0.1:7651/test1 install
+```
+
+## Classification Algorithm
+
+Take the housing price prediction with the support vector machine (SVM) as an example:
+
+1. Prepare a dataset.
+
+   ```
+   DROP TABLE IF EXISTS houses;
+   CREATE TABLE houses (id INT, tax INT, bedroom INT, bath FLOAT, price INT,  size INT, lot INT);
+   INSERT INTO houses VALUES
+   (1 ,  590 ,       2 ,    1 ,  50000 ,  770 , 22100),
+   (2 , 1050 ,       3 ,    2 ,  85000 , 1410 , 12000),
+   (3 ,   20 ,       3 ,    1 ,  22500 , 1060 ,  3500),
+   (4 ,  870 ,       2 ,    2 ,  90000 , 1300 , 17500),
+   (5 , 1320 ,       3 ,    2 , 133000 , 1500 , 30000),
+   (6 , 1350 ,       2 ,    1 ,  90500 ,  820 , 25700),
+   (7 , 2790 ,       3 ,  2.5 , 260000 , 2130 , 25000),
+   (8 ,  680 ,       2 ,    1 , 142500 , 1170 , 22000),
+   (9 , 1840 ,       3 ,    2 , 160000 , 1500 , 19000),
+   (10 , 3680 ,       4 ,    2 , 240000 , 2790 , 20000),
+   (11 , 1660 ,       3 ,    1 ,  87000 , 1030 , 17500),
+   (12 , 1620 ,       3 ,    2 , 118600 , 1250 , 20000),
+   (13 , 3100 ,       3 ,    2 , 140000 , 1760 , 38000),
+   (14 , 2070 ,       2 ,    3 , 148000 , 1550 , 14000),
+   (15 ,  650 ,       3 ,  1.5 ,  65000 , 1450 , 12000);
+   ```
+
+2. Train the model.
+
+   Configure the corresponding schema and compatibility parameters before training.
+
+   ```
+   SET search_path="$user",public,madlib;
+   SET behavior_compat_options = 'bind_procedure_searchpath';
+   ```
+
+   Use default parameters for training. The classification condition is 'price &lt; 100000'. The SQL statement is as follows:
+
+   ```
+   DROP TABLE IF EXISTS houses_svm, houses_svm_summary;
+   SELECT madlib.svm_classification('public.houses','public.houses_svm','price < 100000','ARRAY[1, tax, bath, size]');
+   ```
+
+3. View the model.
+
+   ```
+   \x on
+   SELECT * FROM houses_svm;
+   \x off
+   ```
+
+   The results are displayed as follows:
+
+   ```
+   -[ RECORD 1 ]------+-----------------------------------------------------------------
+   coef               | {.113989576847,-.00226133300602,-.0676303607996,.00179440841072}
+   loss               | .614496714256667
+   norm_of_gradient   | 108.171180769224
+   num_iterations     | 100
+   num_rows_processed | 15
+   num_rows_skipped   | 0
+   dep_var_mapping    | {f,t}
+   ```
+
+4. Perform prediction.
+
+   ```
+   DROP TABLE IF EXISTS houses_pred;
+   SELECT madlib.svm_predict('public.houses_svm','public.houses','id','public.houses_pred');
+   ```
+
+   - View the prediction result.
+
+     ```
+     SELECT *, price < 100000 AS actual FROM houses JOIN houses_pred USING (id) ORDER BY id;
+     ```
+
+     The results are displayed as follows:
+
+     ```
+      id | tax  | bedroom | bath | price  | size |  lot  | prediction | decision_function | actual
+     ----+------+---------+------+--------+------+-------+------------+-------------------+--------
+      1 |  590 |       2 |    1 |  50000 |  770 | 22100 | t          |      .09386721875 | t
+      2 | 1050 |       3 |    2 |  85000 | 1410 | 12000 | t          |     .134445058042 | t
+      3 |   20 |       3 |    1 |  22500 | 1060 |  3500 | t          |   1.9032054712902 | t
+      4 |  870 |       2 |    2 |  90000 | 1300 | 17500 | t          |    .3441000739464 | t
+      5 | 1320 |       3 |    2 | 133000 | 1500 | 30000 | f          |   -.3146180966186 | f
+      6 | 1350 |       2 |    1 |  90500 |  820 | 25700 | f          |  -1.5350254452892 | t
+      7 | 2790 |       3 |  2.5 | 260000 | 2130 | 25000 | f          |  -2.5421154971142 | f
+      8 |  680 |       2 |    1 | 142500 | 1170 | 22000 | t          |    .6081106124962 | f
+      9 | 1840 |       3 |    2 | 160000 | 1500 | 19000 | f          |   -1.490511259749 | f
+     10 | 3680 |       4 |    2 | 240000 | 2790 | 20000 | f          |   -3.336577140997 | f
+     11 | 1660 |       3 |    1 |  87000 | 1030 | 17500 | f          |  -1.8592129109042 | t
+     12 | 1620 |       3 |    2 | 118600 | 1250 | 20000 | f          |  -1.4416201011046 | f
+     13 | 3100 |       3 |    2 | 140000 | 1760 | 38000 | f          |   -3.873244660547 | f
+     14 | 2070 |       2 |    3 | 148000 | 1550 | 14000 | f          |  -1.9885277913972 | f
+     15 |  650 |       3 |  1.5 |  65000 | 1450 | 12000 | t          |   1.1445697772786 | t
+     (15 rows)
+     ```
+
+   - View the false positive rate.
+
+     ```
+     SELECT COUNT(*) FROM houses_pred JOIN houses USING (id) WHERE houses_pred.prediction != (houses.price < 100000);
+     ```
+
+     The results are displayed as follows:
+
+     ```
+     count
+     -------
+          3
+     (1 row)
+     ```
+
+5. Use other SVM cores for training.
+
+   ```
+   DROP TABLE IF EXISTS houses_svm_gaussian, houses_svm_gaussian_summary, houses_svm_gaussian_random;
+   SELECT madlib.svm_classification( 'public.houses','public.houses_svm_gaussian','price < 100000','ARRAY[1, tax, bath, size]','gaussian','n_components=10', '', 'init_stepsize=1, max_iter=200' );
+   ```
+
+   Perform prediction and view the training result.
+
+   ```
+   DROP TABLE IF EXISTS houses_pred_gaussian;
+   SELECT madlib.svm_predict('public.houses_svm_gaussian','public.houses','id', 'public.houses_pred_gaussian');
+   SELECT COUNT(*) FROM houses_pred_gaussian JOIN houses USING (id) WHERE houses_pred_gaussian.prediction != (houses.price < 100000);
+   ```
+
+   The result is as follows:
+
+   ```
+    count
+   -------+
+   0
+   (1 row)
+   ```
+
+6. Use other parameters.
+
+   In addition to specifying different kernel methods, you can specify the number of training steps and initial parameters, such as **init_stepsize**, **max_iter**, and **class_weight**.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> ```
+> SET search_path="$user",public,madlib;
+> SET behavior_compat_options = 'bind_procedure_searchpath';
+> ```
+>
+> Before executing the algorithm, you need to set the schema in **search_path** and set the **bind_procedure_searchpath**. Otherwise, the table cannot be found. All machine learning methods are installed in a schema, and user tables are installed in user's schemas. In this example, the algorithm is installed in **madlib**, and user tables are stored in **public**. If no schema is set, the table may not be found when the algorithm is executed. When executing the algorithm, you are advised to add the scheme of the input table.
+
+## Regression Algorithm
+
+Use the Boston housing price prediction with the linear regression as an example:
+
+1. Prepare a dataset.
+
+   The dataset is the same as that of the SVM.
+
+2. Train a model.
+
+   ```
+   SET search_path="$user",public,madlib;
+   SET behavior_compat_options = 'bind_procedure_searchpath';
+
+   DROP TABLE IF EXISTS houses_linregr, houses_linregr_summary;
+   SELECT madlib.linregr_train( 'public.houses', 'public.houses_linregr',  'price', 'ARRAY[1, tax, bath, size]');
+   ```
+
+3. View the model content.
+
+   ```
+   \x ON
+   SELECT * FROM houses_linregr;
+   \x OFF
+   ```
+
+   The returned result is as follows:
+
+   ```
+   -[ RECORD 1 ]------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+   coef                     | {-12849.4168959872,28.9613922651775,10181.6290712649,50.516894915353}
+   r2                       | .768577580597462
+   std_err                  | {33453.0344331377,15.8992104963991,19437.7710925915,32.9280231740856}
+   t_stats                  | {-.384103179688204,1.82156166004197,.523806408809163,1.53416118083608}
+   p_values                 | {.708223134615411,.0958005827189556,.610804093526516,.153235085548177}
+   condition_no             | 9002.50457069858
+   num_rows_processed       | 15
+   num_missing_rows_skipped | 0
+   variance_covariance      | {{1119105512.7847,217782.067878005,-283344228.394538,-616679.693190829},{217782.067878005,252.784894408806,-46373.1796964038,-369.864520095145},{-283344228.394538,-46373.1796964038,377826945.047986,-209088.217319699},{-616679.693190829,-369.864520095145,-209088.217319699,1084.25471015312}}
+   ```
+
+4. Predict and compare the results.
+
+   ```
+   SELECT houses.*,
+       madlib.linregr_predict( m.coef, ARRAY[1,tax,bath,size]) as predict,
+       price - madlib.linregr_predict( m.coef, ARRAY[1,tax,bath,size]) as residual
+   FROM public.houses, public.houses_linregr AS m
+   ORDER BY id;
+   ```
+
+   The returned result is as follows:
+
+   ```
+    id | tax  | bedroom | bath | price  | size |  lot  |     predict      |     residual
+   ----+------+---------+------+--------+------+-------+------------------+-------------------
+    1 |  590 |       2 |    1 |  50000 |  770 | 22100 | 53317.4426965543 | -3317.44269655428
+    2 | 1050 |       3 |    2 |  85000 | 1410 | 12000 | 109152.124955627 | -24152.1249556268
+    3 |   20 |       3 |    1 |  22500 | 1060 |  3500 | 51459.3486308555 | -28959.3486308555
+    4 |  870 |       2 |    2 |  90000 | 1300 | 17500 |  98382.215907206 | -8382.21590720599
+    5 | 1320 |       3 |    2 | 133000 | 1500 | 30000 | 121518.221409606 |  11481.7785903935
+    6 | 1350 |       2 |    1 |  90500 |  820 | 25700 | 77853.9455638568 |  12646.0544361432
+    7 | 2790 |       3 |  2.5 | 260000 | 2130 | 25000 | 201007.926371722 |  58992.0736282778
+    8 |  680 |       2 |    1 | 142500 | 1170 | 22000 | 76130.7259665615 |  66369.2740334385
+    9 | 1840 |       3 |    2 | 160000 | 1500 | 19000 | 136578.145387499 |  23421.8546125013
+   10 | 3680 |       4 |    2 | 240000 | 2790 | 20000 | 255033.901596231 | -15033.9015962306
+   11 | 1660 |       3 |    1 |  87000 | 1030 | 17500 | 97440.5250982859 | -10440.5250982859
+   12 | 1620 |       3 |    2 | 118600 | 1250 | 20000 | 117577.415360321 |  1022.58463967856
+   13 | 3100 |       3 |    2 | 140000 | 1760 | 38000 | 186203.892319614 | -46203.8923196141
+   14 | 2070 |       2 |    3 | 148000 | 1550 | 14000 | 155946.739425522 | -7946.73942552213
+   15 |  650 |       3 |  1.5 |  65000 | 1450 | 12000 | 94497.4293105374 | -29497.4293105374
+   (15 rows)
+   ```
+
+## Clustering Algorithm
+
+Use kmeans as an example:
+
+1. Prepare the data.
+
+   ```
+   DROP TABLE IF EXISTS km_sample;
+   CREATE TABLE km_sample(pid int, points double precision[]);
+   INSERT INTO km_sample VALUES
+   (1,  '{14.23, 1.71, 2.43, 15.6, 127, 2.8, 3.0600, 0.2800, 2.29, 5.64, 1.04, 3.92, 1065}'),
+   (2,  '{13.2, 1.78, 2.14, 11.2, 1, 2.65, 2.76, 0.26, 1.28, 4.38, 1.05, 3.49, 1050}'),
+   (3,  '{13.16, 2.36,  2.67, 18.6, 101, 2.8,  3.24, 0.3, 2.81, 5.6799, 1.03, 3.17, 1185}'),
+   (4,  '{14.37, 1.95, 2.5, 16.8, 113, 3.85, 3.49, 0.24, 2.18, 7.8, 0.86, 3.45, 1480}'),
+   (5,  '{13.24, 2.59, 2.87, 21, 118, 2.8, 2.69, 0.39, 1.82, 4.32, 1.04, 2.93, 735}'),
+   (6,  '{14.2, 1.76, 2.45, 15.2, 112, 3.27, 3.39, 0.34, 1.97, 6.75, 1.05, 2.85, 1450}'),
+   (7,  '{14.39, 1.87, 2.45, 14.6, 96, 2.5, 2.52, 0.3, 1.98, 5.25, 1.02, 3.58, 1290}'),
+   (8,  '{14.06, 2.15, 2.61, 17.6, 121, 2.6, 2.51, 0.31, 1.25, 5.05, 1.06, 3.58, 1295}'),
+   (9,  '{14.83, 1.64, 2.17, 14, 97, 2.8, 2.98, 0.29, 1.98, 5.2, 1.08, 2.85, 1045}'),
+   (10, '{13.86, 1.35, 2.27, 16, 98, 2.98, 3.15, 0.22, 1.8500, 7.2199, 1.01, 3.55, 1045}');
+   ```
+
+2. Run the kmeans algorithm.
+
+   Use kmeans++ and Euclidean distance function for calculation.
+
+   ```
+   SET search_path="$user",public,madlib;
+   SET behavior_compat_options = 'bind_procedure_searchpath';
+
+   DROP TABLE IF EXISTS km_result;
+   CREATE TABLE km_result AS SELECT * FROM madlib.kmeanspp( 'public.km_sample',   -- Table of source data
+                                                            'points',      -- Column containing point co-ordinates
+                                                            2,             -- Number of centroids to calculate
+                                                            'madlib.squared_dist_norm2',   -- Distance function
+                                                            'madlib.avg',  -- Aggregate function
+                                                            20,            -- Number of iterations
+                                                            0.001          -- Fraction of centroids reassigned to keep iterating
+   );
+   ```
+
+   After kmeans is executed, no table is automatically created to save the content. Therefore, you need to create a table.
+
+   ```
+   \x on
+    select * from km_result;
+   \x off
+   ```
+
+   The returned result is as follows:
+
+   ```
+   -[ RECORD 1 ]----+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+   centroids        | {{14.0333333333333,1.84111111111111,2.41,15.5111111111111,96.2222222222222,2.91666666666667,3.01111111111111,.282222222222222,1.95444444444444,5.88553333333333,1.02222222222222,3.38222222222222,1211.66666666667},{13.24,2.59,2.87,21,118,2.8,2.69,.39,1.82,4.32,1.04,2.93,735}}
+   cluster_variance | {257041.999707571,0}
+   objective_fn     | 257041.999707571
+   frac_reassigned  | 0
+   num_iterations   | 2
+   ```
+
+3. Apply the clustering result.
+
+   Execute the following function to calculate the adjacent node and the corresponding distance of each node:
+
+   ```
+   DROP TABLE IF EXISTS km_points_silh;
+   SELECT * FROM madlib.simple_silhouette_points('public.km_sample',          -- Input points table
+                                                 'public.km_points_silh',      -- Output table
+                                                 'pid',                 -- Point ID column in input table
+                                                 'points',              -- Points column in input table
+                                                 'public.km_result',           -- Centroids table
+                                                 'centroids',           -- Column in centroids table containing centroids
+                                                 'madlib.squared_dist_norm2'   -- Distance function
+   );
+   SELECT * FROM km_points_silh ORDER BY pid;
+   ```
+
+   The returned result is as follows:
+
+   ```
+    pid | centroid_id | neighbor_centroid_id |       silh
+   -----+-------------+----------------------+------------------
+     1 |           0 |                    1 | .793983543638996
+     2 |           0 |                    1 | .688301735667703
+     3 |           0 |                    1 | .996324103148159
+     4 |           0 |                    1 | .869765755931474
+     5 |           1 |                    0 |                1
+     6 |           0 |                    1 | .888416176253661
+     7 |           0 |                    1 | .980107240092519
+     8 |           0 |                    1 | .975880363039906
+     9 |           0 |                    1 | .712384473959954
+    10 |           0 |                    1 | .712198411442872
+   (10 rows)
+   ```
+
+## gbdt Algorithm
+
+Although the gdbt base learner is a regression tree, the algorithm itself supports both classification and regression operations. The following describes the implementation of the two types of tasks. It is worth noting that this method does not support NULL values in the label column.
+
+**Classification**
+
+1. Prepare the data.
+
+   ```
+   DROPTABLEIFEXISTS dt_golf CASCADE;
+   DROPTABLEIFEXISTS train_output,train_output_summary;
+   CREATETABLE dt_golf (
+       id integerNOTNULL,
+   "OUTLOOK"text,
+       temperature double precision,
+       humidity double precision,
+   "Cont_features"double precision[],
+       cat_features text[],
+       windy boolean,
+       class integer
+   ) ;
+   INSERTINTO dt_golf (id,"OUTLOOK",temperature,humidity,"Cont_features",cat_features, windy,class) VALUES
+   (1, 'sunny', 85, 85,ARRAY[85, 85], ARRAY['a', 'b'], false, 0),
+   (2, 'sunny', 80, 90, ARRAY[80, 90], ARRAY['a', 'b'], true, 0),
+   (3, 'overcast', 83, 78, ARRAY[83, 78], ARRAY['a', 'b'], false, 1),
+   (4, 'rain', 70, NULL, ARRAY[70, 96], ARRAY['a', 'b'], false, 1),
+   (5, 'rain', 68, 80, ARRAY[68, 80], ARRAY['a', 'b'], false, 1),
+   (6, 'rain', NULL, 70, ARRAY[65, 70], ARRAY['a', 'b'], true, 0),
+   (7, 'overcast', 64, 65, ARRAY[64, 65], ARRAY['c', 'b'], NULL , 1),
+   (8, 'sunny', 72, 95, ARRAY[72, 95], ARRAY['a', 'b'], false, 0),
+   (9, 'sunny', 69, 70, ARRAY[69, 70], ARRAY['a', 'b'], false, 1),
+   (10, 'rain', 75, 80, ARRAY[75, 80], ARRAY['a', 'b'], false, 1),
+   (11, 'sunny', 75, 70, ARRAY[75, 70], ARRAY['a', 'd'], true, 1),
+   (12, 'overcast', 72, 90, ARRAY[72, 90], ARRAY['c', 'b'], NULL, 1),
+   (13, 'overcast', 81, 75, ARRAY[81, 75], ARRAY['a', 'b'], false, 1),
+   (15, NULL, 81, 75, ARRAY[81, 75], ARRAY['a', 'b'], false, 1),
+   (16, 'overcast', NULL, 75, ARRAY[81, 75], ARRAY['a', 'd'], false,1),
+   (14, 'rain', 71, 80, ARRAY[71, 80], ARRAY['c', 'b'], true, 0);
+   ```
+
+2. Train a model.
+
+   ```
+   select madlib.gbdt_train('dt_golf',         -- source table
+                     'train_output',    -- output model table
+                     'id'  ,            -- id column
+                     'class',           -- response
+                     '"OUTLOOK", temperature',          -- features
+                     NULL,        -- exclude columns
+                     1,       --weight
+                     10,                -- num of trees
+                     NULL,                 -- num of random features
+                     10,       -- max depth
+                     1,        -- min split
+                     1,        -- min bucket
+                     8,        -- number of bins per continuous variable
+                     'max_surrogates=0',
+                     TRUE
+   );
+   ```
+
+   After the model training is complete, two tables are generated. The **train_output** table stores the regression tree model in gdbt, including the parameter records of each base learner.
+
+   ```
+          Column       |     Type      | Modifiers | Storage  | Stats target | Description
+   --------------------+---------------+-----------+----------+--------------+-------------
+   iteration          | integer       |           | plain    |              |
+   tree               | madlib.bytea8 |           | external |              |
+   cat_levels_in_text | text[]        |           | extended |              |
+   cat_n_levels       | integer[]     |           | extended |              |
+   tree_depth         | integer       |           | plain    |              |
+   ```
+
+   ```
+    iteration |  cat_levels_in_text   | cat_n_levels | tree_depth
+   -----------+-----------------------+--------------+------------
+           0 | {sunny,rain,overcast} | {3}          |          4
+           1 | {sunny,rain,overcast} | {3}          |          5
+           2 | {sunny,rain,overcast} | {3}          |          6
+           3 | {sunny,rain,overcast} | {3}          |          4
+           4 | {sunny,rain,overcast} | {3}          |          5
+           5 | {sunny,rain,overcast} | {3}          |          5
+           6 | {sunny,rain,overcast} | {3}          |          5
+           7 | {sunny,rain,overcast} | {3}          |          5
+           8 | {sunny,rain,overcast} | {3}          |          4
+           9 | {sunny,rain,overcast} | {3}          |          3
+   (10 rows)
+   ```
+
+   The **train_output_summary** table describes the gdbt training.
+
+   ```
+   select * from train_output_summary;
+    method | cat_features | con_features | source_table | model_table  | null_proxy | learning_rate | is_classification | predict_dt_prob | num_trees
+   --------+--------------+--------------+--------------+--------------+------------+---------------+-------------------+-----------------+-----------
+    GBDT   | "OUTLOOK"    | temperature  | dt_golf      | train_output |            |           .01 | t                 | response        |        10
+   (1 row)
+   ```
+
+3. Perform prediction.
+
+   ```
+   select madlib.gbdt_predict('dt_golf2','train_output','test_output','id');
+   ```
+
+   View the prediction result.
+
+   ```
+   select test_output.id, test_prediction,class from test_output join dt_golf using (id);
+   id | test_prediction | class
+   ----+-----------------+-------
+     1 |             1.0 |     0
+     2 |             1.0 |     0
+     3 |             1.0 |     1
+     4 |             1.0 |     1
+     5 |             1.0 |     1
+     6 |             1.0 |     0
+     7 |             1.0 |     1
+     8 |             0.0 |     0
+     9 |             1.0 |     1
+    10 |             1.0 |     1
+    11 |             1.0 |     1
+    12 |             1.0 |     1
+    13 |             1.0 |     1
+    15 |             0.0 |     1
+    16 |             1.0 |     1
+    14 |             0.0 |     0
+   (16 rows)
+   ```
+
+## **Regression**
+
+1. Prepare the data.
+
+   ```
+   DROP TABLE IF EXISTS crime;
+   CREATE TABLE crime (
+       id SERIAL NOT NULL,
+       CrimeRat DOUBLE PRECISION,
+       MaleTeen INTEGER,
+       South SMALLINT,
+       Educ DOUBLE PRECISION,
+       Police60 INTEGER,
+       Police59 INTEGER,
+       Labor INTEGER,
+       Males INTEGER,
+       Pop   INTEGER,
+       NonWhite INTEGER,
+       Unemp1  INTEGER,
+       Unemp2  INTEGER,
+       Median  INTEGER,
+       BelowMed INTEGER
+   );
+
+   INSERT INTO crime(
+       CrimeRat, MaleTeen, South, Educ, Police60, Police59, Labor, Males, Pop,
+       NonWhite, Unemp1, Unemp2, Median, BelowMed
+   ) VALUES
+   (79.1, 151, 1, 9.1, 58, 56, 510, 950, 33, 301, 108, 41, 394, 261),
+   (163.5, 143, 0, 11.3, 103, 95, 583, 1012, 13, 102, 96, 36, 557, 194),
+   (57.8, 142, 1, 8.9, 45, 44, 533, 969, 18, 219, 94, 33, 318, 250),
+   (196.9, 136, 0, 12.1, 149, 141, 577, 994, 157, 80, 102, 39, 673, 167),
+   (123.4, 141, 0, 12.1, 109, 101, 591, 985, 18, 30, 91, 20, 578, 174),
+   (68.2, 121, 0, 11.0, 118, 115, 547, 964, 25, 44, 84, 29, 689, 126),
+   (96.3, 127, 1, 11.1, 82, 79, 519, 982, 4, 139, 97, 38, 620, 168),
+   (155.5, 131, 1, 10.9, 115, 109, 542, 969, 50, 179, 79, 35, 472, 206),
+   (85.6, 157, 1, 9.0, 65, 62, 553, 955, 39, 286, 81, 28, 421, 239),
+   (70.5, 140, 0, 11.8, 71, 68, 632, 1029, 7, 15, 100, 24, 526, 174),
+   (167.4, 124, 0, 10.5, 121, 116, 580, 966, 101, 106, 77, 35, 657, 170),
+   (84.9, 134, 0, 10.8, 75, 71, 595, 972, 47, 59, 83, 31, 580, 172),
+   (51.1, 128, 0, 11.3, 67, 60, 624, 972, 28, 10, 77, 25, 507, 206),
+   (66.4, 135, 0, 11.7, 62, 61, 595, 986, 22, 46, 77, 27, 529, 190),
+   (79.8, 152, 1, 8.7, 57, 53, 530, 986, 30, 72, 92, 43, 405, 264),
+   (94.6, 142, 1, 8.8, 81, 77, 497, 956, 33, 321, 116, 47, 427, 247),
+   (53.9, 143, 0, 11.0, 66, 63, 537, 977, 10, 6, 114, 35, 487, 166),
+   (92.9, 135, 1, 10.4, 123, 115, 537, 978, 31, 170, 89, 34, 631, 165),
+   (75.0, 130, 0, 11.6, 128, 128, 536, 934, 51, 24, 78, 34, 627, 135),
+   (122.5, 125, 0, 10.8, 113, 105, 567, 985, 78, 94, 130, 58, 626, 166),
+   (74.2, 126, 0, 10.8, 74, 67, 602, 984, 34, 12, 102, 33, 557, 195),
+   (43.9, 157, 1, 8.9, 47, 44, 512, 962, 22, 423, 97, 34, 288, 276),
+   (121.6, 132, 0, 9.6, 87, 83, 564, 953, 43, 92, 83, 32, 513, 227),
+   (96.8, 131, 0, 11.6, 78, 73, 574, 1038, 7, 36, 142, 42, 540, 176),
+   (52.3, 130, 0, 11.6, 63, 57, 641, 984, 14, 26, 70, 21, 486, 196),
+   (199.3, 131, 0, 12.1, 160, 143, 631, 1071, 3, 77, 102, 41, 674, 152),
+   (34.2, 135, 0, 10.9, 69, 71, 540, 965, 6, 4, 80, 22, 564, 139),
+   (121.6, 152, 0, 11.2, 82, 76, 571, 1018, 10, 79, 103, 28, 537, 215),
+   (104.3, 119, 0, 10.7, 166, 157, 521, 938, 168, 89, 92, 36, 637, 154),
+   (69.6, 166, 1, 8.9, 58, 54, 521, 973, 46, 254, 72, 26, 396, 237),
+   (37.3, 140, 0, 9.3, 55, 54, 535, 1045, 6, 20, 135, 40, 453, 200),
+   (75.4, 125, 0, 10.9, 90, 81, 586, 964, 97, 82, 105, 43, 617, 163),
+   (107.2, 147, 1, 10.4, 63, 64, 560, 972, 23, 95, 76, 24, 462, 233),
+   (92.3, 126, 0, 11.8, 97, 97, 542, 990, 18, 21, 102, 35, 589, 166),
+   (65.3, 123, 0, 10.2, 97, 87, 526, 948, 113, 76, 124, 50, 572, 158),
+   (127.2, 150, 0, 10.0, 109, 98, 531, 964, 9, 24, 87, 38, 559, 153),
+   (83.1, 177, 1, 8.7, 58, 56, 638, 974, 24, 349, 76, 28, 382, 254),
+   (56.6, 133, 0, 10.4, 51, 47, 599, 1024, 7, 40, 99, 27, 425, 225),
+   (82.6, 149, 1, 8.8, 61, 54, 515, 953, 36, 165, 86, 35, 395, 251),
+   (115.1, 145, 1, 10.4, 82, 74, 560, 981, 96, 126, 88, 31, 488, 228),
+   (88.0, 148, 0, 12.2, 72, 66, 601, 998, 9, 19, 84, 20, 590, 144),
+   (54.2, 141, 0, 10.9, 56, 54, 523, 968, 4, 2, 107, 37, 489, 170),
+   (82.3, 162, 1, 9.9, 75, 70, 522, 996, 40, 208, 73, 27, 496, 224),
+   (103.0, 136, 0, 12.1, 95, 96, 574, 1012, 29, 36, 111, 37, 622, 162),
+   (45.5, 139, 1, 8.8, 46, 41, 480, 968, 19, 49, 135, 53, 457, 249),
+   (50.8, 126, 0, 10.4, 106, 97, 599, 989, 40, 24, 78, 25, 593, 171),
+   (84.9, 130, 0, 12.1, 90, 91, 623, 1049, 3, 22, 113, 40, 588, 160);
+   ```
+
+2. Train a model.
+
+   ```
+   select madlib.gbdt_train('crime',         -- source table
+                     'train_output',    -- output model table
+                     'id'  ,            -- id column
+                     'CrimeRat',           -- response
+                    '*',          -- features
+                     NULL,        -- exclude columns
+                     1,       --weight
+                     20,                -- num of trees
+                     4,                 -- num of random features
+                     10,       -- max depth
+                     1,        -- min split
+                     1,        -- min bucket
+                     8,        -- number of bins per continuous variable
+                     'max_surrogates=0',
+                     FALSE
+   );
+   ```
+
+   When **is_classification** is set to **FALSE**, the model is a regression task. By default, gbdt provides the regression calculation function. The method generates two tables. One table records the collective information of each tree and the binary of the model. The other table records the parameter information of the method.
+
+3. Perform prediction.
+
+   ```
+   select madlib.gbdt_predict('crime','train_output','test_output','id');
+   ```
+
+   View the prediction result.
+
+   ```
+   select test_output.id, test_prediction,CrimeRat  from test_output join crime using (id);
+
+    id |  test_prediction   | crimerat
+   ----+--------------------+----------
+     1 |               79.1 |     79.1
+     2 |              163.5 |    163.5
+     3 |               57.8 |     57.8
+     4 |              196.9 |    196.9
+     5 |              123.4 |    123.4
+     6 |               68.2 |     68.2
+     7 |   96.2999999992251 |     96.3
+     8 | 155.49842087765936 |    155.5
+     9 |              84.35 |     85.6
+    10 |  70.50157912234037 |     70.5
+    11 |  167.4000000007749 |    167.4
+    12 |               84.9 |     84.9
+    13 |               51.1 |     51.1
+    14 |               66.4 |     66.4
+    15 |               79.8 |     79.8
+    16 |               94.6 |     94.6
+    17 |               53.9 |     53.9
+    18 |               92.9 |     92.9
+    19 |               75.0 |       75
+    20 |              122.5 |    122.5
+    21 |               74.2 |     74.2
+    22 |               43.9 |     43.9
+    23 |              121.6 |    121.6
+    24 |               96.8 |     96.8
+    25 |               52.3 |     52.3
+    26 |              199.3 |    199.3
+    27 |               34.2 |     34.2
+    28 |              121.6 |    121.6
+    29 |              104.3 |    104.3
+    30 |               69.6 |     69.6
+    31 |               37.3 |     37.3
+    32 |               75.4 |     75.4
+    33 |              107.2 |    107.2
+    34 |               92.3 |     92.3
+    35 |   65.2999999992251 |     65.3
+    36 | 127.19842087765963 |    127.2
+    37 |  84.35000000002215 |     83.1
+    38 |  56.60155638297881 |     56.6
+    39 |  82.45000000075257 |     82.6
+    40 | 115.10002273936168 |    115.1
+    41 |               88.0 |       88
+    42 |  54.19997726063828 |     54.2
+    43 |  82.44999999999999 |     82.3
+    44 | 103.00002273936173 |      103
+    45 | 45.500000000000156 |     45.5
+    46 |               50.8 |     50.8
+    47 |               84.9 |     84.9
+   (47 rows)
+   ```
+
+## xgboost Algorithm
+
+The new xgboost supports classification and regression. The following uses the iris flower classification as an example to describe the xgboost algorithm.
+
+The xgboost supports grid search mode and can train multiple groups of parameters at the same time.
+
+1. Prepare the data.
+
+   ```
+   DROP TABLE IF EXISTS iris;
+   create table iris (id serial, a float, d float, c float, b float, label int);
+
+   INSERT into iris (a, b, c, d, label) values
+   (5.1, 3.5, 1.4, 0.2, 0),(4.9, 3.0, 1.4, 0.2, 0),(4.7, 3.2, 1.3, 0.2, 0),(4.6, 3.1, 1.5, 0.2, 0),
+   (5.0, 3.6, 1.4, 0.2, 0),(5.4, 3.9, 1.7, 0.4, 0),(4.6, 3.4, 1.4, 0.3, 0),(5.0, 3.4, 1.5, 0.2, 0),
+   (4.4, 2.9, 1.4, 0.2, 0),(4.9, 3.1, 1.5, 0.1, 0),(5.4, 3.7, 1.5, 0.2, 0),(4.8, 3.4, 1.6, 0.2, 0),
+   (4.8, 3.0, 1.4, 0.1, 0),(4.3, 3.0, 1.1, 0.1, 0),(5.8, 4.0, 1.2, 0.2, 0),(5.7, 4.4, 1.5, 0.4, 0),
+   (5.4, 3.9, 1.3, 0.4, 0),(5.1, 3.5, 1.4, 0.3, 0),(5.7, 3.8, 1.7, 0.3, 0),(5.1, 3.8, 1.5, 0.3, 0),
+   (5.4, 3.4, 1.7, 0.2, 0),(5.1, 3.7, 1.5, 0.4, 0),(4.6, 3.6, 1.0, 0.2, 0),(5.1, 3.3, 1.7, 0.5, 0),
+   (4.8, 3.4, 1.9, 0.2, 0),(5.0, 3.0, 1.6, 0.2, 0),(5.0, 3.4, 1.6, 0.4, 0),(5.2, 3.5, 1.5, 0.2, 0),
+   (5.2, 3.4, 1.4, 0.2, 0),(4.7, 3.2, 1.6, 0.2, 0),(4.8, 3.1, 1.6, 0.2, 0),(5.4, 3.4, 1.5, 0.4, 0),
+   (5.2, 4.1, 1.5, 0.1, 0),(5.5, 4.2, 1.4, 0.2, 0),(4.9, 3.1, 1.5, 0.2, 0),(5.0, 3.2, 1.2, 0.2, 0),
+   (5.5, 3.5, 1.3, 0.2, 0),(4.9, 3.6, 1.4, 0.1, 0),(4.4, 3.0, 1.3, 0.2, 0),(5.1, 3.4, 1.5, 0.2, 0),
+   (5.0, 3.5, 1.3, 0.3, 0),(4.5, 2.3, 1.3, 0.3, 0),(4.4, 3.2, 1.3, 0.2, 0),(5.0, 3.5, 1.6, 0.6, 0),
+   (5.1, 3.8, 1.9, 0.4, 0),(4.8, 3.0, 1.4, 0.3, 0),(5.1, 3.8, 1.6, 0.2, 0),(4.6, 3.2, 1.4, 0.2, 0),
+   (5.3, 3.7, 1.5, 0.2, 0),(5.0, 3.3, 1.4, 0.2, 0),(7.0, 3.2, 4.7, 1.4, 1),(6.4, 3.2, 4.5, 1.5, 1),
+   (6.9, 3.1, 4.9, 1.5, 1),(5.5, 2.3, 4.0, 1.3, 1),(6.5, 2.8, 4.6, 1.5, 1),(5.7, 2.8, 4.5, 1.3, 1),
+   (6.3, 3.3, 4.7, 1.6, 1),(4.9, 2.4, 3.3, 1.0, 1),(6.6, 2.9, 4.6, 1.3, 1),(5.2, 2.7, 3.9, 1.4, 1),
+   (5.0, 2.0, 3.5, 1.0, 1),(5.9, 3.0, 4.2, 1.5, 1),(6.0, 2.2, 4.0, 1.0, 1),(6.1, 2.9, 4.7, 1.4, 1),
+   (5.6, 2.9, 3.6, 1.3, 1),(6.7, 3.1, 4.4, 1.4, 1),(5.6, 3.0, 4.5, 1.5, 1),(5.8, 2.7, 4.1, 1.0, 1),
+   (6.2, 2.2, 4.5, 1.5, 1),(5.6, 2.5, 3.9, 1.1, 1),(5.9, 3.2, 4.8, 1.8, 1),(6.1, 2.8, 4.0, 1.3, 1),
+   (6.3, 2.5, 4.9, 1.5, 1),(6.1, 2.8, 4.7, 1.2, 1),(6.4, 2.9, 4.3, 1.3, 1),(6.6, 3.0, 4.4, 1.4, 1),
+   (6.8, 2.8, 4.8, 1.4, 1),(6.7, 3.0, 5.0, 1.7, 1),(6.0, 2.9, 4.5, 1.5, 1),(5.7, 2.6, 3.5, 1.0, 1),
+   (5.5, 2.4, 3.8, 1.1, 1),(5.5, 2.4, 3.7, 1.0, 1),(5.8, 2.7, 3.9, 1.2, 1),(6.0, 2.7, 5.1, 1.6, 1),
+   (5.4, 3.0, 4.5, 1.5, 1),(6.0, 3.4, 4.5, 1.6, 1),(6.7, 3.1, 4.7, 1.5, 1),(6.3, 2.3, 4.4, 1.3, 1),
+   (5.6, 3.0, 4.1, 1.3, 1),(5.5, 2.5, 4.0, 1.3, 1),(5.5, 2.6, 4.4, 1.2, 1),(6.1, 3.0, 4.6, 1.4, 1),
+   (5.8, 2.6, 4.0, 1.2, 1),(5.0, 2.3, 3.3, 1.0, 1),(5.6, 2.7, 4.2, 1.3, 1),(5.7, 3.0, 4.2, 1.2, 1),
+   (5.7, 2.9, 4.2, 1.3, 1),(6.2, 2.9, 4.3, 1.3, 1),(5.1, 2.5, 3.0, 1.1, 1),(5.7, 2.8, 4.1, 1.3, 1),
+   (6.3, 3.3, 6.0, 2.5, 2),(5.8, 2.7, 5.1, 1.9, 2),(7.1, 3.0, 5.9, 2.1, 2),(6.3, 2.9, 5.6, 1.8, 2),
+   (6.5, 3.0, 5.8, 2.2, 2),(7.6, 3.0, 6.6, 2.1, 2),(4.9, 2.5, 4.5, 1.7, 2),(7.3, 2.9, 6.3, 1.8, 2),
+   (6.7, 2.5, 5.8, 1.8, 2),(7.2, 3.6, 6.1, 2.5, 2),(6.5, 3.2, 5.1, 2.0, 2),(6.4, 2.7, 5.3, 1.9, 2),
+   (6.8, 3.0, 5.5, 2.1, 2),(5.7, 2.5, 5.0, 2.0, 2),(5.8, 2.8, 5.1, 2.4, 2),(6.4, 3.2, 5.3, 2.3, 2),
+   (6.5, 3.0, 5.5, 1.8, 2),(7.7, 3.8, 6.7, 2.2, 2),(7.7, 2.6, 6.9, 2.3, 2),(6.0, 2.2, 5.0, 1.5, 2),
+   (6.9, 3.2, 5.7, 2.3, 2),(5.6, 2.8, 4.9, 2.0, 2),(7.7, 2.8, 6.7, 2.0, 2),(6.3, 2.7, 4.9, 1.8, 2),
+   (6.7, 3.3, 5.7, 2.1, 2),(7.2, 3.2, 6.0, 1.8, 2),(6.2, 2.8, 4.8, 1.8, 2),(6.1, 3.0, 4.9, 1.8, 2),
+   (6.4, 2.8, 5.6, 2.1, 2),(7.2, 3.0, 5.8, 1.6, 2),(7.4, 2.8, 6.1, 1.9, 2),(7.9, 3.8, 6.4, 2.0, 2),
+   (6.4, 2.8, 5.6, 2.2, 2),(6.3, 2.8, 5.1, 1.5, 2),(6.1, 2.6, 5.6, 1.4, 2),(7.7, 3.0, 6.1, 2.3, 2),
+   (6.3, 3.4, 5.6, 2.4, 2),(6.4, 3.1, 5.5, 1.8, 2),(6.0, 3.0, 4.8, 1.8, 2),(6.9, 3.1, 5.4, 2.1, 2),
+   (6.7, 3.1, 5.6, 2.4, 2),(6.9, 3.1, 5.1, 2.3, 2),(5.8, 2.7, 5.1, 1.9, 2),(6.8, 3.2, 5.9, 2.3, 2),
+   (6.7, 3.3, 5.7, 2.5, 2),(6.7, 3.0, 5.2, 2.3, 2),(6.3, 2.5, 5.0, 1.9, 2),(6.5, 3.0, 5.2, 2.0, 2),
+   (6.2, 3.4, 5.4, 2.3, 2),(5.9, 3.0, 5.1, 1.8, 2);
+   ```
+
+2. Perform the classification training.
+
+   ```
+   SET search_path="$user",public,madlib;
+   SET behavior_compat_options = 'bind_procedure_searchpath';
+   select madlib.xgboost_sk_Classifier('public.iris', 'public.iris_model_xgbc', 'id', 'label', 'a,b,c,d', NULL,
+   $${'booster': ['gbtree'], 'eta':   (0.1, 0.9), 'max_depth': (5,1), 'objective': ('multi:softmax',)}$$,   -- Training parameter combination. If there are multiple parameters, input them in tuple or list mode.
+   TRUE);                                  -- Whether to evaluate the model. The multi-classification evaluation metrics are the accuracy and kappa value. The binary classification evaluation metrics are precision, recall, fscore, and support. The regression evaluation metrics are mae, mse, R2squared, and rmse.
+   ```
+
+   The xgboost supports parallel training of multiple groups of parameters. For example, the **eta** values in the case are **0.1** and **0.9**, and the maximum depth is **5** or **1**.
+
+   ```
+   select id, train_timestamp, source_table, y_type, metrics, features, params from iris_model_xgbc;
+   ```
+
+   The following shows the model result.
+
+   ```
+    id |        train_timestamp        | source_table | y_type  |          metrics           | features  |                                     params
+   ----+-------------------------------+--------------+---------+----------------------------+-----------+---------------------------------------------------------------------------------
+    1 | 2020-12-14 20:15:05.904184+08 | public.iris  | integer | {'acc': 1.0, 'kappa': 1.0} | {a,b,c,d} | ('objective = multi:softmax', 'eta = 0.1', 'max_depth = 5', 'booster = gbtree')
+    2 | 2020-12-14 20:15:05.904184+08 | public.iris  | integer | {'acc': 1.0, 'kappa': 1.0} | {a,b,c,d} | ('objective = multi:softmax', 'eta = 0.1', 'max_depth = 1', 'booster = gbtree')
+    3 | 2020-12-14 20:15:05.904184+08 | public.iris  | integer | {'acc': 1.0, 'kappa': 1.0} | {a,b,c,d} | ('objective = multi:softmax', 'eta = 0.9', 'max_depth = 5', 'booster = gbtree')
+    4 | 2020-12-14 20:15:05.904184+08 | public.iris  | integer | {'acc': 1.0, 'kappa': 1.0} | {a,b,c,d} | ('objective = multi:softmax', 'eta = 0.9', 'max_depth = 1', 'booster = gbtree')
+   (4 rows)
+   ```
+
+   The result table records the training time, features, result types, and used parameters.
+
+   In this example, two types of eta and two types of max_depth are selected. Therefore, there are a total of four parameter combinations displayed on four rows in the result. In the **metrics** column, the training evaluation results of the four parameter combinations are recorded. You can enter multiple parameter combinations and select a proper model after training.
+
+3. View the prediction result.
+
+   ```
+   select madlib.xgboost_sk_predict('public.iris', 'public.iris_model_xgbc', 'public.iris_xgbc_out', 'id');
+   select t1.id, prediction, label from iris as t1, iris_xgbc_out as t2 where t1.id = t2.id and prediction <> label;
+   ```
+
+   The comparison between the prediction result and the training result shows that the number of unmatched rows is 0, indicating that the classification accuracy is high.
+
+   ```
+    id | prediction | label
+   ----+------------+-------
+   (0 rows)
+   ```
+
+## prophet Algorithm
+
+The prophet time series forecasting algorithm for Facebook is added. The following uses time series data as an example to describe how to use the prophet algorithm.
+
+1. Prepare the data.
+
+   ```
+   DROP TABLE IF EXISTS ts_data;
+   CREATE TABLE ts_data(date date, value float);
+
+   INSERT into ts_data (date, value) values
+   ('2016-11-29 21:20:00', 5.6),('2016-11-29 21:30:00', 5.2),('2016-11-29 21:40:00', 5.3),('2016-11-29 21:50:00', 5.3),
+   ('2016-11-29 22:00:00', 5.1),('2016-11-29 22:10:00', 5.8),('2016-11-29 22:20:00', 5.6),('2016-11-29 22:30:00', 5.4),
+   ('2016-11-29 22:40:00', 5.4),('2016-11-29 22:50:00', 5.1),('2016-11-29 23:00:00', 5.2),('2016-11-29 23:10:00', 5.9),
+   ('2016-11-29 23:20:00', 5.9),('2016-11-29 23:30:00', 5.1),('2016-11-29 23:40:00', 5.8),('2016-11-29 23:50:00', 6.0),
+   ('2016-11-30 00:00:00', 5.9),('2016-11-30 00:10:00', 5.3),('2016-11-30 00:20:00', 5.4),('2016-11-30 00:30:00', 5.1),
+   ('2016-11-30 00:40:00', 5.6),('2016-11-30 00:50:00', 5.7),('2016-11-30 01:00:00', 5.8),('2016-11-30 01:10:00', 5.4),
+   ('2016-11-30 01:20:00', 5.8),('2016-11-30 01:30:00', 5.1),('2016-11-30 01:40:00', 5.6),('2016-11-30 01:50:00', 5.6),
+   ('2016-11-30 02:00:00', 5.6),('2016-11-30 02:10:00', 5.9),('2016-11-30 02:20:00', 5.7),('2016-11-30 02:30:00', 5.4),
+   ('2016-11-30 02:40:00', 5.6),('2016-11-30 02:50:00', 5.4),('2016-11-30 03:00:00', 5.1),('2016-11-30 03:10:00', 5.0),
+   ('2016-11-30 03:20:00', 5.9),('2016-11-30 03:30:00', 5.8),('2016-11-30 03:40:00', 5.4),('2016-11-30 03:50:00', 5.7),
+   ('2016-11-30 04:00:00', 5.6),('2016-11-30 04:10:00', 5.9),('2016-11-30 04:20:00', 5.1),('2016-11-30 04:30:00', 5.8),
+   ('2016-11-30 04:40:00', 5.5),('2016-11-30 04:50:00', 5.1),('2016-11-30 05:00:00', 5.8),('2016-11-30 05:10:00', 5.5),
+   ('2016-11-30 05:20:00', 5.7),('2016-11-30 05:30:00', 5.2),('2016-11-30 05:40:00', 5.7),('2016-11-30 05:50:00', 6.0),
+   ('2016-11-30 06:00:00', 5.8),('2016-11-30 06:10:00', 5.6),('2016-11-30 06:20:00', 5.2),('2016-11-30 06:30:00', 5.8),
+   ('2016-11-30 06:40:00', 5.3),('2016-11-30 06:50:00', 5.4),('2016-11-30 07:00:00', 5.8),('2016-11-30 07:10:00', 5.2),
+   ('2016-11-30 07:20:00', 5.3),('2016-11-30 07:30:00', 5.3),('2016-11-30 07:40:00', 5.8),('2016-11-30 07:50:00', 5.9),
+   ('2016-11-30 08:00:00', 5.6),('2016-11-30 08:10:00', 5.2),('2016-11-30 08:20:00', 5.4),('2016-11-30 08:30:00', 5.6),
+   ('2016-11-30 08:40:00', 6.0),('2016-11-30 08:50:00', 5.4),('2016-11-30 09:00:00', 6.0),('2016-11-30 09:10:00', 5.1),
+   ('2016-11-30 09:20:00', 5.1),('2016-11-30 09:30:00', 5.5),('2016-11-30 09:40:00', 5.6),('2016-11-30 09:50:00', 5.0),
+   ('2016-11-30 10:00:00', 5.1),('2016-11-30 10:10:00', 5.7),('2016-11-30 10:20:00', 5.4),('2016-11-30 10:30:00', 5.4),
+   ('2016-11-30 10:40:00', 5.7),('2016-11-30 10:50:00', 5.2),('2016-11-30 11:00:00', 5.4),('2016-11-30 11:10:00', 5.3),
+   ('2016-11-30 11:20:00', 5.6),('2016-11-30 11:30:00', 5.0),('2016-11-30 11:40:00', 5.2),('2016-11-30 11:50:00', 5.2),
+   ('2016-11-30 12:00:00', 5.5),('2016-11-30 12:10:00', 5.1),('2016-11-30 12:20:00', 5.7),('2016-11-30 12:30:00', 5.4),
+   ('2016-11-30 12:40:00', 5.2),('2016-11-30 12:50:00', 5.5),('2016-11-30 13:00:00', 5.0),('2016-11-30 13:10:00', 5.5),
+   ('2016-11-30 13:20:00', 5.6),('2016-11-30 13:30:00', 5.3),('2016-11-30 13:40:00', 5.5),('2016-11-30 13:50:00', 5.9),
+   ('2016-11-30 14:00:00', 10.9),('2016-11-30 14:10:00', 10.6),('2016-11-30 14:20:00', 10.3),('2016-11-30 14:30:00', 11.0),
+   ('2016-11-30 14:40:00', 10.0),('2016-11-30 14:50:00', 10.1),('2016-11-30 15:00:00', 10.2),('2016-11-30 15:10:00', 10.2),
+   ('2016-11-30 15:20:00', 10.3),('2016-11-30 15:30:00', 10.1),('2016-11-30 15:40:00', 10.9),('2016-11-30 15:50:00', 10.1),
+   ('2016-11-30 16:00:00', 11.0),('2016-11-30 16:10:00', 10.2),('2016-11-30 16:20:00', 10.7),('2016-11-30 16:30:00', 10.2),
+   ('2016-11-30 16:40:00', 10.2),('2016-11-30 16:50:00', 10.2),('2016-11-30 17:00:00', 10.8),('2016-11-30 17:10:00', 10.6),
+   ('2016-11-30 17:20:00', 10.5),('2016-11-30 17:30:00', 10.7),('2016-11-30 17:40:00', 10.9),('2016-11-30 17:50:00', 10.9),
+   ('2016-11-30 18:00:00', 10.1),('2016-11-30 18:10:00', 10.3),('2016-11-30 18:20:00', 10.1),('2016-11-30 18:30:00', 10.6),
+   ('2016-11-30 18:40:00', 10.3),('2016-11-30 18:50:00', 10.8),('2016-11-30 19:00:00', 10.9),('2016-11-30 19:10:00', 10.8),
+   ('2016-11-30 19:20:00', 10.6),('2016-11-30 19:30:00', 11.0),('2016-11-30 19:40:00', 10.3),('2016-11-30 19:50:00', 10.9),
+   ('2016-11-30 20:00:00', 10.6),('2016-11-30 20:10:00', 10.6),('2016-11-30 20:20:00', 10.5),('2016-11-30 20:30:00', 10.4),
+   ('2016-11-30 20:40:00', 10.9),('2016-11-30 20:50:00', 10.9),('2016-11-30 21:00:00', 10.7),('2016-11-30 21:10:00', 10.6),
+   ('2016-11-30 21:20:00', 10.5),('2016-11-30 21:30:00', 10.8),('2016-11-30 21:40:00', 10.4),('2016-11-30 21:50:00', 10.0),
+   ('2016-11-30 22:00:00', 10.6),('2016-11-30 22:10:00', 10.6),('2016-11-30 22:20:00', 10.6),('2016-11-30 22:30:00', 10.1),
+   ('2016-11-30 22:40:00', 10.4),('2016-11-30 22:50:00', 10.8),('2016-11-30 23:00:00', 10.4),('2016-11-30 23:10:00', 10.6),
+   ('2016-11-30 23:20:00', 10.1),('2016-11-30 23:30:00', 10.2),('2016-11-30 23:40:00', 10.6),('2016-11-30 23:50:00', 10.8),
+   ('2016-12-01 00:00:00', 10.6),('2016-12-01 00:10:00', 10.2),('2016-12-01 00:20:00', 10.9),('2016-12-01 00:30:00', 10.3),
+   ('2016-12-01 00:40:00', 10.3),('2016-12-01 00:50:00', 10.1),('2016-12-01 01:00:00', 10.7),('2016-12-01 01:10:00', 10.5),
+   ('2016-12-01 01:20:00', 10.4),('2016-12-01 01:30:00', 10.7),('2016-12-01 01:40:00', 10.5),('2016-12-01 01:50:00', 10.7),
+   ('2016-12-01 02:00:00', 10.8),('2016-12-01 02:10:00', 10.9),('2016-12-01 02:20:00', 10.9),('2016-12-01 02:30:00', 10.1),
+   ('2016-12-01 02:40:00', 10.4),('2016-12-01 02:50:00', 10.7),('2016-12-01 03:00:00', 10.7),('2016-12-01 03:10:00', 10.5),
+   ('2016-12-01 03:20:00', 10.2),('2016-12-01 03:30:00', 10.2),('2016-12-01 03:40:00', 10.8),('2016-12-01 03:50:00', 10.2),
+   ('2016-12-01 04:00:00', 10.9),('2016-12-01 04:10:00', 10.4),('2016-12-01 04:20:00', 10.6),('2016-12-01 04:30:00', 11.0),
+   ('2016-12-01 04:40:00', 10.4),('2016-12-01 04:50:00', 10.3),('2016-12-01 05:00:00', 10.7),('2016-12-01 05:10:00', 10.6),
+   ('2016-12-01 05:20:00', 10.9),('2016-12-01 05:30:00', 11.0),('2016-12-01 05:40:00', 10.9),('2016-12-01 05:50:00', 10.0),
+   ('2016-12-01 06:00:00', 10.8),('2016-12-01 06:10:00', 10.0),('2016-12-01 06:20:00', 10.1),('2016-12-01 06:30:00', 10.5),
+   ('2016-12-01 06:40:00', 15.5),('2016-12-01 06:50:00', 15.7),('2016-12-01 07:00:00', 15.1),('2016-12-01 07:10:00', 15.6),
+   ('2016-12-01 07:20:00', 15.5),('2016-12-01 07:30:00', 15.4),('2016-12-01 07:40:00', 15.7),('2016-12-01 07:50:00', 15.6),
+   ('2016-12-01 08:00:00', 15.3),('2016-12-01 08:10:00', 15.6),('2016-12-01 08:20:00', 15.1),('2016-12-01 08:30:00', 15.6),
+   ('2016-12-01 08:40:00', 15.9),('2016-12-01 08:50:00', 16.0),('2016-12-01 09:00:00', 15.4),('2016-12-01 09:10:00', 15.0),
+   ('2016-12-01 09:20:00', 15.0),('2016-12-01 09:30:00', 15.4),('2016-12-01 09:40:00', 15.9),('2016-12-01 09:50:00', 15.6),
+   ('2016-12-01 10:00:00', 15.7),('2016-12-01 10:10:00', 15.4),('2016-12-01 10:20:00', 15.2),('2016-12-01 10:30:00', 15.2),
+   ('2016-12-01 10:40:00', 15.8),('2016-12-01 10:50:00', 15.4),('2016-12-01 11:00:00', 16.0),('2016-12-01 11:10:00', 15.9),
+   ('2016-12-01 11:20:00', 15.1),('2016-12-01 11:30:00', 15.0),('2016-12-01 11:40:00', 15.0),('2016-12-01 11:50:00', 15.4),
+   ('2016-12-01 12:00:00', 15.5),('2016-12-01 12:10:00', 15.3),('2016-12-01 12:20:00', 16.0),('2016-12-01 12:30:00', 15.1),
+   ('2016-12-01 12:40:00', 15.5),('2016-12-01 12:50:00', 16.0),('2016-12-01 13:00:00', 15.7),('2016-12-01 13:10:00', 15.9),
+   ('2016-12-01 13:20:00', 15.4),('2016-12-01 13:30:00', 15.3),('2016-12-01 13:40:00', 15.9),('2016-12-01 13:50:00', 15.8),
+   ('2016-12-01 14:00:00', 15.4),('2016-12-01 14:10:00', 15.9),('2016-12-01 14:20:00', 15.3),('2016-12-01 14:30:00', 16.0),
+   ('2016-12-01 14:40:00', 15.5),('2016-12-01 14:50:00', 15.0),('2016-12-01 15:00:00', 15.1),('2016-12-01 15:10:00', 16.0),
+   ('2016-12-01 15:20:00', 15.8),('2016-12-01 15:30:00', 15.9),('2016-12-01 15:40:00', 15.4),('2016-12-01 15:50:00', 15.1),
+   ('2016-12-01 16:00:00', 15.8),('2016-12-01 16:10:00', 15.2),('2016-12-01 16:20:00', 15.4),('2016-12-01 16:30:00', 15.8),
+   ('2016-12-01 16:40:00', 15.8),('2016-12-01 16:50:00', 15.1),('2016-12-01 17:00:00', 15.3),('2016-12-01 17:10:00', 15.6),
+   ('2016-12-01 17:20:00', 15.3),('2016-12-01 17:30:00', 15.8),('2016-12-01 17:40:00', 15.0),('2016-12-01 17:50:00', 15.3),
+   ('2016-12-01 18:00:00', 15.5),('2016-12-01 18:10:00', 15.4),('2016-12-01 18:20:00', 15.3),('2016-12-01 18:30:00', 15.8),
+   ('2016-12-01 18:40:00', 15.2),('2016-12-01 18:50:00', 15.9),('2016-12-01 19:00:00', 15.4),('2016-12-01 19:10:00', 15.3),
+   ('2016-12-01 19:20:00', 15.1),('2016-12-01 19:30:00', 15.3),('2016-12-01 19:40:00', 15.9),('2016-12-01 19:50:00', 15.3),
+   ('2016-12-01 20:00:00', 15.3),('2016-12-01 20:10:00', 15.2),('2016-12-01 20:20:00', 15.0),('2016-12-01 20:30:00', 15.3),
+   ('2016-12-01 20:40:00', 15.1),('2016-12-01 20:50:00', 15.1),('2016-12-01 21:00:00', 15.6),('2016-12-01 21:10:00', 15.8),
+   ('2016-12-01 21:20:00', 15.4),('2016-12-01 21:30:00', 15.2),('2016-12-01 21:40:00', 16.0),('2016-12-01 21:50:00', 15.5),
+   ('2016-12-01 22:00:00', 15.4),('2016-12-01 22:10:00', 15.7),('2016-12-01 22:20:00', 15.3),('2016-12-01 22:30:00', 15.9),
+   ('2016-12-01 22:40:00', 15.9),('2016-12-01 22:50:00', 15.2),('2016-12-01 23:00:00', 15.8),('2016-12-01 23:10:00', 15.9),
+   ('2016-12-01 23:20:00', 20.9),('2016-12-01 23:30:00', 20.4),('2016-12-01 23:40:00', 20.3),('2016-12-01 23:50:00', 20.1),
+   ('2016-12-02 00:00:00', 20.7),('2016-12-02 00:10:00', 20.7),('2016-12-02 00:20:00', 20.5),('2016-12-02 00:30:00', 20.4),
+   ('2016-12-02 00:40:00', 20.4),('2016-12-02 00:50:00', 20.1),('2016-12-02 01:00:00', 20.2),('2016-12-02 01:10:00', 20.9),
+   ('2016-12-02 01:20:00', 20.6),('2016-12-02 01:30:00', 20.0),('2016-12-02 01:40:00', 20.4),('2016-12-02 01:50:00', 20.2),
+   ('2016-12-02 02:00:00', 20.6),('2016-12-02 02:10:00', 20.4),('2016-12-02 02:20:00', 20.5),('2016-12-02 02:30:00', 20.4),
+   ('2016-12-02 02:40:00', 20.5),('2016-12-02 02:50:00', 20.7),('2016-12-02 03:00:00', 20.2),('2016-12-02 03:10:00', 20.2),
+   ('2016-12-02 03:20:00', 20.1),('2016-12-02 03:30:00', 20.5),('2016-12-02 03:40:00', 20.5),('2016-12-02 03:50:00', 20.0),
+   ('2016-12-02 04:00:00', 20.7),('2016-12-02 04:10:00', 20.8),('2016-12-02 04:20:00', 20.6),('2016-12-02 04:30:00', 20.4),
+   ('2016-12-02 04:40:00', 20.5),('2016-12-02 04:50:00', 20.8),('2016-12-02 05:00:00', 20.1),('2016-12-02 05:10:00', 20.9),
+   ('2016-12-02 05:20:00', 20.5),('2016-12-02 05:30:00', 20.4),('2016-12-02 05:40:00', 20.2),('2016-12-02 05:50:00', 20.4),
+   ('2016-12-02 06:00:00', 20.8),('2016-12-02 06:10:00', 20.7),('2016-12-02 06:20:00', 20.9),('2016-12-02 06:30:00', 20.1),
+   ('2016-12-02 06:40:00', 20.3),('2016-12-02 06:50:00', 20.2),('2016-12-02 07:00:00', 20.4),('2016-12-02 07:10:00', 20.7),
+   ('2016-12-02 07:20:00', 20.4),('2016-12-02 07:30:00', 20.8),('2016-12-02 07:40:00', 20.8),('2016-12-02 07:50:00', 20.1),
+   ('2016-12-02 08:00:00', 20.3),('2016-12-02 08:10:00', 20.7),('2016-12-02 08:20:00', 20.9),('2016-12-02 08:30:00', 21.0),
+   ('2016-12-02 08:40:00', 20.2),('2016-12-02 08:50:00', 20.5),('2016-12-02 09:00:00', 20.2),('2016-12-02 09:10:00', 20.8),
+   ('2016-12-02 09:20:00', 20.9),('2016-12-02 09:30:00', 20.5),('2016-12-02 09:40:00', 20.9),('2016-12-02 09:50:00', 20.7),
+   ('2016-12-02 10:00:00', 20.3),('2016-12-02 10:10:00', 21.0),('2016-12-02 10:20:00', 20.5),('2016-12-02 10:30:00', 20.3),
+   ('2016-12-02 10:40:00', 20.2),('2016-12-02 10:50:00', 20.3),('2016-12-02 11:00:00', 20.4),('2016-12-02 11:10:00', 20.4),
+   ('2016-12-02 11:20:00', 21.0),('2016-12-02 11:30:00', 20.3),('2016-12-02 11:40:00', 20.3),('2016-12-02 11:50:00', 20.9),
+   ('2016-12-02 12:00:00', 20.8),('2016-12-02 12:10:00', 20.9),('2016-12-02 12:20:00', 20.7),('2016-12-02 12:30:00', 20.7);
+   ```
+
+2. Perform training.
+
+   ```
+   SET search_path="$user",public,madlib;
+   SET behavior_compat_options = 'bind_procedure_searchpath';
+   select madlib.prophet_fit('public.ts_data', 'public.prophet_model',
+   $${'ds': 'date', 'y': 'value'}$$, -- Column name mapping. The prophet requires that the time column name be 'ds' and the time series value column name be 'y'.
+   $${'growth': 'linear', 'changepoints': ['2016-11-30 05:40:00']}$$ -- Training parameter combination. If there are multiple parameters, input them in tuple mode.
+   );
+   ```
+
+   Query the model table.
+
+   ```
+    select id, y_type, params from public.prophet_model;
+
+   id |      y_type      |                            params
+   ----+------------------+---------------------------------------------------------------
+    1 | double precision | {'changepoints': ['2016-11-30 05:40:00'], 'growth': 'linear'}
+   ```
+
+   The model table records the training time, result types, and used parameters.
+
+3. Perform the prediction.
+
+   ```
+   select madlib.prophet_predict('public.prophet_model','public.prophet_output', 10, '10T');
+   ```
+
+   View the prediction result.
+
+   ```
+   select ds, yhat, yhat_lower, yhat_upper from public.prophet_output;
+
+        ds     |     yhat      |  yhat_lower   |  yhat_upper
+   ------------+---------------+---------------+---------------
+    2016-12-02 | 20.6943848045 | 17.7671496048 | 23.4160694837
+    2016-12-02 | 20.7408355633 | 17.9264413164 | 23.6426403933
+    2016-12-02 | 20.7872863221 | 17.9298207895 | 23.4548814727
+    2016-12-02 |  20.833737081 |  18.234443228 | 23.5317342873
+    2016-12-02 | 20.8801878398 | 18.2471709649 | 23.8345735574
+    2016-12-02 | 20.9266385986 | 18.1780101465 |  23.696087927
+    2016-12-02 | 20.9730893575 | 18.4292088648 | 23.7209823631
+    2016-12-02 | 21.0195401163 | 18.2623494126 | 23.7341427068
+    2016-12-02 | 21.0659908751 | 18.1173966769 | 23.7919478206
+    2016-12-02 |  21.112441634 | 18.5018042056 | 23.9508963879
+   (10 rows)
+   ```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/7-deepsql/7-5-troubleshooting.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/7-deepsql/7-5-troubleshooting.md
new file mode 100644
index 0000000000000000000000000000000000000000..cc172f05f431612e1d6b19934ab70b9ae634ad70
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/7-deepsql/7-5-troubleshooting.md
@@ -0,0 +1,46 @@
+---
+title: Troubleshooting
+summary: Troubleshooting
+author: Guo Huan
+date: 2021-05-19
+---
+
+# Troubleshooting
+
+- **Problem description**: When you compile the database, the following messages about the Python module are displayed: "can not be used when making a shared object;recompile with -fPIC" or "libpython22.7.a: could not read symbols: Bad value".
+
+  **Solution**:
+
+  1. Check the Python version and environment variables.
+  2. Check whether python-devel is i**gdb** oor whether **-enable-shared** is enabled during Python compilation.
+
+- **Problem description**: When the **gdb** or **gstack** command is executed, the error message "gdb: symbol lookup error: gdb: undefined symbol: PyUnicodeUCS4_FromEncodedObject" is displayed.
+
+  **Solution**: This problem generally occurs in the environment where Python 2 is compiled. During Python 2 compilation and installation, you can use the **-enable-unicode=ucs2** or **-enable-unicode=ucs4** option to specify that two bytes or four bytes are used to represent a Unicode character. By default, Python 2 uses **-enable-unicode=ucs2**. By default, Python 3 uses four bytes to represent a Unicode character.
+
+  You can run the **import sys; print sys.maxunicode** command in the built-in Python 2 and view the result. If the result is **65535**, the system uses the UCS2 code by default. If the result is **1114111**, the system uses the UCS4 code.
+
+  When you compile Python 2 by yourself, if the built-in Python 2 uses UCS4, the gdb in the system also depends on UCS4. Therefore, you need to add **-enable-unicode=ucs4** when configuring Python 2 that is compiled by yourself.
+
+- **Problem description**: The error message " "Data table does not exist" " is displayed when the kmeans algorithm is used.
+
+  **Solution**: If the schema where the algorithm is located and the input table are not in the same schema, you can set **SET behavior_compat_options = 'bind_procedure_searchpath'** to solve the problem.
+
+- **Problem description**: An error is reported during Python startup or import.
+
+  **Solution**:
+
+  1. Check the environment variables, such as **PYTHONHOME** and *PYTHONPATH*.
+  2. Install the required dependency packages.
+
+- **Problem description**: An error message "ERROR: spiexceptions.UndefinedFunction: operator does not exist: json -&gt;&gt; unknown." is displayed when algorithms such as regression are used.
+
+  **Solution**: The database does not support the JSON export function.
+
+- **Problem description**: During compilation in MADlib, if **make -sj** is used, boost-related errors are reported. For example: **fatal error: boost/mpl/if.hpp: No such file or directory**.
+
+  **Solution**: This is not a problem. During MADlib compilation, the installation packages are decompressed first. If the compilation is performed in parallel mode, the compilation and decompression may be performed at the same time. If this file used for compilation has not been decompressed yet, such an error is reported. You can run the **make -sj** command again to solve the problem.
+
+- **Problem description**: The error message "ERROR: Failed to connect to database" is displayed when you run the **./madpack** command to install the Madpack.
+
+  **Solution**: Check whether the database is started, whether the target database exists, whether the database port is occupied, and whether the installation user has the administrator permission. When installing the Madpack, set the IP address to **127.0.0.1** instead of localhost. Otherwise, the connection fails.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/8-db4ai/8-1-overview.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/8-db4ai/8-1-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..38d232b57e9d2fd30982cf52d345264b93ff493c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/8-db4ai/8-1-overview.md
@@ -0,0 +1,10 @@
+---
+title: Overview
+summary: Overview
+author: Guo Huan
+date: 2021-10-20
+---
+
+# Overview
+
+DB4AI uses database capabilities to drive AI tasks and implement data storage and technology stack isomorphism. By integrating AI algorithms into the database, MogDB supports the native AI computing engine, model management, AI operators, and native AI execution plan, providing users with inclusive AI technologies. Different from the traditional AI modeling process, DB4AI one-stop modeling eliminates repeated data flowing among different platforms, simplifies the development process, and plans the optimal execution path through the database, so that developers can focus on the tuning of specific services and models. It outcompetes similar products in ease-of-use and performance.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/8-db4ai/8-2-db4ai-snapshots-for-data-version-management.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/8-db4ai/8-2-db4ai-snapshots-for-data-version-management.md
new file mode 100644
index 0000000000000000000000000000000000000000..497627218f1be43ba4ba8cb11e77cd65ecede75d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/8-db4ai/8-2-db4ai-snapshots-for-data-version-management.md
@@ -0,0 +1,265 @@
+---
+title: DB4AI-Snapshots for Data Version Management
+summary: DB4AI-Snapshots for Data Version Management
+author: Guo Huan
+date: 2021-10-20
+---
+
+# DB4AI-Snapshots for Data Version Management
+
+DB4AI-Snapshots is used by the DB4AI module to manage dataset versions. With the DB4AI-Snapshots component, developers can easily and quickly perform data preprocessing operations such as feature filtering and type conversion. In addition, developers can perform version control on training datasets like Git. After a data table snapshot is created, it can be used as a view. However, once the data table snapshot is released, it is fixed as static data. To modify the content of this data table snapshot, you need to create a data table snapshot with a different version number.
+
+## Lifecycle of DB4AI-Snapshots
+
+DB4AI-Snapshots can be published, archived, or purged. After being published, DB4AI-Snapshots can be used. Archived DB4AI-Snapshots are in the archiving period and will not be used to train new models. Instead, old data is used to verify new models. Purged DB4AI-Snapshots will not be found in the database system.
+
+Note that the DB4AI-Snapshots function is used to provide unified training data for users. Team members can use the specified training data to retrain the machine learning models, facilitating collaboration between users. Therefore, the DB4AI-Snapshots feature is not supported in scenarios where user data conversion is not supported, such as **private users** and **separation of duty** (**enableSeparationOfDuty** set to **ON**).
+
+You can run the **CREATE SNAPSHOT** statement to create a data table snapshot. The created snapshot is in the published state by default. You can create a table snapshot in either **MSS** or **CSS** mode, which can be configured using the GUC parameter **db4ai_snapshot_mode**. For the MSS mode, it is realized by materialization algorithm where data entity of original datasets is stored. The CSS mode is implemented based on a relative calculation algorithm where incremental data information is stored. The metadata of the data table snapshot is stored in the system directory of DB4AI. You can view it in the **db4ai.snapshot** system catalog.
+
+You can run the **ARCHIVE SNAPSHOT** statement to mark a data table snapshot as archived, and run the **PUBLISH SNAPSHOT** statement to mark it as published again. The state of a data table snapshot is marked to help data scientists work together as a team.
+
+If a table snapshot is no longer useful, you can run the **PURGE SNAPSHOT** statement to permanently delete it and restore the storage space.
+
+## DB4AI-Snapshots Usage Guide
+
+1. Create a table and insert table data.
+
+   If a data table exists in the database, you can create a data table snapshot based on the existing data table. To facilitate subsequent demonstration, create a data table named **t1** and insert test data into the table.
+
+   ```sql
+   create table t1 (id int, name varchar);
+   insert into t1 values (1, 'zhangsan');
+   insert into t1 values (2, 'lisi');
+   insert into t1 values (3, 'wangwu');
+   insert into t1 values (4, 'lisa');
+   insert into t1 values (5, 'jack');
+   ```
+
+   Run the following SQL statement to query the content of the collocation data table:
+
+   ```sql
+   SELECT * FROM t1;
+   id |   name
+   ----+----------
+     1 | zhangsan
+     2 | lisi
+     3 | wangwu
+     4 | lisa
+     5 | jack
+   (5 rows)
+   ```
+
+2. Use DB4AI-Snapshots.
+
+   - Create DB4AI-Snapshots.
+
+     - Example 1: CREATE SNAPSHOT… AS
+
+       In the following example, the default version separator is an at sign (@), and the default subversion separator is a period (.). You can set the separator by setting the **db4ai_snapshot_version_delimiter** and **db4ai_snapshot_version_separator** parameters.
+
+       ```sql
+       create snapshot s1@1.0 comment is 'first version' as select * from t1;
+       schema |  name
+       --------+--------
+        public | s1@1.0
+       (1 row)
+       ```
+
+       The command output indicates that a snapshot has been created for data table **s1** and the version number is **1.0**. A created data table snapshot can be queried in the same way as a common view, but cannot be updated using the **INSERT INTO** statement. For example, you can use any of the following statements to query the content of data table snapshot **s1** of version 1.0:
+
+       ```sql
+       SELECT * FROM s1@1.0;
+       SELECT * FROM public.s1@1.0;
+       SELECT * FROM public . s1 @ 1.0;
+       id |   name
+       ----+----------
+         1 | zhangsan
+         2 | lisi
+         3 | wangwu
+         4 | lisa
+         5 | jack
+       (5 rows)
+       ```
+
+       You can run the following SQL statement to modify the content of the **t1** data table:
+
+       ```sql
+       UPDATE t1 SET name = 'tom' where id = 4;
+       insert into t1 values (6, 'john');
+       insert into t1 values (7, 'tim');
+       ```
+
+       When content of data table **t1** is retrieved again, it is found that although the content of data table **t1** has changed, the query result of data table snapshot **s1@1.0** does not change. Because data in data table **t1** has changed, to use content of the current data table as a version 2.0, you can create snapshot **s1@2.0** by using the following SQL statement:
+
+       ```sql
+       create snapshot s1@2.0 as select * from t1;
+       ```
+
+       According to the foregoing example, it can be found that the data table snapshot can solidify content of a data table, to avoid instability during training of a machine learning model caused by data modification in the process, and can also avoid a lock conflict caused when multiple users access and modify the same table at the same time.
+
+     - Example 2: CREATE SNAPSHOT… FROM
+
+       You can run an SQL statement to inherit a created data table snapshot and generate a new data table snapshot based on the data modification. Example:
+
+       ```sql
+       create snapshot s1@3.0 from @1.0 comment is 'inherits from @1.0' using (INSERT VALUES(6, 'john'), (7, 'tim'); DELETE WHERE id = 1);
+       schema |  name
+       --------+--------
+        public | s1@3.0
+       (1 row)
+       ```
+
+       Where, @ is the data table snapshot version separator and the from clause is followed by the existing data table snapshot, in the format of @ + version number. You can add an operation keyword (such as **INSERT**, **UPDATE**, **DELETE**, or **ALTER**) after the **USING** keyword. In the **INSERT INTO** and **DELETE FROM** statements, clauses related to data table snapshot names, such as **INTO** and **FROM**, can be omitted. For details, see [AI Feature Functions](28-ai-feature-functions).
+
+       In the example, based on the **s1@1.0** snapshot, insert two pieces of data and delete one piece of data to generate a new snapshot **s1@3.0**. Then, retrieve **s1@3.0**.
+
+       ```sql
+       SELECT * FROM s1@3.0;
+       id |   name
+       ----+----------
+         1 | zhangsan
+         2 | lisi
+         3 | wangwu
+         4 | lisa
+         5 | jack
+         6 | john
+         7 | tim
+       (7 rows)
+       ```
+
+   - Delete the data table snapshot **SNAPSHOT**.
+
+     ```sql
+     purge snapshot s1@3.0;
+     schema |  name
+     --------+--------
+      public | s1@3.0
+     (1 row)
+     ```
+
+     At this time, no data can be retrieved from **s1@3.0**, and the records of the data table snapshot in the **db4ai.snapshot** view are cleared. Deleting the data table snapshot of this version does not affect the data table snapshots of other versions.
+
+   - Sample from a data table snapshot.
+
+     Example: Use the sampling rate 0.5 to extract data from snapshot **s1**.
+
+     ```sql
+     sample snapshot s1@2.0 stratify by name as nick at ratio .5;
+     schema |    name
+     --------+------------
+      public | s1nick@2.0
+     (1 row)
+     ```
+
+     You can use this function to create a training set and a test set. For example:
+
+     ```sql
+     SAMPLE SNAPSHOT s1@2.0  STRATIFY BY name AS _test AT RATIO .2, AS _train AT RATIO .8 COMMENT IS 'training';
+     schema |      name
+     --------+----------------
+      public | s1_test@2.0
+      public | s1_train@2.0
+     (2 rows)
+     ```
+
+   - Publish a data table snapshot.
+
+     Run the following SQL statement to mark the data table snapshot **s1@2.0** as published:
+
+     ```sql
+     publish snapshot s1@2.0;
+     schema |  name
+     --------+--------
+      public | s1@2.0
+     (1 row)
+     ```
+
+   - Archive a data table snapshot.
+
+     Run the following statement to mark the data table snapshot as archived:
+
+     ```sql
+     archive snapshot s1@2.0;
+     schema |  name
+     --------+--------
+      public | s1@2.0
+     (1 row)
+     ```
+
+     You can use the views provided by DB4AI-Snapshots to view the status of the current data table snapshot and other information.
+
+     ```sql
+     select * from db4ai.snapshot;
+     id | parent_id | matrix_id | root_id | schema |    name    | owner  |                 commands                 | comment | published | archived |          created           | row_count
+     ----+-----------+-----------+---------+--------+------------+--------+------------------------------------------+---------+-----------+----------+----------------------------+-----------
+       1 |           |           |       1 | public | s1@2.0     | omm | {"select *","from t1 where id > 3",NULL} |         | t         | f        | 2021-04-17 09:24:11.139868 |         2
+       2 |         1 |           |       1 | public | s1nick@2.0 | omm | {"SAMPLE nick .5 {name}"}                |         | f         | f        | 2021-04-17 10:02:31.73923  |         0
+     ```
+
+3. Perform troubleshooting in case of exceptions.
+
+   - The data table or DB4AI snapshot does not exist.
+
+     ```sql
+     purge snapshot s1nick@2.0;
+     publish snapshot s1nick@2.0;
+     ---------
+     ERROR:  snapshot public."s1nick@2.0" does not exist
+     CONTEXT:  PL/pgSQL function db4ai.publish_snapshot(name,name) line 11 at assignment
+
+     archive snapshot s1nick@2.0;
+     ----------
+     ERROR:  snapshot public."s1nick@2.0" does not exist
+     CONTEXT:  PL/pgSQL function db4ai.archive_snapshot(name,name) line 11 at assignment
+     ```
+
+   - Before deleting a snapshot, ensure that other snapshots that depend on it have been deleted.
+
+     ```sql
+     purge snapshot s1@1.0;
+     ERROR:  cannot purge root snapshot 'public."s1@1.0"' having dependent db4ai-snapshots
+     HINT:  purge all dependent db4ai-snapshots first
+     CONTEXT:  referenced column: purge_snapshot_internal
+     SQL statement "SELECT db4ai.purge_snapshot_internal(i_schema, i_name)"
+     PL/pgSQL function db4ai.purge_snapshot(name,name) line 62 at PERFORM
+     ```
+
+4. Set GUC parameters.
+
+   - db4ai_snapshot_mode:
+
+     There are two snapshot modes: MSS (materialized mode, used to store data entities) and CSS (computing mode, used to store incremental information). The snapshot mode can be switched between MSS and CSS. The default snapshot mode is MSS.
+
+   - db4ai_snapshot_version_delimiter:
+
+     Used to set the data table snapshot version separator. The at sign (@) is the default data table snapshot version separator.
+
+   - db4ai_snapshot_version_separator
+
+     Used to set the data table snapshot subversion separator. The period (.) is the default data table snapshot subversion separator.
+
+5. View the snapshot details of a data table in the DB4AI schema by using **db4ai.snapshot**.
+
+   ```sql
+   mogdb=# \d db4ai.snapshot
+                          Table "db4ai.snapshot"
+     Column   |            Type             |         Modifiers
+   -----------+-----------------------------+---------------------------
+    id        | bigint                      |
+    parent_id | bigint                      |
+    matrix_id | bigint                      |
+    root_id   | bigint                      |
+    schema    | name                        | not null
+    name      | name                        | not null
+    owner     | name                        | not null
+    commands  | text[]                      | not null
+    comment   | text                        |
+    published | boolean                     | not null default false
+    archived  | boolean                     | not null default false
+    created   | timestamp without time zone | default pg_systimestamp()
+    row_count | bigint                      | not null
+   Indexes:
+       "snapshot_pkey" PRIMARY KEY, btree (schema, name) TABLESPACE pg_default
+       "snapshot_id_key" UNIQUE CONSTRAINT, btree (id) TABLESPACE pg_default
+   ```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/8-db4ai/8-3-db4ai-query-for-model-training-and-prediction.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/8-db4ai/8-3-db4ai-query-for-model-training-and-prediction.md
new file mode 100644
index 0000000000000000000000000000000000000000..d4b4153b8312314e68eedad240a52cb064d1eae3
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/8-db4ai/8-3-db4ai-query-for-model-training-and-prediction.md
@@ -0,0 +1,420 @@
+---
+title: DB4AI-Query for Model Training and Prediction
+summary: DB4AI-Query for Model Training and Prediction
+author: Guo Huan
+date: 2021-10-20
+---
+
+# DB4AI-Query for Model Training and Prediction
+
+The current version of MogDB supports the native DB4AI capability. By introducing native AI operators, MogDB simplifies the operation process and fully utilizes the optimization and execution capabilities of the database optimizer and executor to obtain the high-performance model training capability in the database. With a simpler model training and prediction process and higher performance, developers can focus on model tuning and data analysis in a shorter period of time, avoiding fragmented technology stacks and redundant code implementation.
+
+## Keyword Parsing
+
+**Table 1** DB4AI syntax and keywords
+
+<table>
+    <tr>
+        <th></th>
+        <th>Name</th>
+        <th>Description</th>
+    </tr>
+    <tr>
+        <td rowspan=2>Statement</td>
+        <td>CREATE MODEL</td>
+        <td>Creates a model, trains it, and saves the model.</td>
+    </tr>
+<tr>
+    <td>PREDICT BY</td>
+    <td>Uses an existing model for prediction.</td>
+</tr>
+<tr>
+    <td rowspan=3>Keyword</td>
+    <td>TARGET</td>
+    <td>Target column name of a training or prediction task.</td>
+</tr>
+<tr>
+    <td>FEATURES</td>
+    <td>Data feature column name of a training or prediction task.</td>
+</tr>
+<tr>
+    <td>MODEL</td>
+    <td>Model name of a training task.</td>
+</tr>
+    </table>
+
+## Developer Guide
+
+1. Introduce the algorithms supported in this version.
+
+   DB4AI of the current version supports logistic regression (binary classification tasks), linear regression, and vector machine algorithms (classification tasks) based on the SGD operator, as well as the K-Means clustering algorithm based on the K-Means operator.
+
+2. Learn about the model training syntax.
+
+   - CREATE MODEL
+
+     You can run the **CREATE MODEL** statement to create and train a model. Taking dataset **kmeans_2d** as an example, the data content of the table is as follows:
+
+     ```sql
+     mogdb=# select * from kmeans_2d;
+      id |              position
+     ----+-------------------------------------
+       1 | {74.5268815685995,88.2141939294524}
+       2 | {70.9565760521218,98.8114827475511}
+       3 | {76.2756086327136,23.8387574302033}
+       4 | {17.8495847294107,81.8449544720352}
+       5 | {81.2175785354339,57.1677675866522}
+       6 | {53.97752255667,49.3158342130482}
+       7 | {93.2475341879763,86.934042100329}
+       8 | {72.7659293473698,19.7020415100269}
+       9 | {16.5800288529135,75.7475957670249}
+      10 | {81.8520747194998,40.3476078575477}
+      11 | {76.796671198681,86.3827232690528}
+      12 | {59.9231450678781,90.9907738864422}
+      13 | {70.161884885747,19.7427458665334}
+      14 | {11.1269539105706,70.9988166182302}
+      15 | {80.5005071521737,65.2822235273197}
+      16 | {54.7030725912191,52.151339428965}
+      17 | {103.059707058128,80.8419883321039}
+      18 | {85.3574452036992,14.9910179991275}
+      19 | {28.6501615960151,76.6922890325077}
+      20 | {69.7285806713626,49.5416352967732}
+     (20 rows)
+     ```
+
+     The data type of the **position** field in this table is double precision[].
+
+   - The following uses K-Means as an example to describe how to train a model. Specify **position** as a feature column in the **kmeans_2d** training set, and use the K-Means algorithm to create and save the **point_kmeans** model.
+
+     ```sql
+     mogdb=# CREATE MODEL point_kmeans USING kmeans FEATURES position FROM kmeans_2d WITH num_centroids=3;
+     NOTICE:  Hyperparameter max_iterations takes value DEFAULT (10)
+     NOTICE:  Hyperparameter num_centroids takes value 3
+     NOTICE:  Hyperparameter tolerance takes value DEFAULT (0.000010)
+     NOTICE:  Hyperparameter batch_size takes value DEFAULT (10)
+     NOTICE:  Hyperparameter num_features takes value DEFAULT (2)
+     NOTICE:  Hyperparameter distance_function takes value DEFAULT (L2_Squared)
+     NOTICE:  Hyperparameter seeding_function takes value DEFAULT (Random++)
+     NOTICE:  Hyperparameter verbose takes value DEFAULT (0)
+     NOTICE:  Hyperparameter seed takes value DEFAULT (0)
+     MODEL CREATED. PROCESSED 1
+     ```
+
+     In the preceding command:
+
+     - The **CREATE MODEL** statement is used to train and save a model.
+
+     - **USING** specifies the algorithm name.
+
+     - **FEATURES** specifies the features of the training model and needs to be added based on the column name of the training data table.
+
+     - **TARGET** specifies the training target of the model. It can be the column name of the data table required for training or an expression, for example, **price > 10000**.
+
+     - **WITH** specifies the hyperparameters used for model training. When the hyperparameter is not set by the user, the framework uses the default value.
+
+       The framework supports various hyperparameter combinations for different operators.
+
+       **Table 2** Hyperparameters supported by operators
+
+       | Operator                                                     | Hyperparameter                                               |
+       | :----------------------------------------------------------- | :----------------------------------------------------------- |
+       | GD(logistic_regression, linear_regression, and svm_classification) | optimizer(char\*), verbose(bool), max_iterations(int), max_seconds(double), batch_size(int), learning_rate(double), decay(double), and tolerance(double)<br/>SVM limits the hyperparameter lambda(double). |
+       | K-Means                                                      | max_iterations(int), num_centroids(int), tolerance(double), batch_size(int), num_features(int), distance_function(char), seeding_function(char*), verbose(int), and seed(int) |
+
+       The default value and value range of each hyperparameter are as follows:
+
+       **Table 3** Default values and value ranges of hyperparameters
+
+       <table>
+           <tr>
+               <th>Operator</th>
+               <th>Default Hyperparameter Value</th>
+               <th>Value Range</th>
+               <th>Hyperparameter Description</th>
+           </tr>
+           <tr>
+               <td rowspan=10>GD (logistic_regression, linear_regression, and svm_classification)</td>
+               <td>optimizer = gd (gradient descent)</td>
+               <td>gd or ngd (natural gradient descent)</td>
+               <td>Optimizer</td>
+           </tr>
+           <tr>
+               <td>verbose = false</td>
+               <td>T or F</td>
+               <td>Log display</td>
+           </tr>
+           <tr>
+               <td>max_iterations = 100</td>
+               <td>(0, INT_MAX_VALUE]</td>
+               <td>Maximum iterations</td>
+           </tr>
+           <tr>
+               <td>max_seconds = 0 (The running duration is not limited.)</td>
+               <td>[0,INT_MAX_VALUE]</td>
+               <td>Running duration</td>
+           </tr>
+           <tr>
+               <td>batch_size = 1000</td>
+               <td>(0, MAX_MEMORY_LIMIT]</td>
+               <td>Number of data records selected per training</td>
+           </tr>
+           <tr>
+               <td>learning_rate = 0.8</td>
+               <td>(0, DOUBLE_MAX_VALUE]</td>
+               <td>Learning rate</td>
+           </tr>
+           <tr>
+               <td>decay = 0.95</td>
+               <td>(0, DOUBLE_MAX_VALUE]</td>
+               <td>Weight decay rate</td>
+           </tr>
+           <tr>
+               <td>tolerance = 0.0005</td>
+               <td>(0, DOUBLE_MAX_VALUE]</td>
+               <td>Tolerance</td>
+           </tr>
+           <tr>
+               <td>seed = 0 (random value of seed)</td>
+               <td>[0, INT_MAX_VALUE]</td>
+               <td>Seed</td>
+           </tr>
+           <tr>
+               <td>just for SVM：lambda = 0.01</td>
+               <td>(0, DOUBLE_MAX_VALUE)</td>
+               <td>Regularization parameter</td>
+           </tr>
+           <tr>
+               <td rowspan=9>Kmeans</td>
+               <td>max_iterations = 10</td>
+               <td>[1, INT_MAX_VALUE]</td>
+               <td>Maximum iterations</td>
+           </tr>
+           <tr>
+               <td>num_centroids = 10</td>
+               <td>[1, MAX_MEMORY_LIMIT]</td>
+               <td>Number of clusters</td>
+           </tr>
+           <tr>
+               <td>tolerance = 0.00001</td>
+               <td>(0,1)</td>
+               <td>Central point error</td>
+           </tr>
+           <tr>
+               <td>batch_size = 10</td>
+               <td>[1, MAX_MEMORY_LIMIT]</td>
+               <td>Number of data records selected per training</td>
+           </tr>
+           <tr>
+               <td>num_features = 2</td>
+               <td>[1, GS_MAX_COLS]</td>
+               <td>Number of sample features</td>
+           </tr>
+           <tr>
+               <td>distance_function = "L2_Squared"</td>
+               <td>L1, L2, L2_Squared, or Linf</td>
+               <td>Regularization method</td>
+           </tr>
+           <tr>
+               <td>seeding_function = "Random++"</td>
+               <td>"Random++" or "KMeans||"</td>
+               <td>Method for initializing seed points</td>
+           </tr>
+           <tr>
+               <td>verbose = 0U</td>
+               <td>{ 0, 1, 2 }</td>
+               <td>Verbose mode</td>
+           </tr>
+           <tr>
+               <td>seed = 0U</td>
+               <td>[0, INT_MAX_VALUE]</td>
+               <td>Seed</td>
+           </tr>
+           <tr>
+               <td colspan=4>MAX_MEMORY_LIMIT = Maximum number of tuples loaded in memory</td>
+           </tr>
+           <tr>
+               <td colspan=4>GS_MAX_COLS = Maximum number of attributes in a database table</td>
+           </tr>
+       </table>
+
+   - If the model is saved successfully, the following information is returned:
+
+     ```sql
+     MODEL CREATED. PROCESSED x
+     ```
+
+3. View the model information.
+
+   After the training is complete, the model is stored in the **gs_model_warehouse** system catalog. You can view information about the model and training process in the **gs_model_warehouse** system catalog.
+
+   You can view a model by viewing the system catalog. For example, run the following SQL statement to view the model named **point_kmeans**:
+
+   ```sql
+   mogdb=# select * from gs_model_warehouse where modelname='point_kmeans';
+   -[ RECORD 1 ]---------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+   modelname             | point_kmeans
+   modelowner            | 10
+   createtime            | 2021-04-30 17:30:39.59044
+   processedtuples       | 20
+   discardedtuples       | 0
+   pre_process_time      | 6.2001e-05
+   exec_time             | .000185272
+   iterations            | 5
+   outputtype            | 23
+   modeltype             | kmeans
+   query                 | CREATE MODEL point_kmeans USING kmeans FEATURES position FROM kmeans_2d WITH num_centroids=3;
+   modeldata             |
+   weight                |
+   hyperparametersnames  | {max_iterations,num_centroids,tolerance,batch_size,num_features,distance_function,seeding_function,verbose,seed}
+   hyperparametersvalues | {10,3,1e-05,10,2,L2_Squared,Random++,0,0}
+   hyperparametersoids   | {23,23,701,23,23,1043,1043,23,23}
+   coefnames             | {original_num_centroids,actual_num_centroids,dimension,distance_function_id,seed,coordinates}
+   coefvalues            | {3,3,2,2,572368998,"(77.282589,23.724434)(74.421616,73.239455)(18.551682,76.320914)"}
+   coefoids              |
+   trainingscoresname    |
+   trainingscoresvalue   |
+   modeldescribe         | {"id:1,objective_function:542.851169,avg_distance_to_centroid:108.570234,min_distance_to_centroid:1.027078,max_distance_to_centroid:297.210108,std_dev_distance_to_centroid:105.053257,cluster_size:5","id:2,objective_function:5825.982139,avg_distance_to_centroid:529.634740,min_distance_to_centroid:100.270449,max_distance_to_centroid:990.300588,std_dev_distance_to_centroid:285.915094,cluster_size:11","id:3,objective_function:220.792591,avg_distance_to_centroid:55.198148,min_distance_to_centroid:4.216111,max_distance_to_centroid:102.117204,std_dev_distance_to_centroid:39.319118,cluster_size:4"}
+   ```
+
+4. Use an existing model to perform a prediction task.
+
+   Use the **SELECT** and **PREDICT BY** keywords to complete the prediction task based on the existing model.
+
+   Query syntax: SELECT… PREDICT BY… (FEATURES…)… FROM…;
+
+   ```sql
+   mogdb=# SELECT id, PREDICT BY point_kmeans (FEATURES position) as pos FROM (select * from kmeans_2d limit 10);
+    id | pos
+   ----+-----
+     1 |   2
+     2 |   2
+     3 |   1
+     4 |   3
+     5 |   2
+     6 |   2
+     7 |   2
+     8 |   1
+     9 |   3
+    10 |   1
+   (10 rows)
+   ```
+
+   For the same prediction task, the results of the same model are stable. In addition, models trained based on the same hyperparameter and training set are stable. AI model training is random (random gradient descent of data distribution each batch). Therefore, the computing performance and results of different models can vary slightly.
+
+5. View the execution plan.
+
+   You can use the **EXPLAIN** statement to analyze the execution plan in the model training or prediction process of **CREATE MODEL** and **PREDICT BY**. The keyword **EXPLAIN** can be followed by a **CREATE MODEL** or **PREDICT BY** clause or an optional parameter. The supported parameters are as follows:
+
+   **Table 4** Parameters supported by EXPLAIN
+
+   | Parameter | Description                                                  |
+   | :-------- | :----------------------------------------------------------- |
+   | ANALYZE   | Boolean variable, which is used to add description information such as the running time and number of loop times |
+   | VERBOSE   | Boolean variable, which determines whether to output the training running information to the client |
+   | COSTS     | Boolean variable                                             |
+   | CPU       | Boolean variable                                             |
+   | DETAIL    | Boolean variable, which is available only in distributed mode |
+   | NODES     | Boolean variable, which is available only in distributed mode |
+   | NUM_NODES | Boolean variable, which is available only in distributed mode |
+   | BUFFERS   | Boolean variable                                             |
+   | TIMING    | Boolean variable                                             |
+   | PLAN      | Boolean variable                                             |
+   | FORMAT    | Optional format type: TEXT, XML, JSON, and YAML              |
+
+   Example:
+
+   ```sql
+   mogdb=# Explain CREATE MODEL patient_logisitic_regression USING logistic_regression FEATURES second_attack, treatment TARGET trait_anxiety > 50 FROM patients WITH batch_size=10, learning_rate = 0.05;
+   NOTICE:  Hyperparameter batch_size takes value 10
+   NOTICE:  Hyperparameter decay takes value DEFAULT (0.950000)
+   NOTICE:  Hyperparameter learning_rate takes value 0.050000
+   NOTICE:  Hyperparameter max_iterations takes value DEFAULT (100)
+   NOTICE:  Hyperparameter max_seconds takes value DEFAULT (0)
+   NOTICE:  Hyperparameter optimizer takes value DEFAULT (gd)
+   NOTICE:  Hyperparameter tolerance takes value DEFAULT (0.000500)
+   NOTICE:  Hyperparameter seed takes value DEFAULT (0)
+   NOTICE:  Hyperparameter verbose takes value DEFAULT (FALSE)
+   NOTICE:  GD shuffle cache size 212369
+                               QUERY PLAN
+   -------------------------------------------------------------------
+    Gradient Descent  (cost=0.00..0.00 rows=0 width=0)
+      ->  Seq Scan on patients  (cost=0.00..32.20 rows=1776 width=12)
+   (2 rows)
+   ```
+
+6. Perform troubleshooting in case of exceptions.
+
+   - Training phase
+
+     - Scenario 1: When the value of the hyperparameter exceeds the value range, the model training fails and an error message is returned. For example:
+
+       ```sql
+       mogdb=# CREATE MODEL patient_linear_regression USING linear_regression FEATURES second_attack,treatment TARGET trait_anxiety  FROM patients WITH optimizer='aa';
+       NOTICE:  Hyperparameter batch_size takes value DEFAULT (1000)
+       NOTICE:  Hyperparameter decay takes value DEFAULT (0.950000)
+       NOTICE:  Hyperparameter learning_rate takes value DEFAULT (0.800000)
+       NOTICE:  Hyperparameter max_iterations takes value DEFAULT (100)
+       NOTICE:  Hyperparameter max_seconds takes value DEFAULT (0)
+       NOTICE:  Hyperparameter optimizer takes value aa
+       ERROR:  Invalid hyperparameter value for optimizer. Valid values are: gd, ngd. (default is gd)
+       ```
+
+     - Scenario 2: If the model name already exists, the model fails to be saved, and an error message with the cause is displayed:
+
+       ```sql
+       mogdb=# CREATE MODEL patient_linear_regression USING linear_regression FEATURES second_attack,treatment TARGET trait_anxiety  FROM patients;
+       NOTICE:  Hyperparameter batch_size takes value DEFAULT (1000)
+       NOTICE:  Hyperparameter decay takes value DEFAULT (0.950000)
+       NOTICE:  Hyperparameter learning_rate takes value DEFAULT (0.800000)
+       NOTICE:  Hyperparameter max_iterations takes value DEFAULT (100)
+       NOTICE:  Hyperparameter max_seconds takes value DEFAULT (0)
+       NOTICE:  Hyperparameter optimizer takes value DEFAULT (gd)
+       NOTICE:  Hyperparameter tolerance takes value DEFAULT (0.000500)
+       NOTICE:  Hyperparameter seed takes value DEFAULT (0)
+       NOTICE:  Hyperparameter verbose takes value DEFAULT (FALSE)
+       NOTICE:  GD shuffle cache size 5502
+       ERROR:  The model name "patient_linear_regression" already exists in gs_model_warehouse.
+       ```
+
+     - Scenario 3: If the value in the **FEATURE** or **TARGETS** column is **\***, **ERROR** is returned with the error cause:
+
+       ```sql
+       mogdb=# CREATE MODEL patient_linear_regression USING linear_regression FEATURES *  TARGET trait_anxiety  FROM
+       patients;
+       ERROR:  FEATURES clause cannot be *
+       -----------------------------------------------------------------------------------------------------------------------
+       mogdb=# CREATE MODEL patient_linear_regression USING linear_regression FEATURES second_attack,treatment TARGET *  FROM patients;
+       ERROR:  TARGET clause cannot be *
+       ```
+
+     - Scenario 4: If the keyword **TARGET** is used in the unsupervised learning method or is not applicable to the supervised learning method, **ERROR** is returned with the error cause:
+
+       ```sql
+       mogdb=# CREATE MODEL patient_linear_regression USING linear_regression FEATURES second_attack,treatment FROM patients;
+       ERROR:  Supervised ML algorithms require TARGET clause
+       -----------------------------------------------------------------------------------------------------------------------------
+       CREATE MODEL patient_linear_regression USING linear_regression TARGET trait_anxiety  FROM patients;   ERROR:  Supervised ML algorithms require FEATURES clause
+       ```
+
+     - Scenario 5: If the GUC parameter **statement_timeout** is set, the statement that is executed due to training timeout will be terminated. In this case, execute the **CREATE MODEL** statement. Parameters such as the size of the training set, number of training rounds (**iteration**), early termination conditions (**tolerance** and **max_seconds**), and number of parallel threads (**nthread**) affect the training duration. When the duration exceeds the database limit, the statement execution is terminated and model training fails.
+
+   - Prediction phase
+
+     - Scenario 6: If the model name cannot be found in the system catalog, the database reports **ERROR**:
+
+       ```sql
+       mogdb=# select id, PREDICT BY patient_logistic_regression (FEATURES second_attack,treatment) FROM patients;
+       ERROR:  There is no model called "patient_logistic_regression".
+       ```
+
+     - Scenario 7: If the data dimension and data type of the **FEATURES** task are inconsistent with those of the training set, **ERROR** is reported and the error cause is displayed. For example:
+
+       ```sql
+       mogdb=# select id, PREDICT BY patient_linear_regression (FEATURES second_attack) FROM patients;
+       ERROR:  Invalid number of features for prediction, provided 1, expected 2
+       CONTEXT:  referenced column: patient_linear_regression_pred
+       -------------------------------------------------------------------------------------------------------------------------------------
+       mogdb=# select id, PREDICT BY patient_linear_regression (FEATURES 1,second_attack,treatment) FROM patients;
+       ERROR:  Invalid number of features for prediction, provided 3, expected 2
+       CONTEXT:  referenced column: patient_linear_regression_pre
+       ```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/AI-features/8-db4ai/8-4-pl-python-fenced-mode.md b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/8-db4ai/8-4-pl-python-fenced-mode.md
new file mode 100644
index 0000000000000000000000000000000000000000..f2bcefe30ed24207670c0ff0eb8c6a76bab3292c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/AI-features/8-db4ai/8-4-pl-python-fenced-mode.md
@@ -0,0 +1,135 @@
+---
+title: PL/Python Fenced Mode
+summary: PL/Python Fenced Mode
+author: Guo Huan
+date: 2021-10-20
+---
+
+# PL/Python Fenced Mode
+
+PL/Python is added to the fenced mode, which is insecure. During database compilation, to integrate Python into the database, you can add the **-with-python** option to **configure**, or specify the Python path for installing PL/Python and add the **-with-includes='/python-dir=path'** option.
+
+Before starting the database, set the GUC parameter **unix_socket_directory** to specify the file address for communication between unix_socket processes. You need to create a folder in **user-set-dir-path** in advance and grant read, write, and execute permissions on the folder.
+
+```bash
+unix_socket_directory = '/user-set-dir-path'
+```
+
+After the configuration is complete, start the database.
+
+After PL/Python is added to the database compilation and the GUC parameter **unix_socket_directory** is set, the **fenced-Master** process is automatically created during database startup. If Python compilation is not performed for the database, you need to manually start the master process in fenced mode. After the GUC parameter is set, run the command to create the master process.
+
+Run the following command to start the **fenced-Master** process:
+
+```bash
+gaussdb --fenced -k /user-set-dir-path -D /user-set-dir-path &
+```
+
+After the fenced mode is configured, the UDF calculation is performed in the **fenced-worker** process for the PL/Python-fenced UDF database.
+
+## User Guide
+
+- Create an extension.
+
+  - When the compiled PL/Python is Python 2:
+
+    ```sql
+    mogdb=# create extension plpythonu;
+    CREATE EXTENSION
+    ```
+
+  - When the compiled PL/Python is Python 3:
+
+    ```sql
+    mogdb=# create extension plpython3u;
+    CREATE EXTENSION
+    ```
+
+  The following uses Python 2 as an example.
+
+- Create a PL/Python-fenced UDF database.
+
+  ```sql
+  mogdb=# create or replace function pymax(a int, b int)
+  mogdb-# returns INT
+  mogdb-# language plpythonu fenced
+  mogdb-# as $$
+  mogdb$# import numpy
+  mogdb$# if a > b:
+  mogdb$#     return a;
+  mogdb$# else:
+  mogdb$#     return b;
+  mogdb$# $$;
+  CREATE FUNCTION
+  ```
+
+- View UDF information.
+
+  ```sql
+  mogdb=# select * from pg_proc where proname='pymax';
+  -[ RECORD 1 ]----+--------------
+  proname          | pymax
+  pronamespace     | 2200
+  proowner         | 10
+  prolang          | 16388
+  procost          | 100
+  prorows          | 0
+  provariadic      | 0
+  protransform     | -
+  proisagg         | f
+  proiswindow      | f
+  prosecdef        | f
+  proleakproof     | f
+  proisstrict      | f
+  proretset        | f
+  provolatile      | v
+  pronargs         | 2
+  pronargdefaults  | 0
+  prorettype       | 23
+  proargtypes      | 23 23
+  proallargtypes   |
+  proargmodes      |
+  proargnames      | {a,b}
+  proargdefaults   |
+  prosrc           |
+                   | import numpy
+                   | if a > b:
+                   |     return a;
+                   | else:
+                   |     return b;
+                   |
+  probin           |
+  proconfig        |
+  proacl           |
+  prodefaultargpos |
+  fencedmode       | t
+  proshippable     | f
+  propackage       | f
+  prokind          | f
+  proargsrc        |
+  ```
+
+- Run the UDF.
+
+  - Create a data table.
+
+    ```sql
+    mogdb=# create table temp (a int ,b int) ;
+    CREATE TABLE
+    mogdb=# insert into temp values (1,2),(2,3),(3,4),(4,5),(5,6);
+    INSERT 0 5
+    ```
+
+  - Run the UDF.
+
+    ```sql
+    mogdb=# select pymax(a,b) from temp;
+    pymax
+    -------
+        2
+        3
+        4
+        5
+        6
+    (5 rows)
+    ```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/autonomous-transaction/1-introduction-to-autonomous-transaction.md b/product/en/docs-mogdb/v3.0/developer-guide/autonomous-transaction/1-introduction-to-autonomous-transaction.md
new file mode 100644
index 0000000000000000000000000000000000000000..604bb593648d89fd718f9a4728b7afbd1e85d924
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/autonomous-transaction/1-introduction-to-autonomous-transaction.md
@@ -0,0 +1,12 @@
+---
+title: Introduction
+summary: Introduction
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# Introduction
+
+An autonomous transaction is an independent transaction that is started during the execution of a primary transaction. Committing and rolling back an autonomous transaction does not affect the data that has been committed by the primary transaction. In addition, an autonomous transaction is not affected by the primary transaction.
+
+Autonomous transactions are defined in stored procedures, functions, and anonymous blocks, and are declared using the **PRAGMA AUTONOMOUS_TRANSACTION** keyword.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/autonomous-transaction/2-function-supporting-autonomous-transaction.md b/product/en/docs-mogdb/v3.0/developer-guide/autonomous-transaction/2-function-supporting-autonomous-transaction.md
new file mode 100644
index 0000000000000000000000000000000000000000..50bc79d4dcb4f8479ea0a736b32be80311a3dedf
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/autonomous-transaction/2-function-supporting-autonomous-transaction.md
@@ -0,0 +1,41 @@
+---
+title: Function Supporting Autonomous Transaction
+summary: Function Supporting Autonomous Transaction
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# Function Supporting Autonomous Transaction
+
+An autonomous transaction can be defined in a function. The identifier of an autonomous transaction is **PRAGMA AUTONOMOUS_TRANSACTION**. The syntax of an autonomous transaction is the same as that of creating a function. The following is an example.
+
+```sql
+create table t4(a int, b int, c text);
+
+CREATE OR REPLACE function autonomous_32(a int ,b int ,c text) RETURN int AS
+DECLARE
+    PRAGMA AUTONOMOUS_TRANSACTION;
+BEGIN
+    insert into t4 values(a, b, c);
+    return 1;
+END;
+/
+CREATE OR REPLACE function autonomous_33(num1 int) RETURN int AS
+DECLARE
+    num3 int := 220;
+    tmp int;
+    PRAGMA AUTONOMOUS_TRANSACTION;
+BEGIN
+    num3 := num3/num1;
+    return num3;
+EXCEPTION
+    WHEN division_by_zero THEN
+        select autonomous_32(num3, num1, sqlerrm) into tmp;
+        return 0;
+END;
+/
+
+select autonomous_33(0);
+
+select * from t4;
+```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/autonomous-transaction/3-stored-procedure-supporting-autonomous-transaction.md b/product/en/docs-mogdb/v3.0/developer-guide/autonomous-transaction/3-stored-procedure-supporting-autonomous-transaction.md
new file mode 100644
index 0000000000000000000000000000000000000000..65adcbc347df7a23f6afa890b621f08bce920aa2
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/autonomous-transaction/3-stored-procedure-supporting-autonomous-transaction.md
@@ -0,0 +1,45 @@
+---
+title: Stored Procedure Supporting Autonomous Transaction
+summary: Stored Procedure Supporting Autonomous Transaction
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# Stored Procedure Supporting Autonomous Transaction
+
+An autonomous transaction can be defined in a stored procedure. The identifier of an autonomous transaction is **PRAGMA AUTONOMOUS_TRANSACTION**. The syntax of an autonomous transaction is the same as that of creating a stored procedure. The following is an example.
+
+```sql
+-- Create a table.
+create table t2(a int, b int);
+insert into t2 values(1,2);
+select * from t2;
+
+-- Create a stored procedure that contains an autonomous transaction.
+CREATE OR REPLACE PROCEDURE autonomous_4(a int, b int)  AS
+DECLARE
+    num3 int := a;
+    num4 int := b;
+    PRAGMA AUTONOMOUS_TRANSACTION;
+BEGIN
+    insert into t2 values(num3, num4);
+    dbe_output.print_line('just use call.');
+END;
+/
+-- Create a common stored procedure that invokes an autonomous transaction stored procedure.
+CREATE OR REPLACE PROCEDURE autonomous_5(a int, b int)  AS
+DECLARE
+BEGIN
+    dbe_output.print_line('just no use call.');
+    insert into t2 values(666, 666);
+    autonomous_4(a,b);
+    rollback;
+END;
+/
+-- Invoke a common stored procedure.
+select autonomous_5(11,22);
+-- View the table result.
+select * from t2 order by a;
+```
+
+In the preceding example, a stored procedure containing an autonomous transaction is finally executed in a transaction block to be rolled back, which directly illustrates a characteristic of the autonomous transaction, that is, rollback of the primary transaction does not affect content that has been committed by the autonomous transaction.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/autonomous-transaction/4-restrictions.md b/product/en/docs-mogdb/v3.0/developer-guide/autonomous-transaction/4-restrictions.md
new file mode 100644
index 0000000000000000000000000000000000000000..e15ba978707d998d53f7ddfb0ce7c59797211bc7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/autonomous-transaction/4-restrictions.md
@@ -0,0 +1,73 @@
+---
+title: Restrictions
+summary: Restrictions
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# Restrictions
+
+- A trigger function does not support autonomous transactions.
+
+- In the autonomous transaction block of a function or stored procedure, static SQL statements do not support variable transfer.
+
+  ```sql
+  -- Autonomous transactions do not support the execution of the following functions. The SQL statement contains the variable i.
+  CREATE OR REPLACE FUNCTION autonomous_easy_2(i int) RETURNS integer
+  LANGUAGE plpgsql
+  AS $$
+  DECLARE
+  PRAGMA AUTONOMOUS_TRANSACTION;
+  BEGIN
+  START TRANSACTION;
+  INSERT INTO test1 VALUES (i, 'test');
+  COMMIT;
+  RETURN 42;
+  END;
+  $$;
+  -- To use the parameter transfer, use the dynamic statement EXECUTE to replace variables. The following is an example:
+  CREATE OR REPLACE FUNCTION autonomous_easy(i int) RETURNS integer
+  LANGUAGE plpgsql
+  AS $$
+  DECLARE
+  PRAGMA AUTONOMOUS_TRANSACTION;
+  BEGIN
+  START TRANSACTION;
+  EXECUTE 'INSERT INTO test1 VALUES (' || i::integer || ', ''test'')';
+  COMMIT;
+  RETURN 42;
+  END;
+  $$;
+  ```
+
+- Autonomous transactions do not support nesting.
+
+    > **NOTICE:** In a function that contains an autonomous transaction, it is not allowed to explicitly execute another function or stored procedure that contains an autonomous transaction through **PERFORM**, **SELECT**, or **CALL**. However, another function or stored procedure that contains an autonomous transaction can be explicitly called in the last **RETURN**.
+
+- A function containing an autonomous transaction does not support the return value of parameter transfer.
+
+    ```sql
+    -- In the following example, the return value ret is not transferred and only null is returned.
+    create or replace function at_test2(i int) returns text
+    LANGUAGE plpgsql
+    as $$
+    declare
+    ret text;
+    pragma autonomous_transaction;
+    begin
+    START TRANSACTION;
+    insert into at_tb2 values(1, 'before s1');
+    if i > 10 then
+    rollback;
+    else
+    commit;
+    end if;
+    select val into ret from at_tb2 where id=1;
+    return ret;
+    end;
+    $$;
+    ```
+
+- A stored procedure or function that contains an autonomous transaction does not support exception handling.
+
+- A trigger function does not support autonomous transactions.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/autonomous-transaction/anonymous-block-supporting-autonomous-transaction.md b/product/en/docs-mogdb/v3.0/developer-guide/autonomous-transaction/anonymous-block-supporting-autonomous-transaction.md
new file mode 100644
index 0000000000000000000000000000000000000000..93485a923a88aa2d935624ee75946740d7ae2224
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/autonomous-transaction/anonymous-block-supporting-autonomous-transaction.md
@@ -0,0 +1,29 @@
+---
+title: Anonymous Block Supporting Autonomous Transaction
+summary: Anonymous Block Supporting Autonomous Transaction
+author: Guo Huan
+date: 2021-10-15
+---
+
+# Anonymous Block Supporting Autonomous Transaction
+
+An autonomous transaction can be defined in an anonymous block. The identifier of an autonomous transaction is **PRAGMA AUTONOMOUS_TRANSACTION**. The syntax of an autonomous transaction is the same as that of creating an anonymous block. The following is an example.
+
+```sql
+create table t1(a int ,b text);
+
+START TRANSACTION;
+DECLARE
+    PRAGMA AUTONOMOUS_TRANSACTION;
+BEGIN
+    dbe_output.print_line('just use call.');
+    insert into t1 values(1,'you are so cute,will commit!');
+END;
+/
+insert into t1 values(1,'you will rollback!');
+rollback;
+
+select * from t1;
+```
+
+In the preceding example, an anonymous block containing an autonomous transaction is finally executed before a transaction block to be rolled back, which directly illustrates a characteristic of the autonomous transaction, that is, rollback of the primary transaction does not affect content that has been committed by the autonomous transaction.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/1-development-specifications.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/1-development-specifications.md
new file mode 100644
index 0000000000000000000000000000000000000000..a19bf3de377ecca7ada9703afcd67cdcd48a3006
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/1-development-specifications.md
@@ -0,0 +1,752 @@
+---
+title: Development Specifications
+summary: Development Specifications
+author: Guo Huan
+date: 2021-07-21
+---
+
+# Development Specifications
+
+If the connection pool mechanism is used during application development, comply with the following specifications:
+
+- If GUC parameters are set in the connection, run **SET SESSION AUTHORIZATION DEFAULT;RESET ALL;** to clear the connection status before you return the connection to the connection pool.
+- If a temporary table is used, delete the temporary table before you return the connection to the connection pool.
+
+If you do not do so, the connection in the connection pool will be stateful, which affects subsequent operations on the connection pool.
+
+## Overview
+
+### Introduction
+
+Although ISO has issued SQL-92, SQL:1999, SQL:2006, and other standards for SQL, due to the characteristics of different databases, the same functions are not the same in the implementation of their products, which also makes the relevant grammatical rules different. Therefore, when formulating specific development specifications, it is necessary to write corresponding specifications for different databases.
+
+This specification emphasizes practicability and operability. According to the common problems and mistakes easily made by developers in the coding process, detailed and clear specifications and constraints are carried out on all aspects of code writing. It mainly includes the following content:
+
+- Naming specification
+
+- Design specification
+
+- Syntax specification
+
+- Optimization-related specification
+
+- PG compatibility
+
+- Commonly used functions
+
+In addition, specific examples are given for each detailed rule of the specification.
+
+### Application Scope
+
+This specification applies to MogDB 1.1.0 and later versions.
+
+## Naming Specification
+
+### Unified Object Naming Specification
+
+The unified standards for naming database objects, such as database, schema, table, column, view, index, constraint, sequence, function, trigger, etc. are as follows:
+
+- It is advised to use a combination of lowercase letters, numbers, and underscores.
+
+- It is advised to use meaningful English vocabularies.
+
+- It is not advised to use double quotation marks (") unless it must contain special characters such as uppercase letters or spaces.
+
+- The length cannot exceed 63 characters.
+
+- It is not advised to start with PG, GS (to avoid confusion with the system DB object), and it is not advised to start with a number.
+
+- It is forbidden to use reserved words. Refer to official documents for reserved keywords.
+
+- The number of columns that a table can contain varies from 250 to 1600 depending on the field type.
+
+### Temporary and Backup Object Naming
+
+- It is recommended to add a date to the names of temporary or backup database objects (such as table), for example, dba.trade_record_2020_12_08 (where dba is the DBA-specific schema, trade_record is the table name, and 2020_12_08 is the backup date).
+
+### Tablespace Naming
+
+- The user tablespace of the database is represented by **ts_\<tablespace name>**, where the **tablespace name** contains the following two categories:
+  1. Data space: For the user's default tablespace, it is represented by **default**. For other tablespaces, it is represented according to the category of the tables hosted on the tablespace. For example, the table that stores code is represented by **code**. The table that stores customer information is represented by **customer**. Try to use one tablespace to host the tables of that category. If a table is particularly large, consider using a separate tablespace.
+  2. Index space: add **idx_** in front of the name of the corresponding data tablespace. For example, the index space for the user's default tablespace is represented by **ts_idx_default**. For index tablespace of code table, use **ts_idx_code**.
+- The tablespace name is prohibited to start with **PG_**.
+
+### Index Naming
+
+- Index object naming rules: **table_column_idx**, such as **student_name_idx**, the index naming method is the default naming method when the index name is not explicitly specified when an index is created for the MogDB database.
+
+  Therefore, it is advised to create indexes without naming them explicitly, but using DBMS defaults.
+
+```sql
+create unique index on departments(department_id);
+
+CREATE INDEX
+
+ \di
+
++----------+-------------------------------+--------+---------+
+
+| Schema  | Name              | Type  | Owner  |
+
+|----------+-------------------------------+--------+---------|
+
+| mogdb   | departments_department_id_idx | index  | mogdb  |
+
++----------+-------------------------------+--------+---------+
+
+SELECT 1
+```
+
+### Variables Naming
+
+- English words should be used for naming, and pinyin should be avoided, especially pinyin abbreviations should not be used. Chinese or special characters are not allowed in the naming.
+
+- If no complicated operations are involved, simple applications such as counting are always defined by number.
+
+### Partitioned Table Naming
+
+- The name of the partitioned table follows the naming rules of ordinary tables.
+
+- A table is partitioned by time range (one partition per month), and the partition name is **PART_YYYYMM**.
+
+  For example, PART_201901 and PART_201902
+
+### Function Naming
+
+- The name should be consistent with its actual function. A verb should be used as a prefix command to cause an action to take place.
+
+Example: The following naming conforms to the specification:
+
+```
+func_addgroups (Add multiple groups)
+func_addgroup (Add one group)
+```
+
+## Design Specification
+
+### Database Design
+
+- The database is preferentially created using the PG compatibility type.
+
+- The database encoding can use only utf8.
+
+### Tablespace Design
+
+- Generally larger tables or indexes use a separate tablespace.
+
+- The objects for which high frequency insert statements need to be run are divided into a group and stored in the corresponding tablespace.
+
+- The objects added, deleted, and modified are divided into groups and stored in the corresponding tablespace.
+
+- Tables and indexes are stored in separate tablespaces.
+
+- In principle, each schema corresponds to a tablespace and a corresponding index tablespace; each large table under a schema corresponds to a separate tablespace and index tablespace.
+
+### Table Design
+
+- When designing a table structure, you should plan well to avoid adding fields frequently, or modifying field types or lengths.
+
+- You must add comment information to the table, and make sure that the table name matches the comment information.
+
+- It is forbidden to use the **unlogged** keyword to create a new table. By default, a non-compressed row-based table is created.
+
+- When each table is created, you must specify the tablespace where it is located. Do not use the default tablespace to prevent the table from being built on the system tablespace and thereby causing performance problems. For data tables with busy transactions, they must be stored in a dedicated tablespace.
+
+- The data types of the fields used for the connection relationship between the tables must be strictly consistent to avoid the inability of the index to be used normally.
+
+- It is forbidden to use **VARCHAR** or other character types to store date values. If it is used, operations cannot be performed on this field, and it needs to be strictly defined in the data specification.
+
+- The field must be added with a comment that can clearly indicate its meaning, and the description of each state value must be clearly listed in the comment of the state field.
+
+- For frequently updated tables, it is advised to specify **fillfactor=85** during table creation, and reserve 15% of the space on each page for HOT updates.
+
+- The data type defined by the field in the table structure is consistent with that in the application, and the field collation rules between tables are consistent to avoid errors or inability to use indexes.
+
+  Note: For example, the data type of the **user_id** field of table A is defined as **varchar**, but the SQL statement is **where user_id=1234;**
+
+### Partitioned Table Design
+
+- The partitioned tables supported by MogDB database are range partitioned tables.
+
+- The number of partitioned tables is not recommended to exceed 1000.
+
+- The primary key or unique index must contain the partition key.
+
+- For tables with a relatively large amount of data, they should be partitioned according to the properties of the table data to get a better performance.
+
+- To convert a normal table into a partitioned table, you need to create a new partitioned table, and then import the data from the normal table into the newly created partitioned table. Therefore, when you initially design the table, please plan in advance whether to use partitioned tables according to your business.
+
+- For businesses with regular historical data deletion needs, it is recommended to partition the tables by time and not use the **DELETE** operation when deleting, but **DROP** or **TRUNCATE** the corresponding table.
+
+- It is not recommended to use a global index in a partitioned table, because the partition maintenance operation may cause the global index to fail and make it difficult to maintain.
+
+#### Use of Partitioned Table
+
+Operate on the range partitioned table as follows.
+
+- Create a tablespace
+
+```sql
+mogdb=# CREATE TABLESPACE example1 RELATIVE LOCATION 'tablespace1/tablespace_1';
+mogdb=# CREATE TABLESPACE example2 RELATIVE LOCATION 'tablespace2/tablespace_2';
+mogdb=# CREATE TABLESPACE example3 RELATIVE LOCATION 'tablespace3/tablespace_3';
+mogdb=# CREATE TABLESPACE example4 RELATIVE LOCATION 'tablespace4/tablespace_4';
+```
+
+When the following information is displayed, it means the creation is successful.
+
+```sql
+CREATE TABLESPACE
+```
+
+- Create a partitioned table
+
+```sql
+mogdb=# CREATE TABLE mogdb_usr.customer_address
+(
+  ca_address_sk    integer          NOT NULL  ,
+  ca_address_id    character(16)       NOT NULL  ,
+  ca_street_number   character(10)            ,
+  ca_street_name    character varying(60)        ,
+  ca_street_type    character(15)            ,
+  ca_suite_number   character(10)            ,
+  ca_city       character varying(60)        ,
+  ca_county      character varying(30)        ,
+  ca_state       character(2)             ,
+  ca_zip        character(10)            ,
+  ca_country      character varying(20)        ,
+  ca_gmt_offset    numeric(5,2)             ,
+  ca_location_type   character(20)
+)
+TABLESPACE example1
+
+PARTITION BY RANGE (ca_address_sk)
+(
+    PARTITION P1 VALUES LESS THAN(5000),
+    PARTITION P2 VALUES LESS THAN(10000),
+    PARTITION P3 VALUES LESS THAN(15000),
+    PARTITION P4 VALUES LESS THAN(20000),
+    PARTITION P5 VALUES LESS THAN(25000),
+    PARTITION P6 VALUES LESS THAN(30000),
+    PARTITION P7 VALUES LESS THAN(40000),
+    PARTITION P8 VALUES LESS THAN(MAXVALUE) TABLESPACE example2
+)
+ENABLE ROW MOVEMENT;
+```
+
+When the following information is displayed, it means the creation is successful.
+
+```sql
+CREATE TABLE
+```
+
+   ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) It is recommended that the number of column-based partitioned tables does not exceed 1,000.
+
+- Insert data
+
+Insert data from table **mogdb_usr.customer_address** into table **mogdb_usr.customer_address_bak**. For example, you have created a backup table **mogdb_usr.customer_address_bak** of table **mogdb_usr.customer_address** in the database, and now you need to insert the data from table **mogdb_usr.customer_address** into table **mogdb_usr. customer_address_bak**, then you can run the following command.
+
+```sql
+mogdb=# CREATE TABLE mogdb_usr.customer_address_bak
+(
+  ca_address_sk    integer          NOT NULL  ,
+  ca_address_id    character(16)       NOT NULL  ,
+  ca_street_number   character(10)            ,
+  ca_street_name    character varying(60)        ,
+  ca_street_type    character(15)            ,
+  ca_suite_number   character(10)            ,
+  ca_city       character varying(60)        ,
+  ca_county      character varying(30)        ,
+  ca_state       character(2)             ,
+  ca_zip        character(10)            ,
+  ca_country      character varying(20)        ,
+  ca_gmt_offset    numeric(5,2)             ,
+  ca_location_type   character(20)
+)
+TABLESPACE example1
+PARTITION BY RANGE (ca_address_sk)
+(
+    PARTITION P1 VALUES LESS THAN(5000),
+    PARTITION P2 VALUES LESS THAN(10000),
+    PARTITION P3 VALUES LESS THAN(15000),
+    PARTITION P4 VALUES LESS THAN(20000),
+    PARTITION P5 VALUES LESS THAN(25000),
+    PARTITION P6 VALUES LESS THAN(30000),
+    PARTITION P7 VALUES LESS THAN(40000),
+    PARTITION P8 VALUES LESS THAN(MAXVALUE) TABLESPACE example2
+)
+ENABLE ROW MOVEMENT;
+CREATE TABLE
+mogdb=# INSERT INTO mogdb_usr.customer_address_bak SELECT * FROM mogdb_usr.customer_address;
+INSERT 0 0
+```
+
+- Alter partitioned table row movement properties
+
+```sql
+mogdb=# ALTER TABLE mogdb_usr.customer_address_bak DISABLE ROW MOVEMENT;
+ALTER TABLE
+```
+
+- Delete a partition
+
+Delete partition P8。
+
+```sql
+mogdb=# ALTER TABLE mogdb_usr.customer_address_bak DROP PARTITION P8;
+ALTER TABLE
+```
+
+- Add a partition
+
+Add partition P8. The range is 40000<= P8<=MAXVALUE.
+
+```sql
+mogdb=# ALTER TABLE mogdb_usr.customer_address_bak ADD PARTITION P8 VALUES LESS THAN (MAXVALUE);
+ALTER TABLE
+```
+
+- Rename a partition
+
+Rename partition P8 as P_9.
+
+```sql
+mogdb=# ALTER TABLE mogdb_usr.customer_address_bak RENAME PARTITION P8 TO P_9;
+ALTER TABLE
+```
+
+Rename partition  P_9 as P8.
+
+```sql
+mogdb=# ALTER TABLE mogdb_usr.customer_address_bak RENAME PARTITION FOR (40000) TO P8;
+ALTER TABLE
+```
+
+- Alter the tablespace of partition
+
+Alter the tablespace of partition P6 to example3.
+
+```sql
+mogdb=#  ALTER TABLE mogdb_usr.customer_address_bak MOVE PARTITION P6 TABLESPACE example3;
+ALTER TABLE
+```
+
+Alter the tablespace of partition P4 to example4.
+
+```sql
+mogdb=#  ALTER TABLE mogdb_usr.customer_address_bak MOVE PARTITION P4 TABLESPACE example4;
+ALTER TABLE
+```
+
+- Query a partition
+
+Query partition P6.
+
+```sql
+mogdb=# SELECT * FROM mogdb_usr.customer_address_bak PARTITION (P6);
+mogdb=# SELECT * FROM mogdb_usr.customer_address_bak PARTITION FOR (35888);
+```
+
+- Delete a partitioned table and tablespace
+
+```sql
+mogdb=# DROP TABLE mogdb_usr.customer_address_bak;
+DROP TABLE
+mogdb=# DROP TABLESPACE example1;
+mogdb=# DROP TABLESPACE example2;
+mogdb=# DROP TABLESPACE example3;
+mogdb=# DROP TABLESPACE example4;
+DROP TABLESPACE
+```
+
+### Column Design
+
+- It is recommended to avoid using character types when numeric types can be used.
+
+- It is recommended to avoid using **char(N)** if you can use **varchar(N)**, and avoid using **text** and **varchar** if you can use **varchar(N)**.
+
+- Only **char(N)**, **varchar(N)** and **text** character types are allowed.
+
+- The newly created MogDB database is compatible with Oracle by default, and the **not null** constraint does not support empty strings. Empty strings will be converted to **null** by default. Databases compatible with the PG mode will not have this problem.
+
+- It is recommended to use **timestamp with time zone (timestamptz)** instead of **timestamp without time zone**.
+
+- It is recommended to use **NUMERIC (precision, scale)** to store currency amounts and other values that require precise calculations, but not to use **real**, **double precision**.
+
+### Sequence Design
+
+- It is forbidden to manually add sequences related to the table.
+
+- A sequence is created by specifying the **serial** or **bigserial** type of the column when a table is created.
+
+- The sequence should be consistent with the variable definition type and range in the code to prevent data from being unable to be inserted.
+
+### Constraint Design
+
+#### Primary Key Constraint
+
+- Each table must include a primary key.
+- It is not recommended that the name of the primary key has the service meaning, such as identification certificate or country name although the name is unique.
+- It is recommended that a primary key is written as id serial primary key or id bigserial primary key.
+- It is recommended that the primary key in a large-sized table can be written as follows, which is easy to maintain later.
+
+```sql
+create table test(id serial not null );
+create unique index CONCURRENTLY ON test (id);
+```
+
+#### Unique Constraint
+
+Apart from the primary key, unique constraint is needed. You can create a unique index with uk_ as the prefix to create unique constraint.
+
+#### Foreign Key Constraint
+
+- You'd better create foreign key constraints for a table with foreign key relationship.
+- When using the foreign key, you must set the action of the foreign key, such as cascade, set null, or set default.
+
+#### Non-Empty Column
+
+- All non-empty columns must be clearly marked as NOT NULL during database creation. After the database is used, no change can be performed. Additionally, you need to pay attention to the difference of the query results between NULL and "": null will be converted to NULL while "" does not display any character.
+
+#### Check Constraint
+
+- For fields with the check constraint, it is required to specify the check rules, such as the gender and status fields.
+
+### Index Design
+
+- MogDB provides the row-store and column-store tables. The row-store table supports the btree (default), gin, and gist index types. The column-store table supports the Psort (default), btree, and gin index types.
+- It is recommended that the CONCURRENTLY parameter is added when you create or drop an index. This can achieve concurrency when data is written into a table. The column-store, partition, and temporary tables do not support index created CONCURRENTLY.
+- It is recommended that "create index CONCURRENTLY" and "drop index CONCURRENTLY" are used to maintain the related indexes of a table whose columns included in the indexes are frequently updated and deleted.
+- It is recommended that unique index is used to replace unique constraints, facilitating follow-up maintenance.
+- It is recommended that a joint index of multiple fields are created based on data distribution for a high-frequency query in which there are multiple fields and conditions in the where statement.
+- Each table can include five indexes at most.
+- Deep analysis is required for creation of composite indexes.
+  - The first field in a composite index needs to be correctly chosen. Generally, it has good selectivity and is a common field in the where clause.
+  - If several fields in a composite index are usually presented in a where clause and linked with AND, and single-field query is less or even not involved, you can create a composite index. Otherwise, you can create a single-field index.
+  - If several fields in a composite index are usually presented in a where clause individually, they can be divided into multiple single-field indexes.
+  - If both single-field index and composite index with the single field as its first column, the single-field index can be deleted.
+  - Typically, the first field in a composite index cannot be a time field because the time field is used to scan a range. However, when the former fields are scanned by range, the latter fields cannot be used for index filtration.
+  - A composite index can include four fields at most.
+- For a table with the number of write times significantly greater than that of read times, you'd better not create too many indexes.
+- Unused indexes and duplicated indexes should be deleted so that the execution plan and database performance are not affected.
+
+### View Design
+
+- You'd better use simple views and use less complex views.
+
+  Simple view: Data comes from a single table and a simple view does not contain groups of data and functions.
+
+  Complex view: Data comes from multiple tables, or a complex view contains groups of data or functions. A complex view can contain three tables at most.
+
+- You'd better not use nested views. If nested views have to be used, it is advised to have two levels of nesting at most.
+
+### Function Design
+
+- A function must retrieve database table records or other database objects, or even modify database information, such as Insert, Delete, Update, Drop, or Create.
+- If a function does not relate to a database, it cannot be realized using a database function.
+- It is not advised to use DML or DDL statements in a function.
+
+## Syntax Specification
+
+### About NULL
+
+- Note: Check whether it is null or is not null.
+- Note: The values of the boolean type can be true, false, and NULL.
+- Note: Pay attention to that the NOT IN set includes some NULL elements.
+
+```sql
+mogdb=# SELECT * FROM (VALUES(1),(2)) v(a) ;  a
+
+\---
+
+ 1
+
+ 2
+
+(2 rows)
+
+mogdb=# select 1 NOT IN (1,NULL);
+
+?column?
+
+\---------
+
+f
+
+(1 row)
+
+mogdb=# select 2 NOT IN (1,NULL);
+
+?column?
+
+\---------
+
+(1 row)
+
+mogdb=# SELECT * FROM (VALUES(1),(2)) v(a) WHERE a NOT IN (1, NULL);  a
+
+\---
+
+(0 rows)
+```
+
+- Suggestion: It is recommended that count(1) or count(\*) is used to count the number of rows. count(col) is not used to count the number of rows because the NULL value is not counted.
+- Rule: For count(names of multiple columns), the names of multiple columns must be enclosed in brackets, for example count((col1,col2,col3)).
+- Note: For count (names of multiple columns), even if the values of all columns are null, the columns will also be counted. Therefore, the calculating result of count(names of multiple columns) is consistent with that of count(\*).
+- Note: count(distinct col) is used to count the number of values that are distinct from each other and not null.
+
+count(distinct (col1,col2,...)) is used to calculate the unique value of those of all columns where NULL is counted. Additionally, two NULL values are considered the same.
+
+- Note: Distinction between count and sum of NULL
+
+```sql
+select count(1), count(a), sum(a)  from (SELECT * FROM (VALUES (NULL), (2) ) v(a)) as foo where a is NULL;
+
+count | count | sum
+
+-------+-------+-----
+
+   1 |   0 |
+
+(1 row)
+```
+
+- Check whether two values are the same (NULL is considered as the same value).
+
+```sql
+select null is distinct from null;
+
+?column?
+
+\---------
+
+f
+
+(1 row)
+
+select null is distinct from 1;
+
+?column?
+
+\---------
+
+t
+
+(1 row)
+
+select null is not distinct from null;
+
+?column?
+
+\---------
+
+t
+
+(1 row)
+
+select null is not distinct from 1;
+
+?column?
+
+\---------
+
+f
+
+(1 row)
+```
+
+### About Invalid Indexes
+
+- During SQL statement writing, functions and expressions are usually used  in query operations. It is not recommended that functions and expressions are used in condition columns. Using a function or expression in a condition column will make indexes of the condition column unused, thereby affecting the SQL query efficiency. It is recommended that functions or expressions are used in condition values. For example,
+
+  `select name from tab where id+100>1000;`
+
+  This statement can be changed to the following:
+
+  `select name from tab where id>1000-100;`
+
+- Do not use left fuzzy query. For example,
+
+  `select id from tab where name like '%ly';`
+
+- Do not use the negative query, such as not in/like. For example,
+
+  `select id from tab where name not in ('ly','ty');`
+
+### Ensuring That All Variables and Parameters Are Used
+
+- Declare-variable also generates certain system overhead and makes code look loose. If some variables are not used in compilation, they will report alarms. Make sure that no any alarm is reported.
+
+## Query Operations
+
+### DDL Operation
+
+- Database object, especially columns with comments added can facilitate service learning and maintenance.
+- DDL sent to DBAs, which is attached with common SQLs, such as SELECT, INSERT, DELETE, and UPDATE, can assist DBAs providing optimization suggestions, including creating index CONCURRENTLY.
+- When columns need to be added to a large-sized table, "alter table t add column col datatype not null default xxx" can be processed as follows. This can prevent the table from being locked due to long time for filling in the default values.
+
+```sql
+alter table t add column col datatype ；
+
+alter table t alter column col set default xxx；
+
+update table t  set column= DEFAULT where id in ( select id from t where column is null limit
+
+1000 ) ; \watch 3
+
+alter table t alter column col set not null；
+```
+
+### DML Operation
+
+- When updating a table, the "<>" judgement is needed. For example, the statement "update table_a set column_b = c where column_b <> c" indicates that a table needs to be updated to make the value of column b equal to that of column c if the value of column b is not equal to that of column c. In the statement, it is prohibited that the value of column b is equal to that of column c in the where clause.
+- A single DML statement can support a maximum of 100 thousand data records.
+- When a table needs to be cleared, it is recommended that TRUNCATE is used rather than DELETE.
+
+### DQL Operation
+
+- Typically, it is prohibited to use select \*. Selecting only necessary fields can reduce the consumption of including but not limited to network bandwidth and prevent programs from being affected by table structure modification, such as some prepare queries.
+- For report-based queries or basic data queries, materialized views can be used to periodically take data snapshots, so that multiple tables are not performed on the same query repeatedly, especially for tables with frequent write operations.
+- Window functions can be used for complex statistics queries.
+- Make sure that the data type of the associated fields are consistent. It is prohibited to use implicit type conversion.
+- The or statements of different fields can be replaced with union.
+
+### Data Import
+
+- When a large amount of data needs to be stored in a table, it is recommended that COPY is used rather than INSERT. This can improve the data write speed.
+- Before data is imported, delete related indexes. After the import is complete, recreate indexes. This can improve the data import speed.
+
+### Transaction Operation
+
+- Make sure that the SQL logic in a transaction is simple, the granularity of each transaction is small, less resources are locked, lock and deadlock can be avoided, and transaction can be committed in a timely manner after being executed.
+- For DDL operations, especially multiple DDL operations, including CRAETE, DROP, and ALTER, do not explicitly start a transaction because the lock mode value is very high and deadlock easily occurs.
+- If the state of the master node is idle in transaction, related resources will be locked, thereby leading to lock, even deadlock. If the state of the slave node is idle in transaction, synchronization between the master and slave nodes will be suspended.
+
+### Others
+
+- For instances running in SSDs, it is recommended that the value of **random_page_cost** (default value: **4**) is set to a value ranging from 1.0 to 2.0. This can make the query planner preferably use the index to perform scanning.
+- In the scenario where EXPLAIN ANALYZE needs to be used to view the actual execution plan and time, if a write query is to be performed, it is strongly recommended that a transaction is started first and then rollback is performed.
+- For tables frequently updated and with the data size largely increased, table reorganization should be performed in appropriate time to lower the high water mark.
+
+## PostgreSQL Compatibility
+
+### Database Creation Specifications
+
+During MogDB database creation, the following PG compatibility mode is used:
+
+create database dbnam DBCOMPATIBILITY='PG' encoding=’utf8’;
+
+### Data Type
+
+#### Value Type
+
+During development and usage, MogDB supports only the smallint, integer, bigint, numeric[(p[,s])], serial, and bigserial value types.
+
+| Type             | PostgreSQL | MogDB     | Storage Length | Remarks                                                      |
+| :--------------- | :--------- | :-------- | :------------- | :----------------------------------------------------------- |
+| tinyint          | /          | Supported | 1 byte         | 0 to 255                                                     |
+| smallint         | Supported  | Supported | 2 bytes        | -32,768 to +32,767                                           |
+| integer          | Supported  | Supported | 4 bytes        | -2,147,483,648 to +2,147,483,647                             |
+| binary_integer   | /          | Supported | /              | integer alias                                                |
+| bigint           | Supported  | Supported | 8 bytes        | -9,223,372,036,854,775,808 to +9,223,372,036,854,775,807     |
+| decimal[(p[,s])] | Supported  | Supported | Variable byte  | A maximum of 131072 before the decimal point and 16383 after the decimal point |
+| numeric[(p[,s])] | Supported  | Supported | Variable byte  | A maximum of 131072 before the decimal point and 16383 after the decimal point |
+| number[(p[,s])]  | /          | Supported | /              | Numeric alias                                                |
+| real             | Supported  | Supported | 4 bytes        | Accurate to six decimal digits                               |
+| float4           | /          | Supported | 4 bytes        | Accurate to six decimal digits                               |
+| double precision | Supported  | Supported | 8 bytes        | Accurate to fifteen decimal digits                           |
+| binary_double    | /          | Supported | 8 bytes        | Double precision alias                                       |
+| float8           | /          | Supported | 8 bytes        | Accurate to fifteen decimal digits                           |
+| float[(p )]      | /          | Supported | 4 or 8 bytes   |                                                              |
+| dec[(p,[s])]     | /          | Supported | /              | A maximum of 131072 before the decimal point and 16383 after the decimal point |
+| integer[(p,[s])] | /          | Supported | /              | A maximum of 131072 before the decimal point and 16383 after the decimal point |
+| smallserial      | Supported  | Supported | 2 bytes        | 1 to 32,767                                                  |
+| serial           | Supported  | Supported | 4 bytes        | 1 to 2,147,483,647                                           |
+| bigserial        | Supported  | Supported | 8 bytes        | 1 to 9,223,372,036,854,775,807                               |
+| tinyint          | /          | Supported | 1 byte         | 0 to 255                                                     |
+
+#### Character Type
+
+During the development, MogDB supports only the char(n), varchar(n), and text character types.
+
+| Type         | PostgreSQL | MogDB     | Storage Length                                               | Remarks                                                      |
+| :----------- | :--------- | :-------- | :----------------------------------------------------------- | :----------------------------------------------------------- |
+| char(n)      | Supported  | Supported | A maximum of 1 GB in postgreSQL<br />A maximum of 10 MB in MogDB | In postgreSQL, *n* indicates the number of characters. <br />In MogDB, *n* indicates the number of bytes. <br />In the compatibility PG mode, *n* indicates the number of characters. |
+| nchar(n)     | /          | Supported | A maximum of 10 MB                                           | *n* indicates the number of bytes. <br />In the compatibility PG mode, *n* indicates the number of characters. |
+| varchar(n)   | Supported  | Supported | A maximum of 1 GB in postgreSQL<br />A maximum of 10 MB in MogDB | In postgreSQL, *n* indicates the number of characters. <br />In MogDB, *n* indicates the number of bytes. <br />In the compatibility PG mode, *n* indicates the number of characters. |
+| varchar2(n)  | /          | Supported | A maximum of 10 MB                                           | varchar(n) alias                                             |
+| nvarchar2(n) | /          | Supported | A maximum of 10 MB                                           | *n* indicates the number of characters.                      |
+| text         | Supported  | Supported | 1 GB - 1                                                     |                                                              |
+| clob         | /          | Supported | 1 GB - 1                                                     | text alias                                                   |
+
+#### Time Type
+
+During the development, MogDB supports only the timestamp[(p )][with time zone] and date time types.
+
+| Type                               | PostgreSQL | MogDB     | Storage Length | Remarks                                                      |
+| :--------------------------------- | :--------- | :-------- | :------------- | :----------------------------------------------------------- |
+| timestamp[(p )][without time zone] | Supported  | Supported | 8 bytes        | 4713 BC to 294276 AD                                         |
+| timestamp[(p )][with time zone]    | Supported  | Supported | 8 bytes        | 4713 BC to 294276 AD                                         |
+| date                               | Supported  | Supported | 4 bytes        | 4713 BC to 5874897 AD (The actual storage size is 8 bytes in MogDB) |
+| time[(p )][without time zone]      | Supported  | Supported | 8 bytes        | 00:00:00 to 24:00:00                                         |
+| time[(p )][with time zone]         | Supported  | Supported | 12 bytes       | 00:00:00+1459 to 24:00:00-1459                               |
+| interval[fields][(p )]             | Supported  | Supported | 16 bytes       | -178000000 to 178000000 years                                |
+| smalldatetime                      | /          | Supported | 8 bytes        | Date and time without timezone, accurating to the minute, 30s equaling one minute |
+| interval day(1) to second(p )      | /          | Supported | 16 bytes       |                                                              |
+| reltime                            | /          | Supported | 4 bytes        |                                                              |
+
+#### JSON Type
+
+MogDB supports only the JSON type.
+
+| Type  | PostgreSQL | MogDB     | Storage Length | Remarks |
+| :---- | :--------- | :-------- | :------------- | :------ |
+| json  | Supported  | Supported | /              |         |
+| jsonb | Supported  | /         | /              |         |
+
+### Keywords
+
+In the following table, **Reserved** indicates that keywords in a database are reserved and cannot be customized. **Non-reserved** or **N/A** indicates that keywords can be customized.
+
+| Keyword       | MogDB                                            | PostgreSQL                                       |
+| :------------ | :----------------------------------------------- | :----------------------------------------------- |
+| AUTHID        | Reserved                                         | N/A                                              |
+| BUCKETS       | Reserved                                         | N/A                                              |
+| COMPACT       | Reserved                                         | N/A                                              |
+| DATE          | Non-reserved (function or type is not supported) |                                                  |
+| DELTAMERGE    | Reserved                                         | N/A                                              |
+| EXCLUDED      | Reserved                                         | N/A                                              |
+| FENCED        | Reserved                                         | N/A                                              |
+| GROUPING      |                                                  | Non-reserved (function or type is not supported) |
+| HDFSDIRECTORY | Reserved                                         | N/A                                              |
+| IS            | Reserved                                         | Reserved (function or type is supported)         |
+| ISNULL        | Non-reserved                                     | Reserved (function or type is supported)         |
+| LATERAL       |                                                  | Reserved                                         |
+| LESS          | Reserved                                         | N/A                                              |
+| MAXVALUE      | Reserved                                         | Non-reserved                                     |
+| MINUS         | Reserved                                         | N/A                                              |
+| MODIFY        | Reserved                                         | N/A                                              |
+| NLSSORT       | Reserved                                         | N/A                                              |
+| NUMBER        | Non-reserved (function or type is not supported) |                                                  |
+| PERFORMANCE   | Reserved                                         | N/A                                              |
+| PROCEDURE     | Reserved                                         | Non-reserved                                     |
+| REJECT        | Reserved                                         | N/A                                              |
+| ROWNUM        | Reserved                                         | N/A                                              |
+| SYSDATE       | Reserved                                         | N/A                                              |
+| VERIFY        | Reserved                                         | N/A                                              |
+
+### Implicit Conversion Comparison Table
+
+| Input Type  | Target Type                                                | MogDB     |
+| :---------- | :--------------------------------------------------------- | :-------- |
+| bool        | int2, int4, int8                                           | Supported |
+| int2        | bool, text, varchar,interval                               | Supported |
+| int4        | bool, int2, text, varchar, interval                        | Supported |
+| int8        | bool, text, varchar                                        | Supported |
+| text        | int8, int4, int2, float4, float8, date, timestamp, nemeric | Supported |
+| float4      | int8, int4, int2, text, varchar                            | Supported |
+| float8      | int8, int4, int2, text, float4, varchar, interval, numeric | Supported |
+| date        | text, varchar                                              | Supported |
+| timestamp   | text, varchar                                              | Supported |
+| timestamptz | text                                                       | Supported |
+| numeric     | int8, int4, int2, text, varchar, interval                  | Supported |
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/1-development-based-on-jdbc-overview.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/1-development-based-on-jdbc-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..74f232a2f0df7b72d9bf6687e4b9f077ae9f84bd
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/1-development-based-on-jdbc-overview.md
@@ -0,0 +1,10 @@
+---
+title: Overview
+summary: Overview
+author: Guo Huan
+date: 2021-04-26
+---
+
+# Overview
+
+Java Database Connectivity (JDBC) is a Java API for running SQL statements. It provides unified access interfaces for different relational databases, based on which applications process data. MogDB supports JDBC 4.0 and requires JDK 1.8 for code compiling. It does not support JDBC-ODBC bridge.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/10-example-common-operations.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/10-example-common-operations.md
new file mode 100644
index 0000000000000000000000000000000000000000..2bd173e804ed6dc8e599f90781b7d7236004b8fd
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/10-example-common-operations.md
@@ -0,0 +1,243 @@
+---
+title: Example Common Operations
+summary: Example Common Operations
+author: Guo Huan
+date: 2021-04-26
+---
+
+# Example: Common Operations
+
+**Example 1:**
+
+The following illustrates how to develop applications based on MogDB JDBC interfaces.
+
+```java
+//DBtest.java
+// This example illustrates the main processes of JDBC-based development, covering database connection creation, table creation, and data insertion.
+
+import java.sql.Connection;
+import java.sql.DriverManager;
+import java.sql.PreparedStatement;
+import java.sql.SQLException;
+import java.sql.Statement;
+import java.sql.CallableStatement;
+
+public class DBTest {
+
+  // Create a database connection.
+  public static Connection GetConnection(String username, String passwd) {
+    String driver = "org.postgresql.Driver";
+    String sourceURL = "jdbc:postgresql://localhost:8000/postgres";
+    Connection conn = null;
+    try {
+      // Load the database driver.
+      Class.forName(driver).newInstance();
+    } catch (Exception e) {
+      e.printStackTrace();
+      return null;
+    }
+
+    try {
+      // Create a database connection.
+      conn = DriverManager.getConnection(sourceURL, username, passwd);
+      System.out.println("Connection succeed!");
+    } catch (Exception e) {
+      e.printStackTrace();
+      return null;
+    }
+
+    return conn;
+  };
+
+  // Run a common SQL statement to create table customer_t1.
+  public static void CreateTable(Connection conn) {
+    Statement stmt = null;
+    try {
+      stmt = conn.createStatement();
+
+      // Run a common SQL statement.
+      int rc = stmt
+          .executeUpdate("CREATE TABLE customer_t1(c_customer_sk INTEGER, c_customer_name VARCHAR(32));");
+
+      stmt.close();
+    } catch (SQLException e) {
+      if (stmt != null) {
+        try {
+          stmt.close();
+        } catch (SQLException e1) {
+          e1.printStackTrace();
+        }
+      }
+      e.printStackTrace();
+    }
+  }
+
+  // Run a prepared statement to insert data in batches.
+  public static void BatchInsertData(Connection conn) {
+    PreparedStatement pst = null;
+
+    try {
+      // Generate a prepared statement.
+      pst = conn.prepareStatement("INSERT INTO customer_t1 VALUES (?,?)");
+      for (int i = 0; i < 3; i++) {
+        // Add parameters.
+        pst.setInt(1, i);
+        pst.setString(2, "data " + i);
+        pst.addBatch();
+      }
+      // Perform batch processing.
+      pst.executeBatch();
+      pst.close();
+    } catch (SQLException e) {
+      if (pst != null) {
+        try {
+          pst.close();
+        } catch (SQLException e1) {
+        e1.printStackTrace();
+        }
+      }
+      e.printStackTrace();
+    }
+  }
+
+  // Run a prepared statement to update data.
+  public static void ExecPreparedSQL(Connection conn) {
+    PreparedStatement pstmt = null;
+    try {
+      pstmt = conn
+          .prepareStatement("UPDATE customer_t1 SET c_customer_name = ? WHERE c_customer_sk = 1");
+      pstmt.setString(1, "new Data");
+      int rowcount = pstmt.executeUpdate();
+      pstmt.close();
+    } catch (SQLException e) {
+      if (pstmt != null) {
+        try {
+          pstmt.close();
+        } catch (SQLException e1) {
+          e1.printStackTrace();
+        }
+      }
+      e.printStackTrace();
+    }
+  }
+
+
+// Run a stored procedure.
+  public static void ExecCallableSQL(Connection conn) {
+    CallableStatement cstmt = null;
+    try {
+
+      cstmt=conn.prepareCall("{? = CALL TESTPROC(?,?,?)}");
+      cstmt.setInt(2, 50);
+      cstmt.setInt(1, 20);
+      cstmt.setInt(3, 90);
+      cstmt.registerOutParameter(4, Types.INTEGER);  // Register an OUT parameter of the integer type.
+      cstmt.execute();
+      int out = cstmt.getInt(4);  // Obtain the OUT parameter.
+      System.out.println("The CallableStatment TESTPROC returns:"+out);
+      cstmt.close();
+    } catch (SQLException e) {
+      if (cstmt != null) {
+        try {
+          cstmt.close();
+        } catch (SQLException e1) {
+          e1.printStackTrace();
+        }
+      }
+      e.printStackTrace();
+    }
+  }
+
+
+  /**
+   *Main process. Call static methods one by one.
+   * @param args
+  */
+  public static void main(String[] args) {
+    // Create a database connection.
+    Connection conn = GetConnection("tester", "Password1234");
+
+    // Create a table.
+    CreateTable(conn);
+
+    // Insert data in batches.
+    BatchInsertData(conn);
+
+    // Run a prepared statement to update data.
+    ExecPreparedSQL(conn);
+
+    // Run a stored procedure.
+    ExecCallableSQL(conn);
+
+    // Close the connection to the database.
+    try {
+      conn.close();
+    } catch (SQLException e) {
+      e.printStackTrace();
+    }
+
+  }
+
+}
+```
+
+**Example 2 High Client Memory Usage**
+
+In this example, **setFetchSize** adjusts the memory usage of the client by using the database cursor to obtain server data in batches. It may increase network interaction and deteriorate some performance.
+
+The cursor is valid within a transaction. Therefore, disable automatic commit and then manually commit the code.
+
+```java
+// Disable automatic commit.
+conn.setAutoCommit(false);
+Statement st = conn.createStatement();
+
+// Open the cursor and obtain 50 lines of data each time.
+st.setFetchSize(50);
+ResultSet rs = st.executeQuery("SELECT * FROM mytable");
+conn.commit();
+while (rs.next())
+{
+    System.out.print("a row was returned.");
+}
+rs.close();
+
+// Disable the server cursor.
+st.setFetchSize(0);
+rs = st.executeQuery("SELECT * FROM mytable");
+conn.commit();
+while (rs.next())
+{
+    System.out.print("many rows were returned.");
+}
+rs.close();
+
+// Close the statement.
+st.close();
+conn.close();
+```
+
+Run the following command to enable automatic commit:
+
+```
+conn.setAutoCommit(true);
+```
+
+**Example 3 Common Data Type**
+
+```
+//Use the bit type as an example. Note that the value of the bit type of data ranges from 0 to 1.
+Statement st = conn.createStatement();
+String sqlstr = "create or replace function fun_1()\n" +
+        "returns bit AS $$\n" +
+        "select col_bit from t_bit limit 1;\n" +
+        "$$\n" +
+        "LANGUAGE SQL;";
+st.execute(sqlstr);
+CallableStatement c = conn.prepareCall("{ ? = call fun_1() }");
+//Register the output type and string type.
+c.registerOutParameter(1, Types.BIT);
+c.execute();
+//Use the Boolean type to obtain the result.
+System.out.println(c.getBoolean(1));
+```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/11-example-retrying-sql-queries-for-applications.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/11-example-retrying-sql-queries-for-applications.md
new file mode 100644
index 0000000000000000000000000000000000000000..7593d4a940ef353e065846a9eda4dd1ed4a8a2fe
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/11-example-retrying-sql-queries-for-applications.md
@@ -0,0 +1,205 @@
+---
+title: Example Retrying SQL Queries for Applications
+summary: Example Retrying SQL Queries for Applications
+author: Guo Huan
+date: 2021-04-26
+---
+
+# Example Retrying SQL Queries for Applications
+
+If the primary database node is faulty and cannot be restored within 10s, the standby database node automatically switches to the active state to ensure the normal running of MogDB. During the switchover, jobs that are running will fail and those start running after the switchover are not affected. To prevent upper-layer services from being affected by the failover, refer to the following example to construct an SQL retry mechanism at the service layer.
+
+```java
+import java.sql.Connection;
+import java.sql.DriverManager;
+import java.sql.PreparedStatement;
+import java.sql.ResultSet;
+import java.sql.SQLException;
+import java.sql.Statement;
+
+class ExitHandler extends Thread {
+    private Statement cancel_stmt = null;
+
+    public ExitHandler(Statement stmt) {
+        super("Exit Handler");
+        this.cancel_stmt = stmt;
+    }
+    public void run() {
+        System.out.println("exit handle");
+        try {
+            this.cancel_stmt.cancel();
+        } catch (SQLException e) {
+            System.out.println("cancel query failed.");
+            e.printStackTrace();
+        }
+    }
+}
+
+public class SQLRetry {
+   // Create a database connection.
+   public static Connection GetConnection(String username, String passwd) {
+     String driver = "org.postgresql.Driver";
+     String sourceURL = "jdbc:postgresql://10.131.72.136:8000/postgres";
+     Connection conn = null;
+     try {
+       // Load the database driver.
+       Class.forName(driver).newInstance();
+     } catch (Exception e) {
+       e.printStackTrace();
+       return null;
+     }
+
+     try {
+       // Create a database connection.
+       conn = DriverManager.getConnection(sourceURL, username, passwd);
+       System.out.println("Connection succeed!");
+     } catch (Exception e) {
+       e.printStackTrace();
+       return null;
+     }
+
+     return conn;
+}
+
+   // Run a common SQL statement. Create the jdbc_test1 table.
+   public static void CreateTable(Connection conn) {
+     Statement stmt = null;
+     try {
+       stmt = conn.createStatement();
+
+
+       Runtime.getRuntime().addShutdownHook(new ExitHandler(stmt));
+
+       // Run a common SQL statement.
+       int rc2 = stmt
+          .executeUpdate("DROP TABLE if exists jdbc_test1;");
+
+       int rc1 = stmt
+          .executeUpdate("CREATE TABLE jdbc_test1(col1 INTEGER, col2 VARCHAR(10));");
+
+       stmt.close();
+     } catch (SQLException e) {
+       if (stmt != null) {
+         try {
+           stmt.close();
+         } catch (SQLException e1) {
+           e1.printStackTrace();
+         }
+       }
+       e.printStackTrace();
+     }
+   }
+
+   // Run a prepared statement to insert data in batches.
+   public static void BatchInsertData(Connection conn) {
+     PreparedStatement pst = null;
+
+     try {
+      // Generate a prepared statement.
+       pst = conn.prepareStatement("INSERT INTO jdbc_test1 VALUES (?,?)");
+       for (int i = 0; i < 100; i++) {
+        // Add parameters.
+         pst.setInt(1, i);
+         pst.setString(2, "data " + i);
+         pst.addBatch();
+       }
+      // Perform batch processing.
+       pst.executeBatch();
+       pst.close();
+     } catch (SQLException e) {
+       if (pst != null) {
+         try {
+           pst.close();
+         } catch (SQLException e1) {
+         e1.printStackTrace();
+         }
+       }
+       e.printStackTrace();
+     }
+   }
+
+   // Run a prepared statement to update data.
+   private static boolean QueryRedo(Connection conn){
+     PreparedStatement pstmt = null;
+     boolean retValue = false;
+     try {
+       pstmt = conn
+           .prepareStatement("SELECT col1 FROM jdbc_test1 WHERE col2 = ?");
+
+           pstmt.setString(1, "data 10");
+           ResultSet rs = pstmt.executeQuery();
+
+           while (rs.next()) {
+               System.out.println("col1 = " + rs.getString("col1"));
+           }
+           rs.close();
+
+       pstmt.close();
+        retValue = true;
+      } catch (SQLException e) {
+       System.out.println("catch...... retValue " + retValue);
+       if (pstmt != null) {
+         try {
+          pstmt.close();
+        } catch (SQLException e1) {
+          e1.printStackTrace();
+         }
+       }
+       e.printStackTrace();
+     }
+
+      System.out.println("finesh......");
+     return retValue;
+   }
+
+   // Configure the number of retry attempts for the retry of a query statement upon a failure.
+   public static void ExecPreparedSQL(Connection conn) throws InterruptedException {
+         int maxRetryTime = 50;
+         int time = 0;
+         String result = null;
+         do {
+             time++;
+             try {
+  System.out.println("time:" + time);
+  boolean ret = QueryRedo(conn);
+  if(ret == false){
+   System.out.println("retry, time:" + time);
+   Thread.sleep(10000);
+   QueryRedo(conn);
+  }
+             } catch (Exception e) {
+                 e.printStackTrace();
+             }
+         } while (null == result && time < maxRetryTime);
+
+   }
+
+   /**
+    *Main process. Call static methods one by one.
+    * @param args
+    * @throws InterruptedException
+    */
+   public static void main(String[] args) throws InterruptedException {
+     // Create a database connection.
+     Connection conn = GetConnection("testuser", "test@123");
+
+     // Create a table.
+     CreateTable(conn);
+
+     // Insert data in batches.
+     BatchInsertData(conn);
+
+     // Run a prepared statement to update data.
+     ExecPreparedSQL(conn);
+
+     // Close the connection to the database.
+     try {
+       conn.close();
+     } catch (SQLException e) {
+       e.printStackTrace();
+     }
+
+   }
+
+ }
+```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/12-example-importing-and-exporting-data-through-local-files.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/12-example-importing-and-exporting-data-through-local-files.md
new file mode 100644
index 0000000000000000000000000000000000000000..ce8625c3bb24c768f297e382da0f5de10d0b9261
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/12-example-importing-and-exporting-data-through-local-files.md
@@ -0,0 +1,119 @@
+---
+title: Example Importing and Exporting Data Through Local Files
+summary: Example Importing and Exporting Data Through Local Files
+author: Guo Huan
+date: 2021-04-26
+---
+
+# Example Importing and Exporting Data Through Local Files
+
+When Java is used for secondary development based on MogDB, you can use the CopyManager interface to export data from the database to a local file or import a local file to the database by streaming. The file can be in CSV or TEXT format.
+
+The sample program is as follows. Load the MogDB JDBC driver before running it.
+
+```java
+import java.sql.Connection;
+import java.sql.DriverManager;
+import java.io.IOException;
+import java.io.FileInputStream;
+import java.io.FileOutputStream;
+import java.sql.SQLException;
+import org.postgresql.copy.CopyManager;
+import org.postgresql.core.BaseConnection;
+
+public class Copy{
+
+     public static void main(String[] args)
+     {
+      String urls = new String("jdbc:postgresql://10.180.155.74:8000/postgres"); // Database URL
+      String username = new String("jack");            // Username
+      String password = new String("Gauss@123");             // Password
+      String tablename = new String("migration_table"); // Table information
+      String tablename1 = new String("migration_table_1"); // Table information
+      String driver = "org.postgresql.Driver";
+      Connection conn = null;
+
+      try {
+            Class.forName(driver);
+            conn = DriverManager.getConnection(urls, username, password);
+          } catch (ClassNotFoundException e) {
+               e.printStackTrace(System.out);
+          } catch (SQLException e) {
+               e.printStackTrace(System.out);
+          }
+
+      // Export the query result of SELECT * FROM migration_table to the local file d:/data.txt.
+      try {
+     copyToFile(conn, "d:/data.txt", "(SELECT * FROM migration_table)");
+   } catch (SQLException e) {
+  k
+  e.printStackTrace();
+   } catch (IOException e) {
+
+  e.printStackTrace();
+   }
+      // Import data from the d:/data.txt file to the migration_table_1 table.
+      try {
+      copyFromFile(conn, "d:/data.txt", tablename1);
+   } catch (SQLException e) {
+         e.printStackTrace();
+ } catch (IOException e) {
+
+  e.printStackTrace();
+ }
+
+      // Export the data from the migration_table_1 table to the d:/data1.txt file.
+      try {
+      copyToFile(conn, "d:/data1.txt", tablename1);
+   } catch (SQLException e) {
+
+  e.printStackTrace();
+   } catch (IOException e) {
+
+
+  e.printStackTrace();
+ }
+     }
+  // Use copyIn to import data from a file to the database.
+  public static void copyFromFile(Connection connection, String filePath, String tableName)
+         throws SQLException, IOException {
+
+     FileInputStream fileInputStream = null;
+
+     try {
+         CopyManager copyManager = new CopyManager((BaseConnection)connection);
+         fileInputStream = new FileInputStream(filePath);
+         copyManager.copyIn("COPY " + tableName + " FROM STDIN", fileInputStream);
+     } finally {
+         if (fileInputStream != null) {
+             try {
+                 fileInputStream.close();
+             } catch (IOException e) {
+                 e.printStackTrace();
+             }
+         }
+     }
+ }
+
+  // Use copyOut to export data from the database to a file.
+  public static void copyToFile(Connection connection, String filePath, String tableOrQuery)
+          throws SQLException, IOException {
+
+      FileOutputStream fileOutputStream = null;
+
+      try {
+          CopyManager copyManager = new CopyManager((BaseConnection)connection);
+          fileOutputStream = new FileOutputStream(filePath);
+          copyManager.copyOut("COPY " + tableOrQuery + " TO STDOUT", fileOutputStream);
+      } finally {
+          if (fileOutputStream != null) {
+              try {
+                  fileOutputStream.close();
+              } catch (IOException e) {
+                  e.printStackTrace();
+              }
+          }
+      }
+  }
+}
+```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/13-example-2-migrating-data-from-a-my-database-to-mogdb.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/13-example-2-migrating-data-from-a-my-database-to-mogdb.md
new file mode 100644
index 0000000000000000000000000000000000000000..c17f3f6450469f96b9f741bed7ab90ca5f8d0466
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/13-example-2-migrating-data-from-a-my-database-to-mogdb.md
@@ -0,0 +1,97 @@
+---
+title: Example 2 Migrating Data from a MY Database to MogDB
+summary: Example 2 Migrating Data from a MY Database to MogDB
+author: Guo Huan
+date: 2021-04-26
+---
+
+# Example 2 Migrating Data from a MY Database to MogDB
+
+The following example shows how to use CopyManager to migrate data from MY to MogDB.
+
+```java
+import java.io.StringReader;
+import java.sql.Connection;
+import java.sql.DriverManager;
+import java.sql.ResultSet;
+import java.sql.SQLException;
+import java.sql.Statement;
+
+import org.postgresql.copy.CopyManager;
+import org.postgresql.core.BaseConnection;
+
+public class Migration{
+
+    public static void main(String[] args) {
+        String url = new String("jdbc:postgresql://10.180.155.74:8000/postgres"); // Database URL
+        String user = new String("jack");            // MogDB username
+        String pass = new String("Gauss@123");             // MogDB password
+        String tablename = new String("migration_table"); // Table information
+        String delimiter = new String("|");              // Delimiter
+        String encoding = new String("UTF8");            // Character set
+        String driver = "org.postgresql.Driver";
+        StringBuffer buffer = new StringBuffer();       // Buffer to store formatted data
+
+        try {
+            // Obtain the query result set of the source database.
+            ResultSet rs = getDataSet();
+
+            // Traverse the result set and obtain records row by row.
+            // The values of columns in each record are separated by the specified delimiter and end with a linefeed, forming strings.
+            // Add the strings to the buffer.
+            while (rs.next()) {
+                buffer.append(rs.getString(1) + delimiter
+                        + rs.getString(2) + delimiter
+                        + rs.getString(3) + delimiter
+                        + rs.getString(4)
+                        + "\n");
+            }
+            rs.close();
+
+            try {
+                // Connect to the target database.
+                Class.forName(driver);
+                Connection conn = DriverManager.getConnection(url, user, pass);
+                BaseConnection baseConn = (BaseConnection) conn;
+                baseConn.setAutoCommit(false);
+
+                // Initialize the table.
+                String sql = "Copy " + tablename + " from STDIN DELIMITER " + "'" + delimiter + "'" + " ENCODING " + "'" + encoding + "'";
+
+                // Commit data in the buffer.
+                CopyManager cp = new CopyManager(baseConn);
+                StringReader reader = new StringReader(buffer.toString());
+                cp.copyIn(sql, reader);
+                baseConn.commit();
+                reader.close();
+                baseConn.close();
+            } catch (ClassNotFoundException e) {
+                e.printStackTrace(System.out);
+            } catch (SQLException e) {
+                e.printStackTrace(System.out);
+            }
+
+        } catch (Exception e) {
+            e.printStackTrace();
+        }
+    }
+
+    //********************************
+    // Return the query result set from the source database.
+    //*********************************
+    private static ResultSet getDataSet() {
+        ResultSet rs = null;
+        try {
+            Class.forName("com.MY.jdbc.Driver").newInstance();
+            Connection conn = DriverManager.getConnection("jdbc:MY://10.119.179.227:3306/jack?useSSL=false&allowPublicKeyRetrieval=true", "jack", "Gauss@123");
+            Statement stmt = conn.createStatement();
+            rs = stmt.executeQuery("select * from migration_table");
+        } catch (SQLException e) {
+            e.printStackTrace();
+        } catch (Exception e) {
+            e.printStackTrace();
+        }
+        return rs;
+    }
+}
+```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/14-example-logic-replication-code.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/14-example-logic-replication-code.md
new file mode 100644
index 0000000000000000000000000000000000000000..6d1d422f169b6ac1bbc7ff9debe9972514a29e15
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/14-example-logic-replication-code.md
@@ -0,0 +1,111 @@
+---
+title: Example Logic Replication Code
+summary: Example Logic Replication Code
+author: Guo Huan
+date: 2021-04-26
+---
+
+# Example Logic Replication Code
+
+The following example demonstrates how to use the logical replication function through the JDBC interface.
+
+```java
+//Logical replication function example: file name, LogicalReplicationDemo.java
+//Prerequisite: Add the IP address of the JDBC user machine to the database whitelist. Add the following content to pg_hba.conf:
+//Assume that the IP address of the JDBC user machine is 10.10.10.10.
+//host    all             all             10.10.10.10/32        sha256
+//host    replication     all             10.10.10.10/32        sha256
+
+import org.postgresql.PGProperty;
+import org.postgresql.jdbc.PgConnection;
+import org.postgresql.replication.LogSequenceNumber;
+import org.postgresql.replication.PGReplicationStream;
+
+import java.nio.ByteBuffer;
+import java.sql.DriverManager;
+import java.util.Properties;
+import java.util.concurrent.TimeUnit;
+
+public class LogicalReplicationDemo {
+    public static void main(String[] args) {
+        String driver = "org.postgresql.Driver";
+    //Set the IP address and port number of the database.
+        String sourceURL = "jdbc:postgresql://$ip:$port/postgres";
+        PgConnection conn = null;
+    //The default name of the logical replication slot is replication_slot.
+    //Test mode: Create a logical replication slot.
+        int TEST_MODE_CREATE_SLOT = 1;
+    //Test mode: Enable logical replication (The prerequisite is that the logical replication slot already exists).
+        int TEST_MODE_START_REPL = 2;
+    //Test mode: Delete a logical replication slot.
+        int TEST_MODE_DROP_SLOT = 3;
+    //Enable different test modes.
+        int testMode = TEST_MODE_START_REPL;
+
+        try {
+            Class.forName(driver);
+        } catch (Exception e) {
+            e.printStackTrace();
+            return;
+        }
+
+        try {
+            Properties properties = new Properties();
+            PGProperty.USER.set(properties, "user");
+            PGProperty.PASSWORD.set(properties, "passwd");
+    //For logical replication, the following three attributes are mandatory.
+            PGProperty.ASSUME_MIN_SERVER_VERSION.set(properties, "9.4");
+            PGProperty.REPLICATION.set(properties, "database");
+            PGProperty.PREFER_QUERY_MODE.set(properties, "simple");
+            conn = (PgConnection) DriverManager.getConnection(sourceURL, properties);
+            System.out.println("connection success!");
+
+            if(testMode == TEST_MODE_CREATE_SLOT){
+                conn.getReplicationAPI()
+                        .createReplicationSlot()
+                        .logical()
+                        .withSlotName("replication_slot")
+                        .withOutputPlugin("test_decoding")
+                        .make();
+            }else if(testMode == TEST_MODE_START_REPL) {
+                //Create a replication slot before enabling this mode.
+                LogSequenceNumber waitLSN = LogSequenceNumber.valueOf("6F/E3C53568");
+                PGReplicationStream stream = conn
+                        .getReplicationAPI()
+                        .replicationStream()
+                        .logical()
+                        .withSlotName("replication_slot")
+                        .withSlotOption("include-xids", false)
+                        .withSlotOption("skip-empty-xacts", true)
+                        .withStartPosition(waitLSN)
+                        .start();
+                while (true) {
+                    ByteBuffer byteBuffer = stream.readPending();
+
+                    if (byteBuffer == null) {
+                        TimeUnit.MILLISECONDS.sleep(10L);
+                        continue;
+                    }
+
+                    int offset = byteBuffer.arrayOffset();
+                    byte[] source = byteBuffer.array();
+                    int length = source.length - offset;
+                    System.out.println(new String(source, offset, length));
+
+                    //If the LSN needs to be flushed, call the following APIs based on the service requirements:
+                    //LogSequenceNumber lastRecv = stream.getLastReceiveLSN();
+                    //stream.setFlushedLSN(lastRecv);
+                    //stream.forceUpdateStatus();
+
+                }
+            }else if(testMode == TEST_MODE_DROP_SLOT){
+                conn.getReplicationAPI()
+                        .dropReplicationSlot("replication_slot");
+            }
+        } catch (Exception e) {
+            e.printStackTrace();
+            return;
+        }
+    }
+}
+```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/14.1-example-parameters-for-connecting-to-the-database-in-different-scenarios.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/14.1-example-parameters-for-connecting-to-the-database-in-different-scenarios.md
new file mode 100644
index 0000000000000000000000000000000000000000..c953f095aed64b393e85994611d3b23b5a23b098
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/14.1-example-parameters-for-connecting-to-the-database-in-different-scenarios.md
@@ -0,0 +1,60 @@
+---
+title: Parameters for Connecting to the Database in Different Scenarios
+summary: Parameters for Connecting to the Database in Different Scenarios
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# Example: Parameters for Connecting to the Database in Different Scenarios
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** In the following example, **host:port** represents a node, where **host** indicates the name or IP address of the server where the database resides, and **port** indicates the port number of the server where the database resides.
+
+## DR
+
+A customer has two database instances. Database instance A is the production database instance, and database instance B is the DR database instance. When the customer performs a DR switchover, database instance A is demoted to the DR database instance, and database instance B is promoted the production database instance. In this case, to avoid application restart or re-release caused by modifications on the configuration file, the customer can write database instances A and B to the connection string when initializing the configuration file. If the primary database instance cannot be connected, the driver attempts to connect to the DR database instance. For example, database instance A consists of *node1*, *node2*, and *node3*, and database instance B consists of *node4*, *node5*, and *node6*.
+
+The URL can be configured as follows:
+
+```
+jdbc:postgresql://node1,node2,node3,node4,node5,node6/database?priorityServers=3
+```
+
+## Load Balancing
+
+A customer has a centralized database instance that consists of one primary node and two standby nodes, that is, *node1*, *node2*, and *node3*. *node1* is the primary node, and *node2* and *node3* are the standby nodes.
+
+If the customer wants to evenly distribute the connections established on the same application to three nodes, the URL can be configured as follows:
+
+```
+jdbc:postgresql://node1,node2,node3/database?loadBalanceHosts=true
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **CAUTION:** When **loadBalanceHosts** is used, if the connection is established on the standby DN, write operations cannot be performed. If read and write operations are required, do not set this parameter.
+
+## Log Diagnosis
+
+If a customer encounters slow data import or some errors that are difficult to analyze, the trace log function can be enabled for diagnosis. The URL can be configured as follows:
+
+```
+jdbc:postgresql://node1/database?loggerLevel=trace&loggerFile=jdbc.log
+```
+
+## High Performance
+
+A customer may execute the same SQL statement for multiple times with different input parameters. To improve the execution efficiency, the **prepareThreshold** parameter can be enabled to avoid repeatedly generating execution plans. The URL can be configured as follows:
+
+```
+jdbc:postgresql://node1/database?prepareThreshold=5
+```
+
+A customer queries 10 million data records at a time. To prevent memory overflow caused by simultaneous return of the data records, the **defaultRowFetchSize** parameter can be used. The URL can be configured as follows:
+
+```
+jdbc:postgresql://node1/database?defaultRowFetchSize=50000
+```
+
+A customer needs to insert 10 million data records in batches. To improve efficiency, the **batchMode** parameter can be used. The URL can be configured as follows:
+
+```
+jdbc:postgresql://node1/database?batchMode=true
+```
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/1-java-sql-Connection.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/1-java-sql-Connection.md
new file mode 100644
index 0000000000000000000000000000000000000000..0598e5efa995bda8f5c6978c869fcc29a70a63f8
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/1-java-sql-Connection.md
@@ -0,0 +1,67 @@
+---
+title: java.sql.Connection
+summary: java.sql.Connection
+author: Guo Huan
+date: 2021-05-17
+---
+
+# java.sql.Connection
+
+This section describes **java.sql.Connection**, the interface for connecting to a database.
+
+**Table 1** Support status for java.sql.Connection
+
+| Method Name                                                  | Return Type                      | JDBC 4 Is Supported Or Not |
+| :----------------------------------------------------------- | :------------------------------- | :------------------------- |
+| abort(Executor executor)                                     | void                             | Yes                        |
+| clearWarnings()                                              | void                             | Yes                        |
+| close()                                                      | void                             | Yes                        |
+| commit()                                                     | void                             | Yes                        |
+| createArrayOf(String typeName, Object[] elements)            | Array                            | Yes                        |
+| createBlob()                                                 | Blob                             | Yes                        |
+| createClob()                                                 | Clob                             | Yes                        |
+| createSQLXML()                                               | SQLXML                           | Yes                        |
+| createStatement()                                            | Statement                        | Yes                        |
+| createStatement(int resultSetType, int resultSetConcurrency) | Statement                        | Yes                        |
+| createStatement(int resultSetType, int resultSetConcurrency, int resultSetHoldability) | Statement                        | Yes                        |
+| getAutoCommit()                                              | Boolean                          | Yes                        |
+| getCatalog()                                                 | String                           | Yes                        |
+| getClientInfo()                                              | Properties                       | Yes                        |
+| getClientInfo(String name)                                   | String                           | Yes                        |
+| getHoldability()                                             | int                              | Yes                        |
+| getMetaData()                                                | DatabaseMetaData                 | Yes                        |
+| getNetworkTimeout()                                          | int                              | Yes                        |
+| getSchema()                                                  | String                           | Yes                        |
+| getTransactionIsolation()                                    | int                              | Yes                        |
+| getTypeMap()                                                 | Map&lt;String,Class&lt;?&gt;&gt; | Yes                        |
+| getWarnings()                                                | SQLWarning                       | Yes                        |
+| isClosed()                                                   | Boolean                          | Yes                        |
+| isReadOnly()                                                 | Boolean                          | Yes                        |
+| isValid(int timeout)                                         | boolean                          | Yes                        |
+| nativeSQL(String sql)                                        | String                           | Yes                        |
+| prepareCall(String sql)                                      | CallableStatement                | Yes                        |
+| prepareCall(String sql, int resultSetType, int resultSetConcurrency) | CallableStatement                | Yes                        |
+| prepareCall(String sql, int resultSetType, int resultSetConcurrency, int resultSetHoldability) | CallableStatement                | Yes                        |
+| prepareStatement(String sql)                                 | PreparedStatement                | Yes                        |
+| prepareStatement(String sql, int autoGeneratedKeys)          | PreparedStatement                | Yes                        |
+| prepareStatement(String sql, int[] columnIndexes)            | PreparedStatement                | Yes                        |
+| prepareStatement(String sql, int resultSetType, int resultSetConcurrency) | PreparedStatement                | Yes                        |
+| prepareStatement(String sql, int resultSetType, int resultSetConcurrency, int resultSetHoldability) | PreparedStatement                | Yes                        |
+| prepareStatement(String sql, String[] columnNames)           | PreparedStatement                | Yes                        |
+| releaseSavepoint(Savepoint savepoint)                        | void                             | Yes                        |
+| rollback()                                                   | void                             | Yes                        |
+| rollback(Savepoint savepoint)                                | void                             | Yes                        |
+| setAutoCommit(boolean autoCommit)                            | void                             | Yes                        |
+| setClientInfo(Properties properties)                         | void                             | Yes                        |
+| setClientInfo(String name,String value)                      | void                             | Yes                        |
+| setHoldability(int holdability)                              | void                             | Yes                        |
+| setNetworkTimeout(Executor executor, int milliseconds)       | void                             | Yes                        |
+| setReadOnly(boolean readOnly)                                | void                             | Yes                        |
+| setSavepoint()                                               | Savepoint                        | Yes                        |
+| setSavepoint(String name)                                    | Savepoint                        | Yes                        |
+| setSchema(String schema)                                     | void                             | Yes                        |
+| setTransactionIsolation(int level)                           | void                             | Yes                        |
+| setTypeMap(Map&lt;String,Class&lt;?&gt;&gt; map)             | void                             | Yes                        |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> The AutoCommit mode is used by default within the interface. If you disable it by running **setAutoCommit(false)**, all the statements executed later will be packaged in explicit transactions, and you cannot execute statements that cannot be executed within transactions.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/10-javax-sql-DataSource.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/10-javax-sql-DataSource.md
new file mode 100644
index 0000000000000000000000000000000000000000..0aeccd036e7e7b833f90f25bc62ea06c3abed656
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/10-javax-sql-DataSource.md
@@ -0,0 +1,21 @@
+---
+title: javax.sql.DataSource
+summary: javax.sql.DataSource
+author: Guo Huan
+date: 2021-05-17
+---
+
+# javax.sql.DataSource
+
+This section describes **javax.sql.DataSource**, the interface for data sources.
+
+**Table 1** Support status for javax.sql.DataSource
+
+| Method Name                                    | Return Type | Support JDBC 4 |
+| :--------------------------------------------- | :---------- | :------------- |
+| getConneciton()                                | Connection  | Yes            |
+| getConnection(String username,String password) | Connection  | Yes            |
+| getLoginTimeout()                              | int         | Yes            |
+| getLogWriter()                                 | PrintWriter | Yes            |
+| setLoginTimeout(int seconds)                   | void        | Yes            |
+| setLogWriter(PrintWriter out)                  | void        | Yes            |
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/11-javax-sql-PooledConnection.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/11-javax-sql-PooledConnection.md
new file mode 100644
index 0000000000000000000000000000000000000000..b1f4004dc0fcf426efcfc75bf4d586cac2d2ebb3
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/11-javax-sql-PooledConnection.md
@@ -0,0 +1,19 @@
+---
+title: javax.sql.PooledConnection
+summary: javax.sql.PooledConnection
+author: Guo Huan
+date: 2021-05-17
+---
+
+# javax.sql.PooledConnection
+
+This section describes **javax.sql.PooledConnection**, the connection interface created by a connection pool.
+
+**Table 1** Support status for javax.sql.PooledConnection
+
+| Method Name                                                  | Return Type | JDBC 4 Is Supported Or Not |
+| :----------------------------------------------------------- | :---------- | :------------------------- |
+| addConnectionEventListener (ConnectionEventListener listener) | void        | Yes                        |
+| close()                                                      | void        | Yes                        |
+| getConnection()                                              | Connection  | Yes                        |
+| removeConnectionEventListener (ConnectionEventListener listener) | void        | Yes                        |
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/12-javax-naming-Context.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/12-javax-naming-Context.md
new file mode 100644
index 0000000000000000000000000000000000000000..26da1f5a0b5d258855b70ea3967d650844c19c6c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/12-javax-naming-Context.md
@@ -0,0 +1,25 @@
+---
+title: javax.naming.Context
+summary: javax.naming.Context
+author: Guo Huan
+date: 2021-05-17
+---
+
+# javax.naming.Context
+
+This section describes **javax.naming.Context**, the context interface for connection configuration.
+
+**Table 1** Support status for javax.naming.Context
+
+| Method Name                            | Return Type | Support JDBC 4 |
+| :------------------------------------- | :---------- | :------------- |
+| bind(Name name, Object obj)            | void        | Yes            |
+| bind(String name, Object obj)          | void        | Yes            |
+| lookup(Name name)                      | Object      | Yes            |
+| lookup(String name)                    | Object      | Yes            |
+| rebind(Name name, Object obj)          | void        | Yes            |
+| rebind(String name, Object obj)        | void        | Yes            |
+| rename(Name oldName, Name newName)     | void        | Yes            |
+| rename(String oldName, String newName) | void        | Yes            |
+| unbind(Name name)                      | void        | Yes            |
+| unbind(String name)                    | void        | Yes            |
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/13-javax-naming-spi-InitialContextFactory.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/13-javax-naming-spi-InitialContextFactory.md
new file mode 100644
index 0000000000000000000000000000000000000000..ef15dfccd645fedeb9a5175528da0703ebf2a40a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/13-javax-naming-spi-InitialContextFactory.md
@@ -0,0 +1,16 @@
+---
+title: javax.naming.spi.InitialContextFactory
+summary: javax.naming.spi.InitialContextFactory
+author: Guo Huan
+date: 2021-05-17
+---
+
+# javax.naming.spi.InitialContextFactory
+
+This section describes **javax.naming.spi.InitialContextFactory**, the initial context factory interface.
+
+**Table 1** Support status for javax.naming.spi.InitialContextFactory
+
+| Method Name                                         | Return Type | Support JDBC 4 |
+| :-------------------------------------------------- | :---------- | :------------- |
+| getInitialContext(Hashtable&lt;?,?&gt; environment) | Context     | Yes            |
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/14-CopyManager.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/14-CopyManager.md
new file mode 100644
index 0000000000000000000000000000000000000000..258d60683e2651f8cbbb5a8b13fbb47feb924e95
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/14-CopyManager.md
@@ -0,0 +1,40 @@
+---
+title: CopyManager
+summary: CopyManager
+author: Guo Huan
+date: 2021-05-17
+---
+
+# CopyManager
+
+CopyManager is an API class provided by the JDBC driver in MogDB. It is used to import data to MogDB in batches.
+
+## Inheritance Relationship of CopyManager
+
+The CopyManager class is in the **org.postgresql.copy** package and inherits the java.lang.Object class. The declaration of the class is as follows:
+
+```java
+public class CopyManager
+extends Object
+```
+
+## Construction Method
+
+public CopyManager(BaseConnection connection)
+
+throws SQLException
+
+## Common Methods
+
+**Table 1** Common methods of CopyManager
+
+| Return Value             | Method               | Description          | throws               |
+| :----------------------- | :------------------- | :------------------- | :------------------- |
+| CopyIn       | copyIn(String sql)                                   | -                                                            | SQLException             |
+| long         | copyIn(String sql, InputStream from)                 | Uses **COPY FROM STDIN** to quickly load data to tables in the database from InputStream. | SQLException,IOException |
+| long         | copyIn(String sql, InputStream from, int bufferSize) | Uses **COPY FROM STDIN** to quickly load data to tables in the database from InputStream. | SQLException,IOException |
+| long         | copyIn(String sql, Reader from)                      | Uses **COPY FROM STDIN** to quickly load data to tables in the database from Reader. | SQLException,IOException |
+| long         | copyIn(String sql, Reader from, int bufferSize)      | Uses **COPY FROM STDIN** to quickly load data to tables in the database from Reader. | SQLException,IOException |
+| CopyOut      | copyOut(String sql)                                  | -                                                            | SQLException             |
+| long         | copyOut(String sql, OutputStream to)                 | Sends the result set of **COPY TO STDOUT** from the database to the OutputStream class. | SQLException,IOException |
+| long         | copyOut(String sql, Writer to)                       | Sends the result set of **COPY TO STDOUT** from the database to the Writer class. | SQLException,IOException |
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/2-java-sql-CallableStatement.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/2-java-sql-CallableStatement.md
new file mode 100644
index 0000000000000000000000000000000000000000..dc493d97a52c8b9ae60e13d2c77609c5e530a108
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/2-java-sql-CallableStatement.md
@@ -0,0 +1,46 @@
+---
+title: java.sql.CallableStatement
+summary: java.sql.CallableStatement
+author: Guo Huan
+date: 2021-05-17
+---
+
+# java.sql.CallableStatement
+
+This section describes **java.sql.CallableStatement**, the interface for executing the stored procedure.
+
+**Table 1** Support status for java.sql.CallableStatement
+
+| Method Name                                        | Return Type | JDBC 4 Is Supported Or Not |
+| :------------------------------------------------- | :---------- | :------------------------- |
+| getArray(int parameterIndex)                       | Array       | Yes                        |
+| getBigDecimal(int parameterIndex)                  | BigDecimal  | Yes                        |
+| getBlob(int parameterIndex)                        | Blob        | Yes                        |
+| getBoolean(int parameterIndex)                     | boolean     | Yes                        |
+| getByte(int parameterIndex)                        | byte        | Yes                        |
+| getBytes(int parameterIndex)                       | byte[]      | Yes                        |
+| getClob(int parameterIndex)                        | Clob        | Yes                        |
+| getDate(int parameterIndex)                        | Date        | Yes                        |
+| getDate(int parameterIndex, Calendar cal)          | Date        | Yes                        |
+| getDouble(int parameterIndex)                      | double      | Yes                        |
+| getFloat(int parameterIndex)                       | float       | Yes                        |
+| getInt(int parameterIndex)                         | int         | Yes                        |
+| getLong(int parameterIndex)                        | long        | Yes                        |
+| getObject(int parameterIndex)                      | Object      | Yes                        |
+| getObject(int parameterIndex, Class&lt;T&gt; type) | Object      | Yes                        |
+| getShort(int parameterIndex)                       | short       | Yes                        |
+| getSQLXML(int parameterIndex)                      | SQLXML      | Yes                        |
+| getString(int parameterIndex)                      | String      | Yes                        |
+| getNString(int parameterIndex)                     | String      | Yes                        |
+| getTime(int parameterIndex)                        | Time        | Yes                        |
+| getTime(int parameterIndex, Calendar cal)          | Time        | Yes                        |
+| getTimestamp(int parameterIndex)                   | Timestamp   | Yes                        |
+| getTimestamp(int parameterIndex, Calendar cal)     | Timestamp   | Yes                        |
+| registerOutParameter(int parameterIndex, int type) | void        | Yes                        |
+| wasNull()                                          | Boolean     | Yes                        |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - The batch operation of statements containing OUT parameter is not allowed.
+> - The following methods are inherited from java.sql.Statement: close, execute, executeQuery, executeUpdate, getConnection, getResultSet, getUpdateCount, isClosed, setMaxRows, and setFetchSize.
+> - The following methods are inherited from java.sql.PreparedStatement: addBatch, clearParameters, execute, executeQuery, executeUpdate, getMetaData, setBigDecimal, setBoolean, setByte, setBytes, setDate, setDouble, setFloat, setInt, setLong, setNull, setObject, setString, setTime, and setTimestamp.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/3-java-sql-DatabaseMetaData.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/3-java-sql-DatabaseMetaData.md
new file mode 100644
index 0000000000000000000000000000000000000000..bb39de1129ff7d110c05c6941159a67c1e1ed353
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/3-java-sql-DatabaseMetaData.md
@@ -0,0 +1,189 @@
+---
+title: java.sql.DatabaseMetaData
+summary: java.sql.DatabaseMetaData
+author: Guo Huan
+date: 2021-05-17
+---
+
+# java.sql.DatabaseMetaData
+
+This section describes **java.sql.DatabaseMetaData**, the interface for defining database objects.
+
+**Table 1** Support status for java.sql.DatabaseMetaData
+
+| Method Name                                                  | Return Type  | JDBC 4 Is Supported Or Not |
+| :----------------------------------------------------------- | :----------- | :------------------------- |
+| allProceduresAreCallable()                                   | boolean      | Yes                        |
+| allTablesAreSelectable()                                     | boolean      | Yes                        |
+| autoCommitFailureClosesAllResultSets()                       | boolean      | Yes                        |
+| dataDefinitionCausesTransactionCommit()                      | boolean      | Yes                        |
+| dataDefinitionIgnoredInTransactions()                        | boolean      | Yes                        |
+| deletesAreDetected(int type)                                 | boolean      | Yes                        |
+| doesMaxRowSizeIncludeBlobs()                                 | boolean      | Yes                        |
+| generatedKeyAlwaysReturned()                                 | boolean      | Yes                        |
+| getBestRowIdentifier(String catalog, String schema, String table, int scope, boolean nullable) | ResultSet    | Yes                        |
+| getCatalogs()                                                | ResultSet    | Yes                        |
+| getCatalogSeparator()                                        | String       | Yes                        |
+| getCatalogTerm()                                             | String       | Yes                        |
+| getClientInfoProperties()                                    | ResultSet    | Yes                        |
+| getColumnPrivileges(String catalog, String schema, String table, String columnNamePattern) | ResultSet    | Yes                        |
+| getConnection()                                              | Connection   | Yes                        |
+| getCrossReference(String parentCatalog, String parentSchema, String parentTable, String foreignCatalog, String foreignSchema, String foreignTable) | ResultSet    | Yes                        |
+| getDefaultTransactionIsolation()                             | int          | Yes                        |
+| getExportedKeys(String catalog, String schema, String table) | ResultSet    | Yes                        |
+| getExtraNameCharacters()                                     | String       | Yes                        |
+| getFunctionColumns(String catalog, String schemaPattern, String functionNamePattern, String columnNamePattern) | ResultSet    | Yes                        |
+| getFunctions(String catalog, String schemaPattern, String functionNamePattern) | ResultSet    | Yes                        |
+| getIdentifierQuoteString()                                   | String       | Yes                        |
+| getImportedKeys(String catalog, String schema, String table) | ResultSet    | Yes                        |
+| getIndexInfo(String catalog, String schema, String table, boolean unique, boolean approximate) | ResultSet    | Yes                        |
+| getMaxBinaryLiteralLength()                                  | int          | Yes                        |
+| getMaxCatalogNameLength()                                    | int          | Yes                        |
+| getMaxCharLiteralLength()                                    | int          | Yes                        |
+| getMaxColumnNameLength()                                     | int          | Yes                        |
+| getMaxColumnsInGroupBy()                                     | int          | Yes                        |
+| getMaxColumnsInIndex()                                       | int          | Yes                        |
+| getMaxColumnsInOrderBy()                                     | int          | Yes                        |
+| getMaxColumnsInSelect()                                      | int          | Yes                        |
+| getMaxColumnsInTable()                                       | int          | Yes                        |
+| getMaxConnections()                                          | int          | Yes                        |
+| getMaxCursorNameLength()                                     | int          | Yes                        |
+| getMaxIndexLength()                                          | int          | Yes                        |
+| getMaxLogicalLobSize()                                       | default long | Yes                        |
+| getMaxProcedureNameLength()                                  | int          | Yes                        |
+| getMaxRowSize()                                              | int          | Yes                        |
+| getMaxSchemaNameLength()                                     | int          | Yes                        |
+| getMaxStatementLength()                                      | int          | Yes                        |
+| getMaxStatements()                                           | int          | Yes                        |
+| getMaxTableNameLength()                                      | int          | Yes                        |
+| getMaxTablesInSelect()                                       | int          | Yes                        |
+| getMaxUserNameLength()                                       | int          | Yes                        |
+| getNumericFunctions()                                        | String       | Yes                        |
+| getPrimaryKeys(String catalog, String schema, String table)  | ResultSet    | Yes                        |
+| getProcedureColumns(String catalog, String schemaPattern, String procedureNamePattern, String columnNamePattern) | ResultSet    | Yes                        |
+| getProcedures(String catalog, String schemaPattern, String procedureNamePattern) | ResultSet    | Yes                        |
+| getProcedureTerm()                                           | String       | Yes                        |
+| getSchemas()                                                 | ResultSet    | Yes                        |
+| getSchemas(String catalog, String schemaPattern)             | ResultSet    | Yes                        |
+| getSchemaTerm()                                              | String       | Yes                        |
+| getSearchStringEscape()                                      | String       | Yes                        |
+| getSQLKeywords()                                             | String       | Yes                        |
+| getSQLStateType()                                            | int          | Yes                        |
+| getStringFunctions()                                         | String       | Yes                        |
+| getSystemFunctions()                                         | String       | Yes                        |
+| getTablePrivileges(String catalog, String schemaPattern, String tableNamePattern) | ResultSet    | Yes                        |
+| getTimeDateFunctions()                                       | String       | Yes                        |
+| getTypeInfo()                                                | ResultSet    | Yes                        |
+| getUDTs(String catalog, String schemaPattern, String typeNamePattern, int[] types) | ResultSet    | Yes                        |
+| getURL()                                                     | String       | Yes                        |
+| getVersionColumns(String catalog, String schema, String table) | ResultSet    | Yes                        |
+| insertsAreDetected(int type)                                 | boolean      | Yes                        |
+| locatorsUpdateCopy()                                         | boolean      | Yes                        |
+| othersDeletesAreVisible(int type)                            | boolean      | Yes                        |
+| othersInsertsAreVisible(int type)                            | boolean      | Yes                        |
+| othersUpdatesAreVisible(int type)                            | boolean      | Yes                        |
+| ownDeletesAreVisible(int type)                               | boolean      | Yes                        |
+| ownInsertsAreVisible(int type)                               | boolean      | Yes                        |
+| ownUpdatesAreVisible(int type)                               | boolean      | Yes                        |
+| storesLowerCaseIdentifiers()                                 | boolean      | Yes                        |
+| storesMixedCaseIdentifiers()                                 | boolean      | Yes                        |
+| storesUpperCaseIdentifiers()                                 | boolean      | Yes                        |
+| supportsBatchUpdates()                                       | boolean      | Yes                        |
+| supportsCatalogsInDataManipulation()                         | boolean      | Yes                        |
+| supportsCatalogsInIndexDefinitions()                         | boolean      | Yes                        |
+| supportsCatalogsInPrivilegeDefinitions()                     | boolean      | Yes                        |
+| supportsCatalogsInProcedureCalls()                           | boolean      | Yes                        |
+| supportsCatalogsInTableDefinitions()                         | boolean      | Yes                        |
+| supportsCorrelatedSubqueries()                               | boolean      | Yes                        |
+| supportsDataDefinitionAndDataManipulationTransactions()      | boolean      | Yes                        |
+| supportsDataManipulationTransactionsOnly()                   | boolean      | Yes                        |
+| supportsGetGeneratedKeys()                                   | boolean      | Yes                        |
+| supportsMixedCaseIdentifiers()                               | boolean      | Yes                        |
+| supportsMultipleOpenResults()                                | boolean      | Yes                        |
+| supportsNamedParameters()                                    | boolean      | Yes                        |
+| supportsOpenCursorsAcrossCommit()                            | boolean      | Yes                        |
+| supportsOpenCursorsAcrossRollback()                          | boolean      | Yes                        |
+| supportsOpenStatementsAcrossCommit()                         | boolean      | Yes                        |
+| supportsOpenStatementsAcrossRollback()                       | boolean      | Yes                        |
+| supportsPositionedDelete()                                   | boolean      | Yes                        |
+| supportsPositionedUpdate()                                   | boolean      | Yes                        |
+| supportsRefCursors()                                         | boolean      | Yes                        |
+| supportsResultSetConcurrency(int type, int concurrency)      | boolean      | Yes                        |
+| supportsResultSetType(int type)                              | boolean      | Yes                        |
+| supportsSchemasInIndexDefinitions()                          | boolean      | Yes                        |
+| supportsSchemasInPrivilegeDefinitions()                      | boolean      | Yes                        |
+| supportsSchemasInProcedureCalls()                            | boolean      | Yes                        |
+| supportsSchemasInTableDefinitions()                          | boolean      | Yes                        |
+| supportsSelectForUpdate()                                    | boolean      | Yes                        |
+| supportsStatementPooling()                                   | boolean      | Yes                        |
+| supportsStoredFunctionsUsingCallSyntax()                     | boolean      | Yes                        |
+| supportsStoredProcedures()                                   | boolean      | Yes                        |
+| supportsSubqueriesInComparisons()                            | boolean      | Yes                        |
+| supportsSubqueriesInExists()                                 | boolean      | Yes                        |
+| supportsSubqueriesInIns()                                    | boolean      | Yes                        |
+| supportsSubqueriesInQuantifieds()                            | boolean      | Yes                        |
+| supportsTransactionIsolationLevel(int level)                 | boolean      | Yes                        |
+| supportsTransactions()                                       | boolean      | Yes                        |
+| supportsUnion()                                              | boolean      | Yes                        |
+| supportsUnionAll()                                           | boolean      | Yes                        |
+| updatesAreDetected(int type)                                 | boolean      | Yes                        |
+| getTables(String catalog, String schemaPattern, String tableNamePattern, String[] types) | ResultSet    | Yes                        |
+| getColumns(String catalog, String schemaPattern, String tableNamePattern, String columnNamePattern) | ResultSet    | Yes                        |
+| getTableTypes()                                              | ResultSet    | Yes                        |
+| getUserName()                                                | String       | Yes                        |
+| isReadOnly()                                                 | boolean      | Yes                        |
+| nullsAreSortedHigh()                                         | boolean      | Yes                        |
+| nullsAreSortedLow()                                          | boolean      | Yes                        |
+| nullsAreSortedAtStart()                                      | boolean      | Yes                        |
+| nullsAreSortedAtEnd()                                        | boolean      | Yes                        |
+| getDatabaseProductName()                                     | String       | Yes                        |
+| getDatabaseProductVersion()                                  | String       | Yes                        |
+| getDriverName()                                              | String       | Yes                        |
+| getDriverVersion()                                           | String       | Yes                        |
+| getDriverMajorVersion()                                      | int          | Yes                        |
+| getDriverMinorVersion()                                      | int          | Yes                        |
+| usesLocalFiles()                                             | boolean      | Yes                        |
+| usesLocalFilePerTable()                                      | boolean      | Yes                        |
+| supportsMixedCaseIdentifiers()                               | boolean      | Yes                        |
+| storesUpperCaseIdentifiers()                                 | boolean      | Yes                        |
+| storesLowerCaseIdentifiers()                                 | boolean      | Yes                        |
+| supportsMixedCaseQuotedIdentifiers()                         | boolean      | Yes                        |
+| storesUpperCaseQuotedIdentifiers()                           | boolean      | Yes                        |
+| storesLowerCaseQuotedIdentifiers()                           | boolean      | Yes                        |
+| storesMixedCaseQuotedIdentifiers()                           | boolean      | Yes                        |
+| supportsAlterTableWithAddColumn()                            | boolean      | Yes                        |
+| supportsAlterTableWithDropColumn()                           | boolean      | Yes                        |
+| supportsColumnAliasing()                                     | boolean      | Yes                        |
+| nullPlusNonNullIsNull()                                      | boolean      | Yes                        |
+| supportsConvert()                                            | boolean      | Yes                        |
+| supportsConvert(int fromType, int toType)                    | boolean      | Yes                        |
+| supportsTableCorrelationNames()                              | boolean      | Yes                        |
+| supportsDifferentTableCorrelationNames()                     | boolean      | Yes                        |
+| supportsExpressionsInOrderBy()                               | boolean      | Yes                        |
+| supportsOrderByUnrelated()                                   | boolean      | Yes                        |
+| supportsGroupBy()                                            | boolean      | Yes                        |
+| supportsGroupByUnrelated()                                   | boolean      | Yes                        |
+| supportsGroupByBeyondSelect()                                | boolean      | Yes                        |
+| supportsLikeEscapeClause()                                   | boolean      | Yes                        |
+| supportsMultipleResultSets()                                 | boolean      | Yes                        |
+| supportsMultipleTransactions()                               | boolean      | Yes                        |
+| supportsNonNullableColumns()                                 | boolean      | Yes                        |
+| supportsMinimumSQLGrammar()                                  | boolean      | Yes                        |
+| supportsCoreSQLGrammar()                                     | boolean      | Yes                        |
+| supportsExtendedSQLGrammar()                                 | boolean      | Yes                        |
+| supportsANSI92EntryLevelSQL()                                | boolean      | Yes                        |
+| supportsANSI92IntermediateSQL()                              | boolean      | Yes                        |
+| supportsANSI92FullSQL()                                      | boolean      | Yes                        |
+| supportsIntegrityEnhancementFacility()                       | boolean      | Yes                        |
+| supportsOuterJoins()                                         | boolean      | Yes                        |
+| supportsFullOuterJoins()                                     | boolean      | Yes                        |
+| supportsLimitedOuterJoins()                                  | boolean      | Yes                        |
+| isCatalogAtStart()                                           | boolean      | Yes                        |
+| supportsSchemasInDataManipulation()                          | boolean      | Yes                        |
+| supportsSavepoints()                                         | boolean      | Yes                        |
+| supportsResultSetHoldability(int holdability)                | boolean      | Yes                        |
+| getResultSetHoldability()                                    | int          | Yes                        |
+| getDatabaseMajorVersion()                                    | int          | Yes                        |
+| getDatabaseMinorVersion()                                    | int          | Yes                        |
+| getJDBCMajorVersion()                                        | int          | Yes                        |
+| getJDBCMinorVersion()                                        | int          | Yes                        |
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/4-java-sql-Driver.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/4-java-sql-Driver.md
new file mode 100644
index 0000000000000000000000000000000000000000..cb99815436e25f30ee33cab95079467f9aab0a14
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/4-java-sql-Driver.md
@@ -0,0 +1,22 @@
+---
+title: java.sql.Driver
+summary: java.sql.Driver
+author: Guo Huan
+date: 2021-05-17
+---
+
+# java.sql.Driver
+
+This section describes **java.sql.Driver**, the database driver interface.
+
+**Table 1** Support status for java.sql.Driver
+
+| Method Name                                  | Return Type          | JDBC 4 Is Supported Or Not |
+| :------------------------------------------- | :------------------- | :------------------------- |
+| acceptsURL(String url)                       | Boolean              | Yes                        |
+| connect(String url, Properties info)         | Connection           | Yes                        |
+| jdbcCompliant()                              | Boolean              | Yes                        |
+| getMajorVersion()                            | int                  | Yes                        |
+| getMinorVersion()                            | int                  | Yes                        |
+| getParentLogger()                            | Logger               | Yes                        |
+| getPropertyInfo(String url, Properties info) | DriverPropertyInfo[] | Yes                        |
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/5-java-sql-PreparedStatement.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/5-java-sql-PreparedStatement.md
new file mode 100644
index 0000000000000000000000000000000000000000..50091489a626e20b507a6220852ed0e968204686
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/5-java-sql-PreparedStatement.md
@@ -0,0 +1,70 @@
+---
+title: java.sql.PreparedStatement
+summary: java.sql.PreparedStatement
+author: Guo Huan
+date: 2021-05-17
+---
+
+# java.sql.PreparedStatement
+
+This section describes **java.sql.PreparedStatement**, the interface for preparing statements.
+
+**Table 1** Support status for java.sql.PreparedStatement
+
+| Method Name                                                  | Return Type       | JDBC 4 Is Supported Or Not |
+| :----------------------------------------------------------- | :---------------- | :------------------------- |
+| clearParameters()                                            | void              | Yes                        |
+| execute()                                                    | Boolean           | Yes                        |
+| executeQuery()                                               | ResultSet         | Yes                        |
+| excuteUpdate()                                               | int               | Yes                        |
+| executeLargeUpdate()                                         | long              | No                         |
+| getMetaData()                                                | ResultSetMetaData | Yes                        |
+| getParameterMetaData()                                       | ParameterMetaData | Yes                        |
+| setArray(int parameterIndex, Array x)                        | void              | Yes                        |
+| setAsciiStream(int parameterIndex, InputStream x, int length) | void              | Yes                        |
+| setBinaryStream(int parameterIndex, InputStream x)           | void              | Yes                        |
+| setBinaryStream(int parameterIndex, InputStream x, int length) | void              | Yes                        |
+| setBinaryStream(int parameterIndex, InputStream x, long length) | void              | Yes                        |
+| setBlob(int parameterIndex, InputStream inputStream)         | void              | Yes                        |
+| setBlob(int parameterIndex, InputStream inputStream, long length) | void              | Yes                        |
+| setBlob(int parameterIndex, Blob x)                          | void              | Yes                        |
+| setCharacterStream(int parameterIndex, Reader reader)        | void              | Yes                        |
+| setCharacterStream(int parameterIndex, Reader reader, int length) | void              | Yes                        |
+| setClob(int parameterIndex, Reader reader)                   | void              | Yes                        |
+| setClob(int parameterIndex, Reader reader, long length)      | void              | Yes                        |
+| setClob(int parameterIndex, Clob x)                          | void              | Yes                        |
+| setDate(int parameterIndex, Date x, Calendar cal)            | void              | Yes                        |
+| setNull(int parameterIndex, int sqlType)                     | void              | Yes                        |
+| setNull(int parameterIndex, int sqlType, String typeName)    | void              | Yes                        |
+| setObject(int parameterIndex, Object x)                      | void              | Yes                        |
+| setObject(int parameterIndex, Object x, int targetSqlType)   | void              | Yes                        |
+| setObject(int parameterIndex, Object x, int targetSqlType, int scaleOrLength) | void              | Yes                        |
+| setSQLXML(int parameterIndex, SQLXML xmlObject)              | void              | Yes                        |
+| setTime(int parameterIndex, Time x)                          | void              | Yes                        |
+| setTime(int parameterIndex, Time x, Calendar cal)            | void              | Yes                        |
+| setTimestamp(int parameterIndex, Timestamp x)                | void              | Yes                        |
+| setTimestamp(int parameterIndex, Timestamp x, Calendar cal)  | void              | Yes                        |
+| setUnicodeStream(int parameterIndex, InputStream x, int length) | void              | Yes                        |
+| setURL(int parameterIndex, URL x)                            | void              | Yes                        |
+| setBoolean(int parameterIndex, boolean x)                    | void              | Yes                        |
+| setBigDecimal(int parameterIndex, BigDecimal x)              | void              | Yes                        |
+| setByte(int parameterIndex, byte x)                          | void              | Yes                        |
+| setBytes(int parameterIndex, byte[] x)                       | void              | Yes                        |
+| setDate(int parameterIndex, Date x)                          | void              | Yes                        |
+| setDouble(int parameterIndex, double x)                      | void              | Yes                        |
+| setFloat(int parameterIndex, float x)                        | void              | Yes                        |
+| setInt(int parameterIndex, int x)                            | void              | Yes                        |
+| setLong(int parameterIndex, long x)                          | void              | Yes                        |
+| setShort(int parameterIndex, short x)                        | void              | Yes                        |
+| setString(int parameterIndex, String x)                      | void              | Yes                        |
+| setNString(int parameterIndex, String x)                     | void              | Yes                        |
+| addBatch()                                                   | void              | Yes                        |
+| executeBatch()                                               | int[]             | Yes                        |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - Execute addBatch() and execute() only after running clearBatch().
+> - Batch is not cleared by calling executeBatch(). Clear batch by explicitly calling clearBatch().
+> - After bounded variables of a batch are added, if you want to reuse these values (add a batch again), set*() is not necessary.
+> - The following methods are inherited from java.sql.Statement: close, execute, executeQuery, executeUpdate, getConnection, getResultSet, getUpdateCount, isClosed, setMaxRows, and setFetchSize.
+> - The **executeLargeUpdate()** method can only be used in JDBC 4.2 or later.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/6-java-sql-ResultSet.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/6-java-sql-ResultSet.md
new file mode 100644
index 0000000000000000000000000000000000000000..390cb97bc47eca24ad83ed1a653e4f4f7602d0a1
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/6-java-sql-ResultSet.md
@@ -0,0 +1,154 @@
+---
+title: java.sql.ResultSet
+summary: java.sql.ResultSet
+author: Guo Huan
+date: 2021-05-17
+---
+
+# java.sql.ResultSet
+
+This section describes **java.sql.ResultSet**, the interface for execution result sets.
+
+**Table 1** Support status for java.sql.ResultSet
+
+| Method Name                                                  | Return Type       | JDBC 4 Is Supported Or Not |
+| :----------------------------------------------------------- | :---------------- | :------------------------- |
+| absolute(int row)                                            | Boolean           | Yes                        |
+| afterLast()                                                  | void              | Yes                        |
+| beforeFirst()                                                | void              | Yes                        |
+| cancelRowUpdates()                                           | void              | Yes                        |
+| clearWarnings()                                              | void              | Yes                        |
+| close()                                                      | void              | Yes                        |
+| deleteRow()                                                  | void              | Yes                        |
+| findColumn(String columnLabel)                               | int               | Yes                        |
+| first()                                                      | Boolean           | Yes                        |
+| getArray(int columnIndex)                                    | Array             | Yes                        |
+| getArray(String columnLabel)                                 | Array             | Yes                        |
+| getAsciiStream(int columnIndex)                              | InputStream       | Yes                        |
+| getAsciiStream(String columnLabel)                           | InputStream       | Yes                        |
+| getBigDecimal(int columnIndex)                               | BigDecimal        | Yes                        |
+| getBigDecimal(String columnLabel)                            | BigDecimal        | Yes                        |
+| getBinaryStream(int columnIndex)                             | InputStream       | Yes                        |
+| getBinaryStream(String columnLabel)                          | InputStream       | Yes                        |
+| getBlob(int columnIndex)                                     | Blob              | Yes                        |
+| getBlob(String columnLabel)                                  | Blob              | Yes                        |
+| getBoolean(int columnIndex)                                  | Boolean           | Yes                        |
+| getBoolean(String columnLabel)                               | Boolean           | Yes                        |
+| getByte(int columnIndex)                                     | byte              | Yes                        |
+| getBytes(int columnIndex)                                    | byte[]            | Yes                        |
+| getByte(String columnLabel)                                  | byte              | Yes                        |
+| getBytes(String columnLabel)                                 | byte[]            | Yes                        |
+| getCharacterStream(int columnIndex)                          | Reader            | Yes                        |
+| getCharacterStream(String columnLabel)                       | Reader            | Yes                        |
+| getClob(int columnIndex)                                     | Clob              | Yes                        |
+| getClob(String columnLabel)                                  | Clob              | Yes                        |
+| getConcurrency()                                             | int               | Yes                        |
+| getCursorName()                                              | String            | Yes                        |
+| getDate(int columnIndex)                                     | Date              | Yes                        |
+| getDate(int columnIndex, Calendar cal)                       | Date              | Yes                        |
+| getDate(String columnLabel)                                  | Date              | Yes                        |
+| getDate(String columnLabel, Calendar cal)                    | Date              | Yes                        |
+| getDouble(int columnIndex)                                   | double            | Yes                        |
+| getDouble(String columnLabel)                                | double            | Yes                        |
+| getFetchDirection()                                          | int               | Yes                        |
+| getFetchSize()                                               | int               | Yes                        |
+| getFloat(int columnIndex)                                    | float             | Yes                        |
+| getFloat(String columnLabel)                                 | float             | Yes                        |
+| getInt(int columnIndex)                                      | int               | Yes                        |
+| getInt(String columnLabel)                                   | int               | Yes                        |
+| getLong(int columnIndex)                                     | long              | Yes                        |
+| getLong(String columnLabel)                                  | long              | Yes                        |
+| getMetaData()                                                | ResultSetMetaData | Yes                        |
+| getObject(int columnIndex)                                   | Object            | Yes                        |
+| getObject(int columnIndex, Class&lt;T&gt; type)              | &lt;T&gt; T       | Yes                        |
+| getObject(int columnIndex, Map&lt;String,Class&lt;?&gt;&gt; map) | Object            | Yes                        |
+| getObject(String columnLabel)                                | Object            | Yes                        |
+| getObject(String columnLabel, Class&lt;T&gt; type)           | &lt;T&gt; T       | Yes                        |
+| getObject(String columnLabel, Map&lt;String,Class&lt;?&gt;&gt; map) | Object            | Yes                        |
+| getRow()                                                     | int               | Yes                        |
+| getShort(int columnIndex)                                    | short             | Yes                        |
+| getShort(String columnLabel)                                 | short             | Yes                        |
+| getSQLXML(int columnIndex)                                   | SQLXML            | Yes                        |
+| getSQLXML(String columnLabel)                                | SQLXML            | Yes                        |
+| getStatement()                                               | Statement         | Yes                        |
+| getString(int columnIndex)                                   | String            | Yes                        |
+| getString(String columnLabel)                                | String            | Yes                        |
+| getNString(int columnIndex)                                  | String            | Yes                        |
+| getNString(String columnLabel)                               | String            | Yes                        |
+| getTime(int columnIndex)                                     | Time              | Yes                        |
+| getTime(int columnIndex, Calendar cal)                       | Time              | Yes                        |
+| getTime(String columnLabel)                                  | Time              | Yes                        |
+| getTime(String columnLabel, Calendar cal)                    | Time              | Yes                        |
+| getTimestamp(int columnIndex)                                | Timestamp         | Yes                        |
+| getTimestamp(int columnIndex, Calendar cal)                  | Timestamp         | Yes                        |
+| getTimestamp(String columnLabel)                             | Timestamp         | Yes                        |
+| getTimestamp(String columnLabel, Calendar cal)               | Timestamp         | Yes                        |
+| getType()                                                    | int               | Yes                        |
+| getWarnings()                                                | SQLWarning        | Yes                        |
+| insertRow()                                                  | void              | Yes                        |
+| isAfterLast()                                                | Boolean           | Yes                        |
+| isBeforeFirst()                                              | Boolean           | Yes                        |
+| isClosed()                                                   | Boolean           | Yes                        |
+| isFirst()                                                    | Boolean           | Yes                        |
+| isLast()                                                     | Boolean           | Yes                        |
+| last()                                                       | Boolean           | Yes                        |
+| moveToCurrentRow()                                           | void              | Yes                        |
+| moveToInsertRow()                                            | void              | Yes                        |
+| next()                                                       | Boolean           | Yes                        |
+| previous()                                                   | Boolean           | Yes                        |
+| refreshRow()                                                 | void              | Yes                        |
+| relative(int rows)                                           | Boolean           | Yes                        |
+| rowDeleted()                                                 | Boolean           | Yes                        |
+| rowInserted()                                                | Boolean           | Yes                        |
+| rowUpdated()                                                 | Boolean           | Yes                        |
+| setFetchDirection(int direction)                             | void              | Yes                        |
+| setFetchSize(int rows)                                       | void              | Yes                        |
+| updateArray(int columnIndex, Array x)                        | void              | Yes                        |
+| updateArray(String columnLabel, Array x)                     | void              | Yes                        |
+| updateAsciiStream(int columnIndex, InputStream x, int length) | void              | Yes                        |
+| updateAsciiStream(String columnLabel, InputStream x, int length) | void              | Yes                        |
+| updateBigDecimal(int columnIndex, BigDecimal x)              | void              | Yes                        |
+| updateBigDecimal(String columnLabel, BigDecimal x)           | void              | Yes                        |
+| updateBinaryStream(int columnIndex, InputStream x, int length) | void              | Yes                        |
+| updateBinaryStream(String columnLabel, InputStream x, int length) | void              | Yes                        |
+| updateBoolean(int columnIndex, boolean x)                    | void              | Yes                        |
+| updateBoolean(String columnLabel, boolean x)                 | void              | Yes                        |
+| updateByte(int columnIndex, byte x)                          | void              | Yes                        |
+| updateByte(String columnLabel, byte x)                       | void              | Yes                        |
+| updateBytes(int columnIndex, byte[] x)                       | void              | Yes                        |
+| updateBytes(String columnLabel, byte[] x)                    | void              | Yes                        |
+| updateCharacterStream(int columnIndex, Reader x, int length) | void              | Yes                        |
+| updateCharacterStream(String columnLabel, Reader reader, int length) | void              | Yes                        |
+| updateDate(int columnIndex, Date x)                          | void              | Yes                        |
+| updateDate(String columnLabel, Date x)                       | void              | Yes                        |
+| updateDouble(int columnIndex, double x)                      | void              | Yes                        |
+| updateDouble(String columnLabel, double x)                   | void              | Yes                        |
+| updateFloat(int columnIndex, float x)                        | void              | Yes                        |
+| updateFloat(String columnLabel, float x)                     | void              | Yes                        |
+| updateInt(int columnIndex, int x)                            | void              | Yes                        |
+| updateInt(String columnLabel, int x)                         | void              | Yes                        |
+| updateLong(int columnIndex, long x)                          | void              | Yes                        |
+| updateLong(String columnLabel, long x)                       | void              | Yes                        |
+| updateNull(int columnIndex)                                  | void              | Yes                        |
+| updateNull(String columnLabel)                               | void              | Yes                        |
+| updateObject(int columnIndex, Object x)                      | void              | Yes                        |
+| updateObject(int columnIndex, Object x, int scaleOrLength)   | void              | Yes                        |
+| updateObject(String columnLabel, Object x)                   | void              | Yes                        |
+| updateObject(String columnLabel, Object x, int scaleOrLength) | void              | Yes                        |
+| updateRow()                                                  | void              | Yes                        |
+| updateShort(int columnIndex, short x)                        | void              | Yes                        |
+| updateShort(String columnLabel, short x)                     | void              | Yes                        |
+| updateSQLXML(int columnIndex, SQLXML xmlObject)              | void              | Yes                        |
+| updateSQLXML(String columnLabel, SQLXML xmlObject)           | void              | Yes                        |
+| updateString(int columnIndex, String x)                      | void              | Yes                        |
+| updateString(String columnLabel, String x)                   | void              | Yes                        |
+| updateTime(int columnIndex, Time x)                          | void              | Yes                        |
+| updateTime(String columnLabel, Time x)                       | void              | Yes                        |
+| updateTimestamp(int columnIndex, Timestamp x)                | void              | Yes                        |
+| updateTimestamp(String columnLabel, Timestamp x)             | void              | Yes                        |
+| wasNull()                                                    | Boolean           | Yes                        |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - One Statement cannot have multiple open ResultSets.
+> - The cursor that is used for traversing the ResultSet cannot be open after being committed.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/7-java-sql-ResultSetMetaData.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/7-java-sql-ResultSetMetaData.md
new file mode 100644
index 0000000000000000000000000000000000000000..e8d43f9a30edd55393bc1fbede5d13d6e4b781f7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/7-java-sql-ResultSetMetaData.md
@@ -0,0 +1,36 @@
+---
+title: java.sql.ResultSetMetaData
+summary: java.sql.ResultSetMetaData
+author: Guo Huan
+date: 2021-05-17
+---
+
+# java.sql.ResultSetMetaData
+
+This section describes **java.sql.ResultSetMetaData**, which provides details about ResultSet object information.
+
+**Table 1** Support status for java.sql.ResultSetMetaData
+
+| Method Name                      | Return Type | JDBC 4 Is Supported Or Not |
+| :------------------------------- | :---------- | :------------------------- |
+| getCatalogName(int column)       | String      | Yes                        |
+| getColumnClassName(int column)   | String      | Yes                        |
+| getColumnCount()                 | int         | Yes                        |
+| getColumnDisplaySize(int column) | int         | Yes                        |
+| getColumnLabel(int column)       | String      | Yes                        |
+| getColumnName(int column)        | String      | Yes                        |
+| getColumnType(int column)        | int         | Yes                        |
+| getColumnTypeName(int column)    | String      | Yes                        |
+| getPrecision(int column)         | int         | Yes                        |
+| getScale(int column)             | int         | Yes                        |
+| getSchemaName(int column)        | String      | Yes                        |
+| getTableName(int column)         | String      | Yes                        |
+| isAutoIncrement(int column)      | boolean     | Yes                        |
+| isCaseSensitive(int column)      | boolean     | Yes                        |
+| isCurrency(int column)           | boolean     | Yes                        |
+| isDefinitelyWritable(int column) | boolean     | Yes                        |
+| isNullable(int column)           | int         | Yes                        |
+| isReadOnly(int column)           | boolean     | Yes                        |
+| isSearchable(int column)         | boolean     | Yes                        |
+| isSigned(int column)             | boolean     | Yes                        |
+| isWritable(int column)           | boolean     | Yes                        |
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/8-java-sql-Statement.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/8-java-sql-Statement.md
new file mode 100644
index 0000000000000000000000000000000000000000..d3333ee2e427a91f87c980033b042a552cfe339e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/8-java-sql-Statement.md
@@ -0,0 +1,69 @@
+---
+title: java.sql.Statement
+summary: java.sql.Statement
+author: Guo Huan
+date: 2021-05-17
+---
+
+# java.sql.Statement
+
+This section describes **java.sql.Statement**, the interface for executing SQL statements.
+
+**Table 1** Support status for java.sql.Statement
+
+| Method Name                                           | Return Type | JDBC 4 Is Supported Or Not |
+| :---------------------------------------------------- | :---------- | :------------------------- |
+| addBatch(String sql)                                  | void        | Yes                        |
+| clearBatch()                                          | void        | Yes                        |
+| clearWarnings()                                       | void        | Yes                        |
+| close()                                               | void        | Yes                        |
+| closeOnCompletion()                                   | void        | Yes                        |
+| execute(String sql)                                   | Boolean     | Yes                        |
+| execute(String sql, int autoGeneratedKeys)            | Boolean     | Yes                        |
+| execute(String sql, int[] columnIndexes)              | Boolean     | Yes                        |
+| execute(String sql, String[] columnNames)             | Boolean     | Yes                        |
+| executeBatch()                                        | Boolean     | Yes                        |
+| executeQuery(String sql)                              | ResultSet   | Yes                        |
+| executeUpdate(String sql)                             | int         | Yes                        |
+| executeUpdate(String sql, int autoGeneratedKeys)      | int         | Yes                        |
+| executeUpdate(String sql, int[] columnIndexes)        | int         | Yes                        |
+| executeUpdate(String sql, String[] columnNames)       | int         | Yes                        |
+| getConnection()                                       | Connection  | Yes                        |
+| getFetchDirection()                                   | int         | Yes                        |
+| getFetchSize()                                        | int         | Yes                        |
+| getGeneratedKeys()                                    | ResultSet   | Yes                        |
+| getMaxFieldSize()                                     | int         | Yes                        |
+| getMaxRows()                                          | int         | Yes                        |
+| getMoreResults()                                      | boolean     | Yes                        |
+| getMoreResults(int current)                           | boolean     | Yes                        |
+| getResultSet()                                        | ResultSet   | Yes                        |
+| getResultSetConcurrency()                             | int         | Yes                        |
+| getResultSetHoldability()                             | int         | Yes                        |
+| getResultSetType()                                    | int         | Yes                        |
+| getQueryTimeout()                                     | int         | Yes                        |
+| getUpdateCount()                                      | int         | Yes                        |
+| getWarnings()                                         | SQLWarning  | Yes                        |
+| isClosed()                                            | Boolean     | Yes                        |
+| isCloseOnCompletion()                                 | Boolean     | Yes                        |
+| isPoolable()                                          | Boolean     | Yes                        |
+| setCursorName(String name)                            | void        | Yes                        |
+| setEscapeProcessing(boolean enable)                   | void        | Yes                        |
+| setFetchDirection(int direction)                      | void        | Yes                        |
+| setMaxFieldSize(int max)                              | void        | Yes                        |
+| setMaxRows(int max)                                   | void        | Yes                        |
+| setPoolable(boolean poolable)                         | void        | Yes                        |
+| setQueryTimeout(int seconds)                          | void        | Yes                        |
+| setFetchSize(int rows)                                | void        | Yes                        |
+| cancel()                                              | void        | Yes                        |
+| executeLargeUpdate(String sql)                        | long        | No                         |
+| getLargeUpdateCount()                                 | long        | No                         |
+| executeLargeBatch()                                   | long        | No                         |
+| executeLargeUpdate(String sql, int autoGeneratedKeys) | long        | No                         |
+| executeLargeUpdate(String sql, int[] columnIndexes)   | long        | No                         |
+| executeLargeUpdate(String sql, String[] columnNames)  | long        | No                         |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - Using setFetchSize can reduce the memory occupied by result sets on the client. Result sets are packaged into cursors and segmented for processing, which will increase the communication traffic between the database and the client, affecting performance.
+> - Database cursors are valid only within their transactions. If **setFetchSize** is set, set **setAutoCommit(false)** and commit transactions on the connection to flush service data to a database.
+> - **LargeUpdate** methods can only be used in JDBC 4.2 or later.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/9-javax-sql-ConnectionPoolDataSource.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/9-javax-sql-ConnectionPoolDataSource.md
new file mode 100644
index 0000000000000000000000000000000000000000..73d1518fb6b9ee1849a7d1fba13d185e3d87b1d1
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/9-javax-sql-ConnectionPoolDataSource.md
@@ -0,0 +1,17 @@
+---
+title: javax.sql.ConnectionPoolDataSource
+summary: javax.sql.ConnectionPoolDataSource
+author: Guo Huan
+date: 2021-05-17
+---
+
+# javax.sql.ConnectionPoolDataSource
+
+This section describes **javax.sql.ConnectionPoolDataSource**, the interface for data source connection pools.
+
+**Table 1** Support status for javax.sql.ConnectionPoolDataSource
+
+| Method Name                                      | Return Type      | JDBC 4 Is Supported Or Not |
+| :----------------------------------------------- | :--------------- | :------------------------- |
+| getPooledConnection()                            | PooledConnection | Yes                        |
+| getPooledConnection(String user,String password) | PooledConnection | Yes                        |
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/2-jdbc-package-driver-class-and-environment-class.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/2-jdbc-package-driver-class-and-environment-class.md
new file mode 100644
index 0000000000000000000000000000000000000000..b25547806847ed5d3ca1f71cee3cc0a8f1f09597
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/2-jdbc-package-driver-class-and-environment-class.md
@@ -0,0 +1,51 @@
+---
+title: JDBC Package, Driver Class, and Environment Class
+summary: JDBC Package, Driver Class, and Environment Class
+author: Guo Huan
+date: 2021-04-26
+---
+
+# JDBC Package, Driver Class, and Environment Class
+
+**JDBC Package**
+
+Run **build.sh** in the source code directory on Linux OS to obtain the driver JAR package **postgresql.jar**, which is stored in the source code directory. Obtain the package from the release package named [**openGauss-x.x.x-JDBC.tar.gz**](https://opengauss.org/en/download.html).
+
+The driver package is compatible with PostgreSQL. The class name and structure in the driver are the same as those in the PostgreSQL driver. All applications running on PostgreSQL can be smoothly migrated to the current system.
+
+**Driver Class**
+
+Before establishing a database connection, load the **org.postgresql.Driver** database driver class.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - MogDB is compatible with PostgreSQL in the use of JDBC. Therefore, when two JDBC drivers are used in the same process, class names may conflict.
+>
+> - Compared with the PostgreSQL driver, the openGauss JDBC driver has the following enhanced features:
+>       - The SHA256 encryption mode is supported for login.
+>       - The third-party log framework that implements the sf4j API can be connected.
+>       - DR failover is supported.
+
+**Environment Class**
+
+JDK 1.8 must be configured on the client. The configuration method is as follows:
+
+1. In the MS-DOS window, run **java -version** to check the JDK version. Ensure that the version is JDK 1.8. If JDK is not installed, download the installation package from the official website and install it.
+
+2. Configure system environment variables.
+
+   1. Right-click **My computer** and choose **Properties**.
+
+   2. In the navigation pane, choose **Advanced system settings**.
+
+   3. In the **System Properties** dialog box, click **Environment Variables** on the **Advanced** tab page.
+
+   4. In the **System variables** area of the **Environment Variables** dialog box, click **New** or **Edit** to configure system variables. For details, see [Table 1](#Description).
+
+      <a id="Description">**Table 1**</a> Description
+
+      | Variable  | Operation                                                    | Variable Value                                               |
+      | :-------- | :----------------------------------------------------------- | :----------------------------------------------------------- |
+      | JAVA_HOME | - If the variable exists, click **Edit**.<br />- If the variable does not exist, click **New**. | Specifies the Java installation directory.<br />Example: C:\Program Files\Java\jdk1.8.0_131 |
+      | Path      | Edit                                                         | - If JAVA_HOME is configured, add **%JAVA_HOME%\bin** before the variable value.<br />- If JAVA_HOME is not configured, add the full Java installation path before the variable value:<br />C:\Program Files\Java\jdk1.8.0_131\bin; |
+      | CLASSPATH | New                                                          | .;%JAVA_HOME%\lib;%JAVA_H                                    |
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/3-development-process.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/3-development-process.md
new file mode 100644
index 0000000000000000000000000000000000000000..e73100d573bff2b2082b342988768e7879df88f2
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/3-development-process.md
@@ -0,0 +1,12 @@
+---
+title: Development Process
+summary: Development Process
+author: Guo Huan
+date: 2021-04-26
+---
+
+# Development Process
+
+**Figure 1** Application development process based on JDBC
+
+![application-development-process-based-on-jdbc](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/development-process-2.png)
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/4-loading-the-driver.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/4-loading-the-driver.md
new file mode 100644
index 0000000000000000000000000000000000000000..246146e23e08dc20044f575372e0d642866019b3
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/4-loading-the-driver.md
@@ -0,0 +1,19 @@
+---
+title: Loading the Driver
+summary: Loading the Driver
+author: Guo Huan
+date: 2021-04-26
+---
+
+# Loading the Driver
+
+Load the database driver before creating a database connection.
+
+You can load the driver in the following ways:
+
+- Before creating a connection, implicitly load the driver in the code:**Class.forName("org.postgresql.Driver")**
+
+- During the JVM startup, transfer the driver as a parameter to the JVM:**java -Djdbc.drivers=org.postgresql.Driver jdbctest**
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  > **jdbctest** is the name of a test application.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/5-connecting-to-a-database.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/5-connecting-to-a-database.md
new file mode 100644
index 0000000000000000000000000000000000000000..13682723215a7b23be3444b6d8a47d54bcfd57dd
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/5-connecting-to-a-database.md
@@ -0,0 +1,105 @@
+---
+title: Connecting to a Database
+summary: Connecting to a Database
+author: Guo Huan
+date: 2021-04-26
+---
+
+# Connecting to a Database
+
+After a database is connected, you can use JDBC to run SQL statements to operate data.
+
+**Function Prototype**
+
+JDBC provides the following three database connection methods:
+
+- DriverManager.getConnection(String url);
+- DriverManager.getConnection(String url, Properties info);
+- DriverManager.getConnection(String url, String user, String password);
+
+**Parameters**
+
+**Table 1** Database connection parameters
+
+| Parameter | Description                                                  |
+| --------- | ------------------------------------------------------------ |
+| url       | **postgresql.jar** database connection descriptor. The format is as follows:<br />- jdbc:postgresql:database<br />- jdbc:postgresql://host/database<br />- jdbc:postgresql://host:port/database<br />- jdbc:postgresql://host:port/database?param1=value1&param2=value2<br />- jdbc:postgresql://host1:port1,host2:port2/database?param1=value1&param2=value2<br />NOTE:<br />- **database** indicates the name of the database to connect.<br />- **host** indicates the name or IP address of the database server.<br />If a machine connected to MogDB is not in the same network segment as MogDB, the IP address specified by **host** should be the value of **coo.cooListenIp2** (application access IP address) set in Manager.<br />For security purposes, the primary database node forbids access from other nodes in MogDB without authentication. To access the primary database node from inside MogDB, deploy the JDBC program on the host where the primary database node is located and set **host** to **127.0.0.1**. Otherwise, the error message "FATAL: Forbid remote connection with trust method!" may be displayed.<br />It is recommended that the service system be deployed outside MogDB. If it is deployed inside, database performance may be affected.<br />By default, the local host is used to connect to the server.<br />- **port** indicates the port number of the database server.<br />By default, the database on port 5432 of the local host is connected.<br />- **param** indicates a database connection attribute.<br />The parameter can be configured in the URL. The URL starts with a question mark (?), uses an equal sign (=) to assign a value to the parameter, and uses an ampersand (&) to separate parameters. You can also use the attributes of the **info** object for configuration. For details, see the example below.<br />- **value** indicates the database connection attribute values.<br />The **connectTimeout** and **socketTimeout** parameters must be set for connection. If they are not set, the default value **0** is used, indicating that the connection will not time out. When the network between the DN and client is faulty, the client does not receive the ACK packet from the DN. In this case, the client starts the timeout retransmission mechanism to continuously retransmit packets. A timeout error is reported only when the timeout interval reaches the default value **600s**. As a result, the RTO is high. |
+| info      | Database connection attributes (all attributes are case sensitive). Common attributes are described as follows:<br />- **PGDBNAME**: string type. This parameter specifies the database name. (This parameter does not need to be set in the URL. The system automatically parses the URL to obtain its value.)<br />- **PGHOST**: string type. This parameter specifies the host IP address. For details, see the example below.<br />- **PGPORT**: integer type. This parameter specifies the host port number. For details, see the example below.<br />- **user**: string type. This parameter specifies the database user who creates the connection.<br />- **password**: string type. This parameter specifies the password of the database user.<br />- **enable_ce**: string type. If **enable_ce** is set to **1**, JDBC supports encrypted equality query.<br />- **loggerLevel**: string type. The following log levels are supported:**OFF**, **DEBUG**, and **TRACE**. The value **OFF** indicates that the log function is disabled. **DEBUG** and **TRACE** logs record information of different levels.<br />- **loggerFile**: string type. This parameter specifies the name of a log file. You can specify a directory for storing logs. If no directory is specified, logs are stored in the directory where the client program is running.<br />- **allowEncodingChanges**: Boolean type. If this parameter is set to **true**, the character set type can be changed. This parameter is used together with **characterEncoding=CHARSET** to set the character set. The two parameters are separated by ampersands (&). The value of **characterEncoding** can be **UTF8**, **GBK**, or **LATIN1**.<br />- **currentSchema**: string type. This parameter specifies the schema to be set in **search-path**.<br />- **hostRecheckSeconds**: integer type. After JDBC attempts to connect to a host, the host status is saved: connection success or connection failure. This status is trusted within the duration specified by **hostRecheckSeconds**. After the duration expires, the status becomes invalid. The default value is 10 seconds.<br />- **ssl**: Boolean type. This parameter specifies a connection in SSL mode. When **ssl** is set to **true**, the NonValidatingFactory channel and certificate mode are supported.<br />1. For the NonValidatingFactory channel, configure the username and password and set **SSL** to **true**.<br />2. In certification mode, configure the client certificate, key, and root certificate, and set **SSL** to **true**.<br />- **sslmode**: string type. This parameter specifies the SSL authentication mode. The value can be **require**, **verify-ca**, or **verify-full**.<br />- **require**: The system attempts to set up an SSL connection. If there is a CA file, the system performs verification as if the parameter was set to **verify-ca**.<br />- **verify-ca**: The system attempts to set up an SSL connection and checks whether the server certificate is issued by a trusted CA.<br />- **verify-full**: The system attempts to set up an SSL connection, checks whether the server certificate is issued by a trusted CA, and checks whether the host name of the server is the same as that in the certificate.<br />- **sslcert**: string type. This parameter specifies the complete path of the certificate file. The type of the client and server certificates is **End Entity**.<br />- **sslkey**: string type. This parameter specifies the complete path of the key file. You must run the following command to convert the client certificate to the DER format:<br />`openssl pkcs8 -topk8 -outform DER -in client.key -out client.key.pk8 -nocrypt`<br />- **sslrootcert**: string type. This parameter specifies the name of the SSL root certificate. The root certificate type is CA.<br />- **sslpassword**: string type. This parameter is provided for ConsoleCallbackHandler.<br />- **sslpasswordcallback**: string type. This parameter specifies the class name of the SSL password provider. The default value is **org.postgresql.ssl.jdbc4.LibPQFactory.ConsoleCallbackHandler**.<br />- **sslfactory**: string type. This parameter specifies the class name used by SSLSocketFactory to establish an SSL connection.<br />- **sslfactoryarg**: string type. The value is an optional parameter of the constructor function of the **sslfactory** class and is not recommended.<br />- **sslhostnameverifier**: string type. This parameter specifies the class name of the host name verifier. The interface must implement javax.net.ssl.HostnameVerifier. The default value is **org.postgresql.ssl.PGjdbcHostnameVerifier**.<br />- **loginTimeout**: integer type. This parameter specifies the waiting time for establishing the database connection, in seconds.**connectTimeout**: integer type. This parameter specifies the timeout duration for connecting to a server, in seconds. If the time taken to connect to a server exceeds the value specified, the connection is interrupted. If the value is **0**, the timeout mechanism is disabled.<br />- **socketTimeout**: integer type. This parameter specifies the timeout duration for a socket read operation, in seconds. If the time taken to read data from a server exceeds the value specified, the connection is closed. If the value is **0**, the timeout mechanism is disabled.<br />- **cancelSignalTimeout**: integer type. Cancel messages may cause a block. This parameter controls **connectTimeout** and **socketTimeout** in a cancel message, in seconds. The default value is 10 seconds.<br />- **tcpKeepAlive**: Boolean type. This parameter is used to enable or disable TCP keepalive detection. The default value is **false**.<br />- **logUnclosedConnections**: Boolean type. The client may leak a connection object because it does not call the connection object's close() method. These objects will be collected as garbage and finalized using the finalize() method. If the caller ignores this operation, this method closes the connection.<br />- **assumeMinServerVersion**: string type. The client sends a request to set a floating point. This parameter specifies the version of the server to connect, for example, **assumeMinServerVersion=9.0**. This parameter can reduce the number of packets to send during connection setup.<br />- **ApplicationName**: string type. This parameter specifies the name of the JDBC driver that is being connected. You can query the **pg_stat_activity** table on the primary database node to view information about the client that is being connected. The JDBC driver name is displayed in the **application_name** column. The default value is **PostgreSQL JDBC Driver**.<br />- **connectionExtraInfo**: Boolean type. This parameter specifies whether the JDBC driver reports the driver deployment path and process owner to the database.The value can be **true** or **false**. The default value is **false**. If **connectionExtraInfo** is set to **true**, the JDBC driver reports the driver deployment path and process owner, and URL connection configuration information to the database and displays the information in the **connection_info** parameter. In this case, you can query the information from **PG_STAT_ACTIVITY**.<br />- **autosave**: string type. The value can be **always**, **never**, or **conservative**. The default value is **never**. This parameter specifies the action that the driver should perform upon a query failure. If **autosave** is set to **always**, the JDBC driver sets a savepoint before each query and rolls back to the savepoint if the query fails. If **autosave** is set to **never**, there is no savepoint. If **autosave** is set to **conservative**, a savepoint is set for each query. However, the system rolls back and retries only when there is an invalid statement.<br />- **protocolVersion**: integer type. This parameter specifies the connection protocol version. Only version 3 is supported. Note: MD5 encryption is used when this parameter is set. You must use the following command to change the database encryption mode:**gs_guc set -N all -I all -c "password_encryption_type=1"**. After MogDB is restarted, create a user that uses MD5 encryption to encrypt passwords. You must also change the client connection mode to **md5** in the **pg_hba.conf** file. Log in as the new user (not recommended).<br />NOTE:<br />The MD5 encryption algorithm has lower security and poses security risks. Therefore, you are advised to use a more secure encryption algorithm.<br />- **prepareThreshold**: integer type. This parameter specifies the time when the parse statement is sent. The default value is **5**. It takes a long time to parse an SQL statement for the first time, but a short time to parse SQL statements later because of cache. If a session runs an SQL statement multiple consecutive times and the number of execution times exceeds the value of **prepareThreshold**, JDBC does not send the parse command to the SQL statement.<br />- **preparedStatementCacheQueries**: integer type. This parameter specifies the number of queries cached in each connection. The default value is **256**. If more than 256 different queries are used in the prepareStatement() call, the least recently used query cache will be discarded. The value **0** indicates that the cache function is disabled.<br />- **preparedStatementCacheSizeMiB**: integer type. This parameter specifies the maximum cache size of each connection, in MB. The default value is **5**. If the size of the cached queries exceeds 5 MB, the least recently used query cache will be discarded. The value **0** indicates that the cache function is disabled.<br />- **databaseMetadataCacheFields**: integer type. The default value is **65536**. This parameter specifies the maximum cache size of each connection. The value **0** indicates that the cache function is disabled.<br />- **databaseMetadataCacheFieldsMiB**: integer type. The default value is **5**. This parameter specifies the maximum cache size of each connection, in MB. The value **0** indicates that the cache function is disabled.<br />- **stringtype**: string type. The value can be **false**, **unspecified**, or **varchar**. The default value is **varchar**. This parameter specifies the type of the **PreparedStatement** parameter used by the setString() method. If **stringtype** is set to **varchar**, these parameters are sent to the server as varchar parameters. If **stringtype** is set to **unspecified**, these parameters are sent to the server as an untyped value, and the server attempts to infer their appropriate type.<br />- **batchMode**: Boolean type. This parameter specifies whether to connect the database in batch mode. The default value is **on**, indicating that the batch mode is enabled.<br />- **fetchsize**: integer type. This parameter specifies the default fetchsize for statements in the created connection. The default value is **0**, indicating that all results are obtained at a time.<br />- **reWriteBatchedInserts**: Boolean type. During batch import, set this parameter to **true** to combine **N** insertion statements into one: insert into TABLE_NAME values(values1, …, valuesN), …, (values1, …, valuesN). To use this parameter, set **batchMode** to **off**.<br />- **unknownLength**: integer type. The default value is **Integer.MAX\_VALUE**. This parameter specifies the length of the unknown length type when the data of some postgresql types (such as TEXT) is returned by functions such as ResultSetMetaData.getColumnDisplaySize and ResultSetMetaData.getPrecision.<br />- **defaultRowFetchSize**: integer type. This parameter specifies the number of rows read by fetch in ResultSet at a time. Limiting the number of rows read each time in a database access request can avoid unnecessary memory consumption, thereby avoiding out of memory exception. The default value is **0**, indicating that all rows are obtained at a time in ResultSet. There is no negative value.<br />- **binaryTransfer**: Boolean type. This parameter specifies whether data is sent and received in binary format. The default value is **false**.<br />- **binaryTransferEnable**: string type. This parameter specifies the type for which binary transmission is enabled. Every two types are separated by commas (,). You can select either the OID or name, for example, binaryTransferEnable=Integer4_ARRAY,Integer8_ARRAY. <br />For example, if the OID name is **BLOB** and the OID number is 88, you can configure the OID as follows: <br />**binaryTransferEnable=BLOB or binaryTransferEnable=88**<br />- **binaryTransferDisEnable**: string type. This parameter specifies the type for which binary transmission is disabled. Every two types are separated by commas (,). You can select either the OID or name. The value of this parameter overwrites the value of **binaryTransferEnable**.<br />- **blobMode**: string type. This parameter sets the setBinaryStream method to assign values to different types of data. The value **on** indicates that values are assigned to blob data. The value **off** indicates that values are assigned to bytea data. The default value is **on**.<br />- **socketFactory**: string type. This parameter specifies the name of the class used to create a socket connection with the server. This class must implement the **javax.net.SocketFactory** interface and define a constructor with no parameter or a single string parameter.<br />- **socketFactoryArg**: string type. The value is an optional parameter of the constructor function of the socketFactory class and is not recommended.<br />- **receiveBufferSize**: integer type. This parameter is used to set **SO\_RCVBUF** on the connection stream.<br />- **sendBufferSize**: integer type. This parameter is used to set **SO\_SNDBUF** on the connection stream.<br />- **preferQueryMode**: string type. The value can be **extended**, **extendedForPrepared**, **extendedCacheEverything**, or **simple**. This parameter specifies the query mode. In **simple** mode, the query is executed without parsing or binding. In **extended** mode, the query is executed and bound. The **extendedForPrepared** mode is used for prepared statement extension. In **extendedCacheEverything** mode, each statement is cached.<br />- **targetServerType**: string type. The difference between primary DN and standby DN is whether the DN allows the write operation in the URL connection string. The default value is **any**. The value can be **any**, **master**, **slave**, or **preferSlave**.<br />  - **master**: attempts to connect to a primary DN in the URL connection string. If the primary DN cannot be found, an exception is thrown.<br />  - **slave**: attempts to connect to a standby DN in the URL connection string. If the primary DN cannot be found, an exception is thrown.  <br />  - **preferSlave** attempts to connect to a standby DN (if available) in the URL connection string. Otherwise, it connects to the primary DN.<br />  - **any** attempts to connect to any DN in the URL connection string.<br />- **priorityServers**: integer type. This value is used to specify the first **n** nodes configured in the URL as the primary database instance to be connected preferentially. The default value is **null**. The value is a number greater than 0 and less than the number of DNs configured in the URL.<br />For example, jdbc:postgresql://host1:port1,host2:port2,host3:port3,host4:port4,/database?priorityServers=2. That is, **host1** and **host2** are primary database instance nodes, and **host3** and **host4** are DR database instance nodes.<br />- **forceTargetServerSlave**: Boolean type. This parameter specifies whether to enable the function of forcibly connecting to the standby node and forbid the existing connections to be used on the standby node that is promoted to primary during the primary/standby switchover of the database instance. The default value is **false**, indicating that the function of forcibly connecting to the standby node is disabled. **true**: The function of forcibly connecting to the standby node is enabled. |
+| user      | Database user.                                               |
+| password  | Password of the database user.                               |
+
+**Examples**
+
+```java
+// The following code encapsulates database connection operations into an interface. The database can then be connected using an authorized username and a password.
+public static Connection getConnect(String username, String passwd)
+    {
+        // Driver class.
+        String driver = "org.postgresql.Driver";
+        // Database connection descriptor.
+        String sourceURL = "jdbc:postgresql://10.10.0.13:8000/postgres";
+        Connection conn = null;
+
+        try
+        {
+            // Load the driver.
+            Class.forName(driver);
+        }
+        catch( Exception e )
+        {
+            e.printStackTrace();
+            return null;
+        }
+
+        try
+        {
+             // Create a connection.
+            conn = DriverManager.getConnection(sourceURL, username, passwd);
+            System.out.println("Connection succeed!");
+        }
+        catch(Exception e)
+        {
+            e.printStackTrace();
+            return null;
+        }
+
+        return conn;
+    };
+// The following code uses the Properties object as a parameter to establish a connection.
+public static Connection getConnectUseProp(String username, String passwd)
+    {
+        // Driver class.
+        String driver = "org.postgresql.Driver";
+        // Database connection descriptor.
+        String sourceURL = "jdbc:postgresql://10.10.0.13:8000/postgres?";
+        Connection conn = null;
+        Properties info = new Properties();
+
+        try
+        {
+            // Load the driver.
+            Class.forName(driver);
+        }
+        catch( Exception e )
+        {
+            e.printStackTrace();
+            return null;
+        }
+
+        try
+        {
+             info.setProperty("user", username);
+             info.setProperty("password", passwd);
+             // Create a connection.
+             conn = DriverManager.getConnection(sourceURL, info);
+             System.out.println("Connection succeed!");
+        }
+        catch(Exception e)
+        {
+            e.printStackTrace();
+            return null;
+        }
+
+        return conn;
+    };
+```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/6-connecting-to-a-database-using-ssl.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/6-connecting-to-a-database-using-ssl.md
new file mode 100644
index 0000000000000000000000000000000000000000..9351b393ecb9d139cd4c5a7de9a73391d1fe27a4
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/6-connecting-to-a-database-using-ssl.md
@@ -0,0 +1,147 @@
+---
+title: Connecting to the Database (Using SSL)
+summary: Connecting to the Database (Using SSL)
+author: Guo Huan
+date: 2021-04-26
+---
+
+# Connecting to the Database (Using SSL)
+
+When establishing connections to the MogDB server using JDBC, you can enable SSL connections to encrypt client and server communications for security of sensitive data transmission on the Internet. This section describes how applications establish an SSL connection to MogDB using JDBC. To start the SSL mode, you must have the server certificate, client certificate, and private key files. For details on how to obtain these files, see related documents and commands of OpenSSL.
+
+**Configuring the Server**
+
+The SSL mode requires a root certificate, a server certificate, and a private key.
+
+Perform the following operations (assuming that the license files are saved in the data directory **/mogdb/data/datanode** and the default file names are used):
+
+1. Log in as the OS user **omm** to the primary node of the database.
+
+2. Generate and import a certificate.
+
+   Generate an SSL certificate. For details, see **Generating Certificates**. Copy the generated **server.crt**, **server.key**, and **cacert.pem** files to the data directory on the server.
+
+   Run the following command to query the data directory of the database node. The instance column indicates the data directory.
+
+   ```bash
+   gs_om -t status --detail
+   ```
+
+   In the Unix OS, **server.crt** and **server.key** must deny the access from the external or any group. Run the following command to set this permission:
+
+   ```bash
+   chmod 0600 server.key
+   ```
+
+3. Enable the SSL authentication mode.
+
+   ```bash
+   gs_guc set -D /mogdb/data/datanode -c "ssl=on"
+   ```
+
+4. Set client access authentication parameters. The IP address is the IP address of the host to be connected.
+
+   ```bash
+   gs_guc reload -D /mogdb/data/datanode -h "hostssl all             all             127.0.0.1/32           cert"
+   gs_guc reload -D /mogdb/data/datanode -h "hostssl all             all             IP/32           cert"
+   ```
+
+   Clients on the **127.0.0.1⁄32** network segment can connect to MogDB servers in SSL mode.
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+   >
+   > - If **METHOD** is set to **cert** in the **pg_hba.conf** file of the server, the client must use the username (common name) configured in the license file (**client.crt**) for the database connection. If **METHOD** is set to **md5**, **sm3** or **sha256**, there is no such a restriction.
+   > - The MD5 encryption algorithm has lower security and poses security risks. Therefore, you are advised to use a more secure encryption algorithm.
+
+5. Configure the digital certificate parameters related to SSL authentication.
+
+   The information following each command indicates operation success.
+
+   ```bash
+   gs_guc set -D /mogdb/data/datanode -c "ssl_cert_file='server.crt'"
+   gs_guc set: ssl_cert_file='server.crt'
+   ```
+
+   ```bash
+   gs_guc set -D /mogdb/data/datanode -c "ssl_key_file='server.key'"
+   gs_guc set: ssl_key_file='server.key'
+   ```
+
+   ```bash
+   gs_guc set -D /mogdb/data/datanode -c "ssl_ca_file='cacert.pem'"
+   gs_guc set: ssl_ca_file='cacert.pem'
+   ```
+
+6. Restart the database.
+
+   ```bash
+   gs_om -t stop && gs_om -t start
+   ```
+
+7. Generate and upload a certificate file.
+
+**Configuring the Client**
+
+To configure the client, perform the following steps:
+
+Upload the certificate files **client.key.pk8**, **client.crt**, and **cacert.pem** generated in **Configuring the Server** to the client.
+
+**Example**
+
+Note: Choose one of example 1 and example 2.
+
+```java
+import java.sql.Connection;
+import java.util.Properties;
+import java.sql.DriverManager;
+import java.sql.Statement;
+import java.sql.ResultSet;
+
+public class SSL{
+    public static void main(String[] args) {
+        Properties urlProps = new Properties();
+        String urls = "jdbc:postgresql://10.29.37.136:8000/postgres";
+
+        /**
+* ================== Example 1: The NonValidatingFactory channel is used, and MTETHOD in the pg_hba.conf file is not cert.
+         */
+/*
+        urlProps.setProperty("sslfactory","org.postgresql.ssl.NonValidatingFactory");
+        urlProps.setProperty("user", "world");
+//test@123 is the password specified when user CREATE USER world WITH PASSWORD 'test123@' is created.
+        urlProps.setProperty("password", "test@123");
+        urlProps.setProperty("ssl", "true");
+*/
+        /**
+* ================== Example 2 - 5: Use a certificate. In the pg_hba.conf file, MTETHOD is cert.
+         */
+        urlProps.setProperty("sslcert", "client.crt");
+// Client key in DER format
+        urlProps.setProperty("sslkey", "client.key.pk8");
+        urlProps.setProperty("sslrootcert", "cacert.pem");
+        urlProps.setProperty("user", "world");
+       /* ================== Example 2: Set ssl to true to use the certificate for authentication.*/
+        urlProps.setProperty("ssl", "true");
+       /* ================== Example 3: Set sslmode to require to use the certificate for authentication. */
+//        urlProps.setProperty("sslmode", "require");
+       /* ================== Example 4: Set sslmode to verify-ca to use the certificate for authentication. */
+//        urlProps.setProperty("sslmode", "verify-ca");
+       /* ================== Example 5: Set sslmode to verify-full to use the certificate (in the Linux OS) for authentication. */
+//        urls = "jdbc:postgresql://world:8000/postgres";
+//        urlProps.setProperty("sslmode", "verify-full");
+
+        try {
+            Class.forName("org.postgresql.Driver").newInstance();
+        } catch (Exception e) {
+            e.printStackTrace();
+        }
+        try {
+            Connection conn;
+            conn = DriverManager.getConnection(urls,urlProps);
+            conn.close();
+        } catch (Exception e) {
+            e.printStackTrace();
+        }
+    }
+}
+```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/7-running-sql-statements.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/7-running-sql-statements.md
new file mode 100644
index 0000000000000000000000000000000000000000..0a8b3f94ea82bc33dda7b00c878b03c3360d2eee
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/7-running-sql-statements.md
@@ -0,0 +1,166 @@
+---
+title: Running SQL Statements
+summary: Running SQL Statements
+author: Guo Huan
+date: 2021-04-26
+---
+
+# Running SQL Statements
+
+**Running a Common SQL Statement**
+
+To enable an application to operate data in the database by running SQL statements (statements that do not need to transfer parameters), perform the following operations:
+
+1. Create a statement object by calling the **createStatement** method in **Connection**.
+
+   ```bash
+   Connection conn = DriverManager.getConnection("url","user","password");
+   Statement stmt = conn.createStatement();
+   ```
+
+2. Run the SQL statement by calling the **executeUpdate** method in **Statement**.
+
+   ```bash
+   int rc = stmt.executeUpdate("CREATE TABLE customer_t1(c_customer_sk INTEGER, c_customer_name VARCHAR(32));");
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+   > If an execution request (not in a transaction block) received in the database contains multiple statements, the request is packed into a transaction. **VACUUM** is not supported in a transaction block. If one of the statements fails, the entire request will be rolled back.
+
+3. Close the statement object.
+
+   ```
+   stmt.close();
+   ```
+
+**Running a Prepared SQL Statement**
+
+Prepared statements are complied and optimized once but can be used in different scenarios by assigning multiple values. Using prepared statements improves execution efficiency. If you want to run a statement for several times, use a precompiled statement. Perform the following operations:
+
+1. Create a prepared statement object by calling the prepareStatement method in Connection.
+
+   ```json
+   PreparedStatement pstmt = con.prepareStatement("UPDATE customer_t1 SET c_customer_name = ? WHERE c_customer_sk = 1");
+   ```
+
+2. Set parameters by calling the setShort method in PreparedStatement.
+
+   ```json
+   pstmt.setShort(1, (short)2);
+   ```
+
+3. Run the prepared statement by calling the executeUpdate method in PreparedStatement.
+
+   ```json
+   int rowcount = pstmt.executeUpdate();
+   ```
+
+4. Close the prepared statement object by calling the close method in PreparedStatement.
+
+   ```json
+   pstmt.close();
+   ```
+
+**Calling a Stored Procedure**
+
+To call an existing stored procedure through JDBC in MogDB, perform the following operations:
+
+1. Create a call statement object by calling the **prepareCall** method in **Connection**.
+
+   ```bash
+   Connection myConn = DriverManager.getConnection("url","user","password");
+   CallableStatement cstmt = myConn.prepareCall("{? = CALL TESTPROC(?,?,?)}");
+   ```
+
+2. Set parameters by calling the **setInt** method in **CallableStatement**.
+
+   ```
+   cstmt.setInt(2, 50);
+   cstmt.setInt(1, 20);
+   cstmt.setInt(3, 90);
+   ```
+
+3. Register an output parameter by calling the **registerOutParameter** method in **CallableStatement**.
+
+   ```
+   cstmt.registerOutParameter(4, Types.INTEGER);  // Register an OUT parameter of the integer type.
+   ```
+
+4. Call the stored procedure by calling the **execute** method in **CallableStatement**.
+
+   ```
+   cstmt.execute();
+   ```
+
+5. Obtain the output parameter by calling the **getInt** method in **CallableStatement**.
+
+   ```
+   int out = cstmt.getInt(4);  // Obtain the OUT parameter.
+   ```
+
+   Example:
+
+   ```
+   // The following stored procedure (containing the OUT parameter) has been created:
+   create or replace procedure testproc
+   (
+       psv_in1 in integer,
+       psv_in2 in integer,
+       psv_inout in out integer
+   )
+   as
+   begin
+       psv_inout := psv_in1 + psv_in2 + psv_inout;
+   end;
+   /
+   ```
+
+6. Close the call statement by calling the **close** method in **CallableStatement**.
+
+   ```
+   cstmt.close();
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+   >
+   > - Many database classes such as Connection, Statement, and ResultSet have a close() method. Close these classes after using their objects. Closing Connection will close all the related Statements, and closing a Statement will close its ResultSet.
+   > - Some JDBC drivers support named parameters, which can be used to set parameters by name rather than sequence. If a parameter has the default value, you do not need to specify any parameter value but can use the default value directly. Even though the parameter sequence changes during a stored procedure, the application does not need to be modified. Currently, the MogDB JDBC driver does not support this method.
+   > - MogDB does not support functions containing OUT parameters, or stored procedures and function parameters containing default values.
+   >
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE**:
+   >
+   > - If JDBC is used to call a stored procedure whose returned value is a cursor, the returned cursor cannot be used.
+   > - A stored procedure and an SQL statement must be run separately.
+
+**Batch Processing**
+
+When a prepared statement processes multiple pieces of similar data, the database creates only one execution plan. This improves compilation and optimization efficiency. Perform the following operations:
+
+1. Create a prepared statement object by calling the prepareStatement method in Connection.
+
+   ```
+   Connection conn = DriverManager.getConnection("url","user","password");
+   PreparedStatement pstmt = conn.prepareStatement("INSERT INTO customer_t1 VALUES (?)");
+   ```
+
+2. Call the setShort parameter for each piece of data, and call addBatch to confirm that the setting is complete.
+
+   ```
+   pstmt.setShort(1, (short)2);
+   pstmt.addBatch();
+   ```
+
+3. Perform batch processing by calling the executeBatch method in PreparedStatement.
+
+   ```
+   int[] rowcount = pstmt.executeBatch();
+   ```
+
+4. Close the prepared statement object by calling the close method in PreparedStatement.
+
+   ```
+   pstmt.close();
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+   > Do not terminate a batch processing action when it is ongoing; otherwise, database performance will deteriorate. Therefore, disable automatic commit during batch processing. Manually commit several rows at a time. The statement for disabling automatic commit is **conn.setAutoCommit(false);**.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/8-processing-data-in-a-result-set.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/8-processing-data-in-a-result-set.md
new file mode 100644
index 0000000000000000000000000000000000000000..d45f9df5ee3e1d155fa4e5f44a1b70f2c2a59cb2
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/8-processing-data-in-a-result-set.md
@@ -0,0 +1,76 @@
+---
+title: Processing Data in a Result Set
+summary: Processing Data in a Result Set
+author: Guo Huan
+date: 2021-04-26
+---
+
+# Processing Data in a Result Set
+
+**Setting a Result Set Type**
+
+Different types of result sets apply to different application scenarios. Applications select proper types of result sets based on requirements. Before running an SQL statement, you must create a statement object. Some methods of creating statement objects can set the type of a result set. [Table 1](#Result set types) lists result set parameters. The related Connection methods are as follows:
+
+```
+// Create a Statement object. This object will generate a ResultSet object with a specified type and concurrency.
+createStatement(int resultSetType, int resultSetConcurrency);
+
+// Create a PreparedStatement object. This object will generate a ResultSet object with a specified type and concurrency.
+prepareStatement(String sql, int resultSetType, int resultSetConcurrency);
+
+// Create a CallableStatement object. This object will generate a ResultSet object with a specified type and concurrency.
+prepareCall(String sql, int resultSetType, int resultSetConcurrency);
+```
+
+<a id="Result set types">**Table 1**</a> Result set types
+
+| Parameter            | Description                                                  |
+| :------------------- | :----------------------------------------------------------- |
+| resultSetType        | Type of a result set. There are three types of result sets:<br />- **ResultSet.TYPE_FORWARD_ONLY**: The ResultSet object can only be navigated forward. It is the default value.<br />- **ResultSet.TYPE_SCROLL_SENSITIVE**: You can view the modified result by scrolling to the modified row.<br />- **ResultSet.TYPE_SCROLL_INSENSITIVE**: The ResultSet object is insensitive to changes in the underlying data source.<br />NOTE:<br />After a result set has obtained data from the database, the result set is insensitive to data changes made by other transactions, even if the result set type is **ResultSet.TYPE_SCROLL_SENSITIVE**. To obtain up-to-date data of the record pointed by the cursor from the database, call the refreshRow() method in a ResultSet object. |
+| resultSetConcurrency | Concurrency type of a result set. There are two types of concurrency.<br />- **ResultSet.CONCUR_READ_ONLY**: Data in a result set cannot be updated except that an updated statement has been created in the result set data.<br />- **ResultSet.CONCUR_UPDATEABLE**: changeable result set. The concurrency type for a result set object can be updated if the result set is scrollable. |
+
+**Positioning a Cursor in a Result Set**
+
+ResultSet objects include a cursor pointing to the current data row. The cursor is initially positioned before the first row. The next method moves the cursor to the next row from its current position. When a ResultSet object does not have a next row, a call to the next method returns **false**. Therefore, this method is used in the while loop for result set iteration. However, the JDBC driver provides more cursor positioning methods for scrollable result sets, which allows positioning cursor in the specified row. [Table 2](#Methods for positioning) describes these methods.
+
+<a id="Methods for positioning">**Table 2**</a> Methods for positioning a cursor in a result set
+
+| Method        | Description                                                  |
+| :------------ | :----------------------------------------------------------- |
+| next()        | Moves cursor to the next row from its current position.      |
+| previous()    | Moves cursor to the previous row from its current position.  |
+| beforeFirst() | Places cursor before the first row.                          |
+| afterLast()   | Places cursor after the last row.                            |
+| first()       | Places cursor to the first row.                              |
+| last()        | Places cursor to the last row.                               |
+| absolute(int) | Places cursor to a specified row.                            |
+| relative(int) | Moves the row specified by the forward parameter (that is, the value of is 1, which is equivalent to next()) or backward (that is, the value of is -1, which is equivalent to previous()). |
+
+**Obtaining the Cursor Position from a Result Set**
+
+This cursor positioning method will be used to change the cursor position for a scrollable result set. The JDBC driver provides a method to obtain the cursor position in a result set. [Table 3](#Methods for obtaining) describes these methods.
+
+<a id="Methods for obtaining">**Table 3**</a> Methods for obtaining a cursor position in a result set
+
+| Method          | Description                                        |
+| :-------------- | :------------------------------------------------- |
+| isFirst()       | Checks whether the cursor is in the first row.     |
+| isLast()        | Checks whether the cursor is in the last row.      |
+| isBeforeFirst() | Checks whether the cursor is before the first row. |
+| isAfterLast()   | Checks whether the cursor is after the last row.   |
+| getRow()        | Gets the current row number of the cursor.         |
+
+**Obtaining Data from a Result Set**
+
+ResultSet objects provide a variety of methods to obtain data from a result set. [Table 4](#Common methods for obtaining) describes the common methods for obtaining data. If you want to know more about other methods, see JDK official documents.
+
+<a id="Common methods for obtaining">**Table 4** </a>Common methods for obtaining data from a result set
+
+| Method                               | Description                                                  |
+| :----------------------------------- | :----------------------------------------------------------- |
+| int getInt(int columnIndex)          | Retrieves the value of the column designated by a column index in the current row as an integer. |
+| int getInt(String columnLabel)       | Retrieves the value of the column designated by a column label in the current row as an integer. |
+| String getString(int columnIndex)    | Retrieves the value of the column designated by a column index in the current row as a string. |
+| String getString(String columnLabel) | Retrieves the value of the column designated by a column label in the current row as a string. |
+| Date getDate(int columnIndex)        | Retrieves the value of the column designated by a column index in the current row as a date. |
+| Date getDate(String columnLabel)     | Retrieves the value of the column designated by a column name in the current row as a date. |
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/8.1-log-management.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/8.1-log-management.md
new file mode 100644
index 0000000000000000000000000000000000000000..478aa24053789831a28064b2620f81ca9e278f39
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/8.1-log-management.md
@@ -0,0 +1,142 @@
+---
+title: Log Management
+summary: Log Management
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# Log Management
+
+The MogDB JDBC driver uses log records to help solve problems when the MogDB JDBC driver is used in applications. MogDB JDBC supports the following log management methods:
+
+1. Use the connection properties to specify a temporary log file.
+2. Use the SLF4J log framework for interconnecting with applications.
+3. Use the JdkLogger log framework for interconnecting with applications.
+
+SLF4J and JdkLogger are mainstream frameworks for Java application log management in the industry. For details about how to use these frameworks, see the official documents (SLF4J: <http://www.slf4j.org/manual.html>; JdkLogger: <https://docs.oracle.com/javase/8/docs/technotes/guides/logging/overview.html>).
+
+Method 1: Use the connection attribute.
+
+Configure loggerLevel and loggerFile in the URL.
+
+This method is easy to configure and applies to the debug driver. However, the log level, file size, and file quantity cannot be controlled. If logs are not manually processed in a timely manner, the disk space will be used up. Therefore, this method is not recommended except for the debug driver.
+
+Example:
+
+```
+public static Connection GetConnection(String username, String passwd){
+
+    String sourceURL = "jdbc:postgresql://10.10.0.13:8000/postgres?loggerLevel=DEBUG&loggerFile=gsjdbc.log";
+    Connection conn = null;
+
+    try{
+// Create a connection.
+        conn = DriverManager.getConnection(sourceURL,username,passwd);
+        System.out.println("Connection succeed!");
+    }catch (Exception e){
+        e.printStackTrace();
+        return null;
+    }
+    return conn;
+}
+```
+
+Method 2: Use the SLF4J log framework for interconnecting with applications.
+
+When a connection is set up, **logger=Slf4JLogger** is configured in the URL.
+
+The SLF4J may be implemented by using Log4j or Log4j2. When the Log4j is used to implement the SLF4J, the following JAR packages need to be added: **log4j-\*.jar**, **slf4j-api-\*.jar**, and **slf4j-log4\*-\*.jar** (*varies according to versions), and configuration file **log4j.properties**. If the Log4j2 is used to implement the SLF4J, you need to add the following JAR packages: **log4j-api-\*.jar**, **log4j-core-\*.jar**, **log4j-slf4j18-impl-\*.jar**, and **slf4j-api-\*-alpha1.jar** (* varies according to versions), and configuration file **log4j2.xml**.
+
+This method supports log management and control. The SLF4J can implement powerful log management and control functions through related configurations in files. This method is recommended.
+
+Example:
+
+```
+public static Connection GetConnection(String username, String passwd){
+
+    String sourceURL = "jdbc:postgresql://10.10.0.13:8000/postgres?logger=Slf4JLogger";
+    Connection conn = null;
+
+    try{
+// Create a connection.
+        conn = DriverManager.getConnection(sourceURL,username,passwd);
+        System.out.println("Connection succeed!");
+    }catch (Exception e){
+        e.printStackTrace();
+        return null;
+    }
+    return conn;
+}
+```
+
+The following is an example of the **log4j.properties** file:
+
+```
+log4j.logger.org.postgresql=ALL, log_gsjdbc
+
+# Default file output configuration
+log4j.appender.log_gsjdbc=org.apache.log4j.RollingFileAppender
+log4j.appender.log_gsjdbc.Append=true
+log4j.appender.log_gsjdbc.File=gsjdbc.log
+log4j.appender.log_gsjdbc.Threshold=TRACE
+log4j.appender.log_gsjdbc.MaxFileSize=10MB
+log4j.appender.log_gsjdbc.MaxBackupIndex=5
+log4j.appender.log_gsjdbc.layout=org.apache.log4j.PatternLayout
+log4j.appender.log_gsjdbc.layout.ConversionPattern=%d %p %t %c - %m%n
+log4j.appender.log_gsjdbc.File.Encoding = UTF-8
+```
+
+The following is an example of the **log4j2.xml** file:
+
+```
+<?xml version="1.0" encoding="UTF-8"?>
+<configuration status="OFF">
+    <appenders>
+        <Console name="Console" target="SYSTEM_OUT">
+            <PatternLayout pattern="%d %p %t %c - %m%n"/>
+        </Console>
+        <File name="FileTest" fileName="test.log">
+            <PatternLayout pattern="%d %p %t %c - %m%n"/>
+        </File>
+        <!-- JDBC driver log file output configuration. Log rewinding is supported. When the log size exceeds 10 MB, a new file is created. The new file is named in the format of yyyy-mm-dd-file ID. -->
+        <RollingFile name="RollingFileJdbc" fileName="gsjdbc.log" filePattern="%d{yyyy-MM-dd}-%i.log">
+            <PatternLayout pattern="%d %p %t %c - %m%n"/>
+            <Policies>
+                <SizeBasedTriggeringPolicy size="10 MB"/>
+            </Policies>
+        </RollingFile>
+    </appenders>
+    <loggers>
+        <root level="all">
+            <appender-ref ref="Console"/>
+            <appender-ref ref="FileTest"/>
+        </root>
+        <!-- JDBC driver logs. The log level is all. All logs can be viewed and exported to the gsjdbc.log file. -->
+        <logger name="org.postgresql" level="all" additivity="false">
+            <appender-ref ref="RollingFileJdbc"/>
+        </logger>
+    </loggers>
+</configuration>
+```
+
+Method 3: Use the JdkLogger log framework for interconnecting with applications.
+
+The default Java logging framework stores its configurations in a file named **logging.properties**. Java installs the global configuration file in the folder in the Java installation directory. The **logging.properties** file can also be created and stored with a single project.
+
+Configuration example of **logging.properties**:
+
+```
+# Specify the processing program as a file.
+handlers= java.util.logging.FileHandler
+
+# Specify the default global log level.
+.level= ALL
+
+# Specify the log output control standard.
+java.util.logging.FileHandler.level=ALL
+java.util.logging.FileHandler.pattern = gsjdbc.log
+java.util.logging.FileHandler.limit = 500000
+java.util.logging.FileHandler.count = 30
+java.util.logging.FileHandler.formatter = java.util.logging.SimpleFormatter
+java.util.logging.FileHandler.append=false
+```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/9-closing-a-connection.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/9-closing-a-connection.md
new file mode 100644
index 0000000000000000000000000000000000000000..d597422110816a06857459eed3ae85e666b26ad8
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/9-closing-a-connection.md
@@ -0,0 +1,12 @@
+---
+title: Closing a Connection
+summary: Closing a Connection
+author: Guo Huan
+date: 2021-04-26
+---
+
+# Closing a Connection
+
+After you complete required data operations in the database, close the database connection.
+
+Call the close method to close the connection, for example, **Connection conn = DriverManager.getConnection("url","user","password"); conn.close();**
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/1-development-based-on-odbc-overview.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/1-development-based-on-odbc-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..f4a1710b8df4539903ca8fcf0220da9980ffcfdb
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/1-development-based-on-odbc-overview.md
@@ -0,0 +1,34 @@
+---
+title: Overview
+summary: Overview
+author: Guo Huan
+date: 2021-04-26
+---
+
+# Overview
+
+Open Database Connectivity (ODBC) is a Microsoft API for accessing databases based on the X/OPEN CLI. Applications interact with the database through the APIs provided by ODBC, which enhances their portability, scalability, and maintainability.
+
+[Figure 1](#ODBC) shows the system structure of ODBC.
+
+<a id="ODBC">**Figure 1** </a>ODBC system structure
+
+![odbc-system-structure](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/development-based-on-odbc-overview-2.png)
+
+MogDB supports ODBC 3.5 in the following environments.
+
+**Table 1** OSs Supported by ODBC
+
+| OS                                                 | Platform |
+| :------------------------------------------------- | :------- |
+| CentOS 6.4/6.5/6.6/6.7/6.8/6.9/7.0/7.1/7.2/7.3/7.4 | x86_64   |
+| CentOS 7.6                                         | ARM64    |
+| EulerOS 2.0 SP2/SP3                                | x86_64   |
+| EulerOS 2.0 SP8                                    | ARM64    |
+
+The ODBC Driver Manager running on UNIX or Linux can be unixODBC or iODBC. unixODBC-2.3.0 is used as the component for connecting the database.
+
+Windows has a native ODBC Driver Manager. You can locate **Data Sources (ODBC)** by choosing **Control Panel** &gt; **Administrative Tools**.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> The current database ODBC driver is based on an open-source version and may be incompatible with data types tinyint, smalldatetime, and nvarchar2.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/2-odbc-packages-dependent-libraries-and-header-files.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/2-odbc-packages-dependent-libraries-and-header-files.md
new file mode 100644
index 0000000000000000000000000000000000000000..16764e9dddb25c43a26673eda71911a855ee0c1b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/2-odbc-packages-dependent-libraries-and-header-files.md
@@ -0,0 +1,12 @@
+---
+title: ODBC Packages, Dependent Libraries, and Header Files
+summary: ODBC Packages, Dependent Libraries, and Header Files
+author: Guo Huan
+date: 2021-04-26
+---
+
+# ODBC Packages, Dependent Libraries, and Header Files
+
+**ODBC Packages for the Linux OS**
+
+Obtain the [**openGauss-x.x.x-ODBC.tar.gz**](https://opengauss.org/en/download.html) package from the release package. In the Linux OS, header files (including **sql.h** and **sqlext.h**) and library (**libodbc.so**) are required in application development. These header files and library can be obtained from the **unixODBC-2.3.0** installation package.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md
new file mode 100644
index 0000000000000000000000000000000000000000..192d945106107cf9cb8530a6c4e99fad3c5c42d7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md
@@ -0,0 +1,324 @@
+---
+title: Configuring a Data Source in the Linux OS
+summary: Configuring a Data Source in the Linux OS
+author: Guo Huan
+date: 2021-04-26
+---
+
+# Configuring a Data Source in the Linux OS
+
+The ODBC driver (psqlodbcw.so) provided by MogDB can be used after it has been configured in a data source. To configure a data source, you must configure the **odbc.ini** and **odbcinst.ini** files on the server. The two files are generated during the unixODBC compilation and installation, and are saved in the **/usr/local/etc** directory by default.
+
+**Procedure**
+
+1. Obtain the source code package of unixODBC by following link:
+
+   <https://sourceforge.net/projects/unixodbc/files/unixODBC/2.3.7/unixODBC-2.3.7pre.tar.gz/download>
+
+   After the download, validate the integrity based on the integrity validation algorithm provided by the community.
+
+2. Install unixODBC. It does not matter if unixODBC of another version has been installed.
+
+   Currently, unixODBC-2.2.1 is not supported. For example, to install unixODBC-2.3.0, run the commands below. unixODBC is installed in the **/usr/local** directory by default. The data source file is generated in the **/usr/local/etc** directory, and the library file is generated in the **/usr/local/lib** directory.
+
+   ```bash
+   tar zxvf unixODBC-2.3.0.tar.gz
+   cd unixODBC-2.3.0
+   #Modify the configure file. (If it does not exist, modify the configure.ac file.) Find LIB_VERSION.
+   #Change the value of LIB_VERSION to 1:0:0 to compile a *.so.1 dynamic library with the same dependency on psqlodbcw.so.
+   vim configure
+
+   ./configure --enable-gui=no #To perform compilation on a Kunpeng server, add the configure parameter --build=aarch64-unknown-linux-gnu.
+   make
+   #The installation may require root permissions.
+   make install
+   ```
+
+3. Replace the openGauss driver on the client.
+
+   a. Decompress **openGauss-** **1.1.0**-**ODBC.tar.gz** to the **/usr/local/lib** directory. **psqlodbcw.la** and **psqlodbcw.so** files are obtained.
+
+   b. Copy the library in the **lib** directory obtained after decompressing **openGauss**-**1.1.0**-**ODBC.tar.gz** to the **/usr/local/lib** directory.
+
+4. Configure a data source.
+
+   a. Configure the ODBC driver file.
+
+   Add the following content to the **/xxx/odbc/etc/odbcinst.ini** file:
+
+   ```
+   [GaussMPP]
+   Driver64=/xxx/odbc/lib/psqlodbcw.so
+   setup=/xxx/odbc/lib/psqlodbcw.so
+   ```
+
+   For descriptions of the parameters in the **odbcinst.ini** file, see [Table 1](#odbcinst.ini).
+
+   **Table 1** odbcinst.ini configuration parameters<a id="odbcinst.ini"></a>
+
+   | **Parameter** | **Description**                                              | **Example**                         |
+   | ------------- | ------------------------------------------------------------ | ----------------------------------- |
+   | [DriverName]  | Driver name, corresponding to the driver in DSN.             | [DRIVER_N]                          |
+   | Driver64      | Path of the dynamic driver library.                          | Driver64=/xxx/odbc/lib/psqlodbcw.so |
+   | setup         | Driver installation path, which is the same as the dynamic library path in Driver64. | setup=/xxx/odbc/lib/psqlodbcw.so    |
+
+   b. Configure the data source file.
+
+   Add the following content to the **/usr/local/etc/odbc.ini** file:
+
+   ```bash
+   [MPPODBC]
+   Driver=GaussMPP
+   Servername=10.145.130.26 (IP address of the server where the database resides)
+   Database=postgres  (database name)
+   Username=omm  (database username)
+   Password=    (user password of the database)
+   Port=8000 (listening port of the database)
+   Sslmode=allow
+   ```
+
+   For descriptions of the parameters in the **odbc.ini** file, see [Table 2](#odbc.ini).
+
+   **Table 2** odbc.ini configuration parameters<a id="odbc.ini"></a>
+
+   | **Parameter**           | **Description**                                              | **Example**                                                  |
+   | ----------------------- | ------------------------------------------------------------ | ------------------------------------------------------------ |
+   | [DSN]                   | Data source name                                             | [MPPODBC]                                                    |
+   | Driver                  | Driver name, corresponding to DriverName in **odbcinst.ini** | Driver=DRIVER_N                                              |
+   | Servername              | Server IP address                                            | Servername=10.145.130.26                                     |
+   | Database                | Name of the database to connect to                           | Database=postgres                                            |
+   | Username                | Database username                                            | Username=omm                                                 |
+   | Password                | Database user password                                       | Password=<br />NOTE:<br />After a user established a connection, the ODBC driver automatically clears their password stored in memory.<br />However, if this parameter is configured, UnixODBC will cache data source files, which may cause the password to be stored in the memory for a long time.<br />When you connect to an application, you are advised to send your password through an API instead of writing it in a data source configuration file. After the connection has been established, immediately clear the memory segment where your password is stored. |
+   | Port                    | Port number of the server                                    | Port=8000                                                    |
+   | Sslmode                 | Whether to enable SSL                                        | Sslmode=allow                                                |
+   | Debug                   | If this parameter is set to **1**, the **mylog** file of the PostgreSQL ODBC driver will be printed. The directory generated for storing logs is **/tmp/**. If this parameter is set to **0**, no directory is generated. | Debug=1                                                      |
+   | UseServerSidePrepare    | Whether to enable the extended query protocol for the database.<br />The value can be **0** or **1**. The default value is **1**, indicating that the extended query protocol is enabled. | UseServerSidePrepare=1                                       |
+   | UseBatchProtocol        | Whether to enable the batch query protocol. If it is enabled, DML performance can be improved. The value can be **0** or **1**. The default value is **1**.<br />If this parameter is set to **0**, the batch query protocol is disabled (mainly for communication with earlier database versions).<br />If this parameter is set to **1** and **support_batch_bind** is set to **on**, the batch query protocol is enabled. | UseBatchProtocol=1                                           |
+   | ForExtensionConnector   | This parameter specifies whether the savepoint is sent.      | ForExtensionConnector=1                                      |
+   | UnamedPrepStmtThreshold | Each time **SQLFreeHandle** is invoked to release statements, ODBC sends a **Deallocate plan_name** statement to the server. A large number of such a statement exist in the service. To reduce the number of the statements to be sent, **stmt->plan_name** is left empty so that the database can identify them as unnamed statements. This parameter is added to control the threshold for unnamed statements. | UnamedPrepStmtThreshold=100                                  |
+   | ConnectionExtraInfo     | Whether to display the driver deployment path and process owner in the **connection_info** parameter mentioned in **connection_info**. | ConnectionExtraInfo=1NOTE:The default value is **0**. If this parameter is set to **1**, the ODBC driver reports the driver deployment path and process owner to the database and displays the information in the **connection_info** parameter (see **BEGIN**). In this case, you can query the information from PG_STAT_ACTIVITY. |
+   | BoolAsChar              | If this parameter is set to **Yes**, the Boolean value is mapped to the SQL_CHAR type. If this parameter is not set, the value is mapped to the SQL_BIT type. | BoolsAsChar = Yes                                            |
+   | RowVersioning           | When an attempt is made to update a row of data, setting this parameter to **Yes** allows the application to detect whether the data has been modified by other users. | RowVersioning = Yes                                          |
+   | ShowSystemTables        | By default, the driver regards the system table as a common SQL table. | ShowSystemTables = Yes                                       |
+
+   The valid values of **Sslmode** are as follows:
+
+   **Table 3** Sslmode options<a id="sslmode"></a>
+
+   | sslmode     | Whether SSL Encryption Is Enabled | Description                                                  |
+   | ----------- | --------------------------------- | ------------------------------------------------------------ |
+   | disable     | No                                | SSL connection is not enabled.                               |
+   | allow       | Possible                          | If the database server requires SSL connection, SSL connection can be enabled. However, authenticity of the database server will not be verified. |
+   | prefer      | Possible                          | If the database supports SSL connection, SSL connection is recommended. However, authenticity of the database server will not be verified. |
+   | require     | Yes                               | SSL connection is required and data is encrypted. However, authenticity of the database server will not be verified. |
+   | verify-ca   | Yes                               | SSL connection is required and whether the database has a trusted certificate will be verified. |
+   | verify-full | Yes                               | SSL connection is required. In addition to the check scope specified by **verify-ca**, the system checks whether the name of the host where the database resides is the same as that in the certificate. MogDB does not support this mode. |
+
+5. (Optional) Generate an SSL certificate. For details, see **Generating Certificates**.This step and step 6 need to be performed when the server and the client are connected via ssl. It can be skipped in case of non-ssl connection.
+
+6. (Optional) Replace an SSL certificate. For details, see **Replacing Certificates**.
+
+7. SSL mode:
+
+   ```
+   Return to the root directory, create the .postgresql directory, and put root.crt, client.crt, client.key, client.key.cipher, client.key.rand, client.req, server.crt, server.key, server.key.cipher, server.key.rand, and server.req in the directory.
+   Copy root.crt and related certificate files starting with "server" to the install/data directory of the database (the postgresql.conf file is also stored in the install/data directory.)
+   Modify the postgresql.conf file.
+       ssl = on
+       ssl_cert_file = 'server.crt'
+       ssl_key_file = 'server.key'
+       ssl_ca_file = 'root.crt'
+   Restart the database after the modification is complete.
+   Modify the sslmode parameter in the odbc.ini configuration file (require or verify-ca).
+   ```
+
+8. Configure the database server.<a id="8"></a>
+
+   a. Log in as the OS user **omm** to the primary node of the database.
+
+   b. Run the following command to add NIC IP addresses or host names, with values separated by commas (,). The NICs and hosts are used to provide external services. In the following command, *NodeName* specifies the name of the current node.
+
+   ```
+   gs_guc reload -N NodeName -I all -c "listen_addresses='localhost,192.168.0.100,10.11.12.13'"
+   ```
+
+   If direct routing of LVS is used, add the virtual IP address (10.11.12.13) of LVS to the server listening list.
+
+   You can also set **listen_addresses** to **\*** or **0.0.0.0** to listen to all NICs, but this incurs security risks and is not recommended.
+
+   c. Run the following command to add an authentication rule to the configuration file of the primary database node. In this example, the IP address (10.11.12.13) of the client is the remote host IP address.
+
+   ```
+   gs_guc reload -N all -I all -h "host all jack 10.11.12.13/32 sha256"
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+   >
+   > - **-N all** indicates all hosts in MogDB.
+   > - **-I all** indicates all instances of the host.
+   > - **-h** specifies statements that need to be added in the **pg_hba.conf** file.
+   > - **all** indicates that a client can connect to any database.
+   > - **jack** indicates the user that accesses the database.
+   > - **10.11.12.13/32** indicates hosts whose IP address is 10.11.12.13 can be connected. Configure the parameter based on your network conditions. **32** indicates that there are 32 bits whose value is 1 in the subnet mask. That is, the subnet mask is 255.255.255.255.
+   > - **sha256** indicates that the password of user **jack** is encrypted using the SHA-256 algorithm.
+
+   If the ODBC client and the primary database node to connect are deployed on the same machine, you can use the local trust authentication mode. Run the following command:
+
+   ```
+   local all all trust
+   ```
+
+   If the ODBC client and the primary database node to connect are deployed on different machines, use the SHA-256 authentication mode. Run the following command:
+
+   ```
+   host all all xxx.xxx.xxx.xxx/32 sha256
+   ```
+
+   d. Restart MogDB.
+
+   ```
+   gs_om -t stop
+   gs_om -t start
+   ```
+
+9. Configure environment variables on the client.
+
+   ```
+   vim ~/.bashrc
+   ```
+
+   Add the following information to the configuration file:
+
+   ```bash
+   export LD_LIBRARY_PATH=/usr/local/lib/:$LD_LIBRARY_PATH
+   export ODBCSYSINI=/usr/local/etc
+   export ODBCINI=/usr/local/etc/odbc.ini
+   ```
+
+10. Run the following command to validate the addition:
+
+   ```
+   source ~/.bashrc
+   ```
+
+**Verifying the Data Source Configuration**
+
+Run the **./isql-v** **MPPODBC** command (**MPPODBC** is the data source name).
+
+- If the following information is displayed, the configuration is correct and the connection succeeds.
+
+  ```
+  +---------------------------------------+
+  | Connected!                            |
+  |                                       |
+  | sql-statement                         |
+  | help [tablename]                      |
+  | quit                                  |
+  |                                       |
+  +---------------------------------------+
+  SQL>
+  ```
+
+- If error information is displayed, the configuration is incorrect. Check the configuration.
+
+**FAQs**
+
+- [UnixODBC]Can't open lib 'xxx/xxx/psqlodbcw.so' : file not found.
+
+    Possible causes:
+
+  - The path configured in the **odbcinst.ini** file is incorrect.
+
+    Run **ls** to check the path in the error information, and ensure that the **psqlodbcw.so** file exists and you have execute permissions on it.
+
+  - The dependent library of **psqlodbcw.so** does not exist or is not in system environment variables.
+
+    Run **ldd** to check the path in the error information. If **libodbc.so.1** or other UnixODBC libraries do not exist, configure UnixODBC again following the procedure provided in this section, and add the **lib** directory under its installation directory to **LD_LIBRARY_PATH**. If other libraries do not exist, add the **lib** directory under the ODBC driver package to **LD_LIBRARY_PATH**.
+
+- [UnixODBC]connect to server failed: no such file or directory
+
+    Possible causes:
+
+  - An incorrect or unreachable database IP address or port number was configured.
+
+    Check the **Servername** and **Port** configuration items in data sources.
+
+  - Server monitoring is improper.
+
+    If **Servername** and **Port** are correctly configured, ensure the proper network adapter and port are monitored by following the database server configurations in the procedure in this section.
+
+  - Firewall and network gatekeeper settings are improper.
+
+    Check firewall settings, and ensure that the database communication port is trusted.
+
+    Check to ensure network gatekeeper settings are proper (if any).
+
+- [unixODBC]The password-stored method is not supported.
+
+  Possible causes:
+
+  The **sslmode** configuration item is not configured in the data sources.
+
+  Solution:
+
+  Set the configuration item to **allow** or a higher level. For details, see [Table 3](#sslmode).
+
+- Server common name "xxxx" does not match host name "xxxxx"
+
+  Possible causes:
+
+  When **verify-full** is used for SSL encryption, the driver checks whether the host name in certificates is the same as the actual one.
+
+  Solution:
+
+  To solve this problem, use **verify-ca** to stop checking host names, or generate a set of CA certificates containing the actual host names.
+
+- Driver's SQLAllocHandle on SQL_HANDLE_DBC failed
+
+  Possible causes:
+
+  The executable file (such as the **isql** tool of unixODBC) and the database driver (**psqlodbcw.so**) depend on different library versions of ODBC, such as **libodbc.so.1** and **libodbc.so.2**. You can verify this problem by using the following method:
+
+  ```
+  ldd `which isql` | grep odbc
+  ldd psqlodbcw.so | grep odbc
+  ```
+
+  If the suffix digits of the outputs **libodbc.so** are different or indicate different physical disk files, this problem exists. Both **isql** and **psqlodbcw.so** load **libodbc.so**. If different physical files are loaded, different ODBC libraries with the same function list conflict with each other in a visible domain. As a result, the database driver cannot be loaded.
+
+  Solution:
+
+  Uninstall the unnecessary unixODBC, such as libodbc.so.2, and create a soft link with the same name and the .so.2 suffix for the remaining libodbc.so.1 library.
+
+- FATAL: Forbid remote connection with trust method!
+
+  For security purposes, the primary database node forbids access from other nodes in MogDB without authentication.
+
+  To access the primary database node from inside MogDB, deploy the ODBC program on the host where the primary database node is located and set the server address to **127.0.0.1**. It is recommended that the service system be deployed outside MogDB. If it is deployed inside, database performance may be affected.
+
+- [unixODBC]Invalid attribute value
+
+  This problem occurs when you use SQL on other MogDB. The possible cause is that the unixODBC version is not the recommended one. You are advised to run the **odbcinst -version** command to check the unixODBC version.
+
+- authentication method 10 not supported.
+
+  If this error occurs on an open-source client, the cause may be:
+
+  The database stores only the SHA-256 hash of the password, but the open-source client supports only MD5 hashes.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > - The database stores the hashes of user passwords instead of actual passwords.
+  > - If a password is updated or a user is created, both types of hashes will be stored, compatible with open-source authentication protocols.
+  > - An MD5 hash can only be generated using the original password, but the password cannot be obtained by reversing its SHA-256 hash. Passwords in the old version will only have SHA-256 hashes and not support MD5 authentication.
+  > - The MD5 encryption algorithm has lower security and poses security risks. Therefore, you are advised to use a more secure encryption algorithm.
+
+  To solve this problem, you can update the user password (see **ALTER USER**) or create a user (see **CREATE USER**) having the same permissions as the faulty user.
+
+- unsupported frontend protocol 3.51: server supports 1.0 to 3.0
+
+  The database version is too early or the database is an open-source database. Use the driver of the required version to connect to the database.
+
+- FATAL: GSS authentication method is not allowed because XXXX user password is not disabled.
+
+  In **pg_hba.conf** of the target primary database node, the authentication mode is set to **gss** for authenticating the IP address of the current client. However, this authentication algorithm cannot authenticate clients. Change the authentication algorithm to **sha256** and try again. For details, see [8](#8).
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/4-development-process.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/4-development-process.md
new file mode 100644
index 0000000000000000000000000000000000000000..838f216c786839f3594bc9bc40711a29e775164a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/4-development-process.md
@@ -0,0 +1,38 @@
+---
+title: Development Process
+summary: Development Process
+author: Guo Huan
+date: 2021-04-26
+---
+
+# Development Process
+
+**Figure 1** ODBC-based application development process
+
+![odbc-based-application-development-process](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/development-process-4.png)
+
+**APIs Involved in the Development Process**
+
+**Table 1** API description
+
+| **Function**                                              | **API**                                                      |
+| :-------------------------------------------------------- | :----------------------------------------------------------- |
+| Allocate a handle                                         | SQLAllocHandle is a generic function for allocating a handle. It can replace the following functions:<br />- SQLAllocEnv: allocate an environment handle<br />- SQLAllocConnect: allocate a connection handle<br />- SQLAllocStmt: allocate a statement handle |
+| Set environment attributes                                | SQLSetEnvAttr                                                |
+| Set connection attributes                                 | SQLSetConnectAttr                                            |
+| Set statement attributes                                  | SQLSetStmtAttr                                               |
+| Connect to a data source                                  | SQLConnect                                                   |
+| Bind a buffer to a column in the result set               | SQLBindCol                                                   |
+| Bind the parameter marker of an SQL statement to a buffer | SQLBindParameter                                             |
+| Return the error message of the last operation            | SQLGetDiagRec                                                |
+| Prepare an SQL statement for execution                    | SQLPrepare                                                   |
+| Run a prepared SQL statement                              | SQLExecute                                                   |
+| Run an SQL statement directly                             | SQLExecDirect                                                |
+| Fetch the next row (or rows) from the result set          | SQLFetch                                                     |
+| Return data in a column of the result set                 | SQLGetData                                                   |
+| Get the column information from a result set              | SQLColAttribute                                              |
+| Disconnect from a data source                             | SQLDisconnect                                                |
+| Release a handle                                          | SQLFreeHandle is a generic function for releasing a handle. It can replace the following functions:<br />- SQLFreeEnv: release an environment handle<br />- SQLFreeConnect: release a connection handle<br />- SQLFreeStmt: release a statement handle |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> If an execution request (not in a transaction block) received in the database contains multiple statements, the request is packed into a transaction. If one of the statements fails, the entire request will be rolled back.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/5-example-common-functions-and-batch-binding.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/5-example-common-functions-and-batch-binding.md
new file mode 100644
index 0000000000000000000000000000000000000000..eed5abea290f6be68eb9ff7db1734bf531b146e5
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/5-example-common-functions-and-batch-binding.md
@@ -0,0 +1,440 @@
+---
+title: Common Functions and Batch Binding
+summary: Common Functions and Batch Binding
+author: Guo Huan
+date: 2021-04-26
+---
+
+# Example: Common Functions and Batch Binding
+
+## Code for Common Functions
+
+```
+//The following example shows how to obtain data from openGauss through the ODBC interface.
+// DBtest.c (compile with: libodbc.so)   
+#include <stdlib.h> 
+#include <stdio.h> 
+#include <sqlext.h>
+#ifdef WIN32
+#include <windows.h>
+#endif 
+SQLHENV       V_OD_Env;        // Handle ODBC environment 
+SQLHSTMT      V_OD_hstmt;      // Handle statement 
+SQLHDBC       V_OD_hdbc;       // Handle connection     
+char          typename[100];
+SQLINTEGER    value = 100;
+SQLINTEGER    V_OD_erg,V_OD_buffer,V_OD_err,V_OD_id;
+int main(int argc,char *argv[]) 
+{         
+      // 1. Allocate an environment handle.
+      V_OD_erg = SQLAllocHandle(SQL_HANDLE_ENV,SQL_NULL_HANDLE,&V_OD_Env);     
+      if ((V_OD_erg != SQL_SUCCESS) && (V_OD_erg != SQL_SUCCESS_WITH_INFO))        
+      {           
+           printf("Error AllocHandle\n");           
+           exit(0);        
+      } 
+      // 2. Set environment attributes (version information).
+      SQLSetEnvAttr(V_OD_Env, SQL_ATTR_ODBC_VERSION, (void*)SQL_OV_ODBC3, 0);      
+      // 3. Allocate a connection handle.
+      V_OD_erg = SQLAllocHandle(SQL_HANDLE_DBC, V_OD_Env, &V_OD_hdbc);     
+      if ((V_OD_erg != SQL_SUCCESS) && (V_OD_erg != SQL_SUCCESS_WITH_INFO))      
+      {                     
+           SQLFreeHandle(SQL_HANDLE_ENV, V_OD_Env);          
+           exit(0);       
+      }
+      // 4. Set connection attributes.
+      SQLSetConnectAttr(V_OD_hdbc, SQL_ATTR_AUTOCOMMIT, SQL_AUTOCOMMIT_ON, 0);          
+     // 5. Connect to the data source. userName and password indicate the username and password for connecting to the database. Set them as needed.
+     // If the username and password have been set in the odbc.ini file, you do not need to set userName or password here, retaining "" for them. However, you are not advised to do so because the username and password will be disclosed if the permission for odbc.ini is abused.
+      V_OD_erg = SQLConnect(V_OD_hdbc, (SQLCHAR*) "gaussdb", SQL_NTS,  
+                           (SQLCHAR*) "userName", SQL_NTS,  (SQLCHAR*) "password", SQL_NTS);        
+      if ((V_OD_erg != SQL_SUCCESS) && (V_OD_erg != SQL_SUCCESS_WITH_INFO))      
+      {           
+          printf("Error SQLConnect %d\n",V_OD_erg);            
+          SQLFreeHandle(SQL_HANDLE_ENV, V_OD_Env);       
+          exit(0);        
+      }     
+      printf("Connected !\n"); 
+      // 6. Set statement attributes.
+      SQLSetStmtAttr(V_OD_hstmt,SQL_ATTR_QUERY_TIMEOUT,(SQLPOINTER *)3,0);
+       // 7. Allocate a statement handle.
+      SQLAllocHandle(SQL_HANDLE_STMT, V_OD_hdbc, &V_OD_hstmt);       
+      // 8. Run SQL statements.
+      SQLExecDirect(V_OD_hstmt,"drop table IF EXISTS customer_t1",SQL_NTS);
+      SQLExecDirect(V_OD_hstmt,"CREATE TABLE customer_t1(c_customer_sk INTEGER, c_customer_name VARCHAR(32));",SQL_NTS);
+      SQLExecDirect(V_OD_hstmt,"insert into customer_t1 values(25,li)",SQL_NTS);
+      // 9. Prepare for execution.
+      SQLPrepare(V_OD_hstmt,"insert into customer_t1 values(?)",SQL_NTS); 
+      // 10. Bind parameters.
+      SQLBindParameter(V_OD_hstmt,1,SQL_PARAM_INPUT,SQL_C_SLONG,SQL_INTEGER,0,0,
+                       &value,0,NULL);
+      // 11. Run prepared statements.
+      SQLExecute(V_OD_hstmt);
+      SQLExecDirect(V_OD_hstmt,"select id from testtable",SQL_NTS);
+      // 12. Obtain attributes of a specific column in the result set.
+      SQLColAttribute(V_OD_hstmt,1,SQL_DESC_TYPE,typename,100,NULL,NULL);                 
+      printf("SQLColAtrribute %s\n",typename);
+      // 13. Bind the result set.
+      SQLBindCol(V_OD_hstmt,1,SQL_C_SLONG, (SQLPOINTER)&V_OD_buffer,150,
+                (SQLLEN *)&V_OD_err);
+      // 14. Obtain data in the result set by executing SQLFetch.
+      V_OD_erg=SQLFetch(V_OD_hstmt);
+      // 15. Obtain and return data by executing SQLGetData.
+      while(V_OD_erg != SQL_NO_DATA)
+      {
+          SQLGetData(V_OD_hstmt,1,SQL_C_SLONG,(SQLPOINTER)&V_OD_id,0,NULL);
+          printf("SQLGetData ----ID = %d\n",V_OD_id);
+          V_OD_erg=SQLFetch(V_OD_hstmt);
+      };
+      printf("Done !\n");
+      // 16. Disconnect data source connections and release handles.
+      SQLFreeHandle(SQL_HANDLE_STMT,V_OD_hstmt);    
+      SQLDisconnect(V_OD_hdbc);         
+      SQLFreeHandle(SQL_HANDLE_DBC,V_OD_hdbc);       
+      SQLFreeHandle(SQL_HANDLE_ENV, V_OD_Env);  
+      return(0);
+ }
+```
+
+## Code for Batch Processing
+
+```
+/**********************************************************************
+* Enable UseBatchProtocol in the data source and set the database parameter support_batch_bind
+* to on.
+* The CHECK_ERROR command is used to check and print error information.
+* This example is used to interactively obtain the DSN, data volume to be processed, and volume of ignored data from users, and insert required data into the test_odbc_batch_insert table.
+***********************************************************************/
+#include <stdio.h>
+#include <stdlib.h>
+#include <sql.h>
+#include <sqlext.h>
+#include <string.h>
+
+void Exec(SQLHDBC hdbc, SQLCHAR* sql)
+{
+    SQLRETURN retcode;                  // Return status
+    SQLHSTMT hstmt = SQL_NULL_HSTMT;    // Statement handle
+    SQLCHAR     loginfo[2048];
+
+    // Allocate Statement Handle
+    retcode = SQLAllocHandle(SQL_HANDLE_STMT, hdbc, &hstmt);
+    
+    if (!SQL_SUCCEEDED(retcode)) {
+        printf("SQLAllocHandle(SQL_HANDLE_STMT) failed");
+        return;
+    }
+
+    // Prepare Statement
+    retcode = SQLPrepare(hstmt, (SQLCHAR*) sql, SQL_NTS);
+    sprintf((char*)loginfo, "SQLPrepare log: %s", (char*)sql);
+    
+    if (!SQL_SUCCEEDED(retcode)) {
+        printf("SQLPrepare(hstmt, (SQLCHAR*) sql, SQL_NTS) failed");
+        return;
+    }
+
+    // Execute Statement
+    retcode = SQLExecute(hstmt);
+    sprintf((char*)loginfo, "SQLExecute stmt log: %s", (char*)sql);
+    
+    if (!SQL_SUCCEEDED(retcode)) {
+        printf("SQLExecute(hstmt) failed");
+        return;
+    }
+    // Free Handle
+    retcode = SQLFreeHandle(SQL_HANDLE_STMT, hstmt);
+    sprintf((char*)loginfo, "SQLFreeHandle stmt log: %s", (char*)sql);
+    
+    if (!SQL_SUCCEEDED(retcode)) {
+        printf("SQLFreeHandle(SQL_HANDLE_STMT, hstmt) failed");
+        return;
+    }
+}
+
+int main () 
+{
+    SQLHENV  henv  = SQL_NULL_HENV;
+    SQLHDBC  hdbc  = SQL_NULL_HDBC; 
+    int      batchCount = 1000; // Amount of data that is bound in batches
+    SQLLEN   rowsCount = 0;
+    int      ignoreCount = 0; // Amount of data that is not imported to the database among the data that is bound in batches
+
+    SQLRETURN   retcode;
+    SQLCHAR     dsn[1024] = {'\0'};
+    SQLCHAR     loginfo[2048];
+
+    do 
+    {
+        if (ignoreCount > batchCount)
+        {
+            printf("ignoreCount(%d) should be less than batchCount(%d)\n", ignoreCount, batchCount);
+        }
+    }while(ignoreCount > batchCount);
+
+    retcode = SQLAllocHandle(SQL_HANDLE_ENV, SQL_NULL_HANDLE, &henv);
+    
+    if (!SQL_SUCCEEDED(retcode)) {
+        printf("SQLAllocHandle failed");
+        goto exit;
+    }
+
+    // Set ODBC Verion
+    retcode = SQLSetEnvAttr(henv, SQL_ATTR_ODBC_VERSION,
+                                        (SQLPOINTER*)SQL_OV_ODBC3, 0);
+    
+    if (!SQL_SUCCEEDED(retcode)) {
+        printf("SQLSetEnvAttr failed");
+        goto exit;
+    }
+
+    // Allocate Connection
+    retcode = SQLAllocHandle(SQL_HANDLE_DBC, henv, &hdbc);
+    
+    if (!SQL_SUCCEEDED(retcode)) {
+        printf("SQLAllocHandle failed");
+        goto exit;
+    }
+
+
+    // Set Login Timeout
+    retcode = SQLSetConnectAttr(hdbc, SQL_LOGIN_TIMEOUT, (SQLPOINTER)5, 0);
+    
+    if (!SQL_SUCCEEDED(retcode)) {
+        printf("SQLSetConnectAttr failed");
+        goto exit;
+    }
+
+
+    // Set Auto Commit
+    retcode = SQLSetConnectAttr(hdbc, SQL_ATTR_AUTOCOMMIT,
+                                        (SQLPOINTER)(1), 0);
+    
+    if (!SQL_SUCCEEDED(retcode)) {
+        printf("SQLSetConnectAttr failed");
+        goto exit;
+    }
+
+
+    // Connect to DSN
+    // gaussdb indicates the name of the data source used by users.
+    sprintf(loginfo, "SQLConnect(DSN:%s)", dsn);
+    retcode = SQLConnect(hdbc, (SQLCHAR*) "gaussdb", SQL_NTS,
+                               (SQLCHAR*) NULL, 0, NULL, 0);
+    
+    if (!SQL_SUCCEEDED(retcode)) {
+        printf("SQLConnect failed");
+        goto exit;
+    }
+
+    // init table info.
+    Exec(hdbc, "drop table if exists test_odbc_batch_insert");
+    Exec(hdbc, "create table test_odbc_batch_insert(id int primary key, col varchar2(50))");
+
+   // The following code constructs the data to be inserted based on the data volume entered by users:
+    {
+        SQLRETURN retcode; 
+        SQLHSTMT hstmtinesrt = SQL_NULL_HSTMT;
+        int          i;
+        SQLCHAR      *sql = NULL;
+        SQLINTEGER   *ids  = NULL;
+        SQLCHAR      *cols = NULL;
+        SQLLEN       *bufLenIds = NULL;
+        SQLLEN       *bufLenCols = NULL;
+        SQLUSMALLINT *operptr = NULL;
+        SQLUSMALLINT *statusptr = NULL;
+        SQLULEN      process = 0;
+
+        // Data is constructed by column. Each column is stored continuously.
+        ids = (SQLINTEGER*)malloc(sizeof(ids[0]) * batchCount);
+        cols = (SQLCHAR*)malloc(sizeof(cols[0]) * batchCount * 50);
+       // Data size in each row for a column
+        bufLenIds = (SQLLEN*)malloc(sizeof(bufLenIds[0]) * batchCount);
+        bufLenCols = (SQLLEN*)malloc(sizeof(bufLenCols[0]) * batchCount);
+       // Whether this row needs to be processed. The value is SQL_PARAM_IGNORE or SQL_PARAM_PROCEED.
+        operptr = (SQLUSMALLINT*)malloc(sizeof(operptr[0]) * batchCount);
+        memset(operptr, 0, sizeof(operptr[0]) * batchCount);
+       // Processing result of the row
+       // Note: In the database, a statement belongs to one transaction. Therefore, data is processed as a unit. Either all data is inserted successfully or all data fails to be inserted.
+        statusptr = (SQLUSMALLINT*)malloc(sizeof(statusptr[0]) * batchCount);
+        memset(statusptr, 88, sizeof(statusptr[0]) * batchCount);
+
+        if (NULL == ids || NULL == cols || NULL == bufLenCols || NULL == bufLenIds)
+        {
+            fprintf(stderr, "FAILED:\tmalloc data memory failed\n");
+            goto exit;
+        }
+
+        for (int i = 0; i < batchCount; i++)
+        {
+            ids[i] = i;
+            sprintf(cols + 50 * i, "column test value %d", i);
+            bufLenIds[i] = sizeof(ids[i]);
+            bufLenCols[i] = strlen(cols + 50 * i);
+            operptr[i] = (i < ignoreCount) ? SQL_PARAM_IGNORE : SQL_PARAM_PROCEED;
+        }
+
+        // Allocate Statement Handle
+        retcode = SQLAllocHandle(SQL_HANDLE_STMT, hdbc, &hstmtinesrt);
+        
+        if (!SQL_SUCCEEDED(retcode)) {
+            printf("SQLAllocHandle failed");
+            goto exit;
+        }
+
+        // Prepare Statement
+        sql = (SQLCHAR*)"insert into test_odbc_batch_insert values(?, ?)";
+        retcode = SQLPrepare(hstmtinesrt, (SQLCHAR*) sql, SQL_NTS);
+        sprintf((char*)loginfo, "SQLPrepare log: %s", (char*)sql);
+        
+        if (!SQL_SUCCEEDED(retcode)) {
+            printf("SQLPrepare failed");
+            goto exit;
+        }
+
+        retcode = SQLSetStmtAttr(hstmtinesrt, SQL_ATTR_PARAMSET_SIZE, (SQLPOINTER)batchCount, sizeof(batchCount));
+        
+        if (!SQL_SUCCEEDED(retcode)) {
+            printf("SQLSetStmtAttr failed");
+            goto exit;
+        }
+
+        retcode = SQLBindParameter(hstmtinesrt, 1, SQL_PARAM_INPUT, SQL_C_SLONG, SQL_INTEGER, sizeof(ids[0]), 0,&(ids[0]), 0, bufLenIds);
+        
+        if (!SQL_SUCCEEDED(retcode)) {
+            printf("SQLBindParameter failed");
+            goto exit;
+        }
+
+        retcode = SQLBindParameter(hstmtinesrt, 2, SQL_PARAM_INPUT, SQL_C_CHAR, SQL_CHAR, 50, 50, cols, 50, bufLenCols);
+        
+        if (!SQL_SUCCEEDED(retcode)) {
+            printf("SQLBindParameter failed");
+            goto exit;
+        }
+
+        retcode = SQLSetStmtAttr(hstmtinesrt, SQL_ATTR_PARAMS_PROCESSED_PTR, (SQLPOINTER)&process, sizeof(process));
+        
+        if (!SQL_SUCCEEDED(retcode)) {
+            printf("SQLSetStmtAttr failed");
+            goto exit;
+        }
+
+        retcode = SQLSetStmtAttr(hstmtinesrt, SQL_ATTR_PARAM_STATUS_PTR, (SQLPOINTER)statusptr, sizeof(statusptr[0]) * batchCount);
+        
+        if (!SQL_SUCCEEDED(retcode)) {
+            printf("SQLSetStmtAttr failed");
+            goto exit;
+        }
+
+        retcode = SQLSetStmtAttr(hstmtinesrt, SQL_ATTR_PARAM_OPERATION_PTR, (SQLPOINTER)operptr, sizeof(operptr[0]) * batchCount);
+        
+        if (!SQL_SUCCEEDED(retcode)) {
+            printf("SQLSetStmtAttr failed");
+            goto exit;
+        }
+
+        retcode = SQLExecute(hstmtinesrt);
+        sprintf((char*)loginfo, "SQLExecute stmt log: %s", (char*)sql);
+        
+        if (!SQL_SUCCEEDED(retcode)) {
+            printf("SQLExecute(hstmtinesrt) failed");
+            goto exit;
+
+        retcode = SQLRowCount(hstmtinesrt, &rowsCount);
+        
+        if (!SQL_SUCCEEDED(retcode)) {
+            printf("SQLRowCount failed");
+            goto exit;
+        }
+
+        if (rowsCount != (batchCount - ignoreCount))
+        {
+            sprintf(loginfo, "(batchCount - ignoreCount)(%d) != rowsCount(%d)", (batchCount - ignoreCount), rowsCount);
+            
+            if (!SQL_SUCCEEDED(retcode)) {
+                printf("SQLExecute failed");
+                goto exit;
+            }
+        }
+        else
+        {
+            sprintf(loginfo, "(batchCount - ignoreCount)(%d) == rowsCount(%d)", (batchCount - ignoreCount), rowsCount);
+            
+            if (!SQL_SUCCEEDED(retcode)) {
+                printf("SQLExecute failed");
+                goto exit;
+            }
+        }
+
+        // check row number returned
+        if (rowsCount != process)
+        {
+            sprintf(loginfo, "process(%d) != rowsCount(%d)", process, rowsCount);
+            
+            if (!SQL_SUCCEEDED(retcode)) {
+                printf("SQLExecute failed");
+                goto exit;
+            }
+        }
+        else
+        {
+            sprintf(loginfo, "process(%d) == rowsCount(%d)", process, rowsCount);
+            
+            if (!SQL_SUCCEEDED(retcode)) {
+                printf("SQLExecute failed");
+                goto exit;
+            }
+        }
+
+        for (int i = 0; i < batchCount; i++)
+        {
+            if (i < ignoreCount)
+            {
+                if (statusptr[i] != SQL_PARAM_UNUSED)
+                {
+                    sprintf(loginfo, "statusptr[%d](%d) != SQL_PARAM_UNUSED", i, statusptr[i]);
+                    
+                    if (!SQL_SUCCEEDED(retcode)) {
+                        printf("SQLExecute failed");
+                        goto exit;
+                    }
+                }
+            }
+            else if (statusptr[i] != SQL_PARAM_SUCCESS)
+            {
+                sprintf(loginfo, "statusptr[%d](%d) != SQL_PARAM_SUCCESS", i, statusptr[i]);
+                
+                if (!SQL_SUCCEEDED(retcode)) {
+                    printf("SQLExecute failed");
+                    goto exit;
+                }
+            }
+        }
+
+        retcode = SQLFreeHandle(SQL_HANDLE_STMT, hstmtinesrt);
+        sprintf((char*)loginfo, "SQLFreeHandle hstmtinesrt");
+        
+        if (!SQL_SUCCEEDED(retcode)) {
+            printf("SQLFreeHandle failed");
+            goto exit;
+        }
+    }
+
+
+exit:
+    (void) printf ("\nComplete.\n");
+
+    // Connection
+    if (hdbc != SQL_NULL_HDBC) {
+        SQLDisconnect(hdbc);
+        SQLFreeHandle(SQL_HANDLE_DBC, hdbc);
+    }
+
+    // Environment
+    if (henv != SQL_NULL_HENV)
+        SQLFreeHandle(SQL_HANDLE_ENV, henv);
+
+    return 0;
+}
+```
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/5.1-typical-application-scenarios-and-configurations.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/5.1-typical-application-scenarios-and-configurations.md
new file mode 100644
index 0000000000000000000000000000000000000000..7017deb1846b5e1fab85f9a0981ded031b1d75cd
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/5.1-typical-application-scenarios-and-configurations.md
@@ -0,0 +1,496 @@
+---
+title: Typical Application Scenarios and Configurations
+summary: Typical Application Scenarios and Configurations
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# Typical Application Scenarios and Configurations
+
+## Log Diagnosis Scenario
+
+ODBC logs are classified into unixODBC driver manager logs and psqlODBC driver logs. The former is used to trace whether the application API is successfully executed, and the latter is used to locate problems based on DFX logs generated during underlying implementation.
+
+The unixODBC log needs to be configured in the **odbcinst.ini** file:
+
+```bash
+[ODBC]
+Trace=Yes
+TraceFile=/path/to/odbctrace.log
+
+[GaussMPP]
+Driver64=/usr/local/lib/psqlodbcw.so
+setup=/usr/local/lib/psqlodbcw.so
+```
+
+You only need to add the following information to the **odbc.ini** file:
+
+```bash
+[gaussdb]
+Driver=GaussMPP
+Servername=10.10.0.13 (database server IP address)
+...
+Debug=1 (Enable the debug log function of the driver.)
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The unixODBC logs are generated in the path configured by **TraceFile**. The psqlODBC generates the **mylog_***xxx***.log** file in the **/tmp/** directory.
+
+## High Performance
+
+If a large amount of data needs to be inserted, you are advised to perform the following operations:
+
+- You need to set **UseBatchProtocol** to **1** in the **odbc.ini** file and **support_batch_bind** to **on** in the database.
+- The ODBC program binding type must be the same as that in the database.
+- The character set of the client is the same as that of the database.
+- The transaction is committed manually.
+
+**odbc.ini** configuration file:
+
+```bash
+[gaussdb]
+Driver=GaussMPP
+Servername=10.10.0.13 (database server IP address)
+...
+UseBatchProtocol=1 (enabled by default)
+ConnSettings=set client_encoding=UTF8 (Set the character code on the client to be the same as that on the server.)
+```
+
+Binding type case:
+
+```c
+#include <stdio.h>
+#include <stdlib.h>
+#include <sql.h>
+#include <sqlext.h>
+#include <string.h>
+#include <sys/time.h>
+
+#define MESSAGE_BUFFER_LEN  128
+SQLHANDLE   h_env = NULL;
+SQLHANDLE   h_conn = NULL;
+SQLHANDLE   h_stmt = NULL;
+void print_error()
+{
+    SQLCHAR     Sqlstate[SQL_SQLSTATE_SIZE+1];
+    SQLINTEGER  NativeError;
+    SQLCHAR     MessageText[MESSAGE_BUFFER_LEN];
+    SQLSMALLINT TextLength;
+    SQLRETURN   ret = SQL_ERROR;
+
+    ret = SQLGetDiagRec(SQL_HANDLE_STMT, h_stmt, 1, Sqlstate, &NativeError, MessageText, MESSAGE_BUFFER_LEN, &TextLength);
+    if ( SQL_SUCCESS == ret)
+    {
+        printf("\n STMT ERROR-%05d %s", NativeError, MessageText);
+        return;
+    }
+
+    ret = SQLGetDiagRec(SQL_HANDLE_DBC, h_conn, 1, Sqlstate, &NativeError, MessageText, MESSAGE_BUFFER_LEN, &TextLength);
+    if ( SQL_SUCCESS == ret)
+    {
+        printf("\n CONN ERROR-%05d %s", NativeError, MessageText);
+        return;
+    }
+
+    ret = SQLGetDiagRec(SQL_HANDLE_ENV, h_env, 1, Sqlstate, &NativeError, MessageText, MESSAGE_BUFFER_LEN, &TextLength);
+    if ( SQL_SUCCESS == ret)
+    {
+        printf("\n ENV ERROR-%05d %s", NativeError, MessageText);
+        return;
+    }
+
+    return;
+}
+
+/* Expect the function to return SQL_SUCCESS. */
+#define RETURN_IF_NOT_SUCCESS(func) \
+{\
+    SQLRETURN ret_value = (func);\
+    if (SQL_SUCCESS != ret_value)\
+    {\
+        print_error();\
+        printf("\n failed line = %u: expect SQL_SUCCESS, but ret = %d", __LINE__, ret_value);\
+        return SQL_ERROR; \
+    }\
+}
+
+/* Expect the function to return SQL_SUCCESS. */
+#define RETURN_IF_NOT_SUCCESS_I(i, func) \
+{\
+    SQLRETURN ret_value = (func);\
+    if (SQL_SUCCESS != ret_value)\
+    {\
+        print_error();\
+        printf("\n failed line = %u (i=%d): : expect SQL_SUCCESS, but ret = %d", __LINE__, (i), ret_value);\
+        return SQL_ERROR; \
+    }\
+}
+
+/* Expect the function to return SQL_SUCCESS_WITH_INFO. */
+#define RETURN_IF_NOT_SUCCESS_INFO(func) \
+{\
+    SQLRETURN ret_value = (func);\
+    if (SQL_SUCCESS_WITH_INFO != ret_value)\
+    {\
+        print_error();\
+        printf("\n failed line = %u: expect SQL_SUCCESS_WITH_INFO, but ret = %d", __LINE__, ret_value);\
+        return SQL_ERROR; \
+    }\
+}
+
+/* Expect the values are the same. */
+#define RETURN_IF_NOT(expect, value) \
+if ((expect) != (value))\
+{\
+    printf("\n failed line = %u: expect = %u, but value = %u", __LINE__, (expect), (value)); \
+    return SQL_ERROR;\
+}
+
+/* Expect the character strings are the same. */
+#define RETURN_IF_NOT_STRCMP_I(i, expect, value) \
+if (( NULL == (expect) ) || (NULL == (value)))\
+{\
+    printf("\n failed line = %u (i=%u): input NULL pointer !", __LINE__, (i)); \
+    return SQL_ERROR; \
+}\
+else if (0 != strcmp((expect), (value)))\
+{\
+    printf("\n failed line = %u (i=%u): expect = %s, but value = %s", __LINE__, (i), (expect), (value)); \
+    return SQL_ERROR;\
+}
+
+
+// prepare + execute SQL statement
+int execute_cmd(SQLCHAR *sql)
+{
+    if ( NULL == sql )
+    {
+        return SQL_ERROR;
+    }
+
+    if ( SQL_SUCCESS != SQLPrepare(h_stmt, sql, SQL_NTS))
+    {
+        return SQL_ERROR;
+    }
+
+    if ( SQL_SUCCESS != SQLExecute(h_stmt))
+    {
+        return SQL_ERROR;
+    }
+
+    return SQL_SUCCESS;
+}
+// execute + commit handle
+int commit_exec()
+{
+    if ( SQL_SUCCESS != SQLExecute(h_stmt))
+    {
+        return SQL_ERROR;
+    }
+
+     // Manual committing
+    if ( SQL_SUCCESS != SQLEndTran(SQL_HANDLE_DBC, h_conn, SQL_COMMIT))
+    {
+        return SQL_ERROR;
+    }
+
+    return SQL_SUCCESS;
+}
+
+int begin_unit_test()
+{
+    SQLINTEGER    ret;
+
+    /* Allocate an environment handle. */
+    ret = SQLAllocHandle(SQL_HANDLE_ENV, SQL_NULL_HANDLE, &h_env);
+    if ((SQL_SUCCESS != ret) && (SQL_SUCCESS_WITH_INFO != ret))
+    {
+        printf("\n begin_unit_test::SQLAllocHandle SQL_HANDLE_ENV failed ! ret = %d", ret);
+        return SQL_ERROR;
+    }
+
+    /* Set the version number before connection. */
+    if (SQL_SUCCESS != SQLSetEnvAttr(h_env, SQL_ATTR_ODBC_VERSION, (SQLPOINTER)SQL_OV_ODBC3, 0))
+    {
+        print_error();
+        printf("\n begin_unit_test::SQLSetEnvAttr SQL_ATTR_ODBC_VERSION failed ! ret = %d", ret);
+        SQLFreeHandle(SQL_HANDLE_ENV, h_env);
+        return SQL_ERROR;
+    }
+
+    /* Allocate a connection handle. */
+    ret = SQLAllocHandle(SQL_HANDLE_DBC, h_env, &h_conn);
+    if (SQL_SUCCESS != ret)
+    {
+        print_error();
+        printf("\n begin_unit_test::SQLAllocHandle SQL_HANDLE_DBC failed ! ret = %d", ret);
+        SQLFreeHandle(SQL_HANDLE_ENV, h_env);
+        return SQL_ERROR;
+    }
+
+    /* Establish a connection. */
+    ret = SQLConnect(h_conn, (SQLCHAR*) "gaussdb", SQL_NTS,
+                               (SQLCHAR*) NULL, 0, NULL, 0);
+    if (SQL_SUCCESS != ret)
+    {
+        print_error();
+        printf("\n begin_unit_test::SQLConnect  failed ! ret = %d", ret);
+        SQLFreeHandle(SQL_HANDLE_DBC, h_conn);
+        SQLFreeHandle(SQL_HANDLE_ENV, h_env);
+        return SQL_ERROR;
+    }
+
+    /* Allocate a statement handle. */
+    ret = SQLAllocHandle(SQL_HANDLE_STMT, h_conn, &h_stmt);
+    if (SQL_SUCCESS != ret)
+    {
+        print_error();
+        printf("\n begin_unit_test::SQLAllocHandle SQL_HANDLE_STMT failed ! ret = %d", ret);
+        SQLFreeHandle(SQL_HANDLE_DBC, h_conn);
+        SQLFreeHandle(SQL_HANDLE_ENV, h_env);
+        return SQL_ERROR;
+    }
+
+    return SQL_SUCCESS;
+}
+
+void end_unit_test()
+{
+    /* Release a statement handle. */
+    if (NULL != h_stmt)
+    {
+        SQLFreeHandle(SQL_HANDLE_STMT, h_stmt);
+    }
+
+    /* Release a connection handle. */
+    if (NULL != h_conn)
+    {
+        SQLDisconnect(h_conn);
+        SQLFreeHandle(SQL_HANDLE_DBC, h_conn);
+    }
+
+    /* Release an environment handle. */
+    if (NULL != h_env)
+    {
+        SQLFreeHandle(SQL_HANDLE_ENV, h_env);
+    }
+
+    return;
+}
+
+int main()
+{
+    // begin test
+    if (begin_unit_test() != SQL_SUCCESS)
+    {
+        printf("\n begin_test_unit failed.");
+        return SQL_ERROR;
+    }
+    // The handle configuration is the same as that in the preceding case
+    int         i = 0;
+    SQLCHAR*    sql_drop   = "drop table if exists test_bindnumber_001";
+    SQLCHAR*    sql_create = "create table test_bindnumber_001("
+                             "f4 number, f5 number(10, 2)"
+                             ")";
+    SQLCHAR*    sql_insert = "insert into test_bindnumber_001 values(?, ?)";
+    SQLCHAR*    sql_select = "select * from test_bindnumber_001";
+    SQLLEN      RowCount;
+    SQL_NUMERIC_STRUCT st_number;
+    SQLCHAR     getValue[2][MESSAGE_BUFFER_LEN];
+
+    /* Step 1. Create a table. */
+    RETURN_IF_NOT_SUCCESS(execute_cmd(sql_drop));
+    RETURN_IF_NOT_SUCCESS(execute_cmd(sql_create));
+
+    /* Step 2.1 Bind parameters using the SQL_NUMERIC_STRUCT structure. */
+    RETURN_IF_NOT_SUCCESS(SQLPrepare(h_stmt, sql_insert, SQL_NTS));
+
+    // First line: 1234.5678
+    memset(st_number.val, 0, SQL_MAX_NUMERIC_LEN);
+    st_number.precision = 8;
+    st_number.scale = 4;
+    st_number.sign = 1;
+    st_number.val[0] = 0x4E;
+    st_number.val[1] = 0x61;
+    st_number.val[2] = 0xBC;
+
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 1, SQL_PARAM_INPUT, SQL_C_NUMERIC, SQL_NUMERIC, sizeof(SQL_NUMERIC_STRUCT), 4, &st_number, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 2, SQL_PARAM_INPUT, SQL_C_NUMERIC, SQL_NUMERIC, sizeof(SQL_NUMERIC_STRUCT), 4, &st_number, 0, NULL));
+
+    // Disable the automatic commit function.
+    SQLSetConnectAttr(h_conn, SQL_ATTR_AUTOCOMMIT, (SQLPOINTER)SQL_AUTOCOMMIT_OFF, 0);
+
+    RETURN_IF_NOT_SUCCESS(commit_exec());
+    RETURN_IF_NOT_SUCCESS(SQLRowCount(h_stmt, &RowCount));
+    RETURN_IF_NOT(1, RowCount);
+
+    // Second line: 12345678
+    memset(st_number.val, 0, SQL_MAX_NUMERIC_LEN);
+    st_number.precision = 8;
+    st_number.scale = 0;
+    st_number.sign = 1;
+    st_number.val[0] = 0x4E;
+    st_number.val[1] = 0x61;
+    st_number.val[2] = 0xBC;
+
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 1, SQL_PARAM_INPUT, SQL_C_NUMERIC, SQL_NUMERIC, sizeof(SQL_NUMERIC_STRUCT), 0, &st_number, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 2, SQL_PARAM_INPUT, SQL_C_NUMERIC, SQL_NUMERIC, sizeof(SQL_NUMERIC_STRUCT), 0, &st_number, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(commit_exec());
+    RETURN_IF_NOT_SUCCESS(SQLRowCount(h_stmt, &RowCount));
+    RETURN_IF_NOT(1, RowCount);
+
+    // Third line: 12345678
+    memset(st_number.val, 0, SQL_MAX_NUMERIC_LEN);
+    st_number.precision = 0;
+    st_number.scale = 4;
+    st_number.sign = 1;
+    st_number.val[0] = 0x4E;
+    st_number.val[1] = 0x61;
+    st_number.val[2] = 0xBC;
+
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 1, SQL_PARAM_INPUT, SQL_C_NUMERIC, SQL_NUMERIC, sizeof(SQL_NUMERIC_STRUCT), 4, &st_number, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 2, SQL_PARAM_INPUT, SQL_C_NUMERIC, SQL_NUMERIC, sizeof(SQL_NUMERIC_STRUCT), 4, &st_number, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(commit_exec());
+    RETURN_IF_NOT_SUCCESS(SQLRowCount(h_stmt, &RowCount));
+    RETURN_IF_NOT(1, RowCount);
+
+
+    /* Step 2.2 Bind parameters by using the SQL_C_CHAR character string in the fourth line. */
+    RETURN_IF_NOT_SUCCESS(SQLPrepare(h_stmt, sql_insert, SQL_NTS));
+    SQLCHAR*    szNumber = "1234.5678";
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 1, SQL_PARAM_INPUT, SQL_C_CHAR, SQL_NUMERIC, strlen(szNumber), 0, szNumber, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 2, SQL_PARAM_INPUT, SQL_C_CHAR, SQL_NUMERIC, strlen(szNumber), 0, szNumber, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(commit_exec());
+    RETURN_IF_NOT_SUCCESS(SQLRowCount(h_stmt, &RowCount));
+    RETURN_IF_NOT(1, RowCount);
+
+    /* Step 2.3 Bind parameters by using SQL_C_FLOAT in the fifth line. */
+    RETURN_IF_NOT_SUCCESS(SQLPrepare(h_stmt, sql_insert, SQL_NTS));
+    SQLREAL    fNumber = 1234.5678;
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 1, SQL_PARAM_INPUT, SQL_C_FLOAT, SQL_NUMERIC, sizeof(fNumber), 4, &fNumber, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 2, SQL_PARAM_INPUT, SQL_C_FLOAT, SQL_NUMERIC, sizeof(fNumber), 4, &fNumber, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(commit_exec());
+    RETURN_IF_NOT_SUCCESS(SQLRowCount(h_stmt, &RowCount));
+    RETURN_IF_NOT(1, RowCount);
+
+    /* Step 2.4 Bind parameters by using SQL_C_DOUBLE in the sixth line. */
+    RETURN_IF_NOT_SUCCESS(SQLPrepare(h_stmt, sql_insert, SQL_NTS));
+    SQLDOUBLE   dNumber = 1234.5678;
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 1, SQL_PARAM_INPUT, SQL_C_DOUBLE, SQL_NUMERIC, sizeof(dNumber), 4, &dNumber, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 2, SQL_PARAM_INPUT, SQL_C_DOUBLE, SQL_NUMERIC, sizeof(dNumber), 4, &dNumber, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(commit_exec());
+    RETURN_IF_NOT_SUCCESS(SQLRowCount(h_stmt, &RowCount));
+    RETURN_IF_NOT(1, RowCount);
+
+    SQLBIGINT   bNumber1 = 0xFFFFFFFFFFFFFFFF;
+    SQLBIGINT   bNumber2 = 12345;
+
+    /* Step 2.5 Bind parameters by using SQL_C_SBIGINT in the seventh line. */
+    RETURN_IF_NOT_SUCCESS(SQLPrepare(h_stmt, sql_insert, SQL_NTS));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 1, SQL_PARAM_INPUT, SQL_C_SBIGINT, SQL_NUMERIC, sizeof(bNumber1), 4, &bNumber1, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 2, SQL_PARAM_INPUT, SQL_C_SBIGINT, SQL_NUMERIC, sizeof(bNumber2), 4, &bNumber2, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(commit_exec());
+    RETURN_IF_NOT_SUCCESS(SQLRowCount(h_stmt, &RowCount));
+    RETURN_IF_NOT(1, RowCount);
+
+    /* Step 2.6 Bind parameters by using SQL_C_UBIGINT in the eighth line. */
+    RETURN_IF_NOT_SUCCESS(SQLPrepare(h_stmt, sql_insert, SQL_NTS));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 1, SQL_PARAM_INPUT, SQL_C_UBIGINT, SQL_NUMERIC, sizeof(bNumber1), 4, &bNumber1, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 2, SQL_PARAM_INPUT, SQL_C_UBIGINT, SQL_NUMERIC, sizeof(bNumber2), 4, &bNumber2, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(commit_exec());
+    RETURN_IF_NOT_SUCCESS(SQLRowCount(h_stmt, &RowCount));
+    RETURN_IF_NOT(1, RowCount);
+
+    SQLLEN  lNumber1 = 0xFFFFFFFFFFFFFFFF;
+    SQLLEN  lNumber2 = 12345;
+
+    /* Step 2.7 Bind parameters by using SQL_C_LONG in the ninth line. */
+    RETURN_IF_NOT_SUCCESS(SQLPrepare(h_stmt, sql_insert, SQL_NTS));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 1, SQL_PARAM_INPUT, SQL_C_LONG, SQL_NUMERIC, sizeof(lNumber1), 0, &lNumber1, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 2, SQL_PARAM_INPUT, SQL_C_LONG, SQL_NUMERIC, sizeof(lNumber2), 0, &lNumber2, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(commit_exec());
+    RETURN_IF_NOT_SUCCESS(SQLRowCount(h_stmt, &RowCount));
+    RETURN_IF_NOT(1, RowCount);
+
+    /* Step 2.8 Bind parameters by using SQL_C_ULONG in the tenth line. */
+    RETURN_IF_NOT_SUCCESS(SQLPrepare(h_stmt, sql_insert, SQL_NTS));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 1, SQL_PARAM_INPUT, SQL_C_ULONG, SQL_NUMERIC, sizeof(lNumber1), 0, &lNumber1, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 2, SQL_PARAM_INPUT, SQL_C_ULONG, SQL_NUMERIC, sizeof(lNumber2), 0, &lNumber2, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(commit_exec());
+    RETURN_IF_NOT_SUCCESS(SQLRowCount(h_stmt, &RowCount));
+    RETURN_IF_NOT(1, RowCount);
+
+    SQLSMALLINT sNumber = 0xFFFF;
+
+    /* Step 2.9 Bind parameters by using SQL_C_SHORT in the eleventh line. */
+    RETURN_IF_NOT_SUCCESS(SQLPrepare(h_stmt, sql_insert, SQL_NTS));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 1, SQL_PARAM_INPUT, SQL_C_SHORT, SQL_NUMERIC, sizeof(sNumber), 0, &sNumber, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 2, SQL_PARAM_INPUT, SQL_C_SHORT, SQL_NUMERIC, sizeof(sNumber), 0, &sNumber, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(commit_exec());
+    RETURN_IF_NOT_SUCCESS(SQLRowCount(h_stmt, &RowCount));
+    RETURN_IF_NOT(1, RowCount);
+
+    /* Step 2.10 Bind parameters by using SQL_C_USHORT in the twelfth line. */
+    RETURN_IF_NOT_SUCCESS(SQLPrepare(h_stmt, sql_insert, SQL_NTS));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 1, SQL_PARAM_INPUT, SQL_C_USHORT, SQL_NUMERIC, sizeof(sNumber), 0, &sNumber, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 2, SQL_PARAM_INPUT, SQL_C_USHORT, SQL_NUMERIC, sizeof(sNumber), 0, &sNumber, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(commit_exec());
+    RETURN_IF_NOT_SUCCESS(SQLRowCount(h_stmt, &RowCount));
+    RETURN_IF_NOT(1, RowCount);
+
+    SQLCHAR cNumber = 0xFF;
+
+    /* Step 2.11 Bind parameters by using SQL_C_TINYINT in the thirteenth line. */
+    RETURN_IF_NOT_SUCCESS(SQLPrepare(h_stmt, sql_insert, SQL_NTS));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 1, SQL_PARAM_INPUT, SQL_C_TINYINT, SQL_NUMERIC, sizeof(cNumber), 0, &cNumber, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 2, SQL_PARAM_INPUT, SQL_C_TINYINT, SQL_NUMERIC, sizeof(cNumber), 0, &cNumber, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(commit_exec());
+    RETURN_IF_NOT_SUCCESS(SQLRowCount(h_stmt, &RowCount));
+    RETURN_IF_NOT(1, RowCount);
+
+    /* Step 2.12 Bind parameters by using SQL_C_UTINYINT in the fourteenth line.*/
+    RETURN_IF_NOT_SUCCESS(SQLPrepare(h_stmt, sql_insert, SQL_NTS));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 1, SQL_PARAM_INPUT, SQL_C_UTINYINT, SQL_NUMERIC, sizeof(cNumber), 0, &cNumber, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 2, SQL_PARAM_INPUT, SQL_C_UTINYINT, SQL_NUMERIC, sizeof(cNumber), 0, &cNumber, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(commit_exec());
+    RETURN_IF_NOT_SUCCESS(SQLRowCount(h_stmt, &RowCount));
+    RETURN_IF_NOT(1, RowCount);
+
+    /* Use the character string type to unify the expectation. */
+    SQLCHAR*    expectValue[14][2] = {{"1234.5678",             "1234.57"},
+                                      {"12345678",              "12345678"},
+                                      {"0",                     "0"},
+                                      {"1234.5678",             "1234.57"},
+                                      {"1234.5677",             "1234.57"},
+                                      {"1234.5678",             "1234.57"},
+                                      {"-1",                    "12345"},
+                                      {"18446744073709551615",  "12345"},
+                                      {"-1",                    "12345"},
+                                      {"4294967295",            "12345"},
+                                      {"-1",                    "-1"},
+                                      {"65535",                 "65535"},
+                                      {"-1",                    "-1"},
+                                      {"255",                   "255"},
+                                      };
+
+    RETURN_IF_NOT_SUCCESS(execute_cmd(sql_select));
+    while ( SQL_NO_DATA != SQLFetch(h_stmt))
+    {
+        RETURN_IF_NOT_SUCCESS_I(i, SQLGetData(h_stmt, 1, SQL_C_CHAR, &getValue[0], MESSAGE_BUFFER_LEN, NULL));
+        RETURN_IF_NOT_SUCCESS_I(i, SQLGetData(h_stmt, 2, SQL_C_CHAR, &getValue[1], MESSAGE_BUFFER_LEN, NULL));
+
+        //RETURN_IF_NOT_STRCMP_I(i, expectValue[i][0], getValue[0]);
+        //RETURN_IF_NOT_STRCMP_I(i, expectValue[i][1], getValue[1]);
+        i++;
+    }
+
+    RETURN_IF_NOT_SUCCESS(SQLRowCount(h_stmt, &RowCount));
+    RETURN_IF_NOT(i, RowCount);
+    SQLCloseCursor(h_stmt);
+    /* Final step. Delete the table and restore the environment. */
+    RETURN_IF_NOT_SUCCESS(execute_cmd(sql_drop));
+
+    end_unit_test();
+}
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** In the preceding example, the number column is defined. When the **SQLBindParameter** API is called, the performance of binding SQL_NUMERIC is higher than that of SQL_LONG. If char is used, the data type needs to be converted when data is inserted to the database server, causing a performance bottleneck.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-0-odbc-overview.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-0-odbc-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..2afef8791be5a7e9a2cdb15fe82800702d437a08
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-0-odbc-overview.md
@@ -0,0 +1,10 @@
+---
+title: Description
+summary: Description
+author: Guo Huan
+date: 2021-05-17
+---
+
+# Description
+
+The ODBC interface is a set of API functions provided to users. This chapter describes its common interfaces. For details on other interfaces, see "ODBC Programmer's Reference" at MSDN (<https://msdn.microsoft.com/en-us/library/windows/desktop/ms714177(v=vs.85).aspx>).
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-1-SQLAllocEnv.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-1-SQLAllocEnv.md
new file mode 100644
index 0000000000000000000000000000000000000000..64e6ed59f8d132e23dedd889f1a96377233495bc
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-1-SQLAllocEnv.md
@@ -0,0 +1,10 @@
+---
+title: SQLAllocEnv
+summary: SQLAllocEnv
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLAllocEnv
+
+In ODBC 3.x, SQLAllocEnv (an ODBC 2.x function) was deprecated and replaced by SQLAllocHandle. For details, see SQLAllocHandle.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-10-SQLExecDirect.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-10-SQLExecDirect.md
new file mode 100644
index 0000000000000000000000000000000000000000..02cc87ecd76605c6e240d6a5eb3af5b46baf736c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-10-SQLExecDirect.md
@@ -0,0 +1,48 @@
+---
+title: SQLExecDirect
+summary: SQLExecDirect
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLExecDirect
+
+## Function
+
+SQLExecDirect is used to execute a prepared SQL statement specified in this parameter. This is the fastest method for executing only one SQL statement at a time.
+
+## Prototype
+
+```
+SQLRETURN SQLExecDirect(SQLHSTMT         StatementHandle,
+                        SQLCHAR         *StatementText,
+                        SQLINTEGER       TextLength);
+```
+
+## Parameter
+
+**Table 1** SQLExecDirect parameters
+
+| **Keyword**     | **Parameter Description**                                    |
+| :-------------- | :----------------------------------------------------------- |
+| StatementHandle | Statement handle, obtained from SQLAllocHandle.              |
+| StatementText   | SQL statement to be executed. One SQL statement can be executed at a time. |
+| TextLength      | Length of **StatementText**.                                 |
+
+## Return Value
+
+- **SQL_SUCCESS** indicates that the call succeeded.
+- **SQL_SUCCESS_WITH_INFO** indicates that some warning information is displayed.
+- **SQL_NEED_DATA** indicates that parameters provided before executing the SQL statement are insufficient.
+- **SQL_ERROR** indicates major errors, such as memory allocation and connection failures.
+- **SQL_INVALID_HANDLE** indicates that invalid handles were called. This value may also be returned by other APIs.
+- **SQL_STILL_EXECUTING** indicates that the statement is being executed.
+- **SQL_NO_DATA** indicates that the SQL statement does not return a result set.
+
+## Precautions
+
+If SQLExecDirect returns **SQL_ERROR** or **SQL_SUCCESS_WITH_INFO**, the application can call SQLGetDiagRec, with **HandleType** and **Handle** set to **SQL_HANDLE_STMT** and **StatementHandle**, respectively, to obtain the **SQLSTATE** value. The **SQLSTATE** value provides the detailed function calling information.
+
+## Example
+
+See ODBC - Examples.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-11-SQLExecute.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-11-SQLExecute.md
new file mode 100644
index 0000000000000000000000000000000000000000..41b4d385be31528f0ea803ed73afe3ad3bccec5d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-11-SQLExecute.md
@@ -0,0 +1,44 @@
+---
+title: SQLExecute
+summary: SQLExecute
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLExecute
+
+## Function
+
+SQLExecute is used to execute a prepared SQL statement using SQLPrepare. The statement is executed using the current value of any application variables that were bound to parameter markers by SQLBindParameter.
+
+## Prototype
+
+```
+SQLRETURN SQLExecute(SQLHSTMT    StatementHandle);
+```
+
+## Parameter
+
+**Table 1** SQLExecute parameters
+
+| **Keyword**     | **Parameter Description**        |
+| :-------------- | :------------------------------- |
+| StatementHandle | Statement handle to be executed. |
+
+## Return Value
+
+- **SQL_SUCCESS** indicates that the call succeeded.
+- **SQL_SUCCESS_WITH_INFO** indicates that some warning information is displayed.
+- **SQL_NEED_DATA** indicates that parameters provided before executing the SQL statement are insufficient.
+- **SQL_ERROR** indicates major errors, such as memory allocation and connection failures.
+- **SQL_NO_DATA** indicates that the SQL statement does not return a result set.
+- **SQL_INVALID_HANDLE** indicates that invalid handles were called. This value may also be returned by other APIs.
+- **SQL_STILL_EXECUTING** indicates that the statement is being executed.
+
+## Precautions
+
+If SQLExecute returns **SQL_ERROR** or **SQL_SUCCESS_WITH_INFO**, the application can call SQLGetDiagRec, with **HandleType** and **Handle** set to **SQL_HANDLE_STMT** and **StatementHandle**, respectively, to obtain the **SQLSTATE** value. The **SQLSTATE** value provides the detailed function calling information.
+
+## Example
+
+See ODBC - Examples.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-12-SQLFetch.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-12-SQLFetch.md
new file mode 100644
index 0000000000000000000000000000000000000000..519f9946a7af1fd6ec83970e2d00899934373689
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-12-SQLFetch.md
@@ -0,0 +1,43 @@
+---
+title: SQLFetch
+summary: SQLFetch
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLFetch
+
+## Function
+
+SQLFetch is used to advance the cursor to the next row of the result set and retrieve any bound columns.
+
+## Prototype
+
+```
+CSQLRETURN SQLFetch(SQLHSTMT    StatementHandle);
+```
+
+## Parameter
+
+**Table 1** SQLFetch parameters
+
+| **Keyword**     | **Parameter Description**                       |
+| :-------------- | :---------------------------------------------- |
+| StatementHandle | Statement handle, obtained from SQLAllocHandle. |
+
+## Return Value
+
+- **SQL_SUCCESS** indicates that the call succeeded.
+- **SQL_SUCCESS_WITH_INFO** indicates that some warning information is displayed.
+- **SQL_ERROR** indicates major errors, such as memory allocation and connection failures.
+- **SQL_NO_DATA** indicates that the SQL statement does not return a result set.
+- **SQL_INVALID_HANDLE** indicates that invalid handles were called. This value may also be returned by other APIs.
+- **SQL_STILL_EXECUTING** indicates that the statement is being executed.
+
+## Precautions
+
+If SQLFetch returns **SQL_ERROR** or **SQL_SUCCESS_WITH_INFO**, the application can call SQLGetDiagRec, with **HandleType** and **Handle** set to **SQL_HANDLE_STMT** and **StatementHandle**, respectively, to obtain the **SQLSTATE** value. The **SQLSTATE** value provides the detailed function calling information.
+
+## Example
+
+See ODBC - Examples.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-13-SQLFreeStmt.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-13-SQLFreeStmt.md
new file mode 100644
index 0000000000000000000000000000000000000000..7c2d3e6705c1e38511614fc63b7803781c5950d3
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-13-SQLFreeStmt.md
@@ -0,0 +1,10 @@
+---
+title: SQLFreeStmt
+summary: SQLFreeStmt
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLFreeStmt
+
+In ODBC 3.x, SQLFreeStmt (an ODBC 2.x function) was deprecated and replaced by SQLFreeHandle. For details, see SQLFreeHandle.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-14-SQLFreeConnect.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-14-SQLFreeConnect.md
new file mode 100644
index 0000000000000000000000000000000000000000..1c097d143263533e1fc5771a5d123c2cf52556ae
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-14-SQLFreeConnect.md
@@ -0,0 +1,10 @@
+---
+title: SQLFreeConnect
+summary: SQLFreeConnect
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLFreeConnect
+
+In ODBC 3.x, SQLFreeConnect (an ODBC 2.x function) was deprecated and replaced by SQLFreeHandle. For details, see SQLFreeHandle.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-15-SQLFreeHandle.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-15-SQLFreeHandle.md
new file mode 100644
index 0000000000000000000000000000000000000000..131a10cf2e7a29a0900056aa820c5a19bd67ec14
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-15-SQLFreeHandle.md
@@ -0,0 +1,43 @@
+---
+title: SQLFreeHandle
+summary: SQLFreeHandle
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLFreeHandle
+
+## Function
+
+SQLFreeHandle is used to release resources associated with a specific environment, connection, or statement handle. It replaces the ODBC 2.x functions: SQLFreeEnv, SQLFreeConnect, and SQLFreeStmt.
+
+## Prototype
+
+```
+SQLRETURN SQLFreeHandle(SQLSMALLINT   HandleType,
+                        SQLHANDLE     Handle);
+```
+
+## Parameter
+
+**Table 1** SQLFreeHandle parameters
+
+| **Keyword** | **Parameter Description**                                    |
+| :---------- | :----------------------------------------------------------- |
+| HandleType  | Type of handle to be freed by SQLFreeHandle. The value must be one of the following:<br/>- SQL_HANDLE_ENV<br/>- SQL_HANDLE_DBC<br/>- SQL_HANDLE_STMT<br/>- SQL_HANDLE_DESC<br/>If **HandleType** is not one of the preceding values, SQLFreeHandle returns **SQL_INVALID_HANDLE**. |
+| Handle      | Name of the handle to be freed.                              |
+
+## Return Value
+
+- **SQL_SUCCESS** indicates that the call succeeded.
+- **SQL_SUCCESS_WITH_INFO** indicates that some warning information is displayed.
+- **SQL_ERROR** indicates major errors, such as memory allocation and connection failures.
+- **SQL_INVALID_HANDLE** indicates that invalid handles were called. This value may also be returned by other APIs.
+
+## Precautions
+
+If SQLFreeHandle returns **SQL_ERROR**, the handle is still valid.
+
+## Example
+
+See ODBC - Examples.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-16-SQLFreeEnv.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-16-SQLFreeEnv.md
new file mode 100644
index 0000000000000000000000000000000000000000..3ff15ad8e72e67aef4df7d7b4fbadd22b31a2175
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-16-SQLFreeEnv.md
@@ -0,0 +1,10 @@
+---
+title: SQLFreeEnv
+summary: SQLFreeEnv
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLFreeEnv
+
+In ODBC 3.x, SQLFreeEnv (an ODBC 2.x function) was deprecated and replaced by SQLFreeHandle. For details, see SQLFreeHandle.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-17-SQLPrepare.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-17-SQLPrepare.md
new file mode 100644
index 0000000000000000000000000000000000000000..e385634421da0b0f76f7984aad5c9fcb9f03ac12
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-17-SQLPrepare.md
@@ -0,0 +1,46 @@
+---
+title: SQLPrepare
+summary: SQLPrepare
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLPrepare
+
+## Function
+
+SQLPrepare is used to prepare an SQL statement to be executed.
+
+## Prototype
+
+```
+SQLRETURN SQLPrepare(SQLHSTMT      StatementHandle,
+                     SQLCHAR       *StatementText,
+                     SQLINTEGER    TextLength);
+```
+
+## Parameter
+
+**Table 1** SQLPrepare parameters
+
+| **Keyword**     | **Parameter Description**    |
+| :-------------- | :--------------------------- |
+| StatementHandle | Statement handle.            |
+| StatementText   | SQL text string.             |
+| TextLength      | Length of **StatementText**. |
+
+## Return Value
+
+- **SQL_SUCCESS** indicates that the call succeeded.
+- **SQL_SUCCESS_WITH_INFO** indicates that some warning information is displayed.
+- **SQL_ERROR** indicates major errors, such as memory allocation and connection failures.
+- **SQL_INVALID_HANDLE** indicates that invalid handles were called. This value may also be returned by other APIs.
+- **SQL_STILL_EXECUTING** indicates that the statement is being executed.
+
+## Precautions
+
+If SQLPrepare returns **SQL_ERROR** or **SQL_SUCCESS_WITH_INFO**, the application can call SQLGetDiagRec, with **HandleType** and **Handle** set to **SQL_HANDLE_STMT** and **StatementHandle**, respectively, to obtain the **SQLSTATE** value. The **SQLSTATE** value provides the detailed function calling information.
+
+## Example
+
+See ODBC - Examples.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-18-SQLGetData.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-18-SQLGetData.md
new file mode 100644
index 0000000000000000000000000000000000000000..2a88178b775fa03b9523be3a546edeb489d87326
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-18-SQLGetData.md
@@ -0,0 +1,53 @@
+---
+title: SQLGetData
+summary: SQLGetData
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLGetData
+
+## Function
+
+SQLGetData is used to retrieve data for a single column in the result set. It can be called for many times to retrieve data of variable lengths.
+
+## Prototype
+
+```
+SQLRETURN SQLGetData(SQLHSTMT        StatementHandle,
+                     SQLUSMALLINT    Col_or_Param_Num,
+                     SQLSMALLINT     TargetType,
+                     SQLPOINTER      TargetValuePtr,
+                     SQLLEN          BufferLength,
+                     SQLLEN          *StrLen_or_IndPtr);
+```
+
+## Parameter
+
+**Table 1** SQLGetData parameters
+
+| **Keyword**      | **Parameter Description**                                    |
+| :--------------- | :----------------------------------------------------------- |
+| StatementHandle  | Statement handle, obtained from SQLAllocHandle.              |
+| Col_or_Param_Num | Column number for which the data retrieval is requested. The column number starts with 1 and increases in ascending order. The number of the bookmark column is 0. |
+| TargetType       | C data type in the TargetValuePtr buffer. If **TargetType** is **SQL_ARD_TYPE**, the driver uses the data type of the **SQL_DESC_CONCISE_TYPE** field in ARD. If **TargetType** is **SQL_C_DEFAULT**, the driver selects a default data type according to the source SQL data type. |
+| TargetValuePtr   | **Output parameter**: pointer to the pointer that points to the buffer where the data is located. |
+| BufferLength     | Size of the buffer pointed to by **TargetValuePtr**.         |
+| StrLen_or_IndPtr | **Output parameter**: pointer to the buffer where the length or identifier value is returned. |
+
+## Return Value
+
+- **SQL_SUCCESS** indicates that the call succeeded.
+- **SQL_SUCCESS_WITH_INFO** indicates that some warning information is displayed.
+- **SQL_ERROR** indicates major errors, such as memory allocation and connection failures.
+- **SQL_NO_DATA** indicates that the SQL statement does not return a result set.
+- **SQL_INVALID_HANDLE** indicates that invalid handles were called. This value may also be returned by other APIs.
+- **SQL_STILL_EXECUTING** indicates that the statement is being executed.
+
+## Precautions
+
+If SQLGetData returns **SQL_ERROR** or **SQL_SUCCESS_WITH_INFO**, the application can call SQLGetDiagRec, with **HandleType** and **Handle** set to **SQL_HANDLE_STMT** and **StatementHandle**, respectively, to obtain the **SQLSTATE** value. The **SQLSTATE** value provides the detailed function calling information.
+
+## Example
+
+See ODBC - Examples.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-19-SQLGetDiagRec.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-19-SQLGetDiagRec.md
new file mode 100644
index 0000000000000000000000000000000000000000..328f677b0e64fa0290cda0b4e4ad9571f5f3b998
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-19-SQLGetDiagRec.md
@@ -0,0 +1,74 @@
+---
+title: SQLGetDiagRec
+summary: SQLGetDiagRec
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLGetDiagRec
+
+## Function
+
+SQLGetDiagRec is used to return the current values of multiple fields in a diagnostic record that contains error, warning, and status information.
+
+## Prototype
+
+```
+SQLRETURN  SQLGetDiagRec(SQLSMALLINT    HandleType
+                         SQLHANDLE      Handle,
+                         SQLSMALLINT    RecNumber,
+                         SQLCHAR        *SQLState,
+                         SQLINTEGER     *NativeErrorPtr,
+                         SQLCHAR        *MessageText,
+                         SQLSMALLINT    BufferLength
+                         SQLSMALLINT    *TextLengthPtr);
+```
+
+## Parameter
+
+**Table 1** SQLGetDiagRec parameters
+
+| **Keyword**    | **Parameter Description**                                    |
+| :------------- | :----------------------------------------------------------- |
+| HandleType     | A handle-type identifier that describes the type of handle for which diagnostics are desired. The value must be one of the following:<br/>- SQL_HANDLE_ENV<br/>- SQL_HANDLE_DBC<br/>- SQL_HANDLE_STMT<br/>- SQL_HANDLE_DESC |
+| Handle         | A handle for the diagnostic data structure. Its type is indicated by **HandleType**. If **HandleType** is **SQL_HANDLE_ENV**, **Handle** may be a shared or non-shared environment handle. |
+| RecNumber      | Status record from which the application seeks information. **RecNumber** starts with 1. |
+| SQLState       | **Output parameter**: pointer to a buffer that saves the 5-character **SQLSTATE** code pertaining to **RecNumber**. |
+| NativeErrorPtr | **Output parameter**: pointer to a buffer that saves the native error code. |
+| MessageText    | Pointer to a buffer that saves text strings of diagnostic information. |
+| BufferLength   | Length of **MessageText**.                                   |
+| TextLengthPtr  | **Output parameter**: pointer to the buffer, the total number of bytes in the returned **MessageText**. If the number of bytes available to return is greater than **BufferLength**, then the diagnostics information text in **MessageText** is truncated to **BufferLength** minus the length of the null termination character. |
+
+## Return Value
+
+- **SQL_SUCCESS** indicates that the call succeeded.
+- **SQL_SUCCESS_WITH_INFO** indicates that some warning information is displayed.
+- **SQL_ERROR** indicates major errors, such as memory allocation and connection failures.
+- **SQL_INVALID_HANDLE** indicates that invalid handles were called. This value may also be returned by other APIs.
+
+## Precautions
+
+SQLGetDiagRec does not release diagnostic records for itself. It uses the following return values to report execution results:
+
+- **SQL_SUCCESS** indicates that the function successfully returns diagnostic information.
+- **SQL_SUCCESS_WITH_INFO** indicates that the **MessageText** buffer is too small to hold the requested diagnostic information. No diagnostic records are generated.
+- **SQL_INVALID_HANDLE** indicates that the handle indicated by **HandType** and **Handle** is an invalid handle.
+- **SQL_ERROR** indicates that **RecNumber** is less than or equal to 0 or that **BufferLength** is smaller than 0.
+
+If an ODBC function returns **SQL_ERROR** or **SQL_SUCCESS_WITH_INFO**, the application can call SQLGetDiagRec to obtain the **SQLSTATE** value. The possible **SQLSTATE** values are listed as follows:
+
+**Table 2** SQLSTATE values
+
+| SQLSATATE | Error                                 | Description                                                  |
+| :-------- | :------------------------------------ | :----------------------------------------------------------- |
+| HY000     | General error.                        | An error occurred for which there is no specific SQLSTATE.   |
+| HY001     | Memory allocation error.              | The driver is unable to allocate memory required to support execution or completion of the function. |
+| HY008     | Operation canceled.                   | SQLCancel is called to terminate the statement execution, but the StatementHandle function is still called. |
+| HY010     | Function sequence error.              | The function is called prior to sending data to data parameters or columns being executed. |
+| HY013     | Memory management error.              | The function fails to be called. The error may be caused by low memory conditions. |
+| HYT01     | Connection timeout.                   | The timeout period expired before the application was able to connect to the data source. |
+| IM001     | Function not supported by the driver. | The called function is not supported by the StatementHandle driver. |
+
+## Example
+
+See ODBC - Examples.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-2-SQLAllocConnect.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-2-SQLAllocConnect.md
new file mode 100644
index 0000000000000000000000000000000000000000..3e9dd4f93a6c3df229c0dcbf5609f704bb1ba09c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-2-SQLAllocConnect.md
@@ -0,0 +1,10 @@
+---
+title: SQLAllocConnect
+summary: SQLAllocConnect
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLAllocConnect
+
+In ODBC 3.x, SQLAllocConnect (an ODBC 2.x function) was deprecated and replaced by SQLAllocHandle. For details, see SQLAllocHandle.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-20-SQLSetConnectAttr.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-20-SQLSetConnectAttr.md
new file mode 100644
index 0000000000000000000000000000000000000000..a2d60a9112fd788b6c6b8896d09edff6dc1fab42
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-20-SQLSetConnectAttr.md
@@ -0,0 +1,47 @@
+---
+title: SQLSetConnectAttr
+summary: SQLSetConnectAttr
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLSetConnectAttr
+
+## Function
+
+SQLSetConnectAttr is used to set connection attributes.
+
+## Prototype
+
+```
+SQLRETURN SQLSetConnectAttr(SQLHDBC       ConnectionHandle
+                            SQLINTEGER    Attribute,
+                            SQLPOINTER    ValuePtr,
+                            SQLINTEGER    StringLength);
+```
+
+## Parameter
+
+**Table 1** SQLSetConnectAttr parameters
+
+| **Keyword**      | **Parameter Description**                                    |
+| :--------------- | :----------------------------------------------------------- |
+| ConnectionHandle | Connection handle.                                           |
+| Attribute        | Attribute to set.                                            |
+| ValuePtr         | Pointer to the **Attribute** value. **ValuePtr** depends on the **Attribute** value, and can be a 32-bit unsigned integer value or a null-terminated string. If the **ValuePtr** parameter is a driver-specific value, it may be a signed integer. |
+| StringLength     | If **ValuePtr** points to a string or a binary buffer, **StringLength** is the length of ***ValuePtr**. If **ValuePtr** points to an integer, **StringLength** is ignored. |
+
+## Return Value
+
+- **SQL_SUCCESS** indicates that the call succeeded.
+- **SQL_SUCCESS_WITH_INFO** indicates that some warning information is displayed.
+- **SQL_ERROR** indicates major errors, such as memory allocation and connection failures.
+- **SQL_INVALID_HANDLE** indicates that invalid handles were called. This value may also be returned by other APIs.
+
+## Precautions
+
+If SQLSetConnectAttr returns **SQL_ERROR** or **SQL_SUCCESS_WITH_INFO**, the application can call SQLGetDiagRec, with **HandleType** and **Handle** set to **SQL_HANDLE_DBC** and **ConnectionHandle**, respectively, to obtain the **SQLSTATE** value. The **SQLSTATE** value provides the detailed function calling information.
+
+## Example
+
+See ODBC - Examples.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-21-SQLSetEnvAttr.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-21-SQLSetEnvAttr.md
new file mode 100644
index 0000000000000000000000000000000000000000..6e5494f5055ed4e0633227a2fcdc037fb36c1cf0
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-21-SQLSetEnvAttr.md
@@ -0,0 +1,47 @@
+---
+title: SQLSetEnvAttr
+summary: SQLSetEnvAttr
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLSetEnvAttr
+
+## Function
+
+SQLSetEnvAttr is used to set environment attributes.
+
+## Prototype
+
+```
+SQLRETURN SQLSetEnvAttr(SQLHENV       EnvironmentHandle
+                        SQLINTEGER    Attribute,
+                        SQLPOINTER    ValuePtr,
+                        SQLINTEGER    StringLength);
+```
+
+## Parameter
+
+**Table 1** SQLSetEnvAttr parameters
+
+| **Keyword**       | **Parameter Description**                                    |
+| :---------------- | :----------------------------------------------------------- |
+| EnvironmentHandle | Environment handle.                                          |
+| Attribute         | Environment attribute to be set. The value must be one of the following:<br/>- **SQL_ATTR_ODBC_VERSION**: ODBC version<br/>- **SQL_CONNECTION_POOLING**: connection pool attribute<br/>- **SQL_OUTPUT_NTS**: string type returned by the driver |
+| ValuePtr          | Pointer to the **Attribute** value. **ValuePtr** depends on the **Attribute** value, and can be a 32-bit integer value or a null-terminated string. |
+| StringLength      | If **ValuePtr** points to a string or a binary buffer, **StringLength** is the length of ***ValuePtr**. If **ValuePtr** points to an integer, **StringLength** is ignored. |
+
+## Return Value
+
+- **SQL_SUCCESS** indicates that the call succeeded.
+- **SQL_SUCCESS_WITH_INFO** indicates that some warning information is displayed.
+- **SQL_ERROR** indicates major errors, such as memory allocation and connection failures.
+- **SQL_INVALID_HANDLE** indicates that invalid handles were called. This value may also be returned by other APIs.
+
+## Precautions
+
+If SQLSetEnvAttr returns **SQL_ERROR** or **SQL_SUCCESS_WITH_INFO**, the application can call SQLGetDiagRec, set **HandleType** and **Handle** to **SQL_HANDLE_ENV** and **EnvironmentHandle**, and obtain the **SQLSTATE** value. The **SQLSTATE** value provides the detailed function calling information.
+
+## Example
+
+See ODBC - Examples.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-22-SQLSetStmtAttr.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-22-SQLSetStmtAttr.md
new file mode 100644
index 0000000000000000000000000000000000000000..1b1d2d6cf2f2583a7b7912999c3cb5f617e3c833
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-22-SQLSetStmtAttr.md
@@ -0,0 +1,47 @@
+---
+title: SQLSetStmtAttr
+summary: SQLSetStmtAttr
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLSetStmtAttr
+
+## Function
+
+SQLSetStmtAttr is used to set attributes related to a statement.
+
+## Prototype
+
+```
+SQLRETURN SQLSetStmtAttr(SQLHSTMT      StatementHandle
+                         SQLINTEGER    Attribute,
+                         SQLPOINTER    ValuePtr,
+                         SQLINTEGER    StringLength);
+```
+
+## Parameter
+
+**Table 1** SQLSetStmtAttr parameters
+
+| **Keyword**     | **Parameter Description**                                    |
+| :-------------- | :----------------------------------------------------------- |
+| StatementHandle | Statement handle.                                            |
+| Attribute       | Attribute to set.                                            |
+| ValuePtr        | Pointer to the **Attribute** value. **ValuePtr** depends on the **Attribute** value, and can be a 32-bit unsigned integer value or a pointer to a null-terminated string, a binary buffer, or a driver-specified value. If the **ValuePtr** parameter is a driver-specific value, it may be a signed integer. |
+| StringLength    | If **ValuePtr** points to a string or a binary buffer, **StringLength** is the length of ***ValuePtr**. If **ValuePtr** points to an integer, **StringLength** is ignored. |
+
+## Return Value
+
+- **SQL_SUCCESS** indicates that the call succeeded.
+- **SQL_SUCCESS_WITH_INFO** indicates that some warning information is displayed.
+- **SQL_ERROR** indicates major errors, such as memory allocation and connection failures.
+- **SQL_INVALID_HANDLE** indicates that invalid handles were called. This value may also be returned by other APIs.
+
+## Precautions
+
+If SQLSetStmtAttr returns **SQL_ERROR** or **SQL_SUCCESS_WITH_INFO**, the application can call SQLGetDiagRec, with **HandleType** and **Handle** set to **SQL_HANDLE_STMT** and **StatementHandle**, respectively, to obtain the **SQLSTATE** value. The **SQLSTATE** value provides the detailed function calling information.
+
+## Example
+
+See ODBC - Examples.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-23-Examples.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-23-Examples.md
new file mode 100644
index 0000000000000000000000000000000000000000..ef42c9cba275467f59dce375514878ec989f1ad3
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-23-Examples.md
@@ -0,0 +1,345 @@
+---
+title: Examples
+summary: Examples
+author: Guo Huan
+date: 2021-05-17
+---
+
+# Examples
+
+## Code for Common Functions
+
+```c
+// The following example shows how to obtain data from MogDB through the ODBC interface.
+// DBtest.c (compile with: libodbc.so)
+#include <stdlib.h>
+#include <stdio.h>
+#include <sqlext.h>
+#ifdef WIN32
+#include <windows.h>
+#endif
+SQLHENV       V_OD_Env;        // Handle ODBC environment
+SQLHSTMT      V_OD_hstmt;      // Handle statement
+SQLHDBC       V_OD_hdbc;       // Handle connection
+char          typename[100];
+SQLINTEGER    value = 100;
+SQLINTEGER    V_OD_erg,V_OD_buffer,V_OD_err,V_OD_id;
+int main(int argc,char *argv[])
+{
+      // 1. Allocate an environment handle.
+      V_OD_erg = SQLAllocHandle(SQL_HANDLE_ENV,SQL_NULL_HANDLE,&V_OD_Env);
+      if ((V_OD_erg != SQL_SUCCESS) && (V_OD_erg != SQL_SUCCESS_WITH_INFO))
+      {
+           printf("Error AllocHandle\n");
+           exit(0);
+      }
+      // 2. Set environment attributes (version information).
+      SQLSetEnvAttr(V_OD_Env, SQL_ATTR_ODBC_VERSION, (void*)SQL_OV_ODBC3, 0);
+      // 3. Allocate a connection handle.
+      V_OD_erg = SQLAllocHandle(SQL_HANDLE_DBC, V_OD_Env, &V_OD_hdbc);
+      if ((V_OD_erg != SQL_SUCCESS) && (V_OD_erg != SQL_SUCCESS_WITH_INFO))
+      {
+           SQLFreeHandle(SQL_HANDLE_ENV, V_OD_Env);
+           exit(0);
+      }
+      // 4. Set connection attributes.
+      SQLSetConnectAttr(V_OD_hdbc, SQL_ATTR_AUTOCOMMIT, SQL_AUTOCOMMIT_ON, 0);
+     // 5. Connect to the data source. userName and password indicate the username and password for connecting to the database. Set them as needed.
+     // If the username and password have been set in the odbc.ini file, you do not need to set userName or password here, retaining "" for them. However, you are not advised to do so because the username and password will be disclosed if the permission for odbc.ini is abused.
+      V_OD_erg = SQLConnect(V_OD_hdbc, (SQLCHAR*) "gaussdb", SQL_NTS,
+                           (SQLCHAR*) "userName", SQL_NTS,  (SQLCHAR*) "password", SQL_NTS);
+      if ((V_OD_erg != SQL_SUCCESS) && (V_OD_erg != SQL_SUCCESS_WITH_INFO))
+      {
+          printf("Error SQLConnect %d\n",V_OD_erg);
+          SQLFreeHandle(SQL_HANDLE_ENV, V_OD_Env);
+          exit(0);
+      }
+      printf("Connected !\n");
+      // 6. Set statement attributes.
+      SQLSetStmtAttr(V_OD_hstmt,SQL_ATTR_QUERY_TIMEOUT,(SQLPOINTER *)3,0);
+       // 7. Allocate a statement handle.
+      SQLAllocHandle(SQL_HANDLE_STMT, V_OD_hdbc, &V_OD_hstmt);
+      // 8. Run SQL statements.
+      SQLExecDirect(V_OD_hstmt,"drop table IF EXISTS customer_t1",SQL_NTS);
+      SQLExecDirect(V_OD_hstmt,"CREATE TABLE customer_t1(c_customer_sk INTEGER, c_customer_name VARCHAR(32));",SQL_NTS);
+      SQLExecDirect(V_OD_hstmt,"insert into customer_t1 values(25,li)",SQL_NTS);
+      // 9. Prepare for execution.
+      SQLPrepare(V_OD_hstmt,"insert into customer_t1 values(?)",SQL_NTS);
+      // 10. Bind parameters.
+      SQLBindParameter(V_OD_hstmt,1,SQL_PARAM_INPUT,SQL_C_SLONG,SQL_INTEGER,0,0,
+                       &value,0,NULL);
+      // 11. Run prepared statements.
+      SQLExecute(V_OD_hstmt);
+      SQLExecDirect(V_OD_hstmt,"select id from testtable",SQL_NTS);
+      // 12. Obtain attributes of a specific column in the result set.
+      SQLColAttribute(V_OD_hstmt,1,SQL_DESC_TYPE,typename,100,NULL,NULL);
+      printf("SQLColAtrribute %s\n",typename);
+      // 13. Bind the result set.
+      SQLBindCol(V_OD_hstmt,1,SQL_C_SLONG, (SQLPOINTER)&V_OD_buffer,150,
+                (SQLLEN *)&V_OD_err);
+      // 14. Obtain data in the result set by executing SQLFetch.
+      V_OD_erg=SQLFetch(V_OD_hstmt);
+      // 15. Obtain and return data by executing SQLGetData.
+      while(V_OD_erg != SQL_NO_DATA)
+      {
+          SQLGetData(V_OD_hstmt,1,SQL_C_SLONG,(SQLPOINTER)&V_OD_id,0,NULL);
+          printf("SQLGetData ----ID = %d\n",V_OD_id);
+          V_OD_erg=SQLFetch(V_OD_hstmt);
+      };
+      printf("Done !\n");
+      // 16. Disconnect data source connections and release handles.
+      SQLFreeHandle(SQL_HANDLE_STMT,V_OD_hstmt);
+      SQLDisconnect(V_OD_hdbc);
+      SQLFreeHandle(SQL_HANDLE_DBC,V_OD_hdbc);
+      SQLFreeHandle(SQL_HANDLE_ENV, V_OD_Env);
+      return(0);
+ }
+```
+
+## Code for Batch Processing
+
+```c
+/**********************************************************************
+*Set UseBatchProtocol to 1 in the data source and set the database parameter support_batch_bind
+*to on.
+*The CHECK_ERROR command is used to check and print error information.
+*This example is used to interactively obtain the DSN, data volume to be processed, and volume of ignored data from users, and insert required data into the test_odbc_batch_insert table.
+***********************************************************************/
+#include <stdio.h>
+#include <stdlib.h>
+#include <sql.h>
+#include <sqlext.h>
+#include <string.h>
+
+#include "util.c"
+
+void Exec(SQLHDBC hdbc, SQLCHAR* sql)
+{
+    SQLRETURN retcode;                  // Return status
+    SQLHSTMT hstmt = SQL_NULL_HSTMT;    // Statement handle
+    SQLCHAR     loginfo[2048];
+
+    // Allocate Statement Handle
+    retcode = SQLAllocHandle(SQL_HANDLE_STMT, hdbc, &hstmt);
+    CHECK_ERROR(retcode, "SQLAllocHandle(SQL_HANDLE_STMT)",
+                hstmt, SQL_HANDLE_STMT);
+
+    // Prepare Statement
+    retcode = SQLPrepare(hstmt, (SQLCHAR*) sql, SQL_NTS);
+    sprintf((char*)loginfo, "SQLPrepare log: %s", (char*)sql);
+    CHECK_ERROR(retcode, loginfo, hstmt, SQL_HANDLE_STMT);
+
+    // Execute Statement
+    retcode = SQLExecute(hstmt);
+    sprintf((char*)loginfo, "SQLExecute stmt log: %s", (char*)sql);
+    CHECK_ERROR(retcode, loginfo, hstmt, SQL_HANDLE_STMT);
+
+    // Free Handle
+    retcode = SQLFreeHandle(SQL_HANDLE_STMT, hstmt);
+    sprintf((char*)loginfo, "SQLFreeHandle stmt log: %s", (char*)sql);
+    CHECK_ERROR(retcode, loginfo, hstmt, SQL_HANDLE_STMT);
+}
+
+int main ()
+{
+    SQLHENV  henv  = SQL_NULL_HENV;
+    SQLHDBC  hdbc  = SQL_NULL_HDBC;
+    int      batchCount = 1000;
+    SQLLEN   rowsCount = 0;
+    int      ignoreCount = 0;
+
+    SQLRETURN   retcode;
+    SQLCHAR     dsn[1024] = {'\0'};
+    SQLCHAR     loginfo[2048];
+
+   // Interactively obtain data source names.
+    getStr("Please input your DSN", (char*)dsn, sizeof(dsn), 'N');
+   // Interactively obtain the volume of data to be batch processed.
+    getInt("batchCount", &batchCount, 'N', 1);
+    do
+    {
+       // Interactively obtain the volume of batch processing data that is not inserted into the database.
+        getInt("ignoreCount", &ignoreCount, 'N', 1);
+        if (ignoreCount > batchCount)
+        {
+            printf("ignoreCount(%d) should be less than batchCount(%d)\n", ignoreCount, batchCount);
+        }
+    }while(ignoreCount > batchCount);
+
+    retcode = SQLAllocHandle(SQL_HANDLE_ENV, SQL_NULL_HANDLE, &henv);
+    CHECK_ERROR(retcode, "SQLAllocHandle(SQL_HANDLE_ENV)",
+                henv, SQL_HANDLE_ENV);
+
+    // Set ODBC Verion
+    retcode = SQLSetEnvAttr(henv, SQL_ATTR_ODBC_VERSION,
+                                        (SQLPOINTER*)SQL_OV_ODBC3, 0);
+    CHECK_ERROR(retcode, "SQLSetEnvAttr(SQL_ATTR_ODBC_VERSION)",
+                henv, SQL_HANDLE_ENV);
+
+    // Allocate Connection
+    retcode = SQLAllocHandle(SQL_HANDLE_DBC, henv, &hdbc);
+    CHECK_ERROR(retcode, "SQLAllocHandle(SQL_HANDLE_DBC)",
+                henv, SQL_HANDLE_DBC);
+
+    // Set Login Timeout
+    retcode = SQLSetConnectAttr(hdbc, SQL_LOGIN_TIMEOUT, (SQLPOINTER)5, 0);
+    CHECK_ERROR(retcode, "SQLSetConnectAttr(SQL_LOGIN_TIMEOUT)",
+                hdbc, SQL_HANDLE_DBC);
+
+    // Set Auto Commit
+    retcode = SQLSetConnectAttr(hdbc, SQL_ATTR_AUTOCOMMIT,
+                                        (SQLPOINTER)(1), 0);
+    CHECK_ERROR(retcode, "SQLSetConnectAttr(SQL_ATTR_AUTOCOMMIT)",
+                hdbc, SQL_HANDLE_DBC);
+
+    // Connect to DSN
+    sprintf(loginfo, "SQLConnect(DSN:%s)", dsn);
+    retcode = SQLConnect(hdbc, (SQLCHAR*) dsn, SQL_NTS,
+                               (SQLCHAR*) NULL, 0, NULL, 0);
+    CHECK_ERROR(retcode, loginfo, hdbc, SQL_HANDLE_DBC);
+
+    // init table info.
+    Exec(hdbc, "drop table if exists test_odbc_batch_insert");
+    Exec(hdbc, "create table test_odbc_batch_insert(id int primary key, col varchar2(50))");
+
+   // The following code constructs the data to be inserted based on the data volume entered by users:
+    {
+        SQLRETURN retcode;
+        SQLHSTMT hstmtinesrt = SQL_NULL_HSTMT;
+        int          i;
+        SQLCHAR      *sql = NULL;
+        SQLINTEGER   *ids  = NULL;
+        SQLCHAR      *cols = NULL;
+        SQLLEN       *bufLenIds = NULL;
+        SQLLEN       *bufLenCols = NULL;
+        SQLUSMALLINT *operptr = NULL;
+        SQLUSMALLINT *statusptr = NULL;
+        SQLULEN      process = 0;
+
+        // Data is constructed by column. Each column is stored continuously.
+        ids = (SQLINTEGER*)malloc(sizeof(ids[0]) * batchCount);
+        cols = (SQLCHAR*)malloc(sizeof(cols[0]) * batchCount * 50);
+       // Data size in each row for a column
+        bufLenIds = (SQLLEN*)malloc(sizeof(bufLenIds[0]) * batchCount);
+        bufLenCols = (SQLLEN*)malloc(sizeof(bufLenCols[0]) * batchCount);
+       // Whether this row needs to be processed. The value is SQL_PARAM_IGNORE or SQL_PARAM_PROCEED.
+        operptr = (SQLUSMALLINT*)malloc(sizeof(operptr[0]) * batchCount);
+        memset(operptr, 0, sizeof(operptr[0]) * batchCount);
+       // Processing result of the row
+       // Note: In the database, a statement belongs to one transaction. Therefore, data is processed as a unit. Either all data is inserted successfully or all data fails to be inserted.
+        statusptr = (SQLUSMALLINT*)malloc(sizeof(statusptr[0]) * batchCount);
+        memset(statusptr, 88, sizeof(statusptr[0]) * batchCount);
+
+        if (NULL == ids || NULL == cols || NULL == bufLenCols || NULL == bufLenIds)
+        {
+            fprintf(stderr, "FAILED:\tmalloc data memory failed\n");
+            goto exit;
+        }
+
+        for (int i = 0; i < batchCount; i++)
+        {
+            ids[i] = i;
+            sprintf(cols + 50 * i, "column test value %d", i);
+            bufLenIds[i] = sizeof(ids[i]);
+            bufLenCols[i] = strlen(cols + 50 * i);
+            operptr[i] = (i < ignoreCount) ? SQL_PARAM_IGNORE : SQL_PARAM_PROCEED;
+        }
+
+        // Allocate Statement Handle
+        retcode = SQLAllocHandle(SQL_HANDLE_STMT, hdbc, &hstmtinesrt);
+        CHECK_ERROR(retcode, "SQLAllocHandle(SQL_HANDLE_STMT)",
+                    hstmtinesrt, SQL_HANDLE_STMT);
+
+        // Prepare Statement
+        sql = (SQLCHAR*)"insert into test_odbc_batch_insert values(?, ?)";
+        retcode = SQLPrepare(hstmtinesrt, (SQLCHAR*) sql, SQL_NTS);
+        sprintf((char*)loginfo, "SQLPrepare log: %s", (char*)sql);
+        CHECK_ERROR(retcode, loginfo, hstmtinesrt, SQL_HANDLE_STMT);
+
+        retcode = SQLSetStmtAttr(hstmtinesrt, SQL_ATTR_PARAMSET_SIZE, (SQLPOINTER)batchCount, sizeof(batchCount));
+        CHECK_ERROR(retcode, "SQLSetStmtAttr", hstmtinesrt, SQL_HANDLE_STMT);
+
+        retcode = SQLBindParameter(hstmtinesrt, 1, SQL_PARAM_INPUT, SQL_C_SLONG, SQL_INTEGER, sizeof(ids[0]), 0,&(ids[0]), 0, bufLenIds);
+        CHECK_ERROR(retcode, "SQLBindParameter for id", hstmtinesrt, SQL_HANDLE_STMT);
+
+        retcode = SQLBindParameter(hstmtinesrt, 2, SQL_PARAM_INPUT, SQL_C_CHAR, SQL_CHAR, 50, 50, cols, 50, bufLenCols);
+        CHECK_ERROR(retcode, "SQLBindParameter for cols", hstmtinesrt, SQL_HANDLE_STMT);
+
+        retcode = SQLSetStmtAttr(hstmtinesrt, SQL_ATTR_PARAMS_PROCESSED_PTR, (SQLPOINTER)&process, sizeof(process));
+        CHECK_ERROR(retcode, "SQLSetStmtAttr for SQL_ATTR_PARAMS_PROCESSED_PTR", hstmtinesrt, SQL_HANDLE_STMT);
+
+        retcode = SQLSetStmtAttr(hstmtinesrt, SQL_ATTR_PARAM_STATUS_PTR, (SQLPOINTER)statusptr, sizeof(statusptr[0]) * batchCount);
+        CHECK_ERROR(retcode, "SQLSetStmtAttr for SQL_ATTR_PARAM_STATUS_PTR", hstmtinesrt, SQL_HANDLE_STMT);
+
+        retcode = SQLSetStmtAttr(hstmtinesrt, SQL_ATTR_PARAM_OPERATION_PTR, (SQLPOINTER)operptr, sizeof(operptr[0]) * batchCount);
+        CHECK_ERROR(retcode, "SQLSetStmtAttr for SQL_ATTR_PARAM_OPERATION_PTR", hstmtinesrt, SQL_HANDLE_STMT);
+
+        retcode = SQLExecute(hstmtinesrt);
+        sprintf((char*)loginfo, "SQLExecute stmt log: %s", (char*)sql);
+        CHECK_ERROR(retcode, loginfo, hstmtinesrt, SQL_HANDLE_STMT);
+
+        retcode = SQLRowCount(hstmtinesrt, &rowsCount);
+        CHECK_ERROR(retcode, "SQLRowCount execution", hstmtinesrt, SQL_HANDLE_STMT);
+
+        if (rowsCount != (batchCount - ignoreCount))
+        {
+            sprintf(loginfo, "(batchCount - ignoreCount)(%d) != rowsCount(%d)", (batchCount - ignoreCount), rowsCount);
+            CHECK_ERROR(SQL_ERROR, loginfo, NULL, SQL_HANDLE_STMT);
+        }
+        else
+        {
+            sprintf(loginfo, "(batchCount - ignoreCount)(%d) == rowsCount(%d)", (batchCount - ignoreCount), rowsCount);
+            CHECK_ERROR(SQL_SUCCESS, loginfo, NULL, SQL_HANDLE_STMT);
+        }
+
+        // check row number returned
+        if (rowsCount != process)
+        {
+            sprintf(loginfo, "process(%d) != rowsCount(%d)", process, rowsCount);
+            CHECK_ERROR(SQL_ERROR, loginfo, NULL, SQL_HANDLE_STMT);
+        }
+        else
+        {
+            sprintf(loginfo, "process(%d) == rowsCount(%d)", process, rowsCount);
+            CHECK_ERROR(SQL_SUCCESS, loginfo, NULL, SQL_HANDLE_STMT);
+        }
+
+        for (int i = 0; i < batchCount; i++)
+        {
+            if (i < ignoreCount)
+            {
+                if (statusptr[i] != SQL_PARAM_UNUSED)
+                {
+                    sprintf(loginfo, "statusptr[%d](%d) != SQL_PARAM_UNUSED", i, statusptr[i]);
+                    CHECK_ERROR(SQL_ERROR, loginfo, NULL, SQL_HANDLE_STMT);
+                }
+            }
+            else if (statusptr[i] != SQL_PARAM_SUCCESS)
+            {
+                sprintf(loginfo, "statusptr[%d](%d) != SQL_PARAM_SUCCESS", i, statusptr[i]);
+                CHECK_ERROR(SQL_ERROR, loginfo, NULL, SQL_HANDLE_STMT);
+            }
+        }
+
+        retcode = SQLFreeHandle(SQL_HANDLE_STMT, hstmtinesrt);
+        sprintf((char*)loginfo, "SQLFreeHandle hstmtinesrt");
+        CHECK_ERROR(retcode, loginfo, hstmtinesrt, SQL_HANDLE_STMT);
+    }
+
+
+exit:
+    printf ("\nComplete.\n");
+
+    // Connection
+    if (hdbc != SQL_NULL_HDBC) {
+        SQLDisconnect(hdbc);
+        SQLFreeHandle(SQL_HANDLE_DBC, hdbc);
+    }
+
+    // Environment
+    if (henv != SQL_NULL_HENV)
+        SQLFreeHandle(SQL_HANDLE_ENV, henv);
+
+    return 0;
+}
+```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-3-SQLAllocHandle.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-3-SQLAllocHandle.md
new file mode 100644
index 0000000000000000000000000000000000000000..7f5e24d7016f62f43891e936990a396a2fa3c2c0
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-3-SQLAllocHandle.md
@@ -0,0 +1,45 @@
+---
+title: SQLAllocHandle
+summary: SQLAllocHandle
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLAllocHandle
+
+## Function
+
+SQLAllocHandle is used to allocate environment, connection, statement, or descriptor handles. This function replaces the deprecated ODBC 2.x functions SQLAllocEnv, SQLAllocConnect, and SQLAllocStmt.
+
+## Prototype
+
+```
+SQLRETURN SQLAllocHandle(SQLSMALLINT   HandleType,
+                         SQLHANDLE     InputHandle,
+                         SQLHANDLE     *OutputHandlePtr);
+```
+
+## Parameter
+
+**Table 1** SQLAllocHandle parameters
+
+| **Keyword**     | **Parameter Description**                                    |
+| :-------------- | :----------------------------------------------------------- |
+| HandleType      | Type of handle to be allocated by SQLAllocHandle. The value must be one of the following:<br/>- SQL_HANDLE_ENV (environment handle)<br/>- SQL_HANDLE_DBC (connection handle)<br/>- SQL_HANDLE_STMT (statement handle)<br/>- SQL_HANDLE_DESC (descriptor handle)<br/>The handle application sequence is: **SQL_HANDLE_ENV** &gt; **SQL_HANDLE_DBC** &gt; **SQL_HANDLE_STMT**. The handle applied later depends on the handle applied prior to it. |
+| InputHandle     | Existing handle to use as a context for the new handle being allocated.<br/>- If **HandleType** is **SQL_HANDLE_ENV**, this parameter is set to **SQL_NULL_HANDLE**.<br/>- If **HandleType** is **SQL_HANDLE_DBC**, this parameter value must be an environment handle.<br/>- If **HandleType** is **SQL_HANDLE_STMT** or **SQL_HANDLE_DESC**, this parameter value must be a connection handle. |
+| OutputHandlePtr | **Output parameter**: Pointer to a buffer that stores the returned handle in the newly allocated data structure. |
+
+## Return Value
+
+- **SQL_SUCCESS** indicates that the call succeeded.
+- **SQL_SUCCESS_WITH_INFO** indicates that some warning information is displayed.
+- **SQL_ERROR** indicates major errors, such as memory allocation and connection failures.
+- **SQL_INVALID_HANDLE** indicates that invalid handles were called. This value may also be returned by other APIs.
+
+## Precautions
+
+If SQLAllocHandle returns **SQL_ERROR** when it is used to allocate a non-environment handle, it sets **OutputHandlePtr** to **SQL_NULL_HDBC**, **SQL_NULL_HSTMT**, or **SQL_NULL_HDESC**. The application can then call SQLGetDiagRec, with **HandleType** and **Handle** set to the value of **IntputHandle**, to obtain the **SQLSTATE** value. The **SQLSTATE** value provides the detailed function calling information.
+
+## Example
+
+See ODBC - Examples.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-4-SQLAllocStmt.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-4-SQLAllocStmt.md
new file mode 100644
index 0000000000000000000000000000000000000000..b36225e751ec8cfe330b76cdc829b19217aef31b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-4-SQLAllocStmt.md
@@ -0,0 +1,10 @@
+---
+title: SQLAllocStmt
+summary: SQLAllocStmt
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLAllocStmt
+
+In ODBC 3.x, SQLAllocStmt was deprecated and replaced by SQLAllocHandle. For details, see SQLAllocHandle.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-5-SQLBindCol.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-5-SQLBindCol.md
new file mode 100644
index 0000000000000000000000000000000000000000..2e7ab5ce1c4e61b74145386300a9fc53ddf6b077
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-5-SQLBindCol.md
@@ -0,0 +1,51 @@
+---
+title: SQLBindCol
+summary: SQLBindCol
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLBindCol
+
+## Function
+
+SQLBindCol is used to bind columns in a result set to an application data buffer.
+
+## Prototype
+
+```
+SQLRETURN SQLBindCol(SQLHSTMT       StatementHandle,
+                     SQLUSMALLINT   ColumnNumber,
+                     SQLSMALLINT    TargetType,
+                     SQLPOINTER     TargetValuePtr,
+                     SQLLEN     BufferLength,
+                     SQLLEN     *StrLen_or_IndPtr);
+```
+
+## Parameters
+
+**Table 1** SQLBindCol parameters
+
+| **Keyword**      | **Parameter Description**                                    |
+| :--------------- | :----------------------------------------------------------- |
+| StatementHandle  | Statement handle.                                            |
+| ColumnNumber     | Number of the column to be bound. The column number starts with 0 and increases in ascending order. Column 0 is the bookmark column. If no bookmark column is set, column numbers start with 1. |
+| TargetType       | C data type in the buffer.                                   |
+| TargetValuePtr   | **Output parameter**: pointer to the buffer bound with the column. The SQLFetch function returns data in the buffer. If **TargetValuePtr** is null, **StrLen_or_IndPtr** is a valid value. |
+| BufferLength     | Length of the **TargetValuePtr** buffer in bytes.            |
+| StrLen_or_IndPtr | **Output parameter**: pointer to the length or indicator of the buffer. If **StrLen_or_IndPtr** is null, no length or indicator is used. |
+
+## Return Value
+
+- **SQL_SUCCESS** indicates that the call succeeded.
+- **SQL_SUCCESS_WITH_INFO** indicates that some warning information is displayed.
+- **SQL_ERROR** indicates major errors, such as memory allocation and connection failures.
+- **SQL_INVALID_HANDLE** indicates that invalid handles were called. This value may also be returned by other APIs.
+
+## Precautions
+
+If SQLBindCol returns **SQL_ERROR** or **SQL_SUCCESS_WITH_INFO**, the application can call SQLGetDiagRec, with **HandleType** and **Handle** set to **SQL_HANDLE_STMT** and **StatementHandle**, respectively, to obtain the **SQLSTATE** value. The **SQLSTATE** value provides the detailed function calling information.
+
+## Example
+
+See ODBC - Examples.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-6-SQLBindParameter.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-6-SQLBindParameter.md
new file mode 100644
index 0000000000000000000000000000000000000000..0278e069a0c00f4948b8721c6c685cc3fde788a6
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-6-SQLBindParameter.md
@@ -0,0 +1,59 @@
+---
+title: SQLBindParameter
+summary: SQLBindParameter
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLBindParameter
+
+## Function
+
+SQLBindParameter is used to bind parameter markers in an SQL statement to a buffer.
+
+## Prototype
+
+```
+SQLRETURN SQLBindParameter(SQLHSTMT       StatementHandle,
+                           SQLUSMALLINT   ParameterNumber,
+                           SQLSMALLINT    InputOutputType,
+                           SQLSMALLINT    ValuetType,
+                           SQLSMALLINT    ParameterType,
+                           SQLULEN    ColumnSize,
+                           SQLSMALLINT    DecimalDigits,
+                           SQLPOINTER     ParameterValuePtr,
+                           SQLLEN     BufferLength,
+                           SQLLEN     *StrLen_or_IndPtr);
+```
+
+## Parameters
+
+**Table 1** SQLBindParameter
+
+| **Keyword**       | **Parameter Description**                                    |
+| :---------------- | :----------------------------------------------------------- |
+| StatementHandle   | Statement handle.                                            |
+| ParameterNumber   | Parameter marker number, starting with 1 and increasing in ascending order. |
+| InputOutputType   | Input/output type of the parameter.                          |
+| ValueType         | C data type of the parameter.                                |
+| ParameterType     | SQL data type of the parameter.                              |
+| ColumnSize        | Size of the column or expression of the corresponding parameter marker. |
+| DecimalDigits     | Decimal digit of the column or the expression of the corresponding parameter marker. |
+| ParameterValuePtr | Pointer to the storage parameter buffer.                     |
+| BufferLength      | Length of the **ParameterValuePtr** buffer in bytes.         |
+| StrLen_or_IndPtr  | Pointer to the length or indicator of the buffer. If **StrLen_or_IndPtr** is null, no length or indicator is used. |
+
+## Return Value
+
+- **SQL_SUCCESS** indicates that the call succeeded.
+- **SQL_SUCCESS_WITH_INFO** indicates that some warning information is displayed.
+- **SQL_ERROR** indicates major errors, such as memory allocation and connection failures.
+- **SQL_INVALID_HANDLE** indicates that invalid handles were called. This value may also be returned by other APIs.
+
+## Precautions
+
+If SQLBindParameter returns **SQL_ERROR** or **SQL_SUCCESS_WITH_INFO**, the application can call SQLGetDiagRec, with **HandleType** and **Handle** set to **SQL_HANDLE_STMT** and **StatementHandle**, respectively, to obtain the **SQLSTATE** value. The **SQLSTATE** value provides the detailed function calling information.
+
+## Example
+
+See ODBC - Examples.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-7-SQLColAttribute.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-7-SQLColAttribute.md
new file mode 100644
index 0000000000000000000000000000000000000000..8290a824e1de6ce54c6ade7d5becd047a417717d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-7-SQLColAttribute.md
@@ -0,0 +1,53 @@
+---
+title: SQLColAttribute
+summary: SQLColAttribute
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLColAttribute
+
+## Function
+
+SQLColAttribute is used to return the descriptor information about a column in the result set.
+
+## Prototype
+
+```
+SQLRETURN SQLColAttibute(SQLHSTMT        StatementHandle,
+                         SQLUSMALLINT    ColumnNumber,
+                         SQLUSMALLINT    FieldIdentifier,
+                         SQLPOINTER      CharacterAtrriburePtr,
+                         SQLSMALLINT     BufferLength,
+                         SQLSMALLINT     *StringLengthPtr,
+                         SQLLEN       *NumericAttributePtr);
+```
+
+## Parameters
+
+**Table 1** SQLColAttribute parameters
+
+| **Keyword**           | **Parameter Description**                                    |
+| :-------------------- | :----------------------------------------------------------- |
+| StatementHandle       | Statement handle.                                            |
+| ColumnNumber          | Column number of the field to be queried, starting with 1 and increasing in ascending order. |
+| FieldIdentifier       | Field identifier of **ColumnNumber** in IRD.                 |
+| CharacterAttributePtr | **Output parameter**: pointer to the buffer that returns the **FieldIdentifier** value. |
+| BufferLength          | - **BufferLength** indicates the length of the buffer if **FieldIdentifier** is an ODBC-defined field and **CharacterAttributePtr** points to a string or a binary buffer.<br/>- Ignore this parameter if **FieldIdentifier** is an ODBC-defined field and **CharacterAttributePtr** points to an integer. |
+| StringLengthPtr       | **Output parameter**: pointer to a buffer in which the total number of valid bytes (for string data) is stored in ***CharacterAttributePtr**. Ignore the value of **BufferLength** if the data is not a string. |
+| NumericAttributePtr   | **Output parameter**: pointer to an integer buffer in which the value of **FieldIdentifier** in the **ColumnNumber** row of the IRD is returned. |
+
+## Return Value
+
+- **SQL_SUCCESS** indicates that the call succeeded.
+- **SQL_SUCCESS_WITH_INFO** indicates that some warning information is displayed.
+- **SQL_ERROR** indicates major errors, such as memory allocation and connection failures.
+- **SQL_INVALID_HANDLE** indicates that invalid handles were called. This value may also be returned by other APIs.
+
+## Precautions
+
+If SQLColAttribute returns **SQL_ERROR** or **SQL_SUCCESS_WITH_INFO**, the application can call SQLGetDiagRec, with **HandleType** and **Handle** set to **SQL_HANDLE_STMT** and **StatementHandle**, respectively, to obtain the **SQLSTATE** value. The **SQLSTATE** value provides the detailed function calling information.
+
+## Example
+
+See ODBC - Examples.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-8-SQLConnect.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-8-SQLConnect.md
new file mode 100644
index 0000000000000000000000000000000000000000..52c70d22388626eb0abd90d6c2f135c185504dac
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-8-SQLConnect.md
@@ -0,0 +1,54 @@
+---
+title: SQLConnect
+summary: SQLConnect
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLConnect
+
+## Function
+
+SQLConnect is used to establish a connection between a driver and a data source. After the connection is established, the connection handle can be used to access all information about the data source, including its application operating status, transaction processing status, and error information.
+
+## Prototype
+
+```
+SQLRETURN  SQLConnect(SQLHDBC        ConnectionHandle,
+                      SQLCHAR        *ServerName,
+                      SQLSMALLINT    NameLength1,
+                      SQLCHAR        *UserName,
+                      SQLSMALLINT    NameLength2,
+                      SQLCHAR        *Authentication,
+                      SQLSMALLINT    NameLength3);
+```
+
+## Parameter
+
+**Table 1** SQLConnect parameters
+
+| **Keyword**      | **Parameter Description**                         |
+| :--------------- | :------------------------------------------------ |
+| ConnectionHandle | Connection handle, obtained from SQLAllocHandle.  |
+| ServerName       | Name of the data source to connect.               |
+| NameLength1      | Length of **ServerName**.                         |
+| UserName         | Username of the database in the data source.      |
+| NameLength2      | Length of **UserName**.                           |
+| Authentication   | User password of the database in the data source. |
+| NameLength3      | Length of **Authentication**.                     |
+
+## Return Value
+
+- **SQL_SUCCESS** indicates that the call succeeded.
+- **SQL_SUCCESS_WITH_INFO** indicates that some warning information is displayed.
+- **SQL_ERROR** indicates major errors, such as memory allocation and connection failures.
+- **SQL_INVALID_HANDLE** indicates that invalid handles were called. This value may also be returned by other APIs.
+- **SQL_STILL_EXECUTING** indicates that the statement is being executed.
+
+## Precautions
+
+If SQLConnect returns **SQL_ERROR** or **SQL_SUCCESS_WITH_INFO**, the application can call SQLGetDiagRec, with **HandleType** and **Handle** set to **SQL_HANDLE_DBC** and **ConnectionHandle**, respectively, to obtain the **SQLSTATE** value. The **SQLSTATE** value provides the detailed function calling information.
+
+## Example
+
+See ODBC - Examples.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-9-SQLDisconnect.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-9-SQLDisconnect.md
new file mode 100644
index 0000000000000000000000000000000000000000..9e44b6e4031cf8f23efae55464f52ff0f6f40f71
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-9-SQLDisconnect.md
@@ -0,0 +1,41 @@
+---
+title: SQLDisconnect
+summary: SQLDisconnect
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLDisconnect
+
+## Function
+
+SQLDisconnect is used to close the connection associated with a database connection handle.
+
+## Prototype
+
+```
+SQLRETURN SQLDisconnect(SQLHDBC    ConnectionHandle);
+```
+
+## Parameter
+
+**Table 1** SQLDisconnect parameters
+
+| **Keyword**      | **Parameter Description**                        |
+| :--------------- | :----------------------------------------------- |
+| ConnectionHandle | Connection handle, obtained from SQLAllocHandle. |
+
+## Return Value
+
+- **SQL_SUCCESS** indicates that the call succeeded.
+- **SQL_SUCCESS_WITH_INFO** indicates that some warning information is displayed.
+- **SQL_ERROR** indicates major errors, such as memory allocation and connection failures.
+- **SQL_INVALID_HANDLE** indicates that invalid handles were called. This value may also be returned by other APIs.
+
+## Precautions
+
+If SQLDisconnect returns **SQL_ERROR** or **SQL_SUCCESS_WITH_INFO**, the application can call SQLGetDiagRec, with **HandleType** and **Handle** set to **SQL_HANDLE_DBC** and **ConnectionHandle**, respectively, to obtain the **SQLSTATE** value. The **SQLSTATE** value provides the detailed function calling information.
+
+## Example
+
+See ODBC - Examples.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/1-development-based-on-libpq.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/1-development-based-on-libpq.md
new file mode 100644
index 0000000000000000000000000000000000000000..0677ed340682c3d6be3d22b4538cec6d7f0a49b5
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/1-development-based-on-libpq.md
@@ -0,0 +1,10 @@
+---
+title: Development Based on libpq
+summary: Development Based on libpq
+author: Guo Huan
+date: 2021-04-27
+---
+
+# Development Based on libpq
+
+MogDB does not verify the use of libpq interfaces in application development. You are not advised to use this set of interfaces for application development, because underlying risks probably exist. You can use the ODBC or JDBC interface instead.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/1-database-connection-control-functions-overview.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/1-database-connection-control-functions-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..67d1a774f4281eca8e67a29e54ac58145c29c7ac
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/1-database-connection-control-functions-overview.md
@@ -0,0 +1,10 @@
+---
+title: Description
+summary: Description
+author: Guo Huan
+date: 2021-05-17
+---
+
+# Description
+
+Database connection control functions control the connections to MogDB servers. An application can connect to multiple servers at a time. For example, a client connects to multiple databases. Each connection is represented by a PGconn object, which is obtained from the function PQconnectdb, PQconnectdbParams, or PQsetdbLogin. Note that these functions will always return a non-null object pointer, unless there is too little memory to allocate the PGconn object. The interface for establishing a connection is stored in the PGconn object. The PQstatus function can be called to check the return value for a successful connection.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/10-PQstatus.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/10-PQstatus.md
new file mode 100644
index 0000000000000000000000000000000000000000..5d15ea90e8b3c21d4b7e50dc8f801659a4f46be2
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/10-PQstatus.md
@@ -0,0 +1,64 @@
+---
+title: PQstatus
+summary: PQstatus
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQstatus
+
+## Function
+
+PQstatus is used to return the connection status.
+
+## Prototype
+
+```
+ConnStatusType PQstatus(const PGconn *conn);
+```
+
+## Parameter
+
+**Table 1** PQ status parameter
+
+| **Keyword** | **Parameter Description**                                    |
+| :---------- | :----------------------------------------------------------- |
+| conn        | Points to the object pointer that contains the connection information. |
+
+## Return Value
+
+**ConnStatusType** indicates the connection status. The enumerated values are as follows:
+
+```
+CONNECTION_STARTED
+Waiting for the connection to be established.
+
+CONNECTION_MADE
+Connection succeeded; waiting to send
+
+CONNECTION_AWAITING_RESPONSE
+Waiting for a response from the server.
+
+CONNECTION_AUTH_OK
+Authentication received; waiting for backend startup to complete.
+
+CONNECTION_SSL_STARTUP
+Negotiating SSL encryption.
+
+CONNECTION_SETENV
+Negotiating environment-driven parameter settings.
+
+CONNECTION_OK
+Normal connection.
+
+CONNECTION_BAD
+Failed connection.
+```
+
+## Precautions
+
+The connection status can be one of the preceding values. After the asynchronous connection procedure is complete, only two of them, **CONNECTION_OK** and **CONNECTION_BAD**, can return. **CONNECTION_OK** indicates that the connection to the database is normal. **CONNECTION_BAD** indicates that the connection attempt fails. Generally, the **CONNECTION_OK** state remains until PQfinish is called. However, a communication failure may cause the connection status to become to **CONNECTION_BAD** before the connection procedure is complete. In this case, the application can attempt to call PQreset to restore the communication.
+
+## Example
+
+For details, see Example.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/2-PQconnectdbParams.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/2-PQconnectdbParams.md
new file mode 100644
index 0000000000000000000000000000000000000000..d1ed1479f3ebb2cbb78f8ca3a93661f990d0f30a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/2-PQconnectdbParams.md
@@ -0,0 +1,42 @@
+---
+title: PQconnectdbParams
+summary: PQconnectdbParams
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQconnectdbParams
+
+## Function
+
+PQconnectdbParams is used to establish a new connection with the database server.
+
+## Prototype
+
+```
+PGconn *PQconnectdbParams(const char * const *keywords,
+                          const char * const *values,
+                          int expand_dbname);
+```
+
+## Parameter
+
+**Table 1** PQconnectdbParams parameters
+
+| **Keyword**   | **Parameter Description**                                    |
+| :------------ | :----------------------------------------------------------- |
+| keywords      | An array of strings, each of which is a keyword.             |
+| values        | Value assigned to each keyword.                              |
+| expand_dbname | When **expand\_dbname** is non-zero, the **dbname** keyword value can be recognized as a connection string. Only **dbname** that first appears is expanded in this way, and any subsequent **dbname** value is treated as a database name. |
+
+## Return Value
+
+**PGconn \*** points to the object pointer that contains a connection. The memory is applied for by the function internally.
+
+## Precautions
+
+This function establishes a new database connection using the parameters taken from two NULL-terminated arrays. Unlike PQsetdbLogin, the parameter set can be extended without changing the function signature. Therefore, use of this function (or its non-blocking analogs PQconnectStartParams and PQconnectPoll) is preferred for new application programming.
+
+## Example
+
+For details, see Example.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/3-PQconnectdb.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/3-PQconnectdb.md
new file mode 100644
index 0000000000000000000000000000000000000000..cf7b3e8aa86e7b5b2695bcf4550e6cb1e05fc3db
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/3-PQconnectdb.md
@@ -0,0 +1,39 @@
+---
+title: PQconnectdb
+summary: PQconnectdb
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQconnectdb
+
+## Function
+
+PQconnectdb is used to establish a new connection with the database server.
+
+## Prototype
+
+```
+PGconn *PQconnectdb(const char *conninfo);
+```
+
+## Parameter
+
+**Table 1** PQconnectdb parameter
+
+| **Keyword** | **Parameter Description**                                    |
+| :---------- | :----------------------------------------------------------- |
+| conninfo    | Connection string. For details about the fields in the string, see Connection Characters. |
+
+## Return Value
+
+**PGconn \*** points to the object pointer that contains a connection. The memory is applied for by the function internally.
+
+## Precautions
+
+- This function establishes a new database connection using the parameters taken from the string **conninfo**.
+- The input parameter can be empty, indicating that all default parameters can be used. It can contain one or more values separated by spaces or contain a URL.
+
+## Example
+
+For details, see Example.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/4-PQconninfoParse.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/4-PQconninfoParse.md
new file mode 100644
index 0000000000000000000000000000000000000000..12ba279198b8437b40f3c448ab83d04285651e0f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/4-PQconninfoParse.md
@@ -0,0 +1,31 @@
+---
+title: PQconninfoParse
+summary: PQconninfoParse
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQconninfoParse
+
+## Function
+
+PQconninfoParse is used to return parsed connection options based on the connection.
+
+## Prototype
+
+```
+PQconninfoOption* PQconninfoParse(const char* conninfo, char** errmsg);
+```
+
+## Parameters
+
+**Table 1**
+
+| **Keyword** | **Parameter Description**                                    |
+| :---------- | :----------------------------------------------------------- |
+| conninfo    | Passed string. This parameter can be left empty. In this case, the default value is used. It can contain one or more values separated by spaces or contain a URL. |
+| errmsg      | Error information.                                           |
+
+## Return Value
+
+PQconninfoOption pointers
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/5-PQconnectStart.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/5-PQconnectStart.md
new file mode 100644
index 0000000000000000000000000000000000000000..d4214eb50a08c4cc8db762d582a2863b870e1063
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/5-PQconnectStart.md
@@ -0,0 +1,30 @@
+---
+title: PQconnectStart
+summary: PQconnectStart
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQconnectStart
+
+## Function
+
+PQconnectStart is used to establish a non-blocking connection with the database server.
+
+## Prototype
+
+```
+PGconn* PQconnectStart(const char* conninfo);
+```
+
+## Parameters
+
+**Table 1**
+
+| **Keyword** | **Parameter Description**                                    |
+| :---------- | :----------------------------------------------------------- |
+| conninfo    | String of connection information. This parameter can be left empty. In this case, the default value is used. It can contain one or more values separated by spaces or contain a URL. |
+
+## Return Value
+
+PGconn pointers
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/6-PQerrorMessage.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/6-PQerrorMessage.md
new file mode 100644
index 0000000000000000000000000000000000000000..7d03c6dedd55cc8d9d063da43d05d425dc91fa9f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/6-PQerrorMessage.md
@@ -0,0 +1,34 @@
+---
+title: PQerrorMessage
+summary: PQerrorMessage
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQerrorMessage
+
+## Function
+
+PQerrorMessage is used to return error information on a connection.
+
+## Prototype
+
+```
+char* PQerrorMessage(const PGconn* conn);
+```
+
+## Parameter
+
+**Table 1**
+
+| **Keyword** | **Parameter Description** |
+| :---------- | :------------------------ |
+| conn        | Connection handle.        |
+
+## Return Value
+
+char pointers
+
+## Example
+
+For details, see Example.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/7-PQsetdbLogin.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/7-PQsetdbLogin.md
new file mode 100644
index 0000000000000000000000000000000000000000..ee22108accd397c26240096359f9af765ebc9a0c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/7-PQsetdbLogin.md
@@ -0,0 +1,51 @@
+---
+title: PQsetdbLogin
+summary: PQsetdbLogin
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQsetdbLogin
+
+## Function
+
+PQsetdbLogin is used to establish a new connection with the database server.
+
+## Prototype
+
+```
+PGconn *PQsetdbLogin(const char *pghost,
+                     const char *pgport,
+                     const char *pgoptions,
+                     const char *pgtty,
+                     const char *dbName,
+                     const char *login,
+                     const char *pwd);
+```
+
+## Parameter
+
+**Table 1** PQsetdbLogin parameters
+
+| **Keyword** | **Parameter Description**                                    |
+| :---------- | :----------------------------------------------------------- |
+| pghost      | Name of the host to be connected. For details, see the **host** field described in Connection Characters. |
+| pgport      | Port number of the host server. For details, see the **port** field described in Connection Characters. |
+| pgoptions   | Command-line options to be sent to the server during running. For details, see the **options** field described in Connection Characters. |
+| pgtty       | This field can be ignored. (Previously, this field declares the output direction of server logs.) |
+| dbName      | Name of the database to be connected. For details, see the **dbname** field described in Connection Characters. |
+| login       | Username for connection. For details, see the **user** field described in Connection Characters. |
+| pwd         | Password used for authentication during connection. For details, see the **password** field described in Connection Characters. |
+
+## Return Value
+
+**PGconn \*** points to the object pointer that contains a connection. The memory is applied for by the function internally.
+
+## Precautions
+
+- This function is the predecessor of PQconnectdb with a fixed set of parameters. When an undefined parameter is called, its default value is used. Write NULL or an empty string for any one of the fixed parameters that is to be defaulted.
+- If the **dbName** value contains an = sign or a valid prefix in the connection URL, it is taken as a conninfo string and passed to PQconnectdb, and the remaining parameters are consistent with PQconnectdbParams parameters.
+
+## Example
+
+For details, see Example.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/8-PQfinish.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/8-PQfinish.md
new file mode 100644
index 0000000000000000000000000000000000000000..d6abc3b2d5e40ab6a84958ad11b8109630fd7f67
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/8-PQfinish.md
@@ -0,0 +1,34 @@
+---
+title: PQfinish
+summary: PQfinish
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQfinish
+
+## Function
+
+PQfinish is used to close the connection to the server and release the memory used by the PGconn object.
+
+## Prototype
+
+```
+void PQfinish(PGconn *conn);
+```
+
+## Parameter
+
+**Table 1** PQfinish parameter
+
+| **Keyword** | **Parameter Description**                                    |
+| :---------- | :----------------------------------------------------------- |
+| conn        | Points to the object pointer that contains the connection information. |
+
+## Precautions
+
+If the server connection attempt fails (as indicated by PQstatus), the application should call PQfinish to release the memory used by the PGconn object. The PGconn pointer must not be used again after PQfinish has been called.
+
+## Example
+
+For details, see Example.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/9-PQreset.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/9-PQreset.md
new file mode 100644
index 0000000000000000000000000000000000000000..fd8f48fe7eec67e337d088c8ac0a616cf8b28629
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/9-PQreset.md
@@ -0,0 +1,34 @@
+---
+title: PQreset
+summary: PQreset
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQreset
+
+## Function
+
+PQreset is used to reset the communication port to the server.
+
+## Prototype
+
+```
+void PQreset(PGconn *conn);
+```
+
+## Parameter
+
+**Table 1** PQreset parameter
+
+| **Keyword** | **Parameter Description**                                    |
+| :---------- | :----------------------------------------------------------- |
+| conn        | Points to the object pointer that contains the connection information. |
+
+## Precautions
+
+This function will close the connection to the server and attempt to establish a new connection to the same server by using all the parameters previously used. This function is applicable to fault recovery after a connection exception occurs.
+
+## Example
+
+For details, see Example.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/1-PQclear.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/1-PQclear.md
new file mode 100644
index 0000000000000000000000000000000000000000..d31b1cec3b23dcfba12db140a4c9ed4dbf350aaf
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/1-PQclear.md
@@ -0,0 +1,34 @@
+---
+title: PQclear
+summary: PQclear
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQclear
+
+## Function
+
+PQclear is used to release the storage associated with PGresult. Any query result should be released by PQclear when it is no longer needed.
+
+## Prototype
+
+```
+void PQclear(PGresult *res);
+```
+
+## Parameters
+
+**Table 1** PQclear parameter
+
+| **Keyword** | **Parameter Description**                      |
+| :---------- | :--------------------------------------------- |
+| res         | Object pointer that contains the query result. |
+
+## Precautions
+
+PGresult is not automatically released. That is, it does not disappear when a new query is submitted or even if you close the connection. To delete it, you must call PQclear. Otherwise, memory leakage occurs.
+
+## Example
+
+For details, see Example.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/10-PQntuples.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/10-PQntuples.md
new file mode 100644
index 0000000000000000000000000000000000000000..e3100a76e980ca08dd6ad832623893b1e9b0c5a7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/10-PQntuples.md
@@ -0,0 +1,34 @@
+---
+title: PQntuples
+summary: PQntuples
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQntuples
+
+## Function
+
+PQntuples is used to return the number of rows (tuples) in the query result. An overflow may occur if the return value is out of the value range allowed in a 32-bit OS.
+
+## Prototype
+
+```
+int PQntuples(const PGresult *res);
+```
+
+## Parameter
+
+**Table 1**
+
+| **Keyword** | **Parameter Description** |
+| :---------- | :------------------------ |
+| res         | Operation result handle.  |
+
+## Return Value
+
+Value of the int type
+
+## Example
+
+For details, see Example.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/11-PQprepare.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/11-PQprepare.md
new file mode 100644
index 0000000000000000000000000000000000000000..27ec13ad93ccd18e00ae688c3147de9300532f2e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/11-PQprepare.md
@@ -0,0 +1,50 @@
+---
+title: PQprepare
+summary: PQprepare
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQprepare
+
+## Function
+
+PQprepare is used to submit a request to create a prepared statement with given parameters and wait for completion.
+
+## Prototype
+
+```
+PGresult *PQprepare(PGconn *conn,
+                    const char *stmtName,
+                    const char *query,
+                    int nParams,
+                    const Oid *paramTypes);
+```
+
+## Parameters
+
+**Table 1** PQprepare parameters
+
+| **Keyword** | **Parameter Description**                                    |
+| :---------- | :----------------------------------------------------------- |
+| conn        | Points to the object pointer that contains the connection information. |
+| stmtName    | Name of **stmt** to be executed.                             |
+| query       | Query string to be executed.                                 |
+| nParams     | Parameter quantity.                                          |
+| paramTypes  | Array of the parameter type.                                 |
+
+## Return Value
+
+**PGresult** indicates the object pointer that contains the query result.
+
+## Precautions
+
+- PQprepare creates a prepared statement for later execution with PQexecPrepared. This function allows commands to be repeatedly executed, without being parsed and planned each time they are executed. PQprepare is supported only in protocol 3.0 or later. It will fail when protocol 2.0 is used.
+- This function creates a prepared statement named **stmtName** from the query string, which must contain an SQL command. **stmtName** can be **""** to create an unnamed statement. In this case, any pre-existing unnamed statement will be automatically replaced. Otherwise, this is an error if the statement name has been defined in the current session. If any parameters are used, they are referred to in the query as $1, $2, and so on. **nParams** is the number of parameters for which types are pre-specified in the array paramTypes[]. (The array pointer can be **NULL** when **nParams** is **0**.) paramTypes[] specifies the data types to be assigned to the parameter symbols by OID. If **paramTypes** is **NULL**, or any element in the array is **0**, the server assigns a data type to the parameter symbol in the same way as it does for an untyped literal string. In addition, the query can use parameter symbols whose numbers are greater than **nParams**. Data types of these symbols will also be inferred.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> You can also execute the **SQLPREPARE** statement to create a prepared statement that is used with PQexecPrepared. Although there is no libpq function of deleting a prepared statement, the **SQL DEALLOCATE** statement can be used for this purpose.
+
+## Example
+
+For details, see Example.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/12-PQresultStatus.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/12-PQresultStatus.md
new file mode 100644
index 0000000000000000000000000000000000000000..4a2958410cda31749cd23f455a0b3522066a2f20
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/12-PQresultStatus.md
@@ -0,0 +1,72 @@
+---
+title: PQresultStatus
+summary: PQresultStatus
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQresultStatus
+
+## Function
+
+PQresultStatus is used to return the result status of a command.
+
+## Prototype
+
+```
+ExecStatusType PQresultStatus(const PGresult *res);
+```
+
+## Parameter
+
+**Table 1** PQresultStatus parameter
+
+| **Keyword** | **Parameter Description**                      |
+| :---------- | :--------------------------------------------- |
+| res         | Object pointer that contains the query result. |
+
+## Return Value
+
+**PQresultStatus** indicates the command execution status. The enumerated values are as follows:
+
+```
+PQresultStatus can return one of the following values:
+PGRES_EMPTY_QUERY
+The string sent to the server was empty.
+
+PGRES_COMMAND_OK
+A command that does not return data was successfully executed.
+
+PGRES_TUPLES_OK
+A query (such as SELECT or SHOW) that returns data was successfully executed.
+
+PGRES_COPY_OUT
+Copy Out (from the server) data transfer started.
+
+PGRES_COPY_IN
+Copy In (to the server) data transfer started.
+
+PGRES_BAD_RESPONSE
+The response from the server cannot be understood.
+
+PGRES_NONFATAL_ERROR
+A non-fatal error (notification or warning) occurred.
+
+PGRES_FATAL_ERROR
+A fatal error occurred.
+
+PGRES_COPY_BOTH
+Copy In/Out (to and from the server) data transfer started. This state occurs only in streaming replication.
+
+PGRES_SINGLE_TUPLE
+PGresult contains a result tuple from the current command. This state occurs in a single-row query.
+```
+
+## Precautions
+
+- Note that the SELECT command that happens to retrieve zero rows still returns **PGRES_TUPLES_OK**. **PGRES_COMMAND_OK** is used for commands that can never return rows (such as INSERT or UPDATE, without return clauses). The result status **PGRES_EMPTY_QUERY** might indicate a bug in the client software.
+- The result status **PGRES_NONFATAL_ERROR** will never be returned directly by PQexec or other query execution functions. Instead, such results will be passed to the notice processor.
+
+## Example
+
+For details, see Example.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/2-PQexec.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/2-PQexec.md
new file mode 100644
index 0000000000000000000000000000000000000000..c752c487dfdf9a72784249550ad4ac912b0262fa
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/2-PQexec.md
@@ -0,0 +1,42 @@
+---
+title: PQexec
+summary: PQexec
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQexec
+
+## Function
+
+PQexec is used to commit a command to the server and wait for the result.
+
+## Prototype
+
+```
+PGresult *PQexec(PGconn *conn, const char *command);
+```
+
+## Parameter
+
+**Table 1** PQexec parameters
+
+| **Keyword** | **Parameter Description**                                    |
+| :---------- | :----------------------------------------------------------- |
+| conn        | Points to the object pointer that contains the connection information. |
+| command     | Query string to be executed.                                 |
+
+## Return Value
+
+**PGresult** indicates the object pointer that contains the query result.
+
+## Precautions
+
+The PQresultStatus function should be called to check the return value for any errors (including the value of a null pointer, in which **PGRES_FATAL_ERROR** will be returned). The PQerrorMessage function can be called to obtain more information about such errors.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> The command string can contain multiple SQL commands separated by semicolons (;). Multiple queries sent in a PQexec call are processed in one transaction, unless there are specific BEGIN/COMMIT commands in the query string to divide the string into multiple transactions. Note that the returned PGresult structure describes only the result of the last command executed from the string. If a command fails, the string processing stops and the returned PGresult describes the error condition.
+
+## Example
+
+For details, see Example.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/3-PQexecParams.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/3-PQexecParams.md
new file mode 100644
index 0000000000000000000000000000000000000000..f8c2120cfb02b653d1cae499a403cb59f366cee0
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/3-PQexecParams.md
@@ -0,0 +1,44 @@
+---
+title: PQexecParams
+summary: PQexecParams
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQexecParams
+
+## Function
+
+PQexecParams is used to run a command to bind one or more parameters.
+
+## Prototype
+
+```
+PGresult* PQexecParams(PGconn* conn,
+                       const char* command,
+                       int nParams,
+                       const Oid* paramTypes,
+                       const char* const* paramValues,
+                       const int* paramLengths,
+                       const int* paramFormats,
+                       int resultFormat);
+```
+
+## Parameter
+
+**Table 1**
+
+| **Keyword**  | **Parameter Description**           |
+| :----------- | :---------------------------------- |
+| conn         | Connection handle.                  |
+| command      | SQL text string.                    |
+| nParams      | Number of parameters to be bound.   |
+| paramTypes   | Types of parameters to be bound.    |
+| paramValues  | Values of parameters to be bound.   |
+| paramLengths | Parameter lengths.                  |
+| paramFormats | Parameter formats (text or binary). |
+| resultFormat | Result format (text or binary).     |
+
+## Return Value
+
+PGresult pointers
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/4-PQexecParamsBatch.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/4-PQexecParamsBatch.md
new file mode 100644
index 0000000000000000000000000000000000000000..f7e4b3c0daab95406454d0c8ebe6a710b86b4813
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/4-PQexecParamsBatch.md
@@ -0,0 +1,46 @@
+---
+title: PQexecParamsBatch
+summary: PQexecParamsBatch
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQexecParamsBatch
+
+## Function
+
+PQexecParamsBatch is used to run a command to bind batches of parameters.
+
+## Prototype
+
+```
+PGresult* PQexecParamsBatch(PGconn* conn,
+                            const char* command,
+                            int nParams,
+                            int nBatch,
+                            const Oid* paramTypes,
+                            const char* const* paramValues,
+                            const int* paramLengths,
+                            const int* paramFormats,
+                            int resultFormat);
+```
+
+## Parameter
+
+**Table 1**
+
+| **Keyword**  | **Parameter Description**           |
+| :----------- | :---------------------------------- |
+| conn         | Connection handle.                  |
+| command      | SQL text string.                    |
+| nParams      | Number of parameters to be bound.   |
+| nBatch       | Number of batch operations.         |
+| paramTypes   | Types of parameters to be bound.    |
+| paramValues  | Values of parameters to be bound.   |
+| paramLengths | Parameter lengths.                  |
+| paramFormats | Parameter formats (text or binary). |
+| resultFormat | Result format (text or binary).     |
+
+## Return Value
+
+PGresult pointers
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/5-PQexecPrepared.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/5-PQexecPrepared.md
new file mode 100644
index 0000000000000000000000000000000000000000..b2eab81bdce3baedbb35350692afc3f52e353e77
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/5-PQexecPrepared.md
@@ -0,0 +1,42 @@
+---
+title: PQexecPrepared
+summary: PQexecPrepared
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQexecPrepared
+
+## Function
+
+PQexecPrepared is used to send a request to execute a prepared statement with given parameters and wait for the result.
+
+## Prototype
+
+```
+PGresult* PQexecPrepared(PGconn* conn,
+                         const char* stmtName,
+                         int nParams,
+                         const char* const* paramValues,
+                         const int* paramLengths,
+                         const int* paramFormats,
+                         int resultFormat);
+```
+
+## Parameter
+
+**Table 1**
+
+| **Keyword**  | **Parameter Description**                                    |
+| :----------- | :----------------------------------------------------------- |
+| conn         | Connection handle.                                           |
+| stmtName     | **stmt** name, which can be set to "" or NULL to reference an unnamed statement. Otherwise, it must be the name of an existing prepared statement. |
+| nParams      | Parameter quantity.                                          |
+| paramValues  | Actual values of parameters.                                 |
+| paramLengths | Actual data lengths of parameters.                           |
+| paramFormats | Parameter formats (text or binary).                          |
+| resultFormat | Return result format (text or binary).                       |
+
+## Return Value
+
+PGresult pointers
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/6-PQexecPreparedBatch.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/6-PQexecPreparedBatch.md
new file mode 100644
index 0000000000000000000000000000000000000000..23ed2c96854988ad26cf1519fdcc2f7e77519d51
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/6-PQexecPreparedBatch.md
@@ -0,0 +1,44 @@
+---
+title: PQexecPreparedBatch
+summary: PQexecPreparedBatch
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQexecPreparedBatch
+
+## Function
+
+PQexecPreparedBatch is used to send a request to execute a prepared statement with batches of given parameters and wait for the result.
+
+## Prototype
+
+```
+PGresult* PQexecPreparedBatch(PGconn* conn,
+                              const char* stmtName,
+                              int nParams,
+                              int nBatchCount,
+                              const char* const* paramValues,
+                              const int* paramLengths,
+                              const int* paramFormats,
+                              int resultFormat);
+```
+
+## Parameter
+
+**Table 1**
+
+| **Keyword**  | **Parameter Description**                                    |
+| :----------- | :----------------------------------------------------------- |
+| conn         | Connection handle.                                           |
+| stmtName     | **stmt** name, which can be set to "" or NULL to reference an unnamed statement. Otherwise, it must be the name of an existing prepared statement. |
+| nParams      | Parameter quantity.                                          |
+| nBatchCount  | Number of batches.                                           |
+| paramValues  | Actual values of parameters.                                 |
+| paramLengths | Actual data lengths of parameters.                           |
+| paramFormats | Parameter formats (text or binary).                          |
+| resultFormat | Return result format (text or binary).                       |
+
+## Return Value
+
+PGresult pointers
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/7-PQfname.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/7-PQfname.md
new file mode 100644
index 0000000000000000000000000000000000000000..f62035545dacd5991ec91d386f339a0ad52acbc8
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/7-PQfname.md
@@ -0,0 +1,36 @@
+---
+title: PQfname
+summary: PQfname
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQfname
+
+## Function
+
+PQfname is used to return the column name associated with the given column number. Column numbers start from 0. The caller should not release the result directly. The result will be released when the associated PGresult handle is passed to PQclear.
+
+## Prototype
+
+```
+char *PQfname(const PGresult *res,
+              int column_number);
+```
+
+## Parameter
+
+**Table 1**
+
+| **Keyword**   | **Parameter Description** |
+| :------------ | :------------------------ |
+| res           | Operation result handle.  |
+| column_number | Number of columns.        |
+
+## Return Value
+
+char pointers
+
+## Example
+
+For details, see Example.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/8-PQgetvalue.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/8-PQgetvalue.md
new file mode 100644
index 0000000000000000000000000000000000000000..86a7fa972a42441e7a1e0d7847afaf391e21c14d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/8-PQgetvalue.md
@@ -0,0 +1,42 @@
+---
+title: PQgetvalue
+summary: PQgetvalue
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQgetvalue
+
+## Function
+
+PQgetvalue is used to return a single field value of one row of a PGresult. Row and column numbers start from 0. The caller should not release the result directly. The result will be released when the associated PGresult handle is passed to PQclear.
+
+## Prototype
+
+```
+char *PQgetvalue(const PGresult *res,
+                 int row_number,
+                 int column_number);
+```
+
+## Parameter
+
+**Table 1**
+
+| **Keyword**   | **Parameter Description** |
+| :------------ | :------------------------ |
+| res           | Operation result handle.  |
+| row_number    | Number of rows.           |
+| column_number | Number of columns.        |
+
+## Return Value
+
+For data in text format, the value returned by PQgetvalue is a null-terminated string representation of the field value.
+
+For binary data, the value is a binary representation determined by the typsend and typreceive functions of the data type.
+
+If this field is left blank, an empty string is returned.
+
+## Example
+
+For details, see Example.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/9-PQnfields.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/9-PQnfields.md
new file mode 100644
index 0000000000000000000000000000000000000000..459ecaa8aa32218edcb98e0c5e3dbe3b495fd18d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/9-PQnfields.md
@@ -0,0 +1,34 @@
+---
+title: PQnfields
+summary: PQnfields
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQnfields
+
+## Function
+
+PQnfields is used to return the number of columns (fields) in each row of the query result.
+
+## Prototype
+
+```
+int PQnfields(const PGresult *res);
+```
+
+## Parameter
+
+**Table 1**
+
+| **Keyword** | **Parameter Description** |
+| :---------- | :------------------------ |
+| res         | Operation result handle.  |
+
+## Return Value
+
+Value of the int type
+
+## Example
+
+For details, see Example.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/1-functions-for-asynchronous-command-processing-overview.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/1-functions-for-asynchronous-command-processing-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..df0fbcb1114ea986a47ee14e8da2aa4194ab269f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/1-functions-for-asynchronous-command-processing-overview.md
@@ -0,0 +1,17 @@
+---
+title: Description
+summary: Description
+author: Guo Huan
+date: 2021-05-17
+---
+
+# Description
+
+The PQexec function is adequate for committing commands in common, synchronous applications. However, it has several defects, which may be important to some users:
+
+- PQexec waits for the end of the command, but the application may have other work to do (for example, maintaining a user interface). In this case, PQexec would not want to be blocked to wait for the response.
+- As the client application is suspended while waiting for the result, it is difficult for the application to determine whether to cancel the ongoing command.
+- PQexec can return only one PGresult structure. If the committed command string contains multiple SQL commands, all the PGresult structures except the last PGresult are discarded by PQexec.
+- PQexec always collects the entire result of the command and caches it in a PGresult. Although this mode simplifies the error handling logic for applications, it is impractical for results that contain multiple rows.
+
+Applications that do not want to be restricted by these limitations can use the following functions that PQexec is built from: PQsendQuery and PQgetResult. The functions PQsendQueryParams, PQsendPrepare, and PQsendQueryPrepared can also be used with PQgetResult.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/2-PQsendQuery.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/2-PQsendQuery.md
new file mode 100644
index 0000000000000000000000000000000000000000..c8237c713138fe440129269872011057a531536a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/2-PQsendQuery.md
@@ -0,0 +1,39 @@
+---
+title: PQsendQuery
+summary: PQsendQuery
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQsendQuery
+
+## Function
+
+PQsendQuery is used to commit a command to the server without waiting for the result. If the query is successful, **1** is returned. Otherwise, **0** is returned.
+
+## Prototype
+
+```c
+int PQsendQuery(PGconn *conn, const char *command);
+```
+
+## Parameter
+
+**Table 1** PQsendQuery parameters
+
+| **Keyword** | **Parameter Description**                                    |
+| :---------- | :----------------------------------------------------------- |
+| conn        | Points to the object pointer that contains the connection information. |
+| command     | Query string to be executed.                                 |
+
+## Return Value
+
+**int** indicates the execution result. **1** indicates successful execution and **0** indicates an execution failure. The failure cause is stored in **conn-&gt;errorMessage**.
+
+## Precautions
+
+After PQsendQuery is successfully called, call PQgetResult one or more times to obtain the results. PQsendQuery cannot be called again (on the same connection) until PQgetResult returns a null pointer, indicating that the command execution is complete.
+
+## Example
+
+For details, see Example.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/3-PQsendQueryParams.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/3-PQsendQueryParams.md
new file mode 100644
index 0000000000000000000000000000000000000000..d8e5c99f9f3437c389dce7cade907d7ee417f12e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/3-PQsendQueryParams.md
@@ -0,0 +1,52 @@
+---
+title: PQsendQueryParams
+summary: PQsendQueryParams
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQsendQueryParams
+
+## Function
+
+PQsendQueryParams is used to commit a command and separate parameters to the server without waiting for the result.
+
+## Prototype
+
+```c
+int PQsendQueryParams(PGconn *conn,
+                      const char *command,
+                      int nParams,
+                      const Oid *paramTypes,
+                      const char * const *paramValues,
+                      const int *paramLengths,
+                      const int *paramFormats,
+                      int resultFormat);
+```
+
+## Parameter
+
+**Table 1** PQsendQueryParams parameters
+
+| **Keyword**  | **Parameter Description**                                    |
+| :----------- | :----------------------------------------------------------- |
+| conn         | Points to the object pointer that contains the connection information. |
+| command      | Query string to be executed.                                 |
+| nParams      | Parameter quantity.                                          |
+| paramTypes   | Parameter type.                                              |
+| paramValues  | Parameter value.                                             |
+| paramLengths | Parameter length.                                            |
+| paramFormats | Parameter format.                                            |
+| resultFormat | Result format.                                               |
+
+## Return Value
+
+**int** indicates the execution result. **1** indicates successful execution and **0** indicates an execution failure. The failure cause is stored in **conn-&gt;errorMessage**.
+
+## Precautions
+
+PQsendQueryParams is equivalent to PQsendQuery. The only difference is that query parameters can be specified separately from the query string. PQsendQueryParams parameters are handled in the same way as PQexecParams parameters. Like PQexecParams, PQsendQueryParams cannot work on connections using protocol 2.0 and it allows only one command in the query string.
+
+## Example
+
+For details, see Example.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/4-PQsendPrepare.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/4-PQsendPrepare.md
new file mode 100644
index 0000000000000000000000000000000000000000..550c4f1ea98aa02fd94db396a62bc9272aef3aa8
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/4-PQsendPrepare.md
@@ -0,0 +1,46 @@
+---
+title: PQsendPrepare
+summary: PQsendPrepare
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQsendPrepare
+
+## Function
+
+PQsendPrepare is used to send a request to create a prepared statement with given parameters, without waiting for completion.
+
+## Prototype
+
+```c
+int PQsendPrepare(PGconn *conn,
+                  const char *stmtName,
+                  const char *query,
+                  int nParams,
+                  const Oid *paramTypes);
+```
+
+## Parameters
+
+**Table 1** PQsendPrepare parameters
+
+| **Keyword** | **Parameter Description**                                    |
+| :---------- | :----------------------------------------------------------- |
+| conn        | Points to the object pointer that contains the connection information. |
+| stmtName    | Name of **stmt** to be executed.                             |
+| query       | Query string to be executed.                                 |
+| nParams     | Parameter quantity.                                          |
+| paramTypes  | Array of the parameter type.                                 |
+
+## Return Value
+
+**int** indicates the execution result. **1** indicates successful execution and **0** indicates an execution failure. The failure cause is stored in **conn-&gt;errorMessage**.
+
+## Precautions
+
+PQsendPrepare is an asynchronous version of PQprepare. If it can dispatch a request, **1** is returned. Otherwise, **0** is returned. After a successful calling of PQsendPrepare, call PQgetResult to check whether the server successfully created the prepared statement. PQsendPrepare parameters are handled in the same way as PQprepare parameters. Like PQprepare, PQsendPrepare cannot work on connections using protocol 2.0.
+
+## Example
+
+For details, see Example.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/5-PQsendQueryPrepared.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/5-PQsendQueryPrepared.md
new file mode 100644
index 0000000000000000000000000000000000000000..4ce131cc997b91c09897c106ec204977bf8fbac5
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/5-PQsendQueryPrepared.md
@@ -0,0 +1,50 @@
+---
+title: PQsendQueryPrepared
+summary: PQsendQueryPrepared
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQsendQueryPrepared
+
+## Function
+
+PQsendQueryPrepared is used to send a request to execute a prepared statement with given parameters, without waiting for the result.
+
+## Prototype
+
+```c
+int PQsendQueryPrepared(PGconn *conn,
+                        const char *stmtName,
+                        int nParams,
+                        const char * const *paramValues,
+                        const int *paramLengths,
+                        const int *paramFormats,
+                        int resultFormat);
+```
+
+## Parameters
+
+**Table 1** PQsendQueryPrepared parameters
+
+| **Keyword**  | **Parameter Description**                                    |
+| :----------- | :----------------------------------------------------------- |
+| conn         | Points to the object pointer that contains the connection information. |
+| stmtName     | Name of **stmt** to be executed.                             |
+| nParams      | Parameter quantity.                                          |
+| paramValues  | Parameter value.                                             |
+| paramLengths | Parameter length.                                            |
+| paramFormats | Parameter format.                                            |
+| resultFormat | Result format.                                               |
+
+## Return Value
+
+**int** indicates the execution result. **1** indicates successful execution and **0** indicates an execution failure. The failure cause is stored in **conn-&gt;errorMessage**.
+
+## Precautions
+
+PQsendQueryPrepared is similar to PQsendQueryParams, but the command to be executed is specified by naming a previously-prepared statement, instead of providing a query string. PQsendQueryPrepared parameters are handled in the same way as PQexecPrepared parameters. Like PQexecPrepared, PQsendQueryPrepared cannot work on connections using protocol 2.0.
+
+## Example
+
+For details, see Example.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/6-PQflush.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/6-PQflush.md
new file mode 100644
index 0000000000000000000000000000000000000000..485875afc9bba8f3479e9a60ebc3eb8c0eb0ed2b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/6-PQflush.md
@@ -0,0 +1,38 @@
+---
+title: PQflush
+summary: PQflush
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQflush
+
+## Function
+
+PQflush is used to try to flush any queued output data to the server.
+
+## Prototype
+
+```c
+Cint PQflush(PGconn *conn);
+```
+
+## Parameter
+
+**Table 1** PQflush parameter
+
+| **Keyword** | **Parameter Description**                                    |
+| :---------- | :----------------------------------------------------------- |
+| conn        | Points to the object pointer that contains the connection information. |
+
+## Return Value
+
+**int** indicates the execution result. If the operation is successful (or the send queue is empty), **0** is returned. If the operation fails, **-1** is returned. If all data in the send queue fails to be sent, **1** is returned. (This case occurs only when the connection is non-blocking.) The failure cause is stored in **conn-&gt;error_message**.
+
+## Precautions
+
+Call PQflush after sending any command or data over a non-blocking connection. If **1** is returned, wait for the socket to become read- or write-ready. If the socket becomes write-ready, call PQflush again. If the socket becomes read-ready, call PQconsumeInput and then call PQflush again. Repeat the operation until the value **0** is returned for PQflush. (It is necessary to check for read-ready and drain the input using PQconsumeInput. This is because the server can block trying to send us data, for example, notification messages, and will not read our data until we read it.) Once PQflush returns **0**, wait for the socket to be read-ready and then read the response as described above.
+
+## Example
+
+For details, see Example.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/4-functions-for-canceling-queries-in-progress/1-PQgetCancel.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/4-functions-for-canceling-queries-in-progress/1-PQgetCancel.md
new file mode 100644
index 0000000000000000000000000000000000000000..234b1051b81532f0a6a84885251b9599579d3346
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/4-functions-for-canceling-queries-in-progress/1-PQgetCancel.md
@@ -0,0 +1,38 @@
+---
+title: PQgetCancel
+summary: PQgetCancel
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQgetCancel
+
+## Function
+
+PQgetCancel is used to create a data structure that contains the information required to cancel a command issued through a specific database connection.
+
+## Prototype
+
+```c
+PGcancel *PQgetCancel(PGconn *conn);
+```
+
+## Parameter
+
+**Table 1** PQgetCancel parameter
+
+| **Keyword** | **Parameter Description**                                    |
+| :---------- | :----------------------------------------------------------- |
+| conn        | Points to the object pointer that contains the connection information. |
+
+## Return Value
+
+**PGcancel** points to the object pointer that contains the cancel information.
+
+## Precautions
+
+PQgetCancel creates a PGcancel object for a given PGconn connection object. If the given connection object (**conn**) is NULL or an invalid connection, PQgetCancel will return NULL. The PGcancel object is an opaque structure that cannot be directly accessed by applications. It can be transferred only to PQcancel or PQfreeCancel.
+
+## Example
+
+For details, see Example.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/4-functions-for-canceling-queries-in-progress/2-PQfreeCancel.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/4-functions-for-canceling-queries-in-progress/2-PQfreeCancel.md
new file mode 100644
index 0000000000000000000000000000000000000000..3df29bc62ea1c9870179d967dcb595f3bc19a543
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/4-functions-for-canceling-queries-in-progress/2-PQfreeCancel.md
@@ -0,0 +1,34 @@
+---
+title: PQfreeCancel
+summary: PQfreeCancel
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQfreeCancel
+
+## Function
+
+PQfreeCancel is used to release the data structure created by PQgetCancel.
+
+## Prototype
+
+```c
+void PQfreeCancel(PGcancel *cancel);
+```
+
+## Parameter
+
+**Table 1** PQfreeCancel parameter
+
+| **Keyword** | **Parameter Description**                                    |
+| :---------- | :----------------------------------------------------------- |
+| cancel      | Points to the object pointer that contains the cancel information. |
+
+## Precautions
+
+PQfreeCancel releases a data object previously created by PQgetCancel.
+
+## Example
+
+For details, see Example.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/4-functions-for-canceling-queries-in-progress/3-PQcancel.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/4-functions-for-canceling-queries-in-progress/3-PQcancel.md
new file mode 100644
index 0000000000000000000000000000000000000000..1a71f6b718054f756db1770cfb69807ecd846436
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/4-functions-for-canceling-queries-in-progress/3-PQcancel.md
@@ -0,0 +1,41 @@
+---
+title: PQcancel
+summary: PQcancel
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQcancel
+
+## Function
+
+PQcancel is used to request the server to abandon processing of the current command.
+
+## Prototype
+
+```c
+int PQcancel(PGcancel *cancel, char *errbuf, int errbufsize);
+```
+
+## Parameter
+
+**Table 1** PQcancel parameters
+
+| **Keyword** | **Parameter Description**                                    |
+| :---------- | :----------------------------------------------------------- |
+| cancel      | Points to the object pointer that contains the cancel information. |
+| errbuf      | Buffer for storing error information.                        |
+| errbufsize  | Size of the buffer for storing error information.            |
+
+## Return Value
+
+**int** indicates the execution result. **1** indicates successful execution and **0** indicates an execution failure. The failure cause is stored in **errbuf**.
+
+## Precautions
+
+- Successful sending does not guarantee that the request will have any effect. If the cancellation is valid, the current command is terminated early and an error is returned. If the cancellation fails (for example, because the server has processed the command), no result is returned.
+- If **errbuf** is a local variable in a signal handler, you can safely call PQcancel from the signal handler. For PQcancel, the PGcancel object is read-only, so it can also be called from a thread that is separate from the thread that is operating the PGconn object.
+
+## Example
+
+For details, see Example.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/5-libpq-example.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/5-libpq-example.md
new file mode 100644
index 0000000000000000000000000000000000000000..131cd599ec1ba2bbf13181cc95a0ad85dbb2202f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/5-libpq-example.md
@@ -0,0 +1,282 @@
+---
+title: Example
+summary: Example
+author: Guo Huan
+date: 2021-05-17
+---
+
+# Example
+
+## Code for Common Functions
+
+Example 1:
+
+```c
+/*
+ * testlibpq.c
+ */
+#include <stdio.h>
+#include <stdlib.h>
+#include <libpq-fe.h>
+
+static void
+exit_nicely(PGconn *conn)
+{
+    PQfinish(conn);
+    exit(1);
+}
+
+int
+main(int argc, char **argv)
+{
+    const char *conninfo;
+    PGconn     *conn;
+    PGresult   *res;
+    int         nFields;
+    int         i,j;
+
+    /*
+     * This value is used when the user provides the value of the conninfo character string in the command line.
+     * Otherwise, the environment variables or the default values
+     * are used for all other connection parameters.
+     */
+    if (argc > 1)
+        conninfo = argv[1];
+    else
+        conninfo = "dbname=postgres port=42121 host='10.44.133.171' application_name=test connect_timeout=5 sslmode=allow user='test' password='test_1234'";
+
+    /* Connect to the database. */
+    conn = PQconnectdb(conninfo);
+
+    /* Check whether the backend connection has been successfully established. */
+    if (PQstatus(conn) != CONNECTION_OK)
+    {
+        fprintf(stderr, "Connection to database failed: %s",
+                PQerrorMessage(conn));
+        exit_nicely(conn);
+    }
+
+    /*
+     * Since a cursor is used in the test case, a transaction block is required.
+     * Put all data in one "select * from pg_database"
+     * PQexec() is too simple and is not recommended.
+     */
+
+    /* Start a transaction block. */
+    res = PQexec(conn, "BEGIN");
+    if (PQresultStatus(res) != PGRES_COMMAND_OK)
+    {
+        fprintf(stderr, "BEGIN command failed: %s", PQerrorMessage(conn));
+        PQclear(res);
+        exit_nicely(conn);
+    }
+
+    /*
+     * PQclear PGresult should be executed when it is no longer needed, to avoid memory leakage.
+     */
+    PQclear(res);
+
+    /*
+     * Fetch data from the pg_database system catalog.
+     */
+    res = PQexec(conn, "DECLARE myportal CURSOR FOR select * from pg_database");
+    if (PQresultStatus(res) != PGRES_COMMAND_OK)
+    {
+        fprintf(stderr, "DECLARE CURSOR failed: %s", PQerrorMessage(conn));
+        PQclear(res);
+        exit_nicely(conn);
+    }
+    PQclear(res);
+
+    res = PQexec(conn, "FETCH ALL in myportal");
+    if (PQresultStatus(res) != PGRES_TUPLES_OK)
+    {
+        fprintf(stderr, "FETCH ALL failed: %s", PQerrorMessage(conn));
+        PQclear(res);
+        exit_nicely(conn);
+    }
+
+    /* First, print out the attribute name. */
+    nFields = PQnfields(res);
+    for (i = 0; i < nFields; i++)
+        printf("%-15s", PQfname(res, i));
+    printf("\n\n");
+
+    /* Print lines. */
+    for (i = 0; i < PQntuples(res); i++)
+    {
+        for (j = 0; j < nFields; j++)
+            printf("%-15s", PQgetvalue(res, i, j));
+        printf("\n");
+    }
+
+    PQclear(res);
+
+    /* Close the portal. We do not need to check for errors. */
+    res = PQexec(conn, "CLOSE myportal");
+    PQclear(res);
+
+    /* End the transaction. */
+    res = PQexec(conn, "END");
+    PQclear(res);
+
+    /* Close the database connection and clean up the database. */
+    PQfinish(conn);
+
+    return 0;
+}
+```
+
+<br/>
+
+Example 2:
+
+```c
+/*
+ * testlibpq2.c
+ *      Test out-of-line parameters and binary I/Os.
+ *
+ * Before running this example, run the following command to populate a database:
+ *
+ *
+ * CREATE TABLE test1 (i int4, t text);
+ *
+  * INSERT INTO test1 values (2, 'ho there');
+ *
+ * The expected output is as follows:
+ *
+ *
+ * tuple 0: got
+ *  i = (4 bytes) 2
+ *  t = (8 bytes) 'ho there'
+ *
+ */
+#include <stdio.h>
+#include <stdlib.h>
+#include <string.h>
+#include <sys/types.h>
+#include <libpq-fe.h>
+
+/* for ntohl/htonl */
+#include <netinet/in.h>
+#include <arpa/inet.h>
+
+static void
+exit_nicely(PGconn *conn)
+{
+    PQfinish(conn);
+    exit(1);
+}
+
+/*
+ * This function is used to print out the query results. The results are in binary format
+* and fetched from the table created in the comment above.
+ */
+static void
+show_binary_results(PGresult *res)
+{
+    int         i;
+    int         i_fnum,
+                t_fnum;
+
+    /* Use PQfnumber to avoid assumptions about field order in the result. */
+    i_fnum = PQfnumber(res, "i");
+    t_fnum = PQfnumber(res, "t");
+
+    for (i = 0; i < PQntuples(res); i++)
+    {
+        char       *iptr;
+        char       *tptr;
+        int         ival;
+
+        /* Obtain the field value. (Ignore the possibility that they may be null). */
+        iptr = PQgetvalue(res, i, i_fnum);
+        tptr = PQgetvalue(res, i, t_fnum);
+
+        /*
+         * The binary representation of INT4 is the network byte order,
+         * which is better to be replaced with the local byte order.
+         */
+        ival = ntohl(*((uint32_t *) iptr));
+
+        /*
+         * The binary representation of TEXT is text. Since libpq can append a zero byte to it,
+         *  and think of it as a C string.
+         *
+         */
+
+        printf("tuple %d: got\n", i);
+        printf(" i = (%d bytes) %d\n",
+               PQgetlength(res, i, i_fnum), ival);
+        printf(" t = (%d bytes) '%s'\n",
+               PQgetlength(res, i, t_fnum), tptr);
+        printf("\n\n");
+    }
+}
+
+int
+main(int argc, char **argv)
+{
+    const char *conninfo;
+    PGconn     *conn;
+    PGresult   *res;
+    const char *paramValues[1];
+    int         paramLengths[1];
+    int         paramFormats[1];
+    uint32_t    binaryIntVal;
+
+    /*
+     * If the user provides a parameter on the command line,
+     * The value of this parameter is a conninfo character string. Otherwise,
+    * Use environment variables or default values.
+     */
+    if (argc > 1)
+        conninfo = argv[1];
+    else
+        conninfo = "dbname=postgres port=42121 host='10.44.133.171' application_name=test connect_timeout=5 sslmode=allow user='test' password='test_1234'";
+
+    /* Connect to the database. */
+    conn = PQconnectdb(conninfo);
+
+     /* Check whether the connection to the server was successfully established. */
+    if (PQstatus(conn) != CONNECTION_OK)
+    {
+        fprintf(stderr, "Connection to database failed: %s",
+                PQerrorMessage(conn));
+        exit_nicely(conn);
+    }
+
+    /* Convert the integer value "2" to the network byte order. */
+    binaryIntVal = htonl((uint32_t) 2);
+
+    /* Set the parameter array for PQexecParams. */
+    paramValues[0] = (char *) &binaryIntVal;
+    paramLengths[0] = sizeof(binaryIntVal);
+    paramFormats[0] = 1;        /* Binary */
+
+    res = PQexecParams(conn,
+                       "SELECT * FROM test1 WHERE i = $1::int4",
+                       1,       /* One parameter */
+                       NULL,    /* Enable the backend to deduce the parameter type. */
+                       paramValues,
+                       paramLengths,
+                       paramFormats,
+                       1);      /* require binary results. */
+
+    if (PQresultStatus(res) != PGRES_TUPLES_OK)
+    {
+        fprintf(stderr, "SELECT failed: %s", PQerrorMessage(conn));
+        PQclear(res);
+        exit_nicely(conn);
+    }
+
+    show_binary_results(res);
+
+    PQclear(res);
+
+    /* Close the database connection and clean up the database. */
+    PQfinish(conn);
+
+    return 0;
+}
+```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/6-connection-characters.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/6-connection-characters.md
new file mode 100644
index 0000000000000000000000000000000000000000..8dae6386d2e085b45644484f66255eafca2960cf
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/6-connection-characters.md
@@ -0,0 +1,27 @@
+---
+title: Connection Characters
+summary: Connection Characters
+author: Guo Huan
+date: 2021-05-17
+---
+
+# Connection Characters
+
+**Table 1** Connection strings
+
+| Character String    | Description                                                  |
+| :------------------ | :----------------------------------------------------------- |
+| host                | Name of the host to connect to. If the host name starts with a slash (/), Unix-domain socket communications instead of TCP/IP communications are used. The value is the directory where the socket file is stored. If **host** is not specified, the default behavior is to connect to the Unix-domain socket in the **/tmp** directory (or the socket directory specified during MogDB installation). On a machine without a Unix-domain socket, the default behavior is to connect to **localhost**. |
+| hostaddr            | IP address of the host to connect to. The value is in standard IPv4 address format, for example, 172.28.40.9. If your machine supports IPv6, IPv6 address can also be used. If a non-null string is specified, TCP/IP communications are used.<br/>Replacing **host** with **hostaddr** can prevent applications from querying host names, which may be important for applications with time constraints. However, a host name is required for GSSAPI or SSPI authentication methods. Therefore, the following rules are used:<br/>1. If **host** is specified but **hostaddr** is not, a query for the host name will be executed.<br/>2. If **hostaddr** is specified but **host** is not, the value of **hostaddr** is the server network address. If the host name is required by authentication, the connection attempt fails.<br/>3. If both **host** and **hostaddr** are specified, the value of **hostaddr** is the server network address. The value of **host** is ignored unless it is required by authentication, in which case it is used as the host name.<br/>NOTICE:<br/>- If **host** is not the server name in the network address specified by **hostaddr**, the authentication may fail.<br/>- If neither **host** nor **hostaddr** is specified, libpq will use a local Unix-domain socket for connection. If the machine does not have a Unix-domain socket, it will attempt to connect to **localhost**. |
+| port                | Port number of the host server, or the socket file name extension for Unix-domain connections. |
+| user                | Name of the user to connect as. By default, the username is the same as the operating system name of the user running the application. |
+| dbname              | Database name. The default value is the same as the username. |
+| password            | Password to be used if the server requires password authentication. |
+| connect_timeout     | Maximum timeout period of the connection, in seconds (in decimal integer string). The value **0** or null indicates infinity. You are not advised to set the connection timeout period to a value less than 2 seconds. |
+| client_encoding     | Client encoding for the connection. In addition to the values accepted by the corresponding server options, you can use **auto** to determine the correct encoding from the current environment in the client (the LC_CTYPE environment variable in the Unix system). |
+| options             | Adds command-line options to send to the server at runtime.  |
+| application_name    | Current user identity.                                       |
+| keepalives          | Whether TCP keepalive is enabled on the client side. The default value is **1**, indicating that the function is enabled. The value **0** indicates that the function is disabled. Ignore this parameter for Unix-domain connections. |
+| keepalives_idle     | The number of seconds of inactivity after which TCP should send a keepalive message to the server. The value **0** indicates that the default value is used. Ignore this parameter for Unix-domain connections or if keep-alive is disabled. |
+| keepalives_interval | The number of seconds after which a TCP keepalive message that is not acknowledged by the server should be retransmitted. The value **0** indicates that the default value is used. Ignore this parameter for Unix-domain connections or if keep-alive is disabled. |
+| keepalives_count    | Adds command-line options to send to the server at runtime. For example, adding **-c comm_debug_mode=off** to set the value of the GUC parameter **comm_debug_mode** to **off**. |
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/1-psycopg-based-development.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/1-psycopg-based-development.md
new file mode 100644
index 0000000000000000000000000000000000000000..a144c443330c0224b7923561984827a8cffb2d41
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/1-psycopg-based-development.md
@@ -0,0 +1,19 @@
+---
+title: Psycopg-Based Development
+summary: Psycopg-Based Development
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# Psycopg-Based Development
+
+Psycopg is a Python API used to execute SQL statements and provides a unified access API for PostgreSQL and GaussDB. Applications can perform data operations based on psycopg. Psycopg2 is an encapsulation of libpq and is implemented using the C language, which is efficient and secure. It provides cursors on both clients and servers, asynchronous communication and notification, and the COPY TO and COPY FROM functions. Psycopg2 supports multiple types of Python out-of-the-box and adapts to PostgreSQL data types. Through the flexible object adaptation system, you can extend and customize the adaptation. Psycopg2 is compatible with Unicode and Python 3.
+
+MogDB supports the psycopg2 feature and allows psycopg2 to be connected in SSL mode.
+
+**Table 1** Platforms supported by Psycopg
+
+| OS          | Platform |
+| :---------- | :------- |
+| EulerOS 2.5 | x86_64   |
+| EulerOS 2.8 | ARM64    |
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/10.1-example-common-operations.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/10.1-example-common-operations.md
new file mode 100644
index 0000000000000000000000000000000000000000..42e76fe7977319efe2bd44c5a5dbc6a5d077f311
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/10.1-example-common-operations.md
@@ -0,0 +1,243 @@
+---
+title: Common Operations
+summary: Common Operations
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# Examples: Common Operations
+
+## Example 1
+
+The following illustrates how to develop applications based on MogDB JDBC interfaces.
+
+```
+//DBtest.java
+// This example illustrates the main processes of JDBC-based development, covering database connection creation, table creation, and data insertion.
+
+import java.sql.Connection;
+import java.sql.DriverManager;
+import java.sql.PreparedStatement;
+import java.sql.SQLException;
+import java.sql.Statement;
+import java.sql.CallableStatement;
+
+public class DBTest {
+
+  // Create a database connection.
+  public static Connection GetConnection(String username, String passwd) {
+    String driver = "org.postgresql.Driver";
+    String sourceURL = "jdbc:postgresql://localhost:8000/postgres";
+    Connection conn = null;
+    try {
+      // Load the database driver.
+      Class.forName(driver).newInstance();
+    } catch (Exception e) {
+      e.printStackTrace();
+      return null;
+    }
+
+    try {
+      // Create a database connection.
+      conn = DriverManager.getConnection(sourceURL, username, passwd);
+      System.out.println("Connection succeed!");
+    } catch (Exception e) {
+      e.printStackTrace();
+      return null;
+    }
+
+    return conn;
+  };
+
+  // Run a common SQL statement to create table customer_t1.
+  public static void CreateTable(Connection conn) {
+    Statement stmt = null;
+    try {
+      stmt = conn.createStatement();
+
+      // Run a common SQL statement.
+      int rc = stmt
+          .executeUpdate("CREATE TABLE customer_t1(c_customer_sk INTEGER, c_customer_name VARCHAR(32));");
+
+      stmt.close();
+    } catch (SQLException e) {
+      if (stmt != null) {
+        try {
+          stmt.close();
+        } catch (SQLException e1) {
+          e1.printStackTrace();
+        }
+      }
+      e.printStackTrace();
+    }
+  }
+
+  // Run a prepared statement to insert data in batches.
+  public static void BatchInsertData(Connection conn) {
+    PreparedStatement pst = null;
+
+    try {
+      // Generate a prepared statement.
+      pst = conn.prepareStatement("INSERT INTO customer_t1 VALUES (?,?)");
+      for (int i = 0; i < 3; i++) {
+        // Add parameters.
+        pst.setInt(1, i);
+        pst.setString(2, "data " + i);
+        pst.addBatch();
+      }
+      // Perform batch processing.
+      pst.executeBatch();
+      pst.close();
+    } catch (SQLException e) {
+      if (pst != null) {
+        try {
+          pst.close();
+        } catch (SQLException e1) {
+        e1.printStackTrace();
+        }
+      }
+      e.printStackTrace();
+    }
+  }
+
+  // Run a prepared statement to update data.
+  public static void ExecPreparedSQL(Connection conn) {
+    PreparedStatement pstmt = null;
+    try {
+      pstmt = conn
+          .prepareStatement("UPDATE customer_t1 SET c_customer_name = ? WHERE c_customer_sk = 1");
+      pstmt.setString(1, "new Data");
+      int rowcount = pstmt.executeUpdate();
+      pstmt.close();
+    } catch (SQLException e) {
+      if (pstmt != null) {
+        try {
+          pstmt.close();
+        } catch (SQLException e1) {
+          e1.printStackTrace();
+        }
+      }
+      e.printStackTrace();
+    }
+  }
+
+
+// Run a stored procedure.
+  public static void ExecCallableSQL(Connection conn) {
+    CallableStatement cstmt = null;
+    try {
+
+      cstmt=conn.prepareCall("{? = CALL TESTPROC(?,?,?)}");
+      cstmt.setInt(2, 50);
+      cstmt.setInt(1, 20);
+      cstmt.setInt(3, 90);
+      cstmt.registerOutParameter(4, Types.INTEGER);  // Register an OUT parameter of the integer type.
+      cstmt.execute();
+      int out = cstmt.getInt(4);  // Obtain the OUT parameter.
+      System.out.println("The CallableStatment TESTPROC returns:"+out);
+      cstmt.close();
+    } catch (SQLException e) {
+      if (cstmt != null) {
+        try {
+          cstmt.close();
+        } catch (SQLException e1) {
+          e1.printStackTrace();
+        }
+      }
+      e.printStackTrace();
+    }
+  }
+
+
+  /**
+   * Main process. Call static methods one by one.
+   * @param args
+  */
+  public static void main(String[] args) {
+    // Create a database connection.
+    Connection conn = GetConnection("tester", "Password1234");
+
+    // Create a table.
+    CreateTable(conn);
+
+    // Insert data in batches.
+    BatchInsertData(conn);
+
+  // Run a prepared statement to update data.
+    ExecPreparedSQL(conn);
+
+    // Run a stored procedure.
+    ExecCallableSQL(conn);
+
+    // Close the connection to the database.
+    try {
+      conn.close();
+    } catch (SQLException e) {
+      e.printStackTrace();
+    }
+
+  }
+
+}
+```
+
+## Example 2: High Client Memory Usage
+
+In this example, **setFetchSize** adjusts the memory usage of the client by using the database cursor to obtain server data in batches. It may increase network interaction and damage some performance.
+
+The cursor is valid within a transaction. Therefore, disable automatic commit and then manually commit the code.
+
+```
+// Disable automatic commit.
+conn.setAutoCommit(false);
+Statement st = conn.createStatement();
+
+// Open the cursor and obtain 50 lines of data each time.
+st.setFetchSize(50);
+ResultSet rs = st.executeQuery("SELECT * FROM mytable");
+conn.commit();
+while (rs.next())
+{
+    System.out.print("a row was returned.");
+}
+rs.close();
+
+// Disable the server cursor.
+st.setFetchSize(0);
+rs = st.executeQuery("SELECT * FROM mytable");
+conn.commit();
+while (rs.next())
+{
+    System.out.print("many rows were returned.");
+}
+rs.close();
+
+// Close the statement.
+st.close();
+conn.close();
+```
+
+Run the following command to enable automatic commit:
+
+```
+conn.setAutoCommit(true);
+```
+
+## Example 3: Example of Common Data Types
+
+```
+//Example of the bit type. Note that the value range of the bit type is [0,1].
+Statement st = conn.createStatement();
+String sqlstr = "create or replace function fun_1()\n" +
+        "returns bit AS $$\n" +
+        "select col_bit from t_bit limit 1;\n" +
+        "$$\n" +
+        "LANGUAGE SQL;";
+st.execute(sqlstr);
+CallableStatement c = conn.prepareCall("{ ? = call fun_1() }");
+//Register the output type, which is a bit string.
+c.registerOutParameter(1, Types.BIT);
+c.execute();
+//Use the Boolean type to obtain the result.
+System.out.println(c.getBoolean(1));
+```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/1-psycopg2-connect.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/1-psycopg2-connect.md
new file mode 100644
index 0000000000000000000000000000000000000000..d4ca8b008709b0967d1cbf27dddb54e3eb810713
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/1-psycopg2-connect.md
@@ -0,0 +1,42 @@
+---
+title: psycopg2.connect()
+summary: psycopg2.connect()
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# psycopg2.connect()
+
+## Function
+
+This method creates a database session and returns a new connection object.
+
+## Prototype
+
+```
+conn=psycopg2.connect(dbname="test",user="postgres",password="secret",host="127.0.0.1",port="5432")
+```
+
+## Parameter
+
+**Table 1** psycopg2.connect parameters
+
+| **Keyword** | **Description**                                              |
+| :---------- | :----------------------------------------------------------- |
+| dbname      | Database name.                                               |
+| user        | Username.                                                    |
+| password    | Password.                                                    |
+| host        | Database IP address. The default type is UNIX socket.        |
+| port        | Connection port number. The default value is **5432**.       |
+| sslmode     | SSL mode, which is used for SSL connection.                  |
+| sslcert     | Path of the client certificate, which is used for SSL connection. |
+| sslkey      | Path of the client key, which is used for SSL connection.    |
+| sslrootcert | Path of the root certificate, which is used for SSL connection. |
+
+## Return Value
+
+Connection object (for connecting to the openGauss DB instance)
+
+## Examples
+
+For details, see [Example: Common Operations](10.1-example-common-operations).
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/10-connection-close.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/10-connection-close.md
new file mode 100644
index 0000000000000000000000000000000000000000..111a510f406c66d5a652a2910eec9d2c49507d2c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/10-connection-close.md
@@ -0,0 +1,32 @@
+---
+title: connection.close()
+summary: connection.close()
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# connection.close()
+
+## Function
+
+This method closes the database connection.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **CAUTION:** This method closes the database connection and does not automatically call **commit()**. If you just close the database connection without calling **commit()** first, changes will be lost.
+
+## Prototype
+
+```
+connection.close()
+```
+
+## Parameter
+
+None
+
+## Return Value
+
+None
+
+## Examples
+
+For details, see [Example: Common Operations](10.1-example-common-operations).
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/2-connection-cursor.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/2-connection-cursor.md
new file mode 100644
index 0000000000000000000000000000000000000000..b78fb863759ad6ff3179bbc072a43743ccccdecc
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/2-connection-cursor.md
@@ -0,0 +1,37 @@
+---
+title: connection.cursor()
+summary: connection.cursor()
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# connection.cursor()
+
+## Function
+
+This method returns a new cursor object.
+
+## Prototype
+
+```
+cursor(name=None, cursor_factory=None, scrollable=None, withhold=False)
+```
+
+## Parameter
+
+**Table 1** connection.cursor parameters
+
+| **Keyword**    | **Description**                                              |
+| :------------- | :----------------------------------------------------------- |
+| name           | Cursor name. The default value is **None**.                  |
+| cursor_factory | Creates a non-standard cursor. The default value is **None**. |
+| scrollable     | Sets the SCROLL option. The default value is **None**.       |
+| withhold       | Sets the HOLD option. The default value is **False**.        |
+
+## Return Value
+
+Cursor object (used for cusors that are programmed using Python in the entire database)
+
+## Examples
+
+For details, see [Example: Common Operations](10.1-example-common-operations).
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/3-cursor-execute-query-vars-list.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/3-cursor-execute-query-vars-list.md
new file mode 100644
index 0000000000000000000000000000000000000000..ea04a2585fd45bc41ea812dc3e675a7581c7a097
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/3-cursor-execute-query-vars-list.md
@@ -0,0 +1,35 @@
+---
+title: cursor.execute(query,vars_list)
+summary: cursor.execute(query,vars_list)
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# cursor.execute(query,vars_list)
+
+## Function
+
+This method executes the parameterized SQL statements (that is, placeholders instead of SQL literals). The psycopg2 module supports placeholders marked with **%s**.
+
+## Prototype
+
+```
+curosr.execute(query,vars_list)
+```
+
+## Parameters
+
+**Table 1** curosr.execute parameters
+
+| **Keyword** | **Description**                                              |
+| :---------- | :----------------------------------------------------------- |
+| query       | SQL statement to be executed.                                |
+| vars_list   | Variable list, which matches the **%s** placeholder in the query. |
+
+## Return Value
+
+None
+
+## Examples
+
+For details, see [Example: Common Operations](10.1-example-common-operations).
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/4-curosr-executemany-query-vars-list.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/4-curosr-executemany-query-vars-list.md
new file mode 100644
index 0000000000000000000000000000000000000000..b4a57a6c16b7b2ff5a044feafb3d853821fab966
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/4-curosr-executemany-query-vars-list.md
@@ -0,0 +1,35 @@
+---
+title: curosr.executemany(query,vars_list)
+summary: curosr.executemany(query,vars_list)
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# curosr.executemany(query,vars_list)
+
+## Function
+
+This method executes an SQL command against all parameter sequences or mappings found in the sequence SQL.
+
+## Prototype
+
+```
+curosr.executemany(query,vars_list)
+```
+
+## Parameter
+
+**Table 1** curosr.executemany parameters
+
+| **Keyword** | **Description**                                              |
+| :---------- | :----------------------------------------------------------- |
+| query       | SQL statement that you want to execute.                      |
+| vars_list   | Variable list, which matches the **%s** placeholder in the query. |
+
+## Return Value
+
+None
+
+## Examples
+
+For details, see [Example: Common Operations](10.1-example-common-operations).
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/5-connection-commit.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/5-connection-commit.md
new file mode 100644
index 0000000000000000000000000000000000000000..1f2cdd5251427edb135a58567a61e24836e69816
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/5-connection-commit.md
@@ -0,0 +1,32 @@
+---
+title: connection.commit()
+summary: connection.commit()
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# connection.commit()
+
+## Function
+
+This method commits the currently pending transaction to the database.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **CAUTION:** By default, Psycopg opens a transaction before executing the first command. If **commit()** is not called, the effect of any data operation will be lost.
+
+## Prototype
+
+```
+connection.commit()
+```
+
+## Parameter
+
+None
+
+## Return Value
+
+None
+
+## Examples
+
+For details, see [Example: Common Operations](10.1-example-common-operations).
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/6-connection-rollback.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/6-connection-rollback.md
new file mode 100644
index 0000000000000000000000000000000000000000..0284fcd43997b32d6ca7267b4e3ff97be1be6de4
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/6-connection-rollback.md
@@ -0,0 +1,32 @@
+---
+title: connection.rollback()
+summary: connection.rollback()
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# connection.rollback()
+
+## Function
+
+This method rolls back the current pending transaction.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **CAUTION:** If you close the connection using **close()** but do not commit the change using **commit()**, an implicit rollback will be performed.
+
+## Prototype
+
+```
+connection.rollback()
+```
+
+## Parameter
+
+None
+
+## Return Value
+
+None
+
+## Examples
+
+For details, see [Example: Common Operations](10.1-example-common-operations).
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/7-cursor-fetchone.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/7-cursor-fetchone.md
new file mode 100644
index 0000000000000000000000000000000000000000..a9af28472feac88dae831f1459c6e89d236f650e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/7-cursor-fetchone.md
@@ -0,0 +1,30 @@
+---
+title: cursor.fetchone()
+summary: cursor.fetchone()
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# cursor.fetchone()
+
+## Function
+
+This method extracts the next row of the query result set and returns a tuple.
+
+## Prototype
+
+```
+cursor.fetchone()
+```
+
+## Parameter
+
+None
+
+## Return Value
+
+A single tuple is the first result in the result set. If no more data is available, **None** is returned.
+
+## Examples
+
+For details, see [Example: Common Operations](10.1-example-common-operations).
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/8-cursor-fetchall.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/8-cursor-fetchall.md
new file mode 100644
index 0000000000000000000000000000000000000000..c8949edd5d7f484e89f95ec1dfbdb9e15220b782
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/8-cursor-fetchall.md
@@ -0,0 +1,30 @@
+---
+title: cursor.fetchall()
+summary: cursor.fetchall()
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# cursor.fetchall()
+
+## Function
+
+This method obtains all the (remaining) rows of the query result and returns them as a list of tuples.
+
+## Prototype
+
+```
+cursor.fetchall()
+```
+
+## Parameter
+
+None
+
+## Return Value
+
+Tuple list, which contains all results of the result set. An empty list is returned when no rows are available.
+
+## Examples
+
+For details, see [Example: Common Operations](10.1-example-common-operations).
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/9-cursor-close.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/9-cursor-close.md
new file mode 100644
index 0000000000000000000000000000000000000000..7fa9acd286fd3029c09d5e3c92468e9d3ab6e1c2
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/9-cursor-close.md
@@ -0,0 +1,30 @@
+---
+title: cursor.close()
+summary: cursor.close()
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# cursor.close()
+
+## Function
+
+This method closes the cursor of the current connection.
+
+## Prototype
+
+```
+cursor.close()
+```
+
+## Parameter
+
+None
+
+## Return Value
+
+None
+
+## Examples
+
+For details, see [Example: Common Operations](10.1-example-common-operations).
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/2-psycopg-package.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/2-psycopg-package.md
new file mode 100644
index 0000000000000000000000000000000000000000..1a6e0577c32670b9e4ddab9b5082ebb891f6ea73
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/2-psycopg-package.md
@@ -0,0 +1,15 @@
+---
+title: Psycopg Package
+summary: Psycopg Package
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# Psycopg Package
+
+The psycopg package is obtained from the release package. Its name is **GaussDB-Kernel-VxxxRxxxCxx-OS version number-64bit-Python.tar.gz**.
+
+After the decompression, the following folders are generated:
+
+- **psycopg2**: **psycopg2** library file
+- **lib**: **lib** library file
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/3.1-development-process.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/3.1-development-process.md
new file mode 100644
index 0000000000000000000000000000000000000000..9e2f3d5b39a81a023d1db4536d204d6ce9a0a8b3
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/3.1-development-process.md
@@ -0,0 +1,12 @@
+---
+title: Development Process
+summary: Development Process
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# Development Process
+
+**Figure 1** Application development process based on psycopg2
+
+![application-development-process-based-on-psycopg2](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/development-process-2.png)
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/4-loading-a-driver.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/4-loading-a-driver.md
new file mode 100644
index 0000000000000000000000000000000000000000..952882e00dc0e038b500f40914acd2e53a1cb72a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/4-loading-a-driver.md
@@ -0,0 +1,21 @@
+---
+title: Loading a Driver
+summary: Loading a Driver
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# Loading a Driver
+
+- Before using the driver, perform the following operations:
+
+  1. Decompress the driver package of the corresponding version and copy psycopg2 to the **site-packages** folder in the Python installation directory as the **root** user.
+  2. Change the **psycopg2** directory permission to **755**.
+  3. Add the **psycopg2** directory to the environment variable *$PYTHONPATH* and validate it.
+  4. For non-database users, configure the **lib** directory in *LD_LIBRARY_PATH* after decompression.
+
+- Load a database driver before creating a database connection:
+
+  ```bash
+  import  psycopg2
+  ```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/5.1-connecting-to-a-database.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/5.1-connecting-to-a-database.md
new file mode 100644
index 0000000000000000000000000000000000000000..556bf4391713b2f183702b5fe62c4dbd64e5252f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/5.1-connecting-to-a-database.md
@@ -0,0 +1,12 @@
+---
+title: Connecting to a Database
+summary: Connecting to a Database
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# Connecting to a Database
+
+1. Use the .ini file (the **configparser** package of Python can parse this type of configuration file) to save the configuration information about the database connection.
+2. Use the **psycopg2.connect** function to obtain the connection object.
+3. Use the connection object to create a cursor object.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/6-executing-sql-statements.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/6-executing-sql-statements.md
new file mode 100644
index 0000000000000000000000000000000000000000..78313f70fa3ec3772f63aeeb1417c2436a4a268e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/6-executing-sql-statements.md
@@ -0,0 +1,11 @@
+---
+title: Executing SQL Statements
+summary: Executing SQL Statements
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# Executing SQL Statements
+
+1. Construct an operation statement and use **%s** as a placeholder. During execution, psycopg2 will replace the placeholder with the parameter value. You can add the RETURNING clause to obtain the automatically generated column values.
+2. The **cursor.execute** method is used to perform operations on one row, and the **cursor.executemany** method is used to perform operations on multiple rows.
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/7-processing-the-result-set.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/7-processing-the-result-set.md
new file mode 100644
index 0000000000000000000000000000000000000000..c24096ab1b5dd0318a1bbd8ce2984dc552945fe4
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/7-processing-the-result-set.md
@@ -0,0 +1,11 @@
+---
+title: Processing the Result Set
+summary: Processing the Result Set
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# Processing the Result Set
+
+1. **cursor.fetchone()**: Fetches the next row in a query result set and returns a sequence. If no data is available, null is returned.
+2. **cursor.fetchall()**: Fetches all remaining rows in a query result and returns a list. An empty list is returned when no rows are available.
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/8-closing-the-connection.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/8-closing-the-connection.md
new file mode 100644
index 0000000000000000000000000000000000000000..6e0d0c06b4b563815b4ede3fc4691063ac85666d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/8-closing-the-connection.md
@@ -0,0 +1,12 @@
+---
+title: Closing the Connection
+summary: Closing the Connection
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# Closing the Connection
+
+After you complete required data operations in a database, close the database connection. Call the close method such as **connection.close()** to close the connection.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **CAUTION:** This method closes the database connection and does not automatically call **commit()**. If you just close the database connection without calling **commit()** first, changes will be lost.
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/9-connecting-to-the-database-using-ssl.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/9-connecting-to-the-database-using-ssl.md
new file mode 100644
index 0000000000000000000000000000000000000000..17dffd022da56403d52b2402997109d7afdc900f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/9-connecting-to-the-database-using-ssl.md
@@ -0,0 +1,30 @@
+---
+title: Connecting to the Database
+summary: Connecting to the Database
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# Connecting to the Database (Using SSL)
+
+When you use psycopy2 to connect to the MogDB server, you can enable SSL to encrypt the communication between the client and server. To enable SSL, you must have the server certificate, client certificate, and private key files. For details on how to obtain these files, see related documents and commands of OpenSSL.
+
+1. Use the .ini file (the **configparser** package of Python can parse this type of configuration file) to save the configuration information about the database connection.
+2. Add SSL connection parameters **sslmode**, **sslcert**, **sslkey**, and **sslrootcert** to the connection options.
+   1. **sslmode**: [Table 1](#table1.1)
+   2. **sslcert**: client certificate path
+   3. **sslkey**: client key path
+   4. **sslrootcert**: root certificate path
+3. Use the **psycopg2.connect** function to obtain the connection object.
+4. Use the connection object to create a cursor object.
+
+**Table 1** sslmode options <a id="table1.1"> </a>
+
+| sslmode     | Whether SSL Encryption Is Enabled | Description                                                  |
+| :---------- | :-------------------------------- | :----------------------------------------------------------- |
+| disable     | No                                | SSL connection is not enabled.                               |
+| allow       | Possible                          | If the database server requires SSL connection, SSL connection can be enabled. However, authenticity of the database server will not be verified. |
+| prefer      | Possible                          | If the database supports SSL connection, SSL connection is preferred. However, authenticity of the database server will not be verified. |
+| require     | Yes                               | SSL connection is required and data is encrypted. However, authenticity of the database server will not be verified. |
+| verify-ca   | Yes                               | The SSL connection must be enabled.                          |
+| verify-full | Yes                               | The SSL connection must be enabled, which is not supported by MogDB currently. |
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/5-commissioning.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/5-commissioning.md
new file mode 100644
index 0000000000000000000000000000000000000000..848fff962eb9fe65080f09da7b53fc17109ce741
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/5-commissioning.md
@@ -0,0 +1,40 @@
+---
+title:  Commissioning
+summary:  Commissioning
+author:  Guo Huan
+date: 2021-04-27
+---
+
+# Commissioning
+
+To control the output of log files and better understand the operating status of the database, modify specific configuration parameters in the **postgresql.conf** file in the instance data directory.
+
+[Table 1](#Configuration parameters) describes the adjustable configuration parameters.
+
+<a id="Configuration parameters">**Table 1** </a>Configuration parameters
+
+| Parameter                                                    | Description                           | Value Range                           | Remarks                               |
+| ------------------------------------------------------------ | ------------------------------------- | ------------------------------------- | ------------------------------------- |
+| client_min_messages                | Level of messages to be sent to clients.                     | - DEBUG5<br />- DEBUG4<br />- DEBUG3<br />- DEBUG2<br />- DEBUG1<br />- LOG<br />- NOTICE<br />WARNING<br />- ERROR<br />- FATAL<br />- PANIC<br />Default value: NOTICE | Messages of the set level or lower will be sent to clients. The lower the level is, the fewer the messages will be sent. |
+| log_min_messages                   | Level of messages to be recorded in server logs.             | - DEBUG5<br />- DEBUG4<br />- DEBUG3<br />- DEBUG2<br />- DEBUG1<br />- INFO<br />- NOTICE<br />- WARNING<br />- ERROR<br />- LOG<br />- FATAL<br />- PANIC<br />Default value: WARNING | Messages higher than the set level will be recorded in logs. The higher the level is, the fewer the server logs will be recorded. |
+| log_min_error_statement            | Level of SQL error statements to be recorded in server logs. | - DEBUG5<br />- DEBUG4<br />- DEBUG3<br />- DEBUG2<br />- DEBUG1<br />- INFO<br />- NOTICE<br />- WARNING<br />- ERROR<br />- FATAL<br />- PANIC<br />Default value: ERROR。 | SQL error statements of the set level or higher will be recorded in server logs.Only a system administrator is allowed to modify this parameter. |
+| log_min_duration_statement         | Minimum execution duration of a statement. If the execution duration of a statement is equal to or longer than the set milliseconds, the statement and its duration will be recorded in logs. Enabling this function can help you track the query attempts to be optimized. | INT type<br />Default value: 30min<br />Unit: millisecond    | The default value (-1) indicates that the function is disabled.Only a system administrator is allowed to modify this parameter. |
+| log_connections/log_disconnections | Whether to record a server log message when each session is connected or disconnected. | - **on**: The system records a log server when each session is connected or disconnected.<br />- **off**: The system does not record a log server when each session is connected or disconnected.<br />Default value: off | -                                                            |
+| log_duration                       | Whether to record the duration of each executed statement.   | - **on**: The system records the duration of each executed statement.<br />- **off**: The system does not record the duration of each executed statement.<br />Default value: on | Only a system administrator is allowed to modify this parameter. |
+| log_statement                      | SQL statements to be recorded in logs.                       | - **none**: The system does not record any SQL statements.<br />- **ddl**: The system records data definition statements.<br />- **mod**: The system records data definition statements and data operation statements.<br />- **all**: The system records all statements.<br />Default value: none | Only a system administrator is allowed to modify this parameter. |
+| log_hostname                       | Whether to record host names.                                | - **on**: The system records host names.<br />- **off**: The system does not record host names.<br />Default value: off | By default, connection logs only record the IP addresses of connected hosts. With this function, the host names will also be recorded.This parameter affects parameters in **Querying Audit Results**, GS_WLM_SESSION_HISTORY, PG_STAT_ACTIVITY, and **log_line_prefix**. |
+
+[Table 2](#description) describes the preceding parameter levels.
+
+<a id="description">**Table 2**</a> Description of log level parameters
+
+| Level      | Description                                                  |
+| ---------- | ------------------------------------------------------------ |
+| DEBUG[1-5] | Provides information that can be used by developers. Level 1 is the lowest level whereas level 5 is the highest level. |
+| INFO       | Provides information about users' hidden requests, for example, information about the VACUUM VERBOSE process. |
+| NOTICE     | Provides information that may be important to users, for example, truncations of long identifiers or indexes created as a part of a primary key. |
+| WARNING    | Provides warning information for users, for example, COMMIT out of transaction blocks. |
+| ERROR      | Reports an error that causes a command to terminate.         |
+| LOG        | Reports information that administrators may be interested in, for example, the activity levels of check points. |
+| FATAL      | Reports the reason that causes a session to terminate.       |
+| PANIC      | Reports the reason that causes all sessions to terminate.    |
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/dev/6-appendix.md b/product/en/docs-mogdb/v3.0/developer-guide/dev/6-appendix.md
new file mode 100644
index 0000000000000000000000000000000000000000..137e0bc4f7625aa5f2b37de549a14b438dacd1fa
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/dev/6-appendix.md
@@ -0,0 +1,107 @@
+---
+title:  Appendices
+summary:  Appendices
+author:  Guo Huan
+date: 2021-04-27
+---
+
+# Appendices
+
+## <a id="PG_STAT_ACTIVITY">**Table 1** </a>PG_STAT_ACTIVITY Columns
+
+| Name             | Type                     | Description                                                  |
+| ---------------- | ------------------------ | ------------------------------------------------------------ |
+| datid            | oid                      | OID of the database that the user session connects to in the backend |
+| datname          | name                     | Name of the database that the user session connects to in the backend |
+| pid              | bigint                   | Thread ID of the backend                                     |
+| sessionid        | bigint                   | Session ID                                                   |
+| usesysid         | oid                      | OID of the user logged in to the backend                     |
+| usename          | name                     | Name of the user logged in to the backend                    |
+| application_name | text                     | Name of the application connected to the backend             |
+| client_addr      | inet                     | IP address of the client connected to the backend. If this column is null, it indicates either the client is connected via a Unix socket on the server or this is an internal process, such as autovacuum. |
+| client_hostname  | text                     | Host name of the connected client, as reported by a reverse DNS lookup of `client_addr`. This column will be non-null only for IP connections and only when **log_hostname** is enabled. |
+| client_port      | integer                  | TCP port number that the client uses for communication with this backend (**-1** if a Unix socket is used) |
+| backend_start    | timestamp with time zone | Time when this process was started, that is, when the client connected to the server |
+| xact_start       | timestamp with time zone | Time when current transaction was started (null if no transaction is active) If the current query is the first of its transaction, the value of this column is the same as that of the **query_start** column. |
+| query_start      | timestamp with time zone | Time when the currently active query was started, or if **state** is not **active**, when the last query was started |
+| state_change     | timestamp with time zone | Time when the **state** was last changed                     |
+| waiting          | Boolean                  | Whether the backend is currently waiting on a lock. If yes, the value is **true**. |
+| enqueue          | text                     | Unsupported currently                                        |
+| state            | text                     | Overall status of this backend. The value must be one of the following:<br />- **active**: The backend is executing a query.<br />- **idle**: The backend is waiting for a new client command.<br />- **idle in transaction**: The backend is in a transaction, but there is no statement being executed in the transaction.<br />- **idle in transaction** (aborted): The backend is in a transaction, but there are statements failed in the transaction.<br />- **fastpath function call**: The backend is executing a fast-path function.<br />- **disabled**: This state is reported if **track_activities** is disabled in this backend.<br />NOTE:<br />Common users can view their own session status only. The state information of other accounts is empty. For example, after user **judy** is connected to the database, the state information of user **joe** and the initial user omm in **pg_stat_activity** is empty.<br />`SELECT datname, usename, usesysid, state,pid FROM pg_stat_activity;`<br />`datname  | usename | usesysid | state  |       pid ----+---+----+---+------ postgres | omm     |       10 |        | 139968752121616 postgres | omm     |       10 |        | 139968903116560 db_tpcc | judy    |    16398 | active | 139968391403280 postgres | omm     |       10 |        | 139968643069712 postgres | omm     |       10 |        | 139968680818448 postgres | joe     |    16390 |        | 139968563377936 (6 rows)` |
+| resource_pool    | name                     | Resource pool used by the user                               |
+| query_id         | bigint                   | ID of a query                                                |
+| query            | text                     | Text of this backend's most recent query. If **state** is **active**, this column shows the ongoing query. In all other states, it shows the last query that was executed. |
+| connection_info  | text                     | A string in JSON format recording the driver type, driver version, driver deployment path, and process owner of the connected database. For details, see **connection_info**. |
+
+## <a id="GS_WLM">**Table 2** </a>GS_WLM_SESSION_HISTORY Columns
+
+| Name                | Type                     | Description                                                  |
+| ------------------------ | ---------------------- | ---------------------- |
+| datid               | oid                      | OID of the database that the backend is connected to         |
+| dbname              | text                     | Name of the database that the backend is connected to        |
+| schemaname          | text                     | Schema name                                                  |
+| nodename            | text                     | Name of the database node where the statement is executed    |
+| username            | text                     | Username used for connecting to the backend                  |
+| application_name    | text                     | Name of the application connected to the backend             |
+| client_addr         | inet                     | IP address of the client connected to the backend. If this column is null, it indicates either the client is connected via a Unix socket on the server or this is an internal process, such as autovacuum. |
+| client_hostname     | text                     | Host name of the connected client, as reported by a reverse DNS lookup of `client_addr`. This column will be non-null only for IP connections and only when **log_hostname** is enabled. |
+| client_port         | integer                  | TCP port number that the client uses for communication with this backend (**-1** if a Unix socket is used) |
+| query_band          | text                     | Job type, which is specified by the GUC parameter **query_band**. The default value is a null string. |
+| block_time          | bigint                   | Duration that the statement is blocked before being executed, including the statement parsing and optimization duration (unit: ms) |
+| start_time          | timestamp with time zone | Time when the statement starts to be executed                |
+| finish_time         | timestamp with time zone | Time when the statement execution ends                       |
+| duration            | bigint                   | Execution time of the statement, in ms                       |
+| estimate_total_time | bigint                   | Estimated execution time of the statement, in ms             |
+| status              | text                     | Final statement execution status, which can be **finished** (normal) or **aborted** (abnormal). |
+| abort_info          | text                     | Exception information displayed if the final statement execution status is **aborted** |
+| resource_pool       | text                     | Resource pool used by the user                               |
+| control_group       | text                     | The function is not supported currently.                     |
+| estimate_memory     | integer                  | Estimated memory size of the statement.                      |
+| min_peak_memory     | integer                  | Minimum memory peak of the statement across the database nodes, in MB |
+| max_peak_memory     | integer                  | Maximum memory peak of the statement across the database nodes, in MB |
+| average_peak_memory | integer                  | Average memory usage during statement execution (unit: MB)   |
+| memory_skew_percent | integer                  | Memory usage skew of the statement among the database nodes  |
+| spill_info          | text                     | Information about statement spill to the database nodes<br />- **None**: The statement has not been spilled to disks on the database nodes.<br />- **All**: The statement has been spilled to disks on the database nodes.<br />- **[a:b]**: The statement has been spilled to disks on *a* of *b* database nodes. |
+| min_spill_size      | integer                  | Minimum spilled data among database nodes when a spill occurs, in MB (default value:**0**) |
+| max_spill_size      | integer                  | Maximum spilled data among database nodes when a spill occurs, in MB (default value:**0**) |
+| average_spill_size  | integer                  | Average spilled data among database nodes when a spill occurs, in MB (default value:**0**) |
+| spill_skew_percent  | integer                  | database node spill skew when a spill occurs                 |
+| min_dn_time         | bigint                   | Minimum execution time of the statement across the database nodes, in ms |
+| max_dn_time         | bigint                   | Maximum execution time of the statement across the database nodes, in ms |
+| average_dn_time     | bigint                   | Average execution time of the statement across the database nodes, in ms |
+| dntime_skew_percent | integer                  | Execution time skew of the statement among the database nodes |
+| min_cpu_time        | bigint                   | Minimum CPU time of the statement across the database nodes, in ms |
+| max_cpu_time        | bigint                   | Maximum CPU time of the statement across the database nodes, in ms |
+| total_cpu_time      | bigint                   | Total CPU time of the statement across the database nodes, in ms |
+| cpu_skew_percent    | integer                  | CPU time skew of the statement among database nodes          |
+| min_peak_iops       | integer                  | Minimum IOPS peak of the statement across the database nodes. It is counted by ones in a column-store table and by ten thousands in a row-store table. |
+| max_peak_iops       | integer                  | Maximum IOPS peak of the statement across the database nodes. It is counted by ones in a column-store table and by ten thousands in a row-store table. |
+| average_peak_iops   | integer                  | Average IOPS peak of the statement across the database nodes. It is counted by ones in a column-store table and by ten thousands in a row-store table. |
+| iops_skew_percent   | integer                  | I/O skew across database nodes                               |
+| warning             | text                     | Warning. The following warnings are displayed:<br />- Spill file size large than 256 MB<br />- Broadcast size large than 100 MB<br />- Early spill<br />- Spill times is greater than 3<br />- Spill on memory adaptive<br />- Hash table conflict |
+| queryid             | bigint                   | Internal query ID used for statement execution               |
+| query               | text                     | Statement executed                                           |
+| query_plan          | text                     | Execution plan of the statement                              |
+| node_group          | text                     | Unsupported currently                                        |
+| cpu_top1_node_name  | text                     | Name of the current database node                            |
+| cpu_top2_node_name  | text                     | Unsupported currently                                        |
+| cpu_top3_node_name  | text                     | Unsupported currently                                        |
+| cpu_top4_node_name  | text                     | Unsupported currently                                        |
+| cpu_top5_node_name  | text                     | Unsupported currently                                        |
+| mem_top1_node_name  | text                     | Current database name                                        |
+| mem_top2_node_name  | text                     | Unsupported currently                                        |
+| mem_top3_node_name  | text                     | Unsupported currently                                        |
+| mem_top4_node_name  | text                     | Unsupported currently                                        |
+| mem_top5_node_name  | text                     | Unsupported currently                                        |
+| cpu_top1_value      | bigint                   | CPU usage of the current database node                       |
+| cpu_top2_value      | bigint                   | Unsupported currently                                        |
+| cpu_top3_value      | bigint                   | Unsupported currently                                        |
+| cpu_top4_value      | bigint                   | Unsupported currently                                        |
+| cpu_top5_value      | bigint                   | Unsupported currently                                        |
+| mem_top1_value      | bigint                   | Memory usage of the current database node                    |
+| mem_top2_value      | bigint                   | Unsupported currently                                        |
+| mem_top3_value      | bigint                   | Unsupported currently                                        |
+| mem_top4_value      | bigint                   | Unsupported currently                                        |
+| mem_top5_value      | bigint                   | Unsupported currently                                        |
+| top_mem_dn          | text                     | Memory usage information of the current database node        |
+| top_cpu_dn          | text                     | CPU usage information of the current database node           |
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-design/constraint-design.md b/product/en/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-design/constraint-design.md
new file mode 100644
index 0000000000000000000000000000000000000000..d595b4e68fdd43b1433832386af86d5911445b22
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-design/constraint-design.md
@@ -0,0 +1,37 @@
+---
+title: Constraint Design
+summary: Constraint Design
+author: Guo Huan
+date: 2021-10-14
+---
+
+# Constraint Design
+
+## DEFAULT and NULL Constraints
+
+- [Proposal] If all the column values can be obtained from services, you are not advised to use the **DEFAULT** constraint. Otherwise, unexpected results will be generated during data loading.
+- [Proposal] Add **NOT NULL** constraints to columns that never have NULL values. The optimizer automatically optimizes the columns in certain scenarios.
+- [Proposal] Explicitly name all constraints excluding **NOT NULL** and **DEFAULT**.
+
+## Partial Cluster Keys
+
+A partial cluster key (PCK) is a local clustering technology used for column-store tables. After creating a PCK, you can quickly filter and scan fact tables using min or max sparse indexes in MogDB. Comply with the following rules to create a PCK:
+
+- [Notice] Only one PCK can be created in a table. A PCK can contain multiple columns, preferably no more than two columns.
+- [Proposal] Create a PCK on simple expression filter conditions in a query. Such filter conditions are usually in the form of **col op const**, where **col** specifies a column name, **op** specifies an operator (such as =, >, >=, <=, and <), and **const** specifies a constant.
+- [Proposal] If the preceding conditions are met, create a PCK on the column having the most distinct values.
+
+## Unique Constraints
+
+- [Notice] Unique constraints can be used in row-store tables and column-store tables.
+- [Proposal] The constraint name should indicate that it is a unique constraint, for example, **UNIIncluded columns**.
+
+## Primary Key Constraints
+
+- [Notice] Primary key constraints can be used in row-store tables and column-store tables.
+- [Proposal] The constraint name should indicate that it is a primary key constraint, for example, **PKIncluded columns**.
+
+## Check Constraints
+
+- [Notice] Check constraints can be used in row-store tables but not in column-store tables.
+- [Proposal] The constraint name should indicate that it is a check constraint, for example, **CKIncluded columns**.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-design/database-and-schema-design.md b/product/en/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-design/database-and-schema-design.md
new file mode 100644
index 0000000000000000000000000000000000000000..c72ba82a19d03e6d95d0146ad58024999e86691f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-design/database-and-schema-design.md
@@ -0,0 +1,27 @@
+---
+title: Database and Schema Design
+summary: Database and Schema Design
+author: Guo Huan
+date: 2021-10-14
+---
+
+# Database and Schema Design
+
+In MogDB, services can be isolated by databases and schemas. Databases share little resources and cannot directly access each other. Connections to and permissions on them are also isolated. Schemas share more resources than databases do. User permissions on schemas and subordinate objects can be controlled using the **GRANT** and **REVOKE** syntax.
+
+- You are advised to use schemas to isolate services for convenience and resource sharing.
+- It is recommended that system administrators create schemas and databases and then assign required permissions to users.
+
+## Database Design
+
+- [Rule] Create databases as required by your service. Do not use the default **postgres** database of a database instance.
+- [Proposal] Create a maximum of three user-defined databases in a database instance.
+- [Proposal] To make your database compatible with most characters, you are advised to use the UTF-8 encoding when creating a database.
+- [Notice] When you create a database, exercise caution when you set **ENCODING** and **DBCOMPATIBILITY** configuration items. MogDB supports the A, B and PG compatibility modes, which are compatible with the Oracle syntax, MySQL syntax and PostgreSQL syntax, respectively. The syntax behavior varies according to the compatibility mode. By default, the A compatibility mode is used.
+- [Notice] By default, a database owner has all permissions for all objects in the database, including the deletion permission. Exercise caution when deleting a permission.
+
+## Schema Design
+
+- [Notice] To let a user access an object in a schema, assign the usage permission and the permissions for the object to the user, unless the user has the **sysadmin** permission or is the schema owner.
+- [Notice] To let a user create an object in the schema, grant the create permission for the schema to the user.
+- [Notice] By default, a schema owner has all permissions for all objects in the schema, including the deletion permission. Exercise caution when deleting a permission.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-design/field-design.md b/product/en/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-design/field-design.md
new file mode 100644
index 0000000000000000000000000000000000000000..1759925cfc57c182b18f59d9815aad1e4c1ecafc
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-design/field-design.md
@@ -0,0 +1,40 @@
+---
+title: Field Design
+summary: Field Design
+author: Guo Huan
+date: 2021-10-14
+---
+
+# Field Design
+
+## Selecting a Data Type
+
+To improve query efficiency, comply with the following rules when designing columns:
+
+- [Proposal] Use the most efficient data types allowed.
+
+  If all of the following number types provide the required service precision, they are recommended in descending order of priority: integer, floating point, and numeric.
+
+- [Proposal] In tables that are logically related, columns having the same meaning should use the same data type.
+
+- [Proposal] For string data, you are advised to use variable-length strings and specify the maximum length. To avoid truncation, ensure that the specified maximum length is greater than the maximum number of characters to be stored. You are not advised to use CHAR(n), BPCHAR(n), NCHAR(n), or CHARACTER(n), unless you know that the string length is fixed.
+
+  For details about string types, see below.
+
+## Common String Types
+
+Every column requires a data type suitable for its data characteristics. The following table lists common string types in MogDB.
+
+**Table 1** Common string types
+
+| **Name**             | **Description**                                              | **Max. Storage Capacity** |
+| :------------------- | :----------------------------------------------------------- | :------------------------ |
+| CHAR(n)              | Fixed-length string, where *n* indicates the stored bytes. If the length of an input string is smaller than *n*, the string is automatically padded to *n* bytes using NULL characters. | 10 MB                     |
+| CHARACTER(n)         | Fixed-length string, where *n* indicates the stored bytes. If the length of an input string is smaller than *n*, the string is automatically padded to *n* bytes using NULL characters. | 10 MB                     |
+| NCHAR(n)             | Fixed-length string, where *n* indicates the stored bytes. If the length of an input string is smaller than *n*, the string is automatically padded to *n* bytes using NULL characters. | 10 MB                     |
+| BPCHAR(n)            | Fixed-length string, where *n* indicates the stored bytes. If the length of an input string is smaller than *n*, the string is automatically padded to *n* bytes using NULL characters. | 10 MB                     |
+| VARCHAR(n)           | Variable-length string, where *n* indicates the maximum number of bytes that can be stored. | 10 MB                     |
+| CHARACTER VARYING(n) | Variable-length string, where *n* indicates the maximum number of bytes that can be stored. This data type and VARCHAR(n) are different representations of the same data type. | 10 MB                     |
+| VARCHAR2(n)          | Variable-length string, where *n* indicates the maximum number of bytes that can be stored. This data type is added to be compatible with the Oracle database, and its behavior is the same as that of VARCHAR(n). | 10 MB                     |
+| NVARCHAR2(n)         | Variable-length string, where *n* indicates the maximum number of bytes that can be stored. | 10 MB                     |
+| TEXT                 | Variable-length string. Its maximum length is 1 GB minus 8203 bytes. | 1 GB minus 8203 bytes     |
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-design/table-design.md b/product/en/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-design/table-design.md
new file mode 100644
index 0000000000000000000000000000000000000000..c883964861f4d0a56ce02115536e592c0eddaa60
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-design/table-design.md
@@ -0,0 +1,57 @@
+---
+title: Table Design
+summary: Table Design
+author: Guo Huan
+date: 2021-10-14
+---
+
+# Table Design
+
+Comply with the following principles to properly design a table:
+
+- [Notice] Reduce the amount of data to be scanned. You can use the pruning mechanism of a partitioned table.
+- [Notice] Minimize random I/Os. By clustering or local clustering, you can sequentially store hot data, converting random I/O to sequential I/O to reduce the cost of I/O scanning.
+
+## Selecting a Storage Mode
+
+[Proposal] Selecting a storage model is the first step in defining a table. The storage model mainly depends on the customer's service type. For details, see Table 1.
+
+**Table 1** Table storage modes and scenarios
+
+| Storage Type | Application Scenario                                         |
+| :----------- | :----------------------------------------------------------- |
+| Row store    | - Point queries (simple index-based queries that only return a few records).<br />- Scenarios requiring frequent addition, deletion, and modification. |
+| Column store | - Statistical analysis queries (requiring a large number of association and grouping operations).<br />- Ad hoc queries (using uncertain query conditions and unable to utilize indexes to scan row-store tables). |
+
+## Selecting a Partitioning Mode
+
+If a table contains a large amount of data, partition the table based on the following rules:
+
+- [Proposal] Create partitions on columns that indicate certain ranges, such as dates and regions.
+- [Proposal] A partition name should show the data characteristics of a partition. For example, its format can be **Keyword+Range** characteristics.
+- [Proposal] Set the upper limit of a partition to **MAXVALUE** to prevent data overflow.
+
+The example of a partitioned table definition is as follows:
+
+```sql
+CREATE TABLE staffS_p1
+(
+  staff_ID       NUMBER(6) not null,
+  FIRST_NAME     VARCHAR2(20),
+  LAST_NAME      VARCHAR2(25),
+  EMAIL          VARCHAR2(25),
+  PHONE_NUMBER   VARCHAR2(20),
+  HIRE_DATE      DATE,
+  employment_ID  VARCHAR2(10),
+  SALARY         NUMBER(8,2),
+  COMMISSION_PCT NUMBER(4,2),
+  MANAGER_ID     NUMBER(6),
+  section_ID     NUMBER(4)
+)
+PARTITION BY RANGE (HIRE_DATE)
+(
+   PARTITION HIRE_19950501 VALUES LESS THAN ('1995-05-01 00:00:00'),
+   PARTITION HIRE_19950502 VALUES LESS THAN ('1995-05-02 00:00:00'),
+   PARTITION HIRE_maxvalue VALUES LESS THAN (MAXVALUE)
+);
+```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-design/view-and-joined-table-design.md b/product/en/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-design/view-and-joined-table-design.md
new file mode 100644
index 0000000000000000000000000000000000000000..ea5629a424839598bbc19b85b225528c28c53278
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-design/view-and-joined-table-design.md
@@ -0,0 +1,19 @@
+---
+title: View and Joined Table Design
+summary: View and Joined Table Design
+author: Guo Huan
+date: 2021-10-14
+---
+
+# View and Joined Table Design
+
+## View Design
+
+- [Proposal] Do not nest views unless they have strong dependency on each other.
+- [Proposal] Try to avoid collation operations in a view definition.
+
+## Joined Table Design
+
+- [Proposal] Minimize joined columns across tables.
+- [Proposal] Use the same data type for joined columns.
+- [Proposal] The names of joined columns should indicate their relationship. For example, they can use the same name.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-naming-conventions.md b/product/en/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-naming-conventions.md
new file mode 100644
index 0000000000000000000000000000000000000000..1f8e5b2e593267d572b5218bb0caedb2741d7ec4
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-naming-conventions.md
@@ -0,0 +1,31 @@
+---
+title: Database Object Naming Conventions
+summary: Database Object Naming Conventions
+author: Guo Huan
+date: 2021-10-14
+---
+
+# Database Object Naming Conventions
+
+The name of a database object must meet the following requirements: The name of a non-time series table ranges from 1 to 63 characters and that of a time series table ranges from 1 to 53 characters. The name must start with a letter or underscore (_), and can contain letters, digits, underscores (_), dollar signs ($), and number signs (#).
+
+- [Proposal] Do not use reserved or non-reserved keywords to name database objects.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** You can use the select * from pg_get_keywords() query openGauss keyword or view the keyword in [Keywords](2-keywords).
+
+- [Proposal] Do not use a string enclosed in double quotation marks ("") to define the database object name, unless you need to specify its capitalization. Case sensitivity of database object names makes problem location difficult.
+
+- [Proposal] Use the same naming format for database objects.
+
+  - In a system undergoing incremental development or service migration, you are advised to comply with its historical naming conventions.
+  - You are advised to use multiple words separated with underscores (_).
+  - You are advised to use intelligible names and common acronyms or abbreviations for database objects. Acronyms or abbreviations that are generally understood are recommended. For example, you can use English words or Chinese pinyin indicating actual business terms. The naming format should be consistent within a database instance.
+  - A variable name must be descriptive and meaningful. It must have a prefix indicating its type.
+
+- [Proposal] The name of a table object should indicate its main characteristics, for example, whether it is an ordinary, temporary, or unlogged table.
+
+  - An ordinary table name should indicate the business relevant to a dataset.
+  - Temporary tables are named in the format of **tmp_Suffix**.
+  - Unlogged tables are named in the format of **ul_Suffix**.
+  - Foreign tables are named in the format of **f_Suffix**.
+  - Do not create database objects whose names start with **redis_**.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/overview-of-development-and-design-proposal.md b/product/en/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/overview-of-development-and-design-proposal.md
new file mode 100644
index 0000000000000000000000000000000000000000..9b98deb87e6cb87a2b02359953634464b613bf43
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/overview-of-development-and-design-proposal.md
@@ -0,0 +1,15 @@
+---
+title: Overview of Development and Design Proposal
+summary: Overview of Development and Design Proposal
+author: Guo Huan
+date: 2021-10-14
+---
+
+# Overview of Development and Design Proposal
+
+This section describes the design specifications for database modeling and application development. Modeling based on these specifications can better fit the distributed processing architecture of MogDB and output more efficient service SQL code.
+
+The meaning of "Proposal" and "Notice" in this section is as follows:
+
+- **Proposal**: Design rules. Services complying with the rules can run efficiently, and those violating the rules may have low performance or logic errors.
+- **Notice**: Details requiring attention during service development. This term identifies SQL behavior that complies with SQL standards but users may have misconceptions about, and default behavior that users may be unaware of in a program.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/sql-compilation.md b/product/en/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/sql-compilation.md
new file mode 100644
index 0000000000000000000000000000000000000000..5935dd148cca60eaf42f7880532c6e2851df1281
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/sql-compilation.md
@@ -0,0 +1,143 @@
+---
+title: SQL Compilation
+summary: SQL Compilation
+author: Guo Huan
+date: 2021-10-14
+---
+
+# SQL Compilation
+
+## DDL
+
+- [Proposal] In MogDB, you are advised to execute DDL operations, such as creating table or making comments, separately from batch processing jobs to avoid performance deterioration caused by many concurrent transactions.
+- [Proposal] Execute data truncation after unlogged tables are used because MogDB cannot ensure the security of unlogged tables in abnormal scenarios.
+- [Proposal] Suggestions on the storage mode of temporary and unlogged tables are the same as those on base tables. Create temporary tables in the same storage mode as the base tables to avoid high computing costs caused by hybrid row and column correlation.
+- [Proposal] The total length of an index column cannot exceed 50 bytes. Otherwise, the index size will increase greatly, resulting in large storage cost and low index performance.
+- [Proposal] Do not delete objects using **DROP…CASCADE**, unless the dependency between objects is specified. Otherwise, the objects may be deleted by mistake.
+
+## Data Loading and Uninstalling
+
+- [Proposal] Provide the inserted column list in the insert statement. Example:
+
+  ```sql
+  INSERT INTO task(name,id,comment) VALUES ('task1','100','100th task');
+  ```
+
+- [Proposal] After data is imported to the database in batches or the data increment reaches the threshold, you are advised to analyze tables to prevent the execution plan from being degraded due to inaccurate statistics.
+
+- [Proposal] To clear all data in a table, you are advised to use **TRUNCATE TABLE** instead of **DELETE TABLE**. **DELETE TABLE** is not efficient and cannot release disk space occupied by the deleted data.
+
+## Type Conversion
+
+- [Proposal] Convert data types explicitly. If you perform implicit conversion, the result may differ from expected.
+- [Proposal] During data query, explicitly specify the data type for constants, and do not attempt to perform any implicit data type conversion.
+- [Notice] If **sql_compatibility** is set to **A**, null strings will be automatically converted to **NULL** during data import. If null strings need to be reserved, set **sql_compatibility** to **C**.
+
+## Query Operation
+
+- [Proposal] Do not return a large number of result sets to a client except the ETL program. If a large result set is returned, consider modifying your service design.
+
+- [Proposal] Perform DDL and DML operations encapsulated in transactions. Operations like table truncation, update, deletion, and dropping, cannot be rolled back once committed. You are advised to encapsulate such operations in transactions so that you can roll back the operations if necessary.
+
+- [Proposal] During query compilation, you are advised to list all columns to be queried and avoid using **SELECT \***. Doing so reduces output lines, improves query performance, and avoids the impact of adding or deleting columns on front-end service compatibility.
+
+- [Proposal] During table object access, add the schema prefix to the table object to avoid accessing an unexpected table due to schema switchover.
+
+- [Proposal] The cost of joining more than three tables or views, especially full joins, is difficult to be estimated. You are advised to use the **WITH TABLE AS** statement to create interim tables to improve the readability of SQL statements.
+
+- [Proposal] Avoid using Cartesian products or full joins. Cartesian products and full joins will result in a sharp expansion of result sets and poor performance.
+
+- [Notice] Only **IS NULL** and **IS NOT NULL** can be used to determine NULL value comparison results. If any other method is used, **NULL** is returned. For example, **NULL** instead of expected Boolean values is returned for **NULL<>NULL**, **NULL=NULL**, and **NULL<>1**.
+
+- [Notice] Do not use **count(col)** instead of **count(\*)** to count the total number of records in a table. **count(\*)** counts the NULL value (actual rows) while **count(col)** does not.
+
+- [Notice] While executing **count(col)**, the number of NULL record rows is counted as 0. While executing **sum(col)**, **NULL** is returned if all records are NULL. If not all the records are NULL, the number of NULL record rows is counted as 0.
+
+- [Notice] To count multiple columns using **count()**, column names must be enclosed in parentheses. For example, count ((col1, col2, col3)). Note: When multiple columns are used to count the number of NULL record rows, a row is counted even if all the selected columns are NULL. The result is the same as that when **count(\*)** is executed.
+
+- [Notice] NULL records are not counted when **count(distinct col)** is used to calculate the number of non-NULL columns that are not repeated.
+
+- [Notice] If all statistical columns are NULL when **count(distinct (col1,col2,…))** is used to count the number of unique values in multiple columns, NULL records are also counted, and the records are considered the same.
+
+- [Proposal] Use the connection operator || to replace the **concat** function for string connection because the execution plan generated by the **concat** function cannot be pushed down to disks. As a result, the query performance severely deteriorates.
+
+- [Proposal] Use the following time-related macros to replace the **now** function and obtain the current time because the execution plan generated by the **now** function cannot be pushed down to disks. As a result, the query performance severely deteriorates.
+
+  **Table 1** Time-related macros
+
+  | **Macro Name**       | **Description**                                              | **Example**                                                  |
+  | :------------------- | :----------------------------------------------------------- | :----------------------------------------------------------- |
+  | CURRENT_DATE         | Obtains the current date, excluding the hour, minute, and second details. | `mogdb=# select CURRENT_DATE; date ----- 2018-02-02 (1 row)` |
+  | CURRENT_TIME         | Obtains the current time, excluding the year, month, and day. | `mogdb=# select CURRENT_TIME; timetz -------- 00:39:34.633938+08 (1 row)` |
+  | CURRENT_TIMESTAMP(n) | Obtains the current date and time, including year, month, day, hour, minute, and second.<br />NOTE:<br />**n** indicates the number of digits after the decimal point in the time string. | `mogdb=# select CURRENT_TIMESTAMP(6); timestamptz ----------- 2018-02-02 00:39:55.231689+08 (1 row)` |
+
+- [Proposal] Do not use scalar subquery statements. A scalar subquery appears in the output list of a SELECT statement. In the following example, the underlined part is a scalar subquery statement:
+
+  ```sql
+  SELECT id, (SELECT COUNT(*) FROM films f WHERE f.did = s.id) FROM staffs_p1 s;
+  ```
+
+  Scalar subqueries often result in query performance deterioration. During application development, scalar subqueries need to be converted into equivalent table associations based on the service logic.
+
+- [Proposal] In **WHERE** clauses, the filter conditions should be collated. The condition that few records are selected for reading (the number of filtered records is small) is listed at the beginning.
+
+- [Proposal] Filter conditions in **WHERE** clauses should comply with unilateral rules, that is, to place the column name on one side of a comparison operator. In this way, the optimizer automatically performs pruning optimization in some scenarios. Filter conditions in a **WHERE** clause will be displayed in **col op expression** format, where **col** indicates a table column, **op** indicates a comparison operator, such as = and >, and **expression** indicates an expression that does not contain a column name. Example:
+
+  ```sql
+  SELECT id, from_image_id, from_person_id, from_video_id FROM face_data WHERE current_timestamp(6) - time < '1 days'::interval;
+  ```
+
+  The modification is as follows:
+
+  ```sql
+  SELECT id, from_image_id, from_person_id, from_video_id FROM face_data where time >  current_timestamp(6) - '1 days'::interval;
+  ```
+
+- [Proposal] Do not perform unnecessary collation operations. Collation requires a large amount of memory and CPU. If service logic permits, **ORDER BY** and **LIMIT** can be combined to reduce resource overheads. By default, MogDB perform collation by ASC & NULL LAST.
+
+- [Proposal] When the **ORDER BY** clause is used for collation, specify collation modes (ASC or DESC), and use NULL FIRST or NULL LAST for NULL record sorting.
+
+- [Proposal] Do not rely on only the **LIMIT** clause to return the result set displayed in a specific sequence. Combine **ORDER BY** and **LIMIT** clauses for some specific result sets and use **OFFSET** to skip specific results if necessary.
+
+- [Proposal] If the service logic is accurate, you are advised to use **UNION ALL** instead of **UNION**.
+
+- [Proposal] If a filter condition contains only an **OR** expression, convert the **OR** expression to **UNION ALL** to improve performance. SQL statements that use **OR** expressions cannot be optimized, resulting in slow execution. Example:
+
+  ```sql
+  SELECT * FROM scdc.pub_menu
+  WHERE (cdp= 300 AND inline=301) OR (cdp= 301 AND inline=302) OR (cdp= 302 ANDinline=301);
+  ```
+
+  Convert the statement to the following:
+
+  ```sql
+  SELECT * FROM scdc.pub_menu
+  WHERE (cdp= 300 AND inline=301)
+  union all
+  SELECT * FROM scdc.pub_menu
+  WHERE (cdp= 301 AND inline=302)
+  union all
+  SELECT * FROM tablename
+  WHERE (cdp= 302 AND inline=301)
+  ```
+
+- [Proposal] If an **in(val1, val2, val3…)** expression contains a large number of columns, you are advised to replace it with the **in (values (va11), (val2),(val3)…)** statement. The optimizer will automatically convert the **IN** constraint into a non-correlated subquery to improve the query performance.
+
+- [Proposal] Replace **(not) in** with **(not) exist** when associated columns do not contain **NULL** values. For example, in the following query statement, if the **T1.C1** column does not contain any **NULL** value, add the **NOT NULL** constraint to the **T1.C1** column, and then rewrite the statements.
+
+  ```sql
+  SELECT * FROM T1 WHERE T1.C1 NOT IN (SELECT T2.C2 FROM T2);
+  ```
+
+  Rewrite the statement as follows:
+
+  ```sql
+  SELECT * FROM T1 WHERE NOT EXISTS (SELECT  * FROM T1,T2 WHERE T1.C1=T2.C2);
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > - If the value of the T1.C1 column is not **NOT NULL**, the preceding rewriting cannot be performed.
+  > - If the **T1.C1** column is the output of a subquery, check whether the output is **NOT NULL** based on the service logic.
+
+- [Proposal] Use cursors instead of the **LIMIT OFFSET** syntax to perform pagination queries to avoid resource overheads caused by multiple executions. A cursor must be used in a transaction, and you must disable the cursor and commit the transaction once the query is finished.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/tool-interconnection/jdbc-configuration.md b/product/en/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/tool-interconnection/jdbc-configuration.md
new file mode 100644
index 0000000000000000000000000000000000000000..cd91b5d436344dfb0036885b0dc28475a40e3042
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/tool-interconnection/jdbc-configuration.md
@@ -0,0 +1,62 @@
+---
+title: JDBC Configuration
+summary: JDBC Configuration
+author: Guo Huan
+date: 2021-10-14
+---
+
+# JDBC Configuration
+
+Currently, third-party tools related to MogDB are connected through JDBC. This section describes the precautions for configuring the tool.
+
+## Connection Parameters
+
+- [Notice] When a third-party tool connects to MogDB through JDBC, JDBC sends a connection request to MogDB. By default, the following configuration parameters are added. For details, see the implementation of the ConnectionFactoryImpl class in the JDBC code.
+
+  ```
+  params = {
+  { "user", user },
+  { "database", database },
+  { "client_encoding", "UTF8" },
+  { "DateStyle", "ISO" },
+  { "extra_float_digits", "3" },
+  { "TimeZone",  createPostgresTimeZone() },
+  };
+  ```
+
+  These parameters may cause the JDBC and **gsql** clients to display inconsistent data, for example, date data display mode, floating point precision representation, and timezone.
+
+  If the result is not as expected, you are advised to explicitly set these parameters in the Java connection setting.
+
+- [Proposal] When connecting to the database through JDBC, ensure that the following three time zones are the same:
+
+  - Time zone of the host where the JDBC client is located
+
+  - Time zone of the host where the MogDB database instance is located.
+
+  - Time zone used during MogDB database instance configuration.
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** For details about how to set the time zone, see "[Setting the Time Zone and Time](3-modifying-os-configuration#setting-the-time-zone-and-time)" in *Installation Guide*.
+
+## fetchsize
+
+[Notice] To use **fetchsize** in applications, disable **autocommit**. Enabling the **autocommit** switch makes the **fetchsize** configuration invalid.
+
+## autocommit
+
+[Proposal] You are advised to enable **autocommit** in the code for connecting to MogDB by the JDBC. If **autocommit** needs to be disabled to improve performance or for other purposes, applications need to ensure their transactions are committed. For example, explicitly commit translations after specifying service SQL statements. Particularly, ensure that all transactions are committed before the client exits.
+
+## Connection Releasing
+
+[Proposal] You are advised to use connection pools to limit the number of connections from applications. Do not connect to a database every time you run an SQL statement.
+
+[Proposal] After an application completes its tasks, disconnect its connection to MogDB to release occupied resources. You are advised to set the session timeout interval in the jobs.
+
+[Proposal] Reset the session environment before releasing connections to the JDBC connection tool. Otherwise, historical session information may cause object conflicts.
+
+- If GUC parameters are set in the connection, run **SET SESSION AUTHORIZATION DEFAULT;RESET ALL;** to clear the connection status before you return the connection to the connection pool.
+- If a temporary table is used, delete the temporary table before you return the connection to the connection pool.
+
+## CopyManager
+
+[Proposal] In the scenario where the ETL tool is not used and real-time data import is required, it is recommended that you use the **CopyManager** interface driven by the MogDB JDBC to import data in batches during application development.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/1-oracle_fdw.md b/product/en/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/1-oracle_fdw.md
new file mode 100644
index 0000000000000000000000000000000000000000..18d35ec9e1bb03b517824d2064416eb9b2ca3b38
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/1-oracle_fdw.md
@@ -0,0 +1,49 @@
+---
+title: oracle_fdw
+summary: oracle_fdw
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# oracle_fdw
+
+oracle_fdw is an open-source plug-in. MogDB is developed and adapted based on the open-source oracle_fdw Release 2.2.0.
+
+To compile and use oracle_fdw, the Oracle development packages must be included in the environment. Therefore, MogDB does not compile oracle_fdw by default. The following describes how to compile and use oracle_fdw.
+
+## Compiling oracle_fdw
+
+To compile oracle_fdw, install the Oracle development library and header files from the [Oracle official website](https://www.oracle.com/database/technologies/instant-client/downloads.html).
+
+Select a proper running environment and version, download **Basic Package** and **SDK Package**, and install them. In addition, **SQLPlus Package** is a client tool of the Oracle server. You can install it as required to connect to the Oracle server for testing.
+
+After installing the development packages, start oracle_fdw compilation. Add the **-enable-oracle-fdw** option when running the **configure** command. Perform compilation using the common MogDB compilation method.
+
+After the compilation is complete, the **oracle_fdw.so** file is generated in **lib/postgresql/** in the installation directory. SQL files and control files related to oracle_fdw are stored in **share/postgresql/extension/** in the installation directory.
+
+If the **-enable-oracle-fdw** option is not added during compilation and installation, compile oracle_fdw again after MogDB is installed, and then manually place the **oracle\_fdw.so** file to **lib/postgresql/** in the installation directory, and place **oracle\_fdw-1.0-1.1.sql**, **oracle\_fdw-1.1.sql**, and **oracle\_fdw.control** to **share/postgresql/extension/** in the installation directory.
+
+## Using oracle_fdw
+
+- To use oracle_fdw, install and connect to the Oracle server.
+- Load the oracle_fdw extension using **CREATE EXTENSION oracle_fdw;**.
+- Create a server object using **CREATE SERVER**.
+- Create a user mapping using **CREATE USER MAPPING**.
+- Create a foreign table using **CREATE FOREIGN TABLE**. The structure of the foreign table must be the same as that of the Oracle table. The first column in the table on the Oracle server must be unique, for example, **PRIMARY KEY** and **UNIQUE**.
+- Perform normal operations on the foreign table, such as **INSERT**, **UPDATE**, **DELETE**, **SELECT**, **EXPLAIN**, **ANALYZE** and **COPY**.
+- Drop a foreign table using **DROP FOREIGN TABLE**.
+- Drop a user mapping using **DROP USER MAPPING**.
+- Drop a server object using **DROP SERVER**.
+- Drop an extension using **DROP EXTENSION oracle_fdw;**.
+
+## Common Issues
+
+- When a foreign table is created on the MogDB, the table is not created on the Oracle server. You need to use the Oracle client to connect to the Oracle server to create a table.
+- The Oracle user used for executing **CREATE USER MAPPING** must have the permission to remotely connect to the Oracle server and perform operations on tables. Before using a foreign table, you can use the Oracle client on the machine where the MogDB server is located and use the corresponding user name and password to check whether the Oracle server can be successfully connected and operations can be performed.
+- When **CREATE EXTENSION oracle_fdw;** is executed, the message **libclntsh.so: cannot open shared object file: No such file or directory** is displayed. The reason is that the Oracle development library **libclntsh.so** is not in the related path of the system. You can find the specific path of **libclntsh.so**, and then add the folder where the **libclntsh.so** file is located to **/etc/ld.so.conf**. For example, if the path of **libclntsh.so** is **/usr/lib/oracle/11.2/client64/lib/libclntsh.so.11.1**, add **/usr/lib/oracle/11.2/client64/lib/** to the end of **/etc/ld.so.conf**. Run the **ldconfig** command for the modification to take effect. Note that this operation requires the **root** permission.
+
+## Precautions
+
+- **SELECT JOIN** between two Oracle foreign tables cannot be pushed down to the Oracle server for execution. Instead, **SELECT JOIN** is divided into two SQL statements and transferred to the Oracle server for execution. Then the processing result is summarized in the MogDB.
+- The **IMPORT FOREIGN SCHEMA** syntax is not supported.
+- **CREATE TRIGGER** cannot be executed for foreign tables.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/2-mysql_fdw.md b/product/en/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/2-mysql_fdw.md
new file mode 100644
index 0000000000000000000000000000000000000000..981b7691d5f1796fb341a0da2d269f51348d1ee9
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/2-mysql_fdw.md
@@ -0,0 +1,49 @@
+---
+title: mysql_fdw
+summary: mysql_fdw
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# mysql_fdw
+
+mysql_fdw is an open-source plug-in. MogDB is developed and adapted based on the open-source [mysql_fdw Release 2.5.3](https://github.com/EnterpriseDB/mysql_fdw/archive/REL-2_5_3.tar.gz).
+
+To compile and use mysql_fdw, the MariaDB development packages must be included in the environment. Therefore, MogDB does not compile mysql_fdw by default. The following describes how to compile and use mysql_fdw.
+
+## Compiling mysql_fdw
+
+To compile mysql_fdw, install the development library and header file of MariaDB. You are advised to use the official MariaDB repositories. For details about how to select a repository, visit [http://downloads.mariadb.org/mariadb/repositories/](http://downloads.mariadb.org/mariadb/repositories).
+
+After the repository is configured, run the **yum install MariaDB-devel MariaDB-shared** command to install the related development libraries. In addition, **MariaDB-client** is a client tool of the MariaDB. You can install it as required to connect to the MariaDB for testing.
+
+After installing the development packages, start mysql_fdw compilation. Add the **-enable-mysql-fdw** option when running the **configure** command. Perform compilation using the common MogDB compilation method.
+
+After the compilation is complete, the **mysql_fdw.so** file is generated in **lib/postgresql/** in the installation directory. SQL files and control files related to mysql_fdw are stored in **share/postgresql/extension/** in the installation directory.
+
+If the **-enable-mysql-fdw** option is not added during compilation and installation, compile mysql_fdw again after MogDB is installed, and then manually place the **mysql\_fdw.so** file to **lib/postgresql/** in the installation directory, and place **mysql\_fdw-1.0-1.1.sql**, **mysql\_fdw-1.1.sql**, and **mysql\_fdw.control** to **share/postgresql/extension/** in the installation directory.
+
+## Using mysql_fdw
+
+- To use mysql_fdw, install and connect to MariaDB or MySQL server.
+- Load the mysql_fdw extension using **CREATE EXTENSION mysql_fdw;**.
+- Create a server object using **CREATE SERVER**.
+- Create a user mapping using **CREATE USER MAPPING**.
+- Create a foreign table using **CREATE FOREIGN TABLE**. The structure of the foreign table must be the same as that of the MySQL or MariaDB table. The first column in the table on the MySQL or MariaDB must be unique, for example, **PRIMARY KEY** and **UNIQUE**.
+- Perform normal operations on the foreign table, such as **INSERT**, **UPDATE**, **DELETE**, **SELECT**, **EXPLAIN**, **ANALYZE** and **COPY**.
+- Drop a foreign table using **DROP FOREIGN TABLE**.
+- Drop a user mapping using **DROP USER MAPPING**.
+- Drop a server object using **DROP SERVER**.
+- Drop an extension using **DROP EXTENSION mysql_fdw;**.
+
+## Common Issues
+
+- When a foreign table is created on the MogDB, the table is not created on the MariaDB or MySQL server. You need to use the MariaDB or MySQL server client to connect to the MariaDB or MySQL server to create a table.
+- The MariaDB or MySQL server user used for creating **USER MAPPING** must have the permission to remotely connect to the MariaDB or MySQL server and perform operations on tables. Before using a foreign table, you can use the MariaDB or MySQL server client on the machine where the MogDB server is located and use the corresponding user name and password to check whether the MariaDB or MySQL server can be successfully connected and operations can be performed.
+- The **Can't initialize character set SQL_ASCII (path: compiled_in)** error occurs when the DML operation is performed on a foreign table. MariaDB does not support the **SQL_ASCII** encoding format. Currently, this problem can be resolved only by modifying the encoding format of the MogDB database. Change the database encoding format to **update pg_database set encoding = pg_char_to_encoding('UTF-8') where datname = 'postgres';**. Set **datname** based on the actual requirements. After the encoding format is changed, start a gsql session again so that mysql_fdw can use the updated parameters. You can also use **-locale=LOCALE** when running **gs_initdb** to set the default encoding format to non-SQL_ASCII.
+
+## Precautions
+
+- **SELECT JOIN** between two MySQL foreign tables cannot be pushed down to the MariaDB or MySQL server for execution. Instead, **SELECT JOIN** is divided into two SQL statements and transferred to the MariaDB or MySQL server for execution. Then the processing result is summarized in the MogDB.
+- The **IMPORT FOREIGN SCHEMA** syntax is not supported.
+- **CREATE TRIGGER** cannot be executed for foreign tables.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/3-postgres_fdw.md b/product/en/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/3-postgres_fdw.md
new file mode 100644
index 0000000000000000000000000000000000000000..50864c9e199e3024164a19597cd6f9f662f09489
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/3-postgres_fdw.md
@@ -0,0 +1,37 @@
+---
+title: postgres_fdw
+summary: postgres_fdw
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# postgres_fdw
+
+postgres_fdw is an open-source plug-in. Its code is released with the PostgreSQL source code. MogDB is developed and adapted based on the open-source postgres_fdw source code (<https://ftp.postgresql.org/pub/source/v9.4.26/postgresql-9.4.26.tar.gz>) in PostgreSQL 9.4.26.
+
+The postgres_fdw plug-in is involved in compilation by default. After installing MogDB using the installation package, you can directly use postgres_fdw without performing other operations.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** Currently, postgres_fdw supports only connection between MogDB databases.
+
+## Using postgres_fdw
+
+- Load the postgres_fdw extension using **CREATE EXTENSION postgres_fdw;**.
+- Create a server object using **CREATE SERVER**.
+- Create a user mapping using **CREATE USER MAPPING**.
+- Create a foreign table using **CREATE FOREIGN TABLE**. The structure of the foreign table must be the same as that of the remote MogDB table.
+- Perform normal operations on the foreign table, such as **INSERT**, **UPDATE**, **DELETE**, **SELECT**, **EXPLAIN**, **ANALYZE** and **COPY**.
+- Drop a foreign table using **DROP FOREIGN TABLE**.
+- Drop a user mapping using **DROP USER MAPPING**.
+- Drop a server object using **DROP SERVER**.
+- Drop an extension using **DROP EXTENSION postgres_fdw;**.
+
+## Common Issues
+
+- When a foreign table is created on the MogDB, the table is not created on the remote MogDB database. You need to use the Oracle client to connect to the remote MogDB database to create a table.
+- The MogDB user used for executing **CREATE USER MAPPING** must have the permission to remotely connect to the MogDB database and perform operations on tables. Before using a foreign table, you can use the gsql client on the local machine and use the corresponding user name and password to check whether the remote MogDB database can be successfully connected and operations can be performed.
+
+## Precautions
+
+- **SELECT JOIN** between two postgres_fdw foreign tables cannot be pushed down to the remote MogDB database for execution. Instead, **SELECT JOIN** is divided into two SQL statements and transferred to the remote MogDB database for execution. Then the processing result is summarized locally.
+- The **IMPORT FOREIGN SCHEMA** syntax is not supported.
+- **CREATE TRIGGER** cannot be executed for foreign tables.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/dblink.md b/product/en/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/dblink.md
new file mode 100644
index 0000000000000000000000000000000000000000..9206f7629751653ee8a5a9b1f8f7b8cdd594e498
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/dblink.md
@@ -0,0 +1,80 @@
+---
+title: dblink
+summary: dblink
+author: Guo Huan
+date: 2021-11-22
+---
+
+# dblink
+
+dblink is a tool that can connect to other MogDB databases in an MogDB database session. The connection parameters supported by dblink are the same as those supported by libpq. For details, see [Connection Characters](6-connection-characters). By default, MogDB does not compile dblink. The following describes how to compile and use dblink.
+
+## Compiling dblink
+
+Currently, the source code of dblink is stored in the [contrib/dblink](https://gitee.com/opengauss/openGauss-server/tree/master/contrib/dblink) directory. After the MogDB database is compiled and installed, if you need to use the dblink, go to the preceding directory and run the following command to compile and install the dblink:
+
+```bash
+make
+make install
+```
+
+## Common dblink Functions
+
+- Load the dblink extension.
+
+  ```sql
+  CREATE EXTENSION dblink;
+  ```
+
+- Open a persistent connection to a remote database.
+
+  ```sql
+  SELECT dblink_connect(text connstr);
+  ```
+
+- Close a persistent connection to a remote database.
+
+  ```sql
+  SELECT dblink_disconnect();
+  ```
+
+- Query data in a remote database.
+
+  ```sql
+  SELECT * FROM dblink(text connstr, text sql);
+  ```
+
+- Execute commands in a remote database.
+
+  ```sql
+  SELECT dblink_exec(text connstr, text sql);
+  ```
+
+- Return the names of all opened dblinks.
+
+  ```sql
+  SELECT dblink_get_connections();
+  ```
+
+- Send an asynchronous query to a remote database.
+
+  ```sql
+  SELECT dblink_send_query(text connname, text sql);
+  ```
+
+- Check whether the connection is busy with an asynchronous query.
+
+  ```sql
+  SELECT dblink_is_busy(text connname);
+  ```
+
+- Delete the extension.
+
+  ```sql
+  DROP EXTENSION dblink;
+  ```
+
+## Precautions
+
+- Currently, dblink allows only the MogDB database to access another MogDB database and does not allow the MogDB database to access a PostgreSQL database.
+- Currently, dblink does not support the thread pool mode.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/fdw-introduction.md b/product/en/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/fdw-introduction.md
new file mode 100644
index 0000000000000000000000000000000000000000..d1d655fbafa870f9a6b002f80a28d0d3a95bce1d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/fdw-introduction.md
@@ -0,0 +1,10 @@
+---
+title: Introduction
+summary: Introduction
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Introduction
+
+The foreign data wrapper (FDW) of the MogDB can implement cross-database operations between MogDB databases and remote databases. Currently, the following remote servers are supported: Oracle, MySQL(MariaDB), PostgreSQL/openGauss/MogDB(postgres_fdw), file_fdw, dblink.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/file_fdw.md b/product/en/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/file_fdw.md
new file mode 100644
index 0000000000000000000000000000000000000000..b85647201c5843241e64e57ffd28b5d1d9e7f03c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/file_fdw.md
@@ -0,0 +1,81 @@
+---
+title: file_fdw
+summary: file_fdw
+author: Guo Huan
+date: 2021-10-19
+---
+
+# file_fdw
+
+The file_fdw module provides the external data wrapper file_fdw, which can be used to access data files in the file system of a server. The format of the data files must be readable by the **COPY FROM** command. For details, see [COPY](41-COPY). file_fdw is only used to access readable data files, but cannot write data to the data files.
+
+By default, the file_fdw is compiled in MogDB. During database initialization, the plug-in is created in the **pg_catalog** schema.
+
+When you create a foreign table using file_fdw, you can add the following options:
+
+- filename
+
+  File to be read. This parameter is mandatory and must be an absolute path.
+
+- format
+
+  File format of the remote server, which is the same as the **FORMAT** option in the **COPY** statement. The value can be **text**, **csv**, **binary**, or **fixed**.
+
+- header
+
+  Whether the specified file has a header, which is the same as the **HEADER** option of the **COPY** statement.
+
+- delimiter
+
+  File delimiter, which is the same as the **DELIMITER** option of the **COPY** statement.
+
+- quote
+
+  Quote character of a file, which is the same as the **QUOTE** option of the **COPY** statement.
+
+- escape
+
+  Escape character of a file, which is the same as the **ESCAPE** option of the **COPY** statement.
+
+- null
+
+  Null string of a file, which is the same as the **NULL** option of the **COPY** statement.
+
+- encoding
+
+  Encoding of a file, which is the same as the **ENCODING** option of the **COPY** statement.
+
+- force_not_null
+
+  File-level null option, which is a Boolean option. If it is true, the value of the declared field cannot be an empty string. This option is the same as the **FORCE_NOT_NULL** option of the **COPY** statement.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - file_fdw does not support the **OIDS** and **FORCE\_QUOTE** options of the **COPY** statement.
+> - These options can only be declared for a foreign table or the columns of the foreign table, not for the file_fdw itself, nor for the server or user mapping that uses file_fdw.
+> - To modify table-level options, you must obtain the system administrator role permissions. For security reasons, only the system administrator can determine the files to be read.
+> - For an external table that uses file_fdw, **EXPLAIN** displays the name and size (in bytes) of the file to be read. If the keyword **COSTS OFF** is specified, the file size is not displayed.
+
+## Using file_fdw
+
+- To create a server object, use **CREATE SERVER**.
+
+- To create a user mapping, use **CREATE USER MAPPING**.
+
+- To create a foreign table, use **CREATE FOREIGN TABLE**.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > - The structure of the foreign table must be consistent with the data in the specified file.
+  > - When a foreign table is queried, no write operation is allowed.
+
+- To drop a foreign table, use **DROP FOREIGN TABLE**.
+
+- To drop a user mapping, use **DROP USER MAPPING**.
+
+- To drop a server object, use **DROP SERVER**.
+
+## Precautions
+
+- To use file_fdw, you need to specify the file to be read. Prepare the file and grant the read permission on the file for the database to access the file.
+- **DROP EXTENSION file_fdw** is not supported.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/logical-replication/1-logical-decoding.md b/product/en/docs-mogdb/v3.0/developer-guide/logical-replication/1-logical-decoding.md
new file mode 100644
index 0000000000000000000000000000000000000000..66f24ddaf79e33b3c232365eaed8e65731e7880d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/logical-replication/1-logical-decoding.md
@@ -0,0 +1,53 @@
+---
+title: Overview
+summary: Overview
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# Overview
+
+## Function
+
+The data replication capabilities supported by MogDB are as follows:
+
+Data is periodically synchronized to heterogeneous databases (such as Oracle databases) using a data migration tool. Real-time data replication is not supported. Therefore, the requirements for real-time data synchronization to heterogeneous databases are not satisfied.
+
+MogDB provides the logical decoding function to generate logical logs by decoding Xlogs. A target database parses logical logs to replicate data in real time. For details, see Figure 1. Logical replication reduces the restrictions on target databases, allowing for data synchronization between heterogeneous databases and homogeneous databases with different forms. It allows data to be read and written during data synchronization on a target database, reducing the data synchronization latency.
+
+**Figure 1** Logical replication
+
+![image-20210512181021060](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/logical-decoding-2.png)
+
+Logical replication consists of logical decoding and data replication. Logical decoding outputs logical logs by transaction. The database service or middleware parses the logical logs to implement data replication. Currently, MogDB supports only logical decoding. Therefore, this section involves only logical decoding.
+
+Logical decoding provides basic transaction decoding capabilities for logical replication. MogDB uses SQL functions for logical decoding. This method features easy function calling, requires no tools to obtain logical logs, and provides specific interfaces for interconnecting with external replay tools, saving the need of additional adaptation.
+
+Logical logs are output only after transactions are committed because they use transactions as the unit and logical decoding is driven by users. Therefore, to prevent Xlogs from being reclaimed by the system when transactions start and prevent required transaction information from being reclaimed by **VACUUM**, MogDB introduces logical replication slots to block Xlog reclaiming.
+
+A logical replication slot means a stream of changes that can be replayed in other databases in the order they were generated in the original database. Each owner of logical logs maintains one logical replication slot.
+
+## Precautions
+
+- DDL statement decoding is not supported. When a specific DDL statement (for example, to truncate an ordinary table or exchange a partitioned table) is executed, decoded data may be lost.
+- Decoding for column-store data and data page replication is not supported.
+- Logical decoding is not supported on the cascaded standby node.
+- After a DDL statement (for example, **ALTER TABLE**) is executed, the physical logs that are not decoded before the DDL statement execution may be lost.
+- The size of a single tuple cannot exceed 1 GB, and decoded data may be larger than inserted data. Therefore, it is recommended that the size of a single tuple be less than or equal to 500 MB.
+- openGauss supports the following data types for decoding: **INTEGER**, **BIGINT**, **SMALLINT**, **TINYINT**, **SERIAL**, **SMALLSERIAL**, **BIGSERIAL**, **FLOAT**, **DOUBLE PRECISION**, **DATE**, **TIME[WITHOUT TIME ZONE]**, **TIMESTAMP[WITHOUT TIME ZONE]**, **CHAR(***n***)**, **VARCHAR(***n***)**, and **TEXT**.
+- Currently, SSL connections are not supported by default. If SSL connections are required, set the GUC parameter **ssl** to **on**.
+- The logical replication slot name must contain fewer than 64 characters and contain only one or more types of the following characters: lowercase letters, digits, and underscores (_).
+- Currently, logical replication does not support the MOT feature.
+- After the database where a logical replication slot resides is deleted, the replication slot becomes unavailable and needs to be manually deleted.
+- Only the UTF-8 character set is supported.
+- To decode multiple databases, you need to create a stream replication slot in each database and start decoding. Logs need to be scanned for decoding of each database.
+- Forcible startup is not supported. After forcible startup, you need to export all data again.
+- During decoding on the standby node, the decoded data may increase during switchover and failover, which needs to be manually filtered out. When the quorum protocol is used, switchover and failover should be performed on the standby node that is to be promoted to primary, and logs must be synchronized from the primary node to the standby node.
+- The same replication slot for decoding cannot be used between the primary node and standby node or between different standby nodes at the same time. Otherwise, data inconsistency occurs.
+- Replication slots can only be created or deleted on hosts.
+- After the database is restarted due to a fault or the logical replication process is restarted, duplicate decoded data exists. You need to filter out the duplicate data.
+- If the computer kernel is faulty, garbled characters are displayed during decoding which need to be manually or automatically filtered out.
+- Currently, the logical decoding on the standby node does not support enabling the ultimate RTO.
+- Ensure that the long transaction is not started during the creation of the logical replication slot. If the long transaction is started, the creation of the logical replication slot will be blocked.
+- Interval partitioned tables cannot be replicated.
+- After a DDL statement is executed in a transaction, the DDL statement and subsequent statements are not decoded.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/logical-replication/2-logical-decoding-by-sql-function-interfaces.md b/product/en/docs-mogdb/v3.0/developer-guide/logical-replication/2-logical-decoding-by-sql-function-interfaces.md
new file mode 100644
index 0000000000000000000000000000000000000000..f02c7c08f98b9706bf07248d63c26cd4e9d4edbc
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/logical-replication/2-logical-decoding-by-sql-function-interfaces.md
@@ -0,0 +1,83 @@
+---
+title: Logical Decoding by SQL Function Interfaces
+summary: Logical Decoding by SQL Function Interfaces
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# Logical Decoding by SQL Function Interfaces
+
+In MogDB, you can call SQL functions to create, delete, and push logical replication slots, as well as obtain decoded transaction logs.
+
+## Prerequisites
+
+- Currently, logical logs are extracted from host nodes. Since SSL connections are disabled by default, to perform logical replication, set the GUC parameter **ssl** to **on** on host nodes.
+
+  > **NOTE:** For security purposes, ensure that SSL connections are enabled.
+
+- The GUC parameter **wal_level** is set to **logical**.
+
+- The GUC parameter max_replication_slots is set to a value greater than the number of physical replication slots and logical replication slots required by each node.
+
+  Physical replication slots provide an automatic method to ensure that Xlogs are not removed from a primary node before they are received by all the standby nodes and secondary nodes. That is, physical replication slots are used to support HA clusters. The number of physical replication slots required by a cluster is equal to the ratio of standby and secondary nodes to the primary node. For example, if an HA cluster has 1 primary node, 1 standby node, and 1 secondary node, the number of required physical replication slots will be 2. If an HA cluster has 1 primary node and 3 standby nodes, the number of required physical replication slots will be 3.
+
+  Plan the number of logical replication slots as follows:
+
+  - A logical replication slot can carry changes of only one database for decoding. If multiple databases are involved, create multiple logical replication slots.
+  - If logical replication is needed by multiple target databases, create multiple logical replication slots in the source database. Each logical replication slot corresponds to one logical replication link.
+
+- Only database administrators and users with the **REPLICATION** permission can perform operations in this scenario.
+
+## Procedure
+
+1. Log in to the primary node of the MogDB cluster as the cluster installation user.
+
+2. Run the following command to connect to the default database **postgres**:
+
+   ```
+   gsql -d postgres -p 16000 -r
+   ```
+
+   In this command, **16000** is the database port number. It can be replaced by an actual port number.
+
+3. Create a logical replication slot named **slot1**.
+
+   ```
+   mogdb=# SELECT * FROM pg_create_logical_replication_slot('slot1', 'mppdb_decoding');
+   slotname | xlog_position
+   ----------+---------------
+   slot1    | 0/601C150
+   (1 row)
+   ```
+
+4. Create a table **t** in the database and insert data into it.
+
+   ```
+   mogdb=# CREATE TABLE t(a int PRIMARY KEY, b int);
+   mogdb=# INSERT INTO t VALUES(3,3);
+   ```
+
+5. Read the decoding result of **slot1**. The number of decoded records is 4096.
+
+   ```
+   mogdb=# SELECT * FROM pg_logical_slot_peek_changes('slot1', NULL, 4096);
+   location  |  xid  | data
+   -----------+-------+-------------------------------------------------------------------------------------------------------------------------------------------------
+   -------------------------------------------
+    0/601C188 | 1010023 | BEGIN 1010023
+    0/601ED60 | 1010023 | COMMIT 1010023 CSN 1010022
+    0/601ED60 | 1010024 | BEGIN 1010024
+    0/601ED60 | 1010024 | {"table_name":"public.t","op_type":"INSERT","columns_name":["a","b"],"columns_type":["integer","integer"],"columns_val":["3","3"],"old_keys_name":[],"old_keys_type":[],"old_keys_val":[]}
+    0/601EED8 | 1010024 | COMMIT 1010024 CSN 1010023
+   (5 rows)
+   ```
+
+6. Delete the logical replication slot **slot1**.
+
+   ```
+   mogdb=#  SELECT * FROM pg_drop_replication_slot('slot1');
+    pg_drop_replication_slot
+   --------------------------
+
+   (1 row)
+   ```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/materialized-view/1-materialized-view-overview.md b/product/en/docs-mogdb/v3.0/developer-guide/materialized-view/1-materialized-view-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..b5ddb309b5b48e0c4fc630fab240b65e1230c17a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/materialized-view/1-materialized-view-overview.md
@@ -0,0 +1,10 @@
+---
+title: Materialized View Overview
+summary: Materialized View Overview
+author: Guo Huan
+date: 2021-05-21
+---
+
+# Materialized View Overview
+
+A materialized view is a special physical table, which is relative to a common view. A common view is a virtual table and has many application limitations. Any query on a view is actually converted into a query on an SQL statement, and performance is not actually improved. The materialized view actually stores the results of the statements executed by the SQL statement, and is used to cache the results.
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/materialized-view/2-full-materialized-view/1-full-materialized-view-overview.md b/product/en/docs-mogdb/v3.0/developer-guide/materialized-view/2-full-materialized-view/1-full-materialized-view-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..721d69a42595935535c885dd0a4e700b934aca3a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/materialized-view/2-full-materialized-view/1-full-materialized-view-overview.md
@@ -0,0 +1,10 @@
+---
+title: Overview
+summary: Overview
+author: Liuxu
+date: 2021-05-21
+---
+
+# Overview
+
+Full materialized views can be fully refreshed only. The syntax for creating a full materialized view is similar to the CREATE TABLE AS syntax.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/materialized-view/2-full-materialized-view/2-full-materialized-view-usage.md b/product/en/docs-mogdb/v3.0/developer-guide/materialized-view/2-full-materialized-view/2-full-materialized-view-usage.md
new file mode 100644
index 0000000000000000000000000000000000000000..80e76ef110c0f773e274b73aa839e50c74a4dd13
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/materialized-view/2-full-materialized-view/2-full-materialized-view-usage.md
@@ -0,0 +1,69 @@
+---
+title: Usage
+summary: Usage
+author: Guo Huan
+date: 2021-05-21
+---
+
+# Usage
+
+## Syntax
+
+- Create a full materialized view.
+
+  ```
+  CREATE MATERIALIZED VIEW [ view_name ] AS { query_block };
+  ```
+
+- Fullly refresh a materialized view.
+
+  ```
+  REFRESH MATERIALIZED VIEW [ view_name ];
+  ```
+
+- Delete a materialized view.
+
+  ```
+  DROP MATERIALIZED VIEW [ view_name ];
+  ```
+
+- Query a materialized view.
+
+  ```
+  SELECT * FROM [ view_name ];
+  ```
+
+## Examples
+
+```
+-- Prepare data.
+mogdb=# CREATE TABLE t1(c1 int, c2 int);
+mogdb=# INSERT INTO t1 VALUES(1, 1);
+mogdb=# INSERT INTO t1 VALUES(2, 2);
+
+-- Create a full materialized view.
+mogdb=# CREATE MATERIALIZED VIEW mv AS select count(*) from t1;
+
+-- Query the materialized view result.
+mogdb=# SELECT * FROM mv;
+ count
+-------
+     2
+(1 row)
+
+-- Insert data into the base table in the materialized view.
+mogdb=# INSERT INTO t1 VALUES(3, 3);
+
+-- Fully refresh a full materialized view.
+mogdb=# REFRESH MATERIALIZED VIEW mv;
+
+-- Query the materialized view result.
+mogdb=# SELECT * FROM mv;
+ count
+-------
+     3
+(1 row)
+
+-- Delete a materialized view.
+mogdb=# DROP MATERIALIZED VIEW mv;
+```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/materialized-view/2-full-materialized-view/3-full-materialized-view-support-and-constraints.md b/product/en/docs-mogdb/v3.0/developer-guide/materialized-view/2-full-materialized-view/3-full-materialized-view-support-and-constraints.md
new file mode 100644
index 0000000000000000000000000000000000000000..d0f35b92976a8681d9c77614c624b19b67093d98
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/materialized-view/2-full-materialized-view/3-full-materialized-view-support-and-constraints.md
@@ -0,0 +1,18 @@
+---
+title: Support and Constraints
+summary: Support and Constraints
+author: Liuxu
+date: 2021-05-21
+---
+
+# Support and Constraints
+
+## Supported Scenarios
+
+- Supports the same query scope as the CREATE TABLE AS statement does.
+- Supports index creation in full materialized views.
+- Supports ANALYZE and EXPLAIN.
+
+## Unsupported Scenarios
+
+Materialized views cannot be added, deleted, or modified. They support only query statements.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/materialized-view/3-incremental-materialized-view/1-incremental-materialized-view-overview.md b/product/en/docs-mogdb/v3.0/developer-guide/materialized-view/3-incremental-materialized-view/1-incremental-materialized-view-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..8da9c3df584795fc5ebd719cbfb74bcdb7a67037
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/materialized-view/3-incremental-materialized-view/1-incremental-materialized-view-overview.md
@@ -0,0 +1,10 @@
+---
+title: Overview
+summary: Overview
+author: Guo Huan
+date: 2021-05-21
+---
+
+# Overview
+
+Incremental materialized views can be incrementally refreshed. You need to manually execute statements to incrementally refresh materialized views in a period of time. The difference between the incremental and the full materialized views is that the incremental materialized view supports only a small number of scenarios. Currently, only base table scanning statements or UNION ALL can be used to create materialized views.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/materialized-view/3-incremental-materialized-view/2-incremental-materialized-view-usage.md b/product/en/docs-mogdb/v3.0/developer-guide/materialized-view/3-incremental-materialized-view/2-incremental-materialized-view-usage.md
new file mode 100644
index 0000000000000000000000000000000000000000..e0f81c2f02f11179bce9812a85cc1f7b04e1afaf
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/materialized-view/3-incremental-materialized-view/2-incremental-materialized-view-usage.md
@@ -0,0 +1,92 @@
+---
+title: Usage
+summary: Usage
+author: Guo Huan
+date: 2021-05-21
+---
+
+# Usage
+
+## Syntax
+
+- Create a incremental materialized view.
+
+  ```
+  CREATE INCREMENTAL MATERIALIZED VIEW [ view_name ] AS { query_block };
+  ```
+
+- Fully refresh a materialized view.
+
+  ```
+  REFRESH MATERIALIZED VIEW [ view_name ];
+  ```
+
+- Incrementally refresh a materialized view.
+
+  ```
+  REFRESH INCREMENTAL MATERIALIZED VIEW [ view_name ];
+  ```
+
+- Delete a materialized view.
+
+  ```
+  DROP MATERIALIZED VIEW [ view_name ];
+  ```
+
+- Query a materialized view.
+
+  ```
+  SELECT * FROM [ view_name ];
+  ```
+
+## Examples
+
+```
+-- Prepare data.
+CREATE TABLE t1(c1 int, c2 int);
+INSERT INTO t1 VALUES(1, 1);
+INSERT INTO t1 VALUES(2, 2);
+
+-- Create an incremental materialized view.
+mogdb=# CREATE INCREMENTAL MATERIALIZED VIEW mv AS SELECT * FROM t1;
+CREATE MATERIALIZED VIEW
+
+-- Insert data.
+mogdb=# INSERT INTO t1 VALUES(3, 3);
+INSERT 0 1
+
+-- Incrementally refresh a materialized view.
+mogdb=# REFRESH INCREMENTAL MATERIALIZED VIEW mv;
+REFRESH MATERIALIZED VIEW
+
+-- Query the materialized view result.
+mogdb=# SELECT * FROM mv;
+ c1 | c2
+----+----
+  1 |  1
+  2 |  2
+  3 |  3
+(3 rows)
+
+-- Insert data.
+mogdb=# INSERT INTO t1 VALUES(4, 4);
+INSERT 0 1
+
+-- Fullly refresh a materialized view.
+mogdb=# REFRESH MATERIALIZED VIEW mv;
+REFRESH MATERIALIZED VIEW
+
+-- Query the materialized view result.
+mogdb=# select * from mv;
+ c1 | c2
+----+----
+  1 |  1
+  2 |  2
+  3 |  3
+  4 |  4
+(4 rows)
+
+-- Delete a materialized view.
+mogdb=# DROP MATERIALIZED VIEW mv;
+DROP MATERIALIZED VIEW
+```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/materialized-view/3-incremental-materialized-view/3-incremental-materialized-view-support-and-constraints.md b/product/en/docs-mogdb/v3.0/developer-guide/materialized-view/3-incremental-materialized-view/3-incremental-materialized-view-support-and-constraints.md
new file mode 100644
index 0000000000000000000000000000000000000000..6bcde8f8819415fd63c2383b54e65b198a921ff8
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/materialized-view/3-incremental-materialized-view/3-incremental-materialized-view-support-and-constraints.md
@@ -0,0 +1,29 @@
+---
+title: Support and Constraints
+summary: Support and Constraints
+author: Guo Huan
+date: 2021-05-21
+---
+
+# Support and Constraints
+
+## Supported Scenarios
+
+- Supports statements for querying a single table.
+- Supports UNION ALL for querying multiple single tables.
+- Supports index creation in materialized views.
+- Supports the Analyze operation in materialized views.
+
+## Unsupported Scenarios
+
+- Multi-table join plans and subquery plans are not supported in materialized views.
+- Except for a few ALTER operations, most DDL operations cannot be performed on base tables in materialized views.
+- Materialized views cannot be added, deleted, or modified. They support only query statements.
+- The temporary table, hashbucket, unlog, or partitioned table cannot be used to create materialized views.
+- Materialized views cannot be created in nested mode (that is, a materialized view cannot be created in another materialized view).
+- The column-store tables are not supported. Only row-store tables are supported.
+- Materialized views of the UNLOGGED type are not supported, and the WITH syntax is not supported.
+
+## Constraints
+
+If the materialized view definition is UNION ALL, each subquery needs to use a different base table.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-1-plpgsql-overview.md b/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-1-plpgsql-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..2e19bda3747159d690ade3a33a22ef567d9a0cb7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-1-plpgsql-overview.md
@@ -0,0 +1,24 @@
+---
+title: Overview of PL/pgSQL Functions
+summary: Overview of PL/pgSQL Functions
+author: Guo Huan
+date: 2021-11-10
+---
+
+# Overview of PL/pgSQL Functions
+
+PL/pgSQL is a loadable procedural language.
+
+The functions created using PL/pgSQL can be used in any place where you can use built-in functions. For example, you can create calculation functions with complex conditions and use them to define operators or use them for index expressions.
+
+SQL is used by most databases as a query language. It is portable and easy to learn. Each SQL statement must be executed independently by a database server.
+
+In this case, when a client application sends a query to the server, it must wait for it to be processed, receive and process the results, and then perform some calculation before sending more queries to the server. If the client and server are not on the same machine, all these operations will cause inter-process communication and increase network loads.
+
+PL/pgSQL enables a whole computing part and a series of queries to be grouped inside a database server. This makes procedural language available and SQL easier to use. In addition, the client/server communication cost is reduced.
+
+- Extra round-trip communication between clients and servers is eliminated.
+- Intermediate results that are not required by clients do not need to be sorted or transmitted between the clients and servers.
+- Parsing can be skipped in multiple rounds of queries.
+
+PL/pgSQL can use all data types, operators, and functions in SQL. There are some common functions, such as  gs_extend_library.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-10-other-statements.md b/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-10-other-statements.md
new file mode 100644
index 0000000000000000000000000000000000000000..a5e5be684ea02c9c5ed0bd1a6c54bf4d1789d6a5
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-10-other-statements.md
@@ -0,0 +1,20 @@
+---
+title: Other Statements
+summary: Other Statements
+author: Guo Huan
+date: 2021-03-04
+---
+
+# Other Statements
+
+## Lock Operations
+
+MogDB provides multiple lock modes to control concurrent accesses to table data. These modes are used when Multi-Version Concurrency Control (MVCC) cannot give expected behaviors. Alike, most MogDB commands automatically apply appropriate locks to ensure that called tables are not deleted or modified in an incompatible manner during command execution. For example, when concurrent operations exist, **ALTER TABLE** cannot be executed on the same table.
+
+## Cursor Operations
+
+MogDB provides cursors as a data buffer for users to store execution results of SQL statements. Each cursor region has a name. Users can use SQL statements to obtain records one by one from cursors and grant the records to master variables, then being processed further by host languages.
+
+Cursor operations include cursor definition, open, fetch, and close operations.
+
+For the complete example of cursor operations, see [Explicit Cursor](1-11-cursors#explicit-cursor).
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-11-cursors.md b/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-11-cursors.md
new file mode 100644
index 0000000000000000000000000000000000000000..4a011600737b2d86b2516f1ada39f53ab7026af0
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-11-cursors.md
@@ -0,0 +1,178 @@
+---
+title: Cursors
+summary: Cursors
+author: Guo Huan
+date: 2021-03-04
+---
+
+# Cursors
+
+## Overview
+
+To process SQL statements, the stored procedure process assigns a memory segment to store context association. Cursors are handles or pointers pointing to context regions. With cursors, stored procedures can control alterations in context regions.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> If JDBC is used to call a stored procedure whose returned value is a cursor, the returned cursor cannot be used.
+
+Cursors are classified into explicit cursors and implicit cursors. [Table 1](#Table 1) shows the usage conditions of explicit and implicit cursors for different SQL statements.
+
+**Table 1** Cursor usage conditions<a id="Table 1"> </a>
+
+| SQL Statement                             | Cursor               |
+| :---------------------------------------- | :------------------- |
+| Non-query statements                      | Implicit             |
+| Query statements with single-line results | Implicit or explicit |
+| Query statements with multi-line results  | Explicit             |
+
+## Explicit Cursor
+
+An explicit cursor is used to process query statements, particularly when query results are multiple records.
+
+**Procedure**
+
+An explicit cursor performs the following six PL/SQL steps to process query statements:
+
+1. **Define a static cursor:** Define a cursor name and its corresponding **SELECT** statement.
+
+   [Figure 1](#static_cursor_define) shows the syntax diagram for defining a static cursor.
+
+   **Figure 1** static_cursor_define::=<a id="static_cursor_define"> </a>
+
+   ![static_cursor_define](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/cursors-1.jpg)
+
+   Parameter description:
+
+   - **cursor_name**: defines a cursor name.
+
+   - **parameter**: specifies cursor parameters. Only input parameters are allowed in the following format:
+
+     ```
+     parameter_name datatype
+     ```
+
+   - **select_statement**: specifies a query statement.
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+   > The system automatically determines whether the cursor can be used for backward fetches based on the execution plan.
+
+   **Define a dynamic cursor:** Define a **ref** cursor, which means that the cursor can be opened dynamically by a set of static SQL statements. First define the type of the **ref** cursor first and then the cursor variable of this cursor type. Dynamically bind a **SELECT** statement through **OPEN FOR** when the cursor is opened.
+
+   [Figure 2](#cursor_typename) and [Figure 3](#dynamic_cursor_define) show the syntax diagrams for defining a dynamic cursor.
+
+   **Figure 2** cursor_typename::=<a id="cursor_typename"> </a>
+
+   ![cursor_typename](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/cursors-2.png)
+
+   **Figure 3** dynamic_cursor_define::=<a id="dynamic_cursor_define"> </a>
+
+   ![dynamic_cursor_define](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/cursors-3.png)
+
+2. **Open the static cursor:** Execute the **SELECT** statement corresponding to the cursor. The query result is placed in the workspace and the pointer directs to the head of the workspace to identify the cursor result set. If the cursor query statement carries the **FOR UPDATE** option, the **OPEN** statement locks the data row corresponding to the cursor result set in the database table.
+
+   [Figure 4](#open_static_cursor) shows the syntax diagram for opening a static cursor.
+
+   **Figure 4** open_static_cursor::=<a id="open_static_cursor"> </a>
+
+   ![open_static_cursor](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/cursors-4.png)
+
+   **Open the dynamic cursor:** Use the **OPEN FOR** statement to open the dynamic cursor and the SQL statement is dynamically bound.
+
+   [Figure 5](#open_dynamic_cursor) shows the syntax diagrams for opening a dynamic cursor.
+
+   **Figure 5** open_dynamic_cursor::=<a id="open_dynamic_cursor"> </a>
+
+   ![open_dynamic_cursor](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/cursors-5.png)
+
+   A PL/SQL program cannot use the OPEN statement to repeatedly open a cursor.
+
+3. **Fetch cursor data**: Retrieve data rows in the result set and place them in specified output variables.
+
+   [Figure 6](#fetch_cursor) shows the syntax diagrams for fetching cursor data.
+
+   **Figure 6** fetch_cursor::=<a id="fetch_cursor"> </a>
+
+   ![fetch_cursor](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/cursors-6.png)
+
+4. Process the record.
+
+5. Continue to process until the active set has no record.
+
+6. **Close the cursor**: When fetching and finishing the data in the cursor result set, close the cursor immediately to release system resources used by the cursor and invalidate the workspace of the cursor so that the **FETCH** statement cannot be used to fetch data any more. A closed cursor can be reopened by an OPEN statement.
+
+   [Figure 7](#close_cursor) shows the syntax diagram for closing a cursor.
+
+   **Figure 7** close_cursor::=<a id="close_cursor"> </a>
+
+   ![close_cursor](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/cursors-7.jpg)
+
+**Attribute**
+
+Cursor attributes are used to control program procedures or know program status. When a DML statement is executed, the PL/SQL opens a built-in cursor and processes its result. A cursor is a memory segment for maintaining query results. It is opened when a DML statement is executed and closed when the execution is finished. An explicit cursor has the following attributes:
+
+- **%FOUND** attribute: returns **TRUE** if the last fetch returns a row.
+- **%NOTFOUND** attribute: works opposite to the **%FOUND** attribute.
+- **%ISOPEN** attribute: returns **TRUE** if the cursor has been opened.
+- **%ROWCOUNT** attribute: returns the number of records fetched from the cursor.
+
+## Implicit Cursor
+
+Implicit cursors are automatically set by the system for non-query statements such as modify or delete operations, along with their workspace. Implicit cursors are named **SQL**, which is defined by the system.
+
+**Overview**
+
+Implicit cursor operations, such as definition, open, value-grant, and close operations, are automatically performed by the system and do not need users to process. Users can use only attributes related to implicit cursors to complete operations. In workspace of implicit cursors, the data of the latest SQL statement is stored and is not related to explicit cursors defined by users.
+
+Format call:**SQL%**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> **INSERT**, **UPDATE**, **DELETE**, and **SELECT** statements do not need defined cursors.
+
+**Attributes**
+
+An implicit cursor has the following attributes:
+
+- **SQL%FOUND**: Boolean attribute, which returns **TRUE** if the last fetch returns a row.
+- **SQL%NOTFOUND**: Boolean attribute, which works opposite to the **SQL%FOUND** attribute.
+- **SQL%ROWCOUNT**: numeric attribute, which returns the number of records fetched from the cursor.
+- **SQL%ISOPEN**: Boolean attribute, whose value is always **FALSE**. Close implicit cursors immediately after an SQL statement is run.
+
+**Examples**
+
+```sql
+-- Delete all employees in a department from the hr.staffs table. If the department has no employees, delete the department from the hr.sections table.
+CREATE OR REPLACE PROCEDURE proc_cursor3()
+AS
+    DECLARE
+    V_DEPTNO NUMBER(4) := 100;
+    BEGIN
+        DELETE FROM hr.staffs WHERE section_ID = V_DEPTNO;
+        -- Proceed based on cursor status.
+        IF SQL%NOTFOUND THEN
+        DELETE FROM hr.sections WHERE section_ID = V_DEPTNO;
+        END IF;
+    END;
+/
+
+CALL proc_cursor3();
+
+-- Delete the stored procedure and the temporary table.
+DROP PROCEDURE proc_cursor3;
+```
+
+## Cursor Loop
+
+Use of cursors in WHILE and LOOP statements is called a cursor loop. Generally, OPEN, FETCH, and CLOSE statements are involved in this kind of loop. The following describes a loop that simplifies a cursor loop without the need for these operations. This kind of loop is applicable to a static cursor loop, without executing four steps about a static cursor.
+
+**Syntax**
+
+[Figure 8](#FOR_AS_loop) shows the syntax diagram of the **FOR AS** loop.
+
+**Figure 8** FOR_AS_loop::=<a id="FOR_AS_loop"> </a>
+
+![for_as_loop](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/cursors-8.png)
+
+**Precautions**
+
+- The **UPDATE** operation for the queried table is not allowed in the loop statement.
+- The variable loop_name is automatically defined and is valid only in this loop. Its type is the same as that in the select_statement query result. The value of **loop_name** is the query result of **select_statement**.
+- The **%FOUND**, **%NOTFOUND**, and **%ROWCOUNT** attributes access the same internal variable in MogDB. Transactions and the anonymous block do not support multiple cursor accesses at the same time.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-12-retry-management.md b/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-12-retry-management.md
new file mode 100644
index 0000000000000000000000000000000000000000..f45df13aa74998f278abfa5ec533637858f46ea0
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-12-retry-management.md
@@ -0,0 +1,26 @@
+---
+title: Retry Management
+summary: Retry Management
+author: Guo Huan
+date: 2021-03-04
+---
+
+# Retry Management
+
+Retry is a process in which the database executes a SQL statement or stored procedure (including anonymous block) again in the case of execution failure, improving the execution success rate and user experience. The database checks the error code and retry configuration to determine whether to retry.
+
+- If the execution fails, the system rolls back the executed statements and executes the stored procedure again.
+
+  Example:
+
+  ```sql
+  mogdb=# CREATE OR REPLACE PROCEDURE retry_basic ( IN  x INT)
+  AS
+  BEGIN
+        INSERT INTO t1 (a) VALUES (x);
+        INSERT INTO t1 (a) VALUES (x+1);
+  END;
+  /
+
+  mogdb=# CALL retry_basic(1);
+  ```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-13-debugging.md b/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-13-debugging.md
new file mode 100644
index 0000000000000000000000000000000000000000..65081dcdcbda572a26c90880efe654cad715fea7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-13-debugging.md
@@ -0,0 +1,136 @@
+---
+title: Debugging
+summary: Debugging
+author: Guo Huan
+date: 2021-03-04
+---
+
+# Debugging
+
+**Syntax**
+
+RAISE has the following five syntax formats:
+
+**Figure 1** raise_format::=
+
+![raise_format](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/debugging-1.png)
+
+**Figure 2** raise_condition::=
+
+![raise_condition](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/debugging-2.png)
+
+**Figure 3** raise_sqlstate::=
+
+![raise_sqlstate](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/debugging-3.png)
+
+**Figure 4** raise_option::=
+
+![raise_option](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/debugging-4.png)
+
+**Figure 5** raise::=<a id="raise"> </a>
+
+![raise](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/debugging-5.png)
+
+**Parameter description**:
+
+- The level option is used to specify the error level, that is, **DEBUG**, **LOG**, **INFO**, **NOTICE**, **WARNING**, or **EXCEPTION** (default). **EXCEPTION** throws an error that normally terminates the current transaction and the others only generate information at their levels. The log_min_messages and client_min_messages parameters control whether the error messages of specific levels are reported to the client and are written to the server log.
+
+- **format**: specifies the error message text to be reported, a format string. The format string can be appended with an expression for insertion to the message text. In a format string, **%** is replaced by the parameter value attached to format and **%%** is used to print **%**. For example:
+
+  ```
+  --v_job_id replaces % in the string.
+  RAISE NOTICE 'Calling cs_create_job(%)',v_job_id;
+  ```
+
+- **option = expression**: inserts additional information to an error report. The keyword option can be **MESSAGE**, **DETAIL**, **HINT**, or **ERRCODE**, and each expression can be any string.
+
+  - **MESSAGE**: specifies the error message text. This option cannot be used in a **RAISE** statement that contains a format character string in front of **USING**.
+  - **DETAIL**: specifies detailed information of an error.
+  - **HINT**: prints hint information.
+  - **ERRCODE**: designates an error code (SQLSTATE) to a report. A condition name or a five-character SQLSTATE error code can be used.
+
+- **condition_name**: specifies the condition name corresponding to the error code.
+
+- **sqlstate**: specifies the error code.
+
+If neither a condition name nor an **SQLSTATE** is designated in a **RAISE EXCEPTION** command, the **RAISE EXCEPTION (P0001)** is used by default. If no message text is designated, the condition name or SQLSTATE is used as the message text by default.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> If the **SQLSTATE** designates an error code, the error code is not limited to a defined error code. It can be any error code containing five digits or ASCII uppercase rather than **00000**. Do not use an error code ended with three zeros because this kind of error codes are type codes and can be captured by the whole category.
+>
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> The syntax described in [Figure 5](#raise) does not append any parameter. This form is used only for the **EXCEPTION** statement in a **BEGIN** block so that the error can be re-processed.
+
+**Example**
+
+Display error and hint information when a transaction terminates:
+
+```sql
+CREATE OR REPLACE PROCEDURE proc_raise1(user_id in integer)
+AS
+BEGIN
+RAISE EXCEPTION 'Noexistence ID --> %',user_id USING HINT = 'Please check your user ID';
+END;
+/
+
+call proc_raise1(300011);
+
+-- Execution result:
+ERROR:  Noexistence ID --> 300011
+HINT:  Please check your user ID
+```
+
+Two methods are available for setting **SQLSTATE**:
+
+```sql
+CREATE OR REPLACE PROCEDURE proc_raise2(user_id in integer)
+AS
+BEGIN
+RAISE 'Duplicate user ID: %',user_id USING ERRCODE = 'unique_violation';
+END;
+/
+
+\set VERBOSITY verbose
+call proc_raise2(300011);
+
+-- Execution result:
+ERROR:  Duplicate user ID: 300011
+SQLSTATE: 23505
+LOCATION:  exec_stmt_raise, pl_exec.cpp:3482
+```
+
+If the main parameter is a condition name or **SQLSTATE**, the following applies:
+
+RAISE division_by_zero;
+
+RAISE SQLSTATE '22012';
+
+For example:
+
+```sql
+CREATE OR REPLACE PROCEDURE division(div in integer, dividend in integer)
+AS
+DECLARE
+res int;
+    BEGIN
+    IF dividend=0 THEN
+        RAISE division_by_zero;
+        RETURN;
+    ELSE
+        res := div/dividend;
+        RAISE INFO 'division result: %', res;
+        RETURN;
+    END IF;
+    END;
+/
+call division(3,0);
+
+-- Execution result:
+ERROR:  division_by_zero
+```
+
+Alternatively:
+
+```
+RAISE unique_violation USING MESSAGE = 'Duplicate user ID: ' || user_id;
+```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-2-data-types.md b/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-2-data-types.md
new file mode 100644
index 0000000000000000000000000000000000000000..e43bc6ea5ee4c8e9239cdbb57171b4d25418ae1d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-2-data-types.md
@@ -0,0 +1,10 @@
+---
+title: Data Types
+summary: Data Types
+author: Guo Huan
+date: 2021-03-04
+---
+
+# Data Types
+
+A data type refers to a value set and an operation set defined on the value set. The MogDB database consists of tables, each of which is defined by its own columns. Each column corresponds to a data type. The MogDB uses corresponding functions to perform operations on data based on data types. For example, the MogDB can perform addition, subtraction, multiplication, and division operations on data of numeric values.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-3-data-type-conversion.md b/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-3-data-type-conversion.md
new file mode 100644
index 0000000000000000000000000000000000000000..f37d0f9bf0c1e8eb4d4ed5d76990ed1cb36dcc21
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-3-data-type-conversion.md
@@ -0,0 +1,41 @@
+---
+title: Data Type Conversion
+summary: Data Type Conversion
+author: Guo Huan
+date: 2021-03-04
+---
+
+# Data Type Conversion
+
+Certain data types in the database support implicit data type conversions, such as assignments and parameters called by functions. For other data types, you can use the type conversion functions provided by MogDB, such as the **CAST** function, to forcibly convert them.
+
+MogDB lists common implicit data type conversions in [Table 1](#Implicit data type conversions).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> The valid value range of **DATE** supported by MogDB is from 4713 B.C. to 294276 A.D.
+
+**Table 1** Implicit data type conversions<a id="Implicit data type conversions"> </a>
+
+| Raw Data Type | Target Data Type | **Remarks**                                  |
+| :------------ | :--------------- | :------------------------------------------- |
+| CHAR          | VARCHAR2         | -                                            |
+| CHAR          | NUMBER           | Raw data must consist of digits.             |
+| CHAR          | DATE             | Raw data cannot exceed the valid date range. |
+| CHAR          | RAW              | -                                            |
+| CHAR          | CLOB             | -                                            |
+| VARCHAR2      | CHAR             | -                                            |
+| VARCHAR2      | NUMBER           | Raw data must consist of digits.             |
+| VARCHAR2      | DATE             | Raw data cannot exceed the valid date range. |
+| VARCHAR2      | CLOB             | -                                            |
+| NUMBER        | CHAR             | -                                            |
+| NUMBER        | VARCHAR2         | -                                            |
+| DATE          | CHAR             | -                                            |
+| DATE          | VARCHAR2         | -                                            |
+| RAW           | CHAR             | -                                            |
+| RAW           | VARCHAR2         | -                                            |
+| CLOB          | CHAR             | -                                            |
+| CLOB          | VARCHAR2         | -                                            |
+| CLOB          | NUMBER           | Raw data must consist of digits.             |
+| INT4          | CHAR             | -                                            |
+| INT4          | BOOLEAN          | -                                            |
+| BOOLEAN       | INT4             | -                                            |
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-4-arrays-and-records.md b/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-4-arrays-and-records.md
new file mode 100644
index 0000000000000000000000000000000000000000..1b8266af0426574424b442cd620376ab5e090e14
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-4-arrays-and-records.md
@@ -0,0 +1,156 @@
+---
+title: Arrays and Records
+summary: Arrays and Records
+author: Guo Huan
+date: 2021-03-04
+---
+
+# Arrays and Records
+
+## Arrays
+
+**Use of Array Types**
+
+Before the use of arrays, an array type needs to be defined:
+
+Define an array type immediately after the **AS** keyword in a stored procedure. The method is as follows:
+
+```
+TYPE array_type IS VARRAY(size) OF data_type;
+```
+
+In the preceding information:
+
+- **array_type**: indicates the name of the array type to be defined.
+- **VARRAY**: indicates the array type to be defined.
+- **size**: indicates the maximum number of members in the array type to be defined. The value is a positive integer.
+- **data_type**: indicates the types of members in the array type to be created.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - In MogDB, an array automatically increases. If an access violation occurs, a null value is returned, and no error message is reported.
+> - The scope of an array type defined in a stored procedure takes effect only in this storage process.
+> - It is recommended that you use one of the preceding methods to define an array type. If both methods are used to define the same array type, MogDB prefers the array type defined in a stored procedure to declare array variables.
+> - **data_type** can also be a **record** type defined in a stored procedure (anonymous blocks are not supported), but cannot be an array or collection type defined in a stored procedure.
+
+MogDB supports the access of contents in an array by using parentheses, and the **extend**, **count**, **first**, and **last** functions.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> If the stored procedure contains the DML statement (SELECT, UPDATE, INSERT, or DELETE), DML statements can access array elements only using brackets. In this way, it may be separated from the function expression area.
+
+## record
+
+**record Variables**
+
+Perform the following operations to create a record variable:
+
+Define a record type and use this type to declare a variable.
+
+**Syntax**
+
+For the syntax of the record type, see [Figure 1](#Syntax of the record type).
+
+**Figure 1** Syntax of the record type<a id="Syntax of the record type"> </a>
+
+![syntax-of-the-record-type](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/arrays-and-records-1.png)
+
+The above syntax diagram is explained as follows:
+
+- **record_type**: record name
+- **field**: record columns
+- **datatype**: record data type
+- **expression**: expression for setting a default value
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> In MogDB:
+>
+> - When assigning values to record variables, you can:
+>   - Declare a record type and define member variables of this type when you declare a function or stored procedure.
+>   - Assign the value of a record variable to another record variable.
+>   - Use **SELECT INTO** or **FETCH** to assign values to a record type.
+>   - Assign the **NULL** value to a record variable.
+> - The **INSERT** and **UPDATE** statements cannot use a record variable to insert or update data.
+> - Just like a variable, a record column of the compound type does not have a default value in the declaration.
+> - **date_type** can also be the **record** type, array type, and collection type defined in the stored procedure (anonymous blocks are not supported).
+
+**Example**
+
+```sql
+The table used in the following example is defined as follows:
+mogdb=# \d emp_rec
+                Table "public.emp_rec"
+  Column  |              Type              | Modifiers
+----------+--------------------------------+-----------
+ empno    | numeric(4,0)                   | not null
+ ename    | character varying(10)          |
+ job      | character varying(9)           |
+ mgr      | numeric(4,0)                   |
+ hiredate | timestamp(0) without time zone |
+ sal      | numeric(7,2)                   |
+ comm     | numeric(7,2)                   |
+ deptno   | numeric(2,0)                   |
+
+-- Perform array operations in the function.
+mogdb=# CREATE OR REPLACE FUNCTION regress_record(p_w VARCHAR2)
+RETURNS
+VARCHAR2  AS $$
+DECLARE
+
+   -- Declare a record type.
+   type rec_type is record (name  varchar2(100), epno int);
+   employer rec_type;
+
+   -- Use %type to declare the record type.
+   type rec_type1 is record (name  emp_rec.ename%type, epno int not null :=10);
+   employer1 rec_type1;
+
+   -- Declare a record type with a default value.
+   type rec_type2 is record (
+         name varchar2 not null := 'SCOTT',
+         epno int not null :=10);
+    employer2 rec_type2;
+    CURSOR C1 IS  select ename,empno from emp_rec order by 1 limit 1;
+
+BEGIN
+      -- Assign a value to a member record variable.
+     employer.name := 'WARD';
+     employer.epno = 18;
+     raise info 'employer name: % , epno:%', employer.name, employer.epno;
+
+      -- Assign the value of a record variable to another variable.
+     employer1 := employer;
+     raise info 'employer1 name: % , epno: %',employer1.name, employer1.epno;
+
+      -- Assign the NULL value to a record variable.
+     employer1 := NULL;
+     raise info 'employer1 name: % , epno: %',employer1.name, employer1.epno;
+
+      -- Obtain the default value of a record variable.
+     raise info 'employer2 name: % ,epno: %', employer2.name, employer2.epno;
+
+      -- Use a record variable in the FOR loop.
+      for employer in select ename,empno from emp_rec order by 1  limit 1
+          loop
+               raise info 'employer name: % , epno: %', employer.name, employer.epno;
+          end loop;
+
+      -- Use a record variable in the SELECT INTO statement.
+      select ename,empno  into employer2 from emp_rec order by 1 limit 1;
+      raise info 'employer name: % , epno: %', employer2.name, employer2.epno;
+
+      -- Use a record variable in a cursor.
+      OPEN C1;
+      FETCH C1 INTO employer2;
+      raise info 'employer name: % , epno: %', employer2.name, employer2.epno;
+      CLOSE C1;
+      RETURN employer.name;
+END;
+$$
+LANGUAGE plpgsql;
+
+-- Invoke the function.
+mogdb=# CALL regress_record('abc');
+
+-- Delete the function.
+mogdb=# DROP FUNCTION regress_record;
+```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-5-declare-syntax.md b/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-5-declare-syntax.md
new file mode 100644
index 0000000000000000000000000000000000000000..0ae3fb792494249ae60c66515e851e1bb0362118
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-5-declare-syntax.md
@@ -0,0 +1,82 @@
+---
+title: DECLARE Syntax
+summary: DECLARE Syntax
+author: Guo Huan
+date: 2021-03-04
+---
+
+# DECLARE Syntax
+
+## Basic Structure
+
+**Structure**
+
+A PL/SQL block can contain a sub-block which can be placed in any section. The following describes the architecture of a PL/SQL block:
+
+- **DECLARE**: declares variables, types, cursors, and regional stored procedures and functions used in the PL/SQL block.
+
+  ```sql
+  DECLARE
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  > This part is optional if no variable needs to be declared.
+  >
+  > - An anonymous block may omit the **DECLARE** keyword if no variable needs to be declared.
+  > - For a stored procedure, **AS** is used, which is equivalent to **DECLARE**. The **AS** keyword must be reserved even if there is no variable declaration part.
+
+- **EXECUTION**: specifies procedure and SQL statements. It is the main part of a program. Mandatory.
+
+  ```sql
+  BEGIN
+  ```
+
+- Exception part: processes errors. Optional.
+
+  ```sql
+  EXCEPTION
+  ```
+
+- End
+
+  ```
+  END;
+  /
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+  > You are not allowed to use consecutive tabs in the PL/SQL block because they may result in an exception when the **gsql** tool is executed with the **-r** parameter specified.
+
+**Category**
+
+PL/SQL blocks are classified into the following types:
+
+- Anonymous block: a dynamic block that can be executed only for once. For details about the syntax, see [Figure 1](#anonymous_block::=).
+- Subprogram: a stored procedure, function, operator, or packages stored in a database. A subprogram created in a database can be called by other programs.
+
+## Anonymous Blocks
+
+An anonymous block applies to a script infrequently executed or a one-off activity. An anonymous block is executed in a session and is not stored.
+
+**Syntax**
+
+[Figure 1](#anonymous_block::=) shows the syntax diagrams for an anonymous block.
+
+**Figure 1** anonymous_block::=<a id="anonymous_block::="> </a>
+
+![anonymous_block](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/declare-syntax-1.png)
+
+Details about the syntax diagram are as follows:
+
+- The execute part of an anonymous block starts with a **BEGIN** statement, has a break with an **END** statement, and ends with a semicolon (;). Type a slash (/) and press **Enter** to execute the statement.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+  > The terminator "/" must be written in an independent row.
+
+- The declaration section includes the variable definition, type, and cursor definition.
+
+- A simplest anonymous block does not execute any commands. At least one statement, even a **NULL** statement, must be presented in any implementation blocks.
+
+## Subprogram
+
+A subprogram stores stored procedures, functions, operators, and advanced packages. A subprogram created in a database can be called by other programs.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-6-basic-statements.md b/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-6-basic-statements.md
new file mode 100644
index 0000000000000000000000000000000000000000..8441f154af2b468ef00776cdabde183c2c503b84
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-6-basic-statements.md
@@ -0,0 +1,169 @@
+---
+title: Basic Statements
+summary: Basic Statements
+author: Guo Huan
+date: 2021-03-04
+---
+
+# Basic Statements
+
+During PL/SQL programming, you may define some variables, assign values to variables, and call other stored procedures. This chapter describes basic PL/SQL statements, including variable definition statements, value assignment statements, call statements, and return statements.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> You are advised not to call the SQL statements containing passwords in the stored procedures because authorized users may view the stored procedure file in the database and password information is leaked. If a stored procedure contains other sensitive information, permission to access this procedure must be configured, preventing information leakage.
+
+## Define Variable
+
+This section describes the declaration of variables in the PL/SQL and the scope of this variable in codes.
+
+**Variable Declaration**
+
+For details about the variable declaration syntax, see [Figure 1](#declare_variable::=).
+
+**Figure 1** declare_variable::=<a id="declare_variable::="> </a>
+
+![declare_variable](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/basic-statements-1.png)
+
+The above syntax diagram is explained as follows:
+
+- **variable_name** indicates the name of a variable.
+- **type** indicates the type of a variable.
+- **value** indicates the initial value of the variable. (If the initial value is not given, NULL is taken as the initial value.) **value** can also be an expression.
+
+**Examples**
+
+```sql
+mogdb=# DECLARE
+    emp_id  INTEGER := 7788; -- Define a variable and assign a value to it.
+BEGIN
+    emp_id := 5*7784; -- Assign a value to the variable.
+END;
+/
+```
+
+In addition to the declaration of basic variable types, **%TYPE** and **%ROWTYPE** can be used to declare variables related to table columns or table structures.
+
+**%TYPE Attribute**
+
+**%TYPE** declares a variable to be of the same data type as a previously declared variable (for example, a column in a table). For example, if you want to define a *my_name* variable whose data type is the same as the data type of the **firstname** column in the **employee** table, you can define the variable as follows:
+
+```
+my_name employee.firstname%TYPE
+```
+
+In this way, you can declare *my_name* without the need of knowing the data type of **firstname** in **employee**, and the data type of **my_name** can be automatically updated when the data type of **firstname** changes.
+
+**%ROWTYPE Attribute**
+
+**%ROWTYPE** declares data types of a set of data. It stores a row of table data or results fetched from a cursor. For example, if you want to define a set of data with the same column names and column data types as the **employee** table, you can define the data as follows:
+
+```
+my_employee employee%ROWTYPE
+```
+
+**Scope of a Variable**
+
+The scope of a variable indicates the accessibility and availability of the variable in code block. In other words, a variable takes effect only within its scope.
+
+- To define a function scope, a variable must declare and create a **BEGIN-END** block in the declaration section. The necessity of such declaration is also determined by block structure, which requires that a variable has different scopes and lifetime during a process.
+- A variable can be defined multiple times in different scopes, and inner definition can cover outer one.
+- A variable defined in an outer block can also be used in a nested block. However, the outer block cannot access variables in the nested block.
+
+## Assignment Statements
+
+**Syntax**
+
+[Figure 2](#assignment_value) shows the syntax diagram for assigning a value to a variable.
+
+**Figure 2** assignment_value::=<a id="assignment_value"> </a>
+
+![assignment_value](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/basic-statements-2.png)
+
+The above syntax diagram is explained as follows:
+
+- **variable_name** indicates the name of a variable.
+- **value** can be a value or an expression. The type of **value** must be compatible with the type of **variable_name**.
+
+**Example**
+
+```sql
+mogdb=# DECLARE
+    emp_id  INTEGER := 7788; --Assignment
+BEGIN
+    emp_id := 5; --Assignment
+    emp_id := 5*7784;
+END;
+/
+```
+
+**Nested Value Assignment**
+
+[Figure 3](#nested_assignment_value) shows the syntax diagram for assigning a nested value to a variable.
+
+**Figure 3** nested_assignment_value::=<a id="nested_assignment_value"> </a>
+
+![nested_assignment_value](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/basic-statements-3.png)
+
+The syntax in Figure 3 is described as follows:
+
+- **variable_name**: variable name
+- **col_name**: column name
+- **subscript**: subscript, which is used for an array variable. The value can be a value or an expression and must be of the int type.
+- **value**: value or expression. The type of **value** must be compatible with the type of **variable_name**.
+
+## Examples
+
+```sql
+mogdb=# CREATE TYPE o1 as (a int, b int);
+mogdb=# DECLARE
+    TYPE r1 is VARRAY(10) of o1;
+    emp_id  r1;
+BEGIN
+    emp_id(1).a := 5;-- Assign a value.
+    emp_id(1).b := 5*7784;
+END;
+/
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - In INTO mode, values can be assigned only to the columns at the first layer. Two-dimensional or above arrays are not supported.
+> - When a nested column value is referenced, if an array subscript exists, only one parenthesis can exist in the first three layers of columns. You are advised to use square brackets to reference the subscript.
+
+## Call Statement
+
+**Syntax**
+
+[Figure 4](#call_clause) shows the syntax diagram for calling a clause.
+
+**Figure 4** call_clause::=<a id="call_clause"> </a>
+
+![call_clause](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/basic-statements-4.png)
+
+The above syntax diagram is explained as follows:
+
+- **procedure_name** specifies the name of a stored procedure.
+- **parameter** specifies the parameters for the stored procedure. You can set no parameter or multiple parameters.
+
+**Example**<a id="Example"> </a>
+
+```sql
+-- Create the stored procedure proc_staffs:
+mogdb=# CREATE OR REPLACE PROCEDURE proc_staffs
+(
+section     NUMBER(6),
+salary_sum out NUMBER(8,2),
+staffs_count out INTEGER
+)
+IS
+BEGIN
+SELECT sum(salary), count(*) INTO salary_sum, staffs_count FROM hr.staffs where section_id = section;
+END;
+/
+
+-- Invoke a stored procedure proc_return:
+mogdb=# CALL proc_staffs(2,8,6);
+
+-- Delete a stored procedure:
+mogdb=# DROP PROCEDURE proc_staffs;
+```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-7-dynamic-statements.md b/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-7-dynamic-statements.md
new file mode 100644
index 0000000000000000000000000000000000000000..7d982b4672c660c46cd401edf7ac95478069d3d4
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-7-dynamic-statements.md
@@ -0,0 +1,166 @@
+---
+title: Dynamic Statements
+summary: Dynamic Statements
+author: Guo Huan
+date: 2021-03-04
+---
+
+# Dynamic Statements
+
+## Executing Dynamic Query Statements
+
+You can perform dynamic queries MogDB provides two modes: EXECUTE IMMEDIATE and OPEN FOR. **EXECUTE IMMEDIATE** dynamically executes **SELECT** statements and **OPEN FOR** combines use of cursors. If you need to store query results in a data set, use **OPEN FOR**.
+
+**EXECUTE IMMEDIATE**
+
+[Figure 1](#EXECUTE IMMEDIATE) shows the syntax diagram.
+
+**Figure 1** EXECUTE IMMEDIATE dynamic_select_clause::=<a id="EXECUTE IMMEDIATE"> </a>
+
+![execute-immediate-dynamic_select_clause](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/dynamic-statements-1.png)
+
+[Figure 2](#using_clause) shows the syntax diagram for **using_clause**.
+
+**Figure 2** using_clause::=<a id="using_clause"> </a>
+
+![using_clause](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/dynamic-statements-2.png)
+
+The above syntax diagram is explained as follows:
+
+- **define_variable**: specifies variables to store single-line query results.
+
+- **USING IN bind_argument**: specifies where the variable passed to the dynamic SQL value is stored, that is, in the dynamic placeholder of **dynamic_select_string**.
+
+- **USING OUT bind_argument**: specifies where the dynamic SQL returns the value of the variable.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+  >
+  > - In query statements, **INTO** and **OUT** cannot coexist.
+  > - A placeholder name starts with a colon (:) followed by digits, characters, or strings, corresponding to **bind_argument** in the **USING** clause.
+  > - **bind_argument** can only be a value, variable, or expression. It cannot be a database object such as a table name, column name, and data type. That is, **bind_argument** cannot be used to transfer schema objects for dynamic SQL statements. If a stored procedure needs to transfer database objects through **bind_argument** to construct dynamic SQL statements (generally, DDL statements), you are advised to use double vertical bars (||) to concatenate **dynamic_select_clause** with a database object.
+  > - A dynamic PL/SQL block allows duplicate placeholders. That is, a placeholder can correspond to only one **bind_argument** in the **USING** clause.
+
+**OPEN FOR**
+
+Dynamic query statements can be executed by using **OPEN FOR** to open dynamic cursors.
+
+[Figure 3](#open_for) shows the syntax diagram.
+
+**Figure 3** open_for::=<a id="open_for"> </a>
+
+![open_for](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/dynamic-statements-3.png)
+
+Parameter description:
+
+- **cursor_name**: specifies the name of the cursor to be opened.
+- **dynamic_string**: specifies the dynamic query statement.
+- **USING value**: applies when a placeholder exists in dynamic_string.
+
+For use of cursors, see [Cursors](1-11-cursors).
+
+## Executing Dynamic Non-query Statements
+
+**Syntax**
+
+[Figure 4](#noselect) shows the syntax diagram.
+
+**Figure 4** noselect::=<a id="noselect"> </a>
+
+![noselect](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/dynamic-statements-4.png)
+
+[Figure 5](#using_clause::=) shows the syntax diagram for **using_clause**.
+
+**Figure 5** using_clause::=<a id="using_clause::="> </a>
+
+![using_clause-0](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/dynamic-statements-5.png)
+
+The above syntax diagram is explained as follows:
+
+**USING IN bind_argument** is used to specify the variable whose value is passed to the dynamic SQL statement. The variable is used when a placeholder exists in **dynamic_noselect_string**. That is, a placeholder is replaced by the corresponding **bind_argument** when a dynamic SQL statement is executed. Note that **bind_argument** can only be a value, variable, or expression, and cannot be a database object such as a table name, column name, and data type. If a stored procedure needs to transfer database objects through **bind_argument** to construct dynamic SQL statements (generally, DDL statements), you are advised to use double vertical bars (||) to concatenate **dynamic_select_clause** with a database object. In addition, a dynamic PL/SQL block allows duplicate placeholders. That is, a placeholder can correspond to only one **bind_argument**.
+
+**Example**
+
+```sql
+-- Create a table:
+mogdb=# CREATE TABLE sections_t1
+(
+   section       NUMBER(4) ,
+   section_name  VARCHAR2(30),
+   manager_id    NUMBER(6),
+   place_id      NUMBER(4)
+);
+
+-- Declare a variable:
+mogdb=# DECLARE
+   section       NUMBER(4) := 280;
+   section_name  VARCHAR2(30) := 'Info support';
+   manager_id    NUMBER(6) := 103;
+   place_id      NUMBER(4) := 1400;
+   new_colname   VARCHAR2(10) := 'sec_name';
+BEGIN
+-- Execute the query:
+    EXECUTE IMMEDIATE 'insert into sections_t1 values(:1, :2, :3, :4)'
+       USING section, section_name, manager_id,place_id;
+-- Execute the query (duplicate placeholders):
+    EXECUTE IMMEDIATE 'insert into sections_t1 values(:1, :2, :3, :1)'
+       USING section, section_name, manager_id;
+-- Run the ALTER statement. (You are advised to use double vertical bars (||) to concatenate the dynamic DDL statement with a database object.)
+    EXECUTE IMMEDIATE 'alter table sections_t1 rename section_name to ' || new_colname;
+END;
+/
+
+-- Query data:
+mogdb=# SELECT * FROM sections_t1;
+
+--Delete the table.
+mogdb=# DROP TABLE sections_t1;
+```
+
+## Dynamically Calling Stored Procedures
+
+This section describes how to dynamically call store procedures. You must use anonymous statement blocks to package stored procedures or statement blocks and append **IN** and **OUT** behind the **EXECUTE IMMEDIATE…USING** statement to input and output parameters.
+
+**Syntax**
+
+[Figure 6](#call_procedure) shows the syntax diagram.
+
+**Figure 6** call_procedure::=<a id="call_procedure"> </a>
+
+![call_procedure](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/dynamic-statements-6.png)
+
+[Figure 7](#Figure 2) shows the syntax diagram for **using_clause**.
+
+**Figure 7** using_clause::=<a id="Figure 2"> </a>
+
+![using_clause-1](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/dynamic-statements-7.png)
+
+The above syntax diagram is explained as follows:
+
+- **CALL procedure_name**: calls the stored procedure.
+- **[:placeholder1,:placeholder2,…]**: specifies the placeholder list of the stored procedure parameters. The numbers of the placeholders and parameters are the same.
+- **USING [IN|OUT|IN OUT]bind_argument**: specifies where the variable passed to the stored procedure parameter value is stored. The modifiers in front of **bind_argument** and of the corresponding parameter are the same.
+
+## Dynamically Calling Anonymous Blocks
+
+This section describes how to execute anonymous blocks in dynamic statements. Append **IN** and **OUT** behind the **EXECUTE IMMEDIATE…USING** statement to input and output parameters.
+
+**Syntax**
+
+[Figure 8](#call_anonymous_block) shows the syntax diagram.
+
+**Figure 8** call_anonymous_block::=<a id="call_anonymous_block"> </a>
+
+![call_anonymous_block](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/dynamic-statements-8.png)
+
+[Figure 9](#Figure 2using_clause) shows the syntax diagram for **using_clause**.
+
+**Figure 9** using_clause::=<a id="Figure 2using_clause"> </a>
+
+![using_clause-2](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/dynamic-statements-9.png)
+
+The above syntax diagram is explained as follows:
+
+- The execute part of an anonymous block starts with a **BEGIN** statement, has a break with an **END** statement, and ends with a semicolon (;).
+- **USING [IN|OUT|IN OUT]bind_argument**: specifies where the variable passed to the stored procedure parameter value is stored. The modifiers in front of **bind_argument** and of the corresponding parameter are the same.
+- The input and output parameters in the middle of an anonymous block are designated by placeholders. The numbers of the placeholders and parameters are the same. The sequences of the parameters corresponding to the placeholders and the USING parameters are the same.
+- Currently in MogDB, when dynamic statements call anonymous blocks, placeholders cannot be used to pass input and output parameters in an **EXCEPTION** statement.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-8-control-statements.md b/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-8-control-statements.md
new file mode 100644
index 0000000000000000000000000000000000000000..32e01601c65c22490ff452de4f1e99c64e2dd087
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-8-control-statements.md
@@ -0,0 +1,647 @@
+---
+title: Control Statements
+summary: Control Statements
+author: Guo Huan
+date: 2021-03-04
+---
+
+# Control Statements
+
+## RETURN Statements
+
+In MogDB, data can be returned in either of the following ways:**RETURN**, **RETURN NEXT**, or **RETURN QUERY**. **RETURN NEXT** and **RETURN QUERY** are used only for functions and cannot be used for stored procedures.
+
+### RETURN
+
+**Syntax**
+
+[Figure 1](#return_clause::=) shows the syntax diagram for a return statement.
+
+**Figure 1** return_clause::=<a id="return_clause::="> </a>
+
+![return_clause](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/control-statements-1.jpg)
+
+The above syntax diagram is explained as follows:
+
+This statement returns control from a stored procedure or function to a caller.
+
+**Examples**
+
+See [Example](1-6-basic-statements#call-statement) for call statement examples.
+
+### RETURN NEXT and RETURN QUERY
+
+**Syntax**
+
+When creating a function, specify **SETOF datatype** for the return values.
+
+return_next_clause::=
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/control-statements-2.png)
+
+return_query_clause::=
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/control-statements-3.png)
+
+The above syntax diagram is explained as follows:
+
+If a function needs to return a result set, use **RETURN NEXT** or **RETURN QUERY** to add results to the result set, and then continue to execute the next statement of the function. As the **RETURN NEXT** or **RETURN QUERY** statement is executed repeatedly, more and more results will be added to the result set. After the function is executed, all results are returned.
+
+**RETURN NEXT** can be used for scalar and compound data types.
+
+**RETURN QUERY** has a variant **RETURN QUERY EXECUTE**. You can add dynamic queries and add parameters to the queries by **USING**.
+
+**Examples**
+
+```sql
+mogdb=# CREATE TABLE t1(a int);
+mogdb=# INSERT INTO t1 VALUES(1),(10);
+
+--RETURN NEXT
+mogdb=# CREATE OR REPLACE FUNCTION fun_for_return_next() RETURNS SETOF t1 AS $$
+DECLARE
+   r t1%ROWTYPE;
+BEGIN
+   FOR r IN select * from t1
+   LOOP
+      RETURN NEXT r;
+   END LOOP;
+   RETURN;
+END;
+$$ LANGUAGE PLPGSQL;
+mogdb=# call fun_for_return_next();
+ a
+---
+ 1
+ 10
+(2 rows)
+
+-- RETURN QUERY
+mogdb=# CREATE OR REPLACE FUNCTION fun_for_return_query() RETURNS SETOF t1 AS $$
+DECLARE
+   r t1%ROWTYPE;
+BEGIN
+   RETURN QUERY select * from t1;
+END;
+$$
+language plpgsql;
+mogdb=# call fun_for_return_query();
+ a
+---
+ 1
+ 10
+(2 rows)
+```
+
+## Conditional Statements
+
+Conditional statements are used to decide whether given conditions are met. Operations are executed based on the decisions made.
+
+MogDB supports five usages of **IF**:
+
+- IF_THEN
+
+  **Figure 2** IF_THEN::=
+
+  ![if_then](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/control-statements-4.jpg)
+
+  **IF_THEN** is the simplest form of **IF**. If the condition is true, statements are executed. If it is false, they are skipped.
+
+  Example:
+
+  ```sql
+  mogdb=# IF v_user_id <> 0 THEN
+      UPDATE users SET email = v_email WHERE user_id = v_user_id;
+  END IF;
+  ```
+
+- IF_THEN_ELSE
+
+  **Figure 3** IF_THEN_ELSE::=
+
+  ![if_then_else](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/control-statements-5.jpg)
+
+  **IF-THEN-ELSE** statements add **ELSE** branches and can be executed if the condition is false.
+
+  Example:
+
+  ```sql
+  mogdb=# IF parentid IS NULL OR parentid = ''
+  THEN
+      RETURN;
+  ELSE
+      hp_true_filename(parentid); -- Call the stored procedure.
+  END IF;
+  ```
+
+- IF_THEN_ELSE IF
+
+  **IF** statements can be nested in the following way:
+
+  ```sql
+  mogdb=# IF sex = 'm' THEN
+      pretty_sex := 'man';
+  ELSE
+      IF sex = 'f' THEN
+          pretty_sex := 'woman';
+      END IF;
+  END IF;
+  ```
+
+  Actually, this is a way of an **IF** statement nesting in the **ELSE** part of another **IF** statement. Therefore, an **END IF** statement is required for each nesting **IF** statement and another **END IF** statement is required to end the parent **IF-ELSE** statement. To set multiple options, use the following form:
+
+- IF_THEN_ELSIF_ELSE
+
+  **Figure 4** IF_THEN_ELSIF_ELSE::=
+
+  ![if_then_elsif_else](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/control-statements-6.png)
+
+  Example:
+
+  ```sql
+  IF number_tmp = 0 THEN
+      result := 'zero';
+  ELSIF number_tmp > 0 THEN
+      result := 'positive';
+  ELSIF number_tmp < 0 THEN
+      result := 'negative';
+  ELSE
+      result := 'NULL';
+  END IF;
+  ```
+
+- IF_THEN_ELSEIF_ELSE
+
+  **ELSEIF** is an alias of **ELSIF**.
+
+  Example:
+
+  ```sql
+  CREATE OR REPLACE PROCEDURE proc_control_structure(i in integer)
+  AS
+      BEGIN
+          IF i > 0 THEN
+              raise info 'i:% is greater than 0. ',i;
+          ELSIF i < 0 THEN
+              raise info 'i:% is smaller than 0. ',i;
+          ELSE
+              raise info 'i:% is equal to 0. ',i;
+          END IF;
+          RETURN;
+      END;
+  /
+
+  CALL proc_control_structure(3);
+
+  -- Delete the stored procedure.
+  DROP PROCEDURE proc_control_structure;
+  ```
+
+## Loop Statements
+
+**Simple LOOP Statements**
+
+The syntax diagram is as follows:
+
+**Figure 5** loop::=
+
+![loop](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/control-statements-7.png)
+
+**Example**
+
+```sql
+CREATE OR REPLACE PROCEDURE proc_loop(i in integer, count out integer)
+AS
+    BEGIN
+        count:=0;
+        LOOP
+        IF count > i THEN
+            raise info 'count is %. ', count;
+            EXIT;
+        ELSE
+            count:=count+1;
+        END IF;
+        END LOOP;
+    END;
+/
+
+CALL proc_loop(10,5);
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> The loop must be exploited together with **EXIT**; otherwise, a dead loop occurs.
+
+**WHILE-LOOP Statements**
+
+**Syntax diagram**
+
+**Figure 6** while_loop::=
+
+![while_loop](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/control-statements-8.png)
+
+If the conditional expression is true, a series of statements in the WHILE statement are repeatedly executed and the condition is decided each time the loop body is executed.
+
+**Example**
+
+```sql
+CREATE TABLE integertable(c1 integer) ;
+CREATE OR REPLACE PROCEDURE proc_while_loop(maxval in integer)
+AS
+    DECLARE
+    i int :=1;
+    BEGIN
+        WHILE i < maxval LOOP
+            INSERT INTO integertable VALUES(i);
+            i:=i+1;
+        END LOOP;
+    END;
+/
+
+-- Invoke a function:
+CALL proc_while_loop(10);
+
+-- Delete the stored procedure and table.
+DROP PROCEDURE proc_while_loop;
+DROP TABLE integertable;
+```
+
+**FOR_LOOP (Integer variable) Statement**
+
+**Syntax diagram**
+
+**Figure 7** for_loop::=
+
+![for_loop](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/control-statements-9.png)
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - The variable **name** is automatically defined as the **integer** type and exists only in this loop. The variable name falls between lower_bound and upper_bound.
+> - When the keyword **REVERSE** is used, the lower bound must be greater than or equal to the upper bound; otherwise, the loop body is not executed.
+
+**FOR_LOOP Query Statements**
+
+**Syntax diagram**
+
+**Figure 8** for_loop_query::=
+
+![for_loop_query](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/control-statements-10.png)
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> The variable **target** is automatically defined, its type is the same as that in the **query** result, and it is valid only in this loop. The target value is the query result.
+
+**FORALL Batch Query Statements**
+
+**Syntax diagram**
+
+**Figure 9** forall::=
+
+![forall](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/control-statements-11.png)
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> The variable **index** is automatically defined as the **integer** type and exists only in this loop. The index value falls between low_bound and upper_bound.
+
+**Example**
+
+```sql
+CREATE TABLE hdfs_t1 (
+  title NUMBER(6),
+  did VARCHAR2(20),
+  data_peroid VARCHAR2(25),
+  kind VARCHAR2(25),
+  interval VARCHAR2(20),
+  time DATE,
+  isModified VARCHAR2(10)
+);
+
+INSERT INTO hdfs_t1 VALUES( 8, 'Donald', 'OConnell', 'DOCONNEL', '650.507.9833', to_date('21-06-1999', 'dd-mm-yyyy'), 'SH_CLERK' );
+
+CREATE OR REPLACE PROCEDURE proc_forall()
+AS
+BEGIN
+    FORALL i IN 100..120
+        update hdfs_t1 set title = title + 100*i;
+END;
+/
+
+-- Invoke a function:
+CALL proc_forall();
+
+-Query the invocation result of the stored procedure.
+SELECT * FROM hdfs_t1 WHERE title BETWEEN 100 AND 120;
+
+-- Delete the stored procedure and table.
+DROP PROCEDURE proc_forall;
+DROP TABLE hdfs_t1;
+```
+
+## Branch Statements
+
+**Syntax**
+
+[Figure 10](#case_when) shows the syntax diagram for a branch statement.
+
+**Figure 10** case_when::=<a id="case_when"> </a>
+
+![case_when](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/control-statements-12.png)
+
+[Figure 11](#when_clause) shows the syntax diagram for **when_clause**.
+
+**Figure 11** when_clause::=<a id="when_clause"> </a>
+
+![when_clause](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/control-statements-13.png)
+
+Parameter description:
+
+- **case_expression**: specifies the variable or expression.
+- **when_expression**: specifies the constant or conditional expression.
+- **statement**: specifies the statement to be executed.
+
+**Examples**
+
+```sql
+CREATE OR REPLACE PROCEDURE proc_case_branch(pi_result in integer, pi_return out integer)
+AS
+    BEGIN
+        CASE pi_result
+            WHEN 1 THEN
+                pi_return := 111;
+            WHEN 2 THEN
+                pi_return := 222;
+            WHEN 3 THEN
+                pi_return := 333;
+            WHEN 6 THEN
+                pi_return := 444;
+            WHEN 7 THEN
+                pi_return := 555;
+            WHEN 8 THEN
+                pi_return := 666;
+            WHEN 9 THEN
+                pi_return := 777;
+            WHEN 10 THEN
+                pi_return := 888;
+            ELSE
+                pi_return := 999;
+        END CASE;
+        raise info 'pi_return : %',pi_return ;
+END;
+/
+
+CALL proc_case_branch(3,0);
+
+-- Delete the stored procedure.
+DROP PROCEDURE proc_case_branch;
+```
+
+## NULL Statements
+
+In PL/SQL programs, **NULL** statements are used to indicate "nothing should be done", equal to placeholders. They grant meanings to some statements and improve program readability.
+
+**Syntax**
+
+The following shows example use of **NULL** statements.
+
+```sql
+DECLARE
+    ...
+BEGIN
+    ...
+    IF v_num IS NULL THEN
+        NULL; --No data needs to be processed.
+    END IF;
+END;
+/
+```
+
+## Error Trapping Statements
+
+By default, any error occurring in a PL/SQL function aborts execution of the function, and indeed of the surrounding transaction as well. You can trap errors and restore from them by using a **BEGIN** block with an **EXCEPTION** clause. The syntax is an extension of the normal syntax for a **BEGIN** block:
+
+```sql
+[<<label>>]
+[DECLARE
+    declarations]
+BEGIN
+    statements
+EXCEPTION
+    WHEN condition [OR condition ...] THEN
+        handler_statements
+    [WHEN condition [OR condition ...] THEN
+        handler_statements
+    ...]
+END;
+```
+
+If no error occurs, this form of block simply executes all the statements, and then control passes to the next statement after **END**. But if an error occurs within the statements, further processing of the statements is abandoned, and control passes to the **EXCEPTION** list. The list is searched for the first condition matching the error that occurred. If a match is found, the corresponding **handler_statements** are executed, and then control passes to the next statement after **END**. If no match is found, the error propagates out as though the **EXCEPTION** clause were not there at all:
+
+The error can be caught by an enclosing block with **EXCEPTION**, or if there is none it aborts processing of the function.
+
+The condition names can be any of those shown in SQL standard error codes. The special condition name **OTHERS** matches every error type except **QUERY_CANCELED**.
+
+If a new error occurs within the selected **handler_statements**, it cannot be caught by this **EXCEPTION** clause, but is propagated out. A surrounding **EXCEPTION** clause could catch it.
+
+When an error is caught by an **EXCEPTION** clause, the local variables of the PL/SQL function remain as they were when the error occurred, but all changes to persistent database state within the block are rolled back.
+
+Example:
+
+```sql
+CREATE TABLE mytab(id INT,firstname VARCHAR(20),lastname VARCHAR(20)) ;
+
+INSERT INTO mytab(firstname, lastname) VALUES('Tom', 'Jones');
+
+CREATE FUNCTION fun_exp() RETURNS INT
+AS $$
+DECLARE
+    x INT :=0;
+    y INT;
+BEGIN
+    UPDATE mytab SET firstname = 'Joe' WHERE lastname = 'Jones';
+    x := x + 1;
+    y := x / 0;
+EXCEPTION
+    WHEN division_by_zero THEN
+        RAISE NOTICE 'caught division_by_zero';
+        RETURN x;
+END;$$
+LANGUAGE plpgsql;
+
+call fun_exp();
+NOTICE:  caught division_by_zero
+ fun_exp
+---------
+       1
+(1 row)
+
+select * from mytab;
+ id | firstname | lastname
+----+-----------+----------
+    | Tom       | Jones
+(1 row)
+
+DROP FUNCTION fun_exp();
+DROP TABLE mytab;
+```
+
+When control reaches the assignment to **y**, it will fail with a **division_by_zero** error. This will be caught by the **EXCEPTION** clause. The value returned in the **RETURN** statement will be the incremented value of **x**.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> A block containing an **EXCEPTION** clause is more expensive to enter and exit than a block without one. Therefore, do not use **EXCEPTION** without need.
+> In the following scenario, an exception cannot be caught, and the entire transaction rolls back. The threads of the nodes participating the stored procedure exit abnormally due to node failure and network fault, or the source data is inconsistent with that of the table structure of the target table during the COPY FROM operation.
+
+Example: Exceptions with **UPDATE**/**INSERT**
+
+This example uses exception handling to perform either **UPDATE** or **INSERT**, as appropriate:
+
+```sql
+CREATE TABLE db (a INT, b TEXT);
+
+CREATE FUNCTION merge_db(key INT, data TEXT) RETURNS VOID AS
+$$
+BEGIN
+    LOOP
+
+-- First try to update the key
+        UPDATE db SET b = data WHERE a = key;
+        IF found THEN
+            RETURN;
+        END IF;
+-- Not there, so try to insert the key. If someone else inserts the same key concurrently, we could get a unique-key failure.
+        BEGIN
+            INSERT INTO db(a,b) VALUES (key, data);
+            RETURN;
+        EXCEPTION WHEN unique_violation THEN
+        -- Do nothing, and loop to try the UPDATE again.
+        END;
+     END LOOP;
+END;
+$$
+LANGUAGE plpgsql;
+
+SELECT merge_db(1, 'david');
+SELECT merge_db(1, 'dennis');
+
+--Delete FUNCTION and TABLE:
+DROP FUNCTION merge_db;
+DROP TABLE db;
+```
+
+## GOTO Statements
+
+A **GOTO** statement unconditionally transfers the control from the current statement to a labeled statement. The **GOTO** statement changes the execution logic. Therefore, use this statement only when necessary. Alternatively, you can use the **EXCEPTION** statement to handle issues in special scenarios. To run a **GOTO** statement, the labeled statement must be unique.
+
+**Syntax**
+
+label declaration ::=
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/control-statements-14.png)
+
+goto statement ::=
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/control-statements-15.png)
+
+**Examples**
+
+```sql
+mogdb=# CREATE OR REPLACE PROCEDURE GOTO_test()
+AS
+DECLARE
+    v1  int;
+BEGIN
+    v1  := 0;
+        LOOP
+        EXIT WHEN v1 > 100;
+                v1 := v1 + 2;
+                if v1 > 25 THEN
+                        GOTO pos1;
+                END IF;
+        END LOOP;
+<<pos1>>
+v1 := v1 + 10;
+raise info 'v1 is %. ', v1;
+END;
+/
+
+call GOTO_test();
+```
+
+**Constraints**
+
+Using **GOTO** statements has the following constraints:
+
+- A **GOTO** statement does not allow multiple labeled statements even if the statements are in different blocks.
+
+  ```sql
+  BEGIN
+    GOTO pos1;
+    <<pos1>>
+    SELECT * FROM ...
+    <<pos1>>
+    UPDATE t1 SET ...
+  END;
+  ```
+
+- A **GOTO** statement cannot transfer control to the **IF**, **CASE**, or **LOOP** statement.
+
+  ```sql
+  BEGIN
+     GOTO pos1;
+     IF valid THEN
+       <<pos1>>
+       SELECT * FROM ...
+     END IF;
+   END;
+  ```
+
+- A **GOTO** statement cannot transfer control from one **IF** clause to another, or from one **WHEN** clause in the **CASE** statement to another.
+
+  ```sql
+  BEGIN
+     IF valid THEN
+       GOTO pos1;
+       SELECT * FROM ...
+     ELSE
+       <<pos1>>
+       UPDATE t1 SET ...
+     END IF;
+   END;
+  ```
+
+- A **GOTO** statement cannot transfer control from an outer block to an inner **BEGIN-END** block.
+
+  ```sql
+  BEGIN
+     GOTO pos1;
+     BEGIN
+       <<pos1>>
+       UPDATE t1 SET ...
+     END;
+   END;
+  ```
+
+- A **GOTO** statement cannot transfer control from an exception handler to the current **BEGIN-END** block. However, a **GOTO** statement can transfer control to the upper-layer **BEGIN-END** block.
+
+  ```sql
+  BEGIN
+     <<pos1>>
+     UPDATE t1 SET ...
+     EXCEPTION
+       WHEN condition THEN
+          GOTO pos1;
+   END;
+  ```
+
+- To branch to a position that does not have an executable statement, add the **NULL** statement.
+
+  ```sql
+  DECLARE
+     done  BOOLEAN;
+  BEGIN
+     FOR i IN 1..50 LOOP
+        IF done THEN
+           GOTO end_loop;
+        END IF;
+        <<end_loop>>  -- not allowed unless an executable statement follows
+        NULL; -- add NULL statement to avoid error
+     END LOOP;  -- raises an error without the previous NULL
+  END;
+  /
+  ```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-9-transaction-management.md b/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-9-transaction-management.md
new file mode 100644
index 0000000000000000000000000000000000000000..88b4885cfd54bc23eae36f6d1c41c7af40cd4067
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/plpgsql/1-9-transaction-management.md
@@ -0,0 +1,426 @@
+---
+title: Transaction Management
+summary: Transaction Management
+author: Guo Huan
+date: 2021-03-04
+---
+
+# Transaction Management
+
+Calling a stored procedure automatically starts a transaction. When the calling is complete, the transaction is automatically submitted, or rolled back upon an exception. In addition to automatic transaction control, you can also use COMMIT/ROLLBACK to control transactions in stored procedures. Running the COMMIT/ROLLBACK commands in a stored procedure will commit or roll back the current transaction and automatically starts a new transaction. All subsequent operations will be performed in the new transaction.
+
+A savepoint is a special mark inside a transaction. It allows all commands that are executed after it was established to be rolled back, restoring the transaction state to what it was at the time of the savepoint. In a stored procedure, you can use savepoints to manage transactions. Currently, you can create, roll back, and release savepoints. If a savepoint for rollback is used in a stored procedure, only the modification of the current transaction is rolled back. The execution process of the stored procedure is not changed, and the values of local variables in the stored procedure are not rolled back.
+
+## Syntax
+
+```sql
+# Define a savepoint.
+    SAVEPOINT savepoint_name;
+# Roll back a savepoint.
+    ROLLBACK TO [SAVEPOINT] savepoint_name;
+# Release a savepoint.
+    RELEASE [SAVEPOINT] savepoint_name;
+```
+
+## **Usage Scenarios**
+
+The applicable contexts are as follows:
+
+- COMMIT/ROLLBACK/SAVEPOINT can be used in stored procedures in PL/SQL.
+- COMMIT, ROLLBACK, and SAVEPOINT can be used in stored procedures that contain EXCEPTION.
+- COMMIT, ROLLBACK, and SAVEPOINT can be used in EXCEPTION statements of stored procedures.
+- A stored procedure that contains COMMIT, ROLLBACK, or SAVEPOINT (which means the stored procedure is controlled by BEGIN, START, or END) can be called in a transaction block.
+- A stored procedure that contains savepoints can be invoked in a subtransaction. That is, an externally defined savepoint is used in the stored procedure to roll back the transaction to the savepoint defined outside the stored procedure.
+- A stored procedure is visible to a savepoint defined in the stored procedure. That is, the modification of the transaction can be rolled back to the savepoint defined in the stored procedure.
+- COMMIT, ROLLBACK, and SAVEPOINT, as well as IF, FOR, CURSOR LOOP, and WHILE, can be called in most contexts and statements in PLSQL.
+
+The following content can be submitted or rolled back:
+
+- DDL statements after COMMIT/ROLLBACK can be submitted or rolled back.
+- DML statements after COMMIT/ROLLBACK can be submitted.
+- GUC parameters in stored procedures can be submitted or rolled back.
+
+## **Usage Restrictions**
+
+COMMIT and ROLLBACK cannot be used in the following contexts:
+
+- COMMIT, ROLLBACK, and SAVEPOINT cannot be called in stored procedures other than PLSQL, such as PLJava and PLPython.
+- COMMIT, ROLLBACK, SAVEPOINT and stored procedures that contain COMMIT, ROLLBACK, or SAVEPOINT cannot be called in functions.
+- After SAVEPOINT is called in a transaction block, stored procedures that contain COMMIT/ROLLBACK cannot be called.
+- Stored procedures that contain COMMIT, ROLLBACK, or SAVEPOINT cannot be called in TRIGGER.
+- COMMIT, ROLLBACK, and SAVEPOINT cannot be invoked in EXECUTE statements.
+- Stored procedures that contain COMMIT, ROLLBACK, or SAVEPOINT cannot be called in CURSOR statements.
+- Stored procedures that contain IMMUTABLE or SHIPPABLE cannot call COMMIT, ROLLBACK, SAVEPOINT or another stored procedure that contain COMMIT, ROLLBACK, or SAVEPOINT.
+- Stored procedures that contain COMMIT, ROLLBACK, or SAVEPOINT cannot be called in SQL statements other than SELECT PROC and CALL PROC.
+- COMMIT, ROLLBACK, or SAVEPOINT cannot be called in a stored procedure whose header contains GUC parameters.
+- COMMIT, ROLLBACK, or SAVEPOINT cannot be called in expressions or CURSOR and EXECUTE statements.
+- Stored procedures that contain COMMIT, ROLLBACK, or SAVEPOINT cannot be called in the return values and expression calculation of stored procedures.
+- An autonomous transaction and a stored procedure transaction are two independent transactions that cannot use the savepoints defined in each other.
+
+The following content cannot be committed or rolled back:
+
+- Variables declared or imported in stored procedures cannot be submitted or rolled back.
+- In stored procedures, GUC parameters that take effect only after a restart cannot be submitted or rolled back.
+
+**Examples**
+
+- Example 1: COMMIT/ROLLBACK can be used in stored procedures in PLSQL.
+
+  ```sql
+  CREATE TABLE EXAMPLE1(COL1 INT);
+
+  CREATE OR REPLACE PROCEDURE TRANSACTION_EXAMPLE()
+  AS
+  BEGIN
+      FOR i IN 0..20 LOOP
+          INSERT INTO EXAMPLE1(COL1) VALUES (i);
+          IF i % 2 = 0 THEN
+              COMMIT;
+          ELSE
+              ROLLBACK;
+          END IF;
+      END LOOP;
+  END;
+  /
+  ```
+
+- Example 2:
+
+  COMMIT and ROLLBACK can be used in stored procedures that contain EXCEPTION.
+
+  COMMIT and ROLLBACK can be used in EXCEPTION statements of stored procedures.
+
+  DDL statements after COMMIT or ROLLBACK can be submitted or rolled back.
+
+  ```sql
+  CREATE OR REPLACE PROCEDURE TEST_COMMIT_INSERT_EXCEPTION_ROLLBACK()
+  AS
+  BEGIN
+      DROP TABLE IF EXISTS TEST_COMMIT;
+      CREATE TABLE TEST_COMMIT(A INT, B INT);
+      INSERT INTO TEST_COMMIT SELECT 1, 1;
+      COMMIT;
+          CREATE TABLE TEST_ROLLBACK(A INT, B INT);
+      RAISE EXCEPTION 'RAISE EXCEPTION AFTER COMMIT';
+  EXCEPTION
+      WHEN OTHERS THEN
+      INSERT INTO TEST_COMMIT SELECT 2, 2;
+      ROLLBACK;
+  END;
+  /
+
+  ```
+
+- Example 3: A stored procedure that contains COMMIT or ROLLBACK (which means the stored procedure is controlled by BEGIN, START, or END) can be called in a transaction block.
+
+  ```sql
+  BEGIN;
+      CALL TEST_COMMIT_INSERT_EXCEPTION_ROLLBACK();
+  END;
+  ```
+
+- Example 4: COMMIT/ROLLBACK, including IF, FOR, CURSOR LOOP, and WHILE, can be called in most PLSQL contexts and statements.
+
+  ```sql
+  CREATE OR REPLACE PROCEDURE TEST_COMMIT2()
+  IS
+  BEGIN
+      DROP TABLE IF EXISTS TEST_COMMIT;
+      CREATE TABLE TEST_COMMIT(A INT);
+      FOR I IN REVERSE 3..0 LOOP
+      INSERT INTO TEST_COMMIT SELECT I;
+      COMMIT;
+      END LOOP;
+      FOR I IN REVERSE 2..4 LOOP
+      UPDATE TEST_COMMIT SET A=I;
+      COMMIT;
+      END LOOP;
+  EXCEPTION
+  WHEN OTHERS THEN
+      INSERT INTO TEST_COMMIT SELECT 4;
+      COMMIT;
+  END;
+  /
+  ```
+
+- Example 5: GUC parameters in stored procedures can be submitted or rolled back.
+
+  ```sql
+  SHOW explain_perf_mode;
+  SHOW enable_force_vector_engine;
+
+  CREATE OR REPLACE PROCEDURE GUC_ROLLBACK()
+  AS
+  BEGIN
+      SET enable_force_vector_engine = on;
+      COMMIT;
+      SET explain_perf_mode TO pretty;
+      ROLLBACK;
+  END;
+  /
+
+  call GUC_ROLLBACK();
+  SHOW explain_perf_mode;
+  SHOW enable_force_vector_engine;
+  SET enable_force_vector_engine = off;
+  ```
+
+- Example 6: COMMIT, ROLLBACK, and stored procedures that contain COMMIT or ROLLBACK cannot be called in functions.
+
+  ```sql
+  CREATE OR REPLACE FUNCTION FUNCTION_EXAMPLE1() RETURN INT
+  AS
+  EXP INT;
+  BEGIN
+      FOR i IN 0..20 LOOP
+          INSERT INTO EXAMPLE1(col1) VALUES (i);
+          IF i % 2 = 0 THEN
+              COMMIT;
+          ELSE
+              ROLLBACK;
+          END IF;
+      END LOOP;
+      SELECT COUNT(*) FROM EXAMPLE1 INTO EXP;
+      RETURN EXP;
+  END;
+  /
+  ```
+
+- Example 7: Stored procedures that contain COMMIT or ROLLBACK cannot be called in functions.
+
+  ```sql
+  CREATE OR REPLACE FUNCTION FUNCTION_EXAMPLE2() RETURN INT
+  AS
+  EXP INT;
+  BEGIN
+      -- transaction_example is a stored procedure and contains the COMMIT/ROLLBACK statement.
+      CALL transaction_example();
+      SELECT COUNT(*) FROM EXAMPLE1 INTO EXP;
+      RETURN EXP;
+  END;
+  /
+  ```
+
+- Example 8: A TRIGGER stored procedure cannot contain COMMIT/ROLLBACK or called another stored procedure that contains COMMIT/ROLLBACK.
+
+  ```sql
+  CREATE OR REPLACE FUNCTION FUNCTION_TRI_EXAMPLE2() RETURN TRIGGER
+  AS
+  EXP INT;
+  BEGIN
+      FOR i IN 0..20 LOOP
+          INSERT INTO EXAMPLE1(col1) VALUES (i);
+          IF i % 2 = 0 THEN
+              COMMIT;
+          ELSE
+              ROLLBACK;
+          END IF;
+      END LOOP;
+      SELECT COUNT(*) FROM EXAMPLE1 INTO EXP;
+  END;
+  /
+
+  CREATE TRIGGER TRIGGER_EXAMPLE AFTER DELETE ON EXAMPLE1
+  FOR EACH ROW EXECUTE PROCEDURE FUNCTION_TRI_EXAMPLE2();
+
+  DELETE FROM EXAMPLE1;
+  ```
+
+- Example 9: Stored procedures that contain IMMUTABLE or SHIPPABLE cannot call COMMIT, ROLLBACK, or another stored procedure that contains COMMIT or ROLLBACK.
+
+  ```sql
+  CREATE OR REPLACE PROCEDURE TRANSACTION_EXAMPLE1()
+  IMMUTABLE
+  AS
+  BEGIN
+      FOR i IN 0..20 LOOP
+          INSERT INTO EXAMPLE1 (col1) VALUES (i);
+          IF i % 2 = 0 THEN
+              COMMIT;
+          ELSE
+              ROLLBACK;
+          END IF;
+      END LOOP;
+  END;
+  /
+  ```
+
+- Example 10: Variables declared or imported in stored procedures cannot be submitted or rolled back.
+
+  ```sql
+  CREATE OR REPLACE PROCEDURE TRANSACTION_EXAMPLE2(EXP_OUT OUT INT)
+  AS
+  EXP INT;
+  BEGIN
+      EXP_OUT := 0;
+      COMMIT;
+      DBE_OUTPUT.PRINT_LINE('EXP IS:'||EXP);
+      EXP_OUT := 1;
+      ROLLBACK;
+      DBE_OUTPUT.PRINT_LINE('EXP IS:'||EXP);
+  END;
+  /
+  ```
+
+- Example 11: Calling in SQL statements (other than Select Procedure) is not supported.
+
+  ```sql
+  CREATE OR REPLACE PROCEDURE TRANSACTION_EXAMPLE3()
+  AS
+  BEGIN
+      FOR i IN 0..20 LOOP
+          INSERT INTO EXAMPLE1 (col1) VALUES (i);
+          IF i % 2 = 0 THEN
+              EXECUTE IMMEDIATE 'COMMIT';
+          ELSE
+              EXECUTE IMMEDIATE 'ROLLBACK';
+          END IF;
+      END LOOP;
+  END;
+  /
+  ```
+
+- Example 12: COMMIT/ROLLBACK cannot be called in a stored procedure whose header contains GUC parameters.
+
+  ```sql
+  CREATE OR REPLACE PROCEDURE TRANSACTION_EXAMPLE4()
+  SET ARRAY_NULLS TO "ON"
+  AS
+  BEGIN
+      FOR i IN 0..20 LOOP
+          INSERT INTO EXAMPLE1 (col1) VALUES (i);
+          IF i % 2 = 0 THEN
+              COMMIT;
+          ELSE
+              ROLLBACK;
+          END IF;
+      END LOOP;
+  END;
+  /
+  ```
+
+- Example 13: A stored procedure object whose cursor is open cannot contain COMMIT/ROLLBACK.
+
+  ```sql
+  CREATE OR REPLACE PROCEDURE TRANSACTION_EXAMPLE5(INTIN IN INT, INTOUT OUT INT)
+  AS
+  BEGIN
+  INTOUT := INTIN + 1;
+  COMMIT;
+  END;
+  /
+
+  CREATE OR REPLACE PROCEDURE TRANSACTION_EXAMPLE6()
+  AS
+  CURSOR CURSOR1(EXPIN INT)
+  IS SELECT TRANSACTION_EXAMPLE5(EXPIN);
+  INTEXP INT;
+  BEGIN
+      FOR i IN 0..20 LOOP
+          OPEN CURSOR1(i);
+          FETCH CURSOR1 INTO INTEXP;
+          INSERT INTO EXAMPLE1(COL1) VALUES (INTEXP);
+          IF i % 2 = 0 THEN
+              COMMIT;
+          ELSE
+              ROLLBACK;
+          END IF;
+          CLOSE CURSOR1;
+      END LOOP;
+  END;
+  /
+  ```
+
+- Example 14: COMMIT and ROLLBACK cannot be called in expressions or CURSOR and EXECUTE statements.
+
+  ```sql
+  CREATE OR REPLACE PROCEDURE exec_func1()
+  AS
+  BEGIN
+      CREATE TABLE TEST_exec(A INT);
+  COMMIT;
+  END;
+  /
+  CREATE OR REPLACE PROCEDURE exec_func2()
+  AS
+  BEGIN
+  EXECUTE exec_func1();
+  COMMIT;
+  END;
+  /
+  ```
+
+- Example 15: Return values and expression calculation of stored procedures are not supported.
+
+  ```sql
+  CREATE OR REPLACE PROCEDURE exec_func3(RET_NUM OUT INT)
+  AS
+  BEGIN
+      RET_NUM := 1+1;
+  COMMIT;
+  END;
+  /
+  CREATE OR REPLACE PROCEDURE exec_func4(ADD_NUM IN INT)
+  AS
+  SUM_NUM INT;
+  BEGIN
+  SUM_NUM := ADD_NUM + exec_func3();
+  COMMIT;
+  END;
+  /
+  ```
+
+- Example 16: Roll back some modifications of stored procedure on a transaction to a savepoint.
+
+    ```sql
+    CREATE OR REPLACE PROCEDURE STP_SAVEPOINT_EXAMPLE1()
+    AS
+    BEGIN
+        INSERT INTO EXAMPLE1 VALUES(1);
+        SAVEPOINT s1;
+        INSERT INTO EXAMPLE1 VALUES(2);
+        ROLLBACK TO s1;  -- Roll back the insertion of record 2.
+        INSERT INTO EXAMPLE1 VALUES(3);
+    END;
+    /
+    ```
+
+- Example 17: Roll back a stored procedure to a savepoint defined outside the stored procedure.
+
+    ```sql
+    CREATE OR REPLACE PROCEDURE STP_SAVEPOINT_EXAMPLE2()
+    AS
+    BEGIN
+        INSERT INTO EXAMPLE1 VALUES(2);
+        ROLLBACK TO s1;  -- Roll back the insertion of record 2.
+        INSERT INTO EXAMPLE1 VALUES(3);
+    END;
+    /
+
+    BEGIN;
+    INSERT INTO EXAMPLE1 VALUES(1);
+    SAVEPOINT s1;
+    CALL STP_SAVEPOINT_EXAMPLE2();
+    SELECT * FROM EXAMPLE1;
+    COMMIT;
+    ```
+
+- Example 18: Roll back an external SQL or other stored procedure to a savepoint defined in the stored procedure.
+
+    ```sql
+    CREATE OR REPLACE PROCEDURE STP_SAVEPOINT_EXAMPLE3()
+    AS
+    BEGIN
+        INSERT INTO EXAMPLE1 VALUES(1);
+        SAVEPOINT s1;
+        INSERT INTO EXAMPLE1 VALUES(2);
+    END;
+    /
+
+    BEGIN;
+    INSERT INTO EXAMPLE1 VALUES(3);
+    CALL STP_SAVEPOINT_EXAMPLE3();
+    ROLLBACK TO SAVEPOINT s1; -- Roll back the insertion of record 2 to the stored procedure.
+    SELECT * FROM EXAMPLE1;
+    COMMIT;
+    ```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/resource-load-management/resource-load-management-overview.md b/product/en/docs-mogdb/v3.0/developer-guide/resource-load-management/resource-load-management-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..496548fa26bfd4c6e0a1778c3544e92f5d02db1f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/resource-load-management/resource-load-management-overview.md
@@ -0,0 +1,26 @@
+---
+title: Overview
+summary: Overview
+author: Guo Huan
+date: 2021-10-22
+---
+
+# Overview
+
+## Function
+
+MogDB manages resource load to balance system resource usage for jobs.
+
+## Related Concepts
+
+**Resource management**
+
+MogDB manages system resources, including CPU, memory, I/O, and storage resources. It allocates system resources in a proper way to prevent system efficiency deterioration or system running problems.
+
+**Cgroup**
+
+Control groups (Cgroups) are a mechanism provided by the Linux kernel to restrict, record, and isolate physical resources (such as CPU, memory, and I/O resources) used by process groups. Cgroups have strict restrictions on Linux system resources. If a process is added to a Cgroup, it can use only restricted resources. For details about Cgroup principles, see the product manual corresponding to your OS.
+
+**Resource pool**
+
+Resource pools are a configuration mechanism provided by MogDB to divide host resources (memory and I/O resources) and control SQL concurrency. Resource pools are bound to Cgroups. In this way, you can manage the resource loads of jobs in a specific resource pool.
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/resource-load-management/resource-management-preparation/creating-a-resource-pool.md b/product/en/docs-mogdb/v3.0/developer-guide/resource-load-management/resource-management-preparation/creating-a-resource-pool.md
new file mode 100644
index 0000000000000000000000000000000000000000..4b732af1af9939385b1f283f023e175489204e5b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/resource-load-management/resource-management-preparation/creating-a-resource-pool.md
@@ -0,0 +1,152 @@
+---
+title: Creating a Resource Pool
+summary: Creating a Resource Pool
+author: Guo Huan
+date: 2021-10-22
+---
+
+# Creating a Resource Pool
+
+## Background
+
+MogDB creates resource pools to divide host resources. After resource load management is enabled, the default resource pool alone is insufficient to address the resource load management requirements of services. Therefore, new resource pools must be used to reallocate system resources for granular control purposes. Table 1 describes the features of a common resource pool.
+
+**Table 1** Features of a common resource pool
+
+| Resource Pool                          | Feature                                                      |
+| :------------------------------------- | :----------------------------------------------------------- |
+| Common resource pool (common scenario) | A common resource pool is associated with a Workload Cgroup, and its group resource pool must not be associated with the corresponding sub-Class Cgroup. For example, to create a service resource pool and associate it with **class1:wd**, ensure that its group resource pool has not been associated with **class1**.The default value of **mem_percent** is **0%**. The sum of **mem_percent** for all common resource groups under the same group resource pool can be greater than or equal to 100%. |
+
+After resource load management is enabled, the system automatically creates **default_pool**. If no resource pool is specified for a session or user, they will be automatically associated with **default_pool**. By default, **default_pool** is associated with the **DefaultClass:Medium** Cgroup and does not limit the number of concurrent services. Table 2 describes the attributes of **default_pool**.
+
+**Table 2** default_pool attributes
+
+| Attribute         | Value               | Description                                                  |
+| :---------------- | :------------------ | :----------------------------------------------------------- |
+| respool_name      | default_pool        | Name of the resource pool                                    |
+| mem_percent       | 100                 | Maximum percentage of used memory                            |
+| cpu_affinity      | -1                  | CPU affinity (reserved)                                      |
+| control_group     | DefaultClass:Medium | Cgroup associated with the resource pool                     |
+| active_statements | -1                  | Maximum number of concurrent queries allowed by the resource pool. The value **-1** indicates that the number of concurrent queries is not limited. |
+| max_dop           | 1                   | Concurrency level of execution operators after the SMP is enabled (reserved) |
+| memory_limit      | 8GB                 | Upper memory usage limit (reserved)                          |
+| parentid          | 0                   | OID of the parent resource pool                              |
+| io_limits         | 0                   | Upper limit of IOPS. It is counted by ones for column storage and by 10 thousands for row storage. The value **0** indicates there is no limit. |
+| io_priority       | None                | I/O priority set for jobs that consume many I/O resources. It takes effect when the I/O usage reaches 90%. **None** indicates there is no control. |
+| nodegroup         | installation        | Name of the logical cluster to which the resource pool belongs |
+| is_foreign        | f                   | Specifies that the resource pool is not used for users outside the logical cluster. |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** **default_pool** cannot be modified in MogDB.
+
+## Prerequisites
+
+You are familiar with the [CREATE RESOURCE POOL](53.2-CREATE-RESOURCE-POOL), [ALTER RESOURCE POOL](11.3-ALTER-RESOURCE-POOL), and [DROP RESOURCE POOL](86.2-DROP-RESOURCE-POOL) syntax.
+
+## **Procedure**
+
+**Creating a resource pool**
+
+1. Perform the steps in [Using the gsql Client for Connection](using-the-gsql-client-for-connection).
+
+2. Create a group resource pool and associate it with the specified sub-Class Cgroup. In the following example, the group resource pool named **resource_pool_a** is associated with the **class_a** Cgroup.
+
+   ```sql
+   mogdb=# CREATE RESOURCE POOL resource_pool_a WITH (control_group='class_a');
+   mogdb=# CREATE RESOURCE POOL resource_pool_b WITH (control_group='class_b');
+   CREATE RESOURCE POOL
+   ```
+
+3. Create a service resource pool and associate it with the specified Workload Cgroup. In the following example, the service resource pool named **resource_pool_a1** is associated with the **workload_a1** Cgroup.
+
+   ```sql
+   mogdb=# CREATE RESOURCE POOL resource_pool_a1 WITH (control_group='class_a:workload_a1');
+   mogdb=# CREATE RESOURCE POOL resource_pool_a2 WITH (control_group='class_a:workload_a2');
+   mogdb=# CREATE RESOURCE POOL resource_pool_b1 WITH (control_group='class_b:workload_b1');
+   mogdb=# CREATE RESOURCE POOL resource_pool_b2 WITH (control_group='class_b:workload_b2');
+   CREATE RESOURCE POOL
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+   >
+   > - If you do not specify an associated Cgroup when creating a resource pool, the resource pool will be associated with the default Cgroup, which is the Timeshare Cgroup **Medium** under the **DefaultClass** Cgroup.
+   > - The value of **control_group** is case-sensitive and must be contained in single quotation marks (").
+   > - If a database user specifies the Timeshare string (**Rush**, **High**, **Medium**, or **Low**) in the syntax, for example, **control_group** is set to **High**, the resource pool will be associated with the **High** Timeshare Cgroup under **DefaultClass**.
+   > - **control_group** allows you to create a Workload Cgroup, for example, **class1:wd** whose Cgroup level can also be appended, such as **class1:wd:2**. The Cgroup level must be within 1 to 10, but it is not used for Cgroup differentiation. In earlier versions, you can create Workload Cgroups with the same name and differentiate them by their levels. In the latest version, Cgroup names must be unique. If you have created duplicate Workload Cgroups in an earlier version, delete them to avoid confusion.
+
+**Managing resource pools**
+
+Modify resource pool attributes. In the following example, the Cgroup associated with the resource pool **resource_pool_a2** is changed to **class_a:workload_a1** (assuming that **class_a:workload_a1** is not associated with any other resource pools).
+
+```sql
+mogdb=# ALTER RESOURCE POOL resource_pool_a2 WITH (control_group="class_a:workload_a1");
+ALTER RESOURCE POOL
+```
+
+**Deleting a resource pool**
+
+Delete a resource pool. For example, run the following command to delete the resource pool **resource_pool_a2**:
+
+```sql
+mogdb=# DROP RESOURCE POOL resource_pool_a2;
+DROP RESOURCE POOL
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - The resource pool cannot be deleted if it is associated with a role.
+> - In a multi-tenant scenario, deleting a group resource pool also deletes the related service resource pools. A resource pool can be deleted only when it is not associated with any users.
+
+## Viewing Resource Pool Information
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - Do not use the INSERT, UPDATE, DELETE, and TRUNCATE statements in the **pg_resource_pool** system catalog that manages resource load.
+> - Do not modify the **memory_limit** and **cpu_affinity** attributes of a resource pool.
+
+- Run the following command to view the information of all the resource pools of the current cluster:
+
+  ```sql
+  mogdb=# SELECT * FROM PG_RESOURCE_POOL;
+  ```
+
+  ```sql
+     respool_name   | mem_percent | cpu_affinity |    control_group    | active_statements | max_dop | memory_limit | parentid | io_limits | io_priority |  nodegroup   | is_foreign  | max_worker
+  ------------------+-------------+--------------+---------------------+-------------------+---------+--------------+----------+-----------+--------------+--------------+------------
+  default_pool     |         100 |           -1 | DefaultClass:Medium |                -1 |       1 | 8GB          |        0 |         0 | None        | installation | f  |
+  resource_pool_a  |          20 |           -1 | class_a             |                10 |       1 | 8GB          |        0 |         0 | None        | installation | f  |
+  resource_pool_b  |          20 |           -1 | class_b             |                10 |       1 | 8GB          |        0 |         0 | None        | installation | f  |
+  resource_pool_a1 |          20 |           -1 | class_a:workload_a1 |                10 |       1 | 8GB          |    16970 |         0 | None        | installation | f  |
+  resource_pool_a2 |          20 |           -1 | class_a:workload_a2 |                10 |       1 | 8GB          |    16970 |         0 | None        | installation | f  |
+  resource_pool_b1 |          20 |           -1 | class_b:workload_b1 |                10 |       1 | 8GB          |    16971 |         0 | None        | installation | f  |
+  resource_pool_b2 |          20 |           -1 | class_b:workload_b2 |                10 |       1 | 8GB          |    16971 |         0 | None        | installation | f  |
+  (7 rows)
+  ```
+
+- View information about Cgroups associated with a resource pool. For details, see **gs_control_group_info(pool text)** in [Statistics Information Functions](25-statistics-information-functions).
+
+  In the following example, **resource_pool_a1** is the name of the resource pool.
+
+  ```sql
+  mogdb=# SELECT * FROM gs_control_group_info('resource_pool_a1');
+  ```
+
+  ```sql
+          name         |  class  |  workload   | type  | gid | shares | limits | rate | cpucores
+  ---------------------+---------+-------------+-------+-----+--------+--------+------+----------
+  class_a:workload_a1 | class_a | workload_a1 | DEFWD |  87 |     30 |      0 |    0 | 0-3
+  (1 row)
+  ```
+
+  **Table 3** gs_control_group_info attributes
+
+  | Attribute | Value               | Description                                             |
+  | :-------- | :------------------ | :------------------------------------------------------ |
+  | name      | class_a:workload_a1 | Class name and workload name                            |
+  | class     | class_a             | Class Cgroup name                                       |
+  | workload  | workload_a1         | Workload Cgroup name                                    |
+  | type      | DEFWD               | Cgroup type (Top, CLASS, BAKWD, DEFWD, and TSWD)        |
+  | gid       | 87                  | Cgroup ID                                               |
+  | shares    | 30                  | Percentage of CPU resources to those on the parent node |
+  | limits    | 0                   | Percentage of CPU cores to those on the parent node     |
+  | rate      | 0                   | Allocation ratio in Timeshare                           |
+  | cpucores  | 0-3                 | CPU cores                                               |
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/resource-load-management/resource-management-preparation/enabling-resource-load-management.md b/product/en/docs-mogdb/v3.0/developer-guide/resource-load-management/resource-management-preparation/enabling-resource-load-management.md
new file mode 100644
index 0000000000000000000000000000000000000000..4a252063a5ddb8c8891e4c0171792305f91bd046
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/resource-load-management/resource-management-preparation/enabling-resource-load-management.md
@@ -0,0 +1,73 @@
+---
+title: Enabling Resource Load Management
+summary: Enabling Resource Load Management
+author: Guo Huan
+date: 2021-10-22
+---
+
+# Enabling Resource Load Management
+
+## Background
+
+This section describes how to configure parameters for resource load management.
+
+## Prerequisites
+
+- In MogDB, you can manage system resources only as a database administrator. Run the following statement to query user permissions:
+
+  ```sql
+  mogdb=# SELECT rolname FROM pg_roles WHERE rolsystemadmin = 't';
+   rolname
+  ---------
+   omm
+   Jack
+  (2 rows)
+  ```
+
+- Resource load management can be applied only to users with the login permission. Run the following statement to query user permissions:
+
+  ```sql
+  mogdb=# SELECT rolname FROM pg_roles WHERE rolcanlogin = 't';
+   rolname
+  ---------
+   omm
+  (1 row)
+  ```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** If a user's login permission is revoked, the user's resource pool will be changed to **default_pool**. For details about **default_pool**, see Table 2 in [Creating a Resource Pool](creating-a-resource-pool).
+
+## Procedure
+
+You can perform the following steps only as a database administrator to enable load management based on the resource pool. The following uses user **omm** as an example.
+
+1. Log in as the OS user **omm** to the primary node of MogDB.
+
+2. Enable the Cgroup function.
+
+   ```bash
+   gs_guc reload -Z coordinator -Z datanode -N all -I all -c "enable_control_group=on"
+   ```
+
+3. Enable resource pool-based load management.
+
+   ```bash
+   gs_guc set -Z coordinator -Z datanode -N all -I all -c "use_workload_manager=on"
+   ```
+
+4. Enable resident backend thread control for the database.
+
+   ```bash
+   gs_guc set -Z coordinator -Z datanode -N all -I all -c "enable_backend_control=on"
+   ```
+
+5. Enable control over the autoVacuumWorker thread among the resident backend threads for the database.
+
+   ```bash
+   gs_guc set -Z coordinator -Z datanode -N all -I all -c "enable_vacuum_control=on"
+   ```
+
+6. Restart the database for the parameter settings to take effect.
+
+   ```bash
+   gs_om -t stop && gs_om -t start
+   ```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/resource-load-management/resource-management-preparation/planning-resources.md b/product/en/docs-mogdb/v3.0/developer-guide/resource-load-management/resource-management-preparation/planning-resources.md
new file mode 100644
index 0000000000000000000000000000000000000000..a76a87c641ee08f58f19dcfa4a43c313e99ba377
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/resource-load-management/resource-management-preparation/planning-resources.md
@@ -0,0 +1,81 @@
+---
+title: Planning Resources
+summary: Planning Resources
+author: Guo Huan
+date: 2021-10-22
+---
+
+# Planning Resources
+
+Before configuring resource load management, plan tenant resources based on service models. After services run for a period of time, you can adjust the configurations based on resource usage.
+
+Assume that two departments in a large enterprise use the same cluster. MogDB puts system resources used by the same department in a group to isolate resources for different departments. Table 1 describes the resource plan.
+
+**Table 1** Tenant resource plan
+
+<table>
+    <tr>
+        <th>Tenant Name</th>
+        <th>Parameter</th>
+        <th>Example Value</th>
+    </tr>
+    <tr>
+        <td rowspan=6>Tenant A</td>
+        <td>Sub-Class Cgroup</td>
+        <td>class_a</td>
+    </tr>
+    <tr>
+        <td>Workload Cgroup</td>
+        <td>- workload_a1<br/>- workload_a2</td>
+    </tr>
+    <tr>
+        <td>Group resource pool</td>
+        <td>resource_pool_a</td>
+    </tr>
+    <tr>
+        <td>Service resource pool</td>
+        <td>- resource_pool_a1<br/>- resource_pool_a2</td>
+    </tr>
+    <tr>
+        <td>Group user</td>
+        <td>tenant_a</td>
+    </tr>
+    <tr>
+        <td>Service user</td>
+        <td>- tenant_a1<br/>- tenant_a2</td>
+    </tr>
+
+</table>
+
+<table>
+    <tr>
+        <th>Tenant Name</th>
+        <th>Parameter</th>
+        <th>Example Value</th>
+    </tr>
+    <tr>
+        <td rowspan=6>Tenant B</td>
+        <td>Sub-Class Cgroup</td>
+        <td>class_b</td>
+    </tr>
+    <tr>
+        <td>Workload Cgroup</td>
+        <td>- workload_b1<br/>- workload_b2</td>
+    </tr>
+    <tr>
+        <td>Group resource pool</td>
+        <td>resource_pool_b</td>
+    </tr>
+    <tr>
+        <td>Service resource pool</td>
+        <td>- resource_pool_b1<br/>- resource_pool_b2</td>
+    </tr>
+    <tr>
+        <td>Group user</td>
+        <td>tenant_b</td>
+    </tr>
+    <tr>
+        <td>Service user</td>
+        <td>- tenant_b1<br/>- tenant_b2</td>
+    </tr>
+</table>
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/resource-load-management/resource-management-preparation/setting-a-cgroup.md b/product/en/docs-mogdb/v3.0/developer-guide/resource-load-management/resource-management-preparation/setting-a-cgroup.md
new file mode 100644
index 0000000000000000000000000000000000000000..24b1053980f461e7a6d2e14a5e934d7d950e189a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/resource-load-management/resource-management-preparation/setting-a-cgroup.md
@@ -0,0 +1,280 @@
+---
+title: Setting a Cgroup
+summary: Setting a Cgroup
+author: Guo Huan
+date: 2021-03-04
+---
+
+# Setting a Cgroup
+
+## Background
+
+The core of MogDB resource load management is resource pools. The first step of configuring a resource pool is to configure Cgroups in the environment. For details about Cgroup principles, see the product manual corresponding to your OS. For details about MogDB Cgroups, see [Viewing Cgroup Information](#Viewing-Cgroup-Information).
+
+The Class Cgroup is a top-layer Cgroup for database service running. **DefaultClass** is a sub-category of the Class Cgroup and is automatically created when a cluster is deployed. The **Medium** Cgroup under **DefaultClass** contains running jobs that are triggered by the system. Resource configurations of **Medium** cannot be modified, and the jobs running on it are not controlled by resource management. Therefore, you are advised to create sub-Class and Workload Cgroups to control resource allocation.
+
+## Prerequisites
+
+You are familiar with "Server Tools > [gs_cgroup](0-gs_cgroup)" and "Server Tools > [gs_ssh](10-gs_ssh)" in Tool Reference.
+
+## Procedure
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - To control all the resources in MogDB, you need to create, update, and delete Cgroups on each node. Use **gs_ssh** (see "Server Tools > gs_ssh" in *Tool Reference*) to run commands in the steps below.
+> - A Cgroup must be named as follows:
+>   - The names of sub-Class Cgroups and Workload Cgroups cannot contain columns (:).
+>   - Cgroups having the same name cannot be created.
+
+**Creating sub-Class and Workload Cgroups**
+
+1. Log in as the OS user **omm** to the primary node of MogDB.
+
+2. Create sub-Class Cgroups **class_a** and **class_b**, and allocate 40% and 20% of Class CPU resources to them, respectively.
+
+   ```bash
+   gs_ssh -c "gs_cgroup -c -S class_a -s 40"
+   ```
+
+   ```bash
+   gs_ssh -c "gs_cgroup -c -S class_b -s 20"
+   ```
+
+3. Create Workload Cgroups **workload_a1** and **workload_a2** under **class_a**, and allocate 20% and 60% of **class_a** CPU resources to them, respectively.
+
+   ```bash
+   gs_ssh -c "gs_cgroup -c -S class_a -G workload_a1 -g 20 "
+   ```
+
+   ```bash
+   gs_ssh -c "gs_cgroup -c -S class_a -G workload_a2 -g 60 "
+   ```
+
+4. Create Workload Cgroups **workload_b1** and **workload_b2** under **class_b**, and allocate 50% and 40% of **class_b** CPU resources to them, respectively.
+
+   ```bash
+   gs_ssh -c "gs_cgroup -c -S class_b -G workload_b1 -g 50 "
+   ```
+
+   ```bash
+   gs_ssh -c "gs_cgroup -c -S class_b -G workload_b2 -g 40 "
+   ```
+
+**Adjusting resource quotas for Cgroups**
+
+1. Change the CPU resource quota for **class_a** to 30%.
+
+   ```bash
+   gs_ssh -c "gs_cgroup -u -S class_a -s 30"
+   ```
+
+2. Change the CPU resource quota for **workload_a1** under **class_a** to 30% of **class_a** CPU resources.
+
+   ```bash
+   gs_ssh -c "gs_cgroup -u -S class_a -G workload_a1 -g 30"
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** After adjustment, CPU resources allocated to **workload_a1** should not be greater than those allocated to **class_a**. The name of a Workload Cgroup cannot be a default name of the Timeshare Cgroup, that is, **Low**, **Medium**, **High**, or **Rush**.
+
+**Deleting a Cgroup**
+
+1. Delete the Cgroup **class_a**.
+
+   ```bash
+   gs_ssh -c "gs_cgroup -d  -S class_a"
+   ```
+
+   After the command is executed, the Cgroup **class_a** is deleted.
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** User **root** or a user with the **root** permission can delete the default Cgroups that can be accessed by a common user **username** by specifying **-d** and **-U** **username**. A common user can delete existing Class Cgroups by specifying **-d** and **-S** **classname**.
+
+## Viewing Cgroup Information
+
+1. View Cgroup information in configuration files.
+
+   ```bash
+   gs_cgroup -p
+   ```
+
+   Cgroup configuration
+
+   ```bash
+   gs_cgroup -p
+
+   Top Group information is listed:
+   GID:   0 Type: Top    Percent(%): 1000( 50) Name: Root                  Cores: 0-47
+   GID:   1 Type: Top    Percent(%):  833( 83) Name: Gaussdb:omm           Cores: 0-20
+   GID:   2 Type: Top    Percent(%):  333( 40) Name: Backend               Cores: 0-20
+   GID:   3 Type: Top    Percent(%):  499( 60) Name: Class                 Cores: 0-20
+
+   Backend Group information is listed:
+   GID:   4 Type: BAKWD  Name: DefaultBackend   TopGID:   2 Percent(%): 266(80) Cores: 0-20
+   GID:   5 Type: BAKWD  Name: Vacuum           TopGID:   2 Percent(%):  66(20) Cores: 0-20
+
+   Class Group information is listed:
+   GID:  20 Type: CLASS  Name: DefaultClass     TopGID:   3 Percent(%): 166(20) MaxLevel: 1 RemPCT: 100 Cores: 0-20
+   GID:  21 Type: CLASS  Name: class1           TopGID:   3 Percent(%): 332(40) MaxLevel: 2 RemPCT:  70 Cores: 0-20
+
+   Workload Group information is listed:
+   GID:  86 Type: DEFWD  Name: grp1:2           ClsGID:  21 Percent(%):  99(30) WDLevel:  2 Quota(%): 30 Cores: 0-5
+
+   Timeshare Group information is listed:
+   GID: 724 Type: TSWD   Name: Low              Rate: 1
+   GID: 725 Type: TSWD   Name: Medium           Rate: 2
+   GID: 726 Type: TSWD   Name: High             Rate: 4
+   GID: 727 Type: TSWD   Name: Rush             Rate: 8
+
+   Group Exception information is listed:
+   GID:  20 Type: EXCEPTION Class: DefaultClass
+   PENALTY: QualificationTime=1800 CPUSkewPercent=30
+
+   GID:  21 Type: EXCEPTION Class: class1
+   PENALTY: AllCpuTime=100 QualificationTime=2400 CPUSkewPercent=90
+
+   GID:  86 Type: EXCEPTION Group: class1:grp1:2
+   ABORT: BlockTime=1200 ElapsedTime=2400
+   ```
+
+   Table 1 lists the Cgroup configuration shown in the above example.
+
+   **Table 1** Cgroup configuration
+
+   <table>
+       <tr>
+           <th>GID</th>
+           <th>Type</th>
+           <th>Name</th>
+           <th>Percentage (%)</th>
+           <th>Remarks</th>
+       </tr>
+       <tr>
+           <td>0</td>
+           <td rowspan=4>Top Cgroup</td>
+           <td>Root</td>
+           <td>The number 1000 indicates that the total system resources are divided into 1000 pieces.<br/>The number 50 in the parentheses indicates 50% of I/O resources.<br/>MogDB does not control I/O resources through Cgroups. Therefore, the following Cgroup information is only about CPU.</td>
+           <td>-</td>
+       </tr>
+       <tr>
+           <td>1</td>
+           <td>Gaussdb:omm</td>
+           <td>Only one database program runs in a cluster. The default quota of the Gaussdb:omm Cgroup is 833. That is, the ratio of database programs to non-database programs is 5:1 (833:167).</td>
+           <td>-</td>
+       </tr>
+       <tr>
+           <td>2</td>
+           <td>Backend</td>
+           <td rowspan=2>The number 40 in the parentheses indicates that the Backend Cgroup takes up 40% of the resources of the Gaussdb:dbuser Cgroup. The number 60 in the parentheses indicates that the Class Cgroup takes up 60% of the resources of the Gaussdb:dbuser Cgroup.</td>
+           <td>-</td>
+       </tr>
+       <tr>
+           <td>3</td>
+           <td>Class</td>
+           <td>-</td>
+       </tr>
+       <tr>
+           <td>4</td>
+           <td rowspan=2>Backend Cgroup</td>
+           <td>DefaultBackend</td>
+           <td rowspan=2>The numbers 80 and 20 in the parentheses indicate the percentages of Backend Cgroup resources taken by the DefaultBackend and Vacuum groups, respectively.</td>
+           <td rowspan=2>TopGID: GID (2) of the Backend Cgroup in a Top Cgroup</td>
+       </tr>
+       <tr>
+           <td>5</td>
+           <td>Vacuum</td>
+       </tr>
+       <tr>
+           <td>20</td>
+           <td rowspan=2>Class Cgroup</td>
+           <td>DefaultClass</td>
+           <td rowspan=2>The number 20 in the parentheses indicates that the DefaultClass Cgroup takes up 20% of the Class Cgroup resources. The number 40 in the parentheses indicates that the class1 Cgroup takes up 40% of the Class Cgroup resources. There are only two Class Cgroups currently. Therefore, the system resource quotas for the Class Cgroups (499) are allocated in the ratio of 20:40 (166:332).</td>
+           <td rowspan=2>- TopGID: GID (3) of the Class Cgroups in a Top Cgroup to which the DefaultClass and class1 Cgroups belong.<br/>-
+   MaxLevel: maximum number of levels for Workload Cgroups in a Class Cgroup. This parameter is set to 1 for DefaultClass because it has no Workload Cgroups.<br/>-
+   RemPCT: percentage of remaining resources in a Class Cgroup after its resources are allocated to Workload Cgroups. For example, the percentage of remaining resources in the class1 Cgroup is 70%.</td>
+       </tr>
+       <tr>
+           <td>21</td>
+           <td>class1</td>
+       </tr>
+       <tr>
+           <td>86</td>
+           <td>Workload Cgroup</td>
+           <td>grp1:2<br/>(This name is composed of the name of a Workload Cgroup and its level in the Class Cgroup. This grp1:2 Cgroup is the first Workload Cgroup under the class1 Cgroup, and its level is 2. Each Class Cgroup contains a maximum of 10 levels of Workload Cgroups.)</td>
+           <td>In this example, this Workload Cgroup takes up 30% of class1 Cgroup resources (332 x 30% = 99).</td>
+           <td>- ClsGID: GID of the class1 Cgroup to which the Workload Cgroup belongs.<br/>- WDLevel: level of the Workload Cgroup in the corresponding Class Cgroup.</td>
+       </tr>
+       <tr>
+           <td>724</td>
+           <td rowspan=4>Timeshare Cgroup</td>
+           <td>Low</td>
+           <td>-</td>
+           <td rowspan=4>Rate: rate of resources allocated to a Timeshare Cgroup. The Low Cgroup has the minimum rate 1 and the Rush Cgroup has the maximum rate 8. The resource rate for Rush:High:Medium:Low is 8:4:2:1 under a Timeshare Cgroup.</td>
+       </tr>
+       <tr>
+           <td>725</td>
+           <td>Medium</td>
+           <td>-</td>
+       </tr>
+       <tr>
+           <td>726</td>
+           <td>High</td>
+           <td>-</td>
+       </tr>
+       <tr>
+           <td>727</td>
+           <td>Rush</td>
+           <td>-</td>
+       </tr>
+   </table>
+
+2. View the Cgroup tree in the OS.
+
+   Run the following command to query the structure of the Cgroup tree:
+
+   ```bash
+   gs_cgroup -P
+   ```
+
+   In the command output, **shares** indicates the value of **cpu.shares**, which specifies the dynamic quota of CPU resources in the OS, and **cpus** indicates the value of **cpuset.cpus**, which specifies the dynamic quota of CPUSET resources in the OS (number of cores that a Cgroup can use).
+
+   ```
+   Mount Information:
+   cpu:/dev/cgroup/cpu
+   blkio:/dev/cgroup/blkio
+   cpuset:/dev/cgroup/cpuset
+   cpuacct:/dev/cgroup/cpuacct
+
+   Group Tree Information:
+   - Gaussdb:wangrui (shares: 5120, cpus: 0-20, weight: 1000)
+           - Backend (shares: 4096, cpus: 0-20, weight: 400)
+                   - Vacuum (shares: 2048, cpus: 0-20, weight: 200)
+                   - DefaultBackend (shares: 8192, cpus: 0-20, weight: 800)
+           - Class (shares: 6144, cpus: 0-20, weight: 600)
+                   - class1 (shares: 4096, cpus: 0-20, weight: 400)
+                           - RemainWD:1 (shares: 1000, cpus: 0-20, weight: 100)
+                                   - RemainWD:2 (shares: 7000, cpus: 0-20, weight: 700)
+                                           - Timeshare (shares: 1024, cpus: 0-20, weight: 500)
+                                                   - Rush (shares: 8192, cpus: 0-20, weight: 800)
+                                                   - High (shares: 4096, cpus: 0-20, weight: 400)
+                                                   - Medium (shares: 2048, cpus: 0-20, weight: 200)
+                                                   - Low (shares: 1024, cpus: 0-20, weight: 100)
+                                   - grp1:2 (shares: 3000, cpus: 0-5, weight: 300)
+                           - TopWD:1 (shares: 9000, cpus: 0-20, weight: 900)
+                   - DefaultClass (shares: 2048, cpus: 0-20, weight: 200)
+                           - RemainWD:1 (shares: 1000, cpus: 0-20, weight: 100)
+                                   - Timeshare (shares: 1024, cpus: 0-20, weight: 500)
+                                           - Rush (shares: 8192, cpus: 0-20, weight: 800)
+                                           - High (shares: 4096, cpus: 0-20, weight: 400)
+                                           - Medium (shares: 2048, cpus: 0-20, weight: 200)
+                                           - Low (shares: 1024, cpus: 0-20, weight: 100)
+                           - TopWD:1 (shares: 9000, cpus: 0-20, weight: 900)
+   ```
+
+3. Obtain the Cgroup configuration in a system view.
+
+   1. Perform the steps in [Using the gsql Client for Connection](using-the-gsql-client-for-connection).
+
+   2. Obtain the configuration about all Cgroups in the system.
+
+      ```sql
+      mogdb=# SELECT * FROM gs_all_control_group_info;
+      ```
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/scheduled-jobs/pkg-service.md b/product/en/docs-mogdb/v3.0/developer-guide/scheduled-jobs/pkg-service.md
new file mode 100644
index 0000000000000000000000000000000000000000..dc4723a4acbc71e541a21e60531699231307ad60
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/scheduled-jobs/pkg-service.md
@@ -0,0 +1,367 @@
+---
+title: PKG_SERVICE API
+summary: PKG_SERVICE API
+author: Guo Huan
+date: 2022-03-18
+---
+
+# PKG_SERVICE API
+
+MogDB 2.1 provides the following PKG_SERVICE API to manage scheduled jobs.
+
+<br/>
+
+Table1 API Descriptions
+
+| API                    | Descriptions                                                 |
+| ---------------------- | ------------------------------------------------------------ |
+| PKG_SERVICE.JOB_CANCEL | Delete the scheduled job by job ID.                          |
+| PKG_SERVICE.JOB_FINISH | Disable or enable scheduled job.                             |
+| PKG_SERVICE.JOB_SUBMIT | Submit a scheduled job. The job ID is automatically generated by the system or specified by the user. |
+| PKG_SERVICE.JOB_UPDATE | Update the properties of the scheduled job, including job content, next execution time, and execution interval. |
+
+<br/>
+
+## API Definition and Usage Examples
+
+- PKG_SERVICE.JOB_CANCEL
+
+  The **CANCEL** procedure deletes the specified scheduled job.
+
+  PKG_SERVICE.JOB_CANCEL function prototype is:
+
+  ```
+  PKG_SERVICE.JOB_CANCEL( job IN INTEGER);
+  ```
+
+  Table 2 PKG_SERVICE.JOB_CANCEL API parameters description
+
+  | Parameter | Type    | In/Out | Whether it can be empty | Definition        |
+  | --------- | ------- | ------ | ----------------------- | ----------------- |
+  | id        | integer | IN     | No                      | Specified job ID. |
+
+  **Example:**
+
+  ```sql
+  CALL PKG_SERVICE.JOB_CANCEL(101);
+  ```
+
+- PKG_SERVICE.JOB_FINISH
+
+  The **FINISH** procedure disables or enables scheduled job.
+
+  PKG_SERVICE.JOB_FINISH function prototype is:
+
+  ```
+  PKG_SERVICE.JOB_FINISH(
+  id IN INTEGER,
+  broken IN BOOLEAN, 
+  next_time IN TIMESTAMP DEFAULT sysdate);
+  ```
+
+  Table 3 PKG_SERVICE.JOB_FINISH API parameters description
+  
+  | Parameter | Type      | In/Out | Whether it can be empty | Definition                                                   |
+  | --------- | --------- | ------ | ----------------------- | ------------------------------------------------------------ |
+  | id        | integer   | IN     | No                      | Specified job ID.                                            |
+  | broken    | Boolean   | IN     | No                      | Status flag bit, **true** means disabled, **false** means enabled. The current job is updated according to the **true** or **false** value; if it is **null**, the status of the original job is not changed. |
+  | next_time | timestamp | IN     | Yes                     | The next run time, the default value is the current system time. If the parameter **broken** state is **true**, the parameter is updated to **4000-1-1**; if the parameter **broken** state is **false**, and if the parameter next_time is not null, the **next_time** value of the specified job is updated, if **next_time** is **null**, the **next_time** value is not updated. This parameter can be omitted and is the default value. |
+
+- PKG_SERVICE.JOB_SUBMIT
+
+  The **JOB_SUBMIT** procedure submits a system-provided scheduled job.
+
+  PKG_SERVICE.JOB_SUBMIT function prototype is:
+
+  ```
+  PKG_SERVICE.JOB_SUBMIT(
+  id IN BIGINT DEFAULT, 
+  content IN TEXT, 
+  next_date IN TIMESTAMP DEFAULT sysdate, 
+  interval_time IN TEXT DEFAULT 'null', 
+  job OUT INTEGER);
+  ```
+  
+  > Note: When a scheduled job is created, the system binds the current database and user name to the currently created timed task by default. This API function can be called by **call** or **select** statement, if called by **select**, you can leave out the parameters. If in a stored procedure, the API function needs to be called via **perform** statement. If the submitted SQL statement job uses a non-public schema, you should specify the schema of the table or function, or add the `set current_schema = xxx;` statement before the SQL statement.
+  >
+  
+  Table 4 PKG_SERVICE.JOB_SUBMIT API parameters description
+  
+  | Parameter     | Type      | In/Out | Whether it can be empty | Definition                                                   |
+  | ------------- | --------- | ------ | ----------------------- | ------------------------------------------------------------ |
+  | id            | bigint    | IN     | No                      | Job ID. If the passed id is **NULL**, the job ID will be generated internally. |
+  | context       | text      | IN     | No                      | The SQL statement to be executed. Support one or more scenarios of 'DML', 'anonymous block', 'statement calling a stored procedure' or a mix of all 3. |
+  | next_time     | timestamp | IN     | No                      | The next job run time. The default value is the current system time (sysdate). If it is a past time, it indicates immediate execution when the job is submitted. |
+  | interval_time | text      | IN     | Yes                     | The time expression used to calculate the next job run time, either as an interval expression or as sysdate plus a numeric value (e.g. sysdate+1.0/24). If the value is null or the string "null", it means that the job will be executed only once, and the job status will become 'd' after execution. |
+  | job           | integer   | OUT    | No                      | Job ID. The range is 1-32767. This parameter can be omitted when pkg_service.job_submit is called with **select** statement. |
+  
+  **Example:**
+  
+  ```sql
+  SELECT PKG_SERVICE.JOB_SUBMIT(NULL, 'call pro_xxx();', to_date('20180101','yyyymmdd'),'sysdate+1');
+  
+  SELECT PKG_SERVICE.JOB_SUBMIT(NULL, 'call pro_xxx();', to_date('20180101','yyyymmdd'),'sysdate+1.0/24');
+  
+  CALL PKG_SERVICE.JOB_SUBMIT(NULL, 'INSERT INTO T_JOB  VALUES(1);  call pro_1(); call pro_2();', add_months(to_date('201701','yyyymm'),1), 'date_trunc(''day'',SYSDATE) + 1 +(8*60+30.0)/(24*60)' ,:jobid);
+  
+  SELECT PKG_SERVICE.JOB_SUBMIT (101, 'insert_msg_statistic1;', sysdate, 'sysdate+3.0/24');
+  ```
+
+- PKG_SERVICE.JOB_UPDATE
+
+  The **UPDATE** procedure modifies the properties of a scheduled job, including the job content, next execution time, and execution interval.
+
+  PKG_SERVICE.JOB_UPDATE function prototype is:
+
+  ```
+  PKG_SERVICE.JOB_UPDATE(
+  id IN BIGINT, 
+  next_time IN TIMESTAMP, 
+  interval_time IN TEXT, 
+  content IN TEXT);
+  ```
+
+  Table 5 PKG_SERVICE.JOB_UPDATE API parameters description
+
+  | Parameter     | Type      | In/Out | Whether it can be empty | Definition                                                   |
+  | ------------- | --------- | ------ | ----------------------- | ------------------------------------------------------------ |
+  | id            | integer   | IN     | No                      | Specified job ID.                                            |
+  | next_time     | timestamp | IN     | Yes                     | The next job run time. If this parameter is null, the next_time value of the specified job is not updated, otherwise the next_time value of the specified job is updated. |
+  | interval_time | text      | IN     | Yes                     | The time expression used to calculate the next job run time. If the parameter is null, the interval_time value of the specified job will not be updated; if the parameter is not null, it will check whether the interval_time is a valid time type or interval type, then the interval_time value of the specified job will be updated. If it is the string "null", it means it will be executed only once, and the job status will become 'd' after execution. |
+  | content       | text      | IN     | Yes                     | The name of the stored procedure or SQL statement block to execute. If this parameter is null, the content value of the specified job is not updated, otherwise the content value of the specified job is updated. |
+
+  **Example:**
+
+  ```sql
+  CALL PKG_SERVICE.JOB_UPDATE(101, 'call userproc();', sysdate, 'sysdate + 1.0/1440');
+  
+  CALL PKG_SERVICE.JOB_UPDATE(101, 'insert into tbl_a values(sysdate);', sysdate, 'sysdate + 1.0/1440');
+  ```
+
+<br/>
+
+## Examples of Using Scheduled Job
+
+This example describes how to implement job management through the above APIs.
+
+- Create a test table
+
+  ```
+  mogdb=# create table t_job (value TIMESTAMP);
+  CREATE TABLE
+  
+  mogdb=# insert into t_job values(sysdate);
+  INSERT 0 1
+  
+  mogdb=# select * from t_job;
+  +---------------------+
+  | value               |
+  |---------------------|
+  | 2021-10-09 04:36:20 |
+  +---------------------+
+  SELECT 1
+  ```
+
+- Create a job to insert a record every minute
+
+  ```
+  mogdb=# select pkg_service.job_submit(null, 'insert into t_job values(sysdate);',sysdate,'sysdate + 1/1440');
+  +--------------+
+  | job_submit   |
+  |--------------|
+  | 15566        |
+  +--------------+
+  SELECT 1
+  ```
+
+- Check the results of the job runs
+
+  ```
+  mogdb=# select * from t_job;
+  +---------------------+
+  | value               |
+  |---------------------|
+  | 2021-10-09 04:36:20 |
+  | 2021-10-09 04:40:54 |
+  | 2021-10-09 04:41:54 |
+  | 2021-10-09 04:42:54 |
+  +---------------------+
+  SELECT 4
+  ```
+
+- Check job operation from system view
+
+  ```
+  mogdb=# select job_id,dbname,start_date,next_run_date,interval,failure_count from pg_job;
+  +----------+----------+----------------------------+---------------------+------------------+-----------------+
+  | job_id   | dbname   | start_date                 | next_run_date       | interval         | failure_count   |
+  |----------+----------+----------------------------+---------------------+------------------+-----------------|
+  | 15566    | postgres | 2021-10-09 04:40:54.072363 | 2021-10-09 04:56:54 | sysdate + 1/1440 | 0               |
+  +----------+----------+----------------------------+---------------------+------------------+-----------------+
+  SELECT 1
+  Time: 0.089s
+  mogdb=# select * from pg_catalog.pg_job_proc pjp where job_id=15566;
+  +----------+------------------------------------+
+  | job_id   | what                               |
+  |----------+------------------------------------|
+  | 15566    | insert into t_job values(sysdate); |
+  +----------+------------------------------------+
+  SELECT 1
+  Time: 0.089s
+  ```
+
+- Modified to execute once every 2 minutes
+
+  ```
+  mogdb=# select pkg_service.job_update(15566,null,'sysdate + 2/1440',null);
+  +--------------+
+  | job_update   |
+  |--------------|
+  |              |
+  +--------------+
+  SELECT 1
+  ```
+
+- Check modifications and run results
+
+  ```
+  mogdb=# select job_id,interval from pg_job where job_id=15566;
+  +----------+------------------+
+  | job_id   | interval         |
+  |----------+------------------|
+  | 15566    | sysdate + 2/1440 |
+  +----------+------------------+
+  SELECT 1
+  mogdb=# select * from t_job;
+  +---------------------+
+  | value               |
+  |---------------------|
+  | 2021-10-09 04:36:20 |
+  | 2021-10-09 04:40:54 |
+  | 2021-10-09 04:41:54 |
+  | 2021-10-09 04:42:54 |
+  | 2021-10-09 04:43:54 |
+  | 2021-10-09 04:44:54 |
+  | 2021-10-09 04:45:54 |
+  | 2021-10-09 04:46:54 |
+  | 2021-10-09 04:47:54 |
+  | 2021-10-09 04:48:54 |
+  | 2021-10-09 04:49:54 |
+  | 2021-10-09 04:50:54 |
+  | 2021-10-09 04:51:54 |
+  | 2021-10-09 04:52:54 |
+  | 2021-10-09 04:53:54 |
+  | 2021-10-09 04:54:54 |
+  | 2021-10-09 04:55:54 |
+  | 2021-10-09 04:56:54 |
+  | 2021-10-09 04:57:54 |
+  | 2021-10-09 04:58:54 |
+  | 2021-10-09 04:59:54 |
+  | 2021-10-09 05:00:55 |
+  | 2021-10-09 05:01:56 | <---
+  | 2021-10-09 05:03:57 | <--- Start interval 2 minutes
+  +---------------------+
+  SELECT 24
+  Time: 0.088s
+  mogdb=# select job_id,interval,next_run_date from pg_job where job_id=15566;
+  +----------+------------------+---------------------+
+  | job_id   | interval         | next_run_date       |
+  |----------+------------------+---------------------|
+  | 15566    | sysdate + 2/1440 | 2021-10-09 05:05:57 |
+  +----------+------------------+---------------------+
+  SELECT 1
+  Time: 0.078s>
+  ```
+
+- Finish and start jobs
+
+  Both finish and start are the same function **pkg_service.job_finish**, and different parameters are passed in to indicate whether to finish or start.
+
+  ```
+  mogdb=# select pkg_service.job_finish(15566,true,null);
+  +--------------+
+  | job_finish   |
+  |--------------|
+  |              |
+  +--------------+
+  SELECT 1
+  Time: 0.089s
+  mogdb=# select job_id,next_run_date,job_status from pg_job where job_id=15566;
+  +----------+---------------------+--------------+
+  | job_id   | next_run_date       | job_status   |
+  |----------+---------------------+--------------|
+  | 15566    | 4000-01-01 00:00:00 | d            |
+  +----------+---------------------+--------------+
+  SELECT 1
+  Time: 0.075s
+  mogdb=# select pkg_service.job_finish(15566,false,null);
+  +--------------+
+  | job_finish   |
+  |--------------|
+  |              |
+  +--------------+
+  SELECT 1
+  Time: 0.091s
+  mogdb=# select job_id,next_run_date,job_status from pg_job where job_id=15566;
+  +----------+---------------------+--------------+
+  | job_id   | next_run_date       | job_status   |
+  |----------+---------------------+--------------|
+  | 15566    | 4000-01-01 00:00:00 | s            |
+  +----------+---------------------+--------------+
+  SELECT 1
+  Time: 0.080s
+  ```
+
+  It can be seen that if the next run time is not specified when the job is re-start, the next run time will always remain at 4000, which means that it will still not start, so if the job is finished and then restarted, you need to manually specify the next run time.
+
+  ```
+  mogdb=# select pkg_service.job_finish(15566,false,sysdate);
+  +--------------+
+  | job_finish   |
+  |--------------|
+  |              |
+  +--------------+
+  SELECT 1
+  Time: 0.088s
+  mogdb=# select job_id,next_run_date,job_status from pg_job where job_id=15566;
+  +----------+---------------------+--------------+
+  | job_id   | next_run_date       | job_status   |
+  |----------+---------------------+--------------|
+  | 15566    | 2021-10-09 05:16:22 | s            |
+  +----------+---------------------+--------------+
+  SELECT 1
+  Time: 0.086s
+  ```
+
+- Cancel job
+
+  ```
+  mogdb=# select pkg_service.job_cancel(15566);
+  +--------------+
+  | job_cancel   |
+  |--------------|
+  |              |
+  +--------------+
+  SELECT 1
+  Time: 0.082s
+  mogdb=# select job_id,next_run_date,job_status from pg_job where job_id=15566;
+  +----------+-----------------+--------------+
+  | job_id   | next_run_date   | job_status   |
+  |----------+-----------------+--------------|
+  +----------+-----------------+--------------+
+  SELECT 0
+  Time: 0.086s
+  mogdb=# select * from pg_catalog.pg_job_proc pjp where job_id=15566;
+  +----------+--------+
+  | job_id   | what   |
+  |----------+--------|
+  +----------+--------+
+  SELECT 0
+  Time: 0.087s
+  ```
+
+<br/>
+
+## Related Pages
+
+[PG_JOB](PG_JOB), [Scheduled Job](31-scheduled-task)
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/developer-guide/user-defined-functions.md b/product/en/docs-mogdb/v3.0/developer-guide/user-defined-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..50deb44c39ed7d6ada20ba0ba88d035c66918c3b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/developer-guide/user-defined-functions.md
@@ -0,0 +1,16 @@
+---
+title: User-defined Functions
+summary: User-defined Functions
+author: Guo Huan
+date: 2021-03-04
+---
+
+# User-defined Functions
+
+In the MogDB, in order to achieve specific functions, users can define functions, just like most other languages, in addition to system library functions, programmers will also write many custom functions.
+
+MogDB user-defined functions are a combination of a set of SQL and procedure statements (declaration, allocation, loop, control flow, etc.) that are stored on the database server and can be called using the SQL interface.  In terms of presentation, user-defined functions and stored procedures are very similar, except that stored procedures have no return values but the functions have.
+
+For details about how to create and call a user-defined function, see [CREATE FUNCTION](48-CREATE-FUNCTION).
+
+The application methods for stored procedures mentioned in [Stored Procedure](1-1-stored-procedure) are similar to those for user-defined functions in this section. For details, please refer to [PL/pgSQL-SQL Procedural Language](1-1-plpgsql-overview) section, unless otherwise specified, the contents apply to stored procedures and user-defined functions.
diff --git a/product/en/docs-mogdb/v3.0/faqs/application-development-faqs.md b/product/en/docs-mogdb/v3.0/faqs/application-development-faqs.md
new file mode 100644
index 0000000000000000000000000000000000000000..e3f9276f1713eca9ded0526091e2dc4b22d16a54
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/faqs/application-development-faqs.md
@@ -0,0 +1,8 @@
+---
+title: Application Development FAQs
+summary: Application Development FAQs
+author: Guo Huan
+date: 2021-09-26
+---
+
+In preparing……
diff --git a/product/en/docs-mogdb/v3.0/faqs/deployment-and-maintenance-faqs.md b/product/en/docs-mogdb/v3.0/faqs/deployment-and-maintenance-faqs.md
new file mode 100644
index 0000000000000000000000000000000000000000..d8db9da2611f45253b3a09213d5cec8c2e096744
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/faqs/deployment-and-maintenance-faqs.md
@@ -0,0 +1,330 @@
+---
+title: Deployment and Maintenance FAQs
+summary: Deployment and Maintenance FAQs
+author: Guo Huan
+date: 2021-09-26
+---
+
+# Deployment and Maintenance FAQs
+
+## Environment Initialization FAQs
+
+**Q1: What parameter values need to be changed in `clusterconfig.xml` sample configuration file?**
+
+The node name and IP address need to be changed.
+
+```xml
+<?xml version="1.0" encoding="UTF-8"?>
+<ROOT>
+    <!-- Overall information about MogDB -->
+    <CLUSTER>
+        <PARAM name="clusterName" value="dbCluster" />
+        <PARAM name="nodeNames" value="mogdb-kernel-0002" />
+        <PARAM name="backIp1s" value="172.16.0.245"/>
+        <PARAM name="gaussdbAppPath" value="/opt/mogdb/app" />
+        <PARAM name="gaussdbLogPath" value="/opt/mogdb/mogdb_log/omm" />
+        <PARAM name="gaussdbToolPath" value="/opt/mogdb/tool" />
+        <PARAM name="corePath" value="/opt/mogdb/corefile"/>
+        <PARAM name="clusterType" value="single-inst"/>
+    </CLUSTER>
+
+    <!-- Information about node deployment on each server -->
+    <DEVICELIST>
+        <!-- Information about the node deployment on node1 -->
+        <DEVICE sn="1000001">
+            <PARAM name="name" value="mogdb-kernel-0002"/>
+            <PARAM name="azName" value="AZ1"/>
+            <PARAM name="azPriority" value="1"/>
+            <!-- If only one NIC is available for the server, set backIP1 and sshIP1 to the same IP address. -->
+            <PARAM name="backIp1" value="172.16.0.245"/>
+            <PARAM name="sshIp1" value="172.16.0.245"/>
+
+            <!--dbnode-->
+            <PARAM name="dataNum" value="1"/>
+            <PARAM name="dataPortBase" value="26000"/>
+            <PARAM name="dataNode1" value="/mogdb/data/db1"/>
+        </DEVICE>
+    </DEVICELIST>
+</ROOT>
+```
+
+<br/>
+
+## Script Initialization FAQs
+
+**Q2: What should I do if it is prompted that the parameter value of the configuration file does not match the system environment variable value?**
+
+```bash
+Failed to check the preinstall repeat condition.gaussdbToolPath [/opt/enmo/wisery] is not same with environment [/opt/mogdb/tool]
+```
+
+You can change the value of `gaussdbToolPath` in `clusterconfig.xml` to `/opt/mogdb/tool`.
+
+> Note:
+>
+> - This problem occurs mainly because the system has installed MogDB before and the environment may not be fully cleared, so there will be a situation that the parameter value in the configuration file does not match the system environment variable value, which will lead to the failure of execution. You can change the value of the parameter that reports an error in `clusterconfig.xml` configuration file to the same value as that of the parameter in the environment variable file.
+> - You can run `vi ~/.bashrc` as user `omm` to view the environment variables.
+
+**Q3: What should I do if it is prompted that I do not have permission to run the command?**
+
+```bash
+Fixing server package owner.
+[GAUSS-51400] : Failed to execute the command: su - omm -c 'cd '/opt/software/mogdb/''. Error:
+-bash: line 0: cd: /opt/software/mogdb/: Permission denied
+```
+
+Run `chmod 755 -R /opt/software` to grant permissions to the directory, and then run the script initialization command again.
+
+**Q4: What should I do if the symbolic link creation fails?**
+
+```bash
+In:failed to create symbolic link 'usr/bin/python3': File exists
+```
+
+Delete `python3` from the `usr/bin/` directory and run the `In` command again.
+
+**Q5: What should I do if it is prompted that the host name is not in the cluster?**
+
+```bash
+GAUSS-51619: "The host name [host-172-16-0-195] is not in the cluster."
+```
+
+This is because the actual host name is `host-172-16-0-195`, not `mogdb-kernel-0006`, so you need to change the node name in `clusterconfig.xml` to `host-172-16-0-195`.
+
+**Q6: What should I do if it is prompted the following error?**
+
+```bash
+[GAUSS-50202]:The /opt/mogdb must be empty. Or user [omm] has write permission to directory /opt/mogdb. Because it will create symbolic link [/opt/mogdb/app] to install path [/opt/mogdb/app_e0e9f58d] in gs_install process with this user.
+```
+
+Run `vi ~/.bashrc` as user `omm` to clear the environment variables and execute the initialization script again.
+
+**Q7: What should I do if an error related to certain dependency software is prompted?**
+
+```
+/opt/software/mogdb/bin/mogdb: error while loading shared libraries: libnsl.so.1: cannot open shared object file: No such file or directory
+no data was returned by command ""/opt/software/mogdb/bin/mogdb" -V"
+The program "mogdb" is needed by gs_initdb but was not found in the
+same directory as "/opt/software/mogdb/bin/gs_initdb".
+Check your installation.
+```
+
+Reinstall the dependency software libnsl*.
+
+<br/>
+
+## Installation FAQs
+
+**Q8: What should I do if it is prompted that the cluster has been installed?**
+
+```bash
+[GAUSS-51400] : Failed to execute the command: source /home/omm/.bashrc;python3 '/opt/mogdb/tool/script/local/CheckInstall.py' -U omm:dbgrp -R /opt/mogdb/app -l /opt/mogdb/mogdb_log/omm/omm/om/gs_local.log -X /opt/software/mogdb/clusterconfig.xml.Error:
+Checking old installation.
+[GAUSS-51806] : The cluster has been installed.
+```
+
+Run `vi ~/.bashrc` to view the environment variables, change `GAUSS_ENV=2` to `GAUSS_ENV=1`, and run the install command again.
+
+**Q9: What should I do if the following error is prompted?**
+
+```bash
+[GAUSS-51400] : Failed to execute the command: source /home/omm/.bashrc;python3 '/opt/mogdb/tool/script/local/CheckInstall.py' -U omm:dbgrp -R /opt/mogdb/app -l /opt/mogdb/mogdb_log/omm/omm/om/gs_local.log -X /opt/software/mogdb/clusterconfig.xml.Error:
+Checking old installation.
+Successfully checked old installation.
+Checking SHA256.
+Successfully checked SHA256.
+Checking kernel parameters.
+Successfully checked kernel parameters.
+Checking directory.
+[GAUSS-50202] : The /opt/mogdb/app_b75b585a must be empty.
+```
+
+Switch to `/opt/mogdb/app_b75b585a` directory as user **root**, run `rm -rf *` to delete all files in the directory, and run the install command again.
+
+**Q10: What should I do if it is prompted that the socket file already exists?**
+
+```bash
+[GAUSS-50200] : The socket file already exists. Port:26000.
+```
+
+You can change the `dataPortBase` value in `clusterconfig.xml` to a port that is available.
+
+**Q11: Which ports need to be enabled during MogDB installation test?**
+
+Ports 26000, 26001, 26003, 26004, and 26005 need to be enabled.
+
+<br/>
+
+## Post-Deployment FAQs
+
+**Failed to start database via `gs_om -t start`: Changed the host name via `hostnamectl set` after standard installation**
+
+**Applicable to:**
+
+* MogDB 1.1.0
+
+* MogDB 2.0.0
+
+* MogDB 2.0.1
+
+* MogDB 2.1.0
+
+* MogDB 2.1.1
+
+* MogDB single node
+
+The solution in this document is for the x86 architecture.
+
+**Symptom:**
+
+After the standard installation is finished (single node), when `hostnamectl set` is run to change the host name, and `gs_om -t start` is run to start the database, the start fails.
+
+For example:
+
+1. Change the host name from `mogdb-kernel-0005` to `www.mogdb.com` by running `hostnamectl set` as user `root`.
+
+   ```bash
+   [root@mogdb-kernel-0005 ~]# hostnamectl
+   Static hostname: mogdb-kernel-0005
+         Icon name: computer-vm
+           Chassis: vm
+        Machine ID: de03a5f3bf5a4b7e9df939c9dc5b428d
+           Boot ID: 828bfbe948ed4de7aff2a059103a0eaa
+    Virtualization: kvm
+    Operating System: CentOS Linux 7 (Core)
+       CPE OS Name: cpe:/o:centos:centos:7
+            Kernel: Linux 3.10.0-1160.15.2.el7.x86_64
+      Architecture: x86-64
+   [root@mogdb-kernel-0005 ~]# id
+   uid=0(root) gid=0(root) groups=0(root)
+   [root@mogdb-kernel-0005 ~]# hostname
+   mogdb-kernel-0005
+   [root@mogdb-kernel-0005 ~]# hostnamectl set-hostname www.mogdb.com
+   ```
+
+2. Run the following command as any user to see if the host name is successfully changed.
+
+   ```bash
+   [root@mogdb-kernel-0005 ~]# hostname
+   www.mogdb.com
+   ```
+
+3. Run the following command as user `omm` to stop the database.
+
+   ```bash
+   [root@mogdb-kernel-0005 ~]# su - omm
+   Last login: Tue Jul 27 11:18:16 CST 2021 on pts/1
+   [omm@www ~]$ gs_ctl stop -D /mogdb/data/db1
+   [2021-07-27 11:19:20.283][32166][][gs_ctl]: gs_ctl stopped ,datadir is /mogdb/data/db1
+   waiting for server to shut down.... done
+   server stopped
+   ```
+
+4. Run the following command as user `omm` to start the database.
+
+   ```bash
+   [omm@www ~]$ gs_om -t start
+
+   Starting cluster.
+   =========================================
+
+   =========================================
+   [GAUSS-53600]: Can not start the database, the cmd is source /home/omm/.bashrc; python3 '/opt/enmo/wisequery/script/local/StartInstance.py' -U omm -R /opt/mogdb/app -t 300 --security-mode=off,  Error:
+   [GAUSS-51400]: Failed to execute the command: source /home/omm/.bashrc; python3 '/opt/enmo/wisequery/script/local/StartInstance.py' -U omm -R /opt/mogdb/app -t 300 --security-mode=off. Error:
+   [FAILURE] mogdb-kernel-0005
+   ```
+
+**Purpose:**
+
+After the standard installation (single node) is finished , when the host name is changed through `modip.py`, and `gs_om -t start` is run to start the command, the database starts successfully.
+
+**Resolution:**
+
+1. Create `modip.py` as user `omm`.
+
+   ```python
+   [omm@www ~]$ cd
+   [omm@www ~]$ pwd
+   /home/omm
+   [omm@www ~]$ vi modip.py
+
+   # -*- coding:utf-8 -*-
+
+   import sys
+   ##sys.path.append(r'$GPHOME/script/')
+   sys.path.append(r'/opt/enmo/wisequery/script/')
+   from gspylib.common.DbClusterInfo import dbClusterInfo
+
+   oldIP = '172.16.0.176'
+   newIP = '172.16.0.176'
+   oldnodename = 'mogdb-kernel-0005'
+   newnodename = 'www.mogdb.com'
+   ##Output file directory
+   tmpDir = r'/home/omm'
+   dbuser = 'omm'
+
+   c1=dbClusterInfo()
+   c1.initFromStaticConfig(dbuser)
+
+   for node in c1.dbNodes:
+       if node.backIps[0] == oldIP:
+           node.backIps[0] = newIP
+       if len(node.virtualIp):
+           if node.virtualIp[0] == oldIP:
+               node.virtualIp[0] = newIP
+       if node.name == oldnodename:
+           node.name = newnodename
+       if node.sshIps[0] == oldIP:
+           node.sshIps[0] = newIP
+       for dn in node.datanodes:
+           if dn.listenIps[0] == oldIP:
+               dn.listenIps[0] = newIP
+           if dn.haIps[0] == oldIP:
+               dn.haIps[0] = newIP
+           for peerdn in dn.peerInstanceInfos:
+               if len(peerdn.peerHAIPs):
+                   if peerdn.peerHAIPs[0] == oldIP:
+                       peerdn.peerHAIPs[0] = newIP
+   for node in c1.dbNodes:
+       staticConfigPath_dn = "%s/cluster_static_config_%s" % (tmpDir, node.name)
+       c1.saveToStaticConfig(staticConfigPath_dn, node.id)
+       print(staticConfigPath_dn)
+   ```
+
+   > **Note：**You need to modify the IP address and host name according to the actual situation. In this example, the IP address is `172.16.0.176`, the old host name is `mogdb-kernel-0005`, and the new host name is `www.mogdb.com`.
+
+2. Run the following command to generate the static configuration file of the cluster.
+
+   ```bash
+   [omm@www ~]$ python3 modip.py
+   ```
+
+   The following output indicates that the command is run successfully.
+
+   ```bash
+   /home/omm/cluster_static_config_www.mogdb.com
+   ```
+
+3. Run the following command to replace the original file.
+
+   ```bash
+   [omm@www ~]$ mv /opt/mogdb/app/bin/cluster_static_config /opt/mogdb/app/bin/cluster_static_config_mogdb.com
+
+   [omm@www ~]$ cp /home/omm/cluster_static_config_www.mogdb.com /opt/mogdb/app/bin/cluster_static_config
+   ```
+
+4. Run the following command to start the database.
+
+   ```bash
+   [omm@www ~]$ gs_om -t start
+
+   Starting cluster.
+   =========================================
+
+   [SUCCESS] www.mogdb.com
+
+   2021-07-26 16:20:42.938 60fe7056.1 [unknown] 139667408496384 [unknown] 0 dn_6001 01000  0 [BACKEND] WARNING: could not create any HA TCP/IP sockets
+   =========================================
+
+   Successfully started.
+   ```
diff --git a/product/en/docs-mogdb/v3.0/faqs/high-availability-faqs.md b/product/en/docs-mogdb/v3.0/faqs/high-availability-faqs.md
new file mode 100644
index 0000000000000000000000000000000000000000..a1b3b34ff9d4e53440827b394e70cf796f155fc4
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/faqs/high-availability-faqs.md
@@ -0,0 +1,28 @@
+---
+title: HA FAQs
+summary: HA FAQs
+author: Guo Huan
+date: 2021-09-26
+---
+
+# HA FAQs
+
+**Q1: What is the function of MogHA?**
+
+MogHA is an independent HA suite. It can handle multiple failures such as server or instance breakdown, thereby lowering the downtime from minutes to seconds.
+
+**Q2: What is the HA architecture of MogDB?**
+
+MogHA supports one primary database and at least one standby database or a maximum of eight standby databases (which is kept pace with openGauss of the latest version).
+
+The architecture of one primary and multiple standby databases is optimized based on openGauss, in which RPO can reach zero and RTO is less than 10s. In other word, when the primary instance fails, the standby instance can take over services from the faulty primary instance within 10s, ensuring zero data loss.
+
+**Q3：What is the common deployment architecture of MogDB?**
+
+MogDB supports three types of nodes, including primary, standby, and cascaded nodes. The maximum number of standby and cascaded nodes totals eight, one primary node, four standby nodes, and four cascaded nodes, or one primary node and eight standby nodes. The following figure shows the production deployment architecture from one customer, including one primary node, five standby nodes, and one cascaded node.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/faqs/high-availability-faqs-en-1.png)
+
+**Q4: How is RPO/RTO of MogDB achieved? Can HA reach 99.999%?**
+
+RPO = 0, RTO < 10s, and SLA = 99.999%
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/faqs/migration-faqs.md b/product/en/docs-mogdb/v3.0/faqs/migration-faqs.md
new file mode 100644
index 0000000000000000000000000000000000000000..c13ce53a0e8da4fb86cbffeae4ab66a7de803b38
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/faqs/migration-faqs.md
@@ -0,0 +1,19 @@
+---
+title: Migration FAQs
+summary: Migration FAQs
+author: Guo Huan
+date: 2021-09-26
+---
+
+**Q1: Which databases can be migrated to MogDB currently?**
+
+With the heterogeneous database migration tool MTK developed by ENMOTECH, you can migrate data structures and full data of the following databases to MogDB at a high speed. 
+
+* Oracle
+* MySQL
+* DB2 
+* openGauss
+* PostgreSQL (Not supported for stored procedures)
+* SQL Server (Not supported for partitioned tables)
+
+For more information, visit [MTK official document](http://docs.mogdb.io:8000/zh/mtk/v2.0/overview).
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/faqs/product-faqs.md b/product/en/docs-mogdb/v3.0/faqs/product-faqs.md
new file mode 100644
index 0000000000000000000000000000000000000000..2b609625ebaaef93695b195ee7bb083523f076b7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/faqs/product-faqs.md
@@ -0,0 +1,165 @@
+---
+title: Product FAQs
+summary: Product FAQs
+author: Guo Huan
+date: 2021-09-26
+---
+
+# Product FAQs
+
+**Q1. What is the relationship between ultimate RTO, parallel recovery, and standby node readability?**
+
+The configurations of ultimate RTO, parallel recovery, and standby node readability are as follows:
+
+- Ultimate RTO: **recovery_parse_workers** indicates the number of Xlog threads parsed during parallel recovery. **recovery_parallelism** indicates the actual number of Xlog threads during parallel recovery. When **recovery_parse_workers** is greater than 1, ultimate RTO recovery is implemented. Only when both **recovery_parse_workers** and **recovery_parallelism** are set to a value greater than 1, can parallel recovery be implemented.
+- Parallel recovery: **recovery_max_workers** specifies the maximum number of threads for parallel recovery. **recovery_parallelism** specifies the actual number of threads for parallel recovery. If the value of **recovery_max_workers** is greater than 1, parallel recovery is configured. However, only when **recovery_max_workers** and **recovery_parallelism** are set to a value greater than 1, can parallel recovery be implemented.
+- Standby node readability: **hot_standby** indicates that a hot standby node can be read during recovery. If the value of **hot_standby** is **true**, the standby node can be read.
+
+Parallel recovery is a file-level parallel redo, and the ultimate RTO is a data block-level parallel recovery. Parallel recovery is compatible with standby node readability, but ultimate RTO is incompatible with standby node readability. During configuration of preceding parameters, code check (with **CheckExtremeRtoGUCConflicts**) is performed. If **recovery_parse_workers** is set to a value greater than 1 and **hot_standby** is set to **true**, an error will be reported.
+
+**Q2. How can I select a candidate primary node for primary/standby switchover when the standby node cannot be read in the ultimate RTO scenario?**
+
+The standby node cannot be read only when the RTO is ultimate. In serial recovery and parallel recovery, the standby node can be read. If the ultimate RTO is used, only the synchronous mode can be configured, and a node is selected randomly as the primary. After the synchronous mode is used, the data on all nodes is the same.
+
+**Q3. What is the function of the template database? Which tables are contained in the template database?**
+
+The template database provides a method of quickly creating a database. When creating a database, you can specify the **TEMPLATE** parameter to create a database by copying a template database.
+
+The template database does not contain any user table. You can view the attributes of the template database in the **PG_DATABASE** system catalog.
+
+**Q4. When MogDB supports physical replication, does the standby node replay logs by page in parallel mode?**
+
+MogDB supports two parallel recovery modes: file-level recovery and page-level recovery.
+
+**Q5: Is MogDB a distributed database?**
+
+No. MogDB supports only primary/standby deployment in standalone mode currently.
+
+MogDB uses the distributed middleware pgpool-II or Shardingsphere to deal with sharding and non-native distributed requests.
+
+**Q6: What are MogDB application scenarios?**
+
+MogDB application scenarios are similar to those of postgreSQL. MogDB can be applied to e-commerce, finance, O2O, and telecom CRM/billing which feature high concurrency and large data volume.
+
+Application scenarios include transactional application scenarios which focus on online transaction processing and IoT application scenarios which focus on industrial monitoring, remote control, smart cities, smart homes, and IoV.
+
+MogDB provides not only basic functions of relational databases but enhanced HA and monitoring functions for enterprise application scenarios and features.
+
+**Q7: Can MogDB be deployed on x86 servers? What are the recommended hardware configurations?**
+
+MogDB can be installed on x86 servers (AMD64 architecture). For details, see [Hardware Requirements](2-environment-requirement)。
+
+**Q8: Can MogDB be deployed on KUNPENG servers? What are the recommended hardware configurations?**
+
+MogDB can be deployed on KUNPENG servers (ARM architecture) with the recommended hardware configurations the same as those of x86 servers.
+
+Actually, the performance of MogDB on KUNPENG servers is better than that on x86 servers. Therefore, you are advised to choose domestic chip servers.
+
+**Q9: Is MogDB free? How is MogDB charged?**
+
+MogDB is not free (openGauss is free). MogDB is designed for enterprise users and is not open to individuals. For details about the pricing rules, please contact the sales personnel for consultation.
+
+**Q10: What does the database compatibility setting mean during MogDB database creation? What is done to data types for being compatible with different databases?**
+
+During MogDB database creation, you can set the DBCOMPATIBILITY parameter to make MogDB compatible with different databases. However, compatibility here refers to only data storage structure compatibility and does not include SQL syntax compatibility.
+
+Currently, you can configure MogDB compatible with Oracle, MySQL, or PostgreSQL. The default setting is that MogDB is compatible with Oracle.
+
+- For the compatibility type of Oracle, the database considers an empty string as null and replace the data type **DATE** with **TIMESTAMP(0) WITHOUT TIME ZONE**.
+
+- For the compatibility type of MySQL, when a string is converted to an integer type, if an illegal value is entered, it will be converted to 0. However, for other compatibility types, an error will be reported.
+
+- For the compatibility type of PostgreSQL, CHAR and VARCHAR use character as the string unit. For other compatibility types, byte is used as the string unit.
+
+  For example, as for UTF-8 character set, CHAR(3) can hold 3 Chinese characters in the compatibility type of PG but only one Chinese character in the other compatibility types.
+
+If you need to create a database compatible with PostgreSQL, the syntax format is "CREATE DATABASE dbname DBCOMPATIBILITY='PG';."
+
+Parameter description:
+
+DBCOMPATIBILITY [ = ] compatibility_type
+
+Specifies the type of the database to be compatible with.
+
+Value range: **A**, **B**, **C**, and **PG**
+
+**A** indicates that MogDB is compatible with Oracle. **B** indicates that MogDB is compatible with MySQL. **C** indicates that MogDB is compatible with Teradata. **PG** indicates that MogDB is compatible with PostgreSQL. However, **C** is not supported currently. Therefore, the values **A**, **B**, and **PG** are commonly used.
+
+**Q11: What are major improvement of MogDB based on traditional PostgreSQL? What are advantages of MogDB?**
+
+For technical implementation:
+
+- most_available_sync (If the synchronous standby node fails, the services of the primary node will not be interrupted.)
+- XIDs that cannot be exhausted
+- Physical replication slot automatically created in the stream replication environment
+- Incremental checkpoints
+- Double write
+
+For ecological consideration:
+
+- Modified based on openGauss and dependent on the Huawei R&D team
+
+- Completely autonomous and controllable
+
+- Integrated ecological tools, including PTK, MTK, RWT, MIT, SCA, and BRM
+
+  Additionally, part of tools are being developed.
+
+- Active community and rich materials
+
+**Q12: What is the MogDB performance in terms of the Intel processor?**
+
+| **Test Item**                                            | **Data Volume** | Number of Concurrent Requests | **Average CPU Usage** | **IOPS** | **IO** Delay | **Number of WALs** | **tpmC** | **Test Duration** |
+| -------------------------------------------------------- | --------------- | ----------------------------- | --------------------- | -------- | ------------ | ------------------ | -------- | ----------------- |
+| Single node                                              | 100 GB          | 500                           | 29.39%                | 6.50K    | 1.94 ms      | 3974               | 520896.3 | 10 minutes        |
+| One primary, one synchronous, and one asynchronous nodes | 100 GB          | 500                           | 30.4%                 | 5.31K    | 453.2 us     | 3944               | 519993.5 | 10 minutes        |
+| One primary and two synchronous nodes                    | 100 GB          | 500                           | 26.35%                | 7.66K    | 531.9 us     | 3535               | 480842.2 | 10 minutes        |
+
+**Q13: Which OSs can MogDB be deployed on? Is there any compatibility problems?**
+
+MogDB can be deployed on the following OSs:
+
+- ARM:
+  - openEuler 20.3LTS (recommended)
+  - Kylin OS V10
+- x86:
+  - openEuler 20.3LTS
+  - CentOS 7.6
+  - Asianux 7.6
+
+Different OSs and CPU architectures have compatibility problems.
+
+**Q14: What are distinctions between MogDB and Oracle in implementation of MVCC?**
+
+Oracle is based on SCN, stores data in data blocks, uses undo segments in a circular fashion, and supports the flashback function. However, there exists a large number of transaction rollbacks and too old snapshots (ORA-01555).
+MogDB is based on transaction ID (TXID), supports row-level storage, does not need undo segments, and supports instantaneous rollback of large transactions. However, there exists block page space and performance overhead problems.
+
+**Q15: What are advantages of MogDB incremental checkpoints?**
+
+Incremental checkpoints can refresh dirty pages in small batches, in stages, or rolling mode, update LSN information, and reclaim unwanted Xlogs, thereby preventing the performance from being affected by the impact on disks caused by fully refreshing dirty pages.
+
+**Q16: How does MogDB deal with XID exhaustion occurred in native PostgreSQL?**
+
+MogDB changes transaction ID from int32 to int64. 64-bit XIDs cannot be exhausted for ever. Expired XIDs also need to be frozen but the risk of XID rollback failure will never occur.
+
+**Q17: What are distinctions between MogDB AND Oracle in user permission?**
+
+Oracle schema and user are the same concept. But they are not the same in MogDB. In MogDB, all objects created by a user are under a specified schema (or namespace). Other users may have or may not have permission to access these objects or even they cannot create objects in the schema. User (or role) are global objects and not defined in a database but in an instance. Schema is created in a specified database which includes database objects.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/faqs/product-faqs-1.png)
+
+**Q18: What is the difference between double write in MogDB and second commit in MySQL?**
+
+The implementation principle of double write is the same as that of second commit in MySQL. It aims to maintain data consistency and avoid data loss due to damaged data blocks so that data can be recovered.
+
+**Q19: What are distinctions between MogDB primary/standby and Oracle Data Guard?**
+
+The standby database can receive query requests to share the pressure with the primary database in both MogDB and Oracle.
+
+**Q20: Is concurrent physical backup supported? Can physical backup be performed remotely? How can data files be transmitted to the target machine during remote physical backup?**
+
+gs_probackup supports concurrent physical backup. Physical backup can be performed remotely to transmit data files to the target machine by using the archive file or stream protocol.
+
+**Q21: What is the difference when xlog-method is set to stream or fetch during physical backup?**
+
+**xlog-method** indicates the Xlog transmission mode. If you do not set the parameter, the default value is **stream**. The **stream** mode includes all WALs generated during backup. The **fetch** mode collects WALs at the end of backup. Therefore, the value of **wal_keep_segments** needs to be set high enough so that logs will not be removed by the end of the backup. If logs have been removed during log transmission, the backup will fail and become unavailable. The **stream** mode transmits WALs during backup creation, which will start a second connection to a server and transmit WALs during backup. Therefore, the **stream** mode uses a maximum of two connections determined by the **max_wal_senders** parameter. The **stream** mode does not need to store additional WALs only when the client can receive WALs constantly.
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/faqs/upgrade-faqs.md b/product/en/docs-mogdb/v3.0/faqs/upgrade-faqs.md
new file mode 100644
index 0000000000000000000000000000000000000000..962e96b3ce9988e0f614936775b387aeacc4a2ec
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/faqs/upgrade-faqs.md
@@ -0,0 +1,8 @@
+---
+title: Upgrade FAQs
+summary: Upgrade FAQs
+author: Guo Huan
+date: 2021-09-26
+---
+
+In preparing……
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/glossary.md b/product/en/docs-mogdb/v3.0/glossary.md
new file mode 100644
index 0000000000000000000000000000000000000000..d1e44e86b21a9b9bfbb842d393496bfe6fc879d9
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/glossary.md
@@ -0,0 +1,157 @@
+---
+title: Glossary
+summary: Glossary
+author: Guo Huan
+date: 2021-03-04
+---
+
+# Glossary
+
+**Table 1** Glossary
+
+| **Terms**                         | **Description**                                              |
+| :-------------------------------- | :----------------------------------------------------------- |
+| **A - E**                         |                                                              |
+| ACID                              | Atomicity, consistency, isolation, and durability (ACID) is a set of properties that guarantee that transactions are processed reliably in a database management system (DBMS). |
+| AZ                                | Acronym for available zone which usually refers to an equipment room. |
+| bgwriter                          | A background write thread created when the database starts. The thread is used to flush dirty pages out of the database to a permanent device (such as a disk). |
+| bit                               | Short for binary digit. The smallest unit of information handled by a computer. One bit expresses a 1 or a 0 in a binary numeral, or a true or false logical condition, and is represented physically by an element such as a high or low voltage at one point in a circuit or a small spot on a disk magnetized one way or the other. A single bit conveys little information a human would consider meaningful. A group of 8 bits, however, makes up a byte, which can be used to represent many types of information, such as a letter of the alphabet, a decimal digit, or other character. |
+| bloom filter                      | Bloom filter is a space-efficient binary vectorized data structure, conceived by Burton Howard Bloom in 1970, that is used to test whether an element is a member of a set. False positive matches are possible, but false negatives are not. In other words, a query returns either "possibly in set (possible error)" or "definitely not in set". In the cases, Bloom filter sacrificed the accuracy for time and space. |
+| CEK                               | Acronym for column encryption key.                           |
+| CIDR                              | Acronym for classless inter-domain routing. Whereas classical network design for IPv4 sized the network prefix as one or more 8-bit groups, resulting in the blocks of Class A (8-bit), B (16-bit), or C (24-bit) addresses, CIDR allocates address space on any address bit boundary. A CIDR address is in the format of *IP address***/***Number of bits in a network ID*. For example, in **192.168.23.35⁄21**, **21** indicates that the first 21 bits are the network prefix and others are the host ID. |
+| CLI                               | Acronym for command-line interface. A means of communication between a program and its user, based solely on textual input and output. Commands are input with the help of a keyboard or similar device and are interpreted and executed by the program. Results are output as text or graphics to the terminal. |
+| CMK                               | Acronym for client master key in the full encryption scenario. |
+| CU                                | Acronym for compression unit. It is the smallest storage unit in a column-store table. |
+| core file                         | A file that is created for further analysis when memory overwriting, assertion failures, or access to invalid memory occurs in a program, causing a process to fail.A core file stores memory dump data, and supports binary mode and specified ports. The name of a core file consists of the word "core" and the OS process ID.The core file is available regardless of the type of platform. |
+| core dump                         | A core dump, memory dump, or system dump consists of the recorded state of the working memory of a computer program at a specific time, generally when the program stops abnormally. In practice, other key pieces of program state are usually dumped at the same time, including the processor registers, which may include the program counter and stack pointer, memory management information, and other processor and OS flags and information. Core dumps are often used to assist in diagnosing and debugging errors in computer programs. |
+| DBA                               | Acronym for database administrator who instructs or executes database maintenance operations. |
+| DBLINK                            | An object of the path from one database to another database. Using DBLINK, you can query a remote database object. |
+| DBMS                              | Acronym for database management system. It is a piece of system management software that allows users to access information in a database. It is a collection of programs that allows users to access, manage, and query data in a database. A DBMS can be classified as memory DBMS or disk DBMS based on the location of the data. |
+| DCL                               | Acronym for data control language.                           |
+| DDL                               | Acronym for data definition language.                        |
+| DEK                               | Acronym for data encryption key.                             |
+| DML                               | Acronym for data manipulation language.                      |
+| backup                            | A backup copy or an act of creating a backup refers to copying and archiving computer data for purposes of recovery in case the original copy of data is lost. |
+| backup and restoration            | A collection of concepts, procedures, and strategies to prevent data loss caused by invalid media or misoperations. |
+| standby node                      | A node in the openGauss primary/standby solution. It functions as a backup of the primary node. If the primary node fails, the standby node is promoted to primary, ensuring uninterrupted data services. |
+| crash                             | A crash (or system breakdown) is an event that a computer or program, such as a software application or an operating system, fails to function correctly. If a program experiences a crash, it often automatically exits. The program responsible may appear to freeze or hang until a crash reporting service reports the crash and any details relating to it. If the program is a critical part of the operating system, the entire system may crash or hang, often resulting in a kernel panic or fatal system error. |
+| coding                            | Coding is representing data and information using code so that it can be processed and analyzed by a computer. Characters, digits, and other objects can be converted into digital code, or information and data can be converted into the required electrical pulse signals based on predefined rules. |
+| encoding technology               | A technology that presents data using a specific set of characters, which can be identified by computer hardware and software. |
+| table                             | A table consists of columns and rows. Each column is referred to as a field. The value in each field represents a data type. For example, if a table contains three fields **Name**, **City**, and **State**, it has three columns **Name**, **City**, and **State**. In every row of the table, the **Name** column contains a name, the **City** column contains a city, and the **State** column contains a state. |
+| tablespace                        | A tablespace is a logical storage structure that contains tables, indexes, large objects, and long data. A tablespace provides an abstract layer between physical data and logical data, and provides storage space for all database objects. When you create an object, you can specify which tablespace it belongs to. |
+| concurrency control               | A DBMS service that ensures data integrity when multiple transactions are concurrently executed in a multi-user environment. In a multi-threaded openGauss environment, concurrency control ensures that database operations are safe and all database transactions remain consistent at any given time. |
+| query                             | A request sent to the database with the purpose of updating, modifying, querying, or deleting information. |
+| query operator                    | An iterator or a query tree node, which is a basic unit for the execution of a query. Execution of a query can be split into one or more query operators. Common query operators include scan, join, and aggregation. |
+| durability                        | One of the ACID properties of a database transaction. After a transaction is complete, the changes made by the transaction to the database are permanently stored in the database and will not be rolled back. |
+| stored procedure                  | A collection of SQL statements compiled and stored on a server in a large database system that can be executed using an interface (specifying the procedure name and parameters if any) to perform a specific operation. |
+| operating system                  | An operating system (OS) is loaded by a boot program to a computer to manage other programs in the computer. Other programs are called applications or application programs. |
+| Blob                              | Acronym for binary large object, a collection of binary data stored in a database. Blobs are typically videos, audio or other multimedia objects. |
+| segment                           | A segment is a set of extents in a database. The smallest space scope of a database is an extent, which consists of data blocks. One or more segments comprise a tablespace. |
+| **F - J**                         |                                                              |
+| failover                          | Automatic switchover from a faulty primary node to its standby node. Reversely, automatic switchback from the standby node to the primary node is called failback. |
+| FDW                               | Acronym for foreign data wrapper. It is an SQL interface provided by openGauss. It is used to access big data objects stored in remote data so that DBAs can integrate data from unrelated data sources and store them in public schema in the database. |
+| freeze                            | An operation automatically performed by the AutoVacuum Worker process when transaction IDs are exhausted. openGauss records transaction IDs in the row heading. When a transaction reads a row, the transaction ID in the row heading and the actual transaction ID are compared to determine whether this row is explicit. Transaction IDs are integers containing no symbols. If exhausted, transaction IDs are re-calculated outside of the integer range, causing the explicit rows to become implicit. To prevent such a problem, the freeze operation marks a transaction ID as a special ID. Rows marked with these special transaction IDs are explicit to all transactions. |
+| GDB                               | Acronym for GNU debugger which is used to monitor the internal situation of a running program or rewind a crashed program to see what happened. GDB can perform the following operations (strengthening PDK functions) to detect bugs:Starts a program and specifies anything that might affect its behavior.Stops a program under a specific condition.Checks what happens when a program stops.Modifies the program content to rectify the fault and proceeds with the next one. |
+| GIN index                         | Acronym for generalized inverted index. It is used for handling cases where the items to be indexed are composite values, and the queries to be handled by the index need to search for element values that appear within the composite items. |
+| GNU                               | The GNU Project was publicly announced on September 27, 1983 by Richard Stallman, aiming at building an OS composed wholly of free software. GNU is a recursive acronym for "GNU's Not Unix!". Stallman announced that GNU should be pronounced as Guh-NOO. Unix is a widely used commercial OS. GNU's design is Unix-like, but GNU differs from Unix by being free software. |
+| gsql                              | openGauss interaction terminal. It enables you to interactively enter and issue queries to openGauss, and view the query results. Queries can also be entered from files. In addition, **gsql** supports many meta commands and shell-like commands, allowing you to conveniently compile scripts and automate tasks. |
+| GUC                               | Acronym for grand unified configuration which includes parameters for running databases, and the values of which affect database system behavior. |
+| HA                                | Acronym for high availability which helps to minimize the duration of service interruptions caused by routine maintenance (planned) or sudden system breakdowns (unplanned), improving the system and application usability. |
+| HBA                               | Acronym for host-based authentication which allows hosts to authenticate on behalf of all or some of that particular host's users. Those accounts can be all of the accounts on a system or a subset designated by the **Match** directive. This type of authentication can be useful for managing computing and other fairly homogenous pools of machines. In all, three files on the server and one file on the client must be modified to prepare for host-based authentication. |
+| IV                                | Acronym for initialization vector. An IV is a block used for random encryption in many encryption modes. Therefore, different ciphertexts may be generated by using the same plaintext and key. |
+| server                            | A combination of hardware and software designed for providing clients with services. This word alone refers to a computer running a server OS, or software or dedicated hardware providing services. |
+| isolation                         | One of the ACID properties of a database transaction. Isolation means that operations and data used in a transaction are isolated from those in other concurrent transactions. Concurrent transactions are independent of each other. |
+| relational database               | A database that conforms to the relational model. It processes data using mathematical concepts and methods such as the set algebra. |
+| archive thread                    | A thread started when the archive function is enabled on a database. The thread is used to archive database logs to a specified path. |
+| failover                          | Automatic substitution of a functionally equivalent system component for a failed one. The system component can be a processor, server, network, or database. |
+| environment variable              | Environment variables are used to define part of the environment in which a process runs. For example, it can be used to define a home directory, command search path, terminal being used, or the current time zone. |
+| checkpoint                        | A mechanism that stores data at a certain time in the database memory to disks. openGauss periodically stores the data of committed transactions and data of uncommitted transactions to disks. The data and redo logs can be used for database restoration if a database restarts or breaks down. |
+| encryption                        | A function hiding information content during data transmission to prevent the unauthorized use of the information. |
+| node                              | Database nodes (or nodes) are physical and virtual severs that make up the openGauss database environment. |
+| error correction                  | A technique that automatically detects and corrects errors in software and data flows to improve system stability and reliability. |
+| process                           | An instance of a computer program that is being executed. A process consists of one or more threads. A process cannot use a thread occupied by another process. |
+| PITR                              | Acronym for point-in-time recovery, a backup and restoration feature of openGauss. Data can be restored to a specified point in time if backup data and WAL logs are normal. |
+| record                            | In a relational database, a record corresponds to data in each row of a table. |
+| **K - O**                         |                                                              |
+| KMC                               | Acronym for key management component.                        |
+| KMS                               | Acronym for key management service.                          |
+| KSF                               | Acronym for key store file.                                  |
+| logical replication               | Data synchronization mode between primary and standby database nodes or between two databases. Different from physical replication which replays physical logs, logical replication transfers logical logs between two databases or synchronizes data through SQL statements in logical logs. |
+| logical log                       | Logs recording database changes made through SQL statements. Generally, the changes are logged at the row level. Logical logs are different from physical logs that record changes of physical pages. |
+| logical decoding                  | Logic decoding is a process of extracting all permanent changes in database tables into a clear and easy-to-understand format by decoding Xlogs. |
+| logical replication slot          | In a logical replication process, logic replication slots are used to prevent Xlogs from being reclaimed by the system or **VACCUM**. A logical replication slot in openGauss is an object that records logical decoding positions. It can be created, deleted, read, and pushed by invoking SQL functions. |
+| MVCC                              | Acronym for multi-version concurrency control. It is a protocol that allows a tuple to have multiple versions, on which different query operations can be performed. One advantage is that read and write operations do not conflict. |
+| NameNode                          | NameNode is the centerpiece of an HDFS, managing the namespace of the file system and client access to files. |
+| OM                                | Acronym for operations management. It provides management interfaces and tools for routine maintenance and configuration management of the database. |
+| client                            | A computer or program that connects to or requests the services of another computer or program. |
+| free space management             | A mechanism for managing free space in a table. This mechanism enables the database system to record free space in each table and establish an easy-to-find data structure, accelerating operations (such as INSERT) performed on the free space. |
+| junk tuple                        | A tuple that is deleted using the **DELETE** and **UPDATE** statements. When deleting a tuple, openGauss only marks the tuples that are to be cleared. The **VACUUM** thread will then periodically clear these junk tuples. |
+| column                            | An equivalent concept of field. A database table consists of one or more columns. |
+| logical node                      | Multiple logical nodes can be installed on the same physical node. A logical node is a database instance. |
+| schema                            | Collection of database objects, including logical structures, such as tables, views, sequences, stored procedures, synonyms, indexes, and database links. |
+| schema file                       | An SQL file that determines the database structure.          |
+| **P - T**                         |                                                              |
+| page                              | Smallest memory unit for row storage in the relational object structure in openGauss. The default size of a page is 8 KB. |
+| Paxos                             | Distributed consistency protocol.                            |
+| PostgreSQL                        | An open-source relational DBMS developed by volunteers all over the world. PostgreSQL is not controlled by any companies or individuals. Its source code can be used for free. |
+| postmaster                        | A thread started when the database service is started. It listens on connection requests from other nodes in the database or from clients.After receiving and accepting a connection request from the standby node, the primary node creates a WAL sender thread to interact with the standby node. |
+| RHEL                              | Acronym for Red Hat Enterprise Linux.                        |
+| redo log                          | A log that records operations on the database. Redo logs contain the information required for performing these operations again. If a database is faulty, redo logs can be used to restore the database to its pre-fault state. |
+| RK                                | Acronym for root key.                                        |
+| SCTP                              | Acronym for stream control transmission protocol. It is a transport-layer protocol defined by Internet Engineering Task Force (IETF) in 2000. The protocol ensures the reliability of datagram transport based on unreliable service transmission protocols by transferring SCN narrowband signaling over IP network. |
+| savepoint                         | A savepoint marks the end of a sub-transaction (also known as a nested transaction) in a relational DBMS. The process of a long transaction can be divided into several parts. After a part is successfully executed, a savepoint will be created. If later execution fails, the transaction will be rolled back to the savepoint instead of being totally rolled back. This is helpful for recovering database applications from complicated errors. If an error occurs in a multi-statement transaction, the application can be restored by rolling back to the savepoint without terminating the entire transaction. |
+| session                           | If a database receives a connection request from an application, a task is created for the connection. Sessions are managed by the session manager. They execute initial tasks and perform all user operations. |
+| SMP                               | Acronym for symmetric multiprocessing. A group of processors (multiple CPUs) is integrated on a computer. These CPUs share the memory subsystem and bus structure. The OS must support multitasking and multithreading to ensure an SMP system achieves high performance. In databases, SMP means to concurrently execute queries using the multi-thread technology, efficiently using all CPU resources and improving query performance. |
+| SQL                               | Acronym for structured query language. A standard database query language, consisting of data definition language (DDL), data manipulation language (DML), and data control language (DCL). |
+| SSL                               | Acronym for secure sockets layer. It is a network security protocol introduced by Netscape. It is based on the TCP/IP and uses public key technology. SSL supports a wide range of networks and provides three basic security services, all of which use the public key technology. SSL ensures the security of service communication through the network by establishing a secure connection between a client and a server and then being able to securely send any data through this connection. |
+| oversubscription ratio            | The ratio of downlink bandwidth to uplink bandwidth of a switch. A high oversubscription ratio indicates a highly oversubscribed traffic environment and severe packet loss. |
+| Table Access Method               | The table access method layer decouples the execution engine from the storage engine to implement the pluggable capability of the storage engine. |
+| TCP                               | Acronym for transmission control protocol. It splits data into packets which are sent through the Internet protocol (IP), and checks and reassembles packets received through IP to obtain original information. TCP is a connection-oriented, reliable protocol that ensures information correctness in transmission. |
+| trace                             | A specialized use of logging to record information about the way a program is executed. Programmers use the information for debugging. System administrators and technical support personnel can diagnose common problems by using software monitoring tools and based on this information. |
+| strong consistency                | A query cannot see any instantaneous intermediate state of a transaction. |
+| full backup                       | Backup of the whole database.                                |
+| full synchronization              | A data synchronization mechanism specified in the openGauss primary/standby solution, which is used to synchronize all data from the primary node to a standby node. |
+| log file                          | A file containing a record of to activities made in a computer. |
+| transaction                       | A logical unit of work performed within a database management system against a database. A transaction consists of a limited database operation sequence, and must have ACID features. |
+| data                              | A representation of facts or directives for manual or automatic communication, explanation, or processing. Data includes constants, variables, arrays, and strings. |
+| data partition                    | The action of dividing a table into parts (partitions) whose data does not overlap within a database instance. Tables can be partitioned by range, where the target storage location is mapped based on the range of the values in the column that is specified in the tuple. |
+| database                          | A collection of data that is stored together and can be accessed, managed, and updated. Data in a view in the database can be classified into the following types: numerals, full text, digits, and images. |
+| database instance                 | A database instance consists of a process in openGauss and files controlled by the process. openGauss allows multiple database instances to be installed on one physical node. A database instance is also called a logical node. |
+| database primary/standby solution | openGauss provides a highly reliable HA solution. In this solution, each openGauss is called a primary or standby node. At the same time, only one openGauss is identified as the primary node. When the primary/standby system is deployed for the first time, the primary node performs full synchronization on the standby node, and then performs incremental synchronization on the standby node. When the primary/standby system is running, the primary node can receive data read and write operation requests and the standby node only synchronize logs. |
+| database file                     | A binary file that stores user data and the data inside the database system. |
+| data dictionary                   | A read-only collection of database tables and views containing reference information about the database. The information includes database design information, stored procedure information, user rights, user statistics, database process information, database increase statistics, and database performance statistics. |
+| deadlock                          | A situation where different transactions are unable to proceed, because each holds a lock that the other needs. |
+| index                             | An ordered data structure in DBMS to help quickly query and update data in database tables. |
+| statistics                        | Information that is automatically collected by databases, including table-level information (number of tuples and number of pages) and column-level information (column value range distribution histogram). Statistics in databases are used to estimate the cost of query plans to find a plan with the lowest cost. |
+| stop word                         | In computing, stop words are words which are filtered out before or after processing of natural language data (text), saving storage space and improving search efficiency. |
+| **U - Z**                         |                                                              |
+| Ustore                            | Alias for the in-place update storage engine which solves the problems of space expansion and large tuples of the Append update storage engine. The design of efficient rollback segments is the basis of the in-place update storage engine. |
+| Undo Record                       | An undo record can be inserted, queried, and organized. It connects to the ustore through the northbound interface and connects to the buffer pool through the southbound interface. |
+| Undo Space                        | Manages physical resources of undo records, including adding and deleting undo files. |
+| Undo Zone                         | Be bound to service threads and manages the undo logical resources of each service thread. |
+| TransactionSlot                   | Records undo records by transaction granularity for transaction rollback and undo record recycling. |
+| TIMECAPSULE                       | Flashback keyword. After the flashback technology is used, it takes only seconds to restore the submitted data before the database is modified. The restoration time is irrelevant to the database size. |
+| RECYCLE BIN                       | After the recycle bin function is enabled, DROP TABLE can move a table and its sub-objects to the recycle bin. |
+| PURGE                             | Clears objects in the recycle bin.                           |
+| VACUUM                            | A thread that is periodically started by a database to remove junk tuples. Multiple **VACUUM** threads can be started concurrently by setting a parameter. |
+| verbose                           | A verbose option specifies the information to be displayed.  |
+| WAL                               | Acronym for write-ahead logging, a standard method for logging a transaction. Corresponding logs must be written into a permanent device before a data file (carrier for a table and index) is modified. |
+| WAL receiver                      | A thread created by a standby node during database replication. The thread is used to receive data and commands from the primary node and to tell the primary node that the data and commands have been acknowledged. Only one WAL receiver thread can run on one standby node. |
+| WAL sender                        | A thread created on the primary node when the primary node has received a connection request from a standby node during database replication. This thread is used to send data and commands to the standby node and to receive responses from the standby node. Multiple WAL sender threads may run on one primary node. Each WAL sender thread corresponds to a connection request initiated by a standby node. |
+| WAL writer                        | A thread for writing redo logs that are created when a database is started. This thread is used to write logs in the memory to a permanent device, such as a disk. |
+| Xlog                              | A transaction log. A logical node can have only one .xlog file. |
+| xDR                               | The x detail record is a general term that refers to call detail records (CDRs), user flow data records (UFDRs), transaction detail records (TDRs), and statistics detail records (SDRs) on the user and signaling planes. |
+| physical node                     | A physical machine.                                          |
+| system catalog                    | A system catalog stores meta information about a database, including user tables, indexes, columns, functions, and data types. |
+| pushdown                          | In openGauss, a primary database node can send a query plan to multiple DNs for parallel execution. This behavior is called pushdown. It achieves better query performance than extracting data to a primary database node for query. |
+| compression                       | Data compression, source coding, or bit-rate reduction involves encoding information that uses fewer bits than the original representation. Compression can be either lossy or lossless. Lossless compression reduces bits by identifying and eliminating statistical redundancy. No information is lost in lossless compression. Lossy compression reduces bits by identifying and removing less noticeable information. The process of reducing the size of a data file is commonly referred as data compression, although its formal name is source coding (coding done at the source of the data, before it is stored or transmitted). |
+| consistency                       | One of the ACID properties of a database transaction. Data in the database must comply with integrity constraints. |
+| metadata                          | Data that provides information about other data. Metadata describes the source, size, format, or other characteristics of data. In the data field, metadata helps to explain the content of a data warehouse. |
+| atomicity                         | One of the ACID properties of a database transaction. A transaction is composed of an indivisible unit of work. Operations performed in a transaction must be all finished or have not been performed. If an error occurs during transaction execution, the transaction is rolled back to the state when it was not performed. |
+| dirty page                        | A page that has been modified, where the changes are not yet written to a permanent device. |
+| incremental backup                | Incremental backup only saves data changed since the last valid backup. |
+| incremental synchronization       | A data synchronization mechanism in the openGauss primary/standby solution, which is used to synchronize inconsistent data from the primary node to a standby node. |
+| primary node                      | A node that allows read and write operations and works with all standby nodes in the openGauss primary/standby system. At the same time, only one node in the primary/standby system is identified as the primary node. |
+| subject term                      | A standardized word or phrase that describes the subject of an article. |
+| dump file                         | A specific type of trace file. A dump is typically a one-time output of diagnostic data in response to an event, whereas a trace tends to be continuous output of diagnostic data. |
+| minimum restoration point         | A method used by openGauss to ensure data consistency. During startup, openGauss checks consistency between the latest WAL logs and the minimum restoration point. If the record location of the minimum restoration point is greater than that of the latest WAL logs, the database fails to start. |
diff --git a/product/en/docs-mogdb/v3.0/installation-guide/docker-installation/docker-installation.md b/product/en/docs-mogdb/v3.0/installation-guide/docker-installation/docker-installation.md
new file mode 100644
index 0000000000000000000000000000000000000000..7443536b6081b3620f71e9c8c12a9e227331f1c1
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/installation-guide/docker-installation/docker-installation.md
@@ -0,0 +1,448 @@
+---
+title: Container-based Installation
+summary: Container-based Installation
+author: Guo Huan
+date: 2021-06-01
+---
+
+# Container-based Installation
+
+This document introduces the installation of single instance and primary/standby instances in a MogDB docker container. MogDB container does not support the MogHA and OM tools, and currently supports at most one primary node and eight standby nodes. MogDB 2.1 container version supports the latest version of compat-tools and plugin functions.<br/>
+
+In consideration of narrowing the container image size for quick download and deployment, it is recommended that the x86 and ARM-based OSs depended by MogDB running in a docker container will be Ubuntu and Debian since MogDB 2.0. <br/>
+
+A MogDB container based on the x86-64 architecture runs in Ubuntu 18.04.<br/>
+
+A MogDB container based on the ARM64 architecture runs in Debian 10.
+
+<br/>
+
+## Docker-based Deployment
+
+### Single Instance Installation
+
+#### Before You Start
+
+The installation of a MogDB container is independent of the host OS. All OSs that can run a container enginer are supported, such as Linux, Windows, and macOS.
+
+Before installing the MogDB container, you need to prepare the container runnning environment, such as Docker.
+
+Docker is an open source application container engine based on Go and compliant with the Apache 2.0 protocol. Docker allows developers to package their applications and dependency packages into a lightweight, portable container that can then be distributed to any popular Linux machine and virtualized.
+
+Docker Desktop download address: <https://www.docker.com/products/docker-desktop>
+
+#### Installation Procedures
+
+1. Run Docker.
+
+2. Run the following command to obtain the latest version of the MogDB image file.
+
+   ```bash
+   docker pull swr.cn-north-4.myhuaweicloud.com/mogdb/mogdb:2.1.1
+   ```
+   
+   > Note: MogDB image supports x86 and ARM architectures, and the system will automatically download the corresponding image according to the server architecture that initiates the command, no need to specify manually.
+
+3. Run the following command to create a running directory for MogDB, using **mogdb** as an example below.
+
+   ```bash
+   mkdir /mogdb
+   ```
+
+4. Continue with the following command to create a new container, and name it **mogdb** to run a MogDB instance:
+
+   ```bash
+   docker run --name mogdb --privileged=true -d -e GS_PASSWORD=Secretpassword@123  -v /mogdb:/var/lib/mogdb  -p 15432:5432  swr.cn-north-4.myhuaweicloud.com/mogdb/mogdb:2.1.1
+   ```
+
+   For Windows OS:
+   - If Docker uses Hyper-V as the engine, run the following commands in sequence to create the logical object **mogdata** of the volume in Hyper-V, and then create the container:
+
+      ```bash
+      docker volume create mogdata
+
+      docker run --name mogdb --privileged=true -d -e GS_PASSWORD=Secretpassword@123 -v mogdata:/var/lib/mogdb -p 15453:5432  swr.cn-north-4.myhuaweicloud.com/mogdb/mogdb:2.1.1
+      ```
+
+   - If Docker uses WSL 2 as the engine, run the following command to create the container:
+
+      ```bash
+      docker run --name mogdb --privileged=true -d -e GS_PASSWORD=Secretpassword@123 -v C:\mogdb:/var/lib/mogdb -p 15432:5432  swr.cn-north-4.myhuaweicloud.com/mogdb/mogdb:2.1.1
+      ```
+
+   > Note:
+   >
+   > - MogDB uses port 5432 in the container for listening by default. If you want to access the database from outside the container, you need to specify the `-p` parameter in `docker run` command. For example, the above command will allow access to the container database using port 15432.
+   > - Once the container is deleted, all the data and configuration in the container will be lost. After re-running a container from the image, all the data is presented in the initialized state. So for the database container, in order to prevent the loss of data due to the demise of the container or corruption, the operation of persistent storage data is required. This is achieved by specifying the `-v` parameter in `docker run` command. For example, the above command will specify that all data files of MogDB will be stored under **/mogdb** of the host. In addition, If you use Podman, there will be a target path check. Therefore you need to create the target path in advance (step 4).
+
+5. Open the docker terminal:
+
+   ```bash
+   docker exec -it mogdb bash
+   ```
+
+   Now, the single instance installation in a MogDB container is complete.
+
+#### Using MogDB
+
+After the installation is complete and enter the container, switch to omm user by running "su - omm", you can access the database via gsql and use MogDB properly.
+
+```
+root@384ac97543bd:/# su - omm
+omm@384ac97543bd:~$ gsql -d postgres
+gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+Non-SSL connection (SSL connection is recommended when requiring high-security)
+Type "help" for help.
+
+MogDB=#
+```
+
+<br/>
+
+#### Environment Variables
+
+To flexibly use an MogDB image, you can set additional parameters. In the future, more control parameters will be added. The current version supports the setting of the following variables.
+
+**GS_PASSWORD**
+
+This parameter is mandatory when the MogDB image is used. The value cannot be empty or undefined. This parameter specifies the passwords of superuser **omm** and test user **mogdb** of the MogDB database. During the MogDB installation, the superuser **omm** is created by default. This username cannot be changed. The test user **mogdb** is created in  **entrypoint.sh**.
+
+The local trust mechanism is configured for the MogDB image. Therefore, no password is required for connecting to the database in the container. However, if you want to connect to the database from other hosts or containers, you need to enter the password.
+
+The password must contain at least eight characters, including uppercase letters, lowercase letters, digits, and special characters ( \# ? ! @ $ % ^ & * \- ). **!$&**must be escaped using a backslash ().
+
+**GS_NODENAME**
+
+Specifies the database node name. The default value is  **mogdb**.
+
+**GS_USERNAME**
+
+Specifies the username for connecting to the database. The default value is  **mogdb**.
+
+**GS_PORT**
+
+Specifies the database port. The default value is  **5432**.
+
+<br/>
+
+### Primary/Standby Installation
+
+#### Before You Begin
+
+To implement primary/standby installation in a MogDB container, please complete the steps in the previous document **Single Instance Installation** first.
+
+#### Procedures
+
+1. Switch to user **root**.
+
+   ```bash
+   su - root
+   ```
+
+2. Create custom networks to create fixed IPs that are easy for containers to use.
+
+   ```bash
+   docker network create --subnet=172.18.0.0/16 myNetwork
+   ```
+
+3. Create a primary database container.
+
+   ```bash
+   docker run --name mogdb_master \
+   --network myNetwork --ip 172.18.0.10 --privileged=true \
+   --hostname mogdb_master --detach \
+   --env GS_PORT=6432 \
+   --env OG_SUBNET=172.18.0.0/16 \
+   --env GS_PASSWORD=Enmo@1234 \
+   --env NODE_NAME=mogdb_master \
+   --env REPL_CONN_INFO="replconninfo1 = 'localhost=172.18.0.10 localport=6439  localservice=6432 remotehost=172.18.0.11 remoteport=6439 remoteservice=6432 '\n" \
+   swr.cn-north-4.myhuaweicloud.com/mogdb/mogdb:2.1.1 -M primary
+   ```
+
+4. Create a standby database container.
+
+   ```bash
+    docker run --name mogdb_slave_one \
+    --network myNetwork --ip 172.18.0.11 --privileged=true \
+    --hostname mogdb_slave_one --detach \
+    --env GS_PORT=6432 \
+    --env OG_SUBNET=172.18.0.0/16 \
+    --env GS_PASSWORD=Enmotech@1234 \
+    --env NODE_NAME=mogdb_slave_one \
+    --env REPL_CONN_INFO="replconninfo1 = 'localhost=172.18.0.11 localport=6439  localservice=6432 remotehost=172.18.0.10 remoteport=6439 remoteservice=6432 '\n" \
+    enmotech/mogdb:2.1.1 -M standby
+   ```
+
+5. Query the status of the primary database.
+
+   ```
+   [root@localhost ~]# docker exec -it mogdb_master bash 
+   [root@mogdb_master /] # su - omm
+   [omm@mogdb_master ~] $ gs_ctl query -D /var/lib/mogdb/data/
+   [2021-04-07 13:28:15.492][323][][gs_ctl] : gs_ctl query ,datadir is /var/lib/mogdb/data
+    HA state:
+         local_role                   : Primary
+         static_connections           : 1
+         db_state                     : Normal
+         detail_information           : Normal
+         
+    Senders info:
+         sender_pid                   : 286
+         local_role                   : Primary
+         peer_role                    : Standby
+         peer_state                   : Normal
+         state                        : Streaming
+         sender_sent_location         : 0/40007D0
+         sender_write_location        : 0/40007D0
+         sender_flush_location        : 0/40007D0
+         sender_replay_location       : 0/40007D0
+         receiver_received_location   : 0/40007D0
+         receiver_write_location      : 0/40007D0
+         receiver_flush_location      : 0/40007D0
+         receiver_replay_location     : 0/40007D0
+         sync_percent                 : 100%
+         sync_state                   : Sync
+         sync_priority                : 1
+         sync_most_available          : On
+         channel                      : 172.18.0.10:6439-->172.18.0.11: 45640
+   
+    Receiver info: 
+   No information
+   ```
+
+6. Query the status of the standby database.
+
+   ```
+   [root@localhost ~]# docker exec -it mogdb_slave_one bash
+   [root@mogdb_slave_one /] # su - omm
+   Last login: Wed Apr 7 13:32:23 UTC 2021 on pts/0
+   [omm@mogdb_slave_one ~] $ gs_ctl query -D /var/lib/mogdb/data/
+   [2021-04-07 14:46:15.492][393][][gs_ctl] : gs_ctl query ,datadir is /var/lib/mogdb/data
+    HA state:
+         local_role                   : Standby
+         static_connections           : 1
+         db_state                     : Normal
+         detail_information           : Normal
+         
+    Senders info:
+   No information
+    Receiver info: 
+         receiver_pid                 : 312
+         local_role                   : Standby
+         peer_role                    : Primary
+         peer_state                   : Normal
+         state                        : Normal
+         sender_sent_location         : 0/4005D50
+         sender_write_location        : 0/4005D50
+         sender_flush_location        : 0/4005D50
+         sender_replay_location       : 0/4005D50
+         receiver_received_location   : 0/4005D50
+         receiver_write_location      : 0/4005D50
+         receiver_flush_location      : 0/4005D50
+         receiver_replay_location     : 0/4005D50
+         sync_percent                 : 100%
+         channel                      : 172.18.0.11:45640<--172.18.0.10:6439
+   ```
+   
+   > Note: As shown in the figures above, the senders info and the receiver info indicate that the status of the primary and standby databases is normal.
+
+#### Read/Write Testing
+
+Primary database write test:
+
+```sql
+[omm@mogdb_master ~] $ gsql -p6432
+gsql ((MogDB 2.1.1 build 56189e20) compiled at 2022-03-21 18:47:53 commit 0 last mr  )
+Non-SSL connection (SSL connection is recommended when requiring high-security)
+Type "help" for help.
+
+omm=# create table test(ID int);
+CREATE TABLE
+omm=# insert into test values(1);
+INSERT 0 1
+```
+
+Standby database read test:
+
+```sql
+[omm@mogdb_slave_one ~] $ gsql -p6432
+gsql ((MogDB 2.1.1 build 56189e20) compiled at 2022-03-21 18:47:53 commit 0 last mr  )
+Non-SSL connection (SSL connection is recommended when requiring high-security)
+Type "help" for help.
+
+omm=# select * from test;
+ id 
+----
+  1
+(1 row)
+
+omm=# delete from test;
+ERROR: cannot execute DELETE in a read-only transaction
+```
+
+> Note: The result shows that the primary database is writable and the standby database is readable but not writable.
+
+#### Switchover Testing
+
+Switch **mogdb_slave_one** as the primary database and **mogdb_master** as the standby database.
+
+Run the switchover command in **mogdb_slave_one**.
+
+```
+[omm@mogdb_slave_one ~] $ gs_ctl switchover -D /var/lib/mogdb/data/
+[2021-04-07 15:31:45.246][428][][gs_ctl]: gs_ctl switchover ,datadir is /var/lib/mogdb/data
+[2021-04-07 15:31:45.247][428][][gs_ctl]: switchover term(1)
+[2021-04-07 15:31:45.251][428][][gs_ctl]: waiting for server to switchover......
+[2021-04-07 15:31:45.325][428][][gs_ctl]: done
+[2021-04-07 15:31:45.325][428][][gs_ctl]: switchover completed (/var/lib/mogdb/data)
+```
+
+Query the status of **mogdb_slave_one**.
+
+```
+[omm@mogdb_slave_one ~] $ gs_ctl query -D /var/lib/mogdb/data/
+[2021-04-07 15:42:45.246][459][][gs_ctl]: gs_ctl query ,datadir is /var/lib/mogdb/data
+ HA state:
+      local_role                   : Primary
+      static_connections           : 1
+      db_state                     : Normal
+      detail_information           : Normal
+      
+ Senders info:
+      sender_pid                   : 442
+      local_role                   : Primary
+      peer_role                    : Standby
+      peer_state                   : Normal
+      state                        : Streaming
+      sender_sent_location         : 0/40102B8
+      sender_write_location        : 0/40102B8
+      sender_flush_location        : 0/40102B8
+      sender_replay_location       : 0/40102B8
+      receiver_received_location   : 0/40102B8
+      receiver_write_location      : 0/40102B8
+      receiver_flush_location      : 0/40102B8
+      receiver_replay_location     : 0/40102B8
+      sync_percent                 : 100%
+      sync_state                   : Sync
+      sync_priority                : 1
+      sync_most_available          : On
+      channel                      : 172.18.0.11:6439-->172.18.0.10: 49696
+
+ Receiver info: 
+No information
+```
+
+Query the status of **mogdb_master**.
+
+```
+[omm@mogdb_master ~] $ gs_ctl query -D /var/lib/mogdb/data/
+[2021-04-07 15:46:35.246][619][][gs_ctl]: gs_ctl query ,datadir is /var/lib/mogdb/data
+ HA state:
+      local_role                   : Standby
+      static_connections           : 1
+      db_state                     : Normal
+      detail_information           : Normal
+      
+ Senders info:
+No information
+ Receiver info: 
+      receiver_pid                 : 590
+      local_role                   : Standby
+      peer_role                    : Primary
+      peer_state                   : Normal
+      state                        : Normal
+      sender_sent_location         : 0/4010718
+      sender_write_location        : 0/4010718
+      sender_flush_location        : 0/4010718
+      sender_replay_location       : 0/4010718
+      receiver_received_location   : 0/4010718
+      receiver_write_location      : 0/4010718
+      receiver_flush_location      : 0/4010718
+      receiver_replay_location     : 0/4010718
+      sync_percent                 : 100%
+      channel                      : 172.18.0.10:49696<--172.18.0.11:6439
+```
+
+You can find that **mogdb_master** becomes the standby database and **mogdb_slave_one** becomes the primary database. The switchover is successful.
+
+#### Read/Write Verification
+
+Perform write validation on the primary database **mogdb_slave_one**.
+
+```sql
+[omm@mogdb_slave_one ~] $ gsql -p6432
+gsql ((MogDB 2.1.1 build 56189e20) compiled at 2022-03-21 18:47:53 commit 0 last mr  )
+Non-SSL connection (SSL connection is recommended when requiring high-security)
+Type "help" for help.
+
+omm=# select * from test;
+ id 
+----
+  1
+(1 row)
+
+omm=# insert into test values(2);
+INSERT 0 1
+```
+
+Perform read validation on the standby database **mogdb_master**.
+
+```sql
+[omm@mogdb_master ~] $ gsql -p6432
+gsql ((MogDB 2.1.1 build 56189e20) compiled at 2022-03-21 18:47:53 commit 0 last mr  )
+Non-SSL connection (SSL connection is recommended when requiring high-security)
+Type "help" for help.
+
+omm=# select * from test;
+ id 
+----
+  1
+  2
+(2 row)
+
+omm=# delete from test;
+ERROR: cannot execute DELETE in a read-only transaction
+```
+
+As you can see, the original standby database is writable after being switched as the primary database, and the original primary database is readable but not writable after being switched as the standby database.
+
+<br/>
+
+## Kubernetes-based Deployment
+
+MogDB 2.1 and later supports Kubernetes-based deployment.
+
+- x86
+  
+  ```
+  $ kubectl apply -f https://gitee.com/enmotech/enmotech-docker-mogdb/raw/master/2.1.1/k8s_amd.yaml
+  pod/mogdb created
+  ```
+
+- arm
+
+  ```
+  $ kubectl apply -f https://gitee.com/enmotech/enmotech-docker-mogdb/raw/master/2.1.1/k8s_arm.yaml
+  pod/mogdb created
+  ```
+
+- Kubernetes connect the pod
+
+  Connect to MogDB through the gsql command in the pod.
+
+  ```
+  $ kubectl exec -it mogdb -- bash
+  root@mogdb:/# su - omm
+  omm@mogdb:~$ gsql -d postgres
+  gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+  Non-SSL connection (SSL connection is recommended when requiring high-security)
+  Type "help" for help.
+  
+  MogDB=#
+  ```
+
+<br/>
+
+## What's Next
+
+MogDB container does not support MogHA and OM tools. It is only used for testing, and currently supports at most one primary node and eight standby nodes. MogDB Enterprise Edition includes MogHA component. The basic functions of the MogDB container and Enterprise Edition are identical. It is recommended that MogDB Enterprise Edition is used in the production environment.
diff --git a/product/en/docs-mogdb/v3.0/installation-guide/manual-installation.md b/product/en/docs-mogdb/v3.0/installation-guide/manual-installation.md
new file mode 100644
index 0000000000000000000000000000000000000000..a1fd9827f0cbd7b7e97e4dc3d6b251d0e784e11f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/installation-guide/manual-installation.md
@@ -0,0 +1,374 @@
+---
+title: Manually Deploying MogDB/openGauss
+summary: Manually Deploying MogDB/openGauss
+author: Zhang Cuiping
+date: 2021-10-14
+---
+
+# Manually Deploying MogDB/openGauss in the Standalone, Primary/Standby, and Cascaded Modes
+
+## 1. Preparation
+
+a. Disable the firewall.
+
+```bash
+systemctl disable firewalld.service
+systemctl stop firewalld.service
+setenforce=0
+sed -i '/^SELINUX=/c'SELINUX=disabled /etc/selinux/config
+```
+
+b. Install the dependency.
+
+```bash
+yum install libaio-devel -y
+```
+
+c. Create the related directory, user, and user group.
+
+```bash
+groupadd dbgrp -g 2000
+useradd omm -g 2000 -u 2000
+echo "Enmo@123" | passwd --stdin omm
+mkdir -p /opt/mogdb/software
+chown -R omm:dbgrp /opt/software/mogdb
+```
+
+d. Upload and decompress the binary file.
+
+```bash
+[root@mogdb-kernel-0001 software]# pwd
+/opt/mogdb/software
+[root@mogdb-kernel-0001 software]# ls -lrt
+total 90236
+-r-------- 1 root root 92401412 Jun 13 06:14 MogDB-2.1.1-openEuler-64bit.tar.bz2
+chown omm:dbgrp MogDB-2.1.1-openEuler-64bit.tar.bz2
+su - omm
+cd /opt/mogdb/software/
+tar -xf MogDB-2.1.1-openEuler-64bit.tar.bz2
+```
+
+## 2. Database Initialization (Standalone)
+
+a. Configure environment variables.
+
+```bash
+echo "export GAUSSHOME=/opt/mogdb/software"  >> /home/omm/.bashrc && \
+echo "export PATH=\$GAUSSHOME/bin:\$PATH " >> /home/omm/.bashrc && \
+echo "export LD_LIBRARY_PATH=\$GAUSSHOME/lib:\$LD_LIBRARY_PATH" >> /home/omm/.bashrc
+source /home/omm/.bashrc
+```
+
+b. Initialize the database.
+
+```bash
+bin/gs_initdb --pgdata=/opt/mogdb/data --nodename=primary --pwpasswd=Enmo@123 --encoding=UTF-8 --locale=en_US.UTF-8
+```
+
+c. Modify initialized parameters.
+
+```bash
+echo "port=26000" >> /opt/mogdb/data/postgresql.conf
+echo "listen_addresses = '0.0.0.0'" >> /opt/mogdb/data/postgresql.conf
+echo "password_encryption_type = 0" >> /opt/mogdb/data/postgresql.conf
+echo "log_directory = 'pg_log'" >> /opt/mogdb/data/postgresql.conf
+echo "remote_read_mode=non_authentication" >> /opt/mogdb/data/postgresql.conf
+echo "host all all 0.0.0.0/0 md5" >> /opt/mogdb/data/pg_hba.conf
+```
+
+d. Start the database.
+
+```bash
+gs_ctl start -D /opt/mogdb/data
+```
+
+**Standalone installation is complete.**
+
+## 3. Primary/Standby Installation
+
+a. Install the primary database.
+
+- Configure the connection.
+
+  ```bash
+  echo "replconninfo1='localhost=172.16.0.106 localport=26001 localheartbeatport=26005 localservice=26004 remotehost=172.16.0.245 remoteport=26001 remoteheartbeatport=26005 remoteservice=26004'
+  " >> /opt/mogdb/data/postgresql.conf
+  ```
+
+  **localhost indicates the IP address of the primary database, and remotehost indicates the IP address of the standby database.**
+
+- Start the primary database in primary mode.
+
+  ```bash
+  gs_ctl restart -D /opt/mogdb/data/ -M primary
+  ```
+
+b. Install the standby database.
+
+- For details about the preparation, see [Preparation](1-Preparation).
+
+- Configure environment variables.
+
+  ```bash
+  echo "export GAUSSHOME=/opt/mogdb/software"  >> /home/omm/.bashrc && \
+  echo "export PATH=\$GAUSSHOME/bin:\$PATH " >> /home/omm/.bashrc && \
+  echo "export LD_LIBRARY_PATH=\$GAUSSHOME/lib:\$LD_LIBRARY_PATH" >> /home/omm/.bashrc
+  source /home/omm/.bashrc
+  # Upload configuration files of the primary database to the standby database.
+  scp /opt/mogdb/data/pg_hba.conf /opt/mogdb/data/postgresql.conf 172.16.0.245:/opt/mogdb/data/
+  ```
+
+- Configure the connection.
+
+  ```bash
+  sed -i "/^replconninfo1/creplconninfo1=‘localhost=172.16.0.245 localport=26001 localheartbeatport=26005 localservice=26004 remotehost=172.16.0.106 remoteport=26001 remoteheartbeatport=26005 remoteservice=26004’" /opt/mogdb/data/postgresql.conf
+  ```
+
+  **localhost indicates the IP address of the standby database, and the remotehost indicates the IP address of the primary database.**
+
+- Build the primary/standby relationship.
+
+  ```bash
+  gs_ctl build -D /opt/mogdb/data/ -b full -M standby
+  ```
+
+- Query the status of the primary and standby databases.
+
+  - Primary database
+
+    ```bash
+    [omm@mogdb-kernel-0001 data]$ gs_ctl query -D /opt/mogdb/data/
+    [2021-06-13 07:51:41.119][159054][][gs_ctl]: gs_ctl query ,datadir is /opt/mogdb/data
+    HA state:
+            local_role                     : Primary
+            static_connections             : 1
+            db_state                       : Normal
+            detail_information             : Normal
+
+    Senders info:
+            sender_pid                     : 159041
+            local_role                     : Primary
+            peer_role                      : Standby
+            peer_state                     : Normal
+            state                          : Streaming
+            sender_sent_location           : 0/14000258
+            sender_write_location          : 0/14000258
+            sender_flush_location          : 0/14000258
+            sender_replay_location         : 0/14000258
+            receiver_received_location     : 0/14000258
+            receiver_write_location        : 0/14000258
+            receiver_flush_location        : 0/14000258
+            receiver_replay_location       : 0/14000258
+            sync_percent                   : 100%
+            sync_state                     : Sync
+            sync_priority                  : 1
+            sync_most_available            : Off
+            channel                        : 172.16.0.106:26001-->172.16.0.245:60856
+
+    Receiver info:
+    No information
+    ```
+
+  - Standby database
+
+    ```bash
+    [omm@mogdb-kernel-0002 data]$ gs_ctl query -D /opt/mogdb/data/
+    [2021-06-13 07:51:32.743][123204][][gs_ctl]: gs_ctl query ,datadir is /opt/mogdb/data
+    HA state:
+            local_role                     : Standby
+            static_connections             : 1
+            db_state                       : Normal
+            detail_information             : Normal
+
+    Senders info:
+    No information
+    Receiver info:
+            receiver_pid                   : 123194
+            local_role                     : Standby
+            peer_role                      : Primary
+            peer_state                     : Normal
+            state                          : Normal
+            sender_sent_location           : 0/14000140
+            sender_write_location          : 0/14000140
+            sender_flush_location          : 0/14000140
+            sender_replay_location         : 0/14000140
+            receiver_received_location     : 0/14000140
+            receiver_write_location        : 0/14000140
+            receiver_flush_location        : 0/14000140
+            receiver_replay_location       : 0/14000140
+            sync_percent                   : 100%
+            channel                        : 172.16.0.245:60856<--172.16.0.106:26001
+    ```
+
+**Primary/standby installation is complete.**
+
+## 4. Cascaded Installation
+
+a. For details about the primary/standby installation, see [Preparation](1-Preparation), [Database Initialization](2-Database Initialization (Standalone)), and [Primary/Standby Installation](3-Primary/Standby Installation).
+
+b. Add the replication channel.
+
+- Primary database
+
+  ```bash
+  gsql -d postgres -p26000 -c "alter system set replconninfo2 to ‘localhost=172.16.0.106 localport=26001 localheartbeatport=26005 localservice=26004 remotehost=172.16.0.127 remoteport=26001 remoteheartbeatport=26005 remoteservice=26004 iscascade=true’;"
+  ```
+
+- Standby database
+
+  ```bash
+  gsql -d postgres -p26000 -c "alter system set replconninfo2 to ‘localhost=172.16.0.245 localport=26001 localheartbeatport=26005 localservice=26004 remotehost=172.16.0.127 remoteport=26001 remoteheartbeatport=26005 remoteservice=26004 iscascade=true’;"
+  ```
+
+c. Operate with the cascaded database.
+
+- For details about the preparation, see [Preparation](1-Preparation).
+
+- Configure environment variables.
+
+  ```bash
+  echo "export GAUSSHOME=/opt/mogdb/software"  >> /home/omm/.bashrc && \
+  echo "export PATH=\$GAUSSHOME/bin:\$PATH " >> /home/omm/.bashrc && \
+  echo "export LD_LIBRARY_PATH=\$GAUSSHOME/lib:\$LD_LIBRARY_PATH" >> /home/omm/.bashrc
+  source /home/omm/.bashrc
+  ```
+
+- Upload configuration files of the standby database to the standby database.
+
+  ```bash
+  scp /opt/mogdb/data/pg_hba.conf /opt/mogdb/data/postgresql.conf 172.16.0.245:/opt/mogdb/data/
+  ```
+
+- Configure the connection.
+
+  ```bash
+  sed -i "/^replconninfo1/creplconninfo1='localhost=172.16.0.127 localport=26001 localheartbeatport=26005 localservice=26004 remotehost=172.16.0.106 remoteport=26001 remoteheartbeatport=26005 remoteservice=26004'" /opt/mogdb/data/postgresql.conf
+  sed -i "/replconninfo2/creplconninfo2='localhost=172.16.0.127 localport=26001 localheartbeatport=26005 localservice=26004 remotehost=172.16.0.245 remoteport=26001 remoteheartbeatport=26005 remoteservice=26004'" /opt/mogdb/data/postgresql.conf
+  ```
+
+  **localhost indicates the IP address of the cascaded database, and remotehost indicates the IP addresses of the primary and standby databases.**
+
+- Build the primary/standby relationship.
+
+  ```bash
+  gs_ctl build -D /opt/mogdb/data/ -b full -M cascade_standby
+  ```
+
+d. Query the status of the primary, standby, and cascaded databases.
+
+- Primary database
+
+  ```bash
+  [omm@mogdb-kernel-0001 ~]$ gs_ctl query -D /opt/mogdb/data
+  [2021-06-13 08:37:03.281][207069][][gs_ctl]: gs_ctl query ,datadir is /opt/mogdb/data
+   HA state:
+          local_role                     : Primary
+          static_connections             : 2
+          db_state                       : Normal
+          detail_information             : Normal
+
+   Senders info:
+          sender_pid                     : 206143
+          local_role                     : Primary
+          peer_role                      : Standby
+          peer_state                     : Normal
+          state                          : Streaming
+          sender_sent_location           : 0/1A000140
+          sender_write_location          : 0/1A000140
+          sender_flush_location          : 0/1A000140
+          sender_replay_location         : 0/1A000140
+          receiver_received_location     : 0/1A000140
+          receiver_write_location        : 0/1A000140
+          receiver_flush_location        : 0/1A000140
+          receiver_replay_location       : 0/1A000140
+          sync_percent                   : 100%
+          sync_state                     : Sync
+          sync_priority                  : 1
+          sync_most_available            : Off
+          channel                        : 172.16.0.106:26001-->172.16.0.245:34586
+
+   Receiver info:
+  No information
+  ```
+
+- Standby database
+
+  ```bash
+  gs_ctl query -D /opt/mogdb/data
+  [2021-06-13 08:37:09.128][147065][][gs_ctl]: gs_ctl query ,datadir is /opt/mogdb/data
+   HA state:
+          local_role                     : Standby
+          static_connections             : 2
+          db_state                       : Normal
+          detail_information             : Normal
+
+   Senders info:
+          sender_pid                     : 147043
+          local_role                     : Standby
+          peer_role                      : Cascade Standby
+          peer_state                     : Normal
+          state                          : Streaming
+          sender_sent_location           : 0/1A000140
+          sender_write_location          : 0/1A000140
+          sender_flush_location          : 0/1A000140
+          sender_replay_location         : 0/1A000140
+          receiver_received_location     : 0/1A000140
+          receiver_write_location        : 0/1A000140
+          receiver_flush_location        : 0/1A000140
+          receiver_replay_location       : 0/1A000140
+          sync_percent                   : 100%
+          sync_state                     : Async
+          sync_priority                  : 0
+          sync_most_available            : Off
+          channel                        : 172.16.0.245:26001-->172.16.0.127:49110
+
+   Receiver info:
+          receiver_pid                   : 146771
+          local_role                     : Standby
+          peer_role                      : Primary
+          peer_state                     : Normal
+          state                          : Normal
+          sender_sent_location           : 0/1A000140
+          sender_write_location          : 0/1A000140
+          sender_flush_location          : 0/1A000140
+          sender_replay_location         : 0/1A000140
+          receiver_received_location     : 0/1A000140
+          receiver_write_location        : 0/1A000140
+          receiver_flush_location        : 0/1A000140
+          receiver_replay_location       : 0/1A000140
+          sync_percent                   : 100%
+          channel                        : 172.16.0.245:34586<--172.16.0.106:26001
+  ```
+
+- Cascaded database
+
+  ```bash
+  gs_ctl query -D /opt/mogdb/data
+  [2021-06-13 08:36:56.223][273241][][gs_ctl]: gs_ctl query ,datadir is /opt/mogdb/data
+   HA state:
+          local_role                     : Cascade Standby
+          static_connections             : 2
+          db_state                       : Normal
+          detail_information             : Normal
+
+   Senders info:
+  No information
+   Receiver info:
+          receiver_pid                   : 273237
+          local_role                     : Cascade Standby
+          peer_role                      : Standby
+          peer_state                     : Normal
+          state                          : Normal
+          sender_sent_location           : 0/1A000140
+          sender_write_location          : 0/1A000140
+          sender_flush_location          : 0/1A000140
+          sender_replay_location         : 0/1A000140
+          receiver_received_location     : 0/1A000140
+          receiver_write_location        : 0/1A000140
+          receiver_flush_location        : 0/1A000140
+          receiver_replay_location       : 0/1A000140
+          sync_percent                   : 100%
+          channel                        : 172.16.0.127:49110<--172.16.0.245:26001
+  ```
+
+**Cascaded installation is complete.**
diff --git a/product/en/docs-mogdb/v3.0/installation-guide/simplified-installation-process/1-installation-preparation.md b/product/en/docs-mogdb/v3.0/installation-guide/simplified-installation-process/1-installation-preparation.md
new file mode 100644
index 0000000000000000000000000000000000000000..3620daee92d548d7142fcc05bbf2d240ccdf55fd
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/installation-guide/simplified-installation-process/1-installation-preparation.md
@@ -0,0 +1,294 @@
+---
+title: Preparing for Installation
+summary: Preparing for Installation
+author: Zhang Cuiping
+date: 2021-06-11
+---
+
+# Preparing for Installation
+
+This section describes how to prepare and configure an environment for simplified MogDB installation. The simplified installation can be performed on a single node or on primary/standby nodes. Read this section carefully before installation. If the configuration in this section has been completed, skip this section.
+
+## Obtaining the Installation Package
+
+You can obtain the installation package from the MogDB website.
+
+MogDB website: <https://www.mogdb.io/en/downloads/mogdb/>
+
+**Procedure**
+
+This section takes the openEuler OS as an example to describe how to obtain the target installation package.
+
+1. Upload the downloaded standard installation package and decompress it to obtain the single-node installation package.
+
+   ```bash
+   tar -xvf MogDB-x.x.x-openEuler-arm_64.tar
+   ```
+
+   > Note:
+   >
+   > + The MogDB website provides the standard installation package **MogDB-x.x.x-openEuler-arm_64.tar**. You need to decompress it to obtain the single-node installation package **MogDB-x.x.x-openEuler-64bit.tar.bz2**.
+   >
+   > + In environments that allow access to external networks, the standard installation package can be downloaded directly via the wget command.
+   >
+   >   ```bash
+   >   wget -c https://cdn-mogdb.enmotech.com/mogdb-media/2.1.1/MogDB-2.1.1-openEuler-arm_64.tar
+   >   ```
+   >
+   >   Then you can run the **tar** command to decompress it.
+
+2. Check the installation package.
+
+   Decompress the installation package and check whether the installation directory and files are complete. Run the following commands in the directory where the installation package is stored:
+
+   ```bash
+   tar -jxf MogDB-x.x.x-openEuler-64bit.tar.bz2
+   ls -1b
+   ```
+
+   Run the **ls** command to display information similar to the following:
+
+   ```bash
+   total 90296
+   drwx------ 3 root root     4096 Mar 31 21:18 bin
+   drwx------ 3 root root     4096 Mar 31 21:18 etc
+   drwx------ 3 root root     4096 Mar 31 21:18 include
+   drwx------ 4 root root     4096 Mar 31 21:18 jre
+   drwx------ 5 root root     4096 Mar 31 21:18 lib
+   -rw------- 1 root root 92427499 Apr  1 09:43 MogDB-x.x.x-openEuler-64bit.tar.bz2
+   drwx------ 5 root root     4096 Mar 31 21:18 share
+   drwx------ 2 root root     4096 Mar 31 21:18 simpleInstall
+   -rw------- 1 root root       32 Mar 31 21:18 version.cfg
+   ```
+
+## Preparing the Software and Hardware Installation Environment
+
+This section describes the preparations for installation. It is recommended that servers to be deployed on MogDB have the same software and hardware configurations.
+
+### Hardware Requirements
+
+Table 1 lists the minimum hardware requirements of the MogDB server. When planning the hardware configuration of a product, consider the data scale and expected database response speed. Plan hardware as required.
+
+**Table 1** Hardware requirements
+
+| Item    | Configuration Description                                    |
+| :------ | :----------------------------------------------------------- |
+| Memory  | It is recommended that the memory be 32 GB or above for function debugging.<br />In performance tests and commercial deployment, it is recommended that the memory be 128 GB or above for single-instance deployment.<br />Complex queries require much more memory, and therefore, the memory may be insufficient in high-concurrency scenarios. In this case, it is recommended that a large-memory server or load management be used to restrict concurrency on the system. |
+| CPU     | It is recommended at least one 8-core 2.0 GHz CPU be used for function debugging.<br />In performance tests and commercial deployment, it is recommended that one 16-core 2.0 GHz CPU be used.<br />You can set CPUs to hyper-threading or non-hyper-threading mode.<br />NOTE:<br />For individual developers, the minimum configuration is 2 cores and 4 GB memory, and the recommended configuration is 4 cores and 8 GB memory.<br />Currently, MogDB supports Kunpeng 920 servers, Hygon 3000, 5000, 7000 series servers, ZHAOXIN KH30000、KH20000、ZX-C+ series servers and x86_64-based universal PC servers. |
+| Disk    | Hard disks used for installing MogDB must meet the following requirements:<br />- At least 1 GB is used to install the MogDB applications.<br />- About 300 MB is used for each host to store metadata.<br />- More than 70% of available disk space is reserved to store data.<br />You are advised to configure the system disk to RAID 1 and data disk to RAID 5 and plan four groups of RAID 5 data disks for installing MogDB. For details about RAID configuration, see the instructions in the hardware vendors' manuals. Set **Disk Cache Policy** to **Disabled** to avoid data loss upon unexpected power-off.<br />MogDB supports using an SSD with the SAS interface and NVMe protocol deployed in RAID mode as the primary storage device of the database. |
+| Network | Minimum 300 Mbit/s Ethernet is required.<br />You are advised to bond two NICs for redundancy. For details about NIC redundancy bond configuration, see the instructions in the hardware vendors' manuals. |
+
+### Software Requirements
+
+**Table 2** Software requirements
+
+| Software          | Configuration Description                                    |
+| :---------------- | :----------------------------------------------------------- |
+| rdtscp Instruction Set (x86)  | Run the `lscpu \| grep rdtscp` command to see if the rdtscp instruction set is supported.            |
+| bmi2 Instruction Set (CentOS)  | Run the `lscpu \| grep bmi2` command to see if the bmi2 instruction set is supported.            |
+| Tool              | bzip2                                                        |
+
+### Operating System Requirements
+
+This release supports the following OS and CPU architecture combinations:
+
+**Table 3** Operating System Requirements
+
+| OS              | x86                        | ARM           |
+| --------------- | -------------------------- | ------------- |
+| CentOS 7.x      | Intel, AMD, Hygon, ZHAOXIN | Being adapted |
+| Redhat 7.x      | Intel, AMD, Hygon, ZHAOXIN | Being adapted |
+| openEuler 20.03 | Intel, AMD, Hygon, ZHAOXIN | Kunpeng       |
+| Kylin V10       | Intel, AMD, Hygon, ZHAOXIN | Kunpeng       |
+| UOS V20-D/V20-E | Intel, AMD, Hygon, ZHAOXIN | Kunpeng       |
+| UOS V20-A       | Intel, AMD, Hygon, ZHAOXIN | Being adapted |
+
+### Software Dependency Requirements
+
+Table 4 describes the MogDB software dependency requirements.
+
+You are advised to use the default installation packages of the following dependent software in the listed OS installation CD-ROMs or sources. If the following software does not exist, refer to the recommended versions of the software.
+
+**Table 4** Software dependency requirements
+
+| Software                                    | Recommended Version |
+| :------------------------------------------ | :------------------ |
+| libaio-devel                                | 0.3.109-13          |
+| flex                                        | 2.5.31 or later     |
+| bison                                       | 2.7-4               |
+| ncurses-devel                               | 5.9-13.20130511     |
+| glibc-devel                                 | 2.17-111            |
+| patch                                       | 2.7.1-10            |
+| redhat-lsb-core                             | 4.1                 |
+| readline-devel                              | 7.0-13              |
+| libnsl (in the openEuler + x86 environment) | 2.28-36             |
+| openSSH                                     | 8.4p1               |
+
+<br/>
+
+## Modifying OS Configuration
+
+### Disabling the OS Firewall
+
+To ensure that MogDB can work properly when the firewall is enabled, MogDB-related services, protocols, IP addresses, and ports need to be added to the firewall whitelist of the MogDB host.
+
+Take openEuler OS as an example. Assume that the MogDB information is listed in Table 5.
+
+**Table 5** MogDB information
+
+| Host Name          | Internal IP Address | External IP Address |
+| :----------------- | :------------------ | :------------------ |
+| plat1              | 192.168.0.11        | 10.10.0.11          |
+| Management network | -                   | 10.10.64.236        |
+
+Currently, the installation can be performed only when the firewall is disabled.
+
+1. Modify the SELinux operating mode to temporarily disable the firewall.<a id="config file"></a>
+
+   ```bash
+   setenforce 0
+   ```
+
+2. Set the value of **SELINUX** in the **/etc/selinux/config** file to **disabled**.
+
+   a. Run the **vim** command to open the **config** file.
+
+   ```bash
+   vim /etc/selinux/config
+   ```
+
+   b. Change the value of **SELINUX** to **disabled** and run the **:wq** command to save the change and exit.
+
+   ```bash
+   SELINUX=disabled
+   ```
+
+3. (Optional)Restart the OS.
+
+   ```bash
+   reboot
+   ```
+
+   Perform the following operations to permanently disable the firewall.
+
+4. Check whether the firewall is disabled.
+
+   ```bash
+   systemctl status firewalld
+   ```
+
+   If the firewall status is **active (running)**, the firewall is not disabled. Go to step [5](#disablethefirewall).
+
+   If the firewall status is **inactive (dead)**, you do not need to disable the firewall.
+
+5. Disable the firewall service. <a id="disablethefirewall"></a>
+
+   ```bash
+   systemctl disable firewalld.service
+   systemctl stop firewalld.service
+   ```
+
+6. Repeat steps [1](#config file) to [5](#disablethefirewall) on other hosts.
+
+### Setting Character Set Parameters
+
+Set the same character set for all database nodes. You can add **export LANG=Unicode** to the **/etc/profile** file.
+
+```bash
+vim /etc/profile
+```
+
+### Setting the Time Zone and Time
+
+Ensure that the time zone and time on each database node are consistent.
+
+1. Run the following command to check whether the time and time zone of each database node are consistent: If the time and time zone of each database node are inconsistent, perform steps [2](#2) to [3](#3).
+
+   ```bash
+   date
+   ```
+
+2. Run the following command to copy the **/etc/localtime** file to the **/usr/share/zoneinfo/** directory of each database node: <a id="2"> </a>
+
+   ```bash
+   cp /usr/share/zoneinfo/$Locale/$Time zone /etc/localtime
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif)  **NOTE:**
+   > `$Locale/$Time zone` indicates the locale and time zone to be set, for example, **Asia/Shanghai**.
+
+3. Run the **date -s** command to set the time of each database node to the same time. For example: <a id="3"></a>
+
+   ```bash
+   date -s "Sat Sep 27 16:00:07 CST 2020"
+   ```
+
+### (Optional) Disabling the Swap Memory
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif)  **NOTE:** Disabling the swap memory ensures the access performance of the database and prevents the buffer memory of the database from being evicted to the disk. If the server memory is small and the memory is overloaded, you can enable the swap memory to ensure normal running.
+
+Run the **swapoff -a** command on each database node to disable the swap memory.
+
+```bash
+swapoff -a
+```
+
+### Disabling RemoveIPC
+
+On each database node, disable RemoveIPC. For CentOS, skip this step.
+
+1. Change the value of **RemoveIPC** in the **/etc/systemd/logind.conf** file to **no**. <a id="1"></a>.
+
+   a. Run the **vim** command to open the **logind.conf** file.
+
+   ```bash
+   vim  /etc/systemd/logind.conf
+   ```
+
+   b. Change the value of **RemoveIPC** to **no**.
+
+   ```bash
+   RemoveIPC=no
+   ```
+
+2. Change the value of **RemoveIPC** in the **/usr/lib/systemd/system/systemd-logind.service** file to **no**.
+
+   a. Run the **vim** command to open the **systemd-logind.service** file.
+
+   ```bash
+   vim /usr/lib/systemd/system/systemd-logind.service
+   ```
+
+   b. Change the value of **RemoveIPC** to **no**.
+
+   ```bash
+   RemoveIPC=no
+   ```
+
+3. Reload configuration parameters.
+
+   ```bash
+   systemctl daemon-reload
+   systemctl restart systemd-logind
+   ```
+
+4. Check whether the modification takes effect.
+
+   ```bash
+   loginctl show-session | grep RemoveIPC
+   systemctl show systemd-logind | grep RemoveIPC
+   ```
+
+5. Open the **limits.conf** and **sysctl.conf** configuration files and add the following content to the corresponding files, respectively.<a id="5"> </a>
+
+   ```bash
+   vim /etc/security/limits.conf
+   #Add the following content to the limits.conf configuration file：
+   omm            soft    nofile          1000000
+   omm            hard    nofile          1000000
+   vim /etc/sysctl.conf
+   #Add the following content to the sysctl.conf configuration file：
+   kernel.sem = 250 32000 100 999
+   ```
+
+6. Repeat steps [1](#1) to [5](#5) on other hosts.
diff --git a/product/en/docs-mogdb/v3.0/installation-guide/simplified-installation-process/2-installation-on-a-single-node.md b/product/en/docs-mogdb/v3.0/installation-guide/simplified-installation-process/2-installation-on-a-single-node.md
new file mode 100644
index 0000000000000000000000000000000000000000..84fd78083d767065661390ef3bc46e406953e5dd
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/installation-guide/simplified-installation-process/2-installation-on-a-single-node.md
@@ -0,0 +1,97 @@
+---
+title: Installation on a Single Node
+summary: Installation on a Single Node
+author: Zhang Cuiping
+date: 2021-06-11
+
+---
+
+# Installation on a Single Node
+
+This section takes openEuler system as an example to introduce how to install MogDB on a single node.
+
+1. Create directory, user, group, and authorize them.
+
+   ```
+   groupadd dbgrp -g 2000
+   useradd omm -g 2000 -u 2000
+   mkdir -p /opt/software/mogdb
+   chown -R omm:dbgrp /opt/software/mogdb
+   ```
+
+2. Decompress the MogDB package to the installation directory.
+
+   ```
+   su - omm
+   cd /opt/software/mogdb/
+   tar -jxf MogDB-x.x.x-openEuler-64bit.tar.bz2 -C /opt/software/mogdb/
+   ```
+
+3. Go to the **simpleInstall** directory.
+
+   ```
+   cd /opt/software/mogdb/simpleInstall
+   ```
+
+4. Run the **install.sh -w** command to install MogDB.
+
+   ```
+   sh install.sh  -w xxxx
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+   >
+   > - **-w**: initializes the database password (specified by **gs_initdb**). This parameter is mandatory for security purposes. Make sure that the password complexity requirement is met, including uppercase and lower case letters, characters, and digits.
+   > - **-p**: specifies the MogDB port number. If the port number is not specified, the default value **5432** is used.
+   > - **-h|-help**: displays usage instructions.
+   > - After the installation, the database name is **sgnode**.
+   > - The installation path of the database directory is **/opt/software/mogdb/data/single_node**, in which **/opt/software/mogdb** is the decompression path and **data/single_node** is the newly created database node directory.
+
+5. After the installation is complete, check whether the process is normal by using **ps** and **gs_ctl**.
+
+   ```
+   ps ux | grep mogdb
+   gs_ctl query -D /opt/software/mogdb/data/single_node
+   ```
+
+   Run the **ps** command to display information similar to the following:
+
+   ```
+   omm      24209 11.9  1.0 1852000 355816 pts/0  Sl   01:54   0:33 /opt/software/mogdb/bin/mogdb -D /opt/software/mogdb/single_node
+   omm      20377  0.0  0.0 119880  1216 pts/0    S+   15:37   0:00 grep --color=auto mogdb
+   ```
+
+   Run the **gs_ctl** command to display information similar to the following:
+
+   ```
+   gs_ctl query ,datadir is /opt/software/mogdb/data/single_node
+   HA state:
+       local_role                     : Normal
+       static_connections             : 0
+       db_state                       : Normal
+       detail_information             : Normal
+   
+   Senders info:
+       No information
+   
+    Receiver info:
+   No information
+   ```
+
+6. Use MogDB
+
+```
+-- Configure PATH
+echo "PATH=/opt/software/mogdb/bin:\$PATH" >> /home/omm/.bash_profile
+source ~/.bash_profile
+-bash: ulimit: open files: cannot modify limit: Operation not permitted
+(The default setting fd available size exceeds the system setting, you can ignore the setting)
+
+-- Login to MogDB
+gsql -d postgres -p 5432 -r
+gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+Non-SSL connection (SSL connection is recommended when requiring high-security)
+Type "help" for help.
+
+mogdb=#
+```
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/installation-guide/simplified-installation-process/3-installation-on-primary-standby-nodes.md b/product/en/docs-mogdb/v3.0/installation-guide/simplified-installation-process/3-installation-on-primary-standby-nodes.md
new file mode 100644
index 0000000000000000000000000000000000000000..99c6e96621e083b67b3dabac9d8cb61a30a0aadb
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/installation-guide/simplified-installation-process/3-installation-on-primary-standby-nodes.md
@@ -0,0 +1,115 @@
+---
+title: Installation on Primary/Standby Nodes
+summary: Installation on Primary/Standby Nodes
+author: Zhang Cuiping
+date: 2021-06-15
+---
+
+# Installation on Primary/Standby Nodes
+
+This section takes openEuler system as an example to introduce how to install MogDB on primary/standby  nodes.
+
+1. Create directory, user, group, and authorize them.
+
+   ```
+   groupadd dbgrp -g 2000
+   useradd omm -g 2000 -u 2000
+   mkdir -p /opt/software/mogdb
+   chown -R omm:dbgrp /opt/software/mogdb
+   ```
+
+2. Decompress the MogDB package to the installation directory.
+
+   ```
+   su - omm
+   cd /opt/software/mogdb/
+   tar -jxf MogDB-x.x.x-openEuler-64bit.tar.bz2 -C /opt/software/mogdb/
+   ```
+
+3. Go to the **simpleInstall** directory.
+
+   ```
+   cd /opt/software/mogdb/simpleInstall
+   ```
+
+4. Run the **install.sh -w** command to install MogDB.
+
+   ```
+   sh install.sh  -w xxxx  --multinode
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif)  **NOTE:**
+   >
+   > - **-w**: initializes the database password (specified by **gs_initdb**). This parameter is mandatory for security purposes. Make sure that the password complexity requirement is met, including uppercase and lower case letters, characters, and digits.
+   > - **-p**: specifies the port number of the primary MogDB node. The default value is **5432**. The port number of the standby node is that of the primary node plus 200. The default port number is **5632**.
+   > - **-multinode**: determines whether the installation is performed on a single node or on primary/standby nodes.
+   > - **-h|-help**: displays usage instructions.
+   > - After the installation, the primary database node name is **nodename1** and the standby database node name is **nodename2**.
+   > - The installation path of the primary database node directory is **/opt/software/mogdb/data/master**, and that of the standby node directory is **/opt/software/mogdb/data/slave**, in which **/opt/software/mogdb** is the decompression path, and **data/master(slave)** is the newly created database node directory.
+
+5. After the installation is complete, check whether the process is normal by using **ps** and **gs_ctl**.
+
+   ```
+   ps ux | grep mogdb
+   gs_ctl query -D /opt/software/mogdb/data/master
+   ```
+
+   Run the **ps** command to display information similar to the following:
+
+   ```
+   omm  4879 11.8 1.1 2082452 373832 pts/0  Sl   14:26   8:29 /opt/software/mogdb/bin/mogdb -D /opt/software/mogdb/data/master -M primary
+   omm  5083  1.1  0.9 1819988 327200 pts/0  Sl   14:26   0:49 /opt/software/mogdb/bin/mogdb -D /opt/software/mogdb/data/slave -M standby
+   omm      20377  0.0  0.0 119880  1216 pts/0    S+   15:37   0:00 grep --color=auto mogdb
+   ```
+   
+   Run the **gs_ctl** command to display information similar to the following:
+
+   ```
+   gs_ctl query ,datadir is /opt/software/mogdb/data/master
+   HA state:
+       local_role                     : Primary
+       static_connections             : 1
+       db_state                       : Normal
+       detail_information             : Normal
+   
+   Senders info:
+       sender_pid                     : 5165
+       local_role                     : Primary
+       peer_role                      : Standby
+       peer_state                     : Normal
+       state                          : Streaming
+       sender_sent_location           : 0/4005148
+       sender_write_location          : 0/4005148
+       sender_flush_location          : 0/4005148
+       sender_replay_location         : 0/4005148
+       receiver_received_location     : 0/4005148
+       receiver_write_location        : 0/4005148
+       receiver_flush_location        : 0/4005148
+       receiver_replay_location       : 0/4005148
+       sync_percent                   : 100%
+       sync_state                     : Sync
+       sync_priority                  : 1
+       sync_most_available            : Off
+       channel                        : 10.244.44.52:27001-->10.244.44.52:35912
+   
+    Receiver info:
+   No information
+   ```
+
+6. Use MogDB
+
+```
+-- Configure PATH
+echo "PATH=/opt/software/mogdb/bin:\$PATH" >> /home/omm/.bash_profile
+source ~/.bash_profile
+-bash: ulimit: open files: cannot modify limit: Operation not permitted
+(The default setting fd available size exceeds the system setting, you can ignore the setting)
+
+-- Login to MogDB
+gsql -d postgres -p 5432 -r
+gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+Non-SSL connection (SSL connection is recommended when requiring high-security)
+Type "help" for help.
+
+mogdb=#
+```
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/installation-guide/standard-installation/1-installation-overview.md b/product/en/docs-mogdb/v3.0/installation-guide/standard-installation/1-installation-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..93dee0675e6c3b6fd13f92df0325148ed6dc1385
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/installation-guide/standard-installation/1-installation-overview.md
@@ -0,0 +1,10 @@
+---
+title: Installation Overview
+summary: Installation Overview
+author: Zhang Cuiping
+date: 2021-04-02
+---
+
+# Installation Overview
+
+MogDB can be deployed in standalone or in standalone HA mode. In standalone mode, multiple database instances can be deployed on a single host. However, this mode is not recommended for data security purposes. In the standalone HA deployment mode, one primary server and at least one standby server are supported, and a maximum of eight standby servers are supported.
diff --git a/product/en/docs-mogdb/v3.0/installation-guide/standard-installation/2-environment-requirement.md b/product/en/docs-mogdb/v3.0/installation-guide/standard-installation/2-environment-requirement.md
new file mode 100644
index 0000000000000000000000000000000000000000..66291155c991f4bf837f3fc8da7a5af744df91e6
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/installation-guide/standard-installation/2-environment-requirement.md
@@ -0,0 +1,57 @@
+---
+title: Environment Requirement
+summary: Environment Requirement
+author: Zhang Cuiping
+date: 2021-04-2
+---
+
+# Environment Requirement
+
+## Hardware Requirements
+
+The following table describes the minimum hardware requirements of MogDB. When planning the hardware configuration of a product, consider the data scale and expected database response speed. Plan hardware as required.
+
+| Item                 | Description                                                  |
+| -------------------- | ------------------------------------------------------------ |
+| Minimum memory       | Minimum 32 GB of memory is required for function debugging. <br />In performance tests and commercial deployment, the single-instance deployment is performed. It is recommended that the memory be greater than 128 GB.  <br />Complex queries require much memory but the memory may be insufficient in high-concurrency scenarios. In this case, it is recommended that a large-memory server or load management be used to restrict concurrences on the system. |
+| CPU                  | Minimum one 8-core 2.0 GHz CPU is required for function debugging.  <br />In performance tests and commercial deployment, the single-instance deployment is performed. It is recommended that one 16-core 2.0 GHz CPU be used.  <br />You can set CPUs to hyper-threading or non-hyper-threading mode, but ensure the setting is consistent across all the MogDB nodes. |
+| Hard disk            | Hard disks used for installing the MogDB must meet the following requirements: <br />-  At least 1 GB is used to install the MogDB application. <br />- About 300 MB is used for each host to store metadata.  <br />- More than 70% of available disk space is reserved to store data.  <br />You are advised to configure the system disk to RAID 1 and data disk to RAID 5 and plan four groups of RAID 5 data disks for installing MogDB. RAID configuration is not described in this document. You can configure RAID by following instructions in the hardware vendors' manuals or using common methods found on the Internet. Set **Disk Cache Policy** to **Disabled** to avoid data loss in an unexpected power-off. <br />MogDB supports using an SSD with the SAS interface and NVMe protocol deployed in RAID mode as the primary storage device of the database. |
+| Network requirements | Minimum 300 Mbit/s Ethernet is required.  <br />You are advised to bond two NICs for redundancy. The configuration is not described in this document. You can configure it by following instructions in the manual provided by the hardware manufacturer or using the methods provided on the Internet.<br />If bonds are configured for the MogDB, ensure the consistency among these bond modes, because inconsistent bond modes may cause MogDB running exceptions. |
+
+## Software Requirements
+
+| Software          | Description                                                  |
+| ----------------- | ------------------------------------------------------------ |
+| rdtscp Instruction Set (x86)  | Run the `lscpu \| grep rdtscp` command to see if the rdtscp instruction set is supported.            |
+| bmi2 Instruction Set (CentOS)  | Run the `lscpu \| grep bmi2` command to see if the bmi2 instruction set is supported.            |
+| Tool              | Huawei JDK 1.8.0, psmisc, and bzip2                          |
+| Python            | - openEuler: Python 3.7.X is supported.<br />- CentOS: Python 3.6.X is supported.<br />- Kirin: Python 3.7.X is supported.<br />NOTE:<br />Python needs to be compiled in -enable-shared mode. |
+
+## Operating System Requirements
+
+| OS              | x86                        | ARM           |
+| --------------- | -------------------------- | ------------- |
+| CentOS 7.x      | Intel, AMD, Hygon, ZHAOXIN | Being adapted |
+| Redhat 7.x      | Intel, AMD, Hygon, ZHAOXIN | Being adapted |
+| openEuler 20.03 | Intel, AMD, Hygon, ZHAOXIN | Kunpeng       |
+| Kylin V10       | Intel, AMD, Hygon, ZHAOXIN | Kunpeng       |
+| UOS V20-D/V20-E | Intel, AMD, Hygon, ZHAOXIN | Kunpeng       |
+| UOS V20-A       | Intel, AMD, Hygon, ZHAOXIN | Being adapted |
+
+## Software Dependency Requirements
+
+You are advised to use the default installation packages of the following dependent software in the listed OS installation CD-ROMs or sources. If the following software does not exist, refer to the recommended versions of the software.
+
+| Software       | Recommended Version |
+| :------------- | :------------------ |
+| libaio-devel   | 0.3.109-13          |
+| flex           | 2.5.31 or later     |
+| bison          | 2.7-4               |
+| ncurses-devel  | 5.9-13.20130511     |
+| glibc-devel    | 2.17-111            |
+| patch          | 2.7.1-10            |
+| lsb_release    | 4.1                 |
+| readline_devel | 7.0-13              |
+| openSSH        | 8.4p1               |
+
+Note: Installation is supported even if there is only 4 GB memory in actual test. If the memory size is greater than 4 GB, it does not need to be modified.
diff --git a/product/en/docs-mogdb/v3.0/installation-guide/standard-installation/3-modifying-os-configuration.md b/product/en/docs-mogdb/v3.0/installation-guide/standard-installation/3-modifying-os-configuration.md
new file mode 100644
index 0000000000000000000000000000000000000000..5b3edfa47172b0008cdec7caf066f41640201baf
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/installation-guide/standard-installation/3-modifying-os-configuration.md
@@ -0,0 +1,241 @@
+---
+title: Modifying OS Configuration
+summary: Modifying OS Configuration
+author: Zhang Cuiping
+date: 2021-04-2
+---
+
+# Modifying OS Configuration
+
+## Disabling the OS Firewall
+
+To ensure that the MogDB can work properly when the firewall is enabled, related services, protocols, IP addresses, and ports need to be added to the firewall whitelist of each host in the MogDB.
+
+Take openEuler OS as an example. Assume that the MogDB information is listed in [Table 1](#mogdb).
+
+**Table 1** Information of MogDB <a id="mogdb"></a>
+
+| Host Name          | Internal IP Address | External IP Address |
+| :----------------- | :------------------ | :------------------ |
+| plat1              | 192.168.0.11        | 10.10.0.11          |
+| plat2              | 192.168.0.12        | 10.10.0.12          |
+| plat3              | 192.168.0.13        | 10.10.0.13          |
+| plat4              | 192.168.0.14        | 10.10.0.14          |
+| Management network | -                   | 10.10.64.236        |
+
+**Procedure**
+
+Currently, EulerOS can be installed only when the firewall is disabled.
+
+1. Set the value of **SELINUX** in the **/etc/selinux/config** file to **disabled**. <a id="1"> </a>
+   a. Run the **vim** command to open the **config** file.
+
+   ```bash
+   vim /etc/selinux/config
+   ```
+
+   b. Change the value of **SELINUX** to **disabled** and run the **:wq** command to save the change and exit.
+
+   ```bash
+   SELINUX=disabled
+   ```
+
+2. Restart the OS.
+
+   ```bash
+   reboot
+   ```
+
+3. Check whether the firewall is disabled.
+
+   ```bash
+   systemctl status firewalld
+   ```
+
+   If the firewall status is **active (running)**, the firewall is not disabled. Go to [4](#4).
+
+   If the firewall status is **inactive (dead)**, you do not need to disable the firewall.
+
+4. Disable the firewall. <a id="4"> </a>
+
+   ```bash
+   systemctl disable firewalld.service
+   systemctl stop firewalld.service
+   ```
+
+5. Repeat steps [1](#1) to [4](#4) on other hosts.
+
+## Setting Character Set Parameters
+
+Set the same character set for all database nodes. You can add **export LANG=Unicode** in the **/etc/profile** file.
+
+```bash
+vim /etc/profile
+```
+
+## Setting the Time Zone and Time
+
+Set the same time zone for all database nodes by copying the **/etc/localtime** time zone file to the **/usr/share/zoneinfo/** directory.
+
+```bash
+cp /usr/share/zoneinfo/$Locale/$Time zone /etc/localtime
+```
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+*$Locale/$Time zone* indicates the locale and time zone to be set, for example, **Asia/Shanghai**.
+
+Run the **date -s** command to set the time of each host to the same time. For example:
+
+```bash
+date -s "Sat Sep 27 16:00:07 CST 2020"
+```
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+You can run the **date** command to query the time zone of the host.
+
+## (Optional) Disabling the Swap Memory
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **Note:** Disabling the swap memory ensures the access performance of the database and prevents the buffer memory of the database from being evicted to the disk. If the server memory is small and the memory is overloaded, you can enable the swap memory to ensure normal running.
+
+Run the **swapoff -a** command on each database node to disable the swap memory.
+
+```bash
+swapoff -a
+```
+
+## Setting the NIC MTU
+
+Set the NIC MTU value on each database node to the same value. For x86, the recommended MTU value is 1500. For ARM, the recommended MTU value is 8192.
+
+```bash
+ifconfig NIC ID mtu Value
+```
+
+## Disabling RemoveIPC
+
+On each database node, disable RemoveIPC. For CentOS, skip this step.
+
+**Procedure**
+
+1. Change the value of **RemoveIPC** in the **/etc/systemd/logind.conf** file to **no**. <a id="01"></a>.
+
+   a. Run the **vim** command to open the **logind.conf** file.
+
+   ```bash
+   vim  /etc/systemd/logind.conf
+   ```
+
+   b. Change the value of **RemoveIPC** to **no**.
+
+   ```bash
+   RemoveIPC=no
+   ```
+
+2. Change the value of **RemoveIPC** in the **/usr/lib/systemd/system/systemd-logind.service** file to **no**.
+
+   a. Run the **vim** command to open the **systemd-logind.service** file.
+
+   ```bash
+   vim /usr/lib/systemd/system/systemd-logind.service
+   ```
+
+   b. Change the value of **RemoveIPC** to **no**.
+
+   ```bash
+   RemoveIPC=no
+   ```
+
+3. Reload configuration parameters.
+
+   ```bash
+   systemctl daemon-reload
+   systemctl restart systemd-logind
+   ```
+
+4. Check whether the modification takes effect. <a id="04"> </a>
+
+   ```bash
+   loginctl show-session | grep RemoveIPC
+   systemctl show systemd-logind | grep RemoveIPC
+   ```
+
+5. Repeat steps [1](#01) to [4](#04) on other hosts.
+
+## Setting Remote Login of User root
+
+During the MogDB installation, the user **root** is required for remote login. This section describes how to set the user **root** for remote login.
+
+1. Modify the **PermitRootLogin** configuration to enable remote login of user **root**.
+
+   a. Open the **sshd_config** file.
+
+   ```bash
+   vim /etc/ssh/sshd_config
+   ```
+
+   b. Modify permissions of user **root** using either of the following methods:
+
+   - Comment out **PermitRootLogin no**.
+
+     ```bash
+     #PermitRootLogin no
+     ```
+
+   - Set the value of **PermitRootLogin** to **yes**.
+
+     ```bash
+     PermitRootLogin yes
+     ```
+
+   c. Run the **:wq** command to save the modification and exit.
+
+2. Modify the **Banner** configuration to delete the welcome information displayed when you connect to the system. The welcome information affects the return result of remote operations during the installation.
+
+   a. Open the **sshd_config** file.
+
+   ```bash
+   vim /etc/ssh/sshd_config
+   ```
+
+   b. Comment out the line where **Banner** is located.
+
+   ```bash
+   #Banner XXXX
+   ```
+
+   c. Run the **:wq** command to save the modification and exit.
+
+3. Run the following command to validate the settings:
+
+   ```bash
+   systemctl restart sshd.service
+   ```
+
+4. Re-log in to the system as user **root**.
+
+   ```bash
+   ssh xxx.xxx.xxx.xxx
+   ```
+
+   ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+   *xxx.xxx.xxx.xxx* indicates the IP address of the MogDB installation environment.
+
+## Dynamically Disabling Transparent Huge Page
+
+```bash
+echo never > /sys/kernel/mm/transparent_hugepage/enabled
+```
+
+For example: openEuler
+
+```bash
+/root~ # cat /etc/system-release
+openEuler release 20.03 (LTS)
+/etc/default~ # echo never > /sys/kernel/mm/transparent_hugepage/enabled
+/etc/default~ # cat /sys/kernel/mm/transparent_hugepage/enabled
+always madvise [never]
+```
+
+If the transparent huge page function is successfully disabled, [never] will be displayed.
+
+Disabling the transparent huge page function can reduce the overhead of the host OS to achieve more stable performance.
diff --git a/product/en/docs-mogdb/v3.0/installation-guide/standard-installation/4-installing-mogdb.md b/product/en/docs-mogdb/v3.0/installation-guide/standard-installation/4-installing-mogdb.md
new file mode 100644
index 0000000000000000000000000000000000000000..75cd486e608fb9ba90e4bbe9353ffde62c3f10c5
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/installation-guide/standard-installation/4-installing-mogdb.md
@@ -0,0 +1,494 @@
+---
+title: Installing MogDB
+summary: Installing MogDB
+author: Zhang Cuiping
+date: 2021-04-2
+---
+
+# Installing MogDB
+
+## Creating an XML Configuration File
+
+Before installing MogDB, you need to create the XML file. The XML file contains the information about the server where MogDB is deployed, installation path, IP address, and port number. This file is used to guide how to deploy the MogDB. You need to configure the XML configuration file according to the actual deployment requirements.
+
+<br/>
+
+**Parameter description**
+
+<table>
+  <tr>
+    <td><b>Parameter</b></td>
+    <td><b>Description</b></td>
+  </tr>
+  <tr>
+    <td>clusterName</td>
+    <td>MogDB name.</td>
+  </tr>
+  <tr>
+    <td>nodeNames</td>
+    <td>Host name in the MogDB.</td>
+  </tr>
+  <tr>
+    <td>backIp1s</td>
+    <td>
+      Intranet IP address of the host in the backend storage network. All the
+      MogDB hosts communicate with each other on this network.
+    </td>
+  </tr>
+  <tr>
+    <td>gaussdbAppPath</td>
+    <td>
+      Installation directory of the MogDB program. This directory must meet the
+      following requirements:<br />- The disk space is greater than 1 GB.<br />-
+      This directory is independent of other directories required by the
+      database.
+    </td>
+  </tr>
+  <tr>
+    <td>gaussdbLogPath</td>
+    <td>
+      Directory that stores run logs and operation logs of the MogDB. This
+      directory must meet the following requirements:<br />- You are advised to
+      plan the disk space based on the number of database nodes on the host.
+      Reserve 1 GB space for database nodes and reserve redundant space.<br />-
+      This directory is independent of other directories required by the
+      MogDB.<br />
+      This directory is optional. If the directory is not specified,
+      <b>$GAUSSLOG/installation uername</b> will be specified as the log
+      directory by default during MogDB installation.
+    </td>
+  </tr>
+  <tr>
+    <td>tmpdbPath</td>
+    <td>
+      Directory for storing temporary database files.<br />
+      If <b>tmpdbPath</b> is not set, the file is stored in
+      <b>/opt/mogdb/tools/perfadm_db</b> by default.
+    </td>
+  </tr>
+  <tr>
+    <td>gaussdbToolPath</td>
+    <td>
+      Directory for storing MogDB system tools. This directory is used to store
+      tools for mutual trust. This directory must meet the following
+      requirements:<br />- The disk space is greater than 100 MB. <br />- This
+      directory cannot be changed and is independent of other directories
+      required by the database.<br />
+      This directory is optional. If this parameter is not specified,
+      <b>/opt/mogdb/tools</b> is specified as the database system tool directory
+      by default during MogDB installation.
+    </td>
+  </tr>
+  <tr>
+    <td>corePath</td>
+    <td>Directory for storing the MogDB core file.</td>
+  </tr>
+  <tr>
+    <td>clusterType</td>
+    <td>
+      MogDB type cluster type. This parameter is optional.<br />
+      <b>single-inst</b> indicates the standalone cluster with one primary node
+      and multiple standby nodes.
+    </td>
+  </tr>
+</table>
+
+### Example
+
+#### Configuration File for Single-Instance Deployment
+
+```xml
+<?xml version="1.0" encoding="UTF-8"?>
+<ROOT>
+    <!-- Overall information about MogDB -->
+    <CLUSTER>
+        <PARAM name="clusterName" value="dbCluster" />
+        <PARAM name="nodeNames" value="node1" />
+        <PARAM name="backIp1s" value="192.168.0.11"/>
+        <PARAM name="gaussdbAppPath" value="/opt/mogdb/app" />
+        <PARAM name="gaussdbLogPath" value="/var/log/mogdb" />
+        <PARAM name="gaussdbToolPath" value="/opt/mogdb/tools" />
+        <PARAM name="corePath" value="/opt/mogdb/corefile"/>
+        <PARAM name="clusterType" value="single-inst"/>
+    </CLUSTER>
+
+    <!-- Information about node deployment on each server  -->
+    <DEVICELIST>
+        <!-- Information about the node deployment on node1  -->
+        <DEVICE sn="1000001">
+            <PARAM name="name" value="node1"/>
+            <PARAM name="azName" value="AZ1"/>
+            <PARAM name="azPriority" value="1"/>
+            <!-- If only one NIC is available for the server, set backIP1 and sshIP1 to the same IP address. -->
+            <PARAM name="backIp1" value="192.168.0.11"/>
+            <PARAM name="sshIp1" value="192.168.0.11"/>
+
+            <!--dbnode-->
+            <PARAM name="dataNum" value="1"/>
+            <PARAM name="dataPortBase" value="26000"/>
+            <PARAM name="dataNode1" value="/mogdb/data/db1"/>
+        </DEVICE>
+    </DEVICELIST>
+</ROOT>
+```
+
+> Note: The host name and IP address need to be replaced. For other parameters, retain the default values.
+
+#### Configuration File for One Primary and One Standby
+
+```xml
+<?xml version="1.0" encoding="UTF-8"?>
+<ROOT>
+    <!-- Overall information about MogDB -->
+    <CLUSTER>
+        <PARAM name="clusterName" value="dbCluster" />
+        <PARAM name="nodeNames" value="node1,node2" />
+        <PARAM name="backIp1s" value="192.168.0.11,192.168.0.12"/>
+        <PARAM name="gaussdbAppPath" value="/opt/mogdb/app" />
+        <PARAM name="gaussdbLogPath" value="/var/log/mogdb" />
+        <PARAM name="gaussdbToolPath" value="/opt/mogdb/tools" />
+        <PARAM name="corePath" value="/opt/mogdb/corefile"/>
+        <PARAM name="clusterType" value="single-inst"/>
+    </CLUSTER>
+    <!-- Information about node deployment on each server -->
+    <DEVICELIST>
+        <!-- Information about the node deployment on node1 -->
+        <DEVICE sn="1000001">
+            <PARAM name="name" value="node1"/>
+            <PARAM name="azName" value="AZ1"/>
+            <PARAM name="azPriority" value="1"/>
+            <!-- If only one NIC is available for the server, set backIP1 and sshIP1 to the same IP address. -->
+            <PARAM name="backIp1" value="192.168.0.11"/>
+            <PARAM name="sshIp1" value="192.168.0.11"/>
+
+            <!--dbnode-->
+            <PARAM name="dataNum" value="1"/>
+            <PARAM name="dataPortBase" value="26000"/>
+            <PARAM name="dataNode1" value="/mogdb/data/db1,node2,/mogdb/data/db1"/>
+        </DEVICE>
+
+        <!-- Node deployment information on node2. The value of name is the host name.  -->
+        <DEVICE sn="1000002">
+            <PARAM name="name" value="node2"/>
+            <PARAM name="azName" value="AZ1"/>
+            <PARAM name="azPriority" value="1"/>
+            <!-- If only one NIC is available for the server, set backIP1 and sshIP1 to the same IP address. -->
+            <PARAM name="backIp1" value="192.168.0.12"/>
+            <PARAM name="sshIp1" value="192.168.0.12"/>
+        </DEVICE>
+    </DEVICELIST>
+</ROOT>
+```
+
+> Note: The host name and IP address need to be replaced. For other parameters, retain the default values.
+
+#### Configuration File for One Primary and Two Standbys
+
+```xml
+<?xml version="1.0" encoding="UTF-8"?>
+<ROOT>
+    <!-- Overall information about MogDB -->
+    <CLUSTER>
+        <PARAM name="clusterName" value="dbCluster" />
+        <PARAM name="nodeNames" value="node1,node2,node3" />
+        <PARAM name="backIp1s" value="192.168.0.11,192.168.0.12, 192.168.0.13"/>
+        <PARAM name="gaussdbAppPath" value="/opt/mogdb/app" />
+        <PARAM name="gaussdbLogPath" value="/var/log/mogdb" />
+        <PARAM name="gaussdbToolPath" value="/opt/mogdb/tools" />
+        <PARAM name="corePath" value="/opt/mogdb/corefile"/>
+        <PARAM name="clusterType" value="single-inst"/>
+    </CLUSTER>
+    <!-- Information about node deployment on each server -->
+    <DEVICELIST>
+        <!-- Information about the node deployment on node1 -->
+        <DEVICE sn="1000001">
+            <PARAM name="name" value="node1"/>
+            <PARAM name="azName" value="AZ1"/>
+            <PARAM name="azPriority" value="1"/>
+            <!-- If only one NIC is available for the server, set backIP1 and sshIP1 to the same IP address. -->
+            <PARAM name="backIp1" value="192.168.0.11"/>
+            <PARAM name="sshIp1" value="192.168.0.11"/>
+
+            <!--dbnode-->
+            <PARAM name="dataNum" value="1"/>
+            <PARAM name="dataPortBase" value="26000"/>
+            <PARAM name="dataNode1" value="/mogdb/data/db1,node2,/mogdb/data/db1, node3,/mogdb/data/db1"/>
+        </DEVICE>
+
+        <!-- Node deployment information on node2. The value of name is the host name.  -->
+        <DEVICE sn="1000002">
+            <PARAM name="name" value="node2"/>
+            <PARAM name="azName" value="AZ1"/>
+            <PARAM name="azPriority" value="1"/>
+            <!-- If only one NIC is available for the server, set backIP1 and sshIP1 to the same IP address. -->
+            <PARAM name="backIp1" value="192.168.0.12"/>
+            <PARAM name="sshIp1" value="192.168.0.12"/>
+        </DEVICE>
+        <!--Node deployment information on node3. The value of name is the host name.  -->
+        <DEVICE sn="1000003">
+            <PARAM name="name" value="node3"/>
+            <PARAM name="azName" value="AZ1"/>
+            <PARAM name="azPriority" value="1"/>
+            <!-- If only one NIC is available for the server, set backIP1 and sshIP1 to the same IP address. -->
+            <PARAM name="backIp1" value="192.168.0.13"/>
+            <PARAM name="sshIp1" value="192.168.0.13"/>
+        </DEVICE>
+    </DEVICELIST>
+</ROOT>
+```
+
+> Note: The host name and IP address need to be replaced. For other parameters, retain the default values.  **/mogdb/data/db1** indicates the directory for storing data. You can replace the directory according to the actual environment requirement.
+
+<br/>
+
+## Downloading an Installation Package
+
+Before installation, you can visit [MogDB download page](https://www.mogdb.io/en/downloads/mogdb/) to download the installation package applicable to your current operating system and CPU. The following takes the CentOS system as an example. Each installation package and its functions are introduced in the following table.
+
+| **Package**                           | **Function**                                                 |
+| ------------------------------------- | ------------------------------------------------------------ |
+| MogDB-x.x.x-CentOS-x86_64.tar     | Contains all files of all installation packages              |
+| MogDB-x.x.x-CentOS-64bit.tar.bz2      | (Primary/Standby) MogDB primary/standby (Datanode). <br />Stores business data, performs data query tasks, and returns execution results to the client. <br />MogDB instances include primary instance and standby instance, currently supports at most one primary node and eight standby nodes. It is recommended to deploy the primary and standby MogDB instances on different physical servers. |
+| MogDB-x.x.x-CentOS-64bit.sha256       | Hash value of sha256 of MogDB-x.x.x-CentOS-64bit.tar.bz2     |
+| MogDB-x.x.x-CentOS-64bit-Libpq.tar.gz | Driver for C program to access MogDB database                |
+| MogDB-x.x.x-CentOS-64bit-om.tar.gz    | Operation and maintenance management module (Operation Manager). <br />Provides management interfaces and tools for daily database operation and maintenance and configuration management. |
+| MogDB-x.x.x-CentOS-64bit-om.sha256    | Hash value of sha256 of MogDB-x.x.x-CentOS-64bit-om.tar.gz   |
+| MogDB-x.x.x-CentOS-64bit-tools.tar.gz | Client Driver. <br />Receives the access request from the application and returns the execution result to the application.<br /> The client driver is used for communicating with the MogDB instance, sending application SQL commands, and receiving the execution results of the MogDB instance. |
+| upgrade_sql.tar.gz                    | SQL commands required for the upgrade                        |
+| upgrade_sql.sha256                    | Hash value of sha256 of upgrade_sql.tar.gz                   |
+
+<br/>
+
+## Initializing the Environment
+
+This section takes the CentOS OS as an example to describe the environment initialization process.
+
+**Procedure**
+
+1. Run the following command as user root to install the required environment dependency packages.
+
+   ```
+   yum install -y bzip2 libaio-devel flex bison ncurses-devel glibc-devel libxml2-devel patch redhat-lsb-core unzip gcc gcc-c++ perl openssl-devel libffi-devel libtool zlib-devel
+   ```
+
+2. Log in to any host where the MogDB is to be installed as user **root** and create a directory for storing the installation package as planned.
+
+   ```
+   mkdir -p /opt/software/mogdb
+   chmod 755 -R /opt/software
+   ```
+
+3. Upload the software package **MogDB-x.x.x-CentOS-x86_64.tar** and the configuration file **clusterconfig.xml** to the created directory. If the configuration file is not created, run the `vi clusterconfig.xml` command to create and edit the configuration file.
+
+   ```
+   cd /opt/software/mogdb
+   ```
+
+   > Note:
+   > In environments that allow access to external networks, the installation package can be downloaded directly via the `wget` command. For example:
+   >
+   > ```
+   > wget -c https://cdn-mogdb.enmotech.com/mogdb-media/2.1.1/MogDB-2.1.1-CentOS-x86_64.tar
+   > ```
+
+4. Go to the directory for storing the uploaded software package and decompress the following packages in sequence.
+
+   ```
+   tar -xvf  MogDB-x.x.x-CentOS-x86_64.tar
+   tar -xvf  MogDB-x.x.x-CentOS-64bit-om.tar.gz
+   ```
+
+5. Go to the directory for storing tool scripts.
+
+   ```
+   cd /opt/software/mogdb/script
+   ```
+
+6. To ensure that the openssl version is correct, upload the lib library in the software package before pre-installation. Run the following command. **{packagePath}** indicates the directory where the software package is located. The value is **/opt/software/mogdb** in this example.
+
+   ```
+   export LD_LIBRARY_PATH={packagePath}/script/gspylib/clib:$LD_LIBRARY_PATH
+   ```
+
+7. To ensure successful installation, run the following command to check whether the values of **hostname** and **/etc/hostname** are the same. During the pre-installation, **hostname** will be checked.
+
+   ```
+   hostname
+   vi /etc/hostname
+   ```
+
+8. If the openEuler OS is used, comment out **sysctl -w vm.min_free_kbytes=112640 &> /dev/null** in the **performance.sh** file.
+
+   ```
+   vi /etc/profile.d/performance.sh
+   ```
+
+9. Install python3 for the CentOS.
+
+   Note: For standard installation in the CentOS system, you must install Python 3.6.x. Python of a higher version is not supported currently.
+
+   ```
+   wget https://www.python.org/ftp/python/3.6.5/Python-3.6.5.tgz
+   mkdir -p /usr/local/python3
+   tar -zxvf Python-3.6.5.tgz
+   cd Python-3.6.5
+   ./configure --prefix=/usr/local/python3 --enable-shared CFLAGS=-fPIC && make && make install
+   ln -s /usr/local/python3/bin/python3 /usr/bin/python3
+   ln -s /usr/local/python3/bin/pip3 /usr/bin/pip3
+   ```
+
+   > Note:
+   >
+   > - If the error "zipimport.ZipImportError: can't decompress data; zlib not available" is reported, run the **yum -y install zlib*** command and install again.
+   >
+   > - If an error similar to "find:'/run/user/1000/gvfs':Permission denied" is reported, it can be ignored.
+   >
+
+<br/>
+
+## Initializing the Script
+
+```
+/opt/software/mogdb/script/gs_preinstall -U omm -G dbgrp -X /opt/software/mogdb/clusterconfig.xml
+
+Parsing the configuration file.
+Successfully parsed the configuration file.
+Installing the tools on the local node.
+Successfully installed the tools on the local node.
+Distributing package.
+Begin to distribute package to tool path.
+Successfully distribute package to tool path.
+Begin to distribute package to package path.
+Successfully distribute package to package path.
+Successfully distributed package.
+Installing the tools in the cluster.
+Successfully installed the tools in the cluster.
+Checking hostname mapping.
+Successfully checked hostname mapping.
+Checking OS version.
+Successfully checked OS version.
+Creating cluster's path.
+Successfully created cluster's path.
+Setting SCTP service.
+Successfully set SCTP service.
+Set and check OS parameter.
+Setting OS parameters.
+Successfully set OS parameters.
+Set and check OS parameter completed.
+Preparing CRON service.
+Successfully prepared CRON service.
+Preparing SSH service.
+Successfully prepared SSH service.
+Setting user environmental variables.
+Successfully set user environmental variables.
+Configuring alarms on the cluster nodes.
+Successfully configured alarms on the cluster nodes.
+Setting the dynamic link library.
+Successfully set the dynamic link library.
+Setting Cgroup.
+Successfully set Cgroup.
+Set ARM Optimization.
+Successfully set ARM Optimization.
+Setting finish flag.
+Successfully set finish flag.
+Preinstallation succeeded.
+```
+
+> Note:
+>
+> - During the running, the system will ask whether to create the user omm, you need to enter **yes**. Additionally, you need to enter related passwords and make sure that the password complexity requirement is met, including uppercase and lower case letters, characters, and digits, such as **Enmo@123**.
+>
+> - If an error similar to the following is displayed, the version of Python is high.
+>
+>   ```
+>   [root@localhost mogdb]# /opt/software/mogdb/script/gs_preinstall -U omm -G dbgrp -X /mogdb/etc/mogdb_clusterconfig.xml
+>   Failed to execute cmd: rm -rf '/opt/software/mogdb/script/gspylib/os/./../../../lib/psutil/_psutil_linux.so' && cp -r '/opt/software/mogdb/script/gspylib/os/./../../../lib/psutil/_psutil_linux.so_3.9' '/opt/software/mogdb/script/gspylib/os/./../../../lib/psutil/_psutil_linux.so' && rm -rf '/opt/software/mogdb/script/gspylib/os/./../../../lib/psutil/_psutil_posix.so' && cp -r '/opt/software/mogdb/script/gspylib/os/./../../../lib /psutil/_psutil_posix.so_3.9' '/opt/software/mogdb/script/gspylib/os/./../../../lib/psutil/_psutil_posix.so' . Error:
+>   cp: cannot stat '/opt/software/mogdb/script/gspylib/os/./../../../lib/psutil/_psutil_linux.so_3.9': No such file or directory
+>   ```
+
+<br/>
+
+## Performing the Installation
+
+Modify the user and user group of the **lib** and **script** folder in the installation directory:
+
+```
+chown -R omm:dbgrp /opt/software/mogdb/lib
+chown -R omm:dbgrp /opt/software/mogdb/script
+```
+
+Run the following commands in sequence to install MogDB:
+
+```
+su - omm
+gs_install -X /opt/software/mogdb/clusterconfig.xml --gsinit-parameter="--locale=en_US.UTF-8" --gsinit-parameter="--encoding=UTF-8"
+
+Parsing the configuration file.
+Check preinstall on every node.
+Successfully checked preinstall on every node.
+Creating the backup directory.
+Successfully created the backup directory.
+begin deploy..
+Installing the cluster.
+begin prepare Install Cluster..
+Checking the installation environment on all nodes.
+begin install Cluster..
+Installing applications on all nodes.
+Successfully installed APP.
+begin init Instance..
+encrypt ciper and rand files for database.
+Please enter password for database:
+Please repeat for database:
+begin to create CA cert files
+The sslcert will be generated in /opt/mogdb/cluster/app/share/sslcert/om
+Cluster installation is completed.
+Configuring.
+Deleting instances from all nodes.
+Successfully deleted instances from all nodes.
+Checking node configuration on all nodes.
+Initializing instances on all nodes.
+Updating instance configuration on all nodes.
+Check consistence of memCheck and coresCheck on DN nodes.
+Successful check consistence of memCheck and coresCheck on all nodes.
+Configuring pg_hba on all nodes.
+Configuration is completed.
+Successfully started cluster.
+Successfully installed application.
+```
+
+> Note: During the installation, the user needs to enter the password of the database as prompted. The password must meet the complexity requirement. To ensure that the user can use the database normally, make note of the database password.
+>
+
+<br/>
+
+## Connecting To MogDB
+
+After installation, you can connect to MogDB by running **gsql -d postgres -p 26000 -r** under the **omm** user, where **-p 26000** is the database port number. You need to replace it according to the actual situation. Additionally, you can run the **\copyright** command to check the copyright information.
+
+```sql
+[omm@ecs-saving-0006 ~]$ gsql -d postgres -p 26000 -r
+gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+Non-SSL connection (SSL connection is recommended when requiring high-security)
+Type "help" for help.
+
+MogDB=# \copyright
+MogDB Kernel Database Management System
+Copyright (c) Yunhe Enmo (Beijing) Information Technology Co., Ltd. Copyright © 2009-2022 , All rights reserved.
+```
+
+<br/>
+
+## Modifying the Synchronous Node
+
+By default, the standby database is an asynchronous database. If you need to configure it as a synchronous database, configure it as follows:
+
+```
+[omm@ecs-saving-0006 ~]$ sed -i "/synchronous_standby_names/csynchronous_standby_names = 'dn_6002'" /gaussdb/data/db1/postgresql.conf
+[omm@ecs-saving-0006 ~]$ gs_om -t restart
+```
+
+The value **dn_6002** is special, which is fixed. It is **dn_6001** for the primary database, **dn_6002** for the first standby database, and **dn_6003** for the second standby database in sequence.
+
+'dn_6002,dn_6003'  indicates that the first and second standby databases are synchronous databases.
+
+The data storing directory needs to be replaced as required.
diff --git a/product/en/docs-mogdb/v3.0/installation-guide/standard-installation/5-verifying-installation.md b/product/en/docs-mogdb/v3.0/installation-guide/standard-installation/5-verifying-installation.md
new file mode 100644
index 0000000000000000000000000000000000000000..e700798858461fa7abae17e4de1abbd6d2f34cd9
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/installation-guide/standard-installation/5-verifying-installation.md
@@ -0,0 +1,32 @@
+---
+title: Verifying the Installation
+summary: Verifying the Installation
+author: Zhang Cuiping
+date: 2021-04-2
+---
+
+# Verifying the Installation
+
+Use the **gs_om** tool provided by MogDB to check the database status.
+
+**Prerequisites**
+
+The MogDB database has been installed.
+
+**Procedure**
+
+1. Log in to the server as user **omm**.
+
+2. Run the following command to check whether the database is normal. If the value of **cluster_state** is **Normal**, the database is running properly.
+
+   ```
+   gs_om -t status
+   ```
+
+3. After the database is installed, a database named **postgres** is generated by default. When connecting to a database for the first time, you can connect to this database.
+
+   In the following command, **postgres** indicates the name of the database to be connected, and **26000** indicates the port number of the primary database node, that is, the value of **dataPortBase** in the XML configuration file. Replace the values as required.
+
+   ```
+   gsql -d postgres -p 26000
+   ```
diff --git a/product/en/docs-mogdb/v3.0/installation-guide/standard-installation/6-uninstallation.md b/product/en/docs-mogdb/v3.0/installation-guide/standard-installation/6-uninstallation.md
new file mode 100644
index 0000000000000000000000000000000000000000..970dd4b578088139580aff2bb3068bcf56b2cf10
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/installation-guide/standard-installation/6-uninstallation.md
@@ -0,0 +1,159 @@
+---
+title: Uninstalling the MogDB
+summary: Uninstalling the MogDB
+author: Zhang Cuiping
+date: 2021-04-2
+---
+
+# Uninstalling the MogDB
+
+The process of uninstalling the MogDB includes uninstalling the MogDB and clearing the environment of the MogDB server.
+
+## Executing Uninstallation
+
+The MogDB provides an uninstallation script to help users uninstall the MogDB.
+
+**Procedure**
+
+1. Log in as the OS user **omm** to the primary node of the database.
+
+2. Execute the **gs_uninstall** script to uninstall the MogDB.
+
+   ```bash
+   gs_uninstall --delete-data
+   ```
+
+   Alternatively, locally uninstall each node of the MogDB.
+
+   ```bash
+   gs_uninstall --delete-data -L
+   ```
+
+**Examples**
+
+Execute the **gs_uninstall** script to uninstall the MogDB.
+
+```bash
+gs_uninstall --delete-data
+Checking uninstallation.
+Successfully checked uninstallation.
+Stopping the cluster.
+Successfully stopped the cluster.
+Successfully deleted instances.
+Uninstalling application.
+Successfully uninstalled application.
+Uninstallation succeeded.
+```
+
+Execute the **gs_uninstall** script to perform single-node uninstallation.
+
+```bash
+gs_uninstall --delete-data
+Checking uninstallation.
+Successfully checked uninstallation.
+Stopping the cluster.
+Successfully stopped the cluster.
+Successfully deleted instances.
+Uninstalling application.
+Successfully uninstalled application.
+Uninstallation succeeded.
+```
+
+**Troubleshooting**
+
+If the uninstallation fails, locate faults by following the log information provided in the **$GAUSSLOG/om/gs_uninstall-YYYY-MM-DD_HHMMSS.log** file.
+
+## Deleting Cluster Configurations
+
+After the MogDB is uninstalled, execute the **gs_postuninstall** script to delete configurations from all servers in the MogDB if you do not need to re-deploy the MogDB using these configurations. These configurations are made by the **gs_preinstall** script.
+
+**Prerequisites**
+
+- The MogDB uninstallation task has been successfully executed.
+- User **root** is trustworthy and available.
+- Only user **root** is authorized to run the **gs_postuninstall** command.
+
+**Procedure**
+
+1. Log in to the MogDB server as user **root**.
+
+2. Check whether the mutual trust has been established between the users **root**. If not, manually establish the mutual trust.
+
+   Run the **ssh** *Host name* command to check whether mutual trust has been successfully established. Then, enter **exit**.
+
+   ```bash
+   plat1:~ # ssh plat2
+   Last login: Tue Jan  5 10:28:18 2016 from plat1
+   Huawei's internal systems must only be used for conducting Huawei's business or for purposes authorized by Huawei management.Use is subject to audit at any time by Huawei management.
+   plat2:~ # exit
+   logout
+   Connection to plat2 closed.
+   plat1:~ #
+   ```
+
+3. Go to the following path:
+
+   ```bash
+   cd /opt/software/MogDB/script
+   ```
+
+4. Run the **gs_postuninstall** command to clear the environment. If the cluster is installed in environment variable separation mode, run the **source** command to obtain the environment variable separation file **ENVFILE**.
+
+   ```bash
+   ./gs_postuninstall -U omm -X /opt/software/MogDB/cluster_config.xml --delete-user --delete-group
+   ```
+
+   Alternatively, locally use the **gs_postuninstall** tool to clear each MogDB node.
+
+   ```bash
+   ./gs_postuninstall -U omm -X /opt/software/MogDB/cluster_config.xml --delete-user --delete-group -L
+   ```
+
+   **omm** is the name of the OS user who runs the MogDB, and the path of the MogDB configuration file is **/opt/software/MogDB/cluster_config.xml**.
+
+   If the cluster is installed in environment variable separation mode, delete the environment variable separation parameter **ENV** obtained by running the **source** command.
+
+   ```bash
+   unset MPPDB_ENV_SEPARATE_PATH
+   ```
+
+5. Delete the mutual trust between the users **root** on each MogDB database node.
+
+**Examples**
+
+Clear the host environment.
+
+```bash
+gs_postuninstall -U omm -X /opt/software/MogDB/cluster_config.xml --delete-user
+Parsing the configuration file.
+Successfully parsed the configuration file.
+Check log file path.
+Successfully checked log file path.
+Checking unpreinstallation.
+Successfully checked unpreinstallation.
+Deleting Cgroup.
+Successfully deleted Cgroup.
+Deleting the instance's directory.
+Successfully deleted the instance's directory.
+Deleting the installation directory.
+Successfully deleted the installation directory.
+Deleting the temporary directory.
+Successfully deleted the temporary directory.
+Deleting remote OS user.
+Successfully deleted remote OS user.
+Deleting software packages and environmental variables of other nodes.
+Successfully deleted software packages and environmental variables of other nodes.
+Deleting logs of other nodes.
+Successfully deleted logs of other nodes.
+Deleting software packages and environmental variables of the local node.
+Successfully deleted software packages and environmental variables of the local nodes.
+Deleting local OS user.
+Successfully deleted local OS user.
+Deleting local node's logs.
+Successfully deleted local node's logs.
+Successfully cleaned environment.
+```
+
+ **Troubleshooting**
+
+If the configuration deletion fails, locate faults by following the log information provided in the **$GAUSSLOG/om/gs_postuninstall-YYYY-MM-DD_HHMMSS.log** file.
diff --git a/product/en/docs-mogdb/v3.0/installation-guide/standard-installation/7-recommended-parameter-settings.md b/product/en/docs-mogdb/v3.0/installation-guide/standard-installation/7-recommended-parameter-settings.md
new file mode 100644
index 0000000000000000000000000000000000000000..ed07f08ea62feca91adb5ee3620619936799529f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/installation-guide/standard-installation/7-recommended-parameter-settings.md
@@ -0,0 +1,159 @@
+---
+title: Recommended Parameter Settings
+summary: Recommended Parameter Settings
+author: Guo Huan
+date: 2021-06-24
+---
+
+# Recommended Parameter Settings
+
+After installing the database, it is recommended to execute the following shell script to set the initialization parameters.
+
+> Note:
+>
+> Before executing the script, please make sure that all relevant file directories mentioned in the script exist. If not, you need to run the `mkdir -p <file directory>` command to create it in advance.
+>
+> For example: Before running `gs_guc set -I all -N all -c "archive_dest='/ogarchive'"`, you can run `ls -l` to check if the directory exists. If it does not exist, run `mkdir -p ogarchive` to create this directory.
+
+```bash
+#!/bin/bash
+
+source ~/.bashrc
+
+memory=`free|awk '{print $2}' |sed -n 2p`
+if [[ $memory -lt 4*1024*1024 ]]
+then
+    max_process_memory=2GB
+    shared_buffers=128MB
+    max_connections=500
+    work_mem=4MB
+    maintenance_work_mem=256MB
+    echo "If the database fails to start, lower the parameters max_process_memory and shared_buffers"
+elif [[ $memory -gt 4*1024*1024 ]] && [[ $memory -lt 8*1024*1024 ]]
+then
+    max_process_memory=5GB
+    shared_buffers=1GB
+    max_connections=1000
+    work_mem=16MB
+    maintenance_work_mem=1GB
+else
+    max_process_memory=$((memory*6/10/1024/1024))GB
+    shared_buffers=$((memory*3/10/1024/1024))GB
+    max_connections=3000
+    work_mem=64MB
+    maintenance_work_mem=2GB
+fi
+
+##Memory-related parameters
+gs_guc set -I all -N all -c "max_process_memory=${max_process_memory}"
+gs_guc set -I all -N all -c "shared_buffers=${shared_buffers}"
+gs_guc set -I all -N all -c "work_mem=${work_mem}"
+gs_guc set -I all -N all -c "maintenance_work_mem=${maintenance_work_mem}"
+gs_guc set -I all -N all -c "cstore_buffers=16MB"
+gs_guc set -I all -N all -c "wal_buffers=1GB"
+gs_guc set -I all -N all -c "local_syscache_threshold=32MB"
+gs_guc set -I all -N all -c "standby_shared_buffers_fraction=1"
+
+##Connection access-related parameters
+gs_guc set -I all -N all -c "max_connections=${max_connections}"
+gs_guc set -I all -N all -c "max_prepared_transactions=${max_connections}"
+gs_guc set -I all -N all -c "listen_addresses = '*'"
+gs_guc set -I all -N all -c "remote_read_mode=non_authentication"
+gs_guc set -I all -N all -c "password_encryption_type=1"
+gs_guc set -I all -N all -c "password_reuse_time=0"
+gs_guc set -I all -N all -c "password_lock_time=0"
+gs_guc set -I all -N all -c "password_effect_time=0"
+gs_guc set -I all -N all -c "session_timeout=0"
+
+##WAL-related parameters
+gs_guc set -I all -N all -c "wal_level=logical"
+gs_guc set -I all -N all -c "full_page_writes=off"
+gs_guc set -I all -N all -c "wal_log_hints=off"
+gs_guc set -I all -N all -c "xloginsert_locks=48"
+gs_guc set -I all -N all -c "advance_xlog_file_num=10"
+
+##Replication-related parameters
+gs_guc set -I all -N all -c "synchronous_commit=on"
+gs_guc set -I all -N all -c "wal_keep_segments=1024"
+gs_guc set -I all -N all -c "max_wal_senders=16"
+gs_guc set -I all -N all -c "recovery_max_workers=4"
+gs_guc set -I all -N all -c "most_available_sync=on"
+gs_guc set -I all -N all -c "max_size_for_xlog_prune=104857600"
+gs_guc set -I all -N all -c "catchup2normal_wait_time=0"
+gs_guc set -I all -N all -c "enable_slot_log=on"
+gs_guc set -I all -N all -c "max_replication_slots=32"
+gs_guc set -I all -N all -c "wal_receiver_timeout=60s"
+gs_guc set -I all -N all -c "sync_config_strategy=none_node"
+
+##Log-related parameters
+gs_guc set -I all -N all -c "logging_collector=on"
+gs_guc set -I all -N all -c "log_duration=on"
+gs_guc set -I all -N all -c "log_line_prefix='%m %u %d %r %p %S'"
+gs_guc set -I all -N all -c "log_checkpoints=on"
+gs_guc set -I all -N all -c "plog_merge_age=0"
+
+##Performance statistics-related parameters
+gs_guc set -I all -N all -c "vacuum_cost_limit=1000"
+gs_guc set -I all -N all -c "autovacuum_max_workers=10"
+gs_guc set -I all -N all -c "autovacuum_naptime=20s"
+gs_guc set -I all -N all -c "autovacuum_vacuum_cost_delay=10"
+gs_guc set -I all -N all -c "autovacuum_vacuum_scale_factor=0.05"
+gs_guc set -I all -N all -c "autovacuum_analyze_scale_factor=0.02"
+gs_guc set -I all -N all -c "autovacuum_vacuum_threshold=200"
+gs_guc set -I all -N all -c "autovacuum_analyze_threshold=200"
+gs_guc set -I all -N all -c "autovacuum_io_limits=104857600"
+gs_guc set -I all -N all -c "instr_unique_sql_count=20000"
+gs_guc set -I all -N all -c "enable_save_datachanged_timestamp=off"
+gs_guc set -I all -N all -c "track_sql_count=off"
+gs_guc set -I all -N all -c "enable_instr_rt_percentile=off"
+gs_guc set -I all -N all -c "enable_instance_metric_persistent=off"
+gs_guc set -I all -N all -c "enable_logical_io_statistics=off"
+gs_guc set -I all -N all -c "enable_user_metric_persistent=off"
+gs_guc set -I all -N all -c "enable_mergejoin=on"
+gs_guc set -I all -N all -c "enable_nestloop=on"
+gs_guc set -I all -N all -c "enable_pbe_optimization=off"
+gs_guc set -I all -N all -c "enable_resource_track=on"
+gs_guc set -I all -N all -c "enable_wdr_snapshot=on"
+gs_guc set -I all -N all -c "instr_unique_sql_count=5000"
+
+##Client whitelist
+gs_guc set -I all -N all -h "host     all      all  0.0.0.0/0    md5"
+
+##Other parameters
+gs_guc set -I all -N all -c "checkpoint_segments=1024"
+gs_guc set -I all -N all -c "checkpoint_completion_target=0.8"
+gs_guc set -I all -N all -c "pagewriter_sleep=200"
+
+gs_guc set -I all -N all -c "enable_alarm=off"
+gs_guc set -I all -N all -c "enable_codegen=off"
+gs_guc set -I all -N all -c "audit_enabled=off"
+gs_guc set -I all -N all -c "enable_asp=off"
+
+gs_guc set -I all -N all -c "lc_messages='en_US.UTF-8'"
+gs_guc set -I all -N all -c "lc_monetary='en_US.UTF-8'"
+gs_guc set -I all -N all -c "lc_numeric='en_US.UTF-8'"
+gs_guc set -I all -N all -c "lc_time='en_US.UTF-8'"
+
+gs_guc set -I all -N all -c "update_lockwait_timeout=1min"
+gs_guc set -I all -N all -c "lockwait_timeout=1min"
+
+gs_guc set -I all -N all -c "max_files_per_process=100000"
+gs_guc set -I all -N all -c "behavior_compat_options='display_leading_zero'"
+gs_guc set -I all -N all -c "enable_thread_pool=off"
+```
+
+Restart the database to make the parameters take effect.
+
+```bash
+gs_om -t stop && gs_om -t start
+```
+
+After the database is initialized, it is recommended to create a new database and a new user if you need to test. For example, if you need to create a database and a user for TPCC testing, run the following commands.
+
+```sql
+CREATE DATABASE tpcc_db;
+\c tpcc_db
+CREATE USER tpcc_usr WITH PASSWORD "tpcc@1234";
+alter user tpcc_usr sysadmin;
+GRANT ALL ON schema public TO tpcc_usr;
+```
diff --git a/product/en/docs-mogdb/v3.0/overview.md b/product/en/docs-mogdb/v3.0/overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..2e140f456879f9ee09c8e0f8600f6b2ca0431163
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/overview.md
@@ -0,0 +1,143 @@
+---
+title: MogDB - Safe and Easy-to-Use Commercial Database
+summary: MogDB - Safe and Easy-to-Use Commercial Database
+author: Liu Xu
+date: 2021-03-04
+---
+
+# MogDB - Safe and Easy-to-Use Commercial Database
+
+MogDB (En**Mo**tech **o**pen**G**auss **D**ata**B**ase Enterprise Edition) is a commercial database developed by ENMOTECH based on openGauss open source database.
+
+It aims at enterprise users and features high availability, security, automatic operation and maintenance, database appliance, and SQL audit optimization. Its core values lie in such advantages as ease of use, high performance, high availability, and 24/7 enterprise support.
+
+## Core Technologies of MogDB
+
+### Basic Functions Oriented to Application Development
+
+- **Standard SQL**
+
+  MogDB supports standard SQL statements. The SQL standard is an international standard and updated periodically.
+
+- **Standard Development Interfaces**
+
+  Standard ODBC and JDBC interfaces are provided to ensure quick migration of user services to MogDB.
+
+- **Transaction Support**
+
+  Transaction support refers to the system capability of ensuring atomicity, consistency, isolation, and durability (ACID) features of global transactions.
+
+- **Support for Functions and Stored Procedures**
+
+  Functions and stored procedures are important database objects. They encapsulate SQL statement sets used for certain functions so that the statements can be easily invoked.
+
+- **PG Interface Compatibility**
+
+  Compatible with PostgreSQL clients and interfaces.
+
+- **SQL Hints**
+
+  SQL hints are supported, which can override any execution plan and thus improve SQL query performance. In plan hints, you can specify a join order, join, stream, and scan operations, and the number of rows in a result of tuning an execution plan, thereby improving query performance.
+
+- **Copy Interface for Error Tolerance**
+
+  MogDB provides the encapsulated copy error tables for creating functions and allows users to specify error tolerance options when the Copy From statement is used. In this way, errors related to parsing, data format, and character set during the execution of the Copy From statement are recorded in the error table instead of being reported and interrupted. Even if a small amount of data in the target file of Copy From is incorrect, the data can be imported to the database. You can locate and rectify the fault in the error table later.
+
+### Database Security
+
+- **Access Control**
+
+  Access control is to manage users' database access control permissions, including database system permissions and object permissions.
+
+- **Separation of Control and Access Permissions**
+
+  For the system administrator, the control and access permissions on table objects are separated to improve data security of common users and restrict the object access permissions of administrators.
+
+- **Database Encryption Authentication**
+
+  The password encryption method based on the RFC5802 mechanism is used for authentication.
+
+- **Database Audit**
+
+  The password encryption method based on the RFC5802 mechanism is used for authentication.
+
+- **Network Communication Security**
+
+  Audit logs record user operations performed on database startup and stopping, connection, and DDL, DML, and DCL operations. The audit log mechanism enhances the database capability of tracing illegal operations and collecting evidence.
+
+- **Row-Level Access Control**
+
+  The row-level access control feature enables database access control to be accurate to each row of data tables. When different users perform the same SQL query operation, the read results may be different according to the row-level access control policy.
+
+### High Performance
+
+- **CBO Optimizer**
+
+  The MogDB optimizer is a typical optimizer developed from Cost-based Optimization (CBO). By using CBO, the database calculates the number of tuples and the execution cost for each step under each execution plan based on the number of table tuples, column width, null record ratio, and characteristic values, such as distinct, MCV, and HB values, and certain cost calculation methods.
+
+- **Hybrid Row-Column Storage**
+
+  MogDB supports both row-store and column-store models. You can choose a row-store or column-store table as needed.
+
+  Column-store is recommended if a table contains many columns (called a wide table) but its query involves only a few columns. Row-store is recommended if a table contains only a few columns and a query involves most of the columns.
+
+- **Adaptive Compression**
+
+  Currently, mainstream databases usually use the data compression technology. Various compression algorithms are used for different data types. If pieces of data of the same type have different characteristics, their compression algorithms and results will also be different. Adaptive compression chooses the suitable compression algorithm for data based on the data type and characteristics, achieving high performance in compression ratio, import, and query.
+
+- **Partitioning**
+
+  In the MogDB system, data is partitioned horizontally on an instance using a specified policy. This operation splits a table into multiple partitions that are not overlapped.
+
+- **SQL Bypass**
+
+  To accelerate such query, the SQL bypass framework is proposed. After simple mode judgment is performed on such query at the parse layer, the query enters a special execution path and skips the classic execution framework, including operator initialization and execution, expression, and projection. Instead, it directly rewrites a set of simple execution paths and directly invokes storage interfaces, greatly accelerating the execution of simple queries.
+
+- **Kunpeng NUMA Architecture Optimization**
+
+  - Based on the multi-core NUMA architecture of the Kunpeng processor, MogDB optimizes the NUMA architecture to reduce the cross-core memory access latency and maximize the multi-core Kunpeng computing capability. The key technologies include redo log batch insertion, NUMA distribution of hotspot data, and Clog partitions, greatly improving the processing performance of the TP system.
+  - Based on the ARMv8.1 architecture used by the Kunpeng chip, MogDB uses the LSE instruction set to implement efficient atomic operations, effectively improving the CPU usage, multi-thread synchronization performance, and XLog write performance.
+  - Based on the wider L3 cacheline provided by the Kunpeng chip, MogDB optimizes hotspot data access, effectively improving the cache access hit ratio, reducing the cache consistency maintenance overhead, and greatly improving the overall data access performance of the system.
+
+### High Scalability
+
+**High Concurrency of the Thread Pool**
+
+In the OLTP field, a database needs to process a large quantity of client connections. Therefore, the processing capability in high-concurrency scenarios is one of the important capabilities of the database.
+
+The simplest processing mode for external connections is the per-thread-per-connection mode, in which a user connection generates a thread. This mode features simple processing thanks to its architecture. However, in high-concurrency scenarios, there are too many threads, causing heavy workload in thread switchover and large conflict between the lightweight lock areas of the database. As a result, the performance (throughput) deteriorates sharply and the SLA of user performance cannot be met.
+
+Therefore, a thread resource pooling and reuse technology needs to be used to resolve this problem. The overall design idea of the thread pool technology is to pool thread resources and reuse them among different connections. After the system is started, a fixed number of working threads are started based on the current number of cores or user configuration. A working thread serves one or more connection sessions. In this way, the session and thread are decoupled. The number of worker threads is fixed. Therefore, frequent thread switchover does not occur in case of high concurrency. The database layer schedules and manages sessions.
+
+### HA
+
+- **Primary/Standby**
+
+  To ensure that a fault can be rectified, data needs to be written into multiple copies. Multiple copies are configured for the primary and standby nodes, and logs are used for data synchronization. In this way, MogDB has no data lost when a node is faulty or the system restarts after a stop, meeting the ACID feature requirements. The primary/standby environment supports two modes: primary/standby, and one primary and multiple standbys. In primary/standby mode, if the standby node needs to redo logs, it can be promoted to primary. In the one primary and multiple standbys mode, all standby nodes need to redo logs and can be promoted to primary. The primary/standby mode is mainly used for OLTP systems with general reliability to save storage resources. The one primary and multiple standbys mode provides higher DR capabilities and is suitable for the OLTP system with higher availability transaction processing.
+
+- **Logical Backup**
+
+  MogDB provides the logical backup capability to back up data in user tables to local disk files in text or CSV format and restore the data in homogeneous or heterogeneous databases.
+
+- **Physical backup**
+
+  MogDB provides the physical backup capability to back up data of the entire instance to local disk files in the internal database format, and restore data of the entire instance in a homogeneous database.
+
+- **Point-In-Time Recovery (PITR)**
+
+  PITR uses basic hot backup, write-ahead logs (WALs), and archived WALs for backup and recovery. When replaying a WAL record, you can stop at any point in time, so that there is a snapshot of the consistent database at any point in time. That is, you can restore the database to the state at any time since the backup starts. During recovery, MogDB supports specifying the recovery stop point as TID, time, and LSN.
+
+### Maintainability
+
+**Workload Diagnosis Report**
+
+The workload diagnosis report (WDR) generates a performance report between two different time points based on the system performance snapshot data at two different time points. The report is used to diagnose database kernel performance faults.
+
+WDR depends on the following two components:
+
+- SNAPSHOT: The performance snapshot can be configured to collect a certain amount of performance data from the kernel at a specified interval and store the data in the user tablespace. Any snapshot can be used as a performance baseline for comparison with other snapshots.
+- WDR Reporter: This tool analyzes the overall system performance based on two snapshots, calculates the changes of more specific performance indicators between the two time periods, and generates summarized and detailed performance data.
+
+## MogDB Manager
+
+MogDB Manager provides a whole set of enterprise-level database management suite, including installation and deployment, high availability monitoring, troubleshooting, performance monitoring, database migration, backup and restoration management, data synchronization between heterogeneous databases, SQL compatibility analysis, comparative analysis of performance pressure tests,  ultimate data recovery. It helps customers improve database management efficiency in multiple O&M dimensions.
diff --git a/product/en/docs-mogdb/v3.0/performance-tuning/1-system/1-optimizing-os-parameters.md b/product/en/docs-mogdb/v3.0/performance-tuning/1-system/1-optimizing-os-parameters.md
new file mode 100644
index 0000000000000000000000000000000000000000..7e0a3e531463847a52954558c48b51ffc5055089
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/performance-tuning/1-system/1-optimizing-os-parameters.md
@@ -0,0 +1,117 @@
+---
+title: Optimizing OS Parameters
+summary: Optimizing OS Parameters
+author: Liu Xu
+date: 2021-03-04
+---
+
+# Optimizing OS Parameters
+
+You can improve the MogDB performance by modifying key parameters of the OS based on actual service requirements during the performance optimization.
+
+## Prerequisites
+
+You have checked whether the OS parameters are set to the suggested values using **gs_check**. If not, modify them as required.
+
+## Memory Parameters
+
+In the **sysctl.conf** file, change the value of **vm.extfrag_threshold** to **1000** (reference value). If the file does not contain memory parameters, add them manually.
+
+```bash
+vim /etc/sysctl.conf
+```
+
+Run the following command to make the modification take effect:
+
+```sql
+sysctl -p
+```
+
+## Network Parameters
+
+- In the **sysctl.conf** file, modify network parameters. If the file does not contain such parameters, add them manually. For details, see [Table 1](#table 1).
+
+  ```
+  vim /etc/sysctl.conf
+  ```
+
+  Run the following command to make the modification take effect:
+
+  ```
+  sysctl -p
+  ```
+
+  <a id="table 1">**Table 1**</a> Network parameters
+
+  | Parameter                    | Reference Value              | Description                                                  |
+| :--------------------------- | :--------------------------- | :----------------------------------------------------------- |
+  | net.ipv4.tcp_timestamps      | 1                            | Specifies whether to enable quick reclamation of the sockets in TIME-WAIT state during TCP connection establishment. The default value **0** indicates that quick reclamation is disabled, and the value **1** indicates that quick reclamation is enabled. |
+  | net.ipv4.tcp_mem             | 94500000 915000000 927000000 | **94500000**: If less than 94,500,000 pages are used by the TCP, the kernel is not affected.<br />**915000000**: If more than 915,000,000 pages are used by the TCP, the kernel enters the **memory pressure** mode.<br />**927000000**: If more than 927,000,000 pages are used by the TCP, the "Out of socket memory." message is displayed. |
+  | net.ipv4.tcp_max_orphans     | 3276800                      | Maximum number of the orphan sockets                         |
+  | net.ipv4.tcp_fin_timeout     | 60                           | Default timeout period                                       |
+  | net.ipv4.ip_local_port_range | 26000 65535                  | Port range that can be used by TCP or UDP                    |
+
+- Use the **ifconfig** command to set the maximum transmission unit (MTU) of 10 GE NICs. The value **8192** is recommended because this setting improves the network bandwidth usage.
+
+  Example:
+
+```bash
+  #ifconfig ethx mtu 8192
+#ifconfig ethx
+  ethx   Link encap:Ethernet  HWaddr XX:XX:XX:XX:XX:XX
+  inet addr:xxx.xxx.xxx.xxx  Bcast:xxx.xxx.xxx.xxx  Mask:xxx.xxx.xxx.0
+  inet6 addr: fxxx::9xxx:bxxx:xxxa:1d18/64 Scope:Link
+  UP BROADCAST RUNNING MULTICAST  MTU:8192  Metric:1
+  RX packets:179849803 errors:0 dropped:0 overruns:0 frame:0
+  TX packets:40492292 errors:0 dropped:0 overruns:0 carrier:0
+  collisions:0 txqueuelen:1000
+  RX bytes:17952090386 (17120.4 Mb)  TX bytes:171359670290 (163421.3 Mb)
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+> - **ethx** indicates the 10 GE service NIC used in the database.
+  > - The first command is used to set the MTU. The second command is used to verify that the MTU has been successfully set. The texts in bold indicate the value of the MTU.
+  > - Set the MTU as user **root**.
+
+- Use **ethtool** to set the length of the receiving (**RX**) queue and that of the sending (**TX**) queue for 10 GE NICs. The value **4096** is recommended because this setting improves the network bandwidth usage.
+
+  Example:
+
+  ```
+  # ethtool -G ethx rx 4096 tx 4096
+  # ethtool -g ethx
+  Ring parameters for ethx:
+  Pre-set maximums:
+  RX:             4096
+  RX Mini:        0
+  RX Jumbo:       0
+  TX:             4096
+  Current hardware settings:
+  RX:             4096
+  RX Mini:        0
+  RX Jumbo:       0
+  TX:             4096
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > - **ethx** indicates the 10 GE service NIC used in the database.
+  > - The first command is used to set the lengths of the receiving and sending queues. The second command is to verify whether the lengths have been successfully set. If information similar to the example is displayed, the setting is successful.
+  > - Set the lengths of the receiving and sending queues as user **root**.
+
+## I/O Parameters
+
+Set the **hugepage** attribute. Run the following commands to disable the transparent huge page function:
+
+```bash
+echo never >
+/sys/kernel/mm/transparent_hugepage/enabled
+echo never > /sys/kernel/mm/transparent_hugepage/defrag
+```
+
+Run the following command to make the modification take effect:
+
+```
+ reboot
+```
diff --git a/product/en/docs-mogdb/v3.0/performance-tuning/1-system/2-optimizing-database-parameters.md b/product/en/docs-mogdb/v3.0/performance-tuning/1-system/2-optimizing-database-parameters.md
new file mode 100644
index 0000000000000000000000000000000000000000..a28c0778c4685fba7df38fd6f584137af6e95af0
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/performance-tuning/1-system/2-optimizing-database-parameters.md
@@ -0,0 +1,55 @@
+---
+title: Optimizing Database Parameters
+summary: Optimizing Database Parameters
+author: Liu Xu
+date: 2021-03-04
+---
+
+# Optimizing Database Parameters
+
+## Optimizing Database Memory Parameters
+
+The performance of complex query statements strongly depends on the configuration parameters of the database memory. The database memory parameters include the control parameters for logical memory management and parameters determining whether execution operators are spilled to disks.
+
+### Parameter for Logical Memory Management
+
+**max_process_memory** is a parameter used for logical memory management.
+
+Use the following formula to calculate the available memory for job execution:
+
+**max_process_memory** - Shared memory (including **shared_buffers**) - **cstore_buffers**
+
+Therefore, the memory available to job execution depends on **shared_buffers** and **cstore_buffers**.
+
+Views for logical memory management are provided to display the used memory and peak information in each database block. You can connect to a database node and run **pg_total_memory_detail** to query information about the memory usage on this database node. Alternatively, you can connect to the primary node of the database and run **pgxc_total_memory_detail** to query information about the memory usage on all the database nodes.
+
+When the specified physical memory is insufficient, **work_mem** determines whether to write additional operator calculation data into temporary tables based on query characteristics and concurrency. This reduces performance by five to 10 times and prolongs the query response time from seconds to minutes.
+
+- For complex serial queries, each query requires five to ten associated operations. Set **work_mem** using the following formula:**work_mem** = 50% of the memory/10.
+- For simple serial queries, each query requires two to five associated operations. Set **work_mem** using the following formula:**work_mem** = 50% of the memory/5.
+- For concurrent queries, set **work_mem** using the following formula:**work_mem** = **work_mem** for serial queries/Number of concurrent SQL statements.
+
+### Parameter Determining Whether to Spill Execution Operators to Disks
+
+**work_mem** sets the used memory threshold. Execution operators that can be spilled to disks will be written when the used memory exceeds the threshold. Such execution operators include Hash(VecHashJoin), Agg(VecAgg), Sort(VecSort), Material(VecMaterial), SetOp(VecSetOp), and WindowAgg(VecWindowAgg). They can be vectorized or non-vectorized. This parameter ensures concurrent throughput and the performance of a single query job. Therefore, you need to optimize the parameter based on the output of **Explain Performance**.
+
+## Optimizing Concurrent Queue Parameters
+
+You can globally or locally control concurrent queues.
+
+### Global Concurrent Queues
+
+In a global concurrent queue, **max_active_statements** controls the number of concurrent jobs on the primary node of the database. All common users' jobs are controlled, regardless of their complexity. When the number of concurrent jobs reaches the specified threshold, the rest of the jobs wait in a queue. Administrators' jobs are not under such control.
+
+Set this parameter based on system capacities, such as memory and I/O usage. In a resource pool associated with common users, if the jobs of different priorities occupy different portions, they will be queued by priority first. Then, the jobs of the same priority are queued. Jobs in the queue of highest priority will be woken up first.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - In a high transactional concurrency scenario, you are advised to set **max_active_statements** to **-1**, indicating that global concurrency is not limited.
+> - In an analytical query scenario, set **max_active_statements** to the number of CPU cores divided by the number of database nodes. Generally, its value ranges from 5 to 8.
+
+### Local Concurrent Queues
+
+You can locally control the number of concurrent jobs within the same resource pool on the primary node of the database. The number of concurrent complex jobs are controlled based on their cost.
+
+**parctl_min_cost** is used to determine whether a job is complex.
diff --git a/product/en/docs-mogdb/v3.0/performance-tuning/1-system/3-configuring-llvm.md b/product/en/docs-mogdb/v3.0/performance-tuning/1-system/3-configuring-llvm.md
new file mode 100644
index 0000000000000000000000000000000000000000..f2fb18d8ce9f7c1b573fb2093068b7960f420632
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/performance-tuning/1-system/3-configuring-llvm.md
@@ -0,0 +1,75 @@
+---
+title: Configuring LLVM
+summary: Configuring LLVM
+author: Liu Xu
+date: 2021-03-04
+---
+
+# Configuring LLVM
+
+Low Level Virtual Machine (LLVM) dynamic compilation can be used to generate customized machine code for each query to replace original common functions. Query performance is improved by reducing redundant judgment conditions and virtual function calls, and by making local data more accurate during actual queries.
+
+LLVM needs to consume extra MogDB to pre-generate intermediate representation (IR) and compile it into codes. Therefore, if the data volume is small or if a query itself consumes less MogDB, the performance deteriorates.
+
+## LLVM Application Scenarios and Restrictions
+
+### Application Scenarios
+
+- Expressions supporting LLVM
+
+  The query statements that contain the following expressions support LLVM optimization:
+
+  1. Case…when…
+  2. IN
+  3. Bool (AND/OR/NOT)
+  4. BooleanTest (IS_NOT_KNOWN/IS_UNKNOWN/IS_TRUE/IS_NOT_TRUE/IS_FALSE/IS_NOT_FALSE)
+  5. NullTest (IS_NOT_NULL/IS_NULL)
+  6. Operator
+  7. Function (lpad, substring, btrim, rtrim, length)
+  8. Nullif
+
+  Supported data types for expression computing are bool, tinyint, smallint, int, bigint, float4, float8, numeric, date, MogDB, MogDBtz, MogDBstamp, MogDBstamptz, interval, bpchar, varchar, text, and oid.
+
+  Consider using LLVM dynamic compilation and optimization only if expressions are used in the following content in a vectorized executor:**filter** in the **Scan** node; **complicate hash condition**, **hash join filter**, and **hash join target** in the **Hash Join** node; **filter** and **join filter** in the **Nested Loop** node; **merge join filter** and **merge join target** in the **Merge Join** node; and **filter** in the **Group** node.
+
+- Operators supporting LLVM
+
+  1. Join: HashJoin
+  2. Agg: HashAgg
+  3. Sort
+
+  Where HashJoin supports only Hash Inner Join, and the corresponding hash cond supports comparisons between int4, bigint, and bpchar. HashAgg supports sum and avg operations of bigint and numeric data types. Group By statements supports int4, bigint, bpchar, text, varchar, MogDBstamp, and count(*) aggregation operation. Sort supports only comparisons between int4, bigint, numeric, bpchar, text, and varchar data types. Except the preceding operations, LLVM dynamic compilation and optimization cannot be used. You can use the explain performance tool to check whether LLVM dynamic compilation and optimization can be used.
+
+### Non-applicable Scenarios
+
+- Tables that have small amount of data cannot be dynamically compiled.
+- Query jobs with a non-vectorized execution path cannot be generated.
+
+## Other Factors Affecting LLVM Performance
+
+The LLVM optimization effect depends on not only operations and computing in the database, but also the selected hardware environment.
+
+- Number of C functions called by expressions
+
+  CodeGen cannot be used in all expressions in an entire expression, that is, some expressions use CodeGen while others invoke original C codes for calculation. In an entire expression, if more expressions invoke original C codes, LLVM dynamic compilation and optimization may reduce the calculation performance. By setting **log_min_message** to **DEBUG1**, you can view expressions that directly invoke C codes.
+
+- Memory resources
+
+  One of the key LLVM features is to ensure the locality of data, that is, data should be stored in registers as much as possible. Data loading should be reduced at the same MogDB. Therefore, when using LLVM optimization, value of **work_mem** must be set as large as required to ensure that codes are processed in the memory using corresponding LLVM. Otherwise, performance deteriorates.
+
+- Optimizer cost estimation
+
+  The LLVM feature realizes a simple cost estimation model. You can determine whether to use LLVM dynamic compilation and optimization for the current node based on the tables involved in the node computing. If the optimizer understates or overestimates the actual number of rows involved, the income cannot be obtained.
+
+## Recommended Suggestions for LLVM
+
+Currently, the LLVM is enabled by default in the database kernel, and users can perform related configurations on it. The overall suggestions are as follows:
+
+1. Set **work_mem** to an appropriate value and set it to a large value in allowed conditions. If much data is spilled to disks, you are advised to disable the LLVM dynamic compilation and optimization by setting **enable_codegen** to **off**).
+
+2. Set **codegen_cost_threshold** to an appropriate value (The default value is **10000**). Ensure that LLVM dynamic compilation and optimization is not used when the data volume is small. After the value of **codegen_cost_threshold** is set, the database performance may deteriorate due to the use of LLVM dynamic compilation and optimization. In this case, you are advised to increase the parameter value.
+
+3. If a large number of C functions are called, you are advised not to use the LLVM dynamic compilation and optimization.
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+   > If resources are robust, the larger the data volume is, the better the performance improvement effect is.
diff --git a/product/en/docs-mogdb/v3.0/performance-tuning/1-system/4-configuring-smp.md b/product/en/docs-mogdb/v3.0/performance-tuning/1-system/4-configuring-smp.md
new file mode 100644
index 0000000000000000000000000000000000000000..56be1940c36a3661a1cf18f7fefe92a3575d1806
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/performance-tuning/1-system/4-configuring-smp.md
@@ -0,0 +1,111 @@
+---
+title: Configuring SMP
+summary: Configuring SMP
+author: Guo Huan
+date: 2021-07-26
+---
+
+# Configuring SMP
+
+This section describes the usage restrictions, application scenarios, and configuration guide of symmetric multiprocessing (SMP).
+
+## SMP Application Scenarios and Restrictions
+
+### Context
+
+The SMP feature improves the performance through operator parallelism and occupies more system resources, including CPU, memory, and I/O. Actually, SMP is a method consuming resources to save time. It improves system performance in appropriate scenarios and when resources are sufficient, but may deteriorate performance otherwise. SMP applies to analytical query scenarios where a single query takes a long time and the service concurrency is low. The SMP parallel technology can reduce the query delay and improve the system throughput performance. However, in a high transactional concurrency scenario, a single query has a short delay. In this case, using a multi-thread parallel technology increases the query delay and reduces the system throughput performance.
+
+### Application Scenarios
+
+- Operators that support parallelism. The plan contains the following operators that support parallelism.
+
+  - Scan: Row-store ordinary tables and row-store partitioned tables, and column-store ordinary tables and column-store partitioned tables can be sequentially scanned.
+  - Join: HashJoin and NestLoop
+  - Agg: HashAgg, SortAgg, PlainAgg, and WindowAgg (which supports only **partition by**, and does not support **order by**)
+  - Stream: Local Redistribute and Local Broadcast
+  - Others: Result, Subqueryscan, Unique, Material, Setop, Append, VectoRow, and RowToVec
+
+- SMP-specific operators: To execute queries in parallel, Stream operators are added for data exchange of the SMP feature. These new operators can be considered as the subtypes of Stream operators.
+
+  - Local Gather aggregates data of parallel threads within an instance.
+  - Local Redistribute redistributes data based on the distributed key across threads within an instance.
+  - Local Broadcast broadcasts data to each thread within an instance.
+  - Local RoundRobin distributes data in polling mode across threads within an instance.
+
+- The following uses the **TPCH Q1** parallel plan as an example.
+
+  ![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/configuring-smp-1.png)
+
+  In this plan, the Scan and HashAgg operators are processed in parallel, and the Local Gather operator is added for data exchange. Operator 3 is a Local Gather operator. "dop: 1⁄4" indicates that the degree of parallelism of the sender thread is 4 and the degree of parallelism of the receiver thread is 1. That is, the lower-layer HashAggregate operator 4 is executed based on the degree of parallelism 4, the upper-layer operators 1 and 2 are executed in serial mode, and operator 3 aggregates data of parallel threads within the instance.
+
+  You can view the parallelism situation of each operator in the dop information.
+
+### Non-applicable Scenarios
+
+1. Index scanning cannot be executed in parallel.
+2. MergeJoin cannot be executed in parallel.
+3. WindowAgg order by cannot be executed in parallel.
+4. The cursor cannot be executed in parallel.
+5. Queries in stored procedures and functions cannot be executed in parallel.
+6. Subplans and initplans cannot be queried in parallel, and operators that contain subqueries cannot be executed in parallel, either.
+7. Query statements that contain the median operation cannot be executed in parallel.
+8. Queries with global temporary tables cannot be executed in parallel.
+9. Updating materialized views cannot be executed in parallel.
+
+## Resource Impact on SMP Performance
+
+The SMP architecture uses abundant resources to obtain time. After the plan parallelism is executed, the resource consumption is added, including the CPU, memory, and I/O resources. As the parallelism degree is expanded, the resource consumption increases. If these resources become a bottleneck, the SMP cannot improve the performance and the overall cluster performance may be deteriorated. The following information describes the situations that the SMP affects theses resources:
+
+- CPU resources
+
+  In a general customer scenario, the system CPU usage is not high. Using the SMP parallelism architecture will fully use the CPU resources to improve the system performance. If the number of CPU kernels of the database server is too small and the CPU usage is already high, enabling the SMP parallelism may deteriorate the system performance due to resource competition between multiple threads.
+
+- Memory resources
+
+  Query parallel causes memory usage growth, but the memory usage of each operator is still restricted by **work_mem** and other parameters. Assuming that **work_mem** is 4 GB and the degree of parallelism is 2, the memory usage of each thread in parallel is limited to 2 GB. When **work_mem** is small or the system memory is not sufficient, using SMP may flush data to disks. As a result, the query performance deteriorates.
+
+- I/O resources
+
+  A parallel scan increases I/O resource consumption. It can improve scan performance only when I/O resources are sufficient.
+
+## Other Factors Affecting SMP Performance
+
+Besides resource factors, there are other factors that impact the SMP performance, such as uneven data distribution in a partitioned table and system parallelism degree.
+
+- Impact of data skew on SMP performance
+
+  Severe data skew deteriorates SMP performance. For example, if the data volume of a value in the join column is much more than that of other values, the data volume of a parallel thread will be much more than that of others after Hash-based data redistribution, resulting in the long-tail issue and poor SMP performance.
+
+- Impact of system parallelism degree on the SMP performance
+
+  The SMP feature uses more resources, and remaining resources are insufficient in a high concurrency scenario. Therefore, enabling the SMP function will result in severe resource competition among queries. Once resource competition occurs, no matter the CPU, I/O, or memory resources, all of them will result in entire performance deterioration. In the high concurrency scenario, enabling the SMP function will not improve the performance and even may cause performance deterioration.
+
+## Suggestions for Using SMP
+
+### Limitations
+
+To use the SMP feature to improve the performance, ensure that the following conditions are met:
+
+The CPU, memory, and I/O resources are sufficient. SMP is a solution that uses abundant resources to exchange time. After plan parallel is executed, resource consumption is increased. When these resources become a bottleneck, the SMP feature cannot improve the performance and even may deteriorate the performance. In the case of a resource bottleneck, you are advised to disable the SMP feature.
+
+### Procedure
+
+1. Observe the current system load situation. If resources are sufficient (the resource usage is smaller than 50%), perform step 2. Otherwise, exit this system.
+
+2. Set **query_dop** to **1** (default value). Use **explain** to generate an execution plan and check whether the plan can be used in scenarios in [SMP Application Scenarios and Restrictions](#smp-application-scenarios-and-restrictions). If yes, go to step 3.
+
+3. Set **query_dop** to **value**. The parallelism degree is 1 or **value** regardless of the resource usage and plan characteristics.
+
+4. Before the query statement is executed, set **query_dop** to an appropriate value. After the statement is executed, set **query_dop** to disable the query. The following provides an example:
+
+   ```
+   mogdb=# SET query_dop = 4;
+   mogdb=# SELECT COUNT(*) FROM t1 GROUP BY a;
+   ......
+   mogdb=# SET query_dop = 1;
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+   >
+   > - If resources are sufficient, the higher the parallelism degree is, the better the performance improvement effect is.
+   > - The SMP parallelism degree supports session level settings. You are advised to enable the SMP feature before executing a query that meets the requirements. After the execution is complete, disable the SMP feature. Otherwise, SMP may affect services in peak hours.
diff --git a/product/en/docs-mogdb/v3.0/performance-tuning/2-sql/1-query-execution-process.md b/product/en/docs-mogdb/v3.0/performance-tuning/2-sql/1-query-execution-process.md
new file mode 100644
index 0000000000000000000000000000000000000000..d74c989ae44a555dbe65881e0972ec1fcee94746
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/performance-tuning/2-sql/1-query-execution-process.md
@@ -0,0 +1,57 @@
+---
+title: Query Execution Process
+summary: Query Execution Process
+author: Guo Huan
+date: 2021-03-16
+---
+
+# Query Execution Process
+
+## Introduction
+
+The process from receiving SQL statements to the statement execution by the SQL engine is shown in Figure 1 and described in Table 1. The texts in red are steps where database administrators can optimize queries.
+
+**Figure 1** Execution process of query-related SQL statements by the SQL engine
+
+![execution-process-of-query-related-sql-statements-by-the-sql-engine](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/query-execution-process-en-1.png)
+
+**Table 1** Execution process of query-related SQL statements by the SQL engine
+
+| Step                                   | Description                                                  |
+| :------------------------------------- | :----------------------------------------------------------- |
+| 1. Perform syntax and lexical parsing. | Converts the input SQL statements from the string data type to the formatted structure stmt based on the specified SQL statement rules. |
+| 2. Perform semantic parsing.           | Converts the formatted structure obtained from the previous step into objects that can be recognized by the database. |
+| 3. Rewrite the query statements.       | Converts the output of the previous step into the structure that optimizes the query execution. |
+| 4. Optimize the query.                 | Determines the execution mode of SQL statements (the execution plan) based on the result obtained from the previous step and the internal database statistics. For details about how the internal database statistics and GUC parameters affect the query optimization (execution plan), see [Optimizing Queries Using Statistics](#Optimizing Queries Using Statistics) and [Optimizing Queries Using GUC parameters](#Optimizing Queries Using GUC parameters). |
+| 5. Perform the query.                  | Executes the SQL statements based on the execution path specified in the previous step. Selecting a proper underlying storage mode improves the query execution efficiency. For details, see [Optimizing Queries Using the Underlying Storage](#Optimizing Queries Using the Underlying Storage). |
+
+## Optimizing Queries Using Statistics
+
+The MogDB optimizer is a typical Cost-based Optimization (CBO). By using CBO, the database calculates the number of tuples and the execution cost for each step under each execution plan based on the number of table tuples, column width, null record ratio, and characteristic values, such as distinct, MCV, and HB values, and certain cost calculation methods. The database then selects the execution plan that takes the lowest cost for the overall execution or for the return of the first tuple. These characteristic values are the statistics, which is the core for optimizing a query. Accurate statistics helps the planner select the most appropriate query plan. Generally, you can collect statistics of a table or that of some columns in a table using **ANALYZE**. You are advised to periodically execute **ANALYZE** or execute it immediately after you modified most contents in a table.
+
+## Optimizing Queries Using GUC parameters
+
+Optimizing queries aims to select an efficient execution mode.
+
+Take the following SQL statement as an example:
+
+```
+select count(1)
+from customer inner join store_sales on (ss_customer_sk = c_customer_sk);
+```
+
+During execution of **customer inner join store_sales**, MogDB supports nested loop, merge join, and hash join. The optimizer estimates the result set sizes and the execution cost for each join mode based on the statistics on the **customer** and **store_sales** tables. It then compares the costs and selects the one costing the least.
+
+As described in the preceding content, the execution cost is calculated based on certain methods and statistics. If the actual execution cost cannot be accurately estimated, you need to optimize the execution plan by setting the GUC parameters.
+
+## Optimizing Queries Using the Underlying Storage
+
+MogDB supports row- and column-store tables. The selection of an underlying storage mode strongly depends on specific customer service scenarios. You are advised to use column-store tables for computing service scenarios (mainly involving association and aggregation operations) and row-store tables for service scenarios, such as point queries and massive **UPDATE** or **DELETE** executions.
+
+Optimization methods of each storage mode will be described in detail below.
+
+## Optimizing Queries by Rewriting SQL Statements
+
+Besides the preceding methods that improve the performance of the execution plan generated by the SQL engine, database administrators can also enhance SQL statement performance by rewriting SQL statements while retaining the original service logic based on the execution mechanism of the database and abundant practices.
+
+This requires that database administrators know the customer services well and have professional knowledge of SQL statements. Below chapters will describe some common SQL rewriting scenarios.
diff --git a/product/en/docs-mogdb/v3.0/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md b/product/en/docs-mogdb/v3.0/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md
new file mode 100644
index 0000000000000000000000000000000000000000..9fbe0358a7d1014e0e056247f870bfc0a219ea27
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md
@@ -0,0 +1,136 @@
+---
+title: Introduction to the SQL Execution Plan
+summary: Introduction to the SQL Execution Plan
+author: Guo Huan
+date: 2021-03-16
+---
+
+# Introduction to the SQL Execution Plan
+
+## Overview
+
+The SQL execution plan is a node tree, which displays detailed procedure when MogDB runs an SQL statement. A database operator indicates one step.
+
+You can run the **EXPLAIN** command to view the execution plan generated for each query by an optimizer. The output of **EXPLAIN** has one row for each execution node, showing the basic node type and the cost estimation that the optimizer made for the execution of this node, as shown in Figure 1.
+
+**Figure 1** SQL execution plan example
+
+![sql-execution-plan-example](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/introduction-to-the-sql-execution-plan-1.png)
+
+- Nodes at the bottom level are scan nodes. They scan tables and return raw rows. The types of scan nodes (sequential scans and index scans) vary depending on the table access methods. Objects scanned by the bottom layer nodes may not be row-store data (not directly read from a table), such as **VALUES** clauses and functions that return rows, which have their own types of scan nodes.
+
+- If the query requires join, aggregation, sorting, or other operations on the raw rows, there will be other nodes above the scan nodes to perform these operations. In addition, there is more than one way to perform these operations, so different types of execution nodes may be displayed here.
+
+- The first row (the upper-layer node) estimates the total execution cost of the execution plan. Such an estimate indicates the value that the optimizer tries to minimize.
+
+### Execution Plan Information
+
+In addition to setting different display formats for an execution plan, you can use different **EXPLAIN** syntax to display execution plan information in detail. The following lists the common **EXPLAIN** syntax. For details about more **EXPLAIN** syntax, see EXPLAIN.
+
+- EXPLAIN **statement**: only generates an execution plan and does not execute. The *statement* indicates SQL statements.
+- EXPLAIN ANALYZE **statement**: generates and executes an execution plan, and displays the execution summary. Then actual execution time statistics are added to the display, including the total elapsed time expended within each plan node (in milliseconds) and the total number of rows it actually returned.
+- EXPLAIN PERFORMANCE **statement**: generates and executes the execution plan, and displays all execution information.
+
+To measure the run time cost of each node in the execution plan, the current execution of **EXPLAIN ANALYZE** or **EXPLAIN PERFORMANCE** adds profiling overhead to query execution. Running **EXPLAIN ANALYZE** or **EXPLAIN PERFORMANCE** on a query sometimes takes longer time than executing the query normally. The amount of overhead depends on the nature of the query, as well as the platform being used.
+
+Therefore, if an SQL statement is not finished after being running for a long time, run the **EXPLAIN** statement to view the execution plan and then locate the fault. If the SQL statement has been properly executed, run the **EXPLAIN ANALYZE** or **EXPLAIN PERFORMANCE** statement to check the execution plan and information to locate the fault.
+
+The **EXPLAIN PERFORMANCE** lightweight execution is consistent with **EXPLAIN PERFORMANCE** but greatly reduces the time spent on performance analysis.
+
+## Description
+
+As described in [Overview](#Overview), **EXPLAIN** displays the execution plan, but will not actually run SQL statements. **EXPLAIN ANALYZE** and **EXPLAIN PERFORMANCE** both will actually run SQL statements and return the execution information. This section describes the execution plan and execution information in detail.
+
+### Execution Plans
+
+The following SQL statement is used as an example:
+
+```sql
+SELECT * FROM t1, t2 WHERE t1.c1 = t2.c2;
+```
+
+Run the **EXPLAIN** command and the output is as follows:
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/introduction-to-the-sql-execution-plan-2.png)
+
+**Interpretation of the execution plan level (vertical)**:
+
+1. Layer 1:**Seq Scan on t2**
+
+   The table scan operator scans the table **t2** using **Seq Scan**. At this layer, data in the table **t2** is read from a buffer or disk, and then transferred to the upper-layer node for calculation.
+
+2. Layer 2:**Hash**
+
+   Hash operator. It is used to calculate the hash value of the operator transferred from the lower layer for subsequent hash join operations.
+
+3. Layer 3:**Seq Scan on t1**
+
+   The table scan operator scans the table **t1** using **Seq Scan**. At this layer, data in the table **t1** is read from a buffer or disk, and then transferred to the upper-layer node for hash join calculation.
+
+4. Layer 4:**Hash Join**
+
+   Join operator. It is used to join data in the **t1** and **t2** tables using the hash join method and output the result data.
+
+**Keywords in the execution plan**:
+
+1. Table access modes
+
+   - Seq Scan
+
+     Scans all rows of the table in sequence.
+
+   - Index Scan
+
+     The optimizer uses a two-step plan: the child plan node visits an index to find the locations of rows matching the index condition, and then the upper plan node actually fetches those rows from the table itself. Fetching rows separately is much more expensive than reading them sequentially, but because not all pages of the table have to be visited, this is still cheaper than a sequential scan. The upper-layer planning node sorts index-identified rows based on their physical locations before reading them. This minimizes the independent capturing overhead.
+
+     If there are separate indexes on multiple columns referenced in **WHERE**, the optimizer might choose to use an **AND** or **OR** combination of the indexes. However, this requires the visiting of both indexes, so it is not necessarily a win compared to using just one index and treating the other condition as a filter.
+
+     The following Index scans featured with different sorting mechanisms are involved:
+
+     - Bitmap Index Scan
+
+       Fetches data pages using a bitmap.
+
+     - Index Scan using index_name
+
+       Fetches table rows in index order, which makes them even more expensive to read. However, there are so few rows that the extra cost of sorting the row locations is unnecessary. This plan type is used mainly for queries fetching just a single row and queries having an **ORDER BY** condition that matches the index order, because no extra sorting step is needed to satisfy **ORDER BY**.
+
+2. Table connection modes
+
+   - Nested Loop
+
+     A nested loop is used for queries that have a smaller data set connected. In a nested loop join, the foreign table drives the internal table and each row returned from the foreign table should have a matching row in the internal table. The returned result set of all queries should be less than 10,000. The table that returns a smaller subset will work as a foreign table, and indexes are recommended for connection columns of the internal table.
+
+   - (Sonic) Hash Join
+
+     A hash join is used for large tables. The optimizer uses a hash join, in which rows of one table are entered into an in-memory hash table, after which the other table is scanned and the hash table is probed for matches to each row. Sonic and non-Sonic hash joins differ in their hash table structures, which do not affect the execution result set.
+
+   - Merge Join
+
+     In most cases, the execution performance of a merge join is lower than that of a hash join. However, if the source data has been pre-sorted and no more sorting is needed during the merge join, its performance excels.
+
+3. Operators
+
+   - sort
+
+     Sorts the result set.
+
+   - filter
+
+     The **EXPLAIN** output shows the **WHERE** clause being applied as a **Filter** condition attached to the **Seq Scan** plan node. This means that the plan node checks the condition for each row it scans, and returns only the ones that meet the condition. The estimated number of output rows has been reduced because of the **WHERE** clause. However, the scan will still have to visit all 10,000 rows, as a result, the cost is not decreased. It increases a bit (by 10,000 x **cpu_operator_cost**) to reflect the extra CPU time spent on checking the **WHERE** condition.
+
+   - LIMIT
+
+     Limits the number of output execution results. If a **LIMIT** condition is added, not all rows are retrieved.
+
+### Execution Information
+
+The following SQL statement is used as an example:
+
+```sql
+select sum(t2.c1) from t1,t2 where t1.c1=t2.c2 group by t1.c2;
+```
+
+The output of running **EXPLAIN PERFORMANCE** is as follows:
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/introduction-to-the-sql-execution-plan-3.png)
diff --git a/product/en/docs-mogdb/v3.0/performance-tuning/2-sql/3-tuning-process.md b/product/en/docs-mogdb/v3.0/performance-tuning/2-sql/3-tuning-process.md
new file mode 100644
index 0000000000000000000000000000000000000000..13a7e6581f622f4dac505ab550eb62f5ac5eaf9b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/performance-tuning/2-sql/3-tuning-process.md
@@ -0,0 +1,33 @@
+---
+title: Tuning Process
+summary: Tuning Process
+author: Guo Huan
+date: 2021-03-16
+---
+
+# Tuning Process
+
+You can analyze slow SQL statements to optimize them.
+
+## Collect all table statistics associated with the SQL statements
+
+In a database, statistics indicate the source data of a plan generated by a planner. If no statistics are available or out of date, the execution plan may seriously deteriorate, leading to low performance. According to past experience, about 10% performance problems occurred because no statistics are collected. For details, see Updating Statistics.
+
+## View the execution plan to find out the cause
+
+If the SQL statements have been running for a long period of time and not ended, run the **EXPLAIN** statement to view the execution plan and then locate the fault. If the SQL statement has been properly executed, run the **EXPLAIN ANALYZE** or **EXPLAIN PERFORMANCE** statement to check the execution plan and information to locate the fault. For details about the execution plan, see Introduction to the SQL Execution Plan.
+
+## Locate the specific cause of slow SQL statements and improvement measures for EXPLAIN or EXPLAIN PERFORMANCE statement
+
+It can be analyzed in four ways:
+
+- SQL Self-Diagnosis
+
+- Subquery Tuning
+- Statistics Tuning
+
+- Operator-level tuning
+
+## Generally, some SQL statements can be converted to its equivalent statements in all or certain scenarios by rewriting querie
+
+SQL statements are simpler after they are rewritten. Some execution steps can be simplified to improve the performance. Query rewriting methods are universal in all databases.
diff --git a/product/en/docs-mogdb/v3.0/performance-tuning/2-sql/4-updating-statistics.md b/product/en/docs-mogdb/v3.0/performance-tuning/2-sql/4-updating-statistics.md
new file mode 100644
index 0000000000000000000000000000000000000000..15826f49d2ec243a1680326dec3e1525758a9cc7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/performance-tuning/2-sql/4-updating-statistics.md
@@ -0,0 +1,54 @@
+---
+title: Updating Statistics
+summary: Updating Statistics
+author: Guo Huan
+date: 2021-03-16
+---
+
+# Updating Statistics
+
+In a database, statistics indicate the source data of a plan generated by a planner. If no statistics are available or out of date, the execution plan may seriously deteriorate, leading to low performance.
+
+## Background
+
+The **ANALYZE** statement collects statistic about table contents in databases, which will be stored in the **PG_STATISTIC** system catalog. Then, the query optimizer uses the statistics to work out the most efficient execution plan.
+
+After executing batch insertions and deletions, you are advised to run the **ANALYZE** statement on the table or the entire library to update statistics. By default, 30,000 rows of statistics are sampled. That is, the default value of the GUC parameter **default_statistics_target** is **100**. If the total number of rows in the table exceeds 1,600,000, you are advised to set **default_statistics_target** to **-2**, indicating that 2% of the statistics are collected.
+
+For an intermediate table generated during the execution of a batch script or stored procedure, you also need to run the **ANALYZE** statement.
+
+If there are multiple inter-related columns in a table and the conditions or grouping operations based on these columns are involved in the query, collect statistics about these columns so that the query optimizer can accurately estimate the number of rows and generate an effective execution plan.
+
+## Procedure
+
+Run the following commands to update the statistics about a table or the entire database:
+
+```sql
+--Update statistics about a table.
+ANALYZE tablename;
+---Update statistics about the entire database.
+ANALYZE;
+```
+
+Run the following statements to perform statistics-related operations on multiple columns:
+
+```sql
+--Collect statistics about column_1 and column_2 of tablename.
+ANALYZE tablename ((column_1, column_2));
+
+--Declare statistics about column_1 and column_2 of tablename.
+ALTER TABLE tablename ADD STATISTICS ((column_1, column_2));
+
+--Collect statistics about one or more columns.
+ANALYZE tablename;
+
+--Delete statistics about column_1 and column_2 of tablename or their statistics declaration.
+ALTER TABLE tablename DELETE STATISTICS ((column_1, column_2));
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> After the statistics are declared for multiple columns by running the **ALTER TABLE** **tablename** **ADD STATISTICS** statement, the system collects the statistics about these columns next time **ANALYZE** is performed on the table or the entire database.
+> To collect the statistics, run the **ANALYZE** statement.
+>
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> Use **EXPLAIN** to show the execution plan of each SQL statement. If **rows=10** (the default value, probably indicating that the table has not been analyzed) is displayed in the **SEQ SCAN** output of a table, run the **ANALYZE** statement for this table.
diff --git a/product/en/docs-mogdb/v3.0/performance-tuning/2-sql/5-reviewing-and-modifying-a-table-definition.md b/product/en/docs-mogdb/v3.0/performance-tuning/2-sql/5-reviewing-and-modifying-a-table-definition.md
new file mode 100644
index 0000000000000000000000000000000000000000..05a4a6563f673076f8a143830241ccd3dd81600e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/performance-tuning/2-sql/5-reviewing-and-modifying-a-table-definition.md
@@ -0,0 +1,64 @@
+---
+title: Reviewing and Modifying a Table Definition
+summary: Reviewing and Modifying a Table Definition
+author: Guo Huan
+date: 2021-03-16
+---
+
+# Reviewing and Modifying a Table Definition
+
+## Overview
+
+To properly define a table, you must:
+
+1. **Reduce the data volume scanned** by using the partition pruning mechanism.
+2. **Minimize random I/Os** by using clustering or partial clustering.
+
+The table definition is created during the database design and is reviewed and modified during the SQL statement optimization.
+
+## Selecting a Storage Model
+
+During database design, some key factors about table design will greatly affect the subsequent query performance of the database. Table design affects data storage as well. Scientific table design reduces I/O operations and minimizes memory usage, improving the query performance.
+
+Selecting a model for table storage is the first step of table definition. Select a proper storage model for your service based on the following table.
+
+| **Storage Model** | **Application Scenario**                                     |
+| :---------------- | :----------------------------------------------------------- |
+| Row storage       | Point queries (simple index-based queries that only return a few records)<br/>Scenarios requiring frequent addition, deletion, and modification operations |
+| Column storage    | Statistics analysis query, in which operations, such as group and join, are performed many times |
+
+## Using PCKs
+
+1. The PCK is the column-store-based technology. It can minimize or maximize sparse indexes to quickly filter base tables. You are advised to select a maximum of two columns as PCKs. Use the following principles to specify PCKs:
+   1. The selected PCKs must be restricted by simple expressions in base tables. Such constraints are usually represented by **col op const**, in which **col** indicates the column name, **op** indicates operators, (including =, &gt;, &gt;=, &lt;=, and &lt;), and **const** indicates constants.
+   2. Select columns that are frequently selected (to filter much more undesired data) in simple expressions.
+   3. List the less frequently selected columns on the top.
+   4. List the columns of the enumerated type at the top.
+
+## Using Partitioned Tables
+
+Partitioning refers to splitting what is logically one large table into smaller physical pieces based on specific schemes. The table based on the logic is called a partitioned table, and a physical piece is called a partition. Data is stored in physical partitions not the logical table. A partitioned table has the following advantages over an ordinary table:
+
+1. High query performance: You can specify partitions when querying partitioned tables, improving query efficiency.
+2. High availability: If a certain partition in a partitioned table is faulty, data in the other partitions is still available.
+3. Easy maintenance: To fix a partitioned table having a faulty partition, you only need to fix the partition.
+
+MogDB supports range partitioned tables.
+
+Range partitioned table: Data in different ranges is mapped to different partitions. The range is determined by the partition key specified during the partitioned table creation. The partition key is usually a date. For example, sales data is partitioned by month.
+
+## Selecting a Data Type
+
+Use the following principles to select efficient data types:
+
+1. **Select data types that facilitate data calculation.**
+
+   Generally, the calculation of integers (including common comparison calculations, such as =, &gt;, &lt;, ≥, ≤, and ≠ and group by) is more efficient than that of strings and floating point numbers. For example, if you need to perform a point query on a column-store table whose numeric column is used as a filter condition, the query will take over 10s. If you change the data type from **NUMERIC** to **INT**, the query duration will be reduced to 1.8s.
+
+2. **Select data types with a short length.**
+
+   Data types with short length reduce both the data file size and the memory used for computing, improving the I/O and computing performance. For example, use **SMALLINT** instead of **INT**, and **INT** instead of **BIGINT**.
+
+3. **Use the same data type for a join.**
+
+   You are advised to use the same data type for a join. To join columns with different data types, the database needs to convert them to the same type, which leads to additional performance overheads.
diff --git a/product/en/docs-mogdb/v3.0/performance-tuning/2-sql/6-typical-sql-optimization-methods.md b/product/en/docs-mogdb/v3.0/performance-tuning/2-sql/6-typical-sql-optimization-methods.md
new file mode 100644
index 0000000000000000000000000000000000000000..f863aab3bf0c55654b25b7d2a1f14c78ba4233f6
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/performance-tuning/2-sql/6-typical-sql-optimization-methods.md
@@ -0,0 +1,704 @@
+---
+title: Typical SQL Optimization Methods
+summary: Typical SQL Optimization Methods
+author: Guo Huan
+date: 2021-03-16
+---
+
+# Typical SQL Optimization Methods
+
+SQL optimization involves continuous analysis and trying. Queries are run before they are used for services to determine whether the performance meets requirements. If it does not, queries will be optimized by checking the execution plan and identifying the causes. Then, the queries will be run and optimized again until they meet the requirements.
+
+## Optimizing SQL Self-Diagnosis
+
+Performance issues may occur when you query data or run the **INSERT**, **DELETE**, **UPDATE**, or **CREATE TABLE AS** statement. In this case, you can query the **warning** column in the PG_CONTROL_GROUP_CONFIG, GS_SESSION_MEMORY_DETAIL views to obtain reference for performance optimization.
+
+Alarms that can trigger SQL self diagnosis depend on the settings of **resource_track_level**. If **resource_track_level** is set to **query**, alarms about the failures in collecting column statistics and pushing down SQL statements will trigger the diagnosis. If **resource_track_level** is set to **operator**, all alarms will trigger the diagnosis.
+
+Whether a SQL plan will be diagnosed depends on the settings of **resource_track_cost**. A SQL plan will be diagnosed only if its execution cost is greater than **resource_track_cost**. You can use the **EXPLAIN** keyword to check the plan execution cost.
+
+### Alarms
+
+Currently, performance alarms will be reported when statistics about one or multiple columns are not collected.
+
+An alarm will be reported when statistics about one or multiple columns are not collected. For details about the optimization, see Updating Statistics and Optimizing Statistics.
+
+Example alarms:
+
+No statistics about a table are not collected.
+
+```
+Statistic Not Collect:
+    schema_test.t1
+```
+
+The statistics about a single column are not collected.
+
+```
+Statistic Not Collect:
+    schema_test.t2(c1,c2)
+```
+
+The statistics about multiple columns are not collected.
+
+```
+Statistic Not Collect:
+    schema_test.t3((c1,c2))
+```
+
+The statistics about a single column and multiple columns are not collected.
+
+```
+Statistic Not Collect:
+    schema_test.t4(c1,c2)    schema_test.t4((c1,c2))
+```
+
+### Restrictions
+
+1. An alarm contains a maximum of 2048 characters. If the length of an alarm exceeds this value (for example, a large number of long table names and column names are displayed in the alarm when their statistics are not collected), a warning instead of an alarm will be reported.
+
+   ```
+   WARNING, "Planner issue report is truncated, the rest of planner issues will be skipped"
+   ```
+
+2. If a query statement contains the **Limit** operator, alarms of operators lower than **Limit** will not be reported.
+
+## Optimizing Subqueries
+
+### Background
+
+When an application runs a SQL statement to operate the database, a large number of subqueries are used because they are more clear than table join. Especially in complicated query statements, subqueries have more complete and independent semantics, which makes SQL statements clearer and easier to understand. Therefore, subqueries are widely used.
+
+In MogDB, subqueries can also be called sublinks based on the location of subqueries in SQL statements.
+
+- Subquery: corresponds to a range table (RangeTblEntry) in the query parse tree. That is, a subquery is a **SELECT** statement following immediately after the **FROM** keyword.
+
+- Sublink: corresponds to an expression in the query parsing tree. That is, a sublink is a statement in the **WHERE** or **ON** clause or in the target list.
+
+  In conclusion, a subquery is a RangeTblEntry and a sublink is an expression in the query parsing tree. A sublink can be found in constraint conditions and expressions. In MogDB, sublinks can be classified into the following types:
+
+  - exist_sublink: corresponds to the **EXIST** and **NOT EXIST** statements.
+  - any_sublink: corresponding to the **op** **ALL(SELECT…)** statement. **op** can be the **IN**, **&lt;**, **&gt;**, or **=** operator.
+  - all_sublink: corresponding to the **op** **ALL(SELECT…)** statement. **op** can be the **IN**, **&lt;**, **&gt;**, or **=** operator.
+  - rowcompare_sublink: corresponds to the **RECORD** **op** **(SELECT…)** statement.
+  - expr_sublink: corresponds to the **(SELECT with a single target list item…)** statement.
+  - array_sublink: corresponds to the **ARRAY(SELECT…)** statement.
+  - cte_sublink: corresponds to the **WITH(…)** query statement.
+
+  The sublinks commonly used in OLAP and HTAP are exist_sublink and any_sublink. The sublinks are pulled up by the optimization engine of MogDB. Because of the flexible use of subqueries in SQL statements, complex subqueries may affect query performance. Subqueries are classified into non-correlated subqueries and correlated subqueries.
+
+  - **Non-correlated subqueries**
+
+    The execution of a subquery is independent from attributes of the outer query. In this way, a subquery can be executed before outer queries.
+
+    For example:
+
+    ```sql
+    select t1.c1,t1.c2
+    from t1
+    where t1.c1 in (
+        select c2
+        from t2
+        where t2.c2 IN (2,3,4)
+    );
+                                  QUERY PLAN
+    ----------------------------------------------------------------
+     Hash Join
+       Hash Cond: (t1.c1 = t2.c2)
+       ->  Seq Scan on t1
+             Filter: (c1 = ANY ('{2,3,4}'::integer[]))
+       ->  Hash
+             ->  HashAggregate
+                   Group By Key: t2.c2
+                   ->  Seq Scan on t2
+                         Filter: (c2 = ANY ('{2,3,4}'::integer[]))
+    (9 rows)
+
+    ```
+
+  - **Correlated subqueries**
+
+    The execution of a subquery depends on some attributes (used as **AND** conditions of the subquery) of outer queries. In the following example, **t1.c1** in the **t2.c1 = t1.c1** condition is a correlated attribute. Such a subquery depends on outer queries and needs to be executed once for each outer query.
+
+    For example:
+
+    ```sql
+    select t1.c1,t1.c2
+    from t1
+    where t1.c1 in (
+        select c2
+        from t2
+        where t2.c1 = t1.c1 AND t2.c2 in (2,3,4)
+    );
+                                   QUERY PLAN
+    ------------------------------------------------------------------------
+     Seq Scan on t1
+       Filter: (SubPlan 1)
+       SubPlan 1
+         ->  Seq Scan on t2
+               Filter: ((c1 = t1.c1) AND (c2 = ANY ('{2,3,4}'::integer[])))
+    (5 rows)
+    ```
+
+### Sublink Optimization on MogDB
+
+To optimize a sublink, a subquery is pulled up to join with tables in outer queries, preventing the subquery from being converted into a plan involving subplans and broadcast. You can run the **EXPLAIN** statement to check whether a sublink is converted into such a plan.
+
+For example:
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/typical-sql-optimization-methods-1.png)
+
+Replace the execution plan on the right of the arrow with the following execution plan:
+
+```sql
+QUERY PLAN
+--------------------------------
+Seq Scan on t1
+Filter: (SubPlan 1)
+SubPlan 1
+->  Seq Scan on t2
+Filter: (c1 = t1.c1)
+(5 rows)
+```
+
+- **Sublink-release scenarios supported by MogDB**
+
+  - Pulling up the **IN** sublink
+
+    - The subquery cannot contain columns in the outer query (columns in more outer queries are allowed).
+    - The subquery cannot contain volatile functions.
+
+    ![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/typical-sql-optimization-methods-2.png)
+
+    Replace the execution plan on the right of the arrow with the following execution plan:
+
+    ```sql
+    QUERY PLAN
+    --------------------------------------
+    Hash Join
+    Hash Cond: (t1.c1 = t2.c2)
+    ->  Seq Scan on t1
+    ->  Hash
+    ->  HashAggregate
+    Group By Key: t2.c2
+    ->  Seq Scan on t2
+    Filter: (c1 = 1)
+    (8 rows)
+    ```
+
+  - Pulling up the **EXISTS** sublink
+
+    The **WHERE** clause must contain a column in the outer query. Other parts of the subquery cannot contain the column. Other restrictions are as follows:
+
+    - The subquery must contain the **FROM** clause.
+    - The subquery cannot contain the **WITH** clause.
+    - The subquery cannot contain aggregate functions.
+    - The subquery cannot contain a **SET**, **SORT**, **LIMIT**, **WindowAgg**, or **HAVING** operation.
+    - The subquery cannot contain volatile functions.
+
+    ![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/typical-sql-optimization-methods-3.png)
+
+    Replace the execution plan on the right of the arrow with the following execution plan:
+
+    ```bash
+    QUERY PLAN
+    ------
+    Hash Join
+    Hash Cond: (t1.c1 = t2.c1)
+    -> Seq Scan on t1
+    -> Hash
+    -> HashAggregate
+    Group By Key: t2.c1
+    -> Seq Scan on t2
+    (7 rows)
+    ```
+
+  - Pulling up an equivalent correlated query containing aggregate functions
+
+    The **WHERE** condition of the subquery must contain a column from the outer query. Equivalence comparison must be performed between this column and related columns in tables of the subquery. These conditions must be connected using **AND**. Other parts of the subquery cannot contain the column. Other restrictions are as follows:
+
+    - The columns in the expression in the **WHERE** condition of the subquery must exist in tables.
+
+    - After the **SELECT** keyword of the subquery, there must be only one output column. The output column must be an aggregate function (for example, **MAX**), and the parameter (for example, **t2.c2**) of the aggregate function cannot be columns of a table (for example, **t1**) in outer queries. The aggregate function cannot be **COUNT**.
+
+      For example, the following subquery can be pulled up:
+
+      ```sql
+      select * from t1 where c1 >(
+             select max(t2.c1) from t2 where t2.c1=t1.c1
+      );
+      ```
+
+      The following subquery cannot be pulled up because the subquery has no aggregate function:
+
+      ```sql
+      select * from t1 where c1 >(
+             select  t2.c1 from t2 where t2.c1=t1.c1
+      );
+      ```
+
+      The following subquery cannot be pulled up because the subquery has two output columns:
+
+      ```sql
+      select * from t1 where (c1,c2) >(
+             select  max(t2.c1),min(t2.c2) from t2 where t2.c1=t1.c1
+      );
+      ```
+
+    - The subquery must be a **FROM** clause.
+
+    - The subquery cannot contain a **GROUP BY**, **HAVING**, or **SET** operation.
+
+    - The subquery can only be an inner join.
+
+      For example, the following subquery cannot be pulled up:
+
+      ```sql
+      select * from t1 where c1 >(
+             select max(t2.c1) from t2 full join t3 on (t2.c2=t3.c2) where t2.c1=t1.c1
+      );
+      ```
+
+    - The target list of the subquery cannot contain the function that returns a set.
+
+    - The **WHERE** condition of the subquery must contain a column from the outer query. Equivalence comparison must be performed between this column and related columns in tables of the subquery. These conditions must be connected using **AND**. Other parts of the subquery cannot contain the column. For example, the following subquery can be pulled up:
+
+      ```sql
+      select * from t3 where t3.c1=(
+              select t1.c1
+              from t1 where c1 >(
+                      select max(t2.c1) from t2 where t2.c1=t1.c1
+      ));
+      ```
+
+      If another condition is added to the subquery in the previous example, the subquery cannot be pulled up because the subquery references to the column in the outer query. For example:
+
+      ```sql
+      select * from t3 where t3.c1=(
+              select t1.c1
+              from t1 where c1 >(
+                     select max(t2.c1) from t2 where t2.c1=t1.c1 and t3.c1>t2.c2
+
+      ));
+      ```
+
+  - Pulling up a sublink in the **OR** clause
+
+    If the **WHERE** condition contains an **EXIST** correlated sublink connected by **OR**,
+
+    for example:
+
+    ```sql
+    select a, c from t1
+    where t1.a = (select avg(a) from t3 where t1.b = t3.b) or
+    exists (select * from t4 where t1.c = t4.c);
+    ```
+
+    the process of pulling up such a sublink is as follows:
+
+    1. Extract **opExpr** from the **OR** clause in the **WHERE** condition. The value is **t1.a = (select avg(a) from t3 where t1.b = t3.b)**.
+
+    2. The **opExpr** contains a subquery. If the subquery can be pulled up, the subquery is rewritten as **select avg(a), t3.b from t3 group by t3.b**, generating the **NOT NULL** condition **t3.b is not null**. The **opExpr** is replaced with this **NOT NULL** condition. In this case, the SQL statement changes to:
+
+       ```sql
+       select a, c
+       from t1 left join (select avg(a) avg, t3.b from t3 group by t3.b)  as t3 on (t1.a = avg and t1.b = t3.b)
+       where t3.b is not null or exists (select * from t4 where t1.c = t4.c);
+       ```
+
+    3. Extract the **EXISTS** sublink **exists (select * from t4 where t1.c = t4.c)** from the **OR** clause to check whether the sublink can be pulled up. If it can be pulled up, it is converted into **select t4.c from t4 group by t4.c**, generating the **NOT NULL** condition **t4.c is not null**. In this case, the SQL statement changes to:
+
+       ```sql
+       select a, c
+       from t1 left join (select avg(a) avg, t3.b from t3 group by t3.b)  as t3 on (t1.a = avg and t1.b = t3.b)
+       left join (select t4.c from t4 group by t4.c) where t3.b is not null or t4.c is not null;
+       ```
+
+- **Sublink-release scenarios not supported by MogDB**
+
+  Except the sublinks described above, all the other sublinks cannot be pulled up. In this case, a join subquery is planned as the combination of subplans and broadcast. As a result, if tables in the subquery have a large amount of data, query performance may be poor.
+
+  If a correlated subquery joins with two tables in outer queries, the subquery cannot be pulled up. You need to change the outer query into a **WITH** clause and then perform the join.
+
+  For example:
+
+  ```sql
+  select distinct t1.a, t2.a
+  from t1 left join t2 on t1.a=t2.a and not exists (select a,b from test1 where test1.a=t1.a and test1.b=t2.a);
+  ```
+
+  The outer query is changed into:
+
+  ```sql
+  with temp as
+  (
+          select * from (select t1.a as a, t2.a as b from t1 left join t2 on t1.a=t2.a)
+
+  )
+  select distinct a,b
+  from temp
+  where not exists (select a,b from test1 where temp.a=test1.a and temp.b=test1.b);
+  ```
+
+  - The subquery (without **COUNT**) in the target list cannot be pulled up.
+
+    For example:
+
+    ```
+    explain (costs off)
+    select (select c2 from t2 where t1.c1 = t2.c1) ssq, t1.c2
+    from t1
+    where t1.c2 > 10;
+    ```
+
+    The execution plan is as follows:
+
+    ```
+    explain (costs off)
+    select (select c2 from t2 where t1.c1 = t2.c1) ssq, t1.c2
+    from t1
+    where t1.c2 > 10;
+               QUERY PLAN
+    --------------------------------
+     Seq Scan on t1
+       Filter: (c2 > 10)
+       SubPlan 1
+         ->  Seq Scan on t2
+               Filter: (t1.c1 = c1)
+    (5 rows)
+    ```
+
+    The correlated subquery is displayed in the target list (query return list). Values need to be returned even if the condition **t1.c1=t2.c1** is not met. Therefore, use left outer join to join **T1** and **T2** so that SSQ can return padding values when the condition **t1.c1=t2.c1** is not met.
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+    > ScalarSubQuery (SSQ) and Correlated-ScalarSubQuery (CSSQ) are described as follows:
+    >
+    > - SSQ: a sublink that returns a scalar value of a single row with a single column
+    > - CSSQ: an SSQ containing correlation conditions
+
+    The preceding SQL statement can be changed into:
+
+    ```
+    with ssq as
+    (
+        select t2.c2 from t2
+    )
+    select ssq.c2, t1.c2
+    from t1 left join ssq on t1.c1 = ssq.c2
+    where t1.c2 > 10;
+    ```
+
+    The execution plan after the change is as follows:
+
+    ```
+               QUERY PLAN
+    ---------------------------------
+    Hash Right Join
+      Hash Cond: (ssq.c2 = t1.c1)
+      CTE ssq
+        ->  Seq Scan on t2
+      ->  CTE Scan on ssq
+      ->  Hash
+            ->  Seq Scan on t1
+                  Filter: (c2 > 10)
+    (8 rows)
+    ```
+
+    In the preceding example, the SSQ in the target list is pulled up to right join, preventing poor performance caused by the plan involving subplans when the table (**T2**) in the subquery is too large.
+
+  - The subquery (with **COUNT**) in the target list cannot be pulled up.
+
+    For example:
+
+    ```
+    select (select count(*) from t2 where t2.c1=t1.c1) cnt, t1.c1, t3.c1
+    from t1,t3
+    where t1.c1=t3.c1 order by cnt, t1.c1;
+    ```
+
+    The execution plan is as follows:
+
+    ```
+                    QUERY PLAN
+    --------------------------------------------
+    Sort
+      Sort Key: ((SubPlan 1)), t1.c1
+      ->  Hash Join
+            Hash Cond: (t1.c1 = t3.c1)
+            ->  Seq Scan on t1
+            ->  Hash
+                  ->  Seq Scan on t3
+            SubPlan 1
+              ->  Aggregate
+                    ->  Seq Scan on t2
+                          Filter: (c1 = t1.c1)
+    (11 rows)
+    ```
+
+    The correlated subquery is displayed in the target list (query return list). Values need to be returned even if the condition **t1.c1=t2.c1** is not met. Therefore, use left outer join to join **T1** and **T2** so that SSQ can return padding values when the condition **t1.c1=t2.c1** is not met. However, **COUNT** is used, which requires that **0** is returned when the condition is not met. Therefore, `case-when NULL then 0 else count(*)` can be used.
+
+    The preceding SQL statement can be changed into:
+
+    ```
+    with ssq as
+    (
+        select count(*) cnt, c1 from t2 group by c1
+    )
+    select case when
+                ssq.cnt is null then 0
+                else ssq.cnt
+           end cnt, t1.c1, t3.c1
+    from t1 left join ssq on ssq.c1 = t1.c1,t3
+    where t1.c1 = t3.c1
+    order by ssq.cnt, t1.c1;
+    ```
+
+    The execution plan after the change is as follows:
+
+    ```
+                    QUERY PLAN
+    -------------------------------------------
+    Sort
+      Sort Key: ssq.cnt, t1.c1
+      CTE ssq
+        ->  HashAggregate
+              Group By Key: t2.c1
+              ->  Seq Scan on t2
+      ->  Hash Join
+            Hash Cond: (t1.c1 = t3.c1)
+            ->  Hash Left Join
+                  Hash Cond: (t1.c1 = ssq.c1)
+                  ->  Seq Scan on t1
+                  ->  Hash
+                        ->  CTE Scan on ssq
+            ->  Hash
+                  ->  Seq Scan on t3
+    (15 rows)
+    ```
+
+  - Non-equivalent correlated subqueries cannot be pulled up.
+
+    For example:
+
+    ```
+    select t1.c1, t1.c2
+    from t1
+    where t1.c1 = (select agg() from t2.c2 > t1.c2);
+    ```
+
+    Non-equivalent correlated subqueries cannot be pulled up. You can perform join twice (one CorrelationKey and one rownum self-join) to rewrite the statement.
+
+    You can rewrite the statement in either of the following ways:
+
+    - Subquery rewriting
+
+      ```
+      select t1.c1, t1.c2
+      from t1, (
+          select t1.rowid, agg() aggref
+          from t1,t2
+          where t1.c2 > t2.c2 group by t1.rowid
+      ) dt /* derived table */
+      where t1.rowid = dt.rowid AND t1.c1 = dt.aggref;
+      ```
+
+    - CTE rewriting
+
+      ```
+      WITH dt as
+      (
+          select t1.rowid, agg() aggref
+          from t1,t2
+          where t1.c2 > t2.c2 group by t1.rowid
+      )
+      select t1.c1, t1.c2
+      from t1, derived_table
+      where t1.rowid = derived_table.rowid AND
+      t1.c1 = derived_table.aggref;
+      ```
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+    >
+    > - If the AGG type is **COUNT(\\*)**, **0** is used for data padding when **CASE-WHEN** is not matched. If the type is not **COUNT(\\*)**, **NULL** is used.
+    > - CTE rewriting works better by using share scan.
+
+### More Optimization Examples
+
+Modify the **SELECT** statement by changing the subquery to a **JOIN** relationship between the primary table and the parent query or modifying the subquery to improve the query performance. Ensure that the subquery to be used is semantically correct.
+
+```
+explain (costs off) select * from t1 where t1.c1 in (select t2.c1 from t2 where t1.c1 = t2.c2);
+           QUERY PLAN
+--------------------------------
+ Seq Scan on t1
+   Filter: (SubPlan 1)
+   SubPlan 1
+     ->  Seq Scan on t2
+           Filter: (t1.c1 = c2)
+(5 rows)
+```
+
+In the preceding example, a subplan is used. To remove the subplan, you can modify the statement as follows:
+
+```
+explain (costs off) select * from t1 where exists (select t2.c1 from t2 where t1.c1 = t2.c2 and t1.c1 = t2.c1);
+                QUERY PLAN
+------------------------------------------
+ Hash Join
+   Hash Cond: (t1.c1 = t2.c2)
+   ->  Seq Scan on t1
+   ->  Hash
+         ->  HashAggregate
+               Group By Key: t2.c2, t2.c1
+               ->  Seq Scan on t2
+                     Filter: (c2 = c1)
+(8 rows)
+```
+
+In this way, the subplan is replaced by the hash-join between the two tables, greatly improving the execution efficiency.
+
+## Optimizing Statistics
+
+### Background
+
+MogDB generates optimal execution plans based on the cost estimation. Optimizers need to estimate the number of data rows and the cost based on statistics collected using **ANALYZE**. Therefore, the statistics is vital for the estimation of the number of rows and cost. Global statistics are collected using **ANALYZE**: **relpages** and **reltuples** in the **pg_class** table; **stadistinct**, **stanullfrac**, **stanumbersN**, **stavaluesN**, and **histogram_bounds** in the **pg_statistic** table.
+
+### Example 1: Poor Query Performance Due to the Lack of Statistics
+
+In most cases, the lack of statistics about tables or columns involved in the query greatly affects the query performance.
+
+The table structure is as follows:
+
+```
+CREATE TABLE LINEITEM
+(
+L_ORDERKEY         BIGINT        NOT NULL
+, L_PARTKEY        BIGINT        NOT NULL
+, L_SUPPKEY        BIGINT        NOT NULL
+, L_LINENUMBER     BIGINT        NOT NULL
+, L_QUANTITY       DECIMAL(15,2) NOT NULL
+, L_EXTENDEDPRICE  DECIMAL(15,2) NOT NULL
+, L_DISCOUNT       DECIMAL(15,2) NOT NULL
+, L_TAX            DECIMAL(15,2) NOT NULL
+, L_RETURNFLAG     CHAR(1)       NOT NULL
+, L_LINESTATUS     CHAR(1)       NOT NULL
+, L_SHIPDATE       DATE          NOT NULL
+, L_COMMITDATE     DATE          NOT NULL
+, L_RECEIPTDATE    DATE          NOT NULL
+, L_SHIPINSTRUCT   CHAR(25)      NOT NULL
+, L_SHIPMODE       CHAR(10)      NOT NULL
+, L_COMMENT        VARCHAR(44)   NOT NULL
+) with (orientation = column, COMPRESSION = MIDDLE);
+
+CREATE TABLE ORDERS
+(
+O_ORDERKEY        BIGINT        NOT NULL
+, O_CUSTKEY       BIGINT        NOT NULL
+, O_ORDERSTATUS   CHAR(1)       NOT NULL
+, O_TOTALPRICE    DECIMAL(15,2) NOT NULL
+, O_ORDERDATE     DATE NOT NULL
+, O_ORDERPRIORITY CHAR(15)      NOT NULL
+, O_CLERK         CHAR(15)      NOT NULL
+, O_SHIPPRIORITY  BIGINT        NOT NULL
+, O_COMMENT       VARCHAR(79)   NOT NULL
+)with (orientation = column, COMPRESSION = MIDDLE);
+```
+
+The query statements are as follows:
+
+```
+explain verbose select
+count(*) as numwait
+from
+lineitem l1,
+orders
+where
+o_orderkey = l1.l_orderkey
+and o_orderstatus = 'F'
+and l1.l_receiptdate > l1.l_commitdate
+and not exists (
+select
+*
+from
+lineitem l3
+where
+l3.l_orderkey = l1.l_orderkey
+and l3.l_suppkey <> l1.l_suppkey
+and l3.l_receiptdate > l3.l_commitdate
+)
+order by
+numwait desc;
+```
+
+If such an issue occurs, you can use the following methods to check whether statistics in tables or columns has been collected using **ANALYZE**.
+
+1. Execute **EXPLAIN VERBOSE** to analyze the execution plan and check the warning information:
+
+   ```
+   WARNING:Statistics in some tables or columns(public.lineitem.l_receiptdate, public.lineitem.l_commitdate, public.lineitem.l_orderkey, public.lineitem.l_suppkey, public.orders.o_orderstatus, public.orders.o_orderkey) are not collected.
+   HINT:Do analyze for them in order to generate optimized plan.
+   ```
+
+2. Check whether the following information exists in the log file in the **pg_log** directory. If it does, the poor query performance was caused by the lack of statistics in some tables or columns.
+
+   ```
+   2017-06-14 17:28:30.336 CST 140644024579856 20971684 [BACKEND] LOG:Statistics in some tables or columns(public.lineitem.l_receiptdate, public.lineitem.l_commitdate, public.lineitem.l_orderkey, public.linei
+   tem.l_suppkey, public.orders.o_orderstatus, public.orders.o_orderkey) are not collected.
+   2017-06-14 17:28:30.336 CST 140644024579856 20971684 [BACKEND] HINT:Do analyze for them in order to generate optimized plan.
+   ```
+
+By using any of the preceding methods, you can identify tables or columns whose statistics have not been collected using **ANALYZE**. You can execute **ANALYZE** to warnings or tables and columns recorded in logs to resolve the problem.
+
+## Optimizing Operators
+
+### Background
+
+A query statement needs to go through multiple operator procedures to generate the final result. Sometimes, the overall query performance deteriorates due to long execution time of certain operators, which are regarded as bottleneck operators. In this case, you need to execute the **EXPLAIN ANALYZE** or **EXPLAIN PERFORMANCE** command to view the bottleneck operators, and then perform optimization.
+
+For example, in the following execution process, the execution time of the **Hashagg** operator accounts for about 66% [(51016-13535)/56476 ≈ 66%] of the total execution time. Therefore, the **Hashagg** operator is the bottleneck operator for this query. Optimize this operator first.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/typical-sql-optimization-methods-4.png)
+
+### Example
+
+1. Scan the base table. For queries requiring large volume of data filtering, such as point queries or queries that need range scanning, a full table scan using SeqScan will take a long time. To facilitate scanning, you can create indexes on the condition column and select IndexScan for index scanning.
+
+   ```
+   mogdb=#  explain (analyze on, costs off) select * from store_sales where ss_sold_date_sk = 2450944;
+   id |             operation          |       A-time        | A-rows | Peak Memory  | A-width
+   ----+--------------------------------+---------------------+--------+--------------+---------
+   1 | ->  Streaming (type: GATHER)   | 3666.020            |   3360 | 195KB        |
+   2 |    ->  Seq Scan on store_sales | [3594.611,3594.611] |   3360 | [34KB, 34KB] |
+   (2 rows)
+
+   Predicate Information (identified by plan id)
+   -----------------------------------------------
+   2 --Seq Scan on store_sales
+        Filter: (ss_sold_date_sk = 2450944)
+        Rows Removed by Filter: 4968936
+   ```
+
+   ```
+   mogdb=#  create index idx on store_sales_row(ss_sold_date_sk);
+   CREATE INDEX
+   mogdb=#  explain (analyze on, costs off) select * from store_sales_row where ss_sold_date_sk = 2450944;
+   id |                   operation                    |     A-time      | A-rows | Peak Memory  | A-width
+   ----+------------------------------------------------+-----------------+--------+--------------+----------
+   1 | ->  Streaming (type: GATHER)                   | 81.524          |   3360 | 195KB        |
+   2 |    ->  Index Scan using idx on store_sales_row | [13.352,13.352] |   3360 | [34KB, 34KB] |
+   (2 rows)
+   ```
+
+   In this example, the full table scan filters much data and returns 3360 records. After an index has been created on the **ss_sold_date_sk** column, the scanning efficiency is significantly boosted from 3.6s to 13 ms by using **IndexScan**.
+
+2. If NestLoop is used for joining tables with a large number of rows, the join may take a long time. In the following example, NestLoop takes 181s. If **enable_mergejoin** is set to **off** to disable merge join and **enable_nestloop** is set to **off** to disable NestLoop so that the optimizer selects hash join, the join takes more than 200 ms.
+
+   ![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/typical-sql-optimization-methods-5.png)
+
+   ![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/typical-sql-optimization-methods-6.png)
+
+3. Generally, query performance can be improved by selecting **HashAgg**. If **Sort** and **GroupAgg** are used for a large result set, you need to set **enable_sort** to **off**. **HashAgg** consumes less time than **Sort** and **GroupAgg**.
+
+   ![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/typical-sql-optimization-methods-7.png)
+   
+   ![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/typical-sql-optimization-methods-8.png)
diff --git a/product/en/docs-mogdb/v3.0/performance-tuning/2-sql/7-experience-in-rewriting-sql-statements.md b/product/en/docs-mogdb/v3.0/performance-tuning/2-sql/7-experience-in-rewriting-sql-statements.md
new file mode 100644
index 0000000000000000000000000000000000000000..8da3b8aa60afba183353bb38c2b02edf7dc70511
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/performance-tuning/2-sql/7-experience-in-rewriting-sql-statements.md
@@ -0,0 +1,63 @@
+---
+title: Experience in Rewriting SQL Statements
+summary: Experience in Rewriting SQL Statements
+author: Guo Huan
+date: 2021-03-16
+---
+
+# Experience in Rewriting SQL Statements
+
+Based on the SQL execution mechanism and a large number of practices, SQL statements can be optimized by following certain rules to enable the database to execute SQL statements more quickly and obtain correct results. You can comply with these rules to improve service query efficiency.
+
+- Replace **UNION** with **UNION ALL**.
+
+  **UNION** eliminates duplicate rows while merging two result sets but **UNION ALL** merges the two result sets without deduplication. Therefore, replace **UNION** with **UNION ALL** if you are sure that the two result sets do not contain duplicate rows based on the service logic.
+
+- Add **NOT NULL** to the join columns.
+
+  If there are many NULL values in the **JOIN** columns, you can add the filter criterion **IS NOT NULL** to filter data in advance to improve the **JOIN** efficiency.
+
+- Convert **NOT IN** to **NOT EXISTS**.
+
+  **nestloop anti join** must be used to implement **NOT IN**, and **hash anti join** is required for **NOT EXISTS**. If no NULL value exists in the **JOIN** columns, **NOT IN** is equivalent to **NOT EXISTS**. Therefore, if you are sure that no NULL value exists, you can convert **NOT IN** to **NOT EXISTS** to generate **hash join** and to improve the query performance.
+
+  As shown in the following statement, the **t2.d2** column does not contain null values (it is set to **NOT NULL**) and **NOT EXISTS** is used for the query.
+
+  ```sql
+  SELECT * FROM t1 WHERE  NOT EXISTS (SELECT * FROM t2 WHERE t1.c1=t2.d2);
+  ```
+
+  The generated execution plan is as follows:
+
+  ```
+  QUERY PLAN
+  ------------------------------
+  Hash Anti Join
+  Hash Cond: (t1.c1 = t2.d2)
+  ->  Seq Scan on t1
+  ->  Hash
+  ->  Seq Scan on t2
+  (5 rows)
+  ```
+
+- Use **hashagg**.
+
+  If a plan involving groupAgg and SORT operations generated by the **GROUP BY** statement is poor in performance, you can set **work_mem** to a larger value to generate a **hashagg** plan, which does not require sorting and improves the performance.
+
+- Replace functions with **CASE** statements.
+
+  The MogDB performance greatly deteriorates if a large number of functions are called. In this case, you can change the pushdown functions to **CASE** statements.
+
+- Do not use functions or expressions for indexes.
+
+  Using functions or expressions for indexes stops indexing. Instead, it enables scanning on the full table.
+
+- Do not use **!=** or &lt;&gt; operators, **NULL**, **OR**, or implicit parameter conversion in **WHERE** clauses.
+
+- Split complex SQL statements.
+
+  You can split an SQL statement into several ones and save the execution result to a temporary table if the SQL statement is too complex to be tuned using the solutions above, including but not limited to the following scenarios:
+
+  - The same subquery is involved in multiple SQL statements of a job and the subquery contains large amounts of data.
+  - Incorrect plan cost causes a small hash bucket of subquery. For example, the actual number of rows is 10 million, but only 1000 rows are in hash bucket.
+  - Functions such as **substr** and **to_number** cause incorrect measures for subqueries containing large amounts of data.
diff --git a/product/en/docs-mogdb/v3.0/performance-tuning/2-sql/8-resetting-key-parameters-during-sql-tuning.md b/product/en/docs-mogdb/v3.0/performance-tuning/2-sql/8-resetting-key-parameters-during-sql-tuning.md
new file mode 100644
index 0000000000000000000000000000000000000000..007aeedab93827b58d42f57186ca982f9a171ec7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/performance-tuning/2-sql/8-resetting-key-parameters-during-sql-tuning.md
@@ -0,0 +1,22 @@
+---
+title: Resetting Key Parameters During SQL Tuning
+summary: Resetting Key Parameters During SQL Tuning
+author: Guo Huan
+date: 2021-03-16
+---
+
+# Resetting Key Parameters During SQL Tuning
+
+| Parameter/Reference Value | Description                                                  |
+| :------------------------ | :----------------------------------------------------------- |
+| enable_nestloop=on        | Specifies how the optimizer uses **Nest Loop Join**. If this parameter is set to **on**, the optimizer preferentially uses **Nest Loop Join**. If it is set to **off**, the optimizer preferentially uses other methods, if any.<br/>NOTE:<br/>If you only want to temporarily change the value of this parameter during the current database connection (that is, the current session), execute the following SQL statement:<br/>`SET enable_nestloop to off;`<br/>By default, this parameter is set to **on**. Change the value as required. Generally, nested loop join has the poorest performance among the three **JOIN** methods (nested loop join, merge join, and hash join). You are advised to set this parameter to **off**. |
+| enable_bitmapscan=on      | Specifies whether the optimizer uses bitmap scanning. If the value is **on**, bitmap scanning is used. If the value is **off**, it is not used.<br/>NOTE:<br/>If you only want to temporarily change the value of this parameter during the current database connection (that is, the current session), execute the following SQL statement:<br/>`SET enable_bitmapscan to off;`<br/>The bitmap scanning applies only in the query condition where **a &gt; 1 and b &gt; 1** and indexes are created on columns **a** and **b**. During performance tuning, if the query performance is poor and bitmapscan operators are in the execution plan, set this parameter to **off** and check whether the performance is improved. |
+| enable_hashagg=on         | Specifies whether to enable the optimizer's use of Hash-aggregation plan types. |
+| enable_hashjoin=on        | Specifies whether to enable the optimizer's use of Hash-join plan types. |
+| enable_mergejoin=on       | Specifies whether to enable the optimizer's use of Hash-merge plan types. |
+| enable_indexscan=on       | Specifies whether to enable the optimizer's use of index-scan plan types. |
+| sql_beta_feature          | Specifies whether to enable the optimizer's use of index-only-scan plan types. |
+| enable_seqscan=on         | Specifies whether the optimizer uses bitmap scanning. It is impossible to suppress sequential scans entirely, but setting this variable to **off** encourages the optimizer to choose other methods if available. |
+| enable_sort=on            | Specifies the optimizer sorts. It is impossible to fully suppress explicit sorts, but setting this variable to **off** allows the optimizer to preferentially choose other methods if available. |
+| rewrite_rule              | Specifies whether the optimizer enables the **LAZY\_AGG** and **MAGIC_SET** rewriting rules. |
+| sql_beta_feature          | Controls whether the optimizer is enabled. SEL SEMI POISSON/SEL EXPR INSTR/PARAM PATH GEN/RAND COST OPT/PARAM PATH OPT/PAGE EST Opt test function. |
diff --git a/product/en/docs-mogdb/v3.0/performance-tuning/2-sql/9-hint-based-tuning.md b/product/en/docs-mogdb/v3.0/performance-tuning/2-sql/9-hint-based-tuning.md
new file mode 100644
index 0000000000000000000000000000000000000000..735566fe35a7b3436762880258638c8a022d2aa5
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/performance-tuning/2-sql/9-hint-based-tuning.md
@@ -0,0 +1,704 @@
+---
+title: Hint-based Tuning
+summary: Hint-based Tuning
+author: Guo Huan
+date: 2021-03-16
+---
+
+# Hint-based Tuning
+
+## Plan Hint Optimization
+
+In plan hints, you can specify a join order, join and scan operations, and the number of rows in a result to tune an execution plan, improving query performance.
+
+### Function
+
+The hint syntax must follow immediately after a **SELECT** keyword and is written in the following format:
+
+```
+/*+ <plan hint>*/
+```
+
+You can specify multiple hints for a query plan and separate them by spaces. A hint specified for a query plan does not apply to its subquery plans. To specify a hint for a subquery, add the hint following the **SELECT** of this subquery.
+
+For example:
+
+```sql
+select /*+ <plan_hint1> <plan_hint2> */ * from t1, (select /*+ <plan_hint3> */ from t2) where 1=1;
+```
+
+In the preceding command, &lt;**plan_hint1**&gt; and &lt;**plan_hint2**&gt; are the hints of a query, and &lt;**plan_hint3**&gt; is the hint of its subquery.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> If a hint is specified in the **CREATE VIEW** statement, the hint will be applied each time this view is used.
+> If the random plan function is enabled (**plan_mode_seed** is set to a value other than 0), the specified hint will not be used.
+
+### Scope
+
+Currently, the following hints are supported:
+
+- Join order hints (**leading**)
+- Join operation hints, excluding the **semi join**, **anti join**, and **unique plan** hints
+- Rows hints
+- Scan operation hints, supporting only **tablescan**, **indexscan**, and **indexonlyscan**
+- Sublink name hints
+
+### Precautions
+
+Hints do not support **Agg**, **Sort**, **Setop**, or **Subplan**.
+
+### Example
+
+The following is the original plan and is used for comparing with the optimized ones:
+
+```sql
+create table store
+(
+    s_store_sk                integer               not null,
+    s_store_id                char(16)              not null,
+    s_rec_start_date          date                          ,
+    s_rec_end_date            date                          ,
+    s_closed_date_sk          integer                       ,
+    s_store_name              varchar(50)                   ,
+    s_number_employees        integer                       ,
+    s_floor_space             integer                       ,
+    s_hours                   char(20)                      ,
+    s_manager                 varchar(40)                   ,
+    s_market_id               integer                       ,
+    s_geography_class         varchar(100)                  ,
+    s_market_desc             varchar(100)                  ,
+    s_market_manager          varchar(40)                   ,
+    s_division_id             integer                       ,
+    s_division_name           varchar(50)                   ,
+    s_company_id              integer                       ,
+    s_company_name            varchar(50)                   ,
+    s_street_number           varchar(10)                   ,
+    s_street_name             varchar(60)                   ,
+    s_street_type             char(15)                      ,
+    s_suite_number            char(10)                      ,
+    s_city                    varchar(60)                   ,
+    s_county                  varchar(30)                   ,
+    s_state                   char(2)                       ,
+    s_zip                     char(10)                      ,
+    s_country                 varchar(20)                   ,
+    s_gmt_offset              decimal(5,2)                  ,
+    s_tax_precentage          decimal(5,2)                  ,
+    primary key (s_store_sk)
+);
+create table store_sales
+(
+    ss_sold_date_sk           integer                       ,
+    ss_sold_time_sk           integer                       ,
+    ss_item_sk                integer               not null,
+    ss_customer_sk            integer                       ,
+    ss_cdemo_sk               integer                       ,
+    ss_hdemo_sk               integer                       ,
+    ss_addr_sk                integer                       ,
+    ss_store_sk               integer                       ,
+    ss_promo_sk               integer                       ,
+    ss_ticket_number          integer               not null,
+    ss_quantity               integer                       ,
+    ss_wholesale_cost         decimal(7,2)                  ,
+    ss_list_price             decimal(7,2)                  ,
+    ss_sales_price            decimal(7,2)                  ,
+    ss_ext_discount_amt       decimal(7,2)                  ,
+    ss_ext_sales_price        decimal(7,2)                  ,
+    ss_ext_wholesale_cost     decimal(7,2)                  ,
+    ss_ext_list_price         decimal(7,2)                  ,
+    ss_ext_tax                decimal(7,2)                  ,
+    ss_coupon_amt             decimal(7,2)                  ,
+    ss_net_paid               decimal(7,2)                  ,
+    ss_net_paid_inc_tax       decimal(7,2)                  ,
+    ss_net_profit             decimal(7,2)                  ,
+    primary key (ss_item_sk, ss_ticket_number)
+);
+create table store_returns
+(
+    sr_returned_date_sk       integer                       ,
+    sr_return_time_sk         integer                       ,
+    sr_item_sk                integer               not null,
+    sr_customer_sk            integer                       ,
+    sr_cdemo_sk               integer                       ,
+    sr_hdemo_sk               integer                       ,
+    sr_addr_sk                integer                       ,
+    sr_store_sk               integer                       ,
+    sr_reason_sk              integer                       ,
+    sr_ticket_number          integer               not null,
+    sr_return_quantity        integer                       ,
+    sr_return_amt             decimal(7,2)                  ,
+    sr_return_tax             decimal(7,2)                  ,
+    sr_return_amt_inc_tax     decimal(7,2)                  ,
+    sr_fee                    decimal(7,2)                  ,
+    sr_return_ship_cost       decimal(7,2)                  ,
+    sr_refunded_cash          decimal(7,2)                  ,
+    sr_reversed_charge        decimal(7,2)                  ,
+    sr_store_credit           decimal(7,2)                  ,
+    sr_net_loss               decimal(7,2)                  ,
+    primary key (sr_item_sk, sr_ticket_number)
+);
+create table customer
+(
+    c_customer_sk             integer               not null,
+    c_customer_id             char(16)              not null,
+    c_current_cdemo_sk        integer                       ,
+    c_current_hdemo_sk        integer                       ,
+    c_current_addr_sk         integer                       ,
+    c_first_shipto_date_sk    integer                       ,
+    c_first_sales_date_sk     integer                       ,
+    c_salutation              char(10)                      ,
+    c_first_name              char(20)                      ,
+    c_last_name               char(30)                      ,
+    c_preferred_cust_flag     char(1)                       ,
+    c_birth_day               integer                       ,
+    c_birth_month             integer                       ,
+    c_birth_year              integer                       ,
+    c_birth_country           varchar(20)                   ,
+    c_login                   char(13)                      ,
+    c_email_address           char(50)                      ,
+    c_last_review_date        char(10)                      ,
+    primary key (c_customer_sk)
+);
+create table promotion
+(
+    p_promo_sk                integer               not null,
+    p_promo_id                char(16)              not null,
+    p_start_date_sk           integer                       ,
+    p_end_date_sk             integer                       ,
+    p_item_sk                 integer                       ,
+    p_cost                    decimal(15,2)                 ,
+    p_response_target         integer                       ,
+    p_promo_name              char(50)                      ,
+    p_channel_dmail           char(1)                       ,
+    p_channel_email           char(1)                       ,
+    p_channel_catalog         char(1)                       ,
+    p_channel_tv              char(1)                       ,
+    p_channel_radio           char(1)                       ,
+    p_channel_press           char(1)                       ,
+    p_channel_event           char(1)                       ,
+    p_channel_demo            char(1)                       ,
+    p_channel_details         varchar(100)                  ,
+    p_purpose                 char(15)                      ,
+    p_discount_active         char(1)                       ,
+    primary key (p_promo_sk)
+);
+create table customer_address
+(
+    ca_address_sk             integer               not null,
+    ca_address_id             char(16)              not null,
+    ca_street_number          char(10)                      ,
+    ca_street_name            varchar(60)                   ,
+    ca_street_type            char(15)                      ,
+    ca_suite_number           char(10)                      ,
+    ca_city                   varchar(60)                   ,
+    ca_county                 varchar(30)                   ,
+    ca_state                  char(2)                       ,
+    ca_zip                    char(10)                      ,
+    ca_country                varchar(20)                   ,
+    ca_gmt_offset             decimal(5,2)                  ,
+    ca_location_type          char(20)                      ,
+    primary key (ca_address_sk)
+);
+create table item
+(
+    i_item_sk                 integer               not null,
+    i_item_id                 char(16)              not null,
+    i_rec_start_date          date                          ,
+    i_rec_end_date            date                          ,
+    i_item_desc               varchar(200)                  ,
+    i_current_price           decimal(7,2)                  ,
+    i_wholesale_cost          decimal(7,2)                  ,
+    i_brand_id                integer                       ,
+    i_brand                   char(50)                      ,
+    i_class_id                integer                       ,
+    i_class                   char(50)                      ,
+    i_category_id             integer                       ,
+    i_category                char(50)                      ,
+    i_manufact_id             integer                       ,
+    i_manufact                char(50)                      ,
+    i_size                    char(20)                      ,
+    i_formulation             char(20)                      ,
+    i_color                   char(20)                      ,
+    i_units                   char(10)                      ,
+    i_container               char(10)                      ,
+    i_manager_id              integer                       ,
+    i_product_name            char(50)                      ,
+    primary key (i_item_sk)
+);
+explain
+select i_product_name product_name
+,i_item_sk item_sk
+,s_store_name store_name
+,s_zip store_zip
+,ad2.ca_street_number c_street_number
+,ad2.ca_street_name c_street_name
+,ad2.ca_city c_city
+,ad2.ca_zip c_zip
+,count(*) cnt
+,sum(ss_wholesale_cost) s1
+,sum(ss_list_price) s2
+,sum(ss_coupon_amt) s3
+FROM   store_sales
+,store_returns
+,store
+,customer
+,promotion
+,customer_address ad2
+,item
+WHERE  ss_store_sk = s_store_sk AND
+ss_customer_sk = c_customer_sk AND
+ss_item_sk = i_item_sk and
+ss_item_sk = sr_item_sk and
+ss_ticket_number = sr_ticket_number and
+c_current_addr_sk = ad2.ca_address_sk and
+ss_promo_sk = p_promo_sk and
+i_color in ('maroon','burnished','dim','steel','navajo','chocolate') and
+i_current_price between 35 and 35 + 10 and
+i_current_price between 35 + 1 and 35 + 15
+group by i_product_name
+,i_item_sk
+,s_store_name
+,s_zip
+,ad2.ca_street_number
+,ad2.ca_street_name
+,ad2.ca_city
+,ad2.ca_zip
+;
+```
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/hint-based-tuning-1.png)
+
+## Join Order Hints
+
+### Function
+
+Theses hints specify the join order and outer/inner tables.
+
+### Syntax
+
+- Specify only the join order.
+
+  ```
+  leading(join_table_list)
+  ```
+
+- Specify the join order and outer/inner tables. The outer/inner tables are specified by the outermost parentheses.
+
+  ```
+  leading((join_table_list))
+  ```
+
+## Parameter Description
+
+**join_table_list** specifies the tables to be joined. The values can be table names or table aliases. If a subquery is pulled up, the value can also be the subquery alias. Separate the values with spaces. You can add parentheses to specify the join priorities of tables.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> A table name or alias can only be a string without a schema name.
+> An alias (if any) is used to represent a table.
+
+To prevent semantic errors, tables in the list must meet the following requirements:
+
+- The tables must exist in the query or its subquery to be pulled up.
+- The table names must be unique in the query or subquery to be pulled up. If they are not, their aliases must be unique.
+- A table appears only once in the list.
+- An alias (if any) is used to represent a table.
+
+For example:
+
+**leading(t1 t2 t3 t4 t5)**:**t1**, **t2**, **t3**, **t4**, and **t5** are joined. The join order and outer/inner tables are not specified.
+
+**leading((t1 t2 t3 t4 t5))**:**t1**, **t2**, **t3**, **t4**, and **t5** are joined in sequence. The table on the right is used as the inner table in each join.
+
+**leading(t1 (t2 t3 t4) t5)**: First, **t2**, **t3**, and **t4** are joined and the outer/inner tables are not specified. Then, the result is joined with **t1** and **t5**, and the outer/inner tables are not specified.
+
+**leading((t1 (t2 t3 t4) t5))**: First, **t2**, **t3**, and **t4** are joined and the outer/inner tables are not specified. Then, the result is joined with **t1**, and **(t2 t3 t4)** is used as the inner table. Finally, the result is joined with **t5**, and **t5** is used as the inner table.
+
+**leading((t1 (t2 t3) t4 t5)) leading((t3 t2))**: First, **t2** and **t3** are joined and **t2** is used as the inner table. Then, the result is joined with **t1**, and **(t2 t3)** is used as the inner table. Finally, the result is joined with **t4** and then **t5**, and the table on the right in each join is used as the inner table.
+
+### Example
+
+Hint the query plan in Example as follows:
+
+```sql
+explain
+select /*+ leading((((((store_sales store) promotion) item) customer) ad2) store_returns) leading((store store_sales))*/ i_product_name product_name ...
+```
+
+First, **store_sales** and **store** are joined and **store_sales** is the inner table. Then, the result is joined with **promotion**, **item**, **customer**, **ad2**, and **store_returns** in sequence. The optimized plan is as follows:
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/hint-based-tuning-2.png)
+
+## Join Operation Hints
+
+### Function
+
+These hints specify the join method, which can be nested loop join, hash join, or merge join.
+
+### Syntax
+
+```
+[no] nestloop|hashjoin|mergejoin(table_list)
+```
+
+### Parameter Description
+
+- **no** indicates that the specified hint will not be used for a join.
+- **table_list** specifies the tables to be joined. The values are the same as those of **join_table_list** but contain no parentheses.
+
+For example:
+
+**no nestloop(t1 t2 t3)**:**nestloop** is not used for joining **t1**, **t2**, and **t3**. The three tables may be joined in either of the two ways: Join **t2** and **t3**, and then **t1**; join **t1** and **t2**, and then **t3**. This hint takes effect only for the last join. If necessary, you can hint other joins. For example, you can add **no nestloop(t2 t3)** to join **t2** and **t3** first and to forbid the use of **nestloop**.
+
+### Example
+
+Hint the query plan in Example as follows:
+
+```sql
+explain
+select /*+ nestloop(store_sales store_returns item) */ i_product_name product_name ...
+```
+
+**nestloop** is used for the last join between **store_sales**, **store_returns**, and **item**. The optimized plan is as follows:
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/hint-based-tuning-3.png)
+
+## Rows Hints
+
+### Function
+
+These hints specify the number of rows in an intermediate result set. Both absolute values and relative values are supported.
+
+### Syntax
+
+```
+rows(table_list #|+|-|* const)
+```
+
+### Parameter Description
+
+- **#**, **+**, **-**, and **\*** are operators used for hinting the estimation. **#** indicates that the original estimation is used without any calculation. **+**, **-**, and **\*** indicate that the original estimation is calculated using these operators. The minimum calculation result is 1. *table_list* specifies the tables to be joined. The values are the same as those of **table_list** in Join Operation Hints.
+- **const** can be any non-negative number and supports scientific notation.
+
+For example:
+
+**rows(t1 #5)**: The result set of **t1** is five rows.
+
+**rows(t1 t2 t3 \*1000)**: Multiply the result set of joined **t1**, **t2**, and **t3** by 1000.
+
+### Suggestion
+
+- The hint using **\*** for two tables is recommended. This hint will be triggered if the two tables appear on two sides of a join. For example, if the hint is **rows(t1 t2 \* 3)**, the join result of **(t1 t3 t4)** and **(t2 t5 t6)** will be multiplied by 3 because **t1** and **t2** appear on both sides of the join.
+- **rows** hints can be specified for the result sets of a single table, multiple tables, function tables, and subquery scan tables.
+
+### Example
+
+Hint the query plan in Example as follows:
+
+```sql
+explain
+select /*+ rows(store_sales store_returns *50) */ i_product_name product_name ...
+```
+
+Multiply the result set of joined **store_sales** and **store_returns** by 50. The optimized plan is as follows:
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/hint-based-tuning-4.png)
+
+## Scan Operation Hints
+
+### Function
+
+These hints specify a scan operation, which can be **tablescan**, **indexscan**, or **indexonlyscan**.
+
+### Syntax
+
+```
+[no] tablescan|indexscan|indexonlyscan(table [index])
+```
+
+### Parameter Description
+
+- **no** indicates that the specified hint will not be used for a join.
+- **table** specifies the table to be scanned. You can specify only one table. Use a table alias (if any) instead of a table name.
+- **index** indicates the index for **indexscan** or **indexonlyscan**. You can specify only one index.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> **indexscan** and **indexonlyscan** hints can be used only when the specified index belongs to the table.
+> Scan operation hints can be used for row-store tables, column-store tables, OBS tables, and subquery tables.
+
+### Example
+
+To specify an index-based hint for a scan, create an index named **i** on the **i_item_sk** column of the **item** table.
+
+```sql
+create index i on item(i_item_sk);
+```
+
+Hint the query plan in Example as follows:
+
+```
+explain
+select /*+ indexscan(item i) */ i_product_name product_name ...
+```
+
+**item** is scanned based on an index. The optimized plan is as follows:
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/hint-based-tuning-5.png)
+
+## Sublink Name Hints
+
+### Function
+
+These hints specify the name of a sublink block.
+
+### Syntax
+
+```
+blockname (table)
+```
+
+### Parameter Description
+
+- **table** specifies the name you have specified for a sublink block.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - The **blockname** hint is used by an outer query only when a sublink is pulled up. Currently, only the **Agg** equivalent join, **IN**, and **EXISTS** sublinks can be pulled up. This hint is usually used together with the hints described in the previous sections.
+> - The subquery after the **FROM** keyword is hinted by using the subquery alias. In this case, **blockname** becomes invalid.
+> - If a sublink contains multiple tables, the tables will be joined with the outer-query tables in a random sequence after the sublink is pulled up. In this case, **blockname** also becomes invalid.
+
+### Example
+
+```
+explain select /*+nestloop(store_sales tt) */ * from store_sales where ss_item_sk in (select /*+blockname(tt)*/ i_item_sk from item group by 1);
+```
+
+**tt** indicates the sublink block name. After being pulled up, the sublink is joined with the outer-query table **store_sales** by using **nestloop**. The optimized plan is as follows:
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/hint-based-tuning-6.png)
+
+## Hint Errors, Conflicts, and Other Warnings
+
+Plan hints change an execution plan. You can run **EXPLAIN** to view the changes.
+
+Hints containing errors are invalid and do not affect statement execution. The errors will be displayed in different ways based on statement types. Hint errors in an **EXPLAIN** statement are displayed as a warning on the interface. Hint errors in other statements will be recorded in debug1-level logs containing the **PLANHINT** keyword.
+
+Hint error types are as follows:
+
+- Syntax errors
+
+  An error will be reported if the syntax tree fails to be reduced. The No. of the row generating an error is displayed in the error details.
+
+  For example, the hint keyword is incorrect, no table or only one table is specified in the **leading** or **join** hint, or no tables are specified in other hints. The parsing of a hint is terminated immediately after a syntax error is detected. Only the hints that have been parsed successfully are valid.
+
+  For example:
+
+  ```
+  leading((t1 t2)) nestloop(t1) rows(t1 t2 #10)
+  ```
+
+  The syntax of **nestloop(t1)** is wrong and its parsing is terminated. Only **leading(t1 t2)** that has been successfully parsed before **nestloop(t1)** is valid.
+
+- Semantic errors
+
+  - An error will be reported if the specified tables do not exist, multiple tables are found based on the hint setting, or a table is used more than once in the **leading** or **join** hint.
+  - An error will be reported if the index specified in a scan hint does not exist.
+  - If multiple tables with the same name exist after a subquery is pulled up and some of them need to be hinted, add aliases for them to avoid name duplication.
+
+- Duplicated or conflicted hints
+
+    If hint duplication or conflicts occur, only the first hint takes effect. A message will be displayed to describe the situation.
+
+  - Hint duplication indicates that a hint is used more than once in the same query, for example, **nestloop(t1 t2) nestloop(t1 t2)**.
+
+  - A hint conflict indicates that the functions of two hints with the same table list conflict with each other.
+
+    For example, if **nestloop (t1 t2) hashjoin (t1 t2)** is used, **hashjoin (t1 t2)** becomes invalid. **nestloop(t1 t2)** does not conflict with **no mergejoin(t1 t2)**.
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+    > The table list in the **leading** hint is disassembled. For example, **leading ((t1 t2 t3))** will be disassembled as **leading((t1 t2)) leading(((t1 t2) t3))**, which will conflict with **leading((t2 t1))** (if any). In this case, the latter **leading(t2 t1)** becomes invalid. If two hints use duplicated table lists and only one of them has the specified outer/inner table, the one without a specified outer/inner table becomes invalid.
+
+- A hint becomes invalid after a sublink is pulled up.
+
+  In this case, a message will be displayed. Generally, such invalidation occurs when a sublink contains multiple tables to be joined. After the sublink is pulled up, the tables will not be join members.
+
+- Unsupported column types
+
+  - Skew hints are specified to optimize redistribution. They will be invalid if their corresponding columns do not support redistribution.
+
+- Hints are not used.
+
+  - If **hashjoin** or **mergejoin** is specified for non-equivalent joins, it will not be used.
+  - If **indexscan** or **indexonlyscan** is specified for a table that does not have an index, it will not be used.
+  - If **indexscan hint** or **indexonlyscan** is specified for a full-table scan or for a scan whose filtering conditions are not set on index columns, it will not be used.
+  - The specified **indexonlyscan** hint is used only when the output column contains only indexes.
+  - In equivalent joins, only the joins containing equivalence conditions are valid. Therefore, the **leading**, **join**, and **rows** hints specified for the joins without an equivalence condition will not be used. For example, **t1**, **t2**, and **t3** are to be joined, and the join between **t1** and **t3** does not contain an equivalence condition. In this case, **leading(t1 t3)** will not be used.
+  - To generate a streaming plan, if the distribution key of a table is the same as its join key, **redistribute** specified for this table will not be used. If the distribution key and join key are different for this table but the same for the other table in the join, **redistribute** specified for this table will be used but **broadcast** will not.
+  - If no sublink is pulled up, the specified **blockname** hint will not be used.
+  - Skew hints are not used possibly because:
+    - The plan does not require redistribution.
+    - The columns specified by hints contain distribution keys.
+    - Skew information specified in hints is incorrect or incomplete, for example, no value is specified for join optimization.
+  - Skew optimization is disabled by GUC parameters.
+
+## Optimizer GUC Parameter Hints
+
+### Function
+
+Sets GUC parameters related to query optimization that take effect during the query execution. For details about the application scenarios of hints, see the description of each GUC parameter.
+
+### Syntax
+
+```
+set(param value)
+```
+
+### Parameters
+
+- **param**  indicates the parameter name.
+
+- **value**  indicates the value of a parameter.
+
+- Currently, the following parameters can be set and take effect by using Hint:
+
+  - Boolean
+
+    - **enable_bitmapscan**
+    - **enable_hashagg**
+    - **enable_hashjoin**
+    - **enable_indexscan**
+    - **enable_indexonlyscan**
+    - **enable_material**
+    - **enable_mergejoin**
+    - **enable_nestloop**
+    - **enable_index_nestloop**
+    - **enable_seqscan**
+    - **enable_sort**
+    - **enable_tidscan**
+
+  - Integer
+
+    **query_dop**
+
+  - Floating point
+
+    - **cost_weight_index**
+    - **default_limit_rows**
+    - **seq_page_cost**
+    - **random_page_cost**
+    - **cpu_tuple_cost**
+    - **cpu_index_tuple_cost**
+    - **cpu_operator_cost**
+    - **effective_cache_size**
+
+>![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif)  **NOTE:**
+>
+>- If you set a parameter that is not in the whitelist and the parameter value is invalid or the hint syntax is incorrect, the query execution is not affected. Run  **explain(verbose on)**. An error message is displayed, indicating that hint parsing fails.
+>- The GUC parameter hint takes effect only in the outermost query. That is, the GUC parameter hint in the subquery does not take effect.
+>- The GUC parameter hint in the view definition does not take effect.
+>- In the  **CREATE TABLE ... AS ...**  statement, the outermost GUC parameter hint takes effect.
+
+## Hint for Selecting the Custom Plan or Generic Plan
+
+### Function
+
+For query statements and DML statements executed in PBE mode, the optimizer generates a custom plan or generic plan based on factors such as rules, costs, and parameters. You can use the hint of  **use_cplan**  or  **use_gplan**  to specify the plan to execute.
+
+### Syntax
+
+- To select the custom plan, run the following statement:
+
+  ```
+  use_cplan
+  ```
+
+- To select the generic plan, run the following statement:
+
+  ```
+  use_gplan
+  ```
+
+>![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif)  **NOTE:**
+>
+>- For SQL statements that are executed in non-PBE mode, setting this hint does not affect the execution mode.
+>- This hint has a higher priority than cost-based selection and the  **plan_cache_mode**  parameter. That is, this hint does not take effect for statements for which  **plan_cache_mode**  cannot be forcibly set to specify an execution mode.
+
+### Examples
+
+Forcibly use the custom plan.
+
+```
+set enable_fast_query_shipping = off;
+create table t (a int, b int, c int);
+prepare p as select /*+ use_cplan */ * from t where a = $1;
+explain execute p(1);
+```
+
+In the following plan, the filtering condition is the actual value of the input parameter, that is, the plan is a custom plan.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/hint-based-tuning-7.png)
+
+Forcibly use the generic plan.
+
+```
+deallocate p;
+prepare p as select /*+ use_gplan */ * from t where a = $1;
+explain execute p(1);
+```
+
+In the following plan, the filtering condition is the input parameter to be added, that is, the plan is a custom plan.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/hint-based-tuning-8.png)
+
+## Hint Specifying Not to Expand Subqueries
+
+### Function
+
+When the database optimizes the query logic, some subqueries can be promoted to the upper layer to avoid nested execution. However, for some subqueries that have a low selection rate and can use indexes to filter access pages, nested execution does not cause too much performance deterioration, while after the promotion, the query search scope is expanded, which may cause performance deterioration. In this case, you can use the  **no_expand**  hint for debugging. This hint is not recommended in most cases.
+
+### Syntax
+
+```
+no_expand
+```
+
+### Examples
+
+Normal query execution:
+
+```
+explain select * from t1 where t1.a in (select t2.a from t2);
+```
+
+Plan:
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/hint-based-tuning-9.png)
+
+After  **no_expand**  is added:
+
+```
+explain select * from t1 where t1.a in (select /*+ no_expand*/ t2.a from t2);
+```
+
+Plan:
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/hint-based-tuning-10.png)
+
+## Hint Specifying Not to Use Global Plan Cache
+
+### Function
+
+When global plan cache is enabled, you can use the  **no_gpc**  hint to force a single query statement not to share the plan cache globally. Only the plan cache within the current session lifecycle is retained.
+
+### Syntax
+
+```
+no_gpc
+```
+
+>![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif)  **NOTE:**
+>This parameter takes effect only for statements executed by PBE when  **enable_global_plancache**  is set to  **on**.
+
+### Example
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/hint-based-tuning-11.png)
+
+No result exists in the  **dbe_perf.global_plancache_status**  view, that is, no plan is cached globally.
diff --git a/product/en/docs-mogdb/v3.0/performance-tuning/TPCC-performance-tuning-guide.md b/product/en/docs-mogdb/v3.0/performance-tuning/TPCC-performance-tuning-guide.md
new file mode 100644
index 0000000000000000000000000000000000000000..f4ff60e28f3d1de7e06cecd40dd1059843961908
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/performance-tuning/TPCC-performance-tuning-guide.md
@@ -0,0 +1,780 @@
+---
+title: TPCC Performance Tuning Guide
+summary: TPCC Performance Tuning Guide
+author: Guo Huan
+date: 2021-08-03
+---
+
+# TPCC Performance Tuning Guide
+
+This section introduces the TPCC tesing method of the MogDB database and key system-level tuning depended by the database for reaching its optimal tpmC performance.
+
+<br/>
+
+## Hardware Environment
+
+* Server
+  * The optimal TPC-C result can be achieved by using one four-path KUNPENG servers (256 CPUs, 512 to 1024 GB memory) and one two-path KUNPENG server.
+  * In normal conditions, two two-path KUNPENG servers can be used (128 CPUs, 512 to 1024 GB memory).
+  * Two x86 servers can also be used. But the test guide does not use NUMA optimization.
+
+* Hard disk
+  * It is suggested to use two NVME flash cards on the database client.
+  * Three to four SSDs are used.
+
+* NIC
+  * Hi1822 NICs matched with the KUNPENG server are used.
+  * It is suggested to use gigabit NICs on x86 servers.
+
+<br/>
+
+## Software Environment
+
+* Database: MogDB 2.1.1
+
+* TPCC client: Use TiDB-optimized BenchmarkSQL 5.0 ([https://github.com/pingcap/benchmarksql](https://github.com/pingcap/benchmarksql))
+
+* Dependencies
+
+  | Software | Suggested Version |
+  | :------- | :---------------- |
+  | numactl  | -                 |
+  | JDK      | 1.8.0-242         |
+  | Ant      | 1.10.5            |
+  | htop     | -                 |
+
+<br/>
+
+## Test Procedure
+
+1. Install MogDB. For details, see [Installing MogDB](4-installing-mogdb) for single-instance deployment.
+
+2. Initialize parameter settings and restart the database to make parameters take effect. For details, see [Recommended Parameter Settings](7-recommended-parameter-settings).
+
+3. Download the TPC-C standard test tool BenchmarkSQL 5.0.
+
+   ```bash
+   [root@node151 ~]# git clone -b 5.0-mysql-support-opt-2.1 https://github.com/pingcap/benchmarksql.git
+   Cloning into 'tpcc-mysql'...
+   remote: Enumerating objects: 106, done.
+   remote: Total 106 (delta 0), reused 0 (delta 0), pack-reused 106
+   Receiving objects: 100% (106/106), 64.46 KiB | 225.00 KiB/s, done.
+   Resolving deltas: 100% (30/30), done.
+   ```
+
+4. Download and install the JDK and Ant dependencies.
+
+   ```bash
+   [root@node151 ~]# rpm -ivh ant-1.10.5-6.oe1.noarch.rpm jdk-8u281-linux-aarch64.rpm --force --nodeps
+   warning: ant-1.10.5-6.oe1.noarch.rpm: Header V3 RSA/SHA1 Signature, key ID b25e7f66: NOKEY
+   warning: jdk-8u281-linux-aarch64.rpm: Header V3 RSA/SHA256 Signature, key ID ec551f03: NOKEY
+   Verifying...                          ################################# [100%]
+   Preparing...                          ################################# [100%]
+   Updating / installing...
+      1:jdk1.8-2000:1.8.0_281-fcs        ################################# [ 50%]
+   Unpacking JAR files...
+           tools.jar...
+           rt.jar...
+           jsse.jar...
+           charsets.jar...
+           localedata.jar...
+      2:ant-0:1.10.5-6.oe1               ################################# [100%]
+   ```
+
+5. Configure JAVA environment variables.
+
+   ```bash
+   [root@node151 ~]# tail -3  /root/.bashrc
+   export JAVA_HOME=/usr/java/jdk1.8.0_281-aarch64
+   export PATH=$JAVA_HOME/bin:$PATH
+   export CLASSPATH=.:JAVA_HOME/lib:$BENCHMARKSQLPATH/run/ojdbc7.jar
+   ```
+
+6. Open the BenchmarkSQL directory and run the **ant** command to compile source files.
+
+   After successful compilation, two directories **\build** and **\dist** will generate.
+
+   ```bash
+   [root@node151 benchmarksql-5.0-mysql-support-opt-2.1]# pwd
+   /tmp/benchmarksql-5.0-mysql-support-opt-2.1
+   [root@node151 benchmarksql-5.0-mysql-support-opt-2.1]# ant
+   Buildfile: /tmp/benchmarksql-5.0-mysql-support-opt-2.1/build.xml
+
+   init:
+       [mkdir] Created dir: /tmp/benchmarksql-5.0-mysql-support-opt-2.1/build
+
+   compile:
+       [javac] Compiling 12 source files to /tmp/benchmarksql-5.0-mysql-support-opt-2.1/build
+
+   dist:
+       [mkdir] Created dir: /tmp/benchmarksql-5.0-mysql-support-opt-2.1/dist
+         [jar] Building jar: /tmp/benchmarksql-5.0-mysql-support-opt-2.1/dist/BenchmarkSQL-5.0.jar
+
+   BUILD SUCCESSFUL
+   Total time: 1 second
+   ```
+
+7. Based on your system architecture, download the corresponding JDBC driver ([https://opengauss.org/zh/download.html](https://opengauss.org/zh/download.html)) to the **lib/postgresql** folder in the **BenchmarkSQL** directory, decompress it, and delete the self-contained JDBC driver.
+
+   ```bash
+   [root@node151 postgres]# pwd
+   /tmp/benchmarksql-5.0-mysql-support-opt-2.1/lib/postgres/
+   [root@node151 postgres]# ls
+   openGauss-2.0.0-JDBC.tar.gz  postgresql-9.3-1102.jdbc41.jar
+   [root@node151 postgres]# rm -f postgresql-9.3-1102.jdbc41.jar
+   [root@node151 postgres]# tar -xf openGauss-2.0.0-JDBC.tar.gz
+   [root@node151 postgres]# ls
+   openGauss-2.0.0-JDBC.tar.gz  postgresql.jar
+   ```
+
+8. In the database, create database **tpcc_db** and user **tpcc**.
+
+   ```sql
+   [omm@node151 ~]$ gsql -d postgres -p 26000 -r
+   postgres=# create database tpcc_db;
+   CREATE DATABASE
+   postgres=# \q
+   [omm@node151 ~]$ gsql -d tpcc_db -p 26000 -r
+   tpcc_db=# CREATE USER tpcc WITH PASSWORD "tpcc@123";
+   CREATE ROLE
+   tpcc_db=# GRANT ALL ON schema public TO tpcc;
+   GRANT
+   tpcc_db=# ALTER User tpcc sysadmin;
+   ALTER ROLE
+   ```
+
+9. On the client, open the **run** folder in the **BenchmarkSQL** directory, edit the **benchmarksql** configuration file, and modify test parameters, including database user name, password, IP address, port, and database.
+
+   ```bash
+   [root@node151 db1]# cd /tmp/benchmarksql-5.0-mysql-support-opt-2.1/run
+   [root@node151 run]# vim props.mogdb
+   db=postgres
+   driver=org.postgresql.Driver
+   conn=jdbc:postgresql://172.16.0.176:26000/tpcc_db?prepareThreshold=1&batchMode=on&fetchsize=10&loggerLevel=off #Modify the connection character string, including IP address, port, and database.
+   user=tpcc #User name
+   password=tpcc@123 #Password
+   warehouses=100  #Number of warehouses
+   terminals=300 #Number of terminals
+   runMins=5  #Running time
+   runTxnsPerTerminal=0
+   loadWorkers=100
+   limitTxnsPerMin=0
+   terminalWarehouseFixed=false
+   newOrderWeight=45
+   paymentWeight=43
+   orderStatusWeight=4
+   deliveryWeight=4
+   stockLevelWeight=4
+   ```
+
+10. Initialize data.
+
+    ```bash
+    [root@node151 run]# sh runDatabaseBuild.sh props.mogdb
+
+    # ------------------------------------------------------------
+    # Loading SQL file ./sql.common/tableCreates.sql
+    # ------------------------------------------------------------
+    create table bmsql_config (
+    cfg_name    varchar(30) primary key,
+    cfg_value   varchar(50)
+    );
+
+
+    ......
+
+    # ------------------------------------------------------------
+    # Loading SQL file ./sql.postgres/buildFinish.sql
+    # ------------------------------------------------------------
+    -- ----
+    -- Extra commands to run after the tables are created, loaded,
+    -- indexes built and extra's created.
+    -- PostgreSQL version.
+    -- ----
+    vacuum analyze;
+    ```
+
+11. Modify the path of **funcs.sh** in the **runBenchmark.sh** file to the actual path.
+
+    ```bash
+    [root@node151 run]# vim runBenchmark.sh
+    #!/usr/bin/env bash
+
+    if [ $# -ne 1 ] ; then
+        echo "usage: $(basename $0) PROPS_FILE" >&2
+        exit 2
+    fi
+
+    SEQ_FILE="./.jTPCC_run_seq.dat"
+    if [ ! -f "${SEQ_FILE}" ] ; then
+        echo "0" > "${SEQ_FILE}"
+    fi
+    SEQ=$(expr $(cat "${SEQ_FILE}") + 1) || exit 1
+    echo "${SEQ}" > "${SEQ_FILE}"
+
+    source /tmp/benchmarksql-5.0-mysql-support-opt-2.1/run/funcs.sh $1  #Modify the path to the actual path in which the file is stored.
+
+    setCP || exit 1
+
+    myOPTS="-Dprop=$1 -DrunID=${SEQ}"
+
+    java -cp "$myCP" $myOPTS jTPCC
+    ```
+
+12. Start the test. The tpmC part shows the test result which is stored in **runLog_mmdd-hh24miss.log**.
+
+    ```bash
+    [root@node151 run]# sh runBenchmark.sh props.mogdb| tee runLog_`date +%m%d-%H%M%S`.log
+
+    ...
+
+    15:08:26,663 [Thread-16] INFO   jTPCC : Term-00, Measured tpmC (NewOrders) = 106140.46
+    15:08:26,663 [Thread-16] INFO   jTPCC : Term-00, Measured tpmTOTAL = 235800.39
+    15:08:26,664 [Thread-16] INFO   jTPCC : Term-00, Session Start     = 2021-08-04 15:03:26
+    15:08:26,664 [Thread-16] INFO   jTPCC : Term-00, Session End       = 2021-08-04 15:08:26
+    15:08:26,664 [Thread-16] INFO   jTPCC : Term-00, Transaction Count = 1179449
+    15:08:26,664 [Thread-16] INFO   jTPCC : executeTime[Payment]=29893614
+    15:08:26,664 [Thread-16] INFO   jTPCC : executeTime[Order-Status]=2564424
+    15:08:26,664 [Thread-16] INFO   jTPCC : executeTime[Delivery]=4438389
+    15:08:26,664 [Thread-16] INFO   jTPCC : executeTime[Stock-Level]=4259325
+    15:08:26,664 [Thread-16] INFO   jTPCC : executeTime[New-Order]=48509926
+    ```
+
+    Adjust props.mogdb or use several props files and perform the test several times as required.
+
+13. To prevent generating large volume of data due to multiple tests from affecting performance, clear the data and then start the test.
+
+    ```bash
+    [root@node151 run]# sh runDatabaseDestroy.sh props.mogdb
+    # ------------------------------------------------------------
+    # Loading SQL file ./sql.common/tableDrops.sql
+    # ------------------------------------------------------------
+    drop table bmsql_config;
+    drop table bmsql_new_order;
+    drop table bmsql_order_line;
+    drop table bmsql_oorder;
+    drop table bmsql_history;
+    drop table bmsql_customer;
+    drop table bmsql_stock;
+    drop table bmsql_item;
+    drop table bmsql_district;
+    drop table bmsql_warehouse;
+    drop sequence bmsql_hist_id_seq;
+    ```
+
+    During the tuning, you can execute the build operation once and execute the run operation multiple times. However, in the formal test, you are advised to perform the build, run, and destroy operations in sequence every time.
+
+<br/>
+
+## Tuning
+
+### 1. Host Optimization (KUNPENG Exclusive)
+
+​Adjust BIOS.
+
+- Choose **BIOS** &gt; **Advanced** &gt; **MISC Config**, and set **Support Smmu** to **Disabled**.
+- Choose **BIOS** &gt; **Advanced** &gt; **MISC Config**, and set **CPU Prefetching Configuration** to **Disabled**.
+- Choose **BIOS** &gt; **Advanced** &gt; **Memory Config**, and set **Die Interleaving** to **Disabled**.
+
+### 2. OS Optimization (KUNPENG Exclusive)
+
+- Change **PAGESIZE** of the OS kernel to **64KB** (default value)
+
+- Disable irqbalance.
+
+  ```bash
+  systemctl stop irqbalance
+  ```
+
+- Adjust numa_balance.
+
+  ```bash
+  echo 0 > /proc/sys/kernel/numa_balancing
+  ```
+
+- Adjust the transparent huge page.
+
+  ```bash
+  echo 'never' > /sys/kernel/mm/transparent_hugepage/enabled
+  echo 'never' > /sys/kernel/mm/transparent_hugepage/defrag
+  ```
+
+- Configure the scheduling mechanism of the NVME disk IO queue.
+
+  ```bash
+  echo none > /sys/block/nvmen/queue/scheduler
+  ```
+
+### 3. File System Configuration
+
+- The format is xfs, and the database size is 8 KB.
+
+  ```bash
+  mkfs.xfs -b size=8192 /dev/nvme0n1 -f
+  ```
+
+### 4. Network Configuration
+
+- NIC multi-interrupt queue setting
+
+  Downlaod [IN500_solution_5.1.0.SPC401.zip](https://support.huawei.com/enterprise/zh/software/250968786-ESW2000173161) and install hinicadm.
+
+  ```bash
+  [root@node151 fc]# pwd
+  /root/IN500_solution_5/tools/linux_arm/fc
+  [root@node151 fc]# rpm -ivh hifcadm-2.4.1.0-1.aarch64.rpm
+  Verifying...                          ################################# [100%]
+  Preparing...                          ################################# [100%]
+          package hifcadm-2.4.1.0-1.aarch64 is already installed
+  [root@node151 fc]#
+  ```
+
+- Modify the maximum number of multi-interrupt queues supported by the system.
+
+  ```bash
+  [root@node151 config]# pwd
+  /root/IN500_solution_5/tools/linux_arm/nic/config
+  [root@node151 config]# ./hinicconfig hinic0 -f std_sh_4x25ge_dpdk_cfg_template0.ini
+  [root@node151 config]# reboot
+  [root@node151 config]# ethtool -L enp3s0 combined 48
+  ```
+
+  The tuning value varies depending on the platform and application. For the current platform of 128 cores, the tuning value is 12 on the server client and 48 on the client.
+
+- For interrupt tuning, enable the tso, lro, gro, and gso features.
+
+  ```bash
+  ethtool -K enp3s0 tso on
+  ethtool -K enp3s0 lro on
+  ethtool -K enp3s0 gro on
+  ethtool -K enp3s0 gso on
+  ```
+
+- Confirm and update the NIC firmware.
+
+  ```bash
+  [root@node151 ~]# ethtool -i enp3s0
+  driver: hinic
+  version: 2.3.2.11
+  firmware-version: 2.4.1.0
+  expansion-rom-version:
+  bus-info: 0000:03:00.0
+  supports-statistics: yes
+  supports-test: yes
+  supports-eeprom-access: no
+  supports-register-dump: no
+  supports-priv-flags: no
+  ```
+
+  The NIC firmware version is 2.4.1.0.
+
+- Update the NIC firmware.
+
+  ```bash
+  [root@node151 cfg_data_nic_prd_1h_4x25G]# pwd
+  /root/IN500_solution_5/firmware/update_bin/cfg_data_nic_prd_1h_4x25G
+  [root@node151 cfg_data_nic_prd_1h_4x25G]# hinicadm updatefw -i enp3s0 -f /root/IN500_solution_5/firmware/update_bin/cfg_data_nic_prd_1h_4x25G/Hi1822_nic_prd_1h_4x25G.bin
+  ```
+
+  Restart the server and confirm that the NIC firmware version is updated to 2.4.1.0.
+
+### 5. Core Binding on the Database Server and Client Server
+
+* NUMA binding tuning on KUNPENG servers (128 cores)
+
+  * Install NUMA on the database server and client server.
+
+    ```bash
+    yum install numa -y
+    ```
+
+    Install the NIC driver on the database server and client server. For details, see the **Network Configuration** section.
+
+  * Database server
+
+    ```bash
+    cp `find /opt -name "bind*.sh"|head -1 ` /root
+    sh /root/bind_net_irq.sh 12
+    ```
+
+    Set database parameters:
+
+    ```bash
+    thread_pool_attr = '345,4,(cpubind:1-28,32-60,64-92,96-124)'
+    enable_thread_pool = on
+    ```
+
+    Stop the database.
+    Change the database start command to the following:
+
+    ```bash
+    numactl -C 1-28,32-60,64-92,96-124 mogdb --single_node -D /opt/data/db2/ -p 26000 &
+    ```
+
+  * Client server
+    Copy **/root/bind_net_irq.sh** to the client server.
+
+    ```bash
+    sh /root/bind_net_irq.sh 48
+    ```
+
+    Change the benchmark start command to the following:
+
+    ```bash
+    numactl -C 0-19,32-51,64-83,96-115 sh runBenchmark.sh props.mog
+    ```
+
+* NUMA binding tuning on KUNPENG servers (256 cores)
+
+  * Install NUMA on the database server and client server.
+
+    ```bash
+    yum install numa* -y
+    ```
+
+    Install the NIC driver on the database server and client server. For details, see the **Network Configuration** section.
+
+  * Database server
+
+    ```bash
+    cp `find /opt -name "bind*.sh"|head -1 ` /root
+    sh /root/bind_net_irq.sh 24
+    ```
+
+    Set database parameters:
+
+    ```bash
+    thread_pool_attr = '696,4,(cpubind:1-28,32-60,64-92,96-124,128-156,160-188,192-220,224-252)'
+    enable_thread_pool = on
+    ```
+
+    Stop the database
+    Change the database start command to the following:
+
+    ```bash
+    numactl -C 1-28,32-60,64-92,96-124,128-156,160-188,192-220,224-252 mogdb --single_node -D /opt/data/db2/ -p 26000 &
+    ```
+
+  * Client server
+    Copy **/root/bind_net_irq.sh** to the client server.
+
+    ```bash
+    sh /root/bind_net_irq.sh 48
+    ```
+
+    Change the benchmark start command to the following:
+
+    ```bash
+    numactl -C 0-19,32-51,64-83,96-115 sh runBenchmark.sh props.mog
+    ```
+
+### 6. Database Parameter Tuning (Commonly Used Method)
+
+Modify **postgresql.conf** in PGDATA and restart the database.
+
+```bash
+max_connections = 4096
+allow_concurrent_tuple_update = true
+audit_enabled = off
+cstore_buffers =16MB
+enable_alarm = off
+enable_codegen = false
+enable_data_replicate = off
+full_page_writes = off
+max_files_per_process = 100000
+max_prepared_transactions = 2048
+shared_buffers = 350GB
+use_workload_manager = off
+wal_buffers = 1GB
+work_mem = 1MB
+transaction_isolation = 'read committed'
+default_transaction_isolation = 'read committed'
+synchronous_commit = on
+fsync = on
+maintenance_work_mem = 2GB
+vacuum_cost_limit = 2000
+autovacuum = on
+autovacuum_mode = vacuum
+autovacuum_vacuum_cost_delay =10
+xloginsert_locks = 48
+update_lockwait_timeout =20min
+enable_mergejoin = off
+enable_nestloop = off
+enable_hashjoin = off
+enable_bitmapscan = on
+enable_material = off
+wal_log_hints = off
+log_duration = off
+checkpoint_timeout = 15min
+autovacuum_vacuum_scale_factor = 0.1
+autovacuum_analyze_scale_factor = 0.02
+enable_save_datachanged_timestamp =FALSE
+log_timezone = 'PRC'
+timezone = 'PRC'
+lc_messages = 'C'
+lc_monetary = 'C'
+lc_numeric = 'C'
+lc_time = 'C'
+enable_double_write = on
+enable_incremental_checkpoint = on
+enable_opfusion = on
+numa_distribute_mode = 'all'
+track_activities = off
+enable_instr_track_wait = off
+enable_instr_rt_percentile = off
+track_counts =on
+track_sql_count = off
+enable_instr_cpu_timer = off
+plog_merge_age = 0
+session_timeout = 0
+enable_instance_metric_persistent = off
+enable_logical_io_statistics = off
+enable_user_metric_persistent =off
+enable_xlog_prune = off
+enable_resource_track = off
+instr_unique_sql_count = 0
+enable_beta_opfusion = on
+enable_thread_pool = on
+#0 core is used for binding the walwriter thread to the core.
+enable_partition_opfusion=off
+wal_writer_cpu=0
+xlog_idle_flushes_before_sleep = 500000000
+max_io_capacity = 2GB
+dirty_page_percent_max = 0.1
+candidate_buf_percent_target = 0.7
+bgwriter_delay = 500
+pagewriter_sleep = 30
+checkpoint_segments =10240
+advance_xlog_file_num = 100
+autovacuum_max_workers = 20
+autovacuum_naptime = 5s
+bgwriter_flush_after = 256kB
+data_replicate_buffer_size = 16MB
+enable_stmt_track = off
+remote_read_mode=non_authentication
+wal_level = archive
+hot_standby = off
+hot_standby_feedback = off
+client_min_messages = ERROR
+log_min_messages = FATAL
+enable_asp = off
+enable_bbox_dump = off
+enable_ffic_log = off
+enable_twophase_commit = off
+minimum_pool_size = 200
+wal_keep_segments = 1025
+incremental_checkpoint_timeout = 5min
+max_process_memory = 12GB
+vacuum_cost_limit = 10000
+xloginsert_locks = 8
+wal_writer_delay = 100
+wal_file_init_num = 30
+wal_level=minimal
+max_wal_senders=0
+fsync=off
+synchronous_commit = off
+enable_indexonlyscan=on
+thread_pool_attr = '345,4,(cpubind:1-28,32-60,64-92,96-124)'
+enable_page_lsn_check = off
+enable_double_write = off
+```
+
+### 7. BenchmarkSQL Tuning
+
+- Connection string
+
+  ```bash
+  conn=jdbc:postgresql://10.10.10.40:26000/tpcc?prepareThreshold=1&batchMode=on&fetchsize=10&loggerLevel=off
+  ```
+
+- Modify the file to distribute the data. Adjust FILLFACTOR and partition data disks.
+
+  ```sql
+  [root@node151 ~]# ls benchmarksql-5.0-mysql-support-opt-2.1/run/sql.common/tableCreates.sql
+  benchmarksql-5.0-mysql-support-opt-2.1/run/sql.common/tableCreates.sql
+  [root@node151 sql.common]# cat tableCreates.sql
+  CREATE TABLESPACE example2 relative location 'tablespace2';
+  CREATE TABLESPACE example3 relative location 'tablespace3';
+
+  create table bmsql_config (
+    cfg_name    varchar(30),
+    cfg_value   varchar(50)
+  );
+
+  create table bmsql_warehouse (
+    w_id        integer   not null,
+    w_ytd       decimal(12,2),
+    w_tax       decimal(4,4),
+    w_name      varchar(10),
+    w_street_1  varchar(20),
+    w_street_2  varchar(20),
+    w_city      varchar(20),
+    w_state     char(2),
+    w_zip       char(9)
+  ) WITH (FILLFACTOR=80);
+
+  create table bmsql_district (
+    d_w_id       integer       not null,
+    d_id         integer       not null,
+    d_ytd        decimal(12,2),
+    d_tax        decimal(4,4),
+    d_next_o_id  integer,
+    d_name       varchar(10),
+    d_street_1   varchar(20),
+    d_street_2   varchar(20),
+    d_city       varchar(20),
+    d_state      char(2),
+    d_zip        char(9)
+   ) WITH (FILLFACTOR=80);
+
+  create table bmsql_customer (
+    c_w_id         integer        not null,
+    c_d_id         integer        not null,
+    c_id           integer        not null,
+    c_discount     decimal(4,4),
+    c_credit       char(2),
+    c_last         varchar(16),
+    c_first        varchar(16),
+    c_credit_lim   decimal(12,2),
+    c_balance      decimal(12,2),
+    c_ytd_payment  decimal(12,2),
+    c_payment_cnt  integer,
+    c_delivery_cnt integer,
+    c_street_1     varchar(20),
+    c_street_2     varchar(20),
+    c_city         varchar(20),
+    c_state        char(2),
+    c_zip          char(9),
+    c_phone        char(16),
+    c_since        timestamp,
+    c_middle       char(2),
+    c_data         varchar(500)
+  ) WITH (FILLFACTOR=80) tablespace example2;
+
+  create sequence bmsql_hist_id_seq;
+
+  create table bmsql_history (
+    hist_id  integer,
+    h_c_id   integer,
+    h_c_d_id integer,
+    h_c_w_id integer,
+    h_d_id   integer,
+    h_w_id   integer,
+    h_date   timestamp,
+    h_amount decimal(6,2),
+    h_data   varchar(24)
+  ) WITH (FILLFACTOR=80);
+
+  create table bmsql_new_order (
+    no_w_id  integer   not null,
+    no_d_id  integer   not null,
+    no_o_id  integer   not null
+  ) WITH (FILLFACTOR=80);
+
+  create table bmsql_oorder (
+    o_w_id       integer      not null,
+    o_d_id       integer      not null,
+    o_id         integer      not null,
+    o_c_id       integer,
+    o_carrier_id integer,
+    o_ol_cnt     integer,
+    o_all_local  integer,
+    o_entry_d    timestamp
+  ) WITH (FILLFACTOR=80);
+
+  create table bmsql_order_line (
+    ol_w_id         integer   not null,
+    ol_d_id         integer   not null,
+    ol_o_id         integer   not null,
+    ol_number       integer   not null,
+    ol_i_id         integer   not null,
+    ol_delivery_d   timestamp,
+    ol_amount       decimal(6,2),
+    ol_supply_w_id  integer,
+    ol_quantity     integer,
+    ol_dist_info    char(24)
+  ) WITH (FILLFACTOR=80);
+
+  create table bmsql_item (
+    i_id     integer      not null,
+    i_name   varchar(24),
+    i_price  decimal(5,2),
+    i_data   varchar(50),
+    i_im_id  integer
+  );
+
+  create table bmsql_stock (
+    s_w_id       integer       not null,
+    s_i_id       integer       not null,
+    s_quantity   integer,
+    s_ytd        integer,
+    s_order_cnt  integer,
+    s_remote_cnt integer,
+    s_data       varchar(50),
+    s_dist_01    char(24),
+    s_dist_02    char(24),
+    s_dist_03    char(24),
+    s_dist_04    char(24),
+    s_dist_05    char(24),
+    s_dist_06    char(24),
+    s_dist_07    char(24),
+    s_dist_08    char(24),
+    s_dist_09    char(24),
+    s_dist_10    char(24)
+  ) WITH (FILLFACTOR=80) tablespace example3;
+  ```
+
+### 8. Database File Location Tuning (Commonly Used Method)
+
+Place the **primary**, **xlog**, **example2**, and **example3** directories in multiple underlying disks to avoid IO bottleneck.
+If there are only two high-performance disks, preferably move the **xlog** directory. If there are three high-performance disks, move the **xlog** and **example2** directories.
+The example is as follows:
+
+```bash
+PGDATA=/opt/data/mogdb
+cd $PGDATA
+mv pg_xlog /tpccdir1
+ln -s /tpccdir1/pg_xlog .
+cd pg_location
+mv tablespace2 /tpccdir2
+ln -s /tpccdir2/tablespace2 .
+mv tablespace3 /tpccdir3
+ln -s /tpccdir3/tablespace3 .
+```
+
+### 9. Observation of System Resource Tools
+
+- htop is used to observe the CPU usage. For the ARM platform, the compilation needs to be performed from source code.
+
+  By using htop to monitor the CPU usage on the database server and client server, it is found that the CPU usage of each service is very high, reaching more than 90% under the optimal performance test. If the CPU usage of any service does not reach the standard, the core-binding mode may be incorrect or other problem may occur. It needs to be located and modified.
+
+- **iostat** is used to check the system IO usage.
+
+- **sar** is used to check the network usage.
+
+- **nmon** is used to monitor the overall system resources.
+
+**Screenshots of part of data**
+
+- htop result of the database server
+
+  ![htop.png](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/TPCC-performance-tuning-guide-1.png)
+
+- htop result of the client server
+
+  ![客户端_htop.png](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/TPCC-performance-tuning-guide-2.png)
+
+- **iostat** is used to check the system IO usage.
+
+  ![iostat.png](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/TPCC-performance-tuning-guide-3.png)
+
+- **sar** is used to check the network usage.
+
+  ![sar.png](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/TPCC-performance-tuning-guide-4.png)
+
+<br/>
+
+## Ideal Results
+
+4-path KUNPENG server with 256 CPUs, 1000 warehouses, and 500 terminals: 250W tpmC<br/>
+2-path KUNPENG server with 100 warehouses and 100 terminals: 90W tpmC<br/>2-path KUNPENG server with 100 warehouses and 300 terminals: 140W tpmC
diff --git a/product/en/docs-mogdb/v3.0/performance-tuning/wdr-snapshot-schema.md b/product/en/docs-mogdb/v3.0/performance-tuning/wdr-snapshot-schema.md
new file mode 100644
index 0000000000000000000000000000000000000000..9546295fc6456da9d579bcc2b276a25215167157
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/performance-tuning/wdr-snapshot-schema.md
@@ -0,0 +1,179 @@
+---
+title: WDR Snapshot Schema
+summary: WDR Snapshot Schema
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# WDR Snapshot Schema
+
+After the WDR snapshot function is enabled (**enable_wdr_snapshot** is set to **on**), schema **snapshot** is created in user tablespace **pg_default** in database **postgres** to flush WDR snapshot data. By default, the initial user or the **monadmin** user can access the snapshot schema.
+
+You can set the parameter **wdr_snapshot_retention_days** to automatically manage the snapshot lifecycle.
+
+## Original Information Table of WDR Snapshots
+
+### SNAPSHOT.SNAPSHOT
+
+**SNAPSHOT** records the index information, start time, and end time of WDR snapshots stored in the current system. The results can only be queried in the system library, but not in the user library.
+
+**Table 1** SNAPSHOT attributes
+
+| Name        | Type      | Description                  | Example                       |
+| :---------- | :-------- | :--------------------------- | :---------------------------- |
+| snapshot_id | bigint    | WDR snapshot ID              | 1                             |
+| start_ts    | timestamp | Start time of a WDR snapshot | 2019-12-28 17:11:27.423742+08 |
+| end_ts      | timestamp | End time of a WDR snapshot   | 2019-12-28 17:11:43.67726+08  |
+
+### SNAPSHOT.TABLES_SNAP_TIMESTAMP
+
+**TABLES_SNAP_TIMESTAMP** records the start time and end time of data collection, as well as corresponding databases, and table objects for all stored WDR snapshots.
+
+**Table 2** TABLES_SNAP_TIMESTAMP attributes
+
+| Name        | Type      | Description                              | Example                       |
+| :---------- | :-------- | :--------------------------------------- | :---------------------------- |
+| snapshot_id | bigint    | WDR snapshot ID                          | 1                             |
+| db_name     | text      | Database corresponding to a WDR snapshot | tpcc1000                      |
+| tablename   | text      | Table corresponding to a WDR snapshot    | snap_xc_statio_all_indexes    |
+| start_ts    | timestamp | Start time of a WDR snapshot             | 2019-12-28 17:11:27.425849+08 |
+| end_ts      | timestamp | End time of a WDR snapshot               | 2019-12-28 17:11:27.707398+08 |
+
+### SNAP_SEQ
+
+**SNAP_SEQ** is an ascending sequence, which provides IDs for WDR snapshots.
+
+## WDR Snapshot Data Table
+
+The naming rule of a WDR snapshot data table is **snap_{Source data table}**.
+
+WDR snapshot data tables come from all views in **DBE_PERF** Schema.
+
+## Performance Report Generated Based on WDR Snapshot
+
+A performance report is generated by summarizing and collecting statistics based on WDR snapshot data tables.
+
+**Prerequisites**
+
+A report can be generated after the WDR snapshot function is enabled (that is, **enable_wdr_snapshot** is set to **on**) and the number of snapshots is greater than or equal to 2.
+
+**Procedure**
+
+1. Run the following command to connect the postgres database.
+
+   ```bash
+   gsql -d postgres -p <Port number> -r
+   ```
+
+2. Run the following command to query the generated snapshot and obtain **snapshot_id**:
+
+   ```sql
+   select * from snapshot.snapshot;
+   ```
+
+3. (Optional) Run the following command on CCN to manually create a snapshot. If only one snapshot exists in the database or to view the monitoring data of the database in the current period, manually create a snapshot.
+
+   ```sql
+   select create_wdr_snapshot();
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **Note:**
+   > Run the **cm_ctl query -Cdvi** command. The command output returned in the **Central Coordinator State** part is the CCN information.
+
+4. Perform the following steps to generate a performance report:
+
+   a. Run the following command to generate a formatted performance report file:
+
+   ```bash
+   \a \t \o Server file path
+   ```
+
+   The parameters in the preceding command are described as follows:
+
+   - **\\a**: switches the unaligned mode.
+   - **\\t**: switches the information and row count footer of the output column name.
+   - **\\o**: specifies that all the query results are sent to the server file.
+   - *Server file path*: indicates the path for storing the generated performance report file. The user must have the read and write permissions on the path.
+
+   b. Run the following command to write the queried information to the performance report:
+
+   ```sql
+   select generate_wdr_report(begin_snap_id bigint, end_snap_id bigint, report_type cstring, report_scope cstring, node_name cstring);
+   ```
+
+   The description of the parameters in the preceding command is as follows:
+
+   **Table 3** Parameters of the generate_wdr_report function
+
+   | Parameter                      | Description                  | Value Range                        |
+   | :----------------------------- | :--------------------------- | :--------------------------------- |
+   | begin_snap_id | ID of a snapshot when a query starts, which is specified by **snapshot_id** in the **snapshot.snaoshot** table. | -                                                            |
+   | end_snap_id   | ID of a snapshot when a query ends. By default, the value of **end_snap_id** is greater than that of **begin_snap_id table**. | -                                                            |
+   | report_type   | Type of the generated report. The value can be **summary**, **detail**, or **all**. | **summary**: Summary data<br />**detail**: Detailed data<br />**all**: summary data and detailed data |
+   | report_scope  | Range of the generated report. The value can be **cluster** or **node**. | **cluster**: database-level information<br />**node**: node-level information |
+   | node_name     | When **report\_scope** is set to **node**, set this parameter to the name of the corresponding node. (You can run the `select * from pg_node_env;` command to query the node name.)If **report\_scope** is set to **cluster**, this parameter can be omitted, left blank, empty or set to **NULL**. | **node**: a node name in MogDB<br />**cluster**: This value is omitted, left blank,empty or set to **NULL**. |
+
+   c. Run the following commands to disable the output options and format the output:
+
+   ```bash
+   \o \a \t
+   ```
+
+5. View the WDR report as required.
+
+**Table 4** WDR report
+
+| Item                                                  | Description                                                  |
+| :---------------------------------------------------- | :----------------------------------------------------------- |
+| Database Stat (database scope)                        | Performance statistics information in database dimensions, including transaction, write/read, row activity, write conflict, deadlock, and so on |
+| Load Profile (database scope)                         | Performance statistics information in database dimensions, including CPU time, DB time, logical read/physical read, IO performance, login/logout, workload intensity, and workload performance, and so on |
+| Instance Efficiency Percentages (database/node scope) | Buffer Hit (buffer hit rate), Effective CPU (CPU usage), WalWrite NoWait (success rate of obtaining Wal Buffer), Soft Parse (soft parsing rate), and Non-parse CPU (percentage of CPU time spent in non-parsing activities) at the database or node level |
+| Top 10 Events by Total Wait Time (node scope)         | Event that consumes the most time                            |
+| Wait Classes by Total Wait Time (node scope)          | Class of wait events that consume the most time              |
+| Host CPU (node scope)                                 | CPU usage of the host                                        |
+| Memory Statistics (node scope)                        | memory statistics in the kernel                              |
+| Object stats (node scope)                             | Performance statistics information in the table and index dimensions |
+| Database Configuration (node scope)                   | Node configuration                                           |
+| SQL Statistics (node scope)                           | Performance statistics of a SQL statement in all dimensions, including end-to-end time, row activity, cache hit rate, CPU usage, time consumption segmentation |
+| SQL Detail (node scope)                               | SQL statement details                                        |
+
+**Examples**
+
+```sql
+-- To query enable_wdr_snapshot, set this parameter to on.
+mogdb=# show enable_wdr_snapshot;
+ enable_wdr_snapshot
+---------------------
+ on
+(1 row)
+
+-- Query the snapshots that have been generated.
+mogdb=# select * from snapshot.snapshot;
+ snapshot_id |           start_ts            |            end_ts
+-------------+-------------------------------+-------------------------------
+           1 | 2020-09-07 10:20:36.763244+08 | 2020-09-07 10:20:42.166511+08
+           2 | 2020-09-07 10:21:13.416352+08 | 2020-09-07 10:21:19.470911+08
+(2 rows)
+
+-- Generate the formatted performance report wdrTestNode.html.
+mogdb=# \a \t \o /home/om/wdrTestNode.html
+Output format is unaligned.
+Showing only tuples.
+
+-- Write data into the performance report wdrTestNode.html.
+mogdb=# select generate_wdr_report(1, 2, 'all', 'node', 'dn');
+
+-- Close the performance report wdrTestNode.html.
+mogdb=# \o
+
+-- Generate the formatted performance report wdrTestCluster.html.
+mogdb=# \o /home/om/wdrTestCluster.html
+
+-- Write data into the performance report wdrTestCluster.html.
+mogdb=# select generate_wdr_report(1, 2, 'all', 'cluster', '');
+
+-- Close the performance report wdrTestCluster.html.
+mogdb=# \o \a \t
+Output format is aligned.
+Tuples only is off.
+```
diff --git a/product/en/docs-mogdb/v3.0/quick-start/container-based-installation.md b/product/en/docs-mogdb/v3.0/quick-start/container-based-installation.md
new file mode 100644
index 0000000000000000000000000000000000000000..d545e602716e3a121ad1e6e9b2bf8fb85a784419
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/quick-start/container-based-installation.md
@@ -0,0 +1,208 @@
+---
+title: Container-based MogDB Installation
+summary: Container-based MogDB Installation
+author: Guo Huan
+date: 2021-04-01
+---
+
+# Container-based MogDB Installation
+
+This document introduces the installation of single instance and primary/standby instances in a MogDB docker container. MogDB container does not support the MogHA and OM tools, and currently supports at most one primary node and eight standby nodes. MogDB 2.1 container version supports the latest version of compat-tools and plugin functions.<br/>
+
+In consideration of narrowing the container image size for quick download and deployment, it is recommended that the x86 and ARM-based OSs depended by MogDB running in a docker container will be Ubuntu and Debian since MogDB 2.0. <br/>
+
+A MogDB container based on the x86-64 architecture runs in Ubuntu 18.04.<br/>
+
+A MogDB container based on the ARM64 architecture runs in Debian 10.
+
+<br/>
+
+## Docker-based Deployment
+
+### Before You Start
+
+The installation of a MogDB container is independent of the host OS. All OSs that can run a container enginer are supported, such as Linux, Windows, and macOS.
+
+Before installing the MogDB container, you need to prepare the container runnning environment, such as Docker.
+
+Docker is an open source application container engine based on Go and compliant with the Apache 2.0 protocol. Docker allows developers to package their applications and dependency packages into a lightweight, portable container that can then be distributed to any popular Linux machine and virtualized.
+
+Docker Desktop download address: <https://www.docker.com/products/docker-desktop>
+
+<br/>
+
+### Installation Procedures
+
+1. Run Docker.
+
+2. Run the following command to obtain the latest version of the MogDB image file.
+
+   ```bash
+   docker pull swr.cn-north-4.myhuaweicloud.com/mogdb/mogdb:2.1.1
+   ```
+   
+   > Note: MogDB image supports x86 and ARM architectures, and the system will automatically download the corresponding image according to the server architecture that initiates the command, no need to specify manually.
+
+3. Run the following command to create a running directory for MogDB, using **mogdb** as an example below.
+
+   ```bash
+   mkdir /mogdb
+   ```
+
+4. Continue with the following command to create a new container, and name it **mogdb** to run a MogDB instance:
+
+   ```bash
+   docker run --name mogdb --privileged=true -d -e GS_PASSWORD=Secretpassword@123  -v /mogdb:/var/lib/mogdb  -p 15432:5432  swr.cn-north-4.myhuaweicloud.com/mogdb/mogdb:2.1.1
+   ```
+
+   For Windows OS:
+   - If Docker uses Hyper-V as the engine, run the following commands in sequence to create the logical object **mogdata** of the volume in Hyper-V, and then create the container:
+
+      ```bash
+      docker volume create mogdata
+
+      docker run --name mogdb --privileged=true -d -e GS_PASSWORD=Secretpassword@123 -v mogdata:/var/lib/mogdb -p 15453:5432  swr.cn-north-4.myhuaweicloud.com/mogdb/mogdb:2.1.1
+      ```
+
+   - If Docker uses WSL 2 as the engine, run the following command to create the container:
+
+      ```bash
+      docker run --name mogdb --privileged=true -d -e GS_PASSWORD=Secretpassword@123 -v C:\mogdb:/var/lib/mogdb -p 15432:5432  swr.cn-north-4.myhuaweicloud.com/mogdb/mogdb:2.1.1
+      ```
+
+   > Note:
+   >
+   > - MogDB uses port 5432 in the container for listening by default. If you want to access the database from outside the container, you need to specify the `-p` parameter in `docker run` command. For example, the above command will allow access to the container database using port 15432.
+   > - Once the container is deleted, all the data and configuration in the container will be lost. After re-running a container from the image, all the data is presented in the initialized state. So for the database container, in order to prevent the loss of data due to the demise of the container or corruption, the operation of persistent storage data is required. This is achieved by specifying the `-v` parameter in `docker run` command. For example, the above command will specify that all data files of MogDB will be stored under **/mogdb** of the host. In addition, If you use Podman, there will be a target path check. Therefore you need to create the target path in advance (step 4).
+
+5. Execute bash in the **mogdb** container via the **exec** command:
+
+   ```bash
+   docker exec -it mogdb bash
+   ```
+
+   Now, the installation of MogDB in the container is complete.
+
+<br/>
+
+### Using MogDB
+
+After the installation is complete and enter the container, switch to omm user by running "su - omm", you can access the database via gsql and use MogDB properly.
+
+```bash
+root@384ac97543bd:/# su - omm
+omm@384ac97543bd:~$ gsql -d postgres
+gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+Non-SSL connection (SSL connection is recommended when requiring high-security)
+Type "help" for help.
+
+postgres=#
+```
+
+<br/>
+
+### Environment Variables
+
+To flexibly use an MogDB image, you can set additional parameters. In the future, more control parameters will be added. The current version supports the setting of the following variables:
+
+**GS_PASSWORD**
+
+This parameter is mandatory when the MogDB image is used. The value cannot be empty or undefined. This parameter specifies the passwords of superuser **omm** and test user **mogdb** of the MogDB database. During the MogDB installation, the superuser **omm** is created by default. This username cannot be changed. The test user **mogdb** is created in  **entrypoint.sh**.
+
+The local trust mechanism is configured for the MogDB image. Therefore, no password is required for connecting to the database in the container. However, if you want to connect to the database from other hosts or containers, you need to enter the password.
+
+The password must contain at least eight characters, including uppercase letters, lowercase letters, digits, and special characters ( \# ? ! @ $ % ^ & * \- ). ** ! $ &** must be escaped using a backslash (\\).
+
+**GS_NODENAME**
+
+Specifies the database node name. The default value is  **mogdb**.
+
+**GS_USERNAME**
+
+Specifies the username for connecting to the database. The default value is  **mogdb**.
+
+**GS_PORT**
+
+Specifies the database port. The default value is  **5432**.
+
+<br/>
+
+## Kubernetes-based Deployment
+
+MogDB 2.1 and later supports Kubernetes-based deployment.
+
+- x86
+  
+  ```
+  $ kubectl apply -f https://gitee.com/enmotech/enmotech-docker-mogdb/raw/master/2.1.1/k8s_amd.yaml
+  pod/mogdb created
+  ```
+
+- arm
+
+  ```
+  $ kubectl apply -f https://gitee.com/enmotech/enmotech-docker-mogdb/raw/master/2.1.1/k8s_arm.yaml
+  pod/mogdb created
+  ```
+
+- Kubernetes connect the pod
+
+  Connect to MogDB through the gsql command in the pod.
+
+  ```
+  $ kubectl exec -it mogdb -- bash
+  root@mogdb:/# su - omm
+  omm@mogdb:~$ gsql -d postgres
+  gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+  Non-SSL connection (SSL connection is recommended when requiring high-security)
+  Type "help" for help.
+  
+  MogDB=#
+  ```
+
+<br/>
+
+## Sample dataset: Mogila
+
+MogDB Container Edition has a built-in sample dataset mogila. Mogila is a database representing a DVD rental store, containing information about films (like title, category, actresses), rental stores (like address, staff members, customers) and rentals, where a customer rents a film from a store through its staff. After installing MogDB Container Edition, you can use the mogila database for various functional tests.
+
+After the installation is complete and enter the container, switch to omm user by running `su - omm`, and execute `gsql -d mogila` to access the mogila database.
+
+```sql
+root@07456ed8f523:/# su - omm
+omm@07456ed8f523:~$ gsql -d mogila
+gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+Non-SSL connection (SSL connection is recommended when requiring high-security)
+Type "help" for help.
+
+MogDB=#\dt
+                             List of relations
+ Schema |     Name      | Type  | Owner |             Storage
+--------+---------------+-------+-------+----------------------------------
+ public | actor         | table | mogdb | {orientation=row,compression=no}
+ public | address       | table | mogdb | {orientation=row,compression=no}
+ public | category      | table | mogdb | {orientation=row,compression=no}
+ public | city          | table | mogdb | {orientation=row,compression=no}
+ public | country       | table | mogdb | {orientation=row,compression=no}
+ public | customer      | table | mogdb | {orientation=row,compression=no}
+ public | film          | table | mogdb | {orientation=row,compression=no}
+ public | film_actor    | table | mogdb | {orientation=row,compression=no}
+ public | film_category | table | mogdb | {orientation=row,compression=no}
+ public | inventory     | table | mogdb | {orientation=row,compression=no}
+ public | language      | table | mogdb | {orientation=row,compression=no}
+ public | payment       | table | mogdb | {orientation=row,compression=no}
+ public | rental        | table | mogdb | {orientation=row,compression=no}
+ public | staff         | table | mogdb | {orientation=row,compression=no}
+ public | store         | table | mogdb | {orientation=row,compression=no}
+(15 rows)
+
+MogDB=#
+```
+
+For detailed introduction and query example of mogila sample dataset, please refer to [Using Sample Dataset Mogila](mogila).
+
+<br/>
+
+## What's Next
+
+MogDB container does not support MogHA and OM tools. It is only used for testing, and currently supports at most one primary node and eight standby nodes. MogDB Enterprise Edition includes MogHA component. The basic functions of the MogDB container and Enterprise Edition are identical. It is recommended that MogDB Enterprise Edition is used in the production environment.
diff --git a/product/en/docs-mogdb/v3.0/quick-start/installation-on-a-single-node.md b/product/en/docs-mogdb/v3.0/quick-start/installation-on-a-single-node.md
new file mode 100644
index 0000000000000000000000000000000000000000..a5d6003645987bc7fc7b3d395d7e842e1fabd757
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/quick-start/installation-on-a-single-node.md
@@ -0,0 +1,130 @@
+---
+title: Installation on a Single Node
+summary: Installation on a Single Node
+author: Zhang Cuiping
+date: 2021-04-2
+---
+
+# Installation on a Single Node
+
+This article introduces the installation process of MogDB Simplified version, which is mainly for universities and personal test environments, and is simpler and faster than the enterprise installation process. The package does not contain OM tools, and the script can be used to achieve one-click installation and deployment.
+
+<br/>
+
+## Preparing the Software and Hardware Installation Environment
+
+**Software Environment:** Visit [MogDB download page](https://www.mogdb.io/en/downloads/mogdb/) to download the installation package according to your OS and CPU architecture. The `MogDB-x.x.x-openEuler-64bit.tar.bz2` obtained after unpacking the standard installation package is the simplified installation package.
+
+**Hardware Environment:** The minimum configuration for individual developers is 2 cores/4G, and the recommended configuration is 4 cores/8G.
+
+> Note:
+>
+> In order to accommodate small memory machines, the simplified version sets some important memory parameters lower during deployment, such as `shared_buffers = 32MB`, `cstore_buffers = 512MB`. In addition, the database character set of the simplified version is changed from the original default `SQL_ACSII` character set to `en_US.UTF-8`, and the initial user password is not forced to be changed, i.e. `modify_initial_password = false`.
+
+<br/>
+
+## Running Environment Configuration
+
+1. Disable the firewall.
+
+   ```
+   systemctl disable firewalld.service
+   systemctl stop firewalld.service
+   setenforce=0
+   sed -i '/^SELINUX=/c'SELINUX=disabled /etc/selinux/config
+   ```
+
+2. Install dependency packages.
+
+   ```
+   yum install libaio-devel flex bison ncurses-devel glibc-devel patch redhat-lsb-core readline-devel -y
+   ```
+
+3. Set the time zone and time.
+
+   ```
+   rm -fr /etc/localtime
+   ln -s /usr/share/zoneinfo/Asia/Shanghai /etc/localtime
+   ll /etc/localtime
+   ```
+
+4. For openEuler OS, you need to disable RemoveIPC. For CentOS, skip this step.
+
+   ```
+   # Modify the value of "RemoveIPC" in the /etc/systemd/logind.conf file to "no".
+   vim  /etc/systemd/logind.conf
+   RemoveIPC=no
+   
+   # Modify the value of "RemoveIPC" in the /usr/lib/systemd/system/systemd-logind.service file to "no".
+   vim /usr/lib/systemd/system/systemd-logind.service
+   RemoveIPC=no
+   
+   # Reload the configuration parameters.
+   systemctl daemon-reload
+   systemctl restart systemd-logind
+   
+   # Check if the changes take effect.
+   loginctl show-session | grep RemoveIPC
+   systemctl show systemd-logind | grep RemoveIPC
+   ```
+
+<br/>
+
+## Installation Procedure
+
+1. Create directory, user, group, and authorize them.
+
+   ```
+   groupadd dbgrp -g 2000
+   useradd omm -g 2000 -u 2000
+   mkdir -p /opt/software/mogdb
+   chown -R omm:dbgrp /opt/software/mogdb
+   ```
+
+2. Decompress the MogDB package to the installation directory.
+
+   ```
+   su - omm
+   cd /opt/software/mogdb/
+   tar -jxf MogDB-x.x.x-openEuler-64bit.tar.bz2 -C /opt/software/mogdb/
+   ```
+
+3. Go to the **simpleInstall** directory.
+
+   ```
+   cd /opt/software/mogdb/simpleInstall
+   ```
+
+4. Run the **install.sh -w** command to install MogDB.
+
+   ```
+   sh install.sh  -w xxxx
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+   >
+   > - **-w**: initializes the database password (specified by **gs_initdb**). This parameter is mandatory for security purposes.
+   > - **-p**: specifies the MogDB port number. If the port number is not specified, the default value **5432** is used.
+   > - **-h|-help**: displays usage instructions.
+   > - After the installation, the database name is **sgnode**.
+   > - The installation path of the database directory is **/opt/software/mogdb/data/single_node**, in which **/opt/software/mogdb** is the decompression path and **data/single_node** is the newly created database node directory.
+
+<br/>
+
+## Check and Use
+
+```
+## Configure PATH
+echo "PATH=/opt/software/mogdb/bin:\$PATH" >> /home/omm/.bash_profile
+source ~/.bash_profile
+-bash: ulimit: open files: cannot modify limit: Operation not permitted
+(The default setting fd available size exceeds the system setting, you can ignore the setting)
+
+## Login to MogDB
+gsql -d postgres -p 5432 -r
+gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+Non-SSL connection (SSL connection is recommended when requiring high-security)
+Type "help" for help.
+
+mogdb=#
+```
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-cli-to-access-mogdb/gsql.md b/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-cli-to-access-mogdb/gsql.md
new file mode 100644
index 0000000000000000000000000000000000000000..23403a5547d573458fdae3cdc4b2ea14f9237a17
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-cli-to-access-mogdb/gsql.md
@@ -0,0 +1,216 @@
+---
+title: gsql
+summary: gsql
+author: Guo Huan
+date: 2021-12-1
+---
+
+# gsql
+
+**gsql** is a MogDB-provided database connection tool running in the CLI. **gsql** provides basic and advanced functions of databases to facilitate user operations.
+
+<br/>
+
+## Confirming Connection Information
+
+You can use a client tool to connect a database through the primary node of the database. Before the connection, obtain the IP address of the primary node of the database and the port number of the server where the primary node of the database is deployed.
+
+1. Log in to the primary node of the database as the OS user **omm**.
+
+2. Run the **gs_om -t status --detail** command to query instances in the MogDB cluster.
+
+   ```bash
+   gs_om -t status --detail
+
+   [  Datanode State   ]
+
+   node                 node_ip         instance                state
+   ---------------------------------------------------------------------------------
+   1  mogdb-kernel-0005 172.16.0.176    6001 /mogdb/data/db1 P Primary Normal
+   ```
+
+   For example, the server IP address where the primary node of the database is deployed is 172.16.0.176. The data path of the primary node of the database is **/mogdb/data/db1**.
+
+3. Confirm the port number of the primary node of the database.
+
+   View the port number in the **postgresql.conf** file in the data path of the primary database node obtained in step 2. The command is as follows:
+
+   ```bash
+   cat /mogdb/data/db1/postgresql.conf | grep port
+   
+   port = 26000    # (change requires restart)
+   #comm_sctp_port = 1024   # Assigned by installation (change requires restart)
+   #comm_control_port = 10001  # Assigned by installation (change requires restart)
+         # supported by the operating system:
+         # e.g. 'localhost=10.145.130.2 localport=12211 remotehost=10.145.130.3 remoteport=12212, localhost=10.145.133.2 localport=12213 remotehost=10.145.133.3 remoteport=12214'
+         # e.g. 'localhost=10.145.130.2 localport=12311 remotehost=10.145.130.4 remoteport=12312, localhost=10.145.133.2 localport=12313 remotehost=10.145.133.4 remoteport=12314'
+         #   %r = remote host and port
+   alarm_report_interval = 10
+   support_extended_features=true
+   ```
+
+   **26000** in the first line is the port number of the primary database node.
+
+<br/>
+
+### Installing the gsql Client
+
+On the host, upload the client tool package and configure environment variables for the **gsql** client.
+
+1. Log in to the host where the client resides as any user.
+
+2. Run the following command to create the **/opt/mogdb/tools** directory:
+
+   ```bash
+   mkdir /opt/mogdb/tools
+   ```
+
+3. Obtain the file **MogDB-x.x.x-openEuler-64bit-tools.tar.gz** from the software installation package and upload it to the **/opt/mogdb/tools** directory.
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+   >
+   > - The software package is located where you put it before installation. Set it based on site requirements.
+   > - The tool package name may vary in different OSs. Select the tool package suitable for your OS.
+
+4. Run the following commands to decompress the package:
+
+   ```bash
+   cd /opt/mogdb/tools
+   tar -zxvf MogDB-x.x.x-openEuler-64bit-tools.tar.gz
+   ```
+
+5. Set environment variables.
+
+   Run the following command to open the **~/.bashrc** file:
+
+   ```bash
+   vi ~/.bashrc
+   ```
+
+   Enter the following content and run **:wq!** to save and exit.
+
+   ```bash
+   export PATH=/opt/mogdb/tools/bin:$PATH
+   export LD_LIBRARY_PATH=/opt/mogdb/tools/lib:$LD_LIBRARY_PATH
+   ```
+
+6. Run the following command to make the environment variables take effect:
+
+   ```bash
+   source ~/.bashrc
+   ```
+
+<br/>
+
+## Connecting to a Database Using gsql
+
+<br/>
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - By default, if a client is idle state after connecting to a database, the client automatically disconnects from the database in the duration specified by **session_timeout**. To disable the timeout setting, set **session_timeout** to **0**.
+
+<br/>
+
+### Connecting to a Database Locally
+
+1. Log in as the OS user **omm** to the primary node of the database.
+
+2. Connect to a database.
+
+   After the database is installed, a database named **postgres** is generated by default. When connecting to a database for the first time, you can connect to this database.
+
+   Run the following command to connect to the **postgres** database:
+
+   ```bash
+   gsql -d postgres -p 26000
+   ```
+
+   **postgres** is the name of the database to be connected, and **26000** is the port number of the database primary node. Replace the values as required.
+
+   If information similar to the following is displayed, the connection succeeds:
+
+   ```sql
+   gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+   Non-SSL connection (SSL connection is recommended when requiring high-security)
+   Type "help" for help.
+
+   postgres=#
+   ```
+
+   User **omm** is the administrator, and **postgres=#** is displayed. If you log in to and connect to the database as a common user, **postgres=&gt;** is displayed.
+
+   **Non-SSL connection** indicates that the database is not connected in SSL mode. If high security is required, connect to the database in SSL mode.
+
+3. Exit the database.
+
+   ```sql
+   postgres=# \q
+   ```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - When connecting to the database locally as user **omm**, no password is required. This is due to the default setting in the **pg_hba.conf** file that allows the local machine to connect in the **trust** way.
+> - For details about the client authentication methods, see the [Client Access Authentication](1-client-access-authentication) chapter.
+
+<br/>
+
+## Connecting to a Database Remotely
+
+<br/>
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - Due to security restrictions, you can not remotely connect to the database as user **omm**.
+
+<br/>
+
+### Configuring a Whitelist Using gs_guc (Update pg_hba.conf)
+
+1. Log in as the OS user **omm** to the primary node of the database.
+
+2. Configure the client authentication mode and enable the client to connect to the host as user **jack**. User **omm** cannot be used for remote connection.
+
+   Assume you are to allow the client whose IP address is **172.16.0.245** to access the current host.
+
+   ```sql
+   gs_guc set -N all -I all -h "host all jack 172.16.0.245/24 sha256"
+   ```
+
+   **NOTICE:**
+
+   - Before using user **jack**, connect to the database locally and run the following command in the database to create user **jack**:
+
+     ```sql
+     postgres=# CREATE USER jack PASSWORD 'Test@123';
+     ```
+
+   - **-N all**  indicates all hosts in MogDB.
+
+   - **-I all**  indicates all instances on the host.
+
+   - **-h**  specifies statements that need to be added in the  **pg_hba.conf**  file.
+
+   - **all**  indicates that a client can connect to any database.
+
+   - **jack**  indicates the user that accesses the database.
+
+   - **172.16.0.245/24**  indicates that only the client whose IP address is  **172.16.0.245**  can connect to the host. The specified IP address must be different from those used in MogDB.  **24**  indicates that there are 24 bits whose value is 1 in the subnet mask. That is, the subnet mask is 255.255.255.0.
+
+   - **sha256**  indicates that the password of user  **jack**  is encrypted using the SHA-256 algorithm.
+
+   This command adds a rule to the  **pg_hba.conf**  file corresponds to the primary node of the database. The rule is used to authenticate clients that access primary node.
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+   >
+   > For details about the client authentication methods, see the [Client Access Authentication](1-client-access-authentication) chapter.
+
+3. Connect to a database.
+
+   After the database is installed, a database named **postgres** is generated by default. When connecting to a database for the first time, you can connect to this database.
+
+   ```bash
+   gsql -d postgres -h 172.16.0.176 -U jack -p 26000 -W Test@123
+   ```
+
+   **postgres** is the name of the database, **172.16.0.176** is the IP address of the server where the primary node of the database resides, **jack** is the user of the database, **26000** is the port number of the CN, and **Test@123** is the password of user **jack**.
diff --git a/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-cli-to-access-mogdb/pgcli.md b/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-cli-to-access-mogdb/pgcli.md
new file mode 100644
index 0000000000000000000000000000000000000000..d0277badaf4cf26e716a716fa3383def8fbbf5fd
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-cli-to-access-mogdb/pgcli.md
@@ -0,0 +1,85 @@
+---
+title: pgcli
+summary: pgcli
+author: Guo Huan
+date: 2022-02-16
+---
+
+# pgcli
+
+pgcli is a command line interface for Postgres with auto-completion and syntax highlighting, which is also suitable for MogDB.
+
+Source: [https://github.com/dbcli/pgcli](https://github.com/dbcli/pgcli)
+
+<br/>
+
+## Install
+
+```
+sudo pip3 install pgcli
+```
+
+For detailed installation steps for different OS, please refer to the pgcli home page: [http://pgcli.com](http://pgcli.com/)
+
+After the installation is complete, you can use the help command to view help information.
+
+```
+[root@mogdb-kernel-0004 ~]# pgcli --help
+Usage: pgcli [OPTIONS] [DBNAME] [USERNAME]
+
+Options:
+  -h, --host TEXT            Host address of the postgres database.
+  -p, --port INTEGER         Port number at which the postgres instance is
+                             listening.
+  -U, --username TEXT        Username to connect to the postgres database.
+  -u, --user TEXT            Username to connect to the postgres database.
+  -W, --password             Force password prompt.
+  -w, --no-password          Never prompt for password.
+  --single-connection        Do not use a separate connection for completions.
+  -v, --version              Version of pgcli.
+  -d, --dbname TEXT          database name to connect to.
+  --pgclirc FILE             Location of pgclirc file.
+  -D, --dsn TEXT             Use DSN configured into the [alias_dsn] section
+                             of pgclirc file.
+  --list-dsn                 list of DSN configured into the [alias_dsn]
+                             section of pgclirc file.
+  --row-limit INTEGER        Set threshold for row limit prompt. Use 0 to
+                             disable prompt.
+  --less-chatty              Skip intro on startup and goodbye on exit.
+  --prompt TEXT              Prompt format (Default: "\u@\h:\d> ").
+  --prompt-dsn TEXT          Prompt format for connections using DSN aliases
+                             (Default: "\u@\h:\d> ").
+  -l, --list                 list available databases, then exit.
+  --auto-vertical-output     Automatically switch to vertical output mode if
+                             the result is wider than the terminal width.
+  --warn [all|moderate|off]  Warn before running a destructive query.
+  --help                     Show this message and exit.
+```
+
+<br/>
+
+## Example of Connecting MogDB
+
+Switch to the user omm through the `su - omm` command, and then run `pgcli -d postgres -p 26000` to connect to MogDB.
+
+```
+[root@mogdb-kernel-0004 ~]# su - omm
+Last login: Wed Feb 16 15:31:37 CST 2022 on pts/1
+[omm@mogdb-kernel-0004 ~]$ pgcli -d postgres -p 26000
+Server: PostgreSQL 9.2.4
+Version: 3.3.1
+Home: http://pgcli.com
+postgres> \l
++-----------+---------+----------+-------------+-------------+-------------------+
+| Name      | Owner   | Encoding | Collate     | Ctype       | Access privileges |
+|-----------+---------+----------+-------------+-------------+-------------------|
+| postgres  | omm     | UTF8     | en_US.UTF-8 | en_US.UTF-8 | <null>            |
+| template0 | omm     | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =c/omm            |
+|           |         |          |             |             | omm=CTc/omm       |
+| template1 | omm     | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =c/omm            |
+|           |         |          |             |             | omm=CTc/omm       |
++-----------+---------+----------+-------------+-------------+-------------------+
+SELECT 3
+Time: 0.020s
+postgres>
+```
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-gui-tools-to-access-mogdb/datastudio.md b/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-gui-tools-to-access-mogdb/datastudio.md
new file mode 100644
index 0000000000000000000000000000000000000000..3e511fd883e40b6d584056f0f7944ee05ae235a4
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-gui-tools-to-access-mogdb/datastudio.md
@@ -0,0 +1,112 @@
+---
+title: Use Data Studio to Access MogDB
+summary: Use Data Studio to Access MogDB
+author: Guo Huan
+date: 2021-08-31
+---
+
+# Use Data Studio to Access MogDB
+
+This document introduces how to access MogDB through Data Studio.
+
+<br/>
+
+## Introduction
+
+**Data Studio** is an Integrated Development Environment (IDE) that helps database developers build the application conveniently. It supports essential features of the database.
+This tool allows working with database objects with minimal programming knowledge. Data Studio provides you with various features, such as
+
+- creating and managing database objects
+- executing SQL statements or SQL scripts
+- editing and executing PL/SQL statements
+- viewing the execution plan and cost through the GUI
+- exporting table data
+
+The database objects that are created and managed include
+
+- database
+- schema
+- function
+- procedure
+- table
+- sequence
+- index
+- view
+- tablespace
+- synonym
+
+It also provides SQL assistance for various queries/procedures/functions executed in the SQL Terminal and PL/SQL Viewer.
+
+<br/>
+
+## System Requirements
+
+This section provides the minimum system requirements for using Data Studio.
+
+**Hardware Requirements**
+
+Table 1 Hardware Requirements for Data Studio
+
+| **Hardware Requirement** | **Configuration**                                                     |
+| ------------ | ------------------------------------------------------------ |
+| CPU          | x86 64-bit                                                     |
+| Available RAM     | A minimum of 1 GB memory                                                  |
+| Available hard disk     | A minimum of 1 GB space reserved for Data Studio installation directory and 100 MB space reserved for user's HOME directory. |
+|Network requirements|Gigabit Ethernet|
+
+**Operating System Requirements**
+
+The supported versions of Microsoft Windows running on a universal x86 server include Windows 7 (64-bit), Windows 10 (64-bit), Windows 2012 (64-bit), and Windows 2016 (64-bit).
+
+**Software Requirements**
+
+Java 1.8.0_181 or later
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **Note:**
+>
+> * Please refer to [https://java.com/en/download/help/path.html](https://java.com/en/download/help/path.html) to set the Java Home path.
+> * To ensure the optimal experience, the recommended minimum screen resolution is 1080 x 768. Below this resolution, the interface will be abnormal.
+
+<br/>
+
+## Download and Installation
+
+The download address of Data Studio is as follows: <https://opengauss.org/en/download.html>
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/datastudio-2.png)
+
+After downloading, unzip the installation package and double-click **Data Studio.exe** to run the software.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/use-gui-tools-to-access-mogdb-2.png)
+
+<br/>
+
+## Connection String Configuration
+
+When the software is opened for the first time, the **New Database Connection** window will pop up, as shown in the figure below.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/use-gui-tools-to-access-mogdb-15.png)
+
+You can also choose **File &gt; New Connection** to open this window.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/use-gui-tools-to-access-mogdb-16.png)
+
+Fill in the information on the **General** tab, and click **OK** to establish a database connection.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/use-gui-tools-to-access-mogdb-17.png)
+
+<br/>
+
+## Interface Display
+
+After a successful connection, the software interface is shown below, with examples of syntax and operation lists on the right.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/use-gui-tools-to-access-mogdb-18.png)
+
+<br/>
+
+## Follow-Up Procedure
+
+If you want to learn more about the usage instructions of Data Studio, please choose **Help &gt; User Manual**, or visit the following page to browse the official documents online: [Data Studio User Manual](https://opengauss.obs.cn-south-1.myhuaweicloud.com/2.0.0/Data%20Studio%20User%20Manual.pdf).
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/use-gui-tools-to-access-mogdb-19.png)
diff --git a/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-gui-tools-to-access-mogdb/dbeaver.md b/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-gui-tools-to-access-mogdb/dbeaver.md
new file mode 100644
index 0000000000000000000000000000000000000000..e4a742000220f75fa4f76f4ebe109b2344d76b1d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-gui-tools-to-access-mogdb/dbeaver.md
@@ -0,0 +1,64 @@
+---
+title: Use DBeaver to Access MogDB
+summary: Use DBeaver to Access MogDB
+author: Guo Huan
+date: 2021-08-31
+---
+
+# Use DBeaver to Access MogDB
+
+This document introduces how to access MogDB through DBeaver.
+
+<br/>
+
+## Introduction
+
+**Dbeaver** is a cross-platform database developer tool, including SQL programming, database management and analysis. It supports any database system that adapts to the JDBC driver. At the same time, the tool also supports some non-JDBC data sources, such as MongoDB, Cassandra, Redis, DynamoDB, etc.
+
+* This tool provides many powerful features, such as metadata editor, SQL editor, rich text data editor, ERD, data import/export/migration, SQL execution plan, etc.
+* The tool is developed based on the eclipse platform.
+* Adapted databases include MySQL/MariaDB, PostgreSQL, Greenplum, Oracle, DB2 LUW, Exasol, SQL Server, Sybase/SAP ASE, SQLite, Firebird, H2, HSQLDB, Derby, Teradata, Vertica, Netezza, Informix, etc.
+
+<br/>
+
+## Download and Installation
+
+Dbeaver is an open source software with the download address as follows: [https://dbeaver.io/download/](https://dbeaver.io/download/)
+
+Select and download the appropriate installation package according to your operating system, and double-click the package to install it after the download is complete.
+
+<br/>
+
+## Connection String Configuration
+
+When the software is opened for the first time, the **Connect to a database** window will pop up, as shown in the figure below.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/use-gui-tools-to-access-mogdb-20.png)
+
+You can also choose **Database &gt; New Database Connection** to open this window.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/use-gui-tools-to-access-mogdb-21.png)
+
+Choose **Popular &gt; PostgreSQL**, click **Next**, and download the PostgreSQL driver file on the pop-up page.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/use-gui-tools-to-access-mogdb-22.png)
+
+After the download is complete, the **Connect a database** window will pop up, fill in the database information in this window, and then click **Finish** to establish a database connection.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/use-gui-tools-to-access-mogdb-23.png)
+
+<br/>
+
+## Interface Display
+
+After a successful connection, the software interface is shown below.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/use-gui-tools-to-access-mogdb-24.png)
+
+<br/>
+
+## Follow-Up Procedure
+
+If you want to learn more about the usage instructions of DBeaver, please choose **Help &gt; Help Contents**, or visit the following page to browse the official documents online: [https://dbeaver.com/docs/wiki/](https://dbeaver.com/docs/wiki/).
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/use-gui-tools-to-access-mogdb-25.png)
diff --git a/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-middleware-to-access-mogdb/weblogic-configures-mogdb(postgresql)-data-source-reference.md b/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-middleware-to-access-mogdb/weblogic-configures-mogdb(postgresql)-data-source-reference.md
new file mode 100644
index 0000000000000000000000000000000000000000..f878e806d439ae0704f97d145ed4a7877192b195
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-middleware-to-access-mogdb/weblogic-configures-mogdb(postgresql)-data-source-reference.md
@@ -0,0 +1,175 @@
+---
+title: WebLogic Used for Configuring MogDB (PostgreSQL) Data Sources
+summary: WebLogic Used for Configuring MogDB (PostgreSQL) Data Sources
+author: Guo Huan
+date: 2021-08-11
+---
+
+# WebLogic Used for Configuring MogDB (PostgreSQL) Data Sources
+
+## Overview
+
+WebLogic can be used for configuring MogDB data sources. So does it for configuring PostgreSQL data sources. For details, see the following sections.
+
+<br/>
+
+## Prerequisites
+
+### Confirmation of the WebLogic JDK Version
+
+```bash
+$ /home/jdk1.7.0_80/bin/java -version
+java version "1.7.0_80"
+Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
+Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)
+```
+
+Find the target JDK and check its version.
+
+The JAR packages of the JDBC driver vary depending on the JDK version. Only when you are clear about the JDK version can you download the corresponding driver.
+
+The current environment takes JDK 1.7.0 as an example.
+
+### Downloading of the JDBC Driver Package
+
+```
+The current version is JDBC 42.2.23.
+
+This JDBC is the target driver to be downloaded unless you have special requirements (run the old application programs or JVM). It supports PostgreSQL 8.2 or later and requires Java 6 or a higher version. It also supports the SSL and javax.sql packages.
+
+JDBC 4.2 applies when you use Java 8.
+JDBC 4.1 applies when you use Java 7.
+JDBC 4.0 applies when you use Java 6.
+```
+
+The links for downloading JDBC of certain versions corresponding to the JDK of specific versions are as follows:
+
+| JDK Version | Website of the Corresponding JDBC Driver                     |
+| ----------- | ------------------------------------------------------------ |
+| 1.6         | <https://jdbc.postgresql.org/download/postgresql-42.2.23.jre6.jar> |
+| 1.7         | <https://jdbc.postgresql.org/download/postgresql-42.2.23.jre7.jar> |
+| 1.8         | <https://jdbc.postgresql.org/download/postgresql-42.2.23.jar>  |
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/weblogic-configures-mogdb(postgresql)-data-source-reference-1.png)
+
+The best choice is to use JDBC  42.2.23 because it supports PostgreSQL 8.2 or a higher version and is the most stable version.
+
+Download website: [https://jdbc.postgresql.org/download.html](https://jdbc.postgresql.org/download.html)
+
+<br/>
+
+## Configuration Process
+
+### Confirmation of Related Database Information
+
+| Database Name | User  | Password | Port  | IP Address |
+| ------------- | ----- | -------- | ----- | ---------- |
+| postgres      | mogdb | 123456   | 25431 |            |
+
+### Confirmation of Port Connection
+
+On the middleware server, access the IP port using Telnet and make sure that the database port can be accessed.
+
+### Configuration of Data Sources on the Console
+
+#### Adding a Driver to CLASSPATH
+
+a. Back up the startup file.
+
+```
+cd ${DOMAIN_HOME}/bin
+cp startWebLogic.sh startWebLogic.sh.bak
+```
+
+b. Upload the driver to the WebLogic server.
+
+For example, the JDK version is 1.7. Upload the JDK driver to the following directory:
+
+/home/postgresql-42.2.23.jre7.jar
+
+c. Modify the startup file to add the driver package.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/weblogic-configures-mogdb(postgresql)-data-source-reference-2.png)
+
+Change CLASSPATH="${SAVE_CLASSPATH}"
+
+to:
+
+CLASSPATH="${SAVE_CLASSPATH}:/home/postgresql-42.2.23.jre7.jar"
+
+d. Restart the server to make the change take effect.
+
+#### Configuring Data Sources
+
+a. Create new data sources.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/weblogic-configures-mogdb(postgresql)-data-source-reference-3.png)
+
+b. Fill JNDI with related information.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/weblogic-configures-mogdb(postgresql)-data-source-reference-4.png)
+
+c. Select the default driver.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/weblogic-configures-mogdb(postgresql)-data-source-reference-5.png)
+
+d. Select the default option.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/weblogic-configures-mogdb(postgresql)-data-source-reference-6.png)
+
+e. Fill the database information.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/weblogic-configures-mogdb(postgresql)-data-source-reference-7.png)
+
+f. Test the connection.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/weblogic-configures-mogdb(postgresql)-data-source-reference-8.png)
+
+g. Make sure that the test is successful.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/weblogic-configures-mogdb(postgresql)-data-source-reference-9.png)
+
+h. Select the server as required.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/weblogic-configures-mogdb(postgresql)-data-source-reference-10.png)
+
+i. Finish configurations and activate changes.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/weblogic-configures-mogdb(postgresql)-data-source-reference-11.png)
+
+<br/>
+
+## MogDB Connected Using the openGauss Driver
+
+openGauss JDBC provides only JDK 1.8. Applications developed using JDK 1.8 can connect MogDB using the openGauss driver.
+
+Applications developed using JDK 1.6 or 1.7 can connect MogDB using only the JDBC driver from the PostgreSQL official website.
+
+Website for downloading the openGauss driver:
+
+[https://opengauss.org/zh/download.html](https://opengauss.org/zh/download.html)
+
+<br/>
+
+## Common Questions
+
+When the driver version is higher than the JDK version, the following error occurs once the server is started:
+
+```
+<xxx 10, 2021 10:43:53 PM CST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'pg JDBC Data Source' due to error java.lang.UnsupportedClassVersionError: org/postgresql/Driver : Unsupported major.minor version 52.0.
+java.lang.UnsupportedClassVersionError: org/postgresql/Driver : Unsupported major.minor version 52.0
+        at java.lang.ClassLoader.defineClass1(Native Method)
+        at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
+        at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
+        at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
+        at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
+        Truncated. see log file for complete stacktrace
+Caused By: java.lang.UnsupportedClassVersionError: org/postgresql/Driver : Unsupported major.minor version 52.0
+        at java.lang.ClassLoader.defineClass1(Native Method)
+        at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
+        at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
+        at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
+        at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
+        Truncated. see log file for complete stacktrace
+>
+```
diff --git a/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-middleware-to-access-mogdb/websphere-configures-mogdb(postgresql)-data-source-reference.md b/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-middleware-to-access-mogdb/websphere-configures-mogdb(postgresql)-data-source-reference.md
new file mode 100644
index 0000000000000000000000000000000000000000..719e09a4057d1e3e9a95f46668ecfce085d4eef9
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-middleware-to-access-mogdb/websphere-configures-mogdb(postgresql)-data-source-reference.md
@@ -0,0 +1,212 @@
+---
+title: WebSphere Used for Configuring MogDB (PostgreSQL) Data Sources
+summary: WebSphere Used for Configuring MogDB (PostgreSQL) Data Sources
+author: Guo Huan
+date: 2021-08-09
+---
+
+# WebSphere Used for Configuring MogDB (PostgreSQL) Data Sources
+
+## Overview
+
+WebSphere can be used for configuring MogDB data sources. So does it for configuring PostgreSQL data sources. For details, see the following sections.
+
+<br/>
+
+## Prerequisites
+
+### Confirmation of the WebSphere JDK Version
+
+```bash
+C:\Windows\system32>D:\IBM1\WebSphere\AppServer\java\bin\java -version
+java version "1.6.0"
+Java(TM) SE Runtime Environment (build pwa6460_26sr8fp26ifix-20160708_01(SR8 FP26+IX90174))
+IBM J9 VM (build 2.6, JRE 1.6.0 Windows 8 amd64-64 Compressed References 20160406_298378 (JIT enabled, AOT enabled)
+J9VM - R26_Java626_SR8_20160406_0830_B298378
+JIT  - tr.r11_20160328_114192
+GC   - R26_Java626_SR8_20160406_0830_B298378_CMPRSS
+J9CL - 20160406_298378)
+JCL  - 20160507_01
+
+C:\Windows\system32>
+```
+
+Find the target JDK and check its version.
+
+The JAR packages of the JDBC driver vary depending on the JDK version. Only when you are clear about the JDK version can you download the corresponding driver.
+
+### Downloading of the JDBC Driver Package
+
+```
+The current version is JDBC 42.2.23.
+
+This JDBC is the target driver to be downloaded unless you have special requirements (run the old application programs or JVM). It supports PostgreSQL 8.2 or later and requires Java 6 or a higher version. It also supports the SSL and javax.sql packages.
+
+JDBC 4.2 applies when you use Java 8.
+JDBC 4.1 applies when you use Java 7.
+JDBC 4.0 applies when you use Java 6.
+```
+
+The links for downloading JDBC of certain versions corresponding to the JDK of specific versions are as follows:
+
+| JDK Version | Website of the Corresponding JDBC Driver                     |
+| ----------- | ------------------------------------------------------------ |
+| 1.6         | <https://jdbc.postgresql.org/download/postgresql-42.2.23.jre6.jar> |
+| 1.7         | <https://jdbc.postgresql.org/download/postgresql-42.2.23.jre7.jar> |
+| 1.8         | <https://jdbc.postgresql.org/download/postgresql-42.2.23.jar>  |
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/weblogic-configures-mogdb(postgresql)-data-source-reference-1.png)
+
+The best choice is to use JDBC  42.2.23 because it supports PostgreSQL 8.2 or a higher version and is the most stable version.
+
+Download website: [https://jdbc.postgresql.org/download.html](https://jdbc.postgresql.org/download.html)
+
+<br/>
+
+## Configuration Process
+
+### Confirmation of Related Database Information
+
+| Database Name | User     | Password | Port | IP Address |
+| ------------- | -------- | -------- | ---- | ---------- |
+| postgres      | postgres | 123456   | 5432 |            |
+
+### Confirmation of Port Connection
+
+On the middleware server, access the IP port using Telnet and make sure that the database port can be accessed.
+
+### Console Configuration
+
+#### Configuring the JDBC Provider
+
+a. Create a JDBC provider.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-1.png)
+
+b. Create another JDBC provider.
+
+org.postgresql.ds.PGConnectionPoolDataSource
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-2.png)
+
+c. Specify the driver path.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-3.png)
+
+d. Click **Next** to save the configuration.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-4.png)
+
+#### Configuring Data Sources
+
+a. Create a data source.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-5.png)
+
+b. Fill JNDI with related information.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-6.png)
+
+c. Select the existing JDBC provider.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-7.png)
+
+d. Select the default option.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-8.png)
+
+e. Click **Next**.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-9.png)
+
+f. Save the configuration.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-10.png)
+
+#### Configuring Database Authentication
+
+a. Click the configured pgtest data source.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-11.png)
+
+b. Configure the JAAS - J2C authentication data.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-12.png)
+
+c. Create authentication.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-13.png)
+
+d. Specify the user and password and specify the alias as you will.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-14.png)
+
+e. Save the configuration.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-15.png)
+
+f. Click the configured pgtest data source again and configure security settings.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-16.png)
+
+g. Save the configuration.
+
+#### Customizing Properties
+
+a. Click the configured pgtest data source.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-17.png)
+
+ b. Customize the properties.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-18.png)
+
+c. Click the filter icon.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-19.png)
+
+d. Filter serverName.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-20.png)
+
+e. Click **serverName**.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-21.png)
+
+f. Fill the IP address of the target database.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-22.png)
+
+g. Save the configuration.
+
+h. Similarly, filter portNumber/databaseName.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-23.png)
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-24.png)
+
+#### Restarting the Server to Test Connection
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-25.png)
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-26.png)
+
+<br/>
+
+## MogDB Connected Using the openGauss Driver
+
+openGauss JDBC provides only JDK 1.8. Applications developed using JDK 1.8 can connect MogDB using the openGauss driver.
+
+Applications developed using JDK 1.6 or 1.7 can connect MogDB using only the JDBC driver from the PostgreSQL official website.
+
+Website for downloading the openGauss driver:
+
+[https://opengauss.org/zh/download.html](https://opengauss.org/zh/download.html)
+
+<br/>
+
+## Common Questions
+
+The driver version does not match the JDK version.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-27.png)
diff --git a/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/c-cpp.md b/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/c-cpp.md
new file mode 100644
index 0000000000000000000000000000000000000000..adc50907901ba255f81ece5eaf5c78ecd05ab99f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/c-cpp.md
@@ -0,0 +1,14 @@
+---
+title: Use C/C++ to Access MogDB
+summary: Use C/C++ to Access MogDB
+author: Guo Huan
+date: 2022-03-25
+---
+
+
+
+# Use C/C++ to Access MogDB
+
+libpq is the C application programmer's interface to PostgreSQL. libpq is a set of library functions that allow client programs to pass queries to the PostgreSQL backend server and to receive the results of these queries. libpq is also the underlying engine for several other PostgreSQL application interfaces, including those written for C++, Perl, Python, Tcl and ECPG.
+
+For detailed instructions on using C/C++ to access MogDB database, please refer to [Development Based on libpq](1-development-based-on-libpq) chapter in "Developer's Guide".
diff --git a/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/go.md b/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/go.md
new file mode 100644
index 0000000000000000000000000000000000000000..016b543d1443be96a5d71030c29b19ef9ae9757a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/go.md
@@ -0,0 +1,16 @@
+---
+title: Use Go to Access MogDB
+summary: Use Go to Access MogDB
+author: Guo Huan
+date: 2022-03-31
+---
+
+
+
+# Use Go to Access MogDB
+
+openGauss provides Go openGauss driver for Go‘s database/sql package based on [lib/pq](https://github.com/lib/pq), which is also suitable for Go connection to MogDB.
+
+You can view the source code and operating instructions for this driver by clicking on the following links.
+
+[Source Code](https://gitee.com/opengauss/openGauss-connector-go-pq), [Operating Instructions](https://gitee.com/opengauss/openGauss-connector-go-pq/blob/master/README.cn.md)
diff --git a/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/java.md b/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/java.md
new file mode 100644
index 0000000000000000000000000000000000000000..2268a240c4a07ee5cf98f213f076e694b297baf2
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/java.md
@@ -0,0 +1,14 @@
+---
+title: Use Java to Access MogDB
+summary: Use Java to Access MogDB
+author: Guo Huan
+date: 2022-03-25
+---
+
+
+
+# Use Java to Access MogDB
+
+Java Database Connectivity (JDBC) is a Java API for running SQL statements. It provides unified access interfaces for different relational databases, based on which applications process data. MogDB supports JDBC 4.0.
+
+For detailed instructions on using Java to access MogDB database, please refer to [Development Based on JDBC](1-development-based-on-jdbc-overview) chapter in "Developer's Guide".
diff --git a/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/nodejs.md b/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/nodejs.md
new file mode 100644
index 0000000000000000000000000000000000000000..ae314c7e8d1b86af74766491f952887d9a224b57
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/nodejs.md
@@ -0,0 +1,16 @@
+---
+title: Use NodeJS to Access MogDB
+summary: Use NodeJS to Access MogDB
+author: Guo Huan
+date: 2022-03-31
+---
+
+
+
+# Use NodeJS to Access MogDB
+
+openGauss provides a driver for NodeJS based on [node-postgres](https://github.com/brianc/node-postgres), which also works with NodeJS to connect to MogDB.
+
+You can view the source code and operating instructions for this driver by clicking on the following links.
+
+[Source Code](https://gitee.com/opengauss/openGauss-connector-nodejs), [Operating Instructions](https://gitee.com/opengauss/openGauss-connector-nodejs/blob/master/README.md)
diff --git a/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/python.md b/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/python.md
new file mode 100644
index 0000000000000000000000000000000000000000..28b12116140906452e24d2638cc8fa817e46e2c3
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/python.md
@@ -0,0 +1,14 @@
+---
+title: Use Python to Access MogDB
+summary: Use Python to Access MogDB
+author: Guo Huan
+date: 2022-03-25
+---
+
+
+
+# Use Python to Access MogDB
+
+Psycopg is a Python API used to execute SQL statements and provides a unified access API for PostgreSQL and GaussDB. Applications can perform data operations based on psycopg. Psycopg2 is an encapsulation of libpq and is implemented using the C language, which is efficient and secure. It provides cursors on both clients and servers, asynchronous communication and notification, and the COPY TO and COPY FROM functions. Psycopg2 supports multiple types of Python out-of-the-box and adapts to PostgreSQL data types. Through the flexible object adaptation system, you can extend and customize the adaptation. Psycopg2 is compatible with Unicode and Python 3.
+
+MogDB supports the psycopg2 feature and allows psycopg2 to be connected in SSL mode. For detailed instructions on using Python to access MogDB database, please refer to [Development Based on Psycopg](1-psycopg-based-development) chapter in "Developer's Guide".
diff --git a/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/rust.md b/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/rust.md
new file mode 100644
index 0000000000000000000000000000000000000000..944c351bcf7b682af8d8a3446eb72f50bf00e7ff
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/rust.md
@@ -0,0 +1,16 @@
+---
+title: Use Rust to Access MogDB
+summary: Use Rust to Access MogDB
+author: Guo Huan
+date: 2022-03-31
+---
+
+
+
+# Use Rust to Access MogDB
+
+openGauss provides a driver for Rust based on [rust-postgres](https://github.com/sfackler/rust-postgres), which is also applicable to the Rust language for connecting to MogDB.
+
+You can view the source code and operating instructions for this driver by clicking on the following links.
+
+[Source Code](https://gitee.com/opengauss/openGauss-connector-rust), [Operating Instructions](https://gitee.com/opengauss/openGauss-connector-rust/blob/master/README.md)
diff --git a/product/en/docs-mogdb/v3.0/quick-start/mogdb-playground.md b/product/en/docs-mogdb/v3.0/quick-start/mogdb-playground.md
new file mode 100644
index 0000000000000000000000000000000000000000..be106d349fbc18df14083939af7f687dd2600836
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/quick-start/mogdb-playground.md
@@ -0,0 +1,46 @@
+---
+title: MogDB Playground
+summary: MogDB Playground
+author: Guo Huan
+date: 2022-03-18
+---
+
+# MogDB Playground
+
+MogDB Playground is an online learning and hands-on training platform for MogDB database provided by [modb](https://www.modb.pro/), which also provides Oracle/MySQL compatible packages and Mogila dataset. You can connect to the database with one click through the command line terminal of your browser, and experience the functions of MogDB conveniently and quickly, without the need to provide your own environment for installation.
+
+<br/>
+
+## Enter the Hands-on Training Environment
+
+Visit [MogDB Playground](https://www.modb.pro/terminal). After entering, the relevant operation documents will be displayed on the left side, and the operation platform will be displayed on the right side. At this time, it is not yet connected, and you need to click **Click to enter the hands-on training environment**. Then register or log in to your modb  account in the pop-up window to use MogDB Playground for free.
+
+![image.png](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/playground-1.png)
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/playground-6.png)
+
+## Start Using
+
+After a successful connection, the official operation starts, and it is time to perform the relevant operations.
+
+![image.png](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/playground-2.png)
+
+## Reference Document
+
+When operating, you can operate according to the operation document on the left side, while the operation document on the left side can be collapsed.
+
+![image.png](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/playground-3.png)
+
+## Shutdown Environment
+
+If you want to quit the database, you can click the close button at the bottom right corner to close it, but the data created before will be cleared after closing, and it will be a new environment when you connect again, so please operate carefully.
+
+![image.png](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/playground-4.png)
+
+## FAQ
+
+**What if I exit the page in the middle?**
+
+Users who close the current page directly, the fact that the database resources are still running, as long as you re-enter within 30 minutes, the previously created data will not be deleted (refresh the current page is the same), and exit the current page in the middle, there will be a relevant prompt to determine whether to leave.
+
+![image.png](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/playground-5.png)
diff --git a/product/en/docs-mogdb/v3.0/quick-start/mogila.md b/product/en/docs-mogdb/v3.0/quick-start/mogila.md
new file mode 100644
index 0000000000000000000000000000000000000000..1c8b0558d0e3deeab23fb341b8af12c88635178a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/quick-start/mogila.md
@@ -0,0 +1,410 @@
+---
+title: Using Sample Dataset Mogila
+summary: Using Sample Dataset Mogila
+author: Guo Huan
+date: 2022-02-11
+---
+
+
+
+# Using Sample Dataset Mogila
+
+MogDB provides a sample dataset Mogila, which is a port of the [Sakila example database](https://dev.mysql.com/doc/sakila/en/) available for MySQL. **Sakila** was originally developed by Mike Hillyer of the MySQL AB documentation team. It is intended to provide a standard schema that can be used for examples in books, tutorials, articles, samples, etc.
+
+Mogila is a database representing a DVD rental store, containing information about films (like title, category, actresses), rental stores (like address, staff members, customers) and rentals.
+
+Mogila works against MogDB 2.1 and above.
+
+<br/>
+
+## Entity-relationship Model Diagram
+
+The image below shows an overview of the Mogila database tables and views. Here you can see how the tables relate to each other, through each fields. For example, the `film` table has string columns like `title` and `description`. It also relates to the table `language` with the columns `language_id` and `original_language_id`. With that information, you know that you can join both tables to get the language of each film, or to list all films for a specific language.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/mogila-erm.png)
+
+<br/>
+
+## Use Mogila on MogDB Container Edition
+
+The Mogila sample dataset has been built into the MogDB Container Edition, and no additional installation is required.
+
+1. [Install container-based MogDB](container-based-installation).
+
+2. Use mogila:
+
+   ```
+   docker exec -it mogdb bash
+   omm@eb7aef3f860f:~$ gsql -d mogila -p5432
+   gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+   Non-SSL connection (SSL connection is recommended when requiring high-security)
+   Type "help" for help.
+   
+   mogila=# \dt
+                             List of relations
+    Schema |     Name      | Type  | Owner |             Storage
+   --------+---------------+-------+-------+----------------------------------
+    public | actor         | table | mogdb | {orientation=row,compression=no}
+    public | address       | table | mogdb | {orientation=row,compression=no}
+    public | category      | table | mogdb | {orientation=row,compression=no}
+    public | city          | table | mogdb | {orientation=row,compression=no}
+    public | country       | table | mogdb | {orientation=row,compression=no}
+    public | customer      | table | mogdb | {orientation=row,compression=no}
+    public | film          | table | mogdb | {orientation=row,compression=no}
+    public | film_actor    | table | mogdb | {orientation=row,compression=no}
+    public | film_category | table | mogdb | {orientation=row,compression=no}
+    public | inventory     | table | mogdb | {orientation=row,compression=no}
+    public | language      | table | mogdb | {orientation=row,compression=no}
+    public | payment       | table | mogdb | {orientation=row,compression=no}
+    public | rental        | table | mogdb | {orientation=row,compression=no}
+    public | staff         | table | mogdb | {orientation=row,compression=no}
+    public | store         | table | mogdb | {orientation=row,compression=no}
+   (15 rows)
+   
+   mogila=#
+   ```
+
+<br/>
+
+## Use Mogila on MogDB Enterprise Edition
+
+1. [Install MogDB](installation-on-a-single-node)。
+
+2. Create the sample database mogila and user mogdb, and quit.
+
+   ```
+   # switch to user omm
+   [root@test ~]# su - omm
+   # Log in to the postgres database and enter the port number according to the actual situation
+   [omm@test ~]$ gsql -d postgres -p5432 -r
+   gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+   Non-SSL connection (SSL connection is recommended when requiring high-security)
+   Type "help" for help.
+   MogDB=#create database mogila DBCOMPATIBILITY='PG';
+   CREATE DATABASE
+   MogDB=#create user mogdb password 'Enmo@123';
+   CREATE ROLE
+   MogDB=#\q
+   [omm@test ~]$
+   ```
+
+3. [Download mogila](https://gitee.com/enmotech/mogila), and upload the files to the server and enter the directory where mogila files are located.
+
+4. Create schema objects then insert data manually:
+
+   - 4.1 Create all schema objetcs (tables, etc):
+
+   ```
+   gsql -d mogila -p5432 -f mogila-schema.sql
+   ```
+
+   - 4.2. Insert all data:
+
+   ```
+   gsql -d mogila -p5432 -f mogila-data.sql
+   ```
+
+   **OR create schema objects and insert data by 1 script, if you have done 4.1 and 4.2, you don't need 5!!**
+
+5. Create all schema objetcs (tables, etc) and Insert all data:
+
+   ```
+   gsql -d mogila -p5432 -f mogila-insert-data.sql
+   ```
+
+6. Done! Use:
+
+   ```
+   [omm@test ~]$ gsql -d mogila -p5432 -r
+   gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+   Non-SSL connection (SSL connection is recommended when requiring high-security)
+   Type "help" for help.
+   
+   mogila=# \dt
+                             List of relations
+    Schema |     Name      | Type  | Owner |             Storage
+   --------+---------------+-------+-------+----------------------------------
+    public | actor         | table | mogdb | {orientation=row,compression=no}
+    public | address       | table | mogdb | {orientation=row,compression=no}
+    public | category      | table | mogdb | {orientation=row,compression=no}
+    public | city          | table | mogdb | {orientation=row,compression=no}
+    public | country       | table | mogdb | {orientation=row,compression=no}
+    public | customer      | table | mogdb | {orientation=row,compression=no}
+    public | film          | table | mogdb | {orientation=row,compression=no}
+    public | film_actor    | table | mogdb | {orientation=row,compression=no}
+    public | film_category | table | mogdb | {orientation=row,compression=no}
+    public | inventory     | table | mogdb | {orientation=row,compression=no}
+    public | language      | table | mogdb | {orientation=row,compression=no}
+    public | payment       | table | mogdb | {orientation=row,compression=no}
+    public | rental        | table | mogdb | {orientation=row,compression=no}
+    public | staff         | table | mogdb | {orientation=row,compression=no}
+    public | store         | table | mogdb | {orientation=row,compression=no}
+   (15 rows)
+   
+   mogila=#
+   ```
+
+<br/>
+
+## Sample Queries
+
+This section shows how to use the sample database Mogila with some queries. All the queries results were limited by the first 10 items.
+
+- List all the films by ordered by their length
+
+  ```sql
+  select
+      film_id,
+      title,
+      length
+  from
+      film
+  order by
+      length desc;
+  ```
+
+  ```sql
+  |film_id|title             |length|
+  |-------|------------------|------|
+  |426    |HOME PITY         |185   |
+  |690    |POND SEATTLE      |185   |
+  |609    |MUSCLE BRIGHT     |185   |
+  |991    |WORST BANGER      |185   |
+  |182    |CONTROL ANTHEM    |185   |
+  |141    |CHICAGO NORTH     |185   |
+  |349    |GANGS PRIDE       |185   |
+  |212    |DARN FORRESTER    |185   |
+  |817    |SOLDIERS EVOLUTION|185   |
+  |872    |SWEET BROTHERHOOD |185   |
+  ```
+
+- List how many films there are in each film category
+
+  ```sql
+  select
+      category.name,
+      count(category.name) category_count
+  from
+      category
+  left join film_category on
+      category.category_id = film_category.category_id
+  left join film on
+      film_category.film_id = film.film_id
+  group by
+      category.name
+  order by
+      category_count desc;
+  ```
+
+  ```sql
+  |name       |category_count|
+  |-----------|--------------|
+  |Sports     |74            |
+  |Foreign    |73            |
+  |Family     |69            |
+  |Documentary|68            |
+  |Animation  |66            |
+  |Action     |64            |
+  |New        |63            |
+  |Drama      |62            |
+  |Sci-Fi     |61            |
+  |Games      |61            |
+  ```
+
+- Show the actors and actresses ordered by how many movies they are featured in
+
+  ```sql
+  select
+      actor.first_name,
+      actor.last_name,
+      count(actor.first_name) featured_count
+  from
+      actor
+  left join film_actor on
+      actor.actor_id = film_actor.actor_id
+  group by
+      actor.first_name,
+      actor.last_name
+  order by
+      featured_count desc;
+  ```
+
+  ```sql
+  |first_name|last_name|featured_count|
+  |----------|---------|--------------|
+  |SUSAN     |DAVIS    |54            |
+  |GINA      |DEGENERES|42            |
+  |WALTER    |TORN     |41            |
+  |MARY      |KEITEL   |40            |
+  |MATTHEW   |CARREY   |39            |
+  |SANDRA    |KILMER   |37            |
+  |SCARLETT  |DAMON    |36            |
+  |VIVIEN    |BASINGER |35            |
+  |VAL       |BOLGER   |35            |
+  |GROUCHO   |DUNST    |35            |
+  ```
+
+- Get a list of all active customers, ordered by their first name
+
+  ```sql
+  select
+      first_name,
+      last_name
+  from
+      customer
+  where
+      active = 1
+  order by first_name asc;
+  ```
+
+  ```sql
+  |first_name|last_name|
+  |----------|---------|
+  |MARY      |SMITH    |
+  |PATRICIA  |JOHNSON  |
+  |LINDA     |WILLIAMS |
+  |BARBARA   |JONES    |
+  |ELIZABETH |BROWN    |
+  |JENNIFER  |DAVIS    |
+  |MARIA     |MILLER   |
+  |SUSAN     |WILSON   |
+  |MARGARET  |MOORE    |
+  |DOROTHY   |TAYLOR   |
+  ```
+
+- See who rented most DVDs - and how many times
+
+  ```sql
+  select
+      customer.first_name,
+      customer.last_name,
+      count(customer.first_name) rentals_count
+  from
+      customer
+  left join rental on
+      customer.customer_id = rental.customer_id
+  group by
+      customer.first_name,
+      customer.last_name
+  order by rentals_count desc;
+  ```
+
+  ```sql
+  |first_name|last_name|rentals_count|
+  |----------|---------|-------------|
+  |ELEANOR   |HUNT     |46           |
+  |KARL      |SEAL     |45           |
+  |CLARA     |SHAW     |42           |
+  |MARCIA    |DEAN     |42           |
+  |TAMMY     |SANDERS  |41           |
+  |WESLEY    |BULL     |40           |
+  |SUE       |PETERS   |40           |
+  |MARION    |SNYDER   |39           |
+  |RHONDA    |KENNEDY  |39           |
+  |TIM       |CARY     |39           |
+  ```
+
+- See the total revenue of each rental store
+
+  ```sql
+  select
+      store.store_id,
+      sum(payment.amount) as "total revenue"
+  from
+      store
+  left join inventory on
+      inventory.store_id = store.store_id
+  left join rental on
+      rental.inventory_id = inventory.inventory_id
+  left join payment on
+      payment.rental_id = rental.rental_id
+  where
+      payment.amount is not null
+  group by
+      store.store_id
+  order by
+      sum(payment.amount) desc;
+  ```
+
+  ```sql
+  |store_id|total revenue|
+  |--------|-------------|
+  |       2|     33726.77|
+  |       1|     33689.74|
+  ```
+
+- List the top 5 film genres by their gross revenue
+
+  ```sql
+  select
+      category.name,
+      film.title,
+      sum(payment.amount) as "gross revenue"
+  from
+      film
+  left join film_category on
+      film_category.film_id = film.film_id
+  left join category on
+      film_category.category_id = category.category_id
+  left join inventory on
+      inventory.film_id = film.film_id
+  left join rental on
+      rental.inventory_id = inventory.inventory_id
+  left join payment
+      on payment.rental_id = rental.rental_id
+  where
+      payment.amount is not null
+  group by
+      category.name,
+      film.title
+  order by
+      sum(payment.amount) desc
+  limit 5;
+  ```
+
+  ```sql
+  |   name     |       title       | gross revenue|
+  |------------|-------------------|--------------|
+  |Music       | TELEGRAPH VOYAGE  |        231.73|
+  |Documentary | WIFE TURN         |        223.69|
+  |Comedy      | ZORRO ARK         |        214.69|
+  |Sci-Fi      | GOODFELLAS SALUTE |        209.69|
+  |Sports      | SATURDAY LAMBS    |        204.72|
+  ```
+
+- The `film.description` has the `text` type, allowing for full text search queries, select all descriptions with the words "documentary" and "robot"
+
+  ```sql
+  select
+      film.title,
+      film.description
+  from
+      film
+  where
+      to_tsvector(film.description) @@ to_tsquery('documentary & robot');
+  ```
+
+  ```sql
+  |  title          |                                                    description                                                     |
+  |-----------------|--------------------------------------------------------------------------------------------------------------------|
+  |CASPER DRAGONFLY | A Intrepid Documentary of a Boat And a Crocodile who must Chase a Robot in The Sahara Desert                       |
+  |CHAINSAW UPTOWN  | A Beautiful Documentary of a Boy And a Robot who must Discover a Squirrel in Australia                             |
+  |CONTROL ANTHEM   | A Fateful Documentary of a Robot And a Student who must Battle a Cat in A Monastery                                |
+  |CROSSING DIVORCE | A Beautiful Documentary of a Dog And a Robot who must Redeem a Womanizer in Berlin                                 |
+  |KANE EXORCIST    | A Epic Documentary of a Composer And a Robot who must Overcome a Car in Berlin                                     |
+  |RUNNER MADIGAN   | A Thoughtful Documentary of a Crocodile And a Robot who must Outrace a Womanizer in The Outback                    |
+  |SOUTH WAIT       | A Amazing Documentary of a Car And a Robot who must Escape a Lumberjack in An Abandoned Amusement Park             |
+  |SWEDEN SHINING   | A Taut Documentary of a Car And a Robot who must Conquer a Boy in The Canadian Rockies                             |
+  |VIRGIN DAISY     | A Awe-Inspiring Documentary of a Robot And a Mad Scientist who must Reach a Database Administrator in A Shark Tank |
+  ```
+
+<br/>
+
+## Clean Up
+
+To clean up the environment and destroy the database, run the following commands:
+
+```sql
+\c postgres;
+DROP DATABASE mogila;
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/1-GAUSS-00001-GAUSS-00100.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/1-GAUSS-00001-GAUSS-00100.md
new file mode 100644
index 0000000000000000000000000000000000000000..73f79f96a6fc4170879f17f339ec986c0dcf3a53
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/1-GAUSS-00001-GAUSS-00100.md
@@ -0,0 +1,828 @@
+---
+title: GAUSS-00001 - GAUSS-00100
+summary: GAUSS-00001 - GAUSS-00100
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-00001 - GAUSS-00100
+
+<br/>
+
+## GAUSS-00001 - GAUSS-00010
+
+<br/>
+
+GAUSS-00001: "operator does not exist: %s"
+
+SQLSTATE: 42883
+
+Description: The specified operator does not exist.
+
+Solution: Ensure that the error code contains the data type corresponding to the operator so that you can check whether the operator exists in the system catalog.
+
+GAUSS-00002: "could not identify an ordering operator for type %s"
+
+SQLSTATE: 42883
+
+Description: When you perform a sort or group operation, data is sorted. If the greater than (gt) or less than (lt) operator corresponding to the data type does not exist, this error is reported.
+
+Solution: The error code contains a data type. Query the operator corresponding to the data type from the **pg_operator** system catalog before using the operator and ensure that the operator exists.
+
+GAUSS-00003: "could not identify an equality operator for type %s"
+
+SQLSTATE: 42883
+
+Description: When you perform a group or unique operation, if the equal to (et) operation is involved, but the operator corresponding to the involved data type does not exist, this error is reported.
+
+Solution: The error code contains a data type. Query the operator corresponding to the data type from the **pg_operator** system catalog before using the operator and ensure that the operator exists.
+
+GAUSS-00004: "operator requires run-time type coercion: %s"
+
+SQLSTATE: 42883
+
+Description:**order by using** is used to specify an operator. During code execution, a parse function checks whether the provided data type and operator match. If they do not match, this error is reported.
+
+Solution: Ensure that the specified operator and data type match.
+
+GAUSS-00005: "operator is not unique: %s"
+
+SQLSTATE: 42725
+
+Description: No identified operators are provided for certain data types. Data types need to be converted to match proper operators. When multiple data types are converted, this error is reported.
+
+Solution: Convert a data type that has no corresponding operator to use a specific operator.
+
+GAUSS-00006: "operator is only a shell: %s"
+
+SQLSTATE: 42883
+
+Description: Undefined function.
+
+Solution: Modify the input statement.
+
+GAUSS-00007: "op ANY/ALL (array) requires array on right side"
+
+SQLSTATE: 42809
+
+Description: For the ANY/ALL (array) operator, the right parameter is not of the array type.
+
+Solution: For the ANY/ALL (array) operator, use the right parameter of the array type.
+
+GAUSS-00008: "op ANY/ALL (array) requires operator to yield Boolean"
+
+SQLSTATE: 42809
+
+Description: The value returned for the ANY/ALL (array) operator is not of the Boolean type.
+
+Solution: Ensure that the value returned for the ANY/ALL (array) operator is of the Boolean type.
+
+GAUSS-00009: "op ANY/ALL (array) requires operator not to return a set"
+
+SQLSTATE: 42809
+
+Description: The value returned for the ANY/ALL (array) operator is of the set type, which is not supported.
+
+Solution: Ensure that the value returned for the ANY/ALL (array) operator is of a type excluding the set type.
+
+GAUSS-00010: "could not find array type for data type %s"
+
+SQLSTATE: 42704
+
+Description: The array type corresponding to a data type cannot be found.
+
+Solution: When using the array type corresponding to a data type, ensure that any corresponding or compatible array type exists in the **pg_type** system catalog.
+
+<br/>
+
+## GAUSS-00011 - GAUSS-00020
+
+<br/>
+
+GAUSS-00011: "hash table corrupted"
+
+SQLSTATE: LL002
+
+Description: The hash table is damaged.
+
+Solution:Contact technical support.
+
+GAUSS-00012: "target lists can have at most %d entries"
+
+SQLSTATE: 54000
+
+Description: The number of attributes in the target list exceeds 1664.
+
+Solution: Reduce the number of attributes in the target list.
+
+GAUSS-00013: "cache lookup failed for type %u"
+
+SQLSTATE: 22P06
+
+Description: The operator is invalid.
+
+Solution: Ensure that the operator in the SQL statement is valid.
+
+GAUSS-00014: "cannot subscript type %s because it is not an array"
+
+SQLSTATE: 42804
+
+Description: A subscript operation is performed on a non-array type.
+
+Solution: Do not perform a subscript operation on a non-array type.
+
+GAUSS-00015: "array subscript must have type integer"
+
+SQLSTATE: 42804
+
+Description: The array subscript is incorrect.
+
+Solution: Ensure that the array subscript is an integer.
+
+GAUSS-00016: "array assignment requires type %s but expression is of type %s"
+
+SQLSTATE: 42804
+
+Description: When you set variables of an array type, variables cannot be converted.
+
+Solution: Reassign values to variables. Provide a conversion function so that variables of an array type can be converted. Obtain related information from the **pg_cast** system catalog.
+
+GAUSS-00017: "unrecognized node type: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00018: "failed to find conversion function from %s to %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00020: "cache lookup failed for function %u"
+
+SQLSTATE: 22P06
+
+Description: The function with the corresponding ID is not found in the system catalog.
+
+Solution: Ensure that no concurrent sessions perform a drop, cancel, or replace operation on the function.
+
+<br/>
+
+## GAUSS-00021 - GAUSS-00030
+
+<br/>
+
+GAUSS-00021: "unsupported pathtype %d in build_coercion_expression"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00022: "cannot cast type %s to %s"
+
+SQLSTATE: 42846
+
+Description: Two types cannot be converted to each other.
+
+Solution: Provide a type conversion function. Obtain related information from the **pg_cast** system catalog.
+
+GAUSS-00024: "argument of %s must not return a set"
+
+SQLSTATE: 42804
+
+Description: A set cannot be returned.
+
+Solution: Ensure that the expression can return a set.
+
+GAUSS-00025: "argument of %s must be type %s, not type %s"
+
+SQLSTATE: 42804
+
+Description: The source and target types are different and cannot be converted.
+
+Solution: Ensure that the source and target types are compatible and can be convertible.
+
+GAUSS-00026: "%s types %s and %s cannot be matched"
+
+SQLSTATE: 42804
+
+Description: The two types do not belong to the same category.
+
+Solution: Check the **typcategory** column in the **pg_type** system catalog for the category of each type.
+
+GAUSS-00027: "%s could not convert type %s to %s"
+
+SQLSTATE: 42846
+
+Description: The source and target types are different and cannot be converted.
+
+Solution: Ensure that the source and target types are compatible and can be convertible.
+
+GAUSS-00028: "arguments declared 'anyelement' are not all alike"
+
+SQLSTATE: 42804
+
+Description: A function uses pseudo-type parameters, but the types of elements in an array are different from the defined ones.
+
+Solution: Ensure that the types of elements in an array are same as the defined ones.
+
+GAUSS-00029: "arguments declared 'anyarray' are not all alike"
+
+SQLSTATE: 42804
+
+Description: A function uses pseudo-type parameters, but the types of elements in an array are different from the defined ones.
+
+Solution: Ensure that the types of elements in an array are same as the defined ones.
+
+GAUSS-00030: "arguments declared 'anyrange' are not all alike"
+
+SQLSTATE: 42804
+
+Description: A function uses pseudo-type parameters, but the types of elements in an array are different from the defined ones.
+
+Solution: Ensure that the types of elements in an array are same as the defined ones.
+
+<br/>
+
+## GAUSS-00031 - GAUSS-00040
+
+<br/>
+
+GAUSS-00031: "argument declared 'anyarray' is not an array but type %s"
+
+SQLSTATE: 42804
+
+Description: The type of the declared parameter is inconsistent with that of the input parameter.
+
+Solution: Use an input parameter of the same type as the declared parameter.
+
+GAUSS-00032: "argument declared 'anyarray' is not consistent with argument declared 'anyelement'"
+
+SQLSTATE: 42804
+
+Description: The array type defined does not match the types of elements in an ANY array.
+
+Solution: Ensure that the array type defined in the query statement and the types of elements in an ANY array are correct.
+
+GAUSS-00033: "argument declared 'anyrange' is not a range but type %s"
+
+SQLSTATE: 42804
+
+Description: The range type defined does not match the types of elements in an ANY range.
+
+Solution: Ensure that the range type defined in the query statement and the types of elements in an ANY range are correct.
+
+GAUSS-00034: "argument declared 'anyrange' is not consistent with argument declared 'anyelement'"
+
+SQLSTATE: 42804
+
+Description: The parameter type is different from the declared parameter type.
+
+Solution: Use a parameter of the declared type.
+
+GAUSS-00035: "could not determine polymorphic type because input has type 'unknown'"
+
+SQLSTATE: 42804
+
+Description: Array element types cannot be identified.
+
+Solution: Ensure that the array element types in the ANY predicate are correct.
+
+GAUSS-00036: "type matched to anynonarray is an array type: %s"
+
+SQLSTATE: 42804
+
+Description: The required type is not array.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-00037: "type matched to anyenum is not an enum type: %s"
+
+SQLSTATE: 42804
+
+Description: The required type is ENUM.
+
+Solution: Ensure that an ENUM-type value is used for the parameter of the ANYENUM type.
+
+GAUSS-00038: "could not find range type for data type %s"
+
+SQLSTATE: 42704
+
+Description: The declared array type is range, but the input value is not of the range type.
+
+Solution: Assign a value of the defined type to the array.
+
+GAUSS-00039: "could not determine polymorphic type because context isn't polymorphic"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00040: "unrecognized castcontext: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-00041 - GAUSS-00050
+
+<br/>
+
+GAUSS-00041: "unrecognized castmethod: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00042: "cache lookup failed for relation %u"
+
+SQLSTATE: XX000
+
+Description: When **ALTER TABLE SET TABLESPACE** is run, the relational table does not exist.
+
+Solution: Modify this operation.
+
+GAUSS-00043: "unsafe use of string constant with Unicode escapes"
+
+SQLSTATE: 0A000
+
+Description: When **standard_conforming_strings** is set to **off**, the string constant is defined as an escape character of unified codes.
+
+Solution: 1. Check whether the escape string in the input statement is correct. 2. Set **standard_conforming_strings** to **on** using **gsql**.
+
+GAUSS-00044: "invalid Unicode escape"
+
+SQLSTATE: 22025
+
+Description: The input statement contains an invalid escape character sequence.
+
+Solution: Check whether a character sequence similar to \uXXXX or \UXXXXXXXXX exists. X indicates a digit (0-9), uppercase letter (A-F), or lowercase letter (a-f).
+
+GAUSS-00045: "unsafe use of \\' in a string literal"
+
+SQLSTATE: 22P06
+
+Description: A string uses an invalid escape character ().
+
+Solution: Correct the invalid escape character () used in the SQL syntax.
+
+GAUSS-00046: "%s at end of input"
+
+SQLSTATE: 42601
+
+Description: The syntax of the terminator in the specified statement is incorrect.
+
+Solution: Ensure that the syntax of the input statement is correct.
+
+GAUSS-00047: "%s at or near '%s'"
+
+SQLSTATE: 42601
+
+Description: Syntax error.
+
+Solution: Correct the syntax of the SQL statement to be executed.
+
+GAUSS-00048: "core_yylex_init() failed: %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00049: "invalid hexadecimal digit"
+
+SQLSTATE: XX000
+
+Description: Invalid format.
+
+Solution: Modify the input SQL statement.
+
+<br/>
+
+## GAUSS-00051 - GAUSS-00060
+
+<br/>
+
+GAUSS-00052: "column '%s' of relation '%s' does not exist"
+
+SQLSTATE: 42703
+
+Description: The column name is empty, incorrectly spelled, or not a column name defined in a relational table.
+
+Solution: Run **\d tblname** to check whether the specified column name is the one specified in the table. If it is not, change it to a valid column name.
+
+GAUSS-00053: "type '%s' does not exist"
+
+SQLSTATE: 42704
+
+Description: A specified type is not found in the **pg_type** system catalog.
+
+Solution: Correct the type used in the statement. (See types defined in the **pg_type** system catalog.)
+
+GAUSS-00054: "type '%s' is only a shell"
+
+SQLSTATE: 42704
+
+Description: No corresponding operation functions are defined in the **pg_type** system catalog for a specified type.
+
+Solution: Check whether the type used in the statement is correct. If it is, use the **CREATE TYPE** statement to define the operation function corresponding to the specified type.
+
+GAUSS-00055: "type modifier cannot be specified for shell type '%s'"
+
+SQLSTATE: 42601
+
+Description: The user-defined type contains typmod.
+
+Solution: Correct the user-defined type, typmod.
+
+GAUSS-00056: "type modifier is not allowed for type '%s'"
+
+SQLSTATE: 42601
+
+Description: The user-defined type contains typmod.
+
+Solution: Correct the user-defined type, typmod.
+
+GAUSS-00057: "type modifiers must be simple constants or identifiers"
+
+SQLSTATE: 42601
+
+Description: The provided type modifier is incorrect.
+
+Solution: A type modifier must be defined as a constant or identifier. Check whether the syntax of the specified type modifier is correct. If it is incorrect, define a valid type modifier.
+
+GAUSS-00058: "collations are not supported by type %s"
+
+SQLSTATE: 42804
+
+Description: The collation does not match the type, and the input is incorrect.
+
+Solution: Modify the input SQL statement.
+
+GAUSS-00059: "typeTypeId() called with NULL type struct"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00060: "invalid type name '%s'"
+
+SQLSTATE: 42601
+
+Description: The specified type is invalid.
+
+Solution: Correct the type used in the statement. (See types defined in the **pg_type** system catalog.)
+
+<br/>
+
+## GAUSS-00061 - GAUSS-00070
+
+<br/>
+
+GAUSS-00061: "unrecognized A_Expr kind: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00062: "column %s.%s does not exist"
+
+SQLSTATE: 42703
+
+Description: The column name is empty, incorrectly spelled, or not a column name defined in a relational table.
+
+Solution: Run **\d tblname** to check whether the specified column name is the one specified in the table. If it is not, change it to a valid column name.
+
+GAUSS-00063: "column '%s' not found in data type %s"
+
+SQLSTATE: 42703
+
+Description: The type of the specified column is incorrectly defined.
+
+Solution: Run **\d tblname** to check whether the type of the column in the table is correct.
+
+GAUSS-00064: "could not identify column '%s' in record data type"
+
+SQLSTATE: 42703
+
+Description: The column does not exist because it cannot be identified using the record data type.
+
+Solution: Ensure that the column exists.
+
+GAUSS-00065: "column notation .%s applied to type %s, which is not a composite type"
+
+SQLSTATE: 42809
+
+Description: A non-composite type member is accessed using a dot (.).
+
+Solution: Do not use a dot (.) to access a non-composite type member.
+
+GAUSS-00066: "row expansion via '*' is not supported here"
+
+SQLSTATE: 0A000
+
+Description: The current context does not support unfolding columns using an asterisk (*).
+
+Solution: Do not use an asterisk (*) to unfold columns in the current context.
+
+GAUSS-00067: "column reference '%s' is ambiguous"
+
+SQLSTATE: 42702
+
+Description: A column is referenced multiple times.
+
+Solution: Do not reference a column multiple times.
+
+GAUSS-00068: "column '%s' does not exist"
+
+SQLSTATE: 42703
+
+Description: The column does not exist.
+
+Solution: Ensure that the column to be used exists in the table definition.
+
+GAUSS-00069: "cross-database references are not implemented: %s"
+
+SQLSTATE: 0A000
+
+Description: An object cannot be referenced from a database to another.
+
+Solution: Do not reference an object from a database to another. For example, do not access an object in Database1 from Database2 using **Database1.schema.object**. The object can be a table, index, or view.
+
+GAUSS-00070: "improper qualified name (too many dotted names): %s"
+
+SQLSTATE: 42601
+
+Description: Excessive dot separators are used. As a result, the name cannot be correctly resolved.
+
+Solution: Reduce the number of dot separators and try again.
+
+<br/>
+
+## GAUSS-00071 - GAUSS-00080
+
+<br/>
+
+GAUSS-00071: "there is no parameter $%d"
+
+SQLSTATE: 42P02
+
+Description: The parameter sequence number is invalid.
+
+Solution: Ensure that the parameter sequence number is within the range.
+
+GAUSS-00072: "NULLIF requires = operator to yield Boolean"
+
+SQLSTATE: 42804
+
+Description: When comparing parameters in the NULLIF expression, the return value of the function used is not of the Boolean type.
+
+Solution: Ensure that the return value of the function is a Boolean type.
+
+GAUSS-00073: "arguments of row IN must all be row expressions"
+
+SQLSTATE: 42601
+
+Description: The parameter in the IN expression is neither of the array type nor a row expression.
+
+Solution: Ensure that the parameter is an array type or a row expression.
+
+GAUSS-00074: "unexpected non-SELECT command in SubLink"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00075: "subquery must return a column"
+
+SQLSTATE: 42601
+
+Description: No columns are returned for a subquery.
+
+Solution: Ensure that at least one column is returned for a subquery.
+
+GAUSS-00076: "subquery must return only one column"
+
+SQLSTATE: 42601
+
+Description: When a subquery is used as a sub-expression, more than one column is returned.
+
+Solution: Ensure that only one column is returned.
+
+GAUSS-00077: "subquery has too many columns"
+
+SQLSTATE: 42601
+
+Description: In a row expression, the number of columns returned for a subquery is more than the number of required columns.
+
+Solution: Ensure that the number of columns returned is the same as the number of required columns.
+
+GAUSS-00078: "subquery has too few columns"
+
+SQLSTATE: 42601
+
+Description: In a row expression, the number of columns returned for a subquery is less than the number of required columns.
+
+Solution: Ensure that the number of columns returned is the same as the number of required columns.
+
+GAUSS-00079: "cannot determine type of empty array"
+
+SQLSTATE: 42P18
+
+Description: The type of an empty array cannot be determined.
+
+Solution: Forcibly convert the data type.
+
+GAUSS-00080: "could not find element type for data type %s"
+
+SQLSTATE: 42704
+
+Description: The type of an element in the array is invalid.
+
+Solution: Ensure that the type of an element stored in the array is the same as the specified one.
+
+<br/>
+
+## GAUSS-00081 - GAUSS-00090
+
+<br/>
+
+GAUSS-00081: "unnamed XML attribute value must be a column reference"
+
+SQLSTATE: 42601
+
+Description: The unnamed XML attribute values must be referenced by a column.
+
+Solution: Modify the input SQL statement.
+
+GAUSS-00082: "XML attribute name '%s' appears more than once"
+
+SQLSTATE: 42601
+
+Description: A duplicate column exists in XMLELEMENT.
+
+Solution: Modify the input SQL statement.
+
+GAUSS-00083: "cannot cast XMLSERIALIZE result to %s"
+
+SQLSTATE: 42846
+
+Description: The XMLSERIALIZE type is converted to another type.
+
+Solution: Ensure that types can be converted.
+
+GAUSS-00084: "unrecognized booltesttype: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00085: "WHERE CURRENT OF clause not yet supported"
+
+SQLSTATE: 54001
+
+Description: The **WHERE CURRENT OF** syntax is used, which is not supported.
+
+Solution: Do not use the **WHERE CURRENT OF** syntax.
+
+GAUSS-00086: "unequal number of entries in row expressions"
+
+SQLSTATE: 42601
+
+Description: In a row expression, the number of parameters on the right and that on the left of the equal to (et) operator are different.
+
+Solution: Ensure that the numbers are the same.
+
+GAUSS-00087: "cannot compare rows of zero length"
+
+SQLSTATE: 0A000
+
+Description: The lengths of rows to be compared are zero.
+
+Solution: Ensure that the lengths are not zero.
+
+GAUSS-00088: "row comparison operator must yield type Boolean, not type %s"
+
+SQLSTATE: 42804
+
+Description: The value returned after row expression comparison is not a Boolean type.
+
+Solution: Ensure that the value returned is a Boolean type.
+
+GAUSS-00089: "row comparison operator must not return a set"
+
+SQLSTATE: 42804
+
+Description: The value returned after row expression comparison is a set.
+
+Solution: Ensure that the value returned is not a set.
+
+GAUSS-00090: "could not determine interpretation of row comparison operator %s"
+
+SQLSTATE: 0A000
+
+Description: The row comparison operator cannot be found.
+
+Solution: Ensure that the row comparison operator to be used exists.
+
+<br/>
+
+## GAUSS-00091 - GAUSS-00100
+
+<br/>
+
+GAUSS-00091: "IS DISTINCT FROM requires = operator to yield Boolean"
+
+SQLSTATE: 42804
+
+Description: In the **IS DISTINCT FROM** statement, the value returned for the operator used for deduplication is not of the Boolean type.
+
+Solution: Ensure that the value returned is a Boolean type.
+
+GAUSS-00092: "collation mismatch between implicit collations '%s' and '%s'"
+
+SQLSTATE: 42P21
+
+Description: Two character sets cannot be converted in implicit mode.
+
+Solution: Ensure that two character sets to be converted are compatible.
+
+GAUSS-00093: "collation mismatch between explicit collations '%s' and '%s'"
+
+SQLSTATE: 42P21
+
+Description: Two character sets cannot be converted in explicit mode.
+
+Solution: Ensure that two character sets to be converted are compatible.
+
+GAUSS-00094: "table reference '%s' is ambiguous"
+
+SQLSTATE: 42P09
+
+Description: Table reference is ambiguous because duplicate table names exist.
+
+Solution: Provide a specific table name when referencing a table.
+
+GAUSS-00095: "table reference %u is ambiguous"
+
+SQLSTATE: 42P09
+
+Description: Table reference is ambiguous because duplicate table names exist.
+
+Solution: Provide a specific table name when referencing a table.
+
+GAUSS-00096: "table name '%s' specified more than once"
+
+SQLSTATE: 42712
+
+Description: In the **FROM** clause, the same table is used multiple times without an alias.
+
+Solution: Specify an alias for the table so that it can be used multiple times.
+
+GAUSS-00097: "RTE not found (internal error)"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00098: "bad levelsup for CTE '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00099: "could not find CTE '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/10-GAUSS-00901-GAUSS-01000.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/10-GAUSS-00901-GAUSS-01000.md
new file mode 100644
index 0000000000000000000000000000000000000000..fb3eb7551d0c6b2e47e6d11c96e381451b66a7f1
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/10-GAUSS-00901-GAUSS-01000.md
@@ -0,0 +1,756 @@
+---
+title: GAUSS-00901 - GAUSS-01000
+summary: GAUSS-00901 - GAUSS-01000
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-00901 - GAUSS-01000
+
+<br/>
+
+## GAUSS-00901 - GAUSS-00910
+
+<br/>
+
+GAUSS-00901: "tables in ALTER TABLE EXCHANGE PARTITION must have the same column/row storage"
+
+SQLSTATE: 0A000
+
+Description: Tables in the **ALTER TABLE EXCHANGE PARTITION** statement use both row and column storage.
+
+Solution: Ensure that tables specified in the **ALTER TABLE EXCHANGE PARTITION** statement use the same storage mode.
+
+GAUSS-00902: "tables in ALTER TABLE EXCHANGE PARTITION must have the same type of compress"
+
+SQLSTATE: 0A000
+
+Description: Tables in the **ALTER TABLE EXCHANGE PARTITION** statement use different compression types.
+
+Solution: Ensure that tables in the **ALTER TABLE EXCHANGE PARTITION** statement have the same compression type.
+
+GAUSS-00903: "tables in ALTER TABLE EXCHANGE PARTITION must have the same number of columns"
+
+SQLSTATE: 0A000
+
+Description: Tables in the **ALTER TABLE EXCHANGE PARTITION** statement have different numbers of columns.
+
+Solution: Ensure that tables in the **ALTER TABLE EXCHANGE PARTITION** statement have the same number of columns.
+
+GAUSS-00904: "column name mismatch in ALTER TABLE EXCHANGE PARTITION"
+
+SQLSTATE: 0A000
+
+Description: Tables in the **ALTER TABLE EXCHANGE PARTITION** have different column names.
+
+Solution: Ensure that tables in the **ALTER TABLE EXCHANGE PARTITION** statement have the same column name.
+
+GAUSS-00905: "column type or size mismatch in ALTER TABLE EXCHANGE PARTITION"
+
+SQLSTATE: 0A000
+
+Description: Tables in the **ALTER TABLE EXCHANGE PARTITION** statement have different column types or sizes.
+
+Solution: Ensure that tables in the **ALTER TABLE EXCHANGE PARTITION** statement have the same column type and size.
+
+GAUSS-00906: "column not null constraint mismatch in ALTER TABLE EXCHANGE PARTITION"
+
+SQLSTATE: 0A000
+
+Description: Tables in the **ALTER TABLE EXCHANGE PARTITION** statement have different NOT NULL column attributes.
+
+Solution: Ensure that tables in the **ALTER TABLE EXCHANGE PARTITION** statement have the same NOT NULL column attribute.
+
+GAUSS-00907: "column default constraint mismatch in ALTER TABLE EXCHANGE PARTITION"
+
+SQLSTATE: 0A000
+
+Description: Tables in the **ALTER TABLE EXCHANGE PARTITION** statement have different default column constraints.
+
+Solution: Ensure that tables in the **ALTER TABLE EXCHANGE PARTITION** statement have the same default column constraint.
+
+GAUSS-00908: "column collation mismatch in ALTER TABLE EXCHANGE PARTITION"
+
+SQLSTATE: 0A000
+
+Description: Tables in the **ALTER TABLE EXCHANGE PARTITION** statement have different column orders.
+
+Solution: Ensure that tables in the **ALTER TABLE EXCHANGE PARTITION** statement have the same column order.
+
+GAUSS-00909: "column storage mismatch in ALTER TABLE EXCHANGE PARTITION"
+
+SQLSTATE: 0A000
+
+Description: Tables in the **ALTER TABLE EXCHANGE PARTITION** statement have different column storage settings.
+
+Solution: Ensure that tables in the **ALTER TABLE EXCHANGE PARTITION** statement have the same column storage setting.
+
+GAUSS-00910: "the type of column compress mismatch in ALTER TABLE EXCHANGE PARTITION"
+
+SQLSTATE: 0A000
+
+Description: Tables in the **ALTER TABLE EXCHANGE PARTITION** statement have different column compression types.
+
+Solution: Ensure that tables in the **ALTER TABLE EXCHANGE PARTITION** statement have the same compression type.
+
+<br/>
+
+## GAUSS-00911 - GAUSS-00920
+
+<br/>
+
+GAUSS-00911: "constraint mismatch in ALTER TABLE EXCHANGE PARTITION"
+
+SQLSTATE: 0A000
+
+Description: Tables in the **ALTER TABLE EXCHANGE PARTITION** statement have different column constraints.
+
+Solution: Ensure that tables in the **ALTER TABLE EXCHANGE PARTITION** statement have the same column constraint.
+
+GAUSS-00912: "distribute mismatch for tables in ALTER TABLE EXCHANGE PARTITION"
+
+SQLSTATE: 0A000
+
+Description: Tables in the **ALTER TABLE EXCHANGE PARTITION** statement have different column distribution settings.
+
+Solution: Ensure that tables in the **ALTER TABLE EXCHANGE PARTITION** statement have the same column distribution setting.
+
+GAUSS-00913: "tables in ALTER TABLE EXCHANGE PARTITION must have the same number of indexs"
+
+SQLSTATE: 0A000
+
+Description: Tables in the **ALTER TABLE EXCHANGE PARTITION** statement have different numbers of indexes.
+
+Solution: Ensure that tables in the **ALTER TABLE EXCHANGE PARTITION** statement have the same number of indexes.
+
+GAUSS-00914: "index mismatch for tables in ALTER TABLE EXCHANGE PARTITION"
+
+SQLSTATE: 0A000
+
+Description: Tables in the **ALTER TABLE EXCHANGE PARTITION** statement have different indexes.
+
+Solution: Ensure that tables in the **ALTER TABLE EXCHANGE PARTITION** statement have the same index.
+
+GAUSS-00915: "some rows in table do not qualify for specified partition"
+
+SQLSTATE: 0A000
+
+Description: When **SPLIT PARTITION** is run, some rows in the tables cannot be split.
+
+Solution: Locate the cause.
+
+GAUSS-00916: "the number of resulting partitions must be more than one"
+
+SQLSTATE: 42601
+
+Description: The number of specified partitions is less than two when one partition is split into multiple partitions.
+
+Solution: Ensure that the number of specified partitions is no less than two.
+
+GAUSS-00917: "the bound of the first resulting partition is too low"
+
+SQLSTATE: 42601
+
+Description: Partitioning failed because the first partition border value is too low.
+
+Solution: Ensure that the SPLIT PARTITION operation is correct.
+
+GAUSS-00918: "the bound of resulting partition '%s' is too low"
+
+SQLSTATE: 42601
+
+Description: Partitioning failed because the partition border value is too low.
+
+Solution: Ensure that the SPLIT PARTITION operation is correct.
+
+GAUSS-00919: "the bound of the last resulting partition is not equal with specified partition bound"
+
+SQLSTATE: 42601
+
+Description: Partitioning failed because the last border value is inconsistent with the specific one.
+
+Solution: Ensure that the SPLIT PARTITION operation is correct.
+
+GAUSS-00920: "number of boundary items NOT EQUAL to number of partition keys"
+
+SQLSTATE: 42601
+
+Description: Partition failed because the number of specified partition key attributes is inconsistent with that of original partition key attributes.
+
+Solution: Ensure that the SPLIT PARTITION operation is correct.
+
+<br/>
+
+## GAUSS-00921 - GAUSS-00930
+
+<br/>
+
+GAUSS-00921: "split point is too low"
+
+SQLSTATE: 0A000
+
+Description: After SPLIT PARTITION is run, the split point value is smaller than the border value of the previous partition.
+
+Solution: Ensure that the SPLIT PARTITION operation is correct.
+
+GAUSS-00922: "split point is too high"
+
+SQLSTATE: 0A000
+
+Description: After SPLIT PARTITION is run, the split point value is greater than the border value of the next partition.
+
+Solution: Ensure that the SPLIT PARTITION operation is correct.
+
+GAUSS-00923: "resulting partition '%s' name conflicts with that of an existing partition"
+
+SQLSTATE: 42710
+
+Description: After SPLIT PARTITION is run, the partition names conflict with the existing partition names.
+
+Solution: Rename the partitions.
+
+GAUSS-00924: "number of boundary items NOT EQUAL to number of partition keys"
+
+SQLSTATE: 42601
+
+Description: Partition failed because the number of specified partition key attributes is inconsistent with that of original partition key attributes.
+
+Solution: Ensure that the SPLIT PARTITION operation is correct.
+
+GAUSS-00925: "cache lookup failed for toast table: %u"
+
+SQLSTATE: XX000
+
+Description: The required toast table is not found.
+
+Solution: The system catalog is abnormal. Contact technical support.
+
+GAUSS-00926: "cache lookup failed for cuDesc table: %u"
+
+SQLSTATE: XX000
+
+Description: The required cuDesc table is not found.
+
+Solution: The system catalog is abnormal. Contact technical support.
+
+GAUSS-00927: "cache lookup failed for delta table: %u"
+
+SQLSTATE: XX000
+
+Description: The required delta table is not found.
+
+Solution: The system catalog is abnormal. Contact technical support.
+
+<br/>
+
+## GAUSS-00931 - GAUSS-00940
+
+<br/>
+
+GAUSS-00935: "cache lookup failed for relation %u"
+
+SQLSTATE: 02000
+
+Description: When **ALTER TABLE SET TABLESPACE** is run, the relational table does not exist.
+
+Solution: Modify this operation.
+
+GAUSS-00936: "SQL function cannot return shell type %s"
+
+SQLSTATE: 42P13
+
+Description: The SQL function does not return a shared variable.
+
+Solution: Modify the SQL function and do not use a shared variable as a return value.
+
+GAUSS-00937: "SQL function cannot accept shell type %s"
+
+SQLSTATE: 42P13
+
+Description: The SQL function does not use a shared variable as the function parameter.
+
+Solution: Modify the SQL function, and do not use a shared variable as a function parameter.
+
+GAUSS-00938: "type %s does not exist"
+
+SQLSTATE: 42704
+
+Description: The data type does not exist.
+
+Solution: Check the function or storage process and verify that the parameter data type is correct.
+
+GAUSS-00940: "VARIADIC parameter must be the last input parameter"
+
+SQLSTATE: 42P13
+
+Description:**VARIADIC** must be put at the end of input parameters.
+
+Solution: Put **VARIADIC** at the end of input parameters.
+
+<br/>
+
+## GAUSS-00941 - GAUSS-00950
+
+<br/>
+
+GAUSS-00941: "VARIADIC parameter must be an array"
+
+SQLSTATE: 42P13
+
+Description:**VARIADIC** parameters must be of the array type.
+
+Solution: Use variables of the array type as **VARIADIC** parameters.
+
+GAUSS-00942: "parameter name '%s' used more than once"
+
+SQLSTATE: 42P13
+
+Description: A parameter name is used more than once in the parameter list.
+
+Solution: Use different parameter names.
+
+GAUSS-00943: "only input parameters can have default values"
+
+SQLSTATE: 42P13
+
+Description: A default value exists only when the parameter is set.
+
+Solution: Only define a default value for the input parameter.
+
+GAUSS-00944: "cannot use table references in parameter default value"
+
+SQLSTATE: 42P10
+
+Description: Variables cannot be used as default values of parameters, such as tables, columns, and CurrentOf expressions.
+
+Solution: Do not use variables as default values.
+
+GAUSS-00945: "cannot use subquery in parameter default value"
+
+SQLSTATE: 0A000
+
+Description: Subqueries cannot be used as default values of parameters.
+
+Solution: Do not use subqueries as default values.
+
+GAUSS-00946: "cannot use aggregate function in parameter default value"
+
+SQLSTATE: 42803
+
+Description: Aggregate functions cannot be used as default values of parameters.
+
+Solution: Do not use aggregate functions as default values.
+
+GAUSS-00947: "cannot use window function in parameter default value"
+
+SQLSTATE: 42P20
+
+Description: Window functions cannot be used as default values of parameters.
+
+Solution: Do not use window functions as default values.
+
+GAUSS-00948: "invalid volatility '%s'"
+
+SQLSTATE: XX000
+
+Description: The type of the volatile function is invalid.
+
+Solution: The system catalog is abnormal. Contact technical support.
+
+GAUSS-00949: "no function body specified"
+
+SQLSTATE: 42P13
+
+Description: No function body is defined.
+
+Solution: Ensure that the function body is defined.
+
+GAUSS-00950: "no language specified"
+
+SQLSTATE: 42P13
+
+Description: No language type of the function is defined, such as C/PLPGSQL/SQL.
+
+Solution: Define the language type such as C/PLPGSQL/SQL.
+
+<br/>
+
+## GAUSS-00951 - GAUSS-00960
+
+<br/>
+
+GAUSS-00951: "COST must be positive"
+
+SQLSTATE: 22023
+
+Description: The value of **COST** must be a positive number.
+
+Solution: Ensure that the value of **COST** is a positive number.
+
+GAUSS-00952: "ROWS must be positive"
+
+SQLSTATE: 22023
+
+Description: The value of **ROWS** must be a positive number.
+
+Solution: Ensure that the value of **ROWS** is a positive number.
+
+GAUSS-00953: "only one AS item needed for language '%s'"
+
+SQLSTATE: 42P13
+
+Description: Only one AS clause is required.
+
+Solution: Ensure that only one AS clause exists.
+
+GAUSS-00954: "language '%s' does not exist"
+
+SQLSTATE: 42704
+
+Description: The language does not exist.
+
+Solution: Check the function definition and ensure that the language type of the function is supported by the database, such as PL/pgSQL and SQL.
+
+GAUSS-00955: "only system admin can define a leakproof function"
+
+SQLSTATE: 42501
+
+Description: Only the system administrator can define a leakproof function.
+
+Solution: Create a leakproof function as a system administrator.
+
+GAUSS-00957: "function result type cannot be a view."
+
+SQLSTATE: 42P13
+
+Description: The return type of the function cannot be a view.
+
+Solution: Check the function definition, and do not use a view as the return type of the function.
+
+GAUSS-00958: "ROWS is not applicable when function does not return a set"
+
+SQLSTATE: 22023
+
+Description:**ROWS** is specified, but the function does not return a result set.
+
+Solution: Specify **ROWS** only for functions that return result sets.
+
+GAUSS-00959: "cache lookup failed for pg_aggregate tuple for function %u"
+
+SQLSTATE: XX000
+
+Description: The required aggregate function is not found in the **PG\_AGGREGATE** system catalog.
+
+Solution: The system catalog is abnormal. Contact technical support.
+
+GAUSS-00960: "function %u doesn't return OPAQUE"
+
+SQLSTATE: XX000
+
+Description: The function return type is not opaque.
+
+Solution: Check whether the function return type is correct.
+
+<br/>
+
+## GAUSS-00961 - GAUSS-00970
+
+<br/>
+
+GAUSS-00962: "source data type %s is a pseudo-type"
+
+SQLSTATE: 42809
+
+Description: The source data type is a pseudo type.
+
+Solution: Check the CAST function to be created and ensure that the source data type is not a pseudo type.
+
+GAUSS-00963: "target data type %s is a pseudo-type"
+
+SQLSTATE: 42809
+
+Description: The target data type is a pseudo type.
+
+Solution: Check the CAST function to be created and ensure that the target data type is not a pseudo type.
+
+GAUSS-00964: "must be owner of type %s or type %s"
+
+SQLSTATE: 42501
+
+Description: The user executing this statement is not the owner of the source type and target type.
+
+Solution: Check the SQL statement and ensure that the user is the owner of the source type and target type.
+
+GAUSS-00965: "cast function must take one to three arguments"
+
+SQLSTATE: 42P17
+
+Description: The CAST function does not specify one to three parameters.
+
+Solution: Ensure that the CAST function specifies one to three parameters.
+
+GAUSS-00966: "argument of cast function must match or be binary-coercible from source data type"
+
+SQLSTATE: 42P17
+
+Description: The parameters of the CAST function neither match the source data type nor are compatible with the binary.
+
+Solution: Ensure that the parameters of the CAST function match the source data type or are compatible with the binary.
+
+GAUSS-00967: "second argument of cast function must be type integer"
+
+SQLSTATE: 42P17
+
+Description: The second parameter of the CAST function is not of an integer type.
+
+Solution: Ensure that the second parameter of the CAST function is of an integer type.
+
+GAUSS-00968: "third argument of cast function must be type Boolean"
+
+SQLSTATE: 42P17
+
+Description: The third parameter of the CAST function is not of a Boolean type.
+
+Solution: Ensure that the third parameter of the CAST function is of a Boolean type.
+
+GAUSS-00969: "return data type of cast function must match or be binary-coercible to target data type"
+
+SQLSTATE: 42P17
+
+Description: The return data type of the CAST function neither matches the target data type nor is binary-coercible to target data type.
+
+Solution: Ensure that the return data type of the CAST function matches or is binary-coercible to target data type.
+
+GAUSS-00970: "cast function must not be volatile"
+
+SQLSTATE: 42P17
+
+Description: The CAST function is volatile.
+
+Solution: Ensure that the CAST function is operating properly.
+
+<br/>
+
+## GAUSS-00971 - GAUSS-00980
+
+<br/>
+
+GAUSS-00971: "cast function must not be an aggregate function"
+
+SQLSTATE: 42P17
+
+Description: The function is an aggregate function.
+
+Solution: Ensure that the CAST function is not an aggregate function.
+
+GAUSS-00972: "cast function must not be a window function"
+
+SQLSTATE: 42P17
+
+Description: The function is a window function.
+
+Solution: Ensure that the function is not a window function.
+
+GAUSS-00973: "cast function must not return a set"
+
+SQLSTATE: 42P17
+
+Description: The function returns a result set.
+
+Solution: Ensure that the CAST function does not return a result set.
+
+GAUSS-00974: "must be system admin to create a cast WITHOUT FUNCTION"
+
+SQLSTATE: 42501
+
+Description: The **WITHOUT FUNCTION** attribute of the CAST function can be specified only by the system administrator.
+
+Solution: Specify the **WITHOUT FUNCTION** attribute as a system administrator while creating the CAST function.
+
+GAUSS-00975: "source and target data types are not physically compatible"
+
+SQLSTATE: 42P17
+
+Description: The source and target data types are not physically compatible. (Physical compatibility means source and target data types of **typlen**, **typbyval**, and **typalign** in the **pg_type** system catalog are the same.)
+
+Solution: Ensure that the source and target data types are physically compatible.
+
+GAUSS-00976: "composite data types are not binary-compatible"
+
+SQLSTATE: 42P17
+
+Description: The composite data type is not binary-compatible and cannot be converted.
+
+Solution: While creating a CAST function, do not use the composite data type as the source or target data type.
+
+GAUSS-00977: "enum data types are not binary-compatible"
+
+SQLSTATE: 42P17
+
+Description: The enum data type is not binary-compatible and cannot be converted.
+
+Solution: While creating a CAST function, do not use the enum data type as the source or target data type.
+
+GAUSS-00978: "array data types are not binary-compatible"
+
+SQLSTATE: 42P17
+
+Description: The array data type is not binary-compatible and cannot be converted.
+
+Solution: While creating a CAST function, do not use the array data type as the source or target data type.
+
+GAUSS-00979: "domain data types must not be marked binary-compatible"
+
+SQLSTATE: 42P17
+
+Description: The domain data types are not binary-compatible and cannot be converted.
+
+Solution: While creating a CAST function, do not use the domain data type as the source or target data type.
+
+GAUSS-00980: "source data type and target data type are the same"
+
+SQLSTATE: 42P17
+
+Description: The source and target data types are the same.
+
+Solution: While creating a CAST, ensure that the source and target data types are different.
+
+<br/>
+
+## GAUSS-00981 - GAUSS-00990
+
+<br/>
+
+GAUSS-00981: "unrecognized CoercionContext: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00982: "cast from type %s to type %s already exists"
+
+SQLSTATE: 42710
+
+Description: The CAST function used for converting data from the source data type to the target data type already exists.
+
+Solution: Do not create the CAST function again.
+
+GAUSS-00983: "cast from type %s to type %s does not exist"
+
+SQLSTATE: 42704
+
+Description: The CAST function used for converting data from the source data type to the target data type does not exist.
+
+Solution: Check the **pg_cast** system catalog to see whether the CAST function exists. If it does not exist, create it or rewrite the SQL statement to avoid using it.
+
+GAUSS-00984: "could not find tuple for cast %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00985: "function '%s' already exists in schema '%s'"
+
+SQLSTATE: 42723
+
+Description: The function in the target schema already exists.
+
+Solution: Ensure that no function with the same name has been created in the target schema.
+
+GAUSS-00986: "failed to change schema dependency for function '%s'"
+
+SQLSTATE: XX000
+
+Description: Failed to change the schema dependency of the function.
+
+Solution: The system catalog is abnormal. Contact technical support.
+
+GAUSS-00987: "no inline code specified"
+
+SQLSTATE: 42601
+
+Description: Inline statements are not specified in an anonymous block.
+
+Solution: Check the syntax of the anonymous block to ensure that it contains inline statements.
+
+GAUSS-00988: "language '%s' does not support inline code execution"
+
+SQLSTATE: 0A000
+
+Description: Inline code cannot be executed for this language.
+
+Solution: Use a common function or another language.
+
+GAUSS-00989: "source encoding '%s' does not exist"
+
+SQLSTATE: 42704
+
+Description: The source encoding does not exist.
+
+Solution: Ensure that the source encoding exists in the system.
+
+GAUSS-00990: "destination encoding '%s' does not exist"
+
+SQLSTATE: 42704
+
+Description: The target encoding does not exist.
+
+Solution: Ensure that the target encoding exists in the system.
+
+<br/>
+
+## GAUSS-00991 - GAUSS-01000
+
+<br/>
+
+GAUSS-00991: "encoding conversion function %s must return type 'void'"
+
+SQLSTATE: 42P17
+
+Description: The code conversion function can only return void.
+
+Solution: Check the code conversion function to ensure that the function only returns void.
+
+GAUSS-00992: "cache lookup failed for conversion %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00994: "extra data after last expected column"
+
+SQLSTATE: 22P04
+
+Description: The number of columns in the data file exceeds that in the table.
+
+Solution: Ensure that the data file and the table have the same number of columns.
+
+GAUSS-00995: "field position covers previous field"
+
+SQLSTATE: 22P04
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00998: "%s"
+
+SQLSTATE: 42000
+
+Description: Syntax error.
+
+Solution: Ensure that the SQL statement syntax is correct.
+
+GAUSS-01000: "type '%s' already exists"
+
+SQLSTATE: 42710
+
+Description: The data type already exists.
+
+Solution: Check whether the data type exists in the **pg_type** system catalog.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/11-GAUSS-01001-GAUSS-01100.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/11-GAUSS-01001-GAUSS-01100.md
new file mode 100644
index 0000000000000000000000000000000000000000..3a5d78982aa36b609508eb256185451ad591c709
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/11-GAUSS-01001-GAUSS-01100.md
@@ -0,0 +1,812 @@
+---
+title: GAUSS-01001 - GAUSS-01100
+summary: GAUSS-01001 - GAUSS-01100
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-01001 - GAUSS-01100
+
+<br/>
+
+## GAUSS-01001 - GAUSS-01010
+
+<br/>
+
+GAUSS-01001: "invalid type category '%s': must be simple ASCII"
+
+SQLSTATE: 22023
+
+Description: The type category is invalid.
+
+Solution: Ensure that the category name consists of simple ASCII characters (ACII value from 22 to 126).
+
+GAUSS-01002: "array element type cannot be %s"
+
+SQLSTATE: 42804
+
+Description: The array element type cannot be the pseudo type.
+
+Solution: Do not use the pseudo type as the array element type.
+
+GAUSS-01003: "alignment '%s' not recognized"
+
+SQLSTATE: 22023
+
+Description: Invalid alignment parameter.
+
+Solution: Ensure that the alignment parameters in the data type definition are valid.
+
+GAUSS-01004: "storage '%s' not recognized"
+
+SQLSTATE: 22023
+
+Description: Invalid storage parameter.
+
+Solution: Ensure that the storage parameters in the data type definition are valid.
+
+GAUSS-01005: "type input function must be specified"
+
+SQLSTATE: 42P17
+
+Description: No input function is specified for the data type.
+
+Solution: Specify an input function.
+
+GAUSS-01006: "type output function must be specified"
+
+SQLSTATE: 42P17
+
+Description: No output function is specified for the data type.
+
+Solution: Specify an output function.
+
+GAUSS-01007: "type modifier output function is useless without a type modifier input function"
+
+SQLSTATE: 42P17
+
+Description: Only a typmod_out function is specified for the data type.
+
+Solution: Specify both typmod_in and typmod_out functions.
+
+GAUSS-01008: "type input function %s must return type %s"
+
+SQLSTATE: 42P17
+
+Description: The return type of the input function is not specified.
+
+Solution: Specify the return type of the input function.
+
+GAUSS-01009: "type output function %s must return type 'cstring'"
+
+SQLSTATE: 42P17
+
+Description: The return type of the output function is not specified.
+
+Solution: Specify the return type of the output function.
+
+GAUSS-01010: "type receive function %s must return type %s"
+
+SQLSTATE: 42P17
+
+Description: The return type of the receive function is not specified.
+
+Solution: Specify the return type of the receive function.
+
+<br/>
+
+## GAUSS-01011 - GAUSS-01020
+
+<br/>
+
+GAUSS-01011: "type send function %s must return type 'bytea'"
+
+SQLSTATE: 42P17
+
+Description: The return type of the send function is not specified.
+
+Solution: Specify the return type of the send function.
+
+GAUSS-01012: "'%s' is not a valid base type for a domain"
+
+SQLSTATE: 42804
+
+Description: The base type of the domain is invalid.
+
+Solution: Ensure that the base type of the domain is b, d, e, or r.
+
+GAUSS-01013: "multiple default expressions"
+
+SQLSTATE: 42601
+
+Description: Multiple default expressions are specified.
+
+Solution: Define only one default expression.
+
+GAUSS-01014: "conflicting NULL/NOT NULL constraints"
+
+SQLSTATE: 42601
+
+Description: NULL/NOT NULL constraints conflict.
+
+Solution: Ensure that NULL/NOTNULL constraints do not conflict.
+
+GAUSS-01015: "CHECK constraints for domains cannot be marked NO INHERIT"
+
+SQLSTATE: 42P17
+
+Description: The check constraint of a domain is set to **NO INHERIT**.
+
+Solution: Do not set the check constraint to **NO INHERIT**.
+
+GAUSS-01016: "unique constraints not possible for domains"
+
+SQLSTATE: 42000
+
+Description: The domain definition contains a unique constraint.
+
+Solution: Check the domain definition statement to ensure that no unique constraint exists.
+
+GAUSS-01017: "primary key constraints not possible for domains"
+
+SQLSTATE: 42601
+
+Description: The domain definition contains a primary key constraint.
+
+Solution: Check the domain definition statement to ensure that no primary key constraint exists.
+
+GAUSS-01018: "exclusion constraints not possible for domains"
+
+SQLSTATE: 42601
+
+Description: The domain definition contains an exclusive constraint.
+
+Solution: Check the domain definition statement to ensure that no exclusive constraint exists.
+
+GAUSS-01019: "foreign key constraints not possible for domains"
+
+SQLSTATE: 42601
+
+Description: The domain definition contains a foreign key constraint.
+
+Solution: Check the domain definition statement to ensure that no foreign key constraint exists.
+
+GAUSS-01020: "specifying constraint deferrability not supported for domains"
+
+SQLSTATE: 0A000
+
+Description: The domain contains the deferrability attribute of a constraint.
+
+Solution: Delete the deferrability attribute from the domain definition statement.
+
+<br/>
+
+## GAUSS-01021 - GAUSS-01030
+
+<br/>
+
+GAUSS-01021: "unrecognized constraint subtype: %d"
+
+SQLSTATE: XX000
+
+Description: The constraint type is invalid.
+
+Solution: Check whether the constraint type defined in the SQL statement is correct.
+
+GAUSS-01022: "%s is not an enum"
+
+SQLSTATE: 42809
+
+Description: The object is not an enum type.
+
+Solution: Ensure that the object is an enum type.
+
+GAUSS-01024: "type attribute 'subtype' is required"
+
+SQLSTATE: 42601
+
+Description: The subtype attribute of the type is not specified.
+
+Solution: Add the subtype attribute to the SQL statement.
+
+GAUSS-01025: "range subtype cannot be %s"
+
+SQLSTATE: 42804
+
+Description: Pseudo type.
+
+Solution: Ensure that range subtype is not the pseudo type.
+
+GAUSS-01026: "range collation specified but subtype does not support collation"
+
+SQLSTATE: 42809
+
+Description: Range collation is specified, but the subtype does not support collation.
+
+Solution: If collation is specified, ensure that the subtype supports collation.
+
+GAUSS-01027: "typmod_in function %s must return type 'integer'"
+
+SQLSTATE: 42P17
+
+Description: The return type of the typmod_in function is not integer.
+
+Solution: Check the tymod_in function and ensure that the return type is integer.
+
+GAUSS-01028: "typmod_out function %s must return type 'cstring'"
+
+SQLSTATE: 42P17
+
+Description: The return type of the typmod_out function is not cstring.
+
+Solution: Check the typmod_out function and ensure that the return type is cstring.
+
+GAUSS-01029: "type analyze function %s must return type 'Boolean'"
+
+SQLSTATE: 42P17
+
+Description: The return type of the analyze function is not Boolean.
+
+Solution: Check the analyze function and ensure that the return type is Boolean.
+
+GAUSS-01030: "operator class '%s' does not accept data type %s"
+
+SQLSTATE: 42804
+
+Description: The operator class does not support this data type.
+
+Solution: Ensure that the subtype matches the operator class.
+
+<br/>
+
+## GAUSS-01031 - GAUSS-01040
+
+<br/>
+
+GAUSS-01031: "data type %s has no default operator class for access method '%s'"
+
+SQLSTATE: 42704
+
+Description: Syntax blacklisted.
+
+Solution: Do not use the syntax.
+
+GAUSS-01032: "range canonical function %s must return range type"
+
+SQLSTATE: 42P17
+
+Description: Syntax blacklisted.
+
+Solution: Do not use the syntax.
+
+GAUSS-01033: "range canonical function %s must be immutable"
+
+SQLSTATE: 42P17
+
+Description: Syntax blacklisted.
+
+Solution: Do not use the syntax.
+
+GAUSS-01034: "range subtype diff function %s must return type double precision"
+
+SQLSTATE: 42P17
+
+Description: Syntax blacklisted.
+
+Solution: Do not use the syntax.
+
+GAUSS-01035: "range subtype diff function %s must be immutable"
+
+SQLSTATE: 42P17
+
+Description: Syntax blacklisted.
+
+Solution: Do not use the syntax.
+
+GAUSS-01036: "column '%s' of table '%s' contains null values"
+
+SQLSTATE: 23502
+
+Description: Syntax blacklisted.
+
+Solution: Do not use the syntax.
+
+GAUSS-01037: "constraint '%s' of domain '%s' does not exist"
+
+SQLSTATE: 42704
+
+Description: Syntax blacklisted.
+
+Solution: Do not use the syntax.
+
+GAUSS-01038: "constraint '%s' of domain '%s' is not a check constraint"
+
+SQLSTATE: 42809
+
+Description: Syntax blacklisted.
+
+Solution: Do not use the syntax.
+
+GAUSS-01039: "column '%s' of table '%s' contains values that violate the new constraint"
+
+SQLSTATE: 23514
+
+Description: Syntax blacklisted.
+
+Solution: Do not use the syntax.
+
+GAUSS-01040: "%s is not a domain"
+
+SQLSTATE: 42809
+
+Description: Syntax blacklisted.
+
+Solution: Do not use the syntax.
+
+<br/>
+
+## GAUSS-01041 - GAUSS-01050
+
+<br/>
+
+GAUSS-01041: "constraint '%s' for domain '%s' already exists"
+
+SQLSTATE: 42710
+
+Description: Syntax blacklisted.
+
+Solution: Syntax blacklisted.
+
+GAUSS-01042: "cannot use table references in domain check constraint"
+
+SQLSTATE: 42P10
+
+Description: Syntax blacklisted.
+
+Solution: Syntax blacklisted.
+
+GAUSS-01043: "cannot use subquery in check constraint"
+
+SQLSTATE: 0A000
+
+Description: Syntax blacklisted.
+
+Solution: Syntax blacklisted.
+
+GAUSS-01044: "cannot use aggregate function in check constraint"
+
+SQLSTATE: 42803
+
+Description: Syntax blacklisted.
+
+Solution: Syntax blacklisted.
+
+GAUSS-01045: "cannot use window function in check constraint"
+
+SQLSTATE: 42P20
+
+Description: Syntax blacklisted.
+
+Solution: Syntax blacklisted.
+
+GAUSS-01046: "domain '%s' constraint '%s' has NULL conbin"
+
+SQLSTATE: XX000
+
+Description: The constraint attribute is null.
+
+Solution: The system catalog is abnormal. Contact technical support.
+
+GAUSS-01047: "'%s' is not a domain"
+
+SQLSTATE: 42809
+
+Description: The object is not a type.
+
+Solution: Ensure that the object to be processed is a type.
+
+GAUSS-01048: "%s is a table's row type"
+
+SQLSTATE: 42809
+
+Description: This object is a row type of a table and cannot use the **ALTER TYPE** syntax.
+
+Solution: Replace **ALTER TYPE** with **ALTER TABLE**.
+
+GAUSS-01049: "cannot alter array type %s"
+
+SQLSTATE: 42809
+
+Description: The array type cannot be altered.
+
+Solution: The current operation can alter the array element type and automatically alter the array type.
+
+GAUSS-01050: "type '%s' already exists in schema '%s'"
+
+SQLSTATE: 42710
+
+Description: The type already exists in the schema.
+
+Solution: Check whether the type already exists in the schema.
+
+<br/>
+
+## GAUSS-01051 - GAUSS-01060
+
+<br/>
+
+GAUSS-01051: "failed to change schema dependency for type %s"
+
+SQLSTATE: XX000
+
+Description: Failed to change the schema dependency of the type.
+
+Solution: The system catalog is abnormal. Contact technical support.
+
+GAUSS-01052: "channel name cannot be empty"
+
+SQLSTATE: 22023
+
+Description: The channel name is empty.
+
+Solution: Check the SQL statement and specify a channel name.
+
+GAUSS-01053: "channel name too long"
+
+SQLSTATE: 22023
+
+Description: The channel name is excessively long.
+
+Solution: Check the SQL statement and ensure that the channel name length is valid.
+
+GAUSS-01054: "payload string too long"
+
+SQLSTATE: 22023
+
+Description: The string is too long for the payload type.
+
+Solution: Check the SQL statement and ensure that the payload string length is valid.
+
+GAUSS-01055: "cannot PREPARE a transaction that has executed LISTEN, UNLISTEN, or NOTIFY"
+
+SQLSTATE: 0A000
+
+Description: A transaction that has executed LISTEN, UNLISTEN, or NOTIFY operation cannot be prepared.
+
+Solution: Check the SQL statement and ensure that the prepared transaction has not executed LISTEN, UNLISTEN, or NOTIFY operation.
+
+GAUSS-01056: "too many notifications in the NOTIFY queue"
+
+SQLSTATE: 54000
+
+Description: Excessive notifications exist in the notify queue.
+
+Solution: Retry the failed statement.
+
+GAUSS-01057: "unexpected rewrite result for CREATE TABLE AS SELECT"
+
+SQLSTATE: XX000
+
+Description: The rewriting result of **CREATE TABLE AS SELECT** is incorrect.
+
+Solution: Simplify the **SELECT** statement following **CREATE TABLE AS**.
+
+GAUSS-01058: "no collation was derived for column '%s' with collatable type %s"
+
+SQLSTATE: 42P22
+
+Description: Creating a heap table failed because the attribute column supports attcollation but the attcollation is invalid.
+
+Solution: Ensure that the collation definition in the attribute column is valid when the table is created.
+
+GAUSS-01059: "CREATE TABLE AS specifies too many column names"
+
+SQLSTATE: 42601
+
+Description:**CREATE TABLE AS** specifies too many columns.
+
+Solution: Check the SQL statement and ensure that the number of specified columns is appropriate.
+
+GAUSS-01060: "option '%s' not found"
+
+SQLSTATE: 42704
+
+Description: Option not found.
+
+Solution: Check the SQL statement and ensure that the corresponding option is specified.
+
+<br/>
+
+## GAUSS-01061 - GAUSS-01070
+
+<br/>
+
+GAUSS-01061: "option '%s' provided more than once"
+
+SQLSTATE: 42710
+
+Description: The option is provided more than once.
+
+Solution: Check the SQL statement and ensure that the option is provided only once.
+
+GAUSS-01062: "unrecognized action %d on option '%s'"
+
+SQLSTATE: XX000
+
+Description: The action of the required option is set to an invalid value.
+
+Solution: Check whether the SQL statement parameters are correct.
+
+GAUSS-01063: "foreign-data wrapper '%s' does not exist"
+
+SQLSTATE: 42704
+
+Description: The foreign-data wrapper does not exist.
+
+Solution: Ensure that the foreign-data wrapper has been created.
+
+GAUSS-01064: "foreign-data wrapper '%s' already exists"
+
+SQLSTATE: 42710
+
+Description: The foreign-data wrapper already exists.
+
+Solution: Do not create the foreign-data wrapper again.
+
+GAUSS-01065: "server '%s' does not exist"
+
+SQLSTATE: 42704
+
+Description: The server does not exist.
+
+Solution: Ensure that the server has been created.
+
+GAUSS-01066: "server '%s' already exists"
+
+SQLSTATE: 42710
+
+Description: The server already exists.
+
+Solution: Do not create the server again.
+
+GAUSS-01067: "permission denied to change owner of foreign-data wrapper '%s'"
+
+SQLSTATE: 42501
+
+Description: You do not have permission to change the owner of foreign-data wrapper.
+
+Solution: Change the owner of foreign-data wrapper as a system administrator.
+
+GAUSS-01068: "foreign-data wrapper with OID %u does not exist"
+
+SQLSTATE: 42704
+
+Description: The foreign-data wrapper does not exist.
+
+Solution: Ensure that the foreign-data wrapper has been created.
+
+GAUSS-01069: "foreign server with OID %u does not exist"
+
+SQLSTATE: 42704
+
+Description: The foreign server does not exist.
+
+Solution: Ensure that the foreign server has been created.
+
+GAUSS-01070: "function %s must return type 'fdw_handler'"
+
+SQLSTATE: 42809
+
+Description: The function does not return the fdw_handler type.
+
+Solution: Check the function definition and ensure that the function returns the fdw_handler type.
+
+<br/>
+
+## GAUSS-01071 - GAUSS-01080
+
+<br/>
+
+GAUSS-01071: "permission denied to create foreign-data wrapper '%s'"
+
+SQLSTATE: 42501
+
+Description: You do not have permission to create a foreign-data wrapper.
+
+Solution: Create the foreign-data wrapper as a system administrator.
+
+GAUSS-01072: "permission denied to alter foreign-data wrapper '%s'"
+
+SQLSTATE: 42501
+
+Description: You do not have permission to alter a foreign-data wrapper.
+
+Solution: Alter the foreign-data wrapper as a system administrator.
+
+GAUSS-01073: "cache lookup failed for foreign-data wrapper %u"
+
+SQLSTATE: XX000
+
+Description: Failed to find the required foreign-data wrapper.
+
+Solution: Check whether the settings of GDS, HDFS foreign tables, Roach, and OBS are correct.
+
+GAUSS-01074: "cache lookup failed for foreign server %u"
+
+SQLSTATE: XX000
+
+Description: Failed to find the required foreign-data wrapper.
+
+Solution: Check whether the settings of GDS, HDFS foreign tables, Roach, and OBS are correct.
+
+GAUSS-01075: "user mapping '%s' already exists for server %s"
+
+SQLSTATE: 42710
+
+Description: The user mapping of the server already exists.
+
+Solution: Do not create the user mapping of the server again.
+
+GAUSS-01076: "user mapping '%s' does not exist for the server"
+
+SQLSTATE: 42704
+
+Description: The user mapping of the server does not exist.
+
+Solution: Ensure that the user mapping of the server has been created before using the server.
+
+GAUSS-01077: "cache lookup failed for user mapping %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-01081 - GAUSS-01090
+
+<br/>
+
+GAUSS-01083: "get search path failed"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01084: "get namespace failed"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01086: "unacceptable schema name '%s'"
+
+SQLSTATE: 42939
+
+Description: The schema name is invalid.
+
+Solution: Avoid using the **pg_** prefix. It is reserved for the system catalog.
+
+GAUSS-01087: "cache lookup failed for namespace %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01088: "schema '%s' does not exist"
+
+SQLSTATE: 3F000
+
+Description: The schema does not exist.
+
+Solution: Ensure that the schema already exists before using it.
+
+GAUSS-01089: "schema '%s' already exists"
+
+SQLSTATE: 42P06
+
+Description: The schema already exists.
+
+Solution: Do not create the schema.
+
+GAUSS-01090: "cache lookup failed for schema %u"
+
+SQLSTATE: XX000
+
+Description: Failed to find the schema.
+
+Solution: The system catalog is abnormal. Contact technical support.
+
+<br/>
+
+## GAUSS-01091 - GAUSS-01100
+
+<br/>
+
+GAUSS-01091: "cstore.%s is a internal table"
+
+SQLSTATE: XX000
+
+Description: An internal table starting with **cstore.** is vacuumed.
+
+Solution: Do not vacuum internal tables.
+
+GAUSS-01092: "pg_class entry for relid %u vanished during vacuuming"
+
+SQLSTATE: XX000
+
+Description: Failed to find the required table object after the VACUUM operation is complete.
+
+Solution: The system catalog is abnormal. Contact technical support.
+
+GAUSS-01093: "could not find tuple for database %u"
+
+SQLSTATE: XX000
+
+Description: Failed to find the database object.
+
+Solution: The system catalog is abnormal. Contact technical support.
+
+GAUSS-01094: "pg_partition entry for partid %u vanished during vacuuming"
+
+SQLSTATE: XX000
+
+Description: Failed to find the required partition object after the VACUUM operation is complete.
+
+Solution: The system catalog is abnormal. Contact technical support.
+
+GAUSS-01095: "unexpected relkind!"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01096: "%s requires a parameter"
+
+SQLSTATE: 42601
+
+Description: A parameter is missing.
+
+Solution: Ensure that the number of parameters for the SQL statement is correct.
+
+GAUSS-01097: "%s requires a numeric value"
+
+SQLSTATE: 42601
+
+Description: The parameter provided is not of the numeric type.
+
+Solution: Check the SQL statement and provide the correct parameter.
+
+GAUSS-01098: "%s requires a Boolean value"
+
+SQLSTATE: 42601
+
+Description: The parameter provided is not of the Boolean type.
+
+Solution: Check the SQL statement and provide the correct parameter.
+
+GAUSS-01099: "argument of %s must be a name"
+
+SQLSTATE: 42601
+
+Description: The parameter name must comply with the naming conventions.
+
+Solution: Check the parameter and change the parameter value.
+
+GAUSS-01100: "argument of %s must be a type name"
+
+SQLSTATE: 42601
+
+Description: The parameter must be a type name.
+
+Solution: Ensure that a type name is used as the parameter value.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/12-GAUSS-01101-GAUSS-01200.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/12-GAUSS-01101-GAUSS-01200.md
new file mode 100644
index 0000000000000000000000000000000000000000..7d3c393f7a7083b8521ada98fd2644536c58dfd7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/12-GAUSS-01101-GAUSS-01200.md
@@ -0,0 +1,772 @@
+---
+title: GAUSS-01101 - GAUSS-01200
+summary: GAUSS-01101 - GAUSS-01200
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-01101 - GAUSS-01200
+
+<br/>
+
+## GAUSS-01101 - GAUSS-01110
+
+<br/>
+
+GAUSS-01101: "%s requires an integer value"
+
+SQLSTATE: 42601
+
+Description: The parameter provided is not of the integer type.
+
+Solution: Check the SQL statement and provide the correct parameter.
+
+GAUSS-01102: "invalid argument for %s: '%s'"
+
+SQLSTATE: 42601
+
+Description: Invalid parameter.
+
+Solution: Check the SQL statement and provide the correct parameter.
+
+GAUSS-01103: "table is not partitioned"
+
+SQLSTATE: 0A000
+
+Description: This table is not a partitioned table.
+
+Solution: Check the table name and ensure that the table is partitioned.
+
+GAUSS-01104: "cannot cluster temporary tables of other sessions"
+
+SQLSTATE: 0A000
+
+Description: Temporary tables created in other sessions cannot be clustered.
+
+Solution: Do not cluster temporary tables created in other sessions.
+
+GAUSS-01105: "there is no previously clustered index for table '%s'"
+
+SQLSTATE: 42704
+
+Description: Previously clustered index of this table does not exist.
+
+Solution: Ensure that this table has been previously clustered if the clustered index is not provided. The system will use the previously clustered index. Otherwise, provide the clustered index.
+
+GAUSS-01106: "cannot cluster a shared catalog"
+
+SQLSTATE: 0A000
+
+Description: A system catalog shared by multiple databases cannot be clustered.
+
+Solution: Do not cluster a system catalog shared by multiple databases.
+
+GAUSS-01107: "cannot vacuum temporary tables of other sessions"
+
+SQLSTATE: 0A000
+
+Description: Temporary tables created in other sessions cannot be vacuumed.
+
+Solution: Do not vacuum temporary tables created in other sessions.
+
+GAUSS-01108: "'%s' is not an index for table '%s'"
+
+SQLSTATE: 42809
+
+Description: This index is not of the table and cannot be clustered.
+
+Solution: Ensure that the index in the SQL statement matches the corresponding table.
+
+GAUSS-01109: "cannot cluster on index '%s' because access method does not support clustering"
+
+SQLSTATE: 0A000
+
+Description: The index type cannot be clustered.
+
+Solution: Do not cluster this type of index.
+
+GAUSS-01110: "cannot cluster on partial index '%s'"
+
+SQLSTATE: 0A000
+
+Description: Partial indexes cannot be clustered.
+
+Solution: Do not cluster partial indexes.
+
+<br/>
+
+## GAUSS-01111 - GAUSS-01120
+
+<br/>
+
+GAUSS-01111: "cannot cluster on invalid index '%s'"
+
+SQLSTATE: 0A000
+
+Description: The specified indexes are invalid and remain after **CREATE INDEX CONCURRENTLY** failed to be run.
+
+Solution: Do not cluster invalid indexes.
+
+GAUSS-01112: "cannot cluster on invalid index %u"
+
+SQLSTATE: XX000
+
+Description: Invalid index.
+
+Solution: The system catalog is abnormal. Contact technical support.
+
+GAUSS-01113: "CLUSTER does not support lossy index conditions"
+
+SQLSTATE: XX000
+
+Description: Lossy index conditions cannot be used during **CLUSTER** execution.
+
+Solution: Do not use hash and gist indexes.
+
+GAUSS-01114: "unexpected HeapTupleSatisfiesVacuum result"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01115: "can not cluster partition %s using %s bacause of unusable local index"
+
+SQLSTATE: XX000
+
+Description: The clustered partitioned table cannot use the local index, because it is unavailable.
+
+Solution: Rebuild the partitioned table.
+
+GAUSS-01117: "cannot swap mapped relation '%s' with non-mapped relation"
+
+SQLSTATE: XX000
+
+Description: During scale-out and redistribution, the physical files of two tables fail to be exchanged using the gs_switch_relfilenode function, because the physical file in a table is invalid.
+
+Solution: Check whether the physical file in the table specified in the gs_switch_relfilenode function is valid. If it is invalid, delete the table and rebuild the table using **CREATE TABLE**. Then, rebuild its physical file.
+
+GAUSS-01118: "cannot change tablespace of mapped relation '%s'"
+
+SQLSTATE: XX000
+
+Description: During scale-out and redistribution, the tablespaces of two tables are inconsistent and fail to be exchanged using the gs_switch_relfilenode function.
+
+Solution: Delete the current table, rebuild tablespace using **CREATE TABLESPACE**, and rebuild the table using **CREATE TABLE**.
+
+GAUSS-01119: "cannot swap toast by links for mapped relation '%s'"
+
+SQLSTATE: XX000
+
+Description: During scale-out and redistribution, the physical files of two tables fail to be exchanged using the gs_switch_relfilenode function, because the toast table in one of the tables is empty.
+
+Solution: Delete the current table, rebuild it using **CREATE TABLE**, and rebuild its physical file.
+
+GAUSS-01120: "could not find relation mapping for relation '%s', OID %u"
+
+SQLSTATE: XX000
+
+Description: During scale-out, the physical files of two tables fail to be exchanged using the gs_switch_relfilenode function, because the physical file in a table is invalid.
+
+Solution: Check whether the physical file in the table specified in the gs_switch_relfilenode function is valid. If it is invalid, delete the table and rebuild the table using **CREATE TABLE**. Then, rebuild its physical file.
+
+<br/>
+
+## GAUSS-01121 - GAUSS-01130
+
+<br/>
+
+GAUSS-01121: "cannot swap toast files by content when there's only one"
+
+SQLSTATE: XX000
+
+Description: During scale-out and redistribution, the physical files of two tables fail to be exchanged using the gs_switch_relfilenode function, because the toast table in one of the tables is empty.
+
+Solution: Delete the current table, rebuild it using **CREATE TABLE**, and rebuild its physical file.
+
+GAUSS-01122: "cannot swap toast files by links for system catalogs"
+
+SQLSTATE: XX000
+
+Description: During scale-out and redistribution, when the physical files of two tables are exchanged using the gs_switch_relfilenode function, the toast physical files of system catalogs cannot be exchanged.
+
+Solution: During scale-out and redistribution, the toast physical files of system catalogs cannot be exchanged using the gs_switch_relfilenode function. Check whether the function parameters contain any system catalog names.
+
+GAUSS-01123: "expected one dependency record for TOAST table, found %ld"
+
+SQLSTATE: XX000
+
+Description: During scale-out and redistribution, the physical files of two tables fail to be exchanged using the gs_switch_relfilenode function, because more than one object depends on the toast table.
+
+Solution: Check the number of objects the toast table depends on in the **pg_depend** table. If more than one object exists, delete them and exchange the physical files using the gs_switch_relfilenode function.
+
+GAUSS-01124: "expected none dependency record for partiton's TOAST table, found %ld"
+
+SQLSTATE: XX000
+
+Description: While the partition files of two tables are exchanged during partitioned table rebuilding, toast table files (if any) in the two tables are also exchanged. The partition files fail to be exchanged because the toast tables have dependent objects.
+
+Solution: Rebuild the required partitioned table using **CREATE TABLE PARTITION**.
+
+GAUSS-01125: "expected one dependency record for CUDesc/Delta table, found %ld"
+
+SQLSTATE: XX000
+
+Description: During scale-out and redistribution, the physical files of two column-store tables fail to be exchanged using the gs_switch_relfilenode function, because more than one object depends on the column-store table.
+
+Solution: Check the number of objects the column-store table depends on in the **pg_depend** table. If more than one object exists, delete them and exchange the physical files using the gs_switch_relfilenode function.
+
+GAUSS-01127: "invalid statement name: must not be empty"
+
+SQLSTATE: 42P14
+
+Description: The statement name is empty.
+
+Solution: Specify the statement name.
+
+GAUSS-01128: "could not determine data type of parameter $%d"
+
+SQLSTATE: 42P18
+
+Description: The parameter data type cannot be recognized.
+
+Solution: Change the parameter value to a value recognizable to the system. For the value types recognizable to the system, see en-us_topic_0237121926.html.
+
+GAUSS-01129: "utility statements cannot be prepared"
+
+SQLSTATE: 42P14
+
+Description: DDL statements cannot be prepared.
+
+Solution: Do not prepare DDL statements.
+
+GAUSS-01130: "EXECUTE does not support variable-result cached plans"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-01131 - GAUSS-01140
+
+<br/>
+
+GAUSS-01131: "prepared statement is not a SELECT"
+
+SQLSTATE: 42809
+
+Description: The prepared statement in **CREATE TABLE AS EXECUTE** is not a **SELECT** statement.
+
+Solution: Change the prepared statement to a **SELECT** statement.
+
+GAUSS-01132: "wrong number of parameters for prepared statement '%s'"
+
+SQLSTATE: 42601
+
+Description: The number of parameters required in the prepared statement does not match the number of parameters obtained.
+
+Solution: Ensure that the number of parameters in **EXECUTE** is the same as that in **PREPARE**. Then, run **PREPARE** and **EXECUTE** again.
+
+GAUSS-01136: "parameter $%d of type %s cannot be coerced to the expected type %s"
+
+SQLSTATE: 42804
+
+Description: The parameter type in a prepared statement cannot be converted to the expected parameter type.
+
+Solution: Add required type conversions or ensure that the parameter type can be converted.
+
+GAUSS-01137: "Passing parameters in PREPARE statement is not supported"
+
+SQLSTATE: 0A000
+
+Description: Parameters cannot be remotely passed in prepared statements.
+
+Solution: Do not pass distributed parameters in prepared statements.
+
+GAUSS-01138: "prepared statement '%s' already exists"
+
+SQLSTATE: 42P05
+
+Description: The prepared statement already exists.
+
+Solution: Check the **pg_prepared_statements** view. Do not create duplicate prepared statements.
+
+GAUSS-01139: "prepared statement '%s' does not exist"
+
+SQLSTATE: 26000
+
+Description: The prepared statement to be executed does not exist.
+
+Solution: Check whether the executed prepared statement exists in the **pg_prepared_statements** view.
+
+GAUSS-01140: "EXPLAIN EXECUTE does not support variable-result cached plans"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-01141 - GAUSS-01150
+
+<br/>
+
+GAUSS-01141: "datanode statement '%s' does not exist"
+
+SQLSTATE: 26000
+
+Description: The **EXECUTE DIRECT** syntax does not contain the specified DN information.
+
+Solution: Specify the DN information in the **EXECUTE DIRECT** syntax.
+
+GAUSS-01142: "must be system admin to create procedural language '%s'"
+
+SQLSTATE: 42501
+
+Description: A non-administrator user creates a stored procedure language.
+
+Solution: Create a stored procedure language as a system administrator.
+
+GAUSS-01143: "function %s must return type 'language_handler'"
+
+SQLSTATE: 42809
+
+Description: The return value of a stored procedure language is incorrect.
+
+Solution: Change the language type to **language_handler**.
+
+GAUSS-01144: "unsupported language '%s'"
+
+SQLSTATE: 42704
+
+Description: The stored procedure language is not supported.
+
+Solution: View **pg_pltemplate** and use a language existing in the list.
+
+GAUSS-01145: "must be system admin to create custom procedural language"
+
+SQLSTATE: 42501
+
+Description: A non-administrator user creates a stored procedure language.
+
+Solution: Create a stored procedure language as a system administrator.
+
+GAUSS-01146: "language '%s' already exists"
+
+SQLSTATE: 42710
+
+Description: The language already exists.
+
+Solution: View **pg_language** to check whether the language exists.
+
+GAUSS-01147: "cache lookup failed for language %u"
+
+SQLSTATE: 22P06
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01148: "COPY BINARY is not supported to stdout or from stdin"
+
+SQLSTATE: 0A000
+
+Description: The binary data cannot be copied to the standard input GUI or from the standard output GUI.
+
+Solution: Do not copy binary data to the standard input GUI or from the standard output GUI.
+
+GAUSS-01149: "could not write to COPY file: %m"
+
+SQLSTATE: XX000
+
+Description: Data cannot be copied to a specified file.
+
+Solution: Ensure that you have permission to access the specified file.
+
+GAUSS-01150: "connection lost during COPY to stdout"
+
+SQLSTATE: 08006
+
+Description: The connection is lost during the copy operation.
+
+Solution: Ensure that the network communication between the client and the server is normal.
+
+<br/>
+
+## GAUSS-01151 - GAUSS-01160
+
+<br/>
+
+GAUSS-01151: "COPY_FILE_SEGMENT does not implement in CopySendEndOfRow"
+
+SQLSTATE: XX000
+
+Description: The target data source specified in **COPY TO** is not supported.
+
+Solution: Change the target data source.
+
+GAUSS-01152: "COPY_GDS does not implement in CopySendEndOfRow"
+
+SQLSTATE: XX000
+
+Description: The target data source specified in **COPY TO** is not supported.
+
+Solution: Change the target data source.
+
+GAUSS-01153: "could not read from COPY file: %m"
+
+SQLSTATE: XX000
+
+Description: Failed to read data from a specified copy file.
+
+Solution: Check whether the specified file is damaged and the permission is sufficient.
+
+GAUSS-01154: "unexpected EOF on client connection with an open transaction"
+
+SQLSTATE: 08006
+
+Description: The connection fails when the data is copied to the standard input.
+
+Solution: Ensure that the network communication between the client and the server is normal.
+
+GAUSS-01155: "COPY from stdin failed: %s"
+
+SQLSTATE: 57014
+
+Description: Failed to copy data from the standard input.
+
+Solution: Ensure that the network communication between the client and the server is normal.
+
+GAUSS-01156: "unexpected message type 0x%02X during COPY from stdin"
+
+SQLSTATE: 08P01
+
+Description: The data type copied from the standard input is incorrect.
+
+Solution: Ensure that the data type in the standard input is correct.
+
+GAUSS-01157: "COPY_BUFFER not allowed in this context"
+
+SQLSTATE: XX000
+
+Description: The target data source specified in **COPY TO** is not supported.
+
+Solution: Change the target data source.
+
+GAUSS-01158: "unimplemented CopyDest mode"
+
+SQLSTATE: XX000
+
+Description: The target data source specified in **COPY TO** is not supported.
+
+Solution: Change the target data source.
+
+GAUSS-01159: "must be system admin to COPY to or from a file"
+
+SQLSTATE: 42501
+
+Description: A non-administrator user performs the copy operation.
+
+Solution: Perform the copy operation as a system administrator.
+
+GAUSS-01160: "position of field '%s' can not be less then 0"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-01161 - GAUSS-01170
+
+<br/>
+
+GAUSS-01161: "length of field '%s' can not be less then 0"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01162: "max length of data row cannot greater than 1GB"
+
+SQLSTATE: 42601
+
+Description: The length of the row is greater than 1 GB.
+
+Solution: Ensure that the maximum length of the data row is not greater than 1 GB.
+
+GAUSS-01163: "max length of data row cannot greater than 1GB"
+
+SQLSTATE: 42601
+
+Description: The length of the row is greater than 1 GB.
+
+Solution: Ensure that the maximum length of the data row is not greater than 1 GB.
+
+GAUSS-01164: "pre-field '%s' can not be covered by field '%s'"
+
+SQLSTATE: 42601
+
+Description: The data area is covered.
+
+Solution: Ensure that the data is within the specified range and is not covered.
+
+GAUSS-01165: "default conversion function for encoding '%s' to '%s' does not exist"
+
+SQLSTATE: 42883
+
+Description: No function is used to convert between the encoding format specified in **COPY** and the database encoding format.
+
+Solution: Change the encoding format specified in **COPY**.
+
+GAUSS-01166: "invalid user-define header file '%s'"
+
+SQLSTATE: XX000
+
+Description: A customized header file involved in **COPY** is invalid.
+
+Solution:Contact technical support.
+
+GAUSS-01167: "no data in user-define header file '%s'"
+
+SQLSTATE: XX000
+
+Description: A customized header file involved in **COPY** is invalid.
+
+Solution:Contact technical support.
+
+GAUSS-01168: "user-define header should not longger than 1MB"
+
+SQLSTATE: XX000
+
+Description: A customized header file involved in **COPY** is invalid.
+
+Solution:Contact technical support.
+
+GAUSS-01169: "COPY format '%s' not recognized"
+
+SQLSTATE: 22023
+
+Description: The data file format specified in **COPY** not supported.
+
+Solution: Ensure that the data file format is correct.
+
+GAUSS-01170: "null value string is too long"
+
+SQLSTATE: 22023
+
+Description: An excessively long null value string is used when the data is copied.
+
+Solution: Ensure that the length of the null string specified in **COPY** does not exceed 100 characters.
+
+<br/>
+
+## GAUSS-01171 - GAUSS-01180
+
+<br/>
+
+GAUSS-01171: "argument to option '%s' must be a list of column names"
+
+SQLSTATE: 22023
+
+Description: The parameter option is not one of the column names.
+
+Solution: Ensure that the parameter option is one of the column names.
+
+GAUSS-01172: "argument to option '%s' must be a valid encoding name"
+
+SQLSTATE: 22023
+
+Description: The parameter option is not a valid encoding name.
+
+Solution: Ensure that the parameter option is a known encoding name.
+
+GAUSS-01174: "invalid value of FIX"
+
+SQLSTATE: 22023
+
+Description: The value of the fix option cannot be recognized.
+
+Solution: Ensure that the value is correct.
+
+GAUSS-01175: "option '%s' not recognized"
+
+SQLSTATE: 42601
+
+Description: The value of a copy option cannot be recognized.
+
+Solution: Ensure that the value is correct.
+
+GAUSS-01176: "cannot specify DELIMITER in BINARY/FIXED mode"
+
+SQLSTATE: 42601
+
+Description: A delimiter fails to be specified in BINARY/FIXED mode.
+
+Solution: Do not specify a delimiter in BINARY/FIXED.
+
+GAUSS-01177: "cannot specify NULL in BINARY/FIXED mode"
+
+SQLSTATE: 42601
+
+Description: The null character fails to be specified in BINARY/FIXED mode.
+
+Solution: Do not specify a null character in BINARY/FIXED mode.
+
+GAUSS-01178: "FORMATTER only can be specified in FIXED mode"
+
+SQLSTATE: 42601
+
+Description:**FORMATTER** is not specified in FIXED mode.
+
+Solution: Specify **FORMATTER** in FIXED mode.
+
+GAUSS-01179: "FORMATTER must be specified in FIXED mode"
+
+SQLSTATE: 42601
+
+Description:**FORMATTER** is not specified in FIXED mode.
+
+Solution: Specify **FORMATTER** in FIXED mode.
+
+GAUSS-01180: "FIX only can be specified in FIXED mode"
+
+SQLSTATE: 42601
+
+Description:**FIX** is not specified in FIXED mode.
+
+Solution: Specify **FIX** in FIXED mode.
+
+<br/>
+
+## GAUSS-01181 - GAUSS-01190
+
+<br/>
+
+GAUSS-01181: "COPY delimiter must be less than %d bytes"
+
+SQLSTATE: 0A000
+
+Description: The copy delimiter specified exceeds the maximum length.
+
+Solution: Specify a delimiter with its length within 10 bytes.
+
+GAUSS-01182: "COPY delimiter cannot be newline or carriage return"
+
+SQLSTATE: 22023
+
+Description: Line breaks or carriage returns are used as copy delimiters.
+
+Solution: Use only horizontal tabs or commas as copy delimiters. For details, see en-us_topic_0237122096.html.
+
+GAUSS-01183: "COPY null representation cannot use newline or carriage return"
+
+SQLSTATE: 22023
+
+Description: Line breaks or carriage returns are used as copy null characters.
+
+Solution: Do not use line breaks or carriage returns as copy null characters.
+
+GAUSS-01184: "delimiter '%s' cannot contain any characters in'%s'"
+
+SQLSTATE: 22023
+
+Description: When a non-CSV file is imported, the specified delimiter contains forbidden characters, such as lowercase letters (a-z), digits (0-9), dots (.), and backslashes ().
+
+Solution: Change the delimiter to ensure no forbidden characters are included.
+
+GAUSS-01185: "COPY HEADER available only in CSV mode"
+
+SQLSTATE: 0A000
+
+Description: The copy header is not in CSV mode.
+
+Solution: Ensure that the copy header is in CSV mode.
+
+GAUSS-01186: "COPY quote available only in CSV mode"
+
+SQLSTATE: 0A000
+
+Description: The copy quote is not in CSV mode.
+
+Solution: Ensure that the copy quote is in CSV mode.
+
+GAUSS-01188: "delimiter cannot contain quote character"
+
+SQLSTATE: 22023
+
+Description: When a CSV file is imported, the delimiter contains quotation characters.
+
+Solution: Change the quotation characters to allowed CSV delimiters.
+
+GAUSS-01189: "COPY escape available only in CSV mode"
+
+SQLSTATE: 0A000
+
+Description: The copy escape is not in CSV mode.
+
+Solution: Ensure that the copy escape is in CSV mode.
+
+<br/>
+
+## GAUSS-01191 - GAUSS-01200
+
+<br/>
+
+GAUSS-01191: "COPY force quote available only in CSV mode"
+
+SQLSTATE: 0A000
+
+Description: The copy force quote is not in CSV mode.
+
+Solution: Ensure that the force quote is in CSV mode.
+
+GAUSS-01194: "COPY force not null only available using COPY FROM"
+
+SQLSTATE: 0A000
+
+Description: The force not-null character supports only COPY FROM operation.
+
+Solution: Ensure that the force non-null character is in the **COPY FROM** statement.
+
+GAUSS-01195: "COPY delimiter must not appear in the NULL specification"
+
+SQLSTATE: 0A000
+
+Description: The copy delimiter exists in the null specification.
+
+Solution: Do not use a value in the null specification as a delimiter.
+
+GAUSS-01197: "CSV quote character must not appear in the NULL specification"
+
+SQLSTATE: 0A000
+
+Description: The copy quote character exists in the null specification.
+
+Solution: Do not use a value in the null specification as a delimiter.
+
+GAUSS-01198: "SHARED mode can not be used with CSV format"
+
+SQLSTATE: 0A000
+
+Description: The shared mode is used with CSV format.
+
+Solution: Do not use the shared mode with the CSV format.
+
+GAUSS-01199: "HEADER FILE only available using COPY TO or WRITE ONLY foreign table"
+
+SQLSTATE: 0A000
+
+Description: The header file is not used in **COPY TO** and foreign table scenarios.
+
+Solution: Use the header file only in **COPY TO** and foreign table scenarios.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/13-GAUSS-01201-GAUSS-01300.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/13-GAUSS-01201-GAUSS-01300.md
new file mode 100644
index 0000000000000000000000000000000000000000..545206a3d65d4aa5e8dd3b50166def3679666dac
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/13-GAUSS-01201-GAUSS-01300.md
@@ -0,0 +1,814 @@
+---
+title: GAUSS-01201 - GAUSS-01300
+summary: GAUSS-01201 - GAUSS-01300
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-01201 - GAUSS-01300
+
+<br/>
+
+## GAUSS-01201 - GAUSS-01210
+
+<br/>
+
+GAUSS-01201: "can not specify EOL in BINARY mode"
+
+SQLSTATE: 0A000
+
+Description: The terminator fails to be specified in BINARY mode.
+
+Solution: Do not use terminators in BINARY mode.
+
+GAUSS-01202: "FIX specification only available using COPY FROM or READ ONLY foreign table"
+
+SQLSTATE: 42000
+
+Description:**FIX** is not used in **COPY FROM** or foreign table scenarios.
+
+Solution: Use **FIX** only in **COPY FROM** or foreign table scenarios.
+
+GAUSS-01203: "FILEHEADER specification only available using HEAD"
+
+SQLSTATE: 42601
+
+Description: The file to read HEADER information from is specified, but whether this information is required is not specified.
+
+Solution: Specify **HEADER** in the export statement or remove the name of the file to be read.
+
+GAUSS-01204: "table '%s' does not have OIDs"
+
+SQLSTATE: 42703
+
+Description: The OID item is specified when data is imported, but there is no such OID column in the user table.
+
+Solution: Ensure that the data to be imported has OIDs consistent with the user table definition. Delete the imported OID item or add an OID column to the user table.
+
+GAUSS-01206: "unexpected rewrite result"
+
+SQLSTATE: XX000
+
+Description: Internal system error. The imported SQL statement is not rewritten as expected.
+
+Solution: Runtime error. Contact technical support.
+
+GAUSS-01207: "COPY (SELECT INTO) is not supported"
+
+SQLSTATE: 0A000
+
+Description:**COPY SELECT INTO** is not supported.
+
+Solution: Do not use **SELECT INTO** in **COPY**.
+
+GAUSS-01208: "FORCE QUOTE column '%s' not referenced by COPY"
+
+SQLSTATE: 42P10
+
+Description: In CSV COPY TO mode, quotation marks are not used for non-null values in each specified column.
+
+Solution: Use quotation marks for all not-null values in each specified column. Null values are not quoted.
+
+GAUSS-01209: "FORCE NOT NULL column '%s' not referenced by COPY"
+
+SQLSTATE: 42P10
+
+Description: In CSV COPY FROM mode, the specified column is empty.
+
+Solution: Enter a value for the specified column.
+
+GAUSS-01210: "could not close file '%s': %m"
+
+SQLSTATE: XX000
+
+Description: Failed to close a specified file.
+
+Solution: Ensure that the specified file is not damaged and the permission is sufficient.
+
+<br/>
+
+## GAUSS-01211 - GAUSS-01220
+
+<br/>
+
+GAUSS-01211: "cannot copy from view '%s'"
+
+SQLSTATE: 42809
+
+Description: Failed to copy data from a view.
+
+Solution: Do not copy data from a view.
+
+GAUSS-01212: "cannot copy from foreign table '%s'"
+
+SQLSTATE: 42809
+
+Description: Failed to copy data from a foreign table.
+
+Solution: Do not copy data from a foreign table.
+
+GAUSS-01213: "cannot copy from sequence '%s'"
+
+SQLSTATE: 42809
+
+Description: Failed to copy data from a sequence.
+
+Solution: Do not copy data from a sequence.
+
+GAUSS-01214: "cannot copy from non-table relation '%s'"
+
+SQLSTATE: 42809
+
+Description: Failed to copy data from a non-table relation.
+
+Solution: Do not copy data from a non-table relation.
+
+GAUSS-01215: "relative path not allowed for COPY to file"
+
+SQLSTATE: 42602
+
+Description: The path format of the target file to be copied cannot be a relative path.
+
+Solution: Use an absolute path as a target file path.
+
+GAUSS-01216: "could not open file '%s' for writing: %m"
+
+SQLSTATE: XX000
+
+Description: Failed to open a file.
+
+Solution: Ensure that the file is not damaged and the permission is sufficient.
+
+GAUSS-01217: "'%s' is a directory"
+
+SQLSTATE: 42809
+
+Description: The specified parameter is a directory name but not a file name.
+
+Solution: Specify a file name rather than a directory name in **COPY**.
+
+GAUSS-01218: "could not chmod file '%s' : %m"
+
+SQLSTATE: XX000
+
+Description: Failed to change the file permission.
+
+Solution: Ensure that the permission and user group of the file are correct.
+
+GAUSS-01219: "Invalid file format"
+
+SQLSTATE: XX000
+
+Description: The file format is not supported.
+
+Solution: Use a TXT, binary, or CSV format that is supported during copy.
+
+GAUSS-01220: "null value in column '%s' violates not-null constraint"
+
+SQLSTATE: 23502
+
+Description: A null value is entered in a column having the not-null constraint.
+
+Solution: Enter valid values in columns having the not-null constraint.
+
+<br/>
+
+## GAUSS-01221 - GAUSS-01230
+
+<br/>
+
+GAUSS-01221: "Column Store unsupport CHECK constraint"
+
+SQLSTATE: XX000
+
+Description: Currently, column storage does not support the check constraint.
+
+Solution: Delete the check constraint.
+
+GAUSS-01222: "cannot copy to view '%s'"
+
+SQLSTATE: 42809
+
+Description: Failed to copy data to a view.
+
+Solution: Do not copy data to a view.
+
+GAUSS-01223: "cannot copy to foreign table '%s'"
+
+SQLSTATE: 42809
+
+Description: Failed to copy data to a foreign table.
+
+Solution: Do not copy data to a foreign table.
+
+GAUSS-01224: "cannot copy to sequence '%s'"
+
+SQLSTATE: 42809
+
+Description: Failed to copy data to a sequence.
+
+Solution: Do not copy data to a sequence.
+
+GAUSS-01225: "cannot copy to non-table relation '%s'"
+
+SQLSTATE: 42809
+
+Description: Failed to copy data to a non-table relation.
+
+Solution: Do not copy data to a non-table relation.
+
+GAUSS-01226: "invalid COPY file header (COPY SEND)"
+
+SQLSTATE: 22P04
+
+Description: The copy file header is invalid.
+
+Solution: The file is damaged. Check it.
+
+GAUSS-01227: "Copy failed on a Datanode"
+
+SQLSTATE: 08000
+
+Description: Failed to import data.
+
+Solution: Check logs on DNs to identify the error type and take required measures.
+
+GAUSS-01228: "Missing data when batch insert compressed data !"
+
+SQLSTATE: XX000
+
+Description: Data is lost while compressed data is imported to a row-store table.
+
+Solution: Run **ALTER TABLE** to disable the compression feature of the row-store table and import the data again.
+
+GAUSS-01229: "Non-shippable ROW triggers not supported with COPY"
+
+SQLSTATE: 0A000
+
+Description: Row triggers are used in **COPY**.
+
+Solution: Do not use row triggers in **COPY**.
+
+GAUSS-01230: "could not open file '%s' for reading: %m"
+
+SQLSTATE: XX000
+
+Description: Failed to open a file.
+
+Solution: The file does not exist, the user does not have permission, or the disk space is full. Identify the cause and resolve the problem.
+
+<br/>
+
+## GAUSS-01231 - GAUSS-01240
+
+<br/>
+
+GAUSS-01231: "COPY file signature not recognized"
+
+SQLSTATE: 22P04
+
+Description: Failed to recognize the file signature during copy operation.
+
+Solution: The file is damaged. Check it.
+
+GAUSS-01232: "invalid COPY file header (missing flags)"
+
+SQLSTATE: 22P04
+
+Description: The file header is missing during copy operation.
+
+Solution: The file is damaged. Check it.
+
+GAUSS-01233: "unrecognized critical flags in COPY file header"
+
+SQLSTATE: 22P04
+
+Description: Failed to recognize the file header during copy operation.
+
+Solution: The file is damaged. Check it.
+
+GAUSS-01236: "missing data for OID column"
+
+SQLSTATE: 22P04
+
+Description: The OID value is null during copy operation.
+
+Solution: Ensure that no null value exists in the first column of a file.
+
+GAUSS-01237: "null OID in COPY data"
+
+SQLSTATE: 22P04
+
+Description: The OID value is null during copy operation.
+
+Solution: Ensure that the OID value of a table to which data needs to be imported is not null.
+
+GAUSS-01238: "invalid OID in COPY data"
+
+SQLSTATE: 22P04
+
+Description: The OID value is invalid.
+
+Solution: Check the **COPY** statement and ensure that columns correspond to actual data.
+
+GAUSS-01239: "missing data for column '%s'"
+
+SQLSTATE: 22P04
+
+Description: In the **COPY** statement, the number of columns expected to be imported is greater than the actual number of columns. In this case, some columns lack data.
+
+Solution: Check the **COPY** statement and ensure that the number of columns expected to be imported is consistent with the actual number of columns.
+
+GAUSS-01240: "received copy data after EOF marker"
+
+SQLSTATE: 22P04
+
+Description: Data is obtained after the EOF marker occurs because the marker is not defined in the previous protocol.
+
+Solution: Ensure that the size of data defined in the current protocol does not exceed the expected one.
+
+<br/>
+
+## GAUSS-01241 - GAUSS-01250
+
+<br/>
+
+GAUSS-01241: "row field count is %d, expected %d"
+
+SQLSTATE: 22P04
+
+Description: The number of expected attributes is inconsistent with the actual number.
+
+Solution: Internal error. Contact technical support. If the number of attributes in the target table is inconsistent with that in the source table, modify the column number to ensure that the number of columns in the source file is consistent with that in the target file. "
+
+GAUSS-01242: "literal carriage return found in data"
+
+SQLSTATE: 22P04
+
+Description: A carriage return character exists in the copied data.
+
+Solution: Ensure that no carriage return character exists in the copied data.
+
+GAUSS-01243: "literal newline found in data"
+
+SQLSTATE: 22P04
+
+Description: Unrecognized data format exists in the CSV file.
+
+Solution: Ensure that the data format and content meet the constraints.
+
+GAUSS-01244: "end-of-copy marker does not match previous newline style"
+
+SQLSTATE: 22P04
+
+Description: Abnormal characters exist in the file.
+
+Solution: Ensure that the data format is valid. For details, see en-us_topic_0237122096.html.
+
+GAUSS-01245: "end-of-copy marker corrupt"
+
+SQLSTATE: 22P04
+
+Description: Abnormal characters exist in the file.
+
+Solution: Ensure that the data format is valid. For details, see en-us_topic_0237122096.html.
+
+GAUSS-01246: "unterminated CSV quoted field"
+
+SQLSTATE: 22P04
+
+Description: Abnormal characters exist in the file.
+
+Solution: Ensure that the data format is valid. For details, see en-us_topic_0237122096.html.
+
+GAUSS-01247: "unexpected EOF in COPY data"
+
+SQLSTATE: 22P04
+
+Description: The copied file cannot be read.
+
+Solution: Ensure that the data format is valid. For details, see en-us_topic_0237122096.html.
+
+GAUSS-01248: "invalid field size"
+
+SQLSTATE: 22P04
+
+Description: Invalid data size is detected when the copied file is read.
+
+Solution: Ensure that the data format is valid. For details, see en-us_topic_0237122096.html.
+
+GAUSS-01249: "incorrect binary data format"
+
+SQLSTATE: 22P03
+
+Description: Incorrect binary data format exists.
+
+Solution: Ensure that the data format is valid. For details, see en-us_topic_0237122096.html.
+
+GAUSS-01250: "Failed to initialize Datanodes for COPY"
+
+SQLSTATE: 08000
+
+Description: Failed to initialize connections between DNs during copy operation.
+
+Solution: Check the following items in sequence: 1) whether the cluster is in normal state; 2) whether the connection between nodes is normal; 3) whether the network connection between current nodes is normal; 4) whether memory is sufficient on all nodes and no OOM problem occurs.
+
+<br/>
+
+## GAUSS-01251 - GAUSS-01260
+
+<br/>
+
+GAUSS-01251: "could not read symbolic link '%s': %m"
+
+SQLSTATE: XX000
+
+Description: Failed to read a symbolic link file.
+
+Solution: Ensure that the symbolic link file is correct.
+
+GAUSS-01252: "symbolic link '%s' target is too long"
+
+SQLSTATE: XX000
+
+Description: The length of the symbolic link file name is too long.
+
+Solution: Ensure that the symbolic link file is correct.
+
+GAUSS-01253: "Invalid URL '%s' in LOCATION"
+
+SQLSTATE: XX000
+
+Description: Invalid URL exists in GDS.
+
+Solution: Ensure that the URL value and format are correct.
+
+GAUSS-01254: "unrecognized URL '%s'"
+
+SQLSTATE: XX000
+
+Description: Invalid URL exists in GDS.
+
+Solution: Ensure that the URL value and format are correct.
+
+GAUSS-01255: "wrong URL format '%s'"
+
+SQLSTATE: XX000
+
+Description: Invalid URL exists in GDS.
+
+Solution: Ensure that the URL value and format are correct.
+
+GAUSS-01256: "unable to open file '%s'"
+
+SQLSTATE: XX000
+
+Description: Failed to open a file.
+
+Solution: Ensure that the file format and permission are correct.
+
+GAUSS-01257: "unable to fseek file '%s'"
+
+SQLSTATE: XX000
+
+Description: Failed to set the file pointer position.
+
+Solution: Ensure that the file format and permission are correct.
+
+GAUSS-01258: "no files found to import"
+
+SQLSTATE: XX000
+
+Description: No files are imported. An error is reported when **raise_errors_if_no_files** is enabled.
+
+Solution: Disable **raise_errors_if_no_files**.
+
+GAUSS-01259: "%s"
+
+SQLSTATE: XX000
+
+Description: Syntax error.
+
+Solution: Ensure that the SQL syntax is correct.
+
+GAUSS-01260: "Incomplete Message from GDS ."
+
+SQLSTATE: XX000
+
+Description: Unexpected message data is received from GDS.
+
+Solution: Check the network running status, for example, whether the packet loss rate is high. If the network is running properly, an internal error occurs. Contact technical support.
+
+<br/>
+
+## GAUSS-01261 - GAUSS-01270
+
+<br/>
+
+GAUSS-01261: "unimplemented bulkload mode"
+
+SQLSTATE: XX000
+
+Description: The import mode is not supported.
+
+Solution: Select the normal, shared, or private mode.
+
+GAUSS-01262: "relative path not allowed for writable foreign table file"
+
+SQLSTATE: 42602
+
+Description: A relative path is used in the writable foreign table.
+
+Solution: Use an absolute path in the writable foreign table.
+
+GAUSS-01264: "Found invalid error recored"
+
+SQLSTATE: XX000
+
+Description: Invalid data records exist in tuples.
+
+Solution: Locate the data row where the error occurred based on the error context and check whether invalid characters exist. If they do not, an internal error occurred. Contact technical support.
+
+GAUSS-01265: "could not cache error info:%m"
+
+SQLSTATE: XX000
+
+Description: Failed to cache error information.
+
+Solution: Locate the data row where the error occurred based on the error context and check whether invalid characters exist. If they do not, an internal error occurred. Contact technical support.
+
+GAUSS-01266: "could not fetch error record:%m"
+
+SQLSTATE: XX000
+
+Description: Failed to obtain error information.
+
+Solution: Locate the data row where the error occurred based on the error context and check whether invalid characters exist. If they do not, an internal error occurred. Contact technical support.
+
+GAUSS-01267: "incomplete error record"
+
+SQLSTATE: XX000
+
+Description: Incomplete error information.
+
+Solution: Locate the data row where the error occurred based on the error context and check whether invalid characters exist. If they do not, an internal error occurred. Contact technical support.
+
+GAUSS-01268: "access method '%s' does not exist"
+
+SQLSTATE: 42704
+
+Description: Tuples cannot be obtained from the system cache.
+
+Solution: System catalog information is incorrect. Contact technical support.
+
+GAUSS-01269: "must specify at least one column"
+
+SQLSTATE: 42P17
+
+Description: No column is specified when you create an index.
+
+Solution: Specify at least one column when you create an index.
+
+GAUSS-01270: "cannot use more than %d columns in an index"
+
+SQLSTATE: 54011
+
+Description: The number of specified columns in an index cannot exceed 32.
+
+Solution: Specify a maximum of 32 columns in an index.
+
+<br/>
+
+## GAUSS-01271 - GAUSS-01280
+
+<br/>
+
+GAUSS-01271: "non-partitioned table does not support local partitioned indexes "
+
+SQLSTATE: 0A000
+
+Description: Local partitioned indexes cannot be created in non-partitioned tables.
+
+Solution: To create a partitioned index in local mode, rebuild the base table as a partitioned table.
+
+If you do not need to create a partitioned index in local mode, delete the **local** parameter from **Create unique index…local**.
+
+GAUSS-01274: "cannot create index on foreign table '%s'"
+
+SQLSTATE: 42809
+
+Description: Indexes cannot be created on foreign tables.
+
+Solution: Do not create indexes on foreign tables.
+
+GAUSS-01275: "cannot create indexes on temporary tables of other sessions"
+
+SQLSTATE: 0A000
+
+Description: Indexes cannot be created on temporary tables of other sessions.
+
+Solution: Do not create indexes on temporary tables of other sessions.
+
+GAUSS-01276: "when creating partitioned index, get table partitions failed"
+
+SQLSTATE: XX000
+
+Description: Failed to obtain partitioned tables during the creation of partitioned indexes.
+
+Solution: Check whether the partition definition of partitioned tables is correct. If it is not, rebuild partitioned tables.
+
+GAUSS-01278: "number of partitions of LOCAL index must equal that of the underlying table"
+
+SQLSTATE: 42P17
+
+Description: The number of partitions in a partitioned table is smaller than the number of partitioned indexes.
+
+Solution: Rebuild the partitioned table to ensure that the number of partitions is equal to the number of partitioned indexes.
+
+GAUSS-01279: "unique index columns must contain the partition key"
+
+SQLSTATE: 42P17
+
+Description: The unique index columns do not contain a partition key.
+
+Solution: Ensure that the unique index columns contain a partition key.
+
+GAUSS-01280: "unique index columns must contain the partition key and collation must be default collation"
+
+SQLSTATE: 42P17
+
+Description: The unique index columns do not contain a partition key.
+
+Solution: Ensure that the unique index columns contain a partition key and the default sorting mode is used.
+
+<br/>
+
+## GAUSS-01281 - GAUSS-01290
+
+<br/>
+
+GAUSS-01281: "access method '%s' does not support unique indexes"
+
+SQLSTATE: 0A000
+
+Description: Unique indexes are not supported.
+
+Solution: Do not create unique indexes described in the error message.
+
+GAUSS-01282: "access method '%s' does not support multicolumn indexes"
+
+SQLSTATE: 0A000
+
+Description: Combination indexes are not supported.
+
+Solution: Do not create unique indexes described in the error message.
+
+GAUSS-01283: "access method '%s' does not support exclusion constraints"
+
+SQLSTATE: 0A000
+
+Description: Exclusion constraints are not supported.
+
+Solution: Do not add exclusive constraints described in the error message.
+
+GAUSS-01284: "Cannot create index whose evaluation cannot be enforced to remote nodes"
+
+SQLSTATE: 0A000
+
+Description: MogDB primary key constraint takes effect through a unique B-tree index. The index cannot be created if the primary key constraint does not contain a distribution column.
+
+Solution: Check whether the primary key constraint contains a distribution column.
+
+GAUSS-01285: "unknown constraint type"
+
+SQLSTATE: XX000
+
+Description: The constraint type defined during index creation is incorrect.
+
+Solution: The keyword for creating an index can only be **PRIMARY KEY**, **UNIQUE**, or **EXCLUDE**. Use a one of them to rebuild the index.
+
+GAUSS-01286: "fail to get index info when create index partition"
+
+SQLSTATE: 42P17
+
+Description: Failed to obtain indexes during the creation of partitioned indexes.
+
+Solution: Re-create the partition index. If the system still displays a failure message, an internal error occurs. Contact technical support.
+
+GAUSS-01287: "index partition with name '%s' already exists"
+
+SQLSTATE: 42704
+
+Description: The name of a partitioned index exists.
+
+Solution: Modify the name of a partitioned index to avoid duplication.
+
+GAUSS-01288: "unsupport partitioned strategy"
+
+SQLSTATE: 42P17
+
+Description: The partitioning policy is not supported.
+
+Solution: Currently, the partitioned index can be created only for RANGE or INTERNAL partitioned tables. Change the partitioned table type to **RANGE** or **INTERNAL** and rebuild the partitioned index.
+
+GAUSS-01289: "collation '%s' does not exist"
+
+SQLSTATE: 42P17
+
+Description: The sorting mode of indexes does not exist.
+
+Solution: Ensure that the sorting mode of indexes is correct.
+
+GAUSS-01290: "cannot use subquery in index predicate"
+
+SQLSTATE: 0A000
+
+Description: A subquery is used in an expression index.
+
+Solution: Do not use a subquery in an expression index.
+
+<br/>
+
+## GAUSS-01291 - GAUSS-01300
+
+<br/>
+
+GAUSS-01291: "cannot use aggregate in index predicate"
+
+SQLSTATE: 42803
+
+Description: Aggregate operations are performed in an expression index.
+
+Solution: Do not use an aggregate function in an expression index.
+
+GAUSS-01292: "functions in index predicate must be marked IMMUTABLE"
+
+SQLSTATE: 42P17
+
+Description: A volatile function is used in an expression index.
+
+Solution: Do not use a volatile function in an expression index.
+
+GAUSS-01293: "cannot use subquery in index expression"
+
+SQLSTATE: 0A000
+
+Description: A subquery is used in an expression index.
+
+Solution: Do not use a subquery in an expression index.
+
+GAUSS-01294: "cannot use aggregate function in index expression"
+
+SQLSTATE: 42803
+
+Description: Aggregate operations are performed in an expression index.
+
+Solution: Do not use an aggregate function in an expression index.
+
+GAUSS-01295: "functions in index expression must be marked IMMUTABLE"
+
+SQLSTATE: 42P17
+
+Description: A volatile function is used in an expression index.
+
+Solution: Do not use a volatile function in an expression index.
+
+GAUSS-01296: "could not determine which collation to use for index expression"
+
+SQLSTATE: 42P22
+
+Description: The sorting mode cannot be determined in an expression index.
+
+Solution: Specify the sorting mode during the creation of an expression index.
+
+GAUSS-01297: "operator %s is not commutative"
+
+SQLSTATE: 42809
+
+Description: Operators are not commutative.
+
+Solution: Use commutative operators in exclusive constraints.
+
+GAUSS-01298: "cache lookup failed for opfamily %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01299: "operator %s is not a member of operator family '%s'"
+
+SQLSTATE: 42809
+
+Description: The operator is not a member of an expected operator family.
+
+Solution: Use an operator which is a member of an expected operator family.
+
+GAUSS-01300: "access method '%s' does not support ASC/DESC options"
+
+SQLSTATE: 0A000
+
+Description: ASC or DESC options are used to process indexes.
+
+Solution: Rebuild the index and set the access method (**amcanorder** in **pg_am**) of the index column to true.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/14-GAUSS-01301-GAUSS-01400.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/14-GAUSS-01301-GAUSS-01400.md
new file mode 100644
index 0000000000000000000000000000000000000000..09761f48e7ba13cb340770ace862de834c953c6e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/14-GAUSS-01301-GAUSS-01400.md
@@ -0,0 +1,748 @@
+---
+title: GAUSS-01301 - GAUSS-01400
+summary: GAUSS-01301 - GAUSS-01400
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-01301 - GAUSS-01400
+
+<br/>
+
+## GAUSS-01301 - GAUSS-01310
+
+<br/>
+
+GAUSS-01301: "access method '%s' does not support NULLS FIRST/LAST options"
+
+SQLSTATE: 0A000
+
+Description: The NULLS, FIRST, or LAST option cannot be used for index processing.
+
+Solution: Rebuild the index and set the access method (**amcanorder** in **pg_am**) of the index column to true.
+
+GAUSS-01302: "operator class '%s' does not exist for access method '%s'"
+
+SQLSTATE: 42704
+
+Description: The operator cannot be used for index processing.
+
+Solution: Ensure that the operator is supported for index processing.
+
+GAUSS-01303: "there are multiple default operator classes for data type %s"
+
+SQLSTATE: 42710
+
+Description: The default operator classes of data types are excessive.
+
+Solution: The operator definition in the **pg_opclass** system catalog is incorrect. Contact technical support.
+
+GAUSS-01304: "'%s' does not mean oid '%u'"
+
+SQLSTATE: XX000
+
+Description: The obtained OID of the partitioned table is incorrect.
+
+Solution: Rebuild the index using **ALTER INDEX…REBUILD**.
+
+GAUSS-01305: "'%u' is not a child of '%u'"
+
+SQLSTATE: XX000
+
+Description: The child partition is not in the partitioned table.
+
+Solution: Rebuild the index using **ALTER INDEX…REBUILD**.
+
+GAUSS-01308: "fail to get index info for index %u"
+
+SQLSTATE: XX000
+
+Description: The index information about the partitioned table cannot be obtained.
+
+Solution: Failed to query the index table (index information of the **pg_index** system catalog) of the partitioned table in the cache. The cache is abnormal. Contact technical support.
+
+GAUSS-01309: "unable to find attribute %d for relation %u."
+
+SQLSTATE: XX000
+
+Description: The attribute information about the table cannot be found.
+
+Solution: Failed to find the attribute column of the partitioned index table in the cache. The cache is abnormal. Contact technical support.
+
+GAUSS-01310: "cache %d lookup failed for relation %u"
+
+SQLSTATE: XX000
+
+Description: Failed to find the index table in the **pg_class** table.
+
+Solution: The index table corresponding to the **pg_class** system catalog in the cache is abnormal. Contact technical support.
+
+<br/>
+
+## GAUSS-01311 - GAUSS-01320
+
+<br/>
+
+GAUSS-01311: "collation attribute '%s' not recognized"
+
+SQLSTATE: 42601
+
+Description: The **Create Collation** syntax is used.
+
+Solution: Do not use the syntax.
+
+GAUSS-01314: "collation '%s' for encoding '%s' already exists in schema '%s'"
+
+SQLSTATE: 42710
+
+Description: The sorting rule for a character set exists.
+
+Solution: Do not create duplicate sorting rules for a character set.
+
+GAUSS-01315: "collation '%s' already exists in schema '%s'"
+
+SQLSTATE: 42710
+
+Description: The sorting rule exists in the schema.
+
+Solution: Do not create duplicate sorting rules in a schema.
+
+GAUSS-01316: "unlogged sequences are not supported"
+
+SQLSTATE: 0A000
+
+Description: Unlogged sequences cannot be created.
+
+Solution: Do not create unlogged sequences.
+
+GAUSS-01317: "GTM error, could not create sequence"
+
+SQLSTATE: 08006
+
+Description: A GTM error occurs, resulting in a failure in creating a sequence.
+
+Solution: Run **gs_om -t status -detail** to check GTM status. If the GTM is abnormal, troubleshoot it as described in the *Troubleshooting Guide* and create a sequence again.
+
+GAUSS-01318: "GTM error, could not alter sequence"
+
+SQLSTATE: 08006
+
+Description: A GTM error occurs, resulting in a failure in modifying a sequence.
+
+Solution: Run **gs_om -t status -detail** to check GTM status. If the GTM is abnormal, troubleshoot it as described in the *Troubleshooting Guide* and create a sequence again.
+
+GAUSS-01319: "permission denied for sequence %s"
+
+SQLSTATE: 42501
+
+Description: You do not have permission to access the sequence.
+
+Solution: Ensure that you have permission to access the sequence.
+
+GAUSS-01320: "nextval: reached maximum value of sequence '%s' (%s)"
+
+SQLSTATE: 55000
+
+Description: The maximum sequence value is reached.
+
+Solution: Internal system error. Contact technical support.
+
+<br/>
+
+## GAUSS-01321 - GAUSS-01330
+
+<br/>
+
+GAUSS-01321: "nextval: reached minimum value of sequence '%s' (%s)"
+
+SQLSTATE: 55000
+
+Description: The minimum sequence value is reached.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-01323: "lastval is not yet defined in this session"
+
+SQLSTATE: 55000
+
+Description: The **LASTVAL** of the sequence is not defined in this session.
+
+Solution: Ensure that the **LASTVAL** of the sequence is defined in this session.
+
+GAUSS-01324: "setval: value %s is out of bounds for sequence '%s' (%s..%s)"
+
+SQLSTATE: 22003
+
+Description: The configured sequence value is out of the valid range.
+
+Solution: Ensure that the configured sequence value is within the range.
+
+GAUSS-01325: "GTM error, could not obtain sequence value"
+
+SQLSTATE: 08006
+
+Description: A GTM error occurs, resulting in a failure in obtaining the sequence value.
+
+Solution: Run **gs_om -t status -detail** to check GTM status. If the GTM is abnormal, troubleshoot it as described in the *Troubleshooting Guide* and create a sequence again.
+
+GAUSS-01326: "bad magic number in sequence '%s': %08X"
+
+SQLSTATE: XX000
+
+Description: Internal system error. The magic number in the opened sequence table is different from expected.
+
+Solution: The sequence table may be abnormal. Contact technical support.
+
+GAUSS-01327: "INCREMENT must not be zero"
+
+SQLSTATE: 22023
+
+Description: Ensure that the increment in the sequence is not 0.
+
+Solution: The increment in the sequence cannot be 0.
+
+GAUSS-01328: "MINVALUE (%s) must be less than MAXVALUE (%s)"
+
+SQLSTATE: 22023
+
+Description: The minimum sequence value must be less than the maximum value.
+
+Solution: Ensure that the minimum sequence value is less than the maximum value.
+
+GAUSS-01329: "START value (%s) cannot be less than MINVALUE (%s)"
+
+SQLSTATE: 22023
+
+Description: The minimum sequence value must be less than the maximum value.
+
+Solution: Ensure that the initial sequence value is greater than or equal to the minimum value.
+
+GAUSS-01330: "START value (%s) cannot be greater than MAXVALUE (%s)"
+
+SQLSTATE: 22023
+
+Description: The initial sequence value cannot be greater than the maximum value.
+
+Solution: Ensure that the initial sequence value is less than the maximum value.
+
+<br/>
+
+## GAUSS-01331 - GAUSS-01340
+
+<br/>
+
+GAUSS-01331: "RESTART value (%s) cannot be less than MINVALUE (%s)"
+
+SQLSTATE: 22023
+
+Description: In the **RESTART** clause, the value of **RESTART** is less than the minimum value.
+
+Solution: Change the **RESTART** clause to ensure that the value of **RESTART** is greater than or equal to the minimum value.
+
+GAUSS-01332: "RESTART value (%s) cannot be greater than MAXVALUE (%s)"
+
+SQLSTATE: 22023
+
+Description: In the **RESTART** clause, the value of **RESTART** is greater than the maximum value.
+
+Solution: Change the **RESTART** clause to ensure that the value of **RESTART** is equal to or less than the maximum value.
+
+GAUSS-01334: "invalid OWNED BY option"
+
+SQLSTATE: 42601
+
+Description: The specified value in the **OWNED BY** clause is not none.
+
+Solution: Change the **OWNED BY** clause to ensure that the specified value is none.
+
+GAUSS-01335: "sequence must have same owner as table it is linked to"
+
+SQLSTATE: 55000
+
+Description: The sequence and its associated table do not belong to the same owner.
+
+Solution: In the **OWNED BY** clause, ensure that the sequence and its associated table belong to the same owner.
+
+GAUSS-01336: "sequence must be in same schema as table it is linked to"
+
+SQLSTATE: 55000
+
+Description: The sequence and its associated table do not have the same schema.
+
+Solution: In the **OWNED BY** clause, ensure that the sequence and its associated table have the same schema.
+
+GAUSS-01337: "seq_redo: unknown op code %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01338: "seq_redo: failed to add item to page"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01340: "unrecognized attribute for text search parser: %d"
+
+SQLSTATE: XX000
+
+Description: While a full-text retrieval parser is created using the **CREATE TEXT SEARCH CONFIGURATION PARSER** syntax, a specified table fails to be obtained from the **pg_ts_parser** system catalog.
+
+Solution: The attribute information in **pg_ts_parser** is incorrect due to system exception or manual attribute modification. Contact technical support.
+
+<br/>
+
+## GAUSS-01341 - GAUSS-01350
+
+<br/>
+
+GAUSS-01341: "function %s should return type %s"
+
+SQLSTATE: 42P17
+
+Description: The return value type of the specified function is inconsistent with the expected one during the creation of a text search parser.
+
+Solution: While creating a text search parser, modify the return value type of the specified function based on the error message so that the modified value is consistent with that described in the error message.
+
+GAUSS-01342: "must be system admin to create text search parsers"
+
+SQLSTATE: 42501
+
+Description: A non-administrator user creates a text search parser.
+
+Solution: Create a text search parser as a system administrator.
+
+GAUSS-01343: "text search parser parameter '%s' not recognized"
+
+SQLSTATE: 42601
+
+Description: An unrecognized function is defined during the creation of a text search parser.
+
+Solution: Specify the function whose name is **start**/**gettoken**/**end**/**headline**/**lextypes** while creating a text search parser.
+
+GAUSS-01345: "text search parser gettoken method is required"
+
+SQLSTATE: 42P17
+
+Description: The gettoken method is not defined during the creation of a text search parser.
+
+Solution: While creating a text search parser, define the gettoken method.
+
+GAUSS-01347: "text search parser lextypes method is required"
+
+SQLSTATE: 42P17
+
+Description: The lextypes method is not defined during the creation of a text search parser.
+
+Solution: While creating a text search parser, define the lextypes method.
+
+GAUSS-01348: "cache lookup failed for text search parser %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01349: "must be system admin to rename text search parsers"
+
+SQLSTATE: 42501
+
+Description: A non-administrator user changes the text search parser name.
+
+Solution: Change the text search parser name as a system administrator.
+
+<br/>
+
+## GAUSS-01351 - GAUSS-01360
+
+<br/>
+
+GAUSS-01351: "cache lookup failed for text search template %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01352: "text search template '%s' does not accept options"
+
+SQLSTATE: 42601
+
+Description: The init method is not specified but options are specified during the creation or change of a text search dictionary.
+
+Solution: While creating or altering a text search dictionary, specify the init method and options simultaneously, or do not specify options in any cases.
+
+GAUSS-01353: "text search template is required"
+
+SQLSTATE: 42P17
+
+Description: No template is provided during the creation of a text search dictionary.
+
+Solution: Provide a template while creating a text search dictionary.
+
+GAUSS-01354: "cache lookup failed for text search dictionary %u"
+
+SQLSTATE: XX000
+
+Description: The full-text search dictionary corresponding to the ID is not found in the system catalog.
+
+Solution: Check whether the DROP operation is concurrently performed on the dictionary.
+
+GAUSS-01355: "text search dictionary '%s' already exists"
+
+SQLSTATE: 42710
+
+Description: A conflict occurs when changing the text search dictionary name.
+
+Solution: Rename the text search dictionary.
+
+GAUSS-01356: "unrecognized attribute for text search template: %d"
+
+SQLSTATE: XX000
+
+Description: While a full-text search template is created, a specified column fails to be obtained from the **pg_ts_template** system catalog.
+
+Solution: The attribute information in **pg_ts_template** is incorrect due to system exception or manual attribute modification. Contact technical support.
+
+GAUSS-01357: "must be system admin to create text search templates"
+
+SQLSTATE: 42501
+
+Description: A non-administrator user creates a text search template.
+
+Solution: Create a text search template as a system administrator.
+
+GAUSS-01358: "text search template parameter '%s' not recognized"
+
+SQLSTATE: 42601
+
+Description: Unrecognized template parameters are provided during the creation of a text search template.
+
+Solution: Provide init or lexize template parameters only.
+
+GAUSS-01359: "text search template lexize method is required"
+
+SQLSTATE: 42P17
+
+Description: The lexize method provided during the creation of a text search template is invalid.
+
+Solution: Provide a valid lexize method during the creation of a text search template.
+
+GAUSS-01360: "must be system admin to rename text search templates"
+
+SQLSTATE: 42501
+
+Description: A non-administrator user changes the text search template name.
+
+Solution: Change the text search template name as a system administrator.
+
+<br/>
+
+## GAUSS-01361 - GAUSS-01370
+
+<br/>
+
+GAUSS-01362: "cache lookup failed for text search configuration %u"
+
+SQLSTATE: XX000
+
+Description: The full-text search configuration corresponding to the ID is not found in the system catalog.
+
+Solution: Check whether the DROP operation is concurrently performed on the configuration.
+
+GAUSS-01363: "text search configuration parameter '%s' not recognized"
+
+SQLSTATE: 42601
+
+Description: Unrecognized configuration parameters are provided during the creation of a text search configuration.
+
+Solution: Provide parser or copy configuration parameters only.
+
+GAUSS-01364: "cannot specify both PARSER and COPY options"
+
+SQLSTATE: 42601
+
+Description:**PARSER** and **COPY** are specified simultaneously during the creation of a text search configuration.
+
+Solution: Do not specify **PARSER** and **COPY** simultaneously during the creation of a text search configuration.
+
+GAUSS-01365: "text search parser is required"
+
+SQLSTATE: 42P17
+
+Description: The text search parser cannot be found during the creation of a text search configuration because the **PARSER** or **Copy** is incorrectly configured.
+
+Solution: Configure **PARSER** or **COPY** correctly so that the text search parser can be found during the creation of a text search configuration.
+
+GAUSS-01366: "text search configuration '%s' already exists"
+
+SQLSTATE: 42710
+
+Description: A conflict occurs when changing the text search configuration.
+
+Solution: Rename the text search configuration.
+
+GAUSS-01367: "text search configuration '%s' does not exist"
+
+SQLSTATE: 42704
+
+Description: The configuration of the specified name does not exist during the change of the text search configuration.
+
+Solution: Ensure that the configuration of the specified name exists.
+
+GAUSS-01368: "method lextype isn't defined for text search parser %u"
+
+SQLSTATE: XX000
+
+Description: The required prslextype definition in the **pg_ts_parser** system catalog is incorrect.
+
+Solution: The attribute information in **pg_ts_parser** is incorrect. Contact technical support.
+
+GAUSS-01369: "token type '%s' does not exist"
+
+SQLSTATE: 22023
+
+Description: The token type does not exist during the change of the text search configuration (add/alter/drop mapping).
+
+Solution: Specify an existing token type during the change of the text search configuration (add/alter/drop mapping).
+
+GAUSS-01370: "mapping for token type '%s' does not exist"
+
+SQLSTATE: 42704
+
+Description: The mapping for a token type does not exist during the change of the text search configuration (drop mapping).
+
+Solution: Specify an existing mapping during the change of the text search configuration (drop mapping).
+
+<br/>
+
+## GAUSS-01371 - GAUSS-01380
+
+<br/>
+
+GAUSS-01371: "invalid parameter list format: '%s'"
+
+SQLSTATE: 42601
+
+Description: During dictionary deserialization, the list format is invalid, and a space is missing after the equal sign (=).
+
+Solution: Add a space after the equal sign (=) in the list.
+
+GAUSS-01372: "unrecognized deserialize_deflist state: %d"
+
+SQLSTATE: XX000
+
+Description: The deserialization process state machine of the full text retrieval directory cannot be identified.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-01375: "Bad socket."
+
+SQLSTATE: XX000
+
+Description: Internal system error. Socket reading is invalid.
+
+Solution: Ensure that the network connection between GDS and DNs, network environment, and the system ports of nodes are normal.
+
+GAUSS-01376: "Unexpected EOF on GDS connection '%s': %m"
+
+SQLSTATE: XX000
+
+Description: Internal system error. An error occurs while the database exchanges data with GDS.
+
+Solution: Ensure that the network connection between GDS and DNs, network environment, and the system ports of nodes are normal. Check the GDS warning and error logs to identify the cause.
+
+GAUSS-01377: "Unexpected connection EOF from '%s':%m"
+
+SQLSTATE: XX000
+
+Description: Internal system error. An error occurs while the database exchanges data with GDS.
+
+Solution: Ensure that the network connection between GDS and DNs, network environment, and the system ports of nodes are normal. Check the GDS warning and error logs to identify the cause.
+
+GAUSS-01378: "invalid URI '%s'"
+
+SQLSTATE: XX000
+
+Description: The URI of the GDS foreign table is invalid.
+
+Solution: Check and correct the location settings of the GDS foreign table.
+
+GAUSS-01380: "'%s' is a table"
+
+SQLSTATE: 42809
+
+Description: INSTEAD OF triggers are defined on tables.
+
+Solution: Define only BEFORE or AFTER triggers on tables.
+
+<br/>
+
+## GAUSS-01381 - GAUSS-01390
+
+<br/>
+
+GAUSS-01381: "'%s' is a view"
+
+SQLSTATE: 42809
+
+Description: Row-level BEFORE, AFTER trigger, or TRUNCATE triggers are defined on views.
+
+Solution: Define only INSTEAD OF triggers on views.
+
+GAUSS-01382: "'%s' is not a table or view"
+
+SQLSTATE: 42809
+
+Description: Triggers are not defined on tables and views.
+
+Solution: Define triggers only on tables and views.
+
+GAUSS-01383: "TRUNCATE FOR EACH ROW triggers are not supported"
+
+SQLSTATE: 0A000
+
+Description: Row-level TRUNCATE triggers are defined.
+
+Solution: Do not define row-level TRUNCATE triggers.
+
+GAUSS-01385: "INSTEAD OF triggers cannot have WHEN conditions"
+
+SQLSTATE: 0A000
+
+Description:**WHEN** clauses are added to INSTEAD OF triggers.
+
+Solution: Do not add **WHEN** clauses to INSTEAD OF triggers.
+
+GAUSS-01386: "INSTEAD OF triggers cannot have column lists"
+
+SQLSTATE: 0A000
+
+Description: INSTEAD OF triggers are defined on the columns of tables.
+
+Solution: Do not define INSTEAD OF triggers on the columns of tables.
+
+GAUSS-01387: "cannot use subquery in trigger WHEN condition"
+
+SQLSTATE: 0A000
+
+Description: A subquery is used in the **WHEN** clause for triggers.
+
+Solution: Do not use a subquery in the **WHEN** clause for triggers.
+
+GAUSS-01388: "cannot use aggregate function in trigger WHEN condition"
+
+SQLSTATE: 42803
+
+Description: An aggregate function is used in the **WHEN** clause for triggers.
+
+Solution: Do not use an aggregate function in the **WHEN** clause for triggers.
+
+GAUSS-01389: "cannot use window function in trigger WHEN condition"
+
+SQLSTATE: 42P20
+
+Description: A window function is used in the **WHEN** clause for triggers.
+
+Solution: Do not use a window function in the **WHEN** clause for triggers.
+
+GAUSS-01390: "statement trigger's WHEN condition cannot reference column values"
+
+SQLSTATE: 42P17
+
+Description: Column values are quoted in the **WHEN** clause for statement triggers.
+
+Solution: Do not quote column values in the **WHEN** clause for statement triggers.
+
+<br/>
+
+## GAUSS-01391 - GAUSS-01400
+
+<br/>
+
+GAUSS-01391: "INSERT trigger's WHEN condition cannot reference OLD values"
+
+SQLSTATE: 42P17
+
+Description: Old values are quoted in the **WHEN** clause for INSERT triggers.
+
+Solution: Do not quote old values in the **WHEN** clause for INSERT triggers.
+
+GAUSS-01392: "DELETE trigger's WHEN condition cannot reference NEW values"
+
+SQLSTATE: 42P17
+
+Description: New values are quoted in the **WHEN** clause for DELETE triggers.
+
+Solution: Do not quote new values in the **WHEN** clause for DELETE triggers.
+
+GAUSS-01393: "BEFORE trigger's WHEN condition cannot reference NEW system columns"
+
+SQLSTATE: 0A000
+
+Description: New system column values are quoted in the **WHEN** clause for BEFORE triggers.
+
+Solution: Do not quote new system column values in the **WHEN** clause for BEFORE triggers.
+
+GAUSS-01394: "trigger WHEN condition cannot contain references to other relations"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01395: "function %s must return type 'trigger'"
+
+SQLSTATE: 42P17
+
+Description: The return value of the trigger function is not a trigger type.
+
+Solution: Ensure that the return value of the trigger function is a trigger type.
+
+GAUSS-01396: "trigger '%s' for relation '%s' already exists"
+
+SQLSTATE: 42710
+
+Description: The trigger with the same name is defined on the relational table.
+
+Solution: Modify the trigger name so that it is different from the existing one.
+
+GAUSS-01397: "confused about RI update function"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01398: "confused about RI delete function"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01399: "could not find tuple for trigger %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01400: "trigger '%s' for table '%s' does not exist"
+
+SQLSTATE: 42704
+
+Description: Failed to find a trigger by name.
+
+Solution: Specify an existing trigger name.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/15-GAUSS-01401-GAUSS-01500.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/15-GAUSS-01401-GAUSS-01500.md
new file mode 100644
index 0000000000000000000000000000000000000000..a855340e4b8375e09596da888049865597416cfa
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/15-GAUSS-01401-GAUSS-01500.md
@@ -0,0 +1,820 @@
+---
+title: GAUSS-01401 - GAUSS-01500
+summary: GAUSS-01401 - GAUSS-01500
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-01401 - GAUSS-01500
+
+<br/>
+
+## GAUSS-01401 - GAUSS-01410
+
+<br/>
+
+GAUSS-01401: "permission denied: '%s' is a system trigger"
+
+SQLSTATE: 42501
+
+Description: A non-administrator user enables or disables system triggers.
+
+Solution: Enable or disable system triggers as a system administrator.
+
+GAUSS-01402: "tgargs is null in trigger for relation '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01403: "trigger function %u returned null value"
+
+SQLSTATE: 39P01
+
+Description: Internal system error. The trigger function returns null values.
+
+Solution:Contact technical support.
+
+GAUSS-01404: "BEFORE STATEMENT trigger cannot return a value"
+
+SQLSTATE: 39P01
+
+Description: The BEFORE STATEMENT trigger returns a value.
+
+Solution: Ensure that the trigger function returns no value.
+
+GAUSS-01405: "could not serialize access due to concurrent update"
+
+SQLSTATE: 40001
+
+Description: Transactions cannot be serialized due to concurrent update.
+
+Solution: Retry the failed transaction.
+
+GAUSS-01406: "unrecognized heap_lock_tuple status: %u"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01407: "could not find trigger %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01408: "failed to fetch tuple1 for AFTER trigger"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01409: "failed to fetch tuple2 for AFTER trigger"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01410: "relation %u has no triggers"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-01411 - GAUSS-01420
+
+<br/>
+
+GAUSS-01411: "cross-database references are not implemented: '%s.%s.%s'"
+
+SQLSTATE: 0A000
+
+Description: The **SET CONSTRAINT** statement is executed in the current database to set a constraint for another database.
+
+Solution: Do not set a constraint for any other database.
+
+GAUSS-01412: "constraint '%s' is not deferrable"
+
+SQLSTATE: 42809
+
+Description: When the **SET CONSTRAINT** statement is executed, the constraint is deferrable.
+
+Solution: Do not set a non-deferrable constraint to a deferrable one.
+
+GAUSS-01413: "constraint '%s' does not exist"
+
+SQLSTATE: 42704
+
+Description: When the **SET CONSTRAINT** statement is executed, the constraint does not exist.
+
+Solution: Specify the constraint in the **SET CONSTRAINT** statement.
+
+GAUSS-01414: "no triggers found for constraint with OID %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01415: "AfterTriggerSaveEvent() called outside of transaction"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01416: "AfterTriggerSaveEvent() called outside of query"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01418: "XC: Could not find the required row position %d for AFTER ROW trigger"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01419: "XC: Could not find the required row position %d forAFTER ROW trigger"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-01421 - GAUSS-01430
+
+<br/>
+
+GAUSS-01421: "could not obtain lock on relation '%s'"
+
+SQLSTATE: 55P03
+
+Description: The statement is **LOCK TABLE NOWAIT**. The table cannot obtain a lock.
+
+Solution: Modify the statement to **LOCK TABLE**.
+
+GAUSS-01422: "cache lookup failed for access method %u"
+
+SQLSTATE: 22P06
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01423: "operator family '%s' does not exist for access method '%s'"
+
+SQLSTATE: 42704
+
+Description: During **ALTER OPERATOR FAMILY** execution, the access method specified for the operator family does not exist.
+
+Solution: View the existing operator family and ensure that the access method and the specified operator family match.
+
+GAUSS-01424: "operator family '%s' for access method '%s' already exists"
+
+SQLSTATE: 42710
+
+Description: During **CREATE OPERATOR FAMILY** execution, the operator family already exists.
+
+Solution: Ensure that the operator family name is unique.
+
+GAUSS-01425: "must be system admin to create an operator class"
+
+SQLSTATE: 42501
+
+Description: A non-administrator user executes the **CREATE OPERATOR FAMILY** statement.
+
+Solution: Execute the statement as a system administrator.
+
+GAUSS-01426: "invalid operator number %d, must be between 1 and %d"
+
+SQLSTATE: 42P17
+
+Description:**strategy_number** in the **OPERATOR** clause of the **CREATE OPERATOR CLASS** or **ALTER OPERATOR FAMILY** statement is less than 1 or greater than that of **index_method**.
+
+Solution: Ensure that **strategy_number** ranges from 1 to the maximum **strategy_number** of **index_method**.
+
+GAUSS-01427: "invalid procedure number %d, must be between 1 and %d"
+
+SQLSTATE: 42P17
+
+Description:**support_number** in the **FUNCTION** clause of the **CREATE OPERATOR CLASS** or **ALTER OPERATOR FAMILY** statement is less than 1 or greater than that of **index_method**.
+
+Solution: Ensure that **support_number** ranges from 1 to the maximum **strategy_number** of **index_method**.
+
+GAUSS-01428: "storage type specified more than once"
+
+SQLSTATE: 42P17
+
+Description: The **CREATE OPERATOR CLASS** statement contains multiple and same **STORAGE** clauses.
+
+Solution: Ensure that **STORAGE** clauses contained in the **CREATE OPERATOR CLASS** are different.
+
+GAUSS-01429: "unrecognized item type: %d"
+
+SQLSTATE: XX000
+
+Description: The system does not support customized operators.
+
+Solution: Do not create customized operators using the **CREATE OPERATOR** syntax.
+
+GAUSS-01430: "storage type cannot be different from data type for access method '%s'"
+
+SQLSTATE: 42P17
+
+Description:**column_type** differs from **storage_type** specified in the **STORAGE** clause of the **CREATE OPERATOR CLASS** statement.
+
+Solution: Ensure that the data type of **storage_type** and that of **access_method** are the same.
+
+<br/>
+
+## GAUSS-01431 - GAUSS-01440
+
+<br/>
+
+GAUSS-01431: "operator class '%s' for access method '%s' already exists"
+
+SQLSTATE: 42710
+
+Description: During **CREATE OPERATOR CLASS** execution, the defined operator class already exists.
+
+Solution: Ensure that the operator class name is unique.
+
+GAUSS-01432: "could not make operator class '%s' be default for type %s"
+
+SQLSTATE: 42710
+
+Description: During **CREATE OPERATOR CLASS** execution, the default operator class has been created for a data type.
+
+Solution: Ensure that no default operator class has been created for a data type.
+
+GAUSS-01433: "must be system admin to create an operator family"
+
+SQLSTATE: 42501
+
+Description: A non-administrator user executes the **CREATE OPERATOR FAMILY** statement.
+
+Solution: Execute the statement as a system administrator.
+
+GAUSS-01434: "must be system admin to alter an operator family"
+
+SQLSTATE: 42501
+
+Description: A non-administrator user executes the **ADD** or **DROP** clause of the **ALTER OPERATOR FAMILY** statement.
+
+Solution: Execute the clause as a system administrator.
+
+GAUSS-01435: "operator argument types must be specified in ALTER OPERATOR FAMILY"
+
+SQLSTATE: 42601
+
+Description: In the **ADD OPERATOR** clause of the **ALTER OPERATOR FAMILY** statement, the operator parameter type is not specified.
+
+Solution: Specify the operator parameter type.
+
+GAUSS-01436: "STORAGE cannot be specified in ALTER OPERATOR FAMILY"
+
+SQLSTATE: 42601
+
+Description: In the **ADD** clause of the **ALTER OPERATOR FAMILY … ADD** statement, a **STORAGE** clause is specified.
+
+Solution: Do not specify a **STORAGE** clause.
+
+GAUSS-01437: "one or two argument types must be specified"
+
+SQLSTATE: 42601
+
+Description: In the **ADD** or **DROP** clause of the **CREATE OPERATOR CLASS** or **ALTER OPERATOR FAMILY** statement, more than two operators or functions are specified.
+
+Solution: Specify only one or two operators or functions.
+
+GAUSS-01438: "index operators must be binary"
+
+SQLSTATE: 42P17
+
+Description: In the **ADD** clause of the **CREATE OPERATOR CLASS** or **ALTER OPERATOR FAMILY** statement, the specified operator is not a binary operator.
+
+Solution: The specified operator must be a binary operator.
+
+GAUSS-01439: "access method '%s' does not support ordering operators"
+
+SQLSTATE: 42P17
+
+Description: In the **ADD** clause of the **CREATE OPERATOR CLASS** or **ALTER OPERATOR FAMILY** statement, a sort operator is specified, but **access_method** does not support sorting.
+
+Solution: Ensure that **access_method** supports sorting so that operators can be ordered.
+
+GAUSS-01440: "index search operators must return Boolean"
+
+SQLSTATE: 42P17
+
+Description: In the **ADD OPERATOR…FOR SEARCH** clause of the **CREATE OPERATOR CLASS** or **ALTER OPERATOR FAMILY** statement, the returned operator value is not a Boolean type.
+
+Solution: Ensure that the returned operator value is a Boolean type.
+
+<br/>
+
+## GAUSS-01441 - GAUSS-01450
+
+<br/>
+
+GAUSS-01441: "btree comparison procedures must have two arguments"
+
+SQLSTATE: 42P17
+
+Description: In the **ADD FUNCTION** clause of the **CREATE OPERATOR CLASS** or **ALTER OPERATOR FAMILY** statement, the value of **access_method** is B-tree, and a B-tree comparison function is specified, but the number of parameters is not two.
+
+Solution: If a B-tree comparison function is specified, ensure that the number of parameters must be two.
+
+GAUSS-01442: "btree comparison procedures must return integer"
+
+SQLSTATE: 42P17
+
+Description: In the **ADD FUNCTION** clause of the **CREATE OPERATOR CLASS** or **ALTER OPERATOR FAMILY** statement, the value of **access_method** is B-tree, and a B-tree comparison function is specified, but the return value type is not int.
+
+Solution: If a B-tree comparison function is specified, ensure that the return value must be of the int data type.
+
+GAUSS-01443: "btree sort support procedures must accept type 'internal'"
+
+SQLSTATE: 42P17
+
+Description: In the **ADD FUNCTION** clause of the **CREATE OPERATOR CLASS** or **ALTER OPERATOR FAMILY** statement, the value of **access_method** is B-tree, and a B-tree sort support function is specified, but the return value is not internal.
+
+Solution: If a B-tree sort support function is specified, ensure that the return value must be of the internal type.
+
+GAUSS-01444: "btree sort support procedures must return void"
+
+SQLSTATE: 42P17
+
+Description: In the **ADD FUNCTION** clause of the **CREATE OPERATOR CLASS** or **ALTER OPERATOR FAMILY** statement, the value of **access_method** is B-tree, and a B-tree sort support function is specified, but the return value is not void.
+
+Solution: If a B-tree sort support function is specified, ensure that the return value must be of the void type.
+
+GAUSS-01446: "hash procedures must return integer"
+
+SQLSTATE: 42P17
+
+Description: In the ADD FUNCTION clause of the **CREATE OPERATOR CLASS** or **ALTER OPERATOR FAMILY** statement, the value of **access_method** is **hash**, but the return value type is of the int type.
+
+Solution: If **access_method** is a hash type, the return value type must be of the int type.
+
+GAUSS-01447: "associated data types must be specified for index support procedure"
+
+SQLSTATE: 42P17
+
+Description: FOR TYPE data_type is not specified in the **CREATE OPERATOR CLASS** statement. Left and right parameter types are not specified in the **ADD OPERATOR** clause of the **ALTER OPERATOR FAMILY** statement.
+
+Solution: FOR TYPE data_type must be specified. Left and right parameter types must be specified.
+
+GAUSS-01448: "procedure number %d for (%s,%s) appears more than once"
+
+SQLSTATE: 42P17
+
+Description: In the **ADD** or **DROP** clause of the **CREATE OPERATOR CLASS** or **ALTER OPERATOR FAMILY** statement, the same function appears multiple times.
+
+Solution: Ensure that a function does not repeatedly appear in an SQL statement.
+
+GAUSS-01449: "operator number %d for (%s,%s) appears more than once"
+
+SQLSTATE: 42P17
+
+Description: In the **ADD** or **DROP** clause of the **CREATE OPERATOR CLASS** or **ALTER OPERATOR FAMILY** statement, the same operator appears multiple times.
+
+Solution: Ensure that an operator does not repeatedly appear in an SQL statement.
+
+GAUSS-01450: "operator %d(%s,%s) already exists in operator family '%s'"
+
+SQLSTATE: 42710
+
+Description: In the **ADD** or **DROP** clause of the **CREATE OPERATOR CLASS** or **ALTER OPERATOR FAMILY** statement, the operator to be added already exists.
+
+Solution: Ensure that the operator to be added does not exist in the operator family.
+
+<br/>
+
+## GAUSS-01451 - GAUSS-01460
+
+<br/>
+
+GAUSS-01451: "function %d(%s,%s) already exists in operator family '%s'"
+
+SQLSTATE: 42710
+
+Description: In the **ADD** or **DROP** clause of the **CREATE OPERATOR CLASS** or **ALTER OPERATOR FAMILY** statement, the function to be added already exists.
+
+Solution: Ensure that the function to be added does not exist in the operator family.
+
+GAUSS-01452: "operator %d(%s,%s) does not exist in operator family '%s'"
+
+SQLSTATE: 42704
+
+Description: In the **DROP** clause of the **ALTER OPERATOR FAMILY** statement, the specified operator does not exist.
+
+Solution: Ensure that the operator to be dropped exists in the operator family.
+
+GAUSS-01453: "function %d(%s,%s) does not exist in operator family '%s'"
+
+SQLSTATE: 42704
+
+Description: In the **DROP** clause of the **ALTER OPERATOR FAMILY** statement, the specified function does not exist.
+
+Solution: Ensure that the function to be dropped exists in the operator family.
+
+GAUSS-01454: "could not find tuple for amop entry %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01455: "could not find tuple for amproc entry %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01456: "operator class '%s' for access method '%s' already exists in schema '%s'"
+
+SQLSTATE: 42710
+
+Description: A conflict occurs when changing the operator class name.
+
+Solution: Rename the operator class name.
+
+GAUSS-01457: "operator family '%s' for access method '%s' already exists in schema '%s'"
+
+SQLSTATE: 42710
+
+A conflict occurs when changing the operator family name.
+
+Solution: Rename the operator family name.
+
+GAUSS-01458: "SETOF type not allowed for operator argument"
+
+SQLSTATE: 42P13
+
+Description: In the **CREATE OPERATOR** statement, the type of the left or right parameter is **SETOF** (set).
+
+Solution: Ensure that left and right parameters do not belong to the **SETOF** type (set).
+
+GAUSS-01459: "operator procedure must be specified"
+
+SQLSTATE: 42P13
+
+Description: In **CREATE OPERATOR**, no procedure is specified.
+
+Solution: Specify a procedure in the **CREATE OPERATOR** statement.
+
+GAUSS-01460: "at least one of leftarg or rightarg must be specified"
+
+SQLSTATE: 42P13
+
+Description: In the **CREATE OPERATOR** statement, **LEFTARG** and **RIGHTARG** are not specified.
+
+Solution: Specify either **LEFTARG** or **RIGHTARG** or both of them in the **CREATE OPERATOR** statement.
+
+<br/>
+
+## GAUSS-01461 - GAUSS-01470
+
+<br/>
+
+GAUSS-01461: "restriction estimator function %s must return type 'float8'"
+
+SQLSTATE: 42P17
+
+Description: During **CREATE OPERATOR** execution, the value returned by the specified restriction function is not of the float8 type.
+
+Solution: Ensure that the return value is of the float8 type.
+
+GAUSS-01462: "join estimator function %s must return type 'float8'"
+
+SQLSTATE: 42P17
+
+Description: During **CREATE OPERATOR** execution, the value returned by the specified join function is not of the float8 type.
+
+Solution: Ensure that the return value is of the float8 type.
+
+GAUSS-01464: "invalid cursor name: must not be empty"
+
+SQLSTATE: 34000
+
+Description: During **DECLARE**, **CLOSE**, **FETCH**, or **MOVE CURSOR** execution, the cursor name is not specified.
+
+Solution: Specify the cursor name.
+
+GAUSS-01465: "cursor '%s' does not exist"
+
+SQLSTATE: 34000
+
+Description: During **FETCH**, **MOVE**, **CLOSE** **CURSOR**, **CURRENT OF**, or **XML CURSOR** execution, the specified cursor name does not exist.
+
+Solution: Ensure that the specified cursor name exists.
+
+GAUSS-01466: "portal '%s' cannot be run"
+
+SQLSTATE: 55000
+
+Description: Internal error. The portal status is abnormal.
+
+Solution:Contact technical support.
+
+GAUSS-01467: "could not reposition held cursor"
+
+SQLSTATE: 55000
+
+Description: Internal error. The portal status is abnormal.
+
+Solution:Contact technical support.
+
+GAUSS-01468: "unexpected end of tuple stream"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01469: "unrecognized rename stmt type: %d"
+
+SQLSTATE: XX000
+
+Description: The alter object type in the **ALTER..RENAME TO..** syntax is incorrect.
+
+Solution: Correct the alter object type by referring to the *SQL Reference*.
+
+GAUSS-01470: "unrecognized AlterObjectSchemaStmt type: %d"
+
+SQLSTATE: XX000
+
+Description: The alter object type in the **ALTER..SET SCHEMA..** syntax is incorrect.
+
+Solution: Correct the alter object type by referring to the *SQL Reference*.
+
+<br/>
+
+## GAUSS-01471 - GAUSS-01480
+
+<br/>
+
+GAUSS-01471: "cache lookup failed for object %u of catalog '%s'"
+
+SQLSTATE: XX000
+
+Description: During **ALTER..SET TABLESPACE..** execution, alter objects fail to be obtained from the cache.
+
+Solution: The system cache is abnormal. Contact technical support.
+
+GAUSS-01472: "must be system admin to set schema of %s"
+
+SQLSTATE: 42501
+
+Description: A non-administrator user modifies the object **namespace**.
+
+Solution: Modify the object as a system administrator.
+
+GAUSS-01473: "%s already exists in schema '%s'"
+
+SQLSTATE: 42710
+
+Description: The object already exists in the new schema when the user is to modify the object **namespace**.
+
+Solution: Ensure that the object does not exist in the new schema if the user is to modify the object **namespace**.
+
+GAUSS-01474: "unrecognized AlterOwnerStmt type: %d"
+
+SQLSTATE: XX000
+
+Description: The alter object type in the **ALTER..OWNER TO..** syntax is incorrect.
+
+Solution: Correct the alter object type by referring to the *SQL Reference*.
+
+GAUSS-01475: "Table %s does not support sampling operation for analyze."
+
+SQLSTATE: 42703
+
+Description: GDS foreign tables do not support sample analysis.
+
+Solution: Do not perform sample analysis.
+
+GAUSS-01476: "unsupported datatype"
+
+SQLSTATE: XX000
+
+Description: The analyzed column-store table contains unsupported data types.
+
+Solution: Check whether the column-store table is defined properly. If not, create a column-store table again. Check whether this error persists. Contact technical support.
+
+GAUSS-01477: "extension '%s' does not exist"
+
+SQLSTATE: 42704
+
+Description: During **CREATE EXTENSION** or **ALTER EXTENSION** execution, the extension does not exist.
+
+Solution: Ensure that the specified extension exists.
+
+GAUSS-01478: "invalid extension name: '%s'"
+
+SQLSTATE: 22023
+
+During **CREATE EXTENSION** execution, the extension name is invalid.
+
+Solution: Ensure that the extension name cannot be empty, contain "-", start or end with "-", or contain separators, such as / and \\.
+
+GAUSS-01479: "invalid extension version name: '%s'"
+
+SQLSTATE: 22023
+
+Description: During **CREATE EXTENSION** execution, the version name is invalid. During **ALTER EXTENSION** execution, the new version or default version is invalid.
+
+Solution: Ensure that the version, new version, and default_version cannot be empty, contain "-", begin or end with "-", or contain separators, such as / and \\.
+
+<br/>
+
+## GAUSS-01481 - GAUSS-01490
+
+<br/>
+
+GAUSS-01481: "parameter '%s' cannot be set in a secondary extension control file"
+
+SQLSTATE: 42601
+
+Description: During the execution of **CREATE EXTENSION**, **ALTER EXTENSION**, or other extension-related functions, **default_version** or **directory** is specified in the control file.
+
+Solution: Do not specify **default_version** or **directory** in the control file.
+
+GAUSS-01482: "parameter '%s' requires a Boolean value"
+
+SQLSTATE: 22023
+
+Description: During the execution of **CREATE EXTENSION**, **ALTER EXTENSION**, or other extension related functions, **relocatable** or **sysadmin** lacks a Boolean value in the control file.
+
+Solution: Assign a Boolean value to **relocatable** or **sysadmin** in the control file.
+
+GAUSS-01483: "'%s' is not a valid encoding name"
+
+SQLSTATE: 42704
+
+Description: During the execution of **CREATE EXTENSION**, **ALTER EXTENSION**, or other extension related functions, **encoding** lacks a valid name in the control file.
+
+Solution: Specify a valid name to **encoding** in the control file.
+
+GAUSS-01484: "parameter '%s' must be a list of extension names"
+
+SQLSTATE: 22023
+
+Description: During the execution of **CREATE EXTENSION**, **ALTER EXTENSION**, or other extension-related functions, **requires** lacks a list of extension names in the control file.
+
+Solution: Specify a list of extension names to **requires** in the control file.
+
+GAUSS-01485: "unrecognized parameter '%s' in file '%s'"
+
+SQLSTATE: 42601
+
+Description: During the execution of **CREATE EXTENSION**, **ALTER EXTENSION**, or other extension -related functions, an invalid parameter is specified in the control file.
+
+Solution: Specify only the following parameters: directory/default_version/module_pathname/comment/schema/relocatable/sysadmin/encoding/requires
+
+GAUSS-01486: "parameter 'schema' cannot be specified when 'relocatable' is true"
+
+SQLSTATE: 42601
+
+Description: During the execution of **CREATE EXTENSION**, **ALTER EXTENSION**, or other extension-related functions, **relocatable** is set to true and **schema** is also specified in the control file.
+
+Solution: Do not specify **schema** if **relocatable** is true in the control file.
+
+GAUSS-01487: "transaction control statements are not allowed within an extension script"
+
+SQLSTATE: 0A000
+
+Description: During **CREATE EXTENSION** or **ALTER EXTENSION** execution, SQL script files contain transaction control SQL statements.
+
+Solution: Do not use transaction control SQL statements in SQL script files.
+
+GAUSS-01488: "permission denied to create extension '%s'"
+
+SQLSTATE: 42501
+
+Description: During **CREATE EXTENSION** execution, the extension control file is run with system administrator rights. However, the user does not run the file as a system administrator.
+
+Solution: Ensure that the file is run by a system administrator.
+
+GAUSS-01489: "permission denied to update extension '%s'"
+
+SQLSTATE: 42501
+
+Description: During **ALTER EXTENSION** execution, the extension control file is run with system administrator rights. However, the user does not run the file as a system administrator.
+
+Solution: Ensure that the file is run by a system administrator.
+
+GAUSS-01490: "extension '%s' has no update path from version '%s' to version '%s'"
+
+SQLSTATE: 22023
+
+Description: During **CREATE EXTENSION** or **ALTER EXTENSION** execution, the updated path does not exist.
+
+Solution: Ensure that the name and path of the SQL files are correct if **FROM** *old_version* and **UPDATE TO** *new_version* are contained in the statement.
+
+<br/>
+
+## GAUSS-01491 - GAUSS-01500
+
+<br/>
+
+GAUSS-01492: "nested CREATE EXTENSION is not supported"
+
+SQLSTATE: 0A000
+
+Description: During **CREATE EXTENSION** execution, a nested extension exist in the SQL statement.
+
+Solution: Do not create a nested extension in the SQL statement.
+
+GAUSS-01493: "unrecognized option: %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01494: "version to install must be specified"
+
+SQLSTATE: 22023
+
+Description: During **CREATE/ALTER EXTENSION** execution, **new version** is not specified in the statement, and **default version** is not specified in the control file.
+
+Solution: Specify **new version** in the statement or **default version** in the control file.
+
+GAUSS-01495: "FROM version must be different from installation target version '%s'"
+
+SQLSTATE: 22023
+
+Description: During **CREATE EXTENSION** execution, the from version number and specified version number are the same.
+
+Solution: Ensure that the from version number and specified version number are different.
+
+GAUSS-01496: "extension '%s' must be installed in schema '%s'"
+
+SQLSTATE: 0A000
+
+Description: During **CREATE EXTENSION** execution, the schema specified in the **WITH SCHEMA** statement is different from that specified in the control file.
+
+Solution: Ensure that the schema specified in the **WITH SCHEMA** clause is the same as that specified in the control file.
+
+GAUSS-01497: "there is no default creation target"
+
+SQLSTATE: XX000
+
+Description:**SCHEMA** is not specified in the **CREATE EXTENSION** statement, and the default **SCHEMA** is used, which is empty.
+
+Solution: The default **SCHEMA** is empty, the current system is abnormal, or the current directory of **SCHEMA** is deleted manually. Contact technical support.
+
+GAUSS-01498: "required extension '%s' is not installed"
+
+SQLSTATE: 42704
+
+Description: During **CREATE EXTENSION** or **ALTER EXTENSION** execution, a required extension as specified in the control file is not installed.
+
+Solution: Ensure that all extensions specified in the control file are installed and check them using **\dx**.
+
+GAUSS-01499: "cannot drop extension '%s' because it is being modified"
+
+SQLSTATE: 55000
+
+Description: During **DROP EXTENSION** execution, an extension is being modified by another session.
+
+Solution: Ensure that extensions cannot be modified by other sessions.
+
+GAUSS-01500: "pg_extension_config_dump() can only be called from an SQL script executed by CREATE EXTENSION"
+
+SQLSTATE: 0A000
+
+Description: During **CREATE EXTENSION** execution, **pg_extension_config_dump** is not executed.
+
+Solution: Execute **pg_extension_config_dump** in the **CREATE EXTENSION** statement.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/16-GAUSS-01501-GAUSS-01600.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/16-GAUSS-01501-GAUSS-01600.md
new file mode 100644
index 0000000000000000000000000000000000000000..a572f64e1f54fc6a644de59f5ee000f3451dff19
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/16-GAUSS-01501-GAUSS-01600.md
@@ -0,0 +1,644 @@
+---
+title: GAUSS-01501 - GAUSS-01600
+summary: GAUSS-01501 - GAUSS-01600
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-01501 - GAUSS-01600
+
+<br/>
+
+## GAUSS-01501 - GAUSS-01510
+
+<br/>
+
+GAUSS-01501: "OID %u does not refer to a table"
+
+SQLSTATE: 42P01
+
+Description: *Parameter1* of the **pg_extension_config_dump()** function is not defined in the **pg_class** table.
+
+Solution: Ensure that *parameter1* is defined in the **pg_class** table.
+
+GAUSS-01502: "table '%s' is not a member of the extension being created"
+
+SQLSTATE: 55000
+
+Description: *Parameter1* of the **pg_extension_config_dump()** function is not a member of the extension being created.
+
+Solution: Ensure that *parameter1* is a member of the extension being created.
+
+GAUSS-01503: "extension with oid %u does not exist"
+
+SQLSTATE: XX000
+
+Description: Failed to obtain tuples in the **pg_extension** system catalog from the cache based on the OID of the current extension.
+
+Solution: The system cache is abnormal. Contact technical support.
+
+GAUSS-01504: "extconfig is not a 1-D Oid array"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01505: "extconfig and extcondition arrays do not match"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01507: "extension name cannot be qualified"
+
+SQLSTATE: 42601
+
+Description: During **ALTER EXTENSION SET SCHEMA** execution, a scheme name is added before the extension name.
+
+Solution: Do not add a scheme name.
+
+GAUSS-01508: "cannot move extension '%s' into schema '%s' because the extension contains the schema"
+
+SQLSTATE: 55000
+
+Description: During **ALTER EXTENSION SET SCHEMA** execution, the new schema is a member of the current extension.
+
+Solution: Ensure that the new schema is not a member of the current extension.
+
+GAUSS-01509: "extension '%s' does not support SET SCHEMA"
+
+SQLSTATE: 0A000
+
+Description: During **ALTER EXTENSION SET SCHEMA** execution, **relocatable** of the current extension is false.
+
+Solution: Ensure that **relocatable** of an extension is true.
+
+<br/>
+
+## GAUSS-01511 - GAUSS-01520
+
+<br/>
+
+GAUSS-01511: "nested ALTER EXTENSION is not supported"
+
+SQLSTATE: 0A000
+
+Description:**ALTER EXTENSION UPDATE** is executed for multiple times within a transaction.
+
+Solution: Execute the statement only once within a transaction.
+
+GAUSS-01513: "%s is already a member of extension '%s'"
+
+SQLSTATE: 55000
+
+Description: During **ALTER EXTENSION ADD** execution, the object to be added is already a member of the extension. During **CREATE EXTENSION** execution, a specific object created in the extension SQL script is already a member of other extensions. "
+
+Solution: Add an object that is not a member of the extension. Ensure that all objects created in the extension SQL script are not members of other extensions. "
+
+GAUSS-01514: "cannot add schema '%s' to extension '%s' because the schema contains the extension"
+
+SQLSTATE: 55000
+
+Description: During **ALTER EXTENSION ADD** execution, the added schema is the one that contains the extension.
+
+Solution: Add a schema that does not contain the extension.
+
+GAUSS-01515: "%s is not a member of extension '%s'"
+
+SQLSTATE: 55000
+
+Description: During **ALTER EXTENSION DROP** execution, the object to be deleted is not a member of the extension.
+
+Solution: Delete an object that is a member of the extension.
+
+GAUSS-01517: "cache lookup failed for extension %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01518: "no security label providers have been loaded"
+
+SQLSTATE: 22023
+
+Description: During **SECURITY LABEL** execution, no related extensions are loaded.
+
+Solution: Before executing the statement, load related extensions.
+
+GAUSS-01519: "must specify provider when multiple security label providers have been loaded"
+
+SQLSTATE: 22023
+
+Description: During **SECURITY LABEL** execution, no security labels are specified.
+
+Solution: Before executing the statement, specify security labels.
+
+GAUSS-01520: "security label provider '%s' is not loaded"
+
+SQLSTATE: 22023
+
+Description: During **SECURITY LABEL** execution, the specified security label is not loaded.
+
+Solution: Before executing the statement, only specify security lables that can be loaded.
+
+<br/>
+
+## GAUSS-01521 - GAUSS-01530
+
+<br/>
+
+GAUSS-01521: "can't negate an empty subexpression"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01522: "unrecognized boolop: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01524: "could not find attribute %d in subquery targetlist"
+
+SQLSTATE: XX000
+
+Description: The column returned for the subquery is empty.
+
+Solution: Check whether the query result contains a null value.
+
+GAUSS-01525: "so where are the outer joins?"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01527: "reached base rel"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01528: "could not find join node %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01529: "subquery cannot be result relation"
+
+SQLSTATE: XX000
+
+Description: The subquery is used as the result table.
+
+Solution: Use a non-subquery as the result table.
+
+GAUSS-01530: "unrecognized command_type: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-01531 - GAUSS-01540
+
+<br/>
+
+GAUSS-01531: "targetlist is not sorted correctly"
+
+SQLSTATE: XX000
+
+Description: The sequence of output columns is incorrect.
+
+Solution: Ensure that the sequence of input columns is the same as insert or update columns.
+
+GAUSS-01532: "unexpected outer reference in set operation subquery"
+
+SQLSTATE: XX000
+
+Description: The setop operation involves cross-reference.
+
+Solution: Ensure that no column involved in the setop operation is referenced by other subqueries.
+
+GAUSS-01533: "only UNION queries can be recursive"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01534: "could not implement recursive UNION"
+
+SQLSTATE: 0A000
+
+Description: The recursive union is not executed.
+
+Solution: Adjust corresponding columns so that all of them can be distributed in hash mode.
+
+GAUSS-01535: "could not implement %s"
+
+SQLSTATE: 0A000
+
+Description:**UNION**, **INTERSECT**, or **EXCEPT** is executed.
+
+Solution: Ensure that all columns related to **UNION**, **INTERSECT**, or **EXCEPT** can be distributed in both hash mode and sort mode.
+
+GAUSS-01536: "could not find inherited attribute '%s' of relation '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01537: "attribute '%s' of relation '%s' does not match parent's type"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01538: "attribute '%s' of relation '%s' does not match parent's collation"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01539: "attribute %d of relation '%s' does not exist"
+
+SQLSTATE: XX000
+
+Description: The column does not exist.
+
+Solution: Query existing columns only.
+
+GAUSS-01540: "failed to join all relations together"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-01541 - GAUSS-01550
+
+<br/>
+
+GAUSS-01541: "minimum_count not set"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01542: "neither shared nor minimum number nor random edge found"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01543: "no edge found"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01547: "could not find plan for CTE '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01549: "failed to build any %d-way joins"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-01551 - GAUSS-01560
+
+<br/>
+
+GAUSS-01551: "a join rel requires both the left path and right path"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01552: "can not create remote path for ranges of type %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01553: "can not create remote path for relation of type %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01554: "No node list provided for remote query path"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01557: "operator %u is not a valid ordering operator"
+
+SQLSTATE: 42704
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01558: "volatile EquivalenceClass has no sortref"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-01561 - GAUSS-01570
+
+<br/>
+
+GAUSS-01563: "wrong number of index expressions"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01564: "unsupported indexqual type: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01566: "could not find member %d(%u,%u) of opfamily %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01570: "no = operator for opfamily %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-01571 - GAUSS-01580
+
+<br/>
+
+GAUSS-01571: "no >= operator for opfamily %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01572: "no < operator for opfamily %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01576: "unexpected datatype in string_to_const: %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01577: "left and right pathkeys do not match in mergejoin"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01579: "Unrecognised command type %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01580: "Postgres-XC does not support this distribution type yet"
+
+SQLSTATE: 0A000
+
+Description: The redistribution data type is not supported.
+
+Solution: Currently, data of some types, such as float and double, cannot be redistributed. Modify the data types in this column.
+
+<br/>
+
+## GAUSS-01581 - GAUSS-01590
+
+<br/>
+
+GAUSS-01581: "predicate_classify returned a bogus value"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01582: "too late to create a new PlaceHolderInfo"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01583: "rel %d already exists"
+
+SQLSTATE: XX000
+
+Description: The table already exists.
+
+Solution: Rename the table.
+
+GAUSS-01584: "no relation entry for relid %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01585: "unexpected node type in reltargetlist: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01587: "cannot access temporary or unlogged relations during recovery"
+
+SQLSTATE: 0A000
+
+Description: Internal system error. During recovery, the temporary table or unlogged table cannot be accessed.
+
+Solution:Contact technical support.
+
+GAUSS-01588: "unsupported RTE kind %d in build_physical_tlist"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01589: "invalid restriction selectivity: %f"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01590: "invalid join selectivity: %f"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-01591 - GAUSS-01600
+
+<br/>
+
+GAUSS-01591: "WindowFunc contains out-of-range winref %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01592: "cannot commute non-binary-operator clause"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01593: "could not find commutator for operator %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01595: "unexpected RowCompare type: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01596: "unrecognized nulltesttype: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01598: "function's resolved result type changed during planning"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01599: "null prosrc for function %u"
+
+SQLSTATE: 42P13
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01600: "unexpected paramkind: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/17-GAUSS-01601-GAUSS-01700.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/17-GAUSS-01601-GAUSS-01700.md
new file mode 100644
index 0000000000000000000000000000000000000000..26d010fda694a05cd10dad692a82ce24a50457fd
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/17-GAUSS-01601-GAUSS-01700.md
@@ -0,0 +1,646 @@
+---
+title: GAUSS-01601 - GAUSS-01700
+summary: GAUSS-01601 - GAUSS-01700
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-01601 - GAUSS-01700
+
+<br/>
+
+## GAUSS-01601 - GAUSS-01610
+
+<br/>
+
+GAUSS-01601: "invalid paramid: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01602: "Upper-level Var found where not expected"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01603: "Upper-level Aggref found where not expected"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01604: "Aggref found where not expected"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01605: "Upper-level PlaceHolderVar found where not expected"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01606: "PlaceHolderVar found where not expected"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01607: "could not devise a query plan for the given query"
+
+SQLSTATE: XX000
+
+Description: The plan fails to be generated.
+
+Solution: Check whether the query is proper, for example, whether the join mode is proper.
+
+GAUSS-01608: "ORDER/GROUP BY expression not found in targetlist"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01610: "relation %s is not partitioned"
+
+SQLSTATE: XX000
+
+Description: Internal system error. Check whether the index contains invalid partitions.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-01611 - GAUSS-01620
+
+<br/>
+
+GAUSS-01611: "no local indexes found for partition %s"
+
+SQLSTATE: 42809
+
+Description: Internal system error. Index partitions are not defined in table partitions.
+
+Solution:Contact technical support.
+
+GAUSS-01612: "bit map error when searching for unusable index partition"
+
+SQLSTATE: XX000
+
+Description: Internal system error. Bit errors occur when you search for invalid index partitions.
+
+Solution: Roll back the transaction.
+
+GAUSS-01613: "bit map error after searching for unusable index partition"
+
+SQLSTATE: XX000
+
+Description: Internal system error. Bit errors occur when you search for invalid index partitions.
+
+Solution: Roll back the transaction.
+
+GAUSS-01614: "relation of oid='%u' is not partitioned table"
+
+SQLSTATE: XX000
+
+Description: The table specified in the **PARTITION FOR** clause is not a partitioned one.
+
+Solution: Ensure that the table specified in the **PARTITION FOR** clause is a partitioned one.
+
+GAUSS-01616: "fail to find partition with oid %u for partitioned table %u"
+
+SQLSTATE: 42P01
+
+Description: Internal system error. The partition specified in the partitioned table cannot be found.
+
+Solution:Contact technical support.
+
+GAUSS-01617: "partitionPruningForExpr: parameter can not be null"
+
+SQLSTATE: XX000
+
+Description: Internal system error. During pruning, the returned pruning parameter is null.
+
+Solution:Contact technical support.
+
+GAUSS-01618: "get null for partition pruning"
+
+SQLSTATE: XX000
+
+Description: Internal system error. During pruning, the returned internal pruning result is null.
+
+Solution:Contact technical support.
+
+GAUSS-01619: "For every node in same expression, pruning result's intervalOffset MUST be same"
+
+SQLSTATE: XX000
+
+Description: Internal system error. For nodes in the same expression, the sequence number of their minimum interval partitions in the pruning result must be the same.
+
+Solution:Contact technical support.
+
+GAUSS-01620: "pruning result(PartitionIdentifier) is invalid"
+
+SQLSTATE: XX000
+
+Description: Internal system error. The pruning result filtered out based on the specified range is invalid.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-01621 - GAUSS-01630
+
+<br/>
+
+GAUSS-01621: "unsupported partition key column range mode"
+
+SQLSTATE: 42P17
+
+Description: Internal system error. An internal structure based on the partition sequence number is invalid.
+
+Solution:Contact technical support.
+
+GAUSS-01623: "Unupport partition strategy '%c'"
+
+SQLSTATE: XX000
+
+Description: Internal system error. The partitioning policy is not supported.
+
+Solution:Contact technical support.
+
+GAUSS-01624: "Expected TargetEntry node, but got node with type %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01625: "can not generate shippable query for base relations of type other than plain tables"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01626: "can not handle multiple relations in a single baserel"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01627: "a join relation path should have both left and right paths"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01628: "unexpected unshippable quals in JOIN tree"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01629: "join with unshippable join clauses can not be shipped"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-01631 - GAUSS-01640
+
+<br/>
+
+GAUSS-01631: "Creating remote query plan for relations of type %d is not supported"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01632: "expected a VAR node but got node of type %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01633: "No distribution information found for remote query path"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01634: "creating remote query plan for relations of type %d is not supported"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01635: "Unexpected node type: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01637: "Duplicate node_ids not expected in source target list"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01638: "Duplicate ctids not expected in source target list"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01640: "cache lookup failed for attribute %s of relation %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-01641 - GAUSS-01650
+
+<br/>
+
+GAUSS-01641: "Source data plan's target list does not contain ctid colum"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01642: "Unexpected command type: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01645: "column store doesn't support backward scan"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01646: "Distributed key column can't be updated in current version"
+
+SQLSTATE: 42P10
+
+Description: The distribution column is updated.
+
+Solution: Do not update the distribution column.
+
+GAUSS-01647: "could not find array type for datatype %s"
+
+SQLSTATE: XX000
+
+Description: The data type does not support the array sublink mode.
+
+Solution: Modify the subquery type.
+
+GAUSS-01648: "unexpected PARAM_SUBLINK ID: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01649: "unexpected outer reference in CTE query"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01650: "could not find plan for CteScan referencing plan ID %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-01661 - GAUSS-01670
+
+<br/>
+
+GAUSS-01661: "failed to deconstruct sort operators into partitioning/ordering operators"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01662: "failed to assign all NestLoopParams to plan nodes"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01663: "MergeAppend child's targetlist doesn't match MergeAppend"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01664: "failed to find unique expression in subplan tlist"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01665: "could not find compatible hash operator for operator %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01666: "could not find ordering operator for equality operator %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01667: "could not find param ID for CTE '%s'"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01668: "unsupported RTE kind %d in build_one_column_tlist"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01669: "outer pathkeys do not match mergeclauses"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01670: "inner pathkeys do not match mergeclauses"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-01671 - GAUSS-01680
+
+<br/>
+
+GAUSS-01671: "indexqual clause is not binary opclause"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01672: "inconsistent results from adjust_rowcompare_for_index"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01673: "indexorderby clause is not binary opclause"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01674: "unsupported indexorderby type: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01675: "index key does not match expected index column"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01676: "could not find pathkey item to sort"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01678: "Fail to create path for partitioned table by the lack of info"
+
+SQLSTATE: XX000
+
+Description:Internal system error. The scan operator is set incorrectly.
+
+Solution:Contact technical support.
+
+GAUSS-01679: "Only Scan operator have patition attribute"
+
+SQLSTATE: XX000
+
+Description: Non-scan operators are set in a partitioned table
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-01681 - GAUSS-01690
+
+<br/>
+
+GAUSS-01682: "NestLoopParam was not reduced to a simple Var"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01683: "variable not found in subplan target lists"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01684: "variable not found in subplan target list"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01685: "variable not found in base remote scan target lists"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01687: "SELECT FOR UPDATE/SHARE cannot be applied to the nullable side of an outer join"
+
+SQLSTATE: 0A000
+
+Description: The **SELECT FOR UPDATE/SHARE** statement is used to a table whose outer join is null.
+
+Solution:Contact technical support.
+
+GAUSS-01688: "JOIN qualification cannot refer to other relations"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-01691 - GAUSS-01700
+
+<br/>
+
+GAUSS-01692: "cannot insert into view '%s'"
+
+SQLSTATE: 55000
+
+Description: Data is inserted into a view.
+
+Solution: Do not insert data into any view.
+
+GAUSS-01693: "cannot update view '%s'"
+
+SQLSTATE: 55000
+
+Description: The view cannot be updated.
+
+Solution: Use the **ON UPDATE DO INSTEAD** rule or **INSTEAD OF UPDATE** trigger.
+
+GAUSS-01694: "cannot delete from view '%s'"
+
+SQLSTATE: 55000
+
+Description: Data cannot be deleted from the view.
+
+Solution: Use the **ON UPDATE DO INSTEAD** rule or **INSTEAD OF UPDATE** trigger.
+
+GAUSS-01697: "invalid fork name"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01698: "invalid relation file path %s."
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01699: "invalid relation file path %s: %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01700: "invalid relpersistence: %c"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/18-GAUSS-01701-GAUSS-01800.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/18-GAUSS-01701-GAUSS-01800.md
new file mode 100644
index 0000000000000000000000000000000000000000..340b99b008313328172bc93879c7ffe8b515dfd7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/18-GAUSS-01701-GAUSS-01800.md
@@ -0,0 +1,750 @@
+---
+title: GAUSS-01701 - GAUSS-01800
+summary: GAUSS-01701 - GAUSS-01800
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-01701 - GAUSS-01800
+
+<br/>
+
+## GAUSS-01701 - GAUSS-01710
+
+<br/>
+
+GAUSS-01702: "permission denied to create '%s.%s'"
+
+SQLSTATE: 42501
+
+Description: Creating a heap table failed because the creating mode or the database namespace is not allowed by the system.
+
+Solution: Ensure that the creating mode or the database namespace is correct.
+
+GAUSS-01703: "column name '%s' specified more than once"
+
+SQLSTATE: 42701
+
+Description: Duplicate attribute names exist.
+
+Solution: Ensure that the attribute name is unique.
+
+GAUSS-01704: "column '%s' has pseudo-type %s"
+
+SQLSTATE: 42P16
+
+Description: Attribute check failed because unknown attribute types exist.
+
+Solution: Ensure that the current attribute type is supported by the system.
+
+GAUSS-01705: "composite type %s cannot be made a member of itself"
+
+SQLSTATE: 42P16
+
+Description: The name of the composite type is the same as that of the current type, which is not allowed.
+
+Solution: Ensure that the name of the composite data type is unique.
+
+GAUSS-01706: "no collation was derived for column '%s' with collatable type %s"
+
+SQLSTATE: 42P16
+
+Description: Creating a heap table failed because the attribute column supports attcollation but the attcollation is invalid.
+
+Solution: Ensure that the collation definition in the attribute column is valid when the table is created.
+
+GAUSS-01707: "Invalid distribution column specified"
+
+SQLSTATE: 42P16
+
+Description: The attribute names used to mark distribution status is not contained in the attribute column. As a result, the number of attribute columns is equal to or less than 0.
+
+Solution: Ensure that the attribute name in the **DISTRIBUTE BY** statement exists in the attribute column defined in the table.
+
+GAUSS-01708: "Column %s is not a hash distributable data type"
+
+SQLSTATE: 42809
+
+Description: The data type cannot be distributed in hash mode.
+
+Solution: Ensure that the data used in the current column can be distributed in hash mode.
+
+GAUSS-01709: "Column %s is not modulo distributable data type"
+
+SQLSTATE: 42809
+
+Description: The data type cannot be distributed in modulo mode.
+
+Solution: Ensure that the data used in the current column can be distributed in modulo mode.
+
+GAUSS-01710: "Invalid distribution type"
+
+SQLSTATE: 42P16
+
+Description: The system does not support the specified distribution type.
+
+Solution: Ensure that the distribution type in use is supported by the system.
+
+<br/>
+
+## GAUSS-01711 - GAUSS-01720
+
+<br/>
+
+GAUSS-01712: "PGXC node %s: not a Datanode"
+
+SQLSTATE: 42601
+
+Description: The node specified by this name is not a DN.
+
+Solution: Ensure that the node ID is correct and the system runs properly.
+
+GAUSS-01713: "PGXC Group %s: group not defined"
+
+SQLSTATE: 42704
+
+Description: The node group corresponding to **group_name** does not exist.
+
+Solution: Check whether the **group_name** called is correct, or whether the group is correctly created.
+
+GAUSS-01714: "shared relations must be placed in pg_global tablespace"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01715: "could not find attrdef tuple for relation %u attnum %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01716: "could not find tuple for attrdef %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01717: "could not remove file '%s': %m"
+
+SQLSTATE: XX000
+
+Description: Failed to delete the corresponding error message table.
+
+Solution: Check whether you have that permission.
+
+GAUSS-01718: "cache lookup failed for foreign table %u"
+
+SQLSTATE: XX000
+
+Description: Failed to find the required foreign-data wrapper.
+
+Solution: Check whether the settings of GDS, HDFS foreign tables, Roach, and OBS are correct.
+
+GAUSS-01719: "cache lookup failed for partitioned table %u in pg_partition"
+
+SQLSTATE: XX000
+
+Description: The corresponding tuple cannot be found in a partitioned table.
+
+Solution: Ensure that the object corresponding to **relid** is a partitioned table. If it is, check the status of its tuples.
+
+GAUSS-01720: "check constraint '%s' already exists"
+
+SQLSTATE: 42710
+
+Description: The constraint to be added already exists.
+
+Solution: Ensure that the constraint to be added is unique.
+
+<br/>
+
+## GAUSS-01721 - GAUSS-01730
+
+<br/>
+
+GAUSS-01721: "null conbin for rel %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01722: "constraint '%s' conflicts with non-inherited constraint on relation '%s'"
+
+SQLSTATE: 42P17
+
+Description: The new constraint conflicts with non-inherent constraints in the table.
+
+Solution: Ensure that the type of the new constraint and that of the existing ones are consistent.
+
+GAUSS-01723: "cannot use column references in default expression"
+
+SQLSTATE: 42P10
+
+Description: The default expression contains table attribute variables.
+
+Solution: Ensure that the default expression in the SQL statement does not contain attribute variables.
+
+GAUSS-01724: "default expression must not return a set"
+
+SQLSTATE: 42804
+
+Description: The default expression returns a set, which is not allowed.
+
+Solution: Ensure that the default expression in the SQL statement does not return a set.
+
+GAUSS-01725: "cannot use subquery in default expression"
+
+SQLSTATE: 0A000
+
+Description: The default expression contains subquery expressions, which is not allowed.
+
+Solution: Ensure that the default expression in the SQL statement does not contain subquery expressions.
+
+GAUSS-01727: "cannot use window function in default expression"
+
+SQLSTATE: 42P20
+
+Description: The default expression contains window functions, which is not allowed.
+
+Solution: Ensure that the default expression in the SQL statement does not contain window functions.
+
+GAUSS-01728: "column '%s' is of type %s but default expression is of type %s"
+
+SQLSTATE: 42804
+
+Description: The type of the column attribute is different from that of the value returned by the corresponding default expression.
+
+Solution: Ensure that the expression is correct. If not, rewrite the expression.
+
+GAUSS-01729: "only table '%s' can be referenced in check constraint"
+
+SQLSTATE: 42P10
+
+Description: Only the constraint of a specific table can be checked. Cross-table check is unsupported.
+
+Solution: Ensure that the table name corresponding to the constraint is correct. Alternatively, ensure that the table specified in the expression resolved is consistent with the actual one.
+
+GAUSS-01730: "unsupported ON COMMIT and foreign key combination"
+
+SQLSTATE: 0A000
+
+Description: The foreign key of **Table 2** is the primary key of **Table 1**, indicating that **Table 2** references **Table 1**. However, their COMMIT settings are different.
+
+Solution: Ensure that their COMMIT settings are consistent.
+
+<br/>
+
+## GAUSS-01731 - GAUSS-01740
+
+<br/>
+
+GAUSS-01731: "cannot truncate a table referenced in a foreign key constraint"
+
+SQLSTATE: 0A000
+
+Description: The table referenced by a foreign key constraint cannot be truncated.
+
+Solution: Ensure that the current table to be truncated is referenced by another table. If it is, delete both of them.
+
+GAUSS-01732: "buildPartitionKey(): partKeys specified NONE IS found'"
+
+SQLSTATE: 22015
+
+Description: The **partKeys** corresponding to attributes of the table is not found.
+
+Solution: Ensure that the correct **partKeys** is provided when the partitioned table is created.
+
+GAUSS-01733: "cache lookup failed for partition %u"
+
+SQLSTATE: XX000
+
+Description: Failed to find the partition in the cache.
+
+Solution: Ensure that the partition is valid.
+
+GAUSS-01734: "missing definition for new partition"
+
+SQLSTATE: XX000
+
+Description: The new partition is not defined.
+
+Solution: Ensure that the partition is correctly defined before it is added.
+
+GAUSS-01735: "boundary not defined for new partition"
+
+SQLSTATE: XX000
+
+Description: The boundary is not defined in the new partition.
+
+Solution: Ensure that the boundary is correctly defined in the new partition.
+
+GAUSS-01736: "too many partition keys, allowed is %d"
+
+SQLSTATE: XX000
+
+Description: The number of partitions added exceeds the maximum.
+
+Solution: Ensure that the number of newly added partitions does not exceed the maximum.
+
+GAUSS-01737: "number of partition key columns MUST less or equal than 4"
+
+SQLSTATE: XX000
+
+Description: The number of attribute columns of a partition must be equal to or less than 4.
+
+Solution: Ensure that the number of attribute (**partition key**) columns of the original partitioned table is within the allowed range.
+
+GAUSS-01738: "inserted partition key does not map to any table partition"
+
+SQLSTATE: P0002
+
+Description: The partition key of the inserted tuple does not map to any existing partition.
+
+Solution: Check whether the data inserted is out of the partition range of the partitioned table.
+
+GAUSS-01739: "Inserted partition key does not map to any table partition"
+
+SQLSTATE: P0002
+
+Description: The newly inserted partition key cannot be recognized.
+
+Solution: Ensure that the inserted partition key maps to the current partition.
+
+<br/>
+
+## GAUSS-01741 - GAUSS-01750
+
+<br/>
+
+GAUSS-01742: "cannot have more than %d keys in a cluster key"
+
+SQLSTATE: 54011
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01743: "partial cluster key constraint does not support row/timeseries store"
+
+SQLSTATE: 42P16
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01744: "'%s' is not a valid operator name"
+
+SQLSTATE: 42602
+
+Description: The operator name to be created is invalid.
+
+Solution: Ensure that the name length is correct and the name contains invalid characters or identifiers. For details, see the **validOperatorName** function.
+
+GAUSS-01745: "only binary operators can have commutators"
+
+SQLSTATE: 42P13
+
+Description: In the event of left and right variables in an expression, only binary operators can contain commutators.
+
+Solution: Ensure that the operators to be created are binary ones.
+
+GAUSS-01746: "only binary operators can have join selectivity"
+
+SQLSTATE: 42P13
+
+Description: In the event of left and right variables in an expression, only the return values of binary operators can be used to calculate the join selectivity.
+
+Solution: Ensure that the operators to be created are binary ones.
+
+GAUSS-01748: "only binary operators can hash"
+
+SQLSTATE: 42P13
+
+Description: If left and right variables exist in an expression, only binary operators can be used for the **merge join** path.
+
+Solution: Ensure that the operators to be created are binary ones.
+
+GAUSS-01749: "only boolean operators can have negators"
+
+SQLSTATE: 42P13
+
+Description: Only Boolean operators support negators.
+
+Solution: Ensure that the operators to be created are Boolean ones.
+
+GAUSS-01750: "only boolean operators can have restriction selectivity"
+
+SQLSTATE: 42P13
+
+Description: Only the return values of Boolean operators can be used to calculate the join selectivity.
+
+Solution: Ensure that the operators to be created are Boolean ones.
+
+<br/>
+
+## GAUSS-01751 - GAUSS-01760
+
+<br/>
+
+GAUSS-01751: "only boolean operators can have join selectivity"
+
+SQLSTATE: 42P13
+
+Description: Only the return values of Boolean operators can be used to calculate the join selectivity.
+
+Solution: Ensure that the operators to be created are Boolean ones.
+
+GAUSS-01753: "only boolean operators can hash"
+
+SQLSTATE: 42P13
+
+Description: Only the return values of Boolean operators can be used to generate the **hash** path.
+
+Solution: Ensure that the operators to be created are Boolean ones.
+
+GAUSS-01754: "operator %s already exists"
+
+SQLSTATE: 42723
+
+Description: The operator already exists.
+
+Solution: Ensure that the operator to be created is unique.
+
+GAUSS-01755: "operator cannot be its own negator or sort operator"
+
+SQLSTATE: 42P13
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+G
+
+GAUSS-01758: "large object %u does not exist"
+
+SQLSTATE: 42704
+
+Description: The current large object name cannot be mapped to an actual object.
+
+Solution: Ensure that a large object of the same name has already been created, and the object is dropped during execution.
+
+GAUSS-01759: "unrecognized objtype: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01760: "must specify relation and object name"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-01761 - GAUSS-01770
+
+<br/>
+
+GAUSS-01761: "column name must be qualified"
+
+SQLSTATE: 42601
+
+Description: The attribute name in the object must be specified and described.
+
+Solution:Contact technical support.
+
+GAUSS-01762: "must be owner of large object %u"
+
+SQLSTATE: 42501
+
+Description: The ownership of the large object data is incorrect.
+
+Solution: Run **get_object_address** to obtain the object ID and ensure that the ownership is correct.
+
+GAUSS-01763: "must be system admin"
+
+SQLSTATE: 42501
+
+Description: You are not an initial user.
+
+Solution: Ensure that the user rights are correctly inherited when the object is defined.
+
+GAUSS-01764: "must have CREATEROLE privilege"
+
+SQLSTATE: 42501
+
+Description: Obtain the permission to create objects.
+
+Solution: Check the rights of the user that owns the object data and ensure that the object is valid.
+
+GAUSS-01765: "unrecognized object type: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01766: "cache lookup failed for cache %d oid %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01767: "unrecognized class id: %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01768: "temporary tables cannot specify a schema name"
+
+SQLSTATE: 42P16
+
+Description: The current temporary table is not in the original temporary tablespace.
+
+Solution: Ensure that the temporary tablespace is correctly created and that the tablespace OID is correct.
+
+<br/>
+
+## GAUSS-01771 - GAUSS-01780
+
+<br/>
+
+GAUSS-01771: "cannot create relations in temporary schemas of other sessions"
+
+SQLSTATE: 42P16
+
+Description: Creating tables in the temporary tablespace of other sessions is not allowed.
+
+Solution: Do not create tables in the temporary tablespace of other sessions.
+
+GAUSS-01772: "cannot create temporary relation in non-temporary schema"
+
+SQLSTATE: 42P16
+
+Description: Temporary tables cannot be created in non-temporary tablespace.
+
+Solution: Check the tablespace name before creating a table.
+
+GAUSS-01773: "only temporary relations may be created in temporary schemas"
+
+SQLSTATE: 42P16
+
+Description: Only temporary tables can be created in temporary schemas (tablespace).
+
+Solution: Check the tablespace name before creating an object. Create an object based on the characteristics of the tablespace.
+
+GAUSS-01774: "text search parser '%s' does not exist"
+
+SQLSTATE: 42704
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01775: "text search dictionary '%s' does not exist"
+
+SQLSTATE: 42704
+
+Description: The TS file directory cannot be found or does not exist.
+
+Solution: Ensure that the file directory created in the database is correct.
+
+GAUSS-01776: "text search template '%s' does not exist"
+
+SQLSTATE: 42704
+
+Description: The template database cannot be found. The file directory is invalid.
+
+Solution: Ensure that the template database is correctly created at the initial stage of database creation and that the template database file directory is correct.
+
+GAUSS-01777: "%s is already in schema '%s'"
+
+SQLSTATE: 42P07
+
+Description: The object already exists in the current tablespace.
+
+Solution: Query the system catalog to check whether the object already exists in the schema.
+
+GAUSS-01778: "cannot move objects into or out of temporary schemas"
+
+SQLSTATE: 0A000
+
+Description: Moving an object into or out of a temporary tablespace is not allowed.
+
+Solution: Do not move the object into or out of a temporary tablespace.
+
+GAUSS-01780: "cannot move objects into CSTORE schema"
+
+SQLSTATE: 0A000
+
+Description: Objects of other tablespaces cannot be moved into a column-store tablespace.
+
+Solution: Ensure that the current tablespace is not a column-store one.
+
+<br/>
+
+## GAUSS-01781 - GAUSS-01790
+
+<br/>
+
+GAUSS-01781: "cannot move objects into system schema"
+
+SQLSTATE: 0A000
+
+Description: Objects cannot be moved to the system tablespace.
+
+Solution: Do not move objects to the system tablespace.
+
+GAUSS-01782: "improper relation name (too many dotted names): %s"
+
+SQLSTATE: 42601
+
+Description: The name of an imported table is invalid.
+
+Solution: The most complex table name supported in the database is **catalogname.schemaname.relname**.
+
+GAUSS-01783: "unexpected node type in name list: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01784: "bogus PopOverrideSearchPath call"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01785: "collation '%s' for encoding '%s' does not exist"
+
+SQLSTATE: 42704
+
+Description: The encoding method obtained by executing **GetDatabaseEncodingName()** cannot be used with **NameListToString(name)**.
+
+Solution: For information about character sets and corresponding encoding methods supported by the system, see the *Administrator Guide*.
+
+GAUSS-01786: "conversion '%s' does not exist"
+
+SQLSTATE: 42704
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01787: "invalid list syntax"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01788: "permission denied to create temporary tables in database '%s'"
+
+SQLSTATE: 42501
+
+Description: You do not have permission to create temporary tables in the current database.
+
+Solution: Ensure that you have that permission.
+
+GAUSS-01789: "cannot create temporary tables during recovery"
+
+SQLSTATE: 25006
+
+Description: Temporary tables cannot be created because the database is under recovery.
+
+Solution: Correct the status of the database first if creating a temporary table fails.
+
+GAUSS-01790: "current user does not have privilege to role %s"
+
+SQLSTATE: 42501
+
+Description: You do not have permission to manage roles.
+
+Solution: Manage roles as a system administrator.
+
+<br/>
+
+## GAUSS-01791 - GAUSS-01800
+
+<br/>
+
+GAUSS-01791: "collation '%s' for encoding '%s' already exists"
+
+SQLSTATE: 42710
+
+Description: The character set corresponding to **pg_encoding_to_char(collencoding)** already exists.
+
+Solution: Ensure that the character set space corresponding to the current encoding method is sufficient.
+
+GAUSS-01792: "collation '%s' already exists"
+
+SQLSTATE: 42710
+
+Description: The character set already exists.
+
+Solution: Ensure that the character set to be created is unique.
+
+GAUSS-01793: "could not find tuple for collation %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01794: "multiple pg_shdepend entries for object %u/%u/%d deptype %c"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01795: "cannot drop %s because it is required by the database system"
+
+SQLSTATE: 2BP01
+
+Description: The current object cannot be dropped because other objects are dependent upon it.
+
+Solution: Check the dependency relationship between the current object and other tables. Select **cascade** if you want to delete the object.
+
+GAUSS-01797: "tablespace %u was concurrently dropped"
+
+SQLSTATE: 42704
+
+Description: The object needs to be locked before the system records dependency relationships of tablespaces. However, the tablespace cannot be found after the lock is obtained.
+
+Solution: Query logs to check when the tablespace was dropped and ensure that the operation is logical.
+
+GAUSS-01800: "unrecognized dependency type: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/19-GAUSS-01801-GAUSS-01900.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/19-GAUSS-01801-GAUSS-01900.md
new file mode 100644
index 0000000000000000000000000000000000000000..451fcd08242662bdc59325313177cba02f93cecb
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/19-GAUSS-01801-GAUSS-01900.md
@@ -0,0 +1,740 @@
+---
+title: GAUSS-01801 - GAUSS-01900
+summary: GAUSS-01801 - GAUSS-01900
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-01801 - GAUSS-01900
+
+<br/>
+
+## GAUSS-01801 - GAUSS-01810
+
+<br/>
+
+GAUSS-01801: "cannot drop objects owned by %s because they are required by the database system"
+
+SQLSTATE: 2BP01
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01802: "unexpected dependency type"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01803: "cannot reassign ownership of objects owned by %s because they are required by the database system"
+
+SQLSTATE: 2BP01
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01804: "unexpected shared pin"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01805: "unexpected classid %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01806: "smgr_redo: unknown op code %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-01811 - GAUSS-01820
+
+<br/>
+
+GAUSS-01811: "could not access file '%s': %m"
+
+SQLSTATE: XX000
+
+Description: The dynamic library file must be copied to another physical node but fails to be found.
+
+Solution: Check whether the dynamic library file exists and whether its address and link are correct.
+
+GAUSS-01815: "The name of dynamic library is too long"
+
+SQLSTATE: 42622
+
+Description: The dynamic library name is too long.
+
+Solution: Ensure that the name length does not exceed 1000 characters.
+
+GAUSS-01816: "allParameterTypes is not a 1-D Oid array"
+
+SQLSTATE: XX000
+
+Description: Invalid input parameter. An exception occurs when the procedure is created.
+
+Solution: Ensure that the input parameter **allParameterTypes** is valid.
+
+GAUSS-01817: "parameterModes is not a 1-D char array"
+
+SQLSTATE: XX000
+
+Description: Invalid input parameter. An exception occurs when the procedure is created.
+
+Solution: Ensure that the input parameter **parameterModes** is valid.
+
+GAUSS-01818: "cannot determine result data type"
+
+SQLSTATE: 42P13
+
+Description: The result data type cannot be determined because no parameter input exists.
+
+Solution: Check and correct the parameter input type.
+
+GAUSS-01819: "unsafe use of pseudo-type 'internal'"
+
+SQLSTATE: 42P13
+
+Description: The **internal** return type may be unavailable because no **internal** parameter exists.
+
+Solution: Ensure that the **internal** parameter exists.
+
+GAUSS-01820: "'%s' is already an attribute of type %s"
+
+SQLSTATE: 42701
+
+Description: The composite type name and the attribute type are the same during function creation.
+
+Solution: Ensure that any name used during function creation is different from existing attribute names.
+
+<br/>
+
+## GAUSS-01821 - GAUSS-01830
+
+<br/>
+
+GAUSS-01821: "variadic parameter must be last"
+
+SQLSTATE: XX000
+
+Description: When a procedure is created, the variadic parameter is abnormal.
+
+Solution: Ensure that only the last parameter is a variadic parameter.
+
+GAUSS-01822: "variadic parameter is not an array"
+
+SQLSTATE: XX000
+
+Description: When a procedure is created, the variadic parameter is not an array.
+
+Solution: Ensure that the variadic parameter is normal.
+
+GAUSS-01823: "invalid parameter mode '%c'"
+
+SQLSTATE: XX000
+
+Description: When a procedure is created, the proargmode parameter is invalid.
+
+Solution: Ensure that the proargmode parameter is normal.
+
+GAUSS-01824: "more than one function '%s' already exist, please drop function first"
+
+SQLSTATE: 42723
+
+Description: A duplicate function name already exists.
+
+Solution: Ensure that a new function is given a different name from that of any other function in the schema.
+
+GAUSS-01825: "function '%s' already exists with same argument types"
+
+SQLSTATE: 42723
+
+Description: A duplicate function name already exists, and parameters of the function being created are the same as those of the original function.
+
+Solution: Ensure that the function is new.
+
+GAUSS-01826: "cannot change return type of existing function"
+
+SQLSTATE: 42P13
+
+Description: The return type of an existing function cannot be changed.
+
+Solution: Change the return type of a new function or drop the existing function.
+
+GAUSS-01827: "cannot change name of input parameter '%s'"
+
+SQLSTATE: 42P13
+
+Description: The type of input parameter cannot be changed during function creation.
+
+Solution: Check whether the function parameter is changed and drop the existing function.
+
+GAUSS-01828: "function '%s' is an aggregate function"
+
+SQLSTATE: 42809
+
+Description: Internal error. The function being created is an aggregate function whose status cannot be changed.
+
+Solution:Contact technical support.
+
+GAUSS-01829: "function '%s' is not an aggregate function"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01830: "function '%s' is a window function"
+
+SQLSTATE: 42809
+
+Description: The function being created is a window function whose status cannot be changed.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-01831 - GAUSS-01840
+
+<br/>
+
+GAUSS-01831: "function '%s' is not a window function"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01832: "null prosrc"
+
+SQLSTATE: XX005
+
+Description: Failed to obtain a customized function.
+
+Solution: Ensure that the function name is correct.
+
+GAUSS-01833: "there is no built-in function named '%s'"
+
+SQLSTATE: 42883
+
+Description: No built-in function is found based on the function name provided.
+
+Solution: Check whether the **pg_proc** table contains the corresponding function name.
+
+GAUSS-01834: "null prosrc for C function %u"
+
+SQLSTATE: XX005
+
+Description: Failed to obtain a customized C function.
+
+Solution: Ensure that the function name is correct.
+
+GAUSS-01835: "null probin for C function %u"
+
+SQLSTATE: XX005
+
+Description: Failed to obtain a built-in C function.
+
+Solution: Ensure that the function name is correct.
+
+GAUSS-01836: "SQL functions cannot return type %s"
+
+SQLSTATE: 42P13
+
+Description: SQL functions cannot return **format_type_be(proc->prorettype)** data.
+
+Solution: Check the SQL statement.
+
+GAUSS-01837: "SQL functions cannot have arguments of type %s"
+
+SQLSTATE: 42P13
+
+Description: The types of parameters cannot be **format_type_be(proc->proargtypes.values[i])**.
+
+Solution: Check the types of parameters in SQL functions.
+
+GAUSS-01838: "In XC, SQL functions cannot contain utility statements"
+
+SQLSTATE: 42601
+
+Description: SQL functions cannot contain utility statements.
+
+Solution: Check the content in SQL functions.
+
+GAUSS-01840: "no conversion name supplied"
+
+SQLSTATE: XX000
+
+Description: While a conversion is created, the conversion name is not provided.
+
+Solution: Ensure that the conversion name is not empty.
+
+<br/>
+
+## GAUSS-01841 - GAUSS-01850
+
+<br/>
+
+GAUSS-01841: "conversion '%s' already exists"
+
+SQLSTATE: 42710
+
+Description: A conversion named **conname** already exists.
+
+Solution: Ensure that the conversion name is unique.
+
+GAUSS-01842: "default conversion for %s to %s already exists"
+
+SQLSTATE: 42710
+
+Description: A conversion from **conforencoding** to **contoencoding** already exists.
+
+Solution: Do not create a conversion with the same function.
+
+GAUSS-01843: "could not find tuple for conversion %u"
+
+SQLSTATE: XX000
+
+Description: Failed to find the tuple to be deleted from **pg_conversion**.
+
+Solution: Ensure that the tuple OID is correct.
+
+GAUSS-01844: "pgxc class relid invalid."
+
+SQLSTATE: XX000
+
+Description:**relid** is invalid while **pgxc_class** is created.
+
+Solution: Ensure that **relid** is valid.
+
+GAUSS-01845: "pgxc_group should have at least one default node group"
+
+SQLSTATE: XX000
+
+Description:**pgxc_group** is null.
+
+Solution: Ensure that the **pgxc_group** status is normal while **pgxc_class** is created.
+
+GAUSS-01847: "could not obtain lock on partition '%s'"
+
+SQLSTATE: 55P03
+
+Description: Locks cannot be obtained for the current partition.
+
+Solution: Check whether the resource utilization and the current partition status are normal.
+
+GAUSS-01848: "partition '%s' does not exist"
+
+SQLSTATE: 42P01
+
+Description: A partition named **partitionName** does not exist.
+
+Solution: Ensure that the partition name corresponding to the table is correct.
+
+GAUSS-01849: "the object with oid %u is not a partitioned object"
+
+SQLSTATE: 42P17
+
+Description: The current object is not a partitioned object.
+
+Solution: Check the object attribute or check whether it needs to be partitioned as required.
+
+GAUSS-01850: "object with oid %u is not a partition object"
+
+SQLSTATE: 42704
+
+Description: The current object is not a partitioned object.
+
+Solution: Check the object attribute or check whether it needs to be partitioned as required.
+
+<br/>
+
+## GAUSS-01851 - GAUSS-01860
+
+<br/>
+
+GAUSS-01851: "invalid input parameters when searching for local index under some index"
+
+SQLSTATE: 42704
+
+Description: Input parameters are invalid when index OIDs are checked.
+
+Solution: Ensure that input parameters are valid.
+
+GAUSS-01852: "%u is not a partitioned index"
+
+SQLSTATE: 42704
+
+Description: The object corresponding to the parameter OID is not a partitioned index.
+
+Solution: Search the system catalog to check whether the attribute of the parameter introduced during execution process is correct.
+
+GAUSS-01853: "%u not found in pg_class"
+
+SQLSTATE: 42704
+
+Description: The object corresponding to the parameter OID cannot be found in the **pg_class** system catalog.
+
+Solution: Ensure that the object OID to be found is correct and that the object is analyzed and imported to the system catalog.
+
+GAUSS-01854: "not found local index %u in pg_partition"
+
+SQLSTATE: 42704
+
+Description: The corresponding local index cannot be found in the **pg_partition** system catalog.
+
+Solution: Ensure that the local index is valid and that the attribute of the parameter upon creation is correct.
+
+GAUSS-01855: "none is the son local index of index %u"
+
+SQLSTATE: 42704
+
+Description: No local index is found in the indexes of **partitionedIndexid**.
+
+Solution: Ensure that the local index to be searched for is correct.
+
+GAUSS-01859: "cache lookup failed for index partition %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01860: "more than one item satisfied parttype is %c, parentOid is %u"
+
+SQLSTATE: 0A000
+
+Description: Two partitions in one table are of the same type.
+
+Solution: Ensure that all partitions are of different types.
+
+<br/>
+
+## GAUSS-01861 - GAUSS-01870
+
+<br/>
+
+GAUSS-01861: "'%s' does not require a toast table"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01862: "shared tables cannot be toasted after gs_initdb"
+
+SQLSTATE: 55000
+
+Description: After database initialization is complete, shared tables do not support TOAST.
+
+Solution: Do not implement TOAST on shared tables if the initialization is complete.
+
+GAUSS-01863: "cache lookup failed for relation or partition %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01864: "grant options can only be granted to roles"
+
+SQLSTATE: 0LP01
+
+Description: Only private users can be granted permissions.
+
+Solution: Check whether the user has permission. If the user does not have permission, contact the administrator.
+
+GAUSS-01865: "unrecognized object kind: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01866: "unrecognized GrantStmt.targtype: %d"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01867: "unrecognized GrantStmt.objtype: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01868: "column privileges are only valid for relations"
+
+SQLSTATE: 0LP01
+
+Description: Only table objects have the column storage feature.
+
+Solution: Check whether the object feature is correct, or whether the table object is granted the column storage feature.
+
+GAUSS-01869: "AccessPriv node must specify privilege or columns"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01870: "default privileges cannot be set for columns"
+
+SQLSTATE: 0LP01
+
+Description: Default access rights cannot be set for attribute columns.
+
+Solution: Check whether the object is an attribute column.
+
+<br/>
+
+## GAUSS-01871 - GAUSS-01880
+
+<br/>
+
+GAUSS-01871: "AccessPriv node must specify privilege"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01872: "could not find tuple for default ACL %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01873: "unexpected default ACL type: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01875: "column number out of range"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01876: "'%s' is an index"
+
+SQLSTATE: 42809
+
+Description: Permissions cannot be granted to an index.
+
+Solution: Ensure that all listed objects to be granted with permissions are tables.
+
+GAUSS-01877: "invalid privilege type USAGE for table"
+
+SQLSTATE: 0LP01
+
+Description: The USAGE permission is valid only for sequences.
+
+Solution: Check the table type.
+
+GAUSS-01878: "invalid privilege type %s for column"
+
+SQLSTATE: 0LP01
+
+Description: The permission type is invalid for columns.
+
+Solution: Check the permission description and object type in the context.
+
+GAUSS-01879: "language '%s' is not trusted"
+
+SQLSTATE: 42809
+
+Description: The interface programming language is not trusted by the system.
+
+Solution: Set the interface programming language to one trusted by the system.
+
+<br/>
+
+## GAUSS-01881 - GAUSS-01890
+
+<br/>
+
+GAUSS-01881: "cache lookup failed for tablespace %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01882: "cannot set privileges of array types"
+
+SQLSTATE: 0LP01
+
+Description: Permissions cannot be granted to objects whose types are array.
+
+Solution: Ensure that the object type is correct before you grant permissions.
+
+GAUSS-01883: "unrecognized privilege type '%s'"
+
+SQLSTATE: 42601
+
+Description: The permission type is unrecognized.
+
+Solution: Check the context to determine whether the type definition is correct or has been modified.
+
+GAUSS-01886: "permission denied for column '%s' of relation '%s'"
+
+SQLSTATE: 42501
+
+Description: Permission operations are denied for attribute columns in a table.
+
+Solution: Check whether the permission operation definition is correct.
+
+GAUSS-01887: "role with OID %u does not exist"
+
+SQLSTATE: 42704
+
+Description: The user does not exist.
+
+Solution: Search the user list to check whether the user exists.
+
+GAUSS-01888: "unrecognized objkind: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01889: "attribute %d of relation with OID %u does not exist"
+
+SQLSTATE: 42703
+
+Description: The table does not contain an attribute access right list.
+
+Solution: Check whether the access right list exists when the table is defined.
+
+GAUSS-01890: "relation with OID %u does not exist"
+
+SQLSTATE: 42P01
+
+Description: The result of checking user access rights in the user exit program indicates that the corresponding table does not exist.
+
+Solution: Search the **pg_class** system catalog to check whether the table with corresponding OID exists.
+
+<br/>
+
+## GAUSS-01891 - GAUSS-01900
+
+<br/>
+
+GAUSS-01891: "database with OID %u does not exist"
+
+SQLSTATE: 3D000
+
+Description: The result of checking user access rights indicates that the corresponding database does not exist.
+
+Solution: Check whether the database status in the **pg_database** system catalog is normal.
+
+GAUSS-01892: "function with OID %u does not exist"
+
+SQLSTATE: 42883
+
+Description: The result of checking user access rights in the user exit program indicates that the corresponding function does not exist.
+
+Solution: Check whether the function is defined in the **pg_proc** system catalog.
+
+GAUSS-01893: "language with OID %u does not exist"
+
+SQLSTATE: 42704
+
+Description: The result of checking user access rights in the user exit program indicates that the corresponding language format does not exist.
+
+Solution: Check whether the language is defined in the **pg_language** system catalog.
+
+GAUSS-01894: "schema with OID %u does not exist"
+
+SQLSTATE: 3F000
+
+Description: The result of checking user access rights in the user exit program indicates that the corresponding schema space does not exist.
+
+Solution: Check whether the corresponding space is defined in the **pg_namespace** system catalog.
+
+GAUSS-01895: "tablespace with OID %u does not exist"
+
+SQLSTATE: 42704
+
+Description: The result of checking user access rights in the user exit program indicates that the corresponding tablespace does not exist.
+
+Solution: Check whether the tablespace is defined in the **pg_tablespace** system catalog.
+
+GAUSS-01896: "foreign-data wrapper with OID %u does not exist"
+
+SQLSTATE: XX000
+
+Description: The foreign-data wrapper does not exist.
+
+Solution: Ensure that the foreign-data wrapper has been created.
+
+GAUSS-01897: "foreign server with OID %u does not exist"
+
+SQLSTATE: XX000
+
+Description: The foreign server does not exist.
+
+Solution: Ensure that the foreign server has been created.
+
+GAUSS-01898: "type with OID %u does not exist"
+
+SQLSTATE: XX000
+
+Description: The result of checking user access rights in the user exit program indicates that the corresponding data type does not exist.
+
+Solution: Check whether all types are defined in the **pg_type** system catalog.
+
+GAUSS-01899: "type with OID %u does not exist"
+
+SQLSTATE: 42704
+
+Description: The result of checking user access rights in the user exit program indicates that the corresponding data type does not exist.
+
+Solution: Check whether all types are defined in the **pg_type** system catalog.
+
+GAUSS-01900: "operator with OID %u does not exist"
+
+SQLSTATE: 42883
+
+Description: The result of checking user rights indicates that the corresponding operator type does not exist.
+
+Solution: Check whether the operator is defined in the **pg_operator** system catalog.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/2-GAUSS-00101-GAUSS-00200.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/2-GAUSS-00101-GAUSS-00200.md
new file mode 100644
index 0000000000000000000000000000000000000000..f8dca69911488fad8cbe977fb3f6ecbdd4f1440b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/2-GAUSS-00101-GAUSS-00200.md
@@ -0,0 +1,836 @@
+---
+title: GAUSS-00101 - GAUSS-00200
+summary: GAUSS-00101 - GAUSS-00200
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-00101 - GAUSS-00200
+
+<br/>
+
+## GAUSS-00101 - GAUSS-00110
+
+<br/>
+
+GAUSS-00101: "table '%s' has %d columns available but %d columns specified"
+
+SQLSTATE: 42P10
+
+Description: The number of table columns to be queried is greater than the total number of table columns.
+
+Solution: Ensure that the number of table columns to be queried is less than or equal to the total number of table columns.
+
+GAUSS-00102: "too many column aliases specified for function %s"
+
+SQLSTATE: 42P10
+
+Description: A function alias contains more than one column.
+
+Solution: Ensure that a function alias contains only one column.
+
+GAUSS-00103: "relation '%s' is not partitioned table"
+
+SQLSTATE: 42P01
+
+Description: The table is not a partitioned table.
+
+Solution: Before performing an operation on the table, use the system catalog to ensure that the table is a partitioned table.
+
+GAUSS-00104: "partition '%s' of relation '%s' does not exist"
+
+SQLSTATE: 42P01
+
+Description: The partitioned table does not exist.
+
+Solution: When using a partitioned table, query the **pg_partition** table to check whether the partitioned table exists.
+
+GAUSS-00105: "The partition number is invalid or out-of-range"
+
+SQLSTATE: XX000
+
+Description: The value inserted to the partition is out of the partition range.
+
+Solution: Ensure that the value to be inserted to a partition is within the range of the partition.
+
+GAUSS-00106: "unsupported partition type"
+
+SQLSTATE: XX000
+
+Description: The partition type is not supported.
+
+Solution: Change the partition type. Currently, row-store and column-store tables support only range partitioning.
+
+GAUSS-00107: "relation '%s.%s' does not exist"
+
+SQLSTATE: 42P01
+
+Description: The table object in the specified schema does not exist.
+
+Solution: Use an object that exists.
+
+GAUSS-00108: "relation '%s' does not exist"
+
+SQLSTATE: 42P01
+
+Description: The object does not exist.
+
+Solution: Use an object that exists.
+
+GAUSS-00109: "a column definition list is only allowed for functions returning 'record'"
+
+SQLSTATE: 42601
+
+Description: The column definition list (or table definition) is not allowed for functions that return values of a type other than record.
+
+Solution: Do not use table definitions to specify return values for functions that do not return values of the record type.
+
+GAUSS-00110: "a column definition list is required for functions returning 'record'"
+
+SQLSTATE: 42601
+
+Description: The column definition list (or table definition) is required for functions that return values of the record type.
+
+Solution: Use table definitions to specify return values for functions that return values of the record type.
+
+<br/>
+
+## GAUSS-00111 - GAUSS-00120
+
+<br/>
+
+GAUSS-00111: "column '%s' cannot be declared SETOF"
+
+SQLSTATE: 42P16
+
+Description: In the value returned for the function, a column is specified to SETOF.
+
+Solution: Ensure that no column is specified to SETOF.
+
+GAUSS-00112: "function '%s' in FROM has unsupported return type %s"
+
+SQLSTATE: 42804
+
+Description: The value returned for the function is of an unsupported type.
+
+Solution: Switch the type to another common type and try again. Check whether this problem persists. Contact technical support.
+
+GAUSS-00113: "VALUES lists '%s' have %d columns available but %d columns specified"
+
+SQLSTATE: 42P10
+
+Description: The number of parameters in the **VALUES** expression is inconsistent with the number of specified columns.
+
+Solution: Ensure that the number of parameters in the **VALUES** expression is consistent with the number of specified columns.
+
+GAUSS-00114: "joins can have at most %d columns"
+
+SQLSTATE: 54000
+
+Description: The number of columns in a join is greater than the upper limit (32,767).
+
+Solution: Ensure that the number of columns in a join is less than or equal to the upper limit (32767).
+
+GAUSS-00115: "WITH query '%s' does not have a RETURNING clause"
+
+SQLSTATE: 0A000
+
+Description: In the non-SELECT with statement, no **RETURNING** clause is specified.
+
+Solution: Specify a **RETURNING** clause.
+
+GAUSS-00116: "function in FROM has unsupported return type"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00117: "unrecognized RTE kind: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00118: "invalid attnum %d for rangetable entry %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00119: "cache lookup failed for attribute %d of relation %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00120: "subquery %s does not have attribute %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-00121 - GAUSS-00130
+
+<br/>
+
+GAUSS-00121: "column %d of relation '%s' does not exist"
+
+SQLSTATE: 42703
+
+Description: The column does not exist.
+
+Solution: Ensure that the specified column exists in the table.
+
+GAUSS-00122: "values list %s does not have attribute %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00123: "invalid varattno %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00124: "invalid attribute number %d"
+
+SQLSTATE: 42704
+
+Description: The table attribute ID is invalid.
+
+Solution:Contact technical support.
+
+GAUSS-00125: "invalid reference to FROM-clause entry for table '%s'"
+
+SQLSTATE: 42P01
+
+Description: In a **FROM** clause, the reference to the table is invalid.
+
+Solution: Use correct syntax when referencing the table in a **FROM** clause.
+
+GAUSS-00126: "missing FROM-clause entry for table '%s'"
+
+SQLSTATE: 42P01
+
+Description: The **WITH** statement lacks a **FROM** clause.
+
+Solution: Ensure that the **WITH** statement contains a **FROM** clause.
+
+GAUSS-00127: "Password must be quoted"
+
+SQLSTATE: 42601
+
+Description: The password does not use quotation marks ("").
+
+Solution: Use quotation marks when specifying a password.
+
+GAUSS-00128: "unrecognized role option '%s'"
+
+SQLSTATE: 42601
+
+Description: An unidentified user option is used.
+
+Solution: Use the user option provided in the R&D support document.
+
+GAUSS-00129: "'SET %s TO rolename' not yet supported"
+
+SQLSTATE: 42601
+
+Description:**set name to rolename** is not supported.
+
+Solution: Use **set name rolename**.
+
+GAUSS-00130: "'SET %s = rolename' not yet supported"
+
+SQLSTATE: 42601
+
+Description:**set name = rolename** is not supported.
+
+Solution: Use **set name rolename**.
+
+<br/>
+
+## GAUSS-00131 - GAUSS-00140
+
+<br/>
+
+GAUSS-00131: "current database cannot be changed"
+
+SQLSTATE: 0A000
+
+Description: A system catalog is set in the current database, which is not allowed.
+
+Solution: Do not set a system catalog.
+
+GAUSS-00132: "time zone interval must be HOUR or HOUR TO MINUTE"
+
+SQLSTATE: 42601
+
+Description: The time interval format is incorrect.
+
+Solution: The format must be **HOUR** or **HOUR TO MINUTE**.
+
+GAUSS-00133: "interval precision specified twice"
+
+SQLSTATE: 42601
+
+Description: The interval precision is specified more than once.
+
+Solution: Specify the interval precision only once.
+
+GAUSS-00134: "MATCH PARTIAL not yet implemented"
+
+SQLSTATE: 0A000
+
+Description: Partial matching is used for reference.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-00135: "unrecognized distribution option '%s'"
+
+SQLSTATE: 42601
+
+Description: The distribution column option is unidentified.
+
+Solution: Use a supported distribution column option. For details, see en-us_topic_0237122117.html.
+
+GAUSS-00136: "Invalid option %s"
+
+SQLSTATE: 42601
+
+Description: The option is invalid.
+
+Solution: Use a valid option.
+
+GAUSS-00137: "constraint declared INITIALLY DEFERRED must be DEFERRABLE"
+
+SQLSTATE: 42601
+
+Description: The constraint set to **INITIALLY DEFERRED** is not **DEFERRABLE**.
+
+Solution: Ensure that the constraint set to **INITIALLY DEFERRED** is **DEFERRABLE**.
+
+GAUSS-00138: "conflicting constraint properties"
+
+SQLSTATE: 42601
+
+Description: The constraints conflict with each other.
+
+Solution: Do not use constraints that conflict with each other simultaneously.
+
+GAUSS-00139: "CREATE ASSERTION is not yet implemented"
+
+SQLSTATE: 0A000
+
+Description: The **CREATE ASSERTION** statement is not supported.
+
+Solution: Do not use an unsupported statement.
+
+GAUSS-00140: "DROP ASSERTION is not yet implemented"
+
+SQLSTATE: 0A000
+
+Description: The **DROP ASSERTION** statement is not supported.
+
+Solution: Do not use an unsupported statement.
+
+<br/>
+
+## GAUSS-00141 - GAUSS-00150
+
+<br/>
+
+GAUSS-00141: "missing argument"
+
+SQLSTATE: 42601
+
+Description: The parameter is missing when an operator is deleted.
+
+Solution: Use the parameter defined for an operator when deleting the operator.
+
+GAUSS-00142: "WITH CHECK OPTION is not implemented"
+
+SQLSTATE: 0A000
+
+Description: This option is not supported.
+
+Solution: Use a supported option.
+
+GAUSS-00144: "CREATE TABLE AS EXECUTE not yet supported"
+
+SQLSTATE: 0A000
+
+Description: Syntax not supported.
+
+Solution: Use a supported syntax. For details, see en-us_topic_0237121923.html.
+
+GAUSS-00145: "number of columns does not match number of values"
+
+SQLSTATE: 42601
+
+Description: The number of columns to be modified is inconsistent with the number of provided values.
+
+Solution: Ensure that the number of columns to be modified is consistent with the number of provided values.
+
+GAUSS-00146: "Sort method %s is not supported!"
+
+SQLSTATE: XX000
+
+Description: The sorting method is not supported.
+
+Solution: Use a supported option. For details, see en-us_topic_0237121923.html.
+
+GAUSS-00148: "VALUES in FROM must have an alias"
+
+SQLSTATE: 42601
+
+Description: The **VALUES** statement does not use an alias in the **FROM** clause.
+
+Solution: Use an alias of the **VALUES** statement in the **FROM** clause.
+
+GAUSS-00149: "precision for type float must be at least 1 bit"
+
+SQLSTATE: 22023
+
+Description: The float precision is set to a value less than 1.
+
+Solution: Set the float precision to a value greater than or equal to 1.
+
+GAUSS-00150: "precision for type float must be less than 54 bits"
+
+SQLSTATE: 22023
+
+Description: The float precision is set to a value greater than 54.
+
+Solution: Set the float precision to a value less than or equal to 54.
+
+<br/>
+
+## GAUSS-00151 - GAUSS-00160
+
+<br/>
+
+GAUSS-00151: "UNIQUE predicate is not yet implemented"
+
+SQLSTATE: 0A000
+
+Description: The **UNIQUE** clause is not implemented.
+
+Solution: Use a clause that has been implemented.
+
+GAUSS-00152: "RANGE PRECEDING is only supported with UNBOUNDED"
+
+SQLSTATE: 0A000
+
+Description:**UNBOUNDED** is not specified when **RANGE PRECEDING** is used.
+
+Solution: Specify **UNBOUNDED** when using **RANGE PRECEDING**.
+
+GAUSS-00153: "RANGE FOLLOWING is only supported with UNBOUNDED"
+
+SQLSTATE: 0A000
+
+Description:**UNBOUNDED** is not specified when **RANGE FOLLOWING** is used.
+
+Solution: Specify **UNBOUNDED** when using **RANGE FOLLOWING**.
+
+GAUSS-00154: "frame start cannot be UNBOUNDED FOLLOWING"
+
+SQLSTATE: 42P20
+
+Description:**UNBOUNDED FOLLOWING** is specified for the frame start.
+
+Solution: Do not set the frame start to **UNBOUNDED FOLLOWING**.
+
+GAUSS-00155: "frame starting from following row cannot end with current row"
+
+SQLSTATE: 42P20
+
+Description: The frame starts from the next row and ends in the current row.
+
+Solution: Ensure that the frame does not end in the current row if it starts from the next row.
+
+GAUSS-00156: "frame end cannot be UNBOUNDED PRECEDING"
+
+SQLSTATE: 42P20
+
+Description:**UNBOUNDED PRECEDING** is specified for the frame end.
+
+Solution: Do not set the frame end to **UNBOUNDED PRECEDING**.
+
+GAUSS-00157: "frame starting from current row cannot have preceding rows"
+
+SQLSTATE: 42P20
+
+Description: The frame starts from the current row and ends in the previous row.
+
+Solution: Ensure that the frame does not end in the previous row if it starts from the current row.
+
+GAUSS-00158: "frame starting from following row cannot have preceding rows"
+
+SQLSTATE: 42P20
+
+Description: The frame starts from the next row and ends in the previous row.
+
+Solution: Ensure that the frame does not end in the previous row if it starts from the next row.
+
+GAUSS-00159: "type modifier cannot have parameter name"
+
+SQLSTATE: 42601
+
+Description: The parameter schema for the number of rows contains a parameter.
+
+Solution: Ensure that the parameter schema for the number of rows does not contain a parameter.
+
+GAUSS-00160: "wrong number of parameters on left side of OVERLAPS expression"
+
+SQLSTATE: 42601
+
+Description: The number of left parameters in an overlaps function is greater than 2.
+
+Solution: Use no more than two left parameters in an overlaps function.
+
+<br/>
+
+## GAUSS-00161 - GAUSS-00170
+
+<br/>
+
+GAUSS-00161: "wrong number of parameters on right side of OVERLAPS expression"
+
+SQLSTATE: 42601
+
+Description: The number of right parameters in an overlaps function is greater than 2.
+
+Solution: Use no more than two left parameters in an overlaps function.
+
+GAUSS-00162: "multiple ORDER BY clauses not allowed"
+
+SQLSTATE: 42601
+
+Description: Multiple **ORDER BY** clauses are used in the **INSERT INTO SELECT** statement.
+
+Solution: Use one **ORDER BY** clause in the **INSERT INTO SELECT** statement.
+
+GAUSS-00163: "multiple OFFSET clauses not allowed"
+
+SQLSTATE: 42601
+
+Description: Multiple **OFFSET** clauses are used in the **INSERT INTO SELECT** statement.
+
+Solution: Use one **OFFSET** clause in the **INSERT INTO SELECT** statement.
+
+GAUSS-00164: "multiple LIMIT clauses not allowed"
+
+SQLSTATE: 42601
+
+Description: Multiple **LIMIT** clauses are used in the **INSERT INTO SELECT** statement.
+
+Solution: Use one **LIMIT** clause in the **INSERT INTO SELECT** statement.
+
+GAUSS-00165: "multiple WITH clauses not allowed"
+
+SQLSTATE: 42601
+
+Description: Multiple **WITH** clauses are used in the **INSERT INTO SELECT** statement.
+
+Solution: Use one **WITH** clause in the **INSERT INTO SELECT** statement.
+
+GAUSS-00166: "OUT and INOUT arguments aren't allowed in TABLE functions"
+
+SQLSTATE: 42601
+
+Description: The **OUT** and **INOUT** parameters are used in table functions.
+
+Solution: Do not use the **OUT** and **INOUT** parameters in table functions.
+
+GAUSS-00167: "multiple COLLATE clauses not allowed"
+
+SQLSTATE: 42601
+
+Description: Multiple **COLLATE** clauses are specified.
+
+Solution: Specify only one **COLLATE** clause.
+
+GAUSS-00168: "unexpected node type %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00169: "%s constraints cannot be marked DEFERRABLE"
+
+SQLSTATE: 0A000
+
+Description: The constraint that cannot be marked with **DEFERRABLE** is used.
+
+Solution: Modify the SQL statement.
+
+GAUSS-00170: "%s constraints cannot be marked NOT VALID"
+
+SQLSTATE: 0A000
+
+Description: The constraint that cannot be marked with **NOT VALID** is used.
+
+Solution: Modify the SQL statement.
+
+<br/>
+
+## GAUSS-00171 - GAUSS-00180
+
+<br/>
+
+GAUSS-00171: "%s constraints cannot be marked NO INHERIT"
+
+SQLSTATE: 0A000
+
+Description: The constraint that cannot be marked with **NO INHERIT** is used.
+
+Solution: Modify the SQL statement.
+
+GAUSS-00172: "undefined or invalid action for statement ' alter system '"
+
+SQLSTATE: 42704
+
+Description: The option length is not 1 in the **ALTER SYSTEM** statement.
+
+Solution: Ensure that the option length is 1.
+
+GAUSS-00173: "unsupported action '%s' for statement ' alter system '"
+
+SQLSTATE: 42704
+
+Description: An unsupported option is used in the **ALTER SYSTEM** statement.
+
+Solution: Use a supported option. For details, see en-us_topic_0237122075.html.
+
+GAUSS-00174: "undefined action '%s' for statement ' alter system '"
+
+SQLSTATE: 42704
+
+Description: An unsupported option is used in the **ALTER SYSTEM** statement.
+
+Solution: Use a supported option. For details, see en-us_topic_0237122075.html.
+
+GAUSS-00175: "missing or invalid session ID"
+
+SQLSTATE: 42704
+
+Description: The **Session ID** value used in the **ALTER SYSTEM** statement is incorrect.
+
+Solution: Use a correct **Session ID** value. For details about **Session ID** values, see the **dv_sessions** view.
+
+GAUSS-00176: "parameter '%s' is assigned more than once"
+
+SQLSTATE: 42710
+
+Description: Duplicate parameter names exist.
+
+Solution: Ensure that the parameter names in a function are different.
+
+GAUSS-00177: "parameter '%s' is undefined"
+
+SQLSTATE: 42P02
+
+Description: Undefined parameter.
+
+Solution: Modify the SQL statement.
+
+GAUSS-00178: "the parameter located '%d' have been assigned"
+
+SQLSTATE: 42710
+
+Description: A value has been assigned to the parameter mode.
+
+Solution: Modify the SQL statement.
+
+GAUSS-00179: "parameter mode %c doesn't exist"
+
+SQLSTATE: XX000
+
+Description: An invalid parameter mode is used.
+
+Solution: Use a valid parameter mode.
+
+GAUSS-00180: "output argument located '%d' doesnot assigned"
+
+SQLSTATE: XX000
+
+Description: The type of an output parameter is not set.
+
+Solution: Set types for all parameters.
+
+<br/>
+
+## GAUSS-00181 - GAUSS-00190
+
+<br/>
+
+GAUSS-00181: "function '%s' doesn't exist "
+
+SQLSTATE: 42883
+
+Description: The function is not defined.
+
+Solution: Modify the SQL statement.
+
+GAUSS-00182: "function '%s' isn't exclusive "
+
+SQLSTATE: 42723
+
+Description: Duplicate function definitions exist.
+
+Solution: Ensure that no duplicate functions exist in the system.
+
+GAUSS-00183: "function '%s' with %d parameters doesn't exist "
+
+SQLSTATE: 42883
+
+Description: The function is not defined.
+
+Solution: Modify the SQL statement.
+
+GAUSS-00184: "invalid name: %s"
+
+SQLSTATE: 42601
+
+Description: The variable name is invalid.
+
+Solution: Name a variable in compliance with naming rules. For details, see en-us_topic_0237120321.html.
+
+GAUSS-00185: "WITH query name '%s' specified more than once"
+
+SQLSTATE: 42712
+
+Description: The name of a **WITH** clause is specified multiple times.
+
+Solution: Specify the name of a **WITH** clause only once.
+
+GAUSS-00187: "unexpected utility statement in WITH"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00188: "WITH clause containing a data-modifying statement must be at the top level"
+
+SQLSTATE: 0A000
+
+Description: The non-SELECT with statement is not placed at the beginning of the whole query.
+
+Solution: Place the non-SELECT with statement at the beginning of the whole query.
+
+GAUSS-00189: "wrong number of output columns in WITH"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00190: "recursive query '%s' column %d has type %s in non-recursive term but type %s overall"
+
+SQLSTATE: 42804
+
+Description: The column type in the non-recursive query is inconsistent with that in the recursive query.
+
+Solution: Convert the output type in the non-recursive query to that in the recursive query.
+
+<br/>
+
+## GAUSS-00191 - GAUSS-00200
+
+<br/>
+
+GAUSS-00191: "recursive query '%s' column %d has collation '%s' in non-recursive term but collation '%s' overall"
+
+SQLSTATE: 42P21
+
+Description: The column character set in the recursive query is inconsistent with that of that in the non-recursive query.
+
+Solution: Convert the output character set of the non-recursive query to that of the recursive query.
+
+GAUSS-00192: "WITH query '%s' has %d columns available but %d columns specified"
+
+SQLSTATE: 42P10
+
+Description: The number of parameters specified in the recursive query is inconsistent with the number of parameters required for the actual query.
+
+Solution: Ensure that the number of parameters specified in the recursive query is consistent with the number of parameters required.
+
+GAUSS-00193: "mutual recursion between WITH items is not implemented"
+
+SQLSTATE: 0A000
+
+Description: Recursion between queries is not implemented.
+
+Solution: Use a supported function.
+
+GAUSS-00194: "recursive query '%s' must not contain data-modifying statements"
+
+SQLSTATE: 42P19
+
+Description: The recursive query contains non-query statements.
+
+Solution: Ensure that the recursive query contains only query statements.
+
+GAUSS-00196: "missing recursive reference"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00197: "ORDER BY in a recursive query is not implemented"
+
+SQLSTATE: 0A000
+
+Description:**ORDER BY** is used in a recursive query.
+
+Solution: Do not use **ORDER BY** in a recursive query.
+
+GAUSS-00198: "OFFSET in a recursive query is not implemented"
+
+SQLSTATE: 0A000
+
+Description: Syntax not supported.
+
+Solution: Modify the SQL statement.
+
+GAUSS-00199: "LIMIT in a recursive query is not implemented"
+
+SQLSTATE: 0A000
+
+Description:**LIMIT** is used in a recursive query.
+
+Solution: Do not use **LIMIT** in a recursive query.
+
+GAUSS-00200: "FOR UPDATE/SHARE in a recursive query is not implemented"
+
+SQLSTATE: 0A000
+
+Description:**FOR UPDATE/SHARE** is used in a recursive query.
+
+Solution: Do not use **FOR UPDATE/SHARE** in a recursive query.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/20-GAUSS-01901-GAUSS-02000.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/20-GAUSS-01901-GAUSS-02000.md
new file mode 100644
index 0000000000000000000000000000000000000000..faa82a904593c730dcdca929f1d3ff4e5eb0b0b0
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/20-GAUSS-01901-GAUSS-02000.md
@@ -0,0 +1,614 @@
+---
+title: GAUSS-01901 - GAUSS-02000
+summary: GAUSS-01901 - GAUSS-02000
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-01901 - GAUSS-02000
+
+<br/>
+
+## GAUSS-01901 - GAUSS-01910
+
+<br/>
+
+GAUSS-01901: "language with OID %u does not exist"
+
+SQLSTATE: 42883
+
+Description: The result of checking user access rights in the user exit program indicates that the corresponding language format does not exist.
+
+Solution: Check whether the language is defined in the **pg_language** system catalog.
+
+GAUSS-01904: "text search dictionary with OID %u does not exist"
+
+SQLSTATE: 42704
+
+Description: The result of checking user rights indicates that the corresponding file search path does not exist.
+
+Solution: Check all file search paths in the **pg_ts_dict** system catalog.
+
+GAUSS-01905: "text search configuration with OID %u does not exist"
+
+SQLSTATE: 42704
+
+Description: The result of checking user rights indicates that the corresponding file search composition does not exist.
+
+Solution: Check all file search compositions in the **pg_ts_config** system catalog.
+
+GAUSS-01906: "collation with OID %u does not exist"
+
+SQLSTATE: 42704
+
+Description: The result of checking user rights indicates that the corresponding character set does not exist.
+
+Solution: Check all character sets in the **pg_collation** system catalog.
+
+GAUSS-01907: "conversion with OID %u does not exist"
+
+SQLSTATE: 42704
+
+Description: The result of checking user rights indicates that the corresponding conversion does not exist.
+
+Solution: Check all conversions in the **pg_collation** system catalog.
+
+GAUSS-01908: "extension with OID %u does not exist"
+
+SQLSTATE: 42704
+
+Description: The result of checking user rights indicates that the corresponding extension does not exist.
+
+Solution: Check all extensions in the **pg_extension** system catalog.
+
+GAUSS-01909: "relation '%s' has relchecks = 0"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-01911 - GAUSS-01920
+
+<br/>
+
+GAUSS-01911: "constraint '%s' for domain %s already exists"
+
+SQLSTATE: 42710
+
+Description: The constraint name already exists in the current table.
+
+Solution: Ensure that the constraint name is unique.
+
+GAUSS-01912: "table '%s' has multiple constraints named '%s'"
+
+SQLSTATE: 42710
+
+Description: The table has at least two duplicate constraints.
+
+Solution: Ensure that each constraint has a unique name within one table.
+
+GAUSS-01913: "constraint '%s' for table '%s' does not exist"
+
+SQLSTATE: 42704
+
+Description: The constraint does not exist in the current table.
+
+Solution: Ensure that the constraint exists in the current table. Alternatively, check all constraints in the table.
+
+GAUSS-01914: "domain '%s' has multiple constraints named '%s'"
+
+SQLSTATE: 42710
+
+Description: The domain has at least two duplicate constraints.
+
+Solution: Ensure that each constraint has a unique name within one domain.
+
+GAUSS-01915: "constraint '%s' for domain '%s' does not exist"
+
+SQLSTATE: 42704
+
+Description: The constraint does not exist in the current domain.
+
+Solution: Check all constraints in the domain.
+
+GAUSS-01916: "null conkey for constraint %u"
+
+SQLSTATE: XX005
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01917: "conkey is not a 1-D smallint array"
+
+SQLSTATE: 42804
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01918: "no aggregate name supplied"
+
+SQLSTATE: XX000
+
+Description: The aggregate name is not provided.
+
+Solution: Provide an aggregate name.
+
+GAUSS-01919: "aggregate must have a transition function"
+
+SQLSTATE: XX000
+
+Description: The aggregate does not have a transition function.
+
+Solution: Provide a transition function.
+
+GAUSS-01920: "cannot determine transition data type"
+
+SQLSTATE: 42P13
+
+Description: The conversion type for the composite type cannot be determined during aggregate function creation.
+
+Solution: Set a conversion type for the composite type.
+
+<br/>
+
+## GAUSS-01921 - GAUSS-01930
+
+<br/>
+
+GAUSS-01921: "return type of transition function %s is not %s"
+
+SQLSTATE: 42804
+
+Description: The return type generated based on **transfn** is inconsistent with that as specified.
+
+Solution: Ensure that the return type for the composite type is consistent with that as specified.
+
+GAUSS-01922: "must not omit initial value when transition function is strict and transition type is not compatible with input type"
+
+SQLSTATE: 42P13
+
+Description: When the conversion function is strict and inconsistent with the input type, pay attention to the type of the initial value.
+
+Solution: Ensure that the type of the initial value is consistent with that of the conversion type. Alternatively, it must be at least compatible with binary data.
+
+GAUSS-01923: "return type of collection function %s is not %s"
+
+SQLSTATE: 42804
+
+Description: The return type of the collection function is different from the expected **aggTreanType**.
+
+Solution: Call the correct collection function.
+
+GAUSS-01924: "cannot determine result data type"
+
+SQLSTATE: 42804
+
+Description: The result data type cannot be determined because no parameter input exists.
+
+Solution: Check and correct the parameter input type.
+
+GAUSS-01925: "sort operator can only be specified for single-argument aggregates"
+
+SQLSTATE: 42P13
+
+Description: Sort operators can only appear in an aggregate function with a single parameter.
+
+Solution: Check the number of parameters and whether to call sort operators.
+
+GAUSS-01926: "function %s returns a set"
+
+SQLSTATE: 42804
+
+Description: The aggregate function can return only single value but cannot return a set.
+
+Solution: Check whether the aggregate function is correct.
+
+GAUSS-01927: "function %s requires run-time type coercion"
+
+SQLSTATE: 42804
+
+Description: The function requires type coercion during execution but the type coercion is not performed in the **nodeAgg.c** file.
+
+Solution: Ensure that type conversion does not occur during execution.
+
+GAUSS-01928: "cannot drop %s because %s requires it"
+
+SQLSTATE: 2BP01
+
+Description: This object cannot be deleted because other objects depend on it.
+
+Solution: Remove the dependency relationship. Alternatively, delete the depending objects.
+
+GAUSS-01929: "incorrect use of PIN dependency with %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01930: "unrecognized dependency type '%c' for %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-01931 - GAUSS-01940
+
+<br/>
+
+GAUSS-01931: "cannot drop %s because other objects depend on it"
+
+SQLSTATE: 2BP01
+
+Description: This object cannot be deleted because other objects depend on it.
+
+Solution: Remove the dependency relationship. Alternatively, delete the depending objects.
+
+GAUSS-01932: "cannot drop desired object(s) because other objects depend on them"
+
+SQLSTATE: 2BP01
+
+Description: These objects cannot be deleted because other objects depend on them.
+
+Solution: Use **drop cascade** to delete the depending objects.
+
+GAUSS-01933: "invalid varlevelsup %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01934: "invalid varno %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01935: "already-planned subqueries not supported"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01936: "invalid resultRelation %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01937: "invalid objectSubId 0 for object class %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01938: "could not find tuple for rule %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01939: "no namespace name supplied"
+
+SQLSTATE: XX000
+
+Description: The namespace name is not provided while it is created.
+
+Solution: Provide a namespace name.
+
+GAUSS-01940: "primary keys cannot be expressions"
+
+SQLSTATE: 0A000
+
+Description: Primary keys cannot be expressions.
+
+Solution: Reselect the primary key.
+
+<br/>
+
+## GAUSS-01941 - GAUSS-01950
+
+<br/>
+
+GAUSS-01942: "too few entries in colnames list"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01943: "must index at least one column"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01944: "user-defined indexes on system catalog tables are not supported"
+
+SQLSTATE: 0A000
+
+Description: User-defined indexes cannot be created in system catalogs.
+
+Solution: Do not create indexes in system catalogs.
+
+GAUSS-01945: "concurrent index creation on system catalog tables is not supported"
+
+SQLSTATE: 0A000
+
+Description: Indexes cannot be concurrently created in system catalogs.
+
+Solution: Do not concurrently create indexes in system catalogs.
+
+GAUSS-01946: "shared indexes cannot be created after gs_initdb"
+
+SQLSTATE: 55000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01947: "constraint must be PRIMARY, UNIQUE or EXCLUDE"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01948: "constraints cannot have index expressions"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01949: "DROP INDEX CONCURRENTLY must be first action in transaction"
+
+SQLSTATE: 0A000
+
+Description:**DROP INDEX CONCURRENTLY** must be the first statement in a transaction block.
+
+Solution: Move **DROP INDEX CONCURRENTLY** to the first statement in a transition block.
+
+GAUSS-01950: "invalid indnatts %d for index %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-01951 - GAUSS-01960
+
+<br/>
+
+GAUSS-01951: "could not find tuple for partition %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01952: "cannot reindex temporary tables of other sessions"
+
+SQLSTATE: 0A000
+
+Description: Indexes in temporary tables of other sessions cannot be reorganized.
+
+Solution: Do not reorganize indexes in temporary tables of other sessions.
+
+GAUSS-01953: "cannot reindex while reindexing"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01954: "cache lookup failed for partitioned index %u"
+
+SQLSTATE: XX000
+
+Description: Failed to find the partitioned indexes in the system catalog cache.
+
+Solution: Check whether partitioned indexes exist.
+
+GAUSS-01955: "Memory alloc failed for indexInfo"
+
+SQLSTATE: XX000
+
+Description: Failed to generate the IndexInfo structure.
+
+Solution: Ensure that the memory is sufficient.
+
+GAUSS-01956: "cache lookup failed for index %u"
+
+SQLSTATE: XX000
+
+Description: Failed to find the index in the system catalog cache.
+
+Solution: Ensure that the index name is correct.
+
+GAUSS-01957: "mergingBtreeIndexes, zero or less than 2 or greater than 4 source index relations"
+
+SQLSTATE: XX000
+
+Description: During index merge, only one index is the source index or the number of indexes imported as source indexes exceeds the maximum number 300.
+
+Solution:Contact technical support.
+
+GAUSS-01958: "mergingBtreeIndexes, only btree indexes can be merged"
+
+SQLSTATE: XX000
+
+Description: Only B-tree indexes can be merged.
+
+Solution:Contact technical support.
+
+GAUSS-01959: "target merging index '%s' already contains data"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-01961 - GAUSS-01970
+
+<br/>
+
+GAUSS-01961: "invalid enum label '%s'"
+
+SQLSTATE: 42602
+
+Description: Invalid enum type.
+
+Solution: Check whether SQL statements contain the invalid enumerated type displayed in the system.
+
+GAUSS-01962: "'%s' is not an existing enum label"
+
+SQLSTATE: 22023
+
+Description: Invalid enum type.
+
+Solution: Check whether SQL statements contain the invalid enumerated type displayed in the system.
+
+GAUSS-01963: "ALTER TYPE ADD BEFORE/AFTER is incompatible with binary upgrade"
+
+SQLSTATE: 22023
+
+Description: Enumerated type change is incompatible with binary upgrade.
+
+Solution: Check whether the SQL statements contain enumerated type change information.
+
+GAUSS-01965: "alignment '%c' is invalid for passed-by-value type of size %d"
+
+SQLSTATE: 42P17
+
+Description: The length of the pass-by-value type is invalid.
+
+Solution: Check the type definition.
+
+GAUSS-01966: "internal size %d is invalid for passed-by-value type"
+
+SQLSTATE: 42P17
+
+Description: The length of the pass-by-value type is invalid.
+
+Solution: Check the type definition.
+
+GAUSS-01967: "alignment '%c' is invalid for variable-length type"
+
+SQLSTATE: 42P17
+
+Description: The alignment is invalid for the variable-length type.
+
+Solution: Check the type definition.
+
+GAUSS-01969: "cannot assign new OID to existing shell type"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-01970: "could not form array type name for type '%s'"
+
+SQLSTATE: 42710
+
+Description: The array type name is too long.
+
+Solution: Check whether the array type length defined in the current create type definition statement exceeds the maximum number 63.
+
+<br/>
+
+## GAUSS-01971 - GAUSS-01980
+
+<br/>
+
+GAUSS-01973: "could not stat file or directory '%s': %m"
+
+SQLSTATE: XX000
+
+Description: Files or directories to be accessed during program operation do not exist.
+
+Solution: Manually create required files or directories. Alternatively, reinitialize the data directory.
+
+GAUSS-01977: "could not open file '%s': %m"
+
+SQLSTATE: XX000
+
+Description: Failed to open a file.
+
+Solution: Analyze the cause based on the error message. If the file does not exist, create one. If the permission is incorrect, change the permission. If the file is damaged, restore the file system or disk.
+
+<br/>
+
+## GAUSS-01981 - GAUSS-01990
+
+<br/>
+
+GAUSS-01983: "cannot continue WAL streaming, recovery has already ended"
+
+SQLSTATE: XX000
+
+Description: The walreceiver does not need to be enabled on the primary server. If it is enabled, an error message is reported.
+
+Solution: The error message reporting is normal and does not need to be handled.
+
+GAUSS-01984: "invalid standby handshake message type %d"
+
+SQLSTATE: 08P01
+
+Description: The primary server receives an invalid handshake type from the standby server.
+
+Solution: Check whether the primary and standby server environment is normal and whether packet loss occurs. If no such issues exist, an internal error occurs. Contact technical support.
+
+GAUSS-01986: "invalid standby message type '%c'"
+
+SQLSTATE: 08P01
+
+Description: The primary server receives an invalid message type from the standby server.
+
+Solution: Check whether the primary and standby server environment is normal and whether packet loss occurs. If no such issues exist, an internal error occurs. Contact technical support.
+
+GAUSS-01987: "number of requested standby connections exceeds max_wal_senders (currently %d)"
+
+SQLSTATE: 53300
+
+Description: The number of connection requests from the standby server to the primary server exceeds the upper limit. The reason may be that the standby server attempts to connect to the primary server many times but fail. Also, the value of **max_wal_senders** for the primary server may be too small, especially when the build command is executed on the standby server, because two threads are started on the primary server to send data and logs.
+
+Solution: Check whether the former connections are ended. If not, manually close them. Check whether the value of **max_wal_senders** is too small. If yes, increase the value.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/21-GAUSS-02001-GAUSS-02100.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/21-GAUSS-02001-GAUSS-02100.md
new file mode 100644
index 0000000000000000000000000000000000000000..1502056d6e42e3c0117f8933aa067b9ffd3a8e58
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/21-GAUSS-02001-GAUSS-02100.md
@@ -0,0 +1,376 @@
+---
+title: GAUSS-02001 - GAUSS-02100
+summary: GAUSS-02001 - GAUSS-02100
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-02001 - GAUSS-02100
+
+<br/>
+
+## GAUSS-02011 - GAUSS-02020
+
+<br/>
+
+GAUSS-02015: "select() failed: %m"
+
+SQLSTATE: XX000
+
+Description: The select function failed.
+
+Solution: Determine the root cause based on the error code. The error codes returned are standard error codes. See descriptions of related error codes by querying **Help** in the system.
+
+GAUSS-02016: "replconninfo1 or replconninfo2 not configured."
+
+SQLSTATE: XX000
+
+Description: The configuration of **replconninfo1** or **replconninfo2** is empty in the **postgresql.conf** file.
+
+Solution: Use **gs_guc** to modify corresponding configuration options in the **postgresql.conf** file.
+
+GAUSS-02017: "terminating walreceiver process due to administrator command"
+
+SQLSTATE: 57P01
+
+Description: The walreceiver thread of the standby server receives the **SIGTERM** message. The error message is printed before the process exits.
+
+Solution: Search logs to check whether the preceding operations are correct.
+
+GAUSS-02018: "walreceiver still running according to shared memory state"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02019: "terminating walreceiver process due to the death of walrcvwriter"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02021 - GAUSS-02030
+
+<br/>
+
+GAUSS-02022: "rm xlog comand is not from primary,peer_role=%d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02023: "return type must be a row type"
+
+SQLSTATE: XX000
+
+Description: The tuple descriptor constructed is not a row result message.
+
+Solution: Query again. Check whether this error persists. Contact technical support.
+
+GAUSS-02026: "requested WAL segment %s has already been removed"
+
+SQLSTATE: XX000
+
+Description: The logs requested by the standby/secondary server have been removed from the primary server.
+
+Solution: Check whether there are discontinuous log names in the **pg_xlog** directory of the primary server instances. Re-build the standby server or restart the secondary server. In the cluster environment, the CM server automatically rebuilds the standby server. "
+
+GAUSS-02027: "could not open file '%s' (log file %u, segment %u): %m"
+
+SQLSTATE: XX000
+
+Description: A specific log segment file cannot be opened.
+
+Solution: Check whether the file exists in the **pg_xlog** directory of the instances or whether the permission is correct. Resolve the problem based on specific log error codes. "
+
+GAUSS-02030: "%u/%u/%u invalid bcm buffer %u"
+
+SQLSTATE: XX000
+
+Description: The specified BCM buffer cannot be opened.
+
+Solution: Check whether abnormal deletion occurs by analyzing logs and data files. Restart instances. "
+
+<br/>
+
+## GAUSS-02031 - GAUSS-02040
+
+<br/>
+
+GAUSS-02032: "syntax error: unexpected character '%s'"
+
+SQLSTATE: 42601
+
+Description: Syntax error. The character is unrecognizable.
+
+Solution: Record error information. Contact technical support.
+
+GAUSS-02039: "could not rename file '%s' to '%s': %m"
+
+SQLSTATE: XX000
+
+Description: The file cannot be renamed.
+
+Solution: Resolve the problem based on concrete error codes.
+
+GAUSS-02040: "could not unlink file '%s': %m"
+
+SQLSTATE: XX000
+
+Description: The file cannot be removed.
+
+Solution: Resolve the problem based on concrete error codes.
+
+<br/>
+
+## GAUSS-02041 - GAUSS-02050
+
+<br/>
+
+GAUSS-02041: "could not fsync file '%s': %m"
+
+SQLSTATE: XX000
+
+Description: The file cannot be synchronized.
+
+Solution: Resolve the problem based on concrete error codes.
+
+<br/>
+
+## GAUSS-02061 - GAUSS-02070
+
+<br/>
+
+GAUSS-02063: "cannot continue Data streaming, recovery has already ended"
+
+SQLSTATE: XX000
+
+Description: Restoration of the current instance has been terminated. Data replication does not need to be continued.
+
+Solution: 1. It is normal to report the error message. 2. Ensure that the standby instance is upgraded to a primary instance at a right time. "
+
+GAUSS-02064: "writing incorrect data page checksum at: rnode[%u,%u,%u], blocknum[%u], pageoffset[%u], size[%u], queueoffset[%u/%u]"
+
+SQLSTATE: XX000
+
+Description: A data page CRC received by the standby server from the primary server fails to be verified.
+
+Solution: Check whether the network environment is normal or whether a packet is lost.
+
+GAUSS-02065: "invalid tablespace link %s: %m"
+
+SQLSTATE: XX000
+
+Description: Invalid symbol links exist under the **pg_tblspc** directory of the standby server.
+
+Solution: Check whether the error is caused by malicious operation. If it is, recover the environment. Alternatively, contact technical support to fix the standby instance. "
+
+GAUSS-02069: "could not find type OID for relation %u"
+
+SQLSTATE: XX000
+
+Description: Failed to find the required relation.
+
+Solution: The system catalog is abnormal. Contact technical support.
+
+GAUSS-02070: "unrecognized list node type: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02071 - GAUSS-02080
+
+<br/>
+
+GAUSS-02077: "incomplete Bitmapset structure"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02078: "unrecognized token: '%.*s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02079: "unterminated Bitmapset structure"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02080: "unrecognized integer: '%.*s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02081 - GAUSS-02090
+
+<br/>
+
+GAUSS-02081: "unrecognized boolop '%.*s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02082: "NULL relname for RTE %u found"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02083: "NULL relnamespace for RTE %u found"
+
+SQLSTATE: XX000
+
+Description: The tablespace of the table is null.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02086: "parseNodeString(): badly formatted node string '%s'…"
+
+SQLSTATE: XX000
+
+Description: The correct node information is not found.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02087: "byval datum but length = %lu"
+
+SQLSTATE: XX000
+
+Description: The data represented by the current string exceeds the range represented by **datum**.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02088: "expected ']' to end datum, but got '%s'; length = %lu"
+
+SQLSTATE: XX000
+
+Description: The content does not end with a right square bracket (]).
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02090: "unterminated List structure"
+
+SQLSTATE: XX000
+
+Description: An unexpected empty link list exists.
+
+Solution: Internal system error. Contact technical support.
+
+<br/>
+
+## GAUSS-02091 - GAUSS-02100
+
+<br/>
+
+GAUSS-02091: "unrecognized OID: '%.*s'"
+
+SQLSTATE: XX000
+
+Description: The OID cannot be identified.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02092: "unexpected right parenthesis"
+
+SQLSTATE: XX000
+
+Description: An unexpected right bracket is read during node information reading.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02093: "cannot list_concat() a list to itself"
+
+SQLSTATE: XX000
+
+Description: A list cannot be connected to itself.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02094: "tuple offset out of range: %u"
+
+SQLSTATE: XX000
+
+Description: The data offset exceeds the maximum number of tuples that can be saved on a page.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02095: "negative bitmapset member not allowed"
+
+SQLSTATE: XX000
+
+Description: The location information cannot be a negative number.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02096: "bitmapset is empty"
+
+SQLSTATE: XX000
+
+Description: The current bitmapset cannot be empty.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02097: "bitmapset has multiple members"
+
+SQLSTATE: XX000
+
+Description: The bitmapset has duplicate members.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02098: "cannot get type for untransformed sublink"
+
+SQLSTATE: XX000
+
+Description: For the sublink expression node, the sublink is not converted, so the expression type cannot be obtained.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02099: "cannot get collation for untransformed sublink"
+
+SQLSTATE: XX000
+
+Description: For the sublink expression node, the sublink is not converted, so the collation type cannot be obtained.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02100: "cannot set collation for untransformed sublink"
+
+SQLSTATE: XX000
+
+Description: Failed to set collation for converted sublinks.
+
+Solution: Internal system error. Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/22-GAUSS-02101-GAUSS-02200.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/22-GAUSS-02101-GAUSS-02200.md
new file mode 100644
index 0000000000000000000000000000000000000000..f5e2925fe77ba2f268ef487d23389af1de6ac275
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/22-GAUSS-02101-GAUSS-02200.md
@@ -0,0 +1,580 @@
+---
+title: GAUSS-02101 - GAUSS-02200
+summary: GAUSS-02101 - GAUSS-02200
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-02101 - GAUSS-02200
+
+<br/>
+
+## GAUSS-02101 - GAUSS-02110
+
+<br/>
+
+GAUSS-02101: "Invalid RTE found."
+
+SQLSTATE: XX000
+
+Description: Internal system error. The table information is invalid.
+
+Solution: Contact technical support.
+
+GAUSS-02102: "could not determine which collation to use for regular expression"
+
+SQLSTATE: 42P22
+
+Description: Failed to determine a proper collation for regular expressions.
+
+Solution: Correct the regular expression definition.
+
+GAUSS-02103: "syntax error at line %d: unexpected character '%s'"
+
+SQLSTATE: XX000
+
+Description: Syntax error.
+
+Solution: Modify the SQL statement.
+
+GAUSS-02104: "%s at line %d"
+
+SQLSTATE: XX000
+
+Description: Syntax error.
+
+Solution: Modify the SQL statement.
+
+GAUSS-02105: "incorrect number of columns in row (expected %d, got %d)"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02106: "relation not open"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02107: "too many columns"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02108: "unrecognized process type: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02109: "close of %s when %s was expected"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02110: "close of %s before any relation was opened"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02111 - GAUSS-02120
+
+<br/>
+
+GAUSS-02111: "no open relation to close"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02112: "unrecognized type '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02114: "type OID %u not found in TypInfo"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02115: "out of memory"
+
+SQLSTATE: XX000
+
+Description: Failed to allocate the memory.
+
+Solution: Ensure that the system has sufficient memory.
+
+GAUSS-02116: "Incorrect redistribution operation"
+
+SQLSTATE: 42809
+
+Description: Invalid distribution type.
+
+Solution: Support only **HASH** and **MODULO**.
+
+GAUSS-02117: "a list of nodes should have at least one node"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02119: "Error: no such supported locator type: %c\n"
+
+SQLSTATE: XX000
+
+Description: The specified distribution type cannot be used.
+
+Solution: Support only **REPLICATED**, **HASH**, **RROBIN**, and **MODULO**.
+
+GAUSS-02120: "cache lookup failed for pgxc_group %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02121 - GAUSS-02130
+
+<br/>
+
+GAUSS-02124: "Bucket id(%d:%d) out of range."
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02125: "Node(%d) has no buckets on it."
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02128: "PGXC Group %s: group already defined"
+
+SQLSTATE: 42710
+
+Description: The group has already been defined.
+
+Solution: Delete the existing defined group with a duplicate name. Alternatively, define the group with a new name.
+
+GAUSS-02129: "PGXC node %s: only Datanodes can be group members"
+
+SQLSTATE: 42601
+
+Description: The member of the group is not a DN.
+
+Solution: Modify the SQL statement for creating a node group.
+
+<br/>
+
+## GAUSS-02131 - GAUSS-02140
+
+<br/>
+
+GAUSS-02135: "PGXC Group %s: group not defined"
+
+SQLSTATE: 42710
+
+Description: The node group corresponding to **group_name** does not exist.
+
+Solution: Check whether the **group_name** called is correct, or whether the group is correctly created.
+
+GAUSS-02136: "PGXC Group %s: group not defined"
+
+SQLSTATE: XX000
+
+Description: The node group corresponding to **group_name** does not exist.
+
+Solution: Check whether the **group_name** called is correct, or whether the group is correctly created.
+
+GAUSS-02137: "No options specified"
+
+SQLSTATE: 42601
+
+Description: A syntax error occurs. The **CREATE NODE** statement does not contain **with option**.
+
+Solution: Correct the statement. (User execution of the **CREATE NODE** statement is not recommended.)
+
+GAUSS-02138: "port value is out of range"
+
+SQLSTATE: 22003
+
+Description: The specified **port** value is out of range.
+
+Solution: Adjust the **port** value in the SQL statement.
+
+<br/>
+
+## GAUSS-02141 - GAUSS-02150
+
+<br/>
+
+GAUSS-02141: "port1 value is out of range"
+
+SQLSTATE: 22003
+
+Description: The specified **port1** value is out of range.
+
+Solution: Adjust the **port** value in the SQL statement.
+
+GAUSS-02143: "control_port1 value is out of range"
+
+SQLSTATE: 22003
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02144: "type value is incorrect, specify 'coordinator or 'datanode'"
+
+SQLSTATE: 22023
+
+Description: The specified type is incorrect. The specified type must be either the **coordinator** type or **datanode** type.
+
+Solution: Modify the SQL statement.
+
+GAUSS-02145: "incorrect option: %s"
+
+SQLSTATE: 42601
+
+Description: The specified option is incorrect.
+
+Solution: Modify the SQL statement.
+
+GAUSS-02146: "PGXC node %s: cannot be a primary node, it has to be a Datanode"
+
+SQLSTATE: 42601
+
+Description: Failed to specify the CN as the primary node by executing the **CREATE NODE** or **ALTER NODE** statement.
+
+Solution: Do not specify the CN as the primary node.
+
+GAUSS-02147: "PGXC node %s: cannot be a preferred node, it has to be a Datanode"
+
+SQLSTATE: 42601
+
+Description: The preferred node must be a DN, not a CN.
+
+Solution: Do not specify the CN as the primary node.
+
+GAUSS-02148: "PGXC node %s: Node type not specified"
+
+SQLSTATE: 42601
+
+Description: A syntax error occurs. **with option** of the **CREATE NODE** statement does not contain a **type** field.
+
+Solution: Modify the statement.
+
+GAUSS-02149: "Please choose different node name."
+
+SQLSTATE: 42P17
+
+Description: Failed to generate the unique node ID for the node name specified by the **CREATE NODE** statement in **HASH** mode.
+
+Solution: Modify the specified node name.
+
+<br/>
+
+## GAUSS-02151 - GAUSS-02160
+
+<br/>
+
+GAUSS-02152: "Node name '%s' is too long"
+
+SQLSTATE: 42P17
+
+Description: The specified node name is too long.
+
+Solution: Modify the specified node name.
+
+GAUSS-02153: "Failed to create coordinator, the maximum number of coordinators %d specified by 'max_coordinators' has been reached."
+
+SQLSTATE: 42601
+
+Description: A syntax error occurs. The number of CNs created has exceeded that specified by **max_coordinators**.
+
+Solution: Increase the **max_coordinators** value.
+
+GAUSS-02154: "Failed to create datanode, the maximum number of datanodes %d specified by 'max_datanodes' has been reached."
+
+SQLSTATE: 42601
+
+Description: A syntax error occurs. The number of DNs created has exceeded that specified by **max_datanodes**.
+
+Solution: Increase the **max_datanodes** value.
+
+GAUSS-02155: "PGXC node %s: two nodes cannot be primary"
+
+SQLSTATE: 42601
+
+Description: A syntax error occurs. A primary node has been created.
+
+Solution: Change the primary node created to a non-primary node as required.
+
+GAUSS-02157: "cache lookup failed for object %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02158: "PGXC node %s: cannot alter Coordinator to Datanode"
+
+SQLSTATE: 42601
+
+Description: A syntax error occurs. Failed to change the CN to a DN.
+
+Solution: Do not change a CN to a DN.
+
+GAUSS-02159: "PGXC node %s: cannot alter Datanode to Coordinator"
+
+SQLSTATE: 42601
+
+Description: A syntax error occurs. Failed to change the DN to a CN.
+
+Solution: Do not change a DN to a CN.
+
+<br/>
+
+## GAUSS-02161 - GAUSS-02170
+
+<br/>
+
+GAUSS-02161: "PGXC Node %s: cannot drop local node"
+
+SQLSTATE: 42601
+
+Description: A syntax error occurs. Failed to drop the local node.
+
+Solution: Do not drop the local node.
+
+GAUSS-02167: "Can not connect to pool manager"
+
+SQLSTATE: 58030
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02171 - GAUSS-02180
+
+<br/>
+
+GAUSS-02177: "pool manager only supports UNIX socket"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02178: "unexpected EOF within message length word:%m"
+
+SQLSTATE: 08P01
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02179: "invalid message length"
+
+SQLSTATE: 08P01
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02180: "incomplete message from client:%m"
+
+SQLSTATE: 08P01
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02181 - GAUSS-02190
+
+<br/>
+
+GAUSS-02181: "pooler failed to send res: %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02182: "could not receive data from client: %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02183: "incomplete message from client"
+
+SQLSTATE: 08P01
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02184: "unexpected message code"
+
+SQLSTATE: 08P01
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02185: "pooler failed to send pids: %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02186: "Unexpected response from the Datanodes for 'c' message, current request type %d"
+
+SQLSTATE: XX001
+
+Description: An internal system error occurs. A message having the 'c' packet header comes across a non-COPY TO request.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02188: "Unexpected response from the Datanodes for 'T' message, current request type %d"
+
+SQLSTATE: XX001
+
+Description: An internal system error occurs. A message having the 'T' packet header comes across a non-row description information sequence.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02189: "Unexpected response from the Datanodes for 'S' message, current request type %d"
+
+SQLSTATE: XX001
+
+Description: An internal system error occurs. A message having the 'S' packet header comes across a non-SET request.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02190: "Unexpected response from the Datanodes for 'G' message, current request type %d"
+
+SQLSTATE: XX001
+
+Description: An internal system error occurs. A message having the 'G' packet header comes across a non-COPY IN request.
+
+Solution: Internal system error. Contact technical support.
+
+<br/>
+
+## GAUSS-02191 - GAUSS-02200
+
+<br/>
+
+GAUSS-02191: "Unexpected response from the Datanodes for 'H' message, current request type %d"
+
+SQLSTATE: XX001
+
+Description: An internal system error occurs. A message having the 'H' packet header comes across a non-COPY OUT request.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02192: "Unexpected response from the Datanodes for 'd' message, current request type %d"
+
+SQLSTATE: XX001
+
+Description: An internal system error occurs. A message having the 'd' packet header comes across a non-COPY OUT request.
+
+Solution:Contact technical support.
+
+GAUSS-02193: "Unexpected response from the Datanodes for 'D' message, current request type %d"
+
+SQLSTATE: XX001
+
+Description: An internal system error occurs. A message having the 'D' packet header comes across a non-data receiving request.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02195: "Unexpected response from Datanode"
+
+SQLSTATE: XX000
+
+Description: An internal system error occurs. An unexpected response comes from the DN.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02196: "Failed to read response from Datanodes Detail: %s\n"
+
+SQLSTATE: XX000
+
+Description: An internal system error occurs. Failed to receive response from a DN.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02197: "Failed to fetch from Datanode"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02198: "Unexpected response from the Datanodes, result = %d, request type %d"
+
+SQLSTATE: XX000
+
+Description: An internal system error occurs. An unexpected response comes from the DN.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02200: "failed to send PREPARE TRANSACTION command to the node %u"
+
+SQLSTATE: XX000
+
+Description: An internal system error occurs. Failed to deliver the **PREPARE TRANSACTION** command to the specified node.
+
+Solution: Internal system error. Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/23-GAUSS-02201-GAUSS-02300.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/23-GAUSS-02201-GAUSS-02300.md
new file mode 100644
index 0000000000000000000000000000000000000000..d58166e7b369e5e1882e23fbcb25710806238d7e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/23-GAUSS-02201-GAUSS-02300.md
@@ -0,0 +1,554 @@
+---
+title: GAUSS-02201 - GAUSS-02300
+summary: GAUSS-02201 - GAUSS-02300
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-02201 - GAUSS-02300
+
+<br/>
+
+## GAUSS-02201 - GAUSS-02210
+
+<br/>
+
+GAUSS-02202: "Failed to PREPARE the transaction on one or more nodes"
+
+SQLSTATE: XX000
+
+Description: Failed to prepare the required transaction on the node.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02209: "Error while running COPY"
+
+SQLSTATE: XX000
+
+Description: An unexpected response comes from the DN during information collection.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02210: "could not obtain connection from pool"
+
+SQLSTATE: XX000
+
+Description: Failed to obtain the connection from the connection pool.
+
+Solution: Increase the **max_pool_size** value.
+
+<br/>
+
+## GAUSS-02211 - GAUSS-02220
+
+<br/>
+
+GAUSS-02211: "cannot run transaction to remote nodes during recovery"
+
+SQLSTATE: XX000
+
+Description: Failed to execute a transaction on the remote node during cluster restoration.
+
+Solution: Commit the transaction after the restoration is complete.
+
+GAUSS-02212: "Failed to get next transaction ID"
+
+SQLSTATE: XX000
+
+Description: An internal error occurs. Failed to obtain the next transaction ID.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02214: "Failed to send command to Datanodes"
+
+SQLSTATE: XX000
+
+Description: Failed to deliver the command to the DN.
+
+Solution: Correct the cluster connection status.
+
+GAUSS-02215: "Unexpected response from Datanode %u"
+
+SQLSTATE: XX000
+
+Description: An internal system error occurs. An unexpected response comes from the DN.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02216: "Could not begin transaction on Datanodes %u."
+
+SQLSTATE: XX000
+
+Description: Failed to start the transaction on the primary node.
+
+Solution: Correct the cluster connection status.
+
+GAUSS-02217: "Failed to read response from Datanodes when ending query"
+
+SQLSTATE: XX000
+
+Description: An internal error occurs. Failed to read the response from the DN when the query ends.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02218: "Failed to close Datanode cursor"
+
+SQLSTATE: XX000
+
+Description: An internal error occurs. Failed to close the cursor on the DN.
+
+Solution: Correct the cluster connection status.
+
+GAUSS-02219: "Number of user-supplied parameters do not match the number of remote parameters"
+
+SQLSTATE: XX000
+
+Description: An internal error occurs. The number of parameters provided by the user does not match that of parameters required for the query.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02220: "cannot run EXECUTE DIRECT with utility inside a transaction block"
+
+SQLSTATE: 25001
+
+Description: Failed to execute the **EXECUTE DIRECT** statement in a transaction.
+
+Solution: Execute the **EXECUTE DIRECT** statement outside the transaction.
+
+<br/>
+
+## GAUSS-02221 - GAUSS-02230
+
+<br/>
+
+GAUSS-02221: "Could not begin transaction on Datanodes"
+
+SQLSTATE: XX000
+
+Description: Failed to start the transaction on the primary node.
+
+Solution: Correct the cluster connection status.
+
+GAUSS-02223: "Could not begin transaction on coordinators"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02225: "Unexpected response from coordinator %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02228: "prepared transaction with identifier '%s' does not exist"
+
+SQLSTATE: XX000
+
+Description: The transaction identifier parameter does not exist.
+
+Solution: Check the input parameter and perform the operation again.
+
+GAUSS-02229: "NULL junk attribute"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02230: "Failed to read response from Datanode %u when ending query"
+
+SQLSTATE: XX000
+
+Description: Failed to receive results from the DN.
+
+Solution: Check the DN status, restart the cluster, and query again.
+
+<br/>
+
+## GAUSS-02231 - GAUSS-02240
+
+<br/>
+
+GAUSS-02232: "pgxc_pool_reload cannot run inside a transaction block"
+
+SQLSTATE: 25001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02234: "must define Database name or user name"
+
+SQLSTATE: 42000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02236: "The CREATE BARRIER PREPARE message is expected to arrive at a Coordinator from another Coordinator"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02237: "The CREATE BARRIER END message is expected to arrive at a Coordinator from another Coordinator"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02238: "The CREATE BARRIER EXECUTE message is expected to arrive from a Coordinator"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02239: "Failed to send CREATE BARRIER PREPARE request to the node"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02241 - GAUSS-02250
+
+<br/>
+
+GAUSS-02241: "CREATE BARRIER PREPARE command failed with error %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02242: "Failed to send CREATE BARRIER EXECUTE request to the node"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02244: "CREATE BARRIER command is not expected from another Coordinator"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02250: "cannot open %s query as cursor"
+
+SQLSTATE: 42P11
+
+Description: Failed to open the plan as a cursor.
+
+Solution: Check whether the cursor definition is correct.
+
+<br/>
+
+## GAUSS-02251 - GAUSS-02260
+
+<br/>
+
+GAUSS-02252: "%s is not allowed in a non-volatile function"
+
+SQLSTATE: 0A000
+
+Description: Failed to use the statement for a non-volatile function.
+
+Solution: Check whether the function definition is correct.
+
+GAUSS-02253: "invalid portal in SPI cursor operation"
+
+SQLSTATE: XX000
+
+Description: Failed to obtain variables during execution.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02258: "Failed to read response from Datanodes. Detail: %s\n"
+
+SQLSTATE: XX000
+
+Description: The connection at the transmit end is disconnected. The cause is specified in **Detail**.
+
+Solution: Check whether the peer DN is faulty or whether the network is normal.
+
+GAUSS-02260: "Unhandled datatype for modulo or hash distribution\n"
+
+SQLSTATE: XX000
+
+Description: The data distribution type is invalid.
+
+Solution: Check whether the distribution column definition in the table is correct.
+
+<br/>
+
+## GAUSS-02261 - GAUSS-02270
+
+<br/>
+
+GAUSS-02265: "BitmapOr doesn't support zero inputs"
+
+SQLSTATE: XX000
+
+Description: An internal system error occurs. The input of the **BitmapOr** operator is **NULL**.
+
+Solution:Contact technical support.
+
+GAUSS-02266: "could not identify CTID variable"
+
+SQLSTATE: 42809
+
+Description: The obtained variable is not the CTID variable.
+
+Solution: View the execution plan and check whether the type returned by the expression is CTID. If not, contact technical support.
+
+GAUSS-02268: "invalid operation on partition, allowed are UPDATE/DELETE/SELECT"
+
+SQLSTATE: XX000
+
+Description: Partitioned tables can be only deleted, queried, and modified.
+
+Solution: Check whether the current operation performed for the partitioned table is correct.
+
+<br/>
+
+## GAUSS-02271 - GAUSS-02280
+
+<br/>
+
+GAUSS-02271: "could not determine actual type of argument declared %s"
+
+SQLSTATE: 42804
+
+Description: Failed to determine the data type of the parameter.
+
+Solution: Check whether the function definition is correct.
+
+GAUSS-02272: "%s is not allowed in a SQL function"
+
+SQLSTATE: 0A000
+
+Description: SQL functions cannot contain transaction statements.
+
+Solution: Check whether the function definition is correct.
+
+GAUSS-02273: "could not determine actual result type for function declared to return type %s"
+
+SQLSTATE: 42804
+
+Description: Failed to determine the return type of the function.
+
+Solution: Check whether the function definition is correct.
+
+GAUSS-02274: "failed to fetch lazy-eval tuple"
+
+SQLSTATE: 22P08
+
+Description: An internal system error occurs. Failed to obtain a tuple from the **tuplestore**.
+
+Solution:Contact technical support.
+
+GAUSS-02275: "return type mismatch in function declared to return %s"
+
+SQLSTATE: 42P13
+
+Description: The return type is inconsistent with that defined by the function.
+
+Solution: Check whether the function definition is correct.
+
+GAUSS-02277: "mergejoin clause is not an OpExpr"
+
+SQLSTATE: XX000
+
+Description: A plan error occurs. The **MergeJoin** condition is not an arithmetic expression.
+
+Solution: Generated plan error. Contact technical support.
+
+GAUSS-02278: "unsupported mergejoin strategy %d"
+
+SQLSTATE: XX000
+
+Description: A plan error occurs. The sorting policy used by **MergeJoin** is incorrect.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02279: "cannot merge using non-equality operator %u"
+
+SQLSTATE: XX000
+
+Description: A plan error occurs. The connection policy used by **MergeJoin** is incorrect.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02280: "missing support function %d(%u,%u) in opfamily %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02281 - GAUSS-02290
+
+<br/>
+
+GAUSS-02281: "unrecognized mergejoin state: %d"
+
+SQLSTATE: XX000
+
+Description: An execution error occurs. The execution policy chosen by **MergeJoin** is incorrect.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02282: "RIGHT JOIN is only supported with merge-joinable join conditions"
+
+SQLSTATE: 0A000
+
+Description: A plan error occurs. The **merge right join** is not supported.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02283: "FULL JOIN is only supported with merge-joinable join conditions"
+
+SQLSTATE: 0A000
+
+Description: For **MergeJoin**, **FULL JOIN** cannot process non-constant expressions (**JOIN** clauses).
+
+Solution: Check whether the **JOIN** clauses are constants during **FULL JOIN** invocation in the SQL statement.
+
+GAUSS-02284: "non-MVCC snapshots are not supported in index-only scans"
+
+SQLSTATE: 0A000
+
+Description: The index-only scan does not support MVCC snapshots.
+
+Solution:Contact technical support.
+
+GAUSS-02285: "EvalPlanQual recheck is not supported in index-only scans"
+
+SQLSTATE: 0A000
+
+Description: The index-only scan does not support recheck during concurrent update.
+
+Solution:Contact technical support.
+
+GAUSS-02288: "could not find hash function for hash operator %u"
+
+SQLSTATE: 42883
+
+Description: The corresponding hash function cannot be found.
+
+Solution: Check whether the data type supports the hash function.
+
+GAUSS-02289: "cursor '%s' is not a SELECT query"
+
+SQLSTATE: 24000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02290: "cursor '%s' is held from a previous transaction"
+
+SQLSTATE: 24000
+
+Description: The cursor is held by the previous transaction.
+
+Solution: Check the cursor status.
+
+<br/>
+
+## GAUSS-02291 - GAUSS-02300
+
+<br/>
+
+GAUSS-02291: "cursor '%s' has multiple FOR UPDATE/SHARE references to table '%s'"
+
+SQLSTATE: 24000
+
+Description: Multiple cursors are defined for the table.
+
+Solution: Check whether the cursor is repeatedly defined in the SQL statement.
+
+GAUSS-02292: "cursor '%s' does not have a FOR UPDATE/SHARE reference to table '%s'"
+
+SQLSTATE: 24000
+
+Description: In SQL statements containing **CURRENT OF** and **UPDATE**, the **UPDATE/SHARE** syntax for the table is not defined.
+
+Solution: Check whether the update/share operation has been properly defined for the table. Alternatively, check whether the optimizer works properly.
+
+GAUSS-02294: "cursor '%s' is not a simply updatable scan of table '%s'"
+
+SQLSTATE: 24000
+
+Description: Failed to find the corresponding scan nodes by executing query statements containing the **CURRENT OF** syntax and not containing the **UPDATE** syntax.
+
+Solution: Check whether the operation syntax is properly defined in the SQL statement. Alternatively, check whether the optimizer works properly.
+
+GAUSS-02295: "type of parameter %d (%s) does not match that when preparing the plan (%s)"
+
+SQLSTATE: 42804
+
+Description: The parameter type returned during execution is inconsistent with that of expressions described in the execution plan.
+
+Solution: 1. Check whether the types of expression parameters in the SQL statements are consistent. 2. Check the executable code to ensure that the parameter attribute is correct. "
+
+GAUSS-02296: "no value found for parameter %d"
+
+SQLSTATE: 42704
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02297: "LIMIT subplan failed to run backwards"
+
+SQLSTATE: XX005
+
+Description: The **NULL** is returned in advance when the backward scan is performed on the **LIMIT** lower-layer operator.
+
+Solution:Contact technical support.
+
+GAUSS-02298: "impossible LIMIT state: %d"
+
+SQLSTATE: XX006
+
+Description: The LIMIT state is incorrect.
+
+Solution:Contact technical support.
+
+GAUSS-02299: "OFFSET must not be negative"
+
+SQLSTATE: 2201X
+
+Description: The **OFFSET count** value is an invalid negative value.
+
+Solution: Change the **count** value to a value greater than or equal to 0.
+
+GAUSS-02300: "LIMIT must not be negative"
+
+SQLSTATE: 2201W
+
+Description: The **LIMIT count** value is an invalid negative value.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/24-GAUSS-02301-GAUSS-02400.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/24-GAUSS-02301-GAUSS-02400.md
new file mode 100644
index 0000000000000000000000000000000000000000..46b5361571afc54c8cc8487bc4a09f17981bf8b5
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/24-GAUSS-02301-GAUSS-02400.md
@@ -0,0 +1,759 @@
+---
+title: GAUSS-02301 - GAUSS-02400
+summary: GAUSS-02301 - GAUSS-02400
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-02301 - GAUSS-02400
+
+<br/>
+
+## GAUSS-02301 - GAUSS-02310
+
+<br/>
+
+GAUSS-02301: "frame starting offset must not be null"
+
+SQLSTATE: 22004
+
+Description: The **start offset** specified by the window frame clause is **NULL**.
+
+Solution: Check the SQL statement to ensure that the **start offset** in the frame clause is not **NULL**.
+
+GAUSS-02302: "frame starting offset must not be negative"
+
+SQLSTATE: 22023
+
+Description: The **start offset** specified by the window frame clause is negative.
+
+Solution: Check the SQL statement to ensure that the **start offset** in the frame clause is not negative.
+
+GAUSS-02303: "frame ending offset must not be null"
+
+SQLSTATE: 22004
+
+Description: The **ending offset** specified by the window frame clause is **NULL**.
+
+Solution: Check the SQL statement to ensure that the **ending offset** in the frame clause is not **NULL**.
+
+GAUSS-02304: "frame ending offset must not be negative"
+
+SQLSTATE: 22023
+
+Description: The **ending offset** specified by the window frame clause is negative.
+
+Solution: Check the SQL statement to ensure that the **ending offset** in the frame clause is not negative.
+
+GAUSS-02306: "WindowFunc with winref %u assigned to WindowAgg with winref %u"
+
+SQLSTATE: 42804
+
+Description: A plan error occurs. The sequence number of **WindowFunc** does not match that in **WindowAgg**.
+
+Solution:Contact technical support.
+
+GAUSS-02307: "aggregate %u needs to have compatible input type and transition type"
+
+SQLSTATE: 42P13
+
+Description: The type of the input parameter or the intermediate data is incompatible with the aggregate function.
+
+Solution: Modify the type of the input parameter or intermediate data.
+
+GAUSS-02308: "cannot fetch row before WindowObject's mark position"
+
+SQLSTATE: 22P08
+
+Description: Internal execution logic error.
+
+Solution:Contact technical support.
+
+GAUSS-02309: "cannot move WindowObject's mark position backward"
+
+SQLSTATE: 0A000
+
+Description: Internal execution logic error.
+
+Solution:Contact technical support.
+
+GAUSS-02310: "specified position is out of window: "
+
+SQLSTATE: XX000
+
+Description: Internal execution logic error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02311 - GAUSS-02320
+
+<br/>
+
+GAUSS-02312: "number of array dimensions (%d) exceeds the maximum allowed (%d)"
+
+SQLSTATE: 54000
+
+Description: The number of array dimensions exceeds the upper limit.
+
+Solution: Ensure that the number of array dimensions is less than the upper limit displayed in the error information.
+
+GAUSS-02313: "array subscript in assignment must not be null"
+
+SQLSTATE: 22004
+
+Description: The array subscript in the assignment statement cannot be **NULL**.
+
+Solution: Use a proper array subscript.
+
+GAUSS-02315: "no aggregates in this expression context"
+
+SQLSTATE: 42P25
+
+Description: Expressions do not contain any aggregate functions.
+
+Solution: Check the **AggRef** expression in the SQL statement.
+
+GAUSS-02316: "no window functions in this expression context"
+
+SQLSTATE: 42P20
+
+Description: Expressions do not contain any window functions.
+
+Solution: Check the **WindowFunc** expression in the SQL statement.
+
+GAUSS-02317: "attribute number %d exceeds number of columns %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02318: "attribute %d has wrong type"
+
+SQLSTATE: 42P24
+
+Description: The type does not match.
+
+Solution: Check the SQL statement based on the reported error information.
+
+GAUSS-02319: "table row type and query-specified row type do not match"
+
+SQLSTATE: 42804
+
+Description: Types of table rows do not match those defined in queries.
+
+Solution: Modify types of table rows to match those defined in queries.
+
+<br/>
+
+## GAUSS-02321 - GAUSS-02330
+
+<br/>
+
+GAUSS-02322: "attribute '%s' does not exist"
+
+SQLSTATE: XX000
+
+Description: The attribute column does not exist.
+
+Solution: Check the SQL statement based on the column names.
+
+GAUSS-02323: "set-return function not supported in vector eninge"
+
+SQLSTATE: 0A000
+
+Description: The feature is not supported.
+
+Solution: Do not use this feature.
+
+GAUSS-02324: "functions and operators can take at most one set argument"
+
+SQLSTATE: 0A000
+
+Description: The feature is not supported. Only a set value is allowed in function input parameters.
+
+Solution: Use at most one set value for function input parameters.
+
+GAUSS-02325: "function returning setof record called in context that cannot accept type record"
+
+SQLSTATE: 0A000
+
+Description: The feature is not supported. The function that returns a result set fails to receive a record type.
+
+Solution: Do not use the record type for any functions that return result sets.
+
+GAUSS-02326: "function return row and query-specified return row do not match"
+
+SQLSTATE: 42804
+
+Description: The number of tuple attributes returned by the function is inconsistent with that as expected.
+
+Solution: Check whether the types and number of columns returned are consistent with those defined by the function.
+
+GAUSS-02327: "table-function protocol for materialize mode was not followed"
+
+SQLSTATE: 39P02
+
+Description: Failed to use the function that returns a result set in the materialized mode.
+
+Solution: Do not use the function that returns a result set in the materialized mode.
+
+GAUSS-02328: "unrecognized table-function returnMode: %d"
+
+SQLSTATE: 39P02
+
+Description: Failed to recognize the return mode of the current table function.
+
+Solution: Check whether the related code in the executor properly processes the return mode of the table function.
+
+GAUSS-02329: "function returning set of rows cannot return null value"
+
+SQLSTATE: 22004
+
+Description: Dataset returned by the table function contains **NULL**.
+
+Solution: Check whether **NULL** is properly filtered during expression processing.
+
+GAUSS-02330: "rows returned by function are not all of the same row type"
+
+SQLSTATE: 42804
+
+Description: The tuple descriptors returned by the table function are not always the same.
+
+Solution: Ensure the data consistency.
+
+<br/>
+
+## GAUSS-02331 - GAUSS-02340
+
+<br/>
+
+GAUSS-02331: "IS DISTINCT FROM does not support set arguments"
+
+SQLSTATE: 42804
+
+Description: The **IS DISTINCT FROM** SQL statement does not support multiple parameters.
+
+Solution: Check whether the SQL statement is properly used.
+
+GAUSS-02333: "cannot merge incompatible arrays"
+
+SQLSTATE: 42804
+
+Description: Types of the two arrays are different.
+
+Solution: Ensure that types of the two arrays in the SQL statement are same.
+
+GAUSS-02334: "multidimensional arrays must have array expressions with matching dimensions"
+
+SQLSTATE: 2202E
+
+Description: Multi-dimensional arrays must be provided with dimension-matching expressions.
+
+Solution: Check the input strings.
+
+GAUSS-02335: "unrecognized RowCompareType: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02337: "NULLIF does not support set arguments"
+
+SQLSTATE: 42804
+
+Description: The **NULLIF** operator does not support returning parameters as a set.
+
+Solution: Ensure that the parameters returned to the **NULLIF** function in the SQL statement are not a set.
+
+GAUSS-02338: "domain %s does not allow null values"
+
+SQLSTATE: 23502
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02339: "value for domain %s violates check constraint '%s'"
+
+SQLSTATE: 23514
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02340: "unsupported reference to system column %d in FieldSelect"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02341 - GAUSS-02350
+
+<br/>
+
+GAUSS-02341: "CURRENT OF cannot be executed"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02342: "unrecognized paramkind: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02343: "Aggref found in non-Agg plan node"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02344: "WindowFunc found in non-WindowAgg plan node"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02345: "SubPlan found with no parent plan"
+
+SQLSTATE: 42P27
+
+Description: The **AlternativeSubPlan** expression does not have a parent node whose **PlanState** is empty.
+
+Solution: Check whether the parent node is empty in the SQL statement or execution plan.
+
+GAUSS-02346: "AlternativeSubPlan found with no parent plan"
+
+SQLSTATE: 42P27
+
+Description: The **SubPlan** expression does not have a parent node whose **PlanState** is empty.
+
+Solution: Check whether the parent node is empty in the SQL statement or execution plan.
+
+GAUSS-02347: "target type is not an array"
+
+SQLSTATE: 22023
+
+Description: Array is not the target type of an array-type conversion expression.
+
+Solution: Ensure that array is the source and target types of an array-type conversion expression.
+
+GAUSS-02348: "ROW() column has type %s instead of type %s"
+
+SQLSTATE: 42804
+
+Description: The row expression type does not match.
+
+Solution: Check whether the type is modified by the alter column type operation.
+
+GAUSS-02349: "could not identify a comparison function for type %s"
+
+SQLSTATE: 42883
+
+Description: Failed to define the type comparison functions in the **MIN** and **MAX** expressions.
+
+Solution: Ensure that the **MIN** and **MAX** expressions are properly used.
+
+GAUSS-02350: "CTE subplans should not be executed via ExecSubPlan"
+
+SQLSTATE: XX000
+
+Description: Generated plan error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02351 - GAUSS-02360
+
+<br/>
+
+GAUSS-02351: "cannot set parent params from subquery"
+
+SQLSTATE: XX000
+
+Description: Generated plan error.
+
+Solution:Contact technical support.
+
+GAUSS-02352: "hashed subplan with direct correlation not supported"
+
+SQLSTATE: XX000
+
+Description: The generated plan is incorrect. The hashed subplan does not support correlated subqueries.
+
+Solution: Optimizer error. Contact technical support.
+
+GAUSS-02353: "more than one row returned by a subquery used as an expression"
+
+SQLSTATE: 21000
+
+Description: A redundant row of data is returned by the subquery.
+
+Solution: Check the subquery conditions to ensure that only one row of data is returned.
+
+GAUSS-02354: "unrecognized testexpr type: %d"
+
+SQLSTATE: XX000
+
+Description: Failed to recognize the expression type.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02355: "ANY/ALL subselect unsupported as initplan"
+
+SQLSTATE: XX000
+
+Description: Failed to use the **ANY** or **ALL** as initplan in a subquery.
+
+Solution: Check the query statement. Do not use **ANY** or **ALL** for non-correlated subqueries.
+
+GAUSS-02356: "CTE subplans should not be executed via ExecSetParamPlan"
+
+SQLSTATE: XX000
+
+Description: The CTE cannot be used as the query for non-correlated subqueries.
+
+Solution: Check the query statement. Do not use the CTE for non-correlated subqueries.
+
+GAUSS-02357: "direct correlated subquery unsupported as initplan"
+
+SQLSTATE: XX000
+
+Description: Correlated subqueries cannot be used as InitPlans.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02358: "setParam list of initplan is empty"
+
+SQLSTATE: XX000
+
+Description: The parameter list of correlated subqueries is empty.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02359: "extParam set of initplan is empty"
+
+SQLSTATE: XX000
+
+Description: The parameter list of InitPlans is empty.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02360: "Unrecognized parttype as '%c' for relation '%s'"
+
+SQLSTATE: XX000
+
+Description: An incorrect partition type is detected and the internal protection mechanism is triggered.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02361 - GAUSS-02370
+
+<br/>
+
+GAUSS-02361: "partition table delete conflict"
+
+SQLSTATE: 40000
+
+Description: The partitioned table is concurrently deleted.
+
+Solution: Do not perform concurrent operations.
+
+GAUSS-02362: "unrecognized heap_delete status: %u"
+
+SQLSTATE: XX000
+
+Description: The value returned after a tuple is deleted is not within the expected range. The tuple may be invisible.
+
+Solution: Perform the delete operation again.
+
+GAUSS-02363: "failed to fetch deleted tuple for DELETE RETURNING"
+
+SQLSTATE: XX000
+
+Description: Failed to obtain the deleted tuple using **DELETE RETURNING**.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02364: "cannot UPDATE during bootstrap"
+
+SQLSTATE: XX000
+
+Description: Failed to perform the update operation during initialization.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02365: "unrecognized heap_update status: %u"
+
+SQLSTATE: XX000
+
+Description: The value returned after a tuple is updated is not within the expected range. The tuple may be invisible.
+
+Solution: Perform the delete operation again.
+
+GAUSS-02366: "fail to update partitioned table '%s'"
+
+SQLSTATE: XX000
+
+Description:
+
+1. **DISABLE ROW MOVEMENT** is specified when the partitioned table is created.
+2. The data update exceeds the partition range.
+
+Solution:
+
+1. Change **DISABLE ROW MOVEMENT** to **ENABLE ROW MOVEMENT** for the table. For example:
+
+   ```sql
+   ALTER TABLE table_name ENABLE ROW MOVEMENT
+   ```
+
+2. Change the partition range.
+
+GAUSS-02367: "partition table update conflict"
+
+SQLSTATE: 40000
+
+Description: Failed to concurrently update the partitioned table.
+
+Solution: Specify **DISABLE ROW MOVEMENT** while creating the table.
+
+GAUSS-02368: "unrecognized heap_update status: %u"
+
+SQLSTATE: XX000
+
+Description: The value returned after a tuple is updated is not within the expected range. The tuple may be invisible.
+
+Solution: Perform the delete operation again.
+
+GAUSS-02369: "unknown operation"
+
+SQLSTATE: XX000
+
+Description: Failed to recognize the operation type.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02370: "ModifyTable should not be called during EvalPlanQual"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution: Internal system error. Contact technical support.
+
+<br/>
+
+## GAUSS-02371 - GAUSS-02380
+
+<br/>
+
+GAUSS-02372: "tableoid is null when update partitioned table"
+
+SQLSTATE: XX000
+
+Description: The obtained **junk** column is **NULL**.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02374: "could not find junk ctid column"
+
+SQLSTATE: XX000
+
+Description: Failed to find the **junk** column.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02375: "could not find junk tableoid column"
+
+SQLSTATE: XX000
+
+Description: Failed to find the **junk** column.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02376: "could not find junk wholerow column"
+
+SQLSTATE: XX000
+
+Description: Failed to find the **junk** column.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02377: "ExecReScanModifyTable is not implemented"
+
+SQLSTATE: XX000
+
+Description: Failed to implement the rescan function of **MODIFY TABLE**.
+
+Solution: Plan error. Contact technical support.
+
+GAUSS-02378: "expected valid OLD tuple for triggers"
+
+SQLSTATE: XX000
+
+Description: An internal trigger error occurs.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02380: "indexqual doesn't have key on left side"
+
+SQLSTATE: XX002
+
+Description: The left operand of the index expression is not a variable where an index has been created.
+
+Solution: Check whether indexes have been created for related columns in the system catalog.
+
+<br/>
+
+## GAUSS-02381 - GAUSS-02390
+
+<br/>
+
+GAUSS-02381: "bogus index qualification"
+
+SQLSTATE: XX002
+
+Description: The attribute number of the left operand for the index expression is greater than the number of attributes for which indexes have been created.
+
+Solution: Check the system catalog and execution plan.
+
+GAUSS-02384: "NullTest indexqual has wrong key"
+
+SQLSTATE: XX002
+
+Description: The left operand of the index expression is not a variable where an index has been created.
+
+Solution: Check whether indexes have been created for related columns in the system catalog.
+
+GAUSS-02387: "unrecognized operation code: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02388: "whole-row update is not implemented"
+
+SQLSTATE: XX000
+
+Description: Failed to update an entire column.
+
+Solution: Check the SQL statement.
+
+GAUSS-02390: "cannot change sequence '%s'"
+
+SQLSTATE: 42809
+
+Description: The object type is incorrect. Failed to modify the sequence by using the **INSERT**, **UPDATE**, or **DELETE** statement.
+
+Solution: Modify the SQL statement.
+
+<br/>
+
+## GAUSS-02391 - GAUSS-02400
+
+<br/>
+
+GAUSS-02391: "cannot change TOAST relation '%s'"
+
+SQLSTATE: 42809
+
+Description: The object type is incorrect. Failed to modify the TOAST table by using the **INSERT**, **UPDATE**, or **DELETE** statement.
+
+Solution: Modify the SQL statement.
+
+GAUSS-02392: "cannot insert into foreign table '%s'"
+
+SQLSTATE: 0A000
+
+Description: Failed to perform the insert operation for foreign tables.
+
+Solution: Do not perform the insert operation for foreign tables.
+
+GAUSS-02393: "foreign table '%s' does not allow inserts"
+
+SQLSTATE: 55000
+
+Description: Failed to perform the insert operation for foreign tables.
+
+Solution: Do not perform the insert operation for foreign tables.
+
+GAUSS-02394: "cannot update foreign table '%s'"
+
+SQLSTATE: 0A000
+
+Description: Failed to perform the update operation for foreign tables.
+
+Solution: Do not perform the update operation for foreign tables.
+
+GAUSS-02395: "foreign table '%s' does not allow updates"
+
+SQLSTATE: 55000
+
+Description: Failed to perform the update operation for foreign tables.
+
+Solution: Do not perform the update operation for foreign tables.
+
+GAUSS-02396: "cannot delete from foreign table '%s'"
+
+SQLSTATE: 0A000
+
+Description: Failed to perform the delete operation for foreign tables.
+
+Solution: Do not perform the delete operation for foreign tables.
+
+GAUSS-02397: "foreign table '%s' does not allow deletes"
+
+SQLSTATE: 55000
+
+Description: Failed to perform the delete operation for foreign tables.
+
+Solution: Do not perform the delete operation for foreign tables.
+
+GAUSS-02398: "cannot change relation '%s'"
+
+SQLSTATE: 42809
+
+Description: The object type is incorrect. Failed to modify the object type by using the **INSERT**, **UPDATE**, or **DELETE** statement.
+
+Solution: Modify the SQL statement.
+
+GAUSS-02399: "cannot lock rows in sequence '%s'"
+
+SQLSTATE: 42809
+
+Description: The object type is incorrect. Sequence cannot be locked.
+
+Solution: Modify the SQL statement.
+
+GAUSS-02400: "cannot lock rows in TOAST relation '%s'"
+
+SQLSTATE: 42809
+
+Description: The object type is incorrect. Failed to lock the TOAST table.
+
+Solution: Modify the SQL statement.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/25-GAUSS-02401-GAUSS-02500.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/25-GAUSS-02401-GAUSS-02500.md
new file mode 100644
index 0000000000000000000000000000000000000000..743a8e8ea50969bccd1c8039b111ef00cbfa9f00
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/25-GAUSS-02401-GAUSS-02500.md
@@ -0,0 +1,708 @@
+---
+title: GAUSS-02401 - GAUSS-02500
+summary: GAUSS-02401 - GAUSS-02500
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-02401 - GAUSS-02500
+
+<br/>
+
+## GAUSS-02401 - GAUSS-02410
+
+<br/>
+
+GAUSS-02401: "cannot lock rows in view '%s'"
+
+SQLSTATE: 42809
+
+Description: The object type is incorrect. Failed to lock the view.
+
+Solution: Modify the SQL statement.
+
+GAUSS-02402: "cannot lock rows in foreign table '%s'"
+
+SQLSTATE: 42809
+
+Description: The object type is incorrect. Failed to lock the foreign table.
+
+Solution: Modify the SQL statement.
+
+GAUSS-02403: "cannot lock rows in relation '%s'"
+
+SQLSTATE: 42809
+
+Description: The object type is incorrect. Failed to lock the object.
+
+Solution: Modify the SQL statement.
+
+GAUSS-02404: "new row for relation '%s' violates check constraint '%s'"
+
+SQLSTATE: 23514
+
+Description: The new data conflicts with **CHECK** constraints.
+
+Solution: Check whether the data conflicts with **CHECK** constraints.
+
+GAUSS-02405: "failed to find ExecRowMark for rangetable index %u"
+
+SQLSTATE: XX000
+
+Description: Failed to find **ExecRowMark** in **Rangetable** using the index.
+
+Solution: Check the SQL statement and execution plan.
+
+GAUSS-02407: "t_xmin is uncommitted in tuple to be updated"
+
+SQLSTATE: XX000
+
+Description: Failed to commit the tuple **xmin** to be updated.
+
+Solution:Contact technical support.
+
+GAUSS-02408: "abort transaction due to concurrent update"
+
+SQLSTATE: 40001
+
+Description: The transaction rolls back because concurrent updates of the same tuple are not allowed.
+
+Solution: Do not perform concurrent updates to transactions.
+
+GAUSS-02409: "EvalPlanQual doesn't support locking rowmarks"
+
+SQLSTATE: XX000
+
+Description: Failed to lock the related table when checking whether the updated tuples can be operated in **READ COMMITTED**.
+
+Solution:Contact technical support.
+
+GAUSS-02410: "failed to fetch tuple for EvalPlanQual recheck"
+
+SQLSTATE: 22P08
+
+Description: Failed to obtain the rule when the updated tuple is rechecked.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02411 - GAUSS-02420
+
+<br/>
+
+GAUSS-02411: "failed to fetch tuple for EvalPlanQual recheck"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02412: "found self tuple multiple times in index '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02416: "unrecognized hashjoin state: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02417: "could not rewind hash-join temporary file: %m"
+
+SQLSTATE: XX000
+
+Description: Failed to spill the temporary file to disks.
+
+Solution: Analyze the fault based on the error information.
+
+GAUSS-02419: "could not read from hash-join temporary file: %m"
+
+SQLSTATE: XX000
+
+Description: Failed to spill the temporary file to disks.
+
+Solution: Analyze the fault based on the error information.
+
+GAUSS-02420: "Result nodes do not support mark/restore"
+
+SQLSTATE: XX000
+
+Description: The result operator does not support the mark or restore operation.
+
+Solution: Plan error. Contact technical support.
+
+<br/>
+
+## GAUSS-02421 - GAUSS-02430
+
+<br/>
+
+GAUSS-02421: "Hash node does not support ExecProcNode call convention"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02422: "BitmapAnd doesn't support zero inputs"
+
+SQLSTATE: XX000
+
+Description: Internal system error. The input of the **BitmapAnd** operator is **NULL**.
+
+Solution:Contact technical support.
+
+GAUSS-02424: "ExecLockRows:target relation cannot be NULL"
+
+SQLSTATE: 40001
+
+Description: The input of the **BitmapAnd** operator is **NULL**.
+
+Solution:Contact technical support.
+
+GAUSS-02428: "aggregate function %u called as normal function"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02431 - GAUSS-02440
+
+<br/>
+
+GAUSS-02434: "latch already owned"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02435: "cannot wait on a latch owned by another process"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02436: "failed to create event for socket: error code %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02437: "failed to set up event for socket: error code %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02439: "WaitForMultipleObjects() failed: error code %lu"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02440: "failed to enumerate network events: error code %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02441 - GAUSS-02450
+
+<br/>
+
+GAUSS-02441: "unexpected return code from WaitForMultipleObjects(): %lu"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02442: "pipe() failed: %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02443: "fcntl() failed on read-end of self-pipe: %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02444: "fcntl() failed on write-end of self-pipe: %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02445: "poll() failed: %m"
+
+SQLSTATE: XX000
+
+Description: The system fails to call the **poll** function.
+
+Solution: Internal database error. Record the system error information. Contact technical support.
+
+GAUSS-02446: "read() on self-pipe failed: %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02447: "unexpected EOF on self-pipe"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02448: "sem_open('%s') failed: %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02449: "sem_init failed: %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02450: "too many semaphores created"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02451 - GAUSS-02460
+
+<br/>
+
+GAUSS-02451: "sem_trywait failed: %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02452: "sem_wait failed: %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02453: "sem_post failed: %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02454: "could not get size for full pathname of datadir %s: error code %lu"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02455: "could not allocate memory for shared memory name"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02456: "could not generate full pathname for datadir %s: error code %lu"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02457: "could not create shared memory segment: error code %lu"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02458: "pre-existing shared memory block is still in use"
+
+SQLSTATE: XX000
+
+Description: The **Win32** system is not involved.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02461 - GAUSS-02470
+
+<br/>
+
+GAUSS-02461: "reattaching to shared memory returned unexpected address (got %p, expected %p)"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02462: "reattaching to shared memory returned non-PostgreSQL memory"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02463: "could not create signal listener pipe for PID %d: error code %lu"
+
+SQLSTATE: XX000
+
+Description: The **Win32** system is not involved.
+
+Solution:Contact technical support.
+
+GAUSS-02464: "could not create semaphores: %m"
+
+SQLSTATE: XX000
+
+Description: The number of created semaphores exceeds the system limit.
+
+Solution: Adjust the system kernel parameter **/proc/sys/kernel/sem** so that more semaphores can be created. Alternatively, set **max_connections** of the database to a smaller value.
+
+GAUSS-02465: "semop(id=%d) failed: %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02466: "could not create shared memory segment: %m"
+
+SQLSTATE: XX000
+
+Description: The size of the shared memory exceeds the upper limit.
+
+Solution: Adjust the system shared memory parameters **SHMMAX**, and **SHMMIN**. Alternatively, set the **shared_buffers** of the database to a smaller value.
+
+GAUSS-02467: "shmat(id=%d) failed: %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02468: "could not stat data directory '%s': %m"
+
+SQLSTATE: XX000
+
+Description: The data directory does not exist or you do not have the permission.
+
+Solution: Check whether the data directory exists or whether you have the permission to perform the operation.
+
+GAUSS-02470: "could not create semaphore: error code %d"
+
+SQLSTATE: XX000
+
+Description: The **Win32** system is not involved.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02471 - GAUSS-02480
+
+<br/>
+
+GAUSS-02471: "could not lock semaphore: error code %d"
+
+SQLSTATE: XX000
+
+Description: The **Win32** system is not involved.
+
+Solution:Contact technical support.
+
+GAUSS-02472: "could not unlock semaphore: error code %d"
+
+SQLSTATE: XX000
+
+Description: The **Win32** system is not involved.
+
+Solution:Contact technical support.
+
+GAUSS-02473: "could not try-lock semaphore: error code %d"
+
+SQLSTATE: XX000
+
+Description: The **Win32** system is not involved.
+
+Solution:Contact technical support.
+
+GAUSS-02474: "dynamic load not supported"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02475: "out of on_shmem_exit slots"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02476: "too late to call tuplestore_set_eflags"
+
+SQLSTATE: 23514
+
+Description: Internal system error. **tuplestore_set_eflags** is called too late.
+
+Solution: Contact technical support.
+
+GAUSS-02477: "too late to require new tuplestore eflags"
+
+SQLSTATE: 23514
+
+Description: Internal system error. The new tuplestore flag is set too late.
+
+Solution: Contact technical support.
+
+GAUSS-02478: "tuplestore seek failed"
+
+SQLSTATE: 22P07
+
+Description: Internal system error. Failed to find the tuple data of the required location.
+
+Solution: Contact technical support.
+
+GAUSS-02479: "invalid tuplestore state"
+
+SQLSTATE: XX006
+
+Description: Internal system error. The tuplestor status is incorrect.
+
+Solution: Contact technical support.
+
+<br/>
+
+## GAUSS-02481 - GAUSS-02490
+
+<br/>
+
+GAUSS-02481: "tuplestore seek to EOF failed"
+
+SQLSTATE: 22P07
+
+Description: Internal system error. Failed to find the terminator when data is read from the file.
+
+Solution: Contact technical support.
+
+GAUSS-02482: "bogus tuple length in backward scan"
+
+SQLSTATE: 22P07
+
+Description:NA
+
+Solution:NA
+
+GAUSS-02483: "tuplestore seek to start failed"
+
+SQLSTATE: 22P07
+
+Description: Internal system error. Failed to find the start flag during data reading.
+
+Solution: Contact technical support.
+
+GAUSS-02484: "unexpected end of tape"
+
+SQLSTATE: 22000
+
+Description: Internal system error. An unexpected end exists when data is read from the logical tape.
+
+Solution: Contact technical support.
+
+GAUSS-02485: "unexpected end of data"
+
+SQLSTATE: 22P07
+
+Description: Internal system error. An unexpected end exists when data is read from the logical tape.
+
+Solution: Contact technical support.
+
+GAUSS-02487: "too late to call batchstore_set_eflags"
+
+SQLSTATE: XX006
+
+Description: Internal system error. **batchstore_set_eflags** is called too late.
+
+Solution: Contact technical support.
+
+GAUSS-02488: "too late to require new batchstore eflags"
+
+SQLSTATE: XX006
+
+Description: Internal system error. The new batchstore flag is set too late.
+
+Solution: Contact technical support.
+
+GAUSS-02489: "batchstore seek failed"
+
+SQLSTATE: 22P07
+
+Description: Internal system error. Failed to find the data of the required location.
+
+Solution: Contact technical support.
+
+GAUSS-02490: "invalid batchstore state"
+
+SQLSTATE: XX006
+
+Description: Internal system error. The batchstore status is invalid.
+
+Solution: Contact technical support.
+
+<br/>
+
+## GAUSS-02491 - GAUSS-02500
+
+<br/>
+
+GAUSS-02491: "batchstore seek to EOF failed"
+
+SQLSTATE: 22P07
+
+Description: Internal system error. Failed to find the terminator when data is read from the file.
+
+Solution: Contact technical support.
+
+GAUSS-02492: "batchstore seek to start failed"
+
+SQLSTATE: 22P07
+
+Description: Internal system error. Failed to find the start flag during data reading.
+
+Solution: Contact technical support.
+
+GAUSS-02493: "could not write block %ld of temporary file: %m"
+
+SQLSTATE: XX000
+
+Description: An error occurs when the system writes the temporary file.
+
+Solution: Check whether the disk has free space. If yes, an internal error occurs. Contact technical support.
+
+GAUSS-02494: "could not read block %ld of temporary file: %m"
+
+SQLSTATE: XX000
+
+Description: Internal system error. Failed to read the data block from the temporary file.
+
+Solution: Contact technical support.
+
+GAUSS-02495: "invalid logtape state: should be dirty"
+
+SQLSTATE: 22000
+
+Description: Internal system error. The logtape status is invalid.
+
+Solution: Contact technical support.
+
+GAUSS-02496: "function %u returned NULL"
+
+SQLSTATE: XX005
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02497: "insufficient memory allowed for sort"
+
+SQLSTATE: 53000
+
+Description: The memory is insufficient during sorting.
+
+Solution: Increase the value of **work_mem**.
+
+GAUSS-02498: "invalid tuplesort state"
+
+SQLSTATE: XX006
+
+Description: Internal system error. The row-store sorting status is invalid.
+
+Solution: Contact technical support.
+
+GAUSS-02499: "retrieved too many tuples in a bounded sort"
+
+SQLSTATE: 23001
+
+Description: Internal system error. During the sorting, an unexpected terminator is found. As a result, data is insufficient during bounded sorting.
+
+Solution: Contact technical support.
+
+GAUSS-02500: "tuplesort_restorepos failed"
+
+SQLSTATE: 22P07
+
+Description: Internal system error. Failed to measure the current location again during **MergeJoin**.
+
+Solution: Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/26-GAUSS-02501-GAUSS-02600.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/26-GAUSS-02501-GAUSS-02600.md
new file mode 100644
index 0000000000000000000000000000000000000000..b55bfaf59678be79260da86b7cf08034b4ae767c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/26-GAUSS-02501-GAUSS-02600.md
@@ -0,0 +1,772 @@
+---
+title: GAUSS-02501 - GAUSS-02600
+summary: GAUSS-02501 - GAUSS-02600
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-02501 - GAUSS-02600
+
+<br/>
+
+## GAUSS-02501 - GAUSS-02510
+
+<br/>
+
+GAUSS-02501: "could not create unique index '%s'"
+
+SQLSTATE: 23505
+
+Description: Internal system error. Failed to create a unique index.
+
+Solution: Contact technical support.
+
+GAUSS-02502: "reversedirection_index_hash is not implemented"
+
+SQLSTATE: 0A000
+
+Description: Internal system error. Failed to implement the function.
+
+Solution: Contact technical support.
+
+GAUSS-02503: "copytup_datum() should not be called"
+
+SQLSTATE: 0A000
+
+Description: Internal system error. Failed to call the function because it is not implemented.
+
+Solution: Contact technical support.
+
+GAUSS-02504: "Failed to fetch from data node cursor"
+
+SQLSTATE: 22P08
+
+Description: Internal system error. Failed to obtain data from the DN cursor.
+
+Solution: Contact technical support.
+
+GAUSS-02505: "Node id %d is incorrect"
+
+SQLSTATE: XX006
+
+Description: Internal system error. The obtained node ID is incorrect.
+
+Solution: Contact technical support.
+
+GAUSS-02506: "%s"
+
+SQLSTATE: XX000
+
+Description: Syntax error.
+
+Solution: Ensure that the SQL statement syntax is correct.
+
+GAUSS-02507: "Unexpected response from the data nodes"
+
+SQLSTATE: XX006
+
+Description: Internal system error. An unexpected response comes from the DN.
+
+Solution: Contact technical support.
+
+GAUSS-02508: "invalid BatchSort state"
+
+SQLSTATE: XX006
+
+Description: Internal system error. The column-store sorting status is invalid.
+
+Solution: Contact technical support.
+
+GAUSS-02509: "invalid batchsort state"
+
+SQLSTATE: XX006
+
+Description: Internal system error. The column-store sorting status is invalid.
+
+Solution: Contact technical support.
+
+GAUSS-02510: "batchsort_restorepos failed"
+
+SQLSTATE: D0011
+
+Description: Internal system error. The storage information is incorrect during column-store sorting.
+
+Solution: Contact technical support.
+
+<br/>
+
+## GAUSS-02511 - GAUSS-02520
+
+<br/>
+
+GAUSS-02511: "failed to initialize hash table '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02512: "cannot insert into frozen hashtable '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02513: "out of shared memory"
+
+SQLSTATE: 53200
+
+Description: The shared memory is insufficient.
+
+Solution: Increase the value of the **max_locks_per_transaction** parameter or release the required memory.
+
+GAUSS-02514: "unrecognized hash action code: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02515: "cannot freeze shared hashtable '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02516: "cannot freeze hashtable '%s' because it has active scans"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02517: "hash table '%s' corrupted"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02518: "too many active hash_seq_search scans, cannot start one on '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02519: "no hash_seq_search scan for hash table '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02520: "could not change directory to '%s': %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02521 - GAUSS-02530
+
+<br/>
+
+GAUSS-02521: "could not get current working directory: %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02522: "cannot set parameter '%s' within security-restricted operation"
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02524: "role '%s' is not permitted to login"
+
+SQLSTATE: 28000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02525: "too many connections for role '%s'"
+
+SQLSTATE: 53300
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02526: "permission denied to set session authorization"
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02527: "invalid role OID: %u"
+
+SQLSTATE: 42704
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02528: "could not create lock file '%s': %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02529: "could not open lock file '%s': %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02530: "could not read lock file '%s': %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02531 - GAUSS-02540
+
+<br/>
+
+GAUSS-02532: "lock file '%s' already exists"
+
+SQLSTATE: F0001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02533: "pre-existing shared memory block (key %lu, ID %lu) is still in use"
+
+SQLSTATE: F0001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02534: "could not remove old lock file '%s': %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02535: "could not write lock file '%s': %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02536: "'%s' is not a valid data directory"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02537: "database files are incompatible with server"
+
+SQLSTATE: 22023
+
+Description: Database files are incompatible with the software version.
+
+Solution: Use the correct software version to rebuild the database.
+
+GAUSS-02538: "could not set timer for authorization timeout"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02539: "could not disable timer for authorization timeout"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02540: "database '%s' has disappeared from pg_database"
+
+SQLSTATE: 3D000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02541 - GAUSS-02550
+
+<br/>
+
+GAUSS-02541: "database '%s' is not currently accepting connections"
+
+SQLSTATE: 55000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02542: "permission denied for database '%s'"
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02543: "too many connections for database '%s'"
+
+SQLSTATE: 53300
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02544: "database locale is incompatible with operating system"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02545: "bad backend ID: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02546: "new replication connections are not allowed during database shutdown"
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02547: "must be system admin to connect during database shutdown"
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02548: "must be system admin to connect in binary upgrade mode"
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02551 - GAUSS-02560
+
+<br/>
+
+GAUSS-02551: "database %u does not exist"
+
+SQLSTATE: 3D000
+
+Description: The database does not exist.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02552: "Forbid remote connection with trust method!"
+
+SQLSTATE: 42601
+
+Description: Remotely connecting to the database using the trusted method is not allowed.
+
+Solution: Check the connection security settings.
+
+GAUSS-02554: "not able to set up signal action handler"
+
+SQLSTATE: 53000
+
+Description: Failed to create a signal processing function for a thread.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02555: "failed to create timer for thread"
+
+SQLSTATE: XX000
+
+Description: Failed to create a timer for a thread.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02556: "could not find function '%s' in file '%s'"
+
+SQLSTATE: 42883
+
+Description: Failed to find the function definition.
+
+Solution: Ensure that the function is properly defined in the statement.
+
+GAUSS-02557: "could not load library '%s': %s"
+
+SQLSTATE: XX000
+
+Description: Failed to load the library.
+
+Solution: Check the library based on the prompted error information and troubleshoot the fault.
+
+GAUSS-02558: "incompatible library '%s': missing magic block"
+
+SQLSTATE: XX000
+
+Description: The library is incompatible because the magic numbers are missing.
+
+Solution: Check whether the library file is damaged.
+
+GAUSS-02559: "incompatible library '%s': version mismatch"
+
+SQLSTATE: XX000
+
+Description: The library version is incompatible.
+
+Solution: Ensure that the library file uses a compatible version.
+
+GAUSS-02560: "incompatible library '%s': magic block mismatch"
+
+SQLSTATE: XX000
+
+Description: The library is incompatible because the magic numbers do not match.
+
+Solution: Ensure that the library file uses a compatible version.
+
+<br/>
+
+## GAUSS-02561 - GAUSS-02570
+
+<br/>
+
+GAUSS-02563: "invalid macro name in dynamic library path: %s"
+
+SQLSTATE: 42602
+
+Description: The dynamic library address contains invalid path macros.
+
+Solution: Check whether the path macro in the dynamic library address is valid.
+
+GAUSS-02564: "zero-length component in parameter 'dynamic_library_path'"
+
+SQLSTATE: 42602
+
+Description: The length of the dynamic library address is 0, which is invalid.
+
+Solution: Check the dynamic library path.
+
+GAUSS-02565: "component in parameter 'dynamic_library_path' is not an absolute path"
+
+SQLSTATE: 42602
+
+Description: The dynamic library address is not an absolute path.
+
+Solution: Check the dynamic library path.
+
+GAUSS-02566: "init_MultiFuncCall cannot be called more than once"
+
+SQLSTATE: 2F000
+
+Description: Failed to call the **init_MultiFuncCall** function for multiple times.
+
+Solution: Check the calling logic.
+
+GAUSS-02567: "could not determine actual result type for function '%s' declared to return type %s"
+
+SQLSTATE: 42804
+
+Description: Failed to determine the return type of the function.
+
+Solution: Check the return type of the function.
+
+GAUSS-02568: "proallargtypes is not a 1-D Oid array"
+
+SQLSTATE: XX000
+
+Description: The function parameter is invalid.
+
+Solution: Check the input parameter.
+
+GAUSS-02569: "proargnames must have the same number of elements as the function has arguments"
+
+SQLSTATE: 22023
+
+Description: An internal system error occurs. The number of function parameters does not match **proargnames**.
+
+Solution: Check the input parameter.
+
+<br/>
+
+## GAUSS-02571 - GAUSS-02580
+
+<br/>
+
+GAUSS-02572: "number of aliases does not match number of columns"
+
+SQLSTATE: 42804
+
+Description: The number of aliases does not match the number of columns.
+
+Solution: Query the number of columns using the **\d+** *tablename* command. Then, check whether the number of aliases of the current statement and that of columns are consistent.
+
+GAUSS-02573: "no column alias was provided"
+
+SQLSTATE: 42804
+
+Description: Column aliases are not provided.
+
+Solution: Provide the column aliases.
+
+GAUSS-02574: "could not determine row description for function returning record"
+
+SQLSTATE: 42804
+
+Description: Failed to determine the **RECORD** type definition of the RECORD return type function.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02575: "internal function '%s' is not in internal lookup table"
+
+SQLSTATE: 42883
+
+Description: Failed to find the function definition in the function lookup table.
+
+Solution: Ensure that the function in the SQL statement is valid.
+
+GAUSS-02576: "unrecognized function API version: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02577: "language %u has old-style handler"
+
+SQLSTATE: 42P13
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02578: "null result from info function '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02579: "unrecognized API version %d reported by info function '%s'"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02580: "fmgr_oldstyle received NULL pointer"
+
+SQLSTATE: XX005
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02581 - GAUSS-02590
+
+<br/>
+
+GAUSS-02581: "function %u has too many arguments (%d, maximum is %d)"
+
+SQLSTATE: 54023
+
+Description: The function has too many input parameters.
+
+Solution: Run the **\df** command to check whether the number of parameters defined by the function is consistent with that in the current query statement. The maximum number of function parameters is 16.
+
+GAUSS-02583: "input function %u returned non-NULL"
+
+SQLSTATE: XX005
+
+Description: After the column data is processed, a null string is returned, which conflicts with the NOT NULL constraint.
+
+Solution: Ensure that the column data is not empty and meets the NOT NULL constraint.
+
+GAUSS-02584: "input function %u returned NULL"
+
+SQLSTATE: XX005
+
+Description: After the column data is processed, a not-null string is returned, which conflicts with the NULL constraint.
+
+Solution: Ensure that the column data is empty and meets the NULL constraint.
+
+GAUSS-02585: "receive function %u returned non-NULL"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02586: "receive function %u returned NULL"
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02587: "could not reopen file '%s' as stderr: %m"
+
+SQLSTATE: XX000
+
+Description: Failed to open the file as the stderr redirection file.
+
+Solution: Check whether files exist.
+
+GAUSS-02588: "could not reopen file '%s' as stdout: %m"
+
+SQLSTATE: XX000
+
+Description: Failed to open the file as the stdout redirection file.
+
+Solution: Check whether files exist.
+
+GAUSS-02590: "buffer %d is not owned by resource owner %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02591 - GAUSS-02600
+
+<br/>
+
+GAUSS-02591: "catcache reference %p is not owned by resource owner %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02592: "catcache list reference %p is not owned by resource owner %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02594: "partcache reference %s is not owned by resource owner %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02595: "fakerel reference %s is not owned by resource owner %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02596: "plancache reference %p is not owned by resource owner %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02597: "tupdesc reference %p is not owned by resource owner %s"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02598: "snapshot reference %p is not owned by resource owner %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02599: "temporery file %d is not owned by resource owner %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02600: "pthread mutex %p is not owned by resource owner %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/27-GAUSS-02601-GAUSS-02700.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/27-GAUSS-02601-GAUSS-02700.md
new file mode 100644
index 0000000000000000000000000000000000000000..1fa0a82b4047f6ee69601a69adf329eebc9f13b2
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/27-GAUSS-02601-GAUSS-02700.md
@@ -0,0 +1,764 @@
+---
+title: GAUSS-02601 - GAUSS-02700
+summary: GAUSS-02601 - GAUSS-02700
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-02601 - GAUSS-02700
+
+<br/>
+
+## GAUSS-02601 - GAUSS-02610
+
+<br/>
+
+GAUSS-02601: "invalid source encoding ID: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02602: "expected source encoding '%s', but got '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02603: "invalid destination encoding ID: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02604: "expected destination encoding '%s', but got '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02605: "encoding conversion length must not be negative"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02606: "invalid byte sequence for encoding '%s': %s"
+
+SQLSTATE: 22021
+
+Description: Failed to recognize the character sequence.
+
+Solution: Ensure that the data contains no unrecognizable character encoding by following the instructions provided in Character Set Support in PostgreSQL Documentation.
+
+GAUSS-02607: "character with byte sequence %s in encoding '%s' has no equivalent in encoding '%s'"
+
+SQLSTATE: 22P05
+
+Description: Failed to find the related character encoding.
+
+Solution: Run the **select \* from pg_conversion** command to view the **conname** column. Ensure that the two types of character encoding can be converted to each other.
+
+GAUSS-02608: "encoding name too long"
+
+SQLSTATE: 42622
+
+Description: The character encoding name is too long.
+
+Solution: Shorten the character encoding name.
+
+GAUSS-02609: "invalid encoding number: %d"
+
+SQLSTATE: 22023
+
+Description: Failed to recognize the local character set.
+
+Solution: Check whether the local character set is supported.
+
+GAUSS-02610: "conversion between %s and %s is not supported"
+
+SQLSTATE: 0A000
+
+Description: These two character encoding sets cannot be converted to each other.
+
+Solution: Ensure that the source and target character sets are compatible.
+
+<br/>
+
+## GAUSS-02611 - GAUSS-02620
+
+<br/>
+
+GAUSS-02611: "out of memory"
+
+SQLSTATE: 54000
+
+Description: Failed to allocate the memory.
+
+Solution: Ensure that the system has sufficient memory.
+
+GAUSS-02612: "invalid source encoding name '%s'"
+
+SQLSTATE: 22023
+
+Description: Failed to recognize the source character encoding set.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02613: "invalid destination encoding name '%s'"
+
+SQLSTATE: 22023
+
+Description: Failed to recognize the target character encoding set.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-02614: "invalid encoding name '%s'"
+
+SQLSTATE: 22023
+
+Description: Failed to recognize the character encoding set.
+
+Solution: Modify the SQL statement.
+
+GAUSS-02615: "invalid byte value for encoding '%s': 0x%02x"
+
+SQLSTATE: 22021
+
+Description: Failed to recognize the character encoding.
+
+Solution: Ensure that the data does not contain unrecognizable characters.
+
+GAUSS-02616: "invalid database encoding: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02617: "unexpected encoding ID %d for WIN character sets"
+
+SQLSTATE: XX000
+
+Description: Failed to recognize the character encoding by using the Windows character set.
+
+Solution: Ensure that the data does not contain unrecognizable characters.
+
+GAUSS-02618: "unexpected encoding ID %d for ISO 8859 character sets"
+
+SQLSTATE: XX000
+
+Description: Failed to recognize the character encoding by using the ISO 8859 character set.
+
+Solution: Ensure that the data does not contain unrecognizable characters.
+
+GAUSS-02619: "duplicate portal name"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02620: "cursor '%s' already exists"
+
+SQLSTATE: 42P03
+
+Description: A duplicate portal exists during the portal creation.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02621 - GAUSS-02630
+
+<br/>
+
+GAUSS-02621: "portal already pinned"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02622: "portal not pinned"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02624: "cannot commit while a portal is pinned"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02625: "cannot PREPARE a transaction that has created a cursor WITH HOLD"
+
+SQLSTATE: 0A000
+
+Description: Failed to prepare a transaction that has created a cursor marked with the **WITH HOLD** keyword.
+
+Solution: Ensure that the SQL script does not contain any cursor marked with the **WITH HOLD** keyword.
+
+GAUSS-02627: "invalid memory alloc request size %lu"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02628: "unrecognized context type"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02629: "could not find block containing chunk %p"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02630: "inserted partition key does not map to any table partition"
+
+SQLSTATE: 22003
+
+Description: The partition key of the inserted tuple does not map to any existing partition.
+
+Solution: Check whether the data inserted is out of the partition range of the partitioned table.
+
+<br/>
+
+## GAUSS-02631 - GAUSS-02640
+
+<br/>
+
+GAUSS-02631: "NULL can not be compared with NULL"
+
+SQLSTATE: 42804
+
+Description: Two null pointers cannot be compared during partition key comparison.
+
+Solution: Check whether the partition column or limit values of the inserted data are **NULL**.
+
+GAUSS-02632: "null maxvalue for tuple %u"
+
+SQLSTATE: XX000
+
+Description: The maximum value of the range partition is **NULL**.
+
+Solution: Check the partitioned table definition.
+
+GAUSS-02633: "partition key column's number is not a 1-D smallint array"
+
+SQLSTATE: XX000
+
+Description: The column ID corresponding to the partition key is not a one-dimensional integer array.
+
+Solution: Check the partitioned table definition and query statements.
+
+GAUSS-02635: "Fail to build partitionmap for partitioned table '%s'"
+
+SQLSTATE: XX000
+
+Description: Failed to create the partition mapping because the partitioned table does not exist.
+
+Solution: Do not create partition mapping for non-partitioned tables.
+
+GAUSS-02636: "Fail to build partitionmap for partitioned table '%u'"
+
+SQLSTATE: XX000
+
+Description: Failed to create the partition mapping because the partition mode of the partitioned table is inconsistent with the specified partition mode.
+
+Solution: Do not create partition mapping for non-partitioned tables.
+
+GAUSS-02637: "rebuild partition map ERROR"
+
+SQLSTATE: XX000
+
+Description: Failed to create the partition. The partition mode of the new table is different from that of the old table.
+
+Solution: Ensure that the partitioning mode of the recreated partitioned table is the same as that of the old table.
+
+GAUSS-02638: "invalid partition sequence: %d of relation '%s'"
+
+SQLSTATE: XX000
+
+Description: Failed to obtain the range of the original partition when the partition is split.
+
+Solution: Check the partitioned table definition.
+
+GAUSS-02640: "CAN NOT get number of partition against NON-PARTITIONED relation"
+
+SQLSTATE: XX000
+
+Description: Obtaining the number of partitions in a non-partitioned table is not allowed.
+
+Solution: Roll back the transaction.
+
+<br/>
+
+## GAUSS-02641 - GAUSS-02650
+
+<br/>
+
+GAUSS-02642: "fail to get partition oid, because range partition index is overflow."
+
+SQLSTATE: XX000
+
+Description: Failed to obtain the partition OID. The partition subscript is out of range.
+
+Solution: Check the partitioned table definition and query statements.
+
+GAUSS-02643: "unsupported partition strategy"
+
+SQLSTATE: XX000
+
+Description: The specified partition method is not supported.
+
+Solution: Check whether the specified partition method is in the supported list. For the supported list, see en-us_topic_0237122117.html.
+
+GAUSS-02644: "fail to get partition strategy"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02645: "failed when making EQUAL expression state for constCompare"
+
+SQLSTATE: XX000
+
+Description: Failed to initialize the expression for constant comparison.
+
+Solution:Contact technical support.
+
+GAUSS-02646: "failed when making GREATE-THAN expression state for constCompare"
+
+SQLSTATE: XX000
+
+Description: Failed to initialize the expression for constant comparison.
+
+Solution:Contact technical support.
+
+GAUSS-02647: "null value can not be compared with null value."
+
+SQLSTATE: XX000
+
+Description: Two **NULL** values cannot be compared during partition key comparison.
+
+Solution: Check whether the partition column or limit values of the inserted data are **NULL**.
+
+GAUSS-02648: "unsupported partitioned strategy"
+
+SQLSTATE: 42P17
+
+Description: The partition method is invalid.
+
+Solution: Check whether the specified partition method is in the supported list. For the supported list, see en-us_topic_0237122117.html.
+
+<br/>
+
+## GAUSS-02651 - GAUSS-02660
+
+<br/>
+
+GAUSS-02651: "cache lookup failed for table partition %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02652: "unrecognized rbtree node state: %d"
+
+SQLSTATE: RB001
+
+Description: Failed to recognize the red-black tree node.
+
+Solution:Contact technical support.
+
+GAUSS-02653: "unrecognized rbtree iteration order: %d"
+
+SQLSTATE: RB002
+
+Description: Failed to recognize the iteration sequence of the red-black tree.
+
+Solution:Contact technical support.
+
+GAUSS-02654: "failed to initialize %s to %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02655: "failed to initialize %s to %g"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02656: "failed to initialize %s to '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02657: "could not find enum option %d for %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02658: "unrecognized configuration parameter '%s'"
+
+SQLSTATE: XX000
+
+Description: Failed to recognize the configuration parameter.
+
+Solution: Check whether invalid configuration parameters exist in the configuration file.
+
+GAUSS-02659: "unrecognized configuration parameter '%s'"
+
+SQLSTATE: 42704
+
+Description: Failed to recognize the configuration parameter.
+
+Solution: Check whether invalid configuration parameters exist in the configuration file.
+
+<br/>
+
+## GAUSS-02661 - GAUSS-02670
+
+<br/>
+
+GAUSS-02661: "SET %s takes only one argument"
+
+SQLSTATE: 22023
+
+Description: Failed to specify multiple parameter values for the current GUC variable.
+
+Solution: Check the **SET** command to ensure that only one parameter value is specified each time.
+
+GAUSS-02663: "unexpected SET TRANSACTION element: %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02664: "unexpected SET SESSION element: %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02665: "SET LOCAL TRANSACTION SNAPSHOT is not implemented"
+
+SQLSTATE: 0A000
+
+Description: The **SET LOCAL TRANSACTION SNAPSHOT** command is not supported.
+
+Solution: Do not use this feature.
+
+GAUSS-02666: "unexpected SET MULTI element: %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02667: "unexpected SET name: %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02668: "role name in the set command is empty."
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02669: "verify set session_authorization and passwd failed."
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02670: "verify set role and passwd failed."
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02671 - GAUSS-02680
+
+<br/>
+
+GAUSS-02671: "SET requires parameter name"
+
+SQLSTATE: 22004
+
+Description: No variable name is specified in the **SET** command.
+
+Solution: Specify a variable name and run the **SET** command again.
+
+GAUSS-02672: "Postgres-XC: ERROR SET query"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02673: "cannot create PGC_POSTMASTER variables after startup"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02674: "attempt to redefine parameter '%s'"
+
+SQLSTATE: XX000
+
+Description: Duplicate user variables exist.
+
+Solution: Delete duplicate variables.
+
+GAUSS-02675: "invalid format of exec config params file"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02676: "could not read from file '%s': %m"
+
+SQLSTATE: XX000
+
+Description: Failed to read the configuration file.
+
+Solution: Check whether the configuration file specified in the error message exists or whether you have the access permission.
+
+GAUSS-02677: "failed to locate variable '%s' in exec config params file"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02678: "permission denied to set parameter '%s'"
+
+SQLSTATE: 42501
+
+Description: You do not have the permission to modify the GUC variable.
+
+Solution: Modify the GUC parameter as the initial user.
+
+GAUSS-02679: "Invalid username/password,set role denied."
+
+SQLSTATE: 42704
+
+Description: The user name or password set in the **SET ROLE** statement is invalid.
+
+Solution:Contact technical support.
+
+GAUSS-02680: "Invalid username/password,set session_authorization denied."
+
+SQLSTATE: 42704
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02681 - GAUSS-02690
+
+<br/>
+
+GAUSS-02684: "md5-password encryption failed"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02686: "Invalid username/password,set role denied."
+
+SQLSTATE: XX000
+
+Description: The user name or password set in the **SET ROLE** statement is invalid.
+
+Solution:Contact technical support.
+
+GAUSS-02687: "Invalid username/password,set session_authorization denied."
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02688: "configuration file '%s' contains errors"
+
+SQLSTATE: F0000
+
+Description: Incorrect configuration items exist in the configuration file.
+
+Solution: Check whether invalid configuration parameters exist in the configuration file.
+
+GAUSS-02689: "could not initialize cache %u (%d)"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02690: "invalid cache ID: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02691 - GAUSS-02700
+
+<br/>
+
+GAUSS-02691: "type %u not supported as catcache key"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02692: "wrong number of hash keys: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02693: "only sys attr supported in caches is OID"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02694: "operator %u is not a member of opfamily %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02695: "operator %u does not exist"
+
+SQLSTATE: XX000
+
+Description: An expression is invalid.
+
+Solution: Check whether the expression in the query is valid. If not, modify the query.
+
+GAUSS-02696: "binary I/O not supported during bootstrap"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02697: "invalid syntax for type: '%s'"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02698: "cache lookup failed for node %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02699: "cache lookup failed for group %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02700: "cache lookup failed on distribution relation %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/28-GAUSS-02701-GAUSS-02800.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/28-GAUSS-02701-GAUSS-02800.md
new file mode 100644
index 0000000000000000000000000000000000000000..0971ecb1b9a153a5321052e1bb1550416f825c4b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/28-GAUSS-02701-GAUSS-02800.md
@@ -0,0 +1,732 @@
+---
+title: GAUSS-02701 - GAUSS-02800
+summary: GAUSS-02701 - GAUSS-02800
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-02701 - GAUSS-02800
+
+<br/>
+
+## GAUSS-02701 - GAUSS-02710
+
+<br/>
+
+GAUSS-02701: "unrecognized distribution option found in source like table"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02703: "cache lookup failed for workload group %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02705: "type %s is only a shell"
+
+SQLSTATE: 42704
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02706: "no input function available for type %s"
+
+SQLSTATE: 42883
+
+Description: An internal error occurs. No input function is available for this data type.
+
+Solution:Contact technical support.
+
+GAUSS-02707: "no output function available for type %s"
+
+SQLSTATE: 42883
+
+Description: An internal error occurs. No output function is available for this data type.
+
+Solution:Contact technical support.
+
+GAUSS-02708: "no binary input function available for type %s"
+
+SQLSTATE: 42883
+
+Description: An internal error occurs. No input function is available for this data type.
+
+Solution:Contact technical support.
+
+GAUSS-02709: "no binary output function available for type %s"
+
+SQLSTATE: 42883
+
+Description: An internal error occurs. No output function is available for this data type.
+
+Solution:Contact technical support.
+
+GAUSS-02710: "stavalues is null"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02711 - GAUSS-02720
+
+<br/>
+
+GAUSS-02711: "stanumbers is null"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02712: "stanumbers is not a 1-D float4 array"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02713: "text search parser %u has no prsstart method"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02714: "text search parser %u has no prstoken method"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02715: "text search parser %u has no prsend method"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02716: "text search dictionary %u has no template"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02717: "text search template %u has no lexize method"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02718: "text search configuration %u has no parser"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02719: "maptokentype value %d is out of range"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02721 - GAUSS-02730
+
+<br/>
+
+GAUSS-02721: "too many pg_ts_config_map entries for one token type"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02722: "text search configuration isn't set"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02723: "cannot read pg_class without having selected a database"
+
+SQLSTATE: 3D000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02724: "could not find relation mapping for partition '%s', OID %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02725: "partition %u deleted while still in use"
+
+SQLSTATE: XX000
+
+Description: Failed to schedule the SQL statement.
+
+Solution: The partition in use cannot be deleted. Modify the scheduling statement.
+
+GAUSS-02726: "partition %u is still open"
+
+SQLSTATE: XX000
+
+Description: Failed to schedule the SQL statement.
+
+Solution: The partition in use cannot be deleted. Modify the scheduling statement.
+
+GAUSS-02727: "could not find pg_partition tuple for index %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02728: "cannot change relation mapping within subtransaction"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02729: "attempt to apply a mapping to unmapped relation %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02730: "ran out of space in relation map"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02731 - GAUSS-02740
+
+<br/>
+
+GAUSS-02731: "could not find temporary mapping for relation %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02732: "cannot PREPARE a transaction that modified relation mapping"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02733: "could not open relation mapping file '%s': %m"
+
+SQLSTATE: XX000
+
+Description: An internal error occurs. Failed to access the relation mapping file.
+
+Solution: Contact technical support. Alternatively, ensure that the data directory is not modified externally.
+
+GAUSS-02735: "relation mapping file '%s' contains invalid data"
+
+SQLSTATE: XX000
+
+Description: An internal error occurs. The relation mapping file contains invalid data.
+
+Solution: Contact technical support. Alternatively, ensure that the data directory is not modified externally.
+
+GAUSS-02736: "relation mapping file '%s' contains incorrect checksum"
+
+SQLSTATE: XX000
+
+Description: An internal error occurs. The relation mapping file contains invalid data.
+
+Solution: Contact technical support. Alternatively, ensure that the data directory is not modified externally.
+
+GAUSS-02738: "could not write to relation mapping file '%s': %m"
+
+SQLSTATE: XX000
+
+Description: An internal error occurs. Failed to access the relation mapping file.
+
+Solution: Contact technical support. Alternatively, ensure that the data directory is not modified externally.
+
+GAUSS-02740: "could not close relation mapping file '%s': %m"
+
+SQLSTATE: XX000
+
+Description: An internal error occurs. Failed to access the relation mapping file.
+
+Solution: Contact technical support. Alternatively, ensure that the data directory is not modified externally.
+
+<br/>
+
+## GAUSS-02741 - GAUSS-02750
+
+<br/>
+
+GAUSS-02742: "relmap_redo: unknown op code %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02743: "cannot read pg_class without having selected a database"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02744: "invalid attribute number %d for %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+AUSS-02746: "relnatts disagrees with indnatts for index %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02747: "bogus pg_index tuple"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02748: "could not find tuple for opclass %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02749: "invalid amproc number %d for opclass %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02750: "could not find pg_class tuple for index %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02751 - GAUSS-02760
+
+<br/>
+
+GAUSS-02751: "relation %u deleted while still in use"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02752: "relation %u is still open"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02753: "shared_relation flag for '%s' does not match IsSharedRelation(%u)"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02754: "invalid relowner in pg_class entry for '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02755: "could not open critical system index %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02756: "unexpected constraint record found for rel %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02758: "null cluster key for rel %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02759: "unexpected exclusion constraint record found for rel %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02760: "null conexclop for rel %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02761 - GAUSS-02770
+
+<br/>
+
+AUSS-02762: "exclusion constraint record missing for rel %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02763: "could not find strategy for operator %u in family %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02764: "could not write init file"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02765: "could not remove cache file '%s': %m"
+
+SQLSTATE: XX000
+
+Description: An internal error occurs. Failed to access the cache file.
+
+Solution: Contact technical support. Alternatively, ensure that the data directory is not modified externally.
+
+GAUSS-02766: "Fail to get index key for index with oid %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02767: "unrecognized SI message ID: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02768: "out of syscache_callback_list slots"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02769: "out of relcache_callback_list slots"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02770: "out of partcache_callback_list slots"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02771 - GAUSS-02780
+
+<br/>
+
+GAUSS-02771: "cannot save one-shot cached plan"
+
+SQLSTATE: XX000
+
+Description:change result type
+
+Solution: Execute the original statement again.
+
+GAUSS-02772: "cached plan must not change result type"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02773: "cannot apply ResourceOwner to non-saved cached plan"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02775: "cannot move a saved cached plan to another context"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02776: "cannot move a one-shot cached plan to another context"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02777: "cannot copy a one-shot cached plan"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02778: "invalid typrelid for composite type %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02779: "cache lookup failed for range type %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02780: "type %s is not composite"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02781 - GAUSS-02790
+
+<br/>
+
+GAUSS-02781: "record type has not been registered"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02782: "enum value %u not found in cache for enum %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02787: "could not import the requested snapshot"
+
+SQLSTATE: 55000
+
+Description: Failed to import the snapshot information for the specified transaction because the transaction has been executed.
+
+Solution: Try again.
+
+GAUSS-02789: "could not create file '%s': %m"
+
+SQLSTATE: XX000
+
+Description: An internal error occurs. Failed to access the file.
+
+Solution: Contact technical support. Alternatively, ensure that the data directory is not modified externally.
+
+GAUSS-02790: "could not write to file '%s': %m"
+
+SQLSTATE: XX000
+
+Description: An internal error occurs. Failed to access the file.
+
+Solution: Contact technical support. Alternatively, ensure that the data directory is not modified externally.
+
+<br/>
+
+## GAUSS-02791 - GAUSS-02800
+
+<br/>
+
+GAUSS-02791: "invalid snapshot data in file '%s'"
+
+SQLSTATE: 22P02
+
+Description: An internal error occurs. Failed to access the file.
+
+Solution: Contact technical support. Alternatively, ensure that the data directory is not modified externally.
+
+GAUSS-02792: "SET TRANSACTION SNAPSHOT must be called before any query"
+
+SQLSTATE: 25001
+
+Description:**SET TRANSACTION SNAPSHOT** must be executed as the first statement.
+
+Solution: Check whether the SQL script contains other statements placed prior to **SET TRANSACTION SNAPSHOT**.
+
+GAUSS-02793: "a snapshot-importing transaction must have isolation level SERIALIZABLE or REPEATABLE READ"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02795: "could not stat file '%s': %m"
+
+SQLSTATE: XX000
+
+Description: Failed to obtain the file status information.
+
+Solution: Check whether the file status is abnormal, for example, the file does not exist or you do not have the file read permission.
+
+GAUSS-02796: "could not read file '%s': %m"
+
+SQLSTATE: XX000
+
+Description: Only database system administrator can read the file.
+
+Solution: Read the file as a system administrator.
+
+GAUSS-02797: "a serializable transaction cannot import a snapshot from a non-serializable transaction"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02798: "a non-read-only serializable transaction cannot import a snapshot from a read-only transaction"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02799: "cannot import a snapshot from a different database"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02800: "unrecognized weight: %d"
+
+SQLSTATE: XX000
+
+Description: Failed to recognize the type of the second parameter in the **tsvector_setweight** function.
+
+Solution: The second parameter only supports the following letters:**A**, **a**, **B**, **b**, **C**, **c**, **D**, **d**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/29-GAUSS-02801-GAUSS-02900.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/29-GAUSS-02801-GAUSS-02900.md
new file mode 100644
index 0000000000000000000000000000000000000000..4fe094c395ae2eb5ec43246d9e78f7ff6b6182d3
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/29-GAUSS-02801-GAUSS-02900.md
@@ -0,0 +1,780 @@
+---
+title: GAUSS-02801 - GAUSS-02900
+summary: GAUSS-02801 - GAUSS-02900
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-02801 - GAUSS-02900
+
+<br/>
+
+## GAUSS-02801 - GAUSS-02810
+
+<br/>
+
+GAUSS-02801: "string is too long for tsvector (%d bytes, max %d bytes)"
+
+SQLSTATE: 54000
+
+Description: The string is too long for the tsvector type.
+
+Solution: Shorten the length of the string to a proper one.
+
+GAUSS-02802: "unrecognized operator: %d"
+
+SQLSTATE: XX000
+
+Description: Failed to recognize the **tsvector** operator.
+
+Solution: Use only !, |, or & as the input operator.
+
+GAUSS-02803: "SPI_prepare('%s') failed"
+
+SQLSTATE: XX000
+
+Description: A **NULL** value is returned after **SPI_prepare** is called.
+
+Solution: Internal error. Contact technical support.
+
+GAUSS-02804: "SPI_cursor_open('%s') failed"
+
+SQLSTATE: XX000
+
+Description: A **NULL** value is returned after **SPI_cursor_open** is called.
+
+Solution: Internal error. Contact technical support.
+
+GAUSS-02806: "tsvector_update_trigger: not fired by trigger manager"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02807: "tsvector_update_trigger: must be fired for row"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02808: "tsvector_update_trigger: must be fired BEFORE event"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02809: "tsvector_update_trigger: must be fired for INSERT or UPDATE"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02810: "tsvector_update_trigger: arguments must be tsvector_field, ts_config, text_field1, …)"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02811 - GAUSS-02820
+
+<br/>
+
+GAUSS-02811: “tsvector column '%s' does not exist”
+
+SQLSTATE: 42703
+
+Description: The selected column does not exist.
+
+Solution: Check whether the selected column exists.
+
+GAUSS-02812: “column '%s' is not of tsvector type”
+
+SQLSTATE: 42804
+
+Description: The column is not of the tsvector type.
+
+Solution: Check whether the column type is tsvector.
+
+GAUSS-02813: “configuration column '%s' does not exist”
+
+SQLSTATE: 42703
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02814: “column '%s' is not of regconfig type”
+
+SQLSTATE: 42804
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02815: “configuration column '%s' must not be null”
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02816: “text search configuration name '%s' must be schema-qualified”
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02817: “column '%s' is not of a character type”
+
+SQLSTATE: 42804
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02818: “tsvector_update_trigger: %d returned by SPI_modifytuple”
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02819: “gtsvector_in not implemented”
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02820: “invalid input syntax for type numeric: '%s'”
+
+SQLSTATE: 22P02
+
+Description: The numeric input is invalid.
+
+Solution: Check whether the data contains invalid numeric input.
+
+<br/>
+
+## GAUSS-02821 - GAUSS-02830
+
+<br/>
+
+GAUSS-02821: "invalid length in external 'numeric' value"
+
+SQLSTATE: 22P03
+
+Description: The numeric input is invalid.
+
+Solution: Check whether the data contains invalid numeric input. For the valid format of the numeric type, see en-us_topic_0237121926.html.
+
+GAUSS-02822: "invalid sign in external 'numeric' value"
+
+SQLSTATE: 22P03
+
+Description: The numeric input is invalid.
+
+Solution: Check whether the data contains invalid numeric input. For the valid format of the numeric type, see en-us_topic_0237121926.html.
+
+GAUSS-02823: "invalid digit in external 'numeric' value"
+
+SQLSTATE: 22P03
+
+Description: The numeric input is invalid.
+
+Solution: Check whether the data contains invalid numeric input. For the valid format of the numeric type, see en-us_topic_0237121926.html.
+
+GAUSS-02824: "NUMERIC precision %d must be between 1 and %d"
+
+SQLSTATE: 22023
+
+Description: The **numeric** precision is beyond the range.
+
+Solution: Modify the input value according to the precision range defined in the error message.
+
+GAUSS-02825: "NUMERIC scale %d must be between 0 and precision %d"
+
+SQLSTATE: 22023
+
+Description: The numeric scale is beyond the range.
+
+Solution: Modify the input value according to the precision range defined in the error message.
+
+GAUSS-02826: "invalid NUMERIC type modifier"
+
+SQLSTATE: 22023
+
+Description: The numeric input is invalid.
+
+Solution: Check whether the data contains invalid numeric input. For the valid format of the numeric type, see en-us_topic_0237121926.html.
+
+GAUSS-02827: "count must be greater than zero"
+
+SQLSTATE: 2201G
+
+Description: The value of parameter **count** of the **width_bucket** function must be greater than zero.
+
+Solution: Ensure that the value of parameter **count** of the **width_bucket** function is greater than zero.
+
+GAUSS-02828: "operand, lower bound, and upper bound cannot be NaN"
+
+SQLSTATE: 2201G
+
+Description: The operand and upper and lower limits for the **width_bucket** function cannot be **NaN**.
+
+Solution: Ensure that operand and upper and lower limits for the **width_bucket** function are not **NaN**.
+
+GAUSS-02829: "lower bound cannot equal upper bound"
+
+SQLSTATE: 2201G
+
+Description: The upper and lower limits of the **width_bucket** function must be different.
+
+Solution: Ensure that the upper and lower limits for the **width_bucket** function are different.
+
+GAUSS-02830: "value overflows numeric format"
+
+SQLSTATE: 22003
+
+Description: The numeric factorial overflows.
+
+Solution: Check whether the data input for the program is too large. If not, take measures to solve the problem at the application layer.
+
+<br/>
+
+## GAUSS-02831 - GAUSS-02840
+
+<br/>
+
+GAUSS-02831: "zero raised to a negative power is undefined"
+
+SQLSTATE: 2201F
+
+Description: Failed to calculate zero raised to the negative power.
+
+Solution: Check whether the data input contains calculations of zero raised to the negative power.
+
+GAUSS-02832: "a negative number raised to a non-integer power yields a complex result"
+
+SQLSTATE: 2201F
+
+Description:Internal system error.
+
+Solution: Contact technical support. Alternatively, check the statement or data.
+
+GAUSS-02833: "cannot convert NaN to integer"
+
+SQLSTATE: 0A000
+
+Description: Failed to convert the numeric NaN to the integer type.
+
+Solution: Do not convert NaN to the integer type.
+
+GAUSS-02834: "integer out of range"
+
+SQLSTATE: 22003
+
+Description: An integer type is out of range.
+
+Solution: Check whether the integer type is out of range in the statement. Alternatively, convert the integer type to the numeric type.
+
+GAUSS-02835: "cannot convert NaN to bigint"
+
+SQLSTATE: 0A000
+
+Description: Failed to convert the numeric NaN to the bigint type.
+
+Solution: Do not convert NaN to the bigint type.
+
+GAUSS-02836: "bigint out of range"
+
+SQLSTATE: 22003
+
+Description: A bigint type is out of range.
+
+Solution: Check whether the bigint type is out of range in the statement. Alternatively, convert the bigint type to the numeric type.
+
+GAUSS-02837: "cannot convert NaN to smallint"
+
+SQLSTATE: 0A000
+
+Description: A conversion error occurs.
+
+Solution: Check the original data.
+
+GAUSS-02838: "smallint out of range"
+
+SQLSTATE: 22003
+
+Description: Data is out of range.
+
+Solution: Contact technical support. Alternatively, check the statement or data.
+
+GAUSS-02839: "cannot convert NaN to tinyint"
+
+SQLSTATE: 0A000
+
+Description: A conversion error occurs.
+
+Solution: Check the original data.
+
+GAUSS-02840: "tinyint out of range"
+
+SQLSTATE: 22003
+
+Description: Data is out of range.
+
+Solution: Check the original data volume.
+
+<br/>
+
+## GAUSS-02841 - GAUSS-02850
+
+<br/>
+
+GAUSS-02841: "expected 3-element numeric array"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02842: "expected 2-element numeric array"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02843: "expected 2-element int8 array"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02844: "numeric field overflow"
+
+SQLSTATE: 22003
+
+Description: Data is out of range.
+
+Solution: Check the original data volume.
+
+GAUSS-02845: "invalid input syntax for type double precision: '%s'"
+
+SQLSTATE: 22P02
+
+Description: The data type is incorrect.
+
+Solution: Contact technical support. Alternatively, check the statement or data.
+
+GAUSS-02846: "division by zero"
+
+SQLSTATE: 22012
+
+Description: The divisor is 0.
+
+Solution: Check the SQL statement. Modify it if its divisor may be zero.
+
+GAUSS-02847: "cannot take square root of a negative number"
+
+SQLSTATE: 2201F
+
+Description: Calculating the square root of a negative number is not allowed.
+
+Solution: Contact technical support. Alternatively, check the statement or data.
+
+GAUSS-02849: "cannot take logarithm of zero"
+
+SQLSTATE: 2201E
+
+Description: The logarithm parameter cannot be set to zero.
+
+Solution: Contact technical support. Alternatively, check the statement or data.
+
+<br/>
+
+## GAUSS-02851 - GAUSS-02860
+
+<br/>
+
+GAUSS-02851: "invalid input syntax for integer: '%s'"
+
+SQLSTATE: 22P02
+
+Description: Incorrect source string.
+
+Solution: Check the data source.
+
+GAUSS-02853: "OID out of range"
+
+SQLSTATE: 22003
+
+Description: Data is out of range.
+
+Solution: Check the metadata.
+
+GAUSS-02854: "step size cannot equal zero"
+
+SQLSTATE: 22023
+
+Description: Incorrect statement.
+
+Solution: Modify the SQL statement. The interval cannot be zero.
+
+GAUSS-02855: "argument of ntile must be greater than zero"
+
+SQLSTATE: 22014
+
+Description: Internal system error. The value of the parameter expression in the obtained frame must be greater than zero.
+
+Solution: Contact technical support.
+
+GAUSS-02856: "argument of nth_value must be greater than zero"
+
+SQLSTATE: 22016
+
+Description: Internal system error. For a frame, its values, excluding its first value, should be greater than zero.
+
+Solution: Contact technical support.
+
+GAUSS-02857: "type %u is not a range type"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02858: "range constructor flags argument must not be NULL"
+
+SQLSTATE: 22000
+
+Description: Incorrect SQL statement.
+
+Solution: Modify the statement.
+
+GAUSS-02859: "range types do not match"
+
+SQLSTATE: 42804
+
+Description: Incorrect SQL statement.
+
+Solution: Modify the statement.
+
+GAUSS-02860: "result of range difference would not be contiguous"
+
+SQLSTATE: 22000
+
+Description: Incorrect SQL statement.
+
+Solution: Modify the statement.
+
+<br/>
+
+## GAUSS-02861 - GAUSS-02870
+
+<br/>
+
+GAUSS-02861: "unexpected case in range_minus"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02862: "result of range union would not be contiguous"
+
+SQLSTATE: 22000
+
+Description: Incorrect SQL statement.
+
+Solution: Modify the statement.
+
+GAUSS-02863: "could not identify a hash function for type %s"
+
+SQLSTATE: 42883
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02864: "range lower bound must be less than or equal to range upper bound"
+
+SQLSTATE: 22000
+
+Description: Incorrect SQL statement.
+
+Solution: Modify the statement.
+
+GAUSS-02865: "invalid range bound flags"
+
+SQLSTATE: 42601
+
+Description: Incorrect syntax.
+
+Solution: Modify the SQL statement.
+
+GAUSS-02866: "malformed range literal: '%s'"
+
+SQLSTATE: 22P02
+
+Description: Incorrect syntax.
+
+Solution: Modify the SQL statement.
+
+GAUSS-02867: "cannot store a toast pointer inside a range"
+
+SQLSTATE: 22000
+
+Description: Incorrect syntax.
+
+Solution: Modify the SQL statement.
+
+GAUSS-02868: "invalid input syntax for type macaddr: '%s'"
+
+SQLSTATE: 22P02
+
+Description: Incorrect syntax.
+
+Solution: Modify the SQL statement.
+
+GAUSS-02869: "invalid octet value in 'macaddr' value: '%s'"
+
+SQLSTATE: 22003
+
+Description: Incorrect syntax.
+
+Solution: Modify the SQL statement.
+
+GAUSS-02870: "unrecognized QueryItem type: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02871 - GAUSS-02880
+
+<br/>
+
+GAUSS-02871: "syntax error in tsquery: '%s'"
+
+SQLSTATE: 42601
+
+Description: The syntax of the tsvector variable is incorrect.
+
+Solution: Correct the syntax that used for the tsvector variable.
+
+GAUSS-02872: "there is no escaped character: '%s'"
+
+SQLSTATE: 42601
+
+Description: In the tsvector variable string, no character follows the escape character.
+
+Solution: Ensure that the escape character is followed by a character to be escaped.
+
+GAUSS-02873: "wrong position info in tsvector: '%s'"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02874: "unrecognized state in gettoken_tsvector: %d"
+
+SQLSTATE: XX000
+
+Description: The status of internal tsvector variable parsing is incorrect.
+
+Solution: Contact technical support. Alternatively, check the syntax of the string.
+
+GAUSS-02875: "identifier too long"
+
+SQLSTATE: 42622
+
+Description: The data is too long.
+
+Solution: Contact technical support. Alternatively, check the statement or data.
+
+GAUSS-02879: "unexpected json parse state: %d"
+
+SQLSTATE: XX004
+
+Description: The syntax is incorrect.
+
+Solution: Modify the SQL statement.
+
+GAUSS-02880: "invalid input syntax for type json"
+
+SQLSTATE: 22P02
+
+Description: The syntax is incorrect.
+
+Solution: Modify the SQL statement.
+
+<br/>
+
+## GAUSS-02881 - GAUSS-02890
+
+<br/>
+
+GAUSS-02881: "invalid type modifier"
+
+SQLSTATE: 22023
+
+Description: Syntax error.
+
+Solution: Modify the SQL statement.
+
+GAUSS-02882: "length for type %s must be at least 1"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02883: "length for type %s cannot exceed %d"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02884: "bit string length %d does not match type bit(%d)"
+
+SQLSTATE: 22026
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02885: "'%c' is not a valid binary digit"
+
+SQLSTATE: 22P02
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02886: "'%c' is not a valid hexadecimal digit"
+
+SQLSTATE: 22P02
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02888: "bit string too long for type bit varying(%d)"
+
+SQLSTATE: 22001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02889: "negative substring length not allowed"
+
+SQLSTATE: 22011
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02891 - GAUSS-02900
+
+<br/>
+
+GAUSS-02893: "bit index %d out of valid range (0..%d)"
+
+SQLSTATE: 2202E
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02894: "new bit must be 0 or 1"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02895: "invalid input syntax for type %s: '%s'"
+
+SQLSTATE: 22P02
+
+Description: The network address is invalid.
+
+Solution: Check whether the format of the entered network address is correct.
+
+GAUSS-02896: "invalid cidr value: '%s'"
+
+SQLSTATE: 22P02
+
+Description: The network address is invalid.
+
+Solution: Check whether the format of the entered network address is correct.
+
+GAUSS-02897: "could not format inet value: %m"
+
+SQLSTATE: 22P03
+
+Description: The network address is invalid.
+
+Solution: Check whether the format of the entered network address is correct.
+
+GAUSS-02898: "invalid address family in external '%s' value"
+
+SQLSTATE: 22P03
+
+Description: The network address family is invalid.
+
+Solution: Check whether the format of the entered network address is correct.
+
+GAUSS-02899: "invalid bits in external '%s' value"
+
+SQLSTATE: 22P03
+
+Description: The network address is invalid.
+
+Solution: Check whether the format of the entered network address is correct.
+
+GAUSS-02900: "invalid length in external '%s' value"
+
+SQLSTATE: 22P03
+
+Description: The network address is invalid.
+
+Solution: Check whether the format of the entered network address is correct.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/3-GAUSS-00201-GAUSS-00300.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/3-GAUSS-00201-GAUSS-00300.md
new file mode 100644
index 0000000000000000000000000000000000000000..2eb85a1818bb1502de2a41da52f34aaa7614081c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/3-GAUSS-00201-GAUSS-00300.md
@@ -0,0 +1,748 @@
+---
+title: GAUSS-00201 - GAUSS-00300
+summary: GAUSS-00201 - GAUSS-00300
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-00201 - GAUSS-00300
+
+<br/>
+
+## GAUSS-00201 - GAUSS-00210
+
+<br/>
+
+GAUSS-00202: "unrecognized join type: %d"
+
+SQLSTATE: XX004
+
+Description: Syntax not supported.
+
+Solution: Modify the SQL statement.
+
+GAUSS-00203: "unrecognized set op: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00204: "bogus InhOption value: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00206: "subquery in FROM must have an alias"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00207: "unexpected non-SELECT command in subquery in FROM"
+
+SQLSTATE: XX000
+
+Description: Syntax not supported.
+
+Solution: Modify the SQL statement.
+
+GAUSS-00210: "cannot use aggregate function in function expression in FROM"
+
+SQLSTATE: 42803
+
+Description: The function expression in the **FROM** clause is an aggregate function.
+
+Solution: Do not use an aggregate function in the **FROM** clause.
+
+<br/>
+
+## GAUSS-00211 - GAUSS-00220
+
+<br/>
+
+GAUSS-00211: "cannot use window function in function expression in FROM"
+
+SQLSTATE: 42P20
+
+Description: The function expression in the **FROM** clause is a window function.
+
+Solution: Do not use a window function in the **FROM** clause.
+
+GAUSS-00212: "column name '%s' appears more than once in USING clause"
+
+SQLSTATE: 42701
+
+Description: During join operation, when the **USING** clause is used, the same column name appears in the clause more than once.
+
+Solution: Ensure that the same column name appears only once in the **USING** clause.
+
+GAUSS-00214: "column '%s' specified in USING clause does not exist in left table"
+
+SQLSTATE: 42703
+
+Description: Columns listed in the **USING** clause cannot be found in the left table.
+
+Solution: Ensure that the column name used is in the left and right tables.
+
+GAUSS-00217: "column alias list for '%s' has too many entries"
+
+SQLSTATE: 42601
+
+Description: The number of columns in the object alias exceeds the actual number of columns.
+
+Solution: Ensure that the number of columns in the object alias is consistent with the actual number of columns.
+
+GAUSS-00218: "argument of %s must not contain variables"
+
+SQLSTATE: 42P10
+
+Description: A clause similar to **LIMIT** uses a variable.
+
+Solution: Do not use a variable in a clause similar to **LIMIT**.
+
+GAUSS-00219: "argument of %s must not contain aggregate functions"
+
+SQLSTATE: 42803
+
+Description: A clause similar to **LIMIT** uses an aggregate function.
+
+Solution: Do not use an aggregate function in a clause similar to **LIMIT**.
+
+GAUSS-00220: "argument of %s must not contain window functions"
+
+SQLSTATE: 42P20
+
+Description: A clause similar to **LIMIT** uses a window function.
+
+Solution: Do not use a window function in a clause similar to **LIMIT**.
+
+<br/>
+
+## GAUSS-00221 - GAUSS-00230
+
+<br/>
+
+GAUSS-00221: "%s '%s' is ambiguous"
+
+SQLSTATE: 42702
+
+Description: The column specified by **GROUP BY/ORDER BY** is ambiguous.
+
+Solution: Ensure that the column specified by **GROUP BY/ORDER BY** is correct.
+
+GAUSS-00222: "non-integer constant in %s"
+
+SQLSTATE: 42601
+
+Description: The constant specified by **GROUP BY/ORDER BY** is not of the integer type.
+
+Solution: Ensure that the constant specified by **GROUP BY/ORDER BY** is an integer type.
+
+GAUSS-00223: "%s position %d is not in select list"
+
+SQLSTATE: 42P10
+
+Description: The position of the constant specified by **GROUP BY/ORDER BY** is not in the current list.
+
+Solution: Ensure that the constant position specified by **GROUP BY/ORDER BY** is in the current list.
+
+GAUSS-00224: "window '%s' is already defined"
+
+SQLSTATE: 42P20
+
+Description: The window name has been defined.
+
+Solution: Use an undefined window name.
+
+GAUSS-00225: "window '%s' does not exist"
+
+SQLSTATE: 42704
+
+Description: The specified window object does not exist.
+
+Solution: Define a window object before using it.
+
+GAUSS-00226: "cannot override PARTITION BY clause of window '%s'"
+
+SQLSTATE: 42P20
+
+Description: The **PARTITION BY** clause in the window function is overwritten.
+
+Solution: Ensure that the **PARTITION BY** clause in the window function is not overwritten.
+
+GAUSS-00227: "cannot override ORDER BY clause of window '%s'"
+
+SQLSTATE: 42P20
+
+Description: The **ORDER BY** clause in the window function is overwritten.
+
+Solution: Ensure that the **ORDER BY** clause in the window function is not overwritten.
+
+GAUSS-00228: "cannot override frame clause of window '%s'"
+
+SQLSTATE: 42P20
+
+Description: The frame clause in the window function is overwritten.
+
+Solution: Ensure that the frame clause in the window function is not overwritten.
+
+GAUSS-00229: "in an aggregate with DISTINCT, ORDER BY expressions must appear in argument list"
+
+SQLSTATE: 42P10
+
+Description: In an aggregate operation, parameters in **DISTINCT** and **ORDER BY** expressions do not exist in the target list.
+
+Solution: Ensure that the parameters exist in the target list.
+
+GAUSS-00230: "SELECT DISTINCT ON expressions must match initial ORDER BY expressions"
+
+SQLSTATE: 42P10
+
+Description: When **DISTINCT ON** and **ORDER BY** are used simultaneously, their expressions are different.
+
+Solution: Ensure that their expressions are the same.
+
+<br/>
+
+## GAUSS-00231 - GAUSS-00240
+
+<br/>
+
+GAUSS-00231: "get_matching_location: no matching sortgroupref"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00232: "operator %s is not a valid ordering operator"
+
+SQLSTATE: 42809
+
+Description: The operator specified using **ORDER BY** is an invalid sequencing operator.
+
+Solution: When using **ORDER BY** to specify an operator, use only > or < for sequencing.
+
+GAUSS-00233: "unrecognized sortby_dir: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00234: "unrecognized sortby_nulls: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00235: "window frame with value offset is not implemented"
+
+SQLSTATE: 0A000
+
+Description: Syntax not supported.
+
+Solution: Modify the SQL statement.
+
+GAUSS-00236: "aggregate function calls cannot be nested"
+
+SQLSTATE: 42803
+
+Description: The aggregate function is invoked in nested mode.
+
+Solution: Ensure that the aggregate function is not invoked in nested mode.
+
+GAUSS-00237: "aggregate function calls cannot contain window function calls"
+
+SQLSTATE: 42803
+
+Description: Syntax not supported.
+
+Solution: Modify the SQL statement.
+
+GAUSS-00238: "cache lookup failed for aggregate %u"
+
+SQLSTATE: 22P06
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00239: "window function calls cannot be nested"
+
+SQLSTATE: 42P20
+
+Description: The window function is invoked in nested mode.
+
+Solution: Cancel the nested invoking of the window function.
+
+GAUSS-00240: "aggregates not allowed in WHERE clause"
+
+SQLSTATE: 42803
+
+Description: An aggregate function is used in the **WHERE** clause.
+
+Solution: Do not use an aggregate function in the **WHERE** clause.
+
+<br/>
+
+## GAUSS-00241 - GAUSS-00250
+
+<br/>
+
+GAUSS-00241: "aggregates not allowed in JOIN conditions"
+
+SQLSTATE: 42803
+
+Description: The **JOIN** condition contains an aggregate function.
+
+Solution: Do not use an aggregate function in the **JOIN** condition.
+
+GAUSS-00242: "aggregates not allowed in GROUP BY clause"
+
+SQLSTATE: 42803
+
+Description: The **GROUP BY** clause contains an aggregate function.
+
+Solution: Do not use an aggregate function in the **GROUP BY** clause.
+
+GAUSS-00243: "aggregate functions not allowed in a recursive query's recursive term"
+
+SQLSTATE: 42P19
+
+Description: The recursive query uses an aggregate function.
+
+Solution: Do not use an aggregate function in the recursive query.
+
+GAUSS-00244: "window functions not allowed in WHERE clause"
+
+SQLSTATE: 42P20
+
+Description: The **WHERE** clause contains a window function.
+
+Solution: Do not use a window function in the **WHERE** clause.
+
+GAUSS-00245: "window functions not allowed in JOIN conditions"
+
+SQLSTATE: 42P20
+
+Description: The **JOIN** condition contains a window function.
+
+Solution: Do not use a window function in the **JOIN** condition.
+
+GAUSS-00246: "window functions not allowed in HAVING clause"
+
+SQLSTATE: 42P20
+
+Description: Syntax not supported.
+
+Solution: Modify the SQL statement.
+
+GAUSS-00247: "window functions not allowed in GROUP BY clause"
+
+SQLSTATE: 42P20
+
+Description: The **GROUP BY** clause contains a window function.
+
+Solution: Do not use a window function in the **GROUP BY** clause.
+
+GAUSS-00248: "window functions not allowed in window definition"
+
+SQLSTATE: 42P20
+
+Description: The **PARTITION** or **ORDER BY** clause contains a window function.
+
+Solution: Do not use a window function in the **PARTITION** or **ORDER BY** clause.
+
+GAUSS-00249: "column '%s.%s' must appear in the GROUP BY clause or be used in an aggregate function"
+
+SQLSTATE: 42803
+
+Description: The **GROUP BY** clause contains an aggregate function or lacks variables existing in the target list.
+
+Solution: Do not use an aggregate function in the **GROUP BY** clause or include variables existing in the target list.
+
+GAUSS-00250: "subquery uses ungrouped column '%s.%s' from outer query"
+
+SQLSTATE: 42803
+
+Description: The subquery uses an external ungrouped column.
+
+Solution: Ensure that the subquery uses an external grouped column.
+
+<br/>
+
+## GAUSS-00251 - GAUSS-00260
+
+<br/>
+
+GAUSS-00251: "yylex_init() failed: %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00252: "Invalid RTE found"
+
+SQLSTATE: XX000
+
+Description: The reference is not found.
+
+Solution: Modify the SQL statement.
+
+GAUSS-00253: "cannot assign to system column '%s'"
+
+SQLSTATE: 0A000
+
+Description: A value cannot be assigned to the system column.
+
+Solution: Do not perform any operation on the system column.
+
+GAUSS-00254: "cannot set an array element to DEFAULT"
+
+SQLSTATE: 0A000
+
+Description: The default value is set for an array element.
+
+Solution: Do not set the default value of for an array element.
+
+GAUSS-00255: "cannot set a subfield to DEFAULT"
+
+SQLSTATE: 0A000
+
+Description: The default value is set for an array subscript.
+
+Solution: Do not set the default value for an array subscript.
+
+GAUSS-00256: "column '%s' is of type %s but expression is of type %s"
+
+SQLSTATE: 42804
+
+Description: Data types at both sides of the expression are inconsistent.
+
+Solution: Switch the data type at either side to make them consistent.
+
+GAUSS-00257: "cannot assign to field '%s' of column '%s' because its type %s is not a composite type"
+
+SQLSTATE: 42804
+
+Description: A column is specified for a non-composite variable.
+
+Solution: Do not specify a column for a non-composite variable.
+
+GAUSS-00258: "cannot assign to field '%s' of column '%s' because there is no such column in data type %s"
+
+SQLSTATE: 42703
+
+Description: A column is specified for a non-composite variable.
+
+Solution: Do not specify a column for a non-composite variable.
+
+GAUSS-00259: "cannot assign to system column '%s'"
+
+SQLSTATE: 42703
+
+Description: A value cannot be assigned to the system column.
+
+Solution: Do not perform any operation on the system column.
+
+GAUSS-00260: "array assignment to '%s' requires type %s but expression is of type %s"
+
+SQLSTATE: 42804
+
+Description: The object to which a value is assigned does not match the actual expression type.
+
+Solution: Modify the SQL statement.
+
+<br/>
+
+## GAUSS-00261 - GAUSS-00270
+
+<br/>
+
+GAUSS-00261: "subfield '%s' is of type %s but expression is of type %s"
+
+SQLSTATE: 42804
+
+Description: Data types at both sides of the expression are inconsistent.
+
+Solution: Switch the data type at either side to make them consistent.
+
+GAUSS-00262: "column '%s' specified more than once"
+
+SQLSTATE: 42701
+
+Description: A column is specified multiple times when inserting data to a table.
+
+Solution: Insert data in each column only once.
+
+GAUSS-00263: "SELECT * with no tables specified is not valid"
+
+SQLSTATE: 42601
+
+Description: Syntax not supported.
+
+Solution: Modify the SQL statement.
+
+GAUSS-00265: "Un-support feature"
+
+SQLSTATE: XX000
+
+Description: Feature not supported.
+
+Solution: Do not use it.
+
+GAUSS-00268: "VALUES lists must all be the same length"
+
+SQLSTATE: 42601
+
+Description: In the **INSERT … VALUES** statement, the number of values does not match that of table columns.
+
+Solution: 1. Run **\d tblname** to check columns in the table. 2. Ensure that the number of values matches that of table columns. 3. Modify the syntax of the **INSERT … VALUES** statement.
+
+GAUSS-00269: "VALUES must not contain table references"
+
+SQLSTATE: 0A000
+
+Description: The **SELECT** clause in the **INSERT … VALUES** statement contains a join list.
+
+Solution: Ensure that the **SELECT** clause in the **INSERT … VALUES** statement does not contain a join list. Modify the INSERT statement based on its syntax.
+
+GAUSS-00270: "VALUES must not contain OLD or NEW references"
+
+SQLSTATE: 0A000
+
+Description: Syntax not supported.
+
+Solution: Modify the SQL statement.
+
+<br/>
+
+## GAUSS-00271 - GAUSS-00280
+
+<br/>
+
+GAUSS-00271: "cannot use aggregate function in VALUES"
+
+SQLSTATE: 42803
+
+Description: The **VALUES** clause in the **INSERT** statement contains an aggregate function.
+
+Solution: Ensure that the **VALUES** clause in the **INSERT** statement does not contain an aggregate function. Modify the **INSERT** statement based on its syntax.
+
+GAUSS-00272: "cannot use window function in VALUES"
+
+SQLSTATE: 42P20
+
+Description: Syntax not supported.
+
+Solution: Modify the SQL statement.
+
+GAUSS-00273: "INSERT has more expressions than target columns"
+
+SQLSTATE: 42601
+
+Description: The number of valid expressions or values in the **INSERT** statement is greater than the corresponding number of target columns.
+
+Solution: Ensure that the number of valid expressions or values in the **INSERT** statement is consistent with the corresponding number of target columns.
+
+GAUSS-00274: "INSERT has more target columns than expressions"
+
+SQLSTATE: 42601
+
+Description: The number of target columns in the **INSERT** statement is greater than the corresponding number of valid expressions or values.
+
+Solution: Ensure that the number of target columns in the **INSERT** statement is consistent with the corresponding number of valid expressions or values. If they are inconsistent, modify the **INSERT** statement.
+
+GAUSS-00275: "SELECT … INTO is not allowed here"
+
+SQLSTATE: 42601
+
+Description: The syntax is incorrectly parsed. Specifically, the **SELECT** statement contains an **INTO** clause, which is not supported.
+
+Solution: Modify the **SELECT** statement to ensure that it does not contain an **INTO** clause.
+
+GAUSS-00276: "DEFAULT can only appear in a VALUES list within INSERT"
+
+SQLSTATE: 42601
+
+Description: The syntax is incorrectly parsed. Specifically, the **SELECT** statement contains the default expression or value, which is not supported.
+
+Solution: Ensure that the syntax of the **SELECT** statement is correct.
+
+GAUSS-00277: "SELECT FOR UPDATE/SHARE cannot be applied to VALUES"
+
+SQLSTATE: 0A000
+
+Description: The expression or value in the **SELECT** statement contains the **SELECT FOR UPDATE/SHARE** clause, which is not supported.
+
+Solution: Ensure that the **SELECT** statement is correct.
+
+GAUSS-00278: "SELECT FOR UPDATE/SHARE is not allowed with UNION/INTERSECT/EXCEPT"
+
+SQLSTATE: 0A000
+
+Description: The clause collection (UNION/INTERSECT/EXCEPT) in the **SELECT** statement contains the **SELECT FOR UPDATE/SHARE** clause, which is not supported.
+
+Solution: Ensure that the **SELECT** statement is correct.
+
+GAUSS-00279: "invalid UNION/INTERSECT/EXCEPT ORDER BY clause"
+
+SQLSTATE: 0A000
+
+Description: Syntax not supported.
+
+Solution: Modify the SQL statement.
+
+GAUSS-00280: "INTO is only allowed on first SELECT of UNION/INTERSECT/EXCEPT"
+
+SQLSTATE: 42601
+
+Description: The syntax is incorrectly parsed. The position of the **INTO** clause in the **SELECT..UNION/INTERSECT/EXCEPT** statement is incorrect.
+
+Solution: Ensure that the **INTO** clause exists only in the **SELECT..UNION/INTERSECT/EXCEPT** statement.
+
+<br/>
+
+## GAUSS-00281 - GAUSS-00290
+
+<br/>
+
+GAUSS-00281: "UNION/INTERSECT/EXCEPT member statement cannot refer to other relations of same query level"
+
+SQLSTATE: 42P10
+
+Description: Syntax not supported.
+
+Solution: Modify the SQL statement.
+
+GAUSS-00282: "each %s query must have the same number of columns"
+
+SQLSTATE: 42601
+
+Description: Syntax error.
+
+Solution: Modify the SQL statement.
+
+GAUSS-00283: "cannot use aggregate function in UPDATE"
+
+SQLSTATE: 42803
+
+Description: In the **UPDATE** syntax, the value in the column to be updated cannot be an aggregate function.
+
+Solution: Ensure that the column value to be updated in the **UPDATE** syntax is not an aggregate function. If the column value to be updated is an aggregate function, modify the **UPDATE** syntax.
+
+GAUSS-00284: "cannot use window function in UPDATE"
+
+SQLSTATE: 42P20
+
+Description: Syntax not supported.
+
+Solution: Modify the SQL statement.
+
+GAUSS-00285: "UPDATE target count mismatch - internal error"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00286: "column '%s.%s' of relation '%s' does not exist"
+
+SQLSTATE: 42703
+
+Description: In the **UPDATE** syntax, the column name to be updated does not exist.
+
+Solution: Ensure that the column name to be updated in the **UPDATE** syntax is correct.
+
+GAUSS-00287: "cannot use aggregate function in RETURNING"
+
+SQLSTATE: 42803
+
+Description: The **RETURNING** clause in the **INSERT/UPDATE/DELETE** syntax contains an aggregate function, which is not supported.
+
+Solution: Ensure that the **RETURNING** clause in the **INSERT/UPDATE/DELETE** syntax is correct.
+
+GAUSS-00288: "cannot use window function in RETURNING"
+
+SQLSTATE: 42P20
+
+Description: Syntax not supported.
+
+Solution: Modify the SQL statement.
+
+<br/>
+
+## GAUSS-00291 - GAUSS-00300
+
+<br/>
+
+GAUSS-00291: "unexpected non-SELECT command in DECLARE CURSOR"
+
+SQLSTATE: XX000
+
+Description: Syntax not supported.
+
+Solution: Modify the SQL statement.
+
+GAUSS-00292: "DECLARE CURSOR must not contain data-modifying statements in WITH"
+
+SQLSTATE: 0A000
+
+Description: The **WITH** clause in the **DECLARE CURSOR** syntax contains the **INSERT/UPDATE/DELETE** statement.
+
+Solution: Check and modify the query statement.
+
+GAUSS-00293: "DECLARE CURSOR WITH HOLD … FOR UPDATE/SHARE is not supported"
+
+SQLSTATE: 0A000
+
+Description: The **DECLARE CURSOR WITH HOLD … FOR SelectStmt** clause contains the **UPDATE/SHARE** statement, which is not supported.
+
+Solution:DECLARE CURSOR WITH HOLD … Check and modify the query statement.
+
+GAUSS-00294: "DECLARE SCROLL CURSOR … FOR UPDATE/SHARE is not supported"
+
+SQLSTATE: 0A000
+
+Description: The **DECLARE SCROLL CURSOR… FOR SelectStmt** clause contains the **UPDATE/SHARE** statement, which is not supported.
+
+Solution: Check and modify the query statement.
+
+GAUSS-00295: "DECLARE INSENSITIVE CURSOR … FOR UPDATE/SHARE is not supported"
+
+SQLSTATE: 0A000
+
+Description: The **DECLARE INSENSITIVE CURSOR … FOR SelectStmt** clause contains the **UPDATE/SHARE** statement, which is not supported.
+
+Solution: Check and modify the query statement.
+
+GAUSS-00298: "PGXC Node %s: object not defined"
+
+SQLSTATE: 42704
+
+Description: The specified node object is abnormal or does not exist.
+
+Solution: Ensure that the specified node name exists and is operating properly. If the specified node is abnormal, restart the node.
+
+GAUSS-00300: "EXECUTE DIRECT cannot execute DML queries"
+
+SQLSTATE: 0A000
+
+Description:EXECUTE DIRECT ON ( nodename [, … In the **EXECUTE DIRECT ON ( nodename [, … ] ) query** syntax, a DML statement is executed on a DN, which is not supported.
+
+Solution: Do not execute a DML statement in the **EXECUTE DIRECT ON ( nodename [, … ] ) query** syntax.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/30-GAUSS-02901-GAUSS-03000.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/30-GAUSS-02901-GAUSS-03000.md
new file mode 100644
index 0000000000000000000000000000000000000000..1d5c1b3a0383eede8acda7ea0eefe595307787e9
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/30-GAUSS-02901-GAUSS-03000.md
@@ -0,0 +1,780 @@
+---
+title: GAUSS-02901 - GAUSS-03000
+summary: GAUSS-02901 - GAUSS-03000
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-02901 - GAUSS-03000
+
+<br/>
+
+## GAUSS-02901 - GAUSS-02910
+
+<br/>
+
+GAUSS-02901: "invalid external 'cidr' value"
+
+SQLSTATE: 22P03
+
+Description: The network address is invalid.
+
+Solution: Check whether the format of the entered network address is correct.
+
+GAUSS-02902: "invalid inet bit length: %d"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02903: "invalid mask length: %d"
+
+SQLSTATE: 22023
+
+Description: The network address is invalid.
+
+Solution: Check whether the format of the entered network address is correct.
+
+GAUSS-02904: "could not format cidr value: %m"
+
+SQLSTATE: 22P03
+
+Description: Failed to format the network address to the CIDR format.
+
+Solution: Check whether the data to be formatted is a valid network address.
+
+GAUSS-02905: "unsupported type: %u"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02906: "cannot AND inet values of different sizes"
+
+SQLSTATE: 22023
+
+Description: IPv4 addresses and IPv6 addresses cannot be used as AND operands at the same time.
+
+Solution: Check whether the left and right operands of AND are the same IP address family.
+
+GAUSS-02907: "cannot OR inet values of different sizes"
+
+SQLSTATE: 22023
+
+Description: IPv4 addresses and IPv6 addresses cannot be used as OR operands at the same time.
+
+Solution: Check whether the left and right operands of OR are the same IP address family.
+
+GAUSS-02908: "result is out of range"
+
+SQLSTATE: 22003
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02909: "cannot subtract inet values of different sizes"
+
+SQLSTATE: 22023
+
+Description: IPv4 addresses and IPv6 addresses cannot be used as SUBTRACT operands at the same time.
+
+Solution: Check whether the left and right operands of SUBTRACT are the same IP address family.
+
+GAUSS-02910: "arraycontsel called for unrecognized operator %u"
+
+SQLSTATE: XX000
+
+Description: The array operation is incorrect.
+
+Solution: Contact technical support. Alternatively, check the statement or data.
+
+<br/>
+
+## GAUSS-02911 - GAUSS-02920
+
+<br/>
+
+GAUSS-02911: "suppress_redundant_updates_trigger: must be called as trigger"
+
+SQLSTATE: 39P01
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02912: "suppress_redundant_updates_trigger: must be called on update"
+
+SQLSTATE: 39P01
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02913: "suppress_redundant_updates_trigger: must be called before update"
+
+SQLSTATE: 39P01
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02914: "suppress_redundant_updates_trigger: must be called for each row"
+
+SQLSTATE: 39P01
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02915: "could not determine input data types"
+
+SQLSTATE: 22023
+
+Description: The data type is incorrect.
+
+Solution: Contact technical support. Alternatively, check the statement or data.
+
+GAUSS-02916: "neither input type is an array"
+
+SQLSTATE: 42804
+
+Description: The array data is incorrect.
+
+Solution: Contact technical support. Alternatively, check the statement or data.
+
+GAUSS-02917: "argument must be empty or one-dimensional array"
+
+SQLSTATE: 22000
+
+Description: The parameter is incorrect.
+
+Solution: Contact technical support. Alternatively, check the statement or data.
+
+GAUSS-02918: "cannot concatenate incompatible arrays"
+
+SQLSTATE: 42804
+
+Description: The array data is incorrect.
+
+Solution: Contact technical support. Alternatively, check the statement or data.
+
+GAUSS-02919: "cannot concatenate incompatible arrays"
+
+SQLSTATE: 2202E
+
+Description: The array data is incorrect.
+
+Solution: Contact technical support. Alternatively, check the statement or data.
+
+GAUSS-02920: "invalid number of dimensions: %d"
+
+SQLSTATE: 22023
+
+Description: The array dimension is less than zero.
+
+Solution: Check the input parameter.
+
+<br/>
+
+## GAUSS-02921 - GAUSS-02930
+
+<br/>
+
+GAUSS-02921: "could not determine input data type"
+
+SQLSTATE: 22023
+
+Description: The data type is incorrect.
+
+Solution: Contact technical support. Alternatively, check the statement or data.
+
+GAUSS-02922: "array_agg_transfn called in non-aggregate context"
+
+SQLSTATE: XX000
+
+Description: The **array_agg** function is used in non-aggregation operations.
+
+Solution: Modify the use of **array_agg** in the query.
+
+GAUSS-02924: "no active snapshot set"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02925: "invalid snapshot data"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02926: "SPI_connect failed"
+
+SQLSTATE: SP001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02927: "SPI_finish failed"
+
+SQLSTATE: SP002
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02928: "insert or update on table '%s' violates foreign key constraint '%s'"
+
+SQLSTATE: 23503
+
+Description: The insertion or update operation violates the foreign key constraint.
+
+Solution: Check whether the foreign key constraint meets the current insertion or update operation.
+
+GAUSS-02929: "invalid confmatchtype"
+
+SQLSTATE: 42804
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02930: "unrecognized match type: %d"
+
+SQLSTATE: 42804
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02931 - GAUSS-02940
+
+<br/>
+
+GAUSS-02931: "SPI_prepare returned %d for %s"
+
+SQLSTATE: SP003
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02932: "SPI_execute_snapshot returned %d"
+
+SQLSTATE: SP005
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02933: "function '%s' must be fired for INSERT"
+
+SQLSTATE: 39P01
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02934: "function '%s' must be fired for UPDATE"
+
+SQLSTATE: 39P01
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02935: "function '%s' must be fired for DELETE"
+
+SQLSTATE: 39P01
+
+Description: Failed to trigger the function when the delete operation is performed.
+
+Solution: Ensure that the triggering logic is normal.
+
+GAUSS-02936: "no pg_constraint entry for trigger '%s' on table '%s'"
+
+SQLSTATE: 42P17
+
+Description: No corresponding constraint exists for the trigger on the table.
+
+Solution: Delete the trigger related to the integrity constraint and add a constraint.
+
+GAUSS-02937: "wrong pg_constraint entry for trigger '%s' on table '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02938: "null confkey for constraint %u"
+
+SQLSTATE: XX005
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02939: "confkey is not a 1-D smallint array"
+
+SQLSTATE: 42804
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02941 - GAUSS-02950
+
+<br/>
+
+GAUSS-02941: "conppeqop is not a 1-D Oid array"
+
+SQLSTATE: 42804
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02943: "conffeqop is not a 1-D Oid array"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02944: "referential integrity query on '%s' from constraint '%s' on '%s' gave unexpected result"
+
+SQLSTATE: XX000
+
+Description: An error occurred when checking the primary and foreign key constraints of the two tables.
+
+Solution: Check whether the data in the tables related to the primary and foreign key constraints is correct.
+
+GAUSS-02945: "update or delete on table '%s' violates foreign key constraint '%s' on table '%s'"
+
+SQLSTATE: 23503
+
+Description: Update or delete operations violate the foreign key constraint.
+
+Solution: Check whether the updated or deleted foreign-key values are recorded in the primary key.
+
+GAUSS-02946: "no conversion function from %s to %s"
+
+SQLSTATE: 42883
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02948: "unrecognized bytea_output setting: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02949: "Node id out of range"
+
+SQLSTATE: XX001
+
+Description: The number of node IDs is out of range.
+
+Solution: A maximum of 4096 DNs is supported. If the number of node IDs is greater than 4096 or smaller than 0, it is out of range. Correct the number of node IDs.
+
+GAUSS-02950: "Node id is too long"
+
+SQLSTATE: XX001
+
+Description: The length of the node ID exceeds the maximum length.
+
+Solution: A maximum of 4096 DNs is supported. If the length of the node ID is greater than or equal to 5 characters, it exceeds the maximum length. Correct the length of node ID.
+
+<br/>
+
+## GAUSS-02951 - GAUSS-02960
+
+<br/>
+
+GAUSS-02951: "invalid backend encoding: encoding max length < 1"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02952: "could not determine which collation to use for string comparison"
+
+SQLSTATE: 42P22
+
+Description: The parser cannot parse the implicit conversion mode.
+
+Solution: Check whether multiple collations are compared in the current string.
+
+GAUSS-02953: "could not convert string to UTF-16: error code %lu"
+
+SQLSTATE: XX000
+
+Description: Failed to convert the string to the UTF-16 format.
+
+Solution: Solve the issue based on the error code.
+
+GAUSS-02954: "could not compare Unicode strings: %m"
+
+SQLSTATE: XX000
+
+Description: Failed to convert the string to the Unicode format.
+
+Solution: Correct the string error.
+
+GAUSS-02955: "index %d out of valid range, 0..%d"
+
+SQLSTATE: 2202E
+
+Description: The entered index value is out of the length range of the bytea string.
+
+Solution: Ensure that the index value is within the valid length range of a bytea string.
+
+GAUSS-02956: "invalid name syntax"
+
+SQLSTATE: 42602
+
+Description: Failed to divide strings into delimited string groups.
+
+Solution: Check the input strings.
+
+GAUSS-02957: "regular expression failed: %s"
+
+SQLSTATE: 2201B
+
+Description: An error occurs because a queried string is empty or an incorrect querying mode is used.
+
+Solution: Check the input parameter for querying the string.
+
+GAUSS-02958: "field position must be greater than zero"
+
+SQLSTATE: 22023
+
+Description: The field position is less than 1.
+
+Solution: The field position must be greater than 0 and at least be 1.
+
+GAUSS-02959: "string_agg_transfn called in non-aggregate context"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02960: "could not determine data type of concat() input"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02961 - GAUSS-02970
+
+<br/>
+
+GAUSS-02961: "unterminated conversion specifier"
+
+SQLSTATE: 22023
+
+Description: The formatted string does not have a terminator.
+
+Solution: Check whether the formatted string is correct.
+
+GAUSS-02962: "argument number is out of range"
+
+SQLSTATE: 22003
+
+Description: Excessive parameters for schema matching exist. The number of parameters is out of range.
+
+Solution: Redefine the string for schema matching and reduce the number of parameters.
+
+GAUSS-02964: "too few arguments for format"
+
+SQLSTATE: 22023
+
+Description: The number of parameters is insufficient.
+
+Solution: Ensure that the number of formatted strings matches the number of formatted variables.
+
+GAUSS-02965: "unrecognized conversion specifier '%c'"
+
+SQLSTATE: 22023
+
+Description: The mode used for converting text to string is incorrect.
+
+Solution: Check the mode used of converting text to string. The value can only be '%s', '%I', or '%L'.
+
+GAUSS-02966: "null values cannot be formatted as an SQL identifier"
+
+SQLSTATE: 22004
+
+Description: When '%I' is used to convert text to string, the input data cannot be **NULL**.
+
+Solution: Check whether the conversion mode is correct.
+
+GAUSS-02969: "invalid Datum pointer"
+
+SQLSTATE: 22000
+
+Description: The input data cannot be empty.
+
+Solution: Check the input data.
+
+GAUSS-02970: "invalid typLen: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-02971 - GAUSS-02980
+
+<br/>
+
+GAUSS-02971: "value out of range: overflow"
+
+SQLSTATE: 22003
+
+Description: Overflows occur when the number of floating points exceeds the upper limit.
+
+Solution: Ensure that the input data does not exceed the upper limit. For the data value range, see en-us_topic_0237121926.html.
+
+GAUSS-02972: "invalid input syntax for type real: '%s'"
+
+SQLSTATE: 22P02
+
+Description: The format of the string to be converted to the real type is incorrect.
+
+Solution: Check the input data.
+
+GAUSS-02973: "'%s' is out of range for type real"
+
+SQLSTATE: 22003
+
+Description: Overflows occur when the input string is converted to the real type.
+
+Solution: Check the input data.
+
+GAUSS-02974: "'%s' is out of range for type double precision"
+
+SQLSTATE: 22003
+
+Description: Overflows occur when input string is converted to the double type.
+
+Solution: Check the input data.
+
+GAUSS-02975: "input is out of range"
+
+SQLSTATE: 22003
+
+Description: The input is out of range.
+
+Solution: Ensure that the returned value of the parameter that causes this error is within the range. For the data value range, see en-us_topic_0237121926.html.
+
+GAUSS-02976: "setseed parameter %f out of range [-1,1]"
+
+SQLSTATE: XX000
+
+Description: The **setseed()** function parameter is out of range.
+
+Solution: Ensure that the **setseed()** function parameter ranges from -1 to 1.
+
+GAUSS-02978: "lower and upper bounds must be finite"
+
+SQLSTATE: 2201G
+
+Description: Both the upper and lower limit values must be finite values.
+
+Solution: Check the input data.
+
+GAUSS-02979: "reference to parent directory ('..') not allowed"
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02980: "absolute path not allowed"
+
+SQLSTATE: 42501
+
+Description: Only the data and log directories support absolute paths.
+
+Solution: Change the path to a relative path.
+
+<br/>
+
+## GAUSS-02981 - GAUSS-02990
+
+<br/>
+
+GAUSS-02981: "path must be in or below the current directory"
+
+SQLSTATE: 42501
+
+Description: The input path must be included in the current path.
+
+Solution: Change the input path.
+
+GAUSS-02982: "could not stat file '%s': %m"
+
+SQLSTATE: XX000
+
+Description: Failed to obtain the file status information.
+
+Solution: Check whether the file status is abnormal, for example, the file does not exist or you do not have the file read permission.
+
+GAUSS-02983: "requested length too large"
+
+SQLSTATE: 22023
+
+Description: The length of the file to be read exceeds the maximum value.
+
+Solution: Reduce the size of the file to be read to a value less than 1 GB.
+
+GAUSS-02984: "could not seek in file '%s': %m"
+
+SQLSTATE: XX000
+
+Description: The file cannot be located based on the offset.
+
+Solution: Ensure that the file status is normal.
+
+GAUSS-02985: "could not read file '%s': %m"
+
+SQLSTATE: XX000
+
+Description: Only database system administrator can read the file.
+
+Solution: Read the file as a system administrator.
+
+GAUSS-02987: "requested length cannot be negative"
+
+SQLSTATE: 22023
+
+Description: Only database system administrator can obtain the file information.
+
+Solution: Change to a system administrator.
+
+GAUSS-02990: "requested length too large"
+
+SQLSTATE: 54000
+
+Description: The length of the file to be read exceeds the maximum value.
+
+Solution: Reduce the size of the file to be read to a value less than 1 GB.
+
+<br/>
+
+## GAUSS-02991 - GAUSS-03000
+
+<br/>
+
+GAUSS-02991: "requested character too large"
+
+SQLSTATE: 54000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02992: "requested character too large for encoding: %d"
+
+SQLSTATE: 54000
+
+Description: The input string is too long.
+
+Solution: Ensure that the input string is in Unicode format.
+
+GAUSS-02993: "TIMESTAMP(%d)%s precision must not be negative"
+
+SQLSTATE: 22023
+
+Description: The precision of the timestamp type cannot be smaller than zero.
+
+Solution: Check the precision of the timestamp type.
+
+GAUSS-02994: "timestamp out of range: '%s'"
+
+SQLSTATE: 22020
+
+Description: The input timestamp value is out of range.
+
+Solution: Check the timestamp value.
+
+GAUSS-02995: "date/time value '%s' is no longer supported"
+
+SQLSTATE: 0A000
+
+Description: The string value to be converted to the timestamp type is incorrectly parsed.
+
+Solution: Ensure that the format of the input string is correct. The string to be converted to the timestamp type must meet the format requirements in en-us_topic_0237121952.html.
+
+GAUSS-02996: "unexpected dtype %d while parsing timestamp '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-02997: "timestamp out of range"
+
+SQLSTATE: 22008
+
+Description: The input timestamp value is out of range.
+
+Solution: Check whether the input timestamp value is valid.
+
+GAUSS-02998: "timestamp cannot be NaN"
+
+SQLSTATE: 22008
+
+Description: The data of timestamp type cannot be an unlimited value.
+
+Solution: Check the input data.
+
+GAUSS-02999: "smalldatetime out of range: '%s'"
+
+SQLSTATE: 22008
+
+Description: Data is out of range.
+
+Solution: Check the input data.
+
+GAUSS-03000: "unexpected dtype %d while parsing smalldatetime '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/31-GAUSS-03001-GAUSS-03100.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/31-GAUSS-03001-GAUSS-03100.md
new file mode 100644
index 0000000000000000000000000000000000000000..94e05641f1fc17ed4e012de87fe9bebd7ab6d819
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/31-GAUSS-03001-GAUSS-03100.md
@@ -0,0 +1,812 @@
+---
+title: GAUSS-03001 - GAUSS-03100
+summary: GAUSS-03001 - GAUSS-03100
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-03001 - GAUSS-03100
+
+<br/>
+
+## GAUSS-03001 - GAUSS-03010
+
+<br/>
+
+GAUSS-03001: "smalldatetime out of range"
+
+SQLSTATE: 22008
+
+Description: Data is out of range.
+
+Solution: Check the input data.
+
+GAUSS-03002: "smalldatetime cannot be NaN"
+
+SQLSTATE: 22008
+
+Description: The data of the smalldatetime type cannot be an infinite value.
+
+Solution: Check the input data.
+
+GAUSS-03003: "timestamp(%d) precision must be between %d and %d"
+
+SQLSTATE: 22023
+
+Description: The timestamp precision must range between 0 and 6.
+
+Solution: Ensure that the input precision value is within the range.
+
+GAUSS-03004: "unexpected dtype %d while parsing timestamptz '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03005: "interval out of range"
+
+SQLSTATE: 22008
+
+Description: The input interval value is out of range.
+
+Solution: Check the input data.
+
+GAUSS-03006: "unexpected dtype %d while parsing interval '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03007: "could not convert interval to tm"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03008: "invalid INTERVAL type modifier"
+
+SQLSTATE: 22023
+
+Description: The precision of the interval type is invalid.
+
+Solution: Check the precision value.
+
+GAUSS-03009: "INTERVAL(%d) precision must not be negative"
+
+SQLSTATE: 22023
+
+Description: The precision of the interval type cannot be negative.
+
+Solution: Check the precision value.
+
+GAUSS-03010: "invalid INTERVAL typmod: 0x%x"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03011 - GAUSS-03020
+
+<br/>
+
+GAUSS-03013: "invalid argument for EncodeSpecialTimestamp"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03014: "cannot subtract infinite timestamps"
+
+SQLSTATE: 22008
+
+Description: Failed to subtract the infinite timestamp.
+
+Solution: Check the input data.
+
+GAUSS-03015: "expected 2-element interval array"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03016: "timestamp units '%s' not supported"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03017: "timestamp units '%s' not recognized"
+
+SQLSTATE: 22023
+
+Description: The timestamp does not have a time unit.
+
+Solution: Check the input parameter.
+
+GAUSS-03018: "timestamp with time zone units '%s' not supported"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03019: "timestamp with time zone units '%s' not recognized"
+
+SQLSTATE: 22023
+
+Description: The timestamp with a time zone does not have a time unit.
+
+Solution: Check the input parameter.
+
+GAUSS-03020: "interval units '%s' not supported"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03021 - GAUSS-03030
+
+<br/>
+
+GAUSS-03021: "interval units '%s' not recognized"
+
+SQLSTATE: 22023
+
+Description: The interval type does not have a time unit.
+
+Solution: Check the input parameter.
+
+GAUSS-03022: "could not convert to time zone '%s'"
+
+SQLSTATE: 22023
+
+Description: Failed to convert to a specified time zone.
+
+Solution: Check the input parameter. For the data value range, see en-us_topic_0237121926.html.
+
+GAUSS-03023: "time zone '%s' not recognized"
+
+SQLSTATE: 22023
+
+Description: Failed to recognize the time zone to be converted.
+
+Solution: Check the input parameter.
+
+GAUSS-03024: "interval time zone '%s' must not specify month"
+
+SQLSTATE: 22023
+
+Description: Failed to specify a month for the time zone of the interval type.
+
+Solution: Check the input parameter. For the data value range, see en-us_topic_0237121926.html.
+
+GAUSS-03027: "the format is not correct!"
+
+SQLSTATE: 0A000
+
+Description: The date format is incorrect.
+
+Solution: Ensure that the format of the input data is correct. For the data value range, see en-us_topic_0237121926.html.
+
+GAUSS-03028: "the year is invalid"
+
+SQLSTATE: 0A000
+
+Description: The year value is invalid.
+
+Solution: Ensure that the input year value contains four digits.
+
+GAUSS-03029: "the month is invalid!"
+
+SQLSTATE: 0A000
+
+Description: The month value is invalid.
+
+Solution: Ensure that the input month value contains two digits.
+
+GAUSS-03030: "the format is not correct\n"
+
+SQLSTATE: 0A000
+
+Description: More than two separators are found in time strings, which is invalid.
+
+Solution: Ensure that the input data is valid. For the data value range, see en-us_topic_0237121926.html.
+
+<br/>
+
+## GAUSS-03031 - GAUSS-03040
+
+<br/>
+
+GAUSS-03031: "the time is not correct!"
+
+SQLSTATE: 0A000
+
+Description: The length of the time string exceeds the limit.
+
+Solution: Ensure that the range of input data meets the requirement.
+
+GAUSS-03032: "the hour is invalid!"
+
+SQLSTATE: 0A000
+
+Description: The hour value is invalid.
+
+Solution: Ensure that the input hour value contains two digits.
+
+GAUSS-03033: "the minute is invalid!"
+
+SQLSTATE: 0A000
+
+Description: The minute value is invalid.
+
+Solution: Ensure that the input minute value contains two digits.
+
+GAUSS-03034: "the year = %d is illegal"
+
+SQLSTATE: 0A000
+
+Description: The year value is invalid.
+
+Solution: Ensure that the year value ranges from 0 to 9999.
+
+GAUSS-03035: "the day = %d for february in leap year is illegal"
+
+SQLSTATE: 0A000
+
+Description: A date in February in a leap year is invalid.
+
+Solution: Ensure that the date value is valid.
+
+GAUSS-03036: "the day = %d for big month is illegal"
+
+SQLSTATE: 0A000
+
+Description: The date of a solar month of 31 days is invalid.
+
+Solution: Ensure that the date value is valid.
+
+GAUSS-03037: "the day = %d for small month is illegal"
+
+SQLSTATE: 0A000
+
+Description: The date of a solar month of 30 days is invalid.
+
+Solution: Ensure that the date value is valid.
+
+GAUSS-03038: "the day = %d for February in commen year is illegal"
+
+SQLSTATE: 0A000
+
+Description: A date in February in a non-leap year is invalid.
+
+Solution: Ensure that the date value is valid.
+
+GAUSS-03039: "the month = %d is illegal"
+
+SQLSTATE: 0A000
+
+Description: The month value is invalid.
+
+Solution: Ensure that the month value ranges from 1 to 12.
+
+GAUSS-03040: "the hour = %d is illegal"
+
+SQLSTATE: 0A000
+
+Description: The hour value is invalid.
+
+Solution: Ensure that the hour value ranges from 0 to 24.
+
+<br/>
+
+## GAUSS-03041 - GAUSS-03050
+
+<br/>
+
+GAUSS-03041: "the minute = %d is illegal"
+
+SQLSTATE: 0A000
+
+Description: The minute value is invalid.
+
+Solution: Ensure that the minute value ranges from 0 to 59.
+
+GAUSS-03042: "the second = %d is illegal"
+
+SQLSTATE: 0A000
+
+Description: The second value is invalid.
+
+Solution: Ensure that the second value ranges from 0 to 59.
+
+GAUSS-03043: "encoding conversion from %s to ASCII not supported"
+
+SQLSTATE: 0A000
+
+Description: Converting the current encoding format to ASCII is not supported.
+
+Solution: Ensure that the encoding format of the input string is valid.
+
+GAUSS-03044: "too many points requested"
+
+SQLSTATE: 54000
+
+Description: Too many points need to be obtained.
+
+Solution: Check the input parameter.
+
+GAUSS-03045: "could not format 'path' value"
+
+SQLSTATE: 22023
+
+Description: Failed to obtain the path information.
+
+Solution: Check the input parameter.
+
+GAUSS-03046: "invalid input syntax for type box: '%s'"
+
+SQLSTATE: 22P02
+
+Description: The value of the box type is invalid.
+
+Solution: Check the input parameter.
+
+GAUSS-03047: "invalid input syntax for type line: '%s'"
+
+SQLSTATE: 22P02
+
+Description: The value of the line type is invalid.
+
+Solution: Check the input parameter.
+
+GAUSS-03048: "type 'line' not yet implemented"
+
+SQLSTATE: 0A000
+
+Description: The line type cannot be used.
+
+Solution: Check whether the version supports the line type.
+
+GAUSS-03049: "invalid input syntax for type path: '%s'"
+
+SQLSTATE: 22P02
+
+Description: The value of the path type is invalid.
+
+Solution: Check the input parameter.
+
+GAUSS-03050: "invalid number of points in external 'path' value"
+
+SQLSTATE: 22P03
+
+Description: The number of points in the path is invalid.
+
+Solution: Check the input parameter.
+
+<br/>
+
+## GAUSS-03051 - GAUSS-03060
+
+<br/>
+
+GAUSS-03051: "invalid input syntax for type point: '%s'"
+
+SQLSTATE: 22P02
+
+Description: The value of the point type is invalid.
+
+Solution: Check the input parameter.
+
+GAUSS-03052: "invalid input syntax for type lseg: '%s'"
+
+SQLSTATE: 22P02
+
+Description: The value of the lseg type is invalid.
+
+Solution: Check the input parameter.
+
+GAUSS-03053: "function 'dist_lb' not implemented"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03054: "function 'close_lb' not implemented"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03056: "invalid input syntax for type polygon: '%s'"
+
+SQLSTATE: 22P02
+
+Description: Failed to parse the input value of the polygon type.
+
+Solution: Check the input parameter. The input parameter must be a string separated by commas (,) in the format of **(***a***,***b***)**.
+
+GAUSS-03057: "invalid number of points in external 'polygon' value"
+
+SQLSTATE: 22P03
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03058: "function 'poly_distance' not implemented"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03059: "function 'path_center' not implemented"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03060: "open path cannot be converted to polygon"
+
+SQLSTATE: 22023
+
+Description: A non-returned path cannot be converted to a polygon.
+
+Solution: Ensure that the input path is a returned path.
+
+<br/>
+
+## GAUSS-03061 - GAUSS-03070
+
+<br/>
+
+GAUSS-03061: "invalid input syntax for type circle: '%s'"
+
+SQLSTATE: 22P02
+
+Description: The value of the circle type is invalid.
+
+Solution: Check the input parameter.
+
+GAUSS-03062: "could not format 'circle' value"
+
+SQLSTATE: 22023
+
+Description: The input value of the circle type cannot construct the circle type data.
+
+Solution: No solution is provided (This error does not occur).
+
+GAUSS-03063: "invalid radius in external 'circle' value"
+
+SQLSTATE: 22P03
+
+Description: The input circle radius is smaller than 0.
+
+Solution: Ensure that the input circle value is valid.
+
+GAUSS-03064: "cannot convert circle with radius zero to polygon"
+
+SQLSTATE: 0A000
+
+Description: The circle whose radius is 0 cannot be converted to a polygon.
+
+Solution: Ensure that the input circle value is valid.
+
+GAUSS-03065: "must request at least 2 points"
+
+SQLSTATE: 22023
+
+Description: The number of output points must be at least 2.
+
+Solution: Check the input number of points.
+
+GAUSS-03066: "cannot convert empty polygon to circle"
+
+SQLSTATE: 22023
+
+Description: A polygon without point sets cannot be converted to a circle type value.
+
+Solution: Ensure that the input polygon value is valid.
+
+GAUSS-03067: "NULL pointer"
+
+SQLSTATE: XX005
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03068: "value '%s' is out of range for type integer"
+
+SQLSTATE: 22003
+
+Description: The parameter value is out of the range of the integer type value.
+
+Solution: Check the input parameter. For the data value range, see en-us_topic_0237121926.html.
+
+GAUSS-03069: "value '%s' is out of range for type smallint"
+
+SQLSTATE: 22003
+
+Description: The parameter value is out of the range of the smallint type value.
+
+Solution: Check the input parameter. For the data value range, see en-us_topic_0237121926.html.
+
+GAUSS-03070: "value '%s' is out of range for 8-bit integer"
+
+SQLSTATE: 22003
+
+Description: The parameter value is out of the range of the eight-digit integer type value.
+
+Solution: Check the input parameter. For the data value range, see en-us_topic_0237121926.html.
+
+<br/>
+
+## GAUSS-03071 - GAUSS-03080
+
+<br/>
+
+GAUSS-03071: "unsupported result size: %d"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03072: "invalid regular expression: %s"
+
+SQLSTATE: 2201B
+
+Description: The input expression is invalid.
+
+Solution: Check the database encoding.
+
+GAUSS-03073: "invalid regexp option: '%c'"
+
+SQLSTATE: 22023
+
+Description: The regexp conversion type is invalid.
+
+Solution: Check the input parameter.
+
+GAUSS-03074: "invalid escape string"
+
+SQLSTATE: 22025
+
+Description: The escape character is invalid.
+
+Solution: Check the input parameter.
+
+GAUSS-03075: "regexp_split does not support the global option"
+
+SQLSTATE: 22023
+
+Description:**regexp_split** currently does not support the global option.
+
+Solution: Modify the split option.
+
+GAUSS-03076: "invalid match ending position"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03077: "invalid match starting position"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03078: "unexpected dtype %d while parsing abstime '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03079: "cannot convert abstime 'invalid' to timestamp"
+
+SQLSTATE: 0A000
+
+Description: The value of absolute time is invalid and cannot be converted to the timestamp type.
+
+Solution: Check the input parameter. For the data value range, see en-us_topic_0237121926.html.
+
+GAUSS-03080: "unexpected dtype %d while parsing reltime '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03081 - GAUSS-03090
+
+<br/>
+
+GAUSS-03081: "invalid status in external 'tinterval' value"
+
+SQLSTATE: 22P03
+
+Description: The interval error status obtained in the entered string is inconsistent with the data status.
+
+Solution: Check the input strings.
+
+GAUSS-03082: "cannot convert reltime 'invalid' to interval"
+
+SQLSTATE: 0A000
+
+Description: The value of the reltime type is invalid and cannot be converted to the interval type.
+
+Solution: Check the input parameter.
+
+GAUSS-03083: "invalid input syntax for type tinterval: '%s'"
+
+SQLSTATE: 22007
+
+Description: A syntax error occurs when the input string is converted to the tinterval type.
+
+Solution: Check the input strings.
+
+GAUSS-03084: "invalid input syntax for type boolean: '%s'"
+
+SQLSTATE: 22P02
+
+Description: A syntax error occurs when the input string is converted to the Boolean type.
+
+Solution: Check the input strings.
+
+GAUSS-03085: "missing dimension value"
+
+SQLSTATE: 22P02
+
+Description: The array dimension is not specified.
+
+Solution: Check the input strings.
+
+GAUSS-03086: "missing ']' in array dimensions"
+
+SQLSTATE: 22P02
+
+Description: A right bracket (]) is missing when the array dimension is specified.
+
+Solution: Check the input strings.
+
+GAUSS-03087: "upper bound cannot be less than lower bound"
+
+SQLSTATE: 2202E
+
+Description: The upper limit of the array cannot be less than the lower limit.
+
+Solution: Check the input strings.
+
+GAUSS-03088: "array value must start with '{' or dimension information"
+
+SQLSTATE: 22P02
+
+Description: The array string must start with a left brace ({) or dimension information.
+
+Solution: Check the input strings.
+
+GAUSS-03089: "missing assignment operator"
+
+SQLSTATE: 22P02
+
+Description: If the array dimension information is specified, the **=** operator must be provided.
+
+Solution: Check the input strings.
+
+GAUSS-03090: "array dimensions incompatible with array literal"
+
+SQLSTATE: 22P02
+
+Description: The array dimension is inconsistent with the array data.
+
+Solution: Check the input strings.
+
+<br/>
+
+## GAUSS-03091 - GAUSS-03100
+
+<br/>
+
+GAUSS-03091: "malformed array literal: '%s'"
+
+SQLSTATE: 22P02
+
+Description: The data format of the input array is incorrect.
+
+Solution: Check whether the input string can be converted to an array constant.
+
+GAUSS-03092: "multidimensional arrays must have array expressions with matching dimensions"
+
+SQLSTATE: 22P02
+
+Description: Multi-dimensional arrays must be provided with dimension-matching expressions.
+
+Solution: Check the input strings.
+
+GAUSS-03093: "array size exceeds the maximum allowed (%d)"
+
+SQLSTATE: 54000
+
+Description: The array length exceeds the maximum.
+
+Solution: Ensure that the number of array elements in the input string does not exceed the value specified in the error information.
+
+GAUSS-03095: "invalid number of dimensions: %d"
+
+SQLSTATE: 22P03
+
+Description: The array dimension is less than zero.
+
+Solution: Check the input parameter.
+
+GAUSS-03096: "invalid array flags"
+
+SQLSTATE: 22P03
+
+Description: The array flag is invalid. The value can only be **0** or **1**.
+
+Solution: Check the input parameter.
+
+GAUSS-03097: "wrong element type"
+
+SQLSTATE: 42804
+
+Description: Types of the array elements are inconsistent.
+
+Solution: Check the input parameter.
+
+GAUSS-03098: "insufficient data left in message"
+
+SQLSTATE: 22P03
+
+Description: The remaining length of the message is smaller than the length obtained from the message.
+
+Solution: Check the current string.
+
+GAUSS-03099: "improper binary format in array element %d"
+
+SQLSTATE: 22P03
+
+Description: When the array is read, there is still data in the buffer.
+
+Solution: Check the input data.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/32-GAUSS-03101-GAUSS-03200.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/32-GAUSS-03101-GAUSS-03200.md
new file mode 100644
index 0000000000000000000000000000000000000000..eea659344f02061b25a6a6b829625d36aa84bf8b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/32-GAUSS-03101-GAUSS-03200.md
@@ -0,0 +1,828 @@
+---
+title: GAUSS-03101 - GAUSS-03200
+summary: GAUSS-03101 - GAUSS-03200
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-03101 - GAUSS-03200
+
+<br/>
+
+## GAUSS-03101 - GAUSS-03110
+
+<br/>
+
+GAUSS-03101: "wrong number of array subscripts"
+
+SQLSTATE: 2202E
+
+Description: The array using variable-length elements must be one-dimensional. An error occurs when you replace array elements with variable-length elements of a multiple-dimensional array.
+
+Solution: Check the input parameter.
+
+GAUSS-03102: "array subscript out of range"
+
+SQLSTATE: 2202E
+
+Description: The one-dimensional index value exceeds the value range allowed for the elements contained in the array.
+
+Solution: Check the input parameter.
+
+GAUSS-03103: "cannot assign null value to an element of a fixed-length array"
+
+SQLSTATE: 22004
+
+Description:**NULL** value cannot be assigned to an element of a fixed-length array.
+
+Solution: Check the input parameter.
+
+GAUSS-03104: "updates on slices of fixed-length arrays not implemented"
+
+SQLSTATE: 0A000
+
+Description: Updates are not supported on arrays that use fixed-length elements.
+
+Solution: Check the input parameter.
+
+GAUSS-03105: "source array too small"
+
+SQLSTATE: 2202E
+
+Description: There is no element of the index number to be replaced in the source array.
+
+Solution: Check the input parameter.
+
+GAUSS-03106: "invalid nargs: %d"
+
+SQLSTATE: XX000
+
+Description: The array parameters are invalid.
+
+Solution: Modify the array parameters in the query.
+
+GAUSS-03107: "null input array"
+
+SQLSTATE: XX000
+
+Description: The array does not contain parameters.
+
+Solution: Add valid parameters to the array.
+
+GAUSS-03108: "null array element not allowed in this context"
+
+SQLSTATE: 22004
+
+Description: If the current array element flag is not **NULL**, the value of the array element cannot be **NULL**.
+
+Solution: Check the input parameter.
+
+GAUSS-03110: "invalid arguments to array_create_iterator"
+
+SQLSTATE: XX000
+
+Description: The parameter of the **array_create_iterator** function is invalid.
+
+Solution: Modify the parameter of the **array_create_iterator** function.
+
+<br/>
+
+## GAUSS-03111 - GAUSS-03120
+
+<br/>
+
+GAUSS-03111: "dimension array or low bound array cannot be null"
+
+SQLSTATE: 22004
+
+Description: The array dimension and filled subscript cannot be **NULL**.
+
+Solution: Check the input parameter.
+
+GAUSS-03112: "could not determine data type of input"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03113: "wrong range of array subscripts"
+
+SQLSTATE: 2202E
+
+Description: The lower limit of the array dimension must be 1.
+
+Solution: Check the input parameter.
+
+GAUSS-03114: "dimension values cannot be null"
+
+SQLSTATE: 22004
+
+Description: Array dimension values cannot be **NULL**.
+
+Solution: Check the input parameter.
+
+GAUSS-03115: "unrecognized encoding: '%s'"
+
+SQLSTATE: 22023
+
+Description: Failed to find the encoding corresponding to the current string.
+
+Solution: Check the input strings.
+
+GAUSS-03116: "overflow - encode estimate too small"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03117: "overflow - decode estimate too small"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03118: "invalid hexadecimal digit: '%c'"
+
+SQLSTATE: 22023
+
+Description: Hexadecimal characters are invalid.
+
+Solution: Check the input parameter. For the data value range, see en-us_topic_0237121926.html.
+
+GAUSS-03119: "invalid hexadecimal data: odd number of digits"
+
+SQLSTATE: 22023
+
+Description: The number of digits of the converted hexadecimal characters is an odd number, which is invalid.
+
+Solution: Check the input parameter.
+
+GAUSS-03120: "unexpected '='"
+
+SQLSTATE: 22023
+
+Description: The equal sign (=) exists.
+
+Solution: Check the input parameter.
+
+<br/>
+
+## GAUSS-03121 - GAUSS-03130
+
+<br/>
+
+GAUSS-03121: "invalid symbol"
+
+SQLSTATE: 22023
+
+Description: The input character is invalid.
+
+Solution: Check the input parameter.
+
+GAUSS-03122: "invalid end sequence"
+
+SQLSTATE: 22023
+
+Description: The string parsing is incomplete.
+
+Solution: Check the input parameter.
+
+GAUSS-03123: "'char' out of range"
+
+SQLSTATE: 22003
+
+Description: Overflows occur when int4 is converted to char.
+
+Solution: Check the input parameter. For the data value range, see en-us_topic_0237121926.html.
+
+GAUSS-03124: "invalid input syntax for type oid: '%s'"
+
+SQLSTATE: 22P02
+
+Description: A syntax error occurs when the input string is converted to the OID type.
+
+Solution: Check the input parameter.
+
+GAUSS-03125: "value '%s' is out of range for type oid"
+
+SQLSTATE: 22003
+
+Description: The value is out of the OID value range.
+
+Solution: Check the input parameter.
+
+GAUSS-03126: "oidvector has too many elements"
+
+SQLSTATE: 22023
+
+Description: The OID array has too many element values.
+
+Solution: A maximum of 666 values are supported.
+
+GAUSS-03127: "invalid oidvector data"
+
+SQLSTATE: 22P03
+
+Description: The type of the elements in the OID array is not OID.
+
+Solution: Check the input parameter.
+
+GAUSS-03129: "typmod array must be type cstring[]"
+
+SQLSTATE: 2202E
+
+Description: The type of the array processed in the current function must be cstring.
+
+Solution: Check the element type of the array.
+
+GAUSS-03130: "typmod array must be one-dimensional"
+
+SQLSTATE: 2202E
+
+Description: The array processed by the current function must be one-dimensional.
+
+Solution: Check the array dimension.
+
+<br/>
+
+## GAUSS-03131 - GAUSS-03140
+
+<br/>
+
+GAUSS-03131: "typmod array must not contain nulls"
+
+SQLSTATE: 22004
+
+Description: The array element processed by the current function cannot be **NULL**.
+
+Solution: Ensure that the array elements are not **NULL**.
+
+GAUSS-03132: "unrecognized key word: '%s'"
+
+SQLSTATE: 22P02
+
+Description: The keyword of ACL can only be **group** or **user**.
+
+Solution: Check whether the ACL keyword is correct.
+
+GAUSS-03133: "missing name"
+
+SQLSTATE: 22P02
+
+Description: The keyword **group** or **user** does not have a name following them.
+
+Solution: Ensure that the ACL syntax is correct.
+
+GAUSS-03134: "missing '=' sign"
+
+SQLSTATE: 22P02
+
+Description: The equal sign (=) used for permission assignment for the group or user is missing.
+
+Solution: Ensure that the ACL syntax is correct.
+
+GAUSS-03135: "invalid mode character: must be one of '%s'"
+
+SQLSTATE: 22P02
+
+Description: The permission mode is invalid. The permission mode must be one of **arwdDxtXUCTc**.
+
+Solution: Ensure that the ACL syntax is correct.
+
+GAUSS-03136: "a name must follow the '/' sign"
+
+SQLSTATE: 22P02
+
+Description: To return the permission to a system administrator, a name must be specified after the slash (/).
+
+Solution: Ensure that the ACL syntax is correct.
+
+GAUSS-03137: "invalid size: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03138: "ACL array contains wrong data type"
+
+SQLSTATE: 22023
+
+Description: The ACL array contains non-ACL elements.
+
+Solution: Ensure that the ACL array is valid.
+
+GAUSS-03139: "ACL arrays must be one-dimensional"
+
+SQLSTATE: 22023
+
+Description: The ACL array can only be one-dimensional.
+
+Solution: Ensure that the ACL array is valid.
+
+GAUSS-03140: "ACL arrays must not contain null values"
+
+SQLSTATE: 22004
+
+Description: The ACL array cannot contain **NULL**.
+
+Solution: Ensure that the ACL array is valid.
+
+<br/>
+
+## GAUSS-03141 - GAUSS-03150
+
+<br/>
+
+GAUSS-03141: "extra garbage at the end of the ACL specification"
+
+SQLSTATE: 22P02
+
+Description: Extra strings are left after the string to be converted to the ACL array is parsed.
+
+Solution: Check the input strings.
+
+GAUSS-03142: "unrecognized objtype abbreviation: %c"
+
+SQLSTATE: XX000
+
+Description: The input parameter of the **acldefault** function is incorrect.
+
+Solution: Do not manually call the **acldefault** function or modify the first input parameter of the function.
+
+GAUSS-03143: "grant options cannot be granted back to your own grantor"
+
+SQLSTATE: 0LP01
+
+Description: The permission is granted back to the original grantor.
+
+Solution: Check the ACL rules.
+
+GAUSS-03144: "dependent privileges exist"
+
+SQLSTATE: 2BP01
+
+Description: The permission to be deleted has dependency permissions.
+
+Solution: Use the **cascade** keyword for cascading delete.
+
+GAUSS-03145: "null ACL"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03146: "aclinsert is no longer supported"
+
+SQLSTATE: 0A000
+
+Description: The **aclinsert** function cannot be used.
+
+Solution: Do not manually call the **aclinsert** function.
+
+GAUSS-03147: "aclremove is no longer supported"
+
+SQLSTATE: 0A000
+
+Description: The **aclremove** function cannot be used.
+
+Solution: Do not manually call the **aclremove** function.
+
+GAUSS-03148: "unrecognized privilege type: '%s'"
+
+SQLSTATE: 22023
+
+Description: The parameters of the **makeaclitem** function are incorrect.
+
+Solution: Do not manually call the **makeaclitem** function or modify the third parameter of the function.
+
+GAUSS-03149: "unrecognized aclright: %d"
+
+SQLSTATE: XX000
+
+Description: The parameters of the **aclexplode** function are incorrect.
+
+Solution: Do not manually call the **aclexplode** function or modify its parameter.
+
+GAUSS-03150: "function '%s' does not exist"
+
+SQLSTATE: 42883
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03151 - GAUSS-03160
+
+<br/>
+
+GAUSS-03151: "must be member of role '%s'"
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03152: "int2vector has too many elements"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03153: "invalid int2vector data"
+
+SQLSTATE: 22P03
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03156: "gin_tsquery_consistent requires eight arguments"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03157: "patternsel called for operator without a negator"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03158: "unrecognized consttype: %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03159: "join operator should take two arguments"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03161 - GAUSS-03170
+
+<br/>
+
+GAUSS-03161: "found unexpected null value in index '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03162: "could not find RelOptInfo for given relids"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03163: "case insensitive matching not supported on type bytea"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03164: "could not determine which collation to use for ILIKE"
+
+SQLSTATE: 42P22
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03165: "regular-expression matching not supported on type bytea"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03166: "unrecognized ptype: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03167: "missing support function %d for attribute %d of index '%s'"
+
+SQLSTATE: XX000
+
+Description: Certain operations cannot be performed to index columns.
+
+Solution:Contact technical support.
+
+GAUSS-03168: "could not match index to operand"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03169: "unsupported GIN indexqual type: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03170: "invalid input value for enum %s: '%s'"
+
+SQLSTATE: 22P02
+
+Description: The input of **enum** is invalid.
+
+Solution: Modify the input of **enum**.
+
+<br/>
+
+## GAUSS-03171 - GAUSS-03180
+
+<br/>
+
+GAUSS-03171: "invalid internal value for enum: %u"
+
+SQLSTATE: 22P03
+
+Description: The **enum** parameter is invalid.
+
+Solution: Modify the **enum** parameter.
+
+GAUSS-03172: "invalid argument for enum_recv"
+
+SQLSTATE: XX000
+
+Description: The **enum_recv** parameter is invalid.
+
+Solution: Modify the **enum_recv** parameter.
+
+GAUSS-03173: "could not determine actual enum type"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03174: "enum %s contains no values"
+
+SQLSTATE: 55000
+
+Description: No value is assigned to **enum**.
+
+Solution: Assign a value to **enum**.
+
+GAUSS-03175: "could not open tablespace directory '%s': %m"
+
+SQLSTATE: XX000
+
+Description: Failed to open the tablespace path.
+
+Solution: Check whether the path corresponding to the tablespace is damaged.
+
+GAUSS-03176: "Parameter value should not be negative."
+
+SQLSTATE: 22023
+
+Description: The parameter value cannot be negative.
+
+Solution: Set the parameter to a positive value.
+
+GAUSS-03177: "tablespace with OID %u does not exist"
+
+SQLSTATE: XX000
+
+Description: The result of checking user access rights in the user exit program indicates that the corresponding tablespace does not exist.
+
+Solution: Check whether the **pg_tablespace** system catalog contains the tablespace definition.
+
+GAUSS-03178: "database with OID %u does not exist"
+
+SQLSTATE: XX000
+
+Description: The result of checking user access rights indicates that the corresponding database does not exist.
+
+Solution: Check whether the database status in the **pg_database** system catalog is normal.
+
+GAUSS-03179: "SPI connect failure - returned %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03180: "failed to execute query '%s' on node '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03181 - GAUSS-03190
+
+<br/>
+
+GAUSS-03181: "array of weight must be one-dimensional"
+
+SQLSTATE: 2202E
+
+Description: The array of the first parameter of the **ts_rank_wtt** function is not a one-dimensional array.
+
+Solution: Set the first parameter of the **ts_rank_wtt** function to a one-dimensional array.
+
+GAUSS-03182: "array of weight is too short"
+
+SQLSTATE: 2202E
+
+Description: Among the parameters of the **ts_rank_wtt** function, the number of elements in a one-dimensional array is smaller than 4.
+
+Solution: Ensure that the number of elements in the one-dimensional array is greater than or equal to 4.
+
+GAUSS-03183: "array of weight must not contain nulls"
+
+SQLSTATE: 22004
+
+Description: The array elements of the first parameter of the **ts_rank_wtt** function contain **NULL** values.
+
+Solution: Do not set **NULL** values for the array elements.
+
+GAUSS-03184: "weight out of range"
+
+SQLSTATE: 22023
+
+Description: The array tuple of the first parameter of the **ts_rank_wtt** function is greater than 1.0.
+
+Solution: Do not set the array tuple to a value greater than 1.
+
+GAUSS-03185: "more than one function named '%s'"
+
+SQLSTATE: 42725
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03186: "more than one operator named %s"
+
+SQLSTATE: 42725
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03187: "missing argument"
+
+SQLSTATE: 42601
+
+Description: The parameter is missing when an operator is deleted.
+
+Solution: Use the parameter defined for an operator when deleting the operator.
+
+GAUSS-03188: "too many arguments"
+
+SQLSTATE: 54023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03189: "expected a left parenthesis"
+
+SQLSTATE: 22P02
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03190: "expected a right parenthesis"
+
+SQLSTATE: 22P02
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03191 - GAUSS-03200
+
+<br/>
+
+GAUSS-03191: "expected a type name"
+
+SQLSTATE: 22P02
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03192: "improper type name"
+
+SQLSTATE: 22P02
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03193: "input of anonymous composite types is not implemented"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03194: "malformed record literal: '%s'"
+
+SQLSTATE: 22P02
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03195: "wrong number of columns: %d, expected %d"
+
+SQLSTATE: 42804
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03196: "wrong data type: %u, expected %u"
+
+SQLSTATE: 42804
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03197: "improper binary format in record column %d"
+
+SQLSTATE: 22P03
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03198: "cannot compare dissimilar column types %s and %s at record column %d"
+
+SQLSTATE: 42804
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03199: "cannot compare record types with different numbers of columns"
+
+SQLSTATE: 42804
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03200: "invalid input syntax for type tid: '%s'"
+
+SQLSTATE: 22P02
+
+Description:Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/33-GAUSS-03201-GAUSS-03300.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/33-GAUSS-03201-GAUSS-03300.md
new file mode 100644
index 0000000000000000000000000000000000000000..8e4a70685775538a3913b11ceb8f5d4fa509eb7c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/33-GAUSS-03201-GAUSS-03300.md
@@ -0,0 +1,820 @@
+---
+title: GAUSS-03201 - GAUSS-03300
+summary: GAUSS-03201 - GAUSS-03300
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-03201 - GAUSS-03300
+
+<br/>
+
+## GAUSS-03201 - GAUSS-03210
+
+<br/>
+
+GAUSS-03201: "ctid isn't of type TID"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03202: "currtid cannot handle views with no CTID"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03203: "the view has no rules"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03204: "only one select rule is allowed in views"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03205: "currtid cannot handle this view"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03206: "no operand in tsquery: '%s'"
+
+SQLSTATE: 42601
+
+Description: In the **tsquery** string, no variable follows the operator.
+
+Solution: Check the string to ensure that each operator is followed by an object.
+
+GAUSS-03207: "value is too big in tsquery: '%s'"
+
+SQLSTATE: 54000
+
+Description: In the **tsquery** string, the length of the string following an operator exceeds the limit (1<<20) - 1.
+
+Solution: Ensure that the length of the string does not exceed the upper limit.
+
+GAUSS-03208: "operand is too long in tsquery: '%s'"
+
+SQLSTATE: 54000
+
+Description: In the **tsquery** string, the length of a string exceeds the limit (1<<11) - 1.
+
+Solution: Ensure that the length of the string does not exceed the upper limit.
+
+GAUSS-03209: "word is too long in tsquery: '%s'"
+
+SQLSTATE: 54000
+
+Description: In the **tsquery** string, the length of a string exceeds the limit (1<<11) - 1.
+
+Solution: Ensure that the length of the string does not exceed the upper limit.
+
+GAUSS-03210: "tsquery stack too small"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03211 - GAUSS-03220
+
+<br/>
+
+GAUSS-03211: "malformed tsquery: operand not found"
+
+SQLSTATE: XX000
+
+Description: No operator is found in the string of the tsquery type.
+
+Solution: Check the input and ensure that the variable of the tsquery type contains an operator.
+
+GAUSS-03212: "malformed tsquery: extra nodes"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03213: "unrecognized operator type: %d"
+
+SQLSTATE: XX000
+
+Description: An incorrect operator is entered.
+
+Solution: Use only !, |, or & as the input operator.
+
+GAUSS-03214: "unrecognized tsquery node type: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03215: "invalid size of tsquery"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03216: "invalid tsquery: invalid weight bitmap"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03218: "invalid tsquery: total operand length exceeded"
+
+SQLSTATE: XX000
+
+Description: The string of the tsquery type exceeds the upper limit (1<<20) - 1.
+
+Solution: Ensure that the length of the string does not exceed the upper limit.
+
+GAUSS-03219: "invalid tsquery: unrecognized operator type %d"
+
+SQLSTATE: XX000
+
+Description: An incorrect operator is entered.
+
+Solution: Ensure that the operator uses one of the following characters: ! | &.
+
+<br/>
+
+## GAUSS-03221 - GAUSS-03230
+
+<br/>
+
+GAUSS-03221: "cannot accept a value of type any"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03222: "cannot display a value of type any"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03223: "cannot accept a value of type anyarray"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03224: "cannot accept a value of type anyenum"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03225: "cannot accept a value of type anyrange"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03226: "cannot accept a value of type trigger"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03227: "cannot display a value of type trigger"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03228: "cannot accept a value of type language_handler"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03229: "cannot display a value of type language_handler"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03230: "cannot accept a value of type fdw_handler"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03231 - GAUSS-03240
+
+<br/>
+
+GAUSS-03231: "cannot display a value of type fdw_handler"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03232: "cannot accept a value of type internal"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03233: "cannot display a value of type internal"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03234: "cannot accept a value of type opaque"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03235: "cannot display a value of type opaque"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03236: "cannot accept a value of type anyelement"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03237: "cannot display a value of type anyelement"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03238: "cannot accept a value of type anynonarray"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03239: "cannot display a value of type anynonarray"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03240: "cannot accept a value of a shell type"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03241 - GAUSS-03250
+
+<br/>
+
+GAUSS-03241: "cannot display a value of a shell type"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03242: "cannot accept a value of type pg_node_tree"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03243: "TIME(%d)%s precision must not be negative"
+
+SQLSTATE: 22023
+
+Description: The time format precision cannot be negative.
+
+Solution: Set the time format precision to positive.
+
+GAUSS-03244: "date/time value 'current' is no longer supported"
+
+SQLSTATE: 0A000
+
+Description: The **current** value is invalid.
+
+Solution: Do not use the **current** value.
+
+GAUSS-03245: "date out of range: '%s'"
+
+SQLSTATE: 22008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03246: "date out of range"
+
+SQLSTATE: 22008
+
+Description: The date exceeds the limit.
+
+Solution: Change the date to a valid value.
+
+GAUSS-03248: "cannot subtract infinite dates"
+
+SQLSTATE: 22008
+
+Description: The date does not have a start or end.
+
+Solution: Change the date to a valid value.
+
+GAUSS-03249: "date out of range for timestamp"
+
+SQLSTATE: 22008
+
+Description: The date exceeds the timestamp range.
+
+Solution: Change the date to a valid value.
+
+GAUSS-03250: "cannot convert reserved abstime value to date"
+
+SQLSTATE: 0A000
+
+Description: The absolute time cannot be converted to the required time format.
+
+Solution: Change the date format to a valid value.
+
+<br/>
+
+## GAUSS-03251 - GAUSS-03260
+
+<br/>
+
+GAUSS-03251: "time out of range"
+
+SQLSTATE: 22008
+
+Description: Out of range.
+
+Solution: Check the original data.
+
+GAUSS-03252: "'time' units '%s' not recognized"
+
+SQLSTATE: 22023
+
+Description: The SQL parameter is incorrect.
+
+Solution: Modify the SQL statement.
+
+GAUSS-03253: "time zone displacement out of range"
+
+SQLSTATE: 22009
+
+Description: Out of range.
+
+Solution: Check the original data.
+
+GAUSS-03254: "'time with time zone' units '%s' not recognized"
+
+SQLSTATE: 22023
+
+Description: The SQL parameter is incorrect.
+
+Solution: Modify the SQL statement.
+
+GAUSS-03255: "'interval' time zone '%s' not valid"
+
+SQLSTATE: 22023
+
+Description: Data is invalid.
+
+Solution: Check the original data.
+
+GAUSS-03256: "compressed data is corrupt"
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03257: "value too long for type character(%d)"
+
+SQLSTATE: 22001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03258: "value too long for type character varying(%d)"
+
+SQLSTATE: 22001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03259: "value too long for type nvarchar2(%d)"
+
+SQLSTATE: 22001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03260: "SPI_prepare failed for '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03261 - GAUSS-03270
+
+<br/>
+
+GAUSS-03261: "failed to get pg_rewrite tuple for rule %u"
+
+SQLSTATE: SP005
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03262: "failed to get pg_rewrite tuple for view %u"
+
+SQLSTATE: SP005
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03264: "tgargs is null for trigger %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03265: "unrecognized confmatchtype: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03266: "unrecognized confupdtype: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03267: "unrecognized confdeltype: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03268: "invalid constraint type '%c'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03269: "Deparse of this query at planning is not supported yet"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03270: "Deparse of this query at planning not supported yet"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03271 - GAUSS-03280
+
+<br/>
+
+GAUSS-03271: "rule '%s' has unsupported event type %d"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03272: "unrecognized query command type: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03273: "too many subquery RTEs in INSERT"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03274: "too many values RTEs in INSERT"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03275: "both subquery and values RTEs in INSERT"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03278: "Invalid distribution type"
+
+SQLSTATE: 42000
+
+Description: The system does not support the specified distribution type.
+
+Solution: Ensure that the distribution type in use is supported by the system.
+
+GAUSS-03279: "unexpected utility statement type"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03280: "bogus varlevelsup: %d offset %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03281 - GAUSS-03290
+
+<br/>
+
+GAUSS-03281: "bogus varattno for OUTER_VAR var: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03282: "bogus varattno for INNER_VAR var: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03283: "bogus varattno for INDEX_VAR var: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03284: "bogus varno: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03285: "bogus varattno for subquery var: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03286: "bogus varattno for remotequery var: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03287: "cannot decompile join alias var in plan tree"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03288: "failed to find plan for subquery %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03289: "failed to find plan for CTE %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03290: "bogus oprkind: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03291 - GAUSS-03300
+
+<br/>
+
+GAUSS-03291: "could not find window clause for winref %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03292: "unrecognized sublink type: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03293: "argument type %s of FieldStore is not a tuple type"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03294: "unrecognized oprkind: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03295: "date/time field value out of range: '%s'"
+
+SQLSTATE: 22008
+
+Description: The value of the **date/time** field is out of range. For example, the month value should range from 1 to 12.
+
+Solution: Correct the input value.
+
+GAUSS-03296: "interval field value out of range: '%s'"
+
+SQLSTATE: 22015
+
+Description: The value of the **interval** field is out of range.
+
+Solution: Correct the input value.
+
+GAUSS-03297: "time zone displacement out of range: '%s'"
+
+SQLSTATE: 22009
+
+Description: The value of the **time zone displacement** field is out of range.
+
+Solution: Correct the input value.
+
+GAUSS-03298: "invalid input syntax for type %s: '%s'"
+
+SQLSTATE: 22007
+
+Description: The network address is invalid.
+
+Solution: Check whether the format of the entered network address is correct.
+
+GAUSS-03299: "only system admin can lock the cluster for backup"
+
+SQLSTATE: 42501
+
+Description: Only system administrators have the permission to lock the cluster for backup.
+
+Solution: Perform this operation as a system administrator.
+
+GAUSS-03300: "internal error while locking the cluster for backup"
+
+SQLSTATE: 08000
+
+Description: An error occurs when the cluster is locked for backup.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/34-GAUSS-03301-GAUSS-03400.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/34-GAUSS-03301-GAUSS-03400.md
new file mode 100644
index 0000000000000000000000000000000000000000..89688f61d3d97cab011715f0846a006ae05b6678
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/34-GAUSS-03301-GAUSS-03400.md
@@ -0,0 +1,828 @@
+---
+title: GAUSS-03301 - GAUSS-03400
+summary: GAUSS-03301 - GAUSS-03400
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-03301 - GAUSS-03400
+
+<br/>
+
+## GAUSS-03301 - GAUSS-03310
+
+<br/>
+
+GAUSS-03301: "cannot lock cluster for backup in presence of %d uncommitted prepared transactions"
+
+SQLSTATE: 55P03
+
+Description: The cluster cannot be locked for backup when prepared transactions are uncommitted.
+
+Solution: Lock the cluster for backup after prepared transactions are committed.
+
+GAUSS-03302: "cannot lock cluster for backup, lock is already held"
+
+SQLSTATE: 55P03
+
+Description: The cluster cannot be locked for backup because the lock is not obtained.
+
+Solution: Lock the cluster for backup after the relevant locked resources are released.
+
+GAUSS-03304: "word is too long (%ld bytes, max %ld bytes)"
+
+SQLSTATE: 54000
+
+Description: The word exceeds the maximum length.
+
+Solution: Use a word within the allowed length.
+
+GAUSS-03305: "string is too long for tsvector (%ld bytes, max %ld bytes)"
+
+SQLSTATE: 54000
+
+Description: The string exceeds the maximum length.
+
+Solution: Use a string within the allowed length.
+
+GAUSS-03306: "positions array too long"
+
+SQLSTATE: XX000
+
+Description: The entered string length exceeds the maximum length allowed by the tsvector type (1<<20) - 1.
+
+Solution: Shorten the string.
+
+GAUSS-03307: "invalid size of tsvector"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03308: "invalid tsvector: lexeme too long"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03309: "invalid tsvector: maximum total lexeme length exceeded"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03311 - GAUSS-03320
+
+<br/>
+
+GAUSS-03311: "position information is misordered"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03312: "unrecognized LC category: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03313: "could not convert string to UTF-8: error code %lu"
+
+SQLSTATE: 22021
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03314: "invalid LC_COLLATE setting"
+
+SQLSTATE: D0011
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03315: "invalid LC_CTYPE setting"
+
+SQLSTATE: D0011
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03316: "could not create locale '%s': %m"
+
+SQLSTATE: 22023
+
+Description: The locale cannot be created because the OS cannot find the specified locale name.
+
+Solution: Ensure that the created locale is supported by the OS.
+
+GAUSS-03317: "collations with different collate and ctype values are not supported on this platform"
+
+SQLSTATE: 0A000
+
+Description: The current OS does not support collations with different collate and ctype values.
+
+Solution: The sorting rules of data in each column can be specified. When a collation is created, ensure that the values of **LC_COLLATE** and **LC_CTYPE** are the same.
+
+GAUSS-03318: "nondefault collations are not supported on this platform"
+
+SQLSTATE: 0A000
+
+Description: Non-default collations are not supported.
+
+Solution: Ensure that the default collation is used on this platform.
+
+GAUSS-03319: "wcstombs_l is not available"
+
+SQLSTATE: 22021
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03320: "mbstowcs_l is not available"
+
+SQLSTATE: 22021
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03321 - GAUSS-03330
+
+<br/>
+
+GAUSS-03321: "invalid multibyte character for locale"
+
+SQLSTATE: 22021
+
+Description: The character to be converted is a multi-byte character. The locale specified by **LC_CTYPE locale** on the server is incompatible with the encoding of the database.
+
+Solution: Change the server locale.
+
+GAUSS-03322: "unsupported XML feature"
+
+SQLSTATE: 0A000
+
+Description: The XML feature is not supported.
+
+Solution: Do not use XML feature-related functions.
+
+GAUSS-03323: "invalid XML comment"
+
+SQLSTATE: 2200S
+
+Description: The XML comment is invalid.
+
+Solution: Ensure that the XML comment format is **<- … ->**.
+
+GAUSS-03324: "not an XML document"
+
+SQLSTATE: 2200L
+
+Description: The input XML document in the **xmltotext** function is invalid.
+
+Solution: Correct the XML data.
+
+GAUSS-03325: "invalid XML processing instruction"
+
+SQLSTATE: 42601
+
+Description: The XML processing instruction (PI) is invalid. The target name should not be **xml** (case insensitive).
+
+Solution: Change the target name of PI in the XML document.
+
+GAUSS-03326: "invalid XML processing instruction"
+
+SQLSTATE: 42601
+
+Description: The XML processing instruction (PI) is invalid. The target name should not be **xml** (case insensitive).
+
+Solution: Change the target name of PI in the XML document.
+
+GAUSS-03327: "xmlvalidate is not implemented"
+
+SQLSTATE: 0A000
+
+Description: The **XMLVALIDATE** function is not implemented.
+
+Solution: Do not use the **XMLVALIDATE** function.
+
+GAUSS-03328: "could not initialize XML library"
+
+SQLSTATE: XX000
+
+Description: A system error occurs. Failed to initialize the XML library.
+
+Solution:Contact technical support.
+
+GAUSS-03329: "could not set up XML error handler"
+
+SQLSTATE: 0A000
+
+Description: A system error occurs. Failed to set the XML error handler.
+
+Solution:Contact technical support.
+
+GAUSS-03330: "xml_ereport called with invalid PgXmlErrorContext"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03331 - GAUSS-03340
+
+<br/>
+
+GAUSS-03331: "xml_errorHandler called with invalid PgXmlErrorContext"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03332: "invalid query"
+
+SQLSTATE: 22000
+
+Description: The query is invalid.
+
+Solution: Modify the query statement.
+
+GAUSS-03333: "xpath expression result type %d is unsupported"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03334: "invalid array for XML namespace mapping"
+
+SQLSTATE: 22000
+
+Description: An internal error occurs. The array for XML namespace mapping is invalid. The array must be a two-dimensional array.
+
+Solution:Contact technical support.
+
+GAUSS-03335: "empty XPath expression"
+
+SQLSTATE: 22000
+
+Description: The **Xpath** expression is empty.
+
+Solution: Provide a valid **Xpath** expression when the XML function is called.
+
+GAUSS-03336: "neither namespace name nor URI may be null"
+
+SQLSTATE: 22004
+
+Description: Either the XML namespace or the corresponding URL is **NULL**.
+
+Solution: Ensure that neither the XML namespace nor URL is **NULL**.
+
+GAUSS-03338: "LIKE pattern must not end with escape character"
+
+SQLSTATE: 22025
+
+Description: The **LIKE** pattern should not be ended with an escape character.
+
+Solution: Modify the **LIKE** pattern and ensure that it is not ended with an escape character.
+
+GAUSS-03339: "invalid format specification for an interval value"
+
+SQLSTATE: 22007
+
+Description: The input parameter cannot be the interval type when the **date/time** field is converted to char.
+
+Solution: Ensure that the input parameter is in the correct time format.
+
+GAUSS-03340: "'EEEE' must be the last pattern used"
+
+SQLSTATE: 42601
+
+Description: The numeric format is incorrect. **EEEE** should appear at the last part.
+
+Solution: Modify the value format and perform the operation again.
+
+<br/>
+
+## GAUSS-03341 - GAUSS-03350
+
+<br/>
+
+GAUSS-03341: "'9' must be ahead of 'PR'"
+
+SQLSTATE: 42601
+
+Description: The numeric format is incorrect. **9** must be ahead of **PR**.
+
+Solution: Modify the value format and perform the operation again.
+
+GAUSS-03342: "'0' must be ahead of 'PR'"
+
+SQLSTATE: 42601
+
+Description: The numeric format is incorrect. **0** must be ahead of **PR**.
+
+Solution: Modify the value format and perform the operation again.
+
+GAUSS-03343: "multiple decimal points"
+
+SQLSTATE: 42601
+
+Description: The numeric format is incorrect. Multiple decimal points are forbidden.
+
+Solution: Modify the value format and perform the operation again.
+
+GAUSS-03345: "cannot use 'S' twice"
+
+SQLSTATE: 42601
+
+Description: The numeric format is incorrect. **S** cannot be used twice.
+
+Solution:Contact technical support.
+
+GAUSS-03346: "cannot use 'S' and 'PL'/'MI'/'SG'/'PR' together"
+
+SQLSTATE: 42601
+
+Description: The numeric format is incorrect. **S** cannot be used together with **PL**, **MI**, **SG**, and **PR**.
+
+Solution: Modify the value format and perform the operation again.
+
+GAUSS-03347: "cannot use 'S' and 'MI' together"
+
+SQLSTATE: 42601
+
+Description: The numeric format is incorrect. **S** and **MI** cannot be used together.
+
+Solution: Modify the value format and perform the operation again.
+
+GAUSS-03348: "cannot use 'S' and 'PL' together"
+
+SQLSTATE: 42601
+
+Description: The numeric format is incorrect. **S** and **PL** cannot be used together.
+
+Solution: Modify the value format and perform the operation again.
+
+GAUSS-03349: "cannot use 'S' and 'SG' together"
+
+SQLSTATE: 42601
+
+Description: The numeric format is incorrect. **S** and **SG** cannot be used together.
+
+Solution: Modify the value format and perform the operation again.
+
+GAUSS-03350: "cannot use 'PR' and 'S'/'PL'/'MI'/'SG' together"
+
+SQLSTATE: 42601
+
+Description: The numeric format is incorrect. **PR** cannot be used together with **S**, **PL**, **MI**, and **SG**.
+
+Solution: Modify the value format and perform the operation again.
+
+<br/>
+
+## GAUSS-03351 - GAUSS-03360
+
+<br/>
+
+GAUSS-03351: "cannot use 'EEEE' twice"
+
+SQLSTATE: 42601
+
+Description: The numeric format is incorrect. **EEEE** cannot be used twice.
+
+Solution: Modify the value format and perform the operation again.
+
+GAUSS-03352: "'EEEE' is incompatible with other formats"
+
+SQLSTATE: 42601
+
+Description: The value format is incorrect. **EEEE** is incompatible with other formats.
+
+Solution: Modify the value format and perform the operation again.
+
+GAUSS-03353: "invalid data for match in format string"
+
+SQLSTATE: 22007
+
+Description: When the data is converted to the timestamp format, the format parameter value does not comply with the timestamp format.
+
+Solution: Modify the format string and ensure that it can correctly indicate the timestamp format. Perform the operation again.
+
+GAUSS-03354: "'%s' is not a number"
+
+SQLSTATE: 22P02
+
+Description: A numeric string should not contain non-number characters.
+
+Solution: Modify the numeric string and perform the operation again.
+
+GAUSS-03355: "could not determine which collation to use for lower() function"
+
+SQLSTATE: 42P22
+
+Description: Failed to determine the collation used for calling the **lower** function.
+
+Solution: Use the **COLLATE** clause to set the collation.
+
+GAUSS-03356: "could not determine which collation to use for upper() function"
+
+SQLSTATE: 42P22
+
+Description: Failed to determine the collation used for calling the **upper** function.
+
+Solution: Use the **COLLATE** clause to set the collation.
+
+GAUSS-03357: "could not determine which collation to use for initcap() function"
+
+SQLSTATE: 42P22
+
+Description: Failed to determine the collation used for calling the **initcap** function.
+
+Solution: Use the **COLLATE** clause to set the collation.
+
+GAUSS-03358: " RR/RRRR should be between 0 - 9999"
+
+SQLSTATE: 22008
+
+Description: The date and time format is incorrect. The year value should range between 0 and 9999.
+
+Solution: Correct the year value.
+
+GAUSS-03359: "invalid combination of date conventions"
+
+SQLSTATE: 22007
+
+Description: The date and time format is incorrect. A combination of the Gregorian calendar and ISO week date format cannot be used.
+
+Solution: Modify the date format. Use the Gregorian calendar or ISO week date.
+
+GAUSS-03360: "conflicting values for '%s' field in formatting string"
+
+SQLSTATE: 22007
+
+Description: The date and time format is incorrect. The same field is repeatedly given conflicting values.
+
+Solution: Do not set conflicting values. Cancel the second value assignment.
+
+<br/>
+
+## GAUSS-03361 - GAUSS-03370
+
+<br/>
+
+GAUSS-03361: "source string too short for '%s' formatting field"
+
+SQLSTATE: 22007
+
+Description: The date and time format is incorrect. The length of the source string must be shorter than the length to be read.
+
+Solution: Use the **FM** modifier if the source string does not have a fixed length.
+
+GAUSS-03362: "invalid value '%s' for '%s'"
+
+SQLSTATE: 22007
+
+Description: The date and time format is incorrect. Failed to parse partial characters of the string.
+
+Solution: Correct the date and time format of the string to be converted. If the string does not have a fixed length, use the **FM** modifier.
+
+GAUSS-03363: "value for '%s' in source string is out of range"
+
+SQLSTATE: 22008
+
+Description: The date and time format is incorrect. The string value is out of range.
+
+Solution: Correct the string value based on the prompt.
+
+GAUSS-03364: "character does not match format string"
+
+SQLSTATE: 22007
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03365: "input length of format 'US'/'us'/'FF'/'ff' must between 0 and 6"
+
+SQLSTATE: 22008
+
+Description: The date and time value is out of range. The length of the **US/us/FF/ff** format must range between 0 and 6.
+
+Solution: Change the format length and ensure that the format range between 0 and 6.
+
+GAUSS-03366: "'TZ'/'tz' format patterns are not supported in to_date"
+
+SQLSTATE: 0A000
+
+Description: The date in the TZ/tz format is not supported.
+
+Solution: Modify the date format.
+
+GAUSS-03367: "invalid input string for 'Y,YYY'"
+
+SQLSTATE: 22007
+
+Description: The input string fails to meet the date and time format requirements.
+
+Solution: Ensure that the input string is in the **Y,YYY** format.
+
+GAUSS-03368: "invalid data for match in date string"
+
+SQLSTATE: 22007
+
+Description: The date and time format is incorrect. The data for match in a date string is invalid.
+
+Solution: Use valid string text to query the match.
+
+GAUSS-03369: "invalid data for '%s = %d' ,value must be %s"
+
+SQLSTATE: 22008
+
+Description: The date and time format is incorrect. The input data is inconsistent with the specified value.
+
+Solution: Input the data based on the specified value.
+
+GAUSS-03370: " seconds of minute conflicts with seconds in day"
+
+SQLSTATE: 22007
+
+Description: The date and time format is incorrect. The second value of the minute conflicts with that of the day.
+
+Solution: Modify the date and time format.
+
+<br/>
+
+## GAUSS-03371 - GAUSS-03380
+
+<br/>
+
+GAUSS-03371: " minutes of hour conflicts with seconds in day"
+
+SQLSTATE: 22007
+
+Description: The date and time format is incorrect. The minute value of the hour conflicts with the second value of the day.
+
+Solution: Modify the date and time format.
+
+GAUSS-03372: "hour conflicts with seconds in day"
+
+SQLSTATE: 22007
+
+Description: The date and time format is incorrect. The hour value conflicts with the second value of the day.
+
+Solution: Modify the date and time format.
+
+GAUSS-03373: "hour '%d' is invalid for the 12-hour clock"
+
+SQLSTATE: 22007
+
+Description: The date and time format is incorrect. The hour value for the 12-hour clock is invalid.
+
+Solution: Ensure that the hour value for the 12-hour clock ranges from 1 to 12.
+
+GAUSS-03374: "inconsistent use of year %04d and 'BC'"
+
+SQLSTATE: 22007
+
+Description: The date and time format is incorrect. The BC year value must be a positive value.
+
+Solution: Correct the year value.
+
+GAUSS-03375: "year conflicts with Julian date"
+
+SQLSTATE: 22007
+
+Description: The date and time format is incorrect. The year value conflicts with the Julian date.
+
+Solution: Modify the date and time format.
+
+GAUSS-03376: "month conflicts with Julian date"
+
+SQLSTATE: 22007
+
+Description: The date and time format is incorrect. The month value conflicts with the Julian date.
+
+Solution: Modify the date and time format.
+
+GAUSS-03377: "day conflicts with Julian date"
+
+SQLSTATE: 22007
+
+Description: The date and time format is incorrect. The day value conflicts with the Julian date.
+
+Solution: Modify the date and time format.
+
+GAUSS-03378: "cannot calculate day of year without year information"
+
+SQLSTATE: 22007
+
+Description: The date and time format is incorrect. Failed to calculate days of a year because the year value is missing.
+
+Solution: Modify the date and time format.
+
+GAUSS-03379: "month conflicts with days of year"
+
+SQLSTATE: 22007
+
+Description: The date and time format is incorrect. The month value conflicts with the day value of a year.
+
+Solution: Modify the date and time format.
+
+GAUSS-03380: "days of month conflicts with days of year"
+
+SQLSTATE: 22007
+
+Description: The date and time format is incorrect. The day value of a month conflicts with that of a year.
+
+Solution: Modify the date and time format.
+
+<br/>
+
+## GAUSS-03381 - GAUSS-03390
+
+<br/>
+
+GAUSS-03381: "long_int_add inner error, addend or summand is null pointer"
+
+SQLSTATE: XX000
+
+Description: Internal system error. A null pointer is found when the long integer and the integer are added.
+
+Solution: Contact technical support.
+
+GAUSS-03382: "long_int_add inner error, length of long_int not support."
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03383: "'EEEE' not supported for input"
+
+SQLSTATE: 0A000
+
+Description: The input for a string converted to a number does not support the **EEEE** format.
+
+Solution: Do not use **EEEE** as the format of a string to be converted to a number.
+
+GAUSS-03384: "'RN' not supported for input"
+
+SQLSTATE: 0A000
+
+Description: The input for a string converted to a number does not support the **RN** format.
+
+Solution: Do not use **RN** as the format of a string to be converted to a number.
+
+GAUSS-03385: "'%c' not supported"
+
+SQLSTATE: 0A000
+
+Description: Failed to convert the character to a number.
+
+Solution: Ensure that valid characters are used when a string is converted to a number.
+
+GAUSS-03386: "to_number only support 16 bytes hex to decimal conversion or plen less than 0."
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03387: "invalid number format model"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03388: "invalid number"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03389: "ts_rewrite query must return two tsquery columns"
+
+SQLSTATE: 22023
+
+Description: A system error occurs. Two tsquery columns must be returned when a text search overwrite query is performed.
+
+Solution: Check the query statement during the **ts_rewrite** function calling and ensure that only two columns are returned.
+
+GAUSS-03390: "array_typanalyze was invoked for non-array type %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03391 - GAUSS-03400
+
+<br/>
+
+GAUSS-03391: "insufficient pg_statistic slots for array stats"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03392: "must be system admin or have the same role to cancel queries running in other server processes"
+
+SQLSTATE: 42501
+
+Description: You do not have the permission to cancel queries.
+
+Solution: Cancel queries as a system administrator or an equivalent role.
+
+GAUSS-03394: "must be system admin or have the same role to terminate other backend"
+
+SQLSTATE: 42501
+
+Description: You do not have the permission to terminate other backend processes.
+
+Solution: Terminate queries as a system administrator or an equivalent role.
+
+GAUSS-03395: "must be system admin to signal the postmaster"
+
+SQLSTATE: 42501
+
+Description: Only system administrators can reload database configuration parameters.
+
+Solution: Reload database configuration parameters as a system administrator.
+
+GAUSS-03396: "must be system admin to rotate log files"
+
+SQLSTATE: 42501
+
+Description: Only system administrators can rotate log files.
+
+Solution: Rotate log files as a system administrator.
+
+GAUSS-03397: "fail to drop the user"
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03398: "index '%s' already contains data"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03399: "failed to re-find scan position within index '%s'"
+
+SQLSTATE: XX000
+
+Description: The offset is greater than the maximum internal offset.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03400: "hash does not support mark/restore"
+
+SQLSTATE: XX000
+
+Description: Hash does not support recording or restoring the scan position.
+
+Solution: Do not perform this operation because the function is not supported.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/35-GAUSS-03401-GAUSS-03500.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/35-GAUSS-03401-GAUSS-03500.md
new file mode 100644
index 0000000000000000000000000000000000000000..05611a396b4c848482cd4b3e3ea500c91d456481
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/35-GAUSS-03401-GAUSS-03500.md
@@ -0,0 +1,668 @@
+---
+title: GAUSS-03401 - GAUSS-03500
+summary: GAUSS-03401 - GAUSS-03500
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-03401 - GAUSS-03500
+
+<br/>
+
+## GAUSS-03401 - GAUSS-03410
+
+<br/>
+
+GAUSS-03402: "hash_redo: unimplemented"
+
+SQLSTATE: XX000
+
+Description: The hash index does not support the redo operation.
+
+Solution: Do not perform this operation because the function is not supported.
+
+GAUSS-03404: "index row size %lu exceeds hash maximum %lu"
+
+SQLSTATE: 54000
+
+Description: The size of the tuple exceeds the size of a page.
+
+Solution: Internal system error. Check whether toast is used.
+
+GAUSS-03405: "failed to add index item to '%s'"
+
+SQLSTATE: XX000
+
+Description: Failed to insert the tuple to the hash index page.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-03407: "hash AM does not use P_NEW"
+
+SQLSTATE: XX000
+
+Description: The hash index does not support foreign page expansion.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03408: "access to noncontiguous page in hash index '%s'"
+
+SQLSTATE: XX000
+
+Description: The hash index pages to be expanded must be consecutive.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03409: "unexpected hash relation size: %u, should be %u"
+
+SQLSTATE: XX000
+
+Description: Failed to expand the hash index page.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03410: "cannot initialize non-empty hash index '%s'"
+
+SQLSTATE: XX000
+
+Description: Failed to initialize the not-**NULL** hash table.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+<br/>
+
+## GAUSS-03411 - GAUSS-03420
+
+<br/>
+
+GAUSS-03411: "scan in progress on supposedly new bucket"
+
+SQLSTATE: XX000
+
+Description: The scan operation is performed on the new bucket.
+
+Solution: After the scan operation is complete, perform this operation again.
+
+GAUSS-03412: "could not get lock on supposedly new bucket"
+
+SQLSTATE: XX000
+
+Description: The lock on the new bucket is occupied.
+
+Solution: Try again.
+
+GAUSS-03413: "invalid overflow block number %u"
+
+SQLSTATE: XX000
+
+Description: The maximum internal page number of the hash table is exceeded.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03414: "firstfreebit found no free bit"
+
+SQLSTATE: XX000
+
+Description: No free bit is found.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03415: "invalid overflow bit number %u"
+
+SQLSTATE: XX000
+
+Description: The maximum number of bitmap pages is exceeded.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03416: "out of overflow pages in hash index '%s'"
+
+SQLSTATE: 54000
+
+Description: The number of hash index items exceeds the upper limit.
+
+Solution: Re-create indexes.
+
+GAUSS-03417: "missing support function %d(%u,%u) for index '%s'"
+
+SQLSTATE: XX000
+
+Description: This hash function is not supported.
+
+Solution: Use another hash function.
+
+GAUSS-03418: "index '%s' contains unexpected zero page at block %u"
+
+SQLSTATE: XX002
+
+Description: A blank page is detected by the index.
+
+Solution: Re-create indexes.
+
+GAUSS-03419: "index '%s' contains corrupted page at block %u"
+
+SQLSTATE: XX002
+
+Description: A corrupted page is detected by the index.
+
+Solution: Re-create indexes.
+
+GAUSS-03420: "index '%s' is not a hash index"
+
+SQLSTATE: XX002
+
+Description: The index does not belong to the hash index.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+<br/>
+
+## GAUSS-03421 - GAUSS-03430
+
+<br/>
+
+GAUSS-03421: "index '%s' has wrong hash version"
+
+SQLSTATE: XX002
+
+Description: The version information is incorrect.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03423: "lost saved point in index"
+
+SQLSTATE: XX000
+
+Description: A page in the index is missing.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03424: "could not find additional pending pages for same heap tuple"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03425: "index row size %lu exceeds maximum %lu for index '%s'"
+
+SQLSTATE: 54000
+
+Description: The size of the tuple exceeds the size of a page.
+
+Solution: A preventive error mechanism. Check whether the toast mechanism is used.
+
+GAUSS-03426: "failed to add item to index page in '%s'"
+
+SQLSTATE: XX000
+
+Description: Failed to insert a tuple to the page.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03427: "failed to add item to index root page"
+
+SQLSTATE: XX000
+
+Description: Failed to insert the tuple to the root page.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03428: "Lost path"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03429: "ginmerge: unimplemented"
+
+SQLSTATE: XX000
+
+Description: The GIN index does not support merging.
+
+Solution: Do not perform this operation because the function is not supported.
+
+GAUSS-03430: "unexpected searchMode: %d"
+
+SQLSTATE: XX000
+
+Description: The search mode is incorrect.
+
+Solution: Check the configured search mode.
+
+<br/>
+
+## GAUSS-03431 - GAUSS-03440
+
+<br/>
+
+GAUSS-03431: "old GIN indexes do not support whole-index scans nor searches for nulls"
+
+SQLSTATE: 0A000
+
+Description: The GIN index of an earlier version does not support the whole-index scan or **NULL** search.
+
+Solution: Create a GIN index of the new version.
+
+GAUSS-03432: "GIN does not support mark/restore"
+
+SQLSTATE: XX000
+
+Description: The GIN index does not support recording or restoring the scan position.
+
+Solution: Do not perform this operation because the function is not supported.
+
+GAUSS-03433: "failed to add item to index page in %u/%u/%u"
+
+SQLSTATE: XX000
+
+Description: Failed to insert a tuple to the page.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03434: "failed to add item to index page"
+
+SQLSTATE: XX000
+
+Description: Failed to insert a tuple to the page.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03438: "ginarrayextract requires three arguments"
+
+SQLSTATE: XX000
+
+Description: This function requires three parameters.
+
+Solution: Check the usage of the **ginarrayextract_2args** function.
+
+GAUSS-03439: "ginqueryarrayextract: unknown strategy number: %d"
+
+SQLSTATE: XX000
+
+Description: The strategy is incorrect.
+
+Solution: Check the usage of the **ginqueryarrayextract** function and the third parameter.
+
+<br/>
+
+## GAUSS-03441 - GAUSS-03450
+
+<br/>
+
+GAUSS-03441: "column is not in index"
+
+SQLSTATE: XX000
+
+Description: The index does not contain the attribute column.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03442: "system catalog scans with lossy index conditions are not implemented"
+
+SQLSTATE: XX000
+
+Description: The internal function is not supported.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03443: "cannot do ordered scan on index '%s', because it is being reindexed"
+
+SQLSTATE: XX000
+
+Description: The order scan cannot be performed during reindexing.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03444: "invalid %s regproc"
+
+SQLSTATE: XX000
+
+Description:**regproc** is invalid.
+
+Solution: Internal system error. Check the **regproc**.
+
+GAUSS-03445: "multixact_redo: unknown op code %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03451 - GAUSS-03460
+
+<br/>
+
+GAUSS-03453: "Xid is invalid."
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03454: "current transaction with handle: (%d:%u) have a valid xid: %lu already"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03456: "cannot commit a transaction that deleted files but has no xid"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03457: "cannot commit transaction %lu, it was already aborted"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03458: "maximum number of committed subtransactions (%d) exceeded"
+
+SQLSTATE: 54000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03459: "cannot abort transaction %lu, it was already committed"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03461 - GAUSS-03470
+
+<br/>
+
+GAUSS-03461: "cannot PREPARE a transaction that has exported snapshots"
+
+SQLSTATE: 0A000
+
+Description: A two-phase transaction cannot work on snapshots.
+
+Solution: Close the two-phase transaction.
+
+GAUSS-03462: "CleanupTransaction: unexpected state %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03463: "StartTransactionCommand: unexpected state %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03464: "CommitTransactionCommand: unexpected state %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03465: "%s cannot run inside a transaction block"
+
+SQLSTATE: 25001
+
+Description: Failed to execute the **CREATE TABLESPACE** and **COMMIT PREPARED** SQL statements inside a transaction block.
+
+Solution: Do not execute the **CREATE TABLESPACE** and **COMMIT PREPARED** SQL statements inside a transaction block.
+
+GAUSS-03466: "%s cannot run inside a subtransaction"
+
+SQLSTATE: 25001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03467: "%s cannot be executed from a function or multi-command string"
+
+SQLSTATE: 25001
+
+Description: Failed to execute the **CREATE TABLESPACE** and **COMMIT PREPARED** SQL statements inside a function.
+
+Solution: Do not execute the **CREATE TABLESPACE** and **COMMIT PREPARED** SQL statements inside a function.
+
+GAUSS-03468: "cannot prevent transaction chain"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03469: "%s can only be used in transaction blocks"
+
+SQLSTATE: 25005
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03470: "BeginTransactionBlock: unexpected state %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03471 - GAUSS-03480
+
+<br/>
+
+GAUSS-03471: "EndTransactionBlock: unexpected state %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03472: "UserAbortTransactionBlock: unexpected state %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03473: "DefineSavepoint: unexpected state %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03474: "no such savepoint"
+
+SQLSTATE: 3B001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03475: "ReleaseSavepoint: unexpected state %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03476: "RollbackToSavepoint: unexpected state %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03477: "BeginInternalSubTransaction: unexpected state %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03478: "ReleaseCurrentSubTransaction: unexpected state %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03479: "RollbackAndReleaseCurrentSubTransaction: unexpected state %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03480: "invalid transaction block state: %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03481 - GAUSS-03490
+
+<br/>
+
+GAUSS-03481: "cannot have more than 2^32-1 subtransactions in a transaction"
+
+SQLSTATE: 54000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03482: "PopTransaction with no parent"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03483: "xact_redo: unknown op code %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03485: "cannot assign TransactionIds during recovery"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03487: "Falling back to local Xid. Was = %lu, now is = %lu"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03491 - GAUSS-03500
+
+<br/>
+
+GAUSS-03492: "cannot assign OIDs during recovery"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03493: "Open file %s failed. %s\n"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03494: "Close file %s failed. %s\n"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03495: "seek file %s failed. %s\n"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03496: "clog_redo: unknown op code %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03498: "recovery is in progress"
+
+SQLSTATE: 55000
+
+Description: Failed to execute the WAL control function because the system recovery is ongoing.
+
+Solution: After the system recovery is complete, execute the WAL control function again.
+
+GAUSS-03500: "WAL level not sufficient for creating a restore point"
+
+SQLSTATE: 55000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/36-GAUSS-03501-GAUSS-03600.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/36-GAUSS-03501-GAUSS-03600.md
new file mode 100644
index 0000000000000000000000000000000000000000..220c5b629fe38e813ec7b14c5b67923a9fcd01d7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/36-GAUSS-03501-GAUSS-03600.md
@@ -0,0 +1,700 @@
+---
+title: GAUSS-03501 - GAUSS-03600
+summary: GAUSS-03501 - GAUSS-03600
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-03501 - GAUSS-03600
+
+<br/>
+
+## GAUSS-03501 - GAUSS-03510
+
+<br/>
+
+GAUSS-03501: "value too long for restore point (maximum %d characters)"
+
+SQLSTATE: 22023
+
+Description: The length of the restore point name exceeds 63 bytes.
+
+Solution: Recreate the restore point with a short name.
+
+GAUSS-03502: "could not parse transaction log location '%s'"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03504: "recovery is not in progress"
+
+SQLSTATE: 55000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03505: "invalid input syntax for transaction log location: '%s'"
+
+SQLSTATE: 22P02
+
+Description: The input parameter is invalid.
+
+Solution: Ensure that the function parameter is correct. Then, perform the operation again.
+
+GAUSS-03507: "could not access status of transaction %lu"
+
+SQLSTATE: XX000
+
+Description: Failed to obtain the file status.
+
+Solution: Check whether the file path and permission are correct.
+
+GAUSS-03508: "unrecognized SimpleLru error Description: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03509: "cannot make new WAL entries during recovery"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03511 - GAUSS-03520
+
+<br/>
+
+GAUSS-03513: "xlog write request %X/%X is past end of log %X/%X"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03514: "xlog flush request %X/%X is not satisfied - flushed only to %X/%X"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03515: "not enough data in file '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03516: "InstallXLogFileSegment should not have failed"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03517: "invalid XLogFileRead source %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03518: "could not open transaction log directory '%s': %m"
+
+SQLSTATE: XX000
+
+Description: Failed to open the **pg_xlog** folder.
+
+Solution: Check whether the file path and permission are correct.
+
+GAUSS-03519: "required WAL directory '%s' does not exist"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03520: "could not create missing directory '%s': %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03521 - GAUSS-03530
+
+<br/>
+
+GAUSS-03523: "syntax error in history file: %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03524: "invalid data in history file: %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03525: "invalid data in history file '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03527: "sizeof(ControlFileData) is larger than PG_CONTROL_SIZE; fix either one"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03529: "could not write to control file: %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03530: "could not fsync control file: %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03531 - GAUSS-03540
+
+<br/>
+
+GAUSS-03531: "could not close control file: %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03532: "could not open control file '%s': %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03533: "could not read from control file: %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03534: "database files are incompatible with server"
+
+SQLSTATE: XX000
+
+Description: Database files are incompatible with the software version.
+
+Solution: Use the correct software version to rebuild the database.
+
+GAUSS-03535: "incorrect checksum in control file"
+
+SQLSTATE: XX000
+
+Description: The content of the **pg_control** file is abnormal.
+
+Solution: Use the backup data to restore the **pg_control** file or rebuild the database.
+
+GAUSS-03536: "could not write bootstrap transaction log file: %m"
+
+SQLSTATE: XX000
+
+Description: The disk space is insufficient.
+
+Solution: Ensure that the disk space is sufficient and restart the database.
+
+GAUSS-03537: "could not fsync bootstrap transaction log file: %m"
+
+SQLSTATE: XX000
+
+Description: The file permission is incorrect.
+
+Solution: Check whether the file permission is correct and restart the database.
+
+GAUSS-03538: "could not close bootstrap transaction log file: %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03539: "could not open recovery command file '%s': %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03540: "recovery_target_timeline is not a valid number: '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03541 - GAUSS-03550
+
+<br/>
+
+GAUSS-03541: "recovery_target_xid is not a valid number: '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03542: "recovery_target_name is too long (maximum %d characters)"
+
+SQLSTATE: 22023
+
+Description: The recovery target name is too long.
+
+Solution: Shorten the recovery target name and restore the database.
+
+GAUSS-03543: "unrecognized recovery parameter '%s'"
+
+SQLSTATE: XX000
+
+Description: Failed to configure the recovery parameter.
+
+Solution: Configure the correct recovery parameter and restore the database.
+
+GAUSS-03544: "recovery command file '%s' must specify restore_command when standby mode is not enabled"
+
+SQLSTATE: XX000
+
+Description: The recovery command to be configured is empty.
+
+Solution: Configure the correct recovery command and restore the database.
+
+GAUSS-03545: "recovery target timeline %u does not exist"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03546: "hot standby is not possible because %s = %d is a lower setting than on the master server (its value was %d)"
+
+SQLSTATE: 22023
+
+Description: The configured parameter of the standby server is less than that of the primary server.
+
+Solution: Modify the configuration and restart the database.
+
+GAUSS-03548: "control file contains invalid data"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03549: "requested timeline %u is not a child of database system timeline %u"
+
+SQLSTATE: XX000
+
+Description: The backup WAL file is inconsistent with that in the database.
+
+Solution: Ensure that the WAL file is consistent with that in the database, and restore the database.
+
+GAUSS-03550: "could not find redo location referenced by checkpoint record"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03551 - GAUSS-03560
+
+<br/>
+
+GAUSS-03551: "could not locate required checkpoint record"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03552: "could not locate a valid checkpoint record"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03553: "invalid next transaction ID"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03554: "invalid redo in checkpoint record"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03555: "invalid redo record in shutdown checkpoint"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03556: "backup_label contains data inconsistent with control file"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03558: "requested recovery stop point is before consistent recovery point"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03559: "WAL ends before end of online backup"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03560: "WAL ends before consistent recovery point"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03561 - GAUSS-03570
+
+<br/>
+
+GAUSS-03562: "concurrent transaction log activity while database system is shutting down"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03563: "online backup was canceled, recovery cannot continue"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03564: "unexpected timeline ID %u (after %u) in checkpoint record"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03565: "unexpected timeline ID %u (should be %u) in checkpoint record"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03566: "unrecognized wal_sync_method: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03571 - GAUSS-03580
+
+<br/>
+
+GAUSS-03571: "WAL level not sufficient for making an online backup"
+
+SQLSTATE: 55000
+
+Description: The WAL level is insufficient.
+
+Solution: Set the WAL level to **archive** or **hot_standby** and perform a backup operation after the database is restarted.
+
+GAUSS-03572: "backup label too long (max %d bytes)"
+
+SQLSTATE: 22023
+
+Description: The length of the backup path name exceeds the limit.
+
+Solution: Change the backup path name and back up again.
+
+GAUSS-03573: "a backup is already in progress"
+
+SQLSTATE: 55000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03574: "WAL generated with full_page_writes=off was replayed since last restartpoint"
+
+SQLSTATE: 55000
+
+Description: The configuration item **full_page_writes** is set to **off**.
+
+Solution: Set the configuration item **full_page_writes** to **on**, perform **CHECKPOINT** on the host, and back up again.
+
+GAUSS-03575: "could not write file '%s': %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03576: "a backup is not in progress"
+
+SQLSTATE: 55000
+
+Description: No backup is in process.
+
+Solution: The **SELECT pg_start_backup** and **SELECT pg_stop_backup** functions are called in pairs. Call the **SELECT pg_start_backup** and **SELECT pg_stop_backup** in sequence. Check whether related backup is started.
+
+GAUSS-03577: "invalid data in file '%s'"
+
+SQLSTATE: 55000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03578: "the standby was promoted during online backup"
+
+SQLSTATE: 55000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03579: "WAL generated with full_page_writes=off was replayed during online backup"
+
+SQLSTATE: 55000
+
+Description: The configuration item **full_page_writes** is set to **off**.
+
+Solution: Set the configuration item **full_page_writes** to **on**, perform **CHECKPOINT** on the host, and back up again.
+
+GAUSS-03580: "invalid record offset at %X/%X."
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03581 - GAUSS-03590
+
+<br/>
+
+GAUSS-03581: "not enough shared memory for pg_lsnxlogflushchk share memory"
+
+SQLSTATE: 53200
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03582: "transaction identifier '%s' is too long"
+
+SQLSTATE: 22023
+
+Description: The transaction identifier parameter is too long.
+
+Solution: Check the input parameter and perform the prepare transaction operation again.
+
+GAUSS-03583: "prepared transactions are disabled"
+
+SQLSTATE: 55000
+
+Description: The configuration item **max_prepared_transactions** is set to **0**.
+
+Solution: Set the configuration item **max_prepared_transactions** to a value other than **0**.
+
+GAUSS-03584: "transaction identifier '%s' is already in use"
+
+SQLSTATE: 42710
+
+Description: The transaction identifier parameter is in use.
+
+Solution: Check the input parameter and perform the prepare transaction operation again.
+
+GAUSS-03585: "maximum number of prepared transactions reached"
+
+SQLSTATE: 53200
+
+Description: The value of the configuration item **max_prepared_transactions** is small.
+
+Solution: Set the configuration item **max_prepared_transactions** to a rational value or submit and roll back some transactions.
+
+GAUSS-03586: "prepared transaction with identifier '%s' is busy"
+
+SQLSTATE: 55000
+
+Description: The transaction identifier parameter is in use.
+
+Solution: Perform the operation again.
+
+GAUSS-03587: "permission denied to finish prepared transaction"
+
+SQLSTATE: 42501
+
+Description: The permission is incorrect.
+
+Solution: Terminate the prepared transactions as a transaction initiator or an administrator.
+
+GAUSS-03588: "prepared transaction belongs to another database"
+
+SQLSTATE: 0A000
+
+Description: Failed to connect the database.
+
+Solution: Ensure that the database is correct and connect to the database again.
+
+GAUSS-03589: "prepared transaction with identifier '%s' does not exist"
+
+SQLSTATE: 42704
+
+Description: The transaction identifier parameter does not exist.
+
+Solution: Check the parameter input and perform the operation again.
+
+GAUSS-03590: "failed to find %p in GlobalTransaction array"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03591 - GAUSS-03600
+
+<br/>
+
+GAUSS-03591: "failed to find GlobalTransaction for xid %lu"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03594: "could not write two-phase state file: %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03596: "could not close two-phase state file: %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03598: "could not recreate two-phase state file '%s': %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03599: "could not fsync two-phase state file: %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/37-GAUSS-03601-GAUSS-03700.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/37-GAUSS-03601-GAUSS-03700.md
new file mode 100644
index 0000000000000000000000000000000000000000..f0dbf8d71be9d44393953792ba416c80b01ee5be
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/37-GAUSS-03601-GAUSS-03700.md
@@ -0,0 +1,748 @@
+---
+title: GAUSS-03601 - GAUSS-03700
+summary: GAUSS-03601 - GAUSS-03700
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-03601 - GAUSS-03700
+
+<br/>
+
+## GAUSS-03601 - GAUSS-03610
+
+<br/>
+
+GAUSS-03603: "number of index columns (%d) exceeds limit (%d)"
+
+SQLSTATE: 54011
+
+Description: The number of index tuples exceeds the upper limit 32.
+
+Solution: Reduce the number of columns that require row-store indexes.
+
+GAUSS-03604: "index row requires %lu bytes, maximum size is %lu"
+
+SQLSTATE: 54000
+
+Description: The length of a single index tuple exceeds the size of a page, which is caused by excessively long data in the index column.
+
+Solution: Do not create indexes for excessively long columns.
+
+GAUSS-03605: "column '%s' cannot be applied %s compress mode"
+
+SQLSTATE: 42P16
+
+Description: The column does not support the prompted compression mode.
+
+Solution: Select the correct compression mode for the column.
+
+GAUSS-03606: "unsupported format code: %d"
+
+SQLSTATE: 22023
+
+Description: The type is not supported.
+
+Solution: Check the column type and perform the operation again.
+
+GAUSS-03607: "invalid attnum: %d"
+
+SQLSTATE: XX000
+
+Description: A system column involved in the operation does not exist.
+
+Solution: If the system column query is initiated by the user, check whether the query of the system column is supported. If the query is supported, this error is an internal error. Contact technical support.
+
+GAUSS-03608: "number of columns (%d) exceeds limit (%d)"
+
+SQLSTATE: 54011
+
+Description: The number of columns exceeds the upper limit.
+
+Solution: Reduce the number of columns and perform the operation again.
+
+GAUSS-03609: "Tuple does not match the descriptor"
+
+SQLSTATE: XX001
+
+Description: The number of columns in the tuple is different from the actual column quantity.
+
+Solution: Runtime error. Contact technical support.
+
+GAUSS-03610: "cannot extract system attribute from virtual tuple"
+
+SQLSTATE: XX000
+
+Description: An internal error occurs. The system column cannot be extracted from the virtual tuple.
+
+Solution: Runtime error. Contact technical support.
+
+<br/>
+
+## GAUSS-03611 - GAUSS-03620
+
+<br/>
+
+GAUSS-03611: "cannot extract system attribute from minimal tuple"
+
+SQLSTATE: XX000
+
+Description: An internal error occurs. The system column cannot be extracted from the virtual tuple.
+
+Solution: Runtime error. Contact technical support.
+
+GAUSS-03613: "user-defined relation parameter types limit exceeded"
+
+SQLSTATE: 54000
+
+Description: The definition of relation parameter types exceeds the upper limit.
+
+Solution: Redefine the relation parameter types.
+
+GAUSS-03614: "unsupported option type"
+
+SQLSTATE: XX000
+
+Description: The table definition options contain unsupported data types. Supported data types include boolean, integer, floating point, and string.
+
+Solution: Specify valid data types.
+
+GAUSS-03615: "RESET must not include values for parameters"
+
+SQLSTATE: 42601
+
+Description: The **RESET** command does not support a specified parameter value.
+
+Solution: Check the **RESET** command and run this command to reset the default value.
+
+GAUSS-03616: "unrecognized parameter namespace '%s'"
+
+SQLSTATE: 22023
+
+Description: Failed to recognize the parameter namespace.
+
+Solution: Ensure that the parameter namespace exists and perform the operation again.
+
+GAUSS-03617: "unrecognized parameter '%s'"
+
+SQLSTATE: 22023
+
+Description: Failed to recognize the parameter.
+
+Solution: Ensure that the parameter exists and perform the operation again.
+
+GAUSS-03618: "parameter '%s' specified more than once"
+
+SQLSTATE: 22023
+
+Description: The parameter is specified more than once.
+
+Solution: Check the parameter usage and perform the operation again.
+
+GAUSS-03619: "invalid value for boolean option '%s': %s"
+
+SQLSTATE: XX000
+
+Description: The data of the boolean type is invalid.
+
+Solution: Ensure that the data of the boolean type is valid and perform the operation again.
+
+GAUSS-03620: "invalid value for integer option '%s': %s"
+
+SQLSTATE: XX000
+
+Description: The data of the INT type is invalid.
+
+Solution: Ensure that the data of the INT type is valid and perform the operation again.
+
+<br/>
+
+## GAUSS-03621 - GAUSS-03630
+
+<br/>
+
+GAUSS-03621: "value %s out of bounds for option '%s'"
+
+SQLSTATE: XX000
+
+Description: The data value is out of range.
+
+Solution: Ensure that the data value is within the range and perform the operation again.
+
+GAUSS-03622: "invalid value for floating point option '%s': %s"
+
+SQLSTATE: XX000
+
+Description: The data of the FLOAT type is invalid.
+
+Solution: Ensure that the data of the FLOAT type is valid and perform the operation again.
+
+GAUSS-03623: "unsupported reloption type %d"
+
+SQLSTATE: XX000
+
+Description: The table definition options contain unsupported data types. Supported data types include boolean, integer, floating point, and string.
+
+Solution: Specify valid data types.
+
+GAUSS-03624: "unrecognized reloption type %c"
+
+SQLSTATE: XX000
+
+Description: The table definition options contain unsupported data types. Supported data types include boolean, integer, floating point, and string.
+
+Solution: Specify valid data types.
+
+GAUSS-03625: "reloption '%s' not found in parse table"
+
+SQLSTATE: XX000
+
+Description: A table option specified during table creation does not exist.
+
+Solution: Specify valid options.
+
+GAUSS-03626: "Invalid string for 'ORIENTATION' option"
+
+SQLSTATE: 22023
+
+Description: The parameter of the ORIENTATION option is invalid.
+
+Solution: Ensure that the parameter of the ORIENTATION option is valid and perform the operation again.
+
+GAUSS-03627: "Invalid string for 'COMPRESSION' option"
+
+SQLSTATE: 22023
+
+Description: The parameter of the COMPRESSION option is invalid.
+
+Solution: Ensure that the parameter of the COMPRESSION option is valid and perform the operation again.
+
+GAUSS-03628: "unrecognized StrategyNumber: %d"
+
+SQLSTATE: XX000
+
+Description: The strategy is incorrect.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03629: "missing oprcode for operator %u"
+
+SQLSTATE: XX000
+
+Description:**oprcode** is invalid.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03630: "btree index keys must be ordered by attribute"
+
+SQLSTATE: XX000
+
+Description: The index attribute column is less than 1.
+
+Solution: Ensure that the B-tree index is correctly created.
+
+<br/>
+
+## GAUSS-03631 - GAUSS-03640
+
+<br/>
+
+GAUSS-03631: "multiple active vacuums for index '%s'"
+
+SQLSTATE: XX000
+
+Description: Multiple VACUUM operations are performed on an index.
+
+Solution: Do not perform multiple VACUUM operations on a B-tree index at the same time.
+
+GAUSS-03632: "out of btvacinfo slots"
+
+SQLSTATE: XX000
+
+Description: The number of VACUUM operations exceeds the maximum value.
+
+Solution: Perform this operation after other VACUUM operations are complete.
+
+GAUSS-03633: "index '%s' is not a btree"
+
+SQLSTATE: XX002
+
+Description: This node is not the root of the B-tree index.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03635: "no live root page found in index '%s'"
+
+SQLSTATE: XX000
+
+Description: The B-tree index has no root node.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03636: "root page %u of index '%s' has level %u, expected %u"
+
+SQLSTATE: XX000
+
+Description: The root page of the index contains incorrect level information.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03637: "failed to re-find parent key in index '%s' for deletion target page %u"
+
+SQLSTATE: XX000
+
+Description: Failed to find the parent node during the deletion.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03638: "not enough stack items"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03639: "left link changed unexpectedly in block %u of index '%s'"
+
+SQLSTATE: XX000
+
+Description: The page number of the left link is changed.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03640: "right sibling's left-link doesn't match: block %u links to %u instead of expected %u in index '%s'"
+
+SQLSTATE: XX000
+
+Description: The B-tree index structure is incorrect. The left link of the right sibling does not match.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+<br/>
+
+## GAUSS-03641 - GAUSS-03650
+
+<br/>
+
+GAUSS-03641: "failed to delete rightmost child %u of block %u in index '%s'"
+
+SQLSTATE: XX000
+
+Description: Failed to delete a node.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03642: "right sibling %u of block %u is not next child %u of block %u in index '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03643: "fell off the end of index '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03644: "missing support function %d(%u,%u) for attribute %d of index '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03646: "could not find left sibling of block %u in index '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03647: "btree level %u not found in index '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03648: "invalid scan direction: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03649: "duplicate key value violates unique constraint '%s'"
+
+SQLSTATE: 23505
+
+Description: The inserted index value conflicts with the existing index values.
+
+Solution: Delete the unique constraint and perform the operation again.
+
+GAUSS-03650: "failed to re-find tuple within index '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03651 - GAUSS-03660
+
+<br/>
+
+GAUSS-03651: "failed to add new item to block %u in index '%s'"
+
+SQLSTATE: XX000
+
+Description: Failed to insert the record to the specified index page.
+
+Solution:Contact technical support.
+
+GAUSS-03652: "failed to add hikey to the right sibling while splitting block %u of index '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03653: "failed to add hikey to the left sibling while splitting block %u of index '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03655: "failed to add new item to the right sibling while splitting block %u of index '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03656: "failed to add old item to the left sibling while splitting block %u of index '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03657: "failed to add old item to the right sibling while splitting block %u of index '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03658: "could not find a feasible split point for index '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03659: "failed to re-find parent key in index '%s' for split pages %u/%u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03660: "failed to add leftkey to new root page while splitting block %u of index '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03661 - GAUSS-03670
+
+<br/>
+
+GAUSS-03661: "failed to add rightkey to new root page while splitting block %u of index '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03662: "failed to add item to the index page"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03663: "index compare error, both are NULL"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03664: "_bt_restore_page: cannot add item to page"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03665: "btree_insert_redo: failed to add item"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03666: "failed to add new item to left page after split"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03667: "failed to add high key to left page after split"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03670: "btree_xlog_cleanup: left block unfound"
+
+SQLSTATE: XX000
+
+Description: Failed to find the left block.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+<br/>
+
+## GAUSS-03671 - GAUSS-03680
+
+<br/>
+
+GAUSS-03671: "btree_xlog_cleanup: right block unfound"
+
+SQLSTATE: XX000
+
+Description: Failed to find the right block.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03672: "btree_xlog_cleanup: _bt_pagedel failed"
+
+SQLSTATE: XX000
+
+Description: Failed to delete the B-tree page.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03673: "unlogged GiST indexes are not supported"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03674: "concurrent GiST page split was incomplete"
+
+SQLSTATE: XX000
+
+Description: The split is incomplete.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03675: "index '%s' contains an inner tuple marked as invalid"
+
+SQLSTATE: XX000
+
+Description: The internal index contains invalid tuples.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03676: "failed to re-find parent of a page in index '%s', block %u"
+
+SQLSTATE: XX000
+
+Description: Failed to find the parent node page.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03677: "numberOfAttributes %d > %d"
+
+SQLSTATE: XX000
+
+Description: The number of attribute columns in the index table exceeds the maximum value.
+
+Solution: Reduce the number of attribute columns in the index.
+
+GAUSS-03678: "invalid GiST tuple found on leaf page"
+
+SQLSTATE: XX000
+
+Description: The GIST page is incorrect.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03679: "GiST only supports forward scan direction"
+
+SQLSTATE: XX000
+
+Description: Only the forward direction is supported.
+
+Solution: Internal system error. Check the scanning direction and the second parameter.
+
+<br/>
+
+## GAUSS-03681 - GAUSS-03690
+
+<br/>
+
+GAUSS-03683: "invalid value for 'buffering' option"
+
+SQLSTATE: 22023
+
+Description: The option of **BufferingOption** is not **on**, **off**, or **auto**.
+
+Solution: Internal system error. Check the **BufferingOption** option.
+
+GAUSS-03685: "failed to re-find parent for block %u"
+
+SQLSTATE: XX000
+
+Description: Failed to find the parent node page.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03687: "gistmerge: unimplemented"
+
+SQLSTATE: XX000
+
+Description: Failed to perform the merge operation for GIST indexes.
+
+Solution: Do not perform this operation because the function is not supported.
+
+GAUSS-03688: "failed to add item to GiST index page, size %d bytes"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03690: "GiST does not support mark/restore"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03691 - GAUSS-03700
+
+<br/>
+
+GAUSS-03691: "inconsistent point values"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03692: "unknown strategy number: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03693: "unrecognized strategy number: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03694: "index '%s' is not an SP-GiST index"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03695: "desired SPGiST tuple size is too big"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03696: "SP-GiST inner tuple size %lu exceeds maximum %lu"
+
+SQLSTATE: 54000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03697: "SPGiST inner tuple header field is too small"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03698: "some but not all node labels are null in SPGiST inner tuple"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03699: "failed to add item of size %u to SPGiST index page"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/38-GAUSS-03701-GAUSS-03800.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/38-GAUSS-03701-GAUSS-03800.md
new file mode 100644
index 0000000000000000000000000000000000000000..44ffc9a83c76f341b1a77f6fea8a52831f16c956
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/38-GAUSS-03701-GAUSS-03800.md
@@ -0,0 +1,700 @@
+---
+title: GAUSS-03701 - GAUSS-03800
+summary: GAUSS-03701 - GAUSS-03800
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-03701 - GAUSS-03800
+
+<br/>
+
+## GAUSS-03701 - GAUSS-03710
+
+<br/>
+
+GAUSS-03701: "spg_redo: unknown op code %u"
+
+SQLSTATE: XX000
+
+Description: The redo operation type is incorrect.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03702: "inconsistent tuple chain links in page %u of index '%s'"
+
+SQLSTATE: XX000
+
+Description: The internal tuple chain list of the SPGiST index is incorrect.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03703: "unexpected SPGiST tuple state: %d"
+
+SQLSTATE: XX000
+
+Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03704: "inconsistent counts of deletable tuples"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03705: "redirection leads to root page of index '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03706: "allTheSame should not occur for k-d trees"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03707: "spgmerge: unimplemented"
+
+SQLSTATE: XX000
+
+Description: Failed to perform the merge operation for SPGIN indexes because this function has not been implemented.
+
+Solution:Contact technical support.
+
+GAUSS-03708: "SPGiST does not support mark/restore"
+
+SQLSTATE: XX000
+
+Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03709: "inconsistent inner_consistent results for allTheSame inner tuple"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03710: "SP-GiST only supports forward scan direction"
+
+SQLSTATE: XX000
+
+Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03711 - GAUSS-03720
+
+<br/>
+
+GAUSS-03711: "getQuadrant: impossible case"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03712: "failed to find requested node %d in SPGiST inner tuple"
+
+SQLSTATE: XX000
+
+Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03715: "failed to divide leaf tuple groups across pages"
+
+SQLSTATE: XX000
+
+Description: Leaf nodes are stored on different pages.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03716: "cannot enlarge root tuple any more"
+
+SQLSTATE: XX000
+
+Description: The root tuple cannot be expanded.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03718: "SPGiST inner-tuple split must not produce longer prefix"
+
+SQLSTATE: XX000
+
+Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03719: "SPGiST index page %u has wrong nulls flag"
+
+SQLSTATE: XX000
+
+Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03720: "cannot add a node to an allTheSame inner tuple"
+
+SQLSTATE: XX000
+
+Description: A node cannot be added to identical internal tuples.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+<br/>
+
+## GAUSS-03721 - GAUSS-03730
+
+<br/>
+
+GAUSS-03721: "cannot add a node to an inner tuple without node labels"
+
+SQLSTATE: XX000
+
+Description: When you add a node to an internal tuple, the node label cannot be empty.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-03722: "unrecognized SPGiST choose result: %d"
+
+SQLSTATE: XX000
+
+Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03723: "row is too big: size %lu, maximum size %lu"
+
+SQLSTATE: 54000
+
+Description: The length of a single tuple exceeds the specification, and the TOAST technology cannot be used for storage.
+
+Solution: Split a large table with a large number of columns into multiple small tables before data storage. You can also change certain data types to string for storage. The 64-bit XID system changes the page specification. If an error occurs in the old table, you need to split the large table with a large number of columns into multiple small tables before data storage, or you can also change certain data types to string for storage.
+
+GAUSS-03724: "failed to add tuple"
+
+SQLSTATE: XX000
+
+Description: Internal error. Failed to insert the tuple.
+
+Solution: Try again.
+
+GAUSS-03725: "wrong buffer passed to visibilitymap_clear"
+
+SQLSTATE: XX000
+
+Description: An internal error occurs. Failed to check the validity of the page and page number before the visibility table operation.
+
+Solution: Try again.
+
+GAUSS-03728: "found toasted toast chunk for toast value %u in %s"
+
+SQLSTATE: XX014
+
+Description: An internal exception occurs in the TOAST data storage.
+
+Solution:Contact technical support.
+
+GAUSS-03729: "unexpected chunk number %d (expected %d) for toast value %u in %s"
+
+SQLSTATE: XX014
+
+Description: An internal error occurs. The number of chunks in TOAST data storage is different from expected.
+
+Solution:Contact technical support.
+
+GAUSS-03730: "unexpected chunk size %d (expected %d) in chunk %d of %d for toast value %u in %s"
+
+SQLSTATE: XX014
+
+Description: An internal exception occurs in the TOAST data storage.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03731 - GAUSS-03740
+
+<br/>
+
+GAUSS-03731: "unexpected chunk size %d (expected %d) in final chunk %d for toast value %u in %s"
+
+SQLSTATE: XX014
+
+Description: An internal exception occurs in the TOAST data storage.
+
+Solution:Contact technical support.
+
+GAUSS-03732: "unexpected chunk number %d (out of range %d..%d) for toast value %u in %s"
+
+SQLSTATE: XX014
+
+Description: An internal exception occurs in the TOAST data storage.
+
+Solution:Contact technical support.
+
+GAUSS-03733: "missing chunk number %d for toast value %u in %s"
+
+SQLSTATE: XX014
+
+Description: An internal exception occurs in the TOAST data storage.
+
+Solution:Contact technical support.
+
+GAUSS-03734: "unexpected chunk size %d (expected %d) in chunk %d of %d for toast value %u in %s when fetching slice"
+
+SQLSTATE: XX014
+
+Description: The chunk size of the TOAST table is different from expected.
+
+Solution: Check the TOAST table.
+
+GAUSS-03735: "unexpected chunk size %d (expected %d) in final chunk %d for toast value %u in %s when fetching slice"
+
+SQLSTATE: XX014
+
+Description: The chunk size of the TOAST table is different from expected.
+
+Solution: Check the TOAST table.
+
+GAUSS-03736: "could not open relation with OID %u"
+
+SQLSTATE: XX000
+
+Description: The relation OID is invalid.
+
+Solution: Query the table name and OID in **pg_class**.
+
+GAUSS-03737: "block number %u is out of range for relation '%s'"
+
+SQLSTATE: XX000
+
+Description: The block number exceeds the maximum block number in the table.
+
+Solution: Check the file length of the table.
+
+GAUSS-03738: "attempted to delete invisible tuple"
+
+SQLSTATE: XX000
+
+Description: The tuple to be deleted is invisible.
+
+Solution: Check whether other operations are concurrently performed on the table.
+
+GAUSS-03739: "tuple already updated by self"
+
+SQLSTATE: XX000
+
+Description: The tuple has been updated by the current transaction.
+
+Solution:Contact technical support.
+
+GAUSS-03740: "tuple concurrently updated"
+
+SQLSTATE: XX000
+
+Description: The tuple is concurrently updated or deleted.
+
+Solution: Check whether other operations are concurrently performed on the table.
+
+<br/>
+
+## GAUSS-03741 - GAUSS-03750
+
+<br/>
+
+GAUSS-03741: "attempted to update invisible tuple"
+
+SQLSTATE: XX000
+
+Description: The tuple to be updated is invisible.
+
+Solution: Check whether other operations are concurrently performed on the table.
+
+GAUSS-03742: "attempted to lock invisible tuple"
+
+SQLSTATE: XX000
+
+Description: The tuple to be locked is invisible.
+
+Solution: Check whether other operations are concurrently performed on the table.
+
+GAUSS-03743: "could not obtain lock on row in relation '%s'"
+
+SQLSTATE: 55P03
+
+Description: Failed to add a lock.
+
+Solution: Check whether other operations are concurrently performed on the table.
+
+GAUSS-03744: "heap_inplace_update: invalid lp"
+
+SQLSTATE: XX000
+
+Description: The tuple pointer of the update operation is invalid.
+
+Solution:Contact technical support.
+
+GAUSS-03745: "heap_inplace_update: wrong tuple length"
+
+SQLSTATE: XX000
+
+Description: The tuple length of the update operation is invalid.
+
+Solution:Contact technical support.
+
+GAUSS-03746: "heap_delete_redo: invalid lp"
+
+SQLSTATE: XX000
+
+Description: The tuple pointer during the redo delete operation is invalid.
+
+Solution: Ensure that the .xlog file is correct.
+
+GAUSS-03747: "heap_insert_redo: invalid max offset number"
+
+SQLSTATE: XX000
+
+Description: The page offset of the redo insert operation is invalid.
+
+Solution: Ensure that the .xlog file is correct.
+
+GAUSS-03748: "heap_insert_redo: failed to add tuple"
+
+SQLSTATE: XX000
+
+Description: Failed to add a tuple during the redo insert operation.
+
+Solution: Ensure that the .xlog file is correct.
+
+GAUSS-03749: "heap_multi_insert_redo: invalid max offset number"
+
+SQLSTATE: XX000
+
+Description: The page offset of the redo multi insert operation is invalid.
+
+Solution: Ensure that the .xlog file is correct.
+
+GAUSS-03750: "heap_multi_insert_redo: failed to add tuple"
+
+SQLSTATE: XX000
+
+Description: Failed to add a tuple during the redo multi insert operation.
+
+Solution: Ensure that the .xlog file is correct.
+
+<br/>
+
+## GAUSS-03751 - GAUSS-03760
+
+<br/>
+
+GAUSS-03751: "heap_update_redo: invalid lp"
+
+SQLSTATE: XX000
+
+Description: The tuple pointer during the redo update operation is invalid.
+
+Solution: Ensure that the .xlog file is correct.
+
+GAUSS-03752: "heap_update_redo: invalid max offset number"
+
+SQLSTATE: XX000
+
+Description: The page offset during the redo update tuple operation is invalid.
+
+Solution: Ensure that the .xlog file is correct.
+
+GAUSS-03753: "heap_update_redo: failed to add tuple"
+
+SQLSTATE: XX000
+
+Description: Failed to add a tuple during the redo update operation.
+
+Solution: Ensure that the .xlog file is correct.
+
+GAUSS-03754: "heap_lock_redo: invalid lp"
+
+SQLSTATE: XX000
+
+Description: The tuple pointer during the redo lock operation is invalid.
+
+Solution: Ensure that the .xlog file is correct.
+
+GAUSS-03755: "heap_inplace_redo: invalid lp"
+
+SQLSTATE: XX000
+
+Description: The tuple pointer during the redo inplace operation is invalid.
+
+Solution: Ensure that the .xlog file is correct.
+
+GAUSS-03756: "heap_inplace_redo: wrong tuple length"
+
+SQLSTATE: XX000
+
+Description: The tuple length during the redo inplace operation is invalid.
+
+Solution: Ensure that the .xlog file is correct.
+
+GAUSS-03759: "relation '%s' is not table or index"
+
+SQLSTATE: XX000
+
+Description: The relation of the operation is not a table or index.
+
+Solution: Check whether the object of the SQL operation is a table or index.
+
+<br/>
+
+## GAUSS-03761 - GAUSS-03770
+
+<br/>
+
+GAUSS-03761: "openning partition %u, but relation %s %u is neither table nor index"
+
+SQLSTATE: XX000
+
+Description: The partition of the operation is not a table or an index.
+
+Solution: Check whether the object of the SQL operation is a table or index.
+
+GAUSS-03762: "closing partition %u, but relation %u is neither table nor index"
+
+SQLSTATE: 2200X
+
+Description: The closed partition is not a table or an index.
+
+Solution: Check whether the object of the SQL operation is a table or index.
+
+GAUSS-03763: "failed to add tuple to page"
+
+SQLSTATE: XX000
+
+Description: Failed to add a tuple to the page.
+
+Solution:Contact technical support.
+
+GAUSS-03764: "page %u of relation '%s' should be empty but is not"
+
+SQLSTATE: XX000
+
+Description: The page must be empty.
+
+Solution:Contact technical support.
+
+GAUSS-03765: "tuple is too big: size %lu"
+
+SQLSTATE: XX000
+
+Description: The tuple length is greater than the free space on the page.
+
+Solution:Contact technical support.
+
+GAUSS-03767: "This query is not supported by optimizer in CStore"
+
+SQLSTATE: XX000
+
+Description: The column-store query is run on the CN.
+
+Solution: Check whether the column-store table is queried on the CN.
+
+<br/>
+
+## GAUSS-03771 - GAUSS-03780
+
+<br/>
+
+GAUSS-03771: "could not write cache file '%s': %m"
+
+SQLSTATE: XX000
+
+Description: Failed to write data to the cache file when data is inserted to a column-store partitioned table.
+
+Solution: Rectify the fault based on the error information about writing files.
+
+GAUSS-03772: "could not read cache file '%s': %m"
+
+SQLSTATE: XX000
+
+Description: Failed to read data from the cache file when data is inserted to a column-store partitioned table.
+
+Solution: Rectify the fault based on the error information about reading files.
+
+GAUSS-03774: "Column store don't support"
+
+SQLSTATE: XX000
+
+Description: Column-store tables do not support querying the system column.
+
+Solution: Delete unsupported system columns.
+
+GAUSS-03775: "unsupported datatype branch"
+
+SQLSTATE: XX000
+
+Description: Column-store tables do not support querying the data type.
+
+Solution: Check the data type.
+
+GAUSS-03777: "Non-deterministic UPDATE"
+
+SQLSTATE: 21000
+
+Description: The update is non-deterministic.
+
+Solution: Ensure that no row is updated multiple times.
+
+GAUSS-03778: "These rows have been deleted or updated"
+
+SQLSTATE: 21000
+
+Description: Data is deleted or updated multiple times.
+
+Solution: Ensure that no row is deleted or updated multiple times.
+
+<br/>
+
+## GAUSS-03781 - GAUSS-03790
+
+<br/>
+
+GAUSS-03781: "CStore: unrecognized heap_update status: %u"
+
+SQLSTATE: XX000
+
+Description: Failed to recognize the tuple update status of the CUDesc table.
+
+Solution:Contact technical support.
+
+GAUSS-03785: "WITH query name '%s' appears in both a rule action and the query being rewritten"
+
+SQLSTATE: 0A000
+
+Description: The name of the **WITH** statement appears in both the rule action and the rewriting statement.
+
+Solution: Use different names of the **WITH** statement for the rule action and the rewriting statement.
+
+GAUSS-03786: "cannot have RETURNING lists in multiple rules"
+
+SQLSTATE: 0A000
+
+Description: Multiple rules have RETURNING lists.
+
+Solution: Modify the rule syntax and eliminate inappropriate lists.
+
+GAUSS-03787: "bogus resno %d in targetlist"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03788: "multiple assignments to same column '%s'"
+
+SQLSTATE: 42601
+
+Description: Multiple value assignments to the same column occur (if FieldStore or ArrayRef assigns the value, this is not an error).
+
+Solution: Modify the **UPDATE** statement syntax to avoid multiple value assignments to the same column.
+
+GAUSS-03789: "cannot happen"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03790: "expected just one rule action"
+
+SQLSTATE: XX000
+
+Description: The rule has more than one action.
+
+Solution: Correct the corresponding primary foreign key constraint.
+
+<br/>
+
+## GAUSS-03791 - GAUSS-03800
+
+<br/>
+
+GAUSS-03792: "cannot handle per-attribute ON SELECT rule"
+
+SQLSTATE: XX000
+
+Description: The rule action must be a table-level action.
+
+Solution: Correct the corresponding primary foreign key constraint.
+
+GAUSS-03793: "unrecognized commandType: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03794: "infinite recursion detected in rules for relation '%s'"
+
+SQLSTATE: 42P17
+
+Description: Infinite recursion is detected in rules.
+
+Solution: Check the usage of rules.
+
+GAUSS-03795: "DO INSTEAD NOTHING rules are not supported for data-modifying statements in WITH"
+
+SQLSTATE: 0A000
+
+Description: The data-modifying statements do not support the DO INSTEAD NOTHING rules.
+
+Solution: Check the usage of rules.
+
+GAUSS-03796: "conditional DO INSTEAD rules are not supported for data-modifying statements in WITH"
+
+SQLSTATE: 0A000
+
+Description: The data-modifying statements do not support the conditional DO INSTEAD NO rules.
+
+Solution: Check the usage of rules.
+
+GAUSS-03797: "DO ALSO rules are not supported for data-modifying statements in WITH"
+
+SQLSTATE: 0A000
+
+Description: The data-modifying statements do not support the DO ALSO rules.
+
+Solution: Check the usage of rules.
+
+GAUSS-03799: "cannot perform INSERT RETURNING on relation '%s'"
+
+SQLSTATE: 0A000
+
+Description: An error occurs when the insert returning operation is performed on a table because the INSTEAD rule contains **RETURNING** but the original statement does not.
+
+Solution: Use the unconditional ON INSERT DO INSTEAD rule that contains the **RETURNING** clause.
+
+GAUSS-03800: "cannot perform UPDATE RETURNING on relation '%s'"
+
+SQLSTATE: 0A000
+
+Description: An error occurs when the update returning operation is performed on a table because the INSTEAD rule contains **RETURNING** but the original statement does not.
+
+Solution: Use the unconditional ON UPDATE DO INSTEAD rule that contains the **RETURNING** clause.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/39-GAUSS-03801-GAUSS-03900.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/39-GAUSS-03801-GAUSS-03900.md
new file mode 100644
index 0000000000000000000000000000000000000000..f6eb10f4617203f7650059518e54999586a52592
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/39-GAUSS-03801-GAUSS-03900.md
@@ -0,0 +1,644 @@
+---
+title: GAUSS-03801 - GAUSS-03900
+summary: GAUSS-03801 - GAUSS-03900
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-03801 - GAUSS-03900
+
+<br/>
+
+## GAUSS-03801 - GAUSS-03810
+
+<br/>
+
+GAUSS-03801: "cannot perform DELETE RETURNING on relation '%s'"
+
+SQLSTATE: 0A000
+
+Description: An error occurs when the delete returning operation is performed on a table because the INSTEAD rule contains **RETURNING** but the original statement does not.
+
+Solution: Use the unconditional ON DELETE DO INSTEAD rule that contains the **RETURNING** clause.
+
+GAUSS-03802: "WITH cannot be used in a query that is rewritten by rules into multiple queries"
+
+SQLSTATE: 0A000
+
+Description: Using **WITH** in multiple queries is not allowed.
+
+Solution: Check the usage of rules.
+
+GAUSS-03803: "Unexpected commandType or intoClause is not set properly"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03804: "cannot push down CurrentOfExpr"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03805: "expected to find SELECT subquery"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03806: "could not find rule placeholders"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03807: "conditional utility statements are not implemented"
+
+SQLSTATE: 0A000
+
+Description: The conditional utility statements cannot be used.
+
+Solution: Do not perform this operation because the function is not implemented.
+
+GAUSS-03808: "replace_rte_variables inserted a SubLink, but has noplace to record it"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03809: "WHERE CURRENT OF on a view is not implemented"
+
+SQLSTATE: 0A000
+
+Description: The **WHERE CURRENT OF** clause cannot be used in a view.
+
+Solution: Do not perform this operation because the function is not implemented.
+
+GAUSS-03810: "unexpected varattno %d in expression to be mapped"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03811 - GAUSS-03820
+
+<br/>
+
+GAUSS-03811: "rule '%s' for relation '%s' already exists"
+
+SQLSTATE: 42710
+
+Description: The rule to be inserted into a table exists.
+
+Solution: Do not insert the rule if it exists.
+
+GAUSS-03812: "rule actions on OLD are not implemented"
+
+SQLSTATE: 0A000
+
+Description: The OLD value rule is not implemented.
+
+Solution: Use a view or trigger to avoid the problem.
+
+GAUSS-03813: "rule actions on NEW are not implemented"
+
+SQLSTATE: 0A000
+
+Description: The NEW value rule is not implemented.
+
+Solution: Use a trigger to avoid the problem.
+
+GAUSS-03814: "INSTEAD NOTHING rules on SELECT are not implemented"
+
+SQLSTATE: 0A000
+
+Description: The INSTEAD NOTHING rule ON SELECT is not supported.
+
+Solution: Check the usage of rules.
+
+GAUSS-03815: "multiple actions for rules on SELECT are not implemented"
+
+SQLSTATE: 0A000
+
+Description: The rule has more than one action.
+
+Solution: Simplify the rule actions and retain only one.
+
+GAUSS-03816: "rules on SELECT must have action INSTEAD SELECT"
+
+SQLSTATE: 0A000
+
+Description: The rule action must be INSTEAD SELECT.
+
+Solution: Correct the defined rule action.
+
+GAUSS-03817: "rules on SELECT must not contain data-modifying statements in WITH"
+
+SQLSTATE: 0A000
+
+Description: The required rule action cannot contain data modification operations in the **WITH** statement.
+
+Solution: Correct the defined rule action.
+
+GAUSS-03818: "event qualifications are not implemented for rules on SELECT"
+
+SQLSTATE: 0A000
+
+Description: The execution of rule actions cannot be restricted by conditions.
+
+Solution: Correct the defined rule action.
+
+GAUSS-03819: "'%s' is already a view"
+
+SQLSTATE: 55000
+
+Description: A view can have only the ON SELECT rule action.
+
+Solution: Correct the defined rule action.
+
+GAUSS-03820: "view rule for '%s' must be named '%s'"
+
+SQLSTATE: 42P17
+
+Description: The rule action of a view must be defined as _RETURN.
+
+Solution: Correct the defined rule action.
+
+<br/>
+
+## GAUSS-03821 - GAUSS-03830
+
+<br/>
+
+GAUSS-03821: "could not convert table '%s' to a view because it is a partitioned table"
+
+SQLSTATE: 55000
+
+Description: Failed to convert a partitioned table to a view.
+
+Solution: Ensure that the table to be converted to a view is a non-partitioned table.
+
+GAUSS-03822: "could not convert table '%s' to a view because it is not empty"
+
+SQLSTATE: 55000
+
+Description: Failed to convert a non-empty table to a view.
+
+Solution: Ensure that the table to be converted to a view is an empty table.
+
+GAUSS-03823: "could not convert table '%s' to a view because it has triggers"
+
+SQLSTATE: 55000
+
+Description: Failed to convert a table containing triggers to a view.
+
+Solution: Ensure that the table to be converted to a view does not have triggers.
+
+GAUSS-03824: "could not convert table '%s' to a view because it has indexes"
+
+SQLSTATE: 55000
+
+Description: Failed to convert a table containing indexes to a view.
+
+Solution: Ensure that the table to be converted to a view does not have indexes.
+
+GAUSS-03825: "could not convert table '%s' to a view because it has child tables"
+
+SQLSTATE: 55000
+
+Description: Failed to convert a table containing sub-tables to a view.
+
+Solution: Ensure that the table to be converted to a view does not have sub-tables.
+
+GAUSS-03826: "cannot have multiple RETURNING lists in a rule"
+
+SQLSTATE: 0A000
+
+Description: A rule cannot contain multiple RETURNING lists.
+
+Solution: Check the number of RETURNING lists.
+
+GAUSS-03827: "RETURNING lists are not supported in conditional rules"
+
+SQLSTATE: 0A000
+
+Description: The RETURNING lists are used in the conditional rules.
+
+Solution: Delete the RETURNING lists.
+
+GAUSS-03828: "RETURNING lists are not supported in non-INSTEAD rules"
+
+SQLSTATE: 0A000
+
+Description: The RETURNING lists are used in the non-INSTEAD rules.
+
+Solution: Delete the RETURNING lists.
+
+GAUSS-03829: "SELECT rule's target list has too many entries"
+
+SQLSTATE: 42P17
+
+Description: The SELECT rules target list has more entries than the required number of columns.
+
+Solution: Check the number of columns and delete the unnecessary columns.
+
+GAUSS-03830: "cannot convert relation containing dropped columns to view"
+
+SQLSTATE: 0A000
+
+Description: Failed to convert a table containing dropped columns to a view.
+
+Solution: Check the structure of the table to be converted to a view.
+
+<br/>
+
+## GAUSS-03831 - GAUSS-03840
+
+<br/>
+
+GAUSS-03831: "SELECT rule's target entry %d has different column name from '%s'"
+
+SQLSTATE: 42P17
+
+Description: The column names in the SELECT rule are different.
+
+Solution: Check the column name in the SELECT rule target entry.
+
+GAUSS-03832: "SELECT rule's target entry %d has different type from column '%s'"
+
+SQLSTATE: 42P17
+
+Description: The column types in the SELECT rule are different.
+
+Solution: Check the column type in the SELECT rule target entry.
+
+GAUSS-03833: "SELECT rule's target entry %d has different size from column '%s'"
+
+SQLSTATE: 42P17
+
+Description: The sizes of columns in the SELECT rule are different.
+
+Solution: Check the column size in the SELECT rule target entry.
+
+GAUSS-03834: "SELECT rule's target list has too few entries"
+
+SQLSTATE: 42P17
+
+Description: The number of columns entered in the SELECT rule is too small.
+
+Solution: Check the number of columns entered in the SELECT rule.
+
+GAUSS-03835: "rule '%s' for relation '%s' does not exist"
+
+SQLSTATE: 42704
+
+Description: The rules to be disabled or enabled does not exist in the corresponding table.
+
+Solution: Check the table rules.
+
+GAUSS-03836: "rule '%s' does not exist"
+
+SQLSTATE: 42704
+
+Description: The rules to be obtained do not exist in the corresponding table.
+
+Solution: Check the table rules.
+
+GAUSS-03837: "there are multiple rules named '%s'"
+
+SQLSTATE: 42710
+
+Description: Multiple rules with the same name are found.
+
+Solution: Check the table rules.
+
+GAUSS-03838: "Column store don't support this system column"
+
+SQLSTATE: XX000
+
+Description: Column storage does not support this system column.
+
+Solution: Check the involved system column.
+
+<br/>
+
+## GAUSS-03841 - GAUSS-03850
+
+<br/>
+
+GAUSS-03841: "vector scan for VecMarkPos is not yet implemented "
+
+SQLSTATE: XX000
+
+Description: Internal system error. The MarkPos function for the column scanning node is not implemented.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-03842: "VecResult for VecMarkPos is not yet implemented "
+
+SQLSTATE: XX000
+
+Description: Internal system error. The MarkPos function for the column-store result node is not implemented.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-03844: "vector scan for VecRestrPos is not yet implemented "
+
+SQLSTATE: XX000
+
+Description: Internal system error. The RestrPos function for the column scanning node is not implemented.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-03845: "VecResult for VecRestrPos is not yet implemented "
+
+SQLSTATE: XX000
+
+Description: Internal system error. The RestrPos function for the column-store result node is not implemented.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-03848: "Not support pushing predicate with none-const external param"
+
+SQLSTATE: 0A000
+
+Description: Non-constant external parameters cannot be pushed down.
+
+Solution: Check parameters.
+
+GAUSS-03849: "could not find tuple for operator %u"
+
+SQLSTATE: XX000
+
+Description: Failed to obtain the required corresponding information from the **pg_operator** system catalog based on the ID.
+
+Solution: Check the **pg_operator** system catalog for confirmation.
+
+<br/>
+
+## GAUSS-03851 - GAUSS-03860
+
+<br/>
+
+GAUSS-03851: "UnSupported vector aggregation function %u"
+
+SQLSTATE: XX000
+
+Description: An incorrect execution plan is generated.
+
+Solution: Retain the plan. Contact technical support.
+
+GAUSS-03853: "unsupported aggregation type"
+
+SQLSTATE: XX000
+
+Description: Generated plan error.
+
+Solution: Retain the plan. Contact technical support.
+
+GAUSS-03854: "VecRemoteQuery ReScan is not yet implemented"
+
+SQLSTATE: 0A000
+
+Description: VecRemoteQuery rescanning cannot be implemented.
+
+Solution: Check the scan statement.
+
+GAUSS-03857: "Unsupported window function %s in vector engine"
+
+SQLSTATE: XX000
+
+Description: Usage not supported.
+
+Solution: Modify the SQL statement.
+
+GAUSS-03860: "Un-support CHECK constraint"
+
+SQLSTATE: XX000
+
+Description: Column storage does not support the CHECK constraint.
+
+Solution: Check the syntax and remove the CHECK constraint.
+
+<br/>
+
+## GAUSS-03861 - GAUSS-03870
+
+<br/>
+
+GAUSS-03862: "unsupport join type %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03864: "unrecognized running state: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03865: "ExecReScanVecModifyTable is not implemented"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03866: "could not write into hash-join temporary file: %m"
+
+SQLSTATE: XX000
+
+Description: An error occurs when the **hash-join** temporary file is written.
+
+Solution: Check the file and user permissions.
+
+GAUSS-03867: "could not write to hashAgg temporary file: %m"
+
+SQLSTATE: XX000
+
+Description: An error occurs when the **hashAgg** temporary file is written.
+
+Solution: Check the file and user permissions.
+
+GAUSS-03868: "could not read from hashAgg temporary file: %m"
+
+SQLSTATE: XX000
+
+Description: An error occurs when the **hashAgg** temporary file is read.
+
+Solution: Check the file and user permissions.
+
+GAUSS-03869: "UnSupported vector function %s"
+
+SQLSTATE: XX000
+
+Description: Internal system error. Failed to vectorize the function.
+
+Solution: Contact technical support.
+
+GAUSS-03870: "Unsupported array reference expression in vector engine"
+
+SQLSTATE: XX000
+
+Description: Internal system error. The array reference expression is not vectorized.
+
+Solution: Contact technical support.
+
+<br/>
+
+## GAUSS-03871 - GAUSS-03880
+
+<br/>
+
+GAUSS-03873: "Unsupported field expression in vector engine"
+
+SQLSTATE: XX000
+
+Description: Internal system error. The field select expression function is not vectorized.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-03874: "Unsupported field store expression in vector engine"
+
+SQLSTATE: XX000
+
+Description: Internal system error. The field store expression function is not vectorized.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-03875: "Unsupported convert row type expression in vector engine"
+
+SQLSTATE: XX000
+
+Description: Internal system error. The convert row type expression function is not vectorized.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-03876: "Unsupported array expression in vector engine"
+
+SQLSTATE: XX000
+
+Description: Internal system error. The array expression function is not vectorized.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-03877: "Unsupported xml expression in vector engine"
+
+SQLSTATE: XX000
+
+Description: Internal system error. The XML expression function is not vectorized.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-03878: "Unsupported coerce to domain expression in vector engine"
+
+SQLSTATE: XX000
+
+Description: Internal system error. The coerce to domain expression function is not vectorized.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-03879: "Unsupported coerce to domain value expression in vector engine"
+
+SQLSTATE: XX000
+
+Description: Internal system error. The coerce to domain value expression function is not vectorized.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-03880: "Unsupported current of expression in vector engine"
+
+SQLSTATE: XX000
+
+Description: Internal system error. The **CURRENT OF** expression function is not vectorized.
+
+Solution: Internal system error. Contact technical support.
+
+<br/>
+
+## GAUSS-03881 - GAUSS-03890
+
+<br/>
+
+GAUSS-03882: "Unsupported array coerce expression in vector engine"
+
+SQLSTATE: XX000
+
+Description: Internal system error. The array coerce expression function is not vectorized.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-03888: "redundant options"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03891 - GAUSS-03900
+
+<br/>
+
+GAUSS-03891: "Failed to initialize Cgroup. Please check if workload manager is enabled and Cgroups have been created!"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03893: "invalid control group: %s"
+
+SQLSTATE: XX000
+
+Description: The cgroup name is invalid.
+
+Solution: Check the cgroup name.
+
+GAUSS-03897: "Resource Pool '%s': object not defined"
+
+SQLSTATE: 42704
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03899: "read workload_gpname failed."
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03900: "Workload Group '%s': object not defined"
+
+SQLSTATE: 42704
+
+Description:Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/4-GAUSS-00301-GAUSS-00400.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/4-GAUSS-00301-GAUSS-00400.md
new file mode 100644
index 0000000000000000000000000000000000000000..3671575f755186a52b2e0d56b2a3d5492dd20f7b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/4-GAUSS-00301-GAUSS-00400.md
@@ -0,0 +1,804 @@
+---
+title: GAUSS-00301 - GAUSS-00400
+summary: GAUSS-00301 - GAUSS-00400
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-00301 - GAUSS-00400
+
+<br/>
+
+## GAUSS-00301 - GAUSS-00310
+
+<br/>
+
+GAUSS-00301: "EXECUTE DIRECT cannot execute this utility query"
+
+SQLSTATE: 0A000
+
+Description: In the **EXECUTE DIRECT ON ( nodename [, … ] ) query** syntax, a DML statement is executed on a DN, which is not supported.
+
+Solution: Do not execute a DDL statement in the **EXECUTE DIRECT ON ( nodename [, … ] ) query** syntax.
+
+GAUSS-00302: "EXECUTE DIRECT cannot execute locally this utility query"
+
+SQLSTATE: 0A000
+
+Description: In the **EXECUTE DIRECT ON ( nodename [, … ] ) query** syntax, a **Set** variable statement is executed on a DN.
+
+Solution: Do not execute a **Set** variable statement in the **EXECUTE DIRECT ON ( nodename [, … ] ) query** syntax.
+
+GAUSS-00303: "SELECT FOR UPDATE/SHARE is not allowed with DISTINCT clause"
+
+SQLSTATE: 0A000
+
+Description: The **DISTINCT** clause cannot be used in the **SELECT FOR UPDATE/SHARE** syntax.
+
+Solution: Modify the statement.
+
+GAUSS-00304: "SELECT FOR UPDATE/SHARE is not allowed with GROUP BY clause"
+
+SQLSTATE: 0A000
+
+Description: The **GROUP BY** clause cannot be used in the **SELECT … FOR UPDATE/SHARE** syntax.
+
+Solution: Modify the statement.
+
+GAUSS-00305: "SELECT FOR UPDATE/SHARE is not allowed with HAVING clause"
+
+SQLSTATE: 0A000
+
+Description: The **HAVING** clause cannot be used in the **SELECT … FOR UPDATE/SHARE** syntax.
+
+Solution: Modify the statement.
+
+GAUSS-00306: "SELECT FOR UPDATE/SHARE is not allowed with aggregate functions"
+
+SQLSTATE: 0A000
+
+Description: Aggregate functions cannot be used in the **SELECT … FOR UPDATE/SHARE** syntax.
+
+Solution: Modify the statement.
+
+GAUSS-00307: "SELECT FOR UPDATE/SHARE is not allowed with window functions"
+
+SQLSTATE: 0A000
+
+Description: Window functions cannot be used in the **SELECT … FOR UPDATE/SHARE** syntax.
+
+Solution: Modify the statement.
+
+GAUSS-00308: "SELECT FOR UPDATE/SHARE is not allowed with set-returning functions in the target list"
+
+SQLSTATE: 0A000
+
+Description: Functions with defined return values cannot be used in the **SELECT … FOR UPDATE/SHARE** syntax.
+
+Solution: Modify the statement.
+
+GAUSS-00309: "SELECT FOR UPDATE/SHARE must specify unqualified relation names"
+
+SQLSTATE: 42601
+
+Description: In the **SELECT … FOR UPDATE/SHARE…OF table_name** syntax, the specified table name contains database or schema references.
+
+Solution: Ensure that the specified table name does not contain database or schema references.
+
+GAUSS-00310: "SELECT FOR UPDATE/SHARE cannot be used with column table '%s'"
+
+SQLSTATE: 0A000
+
+Description: The table specified in the **SELECT … FOR UPDATE/SHARE…OF table_name** syntax is a column-store table.
+
+Solution: Modify the syntax to ensure that the specified table cannot be a column-store table.
+
+<br/>
+
+## GAUSS-00311 - GAUSS-00320
+
+<br/>
+
+GAUSS-00311: "SELECT FOR UPDATE/SHARE cannot be applied to a join"
+
+SQLSTATE: 0A000
+
+Description: The range table in the **FOR UPDATE/SHARE…OF table_name** syntax is a join table.
+
+Solution: Modify the syntax to ensure that the specified table is not a join table.
+
+GAUSS-00312: "SELECT FOR UPDATE/SHARE cannot be applied to a function"
+
+SQLSTATE: 0A000
+
+Description: The range table in the **SELECT … FOR UPDATE/SHARE…OF table_name** syntax is a function.
+
+Solution: Modify the syntax to ensure that the specified table is not a function.
+
+GAUSS-00313: "SELECT FOR UPDATE/SHARE cannot be applied to a WITH query"
+
+SQLSTATE: 0A000
+
+Description: The range table in the **SELECT … FOR UPDATE/SHARE…OF table_name** syntax is a list identified by the **WITH** clause.
+
+Solution: Modify the syntax to ensure that the specified range table is not a list identified by the **WITH** clause.
+
+GAUSS-00314: "unrecognized RTE type: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00315: "relation '%s' in FOR UPDATE/SHARE clause not found in FROM clause"
+
+SQLSTATE: 42P01
+
+Description: *table_name* in the **SELECT … FROM table1_name FOR UPDATE/SHARE…OF table_name** syntax does not exist in the **FROM** clause.
+
+Solution: Ensure that *table_name* exists in the **FROM** clause.
+
+GAUSS-00316: "unsupport 'like clause including partition' for partitioned table"
+
+SQLSTATE: 42P16
+
+Description: In the **CREATE TABLE … LIKE source_table** syntax, the table name in the **LIKE** clause is specified as a partitioned table.
+
+Solution: Modify the syntax to ensure that the **PARTITION BY** clause is used if the table name is specified as a partitioned table.
+
+GAUSS-00317: "unsupport 'like clause including reloptions' together with 'with'"
+
+SQLSTATE: 42P16
+
+Description: In the **CREATE TABLE … LIKE source_table** syntax, the **LIKE** clause contains **INCLUDING RELOPTIONS**, which is used together with the **WITH** clause in the source table. As a result, a syntax conflict occurs.
+
+Solution: Do not use **INCLUDING RELOPTIONS** together with the **WITH** clause in the source table. Use either of them because both storage parameters will be copied to a new table. "
+
+GAUSS-00318: "array of serial is not implemented"
+
+SQLSTATE: 0A000
+
+Description: The column type in the **CREATE TABLE** or **ALTER TABLE** syntax is a serial array, causing an error.
+
+Solution: Ensure that the column type is not a serial array.
+
+GAUSS-00319: "conflicting NULL/NOT NULL declarations for column '%s' of table '%s'"
+
+SQLSTATE: 42601
+
+Description: The non-null column names specified in the **CREATE TABLE** or **ALTER TABLE** syntax are in conflict with the null column names specified in the constraint clause.
+
+Solution: Ensure that the null column names specified in the constraint clause are consistent with the column names specified in the column name list.
+
+GAUSS-00320: "multiple default values specified for column '%s' of table '%s'"
+
+SQLSTATE: 42601
+
+Description: Multiple names are specified for a column in the constraint clause of the **CREATE TABLE** or **ALTER TABLE** syntax.
+
+Solution: Specify only one name for a column.
+
+<br/>
+
+## GAUSS-00321 - GAUSS-00330
+
+<br/>
+
+GAUSS-00321: "column exclusion constraints are not supported"
+
+SQLSTATE: XX000
+
+Description: Syntax not supported.
+
+Solution: Modify the SQL statement.
+
+GAUSS-00322: "unrecognized constraint type: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00323: "invalid context for constraint type %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00324: "'%s' is not a table, view, composite type, or foreign table"
+
+SQLSTATE: 42809
+
+Description: *source_table* in the **CREATE TABLE … LIKE source_table** syntax is not a relational table, view table, composite table, or foreign table.
+
+Solution: Ensure that *source_table* is a relational table, view, composite type, or foreign table.
+
+GAUSS-00325: "could not specify 'INCLUDING PARTITION' for non-partitioned-table relation:'%s'"
+
+SQLSTATE: 42809
+
+Description:**INCLUDING PARTITION** is specified for a partitioned table in the **CREATE TABLE … LIKE source_table** syntax.
+
+Solution: Do not specify **INCLUDING PARTITION** for a partitioned table in the **CREATE TABLE … LIKE source_table** syntax.
+
+GAUSS-00326: "could not specify 2 or more 'INCLUDING PARTITION' clauses, only one is allowed"
+
+SQLSTATE: 42809
+
+Description: More than one **LIKE…INCLUDING PARTITION** clause is specified in the **CREATE TABLE … (LIKE source_table INCLUDING PARTITION)** syntax.
+
+Solution: Specify only one **LIKE…INCLUDING PARTITION** clause in the **CREATE TABLE … (LIKE source_table INCLUDING PARTITION)** syntax.
+
+GAUSS-00327: "could not specify 2 or more 'INCLUDING RELOPTIONS' clauses, only one is allowed"
+
+SQLSTATE: 42809
+
+Description: More than one **INCLUDING RELOPTIONS** clause is specified in the **LIKE** clause of the **CREATE TABLE … LIKE source_table** syntax.
+
+Solution: Specify only one **INCLUDING RELOPTIONS** clause in the **LIKE** clause of the **CREATE TABLE … LIKE source_table** syntax.
+
+GAUSS-00328: "could not specify 2 or more 'INCLUDING DISTRIBUTION' clauses, only one is allowed"
+
+SQLSTATE: 42809
+
+Description: More than one **INCLUDING DISTRIBUTION** clause is specified in the **LIKE** clause of the **CREATE TABLE … LIKE source_table** syntax.
+
+Solution: Specify only one **INCLUDING DISTRIBUTION** clause in the **LIKE** clause of the **CREATE TABLE … LIKE source_table** syntax.
+
+GAUSS-00329: "Postgres-XC does not support VIEW in LIKE clauses"
+
+SQLSTATE: 0A000
+
+Description: Views cannot be used in the **LIKE** clause of the **CREATE TABLE … LIKE** syntax.
+
+Solution: Delete views from the **LIKE** clause of the **CREATE TABLE … LIKE** syntax.
+
+GAUSS-00330: "cannot convert whole-row table reference"
+
+SQLSTATE: 0A000
+
+Description: Syntax not supported.
+
+Solution: Modify the SQL statement.
+
+<br/>
+
+## GAUSS-00331 - GAUSS-00340
+
+<br/>
+
+GAUSS-00331: "cache lookup failed on source like relation %u for reloptions"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00332: "null partition key value for relation '%s'"
+
+SQLSTATE: XX000
+
+Description: The null partition key value cannot be used.
+
+Solution: Correct the partition key value.
+
+GAUSS-00333: "partition key column's number of relation '%s' is not a 1-D smallint array"
+
+SQLSTATE: XX000
+
+Description: The number of partition key columns or column type is incorrect for **INCLUDING PARTITION** specified in the **LIKE** clause of the **CREATE TABLE … LIKE** syntax.
+
+Solution: Ensure that the number of partition key columns is 1 and the column type is an integer.
+
+GAUSS-00334: "partition key column's number of %s not in the range of all its columns"
+
+SQLSTATE: XX000
+
+Description: The number of partition key columns for **INCLUDING PARTITION** specified in the **LIKE** clause of the **CREATE TABLE … LIKE** syntax exceeds the column quantity range of the current table.
+
+Solution: Ensure that the number of partition key columns ranges from 1 to the maximum number of allowed columns of the current table.
+
+GAUSS-00335: "' including partition ' for list partitioned relation: '%s' not implemented yet"
+
+SQLSTATE: XX000
+
+Description: The partition type is incorrect for **INCLUDING PARTITION** specified in the **LIKE** clause of the **CREATE TABLE … LIKE** syntax.
+
+Solution: Ensure that the partition type is range or hash partitioning. List partitioning is not supported.
+
+GAUSS-00336: "cache lookup failed for constraint %u"
+
+SQLSTATE: 22P06
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00337: "null conexclop for constraint %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00338: "cache lookup failed for operator %u"
+
+SQLSTATE: 22P06
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00339: "too few entries in indexprs list"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00340: "cache lookup failed for collation %u"
+
+SQLSTATE: 22P06
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-00341 - GAUSS-00350
+
+<br/>
+
+GAUSS-00341: "cache lookup failed for opclass %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00342: "Partitioned table does not support EXCLUDE index"
+
+SQLSTATE: 0A000
+
+Description: The exclusion constraint cannot be specified in the **CREATE TABLE … CONSTRAINT** syntax when creating a partitioned table.
+
+Solution: Modify the syntax to specify other constraints when creating a partitioned table.
+
+GAUSS-00343: "Invalid PRIMARY KEY/UNIQUE constraint for partitioned table"
+
+SQLSTATE: 0A000
+
+Description: In the **CREATE TABLE … CONSTRAINT** syntax, the partition key column for the partitioned table is not contained in the **PRIMARY KEY** or **UNIQUE** constraint for creating a partitioned table.
+
+Solution: Ensure that the partition key column for the partitioned table is contained.
+
+GAUSS-00344: "multiple primary keys for table '%s' are not allowed"
+
+SQLSTATE: 42P16
+
+Description: More than one primary key for **INCLUDING INDEXES** is specified in the **LIKE** clause of the **CREATE TABLE … LIKE source_table** syntax.
+
+Solution: Specify only one primary key.
+
+GAUSS-00345: "cannot use an existing index in CREATE TABLE"
+
+SQLSTATE: 0A000
+
+Description: A constraint is incorrectly specified for the index column in the **CREATE TABLE** syntax.
+
+Solution: Add a new constraint to the data table using the **ALTER TABLE … ADD table_constraint** syntax.
+
+GAUSS-00346: "index '%s' does not exist"
+
+SQLSTATE: 42704
+
+Description: The attribute name for specifying constraints in the **CREATE/ALTER TABLE** syntax does not exist in the relational table.
+
+Solution: Ensure that the attribute name exists in the relational table.
+
+GAUSS-00347: "index '%s' is already associated with a constraint"
+
+SQLSTATE: 55000
+
+Description: Usage not supported.
+
+Solution: Create another index.
+
+GAUSS-00348: "index '%s' does not belong to table '%s'"
+
+SQLSTATE: 55000
+
+Description: The attribute name for specifying constraints in the **CREATE/ALTER TABLE table_name** syntax does not exist in *table_name*.
+
+Solution: Ensure that the attribute name exists.
+
+GAUSS-00349: "index '%s' is not valid"
+
+SQLSTATE: 55000
+
+Description: The attribute name for specifying constraints in the **CREATE/ALTER TABLE** syntax is invalid.
+
+Solution: Ensure that the attribute name exists in a relational or schema table.
+
+GAUSS-00350: "'%s' is not a unique index"
+
+SQLSTATE: 42809
+
+Description: In the **CREATE TABLE … CONSTRAINT** syntax, the index in the **PRIMARY KEY** or **UNIQUE** constraint for creating a partitioned table is not unique.
+
+Solution: Ensure that the index is unique.
+
+<br/>
+
+## GAUSS-00351 - GAUSS-00360
+
+<br/>
+
+GAUSS-00351: "index '%s' contains expressions"
+
+SQLSTATE: 42809
+
+Description: In the **CREATE TABLE … CONSTRAINT** syntax, the index in the **PRIMARY KEY** or **UNIQUE** constraint for creating a partitioned table contains an expression.
+
+Solution: Ensure that the index in the **PRIMARY KEY** or **UNIQUE** constraint for creating a partitioned table in the **CREATE TABLE … CONSTRAINT** syntax does not contain an expression.
+
+GAUSS-00352: "'%s' is a partial index"
+
+SQLSTATE: 42809
+
+Description: Usage not supported.
+
+Solution: Replace it with a valid index.
+
+GAUSS-00353: "'%s' is a deferrable index"
+
+SQLSTATE: 42809
+
+Description: Usage not supported.
+
+Solution: Replace it with a valid index.
+
+GAUSS-00354: "index '%s' is not a btree"
+
+SQLSTATE: 42809
+
+Description: The index specified in the B-tree function is not a B-tree index.
+
+Solution: Use an index function corresponding to the index type.
+
+GAUSS-00355: "index '%s' does not have default sorting behavior"
+
+SQLSTATE: 42809
+
+Description: Usage not supported.
+
+Solution: Replace it with a valid index.
+
+GAUSS-00356: "inherited relation '%s' is not a table"
+
+SQLSTATE: 42809
+
+Description: The table specified in the **INHERITS** clause of the **CREATE TABLE … INHERITS parent_table** syntax is an invalid data table.
+
+Solution: Ensure that the table specified in the **INHERITS** clause of the **CREATE TABLE … INHERITS parent_table** syntax exists.
+
+GAUSS-00357: "column '%s' named in key does not exist"
+
+SQLSTATE: 42703
+
+Description: The column specified by the constraint or **INHERITS** clause of the **CREATE TABLE** syntax does not exist in a table.
+
+Solution: If the column does not exist, replace the inherited column name or re-create a table.
+
+GAUSS-00358: "column '%s' appears twice in primary key constraint"
+
+SQLSTATE: 42701
+
+Description: Two identical primary keys exist in the **UNIQUE** constraint specified in the **PRIMARY KEY** clause of the **CREATE TABLE … CONSTRAINT** syntax.
+
+Solution: Change or delete a primary key.
+
+GAUSS-00359: "column '%s' appears twice in unique constraint"
+
+SQLSTATE: 42701
+
+Description: Two identical primary keys exist in the **PRIMARY KEY** constraint specified in the **UNIQE** clause of the **CREATE TABLE … CONSTRAINT** syntax.
+
+Solution: Change or delete a primary key.
+
+<br/>
+
+## GAUSS-00361 - GAUSS-00370
+
+<br/>
+
+GAUSS-00361: "access method '%s' does not support column store"
+
+SQLSTATE: 0A000
+
+Description: The access method specified in the **CREATE INDEX…USING method** syntax does not support the column storage table.
+
+Solution: Modify the syntax to ensure that the access method can only be the psort type.
+
+GAUSS-00362: "index expression cannot return a set"
+
+SQLSTATE: 42804
+
+Description: The index expression of one or multiple columns specified in the **CREATE INDEX** syntax returns a set.
+
+Solution: Modify the syntax to ensure that the created index expression does not return a set.
+
+GAUSS-00363: "index expressions and predicates can refer only to the table being indexed"
+
+SQLSTATE: 42P10
+
+Description: The created expression of one or multiple columns based on this table specified in the **CREATE INDEX** syntax belongs to different tables.
+
+Solution: Ensure that the created expression of one or multiple columns based on this table specified in the **CREATE INDEX** syntax belongs to the same table.
+
+GAUSS-00364: "unrecognized event type: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00365: "rule WHERE condition cannot contain references to other relations"
+
+SQLSTATE: 42P17
+
+Description: The **WHERE** condition expression in the **CREATE RULE** syntax uses tables other than **NEW** and **OLD** for reference.
+
+Solution: Modify the syntax to ensure that the **WHERE** condition expression only use **NEW** and **OLD** for reference.
+
+GAUSS-00368: "Rule may not use NOTIFY, it is not yet supported"
+
+SQLSTATE: 42P17
+
+Description: The rule action command specified in the **CREATE RULE** syntax incorrectly uses the **NOTIFY** clause.
+
+Solution: Ensure that the rule action command specified in the **CREATE RULE** syntax contains only the **SELECT**, **INSERT**, **UPDATE**, or **DELETE** clause. Modify the syntax because the **NOTIFY** clause is not supported in the current version.
+
+GAUSS-00369: "rules with WHERE conditions can only have SELECT, INSERT, UPDATE, or DELETE actions"
+
+SQLSTATE: 42P17
+
+Description: The **CREATE RULE** syntax incorrectly uses the functional data definition statements, such as **CREATE**, **DESTROY**, **COPY**, and **VACUUM**.
+
+Solution: Do not use those statements. Currently, only the **SELECT**, **INSERT**, **UPDATE**, or **DELETE** clause is supported in the **CREATE RULE** syntax.
+
+GAUSS-00370: "conditional UNION/INTERSECT/EXCEPT statements are not implemented"
+
+SQLSTATE: 0A000
+
+Description: The query tree generated based on the user-created rule filters **UNION**, **INTERSECT**, and **EXCEPT**. Currently, this execution mode is not supported.
+
+Solution: Alternatively, rewrite the rule to avoid unsupported behavior. Contact technical support.
+
+<br/>
+
+## GAUSS-00371 - GAUSS-00380
+
+<br/>
+
+GAUSS-00371: "ON SELECT rule cannot use OLD"
+
+SQLSTATE: 42P17
+
+Description: The name of the referenced table in the **WHERE** condition expression of the **CREATE RULE name AS ON SELECT** syntax is **OLD**.
+
+Solution: Change the referenced table name to **non-OLD**.
+
+GAUSS-00372: "ON SELECT rule cannot use NEW"
+
+SQLSTATE: 42P17
+
+Description: The name of the referenced table in the **WHERE** condition expression of the **CREATE RULE name AS ON SELECT** syntax is **NEW**.
+
+Solution: Change the referenced table name to **non-NEW**.
+
+GAUSS-00373: "ON INSERT rule cannot use OLD"
+
+SQLSTATE: 42P17
+
+Description: The name of the referenced table in the **WHERE** condition expression of the **CREATE RULE name AS ON INSERT** syntax is **OLD**.
+
+Solution: Change the referenced table name to **non-OLD**.
+
+GAUSS-00374: "ON DELETE rule cannot use NEW"
+
+SQLSTATE: 42P17
+
+Description: The name of the referenced table in the **WHERE** condition expression of the **CREATE RULE name AS ON DELETE** syntax is **NEW**.
+
+Solution: Change the referenced table name to **non-NEW**.
+
+GAUSS-00377: "missing definition of adding partition"
+
+SQLSTATE: XX000
+
+Description: When the **ALTER TABLE ADD PARTITION** syntax is used to add a partition to a specified partitioned table, invalid values exist in the partition columns, indexes, constraints, or parent tables defined in the partition.
+
+Solution: Change invalid values to valid values.
+
+GAUSS-00378: "misplaced DEFERRABLE clause"
+
+SQLSTATE: 42601
+
+Description: The constraint types of columns specified by the **column_constraint** clause in the **CREATE TABLE** or **ALTER TABLE** syntax are deferrable types.
+
+Solution: Ensure that the constraint types of columns can be deferrable only when the types are primary key, UNIQUE, exclusion, or foreign key.
+
+GAUSS-00379: "multiple DEFERRABLE/NOT DEFERRABLE clauses not allowed"
+
+SQLSTATE: 42601
+
+Description: Deferrable types and non-deferrable types exist in the **column_constraint** clause of the **CREATE TABLE** or **ALTER TABLE** syntax.
+
+Solution: Modify the **column_constraint** clause to ensure that either deferrable types or non-deferrable types exist.
+
+GAUSS-00380: "misplaced NOT DEFERRABLE clause"
+
+SQLSTATE: 42601
+
+Description: The constraint types of columns specified by the **column_constraint** clause in the **CREATE TABLE** or **ALTER TABLE** syntax are non-deferrable types.
+
+Solution: Ensure that the constraint types of columns can be non-deferrable only when the types are primary key, UNIQUE, exclusion, or foreign key.
+
+<br/>
+
+## GAUSS-00381 - GAUSS-00390
+
+<br/>
+
+GAUSS-00381: "misplaced INITIALLY DEFERRED clause"
+
+SQLSTATE: 42601
+
+Description: Syntax error.
+
+Solution: Modify the SQL statement.
+
+GAUSS-00382: "multiple INITIALLY IMMEDIATE/DEFERRED clauses not allowed"
+
+SQLSTATE: 42601
+
+Description: Syntax error.
+
+Solution: Modify the SQL statement.
+
+GAUSS-00383: "misplaced INITIALLY IMMEDIATE clause"
+
+SQLSTATE: 42601
+
+Description: Syntax error.
+
+Solution: Modify the SQL statement.
+
+GAUSS-00384: "CREATE specifies a schema (%s) different from the one being created (%s)"
+
+SQLSTATE: 42P15
+
+Description: In the **CREATE SCHEMA schema_name schema_element…** syntax, the schema name contained in the **CREATE TABLE**, **CREATE VIEW**, **CREATE INDEX**, **CREATE PARTITION**, or **GRANT** clause specified by schema_element does not match **schema_name**.
+
+Solution: In the **CREATE SCHEMA schema_name schema_element…** syntax, ensure that the schema name contained in the **CREATE TABLE**, **CREATE VIEW**, **CREATE INDEX**, **CREATE PARTITION**, or **GRANT** clause specified by **schema_element** matches **schema_name**. "
+
+GAUSS-00385: "unsupport inherits clause for partitioned table"
+
+SQLSTATE: 42601
+
+Description: Syntax error.
+
+Solution: Modify the SQL statement.
+
+GAUSS-00386: "inherited relation '%s' is a foreign table"
+
+SQLSTATE: 42809
+
+Description: Usage not supported.
+
+Solution: Modify the SQL statement.
+
+GAUSS-00387: "inherited relation '%s' is a partitioned table"
+
+SQLSTATE: XX000
+
+Description: *parent_table* in the **CREATE TABLE table_name (…) INHERITS (parent_table [, … ])** syntax is a partitioned table.
+
+Solution: Ensure that the inherited *parent_table* required by the syntax is not a partitioned table.
+
+GAUSS-00389: "Typed table can't not be partitioned"
+
+SQLSTATE: 42601
+
+Description: The **CREATE … TABLE OF type_name …** syntax cannot be used in this version currently.
+
+Solution: Use other syntax.
+
+GAUSS-00390: "unsupported feature with temporary/unlogged table for partitioned table"
+
+SQLSTATE:42601
+
+Description: The partitioned table in the **CREATE TEMPORARY/UNLOGGED TABLE table_name …** syntax does not support the **TEMPORARY** or **UNLOGGED** attribute.
+
+Solution: Change the partitioned table to a non-partitioned table.
+
+<br/>
+
+## GAUSS-00391 - GAUSS-00400
+
+<br/>
+
+GAUSS-00392: "too many partition keys for partitioned table"
+
+SQLSTATE: 42P16
+
+Description: When a created table is a range partitioned table, the number of specified partition columns exceeds 4 (the maximum number).
+
+Solution: Ensure that the maximum number of partition columns is not greater than 4 when the created table is a range partitioned table.
+
+GAUSS-00393: "too many partitions for partitioned table"
+
+SQLSTATE: 42P16
+
+Description: When the **PARTITION BY RANGE(partition_key)(range_partition_definition_list)…** syntax is used to create a range partitioned table, the number of specified columns for partition values exceeds 32767 (the maximum number). "
+
+Solution: Ensure that the number of specified columns for partition values is not greater than 32767.
+
+GAUSS-00394: "Range partitioned table with INTERVAL was forbidden"
+
+SQLSTATE: 42P16
+
+Description: The **PARTITION BY RANGE(partition_key) INTERVAL** clause (interval partition) cannot be used in the current version.
+
+Solution: Do not use the PARTITION BY RANGE(partition_key) INTERVAL clause (interval partition) in the current version.
+
+GAUSS-00395: "Range partitioned table with INTERVAL clause has more than one column"
+
+SQLSTATE: 42P16
+
+Description: Usage not supported.
+
+Solution: Modify the SQL statement.
+
+GAUSS-00397: "duplicate partition name: '%s'"
+
+SQLSTATE: 42710
+
+Description: When the **PARTITION BY RANGE(partition_key)(range_partition_definition_list)…** syntax is used to create a range partitioned table, duplicate partition names exist in the specified lists for partition values.
+
+Solution: Check whether duplicate partition names exist in the specified lists for partition values. If yes, change the duplicate partition names.
+
+GAUSS-00398: "column '%s' appears twice in partial cluster key constraint"
+
+SQLSTATE: 42701
+
+Description: Duplicate column names exist in the **columnList** list of the **CREATE TABLE … CONSTRAINT PARTIAL CLUSTER KEY (columnList)** syntax.
+
+Solution: Change the duplicate column names.
+
+GAUSS-00399: "column name '%s' conflicts with a system column name"
+
+SQLSTATE: 42701
+
+Description: The column names specified in the **CREATE TABLE** syntax are the same as those retained in the system catalog.
+
+Solution: Change the column names as prompted to ensure that the column names are different.
+
+GAUSS-00400: "access method 'psort' does not support WHERE clause"
+
+SQLSTATE: 0A000
+
+Description: When psort is specified for the **INDEX** clause in the **CREATE INDEX** or **ALTER TABLE** syntax, the **INDEX** clause contains a **WHERE** clause.
+
+Solution: Modify the syntax to ensure that the **WHERE** clause does not exist.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/40-GAUSS-03901-GAUSS-04000.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/40-GAUSS-03901-GAUSS-04000.md
new file mode 100644
index 0000000000000000000000000000000000000000..028be1dcea1c206688f9e31ed3421beb3b56df09
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/40-GAUSS-03901-GAUSS-04000.md
@@ -0,0 +1,644 @@
+---
+title: GAUSS-03901 - GAUSS-04000
+summary: GAUSS-03901 - GAUSS-04000
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-03901 - GAUSS-04000
+
+<br/>
+
+## GAUSS-03901 - GAUSS-03910
+
+<br/>
+
+GAUSS-03903: "Resource Pool '%s': object already defined"
+
+SQLSTATE: 42710
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03906: "Can not alter default_pool"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03907: "cache lookup failed for pg_resource_pool %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03909: "Can not drop default_pool"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03910: "cannot drop resource pool '%s' because other objects depend on it"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03911 - GAUSS-03920
+
+<br/>
+
+GAUSS-03912: "Workload Group '%s': object already defined"
+
+SQLSTATE: 42710
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03915: "Can not alter default_group"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03916: "cache lookup failed for pg_workload_group %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03917: "must be system admin to remove workload groups "
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03918: "Can not drop default_group"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03919: "cannot drop workload group '%s' because other objects depend on it"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03920: "must be system admin to create application workload group mapping"
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03921 - GAUSS-03930
+
+<br/>
+
+GAUSS-03921: "Application Workload Group Mapping '%s': object can not create"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03922: "Application Workload Group Mapping '%s': object already defined"
+
+SQLSTATE: 42710
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03924: "must be system admin to change application workload group mapping"
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03925: "Application Workload Group Mapping '%s': object not defined"
+
+SQLSTATE: 42704
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03926: "Can not alter default_application"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03927: "cache lookup failed for pg_app_workloadgroup_mapping %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03928: "must be system admin to remove application workload group mapping."
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03929: "Can not drop default_application"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03931 - GAUSS-03940
+
+<br/>
+
+GAUSS-03935: "user mapping not found for '%s'"
+
+SQLSTATE: 42704
+
+Description: An error occurs when the foreign data wrapper is initialized.
+
+Solution: Check whether the settings of GDS, HDFS foreign tables, Roach, and OBS are correct. If not, an internal error occurs. Contact technical support.
+
+GAUSS-03936: "foreign-data wrapper handler function %u did not return an FdwRoutine struct"
+
+SQLSTATE: XX000
+
+Description: An error occurs when the foreign data wrapper is initialized.
+
+Solution: Check whether the settings of GDS, HDFS foreign tables, Roach, and OBS are correct. If not, an internal error occurs. Contact technical support.
+
+GAUSS-03937: "foreign-data wrapper '%s' has no handler"
+
+SQLSTATE: 55000
+
+Description: An error occurs when the foreign data wrapper is initialized.
+
+Solution: Check whether the settings of GDS, HDFS foreign tables, Roach, and OBS are correct. If they do not, an internal error occurred. Contact technical support.
+
+GAUSS-03940: "unexpected delimiter"
+
+SQLSTATE: F0000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03941 - GAUSS-03950
+
+<br/>
+
+GAUSS-03941: "unexpected end of line or lexeme"
+
+SQLSTATE: F0000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03943: "unexpected end of line"
+
+SQLSTATE: F0000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03944: "thesaurus sample word '%s' isn't recognized by subdictionary (rule %d)"
+
+SQLSTATE: F0000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03945: "thesaurus sample word '%s' is a stop word (rule %d)"
+
+SQLSTATE: F0000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03946: "thesaurus substitute word '%s' is a stop word (rule %d)"
+
+SQLSTATE: F0000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03947: "thesaurus substitute word '%s' isn't recognized by subdictionary (rule %d)"
+
+SQLSTATE: F0000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03948: "thesaurus substitute phrase is empty (rule %d)"
+
+SQLSTATE: F0000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03949: "multiple DictFile parameters"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03950: "multiple Dictionary parameters"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03951 - GAUSS-03960
+
+<br/>
+
+GAUSS-03951: "unrecognized Thesaurus parameter: '%s'"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03952: "missing DictFile parameter"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03953: "missing Dictionary parameter"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03954: "forbidden call of thesaurus or nested call"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03955: "invalid text search configuration file name '%s'"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03957: "text search parser does not support headline creation"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03958: "word is too long to be indexed"
+
+SQLSTATE: 54000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03959: "unrecognized synonym parameter: '%s'"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03960: "missing Synonyms parameter"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03961 - GAUSS-03970
+
+<br/>
+
+GAUSS-03962: "multiple AffFile parameters"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03963: "multiple StopWords parameters"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03964: "unrecognized Ispell parameter: '%s'"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03965: "missing AffFile parameter"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03966: "internal error in RS_isRegis: state %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03967: "invalid regis pattern: '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03968: "internal error in RS_compile: state %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-03971 - GAUSS-03980
+
+<br/>
+
+GAUSS-03971: "syntax error"
+
+SQLSTATE: F0000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03972: "unrecognized state in parse_affentry: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03974: "could not open affix file '%s': %m"
+
+SQLSTATE: F0000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03977: "multiple Accept parameters"
+
+SQLSTATE: 22023
+
+Description: Multiple accept parameters are entered.
+
+Solution: Check parameters.
+
+GAUSS-03978: "unrecognized simple dictionary parameter: '%s'"
+
+SQLSTATE: 22023
+
+Description: The input dictionary parameter is invalid.
+
+Solution: Check parameters.
+
+GAUSS-03979: "conversion from wchar_t to server encoding failed: %m"
+
+SQLSTATE: 22021
+
+Description: Failed to convert a wchar_t character to the server encoding method.
+
+Solution: Check the character to be converted.
+
+GAUSS-03980: "unrecognized headline parameter: '%s'"
+
+SQLSTATE: 22023
+
+Description: The input parameter cannot not be recognized by the **HighlightAll** command.
+
+Solution: Ensure that the input parameters for the **HighlightAll** command are **1**, **on**, **true**, **t**, **y**, or **yes**.
+
+<br/>
+
+## GAUSS-03981 - GAUSS-03990
+
+<br/>
+
+GAUSS-03981: "MinWords should be less than MaxWords"
+
+SQLSTATE: 22023
+
+Description: The input **min_words** value is greater than the **max_words** value.
+
+Solution: Modify the **min_words** and **max_words** values.
+
+GAUSS-03982: "MinWords should be positive"
+
+SQLSTATE: 22023
+
+Description: The input **min_words** value is less than 0.
+
+Solution: Ensure that the input **min_words** value is a positive number.
+
+GAUSS-03983: "ShortWord should be >= 0"
+
+SQLSTATE: 22023
+
+Description: The input **ShortWord** value is less than 0.
+
+Solution: Ensure that the **ShortWord** value is greater than or equal to 0.
+
+GAUSS-03984: "MaxFragments should be >= 0"
+
+SQLSTATE: 22023
+
+Description: The **MaxFragments** value is less than 0.
+
+Solution: Ensure that the **MaxFragments** value is greater than or equal to 0.
+
+GAUSS-03985: "Invalid formatter options '%s'"
+
+SQLSTATE: XX000
+
+Description: The data format is invalid.
+
+Solution: Check the data format and perform the operation again.
+
+GAUSS-03986: "locations can not use different protocols"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03987: "invalid file header location '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03988: "Loading mode '%s' not recognized"
+
+SQLSTATE: XX000
+
+Description: Failed to recognize the mode.
+
+Solution: Use the NORMAL, SHARED, or PRIVATE mode and perform the operation again.
+
+GAUSS-03989: "LOAD format '%s' not recognized"
+
+SQLSTATE: 22023
+
+Description: Failed to recognize the format.
+
+Solution: Use the TEXT, CSV, or FIXED format and perform the operation again.
+
+<br/>
+
+## GAUSS-03991 - GAUSS-04000
+
+<br/>
+
+GAUSS-03993: "location '%s' is invalid"
+
+SQLSTATE: 42000
+
+Description: The path format is incorrect.
+
+Solution: Ensure that the path format is correct and perform the operation again.
+
+GAUSS-03994: "SHARED mode can not use location '%s'"
+
+SQLSTATE: 42601
+
+Description: The SHARED mode does not support a remote path.
+
+Solution: Use the local path and perform the operation again.
+
+GAUSS-03995: "PRIVATE mode can not use location '%s'"
+
+SQLSTATE: 42601
+
+Description: The PRIVATE mode does not support a remote path.
+
+Solution: Use the local path and perform the operation again.
+
+GAUSS-03996: "Normal mode can not use location '%s'"
+
+SQLSTATE: 42601
+
+Description: The NORMAL mode does not support a remote path.
+
+Solution: Use the local path and perform the operation again.
+
+GAUSS-03997: "can not specify multiple local locations"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03998: "HEADER needs FILEHEADER specification in WRITE ONLY foreign table"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-03999: "can not scan a WRITE ONLY foreign table"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/41-GAUSS-04001-GAUSS-04100.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/41-GAUSS-04001-GAUSS-04100.md
new file mode 100644
index 0000000000000000000000000000000000000000..a730c935fe5df9a23648616606e5ed9409d2446d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/41-GAUSS-04001-GAUSS-04100.md
@@ -0,0 +1,724 @@
+---
+title: GAUSS-04001 - GAUSS-04100
+summary: GAUSS-04001 - GAUSS-04100
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-04001 - GAUSS-04100
+
+<br/>
+
+## GAUSS-04001 - GAUSS-04010
+
+<br/>
+
+GAUSS-04001: "invalid option '%s'"
+
+SQLSTATE: HV00D
+
+Description: The parameter option is invalid.
+
+Solution: Check the input parameter and perform the operation again.
+
+GAUSS-04002: "SHARED mode can only be used with TEXT format"
+
+SQLSTATE: XX000
+
+Description: The user attempts to use a format other than TEXT when using a GDS foreign table in SHARED mode.
+
+Solution: Modify the file format in the import specifications. The GDS foreign table where the error occurred can only read the TEXT file flow.
+
+GAUSS-04003: "can't find error record table '%s'"
+
+SQLSTATE: XX000
+
+Description: Failed to load the error record table because the system memory is insufficient.
+
+Solution: Perform the operation again after the OS reclaims partial memory.
+
+GAUSS-04005: "could not read from file: %m"
+
+SQLSTATE: XX000
+
+Description: The file does not exist or the relevant permission is incorrect.
+
+Solution: Ensure that the file exists and the permission is correct. Perform the operation again.
+
+GAUSS-04006: "unable to open URL '%s'"
+
+SQLSTATE: XX000
+
+Description: The file does not exist or the relevant permission is incorrect.
+
+Solution: Ensure that the file exists and the permission is correct. Perform the operation again.
+
+GAUSS-04007: "fill_missing_fields can't be set while '%s' is NOT NULL"
+
+SQLSTATE: 42601
+
+Description: The **fill_missing_fields** cannot be set for a non-null column.
+
+Solution: Check the input parameter and perform the operation again.
+
+GAUSS-04008: "unsupport BINARY format"
+
+SQLSTATE: XX000
+
+Description: Data in the BINARY format is not supported.
+
+Solution: Check the data format and perform the operation again.
+
+GAUSS-04009: "only both text && csv formats are supported for foreign table"
+
+SQLSTATE: 0A000
+
+Description: The foreign table supports only the data in TEXT and CSV formats.
+
+Solution: Check the data format contained in the foreign table and perform the operation again.
+
+GAUSS-04010: "%s doesn't exist, please create it first"
+
+SQLSTATE: XX000
+
+Description: The folder does not exist or the relevant permission is incorrect.
+
+Solution: Ensure that the folder exists and the permission is correct. Perform the operation again.
+
+<br/>
+
+## GAUSS-04011 - GAUSS-04020
+
+<br/>
+
+GAUSS-04011: "%s exists and is a file, please remove it first and create directory"
+
+SQLSTATE: XX000
+
+Description: The folder does not exist or the relevant permission is incorrect.
+
+Solution: Delete and create a folder or use other paths, and perform the operation again.
+
+GAUSS-04012: "location filepath is too long when importing data to foreign table"
+
+SQLSTATE: 22023
+
+Description: The folder path of the foreign table is too long.
+
+Solution: Use an appropriate path and perform the operation again.
+
+GAUSS-04014: "no Snowball stemmer available for language '%s' and encoding '%s'"
+
+SQLSTATE: 42704
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04015: "multiple Language parameters"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04016: "unrecognized Snowball parameter: '%s'"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04017: "missing Language parameter"
+
+SQLSTATE: 22023
+
+Description: The **Language** parameter is missing.
+
+Solution: Add the **Language** parameter and perform the operation again.
+
+GAUSS-04018: "could not translate host name '%s' to address: %s"
+
+SQLSTATE: XX000
+
+Description: Failed to convert the host name to an IP address.
+
+Solution: Check the host name configured in **hba.conf** and ensure that the IP address is correct.
+
+GAUSS-04019: "unsupported integer size %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04020: "no data left in message"
+
+SQLSTATE: 08P01
+
+Description: No data is left in the message.
+
+Solution: The internal communication of the database is abnormal. Contact technical support.
+
+<br/>
+
+## GAUSS-04021 - GAUSS-04030
+
+<br/>
+
+GAUSS-04021: "insufficient data left in message"
+
+SQLSTATE: 08P01
+
+Description: The remaining length of the message is smaller than the length obtained from the message.
+
+Solution: Check the current string.
+
+GAUSS-04022: "invalid string in message"
+
+SQLSTATE: 08P01
+
+Description: The message is invalid.
+
+Solution: The internal communication of the database is abnormal. Contact technical support.
+
+GAUSS-04023: "invalid message format"
+
+SQLSTATE: 08P01
+
+Description: The message format is invalid.
+
+Solution: The internal communication of the database is abnormal. Contact technical support.
+
+GAUSS-04024: "Postgres-XC does not support large object yet"
+
+SQLSTATE: 0A000
+
+Description: Large objects are not supported.
+
+Solution: Do not use this feature.
+
+GAUSS-04025: "invalid large-object descriptor: %d"
+
+SQLSTATE: 42704
+
+Description: The large-object descriptor is invalid.
+
+Solution: Do not use this feature.
+
+GAUSS-04026: "permission denied for large object %u"
+
+SQLSTATE: 42501
+
+Description: Large objects are not supported.
+
+Solution: Do not use this feature.
+
+GAUSS-04027: "large object descriptor %d was not opened for writing"
+
+SQLSTATE: 55000
+
+Description: Large objects are not supported.
+
+Solution: Do not use this feature.
+
+GAUSS-04028: "must be system admin to use server-side lo_import()"
+
+SQLSTATE: 42501
+
+Description: Only system administrators can use the **lo_import** function on the server.
+
+Solution: Do not use this feature.
+
+GAUSS-04029: "could not open server file '%s': %m"
+
+SQLSTATE: XX000
+
+Description: Failed to open a server file.
+
+Solution: Do not use this feature.
+
+GAUSS-04030: "could not read server file '%s': %m"
+
+SQLSTATE: XX000
+
+Description: Failed to read the server file.
+
+Solution: Do not use this feature.
+
+<br/>
+
+## GAUSS-04031 - GAUSS-04040
+
+<br/>
+
+GAUSS-04031: "must be system admin to use server-side lo_export()"
+
+SQLSTATE: 42501
+
+Description: Only system administrators can use the **lo_export** function on the server.
+
+Solution: Do not use this function.
+
+GAUSS-04032: "could not create server file '%s': %m"
+
+SQLSTATE: XX000
+
+Description: Failed to create the server file.
+
+Solution: Do not use this function.
+
+GAUSS-04033: "could not chmod server file '%s': %m"
+
+SQLSTATE: XX000
+
+Description: Failed to modify the server file permission.
+
+Solution: Do not use this function.
+
+GAUSS-04034: "could not write server file '%s': %m"
+
+SQLSTATE: XX000
+
+Description: Failed to write the server file.
+
+Solution: Do not use this function.
+
+GAUSS-04035: "connection requires a valid client certificate"
+
+SQLSTATE: 28000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04038: "pg_hba.conf rejects connection for host '%s', user '%s', database '%s', %s"
+
+SQLSTATE: 28000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04039: "pg_hba.conf rejects connection for host '%s', user '%s', database '%s'"
+
+SQLSTATE: 28000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04040: "no pg_hba.conf entry for host '%s', user '%s', database '%s', %s"
+
+SQLSTATE: 28000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04041 - GAUSS-04050
+
+<br/>
+
+GAUSS-04041: "no pg_hba.conf entry for host '%s', user '%s', database '%s'"
+
+SQLSTATE: 28000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04045: "Invalid username/password,login denied."
+
+SQLSTATE: 28000
+
+Description: The username or password is invalid and the login fails.
+
+Solution: Ensure that the username and password are valid.
+
+GAUSS-04047: "SSPI is not supported in protocol version 2"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04048: "out of memory"
+
+SQLSTATE: XX000
+
+Description: Failed to allocate the memory.
+
+Solution: Ensure that the system has sufficient memory.
+
+GAUSS-04050: "malloc failed"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04051 - GAUSS-04060
+
+<br/>
+
+GAUSS-04051: "could not set the cipher list (no valid ciphers available)"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04052: "sslciphers can not be null"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04053: "unrecognized ssl ciphers name: '%s'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04055: "could not load server certificate file '%s': %s"
+
+SQLSTATE: F0000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04057: "private key file '%s' has group or world access"
+
+SQLSTATE: F0000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04058: "could not load private key file '%s': %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04059: "check of private key '%s'failed: %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04061 - GAUSS-04070
+
+<br/>
+
+GAUSS-04061: "could not load the ca certificate file"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04062: "could not load root certificate file '%s': %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04063: "could not load SSL certificate revocation list file '%s': %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04068: "cipher file '%s' has group or world access"
+
+SQLSTATE: F0000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04069: "rand file '%s' has group or world access"
+
+SQLSTATE: F0000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04070: "spin.c does not support S_LOCK_FREE()"
+
+SQLSTATE: XX000
+
+Description:**S_LOCK_FREE ()** is not supported.
+
+Solution: Check whether the OS is supported.
+
+<br/>
+
+## GAUSS-04071 - GAUSS-04080
+
+<br/>
+
+GAUSS-04071: "not enough elements in RWConflictPool to record a read/write conflict"
+
+SQLSTATE: 53200
+
+Description: The RWConflictPool memory is insufficient and cannot record more read and write conflicts.
+
+Solution: Increase the **max_connections** value or try again in a new transaction.
+
+GAUSS-04072: "not enough elements in RWConflictPool to record a potential read/write conflict"
+
+SQLSTATE: 53200
+
+Description: The RWConflictPool memory is insufficient and cannot record more read and write conflicts.
+
+Solution: Increase the **max_connections** value or try again in a new transaction.
+
+GAUSS-04073: "not enough shared memory for elements of data structure '%s' (%lu bytes requested)"
+
+SQLSTATE: 53200
+
+Description: The memory is insufficient to initialize PredXactList.
+
+Solution: Check whether the system memory is sufficient.
+
+GAUSS-04074: "cannot use serializable mode in a hot standby"
+
+SQLSTATE: 0A000
+
+Description: Failed to set a hot standby to the serializable mode.
+
+Solution: Set **default_transaction_isolation** to **repeatable read**.
+
+GAUSS-04075: "a snapshot-importing transaction must not be READ ONLY DEFERRABLE"
+
+SQLSTATE: 0A000
+
+Description: READ ONLY DEFERRABLE cannot be imported into snapshots.
+
+Solution: Redefine the transaction level.
+
+GAUSS-04076: "could not serialize access due to read/write dependencies among transactions"
+
+SQLSTATE: 40001
+
+Description: The read and write operations conflict in serializable mode.
+
+Solution: Try again.
+
+GAUSS-04077: "unrecognized return value from HeapTupleSatisfiesVacuum: %u"
+
+SQLSTATE: XX000
+
+Description: Failed to recognize the returned value of **HeapTupleSatisfiesVacuum**.
+
+Solution:Contact technical support.
+
+GAUSS-04078: "deadlock seems to have disappeared"
+
+SQLSTATE: XX000
+
+Description: The deadlock abnormally disappears.
+
+Solution:Contact technical support.
+
+GAUSS-04079: "inconsistent results during deadlock check"
+
+SQLSTATE: XX000
+
+Description: The deadlock detection results are inconsistent.
+
+Solution:Contact technical support.
+
+GAUSS-04080: "deadlock detected"
+
+SQLSTATE: 40P01
+
+Description: A deadlock is detected.
+
+Solution: Run **SELECT pg_cancel_backend** to end the deadlock thread and perform the operation again.
+
+<br/>
+
+## GAUSS-04081 - GAUSS-04090
+
+<br/>
+
+GAUSS-04081: "proc header uninitialized"
+
+SQLSTATE: XX000
+
+Description: ProcGlobal is not initialized.
+
+Solution:Contact technical support.
+
+GAUSS-04082: "you already exist"
+
+SQLSTATE: XX000
+
+Description: The process has exited.
+
+Solution:Contact technical support.
+
+GAUSS-04084: "could not set timer for process wakeup"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04085: "Lock wait timeout: thread %lu on node %s waiting for %s on %s after %ld.%03d ms"
+
+SQLSTATE: YY002
+
+Description: The distributed lock waiting times out.
+
+Solution: Check the concurrent execution status.
+
+GAUSS-04086: "could not disable timer for process wakeup"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04087: "stuck spinlock (%p) detected at %s:%d"
+
+SQLSTATE: XX000
+
+Description: The spinlock has been suspended for a long time.
+
+Solution:Contact technical support.
+
+GAUSS-04089: "unrecognized lock mode: %d"
+
+SQLSTATE: XX000
+
+Description: Failed to recognize the lock mode.
+
+Solution:Contact technical support.
+
+GAUSS-04090: "cannot acquire lock mode %s on database objects while recovery is in progress"
+
+SQLSTATE: 55000
+
+Description: The applied lock level during the restoration is incorrect.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04091 - GAUSS-04100
+
+<br/>
+
+GAUSS-04091: "proclock table corrupted"
+
+SQLSTATE: XX000
+
+Description: The proclock hash table is damaged.
+
+Solution:Contact technical support.
+
+GAUSS-04092: "LockAcquire failed"
+
+SQLSTATE: XX000
+
+Description: Failed to obtain a common lock.
+
+Solution: Check the concurrent execution status.
+
+GAUSS-04093: "lock table corrupted"
+
+SQLSTATE: XX000
+
+Description: The lock hash table is damaged.
+
+Solution:Contact technical support.
+
+GAUSS-04094: "lock %s on object %u/%u/%u is already held"
+
+SQLSTATE: XX000
+
+Description: The object has been locked.
+
+Solution: Check the lock status of the object.
+
+GAUSS-04095: "locallock table corrupted"
+
+SQLSTATE: XX000
+
+Description: The locallock hash table is damaged.
+
+Solution:Contact technical support.
+
+GAUSS-04096: "failed to re-find shared lock object"
+
+SQLSTATE: XX000
+
+Description: Failed to find the shared lock again.
+
+Solution:Contact technical support.
+
+GAUSS-04097: "failed to re-find shared proclock object"
+
+SQLSTATE: XX000
+
+Description: Failed to find the shared proclock again.
+
+Solution:Contact technical support.
+
+GAUSS-04098: "too many conflicting locks found"
+
+SQLSTATE: XX000
+
+Description: The number of common lock conflicts is greater than the **MaxBackends** value.
+
+Solution: Reduce the service concurrency.
+
+GAUSS-04099: "cannot PREPARE while holding both session-level and transaction-level locks on the same object"
+
+SQLSTATE: 0A000
+
+Description: You cannot hold session-level and transaction-level locks for the same object at the same time.
+
+Solution: Check the lock status of the object.
+
+GAUSS-04100: "we seem to have dropped a bit somewhere"
+
+SQLSTATE: XX000
+
+Description: The masks of holding and releasing the lock do not match.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/42-GAUSS-04101-GAUSS-04200.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/42-GAUSS-04101-GAUSS-04200.md
new file mode 100644
index 0000000000000000000000000000000000000000..e0883afef34ebbdc37b3f56e669f993f60008247
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/42-GAUSS-04101-GAUSS-04200.md
@@ -0,0 +1,478 @@
+---
+title: GAUSS-04101 - GAUSS-04200
+summary: GAUSS-04101 - GAUSS-04200
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-04101 - GAUSS-04200
+
+<br/>
+
+## GAUSS-04101 - GAUSS-04110
+
+<br/>
+
+GAUSS-04102: "too many LWLocks taken"
+
+SQLSTATE: XX000
+
+Description: Too many lightweight locks exist.
+
+Solution: Reduce the service concurrency.
+
+GAUSS-04103: "cannot wait without a PGPROC structure"
+
+SQLSTATE: XX000
+
+Description:**MyProc** is **NULL**.
+
+Solution:Contact technical support.
+
+GAUSS-04107: "invalid flags: %d"
+
+SQLSTATE: XX000
+
+Description: An error occurred when you open the large object flag.
+
+Solution:Contact technical support.
+
+GAUSS-04108: "null field found in pg_largeobject"
+
+SQLSTATE: XX000
+
+Description: A large object is incorrectly recorded in **pg_largeobject**.
+
+Solution: Check **pg_largeobject**.
+
+GAUSS-04109: "invalid seek offset: %d"
+
+SQLSTATE: XX000
+
+Description: The access offset of a large object is incorrect.
+
+Solution:Contact technical support.
+
+GAUSS-04110: "invalid whence: %d"
+
+SQLSTATE: XX000
+
+Description: The access flag of a large object is incorrect.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04111 - GAUSS-04120
+
+<br/>
+
+GAUSS-04111: "large object %u was not opened for writing"
+
+SQLSTATE: 55000
+
+Description: The large object is not opened.
+
+Solution:Contact technical support.
+
+GAUSS-04113: "no empty local buffer available"
+
+SQLSTATE: 53000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04118: "cannot access temporary tables of other sessions"
+
+SQLSTATE: 0A000
+
+Description: The temporary tables of other sessions are not supported.
+
+Solution: Use temporary or common tables for the current session.
+
+GAUSS-04119: "unexpected data beyond EOF in block %u of relation %s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04121 - GAUSS-04130
+
+<br/>
+
+GAUSS-04121: "buffer is pinned in InvalidateBuffer"
+
+SQLSTATE: XX010
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04122: "bad buffer ID: %d"
+
+SQLSTATE: XX010
+
+Description: The bufid is incorrect.
+
+Solution: A preventive error mechanism. Contact technical support.
+
+GAUSS-04123: "unrecognized buffer lock mode: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04124: "incorrect local pin count: %d"
+
+SQLSTATE: XX010
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04125: "multiple backends attempting to wait for pincount 1"
+
+SQLSTATE: XX010
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04126: "no unpinned buffers available"
+
+SQLSTATE: XX010
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04127: "unrecognized buffer access strategy: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04128: "malloc fails, out of memory"
+
+SQLSTATE: XX000
+
+Description: The system memory is insufficient and the memory fails to be allocated.
+
+Solution: Perform the operation again after the OS reclaims partial memory.
+
+GAUSS-04129: "Could not open file '%s': %m"
+
+SQLSTATE: XX000
+
+Description: Failed to open the column-store file.
+
+Solution: Contact technical support. Alternatively, check the file that failed to be opened based on the error message.
+
+<br/>
+
+## GAUSS-04131 - GAUSS-04140
+
+<br/>
+
+GAUSS-04131: "flush file '%s' failed: %m"
+
+SQLSTATE: XX000
+
+Description: Failed to write the column-store file.
+
+Solution: Contact technical support. Alternatively, check the file that failed to be written based on the error message.
+
+GAUSS-04134: "memory is not enough during decompressing CU for integer type %d"
+
+SQLSTATE: XX000
+
+Description: The memory for decompressing column-store CU is insufficient.
+
+Solution: Contact technical support. Alternatively, increase the value of the memory configuration parameter of the database.
+
+GAUSS-04135: "data corrupts during decompressing CU for integer type %d"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04138: "could not initialize CStore Column space desc hash table"
+
+SQLSTATE: XX000
+
+Description: Failed to initialize the idle space hash table in column-store mode.
+
+Solution: Restart the database.
+
+GAUSS-04139: "No CUID is left for new CU in relation '%u'. Please execute the VACUUM FULL before do anything else"
+
+SQLSTATE: XX000
+
+Description: No CUID is left for new CU.
+
+Solution: Perform the operation again after the **VACUUM** is successfully executed.
+
+GAUSS-04140: "build global column space cache hash table failed"
+
+SQLSTATE: XX000
+
+Description: Failed to initialize the idle space hash table in column-store mode.
+
+Solution: Restart the database.
+
+<br/>
+
+## GAUSS-04141 - GAUSS-04150
+
+<br/>
+
+GAUSS-04141: "unsupported byval length: %d"
+
+SQLSTATE: XX000
+
+Description: The data type is not supported for row-store dictionary compression.
+
+Solution: Check the data type.
+
+GAUSS-04146: "corrupted item pointer: offset = %u, size = %u"
+
+SQLSTATE: XX001
+
+Description: The structure of the index page is damaged.
+
+Solution:Contact technical support.
+
+GAUSS-04147: "incorrect index offsets supplied"
+
+SQLSTATE: XX000
+
+Description: The location of the index tuple to be deleted is invalid on the page.
+
+Solution: Try again.
+
+GAUSS-04148: "no free slots in PMChildFlags array"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04149: "canceling statement due to conflict with recovery"
+
+SQLSTATE: 40P01
+
+Description: The connection is cancelled due to the conflict with recovery.
+
+Solution: Reconnect to the database and enter the command again.
+
+<br/>
+
+## GAUSS-04151 - GAUSS-04160
+
+<br/>
+
+GAUSS-04152: "GTM error, could not obtain snapshot"
+
+SQLSTATE: 08006
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04156: "should be attached to shared memory already"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04157: "can not malloc memory for HeapmemIndexHeapmemIndex (%lu bytes requested)"
+
+SQLSTATE: 53200
+
+Description: Failed to create the shared cache because the system memory is insufficient.
+
+Solution: Perform the operation again after the OS reclaims partial memory.
+
+GAUSS-04158: "could not create HeapMemIndex entry for data structure '%s'"
+
+SQLSTATE: 53200
+
+Description: Failed to create the shared cache metadata because the system memory is insufficient.
+
+Solution: Perform the operation again after the OS reclaims partial memory.
+
+GAUSS-04159: "HeapMemIndex entry size is wrong for data structure '%s': expected %lu, actual %lu"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04160: "not enough heap memory for data structure '%s' (%lu bytes requested)"
+
+SQLSTATE: 53200
+
+Description: Failed to create the shared cache metadata because the system memory is insufficient.
+
+Solution: Perform the operation again after the OS reclaims partial memory.
+
+<br/>
+
+## GAUSS-04161 - GAUSS-04170
+
+<br/>
+
+GAUSS-04161: "not enough shared memory for data structure '%s' (%lu bytes requested)"
+
+SQLSTATE: 53200
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04162: "could not create ShmemIndex entry for data structure '%s'"
+
+SQLSTATE: 53200
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04163: "ShmemIndex entry size is wrong for data structure '%s': expected %lu, actual %lu"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04165: "could not initialize shared file id hash table"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04166: "insufficient file descriptors available to start server process"
+
+SQLSTATE: 53000
+
+Description: File handles are insufficient to start the server process.
+
+Solution: Set the OS file handles to a reasonable value and restart the database.
+
+GAUSS-04167: "could not close file '%s': %m"
+
+SQLSTATE: XX000
+
+Description: Failed to close a specified file.
+
+Solution: Ensure that the specified file is not damaged and the permission is sufficient.
+
+GAUSS-04168: "file cache corrupted, file %s not opened with handle: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04171 - GAUSS-04180
+
+<br/>
+
+GAUSS-04171: "temporary file size exceeds temp_file_limit (%dkB)"
+
+SQLSTATE: 53400
+
+Description: The temporary file size exceeds the upper limit.
+
+Solution: Set the configuration item **temp_file_limit** to a reasonable value and perform the operation again.
+
+GAUSS-04173: "Invalid socket fd '%d' for poll():%m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04174: "'%s:%d' connect failed"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04176: "AllocateDesc kind not recognized"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04178: "could not read directory '%s': %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04191 - GAUSS-04200
+
+<br/>
+
+GAUSS-04192: "could not open file '%s' (target block %u): %m"
+
+SQLSTATE: XX000
+
+Description: Failed to open the file. An I/O error occurred.
+
+Solution: Check whether the file handle resources are insufficient.
+
+GAUSS-04196: "invalid string enlargement request size: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04197: "bind message has %d result formats but query has %d columns"
+
+SQLSTATE: 08P01
+
+Description: The exported number of columns is inconsistent with the required number of columns.
+
+Solution: Check the query.
+
+GAUSS-04200: "unsupported portal strategy: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/43-GAUSS-04201-GAUSS-04300.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/43-GAUSS-04201-GAUSS-04300.md
new file mode 100644
index 0000000000000000000000000000000000000000..616a9bfd84434a2c0901674e31bda502073c1288
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/43-GAUSS-04201-GAUSS-04300.md
@@ -0,0 +1,692 @@
+---
+title: GAUSS-04201 - GAUSS-04300
+summary: GAUSS-04201 - GAUSS-04300
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-04201 - GAUSS-04300
+
+<br/>
+
+## GAUSS-04201 - GAUSS-04210
+
+<br/>
+
+GAUSS-04201: "unsupported portal strategy"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04202: "bogus direction"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04203: "invalid argument size %d in function call message"
+
+SQLSTATE: 08P01
+
+Description: An invalid parameter value (**argsize** is less than -1) is entered when the function is called.
+
+Solution: Check the number of parameters called by the function.
+
+GAUSS-04204: "function %s has more than %d arguments"
+
+SQLSTATE: XX000
+
+Description: The SQL parameter is incorrect.
+
+Solution: Modify the SQL statement.
+
+GAUSS-04205: "current transaction is aborted, commands ignored until end of transaction block"
+
+SQLSTATE: 25P02
+
+Description: Non-commit and rollback commands are run when the transaction is rolled back.
+
+Solution: Ensure that the previous transaction has been submitted or rolled back when the SQL statement is executed.
+
+GAUSS-04206: "function call message contains %d arguments but function requires %d"
+
+SQLSTATE: 08P01
+
+Description: When the function is called, the number of parameters entered is inconsistent with that defined by the function.
+
+Solution: Check the number of parameters called by the function.
+
+GAUSS-04207: "function call message contains %d argument formats but %d arguments"
+
+SQLSTATE: 08P01
+
+Description: When the function is called, the number of formatted parameters entered is inconsistent with that defined by the function.
+
+Solution: Check the number of parameters called by the function.
+
+GAUSS-04208: "incorrect binary data format in function argument %d"
+
+SQLSTATE: 22P03
+
+Description: Incorrect binary data format is found in the parameters of the function.
+
+Solution: Check the format of parameters called by the function.
+
+GAUSS-04209: "invalid frontend message type %d"
+
+SQLSTATE: 08P01
+
+Description: The message type is invalid.
+
+Solution: Ensure that the input message type is valid.
+
+GAUSS-04210: "could not set timer for session timeout"
+
+SQLSTATE: 58000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04211 - GAUSS-04220
+
+<br/>
+
+GAUSS-04211: "could not disable timer for session timeout"
+
+SQLSTATE: 58000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04214: "bind message has %d parameter formats but %d parameters"
+
+SQLSTATE: 08P01
+
+Description: The number of bound parameters is inconsistent with the number of accepted parameters when the API is used.
+
+Solution: Ensure that the number of accepted parameters is consistent with the number of predicted parameters.
+
+GAUSS-04215: "cannot insert multiple commands into a prepared statement"
+
+SQLSTATE: 42601
+
+Description: Multiple commands are inserted in the prepared statement.
+
+Solution: Insert only one command.
+
+GAUSS-04217: "bind message supplies %d parameters, but prepared statement '%s' requires %d"
+
+SQLSTATE: 08P01
+
+Description: The number of parameters provided by the bind message is incorrect.
+
+Solution: Provide the correct parameter.
+
+GAUSS-04218: "incorrect binary data format in bind parameter %d"
+
+SQLSTATE: 22P03
+
+Description: Incorrect binary data is found in the bind parameter.
+
+Solution: Provide the correct parameter.
+
+GAUSS-04219: "portal '%s' does not exist"
+
+SQLSTATE: 34000
+
+Description: The portal does not exist.
+
+Solution: Specify a correct portal name.
+
+GAUSS-04220: "floating-point exception"
+
+SQLSTATE: 22P01
+
+Description: The floating point number is incorrect. For example, the value is out of range or divided by 0.
+
+Solution: Enter a valid floating point number.
+
+<br/>
+
+## GAUSS-04221 - GAUSS-04230
+
+<br/>
+
+GAUSS-04221: "unrecognized conflict mode: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04222: "terminating autovacuum process due to administrator command"
+
+SQLSTATE: 57P01
+
+Description: The **autovacuum** process is terminated by the administrator.
+
+Solution: Contact the system administrator to check whether the **autovacuum** process is terminated. Let the administrator to restart the process if it has been terminated.
+
+GAUSS-04223: "terminating connection due to conflict with recovery"
+
+SQLSTATE: 40001
+
+Description: The current request conflicts with the data recovery process performed on the database server. The requested connection fails.
+
+Solution: Try to reconnect the database later and run the command again.
+
+GAUSS-04224: "terminating connection due to conflict with recovery"
+
+SQLSTATE: 57P04
+
+Description: The current request conflicts with the data recovery process performed on the database server. The requested connection fails.
+
+Solution: Try to reconnect the database later and run the command again.
+
+GAUSS-04225: "terminating connection due to administrator command"
+
+SQLSTATE: 57P01
+
+Description: The administrator terminates the current connection.
+
+Solution: Contact the system administrator to obtain the reason why the connection is terminated.
+
+GAUSS-04226: "connection to client lost"
+
+SQLSTATE: 08006
+
+Description: The connection is lost.
+
+Solution: Check whether the network connection is normal.
+
+GAUSS-04229: "canceling autovacuum task"
+
+SQLSTATE: 57014
+
+Description: The **autovauum** task is cancelled.
+
+Solution: Find the reason why the process is cancelled.
+
+GAUSS-04230: "canceling statement due to conflict with recovery"
+
+SQLSTATE: 40001
+
+Description: The connection is cancelled due to the conflict with recovery.
+
+Solution: Reconnect to the database and enter the command again.
+
+<br/>
+
+## GAUSS-04231 - GAUSS-04240
+
+<br/>
+
+GAUSS-04231: "canceling statement due to %s request"
+
+SQLSTATE: 57014
+
+Description: The user or a CN cancels this operation.
+
+Solution: Ensure that the reason to cancel the operation is valid. If the operation needs to be canceled, ignore the error. If the operation cancellation is abnormal, analyze the error and rectify it.
+
+GAUSS-04232: "stack depth limit exceeded"
+
+SQLSTATE: 54001
+
+Description: The stack depth exceeds the upper limit, that is, the value of **max_stack_depth_bytes** (the default value is **100x1024**).
+
+Solution: Ensure that the depth of the recursive call function is proper. If the depth is out of limit, expand **max_stack_depth_bytes**.
+
+GAUSS-04233: "local xids can be used only in single user mode"
+
+SQLSTATE: 42601
+
+Description: The local XID can be used only in single-user mode.
+
+Solution: The **-single** parameter needs to be added.
+
+GAUSS-04235: "invalid command-line argument for server process: %s"
+
+SQLSTATE: 42601
+
+Description: An invalid command-line parameter is entered for the server process.
+
+Solution: Use **-help** to check the parameter function and enter the correct parameter.
+
+GAUSS-04236: "%s: invalid command-line argument: %s"
+
+SQLSTATE: 42601
+
+Description: An invalid command-line parameter is entered when the database is being connected.
+
+Solution: Use **-help** to check the parameter function and enter the correct parameter.
+
+GAUSS-04238: "%s: no database nor user name specified"
+
+SQLSTATE: 22023
+
+Description: Neither the database nor the username is specified when the database is being connected.
+
+Solution: Add the database and username parameter.
+
+GAUSS-04239: "invalid CLOSE message subtype %d"
+
+SQLSTATE: 08P01
+
+Description: An invalid **CLOSE** command is entered in the front end or the standard input.
+
+Solution: Ensure the type of **CLOSE** is **S** or **P**.
+
+GAUSS-04240: "invalid DESCRIBE message subtype %d"
+
+SQLSTATE: 08P01
+
+Description: An invalid **DESCRIBE** command is entered in the front end or the standard input.
+
+Solution: Ensure the type of **DESCRIBE** is **S** or **P**.
+
+<br/>
+
+## GAUSS-04241 - GAUSS-04250
+
+<br/>
+
+GAUSS-04241: "Invalid command received"
+
+SQLSTATE: XX000
+
+Description: An invalid command capitalized with **b** (not bP, bX, or bE) is entered in the front end or the standard input.
+
+Solution: Enter the correct command.
+
+GAUSS-04242: "cannot execute %s in a read-only transaction"
+
+SQLSTATE: 25006
+
+Description: The update database type operation is performed in a read-only transaction.
+
+Solution: Ensure that the update type operation is performed in non-read-only transactions.
+
+GAUSS-04243: "cannot execute %s during recovery"
+
+SQLSTATE: 25006
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04244: "cannot execute %s within security-restricted operation"
+
+SQLSTATE: 42501
+
+Description: Security-restricted operations are executed.
+
+Solution:Contact technical support.
+
+GAUSS-04245: "Invalid transaciton_id to prepare."
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04247: "non-DECLARE CURSOR PlannedStmt passed to ProcessUtility"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04248: "CREATE not supported for TEMP and non-TEMP objects"
+
+SQLSTATE: 0A000
+
+Description: A statement is used for supporting both temporary and non-temporary objects.
+
+Solution: Change the SQL statement and use multiple statements to support temporary and non-temporary objects.
+
+GAUSS-04249: "Postgres-XC does not support FOREIGN DATA WRAPPER yet"
+
+SQLSTATE: 0A000
+
+Description: The **FOREIGN DATA WRAPPER** is not supported.
+
+Solution: Internal system error.Contact technical support.
+
+GAUSS-04250: "Postgres-XC does not support USER MAPPING yet"
+
+SQLSTATE: 0A000
+
+Description: The **CREATE USER MAPPING** is not supported.
+
+Solution: Do not use **CREATE USER MAPPING**.
+
+<br/>
+
+## GAUSS-04251 - GAUSS-04260
+
+<br/>
+
+GAUSS-04251: "PGXC does not support concurrent INDEX yet"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04253: "unrecognized alter domain type: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04254: "PGXC does not support GRANT on multiple object types"
+
+SQLSTATE: 0A000
+
+Description: The MogDB **GRANT** syntax does not support performing the view and table operations at the same time.
+
+Solution: Specify only one type of objects (table or view) at a time.
+
+GAUSS-04255: "unrecognized define stmt type: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04257: "DROP not supported for TEMP and non-TEMP objects"
+
+SQLSTATE: 0A000
+
+Description: The **DROP** statement cannot drop temporary and non-temporary objects at the same time.
+
+Solution: Drop temporary objects and non-temporary objects respectively.
+
+GAUSS-04258: "%s is not yet supported."
+
+SQLSTATE: 0A000
+
+Description: The features in the blacklist are not supported when the **support_extended_features** switch is set to **off**.
+
+Solution: Set the **support_extended_features** switch to **on** and do not perform the alter or delete operation on the objects in the blacklist.
+
+GAUSS-04260: "Failed to send snapshot to Datanode %u"
+
+SQLSTATE: XX000
+
+Description: Internal system error. Failed to send the snapshot to the DN.
+
+Solution: Internal system error. Contact technical support.
+
+<br/>
+
+## GAUSS-04261 - GAUSS-04270
+
+<br/>
+
+GAUSS-04261: "Failed to send queryid to Datanode %u"
+
+SQLSTATE: XX000
+
+Description: Communication error.
+
+Solution: Check the network status or whether any node fault occurs.
+
+GAUSS-04265: "delete or update failed because lock conflict"
+
+SQLSTATE: XX000
+
+Description: The deletion and update conditions are complex. As a result, the two rows in the same CU are deleted or updated with a long interval, and a lock conflict occurs while a tuple is deleted or updated.
+
+Solution: Modify the deletion and update conditions to simplify execution.
+
+GAUSS-04266: "delete or update row conflict"
+
+SQLSTATE: XX000
+
+Description: Data is deleted or updated multiple times.
+
+Solution: Ensure that no row is deleted or updated multiple times.
+
+GAUSS-04267: "GiST page split into too many halves (%d, maximum %d)"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04270: "PER NODE REJECT LIMIT must be greater than 0"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04271 - GAUSS-04280
+
+<br/>
+
+GAUSS-04271: "Invalid name \'%s\' in REMOTE LOG"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04272: "PER NODE REJECT LIMIT only available on READ ONLY foreign table"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04273: "PER NODE REJECT LIMIT only available with LOG INTO or REMOTE LOG"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04275: "REMOTE LOG only available on in NORMAL mode"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04276: "FILL_MISSING_FIELDS only available on READ ONLY foreign table"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04277: "MODE only available on READ ONLY foreign table"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04279: "can not specify relative local locations"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04280: "could not fetch expected length:%m"
+
+SQLSTATE: XX000
+
+Description: An error occurs when error data is recorded in the error table.
+
+Solution: Locate the data row where the error occurred based on the error context and check whether invalid characters exist. Contact technical support.
+
+<br/>
+
+## GAUSS-04281 - GAUSS-04290
+
+<br/>
+
+GAUSS-04283: "pg_largeobject entry for OID %u, page %d has invalid data field size %d"
+
+SQLSTATE: XX001
+
+Description: The length of the fragment of a large object is invalid and the data is damaged.
+
+Solution: Contact technical support. Alternatively, try using backup data to restore the data.
+
+GAUSS-04284: "exceeded maxAllocatedDescs (%d) while trying to open file '%s:%d'"
+
+SQLSTATE: 53000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04285: "exceeded maxAllocatedDescs (%d) while trying to open file '%s'"
+
+SQLSTATE: 53000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04286: "exceeded maxAllocatedDescs (%d) while trying to open directory '%s'"
+
+SQLSTATE: 53000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04287: "must have at least one column"
+
+SQLSTATE: 0A000
+
+Description: The **CREATE TABLE** syntax does not specify the column information of the table.
+
+Solution: Ensure that at least one column is specified in the **CREATE TABLE ***table_name\***(***{column_name data_type}\***)** syntax.
+
+GAUSS-04290: "length of field '%s' longer than limit of \'%d\'"
+
+SQLSTATE: 22P04
+
+Description: The length of the column in a GDS foreign table exported in FIXED format is greater than the declared table length.
+
+Solution: Modify the foreign table definition based on the error message.
+
+<br/>
+
+## GAUSS-04291 - GAUSS-04300
+
+<br/>
+
+GAUSS-04291: "tsquery is too large"
+
+SQLSTATE: 54000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04292: "bit string length exceeds the maximum allowed (%d)"
+
+SQLSTATE: 54000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04293: "language validation function %u called for language %u instead of %u"
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04294:"The name of memory context is too long(>=%dbytes)"
+
+SQLSTATE: 42602
+
+Description: The name of the memory context exceeds the limit **MEMORY_CONTEXT_NAME_LEN**.
+
+Solution: Ensure that the memory context is valid.
+
+GAUSS-04295:"Fail to send signal to backend(tid:%lu). "
+
+SQLSTATE: XX000
+
+Description: Failed to send an internal signal to the backend thread.
+
+Solution: The backend may have exited. Let the user check whether the backend exists.
+
+GAUSS-04296:"out of memory when preparing zlib encoder. "
+
+SQLSTATE: 53200
+
+Description: Failed to allocate a large volume of memory required for compression because the system memory is insufficient.
+
+Solution: Release unnecessary processes in the system and import data again.
+
+GAUSS-04297:"level %d is invalid when preparing zlib encoder. "
+
+SQLSTATE: XX000
+
+Description: The zlib compression level is incorrect.
+
+Solution: Use the low or middle compression level during the import.
+
+GAUSS-04298: "version is incompatible when preparing zlib encoder."
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04299:"error %d occurs when preparing zlib encoder. "
+
+SQLSTATE: XX000
+
+Description: System resources are insufficient.
+
+Solution: Release unnecessary memory in the system and import data again.
+
+GAUSS-04300:"RLE decompress failed, expected bytes %d, real size %d "
+
+SQLSTATE: XX001
+
+Description: The data is damaged.
+
+Solution: Use backed up data for restoration.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/44-GAUSS-04301-GAUSS-04400.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/44-GAUSS-04301-GAUSS-04400.md
new file mode 100644
index 0000000000000000000000000000000000000000..f2d4ecf11e81a9905e8581005db50b0678621e8c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/44-GAUSS-04301-GAUSS-04400.md
@@ -0,0 +1,444 @@
+---
+title: GAUSS-04301 - GAUSS-04400
+summary: GAUSS-04301 - GAUSS-04400
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-04301 - GAUSS-04400
+
+<br/>
+
+## GAUSS-04301 - GAUSS-04310
+
+<br/>
+
+GAUSS-04308: "%s: could not locate bin path"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04311 - GAUSS-04320
+
+<br/>
+
+GAUSS-04325: "Parallel Function: Failed to send command to Datanode %u"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04321 - GAUSS-04330
+
+<br/>
+
+GAUSS-04321: "Failed to receive GTM commit transaction response after %s.
+
+SQLSTATE: XX000
+
+Description: Failed to obtain the feedback information to notify the GTM to submit a transaction due to GTM disconnection.
+
+Solution: Check whether the connection between the GTM and other instances is normal.
+
+GAUSS-04325: "Parallel Function: Failed to send command to Datanode %u "
+
+SQLSTATE: XX000
+
+Description: Failed to send the SQL statement or plan to the DN.
+
+Solution: Internal system error. Contact technical support.
+
+GAUSS-04326: "Parallel Function: Failed to read response from Datanodes Detail: %s\n"
+
+SQLSTATE: XX000
+
+Description: Failed to receive responses from the peer DN.
+
+Solution: Check whether a node is faulty or whether the network connection is normal, and then troubleshoot accordingly.
+
+GAUSS-04330: "pooler: Failed to send SIGTERM to postgres thread:%lu in PoolManagerAbortTransactions(), failed: %m"
+
+SQLSTATE: XX000
+
+Description: Failed to send an internal signal to the backend thread.
+
+Solution: Send the signal again.
+
+<br/>
+
+## GAUSS-04331 - GAUSS-04340
+
+<br/>
+
+GAUSS-04333: "pooler: invalid cn/dn node number, input cn: %d, dn: %d; current cn: %d, dn: %d"
+
+SQLSTATE: 08006
+
+Description: The parameter type is invalid.
+
+Solution: This is an error set to prevent internal program logic errors during the development process. The development personnel must locate the error once it occurs.
+
+GAUSS-04335: "pooler: Communication failure, failed to send session commands or invalid incoming data."
+
+SQLSTATE: 08000
+
+Description: A connection error occurs. The communication with the DN fails.
+
+Solution: Perform the query again.
+
+GAUSS-04336: "pooler: Failed to duplicate fd, error: %s"
+
+SQLSTATE: XX000
+
+Description: An internal system error occurs. The number of handles opened in the process is probably restricted.
+
+Solution: Change the system settings to increase the number of handles that can be opened by processes.
+
+GAUSS-04339: "pooler: Failed to reset agent!"
+
+SQLSTATE: XX000
+
+Description: The memory context is incorrect.
+
+Solution: Perform the query again.
+
+<br/>
+
+## GAUSS-04341 - GAUSS-04350
+
+<br/>
+
+GAUSS-04342: "concurrent update under Stream mode is not yet supported"
+
+SQLSTATE: 0A000
+
+Description: Concurrent update operations are not supported in stream mode.
+
+Solution: Set the **enable_stream_operator** switch to **off**, or prevent concurrent update operations in stream mode.
+
+GAUSS-04344: "cannot read results"
+
+SQLSTATE: XX000
+
+Description: Internal system error. Data cannot be read.
+
+Solution:Contact technical support.
+
+GAUSS-04345: "Operator with OID %u dose not exist."
+
+SQLSTATE: XX000
+
+Description: The operator does not exist.
+
+Solution: Use correct operators. For example, **+** and **-**.
+
+GAUSS-04348: "%s is redistributing, please retry later."
+
+SQLSTATE: 0A000
+
+Description: Tables that are being redistributed do not support other DDL operations other than import.
+
+Solution: Wait until the redistribution of the redistributed table is complete and try again.
+
+GAUSS-04350: "duplicated URL '%s' in LOCATION"
+
+SQLSTATE: XX000
+
+Description: The URL used by GDS is duplicate.
+
+Solution: Ensure that the URL used by GDS is different from the existing URL.
+
+<br/>
+
+## GAUSS-04351 - GAUSS-04360
+
+<br/>
+
+GAUSS-04351: "IGNORE_EXTRA_DATA only available on READ ONLY foreign table"
+
+SQLSTATE: 42601
+
+Description:**IGNORE_EXTRA_DATA** is used in **OPTIONS** when a writable foreign table is created.
+
+Solution: Do not use **IGNORE_EXTRA_DATA** in **OPTIONS**.
+
+GAUSS-04352: "Permission denied to drop resource pools."
+
+SQLSTATE: 42501
+
+Description: Common users are not allowed to drop resource pool objects.
+
+Solution: Only system users can drop resource pool objects. Common users do not have the permission to drop objects.
+
+GAUSS-04353: "App Workload Group Mapping '%s': object not defined"
+
+SQLSTATE: 42704
+
+Description: Failed to remove app workload group mapping that does not exist.
+
+Solution: Do not remove app workload group mapping that does not exist.
+
+GAUSS-04355: "internal error, rename partitioned table failed"
+
+SQLSTATE: XX000
+
+Description: Failed to rename the partitioned table.
+
+Solution: Ensure that the *table_name* and *new_table_name* are correctly specified in the **ALTER TABLE [ IF EXISTS ] table_name RENAME TO new_table_name** syntax.
+
+GAUSS-04356: "internal error, rename partition failed"
+
+SQLSTATE: XX000
+
+Description: Failed to rename the partition.
+
+Solution: Ensure that *partition_name* and *partition_new_name* in the **ALTER TABLE..RENAME PARTITION partition_name TO partition_new_name** syntax does not indicate an existing partition.
+
+GAUSS-04358: "statistics percent valid value is between 0 and 100"
+
+SQLSTATE: 22023
+
+Description: The percentage value does not range between 0 and 100.
+
+Solution: Set the percentage to a value ranging between 0 and 100.
+
+GAUSS-04360: "Partition cache lookup failed for index partition %u"
+
+SQLSTATE: XX000
+
+Description: The cache data is refreshed instantaneously. Failed to query the partitioned index.
+
+Solution: Perform the operation again.
+
+<br/>
+
+## GAUSS-04361 - GAUSS-04370
+
+<br/>
+
+GAUSS-04361: "explain_perf_mode requires FORMAT TEXT"
+
+SQLSTATE: 22023
+
+Description: The non-TEXT format is used while this parameter is set to non-normal mode.
+
+Solution: Use the TEXT format when **explain_perf_mode** is set to non-normal mode.
+
+GAUSS-04363: "unsupported type %d"
+
+SQLSTATE: XX000
+
+Description: Internal system error. An unsupported type is used.
+
+Solution:Contact technical support.
+
+GAUSS-04365: "The expiration time could not be earlier than the starting time."
+
+SQLSTATE: XX000
+
+Description: The start time of the validity period is later than the end time.
+
+Solution: Check and set valid startup time and end time of the account.
+
+GAUSS-04366: "The old password can not be NULL, please input your old password with 'replace' grammar."
+
+SQLSTATE: XX000
+
+Description: An error is reported if the original password is not provided when the administrator changes the administrator password or use the **IDENTIFIED BY** statement to change the user password.
+
+Solution: When you use the **IDENTIFIED BY** statement to change the user password, use the **REPLACE** statement to offer original password.
+
+GAUSS-04367: "The old password is invalid."
+
+SQLSTATE: XX000
+
+Description: The password is incorrect when the **IDENTIFIED BY … REPLACE** statement is used to change the user password.
+
+Solution: Provide a correct account password when using the **IDENTIFIED BY … REPLACE** statement to change the user password.
+
+GAUSS-04368: "Permission denied to rename the initial account."
+
+SQLSTATE: 42501
+
+Description: The user is not allowed to rename the initialized database user.
+
+Solution: Check the object to be renamed. You are not allowed to rename the database initialized user.
+
+<br/>
+
+## GAUSS-04371 - GAUSS-04380
+
+<br/>
+
+GAUSS-04371: "Invalid value for tablespace maxsize: '%s'"
+
+SQLSTATE: 22023
+
+Description: The format or value of the tablespace limit is incorrect.
+
+Solution: Correct the format or value according to corresponding prompt information.
+
+GAUSS-04372: "tablespace cannot be created under data directory"
+
+SQLSTATE: 42P17
+
+Description: An error occurs while creating a tablespace in the data directory.
+
+Solution: Do not create tablespace in the data directory. An error is reported if the absolute path of the created tablespace contains the data directory.
+
+GAUSS-04373: "unchangeable tablespace '%s'"
+
+SQLSTATE: 42939
+
+Description: The system tablespace or private tablespace cannot be modified.
+
+Solution: Change the user tablespace name to a valid one.
+
+GAUSS-04374: "Insufficient storage space for tablespace '%s'"
+
+SQLSTATE: XX000
+
+Description: All tablespaces configured are used up.
+
+Solution: Contact the system administrator to adjust the tablespace quota.
+
+GAUSS-04375: "Communication failure, failed to send set commands to pool."
+
+SQLSTATE: 08000
+
+Description: Communication is abnormal.
+
+Solution: Check the network status of the host. Perform this operation when the network pressure is low.
+
+GAUSS-04376: "explain_dna_file should be .csv file."
+
+SQLSTATE: XX000
+
+Description: The file name is not in .csv format.
+
+Solution: Set the file name to the .csv format.
+
+GAUSS-04377: "explain_dna_file should be absolute path + .csv file."
+
+SQLSTATE: XX000
+
+Description: The **explain_dna_file** parameter is not in the format of *Absolute path***.csv**.
+
+Solution: Set the **explain_dna_file** parameter in the format of *Absolute path***.csv**.
+
+GAUSS-04378: "you are not allowed to do that operation immediately, please try again later"
+
+SQLSTATE: XX000
+
+Description: This command cannot be used too frequently.
+
+Solution: Run this command at a certain interval.
+
+GAUSS-04379: "The account is not within the period of validity. "
+
+SQLSTATE: XX000
+
+Description: The current account is not within the valid period.
+
+Solution: The security administrator needs to reset the user's valid start time and end time.
+
+GAUSS-04380: "memory is temporarily unavailable"
+
+SQLSTATE: 53200
+
+Description: An error is reported when memory allocation fails.
+
+Solution: ERROR level. Roll back the job that is being executed.
+
+<br/>
+
+## GAUSS-04381 - GAUSS-04390
+
+<br/>
+
+GAUSS-04381: "detected write past chunk end in %s %p"
+
+SQLSTATE: XX000
+
+Description: While memory is freed up, the entered characters are verified. If the characters are incorrect, an error is reported.
+
+Solution: PANIC level. Check memory overwriting, stop the process, and dump a core in debug mode.
+
+GAUSS-04383: "Bucketmap is NULL"
+
+SQLSTATE: XX000
+
+Description: Bucketmap is **NULL**.
+
+Solution: Do not perform this operation.
+
+GAUSS-04385: "invalid name of memory context: NULL or " "
+
+SQLSTATE: XX000
+
+Description: The **NULL** or empty characters are regarded as invalid memory context names when the function parameters are checked.
+
+Solution: Ensure that the memory context is valid.
+
+GAUSS-04386: "Failed to receive GTM commit transaction response for DN or other CN."
+
+SQLSTATE: XX000
+
+Description: Failed to obtain the feedback information to notify the GTM to submit a transaction due to GTM disconnection.
+
+Solution: Check whether the connection between the GTM and other instances is normal.
+
+GAUSS-04387: "column '%s' needs too many memory"
+
+SQLSTATE: 0A000
+
+Description: The number of imported column-store records is too large.
+
+Solution: Import the row-store records.
+
+GAUSS-04390: "Failed to initialze NativeTarget for LLVM."
+
+SQLSTATE: XX000
+
+Description: Failed to initialize the LLVM local object during the database startup.
+
+Solution: Restart the database.
+
+<br/>
+
+## GAUSS-04391 - GAUSS-04400
+
+<br/>
+
+GAUSS-04391: "Failed to initialze NativeTargetAsmPrinter for LLVM."
+
+SQLSTATE: XX000
+
+Description: Failed to initialize the ASM printer for LLVM during the database startup.
+
+Solution: Restart the database.
+
+GAUSS-04392: "Failed to initialze NativeTargetAsmParser for LLVM."
+
+SQLSTATE: XX000
+
+Description: Failed to initialize the ASM parser for LLVM during the database startup.
+
+Solution: Restart the database.
+
+GAUSS-04400: "Include identical distribution column '%s'"
+
+SQLSTATE: 42P16
+
+Description: Two identical distribution columns are specified during table creation.
+
+Solution: Modify the table creation statement.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/45-GAUSS-04401-GAUSS-04500.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/45-GAUSS-04401-GAUSS-04500.md
new file mode 100644
index 0000000000000000000000000000000000000000..28074e99a76129d9289b308672077e462efe88ff
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/45-GAUSS-04401-GAUSS-04500.md
@@ -0,0 +1,457 @@
+---
+title: GAUSS-04401 - GAUSS-04500
+summary: GAUSS-04401 - GAUSS-04500
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-04401 - GAUSS-04500
+
+<br/>
+
+## GAUSS-04401 - GAUSS-04410
+
+<br/>
+
+GAUSS-04401: "The local index %u on the partition %u not exist."
+
+SQLSTATE: 42704
+
+Description: When partitions and indexes are concurrently dropped, an index dropped with a partition may not exist when **drop index** is executed.
+
+Solution: Adjust concurrency control.
+
+GAUSS-04403: "Can only access temp objects of the current session."
+
+SQLSTATE: 0A000
+
+Description: Accessing temporary objects in other sessions is not allowed.
+
+Solution: Access only the temporary objects in the local session.
+
+GAUSS-04404: "cache lookup failed for role %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04405: "temp relation is invalid because of cluster resizing"
+
+SQLSTATE: 0A000
+
+Description: The original temporary table becomes invalid after scale-out or scale-in.
+
+Solution:
+
+1. Exit the current session, reconnect to the session, and create a temporary table.
+2. Use **DROP SCHEMA ***%s\* and \*%s\*** CASCADE** to delete the temporary schema and recreate a temporary table.
+
+GAUSS-04407: "Not allowed to insert into relation pg_auth_history."
+
+SQLSTATE: XX000
+
+Description:**pg_auth_history** is used to audit username and password changes. Related changes are recorded only when the username and password in **pg_authid** are changed. Any changes on the record will affect the auditing.
+
+Solution: Do not use the **INSERT INTO** statement to insert records into **pg_auth_history**.
+
+GAUSS-04408: "do not support create non-temp table like temp table"
+
+SQLSTATE: 0A000
+
+Description: When a common table is created, the **LIKE** temporary table syntax is used. This method is not supported.
+
+Solution: Do not use the **LIKE** temporary table syntax to create a non-temporary table. If you want to use it, specify the to-be-created table as a temporary table.
+
+<br/>
+
+## GAUSS-04411 - GAUSS-04420
+
+<br/>
+
+GAUSS-04411: "Multi-column combined informational constraint is forbidden."
+
+SQLSTATE: 0A000
+
+Description: Information constraints on a combination of multiple columns are not supported.
+
+Solution: Establish information constraints in a column.
+
+GAUSS-04414: "The number of %s distribute key can not exceed 1"
+
+SQLSTATE: 42601
+
+Description: A non-hash table cannot have multiple distribution columns.
+
+Solution: Modify the table creation statement and specify one column as the distribution column.
+
+GAUSS-04415: "Compatibility args %s is invalid\n"
+
+SQLSTATE: 22023
+
+Description: The specified compatibility line parameter is incorrect.
+
+Solution: Specify the parameter to be **ORA** or **TD**.
+
+GAUSS-04417: "Alias '%s' reference with window function included is not supported."
+
+SQLSTATE: 42703
+
+Description: During alias reference, the referenced expression cannot contain window functions.
+
+Solution: Modify the SQL statement.
+
+GAUSS-04418: "Alias '%s' reference with volatile function included is not supported."
+
+SQLSTATE: 42703
+
+Description: During alias reference, the referenced expression cannot contain volatile functions.
+
+Solution: Modify the SQL statement.
+
+GAUSS-04419: "Alias '%s' is ambiguous."
+
+SQLSTATE: 42703
+
+Description: The alias has been used.
+
+Solution: Change the alias.
+
+<br/>
+
+## GAUSS-04421 - GAUSS-04430
+
+<br/>
+
+GAUSS-04422: "%u/%u/%u invalid bcm meta buffer %u"
+
+SQLSTATE: XX000
+
+Description: The meta page of the BCM file is invalid.
+
+Solution:Contact technical support.
+
+GAUSS-04424: "Vector aggregation does not support this distinct clause in aggregate function"
+
+SQLSTATE: XX000
+
+Description: When the aggregation vectorized executor is initialized, the aggregate function does not support the distinct clause.
+
+Solution:Contact technical support.
+
+GAUSS-04425: "Grant not supported for TEMP and non-TEMP objects together"
+
+SQLSTATE: 0A000
+
+Description: The grant operation does not support temporary and non-temporary objects at the same time.
+
+Solution: Split the statement to be executed into two statements to separately execute temporary and non-temporary objects.
+
+GAUSS-04426: "Explicit prepare transaction is not supported."
+
+SQLSTATE: 0A000
+
+Description: Explicit **PREPARE** is not supported. This error occurs because you entered explicit **PREPARE** statement.
+
+Solution: Do not enter an explicit **PREPARE** statement.
+
+GAUSS-04427: "Explicit commit prepared transaction is not supported."
+
+SQLSTATE: 0A000
+
+Description: Explicit **COMMIT PREPARED** is not supported. This error occurs because you entered explicit **COMMIT PREPARED** statement.
+
+Solution: Do not enter an explicit **COMMIT PREPARED** statement.
+
+GAUSS-04428: "Explicit rollback prepared transaction is not supported."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04429: "LOCK not supported for TEMP and non-TEMP objects together"
+
+SQLSTATE: 0A000
+
+Description: The lock operation does not support temporary and non-temporary objects at the same time.
+
+Solution: Split the statement to be executed into two statements to separately execute temporary and non-temporary objects.
+
+<br/>
+
+## GAUSS-04431 - GAUSS-04440
+
+<br/>
+
+GAUSS-04432: "invalid set size for BipartiteMatch"
+
+SQLSTATE: XX000
+
+Description: Internal system error. The input parameter is invalid.
+
+Solution:Contact technical support.
+
+GAUSS-04433: "AIO Completer io_getevents() failed: error %d ."
+
+SQLSTATE: XX000
+
+Description: Failed to execute the OS function **io_getevents()**.
+
+Solution: Check whether the OS kernel function is greater than Linux 2.6.23 and whether the OS installed the libaio library.
+
+GAUSS-04434: "parent of GROUPING is not VecAgg node"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04435: "parent of GROUPINGID is not VecAgg node"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04436: "Unsupported alternative subPlan expression in vector engine"
+
+SQLSTATE: 0A000
+
+Description: The alternative expression is not vectorized.
+
+Solution: Modify the SQL statement.
+
+GAUSS-04437: "Unsupported rowexpr expression in vector engine"
+
+SQLSTATE: 0A000
+
+Description: The rowexpr expression is not vectorized.
+
+Solution: Modify the SQL statement.
+
+GAUSS-04438: "unsupported vector sub plan type %d"
+
+SQLSTATE: XX000
+
+Description: An error is reported because the subplan type is not supported by the vectorized engine.
+
+Solution: Modify the SQL statement.
+
+GAUSS-04439: "Unsupported state in vec sort agg"
+
+SQLSTATE: 20000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04440: "Failed to connect hdfs."
+
+SQLSTATE: XX000
+
+Description: Failed to connect to HDFS.
+
+Solution: Check CN logs and find out the cause of the error.
+
+<br/>
+
+## GAUSS-04441 - GAUSS-04450
+
+<br/>
+
+GAUSS-04441: "Unsupport store format, only support ORC format for DFS table."
+
+SQLSTATE: XX000
+
+Description: Internal system error. The data format of the HDFS table is not ORC.
+
+Solution: Modify the data format.
+
+GAUSS-04442: "'INSERT' is not supported by the type of relation."
+
+SQLSTATE: D0011
+
+Description: This table does not support the insert operation.
+
+Solution:Contact technical support.
+
+GAUSS-04443: "'DELETE' is not supported by the type of relation."
+
+SQLSTATE: D0011
+
+Description: This table does not support the delete operation.
+
+Solution:Contact technical support.
+
+GAUSS-04444: "'UPDATE' is not supported by the type of relation."
+
+SQLSTATE: D0011
+
+Description: This table does not support the update operation.
+
+Solution:Contact technical support.
+
+GAUSS-04449: "parent of GROUPING is not Agg node"
+
+SQLSTATE: 42P27
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04450: "parent of GROUPINGID is not Agg node"
+
+SQLSTATE: 42P27
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04461 - GAUSS-04470
+
+<br/>
+
+GAUSS-04468: "corrupt during reset shared hash table '%s'"
+
+SQLSTATE: XX000
+
+Description: The memory crashes when the hash table is reset.
+
+Solution: Restart the server.
+
+GAUSS-04469: "terminating SyncLocalXactsWithGTM process due to administrator command"
+
+SQLSTATE: 57P01
+
+Description: The primary server is demoted to standby or **SyncLocalXactsWithGTM** is stopped as the system exits.
+
+Solution: No action is required.
+
+<br/>
+
+## GAUSS-04471 - GAUSS-04480
+
+<br/>
+
+GAUSS-04471: "fallocate(fd=%d, amount=%d, offset=%ld),write count(%d), errno(%d), maybe you use adio without XFS filesystem, if you really want do this,please turn off GUC parameter enable_fast_allocate"
+
+SQLSTATE: XX000
+
+Description: Failed to quickly distribute the data file block.
+
+Solution: Check whether the file system is XFS. If not, disable the **enable_fast_allocate** configuration item.
+
+GAUSS-04472: "FileAsyncRead, file access failed %d"
+
+SQLSTATE: XX000
+
+Description: The abnormal file is detected in asynchronization I/O mode before the server reads the data file.
+
+Solution: Ensure that the data file is normal. If it is abnormal, restore the data from the standby server or the backup data.
+
+GAUSS-04474: "FileAsyncWrite, file access failed %d"
+
+SQLSTATE: XX000
+
+Description: The file is abnormal before the data file is written in asynchronization I/O mode.
+
+Solution: Ensure that the data file is normal. If it is abnormal, restore the data from the standby server or the backup data.
+
+GAUSS-04476: "FileAccess() FAILED %d"
+
+SQLSTATE: XX000
+
+Description: The file is abnormal before the data file is read and written in asynchronization I/O mode.
+
+Solution: Ensure that the data file is normal. If it is abnormal, restore the data from the standby server or the backup data.
+
+GAUSS-04479: "fallocate(fd=%d, amount=%u, offset=%u),write count(%d), errno(%d), maybe you use adio without XFS filesystem, if you really want do this,please turn off GUC parameter enable_fast_allocate"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04481 - GAUSS-04490
+
+<br/>
+
+GAUSS-04481: "Require scratch buflist to reorder writes."
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04483: "CheckIOState, find an error in async write"
+
+SQLSTATE: XX000
+
+Description: An I/O write error occurs in the **VACUUM FULL** row-store table.
+
+Solution: Check whether the disk is faulty or needs to be updated. Then, write again.
+
+GAUSS-04484: "InProgressBuf not null: id %d flags %u, buf: id %d flags %u"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04485: "posix_memalign fails, The alignment argument was not a power of two, or was not a multiple of sizeof(void *)"
+
+SQLSTATE: XX000
+
+Description: Internal system error. The memory of the OS is insufficient, the value of the memory alignment parameter is not the nth power of 2, or the pointer parameter is abnormal.
+
+Solution: After the OS releases part of memory, allocate the memory again.
+
+<br/>
+
+## GAUSS-04491 - GAUSS-04500
+
+<br/>
+
+GAUSS-04492: "redundant options."
+
+SQLSTATE: XX000
+
+Description: The option is redundant.
+
+Solution: Do not set values for redundant options.
+
+GAUSS-04494: "max_dop value can't be %ld."
+
+SQLSTATE: 22003
+
+Description: The value of **max_dop** is invalid.
+
+Solution: Set **max_dop** to a value greater than or equal to 1.
+
+GAUSS-04495: "invalid value '%s' for parameter '%s'"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04496: "memory_limit size value can't be %d."
+
+SQLSTATE: 22003
+
+Description: The value of **memory_limit** is invalid.
+
+Solution: Set the value of **memory_limit** to a positive number.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/46-GAUSS-04501-GAUSS-04600.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/46-GAUSS-04501-GAUSS-04600.md
new file mode 100644
index 0000000000000000000000000000000000000000..d651042a41dc0ef62fe3663c4cdf1279809b83c9
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/46-GAUSS-04501-GAUSS-04600.md
@@ -0,0 +1,644 @@
+---
+title: GAUSS-04501 - GAUSS-04600
+summary: GAUSS-04501 - GAUSS-04600
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-04501 - GAUSS-04600
+
+<br/>
+
+## GAUSS-04501 - GAUSS-04510
+
+<br/>
+
+GAUSS-04503: "wrong buffer passed to BCM_clear, BlockNumber from buf is %u,mapBlock is %u"
+
+SQLSTATE: XX000
+
+Description: The BCM buffer is incorrect, or the block number corresponding to the BCM buffer is inconsistent with the map block number.
+
+Solution:Internal system error.Contact technical support.
+
+GAUSS-04505: "Please use 'ALTER ROLE user_name IDENTIFIED BY 'password' REPLACE 'old password';' to modify the initial password of user %s before operation!"
+
+SQLSTATE: XX000
+
+Description: The initial password is not changed.
+
+Solution: Use the displayed command to change the initial password.
+
+GAUSS-04506: "SECURITY LABEL is not yet supported."
+
+SQLSTATE: 0A000
+
+Description: The feature is not supported.
+
+Solution: Do not use this feature.
+
+GAUSS-04507: "domain is not yet supported."
+
+SQLSTATE: 0A000
+
+Description: The feature is not supported.
+
+Solution: Do not use this feature.
+
+GAUSS-04508: "user defined aggregate is not yet supported."
+
+SQLSTATE: 0A000
+
+Description: The feature is not supported.
+
+Solution: Do not use this feature.
+
+GAUSS-04509: "user defined operator is not yet supported."
+
+SQLSTATE: 0A000
+
+Description: The feature is not supported.
+
+Solution: Do not use this feature.
+
+<br/>
+
+## GAUSS-04511 - GAUSS-04520
+
+<br/>
+
+GAUSS-04511: "user-defined text search parser is not yet supported."
+
+SQLSTATE: 0A000
+
+Description: The feature is not supported.
+
+Solution: Do not use this feature.
+
+GAUSS-04513: "user-defined text search template is not yet supported."
+
+SQLSTATE: 0A000
+
+Description: The feature is not supported.
+
+Solution: Do not use this feature.
+
+GAUSS-04514: "user defined collation is not yet supported."
+
+SQLSTATE: 0A000
+
+Description: The feature is not supported.
+
+Solution: Do not use this feature.
+
+GAUSS-04515: "RULE is not yet supported."
+
+SQLSTATE: 0A000
+
+Description: The feature is not supported.
+
+Solution: Do not use this feature.
+
+GAUSS-04517: "NOFITY statement is not yet supported."
+
+SQLSTATE: 0A000
+
+Description: The feature is not supported.
+
+Solution: Do not use this feature.
+
+GAUSS-04518: "LISTEN statement is not yet supported."
+
+SQLSTATE: 0A000
+
+Description: The feature is not supported.
+
+Solution: Do not use this feature.
+
+GAUSS-04520: "LOAD statement is not yet supported."
+
+SQLSTATE: None
+
+Description: The feature is not supported.
+
+Solution: Do not use this feature.
+
+<br/>
+
+## GAUSS-04521 - GAUSS-04530
+
+<br/>
+
+GAUSS-04521: "DISCARD statement is not yet supported."
+
+SQLSTATE: 0A000
+
+Description: The feature is not supported.
+
+Solution: Do not use this feature.
+
+GAUSS-04523: "new language is not yet supported."
+
+SQLSTATE: 0A000
+
+Description: The feature is not supported.
+
+Solution: Do not use this feature.
+
+GAUSS-04524: "user defined conversion is not yet supported.""
+
+SQLSTATE: 0A000
+
+Description: The feature is not supported.
+
+Solution: Do not use this feature.
+
+GAUSS-04528: "pg_pool_validate cannot run inside a transaction block"
+
+SQLSTATE: 25001
+
+Description: The **pg_pool_validate** function cannot be executed in the transaction block.
+
+Solution: Call the **pg_pool_validate** function instead of using the **start transaction** command.
+
+GAUSS-04529: "Failed to send query ID to %s while sending query ID with sync"
+
+SQLSTATE: XX000
+
+Description: Failed to send the query ID.
+
+Solution: Check whether the peer node reports an error or whether the network is faulty.
+
+GAUSS-04530: "Failed to read response from Datanodes while sending query ID with sync. Detail: %s\n"
+
+SQLSTATE: XX000
+
+Description: Failed to send the query ID.
+
+Solution: Check whether the peer node reports an error or whether the network is faulty.
+
+<br/>
+
+## GAUSS-04531 - GAUSS-04540
+
+<br/>
+
+GAUSS-04531: "Unexpected response from %s while sending query ID with sync"
+
+SQLSTATE: XX000
+
+Description: Failed to send the query ID.
+
+Solution:Internal system error.Contact technical support.
+
+GAUSS-04532: "Could not begin transaction on %s"
+
+SQLSTATE: XX000
+
+Description: Internal system error. During the analysis process, the query command in the **pg_class** and **pg_statistic** tables cannot be sent to the CN and DN.
+
+Solution:Contact technical support.
+
+GAUSS-04533: "Failed to read response from CN %u when ending query"
+
+SQLSTATE: XX000
+
+Description: Internal system error. During the analysis process, the EOF information is obtained from the message buffer when the CN obtains the system catalog information in the **pg_class** and **pg_statistic** tables from the source CN.
+
+Solution:Contact technical support.
+
+GAUSS-04534: "Unexpected response from CN %u"
+
+SQLSTATE: XX000
+
+Description: Internal system error. During the analysis process, unexpected information is obtained from the message buffer when the CN obtains the system catalog information in the **pg_class** and **pg_statistic** tables from the source CN.
+
+Solution:Contact technical support.
+
+GAUSS-04535: "Failed to read response from DN %u when ending query"
+
+SQLSTATE: XX000
+
+Description: During the global statistics analysis process, the EOF information is not obtained when the CN obtains statistics information from the **pg_class** or **pg_statistic** table from DN1.
+
+Solution:Internal system error.Contact technical support.
+
+GAUSS-04536: "Unexpected response from DN %u"
+
+SQLSTATE: XX000
+
+Description: During the global statistics analysis process, unexpected information is obtained when the CN obtains statistics information in the **pg_class** or **pg_statistic** table from DN1.
+
+Solution:Internal system error.Contact technical support.
+
+GAUSS-04538: "The relation %s is invalid because of cluster resize, please quit current session and it will be automatically dropped."
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04539: "Cache lookup failed for relation %u."
+
+SQLSTATE: XX000
+
+Description: The entered table does not exist.
+
+Solution: Execute the SQL statement and enter the correct table name.
+
+GAUSS-04540: "Failed to create directory on HDFS."
+
+SQLSTATE: 42P17
+
+Description: Failed to create the directory.
+
+Solution: View the corresponding logs.
+
+<br/>
+
+## GAUSS-04541 - GAUSS-04550
+
+<br/>
+
+GAUSS-04542: "invalid starelkind for pg_statistic"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04543: "Failed to find the information of DFS table."
+
+SQLSTATE: 42P17
+
+Description: The HDFS information is not found when you add the delta table distribution information.
+
+Solution: Try again.
+
+GAUSS-04544: "could not obtain lock on partition(%d)"
+
+SQLSTATE: 55P03
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04545: "function roach_handler must return type 'fdw_handler'"
+
+SQLSTATE: 42809
+
+Description: Internal system error. The **fdw_handler** is not bound when the Roach tool is used to export data.
+
+Solution:Contact technical support.
+
+GAUSS-04546: "could not open roach %s"
+
+SQLSTATE: XX000
+
+Description: The Roach tool cannot be opened after it is exported.
+
+Solution: Check whether the Roach path contained in the location specified by the foreign Roach table can be accessed as expected.
+
+GAUSS-04547: "could not read from roach"
+
+SQLSTATE: XX000
+
+Description: Internal system error. Data cannot be copied using Roach.
+
+Solution:Contact technical support.
+
+GAUSS-04549: "can not specify multiple locations"
+
+SQLSTATE: 0A000
+
+Description: A maximum of one location can be specified in the Roach export method.
+
+Solution: Specify only one location for the Roach foreign table.
+
+GAUSS-04550: "could not close roach %s"
+
+SQLSTATE: XX000
+
+Description: Internal system error. Roach cannot be closed as expected after data is exported.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04551 - GAUSS-04560
+
+<br/>
+
+GAUSS-04551: "could not write to roach"
+
+SQLSTATE: XX000
+
+Description: Internal system error. An error is reported during Roach export.
+
+Solution:Contact technical support.
+
+GAUSS-04552: "COMPATIBLE_ILLEGAL_CHARS only available on READ ONLY foreign table"
+
+SQLSTATE: 42601
+
+Description: The **compatible_illegal_chars** parameter can only be used to import data.
+
+Solution: Remove the **compatible_illegal_chars** parameter when the export function is enabled.
+
+GAUSS-04553: "DATE_FORMAT only available on READ ONLY foreign table"
+
+SQLSTATE: 42601
+
+Description: The **date_format** parameter can only be used to import data.
+
+Solution: Remove the **date_format** parameter when the export function is enabled.
+
+GAUSS-04554: "TIME_FORMAT only available on READ ONLY foreign table"
+
+SQLSTATE: 42601
+
+Description: The **time_format** parameter can only be used to import data.
+
+Solution: Remove the **time_format** parameter when the export function is enabled.
+
+GAUSS-04555: "TIMESTAMP_FORMAT only available on READ ONLY foreign table"
+
+SQLSTATE: 42601
+
+Description: The **timestamp_format** parameter can only be used to import data.
+
+Solution: Remove the **timestamp_format** parameter when the export function is enabled.
+
+GAUSS-04556: "SMALLDATETIME_FORMAT only available on READ ONLY foreign table"
+
+SQLSTATE: 42601
+
+Description: The **smalldatetime_format** parameter can only be used to import data.
+
+Solution: Remove the **smalldatetime_format** parameter when the export function is enabled.
+
+GAUSS-04557: "could not find block %p"
+
+SQLSTATE: XX000
+
+Description: The allocated memory is not detected during release.
+
+Solution: Avoid the error caused by double free.
+
+GAUSS-04559: "Error happen when execute memcpy_s:%d in reallocating aliged memory"
+
+SQLSTATE: XX000
+
+Description: Failed to call the memory copy function.
+
+Solution:Contact technical support.
+
+GAUSS-04560: "unsupport to get memory size under aligned memory allocator"
+
+SQLSTATE: XX000
+
+Description: The **GetChunkSpace** function is not supported when the memory context is aligned.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04561 - GAUSS-04570
+
+<br/>
+
+GAUSS-04562: "unsupport to reallocate memory under stack memory allocator"
+
+SQLSTATE: XX000
+
+Description: The **realloc** function is not supported when the stack memory context is processed.
+
+Solution:Contact technical support.
+
+GAUSS-04563: "unsupport to get memory size under stack memory allocator"
+
+SQLSTATE: XX000
+
+Description: The **GetChunkSpace** function is not supported when the stack memory context is processed.
+
+Solution:Contact technical support.
+
+GAUSS-04564: "could not write to batchstore temporary file: %m"
+
+SQLSTATE: XX000
+
+Description: An error occurs when the temporary file is written.
+
+Solution: Check whether the disk space is sufficient and whether the disk status is correct.
+
+GAUSS-04565: "could not write to tuplestore temporary file: %m"
+
+SQLSTATE: XX000
+
+Description: An error occurs when the temporary file is written.
+
+Solution: Check whether the disk space is sufficient and whether the disk status is correct.
+
+GAUSS-04566: "unsupported to set memory_detail_tracking value under release version."
+
+SQLSTATE: XX000
+
+Description: The release is not supported.
+
+Solution: Do not use this feature. This feature is supported only by debug versions.
+
+GAUSS-04570: "specified timestamp format is null"
+
+SQLSTATE: 22007
+
+Description: The timestamp format does not support the function.
+
+Solution: Use the timestamp format only for triggers and trigger functions.
+
+<br/>
+
+## GAUSS-04571 - GAUSS-04580
+
+<br/>
+
+GAUSS-04572: "specified date format is null"
+
+SQLSTATE: 22007
+
+Description: The SQL parameter is incorrect.
+
+Solution: Modify the SQL statement.
+
+GAUSS-04573: "specified time format is null"
+
+SQLSTATE: 22007
+
+Description: The logical memory management function is not enabled.
+
+Solution: Inform the user about the reason.
+
+GAUSS-04574: "unsupported view for memory protection feature is disabled."
+
+SQLSTATE: XX000
+
+Description: Feature not supported.
+
+Solution:Contact technical support.
+
+GAUSS-04575: "It is unsupported to calculate size of database '%s' under the DFS tablespace '%s' on data node."
+
+SQLSTATE: 55006
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04576: "It is unsupported to calculate size of DFS tablespace '%s' on data node."
+
+SQLSTATE: 55006
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04578: "ExpectedEntries should be > 0 and < 10000000."
+
+SQLSTATE: XX000
+
+Description: The number of specified items exceeds the allowed quantity when you create a bloom filter.
+
+Solution: Contact technical support. Reduce the number of specified elements.
+
+GAUSS-04580: "Add too many values to the bloom filter."
+
+SQLSTATE: XX000
+
+Description: The number of items added in the bloom filter objects exceeds the maximum quantity.
+
+Solution: Contact technical support. Reduce the number of filled objects to no greater than the maximum number.
+
+<br/>
+
+## GAUSS-04581 - GAUSS-04590
+
+<br/>
+
+GAUSS-04581: "BloomFilters are not compatible for merging."
+
+SQLSTATE: XX000
+
+Description: The bloom filter objects having different coefficients cannot be merged.
+
+Solution: Contact technical support. Do not merge the bloom filter objects that have different coefficients.
+
+GAUSS-04582: "Failed to get enviroment parameter $GAUSSHOME or it is NULL, please set $GAUSSHOME as your installation directory!"
+
+SQLSTATE: 22004
+
+Description: Loading the IR file depends on the environment variable *GAUSSHOME*. If *GAUSSHOME* is not configured, an error is reported to prevent subsequent invalid operations.
+
+Solution: Configure the environment variable *GAUSSHOME*.
+
+GAUSS-04584: "Codegen failed on the procedure of ExecVecQual!"
+
+SQLSTATE: XX000
+
+Description: If an expression is not properly handled when the general IR function is generated, the codegen function fails to be used.
+
+Solution: Contact technical support. Check whether the query meets the code generation requirements and set **enable_codegen** to **off**.
+
+GAUSS-04587: "Codegen failed on the first argument of FuncExpr!\n"
+
+SQLSTATE: XX000
+
+Description: Failed to handle the first parameter when the function parameters are processed, resulting in that the codes cannot be generated and an error is reported.
+
+Solution: Contact technical support. Check whether the current function is valid and set **enable_codegen** to **off**.
+
+GAUSS-04588: "Codegen failed on the second argument of FuncExpr!\n"
+
+SQLSTATE: XX000
+
+Description: Failed to handle the second parameter when the function parameters are processed, resulting in that the codes cannot be generated and an error is reported.
+
+Solution: Contact technical support. Check whether the current function is valid and set **enable_codegen** to **off**.
+
+GAUSS-04589: "Codegen failed on the third argument of FuncExpr!\n"
+
+SQLSTATE: XX000
+
+Description: Failed to handle the third parameter when the function parameters are processed, resulting in that the codes cannot be generated and an error is reported.
+
+Solution: Contact technical support. Check whether the current function is valid and set **enable_codegen** to **off**.
+
+<br/>
+
+## GAUSS-04591 - GAUSS-04600
+
+<br/>
+
+GAUSS-04591: "Failed to create LLVM state object ExecutionEngine: %s"
+
+SQLSTATE: 42704
+
+Description: When the current module is complied, you need to mount it to an execution engine. If this execution engine fails to be created, an error is reported to prevent subsequent invalid operations.
+
+Solution: Create the engine again or set **enable_codegen** to **off** to complete this query.
+
+GAUSS-04592: "Codegen failed on verifying IR function %s."
+
+SQLSTATE: 42883
+
+Description: The IR function obtained based on the code is invalid or has defects.
+
+Solution: Set **enable_codegen** to **off**. Contact technical support.
+
+GAUSS-04593: "Failed to create llvm function prototype."
+
+SQLSTATE: XX000
+
+Description: An error is reported because the LLVM function prototype fails to be declared.
+
+Solution: Try again or set **enable_codegen** to **off**.
+
+GAUSS-04595: "Unsupported LLVM debug type!\n"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04597: "Failed on getting IR function : LLVMIRtexteq!\n"
+
+SQLSTATE: XX000
+
+Description: The **LLVMIRtexteq** function is not found in the current LLVM module. An error is reported to avoid subsequent invalid calling.
+
+Solution: Exclude this function from the ll file corresponding to the IR file or set **enable_codegen** to **off**.
+
+GAUSS-04598: "Failed on getting IR function : LLVMIRtextlt!\n"
+
+SQLSTATE: XX000
+
+Description: The **LLVMIRtextlt** function is not found in the current LLVM module. An error is reported to avoid subsequent invalid calling.
+
+Solution: Exclude this function from the ll file corresponding to the IR file or set **enable_codegen** to **off**.
+
+GAUSS-04599: "Failed on getting IR function : LLVMIRtextgt!\n"
+
+SQLSTATE: XX000
+
+Description: The **LLVMIRtextgt** function is not found in the current LLVM module. An error is reported to avoid subsequent invalid calling.
+
+Solution: Exclude this function from the ll file corresponding to the IR file or set **enable_codegen** to **off**.
+
+GAUSS-04600: "Failed on getting IR function : LLVMIRsubstring!\n"
+
+SQLSTATE: XX000
+
+Description: The **LLVMIRsubstring** function is not found in the current LLVM module. An error is reported to avoid subsequent invalid calling.
+
+Solution: Exclude this function from the ll file corresponding to the IR file or set **enable_codegen** to **off**.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/47-GAUSS-04601-GAUSS-04700.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/47-GAUSS-04601-GAUSS-04700.md
new file mode 100644
index 0000000000000000000000000000000000000000..a402671e11658d9806cbff5c5c378c073b8e825a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/47-GAUSS-04601-GAUSS-04700.md
@@ -0,0 +1,614 @@
+---
+title: GAUSS-04601 - GAUSS-04700
+summary: GAUSS-04601 - GAUSS-04700
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-04601 - GAUSS-04700
+
+<br/>
+
+## GAUSS-04601 - GAUSS-04610
+
+<br/>
+
+GAUSS-04601: "Failed on getting IR function : LLVMIRrtrim1!\n"
+
+SQLSTATE: XX000
+
+Description: The ll file corresponding to the IR file contains the function.
+
+Solution: Exclude this function from the ll file corresponding to the IR file or set **enable_codegen** to **off**.
+
+GAUSS-04602: "Failed on getting IR function : LLVMIRbtrim1!\n"
+
+SQLSTATE: XX000
+
+Description: The **LLVMIRbtrim1** function is not found in the current LLVM module. An error is reported to avoid subsequent invalid calling.
+
+Solution: Exclude this function from the ll file corresponding to the IR file or set **enable_codegen** to **off**.
+
+GAUSS-04603: "Failed on getting IR function : LLVMIRbpchareq!\n"
+
+SQLSTATE: XX000
+
+Description: The **LLVMIRbpchareq** function is not found in the current LLVM module. An error is reported to avoid subsequent invalid calling.
+
+Solution: Exclude this function from the ll file corresponding to the IR file or set **enable_codegen** to **off**.
+
+GAUSS-04604: "Cannot get the llvm::Intrinsic::sadd_with_overflow function!\n"
+
+SQLSTATE: XX000
+
+Description: The addition function in the LLVM database needs to be called. If this function is declared failed, an error is reported.
+
+Solution: Contact technical support. Alternatively, check whether the LLVM database and the LLVM storage path are correct.
+
+GAUSS-04605: "Cannot get the llvm::Intrinsic::ssub_with_overflow function!\n"
+
+SQLSTATE: XX000
+
+Description: The subtraction function in the LLVM database needs to be called. If this function is declared failed, an error is reported.
+
+Solution: Contact technical support. Alternatively, check whether the LLVM database and the LLVM storage path are correct.
+
+GAUSS-04606: "Cannot get the llvm::Intrinsic::smul_with_overflow function!\n"
+
+SQLSTATE: XX000
+
+Description: The multiplication function in the LLVM database needs to be called. If this function is declared failed, an error is reported.
+
+Solution: Contact technical support. Alternatively, check whether the LLVM database and the LLVM storage path are correct.
+
+GAUSS-04607: "Unsupport address, cfgpath, storepath options when the filesystem is not HDFS."
+
+SQLSTATE: XX000
+
+Description: When the tablespace is created, only when the **filesystem** option is set to **HDFS**, the **address**, **cfgpath** and **storepath** options are supported.
+
+Solution: Ensure that the values of the **address**, **cfgpath**, and **storepath** options in **CREATE TABLESPACE..LOCATION** indicate the HDFS file system.
+
+GAUSS-04608: "Failed to get storepath from tablespace options."
+
+SQLSTATE: XX000
+
+Description: Failed to obtain a valid **storepath** parameter from the created **tablespace** option.
+
+Solution: Ensure that the **CREATE TABLESPACE..LOCATION** syntax contains the **storepath** option.
+
+GAUSS-04609: "Failed to get cfgpath from tablespace options."
+
+SQLSTATE: XX000
+
+Description: Failed to find the **cfgpath** parameter during HDFS tablespace creation.
+
+Solution: Specify **cfgpath** during HDFS tablespace creation.
+
+GAUSS-04610: "Failed to create directory '%s' on HDFS."
+
+SQLSTATE: 42P17
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04611 - GAUSS-04620
+
+<br/>
+
+GAUSS-04611: "tablespace HDFS path '%s' is too long."
+
+SQLSTATE: 42P17
+
+Description: The **cfgpath** path of the HDFS tablespace is too long.
+
+Solution: The configured path cannot exceed 1024 bytes.
+
+GAUSS-04612: "Directory '%s' already in use as a tablespace on HDFS."
+
+SQLSTATE: 55006
+
+Description: The directory where the error is reported exists. Failed to create a tablespace.
+
+Solution: Select another **storepath** parameter value during tablespace creation.
+
+GAUSS-04613: "Failed to drop external directory, because the cfgpath option has not been found from pg_tablespace."
+
+SQLSTATE: XX000
+
+Description: The **cfgpath** parameter is not found in the option of the deleted tablespace when you delete the tablespace.
+
+Solution: Internal system error. In the **pg_tablespace** system catalog, the existing tablespace names are modified abnormally. Contact technical support.
+
+GAUSS-04619: "Resource Pool '%s': object not defined."
+
+SQLSTATE: 42704
+
+Description: The resource pool is not defined.
+
+Solution: Check whether the resource pool is defined.
+
+<br/>
+
+## GAUSS-04621 - GAUSS-04630
+
+<br/>
+
+GAUSS-04622: "Password can't contain more than %d characters."
+
+SQLSTATE: 28P01
+
+Description: The account password cannot contain over *%d* characters.
+
+Solution: Change the password format to ensure that the number of characters does not exceed *%d*.
+
+GAUSS-04623: "invalid GDS command: %d"
+
+SQLSTATE: XX000
+
+Description: Invalid GDS interaction is received.
+
+Solution: Check whether invalid data exists in the imported file of GDS foreign tables, clean the file, and import it again.
+
+GAUSS-04624: "Failed to deserialize command, which type is %d"
+
+SQLSTATE: XX000
+
+Description: Invalid GDS interaction is received.
+
+Solution: Check whether invalid data exists in the imported file of GDS foreign tables, clean the file, and import it again.
+
+GAUSS-04626: "Invalid schema oid: %u"
+
+SQLSTATE: 3F000
+
+Description: Failed to find the schema entered by the user.
+
+Solution:Contact technical support.
+
+GAUSS-04627: "deltamerge: This relation doesn't support vacuum deltamerge operation"
+
+SQLSTATE: 42P01
+
+Description: Failed to merge the table by using the **VACUUM DELTAMERGE** *[table_name]* syntax.
+
+Solution: Ensure that *[table_name]* specifies a delta table in the **VACUUM DELTAMERGE** *[table_name]* syntax.
+
+GAUSS-04629: "gs_switch_relfilenode can be only used by redistribution tool."
+
+SQLSTATE: XX000
+
+Description: The metainformation exchange function is only used for the redistribution tool and not recommended for users.
+
+Solution: The database does not support the function. Contact technical support.
+
+GAUSS-04630: "DFS tablespace can not be used as default tablespace."
+
+SQLSTATE: 22023
+
+Description: The DFS tablespace cannot be used as the default tablespace.
+
+Solution: Do not use the DFS tablespace as the default tablespace.
+
+<br/>
+
+## GAUSS-04631 - GAUSS-04640
+
+<br/>
+
+GAUSS-04631: "It is unsupported to rename database '%s' on DFS tablespace '%s'."
+
+SQLSTATE: 0A000
+
+Description: If the DFS tablespace is used in the database, the database cannot be renamed.
+
+Solution: Ensure that no table in the database uses DFS tablespaces.
+
+GAUSS-04634: "cannot alter text search configuration '%s' because other objects depend on it"
+
+SQLSTATE: 2BP01
+
+Description: This configuration information cannot be changed because the context index configuration items have dependent relationship with other tables or indexes.
+
+Solution: Cancel the dependency and then perform this operation.
+
+GAUSS-04637: "It is not allowed to assign version option for non-dfs table."
+
+SQLSTATE: XX000
+
+Description: An error is reported when the **version** parameter is specified for creating row-store tables or column-store tables in CU format.
+
+Solution: Do not use the **version** parameter when creating row-store tables or column-store tables in CU format.
+
+GAUSS-04638: "Unsupport '%s' option"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04639: "Invalid string for 'VERSION' option"
+
+SQLSTATE: XX000
+
+Description: The **version** parameter is invalid.
+
+Solution: Set this parameter to **0.12**.
+
+GAUSS-04640: "Num of partition keys in value-partitioned table should not be zeror"
+
+SQLSTATE: XX000
+
+Description: The partition column is not specified when the HDFS table partitioned by value is created.
+
+Solution: Specify 1 to 4 columns when creating the value-partitioned HDFS table.
+
+<br/>
+
+## GAUSS-04641 - GAUSS-04650
+
+<br/>
+
+GAUSS-04641: "Num of partition keys in value-partitioned table exceeds max allowed num:%d"
+
+SQLSTATE: XX000
+
+Description: The number of partition columns exceeds 4 when the HDFS table partitioned by value is created.
+
+Solution: Specify 1 to 4 columns when creating the value-partitioned HDFS table.
+
+GAUSS-04642: "Unsupport partition strategy '%s' feature for dfs table."
+
+SQLSTATE: XX000
+
+Description: Only the HDFS table partitioned by value is supported. Otherwise, an error is reported.
+
+Solution: Specify the value partition when creating HDFS tables.
+
+GAUSS-04644: "Value partitioned table can only be created on DFS tablespace."
+
+SQLSTATE: 0A000
+
+Description: The value partition can only be created in the DFS table.
+
+Solution: Do not create the value partition for other types of tables except the DFS table.
+
+GAUSS-04645: "It is not supported to truncate foreign table '%s'."
+
+SQLSTATE: 42809
+
+Description: The truncate operation cannot be performed on foreign tables.
+
+Solution: Do not perform the truncate operation on foreign tables.
+
+GAUSS-04646: "It is not supported to truncate non-table '%s'"
+
+SQLSTATE: 42809
+
+Description: The truncate operation is not supported on database objects in abnormal tables.
+
+Solution: Do not perform the truncate operation on database objects in abnormal tables.
+
+GAUSS-04648: "Storage type '%s' is meaningless for column relation"
+
+SQLSTATE: 0A000
+
+Description: The storage type of row-store tables is meaningless for column-store tables.
+
+Solution: Do not set the storage type for the column-store tables.
+
+GAUSS-04649: "column '%s' cannot be served as a value-partitioning column because of its datatype [%s]"
+
+SQLSTATE: 42804
+
+Description: Some types are not supported in value partition.
+
+Solution: Check the documentation and determine the data type supported by the value partition.
+
+GAUSS-04650: "can not set tablespace for partitioned relation"
+
+SQLSTATE: XX000
+
+Description: The tablespace of the partitioned table is changed.
+
+Solution: Do not change the tablespace for partitioned tables.
+
+<br/>
+
+## GAUSS-04651 - GAUSS-04660
+
+<br/>
+
+GAUSS-04651: "It is not supported to rename schema '%s' which includes DFS table '%s'."
+
+SQLSTATE: 42939
+
+Description: Currently, a schema containing the DFS table cannot be renamed using the `ALTER SCHEMA schema_name RENAME TO new_schema_name` syntax.
+
+Solution: Ensure that the `ALTER SCHEMA schema_name RENAME TO new_schema_name` syntax does not contain the DFS table. Delete the DFS table and rename the schema again.
+
+GAUSS-04652: "COPY_ROACH does not implement in CopySendEndOfRow"
+
+SQLSTATE: XX000
+
+Description: Do not use ROACH for COPY TO export.
+
+Solution: Do not use ROACH for COPY TO export.
+
+GAUSS-04653: "the bulkload compatible illegal chars flag is already set before bulkload starts"
+
+SQLSTATE: XX000
+
+Description: Internal system error. The parameter for specifying invalid character compatibility that was imported before has not been cleaned.
+
+Solution:Contact technical support.
+
+GAUSS-04655: "cannot specify bulkload compatibility options in BINARY mode"
+
+SQLSTATE: 42601
+
+Description: Internal system error. The imported CopyState object is not cleared.
+
+Solution:Contact technical support.
+
+GAUSS-04656: "IGNORE_EXTRA_DATA specification only available using COPY FROM or READ ONLY foreign table"
+
+SQLSTATE: 42601
+
+Description: The **ignore_extra_data** parameter can only be used to import data.
+
+Solution: Remove the **ignore_extra_data** parameter when the export function is enabled.
+
+GAUSS-04657: "COMPATIBLE_ILLEGAL_CHARS specification only available using COPY FROM or READ ONLY foreign table"
+
+SQLSTATE: 42601
+
+Description: The **compatible_illegal_chars** parameter can only be used to import data.
+
+Solution: Remove the **compatible_illegal_chars** parameter when the export function is enabled.
+
+GAUSS-04658: "DATE_FORMAT specification only available using COPY FROM or READ ONLY foreign table"
+
+SQLSTATE: 42601
+
+Description: The **date_format** parameter can only be used to import data.
+
+Solution: Remove the **date_format** parameter when the export function is enabled.
+
+GAUSS-04659: "TIME_FORMAT specification only available using COPY FROM or READ ONLY foreign table"
+
+SQLSTATE: 42601
+
+Description: The **time_format** parameter can only be used to import data.
+
+Solution: Remove the **time_format** parameter when the export function is enabled.
+
+GAUSS-04660: "TIMESTAMP_FORMAT specification only available using COPY FROM or READ ONLY foreign table"
+
+SQLSTATE: 42601
+
+Description: The **timestamp_format** parameter can only be used to import data.
+
+Solution: Remove the **timestamp_format** parameter when the export function is enabled.
+
+<br/>
+
+## GAUSS-04661 - GAUSS-04670
+
+<br/>
+
+GAUSS-04662: "illegal chars conversion may confuse COPY null 0x%x"
+
+SQLSTATE: 42601
+
+Description: The **null** parameter is set to a space or question mark (?), and **compatible_illegal_chars** is set to **true**, indicating the invalid characters are compatible. The imported invalid characters are converted to spaces or question marks, introducing confusion with the **null** parameter, which results in potential import errors.
+
+Solution: Set **null** to other characters except a space or question mark to avoid confusion with invalid characters after they are converted.
+
+GAUSS-04663: "illegal chars conversion may confuse COPY delimiter 0x%x"
+
+SQLSTATE: 42601
+
+Description: The **delimiter** parameter is set to a space or question mark (?), and **compatible_illegal_chars** is set to **true**, indicating the invalid characters are compatible. The imported invalid characters are converted to spaces or question marks, introducing confusion with the **delimiter** parameter, which results in potential import errors.
+
+Solution: Set **delimiter** to other characters except a space or question mark to avoid confusion with invalid characters after they are converted.
+
+GAUSS-04664: "illegal chars conversion may confuse COPY quote 0x%x"
+
+SQLSTATE: XX000
+
+Description: The **quote** parameter is set to a space or question mark (?), and **compatible_illegal_chars** is set to **true**, indicating the invalid characters are compatible. The imported invalid characters are converted to spaces or question marks, introducing confusion with the **quote** parameter, which results in potential import errors.
+
+Solution: Set **quote** to other characters except a space or question mark to avoid confusion with invalid characters after they are converted.
+
+GAUSS-04665: "illegal chars conversion may confuse COPY escape 0x%x"
+
+SQLSTATE: 42601
+
+Description: The **escape** parameter is set to a space or question mark (?), and **compatible_illegal_chars** is set to **true**, indicating the imported invalid characters are compatible. The imported invalid characters are converted to spaces or question marks, introducing confusion with the **escape** parameter, which results in potential import errors.
+
+Solution: Set **escape** to other characters except a space or question mark to avoid confusion with invalid characters after they are converted.
+
+GAUSS-04666: "the bulkload state isn't accordant"
+
+SQLSTATE: XX000
+
+Description: Internal system error. The cached global variable CopyState is inconsistent with the imported CopyState.
+
+Solution:Contact technical support.
+
+GAUSS-04667: "Failed to get import task for dn:%s"
+
+SQLSTATE: XX000
+
+Description: A DN is not assigned any import tasks when you use GDS to import data.
+
+Solution: Try again.
+
+GAUSS-04668: "Receive wrong message %d from GDS."
+
+SQLSTATE: XX000
+
+Description: A DN receives an error message from GDS.
+
+Solution: Ensure the current network is normal and try again.
+
+GAUSS-04669: "Receive incomplete message from GDS."
+
+SQLSTATE: XX000
+
+Description: The DN receives a currently unsupported message from GDS.
+
+Solution: Ensure the current network is normal and try again.
+
+<br/>
+
+## GAUSS-04681 - GAUSS-04690
+
+<br/>
+
+GAUSS-04681: "CUBE is limited to 12 elements"
+
+SQLSTATE: 54011
+
+Description: The number of **CUBE** parameters is less than or equal to 12.
+
+Solution: Modify the SQL statement.
+
+GAUSS-04682: "type %s is not yet supported."
+
+SQLSTATE: 0A000
+
+Description: The feature is not supported.
+
+Solution: Modify the SQL statement.
+
+GAUSS-04683: "REFERENCES constraint is not yet supported."
+
+SQLSTATE: 0A000
+
+Description: The feature is not supported.
+
+Solution: Do not use it.
+
+GAUSS-04684: "EXCLUDE constraint is not yet supported."
+
+SQLSTATE: 0A000
+
+Description: The feature is not supported.
+
+Solution: Do not use this feature.
+
+GAUSS-04685: "FOREIGN KEY … REFERENCES constraint is not yet supported."
+
+SQLSTATE: 0A000
+
+Description: The feature is not supported.
+
+Solution: Do not use this feature.
+
+GAUSS-04686: "CREATE TABLE … INHERITS is not yet supported."
+
+SQLSTATE: 0A000
+
+Description: The feature is not supported.
+
+Solution: Do not use this feature.
+
+GAUSS-04687: "CREATE TABLE … WITH OIDS is not yet supported."
+
+SQLSTATE: 0A000
+
+Description: The feature is not supported.
+
+Solution: Do not use this feature.
+
+GAUSS-04689: "CURSOR … WITH HOLD is not yet supported."
+
+SQLSTATE: 0A000
+
+Description: The feature is not supported.
+
+Solution: Do not use this feature.
+
+GAUSS-04690: "SCROLL CURSOR is not yet supported."
+
+SQLSTATE: 0A000
+
+Description: The feature is not supported.
+
+Solution: Do not use this feature.
+
+<br/>
+
+## GAUSS-04691 - GAUSS-04700
+
+<br/>
+
+GAUSS-04691: "INSENSITIVE CURSOR is not yet supported."
+
+SQLSTATE: 0A000
+
+Description: Feature not supported.
+
+Solution: Do not use this feature.
+
+GAUSS-04693: "For foreign table ROUNDROBIN distribution type is built-in support."
+
+SQLSTATE: 0A000
+
+Description: The ROUNDROBIN distribution information is supported when you create a GDS foreign table. Displaying the added distribution information when you create a foreign table is not supported.
+
+Solution: Delete the specified distribution information.
+
+GAUSS-04695: "Value-based partition table should have one column at least"
+
+SQLSTATE: 42601
+
+Description: The value-based partitioned table has at least one column.
+
+Solution:Contact technical support.
+
+GAUSS-04696: "Value-Based partition table creation encounters unexpected data in unnecessary fields"
+
+SQLSTATE: XX000
+
+Description: Unexpected data is generated when the value-based partitioned table is created.
+
+Solution:Contact technical support.
+
+GAUSS-04697: "too many grouping sets present (max 4096)"
+
+SQLSTATE: 54001
+
+Description: The number of groups cannot exceed 4096.
+
+Solution: Modify the SQL statement.
+
+GAUSS-04698: "arguments to GROUPING must be grouping expressions of the associated query level"
+
+SQLSTATE: 42803
+
+Description: Failed to find the **grouping** parameter in the **GROUP BY** clause.
+
+Solution: Modify the SQL statement.
+
+GAUSS-04699: "GROUPING must have fewer than 32 arguments"
+
+SQLSTATE: 54023
+
+Description: The number of **grouping** parameters is less than 32.
+
+Solution: Modify the SQL statement.
+
+GAUSS-04700: "ngram parser only support UTF8/GBK encoding"
+
+SQLSTATE: XX000
+
+Description: The **NGRAM** segmentation algorithm supports only the UTF8 or GBK database encoding format.
+
+Solution:**NGRAM** is a segmentation algorithm to support Chinese full text retrieval. Ensure that the database encoding is UTF8 or GBK format when the **NGRAM** is used.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/48-GAUSS-04701-GAUSS-04800.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/48-GAUSS-04701-GAUSS-04800.md
new file mode 100644
index 0000000000000000000000000000000000000000..5191f7d4c8a70902f863dbf2218ae26682df28c3
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/48-GAUSS-04701-GAUSS-04800.md
@@ -0,0 +1,559 @@
+---
+title: GAUSS-04701 - GAUSS-04800
+summary: GAUSS-04701 - GAUSS-04800
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-04701 - GAUSS-04800
+
+<br/>
+
+## GAUSS-04701 - GAUSS-04710
+
+<br/>
+
+GAUSS-04706: "The parameter can not smaller than -1."
+
+SQLSTATE: XX000
+
+Description: The value of the **prevbit** parameter must be greater than or equal to **-1** when the parameter is verified.
+
+Solution:Contact technical support.
+
+GAUSS-04708: "Column count in table definition does not match with ORC file %s."
+
+SQLSTATE: 22000
+
+Description: The column definition of the table is inconsistent with that of the ORC file.
+
+Solution:Contact technical support.
+
+GAUSS-04709: "Error occurs while read row index of orc file, detail can be found in dn log of %s."
+
+SQLSTATE: 22000
+
+Description: An error occurs when the index data in the ORC file on the DFS is read.
+
+Solution:Contact technical support.
+
+GAUSS-04710: "Unsupported orc type : %u."
+
+SQLSTATE: 0A000
+
+Description: The DFS table does not support this data type.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04711 - GAUSS-04720
+
+<br/>
+
+GAUSS-04714: "Unsupported data type : %u."
+
+SQLSTATE: 0A000
+
+Description: The HDFS table does not support this data type.
+
+Solution: Change the definition type to the type that the HDFS table supports based on the prompt.
+
+GAUSS-04715: "Invalid string for 'COMPRESSION' option."
+
+SQLSTATE: 22023
+
+Description: The compression mode is invalid.
+
+Solution: Set a correct compression mode when creating a table. The HDFS supports only the zlib or snappy compression algorithm.
+
+<br/>
+
+## GAUSS-04721 - GAUSS-04730
+
+<br/>
+
+GAUSS-04721: "The start index is over the limit."
+
+SQLSTATE: 22000
+
+Description: The imported data exceeds the maximum data volume in the buffer process when the HDFS table is imported and the upper-layer data is written to the bottom data stream.
+
+Solution: Check specific reason information in the corresponding DN logs.
+
+GAUSS-04722: "DFS connector can not be NULL when loading data into dfs table."
+
+SQLSTATE: 42704
+
+Description: The HDFS connection to DFS is an invalid pointer when data is imported to the HDFS.
+
+Solution:Contact technical support.
+
+GAUSS-04726: "We only support pushing down opExpr and null test predicate."
+
+SQLSTATE: 0A000
+
+Description: The type of the filter predicates in the HDFS table is not supported.
+
+Solution:Contact technical support.
+
+GAUSS-04727: "could not find operator by oid %u"
+
+SQLSTATE: 42704
+
+Description: Internal system error. Failed to query the operation type through OID.
+
+Solution:Contact technical support.
+
+GAUSS-04728: "Not support pushing predicate with sublink param now!"
+
+SQLSTATE: 0A000
+
+Description: Internal system error. The predicate of the subquery cannot be pushed down.
+
+Solution:Contact technical support.
+
+GAUSS-04729: "Not support pushing predicate with non-const"
+
+SQLSTATE: 0A000
+
+Description: Internal system error. The non-constant predicate cannot be pushed down.
+
+Solution:Contact technical support.
+
+GAUSS-04730: "We only support pushing down opExpr and null test predicates."
+
+SQLSTATE: 0A000
+
+Description: Internal system error. Only the expression predicate and the null predicate can be pushed down.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04731 - GAUSS-04740
+
+<br/>
+
+GAUSS-04731: "Data type %u has not been supported for predicate push down."
+
+SQLSTATE: 0A000
+
+Description: Internal system error. The error data type does not support dynamic predicate pushdown.
+
+Solution:Contact technical support.
+
+GAUSS-04732: "The maximum accuracy of decimal/numeric data type supported is %d bits."
+
+SQLSTATE: 0A000
+
+Description: The maximum precision supported by the decimal or numeric type exceeds 38 digits.
+
+Solution: Define the precision of the decimal or numeric type to be less than or equal to 38 digits when creating a table.
+
+GAUSS-04737: "There is an illegal character \'%c\' in the option %s."
+
+SQLSTATE: 44000
+
+Description: Invalid characters exist in the option of folder name or file name.
+
+Solution: Check the path specification of the folder name or file name and rebuild the HDFS foreign table.
+
+GAUSS-04738: "The option %s should not be end with \'%c\'."
+
+SQLSTATE: 44000
+
+Description: An error is reported when the option of the file name ends up with a slash (/).
+
+Solution: Do not end up the option of the file name with a slash (/).
+
+<br/>
+
+## GAUSS-04741 - GAUSS-04750
+
+<br/>
+
+GAUSS-04741: "The path '%s' must be an absolute path."
+
+SQLSTATE: 42P17
+
+Description: The path of the file name or folder name is not an absolute path.
+
+Solution: The folder name or file name specified for an HDFS table must be an absolute path.
+
+GAUSS-04742: "The address option exists illegal character: \'%c\'"
+
+SQLSTATE: 44000
+
+Description: Invalid spaces exist in the address option of the server on the HDFS.
+
+Solution: Remove the invalid spaces.
+
+GAUSS-04744: "The count of address '%s' must be not greater than %d."
+
+SQLSTATE: 44000
+
+Description: The number of the addresses cannot exceed 2.
+
+Solution: Ensure that the number of addresses specified during DFS server creation does not exceed 2.
+
+GAUSS-04745: "Unsupport ipv6 foramt"
+
+SQLSTATE: 44000
+
+Description: The address of the DFS server does not support the IPv6 address format.
+
+Solution: Change the address of the DFS server to the IPv4 address format.
+
+GAUSS-04746: "The incorrect address format"
+
+SQLSTATE: 44000
+
+Description: The address format is incorrect.
+
+Solution: View the correct address description.
+
+GAUSS-04747: "Failed to create DfsInsert handler when updating table."
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04748: "build global dfs space cache hash table failed"
+
+SQLSTATE: 42704
+
+Description: Internal system error. Failed to create a global cache for HDFS connections.
+
+Solution:Contact technical support.
+
+GAUSS-04749: "The number of files exceeds the limit %d."
+
+SQLSTATE: 22000
+
+Description: The number of files arrives the upper limit.
+
+Solution:Contact technical support.
+
+GAUSS-04750: "could not initialize DFS space hash table"
+
+SQLSTATE: 42704
+
+Description: Do not create the hash table used for caching the file sequence number.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04751 - GAUSS-04760
+
+<br/>
+
+GAUSS-04752: "could not initialize partition pruning result cache."
+
+SQLSTATE: XX000
+
+Description: Failed to create the cache used for searching for partition when the partitioned table is imported.
+
+Solution: Check whether the server has sufficient memory to create the cache used for searching for partition.
+
+GAUSS-04753: "Unsupported data type on column:%s when forming partition signature"
+
+SQLSTATE: XX000
+
+Description: The data type of the partition key is not supported when the partitioned table is imported.
+
+Solution: Check whether data in the system directory table is consistent and determine whether the created partitioned table and partition column are supported by the partition type.
+
+GAUSS-04756: "could not rewind DFS Partition Loading temporary file: %m"
+
+SQLSTATE: XX000
+
+Description: The cache file fails to move the file cursor when the partitioned table is imported.
+
+Solution: Check whether the temporary files are damaged.
+
+GAUSS-04758: "Only ORC is supported for now."
+
+SQLSTATE: 0A000
+
+Description: Internal system error. The HDFS table in the manual supports only the ORC format.
+
+Solution:Contact technical support.
+
+GAUSS-04759: "DfsStore: unrecognized heap_update status: %u"
+
+SQLSTATE: XX000
+
+Description: The delete and update operations of the DESC table conflict with each other.
+
+Solution:Contact technical support.
+
+GAUSS-04760: "type '%s' is not supported in DFS ORC format column store"
+
+SQLSTATE: 0A000
+
+Description: The data type is not supported by the HDFS table.
+
+Solution: Use other data types when creating the HDFS table.
+
+<br/>
+
+## GAUSS-04761 - GAUSS-04770
+
+<br/>
+
+GAUSS-04761: "Value '%s' of option 'compression' is invalid for row table"
+
+SQLSTATE: 0A000
+
+Description: The column-store table compression parameters are incorrectly specified.
+
+Solution: Change the compression parameters to **yes** or **no**.
+
+GAUSS-04762: "Invalid string for 'filesystem' option."
+
+SQLSTATE: 22023
+
+Description: An error is reported because the value of the **filesystem** is incorrect when a tablespace is created.
+
+Solution: Set **filesystem** to **general** or **hdfs** when creating a tablespace.
+
+GAUSS-04764: "No storepath is specified for a DFS server."
+
+SQLSTATE: XX000
+
+Description: The store path is not specified when the HDFS tablespace is created.
+
+Solution: Specify a store path when creating the HDFS tablespace.
+
+GAUSS-04765: "current text search configuration doesnot support options"
+
+SQLSTATE: 22023
+
+Description: The current configuration does not support options.
+
+Solution: Modify the SQL statement based on the documentation.
+
+GAUSS-04766: "CUListWrite: Cannot allocate memory"
+
+SQLSTATE: XX000
+
+Description: Failed to allocate the memory because the system memory is insufficient.
+
+Solution: After the OS releases part of memory, allocate the memory again.
+
+GAUSS-04767: "could not access status of transaction %lu, nextXid is %lu"
+
+SQLSTATE: XX000
+
+Description: The transaction on the node to be accessed does not exist.
+
+Solution:
+
+- If the transaction status that does not exist is called actively, ignore it.
+- If it is a normal transaction and the node involves this transaction, contact technical support.
+
+GAUSS-04770: "write cu failed, colid(%d) cuid(%u), offset(%lu), size(%d) : %m"
+
+SQLSTATE: XX000
+
+Description: An exception occurs when the data file is written in the asynchronization I/O mode.
+
+Solution: Restore the cluster data file from the standby server or the backup data.
+
+<br/>
+
+## GAUSS-04771 - GAUSS-04780
+
+<br/>
+
+GAUSS-04774: "Snapshot too old."
+
+SQLSTATE: XX000
+
+Description: The queried snapshot is the old snapshot.
+
+Solution: Try again.
+
+GAUSS-04778: "Unable to get store format for Dfs relation %s"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04779: "The relation '%s' has no distribute type."
+
+SQLSTATE: 0A000
+
+Description: The queried table has no distribution type, for example, query the Desc table on the CN.
+
+Solution: This type of table can be queried only on the DN.
+
+<br/>
+
+## GAUSS-04781 - GAUSS-04790
+
+<br/>
+
+GAUSS-04781: "Upper-level GROUPING found where not expected"
+
+SQLSTATE: XX000
+
+Description: The upper-layer grouping cannot exist in the subplan.
+
+Solution: Rewrite the SQL statement which has the same meanings.
+
+GAUSS-04782: "GROUPING found where not expected"
+
+SQLSTATE: XX000
+
+Description: The **WHERE** statement cannot contain grouping.
+
+Solution: Modify the SQL statement.
+
+GAUSS-04783: "ORDER/GROUP BY expression not found in list"
+
+SQLSTATE: XX000
+
+Description: Failed to find the specified **ORDER** or **GROUP** reference in the **ORDER BY** or **GROUP BY** clause.
+
+Solution:Contact technical support.
+
+GAUSS-04784: "Relation with OID %u does not exist."
+
+SQLSTATE: XX000
+
+Description: The queried table does not exist.
+
+Solution:Internal system error.Contact technical support.
+
+GAUSS-04785: "get tablespace %u store path failed"
+
+SQLSTATE: 42P01
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+AUSS-04786: "Un-support feature: HDFS"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04787: "cache lookup failed for bucket %u"
+
+SQLSTATE: 29P01
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04788: "null bucket for tuple %u"
+
+SQLSTATE: 22004
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04789: "got null for pgxc_class option %u"
+
+SQLSTATE: 29P01
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04790: "should in restore mode"
+
+SQLSTATE: 42602
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04791 - GAUSS-04800
+
+<br/>
+
+GAUSS-04791: "invalid hashbucketId syntax"
+
+SQLSTATE: 42602
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04792: "Cannot drop all buckets"
+
+SQLSTATE: D0011
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04793: "Invalid bucket id %u, max bucket id is %d"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04794: "invalid relation file path %s for relpath_parse_rnode"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04795: "Failed to write data to the dfs file list, error code: %d"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04796: "grant to public operation is forbidden in security mode"
+
+SQLSTATE: 0LP01
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04797: "Forbid grant language c to user with grant option."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04798: "Forbid grant language c to public."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04800: "Only roles with sysadmin or createdb privileges can do GRANT/REVOKE."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/49-GAUSS-04801-GAUSS-04900.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/49-GAUSS-04801-GAUSS-04900.md
new file mode 100644
index 0000000000000000000000000000000000000000..65d42bb51094499f2475d4bbf5989c331c096483
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/49-GAUSS-04801-GAUSS-04900.md
@@ -0,0 +1,844 @@
+---
+title: GAUSS-04801 - GAUSS-04900
+summary: GAUSS-04801 - GAUSS-04900
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-04801 - GAUSS-04900
+
+<br/>
+
+## GAUSS-04801 - GAUSS-04810
+
+<br/>
+
+GAUSS-04803: "cache lookup failed for data source %u"
+
+SQLSTATE: 29P01
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04804: "computing nodegroup is not a valid group."
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04805: "directory with OID %u does not exist"
+
+SQLSTATE: 42704
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04807: "data source with OID %u does not exist"
+
+SQLSTATE: 42704
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04808: "synonym with OID %u does not exist"
+
+SQLSTATE: 42704
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04809: "Invalid Oid of local index %u on the partition %u."
+
+SQLSTATE: 42704
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04810: "cache lookup failed for directory %u"
+
+SQLSTATE: 29P01
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04811 - GAUSS-04820
+
+<br/>
+
+GAUSS-04811: "could not find tuple for policy %u"
+
+SQLSTATE: 42704
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04812: "cache lookup failed for synonym %u"
+
+SQLSTATE: 29P01
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04813: "Create hash table directly on DN is not allowed."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04814: "Create hash table but there is no valid PGXCBucketMap."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04815: "Invalid BucketMap or wrong NodeId(%d)"
+
+SQLSTATE: 42P16
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04816: "distributeby no hash is invalid with hashbucket"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04817: "Temp tables are invalid because datanode %s restart. Quit your session to clean invalid temp tables."
+
+SQLSTATE: 42P18
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04818: "u_sess->parser_cxt.param_info should not be NULL"
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04819: "partition name is invalid"
+
+SQLSTATE: 23502
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04820: "null partition key value for relation '%s' in check partkey type."
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04821 - GAUSS-04830
+
+<br/>
+
+GAUSS-04821: "partition key column's number of relation '%s' is not a 1-D smallint array in check partkey type."
+
+SQLSTATE: XX001
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04822: "Object in DEFAULT constraints of column '%s' doesn't exists"
+
+SQLSTATE: 42P02
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04823: "Object in CHECK constraints doesn't exists"
+
+SQLSTATE: 42P02
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04824: "Using CREATE SYNONYM is forbidden in template database."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04825: "synonym '%s' already exists"
+
+SQLSTATE: 42710
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04826: "synonym '%s' does not exist"
+
+SQLSTATE: 42704
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04827: "permission denied to change owner of synonym '%s'"
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04828: "must be initial user"
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04829: "initialize the built-in function failed: %s"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04830: "user-defined indexes on value partition columns are not supported"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04831 - GAUSS-04840
+
+<br/>
+
+GAUSS-04831: "unexpected non-btree speculative unique index"
+
+SQLSTATE: 55000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04832: "resource pool %u was concurrently dropped"
+
+SQLSTATE: 42704
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04833: "multiple pg_shdepend entries: object %u/%u/%u/%d, deptype %c"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04834: "multiple pg_shdepend entries for object %u/%u/%u/%d deptype %c"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04835: "no pg_shdepend entry: object %u/%u/%u/%d, deptype %c"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04836: "Sync failed because there is data inside the delta table %d."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04837: "the current function does not support non-column-store table"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04838: "Function pg_sync_all_cstore_delta doest not support to run on DN."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04839: "enum label '%s' already exists"
+
+SQLSTATE: 42710
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04840: "pg_enum OID value not set when in binary upgrade mode"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04841 - GAUSS-04850
+
+<br/>
+
+GAUSS-04841: "cache lookup failed for existing[%d]!"
+
+SQLSTATE: 29P01
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04842: "can't find installation-group."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04843: "AlTER TABLE ADD/DELETE NODE can only be altered up-to installation group."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04844: "Temp namespace %s not found in pg_namespace. "
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04845: "bogus PopOverrideSearchPath call, stack level %d, xact level %d"
+
+SQLSTATE: XX006
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04846: "Failed to set temp namespace."
+
+SQLSTATE: YY005
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04847: "Can't get nodeoid for relation %d"
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04848: "Temp table's data is invalid because datanode %s restart. Quit your session to clean invalid temp tables."
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04849: "Submit or Isubmit job only can be operate on coordinator."
+
+SQLSTATE: 42704
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04850: "Can not find job id %d in system table pg_job."
+
+SQLSTATE: 42704
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04851 - GAUSS-04860
+
+<br/>
+
+GAUSS-04851: "Permission for current user to get this job. current_user: %s, job_user: %s, job_id: %ld"
+
+SQLSTATE: 42704
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04852: "Can not find jobid %d in system table pg_job_proc."
+
+SQLSTATE: 42704
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04853: "Invalid job status, job_id: %d."
+
+SQLSTATE: 20000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04854: "Invalid job_id: %ld"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04855: "Invalid job_status: \'%c\' "
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04856: "Unable to connect to execute internal query, job_id: %d."
+
+SQLSTATE: SP001
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04857: "Call SPI_execute execute job interval fail, job_id: %d."
+
+SQLSTATE: SP005
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04858: "Execute job interval for get next_date error, job_id: %d."
+
+SQLSTATE: SP000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04859: "Interval: %s must evaluate to a time in the future for job_id: %d."
+
+SQLSTATE: 29000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04860: "It is invalid job interval for the reason that it is a fixed timestamp, job_id: %d, interval: %s."
+
+SQLSTATE: 29000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04861 - GAUSS-04870
+
+<br/>
+
+GAUSS-04861: "Execute job failed, job_id: %d."
+
+SQLSTATE: OP001
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04862: "Invalid parameter interval: \'%s\'."
+
+SQLSTATE: 55000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04863: "Parameter what can not be null."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04864: "Parameter next date can not be null."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04865: "All 32768 jobids have alloc, and there is no free jobid"
+
+SQLSTATE: 55000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04866: "only system/monitor admin can submit multi-node jobs!"
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04867: "Parameter node_name can not be null."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04868: "Parameter node_name can only be 'ALL_NODE' for multi-node jobs."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04869: "Parameter Database can not be null."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04870: "Parameter Database can only be 'postgres'."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04871 - GAUSS-04880
+
+<br/>
+
+GAUSS-04871: "Parameter can not be null."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04872: "Invalid job_id: %d"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04873: "Remove jobid:%ld failed."
+
+SQLSTATE: 55000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04874: "can not find jobid in the job queue %d"
+
+SQLSTATE: 55000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04875: "Parameter id for job_update is unexpected."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04876: "Permission for current user to operate the job. current_user: %s, job_user: %s, job_id: %ld"
+
+SQLSTATE: D0011
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04877: "Can not operate this job due to running status, job_id: %ld. "
+
+SQLSTATE: 29000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04878: "File '%s' does not exist."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04879: "Library File '%s' does not have READ permission."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04880: "Library path can not include character %c."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04881 - GAUSS-04890
+
+<br/>
+
+GAUSS-04881: "Library file name can not include character '%c'."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04882: "Copy file '%s' failed: %m"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04883: "Send library to all node fail: %m, command %s"
+
+SQLSTATE: 58000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04884: "Send library to backup fail: %m, command %s"
+
+SQLSTATE: 58000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04885: "Library file '%s' does not exist."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04886: "abort transaction due to concurrent create function."
+
+SQLSTATE: 40001
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04887: "Invalid library path."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04888: "Do not allow package function overload not package function."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04889: "function '%s' is a builtin function,it can not be changed"
+
+SQLSTATE: 42P13
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04890: "can not get current user name."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04891 - GAUSS-04900
+
+<br/>
+
+GAUSS-04891: "package function does not support table parameter."
+
+SQLSTATE: 42P13
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04892: "package function does not support variadic parameter."
+
+SQLSTATE: 42P13
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04893: "Do not allow package function replace not package function."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04894: "Package function does not support function overload which has the same type argument."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04895: "File path can not include character '%c'"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04896: "couldn't get database name"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04897: "out of binary heap slots"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04898: "doubly linked list head address is NULL"
+
+SQLSTATE: 23502
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04899: "doubly linked list is corrupted."
+
+SQLSTATE: XX001
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04900: "singly linked list head address is NULL"
+
+SQLSTATE: 23502
+
+Description: Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/5-GAUSS-00401-GAUSS-00500.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/5-GAUSS-00401-GAUSS-00500.md
new file mode 100644
index 0000000000000000000000000000000000000000..03d90d78a7a3302be0f4f3855a1b418cc35a5178
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/5-GAUSS-00401-GAUSS-00500.md
@@ -0,0 +1,692 @@
+---
+title: GAUSS-00401 - GAUSS-00500
+summary: GAUSS-00401 - GAUSS-00500
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-00401 - GAUSS-00500
+
+<br/>
+
+## GAUSS-00401 - GAUSS-00410
+
+<br/>
+
+GAUSS-00401: "access method 'psort' does not support index expressions"
+
+SQLSTATE: 0A000
+
+Description: When **psort** is specified for the **INDEX** clause in the **CREATE INDEX** or **ALTER TABLE** syntax, the **INDEX** clause contains an expression.
+
+Solution: Modify the syntax to ensure that the expression does not exist.
+
+GAUSS-00402: "Partition key value can not be null"
+
+SQLSTATE: 42601
+
+Description: When a partitioned table is to be created, the partition key value specified using **PARTATION BY RANGE (partition_key)(range_partition_definition_list)** is null.
+
+Solution: Ensure that the partition key value is valid.
+
+GAUSS-00403: "partition key value must be const or const-evaluable expression"
+
+SQLSTATE: 42601
+
+Description: When a partitioned table is to be created, the partition key value specified using **PARTATION BY RANGE (partition_key)(range_partition_definition_list)** is not measurable.
+
+Solution: Ensure that the specified value is a measurable constant or a constant expression.
+
+GAUSS-00404: "argument name '%s' used more than once"
+
+SQLSTATE: 42601
+
+Description: Duplicate parameter names.
+
+Solution: Rename the parameter.
+
+GAUSS-00405: "positional argument cannot follow named argument"
+
+SQLSTATE: 42601
+
+Description: The positional parameter follows behind a named parameter.
+
+Solution: Change the parameter position.
+
+GAUSS-00406: "%s(*) specified, but %s is not an aggregate function"
+
+SQLSTATE: 42809
+
+Description: %s(*) is specified, but function is not an aggregate one.
+
+Solution: Select a valid aggregate function.
+
+GAUSS-00407: "DISTINCT specified, but %s is not an aggregate function"
+
+SQLSTATE: 42809
+
+Description:**DISTINCT** is specified, but the function is not an aggregate one.
+
+Solution: Select a valid aggregate function.
+
+GAUSS-00408: "ORDER BY specified, but %s is not an aggregate function"
+
+SQLSTATE: 42809
+
+Description:**GROUP BY** is specified, but the function is not an aggregate one.
+
+Solution: Select a valid aggregate function.
+
+GAUSS-00409: "OVER specified, but %s is not a window function nor an aggregate function"
+
+SQLSTATE: 42809
+
+Description:**OVER** is specified, but the function is not a window or aggregate one.
+
+Solution: Select a valid window or aggregate function.
+
+GAUSS-00410: "function %s is not unique"
+
+SQLSTATE: 42725
+
+Description: The function is not unique.
+
+Solution: Specify the parameter type and select an optimum function based on the parameter type.
+
+<br/>
+
+## GAUSS-00411 - GAUSS-00420
+
+<br/>
+
+GAUSS-00411: "function %s does not exist"
+
+SQLSTATE: 42883
+
+Description: The function does not exist.
+
+Solution: Ensure that the required function has been defined.
+
+GAUSS-00412: "%s(*) must be used to call a parameterless aggregate function"
+
+SQLSTATE: 42809
+
+Description: When a function or expression is created as an aggregate function, the function parameters are empty but not asterisks (*).
+
+Solution: Use asterisks (*) if the function parameters are empty.
+
+GAUSS-00413: "aggregates cannot return sets"
+
+SQLSTATE: 42P13
+
+Description: When a function or expression is created as an aggregate function, this function returns a set.
+
+Solution: Check the function return type and ensure that no sets can be returned.
+
+GAUSS-00414: "aggregates cannot use named arguments"
+
+SQLSTATE: 0A000
+
+Description: When a function or expression is called as an aggregate function, this function uses parameter names.
+
+Solution: Use valid values instead of parameter names when calling an aggregate function.
+
+GAUSS-00415: "window function call requires an OVER clause"
+
+SQLSTATE: 42809
+
+Description: When a function or expression is called as a window function, the **OVER** clause is not defined.
+
+Solution: Define the **OVER** clause.
+
+GAUSS-00416: "DISTINCT is not implemented for window functions"
+
+SQLSTATE: 0A000
+
+Description: When a function or expression is called as a window function, this window function contains a **DISTINCT** clause.
+
+Solution: Check the syntax and delete the **DISTINCT** clause if any.
+
+GAUSS-00417: "aggregate ORDER BY is not implemented for window functions"
+
+SQLSTATE: 0A000
+
+Description: When a function or expression is called as a window function, this function contains an **ORDER BY** clause.
+
+Solution: Check the syntax and delete the **ORDER BY** clause if any.
+
+GAUSS-00418: "window functions cannot return sets"
+
+SQLSTATE: 42P13
+
+Description: When a function or expression is created as a window function, this function returns a set.
+
+Solution: Check the function return type and ensure that no sets can be returned.
+
+GAUSS-00419: "window functions cannot use named arguments"
+
+SQLSTATE: 0A000
+
+Description: When you call a function or expression as a window function, this function uses parameter names.
+
+Solution: Use valid values instead of parameter names when calling a window function.
+
+GAUSS-00420: "not enough default arguments"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-00421 - GAUSS-00430
+
+<br/>
+
+GAUSS-00421: "function %s asks parameters"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00422: "aggregate %s(*) does not exist"
+
+SQLSTATE: 42883
+
+Description: The aggregate function contains an invalid parameter.
+
+Solution: Check whether the number of parameters is zero.
+
+GAUSS-00423: "aggregate %s does not exist"
+
+SQLSTATE: 42883
+
+Description: The aggregate function is invalid.
+
+Solution: Check whether the aggregate function is contained in the **pg_proc** table.
+
+GAUSS-00424: "function %s is not an aggregate"
+
+SQLSTATE: 42809
+
+Description: The created function is not an invalid aggregate function.
+
+Solution: Ensure that functions with asterisks (*) as parameters must be aggregate functions.
+
+GAUSS-00426: "inconsistent types deduced for parameter $%d"
+
+SQLSTATE: 42P08
+
+Description: Usage not supported.
+
+Solution: Modify the SQL statement.
+
+GAUSS-00427: "could not determine data type of parameter $%d"
+
+SQLSTATE: 42P08
+
+Description: The parameter data type cannot be recognized.
+
+Solution: Change the parameter value to a value recognizable to the system. For the value types recognizable to the system, see en-us_topic_0237121926.html.
+
+GAUSS-00428: "could not create syslogger data transfer thread: %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00429: "could not create pipe for syslog: %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00430: "could not redirect stdout: %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-00431 - GAUSS-00440
+
+<br/>
+
+GAUSS-00431: "could not redirect stderr: %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00432: "checkpoint request failed"
+
+SQLSTATE: XX000
+
+Description: An internal checkpoint error occurs.
+
+Solution:Contact technical support.
+
+GAUSS-00433: "ForwardFsyncRequest must not be called in checkpointer"
+
+SQLSTATE: XX000
+
+Description: An internal checkpoint error occurs.
+
+Solution:Contact technical support.
+
+GAUSS-00434: "could not open archive status directory '%s': %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00435: "no free worker found"
+
+SQLSTATE: XX000
+
+Description: No threads are available to clear 2PC transactions.
+
+Solution: Increase the value of **autovacuum_max_workers**.
+
+GAUSS-00436: "cache lookup failed for database %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00437: "the options of -M is not recognized"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00438: "-%s requires a value"
+
+SQLSTATE: 42601
+
+Description: The value of a parameter is not specified in the command.
+
+Solution: Assign a value to the parameter used in the command.
+
+GAUSS-00439: "-c %s requires a value"
+
+SQLSTATE: 42601
+
+Description: The value of a parameter is not specified in the command.
+
+Solution: Assign a value to the parameter used in the command.
+
+GAUSS-00440: "invalid list syntax for 'listen_addresses'"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-00441 - GAUSS-00450
+
+<br/>
+
+GAUSS-00442: "could not create any TCP/IP sockets"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00444: "no socket created for listening"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00445: "could not create I/O completion port for child queue"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00446: "could not load pg_hba.conf"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00447: "%s: could not locate my own executable path"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00448: "%s: could not locate matching postgres executable"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00449: "could not open directory '%s': %m"
+
+SQLSTATE: XX000
+
+Description: Failed to open a directory.
+
+Solution: Analyze the cause based on the error message. If the directory does not exist, create one. If the permission is incorrect, change the permission. If the directory is damaged, restore the file system or disk.
+
+GAUSS-00450: "data directory '%s' does not exist"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-00451 - GAUSS-00460
+
+<br/>
+
+GAUSS-00451: "could not read permissions of directory '%s': %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00452: "specified data directory '%s' is not a directory"
+
+SQLSTATE: 55000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00453: "data directory '%s' has wrong ownership"
+
+SQLSTATE: 55000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00454: "data directory '%s' has group or world access"
+
+SQLSTATE: 55000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00457: "hot standby is not possible because wal_level was not set to 'hot_standby'"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00458: "when starting as dual mode, we must ensure wal_level was not 'minimal' and max_wal_senders was set at least 1"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-00461 - GAUSS-00470
+
+<br/>
+
+GAUSS-00466: "sorry, too many clients already"
+
+SQLSTATE: 53300
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-00471 - GAUSS-00480
+
+<br/>
+
+GAUSS-00474: "fcntl F_GETFD failed!"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00475: "fcntl F_SETFD failed!"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00476: "could not set timer for startup packet timeout"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00477: "could not disable timer for startup packet timeout"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00478: "out of memory"
+
+SQLSTATE: 53200
+
+Description: Failed to allocate the memory.
+
+Solution: Ensure that the system has sufficient memory.
+
+<br/>
+
+## GAUSS-00481 - GAUSS-00490
+
+<br/>
+
+GAUSS-00481: "parameter error in ParseHaListenAddr()"
+
+SQLSTATE: XX000
+
+Description: The function **ParseHaListenAddr** uses an incorrect parameter.
+
+Solution: Find out the reason why the imported parameter pointer is null.
+
+GAUSS-00482: "must be system admin to reset statistics counters"
+
+SQLSTATE: 42501
+
+Description: Only the system administrator has the permission to reset statistics counters.
+
+Solution: Switch to a system administrator.
+
+GAUSS-00483: "unrecognized reset target: '%s'"
+
+SQLSTATE: 22023
+
+Description: The target parameter to be reset is incorrect.
+
+Solution: The parameter must be **bgwriter**.
+
+GAUSS-00484: "could not read statistics message: %m"
+
+SQLSTATE: XX000
+
+Description:**pgStat** cannot read statistics messages.
+
+Solution: Communication between threads in the database is abnormal. Contact technical support.
+
+GAUSS-00485: "database hash table corrupted during cleanup - abort"
+
+SQLSTATE: XX000
+
+Description: The hash table is corrupted during the database cleanup.
+
+Solution: This is an internal database error. Contact technical support.
+
+GAUSS-00486: "could not create sysauditor data transfer thread: %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00487: "could not create pipe for sysaudit: %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00488: "could not write to audit file: %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00489: "set-valued function called in context that cannot accept a set"
+
+SQLSTATE: 0A000
+
+Description: The function that is expected to return a result set fails to return a result set.
+
+Solution: Ensure that this function is defined to return a result set.
+
+GAUSS-00490: "materialize mode required, but it is not allowed in this context"
+
+SQLSTATE: 0A000
+
+Description: The returned tuplestore is not supported in this context.
+
+Solution: Change the return value type.
+
+<br/>
+
+## GAUSS-00491 - GAUSS-00500
+
+<br/>
+
+GAUSS-00491: "return type must be a row type"
+
+SQLSTATE: XX000
+
+Description: The tuple descriptor constructed is not a row result message.
+
+Solution: Query again. Check whether this error persists. Contact technical support.
+
+GAUSS-00492: "attribute count of the return row type not matched"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00493: "permission denied to query audit"
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00494: "permission denied to delete audit"
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00495: "conflicting or redundant options"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00496: "option '%s' not recognized"
+
+SQLSTATE: XX000
+
+Description: The value of a copy option cannot be recognized.
+
+Solution: Ensure that the value is correct.
+
+GAUSS-00497: "%d is not a valid encoding code"
+
+SQLSTATE: 42704
+
+Description: When a character string is converted into ASCII code, the specified code identifier is not used.
+
+Solution: Ensure that the No. of the specified code identifier is smaller than 42.
+
+GAUSS-00498: "%s is not a valid encoding name"
+
+SQLSTATE: 42704
+
+Description: When a character string is converted to ASCII code, an invalid character encoding name is used.
+
+Solution: Ensure that the code identifier name is valid.
+
+GAUSS-00500: "permission denied to create database"
+
+SQLSTATE: 42501
+
+Description: You do not have permission to create a database.
+
+Solution: Only the user having the CREATEDB permission or the system administrator has permission to create a database. Ensure that you have permission to create a database.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/50-GAUSS-04901-GAUSS-05000.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/50-GAUSS-04901-GAUSS-05000.md
new file mode 100644
index 0000000000000000000000000000000000000000..4ec7a3be371195607943ca463ab2004bc48abdc7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/50-GAUSS-04901-GAUSS-05000.md
@@ -0,0 +1,860 @@
+---
+title: GAUSS-04901 - GAUSS-05000
+summary: GAUSS-04901 - GAUSS-05000
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-04901 - GAUSS-05000
+
+<br/>
+
+## GAUSS-04901 - GAUSS-04910
+
+<br/>
+
+GAUSS-04901: "pg_hba.conf rejects replication connection for host '%s', user '%s', %s"
+
+SQLSTATE: 28000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04902: "pg_hba.conf rejects replication connection for host '%s', user '%s'"
+
+SQLSTATE: 28000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04903: "no pg_hba.conf entry for replication connection from host '%s', user '%s', %s"
+
+SQLSTATE: 28000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04904: "no pg_hba.conf entry for replication connection from host '%s', user '%s'"
+
+SQLSTATE: 28000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04905: "Forbid remote connection with initial user."
+
+SQLSTATE: 28000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04906: "Failed to Generate the random number,errcode:%d"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04907: "Failed to Generate the fake salt"
+
+SQLSTATE: 28000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04908: "Failed to Generate the random serverkey,errcode:%d"
+
+SQLSTATE: 28000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04909: "Failed to Generate the random storedkey,errcode:%d"
+
+SQLSTATE: 28000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04910: "GSS authentication method is not allowed because %s user password is not disabled."
+
+SQLSTATE: 28000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04911 - GAUSS-04920
+
+<br/>
+
+GAUSS-04911: "empty password returned by client"
+
+SQLSTATE: 28P01
+
+Description: The client returns an empty password.
+
+Solution: Contact technical support.
+
+GAUSS-04912: "Could not get user information on this platform"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04913: "could not look up local user ID %ld: %s"
+
+SQLSTATE: D0011
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04914: "could not create SSL context : %s.)"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04915: "certificate file '%s' has group or world access"
+
+SQLSTATE: F0000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04916: "ca certificate file '%s' has group or world access"
+
+SQLSTATE: F0000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04917: "DH: generating parameters (3072 bits) failed"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04918: "Last read message sequence %u is not equal to the max written message sequence %u"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04919: "alert, failed in revert command buffer, invalid params data len %d pq buffer size %d"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04920: "expected message sequnce is %d, actual message sequence is %d"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04921 - GAUSS-04930
+
+<br/>
+
+GAUSS-04921: "expected message length is %d, actual message length is %d"
+
+SQLSTATE: 22026
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04922: "expected crc is %u, actual crc is %u"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04923: "varno is unvalid"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04924: "name for %s %u not found"
+
+SQLSTATE: 29P01
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04925: "namespace for %s %u not found"
+
+SQLSTATE: 29P01
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04926: "seqname of nextval() is not found"
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04927: "token should not return NULL."
+
+SQLSTATE: 22004
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04928: "incomplete array structure"
+
+SQLSTATE: 2202E
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04929: "unterminated array structure"
+
+SQLSTATE: 2202E
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04930: "NULL seqName for nextval()"
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04931 - GAUSS-04940
+
+<br/>
+
+GAUSS-04931: "NULL seqNamespace for nextval()"
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04932: "_readConstraint(): badly contype '%s'…"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04933: "expected '[' to start datum, but got '%s'; length = %lu"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04934: "WITHIN GROUP specified, but %s is not an aggregate function"
+
+SQLSTATE: 42809
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04935: "WITHIN GROUP is required for ordered-set aggregate %s"
+
+SQLSTATE: 42809
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04936: "OVER is not supported for ordered-set aggregate %s"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04937: "DISTINCT + WITHIN GROUP is not supported for ordered-set aggregate %s"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04938: "VARIADIC + WITHIN GROUP is not supported for ordered-set aggregate %s"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04939: "%s is not an ordered-set aggregate, so it cannot have WITHIN GROUP"
+
+SQLSTATE: 42809
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04940: "window function %s requires an OVER clause"
+
+SQLSTATE: 42809
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04941 - GAUSS-04950
+
+<br/>
+
+GAUSS-04941: "window function %s cannot have WITHIN GROUP"
+
+SQLSTATE: 42809
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04942: "window functions cannot allow multiple different order info"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04943: "Operator '(+)' can only be used in WhereClause of Select-Statement or Subquery."
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04944: "column reference '%s' is ambiguous."
+
+SQLSTATE: 42702
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04945: "name data must be quoted"
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04946: "REBUILD is not supported for multiple commands"
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04947: "IF EXISTS is not supported for REBUILD"
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04948: "Must use single quoted string for '%s' option."
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04949: "Row Level Security is not yet supported for INSERT and MERGE"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04950: "unrecognized row security option '%s'"
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04951 - GAUSS-04960
+
+<br/>
+
+GAUSS-04951: "WITH GRANT OPTION is not supported in security mode."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04952: "FENCED mode function is not yet supported in current version."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04953: "COMPACT can only be used with VACUUM FULL"
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04954: "COMPACT can not be used with FREEZE"
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04955: "COMPACT can not be used with PARTITION"
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04956: "COMPACT can not be used with ANALYZE"
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04957: "RETURNING clause is not yet supported whithin INSERT ON DUPLICATE KEY UPDATE statement."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04958: "WITH clause is not yet supported whithin INSERT ON DUPLICATE KEY UPDATE statement."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04959: "Subfield name or array subscript of column '%s' is not yet supported whithin INSERT ON DUPLICATE KEY UPDATE statement."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04960: "Update with subquery is not yet supported whithin INSERT ON DUPLICATE KEY UPDATE statement."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04961 - GAUSS-04970
+
+<br/>
+
+GAUSS-04961: "only allow column name within VALUES"
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04962: "missing WITHIN keyword."
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04963: "cannot use multiple ORDER BY clauses with WITHIN GROUP."
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04964: "cannot use DISTINCT with WITHIN GROUP."
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04965: "cannot use VARIADIC with WITHIN GROUP."
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04966: "cannot use multiple ORDER BY clauses with WITHIN GROUP"
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04967: "cannot use DISTINCT with WITHIN GROUP"
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04968: "cannot use VARIADIC with WITHIN GROUP"
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04969: "timestampdiff syntax is not supported."
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04970: "type modifier cannot have ORDER BY"
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04971 - GAUSS-04980
+
+<br/>
+
+GAUSS-04971: "No function matches the given arguments names. You might need to add explicit declare arguments names."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04972: "argname should not be null"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04974: "must be system admin or monitor admin to use EXECUTE DIRECT"
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04975: "Unsupported typeoid: %d for T_Integer value, please add single quota and try again."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04976: "pstate->p_target_relation is NULL unexpectedly"
+
+SQLSTATE: 22004
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04977: "tupleDesc should not be null"
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04978: "It is forbidden to use placeholder and dollar quoting together."
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04979: "type '%s' must be in installation group"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04980: "Date type is unsupported for hdfs table in TD-format database."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04981 - GAUSS-04990
+
+<br/>
+
+GAUSS-04981: "u_sess->parser_cxt.opr_cache_hash should not be null"
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04982: "OprCacheHash is unexpected null"
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04983: "relation '%s.%s' does not exist on%s %s"
+
+SQLSTATE: 42P01
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04984: "relation '%s' does not exist on%s %s"
+
+SQLSTATE: 42P01
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04985: "pstate can not be NULL"
+
+SQLSTATE: 22004
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04986: "permission denied to select from foreign table in security mode"
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04987: "relation '%s' does not have hash buckets"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04988: "Do not support create table with INERNAL DATA clause."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04989: "It's not supported to create serial column on temporary table"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04990: "It's not supported to alter table add serial column"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-04991 - GAUSS-05000
+
+<br/>
+
+GAUSS-04991: "CREATE TABLE LIKE with column sequence in different NodeGroup is not supported."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04992: "Table %s.%s does not exist in current datanode."
+
+SQLSTATE: 42P01
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04993: "timeseries store does not support add index "
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04994: "Unsupport cgin index in this version"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04995: "access method '%s' does not support row store"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04996: "access method '%s' does not support dfs store"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04997: "permission denied to alter foreign table in security mode"
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04998: "split partition '%s' does not exist."
+
+SQLSTATE: 42P01
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-04999: "access method 'cbtree' does not support WHERE clause"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05000: "access method 'cbtree' does not support index expressions"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/51-GAUSS-05001-GAUSS-05100.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/51-GAUSS-05001-GAUSS-05100.md
new file mode 100644
index 0000000000000000000000000000000000000000..9813aecd2796b450c91594804b4aefa1f0205867
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/51-GAUSS-05001-GAUSS-05100.md
@@ -0,0 +1,868 @@
+---
+title: GAUSS-01801 - GAUSS-01900
+summary: GAUSS-01801 - GAUSS-01900
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-05001 - GAUSS-05100
+
+<br/>
+
+## GAUSS-05001 - GAUSS-05010
+
+<br/>
+
+GAUSS-05001: "access method 'cgin' does not support WHERE clause"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05002: "access method 'cgin' does not support null text search parser"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05003: "It is not allowed to support 'NOT ENFORCED' informational constraint."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05004: "The foreign table only support 'NOT ENFORCED' informational constraint."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05005: "Only the primary key, unique, not null and null be supported."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05006: "CAN NOT get detail info from a NON-PARTITIONED relation."
+
+SQLSTATE: 42P17
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05007: "CAN NOT get detail info from a partitioned relation WITHOUT specified partition."
+
+SQLSTATE: 42P17
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05008: "CAN NOT get partition oid from a NON-PARTITIONED relation."
+
+SQLSTATE: 42P17
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05009: "start/end/every value must be an const-integer for partition '%s'"
+
+SQLSTATE: 42P16
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05010: "unexpected parameter for precheck start/end defstate."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05011 - GAUSS-05020
+
+<br/>
+
+GAUSS-05011: "partition parameter is not constant."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05012: "start value must be less than end value for partition '%s'."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05013: "ambiguous partition rule is raised by EVERY parameter in partition '%s'."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05014: "partition step is too small for partition '%s'."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05015: "partition step is too big for partition '%s'."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05016: "too many partitions after split partition '%s'."
+
+SQLSTATE: 42P16
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05017: "partition '%s' is invalid."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05018: "unsupported datatype served as a partition key in the start/end clause."
+
+SQLSTATE: 42804
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05019: "start value of partition '%s' is too low."
+
+SQLSTATE: 42P16
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05020: "partitioned table has too many partition keys."
+
+SQLSTATE: 42P16
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05021 - GAUSS-05030
+
+<br/>
+
+GAUSS-05021: "too many partition keys for partition '%s'."
+
+SQLSTATE: 42P16
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05022: "datatype of column '%s' is unsupported for partition key in start/end clause."
+
+SQLSTATE: 42804
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05023: "can not add more partitions as partition number is already at its maximum."
+
+SQLSTATE: 42804
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05024: "partition '%s' is not allowed behind MAXVALUE."
+
+SQLSTATE: 42P16
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05025: "start value of partition '%s' is too high."
+
+SQLSTATE: 42P16
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05026: "start value can not be MAXVALUE for partition '%s'."
+
+SQLSTATE: 42P16
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05027: "start value of partition '%s' NOT EQUAL up-boundary of last partition."
+
+SQLSTATE: 42P16
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05028: "end value of partition '%s' is too low."
+
+SQLSTATE: 42P16
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05029: "partition '%s' is an invalid definition clause."
+
+SQLSTATE: 42P16
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05030: "start value of partition '%s' MUST be less than up-boundary of the partition to be splitted."
+
+SQLSTATE: 42P16
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05031 - GAUSS-05040
+
+<br/>
+
+GAUSS-05031: "end value of partition '%s' NOT EQUAL up-boundary of the partition to be splitted."
+
+SQLSTATE: 42P16
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05032: "duplicate partition name: '%s'."
+
+SQLSTATE: 42710
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05033: "Not specify 'INCLUDING PARTITION' for partitioned-table relation:'%s'"
+
+SQLSTATE: 42809
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05034: "check failure with rt_fetch function"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05035: "permission denied to insert into foreign table in security mode"
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05036: "Invalid tablesample method %s"
+
+SQLSTATE: 42704
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05037: "tablesample method %s requires %d argument, not %d"
+
+SQLSTATE: 42809
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05038: "TABLESAMPLE clause can only be applied to tables."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05039: "TABLESAMPLE clause only support relation of oriented-row and oriented-column."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05040: "Cannot find expected NOT MATCHED WHEN clause with operator INSERT."
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05041 - GAUSS-05050
+
+<br/>
+
+GAUSS-05041: "Subquery should at least have a target list or values list."
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05042: "Default column should have default values."
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05043: "Expression whitin primary key or unique index are not supported yet."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05044: "Should not specify INSERT target columns in DEFAULT VALUES."
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05045: "pstate->p_target_relation should not be null"
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05046: "internal relation doesn't allow %s"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05047: "Target relation type is not supported for %s"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05048: "unknown action in MERGE WHEN clause"
+
+SQLSTATE: XX006
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05049: "unreachable WHEN clause specified after unconditional WHEN clause"
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05050: "Two WHEN MATCHED clauses are not supported for MERGE INTO"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05051 - GAUSS-05060
+
+<br/>
+
+GAUSS-05051: "Two WHEN NOT MATCHED clauses are not supported for MERGE INTO"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05052: "Invalid column reference in the UPDATE target values"
+
+SQLSTATE: 42703
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05053: "failed to transform InsertStmt for INSERT ON DUPLICATE KEY UPDATE statement."
+
+SQLSTATE: XX006
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05054: "Columns referenced in the primary or unique index cannot be updated: '%s'.'%s'"
+
+SQLSTATE: 42P10
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05055: "Columns referenced in the ON Clause cannot be updated: '%s'.'%s'"
+
+SQLSTATE: 42P10
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05056: "Replicate table only allows to INSERT static values from a VALUES clause in INSERT … ON DUPLICATE KEY UPDATE."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05057: "It is not allowed to use %s on the replicate table (%s) with column (%s) of unstable default value."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05058: "Subquery in WHERE clauses are not yet supported for %s"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05059: "Subquery in INSERT/UPDATE clauses are not yet supported for %s"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05060: "System Column reference are not yet supported for %s"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05061 - GAUSS-05070
+
+<br/>
+
+GAUSS-05061: "Subquery should at least have a target column."
+
+SQLSTATE: 42703
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05062: "Unexpected Node type '%s'"
+
+SQLSTATE: XX004
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05063: "Invalid column reference in the INSERT VALUES Clause"
+
+SQLSTATE: 42703
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05064: "aggregates not allowed in FROM clause"
+
+SQLSTATE: 42803
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05065: "unexpected args inside agg direct args"
+
+SQLSTATE: 42P25
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05066: "functions can have at most %d parameters"
+
+SQLSTATE: 54000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05067: "Operator '(+)' unknown node detected in %s()"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05068: "Relation can't outer join with each other."
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05069: "'%s' can't outer join with more than one relation."
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05070: "Operator '(+)' can't be specified on more than one relation in one join condition"
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05071 - GAUSS-05080
+
+<br/>
+
+GAUSS-05071: "'%s' can't outer join with more than one relation"
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05072: "Operator '(+)' and Join in FromClause can't be used together"
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05073: "Operator '(+)' is not allowed used with 'OR' together"
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05074: "Operator '(+)' transform failed."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05075: "'%s' is not allowed to outer join with itself."
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05076: "Operator '(+)' can not be used in outer join with SubQuery."
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05077: "Operator '(+)' can not be used in nesting expression."
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05078: "unrecognized A_Expr kind: %d used"
+
+SQLSTATE: XX004
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05079: "INSERT ON DUPLICATE KEY UPDATE is not supported on column orientated table."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05080: "INSERT ON DUPLICATE KEY UPDATE is not supported on foreign table."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05081 - GAUSS-05090
+
+<br/>
+
+GAUSS-05081: "INSERT ON DUPLICATE KEY UPDATE is not supported on VIEW."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05082: "INSERT ON DUPLICATE KEY UPDATE don't allow update on primary key or unique key."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05083: "rte is not in p_rtable list"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05084: "leftmostQuery should not be null"
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05085: "node name in node list is not coorrect"
+
+SQLSTATE: OP003
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05086: "unsupport node type: %d"
+
+SQLSTATE: XX006
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05087: "not support both coordinator and datanode in the execute list"
+
+SQLSTATE: OP003
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05088: "EXECUTE DIRECT cannot execute CREATE RULE"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05089: "EXECUTE DIRECT cannot execute SELECT query with normal table on coordinator"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05090: "subParseState should not be null"
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05091 - GAUSS-05100
+
+<br/>
+
+GAUSS-05091: "non-integer constant in group clause"
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05092: "%s position %ld is not in select list"
+
+SQLSTATE: 42P10
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05093: "Out of memory"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05094: "message len is too short."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05095: "you can only take append_mode = on, off, refresh, read_only, end_catchup"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05096: "Alter-Table set append mode should have 'rel_cn_oid' set together"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05097: "Alter-Table set rel_cn_oid should have 'append_mode' set together"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05098: "Proc redistribution only can be set during data redistribution time"
+
+SQLSTATE: D0011
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05099: "Proc redistribution only can be reset during data redistribution time"
+
+SQLSTATE: D0011
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05100: "Modulo value: %d out of range %d.\n"
+
+SQLSTATE: 22003
+
+Description: Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/52-GAUSS-05101-GAUSS-05200.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/52-GAUSS-05101-GAUSS-05200.md
new file mode 100644
index 0000000000000000000000000000000000000000..8797c6c30ea658c824d166a1329d80581742ccaa
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/52-GAUSS-05101-GAUSS-05200.md
@@ -0,0 +1,604 @@
+---
+title: GAUSS-05101 - GAUSS-05200
+summary: GAUSS-05101 - GAUSS-05200
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-05101 - GAUSS-05200
+
+<br/>
+
+## GAUSS-05101 - GAUSS-05110
+
+<br/>
+
+GAUSS-05101: "Could not alloc new memory."
+
+SQLSTATE: 58000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05102: "Can't get group member"
+
+SQLSTATE: 58000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05103: "null type_loc is invalid"
+
+SQLSTATE: 22004
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05104: "PGXC node %s: cannot be a central node, it has to be a Coordinator"
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05105: "the replication type should be multi-standby, now is %d"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05106: "DN matric cannot alloc memory."
+
+SQLSTATE: 53000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05107: "PGXC Node %s(host = %s, port = %d, sctp_port = %d, control_port = %d): object already defined"
+
+SQLSTATE: 42710
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05108: "Datanode %s: can not be central node."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05109: "PGXC node %s is central node already."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05110: "parameter requires a Boolean value"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05111 - GAUSS-05120
+
+<br/>
+
+GAUSS-05112: "Get buckets failed.reason:the buckets number(%d) is not correct(%d)."
+
+SQLSTATE: D0011
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05113: "group_members is null for tuple %u"
+
+SQLSTATE: 22004
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05116: "Can not find redistributed source group with in_redistribution 'y'."
+
+SQLSTATE: 42704
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05119: "NodeGroup name %s can not be preserved group name"
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05121 - GAUSS-05130
+
+<br/>
+
+GAUSS-05126: "group_name can not be NULL "
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05131 - GAUSS-05140
+
+<br/>
+
+GAUSS-05133: "The installation group has no members."
+
+SQLSTATE: 58000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05137: "No destgroup in resize process"
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05138: "NodeGroup name %s is invalid."
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05141 - GAUSS-05150
+
+<br/>
+
+GAUSS-05145: "cannot drop '%s' because other objects depend on it"
+
+SQLSTATE: 2BP01
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05150: "cannot drop '%s' because at least one role %u depend on it"
+
+SQLSTATE: 2BP01
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+<br/>
+
+## GAUSS-05151 - GAUSS-05160
+
+<br/>
+
+GAUSS-05152: "default_storage_nodegroup %s not defined."
+
+SQLSTATE: 42710
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05153: "Bucketmap is not found with given groupoid %u"
+
+SQLSTATE: 42704
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05155: "Connection to database failed: %s"
+
+SQLSTATE: 58000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05156: "execute statement: %s failed: %s"
+
+SQLSTATE: 58000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05157: "PQtuples num is invalid : %d"
+
+SQLSTATE: 58000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05158: "fail to get tables in database %s for query remain table"
+
+SQLSTATE: 58000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05160: "Invalid null pointer attribute for gs_get_nodegroup_tablecount()"
+
+SQLSTATE: 42P24
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05161 - GAUSS-05170
+
+<br/>
+
+AUSS-05161: "can not open pg_database"
+
+SQLSTATE: 58000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05162: "count is invalid, count:%d, tmpCount:%d"
+
+SQLSTATE: 58000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05163: "must be system admin or operator admin in operation mode to manage pooler"
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05164: "pg_pool_ping cannot run inside a transaction block"
+
+SQLSTATE: 25001
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05165: "invalid input/output buffer in node handle"
+
+SQLSTATE: 53200
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05166: "out of memory for node handles"
+
+SQLSTATE: 53200
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05167: "coordinator cannot identify itself"
+
+SQLSTATE: XX000
+
+Description: An internal system error occurs. The **pgxc_node** system catalog may have been damaged or the user has modified the **pgxc_node_name** parameter of the failed node.
+
+Solution: It is not recommended that users modify the **pgxc_node_name** parameter. If the fault is caused by incorrect parameter modification, perform the following operations: 1. Enable the CN in restore mode. Obtain the nodename by querying the **pgxc_node system** table. Restore the configuration parameter based on the nodename obtained. 2. Restore the configuration parameter using the standard log name of this instance generated in OM mode. "
+
+GAUSS-05168: "message len is too short"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05169: "conn cursor overflow"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05170: "Invalid Datanode number"
+
+SQLSTATE: 53200
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05171 - GAUSS-05180
+
+<br/>
+
+GAUSS-05171: "Invalid coordinator number"
+
+SQLSTATE: 53200
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05172: "failed to get pooled connections"
+
+SQLSTATE: 53000
+
+Description: Failed to request connections from the **pooler manager** thread.
+
+Solution: Locate the root cause by viewing the **pooler manager** logs close to the error log. Perform restoration based on such logs.
+
+GAUSS-05173: "replication type is invalid in PGXCNodeGetNodeId (nodeoid = %u, node_type = %c"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05174: "Failed to connect to the compute pool. See log file for more details."
+
+SQLSTATE: 08006
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05175: "Write to replicated table returned different results from the Datanodes on current DN:%s and previous DN:%s."
+
+SQLSTATE: XX001
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05176: "Unexpected TUPDESC response from Datanode"
+
+SQLSTATE: 08000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05177: "Failed to send queryid to %s"
+
+SQLSTATE: 08000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05178: "Failed to send queryid to %s before PREPARE command"
+
+SQLSTATE: 08000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05179: "failed to send %s command to node %u"
+
+SQLSTATE: 08000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05180: "Failed to COMMIT the transaction on nodes: %s."
+
+SQLSTATE: 08000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05181 - GAUSS-05190
+
+<br/>
+
+GAUSS-05181: "Can not find location info for relation oid: %u"
+
+SQLSTATE: 22004
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05182: "foreignPrivateList is NULL"
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05183: "Could not send user pl to CN of the compute pool: %s."
+
+SQLSTATE: 08000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05184: "Could not begin transaction on Datanodes."
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05185: "Failed to read response from Datanodes"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05186: "FATAL state of connection to datanode %u"
+
+SQLSTATE: 08000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05187: "No coordinator nodes defined in cluster"
+
+SQLSTATE: 42704
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05188: "Failed to send snapshot to %s"
+
+SQLSTATE: 08000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05189: "Failed to send command to %s"
+
+SQLSTATE: 08000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05190: "Could not begin transaction on Coordinator nodes"
+
+SQLSTATE: 08000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05191 - GAUSS-05200
+
+<br/>
+
+GAUSS-05191: "Failed to send command to coordinators"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05192: "Unexpected response from coordinator"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05193: "TUPDESC message has not been received before DATAROW message from %s"
+
+SQLSTATE: 08000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05194: "Failed to close Datanode statement"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05195: "Unsupport DML two phase commit under gtm free mode."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05196: "from remote cluster: %s"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05197: "10655"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05198: "Could not begin transaction on Datanode."
+
+SQLSTATE: 08000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05199: "Fetch statistics from myself is unexpected. Maybe switchover happened."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05200: "cooperation analysis: please update to the same version"
+
+SQLSTATE: 08P01
+
+Description: Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/53-GAUSS-05201-GAUSS-05300.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/53-GAUSS-05201-GAUSS-05300.md
new file mode 100644
index 0000000000000000000000000000000000000000..27153af170e0a8daa30f36e96ee83a84222cd2f0
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/53-GAUSS-05201-GAUSS-05300.md
@@ -0,0 +1,868 @@
+---
+title: GAUSS-05201- GAUSS-05300
+summary: GAUSS-05201- GAUSS-05300
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-05201- GAUSS-05300
+
+<br/>
+
+## GAUSS-05201- GAUSS-05210
+
+<br/>
+
+GAUSS-05201: "unrecognize LOCKMODE type."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05202: "invalid address for the compute pool: %s"
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05203: "invalid message format, please update to the same version"
+
+SQLSTATE: 08P01
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05204: "cooperation analysis: relation does not exist."
+
+SQLSTATE: 42704
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05205: "cooperation analysis: relation kind is not supported."
+
+SQLSTATE: 42809
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05206: "cooperation analysis: colomn information does not match."
+
+SQLSTATE: 42809
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05207: "cooperation analysis: unrecognized check result type: %d"
+
+SQLSTATE: 38000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05208: "cooperation analysis: invalid size of snapshot"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05209: "Failed to send queryid to %s before COMMIT command(1PC)"
+
+SQLSTATE: 08000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05210: "failed to notify node %u to commit"
+
+SQLSTATE: 08000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05211- GAUSS-05220
+
+<br/>
+
+GAUSS-05211: "failed to receice response from node %u after notify commit"
+
+SQLSTATE: 08000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05212: "failed to send commit csn to node %u"
+
+SQLSTATE: 08000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05213: "Failed to get valid node id from node definitions"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05214: "invalid node_list, coor_num:%d, datanode_num:%d"
+
+SQLSTATE: 22026
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05215: "Failed to send COMMIT/ROLLBACK on nodes: %s.Failed to COMMIT/ROLLBACK the transaction on nodes: %s."
+
+SQLSTATE: 08000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05216: "unsupported proc in single node mode."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05217: "pooler: Failed to create agent, number of agent reaches MaxAgentCount: %d"
+
+SQLSTATE: 53300
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05218: "agent cannot alloc memory."
+
+SQLSTATE: 53200
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05219: "pooler: connect failed, invaild argument."
+
+SQLSTATE: 08000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05220: "pooler: Failed to init agent, number of agent reaches MaxAgentCount: %d"
+
+SQLSTATE: 53300
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05221- GAUSS-05230
+
+<br/>
+
+GAUSS-05221: "pooler: could not find node of node[%d], oid[%u], needCreateArrayLen[%d], loopIndex[%d], i[%d], j[%d], isNull[%d]"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05222: "pooler: Failed to get_nodeInfo_from_matric: needCreateNodeArray is null."
+
+SQLSTATE: 01000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05223: "pooler: Failed to get_slave_datanode_oid: can't find slave nodes."
+
+SQLSTATE: 01000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05224: "invalid %s node number: %d, max_value is: %d."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05225: "pooler: The node(oid:%u) has no available slot, the number of slot in use reaches upper limit!"
+
+SQLSTATE: 53300
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05226: "pooler: Node(oid:%u) has been removed or altered"
+
+SQLSTATE: 01000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05227: "pooler: Communication failure, failed to send session commands or invalid incoming data, error count: %d."
+
+SQLSTATE: 08000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05228: "pooler: failed to create connections in parallel mode, due to failover, pending"
+
+SQLSTATE: 08006
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05229: "pooler: failed to create connections in parallel mode, Error Message: %s"
+
+SQLSTATE: 08006
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05230: "pooler: agent_release_connections: agent is null"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05231- GAUSS-05240
+
+<br/>
+
+GAUSS-05231: "malloc memory failed in dynamic loader."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05232: "latch already owned by %lu, my pid %lu"
+
+SQLSTATE: 58000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05233: "could not reattach to shared memory (key=%d): %m"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05234: "reattaching to shared memory returned unexpected address"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05235: "failed to release reserved memory region : error code %lu"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05236: "could not reattach to shared memory : error code %lu"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05237: "Init dictionary failed for invalid inputs"
+
+SQLSTATE: 58000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05238: "multiple FilePath parameters"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05239: "Text search for Danish is not supported!"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05240: "Text search for Dutch is not supported!"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05241- GAUSS-05250
+
+<br/>
+
+GAUSS-05241: "Text search for Finnish is not supported!"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05242: "Text search for French is not supported!"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05243: "Text search for German is not supported!"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05244: "Text search for Hungarian is not supported!"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05245: "Text search for Italian is not supported!"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05246: "Text search for Norwegian is not supported!"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05247: "Text search for Porter is not supported!"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05248: "Text search for Portuguese is not supported!"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05249: "Text search for Spanish is not supported!"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05250: "Text search for Swedish is not supported!"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05251- GAUSS-05260
+
+<br/>
+
+GAUSS-05251: "Text search for Romanian is not supported!"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05252: "Text search for Russian is not supported!"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05253: "Text search for Turkish is not supported!"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05254: "FilePath parameter should be with DictFile/AffFile/StopWords"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05255: "multiple Synonyms parameters"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05256: "multiple CaseSensitive parameters"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05257: "too many lexemes in thesaurus entry"
+
+SQLSTATE: F0000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05258: "Chinese is not supported by ASCII!"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05259: "pound parser only support UTF8/GBK/ASCII encoding"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05260: "Zhparser is not supported!"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05261- GAUSS-05270
+
+<br/>
+
+GAUSS-05261: "the parameter 'len' should not be negative."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05262: "the parameter 'len' is out of limit."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05263: "The name of internal dictionary file is too long"
+
+SQLSTATE: 42622
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05264: "FilePath must set an absolute path followed by 'file://'."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05265: "FilePath must set an absolute path followed by 'file:///'."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05266: "FilePath must set an obs path info followed by 'obs://'."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05267: "FilePath must start with 'file://' or 'obs://': %s"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05268: "The name of dictionary file is too long"
+
+SQLSTATE: 42622
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05269: "Dictionary file '%s' does not exist or cannot access the directory."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05270: "Dictionary File '%s' does not have READ permission."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05271- GAUSS-05280
+
+<br/>
+
+GAUSS-05271: "TEXT SEARCH is not yet supported."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05272: "Dictionary file name value '%s' contain no %c"
+
+SQLSTATE: 58000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05273: "Copy dictionary file '%s' failed: %m"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05274: "Send dictionary file to node fail: %m, command %s"
+
+SQLSTATE: 58000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05275: "Send dictionary file to backup fail: %m, command %s"
+
+SQLSTATE: 58000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05276: "Delete internal dictionary files failed for invalid inputs"
+
+SQLSTATE: 58000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05277: "unrecognized regis node type: %u"
+
+SQLSTATE: XX004
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05278: "affix flag '%s' is out of range"
+
+SQLSTATE: F0000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05279: "invalid affix flag '%s'"
+
+SQLSTATE: F0000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05280: "invalid character in affix flag '%s'"
+
+SQLSTATE: F0000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05281- GAUSS-05290
+
+<br/>
+
+GAUSS-05281: "unrecognized type of Conf->flagMode: %d"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05282: "invalid affix flag '%s' with 'long' flag value"
+
+SQLSTATE: F0000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05283: "unrecognized state in parse_ooaffentry: %d"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05284: "invalid affix alias '%s'"
+
+SQLSTATE: F0000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05285: "Ispell dictionary supports only 'default', 'long', and 'num' flag value"
+
+SQLSTATE: F0000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05286: "number of aliases exceeds specified number %d"
+
+SQLSTATE: F0000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05287: "affix file contains both old-style and new-style commands"
+
+SQLSTATE: F0000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05288: "invalid affix alias '%s', max affix value:%d"
+
+SQLSTATE: F0000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05289: "invalid len: %d"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05290: "localized string format value too long"
+
+SQLSTATE: 22008
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05291- GAUSS-05300
+
+<br/>
+
+GAUSS-05291: "The input NUMCacheEntry is invalid, which is Null."
+
+SQLSTATE: 22004
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05292: "input format of numeric shouldn't bigger than length of buffer."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05293: "invalid data."
+
+SQLSTATE: D0011
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05294: "invalid data for 'year = 0' ,value must be between -4712 and 9999, and not be 0"
+
+SQLSTATE: 22008
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05295: "value '%s' is out of range for type %s"
+
+SQLSTATE: 22003
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05296: "could not format inet value"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05297: "invalid input syntax for %s: '%s'"
+
+SQLSTATE: 22P02
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05298: "could not convert format string from UTF-8: error code %lu"
+
+SQLSTATE: 22021
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05299: "strftime(%s) failed: %m"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05300: "function '%s' does not exist xxxx"
+
+SQLSTATE: 42883
+
+Description: Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/54-GAUSS-05301-GAUSS-05400.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/54-GAUSS-05301-GAUSS-05400.md
new file mode 100644
index 0000000000000000000000000000000000000000..c6922d07281dd879e902f1137979b1d048ee0796
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/54-GAUSS-05301-GAUSS-05400.md
@@ -0,0 +1,860 @@
+---
+title: GAUSS-05301 - GAUSS-05400
+summary: GAUSS-05301 - GAUSS-05400
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-05301 - GAUSS-05400
+
+<br/>
+
+## GAUSS-05301 - GAUSS-05310
+
+<br/>
+
+GAUSS-05301: "more than one function named '%s', %d functions are found"
+
+SQLSTATE: 42725
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05302: "SPI_connect failed: %s"
+
+SQLSTATE: SP001
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05303: "null value not allowed"
+
+SQLSTATE: 22004
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05304: "The length should not be nagative: %d.\n"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05305: "cache lookup failed for attribute %d of relation %u, in node [%s]"
+
+SQLSTATE: 29P01
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05306: "cache lookup failed for type oid %d"
+
+SQLSTATE: 29P01
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05307: "Multi-column statistic needs at least two columns."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05308: "Multi-column statistic supports at most %d columns."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05309: "Replicate foreign table is not supported by extended statistic."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05310: "System catalog is not supported by extended statistic."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05311 - GAUSS-05320
+
+<br/>
+
+GAUSS-05311: "MCV column numbers are not matched."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05312: "ordered_set_startup function context info is null"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05313: "ordered-set aggregate support function called for non-ordered-set aggregate"
+
+SQLSTATE: 29000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05314: "ordered-set aggregate support function does not support multiple aggregated columns"
+
+SQLSTATE: 42P25
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05315: "ordered-set aggregate called in non-aggregate context"
+
+SQLSTATE: 29000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05316: "wrong interpolate type"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05317: "percentile cannot be NULL"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05318: "percentile value %g is not between 0 and 1"
+
+SQLSTATE: 22003
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05319: "missing row in percentile_cont"
+
+SQLSTATE: P0002
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05320: "interval_mul result month: %lf, day: %lf overflow"
+
+SQLSTATE: 22015
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05321 - GAUSS-05330
+
+<br/>
+
+GAUSS-05321: "the input timestamp must not be null."
+
+SQLSTATE: 22004
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05322: "timestamp out of range, negative Julian days is not supported"
+
+SQLSTATE: 22008
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05323: "The result of timestampdiff out of range."
+
+SQLSTATE: 22008
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05324: "the format is not correct"
+
+SQLSTATE: 0A000
+
+Description: The input data is empty or the format is incorrect.
+
+Solution: Check the input data.
+
+GAUSS-05325: "Invalid day format: \'%s\' of the week"
+
+SQLSTATE: 22008
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05326: "Week day out of range, the range is %d … %d"
+
+SQLSTATE: 22008
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05327: "timestamp out of range."
+
+SQLSTATE: 22008
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05328: "Parameters of complex_array_in are invalid."
+
+SQLSTATE: 00000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05329: "array size cannot be negative."
+
+SQLSTATE: 22003
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05330: "null pointer for nullbitmap."
+
+SQLSTATE: 22004
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05331 - GAUSS-05340
+
+<br/>
+
+GAUSS-05331: "input zero npts for path_encode is invalid"
+
+SQLSTATE: 22012
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05332: "file length cannot be divisibed by 8k: file %s, offset %ld, nbytes %ld"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05333: "cheksum failed in file '%s'(computed: %d, recorded: %d)"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05334: "must be initial account to read files"
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05335: "must be initial account to get file information"
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05336: "must be initial account to get directory listings"
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05337: "start value cannot be NaN"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05338: "stop value cannot be NaN"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05339: "step size cannot be NaN"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05340: "there should be at least one non-zero digit."
+
+SQLSTATE: 42P24
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05341 - GAUSS-05350
+
+<br/>
+
+GAUSS-05341: "cannot convert infinity to numeric"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05342: "caller passed the error typcache entry"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05343: "kill backend is prohibited during online expansion."
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05344: "must be system admin to cancel invalid queries running in all server processes"
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05345: "the user have no right to change cgroup for session [%lu]!"
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05346: "must be superuser account to recover node for wlm"
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05347: "must be superuser account to clean node for wlm"
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05348: "permission denied to get role name"
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05349: "Unexpected null value for the rel of vardata"
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05350: "the right operand should not be null in gincost_opexpr"
+
+SQLSTATE: OP002
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05351 - GAUSS-05360
+
+<br/>
+
+GAUSS-05351: "Unexpected null value for the plan"
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05352: "Unexpected null value for the path"
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05353: "Unexpected null value for the list record's head"
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05354: "the timeout_threshold(%d) could not less than 0"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05355: "the timeout_threshold(%d) could not larger than 2147483"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05356: "unsupported view in single node mode."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05357: "permission denied to get system environment"
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05358: "only system/monitor admin can query sql info view"
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05359: "The function 'pg_wlm_get_session_info' is not supported now!"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05360: "The function 'gs_wlm_get_user_session_info' is not supported now!"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05361 - GAUSS-05370
+
+<br/>
+
+GAUSS-05361: "Only system admin user can use this function"
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05362: "invalid thread id %ld for it is 0 or postmaster pid."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05363: "invalid size of cnt"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05364: "failed to get the parameter of resource pool %s!"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05365: "cgroup is not initialized or group name %s is invalid!"
+
+SQLSTATE: 42P26
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05366: "%s logical cluster doesn't exist!"
+
+SQLSTATE: 42704
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05367: "class group %s doesn't exist!"
+
+SQLSTATE: 42704
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05368: "workload group %s doesn't exist!"
+
+SQLSTATE: 42704
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05369: "invalid name of resource pool: NULL or ""
+
+SQLSTATE: 42602
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05370: "parent group '%s' doesn't have exception information!"
+
+SQLSTATE: 42704
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05371 - GAUSS-05380
+
+<br/>
+
+GAUSS-05371: "cgroup is not initialized!"
+
+SQLSTATE: 42704
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05372: "invalid name of logical cluster: NULL or ""
+
+SQLSTATE: 42602
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05373: "Fail to find central coordinator"
+
+SQLSTATE: 29P01
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05374: "Only superuser can call function pg_autovac_status."
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05375: "out of range."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05376: "must be system admin to view the global information"
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05377: "permission denied."
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05378: "must be system admin to reset bad block statistics counters"
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05379: "unknow func name"
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05380: "cannot accpect arrays with dimensions out of range"
+
+SQLSTATE: 2202E
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05381 - GAUSS-05390
+
+<br/>
+
+GAUSS-05381: "unsupported function or view in %s mode."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05382: "invalid null pointer input for text_to_cstring()"
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05383: "blob length: %d ,out of memory"
+
+SQLSTATE: 53200
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05384: "blob/bytea size:%d, only can recevie blob/bytea less than 500M "
+
+SQLSTATE: 53200
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05385: "unsupport type %s"
+
+SQLSTATE: XX004
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05386: "could not determine data type of concat() input to variadic"
+
+SQLSTATE: 42P38
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05387: "could not determine data type of format() input"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05388: "number is out of range"
+
+SQLSTATE: 22003
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05389: "format specifies argument 0, but arguments are numbered from 1"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05390: "width argument position must be ended by '$'"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05391 - GAUSS-05400
+
+<br/>
+
+GAUSS-05391: "ACL string cannot be NULL."
+
+SQLSTATE: 22P02
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05392: "ACL item cannot be NULL."
+
+SQLSTATE: 22P02
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05394: "hash num out of the int max, [%ld]"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05395: "input julian date is overflow"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05396: "the interval value is overflow, it can not perform as oracle interval-style"
+
+SQLSTATE: 22003
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05397: "could not stat bucket dir '%s': %m"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05398: "rel path is not a dir '%s': %m"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05399: "could not stat file under bucket dir '%s': %m"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05400: "expected 1 row, actual %u row"
+
+SQLSTATE: YY015
+
+Description: Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/55-GAUSS-05401-GAUSS-05500.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/55-GAUSS-05401-GAUSS-05500.md
new file mode 100644
index 0000000000000000000000000000000000000000..67bbb1d91fa626110392faf37ae1f579cc931336
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/55-GAUSS-05401-GAUSS-05500.md
@@ -0,0 +1,860 @@
+---
+title: GAUSS-05401 - GAUSS-05500
+summary: GAUSS-05401 - GAUSS-05500
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-05401 - GAUSS-05500
+
+<br/>
+
+## GAUSS-05401 - GAUSS-05410
+
+<br/>
+
+GAUSS-05401: "must be system admin to call gs_get_max_dbsize_name."
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05402: "Please check if another schema is in redistribution in the same database."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05403: "system schema '%s' does not support transfer"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05404: "Only system admin can lock the cluster."
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05405: "temp table is not supported in online expansion"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05406: "Only system admin can use the function on coordinator"
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05407: "Can not run the function during initdb or upgrade"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05408: "Can not get temporary tables defination."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05409: "cache lookup failed for table %d."
+
+SQLSTATE: 29P01
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05410: "Not a ordinary table or foreign table."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05411 - GAUSS-05420
+
+<br/>
+
+GAUSS-05411: "Invalid attribute relation option."
+
+SQLSTATE: 02002
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05412: "recover failed could not write to relation mapping file '%s': %m"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05413: "recover failed could not fsync relation mapping file '%s': %m"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05414: "recover failed could not close relation mapping file '%s': %m"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05415: "relmap_redo: wrong size %d in relmap update record"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05416: "Invalid tablespace relation option."
+
+SQLSTATE: 02002
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05417: "unexpected duplicate for tablespace %u, relfilenode %u"
+
+SQLSTATE: LL002
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05418: "corrupted hashtable"
+
+SQLSTATE: LL002
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05419: "namespace %s was invalid after retry"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05420: "relation %s was invalid after retry"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05421 - GAUSS-05430
+
+<br/>
+
+GAUSS-05421: "Table object with oid %u does not exists (has been dropped)"
+
+SQLSTATE: 42P01
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05422: "cache lookup failed for cfg %u"
+
+SQLSTATE: 29P01
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05423: "cache lookup failed for enumlabelid %u"
+
+SQLSTATE: 29P01
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05424: "null group_members for tuple %u"
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05425: "unrecognized distribution key found in source like table"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05426: "Can't get nodeoid for relation %s"
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05427: "There is no installation group for system catalogs!"
+
+SQLSTATE: 55000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05428: "can not open pg_resource_pool"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05429: "Catalog attribute %d for relation '%s' has been updated concurrently"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05430: "Catalog is missing %d attribute(s) for relid %u"
+
+SQLSTATE: 02000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05431 - GAUSS-05440
+
+<br/>
+
+GAUSS-05431: "bucket key column's number is not a 1-D smallint array"
+
+SQLSTATE: 2202E
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05432: "could not find pg_class entry for %u"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05433: "Invalid Oid while setting new relfilenode for tag table."
+
+SQLSTATE: 42602
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05434: "pg_class entry for relid %u vanished during RelationGetIndexList"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05435: "could not open parent relation with OID %u"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05436: "unknown attrKind %u"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05437: "global plan can't be rebuild in share status stmt name %s :global session id :%lu session_id:%lu"
+
+SQLSTATE: 26000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05438: "could not open index with OID %u"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05439: "SearchCatCacheCheck:current transaction is aborted, commands ignored until end of transaction block"
+
+SQLSTATE: 25P02
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05440: "pg_attribute does not have syscache with id %d"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05441 - GAUSS-05450
+
+<br/>
+
+GAUSS-05441: "pg_localtime must not be null!"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05442: "parse error on statement %s."
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05443: "parse error on query %s."
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05444: "could not load library '%s', get error report failed"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05445: "function returned NULL"
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05446: "datum is NULL"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05447: "Division by zero when calculate element numbers!"
+
+SQLSTATE: 22012
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05448: "invalid path:%s"
+
+SQLSTATE: 58P03
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05449: "Current user id is invalid. Please try later."
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05450: "Abnormal process. UserOid has been reseted. Current userOid[%u], reset username is %s."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05451 - GAUSS-05460
+
+<br/>
+
+GAUSS-05451: "bogus lock file '%s',could not unlink it : %m"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05452: "bogus data in lock file '%s': '%s', please kill the instance process, than remove the damaged lock file"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05453: "Unable to get architecture to check ARM LSE!"
+
+SQLSTATE: 58P03
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05454: "Unable to open /proc/cpuinfo to check ARM LSE!"
+
+SQLSTATE: 58P03
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05455: "Normal user is not allowed to use HA channel!"
+
+SQLSTATE: 28000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05456: "Only applications can connect remotely."
+
+SQLSTATE: 28000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05457: "Forbid remote connection via internal maintenance tools."
+
+SQLSTATE: 28000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05458: "Inner maintenance tools only for the initial user."
+
+SQLSTATE: D0011
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05459: "Only allow initial user or operator admin to use operation tool gs_roach."
+
+SQLSTATE: D0011
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05460: "Already too many clients, active/non-active/reserved: %d/%d/%d."
+
+SQLSTATE: 53300
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05461 - GAUSS-05470
+
+<br/>
+
+GAUSS-05461: "pg_server_to_any returns null."
+
+SQLSTATE: 58000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05462: "Row Level Security is not supported."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05463: "'%s' is not a normal table"
+
+SQLSTATE: 42809
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05464: "do not support row level security policy on temp table '%s'"
+
+SQLSTATE: 42809
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05465: "do not support row level security policy on dfs table '%s'"
+
+SQLSTATE: 42809
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05466: "The text entered contains illegal characters!"
+
+SQLSTATE: 22P05
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05467: "failed to initialize %s to " INT64_FORMAT
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05468: "Incorrect backend environment variable $PGDATA"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05469: "must be initial account to examine '%s'"
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05470: "Current degree of parallelism can only be set within [-64,64]"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05471 - GAUSS-05480
+
+<br/>
+
+GAUSS-05472: "permission denied to set role '%s'"
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05473: "first stage encryption password failed"
+
+SQLSTATE: 28P01
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05474: "second stage encryption password failed"
+
+SQLSTATE: 28P01
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05475: "Invalid password stored"
+
+SQLSTATE: 28P01
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05476: "replication_type is not allowed set 1 in Current Version. Set to default (0)."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05477: "Length of file or line is too long."
+
+SQLSTATE: F0000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05478: "Failed to initilize the memory(%uM) of search server, maybe it exceed the half of maxChunksPerProcess(%dM)."
+
+SQLSTATE: 53200
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05479: "invalid operation on memory context"
+
+SQLSTATE: D0011
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05480: "We can not set memory context parent with different session number"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05481 - GAUSS-05490
+
+<br/>
+
+GAUSS-05481: "%s Memory Context could not find block containing block"
+
+SQLSTATE: OP002
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05482: "%s Memory Context could not find block"
+
+SQLSTATE: OP002
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05483: "portal is NULL"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05484: "Accessing null portal entry found in portal hash table."
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05485: "The block was freed before this time."
+
+SQLSTATE: OP002
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05486: "The memory use was overflow."
+
+SQLSTATE: OP002
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05487: "detected write past chunk end in %s"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05488: "Error on %s Memory Context happened when executing memcpy_s:%d"
+
+SQLSTATE: OP001
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05489: "failed to initialize rwlock in AllocSetContextCreate."
+
+SQLSTATE: D0014
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05490: "could not find block"
+
+SQLSTATE: OP001
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05491 - GAUSS-05500
+
+<br/>
+
+GAUSS-05491: "data cache block %d is not owned by resource owner %s"
+
+SQLSTATE: 01007
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05492: "meta cache block %d is not owned by resource owner %s"
+
+SQLSTATE: 01007
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05493: "fakepart reference %u is not owned by resource owner %s"
+
+SQLSTATE: 01007
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05494: "partition map reference is not owned by resource owner %s"
+
+SQLSTATE: 01007
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05495: "Failed to obtain address of the block!"
+
+SQLSTATE: 29P02
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05496: "could not write to row store temp file: %m"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05497: "could not read from row store temp file: %m"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05498: "row store : dn node id(%d) exceeds max bank num(%d)"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05499: "row store : cn node id(%d) exceeds max bank num(%d)"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05500: "failed to get cn/dn node id for OID %u"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/56-GAUSS-05501-GAUSS-05600.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/56-GAUSS-05501-GAUSS-05600.md
new file mode 100644
index 0000000000000000000000000000000000000000..45937baf5f2456bfa3d71092c75d6c52590fa9f6
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/56-GAUSS-05501-GAUSS-05600.md
@@ -0,0 +1,868 @@
+---
+title: GAUSS-05501 - GAUSS-05600
+summary: GAUSS-05501 - GAUSS-05600
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-05501 - GAUSS-05600
+
+<br/>
+
+## GAUSS-05501 - GAUSS-05510
+
+<br/>
+
+GAUSS-05501: "row store : cannot write cell into either memory or disk"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05502: "row store : expect data from row store, but no data read"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05503: "row store : expect to read node_id = %d but got %d"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05504: "could not seek store temp file: %m"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05505: "row store : expect to read from file but no file opened"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05506: "row store : cannot determine msg len when %s"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05507: "row store : msg and msglen mismatch when %s"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05508: "row store : LZ4_compress_default failed trying to compress the data"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05509: "row store : unexpected original len of msg when decompressing data"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05510: "row store : unexpected compressed len when decompressing data"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05511 - GAUSS-05520
+
+<br/>
+
+GAUSS-05511: "insufficient memory allowed for sort, allowed memory is %ld byte, available memory is %ld byte"
+
+SQLSTATE: 53000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05512: "ActiveTapes should be larger than zero."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05513: "invalid sortkey value: attrNum = %d, sortOperators oid = %d in position of %d."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05514: "Backward skip tupples is not support yet."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05515: "Skip n tuples must bigger than 0."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05516: "retrieved tuples over bounded size"
+
+SQLSTATE: 42P25
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05517: "Cannot found valid cid in UsedComboCids. UsedComboCids: %d, tuple cid: %u."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05518: "snapshot is not active"
+
+SQLSTATE: 29000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05519: "could not resolve cmin/cmax of catalog tuple"
+
+SQLSTATE: P0002
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05520: "could not resolve combocid to cmax"
+
+SQLSTATE: P0002
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05521 - GAUSS-05530
+
+<br/>
+
+GAUSS-05521: "Built-in functions should not be added into pg_proc"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05522: "(s|libcomm_cpu_rate init)\tFailed to malloc g_libcomm_used_rate."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05523: "(r|receivers init)\tFailed to malloc g_r_node_sock[%d]."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05524: "(r|receivers init)\tFailed to malloc g_receivers[%d]."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05525: "(s|sender init)\tFailed to malloc g_s_node_sock[%d]."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05526: "(s|sender init)\tFailed to malloc g_delay_info[%d]."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05527: "(s|sender init)\tFailed to malloc g_senders[%d]."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05528: "Failed to build mailbox[%d]."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05529: "communicator palloc CommReceiverPIDS mempry failed"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05530: "(r|cmailbox init)\tFailed to init cmailbox."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05531 - GAUSS-05540
+
+<br/>
+
+GAUSS-05531: "(s|pmailbox init)\tFailed to init pmailbox."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05532: "(s|pmailbox init)\tFailed to init g_usable_streamid."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05533: "(s|sender init)\tFailed to init sender[%d] for %s."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05534: "Failed to read response from Local Stream Node, Detail: Node %s, Plan Node ID %u, SMP ID %d"
+
+SQLSTATE: XX003
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05535: "(s|flow ctrl init)\tFailed to init poller list:%s."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05536: "(r|receiver init)\tFailed to init receiver listen socket:%s."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05537: "(r|receiver init)\tFailed to init receiver semaphore:%s."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05538: "(r|flow ctrl init)\tFailed to do listen:%s."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05539: "(r|flow ctrl init)\tFailed to init poller list:%s."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05540: "(s|flow ctrl)\tFailed to do epoll wait[%d] with errno[%d]:%s."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05541 - GAUSS-05550
+
+<br/>
+
+GAUSS-05541: "(r|flow ctrl)\tFailed to do epoll wait[%d] with errno[%d]:%s."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05542: "(r|recv loop)\tFailed to do epoll wait[%d] with errno[%d]:%s."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05543: "(r|receiver init)\tFailed to init thd_receiver_id:%s."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05544: "(r|receiver init)\tFailed to init poller list:%s."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05545: "(r|receiver init)\tFailed to add libcomm listen socket[%d] and version[%d] to poller list."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05546: "(r|receiver init)\tLibcomm init receiver threads fail, wait(10s) timeout, please check the machine resource usage, and try again later."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05547: "Column %d receive unexpected C_TYPE %d"
+
+SQLSTATE: 42804
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05548: "unexpected null string in column %d"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05549: "query in function exec_on_extension returns too many columns"
+
+SQLSTATE: 54011
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05550: "SQL_ERROR: unexpected data while converting it into bool."
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05551 - GAUSS-05560
+
+<br/>
+
+GAUSS-05551: "libodbc.so.1 or libodbc.so.2 not found, which is needed to run the Extension Connector."
+
+SQLSTATE: 58P01
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05552: "Can NOT find function '%s()' in libodbc.so.1 or libodbc.so.2."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05553: "unsupport data type: [%s] found in record definition."
+
+SQLSTATE: 42804
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05554: "unsupport data type found, type oid: %d"
+
+SQLSTATE: 42804
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05555: "function returning record called in context that cannot accept type record"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05556: "key '%s' is given more than once!"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05557: "missing data source to be connected for first parameter."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05558: "data source '%s' does not exist"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05559: "missing statement to be executed for second parameter."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05560: "for ODBC driver, we need a DSN!"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05561 - GAUSS-05570
+
+<br/>
+
+GAUSS-05561: "Initialize ODBC Connector failed due to insufficient memory."
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05562: "Invalid string length"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05563: "SQL can not be null!"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05564: "Extension Connector is not supported in current version."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05565: "must be system admin to use this function"
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05566: "Un-support feature in MySQL compatibility"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05567: "Failed to found one dummy server."
+
+SQLSTATE: 22004
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05568: "Only one dummy server is allowed to exist in one database."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05569: "build global Dummy servder cache hash table failed"
+
+SQLSTATE: 42704
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05570: "could not initialize Dummny server hash table"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05571 - GAUSS-05580
+
+<br/>
+
+GAUSS-05571: "foreign table server is invalid."
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05572: "cannot find foreign server with given name %s ."
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05573: "totalrows is invalid"
+
+SQLSTATE: HV000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05574: "Failed to get obskey from options of DWS."
+
+SQLSTATE: HV000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05575: "No 'format' option provided."
+
+SQLSTATE: HV000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05576: "Invalid location value for the foreign table."
+
+SQLSTATE: HV000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05577: "Failed to get obskey from cipher file"
+
+SQLSTATE: 22004
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05578: "Incorrect backend environment variable $GAUSSHOME"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05579: "Failed to open file %s, errno = %d, reason = %s."
+
+SQLSTATE: HV000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05580: "The %s file is empty."
+
+SQLSTATE: HV000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05581 - GAUSS-05590
+
+<br/>
+
+GAUSS-05581: "Failed to read file %s."
+
+SQLSTATE: HV000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05582: "Failed to parse %s file: %s."
+
+SQLSTATE: HV000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05583: "Failed to parse %s file: unkonwn error."
+
+SQLSTATE: HV000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05584: "Must exist array format in the %s json file."
+
+SQLSTATE: HV000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05585: "No such region name: %s in %s file."
+
+SQLSTATE: HV000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05586: "Invalid percentile syntax"
+
+SQLSTATE: XX006
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05587: "Too many percentile values"
+
+SQLSTATE: XX006
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05588: "[UniqueSQL] check unique sql array slot index!"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05589: "[UniqueSQL] invalid 'r' message. node: %s"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05590: "[UniqueSQL] palloc failed for results!"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05591 - GAUSS-05600
+
+<br/>
+
+GAUSS-05591: "[UniqueSQL] during get stat from remote, failed to send/recv data!"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05592: "[UniqueSQL] palloc0 error when querying unique sql stat!"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05593: "only system/monitor admin can query unique sql view"
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05594: "[UniqueSQL] recv invalid sql ids count"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05595: "out of memory during allocating list element."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05596: "Cleanup global unique sql info only support on CN nodes."
+
+SQLSTATE: 01000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05597: "First parameter is wrong. USAGE: [GLOBAL/LOCAL],[ALL/BY_USERID/BY_CNID],[VALUE]"
+
+SQLSTATE: 01000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05598: "Second parameter is wrong. USAGE:[GLOBAL/LOCAL],[ALL/BY_USERID/BY_CNID],[VALUE]"
+
+SQLSTATE: 01000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05599: "only system/monitor admin can reset unique sql"
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05600: "[user] cannot alloc memory for user stat"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/57-GAUSS-05601-GAUSS-05700.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/57-GAUSS-05601-GAUSS-05700.md
new file mode 100644
index 0000000000000000000000000000000000000000..c5d8dec4e464673226b2e5e0dd733f2c108bd7b6
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/57-GAUSS-05601-GAUSS-05700.md
@@ -0,0 +1,868 @@
+---
+title: GAUSS-05601 - GAUSS-05700
+summary: GAUSS-05601 - GAUSS-05700
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-05601 - GAUSS-05700
+
+<br/>
+
+## GAUSS-05601 - GAUSS-05610
+
+<br/>
+
+GAUSS-05601: "only system/monitor admin can get user statistics info"
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05602: "report params is null"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05603: "report type can not = %s"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05604: "report scope can not = %s"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05605: "dashTitle or tableTitle is null"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05606: "out of the Contents"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05607: "no available data for report"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05608: "dashboard title is not assigned"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05609: "table title is not assigned"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05610: "query is null"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05611 - GAUSS-05620
+
+<br/>
+
+GAUSS-05611: "list is null, can not free"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05612: "table is not null when overturn table"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05613: "no this type of report_scope"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05614: "calc trx diff count failed!"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05615: "set the snapshotid"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05616: "snapshot id is invalid"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05617: "Instance reset time is different"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05618: "invalid report type, should be %s or %s or %s"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05619: "invalid report scope, should be %s or %s"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05620: "invalid report node name."
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05621 - GAUSS-05630
+
+<br/>
+
+GAUSS-05621: "The 3rd argument 'report_type' and 4th argument 'report_scope' should not be null"
+
+SQLSTATE: 22004
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05622: "Superuser privilege is neended to generate report"
+
+SQLSTATE: OP001
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05623: "out of memory of current node."
+
+SQLSTATE: 53200
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05624: "could not establish connection"
+
+SQLSTATE: 08001
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05625: "Superuser privilege is need to operate wdr_xdb_query"
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05626: "wrong number of arguments"
+
+SQLSTATE: 54023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05627: "connection '%s' not available"
+
+SQLSTATE: 08003
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05628: "could not send query: %s"
+
+SQLSTATE: 02002
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05629: "failed to set single-row mode for dblink query"
+
+SQLSTATE: 02002
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05630: "remote query result rowtype does not match the specified FROM clause rowtype"
+
+SQLSTATE: 42804
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05631 - GAUSS-05640
+
+<br/>
+
+GAUSS-05631: "only system admin can kill snapshot thread"
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05632: "kill snapshot thread failed %s"
+
+SQLSTATE: OP001
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05633: "kill snapshot thread failed, exceeds MAX_RETRY_COUNT(%d)"
+
+SQLSTATE: OP001
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05634: "set lockwait_timeout failed: %s"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05635: "Superuser privilege is need to operate snapshot"
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05636: "WDR snapshot request can not be accepted, please retry later"
+
+SQLSTATE: OP001
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05637: "Cannot respond to WDR snapshot request"
+
+SQLSTATE: OP001
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05638: "query is NULL"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05639: "this query can not get datum values"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05640: "create sequence failed"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05641 - GAUSS-05650
+
+<br/>
+
+GAUSS-05641: "update snapshot end time stamp filled"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05642: "wdr_snapshot_interval is 0"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05643: "invalid query: %s"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05644: "clean table of snap_%s is failed"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05645: "WDR snapshot analyze table:%s not exist"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05646: "insert into tables_snap_timestamp start time stamp is failed"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05647: "insert into snap_%s is failed"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05648: "update tables_snap_timestamp end time stamp is failed"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05649: "clean snapshot id %lu is failed in snapshot table"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05650: "clean snapshot id %lu is failed in tables_snap_timestamp table"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05651 - GAUSS-05660
+
+<br/>
+
+GAUSS-05651: "query or the tablename is null when snapshot create stat table"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05652: "can not create snapshot stat table"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05653: "create WDR snapshot data table failed"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05654: "spilt str can not null"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05655: "insert into tables_snap_timestamp start time stamp failed"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05656: "create index failed"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05657: "analyze table, connection failed: %s"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05658: "snapshot thread SPI_connect failed: %s"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05659: "The length of str: %d is less than %d"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05660: "Array length %d or %d is less than %d"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+### GAUSS-05661 - GAUSS-05670
+
+<br/>
+
+GAUSS-05661: "[CapView] OOM in capture view"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05662: "[CapView] could not write to view perf file: %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05663: "[CapView] could not ftell json file :%m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05664: "[CapView] pls check database name and view name!"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05665: "[CapView] view name is too long!"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05666: "[CapView] view name can not contain '('!"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05667: "[CapView] only system admin can capure view"
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05668: "[CapView] in capture_view_to_json proc, view_name or is_all_db can not by null"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05669: "[CapView] in capture_view_to_json proc, is_all_db can only be 0 or 1"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05670: "[CapView] SPI_connect failed: %s"
+
+SQLSTATE: SP001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05671 - GAUSS-05680
+
+<br/>
+
+GAUSS-05671: "[CapView] json file can not by NULL"
+
+SQLSTATE: XX005
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05672: "[CapView] calc realpath failed"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05673: "[CapView] could not open log file '%s': %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05674: "[CapView] could not chmod view json file '%s': %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05675: "[CapView] calc localtime failed"
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05676: "[CapView] invalid query"
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05677: "The encryption key can not be empty!"
+
+SQLSTATE: 39000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05678: "The encryption key must be shorter than 16 bytes!"
+
+SQLSTATE: 39000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05679: "The decryption key can not be empty!"
+
+SQLSTATE: 39000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05680: "Decode the cipher text failed or the ciphertext is too short!"
+
+SQLSTATE: 39000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05681 - GAUSS-05690
+
+<br/>
+
+GAUSS-05681: "Encrypt OBS AK/SK failed."
+
+SQLSTATE: 39000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05682: "Encrypt OBS AK/SK internal error"
+
+SQLSTATE: 39000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05683: "Decrypt OBS AK/SK failed."
+
+SQLSTATE: 39000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05684: "Decrypt OBS AK/SK internal error."
+
+SQLSTATE: 39000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05685: "Failed to get OBS certificate file."
+
+SQLSTATE: 39000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05686: "No key file obsserver.key.cipher"
+
+SQLSTATE: 58P01
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05687: "aes128EncryptSpeedFailed!"
+
+SQLSTATE: 39000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05688: "Failed to get EC certificate file: get env GAUSSHOME failed."
+
+SQLSTATE: 39000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05689: "No key file datasource.key.cipher"
+
+SQLSTATE: 58P01
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05690: "Encrypt EC internal error: dest cipher length is too short."
+
+SQLSTATE: 39000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05691 - GAUSS-05700
+
+<br/>
+
+GAUSS-05691: "Decrypt EC internal error: dest plain length is too short."
+
+SQLSTATE: 39000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05692: "it's an encrypted cluster, but parameter not initialized!"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05693: "encrypt failed, return code is %u!"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05694: "encrypt failed after retry three times, error code is %u!"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05695: "decrypt failed, return code is %u!"
+
+SQLSTATE: 22026
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05696: "decrypt failed after retry three times, error code is %u!"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05697: "transparent_encrypt_kms_url and transparent_encrypt_kms_region should not be empty when transparent encryption enabled.\n"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05698: "Failed to get ak/sk for transparent encryption.\n"
+
+SQLSTATE: 39000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05699: "Failed to fork subprocess to get DEK for transparent encryption. Failure command is: [%s]\n"
+
+SQLSTATE: 39000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05700: "Failed to get DEK for transparent encryption. Failure command is [%s], error message is [%s]\n"
+
+SQLSTATE: 39000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/58-GAUSS-05701-GAUSS-05800.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/58-GAUSS-05701-GAUSS-05800.md
new file mode 100644
index 0000000000000000000000000000000000000000..bd4329868e0dafe9486ca4299915ef1c619ba200
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/58-GAUSS-05701-GAUSS-05800.md
@@ -0,0 +1,868 @@
+---
+title: GAUSS-05701 - GAUSS-05800
+summary: GAUSS-05701 - GAUSS-05800
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-05701 - GAUSS-05800
+
+<br/>
+
+## GAUSS-05701 - GAUSS-05710
+
+<br/>
+
+GAUSS-05701: "Failed to get decode DEK for transparent encryption. Failure content is [%s].\n"
+
+SQLSTATE: 39000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05702: "Decode transparent_encrypted_string failed, please check it.\n"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05703: "Decrypt transparent_encrypted_string failed, please check it!\n"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05704: "Out of memory while getting transparent encryption iv.\n"
+
+SQLSTATE: 53200
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05705: "TDE is not supported."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05706: "The data type %u is not supported for bloom filter curently."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05707: "failed to init sigpool mutex: %m."
+
+SQLSTATE: 55P03
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05708: "failed to lock sigpool mutex: %m."
+
+SQLSTATE: 55P03
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05709: "failed to unlock sigpool mutex: %m."
+
+SQLSTATE: 55P03
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05710: "log2m = %d is out of range, it should be in range %d to %d"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05711 - GAUSS-05720
+
+<br/>
+
+GAUSS-05711: "regwidth = %d is out of range, it should be in range %d to %d"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05712: "expthresh = %ld is out of range, it should be in range %d to %d"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05713: "sparseon should be %d or %d"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05714: "no such parameters of input"
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05715: "hll_add_trans_normal outside transition context"
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05716: "hll_union_collect_compressed outside transition context"
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05717: "hll_union_trans_normal outside transition context"
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05718: "hll_union_trans_compressed context"
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05719: "Fail to build partitionmap for realtion'%s'."
+
+SQLSTATE: 42P23
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05720: "Can not run transaction to remote nodes during recovery."
+
+SQLSTATE: 25009
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05721 - GAUSS-05730
+
+<br/>
+
+GAUSS-05721: "could not find tuple with partition OID %u."
+
+SQLSTATE: 42704
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05722: "Fail to build partitionmap for partitioned table '%s'."
+
+SQLSTATE: 42P23
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05723: "Fail to build partitionmap for partitioned table '%u'."
+
+SQLSTATE: 42P23
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05724: "Failed to set the default password for private key File: '%s'"
+
+SQLSTATE: OP002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05725: "too many writing times(>%d):%d, write %d, errno %d"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05726: "%d: write %d, errno %d, detail:%s"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05727: "unrecognized error:%d, write %d, errno %d"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05728: "failed to initialize SSL library, detail:%s"
+
+SQLSTATE: OP002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05729: "failed to create the SSL context, detail:%s"
+
+SQLSTATE: OP002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05730: "invlid cert file directory"
+
+SQLSTATE: OP002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05731 - GAUSS-05740
+
+<br/>
+
+GAUSS-05731: "failed to load the root CA Certificate %s(%s)"
+
+SQLSTATE: OP002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05732: "failed to certificate the %s(%s) file in SSL context"
+
+SQLSTATE: OP002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05733: "stat cipher file '%s' failed, detail: %s"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05734: "stat rand file '%s' failed, detail: %s"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05735: "cipher file '%s' has group or world access;permissions should be u=rw (0600) or less with Error: %s"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05736: "rand file '%s' has group or world access;permissions should be u=rw (0600) or less with Error: %s"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05737: "Failed to create the SSL."
+
+SQLSTATE: OP002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05738: "Failed to set the socket(%d) for SSL"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05739: "Failed to certificate file '%s' in SSL object"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05740: "Failed to check the private key File."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05741 - GAUSS-05750
+
+<br/>
+
+GAUSS-05741: "SSL connect failed, code %d"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05742: "gz_open failed: errno %d"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05743: "gz_read failed: offset %ld, errno %d, returned size %d"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05744: "vfd_file_open failed: vfd(-1), errno %d, file '%s' "
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05745: "vfd_file_open2 failed: vfd(-1), errno %d, file '%s' "
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05746: "vfd_file_read2 failed: errno %d, returned size %d"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05747: "vfd_file_write2 failed: errno %d, returned size %d"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05748: "unzOpen2_64 failed: file '%s'"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05749: "unzGetGlobalInfo64 failed: file '%s', err %d"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05750: "unzOpenCurrentFile failed: file '%s', err %d"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05751 - GAUSS-05760
+
+<br/>
+
+GAUSS-05751: "unzCloseCurrentFile failed: err %d"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05752: "unzReadCurrentFile failed: err %d"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05753: "unzGoToNextFile failed: err %d"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05754: "unzOpenCurrentFile failed: err %d"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05755: "invalid compute pool message subtype %d"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05756: "only coordinator could receive compute pool message type 'I'"
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05757: "only datanode could receive compute pool message type 'R'"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05758: "only coordinator could receive compute pool message type 'C'"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05759: "only coordinator could receive compute pool message type 'D'"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05760: "len is invalid[%d]"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05761 - GAUSS-05770
+
+<br/>
+
+GAUSS-05761: "Failed to get runtime info from the compute pool."
+
+SQLSTATE: 08006
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05762: "Failed to send request to ccn: %s for cp runtime info! Description: %s"
+
+SQLSTATE: 57P03
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05763: "No CCN in cluster!"
+
+SQLSTATE: XX005
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05764: "Failed to send request to ccn: %s for dn list! dnnum: %d, Description: %s"
+
+SQLSTATE: 57P03
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05765: "Failed to get dn list from CCN: %s, Description: %s"
+
+SQLSTATE: 57P03
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05766: "Failed to send request to CCN."
+
+SQLSTATE: 57P03
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05767: "invalid ccn index %d"
+
+SQLSTATE: 42P17
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05768: "invalid size [%lu]"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05769: "something wrong in CPmonitor thread, so reboot CPmonitor thread."
+
+SQLSTATE: 57P03
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05770: "Failed to get the values of $GAUSSHOME"
+
+SQLSTATE: 42704
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05771 - GAUSS-05780
+
+<br/>
+
+GAUSS-05771: "Failed to open config file to connect compute pool. file path: %s"
+
+SQLSTATE: 58P03
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05772: "Failed to get the size of the config file to connect compute pool. file path: %s"
+
+SQLSTATE: 58P03
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05773: "Failed to get the data of the config file to connect compute pool. file path: %s"
+
+SQLSTATE: 58P03
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05774: "'cpip', 'cpport', 'username', 'password', 'version', 'dnnum', 'pl' are needed to connect to the compute pool."
+
+SQLSTATE: 42P17
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05775: "pl should be greater than 0, pl is %d current."
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05776: "no valid config info in cp_client.conf."
+
+SQLSTATE: 42P17
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05777: "get reload signal in %s"
+
+SQLSTATE: D0011
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05778: "the config of node is changed."
+
+SQLSTATE: F0000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05779: "init transaction error, data nodes or coordinators num init failed"
+
+SQLSTATE: D0014
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05780: "no the version of the compute pool is provided."
+
+SQLSTATE: XX005
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05781 - GAUSS-05790
+
+<br/>
+
+GAUSS-05781: "The key string of 'R' request could not be NULL"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05782: "estimate_memory will out of MAX_INT, orign[%d], addMemory[%d]"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05783: "%s space is out of %s's %s space limit"
+
+SQLSTATE: 57014
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05784: "the space used on DN has exceeded the sql use space limit (%d kB)."
+
+SQLSTATE: 57014
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05785: "Remote Sender: Failed to send command to datanode"
+
+SQLSTATE: 22003
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05786: "Normal user could not readjust other user space"
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05787: "cannot open database"
+
+SQLSTATE: 58000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05788: "user space is out of space limit"
+
+SQLSTATE: 57014
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05789: "The memory usage of %s is out of control. it will exit!"
+
+SQLSTATE: 0B000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05790: "role %u does not exist"
+
+SQLSTATE: 42704
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05791 - GAUSS-05800
+
+<br/>
+
+GAUSS-05791: "resource pool %u does not exist in htab."
+
+SQLSTATE: 42704
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05792: "resource pool with control_group %s has been existed in the two-layer resource pool list "
+
+SQLSTATE: 42710
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05793: "cannot create resource pool with class '%s', it has been existed in the normal resource pool list"
+
+SQLSTATE: 42710
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05794: "mem_percent of two-layer resource pools cannot be 0"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05795: "memory percent value is beyond the available range."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05796: "resource pool information of '%s' is missing."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05797: "cannot alter control_group between different groups or alter to a different layer. "
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05798: "resource pool with control group '%s' already exists"
+
+SQLSTATE: 42710
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05799: "cannot alter normal resource pool to the two-layer resource pool list."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05800: "mem_percent of two-layer resource pool cannot be altered to 0."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/59-GAUSS-05801-GAUSS-05900.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/59-GAUSS-05801-GAUSS-05900.md
new file mode 100644
index 0000000000000000000000000000000000000000..d9100d30cf188ee79ec6423d16dc71863b63aa6a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/59-GAUSS-05801-GAUSS-05900.md
@@ -0,0 +1,698 @@
+---
+title: GAUSS-05801 - GAUSS-05900
+summary: GAUSS-05801 - GAUSS-05900
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-05801 - GAUSS-05900
+
+<br/>
+
+## GAUSS-05801 - GAUSS-05810
+
+<br/>
+
+GAUSS-05801: "redundant options: 'mem_percent'"
+
+SQLSTATE: 22002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05802: "mem_percent has to be in the range of 0-100."
+
+SQLSTATE: 22003
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05803: "redundant options: 'active_statements'"
+
+SQLSTATE: 44000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05804: "active_statements value can't be %d."
+
+SQLSTATE: 22003
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05805: "Failed to initialize Cgroup. Please check Workload manager is enabled and Cgroups have been created!"
+
+SQLSTATE: 58000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05806: "redundant options: 'max_dop'"
+
+SQLSTATE: 22002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05807: "redundant options: 'memory_limit'"
+
+SQLSTATE: 22002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05808: "parent is not supported currently!"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05809: "redundant options: 'io_limits'"
+
+SQLSTATE: 22002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05810: "io_limits can't be %d."
+
+SQLSTATE: 22003
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05811 - GAUSS-05820
+
+<br/>
+
+GAUSS-05811: "redundant options: 'io_priority'"
+
+SQLSTATE: 22002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05812: "io_priority can only be named as 'High', 'Low', 'Medium' and 'None'."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05813: "redundant options: 'nodegroup'"
+
+SQLSTATE: 22002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05819: "redundant options: 'is_foreign'"
+
+SQLSTATE: 22002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05821 - GAUSS-05830
+
+<br/>
+
+GAUSS-05823: "Can't modify is_foreign option when altering resource pool."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05826: "Can't create parent resource pool used for foreign users."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05827: "cannot get resource pool information of %u"
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05828: "cache lookup failed for resource pool id %u, it is removed?"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05831 - GAUSS-05840
+
+<br/>
+
+GAUSS-05833: "The create resource pool statement buffer is too small(%d)."
+
+SQLSTATE: 42P26
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05834: "must be system admin or vcadmin to create resource pool"
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05835: "default session_respool 'invalid_pool' is not allowed to set by user"
+
+SQLSTATE: 42602
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05836: "The memory of resource pool htab cannot be out of %dMB. please drop the unnecessary resource pools"
+
+SQLSTATE: 42P26
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05837: "must be system admin or vcadmin to change resource pools"
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05838: "user %u does not exist"
+
+SQLSTATE: 42704
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05839: "user set perm space failed because its used perm space is out of perm space limit."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05840: "user set temp space failed because its used temp space is out of temp space limit."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05841 - GAUSS-05850
+
+<br/>
+
+GAUSS-05841: "user set spill space failed because its used spill space is out of spill space limit."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05842: "user set group user failed because group user's used perm space will be out of perm space limit."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05843: "user set group user failed because group user's used temp space will be out of temp space limit."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05844: "user set group user failed because group user's used spill space will be out of spill space limit."
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05845: "group user's %s space cannot be less than its child user's %s space limit."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05846: "need two valid user."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05847: "cannot get resource pool information of user %u"
+
+SQLSTATE: 42P26
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05848: "user %u cannot be used as user group, for it uses non-parent resource pool %s"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05849: "please specify resource pool when create or alter user with user group %u"
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05850: "cannot get resource pool information of resource pool %u"
+
+SQLSTATE: 42P26
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05851 - GAUSS-05860
+
+<br/>
+
+GAUSS-05851: "resource pool %u cannot be used, for it is used by user %u"
+
+SQLSTATE: 55006
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05852: "please specify user group when create or alter user with child resource pool %u."
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05853: "non-child resource pool %u cannot be used for child user"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05854: "parent user's resource pool(control_group is '%s') and resource pool specified(control_group is '%s') don't match"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05855: "cannot use resource pool %u when alter user with 'user group default'"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05856: "user %u has child users, cannot alter it with any operation"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05857: "please specify 'user group default' when create or alter user with non-child resource pool %u."
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05858: "please specify resource pool when alter user with 'user group default'"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05859: "super user cannot use resource pool in the two-layer resource pool list."
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05860: "cannot find resource pool with user: %u"
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05861 - GAUSS-05870
+
+<br/>
+
+GAUSS-05862: "session_respool name '%s' does not exist"
+
+SQLSTATE: 42602
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05863: "parent resource pool '%s' cannot be used as sesion_respool"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05864: "resource pool '%s' is not in logical cluster '%s'."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05869: "Error: environment variable '%s' contain invaild symbol '%s'.\n"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05870: "Cgroup is not mounted or enable_control_group is false"
+
+SQLSTATE: 0B000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05871 - GAUSS-05880
+
+<br/>
+
+GAUSS-05871: "must be superuser account to print cgroup config"
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05872: "move node failed, out of memory."
+
+SQLSTATE: 53200
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05873: "[DYWLM] Failed to send dynamic workload params to CCN!"
+
+SQLSTATE: 08006
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05874: "[DYWLM] Failed to receive queue info from CCN, error info: %s"
+
+SQLSTATE: 08006
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05875: "out of memory of current node, please check statement count"
+
+SQLSTATE: 53200
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05876: "failed to enqueue in central node"
+
+SQLSTATE: 58000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05877: "resource pool: %s does not exist"
+
+SQLSTATE: 42704
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05878: "out of memory of central node"
+
+SQLSTATE: 53200
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05879: "group name %s does not exist on central node"
+
+SQLSTATE: 42704
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05880: "the counts of waiting statements have reached the limitation."
+
+SQLSTATE: 54000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05881 - GAUSS-05890
+
+<br/>
+
+GAUSS-05881: "out of memory of current memory."
+
+SQLSTATE: 53200
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05882: "Central node is recovering now, please retry later."
+
+SQLSTATE: 08006
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-05885: "client recover failed"
+
+SQLSTATE: 58000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-05886: "records is NULL."
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-05887: "out of memory of records."
+
+SQLSTATE: 53200
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-05888: "dynamic workload record number is not correct!"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-05889: "invalid retcode [%d]"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-05890: "invalid paras."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+<br/>
+
+## GAUSS-05891 - GAUSS-05900
+
+<br/>
+
+GAUSS-05891: "option '%s' not recognized."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05892: "permission denied to create data source '%s'"
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05893: "data source '%s' already exists"
+
+SQLSTATE: 42710
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05894: "permission denied to change owner of data source '%s'"
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05895: "directory path contains illegal string: '%s'"
+
+SQLSTATE: 42602
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05896: "'%s' is not a directory, please check"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05897: "'%s' is a symlink, cannot be added as directory"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05898: "permission denied to create directory '%s'"
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05899: "directory '%s' is already used by an existing object"
+
+SQLSTATE: 42710
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05900: "permission denied to drop directory '%s'"
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/6-GAUSS-00501-GAUSS-00600.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/6-GAUSS-00501-GAUSS-00600.md
new file mode 100644
index 0000000000000000000000000000000000000000..e847f73d96b730b24b2dfdd7ce1ee3dcf22a9c25
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/6-GAUSS-00501-GAUSS-00600.md
@@ -0,0 +1,728 @@
+---
+title: GAUSS-00501 - GAUSS-00600
+summary: GAUSS-00501 - GAUSS-00600
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-00501 - GAUSS-00600
+
+<br/>
+
+## GAUSS-00501 - GAUSS-00510
+
+<br/>
+
+GAUSS-00501: "template database '%s' does not exist"
+
+SQLSTATE: 3D000
+
+Description: The template database **template1** does not exist.
+
+Solution: The **template1** database is lost due to a database system exception. Restart the database or manually create the **template1** database.
+
+GAUSS-00502: "permission denied to copy database '%s'"
+
+SQLSTATE: 42501
+
+Description: In the syntax for creating a database, if the original database is not a template database, the user role does not have permission to create a database.
+
+Solution: In the syntax for creating a database, if the original database is not a template database, only users who have the CREATEDB permission or the system administrator can create a database. Ensure that the user has the required permission.
+
+GAUSS-00503: "invalid server encoding %d"
+
+SQLSTATE: 42809
+
+Description: In the syntax for creating a database, the specified encoding format is invalid.
+
+Solution: Ensure that the encoding format must be GBK, UTF8, or Latin1.
+
+GAUSS-00504: "invalid locale name: '%s'"
+
+SQLSTATE: 42809
+
+Description: When you create a database, the specified database character set is invalid.
+
+Solution: In the syntax for creating a database, ensure that the character set specified for the new database must match that of the template database. Use the **show lc_collate;** command to query the character set of the template database.
+
+GAUSS-00505: "new encoding (%s) is incompatible with the encoding of the template database (%s)"
+
+SQLSTATE: 22023
+
+Description: In the syntax for creating a database, the character encoding specified for the new database does not match that of the template database **template0**.
+
+Solution: In the syntax for creating a database, ensure that the character encoding specified for the new database must match that of the template database **template0**. Use **show server_encoding;** to query the character encoding of the template database **template0**. Then, modify the character encoding specified for the created database.
+
+GAUSS-00506: "new collation (%s) is incompatible with the collation of the template database (%s)"
+
+SQLSTATE: 22023
+
+Description: In the syntax for creating a database, the character set specified for the new database does not match that of the template database **template0**.
+
+Solution: In the syntax for creating a database, ensure that the character set specified for the new database must match that of the template database **template0**. Use the **show lc_collate;** command to query the character set of the template database **template0**. Then, modify the character set specified for the created database.
+
+GAUSS-00507: "new LC_CTYPE (%s) is incompatible with the LC_CTYPE of the template database (%s)"
+
+SQLSTATE: 22023
+
+Description: In the syntax for creating a database, the character type specified for the new database does not match that of the template database **template0**.
+
+Solution: In the syntax for creating a database, ensure that the character type specified for the new database must match that of the template database **template0**. Use the **show lc_ctype;** command to query the character type of the template database **template0**. Then, modify the character type specified for the created database.
+
+GAUSS-00508: "pg_global cannot be used as default tablespace"
+
+SQLSTATE: 22023
+
+Description: In the syntax for creating a database, the default tablespace specified for the new database is **pg_global**.
+
+Solution: In the syntax for creating a database, ensure that the default tablespace specified for the new database is not **pg_global**. Currently, only the default tablespace is supported.
+
+GAUSS-00509: "cannot assign new default tablespace '%s'"
+
+SQLSTATE: 0A000
+
+Description: In the syntax for creating a database, the default tablespace specified for the new database is **pg_global**.
+
+Solution: In the syntax for creating a database, ensure that the directory for the tablespace is valid when specifying a tablespace other than the default tablespace and the global tablespace for the new tablespace. If the directory is invalid, create a valid directory.
+
+GAUSS-00510: "database '%s' already exists"
+
+SQLSTATE: 42P04
+
+Description: The database name already exists.
+
+Solution: Use the **\l** command to check whether the database name exists. If yes, rename the database.
+
+<br/>
+
+## GAUSS-00511 - GAUSS-00520
+
+<br/>
+
+GAUSS-00511: "source database '%s' is being accessed by other users"
+
+SQLSTATE: 55006
+
+Description: The database is being accessed by other users.
+
+Solution: If it is accessed by other users, data is inconsistent. In this case, deny access by other users and log in to the database again.
+
+GAUSS-00512: "encoding '%s' does not match locale '%s'"
+
+SQLSTATE: 22023
+
+Description: The character encoding specified by the currently created database does not match that obtained from a specified character type.
+
+Solution: Ensure that the character encoding specified by the currently created database matches that obtained from a specified character type. If they are inconsistent, specify them to be the same when creating data again.
+
+GAUSS-00513: "database '%s' does not exist"
+
+SQLSTATE: 3D000
+
+Description: When the **DROP DATABASE** syntax is used to delete a database, this database does not exist or is invalid.
+
+Solution: Ensure that the deleted database is a valid one.
+
+GAUSS-00514: "cannot drop a template database"
+
+SQLSTATE: 42809
+
+Description: Attempting to delete the template database **template0** or **template1** is an invalid operation.
+
+Solution: Specify a database to be deleted again because the default template database **template0** or **template1** cannot be deleted.
+
+GAUSS-00515: "cannot drop the currently open database"
+
+SQLSTATE: 55006
+
+Description: The database to be deleted is being accessed by other users and cannot be deleted.
+
+Solution: Ensure that the database to be deleted is not being accessed by other users and instruct the users to log out of the database and then delete the database again.
+
+GAUSS-00516: "cannot drop the default database"
+
+SQLSTATE: 42809
+
+Description: Invalid operation to delete the default database **postgres**.
+
+Solution: Do not delete the default database **postgres**.
+
+GAUSS-00517: "database '%s' is being accessed by other users"
+
+SQLSTATE: 55006
+
+Description: The database is being accessed by other users.
+
+Solution: If it is accessed by other users, data is inconsistent. In this case, deny access by other users and delete the database again.
+
+GAUSS-00519: "permission denied to rename database"
+
+SQLSTATE: 42501
+
+Description: You do not have permission to change the database name.
+
+Solution: Change the database name as a database owner or an administrator user.
+
+GAUSS-00520: "current database cannot be renamed"
+
+SQLSTATE: 0A000
+
+Description: The name of a database in use cannot be changed.
+
+Solution: Do not change the name of the database in use.
+
+<br/>
+
+## GAUSS-00521 - GAUSS-00530
+
+<br/>
+
+GAUSS-00521: "cannot change the tablespace of the currently open database"
+
+SQLSTATE: 55006
+
+Description: When a database is being accessed by other users, its tablespace cannot be modified using the **ALTER DATABASE SET TABLESPACE** syntax.
+
+Solution: Ensure that other users are not accessing the database when modifying the database tablespace. If the database has been accessed by other users, log out of the database and attempt to modify the tablespace of the database again.
+
+GAUSS-00522: "some relations of database '%s' are already in tablespace '%s'"
+
+SQLSTATE: 55000
+
+Description: If relationship objects, such as tables, indexes, and views, exist in the tablespace directory of a database, its tablespace cannot be modified using the **ALTER DATABASE SET TABLESPACE** syntax.
+
+Solution: Ensure that no relationship objects, such as tables, indexes, and views, exist in a database when modifying the database tablespace. If such relationship objects exist, delete them and then attempt to modify the tablespace again.
+
+GAUSS-00523: "could not remove directory '%s': %m"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00524: "permission denied to change owner of database"
+
+SQLSTATE: 42501
+
+Description: You do not have permission to modify the database owner using the **ALTER DATABASE name OWNER TO newowner** syntax.
+
+Solution: Modify the database owner as a database owner or an administrator user using the **ALTER DATABASE name OWNER TO newowner** syntax.
+
+GAUSS-00526: "could not create directory '%s': %m"
+
+SQLSTATE: XX000
+
+Description: When a database tablespace is being created, the following exceptions may occur in the directory of this tablespace: 1. The current user is not an administrator user and does not have permission to access this directory. 2. The file system is read-only. 3. This directory already exists. 4. Disk space is insufficient for creating a directory. 5. Hardware faults result in I/O errors. 6. An internal error occurs in MogDB. "
+
+Solution: Perform the following operations to resolve the problems: 1. Ensure that the current user is an administrator user or has the database creation permission. 2. Change the file system permissions to read and write permissions if the file system is read-only. 3. Do not create a tablespace if the tablespace directory exists.
+
+GAUSS-00527: "could not stat directory '%s': %m"
+
+SQLSTATE: XX000
+
+Description: The directory of a database tablespace to be created does not exist or the directory name is invalid.
+
+Solution: Ensure that the directory of a database tablespace to be created is valid.
+
+GAUSS-00528: "'%s' exists but is not a directory"
+
+SQLSTATE: 42809
+
+Description: The directory of a database tablespace to be created is incorrect.
+
+Solution: Ensure that the directory of a database tablespace to be created is valid.
+
+GAUSS-00529: "Permission denied to create tablespace '%s'."
+
+SQLSTATE: 42501
+
+Description: You do not have permission to create a tablespace in the database.
+
+Solution: Create a tablespace in the database as a system administrator.
+
+GAUSS-00530: "tablespace location cannot contain single quotes"
+
+SQLSTATE: 42602
+
+Description: When the **CREATE TABLESPACE tablespace_name …LOCATION** syntax is used to specify a tablespace directory, the location information strings are marked with single quotation marks (").
+
+Solution: Mark location information strings with double quotation marks ("").
+
+<br/>
+
+## GAUSS-00531 - GAUSS-00540
+
+<br/>
+
+GAUSS-00531: "tablespace location must be an absolute path"
+
+SQLSTATE: 42P17
+
+Description: When the **CREATE TABLESPACE tablespace_name …LOCATION** syntax is used to specify a tablespace directory, the location information strings indicate an incorrect path.
+
+Solution: Specify an absolute path using the location information string.
+
+GAUSS-00532: "tablespace location '%s' is too long"
+
+SQLSTATE: 42P17
+
+Description: When the **CREATE TABLESPACE tablespace_name…LOCATION** syntax is used to specify the length of a tablespace directory, the length value of the tablespace directory is greater than 1024.
+
+Solution: Change the length value of the tablespace directory to a value less than or equal to 1024.
+
+GAUSS-00533: "unacceptable tablespace name '%s'"
+
+SQLSTATE: 42939
+
+Description: When the **CREATE TABLESPACE tablespace_name** syntax is used to create a tablespace, the tablespace name is invalid.
+
+Solution: Ensure that the tablespace name is unique in the database and does not start with **pg** which is used to name system tablespaces.
+
+GAUSS-00534: "tablespace '%s' already exists"
+
+SQLSTATE: 42710
+
+Description: The tablespace name already exists.
+
+Solution: Run **\db** to check whether the tablespace name exists. If yes, rename the tablespace.
+
+GAUSS-00535: "tablespaces are not supported on this platform"
+
+SQLSTATE: 0A000
+
+Description: Tablespaces are not supported.
+
+Solution: Do not use tablespaces.
+
+GAUSS-00536: "Tablespace '%s' does not exist."
+
+SQLSTATE: 42704
+
+Description: The tablespace deleted using **DROP TABLESPACE** does not exist.
+
+Solution: Run **\db** to check whether the tablespace name exists. Only tablespaces that exist in the database can be deleted.
+
+GAUSS-00537: "tablespace '%s' is used by partitioned table '%s'"
+
+SQLSTATE: 0A000
+
+Description: Invalid operation to delete the tablespace used by a partitioned table.
+
+Solution: Do not delete the tablespace that has been used by a partitioned table.
+
+GAUSS-00538: "tablespace '%s' is not empty"
+
+SQLSTATE: 55000
+
+Description: The tablespace to be deleted is not empty.
+
+Solution: Delete a tablespace only when it is empty.
+
+GAUSS-00539: "directory '%s' does not exist"
+
+SQLSTATE: 58P01
+
+Description: When creating a tablespace, the tablespace directory **$PGDATA/pg_tblspc/** does not exist.
+
+Solution: Check whether the tablespace directory **$PGDATA/pg_tblspc/** exists before creating a tablespace. If the directory does not exist, restart the database or a single node.
+
+GAUSS-00540: "could not set permissions on directory '%s': %m"
+
+SQLSTATE: XX000
+
+Description: When creating a tablespace, read, write, and execute permissions failed to be set for the tablespace directory **$PGDATA/pg_tblspc/**.
+
+Solution: Perform the following operations to resolve the problems:
+
+1. Ensure that the current user is an administrator user or has the database creation permission.
+2. Change the file system permissions to read and write permissions if the file system is read-only.
+3. Do not create a tablespace if the tablespace directory exists.
+
+<br/>
+
+## GAUSS-00541 - GAUSS-00550
+
+<br/>
+
+GAUSS-00541: "directory '%s' already in use as a tablespace"
+
+SQLSTATE: 55006
+
+Description: The tablespace directory to be created exists.
+
+Solution: Define the tablespace in another directory.
+
+GAUSS-00542: "could not remove symbolic link '%s': %m"
+
+SQLSTATE: XX000
+
+Description: Failed to remove a sign-linking file.
+
+Solution: Ensure that the symbol link points to a valid file.
+
+GAUSS-00543: "could not create symbolic link '%s': %m"
+
+SQLSTATE: XX000
+
+Description: Failed to create a sign-linking file.
+
+Solution: Check the error code to determine the error causes, such as no permission, insufficient disk space, and existed file. Then, handle the error based on the causes.
+
+GAUSS-00544: "tablespace '%s' does not exist"
+
+SQLSTATE: 42704
+
+Description: The tablespace does not exist.
+
+Solution: Ensure that the tablespace exists in the **pg_tablespace** system catalog.
+
+GAUSS-00546: "could not create tablespace directory '%s': %m"
+
+SQLSTATE: XX000
+
+Description: Failed to create a tablespace.
+
+Solution: Check the error code to determine the error causes, such as no permission, insufficient disk space, and existed file. Then, handle the error based on the causes.
+
+GAUSS-00547: "could not access directory '%s': %m"
+
+SQLSTATE: XX000
+
+Description: Failed to access a tablespace directory.
+
+Solution: Check the error code to determine the error causes, such as no permission, insufficient disk space, and existed file. Then, handle the error based on the causes.
+
+GAUSS-00548: "tblspc_redo: unknown op code %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00549: "'%s' is an aggregate function"
+
+SQLSTATE: 42809
+
+Description: 1. Failed to delete an aggregate function using **DROP FUNCTION**. 2. Failed to modify an aggregate function using **ALTER FUNCTION**. 3. Failed to obtain the definition of an aggregate function using **pg_get_functiondef**.
+
+Solution: Perform the following operations to resolve the problems: 1. Run **DROP AGGREGATE** to delete the aggregate function. 2. Run **ALTER AGGREGATE** to modify the aggregate function. 3. View the aggregate function in the **PG\_AGGREGATE** system catalog.
+
+GAUSS-00550: "unexpected object type (%d)"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-00551 - GAUSS-00560
+
+<br/>
+
+GAUSS-00551: "could not determine which collation to use for view column '%s'"
+
+SQLSTATE: 42P22
+
+Description: The collation to be used by a view column cannot be determined.
+
+Solution: Use the **COLLATE** clause to assign a collation to the column.
+
+GAUSS-00552: "view must have at least one column"
+
+SQLSTATE: 42P16
+
+Description: The number of columns defining a view is smaller than 1.
+
+Solution: Ensure that the number of columns defining a view is greater than or equal to 1.
+
+GAUSS-00553: "'%s' is not a view"
+
+SQLSTATE: 42809
+
+Description: The object is not a view.
+
+Solution: Ensure that the object is a view.
+
+GAUSS-00554: "cannot drop columns from view"
+
+SQLSTATE: 42P16
+
+Description: Failed to delete columns from a view
+
+Solution: Do not delete columns from a view.
+
+GAUSS-00555: "cannot change name of view column '%s' to '%s'"
+
+SQLSTATE: 42P16
+
+Description: Failed to modify the columns in a view.
+
+Solution: Do not modify the columns in a view.
+
+GAUSS-00556: "cannot change data type of view column '%s' from %s to %s"
+
+SQLSTATE: 42P16
+
+Description: When **CREATE OR REPLACE VIEW** is used to define a view, the new view and the original view do not have the same column data type.
+
+Solution: Ensure that the new view and the original view have the same column data type.
+
+GAUSS-00557: "unexpected parse analysis result"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00559: "views must not contain data-modifying statements in WITH"
+
+SQLSTATE: 0A000
+
+Description: Statements used to define a view contain the **WITH** clause.
+
+Solution: Ensure that a single **SELECT** statement is executed to query the results.
+
+GAUSS-00560: "CREATE VIEW specifies more column names than columns"
+
+SQLSTATE: 42601
+
+Description: The number of columns defining a view is greater than that of columns in the returned results.
+
+Solution: Ensure that the number of columns defining a view is not greater than that of columns in the returned results.
+
+<br/>
+
+## GAUSS-00561 - GAUSS-00570
+
+<br/>
+
+GAUSS-00561: "views cannot be unlogged because they do not have storage"
+
+SQLSTATE: 42601
+
+Description: The view to be defined is set to **UNLOGGED**.
+
+Solution: Do not set the view to be defined to **UNLOGGED** because it does not have actual storage.
+
+GAUSS-00562: "unrecognized value for EXPLAIN option '%s': '%s'"
+
+SQLSTATE: 22023
+
+Description: The **EXPLAIN FORMAT** parameter cannot be recognized.
+
+Solution: Ensure that the value of the **EXPLAIN FORMAT** parameter is **TEXT**, **XML**, **JSON**, or **YAML**.
+
+GAUSS-00563: "unrecognized EXPLAIN option '%s'"
+
+SQLSTATE: 42601
+
+Description: The **EXPLAIN** parameter cannot be recognized.
+
+Solution: Ensure that the value of the **EXPLAIN** parameter is **ANALYZE**, **VERBOSE**, **COSTS**, **BUFFERS**, **NODES**, **NUM_NODES**, **TIMING**, **CPU**, **DETAIL**, **PERFORMANCE**, or **FORMAT**.
+
+GAUSS-00564: "EXPLAIN option BUFFERS requires ANALYZE"
+
+SQLSTATE: 22023
+
+Description:**ANALYZE** is not specified for **EXPLAIN BUFFERS**.
+
+Solution: Specify **ANALYZE** for **EXPLAIN BUFFERS**.
+
+GAUSS-00565: "EXPLAIN option CPU requires ANALYZE"
+
+SQLSTATE: 22023
+
+Description:**ANALYZE** is not specified for **EXPLAIN CPU**.
+
+Solution: Specify **ANALYZE** for **EXPLAIN CPU**.
+
+GAUSS-00566: "EXPLAIN option DETAIL requires ANALYZE"
+
+SQLSTATE: 22023
+
+Description:**ANALYZE** is not specified for **EXPLAIN DETAIL**.
+
+Solution: Specify **ANALYZE** for **EXPLAIN DETAIL**.
+
+GAUSS-00567: "EXPLAIN option TIMING requires ANALYZE"
+
+SQLSTATE: 22023
+
+Description:**ANALYZE** is not specified for **EXPLAIN TIMING**.
+
+Solution: Specify **ANALYZE** for **EXPLAIN TIMING**.
+
+GAUSS-00568: "EXPLAIN %s requires ANALYZE"
+
+SQLSTATE: 22023
+
+Description:**ANALYZE** is not specified for **EXPLAIN CREATE TABLE AS SELECT** or **EXPLAIN SELECT INTO**.
+
+Solution: Specify **ANALYZE** for **EXPLAIN CREATE TABLE AS SELECT** or **EXPLAIN SELECT INTO**.
+
+GAUSS-00569: "no tlist entry for key %d"
+
+SQLSTATE: XX000
+
+Description: Generated plan error.
+
+Solution:Contact technical support.
+
+GAUSS-00570: "cache lookup failed for index %u"
+
+SQLSTATE: XX000
+
+Description: Failed to find the index in the system catalog cache.
+
+Solution: Ensure that the index name is correct.
+
+<br/>
+
+## GAUSS-00571 - GAUSS-00580
+
+<br/>
+
+GAUSS-00571: "unrecognized DISCARD target: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00572: "function '%s' was not called by trigger manager"
+
+SQLSTATE: 39P01
+
+Description: A function is not invoked by the trigger manager.
+
+Solution: Ensure that the function is invoked as an AFTER row trigger.
+
+GAUSS-00573: "function '%s' must be fired AFTER ROW"
+
+SQLSTATE: 39P01
+
+Description: A function is invoked before an AFTER row trigger is triggered.
+
+Solution: Ensure that the function is invoked after the AFTER row trigger is triggered.
+
+GAUSS-00574: "function '%s' must be fired for INSERT or UPDATE"
+
+SQLSTATE: 39P01
+
+Description: A trigger is not triggered by the **INSERT/UPDATE** statement.
+
+Solution: Ensure that the trigger is triggered by the **INSERT/UPDATE** statement.
+
+GAUSS-00575: "Permission denied to create role with option UNENCRYPTED."
+
+SQLSTATE: XX000
+
+Description: An error occurs when **UNENCRYPTED** is specified for **CREATE ROLE**.
+
+Solution: Encrypt the password.
+
+GAUSS-00579: "Permission denied to create role."
+
+SQLSTATE: 42501
+
+Description: You have no permission to create users.
+
+Solution: Check user permissions. For permissions to create users, see en-us_topic_0237121098.html.
+
+GAUSS-00580: "Separation of privileges is used,user can't be created because of too many privileges."
+
+SQLSTATE: 42501
+
+Description: The permissions specified for users exceed the limit during privilege separation.
+
+Solution: Ensure that the permissions specified for users do not exceed the limit during privilege separation.
+
+<br/>
+
+## GAUSS-00581 - GAUSS-00590
+
+<br/>
+
+GAUSS-00581: "role name '%s' is reserved"
+
+SQLSTATE: 42939
+
+Description: A username is a reserved keyword.
+
+Solution: Ensure that the username is not the reserved keyword, for example, public or none.
+
+GAUSS-00582: "role '%s' already exists"
+
+SQLSTATE: 42710
+
+Description: The username already exists.
+
+Solution: Use a new username.
+
+GAUSS-00584: "The password does not satisfy the complexity requirement"
+
+SQLSTATE: XX000
+
+Description: The password does not meet the complexity requirements.
+
+Solution: 1. The password cannot be the same as the username. 2. The password contains at least eight characters and at least three of the following: uppercase characters (A to Z), lowercase characters (a to z), digits (0 to 9), and other characters (limited to ~!@#$%^&*()-_=+\|[{}];:,<.>/?).
+
+GAUSS-00588: "The password could not be NULL."
+
+SQLSTATE: XX000
+
+Description: The password is null.
+
+Solution: Ensure that the password is not null.
+
+GAUSS-00589: "unacceptable user name: fail to create same name schema for user '%s'"
+
+SQLSTATE: 42939
+
+Description: If the name of a user is invalid, a schema with the same name as the user cannot be created.
+
+Solution: Ensure that the user name does not start with **pg_** which is used to name system modes.
+
+GAUSS-00590: "the relation pg_user_status is invalid"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-00591 - GAUSS-00600
+
+<br/>
+
+GAUSS-00591: "role '%s' does not exist"
+
+SQLSTATE: 42704
+
+Description: The user does not exist.
+
+Solution: Check the user information in the system catalog **pg_roles**.
+
+GAUSS-00593: "Permission denied to change privilege of the initial account."
+
+SQLSTATE: 42501
+
+Description: You have no permission to modify the rights of the initial user.
+
+Solution: Query the system catalog to check whether you have that permission.
+
+GAUSS-00594: "Permission denied to change password of the initial account."
+
+SQLSTATE: 42501
+
+Description: You have no permission to change the password of the initial user.
+
+Solution: Query the system catalog to check whether you have that permission.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/60-GAUSS-05901-GAUSS-06000.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/60-GAUSS-05901-GAUSS-06000.md
new file mode 100644
index 0000000000000000000000000000000000000000..e75eb3cc4d6d5040034e45d7fe11b2c38c623784
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/60-GAUSS-05901-GAUSS-06000.md
@@ -0,0 +1,764 @@
+---
+title: GAUSS-05901 - GAUSS-06000
+summary: GAUSS-05901 - GAUSS-06000
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-05901 - GAUSS-06000
+
+<br/>
+
+## GAUSS-05901 - GAUSS-05910
+
+<br/>
+
+GAUSS-05901: "permission denied to change owner of directory"
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05902: "could not open extension control file: %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05903: "extension '%s' already exists in schema '%s'"
+
+SQLSTATE: 42710
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05904: "extcondition is not a 1-D Oid array"
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05905: "extension is null"
+
+SQLSTATE: XX005
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05906: "EXPLAIN PLAN does not support on datanode or single node."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05907: "EXPLAIN option 'PLAN' can not work with other options."
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05908: "EXPLAIN %s is not supported when declaring a cursor."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05909: "invalid value for parameter explain_perf_mode."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05910: "unrecognized value for EXPLAIN option 'format'."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05911 - GAUSS-05920
+
+<br/>
+
+GAUSS-05911: "u_sess->instr_cxt.global_instr is NULL"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05912: "statement_id is too long. Input statement_id length=%u, however max length=%d."
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05913: "Relation 'plan_table_data' does not exist"
+
+SQLSTATE: 42602
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05914: "Do not specify any information for CREATE POLICY '%s' ON '%s'"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05915: "Create row level security policy '%s' failed, because it will result in infinite recursion for DML queries"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05916: "row level policy '%s' for table '%s' already exists"
+
+SQLSTATE: 42710
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05917: "Num of row level policies for relation should less than or equal to %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05918: "Do not specify any information for ALTER POLICY '%s' ON '%s'"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05919: "row level security policy '%s' for relation '%s' does not exists"
+
+SQLSTATE: 42704
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05920: "Alter row level security policy '%s' failed, because it will result in infinite recursion for DML queries"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05921 - GAUSS-05930
+
+<br/>
+
+GAUSS-05921: "row level policy '%s' for relation '%s' already exists"
+
+SQLSTATE: 42710
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05922: "unrecognized row level security policy command"
+
+SQLSTATE: 42704
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05923: "too many roles specified in SQL statement."
+
+SQLSTATE: 54000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05924: "%s not implemented"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05925: "could not write to staging temporary file while exporting segment %s"
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05926: "could not write to local temporary buffile: %m"
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05927: "Write-Only table's output directory %s is not empty"
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05928: "could not rewind OBS exporting temporary file: %m"
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05929: "must be system admin to CREATE TEXT SEARCH DICTIONARY"
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05930: "CREATE TEXT SEARCH DICTIONARY in a temp namespace is not supported"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05931 - GAUSS-05940
+
+<br/>
+
+GAUSS-05931: "Not allowed to alter built-in text search dictionary"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05932: "Not allowed to drop built-in text search dictionary"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05933: "Not allowed Template parameter in alter text search dictionary"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05934: "env $GAUSSHOME not found, please set it first"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05935: "failed to bind fd(%d) to ssl"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05936: "m_fd + 1 cannot be greater than FD_SETSIZE"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05937: "The peer GDS has performed an orderly shutdown on current connection."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05938: "exception from GDS '%s':%m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05939: "Message size exceeds the maximum allowed (%d)"
+
+SQLSTATE: OP002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05940: "Invalid command to serialize."
+
+SQLSTATE: OP002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05941 - GAUSS-05950
+
+<br/>
+
+GAUSS-05941: "Unexpected length of data coming supposedly from GDS. Could be an forged attack package."
+
+SQLSTATE: DB001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05942: "Failed to _ReadError in CMD_TYPE_ERROR, could be a forged package."
+
+SQLSTATE: DB001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05943: "Failed to _ReadFileSwitch in CMD_TYPE_FILE_SWITCH, could be a forged package."
+
+SQLSTATE: DB001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05944: "Failed to _ReadResponse in CMD_TYPE_RESPONSE, could be a forged package."
+
+SQLSTATE: DB001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05945: "The corresponding GDS is of an older version. Please upgrade GDS to match the server version."
+
+SQLSTATE: DB001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05946: "Failed to _ReadResult in CMD_TYPE_QUERY_RESULT_V1, could be a forged package."
+
+SQLSTATE: DB001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05947: "Hash bkt dir '%s' not exists:%m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05948: "could not create directory '%s':%m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05949: "'%s' exists but is not a directory."
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05950: "permission denied to create tablespace in security mode"
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05951 - GAUSS-05960
+
+<br/>
+
+GAUSS-05951: "Create tablespace with absolute location can't be allowed"
+
+SQLSTATE: 42P17
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05952: "tablespace location can only be formed of 'a~z', 'A~Z', '0~9', '-', '_'"
+
+SQLSTATE: 42P17
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05953: "relative location can only be formed of 'a~z', 'A~Z', '0~9', '-', '_' and two level directory at most"
+
+SQLSTATE: 42P17
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05954: "The relative location can not be null"
+
+SQLSTATE: 42P17
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05955: "could not open pg_tblspc directory"
+
+SQLSTATE: 42P17
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05956: "could not get '%s' status"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05957: "'%s' is not symlink, please check and clean the remains in '%s'"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05958: "target of symbolic link '%s' doesn't exist"
+
+SQLSTATE: 42P17
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05959: "target of symbolic link '%s' isn't directory"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05960: "find conflict linkpath '%s' in pg_tblspc, location '%s'"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05961 - GAUSS-05970
+
+<br/>
+
+GAUSS-05961: "permission denied to alter tablespace in security mode"
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05962: "It is unsupported to reset 'filesystem' option."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05963: "It is unsupported to alter general tablespace to hdfs tablespace."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05964: "Tablespace '%u' does not exist."
+
+SQLSTATE: 58P01
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05965: "Can not get tablespace size with SnapshotNow after try 3 times."
+
+SQLSTATE: P0002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05970: "conflicting or redundant option: 'resource pool'"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-05971 - GAUSS-05980
+
+<br/>
+
+GAUSS-05971: "conflicting or redundant option: 'user group default'"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05972: "conflictiong or redundant option: 'spill space'"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05975: "Can not create role with resource pool (%s) with foreign users option."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05976: "parent cannot be itself."
+
+SQLSTATE: 0P000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05977: "Role '%s': object not defined."
+
+SQLSTATE: 42704
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+<br/>
+
+## GAUSS-05981 - GAUSS-05990
+
+<br/>
+
+GAUSS-05981: "Independent user is not supported."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05982: "Independent user cannot have sysadmin, auditadmin, vcadmin, createrole, monadmin and opradmin attributes."
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05983: "Failed to Generate the random number, errcode:%u"
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05984: "Can not alter role with resource pool (%s) with foreign users option."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05985: "resource pool of role '%s' does not exist."
+
+SQLSTATE: 42P26
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05989: "Can not alter Role '%s' to vcadmin."
+
+SQLSTATE: 0LP01
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+<br/>
+
+## GAUSS-05991 - GAUSS-06000
+
+<br/>
+
+GAUSS-05991: "Only user himself can remove his own independent attribute."
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05992: "Only independent user himself can alter his own password."
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05993: "Only system admin can enable user's password."
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05994: "Only independent user himself can enable his own password."
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05995: "Only system admin can disable user's password."
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05996: "Only independent user himself can disable his own password."
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05997: "resource pool of role '%s' does not exsist."
+
+SQLSTATE: 42P26
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05998: "Only independent user himself can decide his own membership."
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-05999: "Role '%s' can not be granted across virtual clusters."
+
+SQLSTATE: 0LP01
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06000: "While get super user, invalid role OID: %u"
+
+SQLSTATE: 42704
+
+Description:Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/61-GAUSS-06001-GAUSS-06100.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/61-GAUSS-06001-GAUSS-06100.md
new file mode 100644
index 0000000000000000000000000000000000000000..6f959838eb0c5e177e8215a8181eec11ec79f1ee
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/61-GAUSS-06001-GAUSS-06100.md
@@ -0,0 +1,852 @@
+---
+title: GAUSS-06001 - GAUSS-06100
+summary: GAUSS-06001 - GAUSS-06100
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-06001 - GAUSS-06100
+
+<br/>
+
+## GAUSS-06001 - GAUSS-06010
+
+<br/>
+
+GAUSS-06001: "password encryption failed"
+
+SQLSTATE: 28P01
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06002: "cache lookup failed for role with oid %u"
+
+SQLSTATE: 42704
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06003: "%s is not supported for using here, just support template0"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06005: "could not drop database while ddl delay function is enabled"
+
+SQLSTATE: 55006
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06006: "database '%s' is used by a logical decoding slot"
+
+SQLSTATE: 55006
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06007: "Database '%s' is being accessed by other users. You can stop all connections by command: 'clean connection to all force for database XXXX;' or wait for the sessions to end by querying view: 'pg_stat_activity'."
+
+SQLSTATE: 55006
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06008: "dbase_redo: unknown op code %hhu"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06009: "Not support alter cross-database private pbject, please switch to '%s' and run this command"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06010: "permission denied to create foreign table in security mode"
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06011 - GAUSS-06020
+
+<br/>
+
+GAUSS-06011: "Failed to create foreign table '%s'."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06012: "The schema 'dbe_perf' doesn't allow to drop"
+
+SQLSTATE: OP001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06013: "The schema 'snapshot' doesn't allow to drop"
+
+SQLSTATE: OP001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06014: "The schema '%s' doesn't allow to rename"
+
+SQLSTATE: OP001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06015: "It is not supported to rename schema '%s' which includes timeseries table '%s'."
+
+SQLSTATE: 42939
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06016: "column/timeseries store unsupport constraint '%s'"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06017: " period must smaller than ttl."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06018: "It is unsupported to create row/cstore non-temporary/non-unlogged table in hadoop enviroment."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06019: "It is unsupported to create unlogged table and temporary table on DFS tablespace."
+
+SQLSTATE: 42P16
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06020: "It is unsupported to create table with to group option on DFS tablespace."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06021 - GAUSS-06030
+
+<br/>
+
+GAUSS-06021: "It is unsupported to create foreign table with to group option."
+
+SQLSTATE: 42P16
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06022: "Only support hash/replication distribution for dfs table."
+
+SQLSTATE: 42P16
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06023: "Partition can not be created on DFS tablespace.Only table-level tablespace can be DFS.DFS table only support partition strategy '%s' feature."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06024: " unsupported persistency for timeseries table."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06025: "Only support hash distribution for timeseries table."
+
+SQLSTATE: 42P16
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06026: "kvtype of '%s' must be defined when using timeseries."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06027: "TIMESERIES must have one and only one time column."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06028: "type '%s' is not supported in timeseries store"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06029: "Cannot use orientation is timeseries when enable_tsdb is off."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06030: "Only support one partition Key."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06031 - GAUSS-06040
+
+<br/>
+
+GAUSS-06031: "type '%s' does not exist."
+
+SQLSTATE: 42704
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06032: " Partition Key must be of type TIMESTAMP(TZ) when using ttl or period."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06033: " Partition Key must be of kv type TSTAG."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06034: "ON COMMIT only support PRESERVE ROWS or DELETE ROWS option"
+
+SQLSTATE: 42P16
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06035: "Unsupport the dfs table in this version."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06036: "Only support one partial cluster key for dfs/cstore table."
+
+SQLSTATE: 42P16
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06037: "hash bucket table not supported in current version!"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06038: "Local OID column not supported in column/timeseries store tables."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06039: "column constraint on postgres foreign tables are not supported"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06040: "relation type column on postgres foreign tables are not supported"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06041 - GAUSS-06050
+
+<br/>
+
+GAUSS-06041: "The table %s do not support hash bucket"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06042: "Invalid Oid while setting new relfilenode for ts aux table."
+
+SQLSTATE: 42602
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06043: "NOT-SUPPORT: Not support TRUNCATE multiple objects different nodegroup"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06044: "rel %s can not truncate during redis."
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06045: "column '%s' has a kvtype parameter conflict"
+
+SQLSTATE: 42804
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06046: "RENAME SEQUENCE is not yet supported."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06047: "cannot find timeseries aux table (or index). timeseries table oid: %u"
+
+SQLSTATE: OP001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06048: "This ALTER command is not support in timeseries store."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06049: "alter row table tablespace cannot run inside a transaction block"
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06050: "type '%s' is not supported in DFS table."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06051 - GAUSS-06060
+
+<br/>
+
+GAUSS-06051: "It's not supported to add column with default value for timeseries tables."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06052: "It's not supported to alter table add column default with nextval expression."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06053: "It is not supported on DFS table. The detailed reasons are the followings:"
+
+SQLSTATE: 42P16
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06054: "cannot drop TSTime column '%s' from timeseries table"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06055: "unrecognized table type: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06056: "cannot alter column type to '%s'"
+
+SQLSTATE: 42P16
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06057: "PSort %u should depend on only one index relation but not %ld."
+
+SQLSTATE: OP002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06059: "no perm space is available for the targeted owner"
+
+SQLSTATE: 53000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06060: "no perm space is available for the targeted user group"
+
+SQLSTATE: 53000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06061 - GAUSS-06070
+
+<br/>
+
+GAUSS-06061: "no temp space is available for the targeted owner"
+
+SQLSTATE: 53000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06062: "no temp space is available for the targeted user group"
+
+SQLSTATE: 53000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06063: "can not specify 'PARTITION FOR (value,,,)' for 'MOVE PARTITION CLAUSE'"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06064: "invalid partition node type in 'MOVE PARTITION CLAUSE'"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06065: "fail to remote read page, data corrupted in network"
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06066: "invalid page in block %u of relation %s"
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06067: "unknown type %u for ALTER TABLE ROW LEVEL SECURITY"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06068: "cache lookup failed for relation '%s'"
+
+SQLSTATE: 29P01
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06069: "unexpected identity type %u"
+
+SQLSTATE: XX006
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06070: "cannot use non-unique index '%s' as replica identity"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06071 - GAUSS-06080
+
+<br/>
+
+GAUSS-06071: "cannot use expression index '%s' as replica identity"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06072: "cannot use partial index '%s' as replica identity"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06073: "cannot use invalid index '%s' as replica identity"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06074: "internal column %d in unique index '%s'"
+
+SQLSTATE: 55000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06075: "index '%s' cannot be used as replica identity because column '%s' is nullable"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06076: "The obs foreign partition table cannot support on text, csv, carbondata format."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06077: "The obs foreign table has column type bytea, cannot support on orc format."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06078: "Invalid option '%s'"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06079: "There's dependent sequence, but ALTER SEQUENCE SET SCHEMA is not yet supported."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06080: "can't add partition bacause the relation %s has unusable local index"
+
+SQLSTATE: 42P17
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06081 - GAUSS-06090
+
+<br/>
+
+GAUSS-06081: "can't merge partition bacause partition %s has unusable local index"
+
+SQLSTATE: 42P17
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06082: "ALTER TABLE EXCHANGE requires both ordinary table and partitioned table to have the same hashbucket option(on or off)"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06083: "the kv storage type of column mismatch in ALTER TABLE EXCHANGE PARTITION"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06084: "cache lookup failed for relaton %u"
+
+SQLSTATE: 29P01
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06085: "can't split partition bacause relation %s has unusable local index"
+
+SQLSTATE: 42P17
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06086: "the partition oid(%u) of partition name (%s) is not found in partitioned table(%u)."
+
+SQLSTATE: P0002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06087: "Un-supported feature"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06088: "Cannot find a valid job_id."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06089: "cannot find timeseries aux table (or index). search name: %s"
+
+SQLSTATE: OP001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06090: "Unable to create partition policy when enable_tsdb is off."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06091 - GAUSS-06100
+
+<br/>
+
+GAUSS-06091: "%s does not have partition !"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06092: "cannot create partiton policy for aux table."
+
+SQLSTATE: OP001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06093: "Unable to alter partition policy when enable_tsdb is off."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06094: "The function's %s %u dismatch the type %u"
+
+SQLSTATE: 42804
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06095: "The index table does not support verify on cascade mode."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06096: "Non-table objects do not support verify."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06097: "The hdfs table does not support verify."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06098: "The temporary/unlog table does not support verify."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06099: "The important catalog table %s.%s corrupts, the node is %s, please fix it."
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06100: "pg_class entry for relid %u vanished during updating TotalRows"
+
+SQLSTATE: 2F000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/62-GAUSS-06101-GAUSS-06200.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/62-GAUSS-06101-GAUSS-06200.md
new file mode 100644
index 0000000000000000000000000000000000000000..a557e216e0511b21263e5165da97de1fbfc478e7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/62-GAUSS-06101-GAUSS-06200.md
@@ -0,0 +1,860 @@
+---
+title: GAUSS-06101 - GAUSS-06200
+summary: GAUSS-06101 - GAUSS-06200
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-06101 - GAUSS-06200
+
+<br/>
+
+## GAUSS-06101 - GAUSS-06110
+
+<br/>
+
+GAUSS-06101: "return type '%s' must be in installation group"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06102: "fencedmode function cannot accept shell type %s"
+
+SQLSTATE: 42P13
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06103: "parameterCount is invalid %d"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06104: "argument type '%s' must be in installation group"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06105: "fencedmode could not be fenced"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06106: "User defined window function only support INTERNAL language."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06107: "User defined window function only support INTERNAL window function"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06108: "JAVA UDF is not yet supported in current version."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06109: "Java UDF dose not support NOT FENCED functions."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06110: "the builtin function can not be removed,its function oid is '%u'"
+
+SQLSTATE: 42P13
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06111 - GAUSS-06120
+
+<br/>
+
+GAUSS-06111: "the builtin function can not be renamed,its function oid is '%u'"
+
+SQLSTATE: 42P13
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06112: "function '%s' is a builtin function,its owner can not be changed"
+
+SQLSTATE: 42P13
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06113: "ownerId change failed for function %u, because it is a builtin function."
+
+SQLSTATE: 42P13
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06114: "function '%s' is a builtin function,it can not be altered"
+
+SQLSTATE: 42P13
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06115: "Do not support package for ALTER FUNCTION."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06116: "set return type failed for function %u, because it is a builtin function."
+
+SQLSTATE: 42P13
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06117: "set argument type failed for function %u, because it is a builtin function."
+
+SQLSTATE: 42P13
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06118: "namespace change failed for function %u, because it is a builtin function."
+
+SQLSTATE: 42P13
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06119: "expected none dependency record for partition's CUDesc/Delta table, found %ld"
+
+SQLSTATE: OP002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06120: "Failed on finding partitioned tuple!\n"
+
+SQLSTATE: XX005
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06121 - GAUSS-06130
+
+<br/>
+
+GAUSS-06121: "invalid nodeId: %s(%d)"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06123: "could not open relation %s(%u) on node %s."
+
+SQLSTATE: 42P01
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06124: "Both table should have the same hashbucket option(on or off)"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06125: "analyze prefetch block list can not be NULL"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06126: "records n should not be zero"
+
+SQLSTATE: 22012
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06127: "Multi-columns statistic does not support hist/corr/mcelem/dechist"
+
+SQLSTATE: 42P10
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06128: "COPY_OBS does not implement in CopySendEndOfRow"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06129: "could not get data from COPY source"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06130: "copy from stdin failed because receive close conn message type 0x%02X"
+
+SQLSTATE: 08P01
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06131 - GAUSS-06140
+
+<br/>
+
+GAUSS-06131: "Cannot use OS-reserved file as COPY destination."
+
+SQLSTATE: 42602
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06132: "COPY to or from a file is prohibited for security concerns"
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06133: "could not open header file '%s': %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06134: "'%s' is not a valid EOL string, EOL string must not be empty"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06134: "'%s' is not a valid EOL string, EOL string must not be empty"
+
+SQLSTATE: None
+
+Description: A custom line break cannot be empty.
+
+Solution: Ensure that the custom line break is not empty.
+
+GAUSS-06135: "'%s' is not a valid EOL string, EOL string must not exceed the maximum length (10 bytes)"
+
+SQLSTATE: None
+
+Description: The custom line break exceeds the maximum length (10 bytes).
+
+Solution: Shorten the custom line break.
+
+GAUSS-06136: "COPY delimiter cannot contain user-define EOL string"
+
+SQLSTATE: None
+
+Description: A delimiter cannot contain custom line breaks.
+
+Solution: Ensure that the delimiter does not contain custom line breaks.
+
+GAUSS-06137: "COPY null representation cannot contain user-define EOL string"
+
+SQLSTATE: None
+
+Description: The **NULL** value cannot contain custom line breaks.
+
+Solution: Ensure that the **NULL** value does not contain custom line breaks.
+
+GAUSS-06138: "EOL string '%s' cannot contain any characters in'%s'"
+
+SQLSTATE: None
+
+Description: A custom line break cannot contain specified characters.
+
+Solution: Ensure that the custom line break does not contain specified characters.
+
+GAUSS-06139: "EOL specification can not be used with non-text format using COPY FROM or READ ONLY foreign table"
+
+SQLSTATE: None
+
+Description: Custom line breaks cannot be used for non-TEXT data import using **COPY** or for read-only non-TEXT foreign tables.
+
+Solution: Ensure that the data to be imported using **COPY** and the read-only table are in TEXT format.
+
+GAUSS-06140: "EOL specification can not be used with non-text format using COPY TO or WRITE ONLY foreign table except 0x0D0A and 0x0A"
+
+SQLSTATE: None
+
+Description: Custom line breaks (excluding 0x0D0A and 0x0A) cannot be used for non-TEXT export using **COPY** or for write-only foreign tables.
+
+Solution: Ensure that the data to be exported using **COPY** and the write-only table are in TEXT format.
+
+<br/>
+
+## GAUSS-06141 - GAUSS-06150
+
+<br/>
+
+GAUSS-06141: "out_filename_prefix is only allowed in write-only foreign tables"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06142: "out_fix_alignment is only allowed in write-only foreign tables"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06143: "COPY does not support subtransactions or exceptions."
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06144: "must be system admin to execute 'COPY from log errors data' "
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06145: "Unable to open %s.%s table for COPY FROM error logging."
+
+SQLSTATE: 42704
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06146: "The column definition of %s.%s table is not as intended."
+
+SQLSTATE: OP001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06147: "Don't suppport COPY FROM table with INSERT triggers"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06148: "do not support system admin to COPY from %s"
+
+SQLSTATE: 42602
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06149: "bulkload illegal chars conversion is just allowed for char type attribute, the original character with byte sequence %s in encoding '%s' has no equivalent in encoding '%s'"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06150: "bulkload illegal chars conversion is just allowed for char type attribute, the original invalid byte sequence for encoding '%s': %s"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06151 - GAUSS-06160
+
+<br/>
+
+GAUSS-06151: "target of symbolic link '%s' doesn't exist."
+
+SQLSTATE: OP0A3
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06152: "GDS stream is null pointer, the dynamic cast failed"
+
+SQLSTATE: 29003
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06153: "GDS version does not match MogDB version."
+
+SQLSTATE: DB001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06154: "Abnormal data package received, package length is %d, input buffer length is %d"
+
+SQLSTATE: None
+
+Description: An abnormal data packet is received. The lengths of the data packet and the received buffer are displayed.
+
+Solution: Ensure that the data file is correct.
+
+GAUSS-06155: "Reject Limit , LOG ERRORS or LOG ERRORS DATA can only be used in COPY From Statements."
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06156: "Reject Limit must be used with LOG ERRORS or LOG ERRORS DATA."
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06157: "Error encountered while logging error into %s.%s."
+
+SQLSTATE: SP005
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06158: "the number of attributes is illegal"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06159: "index and table must be in the same schema"
+
+SQLSTATE: 55000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06160: "dfs value partition table does not support local partitioned indexes "
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06161 - GAUSS-06170
+
+<br/>
+
+GAUSS-06162: "It is not supported to create index on DFS tablespace."
+
+SQLSTATE: 42P17
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06163: "The operation of 'REINDEX INTERNAL TABLE %s PARTITION %s' failed. "
+
+SQLSTATE: 42P23
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06164: "The operation of 'REINDEX INTERNAL TABLE %s' on part '%u' failed. "
+
+SQLSTATE: 42P23
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06165: "The operation of 'REINDEX INTERNAL TABLE %s' failed. "
+
+SQLSTATE: XX002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06166: "The table '%s' doesn't support the operation of 'REINDEX INTERNAL TABLE'. There is no Desc table on it."
+
+SQLSTATE: 42P01
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06167: "Bypass process Failed"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06168: "uuids can not be NIL when generating uuid in restore mode."
+
+SQLSTATE: OP003
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06169: "Create table Like in multi-nodegroup is not supported"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06170: "Temporary sequences are not supported"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06171 - GAUSS-06180
+
+<br/>
+
+GAUSS-06171: "Invaild UUID for CREATE SEQUENCE %s."
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06172: "unrecognized sequence columns: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06173: "Sequence '%s' retry %d times to connect GTM on datanode %s"
+
+SQLSTATE: YY004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06174: "currval function is not supported"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06175: "lastval function is not supported"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06176: "'%s.%s' is not a sequence"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06177: "oldseqnamearg should not be null"
+
+SQLSTATE: XX005
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06178: "newseqnamearg should not be null"
+
+SQLSTATE: XX005
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06179: "Only support CREATE TRIGGER on regular row table."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06180: "Unsupport CREATE TRIGGER on table which is under cluster resizing."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06181 - GAUSS-06190
+
+<br/>
+
+GAUSS-06181: "invalid current user oid for trigger"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06182: "trigdesc should not be null"
+
+SQLSTATE: XX005
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06183: "invalid after-trigger event code: %u"
+
+SQLSTATE: 20000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06184: "unrecognized RI_FKey_trigger_type: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06185: "unrecognized node type when find the required outer rels for a bitmap tree: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06186: "unrecognized node type when find the required upper rels for a bitmap tree: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06187: "unrecognized node type when find indexpath quals: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06188: "wrong number of index expressions when match index to operand"
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06189: "unsupported indexqual type when expand indexqual conditions: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06190: "right operator can not be NULL"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06191 - GAUSS-06200
+
+<br/>
+
+GAUSS-06191: "unexpected strategy number %d when expand a single indexqual condition"
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06192: "when expand a single indexqual condition could not find commutator of member %d(%u,%u) of opfamily %u"
+
+SQLSTATE: D0011
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06193: "unexpected opfamily when generate indexqual condition by prefix quals: %u"
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06194: "unexpected const type when generate indexqual condition by prefix quals: %u"
+
+SQLSTATE: 20000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06195: "no < operator for opfamily %u when generate indexqual condition by prefix quals"
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06196: "unexpected operator when generate indexqual condition by network prefix quals: %u"
+
+SQLSTATE: 20000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06197: "no >= operator for opfamily %u when generate indexqual condition by network prefix quals"
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06198: "no > operator for opfamily %u when generate indexqual condition by network prefix quals"
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06199: "no <= operator for opfamily %u when generate indexqual condition by network prefix quals"
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06200: "unexpected rtekind: %d when set relation size"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/63-GAUSS-06201-GAUSS-06300.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/63-GAUSS-06201-GAUSS-06300.md
new file mode 100644
index 0000000000000000000000000000000000000000..d9c6310bd361dd7a3268c6c3c36172d2c8462f30
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/63-GAUSS-06201-GAUSS-06300.md
@@ -0,0 +1,924 @@
+---
+title: GAUSS-06201 - GAUSS-06300
+summary: GAUSS-06201 - GAUSS-06300
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-06201 - GAUSS-06300
+
+<br/>
+
+## GAUSS-06201 - GAUSS-06210
+
+<br/>
+
+GAUSS-06201: "failed on assertion in %s line %d : %s"
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06202: "unexpected rtekind when set relation path list: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06203: "All orientations are not covered."
+
+SQLSTATE: 20000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06204: "bad levelsup for CTE '%s' when set cte pathlist"
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06205: "could not find CTE '%s' when set cte pathlist"
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06206: "could not find plan for CTE '%s' when set cte pathlist"
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06207: "bad levelsup for CTE '%s' when set worktable pathlist"
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06208: "could not find plan for CTE '%s' when set worktable pathlist"
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06209: "unrecognized joinlist node type when build access paths by joinlist: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06210: "unrecognized node type when pushdown recurse through setOperations tree: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06211 - GAUSS-06220
+
+<br/>
+
+GAUSS-06211: "wrong number of tlist entries when compare a subquery targetlist datatypes"
+
+SQLSTATE: 20000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06212: "unrecognized node type when recurse push qual through setOperations tree: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06213: "unrecognized node type when create partiterator path: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06214: "Unsupported Using Index FOR TIMESERIES."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06215: "unrecognized node type of a bitmap index path when get pages: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06216: "unrecognized node type when extract cost and selectivity from a bitmap tree node: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06217: "left and right pathkeys do not match in mergejoin when initlize cost"
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06218: "cannot handle unplanned sub-select when costing quals"
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06219: "unrecognized join type when calculate joinrel size estimate: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06220: "unrecognized join type when match unsorted outer: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06221 - GAUSS-06230
+
+<br/>
+
+GAUSS-06221: "Null value error for building partitionwise join"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06222: "could not find opfamilies for equality operator %u when make pathkey from sortinfo"
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06223: "operator %u is not a valid ordering operator when make pathkey from sortinfo"
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06224: "volatile EquivalenceClass has no sortref when convert subquery pathkeys"
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06225: "too few pathkeys for mergeclauses when make inner pathkeys for merge"
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06226: "outer pathkeys do not match mergeclause when make inner pathkeys for merge"
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06227: "unrecognized join type when make a join rel: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06228: "Unsupported node type %s to check need stream setup for recursive union"
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06229: "encounters invalid varno"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06230: "invalid column number %d for table \n"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06231 - GAUSS-06240
+
+<br/>
+
+GAUSS-06231: "There is no exist vararrno with 0"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06232: "tle can not be found from targetlist"
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06233: "No data node information for table: %s"
+
+SQLSTATE: XX006
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06234: "No data node found for u_sess->pgxc_cxt.gc_fdw_current_idx: %d, u_sess->pgxc_cxt.gc_fdw_max_idx: %d"
+
+SQLSTATE: XX006
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06235: "Unsupported Table Sample FOR TIMESERIES."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06236: "Unsupported Index Scan FOR TIMESERIES."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06237: "Unsupported Bitmap Heap Scan FOR TIMESERIES."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06238: "Unsupported Bitmap And FOR TIMESERIES."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06239: "Unsupported Bitmap OR FOR TIMESERIES."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06240: "Unsupported Bitmap Index Scan FOR TIMESERIES."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06134: "'%s' is not a valid EOL string, EOL string must not be empty"
+
+SQLSTATE: None
+
+Description: A custom line break cannot be empty.
+
+Solution: Ensure that the custom line break is not empty.
+
+GAUSS-06135: "'%s' is not a valid EOL string, EOL string must not exceed the maximum length (10 bytes)"
+
+SQLSTATE: None
+
+Description: The custom line break exceeds the maximum length (10 bytes).
+
+Solution: Shorten the custom line break.
+
+GAUSS-06136: "COPY delimiter cannot contain user-define EOL string"
+
+SQLSTATE: None
+
+Description: A delimiter cannot contain custom line breaks.
+
+Solution: Ensure that the delimiter does not contain custom line breaks.
+
+GAUSS-06137: "COPY null representation cannot contain user-define EOL string"
+
+SQLSTATE: None
+
+Description: The **NULL** value cannot contain custom line breaks.
+
+Solution: Ensure that the **NULL** value does not contain custom line breaks.
+
+GAUSS-06138: "EOL string '%s' cannot contain any characters in'%s'"
+
+SQLSTATE: None
+
+Description: A custom line break cannot contain specified characters.
+
+Solution: Ensure that the custom line break does not contain specified characters.
+
+GAUSS-06139: "EOL specification can not be used with non-text format using COPY FROM or READ ONLY foreign table"
+
+SQLSTATE: None
+
+Description: Custom line breaks cannot be used for non-TEXT data import using **COPY** or for read-only non-TEXT foreign tables.
+
+Solution: Ensure that the data to be imported using **COPY** and the read-only table are in TEXT format.
+
+GAUSS-06140: "EOL specification can not be used with non-text format using COPY TO or WRITE ONLY foreign table except 0x0D0A and 0x0A"
+
+SQLSTATE: None
+
+Description: Custom line breaks (excluding 0x0D0A and 0x0A) cannot be used for non-TEXT export using **COPY** or for write-only foreign tables.
+
+Solution: Ensure that the data to be exported using **COPY** and the write-only table are in TEXT format.
+
+<br/>
+
+## GAUSS-06241 - GAUSS-06250
+
+<br/>
+
+GAUSS-06241: "unrecognized node type: %d when modify worktable wtParam."
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06242: "recursive_union_plan can not be NULL"
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06243: "non-LATERAL parameter required by subquery"
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06244: "unexpected type of subquery parameter"
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06245: "Unsupported Direct Scan FOR TIMESERIES."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06246: "fail to find TargetEntry referenced by SortGroupClause"
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06247: "Unsupported FOR UPDATE/SHARE system table."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06248: "Unsupported FOR UPDATE/SHARE in non shippable plan."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06249: "Only Scan operator have BucketInfo attribute"
+
+SQLSTATE: XX006
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06250: "Unsupported FOR UPDATE/SHARE at non-top-level query in stream plan."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06251 - GAUSS-06260
+
+<br/>
+
+GAUSS-06251: "Unsupported FOR UPDATE/SHARE with limit in stream plan."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06252: "Unsupported FOR UPDATE/SHARE multiple table in stream plan."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06253: "can not find var with varno = %u and varattno = %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06254: "qry_tle should not be null"
+
+SQLSTATE: XX005
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06255: "Partition column can't be updated in current version"
+
+SQLSTATE: 42P10
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06256: "Build subPlan failed.. "
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06257: "convert to SubPlan failed. "
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06258: "Fail to process sublinks mutator."
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06259: "Fail to get sort group clause."
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06260: "failed to find relation %d in joinlist when remove relation from joinlist"
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06261 - GAUSS-06270
+
+<br/>
+
+GAUSS-06261: "unrecognized joinlist node type when remove relation from joinlist: %d"
+
+SQLSTATE: XX006
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06262: "cheapest_total_path should not exist para_info"
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06263: "unrecognized node type when add base_rels to query: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06264: "unrecognized node type when add vars to targetlist: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06265: "expected Var or PlaceHolderVar, others unsupported. "
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06266: "unrecognized join type in one level processing of deconstruct jointree: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06267: "unrecognized node type in one level of deconstruct jointree: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06268: "cannot cope with variable-free clause when distribute restrictinfo to rels"
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06269: "relid must not be less than zero."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06270: "too many range table entries when set plan reference."
+
+SQLSTATE: 54000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06271 - GAUSS-06280
+
+<br/>
+
+GAUSS-06271: "targetlist of stream node with plan_node_id %d should be equal to its child's targetlist"
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06272: "unrecognized node type in set plan refs: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06273: "Could not find the Aggref node when setting agg plan refernece."
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06274: "Could not find the Aggref node when setting agg plan reference."
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06275: "mark_stream_unsupport."
+
+SQLSTATE: 0A100
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06276: "Fail to generate subquery plan."
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06277: "unrecognized node type when process qual condition: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06278: "unrecognized node type when get base relation indexes: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06279: "OBS and HDFS foreign table can NOT be in the same plan."
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06280: "pl_size should not be zero"
+
+SQLSTATE: 22012
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06281 - GAUSS-06290
+
+<br/>
+
+GAUSS-06281: "Failed to get the runtime info from the compute pool."
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06282: "version is not compatible between local cluster and the compute pool"
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06283: "There is no optional index path for index column: %s.\nPlease check for potential performance problem."
+
+SQLSTATE: 01000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06284: "MERGE INTO on replicated table does not yet support using distributed tables."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06285: "unrecognized bool test type: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06286: "RangeTblRef not found."
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06287: "Valid rel not found. "
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06288: "No Such Relation"
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06289: "subquery's setOperations tree should not be NULL in pull_up_simple_union_all"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06290: "jointree in subquery could not be NULL"
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06291 - GAUSS-06300
+
+<br/>
+
+GAUSS-06291: "Join range table do not have system column."
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06292: "Invalid join alias var"
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06293: "Invalid agg param which used in a join clause"
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06294: "Column should NOT be in JOIN clause."
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06295: "unsupported command type: %d."
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06296: "infinite recursion detected, please check the row level security policies for relation '%s'"
+
+SQLSTATE: 42P17
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06297: "could not convert table '%s' to a view because it has row level security enabled"
+
+SQLSTATE: 55000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06298: "could not convert table '%s' to a view because it has row level security policies"
+
+SQLSTATE: 55000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06299: "Fail to find base rel."
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06300: "predcate_classify returned a bogus value"
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/64-GAUSS-06301-GAUSS-06400.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/64-GAUSS-06301-GAUSS-06400.md
new file mode 100644
index 0000000000000000000000000000000000000000..15f83ac88d32b4bff1f627a6ebda855543972230
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/64-GAUSS-06301-GAUSS-06400.md
@@ -0,0 +1,860 @@
+---
+title: GAUSS-06301 - GAUSS-06400
+summary: GAUSS-06301 - GAUSS-06400
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-06301 - GAUSS-06400
+
+<br/>
+
+## GAUSS-06301 - GAUSS-06310
+
+<br/>
+
+GAUSS-06301: "invalid index oid to check for unusability"
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06302: "relation %s is not partitioned when check partition index"
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06303: "Could not find enough valid args for Boundary From OpExpr"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06304: "partSeq: %d out range of current relation partMap element num: %d."
+
+SQLSTATE: 2202E
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06305: "Duplicate range partition map oids: %u, please try again."
+
+SQLSTATE: 42710
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06306: "expected a RowCompareExpr for para clause"
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06307: "fail to eval const expressions."
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06308: "Fail to eval const expressoin."
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06309: "fail to eval const expressions. "
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06310: "Eval const expression mutator failed. "
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06311 - GAUSS-06320
+
+<br/>
+
+GAUSS-06311: "function '%s' doesn't exist"
+
+SQLSTATE: 42883
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06312: "function '%s' with %d parameters doesn't exist"
+
+SQLSTATE: 42883
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06313: "var on action's qual cannot find in target list"
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06314: "none_recursive_plan could not be NULL"
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06315: "outer_path and parent in outer_path could not be NULL"
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06316: "inner_path and parent in inner_path could not be NULL"
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06317: "Failed to get sort group clause. "
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06318: "buckets id %d of table '%s' is outsize range [%d,%d]"
+
+SQLSTATE: 22003
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06319: "%d of duplicate bucket id found"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06320: "No privilage assigned to user %u."
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06321 - GAUSS-06330
+
+<br/>
+
+GAUSS-06322: "Unexpected range table entry type."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06323: "exec_nodes could not be NULL"
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06324: "distribution could not be NULL"
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06325: "is_outer_replicated and is_inner_replicated could not all be false"
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06326: "[ng_get_single_dn_group_exec_node] unknown exec location."
+
+SQLSTATE: 2F000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06327: "Can not get valid skew value from hint."
+
+SQLSTATE: XX005
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06328: "Can not generate equal operation for non skew side."
+
+SQLSTATE: XX005
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06329: "Invalid skew stream type %d."
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06330: "Expected positive width estimation."
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06331 - GAUSS-06340
+
+<br/>
+
+GAUSS-06331: "child rel %u not found in append_rel_list"
+
+SQLSTATE: XX008
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06332: "source '%s' does not exist"
+
+SQLSTATE: 42704
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06333: "global prepared statement '%s' does not exist in PrepareFetch GPC (%ld,%d,%d) dn session_id:%lu"
+
+SQLSTATE: 26000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06334: "store global plan source failed due to memory allocation failed"
+
+SQLSTATE: 26000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06335: "refuse to activate a job since illegal element in ExpiredJobList."
+
+SQLSTATE: 29000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06336: "no free slot when start job worker"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06337: "XuanYuanDB current do not support AIO"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06338: "could not request checkpoint because checkpointer not running"
+
+SQLSTATE: 44000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06339: "could not signal for checkpoint: %m"
+
+SQLSTATE: 44000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06340: "remote service port not available"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06341 - GAUSS-06350
+
+<br/>
+
+GAUSS-06341: "No data left in msg, left len:%u, desire len:%lu"
+
+SQLSTATE: 08P01
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06342: "No data left in msg, left len:%u"
+
+SQLSTATE: 08P01
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06343: "could not create Unix-domain socket: %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06344: "bind socket path %s failed:%m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06345: "listen socket failed: %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06346: "poll() failed in UDFMasterServerLoop, errno:%d, error reason:%s"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06347: "Socket send %d bytes: %m"
+
+SQLSTATE: 08006
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06348: "Invalid udf message len:%u"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06349: "create UDFWorkMemContext failed"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06350: "Otherwise, handlerType can only be UDF_RECV_RESULT"
+
+SQLSTATE: 29003
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06351 - GAUSS-06360
+
+<br/>
+
+GAUSS-06351: "Variable length %d cannot be negative"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06352: "Recv Unsupported argument type: %u"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06353: "Unsupport type: %u"
+
+SQLSTATE: 42804
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06354: "null prosrc for Java function %u"
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06355: "Run udf RPC connect failed: %m"
+
+SQLSTATE: 08006
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06356: "UDF Error:%s"
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06357: "internal_load_library %s failed: %m"
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06358: "load java_call_handler failed."
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06359: "UnixSocketDir is not valid, length is between 1 and %lu: %s/%s"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06360: "Invalid parameter."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06361 - GAUSS-06370
+
+<br/>
+
+GAUSS-06361: "execute cmd %s fail."
+
+SQLSTATE: XX005
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06362: "Can not read process num."
+
+SQLSTATE: XX005
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06363: "Contains invaid character: '%s'"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06364: "Invalid argument: should appoint an option of ls, addjar or rmjar."
+
+SQLSTATE: XX005
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06365: "Invalid argument: only support ls, addjar, rmjar options."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06366: "filepath should not be NULL"
+
+SQLSTATE: XX005
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06367: "Invalid argument: must set correct obs file path."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06368: "Invalid argument: must set accesskey."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06369: "Invalid argument: must set secretkey."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06370: "Invalid argument: must set region."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06371 - GAUSS-06380
+
+<br/>
+
+GAUSS-06371: "Invalid argument: must set a 'libraryname'."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06372: "Invalid argument: 'libraryname' should not contain '/' or starting with '.'."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06373: "Invalid argument: must set an absolute path followed by 'file:///'."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06374: "Invalid argument: the source file must be .jar file."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06375: "Invalid argument: must set bucket and filepath followed by 'obs://'."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06376: "must set correct source file path."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06377: "Invalid argument: the library already existed, please remove it first using rmjar."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06378: "%d %d: System error."
+
+SQLSTATE: 58000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06379: "%d: Failed to access system files."
+
+SQLSTATE: 2F000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06380: "%d: Invalid argument, must set correct region."
+
+SQLSTATE: 2F000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06381 - GAUSS-06390
+
+<br/>
+
+GAUSS-06381: "%d: Parameters error."
+
+SQLSTATE: 2F000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06382: "%d: Failed to connect to obs server."
+
+SQLSTATE: 08006
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06383: "%d: Failed to download from obs server."
+
+SQLSTATE: 2F000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06384: "%d: Obs server is busy. Try again later."
+
+SQLSTATE: 08006
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06385: "%d: Download failed."
+
+SQLSTATE: 2F000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06386: "execute command failed"
+
+SQLSTATE: 2F000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06387: "must be system admin to use the gs_extend_library function"
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06388: "Invaid argument: must at least set libraryname"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06389: "System Error."
+
+SQLSTATE: 58000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06390: "Invalid argument: must set correct bucket and obs file path."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06391 - GAUSS-06400
+
+<br/>
+
+GAUSS-06391: "the move_loc buffer should be invalid."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06392: "Integer overflow when update database-wid stats"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06393: "Failed to get database-wide stats."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06394: "timed_checkpoints overflow"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06395: "requested_checkpoints overflow"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06396: "checkpoint_write_time overflow"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06397: "checkpoint_sync_time overflow"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06398: "buf_written_checkpoints overflow"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06399: "buf_written_clean overflow"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06400: "maxwritten_clean overflow"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/65-GAUSS-06401-GAUSS-06500.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/65-GAUSS-06401-GAUSS-06500.md
new file mode 100644
index 0000000000000000000000000000000000000000..5925938ab690fd759ef2bf287cbd265ba4bf97f7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/65-GAUSS-06401-GAUSS-06500.md
@@ -0,0 +1,788 @@
+---
+title: GAUSS-06401 - GAUSS-06500
+summary: GAUSS-06401 - GAUSS-06500
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-06401 - GAUSS-06500
+
+<br/>
+
+## GAUSS-06401 - GAUSS-06410
+
+<br/>
+
+GAUSS-06401: "buf_written_backend overflow"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06402: "buf_fsync_backend overflow"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06403: "buf_alloc overflow"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06404: "unrecognized bypass recovery conflict reason: %d"
+
+SQLSTATE: 20000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06405: "Invalid database num:%u"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06406: "Unable to connect to execute internal query."
+
+SQLSTATE: OP001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06407: "fail to execute query"
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06408: "toast table map hash table corrupted."
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06409: "AutoVacuum Data share mem is already init"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06410: "file_size is invalid:[%ld]"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06411 - GAUSS-06420
+
+<br/>
+
+GAUSS-06411: "process suicides because the victim of lwlock deadlock is an auxiliary thread"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06412: "syslogger could not open file %d: %m,exit\n"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06413: "terminate because pooler connect timeout(%ds) when process startup packet"
+
+SQLSTATE: 57014
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06414: "pg_strdup: cannot duplicate null pointer (internal error)\n"
+
+SQLSTATE: D0011
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06415: "out of memory\n"
+
+SQLSTATE: 58000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06416: "the options of -n is deprecated"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06417: "the options of -T is deprecated"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06418: "Single node mode: must start as single node (-single_node)\n"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06419: "could not create listen socket for '%s:%d'"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06420: "pooler_port must equal to gsql listen port plus one!"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06421 - GAUSS-06430
+
+<br/>
+
+GAUSS-06421: "could not create ha listen socket for '%s:%d'"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06422: "could not create Ha listen socket for ReplConnInfoArr[%d]'%s:%d'"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06423: "could not create Unix-domain socket for '%s:%d'"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06424: "Init libcomm for stream failed, maybe listen port already in use"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06425: "WAL streaming (max_wal_senders > 0) requires wal_level 'archive', 'hot_standby' or 'logical'"
+
+SQLSTATE: 58000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06426: "invalid value[%d] for parameter 'connect_timeout'"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06427: "no pg_hba.conf entry for host '%s'."
+
+SQLSTATE: 28000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06428: "when replconn port equals gsql port plus one, listen_addresses can not contain '*'"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06429: "set basic info of stream failed!"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06430: "could not set WorkingGrandVersionNum manually while not performing upgrade"
+
+SQLSTATE: D0011
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+<br/>
+
+## GAUSS-06431 - GAUSS-06440
+
+<br/>
+
+GAUSS-06431: "wrong environment variable '%s'"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06432: "unrecorgnized proc type %d"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06433: "create timer fail at thread : %lu"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06434: "unsupport thread role type %d"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06435: "must be superuser account to perform disable_conn()"
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06436: "Connection mode should be polling_connection or specify_connection or prohibit_connection"
+
+SQLSTATE: D0011
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06437: "could not add lock when DN is not redo all xlog, redo done flag is false"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06438: "could not add lock when DN is not redo all xlog."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06439: "Invalid null pointer attribute for disable_conn()"
+
+SQLSTATE: 42P24
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06440: "host is invalid"
+
+SQLSTATE: D0011
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+<br/>
+
+## GAUSS-06441 - GAUSS-06450
+
+<br/>
+
+GAUSS-06441: "Can't get local connection address."
+
+SQLSTATE: 42804
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06442: "get local host failed!"
+
+SQLSTATE: 42804
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06443: "get local port failed!"
+
+SQLSTATE: 42804
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06444: "cannot read disable connection file: '%s' \n"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06445: "sql retrying routine off the track."
+
+SQLSTATE: 2F000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06446: "%s %s do stub test '%c'"
+
+SQLSTATE: XX015
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06447: "%s ecode stub test raise error %s"
+
+SQLSTATE: # thi
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06448: "invalid argument count %d in function call message"
+
+SQLSTATE: 08P01
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06449: "func_id not valid in %s line %d"
+
+SQLSTATE: 42883
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06450: "function call message supplies invalid numAFormats %d"
+
+SQLSTATE: 08P01
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+<br/>
+
+## GAUSS-06451 - GAUSS-06460
+
+<br/>
+
+GAUSS-06457: "Unable to create table on old installation group '%s' while in cluster resizing."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06458: "Current Node is not active"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06459: "commit xid %lu is not equal to the excute one %lu."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06460: "abort xid %lu is not equal to the former one %lu."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+<br/>
+
+## GAUSS-06461 - GAUSS-06470
+
+<br/>
+
+GAUSS-06461: "Current mode does not support FOREIGN table yet"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06462: "Current mode does not support FOREIGN server yet"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06463: "NOT-SUPPORT: Not support DROP multiple objects different nodegroup"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06464: "permission denied to drop foreign table in security mode"
+
+SQLSTATE: 42501
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06465: "foreign table '%s.%s' does not exist"
+
+SQLSTATE: 42P01
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06466: "NOT-SUPPORT: Not support DROP multiple functions in different nodegroup"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06467: "operation copy with file is forbidden in security mode."
+
+SQLSTATE: D0011
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06468: "NOT-SUPPORT: Not support Grant/Revoke privileges to objects in different nodegroup"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06469: "user defined range type is not yet supported."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+ACTION: Contact technical support.
+
+<br/>
+
+## GAUSS-06471 - GAUSS-06480
+
+<br/>
+
+GAUSS-06471: "This relation doesn't support analyze with column."
+
+SQLSTATE: 42P01
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06473: "Invalid value '%s' in WITH clause"
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06474: "Don't support node group in single_node mode."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06476: "%s can not run inside a transaction block"
+
+SQLSTATE: 25001
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06478: "unrecognized portal strategy: %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06479: "cursor can only scan forward"
+
+SQLSTATE: 55000
+
+Description: The NO SCROLL option is explicitly specified or the current execution plan does not support backward scan.
+
+Solution: If NO SCROLL is explicitly specified, delete it. If the current execution plan is not supported, adjust the execution plan.
+
+GAUSS-06480: "Cursor rewind are not supported."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06481 - GAUSS-06490
+
+<br/>
+
+GAUSS-06481: "Invaild parameter."
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06482: "Could not find \'}\' in the query string."
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06483: "unexpect list length %d of mem_list from info_query_string."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06484: "analyzeNode is null."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06485: "node n is null."
+
+SQLSTATE: XX001
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06486: "Invaild UUID Message for CREATE SEQUENCE."
+
+SQLSTATE: XX001
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06487: "Not enough UUID (%d/%d) in CREATE SEQUENCE."
+
+SQLSTATE: XX001
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06488: "Invaild UUID Message while CREATE SEQUENCE by serial."
+
+SQLSTATE: XX001
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06489: "Too long plan_string."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Please contact engineer to support."
+
+GAUSS-06490: "Received unexpected node type."
+
+SQLSTATE: XX006
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+<br/>
+
+## GAUSS-06491 - GAUSS-06500
+
+<br/>
+
+GAUSS-06491: "rel_loc_info is NULL."
+
+SQLSTATE: 58000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06492: "The current node should not receive z messages"
+
+SQLSTATE: 58030
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06493: "portal_name or stmt_name is null."
+
+SQLSTATE: XX001
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06494: "Too long portal_name and stmt_name."
+
+SQLSTATE: 08P01
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06495: "stmts is not NULL"
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06496: "terminating data redistribution process due to administrator command"
+
+SQLSTATE: 57P01
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06497: "terminating snapshot process due to administrator command"
+
+SQLSTATE: 57P01
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06498: "detach and reaper session from thread due to session connection lost"
+
+SQLSTATE: 57014
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06499: "terminate because authentication timeout(%ds)"
+
+SQLSTATE: 57014
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06500: "terminate because cancel interrupts"
+
+SQLSTATE: 57014
+
+Description: Internal system error.
+
+Solution: Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/66-GAUSS-06501-GAUSS-06600.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/66-GAUSS-06501-GAUSS-06600.md
new file mode 100644
index 0000000000000000000000000000000000000000..8f66594f4c2c9e17c042844e3a254edd6e34030d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/66-GAUSS-06501-GAUSS-06600.md
@@ -0,0 +1,868 @@
+---
+title: GAUSS-06501 - GAUSS-06600
+summary: GAUSS-06501 - GAUSS-06600
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-06501 - GAUSS-06600
+
+<br/>
+
+## GAUSS-06501 - GAUSS-06510
+
+<br/>
+
+GAUSS-06501: "canceling statement due to %s.%s"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06502: "canceling statement due to %s"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution:Please contact engineer to support."
+
+GAUSS-06503: "canceling data redistribution task"
+
+SQLSTATE: 57014
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06504: "canceling statement due to failover, pending"
+
+SQLSTATE: 08000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06505: "canceling snapshot task"
+
+SQLSTATE: 57014
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06506: "Postgres-XC: must start as either a Coordinator (-coordinator) or Datanode (-datanode)\n"
+
+SQLSTATE: 42601
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06507: "Cannot execute DDL in a transaction block when need reconnect pooler"
+
+SQLSTATE: 25001
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06508: "invalid number of data nodes when initializing global node definition."
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06509: "invalid frontend message type '%c'."
+
+SQLSTATE: 08P01
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06510: "query_string is NULL."
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+<br/>
+
+## GAUSS-06511 - GAUSS-06520
+
+<br/>
+
+GAUSS-06511: "Too long query_string."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06512: "Invalid packet path, remoteConnType[%d], remote_host[%s], remote_port[%s]."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06513: "Acceptter in pooler stateless resue mode reset connection params %d > sql[%d]."
+
+SQLSTATE: 58000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06514: "Too long schema_name."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06515: "The overrideStack list has been reach the max length."
+
+SQLSTATE: 08P01
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06516: "Invalid message type %d for procedure overrideStack."
+
+SQLSTATE: 08P01
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06517: "invalid execute message"
+
+SQLSTATE: 08P01
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06518: "Too long close_target."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06519: "invalid describe message"
+
+SQLSTATE: 08P01
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06520: "gtm mode unconsistency, remote mode is %s, local mode is %s."
+
+SQLSTATE: 58000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+<br/>
+
+## GAUSS-06521 - GAUSS-06530
+
+<br/>
+
+GAUSS-06521: "Received an invalid commit csn: %lu."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06522: "Need to set support_batch_bind=true if executing batch"
+
+SQLSTATE: 58000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06523: "Portal run not complete for one in Batch bind-execute: name %s, query %s"
+
+SQLSTATE: 58000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06524: "Batch param of distribute key only support const"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06525: "Failed to get DataNode id for Batch bind-execute: name %s, query %s"
+
+SQLSTATE: 58000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06526: "unexpected batch_count %d get from inputmessage"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06527: "unexpected maxlen %d "
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06528: "Batch bind-execute message with invalid batch count: %d"
+
+SQLSTATE: 08P01
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06529: "Not support portal_name %s for Batch bind-execute."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06530: "Batch bind-execute message with invalid parameter number: %d"
+
+SQLSTATE: 08P01
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+<br/>
+
+## GAUSS-06531 - GAUSS-06540
+
+<br/>
+
+GAUSS-06531: "conflict stmt name in Batch bind-execute message: bind %s, describe %s"
+
+SQLSTATE: 08P01
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06532: "conflict portal name in Batch bind-execute message: bind %s, describe %s"
+
+SQLSTATE: 08P01
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06533: "invalid DESCRIBE message subtype in Batch bind-execute message: %d"
+
+SQLSTATE: 08P01
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06534: "conflict portal name in Batch bind-execute message: bind %s, execute %s"
+
+SQLSTATE: 08P01
+
+Description:Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06535: "Not support max_row in Batch bind-execute message: %d"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06536: "invalid value in Batch bind-execute message: %d"
+
+SQLSTATE: 08P01
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06537: "No thread pool worker left while waiting for session close. This is a very rare case when all thread pool workers happen to encounter FATAL problems before session close."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06538: "epoll receive %d events which exceed the limitation %d"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06539: "Exceed stream thread pool limitation %d in group %d"
+
+SQLSTATE: 58000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06540: "Fail to find a free slot for stream"
+
+SQLSTATE: 53000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+<br/>
+
+## GAUSS-06541 - GAUSS-06550
+
+<br/>
+
+GAUSS-06541: "Unexpected receive proc signal."
+
+SQLSTATE: 08000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06542: "receive more connection message %d than expect %d"
+
+SQLSTATE: 08P01
+
+Description:Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06543: "undefined state %d for session attach"
+
+SQLSTATE: 42P24
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06544: "memory usage reach the max_dynamic_memory"
+
+SQLSTATE: YY006
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06545: "Invalid attribute for thread pool."
+
+SQLSTATE: OP0A3
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06546: "Unsupported LLVM report type!"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06547: "Cannot get the llvm::Intrinsic::smul_with_overflow function!"
+
+SQLSTATE: CG002
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06548: "Failed on getting IR function : LLVMIRbpcharne!\n"
+
+SQLSTATE: CG001
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06549: "Cannot get the llvm::Intrinsic::sasub_with_overflow function!\n"
+
+SQLSTATE: CG002
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06550: "Failed on getting IR function : LLVMIRtextlike!\n"
+
+SQLSTATE: CG001
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+<br/>
+
+## GAUSS-06551 - GAUSS-06560
+
+<br/>
+
+GAUSS-06551: "Failed on getting IR function : LLVMIRtextnlike!\n"
+
+SQLSTATE: CG001
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06552: "Unexpected NULL right operator!"
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06553: "Failed to get function Intrinsic::prefetch!\n"
+
+SQLSTATE: CG002
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06154: "Abnormal data package received, package length is %d, input buffer length is %d"
+
+SQLSTATE: None
+
+Description: An abnormal data packet is received. The lengths of the data packet and the received buffer are displayed.
+
+Solution: Ensure that the data file is correct.
+
+GAUSS-06555: "Failed to get the const node of the operation!\n"
+
+SQLSTATE: XX005
+
+Description:Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06556: "Failed on getting IR function : LLVMIRbpchareq!"
+
+SQLSTATE: CG001
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06557: "unrecognized booltexttype: %d"
+
+SQLSTATE: XX004
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06558: "Failed on getting IR function : LLVMIRmemcmp!\n"
+
+SQLSTATE: CG001
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06559: "Codegen failed on the procedure of ExecVecTargetList!"
+
+SQLSTATE: CG000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06560: "Not supported expr node %d yet!"
+
+SQLSTATE: XX004
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+<br/>
+
+## GAUSS-06561 - GAUSS-06570
+
+<br/>
+
+GAUSS-06561: "Unexpected batch information from ExprContext."
+
+SQLSTATE: XX006
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06562: "Codegen keyMatch failed: unsupported data type!\n"
+
+SQLSTATE: 42804
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06563: "Failed to get inner hash key!"
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06564: "Failed to get outer hash key!"
+
+SQLSTATE: XX005
+
+Description:Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06565: "Codegen keyMatch failed for %d-th clause of hash join!\n"
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06566: "Codegen fast keyMatch failed: unsupported data type!\n"
+
+SQLSTATE: 42804
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06567: "Codegen buildHashTable failed: unsupported data type!\n"
+
+SQLSTATE: 42804
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06568: "Codegen probeHashTable failed: unsupported data type!\n"
+
+SQLSTATE: 42804
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06569: "Unsupported operation %u in FastAgg."
+
+SQLSTATE: XX004
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06570: "Failed on generating HashBatchCodeGen!\n"
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+<br/>
+
+## GAUSS-06571 - GAUSS-06580
+
+<br/>
+
+GAUSS-06571: "Failed on generating MatchOneKey Function!\n"
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06572: "Unexpected NULL project information."
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06573: "Unsupported agg function %u!"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06574: "Type %u is not supported yet in hashBatch"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06575: "Type %u is not supported yet in match_key"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06576: "Unexpected operation %u!"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06577: "Cannot get the llvm::Intrinsic::sadd_with_overflow function!"
+
+SQLSTATE: CG002
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06578: "Invalid LLVM type %d"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06579: "unrecognized node type: %d when rescan"
+
+SQLSTATE: XX004
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06580: "unrecognized node type: %d when restore scan position"
+
+SQLSTATE: XX004
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+<br/>
+
+## GAUSS-06581 - GAUSS-06590
+
+<br/>
+
+GAUSS-06581: "cache lookup failed for relation %u when check backward scan for Index."
+
+SQLSTATE: 29P01
+
+Description:Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06582: "cache lookup failed for access method %u when test backward scan for Index %s"
+
+SQLSTATE: 29P01
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06583: "cursor '%s' does not exist when executing Current Of Expr."
+
+SQLSTATE: 34000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06584: "cursor '%s' is not positioned on a row when the cursor uses for UPDATE/SHARE"
+
+SQLSTATE: 24000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06585: "cursor '%s' is not positioned on a row when the cursor doesn't use for UPDATE/SHARE"
+
+SQLSTATE: 24000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06586: "could not find hash function for hash operator %u for TupleHashTable, column number %d, total column number %d."
+
+SQLSTATE: 42883
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06587: "invalid node identifier for update/delete"
+
+SQLSTATE: 42704
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06588: "unrecognized result from subplan for BitmapAnd."
+
+SQLSTATE: XX004
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06589: "unrecognized result from subplan for BitmapHeapScan."
+
+SQLSTATE: XX004
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06590: "prefetch and main iterators are out of sync for BitmapHeapScan."
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+<br/>
+
+## GAUSS-06591 - GAUSS-06600
+
+<br/>
+
+GAUSS-06591: "can't initialize bitmap index scans using unusable index '%s'"
+
+SQLSTATE: XX002
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06592: "no local indexes found for partition %s BitmapIndexScan"
+
+SQLSTATE: 42809
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06593: "can't initialize bitmap index scans using unusable local index '%s' for partition"
+
+SQLSTATE: XX002
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06594: "unrecognized result from BitmapIndexScan subplan when execute BitmapOr"
+
+SQLSTATE: XX004
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06595: "unrecognized result from non-BitmapIndexScan subplan when execute BitmapOr"
+
+SQLSTATE: XX004
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06596: "ExtensibleNodeMethods '%s' was not registered"
+
+SQLSTATE: 42704
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06597: "unrecognized join type: %d for hashjoin"
+
+SQLSTATE: XX004
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06598: "could not write hashvalue %u to hash-join temporary file, written length %lu."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06599: "could not write tuple to hash-join temporary file: written length %lu, tuple length %u"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06600: "could not read from hash-join temporary file: read length %zu"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution: Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/67-GAUSS-06601-GAUSS-06700.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/67-GAUSS-06601-GAUSS-06700.md
new file mode 100644
index 0000000000000000000000000000000000000000..81c74233706bedd77cb509b0623d2b4171ec088a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/67-GAUSS-06601-GAUSS-06700.md
@@ -0,0 +1,868 @@
+---
+title: GAUSS-06601 - GAUSS-06700
+summary: GAUSS-06601 - GAUSS-06700
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-06601 - GAUSS-06700
+
+<br/>
+
+## GAUSS-06601 - GAUSS-06610
+
+<br/>
+
+GAUSS-06601: "The hash-join temporary file is corrupted,hashvalue:%u, length:%u."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06602: "could not read from hash-join temporary file(t_len:%u,nread:%lu): %m"
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06603: "can't initialize index-only scans using unusable index '%s'"
+
+SQLSTATE: XX002
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06604: "can't initialize index-only scans using unusable local index '%s'"
+
+SQLSTATE: XX002
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06605: "unrecognized join type: %d when initializing nestLoop"
+
+SQLSTATE: XX004
+
+Description: Internal system error.
+
+Solution:Please contact engineer to support."
+
+GAUSS-06606: "TABLESAMPLE REPEATABLE parameter cannot be null"
+
+SQLSTATE: 29002
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06607: "sample percentage must be between 0 and 100"
+
+SQLSTATE: 29001
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06608: "invalid operation %d on partition for seqscan, allowed are UPDATE/DELETE/SELECT"
+
+SQLSTATE: D0011
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06609: "unrecognized set op: %d when seting the count of output."
+
+SQLSTATE: XX004
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06610: "MPP with-recursive, globalStreamNodeGroup is not found in Node:[%d]"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+<br/>
+
+## GAUSS-06611 - GAUSS-06620
+
+<br/>
+
+GAUSS-06611: "stop scan the work table due to transaction aborted and vfd invalidated"
+
+SQLSTATE: 57P05
+
+Description: Internal system error.
+
+Solution:Please contact engineer to support."
+
+GAUSS-06612: "MPP With-Recursive sync controller for RecursiveUnion[%d] is not found"
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06613: "[LIGHT PROXY] Failed to get pooled connections from %s[%u]"
+
+SQLSTATE: 08006
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06614: "[LIGHT PROXY] Failed to send parse to %s[%u]"
+
+SQLSTATE: 08000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06615: "[LIGHT PROXY] Failed to get new transaction id"
+
+SQLSTATE: 08000
+
+Description: Internal system error.
+
+Solution:Please contact engineer to support."
+
+GAUSS-06616: "[LIGHT PROXY] Failed to send gxid %lu to %s[%u]"
+
+SQLSTATE: 08000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06617: "[LIGHT PROXY] Failed to send timestamp to %s[%u]"
+
+SQLSTATE: 08000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06618: "[LIGHT PROXY] Failed to send internal begin to %s[%u]"
+
+SQLSTATE: 08000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06619: "[LIGHT PROXY] Failed to send cid to %s[%u]"
+
+SQLSTATE: 08000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06620: "[LIGHT PROXY] Failed to send snapshot to %s[%u]"
+
+SQLSTATE: 08000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+<br/>
+
+## GAUSS-06621 - GAUSS-06630
+
+<br/>
+
+GAUSS-06621: "[LIGHT PROXY] Failed to send cgroup to %s[%u]"
+
+SQLSTATE: 08000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06622: "[LIGHT PROXY] Failed to send query id to %s[%u]"
+
+SQLSTATE: 08000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06623: "[LIGHT PROXY] Failed to send unique sql id to %s[%u]"
+
+SQLSTATE: 08000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06624: "INSERT ON DUPLICATE KEY UPDATE must have an transformed InsertStmt query."
+
+SQLSTATE: XX008
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06625: "invalid msgType %d for process message \n"
+
+SQLSTATE: 20000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06626: "[LIGHT PROXY] Failed to fetch from Datanode %u"
+
+SQLSTATE: 08006
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06627: "[LIGHT PROXY] Unexpected response from %s[%u]"
+
+SQLSTATE: 08000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06628: "[LIGHT PROXY] Failed to send global sess id to Datanode %u"
+
+SQLSTATE: 57P03
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06629: "[LIGHT PROXY] Failed to send sync to %s[%u]"
+
+SQLSTATE: 08000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06630: "CTE subplans should not be executed"
+
+SQLSTATE: 23514
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+<br/>
+
+## GAUSS-06631 - GAUSS-06640
+
+<br/>
+
+GAUSS-06631: "unrecognized testexpr type: %d in a hash subplan"
+
+SQLSTATE: XX004
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06632: "could not find compatible hash operator for operator %u for subplan"
+
+SQLSTATE: 42883
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06633: "could not find hash function for hash operator %u for subplan"
+
+SQLSTATE: 42883
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06634: "CTE subplans should not be executed when execute subplan"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06635: "could not identify CTID expression, %s"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06636: "cache lookup failed for aggregate function %u"
+
+SQLSTATE: 29P01
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06637: "unrecognized node type: %d when executing executor node."
+
+SQLSTATE: XX004
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06638: "unsupport bypass indexqual type: %d"
+
+SQLSTATE: XX004
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06639: "wrong input for router"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06640: "cannot find valid relation oid from router table_name"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+<br/>
+
+## GAUSS-06641 - GAUSS-06650
+
+<br/>
+
+GAUSS-06641: "invalid relation locator info from router table_name"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06642: "only support hash or modulo locator type, the relation locator type for router is %c\n"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06643: "input key number cannot match distribute keys on table %s"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06644: "invalid node id get from input key"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06645: "cannot get result from tuplestore for WinwdowsAgg"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06646: "cache lookup failed for aggregate %u of WindowsAgg"
+
+SQLSTATE: 29P01
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06647: "cache lookup failed for function %u of WindowsAgg in pg_proc"
+
+SQLSTATE: 29P01
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06648: "cannot get result from tuplestore in WindowsAgg."
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06649: "unrecognized window seek type: %d on a specified row of partition."
+
+SQLSTATE: XX004
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06650: "window object is invalid"
+
+SQLSTATE: 22000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+<br/>
+
+## GAUSS-06651 - GAUSS-06660
+
+<br/>
+
+GAUSS-06651: "unrecognized window seek type: %d on a specified row of window frame"
+
+SQLSTATE: XX004
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06652: "Both cacheplan and planstmt are NULL"
+
+SQLSTATE: 26000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06653: "unrecognized bypass support process option: %d"
+
+SQLSTATE: 20000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06654: "r_formats can not be NULL when num of rformats is not 0"
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06655: "unmatched parameter number"
+
+SQLSTATE: 26000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06656: "unexpected node type: %d when processing bypass expression."
+
+SQLSTATE: XX004
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06657: "unexpected arg length : %d when processing bypass expression."
+
+SQLSTATE: XX004
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06658: "unrecognized bypass support number of arguments function calls: %d"
+
+SQLSTATE: 20000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06659: "Invaild Oid when open hash bucket relation."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06660: "Invaild hash bucket oid from current tuple for update."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+<br/>
+
+## GAUSS-06661 - GAUSS-06670
+
+<br/>
+
+GAUSS-06661: "Invaild hash bucket oid from current tuple for delete."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06662: "Invaild hash bucket oid from current tuple for lock."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06663: "upper and lower index lists are not same length (%d, %d)"
+
+SQLSTATE: 2202E
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06664: "a NULL isNull pointer was passed when get attribute by number."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06665: "invalid null attribute name"
+
+SQLSTATE: 42602
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06666: "a NULL isNull pointer was passed when get attribute by name."
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06667: "function doesn't exist "
+
+SQLSTATE: 42883
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06668: "The input function expression is NULL."
+
+SQLSTATE: 22004
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06669: "unrecognized XML operation %d"
+
+SQLSTATE: XX004
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06670: "unrecognized node type: %d when initializing expression."
+
+SQLSTATE: XX004
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+<br/>
+
+## GAUSS-06671 - GAUSS-06680
+
+<br/>
+
+GAUSS-06671: "set-valued function called in context when calculate targetlist that cannot accept a set"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06672: "failed to fetch conflicting tuple for DUPLICATE KEY UPDATE"
+
+SQLSTATE: 40001
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06673: "ON DUPLICATE KEY UPDATE command cannot affect row a second time"
+
+SQLSTATE: 40001
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06674: "unexpected self-updated tuple"
+
+SQLSTATE: 40001
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06675: "unexpected concurrent update tuple"
+
+SQLSTATE: 40001
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06676: "ON DUPLICATE KEY UPDATE is not supported on column orientated table"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06677: "ON DUPLICATE KEY UPDATE is not supported on DFS table"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06678: "delete conflict in delta table cstore.%s"
+
+SQLSTATE: 42P28
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06679: "unable to get a stable set of rows in the source tables"
+
+SQLSTATE: P0003
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06680: "update conflict in delta table cstore.%s"
+
+SQLSTATE: 42P28
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+<br/>
+
+## GAUSS-06681 - GAUSS-06690
+
+<br/>
+
+GAUSS-06681: "unknown operation %d when process BEFORE EACH STATEMENT triggers"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06682: "unknown operation %d when process AFTER EACH STATEMENT triggers"
+
+SQLSTATE: XX004
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06683: "junkfilter should not be NULL"
+
+SQLSTATE: 22004
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06684: "ctid is NULL when do operation %d, junk attribute number is %d"
+
+SQLSTATE: XX007
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06685: "bucketid is null when update table"
+
+SQLSTATE: XX007
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06686: "wholerow is NULL when do operation %d, junk attribute number is %d"
+
+SQLSTATE: XX007
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06687: "unknown operation %d when execute the required table modification."
+
+SQLSTATE: XX004
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06688: "Unsupport 'MERGE INTO' command during online expansion on '%s'"
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06689: "could not find junk tableoid column for partition table."
+
+SQLSTATE: 42P24
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06690: "could not find junk bucketid column for bucketed table."
+
+SQLSTATE: 42P24
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+<br/>
+
+## GAUSS-06691 - GAUSS-06700
+
+<br/>
+
+GAUSS-06691: "tableoid is NULL when try to lock current row."
+
+SQLSTATE: XX007
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06692: "bucketid is NULL when try to lock current row."
+
+SQLSTATE: XX007
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06693: "unrecognized heap_lock_tuple status: %u when lock a tuple"
+
+SQLSTATE: XX004
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06694: "ExecLockRows:target relation cannot be NULL for plan qual recheck."
+
+SQLSTATE: 40001
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06695: "unrecognized bypass support type: %d"
+
+SQLSTATE: XX004
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06696: "tableoid is null when merge partitioned table"
+
+SQLSTATE: XX007
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06697: "bucketid is null when merge table"
+
+SQLSTATE: XX007
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06698: "SPI stack corrupted when connect SPI, %s"
+
+SQLSTATE: XX001
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06699: "SPI stack corrupted when connect SPI, stack depth %d"
+
+SQLSTATE: XX001
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-06700: "SPI stack corrupted when copy tuple, connected level: %d"
+
+SQLSTATE: XX001
+
+Description: Internal system error.
+
+Solution: Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/68-GAUSS-06701-GAUSS-06800.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/68-GAUSS-06701-GAUSS-06800.md
new file mode 100644
index 0000000000000000000000000000000000000000..9f28668462a39bbb9c9f34be3fbc8aea289a7d58
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/68-GAUSS-06701-GAUSS-06800.md
@@ -0,0 +1,868 @@
+---
+title: GAUSS-06701 - GAUSS-06800
+summary: GAUSS-06701 - GAUSS-06800
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-06701 - GAUSS-06800
+
+<br/>
+
+## GAUSS-06701 - GAUSS-06710
+
+<br/>
+
+GAUSS-06701: "SPI stack corrupted when return tuple, connected level: %d"
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06702: "SPI stack corrupted when modify tuple, connected level: %d"
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06703: "SPI stack corrupted when allocate, connected level: %d"
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06704: "open cursor with args has invalid arguments, %s"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06705: "SPI stack is corrupted when open cursor with args, current level: %d, connected level: %d"
+
+SQLSTATE: 24000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06706: "SPI stack is corrupted when open cursor, current level: %d, connected level: %d"
+
+SQLSTATE: 24000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06707: "invalid portal in SPI cursor close operation"
+
+SQLSTATE: 24000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06708: "SPI stack level is corrupted when checking SPI id, current level: %d, connected level: %d"
+
+SQLSTATE: SP006
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06709: "SPI stack is corrupted when checking SPI id."
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06710: "SPI tupletable is not cleaned when initializing SPI."
+
+SQLSTATE: SP006
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06711 - GAUSS-06720
+
+<br/>
+
+GAUSS-06711: "tuple is NULL when store to SPI tupletable."
+
+SQLSTATE: SP006
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06712: "consistency check on SPI tuple count failed when execute plan, %s"
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06713: "SPI stack is corrupted when perform cursor operation, current level: %d, connected level: %d"
+
+SQLSTATE: SP001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06714: "consistency check on SPI tuple count failed, %s"
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06715: "SPI stack corrupted when begin SPI operation."
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06716: "SPI tupletable is NULL when shutdown SPI for analyze."
+
+SQLSTATE: SP000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06717: "Unable to connect to execute internal query, current level: %d, connected level: %d"
+
+SQLSTATE: SP001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06718: "Invalid parameter in function '%s'"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06719: "do not support update or delete on table %s, when do cluster resizing on it."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06720: "delete delta table %s is not found when do cluster resizing table '%s'"
+
+SQLSTATE: 42P01
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06721 - GAUSS-06730
+
+<br/>
+
+GAUSS-06721: "Unsupport '%s' command during online expansion"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06722: "Unsupport '%s' command during online expansion on '%s'"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06723: "Unsupport '%s' command with '%s' option during online expansion on '%s' because the object is in read only mode."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06724: "Unsupport '%s' command with '%s' option during online expansion on '%s'"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06725: "Unsupport 'VACUUM FULL' command during online expansion on '%s'"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06726: "Unsupport '%s' command during online expansion on '%s' because the object is in read only mode."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06727: "function with OID %u does not exist when checking function dnstable"
+
+SQLSTATE: 42883
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06728: "operation expression function with OID %u does not exist."
+
+SQLSTATE: 42883
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06729: "new table %s is not found when do cluster resizing table '%s'"
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06730: "Invalid parameter in function '%s' when getting the name of new table"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06731 - GAUSS-06740
+
+<br/>
+
+GAUSS-06731: "unrecognized markType: %d when initializing query plan."
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06732: "unrecognized CmdType: %d when perform operations on view."
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06733: "could not find tableoid junk %s column when build RowMark"
+
+SQLSTATE: XX007
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06734: "could not find bucketid junk %s column when build RowMark"
+
+SQLSTATE: XX007
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06735: "could not find ctid junk %s column when build RowMark"
+
+SQLSTATE: XX007
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06736: "could not find whole-row junk %s column when build RowMark"
+
+SQLSTATE: XX007
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06737: "failed to fetch tuple for EvalPlanQual recheck from partition relation."
+
+SQLSTATE: 29P02
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06738: "streaminfo space is not enough because STREAM NUMBER : %d + GATHER NUMBER : %d < streamInfoIdx : %d"
+
+SQLSTATE: XX006
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06739: "query dop is out of range: %u [0-%d]"
+
+SQLSTATE: 22017
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06740: "m_query_dop can not be zero"
+
+SQLSTATE: 22023
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06741 - GAUSS-06750
+
+<br/>
+
+GAUSS-06741: "Expecting messages of query: %lu, but received messages of query: %lu"
+
+SQLSTATE: YY002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06742: "slot is out of range"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06743: "can't initialize index scans using unusable index '%s'"
+
+SQLSTATE: XX002
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06744: "indexqual for OpExpr doesn't have key on left side"
+
+SQLSTATE: XX002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06745: "bogus index qualification for OpExpr, attribute number is %d."
+
+SQLSTATE: XX002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06746: "indexqual for RowCompare expression doesn't have key on left side"
+
+SQLSTATE: XX002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06747: "bogus RowCompare index qualification, attribute number is %d"
+
+SQLSTATE: XX002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06748: "RowCompare index qualification contains wrong operator, strategy number is %d."
+
+SQLSTATE: XX002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06749: "n_sub_key can not be zero"
+
+SQLSTATE: XX002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06750: "indexqual for ScalarArray doesn't have key on left side"
+
+SQLSTATE: XX002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06751 - GAUSS-06760
+
+<br/>
+
+GAUSS-06751: "bogus index qualification for ScalarArray, attribute number is %d."
+
+SQLSTATE: XX002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06752: "can't initialize index scans using unusable local index '%s'"
+
+SQLSTATE: XX002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06753: "mergejoin clause is not an OpExpr %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06754: "cannot merge using non-equality operator %u, strategy is %d"
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06755: "mj_InnerTupleSlot cannot be NULL"
+
+SQLSTATE: XX005
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06756: "RIGHT JOIN is only supported with merge-joinable join conditions."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06757: "FULL JOIN is only supported with merge-joinable join conditions."
+
+SQLSTATE: 0A000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06758: "unrecognized join type: %d for mergejoin."
+
+SQLSTATE: XX004
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06759: "INSERT ON DUPLICATE KEY UPDATE does not support deferrable unique constraints/exclusion constraints."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06760: "could not create exclusion constraint '%s' when trying to build a new index"
+
+SQLSTATE: 23P01
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06761 - GAUSS-06770
+
+<br/>
+
+GAUSS-06761: "paramname should not be NULL"
+
+SQLSTATE: XX005
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06762: "cache lookup failed for function %u when initialize function cache."
+
+SQLSTATE: 29P01
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06763: "null prosrc for function %u when we need the function body text"
+
+SQLSTATE: 42P13
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06764: "function returns VOID, failed to get junk filter's slot"
+
+SQLSTATE: 29P02
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06765: "return type %s is not supported for SQL functions with ID %u."
+
+SQLSTATE: 42P13
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06766: "unrecognized node type: %d when initializing executor."
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06767: "unrecognized node type: %d when executing multi executor node."
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06768: "unrecognized node type: %d when ending executor."
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06769: "max iteration times %d hit when looping over right plan tree."
+
+SQLSTATE: 53400
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06770: "MPP with-recursive in node->shareContext is NULL in distributed mode "
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06771 - GAUSS-06780
+
+<br/>
+
+GAUSS-06771: "Unsupported hashing for recursive union"
+
+SQLSTATE: XX006
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06772: "SycUP stream node is not found"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06773: "Unsupported SyncController type typeid:%d typename%s"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06774: "more than one sync-up stream node"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06775: "un-recognize steps for consumer side when synchronizing recusive-union."
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06776: "un-recognized steps for producer side when sychronizing recursive-union."
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06777: "MPP with-recursive. Controller is not found in ExecSyncStreamProducer with stream[%d] top:%s"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06778: "need_rescan should not be NULL"
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06779: "MPP With-Recursive sync controller for Stream[%d] is not found"
+
+SQLSTATE: XX005
+
+Description: Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06780: "MPP with-recursive datanode:%s CTE(%d) none_recursive_finished is not set to finish"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06781 - GAUSS-06790
+
+<br/>
+
+GAUSS-06781: "MPP with-recursive datanode:%s CTE(%d) recursive_union_finish is not set to finish"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06782: "MPP with-recursive step information in SyncUpController is not correct %d"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06783: "Invalid start next recursvie iteration when kick-off the whole cluster."
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06784: "ORDER BY with column index is not supported"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06785: "can not cast from type %s to type %s "
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06786: "invalid operation on partition, allowed are UPDATE/DELETE/SELECT/MERGE"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06787: "Fail to find partition from sequence."
+
+SQLSTATE: XX005
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06788: "The left value of the expression should not be NULL"
+
+SQLSTATE: XX005
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06789: "Fail to get the right value of the expression"
+
+SQLSTATE: XX005
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06790: "unrecognized node type: %s"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06791 - GAUSS-06800
+
+<br/>
+
+GAUSS-06791: "hash bucket is not supported in column store."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06792: "Unexpected vector hash aggregation status"
+
+SQLSTATE: XX006
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06793: "Unexpected vector hashagg status"
+
+SQLSTATE: XX006
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06794: "TIMESERIES store dose not support this operation"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06795: "TIMESERIES store unsupport none partitioned table"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06796: "could not write to hashJoin temporary file: %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06797: "could not read hashkey from hash-join temporary file: %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06798: "unrecognize data type %u."
+
+SQLSTATE: 42P18
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06799: "Unsupported window function %u in vector engine"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06800: "UnSupported vector window aggregation function %u"
+
+SQLSTATE: 42P25
+
+Description:Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/69-GAUSS-06801-GAUSS-06900.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/69-GAUSS-06801-GAUSS-06900.md
new file mode 100644
index 0000000000000000000000000000000000000000..453b245b4482ff857ad23d82bc32733638cc103a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/69-GAUSS-06801-GAUSS-06900.md
@@ -0,0 +1,868 @@
+---
+title: GAUSS-06801 - GAUSS-06900
+summary: GAUSS-06801 - GAUSS-06900
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-06801 - GAUSS-06900
+
+<br/>
+
+## GAUSS-06801 - GAUSS-06810
+
+<br/>
+
+GAUSS-06801: "invalid datum int array size %d"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06802: "[SonicHash] Unsupport sonic data desc size %d without tuple desc"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06803: "[SonicHash] Unrecognize data type %u with tuple desc"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06804: "[VecSonicHashJoin: write numeric atom occurs error.]"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06805: "m_curFlag should not be NULL"
+
+SQLSTATE: 22004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06806: "[VecSonicHashJoin: load numeric atom occurs error.]"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06807: "Unrecognized vector sonic hashjoin run status."
+
+SQLSTATE: 42704
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06808: "Unrecognize data type %u when choosing match functions from inner hash keys."
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06809: "Unrecognize data type %u when choosing match functions from outer hash keys."
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06810: "SonicHashJoin reportSorthashinfo: Unsupport report type %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06811 - GAUSS-06820
+
+<br/>
+
+GAUSS-06811: "[SonicHash] Unrecognize desc type %d with type oid %u"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06812: "[SonicHash] The number of rows is greater than SONIC_MAX_ROWS %u, which is not supported for hash table construction."
+
+SQLSTATE: P0003
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06813: "[SonicHash] Unrecognized datetype %u, attrlen %d when init hash functions."
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06814: "Unrecognized vector sonic hashagg run status."
+
+SQLSTATE: 42704
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06815: "Unrecognized vector sonic hashagg data status."
+
+SQLSTATE: 42704
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06816: "Unrecognized vector sonic hash aggregation status."
+
+SQLSTATE: 42704
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06817: "[SonicHash] could not rewind sonic hash-join temporary file: %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06818: "[SonicHash] Int has unknown type size of %d"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06819: "[VecSonicHashJoin: reading numeric occurs error.]"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06820: "Unimplemented vector node %s"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06821 - GAUSS-06830
+
+<br/>
+
+GAUSS-06821: "unrecognized node type: %s in function ExecVecMarkPos"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06822: "unrecognized node type: %s in ExecRestrPos"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06823: "Type of parameter %d (%s) does not match that when preparing the plan (%s)"
+
+SQLSTATE: 42804
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06824: "No value found for parameter %d"
+
+SQLSTATE: 42704
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06825: "Unrecognized RowCompareType: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06826: "Unrecognized nulltesttype: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06827: "nvalues: %d is invalid"
+
+SQLSTATE: 22015
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06828: "udfInfo->allocRows: %d is not enough"
+
+SQLSTATE: 22015
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06829: "UnSupported vector function %u"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06830: "unrecognized paramtype: %d"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06831 - GAUSS-06840
+
+<br/>
+
+GAUSS-06831: "Unaligned rows for batches need to be expression evaluation"
+
+SQLSTATE: 23514
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06832: "LZ4 decompress failed when deserializing message, return %d, compressed length %d, original length %d"
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06833: "[%s] no such label found"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06834: "Unsupported policy filter values"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06835: "%s policy already exists, create failed"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06836: "Unsupported policy type"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06837: "%s no such policy found, alter failed"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06838: "%s policy does not exist, drop failed"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06839: "Cache lookup failed for relation %u"
+
+SQLSTATE: 29P01
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06840: "Do not support policy label on temp table '%s'"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06841 - GAUSS-06850
+
+<br/>
+
+GAUSS-06841: "[%s] no such schema found"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06842: "[%s.%s] no such relation found"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06843: "[%s.%s] no such view found"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06844: "[%s.%s.%s] no such relation column found"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06845: "[%s.%s] no such function found"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06846: "Column %s already in other label"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06847: "Column name without table"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06848: "%s label already defined"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06849: "Resource %s %s already exists in label %s"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06850: "No such resource %s %s found in label %s"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06851 - GAUSS-06860
+
+<br/>
+
+GAUSS-06851: "Could not find tuple for label %lld"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06852: "%s no such label found"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06853: "One or more labels bound to policies - cannot drop"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06854: "Masking policy can only operate on column object."
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06855: "Masking policy can only operate on column of ordinary table."
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06856: "current policy is conflict with exist policy: %s"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06857: "unsupported policy filter values"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06858: "policy %s not exists."
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06859: "app: [%s] is invalid"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06860: "ip range: [%s] is invalid, please identify"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06861 - GAUSS-06870
+
+<br/>
+
+GAUSS-06861: "role: [%s] is invalid"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06862: "filter: [%s] is invalid"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06863: "length of session ip buffer should more than 128"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06864: "invalid value for 64-bit integer option '%s': %s"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06865: "Value '%s' of option 'compression' is invalid for timeseries table"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06866: "Invalid interval string for 'ttl' option"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06867: "Invalid interval range for 'ttl' option"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06868: "Invalid interval string for 'period' option"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06869: "Invalid interval range for 'period' option"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06870: "invalid value for 'append_mode' option"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06871 - GAUSS-06880
+
+<br/>
+
+GAUSS-06871: "The split flag should exactly be one character and can not be NULL."
+
+SQLSTATE: 2200F
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06872: "%s is not supported by pound parser."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06873: "number of columns (%u) exceeds limit (%d)"
+
+SQLSTATE: 54011
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06874: "index is not correct"
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06875: "data length is not correct"
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06876: "unrecognized batch compress type"
+
+SQLSTATE: 42804
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06877: "the attribute column of user defined CompositeType does not support view type '%s' "
+
+SQLSTATE: 42704
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06878: "unsupport connector type %d"
+
+SQLSTATE: HV00N
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06879: "Invalid file size is found on file: %s."
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06880: "Failed to parse the postscript from string"
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06881 - GAUSS-06890
+
+<br/>
+
+GAUSS-06881: "Failed to parse the filefooter from string"
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06882: "Error occurred while reading column %d: ORC and mpp types do not match, ORC type is %s and mpp type is %s."
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06883: "Error occurs while reading orc file %s, detail can be found in dn log of %s."
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06884: "The type of decimal(precision>38) doesn't support predicate pushdown."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06885: "Unsupported var type %u from data type %s(%u)."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06886: "Unsupported data type : %s."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06887: "Error occurs while reading parquet file %s, detail can be found in dn log of %s."
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06888: "Error occurred while reading column %d: PARQUET and mpp types do not match, PARQUET type is %s(%s) and mpp type is %s."
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06889: "Unsupported parquet type : %u."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06890: "Before encoding, the length of data as partition directory name must be less than dfs_partition_directory_length(%d)/3."
+
+SQLSTATE: 53400
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06891 - GAUSS-06900
+
+<br/>
+
+GAUSS-06891: "line is larger than 1GB."
+
+SQLSTATE: 22P04
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06892: "Indicates the restriction's level is undefined."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06893: "get min max statistics false."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06894: "Unsupported data type for min-max filter: %s(%u)."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06895: "Error occurred while reading column %d: carbondata and kernel types do not match, carbondata type is %s and kernel type is %s."
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06896: "Unsupported var type %s from data type %s."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06897: "Error occurred while reading column %d: carbondata and kernel types do not match, carbondata type is %s(%d,%d) and kernel type is %s."
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06898: "Unsupported data type : %s for predicate filter."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06899: "Unsupported carbondata type : %s."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06900: "Failed to alloc the space to fileFooter."
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/7-GAUSS-00601-GAUSS-00700.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/7-GAUSS-00601-GAUSS-00700.md
new file mode 100644
index 0000000000000000000000000000000000000000..43defb2e7fae6101974d64afaaa0967552711c33
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/7-GAUSS-00601-GAUSS-00700.md
@@ -0,0 +1,748 @@
+---
+title: GAUSS-00601 - GAUSS-00700
+summary: GAUSS-00601 - GAUSS-00700
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-00601 - GAUSS-00700
+
+<br/>
+
+## GAUSS-00601 - GAUSS-00610
+
+<br/>
+
+GAUSS-00601: "Permission denied."
+
+SQLSTATE: 42501
+
+Description: You have no permission to run **CREATE/ALTER/DROP ROLE**.
+
+Solution: Ensure that you have permission to run **CREATE/ALTER/DROP ROLE**.
+
+GAUSS-00602: "Separation of privileges is used,user can't be altered because of too many privileges."
+
+SQLSTATE: 42501
+
+Description: The permissions specified for users exceed the limit during privilege separation.
+
+Solution: Ensure that the permissions specified for users do not exceed the limit during privilege separation.
+
+GAUSS-00603: "The account has been locked."
+
+SQLSTATE: 28000
+
+Description: An account is locked due to invalid operations.
+
+Solution: Contact the system administrator to unlock the account. The system administrator will unlock an account after confirming that no invalid operations exist.
+
+GAUSS-00606: "The role's password is null in pg_authid, REPLACE should not be specified."
+
+SQLSTATE: XX000
+
+Description: The user password is not specified, and the value REPLACE is specified.
+
+Solution: Specify the password.
+
+GAUSS-00610: "Permission denied to drop role."
+
+SQLSTATE: 42501
+
+Description: You have no permission to run **DROP ROLE**.
+
+Solution: Ensure that you have permission to run **DROP ROLE**.
+
+<br/>
+
+## GAUSS-00611 - GAUSS-00620
+
+<br/>
+
+GAUSS-00611: "fail to drop the current schema"
+
+SQLSTATE: 55006
+
+Description:**DROP ROLE** cannot be used to delete the schema.
+
+Solution: Do not delete the schema.
+
+GAUSS-00612: "current user cannot be dropped"
+
+SQLSTATE: 55006
+
+Description:**DROP ROLE** cannot be used to delete the user.
+
+Solution: Do not delete the user.
+
+GAUSS-00613: "session user cannot be dropped"
+
+SQLSTATE: 55006
+
+Description:**DROP ROLE** cannot be used to delete the session user.
+
+Solution: Do not delete the session user.
+
+GAUSS-00615: "role '%s' cannot be dropped because some objects depend on it"
+
+SQLSTATE: 2BP01
+
+Description:**DROP ROLE** cannot be used to delete the user that objects depend on.
+
+Solution: Clear the dependency and try again.
+
+GAUSS-00616: "session user cannot be renamed"
+
+SQLSTATE: 0A000
+
+Description: Failed to rename the session user.
+
+Solution: Rename the session user as an authorized user.
+
+GAUSS-00617: "current user cannot be renamed"
+
+SQLSTATE: 0A000
+
+Description: Failed to rename the user.
+
+Solution: Do not rename the user.
+
+GAUSS-00620: "Permission denied to rename role."
+
+SQLSTATE: 42501
+
+Description: You have no permission to rename users.
+
+Solution: Ensure that you have permission to rename users.
+
+<br/>
+
+## GAUSS-00621 - GAUSS-00630
+
+<br/>
+
+GAUSS-00621: "column names cannot be included in GRANT/REVOKE ROLE"
+
+SQLSTATE: 0LP01
+
+Description: The **GRANT/REVOKE ROLE** statement contains column names.
+
+Solution: Ensure that the **GRANT/REVOKE ROLE** statement does not contain column names.
+
+GAUSS-00622: "Permission denied to drop objects."
+
+SQLSTATE: 42501
+
+Description: You have no permission to delete objects.
+
+Solution: Ensure that you have permission to delete objects.
+
+GAUSS-00623: "Permission denied to reassign objects."
+
+SQLSTATE: 42501
+
+Description: You have no permission to reassign objects.
+
+Solution: Ensure that you have permission to reassign objects.
+
+GAUSS-00625: "must have admin option on role '%s'"
+
+SQLSTATE: 42501
+
+Description: System administrators do not have the **SYSADMIN** attribute.
+
+Solution: Specify the **SYSADMIN** attribute for system administrators when creating them.
+
+GAUSS-00626: "must be system admin to set grantor"
+
+SQLSTATE: 42501
+
+Description: You have no permission to set authorizers.
+
+Solution: Set authorizers as a system administrator.
+
+GAUSS-00627: "role '%s' is a member of role '%s'"
+
+SQLSTATE: 0LP01
+
+Description: The target user is a member of a user.
+
+Solution: Check whether the target user is a member of a user.
+
+GAUSS-00628: "schema '%s' doesnot exist"
+
+SQLSTATE: 3F000
+
+Description: The schema does not exist.
+
+Solution: Check whether the schema exists.
+
+GAUSS-00629: "cannot cancel current session's query"
+
+SQLSTATE: 42601
+
+Description: The session query cannot be canceled.
+
+Solution: Check whether the session has locked the objects owned by users.
+
+GAUSS-00630: "md5-password encryption failed."
+
+SQLSTATE: XX000
+
+Description: MD5 fails to encrypt passwords.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-00631 - GAUSS-00640
+
+<br/>
+
+GAUSS-00631: "sha256-password encryption failed."
+
+SQLSTATE: XX000
+
+Description: SHA256 failed to be encrypted.
+
+Solution: Contact technical support.
+
+GAUSS-00633: "Password must contain at least %d upper characters."
+
+SQLSTATE: 28P01
+
+Description: The password must contain a certain number of uppercase letters specified by the GUC parameter password_min_uppercase.
+
+Solution: Add uppercase letters to the password to meet the parameter requirement.
+
+GAUSS-00634: "Password must contain at least %d lower characters."
+
+SQLSTATE: 28P01
+
+Description: The password must contain a certain number of lowercase letters specified by the GUC parameter password_min_lowercase.
+
+Solution: Add lowercase letters to the password to meet the parameter requirement.
+
+GAUSS-00635: "Password must contain at least %d digital characters."
+
+SQLSTATE: 28P01
+
+Description: The password must contain a certain number of digits specified by the GUC parameter password_min_digital.
+
+Solution: Add digits to the password to meet the parameter requirement.
+
+GAUSS-00636: "Password must contain at least %d special characters."
+
+SQLSTATE: 28P01
+
+Description: The password must contain a certain number of special characters specified by the GUC parameter password_min_special.
+
+Solution: Add special characters to the password to meet the parameter requirement.
+
+GAUSS-00637: "Password must contain at least three kinds of characters."
+
+SQLSTATE: 28P01
+
+Description: Less than three character types are contained in the password.
+
+Solution: 1. The password contains at least eight characters. 2. The password cannot be the same as the username. 3. The password contains at least three of the following character types: uppercase characters, lowercase characters, digits, and special characters (limited to including: ~!@#$ %^&*()-_=+\|[{}];:,<.>/?. "
+
+GAUSS-00638: "The parameter roleID of CheckPasswordComplexity is NULL"
+
+SQLSTATE: XX000
+
+Description: **roleid** is null. Password complexity checking fails.
+
+Solution: Ensure that **roleid** is not null.
+
+GAUSS-00639: "The parameter newPasswd of CheckPasswordComplexity is NULL"
+
+SQLSTATE: XX000
+
+Description: The new password is null. Password complexity checking fails.
+
+Solution: Enter the password again.
+
+GAUSS-00640: "Password should not equal to the rolname."
+
+SQLSTATE: XX000
+
+Description: The new password and the username are the same.
+
+Solution: Ensure that the password is not the same as the username. Reset the password.
+
+<br/>
+
+## GAUSS-00641 - GAUSS-00650
+
+<br/>
+
+GAUSS-00641: "reverse_string failed, possibility out of memory"
+
+SQLSTATE: XX000
+
+Description: The password string failed to be reversed.
+
+Solution: Check whether the OOM problem has occurred.
+
+GAUSS-00644: "New password should not equal to the reverse of old ones."
+
+SQLSTATE: XX000
+
+Description: The new password and the reversed old password are the same.
+
+Solution: Ensure that the new password differs from the reversed old password.
+
+GAUSS-00645: "the parameter passwd of AddAuthHistory is null"
+
+SQLSTATE: XX000
+
+Description: The password is null when you add the record.
+
+Solution: Ensure that the password is not null.
+
+GAUSS-00646: "sha256-password encryption failed"
+
+SQLSTATE: XX000
+
+Description: SHA256 failed to be encrypted.
+
+Solution: Internal system error.
+
+GAUSS-00647: "The password cannot be reused."
+
+SQLSTATE: XX000
+
+Description: The password cannot be reused.
+
+Solution: Check whether the new password is the same as the old password and meets the reuse requirements.
+
+GAUSS-00648: "TryLockAccount(): roleid is not valid."
+
+SQLSTATE: XX000
+
+Description:**roleid** is invalid.
+
+Solution: Ensure that **roleid** is valid.
+
+GAUSS-00649: "Permission denied."
+
+SQLSTATE: XX000
+
+Description: You have no permission to run **CREATE/ALTER/DROP ROLE**.
+
+Solution: Ensure that you have permission to run **CREATE/ALTER/DROP ROLE**.
+
+GAUSS-00650: "TryLockAccount(): parameter extrafails is less than zero."
+
+SQLSTATE: XX000
+
+Description: The value of **extrafails** is smaller than 0.
+
+Solution: Ensure that the value of **extrafails** is not smaller than 0.
+
+<br/>
+
+## GAUSS-00651 - GAUSS-00660
+
+<br/>
+
+GAUSS-00651: "The tuple of pg_user_status not found"
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-00652: "TryUnlockAccount(): roleid is not valid."
+
+SQLSTATE: XX000
+
+Description: **roleid** is invalid.
+
+Solution: Ensure that **roleid** is valid.
+
+GAUSS-00653: "IsAccountLocked(): roleid is not valid."
+
+SQLSTATE: XX000
+
+Description:**roleid** is invalid.
+
+Solution: Ensure that **roleid** is valid.
+
+GAUSS-00654: "getAccountLockedStyle: roleid is not valid."
+
+SQLSTATE: XX000
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-00655: "DropUserStatus(): roleid is not valid."
+
+SQLSTATE: XX000
+
+Description: **roleid** is invalid.
+
+Solution: Ensure that **roleid** is valid.
+
+GAUSS-00656: "Invalid username/password,login denied."
+
+SQLSTATE: 42704
+
+Description: The username or password is invalid and the login fails.
+
+Solution: Ensure that the username and password are valid.
+
+GAUSS-00657: "User's passwordtime in pg_auth_history is 0."
+
+SQLSTATE: 28P01
+
+Description:**passwordtime** of the corresponding user in **pg_auth_history** is empty.
+
+Solution: Theoretically, this column is not empty. Contact technical support.
+
+GAUSS-00658: "aggregate stype must be specified"
+
+SQLSTATE: 42P13
+
+Description: When an aggregate function is defined, **stype** is not specified.
+
+Solution: Specify **stype** when defining an aggregate function.
+
+GAUSS-00659: "aggregate sfunc must be specified"
+
+SQLSTATE: 42P13
+
+Description: When an aggregate function is defined, **sfunc** is not specified.
+
+Solution: Specify **sfunc** when defining an aggregate function.
+
+GAUSS-00660: "aggregate input type must be specified"
+
+SQLSTATE: 42P13
+
+Description: When an aggregate function is defined, **input type** is not specified.
+
+Solution: Specify **input type** when defining an aggregate function.
+
+<br/>
+
+## GAUSS-00661 - GAUSS-00670
+
+<br/>
+
+GAUSS-00661: "basetype is redundant with aggregate input type specification"
+
+SQLSTATE: 42P13
+
+Description: When an aggregate function is defined, **basetype** is redundant.
+
+Solution: If the aggregate function is defined using version pg8.2 or later, do not use **basetype** to describe the input type.
+
+GAUSS-00662: "aggregate transition data type cannot be %s"
+
+SQLSTATE: 42P13
+
+Description: The type of the data to be converted by an aggregate function is incorrect.
+
+Solution: Ensure that the type of the data to be converted by the aggregate function is not pseudo. The initial user type to be converted can be internal.
+
+GAUSS-00663: "function %s already exists in schema '%s'"
+
+SQLSTATE: 42723
+
+Description: A function already exists in the schema.
+
+Solution: Ensure that the function name is unique.
+
+GAUSS-00664: "Unsupport feature"
+
+SQLSTATE: XX000
+
+Description: Feature not supported.
+
+Solution: Check the table definition statement.
+
+GAUSS-00665: "column store unsupport constraint '%s'"
+
+SQLSTATE: XX000
+
+Description: Constraints unsupported by the column-store table are defined.
+
+Solution: Use constraints supported by the column-store table, such as NULL, NOT NULL, DEFAULT, and CLUSTER constraints.
+
+GAUSS-00666: "PARTIAL_CLUSTER_ROWS cannot be less than MAX_BATCHROW."
+
+SQLSTATE: 42P16
+
+Description: The value of **PARTIAL_CLUSTER_ROWS** is smaller than that of **MAX_BATCHROW**.
+
+Solution: Ensure that the value of **PARTIAL_CLUSTER_ROWS** is greater than or equal to that of **MAX_BATCHROW**.
+
+GAUSS-00667: "ON COMMIT can only be used on temporary tables"
+
+SQLSTATE: 42P16
+
+Description:**ON COMMIT** is used for non-temporary tables.
+
+Solution: Use **ON COMMIT** for temporary tables only.
+
+GAUSS-00668: "constraints on foreign tables are not supported"
+
+SQLSTATE: 42809
+
+Description: Constraints on foreign tables are defined.
+
+Solution: Do not define constraints on foreign tables.
+
+GAUSS-00669: "cannot create temporary table within security-restricted operation"
+
+SQLSTATE: 42501
+
+Description: Temporary tables are created under security restrictions.
+
+Solution: Do not create temporary tables under security restrictions.
+
+GAUSS-00670: "only shared relations can be placed in pg_global tablespace"
+
+SQLSTATE: 22023
+
+Description: User-defined relations are added to the tablespace of the **pg_global** table.
+
+Solution: Add only shared relations to the tablespace of the **pg_global** table.
+
+<br/>
+
+## GAUSS-00671 - GAUSS-00680
+
+<br/>
+
+GAUSS-00673: "default values on foreign tables are not supported"
+
+SQLSTATE: 42809
+
+Description: When foreign tables are defined, default values are set for columns.
+
+Solution: Do not set default values for columns of foreign tables.
+
+GAUSS-00674: "No Datanode defined in cluster"
+
+SQLSTATE: 42704
+
+Description: No DN is defined.
+
+Solution: Create DNs for the cluster.
+
+GAUSS-00675: "DROP INDEX CONCURRENTLY does not support dropping multiple objects"
+
+SQLSTATE: 0A000
+
+Description: The **DROP INDEX CONCURRENTLY** statement is used to delete multiple objects.
+
+Solution: Do not delete multiple objects.
+
+GAUSS-00676: "DROP INDEX CONCURRENTLY does not support CASCADE"
+
+SQLSTATE: 0A000
+
+Description:**CASCADE** is specified for the **DROP INDEX CONCURRENTLY** statement.
+
+Solution: Do not specify **CASCADE** for the **DROP INDEX CONCURRENTLY** statement.
+
+GAUSS-00677: "unrecognized drop object type: %d"
+
+SQLSTATE: XX000
+
+Description: The object type cannot be dropped.
+
+Solution: Ensure that the object type can be dropped.
+
+GAUSS-00678: "permission denied: '%s' is a system catalog"
+
+SQLSTATE: 42501
+
+Description: You have no permission to delete a system catalog.
+
+Solution: Do not delete a system catalog.
+
+GAUSS-00679: "PGXC does not support RESTART IDENTITY yet"
+
+SQLSTATE: 0A000
+
+Description: **RESTART IDENTITY** is specified for the **TRUNCATE** statement.
+
+Solution: Do not specify **RESTART IDENTITY** for the **TRUNCATE** statement.
+
+<br/>
+
+## GAUSS-00681 - GAUSS-00690
+
+<br/>
+
+GAUSS-00681: "'%s' is not a table"
+
+SQLSTATE: 42809
+
+Description: The object to be truncated is not a table.
+
+Solution: Ensure that the object to be truncated is a table.
+
+GAUSS-00682: "cannot truncate temporary tables of other sessions"
+
+SQLSTATE: 0A000
+
+Description: Temporary tables of other sessions are truncated.
+
+Solution: Do not truncate temporary tables of other sessions.
+
+GAUSS-00683: "tables can have at most %d columns"
+
+SQLSTATE: 54011
+
+Description: The number of columns of a table is greater than 1600.
+
+Solution: Ensure that the number of columns of a table is not greater than 1600.
+
+GAUSS-00684: "cannot inherit from temporary relation '%s'"
+
+SQLSTATE: 42809
+
+Description: A temporary table is inherited.
+
+Solution: Do not inherit temporary tables. Only temporary tables of the session are displayed.
+
+GAUSS-00685: "cannot inherit from temporary relation of another session"
+
+SQLSTATE: 42809
+
+Description: A temporary table is inherited.
+
+Solution: Do not inherit temporary tables. Only temporary tables of the session are displayed.
+
+GAUSS-00686: "relation '%s' would be inherited from more than once"
+
+SQLSTATE: 42P07
+
+Description: A table has been inherited multiple times.
+
+Solution: Check the table creation statement to ensure that no duplicate tables exist in the inherited table.
+
+GAUSS-00687: "inherited column '%s' has a type conflict"
+
+SQLSTATE: 42804
+
+Description: The type of a column inherited is inconsistent with those of other columns.
+
+Solution: Ensure that the type of the column inherited is consistent with those of other columns.
+
+GAUSS-00688: "inherited column '%s' has a collation conflict"
+
+SQLSTATE: 42P21
+
+Description: The collation of the column inherited is inconsistent with those of other columns.
+
+Solution: Ensure that the collation of the column inherited is consistent with those of other columns.
+
+GAUSS-00689: "inherited column '%s' has a storage parameter conflict"
+
+SQLSTATE: 42804
+
+Description: The storage parameter of the column inherited is inconsistent with those of other columns.
+
+Solution: Ensure that the storage parameter of the column inherited is consistent with those of other columns.
+
+GAUSS-00690: "column '%s' has a type conflict"
+
+SQLSTATE: 42804
+
+Description: The type of a column is inconsistent with those of other columns.
+
+Solution: Ensure that the type of the column inherited is consistent with those of other columns.
+
+<br/>
+
+## GAUSS-00691 - GAUSS-00700
+
+<br/>
+
+GAUSS-00691: "column '%s' has a collation conflict"
+
+SQLSTATE: 42P21
+
+Description: The collation of a column is inconsistent with those of other columns.
+
+Solution: Ensure that the collation of the column inherited is consistent with those of other columns.
+
+GAUSS-00692: "column '%s' has a storage parameter conflict"
+
+SQLSTATE: 42804
+
+Description: The storage parameter of the column is inconsistent with those of other columns.
+
+Solution: Ensure that the storage parameter of the column inherited is consistent with those of other columns.
+
+GAUSS-00693: "column '%s' inherits conflicting default values"
+
+SQLSTATE: 42611
+
+Description: The value a column inherits is inconsistent with the default value.
+
+Solution: Ensure that the value a column inherits is consistent with the default value.
+
+GAUSS-00694: "check constraint name '%s' appears multiple times but with different expressions"
+
+SQLSTATE: 42710
+
+Description: The names of check constraints on different expressions occur multiple times.
+
+Solution: Ensure that the names of check constraints on different expressions appear once.
+
+GAUSS-00695: "cannot rename column of typed table"
+
+SQLSTATE: 42809
+
+Description: The column of a typed table is renamed.
+
+Solution: Do not rename the column of a typed table.
+
+GAUSS-00696: "'%s' is not a table, view, composite type, index, or foreign table"
+
+SQLSTATE: 42809
+
+Description: The object to be renamed is not a table.
+
+Solution: Do not rename the column of a view, type, index, or foreign table.
+
+GAUSS-00697: "inherited column '%s' must be renamed in child tables too"
+
+SQLSTATE: 42P16
+
+Description: A renamed inherited column is not synchronized to child tables.
+
+Solution: Synchronize the renamed inherited column to child tables.
+
+GAUSS-00698: "cannot rename system column '%s'"
+
+SQLSTATE: 0A000
+
+Description: The name of a column reserved for the system is modified.
+
+Solution: Do not modify the name of a column reserved for the system.
+
+GAUSS-00699: "cannot rename inherited column '%s'"
+
+SQLSTATE: 42P16
+
+Description: The name of an inherited column is modified.
+
+Solution: Do not modify the name of an inherited column.
+
+GAUSS-00700: "inherited constraint '%s' must be renamed in child tables too"
+
+SQLSTATE: 42P16
+
+Description: A renamed inherited constraint is not synchronized to child tables.
+
+Solution: Synchronize the renamed inherited constraint to child tables.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/70-GAUSS-06901-GAUSS-07000.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/70-GAUSS-06901-GAUSS-07000.md
new file mode 100644
index 0000000000000000000000000000000000000000..b26dc7c76b55c8ca19a0e15cef451720e1342dad
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/70-GAUSS-06901-GAUSS-07000.md
@@ -0,0 +1,868 @@
+---
+title: GAUSS-06901 - GAUSS-07000
+summary: GAUSS-06901 - GAUSS-07000
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-06901 - GAUSS-07000
+
+<br/>
+
+## GAUSS-06901 - GAUSS-06910
+
+<br/>
+
+GAUSS-06901: "Failed to alloc the space to fileHeader."
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06902: "Failed to alloc the space to fileReader."
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06903: "Can't find .carbondata file."
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06904: "'type' option is not provided."
+
+SQLSTATE: 42P17
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06905: "No 'type' option provided."
+
+SQLSTATE: 42P17
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06906: "setMinMaxByHeapTuple"
+
+SQLSTATE: 20000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06907: "delete or update failed due to concurrent conflict"
+
+SQLSTATE: P0002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06908: "getting next tuple in an ordered catalog scan failed"
+
+SQLSTATE: P0002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06909: "read handler is not in pending_free_reader_list"
+
+SQLSTATE: D0009
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06910: "write handler is not in pending_free_writer_list"
+
+SQLSTATE: D0009
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06911 - GAUSS-06920
+
+<br/>
+
+GAUSS-06911: "Only ORC/PARQUET/CARBONDATA/CSV/TEXT is supported for now."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06912: "Failed to get currentFileName !"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06913: "setDescByFilePath cannot find filename"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06914: "Rigth operation in constraint expression cannot be NULL."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06915: "Invalid Oid for operator %u."
+
+SQLSTATE: 20000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06916: "Unsupported data type on typeoid:%u when converting string to datum."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06917: "Unsupported data type on typeoid:%u when converting datum to string."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06918: "The leftop is null"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06919: "The rightop is null"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06920: "The arg is null"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06921 - GAUSS-06930
+
+<br/>
+
+GAUSS-06921: "bloomFilter create failed"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06922: "empty partition expression"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06923: "Invalid partition expression:%s"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06924: "argument to option'%s' must be a valid encoding name"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06925: "Column %s is unsupported data type."
+
+SQLSTATE: HV004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06926: "No %s is specified for the foreign table."
+
+SQLSTATE: 44000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06927: "Unsupport any empy %s for the foreign table."
+
+SQLSTATE: 44000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06928: "The first character and the end character of each %s must be a '/' in string '%s'."
+
+SQLSTATE: 42P17
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06929: "No folder path is specified for the foreign table."
+
+SQLSTATE: 44000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06930: "No file path is specified for the foreign table."
+
+SQLSTATE: 44000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06931 - GAUSS-06940
+
+<br/>
+
+GAUSS-06931: "No hdfscfg path is specified for the server."
+
+SQLSTATE: 44000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06932: "Only a folder path is allowed for the foreign table."
+
+SQLSTATE: 44000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06933: "Only a hdfscfg path is allowed for the server."
+
+SQLSTATE: 44000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06934: "No address is specified for the server."
+
+SQLSTATE: 44000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06935: "The port value is out of range: \'%s\'"
+
+SQLSTATE: 44000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06936: "Please select other functions to parse deciaml data."
+
+SQLSTATE: HV004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06937: "The incorrect numeric format."
+
+SQLSTATE: HV004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06938: "index row size %zu exceeds maximum %zu for index '%s'"
+
+SQLSTATE: 54000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06939: "number of items mismatch in GIN entry tuple, %d in tuple header, %d decoded"
+
+SQLSTATE: XX002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06940: "Invalid arguments for function ginbuild"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06941 - GAUSS-06950
+
+<br/>
+
+GAUSS-06941: "Invalid arguments for function cginbuild"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06942: "access method 'cgin' does not support multi column index with operator ||"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06943: "access method 'cgin' does not support null column index"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06944: "Invalid arguments for function gininsert"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06945: "invalid item pointer."
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06946: "Invalid arguments for function ginarrayextract"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06947: "Invalid arguments for function ginqueryarrayextract"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06948: "right sibling of GIN page is of different type"
+
+SQLSTATE: XX002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06949: "right sibling of GIN page was deleted"
+
+SQLSTATE: XX002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06950: "invalid return code from GIN placeToPage method: %d"
+
+SQLSTATE: XX002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06951 - GAUSS-06960
+
+<br/>
+
+GAUSS-06951: "'%s' is not a GIN index"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06952: "cannot access temporary indexes of other sessions"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06953: "unexpected GIN leaf action: %hhu"
+
+SQLSTATE: 2200G
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06954: "GIN split record did not contain a full-page image of left page"
+
+SQLSTATE: XX002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06955: "GIN split record did not contain a full-page image of right page"
+
+SQLSTATE: XX002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06956: "GIN split record did not contain a full-page image of root page"
+
+SQLSTATE: XX002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06957: "replay of gin entry tree page vacuum did not restore the page"
+
+SQLSTATE: XX002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06958: "gin_redo: unknown op code %hhu"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06959: "unexpected order by operator: %d"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06960: "Invalid arguments for function ginrescan"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06961 - GAUSS-06970
+
+<br/>
+
+GAUSS-06961: "Invalid arguments for function ginendscan"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06962: "posting list is too long"
+
+SQLSTATE: 54000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06963: "could not split GIN page; all old items didn't fit"
+
+SQLSTATE: XX002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06964: "could not split GIN page; no new items fit"
+
+SQLSTATE: XX002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06965: "could not fit vacuumed posting list"
+
+SQLSTATE: XX002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06966: "Invalid arguments for function ginbulkdelete"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06967: "Invalid arguments for function ginvacuumcleanup"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06968: "missing GIN support function (%d or %d) for attribute %d of index '%s'"
+
+SQLSTATE: 42883
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06969: "invalid attribute num:%hu"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06970: "could not find parent of block %u in lookup table"
+
+SQLSTATE: XX002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06971 - GAUSS-06980
+
+<br/>
+
+GAUSS-06971: "failed to decompress keys in tuple"
+
+SQLSTATE: XX002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06972: "failed to form tuple from gist"
+
+SQLSTATE: XX002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06973: "could not seek temporary file: %ld"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06974: "could not read temporary file: %ld"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06975: "the leaf keys should have the high point equals to the low point"
+
+SQLSTATE: 42P24
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06976: "gist_redo: unknown op code %hhu"
+
+SQLSTATE: XX002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06977: "index '%s' already contains data."
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06978: "no order by operators allowed."
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06979: "hashmerge: unimplemented."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06980: "buckets id %d of table is outsize range [%d,%d]"
+
+SQLSTATE: 22003
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06981 - GAUSS-06990
+
+<br/>
+
+GAUSS-06981: "error format single item string %s"
+
+SQLSTATE: 42602
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06982: "empty merge_list string"
+
+SQLSTATE: 42602
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06983: "find merge_str in pgxc_class and is first set %d"
+
+SQLSTATE: 42602
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06984: "not find merge_str in pgxc_class and not first set %d"
+
+SQLSTATE: 42602
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06985: "could not truncate file '%s' to %u: %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06986: "could not seek to the end of file '%s': %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06987: "could not parse filename '%s'"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06988: "wrong VM buffer passed to visibilitymap_set"
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06989: "attempt to delete tuple containing indirect datums"
+
+SQLSTATE: 29P02
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06990: "shouldn't be called for indirect tuples"
+
+SQLSTATE: 29P02
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-06991 - GAUSS-07000
+
+<br/>
+
+GAUSS-06991: "attempted to kill a tuple inserted by another transaction: %lu, %lu"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06992: "Can't fit xid into page. relation '%s', now xid is %lu, base is %lu, min is %u, max is %u"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06993: "Can't fit xid into page, now xid is %lu, base is %lu, min is %u, max is %u"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06994: "heap_delete: invalid tid %hu, max tid %hu, rnode[%u,%u,%u], block %u"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06995: "attempted to delete self created tuple"
+
+SQLSTATE: 40001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06996: "pg_class entry for relid %u vanished during ExtractReplicaIdentity"
+
+SQLSTATE: 40001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06997: "heap_update: invalid tid %hu, max tid %hu, rnode[%u,%u,%u], block %u"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06998: "attempted to update self created tuple"
+
+SQLSTATE: 40001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-06999: "relation '%s' has one big row which is not supported under 64bits XID system. Current xid is %lu"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07000: "relation '%s' has no free space to upgrade. Current xid is %lu, please VACUUM FULL this relation!!!"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/71-GAUSS-07001-GAUSS-07100.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/71-GAUSS-07001-GAUSS-07100.md
new file mode 100644
index 0000000000000000000000000000000000000000..6d6628fe37b691bcfdcc37d674b689d02e547e9b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/71-GAUSS-07001-GAUSS-07100.md
@@ -0,0 +1,868 @@
+---
+title: GAUSS-07001 - GAUSS-07100
+summary: GAUSS-07001 - GAUSS-07100
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-07001 - GAUSS-07100
+
+<br/>
+
+## GAUSS-07001 - GAUSS-07010
+
+<br/>
+
+GAUSS-07001: "All built-in functions are hard coded, and they should not be updated."
+
+SQLSTATE: 55000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07002: "system column in index"
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07003: "unexpected result when restoring backup block"
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07004: "heap_multi_insert_redo: total tuple length mismatch"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07005: "heap_inplace_redo: no tuple data"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07006: "heap_redo: unknown op code %hhu"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07007: "heap2_redo: unknown op code %hhu"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07008: "heap3_redo: unknown op code %hhu"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07009: "partition %u is invalid"
+
+SQLSTATE: 29P04
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07010: "Invalid arguments for function btgettuple"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07011 - GAUSS-07020
+
+<br/>
+
+GAUSS-07011: "version mismatch in index '%s': file version %u, code version %d"
+
+SQLSTATE: XX002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07012: "failed to add old item to left page after split"
+
+SQLSTATE: XX002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07013: "btree_redo: unknown op code %hhu"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07014: "Failed to check input value: invalid token '%s'.\n"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07015: "invalid client_crt_filepath length %lu"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07016: "Fail to list bucket object in node:%s with error code: %s, %s the bucket name: %s, prefix name: %s"
+
+SQLSTATE: 29000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07017: "Datanode '%s' fail to read OBS object bucket:'%s' key:'%s' with OBS error code:%s %s"
+
+SQLSTATE: 29000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07018: "Fail to flush data content to OBS in buffile offset ['%d'] to_write ['%d']"
+
+SQLSTATE: 29P03
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07019: "Datanode '%s' fail to seek buffer file be (0, 0) after reset actual length"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07020: "Datanode '%s' fail to write OBS object %s with OBS error code:%s %s"
+
+SQLSTATE: 29000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07021 - GAUSS-07030
+
+<br/>
+
+GAUSS-07021: "Node '%s' fail to initialize libobs with OBS error code:%s"
+
+SQLSTATE: 29000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07022: "unsupported operation in OBS handler layer"
+
+SQLSTATE: HV00B
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07023: "OBS URL's %s is not valid '%s'"
+
+SQLSTATE: HV00E
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07024: "Fail to connect OBS host %s in node:%s with error code: %s %s"
+
+SQLSTATE: 29000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07025: "failed to add item of size %d to SPGiST index page"
+
+SQLSTATE: XX002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07026: "reconstrValue is NULL but level = %d (not zero)."
+
+SQLSTATE: XX002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07027: "variable page should not be NULL"
+
+SQLSTATE: XX005
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07028: "sem_destroy failed: %m"
+
+SQLSTATE: DB001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07029: "[REDO_LOG_TRACE]ApplyReadyTxnShareLogRecords encounter fatal error:rmgrID:%u, info:%u, sharcount:%u"
+
+SQLSTATE: DB001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07030: "[REDO_LOG_TRACE]ApplyReadyTxnShareLogRecords encounter fatal error:rmgrID:%u, info:%u, sharcount:%u, refcount:%u"
+
+SQLSTATE: DB001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07031 - GAUSS-07040
+
+<br/>
+
+GAUSS-07031: "[REDO_LOG_TRACE]ApplyReadyTxnShareLogRecords encounter fatal error:rmgrID:%u, info:%u, designatedWorker:%u"
+
+SQLSTATE: DB001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07032: "[REDO_LOG_TRACE]ApplyReadyAllShareLogRecords encounter fatal error:rmgrID:%u, info:%u, sharcount:%u"
+
+SQLSTATE: DB001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07033: "[REDO_LOG_TRACE]ApplyReadyAllShareLogRecords encounter fatal error:rmgrID:%u, info:%u, sharcount:%u, refcount:%u"
+
+SQLSTATE: DB001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07034: "[REDO_LOG_TRACE]ApplyMultiPageAllWorkerRecord encounter fatal error:rmgrID:%u, info:%u"
+
+SQLSTATE: DB001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07035: "[REDO_LOG_TRACE]ApplyMultiPageShareWithTrxnRecord encounter fatal error:rmgrID:%u, info:%u, designatedWorker:%u"
+
+SQLSTATE: DB001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07036: "[REDO_LOG_TRACE]ApplyMultiPageShareWithTrxnRecord encounter fatal error:rmgrID:%u, info:%u"
+
+SQLSTATE: DB001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07037: "WaitWorkerReady failed, no worker is ready for work. totalWorkerCount :%u"
+
+SQLSTATE: DB001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07038: "CheckAlivePageWorkers: thread %lu is still alive"
+
+SQLSTATE: DB001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07039: "[REDO_LOG_TRACE]StartPageRedoWorkers we need at least one worker thread"
+
+SQLSTATE: DB001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07040: "[REDO_LOG_TRACE]DispatchRedoRecord encounter fatal error:rmgrID:%u, info:%u, indexid:%u"
+
+SQLSTATE: DB001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07041 - GAUSS-07050
+
+<br/>
+
+GAUSS-07041: "[REDO_LOG_TRACE]AddWorkerToSet:input work id error, id:%u, work num %u"
+
+SQLSTATE: DB001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07042: "Allocated record buffer failed!, cur item:%u, max item:%u"
+
+SQLSTATE: DB001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07043: "Allocated blocks data failed!, cur item:%u, max item:%u"
+
+SQLSTATE: DB001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07044: "Allocated main_data failed!, cur item:%u, max item:%u"
+
+SQLSTATE: DB001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07045: "NewReaderState Dispatch is null"
+
+SQLSTATE: DB001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07046: "Must be system admin or operator admin in operation mode to get cbm merged file."
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07047: "memory is temporarily unavailable while allocate block string"
+
+SQLSTATE: 53000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07048: "Negative timeout for force track cbm!"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07049: "Timeout happened during force track cbm!"
+
+SQLSTATE: YY004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07050: "start xlog location %X/%X should be smaller than end xlog location %X/%X"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07051 - GAUSS-07060
+
+<br/>
+
+GAUSS-07051: "end xlog location %X/%X should be smaller than already tracked xlog location %X/%X"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07052: "cannot mark transaction %lu committed without CSN %lu"
+
+SQLSTATE: 58030
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07053: "pg_csnlog contains invalid entry: xid %lu points to parent xid %lu"
+
+SQLSTATE: 58030
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07054: "csn log state change from %lu to %lu is not allowed!"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07055: "Snapshot too old when read CSN, this is a safe errorif there is breakdown in gtm of CN log"
+
+SQLSTATE: YY014
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07056: "Initialize the csn log failed."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07057: "the current transaction %lu is smaller than gtm recent global xmin, so no need to set csn log. pageno: %ld, startExtendCSNLogPage: %ld"
+
+SQLSTATE: YY014
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07058: "The lastExtenPage %ld is larger than newExtendPage %ld,and the newestXact is %lu, the recent global xmin %lu"
+
+SQLSTATE: YY014
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07059: "Length of CBM file home path exceeds MAXPGPATH!"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07060: "Length of absolute CBM file path would exceed MAXPGPATH!"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07061 - GAUSS-07070
+
+<br/>
+
+GAUSS-07061: "memory is temporarily unavailable while allocate page read buffer during validate CBM file"
+
+SQLSTATE: 53000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07062: "Failed to truncate CBM file '%s' to length %ld"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07063: "could not create new CBM file '%s': %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07064: "could not open CBM file '%s': %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07065: "failed to stat current cbm file %s :%m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07066: "The xlog LSN to be parsed %08X/%08X is smaller than already tracked xlog LSN %08X/%08X. This may be caused by xlog truncation (pg_rewind), xlog corruption or PITR (at present CBM does not support multiple timelines). Under these scenarios, inconsistent CBM files may be created. To be safe, we zap all existing CBM files and restart CBM tracking"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07067: "memory is temporarily unavailable while allocate xlog reader"
+
+SQLSTATE: 53000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07068: "could not read WAL record at %08X/%08X: %s"
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07069: "could not read WAL record at %08X/%08X"
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07070: "could not find or create CBM page entry: rel %u/%u/%u forknum %d blkno %u page type %d truncate blkno %u"
+
+SQLSTATE: 29P02
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07071 - GAUSS-07080
+
+<br/>
+
+GAUSS-07071: "memory is temporarily unavailable while allocate new CBM page"
+
+SQLSTATE: 53000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07072: "could not create dummy CBM page entry: rel %u/%u/%u forknum %d"
+
+SQLSTATE: 29P02
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07073: "memory is temporarily unavailable while allocate CBM page header array"
+
+SQLSTATE: 53000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07074: "CBM hash table corrupted"
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07075: "fsync CBM file '%s' failed during flushing"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07076: "close CBM file '%s' failed during rotate"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07077: "found invalid CBM file name'%s' before rotate"
+
+SQLSTATE: 42602
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07078: "could not rename file '%s' to '%s' during rotate: %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07079: "could not open CBM file directory '%s': %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07080: "could not find valid CBM file between %08X/%08X and %08X/%08X, which may be caused by previous CBM switch-off, truncation, or corruption"
+
+SQLSTATE: 58P03
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07081 - GAUSS-07090
+
+<br/>
+
+GAUSS-07081: "could not find valid CBM file that contains the merging start point %08X/%08X"
+
+SQLSTATE: 58P03
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07082: "could not find valid CBM file that contains the merging end point %08X/%08X"
+
+SQLSTATE: 58P03
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07083: "there is a gap between CBM file %s and %s, which may be caused by previous CBM switch-off, truncation, or corruption"
+
+SQLSTATE: 29P02
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07084: "memory is temporarily unavailable while allocate page read buffer during merge CBM file array"
+
+SQLSTATE: 53000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07085: "could not open CBM file '%s' while merging: %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07086: "could not find merge start point %08X/%08X in CBM files "
+
+SQLSTATE: 29P02
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07087: "could not find merge end point %08X/%08X in CBM files, the last cbm page end at %08X/%08X"
+
+SQLSTATE: 29P02
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07088: "could not read the first page head of CBM file '%s' "
+
+SQLSTATE: 29P02
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07089: "the first page start LSN %08X/%08X of CBM file '%s' does not equal the file start LSN %08X/%08X"
+
+SQLSTATE: 29P02
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07090: "partial page read occurs at page offset %ld of CBM file '%s', stop reading"
+
+SQLSTATE: 58P03
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07091 - GAUSS-07100
+
+<br/>
+
+GAUSS-07091: "Corruption detected in CBM file '%s', page offset %ld"
+
+SQLSTATE: 58P03
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07092: "LSN track gap detected in CBM file '%s', page offset %ld: previous page batch end LSN is %08X/%08X, current page batch start LSN is %08X/%08X"
+
+SQLSTATE: 29P02
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07093: "Inconsistent start/end LSN in one page batch for CBM file '%s' at page offset %ld: previous page start-end LSN %08X/%08X-%08X/%08X, curent page start-end LSN %08X/%08X-%08X/%08X"
+
+SQLSTATE: 29P02
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07094: "the last read page end LSN %08X/%08X of CBM file '%s' does not equal the file end LSN %08X/%08X"
+
+SQLSTATE: 29P02
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07095: "could not find or create CBM page entry: rel %u/%u/%u forknum %d during merge into hash"
+
+SQLSTATE: 58P03
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07096: "invalid CBM page header: rel %u/%u/%u forknum %d first blkno %u page type %d truncate blkno %u"
+
+SQLSTATE: 29P02
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07097: "could not create merge dest CBM file '%s': %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07098: "memory is temporarily unavailable while allocate CBM array"
+
+SQLSTATE: 53000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07099: "memory is temporarily unavailable while allocate CBM array entry"
+
+SQLSTATE: 53000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07100: "CBM hash table corrupted: incorrect total hash entry number"
+
+SQLSTATE: 29P02
+
+Description:Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/72-GAUSS-07101-GAUSS-07200.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/72-GAUSS-07101-GAUSS-07200.md
new file mode 100644
index 0000000000000000000000000000000000000000..5ee9b90c579c78bdd049332dce858587ad6165cf
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/72-GAUSS-07101-GAUSS-07200.md
@@ -0,0 +1,868 @@
+---
+title: GAUSS-07101 - GAUSS-07200
+summary: GAUSS-07101 - GAUSS-07200
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-07101 - GAUSS-07200
+
+<br/>
+
+## GAUSS-07101 - GAUSS-07110
+
+<br/>
+
+GAUSS-07101: "memory is temporarily unavailable while allocate CBM block array"
+
+SQLSTATE: 53000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07102: "could not force tracking cbm because cbm tracking function is not enabled!"
+
+SQLSTATE: 55000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07103: "the current valid prepared xid list or the next valid prepared list should not be NULL"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07104: "Invalid prepared list lenth: %d"
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07105: "could not read two-phase state from xlog at %X/%X, errormsg: %s"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07106: "expected two-phase state data is not present in xlog at %X/%X"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07107: "invalid twophase resource manager lock id"
+
+SQLSTATE: 29000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07108: "cannot commit prepared transaction %lu, it was already aborted"
+
+SQLSTATE: 25000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07109: "cannot abort prepared transaction %lu, it was already committed"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07110: "Can not connect to gtm when getting gxid, there is a connection error."
+
+SQLSTATE: 08000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07111 - GAUSS-07120
+
+<br/>
+
+GAUSS-07111: "GTM Mode: remote node sub xact can not get gxid directly from gtm"
+
+SQLSTATE: 25000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07112: "GTM Mode: remote node sub xact xid should be larger than parent xid."
+
+SQLSTATE: 25000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07113: "GTM-FREE-MODE: latestCompletedXid %lu larger than next alloc xid %lu."
+
+SQLSTATE: 25000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07114: "cannot have more than 2^32-2 commands in a transaction"
+
+SQLSTATE: 54000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07115: "Node %s: prepare gid is %s, and top xid is %lu, different transaction!"
+
+SQLSTATE: 25000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07116: "Failed to receive GTM commit transaction response after CN local PREPARE TRANSACTION '%s'."
+
+SQLSTATE: 08000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07117: "AbortCurrentTransaction: unexpected state %s"
+
+SQLSTATE: 25000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07118: "non-execute cn or dn: there is already a transaction in progress"
+
+SQLSTATE: 25001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07119: "AbortOutOfAnyTransaction reserving top xact abort: unexpected state %s"
+
+SQLSTATE: 25000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07120: "SUBXACT_TEST %s: Commit subtransaction %s before notice GTM failed."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07121 - GAUSS-07130
+
+<br/>
+
+GAUSS-07121: "xactWillRemoveRelFiles: unknown op code %u"
+
+SQLSTATE: DB001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07122: "the proc group is corrupted, the head is %u, the wakeidx is %u, localProc %p, proc %p, WALInsertLocks %p."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07123: "space reserved for WAL record does not match what was written"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07124: "could not find WAL buffer for %X/%X"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07125: "could not seek in log file %s to offset %u: %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07126: "could not write to log file %s at offset %u, length %lu: %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07127: "could not open file '%s' (log segment %s): %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07128: "lseek2:could not seek in log file %s to offset %u: %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07129: "could not open xlog file '%s' (log segment %s): %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07130: "could not close log file %s: %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07131 - GAUSS-07140
+
+<br/>
+
+GAUSS-07131: "could not parse xlog segment file '%s'"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07132: "recover failed could not open control file '%s': %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07133: "recover failed could not write to control file: %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07134: "recover failed could not fsync control file: %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07135: "recover failed could not close control file: %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07136: "nNumaNodes is zero."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07137: "XLOGShmemInit num_xloginsert_locks should be multiple of NUMA node number in the system."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07138: "XLOGShmemInit could not alloc memory on node %d"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07139: "cann't read a random number from file '/dev/urandom'."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07140: "could not open file '%s'"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07141 - GAUSS-07150
+
+<br/>
+
+GAUSS-07141: "lseek file error '%s' "
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07142: "could not write file '%s' "
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07143: "could not fsync file '%s' "
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07144: "could not close file '%s' "
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07145: "hot standby is not possible because wal_level was not set to 'hot_standby' or higher on the master server"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07146: "old version XLog must be shutdown checkpoint or online checkpoint."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07147: "redo can not support old version!!!!"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07148: "there are some received xlog have not been redo the tail of last redo lsn:%X/%X, received lsn:%X/%X"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07149: "curMinRecLSN little prev checkpoint lsn is %08X/%08X,now lsn is %08X/%08X"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07150: "current dirty page list head recLSN %08X/%08X smaller than redo lsn %08X/%08X"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07151 - GAUSS-07160
+
+<br/>
+
+GAUSS-07151: "unexpected XLogReadBufferForRedo result when restoring backup block"
+
+SQLSTATE: 20000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07152: "could not fsync log segment %s: %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07153: "could not fsync log file %s: %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07154: "could not fsync write-through log file %s: %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07155: "could not fdatasync log file %s: %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07156: "failed to stat %s file:%m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07157: "must be system admin or replication role or operator admin in operation mode to run a backup"
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07158: "file size is wrong, '%s': %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07159: "the file is not exist '%s': %m"
+
+SQLSTATE: 55000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07160: "failed to touch %s file during enable xlog delay: %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07161 - GAUSS-07170
+
+<br/>
+
+GAUSS-07161: "could not remove %s file: %m. This will lead to residual of stale xlog segments"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07162: "could not open rewind file: %s\n"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07163: "could not enable delay ddl when enable_cbm_tracking is off!"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07164: "could not remove %s file: %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07165: "failed to write %s file during enable delay ddl recycle"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07166: " could not disable delay ddl when enable_cbm_tracking is off!"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07167: "valid input lsn is not supported while doing forceful disable delay ddl"
+
+SQLSTATE: 20000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07168: "failed to write %s file during disable delay ddl recycle"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07169: "could not remove %s file after write failure: %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07170: "Failed to get cbm information during execute delayed DDL: %s"
+
+SQLSTATE: 20000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07171 - GAUSS-07180
+
+<br/>
+
+GAUSS-07171: "could not remove %s file before unlink col relation files: %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07172: "mpfl_pwrite_file failed, MPFL_FILE_SIZE %d, offset %ld, write_size %d"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07173: "mpfl_pwrite_file: Write file error"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07174: "mpfl_pwrite_file: Write file size mismatch: expected %d, written %d"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07175: "Could not remove max_flush_lsn file"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07176: "Could not create file '%s'"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07177: "Could not open file '%s'"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07178: "maximum number of WAL record block references exceeded"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07179: "too many registered buffers"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07180: "too much WAL data"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07181 - GAUSS-07190
+
+<br/>
+
+GAUSS-07181: "no block with id %d registered with WAL insertion"
+
+SQLSTATE: 55000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07182: "invalid xlog info mask %hhx"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07183: "invalid page header in block %u, spc oid %u db oid %u relfilenode %u"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07184: "xlog record length is %u, more than XLogRecordMaxSize %u"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07185: "Must be system admin or operator admin in operation mode to control xlog delay function."
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07186: "Must be system admin or operator admin in operation mode to switch transaction log files."
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07187: "Must be system admin or operator admin in operation mode to create a restore point."
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07188: "Must be system admin or operator admin in operation mode to control recovery."
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07189: "Must be system admin or operator admin in operation mode to control ddl delay function."
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07190: "could not parse xlog location '%s'"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07191 - GAUSS-07200
+
+<br/>
+
+GAUSS-07191: "Must be system admin or operator admin in operation mode to control resume_bkp_flag function."
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07192: "could not close log file %u, segment %lu: %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07193: "[REDO_LOG_TRACE]WAL contains references to invalid pages, count:%u"
+
+SQLSTATE: DB001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07194: "can not get xlog lsn from record page block %hhu lsn %lu"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07195: "lsn check error, lsn in record (%lu) ,lsn in current page %lu, page info:%u/%u/%u block %hhu forknum %d lsn %lu blknum:%u"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07196: "failed to locate backup block with ID %d"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07197: "block with WILL_INIT flag in WAL record must be zeroed by redo routine"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07198: "block to be initialized in redo routine must be marked with WILL_INIT flag in the WAL record"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07199: "failed to restore block image"
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07200: "could not seek in log segment %s to offset %u: %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/73-GAUSS-07201-GAUSS-07300.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/73-GAUSS-07201-GAUSS-07300.md
new file mode 100644
index 0000000000000000000000000000000000000000..45bd8f0c9d8a66ee6091ea2d169d45c2f351b9a7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/73-GAUSS-07201-GAUSS-07300.md
@@ -0,0 +1,868 @@
+---
+title: GAUSS-07201 - GAUSS-07300
+summary: GAUSS-07201 - GAUSS-07300
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-07201 - GAUSS-07300
+
+<br/>
+
+## GAUSS-07201 - GAUSS-07210
+
+<br/>
+
+GAUSS-07201: "could not read from log segment %s, offset %u, length %d, readbytes %d: %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07202: "Incorrect xid status %d"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07203: "CLOG STATUS ERROR: xid %lu status %s"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07204: "CLOG PAGE STATUS ERROR: xid %lu status %s"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07205: "CLOG STATUS ERROR: xid: %lu input status %s, current status %s"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07206: "clog pageno should be >= 0"
+
+SQLSTATE: 42804
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07207: "slru zero page under %s"
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07208: "slru read page under %s"
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07209: "slru write page under %s"
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07210: "could not access status of transaction %lu , nextXid is %lu "
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07211 - GAUSS-07220
+
+<br/>
+
+GAUSS-07211: "Read file error"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07212: "Read file size mismatch: expected %d, read %d"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07213: "Write file error"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07214: "Write file size mismatch: expected %d, written %d"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07215: "Seek file error"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07216: "DW extend file failed, expected_file_size %ld, offset %ld, extend_size %ld"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07217: "DW verify checksum: page checksum flag is wrong"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07218: "DW check file size failed, expected_size %ld, actual_size %ld"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07219: "File header is broken"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07220: "Could not truncate dw file during startup!"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07221 - GAUSS-07230
+
+<br/>
+
+GAUSS-07221: "DW file close failed"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07222: "Could not remove the residual DW file"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07223: "DW file does not exist"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07224: "Double write not initialized"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07225: "Double write already closed"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07226: "Memory allocation failed.\n"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07227: "invalid forkNum %d, should be less than %d"
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07228: "invalid page in block %u of relation %s, remote read data corrupted"
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07229: "buffer is dirty but not in dirty page queue in InvalidateBuffer"
+
+SQLSTATE: XX010
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07230: "[exception] private ref->refcount is %d in UnpinBuffer"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07231 - GAUSS-07240
+
+<br/>
+
+GAUSS-07231: "buffer is dirty but not in dirty page queue in TerminateBufferIO_common"
+
+SQLSTATE: XX010
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07232: "TerminateBufferIO_common, dirty page queue is full when trying to push buffer to the queue"
+
+SQLSTATE: XX010
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07233: "remote not available"
+
+SQLSTATE: 58030
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07234: "remote read failed from %s, %s"
+
+SQLSTATE: 58030
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07235: "local buffer hash table corrupted."
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07236: "block %u of %s is still referenced (local %d)"
+
+SQLSTATE: XX011
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07237: "fork number should not be less than zero"
+
+SQLSTATE: 2202E
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07238: "could not initialize local buffer hash table."
+
+SQLSTATE: D0014
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07239: "shared buffer hash table corrupted."
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07240: "Found invalid error recored: negative length that is not -1."
+
+SQLSTATE: OP002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07241 - GAUSS-07250
+
+<br/>
+
+GAUSS-07241: "Found invalid error recored: length is not the same as the attribute length."
+
+SQLSTATE: OP002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07242: "LOCATION is required for the foreign tables"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07243: "if the number of gds is greater than dn , query dop should not be greater than one."
+
+SQLSTATE: HV000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07244: "invalid timestamp string length"
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07245: "Unsupport distribute type."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07246: "It is not allowed to create partition on this foreign table."
+
+SQLSTATE: HV000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07247: "Invalid URL '%s' in trimed LOCATION"
+
+SQLSTATE: HV000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07248: "out_filename_prefix should not be empty"
+
+SQLSTATE: OP0A3
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07249: "out_filename_prefix is not supposed to contain '%c'"
+
+SQLSTATE: OP0A3
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07250: "out_filename_prefix is not supposed to be '%s'"
+
+SQLSTATE: OP0A3
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07251 - GAUSS-07260
+
+<br/>
+
+GAUSS-07251: "Only alphanumeric characters and \'_\' is allowed in out_filename_prefix option"
+
+SQLSTATE: OP0A3
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07252: "out_fix_alignment is only allowed with fixed format"
+
+SQLSTATE: OP0A3
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07253: "Only 'align_left' and 'align_right' is allowed in out_fix_alignment option"
+
+SQLSTATE: OP0A3
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07254: "Do not allow to set region option when the 'gsobs' prefix is specified for the location option."
+
+SQLSTATE: HV002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07255: "OBS foreign table does not support '%s' option"
+
+SQLSTATE: OP0A3
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07256: "OBS foreign table does not support remote_log option"
+
+SQLSTATE: OP0A3
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07257: "OBS foreign table have to specify '%s' option"
+
+SQLSTATE: OP0A3
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07258: "This OBS foreign table only supports CSV/TEXT format"
+
+SQLSTATE: OP0A3
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07259: "Invalid 'encrypt' option value '%s' for OBS foreign table"
+
+SQLSTATE: OP0A3
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07260: "Invalid 'chunksize' option value '%s', only numeric value can be set"
+
+SQLSTATE: OP0A3
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07261 - GAUSS-07270
+
+<br/>
+
+GAUSS-07261: "Invalid 'chunksize' option value '%s' for OBS Read-Only table, valid range [8, 512] in MB"
+
+SQLSTATE: OP0A3
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07262: "Option 'chunksize' is not allowed in OBS write-only table"
+
+SQLSTATE: OP0A3
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07263: "None OBS foreign table does not support '%s' option"
+
+SQLSTATE: OP0A3
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07264: "Shared mode and private mode are only available for the supper user and Operatoradmin"
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07265: "Invalid key string"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07266: "obs option chunksize is too large"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07267: "No free Cache Blocks! cstore_buffers maybe too small, scanned=%d, pinned=%d, unpinned=%d, invalid=%d, looped=%d, reserved=%d, freepinned = %d, start=%d, max=%d. RequestSize = %d, CurrentSize = %ld, BufferMaxSize = %ld."
+
+SQLSTATE: 53500
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07268: "complete IO, slot(%d), flag(%d)"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07269: " palloc size to big, size(%ld)."
+
+SQLSTATE: 53200
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07270: "Unsupported data type in column storage"
+
+SQLSTATE: 42804
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07271 - GAUSS-07280
+
+<br/>
+
+GAUSS-07271: "malloc fails, out of memory: size %lu"
+
+SQLSTATE: 53200
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07272: "unsupported data type length %d of column '%s' of relation '%s' "
+
+SQLSTATE: 42804
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07273: "Cannot load CUDesc and CU for a dropped column '%s' of table '%s'"
+
+SQLSTATE: D0011
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07274: "fail to remote read CU, data corrupted in network"
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07275: "Cannot to fill unsupported system column %d for column store table"
+
+SQLSTATE: 42804
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07276: "Cannot save CUDesc for a dropped column '%s' of table '%s'"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07277: "Cannot fill VecBatch for a dropped column '%s' of table '%s'"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07278: "compression unit descriptor not found, table(%s), column(%s), relfilenode(%u/%u/%u), cuid(%u))."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07279: "CU Delete bitmap is missing."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07280: "Cannot get CUData for a dropped column '%s' of table '%s'"
+
+SQLSTATE: D0011
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07281 - GAUSS-07290
+
+<br/>
+
+GAUSS-07281: "Load CU failed in adio! table(%s), column(%s), relfilenode(%u/%u/%u), cuid(%u)"
+
+SQLSTATE: 58030
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07282: "invalid CU in cu_id %u of relation %s file %s offset %lu, prefetch %s"
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07283: "invalid CU in cu_id %u of relation %s file %s offset %lu, sync load %s"
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07284: "There is an IO error when remote read CU in cu_id %u of relation %s file %s offset %lu. slotId %d, column '%s' "
+
+SQLSTATE: 58030
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07285: "invalid CU in cu_id %u of relation %s file %s offset %lu, remote read %s"
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07286: "compression unit descriptor(talbe '%s', column '%s', cuid %u) not found"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07287: "The delta table's definition is not the same with main relation, please use pg_sync_cstore_delta to adjust it."
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07288: "This query is not supported by optimizer in CStore."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07289: "The max insert memory is too small, it may occur endless loop. The used memory is %lu, the controlled memory limit is %dKB, the partition relation is %s, the flush partition id is %d."
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07290: "Invalid partition value cache record."
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07291 - GAUSS-07300
+
+<br/>
+
+GAUSS-07291: "Relation \'%s\' virtual cudesc tuple(cuid %u) not found"
+
+SQLSTATE: 02000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07292: "failed to remotely read CU, data corrupted in network"
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07293: "invalid CU in cu_id %u of relation %s file %s offset %lu"
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07294: "Invalid original partition name"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07295: "cannot merge partition bacause partition %s has unusable local index"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07296: "cache lookup failed for relation: %u"
+
+SQLSTATE: 29P01
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07297: "inititalSize is too large: initialSize(%u), m_bpNullRawSize(%u)"
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07298: "the CRC32C checksum are different between SSE42 (0x%x) and SB8 (0x%x)."
+
+SQLSTATE: 42804
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07299: "Find invalid compressed buffer or invalid CU while uncompressing."
+
+SQLSTATE: 53200
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07300: "CU size error, %u in CU descriptor but %u in CU header"
+
+SQLSTATE: 53200
+
+Description:Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/74-GAUSS-07301-GAUSS-07400.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/74-GAUSS-07301-GAUSS-07400.md
new file mode 100644
index 0000000000000000000000000000000000000000..9e1ea028d3e07b1e1c583ae3316c1d0a2da56ce3
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/74-GAUSS-07301-GAUSS-07400.md
@@ -0,0 +1,868 @@
+---
+title: GAUSS-07301 - GAUSS-07400
+summary: GAUSS-07301 - GAUSS-07400
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-07301 - GAUSS-07400
+
+<br/>
+
+## GAUSS-07301 - GAUSS-07310
+
+<br/>
+
+GAUSS-07301: "this->m_srcDataSize is too large: %u"
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07302: "No cache found when print data cache slot leak warning: slotId:%d"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07303: "validate user defined attribute failed!"
+
+SQLSTATE: 42P24
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07304: "CU partial write, file '%s', offset(%lu), total(%d), expected(%d), actual(%d): %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07305: "could not extend file '%s', offset(%lu), total(%d), expected(%d), actual(%d): %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07306: "read file '%s' failed, %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07307: "some data are read from '%s', offset(%lu), load size(%d), expected read(%d), actual read(%d)"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07308: "could not read file '%s', offset(%lu), load size(%d), expected read(%d), actual read(%d): %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07309: "write file '%s' failed in savecu!"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07310: "write file '%s' failed in OverwriteCU!"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07311 - GAUSS-07320
+
+<br/>
+
+GAUSS-07311: "read file '%s' failed in load!"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07312: "unexpected cu file read info: offset(%lu), size(%d), readFileId(%d), readOffset(%lu), expect_read_size(%d)."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07313: "read file '%s' failed, offset(%lu), size(%d), expect_read_size(%d), acture_read_size(%d), maybe you should upgrade cstore data files first"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07314: "could not read file '%s', offset(%lu), size(%d), expect_read_size(%d), acture_read_size(%d): %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07315: "read file '%s' failed in wsload!"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07316: "invalid size(%u) in CUStorage::LoadCU"
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07317: "CUStorage::LoadCU size = 0"
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07318: "Invalid tupleSortState, tupleSlot, or sorting strategy while getting tuple in cstore psort."
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07319: "memory alloc failed"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07320: "build global OBS connect cache hash table failed"
+
+SQLSTATE: 42704
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07321 - GAUSS-07330
+
+<br/>
+
+GAUSS-07321: "could not initialize OBS connector hash table"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07322: "dfs forign server type error. type = %d"
+
+SQLSTATE: 42P17
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07323: "wait IO find an error when allocate meta block, slotID(%d), spcID(%u),dbID(%u), relID(%u), fileID(%d), stripeOrBlocketID(%u), columnID(%u)"
+
+SQLSTATE: P0002
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07324: "could not write to temporary file: the file size exceeds the max size: %ldBYTE"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07325: "could not write to temporary file: %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07326: "could not read from temporary file: %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07327: "could not munmap() while flushing data: %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07328: "unable to open process pid directory '%s'"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07329: "out of file descriptors: %m; release and retry"
+
+SQLSTATE: 53000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07330: "io_submit() async read failed %d, dispatch count(%d)"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07331 - GAUSS-07340
+
+<br/>
+
+GAUSS-07331: "io_submit() async write failed %d, dispatch count(%d)"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07332: "FileAsyncCUClose : invalid vfd(%d), SizeVfdCache(%lu)"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07333: "io_submit() async cu read failed %d, dispatch count(%d)"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07334: "io_submit() async cu write failed %d, dispatch count(%d)"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07335: "FileAccess() extend file failed %d"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07336: "exceeded MAX_ALLOCATED_DESCS while trying to open file '%s'"
+
+SQLSTATE: 54000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07337: "Allocate dir failed."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07338: "sorry, too many reserve thread already lastreserveBackend:%d, maxreserveBackends:%d"
+
+SQLSTATE: 53300
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07339: "sorry, session index isnot valid index:%d, maxreserveBackends:%d, maxBackends:%d"
+
+SQLSTATE: 53300
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07340: "sorry, session slot isnot valid:%d, maxreserveBackends:%d, maxBackends:%d"
+
+SQLSTATE: 53300
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07341 - GAUSS-07350
+
+<br/>
+
+GAUSS-07341: "standby_redo: unknown op code %hhu"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07342: "wait transaction %lu sync time exceed %d s."
+
+SQLSTATE: YY003
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07343: "Snapshot is invalid at %s, this is a safe error if there is breakdown in gtm log"
+
+SQLSTATE: YY014
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07344: "Out of memory at palloc memory for xids!"
+
+SQLSTATE: 53200
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07345: "GTM error, could not obtain valid gtm snapshot status."
+
+SQLSTATE: 08006
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07346: "Snapshot is invalid, snaphot type %s, snapshot csn: %lu."
+
+SQLSTATE: YY014
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07347: "Snapshot is invalid, this is a safe error, snapshot too old."
+
+SQLSTATE: YY014
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07348: "GTM error, could not obtain snapshot_status, please check GTM is running or failovering."
+
+SQLSTATE: 08006
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07349: "invalid offset num:%d"
+
+SQLSTATE: 42704
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07350: "Too many visited procs."
+
+SQLSTATE: 53300
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07351 - GAUSS-07360
+
+<br/>
+
+GAUSS-07351: "no more LWLocks available"
+
+SQLSTATE: 55P03
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07352: "force thread %lu to exit because of lwlock deadlock"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07353: "queueing for lock while waiting on another one"
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07354: "lock %s is not held"
+
+SQLSTATE: 55P03
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07355: "InitNuma NUMA is not available"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07356: "InitProcGlobal NUMA memory allocation in node %d failed."
+
+SQLSTATE: 53200
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07357: "Too many clients already, active/non-active: %d/%d."
+
+SQLSTATE: 53300
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07358: "InitProcess numa_run_on_node_mask failed. errno:%d "
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07359: "failed to acquire mutex lock for deleMemContextMutex."
+
+SQLSTATE: 55P03
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07360: "failed to release mutex lock for deleMemContextMutex."
+
+SQLSTATE: 55P03
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07361 - GAUSS-07370
+
+<br/>
+
+GAUSS-07361: "all &g_instance.proc_aux_base are in use"
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07362: "there remain unreleased locks when process exists."
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07363: "could not disable timer for reset txn xmin in Read Committed Mode."
+
+SQLSTATE: 58000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07364: "unrecognized lock method: %hu"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07365: "Failed to allocate memory for lockOwners."
+
+SQLSTATE: 53200
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07366: "newproc should not be null"
+
+SQLSTATE: XX005
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07367: "GetRunningTransactionLocks: index = %d els = %d"
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07368: "proc should not be null"
+
+SQLSTATE: XX005
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07369: "snapshot xmin:%lu is not greater than global xmin:%lu"
+
+SQLSTATE: 55000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07370: "predicate locks hash table corrupted"
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07371 - GAUSS-07380
+
+<br/>
+
+GAUSS-07371: "get parent relation lock's lock tag failed"
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07372: "transfer predicate lock failed"
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07373: "isolation level is not serializable"
+
+SQLSTATE: 25004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07374: "corrupted page pointers: lower = %hu, upper = %hu, special = %hu"
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07375: "corrupted item pointer: %d"
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07376: "corrupted item lengths: total %u, available space %d"
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07377: "invalid index offnum: %hu"
+
+SQLSTATE: 2201X
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07378: "incorrect index offsets supplie"
+
+SQLSTATE: 2201X
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07379: "invalid size of data for block checksum"
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07380: "Can't find the oldest unidentified connection."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07381 - GAUSS-07390
+
+<br/>
+
+GAUSS-07381: "logical decoding requires wal_level >= logical"
+
+SQLSTATE: 55000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07382: "logical decoding requires a database connection"
+
+SQLSTATE: 55000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07383: "cannot perform logical decoding without a acquired slot"
+
+SQLSTATE: 55000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07384: "cannot initialize logical decoding without a specified plugin"
+
+SQLSTATE: 55000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07385: "cannot use physical replication slot created for logical decoding"
+
+SQLSTATE: 55000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07386: "replication slot '%s' was not created in this database"
+
+SQLSTATE: 55000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07387: "cannot create logical replication slot in transaction that has performed writes"
+
+SQLSTATE: 25001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07388: "cannot use physical replication slot for logical decoding"
+
+SQLSTATE: 55000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07389: "Stopped to parse any valid XLog Record at %X/%X: %s."
+
+SQLSTATE: LL001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07390: "writes are only accepted in commit, begin and change callbacks"
+
+SQLSTATE: LL001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07391 - GAUSS-07400
+
+<br/>
+
+GAUSS-07391] : "OutputPluginPrepareWrite needs to be called before OutputPluginWrite"
+
+SQLSTATE: LL001
+
+Description: The **OutputPluginPrepareWrite** function must be called before the **OutputPluginWrite** function is called.
+
+Solution:Contact technical support.
+
+GAUSS-07392: "output plugins have to declare the _PG_output_plugin_init symbol"
+
+SQLSTATE: LL001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07393: "output plugins have to register a change callback"
+
+SQLSTATE: LL001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07394: "output plugins have to register a commit callback"
+
+SQLSTATE: LL001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07395: "unexpected rmgr_id: %u"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07396: "unexpected RM_XLOG_ID record type: %u"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07397: "unexpected RM_XACT_ID record type: %u"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07398: "unexpected RM_STANDBY_ID record type: %u"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07399: "unexpected RM_HEAP2_ID record type: %u"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07400: "unexpected RM_HEAP3_ID record type: %u"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/75-GAUSS-07401-GAUSS-07480.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/75-GAUSS-07401-GAUSS-07480.md
new file mode 100644
index 0000000000000000000000000000000000000000..861800608fb917113236c3f33916366fcb881b59
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/75-GAUSS-07401-GAUSS-07480.md
@@ -0,0 +1,632 @@
+---
+title: GAUSS-07401 - GAUSS-07480
+summary: GAUSS-07401 - GAUSS-07480
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-07401 - GAUSS-07480
+
+<br/>
+
+## GAUSS-07401 - GAUSS-07410
+
+<br/>
+
+GAUSS-07401: "unexpected RM_HEAP_ID record type: %u"
+
+SQLSTATE: XX004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07402: "cannot free a copied snapshot"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07403: "cannot free an active snapshot"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07404: "cannot export a snapshot before reaching a consistent state"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07405: "cannot export a snapshot, not all transactions are monitored anymore"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07406: "cannot export a snapshot when MyPgXact->xmin already is valid"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07407: "cannot export a snapshot from within a transaction"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07408: "can only export one snapshot at a time"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07409: "clearing exported snapshot in wrong transaction state"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07410: "xl_heap_new_cid record without a valid CommandId"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07411 - GAUSS-07420
+
+<br/>
+
+GAUSS-07411: "waiting for ourselves"
+
+SQLSTATE: LL001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07412: "snapbuild state file '%s' has wrong magic %u instead of %d"
+
+SQLSTATE: LL001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07413: "snapbuild state file '%s' has unsupported version %u instead of %d"
+
+SQLSTATE: LL001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07414: "could not read file '%s', read %lu of %lu: %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07415: "could not read file '%s', size overflow"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07416: "snapbuild state file %s: checksum mismatch, is %u, should be %u"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07417: "too much output for sql interface"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07418: "must be superuser or replication role to use replication slots"
+
+SQLSTATE: 42501
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07419: "could not read from log segment %s, offset %u, length %lu: %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07420: "couldn't advance in recovery"
+
+SQLSTATE: 22P02
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07421 - GAUSS-07430
+
+<br/>
+
+GAUSS-07421: "invalid input syntax for type lsn: '%s' of start_lsn"
+
+SQLSTATE: 22P02
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07422: "array must be one-dimensional"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07423: "array must not contain nulls"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07424: "array must be TEXTOID"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07425: "array must have even number of elements"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07426: "could not remove directory '%s'"
+
+SQLSTATE: LL001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07427: "tuplecid value in changequeue"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07428: "output plugin used xid %lu"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07429: "can not found txn which xid = %lu"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07430: "only ever add one set of invalidations"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07431 - GAUSS-07440
+
+<br/>
+
+GAUSS-07431: "txn->subtxns is illegal point"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07432: "could not write to xid %lu's data file: %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07433: "could not read from reorderbuffer spill file: %m"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07434: "incomplete read from reorderbuffer spill file: read %d instead of %u"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07435: "illegality read length %lu"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07436: "could not read from reorderbuffer spill file: read %d instead of %u"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07437: "got sequence entry %u for toast chunk %u instead of seq 0"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07438: "got sequence entry %u for toast chunk %u instead of seq %d"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07439: "fail to get toast chunk"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07440: "unexpected type of toast chunk"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07441 - GAUSS-07450
+
+<br/>
+
+GAUSS-07441: "toast_rel should not be NULL!"
+
+SQLSTATE: LL001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07442: "could not read file '%s', read %d instead of %d"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07443: "could not parse fname %s"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07444: "yyscanner init failed: %m"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07445: "we should be a writer when enable_mix_replication is on"
+
+SQLSTATE: 42P08
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07446: "Insert BCM Info to be interrupted."
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07447: "The got BCM Array index is corrupt: index1 %u index2 %u array_index %u BCMElementArrayOffset1 %X/%X BCMElementArrayOffset2 %X/%X"
+
+SQLSTATE: XX001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07448: "Invalid relation while clearing BCM status: rnode[%u,%u,%u], blocknum[%u], pageoffset[%lu], size[%u], attid[%d]"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07449: "buffer should be valid, but now is %d"
+
+SQLSTATE: 22000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07450: "heap sync hash table not cleaned, num of entries:%ld"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07451 - GAUSS-07460
+
+<br/>
+
+GAUSS-07451: "enable_cbm_tracking must be turn on when enable_mix_replication is on!"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07452: "can't decode in pmState is not run or recovery in progress."
+
+SQLSTATE: LL001
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07453: "cannot use a logical replication slot for physical replication"
+
+SQLSTATE: 55000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07454: "Failed to init the xlog reader for the wal sender."
+
+SQLSTATE: 29000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07455: "walsender stop switchover process for catchup is alive, the process need to be restart"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07456: "terminating Walsender process due to replication timeout.now time(%s) timeout time(%s) last recv time(%s) heartbeat time(%s)"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07457: "syncrep_scanner_yylex_init() failed: %m"
+
+SQLSTATE: 42601
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07458: "invalid replication node index:%d"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07459: "Refuse WAL streaming, connection mode is %d, connertion IP is %s:%d\n"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07460: "terminating walreceiver due to timeout now time(%s) timeout time(%s) last recv time(%s) heartbeat time(%s)"
+
+SQLSTATE: YY004
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07461 - GAUSS-07470
+
+<br/>
+
+GAUSS-07461: "WAL streaming isn't employed to sync all the replication data log."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07462: "the corrupt data total len is %u bytes, the expected len is %lu bytes."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07463: "the unexpected data flag is %X, the expected data flag is 'd'."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07464: "the start xlog employed for the wal data is invalid."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07465: "the end xlog employed for the wal data is invalid."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07466: "the received wal data is unexpected %u bytes at least more than %lu bytes"
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07467: "the received xlog is unexpected %u bytes at least more than %lu bytes."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07468: "fail to push some wal data to the wal streaming writer queue: unexpected wal data flag %c."
+
+SQLSTATE: 22023
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07469: "Unexpected seek in the walreceiver buffer. xlogrecptr is (%X:%X) but local xlogptr is (%X:%X)."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07470: "corrupt wal data write len %u bytes, the expected write data_size %u"
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-07471 - GAUSS-07480
+
+<br/>
+
+GAUSS-07471: "The Row Store Heap Log SHOULD NOT BE synchronized in the WAL Streaming. Tracking the data header info: rnode[%u/%u/%u] blocknum[%u] pageoffset[%lu] size[%u] queueoffset[%u/%u]."
+
+SQLSTATE: 0A000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-07472: "Failed to write the wal data: the database path %s doesn't exist."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/76-GAUSS-50000-GAUSS-50999.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/76-GAUSS-50000-GAUSS-50999.md
new file mode 100644
index 0000000000000000000000000000000000000000..091b793e4e610fa3dc5c0001924231de40b15ed5
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/76-GAUSS-50000-GAUSS-50999.md
@@ -0,0 +1,1100 @@
+---
+title: GAUSS-50000 - GAUSS-50999
+summary: GAUSS-50000 - GAUSS-50999
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-50000 - GAUSS-50999
+
+<br/>
+
+## GAUSS-50000 - GAUSS-50099
+
+<br/>
+
+GAUSS-50000: "Unrecognized parameter: %s."
+
+SQLSTATE: None
+
+Description: Failed to recognize the parameter.
+
+Solution: Check the parameters involved in the error information. An error is reported if the parameters are not those specified in the script to be executed.
+
+GAUSS-50001: "Incorrect parameter. Parameter '-%s' is required"
+
+SQLSTATE: None
+
+Description: The required parameters are missing.
+
+Solution: Check the parameters involved in the error information. An error is reported if the user does not specify a parameter that must be specified in the script to be executed.
+
+GAUSS-50002: "Incorrect parameter. Parameter '-%s' is not required"
+
+SQLSTATE: None
+
+Description: This parameter is unnecessary.
+
+Solution: Check the parameters involved in the error information. An error is reported if the user specifies this parameter, which is not required in the script to be executed.
+
+GAUSS-50003: "The parameter '-%s' type should be %s."
+
+SQLSTATE: None
+
+Description: The parameter type is incorrect.
+
+Solution: Check whether the parameter type in the error information is the specified type.
+
+GAUSS-50004: "The parameter '-%s' value is incorrect."
+
+SQLSTATE: None
+
+Description: The parameter value is incorrect.
+
+Solution: Check whether the parameter value in the error information is correct.
+
+GAUSS-50005: "The parameter '-%s' and '-%s' can not be used together."
+
+SQLSTATE: None
+
+Description: Parameter **A** and parameter **B** cannot be specified simultaneously.
+
+Solution: Check the two parameters involved and the script scenarios to be performed in the error information. Specify only one parameter in the scenarios.
+
+GAUSS-50006: "Too many command-line arguments (first is \"%s\")."
+
+SQLSTATE: None
+
+Description: The number of specified parameters exceeds the required quantity.
+
+Solution: Check whether the number of parameters involved in the error information meets the requirements.
+
+GAUSS-50007: "Failed to set %s parameter."
+
+SQLSTATE: None
+
+Description: GUC parameter settings fail.
+
+Solution: Check whether the parameter settings in **gs_guc** meet the tool requirements.
+
+GAUSS-50008: "Failed to reload parameter."
+
+SQLSTATE: None
+
+Description: Failed to load the parameter.
+
+Solution: Check whether command for loading the parameter is correct.
+
+GAUSS-50009: "Parameter format error."
+
+SQLSTATE: None
+
+Description: The parameter format is incorrect.
+
+Solution: Check whether the parameter format in the command is correct.
+
+GAUSS-50010: "Failed to check %s parameter."
+
+SQLSTATE: None
+
+Description: Failed to check the kernel parameter.
+
+Solution: Check whether the value of the kernel parameter **shared_buffers** or **max_connections** is correct.
+
+GAUSS-50011: "The parameter[%s] value[%s] is invalid."
+
+SQLSTATE: None
+
+Description: The parameter value is invalid.
+
+Solution: Enter the correct parameter.
+
+GAUSS-50012: "The parameter '%s' value can't be empty."
+
+SQLSTATE: None
+
+Description: The parameter cannot be empty.
+
+Solution: Check whether the parameter is empty.
+
+GAUSS-50013: "The parameter '%s' have not been initialized."
+
+SQLSTATE: None
+
+Description: The parameters have not been initialized.
+
+Solution: Check the code logic and initialize the specified parameters.
+
+GAUSS-50014: "Parameters of '%s' can not be empty."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-50015: "The command line parser error: %s."
+
+SQLSTATE: None
+
+Description: An error occurs when the command line parser is executed.
+
+Solution: Correct the command line input parameters based on the error information.
+
+GAUSS-50016: "The re-entrant parameter '-%s' is not same with the previous command."
+
+SQLSTATE: None
+
+Description: The re-entrant parameters are different from the previous ones and the re-entry operation fails.
+
+Solution: Enter the same parameters as those in the last failed operation, or perform rollback before performing a new operation.
+
+GAUSS-50017: "Incorrect value '%s' specified by the parameter '-%s'."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-50018: "The·nodename·%s·upgrade·failed,·please·warm-standby·at·first·for·this·node."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-50100 - GAUSS-50199
+
+<br/>
+
+GAUSS-50100: "The %s is not readable for %s."
+
+SQLSTATE: None
+
+Description: The user has no read permission on this file.
+
+Solution: Check whether the user is correct or whether the user is granted a matching read permission.
+
+GAUSS-50101: "The %s is not executable for %s."
+
+SQLSTATE: None
+
+Description: The user has no execution permission on this file.
+
+Solution: Check whether the user is correct or whether the user is granted a matching execution permission.
+
+GAUSS-50102: "The %s is not writable for %s."
+
+SQLSTATE: None
+
+Description: The user has no write permission on this file.
+
+Solution: Check whether the user is correct or whether the user is granted a matching write permission.
+
+GAUSS-50103: "The %s has unexpected rights."
+
+SQLSTATE: None
+
+Description: The permissions are unauthorized.
+
+Solution: Grant the user with matching permissions.
+
+GAUSS-50104: "Only a user with the root permission can run this script."
+
+SQLSTATE: None
+
+Description: Only the user **root** can execute this script.
+
+Solution: Execute this script as a user **root**.
+
+GAUSS-50105: "Cannot run this script as a user with the root permission."
+
+SQLSTATE: None
+
+Description: This script cannot be executed by the user **root**.
+
+Solution: Execute this script as a non-**root** user.
+
+GAUSS-50106: "Failed to change the owner of %s."
+
+SQLSTATE: None
+
+Description: Failed to change the owner of the file or directory.
+
+Solution: Check whether the permissions on the file or directory of the user or the group are correctly granted.
+
+GAUSS-50107: "Failed to change the permission of %s."
+
+SQLSTATE: None
+
+Description: Failed to change the permission of the file or directory.
+
+Solution: Check whether the user who modifies the directory or file is the user **root**, or check whether the permission granted to the directory or file is correct.
+
+GAUSS-50108: "Failed to change the owner and permission of %s."
+
+SQLSTATE: None
+
+Description: Failed to change the owner and permission of the file or directory.
+
+Solution: Check whether the owner of the file or directory exists, and whether the user or permission value of the file or directory is correct.
+
+GAUSS-50109: "Only a user with the root permission can check SSD information."
+
+SQLSTATE: None
+
+Description: Only the user **root** can check the SSD information.
+
+Solution: Check whether the current user has the **root** permission.
+
+GAUSS-50110: "Cannot execute this script on %s."
+
+SQLSTATE: None
+
+Description: The script cannot be executed on a node.
+
+Solution: Do not execute the **gs_replace** script on the node where the warm backup or node replacement is performed.
+
+<br/>
+
+## GAUSS-50200 - GAUSS-50299
+
+<br/>
+
+GAUSS-50200: "The %s already exists."
+
+SQLSTATE: None
+
+Description: The file or directory exists.
+
+Solution: Delete this file or directory.
+
+GAUSS-50201: "The %s does not exist."
+
+SQLSTATE: None
+
+Description: The file or directory does not exist.
+
+Solution: Check why the file or directory does not exist, create a file or directory, or execute the script that creates this file or directory.
+
+GAUSS-50202: "The %s must be empty."
+
+SQLSTATE: None
+
+Description: The directory is not empty.
+
+Solution: Check the directory and leave it empty after backing it up.
+
+GAUSS-50203: "The %s cannot be empty."
+
+SQLSTATE: None
+
+Description: The directory or file cannot be empty.
+
+Solution: Check why the directory or file is empty, create a directory or file, or execute the script that creates this directory.
+
+GAUSS-50204: "Failed to read %s."
+
+SQLSTATE: None
+
+Description: Failed to read the file.
+
+Solution: Check and modify the file and user permissions.
+
+GAUSS-50205: "Failed to write %s."
+
+SQLSTATE: None
+
+Description: Failed to write the file.
+
+Solution: Check and modify the file and user permissions.
+
+GAUSS-50206: "Failed to create %s."
+
+SQLSTATE: None
+
+Description: Failed to create a file.
+
+Solution: Check and modify the user permissions of this directory under this file path.
+
+GAUSS-50207: "Failed to delete %s."
+
+SQLSTATE: None
+
+Description: Failed to delete the file.
+
+Solution: Check and modify the user permissions of this directory under this file path.
+
+GAUSS-50208: "Failed to create the %s directory."
+
+SQLSTATE: None
+
+Description: Failed to create the folder.
+
+Solution: Check and modify the user permissions of this directory.
+
+GAUSS-50209: "Failed to delete the %s directory."
+
+SQLSTATE: None
+
+Description: Failed to delete the folder.
+
+Solution: Check and modify the user permissions of this directory.
+
+GAUSS-50210: "The %s must be a file."
+
+SQLSTATE: None
+
+Description: The type is not a file type.
+
+Solution: Ensure that the type is a file type.
+
+GAUSS-50211: "The %s must be a directory."
+
+SQLSTATE: None
+
+Description: The type is not a directory type.
+
+Solution: Ensure that the type is a directory type.
+
+GAUSS-50212: "The suffix of the file '%s' should be '%s'."
+
+SQLSTATE: None
+
+Description: The file name extension is not a specified type.
+
+Solution: Change the file name extension to a specified type.
+
+GAUSS-50213: "The %s path must be an absolute path."
+
+SQLSTATE: None
+
+Description: The path is not an absolute path.
+
+Solution: Change the path to an absolute path.
+
+GAUSS-50214: "Failed to copy %s."
+
+SQLSTATE: None
+
+Description: Failed to copy the file.
+
+Solution: Check whether the file to be copied exists, whether the target path exists, and whether the network is normal.
+
+GAUSS-50215: "Failed to back up %s."
+
+SQLSTATE: None
+
+Description: Failed to back up the file or directory.
+
+Solution: Check whether the file or directory to be backed up exists.
+
+GAUSS-50216: "Failed to remote copy %s."
+
+SQLSTATE: None
+
+Description: Failed to copy the file or directory remotely.
+
+Solution: Check whether the file or directory to be copied exists and whether the target path exists.
+
+GAUSS-50217: "Failed to decompress %s."
+
+SQLSTATE: None
+
+Description: Failed to decompress the package.
+
+Solution: Check whether the compressed package to be decompressed exists, whether the format is correct, and whether the package is broken.
+
+GAUSS-50218: "Failed to rename %s."
+
+SQLSTATE: None
+
+Description: Failed to rename the file.
+
+Solution: Check whether the file to be renamed exists and whether the name and extension of the renamed file are correct.
+
+GAUSS-50219: "Failed to obtain %s."
+
+SQLSTATE: None
+
+Description: Failed to obtain the directory, file, or path.
+
+Solution: Check whether the directory, file, or path exists.
+
+GAUSS-50220: "Failed to restore %s."
+
+SQLSTATE: None
+
+Description: Failed to restore the directory, file, or path.
+
+Solution: Check whether the directory, file, or path exists.
+
+GAUSS-50221: "Failed to obtain file type."
+
+SQLSTATE: None
+
+Description: Failed to obtain the file type.
+
+Solution: Check whether the command is correct. Check whether the specified file or path exists.
+
+GAUSS-50222: "The content of file %s is not correct."
+
+SQLSTATE: None
+
+Description: The file content is incorrect.
+
+Solution: Check whether the file content is correct.
+
+GAUSS-50223: "Failed to update %s files."
+
+SQLSTATE: None
+
+Description: Failed to update (write) the file.
+
+Solution: Check whether the file to be updated (written) exists and whether the content written into the file is correct.
+
+GAUSS-50224: "The file name is incorrect."
+
+SQLSTATE: None
+
+Description: The file name is incorrect.
+
+Solution: Check whether multiple extensions (".") exist in the file.
+
+GAUSS-50225: "Failed to back up remotely."
+
+SQLSTATE: None
+
+Description: Failed to back up remotely.
+
+Solution: Check whether the file or directory to be backed up exists and whether the remote target path exists.
+
+GAUSS-50226: "Failed to restore remotely."
+
+SQLSTATE: None
+
+Description: Failed to restore remotely.
+
+Solution: Check whether the running **restore** command is correct.
+
+GAUSS-50227: "Failed to compress %s."
+
+SQLSTATE: None
+
+Description: Failed to compress the file or directory.
+
+Solution: Check whether the file or directory to be compressed exists or whether the target path exists.
+
+GAUSS-50228: "The %s does not exist or is empty."
+
+SQLSTATE: None
+
+Description: The file or directory does not exist or is empty.
+
+Solution: Check whether the file or directory exists or is empty.
+
+GAUSS-50229: "Cannot specify the file [%s] to the cluster path %s."
+
+SQLSTATE: None
+
+Description: A file cannot be specified to a path in a cluster.
+
+Solution: Change the path for saving the file.
+
+GAUSS-50230: "Failed to read/write %s."
+
+SQLSTATE: None
+
+Description: Failed to read or write the file.
+
+Solution: Check whether the file exists and whether you have the read/write permission on the file.
+
+GAUSS-50231: "Failed to generate %s file."
+
+SQLSTATE: None
+
+Description: Failed to generate the file.
+
+Solution: Identify the cause of the file generation failure and try again.
+
+GAUSS-50232: "The instance directory [%s] cannot set in app directory [%s].Please check the xml."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-50233: "The directory name %s and %s cannot be same."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-50234: "Cannot execute the script in the relevant path of the database."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-50300 - GAUSS-50399
+
+<br/>
+
+GAUSS-50300: "User %s does not exist."
+
+SQLSTATE: None
+
+Description: The user does not exist.
+
+Solution: Check why the user does not exist, and then create a user.
+
+GAUSS-50301: "The cluster user/group cannot be a root user/group."
+
+SQLSTATE: None
+
+Description: The user or group of the cluster user cannot be the user or group **root**.
+
+Solution: Change the user or group of the cluster user.
+
+GAUSS-50302: "The cluster user cannot be a user with the root permission."
+
+SQLSTATE: None
+
+Description: Cluster users cannot have the **root** permission.
+
+Solution: Change the permission of a cluster user or switch to another cluster user who does not have the **root** permission.
+
+GAUSS-50303: "Cannot install the program as a user with the root permission."
+
+SQLSTATE: None
+
+Description: This program cannot be installed by the user **root**.
+
+Solution: Change the permission of the user or install the program as a non-**root** user.
+
+GAUSS-50304: "The new user [%s] is not the same as the old user [%s]."
+
+SQLSTATE: None
+
+Description: The old and new users do not match.
+
+Solution: Change the user to match the old user.
+
+GAUSS-50305: "The user is not matched with the user group."
+
+SQLSTATE: None
+
+Description: The user and user group do not match.
+
+Solution: Check and modify the user and user group to make them match.
+
+GAUSS-50306: "The password of %s is incorrect."
+
+SQLSTATE: None
+
+Description: The password is incorrect.
+
+Solution: Correct the password.
+
+GAUSS-50307: "User password has expired."
+
+SQLSTATE: None
+
+Description: The user password has expired.
+
+Solution: Check and modify the password.
+
+GAUSS-50308: "Failed to obtain user information."
+
+SQLSTATE: None
+
+Description: Failed to obtain the user information.
+
+Solution: Check whether the user information is correct.
+
+GAUSS-50309: "Failed to obtain password change times of data base super user"
+
+SQLSTATE: None
+
+Description: Failed to obtain the number of password changes of the initial database user.
+
+Solution: Check whether the password of the initial user has been changed. If not, change the password.
+
+GAUSS-50310: "Failed to obtain password expiring days."
+
+SQLSTATE: None
+
+Description: Failed to obtain the password expiring date.
+
+Solution:Contact technical support.
+
+GAUSS-50311: "Failed to change password for %s."
+
+SQLSTATE: None
+
+Description: Failed to change the password for the user.
+
+Solution: Check whether you have the read permission on the **/temp/temp.***[user]* file and whether the file content is correct.
+
+GAUSS-50312: "There are other users in the group %s on %s, skip to delete group."
+
+SQLSTATE: None
+
+Description: Failed to delete the group because there are other users in the group.
+
+Solution: Delete other users from the group and then delete the group.
+
+GAUSS-50313: "Failed to delete %s group."
+
+SQLSTATE: None
+
+Description: Failed to delete the group.
+
+Solution: Check whether the group to be deleted exists. Check whether the cluster status is normal.
+
+GAUSS-50314: "Failed to delete %s user."
+
+SQLSTATE: None
+
+Description: Failed to delete the user.
+
+Solution: Check whether the user to be deleted exists.
+
+GAUSS-50315: "The user %s is not matched with the owner of %s."
+
+SQLSTATE: None
+
+Description: The user does not match the owner of the path.
+
+Solution: Modify the owner of the path.
+
+GAUSS-50316: "Group [%s] does not exist."
+
+SQLSTATE: None
+
+Description: The group does not exist.
+
+Solution: Execute the pre-processing script again and modify the **-G** parameter.
+
+GAUSS-50317: "Failed to check user and password."
+
+SQLSTATE: None
+
+Description: Failed to check the user and password.
+
+Solution: Check whether the user and password on each node in the cluster are correct.
+
+GAUSS-50318: "Failed to add %s user."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-50319: "Failed to add %s group."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-50320: "Failed to set '%s' to '%s' in /etc/ssh/sshd_config."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-50321: "Failed to get configuration of '%s' from /etc/ssh/sshd_config."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-50400 - GAUSS-50499
+
+<br/>
+
+GAUSS-50400: "The remaining space of device [%s] cannot be less than %s."
+
+SQLSTATE: None
+
+Description: The disk space cannot be less than the specified value.
+
+Solution: Clear the disk space, expand the disk capacity, or replace the disk.
+
+GAUSS-50401: "The usage of the device [%s] space cannot be greater than %s."
+
+SQLSTATE: None
+
+Description: The disk usage cannot be greater than the specified value.
+
+Solution: Clear the disk space, expand the disk capacity, or replace the disk.
+
+GAUSS-50402: "The usage of INODE cannot be greater than %s."
+
+SQLSTATE: None
+
+Description: The INODE usage cannot exceed the specified value.
+
+Solution: Ensure that the INODE usage does not exceed the specified value.
+
+GAUSS-50403: "The IO scheduling policy is incorrect."
+
+SQLSTATE: None
+
+Description: The I/O scheduling policy is abnormal.
+
+Solution: Use **gs_checkos** to set this parameter. For detailed operations, see instructions provided for **gs_checkos**.
+
+GAUSS-50404: "The XFS mount type must be %s."
+
+SQLSTATE: None
+
+Description: The XFS mount type must be the specified type.
+
+Solution: Change the mount type of XFS to the specified type.
+
+GAUSS-50405: "The pre-read block size must be 16384."
+
+SQLSTATE: None
+
+Description: The size of the pre-read block must be 16384.
+
+Solution: Use **gs_checkos** to set this parameter. For detailed operations, see instructions provided for **gs_checkos**.
+
+GAUSS-50406: "Failed to obtain disk read and write rates."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-50407: "Failed to clean shared semaphore."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-50408: "Failed to obtain disk read-ahead memory block."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-50409: "The remaining space of dns cannot support shrink."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-50410: "Failed to check if remaining space of dns support shrink."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+GAUSS-50411: "The remaining space cannot be less than %s."
+
+SQLSTATE: None
+
+Description: Internal system error.
+
+Solution: Contact technical support.
+
+<br/>
+
+## GAUSS-50500 - GAUSS-50599
+
+<br/>
+
+GAUSS-50500: "The SWAP partition is smaller than the actual memory."
+
+SQLSTATE: None
+
+Description: The swap partition size is smaller than the actual memory size.
+
+Solution: Adjust the size of the swap partition to a value greater than the actual memory size.
+
+GAUSS-50501: "Shared_buffers must be less than shmmax. Please check it."
+
+SQLSTATE: None
+
+Description: The value of **Shared_buffers** must be smaller than that of **shmmax**.
+
+Solution: Set the value of **shmmax** on all the hosts in the **/etc/sysctl.conf** file of the cluster to be greater than that of **shmall**. Run the **/sbin/sysctl -p** command to make the parameter effective, and run the command again.
+
+GAUSS-50502: "Failed to obtain %s information."
+
+SQLSTATE: None
+
+Description: Failed to obtain the swap partition or memory information.
+
+Solution: Check whether the system is normal.
+
+<br/>
+
+## GAUSS-50600 - GAUSS-50699
+
+<br/>
+
+GAUSS-50600: "The IP address cannot be pinged, which is caused by network faults."
+
+SQLSTATE: None
+
+Description: Failed to ping the IP address.
+
+Solution: Change the network settings so that the IP address can be pinged.
+
+GAUSS-50601: "The port [%s] is occupied."
+
+SQLSTATE: None
+
+Description: The port is occupied.
+
+Solution: Check whether the resources that occupy the port number are available. If the resources are idle, release the port number. Specify other port numbers.
+
+GAUSS-50602: "Failed to bind network adapters."
+
+SQLSTATE: None
+
+Description: Failed to bind the NIC.
+
+Solution:Contact technical support.
+
+GAUSS-50603: "The IP address is invalid."
+
+SQLSTATE: None
+
+Description: The IP address is invalid.
+
+Solution: Correct the IP address.
+
+GAUSS-50604: "Failed to obtain network interface card of backIp(%s)."
+
+SQLSTATE: None
+
+Description: Failed to obtain the NIC.
+
+Solution: Check whether the network is normal. Check whether the NIC is normal.
+
+GAUSS-50605: "Failed to obtain back IP subnet mask."
+
+SQLSTATE: None
+
+Description: Failed to obtain the subnet mask.
+
+Solution: Check whether the network is normal.
+
+GAUSS-50606: "Back IP(s) do not have the same subnet mask."
+
+SQLSTATE: None
+
+Description: The alternate IP address cannot have the same subnet mask.
+
+Solution: Set a subnet mask to the alternate IP address.
+
+GAUSS-50607:"Failed to obtain configuring virtual IP line number position of network startup file."
+
+SQLSTATE: None
+
+Description: Failed to obtain the virtual IP address in the NIC startup file.
+
+Solution: Manually check the NIC configuration file to see whether the file is damaged.
+
+GAUSS-50608:"Failed to writing virtual IP setting cmds into init file."
+
+SQLSTATE: None
+
+Description: Failed to write the virtual IP configuration command in the initialization file.
+
+Solution: Manually check the NIC configuration file to see whether the file is damaged.
+
+GAUSS-50609:"Failed to check port: %s."
+
+SQLSTATE: None
+
+Description: Failed to check the port.
+
+Solution: Ensure that the port is enabled and not occupied.
+
+GAUSS-50610:"Failed to get the range of random port."
+
+SQLSTATE: None
+
+Description: Failed to obtain the port range.
+
+Solution: Check the cause of the failure and obtain the range again.
+
+GAUSS-50611: "Failed to obtain network card bonding information."
+
+SQLSTATE: None
+
+Description: Failed to obtain the NIC binding information.
+
+Solution: Check whether the **/proc/net/bonding/**_NIC__ _*ID* file exists, whether the **BONDING_OPTS** (the Red Hat environment) or **BONDING_MODULE_OPTS** (the CentOS environment) strings exist.
+
+GAUSS-50612: "Failed to obtain network card %s value."
+
+SQLSTATE: None
+
+Description: Failed to obtain the value of the NIC RTU/RX.
+
+Solution: Check whether the network is normal and whether the NIC is normal.
+
+GAUSS-50613: "Failed to set network card %s value."
+
+SQLSTATE: None
+
+Description: Failed to set the NIC information.
+
+Solution: Check whether the network is normal and whether the NIC is normal.
+
+GAUSS-50614: "Failed to check network information."
+
+SQLSTATE: None
+
+Description: Failed to check the NIC information.
+
+Solution: Check whether **ifconfig** is available. If it is, query it again.
+
+GAUSS-50615:"IP %s and IP %s are not in the same network segment."
+
+SQLSTATE: None
+
+Description: The network segments of the two IP addresses are different.
+
+Solution: Set the network segments of the two IP addresses to the same network segment. Then, perform the operation again.
+
+GAUSS-50616:"Failed to get network interface."
+
+SQLSTATE: None
+
+Description: Failed to obtain the network interface.
+
+Solution: Ensure that the IP address exists, **ifconfig** is available, and IP information exists in the NIC configuration file. Then, perform the operation again.
+
+GAUSS-50617: "The node of XML configure file has the same virtual IP."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-50700 - GAUSS-50799
+
+<br/>
+
+GAUSS-50700: "The firewall should be disabled."
+
+SQLSTATE: None
+
+Description: The firewall is not disabled.
+
+Solution: Disable the firewall.
+
+GAUSS-50701: "The firewall should be opened."
+
+SQLSTATE: None
+
+Description: The firewall is not enabled.
+
+Solution: Enable the firewall.
+
+<br/>
+
+## GAUSS-50800 - GAUSS-50899
+
+<br/>
+
+GAUSS-50800: "Regular tasks are not started."
+
+SQLSTATE: None
+
+Description: The scheduled task is not started.
+
+Solution: Start the scheduled task.
+
+GAUSS-50801: "Failed to set up tasks."
+
+SQLSTATE: None
+
+Description: Failed to set the task.
+
+Solution: Perform the operation again.
+
+GAUSS-50802: "Failed to %s·service."
+
+SQLSTATE: None
+
+Description: Failed to restart the scheduled task service.
+
+Solution: View the logs to identify the detailed error information.
+
+GAUSS-50803: "Failed to check user cron."
+
+SQLSTATE: None
+
+Description: Failed to check the scheduled task.
+
+Solution: Verify whether the cluster status is normal and whether the **/bin/om_monitor/[cron]** file exists.
+
+<br/>
+
+## GAUSS-50900 - GAUSS-50999
+
+<br/>
+
+GAUSS-50900: "The NTPD service is not installed."
+
+SQLSTATE: None
+
+Description: The clock services are not installed.
+
+Solution: Install the clock services.
+
+GAUSS-50901: "The NTPD service is not started."
+
+SQLSTATE: None
+
+Description: The clock services are not enabled.
+
+Solution: Enable the clock services.
+
+GAUSS-50902: "The system time is different."
+
+SQLSTATE: None
+
+Description: The system time is different from the actual time.
+
+Solution: Correct the system time.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/77-GAUSS-51000-GAUSS-51999.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/77-GAUSS-51000-GAUSS-51999.md
new file mode 100644
index 0000000000000000000000000000000000000000..0556ab7116a2a3982d55ba89a6a935fc8ee45753
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/77-GAUSS-51000-GAUSS-51999.md
@@ -0,0 +1,1252 @@
+---
+title: GAUSS-51000 - GAUSS-51999
+summary: GAUSS-51000 - GAUSS-51999
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-51000 - GAUSS-51999
+
+<br/>
+
+## GAUSS-51000 - GAUSS-51099
+
+<br/>
+
+GAUSS-51000: "THP services must be shut down."
+
+SQLSTATE: None
+
+Description: The THP service is not disabled.
+
+Solution: Disable the THP service.
+
+GAUSS-51001: "Failed to obtain THP service."
+
+SQLSTATE: None
+
+Description: Failed to obtain THP service information.
+
+Solution: Check whether the THP file exists.
+
+GAUSS-51002: "Failed to close THP service."
+
+SQLSTATE: None
+
+Description: Failed to disable the THP service.
+
+Solution: Check whether the THP file exists.
+
+<br/>
+
+## GAUSS-51100 - GAUSS-51199
+
+<br/>
+
+GAUSS-51100: "Failed to verify SSH trust on these nodes: %s."
+
+SQLSTATE: None
+
+Description: Failed to verify the SSH mutual trust on each node.
+
+Solution: Verify that the mutual trust between nodes is built.
+
+GAUSS-51101: "SSH exception: \n%s"
+
+SQLSTATE: None
+
+Description: The remote connection is abnormal.
+
+Solution: Ensure that the network connection is normal and that the remote server IP address, login username, and password are correct.
+
+GAUSS-51102:"Failed to exchange SSH keys for user [%s] performing the %s operation."
+
+SQLSTATE: None
+
+Description: Failed to exchange the trust key.
+
+Solution: Verify that the network connection is normal and the server IP address configuration is correct.
+
+GAUSS-51103: "Failed to execute the PSSH command [%s]."
+
+SQLSTATE: None
+
+Description: Failed to run the PSSH command.
+
+Solution: Verify that the PSSH tool is complete and the executed command is correct.
+
+GAUSS-51104: "Failed to obtain SSH status."
+
+SQLSTATE: None
+
+Description: Failed to obtain the SSH status and result.
+
+Solution: Verify that the network connection is normal and the connected server exists.
+
+GAUSS-51105: "Failed to parse SSH output: %s."
+
+SQLSTATE: None
+
+Description: Failed to analyze the SSH result.
+
+Solution: Verify that the SSH tool is complete and the parsed command is correct.
+
+GAUSS-51106: "The SSH tool does not exist."
+
+SQLSTATE: None
+
+Description: The SSH tool does not exist.
+
+Solution: Verify that the SSH tool exists.
+
+GAUSS-51107: "Ssh Paramiko failed."
+
+SQLSTATE: None
+
+Description: The Paramiko mutual trust failed.
+
+Solution:
+
+1. Check whether the network connection is normal.
+2. Check whether the Paramiko package exists.
+3. Check the following options in the **/etc/ssh/sshd_config** file:
+   - PasswordAuthentication=yes;
+   - MaxStartups=1000;
+   - UseDNS=no;
+   - **ClientAliveInterval** is greater than 10800 or equal to 0.
+   - Check whether the value of **MaxSessions** is too small when there are a large number of hosts in the cluster.
+4. After the modification is complete, restart the sshd service.
+
+GAUSS-51108: "Ssh-keygen failed."
+
+SQLSTATE: None
+
+Description: Failed to run the **Ssh-keygen** command.
+
+Solution: Verify that the ssh-keygen tool exists and that the network is normal.
+
+GAUSS-51109: "Failed to check authentication."
+
+SQLSTATE: None
+
+Description: Identity authentication failed.
+
+Solution: View the logs and check the cause of the identity authentication failure. Then, try the authentication again.
+
+GAUSS-51110: "Failed to obtain RSA host key for local host."
+
+SQLSTATE: None
+
+Description: Failed to obtain the RSA host key of the local host.
+
+Solution: Check the cause of the failure and try again.
+
+GAUSS-51111: "Failed to append local ID to authorized_keys on remote node."
+
+SQLSTATE: None
+
+Description: Failed to add the local ID to the **authorized_keys** of the remote node.
+
+Solution: Check the cause of the failure and try again.
+
+GAUSS-51112: "Failed to exchange SSH keys for user[%s] using hostname."
+
+SQLSTATE: None
+
+Description: Failed to exchange the user name using the SSH private key.
+
+Solution: Check whether the network is normal.
+
+<br/>
+
+## GAUSS-51200 - GAUSS-51299
+
+<br/>
+
+GAUSS-51200: "The parameter [%s] in the XML file does not exist."
+
+SQLSTATE: None
+
+Description: Failed to find the *%s* parameter in the XML.
+
+Solution: Check the configuration parameters in the XML.
+
+GAUSS-51201: "Node names must be configured."
+
+SQLSTATE: None
+
+Description: The node name needs to be configured.
+
+Solution: Configure the node name for the node.
+
+GAUSS-51202: "Failed to add the %s instance."
+
+SQLSTATE: None
+
+Description: Failed to add the instance.
+
+Solution: Ensure that the instance exists and the configuration is correct.
+
+GAUSS-51203: "Failed to obtain the %s information from static configuration files."
+
+SQLSTATE: None
+
+Description: Failed to obtain the cluster information from the static configuration file.
+
+Solution: Ensure that the static configuration file exists, that you have the access permission, and that the system is normal.
+
+GAUSS-51204: " Invalid %s instance type: %d."
+
+SQLSTATE: None
+
+Description: The instance type is invalid.
+
+Solution: Check and modify the instance type to be a valid one.
+
+GAUSS-51205: "Failed to refresh the %s instance ID."
+
+SQLSTATE: None
+
+Description: Failed to update the instance ID.
+
+Solution: Check whether the static configuration file of the current cluster exists or whether it has been broken, and check whether the user has the access permission. Update the CN ID of the new cluster based on this file.
+
+GAUSS-51206: "The MPPRC file path must be an absolute path: %s."
+
+SQLSTATE: None
+
+Description: The MPPRC path must be an absolute path.
+
+Solution: Change the MPPRC path to an absolute path.
+
+GAUSS-51207: "Failed to obtain backIp from node [%s]."
+
+SQLSTATE: None
+
+Description: Failed to obtain the alternate IP address on the node.
+
+Solution: Check and correctly configure the alternate IP address on the node.
+
+GAUSS-51208: "Invalid %s number [%d]."
+
+SQLSTATE: None
+
+Description: The quantity is invalid.
+
+Solution: Ensure that the quantity is valid.
+
+GAUSS-51209: "Failed to obtain %s configuration on the host [%s]."
+
+SQLSTATE: None
+
+Description: Failed to obtain the configuration on this node.
+
+Solution: Ensure that the configuration is correct on the node.
+
+GAUSS-51210: "The obtained number does not match the instance number."
+
+SQLSTATE: None
+
+Description: The number of instances obtained does not match the actual instance number.
+
+Solution: Check and modify the obtained number to match the actual instance number.
+
+GAUSS-51211: "Failed to save a static configuration file."
+
+SQLSTATE: None
+
+Description: Failed to save the static configuration file.
+
+Solution: Ensure that the static configuration file exists, that you have the access permission, and that the system is normal.
+
+GAUSS-51212: "There is no information about %s."
+
+SQLSTATE: None
+
+Description: There is no information about *%s*.
+
+Solution: Configure corresponding information for *%s*.
+
+GAUSS-51213: "The port number of XML [%s] conflicted."
+
+SQLSTATE: None
+
+Description: The port number is occupied.
+
+Solution: Check whether the occupied port process is available. If the process is unavailable, kill it, or change a new port number.
+
+GAUSS-51214: "The number of capacity expansion DN nodes cannot be less than three or CN nodes cannot be less than one."
+
+SQLSTATE: None
+
+Description: The number of nodes before scale-out cannot be less than three.
+
+Solution: Ensure that the number of nodes before scale-out is greater than or equal to three.
+
+GAUSS-51215 : "The capacity expansion node [%s] cannot contain GTM/CM/ETCD."
+
+SQLSTATE: None
+
+Description: The GTM, CM, and ETCD cannot be contained on the scale-out node.
+
+Solution: Delete the GTM, CM, and ETCD on the scale-out node.
+
+GAUSS-51216: "The capacity expansion node [%s] must contain CN or DN."
+
+SQLSTATE: None
+
+Description: The node to be added to the cluster for scale-out does not have any CN or DN.
+
+Solution: Add CN or DN on the scale-out node.
+
+GAUSS-51217: "The cluster's static configuration does not match the new configuration file."
+
+SQLSTATE: None
+
+Description: The cluster's static configuration is inconsistent with the new configuration.
+
+Solution: Modify the new XML configuration file, leaving it consistent with the cluster static configuration.
+
+GAUSS-51218: "Failed to obtain initialized configuration parameter: %s."
+
+SQLSTATE: None
+
+Description: Failed to obtain the initialization configuration parameters.
+
+Solution: Try to obtain the parameters again.
+
+GAUSS-51219: "There is no CN in cluster."
+
+SQLSTATE: None
+
+Description: The CN is not installed in the cluster.
+
+Solution: Reconfigure the XML file and execute the preparation and installation operations.
+
+GAUSS-51220: "The IP address %s is incorrect."
+
+SQLSTATE: None
+
+Description: The IP address is incorrect.
+
+Solution: Check whether the IP address configured in the XML file is correct.
+
+GAUSS-51221: "Failed to configure hosts mapping information."
+
+SQLSTATE: None
+
+Description: Failed to configure the host mapping.
+
+Solution: Check whether the **/etc/hosts** file exists and whether the host name and IP address configured in the file are consistent.
+
+GAUSS-51222: "Failed to check hostname mapping."
+
+SQLSTATE: None
+
+Description: Failed to check the host mapping.
+
+Solution: Check whether the mutual trust between nodes is normal.
+
+GAUSS-51223: "Failed to obtain network inet addr on the node(%s)."
+
+SQLSTATE: None
+
+Description: Failed to obtain the inet address from the node.
+
+Solution: Run the **ifconfig** command in the **root** directory to manually check whether the inet address exists. If it does, try to obtain the address again.
+
+GAUSS-51224: "The ip(%s) has been used on other nodes."
+
+SQLSTATE: None
+
+Description: The IP address has been used on another node.
+
+Solution: Check whether the IP address on each node in the XML file conflicts with each other.
+
+GAUSS-51225: "Failed to set virtual IP."
+
+SQLSTATE: None
+
+Description: Failed to configure the virtual IP address.
+
+Solution: Check whether the virtual IP address is used.
+
+GAUSS-51226: "Virtual IP(s) and Back IP(s) do not have the same network segment."
+
+SQLSTATE: None
+
+Description: The virtual IP address and alternate IP address are not in the same network segment.
+
+Solution: Set the virtual IP address and alternate IP address in the XML file to be in the same network segment.
+
+GAUSS-51227: "The number of %s on all nodes are different."
+
+SQLSTATE: None
+
+Description: The number of alternate IP addresses on all nodes is different from that of the SSH IP addresses.
+
+Solution: Set the number of alternate IP addresses in the XML file to be the same as that of the SSH IP address.
+
+GAUSS-51228: "The number %s does not match %s number."
+
+SQLSTATE: None
+
+Description: The two numbers are different.
+
+Solution: Set the two numbers to be the same.
+
+GAUSS-51229: "The DN listenIp(%s) is not in the virtualIp or backIp on the node(%s)."
+
+SQLSTATE: None
+
+Description: The listen IP address on the DN is not the virtual IP address or alternate IP address.
+
+Solution: Change the listen IP address to the virtual IP address or alternate IP address in the XML file.
+
+GAUSS-51230: "The number of %s must %s."
+
+SQLSTATE: None
+
+Description: The number of CM servers, GTMs, or ETCDs is incorrect.
+
+Solution: Configure correct numbers for CM servers, GTMs, and ETCDs in the XML file.
+
+GAUSS-51231: "Old nodes is less than 2."
+
+SQLSTATE: None
+
+Description: The number of old nodes is less than two.
+
+Solution: Set the number of the configured nodes in the XML file to be greater than or equal to 3.
+
+GAUSS-51232: "XML configuration and static configuration are the same."
+
+SQLSTATE: None
+
+Description: The XML configuration and static configuration files are the same.
+
+Solution: Before the scale-out, scale-in, and CN management operations, ensure that the XML is different from that of the installed clusters.
+
+GAUSS-51233: "The Port(%s) is invalid on the node(%s)."
+
+SQLSTATE: None
+
+Description: The port is invalid.
+
+Solution: Check whether the port number configured in the XML file is correct.
+
+GAUSS-51234 : "The configuration file [%s] contains parsing errors."
+
+SQLSTATE: None
+
+Description: The XML file is analyzed incorrectly.
+
+Solution: Check whether the configuration file is broken. If the file has been broken, copy a file from another node. If the file has not been broken, reinstall the cluster.
+
+GAUSS-51235: "Invalid directory [%s]."
+
+SQLSTATE: None
+
+Description: The directory is invalid.
+
+Solution: Check whether the directory is correct.
+
+GAUSS-51236: "Failed to parsing xml."
+
+SQLSTATE: None
+
+Description: Failed to parse the XML file.
+
+Solution: Check whether the XML file is opened successfully.
+
+GAUSS-51239: "Failed to parse json. gs_collect configuration file (%s) is invalid , check key in json file"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-51240: "gs_collect configuration file is invalid, TypeName or content must in config file."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-51241: "The parameter %s(%s) formate is wrong, or value is less than 0."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-51242: "gs_collect configuration file is invalid: %s, the key: (%s) is invalid."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-51243: "content(%s) does not match the typename(%s) in gs_collect configuration file(%s)."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-51244: "(%s) doesn't yet support."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-51245: "There are duplicate key(%s)."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-51246: "%s info only support one time collect."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-51247: "These virtual IP(%s) are not accessible after configuring."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-51248: "gs_collector does not support '%s' view collection. please check key in json file."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-51300 - GAUSS-51399
+
+<br/>
+
+GAUSS-51300: "Failed to execute SQL: %s."
+
+SQLSTATE: None
+
+Description: Failed to execute the SQL statement.
+
+Solution: Ensure that the SQL statement is correct. Check whether the database status is normal. Check whether the user has the execution permission. Check whether the database object exists.
+
+GAUSS-51301 : "Execute SQL time out. \nSql: %s."
+
+SQLSTATE: None
+
+Description: The execution of the SQL statement times out.
+
+Solution: Ensure that the SQL statement is correct. Check whether the database status is normal. Check whether the user has the execution permission. Check whether the network is normal.
+
+GAUSS-51302: "The table '%s.%s' does not exist or is private table!"
+
+SQLSTATE: None
+
+Description: The table does not exist or is a private table.
+
+Solution: 1. Ensure that the table exists in the database. 2. If the table is a private table, use **gs_dump** to back up the table.
+
+GAUSS-51303: "Query·'%s'·has·no·record!."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-51304: "Query '%s' result '%s' is incorrect!."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-51305: "The table '%s.%s' exists!"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-51400 - GAUSS-51499
+
+<br/>
+
+GAUSS-51400: "Failed to execute the command: %s."
+
+SQLSTATE: None
+
+Description: Failed to run the command.
+
+Solution: Check whether the command is correct and whether you have the permission to run the command.
+
+GAUSS-51401: "Failed to do %s.sh."
+
+SQLSTATE: None
+
+Description: Failed to execute the shell script.
+
+Solution: Check whether the command is correct and whether you have the permission to run the command. Ensure that the shell script exists.
+
+GAUSS_50402: "The usage of INODE cannot be greater than %s."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-51500 - GAUSS-51599
+
+<br/>
+
+GAUSS-51500: "Failed to call the interface %s. Exception: %s."
+
+SQLSTATE: None
+
+Description: Failed to invoke the interface.
+
+Solution: Check whether the network connection is normal, whether the path is correct, and whether the invoked interface is open.
+
+<br/>
+
+## GAUSS-51600 - GAUSS-51699
+
+<br/>
+
+GAUSS-51600: "Failed to obtain the cluster status."
+
+SQLSTATE: None
+
+Description: Failed to obtain the cluster status.
+
+Solution: Check whether the cluster has been set up. Check whether the created cluster is started as expected.
+
+GAUSS-51601: "Failed to check %s status."
+
+SQLSTATE: None
+
+Description: Failed to check the cluster or local node status.
+
+Solution: Check whether the cluster or local node status is normal.
+
+GAUSS-51602: "The cluster status is Abnormal."
+
+SQLSTATE: None
+
+Description: The cluster status is abnormal.
+
+Solution: Check whether the cluster status is not restored because the tool script command is not executed.
+
+GAUSS-51603: "Failed to obtain peer %s instance."
+
+SQLSTATE: None
+
+Description: Failed to obtain the peer instance.
+
+Solution: Ensure that the **gtm.conf** path exists if you want to obtain GTM. Check whether the configuration is correct.
+
+GAUSS-51604: "There is no HA status for %s."
+
+SQLSTATE: None
+
+Description: No HA status is available in the instance.
+
+Solution: Ensure that the cluster status and network connection are normal.
+
+GAUSS-51605: "Failed to check whether the %s process exists."
+
+SQLSTATE: None
+
+Description: Failed to check whether the process exists.
+
+Solution: Ensure that the user has the permission to check the process and that the process is correctly checked.
+
+GAUSS-51606: "Failed to kill the %s process.
+
+SQLSTATE: None
+
+Description: Failed to kill the process.
+
+Solution: Ensure that the user has the permission to kill the process and that the execution command is correct.
+
+GAUSS-51607: "Failed to start %s."
+
+Description: Failed to start the cluster, node, or instance.
+
+Solution: Ensure that the network connection is normal and that the configuration file is correct.
+
+GAUSS-51608: "Failed to lock cluster"
+
+SQLSTATE: None
+
+Description: Failed to lock the cluster.
+
+Solution: Do not perform the closure or stop operations before the session is complete.
+
+GAUSS-51609: "Failed to unlock cluster"
+
+SQLSTATE: None
+
+Description: Failed to unlock the cluster.
+
+Solution: Do not perform the closure or stop operations before the session is complete.
+
+GAUSS-51610: "Failed to stop %s."
+
+SQLSTATE: None
+
+Description: Failed to stop the cluster, node, or instance.
+
+Solution: Ensure that the command is correctly executed and that the cluster, node, or instance is normal.
+
+GAUSS-51611: "Failed to create %s instance."
+
+SQLSTATE: None
+
+Description: Failed to create the instance.
+
+Solution: Check whether the CN in the XML file is correctly configured.
+
+GAUSS-51612: "The instance IDs [%s] are not found in %s."
+
+SQLSTATE: None
+
+Description: The ID of an instance is not found in the node information.
+
+Solution: Check whether the CN in the XML file is correctly configured when you add or delete the CN.
+
+GAUSS-51613: "There is no instance in %s to be built."
+
+SQLSTATE: None
+
+Description: No instance needs to be created.
+
+Solution: The XML file is incorrectly configured when the user manages the CN. No instance is configured on the new node in the XML file.
+
+GAUSS-51614: "Received signal[%d]."
+
+SQLSTATE: None
+
+Description: Received the signal *%d*.
+
+Solution: Try to receive the signal again.
+
+GAUSS-51615: "Failed to initialize instance."
+
+SQLSTATE: None
+
+Description: Failed to initialize the instance.
+
+Solution: Ensure that the **gs_initdb** or **gs_initcm** utility exists. Ensure that the **gs_initdb** or **gs_initcm** command is correct. Ensure that the cluster, node, or instance is normal.
+
+GAUSS-51616: "Failed to dump %s schema."
+
+SQLSTATE: None
+
+Description: Failed to dump the CN or DN schema.
+
+Solution: Ensure that the **dumpall** or **dump** tool exists. Ensure that the **dumpall** or **dump** command is correctly executed. Ensure that the cluster, node, or instance is normal.
+
+GAUSS-51617: "Failed to rebuild %s."
+
+SQLSTATE: None
+
+Description: Failed to rebuild.
+
+Solution: Run the command again.
+
+GAUSS-51618: "Failed to get all hostname."
+
+SQLSTATE: None
+
+Description: Failed to obtain all the host names.
+
+Solution: Ensure that the SSH mutual trust is normal.
+
+GAUSS-51619: "The host·name [%s] is not in the cluster."
+
+SQLSTATE: None
+
+Description: The current node is not in the cluster.
+
+Solution: Check whether the node is configured in the XML file.
+
+GAUSS-51620: "Failed to obtain %s instance information."
+
+SQLSTATE: None
+
+Description: Failed to obtain the instance information.
+
+Solution: Ensure that the XML file is correctly configured and that the cluster, host, or instance is normal.
+
+GAUSS-51621: "HA IP is empty."
+
+SQLSTATE: None
+
+Description: The HA IP address is empty.
+
+Solution: Check the configuration information in the XML file. If the HA IP address is configured in the XML file, you need to ensure that the value is correctly configured. If the HA IP address is not configured in the XML file, the alternate IP address will be used by default, and you need to ensure that the alternate IP address is correctly configured in the XML file.
+
+GAUSS-51622: "There is no %s on %s node."
+
+SQLSTATE: None
+
+Description: No CN/DN instance exists on the node.
+
+Solution: Check whether the CN or DN instance is configured on the node in the XML file. Ensure that the current cluster, host, or instance is normal.
+
+GAUSS-51623: "Failed to obtain version."
+
+SQLSTATE: None
+
+Description: Failed to obtain the cluster version.
+
+Solution: Ensure that the *version.cfg* file exists. Check whether the data format of the *version.cfg* file is correct. Check whether the current cluster, host, or instance is normal.
+
+GAUSS-51624: "Failed to get CN connections."
+
+SQLSTATE: None
+
+Description: Failed to obtain the number of CN connections.
+
+Solution: Ensure that the cluster, node, and instance are running properly.
+
+GAUSS-51625: "Cluster is running."
+
+SQLSTATE: None
+
+Description: The cluster is running.
+
+Solution: Stop this cluster.
+
+GAUSS-51626: "Failed to rollback."
+
+SQLSTATE: None
+
+Description: Failed to roll back.
+
+Solution: Ensure that the command is correctly executed. Ensure that the current cluster, host, or instance is normal. View the corresponding log information.
+
+GAUSS-51627: "Configuration failed."
+
+SQLSTATE: None
+
+Description: Configuration failed.
+
+Solution: Perform the configuration again.
+
+GAUSS-51628: "The version number of new cluster is [%s]. It should be float."
+
+SQLSTATE: None
+
+Description: The version number format of the new cluster is incorrect.
+
+Solution: Ensure that the *version.cfg* file exists. Check whether the data format of the *version.cfg* file is correct. Check whether the current cluster, host, or instance is normal.
+
+GAUSS-51629: "The version number of new cluster is [%s]. It should be greater than or equal to the old version."
+
+SQLSTATE: None
+
+Description: The version number of the new cluster is incorrect. It should be later than or equal to the old version number.
+
+Solution: Ensure that the *version.cfg* file exists. Check whether the version number in the *version.cfg* file is earlier than that of the existing cluster. Ensure that the cluster, node, or instance is normal.
+
+GAUSS-51630: "No node named %s."
+
+SQLSTATE: None
+
+Description: The node name does not exist.
+
+Solution: Check whether the node is configured in the XML file. Ensure that the cluster, node, or instance is normal.
+
+GAUSS-51631: "Failed to delete the %s instance."
+
+SQLSTATE: None
+
+Description: Failed to delete the CN.
+
+Solution: Ensure that SSH mutual trust is normal, that the command is correctly executed, and that the cluster, node, or instance is normal.
+
+GAUSS-51632: "Failed to do %s."
+
+SQLSTATE: None
+
+Description: Failed to execute the Python script.
+
+Solution: Ensure that the Python script exists, that the command is correctly executed, and that the cluster, node, or instance is normal.
+
+GAUSS-51633: "The·step·of·upgrade·number·%s·is·incorrect."
+
+SQLSTATE: None
+
+Description: The ID must be composed of digits.
+
+Solution: Ensure that the specified instance exists, that the command is correctly executed, and that the cluster, node, or instance is normal.
+
+GAUSS-51634: "Waiting node synchronizing timeout lead to failure."
+
+SQLSTATE: None
+
+Description: Waiting for the node synchronization results times out.
+
+Solution: Ensure that the command is correctly executed and that the cluster, node, or instance is normal.
+
+GAUSS-51635: "Failed to check SHA256."
+
+SQLSTATE: None
+
+Description: Failed to check SHA-256.
+
+Solution: Ensure that the SHA-256 file exists. Ensure that the command is correctly executed. Ensure that the cluster, node, or instance is normal.
+
+GAUSS-51636: "Failed to obtain %s node information."
+
+SQLSTATE: None
+
+Description: Failed to obtain the node information.
+
+Solution: Ensure that the node is configured in the XML file, that the command is correctly executed, and that the cluster, node, or instance is normal.
+
+GAUSS-51637: "The %s does not match with %s."
+
+SQLSTATE: None
+
+Description: The cluster information does not match.
+
+Solution: Ensure that the two parties to be matched are updated simultaneously. Ensure that the command is correctly executed. Ensure that the cluster, node, or instance is normal.
+
+GAUSS-51638: "Failed to append instance on host [%s]."
+
+SQLSTATE: None
+
+Description: Failed to add an instance on the node.
+
+Solution: Check whether the XML file is correctly configured and whether the path conflict exists. Ensure that the cluster, node, or instance is normal.
+
+GAUSS-51639: "Failed to obtain %s status of local node."
+
+SQLSTATE: None
+
+Description: Failed to obtain the local node status.
+
+Solution: Rectify the fault.
+
+GAUSS-51640: "Can't connect to cm_server, cluster is not running possibly."
+
+SQLSTATE: None
+
+Description:**cm_server** is not connected and the cluster is probably not running.
+
+Solution: Restart the cluster.
+
+GAUSS-51641: "Cluster redistributing status is not accord with expectation."
+
+SQLSTATE: None
+
+Description: The redistribution status does not meet the requirements.
+
+Solution: Check whether the cluster status is normal. Ensure that the cluster, node, or instance is normal.
+
+GAUSS-51642: "Failed to promote peer instances."
+
+SQLSTATE: None
+
+Description: Failed to start the peer instance.
+
+Solution: Ensure that the specified instance exists, that the command is correctly executed, and that the cluster, node, or instance is normal.
+
+GAUSS_51643: "Cluster is in read-only mode."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS_51644: "Failed to set resource control for the cluster."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-51645: "Failed to restart %s."
+
+SQLSTATE: None
+
+Description: Failed to restart the cluster or logical cluster.
+
+Solution: Ensure that the network connection is normal and that the configuration file is correct.
+
+GAUSS-51646: "The other OM operation is currently being performed in the cluster node:"" '%s'."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-51647: "The operation step of OM components in current cluster nodes do not match"" with each other: %s."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-51648: "Waiting for redistribution process to end timeout."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-51649: "Capture exceptions '%s' : %s."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-51650: "Unclassified exceptions: %s."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-51651: "The node '%s' status is Abnormal."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-51652: "The package version on some nodes are inconsistent."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-51653: "The %s can not exist in %s."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-51654: "The standbyIp %s should different Kerberos server IP %s."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-51655: "The %s has already installed."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-51656: "Failed to make server.key.cipher and server.key.rand"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-51700 - GAUSS-51799
+
+<br/>
+
+GAUSS-51704: "Failed to set Cgroup."
+
+SQLSTATE: None
+
+Description: Failed to configure cgroups.
+
+Solution: Configure cgroups again.
+
+GAUSS-51706: "Failed to check Cgroup."
+
+SQLSTATE: None
+
+Description: Failed to check cgroups.
+
+Solution: Check whether the database status is normal.
+
+GAUSS-51707: "Failed to install Cgroup."
+
+SQLSTATE: None
+
+Description: Failed to install cgroups.
+
+Solution: Check whether the cgroups component has been mounted to the database.
+
+GAUSS-51708: "Failed to uninstall Cgroup."
+
+SQLSTATE: None
+
+Description: Failed to uninstall cgroups.
+
+Solution: Uninstall cgroups again.
+
+GAUSS-51709: "Failed to clean Cgroup configuration file."
+
+SQLSTATE: None
+
+Description: Failed to clear the cgroups configuration file.
+
+Solution: Run the clearance command again.
+
+<br/>
+
+## GAUSS-51800 - GAUSS-51899
+
+<br/>
+
+GAUSS-51800: "The environmental variable %s is empty.·or·variable·has·exceeded·maximum·length"
+
+SQLSTATE: None
+
+Description: Environment variable is null.
+
+Solution: Ensure that the environment variable is successfully written.
+
+GAUSS-51801: "The environment variable %s exists."
+
+SQLSTATE: None
+
+Description: The environment variable exists.
+
+Solution: Check why the environment variable exists in the **.barshrc** file and confirm whether it is because the variable has been added in the file.
+
+GAUSS-51802: "Failed to obtain the environment variable %s."
+
+SQLSTATE: None
+
+Description: Failed to obtain the environment variable.
+
+Solution: Ensure that the environment variable configuration is complete. Check that whether the environment variable path is correct.
+
+GAUSS-51803: "Failed to delete the environment variable %s."
+
+SQLSTATE: None
+
+Description: Failed to delete the environment variable.
+
+Solution: Ensure that the deletion command is correct and that you have the permission to delete objects.
+
+GAUSS-51804: "Failed to set the environment variable %s."
+
+SQLSTATE: None
+
+Description: Failed to set the environment variables.
+
+Solution: Check whether the permission is correct. Check whether the network connection is normal. Check whether the command of setting the environment variable is correct.
+
+GAUSS-51805: "The environmental variable [%s]'s value is invalid."
+
+SQLSTATE: None
+
+Description: The environment variable value is invalid.
+
+Solution: Check whether the network connection is normal. Check whether the command of setting the environment variable is correct. Check whether the value of the *$GAUSS_ENV* environment variable in the ./bashrc file is correct.
+
+GAUSS-51806: "The cluster has been installed."
+
+SQLSTATE: None
+
+Description: The cluster has been installed.
+
+Solution: Check whether the value of the *$GAUSS_ENV* environment variable in the .bashrc file is 2.
+
+GAUSS-51807: "$GAUSSHOME of user is not equal to installation path."
+
+SQLSTATE: None
+
+Description: The GAUSSHOME path is inconsistent with that of the cluster installation path.
+
+Solution: Ensure that you have the path access permission and that the network connection is normal. Ensure that the command used for setting the environment variable is correct and that the value of the *$GAUSSHOME* environment variable in the ./bashrc file is the same as the path configured in the XML file.
+
+GAUSS-51808: "The env file contains errmsg: %s."
+
+SQLSTATE: None
+
+Description: The environment variable file package **/etc/profile** contains error or output flows.
+
+Solution: Check the files mentioned in the error information, run **source** to find the corresponding output and delete the corresponding shell.
+
+GAUSS-51809: "The variable [%s] context [%s] is invalid."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-51900 - GAUSS-51999
+
+<br/>
+
+GAUSS-51900: "The current OS is not supported."
+
+SQLSTATE: None
+
+Description: The current OS cannot be used.
+
+Solution: Check and switch to the OS that is supported for further operations.
+
+GAUSS-51901: "The OS versions are different among cluster nodes."
+
+SQLSTATE: None
+
+Description: The OSs between cluster nodes are inconsistent.
+
+Solution: Keep all nodes in the cluster use the same version of OS.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/78-GAUSS-52000-GAUSS-52999.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/78-GAUSS-52000-GAUSS-52999.md
new file mode 100644
index 0000000000000000000000000000000000000000..c0fbee7356c3f69f3cf75a91c0db2a29566177ad
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/78-GAUSS-52000-GAUSS-52999.md
@@ -0,0 +1,914 @@
+---
+title: GAUSS-52000 - GAUSS-52999
+summary: GAUSS-52000 - GAUSS-52999
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-52000 - GAUSS-52999
+
+<br/>
+
+## GAUSS-52000 - GAUSS-52099
+
+<br/>
+
+GAUSS-52000: "Failed to obtain time zone information about the cluster node."
+
+SQLSTATE: None
+
+Description: Failed to obtain the time zone of the cluster node.
+
+Solution: Check whether the time zone can successfully obtain command **date -R**.
+
+GAUSS-52001: "Time zone information is different among cluster nodes."
+
+SQLSTATE: None
+
+Description: Nodes in the cluster use different time zones.
+
+Solution: Use the **date** command to unify time zones of different nodes.
+
+<br/>
+
+## GAUSS-52100 - GAUSS-52199
+
+<br/>
+
+GAUSS-52100: "Failed to obtain cluster node character sets."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-52101: "Character sets are different among cluster nodes."
+
+SQLSTATE: None
+
+Description: Character sets are different among cluster nodes.
+
+Solution: Manually write the required character set forcibly on each node to the **/etc/profile** file.
+
+GAUSS-52102: "The parameter [%s] value is not equal to the expected value."
+
+SQLSTATE: None
+
+Description: The parameter value is not equal to the expected value.
+
+Solution: Set the parameter value to the expected value.
+
+GAUSS-52103: "Failed to forcibly make the character sets to take effect."
+
+SQLSTATE: None
+
+Description: Failed to force the character set to take effect.
+
+Solution: Reinstall the character set.
+
+<br/>
+
+## GAUSS-52200 - GAUSS-52299
+
+<br/>
+
+GAUSS-52200: "Unable to import module: %s."
+
+SQLSTATE: None
+
+Description: Using the default Python execution tool of the system results in imported package errors because the database that Python depends on is lacked.
+
+Solution: Use the Python execution tool of the installation package and go to the directory after the decompression using **./***Tool name* to run the command.
+
+Take the pre-processing script as an example:
+
+Go to the directory for storing tool scripts:
+
+```bash
+cd /opt/software/mogdb/script
+```
+
+Run the **./gs_preinstall** script:
+
+```bash
+./gs_preinstall -U omm -G dbgrp -X /opt/software/mogdb/clusterconfig.xml --alarm-type=5 --root-passwd=Gauss_234
+```
+
+GAUSS-52201: "The current python version %s is not supported."
+
+SQLSTATE: None
+
+Description: The default Python OS is not 2.6.X or 2.7.X.
+
+Solution: Use the default Python compiler in the OS.
+
+<br/>
+
+## GAUSS-52300 - GAUSS-52399
+
+<br/>
+
+GAUSS-52300: "Failed to set OS parameters."
+
+SQLSTATE: None
+
+Description: Failed to configure OS parameters.
+
+Solution:Contact technical support.
+
+GAUSS-52301: "Failed to check OS parameters."
+
+SQLSTATE: None
+
+Description: Failed to check OS parameters.
+
+Solution: Check whether the **uname -r 2>/dev/null** command is available. Check whether the **grep -Er '\' /etc/keepalived/keepalived.conf** command is executable. Check whether Python and the multiprocessing module have been installed.
+
+<br/>
+
+## GAUSS-52400 - GAUSS-52499
+
+<br/>
+
+GAUSS-52400: "Installation environment does not meet the desired result."
+
+SQLSTATE: None
+
+Description: The installation environment does not meet the requirements.
+
+Solution: Use **gs_checkos** to check OS configurations and ensure that it meets the requirements.
+
+GAUSS-52401: "On systemwide basis, the maximum number of %s is not correct. the current %s value is:"
+
+SQLSTATE: None
+
+Description: The maximum amount of semaphore in a semaphore set, the maximum number of semaphore sets, or the maximum amount of semaphore is incorrect. The current *%s* value is:
+
+Solution: View the semaphore obtained from **cat /proc/sys/kernel/sem** and check whether SEMMSL, SEMMNI, or SEMMNS meet the requirements.
+
+GAUSS-52402: "IP [%s] is not matched with hostname [%s]. \n"
+
+SQLSTATE: None
+
+Description: The IP address does not match the host name.
+
+Solution: Check whether the IP address matches the host name. If they are not matched, modify the **/etc/profile** file.
+
+GAUSS-52403: "Command \"%s\" does not exist or the user has no execute permission on %s."
+
+SQLSTATE: None
+
+Description: The command does not exist or you do not have the execution permission.
+
+Solution: Check whether the command exists. Ensure that you have the execution permission.
+
+<br/>
+
+## GAUSS-52500 - GAUSS-52599
+
+<br/>
+
+GAUSS-52500: "Failed to delete regular tasks."
+
+SQLSTATE: None
+
+Description: Failed to delete regular tasks.
+
+Solution:Contact technical support.
+
+GAUSS-52501: "Run %s script before executing this script."
+
+SQLSTATE: None
+
+Description: Another script needs to be run before you execute this script.
+
+Solution: Check the execution sequence of the scripts.
+
+GAUSS-52502: "Another OM process is being executed. To avoid conflicts, this process ends in advance."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-52503: "Failed to execute checkRunStatus.py. Error: %s"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-52600 - GAUSS-52699
+
+<br/>
+
+GAUSS-52600: "Can not obtain any cluster ring."
+
+SQLSTATE: None
+
+Description: Failed to obtain a ring from the database.
+
+Solution: Check whether the node information in the XML file is correctly configured.
+
+GAUSS-52601: "Redistribution failed due to user request."
+
+SQLSTATE: None
+
+Description: Redistribution failed due to user requests.
+
+Solution: Check whether users have performed invalid operations during the scale-in or scale-out process.
+
+GAUSS-52604: " Parameter '-r'[%s] can not be more than the numbers of cluster ring[%s]."
+
+SQLSTATE: None
+
+Description: The number of the **-r** parameters cannot exceed that of the database rings.
+
+Solution: Check whether the number of the **-r** parameters in the **gs_shrink** command exceeds that of database rings configured in the XML file.
+
+GAUSS-52605: "Can not contract local node(%s). "
+
+SQLSTATE: None
+
+Description: The local node cannot be scaled in.
+
+Solution: Ensure that the node where the scale-in command is executed has been configured in the XML.
+
+GAUSS-52606: " Contract too many nodes. It should left three nodes to format a cluster at least."
+
+SQLSTATE: None
+
+Description: Too many nodes are scaled in. Retain at least three nodes in the database after scale-in.
+
+Solution: Check whether the number of nodes in the XML file after the scale-in is smaller than three.
+
+GAUSS-52607: " [%s] does not at the end of instance list."
+
+SQLSTATE: None
+
+Description: The node is not at the end of the instance list.
+
+Solution: Check whether the scale-in nodes configured in the XML file are the nodes at the end of the database in sequence.
+
+GAUSS-52608: " [%s] contains %s instance."
+
+SQLSTATE: None
+
+Description: The code contains CM servers or ETCDs.
+
+Solution: Check whether the scale-in nodes include CM servers or ETCDs. If yes, reconfigure corresponding nodes to exclude them, and then run the command again.
+
+GAUSS-52609: " All contracted nodes do not contain DN instance."
+
+SQLSTATE: None
+
+Description: All the scale-in nodes cannot contain DNs.
+
+Solution: Check whether the scale-in nodes in the XML file contain DNs.
+
+GAUSS-52612: " All dilatation nodes do not contain the DN instance."
+
+SQLSTATE: None
+
+Description: All the scale-out nodes cannot contain DNs.
+
+Solution: Check whether the scale-out nodes in the XML file contain DNs.
+
+GAUSS-52613: " Static configuration is not matched on some nodes. Please handle it first."
+
+SQLSTATE: None
+
+Description: The static configuration file on the node does not match the new XML file.
+
+Solution: Reexecute the pre-processing script.
+
+GAUSS-52614: "Timeout. The current cluster status is %s."
+
+SQLSTATE: None
+
+Description: Timeout occurred.
+
+Solution: Perform the operation again.
+
+GAUSS-52615: "Cluster lock unlocked due to timeout. "
+
+SQLSTATE: None
+
+Description: Failed to unlock the database due to timeout.
+
+Solution: Check whether the database status is normal. Check whether the database can write data. View corresponding logs and detailed error information.
+
+GAUSS-52616: "Can not find a similar instance for [%s %s]. "
+
+SQLSTATE: None
+
+Description: A similar instance [the host name and instance directory] cannot be found.
+
+Solution: Check whether the database status is normal and whether the node information in the XML file is correctly configured.
+
+GAUSS-52617: "Invalid check type. "
+
+SQLSTATE: None
+
+Description: The check type is invalid.
+
+Solution: Ensure that the check types of the node groups in the scale-in module are precheck and postcheck. Other check types are incorrect.
+
+GAUSS-52618: "Failed to delete etcd from node. "
+
+SQLSTATE: None
+
+Description: Failed to delete the ETCD.
+
+Solution:Contact technical support.
+
+GAUSS-52619: "Failed to uninstall application."
+
+SQLSTATE: None
+
+Description: Failed to uninstall the application.
+
+Solution: Perform the operation again.
+
+GAUSS-52620: " Not all nodes found. The following is what we found: %s."
+
+SQLSTATE: None
+
+Description: Failed to find all nodes. The nodes that we found are as follows:
+
+Solution: Check whether the database status is normal and whether the configured scale-in node in the XML file is correct.
+
+GAUSS-52621: " No DNs specified in target create new group."
+
+SQLSTATE: None
+
+Description: No DN is available when you create a node group.
+
+Solution: Check and determine whether the DN configured on the node is normal when you scale in a module and create a node group.
+
+GAUSS-52622: " No new group name specified in target create new group."
+
+SQLSTATE: None
+
+Description: No node group name is available when you create a node group.
+
+Solution: The node group name is empty when you scale in a module and create a node group. Check whether the new node group name is correct. The new node group name value is **group_version2** or **group_version1**.
+
+GAUSS-52625: "The local instance and peer instance does not both in contracted nodes. "
+
+SQLSTATE: None
+
+Description: The local instance and the peer instance are not located on the same scale-in node.
+
+Solution: Check whether the scale-in nodes are formed into a ring.
+
+GAUSS-52627: " The current cluster is locked."
+
+SQLSTATE: None
+
+Description: The database has been locked.
+
+Solution: In the scale-out module, the old node database has been locked. Unlock it and continue scaling out the current database.
+
+GAUSS-52628: "Static configuration has already been updated on all nodes, expansion has been completed possibly. "
+
+SQLSTATE: None
+
+Description: The static configuration file has been updated on each node. The scale-out is probably complete.
+
+Solution: Check whether the database status is normal after the scale-out. If the database includes the scale-out nodes and the database status is normal, do not execute any scale-out commands any more.
+
+GAUSS-52629: "Cluster ring(%s) can not obtain less than three nodes. "
+
+SQLSTATE: None
+
+Description: The number of database rings cannot be less than three.
+
+Solution: Check the XML file configuration in the scale-in scenario to see whether the number of scale-in nodes to be executed is smaller than three.
+
+GAUSS-52630: "Failed to set the read-only mode parameter for all DN instances. "
+
+SQLSTATE: None
+
+Description: Failed to set the read-only mode parameter for all DN instances.
+
+Solution: Check whether the **gs_guc** tool exists and whether the database status is normal. Set the read-only mode again.
+
+GAUSS-52632: "Cluster breakdown or abnormal operation during expanding online, lock process for expansion is lost."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-52633: "Can not excute redistribution for shrink excuted failed."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-52634: "Redis table record count cannot be more than %d."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-52700 - GAUSS-52799
+
+<br/>
+
+GAUSS-52700: "Failed to update ETCD."
+
+SQLSTATE: None
+
+Description: Failed to update the ETCD.
+
+Solution: Solve the problem based on the replace logs.
+
+GAUSS-52701: "All the CMAgents instances are abnormal. Cannot fix the cluster."
+
+SQLSTATE: None
+
+Description: All the CM Agent instances are damaged and the cluster cannot be restored.
+
+Solution: Use **gs_replace** to perform warm backup.
+
+GAUSS-52702: "The cluster status is Normal. There is no instance to fix."
+
+SQLSTATE: None
+
+Description: The cluster status is normal and no instance needs to be restored.
+
+Solution: Do not perform the restore operation.
+
+GAUSS-52703: "The number of normal ETCD must be greater than half."
+
+SQLSTATE: None
+
+Description: More than half of the ETCDs in the cluster must be normal.
+
+Solution: Check whether the cluster status is normal after the warm backup and whether the number of normal ETCDs in the cluster exceeds half of the whole ETCDs.
+
+GAUSS-52704: "Failed to check the %s condition."
+
+SQLSTATE: None
+
+Description: Failed to check the condition.
+
+Solution: Check whether the corresponding process is normal.
+
+GAUSS-52705: "Failed to obtain ETCD key."
+
+SQLSTATE: None
+
+Description: Failed to obtain the ETCD key.
+
+Solution: View the etcdctl logs and solve the problem.
+
+GAUSS-52706: "Failed to clean ETCD and touch flag file on %s."
+
+SQLSTATE: None
+
+Description: Failed to clear ETCD instances and create flag files on the nodes.
+
+Solution: Check whether there are sufficient permissions on corresponding nodes.
+
+GAUSS-52707: "Failed to install on %s."
+
+SQLSTATE: None
+
+Description: Failed to install the warm backup node.
+
+Solution: Solve the problem based on the replace logs.
+
+GAUSS-52708: "Failed to configure on %s."
+
+SQLSTATE: None
+
+Description: Failed to configure the warm backup node.
+
+Solution: Solve the problem based on the replace logs.
+
+GAUSS-52709: "Failed to check the cluster configuration differences:"
+
+SQLSTATE: None
+
+Description: Failed to check the cluster configuration difference.
+
+Solution: When performing the warm backup or modifying the IP address, check whether the XML file and the current cluster configuration are different. If they are the same, skip the preceding operations. Modify the XML configuration information again.
+
+GAUSS-52710: "Replacement failed."
+
+SQLSTATE: None
+
+Description: Failed to replace the instance.
+
+Solution: View the logs and find out detailed failure information.
+
+GAUSS-52711: "Failed to set CMAgent start mode."
+
+SQLSTATE: None
+
+Description: Failed to set the CM Agent startup mode.
+
+Solution: View the etcdctl logs and solve the problem.
+
+GAUSS-52712: "Failed to read step file with erro:[%s]."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-52713: "Failed to repair cm_server, errorinfo:[%s]."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-52714: "Failed to write step file, errorinfo:[%s]."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-52800 - GAUSS-52899
+
+<br/>
+
+GAUSS-52800: "Cluster is %s(%s) now."
+
+SQLSTATE: None
+
+Description: The cluster status is **Abnormal** or **Degrade**.
+
+Solution: Check the cluster status based on the log report analysis.
+
+GAUSS-52801: "Only allow to %s one CN. The %s is not matched."
+
+SQLSTATE: None
+
+Description: Only a CN can be added or deleted. The number of CNs, DNs, GTMs, ETCDs, or CM servers does not match that configured in the XML file.
+
+Solution: Check whether other instances are added or deleted in the XML file.
+
+GAUSS-52802: "Only allow to add one CN at the end."
+
+SQLSTATE: None
+
+Description: Only a CN can be added at the end.
+
+Solution: Check the specified XML configuration. Only a CN can be added at the end of the last node in the cluster.
+
+GAUSS-52803: "There is at least one Normal CN after delete CN."
+
+SQLSTATE: None
+
+Description: Retain at least a normal CN after the CNs are deleted.
+
+Solution: Check whether the XML file where CNs to be deleted are located is properly configured. Ensure that at least a normal CN exists in the cluster after all the CNs are deleted.
+
+GAUSS-52804: "Failed to add the Abnormal CN."
+
+SQLSTATE: None
+
+Description: Failed to add an abnormal CN.
+
+Solution: Analyze the failure reason based on the logs when modifying the **pgxc_node** file fails. Re-execute the command.
+
+GAUSS-52805: "Failed to find another instance as model for instance(%s)."
+
+SQLSTATE: None
+
+Description: No instance template is available.
+
+Solution: Check detailed logs and analyze the reason.
+
+GAUSS-52806: "Invalid rollback step: %s."
+
+SQLSTATE: None
+
+Description: The rollback procedure is invalid.
+
+Solution: In the **GPHOST** directory, check whether data in the **GaussManageCN.dat** file that records the CN configuration procedure is correct.
+
+GAUSS-52807: "There is no IP changed."
+
+SQLSTATE: None
+
+Description: No IP address needs to be modified.
+
+Solution: Check whether the IP address has been already used in the cluster. If it has been used, reconfigure the XML file.
+
+GAUSS-52808: "Detected CN %s, but the action is %s."
+
+SQLSTATE: None
+
+Description: The CN to be added or deleted does not match that configured in the XML file.
+
+Solution: Modify the operations of adding or deleting CNs in the command, or modify the CN configuration information in the XML file.
+
+GAUSS-52809: "Only allow to add or delete one CN."
+
+SQLSTATE: None
+
+Description: The number of CNs to be added or deleted is greater than 1.
+
+Solution: Only one CN can be added or deleted at a time.
+
+GAUSS-52810: "There is Abnormal coodinator(s) in cluster, please delete it firstly."
+
+SQLSTATE: None
+
+Description: There is an abnormal CN in the cluster. As a result, other CNs cannot be deleted.
+
+Solution: Delete the abnormal CN, and then delete other CNs.
+
+<br/>
+
+## GAUSS-52900 - GAUSS-52999
+
+<br/>
+
+GAUSS-52900: " Failed to upgrade strategy: %s."
+
+SQLSTATE: None
+
+Description: Failed to upgrade the policy.
+
+Solution: Check the version information file **version.cfg**.
+
+GAUSS-52901: "New·cluster·commitid·cannot·be·same·with·old·cluster·commitid."
+
+SQLSTATE: None
+
+Description: The binary upgrade backup path cannot exist with the major version upgrade backup path.
+
+Solution: Determine the reason of the last upgrade failure and sort backup files.
+
+GAUSS-52902: "Can not support upgrade from %s to %s"
+
+SQLSTATE: None
+
+Description: The version cannot be upgraded.
+
+Solution: Use a supported version or an intermediate version for upgrade.
+
+GAUSS-52903: "The new cluster version number[%s] should be bigger than the old cluster[%s]."
+
+SQLSTATE: None
+
+Description: Version rollback is not supported, which means the version number after the upgrade must be greater than that of the previous version.
+
+Solution: Confirm the version information.
+
+GAUSS-52904: "Please choose right upgrade strategy."
+
+SQLSTATE: None
+
+Description: The right upgrade policy should be selected.
+
+Solution: Revoke a policy and select an interface. Use the upgrade interface properly, or invoke an automatic upgrade interface.
+
+GAUSS-52905: "Upgrade nodes number cannot be more than %d."
+
+SQLSTATE: None
+
+Description: Failed to obtain the current version.
+
+Solution: View the logs and find out detailed error information.
+
+GAUSS-52906: "Grey upgrade nodes number cannot be more than cluster nodes."
+
+SQLSTATE: None
+
+Description: The upgrade initialization failed.
+
+Solution: View the upgrade logs and identify the fault cause. Initialize the upgrade again.
+
+GAUSS-52907: "Failed to cancel the cluster read-only mode"
+
+SQLSTATE: None
+
+Description: Failed to cancel the cluster read-only mode.
+
+Solution: Manually invoke the GUC tool using commands **gs_guc reload -Z coordinator -N all -I all -c "default_transaction_read_only=false"** and **gs_guc reload -Z datanode -N all -I all -c "default_transaction_read_only=false"**. Try to cancel the read-only mode again.
+
+GAUSS-52908: "Failed to set cluster read-only mode."
+
+SQLSTATE: None
+
+Description: Failed to set the read-only mode.
+
+Solution: View the GUC logs. After troubleshooting the error, run the command again.
+
+GAUSS-52909: "Specified upgrade nodes with same step can do upgrade task."
+
+SQLSTATE: None
+
+Description: The mode is invalid.
+
+Solution: Find corresponding log information.
+
+GAUSS-52910: "These nodes %s have been successfully upgraded to new version, no need to upgrade again."
+
+SQLSTATE: None
+
+Description: Failed to check the user definition.
+
+Solution: Check whether errors exist in the user-defined check script. Identify the upgrade cause based on the expectation.
+
+GAUSS-52911: "Last unsuccessfully upgrade nodes %s are not same with current upgrade nodes."
+
+SQLSTATE: None
+
+Description: The full upgrade failed.
+
+Solution: Perform the upgrade again.
+
+GAUSS-52912: "Some nodes were upgraded but were unsuccessfully, cannot use -continue."
+
+SQLSTATE: None
+
+Description: Failed to enable the cluster in normal mode.
+
+Solution: Manually identify the cause. Invoke the **gs_om -t start** command to enable the cluster.
+
+GAUSS-52913: "All nodes have been upgraded. No need to use -continue."
+
+SQLSTATE: None
+
+Description: Rollback failed.
+
+Solution: Perform the operation again.
+
+GAUSS-52914: "The record commitid is not same with current commitid."
+
+SQLSTATE: None
+
+Description: Failed to clear the rollback script.
+
+Solution: Check the cluster status. If the upgrade succeeds, manually delete the remaining files.
+
+GAUSS-52915: "$GAUSSHOME is not a symbolic link."
+
+SQLSTATE: None
+
+Description: The upgrade procedure is invalid.
+
+Solution: In the **GPHOST** path, confirm whether the backup file that records the upgrade procedure is modified.
+
+GAUSS-52916: "Current upgrade status is not pre commit."
+
+SQLSTATE: None
+
+Description: The cluster node does not meet the submission conditions.
+
+Solution: Submit the upgrade project after all nodes are successfully upgraded.
+
+GAUSS-52917: "Failed to drop old pmk schema."
+
+SQLSTATE: None
+
+Description: The upgrade in binary mode fails and rolls back to the primitive cluster.
+
+Solution: View the upgrade logs and identify the fault cause. Perform the upgrade again.
+
+GAUSS-52918: "Failed to record node upgrade step in table %s.%s."
+
+SQLSTATE: None
+
+Description: Failed to find the GTM.
+
+Solution: Invoke the **gs_om -t status -detail** command to query the cluster status. If the GTM cluster in the cluster is abnormal, reinstall the cluster or perform warm backup to restore the cluster.
+
+GAUSS-52919: "Upgrade has already been committed but not finished commit."
+
+SQLSTATE: None
+
+Description: The upgrade failed.
+
+Solution: View the upgrade logs and identify the fault cause. Perform the upgrade again as required.
+
+GAUSS-52920: "Can not use grey upgrade option -continue before upgrade grey nodes."
+
+SQLSTATE: None
+
+Description: Failed to restore the GUC parameters after the full upgrade.
+
+Solution: View the upgrade logs and the GUC logs. Identify the cause and perform the upgrade again.
+
+GAUSS-52921: "Failed to query disk usage with gs_check tool."
+
+SQLSTATE: None
+
+Description: The upgrade type is invalid.
+
+Solution: Use the automatic upgrade interfaces.
+
+GAUSS-52922: "Disk usage exceeds %s, please clean up before upgrading."
+
+SQLSTATE: None
+
+Description: Failed to record the upgrade procedure.
+
+Solution: Confirm that you have the permission on the temporary file directory or that the directory exists.
+
+GAUSS-52923: "Inplace upgrade commit failed.\n%s"
+
+SQLSTATE: None
+
+Description: Failed to record the upgrade status.
+
+Solution: Confirm that you have the permission on the temporary file directory or that the directory exists.
+
+GAUSS-52924: "The %s parameter are only supported in independent deployment mode."
+
+SQLSTATE: None
+
+Description: The information in the upgrade status file is incorrect.
+
+Solution: Modify the upgrade backup file and try to restore the record file based on the upgrade procedure.
+
+GAUSS-52925: "Input upgrade type [%s] is not same with record upgrade type [%s]."
+
+SQLSTATE: None
+
+Description: An incorrect upgrade interface is used.
+
+Solution: Use the automatic upgrade interface or automatic rollback interface.
+
+GAUSS-52926: "The step of upgrade should be digit."
+
+SQLSTATE: None
+
+Description: The upgrade procedure must be a digit.
+
+Solution: Check whether the upgrade backup file is modified and try to restore it.
+
+GAUSS-52929: "Failed to check application version. Output: \n%s."
+
+SQLSTATE: None
+
+Description: Failed to check the cluster version.
+
+Solution: Check the upgrade logs and confirm the version information on each node.
+
+GAUSS-52932: "There is no CN in the remaining old nodes."
+
+SQLSTATE: None
+
+Description: No CNs are available in the old cluster.
+
+Solution: Check the upgrade logs and confirm the instance information on each node.
+
+GAUSS-52933: "There is not a majority of %s on the remaining old nodes."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-52934: "Binary upgrade failed."
+
+SQLSTATE: None
+
+Description: Failed to upgrade.
+
+Solution: Check the upgrade logs or contact R&D engineers to locate the fault.
+
+GAUSS-52935: "Current upgrade version is not same with unfinished upgrade version record."
+
+SQLSTATE: None
+
+Description: The previous upgrade operation is not complete (not committed or rolled back), and the upgrade is intended to be performed to another version.
+
+Solution: Submit or roll back the previous upgrade, and then perform the upgrade of another version.
+
+GAUSS-52936: "Upgrade is not finished, cannot do another task."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/79-GAUSS-53000-GAUSS-53699.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/79-GAUSS-53000-GAUSS-53699.md
new file mode 100644
index 0000000000000000000000000000000000000000..b58c700444b1fee994f9492d96c7c130150e20fa
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/79-GAUSS-53000-GAUSS-53699.md
@@ -0,0 +1,954 @@
+---
+title: GAUSS-53000 - GAUSS-53699
+summary: GAUSS-53000 - GAUSS-53699
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-53000 - GAUSS-53699
+
+<br/>
+
+## GAUSS-53000 - GAUSS-53099
+
+<br/>
+
+GAUSS-53000: The database user [%s] is not match with the old user [%s].
+
+SQLSTATE: None
+
+Description: The database user does not match the old user.
+
+Solution: Verify that the entered user is correct.
+
+GAUSS-53001: The result of query table is incorrect: %s.
+
+SQLSTATE: None
+
+Description: The returned result for querying the table is incorrect.
+
+Solution: Check whether the database is normal.
+
+GAUSS-53002: Failed to obtain SSD device.
+
+SQLSTATE: None
+
+Description: Failed to obtain the SSD device.
+
+Solution: Check whether the SSD is installed.
+
+GAUSS-53003: The checked item does not meet the standards.
+
+SQLSTATE: None
+
+Description: The check item does not meet the standard.
+
+Solution: Check whether the SSD status is normal.
+
+GAUSS-53004: Failed to collect statistics on all nodes.
+
+SQLSTATE: None
+
+Description: Failed to collect statistics on all nodes.
+
+Solution: Check whether the database is working properly.
+
+GAUSS-53005: Unable to obtain SSD disk on current node.
+
+SQLSTATE: None
+
+Description: Failed to obtain the SSD.
+
+Solution: Check whether the SSD is installed.
+
+GAUSS-53006: No DN instance uses data directory %s on %s.
+
+SQLSTATE: None
+
+Description: The DN data directory does not exist.
+
+Solution: Check whether the DN directory exists.
+
+GAUSS-53007: Failed to switch %s.
+
+SQLSTATE: None
+
+Description: Failed to switch between the primary and standby instances.
+
+Solution: Solve the problem based on the CM logs.
+
+GAUSS-53008: The current node do not install SSD. Can not check SSD performance.
+
+SQLSTATE: None
+
+Description: The SSD is not installed on the current node.
+
+Solution: Install and use the SSD.
+
+GAUSS-53009: Failed to format cu of directory: %s.
+
+SQLSTATE: None
+
+Description: Failed to format the column-store file.
+
+Solution: Rectify the fault based on the pg_format_cu logs.
+
+GAUSS-53010: The function name of %s is not exist in the %s.
+
+SQLSTATE: None
+
+Description: The script does not contain this method.
+
+Solution: Ensure that the command is correct.
+
+GAUSS-53011: Failed to check %s.
+
+SQLSTATE: None
+
+Description: The check failed.
+
+Solution: Solve the problem based on the check logs.
+
+GAUSS-53012: Failed to insert pmk data to database.
+
+SQLSTATE: None
+
+Description: The check failed.
+
+Solution: Rectify the fault based on the gs_checkperf logs.
+
+GAUSS-53013: "Failed to force failover."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-53014: "Performance jobs not enabled."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-53100 - GAUSS-53199
+
+<br/>
+
+GAUSS-53100: "[%s] is not supported in single cluster."
+
+SQLSTATE: None
+
+Description: The check failed.
+
+Solution: Do not use user-specified ports for standalone deployment.
+
+GAUSS-53101: "This interface is not supported in %s cluster.""
+
+SQLSTATE: None
+
+Description: The check failed.
+
+Solution: Do not use user-specified ports in the current cluster.
+
+GAUSS-53102: "[%s] is not supported in express cluster."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-53103: "The single primary multi standby cluster does not support the product"" version '%s'."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-53104: "[%s] is not supported in single instance cluster."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-53200 - GAUSS-53299
+
+<br/>
+
+GAUSS-53200: "The number of standbys for each DN instance must be the same. Please set it."
+
+SQLSTATE:42501
+
+Description: The user has insufficient permissions and cannot connect to the static database.
+
+Solution: Modify the user permissions and try again.
+
+GAUSS-53201: "The number of DN standbys and the AZ settings are incorrect. Please set it."
+
+SQLSTATE:22023
+
+Description: The disk space is insufficient.
+
+Solution: Release the disk space and try again.
+
+GAUSS-53202: "The AZ information is incorrect. Please set it."
+
+SQLSTATE:42P25
+
+Description: No AGG operator exists in the plan.
+
+Solution:Contact technical support.
+
+GAUSS-53203: "The number of ETCD in %s. Please set it."
+
+SQLSTATE:42601
+
+Description: The AGG syntax is incorrect.
+
+Solution: Modify the query statement and try again.
+
+GAUSS-53204: "[%s] is not supported in single primary multistandby cluster."
+
+SQLSTATE:42P24
+
+Description: The attribute column does not exist.
+
+Solution: Change the attribute column and try again.
+
+GAUSS-53205: "The priority of %s must be higher than %s. Please set it."
+
+SQLSTATE:42P24
+
+Description: The column attribute value exceeds the maximum length of the column.
+
+Solution: Modify the column attribute value and try again.
+
+GAUSS-53206: "The value of %s must be greater than 0 and less than 11. Please set it."
+
+SQLSTATE:01000
+
+Description: The username does not exist. The **SQL COUNT** cannot be found in a hash table.
+
+Solution: Change the username and try again.
+
+[GAUSS-53207]: "cannot convert abstime 'invalid' to timestamp"
+
+SQLSTATE:0A000
+
+Description: Failed to convert the low-precision abstime into timestamp.
+
+Solution: Change the value to a valid one, and try again.
+
+[GAUSS-53208]: "cannot convert infinity to numeric"
+
+SQLSTATE:0A000
+
+Description: Failed to convert the infinite value into the numeric type.
+
+Solution: Change the value to a valid one, and try again.
+
+[GAUSS-53209]: "cannot convert reltime 'invalid' to interval"
+
+SQLSTATE:0A000
+
+Description: Failed to convert reltime into a time interval.
+
+Solution: Change the value to a valid one, and try again.
+
+[GAUSS-53210]: "can't initialize bitmap index scans using unusable index '%s'"
+
+SQLSTATE:XX002
+
+Description: The index is invalid. Failed to initialize the bitmap index scanning.
+
+Solution: Change the value to a valid index, and try again.
+
+[GAUSS-53211]: "can't initialize bitmap index scans using unusable local index '%s'"
+
+SQLSTATE:XX002
+
+Description: The local index is invalid. Failed to initialize the bitmap index scanning.
+
+Solution: Change the value to a valid index, and try again.
+
+[GAUSS-53212]: "can't initialize index scans using unusable index '%s'"
+
+SQLSTATE:XX002
+
+Description: The index is invalid. Failed to initialize the index scanning.
+
+Solution: Change the value to a valid index, and try again.
+
+[GAUSS-53213]: "can't initialize index scans using unusable local index '%s'"
+
+SQLSTATE:XX002
+
+Description: The local index is invalid. Failed to initialize the index scanning.
+
+Solution: Change the value to a valid index, and try again.
+
+[GAUSS-53214]: "can't initialize index-only scans using unusable index '%s'"
+
+SQLSTATE:XX002
+
+Description: The index is invalid. Failed to initialize the full index scanning.
+
+Solution: Change the value to a valid index, and try again.
+
+[GAUSS-53215]: "can't initialize index-only scans using unusable local index '%s'"
+
+SQLSTATE:XX002
+
+Description: The local index is invalid. Failed to initialize the full index scanning.
+
+Solution: Change the value to a valid index, and try again.
+
+[GAUSS-53216]: "cgroup is not initialized or group name %s is invalid!"
+
+SQLSTATE:42P26
+
+Description: Failed to initialize cgroups or the group name is invalid.
+
+Solution:Contact technical support.
+
+[GAUSS-53217]: "cgroup is not initialized!"
+
+SQLSTATE:42704
+
+Description: Failed to initialize cgroups.
+
+Solution:Contact technical support.
+
+[GAUSS-53218]: "class group %s doesn't exist!"
+
+SQLSTATE:42704
+
+Description: The cgroup does not exist.
+
+Solution: Create a cgroup and try again.
+
+[GAUSS-53219]: "component in parameter 'dynamic_library_path' is not an absolute path"
+
+SQLSTATE:42602
+
+Description: The path in **dynamic_library_path** is not an absolute path.
+
+Solution: Change the path in **dynamic_library_path** to an absolute path.
+
+[GAUSS-53220]: "conflicting key value violates exclusion constraint '%s'"
+
+SQLSTATE:23P01
+
+Description: Key value conflict occurs, which violates the exclusion constraint.
+
+Solution: Change the key value and try again.
+
+[GAUSS-53221]: "could not convert format string from UTF-8: error code %lu"
+
+SQLSTATE:22021
+
+Description: Failed to format UTF-8 characters.
+
+Solution:Contact technical support.
+
+[GAUSS-53222]: "could not create exclusion constraint '%s'"
+
+SQLSTATE:23P01
+
+Description: Failed to create the exclusion constraint.
+
+Solution:Contact technical support.
+
+[GAUSS-53223]: "could not create locale '%s': %m"
+
+SQLSTATE:22023
+
+Description: Failed to create the database character set.
+
+Solution: Use the existing database character set.
+
+[GAUSS-53224]: "could not create unique index '%s'"
+
+SQLSTATE:23505
+
+Description: Failed to create the unique index column.
+
+Solution:Contact technical support.
+
+[GAUSS-53225]: "internal function '%s' is not in internal lookup table"
+
+SQLSTATE:XX005
+
+Description: Failed to find the function definition in the function lookup table.
+
+Solution: Ensure that the function in the SQL statement is valid.
+
+[GAUSS-53226]: "invalid address family in external '%s' value"
+
+SQLSTATE:22P03
+
+Description: The network address family is invalid.
+
+Solution: Check whether the format of the entered network address is correct.
+
+[GAUSS-53227]: "invalid attribute name"
+
+SQLSTATE:42602
+
+Description: The attribute name is invalid.
+
+Solution: Check the input strings.
+
+[GAUSS-53228]: "invalid bits in external '%s' value"
+
+SQLSTATE:22P03
+
+Description: The network address family is invalid.
+
+Solution: Check whether the format of the entered network address is correct.
+
+[GAUSS-53229]: "invalid cidr value: '%s'"
+
+SQLSTATE:22P02
+
+Description: The network address family is invalid.
+
+Solution: Check whether the format of the entered network address is correct.
+
+[GAUSS-53230]: "invalid digit in external 'numeric' value"
+
+SQLSTATE:22P03
+
+Description: The numeric input is invalid.
+
+Solution: Check whether the data contains invalid numeric input. For the valid format of the numeric type, see en-us_topic_0274503547.html.
+
+[GAUSS-53231]: "invalid external 'cidr' value"
+
+SQLSTATE:22P03
+
+Description: The network address is invalid.
+
+Solution: Check whether the format of the entered network address is correct.
+
+[GAUSS-53232]: "invalid input syntax for %s: '%s'"
+
+SQLSTATE:22P02
+
+Description: The network address is invalid.
+
+Solution: Check whether the format of the entered network address is correct.
+
+[GAUSS-53233]: "invalid length in external '%s' value"
+
+SQLSTATE:22P03
+
+Description: The network address is invalid.
+
+Solution: Check whether the format of the entered network address is correct.
+
+[GAUSS-53234]: "invalid name of logical cluster: NULL or ""
+
+SQLSTATE:42602
+
+Description: The logical cluster name is invalid.
+
+Solution: Check whether the entered logical cluster or its name is empty.
+
+[GAUSS-53235]: "invalid name of memory context: NULL or ""
+
+SQLSTATE:42602
+
+Description: The memory context name is invalid.
+
+Solution: Check whether the entered memory context or its name is empty.
+
+[GAUSS-53236]: "invalid name of resource pool: NULL or ""
+
+SQLSTATE:42602
+
+Description: The resource pool name is invalid.
+
+Solution: Check whether the entered resource pool or its name is empty.
+
+[GAUSS-53237]: "invalid octet value in 'macaddr' value: '%s'"
+
+SQLSTATE:22003
+
+Description: Syntax error.
+
+Solution: Modify the SQL statement.
+
+[GAUSS-53238]: "invalid regexp option: '%c'"
+
+SQLSTATE:22023
+
+Description: The regexp conversion type is invalid.
+
+Solution: Check the input parameter.
+
+[GAUSS-53239]: "invalid sign in external 'numeric' value"
+
+SQLSTATE:22P03
+
+Description: The numeric input is invalid.
+
+Solution: Check whether the data contains invalid numeric input. For the valid format of the numeric type, see en-us_topic_0274503547.html.
+
+[GAUSS-53240]: "invalid status in external 'tinterval' value"
+
+SQLSTATE:22P03
+
+Description: The internal error status obtained in the entered string is inconsistent with the data status.
+
+Solution: Check the input character string.
+
+[GAUSS-53241]: "invalid time zone name: '%s'"
+
+SQLSTATE:22023
+
+Description: The time zone name is invalid.
+
+Solution: Check whether the time zone name is valid.
+
+[GAUSS-53242]: "kill backend is prohibited during online expansion."
+
+SQLSTATE:42501
+
+Description: Do not kill the backend process during online extension.
+
+Solution:Contact technical support.
+
+[GAUSS-53243]: "malformed range literal: '%s'"
+
+SQLSTATE:22P02
+
+Description: Syntax error.
+
+Solution: Check the SQL statement.
+
+[GAUSS-53244]: "malformed record literal: '%s'"
+
+SQLSTATE:22P02
+
+Description: An internal error occurs.
+
+Solution:Contact technical support.
+
+[GAUSS-53245]: "more than one function named '%s'"
+
+SQLSTATE:42725
+
+Description: An internal error occurs.
+
+Solution:Contact technical support.
+
+[GAUSS-53246]: "multidimensional arrays must have array "expressions with matching dimensions"
+
+SQLSTATE:2202E
+
+Description: Multi-dimensional arrays must be provided with dimension-matching expressions.
+
+Solution: Check the input strings.
+
+[GAUSS-53247]: "must be system admin to cancel invalid queries running in all server processes"
+
+SQLSTATE:42501
+
+Description: You do not have the permission to cancel the illegal query from the server process.
+
+Solution: Switch to the system administrator and cancel the illegal query.
+
+[GAUSS-53248]: "must be system admin to reset bad block statistics counters"
+
+SQLSTATE:42501
+
+Description: You do not have the permission to reset damaged block statistics.
+
+Solution: Switch to the system administrator and reset the damaged block statistics.
+
+[GAUSS-53249]: "must be system admin to view the global information"
+
+SQLSTATE:42501
+
+Description: You do not have the permission to view the global distribution of all tables.
+
+Solution: Switch to the system administrator and view the global distribution of all tables.
+
+[GAUSS-53250]: "unrecognized paramkind: %d"
+
+SQLSTATE:XX004
+
+Description: The parameter type is unknown.
+
+Solution: Check the execution plan parameters.
+
+[GAUSS-53251]: "unrecognized reset target: '%s'"
+
+SQLSTATE:22023
+
+Description: The reset target information is unknown.
+
+Solution: Check the name of the reset target information.
+
+[GAUSS-53252]: "unrecognized XML operation"
+
+SQLSTATE:XX004
+
+Description: The XML operation is unknown.
+
+Solution: Check the XML content.
+
+[GAUSS-53253]: "unsupported reference to system column %d in FieldSelect"
+
+SQLSTATE:42P10
+
+Description: An internal error occurs.
+
+Solution:Contact technical support.
+
+[GAUSS-53254]: "update or delete on table '%s' violates foreign key constraint '%s' on table '%s'"
+
+SQLSTATE:23503
+
+Description: The update or delete operation violates the foreign key constraint.
+
+Solution: Check the related statement and foreign key information.
+
+[GAUSS-53255]: "value "%s' is out of range for type %s"
+
+SQLSTATE:22003
+
+Description: The data value exceeds the valid range of the data type.
+
+Solution: Check related data values and data types.
+
+[GAUSS-53256]: "value for domain %s violates check constraint '%s'"
+
+SQLSTATE:23514
+
+Description: The domain values violate the check constraint.
+
+Solution: Check the related domain values.
+
+[GAUSS-53257]: "WindowFunc found in non-WindowAgg plan node"
+
+SQLSTATE:42P20
+
+Description: An internal error occurs.
+
+Solution:Contact technical support.
+
+[GAUSS-53258]: "workload group %s doesn't exist!"
+
+SQLSTATE:42704
+
+Description: The cgroup information is not defined.
+
+Solution: Check the cgroup configuration file.
+
+[GAUSS-53259]: "wrong pg_constraint entry for trigger '%s' on table '%s'"
+
+SQLSTATE:23514
+
+Description: An internal error occurs.
+
+Solution:Contact technical support.
+
+[GAUSS-53260]: "zero-length component in parameter 'dynamic_library_path'"
+
+SQLSTATE:42602
+
+Description: The dynamic database path is abnormal.
+
+Solution: Check the path of the dynamic database.
+
+<br/>
+
+## GAUSS-53300 - GAUSS-53399
+
+<br/>
+
+GAUSS-53300: "The current product version '%s' does not support the license " "register/unregister operation."
+
+SQLSTATE: None
+
+Description: The current product version does not support license registration or deregistration.
+
+Solution: Currently, only MogDB 200 supports license registration and deregistration.
+
+GAUSS-53301: "The license control files are not consistent on the cluster."
+
+SQLSTATE: None
+
+Description: The license files are inconsistent in the cluster.
+
+Solution: Contact O&M personnel.
+
+GAUSS-53302: "The current cluster does not apply the license control, please upgrade it" " first."
+
+SQLSTATE: None
+
+Description: The current database version does not support license management or the license files of all nodes in the cluster are lost.
+
+Solution: If you have not registered any license with FusionInsight Manager, upgrade the database to a version that supports license management. Otherwise, contact O&M personnel to handle the problem that all licenses are lost.
+
+GAUSS-53303: "The DWS cluster does not support the license register/unregister operation."
+
+SQLSTATE: None
+
+Description: The cloud-based DWS cluster does not support license registration or deregistration.
+
+Solution: Currently, only MogDB 200 supports license registration and deregistration.
+
+GAUSS-53304: "Can not register the enabled features."
+
+SQLSTATE: None
+
+Description: The enabled features cannot be registered.
+
+Solution: Correct the command line parameters and register again.
+
+GAUSS-53304: "Can not un-register the disabled features."
+
+SQLSTATE: None
+
+Description: The disabled features cannot be deregistered.
+
+Solution: Correct the command line parameters and perform deregistration again.
+
+GAUSS-53306: "Can not register the unsupported features of the product version '%s'."
+
+SQLSTATE: None
+
+Description: The features not supported by the specified product version cannot be registered.
+
+Solution: Correct the command line parameters and register again.
+
+GAUSS-53307: "No need to un-register the unsupported features of the product version '%s'."
+
+SQLSTATE: None
+
+Description: The features not supported by the specified product version do not need to be deregistered.
+
+Solution: Correct the command line parameters and perform deregistration again.
+
+<br/>
+
+## GAUSS-53400 - GAUSS-53499
+
+<br/>
+
+GAUSS-53400: "Roach ETCD term operate failed."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-53401: "Roach delete/clean operate failed, Failed to clean %s"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-53402: "Get %s cluster infomation/env failed, %s"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-53403: "Cluster balance check failed"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution: Check whether the cluster is down. If not, contact technical support.
+
+GAUSS-53404: "backup key %s does not exist"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-53500 - GAUSS-53599
+
+<br/>
+
+GAUSS-53500: "Relation %s does not exist."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-53501: "Connect to server failed, connection refused"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-53502: "Please check database status"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-53503: "There is no coordinator inst in this host"
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-53504: "There is no %s files: please check start-time and end-time."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-53505: "There is no log files: please check cluster info."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-53506: "Failed to mkdir."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-53507: "Failed to execute %s command."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-53508: "Core pattern is not core-e-p-t."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-53509: "There is no core files: please check core file name pattern is core-e-p-t."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-53510: "Please check db status or database name."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-53511: "There is no %s process."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-53512: "Gstack command not found."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-53513: "Schema '%s' is not in white list."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-53514: "Relation '%s' does not belong to '%s' schema."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-53515: "Database content '%s' is invalid, only support 'schema.relation'."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-53600 - GAUSS-53699
+
+<br/>
+
+GAUSS-53600: "CA password must contain at least eight characters."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-53601: "CA password cannot contain %s."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-53602: "CA password is too simple."
+
+SQLSTATE: None
+
+Description:Internal system error.
+
+Solution:Contact technical support.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/8-GAUSS-00701-GAUSS-00800.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/8-GAUSS-00701-GAUSS-00800.md
new file mode 100644
index 0000000000000000000000000000000000000000..f4dcbc2adec357cc2ca708987dcf5a4c3b2f0642
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/8-GAUSS-00701-GAUSS-00800.md
@@ -0,0 +1,764 @@
+---
+title: GAUSS-00701 - GAUSS-00800
+summary: GAUSS-00701 - GAUSS-00800
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-00701 - GAUSS-00800
+
+<br/>
+
+## GAUSS-00701 - GAUSS-00710
+
+<br/>
+
+GAUSS-00701: "cannot rename inherited constraint '%s'"
+
+SQLSTATE: 42P16
+
+Description: The name of an inherited constraint is modified.
+
+Solution: Do not modify the name of an inherited constraint.
+
+GAUSS-00702: "relation '%s' already exists"
+
+SQLSTATE: 42P07
+
+Description: The relation already exists.
+
+Solution: Ensure that the relation name is unique.
+
+GAUSS-00703: "GTM error, could not rename sequence"
+
+SQLSTATE: 08006
+
+Description: GTM fails to rename a sequence.
+
+Solution: Use **gs_om -t status -detail** to check whether the GTM status is normal.
+
+GAUSS-00706: "partition '%s' of relation '%s' already exists"
+
+SQLSTATE: 42P07
+
+Description: A table partition of the same name already exists.
+
+Solution: Ensure that the table partition name is unique.
+
+GAUSS-00710: "cache lookup failed for partition %u of relation %u"
+
+SQLSTATE: 42704
+
+Description: Failed to find the partition.
+
+Solution: The system is abnormal. Contact technical support.
+
+<br/>
+
+## GAUSS-00711 - GAUSS-00720
+
+<br/>
+
+GAUSS-00711: "cannot %s '%s' because it is being used by active queries in this session"
+
+SQLSTATE: 55006
+
+Description: The object to be modified is being used.
+
+Solution: Modify the object after the active queries are complete.
+
+GAUSS-00712: "cannot %s '%s' because it has pending trigger events"
+
+SQLSTATE: 55006
+
+Description: Pending trigger events are detected when a table is modified.
+
+Solution: Modify the table after pending trigger events are handled.
+
+GAUSS-00713: "Un-support feature"
+
+SQLSTATE: 0A000
+
+Description: Feature not supported.
+
+Solution: Do not use it.
+
+GAUSS-00714: "unrecognized alter table type: %d"
+
+SQLSTATE: XX000
+
+Description: The table is changed to an unsupported type.
+
+Solution: Check whether the new table type is supported.
+
+GAUSS-00715: "Incompatible operation with data redistribution"
+
+SQLSTATE: 54001
+
+Description: The **ALTER** statement is incompatible with data redistribution.
+
+Solution: Use the **ALTER** statement that is compatible with data redistribution.
+
+GAUSS-00716: "cannot set with oids on partitioned table"
+
+SQLSTATE: 0A000
+
+Description: The attribute OIDs of partitioned tables are modified.
+
+Solution: Do not modify the attribute OIDs of partitioned tables.
+
+GAUSS-00717: "cannot set without oids on partitioned table"
+
+SQLSTATE: 0A000
+
+Description: The attribute OIDs of partitioned tables are modified.
+
+Solution: Do not modify the attribute OIDs of partitioned tables.
+
+GAUSS-00718: "cannot rewrite temporary tables of other sessions"
+
+SQLSTATE: 0A000
+
+Description: Temporary tables of other sessions are rewritten.
+
+Solution: Do not rewrite temporary tables of other sessions.
+
+GAUSS-00719: "cannot rewrite system relation '%s'"
+
+SQLSTATE: 0A000
+
+Description: The system catalog is rewritten.
+
+Solution: Do not rewrite the system catalog.
+
+<br/>
+
+## GAUSS-00721 - GAUSS-00730
+
+<br/>
+
+GAUSS-00721: "column '%s' contains null values"
+
+SQLSTATE: 23502
+
+Description: Non-null columns contain null values.
+
+Solution: Check for conflicts in not-null constraints.
+
+GAUSS-00722: "check constraint '%s' is violated by some row"
+
+SQLSTATE: 23514
+
+Description: Some rows violate check constraints.
+
+Solution: Check for conflicts in check constraints.
+
+GAUSS-00723: "cannot alter type '%s' because column '%s.%s' uses it"
+
+SQLSTATE: 0A000
+
+Description: The column type cannot be modified, because other columns depend on this column.
+
+Solution: Check whether other columns depend on it. If they do, delete them and then modify the column type.
+
+GAUSS-00724: "cannot alter foreign table '%s' because column '%s.%s' uses its row type"
+
+SQLSTATE: 0A000
+
+Description: A foreign table cannot be modified if its row type is being used by a column.
+
+Solution: Check whether other columns depend on it. If they do, delete them and then modify the table.
+
+GAUSS-00725: "cannot alter table '%s' because column '%s.%s' uses its row type"
+
+SQLSTATE: 0A000
+
+Description: A table cannot be modified if its row type is being used by a column.
+
+Solution: Check whether other columns depend on it. If they do, delete them and then modify the table.
+
+GAUSS-00726: "cannot alter type '%s' because it is the type of a typed table"
+
+SQLSTATE: 2BP01
+
+Description: The type of a typed table cannot be modified.
+
+Solution: Use **ALTER … CASCADE** to modify the typed table.
+
+GAUSS-00727: "type %s is not a composite type"
+
+SQLSTATE: 42809
+
+Description: The type of **CREATE TABLE OFALTER TABLE OF** is not a composite one.
+
+Solution: Use a composite type and try again.
+
+GAUSS-00728: "cannot add column to typed table"
+
+SQLSTATE: 42809
+
+Description: Columns are added to a typed table.
+
+Solution: Do not add columns to a typed table.
+
+GAUSS-00729: "type '%s' is not supported in column store"
+
+SQLSTATE: 0A000
+
+Description: Column storage does not support this column type.
+
+Solution: Choose the correct column type and try again.
+
+GAUSS-00730: "default value cannot reference to a column"
+
+SQLSTATE: 42809
+
+Description: A default value cannot be used in a column.
+
+Solution: Check whether the default value is enclosed by a pair of quotation marks.
+
+<br/>
+
+## GAUSS-00731 - GAUSS-00740
+
+<br/>
+
+GAUSS-00731: "child table '%s' has different type for column '%s'"
+
+SQLSTATE: 42804
+
+Description: When **AddColumn** is run to add a column to a parent table, this column and a column in the child tables share the same name but have different types.
+
+Solution: Modify the type of the column to be added to that of the child tables.
+
+GAUSS-00732: "child table '%s' has different collation for column '%s'"
+
+SQLSTATE: 42P21
+
+Description: When **AddColumn** is run to add a column to a parent table, this column and a column in the child tables share the same name but have different collations.
+
+Solution: Modify the collation of the column to be added to that of the child tables.
+
+GAUSS-00733: "child table '%s' has a conflicting '%s' column"
+
+SQLSTATE: 42804
+
+Description: When **AddColumn** is run to add a column to a parent table, the column already exists in the child tables.
+
+Solution: Rename the column to be added.
+
+GAUSS-00735: "column must be added to child tables too"
+
+SQLSTATE: 42P16
+
+Description: When **AddColumn** is run to add a column to a parent table, the column is not added to the child tables.
+
+Solution: Add the column recursively to the child tables.
+
+GAUSS-00736: "column '%s' of relation '%s' already exists"
+
+SQLSTATE: 42701
+
+Description: When a column is added to a relational table or a column name is changed, the column name already exists.
+
+Solution: Specify the column name again.
+
+GAUSS-00737: "cannot alter system column '%s'"
+
+SQLSTATE: 0A000
+
+Description: When **ALTER TABLE ALTER COLUMN DROP** is run, the column of a system catalog cannot be modified.
+
+Solution: Cancel this operation.
+
+GAUSS-00738: "column '%s' is in a primary key"
+
+SQLSTATE: 42P16
+
+Description: When **ALTER TABLE ALTER COLUMN DROP** is run, the primary key of a table cannot be modified.
+
+Solution: Cancel this operation.
+
+GAUSS-00739: "'%s' is not a table, index, or foreign table"
+
+SQLSTATE: 42809
+
+Description: When **ALTER TABLE ALTER COLUMN SET STATISTICS** is run, the object to be modified is not a common table, index, or foreign table.
+
+Solution: Run this statement when the object is a common table, index, or foreign table, or cancel this operation.
+
+GAUSS-00740: "statistics target %d is too low"
+
+SQLSTATE: 22023
+
+Description: When **ALTER TABLE ALTER COLUMN SET STATISTICS** is run, the value of a statistics target is excessively small.
+
+Solution: Set a valid value for the statistics target.
+
+<br/>
+
+## GAUSS-00741 - GAUSS-00750
+
+<br/>
+
+GAUSS-00741: "invalid storage type '%s'"
+
+SQLSTATE: 22023
+
+Description: When **ALTER TABLE ALTER COLUMN SET STORAGE** is run, the target data storage type is invalid.
+
+Solution: Modify the target data storage type to a valid one.
+
+GAUSS-00742: "column data type %s can only have storage PLAIN"
+
+SQLSTATE: 0A000
+
+Description: When **ALTER TABLE ALTER COLUMN SET STORAGE** is run, the column data storage type is not set to **PLAIN**.
+
+Solution: Set the column data storage type to **PLAIN**.
+
+GAUSS-00743: "cannot drop column from typed table"
+
+SQLSTATE: 42809
+
+Description: When **ALTER TABLE DROP COLUMN** is run, the column of a typed table cannot be deleted.
+
+Solution: Cancel this operation.
+
+GAUSS-00745: "cannot drop system column '%s'"
+
+SQLSTATE: 0A000
+
+Description: When **ALTER TABLE DROP COLUMN** is run, the column of a system catalog cannot be deleted.
+
+Solution: Cancel this operation.
+
+GAUSS-00747: "cache lookup failed for attribute '%s' of relation %u"
+
+SQLSTATE: XX000
+
+Description: Failed to find the column.
+
+Solution: The system is abnormal. Contact technical support.
+
+GAUSS-00748: "relation %u has non-inherited attribute '%s'"
+
+SQLSTATE: XX000
+
+Description: The inherited table does not have the corresponding inherited columns.
+
+Solution: The system is abnormal. Contact technical support.
+
+GAUSS-00749: "index '%s' is not unique"
+
+SQLSTATE: XX000
+
+Description: The index related to the added unique constraint does not have the unique attribute.
+
+Solution: The system is abnormal. Contact technical support.
+
+GAUSS-00750: "constraint '%s' for relation '%s' already exists"
+
+SQLSTATE: 42710
+
+Description:**ALTER TABLE ADD CONSTRAINT** cannot be run if new constraints already exist.
+
+Solution: Modify the new constraints.
+
+<br/>
+
+## GAUSS-00751 - GAUSS-00760
+
+<br/>
+
+GAUSS-00751: "cluster key for relation '%s' already exists"
+
+SQLSTATE: 42710
+
+Description:**ALTER TABLE ADD CONSTRAINT** cannot be run if the cluster key of a relational table already exists.
+
+Solution: Modify the new constraints.
+
+GAUSS-00753: "referenced relation '%s' is not a table"
+
+SQLSTATE: 42809
+
+Description: When foreign key constraints are added to a table, the referenced table of foreign key constraints is not an ordinary table.
+
+Solution: Ensure that the referenced table of foreign key constraints is an ordinary table.
+
+GAUSS-00754: "Invalid FOREIGN KEY constraints"
+
+SQLSTATE: 42809
+
+Description: The referenced table of foreign key constraints is a partitioned table although the partitioned table supports creating foreign key constraints.
+
+Solution: Ensure that the referenced table of foreign key constraints is an ordinary table.
+
+GAUSS-00755: "constraints on permanent tables may reference only permanent tables"
+
+SQLSTATE: 42P16
+
+Description: Foreign key constraints on ordinary tables do not reference ordinary tables.
+
+Solution: Modify the referenced tables of foreign key constraints to ordinary tables.
+
+GAUSS-00756: "constraints on unlogged tables may reference only permanent or unlogged tables"
+
+SQLSTATE: 42P16
+
+Description: Foreign key constraints on unlogged tables do not reference ordinary tables or unlogged tables.
+
+Solution: Modify the referenced tables of the foreign key constraints to ordinary tables or unlogged tables.
+
+GAUSS-00757: "constraints on temporary tables may reference only temporary tables"
+
+SQLSTATE: 42P16
+
+Description: Foreign key constraints on temporary tables do not reference temporary tables.
+
+Solution: Modify the referenced tables of the foreign key restraints to temporary tables, or cancel this operation.
+
+GAUSS-00758: "constraints on temporary tables must involve temporary tables of this session"
+
+SQLSTATE: 42P16
+
+Description: Foreign key constraints on temporary tables do not reference local temporary tables.
+
+Solution: Modify the referenced tables of the foreign key restraints to temporary tables, or cancel this operation.
+
+GAUSS-00759: "number of referencing and referenced columns for foreign key disagree"
+
+SQLSTATE: 42830
+
+Description: When foreign key constraints are added to a table, the number of constrained columns differs from that of quoted columns.
+
+Solution: Modify the foreign key constraints to ensure that the number of constrained columns is the same as that of quoted columns.
+
+GAUSS-00760: "only b-tree indexes are supported for foreign keys"
+
+SQLSTATE: XX000
+
+Description: The index of the primary key corresponding to the foreign key is not a B-tree index.
+
+Solution: Ensure that the unique constraint index of the primary key is a B-tree index.
+
+<br/>
+
+## GAUSS-00761 - GAUSS-00770
+
+<br/>
+
+GAUSS-00761: "missing operator %d(%u,%u) in opfamily %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00762: "foreign key constraint '%s' cannot be implemented"
+
+SQLSTATE: 42804
+
+Description: When foreign key constraints are added to a table, the type of constrained columns differs from that of quoted columns.
+
+Solution: Modify the foreign key constraints to ensure that the type of constrained columns is the same as that of quoted columns.
+
+GAUSS-00763: "Cannot create foreign key whose evaluation cannot be enforced to remote nodes"
+
+SQLSTATE: 0A000
+
+Description: When foreign key constraints are added to a table, the foreign key constraints on referencing remote nodes cannot be created.
+
+Solution: Cancel this operation.
+
+GAUSS-00764: "constraint '%s' of relation '%s' does not exist"
+
+SQLSTATE: 42704
+
+Description: When **ALTER TABLE VALIDATE CONSTRAINT** is run, the constraint on a table does not exist.
+
+Solution: Modify the constraints that already exist, or cancel this operation.
+
+GAUSS-00765: "constraint '%s' of relation '%s' is not a foreign key or check constraint"
+
+SQLSTATE: 42809
+
+Description: When **ALTER TABLE VALIDATE CONSTRAINT** is run, the relationship constraints are not foreign key constraints or check constraints.
+
+Solution: Modify or cancel this operation.
+
+GAUSS-00766: "constraint must be validated on child tables too"
+
+SQLSTATE: 42P16
+
+Description: When **ALTER TABLE VALIDATE CONSTRAINT** is run to add a constraint to a parent table, the constraint is not added to the child tables.
+
+Solution: Add the constraint to the child tables.
+
+GAUSS-00767: "column '%s' referenced in foreign key constraint does not exist"
+
+SQLSTATE: 42703
+
+Description: The referenced column of foreign key constraints on a relational table does not exist.
+
+Solution: Modify the foreign key constraints.
+
+GAUSS-00768: "cannot have more than %d keys in a foreign key"
+
+SQLSTATE: 54011
+
+Description: The number of referenced columns for a foreign key is greater than 32.
+
+Solution: Limit the number of referenced columns for a foreign key.
+
+GAUSS-00769: "cannot use a deferrable primary key for referenced table '%s'"
+
+SQLSTATE: 55000
+
+Description:**GetPrimaryKey** cannot be run for a deferrable primary key.
+
+Solution: Cancel this operation.
+
+GAUSS-00770: "there is no primary key for referenced table '%s'"
+
+SQLSTATE: 42704
+
+Description: When **GetPrimaryKey** is run, the referenced table has no primary key.
+
+Solution: Cancel this operation.
+
+<br/>
+
+## GAUSS-00771 - GAUSS-00780
+
+<br/>
+
+GAUSS-00771: "cannot use a deferrable unique constraint for referenced table '%s'"
+
+SQLSTATE: 55000
+
+Description: Foreign keys depend on a deferrable unique constraint.
+
+Solution: Modify the dependency of foreign keys.
+
+GAUSS-00772: "there is no unique constraint matching given keys for referenced table '%s'"
+
+SQLSTATE: 42830
+
+Description: Keys of the table that foreign keys depend on are not unique.
+
+Solution: Modify dependency of foreign keys.
+
+GAUSS-00773: "could not find cast from %u to %u"
+
+SQLSTATE: XX000
+
+Description: The conversion method between the types cannot be found.
+
+Solution: Verify that no type conversion method is available in the **pg_cast** system catalog. Contact technical support.
+
+GAUSS-00774: "null conbin for constraint %u"
+
+SQLSTATE: XX000
+
+Description: The constraint attribute is null.
+
+Solution: The system catalog is abnormal. Contact technical support.
+
+GAUSS-00775: "unrecognized FK action type: %d"
+
+SQLSTATE: XX000
+
+Description: The foreign key trigger type does not exist.
+
+Solution: Check the type of the foreign key trigger.
+
+GAUSS-00776: "cannot drop inherited constraint '%s' of relation '%s'"
+
+SQLSTATE: 42P16
+
+Description: When **ALTER TABLE DROP CONSTRAINT** is run, inherited constraints cannot be deleted.
+
+Solution: Modify this operation.
+
+GAUSS-00777: "relation %u has non-inherited constraint '%s'"
+
+SQLSTATE: XX000
+
+Description: The inherited table does not have the corresponding inherited constraints.
+
+Solution: The system catalog is abnormal. Contact technical support.
+
+GAUSS-00778: "cannot alter column type of typed table"
+
+SQLSTATE: 42809
+
+Description: When **ALTER COLUMN TYPE** is run, the column type of a typed table cannot be modified.
+
+Solution: Modify this operation.
+
+GAUSS-00779: "cannot alter inherited column '%s'"
+
+SQLSTATE: 42P16
+
+Description: When **ALTER COLUMN TYPE** is run, the column type of an inherited table cannot be modified.
+
+Solution: Modify this operation.
+
+GAUSS-00780: "cache lookup failed for pgxc_class %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+<br/>
+
+## GAUSS-00781 - GAUSS-00790
+
+<br/>
+
+GAUSS-00781: "cannot alter data type of distribute column"
+
+SQLSTATE: 0A000
+
+Description: When **ALTER COLUMN TYPE** is run, the distribution column type of a table cannot be modified.
+
+Solution: Modify this operation.
+
+GAUSS-00784: "cannot use subquery in transform expression"
+
+SQLSTATE: 0A000
+
+Description: When **ALTER COLUMN TYPE** is run, a transform expression uses a subquery.
+
+Solution: Modify this operation.
+
+GAUSS-00785: "cannot use aggregate function in transform expression"
+
+SQLSTATE: 42803
+
+Description: When **ALTER COLUMN TYPE** is run, a transform expression uses an aggregate function.
+
+Solution: Modify this operation.
+
+GAUSS-00786: "cannot use window function in transform expression"
+
+SQLSTATE: 42P20
+
+Description: When **ALTER COLUMN TYPE** is run, a transform expression uses a window function.
+
+Solution: Modify this operation.
+
+GAUSS-00788: "type of inherited column '%s' must be changed in child tables too"
+
+SQLSTATE: 42P16
+
+Description: When **ALTER COLUMN TYPE** is run, the column type of a child table does not change as the column type of its parent table changes.
+
+Solution: In the statement, specify that the child table changes when the parent table changes.
+
+GAUSS-00789: "cannot alter data type of partitioning column '%s'"
+
+SQLSTATE: 0A000
+
+Description: When **ALTER COLUMN TYPE** is run, the column type of a partitioned table cannot be modified.
+
+Solution: Modify this operation.
+
+GAUSS-00790: "cannot alter type of column '%s' twice"
+
+SQLSTATE: 0A000
+
+Description: When **ALTER COLUMN TYPE** is run, the type of a column cannot be modified twice.
+
+Solution: Modify a column type only once.
+
+<br/>
+
+## GAUSS-00791 - GAUSS-00800
+
+<br/>
+
+GAUSS-00791: "default for column '%s' cannot be cast automatically to type %s"
+
+SQLSTATE: 42804
+
+Description: When **ALTER COLUMN TYPE** is run, a default expression cannot be automatically cast to a type.
+
+Solution: Modify this operation.
+
+GAUSS-00792: "cannot alter type of a pinned column"
+
+SQLSTATE: XX000
+
+Description: The type of the column cannot be changed, because other objects depend on it.
+
+Solution: Find and delete the dependency, and then change the column type.
+
+GAUSS-00793: "unexpected object depending on column: %s"
+
+SQLSTATE: XX000
+
+Description: The dependency type does not exist.
+
+Solution: The system catalog is abnormal. Contact technical support.
+
+GAUSS-00794: "cannot alter type of a column used by a view or rule"
+
+SQLSTATE: 0A000
+
+Description: When **ALTER COLUMN TYPE** is run, a view or rule is used to change the type of a column.
+
+Solution: Modify this operation.
+
+GAUSS-00795: "cannot alter type of a column used in a trigger definition"
+
+SQLSTATE: 0A000
+
+Description: When **ALTER COLUMN TYPE** is run, the type of a column used in a trigger definition cannot be modified.
+
+Solution: Modify this operation.
+
+GAUSS-00796: "unrecognized object class: %u"
+
+SQLSTATE: XX000
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00797: "found unexpected dependency type '%c'"
+
+SQLSTATE: XX000
+
+Description: The dependency type is incorrect.
+
+Solution: The system catalog is abnormal. Contact technical support.
+
+GAUSS-00798: "found unexpected dependency for column"
+
+SQLSTATE: XX000
+
+Description: The column dependency type is incorrect.
+
+Solution: The system catalog is abnormal. Contact technical support.
+
+GAUSS-00799: "foreign table '%s' does not exist"
+
+SQLSTATE: 42704
+
+Description: When **ALTER COLUMN OPTIONS** is run, a foreign table does not exist.
+
+Solution: Modify this operation.
+
+GAUSS-00800: "unexpected statement type: %d"
+
+SQLSTATE: XX000
+
+Description: The clause to change a statement is incorrect.
+
+Solution: Check whether the clause is supported.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/9-GAUSS-00801-GAUSS-00900.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/9-GAUSS-00801-GAUSS-00900.md
new file mode 100644
index 0000000000000000000000000000000000000000..de691c342642af9b62928368c3913a90d7416332
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/9-GAUSS-00801-GAUSS-00900.md
@@ -0,0 +1,724 @@
+---
+title: GAUSS-00801 - GAUSS-00900
+summary: GAUSS-00801 - GAUSS-00900
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-00801 - GAUSS-00900
+
+<br/>
+
+## GAUSS-00801 - GAUSS-00810
+
+<br/>
+
+GAUSS-00801: "null conpfeqop for constraint %u"
+
+SQLSTATE: XX005
+
+Description: The constraint attribute is null.
+
+Solution: The system catalog is abnormal. Contact technical support.
+
+GAUSS-00802: "conpfeqop is not a 1-D Oid array"
+
+SQLSTATE: 42804
+
+Description: The constraint array is not one-dimensional.
+
+Solution: The system catalog is abnormal. Contact technical support.
+
+GAUSS-00803: "cannot change owner of sequence '%s'"
+
+SQLSTATE: 0A000
+
+Description: When **ALTER TABLE OWNER** is run, the owner of a sequence cannot be changed by the owner itself.
+
+Solution: Cancel this operation.
+
+GAUSS-00804: "'%s' is a composite type"
+
+SQLSTATE: 42809
+
+Description: When **ALTER TABLE OWNER** is run, the owner of a composite type cannot be changed.
+
+Solution: Cancel this operation.
+
+GAUSS-00805: "'%s' is not a table, view, sequence, or foreign table"
+
+SQLSTATE: 42809
+
+Description: When **ALTER TABLE OWNER** is run, the object whose owner to be changed is not a common table, view, sequence, or foreign table.
+
+Solution: Modify the object to a common table, view, sequence, or foreign table.
+
+GAUSS-00806: "index '%s' for table '%s' does not exist"
+
+SQLSTATE: 42704
+
+Description: When **ALTER TABLE CLUSTER ON** is run, the index for a table does not exist.
+
+Solution: Cancel this operation.
+
+GAUSS-00807: "cannot have multiple SET TABLESPACE subcommands"
+
+SQLSTATE: 42601
+
+Description: When **ALTER TABLE SET TABLESPACE** is run, multiple **SET TABLESPACE** sub-commands are run.
+
+Solution: Run one **SET TABLESPACE** sub-command at a time.
+
+GAUSS-00808: "relkind of psort tuple shouldn't be '%c'."
+
+SQLSTATE: XX000
+
+Description: The table type related to psort is incorrect.
+
+Solution: Check whether the table is column-store.
+
+GAUSS-00809: "psort tuple doesn't have the correct ORIENTATION value."
+
+SQLSTATE: XX000
+
+Description: The table type related to psort is incorrect.
+
+Solution: Check whether the table is column-store.
+
+GAUSS-00810: "cache lookup failed for relation %u"
+
+SQLSTATE: XX000
+
+Description: When **ALTER TABLE SET TABLESPACE** is run, the relational table does not exist.
+
+Solution: Modify this operation.
+
+<br/>
+
+## GAUSS-00811 - GAUSS-00820
+
+<br/>
+
+GAUSS-00811: "'%s' is not a table, index, or TOAST table"
+
+SQLSTATE: 42809
+
+Description: The set, reset, replace, or reloptions operation is not performed on a table, index, or a toast table.
+
+Solution: Perform this operation on a table, index, or toast table only.
+
+GAUSS-00812: "can not set tablespace for partition of neither table nor index"
+
+SQLSTATE: 42601
+
+Description: The tablespace is set for objects other than tables and indexes in a partitioned table.
+
+Solution: Perform this operation on a table or index only.
+
+GAUSS-00816: "cache lookup failed for partition %u"
+
+SQLSTATE: XX000
+
+Description: Failed to find the partition in the cache.
+
+Solution: Ensure that the partition is valid.
+
+GAUSS-00817: "cannot move system relation '%s'"
+
+SQLSTATE: 0A000
+
+Description: When **ALTER TABLE SET TABLESPACE** is run, the system catalog cannot be moved.
+
+Solution: Cancel this operation.
+
+GAUSS-00819: "cannot change inheritance of typed table"
+
+SQLSTATE: 42809
+
+Description: When **ALTER TABLE INHERIT** is run, the table to which a parent table is added is a typed table.
+
+Solution: Cancel this operation.
+
+GAUSS-00820: "relation '%s' is a partitioned table"
+
+SQLSTATE: XX000
+
+Description: When **ALTER TABLE INHERIT** is run, the table to which a parent table is added is a partitioned table.
+
+Solution: Cancel this operation.
+
+<br/>
+
+## GAUSS-00821 - GAUSS-00830
+
+<br/>
+
+GAUSS-00821: "cannot inherit to temporary relation of another session"
+
+SQLSTATE: 42809
+
+Description: When **ALTER TABLE INHERIT** is run, the temporary relational table of another session cannot be inherited.
+
+Solution: Cancel this operation.
+
+GAUSS-00822: "circular inheritance not allowed"
+
+SQLSTATE: 42P07
+
+Description: When **ALTER TABLE INHERIT** is run, circular inheritance is forbidden.
+
+Solution: Cancel this operation.
+
+GAUSS-00823: "table '%s' without OIDs cannot inherit from table '%s' with OIDs"
+
+SQLSTATE: 42809
+
+Description: When **ALTER TABLE INHERIT** is run, tables without OIDs cannot inherit other tables.
+
+Solution: Add OIDs to tables.
+
+GAUSS-00824: "column '%s' in child table must be marked NOT NULL"
+
+SQLSTATE: 42804
+
+Description: When **ALTER TABLE INHERIT** is run, a parent table has the NOT NULL constraint, but the column of a child table does not have the constraint.
+
+Solution: Add the NOT NUll constraint to the column attribute of the child table.
+
+GAUSS-00825: "child table is missing column '%s'"
+
+SQLSTATE: 42804
+
+Description: When **ALTER TABLE INHERIT** is run, a child table lacking a column cannot inherit a parent table.
+
+Solution: Add the missing column to the child table, or cancel this operation.
+
+GAUSS-00826: "child table '%s' has different definition for check constraint '%s'"
+
+SQLSTATE: 42804
+
+Description: When **ALTER TABLE INHERIT** is run, a child table and a parent table have different definitions on a constraint.
+
+Solution: Ensure that the parent and child tables have the same definition on a constraint.
+
+GAUSS-00827: "constraint '%s' conflicts with non-inherited constraint on child table '%s'"
+
+SQLSTATE: 42P17
+
+Description: When **ALTER TABLE INHERIT** is run, the constraint on a parent table conflicts with the non-inherited constraint on a child table.
+
+Solution: Modify the constraint on the parent or child table.
+
+GAUSS-00828: "child table is missing constraint '%s'"
+
+SQLSTATE: 42804
+
+Description: When **ALTER TABLE INHERIT** is run, a constraint is missing in a child table.
+
+Solution: Modify this operation.
+
+GAUSS-00829: "relation '%s' is not a parent of relation '%s'"
+
+SQLSTATE: 42P01
+
+Description: When **ALTER TABLE NO INHERIT** is run to delete parent table constraints on a child table, the child table does not have the parent table relationship.
+
+Solution: Do not delete the constraints directly.
+
+GAUSS-00830: "typed tables cannot inherit"
+
+SQLSTATE: 42809
+
+Description: When **ALTER TABLE OF** is run, the inherited table cannot be of composite type.
+
+Solution: Cancel this operation.
+
+<br/>
+
+## GAUSS-00831 - GAUSS-00840
+
+<br/>
+
+GAUSS-00831: "table is missing column '%s'"
+
+SQLSTATE: 42804
+
+Description: The column does not exist.
+
+Solution: The system catalog is abnormal. Contact technical support.
+
+GAUSS-00832: "table has column '%s' where type requires '%s'"
+
+SQLSTATE: 42804
+
+Description: The column names of tables and types are inconsistent.
+
+Solution: The system catalog is abnormal. Contact technical support.
+
+GAUSS-00833: "table '%s' has different type for column '%s'"
+
+SQLSTATE: 42804
+
+Description: The attributes of tables and types are inconsistent.
+
+Solution: The system catalog is abnormal. Contact technical support.
+
+GAUSS-00834: "table has extra column '%s'"
+
+SQLSTATE: 42804
+
+Description: The table contains redundant columns.
+
+Solution: The system catalog is abnormal. Contact technical support.
+
+GAUSS-00835: "'%s' is not a typed table"
+
+SQLSTATE: 42809
+
+Description: The DROP OF operation is performed on a non-typed table.
+
+Solution: Ensure that the table is a typed table.
+
+GAUSS-00837: "Distribution mode cannot be altered"
+
+SQLSTATE: 0A000
+
+Description: The **ALTER TABLE** statement is used to modify the distribution mode.
+
+Solution: Do not use the **ALTER TABLE** statement to modify the distribution mode.
+
+GAUSS-00838: "Cannot alter table to distribution incompatible with existing constraints"
+
+SQLSTATE: 0A000
+
+Description: The redistribution of a table is incompatible with the constraints on the table.
+
+Solution: Modify the redistribution to be compatible with the constraints.
+
+GAUSS-00839: "Node list is empty: one node at least is mandatory"
+
+SQLSTATE: 42710
+
+Description: When **DELETE NODE LIST** is run, the node list to be deleted is empty.
+
+Solution: Do not run **DELETE NODE LIST** on empty node lists.
+
+GAUSS-00840: "PGXC Node %s: object not in relation node list"
+
+SQLSTATE: 42710
+
+Description: When **DELETE NODE LIST** is run, the node to be deleted does not exist in a specified node list.
+
+Solution: Do not run **DELETE NODE LIST** on nodes that does not exist in the list.
+
+<br/>
+
+## GAUSS-00841 - GAUSS-00850
+
+<br/>
+
+GAUSS-00841: "PGXC Node %s: object already in relation node list"
+
+SQLSTATE: 42710
+
+Description: When **ADD NODE LIST** is run, the node to be added already exists in a specified node list.
+
+Solution: This operation is not required.
+
+GAUSS-00842: "cannot move an owned sequence into another schema"
+
+SQLSTATE: 0A000
+
+Description: When **ALTER TABLE SET SCHEMA** is run, the sequence of an owner is moved to another schema.
+
+Solution: Do not move the sequence of an owner to another schema.
+
+GAUSS-00843: "relation '%s' already exists in schema '%s'"
+
+SQLSTATE: 42P07
+
+Description: When **ALTER RELATION NAMESPACE** is run, the relation whose namespace is to be modified already exists in the schema.
+
+Solution: This operation is not required.
+
+GAUSS-00844: "failed to change schema dependency for relation '%s'"
+
+SQLSTATE: XX000
+
+Description: Failed to change the schema dependency of the table.
+
+Solution: The system catalog is abnormal. Contact technical support.
+
+GAUSS-00845: "permission denied: system catalog '%s' can not be altered"
+
+SQLSTATE: 42501
+
+Description: The RENAME, SET SCHEMA, or ALTER TABLE operation is performed on a system catalog.
+
+Solution: Do not modify a system catalog.
+
+GAUSS-00846: "'%s' is not a sequence"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00847: "'%s' is not a foreign table"
+
+SQLSTATE: 42809
+
+Description:Internal system error.
+
+Solution:Contact technical support.
+
+GAUSS-00848: "'%s' is not a composite type"
+
+SQLSTATE: 42809
+
+Description: The object is not a composite type.
+
+Solution: Check whether the operation object is a composite type.
+
+GAUSS-00849: "'%s' is not an index"
+
+SQLSTATE: 42809
+
+Description: An index operation is performed on a non-index table.
+
+Solution: Perform this operation on an index table.
+
+GAUSS-00850: "'%s' is a foreign table, which does not support column constraints."
+
+SQLSTATE: 42809
+
+Description: The foreign table and does not support column constraints.
+
+Solution: Do not add column constraints to foreign tables.
+
+<br/>
+
+## GAUSS-00851 - GAUSS-00860
+
+<br/>
+
+GAUSS-00851: "cannot %s '%s' because it is in use"
+
+SQLSTATE: 55006
+
+Description: When an SQL statement is executed, the data partition to be queried is being accessed.
+
+Solution: Run this SQL statement after the data partition access is complete.
+
+GAUSS-00852: "there is no column for a partitioned table!"
+
+SQLSTATE: 42601
+
+Description: When the partition key sequence is obtained from a partitioned table, the column of the partitioned table is empty.
+
+Solution: Ensure that the partitioned table has no empty column.
+
+GAUSS-00853: "there is no partition key!"
+
+SQLSTATE: 42601
+
+Description: When the partition key sequence is obtained from a partitioned table, the value of all partition keys is null.
+
+Solution: Set the values of partition keys to valid ones.
+
+GAUSS-00854: "duplicate partition key: %s"
+
+SQLSTATE: 42701
+
+Description: When the partition key sequence is obtained from a partitioned table, the partitioned table contains duplicate partition keys.
+
+Solution: Modify the partitioned table.
+
+GAUSS-00857: "column %s cannot serve as an interval partitioning column because of its datatype"
+
+SQLSTATE: 42804
+
+Description: The data type of a column does not meet the requirements on interval partition columns.
+
+Solution: Modify the data type of the column to meet the requirements.
+
+GAUSS-00858: "column %s cannot serve as a range partitioning column because of its datatype"
+
+SQLSTATE: 42804
+
+Description: The data type of a column does not meet the data range requirements on the columns of partitioned tables.
+
+Solution: Modify the data type of the column to meet the requirements.
+
+GAUSS-00859: "partition bound list contains too few elements"
+
+SQLSTATE: 42601
+
+Description: When a partition value is modified to the array, the number of the elements contained in the partition bound list is less than that of target elements.
+
+Solution: Change the number of the target elements to that of the elements contained in the partition bound list.
+
+GAUSS-00860: "partition bound list contains too many elements"
+
+SQLSTATE: 42601
+
+Description: When a partition value is modified to the array, the number of the elements contained in the partition bound list is greater than that of target elements.
+
+Solution: Change the number of the target elements to that of the elements contained in the partition bound list.
+
+<br/>
+
+## GAUSS-00861 - GAUSS-00870
+
+<br/>
+
+GAUSS-00865: "invalid range partiiton table definition"
+
+SQLSTATE: 42601
+
+Description: When the **ComparePartitionValue** function is called, the definition of a partitioned table is invalid.
+
+Solution: Select a valid partitioned table.
+
+GAUSS-00866: "there is no partition key"
+
+SQLSTATE: 42601
+
+Description: When the **ComparePartitionValue** function is called, no partition value exists.
+
+Solution: Select a valid partitioned table.
+
+GAUSS-00868: "partition bound of partition '%s' is too low"
+
+SQLSTATE: 42601
+
+Description: When the **ComparePartitionValue** function is called, the partition bound of a partitioned table is excessively low.
+
+Solution: Check the table creation statement to ensure that the boundary values of the partition progressively increase.
+
+GAUSS-00869: "can not add partition against NON-PARTITIONED table"
+
+SQLSTATE: XX000
+
+Description: Partitions cannot be added to a non-partitioned table.
+
+Solution: Modify the table to a partitioned table, or cancel this operation.
+
+GAUSS-00870: "can not drop partition against NON-PARTITIONED table"
+
+SQLSTATE: XX000
+
+Description: Partitions cannot be deleted from a non-partitioned table.
+
+Solution: Cancel this operation.
+
+<br/>
+
+## GAUSS-00871 - GAUSS-00880
+
+<br/>
+
+GAUSS-00871: "can not set unusable index partition against NON-PARTITIONED index"
+
+SQLSTATE: XX000
+
+Description: Unusable index partitions are set for a non-partitioned table.
+
+Solution: Set index partitions for a partitioned table.
+
+GAUSS-00872: "can not set all index unusable on one partition against NON-PARTITIONED table"
+
+SQLSTATE: XX000
+
+Description: Unusable full index partitions are set for a non-partitioned table.
+
+Solution: Set full index partitions for a partitioned table.
+
+GAUSS-00873: "can not enable row movement against NON-PARTITIONED table"
+
+SQLSTATE: XX000
+
+Description: Row movements are not enabled for a non-partitioned table.
+
+Solution: Change the non-partitioned table to a partitioned table.
+
+GAUSS-00874: "can not disable row movement against NON-PARTITIONED table"
+
+SQLSTATE: XX000
+
+Description: Row movements cannot be canceled for a non-partitioned table.
+
+Solution: Change the non-partitioned table to a partitioned table.
+
+GAUSS-00875: "can not truncate partition against NON-PARTITIONED table"
+
+SQLSTATE: XX000
+
+Description: Partitions cannot be truncated for a non-partitioned table.
+
+Solution: Change the non-partitioned table to a partitioned table.
+
+GAUSS-00876: "can not exchange partition against NON-PARTITIONED table"
+
+SQLSTATE: XX000
+
+Description: Partitions cannot be modified for a non-partitioned table.
+
+Solution: Change the non-partitioned table to a partitioned table.
+
+GAUSS-00877: "can not merge partition against NON-PARTITIONED table"
+
+SQLSTATE: XX000
+
+Description: Partitioned cannot be merged for a non-partitioned table.
+
+Solution: Change the non-partitioned table to a partitioned table.
+
+GAUSS-00878: "can not split partition against NON-PARTITIONED table"
+
+SQLSTATE: XX000
+
+Description: Partitions cannot be split for a non-partitioned table.
+
+Solution: Change the non-partitioned table to a partitioned table.
+
+GAUSS-00880: "the current relation have already reached max number of partitions"
+
+SQLSTATE: XX000
+
+Description: The maximum number of partitions of a relational table has been reached.
+
+Solution: Add partitions to the relational table after reducing the number of its partitions.
+
+<br/>
+
+## GAUSS-00881 - GAUSS-00890
+
+<br/>
+
+GAUSS-00882: "upper boundary of adding partition MUST overtop last existing partition"
+
+SQLSTATE: XX000
+
+Description: In a relational table, the upper boundary value of a new partition is smaller than that of the last partition.
+
+Solution: Modify the upper boundary value of the new partition.
+
+GAUSS-00883: "could not acquire AccessExclusiveLock on dest table partition '%s', %s failed"
+
+SQLSTATE: XX000
+
+Description: The AccessExclusiveLock of the partition is not obtained.
+
+Solution: This problem may be caused by concurrency conflicts. Try again later.
+
+GAUSS-00884: "Cannot drop the only partition of a partitioned table"
+
+SQLSTATE: XX000
+
+Description: When the statement on deleting partitions is executed, the last partition cannot be deleted from a relational table.
+
+Solution: Cancel this operation.
+
+GAUSS-00886: "no local index defined on partition %u"
+
+SQLSTATE: XX000
+
+Description: No local index is found in a partition.
+
+Solution: Check whether the partition and index names to be queried exist. If they do not exist, cancel this operation.
+
+GAUSS-00887: "can not set unusable index for relation %s , as it is not a index"
+
+SQLSTATE: XX000
+
+Description: The index for setting a relational table is invalid.
+
+Solution: Use a valid index.
+
+GAUSS-00888: "could not find tuple for relation %u"
+
+SQLSTATE: XX000
+
+Description: When **ModifyRowMovement** is executed, the tuple of a relational table cannot be obtained.
+
+Solution: Check the tuple attribute of the relational table, or cancel this operation.
+
+GAUSS-00889: "cannot truncate a partition owned by partitioned table which is referenced in a foreign key constraint"
+
+SQLSTATE: XX000
+
+Description: The statement on truncating partitions is run for a partitioned table referenced in a foreign key constraint.
+
+Solution: Cancel the reference of the foreign key constraint, or cancel this operation.
+
+GAUSS-00890: "can not merge index partition %s bacause it is unusable local index"
+
+SQLSTATE: XX000
+
+Description: The statement on merging index partitions is run for an unusable local index.
+
+Solution: Ensure that the local index is usable, or cancel this operation.
+
+<br/>
+
+## GAUSS-00891 - GAUSS-00900
+
+<br/>
+
+GAUSS-00891: "source partitions must be at least two partitions"
+
+SQLSTATE: XX000
+
+Description: When **MergePartition** is run, the number of raw partitions is less than two.
+
+Solution: Do not merge partitions when the number of raw partitions is no less than 2.
+
+GAUSS-00892: "merge partitions of relation '%s', source partitions must be no more than %d partitions"
+
+SQLSTATE: XX000
+
+Description: The number of partitions to be merged exceeds the maximum.
+
+Solution: Reduce the partitions to be merged.
+
+GAUSS-00893: "merge partitions cannot process inusable index relation \"%s\""
+
+SQLSTATE: XX000
+
+Description: When **MergePartition** is run, the table contains an unusable local index.
+
+Solution: Ensure that the local index is usable before merging partitions.
+
+GAUSS-00895: "source partitions must be continuous and in ascending order of boundary"
+
+SQLSTATE: XX000
+
+Description: When **MergePartition** is run, raw partitions do not meet the requirements on continuity and boundary values listed in ascending order.
+
+Solution: Run this statement when raw partitions meet the requirements.
+
+GAUSS-00896: "target partition's name '%s' already exists"
+
+SQLSTATE: 42710
+
+Description: When **MergePartition** is run, the name of a target partition already exists.
+
+Solution: Ensure that the name of the target partition is unique.
+
+GAUSS-00898: "could not acquire AccessExclusiveLock on dest table partition '%s', MERGE PARTITIONS failed"
+
+SQLSTATE: XX000
+
+Description: Failed to obtain the exclusive lock of merged partitions.
+
+Solution: Do not perform other operations than merging partitions.
+
+GAUSS-00899: "Specified partition does not exist"
+
+SQLSTATE: 42P01
+
+Description: When **ExchangePartition** is run, the specified partition does not exist.
+
+Solution: Run this statement after confirming the name of the specified partition.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/description-of-sql-error-codes.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/description-of-sql-error-codes.md
new file mode 100644
index 0000000000000000000000000000000000000000..34947d0aee3786a29ff798aebf95cb63d02fba8b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/description-of-sql-error-codes.md
@@ -0,0 +1,398 @@
+---
+title: Description of SQL Error Codes
+summary: Description of SQL Error Codes
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# Description of SQL Error Codes
+
+<br/>
+
+As defined by the X/Open and SQL Access Group SQL CAE specification (1992), SQLERROR returns SQLSTATE values. A SQLSTATE value is a five-character string consisting of a two-character SQL error class and a three-character subclass. Five characters containing numeric or uppercase letters indicate the code for various errors or warning conditions. The successful status is identified by 00000. SQLSTATE codes are mostly defined in the SQL standard.
+
+MogDB also follows the SQL standard to return the SQLSTATE value of the error code, as detailed in [Table 1](#table).
+
+**Table 1** SQLSTATE values for MogDB error codes<a id="table"></a>
+
+| SQLSTATE Value                                               | Description                                                  |
+| :----------------------------------------------------------- | :----------------------------------------------------------- |
+| Class 00 - Successful completion                             |                                                              |
+| 00000                                                        | Successful completion (SUCCESSFUL_COMPLETION)                |
+| Class 01 - Warning                                           |                                                              |
+| 01000                                                        | Warning (WARNING)                                            |
+| 0100C                                                        | Dynamic result set returned (DYNAMIC_RESULT_SETS_RETURNED)   |
+| 01008                                                        | Implicit zero bit padding (IMPLICIT_ZERO_BIT_PADDING)        |
+| 01003                                                        | Null value eliminated in set function (NULL_VALUE_ELIMINATED_IN_SET_FUNCTION) |
+| 01007                                                        | Privilege not granted (PRIVILEGE_NOT_GRANTED)                |
+| 01006                                                        | Privilege not revoked (PRIVILEGE_NOT_REVOKED)                |
+| 01004                                                        | String data right truncation (STRING_DATA_RIGHT_TRUNCATION)  |
+| 01P01                                                        | Deprecated feature (DEPRECATED_FEATURE)                      |
+| Class 02 - No data (This is a warning class according to the SQL standard.) |                                                              |
+| 02000                                                        | No data (NO_DATA)                                            |
+| 02001                                                        | No additional dynamic result sets returned (NO_ADDITIONAL_DYNAMIC_RESULT_SETS_RETURNED) |
+| Class 03 - SQL statement not completed                       |                                                              |
+| 03000                                                        | SQL statement not completed (SQL_STATEMENT_NOT_YET_COMPLETE) |
+| Class 08 - Connection exception                              |                                                              |
+| 08000                                                        | Connection exception (CONNECTION_EXCEPTION)                  |
+| 08003                                                        | Connection does not exist (CONNECTION_DOES_NOT_EXIST)        |
+| 08006                                                        | Connection failure (CONNECTION_FAILURE)                      |
+| 08001                                                        | SQL connections cannot be established on the  SQL client (SQLCLIENT_UNABLE_TO_ESTABLISH_SQLCONNECTION) |
+| 08004                                                        | SQL server rejects establishment of SQL connections (SQLSERVER_REJECTED_ESTABLISHMENT_OF_SQLCONNECTION) |
+| 08007                                                        | Unknown transaction resolution (TRANSACTION_RESOLUTION_UNKNOWN) |
+| 08P01                                                        | Violation of the protocol (PROTOCOL_VIOLATION)               |
+| Class 09 - Triggering action exception                       |                                                              |
+| 09000                                                        | Triggering action exception (TRIGGERED_ACTION_EXCEPTION)     |
+| Class 0A - Feature not supported                             |                                                              |
+| 0A000                                                        | Feature not supported (FEATURE_NOT_SUPPORTED)                |
+| 0A100                                                        | Stream not supported (STREAM_NOT_SUPPORTED)                  |
+| Class 0B - Invalid transaction initiation                    |                                                              |
+| 0B000                                                        | Invalid transaction initiation (INVALID_TRANSACTION_INITIATION) |
+| Class 0F - Locator exception                                 |                                                              |
+| 0F000                                                        | Locator exception (LOCATOR_EXCEPTION)                        |
+| 0F001                                                        | Invalid locator specification (INVALID_LOCATOR_SPECIFICATION) |
+| Class 0L - Invalid grantor                                   |                                                              |
+| 0L000                                                        | Invalid grantor (INVALID_GRANTOR)                            |
+| 0LP01                                                        | Invalid grant operation (INVALID_GRANT_OPERATION)            |
+| Class 0P - Invalid role specification                        |                                                              |
+| 0P000                                                        | Invalid role specification (INVALID_ROLE_SPECIFICATION)      |
+| Class 0Z - Diagnostics exception                             |                                                              |
+| 0Z000                                                        | Diagnostics exception (DIAGNOSTICS_EXCEPTION)                |
+| 0Z002                                                        | Stacked diagnostics accessed without active handler (STACKED_DIAGNOSTICS_ACCESSED_WITHOUT_ACTIVE_HANDLER) |
+| Class 20 - Case not found                                    |                                                              |
+| 20000                                                        | Case not found (CASE_NOT_FOUND)                              |
+| Class 21 - Cardinality violation                             |                                                              |
+| 21000                                                        | Cardinality violation (CARDINALITY_VIOLATION)                |
+| Class 22 - Data exception                                    |                                                              |
+| 22000                                                        | Data exception (DATA_EXCEPTION)                              |
+| 2202E                                                        | Array subscript error (ARRAY_SUBSCRIPT_ERROR)                |
+| 22021                                                        | Character not in repertoire (CHARACTER_NOT_IN_REPERTOIRE)    |
+| 22008                                                        | Datetime field overflow (DATETIME_FIELD_OVERFLOW)            |
+| 22012                                                        | Division by zero (DIVISION_BY_ZERO)                          |
+| 22005                                                        | Error in assignment (ERROR_IN_ASSIGNMENT)                    |
+| 2200B                                                        | Escape character conflict (ESCAPE_CHARACTER_CONFLICT)        |
+| 22022                                                        | Indicator overflow (INDICATOR_OVERFLOW)                      |
+| 22015                                                        | Interval field overflow (INTERVAL_FIELD_OVERFLOW)            |
+| 2201E                                                        | Invalid argument for logarithm (INVALID_ARGUMENT_FOR_LOGARITHM) |
+| 22014                                                        | Invalid argument for NTILE function (INVALID_ARGUMENT_FOR_NTILE_FUNCTION) |
+| 22016                                                        | Invalid argument for N value function (INVALID_ARGUMENT_FOR_NTH_VALUE_FUNCTION) |
+| 2201F                                                        | Invalid argument for power function (INVALID_ARGUMENT_FOR_POWER_FUNCTION) |
+| 2201G                                                        | Invalid argument for width bucket function (INVALID_ARGUMENT_FOR_WIDTH_BUCKET_FUNCTION) |
+| 22018                                                        | Invalid character value for CAST (INVALID_CHARACTER_VALUE_FOR_CAST) |
+| 22007                                                        | Invalid datetime format (INVALID_DATETIME_FORMAT)            |
+| 22019                                                        | Invalid escape character (INVALID_ESCAPE_CHARACTER)          |
+| 2200D                                                        | Invalid escape octet (INVALID_ESCAPE_OCTET)                  |
+| 22025                                                        | Invalid escape sequence (INVALID_ESCAPE_SEQUENCE)            |
+| 22P06                                                        | Nonstandard use of escape character (NONSTANDARD_USE_OF_ESCAPE_CHARACTER) |
+| 22010                                                        | Invalid indicator parameter value (INVALID_INDICATOR_PARAMETER_VALUE) |
+| 22023                                                        | Invalid parameter value (INVALID_PARAMETER_VALUE)            |
+| 2201B                                                        | Invalid regular expression (INVALID_REGULAR_EXPRESSION)      |
+| 2201W                                                        | Invalid row count in LIMIT clause (INVALID_ROW_COUNT_IN_LIMIT_CLAUSE) |
+| 2201X                                                        | Invalid row count in result set clause (INVALID_ROW_COUNT_IN_RESULT_OFFSET_CLAUSE) |
+| 2202H                                                        | Invalid sample parameter (INVALID_TABLESAMPLE_ARGUMENT)      |
+| 2202G                                                        | Invalid sample repeat (INVALID_TABLESAMPLE_REPEAT)           |
+| 22009                                                        | Invalid time zone displacement value (INVALID_TIME_ZONE_DISPLACEMENT_VALUE) |
+| 2200C                                                        | Invalid use of escape character (INVALID_USE_OF_ESCAPE_CHARACTER) |
+| 2200G                                                        | Most specific type mismatch (MOST_SPECIFIC_TYPE_MISMATCH)    |
+| 22004                                                        | Null value not allowed (NULL_VALUE_NOT_ALLOWED)              |
+| 22002                                                        | Null value cannot be used as the indicator parameter(NULL_VALUE_NO_INDICATOR_PARAMETER) |
+| 22003                                                        | Numeric value out of range (NUMERIC_VALUE_OUT_OF_RANGE)      |
+| 22017                                                        | DOP value out of range (DOP_VALUE_OUT_OF_RANGE)              |
+| 22026                                                        | String data length mismatch (STRING_DATA_LENGTH_MISMATCH)    |
+| 22028                                                        | Regular expression mismatch (REGEXP_MISMATCH)                |
+| 22001                                                        | String data right truncation (STRING_DATA_RIGHT_TRUNCATION)  |
+| 22011                                                        | Substring error (SUBSTRING_ERROR)                            |
+| 22027                                                        | Trim error (TRIM_ERROR)                                      |
+| 22024                                                        | Unterminated C string (UNTERMINATED_C_STRING)                |
+| 2200F                                                        | Zero-length character string (ZERO_LENGTH_CHARACTER_STRING)  |
+| 22P01                                                        | Floating point exception (FLOATING_POINT_EXCEPTION)          |
+| 22P02                                                        | Invalid text representation (INVALID_TEXT_REPRESENTATION)    |
+| 22P03                                                        | Invalid binary representation (INVALID_BINARY_REPRESENTATION) |
+| 22P04                                                        | Incorrect copy file format (BAD_COPY_FILE_FORMAT)            |
+| 22P05                                                        | Untranslatable character (UNTRANSLATABLE_CHARACTER)          |
+| 22P06                                                        | Memory query failure (CACHE_LOOKUP_FAILED)                   |
+| 22P07                                                        | Failed to read the file (FILE_READ_FAILED)                   |
+| 22P08                                                        | Failed to obtain data (FETCH_DATA_FAILED)                    |
+| 2200L                                                        | Not XML file (NOT_AN_XML_DOCUMENT)                           |
+| 2200M                                                        | Invalid XML file (INVALID_XML_DOCUMENT)                      |
+| 2200N                                                        | Invalid XML content (INVALID_XML_CONTENT)                    |
+| 2200O                                                        | Invalid XML error information (INVALID_XML_ERROR_CONTEXT)    |
+| 2200S                                                        | Invalid XML comment (INVALID_XML_COMMENT)                    |
+| 2200T                                                        | Invalid XML processing instruction (INVALID_XML_PROCESSING_INSTRUCTION) |
+| 2200X                                                        | RELATION close error (RELATION_CLOSE_ERROR)                  |
+| Class 23 - Integrity constraint violation                    |                                                              |
+| 23000                                                        | Integrity constraint violation (INTEGRITY_CONSTRAINT_VIOLATION) |
+| 23001                                                        | Restrict violation (RESTRICT_VIOLATION)                      |
+| 23502                                                        | Not null violation (NOT_NULL_VIOLATION)                      |
+| 23503                                                        | Foreign key violation (FOREIGN_KEY_VIOLATION)                |
+| 23505                                                        | Uniqueness violation (UNIQUE_VIOLATION)                      |
+| 23514                                                        | CHECK violation (CHECK_VIOLATION)                            |
+| 23P01                                                        | Exclusion violation (EXCLUSION_VIOLATION)                    |
+| Class 24 - Invalid cursor state                              |                                                              |
+| 24000                                                        | Invalid cursor state (INVALID_CURSOR_STATE)                  |
+| Class 25 - Invalid transaction state                         |                                                              |
+| 25000                                                        | Invalid transaction state (INVALID_TRANSACTION_STATE)        |
+| 25001                                                        | Active SQL transaction (ACTIVE_SQL_TRANSACTION)              |
+| 25002                                                        | Branch transaction already activated (BRANCH_TRANSACTION_ALREADY_ACTIVE) |
+| 25008                                                        | Held cursor requires the same isolation level (HELD_CURSOR_REQUIRES_SAME_ISOLATION_LEVEL) |
+| 25003                                                        | Inappropriate access mode for branch transaction (INAPPROPRIATE_ACCESS_MODE_FOR_BRANCH_TRANSACTION) |
+| 25004                                                        | Inappropriate isolation level for branch transaction (INAPPROPRIATE_ISOLATION_LEVEL_FOR_BRANCH_TRANSACTION) |
+| 25005                                                        | No active SQL transaction for branch transaction (NO_ACTIVE_SQL_TRANSACTION_FOR_BRANCH_TRANSACTION) |
+| 25006                                                        | Read-only SQL transaction (READ_ONLY_SQL_TRANSACTION)        |
+| 25007                                                        | Schema and data statement mixing not supported (SCHEMA_AND_DATA_STATEMENT_MIXING_NOT_SUPPORTED) |
+| 25009                                                        | Transaction cannot be started during recovery (RUN_TRANSACTION_DURING_RECOVERY) |
+| 25010                                                        | Transaction ID does not exist (GXID_DOES_NOT_EXIST)          |
+| 25P01                                                        | No active SQL transaction (NO_ACTIVE_SQL_TRANSACTION)        |
+| 25P02                                                        | In failed SQL transaction (IN_FAILED_SQL_TRANSACTION)        |
+| Class 26 - Invalid SQL statement name                        |                                                              |
+| 26000                                                        | Invalid SQL statement name (INVALID_SQL_STATEMENT_NAME)      |
+| Class 27 - Triggered data change violation                   |                                                              |
+| 27000                                                        | Triggered data change violation (TRIGGERED_DATA_CHANGE_VIOLATION) |
+| 27001                                                        | Invalid triggered tuple (TRIGGERED_INVALID_TUPLE)            |
+| Class 28 - Invalid authorization specification               |                                                              |
+| 28000                                                        | Invalid authorization specification (INVALID_AUTHORIZATION_SPECIFICATION) |
+| 28P01                                                        | Invalid password (INVALID_PASSWORD)                          |
+| 28P02                                                        | Initial password not changed (INITIAL_PASSWORD_NOT_MODIFIED) |
+| Class 29 - Invalid or unexpected state                       |                                                              |
+| 29P06                                                        | Invalid cache plan (INVALID_CACHE_PLAN)                      |
+| Class 2B - The dependent privilege descriptor still exists   |                                                              |
+| 2B000                                                        | The dependent privilege descriptor still exists (DEPENDENT_PRIVILEGE_DESCRIPTORS_STILL_EXIST) |
+| 2BP01                                                        | The dependent object still exists (DEPENDENT_OBJECTS_STILL_EXIST) |
+| Class 2D - Invalid transaction termination                   |                                                              |
+| 2D000                                                        | Invalid transaction termination (INVALID_TRANSACTION_TERMINATION) |
+| Class 2F - SQL process exception                             |                                                              |
+| 2F000                                                        | SQL process exception (SQL_ROUTINE_EXCEPTION)                |
+| 2F005                                                        | No return statement during function execution (FUNCTION_EXECUTED_NO_RETURN_STATEMENT) |
+| 2F002                                                        | Modifying SQL data not permitted (MODIFYING_SQL_DATA_NOT_PERMITTED) |
+| 2F003                                                        | Prohibited SQL statement attempted (PROHIBITED_SQL_STATEMENT_ATTEMPTED) |
+| 2F004                                                        | Reading SQL data not permitted (READING_SQL_DATA_NOT_PERMITTED) |
+| Class 34 - Invalid cursor name                               |                                                              |
+| 34000                                                        | Invalid cursor name (INVALID_CURSOR_NAME)                    |
+| Class 38 - External process exception                        |                                                              |
+| 38000                                                        | External process exception (EXTERNAL_ROUTINE_EXCEPTION)      |
+| 38001                                                        | Containing SQL not permitted (CONTAINING_SQL_NOT_PERMITTED)  |
+| 38002                                                        | Modifying SQL data not permitted (MODIFYING_SQL_DATA_NOT_PERMITTED) |
+| 38003                                                        | Prohibited SQL statement attempted (PROHIBITED_SQL_STATEMENT_ATTEMPTED) |
+| 38004                                                        | SQL data read not permitted (READING_SQL_DATA_NOT_PERMITTED) |
+| Class 39 - External process invocation exception             |                                                              |
+| 39000                                                        | External process invocation exception (EXTERNAL_ROUTINE_INVOCATION_EXCEPTION) |
+| 39001                                                        | Invalid SQLSTATE value returned (INVALID_SQLSTATE_RETURNED)  |
+| 39004                                                        | Null value not allowed (NULL_VALUE_NOT_ALLOWED)              |
+| 39P01                                                        | Trigger protocol violated (TRIGGER_PROTOCOL_VIOLATED)        |
+| 39P02                                                        | SRF protocol violated (SRF_PROTOCOL_VIOLATED)                |
+| Class 3B - Savepoint exception                               |                                                              |
+| 3B000                                                        | Savepoint exception (SAVEPOINT_EXCEPTION)                    |
+| 3B001                                                        | Invalid savepoint specification (INVALID_SAVEPOINT_SPECIFICATION) |
+| Class 3D - Invalid database name                             |                                                              |
+| 3D000                                                        | Invalid database name (INVALID_CATALOG_NAME)                 |
+| Class 3F - Invalid schema name                               |                                                              |
+| 3F000                                                        | Invalid schema name (INVALID_SCHEMA_NAME)                    |
+| 3F001                                                        | Undefined mode (UNDEFINED_SCHEMA)                            |
+| Class 40 - Transaction rollback                              |                                                              |
+| 40000                                                        | Transaction rollback (TRANSACTION_ROLLBACK)                  |
+| 40002                                                        | Transaction integrity constraint violation (TRANSACTION_INTEGRITY_CONSTRAINT_VIOLATION) |
+| 40001                                                        | Serialization failure (SERIALIZATION_FAILURE)                |
+| 40003                                                        | Statement completion unknown (STATEMENT_COMPLETION_UNKNOWN)  |
+| 40P01                                                        | Deadlock detected (DEADLOCK_DETECTED)                        |
+| Class 42 - Syntax error or access rule violation             |                                                              |
+| 42000                                                        | Syntax error or access rule violation (SYNTAX_ERROR_OR_ACCESS_RULE_VIOLATION) |
+| 42601                                                        | syntax error (SYNTAX_ERROR)                                  |
+| 42501                                                        | Insufficient privilege (INSUFFICIENT_PRIVILEGE)              |
+| 42846                                                        | Type conversion cannot be performed 无法进行类型转换(CANNOT_COERCE) |
+| 42803                                                        | Grouping error (GROUPING_ERROR)                              |
+| 42P20                                                        | Windowing error (WINDOWING_ERROR)                            |
+| 42P19                                                        | Invalid recursion (INVALID_RECURSION)                        |
+| 42830                                                        | Invalid foreign key (INVALID_FOREIGN_KEY)                    |
+| 42602                                                        | Invalid name (INVALID_NAME)                                  |
+| 42622                                                        | Too long name (NAME_TOO_LONG)                                |
+| 42939                                                        | Reserved name (RESERVED_NAME)                                |
+| 42804                                                        | Data type mismatch (DATATYPE_MISMATCH)                       |
+| 42P18                                                        | Indeterminate data type (INDETERMINATE_DATATYPE)             |
+| 42P21                                                        | Collation mismatch (COLLATION_MISMATCH)                      |
+| 42P22                                                        | Indeterminate collation (INDETERMINATE_COLLATION)            |
+| 42P23                                                        | Partition error (PARTITION_ERROR)                            |
+| 42P24                                                        | Invalid attribute value (INVALID_ATTRIBUTE)                  |
+| 42P25                                                        | Invalid aggregation function (INVALID_AGG)                   |
+| 42P26                                                        | Resource pool error (RESOURCE_POOL_ERROR)                    |
+| 42P27                                                        | Parent plan not found (PLAN_PARENT_NOT_FOUND)                |
+| 42P28                                                        | Update conflict (MODIFY_CONFLICTS)                           |
+| 42P29                                                        | Distribution error (DISTRIBUTION_ERROR)                      |
+| 42809                                                        | Incorrect object type (WRONG_OBJECT_TYPE)                    |
+| 42703                                                        | Undefined column (UNDEFINED_COLUMN)                          |
+| 42883                                                        | Undefined function (UNDEFINED_FUNCTION)                      |
+| 42P01                                                        | Undefined table (UNDEFINED_TABLE)                            |
+| 42P02                                                        | Undefined parameter (UNDEFINED_PARAMETER)                    |
+| 42704                                                        | Undefined object (UNDEFINED_OBJECT)                          |
+| 42701                                                        | Duplicate column (DUPLICATE_COLUMN)                          |
+| 42P03                                                        | Duplicate cursor (DUPLICATE_CURSOR)                          |
+| 42P04                                                        | Duplicate database (DUPLICATE_DATABASE)                      |
+| 42723                                                        | Duplicate function (DUPLICATE_FUNCTION)                      |
+| 42P05                                                        | Duplicate prepared statement (DUPLICATE_PREPARED_STATEMENT)  |
+| 42P06                                                        | Duplicate schema (DUPLICATE_SCHEMA)                          |
+| 42P07                                                        | Duplicate table (DUPLICATE_TABLE)                            |
+| 42712                                                        | Duplicate alias (DUPLICATE_ALIAS)                            |
+| 42710                                                        | Duplicate object (DUPLICATE_OBJECT)                          |
+| 42702                                                        | Ambiguous column (AMBIGUOUS_COLUMN)                          |
+| 42725                                                        | Ambiguous function (AMBIGUOUS_FUNCTION)                      |
+| 42P08                                                        | Ambiguous parameter (AMBIGUOUS_PARAMETER)                    |
+| 42P09                                                        | Ambiguous alias (AMBIGUOUS_ALIAS)                            |
+| 42P10                                                        | Invalid column reference (INVALID_COLUMN_REFERENCE)          |
+| 42611                                                        | Invalid column definition (INVALID_COLUMN_DEFINITION)        |
+| 42P11                                                        | Invalid cursor definition (INVALID_CURSOR_DEFINITION)        |
+| 42P12                                                        | Invalid database definition (INVALID_DATABASE_DEFINITION)    |
+| 42P13                                                        | Invalid function definition (INVALID_FUNCTION_DEFINITION)    |
+| 42P14                                                        | Invalid prepared statement definition (INVALID_PREPARED_STATEMENT_DEFINITION) |
+| 42P15                                                        | Invalid schema definition (INVALID_SCHEMA_DEFINITION)        |
+| 42P16                                                        | Invalid table definition (INVALID_TABLE_DEFINITION)          |
+| 42P17                                                        | Invalid object definition (INVALID_OBJECT_DEFINITION)        |
+| Class 44 - WITH CHECK option violation                       |                                                              |
+| 44000                                                        | WITH CHECK option violation (WITH_CHECK_OPTION_VIOLATION)    |
+| Class 53 - Insufficient resources                            |                                                              |
+| 53000                                                        | Insufficient resources (INSUFFICIENT_RESOURCES)              |
+| 53100                                                        | The disk space is fully occupied (DISK_FULL)                 |
+| 53200                                                        | Out of memory (OUT_OF_MEMORY)                                |
+| 53300                                                        | Too many connections (TOO_MANY_CONNECTIONS)                  |
+| 53400                                                        | Configuration limit exceeded (CONFIGURATION_LIMIT_EXCEEDED)  |
+| Class 54 - Program limit exceeded                            |                                                              |
+| 54000                                                        | Program limit exceeded (PROGRAM_LIMIT_EXCEEDED)              |
+| 54001                                                        | Too complex statement (STATEMENT_TOO_COMPLEX)                |
+| 54011                                                        | Too many columns (TOO_MANY_COLUMNS)                          |
+| 54023                                                        | Too many parameters (TOO_MANY_ARGUMENTS)                     |
+| Class 55 - The object is not in the prerequisite state       |                                                              |
+| 55000                                                        | The object is not in the prerequisite state (OBJECT_NOT_IN_PREREQUISITE_STATE) |
+| 55006                                                        | The object is in use (OBJECT_IN_USE)                         |
+| 55P02                                                        | Runtime parameter cannot be modified (CANT_CHANGE_RUNTIME_PARAM) |
+| 55P03                                                        | Lock unavailable (LOCK_NOT_AVAILABLE)                        |
+| Class 57 - Operator intervention                             |                                                              |
+| 57000                                                        | Operator intervention (OPERATOR_INTERVENTION)                |
+| 57014                                                        | Query canceled (QUERY_CANCELED)                              |
+| 57015                                                        | Internal query canceled (QUERY_INTERNAL_CANCEL)              |
+| 57P01                                                        | System closed by the admin (ADMIN_SHUTDOWN)                  |
+| 57P02                                                        | Crash shutdown (CRASH_SHUTDOWN)                              |
+| 57P03                                                        | Connection not allowed (CANNOT_CONNECT_NOW)                  |
+| 57P04                                                        | Dropped database (DATABASE_DROPPED)                          |
+| Class 58 - System error (MogDB internal error)               |                                                              |
+| 58000                                                        | System error (SYSTEM_ERROR)                                  |
+| 58030                                                        | IO error (IO_ERROR)                                          |
+| 58P01                                                        | Undefined file (UNDEFINED_FILE)                              |
+| 58P02                                                        | Duplicate file (DUPLICATE_FILE)                              |
+| Class F0 - Configuration file error                          |                                                              |
+| F0000                                                        | Configuration file error (CONFIG_FILE_ERROR)                 |
+| F0001                                                        | Lock file exists (LOCK_FILE_EXISTS)                          |
+| Class HV - External data error (SQL/MED)                     |                                                              |
+| HV000                                                        | External data error (FDW_ERROR)                              |
+| HV005                                                        | No name found (FDW_COLUMN_NAME_NOT_FOUND)                    |
+| HV002                                                        | Dynamic parameter value required (FDW_DYNAMIC_PARAMETER_VALUE_NEEDED) |
+| HV010                                                        | Function sequence error (FDW_FUNCTION_SEQUENCE_ERROR)        |
+| HV021                                                        | Inconsistent description information (FDW_INCONSISTENT_DESCRIPTOR_INFORMATION) |
+| HV024                                                        | Invalid attribute value (FDW_INVALID_ATTRIBUTE_VALUE)        |
+| HV007                                                        | Invalid column name (FDW_INVALID_COLUMN_NAME)                |
+| HV008                                                        | Invalid column number (FDW_INVALID_COLUMN_NUMBER)            |
+| HV004                                                        | Invalid data type (FDW_INVALID_DATA_TYPE)                    |
+| HV006                                                        | Invalid data type descriptor (FDW_INVALID_DATA_TYPE_DESCRIPTORS) |
+| HV091                                                        | Invalid filed identifier (FDW_INVALID_DESCRIPTOR_FIELD_IDENTIFIER) |
+| HV00B                                                        | Invalid handling (FDW_INVALID_HANDLE)                        |
+| HV00C                                                        | Invalid index option (FDW_INVALID_OPTION_INDEX)              |
+| HV00D                                                        | Invalid option name (FDW_INVALID_OPTION_NAME)                |
+| HV090                                                        | Invalid string length or buffer length (FDW_INVALID_STRING_LENGTH_OR_BUFFER_LENGTH) |
+| HV00A                                                        | Invalid string format (FDW_INVALID_STRING_FORMAT)            |
+| HV009                                                        | Invalid use of null pointer (FDW_INVALID_USE_OF_NULL_POINTER) |
+| HV014                                                        | Too many handles (FDW_TOO_MANY_HANDLES)                      |
+| HV001                                                        | Out of memory (FDW_OUT_OF_MEMORY)                            |
+| HV00P                                                        | No schema (FDW_NO_SCHEMAS)                                   |
+| HV00J                                                        | No option name found (FDW_OPTION_NAME_NOT_FOUND)             |
+| HV00K                                                        | Reply handle (FDW_REPLY_HANDLE)                              |
+| HV00Q                                                        | No schema found (FDW_SCHEMA_NOT_FOUND)                       |
+| HV00R                                                        | No table found (FDW_TABLE_NOT_FOUND)                         |
+| HV00S                                                        | Incorrect server type (FDW_INVALID_SERVER_TYPE)              |
+| HV00L                                                        | Unable to establish execution (FDW_UNABLE_TO_CREATE_EXECUTION) |
+| HV00M                                                        | Unable to create reply (FDW_UNABLE_TO_CREATE_REPLY)          |
+| HV00N                                                        | Unable to establish connection (FDW_UNABLE_TO_ESTABLISH_CONNECTION) |
+| Class P0 - PL/pgSQL error                                    |                                                              |
+| P0000                                                        | PLPGSQL error (PLPGSQL_ERROR)                                |
+| P0001                                                        | Raise exception (RAISE_EXCEPTION)                            |
+| P0002                                                        | No data found (NO_DATA_FOUND)                                |
+| P0003                                                        | Too many rows (TOO_MANY_ROWS)                                |
+| P0004                                                        | FORALL requires DML operation (FORALL_NEED_DML)              |
+| Class XX - Interval error                                    |                                                              |
+| XX000                                                        | Interval error (INTERNAL_ERROR)                              |
+| XX001                                                        | Data corrupted (DATA_CORRUPTED)                              |
+| XX002                                                        | Index corrupted (INDEX_CORRUPTED)                            |
+| XX003                                                        | Remote stream socket closed (STREAM_REMOTE_CLOSE_SOCKET)     |
+| XX004                                                        | Unrecognized node type (UNRECOGNIZED_NODE_TYPE)              |
+| XX005                                                        | Unexpected null value (UNEXPECTED_NULL_VALUE)                |
+| XX006                                                        | Unexpected node state (UNEXPECTED_NODE_STATE)                |
+| XX007                                                        | Null JUNK attribute (NULL_JUNK_ATTRIBUTE)                    |
+| XX008                                                        | Inconsistent optimizer state (OPTIMIZER_INCONSISTENT_STATE)  |
+| XX009                                                        | Duplicate query ID (STREAM_DUPLICATE_QUERY_ID)               |
+| XX010                                                        | Invalid buffer (INVALID_BUFFER)                              |
+| XX011                                                        | Invalid buffer reference (INVALID_BUFFER_REFERENCE)          |
+| XX012                                                        | Node ID mismatch (NODE_ID_MISSMATCH)                         |
+| XX013                                                        | XID base cannot be modified (CANNOT_MODIFY_XIDBASE)          |
+| XX014                                                        | Unexpected TOAST table data damage (UNEXPECTED_CHUNK_VALUE)  |
+| Class YY - SQL retry error                                   |                                                              |
+| YY001                                                        | Connection reset by peer (CONNECTION_RESET_BY_PEER)          |
+| YY002                                                        | Stream connection reset by peer (STREAM_CONNECTION_RESET_BY_PEER) |
+| YY003                                                        | Lock wait timeout (LOCK_WAIT_TIMEOUT)                        |
+| YY004                                                        | Connection timed out (CONNECTION_TIMED_OUT)                  |
+| YY005                                                        | Set query error (SET_QUERY_ERROR)                            |
+| YY006                                                        | Out of logical memory (OUT_OF_LOGICAL_MEMORY)                |
+| YY007                                                        | SCTP memory allocated (SCTP_MEMORY_ALLOC)                    |
+| YY008                                                        | SCTP no data in buffer (SCTP_NO_DATA_IN_BUFFER)              |
+| YY009                                                        | SCTP release memory close (SCTP_RELEASE_MEMORY_CLOSE)        |
+| YY010                                                        | SCTP and TCP disconnected (SCTP_TCP_DISCONNECT)              |
+| YY011                                                        | SCTP disconnected (SCTP_DISCONNECT)                          |
+| YY012                                                        | SCTP remote close (SCTP_REMOTE_CLOSE)                        |
+| YY013                                                        | SCTP wait poll unknown (SCTP_WAIT_POLL_UNKNOW)               |
+| YY014                                                        | Invalid snapshot (SNAPSHOT_INVALID)                          |
+| YY015                                                        | Connection receive error (CONNECTION_RECEIVE_WRONG)          |
+| Class SI - SPI interface error                               |                                                              |
+| SP000                                                        | SPI interface error (SPI_ERROR)                              |
+| SP001                                                        | SPI connection failure (SPI_CONNECTION_FAILURE)              |
+| SP002                                                        | SPI finish failure (SPI_FINISH_FAILURE)                      |
+| SP003                                                        | SPI preparation failure (SPI_PREPARE_FAILURE)                |
+| SP004                                                        | SPI cursor open failure (SPI_CURSOR_OPEN_FAILURE)            |
+| SP005                                                        | SPI execution failure (SPI_EXECUTE_FAILURE)                  |
+| SP006                                                        | Improper call of SPI (SPI_IMPROPER_CALL_FUNCTION)            |
+| RB class - RBTree error                                      |                                                              |
+| RB001                                                        | RBTree invalid node state (RBTREE_INVALID_NODE_STATE)        |
+| RB002                                                        | RBTree invalid iterator order (RBTREE_INVALID_ITERATOR_ORDER) |
+| Class PD - PL debug server internal error                    |                                                              |
+| D0000                                                        | PL debug server internal error (PLDEBUGGER_INTERNAL_ERROR)   |
+| D0001                                                        | Duplicate breakpoint (DUPLICATE_BREAKPOINT)                  |
+| D0002                                                        | Hash function is not initialized (FUNCTION_HASH_IS_NOT_INITIALIZED) |
+| D0003                                                        | Breakpoint is not present (BREAKPOINT_IS_NOT_PRESENT)        |
+| D0004                                                        | Debug server already attached (DEBUG_SERVER_ALREADY_IS_ATTACHED) |
+| D0005                                                        | Debug server not attached (DEBUG_SERVER_NOT_ATTACHED)        |
+| D0006                                                        | Debug server already in synchronization (DEBUG_SERVER_ALREADY_IN_SYNC) |
+| D0007                                                        | Debug target server not in synchronization (DEBUG_TARGET_SERVERS_NOT_IN_SYNC) |
+| D0008                                                        | Target server already in synchronization (TARGET_SERVER_ALREADY_IN_SYNC) |
+| D0009                                                        | The variable does not exist (NON_EXISTANT_VARIABLE)          |
+| D0010                                                        | Invalid target session ID (INVALID_TARGET_SESSION_ID)        |
+| D0011                                                        | Invalid operation (INVALID_OPERATION)                        |
+| D0012                                                        | Maximum number of debug sessions reached (MAXIMUM_NUMBER_OF_DEBUG_SESSIONS_REACHED) |
+| D0013                                                        | Maximum number of breakpoints reached (MAXIMUM_NUMBER_OF_BREAKPOINTS_REACHED) |
+| LL - Logical decoding error                                  |                                                              |
+| LL001                                                        | Logical decoding error (LOGICAL_DECODE_ERROR)                |
+| LL002                                                        | Hash table query error (RELFILENODEMAP)                      |
+
+**Table 2** SQLSTATE values for MogDB CM error codes
+
+| Class c0 - Connection exception  |                                                             |
+| :------------------------------- | :---------------------------------------------------------- |
+| c0000                            | Connection exception (connection_exception)                 |
+| c0001                            | Connection does not exist (connection_does_not_exist)       |
+| c0002                            | Connection failure (connection_failure)                     |
+| Class c1 - Environment exception |                                                             |
+| c1000                            | Out of memory (out_of_memory)                               |
+| Class c2 - File exception        |                                                             |
+| c2000                            | File failed to be opened (open_file_failure)                |
+| c2001                            | File failed to be read (read_file_failure)                  |
+| c2002                            | Configuration file failure (config_file_failure)            |
+| Class c3 - Parameter exception   |                                                             |
+| c3000                            | Parameter failure (parameter_failure)                       |
+| c3001                            | Environment variable failure (environment_variable_failure) |
+| Class c4 - Etcd exception        |                                                             |
+| c4000                            | Etcd failed to be opened (etcd_open_failure)                |
+| Class c5 - Internal exception    |                                                             |
+| c5000                            | Internal error (internal_error)                             |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/third-party-library-error-codes.md b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/third-party-library-error-codes.md
new file mode 100644
index 0000000000000000000000000000000000000000..a429f6d23328ef1542f23a54f8058a78b5912812
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-code-reference/third-party-library-error-codes.md
@@ -0,0 +1,31 @@
+---
+title: Third-Party Library Error Codes
+summary: Third-Party Library Error Codes
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# Third-Party Library Error Codes
+
+<br/>
+
+A third-party error code contains five characters, the first three indicating the error type and the last two indicating the subclass. The five characters can be digits or uppercase letters, which represent various errors or warnings.
+
+**Table 1** liborc error codes
+
+| Error Level | Error Code | Description                                                  |
+| :---------- | :--------- | :----------------------------------------------------------- |
+| ORC_INFO    | ORC00      | Invalid content (INVALID_ERROR_CODE)                         |
+| ORC_ERROR   | ORC01      | Function that is not supported or cannot be implemented (NOTIMPLEMENTEDYET) |
+| ORC_ERROR   | ORC02      | Compilation error (PARSEERROR)                               |
+| ORC_ERROR   | ORC03      | Logic error (LOGICERROR)                                     |
+| ORC_ERROR   | ORC04      | Range error (RANGEERROR)                                     |
+| ORC_ERROR   | ORC05      | Write error (WRITEERROR)                                     |
+| ORC_FATAL   | ORC06      | Interruption (ASSERTERROR)                                   |
+| ORC_ERROR   | ORC07      | Memory error (MEMORYERROR)                                   |
+| ORC_ERROR   | ORC08      | Other errors (OTHERERROR)                                    |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> 1. Errors of ORC_ERROR and higher levels are printed using **psql**, and their detailed stack information is recorded in the corresponding CN and DN logs. Lower-level logs are only printed in the corresponding CN and DN logs.
+> 2. You can locate and rectify the fault based on the error code and information.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/error-log-reference/kernel-error-message.md b/product/en/docs-mogdb/v3.0/reference-guide/error-log-reference/kernel-error-message.md
new file mode 100644
index 0000000000000000000000000000000000000000..51ce0e6e7c41528b6b306c3f8557f702fa687418
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/error-log-reference/kernel-error-message.md
@@ -0,0 +1,1328 @@
+---
+title: Kernel Error Message
+summary: Kernel Error Message
+author: Zhang Cuiping
+date: 2021-11-08
+---
+
+# Kernel Error Message
+
+ERRMSG: "unsupported syntax: ENCRYPTED WITH in this operation"
+
+SQLSTATE: 42601
+
+CAUSE: "client encryption feature is not supported this operation."
+
+ACTION: "Check client encryption feature whether supported this operation."
+
+ERRMSG: "invalid grant operation"
+
+SQLSTATE: 0LP01
+
+CAUSE: "Grant options cannnot be granted to public."
+
+ACTION: "Grant grant options to roles."
+
+ERRMSG: "unrecognized object kind: %d"
+
+SQLSTATE: XX004
+
+CAUSE: "The object type is not supported for GRANT/REVOKE."
+
+ACTION: "Check GRANT/REVOKE syntax to obtain the supported object types."
+
+ERRMSG: "unrecognized GrantStmt.targtype: %d"
+
+SQLSTATE: XX004
+
+CAUSE: "The target type is not supported for GRANT/REVOKE."
+
+ACTION: "Check GRANT/REVOKE syntax to obtain the supported target types."
+
+ERRMSG: "invalid grant operation"
+
+SQLSTATE: 0LP01
+
+CAUSE: "Grant to public operation is forbidden in security mode."
+
+ACTION: "Don't grant to public in security mode."
+
+ERRMSG: "unrecognized object type"
+
+SQLSTATE: XX004
+
+CAUSE: "The object type is not supported for GRANT/REVOKE."
+
+ACTION: "Check GRANT/REVOKE syntax to obtain the supported object types."
+
+ERRMSG: "invalid grant/revoke operation"
+
+SQLSTATE: 0LP01
+
+CAUSE: "Column privileges are only valid for relations in GRANT/REVOKE."
+
+ACTION: "Use the column privileges only for relations."
+
+ERRMSG: "invalid AccessPriv node"
+
+SQLSTATE: 0LP01
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "unrecognized GrantStmt.objtype: %d"
+
+SQLSTATE: XX004
+
+CAUSE: "The object type is not supported for GRANT/REVOKE."
+
+ACTION: "Check GRANT/REVOKE syntax to obtain the supported object types."
+
+ERRMSG: "undefined client master key"
+
+SQLSTATE: 42705
+
+CAUSE: "The client master key does not exist."
+
+ACTION: "Check whether the client master key exists."
+
+ERRMSG: "undefined column encryption key"
+
+SQLSTATE: 42705
+
+CAUSE: "The column encryption key does not exist."
+
+ACTION: "Check whether the column encryption key exists."
+
+ERRMSG: "large object %u does not exist"
+
+SQLSTATE: 42704
+
+CAUSE: "The large object does not exist."
+
+ACTION: "Check whether the large object exists."
+
+ERRMSG: "redundant options"
+
+SQLSTATE: 42601
+
+CAUSE: "The syntax 'schemas' is redundant in ALTER DEFAULT PRIVILEGES statement."
+
+ACTION: "Check ALTER DEFAULT PRIVILEGES syntax."
+
+ERRMSG: "redundant options"
+
+SQLSTATE: 42601
+
+CAUSE: "The syntax 'roles' is redundant in ALTER DEFAULT PRIVILEGES statement."
+
+ACTION: "Check ALTER DEFAULT PRIVILEGES syntax."
+
+ERRMSG: "option '%s' not recognized"
+
+SQLSTATE: 42601
+
+CAUSE: "The option in ALTER DEFAULT PRIVILEGES statement is not supported."
+
+ACTION: "Check ALTER DEFAULT PRIVILEGES syntax."
+
+ERRMSG: "unrecognized GrantStmt.objtype: %d"
+
+SQLSTATE: XX004
+
+CAUSE: "The object type is not supported for ALTER DEFAULT PRIVILEGES."
+
+ACTION: "Check ALTER DEFAULT PRIVILEGES syntax to obtain the supported object types."
+
+ERRMSG: "invalid alter default privileges operation"
+
+SQLSTATE: 0LP01
+
+CAUSE: "Default privileges cannot be set for columns."
+
+ACTION: "Check ALTER DEFAULT PRIVILEGES syntax."
+
+ERRMSG: "unrecognized objtype: %d"
+
+SQLSTATE: XX004
+
+CAUSE: "The object type is not supported for default privileges."
+
+ACTION: "Check ALTER DEFAULT PRIVILEGES syntax to obtain the supported object types."
+
+ERRMSG: "could not find tuple for default ACL %u"
+
+SQLSTATE: 29P01
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "unexpected default ACL type: %d"
+
+SQLSTATE: 0LP01
+
+CAUSE: "The object type is not supported for default privilege."
+
+ACTION: "Check ALTER DEFAULT PRIVILEGES syntax to obtain the supported object types."
+
+ERRMSG: "invalid object id"
+
+SQLSTATE: 0LP01
+
+CAUSE: "The object type is not supported for GRANT/REVOKE."
+
+ACTION: "Check GRANT/REVOKE syntax to obtain the supported object types."
+
+ERRMSG: "undefined column"
+
+SQLSTATE: 42703
+
+CAUSE: "The column of the relation does not exist."
+
+ACTION: "Check whether the column exists."
+
+ERRMSG: "column number out of range"
+
+SQLSTATE: 0LP01
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "cache lookup failed for attribute %d of relation %u"
+
+SQLSTATE: 29P01
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "cache lookup failed for relation %u"
+
+SQLSTATE: 29P01
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "unsupported object type"
+
+SQLSTATE: 42809
+
+CAUSE: "Index type is not supported for GRANT/REVOKE."
+
+ACTION: "Check GRANT/REVOKE syntax to obtain the supported object types."
+
+ERRMSG: "unsupported object type"
+
+SQLSTATE: 42809
+
+CAUSE: "Composite type is not supported for GRANT/REVOKE."
+
+ACTION: "Check GRANT/REVOKE syntax to obtain the supported object types."
+
+ERRMSG: "wrong object type"
+
+SQLSTATE: 42809
+
+CAUSE: "GRANT/REVOKE SEQUENCE only support sequence objects."
+
+ACTION: "Check GRANT/REVOKE syntax to obtain the supported object types."
+
+ERRMSG: "invalid privilege type USAGE for table"
+
+SQLSTATE: 0LP01
+
+CAUSE: "GRANT/REVOKE TABLE do not support USAGE privilege."
+
+ACTION: "Check GRANT/REVOKE syntax to obtain the supported privilege types for tables."
+
+ERRMSG: "invalid privilege type %s for column"
+
+SQLSTATE: 0LP01
+
+CAUSE: "The privilege type is not supported for column object."
+
+ACTION: "Check GRANT/REVOKE syntax to obtain the supported privilege types for column object."
+
+ERRMSG: "cache lookup failed for database %u"
+
+SQLSTATE: 29P01
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "cache lookup failed for foreign-data wrapper %u"
+
+SQLSTATE: 29P01
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "cache lookup failed for foreign server %u"
+
+SQLSTATE: 29P01
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "cache lookup failed for function %u"
+
+SQLSTATE: 29P01
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "cache lookup failed for language %u"
+
+SQLSTATE: 29P01
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "Grant/revoke on untrusted languages if forbidden."
+
+SQLSTATE: 0LP01
+
+CAUSE: "Grant/revoke on untrusted languages if forbidden."
+
+ACTION: "Support grant/revoke on trusted C languages"
+
+ERRMSG: "Forbid grant language c to user with grant option."
+
+SQLSTATE: 0A000
+
+CAUSE: "Forbid grant language c to user with grant option."
+
+ACTION: "Only support grant language c to user."
+
+ERRMSG: "Forbid grant language c to public."
+
+SQLSTATE: 0A000
+
+CAUSE: "Forbid grant language c to public."
+
+ACTION: "Grant language c to specified users."
+
+ERRMSG: "cache lookup failed for large object %u"
+
+SQLSTATE: 29P01
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "cache lookup failed for namespace %u"
+
+SQLSTATE: 29P01
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "cache lookup failed for tablespace %u"
+
+SQLSTATE: 29P01
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "cache lookup failed for type %u"
+
+SQLSTATE: 29P01
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "cannot set privileges of array types"
+
+SQLSTATE: 0LP01
+
+CAUSE: "Cannot set privileges of array types."
+
+ACTION: "Set the privileges of the element type instead."
+
+ERRMSG: "wrong object type"
+
+SQLSTATE: 42809
+
+CAUSE: "GRANT/REVOKE DOMAIN only support domain objects."
+
+ACTION: "Check GRANT/REVOKE syntax to obtain the supported object types."
+
+ERRMSG: "cache lookup failed for data source %u"
+
+SQLSTATE: 29P01
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "cache lookup failed for client master key %u"
+
+SQLSTATE: 29P01
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "cache lookup failed for column encryption key %u"
+
+SQLSTATE: 29P01
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "cache lookup failed for directory %u"
+
+SQLSTATE: 29P01
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "unrecognized privilege type '%s'"
+
+SQLSTATE: 42601
+
+CAUSE: "The privilege type is not supported."
+
+ACTION: "Check GRANT/REVOKE syntax to obtain the supported privilege types."
+
+ERRMSG: "unrecognized privilege: %d"
+
+SQLSTATE: XX004
+
+CAUSE: "The privilege type is not supported."
+
+ACTION: "Check GRANT/REVOKE syntax to obtain the supported privilege types."
+
+ERRMSG: "unrecognized AclResult"
+
+SQLSTATE: XX004
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "permission denied for column '%s' of relation '%s'"
+
+SQLSTATE: 42501
+
+CAUSE: "Insufficient privileges for the column."
+
+ACTION: "Select the system tables to get the acl of the column."
+
+ERRMSG: "role with OID %u does not exist"
+
+SQLSTATE: 42704
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "unrecognized objkind: %d"
+
+SQLSTATE: XX004
+
+CAUSE: "The object type is not supported for privilege check."
+
+ACTION: "Check GRANT/REVOKE syntax to obtain the supported object types."
+
+ERRMSG: "attribute %d of relation with OID %u does not exist"
+
+SQLSTATE: 42703
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "the column has been dropped"
+
+SQLSTATE: 42703
+
+CAUSE: "The column does not exist."
+
+ACTION: "Check whether the column exists."
+
+ERRMSG: "relation with OID %u does not exist"
+
+SQLSTATE: 42P01
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "invalid group"
+
+SQLSTATE: 22000
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "database with OID %u does not exist"
+
+SQLSTATE: 3D000
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "directory with OID %u does not exist"
+
+SQLSTATE: 42704
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "function with OID %u does not exist"
+
+SQLSTATE: 42883
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "client master key with OID %u does not exist"
+
+SQLSTATE: 42705
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "language with OID %u does not exist"
+
+SQLSTATE: 42704
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "large object %u does not exist"
+
+SQLSTATE: 42704
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "schema with OID %u does not exist"
+
+SQLSTATE: 3F001
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "tablespace with OID %u does not exist"
+
+SQLSTATE: 42704
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "foreign-data wrapper with OID %u does not exist"
+
+SQLSTATE: 42704
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "foreign server with OID %u does not exist"
+
+SQLSTATE: 42704
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "data source with OID %u does not exist"
+
+SQLSTATE: 42704
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "type with OID %u does not exist"
+
+SQLSTATE: 42704
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "operator with OID %u does not exist"
+
+SQLSTATE: 42883
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "column encryption key with OID %u does not exist"
+
+SQLSTATE: 42705
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "operator class with OID %u does not exist"
+
+SQLSTATE: 42704
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "operator family with OID %u does not exist"
+
+SQLSTATE: 42704
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "text search dictionary with OID %u does not exist"
+
+SQLSTATE: 42704
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "text search configuration with OID %u does not exist"
+
+SQLSTATE: 42704
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "collation with OID %u does not exist"
+
+SQLSTATE: 42704
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "conversion with OID %u does not exist"
+
+SQLSTATE: 42704
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "extension with OID %u does not exist"
+
+SQLSTATE: 42704
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "synonym with OID %u does not exist"
+
+SQLSTATE: 42704
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "package can not create the same name with schema."
+
+SQLSTATE: 22023
+
+CAUSE: "Package name conflict"
+
+ACTION: "Please rename package name"
+
+ERRMSG: "type is not exists %s."
+
+SQLSTATE: 22023
+
+CAUSE: "System error."
+
+ACTION: "Contact Enmo Engineer."
+
+ERRMSG: "This input type is not supported for tdigest_in()"
+
+SQLSTATE: 0A000
+
+CAUSE: "input type is not supported"
+
+ACTION: "Check tdigest_in syntax to obtain the supported privilege types"
+
+ERRMSG: "Failed to apply for memory"
+
+SQLSTATE: 53200
+
+CAUSE: "palloc failed"
+
+ACTION: "Check memory"
+
+ERRMSG: "Failed to get tde info from relation '%s'."
+
+SQLSTATE: XX005
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "SPI_connect failed: %s"
+
+SQLSTATE: SP001
+
+CAUSE: "System error."
+
+ACTION: "Analyze the error message before the error"
+
+ERRMSG: "permission denied for terminate snapshot thread"
+
+SQLSTATE: 42501
+
+CAUSE: "The user does not have system admin privilege"
+
+ACTION: "Grant system admin to user"
+
+ERRMSG: "terminate snapshot thread failed"
+
+SQLSTATE: OP001
+
+CAUSE: "Execution failed due to: %s"
+
+ACTION: "check if snapshot thread exists"
+
+ERRMSG: "terminate snapshot thread failed"
+
+SQLSTATE: OP001
+
+CAUSE: "restart wdr snapshot thread timeoutor The thread did not respond to the kill signal"
+
+ACTION: "Check the wdr snapshot thread is restarted"
+
+ERRMSG: "set lockwait_timeout failed"
+
+SQLSTATE: XX000
+
+CAUSE: "System error."
+
+ACTION: "Contact engineer to support."
+
+ERRMSG: "permission denied for create WDR Snapshot"
+
+SQLSTATE: 42501
+
+CAUSE: "The user does not have system admin privilege"
+
+ACTION: "Grant system admin to user"
+
+ERRMSG: "WDR snapshot request can not be accepted, please retry later"
+
+SQLSTATE: OP001
+
+CAUSE: "wdr snapshot thread does not exist"
+
+ACTION: "Check if wdr snapshot thread exists"
+
+ERRMSG: "Cannot respond to WDR snapshot request"
+
+SQLSTATE: OP001
+
+CAUSE: "Execution failed due to: %s"
+
+ACTION: "Check if wdr snapshot thread exists"
+
+ERRMSG: "query(%s) can not get datum values"
+
+SQLSTATE: 22000
+
+CAUSE: "System error."
+
+ACTION: "Check whether the query can be executed"
+
+ERRMSG: "create sequence failed"
+
+SQLSTATE: 22000
+
+CAUSE: "System error."
+
+ACTION: "Check if sequence can be created"
+
+ERRMSG: "update snapshot end time stamp filled"
+
+SQLSTATE: 22000
+
+CAUSE: "System error."
+
+ACTION: "Check whether the snapshot retry is successful"
+
+ERRMSG: "query can not get datum values"
+
+SQLSTATE: 22000
+
+CAUSE: "System error."
+
+ACTION: "Check whether the query can be executed"
+
+ERRMSG: "SPI_connect failed: %s"
+
+SQLSTATE: XX000
+
+CAUSE: "System error."
+
+ACTION: "Check whether the snapshot retry is successful"
+
+ERRMSG: "query(%s) execute failed"
+
+SQLSTATE: 22000
+
+CAUSE: "System error."
+
+ACTION: "Check whether the snapshot retry is successful"
+
+ERRMSG: "clean table of snap_%s is failed"
+
+SQLSTATE: 22000
+
+CAUSE: "System error."
+
+ACTION: "Check whether the snapshot retry is successful"
+
+ERRMSG: "analyze table failed"
+
+SQLSTATE: 22000
+
+CAUSE: "System error."
+
+ACTION: "Check whether the snapshot retry is successful"
+
+ERRMSG: "insert into tables_snap_timestamp start time stamp is failed"
+
+SQLSTATE: 22000
+
+CAUSE: "System error."
+
+ACTION: "Check whether the snapshot retry is successful"
+
+ERRMSG: "insert data failed"
+
+SQLSTATE: 22000
+
+CAUSE: "System error."
+
+ACTION: "Check whether the snapshot retry is successful and check whether the query can be executed"
+
+ERRMSG: "update tables_snap_timestamp end time stamp is failed"
+
+SQLSTATE: 22000
+
+CAUSE: "System error."
+
+ACTION: "Check whether the snapshot retry is successful"
+
+ERRMSG: "clean snapshot id %lu is failed in snapshot table"
+
+SQLSTATE: 22000
+
+CAUSE: "System error."
+
+ACTION: "Check whether the snapshot retry is successful and check whether the query can be executed"
+
+ERRMSG: "clean snapshot failed"
+
+SQLSTATE: 22000
+
+CAUSE: "System error."
+
+ACTION: "Check whether the snapshot retry is successful"
+
+ERRMSG: "can not create snapshot stat table"
+
+SQLSTATE: 22000
+
+CAUSE: "System error."
+
+ACTION: "Check whether the query can be executed"
+
+ERRMSG: "create WDR snapshot data table failed"
+
+SQLSTATE: 22000
+
+CAUSE: "System error."
+
+ACTION: "Check whether the query can be executed"
+
+ERRMSG: "insert into tables_snap_timestamp start time stamp failed"
+
+SQLSTATE: 22000
+
+CAUSE: "System error."
+
+ACTION: "Check whether the query can be executed"
+
+ERRMSG: "insert into snap_%s is failed"
+
+SQLSTATE: 22000
+
+CAUSE: "System error."
+
+ACTION: "Check whether the query can be executed"
+
+ERRMSG: "update tables_snap_timestamp end time stamp failed"
+
+SQLSTATE: 22000
+
+CAUSE: "System error."
+
+ACTION: "Check whether the query can be executed"
+
+ERRMSG: "create index failed"
+
+SQLSTATE: 22000
+
+CAUSE: "System error."
+
+ACTION: "Check whether the query can be executed"
+
+ERRMSG: "analyze table, connection failed: %s"
+
+SQLSTATE: XX000
+
+CAUSE: "System error."
+
+ACTION: "Check whether the snapshot retry is successful"
+
+ERRMSG: "snapshot thread SPI_connect failed: %s"
+
+SQLSTATE: XX000
+
+CAUSE: "System error."
+
+ACTION: "Check whether the snapshot retry is successful"
+
+ERRMSG: "Distributed key column can't be transformed"
+
+SQLSTATE: 42P10
+
+CAUSE: "There is a risk of violating uniqueness when transforming distribution columns."
+
+ACTION: "Change transform column."
+
+ERRMSG: "cannot convert %s to %s"
+
+SQLSTATE: 42804
+
+CAUSE: "There is no conversion path in pg_cast."
+
+ACTION: "Rewrite or cast the expression."
+
+ERRMSG: "create matview on TDE table failed"
+
+SQLSTATE: 0A000
+
+CAUSE: "create materialized views is not supported on TDE table"
+
+ACTION: "check CREATE syntax about create the materialized views"
+
+ERRMSG: "schema name can not same as package"
+
+SQLSTATE: 22023
+
+CAUSE: "schema name conflict"
+
+ACTION: "rename schema name"
+
+ERRMSG: "Unrecognized commandType when checking read-only attribute."
+
+SQLSTATE: XX004
+
+CAUSE: "System error."
+
+ACTION: "Contact Enmo Engineer."
+
+ERRMSG: "Fail to generate subquery plan."
+
+SQLSTATE: XX005
+
+CAUSE: "System error."
+
+ACTION: "Contact Enmo Engineer."
+
+ERRMSG: "Unrecognized node type when processing qual condition."
+
+SQLSTATE: XX004
+
+CAUSE: "System error."
+
+ACTION: "Contact Enmo Engineer."
+
+ERRMSG: "Unrecognized node type when processing const parameters."
+
+SQLSTATE: XX004
+
+CAUSE: "System error."
+
+ACTION: "Contact Enmo Engineer."
+
+ERRMSG: "SELECT FOR UPDATE/SHARE is not allowed with UNION/INTERSECT/EXCEPT"
+
+SQLSTATE: 0A000
+
+CAUSE: "SQL uses unsupported feature."
+
+ACTION: "Modify SQL statement according to the manual."
+
+ERRMSG: "GROUP BY cannot be implemented."
+
+SQLSTATE: 0A000
+
+CAUSE: "GROUP BY uses unsupported datatypes."
+
+ACTION: "Modify SQL statement according to the manual."
+
+ERRMSG: "TSDB functions cannot be used if enable_tsdb is off."
+
+SQLSTATE: D0011
+
+CAUSE: "Functions are not loaded."
+
+ACTION: "Turn on enable_tsdb according to manual."
+
+ERRMSG: "Unrecognized node type when extracting index."
+
+SQLSTATE: XX004
+
+CAUSE: "System error."
+
+ACTION: "Contact Enmo Engineer."
+
+ERRMSG: "Ordering operator cannot be identified."
+
+SQLSTATE: 42883
+
+CAUSE: "Grouping set columns must be able to sort their inputs."
+
+ACTION: "Modify SQL statement according to the manual."
+
+ERRMSG: "DISTINCT cannot be implemented."
+
+SQLSTATE: 0A000
+
+CAUSE: "DISTINCT uses unsupported datatypes."
+
+ACTION: "Modify SQL statement according to the manual."
+
+ERRMSG: "Failed to locate grouping columns."
+
+SQLSTATE: 55000
+
+CAUSE: "System error."
+
+ACTION: "Contact Enmo Engineer."
+
+ERRMSG: "Resjunk output columns are not implemented."
+
+SQLSTATE: 20000
+
+CAUSE: "System error."
+
+ACTION: "Contact Enmo Engineer."
+
+ERRMSG: "PARTITION BY cannot be implemented."
+
+SQLSTATE: 0A000
+
+CAUSE: "PARTITION BY uses unsupported datatypes."
+
+ACTION: "Modify SQL statement according to the manual."
+
+ERRMSG: "ORDER BY cannot be implemented."
+
+SQLSTATE: 0A000
+
+CAUSE: "ORDER BY uses unsupported datatypes."
+
+ACTION: "Modify SQL statement according to the manual."
+
+ERRMSG: "Failed to deconstruct sort operators into partitioning/ordering operators."
+
+SQLSTATE: D0011
+
+CAUSE: "System error."
+
+ACTION: "Contact Enmo Engineer."
+
+ERRMSG: "OBS and HDFS foreign table can NOT be in the same plan."
+
+SQLSTATE: XX008
+
+CAUSE: "SQL uses unsupported feature."
+
+ACTION: "Modify SQL statement according to the manual."
+
+ERRMSG: "Pool size should not be zero"
+
+SQLSTATE: 22012
+
+CAUSE: "Compute pool configuration file contains error."
+
+ACTION: "Please check the value of 'pl' in cp_client.conf."
+
+ERRMSG: "Failed to get the runtime info from the compute pool."
+
+SQLSTATE: 22004
+
+CAUSE: "System error."
+
+ACTION: "Contact Enmo Engineer."
+
+ERRMSG: "Version is not compatible between local cluster and the compute pool."
+
+SQLSTATE: XX008
+
+CAUSE: "Compute pool is not installed appropriately."
+
+ACTION: "Configure compute pool according to manual."
+
+ERRMSG: "No optional index path is found."
+
+SQLSTATE: 01000
+
+CAUSE: "System error."
+
+ACTION: "Contact Enmo Engineer."
+
+ERRMSG: "MERGE INTO on replicated table does not yet support using distributed tables."
+
+SQLSTATE: 0A000
+
+CAUSE: "SQL uses unsupported feature."
+
+ACTION: "Modify SQL statement according to the manual."
+
+ERRMSG: "Fail to find ForeignScan node!"
+
+SQLSTATE: P0002
+
+CAUSE: "System error."
+
+ACTION: "Contact Enmo Engineer."
+
+ERRMSG: "sql advisor don't support none table, temp table, system table."
+
+SQLSTATE: 42601
+
+CAUSE: "sql advisor don't support none table, temp table, system table."
+
+ACTION: "check query component"
+
+ERRMSG: "Invalid autonomous transaction return datatypes"
+
+SQLSTATE: P0000
+
+CAUSE: "PL/SQL uses unsupported feature."
+
+ACTION: "Contact Enmo Engineer."
+
+ERRMSG: "new row for relation '%s' violates check constraint '%s'"
+
+SQLSTATE: 23514
+
+CAUSE: "some rows copy failed"
+
+ACTION: "check table defination"
+
+ERRMSG: "new row for relation '%s' violates check constraint '%s'"
+
+SQLSTATE: 23514
+
+CAUSE: "some rows copy failed"
+
+ACTION: "set client_min_messages = info for more details"
+
+ERRMSG: "get gauss home path is NULL"
+
+SQLSTATE: XX005
+
+CAUSE: "gauss home path not set"
+
+ACTION: "check if $GAUSSHOME is exist"
+
+ERRMSG: "unable to open kms_iam_info.json file"
+
+SQLSTATE: 58P03
+
+CAUSE: "file not exist or broken"
+
+ACTION: "check the kms_iam_info.json file"
+
+ERRMSG: "can not get password plaintext"
+
+SQLSTATE: XX005
+
+CAUSE: "file not exist or broken"
+
+ACTION: "check the password cipher rand file"
+
+ERRMSG: "IAM info json key is NULL"
+
+SQLSTATE: XX005
+
+CAUSE: "IAM info value error"
+
+ACTION: "check tde_config kms_iam_info.json file"
+
+ERRMSG: "get internal password is NULL"
+
+SQLSTATE: XX005
+
+CAUSE: "cipher rand file missing"
+
+ACTION: "check password cipher rand file"
+
+ERRMSG: "KMS info json key is NULL"
+
+SQLSTATE: XX005
+
+CAUSE: "KMS info value error"
+
+ACTION: "check tde_config kms_iam_info.json file"
+
+ERRMSG: "unable to get json file"
+
+SQLSTATE: 58P03
+
+CAUSE: "parse json file failed"
+
+ACTION: "check the kms_iam_info.json file format"
+
+ERRMSG: "get JSON tree is NULL"
+
+SQLSTATE: XX005
+
+CAUSE: "get KMS JSON tree failed"
+
+ACTION: "check input prarmeter or config.ini file"
+
+ERRMSG: "failed to get json tree"
+
+SQLSTATE: XX005
+
+CAUSE: "config.ini json tree error"
+
+ACTION: "check input prarmeter or config.ini file"
+
+ERRMSG: "failed to set the value of json tree"
+
+SQLSTATE: XX005
+
+CAUSE: "config.ini json tree error"
+
+ACTION: "check input prarmeter or config.ini file"
+
+ERRMSG: "http request failed"
+
+SQLSTATE: XX005
+
+CAUSE: "http request error"
+
+ACTION: "check KMS or IAM connect or config parameter"
+
+ERRMSG: "get iam token or iam agency token is NULL"
+
+SQLSTATE: XX005
+
+CAUSE: "connect IAM failed"
+
+ACTION: "check if your env can connect with IAM server"
+
+ERRMSG: "KMS dek json key is NULL"
+
+SQLSTATE: XX005
+
+CAUSE: "KMS return value error"
+
+ACTION: "check KMS config paramenter"
+
+ERRMSG: "get kms dek is NULL"
+
+SQLSTATE: XX005
+
+CAUSE: "connect KMS failed"
+
+ACTION: "check if your env can connect with KMS server"
+
+ERRMSG: "get http header is NULL"
+
+SQLSTATE: XX005
+
+CAUSE: "http request failed"
+
+ACTION: "check IAM config parameter"
+
+ERRMSG: "create KMS dek failed"
+
+SQLSTATE: XX005
+
+CAUSE: "KMS error"
+
+ACTION: "check KMS connect or config parameter"
+
+ERRMSG: "get KMS dek failed"
+
+SQLSTATE: XX005
+
+CAUSE: "KMS error"
+
+ACTION: "check KMS connect or config parameter"
+
+ERRMSG: "get KMS DEK is NULL"
+
+SQLSTATE: XX005
+
+CAUSE: "get KMS dek_plaintext failed"
+
+ACTION: "check KMS network or cipher is right"
+
+ERRMSG: "create matview with TDE failed"
+
+SQLSTATE: 0A000
+
+CAUSE: "TDE feature is not supported for Create materialized views"
+
+ACTION: "check CREATE syntax about create the materialized views"
+
+ERRMSG: "failed to add item to the index page"
+
+SQLSTATE: XX002
+
+CAUSE: "System error."
+
+ACTION: "Check WARNINGS for the details."
+
+ERRMSG: "index row size %lu exceeds maximum %lu for index '%s'"
+
+SQLSTATE: 54000
+
+CAUSE: "Values larger than 1⁄3 of a buffer page cannot be indexed."
+
+ACTION: "Consider a function index of an MD5 hash of the value, or use full text indexing."
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/1-logical-operators.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/1-logical-operators.md
new file mode 100644
index 0000000000000000000000000000000000000000..58501eff388daafef1df9f757b787df2cb0115fe
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/1-logical-operators.md
@@ -0,0 +1,26 @@
+---
+title: Logical Operators
+summary: Logical Operators
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Logical Operators
+
+The usual logical operators include AND, OR, and NOT. SQL uses a three-valued logical system with true, false, and null, which represents "unknown". Their priorities are NOT &gt; AND &gt; OR.
+
+[Table 1](#Operation rules) lists the calculation rules, where a and b represent logical expressions.
+
+**Table 1** Operation rules<a id="Operation rules"> </a>
+
+| a     | b     | a **AND** b Result | a **OR** b Result | **NOT** a Result |
+| :---- | :---- | :----------------- | :---------------- | :--------------- |
+| TRUE  | TRUE  | TRUE               | TRUE              | FALSE            |
+| TRUE  | FALSE | FALSE              | TRUE              | FALSE            |
+| TRUE  | NULL  | NULL               | TRUE              | FALSE            |
+| FALSE | FALSE | FALSE              | FALSE             | TRUE             |
+| FALSE | NULL  | FALSE              | NULL              | TRUE             |
+| NULL  | NULL  | NULL               | NULL              | NULL             |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> The operators AND and OR are commutative, that is, you can switch the left and right operand without affecting the result.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/10-geometric-functions-and-operators.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/10-geometric-functions-and-operators.md
new file mode 100644
index 0000000000000000000000000000000000000000..3b7955b5727dbfe743bdd33a360390d3bcb3b135
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/10-geometric-functions-and-operators.md
@@ -0,0 +1,948 @@
+---
+title: Geometric Functions and Operators
+summary: Geometric Functions and Operators
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Geometric Functions and Operators
+
+## Geometric Operators
+
+- \+
+
+  Description: Translation
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT box '((0,0),(1,1))' + point '(2.0,0)' AS RESULT;
+     result
+  -------------
+   (3,1),(2,0)
+  (1 row)
+  ```
+
+- \-
+
+  Description: Translation
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT box '((0,0),(1,1))' - point '(2.0,0)' AS RESULT;
+      result
+  ---------------
+   (-1,1),(-2,0)
+  (1 row)
+  ```
+
+- \*
+
+  Description: Scaling out/Rotation
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT box '((0,0),(1,1))' * point '(2.0,0)' AS RESULT;
+     result
+  -------------
+   (2,2),(0,0)
+  (1 row)
+  ```
+
+- /
+
+  Description: Scaling in/Rotation
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT box '((0,0),(2,2))' / point '(2.0,0)' AS RESULT;
+     result
+  -------------
+   (1,1),(0,0)
+  (1 row)
+  ```
+
+- \#
+
+  Description: Intersection of two figures
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT box '((1,-1),(-1,1))' # box '((1,1),(-2,-2))' AS RESULT;
+   result
+  ---------------
+   (1,1),(-1,-1)
+  (1 row)
+  ```
+
+- \#
+
+  Description: Number of paths or polygon vertexes of a figure
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT # path'((1,0),(0,1),(-1,0))' AS RESULT;
+   result
+  --------
+        3
+  (1 row)
+  ```
+
+- @-@
+
+  Description: Length or circumference of a figure
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT @-@ path '((0,0),(1,0))' AS RESULT;
+   result
+  --------
+        2
+  (1 row)
+  ```
+
+- @@
+
+  Description: Center of a figure
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT @@ circle '((0,0),10)' AS RESULT;
+   result
+  --------
+   (0,0)
+  (1 row)
+  ```
+
+- &lt;-&gt;
+
+  Description: Distance between two figures
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT circle '((0,0),1)' <-> circle '((5,0),1)' AS RESULT;
+   result
+  --------
+        3
+  (1 row)
+  ```
+
+- &&
+
+  Description: Overlaps? (One point in common makes this true.)
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT box '((0,0),(1,1))' && box '((0,0),(2,2))' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;&lt;
+
+  Description: Is strictly left of (no common horizontal coordinate)?
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT circle '((0,0),1)' << circle '((5,0),1)' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &gt;&gt;
+
+  Description: Is strictly right of (no common horizontal coordinate)?
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT circle '((5,0),1)' >> circle '((0,0),1)' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &&lt;
+
+  Description: Does not extend to the right of?
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT box '((0,0),(1,1))' &< box '((0,0),(2,2))' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &&gt;
+
+  Description: Does not extend to the left of?
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT box '((0,0),(3,3))' &> box '((0,0),(2,2))' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;&lt;|
+
+  Description: Is strictly below (no common horizontal coordinate)?
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT box '((0,0),(3,3))' <<| box '((3,4),(5,5))' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- |&gt;&gt;
+
+  Description: Is strictly above (no common horizontal coordinate)?
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT box '((3,4),(5,5))' |>> box '((0,0),(3,3))' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &&lt;|
+
+  Description: Does not extend above?
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT box '((0,0),(1,1))' &<| box '((0,0),(2,2))' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- |&&gt;
+
+  Description: Does not extend below?
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT box '((0,0),(3,3))' |&> box '((0,0),(2,2))' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;^
+
+  Description: Is below (allows touching)?
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT box '((0,0),(-3,-3))' <^ box '((0,0),(2,2))' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &gt;^
+
+  Description: Is above (allows touching)?
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT box '((0,0),(2,2))' >^ box '((0,0),(-3,-3))'  AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- ?#
+
+  Description: Intersect?
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT lseg '((-1,0),(1,0))' ?# box '((-2,-2),(2,2))' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- ?-
+
+  Description: Is horizontal?
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT ?- lseg '((-1,0),(1,0))' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- ?-
+
+  Description: Are horizontally aligned?
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT point '(1,0)' ?- point '(0,0)' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- ?|
+
+  Description: Is vertical?
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT ?| lseg '((-1,0),(1,0))' AS RESULT;
+   result
+  --------
+   f
+  (1 row)
+  ```
+
+- ?|
+
+  Description: Are vertically aligned?
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT point '(0,1)' ?| point '(0,0)' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- ?-|
+
+  Description: Are perpendicular?
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT lseg '((0,0),(0,1))' ?-| lseg '((0,0),(1,0))' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- ?||
+
+  Description: Are parallel?
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT lseg '((-1,0),(1,0))' ?|| lseg '((-1,2),(1,2))' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- @&gt;
+
+  Description: Contains?
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT circle '((0,0),2)' @> point '(1,1)' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;@
+
+  Description: Contained in or on?
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT point '(1,1)' <@ circle '((0,0),2)' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- ~=
+
+  Description: Same as?
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT polygon '((0,0),(1,1))' ~= polygon '((1,1),(0,0))' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+## Geometric Functions
+
+- area(object)
+
+  Description: Area calculation
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT area(box '((0,0),(1,1))') AS RESULT;
+   result
+  --------
+        1
+  (1 row)
+  ```
+
+- center(object)
+
+  Description: Figure center calculation
+
+  Return type: point
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT center(box '((0,0),(1,2))') AS RESULT;
+   result
+  ---------
+   (0.5,1)
+  (1 row)
+  ```
+
+- diameter(circle)
+
+  Description: Circle diameter calculation
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT diameter(circle '((0,0),2.0)') AS RESULT;
+   result
+  --------
+        4
+  (1 row)
+  ```
+
+- height(box)
+
+  Description: Vertical size of box
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT height(box '((0,0),(1,1))') AS RESULT;
+   result
+  --------
+        1
+  (1 row)
+  ```
+
+- isclosed(path)
+
+  Description: A closed path?
+
+  Return type: Boolean
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT isclosed(path '((0,0),(1,1),(2,0))') AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- isopen(path)
+
+  Description: An open path?
+
+  Return type: Boolean
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT isopen(path '[(0,0),(1,1),(2,0)]') AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- length(object)
+
+  Description: Length calculation
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT length(path '((-1,0),(1,0))') AS RESULT;
+   result
+  --------
+        4
+  (1 row)
+  ```
+
+- npoints(path)
+
+  Description: Number of points in a path
+
+  Return type: int
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT npoints(path '[(0,0),(1,1),(2,0)]') AS RESULT;
+   result
+  --------
+        3
+  (1 row)
+  ```
+
+- npoints(polygon)
+
+  Description: Number of points in a polygon
+
+  Return type: int
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT npoints(polygon '((1,1),(0,0))') AS RESULT;
+   result
+  --------
+        2
+  (1 row)
+  ```
+
+- pclose(path)
+
+  Description: Converts a path to closed.
+
+  Return type: path
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT pclose(path '[(0,0),(1,1),(2,0)]') AS RESULT;
+         result
+  ---------------------
+   ((0,0),(1,1),(2,0))
+  (1 row)
+  ```
+
+- popen(path)
+
+  Description: Converts a path to open.
+
+  Return type: path
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT popen(path '((0,0),(1,1),(2,0))') AS RESULT;
+         result
+  ---------------------
+   [(0,0),(1,1),(2,0)]
+  (1 row)
+  ```
+
+- radius(circle)
+
+  Description: Circle radius calculation
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT radius(circle '((0,0),2.0)') AS RESULT;
+   result
+  --------
+        2
+  (1 row)
+  ```
+
+- width(box)
+
+  Description: Horizontal size of a box
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT width(box '((0,0),(1,1))') AS RESULT;
+   result
+  --------
+        1
+  (1 row)
+  ```
+
+## Geometric Type Conversion Functions
+
+- box(circle)
+
+  Description: Circle to box
+
+  Return type: box
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT box(circle '((0,0),2.0)') AS RESULT;
+                                    result
+  ---------------------------------------------------------------------------
+   (1.41421356237309,1.41421356237309),(-1.41421356237309,-1.41421356237309)
+  (1 row)
+  ```
+
+- box(point, point)
+
+  Description: Points to box
+
+  Return type: box
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT box(point '(0,0)', point '(1,1)') AS RESULT;
+     result
+  -------------
+   (1,1),(0,0)
+  (1 row)
+  ```
+
+- box(polygon)
+
+  Description: Polygon to box
+
+  Return type: box
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT box(polygon '((0,0),(1,1),(2,0))') AS RESULT;
+     result
+  -------------
+   (2,1),(0,0)
+  (1 row)
+  ```
+
+- circle(box)
+
+  Description: Box to circle
+
+  Return type: circle
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT circle(box '((0,0),(1,1))') AS RESULT;
+              result
+  -------------------------------
+   <(0.5,0.5),0.707106781186548>
+  (1 row)
+  ```
+
+- circle(point, double precision)
+
+  Description: Center and radius to circle
+
+  Return type: circle
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT circle(point '(0,0)', 2.0) AS RESULT;
+    result
+  -----------
+   <(0,0),2>
+  (1 row)
+  ```
+
+- circle(polygon)
+
+  Description: Polygon to circle
+
+  Return type: circle
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT circle(polygon '((0,0),(1,1),(2,0))') AS RESULT;
+                    result
+  -------------------------------------------
+   <(1,0.333333333333333),0.924950591148529>
+  (1 row)
+  ```
+
+- lseg(box)
+
+  Description: Box diagonal to line segment
+
+  Return type: lseg
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT lseg(box '((-1,0),(1,0))') AS RESULT;
+       result
+  ----------------
+   [(1,0),(-1,0)]
+  (1 row)
+  ```
+
+- lseg(point, point)
+
+  Description: Points to line segment
+
+  Return type: lseg
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT lseg(point '(-1,0)', point '(1,0)') AS RESULT;
+       result
+  ----------------
+   [(-1,0),(1,0)]
+  (1 row)
+  ```
+
+- slope(point, point)
+
+    Description: Calculates the slope of a straight line formed by two points.
+
+    Return type: double
+
+    Example:
+
+    ```sql
+    mogdb=# SELECT slope(point '(1,1)', point '(0,0)') AS RESULT;
+     result
+    --------
+          1
+    (1 row)
+    ```
+
+- path(polygon)
+
+  Description: Polygon to path
+
+  Return type: path
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT path(polygon '((0,0),(1,1),(2,0))') AS RESULT;
+         result
+  ---------------------
+   ((0,0),(1,1),(2,0))
+  (1 row)
+  ```
+
+- point(double precision, double precision)
+
+  Description: Points
+
+  Return type: point
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT point(23.4, -44.5) AS RESULT;
+      result
+  --------------
+   (23.4,-44.5)
+  (1 row)
+  ```
+
+- point(box)
+
+  Description: Center of a box
+
+  Return type: point
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT point(box '((-1,0),(1,0))') AS RESULT;
+   result
+  --------
+   (0,0)
+  (1 row)
+  ```
+
+- point(circle)
+
+  Description: Center of a circle
+
+  Return type: point
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT point(circle '((0,0),2.0)') AS RESULT;
+   result
+  --------
+   (0,0)
+  (1 row)
+  ```
+
+- point(lseg)
+
+  Description: Center of a line segment
+
+  Return type: point
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT point(lseg '((-1,0),(1,0))') AS RESULT;
+   result
+  --------
+   (0,0)
+  (1 row)
+  ```
+
+- point(polygon)
+
+  Description: Center of a polygon
+
+  Return type: point
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT point(polygon '((0,0),(1,1),(2,0))') AS RESULT;
+          result
+  -----------------------
+   (1,0.333333333333333)
+  (1 row)
+  ```
+
+- polygon(box)
+
+  Description: Box to 4-point polygon
+
+  Return type: polygon
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT polygon(box '((0,0),(1,1))') AS RESULT;
+            result
+  ---------------------------
+   ((0,0),(0,1),(1,1),(1,0))
+  (1 row)
+  ```
+
+- polygon(circle)
+
+  Description: Circle to 12-point polygon
+
+  Return type: polygon
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT polygon(circle '((0,0),2.0)') AS RESULT;
+                                                                                                                                                  result
+
+  -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+   ((-2,0),(-1.73205080756888,1),(-1,1.73205080756888),(-1.22464679914735e-16,2),(1,1.73205080756888),(1.73205080756888,1),(2,2.44929359829471e-16),(1.73205080756888,-0.999999999999999),(1,-1.73205080756888),(3.67394039744206e-16,-2),(-0.999999999999999,-1.73205080756888),(-1.73205080756888,-1))
+  (1 row)
+  ```
+
+- polygon(npts, circle)
+
+  Description: Circle to **npts**-point polygon
+
+  Return type: polygon
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT polygon(12, circle '((0,0),2.0)') AS RESULT;
+                                                                                                                                                  result
+
+  -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+   ((-2,0),(-1.73205080756888,1),(-1,1.73205080756888),(-1.22464679914735e-16,2),(1,1.73205080756888),(1.73205080756888,1),(2,2.44929359829471e-16),(1.73205080756888,-0.999999999999999),(1,-1.73205080756888),(3.67394039744206e-16,-2),(-0.999999999999999,-1.73205080756888),(-1.73205080756888,-1))
+  (1 row)
+  ```
+
+- polygon(path)
+
+  Description: Path to polygon
+
+  Return type: polygon
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT polygon(path '((0,0),(1,1),(2,0))') AS RESULT;
+         result
+  ---------------------
+   ((0,0),(1,1),(2,0))
+  (1 row)
+  ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/11-network-address-functions-and-operators.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/11-network-address-functions-and-operators.md
new file mode 100644
index 0000000000000000000000000000000000000000..b13c85932d407029702ed80a5c74263b22c581e8
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/11-network-address-functions-and-operators.md
@@ -0,0 +1,456 @@
+---
+title: Network Address Functions and Operators
+summary: Network Address Functions and Operators
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Network Address Functions and Operators
+
+## cidr and inet Operators
+
+The operators **&lt;&lt;**, **&lt;&lt;=**, **&gt;&gt;**, and **&gt;&gt;=** test for subnet inclusion. They consider only the network parts of the two addresses (ignoring any host part) and determine whether one network is identical to or a subnet of the other.
+
+- &lt;
+
+  Description: Is less than
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT inet '192.168.1.5' < inet '192.168.1.6' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;=
+
+  Description: Is less than or equals
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT inet '192.168.1.5' <= inet '192.168.1.5' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- =
+
+  Description: Equals
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT inet '192.168.1.5' = inet '192.168.1.5' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &gt;=
+
+  Description: Is greater than or equals
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT inet '192.168.1.5' >= inet '192.168.1.5' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &gt;
+
+  Description: Is greater than
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT inet '192.168.1.5' > inet '192.168.1.4' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;&gt;
+
+  Description: Does not equal to
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT inet '192.168.1.5' <> inet '192.168.1.4' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;&lt;
+
+  Description: Is contained in
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT inet '192.168.1.5' << inet '192.168.1/24' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;&lt;=
+
+  Description: Is contained in or equals
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT inet '192.168.1/24' <<= inet '192.168.1/24' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &gt;&gt;
+
+  Description: Contains
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT inet '192.168.1/24' >> inet '192.168.1.5' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &gt;&gt;=
+
+  Description: Contains or equals
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT inet '192.168.1/24' >>= inet '192.168.1/24' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- ~
+
+  Description: Bitwise NOT
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT ~ inet '192.168.1.6' AS RESULT;
+      result
+  ---------------
+   63.87.254.249
+  (1 row)
+  ```
+
+- &
+
+  Description: Performs an AND operation on each bit of the two network addresses.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT inet '192.168.1.6' & inet '10.0.0.0' AS RESULT;
+   result
+  ---------
+   0.0.0.0
+  (1 row)
+  ```
+
+- |
+
+  Description: Performs an OR operation on each bit of the two network addresses.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT inet '192.168.1.6' | inet '10.0.0.0' AS RESULT;
+     result
+  -------------
+   202.168.1.6
+  (1 row)
+  ```
+
+- \+
+
+  Description: Addition
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT inet '192.168.1.6' + 25 AS RESULT;
+      result
+  --------------
+   192.168.1.31
+  (1 row)
+  ```
+
+- \-
+
+  Description: Subtraction
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT inet '192.168.1.43' - 36 AS RESULT;
+     result
+  -------------
+   192.168.1.7
+  (1 row)
+  ```
+
+- \-
+
+  Description: Subtraction
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT inet '192.168.1.43' - inet '192.168.1.19' AS RESULT;
+   result
+  --------
+       24
+  (1 row)
+  ```
+
+## cidr and inet Functions
+
+The **abbrev**, **host**, and **text** functions are primarily intended to offer alternative display formats.
+
+- abbrev(inet)
+
+  Description: Abbreviated display format as text
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT abbrev(inet '10.1.0.0/16') AS RESULT;
+     result
+  -------------
+   10.1.0.0/16
+  (1 row)
+  ```
+
+- abbrev(cidr)
+
+  Description: Abbreviated display format as text
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT abbrev(cidr '10.1.0.0/16') AS RESULT;
+   result
+  ---------
+   10.1/16
+  (1 row)
+  ```
+
+- broadcast(inet)
+
+  Description: Broadcast address for networks
+
+  Return type: inet
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT broadcast('192.168.1.5/24') AS RESULT;
+        result
+  ------------------
+   192.168.1.255/24
+  (1 row)
+  ```
+
+- family(inet)
+
+  Description: Extracts family of addresses,  **4**  for IPv4, and  **6**  for IPv6.
+
+  Return type: int
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT family('127.0.0.1') AS RESULT;
+   result
+  --------
+        4
+  (1 row)
+  ```
+
+- host(inet)
+
+  Description: Extracts IP addresses as text.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT host('192.168.1.5/24') AS RESULT;
+     result
+  -------------
+   192.168.1.5
+  (1 row)
+  ```
+
+- hostmask(inet)
+
+  Description: Constructs the host mask for a network.
+
+  Return type: inet
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT hostmask('192.168.23.20/30') AS RESULT;
+   result
+  ---------
+   0.0.0.3
+  (1 row)
+  ```
+
+- masklen(inet)
+
+  Description: Extracts subnet mask length.
+
+  Return type: int
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT masklen('192.168.1.5/24') AS RESULT;
+   result
+  --------
+       24
+  (1 row)
+  ```
+
+- netmask(inet)
+
+  Description: Constructs the subnet mask for a network.
+
+  Return type: inet
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT netmask('192.168.1.5/24') AS RESULT;
+      result
+  ---------------
+   255.255.255.0
+  (1 row)
+  ```
+
+- network(inet)
+
+  Description: Extracts the network part of an address.
+
+  Return type: cidr
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT network('192.168.1.5/24') AS RESULT;
+       result
+  ----------------
+   192.168.1.0/24
+  (1 row)
+  ```
+
+- set_masklen(inet, int)
+
+  Description: Sets subnet mask length for the  **inet**  value.
+
+  Return type: inet
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT set_masklen('192.168.1.5/24', 16) AS RESULT;
+       result
+  ----------------
+   192.168.1.5/16
+  (1 row)
+  ```
+
+- set_masklen(cidr, int)
+
+  Description: Sets subnet mask length for the **cidr** value.
+
+  Return type: cidr
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT set_masklen('192.168.1.0/24'::cidr, 16) AS RESULT;
+       result
+  ----------------
+   192.168.0.0/16
+  (1 row)
+  ```
+
+- text(inet)
+
+  Description: Extracts IP addresses and subnet mask length as text.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT text(inet '192.168.1.5') AS RESULT;
+       result
+  ----------------
+   192.168.1.5/32
+  (1 row)
+  ```
+
+Any **cidr** value can be cast to **inet** implicitly or explicitly; therefore, the functions shown above as operating on **inet** also work on **cidr** values. An **inet** value can be cast to **cidr**. After the conversion, any bits to the right of the subnet mask are silently zeroed to create a valid **cidr** value. In addition, you can cast a text string to **inet** or **cidr** using normal casting syntax. For example, **inet(expression)** or **colname::cidr**.
+
+## macaddr Functions
+
+The function **trunc(macaddr)** returns a MAC address with the last 3 bytes set to zero.
+
+- trunc(macaddr)
+
+  Description: Sets last 3 bytes to zero.
+
+  Return type: macaddr
+
+  Example:
+
+```sql
+mogdb=# SELECT trunc(macaddr '12:34:56:78:90:ab') AS RESULT;
+      result
+-------------------
+ 12:34:56:00:00:00
+(1 row)
+```
+
+The **macaddr** type also supports the standard relational operators (such as **&gt;** and **&lt;=**) for lexicographical ordering, and the bitwise arithmetic operators (**~**, **&** and **|**) for NOT, AND and OR.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/12-text-search-functions-and-operators.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/12-text-search-functions-and-operators.md
new file mode 100644
index 0000000000000000000000000000000000000000..17f1c95c2868769b7db9867c16240955cea7bb26
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/12-text-search-functions-and-operators.md
@@ -0,0 +1,535 @@
+---
+title: Text Search Functions and Operators
+summary: Text Search Functions and Operators
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Text Search Functions and Operators
+
+## Text Search Operators
+
+- @@
+
+  Description: Specifies whether the **tsvector**-type words match the **tsquery**-type words.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT to_tsvector('fat cats ate rats') @@ to_tsquery('cat & rat') AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- @@@
+
+  Description: Synonym for @@
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT to_tsvector('fat cats ate rats') @@@ to_tsquery('cat & rat') AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- ||
+
+  Description: Connects two **tsvector**-type words.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT 'a:1 b:2'::tsvector || 'c:1 d:2 b:3'::tsvector AS RESULT;
+            result
+  ---------------------------
+   'a':1 'b':2,5 'c':3 'd':4
+  (1 row)
+  ```
+
+- &&
+
+  Description: Performs an AND operation on two **tsquery**-type words.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT 'fat | rat'::tsquery && 'cat'::tsquery AS RESULT;
+            result
+  ---------------------------
+   ( 'fat' | 'rat' ) & 'cat'
+  (1 row)
+  ```
+
+- ||
+
+  Description: Performs an OR operation on two **tsquery**-type words.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT 'fat | rat'::tsquery || 'cat'::tsquery AS RESULT;
+            result
+  ---------------------------
+   ( 'fat' | 'rat' ) | 'cat'
+  (1 row)
+  ```
+
+- !!
+
+  Description:**NOT** a **tsquery**
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT !! 'cat'::tsquery AS RESULT;
+   result
+  --------
+   !'cat'
+  (1 row)
+  ```
+
+- @&gt;
+
+  Description: Specifies whether a **tsquery**-type word contains another **tsquery**-type word.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT 'cat'::tsquery @> 'cat & rat'::tsquery AS RESULT;
+   result
+  --------
+   f
+  (1 row)
+  ```
+
+- &lt;@
+
+  Description: Specifies whether a **tsquery**-type word is contained in another **tsquery**-type word.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT 'cat'::tsquery <@ 'cat & rat'::tsquery AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+In addition to the preceding operators, the ordinary B-tree comparison operators (including = and &lt;) are defined for types **tsvector** and **tsquery**.
+
+## Text Search Functions
+
+- get_current_ts_config()
+
+  Description: Obtains default text search configurations.
+
+  Return type: regconfig
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT get_current_ts_config();
+   get_current_ts_config
+  -----------------------
+   english
+  (1 row)
+  ```
+
+- length(tsvector)
+
+  Description: Specifies the number of lexemes in a  **tsvector**-type word.
+
+  Return type: integer
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT length('fat:2,4 cat:3 rat:5A'::tsvector);
+   length
+  --------
+        3
+  (1 row)
+  ```
+
+- numnode(tsquery)
+
+  Description: Specifies the number of lexemes plus  **tsquery**  operators.
+
+  Return type: integer
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT numnode('(fat & rat) | cat'::tsquery);
+   numnode
+  ---------
+         5
+  (1 row)
+  ```
+
+- plainto_tsquery([ config regconfig , ] query text)
+
+  Description: Generates **tsquery** lexemes without punctuations.
+
+  Return type: tsquery
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT plainto_tsquery('english', 'The Fat Rats');
+   plainto_tsquery
+  -----------------
+   'fat' & 'rat'
+  (1 row)
+  ```
+
+- querytree(query tsquery)
+
+  Description: Obtains the indexable part of a  **tsquery**.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT querytree('foo & ! bar'::tsquery);
+   querytree
+  -----------
+   'foo'
+  (1 row)
+  ```
+
+- setweight(tsvector, "char")
+
+  Description: Assigns weight to each element of **tsvector**.
+
+  Return type: tsvector
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT setweight('fat:2,4 cat:3 rat:5B'::tsvector, 'A');
+             setweight
+  -------------------------------
+   'cat':3A 'fat':2A,4A 'rat':5A
+  (1 row)
+  ```
+
+- strip(tsvector)
+
+  Description: Removes positions and weights from **tsvector**.
+
+  Return type: tsvector
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT strip('fat:2,4 cat:3 rat:5A'::tsvector);
+         strip
+  -------------------
+   'cat' 'fat' 'rat'
+  (1 row)
+  ```
+
+- to_tsquery([ config regconfig , ] query text)
+
+  Description: Normalizes words and converts them to **tsquery**.
+
+  Return type: tsquery
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT to_tsquery('english', 'The & Fat & Rats');
+    to_tsquery
+  ---------------
+   'fat' & 'rat'
+  (1 row)
+  ```
+
+- to_tsvector([ config regconfig , ] document text)
+
+  Description: Reduces document text to **tsvector**.
+
+  Return type: tsvector
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT to_tsvector('english', 'The Fat Rats');
+     to_tsvector
+  -----------------
+   'fat':2 'rat':3
+  (1 row)
+  ```
+
+- to_tsvector_for_batch([ config regconfig , ] document text)
+
+    Description: Reduces document text to  **tsvector**.
+
+    Return type: tsvector
+
+    Example:
+
+    ```sql
+    mogdb=# SELECT to_tsvector_for_batch('english', 'The Fat Rats');
+       to_tsvector
+    -----------------
+     'fat':2 'rat':3
+    (1 row)
+    ```
+
+- ts_headline([ config regconfig, ] document text, query tsquery [, options text ])
+
+  Description: Highlights a query match.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT ts_headline('x y z', 'z'::tsquery);
+   ts_headline
+  --------------
+   x y <b>z</b>
+  (1 row)
+  ```
+
+- ts_rank([ weights float4[], ] vector tsvector, query tsquery [, normalization integer ])
+
+  Description: Ranks documents for a query.
+
+  Return type: float4
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT ts_rank('hello world'::tsvector, 'world'::tsquery);
+   ts_rank
+  ----------
+   .0607927
+  (1 row)
+  ```
+
+- ts_rank_cd([ weights float4[], ] vector tsvector, query tsquery [, normalization integer ])
+
+  Description: Ranks documents for a query using cover density.
+
+  Return type: float4
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT ts_rank_cd('hello world'::tsvector, 'world'::tsquery);
+   ts_rank_cd
+  ------------
+            .1
+  (1 row)
+  ```
+
+- ts_rewrite(query tsquery, target tsquery, substitute tsquery)
+
+  Description: Replaces a  **tsquery**-type word.
+
+  Return type: tsquery
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT ts_rewrite('a & b'::tsquery, 'a'::tsquery, 'foo|bar'::tsquery);
+         ts_rewrite
+  -------------------------
+   'b' & ( 'foo' | 'bar' )
+  (1 row)
+  ```
+
+- ts_rewrite(query tsquery, select text)
+
+  Description: Replaces **tsquery** data in the target with the result of a **SELECT** command.
+
+  Return type: tsquery
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT ts_rewrite('world'::tsquery, 'select ''world''::tsquery, ''hello''::tsquery');
+   ts_rewrite
+  ------------
+   'hello'
+  (1 row)
+  ```
+
+## Text Search Debugging Functions
+
+- ts_debug([ config regconfig, ] document text, OUT alias text, OUT description text, OUT token text, OUT dictionaries regdictionary[], OUT dictionary regdictionary, OUT lexemes text[])
+
+  Description: Tests a configuration.
+
+  Return type: SETOF record
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT ts_debug('english', 'The Brightest supernovaes');
+                                       ts_debug
+  -----------------------------------------------------------------------------------
+   (asciiword,"Word, all ASCII",The,{english_stem},english_stem,{})
+   (blank,"Space symbols"," ",{},,)
+   (asciiword,"Word, all ASCII",Brightest,{english_stem},english_stem,{brightest})
+   (blank,"Space symbols"," ",{},,)
+   (asciiword,"Word, all ASCII",supernovaes,{english_stem},english_stem,{supernova})
+  (5 rows)
+  ```
+
+- ts_lexize(dict regdictionary, token text)
+
+  Description: Tests a data dictionary.
+
+  Return type: text[]
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT ts_lexize('english_stem', 'stars');
+   ts_lexize
+  -----------
+   {star}
+  (1 row)
+  ```
+
+- ts_parse(parser_name text, document text, OUT tokid integer, OUT token text)
+
+  Description: Tests a parser.
+
+  Return type: SETOF record
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT ts_parse('default', 'foo - bar');
+   ts_parse
+  -----------
+   (1,foo)
+   (12," ")
+   (12,"- ")
+   (1,bar)
+  (4 rows)
+  ```
+
+- ts_parse(parser_oid oid, document text, OUT tokid integer, OUT token text)
+
+  Description: Tests a parser.
+
+  Return type: SETOF record
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT ts_parse(3722, 'foo - bar');
+   ts_parse
+  -----------
+   (1,foo)
+   (12," ")
+   (12,"- ")
+   (1,bar)
+  (4 rows)
+  ```
+
+- ts_token_type(parser_name text, OUT tokid integer, OUT alias text, OUT description text)
+
+  Description: Obtains token types defined by a parser.
+
+  Return type: SETOF record
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT ts_token_type('default');
+                          ts_token_type
+  --------------------------------------------------------------
+   (1,asciiword,"Word, all ASCII")
+   (2,word,"Word, all letters")
+   (3,numword,"Word, letters and digits")
+   (4,email,"Email address")
+   (5,url,URL)
+   (6,host,Host)
+   (7,sfloat,"Scientific notation")
+   (8,version,"Version number")
+   (9,hword_numpart,"Hyphenated word part, letters and digits")
+   (10,hword_part,"Hyphenated word part, all letters")
+   (11,hword_asciipart,"Hyphenated word part, all ASCII")
+   (12,blank,"Space symbols")
+   (13,tag,"XML tag")
+   (14,protocol,"Protocol head")
+   (15,numhword,"Hyphenated word, letters and digits")
+   (16,asciihword,"Hyphenated word, all ASCII")
+   (17,hword,"Hyphenated word, all letters")
+   (18,url_path,"URL path")
+   (19,file,"File or path name")
+   (20,float,"Decimal notation")
+   (21,int,"Signed integer")
+   (22,uint,"Unsigned integer")
+   (23,entity,"XML entity")
+  (23 rows)
+  ```
+
+- ts_token_type(parser_oid oid, OUT tokid integer, OUT alias text, OUT description text)
+
+  Description: Obtains token types defined by a parser.
+
+  Return type: SETOF record
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT ts_token_type(3722);
+                          ts_token_type
+  --------------------------------------------------------------
+   (1,asciiword,"Word, all ASCII")
+   (2,word,"Word, all letters")
+   (3,numword,"Word, letters and digits")
+   (4,email,"Email address")
+   (5,url,URL)
+   (6,host,Host)
+   (7,sfloat,"Scientific notation")
+   (8,version,"Version number")
+   (9,hword_numpart,"Hyphenated word part, letters and digits")
+   (10,hword_part,"Hyphenated word part, all letters")
+   (11,hword_asciipart,"Hyphenated word part, all ASCII")
+   (12,blank,"Space symbols")
+   (13,tag,"XML tag")
+   (14,protocol,"Protocol head")
+   (15,numhword,"Hyphenated word, letters and digits")
+   (16,asciihword,"Hyphenated word, all ASCII")
+   (17,hword,"Hyphenated word, all letters")
+   (18,url_path,"URL path")
+   (19,file,"File or path name")
+   (20,float,"Decimal notation")
+   (21,int,"Signed integer")
+   (22,uint,"Unsigned integer")
+   (23,entity,"XML entity")
+  (23 rows)
+  ```
+
+- ts_stat(sqlquery text, [ weights text, ] OUT word text, OUT ndoc integer, OUT nentry integer)
+
+  Description: Obtains statistics of a  **tsvector**  column.
+
+  Return type: SETOF record
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT ts_stat('select ''hello world''::tsvector');
+     ts_stat
+  -------------
+   (world,1,1)
+   (hello,1,1)
+  (2 rows)
+  ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/13-json-functions.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/13-json-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..ede347d97562075f99234046e6b259efd67047ec
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/13-json-functions.md
@@ -0,0 +1,745 @@
+---
+title: JSON/JSONB Functions and Operators
+summary: JSON/JSONB Functions and Operators
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# JSON/JSONB Functions and Operators
+
+For details about the JSON/JSONB data type, see [JSON/JSONB Types](12-json-types).
+
+**Table 1** JSON/JSONB common operators
+
+| Operator | Left Operand Type  | Right Operand Type | Return Type | Description                                                  | Example                                          | Example Result |
+| :------- | :----------------- | :----------------- | :---------- | :----------------------------------------------------------- | :----------------------------------------------- | :------------- |
+| ->       | Array-json(b)      | int                | json(b)     | Obtains the **array-json** element. If the subscript does not exist, **NULL** is returned. | '[{"a":"foo"},{"b":"bar"},{"c":"baz"}]'::json->2 | {"c":"baz"}    |
+| ->       | object-json(b)     | text               | json(b)     | Obtains the value by a key. If no record is found, **NULL** is returned. | '{"a": {"b":"foo"}}'::json->'a'                  | {"b":"foo"}    |
+| ->>      | Array-json(b)      | int                | text        | Obtains the JSON array element. If the subscript does not exist, **NULL** is returned. | '[1,2,3]'::json->>2                              | 3              |
+| ->>      | object-json(b)     | text               | text        | Obtains the value by a key. If no record is found, **NULL** is returned. | '{"a":1,"b":2}'::json->>'b'                      | 2              |
+| #>       | container-json (b) | text[]             | json(b)     | Obtains the JSON object in the specified path. If the path does not exist, **NULL** is returned. | '{"a": {"b":{"c": "foo"}}}'::json #>'{a,b}'      | {"c": "foo"}   |
+| #>>      | container-json (b) | text[]             | text        | Obtains the JSON object in the specified path. If the path does not exist, **NULL** is returned. | '{"a":[1,2,3],"b":[4,5,6]}'::json #>>'{a,2}'     | 3              |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **CAUTION:** For the **#>** and **#>>** operators, if no data can be found in the specified path, no error is reported and a **NULL** value is returned.
+
+**Table 2** Additional JSONB support for operators
+
+| Operator | Right Operand Type | Description                                                  | Example                                            |
+| :------- | :----------------- | :----------------------------------------------------------- | :------------------------------------------------- |
+| @>       | jsonb              | Whether the top layer of the JSON on the left contains all items of the top layer of the JSON on the right. | '{"a":1, "b":2}'::jsonb @> '{"b":2}'::jsonb        |
+| <@       | jsonb              | Whether all items in the JSON file on the left exist at the top layer of the JSON file on the right. | '{"b":2}'::jsonb <@ '{"a":1, "b":2}'::jsonb        |
+| ?        | text               | Whether the string of the key or element exists at the top layer of the JSON value. | '{"a":1, "b":2}'::jsonb ? 'b'                      |
+| ?\|      | text[]             | Whether any of these array strings exists as top-layer keys. | '{"a":1, "b":2, "c":3}'::jsonb ?\| array['b', 'c'] |
+| ?&       | text[]             | Whether all these array strings exist as top-layer keys.     | '["a", "b"]'::jsonb ?& array['a', 'b']             |
+| =        | jsonb              | Determines the size between two **JSONB** files, which is the same as the **jsonb_eq** function. | /                                                  |
+| <>       | jsonb              | Determines the size between two **JSONB** files, which is the same as the **jsonb_ne** function. | /                                                  |
+| <        | jsonb              | Determines the size between two **JSONB** files, which is the same as the **jsonb_lt** function. | /                                                  |
+| >        | jsonb              | Determines the size between two **JSONB** files, which is the same as the **jsonb_gt** function. | /                                                  |
+| <=       | jsonb              | Determines the size between two **JSONB** files, which is the same as the **jsonb_le** function. | /                                                  |
+| >=       | jsonb              | Determines the size between two **JSONB** files, which is the same as the **jsonb_ge** function. | /                                                  |
+
+## **Functions Supported by JSON/JSONB**
+
+- array_to_json(anyarray [, pretty_bool])
+
+  Description: Returns an array as JSON. A multi-dimensional array becomes a JSON array of arrays. If the value of **pretty_bool** is **true**, a newline character is added between one-dimensional elements.
+
+  Return type: json
+
+  For example:
+
+  ```
+  mogdb=# SELECT array_to_json('{{1,5},{99,100}}'::int[]);
+      array_to_json
+      ------------------
+      [[1,5],[99,100]]
+      (1 row)
+  ```
+
+- row_to_json(record [, pretty_bool])
+
+  Description: Returns a row as JSON. If the value of **preretty_bool** is **true**, a newline character is added between one-dimensional elements.
+
+  Return type: json
+
+  For example:
+
+  ```
+  mogdb=# SELECT row_to_json(row(1,'foo'));
+           row_to_json
+      ---------------------
+       {"f1":1,"f2":"foo"}    (1 row)
+  ```
+
+- json_array_element(array-json, integer), jsonb_array_element(array-jsonb, integer)
+
+  Description: Same as the operator **`->`**, which returns the element with the specified subscript in the array.
+
+  Return type: json, jsonb
+
+  For example:
+
+  ```
+  mogdb=# select json_array_element('[1,true,[1,[2,3
+  ]],null]',2);
+    json_array_element
+    --------------------
+    [1,[2,3]]
+    (1 row)
+  ```
+
+- json_array_element_text(array-json, integer), jsonb_array_element_text(array-jsonb, integer)
+
+  Description: Same as the operator **`->>`**, which returns the element with the specified subscript in the array.
+
+  Return type: text, text
+
+  For example:
+
+  ```
+  mogdb=# select json_array_element_text('[1,true,[1,[2,3]],null]',2);
+  json_array_element_text
+  -----------------------
+    [1,[2,3]]
+    (1 row)
+  ```
+
+- json_object_field(object-json, text), jsonb_object_field(object-jsonb, text)
+
+  Description: Same as the operator **`->`**, which returns the value of a specified key in an object.
+
+  Return type: json, json
+
+  For example:
+
+  ```
+  mogdb=# select json_object_field('{"a": {"b":"foo"}}','a');
+   json_object_field
+   -------------------
+   {"b":"foo"}
+   (1 row)
+  ```
+
+- json_object_field_text(object-json, text), jsonb_object_field_text(object-jsonb, text)
+
+  Description: Same as the operator **`->`**, which returns the value of a specified key in an object.
+
+  Return type: text, text
+
+  For example:
+
+  ```
+  mogdb=# select json_object_field_text('{"a": {"b":"foo"}}','a');
+   json_object_field_text
+   ----------------------
+   {"b":"foo"}
+   (1 row)
+  ```
+
+- json_extract_path(json, VARIADIC text[]), jsonb_extract_path((jsonb, VARIADIC text[])
+
+  Description: Equivalent to the operator **`#>`** searches for JSON based on the path specified by *$2* and returns the result.
+
+  Return type: json, jsonb
+
+  For example:
+
+  ```
+  mogdb=# select json_extract_path('{"f2":{"f3":1},"f4":{"f5":99,"f6":"stringy"}}', 'f4','f6');
+    json_extract_path
+   -------------------
+    "stringy"
+   (1 row)
+  ```
+
+- json_extract_path_op(json, text[]), jsonb_extract_path_op(jsonb, text[])
+
+  Description: Same as the operator **`#>`**, searches for JSON based on the path specified by *$2* and returns the result.
+
+  Return type: json, jsonb
+
+  For example:
+
+  ```
+  mogdb=# select json_extract_path_op('{"f2":{"f3":1},"f4":{"f5":99,"f6":"stringy"}}', 'f4','f6');
+    json_extract_path_op
+   ---------------------
+    "stringy"
+   (1 row)
+  ```
+
+- json_extract_path_text(json, VARIADIC text[]), jsonb_extract_path_text((jsonb, VARIADIC text[])
+
+  Description: Equivalent to the operator **`#>`**, searches for JSON based on the path specified by $2 and return the result.
+
+  Return type: text, text
+
+  For example:
+
+  ```
+  mogdb=# select json_extract_path_text('{"f2":{"f3":1},"f4":{"f5":99,"f6":"stringy"}}', 'f4','f6');
+    json_extract_path_text
+   -----------------------
+    "stringy"
+   (1 row)
+  ```
+
+- json_extract_path_text_op(json, text[]), jsonb_extract_path_text_op(jsonb, text[])
+
+  Description: Same as the operator **`#>`**, searches for JSON based on the path specified by *$2* and returns the result.
+
+  Return type: text, text
+
+  For example:
+
+  ```
+  mogdb=# select json_extract_path_text_op('{"f2":{"f3":1},"f4":{"f5":99,"f6":"stringy"}}', 'f4','f6');
+    json_extract_path_text_op
+   --------------------------
+    "stringy"
+   (1 row)
+  ```
+
+- Json_array_elements(array-json), jsonb_array_elements(array-jsonb)
+
+  Description: Splits an array. Each element returns a row.
+
+  Return type: json, jsonb
+
+  For example:
+
+  ```
+  mogdb=# select json_array_elements('[1,true,[1,[2,3]],null]');
+    json_array_elements
+   ---------------------
+    1
+    true
+    [1,[2,3]]
+    null
+   (4 rows)
+  ```
+
+- Json_array_elements_text(array-json), jsonb_array_elements_text(array-jsonb)
+
+  Description: Splits an array. Each element returns a row.
+
+  Return type: text, text
+
+  For example:
+
+  ```
+  mogdb=# select * from  json_array_elements_text('[1,true,[1,[2,3]],null]');
+       value
+    -----------
+     1
+     true
+     [1,[2,3]]
+
+    (4 rows)
+  ```
+
+- json_array_length(array-json), jsonb_array_length(array-jsonb)
+
+  Description: Returns the array length.
+
+  Return type: integer
+
+  For example:
+
+  ```
+  mogdb=# SELECT json_array_length('[1,2,3,{"f1":1,"f2":[5,6]},4,null]');
+    json_array_length
+   -------------------
+                    6
+   (1 row)
+  ```
+
+- json_each(object-json), jsonb_each(object-jsonb)
+
+  Description: Splits each key-value pair of an object into one row and two columns.
+
+  Return type: setof(key text, value json), setof(key text, value jsonb)
+
+  For example:
+
+  ```
+  mogdb=# select * from  json_each('{"f1":[1,2,3],"f2":{"f3":1},"f4":null}');
+    key |  value
+   -----+----------
+    f1  | [1,2,3]
+    f2  | {"f3":1}
+    f4  | null
+   (3 rows)
+  ```
+
+- json_each_text(object-json), jsonb_each_text(object-jsonb)
+
+  Description: Splits each key-value pair of an object into one row and two columns.
+
+  Return type: setof(key text, value text), setof(key text, value text)
+
+  For example:
+
+  ```
+  mogdb=# select * from  json_each_text('{"f1":[1,2,3],"f2":{"f3":1},"f4":null}');
+    key |  value
+   -----+----------
+    f1  | [1,2,3]
+    f2  | {"f3":1}
+    f4  |
+   (3 rows)
+  ```
+
+- json_object_keys(object-json), jsonb_object_keys(object-jsonb)
+
+  Description: Returns all keys at the top layer of the object.
+
+  Return type: SETOF text
+
+  For example:
+
+  ```
+  mogdb=# select json_object_keys('{"f1":"abc","f2":{"f3":"a", "f4":"b"}, "f1":"abcd"}');
+    json_object_keys
+   ------------------
+    f1
+    f2
+    f1
+   (3 rows)
+  ```
+
+- JSONB deduplication operations:
+
+  ```
+  mogdb=# select jsonb_object_keys('{"f1":"abc","f2":{"f3":"a", "f4":"b"}, "f1":"abcd"}');
+    jsonb_object_keys
+   -------------------
+    f1
+    f2
+   (2 rows)
+  ```
+
+- json_populate_record(anyelement, object-json [, bool]), jsonb_populate_record(anyelement, object-jsonb [, bool])
+
+  Description: *$1* must be a compound parameter. Each key-value in the **object-json** file is split. The key is used as the column name to match the column name in *$1* and fill in the *$1* format.
+
+  Return type: anyelement, anyelement
+
+  For example:
+
+  ```
+  mogdb=# create type jpop as (a text, b int, c bool);
+   CREATE TYPE
+   postgres=# select * from json_populate_record(null::jpop,'{"a":"blurfl","x":43.2}');
+      a    | b | c
+   --------+---+---
+    blurfl |   |
+   (1 row)
+  ```
+
+  ```
+  mogdb=# select * from json_populate_record((1,1,null)::jpop,'{"a":"blurfl","x":43.2}');
+       a    | b | c
+    --------+---+---
+     blurfl | 1 |
+    (1 row)
+  ```
+
+- json_populate_record_set(anyelement, array-json [, bool]), jsonb_populate_record_set(anyelement, array-jsonb [, bool])
+
+  Description: Performs the preceding operations on each element in the *$2* array by referring to the **json_populate_record** and **jsonb_populate_record** functions. Therefore, each element in the *$2* array must be of the **object-json** type.
+
+  Return type: setof anyelement, setof anyelement
+
+  For example:
+
+  ```
+  mogdb=# create type jpop as (a text, b int, c bool);
+   CREATE TYPE
+   postgres=# select * from json_populate_recordset(null::jpop, '[{"a":1,"b":2},{"a":3,"b":4}]');
+    a | b | c
+   ---+---+---
+    1 | 2 |
+    3 | 4 |
+   (2 rows)
+  ```
+
+- json_typeof(json), jsonb_typeof(jsonb)
+
+  Description: Checks the JSON type.
+
+  Return type: text, text
+
+  For example:
+
+  ```
+  mogdb=# select value, json_typeof(value)
+   postgres-# from (values (json '123.4'), (json '"foo"'), (json 'true'), (json 'null'), (json '[1, 2, 3]'), (json '{"x":"foo", "y":123}'), (NULL::json))  as data(value);
+           value         | json_typeof
+   ----------------------+-------------
+    123.4                | number
+    "foo"                | string
+    true                 | boolean
+    null                 | null
+    [1, 2, 3]            | array
+    {"x":"foo", "y":123} | object
+                         |
+   (7 rows)
+  ```
+
+- json_build_array( [VARIADIC "any"] )
+
+  Description: Constructs a JSON array from a variable parameter list.
+
+  Return type: array-json
+
+  For example:
+
+  ```
+  mogdb=# select json_build_array('a',1,'b',1.2,'c',true,'d',null,'e',json '{"x": 3, "y": [1,2,3]}','');
+                                json_build_array
+   ---------------------------------------------------------------------------
+    ["a", 1, "b", 1.2, "c", true, "d", null, "e", {"x": 3, "y": [1,2,3]}, ""]
+   (1 row)
+  ```
+
+- json_build_object( [VARIADIC "any"] )
+
+  Description: Constructs a JSON object from a variable parameter list. The number of input parameters must be an even number. Every two input parameters form a key-value pair. Note that the value of a key cannot be null.
+
+  Return type: object-json
+
+  For example:
+
+  ```
+  mogdb=# select json_build_object(1,2);
+    json_build_object
+   -------------------
+    {"1" : 2}
+   (1 row)
+  ```
+
+- json_to_record(object-json, bool)
+
+  Description: Like all functions that return **record**, the caller must explicitly define the structure of the record with an AS clause. The key-value pair of **object-json** is split and reassembled. The key is used as a column name to match and fill in the structure of the specified record.
+
+  Return type: record
+
+  For example:
+
+  ```
+  mogdb=# select * from json_to_record('{"a":1,"b":"foo","c":"bar"}',true) as x(a int, b text, d text);
+     a |  b  | d
+    ---+-----+---
+     1 | foo |
+    (1 row)
+  ```
+
+- json_to_recordset(array-json, bool)
+
+  Description: Executes the preceding function on each element in the array by referring to the**json_to_record** function. Therefore, each element in the array must be **object-json**.
+
+  Return type: SETOF record
+
+  For example:
+
+  ```
+  mogdb=# select * from json_to_recordset(
+  mogdb(#   '[{"a":1,"b":"foo","d":false},{"a":2,"b":"bar","c":true}]',
+  mogdb(#   false
+  mogdb(# ) as x(a int, b text, c boolean);
+    a |  b  | c
+   ---+-----+---
+    1 | foo |
+    2 | bar | t
+   (2 rows)
+  ```
+
+- json_object(text[]), json_object(text[], text[])
+
+  Description: Constructs an **object-json** from a text array. This is an overloaded function. When the input parameter is a text array, the array length must be an even number, and members are considered as alternate key-value pairs. When two text arrays are used, the first array is considered as a key, and the second array a value. The lengths of the two arrays must be the same. Note that the value of a key cannot be null.
+
+  Return type: object-json
+
+  For example:
+
+  ```
+  mogdb=# select json_object('{a,1,b,2,3,NULL,"d e f","a b c"}');
+                          json_object
+    -------------------------------------------------------
+     {"a" : "1", "b" : "2", "3" : null, "d e f" : "a b c"}
+    (1 row)
+  ```
+
+  ```
+  mogdb=# select json_object('{a,b,"a b c"}', '{a,1,1}');
+                 json_object
+   ---------------------------------------
+    {"a" : "a", "b" : "1", "a b c" : "1"}
+   (1 row)
+  ```
+
+- json_agg(any)
+
+  Description: Aggregates values into a JSON array.
+
+  Return type: array-json
+
+  For example:
+
+  ```
+  mogdb=# select * from classes;
+   name | score
+   -----+-------
+   A    |     2
+   A    |     3
+   D    |     5
+   D    |
+   (4 rows)
+  ```
+
+  ```
+  mogdb=# select name, json_agg(score) score from classes group by name order by name;
+   name |      score
+   -----+-----------------
+   A    | [2, 3]
+   D    | [5, null]
+        | [null]
+   (3 rows)
+  ```
+
+- json_object_agg(any, any)
+
+  Description: Aggregates values into a JSON object.
+
+  Return type: object-json
+
+  For example:
+
+  ```
+  mogdb=# select * from classes;
+   name | score
+   -----+-------
+   A    |     2
+   A    |     3
+   D    |     5
+   D    |
+   (4 rows)
+  ```
+
+  ```
+  mogdb=# select json_object_agg(name, score) from classes group by name order by name;
+        json_object_agg
+   -------------------------
+    { "A" : 2, "A" : 3 }
+    { "D" : 5, "D" : null }
+   (2 rows)
+  ```
+
+- jsonb_contained(jsonb, jsonb)
+
+  Description: Same as the operator **`<@`**, determines whether all elements in_$1_ exist at the top layer of *$2*.
+
+  Return type: Boolean
+
+  For example:
+
+  ```
+  mogdb=# select jsonb_contained('[1,2,3]', '[1,2,3,4]');
+    jsonb_contained
+   -----------------
+    t
+   (1 row)
+  ```
+
+- jsonb_contains(jsonb, jsonb)
+
+  Description: Same as the operator **`@>`**, checks whether all top-layer elements in *$1* are contained in *$2*.
+
+  Return type: Boolean
+
+  For example:
+
+  ```
+  mogdb=# select jsonb_contains('[1,2,3,4]', '[1,2,3]');
+    jsonb_contains
+   ----------------
+    t
+   (1 row)
+  ```
+
+- jsonb_exists(jsonb, text)
+
+  Description: Same as the operator **`?`**, determines whether all elements in the string array *$2* exist at the top layer of *$1* in the form of **key,elem,scalar**.
+
+  Return type: Boolean
+
+  For example:
+
+  ```
+  mogdb=# select jsonb_exists('["1",2,3]', '1');
+    jsonb_exists
+   --------------
+    t
+   (1 row)
+  ```
+
+- jsonb_exists_all(jsonb, text[])
+
+  Description: Same as the operator **`?&`**, checks whether all elements in the string array *$2* exist at the top layer of *$1* in the form of **key,elem,scalar**.
+
+  Return type: Boolean
+
+  For example:
+
+  ```
+  mogdb=# select jsonb_exists_all('["1","2",3]', '{1, 2}');
+    jsonb_exists_all
+   ------------------
+    t
+   (1 row)
+  ```
+
+- jsonb_exists_any(jsonb, text[])
+
+  Description: Same as the operator **`?|`**, checks whether all elements in the string array *$2* exist at the top layer of *$1* in the form of **key,elem,scalar**.
+
+  Return type: Boolean
+
+  For example:
+
+  ```
+  mogdb=# select jsonb_exists_any('["1","2",3]', '{1, 2, 4}');
+    jsonb_exists_any
+   ------------------
+    t
+   (1 row)
+  ```
+
+- jsonb_cmp(jsonb, jsonb)
+
+  Description: Compares values. A positive value indicates greater than, a negative value indicates less than, and **0** indicates equal.
+
+  Return type: integer
+
+  For example:
+
+  ```
+  mogdb=# select jsonb_cmp('["a", "b"]', '{"a":1, "b":2}');
+     jsonb_cmp
+    -----------
+            -1
+    (1 row)
+  ```
+
+- jsonb_eq(jsonb, jsonb)
+
+  Description: Same as the operator **`=`**, compares two values.
+
+  Return type: Boolean
+
+  For example:
+
+  ```
+  mogdb=# select jsonb_eq('["a", "b"]', '{"a":1, "b":2}');
+    jsonb_eq
+   ----------
+    f
+   (1 row)
+  ```
+
+- jsonb_ne(jsonb, jsonb)
+
+  Description: Same as the operator **`<>`**, compares two values.
+
+  Return type: Boolean
+
+  For example:
+
+  ```
+  mogdb=# select jsonb_ne('["a", "b"]', '{"a":1, "b":2}');
+    jsonb_ne
+   ----------
+    t
+   (1 row)
+  ```
+
+- jsonb_gt(jsonb, jsonb)
+
+  Description: Same as the operator **`>`**, compares two values.
+
+  Return type: Boolean
+
+  For example:
+
+  ```
+  mogdb=# select jsonb_gt('["a", "b"]', '{"a":1, "b":2}');
+    jsonb_gt
+   ----------
+    f
+   (1 row)
+  ```
+
+- jsonb_ge(jsonb, jsonb)
+
+  Description: Same as the operator **`>=`**, compares two values.
+
+  Return type: Boolean
+
+  For example:
+
+  ```
+  mogdb=# select jsonb_ge('["a", "b"]', '{"a":1, "b":2}');
+    jsonb_ge
+   ----------
+    f
+   (1 row)
+  ```
+
+- jsonb_lt(jsonb, jsonb)
+
+  Description: Same as the operator **`<`**, compares two values.
+
+  Return type: Boolean
+
+  For example:
+
+  ```
+  mogdb=# select jsonb_lt('["a", "b"]', '{"a":1, "b":2}');
+    jsonb_lt
+   ----------
+    t
+   (1 row)
+  ```
+
+- jsonb_le(jsonb, jsonb)
+
+  Description: Same as the operator **`<=`**, compares two values.
+
+  Return type: Boolean
+
+  For example:
+
+  ```
+  mogdb=# select jsonb_le('["a", "b"]', '{"a":1, "b":2}');
+    jsonb_le
+   ----------
+    t
+   (1 row)
+  ```
+
+- to_json(anyelement)
+
+  Description: Converts parameters to **`json`**.
+
+  Return type: json
+
+  For example:
+
+  ```
+  mogdb=# select to_json('{1,5}'::text[]);
+     to_json
+   -----------
+    ["1","5"]
+   (1 row)
+  ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/13.1-hll-functions-and-operators.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/13.1-hll-functions-and-operators.md
new file mode 100644
index 0000000000000000000000000000000000000000..109af60858e693dd009ae28dd7d1595c834ee4b7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/13.1-hll-functions-and-operators.md
@@ -0,0 +1,876 @@
+---
+title: HLL Functions and Operators
+summary: HLL Functions and Operators
+author: Zhang Cuiping
+date: 2021-06-15
+---
+
+# HLL Functions and Operators
+
+## Hash Functions
+
+- hll_hash_boolean(bool)
+
+  Description: Hashes data of the Boolean type.
+
+  Return type: hll_hashval
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT hll_hash_boolean(FALSE);
+    hll_hash_boolean
+  ---------------------
+   -5451962507482445012
+  (1 row)
+  ```
+
+- hll_hash_boolean(bool, int32)
+
+  Description: Configures a hash seed (that is, change the hash policy) and hashes data of the bool type.
+
+  Return type: hll_hashval
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT hll_hash_boolean(FALSE, 10);
+    hll_hash_boolean
+  --------------------
+   -1169037589280886076
+  (1 row)
+  ```
+
+- hll_hash_smallint(smallint)
+
+  Description: Hashes data of the smallint type.
+
+  Return type: hll_hashval
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT hll_hash_smallint(100::smallint);
+    hll_hash_smallint
+  ---------------------
+   962727970174027904
+  (1 row)
+  ```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** If parameters with the same numeric value are hashed using different data types, the data will differ, because hash functions select different calculation policies for each type.
+
+- hll_hash_smallint(smallint, int32)
+
+  Description: Configures a hash seed (that is, change the hash policy) and hashes data of the smallint type.
+
+  Return type: hll_hashval
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT hll_hash_smallint(100::smallint, 10);
+    hll_hash_smallint
+  ---------------------
+   -9056177146160443041
+  (1 row)
+  ```
+
+- hll_hash_integer(integer)
+
+  Description: Hashes data of the integer type.
+
+  Return type: hll_hashval
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT hll_hash_integer(0);
+     hll_hash_integer
+  ----------------------
+   5156626420896634997
+  (1 row)
+  ```
+
+- hll_hash_integer(integer, int32)
+
+  Description: Hashes data of the integer type and configures a hash seed (that is, change the hash policy).
+
+  Return type: hll_hashval
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT hll_hash_integer(0, 10);
+    hll_hash_integer
+  --------------------
+   -5035020264353794276
+  (1 row)
+  ```
+
+- hll_hash_bigint(bigint)
+
+  Description: Hashes data of the bigint type.
+
+  Return type: hll_hashval
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT hll_hash_bigint(100::bigint);
+     hll_hash_bigint
+  ---------------------
+   -2401963681423227794
+  (1 row)
+  ```
+
+- hll_hash_bigint(bigint, int32)
+
+  Description: Hashes data of the bigint type and configures a hash seed (that is, change the hash policy).
+
+  Return type: hll_hashval
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT hll_hash_bigint(100::bigint, 10);
+     hll_hash_bigint
+  ---------------------
+   -2305749404374433531
+  (1 row)
+  ```
+
+- hll_hash_bytea(bytea)
+
+  Description: Hashes data of the bytea type.
+
+  Return type: hll_hashval
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT hll_hash_bytea(E'\\x');
+   hll_hash_bytea
+  ----------------
+   0
+  (1 row)
+  ```
+
+- hll_hash_bytea(bytea, int32)
+
+  Description: Hashes data of the bytea type and configures a hash seed (that is, change the hash policy).
+
+  Return type: hll_hashval
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT hll_hash_bytea(E'\\x', 10);
+     hll_hash_bytea
+  ---------------------
+   7233188113542599437
+  (1 row)
+  ```
+
+- hll_hash_text(text)
+
+  Description: Hashes data of the text type.
+
+  Return type: hll_hashval
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT hll_hash_text('AB');
+      hll_hash_text
+  ---------------------
+   -5666002586880275174
+  (1 row)
+  ```
+
+- hll_hash_text(text, int32)
+
+  Description: Hashes data of the text type and configures a hash seed (that is, change the hash policy).
+
+  Return type: hll_hashval
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT hll_hash_text('AB', 10);
+  hll_hash_text
+  ---------------------
+  -2215507121143724132
+  (1 row)
+  ```
+
+- hll_hash_any(anytype)
+
+  Description: Hashes data of any type.
+
+  Return type: hll_hashval
+
+  Example:
+
+  ```sql
+  mogdb=# select hll_hash_any(1);
+       hll_hash_any
+  ----------------------
+   -1316670585935156930
+  (1 row)
+
+  mogdb=# select hll_hash_any('08:00:2b:01:02:03'::macaddr);
+       hll_hash_any
+  ----------------------
+   -3719950434455589360
+  (1 row)
+  ```
+
+- hll_hash_any(anytype, int32)
+
+  Description: Hashes data of any type and configures a hash seed (that is, change the hash policy).
+
+  Return type: hll_hashval
+
+  Example:
+
+  ```sql
+  mogdb=# select hll_hash_any(1, 10);
+       hll_hash_any
+  ----------------------
+   7048553517657992351
+  (1 row)
+  ```
+
+- hll_hashval_eq(hll_hashval, hll_hashval)
+
+  Description: Compares two pieces of data of the **hll_hashval** type to check whether they are the same.
+
+  Return type: Boolean
+
+  Example:
+
+  ```sql
+  mogdb=# select hll_hashval_eq(hll_hash_integer(1), hll_hash_integer(1));
+   hll_hashval_eq
+  ----------------
+   t
+  (1 row)
+  ```
+
+- hll_hashval_ne(hll_hashval, hll_hashval)
+
+  Description: Compares two pieces of data of the **hll_hashval** type to check whether they are different.
+
+  Return type: Boolean
+
+  Example:
+
+  ```sql
+  mogdb=# select hll_hashval_ne(hll_hash_integer(1), hll_hash_integer(1));
+   hll_hashval_ne
+  ----------------
+   f
+  (1 row)
+  ```
+
+## HLL Functions
+
+There are three HLL modes: explicit, sparse, and full. When the data size is small, the explicit mode is used. In this mode, distinct values are calculated without errors. As the number of distinct values increases, the HLL mode is switched to the sparse and full modes in sequence. The two modes have no difference in the calculation result, but vary in the calculation efficiency of HLL functions and the storage space of HLL objects. The following functions can be used to view some HLL parameters:
+
+- hll_print(hll)
+
+  Description: Prints some debugging parameters of an HLL.
+
+  Example:
+
+  ```sql
+  mogdb=# select hll_print(hll_empty());
+                                     hll_print
+  -------------------------------------------------------------------------------
+   type=1(HLL_EMPTY), log2m=14, log2explicit=10, log2sparse=12, duplicatecheck=0
+  (1 row)
+  ```
+
+- hll_type(hll)
+
+  Description: Checks the type of the current HLL. The return values are described as follows: **0** indicates **HLL_UNINIT**, an HLL object that is not initialized. **1** indicates **HLL_EMPTY**, an empty HLL object. **2** indicates **HLL_EXPLICIT**, an HLL object in explicit mode. **3** indicates **HLL_SPARSE**, an HLL object in sparse mode. **4** indicates **HLL_FULL**, an HLL object in full mode. **5** indicates **HLL_UNDEFINED**, an invalid HLL object.
+
+  Example:
+
+  ```sql
+  mogdb=# select hll_type(hll_empty());
+   hll_type
+  ----------
+          1
+  (1 row)
+  ```
+
+- hll_log2m(hll)
+
+  Description: Checks the value of **log2m** in the current HLL data structure. **log2m** is the logarithm of the number of buckets. This value affects the error rate of calculating distinct values by HLL. The error rate = ±1.04/√(2^log2m). If the value of **log2m** ranges from 10 to 16, HLL sets the number of buckets to 2log2m. When the value of **log2explicit** is explicitly set to **-1**, the built-in default value is used.
+
+  Example:
+
+  ```sql
+  mogdb=# select hll_log2m(hll_empty());
+   hll_log2m
+  -----------
+          14
+  (1 row)
+
+  mogdb=# select hll_log2m(hll_empty(10));
+   hll_log2m
+  -----------
+          10
+  (1 row)
+
+  mogdb=# select hll_log2m(hll_empty(-1));
+   hll_log2m
+  -----------
+          14
+  (1 row)
+  ```
+
+- hll_log2explicit(hll)
+
+  Description: Queries the **log2explicit** value in the current HLL data structure. Generally, the HLL changes from the explicit mode to the sparse mode and then to the full mode. This process is called the promotion hierarchy policy. You can change the value of **log2explicit** to change the policy. For example, if **log2explicit** is set to **0**, an HLL will skip the explicit mode and directly enter the sparse mode. When the value of **log2explicit** is explicitly set to a value ranging from 1 to 12, HLL will switch to the sparse mode when the length of the data segment exceeds 2log2explicit. When the value of **log2explicit** is explicitly set to **-1**, the built-in default value is used.
+
+  Example:
+
+  ```sql
+  mogdb=# select hll_log2explicit(hll_empty());
+   hll_log2explicit
+  ------------------
+                 10
+  (1 row)
+
+  mogdb=# select hll_log2explicit(hll_empty(12, 8));
+   hll_log2explicit
+  ------------------
+                  8
+  (1 row)
+
+  mogdb=# select hll_log2explicit(hll_empty(12, -1));
+   hll_log2explicit
+  ------------------
+                 10
+  (1 row)
+  ```
+
+- hll_log2sparse(hll)
+
+  Description: Queries the value of **log2sparse** in the current HLL data structure. Generally, the HLL changes from the explicit mode to the sparse mode and then to the full mode. This process is called the promotion hierarchy policy. You can adjust the value of **log2sparse** to change the policy. For example, if the value of **log2sparse** is **0**, the system skips the sparse mode and directly enters the full mode. If the value of **log2sparse** is explicitly set to a value ranging from 1 to 14, HLL will switch to the full mode when the length of the data segment exceeds 2log2sparse. When the value of **log2sparse** is explicitly set to **-1**, the built-in default value is used.
+
+  Example:
+
+  ```sql
+  mogdb=# select hll_log2sparse(hll_empty());
+   hll_log2sparse
+  ----------------
+               12
+  (1 row)
+
+  mogdb=# select hll_log2sparse(hll_empty(12, 8, 10));
+   hll_log2sparse
+  ----------------
+               10
+  (1 row)
+
+  mogdb=# select hll_log2sparse(hll_empty(12, 8, -1));
+   hll_log2sparse
+  ----------------
+               12
+  (1 row)
+  ```
+
+- hll_duplicatecheck(hll)
+
+  Description: Specifies whether duplicate check is enabled. The value **0** indicates that it is disabled and the value **1** indicates that it is enabled. This function is disabled by default. If there are many duplicate values, you can enable this function to improve efficiency. When the value of **duplicatecheck** is explicitly set to **-1**, the built-in default value is used.
+
+  Example:
+
+  ```sql
+  mogdb=# select hll_duplicatecheck(hll_empty());
+   hll_duplicatecheck
+  --------------------
+                    0
+  (1 row)
+
+  mogdb=# select hll_duplicatecheck(hll_empty(12, 8, 10, 1));
+   hll_duplicatecheck
+  --------------------
+                    1
+  (1 row)
+
+  mogdb=# select hll_duplicatecheck(hll_empty(12, 8, 10, -1));
+   hll_duplicatecheck
+  --------------------
+                    0
+  (1 row)
+  ```
+
+## Functional Functions
+
+- hll_empty()
+
+  Description: Creates an empty HLL.
+
+  Return type: hll
+
+  Example:
+
+  ```sql
+  mogdb=# select hll_empty();
+                           hll_empty
+  ------------------------------------------------------------
+   \x484c4c00000000002b05000000000000000000000000000000000000
+  (1 row)
+  ```
+
+- hll_empty(int32 log2m)
+
+  Description: Creates an empty HLL and sets the **log2m** parameter. The parameter value ranges from 10 to 16. If the input is **-1**, the built-in default value is used.
+
+  Return type: HLL
+
+  Example:
+
+  ```sql
+  mogdb=# select hll_empty(10);
+                           hll_empty
+  ------------------------------------------------------------
+   \x484c4c00000000002b04000000000000000000000000000000000000
+  (1 row)
+
+  mogdb=# select hll_empty(-1);
+                           hll_empty
+  ------------------------------------------------------------
+   \x484c4c00000000002b05000000000000000000000000000000000000
+  (1 row)
+  ```
+
+- hll_empty(int32 log2m, int32 log2explicit)
+
+  Description: Creates an empty HLL and sets the **log2m** and **log2explicit** parameters in sequence. The value of **log2explicit** ranges from 0 to 12. The value **0** indicates that the explicit mode is skipped. This parameter is used to set the threshold of the explicit mode. When the length of the data segment reaches 2log2explicit, the mode is switched to the sparse or full mode. If the input is **-1**, the built-in default value of **log2explicit** is used.
+
+  Return type: HLL
+
+  Example:
+
+  ```sql
+  mogdb=# select hll_empty(10, 4);
+                           hll_empty
+  ------------------------------------------------------------
+   \x484c4c00000000001304000000000000000000000000000000000000
+  (1 row)
+
+  mogdb=# select hll_empty(10, -1);
+                           hll_empty
+  ------------------------------------------------------------
+   \x484c4c00000000002b04000000000000000000000000000000000000
+  (1 row)
+  ```
+
+- hll_empty(int32 log2m, int32 log2explicit, int64 log2sparse)
+
+  Description: Creates an empty HLL and sets the **log2m**, **log2explicit** and **log2sparse** parameters in sequence. The value of **log2sparse** ranges from 0 to 14. The value **0** indicates that the sparse mode is skipped. This parameter is used to set the threshold of the sparse mode. When the length of the data segment reaches 2log2sparse, the mode is switched to the full mode. If the input is **-1**, the built-in default value of **log2sparse** is used.
+
+  Return type: HLL
+
+  Example:
+
+  ```sql
+  mogdb=# select hll_empty(10, 4, 8);
+                           hll_empty
+  ------------------------------------------------------------
+   \x484c4c00000000001204000000000000000000000000000000000000
+  (1 row)
+
+  mogdb=# select hll_empty(10, 4, -1);
+                           hll_empty
+  ------------------------------------------------------------
+   \x484c4c00000000001304000000000000000000000000000000000000
+  (1 row)
+  ```
+
+- hll_empty(int32 log2m, int32 log2explicit, int64 log2sparse, int32 duplicatecheck)
+
+  Description: Creates an empty HLL and sets the **log2m**, **log2explicit**, **log2sparse**, and **duplicatecheck** parameters in sequence. The value of **duplicatecheck** is **0** or **1**, indicating whether the duplicate check mode is enabled. By default, this mode is disabled. If the input is **-1**, the built-in default value of **duplicatecheck** is used.
+
+  Return type: HLL
+
+  Example:
+
+  ```sql
+  mogdb=# select hll_empty(10, 4, 8, 0);
+                           hll_empty
+  ------------------------------------------------------------
+   \x484c4c00000000001204000000000000000000000000000000000000
+  (1 row)
+
+  mogdb=# select hll_empty(10, 4, 8, -1);
+                           hll_empty
+  ------------------------------------------------------------
+   \x484c4c00000000001204000000000000000000000000000000000000
+  (1 row)
+  ```
+
+- hll_add(hll, hll_hashval)
+
+  Description: Adds **hll_hashval** to an HLL.
+
+  Return type: HLL
+
+  Example:
+
+  ```sql
+  mogdb=# select hll_add(hll_empty(), hll_hash_integer(1));
+                                    hll_add
+  ----------------------------------------------------------------------------
+   \x484c4c08000002002b0900000000000000f03f3e2921ff133fbaed3e2921ff133fbaed00
+  (1 row)
+  ```
+
+- hll_add_rev(hll_hashval, hll)
+
+  Description: Adds **hll_hashval** to an HLL. This function works the same as **hll_add**, except that the positions of parameters are switched.
+
+  Return type: HLL
+
+  Example:
+
+  ```sql
+  mogdb=# select hll_add_rev(hll_hash_integer(1), hll_empty());
+                                  hll_add_rev
+  ----------------------------------------------------------------------------
+   \x484c4c08000002002b0900000000000000f03f3e2921ff133fbaed3e2921ff133fbaed00
+  (1 row)
+  ```
+
+- hll_eq(hll, hll)
+
+  Description: Compares two HLLs to check whether they are the same.
+
+  Return type: Boolean
+
+  Example:
+
+  ```sql
+  mogdb=# select hll_eq(hll_add(hll_empty(), hll_hash_integer(1)), hll_add(hll_empty(), hll_hash_integer(2)));
+   hll_eq
+  --------
+   f
+  (1 row)
+  ```
+
+- hll_ne(hll, hll)
+
+  Description: Compares two HLLs to check whether they are different.
+
+  Return type: Boolean
+
+  Example:
+
+  ```sql
+  mogdb=# select hll_ne(hll_add(hll_empty(), hll_hash_integer(1)), hll_add(hll_empty(), hll_hash_integer(2)));
+   hll_ne
+  --------
+   t
+  (1 row)
+  ```
+
+- hll_cardinality(hll)
+
+  Description: Calculates the number of distinct values of an HLL.
+
+  Return type: int
+
+  Example:
+
+  ```sql
+  mogdb=# select hll_cardinality(hll_empty() || hll_hash_integer(1));
+   hll_cardinality
+  -----------------
+                 1
+  (1 row)
+  ```
+
+- hll_union(hll, hll)
+
+  Description: Performs an UNION operation on two HLL data structures to obtain one HLL.
+
+  Return type: HLL
+
+  Example:
+
+  ```sql
+  mogdb=# select hll_union(hll_add(hll_empty(), hll_hash_integer(1)), hll_add(hll_empty(), hll_hash_integer(2)));
+                                           hll_union
+  --------------------------------------------------------------------------------------------
+   \x484c4c10002000002b090000000000000000400000000000000000b3ccc49320cca1ae3e2921ff133fbaed00
+  (1 row)
+  ```
+
+## Aggregate Functions
+
+- hll_add_agg(hll_hashval)
+
+  Description: Groups hashed data into HLL
+
+  Return type: HLL
+
+  Example:
+
+  ```sql
+  -- Prepare data.
+  mogdb=# create table t_id(id int);
+  mogdb=# insert into t_id values(generate_series(1,500));
+  mogdb=# create table t_data(a int, c text);
+  mogdb=# insert into t_data select mod(id,2), id from t_id;
+
+  -- Create a table and specify an HLL column.
+  mogdb=# create table t_a_c_hll(a int, c hll);
+
+  -- Use GROUP BY on column a to group data, and insert the data to the HLL.
+  mogdb=# insert into t_a_c_hll select a, hll_add_agg(hll_hash_text(c)) from t_data group by a;
+
+  -- Calculate the number of distinct values for each group in the HLL.
+  mogdb=# select a, #c as cardinality from t_a_c_hll order by a;
+   a |   cardinality
+  ---+------------------
+   0 | 247.862354346299
+   1 | 250.908710610377
+  (2 rows)
+  ```
+
+- hll_add_agg(hll_hashval, int32 log2m)
+
+  Description: Groups hashed data into HLL and specifies the **log2m** parameter. The value ranges from 10 to 16. If the input is **-1** or **NULL**, the built-in default value is used.
+
+  Return type: HLL
+
+  Example:
+
+  ```sql
+  mogdb=# select hll_cardinality(hll_add_agg(hll_hash_text(c), 12)) from t_data;
+   hll_cardinality
+  ------------------
+   497.965240179228
+  (1 row)
+  ```
+
+- hll_add_agg(hll_hashval, int32 log2m, int32 log2explicit)
+
+  Description: Groups hashed data into HLL and specifies the **log2m** and **log2explicit** parameters in sequence. The value of **log2explicit** ranges from 0 to 12. The value **0** indicates that the explicit mode is skipped. This parameter is used to set the threshold of the explicit mode. When the length of the data segment reaches 2log2explicit, the mode is switched to the sparse or full mode. If the input is **-1** or **NULL**, the built-in default value of **log2explicit** is used.
+
+  Return type: HLL
+
+  Example:
+
+  ```sql
+  mogdb=# select hll_cardinality(hll_add_agg(hll_hash_text(c), NULL, 1)) from t_data;
+   hll_cardinality
+  ------------------
+   498.496062953313
+  (1 row)
+  ```
+
+- hll_add_agg(hll_hashval, int32 log2m, int32 log2explicit, int64 log2sparse)
+
+  Description: Groups hashed data into HLL and sets the parameters **log2m**, **log2explicit**, and **log2sparse** in sequence. The value of **log2sparse** ranges from 0 to 14. The value **0** indicates that the sparse mode is skipped. This parameter is used to set the threshold of the sparse mode. When the length of the data segment reaches 2log2sparse, the mode is switched to the full mode. If the input is **-1** or **NULL**, the built-in default value of **log2sparse** is used.
+
+  Return type: HLL
+
+  Example:
+
+  ```sql
+  mogdb=# select hll_cardinality(hll_add_agg(hll_hash_text(c), NULL, 6, 10)) from t_data;
+   hll_cardinality
+  ------------------
+   498.496062953313
+  (1 row)
+  ```
+
+- hll_add_agg(hll_hashval, int32 log2m, int32 log2explicit, int64 log2sparse, int32 duplicatecheck)
+
+  Description: Groups hashed data into HLL and sets the **log2m**, **log2explicit**, **log2sparse**, and **duplicatecheck** parameters. The value of **duplicatecheck** can be **0** or **1**, indicating whether to enable this mode. By default, this mode is disabled. If the input is **-1** or **NULL**, the built-in default value of **duplicatecheck** is used.
+
+  Return type: HLL
+
+  Example:
+
+  ```sql
+  mogdb=# select hll_cardinality(hll_add_agg(hll_hash_text(c), NULL, 6, 10, -1)) from t_data;
+   hll_cardinality
+  ------------------
+   498.496062953313
+  (1 row)
+  ```
+
+- hll_union_agg(hll)
+
+  Description: Performs an UNION operation on multiple pieces of data of the HLL type to obtain one HLL.
+
+  Return type: HLL
+
+  Example:
+
+  ```sql
+  -- Perform an UNION operation on data of the HLL type in each group to obtain one HLL, and calculate the number of distinct values.
+  mogdb=# select #hll_union_agg(c) as cardinality from t_a_c_hll;
+     cardinality
+  ------------------
+   498.496062953313
+  (1 row)
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** To perform an UNION operation on data in multiple HLLs, ensure that the HLLs have the same precision. Otherwise, the UNION operation cannot be performed. This constraint also applies to the **hll_union(hll, hll)** function.
+
+## Obsolete Functions
+
+Some old HLL functions are discarded due to version upgrade. You can replace them with similar functions.
+
+- hll_schema_version(hll)
+
+  Description: Checks the schema version in the current HLL. In earlier versions, the schema version is fixed at **1**, which is used to verify the header of the HLL field. After refactoring, the HLL field is added to the header for verification. The schema version is no longer used.
+
+- hll_regwidth(hll)
+
+  Description: Queries the bucket size in the HLL data structure. In earlier versions, the value of **regwidth** ranges from 1 to 5, which has a large error and limits the upper limit of the cardinality estimation. After refactoring, the value of **regwidth** is fixed at **6** and the **regwidth** variable is not used.
+
+- hll_expthresh(hll)
+
+  Description: Obtains the **expthresh** value in the current HLL. The **hll_log2explicit(hll)** function is used to replace similar functions.
+
+- hll_sparseon(hll)
+
+  Description: Specifies whether to enable the sparse mode. Use **hll_log2sparse(hll)** to replace similar functions. The value **0** indicates that the sparse mode is disabled.
+
+## Built-in Functions
+
+HyperLogLog (HLL) has a series of built-in functions for internal data processing. Generally, users do not need to know how to use these functions. For details, see Table 1.
+
+**Table 1** Built-in Functions
+
+| Function          | Description                                                  |
+| :---------------- | :----------------------------------------------------------- |
+| hll_in            | Receives hll data in string format.                          |
+| hll_out           | Sends hll data in string format.                             |
+| hll_recv          | Receives hll data in bytea format.                           |
+| hll_send          | Sends hll data in bytea format.                              |
+| hll_trans_in      | Receives hll_trans_type data in string format.               |
+| hll_trans_out     | Sends hll_trans_type data in string format.                  |
+| hll_trans_recv    | Receives hll_trans_type data in bytea format.                |
+| hll_trans_send    | Sends hll_trans_type data in bytea format.                   |
+| hll_typmod_in     | Receives typmod data.                                        |
+| hll_typmod_out    | Sends typmod data.                                           |
+| hll_hashval_in    | Receives hll_hashval data.                                   |
+| hll_hashval_out   | Sends hll_hashval data.                                      |
+| hll_add_trans0    | It is similar to **hll_add**. No input parameter is specified during initialization. It is usually used in the first phase of DNs in aggregation operations. |
+| hll_add_trans1    | It is similar to **hll_add**. An input parameter is specified during initialization. It is usually used in the first phase of DNs in aggregation operations. |
+| hll_add_trans2    | It is similar to **hll_add**. Two input parameters are specified during initialization. It is usually used in the first phase of DNs in aggregation operations. |
+| hll_add_trans3    | It is similar to **hll_add**. Three input parameters are specified during initialization. It is usually used in the first phase of DNs in aggregation operations. |
+| hll_add_trans4    | It is similar to **hll_add**. Four input parameters are specified during initialization. It is usually used in the first phase of DNs in aggregation operations. |
+| hll_union_trans   | It is similar to **hll_union** and is used in the first phase of DNs in aggregation operations. |
+| hll_union_collect | It is similar to **hll_union** and is used in the second phase of DNs in aggregation operations to summarize the results of each DN. |
+| hll_pack          | It is used in the third phase of DNs in aggregation operations to convert a user-defined type hll_trans_type to the hll type. |
+| hll               | Converts an HLL type to another HLL type. Input parameters can be specified. |
+| hll_hashval       | Converts the bigint type to the **hll_hashval** type.        |
+| hll_hashval_int4  | Converts the int4 type to the **hll_hashval** type.          |
+
+## Operators
+
+- =
+
+  Description: Compares the values of HLL and **hll_hashval** types to check whether they are the same.
+
+  Return type: Boolean
+
+  Example:
+
+  ```sql
+  --hll
+  mogdb=# select (hll_empty() || hll_hash_integer(1)) = (hll_empty() || hll_hash_integer(1));
+  column
+  ----------
+   t
+  (1 row)
+
+  --hll_hashval
+  mogdb=# select hll_hash_integer(1) = hll_hash_integer(1);
+   ?column?
+  ----------
+   t
+  (1 row)
+  ```
+
+- <> or !=
+
+  Description: Compares the values of HLL and **hll_hashval** types to check whether they are different.
+
+  Return type: Boolean
+
+  Example:
+
+  ```sql
+  --hll
+  mogdb=# select (hll_empty() || hll_hash_integer(1)) <> (hll_empty() || hll_hash_integer(2));
+   ?column?
+  ----------
+   t
+  (1 row)
+
+  --hll_hashval
+  mogdb=# select hll_hash_integer(1) <> hll_hash_integer(2);
+   ?column?
+  ----------
+   t
+  (1 row)
+  ```
+
+- ||
+
+  Description: Represents the functions of **hll_add**, **hll_union**, and **hll_add_rev**.
+
+  Return type: HLL
+
+  Example:
+
+  ```sql
+  --hll_add
+  mogdb=# select hll_empty() || hll_hash_integer(1);
+                                    ?column?
+  ----------------------------------------------------------------------------
+   \x484c4c08000002002b0900000000000000f03f3e2921ff133fbaed3e2921ff133fbaed00
+  (1 row)
+
+  --hll_add_rev
+  mogdb=# select hll_hash_integer(1) || hll_empty();
+                                    ?column?
+  ----------------------------------------------------------------------------
+   \x484c4c08000002002b0900000000000000f03f3e2921ff133fbaed3e2921ff133fbaed00
+  (1 row)
+
+  --hll_union
+  mogdb=# select (hll_empty() || hll_hash_integer(1)) || (hll_empty() || hll_hash_integer(2));
+                                            ?column?
+  --------------------------------------------------------------------------------------------
+   \x484c4c10002000002b090000000000000000400000000000000000b3ccc49320cca1ae3e2921ff133fbaed00
+  (1 row)
+  ```
+
+- \#
+
+  Description: Calculates the number of distinct values of an HLL. It works the same as the **hll_cardinality** function.
+
+  Return type: int
+
+  Example:
+
+  ```sql
+  mogdb=# select #(hll_empty() || hll_hash_integer(1));
+   ?column?
+  ----------
+          1
+  (1 row)
+  ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/14-sequence-functions.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/14-sequence-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..75527422acc7a3d78bbddc0b034ecf353b273aff
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/14-sequence-functions.md
@@ -0,0 +1,127 @@
+---
+title: SEQUENCE Functions
+summary: SEQUENCE Functions
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# SEQUENCE Functions
+
+The sequence functions provide a simple method to ensure security of multiple users for users to obtain sequence values from sequence objects.
+
+- nextval(regclass)
+
+  Description: Specifies an increasing sequence and returns a new value.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  > To avoid blocking of concurrent transactions that obtain numbers from the same sequence, a nextval operation is never rolled back; that is, once a value has been fetched it is considered used, even if the transaction that did the nextval later aborts. This means that aborted transactions may leave unused "holes" in the sequence of assigned values. Therefore, MogDB sequences cannot be used to obtain sequence without gaps.
+  >
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+  > The **nextval** function can be executed only on the primary node. It is not supported on standby nodes.
+
+  Return type: bigint
+
+  The **nextval** function can be invoked in either of the following ways: (In example 2, the sequence name cannot contain a dot.)
+
+  Example 1:
+
+  ```sql
+  mogdb=# select nextval('seqDemo');
+   nextval
+  ---------
+         2
+  (1 row)
+  ```
+
+  Example 2:
+
+  ```sql
+  mogdb=# select seqDemo.nextval;
+   nextval
+  ---------
+         2
+  (1 row)
+  ```
+
+- currval(regclass)
+
+  Returns the last value of **nextval** for a specified sequence in the current session. If **nextval** has not been invoked for the specified sequence in the current session, an error is reported when **currval** is invoked.
+
+  Return type: bigint
+
+  The **currval** function can be invoked in either of the following ways: (In example 2, the sequence name cannot contain a dot.)
+
+  Example 1:
+
+  ```sql
+  mogdb=# select currval('seq1');
+   currval
+  ---------
+         2
+  (1 row)
+  ```
+
+  Example 2:
+
+  ```sql
+  mogdb=# select seq1.currval;
+   currval
+  ---------
+         2
+  (1 row)
+  ```
+
+- lastval()
+
+  Description: Returns the last value of **nextval** in the current session. This function is equivalent to **currval**, but **lastval** does not have a parameter. If **nextval** has not been invoked in the current session, invoking **lastval** will report an error.
+
+  Return type: bigint
+
+  Example:
+
+  ```sql
+  mogdb=# select lastval();
+   lastval
+  ---------
+         2
+  (1 row)
+  ```
+
+- setval(regclass, bigint)
+
+  Description: Sets the current value of a sequence.
+
+  Return type: bigint
+
+  Example:
+
+  ```sql
+  mogdb=# select setval('seqDemo',1);
+   setval
+  --------
+        1
+  (1 row)
+  ```
+
+- setval(regclass, bigint, Boolean)
+
+  Description: Sets the current value of a sequence and the is_called sign.
+
+  Return type: bigint
+
+  Example:
+
+  ```sql
+  mogdb=# select setval('seqDemo',1,true);
+   setval
+  --------
+        1
+  (1 row)
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  > The current session will take effect immediately after **setval** is performed. If other sessions have buffered sequence values, **setval** will take effect only after the values are used up. Therefore, to prevent sequence value conflicts, you are advised to use **setval** with caution.
+  > Because the sequence is non-transactional, the change caused by **setval** will not be undone by transaction rollback.
+  >
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+  > The **nextval** function can be executed only on the primary node. It is not supported on standby nodes.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/15-array-functions-and-operators.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/15-array-functions-and-operators.md
new file mode 100644
index 0000000000000000000000000000000000000000..9d6a26f0376f984b16e0260331a414895c05c721
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/15-array-functions-and-operators.md
@@ -0,0 +1,566 @@
+---
+title: Array Functions and Operators
+summary: Array Functions and Operators
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Array Functions and Operators
+
+## Array Operators
+
+- =
+
+  Description: Specifies whether two arrays are equal.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT ARRAY[1.1,2.1,3.1]::int[] = ARRAY[1,2,3] AS RESULT ;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;&gt;
+
+  Description: Specifies whether two arrays are not equal.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT ARRAY[1,2,3] <> ARRAY[1,2,4] AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;
+
+  Description: Specifies whether an array is less than another.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT ARRAY[1,2,3] < ARRAY[1,2,4] AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &gt;
+
+  Description: Specifies whether an array is greater than another.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT ARRAY[1,4,3] > ARRAY[1,2,4] AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;=
+
+  Description: Specifies whether an array is less than another.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT ARRAY[1,2,3] <= ARRAY[1,2,3] AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &gt;=
+
+  Description: Specifies whether an array is greater than or equal to another.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT ARRAY[1,4,3] >= ARRAY[1,4,3] AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- @&gt;
+
+  Description: Specifies whether an array contains another.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT ARRAY[1,4,3] @> ARRAY[3,1] AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;@
+
+  Description: Specifies whether an array is contained in another.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT ARRAY[2,7] <@ ARRAY[1,7,4,2,6] AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &&
+
+  Description: Specifies whether an array overlaps another (have common elements).
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT ARRAY[1,4,3] && ARRAY[2,1] AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- ||
+
+  Description: Array-to-array concatenation
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT ARRAY[1,2,3] || ARRAY[4,5,6] AS RESULT;
+      result
+  ---------------
+   {1,2,3,4,5,6}
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT ARRAY[1,2,3] || ARRAY[[4,5,6],[7,8,9]] AS RESULT;
+            result
+  ---------------------------
+   {{1,2,3},{4,5,6},{7,8,9}}
+  (1 row)
+  ```
+
+- ||
+
+  Description: Element-to-array concatenation
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT 3 || ARRAY[4,5,6] AS RESULT;
+    result
+  -----------
+   {3,4,5,6}
+  (1 row)
+  ```
+
+- ||
+
+  Description: Array-to-element concatenation
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT ARRAY[4,5,6] || 7 AS RESULT;
+    result
+  -----------
+   {4,5,6,7}
+  (1 row)
+  ```
+
+Array comparisons compare the array contents element-by-element, using the default B-tree comparison function for the element data type. In multidimensional arrays, the elements are accessed in row-major order. If the contents of two arrays are equal but the dimensionality is different, the first difference in the dimensionality information determines the sort order.
+
+## Array Functions
+
+- array_append(anyarray, anyelement)
+
+  Description: Appends an element to the end of an array, and only supports dimension-1 arrays.
+
+  Return type: anyarray
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT array_append(ARRAY[1,2], 3) AS RESULT;
+   result
+  ---------
+   {1,2,3}
+  (1 row)
+  ```
+
+- array_prepend(anyelement, anyarray)
+
+  Description: Appends an element to the beginning of an array, and only supports dimension-1 arrays.
+
+  Return type: anyarray
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT array_prepend(1, ARRAY[2,3]) AS RESULT;
+   result
+  ---------
+   {1,2,3}
+  (1 row)
+  ```
+
+- array_cat(anyarray, anyarray)
+
+  Description: Concatenates two arrays, and supports multi-dimensional arrays.
+
+  Return type: anyarray
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT array_cat(ARRAY[1,2,3], ARRAY[4,5]) AS RESULT;
+     result
+  -------------
+   {1,2,3,4,5}
+  (1 row)
+
+  mogdb=# SELECT array_cat(ARRAY[[1,2],[4,5]], ARRAY[6,7]) AS RESULT;
+         result
+  ---------------------
+   {{1,2},{4,5},{6,7}}
+  (1 row)
+  ```
+
+- array_cat_distinct(anyarray, anyarray)
+
+    Description: Concatenates two arrays and deduplicates them. Only one-dimensional arrays are supported.
+
+    Return type: anyarray
+
+    Example:
+
+    ```sql
+    mogdb=# SELECT array_cat_distinct(ARRAY[1,2,3], ARRAY[3,4,5]) AS RESULT;
+       result
+    -------------
+     {1,2,3,4,5}
+    (1 row)
+    ```
+
+- array_intersect(anyarray, anyarray)
+
+    Description: Intersects two arrays. Only one-dimensional arrays are supported.
+
+    Return type: anyarray
+
+    Example:
+
+    ```sql
+    mogdb=# SELECT array_intersect(ARRAY[1,2,3], ARRAY[3,4,5]) AS RESULT;
+       result
+    -------------
+     {3}
+    (1 row)
+    ```
+
+- array_intersect_distinct(anyarray, anyarray)
+
+    Description: Intersects two arrays and deduplicates them. Only one-dimensional arrays are supported.
+
+    Return type: anyarray
+
+    Example:
+
+    ```sql
+    mogdb=# SELECT array_intersect_distinct(ARRAY[1,2,2], ARRAY[2,2,4,5]) AS RESULT;
+       result
+    -------------
+     {2}
+    (1 row)
+    ```
+
+- array_except(anyarray, anyarray)
+
+    Description: Calculates the difference between two arrays. Only one-dimensional arrays are supported.
+
+    Return type: anyarray
+
+    Example:
+
+    ```sql
+    mogdb=# SELECT array_except(ARRAY[1,2,3], ARRAY[3,4,5]) AS RESULT;
+       result
+    -------------
+     {1,2}
+    (1 row)
+    ```
+
+- array_except_distinct(anyarray, anyarray)
+
+    Description: Calculates the difference between two arrays and deduplicates them. Only one-dimensional arrays are supported.
+
+    Return type: anyarray
+
+    Example:
+
+    ```sql
+    mogdb=# SELECT array_except_distinct(ARRAY[1,2,2,3], ARRAY[3,4,5]) AS RESULT;
+       result
+    -------------
+     {1,2}
+    (1 row)
+    ```
+
+- array_ndims(anyarray)
+
+  Description: Returns the number of dimensions of an array.
+
+  Return type: int
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT array_ndims(ARRAY[[1,2,3], [4,5,6]]) AS RESULT;
+   result
+  --------
+        2
+  (1 row)
+  ```
+
+- array_dims(anyarray)
+
+  Description: Returns the low-order flag bits and high-order flag bits of each dimension in an array.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT array_dims(ARRAY[[1,2,3], [4,5,6]]) AS RESULT;
+     result
+  ------------
+   [1:2][1:3]
+  (1 row)
+  ```
+
+- array_length(anyarray, int)
+
+  Description: Returns the length of the requested array dimension. **int** is the requested array dimension.
+
+  Return type: int
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT array_length(array[1,2,3], 1) AS RESULT;
+   result
+  --------
+        3
+  (1 row)
+
+  mogdb=# SELECT array_length(array[[1,2,3],[4,5,6]], 2) AS RESULT;
+   result
+  --------
+        3
+  (1 row)
+  ```
+
+- array_lower(anyarray, int)
+
+  Description: Returns lower bound of the requested array dimension. **int** is the requested array dimension.
+
+  Return type: int
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT array_lower('[0:2]={1,2,3}'::int[], 1) AS RESULT;
+   result
+  --------
+        0
+  (1 row)
+  ```
+
+- array_upper(anyarray, int)
+
+  Description: Returns upper bound of the requested array dimension. **int** is the requested array dimension.
+
+  Return type: int
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT array_upper(ARRAY[1,8,3,7], 1) AS RESULT;
+   result
+  --------
+        4
+  (1 row)
+  ```
+
+- array_remove(anyarray, anyelement)
+
+    Description: Removes all specified elements from an array. Only one-dimensional arrays are supported.
+
+    Return type: anyarray
+
+    Example:
+
+    ```sql
+    mogdb=# SELECT array_remove(ARRAY[1,8,8,7], 8) AS RESULT;
+     result
+    --------
+     {1,7}
+    (1 row)
+    ```
+
+- array_to_string(anyarray, text [, text])
+
+  Description: Uses the first **text** as the new delimiter and the second **text** to replace **NULL** values.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT array_to_string(ARRAY[1, 2, 3, NULL, 5], ',', '*') AS RESULT;
+    result
+  -----------
+   1,2,3,*,5
+  (1 row)
+  ```
+
+- array_delete(anyarray)
+
+    Description: Clears elements in an array and returns an empty array of the same type.
+
+    Return type: anyarray
+
+    Example:
+
+    ```sql
+    mogdb=# SELECT array_delete(ARRAY[1,8,3,7]) AS RESULT;
+     result
+    --------
+     {}
+    (1 row)
+    ```
+
+- array_extendnull(anyarray, int)
+
+    Description: Adds a specified number of null elements to the end of an array.
+
+    Return type: anyarray
+
+    Example:
+
+    ```sql
+    mogdb=# SELECT array_extendnull(ARRAY[1,8,3,7],1) AS RESULT;
+        result
+    --------------
+    {1,8,3,7,null}
+    (1 row)
+    ```
+
+- array_exists(anyarray, int)
+
+    Description: Checks whether the second parameter is a valid subscript of an array.
+
+    Return type: Boolean
+
+    Example:
+
+    ```sql
+    mogdb=# SELECT array_exists(ARRAY[1,8,3,7],1) AS RESULT;
+     result
+    --------
+     t
+    (1 row)
+    ```
+
+- array_next(anyarray, int)
+
+    Description: Returns the subscript of the element following a specified subscript in an array based on the second input parameter.
+
+    Return type: int
+
+    Example:
+
+    ```sql
+    mogdb=# SELECT array_next(ARRAY[1,8,3,7],1) AS RESULT;
+     result
+    --------
+          2
+    (1 row)
+    ```
+
+- array_prior(anyarray, int)
+
+    Description: Returns the subscript of the element followed by a specified subscript in an array based on the second input parameter.
+
+    Return type: int
+
+    Example:
+
+    ```sql
+    mogdb=# SELECT array_next(ARRAY[1,8,3,7],2) AS RESULT;
+     result
+    --------
+      1
+    (1 row)
+    ```
+
+- string_to_array(text, text [, text])
+
+  Description: Uses the second **text** as the new delimiter and the third **text** as the substring to be replaced by **NULL** values. A substring can be replaced by **NULL** values only when it is the same as the third **text**.
+
+  Return type: text[]
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT string_to_array('xx~^~yy~^~zz', '~^~', 'yy') AS RESULT;
+      result
+  --------------
+   {xx,NULL,zz}
+  (1 row)
+  mogdb=# SELECT string_to_array('xx~^~yy~^~zz', '~^~', 'y') AS RESULT;
+     result
+  ------------
+   {xx,yy,zz}
+  (1 row)
+  ```
+
+- unnest(anyarray)
+
+  Description: Expands an array to a set of rows.
+
+  Return type: setof anyelement
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT unnest(ARRAY[1,2]) AS RESULT;
+   result
+  --------
+        1
+        2
+  (2 rows)
+  ```
+
+In **string_to_array**, if the delimiter parameter is NULL, each character in the input string will become a separate element in the resulting array. If the delimiter is an empty string, then the entire input string is returned as a one-element array. Otherwise the input string is split at each occurrence of the delimiter string.
+
+In **string_to_array**, if the null-string parameter is omitted or NULL, none of the substrings of the input will be replaced by NULL.
+
+In **array_to_string**, if the null-string parameter is omitted or NULL, any null elements in the array are simply skipped and not represented in the output string.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/16-range-functions-and-operators.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/16-range-functions-and-operators.md
new file mode 100644
index 0000000000000000000000000000000000000000..0002dd5f2578b1bc242e561d6b065662c0f003bc
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/16-range-functions-and-operators.md
@@ -0,0 +1,435 @@
+---
+title: Range Functions and Operators
+summary: Range Functions and Operators
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Range Functions and Operators
+
+## Range Operators
+
+- =
+
+  Description: Equals
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT int4range(1,5) = '[1,4]'::int4range AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;&gt;
+
+  Description: Does not equal to
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT numrange(1.1,2.2) <> numrange(1.1,2.3) AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;
+
+  Description: Is less than
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT int4range(1,10) < int4range(2,3) AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &gt;
+
+  Description: Is greater than
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT int4range(1,10) > int4range(1,5) AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;=
+
+  Description: Is less than or equals
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT numrange(1.1,2.2) <= numrange(1.1,2.2) AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &gt;=
+
+  Description: Is greater than or equals
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT numrange(1.1,2.2) >= numrange(1.1,2.0) AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- @&gt;
+
+  Description: Contains ranges
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT int4range(2,4) @> int4range(2,3) AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- @&gt;
+
+  Description: Contains elements
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT '[2011-01-01,2011-03-01)'::tsrange @> '2011-01-10'::timestamp AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;@
+
+  Description: Range is contained by
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT int4range(2,4) <@ int4range(1,7) AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;@
+
+  Description: Element is contained by
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT 42 <@ int4range(1,7) AS RESULT;
+   result
+  --------
+   f
+  (1 row)
+  ```
+
+- &&
+
+  Description: Overlap (have points in common)
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT int8range(3,7) && int8range(4,12) AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;&lt;
+
+  Description: Strictly left of
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT int8range(1,10) << int8range(100,110) AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &gt;&gt;
+
+  Description: Strictly right of
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT int8range(50,60) >> int8range(20,30) AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &&lt;
+
+  Description: Does not extend to the right of
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT int8range(1,20) &< int8range(18,20) AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &&gt;
+
+  Description: Does not extend to the left of
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT int8range(7,20) &> int8range(5,10) AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- -|-
+
+  Description: Is adjacent to
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT numrange(1.1,2.2) -|- numrange(2.2,3.3) AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- \+
+
+  Description: Union
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT numrange(5,15) + numrange(10,20) AS RESULT;
+   result
+  --------
+   [5,20)
+  (1 row)
+  ```
+
+- \*
+
+  Description: Intersection
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT int8range(5,15) * int8range(10,20) AS RESULT;
+   result
+  ---------
+   [10,15)
+  (1 row)
+  ```
+
+- \-
+
+  Description: Difference
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT int8range(5,15) - int8range(10,20) AS RESULT;
+   result
+  --------
+   [5,10)
+  (1 row)
+  ```
+
+The simple comparison operators **&lt;**, **&gt;**, **&lt;=**, and **&gt;=** compare the lower bounds first, and only if those are equal, compare the upper bounds.
+
+The **&lt;&lt;**, **&gt;&gt;**, and **-|-** operators always return false when an empty range is involved; that is, an empty range is not considered to be either before or after any other range.
+
+The union and difference operators will fail if the resulting range would need to contain two disjoint sub-ranges.
+
+## Range Functions
+
+- numrange(numeric, numeric, [text])
+
+    Description: Specifies a range.
+
+    Return type: Range's element type
+
+    Example:
+
+    ```
+    mogdb=# SELECT numrange(1.1,2.2) AS RESULT;
+     result
+    --------
+    [1.1,2.2)
+    (1 row)
+    mogdb=# SELECT numrange(1.1,2.2, '()') AS RESULT;
+     result
+    --------
+    (1.1,2.2)
+    (1 row)
+    ```
+
+- lower(anyrange)
+
+  Description: Lower bound of a range
+
+  Return type: Range's element type
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT lower(numrange(1.1,2.2)) AS RESULT;
+   result
+  --------
+      1.1
+  (1 row)
+  ```
+
+- upper(anyrange)
+
+  Description: Upper bound of a range
+
+  Return type: Range's element type
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT upper(numrange(1.1,2.2)) AS RESULT;
+   result
+  --------
+      2.2
+  (1 row)
+  ```
+
+- isempty(anyrange)
+
+  Description: Is the range empty?
+
+  Return type: Boolean
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT isempty(numrange(1.1,2.2)) AS RESULT;
+   result
+  --------
+   f
+  (1 row)
+  ```
+
+- lower_inc(anyrange)
+
+  Description: Is the lower bound inclusive?
+
+  Return type: Boolean
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT lower_inc(numrange(1.1,2.2)) AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- upper_inc(anyrange)
+
+  Description: Is the upper bound inclusive?
+
+  Return type: Boolean
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT upper_inc(numrange(1.1,2.2)) AS RESULT;
+   result
+  --------
+   f
+  (1 row)
+  ```
+
+- lower_inf(anyrange)
+
+  Description: Is the lower bound infinite?
+
+  Return type: Boolean
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT lower_inf('(,)'::daterange) AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- upper_inf(anyrange)
+
+  Description: Is the upper bound infinite?
+
+  Return type: Boolean
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT upper_inf('(,)'::daterange) AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+The **lower** and **upper** functions return null if the range is empty or the requested bound is infinite. The **lower_inc**, **upper_inc**, **lower_inf**, and **upper_inf** functions all return false for an empty range.
+
+- elem_contained_by_range(anyelement, anyrange)
+
+    Description: Determines whether an element is within the range.
+
+    Return type: Boolean
+
+    Example:
+
+    ```
+    mogdb=# SELECT elem_contained_by_range('2', numrange(1.1,2.2));
+     elem_contained_by_range
+    -------------------------
+     t
+    (1 row)
+    ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/17-aggregate-functions.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/17-aggregate-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..3d6142c0b8bcccddabc4526fda3faf5f12510e0e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/17-aggregate-functions.md
@@ -0,0 +1,819 @@
+---
+title: Aggregate Functions
+summary: Aggregate Functions
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Aggregate Functions
+
+- sum(expression)
+
+  Description: Specifies the sum of expressions across all input values.
+
+  Return type:
+
+  Generally, same as the argument data type. In the following cases, type conversion occurs:
+
+  - **BIGINT** for **SMALLINT** or **INT** arguments
+  - **NUMBER** for **BIGINT** arguments
+  - **DOUBLE PRECISION** for floating-point arguments
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT SUM(ss_ext_tax) FROM tpcds.STORE_SALES;
+    sum
+  --------------
+   213267594.69
+  (1 row)
+  ```
+
+- max(expression)
+
+  Description: Specifies the maximum value of expression across all input values.
+
+  Parameter type: any array, numeric, string, date/time type, or IPv4 and IPv6 addresses (INET and CIDR data types)
+
+  Return type: same as the argument type
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT MAX(inv_quantity_on_hand) FROM tpcds.inventory;
+  ```
+
+- min(expression)
+
+  Description: Specifies the minimum value of expression across all input values.
+
+  Parameter type: any array, numeric, string, date/time type, or IPv4 and IPv6 addresses (INET and CIDR data types)
+
+  Return type: same as the argument type
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT MIN(inv_quantity_on_hand) FROM tpcds.inventory;
+   min
+  -----
+     0
+  (1 row)
+  ```
+
+- avg(expression)
+
+  Description: Specifies the average (arithmetic mean) of all input values.
+
+  Return type:
+
+  **NUMBER** for any integer-type argument.
+
+  **DOUBLE PRECISION** for floating-point arguments.
+
+  otherwise the same as the argument data type.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT AVG(inv_quantity_on_hand) FROM tpcds.inventory;
+           avg
+  ----------------------
+   500.0387129084044604
+  (1 row)
+  ```
+
+- count(expression)
+
+  Description: Specifies the number of input rows for which the value of the expression is not null.
+
+  Return type: bigint
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT COUNT(inv_quantity_on_hand) FROM tpcds.inventory;
+    count
+  ----------
+   11158087
+  (1 row)
+  ```
+
+- count(*)
+
+  Description: Returns the number of input rows.
+
+  Return type: bigint
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT COUNT(*) FROM tpcds.inventory;
+    count
+  ----------
+   11745000
+  (1 row)
+  ```
+
+- median(expression) [over (query partition clause)]
+
+  Description: Returns the median of an expression. **NULL** will be ignored by the median function during calculation. The **DISTINCT** keyword can be used to exclude duplicate records in an expression. The data type of the input expression can be numeric (including integer, double, and bigint) or interval. For other data types, the median cannot be calculated.
+
+  Return type: double or interval
+
+  Example:
+
+  ```sql
+  select median(id) from (values(1), (2), (3), (4), (null)) test(id);
+   median
+  --------
+       2.5
+  (1 row)
+  ```
+
+- array_agg(expression)
+
+  Description: Concatenates input values, including nulls, into an array.
+
+  Return type: array of the argument type
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT ARRAY_AGG(sr_fee) FROM tpcds.store_returns WHERE sr_customer_sk = 2;
+     array_agg
+  ---------------
+   {22.18,63.21}
+  (1 row)
+  ```
+
+- string_agg(expression, delimiter)
+
+  Description: Concatenates input values into a string, separated by delimiter.
+
+  Return type: same as the argument type
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT string_agg(sr_item_sk, ',') FROM tpcds.store_returns where sr_item_sk < 3;
+           string_agg
+  ---------------------------------------------------------------------------------
+  ------------------------------
+   1,2,1,2,2,1,1,2,2,1,2,1,2,1,1,1,2,1,1,1,1,1,2,1,1,1,1,1,2,2,1,1,1,1,1,1,1,1,1,2,
+  2,1,1,1,1,1,1,2,2,1,1,2,1,1,1
+  (1 row)
+  ```
+
+- listagg(expression [, delimiter]) WITHIN GROUP(ORDER BY order-list)
+
+  Description: Sorts aggregation column data according to the mode specified by **WITHIN GROUP** and concatenates the data to a string using the specified delimiter.
+
+  - **expression**: Mandatory. It specifies an aggregation column name or a column-based valid expression. It does not support the **DISTINCT** keyword and the **VARIADIC** parameter.
+  - **delimiter**: Optional. It specifies a delimiter, which can be a string constant or a deterministic expression based on a group of columns. The default value is empty.
+  - **order-list**: Mandatory. It specifies the sorting mode in a group.
+
+  Return type: text
+
+  Example:
+
+  The aggregation column is of the text character set type.
+
+  ```sql
+  mogdb=# SELECT deptno, listagg(ename, ',') WITHIN GROUP(ORDER BY ename) AS employees FROM emp GROUP BY deptno;
+   deptno |              employees
+  --------+--------------------------------------
+       10 | CLARK,KING,MILLER
+       20 | ADAMS,FORD,JONES,SCOTT,SMITH
+       30 | ALLEN,BLAKE,JAMES,MARTIN,TURNER,WARD
+  (3 rows)
+  ```
+
+  The aggregation column is of the integer type.
+
+  ```sql
+  mogdb=# SELECT deptno, listagg(mgrno, ',') WITHIN GROUP(ORDER BY mgrno NULLS FIRST) AS mgrnos FROM emp GROUP BY deptno;
+   deptno |            mgrnos
+  --------+-------------------------------
+       10 | 7782,7839
+       20 | 7566,7566,7788,7839,7902
+       30 | 7698,7698,7698,7698,7698,7839
+  (3 rows)
+  ```
+
+  The aggregation column is of the floating point type.
+
+  ```sql
+  mogdb=# SELECT job, listagg(bonus, '($); ') WITHIN GROUP(ORDER BY bonus DESC) || '($)' AS bonus FROM emp GROUP BY job;
+      job     |                      bonus
+  ------------+-------------------------------------------------
+   CLERK      | 10234.21($); 2000.80($); 1100.00($); 1000.22($)
+   PRESIDENT  | 23011.88($)
+   ANALYST    | 2002.12($); 1001.01($)
+   MANAGER    | 10000.01($); 2399.50($); 999.10($)
+   SALESMAN   | 1000.01($); 899.00($); 99.99($); 9.00($)
+  (5 rows)
+  ```
+
+  The aggregation column is of the time type.
+
+  ```sql
+  mogdb=# SELECT deptno, listagg(hiredate, ', ') WITHIN GROUP(ORDER BY hiredate DESC) AS hiredates FROM emp GROUP BY deptno;
+   deptno |                                                          hiredates
+  --------+------------------------------------------------------------------------------------------------------------------------------
+       10 | 1982-01-23 00:00:00, 1981-11-17 00:00:00, 1981-06-09 00:00:00
+       20 | 2001-04-02 00:00:00, 1999-12-17 00:00:00, 1987-05-23 00:00:00, 1987-04-19 00:00:00, 1981-12-03 00:00:00
+       30 | 2015-02-20 00:00:00, 2010-02-22 00:00:00, 1997-09-28 00:00:00, 1981-12-03 00:00:00, 1981-09-08 00:00:00, 1981-05-01 00:00:00
+  (3 rows)
+  ```
+
+  The aggregation column is of the time interval type.
+
+  ```sql
+  mogdb=# SELECT deptno, listagg(vacationTime, '; ') WITHIN GROUP(ORDER BY vacationTime DESC) AS vacationTime FROM emp GROUP BY deptno;
+   deptno |                                    vacationtime
+  --------+------------------------------------------------------------------------------------
+       10 | 1 year 30 days; 40 days; 10 days
+       20 | 70 days; 36 days; 9 days; 5 days
+       30 | 1 year 1 mon; 2 mons 10 days; 30 days; 12 days 12:00:00; 4 days 06:00:00; 24:00:00
+  (3 rows)
+  ```
+
+  By default, the delimiter is empty.
+
+  ```sql
+  mogdb=# SELECT deptno, listagg(job) WITHIN GROUP(ORDER BY job) AS jobs FROM emp GROUP BY deptno;
+   deptno |                     jobs
+  --------+----------------------------------------------
+       10 | CLERKMANAGERPRESIDENT
+       20 | ANALYSTANALYSTCLERKCLERKMANAGER
+       30 | CLERKMANAGERSALESMANSALESMANSALESMANSALESMAN
+  (3 rows)
+  ```
+
+  When **listagg** is used as a window function, the **OVER** clause does not support the window sorting of **ORDER BY**, and the **listagg** column is an ordered aggregation of the corresponding groups.
+
+  ```sql
+  mogdb=# SELECT deptno, mgrno, bonus, listagg(ename,'; ') WITHIN GROUP(ORDER BY hiredate) OVER(PARTITION BY deptno) AS employees FROM emp;
+   deptno | mgrno |  bonus   |                 employees
+  --------+-------+----------+-------------------------------------------
+       10 |  7839 | 10000.01 | CLARK; KING; MILLER
+       10 |       | 23011.88 | CLARK; KING; MILLER
+       10 |  7782 | 10234.21 | CLARK; KING; MILLER
+       20 |  7566 |  2002.12 | FORD; SCOTT; ADAMS; SMITH; JONES
+       20 |  7566 |  1001.01 | FORD; SCOTT; ADAMS; SMITH; JONES
+       20 |  7788 |  1100.00 | FORD; SCOTT; ADAMS; SMITH; JONES
+       20 |  7902 |  2000.80 | FORD; SCOTT; ADAMS; SMITH; JONES
+       20 |  7839 |   999.10 | FORD; SCOTT; ADAMS; SMITH; JONES
+       30 |  7839 |  2399.50 | BLAKE; TURNER; JAMES; MARTIN; WARD; ALLEN
+       30 |  7698 |     9.00 | BLAKE; TURNER; JAMES; MARTIN; WARD; ALLEN
+       30 |  7698 |  1000.22 | BLAKE; TURNER; JAMES; MARTIN; WARD; ALLEN
+       30 |  7698 |    99.99 | BLAKE; TURNER; JAMES; MARTIN; WARD; ALLEN
+       30 |  7698 |  1000.01 | BLAKE; TURNER; JAMES; MARTIN; WARD; ALLEN
+       30 |  7698 |   899.00 | BLAKE; TURNER; JAMES; MARTIN; WARD; ALLEN
+  (14 rows)
+  ```
+
+- covar_pop(Y, X)
+
+  Description: Specifies the overall covariance.
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT COVAR_POP(sr_fee, sr_net_loss) FROM tpcds.store_returns WHERE sr_customer_sk < 1000;
+      covar_pop
+  ------------------
+   829.749627587403
+  (1 row)
+  ```
+
+- covar_samp(Y, X)
+
+  Description: Specifies the sample covariance.
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT COVAR_SAMP(sr_fee, sr_net_loss) FROM tpcds.store_returns WHERE sr_customer_sk < 1000;
+      covar_samp
+  ------------------
+   830.052235037289
+  (1 row)
+  ```
+
+- stddev_pop(expression)
+
+  Description: Specifies the overall standard deviation.
+
+  Return type: **double precision** for floating-point arguments, otherwise **numeric**
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT STDDEV_POP(inv_quantity_on_hand) FROM tpcds.inventory WHERE inv_warehouse_sk = 1;
+      stddev_pop
+  ------------------
+   289.224294957556
+  (1 row)
+  ```
+
+- stddev_samp(expression)
+
+  Description: Specifies the sample standard deviation of the input values.
+
+  Return type: **double precision** for floating-point arguments, otherwise **numeric**
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT STDDEV_SAMP(inv_quantity_on_hand) FROM tpcds.inventory WHERE inv_warehouse_sk = 1;
+     stddev_samp
+  ------------------
+   289.224359757315
+  (1 row)
+  ```
+
+- var_pop(expression)
+
+  Description: Specifies the population variance of the input values (square of the population standard deviation).
+
+  Return type: **double precision** for floating-point arguments, otherwise **numeric**
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT VAR_POP(inv_quantity_on_hand) FROM tpcds.inventory WHERE inv_warehouse_sk = 1;
+        var_pop
+  --------------------
+   83650.692793695475
+  (1 row)
+  ```
+
+- var_samp(expression)
+
+  Description: Specifies the sample variance of the input values (square of the sample standard deviation).
+
+  Return type: **double precision** for floating-point arguments, otherwise **numeric**
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT VAR_SAMP(inv_quantity_on_hand) FROM tpcds.inventory WHERE inv_warehouse_sk = 1;
+        var_samp
+  --------------------
+   83650.730277028768
+  (1 row)
+  ```
+
+- bit_and(expression)
+
+  Description: bitwise AND of all non-null input values, or null if none
+
+  Return type: same as the argument type
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT BIT_AND(inv_quantity_on_hand) FROM tpcds.inventory WHERE inv_warehouse_sk = 1;
+   bit_and
+  ---------
+         0
+  (1 row)
+  ```
+
+- bit_or(expression)
+
+  Description: bitwise OR of all non-null input values, or null if none
+
+  Return type: same as the argument type
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT BIT_OR(inv_quantity_on_hand) FROM tpcds.inventory WHERE inv_warehouse_sk = 1;
+   bit_or
+  --------
+     1023
+  (1 row)
+  ```
+
+- bool_and(expression)
+
+  Description: Its value is **true** if all input values are **true**, otherwise **false**.
+
+  Return type: Boolean
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT bool_and(100 <2500);
+   bool_and
+  ----------
+   t
+  (1 row)
+  ```
+
+- bool_or(expression)
+
+  Description: Its value is **true** if at least one input value is **true**, otherwise **false**.
+
+  Return type: Boolean
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT bool_or(100 <2500);
+   bool_or
+  ----------
+   t
+  (1 row)
+  ```
+
+- corr(Y, X)
+
+  Description: Specifies the correlation coefficient.
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT CORR(sr_fee, sr_net_loss) FROM tpcds.store_returns WHERE sr_customer_sk < 1000;
+         corr
+  -------------------
+   .0381383624904186
+  (1 row)
+  ```
+
+- every(expression)
+
+  Description: Equivalent to **bool_and**
+
+  Return type: Boolean
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT every(100 <2500);
+   every
+  -------
+   t
+  (1 row)
+  ```
+
+- regr_avgx(Y, X)
+
+  Description: Specifies the average of the independent variable (**sum(X)/N**).
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT REGR_AVGX(sr_fee, sr_net_loss) FROM tpcds.store_returns WHERE sr_customer_sk < 1000;
+      regr_avgx
+  ------------------
+   578.606576740795
+  (1 row)
+  ```
+
+- regr_avgy(Y, X)
+
+  Description: Specifies the average of the dependent variable (**sum(Y)/N**).
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT REGR_AVGY(sr_fee, sr_net_loss) FROM tpcds.store_returns WHERE sr_customer_sk < 1000;
+      regr_avgy
+  ------------------
+   50.0136711629602
+  (1 row)
+  ```
+
+- regr_count(Y, X)
+
+  Description: Specifies the number of input rows in which both expressions are non-null.
+
+  Return type: bigint
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT REGR_COUNT(sr_fee, sr_net_loss) FROM tpcds.store_returns WHERE sr_customer_sk < 1000;
+   regr_count
+  ------------
+         2743
+  (1 row)
+  ```
+
+- regr_intercept(Y, X)
+
+  Description: Specifies the y-intercept of the least-squares-fit linear equation determined by the (X, Y) pairs.
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT REGR_INTERCEPT(sr_fee, sr_net_loss) FROM tpcds.store_returns WHERE sr_customer_sk < 1000;
+    regr_intercept
+  ------------------
+   49.2040847848607
+  (1 row)
+  ```
+
+- regr_r2(Y, X)
+
+  Description: Specifies the square of the correlation coefficient.
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT REGR_R2(sr_fee, sr_net_loss) FROM tpcds.store_returns WHERE sr_customer_sk < 1000;
+        regr_r2
+  --------------------
+   .00145453469345058
+  (1 row)
+  ```
+
+- regr_slope(Y, X)
+
+  Description: Specifies the slope of the least-squares-fit linear equation determined by the (X, Y) pairs.
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT REGR_SLOPE(sr_fee, sr_net_loss) FROM tpcds.store_returns WHERE sr_customer_sk < 1000;
+       regr_slope
+  --------------------
+   .00139920009665259
+  (1 row)
+  ```
+
+- regr_sxx(Y, X)
+
+  Description: **sum(X^2) - sum(X)^2/N** (sum of squares of the independent variables)
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT REGR_SXX(sr_fee, sr_net_loss) FROM tpcds.store_returns WHERE sr_customer_sk < 1000;
+       regr_sxx
+  ------------------
+   1626645991.46135
+  (1 row)
+  ```
+
+- regr_sxy(Y, X)
+
+  Description: **sum(X\*Y) - sum(X) \* sum(Y)/N** ("sum of products" of independent times dependent variable)
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT REGR_SXY(sr_fee, sr_net_loss) FROM tpcds.store_returns WHERE sr_customer_sk < 1000;
+       regr_sxy
+  ------------------
+   2276003.22847225
+  (1 row)
+  ```
+
+- regr_syy(Y, X)
+
+  Description: **sum(Y^2) - sum(Y)^2/N** ("sum of squares" of the dependent variable)
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT REGR_SYY(sr_fee, sr_net_loss) FROM tpcds.store_returns WHERE sr_customer_sk < 1000;
+      regr_syy
+  -----------------
+   2189417.6547314
+  (1 row)
+  ```
+
+- stddev(expression)
+
+  Description: Specifies the alias of **stddev_samp**.
+
+  Return type: **double precision** for floating-point arguments, otherwise **numeric**
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT STDDEV(inv_quantity_on_hand) FROM tpcds.inventory WHERE inv_warehouse_sk = 1;
+        stddev
+  ------------------
+   289.224359757315
+  (1 row)
+  ```
+
+- variance(expexpression,ression)
+
+  Description: Specifies the alias of **var_samp**.
+
+  Return type: **double precision** for floating-point arguments, otherwise **numeric**
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT VARIANCE(inv_quantity_on_hand) FROM tpcds.inventory WHERE inv_warehouse_sk = 1;
+        variance
+  --------------------
+   83650.730277028768
+  (1 row)
+  ```
+
+- delta
+
+  Description: Returns the difference between the current row and the previous row.
+
+  Parameter: numeric
+
+  Return type: numeric
+
+- checksum(expression)
+
+  Description: Returns the **CHECKSUM** value of all input values. This function can be used to check whether the data in the tables is the same before and after the backup, restoration, or migration of the MogDB database (databases other than MogDB are not supported). Before and after database backup, database restoration, or data migration, you need to manually run SQL commands to obtain the execution results. Compare the obtained execution results to check whether the data in the tables before and after the backup or migration is the same.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** - For large tables, the execution of the **CHECKSUM** function may take a long time. - If the **CHECKSUM** values of two tables are different, it indicates that the contents of the two tables are different. Using the hash function in the **CHECKSUM** function may incur conflicts. There is low possibility that two tables with different contents may have the same **CHECKSUM** value. The same problem may occur when **CHECKSUM** is used for columns. - If the time type is timestamp, timestamptz, or smalldatetime, ensure that the time zone settings are the same when calculating the **CHECKSUM** value.
+
+  - If the **CHECKSUM** value of a column is calculated and the column type can be changed to TEXT by default, set *expression* to the column name.
+  - If the **CHECKSUM** value of a column is calculated and the column type cannot be converted to TEXT by default, set *expression* to *Column name***::TEXT**.
+  - If the **CHECKSUM** value of all columns is calculated, set *expression* to *Table name***::TEXT**.
+
+  The following types of data can be converted into TEXT types by default: char, name, int8, int2, int1, int4, raw, pg_node_tree, float4, float8, bpchar, varchar, nvarchar2, date, timestamp, timestamptz, numeric, and smalldatetime. Other types need to be forcibly converted to TEXT.
+
+  Return type: numeric
+
+  Example:
+
+  The following shows the **CHECKSUM** value of a column that can be converted to the TEXT type by default:
+
+  ```sql
+  mogdb=# SELECT CHECKSUM(inv_quantity_on_hand) FROM tpcds.inventory;
+       checksum
+  -------------------
+   24417258945265247
+  (1 row)
+  ```
+
+  The following shows the **CHECKSUM** value of a column that cannot be converted to the TEXT type by default. Note that the **CHECKSUM** parameter is set to *Column name***::TEXT**.
+
+  ```sql
+  mogdb=# SELECT CHECKSUM(inv_quantity_on_hand::TEXT) FROM tpcds.inventory;
+       checksum
+  -------------------
+   24417258945265247
+  (1 row)
+  ```
+
+  The following shows the **CHECKSUM** value of all columns in a table. Note that the **CHECKSUM** parameter is set to *Table name***::TEXT**. The table name is not modified by its schema.
+
+  ```sql
+  mogdb=# SELECT CHECKSUM(inventory::TEXT) FROM tpcds.inventory;
+       checksum
+  -------------------
+   25223696246875800
+  (1 row)
+  ```
+
+- first(anyelement)
+
+  Description: Returns the first non-null input.
+
+  Return type: anyelement
+
+  ```sql
+  mogdb=# select * from tba;
+  name
+  -----
+  A
+  A
+  D
+  (4 rows)
+
+  mogdb=# select first(name) from tba;
+  first
+  -----
+  A
+  (1 rows)
+  ```
+
+- last(anyelement)
+
+  Description: Returns the last non-null input.
+
+  Return type: anyelement
+
+  ```sql
+  mogdb=# select * from tba;
+  name
+  -----
+  A
+  A
+  D
+  (4 rows)
+
+  mogdb=# select last(name) from tba;
+  last
+  -----
+  D
+  (1 rows)
+  ```
+
+- mode() within group (order by value anyelement)
+
+  Description: Returns the value with the highest occurrence frequency in a column. If multiple values have the same frequency, the smallest value is returned. The sorting mode is the same as the default sorting mode of the column type. **value** is an input parameter and can be of any type.
+
+  Return type: same as the input parameter type
+
+  Example:
+
+  ```sql
+  mogdb=# select mode() within group (order by value) from (values(1, 'a'), (2, 'b'), (2, 'c')) v(value, tag);
+   mode
+  ------
+      2
+  (1 row)
+  mogdb=# select mode() within group (order by tag) from (values(1, 'a'), (2, 'b'), (2, 'c')) v(value, tag);
+   mode
+  ------
+   a
+  (1 row)
+  ```
+
+- json_agg(any)
+
+  Description: Aggregates values into a JSON array.
+
+  Return type: array-json
+
+  Example:
+
+  ```sql
+  mogdb=# select * from classes;
+  name | score
+  -----+-------
+  A    |     2
+  A    |     3
+  D    |     5
+  D    |
+  (4 rows)
+  ```
+
+  ```sql
+  mogdb=# select name, json_agg(score) score from classes group by name order by name;
+  name |      score
+  -----+-----------------
+  A    | [2, 3]
+  D    | [5, null]
+  | [null]
+  (3 rows)
+  ```
+
+- json_object_agg(any, any)
+
+  Description: Aggregates values into a JSON object.
+
+  Return type: object-json
+
+  Example:
+
+  ```sql
+  mogdb=# select * from classes;
+  name | score
+  -----+-------
+  A    |     2
+  A    |     3
+  D    |     5
+  D    |
+  (4 rows)
+  ```
+
+  ```sql
+  mogdb=# select json_object_agg(name, score) from classes group by name order by name;
+  json_object_agg
+  -------------------------
+  { "A" : 2, "A" : 3 }
+  { "D" : 5, "D" : null }
+  (2 rows)
+  ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/18-window-functions.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/18-window-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..2fd67b806685658515ef074c57e2eaaa58373413
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/18-window-functions.md
@@ -0,0 +1,628 @@
+---
+title: Window Functions
+summary: Window Functions
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Window Functions
+
+Currently, column-store tables only support **rank(expression)** and **row_number(expression)** functions.
+
+Window functions and the  **OVER**  clause are used together. The  **OVER**  clause is used for grouping data and sorting the elements in a group. Window functions are used for generating sequence numbers for the values in the group.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** **order by** in a window function must be followed by a column name. If it is followed by a number, the number is processed as a constant value and the target column is not ranked.
+
+- RANK()
+
+  Description: Generates non-consecutive sequence numbers for the values in each group. The same values have the same sequence number.
+
+  Return type: bigint
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT d_moy, d_fy_week_seq, rank() OVER(PARTITION BY d_moy ORDER BY d_fy_week_seq) FROM tpcds.date_dim WHERE d_moy < 4 AND d_fy_week_seq < 7 ORDER BY 1,2;
+     d_moy | d_fy_week_seq | rank
+  -------+---------------+------
+       1 |             1 |    1
+       1 |             1 |    1
+       1 |             1 |    1
+       1 |             1 |    1
+       1 |             1 |    1
+       1 |             1 |    1
+       1 |             1 |    1
+       1 |             2 |    8
+       1 |             2 |    8
+       1 |             2 |    8
+       1 |             2 |    8
+       1 |             2 |    8
+       1 |             2 |    8
+       1 |             2 |    8
+       1 |             3 |   15
+       1 |             3 |   15
+       1 |             3 |   15
+       1 |             3 |   15
+       1 |             3 |   15
+       1 |             3 |   15
+       1 |             3 |   15
+       1 |             4 |   22
+       1 |             4 |   22
+       1 |             4 |   22
+       1 |             4 |   22
+       1 |             4 |   22
+       1 |             4 |   22
+       1 |             4 |   22
+       1 |             5 |   29
+       1 |             5 |   29
+       2 |             5 |    1
+       2 |             5 |    1
+       2 |             5 |    1
+       2 |             5 |    1
+       2 |             5 |    1
+       2 |             6 |    6
+       2 |             6 |    6
+       2 |             6 |    6
+       2 |             6 |    6
+       2 |             6 |    6
+       2 |             6 |    6
+       2 |             6 |    6
+  (42 rows)
+  ```
+
+- ROW_NUMBER()
+
+  Description: Generates consecutive sequence numbers for the values in each group. The same values have different sequence numbers.
+
+  Return type: bigint
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT d_moy, d_fy_week_seq, Row_number() OVER(PARTITION BY d_moy ORDER BY d_fy_week_seq) FROM tpcds.date_dim  WHERE d_moy < 4 AND d_fy_week_seq < 7 ORDER BY 1,2;
+   d_moy | d_fy_week_seq | row_number
+  -------+---------------+------------
+       1 |             1 |          1
+       1 |             1 |          2
+       1 |             1 |          3
+       1 |             1 |          4
+       1 |             1 |          5
+       1 |             1 |          6
+       1 |             1 |          7
+       1 |             2 |          8
+       1 |             2 |          9
+       1 |             2 |         10
+       1 |             2 |         11
+       1 |             2 |         12
+       1 |             2 |         13
+       1 |             2 |         14
+       1 |             3 |         15
+       1 |             3 |         16
+       1 |             3 |         17
+       1 |             3 |         18
+       1 |             3 |         19
+       1 |             3 |         20
+       1 |             3 |         21
+       1 |             4 |         22
+       1 |             4 |         23
+       1 |             4 |         24
+       1 |             4 |         25
+       1 |             4 |         26
+       1 |             4 |         27
+       1 |             4 |         28
+       1 |             5 |         29
+       1 |             5 |         30
+       2 |             5 |          1
+       2 |             5 |          2
+       2 |             5 |          3
+       2 |             5 |          4
+       2 |             5 |          5
+       2 |             6 |          6
+       2 |             6 |          7
+       2 |             6 |          8
+       2 |             6 |          9
+       2 |             6 |         10
+       2 |             6 |         11
+       2 |             6 |         12
+  (42 rows)
+  ```
+
+- DENSE_RANK()
+
+  Description: Generates consecutive sequence numbers for the values in each group. The same values have the same sequence number.
+
+  Return type: bigint
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT d_moy, d_fy_week_seq, dense_rank() OVER(PARTITION BY d_moy ORDER BY d_fy_week_seq) FROM tpcds.date_dim WHERE d_moy < 4 AND d_fy_week_seq < 7 ORDER BY 1,2;
+   d_moy | d_fy_week_seq | dense_rank
+  -------+---------------+------------
+       1 |             1 |          1
+       1 |             1 |          1
+       1 |             1 |          1
+       1 |             1 |          1
+       1 |             1 |          1
+       1 |             1 |          1
+       1 |             1 |          1
+       1 |             2 |          2
+       1 |             2 |          2
+       1 |             2 |          2
+       1 |             2 |          2
+       1 |             2 |          2
+       1 |             2 |          2
+       1 |             2 |          2
+       1 |             3 |          3
+       1 |             3 |          3
+       1 |             3 |          3
+       1 |             3 |          3
+       1 |             3 |          3
+       1 |             3 |          3
+       1 |             3 |          3
+       1 |             4 |          4
+       1 |             4 |          4
+       1 |             4 |          4
+       1 |             4 |          4
+       1 |             4 |          4
+       1 |             4 |          4
+       1 |             4 |          4
+       1 |             5 |          5
+       1 |             5 |          5
+       2 |             5 |          1
+       2 |             5 |          1
+       2 |             5 |          1
+       2 |             5 |          1
+       2 |             5 |          1
+       2 |             6 |          2
+       2 |             6 |          2
+       2 |             6 |          2
+       2 |             6 |          2
+       2 |             6 |          2
+       2 |             6 |          2
+       2 |             6 |          2
+  (42 rows)
+  ```
+
+- PERCENT_RANK()
+
+  Description: Generates corresponding sequence numbers for the values in each group. That is, the function calculates the value according to the formula Sequence number = (**rank** - 1) / (**total rows** - 1). **rank** is the corresponding sequence number generated based on the **RANK** function for the value and **totalrows** is the total number of elements in a group.
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT d_moy, d_fy_week_seq, percent_rank() OVER(PARTITION BY d_moy ORDER BY d_fy_week_seq) FROM tpcds.date_dim WHERE d_moy < 4 AND d_fy_week_seq < 7 ORDER BY 1,2;
+   d_moy | d_fy_week_seq |   percent_rank
+  -------+---------------+------------------
+       1 |             1 |                0
+       1 |             1 |                0
+       1 |             1 |                0
+       1 |             1 |                0
+       1 |             1 |                0
+       1 |             1 |                0
+       1 |             1 |                0
+       1 |             2 | .241379310344828
+       1 |             2 | .241379310344828
+       1 |             2 | .241379310344828
+       1 |             2 | .241379310344828
+       1 |             2 | .241379310344828
+       1 |             2 | .241379310344828
+       1 |             2 | .241379310344828
+       1 |             3 | .482758620689655
+       1 |             3 | .482758620689655
+       1 |             3 | .482758620689655
+       1 |             3 | .482758620689655
+       1 |             3 | .482758620689655
+       1 |             3 | .482758620689655
+       1 |             3 | .482758620689655
+       1 |             4 | .724137931034483
+       1 |             4 | .724137931034483
+       1 |             4 | .724137931034483
+       1 |             4 | .724137931034483
+       1 |             4 | .724137931034483
+       1 |             4 | .724137931034483
+       1 |             4 | .724137931034483
+       1 |             5 |  .96551724137931
+       1 |             5 |  .96551724137931
+       2 |             5 |                0
+       2 |             5 |                0
+       2 |             5 |                0
+       2 |             5 |                0
+       2 |             5 |                0
+       2 |             6 | .454545454545455
+       2 |             6 | .454545454545455
+       2 |             6 | .454545454545455
+       2 |             6 | .454545454545455
+       2 |             6 | .454545454545455
+       2 |             6 | .454545454545455
+       2 |             6 | .454545454545455
+  (42 rows)
+  ```
+
+- CUME_DIST()
+
+  Description: Generates accumulative distribution sequence numbers for the values in each group. That is, the function calculates the value according to the following formula: Sequence number = Number of rows preceding or peer with current row/Total rows.
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT d_moy, d_fy_week_seq, cume_dist() OVER(PARTITION BY d_moy ORDER BY d_fy_week_seq) FROM tpcds.date_dim e_dim WHERE d_moy < 4 AND d_fy_week_seq < 7 ORDER BY 1,2;
+   d_moy | d_fy_week_seq |    cume_dist
+  -------+---------------+------------------
+       1 |             1 | .233333333333333
+       1 |             1 | .233333333333333
+       1 |             1 | .233333333333333
+       1 |             1 | .233333333333333
+       1 |             1 | .233333333333333
+       1 |             1 | .233333333333333
+       1 |             1 | .233333333333333
+       1 |             2 | .466666666666667
+       1 |             2 | .466666666666667
+       1 |             2 | .466666666666667
+       1 |             2 | .466666666666667
+       1 |             2 | .466666666666667
+       1 |             2 | .466666666666667
+       1 |             2 | .466666666666667
+       1 |             3 |               .7
+       1 |             3 |               .7
+       1 |             3 |               .7
+       1 |             3 |               .7
+       1 |             3 |               .7
+       1 |             3 |               .7
+       1 |             3 |               .7
+       1 |             4 | .933333333333333
+       1 |             4 | .933333333333333
+       1 |             4 | .933333333333333
+       1 |             4 | .933333333333333
+       1 |             4 | .933333333333333
+       1 |             4 | .933333333333333
+       1 |             4 | .933333333333333
+       1 |             5 |                1
+       1 |             5 |                1
+       2 |             5 | .416666666666667
+       2 |             5 | .416666666666667
+       2 |             5 | .416666666666667
+       2 |             5 | .416666666666667
+       2 |             5 | .416666666666667
+       2 |             6 |                1
+       2 |             6 |                1
+       2 |             6 |                1
+       2 |             6 |                1
+       2 |             6 |                1
+       2 |             6 |                1
+       2 |             6 |                1
+  (42 rows)
+  ```
+
+- NTILE(num_buckets integer)
+
+  Description: Equally allocates sequential data sets to the buckets whose quantity is specified by  **num_buckets**  according to  **num_buckets integer**  and allocates the bucket number to each row. Divide the partition as evenly as possible.
+
+  Return type: integer
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT d_moy, d_fy_week_seq, ntile(3) OVER(PARTITION BY d_moy ORDER BY d_fy_week_seq) FROM tpcds.date_dim WHERE d_moy < 4 AND d_fy_week_seq < 7 ORDER BY 1,2;
+   d_moy | d_fy_week_seq | ntile
+  -------+---------------+-------
+       1 |             1 |     1
+       1 |             1 |     1
+       1 |             1 |     1
+       1 |             1 |     1
+       1 |             1 |     1
+       1 |             1 |     1
+       1 |             1 |     1
+       1 |             2 |     1
+       1 |             2 |     1
+       1 |             2 |     1
+       1 |             2 |     2
+       1 |             2 |     2
+       1 |             2 |     2
+       1 |             2 |     2
+       1 |             3 |     2
+       1 |             3 |     2
+       1 |             3 |     2
+       1 |             3 |     2
+       1 |             3 |     2
+       1 |             3 |     2
+       1 |             3 |     3
+       1 |             4 |     3
+       1 |             4 |     3
+       1 |             4 |     3
+       1 |             4 |     3
+       1 |             4 |     3
+       1 |             4 |     3
+       1 |             4 |     3
+       1 |             5 |     3
+       1 |             5 |     3
+       2 |             5 |     1
+       2 |             5 |     1
+       2 |             5 |     1
+       2 |             5 |     1
+       2 |             5 |     2
+       2 |             6 |     2
+       2 |             6 |     2
+       2 |             6 |     2
+       2 |             6 |     3
+       2 |             6 |     3
+       2 |             6 |     3
+       2 |             6 |     3
+  (42 rows)
+  ```
+
+- LAG(value any [, offset integer [, default any ]])
+
+  Description: Generates lag values for the corresponding values in each group. That is, the value of the row obtained by moving forward the row corresponding to the current value by  **offset**  (integer) is the sequence number. If the row does not exist after the moving, the result value is the default value. If omitted,  **offset**  defaults to  **1**  and  **default**  to  **NULL**.
+
+  Return type: same as the parameter type
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT d_moy, d_fy_week_seq, lag(d_moy,3,null) OVER(PARTITION BY d_moy ORDER BY d_fy_week_seq) FROM tpcds.date_dim WHERE d_moy < 4 AND d_fy_week_seq < 7 ORDER BY 1,2;
+   d_moy | d_fy_week_seq | lag
+  -------+---------------+-----
+       1 |             1 |
+       1 |             1 |
+       1 |             1 |
+       1 |             1 |   1
+       1 |             1 |   1
+       1 |             1 |   1
+       1 |             1 |   1
+       1 |             2 |   1
+       1 |             2 |   1
+       1 |             2 |   1
+       1 |             2 |   1
+       1 |             2 |   1
+       1 |             2 |   1
+       1 |             2 |   1
+       1 |             3 |   1
+       1 |             3 |   1
+       1 |             3 |   1
+       1 |             3 |   1
+       1 |             3 |   1
+       1 |             3 |   1
+       1 |             3 |   1
+       1 |             4 |   1
+       1 |             4 |   1
+       1 |             4 |   1
+       1 |             4 |   1
+       1 |             4 |   1
+       1 |             4 |   1
+       1 |             4 |   1
+       1 |             5 |   1
+       1 |             5 |   1
+       2 |             5 |
+       2 |             5 |
+       2 |             5 |
+       2 |             5 |   2
+       2 |             5 |   2
+       2 |             6 |   2
+       2 |             6 |   2
+       2 |             6 |   2
+       2 |             6 |   2
+       2 |             6 |   2
+       2 |             6 |   2
+       2 |             6 |   2
+  (42 rows)
+  ```
+
+- LEAD(value any [, offset integer [, default any ]])
+
+  Description: Generates leading values for the corresponding values in each group. That is, the value of the row obtained by moving backward the row corresponding to the current value by **offset** (integer) is the sequence number. If the row after the moving exceeds the total number of rows for the current group, the result value is the default value. If omitted, **offset** defaults to **1** and **default** to **NULL**.
+
+  Return type: same as the parameter type
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT d_moy, d_fy_week_seq, lead(d_fy_week_seq,2) OVER(PARTITION BY d_moy ORDER BY d_fy_week_seq) FROM  tpcds.date_dim WHERE d_moy < 4 AND d_fy_week_seq < 7 ORDER BY 1,2;
+  d_moy | d_fy_week_seq | lead
+  -------+---------------+------
+       1 |             1 |    1
+       1 |             1 |    1
+       1 |             1 |    1
+       1 |             1 |    1
+       1 |             1 |    1
+       1 |             1 |    2
+       1 |             1 |    2
+       1 |             2 |    2
+       1 |             2 |    2
+       1 |             2 |    2
+       1 |             2 |    2
+       1 |             2 |    2
+       1 |             2 |    3
+       1 |             2 |    3
+       1 |             3 |    3
+       1 |             3 |    3
+       1 |             3 |    3
+       1 |             3 |    3
+       1 |             3 |    3
+       1 |             3 |    4
+       1 |             3 |    4
+       1 |             4 |    4
+       1 |             4 |    4
+       1 |             4 |    4
+       1 |             4 |    4
+       1 |             4 |    4
+       1 |             4 |    5
+       1 |             4 |    5
+       1 |             5 |
+       1 |             5 |
+       2 |             5 |    5
+       2 |             5 |    5
+       2 |             5 |    5
+       2 |             5 |    6
+       2 |             5 |    6
+       2 |             6 |    6
+       2 |             6 |    6
+       2 |             6 |    6
+       2 |             6 |    6
+       2 |             6 |    6
+       2 |             6 |
+       2 |             6 |
+  (42 rows)
+  ```
+
+- FIRST_VALUE(value any)
+
+  Description: Returns the first value of each group.
+
+  Return type: same as the parameter type
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT d_moy, d_fy_week_seq, first_value(d_fy_week_seq) OVER(PARTITION BY d_moy ORDER BY d_fy_week_seq) FROM tpcds.date_dim WHERE d_moy < 4 AND d_fy_week_seq < 7 ORDER BY 1,2;
+   d_moy | d_fy_week_seq | first_value
+  -------+---------------+-------------
+       1 |             1 |           1
+       1 |             1 |           1
+       1 |             1 |           1
+       1 |             1 |           1
+       1 |             1 |           1
+       1 |             1 |           1
+       1 |             1 |           1
+       1 |             2 |           1
+       1 |             2 |           1
+       1 |             2 |           1
+       1 |             2 |           1
+       1 |             2 |           1
+       1 |             2 |           1
+       1 |             2 |           1
+       1 |             3 |           1
+       1 |             3 |           1
+       1 |             3 |           1
+       1 |             3 |           1
+       1 |             3 |           1
+       1 |             3 |           1
+       1 |             3 |           1
+       1 |             4 |           1
+       1 |             4 |           1
+       1 |             4 |           1
+       1 |             4 |           1
+       1 |             4 |           1
+       1 |             4 |           1
+       1 |             4 |           1
+       1 |             5 |           1
+       1 |             5 |           1
+       2 |             5 |           5
+       2 |             5 |           5
+       2 |             5 |           5
+       2 |             5 |           5
+       2 |             5 |           5
+       2 |             6 |           5
+       2 |             6 |           5
+       2 |             6 |           5
+       2 |             6 |           5
+       2 |             6 |           5
+       2 |             6 |           5
+       2 |             6 |           5
+  (42 rows)
+  ```
+
+- LAST_VALUE(value any)
+
+  Description: Returns the last value of each group.
+
+  Return type: same as the parameter type
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT d_moy, d_fy_week_seq, last_value(d_moy) OVER(PARTITION BY d_moy ORDER BY d_fy_week_seq) FROM tpcds.date_dim WHERE d_moy < 4 AND d_fy_week_seq < 6 ORDER BY 1,2;
+    d_moy | d_fy_week_seq | last_value
+  -------+---------------+------------
+       1 |             1 |          1
+       1 |             1 |          1
+       1 |             1 |          1
+       1 |             1 |          1
+       1 |             1 |          1
+       1 |             1 |          1
+       1 |             1 |          1
+       1 |             2 |          1
+       1 |             2 |          1
+       1 |             2 |          1
+       1 |             2 |          1
+       1 |             2 |          1
+       1 |             2 |          1
+       1 |             2 |          1
+       1 |             2 |          1
+       1 |             3 |          1
+       1 |             3 |          1
+       1 |             3 |          1
+       1 |             3 |          1
+       1 |             3 |          1
+       1 |             3 |          1
+       1 |             3 |          1
+       1 |             4 |          1
+       1 |             4 |          1
+       1 |             4 |          1
+       1 |             4 |          1
+       1 |             4 |          1
+       1 |             4 |          1
+       1 |             4 |          1
+       1 |             5 |          1
+       1 |             5 |          1
+       2 |             5 |          2
+       2 |             5 |          2
+       2 |             5 |          2
+       2 |             5 |          2
+       2 |             5 |          2
+  (35 rows)
+  ```
+
+- NTH_VALUE(value any, nth integer)
+
+  Description: Returns the  _n_th row for a group. If the row does not exist,  **NULL**  is returned by default.
+
+  Return type: same as the parameter type
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT d_moy, d_fy_week_seq, nth_value(d_fy_week_seq,6) OVER(PARTITION BY d_moy ORDER BY d_fy_week_seq) FROM tpcds.date_dim WHERE d_moy < 4 AND d_fy_week_seq < 6 ORDER BY 1,2;
+   d_moy | d_fy_week_seq | nth_value
+  -------+---------------+-----------
+       1 |             1 |         1
+       1 |             1 |         1
+       1 |             1 |         1
+       1 |             1 |         1
+       1 |             1 |         1
+       1 |             1 |         1
+       1 |             1 |         1
+       1 |             2 |         1
+       1 |             2 |         1
+       1 |             2 |         1
+       1 |             2 |         1
+       1 |             2 |         1
+       1 |             2 |         1
+       1 |             2 |         1
+       1 |             3 |         1
+       1 |             3 |         1
+       1 |             3 |         1
+       1 |             3 |         1
+       1 |             3 |         1
+       1 |             3 |         1
+       1 |             3 |         1
+       1 |             4 |         1
+       1 |             4 |         1
+       1 |             4 |         1
+       1 |             4 |         1
+       1 |             4 |         1
+       1 |             4 |         1
+       1 |             4 |         1
+       1 |             5 |         1
+       1 |             5 |         1
+       2 |             5 |
+       2 |             5 |
+       2 |             5 |
+       2 |             5 |
+       2 |             5 |
+  (35 rows)
+  ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/19-security-functions.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/19-security-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..c8c0da17059b165e229deb8d71c73e50d7562717
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/19-security-functions.md
@@ -0,0 +1,263 @@
+---
+title: Security Functions
+summary: Security Functions
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Security Functions
+
+- gs_encrypt_aes128(encryptstr,keystr)
+
+  Description: Encrypts **encryptstr** strings using **keystr** as the key and returns encrypted strings. The value of **keystr** ranges from 8 to 16 bytes and contains at least three types of the following characters: uppercase letters, lowercase letters, digits, and special characters.
+
+  Return type: text
+
+  Length of the return value: At least 92 bytes and no more than (4 \* [*Len*/3] + 68 ) bytes, where *Len* indicates the length of the data before encryption (unit: byte).
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT gs_encrypt_aes128('MPPDB','Asdf1234');
+
+                                 gs_encrypt_aes128
+  -------------------------------------------------------------------------------------
+  gwditQLQG8NhFw4OuoKhhQJoXojhFlYkjeG0aYdSCtLCnIUgkNwvYI04KbuhmcGZp8jWizBdR1vU9CspjuzI0lbz12A=
+  (1 row)
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** A decryption password is required during the execution of this function. For security purposes, the **gsql** tool does not record the function in the execution history. That is, the execution history of this function cannot be found in **gsql** by paging up and down.
+
+- gs_encrypt(encryptstr,keystr, encrypttype)
+
+  Description: Encrypts **encryptstr** strings using **keystr** as the key and returns encrypted strings based on **encrypttype**. The value of **keystr** contains 8 to 16 bytes and at least three types of the following characters: uppercase letters, lowercase letters, digits, and special characters. The value of **encrypttype** can be **aes128** or **sm4**.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=#  SELECT gs_encrypt('MPPDB','Asdf1234','sm4');
+           gs_encrypt
+   ------------------------------
+   ZBzOmaGA4Bb+coyucJ0B8AkIShqc
+  (1 row)
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** A decryption password is required during the execution of this function. For security purposes, the **gsql** tool does not record the function in the execution history. That is, the execution history of this function cannot be found in **gsql** by paging up and down.
+
+- gs_decrypt_aes128(decryptstr,keystr)
+
+  Description: Decrypts **decrypt** strings using **keystr** as the key and returns decrypted strings. The **keystr** used for decryption must be consistent with that used for encryption. **keystr** cannot be empty.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** This parameter needs to be used with the **gs_encrypt_aes128** encryption function.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT gs_decrypt_aes128('gwditQLQG8NhFw4OuoKhhQJoXojhFlYkjeG0aYdSCtLCnIUgkNwvYI04KbuhmcGZp8jWizBdR1vU9CspjuzI0lbz12A=','1234');
+   gs_decrypt_aes128
+  -------------------
+   MPPDB
+  (1 row)
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** A decryption password is required during the execution of this function. For security purposes, the **gsql** tool does not record the function in the execution history. That is, the execution history of this function cannot be found in **gsql** by paging up and down.
+
+- gs_decrypt(decryptstr, keystr, decrypttype)
+
+  Description: Decrypts **decrypt** strings using **keystr** as the key and returns decrypted strings based on **decrypttype**. The **decrypttype** and **keystr** used for decryption must be consistent with those used for encryption. The value of **keystr** cannot be empty. The value of **decrypttype** can be **aes128** or **sm4**.
+
+  This function needs to be used with the **gs_encrypt** encryption function.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# select gs_decrypt('ZBzOmaGA4Bb+coyucJ0B8AkIShqc','Asdf1234','sm4');
+   gs_decrypt
+  ------------
+   MPPDB
+  (1 row)
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** A decryption password is required during the execution of this function. For security purposes, the **gsql** tool does not record the function in the execution history. That is, the execution history of this function cannot be found in **gsql** by paging up and down.
+
+- gs_password_deadline
+
+  Description: Indicates the number of remaining days before the password of the current user expires.
+
+  Return type: interval
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT gs_password_deadline();
+    gs_password_deadline
+  -------------------------
+   83 days 17:44:32.196094
+  (1 row)
+  ```
+
+- gs_password_notifytime
+
+  Description: Specifies the number of days prior to password expiration that a user will receive a reminder.
+
+  Return type: int32
+
+- login_audit_messages
+
+  Description: Queries login information about a login user.
+
+  Return type: tuple
+
+  Example:
+
+  - Check the date, time, and IP address successfully authenticated during the last login.
+
+    ```sql
+    mogdb=> select * from login_audit_messages(true);
+    username | database |       logintime        |    mytype     | result | client_conninfo
+    ----------+----------+------------------------+---------------+--------+-----------------
+    omm      | openGauss | 2020-06-29 21:56:40+08 | login_success | ok     | gsql@[local]
+    (1 row)
+    ```
+
+  - Check the date, time, and IP address that failed to be authenticated during the last login.
+
+    ```sql
+    mogdb=>  select * from login_audit_messages(false) ORDER BY logintime desc limit 1;
+    username | database |       logintime        |    mytype    | result |  client_conninfo
+    ----------+----------+------------------------+--------------+--------+-------------------
+    omm      | openGauss | 2020-06-29 21:57:55+08 | login_failed | failed | [unknown]@[local]
+    (1 row)
+    ```
+
+  - Check the number of failed attempts, date, and time since the previous successful authentication.
+
+    ```sql
+    mogdb=>  select * from login_audit_messages(false);
+    username | database |       logintime        |    mytype    | result |  client_conninfo
+    ----------+----------+------------------------+--------------+--------+-------------------
+    omm      | openGauss | 2020-06-29 21:57:55+08 | login_failed | failed | [unknown]@[local]
+    omm      | openGauss | 2020-06-29 21:57:53+08 | login_failed | failed | [unknown]@[local]
+    (2 rows)
+    ```
+
+- login_audit_messages_pid
+
+  Description: Queries login information about a login user. Different from **login_audit_messages**, this function queries login information based on **backendid**. Information about subsequent logins of the same user does not alter the query result of previous logins and cannot be found using this function.
+
+  Return type: tuple
+
+  Example:
+
+  - Check the date, time, and IP address successfully authenticated during the last login.
+
+    ```sql
+    mogdb=> SELECT * FROM login_audit_messages_pid(true);
+    username | database |       logintime        |    mytype     | result | client_conninfo |    backendid
+    ----------+----------+------------------------+---------------+--------+-----------------+-----------------
+    omm      | openGauss | 2020-06-29 21:56:40+08 | login_success | ok     | gsql@[local]    | 139823109633792
+    (1 row)
+    ```
+
+  - Check the date, time, and IP address that failed to be authenticated during the last login.
+
+    ```sql
+    mogdb=> SELECT * FROM login_audit_messages_pid(false) ORDER BY logintime desc limit 1;
+    username | database |       logintime        |    mytype    | result |  client_conninfo  |    backendid
+    ----------+----------+------------------------+--------------+--------+-------------------+-----------------
+    omm      | openGauss | 2020-06-29 21:57:55+08 | login_failed | failed | [unknown]@[local] | 139823109633792
+    (1 row)
+    ```
+
+  - Check the number of failed attempts, date, and time since the previous successful authentication.
+
+    ```sql
+    mogdb=> SELECT * FROM login_audit_messages_pid(false);
+    username | database |       logintime        |    mytype    | result |  client_conninfo  |    backendid
+    ----------+----------+------------------------+--------------+--------+-------------------+-----------------
+    omm      | openGauss | 2020-06-29 21:57:55+08 | login_failed | failed | [unknown]@[local] | 139823109633792
+    omm      | openGauss | 2020-06-29 21:57:53+08 | login_failed | failed | [unknown]@[local] | 139823109633792
+    (2 rows)
+    ```
+
+- inet_server_addr
+
+  Description: Displays the server IP address.
+
+  Return type: inet
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT inet_server_addr();
+   inet_server_addr
+  ------------------
+   10.10.0.13
+  (1 row)
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > - The client IP address 10.10.0.50 and server IP address 10.10.0.13 are used as an example.
+  > - If the database is connected to the local PC, the value is empty.
+
+- inet_client_addr
+
+  Description: Displays the client IP address.
+
+  Return type: inet
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT inet_client_addr();
+   inet_client_addr
+  ------------------
+   10.10.0.50
+  (1 row)
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > - The client IP address 10.10.0.50 and server IP address 10.10.0.13 are used as an example.
+  > - If the database is connected to the local PC, the value is empty.
+
+- pg_query_audit
+
+  Description: Views audit logs of the primary database node.
+
+  Return type: record
+
+  The following table describes return fields.
+
+  | Name            | Type                     | Description                                 |
+  | :-------------- | :----------------------- | :------------------------------------------ |
+  | time            | timestamp with time zone | Operation time                              |
+  | type            | text                     | Operation                                   |
+  | result          | text                     | Operation result                            |
+  | userid          | oid                      | User ID                                     |
+  | username        | text                     | Name of the user who performs the operation |
+  | database        | text                     | Database name                               |
+  | client_conninfo | text                     | Client connection information               |
+  | object_name     | text                     | Object name                                 |
+  | detail_info     | text                     | Operation details                           |
+  | node_name       | text                     | Node name                                   |
+  | thread_id       | text                     | Thread ID                                   |
+  | local_port      | text                     | Local port                                  |
+  | remote_port     | text                     | Remote port                                 |
+
+  For details about how to use the function and details about function examples, see [Querying Audit Results](3-configuring-database-audit#querying-audit-results).
+
+- pg_delete_audit
+
+  Description: Deletes audit logs in a specified period.
+
+  Return value type: void
+
+  For details about how to use the function and details about function examples, see [Maintaining Audit Logs](3-configuring-database-audit#maintaining-audit-logs).
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/2-comparison-operators.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/2-comparison-operators.md
new file mode 100644
index 0000000000000000000000000000000000000000..edf5f626cac33be7726e62cf88be9508c6cc4356
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/2-comparison-operators.md
@@ -0,0 +1,27 @@
+---
+title: Comparison Operators
+summary: Comparison Operators
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Comparison Operators
+
+Comparison operators are available for the most data types and return Boolean values.
+
+All comparison operators are binary operators. Only data types that are the same or can be implicitly converted can be compared using comparison operators.
+
+Table 1 describes comparison operators provided by MogDB.
+
+**Table 1** Comparison operators
+
+| Operator           | Description              |
+| :----------------- | :----------------------- |
+| &lt;               | Less than                |
+| &gt;               | Greater than             |
+| &lt;=              | Less than or equal to    |
+| &gt;=              | Greater than or equal to |
+| =                  | Equal to                 |
+| &lt;&gt;, != or ^= | Not equal to             |
+
+Comparison operators are available for all relevant data types. All comparison operators are binary operators that returned values of Boolean type. The calculation priority of the inequality sign is higher than that of the equality sign. If the entered data is different and cannot be implicitly converted, the comparison fails. For example, an expression such as 1&lt;2&lt;3 is invalid because the less-than sign (&lt;) cannot be used to compare Boolean values and 3.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/20-encrypted-equality-functions.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/20-encrypted-equality-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..0d2eeb89a19c4500063c5e3abbf81b2552bfccd6
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/20-encrypted-equality-functions.md
@@ -0,0 +1,188 @@
+---
+title: Encrypted Equality Functions
+summary: Encrypted Equality Functions
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Encrypted Equality Functions
+
+- byteawithoutorderwithequalcolin(cstring)
+
+  Description: Converts input data to the internal byteawithoutorderwithequalcol format.
+
+  Parameter type: cstring
+
+  Return type: byteawithoutorderwithequalcol
+
+- byteawithoutorderwithequalcolout(byteawithoutorderwithequalcol)
+
+  Description: Converts internal data of the byteawithoutorderwithequalcol type to data of the cstring type.
+
+  Parameter type: byteawithoutorderwithequalcol
+
+  Return type: cstring
+
+- byteawithoutorderwithequalcolsend(byteawithoutorderwithequalcol)
+
+  Description: Converts data of the byteawithoutorderwithequalcol type to data of the bytea type.
+
+  Parameter type: byteawithoutorderwithequalcol
+
+  Return type: bytea
+
+- byteawithoutorderwithequalcolrecv(internal)
+
+  Description: Converts data of the byteawithoutorderwithequalcol type to data of the byteawithoutorderwithequalcol type.
+
+  Parameter type: internal
+
+  Return type: byteawithoutorderwithequalcol
+
+- byteawithoutorderwithequalcoltypmodin(cstring)
+
+  Description: Converts data of the byteawithoutorderwithequalcol type to data of the byteawithoutorderwithequalcol type.
+
+  Parameter type: cstring
+
+  Return type: int4
+
+- byteawithoutorderwithequalcoltypmodout(int4)
+
+  Description: Converts data of the int4 type into data of the cstring type.
+
+  Parameter type: int4
+
+  Return type: cstring
+
+- byteawithoutordercolin(cstring)
+
+  Description: Converts input data to the internal byteawithoutordercolin format.
+
+  Parameter type: cstring
+
+  Return type: byteawithoutordercol
+
+- byteawithoutordercolout(byteawithoutordercol)
+
+  Description: Converts internal data of the byteawithoutordercol type to data of the cstring type.
+
+  Parameter type: byteawithoutordercol
+
+  Return type: cstring
+
+- byteawithoutordercolsend(byteawithoutordercol)
+
+  Description: Converts data of the byteawithoutordercol type to data of the bytea type.
+
+  Parameter type: byteawithoutordercol
+
+  Return type: bytea
+
+- byteawithoutordercolrecv(internal)
+
+  Description: Converts data of the byteawithoutordercol type to data of the byteawithoutordercol type.
+
+  Parameter type: internal
+
+  Return type: byteawithoutordercol
+
+- byteawithoutorderwithequalcolcmp(byteawithoutorderwithequalcol, byteawithoutorderwithequalcol)
+
+  Description: Compares two byteawithoutorderwithequalcol data sizes. If the first data size is smaller than the second one, **-1** is returned. If the first data size is equal to the second one, **0** is returned. If the first data size is larger than the second one, **1** is returned.
+
+  Parameter type: byteawithoutorderwithequalcol, byteawithoutorderwithequalcol
+
+  Return type: int4
+
+- byteawithoutorderwithequalcolcmpbytear(byteawithoutorderwithequalcol, bytea)
+
+  Description: Compares the byteawithoutorderwithequalcol and bytea data sizes. If the first data size is smaller than the second one, **-1** is returned. If the first data size is equal to the second one, **0** is returned. If the first data size is larger than the second one, **1** is returned.
+
+  Parameter type: byteawithoutorderwithequalcol, bytea
+
+  Return type: int4
+
+- byteawithoutorderwithequalcolcmpbyteal(bytea, byteawithoutorderwithequalcol)
+
+  Description: Compares the bytea and byteawithoutorderwithequalcol data sizes. If the first data size is smaller than the second one, **-1** is returned. If the first data size is equal to the second one, **0** is returned. If the first data size is larger than the second one, **1** is returned.
+
+  Parameter type: byteawithoutorderwithequalcol, bytea
+
+  Return type: int4
+
+- byteawithoutorderwithequalcoleq(byteawithoutorderwithequalcol, byteawithoutorderwithequalcol)
+
+  Description: Compares two byteawithoutorderwithequalcol data records. If they are the same, **true** is returned. Otherwise, **false** is returned.
+
+  Parameter type: byteawithoutorderwithequalcol, bytea
+
+  Return type: Boolean
+
+- byteawithoutorderwithequalcoleqbyteal(bytea, byteawithoutorderwithequalcol)
+
+  Description: Compares the bytea and byteawithoutorderwithequalcol data records. If they are the same, **true** is returned. Otherwise, **false** is returned.
+
+  Parameter type: bytea, byteawithoutorderwithequalcol
+
+  Return type: Boolean
+
+- byteawithoutorderwithequalcoleqbytear(byteawithoutorderwithequalcol, bytea)
+
+  Description: Compares the byteawithoutorderwithequalcol and bytea data records. If they are the same, **true** is returned. Otherwise, **false** is returned.
+
+  Parameter type: byteawithoutorderwithequalcol, bytea
+
+  Return type: Boolean
+
+- byteawithoutorderwithequalcolne(byteawithoutorderwithequalcol, byteawithoutorderwithequalcol)
+
+  Description: Compares two byteawithoutorderwithequalcol data records. If they are different, **true** is returned. Otherwise, **false** is returned.
+
+  Parameter type: byteawithoutorderwithequalcol, byteawithoutorderwithequalcol
+
+  Return type: Boolean
+
+- byteawithoutorderwithequalcolnebyteal(bytea, byteawithoutorderwithequalcol)
+
+  Description: Compares the bytea and byteawithoutorderwithequalcol data records. If they are the same,  **true** is returned. Otherwise,  **false** is returned.
+
+  Parameter type: bytea, byteawithoutorderwithequalcol
+
+  Return type: Boolean
+
+- byteawithoutorderwithequalcolnebytear(byteawithoutorderwithequalcol, bytea)
+
+  Description: Compares the byteawithoutorderwithequalcol and bytea data records. If they are the same, **true** is returned. Otherwise, **false** is returned.
+
+  Parameter type: byteawithoutorderwithequalcol, bytea
+
+  Return type: Boolean
+
+- hll_hash_byteawithoutorderwithequalcol(byteawithoutorderwithequalcol)
+
+  Description: Returns the hll hash value of byteawithoutorderwithequalcol.
+
+  Parameter type: byteawithoutorderwithequalcol
+
+  Return type: hll_hashval
+
+  The implementation of byteawithoutorderwithequalcolin searches for CEK and determines whether it is a normal encrypted data type. Therefore, an error is reported when the user directly uses the function.
+
+  ```sql
+  mogdb=# SELECT * FROM byteawithoutorderwithequalcolsend('\x907219912381298461289346129'::byteawithoutorderwithequalcol);
+  ERROR:  cek with OID 596711794 not found
+  LINE 1: SELECT * FROM byteawithoutorderwithequalcolsend('\x907219912...
+                                                          ^
+  mogdb=# SELECT * FROM byteawithoutordercolout('\x90721901999999999999912381298461289346129');
+  ERROR:  cek with OID 2566986098 not found
+  LINE 1: SELECT * FROM byteawithoutordercolout('\x9072190199999999999...
+
+  SELECT * FROM byteawithoutorderwithequalcolrecv('\x90721901999999999999912381298461289346129'::byteawithoutorderwithequalcol);
+  ERROR:  cek with OID 2566986098 not found
+                                             ^
+  mogdb=# SELECT * FROM byteawithoutorderwithequalcolsend('\x90721901999999999999912381298461289346129'::byteawithoutorderwithequalcol);
+  ERROR:  cek with OID 2566986098 not found
+  LINE 1: SELECT * FROM byteawithoutorderwithequalcolsend('\x907219019...
+                                                          ^
+  ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/20.1-ledger-database-functions.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/20.1-ledger-database-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..bd9339701559ec414ec9de0a8acec6936f581ca0
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/20.1-ledger-database-functions.md
@@ -0,0 +1,96 @@
+---
+title: Ledger Database Functions
+summary: Ledger Database Functions
+author: Guo Huan
+date: 2021-10-28
+---
+
+# Ledger Database Functions
+
+- get_dn_hist_relhash(text, text)
+
+  Description: Returns the hash value of table-level data in a specified tamper-proof user table. This function is used only in distributed mode.
+
+  Parameter type: text
+
+  Return type: hash16
+
+- ledger_hist_check(text, text)
+
+  Description: Verifies the consistency between the hash value of table-level data in a specified tamper-proof user table and that in the corresponding history table.
+
+  Parameter type: text
+
+  Return type: Boolean
+
+- ledger_hist_repair(text, text)
+
+  Description: Restores the hash value of the history table corresponding to the specified tamper-proof user table to be the same as that of the user table, and returns the hash difference.
+
+  Parameter type: text
+
+  Return type: hash16
+
+- ledger_hist_archive(text, text)
+
+  Description: Archives the history table corresponding to a specified tamper-proof user table to the **hist_back** folder in the audit log directory.
+
+  Parameter type: text
+
+  Return type: Boolean
+
+- ledger_gchain_check(text, text)
+
+  Description: Verifies the consistency between the history table hash corresponding to the specified tamper-proof user table and the **relhash** corresponding to the global history table.
+
+  Parameter type: text
+
+  Return type: Boolean
+
+- ledger_gchain_repair(text, text)
+
+  Description: Restores **relhash** of a specified tamper-proof user table in the global history table so that the hash is the same as that in the history table, and returns the hash difference.
+
+  Parameter type: text
+
+  Return type: hash16
+
+- ledger_gchain_archive(void)
+
+  Description: Archives global history tables to the **hist_back** folder in the audit log directory.
+
+  Parameter type: void
+
+  Return type: Boolean
+
+- hash16in(cstring)
+
+  Description: Converts the input hexadecimal string into the internal hash16 format.
+
+  Parameter type: cstring
+
+  Return type: hash16
+
+- hash16out(hash16)
+
+  Description: Converts internal hash16 data to hexadecimal cstring data.
+
+  Parameter type: hash16
+
+  Return type: cstring
+
+- hash32in(cstring)
+
+  Description: Converts the input hexadecimal string (32 characters) into the internal type hash32.
+
+  Parameter type: cstring
+
+  Return type: hash32
+
+- hash32out(hash32)
+
+  Description: Converts internal hash32 data to hexadecimal cstring data.
+
+  Parameter type: cstring
+
+  Return type: hash32
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/21-set-returning-functions.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/21-set-returning-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..20e7e991eea7737b0a2f3a50e62384837dc3a0a3
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/21-set-returning-functions.md
@@ -0,0 +1,131 @@
+---
+title: Set Returning Functions
+summary: Set Returning Functions
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Set Returning Functions
+
+## Series Generating Functions
+
+- generate_series(start, stop)
+
+  Description: Generates a series of values, from **start** to **stop** with a step size of one.
+
+  Parameter type: int, bigint, numeric
+
+  Return type: setof int, setof bigint, setof numeric (same as the parameter type)
+
+- generate_series(start, stop, step)
+
+  Description: Generates a series of values, from **start** to **stop** with a step size of **step**.
+
+  Parameter type: int, bigint, numeric
+
+  Return type: setof int, setof bigint, setof numeric (same as the parameter type)
+
+- generate_series(start, stop, step interval)
+
+  Description: Generates a series of values, from **start** to **stop** with a step size of **step**.
+
+  Parameter type: timestamp or timestamp with time zone
+
+  Return type: setof timestamp or setof timestamp with time zone (same as parameter type)
+
+When **step** is positive, zero rows are returned if **start** is greater than **stop**. Conversely, when **step** is negative, zero rows are returned if **start** is less than **stop**. Zero rows are also returned for **NULL** inputs. It is an error for **step** to be zero.
+
+Example:
+
+```sql
+mogdb=# SELECT * FROM generate_series(2,4);
+ generate_series
+-----------------
+               2
+               3
+               4
+(3 rows)
+
+mogdb=# SELECT * FROM generate_series(5,1,-2);
+ generate_series
+-----------------
+               5
+               3
+               1
+(3 rows)
+
+mogdb=# SELECT * FROM generate_series(4,3);
+ generate_series
+-----------------
+(0 rows)
+
+-- This example applies to the date-plus-integer operator.
+mogdb=# SELECT current_date + s.a AS dates FROM generate_series(0,14,7) AS s(a);
+   dates
+------------
+ 2017-06-02
+ 2017-06-09
+ 2017-06-16
+(3 rows)
+
+mogdb=# SELECT * FROM generate_series('2008-03-01 00:00'::timestamp, '2008-03-04 12:00', '10 hours');
+   generate_series
+---------------------
+ 2008-03-01 00:00:00
+ 2008-03-01 10:00:00
+ 2008-03-01 20:00:00
+ 2008-03-02 06:00:00
+ 2008-03-02 16:00:00
+ 2008-03-03 02:00:00
+ 2008-03-03 12:00:00
+ 2008-03-03 22:00:00
+ 2008-03-04 08:00:00
+(9 rows)
+```
+
+## Subscript Generating Functions
+
+- generate_subscripts(array anyarray, dim int)
+
+  Description: Generates a series comprising the given array's subscripts.
+
+  Return type: setof int
+
+- generate_subscripts(array anyarray, dim int, reverse boolean)
+
+  Description: Generates a series comprising the given array's subscripts. When **reverse** is true, the series is returned in reverse order.
+
+  Return type: setof int
+
+**generate_subscripts** is a function that generates the set of valid subscripts for the specified dimension of the given array. Zero rows are returned for arrays that do not have the requested dimension, or for NULL arrays (but valid subscripts are returned for NULL array elements). Example:
+
+```sql
+-- Basic usage
+mogdb=# SELECT generate_subscripts('{NULL,1,NULL,2}'::int[], 1) AS s;
+ s
+---
+ 1
+ 2
+ 3
+ 4
+(4 rows)
+-- Unnest a 2D array:
+mogdb=# CREATE OR REPLACE FUNCTION unnest2(anyarray)
+RETURNS SETOF anyelement AS $$
+SELECT $1[i][j]
+   FROM generate_subscripts($1,1) g1(i),
+        generate_subscripts($1,2) g2(j);
+$$ LANGUAGE sql IMMUTABLE;
+
+mogdb=# SELECT * FROM unnest2(ARRAY[[1,2],[3,4]]);
+ unnest2
+---------
+       1
+       2
+       3
+       4
+(4 rows)
+
+-- Delete the function.
+mogdb=# DROP FUNCTION unnest2;
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/22-conditional-expressions-functions.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/22-conditional-expressions-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..d8ef0e869c86475dcf33d146bbb13a6e814193eb
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/22-conditional-expressions-functions.md
@@ -0,0 +1,175 @@
+---
+title: Conditional Expression Functions
+summary: Conditional Expression Functions
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Conditional Expression Functions
+
+- coalesce(expr1, expr2, …, exprn)
+
+  Description:
+
+  Returns the first of its parameters that are not null.
+
+  **COALESCE(expr1, expr2)** is equivalent to **CASE WHEN expr1 IS NOT NULL THEN expr1 ELSE expr2 END**.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT coalesce(NULL,'hello');
+   coalesce
+  ----------
+   hello
+  (1 row)
+  ```
+
+  Note:
+
+  - If all the expressions are equivalent to NULL in the expression list, this function returns **NULL**.
+  - This value is replaced by the default value when data is displayed.
+  - Like a **CASE** expression, **COALESCE** only evaluates the parameters that are needed to determine the result. That is, parameters to the right of the first not-**NULL** parameter are not evaluated.
+
+- decode(base_expr, compare1, value1, Compare2,value2, … default)
+
+  Description: Compares **base_expr** with each **compare(n)** and **returns value(n)** if they are matched. If **base_expr** does not match each **compare(n)**, the default value is returned.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT decode('A','A',1,'B',2,0);
+   case
+  ------
+   1
+  (1 row)
+  ```
+
+- nullif(expr1, expr2)
+
+  Description: Returns **NULL** only when **expr1** is equal to **expr2**. Otherwise, **expr1** is returned.
+
+  **nullif(expr1, expr2)** is equivalent to **CASE WHEN expr1 = expr2 THEN NULL ELSE expr1 END**.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT nullif('hello','world');
+   nullif
+  --------
+   hello
+  (1 row)
+  ```
+
+  Note:
+
+  Assume the two parameter data types are different:
+
+  - If implicit conversion exists between the two data types, implicitly convert the parameter of lower priority to this data type using the data type of higher priority. If the conversion succeeds, computation is performed. Otherwise, an error is returned. Example:
+
+    ```sql
+    mogdb=# SELECT nullif('1234'::VARCHAR,123::INT4);
+    nullif
+    --------
+    1234
+    (1 row)
+    ```
+
+    ```sql
+    mogdb=# SELECT nullif('1234'::VARCHAR,'2012-12-24'::DATE);
+    ERROR:  invalid input syntax for type timestamp: "1234"
+    ```
+
+  - If implicit conversion is not applied between two data types, an error is returned. Example:
+
+    ```sql
+    mogdb=# SELECT nullif(TRUE::BOOLEAN,'2012-12-24'::DATE);
+    ERROR:  operator does not exist: boolean = timestamp without time zone
+    LINE 1: SELECT nullif(TRUE::BOOLEAN,'2012-12-24'::DATE) FROM sys_dummy;
+    ^
+    HINT:  No operator matches the given name and argument type(s). You might need to add explicit type casts.
+    ```
+
+- nvl( expr1 , expr2 )
+
+  Description:
+
+  - If **expr1** is **NULL**, **expr2** is returned.
+  - If **expr1** is not **NULL**, **expr1** is returned.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT nvl('hello','world');
+    nvl
+  -------
+   hello
+  (1 row)
+  ```
+
+  Note: Parameters **expr1** and **expr2** can be of any data type. If **expr1** and **expr2** are of different data types, NVL checks whether **expr2** can be implicitly converted to **expr1**. If it can, the data type of **expr1** is returned. Otherwise, an error is returned.
+
+- greatest(expr1 [, …])
+
+  Description: Selects the largest value from a list of any number of expressions.
+
+  Return type:
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT greatest(1*2,2-3,4-1);
+   greatest
+  ----------
+          3
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT greatest('HARRY', 'HARRIOT', 'HAROLD');
+   greatest
+  ----------
+   HARRY
+  (1 row)
+  ```
+
+- least(expr1 [, …])
+
+  Description: Selects the smallest value from a list of any number of expressions.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT least(1*2,2-3,4-1);
+   least
+  -------
+      -1
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT least('HARRY','HARRIOT','HAROLD');
+   least
+  --------
+   HAROLD
+  (1 row)
+  ```
+
+- EMPTY_BLOB()
+
+  Description: Initiates a BLOB variable in an **INSERT** or an **UPDATE** statement to a **NULL** value.
+
+  Return type: BLOB
+
+  Example:
+
+  ```sql
+  -- Create a table.
+  mogdb=# CREATE TABLE blob_tb(b blob,id int);
+  -- Insert data.
+  mogdb=# INSERT INTO blob_tb VALUES (empty_blob(),1);
+  --Delete the table.
+  mogdb=# DROP TABLE blob_tb;
+  ```
+
+  Note: The length is 0 obtained using **DBE_LOB.GET_LENGTH**.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/23-system-information-functions.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/23-system-information-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..7eacf34e948ae2fac738c239b001c530818145a5
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/23-system-information-functions.md
@@ -0,0 +1,1759 @@
+---
+title: System Information Functions
+summary: System Information Functions
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# System Information Functions
+
+## Session Information Functions
+
+- current_catalog
+
+  Description: Name of the current database (called "catalog" in the SQL standard)
+
+  Return type: name
+
+  Example:
+
+  ```
+  mogdb=# SELECT current_catalog;
+   current_database
+  ------------------
+   mogdb
+  (1 row)
+  ```
+
+- current_database()
+
+  Description: Name of the current database
+
+  Return type: name
+
+  Example:
+
+  ```
+  mogdb=# SELECT current_database();
+   current_database
+  ------------------
+   mogdb
+  (1 row)
+  ```
+
+- current_query()
+
+  Description: Text of the currently executing query, as submitted by the client (might contain more than one statement)
+
+  Return type: text
+
+  Example:
+
+  ```
+  mogdb=# SELECT current_query();
+        current_query
+  -------------------------
+   SELECT current_query();
+  (1 row)
+  ```
+
+- current_schema[()]
+
+  Description: Name of current schema
+
+  Return type: name
+
+  Example:
+
+  ```
+  mogdb=# SELECT current_schema();
+   current_schema
+  ----------------
+   public
+  (1 row)
+  ```
+
+  Remarks: **current_schema** returns the first valid schema name in the search path. (If the search path is empty or contains no valid schema name, **NULL** is returned.) This is the schema that will be used for any tables or other named objects that are created without specifying a target schema.
+
+- current_schemas(Boolean)
+
+  Description: Names of schemas in search path
+
+  Return type: name[]
+
+  Example:
+
+  ```
+  mogdb=# SELECT current_schemas(true);
+     current_schemas
+  ---------------------
+   {pg_catalog,public}
+  (1 row)
+  ```
+
+  Note:
+
+  **current_schemas(Boolean)** returns an array of the names of all schemas presently in the search path. The Boolean option determines whether implicitly included system schemas such as **pg_catalog** are included in the returned search path.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The search path can be altered at run time by running the following command:
+  >
+  > ```
+  > SET search_path TO schema [, schema, ...]
+  > ```
+
+- current_user
+
+  Description: User name of current execution context
+
+  Return type: name
+
+  Example:
+
+  ```
+  mogdb=# SELECT current_user;
+   current_user
+  --------------
+   omm
+  (1 row)
+  ```
+
+  Note: **current_user** is the user identifier that is applicable for permission checking. Normally it is equal to the session user, but it can be changed with [SET ROLE](129-SET-ROLE). It also changes during the execution of functions with the attribute **SECURITY DEFINER**.
+
+- definer_current_user
+
+  Description: User name of current execution context
+
+  Return type: name
+
+  Example:
+
+  ```
+  mogdb=# SELECT definer_current_user();
+   definer_current_user
+  ----------------------
+   omm
+  (1 row)
+  ```
+
+- pg_current_sessionid()
+
+  Description: Session ID of the current execution context
+
+  Return type: text
+
+  Example:
+
+  ```
+  mogdb=# SELECT pg_current_sessionid();
+      pg_current_sessionid
+  ----------------------------
+   1579228402.140190434944768
+  (1 row)
+  ```
+
+  Note: **pg_current_sessionid()** is used to obtain the session ID in the current execution context. The structure of the value is *Timestamp. Session ID*. When **enable_thread_pool** is set to **off**, the actual session ID is the thread ID.
+
+- pg_current_sessid
+
+  Description: Session ID of the current execution context
+
+  Return type: text
+
+  Example:
+
+  ```
+  mogdb=# select pg_current_sessid();
+  pg_current_sessid
+  -------------------
+  140308875015936
+  (1 row)
+  ```
+
+  Note: In thread pool mode, the session ID of the current session is obtained. In non-thread pool mode, the background thread ID of the current session is obtained.
+
+- pg_current_userid
+
+  Description: Current user ID.
+
+  Return type: text
+
+  ```
+  mogdb=# SELECT pg_current_userid();
+  pg_current_userid
+  -------------------
+  10
+  (1 row)
+  ```
+
+- working_version_num()
+
+  Description: Returns a version number regarding system compatibility.
+
+  Return type: int
+
+  Example:
+
+  ```
+  mogdb=# SELECT working_version_num();
+   working_version_num
+  ---------------------
+                 92231
+  (1 row)
+
+  ```
+
+- tablespace_oid_name()
+
+  Description: Queries the tablespace name based on the tablespace OID.
+
+  Return type: text
+
+  Example:
+
+  ```
+  mogdb=# select tablespace_oid_name(1663);
+   tablespace_oid_name
+  ---------------------
+   pg_default
+  (1 row)
+  ```
+
+- inet_client_addr()
+
+  Description: Remote connection address. **inet_client_addr** returns the IP address of the current client.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** It is available only in remote connection mode.
+
+  Return type: inet
+
+  Example:
+
+  ```
+  mogdb=# SELECT inet_client_addr();
+   inet_client_addr
+  ------------------
+   10.10.0.50
+  (1 row)
+  ```
+
+- inet_client_port()
+
+  Description: Remote connection port. And **inet_client_port** returns the port number of the current client.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** It is available only in remote connection mode.
+
+  Return type: int
+
+  Example:
+
+  ```
+  mogdb=# SELECT inet_client_port();
+   inet_client_port
+  ------------------
+              33143
+  (1 row)
+  ```
+
+- inet_server_addr()
+
+  Description: Local connection address. **inet_server_addr** returns the IP address on which the server accepted the current connection.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** It is available only in remote connection mode.
+
+  Return type: inet
+
+  Example:
+
+  ```
+  mogdb=# SELECT inet_server_addr();
+   inet_server_addr
+  ------------------
+   10.10.0.13
+  (1 row)
+  ```
+
+- inet_server_port()
+
+  Description: Local connection port. **inet_server_port** returns the port number. All these functions return NULL if the current connection is via a Unix-domain socket.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** It is available only in remote connection mode.
+
+  Return type: int
+
+  Example:
+
+  ```
+  mogdb=# SELECT inet_server_port();
+   inet_server_port
+  ------------------
+               8000
+  (1 row)
+  ```
+
+- pg_backend_pid()
+
+  Description: Process ID of the server process attached to the current session
+
+  Return type: int
+
+  Example:
+
+  ```
+  mogdb=# SELECT pg_backend_pid();
+   pg_backend_pid
+  -----------------
+   140229352617744
+  (1 row)
+  ```
+
+- pg_conf_load_time()
+
+  Description: Configures load time. **pg_conf_load_time** returns the timestamp with time zone when the server configuration files were last loaded.
+
+  Return type: timestamp with time zone
+
+  Example:
+
+  ```
+  mogdb=# SELECT pg_conf_load_time();
+        pg_conf_load_time
+  ------------------------------
+   2017-09-01 16:05:23.89868+08
+  (1 row)
+  ```
+
+- pg_my_temp_schema()
+
+  Description: OID of the temporary schema of a session. The value is **0** if the OID does not exist.
+
+  Return type: oid
+
+  Example:
+
+  ```
+  mogdb=# SELECT pg_my_temp_schema();
+   pg_my_temp_schema
+  -------------------
+                   0
+  (1 row)
+  ```
+
+  Note: **pg_my_temp_schema** returns the OID of the current session's temporary schema, or zero if it has none (because it has not created any temporary tables). **pg_is_other_temp_schema** returns true if the given OID is the OID of another session's temporary schema.
+
+- pg_is_other_temp_schema(oid)
+
+  Description: Specifies whether the schema is the temporary schema of another session.
+
+  Return type: Boolean
+
+  Example:
+
+  ```
+  mogdb=# SELECT pg_is_other_temp_schema(25356);
+   pg_is_other_temp_schema
+  -------------------------
+   f
+  (1 row)
+  ```
+
+- pg_listening_channels()
+
+  Description: Channel names that the session is currently listening on
+
+  Return type: SETOF text
+
+  Example:
+
+  ```
+  mogdb=# SELECT pg_listening_channels();
+   pg_listening_channels
+  -----------------------
+  (0 rows)
+  ```
+
+  Note: **pg_listening_channels** returns a set of names of channels that the current session is listening to.
+
+- pg_postmaster_start_time()
+
+  Description: Server start time **pg_postmaster_start_time** returns the **timestamp with time zone** when the server started.
+
+  Return type: timestamp with time zone
+
+  Example:
+
+  ```
+  mogdb=# SELECT pg_postmaster_start_time();
+     pg_postmaster_start_time
+  ------------------------------
+   2017-08-30 16:02:54.99854+08
+  (1 row)
+  ```
+
+- pg_get_ruledef(rule_oid)
+
+  Description: Obtains the **CREATE RULE** command for a rule.
+
+  Return type: text
+
+  Example:
+
+  ```
+  mogdb=# select * from pg_get_ruledef(24828);
+                                  pg_get_ruledef
+  -------------------------------------------------------------------
+   CREATE RULE t1_ins AS ON INSERT TO t1 DO INSTEAD INSERT INTO t2 (id) VALUES (new.id);
+  (1 row)
+  ```
+
+- sessionid2pid()
+
+  Description: Obtains PID information from a session ID (for example, the **sessid** column in **gs_session_stat**).
+
+  Return type: int8
+
+  Example:
+
+  ```
+  mogdb=# select sessionid2pid(sessid::cstring) from gs_session_stat limit 2;
+    sessionid2pid
+  -----------------
+   139973107902208
+   139973107902208
+  (2 rows)
+  ```
+
+- pg_trigger_depth()
+
+  Description: Current nesting level of triggers
+
+  Return type: int
+
+  Example:
+
+  ```
+  mogdb=# SELECT pg_trigger_depth();
+   pg_trigger_depth
+  ------------------
+                  0
+  (1 row)
+  ```
+
+- session_user
+
+  Description: Session user name
+
+  Return type: name
+
+  Example:
+
+  ```
+  mogdb=# SELECT session_user;
+   session_user
+  --------------
+   omm
+  (1 row)
+  ```
+
+  Note: **session_user** is usually the user who initiated the current database connection, but administrators can change this setting with [SET SESSION AUTHORIZATION](130-SET-SESSION-AUTHORIZATION).
+
+- user
+
+  Description: Equivalent to **current_user**.
+
+  Return type: name
+
+  Example:
+
+  ```
+  mogdb=# SELECT user;
+   current_user
+  --------------
+   omm
+  (1 row)
+  ```
+
+- getpgusername()
+
+  Description: Obtains the database username.
+
+  Return type: name
+
+  Example:
+
+  ```
+  mogdb=# select getpgusername();
+   getpgusername
+  ---------------
+   GaussDB_userna
+  (1 row)
+  ```
+
+- getdatabaseencoding()
+
+  Description: Obtains the database encoding mode.
+
+  Return type: name
+
+  Example:
+
+  ```
+  mogdb=# select getdatabaseencoding();
+   getdatabaseencoding
+  ---------------------
+   SQL_ASCII
+  (1 row)
+  ```
+
+- version()
+
+  Description: Version information. **version** returns a string describing a server's version.
+
+  Return type: text
+
+  Example:
+
+  ```
+  mogdb=# select version();
+  version
+  -------------------------------------------------------------------------------------------------------------------------------------------------------------
+  (mogdb 2.1.1 build 24abfc73) compiled at 2021-04-16 19:39:59 commit 0 last mr 305 debug on x86_64-unknown-linux-gnu, compiled by g++ (GCC) 7.3.0, 64-bit
+  (1 row)
+  ```
+
+- opengauss_version()
+
+  Description: MogDB version information
+
+  Return type: text
+
+  Example:
+
+  ```
+  mogdb=# select opengauss_version();
+   opengauss_version
+  -------------------
+   2.1.0
+  (1 row)
+  ```
+
+- gs_deployment()
+
+  Description: Information about the deployment mode of the current system
+
+  Return type: text
+
+  Example:
+
+  ```
+
+  mogdb=# select gs_deployment();
+      gs_deployment
+  -----------------------
+  OpenSourceCentralized
+  (1 row)
+  ```
+
+- get_hostname()
+
+  Description: Returns the host name of the current node.
+
+  Return type: text
+
+  Example:
+
+  ```
+  mogdb=# SELECT get_hostname();
+   get_hostname
+  --------------
+   linux-user
+  (1 row)
+  ```
+
+- get_nodename()
+
+  Description: Returns the name of the current node.
+
+  Return type: text
+
+  Example:
+
+  ```
+  mogdb=# SELECT get_nodename();
+   get_nodename
+  --------------
+   datanode1
+  (1 row)
+  ```
+
+- get_schema_oid(cstring)
+
+  Description: Returns the OID of the queried schema.
+
+  Return type: oid
+
+  Example:
+
+  ```
+  mogdb=# SELECT get_schema_oid('public');
+   get_schema_oid
+  ----------------
+             2200
+  (1 row)
+  ```
+
+## Access privilege inquiry function
+
+The DDL permissions, including ALTER, DROP, COMMENT, INDEX and VACUUM, are inherent permissions implicitly owned by the owner.
+
+- has_any_column_privilege(user, table, privilege)
+
+  Description: Queries whether a specified user has permission for any column of table.
+
+  **Table 1** Parameter type description
+
+  | Parameter | Valid Input Parameter Type |
+  | :-------- | :------------------------- |
+  | user      | name, oid                  |
+  | table     | text, oid                  |
+  | privilege | text                       |
+
+  Return type: Boolean
+
+- has_any_column_privilege(table, privilege)
+
+  Description: Queries whether the current user has permission to access any column of table. For details about the valid parameter types, see Table 1.
+
+  Return type: Boolean
+
+  **has_any_column_privilege** checks whether a user can access any column of a table in a particular way. Its parameter possibilities are analogous to **has_table_privilege**, except that the desired access permission type must be some combination of SELECT, INSERT, UPDATE, COMMENT or REFERENCES.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** Note that having any of these permissions at the table level implicitly grants it for each column of the table, so **has_any_column_privilege** will always return **true** if **has_table_privilege** does for the same parameters. But **has_any_column_privilege** also succeeds if there is a column-level grant of the permission for at least one column.
+
+- has_column_privilege(user, table, column, privilege)
+
+  Description: Specifies whether a specified user has permission for columns.
+
+  **Table 2** Parameter type description
+
+  | Parameter | Valid Input Parameter Type |
+  | :-------- | :------------------------- |
+  | user      | name, oid                  |
+  | table     | text, oid                  |
+  | column    | text, smallint             |
+  | privilege | text                       |
+
+  Return type: Boolean
+
+- has_column_privilege(table, column, privilege)
+
+  Description: Specifies whether the current user has permission to access columns. For details about the valid parameter types, see Table 2.
+
+  Return type: Boolean
+
+  **has_column_privilege** checks whether a user can access a column in a particular way. Its argument possibilities are analogous to **has_table_privilege**, with the addition that the column can be specified either by name or attribute number. The desired access permission type must evaluate to some combination of **SELECT**, **INSERT**, **UPDATE**, **COMMENT** or **REFERENCES**.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** Note that having any of these permissions at the table level implicitly grants it for each column of the table.
+
+- has_cek_privilege(user, cek, privilege)
+
+  Description: Specifies whether a specified user has permission for CEKs. The parameters are described as follows:
+
+  **Table 3** Parameter type description
+
+  | Parameter | Valid Input Parameter Type | Description           | Range                                                        |
+  | :-------- | :------------------------- | :-------------------- | :----------------------------------------------------------- |
+  | user      | name, oid                  | User                  | User name or ID                                              |
+  | cek       | text, oid                  | Column encryption key | Name or ID of a CEK.                                         |
+  | privilege | text                       | Permission            | **USAGE**: allows users to use the specified CEK.**DROP**: allows users to delete the specified CEK. |
+
+  Return type: Boolean
+
+- has_cmk_privilege(user, cmk, privilege)
+
+  Description: Specifies whether a specified user has permission for CMKs. The parameters are described as follows:
+
+  **Table 4** Parameter type description
+
+  | Parameter | Valid Input Parameter Type | Description | Range                                                        |
+  | :-------- | :------------------------- | :---------- | :----------------------------------------------------------- |
+  | user      | name, oid                  | User        | User name or ID                                              |
+  | cmk       | text, oid                  | CMK         | Name or ID of the CMK                                        |
+  | privilege | text                       | Permission  | **USAGE**: allows users to use the specified CMK.**DROP**: allows users to delete the specified CMK. |
+
+  Return type: Boolean
+
+- has_database_privilege(user, database, privilege)
+
+  Description: Specifies whether a specified user has permission for databases. The parameters are described as follows:
+
+  **Table 5** Parameter type description
+
+  | Parameter | Valid Input Parameter Type |
+  | :-------- | :------------------------- |
+  | user      | name, oid                  |
+  | database  | text, oid                  |
+  | privilege | text                       |
+
+  Return type: Boolean
+
+- has_database_privilege(database, privilege)
+
+  Description: Specifies whether the current user has permission to access a database. For details about the valid parameter types, see Table 5.
+
+  Return type: Boolean
+
+  Note: **has_database_privilege** checks whether a user can access a database in a particular way. Its argument possibilities are analogous to **has_table_privilege**. The desired access permission type must be some combination of **CREATE**, **CONNECT**, **TEMPORARY**, **ALTER**, **DROP**, **COMMENT** or **TEMP** (which is equivalent to **TEMPORARY**).
+
+- has_directory_privilege(user, database, privilege)
+
+  Description: Specifies whether a specified user has permission for directories.
+
+  **Table 6** Parameter type description
+
+  | Parameter | Valid Input Parameter Type |
+  | :-------- | :------------------------- |
+  | user      | name, oid                  |
+  | database  | text, oid                  |
+  | privilege | text                       |
+
+  Return type: Boolean
+
+- has_directory_privilege(database, privilege)
+
+  Description: Specifies whether the current user has permission to access a directory. For details about the valid parameter types, see Table 6.
+
+  Return type: Boolean
+
+- has_foreign_data_wrapper_privilege(user, fdw, privilege)
+
+  Description: Specifies whether a specified user has permission for foreign-data wrappers.
+
+  **Table 7** Parameter type description
+
+  | Parameter | Valid Input Parameter Type |
+  | :-------- | :------------------------- |
+  | user      | name, oid                  |
+  | fdw       | text, oid                  |
+  | privilege | text                       |
+
+  Return type: Boolean
+
+- has_foreign_data_wrapper_privilege(fdw, privilege)
+
+  Description: Specifies whether the current user has permission for foreign-data wrappers. For details about the valid parameter types, see Table 7.
+
+  Return type: Boolean
+
+  Note: **has_foreign_data_wrapper_privilege** checks whether a user can access a foreign-data wrapper in a particular way. Its argument possibilities are analogous to **has_table_privilege**. The desired access permission type must evaluate to **USAGE**.
+
+- has_function_privilege(user, function, privilege)
+
+  Description: Specifies whether a specified user has permission for functions.
+
+  **Table 8** Parameter type description
+
+  | Parameter | Valid Input Parameter Type |
+  | :-------- | :------------------------- |
+  | user      | name, oid                  |
+  | function  | text, oid                  |
+  | privilege | text                       |
+
+  Return type: Boolean
+
+- has_function_privilege(function, privilege)
+
+  Description: Specifies whether the current user has permission for functions. For details about the valid parameter types, see Table 8.
+
+  Return type: Boolean
+
+  Note: **has_function_privilege** checks whether a user can access a function in a particular way. Its argument possibilities are analogous to **has_table_privilege**. When a function is specified by a text string rather than by OID, the allowed input is the same as that for the **regprocedure** data type (see [OID Types](14-object-identifier-types)). The access permission type must be **EXECUTE**, **ALTER**, **DROP**, or **COMMENT**.
+
+- has_language_privilege(user, language, privilege)
+
+  Description: Specifies whether a specified user has permission for languages.
+
+  **Table 9** Parameter type description
+
+  | Parameter | Valid Input Parameter Type |
+  | :-------- | :------------------------- |
+  | user      | name, oid                  |
+  | language  | text, oid                  |
+  | privilege | text                       |
+
+  Return type: Boolean
+
+- has_language_privilege(language, privilege)
+
+  Description: Specifies whether the current user has permission for languages. For details about the valid parameter types, see Table 9.
+
+  Return type: Boolean
+
+  Note: **has_language_privilege** checks whether a user can access a procedural language in a particular way. Its argument possibilities are analogous to **has_table_privilege**. The desired access permission type must evaluate to **USAGE**.
+
+- has_nodegroup_privilege(user, nodegroup, privilege)
+
+  Description: Checks whether a user has permission to access a database node.
+
+  Return type: Boolean
+
+  **Table 10** Parameter type description
+
+  | Parameter | Valid Input Parameter Type |
+  | :-------- | :------------------------- |
+  | user      | name, oid                  |
+  | nodegroup | text, oid                  |
+  | privilege | text                       |
+
+- has_nodegroup_privilege(nodegroup, privilege)
+
+  Description: Checks whether a user has permission to access a database node. The parameter is similar to **has_table_privilege**. The access permission type must be **USAGE**, **CREATE**, **COMPUTE**, **ALTER**, or **CROP**.
+
+  Return type: Boolean
+
+- has_schema_privilege(user, schema, privilege)
+
+  Description: Specifies whether a specified user has permission for schemas.
+
+  Return type: Boolean
+
+- has_schema_privilege(schema, privilege)
+
+  Description: Specifies whether the current user has permission for schemas.
+
+  Return type: Boolean
+
+  Note: **has_schema_privilege** checks whether a user can access a schema in a particular way. Its argument possibilities are analogous to **has_table_privilege**. The desired access permission type must be some combination of **CREATE**, **USAGE**, **ALTER**, **DROP** or **COMMENT**.
+
+- has_server_privilege(user, server, privilege)
+
+  Description: Specifies whether a specified user has permission for foreign servers.
+
+  Return type: Boolean
+
+- has_server_privilege(server, privilege)
+
+  Description: Specifies whether the current user has permission for foreign servers.
+
+  Return type: Boolean
+
+  Note: **has_server_privilege** checks whether a user can access a foreign server in a particular way. Its argument possibilities are analogous to **has_table_privilege**. The access permission type must be **USAGE**, **ALTER**, **DROP**, or **COMMENT**.
+
+- has_table_privilege(user, table, privilege)
+
+  Description: Specifies whether a specified user has permission for tables.
+
+  Return type: Boolean
+
+- has_table_privilege(table, privilege)
+
+  Description: Specifies whether the current user has permission for tables.
+
+  Return type: Boolean
+
+  **has_table_privilege** checks whether a user can access a table in a particular way. The user can be specified by name, by OID (**pg_authid.oid**), **public** to indicate the PUBLIC pseudo-role, or if the argument is omitted **current_user** is assumed. The table can be specified by name or by OID. When it is specified by name, the name can be schema-qualified if necessary. The desired access permission type is specified by a text string, which must be one of the values **SELECT**, **INSERT**, **UPDATE**, **DELETE**, **TRUNCATE**, **REFERENCES**, **TRIGGER**, **ALTER**, **DROP**, **COMMENT**, **INDEX** or **VACUUM**. Optionally, **WITH GRANT OPTION** can be added to a permission type to test whether the permission is held with grant option. Also, multiple permission types can be listed separated by commas, in which case the result will be **true** if any of the listed permissions is held.
+
+  Example:
+
+  ```
+  mogdb=# SELECT has_table_privilege('tpcds.web_site', 'select');
+   has_table_privilege
+  ---------------------
+   t
+  (1 row)
+
+  mogdb=# SELECT has_table_privilege('omm', 'tpcds.web_site', 'select,INSERT WITH GRANT OPTION ');
+   has_table_privilege
+  ---------------------
+   t
+  (1 row)
+  ```
+
+- has_tablespace_privilege(user, tablespace, privilege)
+
+  Description: Specifies whether a specified user has permission for tablespaces.
+
+  Return type: Boolean
+
+- has_tablespace_privilege(tablespace, privilege)
+
+  Description: Specifies whether the current user has permission for tablespaces.
+
+  Return type: Boolean
+
+  Note: **has_tablespace_privilege** checks whether a user can access a tablespace in a particular way. Its argument possibilities are analogous to **has_table_privilege**. The access permission type must be **CREATE**, **ALTER**, **DROP**, or **COMMENT**.
+
+- pg_has_role(user, role, privilege)
+
+  Description: Specifies whether a specified user has permission for roles.
+
+  Return type: Boolean
+
+- pg_has_role(role, privilege)
+
+  Description: Specifies whether the current user has permission for roles.
+
+  Return type: Boolean
+
+  Note: **pg_has_role** checks whether a user can access a role in a particular way. Its argument possibilities are analogous to **has_table_privilege**, except that **public** is not allowed as a user name. The desired access permission type must evaluate to some combination of **MEMBER** or **USAGE**. **MEMBER** denotes direct or indirect membership in the role (that is, the right to do **SET ROLE**), while **USAGE** denotes the permissions of the role are available without doing **SET ROLE**.
+
+## Schema Visibility Inquiry Functions
+
+Each function performs the visibility check for one type of database object. For functions and operators, an object in the search path is visible if there is no object of the same name and parameter data type earlier in the path. For operator classes, both name and associated index access method are considered.
+
+All these functions require object OIDs to identify the object to be checked. If you want to test an object by name, it is convenient to use the OID alias types (**regclass**, **regtype**, **regprocedure**, **regoperator**, **regconfig**, or **regdictionary**).
+
+For example, a table is said to be visible if its containing schema is in the search path and no table of the same name appears earlier in the search path. This is equivalent to the statement that the table can be referenced by name without explicit schema qualification. For example, to list the names of all visible tables:
+
+```
+mogdb=# SELECT relname FROM pg_class WHERE pg_table_is_visible(oid);
+```
+
+- pg_collation_is_visible(collation_oid)
+
+  Description: Specifies whether the collation is visible in search path.
+
+  Return type: Boolean
+
+- pg_conversion_is_visible(conversion_oid)
+
+  Description: Specifies whether the conversion is visible in search path.
+
+  Return type: Boolean
+
+- pg_function_is_visible(function_oid)
+
+  Description: Specifies whether the function is visible in search path.
+
+  Return type: Boolean
+
+- pg_opclass_is_visible(opclass_oid)
+
+  Description: Specifies whether the operator class is visible in search path.
+
+  Return type: Boolean
+
+- pg_operator_is_visible(operator_oid)
+
+  Description: Specifies whether the operator is visible in search path.
+
+  Return type: Boolean
+
+- pg_opfamily_is_visible(opclass_oid)
+
+  Description: Specifies whether the operator family is visible in search path.
+
+  Return type: Boolean
+
+- pg_table_is_visible(table_oid)
+
+  Description: Specifies whether the table is visible in search path.
+
+  Return type: Boolean
+
+- pg_ts_config_is_visible(config_oid)
+
+  Description: Specifies whether the text search configuration is visible in search path.
+
+  Return type: Boolean
+
+- pg_ts_dict_is_visible(dict_oid)
+
+  Description: Specifies whether the text search dictionary is visible in search path.
+
+  Return type: Boolean
+
+- pg_ts_parser_is_visible(parser_oid)
+
+  Description: Specifies whether the text search parser is visible in search path.
+
+  Return type: Boolean
+
+- pg_ts_template_is_visible(template_oid)
+
+  Description: Specifies whether the text search template is visible in search path.
+
+  Return type: Boolean
+
+- pg_type_is_visible(type_oid)
+
+  Description: Specifies whether the type (or domain) is visible in search path.
+
+  Return type: Boolean
+
+## System Catalog Information Functions
+
+- format_type(type_oid, typemod)
+
+  Description: Obtains the SQL name of a data type.
+
+  Return type: text
+
+  Note: **format_type** returns the SQL name of a data type that is identified by its type OID and possibly a type modifier. Pass NULL for the type modifier if no specific modifier is known. Certain type modifiers are passed for data types with length limitations. The SQL name returned from **format_type** contains the length of the data type, which can be calculated by taking sizeof(int32) from actual storage length [actual storage len - sizeof(int32)] in the unit of bytes. 32-bit space is required to store the customized length set by users. So the actual storage length contains 4 bytes more than the customized length. In the following example, the SQL name returned from **format_type** is character varying(6), indicating the length of varchar type is 6 bytes. So the actual storage length of varchar type is 10 bytes.
+
+  ```
+  mogdb=# SELECT format_type((SELECT oid FROM pg_type WHERE typname='varchar'), 10);
+       format_type
+  ----------------------
+   character varying(6)
+  (1 row)
+  ```
+
+- getdistributekey(table_name)
+
+  Description: Obtains a distribution column for a hash table. Distribution is not supported in a standalone system and the return value of this function is empty.
+
+- pg_check_authid(role_oid)
+
+  Description: Checks whether a role name with a given OID exists.
+
+  Return type: Boolean
+
+  Example:
+
+  ```
+  mogdb=# select pg_check_authid(1);
+  pg_check_authid
+  -----------------
+  f
+  (1 row)
+  ```
+
+- pg_describe_object(catalog_id, object_id, object_sub_id)
+
+  Description: Obtains the description of a database object.
+
+  Return type: text
+
+  Note: **pg_describe_object** returns a description of a database object specified by catalog OID, object OID and a (possibly zero) sub-object ID. This is useful to determine the identity of an object as stored in the **pg_depend** catalog.
+
+- pg_get_constraintdef(constraint_oid)
+
+  Description: Obtains the definition of a constraint.
+
+  Return type: text
+
+- pg_get_constraintdef(constraint_oid, pretty_bool)
+
+  Description: Obtains the definition of a constraint.
+
+  Return type: text
+
+  Note: **pg_get_constraintdef** and **pg_get_indexdef** respectively reconstruct the creating command for a constraint and an index.
+
+- pg_get_expr(pg_node_tree, relation_oid)
+
+  Description: Decompiles internal form of an expression, assuming that any Vars in it refer to the relationship indicated by the second parameter.
+
+  Return type: text
+
+- pg_get_expr(pg_node_tree, relation_oid, pretty_bool)
+
+  Description: Decompiles internal form of an expression, assuming that any Vars in it refer to the relationship indicated by the second parameter.
+
+  Return type: text
+
+  Note: **pg_get_expr** decompiles the internal form of an individual expression, such as the default value for a column. It can be useful when examining the contents of system catalogs. If the expression might contain Vars, specify the OID of the relationship they refer to as the second parameter; if no Vars are expected, zero is sufficient.
+
+- pg_get_functiondef(func_oid)
+
+  Description: Obtains the definition of a function.
+
+  Return type: text
+
+  Example:
+
+  ```
+  mogdb=# select * from pg_get_functiondef(598);
+   headerlines |                     definition
+  -------------+----------------------------------------------------
+             4 | CREATE OR REPLACE FUNCTION pg_catalog.abbrev(inet)+
+               |  RETURNS text                                     +
+               |  LANGUAGE internal                                +
+               |  IMMUTABLE STRICT NOT FENCED NOT SHIPPABLE        +
+               | AS $function$inet_abbrev$function$                +
+               |
+  (1 row)
+  ```
+
+- pg_get_function_arguments(func_oid)
+
+  Description: Obtains the parameter list of the function's definition (with default values).
+
+  Return type: text
+
+  Note: **pg_get_function_arguments** returns the parameter list of a function, in the form it would need to appear in within **CREATE FUNCTION**.
+
+- pg_get_function_identity_arguments(func_oid)
+
+  Description: Obtains the parameter list to identify a function (without default values).
+
+  Return type: text
+
+  Note: **pg_get_function_identity_arguments** returns the parameter list necessary to identify a function, in the form it would need to appear in within **ALTER FUNCTION**. This form omits default values.
+
+- pg_get_function_result(func_oid)
+
+  Description: Obtains the **RETURNS** clause for a function.
+
+  Return type: text
+
+  Note: **pg_get_function_result** returns the appropriate **RETURNS** clause for the function.
+
+- pg_get_indexdef(index_oid)
+
+  Description: Obtains the **CREATE INDEX** command for an index.
+
+  Return type: text
+
+  Example:
+
+  ```
+  mogdb=# select * from pg_get_indexdef(16416);
+                               pg_get_indexdef
+  -------------------------------------------------------------------------
+   CREATE INDEX test3_b_idx ON test3 USING btree (b) TABLESPACE pg_default
+  (1 row)
+  ```
+
+- pg_get_indexdef(index_oid, dump_schema_only)
+
+  Description: Obtains the **CREATE INDEX** command for indexes in dump scenarios. For an interval partitioned table that contains a local index, if **dump_schema_only** is set to **true**, the returned index creation statement does not contain the local index information of the automatically created partition. If **dump_schema_only** is set to **false**, the returned index creation statement contains the local index information of the automatically created partition. For a non-interval partitioned table or an interval partitioned table that does not contain a local index, the value of **dump_schema_only** does not affect the returned result of the function.
+
+  Return type: text
+
+  Example:
+
+  ```
+  mogdb=# CREATE TABLE sales
+  mogdb-# (prod_id NUMBER(6),
+  mogdb(#  cust_id NUMBER,
+  mogdb(#  time_id DATE,
+  mogdb(#  channel_id CHAR(1),
+  mogdb(#  promo_id NUMBER(6),
+  mogdb(#  quantity_sold NUMBER(3),
+  mogdb(#  amount_sold NUMBER(10,2)
+  mogdb(# )
+  PARTITION BY RANGE( time_id) INTERVAL('1 day')
+  mogdb-# mogdb-# (
+  mogdb(#  partition p1 VALUES LESS THAN ('2019-02-01 00:00:00'),
+  mogdb(#  partition p2 VALUES LESS THAN ('2019-02-02 00:00:00')
+  mogdb(# );
+  CREATE TABLE
+  mogdb=# create index index_sales on sales(prod_id) local (PARTITION idx_p1 ,PARTITION idx_p2);
+  CREATE INDEX
+  mogdb=#-- If the data to be inserted does not match any partition, create a partition and insert the data into the new partition.
+  mogdb=# INSERT INTO sales VALUES(1, 12, '2019-02-05 00:00:00', 'a', 1, 1, 1);
+  INSERT 0 1
+  mogdb=# select oid from pg_class where relname = 'index_sales';
+    oid
+  -------
+   24632
+  (1 row)
+  mogdb=# select * from pg_get_indexdef(24632, true);
+                                                       pg_get_indexdef
+  --------------------------------------------------------------------------------------------------------------------------
+   CREATE INDEX index_sales ON sales USING btree (prod_id) LOCAL(PARTITION idx_p1, PARTITION idx_p2)  TABLESPACE pg_default
+  (1 row)
+  mogdb=# select * from pg_get_indexdef(24632, false);
+                                                                      pg_get_indexdef
+
+  ------------------------------------------------------------------------------------------------------------------------------------
+  --------------------
+   CREATE INDEX index_sales ON sales USING btree (prod_id) LOCAL(PARTITION idx_p1, PARTITION idx_p2, PARTITION sys_p1_prod_id_idx)  TA
+  BLESPACE pg_default
+  (1 row
+  ```
+
+- pg_get_indexdef(index_oid, column_no, pretty_bool)
+
+  Description: Obtains the **CREATE INDEX** command for an index, or definition of just one index column when **column_no** is not zero.
+
+  Example:
+
+  ```
+  mogdb=# select * from pg_get_indexdef(16416, 0, false);
+                               pg_get_indexdef
+  -------------------------------------------------------------------------
+   CREATE INDEX test3_b_idx ON test3 USING btree (b) TABLESPACE pg_default
+  (1 row)
+  mogdb=# select * from pg_get_indexdef(16416, 1, false);
+   pg_get_indexdef
+  -----------------
+   b
+  (1 row)
+  ```
+
+  Return type: text
+
+  Note: **pg_get_functiondef** returns a complete **CREATE OR REPLACE FUNCTION** statement for a function.
+
+- pg_get_keywords()
+
+  Description: Obtains the list of SQL keywords and their categories.
+
+  Return type: SETOF record
+
+  Note: **pg_get_keywords** returns a set of records describing the SQL keywords recognized by the server. The **word** column contains the keyword. The **catcode** column contains a category code: **U** for unreserved, **C** for column name, **T** for type or function name, or **R** for reserved. The **catdesc** column contains a possibly-localized string describing the category.
+
+- pg_get_userbyid(role_oid)
+
+  Description: Obtains the role name with a given OID.
+
+  Return type: name
+
+  Note: **pg_get_userbyid** extracts a role's name given its OID.
+
+- pg_check_authid(role_id)
+
+  Description: Checks whether a user exists based on **role_id**.
+
+  Return type: text
+
+  Example:
+
+  ```
+  mogdb=# select pg_check_authid(20);
+  pg_check_authid
+  -----------------
+  f
+  (1 row)
+  ```
+
+- pg_get_viewdef(view_name)
+
+  Description: Obtains the underlying **SELECT** command for a view.
+
+  Return type: text
+
+- pg_get_viewdef(view_name, pretty_bool)
+
+  Description: Obtains the underlying **SELECT** command for a view, lines with columns are wrapped to 80 columns if **pretty_bool** is set to **true**.
+
+  Return type: text
+
+  Note: **pg_get_viewdef** reconstructs the **SELECT** query that defines a view. Most of these functions come in two variants. When the function has the parameter **pretty_bool** and the value is true, it can optionally "pretty-print" the result. The pretty-printed format is more readable. The other one is default format which is more likely to be interpreted the same way by future versions of PostgreSQL. Avoid using pretty-printed output for dump purposes. Passing **false** for the pretty-print parameter yields the same result as the variant that does not have the parameter at all.
+
+- pg_get_viewdef(view_oid)
+
+  Description: Obtains the underlying **SELECT** command for a view.
+
+  Return type: text
+
+- pg_get_viewdef(view_oid, pretty_bool)
+
+  Description: Obtains the underlying **SELECT** command for a view, lines with columns are wrapped to 80 columns if **pretty_bool** is set to **true**.
+
+  Return type: text
+
+- pg_get_viewdef(view_oid, wrap_column_int)
+
+  Description: Obtains the underlying **SELECT** command for a view, wrapping lines with columns as specified, printing is implied.
+
+  Return type: text
+
+- pg_get_tabledef(table_oid)
+
+  Description: Obtains a table definition based on **table_oid**.
+
+  Example:
+
+  ```
+  mogdb=# select * from pg_get_tabledef(16384);
+                      pg_get_tabledef
+  -------------------------------------------------------
+   SET search_path = public;                            +
+   CREATE  TABLE t1 (                                   +
+           c1 bigint DEFAULT nextval('serial'::regclass)+
+   )                                                    +
+   WITH (orientation=row, compression=no)               +
+   TO GROUP group1;
+  (1 row)
+  ```
+
+  Return type: text
+
+- pg_get_tabledef(table_name)
+
+  Description: Obtains a table definition based on **table_name**.
+
+  Example:
+
+  ```
+  mogdb=# select * from pg_get_tabledef('t1');
+                      pg_get_tabledef
+  -------------------------------------------------------
+   SET search_path = public;                            +
+   CREATE  TABLE t1 (                                   +
+           c1 bigint DEFAULT nextval('serial'::regclass)+
+   )                                                    +
+   WITH (orientation=row, compression=no)               +
+   TO GROUP group1;
+  (1 row)
+  ```
+
+  Return type: text
+
+  Remarks: **pg_get_tabledef** reconstructs the **CREATE** statement of the table definition, including the table definition, index information, and comments. Users need to create the dependent objects of the table, such as groups, schemas, tablespaces, and servers. The table definition does not include the statements for creating these dependent objects.
+
+- pg_options_to_table(reloptions)
+
+  Description: Obtains the set of storage option name/value pairs.
+
+  Return type: SETOF record
+
+  Note: **pg_options_to_table** returns the set of storage option name/value pairs (**option_name**/**option_value**) when passed **pg_class.reloptions** or **pg_attribute.attoptions**.
+
+- pg_tablespace_databases(tablespace_oid)
+
+  Description: Obtains the set of database OIDs that have objects in the specified tablespace.
+
+  Return type: SETOF oid
+
+  Note: **pg_tablespace_databases** allows a tablespace to be examined. It returns the set of OIDs of databases that have objects stored in the tablespace. If this function returns any rows, the tablespace is not empty and cannot be dropped. To display the specific objects populating the tablespace, you will need to connect to the databases identified by **pg_tablespace_databases** and query their **pg_class** catalogs.
+
+- pg_tablespace_location(tablespace_oid)
+
+  Description: Obtains the path in the file system that this tablespace is located in.
+
+  Return type: text
+
+- pg_typeof(any)
+
+  Description: Obtains the data type of any value.
+
+  Return type: regtype
+
+  Note: **pg_typeof** returns the OID of the data type of the value that is passed to it. This can be helpful for troubleshooting or dynamically constructing SQL queries. The function is declared as returning **regtype**, which is an OID alias type (see [OID Types](14-object-identifier-types)). This means that it is the same as an OID for comparison purposes but displays as a type name.
+
+  Example:
+
+  ```
+  mogdb=# SELECT pg_typeof(33);
+   pg_typeof
+  -----------
+   integer
+  (1 row)
+
+  mogdb=# SELECT typlen FROM pg_type WHERE oid = pg_typeof(33);
+   typlen
+  --------
+        4
+  (1 row)
+  ```
+
+- collation for (any)
+
+  Description: Obtains the collation of the parameter.
+
+  Return type: text
+
+  Note: The expression **collation for** returns the collation of the value that is passed to it.
+
+  Example:
+
+  ```
+  mogdb=# SELECT collation for (description) FROM pg_description LIMIT 1;
+   pg_collation_for
+  ------------------
+   "default"
+  (1 row)
+  ```
+
+  The value might be quoted and schema-qualified. If no collation is derived for the argument expression, then a null value is returned. If the parameter is not of a collectable data type, then an error is thrown.
+
+- pg_extension_update_paths(name)
+
+  Description: Returns the version update path of the specified extension.
+
+  Return type: text(source text), text(path text), text(target text)
+
+- pg_get_serial_sequence(tablename, colname)
+
+  Description: Obtains the sequence of the corresponding table name and column name.
+
+  Return type: text
+
+  Example:
+
+  ```
+  mogdb=# select * from pg_get_serial_sequence('t1', 'c1');
+   pg_get_serial_sequence
+  ------------------------
+   public.serial
+  (1 row)
+  ```
+
+- pg_sequence_parameters(sequence_oid)
+
+  Description: Obtains the parameters of a specified sequence, including the start value, minimum value, maximum value, and incremental value.
+
+  Return type: bigint, bigint, bigint, bigint, Boolean
+
+  Example:
+
+  ```
+  mogdb=# select * from pg_sequence_parameters(16420);
+   start_value | minimum_value |    maximum_value    | increment | cycle_option
+  -------------+---------------+---------------------+-----------+--------------
+           101 |             1 | 9223372036854775807 |         1 | f
+  (1 row)
+  ```
+
+## Comment Information Functions
+
+- col_description(table_oid, column_number)
+
+  Description: Obtains the comment for a table column.
+
+  Return type: text
+
+  Note: **col_description** returns the comment for a table column, which is specified by the OID of its table and its column number.
+
+- obj_description(object_oid, catalog_name)
+
+  Description: Obtains the comment for a database object.
+
+  Return type: text
+
+  Note: The two-parameter form of **obj_description** returns the comment for a database object specified by its OID and the name of the containing system catalog. For example, **obj_description(123456,'pg_class')** would retrieve the comment for the table with OID 123456. The one-parameter form of **obj_description** requires only the object OID.
+
+  **obj_description** cannot be used for table columns since columns do not have OIDs of their own.
+
+- obj_description(object_oid)
+
+  Description: Obtains the comment for a database object.
+
+  Return type: text
+
+- shobj_description(object_oid, catalog_name)
+
+  Description: Obtains the comment for a shared database object.
+
+  Return type: text
+
+  Note: **shobj_description** is used just like **obj_description** except the former is used for retrieving comments on shared objects. Some system catalogs are global to all databases in MogDB, and the comments for objects in them are stored globally as well.
+
+## Transaction IDs and Snapshots
+
+Internal transaction IDs (XIDs) are 64 bits. **txid_snapshot**, the data type used by these functions, stores information about transaction ID visibility at a particular moment. Table 11 describes its components.
+
+**Table 11** Snapshot components
+
+| Name     | Description                                                  |
+| :------- | :----------------------------------------------------------- |
+| xmin     | Earliest transaction ID (txid) that is still active. All earlier transactions will either be committed and visible, or rolled back. |
+| xmax     | First as-yet-unassigned txid. All txids greater than or equal to this are not yet started as of the time of the snapshot, so they are invisible. |
+| xip_list | Active txids at the time of the snapshot. The list includes only those active txids between **xmin** and **xmax**; there might be active txids higher than **xmax**. A txid that is **xmin <= txid < xmax** and not in this list was already completed at the time of the snapshot, and is either visible or dead according to its commit status. The list does not include txids of subtransactions. |
+
+**txid_snapshot**'s textual representation is **xmin:xmax:xip_list**.
+
+For example, **10:20:10,14,15** means **xmin=10, xmax=20, xip_list=10, 14, 15**.
+
+The following functions provide server transaction information in an exportable form. The main use of these functions is to determine which transactions were committed between two snapshots.
+
+- txid_current()
+
+  Description: Obtains the current transaction ID.
+
+  Return type: bigint
+
+- gs_txid_oldestxmin()
+
+  Description: Obtains the minimum transaction ID (specified by **oldesxmin**).
+
+  Return type: bigint
+
+- txid_current_snapshot()
+
+  Description: Obtains the current snapshot.
+
+  Return type: txid_snapshot
+
+- txid_snapshot_xip(txid_snapshot)
+
+  Description: Obtains in-progress transaction IDs in a snapshot.
+
+  Return type: SETOF bigint
+
+- txid_snapshot_xmax(txid_snapshot)
+
+  Description: Obtains **xmax** of snapshots.
+
+  Return type: bigint
+
+- txid_snapshot_xmin(txid_snapshot)
+
+  Description: Obtains **xmin** of snapshots.
+
+  Return type: bigint
+
+- txid_visible_in_snapshot(bigint, txid_snapshot)
+
+  Description: Specifies whether the transaction ID is visible in a snapshot (do not use subtransaction IDs).
+
+  Return type: Boolean
+
+- get_local_prepared_xact()
+
+  Description: Obtains the two-phase residual transaction information of the current node, including the transaction ID, GID of the two-phase transaction, prepared time, owner OID, database OID, and node name of the current node.
+
+  Return type: xid, text, timestamptz, oid, oid, text
+
+- get_remote_prepared_xacts()
+
+  Description: Obtains the two-phase residual transaction information of all remote nodes, including the transaction ID, GID of the two-phase transaction, prepared time, owner name, database name, and node name.
+
+  Return type: xid, text, timestamptz, name, name, text
+
+- global_clean_prepared_xacts(text, text)
+
+  Description: Concurrently cleans two-phase residual transactions. Only the **gs_clean** tool can call this function for the cleaning. In other situations, **false** is returned.
+
+  Return type: Boolean
+
+- slice(hstore, text[])
+
+  Description: Extracts the subset of the hstore type.
+
+  Return type: hstore
+
+  Example:
+
+  ```
+  mogdb=# select slice('a=>1,b=>2,c=>3'::hstore, ARRAY['b','c','x']);
+         slice
+  --------------------
+   "b"=>"2", "c"=>"3"
+  (1 row)
+  ```
+
+- slice_array(hstore, text[])
+
+  Description: Extracts the set of hstore values.
+
+  Return type: value array
+
+  Example:
+
+  ```
+  mogdb=# select slice_array('a=>1,b=>2,c=>3'::hstore, ARRAY['b','c','x']);
+   slice_array
+  -------------
+   {2,3,NULL}
+  (1 row)
+  ```
+
+- skeys(hstore)
+
+  Description: Returns a set of all keys of the hstore type.
+
+  Return type: a set of keys
+
+  Example:
+
+  ```
+  mogdb=# select skeys('a=>1,b=>2');
+   skeys
+  -------
+   a
+   b
+  (2 rows)
+  ```
+
+- pg_control_system()
+
+  Description: Returns the status of the system control file.
+
+  Return type: SETOF record
+
+- pg_control_checkpoint()
+
+  Description: Returns the system checkpoint status.
+
+  Return type: SETOF record
+
+- pv_builtin_functions
+
+  Description: Displays information about all built-in system functions.
+
+  Parameter: nan
+
+  Return type: proname name, pronamespace oid, proowner oid, prolang oid, procost real, prorows real, provariadic oid, protransform regproc, proisagg boolean, proiswindow boolean, prosecdef boolean, proleakproof boolean, proisstrict boolean, proretset boolean, provolatile "char", pronargs smallint, pronargdefaults smallint, prorettype oid, proargtypes oidvector, proallargtypes integer[], proargmodes "char"[], proargnames text[], proargdefaults pg_node_tree, prosrc text, probin text, proconfig text[], proacl aclitem[], prodefaultargpos int2vector, fencedmode boolean, proshippable boolean, propackage boolean, oid oid
+
+- pv_thread_memory_detail
+
+  Description: Returns the memory information of each thread.
+
+  Parameter: nan
+
+  Return type: threadid text, tid bigint, thrdtype text, contextname text, level smallint, parent text, totalsize bigint, freesize bigint, usedsize bigint
+
+- pg_relation_compression_ratio
+
+  Description: Queries the compression rate of a table. By default, **1.0** is returned.
+
+  Parameter: text
+
+  Return type: real
+
+- pg_relation_with_compression
+
+  Description: Specifies whether a table is compressed.
+
+  Parameter: text
+
+  Return type: Boolean
+
+- pg_stat_file_recursive
+
+  Description: Lists all files in a path.
+
+  Parameter: location text
+
+- pg_shared_memory_detail
+
+  Description: Returns usage information about all generated shared memory contexts. For details about each column, see GS_SHARED_MEMORY_DETAIL.
+
+  Parameter: nan
+
+  Return type: contextname text, level smallint, parent text, totalsize bigint, freesize bigint, usedsize bigint
+
+- get_gtm_lite_status
+
+  Description: Returns the backup XID and CSN on the GTM for fault locating. This system function is not supported in GTM-FREE mode.
+
+- gs_stat_get_wlm_plan_operator_info
+
+  Description: Obtains operator plan information from the internal hash table.
+
+  Parameter: oid
+
+  Return type: datname text, queryid int8, plan_node_id int4, startup_time int8, total_time int8, actual_rows int8, max_peak_memory int4, query_dop int4, parent_node_id int4, left_child_id int4, right_child_id int4, operation text, orientation text, strategy text, options text, condition text, projection text
+
+- pg_stat_get_partition_tuples_hot_updated
+
+  Description: Returns statistics on the number of hot-updated tuples in a partition with a specified partition ID.
+
+  Parameter: oid
+
+  Return type: bigint
+
+- gs_session_memory_detail_tp
+
+  Description: Returns the memory usage of the session. For details, see **gs_session_memory_detail**.
+
+  Parameter: nan
+
+  Return type: sessid text, sesstype text, contextname text, level smallint, parent text, totalsize bigint, freesize bigint, usedsize bigint
+
+- gs_thread_memory_detail
+
+  Description: Returns the memory information of each thread.
+
+  Parameter: nan
+
+  Return type: threadid text, tid bigint, thrdtype text, contextname text, level smallint, parent text, totalsize bigint, freesize bigint, usedsize bigint
+
+- pg_stat_get_wlm_realtime_operator_info
+
+  Description: Obtains the operator information of the real-time execution plan from the internal hash table.
+
+  Parameter: nan
+
+  Return type: queryid bigint, pid bigint, plan_node_id integer, plan_node_name text, start_time timestamp with time zone, duration bigint, status text, query_dop integer, estimated_rows bigint, tuple_processed bigint, min_peak_memory integer, max_peak_memory integer, average_peak_memory integer, memory_skew_percent integer, min_spill_size integer, max_spill_size integer, average_spill_size integer, spill_skew_percent integer, min_cpu_time bigint, max_cpu_time bigint, total_cpu_time bigint, cpu_skew_percent integer, warning text
+
+- pg_stat_get_wlm_realtime_ec_operator_info
+
+  Description: Obtains the operator information of the EC execution plan from the internal hash table.
+
+  Parameter: nan
+
+  Return type: queryid bigint, plan_node_id integer, plan_node_name text, start_time timestamp with time zone, ec_operator integer, ec_status text, ec_execute_datanode text, ec_dsn text, ec_username text, ec_query text, ec_libodbc_type text, ec_fetch_count bigint
+
+- pg_stat_get_wlm_operator_info
+
+  Description: Obtains the operator information of the execution plan from the internal hash table.
+
+  Parameter: nan
+
+  Return type: queryid bigint, pid bigint, plan_node_id integer, plan_node_name text, start_time timestamp with time zone, duration bigint, query_dop integer, estimated_rows bigint, tuple_processed bigint, min_peak_memory integer, max_peak_memory integer, average_peak_memory integer, memory_skew_percent integer, min_spill_size integer, max_spill_size integer, average_spill_size integer, spill_skew_percent integer, min_cpu_time bigint, max_cpu_time bigint, total_cpu_time bigint, cpu_skew_percent integer, warning text
+
+- pg_stat_get_wlm_node_resource_info
+
+  Description: Obtains the resource information of the current node.
+
+  Parameter: nan
+
+  Return type: min_mem_util integer, max_mem_util integer, min_cpu_util integer, max_cpu_util integer, min_io_util integer, max_io_util integer, used_mem_rate integer
+
+- pg_stat_get_session_wlmstat
+
+  Description: Returns the load information of the current session.
+
+  Parameter: pid integer
+
+  Return type: datid oid, threadid bigint, sessionid bigint, threadpid integer, usesysid oid, appname text, query text, priority bigint, block_time bigint, elapsed_time bigint, total_cpu_time bigint, skew_percent integer, statement_mem integer, active_points integer, dop_value integer, current_cgroup text, current_status text, enqueue_state text, attribute text, is_plana boolean, node_group text, srespool name
+
+- pg_stat_get_wlm_ec_operator_info
+
+  Description: Obtains the operator information of the EC execution plan from the internal hash table.
+
+  Parameter: nan
+
+  Return type: queryid bigint, plan_node_id integer, plan_node_name text, start_time timestamp with time zone, duration bigint, tuple_processed bigint, min_peak_memory integer, max_peak_memory integer, average_peak_memory integer, ec_operator integer, ec_status text, ec_execute_datanode text, ec_dsn text, ec_username text, ec_query text, ec_libodbc_type text, ec_fetch_count bigint
+
+- pg_stat_get_wlm_instance_info
+
+  Description: Returns the load information of the current instance.
+
+  Parameter: nan
+
+  Return type: instancename text, timestamp, timestamp with time zone, used_cpu integer, free_memory integer, used_memory integer, io_await double precision, io_util double precision, disk_read double precision, disk_write double precision, process_read bigint, process_write bigint, logical_read bigint, logical_write bigint, read_counts bigint, write_counts bigint
+
+- pg_stat_get_wlm_instance_info_with_cleanup
+
+  Description: Returns the load information of the current instance and saves the information to the system catalog.
+
+  Parameter: nan
+
+  Return type: instancename text, timestamp, timestamp with time zone, used_cpu integer, free_memory integer, used_memory integer, io_await double precision, io_util double precision, disk_read double precision, disk_write double precision, process_read bigint, process_write bigint, logical_read bigint, logical_write bigint, read_counts bigint, write_counts bigint
+
+- pg_stat_get_wlm_realtime_session_info
+
+  Description: Returns the load information of the real-time session.
+
+  Parameter: nan
+
+  Return type: nodename text, threadid bigint, block_time bigint, duration bigint, estimate_total_time bigint, estimate_left_time bigint, schemaname text, query_band text, spill_info text, control_group text, estimate_memory integer, min_peak_memory integer, max_peak_memory integer, average_peak_memory integer, memory_skew_percent integer, min_spill_size integer, max_spill_size integer, average_spill_size integer, spill_skew_percent integer, min_dn_time bigint, max_dn_time bigint, average_dn_time bigint, dntime_skew_percent integer, min_cpu_time bigint, max_cpu_time bigint, total_cpu_time bigint, cpu_skew_percent integer, min_peak_iops integer, max_peak_iops integer, average_peak_iops integer, iops_skew_percent integer, warning text, query text, query_plan text, cpu_top1_node_name text, cpu_top2_node_name text, cpu_top3_node_name text, cpu_top4_node_name text, cpu_top5_node_name text, mem_top1_node_name text, mem_top2_node_name text, mem_top3_node_name text, mem_top4_node_name text, mem_top5_node_name text, cpu_top1_value bigint, cpu_top2_value bigint, cpu_top3_value bigint, cpu_top4_value bigint, cpu_top5_value bigint, mem_top1_value bigint, mem_top2_value bigint, mem_top3_value bigint, mem_top4_value bigint, mem_top5_value bigint, top_mem_dn text, top_cpu_dn text
+
+- pg_stat_get_wlm_session_iostat_info
+
+  Description: Returns the session load I/O information.
+
+  Parameter: nan
+
+  Return type: threadid bigint, maxcurr_iops integer, mincurr_iops integer, maxpeak_iops integer, minpeak_iops integer, iops_limits integer, io_priority integer, curr_io_limits integer
+
+- pg_stat_get_wlm_statistics
+
+  Description: Returns session load statistics.
+
+  Parameter: nan
+
+  Return type: statement text, block_time bigint, elapsed_time bigint, total_cpu_time bigint, qualification_time bigint, skew_percent integer, control_group text, status text, action text
+
+## Other Function
+
+- sys_guid function <a id = 'sys_guid'> </a>
+
+  Description: sys_guid generates and returns a globally unique identifier consisting of 16 bytes. The generated identifier is composed of host time, thread identifier, and random value.
+
+  Example:
+
+  ```sql
+  mogdb=# select sys_guid();
+            sys_guid
+  ----------------------------------
+  0005D3DE87AB3147177B0300B2E3FED6
+  (1 row)
+  ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/1-configuration-settings-functions.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/1-configuration-settings-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..4b4cf49fa37fe57aee7d0ae2be3c33405d4a20ff
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/1-configuration-settings-functions.md
@@ -0,0 +1,66 @@
+---
+title: Configuration Settings Functions
+summary: Configuration Settings Functions
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Configuration Settings Functions
+
+Configuration setting functions are used for querying and modifying configuration parameters during running.
+
+- current_setting(setting_name)
+
+  Description: Specifies the current setting.
+
+  Return type: text
+
+  Note:**current_setting** obtains the current setting of **setting_name** by query. It is equivalent to the **SHOW** statement.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT current_setting('datestyle');
+
+   current_setting
+  -----------------
+   ISO, MDY
+  (1 row)
+  ```
+
+- set_working_grand_version_num_manually(tmp_version)
+
+    Description: Upgrades new features of the database by switching the authorization version.
+
+    Return type: void
+
+- shell_in(type)
+
+    Description: Inputs a route for the shell type that has not yet been filled.
+
+    Return type: void
+
+- shell_out(type)
+
+    Description: Outputs a route for the shell type that has not yet been filled.
+
+    Return type: void
+
+- set_config(setting_name, new_value, is_local)
+
+  Description: Sets the parameter and returns a new value.
+
+  Return type: text
+
+  Note: **set_config**  sets  **setting_name**  to  **new_value**. If  **is_local**  is set to  **true**,  **new_value**  applies only to the current transaction. If you want  **new_value**  to apply for the current session, set the value to  **false**  instead. The function corresponds to the  **SET**  statement.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT set_config('log_statement_stats', 'off', false);
+
+   set_config
+  ------------
+   off
+  (1 row)
+  ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/10-undo-system-functions.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/10-undo-system-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..61e14c39c35537cbe93fc64396268449a6bbad6f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/10-undo-system-functions.md
@@ -0,0 +1,62 @@
+---
+title: Undo System Functions
+summary: Undo System Functions
+author: Guo Huan
+date: 2021-10-28
+---
+
+# Undo System Functions
+
+- gs_undo_meta(type, zid, location)
+
+  Description: Specifies metadata of each module in the undo system.
+
+  Parameter description:
+
+  - **type** (metadata type)
+
+    The value **0** indicates the metadata corresponding to **Undo Zone(Record)**.
+
+    The value **1** indicates the metadata corresponding to **Undo Zone(Transaction Slot)**.
+
+    The value **2** indicates the metadata corresponding to **Undo Space(Record)**.
+
+    The value **3** indicates the metadata corresponding to **Undo Space(Transaction Slot)**.
+
+  - **zid** (undo zone ID)
+
+    The value **-1** indicates the metadata of all undo zones.
+
+    The value range 0-1024 x 1024 indicates the metadata of the corresponding zone ID.
+
+  - **location** (read location)
+
+    The value **0** indicates that data is read from the current memory.
+
+    The value **1** indicates that data is read from a physical file.
+
+  Return type: record
+
+- gs_undo_translot(type, zid)
+
+  Description: Specifies transaction slot information of the undo system.
+
+  Parameter description:
+
+  - **type** (metadata type)
+
+    The value **0** indicates the metadata corresponding to **Undo Zone(Record)**.
+
+    The value **1** indicates the metadata corresponding to **Undo Zone(Transaction Slot)**.
+
+    The value **2** indicates the metadata corresponding to **Undo Space(Record)**.
+
+    The value **3** indicates the metadata corresponding to **Undo Space(Transaction Slot)**.
+
+  - **zid** (undo zone ID)
+
+    The value **-1** indicates the metadata of all undo zones.
+
+    The value range 0-1024 x 1024 indicates the metadata of the corresponding zone ID.
+
+  Return type: record
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/2-universal-file-access-functions.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/2-universal-file-access-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..6a80d4db1416a86c7a45684aa272dfc688f16171
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/2-universal-file-access-functions.md
@@ -0,0 +1,148 @@
+---
+title: Universal File Access Functions
+summary: Universal File Access Functions
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Universal File Access Functions
+
+Universal file access functions provide local access interfaces for files on a database server. Only files in the MogDB directory and the **log_directory** directory can be accessed. Use a relative path for files in the MogDB directory, and a path matching the **log_directory** configuration setting for log files. Only database initialization users can use these functions.
+
+- pg_ls_dir(dirname text)
+
+  Description: Lists files in a directory.
+
+  Return type: setof text
+
+  Note:**pg_ls_dir** returns all the names in the specified directory, except the special entries "." and "..".
+
+  For example:
+
+  ```sql
+  mogdb=# SELECT pg_ls_dir('./');
+        pg_ls_dir
+  ----------------------
+   .postgresql.conf.swp
+   postgresql.conf
+   pg_tblspc
+   PG_VERSION
+   pg_ident.conf
+   core
+   server.crt
+   pg_serial
+   pg_twophase
+   postgresql.conf.lock
+   pg_stat_tmp
+   pg_notify
+   pg_subtrans
+   pg_ctl.lock
+   pg_xlog
+   pg_clog
+   base
+   pg_snapshots
+   postmaster.opts
+   postmaster.pid
+   server.key.rand
+   server.key.cipher
+   pg_multixact
+   pg_errorinfo
+   server.key
+   pg_hba.conf
+   pg_replslot
+   .pg_hba.conf.swp
+   cacert.pem
+   pg_hba.conf.lock
+   global
+   mogdb.state
+  (32 rows)
+  ```
+
+- pg_read_file(filename text, offset bigint, length bigint)
+
+  Description: Returns the content of a text file.
+
+  Return type: text
+
+  Note:**pg_read_file** returns part of a text file. It can return a maximum of *length* bytes from *offset*. The actual size of fetched data is less than *length* if the end of the file is reached first. If **offset** is negative, it is the length rolled back from the file end. If **offset** and **length** are omitted, the entire file is returned.
+
+  For example:
+
+  ```sql
+  mogdb=# SELECT pg_read_file('postmaster.pid',0,100);
+               pg_read_file
+  ---------------------------------------
+   53078                                +
+   /srv/BigData/hadoop/data1/dbnode+
+   1500022474                           +
+   8000                                +
+   /var/run/FusionInsight               +
+   localhost                            +
+    2
+  (1 row)
+  ```
+
+- pg_read_binary_file(filename text [, offset bigint, length bigint,missing_ok boolean])
+
+  Description: Returns the content of a binary file.
+
+  Return type: bytea
+
+  Note:**pg_read_binary_file** is similar to **pg_read_file**, except that the result is a **bytea** value; accordingly, no encoding checks are performed. In combination with the **convert_from** function, this function can be used to read a file in a specified encoding:
+
+  ```sql
+  mogdb=# SELECT convert_from(pg_read_binary_file('filename'), 'UTF8');
+  ```
+
+- pg_stat_file(filename text)
+
+  Description: Returns status information about a file.
+
+  Return type: record
+
+  Note:**pg_stat_file** returns a record containing the file size, last access timestamp, last modification timestamp, last file status change timestamp, and a Boolean value indicating if it is a directory. Typical use cases are as follows:
+
+  ```sql
+  mogdb=# SELECT * FROM pg_stat_file('filename');
+  ```
+
+  ```sql
+  mogdb=# SELECT (pg_stat_file('filename')).modification;
+  ```
+
+  For example:
+
+  ```sql
+  mogdb=# SELECT convert_from(pg_read_binary_file('postmaster.pid'), 'UTF8');
+               convert_from
+  --------------------------------------
+   4881                                +
+   /srv/BigData/mogdb/data1/dbnode+
+   1496308688                          +
+   25108                               +
+   /opt/user/Bigdata/mogdb/mogdb_tmp +
+   *                                   +
+    25108001  43352069                 +
+
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT * FROM pg_stat_file('postmaster.pid');
+
+   size |         access         |      modification      |         change
+  | creation | isdir
+  ------+------------------------+------------------------+------------------------
+  +----------+-------
+    117 | 2017-06-05 11:06:34+08 | 2017-06-01 17:18:08+08 | 2017-06-01 17:18:08+08
+  |          | f
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT (pg_stat_file('postmaster.pid')).modification;
+        modification
+  ------------------------
+   2017-06-01 17:18:08+08
+  (1 row)
+  ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/3-server-signal-functions.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/3-server-signal-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..1f83af51aa1eac97a5259d557f9f46cd83008eb2
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/3-server-signal-functions.md
@@ -0,0 +1,66 @@
+---
+title: Server Signal Functions
+summary: Server Signal Functions
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Server Signal Functions
+
+Server signaling functions send control signals to other server processes. Only system administrators can use these functions.
+
+- pg_cancel_backend(pid int)
+
+  Description: Cancels the current query of a backend.
+
+  Return type: Boolean
+
+  Note:**pg_cancel_backend** sends a query cancellation (SIGINT) signal to the backend process identified by **pid**. The PID of an active backend process can be found in the **pid** column of the **pg_stat_activity** view, or can be found by listing the database process using **ps** on the server. A user with the  **SYSADMIN**  permission, the owner of the database connected to the backend process, the owner of the backend process, or a user who inherits the  **gs_role_signal_backend**  permission of the built-in role has the permission to use this function.
+
+- pg_reload_conf()
+
+  Description: Causes all server processes to reload their configuration files (restricted to the system administrator).
+
+  Return type: Boolean
+
+  Note:**pg_reload_conf** sends a SIGHUP signal to the server (restricted to the system administrator). As a result, all server processes reload their configuration files.
+
+- pg_rotate_logfile()
+
+  Description: Rotates the log files of the server.
+
+  Return type: Boolean
+
+  Note:**pg_rotate_logfile** sends a signal to the log file manager, instructing the manager to immediately switch to a new output file. This function works only when **redirect_stderr** is used for log output. Otherwise, no log file manager subprocess exists.
+
+- pg_terminate_backend(pid int)
+
+  Description: Terminates a backend thread.
+
+  Return type: Boolean
+
+  Note: Each of these functions returns **true** if they are successful and **false** otherwise. A user with the  **SYSADMIN**  permission, the owner of the database connected to the backend process, the owner of the backend process, or a user who inherits the  **gs_role_signal_backend**  permission of the built-in role has the permission to use this function.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT pid from pg_stat_activity;
+         pid
+  -----------------
+   140657876268816
+  (1 rows)
+
+  mogdb=# SELECT pg_terminate_backend(140657876268816);
+   pg_terminate_backend
+  ----------------------
+   t
+  (1 row)
+  ```
+
+- pg_terminate_session(pid int64, sessionid int64)
+
+    Description: Terminates a backend session.
+
+    Return type: Boolean
+
+    Note: Each of these functions returns  **true**  if they are successful and  **false**  otherwise. A user with the  **SYSADMIN**  permission, the owner of the database connected to the session, the owner of the session, or a user who inherits the  **gs_role_signal_backend**  permission of the built-in role has the permission to use this function.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/4-backup-and-restoration-control-functions.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/4-backup-and-restoration-control-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..2b1c5834954338b9190864e6b6c2e52dad1ab76d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/4-backup-and-restoration-control-functions.md
@@ -0,0 +1,256 @@
+---
+title: Backup and Restoration Control Functions
+summary: Backup and Restoration Control Functions
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Backup and Restoration Control Functions
+
+## Backup Control Functions
+
+Backup control functions help with online backup.
+
+- pg_create_restore_point(name text)
+
+  Description: Creates a named point for performing the restoration operation (restricted to the system administrator).
+
+  Return type: text
+
+  Note: **pg_create_restore_point** creates a named transaction log record that can be used as a restoration target, and returns the corresponding transaction log location. The given name can then be used with **recovery_target_name** to specify the point up to which restoration will proceed. Avoid creating multiple restoration points with the same name, since restoration will stop at the first one whose name matches the restoration target.
+
+- pg_current_xlog_location()
+
+  Description: Obtains the write position of the current transaction log.
+
+  Return type: text
+
+  Note: **pg_current_xlog_location** displays the write position of the current transaction log in the same format as those of the previous functions. Read-only operations do not require permissions of the system administrator.
+
+- pg_current_xlog_insert_location()
+
+  Description: Obtains the insert position of the current transaction log.
+
+  Return type: text
+
+  Note: **pg_current_xlog_insert_location** displays the insert position of the current transaction log. The insertion point is the logical end of the transaction log at any instant, while the write location is the end of what has been written out from the server's internal buffers. The write position is the end that can be detected externally from the server. This operation can be performed to archive only some of completed transaction log files. The insert position is mainly used for commissioning the server. Read-only operations do not require permissions of the system administrator.
+
+- gs_current_xlog_insert_end_location()
+
+  Description: Obtains the insert position of the current transaction log.
+
+  Return type: text
+
+  Note: **gs_current_xlog_insert_end_location** displays the insert position of the current transaction log.
+
+- pg_start_backup(label text [, fast boolean ])
+
+  Description: Starts executing online backup (restricted to the system administrator or replication roles).
+
+  Return type: text
+
+  Note: **pg_start_backup** receives a user-defined backup label (usually the name of the position where the backup dump file is stored). This function writes a backup label file to the data directory of openGauss and then returns the start position of backed up transaction logs in text mode.
+
+  ```sql
+  mogdb=# SELECT pg_start_backup('label_goes_here');
+   pg_start_backup
+  -----------------
+   0/3000020
+  (1 row)
+  ```
+
+- pg_stop_backup()
+
+  Description: Completes online backup (restricted to the system administrator or replication roles).
+
+  Return type: text
+
+  Note: **pg_stop_backup** deletes the label file created by **pg_start_backup** and creates a backup history file in the transaction log archive area. The history file includes the label given to **pg_start_backup**, the start and end transaction log locations for the backup, and the start and end time of the backup. The return value is the backup's ending transaction log location. After the end position is calculated, the insert position of the current transaction log automatically goes ahead to the next transaction log file. In this way, the ended transaction log file can be immediately archived so that backup is complete.
+
+- pg_switch_xlog()
+
+  Description: Switches to a new transaction log file (restricted to the system administrator).
+
+  Return type: text
+
+  Note: **pg_switch_xlog** moves to the next transaction log file so that the current log file can be archived (if continuous archive is used). The return value is the ending transaction log location + 1 within the just-completed transaction log file. If there has been no transaction log activity since the last transaction log switchover, **pg_switch_xlog** will do nothing but return the start location of the transaction log file currently in use.
+
+- pg_xlogfile_name(location text)
+
+  Description: Converts the position string in a transaction log to a file name.
+
+  Return type: text
+
+  Note: **pg_xlogfile_name** extracts only the transaction log file name. If the given transaction log position is the transaction log file border, a transaction log file name will be returned for both the two functions. This is usually the desired behavior for managing transaction log archiving, since the preceding file is the last one that currently needs to be archived.
+
+- pg_xlogfile_name_offset(location text)
+
+  Description: Converts the position string in a transaction log to a file name and returns the byte offset in the file.
+
+  Return type: text and integer
+
+  Note: **pg_xlogfile_name_offset** can extract transaction log file names and byte offsets from the returned results of the preceding functions. Example:
+
+  ```sql
+  mogdb=# SELECT * FROM pg_xlogfile_name_offset(pg_stop_backup());
+  NOTICE:  pg_stop_backup cleanup done, waiting for required WAL segments to be archived
+  NOTICE:  pg_stop_backup complete, all required WAL segments have been archived
+          file_name         | file_offset
+  --------------------------+-------------
+  000000010000000000000003  |         272
+  (1 row)
+  ```
+
+- pg_xlog_location_diff(location text, location text)
+
+  Description: Calculates the difference in bytes between two transaction log locations.
+
+  Return type: numeric
+
+- pg_cbm_tracked_location()
+
+  Description: Queries the LSN location parsed by CBM.
+
+  Return type: text
+
+- pg_cbm_get_merged_file(startLSNArg text, endLSNArg text)
+
+  Description: Combines CBM files within the specified LSN range into one and returns the name of the combined file.
+
+  Return type: text
+
+  Note: Only the system administrator or O&M administrator can obtain the CBM combination file.
+
+- pg_cbm_get_changed_block(startLSNArg text, endLSNArg text)
+
+  Description: Combines CBM files within the specified LSN range into a table and return records of this table.
+
+  Return type: record
+
+  Note: The table columns include the start LSN, end LSN, tablespace OID, database OID, table relfilenode, table fork number, whether the table is deleted, whether the table is created, whether the table is truncated, number of pages in the truncated table, number of modified pages, and list of modified page numbers.
+
+- pg_cbm_recycle_file(targetLSNArg text)
+
+  Description: Deletes the CBM files that are no longer used and returns the first LSN after the deletion.
+
+  Return type: text
+
+- pg_cbm_force_track(targetLSNArg text,timeOut int)
+
+  Description: Forcibly executes the CBM trace to the specified Xlog position and returns the Xlog position of the actual trace end point.
+
+  Return type: text
+
+- pg_enable_delay_ddl_recycle()
+
+  Description: Enables DDL delay and returns the Xlog position of the enabling point. You need to enable **operate_mode** as the administrator or O&M administrator.
+
+  Return type: text
+
+- pg_disable_delay_ddl_recycle(barrierLSNArg text, isForce bool)
+
+  Description: Disables DDL delay and returns the Xlog range where DDL delay takes effect. You need to enable **operate_mode** as the administrator or O&M administrator.
+
+  Return type: record
+
+- pg_enable_delay_xlog_recycle()
+
+  Description: Enables Xlog recycle delay. This function is used in primary database node restoration.
+
+  Return type: void
+
+- pg_disable_delay_xlog_recycle()
+
+  Description: Disables Xlog recycle delay. This function is used in primary database node restoration.
+
+  Return type: void
+
+- pg_cbm_rotate_file(rotate_lsn text)
+
+  Description: Forcibly switches the file after the CBM parses **rotate_lsn**. This function is called during the build process.
+
+  Return type: void
+
+- gs_roach_stop_backup(backupid text)
+
+  Description: Stops a backup started by the internal backup tool GaussRoach. It is similar to the **pg_stop_backup system** function but is more lightweight.
+
+  Return type: text. The content is the insertion position of the current log.
+
+  Note: Currently, openGauss does not support this function.
+
+- gs_roach_enable_delay_ddl_recycle(backupid name)
+
+  Description: Enables DDL delay and returns the log location of the enabling point. It is similar to the **pg_enable_delay_ddl_recycle** system function but is more lightweight. In addition, different **backupid** values can be used to concurrently open DDL statements with delay.
+
+  Return type: text. The content is the log location of the start point.
+
+  Note: Currently, openGauss does not support this function.
+
+- gs_roach_disable_delay_ddl_recycle(backupid text)
+
+  Description: Disables DDL delay, returns the range of logs on which DDL delay takes effect, and deletes the physical files of column-store tables that are deleted by users within this range. It is similar to the **pg_enable_delay_ddl_recycle** system function but is more lightweight. In addition, the DDL delay function can be disabled concurrently by specifying different backupid values.
+
+  Return type: record. The content is the range of logs for which DDL is delayed to take effect.
+
+  Note: Currently, openGauss does not support this function.
+
+- gs_roach_switch_xlog(request_ckpt bool)
+
+  Description: Switches the currently used log segment file and triggers a full checkpoint if **request_ckpt** is set to **true**.
+
+  Return type: text. The content is the location of the segment log.
+
+  Note: Currently, openGauss does not support this function.
+
+## Restoration Control Functions
+
+Restoration control functions provide information about the status of standby nodes. These functions may be executed both during restoration and in normal running.
+
+- pg_is_in_recovery()
+
+  Description: Returns **true** if restoration is still in progress.
+
+  Return type: bool
+
+- pg_last_xlog_receive_location()
+
+  Description: Gets the last transaction log location received and synchronized to disk by streaming replication. While streaming replication is in progress, this will increase monotonically. If restoration has completed, this value will remain static at the value of the last WAL record received and synchronized to disk during restoration. If streaming replication is disabled or if it has not yet started, the function returns **NULL**.
+
+  Return type: text
+
+- pg_last_xlog_replay_location()
+
+  Description: Gets last transaction log location replayed during restoration. If restoration is still in progress, this will increase monotonically. If restoration has completed, then this value will remain static at the value of the last WAL record received during that restoration. When the server has been started normally without restoration, the function returns **NULL**.
+
+  Return type: text
+
+- pg_last_xact_replay_timestamp()
+
+  Description: Gets the timestamp of last transaction replayed during restoration. This is the time to commit a transaction or abort a WAL record on the primary node. If no transactions have been replayed during restoration, this function will return **NULL**. If restoration is still in progress, this will increase monotonically. If restoration has completed, then this value will remain static at the value of the last WAL record received during that restoration. If the server normally starts without manual intervention, this function will return **NULL**.
+
+  Return type: timestamp with time zone
+
+Restoration control functions control restoration processes. These functions may be executed only during restoration.
+
+- pg_is_xlog_replay_paused()
+
+  Description: Returns **true** if restoration is paused.
+
+  Return type: bool
+
+- pg_xlog_replay_pause()
+
+  Description: Pauses restoration immediately.
+
+  Return type: void
+
+- pg_xlog_replay_resume()
+
+  Description: Restarts restoration if it was paused.
+
+  Return type: void
+
+While restoration is paused, no further database changes are applied. In hot standby mode, all new queries will see the same consistent snapshot of the database, and no further query conflicts will be generated until restoration is resumed.
+
+If streaming replication is disabled, the paused state may continue indefinitely without problem. While streaming replication is in progress, WAL records will continue to be received, which will eventually fill available disk space. This progress depends on the duration of the pause, the rate of WAL generation, and available disk space.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/5-snapshot-synchronization-functions.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/5-snapshot-synchronization-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..73116a4b0ef83b620da6abc610c9e6136308e42a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/5-snapshot-synchronization-functions.md
@@ -0,0 +1,24 @@
+---
+title: Snapshot Synchronization Functions
+summary: Snapshot Synchronization Functions
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Snapshot Synchronization Functions
+
+Snapshot synchronization functions save the current snapshot and return its identifier.
+
+- pg_export_snapshot()
+
+Description: Saves the current snapshot and returns its identifier.
+
+Return type: text
+
+Note:**pg_export_snapshot** saves the current snapshot and returns a text string identifying the snapshot. This string must be passed to clients that want to import the snapshot. A snapshot can be imported when the **set transaction snapshot snapshot_id;** command is executed. Doing so is possible only when the transaction is set to the **SERIALIZABLE** or **REPEATABLE READ** isolation level. The output of the function cannot be used as the input of **set transaction snapshot**.
+
+- pg_export_snapshot_and_csn()
+
+Description: Saves the current snapshot and returns its identifier. Compared with **pg_export_snapshot()**, **pg_export_snapshot()** returns a CSN, indicating the CSN of the current snapshot.
+
+Return type: text
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/6-database-object-functions.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/6-database-object-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..72e083fd5b9649d1676ab6f82bea410c3b178bcb
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/6-database-object-functions.md
@@ -0,0 +1,430 @@
+---
+title: Database Object Functions
+summary: Database Object Functions
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Database Object Functions
+
+## Database Object Size Functions
+
+Database object size functions calculate the actual disk space used by database objects.
+
+- pg_column_size(any)
+
+  Description: Specifies the number of bytes used to store a particular value (possibly compressed)
+
+  Return type: int
+
+  Note: **pg_column_size** displays the space for storing an independent data value.
+
+  ```sql
+  mogdb=# SELECT pg_column_size(1);
+   pg_column_size
+  ----------------
+                4
+  (1 row)
+  ```
+
+- pg_database_size(oid)
+
+  Description: Specifies the disk space used by the database with the specified OID.
+
+  Return type: bigint
+
+- pg_database_size(name)
+
+  Description: Specifies the disk space used by the database with the specified name.
+
+  Return type: bigint
+
+  Note: **pg_database_size** receives the OID or name of a database and returns the disk space used by the corresponding object.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT pg_database_size('postgres');
+   pg_database_size
+  ------------------
+           51590112
+  (1 row)
+  ```
+
+- pg_relation_size(oid)
+
+  Description: Specifies the disk space used by the table with a specified OID or index.
+
+  Return type: bigint
+
+- get_db_source_datasize()
+
+  Description: Estimates the total size of non-compressed data in the current database.
+
+  Return type: bigint
+
+  Remarks: (1) Perform an analysis before this function is called. (2) Calculate the total data capacity in the non-compressed state by estimating the compression rate of the column-store tables.
+
+  Example:
+
+  ```sql
+  mogdb=# analyze;
+  ANALYZE
+  openGauss=# select get_db_source_datasize();
+   get_db_source_datasize
+  ------------------------
+              35384925667
+  (1 row)
+  ```
+
+- pg_relation_size(text)
+
+  Description: Specifies the disk space used by the table with a specified name or index. The table name can be schema-qualified.
+
+  Return type: bigint
+
+- pg_relation_size(relation regclass, fork text)
+
+  Description: Specifies the disk space used by the specified bifurcating tree ('main', 'fsm', or 'vm') of a certain table or index.
+
+  Return type: bigint
+
+- pg_relation_size(relation regclass)
+
+  Description: Is an abbreviation of **pg_relation_size(…, 'main')**.
+
+  Return type: bigint
+
+  Note: **pg_relation_size** receives the OID or name of a table, an index, or a compressed table, and returns the size.
+
+- pg_partition_size(oid,oid)
+
+  Description: Specifies the disk space used by the partition with a specified OID. The first **oid** is the OID of the table and the second **oid** is the OID of the partition.
+
+  Return type: bigint
+
+- pg_partition_size(text, text)
+
+  Description: Specifies the disk space used by the partition with a specified name. The first **text** is the table name and the second **text** is the partition name.
+
+  Return type: bigint
+
+- pg_partition_indexes_size(oid,oid)
+
+  Description: Specifies the disk space used by the index of the partition with a specified OID. The first **oid** is the OID of the table and the second **oid** is the OID of the partition.
+
+  Return type: bigint
+
+- pg_partition_indexes_size(text,text)
+
+  Description: Specifies the disk space used by the index of the partition with a specified name. The first **text** is the table name and the second **text** is the partition name.
+
+  Return type: bigint
+
+- pg_indexes_size(regclass)
+
+  Description: Specifies the total disk space used by the index appended to the specified table.
+
+  Return type: bigint
+
+- pg_size_pretty(bigint)
+
+  Description: Converts a size in bytes expressed as a 64-bit integer into a human-readable format with size units.
+
+  Return type: text
+
+- pg_size_pretty(numeric)
+
+  Description: Converts a size in bytes expressed as a numeric value into a human-readable format with size units.
+
+  Return type: text
+
+  Note: **pg_size_pretty** formats the results of other functions into a human-readable format. KB/MB/GB/TB can be used.
+
+- pg_table_size(regclass)
+
+  Description: Specifies the disk space used by the specified table, excluding indexes (but including TOAST, free space mapping, and visibility mapping).
+
+  Return type: bigint
+
+- pg_tablespace_size(oid)
+
+  Description: Specifies the disk space used by the tablespace with a specified OID.
+
+  Return type: bigint
+
+- pg_tablespace_size(name)
+
+  Description: Specifies the disk space used by the tablespace with a specified name.
+
+  Return type: bigint
+
+  Note:
+
+  **pg_tablespace_size** receives the OID or name of a database and returns the disk space used by the corresponding object.
+
+- pg_total_relation_size(oid)
+
+  Description: Specifies the disk space used by the table with a specified OID, including the index and the compressed data.
+
+  Return type: bigint
+
+- pg_total_relation_size(regclass)
+
+  Description: Specifies the total disk space used by the specified table, including all indexes and TOAST data.
+
+  Return type: bigint
+
+- pg_total_relation_size(text)
+
+  Description: Specifies the disk space used by the table with a specified name, including the index and the compressed data. The table name can be schema-qualified.
+
+  Return type: bigint
+
+  Note: **pg_total_relation_size** receives the OID or name of a table or a compressed table, and returns the sizes of the data, related indexes, and the compressed table in bytes.
+
+- datalength(any)
+
+  Description: Specifies the number of bytes used by an expression of a specified data type (data management space, data compression, or data type conversion is not considered).
+
+  Return type: int
+
+  Note: **datalength** is used to calculate the space of an independent data value.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT datalength(1);
+  datalength
+  ------------
+  4
+  (1 row)
+  ```
+
+  The following table lists the supported data types and calculation methods.
+
+  <table>
+      <tr>
+          <th colspan=3>Data Type</th>
+          <th>Storage Space</th>
+      </tr>
+      <tr>
+          <td rowspan=18>Numeric data types</td>
+          <td rowspan=5>Integer types</td>
+          <td>TINYINT</td>
+          <td>1</td>
+      </tr>
+      <tr>
+          <td>SMALLINT</td>
+          <td>2</td>
+      </tr>
+      <tr>
+          <td>INTEGER</td>
+          <td>4</td>
+      </tr>
+      <tr>
+          <td>BINARY_INTEGER</td>
+          <td>4</td>
+      </tr>
+      <tr>
+          <td>BIGINT</td>
+          <td>8</td>
+      </tr>
+      <tr>
+          <td rowspan=3>Arbitrary precision types</td>
+          <td>DECIMAL</td>
+          <td>Every four decimal digits occupy two bytes. The digits before and after the decimal point are calculated separately.</td>
+      </tr>
+      <tr>
+          <td>NUMERIC</td>
+          <td>Every four decimal digits occupy two bytes. The digits before and after the decimal point are calculated separately.</td>
+      </tr>
+      <tr>
+          <td>NUMBER</td>
+          <td>Every four decimal digits occupy two bytes. The digits before and after the decimal point are calculated separately.</td>
+      </tr>
+      <tr>
+          <td rowspan=3>Sequence integer</td>
+          <td>SMALLSERIAL</td>
+          <td>2</td>
+      </tr>
+      <tr>
+          <td>SERIAL</td>
+          <td>4</td>
+      </tr>
+      <tr>
+          <td>BIGSERIAL</td>
+          <td>8</td>
+      </tr>
+      <tr>
+          <td rowspan=7>Floating point types</td>
+          <td>FLOAT4</td>
+          <td>4</td>
+      </tr>
+      <tr>
+          <td>DOUBLE PRECISION</td>
+          <td>8</td>
+      </tr>
+      <tr>
+          <td>FLOAT8</td>
+          <td>8</td>
+      </tr>
+      <tr>
+          <td>BINARY_DOUBLE</td>
+          <td>8</td>
+      </tr>
+      <tr>
+          <td>FLOAT[(p)]</td>
+          <td>Every four decimal digits occupy two bytes. The digits before and after the decimal point are calculated separately.</td>
+      </tr>
+      <tr>
+          <td>DEC[(p[,s])]</td>
+          <td>Every four decimal digits occupy two bytes. The digits before and after the decimal point are calculated separately.</td>
+      </tr>
+      <tr>
+          <td>INTEGER[(p[,s])]</td>
+          <td>Every four decimal digits occupy two bytes. The digits before and after the decimal point are calculated separately.</td>
+      </tr>
+      <tr>
+          <td>Boolean data types</td>
+          <td>Boolean types</td>
+          <td>BOOLEAN</td>
+          <td>1</td>
+      </tr>
+      <tr>
+          <td rowspan=11>Character data types</td>
+          <td rowspan=11>Character types</td>
+          <td>CHAR</td>
+          <td>n</td>
+      </tr>
+      <tr>
+          <td>CHAR(n)</td>
+          <td>n</td>
+      </tr>
+      <tr>
+          <td>CHARACTER(n)</td>
+          <td>n</td>
+      </tr>
+      <tr>
+          <td>NCHAR(n)</td>
+          <td>n</td>
+      </tr>
+      <tr>
+          <td>VARCHAR(n)</td>
+          <td>n</td>
+      </tr>
+      <tr>
+          <td>CHARACTER</td>
+          <td>Actual number of bytes of a character</td>
+      </tr>
+      <tr>
+          <td>VARYING(n)</td>
+          <td>Actual number of bytes of a character</td>
+      </tr>
+      <tr>
+          <td>VARCHAR2(n)</td>
+          <td>Actual number of bytes of a character</td>
+      </tr>
+      <tr>
+          <td>NVARCHAR2(n)</td>
+          <td>Actual number of bytes of a character</td>
+      </tr>
+      <tr>
+          <td>TEXT</td>
+          <td>Actual number of bytes of a character</td>
+      </tr>
+      <tr>
+          <td>CLOB</td>
+          <td>Actual number of bytes of a character</td>
+      </tr>
+      <tr>
+          <td rowspan=11>Time data types</td>
+          <td rowspan=11>Time types</td>
+          <td>DATE</td>
+          <td>8</td>
+      </tr>
+      <tr>
+          <td>TIME</td>
+          <td>8</td>
+      </tr>
+      <tr>
+          <td>TIMEZ</td>
+          <td>12</td>
+      </tr>
+      <tr>
+          <td>TIMESTAMP</td>
+          <td>8</td>
+      </tr>
+      <tr>
+          <td>TIMESTAMPZ</td>
+          <td>8</td>
+      </tr>
+      <tr>
+          <td>SMALLDATETIME</td>
+          <td>8</td>
+      </tr>
+      <tr>
+          <td>INTERVAL DAY TO SECOND</td>
+          <td>16</td>
+      </tr>
+      <tr>
+          <td>INTERVAL</td>
+          <td>16</td>
+      </tr>
+      <tr>
+          <td>RELTIME</td>
+          <td>4</td>
+      </tr>
+      <tr>
+          <td>ABSTIME</td>
+          <td>4</td>
+      </tr>
+      <tr>
+          <td>TINTERVAL</td>
+          <td>12</td>
+      </tr>
+  </table>
+
+## Database Object Position Functions
+
+- pg_relation_filenode(relation regclass)
+
+  Description: Specifies the ID of a filenode with the specified relationship.
+
+  Return type: oid
+
+  Description: **pg_relation_filenode** receives the OID or name of a table, an index, a sequence, or a compressed table, and returns the number of **filenode** allocated to it. **filenode** is the basic component of the file name used by the relationship. For most tables, the result is the same as that of **pg_class.relfilenode**. For a specified system directory, **relfilenode** is set to **0** and this function must be used to obtain the correct value. If a relationship that is not stored is transmitted, such as a view, this function returns **NULL**.
+
+- pg_relation_filepath(relation regclass)
+
+  Description: Specifies the name of a file path with the specified relationship.
+
+  Return type: text
+
+  Description: **pg_relation_filepath** is similar to **pg_relation_filenode**, except that **pg_relation_filepath** returns the whole file path name for the relationship (relative to the data directory **PGDATA** of openGauss).
+
+- pg_filenode_relation(tablespace oid, filenode oid)
+
+  Description: Obtains the table names corresponding to the tablespace and relfilenode.
+
+  Return type: regclass
+
+- pg_partition_filenode(partition_oid)
+
+  Description: Obtains **filenode** corresponding to the OID lock of a specified partitioned table.
+
+  Return type: oid
+
+- pg_partition_filepath(partition_oid)
+
+  Description: Specifies the file path name of a partition.
+
+  Return type: text
+
+## Recycle Bin Object Functions
+
+- gs_is_recycle_object(classid, objid, objname)
+
+  Description: Determines whether an object is in the recycle bin.
+
+  Return type: Boolean
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/7-advisory-lock-functions.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/7-advisory-lock-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..222060dd71147d3ae236a5141474bacffdff239d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/7-advisory-lock-functions.md
@@ -0,0 +1,190 @@
+---
+title: Advisory Lock Functions
+summary: Advisory Lock Functions
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Advisory Lock Functions
+
+Advisory lock functions manage advisory locks.
+
+- pg_advisory_lock(key bigint)
+
+  Description: Obtains an exclusive session-level advisory lock.
+
+  Return type: void
+
+  Note:**pg_advisory_lock** locks resources defined by an application. The resources can be identified using a 64-bit or two nonoverlapped 32-bit key values. If another session locks the resources, the function blocks the resources until they can be used. The lock is exclusive. Multiple locking requests are pushed into the stack. Therefore, if the same resource is locked three times, it must be unlocked three times so that it is released to another session.
+
+- pg_advisory_lock(key1 int, key2 int)
+
+  Description: Obtains an exclusive session-level advisory lock.
+
+  Return type: void
+
+  Note: Only users with the **sysadmin** permission can add session-level exclusive advisory locks to the key-value pair (65535, 65535).
+
+- pg_advisory_lock(int4, int4, Name)
+
+    Description: Obtains the exclusive advisory lock of a specified database.
+
+    Return type: void
+
+- pg_advisory_lock_shared(key bigint)
+
+  Description: Obtains a shared session-level advisory lock.
+
+  Return type: void
+
+- pg_advisory_lock_shared(key1 int, key2 int)
+
+  Description: Obtains a shared session-level advisory lock.
+
+  Return type: void
+
+  Note:**pg_advisory_lock_shared** works in the same way as **pg_advisory_lock**, except the lock can be shared with other sessions requesting shared locks. Only would-be exclusive lockers are locked out.
+
+- pg_advisory_unlock(key bigint)
+
+  Description: Releases an exclusive session-level advisory lock.
+
+  Return type: Boolean
+
+- pg_advisory_unlock(key1 int, key2 int)
+
+  Description: Releases an exclusive session-level advisory lock.
+
+  Return type: Boolean
+
+  Note:**pg_advisory_unlock** releases the obtained exclusive advisory lock. If the release is successful, the function returns **true**. If the lock was not held, it will return **false**. In addition, a SQL warning will be reported by the server.
+
+- pg_advisory_unlock(int4, int4, Name)
+
+    Description: Releases the exclusive advisory lock of a specified database.
+
+    Return type: Boolean
+
+    Note: If the release is successful,  **true**  is returned. If no lock is held,  **false**  is returned.
+
+- pg_advisory_unlock_shared(key bigint)
+
+  Description: Releases a shared session-level advisory lock.
+
+  Return type: Boolean
+
+- pg_advisory_unlock_shared(key1 int, key2 int)
+
+  Description: Releases a shared session-level advisory lock.
+
+  Return type: Boolean
+
+  Note:**pg_advisory_unlock_shared** works in the same way as **pg_advisory_unlock**, except it releases a shared session-level advisory lock.
+
+- pg_advisory_unlock_all()
+
+  Description: Releases all advisory locks owned by the current session.
+
+  Return type: void
+
+  Note:**pg_advisory_unlock_all** releases all advisory locks owned by the current session. The function is implicitly invoked when the session ends even if the client is abnormally disconnected.
+
+- pg_advisory_xact_lock(key bigint)
+
+  Description: Obtains an exclusive transaction-level advisory lock.
+
+  Return type: void
+
+- pg_advisory_xact_lock(key1 int, key2 int)
+
+  Description: Obtains an exclusive transaction-level advisory lock.
+
+  Return type: void
+
+  Note:**pg_advisory_xact_lock** works in the same way as **pg_advisory_lock**, except the lock is automatically released at the end of the current transaction and cannot be released explicitly. Only users with the **sysadmin** permission can add transaction-level exclusive advisory locks to the key-value pair (65535, 65535).
+
+- pg_advisory_xact_lock_shared(key bigint)
+
+  Description: Obtains a shared transaction-level advisory lock.
+
+  Return type: void
+
+- pg_advisory_xact_lock_shared(key1 int, key2 int)
+
+  Description: Obtains a shared transaction-level advisory lock.
+
+  Return type: void
+
+  Note:**pg_advisory_xact_lock_shared** works in the same way as **pg_advisory_lock_shared**, except the lock is automatically released at the end of the current transaction and cannot be released explicitly.
+
+- pg_try_advisory_lock(key bigint)
+
+  Description: Obtains an exclusive session-level advisory lock if available.
+
+  Return type: Boolean
+
+  Note:**pg_try_advisory_lock** is similar to **pg_advisory_lock**, except **pg_try_advisory_lock** does not block the resource until the resource is released. **pg_try_advisory_lock** either immediately obtains the lock and returns **true** or returns **false**, which indicates the lock cannot be performed currently.
+
+- pg_try_advisory_lock(key1 int, key2 int)
+
+  Description: Obtains an exclusive session-level advisory lock if available.
+
+  Return type: Boolean
+
+  Note: Only users with the **sysadmin** permission can add session-level exclusive advisory locks to the key-value pair (65535, 65535).
+
+- pg_try_advisory_lock_shared(key bigint)
+
+  Description: Obtains a shared session-level advisory lock if available.
+
+  Return type: Boolean
+
+- pg_try_advisory_lock_shared(key1 int, key2 int)
+
+  Description: Obtains a shared session-level advisory lock if available.
+
+  Return type: Boolean
+
+  Note:**pg_try_advisory_lock_shared** is similar to **pg_try_advisory_lock**, except **pg_try_advisory_lock_shared** attempts to obtain a shared lock instead of an exclusive lock.
+
+- pg_try_advisory_xact_lock(key bigint)
+
+  Description: Obtains an exclusive transaction-level advisory lock if available.
+
+  Return type: Boolean
+
+- pg_try_advisory_xact_lock(key1 int, key2 int)
+
+  Description: Obtains an exclusive transaction-level advisory lock if available.
+
+  Return type: Boolean
+
+  Note:**pg_try_advisory_xact_lock** works in the same way as **pg_try_advisory_lock**, except the lock, if acquired, is automatically released at the end of the current transaction and cannot be released explicitly. Note: Only users with the **sysadmin** permission can add transaction-level exclusive advisory locks to the key-value pair (65535, 65535).
+
+- pg_try_advisory_xact_lock_shared(key bigint)
+
+  Description: Obtains a shared transaction-level advisory lock if available.
+
+  Return type: Boolean
+
+- pg_try_advisory_xact_lock_shared(key1 int, key2 int)
+
+  Description: Obtains a shared transaction-level advisory lock if available.
+
+  Return type: Boolean
+
+  Note:**pg_try_advisory_xact_lock_shared** works in the same way as **pg_try_advisory_lock_shared**, except the lock, if acquired, is automatically released at the end of the current transaction and cannot be released explicitly.
+
+- lock_cluster_ddl()
+
+  Description: Attempts to obtain a session-level exclusive advisory lock for all active primary database nodes in MogDB.
+
+  Return type: Boolean
+
+  Note: Only users with the **sysadmin** permission can call this function.
+
+- unlock_cluster_ddl()
+
+  Description: Attempts to add a session-level exclusive advisory lock on the primary database node.
+
+  Return type: Boolean
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/8-logical-replication-functions.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/8-logical-replication-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..6ea96cdc2cfe6a69ec1a98dc1f71053bf536567e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/8-logical-replication-functions.md
@@ -0,0 +1,171 @@
+---
+title: Logical Replication Functions
+summary: Logical Replication Functions
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Logical Replication Functions
+
+- pg_create_logical_replication_slot('slot_name', 'plugin_name')
+
+  Description: Creates a logical replication slot.
+
+  Parameter description:
+
+  - slot_name
+
+    Indicates the name of the streaming replication slot.
+
+    Value range: a string, supporting only letters, digits, and the following special characters: _?-.
+
+  - plugin_name
+
+    Indicates the name of the plugin.
+
+    Value range: a string, supporting **mppdb_decoding**
+
+  Return type: name, text
+
+  Note: The first return value is the slot name, and the second is the start LSN position for decoding in the logical replication slot.
+
+- pg_create_physical_replication_slot('slot_name', 'isDummyStandby')
+
+  Description: Creates a physical replication slot.
+
+  Parameter description:
+
+  - slot_name
+
+    Indicates the name of the streaming replication slot.
+
+    Value range: a string, supporting only letters, digits, and the following special characters: _?-.
+
+  - isDummyStandby
+
+    Specifies whether the replication slot is created by connecting the secondary server to the primary server.
+
+    Type: bool
+
+    Return type: name, text
+
+- pg_drop_replication_slot('slot_name')
+
+  Description: Deletes a streaming replication slot.
+
+  Parameter description:
+
+  - slot_name
+
+    Indicates the name of the streaming replication slot.
+
+    Value range: a string, supporting only letters, digits, and the following special characters: _?-.
+
+  Return type: void
+
+- pg_logical_slot_peek_changes('slot_name', 'LSN', upto_nchanges, 'options_name', 'options_value') <a id="pg_logical"> </a>
+
+  Description: Performs decoding but does not go to the next streaming replication slot. (The decoding result will be returned again on future calls.)
+
+  Parameter description:
+
+  - slot_name
+
+    Indicates the name of the streaming replication slot.
+
+    Value range: a string, supporting only letters, digits, and the following special characters: _?-.
+
+  - LSN
+
+    Indicates a target LSN. Decoding is performed only when an LSN is less than or equal to this value.
+
+    Value range: a string, in the format of xlogid/xrecoff, for example, '1/2AAFC60' (If this parameter is set to **NULL**, the target LSN indicating the end position of decoding is not specified.)
+
+  - upto_nchanges
+
+    Indicates the number of decoded records (including the **begin** and **commit** timestamps). Assume that there are three transactions, which involve 3, 5, and 7 records, respectively. If **upto_nchanges** is **4**, 8 records of the first two transactions will be decoded. Specifically, decoding is stopped when the number of decoded records exceeds 4 after decoding in the first two transactions is finished.
+
+    Value range: a non-negative integer
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** If any of the **LSN** and **upto_nchanges** values are reached, decoding ends.
+
+  - options (optional)
+
+    - include-xids
+
+    Indicates whether the decoded **data** column contains XID information.
+
+    Valid value:**0** and **1**. The default value is **1**.
+
+    - **0**: The decoded **data** column does not contain XID information.
+    - **1**: The decoded **data** column contains XID information.
+
+    - skip-empty-xacts
+
+      Indicates whether to ignore empty transaction information during decoding.
+
+      Valid value:**0** and **1**. The default value is **0**.
+
+      - **0**: The empty transaction information is not ignored during decoding.
+      - **1**: The empty transaction information is ignored during decoding.
+
+    - include-timestamp
+
+        Indicates whether decoding information contains the **commit** timestamp.
+
+        Valid value:**0** and **1**. The default value is **0**.
+
+    - **0**: The decoding information does not contain the **commit** timestamp.
+    - **1**: The decoding information contains the **commit** timestamp.
+
+  Return type: text, uint, text
+
+  Note: The function returns the decoding result. Each decoding result contains three columns, corresponding to the above return types and indicating the LSN position, XID, and decoded content, respectively.
+
+- pg_logical_slot_get_changes('slot_name', 'LSN', upto_nchanges, 'options_name', 'options_value')
+
+  Description: Performs decoding and goes to the next streaming replication slot.
+
+  Parameter: This function has the same parameters as **pg_logical_slot_peek_changes**. For details, see [pg_logical_slot_peek_ch…](#pg_logical).
+
+- pg_replication_slot_advance ('slot_name', 'LSN')
+
+  Description: Directly goes to the streaming replication slot for a specified LSN, without outputting any decoding result.
+
+  Parameter description:
+
+  - slot_name
+
+    Indicates the name of the streaming replication slot.
+
+    Value range: a string, supporting only letters, digits, and the following special characters: _?-.
+
+  - LSN
+
+    Indicates a target LSN. Next decoding will be performed only in transactions whose commission position is greater than this value. If an input LSN is smaller than the position recorded in the current streaming replication slot, the function directly returns. If the input LSN is greater than the LSN of the current physical log, the latter LSN will be directly used for decoding.
+
+    Value range: a string, in the format of xlogid/xrecoff
+
+  Return type: name, text
+
+  Note: A return result contains the slot name and LSN that is actually used for decoding.
+
+- pg_get_replication_slots
+
+  Description: Obtains the replication slot list.
+
+  Return type: text, text, text, oid, boolean, xid, xid, text, boolean
+
+  Example:
+
+  ```sql
+  mogdb=# select * from pg_get_replication_slots();
+   slot_name |     plugin     | slot_type | datoid | active | xmin | catalog_xmin | restart_lsn | dummy_standby
+  -----------+----------------+-----------+--------+--------+------+--------------+-------------+---------------
+   wkl001    | mppdb_decoding | logical   |  15914 | f      |      |      2079556 | 4/1B81D920  | f
+   dn_6002   |                | physical  |      0 | t      |      |              | 8/7CB63BD8  | f
+   dn_6004   |                | physical  |      0 | t      |      |              | 8/7CB63BD8  | f
+   dn_6003   |                | physical  |      0 | t      |      |              | 8/7CB63BD8  | f
+   gfslot001 | mppdb_decoding | logical   |  15914 | f      |      |      2412553 | 4/A54B2428  | f
+  (5 rows)
+  ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/9-other-functions.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/9-other-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..55577bb9f31f052127ed78f3d99745cdcbb43b71
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/9-other-functions.md
@@ -0,0 +1,476 @@
+---
+title: Other Functions
+summary: Other Functions
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Other Functions
+
+- plan_seed()
+
+  Description: Obtains the seed value of the previous query statement (internal use).
+
+  Return type: int
+
+- pg_stat_get_env()
+
+  Description: Obtains the environment variable information of the current node. Only users with the **sysadmin** or **monitor admin** permission can access the environment variable information.
+
+  Return type: record
+
+  Example:
+
+  ```sql
+  mogdb=# select pg_stat_get_env();
+                                                                                pg_stat_get_env
+  ---------------------------------------------------------------------------------------------------------------------------------------
+   (coordinator1,localhost,144773,49100,/data1/GaussDB_Kernel_TRUNK/install,/data1/GaussDB_Kernel_TRUNK/install/data/coordinator1,pg_log)
+  (1 row)
+  ```
+
+- pg_catalog.plancache_clean()
+
+  Description: Clears the global plan cache that is not used on nodes.
+
+  Return type: Boolean
+
+- pg_catalog.plancache_status()
+
+  Description: Displays information about the global plan cache on nodes. The information returned by the function is the same as that in GLOBAL_PLANCACHE_STATUS.
+
+  Return type: record
+
+- textlen(text)
+
+  Description: Provides the method of querying the logical length of text.
+
+  Return type: int
+
+- threadpool_status()
+
+  Description: Displays the status of worker threads and sessions in the thread pool.
+
+  Return type: record
+
+- get_local_active_session()
+
+  Description: Provides sampling records of the historical active sessions stored in the memory of the current node.
+
+  Return type: record
+
+- pg_stat_get_thread()
+
+  Description: Provides status information about all threads on the current node. Users with the **sysadmin** or **monitor admin** permission can view information about all threads, and common users can view only their own thread information.
+
+  Return type: record
+
+- pg_stat_get_sql_count()
+
+  Description: Provides the counts of the **SELECT**, **UPDATE**, **INSERT**, **DELETE**, and **MERGE INTO** statements executed on the current node. Users with the **sysadmin** or **monitor admin** permission can view information about all users, and common users can view only their own statistics.
+
+  Return type: record
+
+- pg_stat_get_data_senders()
+
+  Description: Provides detailed information about the data-copy sending thread active at the moment.
+
+  Return type: record
+
+- get_wait_event_info()
+
+  Description: Provides detailed information about the wait event.
+
+  Return type: record
+
+- generate_wdr_report(begin_snap_id bigint, end_snap_id bigint, report_type cstring, report_scope cstring, node_name cstring)
+
+  Description: Generates system diagnosis reports based on two snapshots. You need to run the command in the **postgres** database. By default, the initial user or the user with the **monadmin** permission can access the database. In V500R001C20SPC002 and earlier versions, the initial user or the user with the **sysadmin** permission can access the database. The result can be queried only in the system database but cannot be queried in the user database.
+
+  Return type: record
+
+  **Table 1** generate_wdr_report parameter description
+
+  | Parameter     | Description                                                  | Range                                                        |
+  | ------------- | ------------------------------------------------------------ | ------------------------------------------------------------ |
+  | begin_snap_id | Snapshot ID that starts the diagnosis report period.         | -                                                            |
+  | end_snap_id   | Snapshot ID that ends the diagnosis report period. By default, the value of **end_snap_id** is greater than that of **begin_snap_id**. | -                                                            |
+  | report_type   | Specifies the type of the generated report.                  | **summary****detail****all**: Both **summary** and **detail** types are included. |
+  | report_scope  | Specifies the scope for a report to be generated.            | **cluster**: database-level information**node**: node-level information |
+  | node_name     | When **report\_scope** is set to **node**, set this parameter to the name of the corresponding node. (You can run the **select \* from pg_node_env;** command to query the node name.)If **report\_scope** is set to **cluster**, this parameter can be omitted, left blank, or set to **NULL**. | **cluster**: This value is omitted, left blank or set to **NULL**.**node**: indicates the node name in MogDB. |
+
+- create_wdr_snapshot()
+
+  Description: Manually generates system diagnosis snapshots. This function requires the **sysadmin** permission.
+
+  Return type: text
+
+- kill_snapshot()
+
+  Description: Kills the WDR snapshot backend thread. Users who invoke this function must have the **SYSADMIN** permission, the **REPLICATION** permission, or inherit the **gs_role_replication** permission of the built-in role.
+
+  Return type: void
+
+- capture_view_to_json(text,integer)
+
+  Description: Saves the view result to the directory specified by GUC: **perf_directory**. If **is_crossdb** is set to **1**, the view is accessed once for all databases. If the value of **is_crossdb** is **0**, the current database is accessed only once. Only users with the **sysadmin** or **monitor admin** permission can execute this function.
+
+  Return type: int
+
+- reset_unique_sql
+
+  Description: Clears the unique SQL statements in the memory of the database node. (The **sysadmin** permission is required.)
+
+  Return type: Boolean
+
+  **Table 2** reset_unique_sql parameter description
+
+  | Parameter   | Type | Description                                                  |
+  | :---------- | :--- | :----------------------------------------------------------- |
+  | scope       | text | Clearance scope type. The options are as follows:**GLOBAL**: Clears all nodes. If the value is **GLOBAL**, this function can be executed only on the primary node.**LOCAL**: Clears the current node. |
+  | clean_type  | text | **BY_USERID**: Unique SQL statements are cleared based on user IDs.**BY_CNID**: Unique SQL statements are cleared based on primary node IDs.**ALL**: All data is cleared. |
+  | clean_value | int8 | Clearance value corresponding to the clearance type.         |
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+  >
+  > - The values **GLOBAL** and **LOCAL** of **scope** apply to distributed databases. For MogDB, the values have the same meaning, indicating that the local node is cleared.
+  > - The value **BY_CNID** of **clean_type** applies only to distributed databases and is invalid for MogDB.
+
+- wdr_xdb_query(db_name_str text, query text)
+
+  Description: Provides the capability of executing local cross-database queries. For example, when connecting to the Postgres database, access tables in the **test** database.
+
+  ```sql
+  select col1 from wdr_xdb_query('dbname=test','select col1 from t1') as dd(col1 int);
+  ```
+
+  Return type: record
+
+- pg_wlm_jump_queue(pid int)
+
+    Description: Moves a task to the top of the queue of the primary node of the database.
+
+    Return type: Boolean
+
+  - **true**: success
+  - **false**: failure
+
+- gs_wlm_switch_cgroup(pid int, cgroup text)
+
+    Description: Moves a job to another Cgroup to change the job priority.
+
+    Return type: Boolean
+
+  - **true**: success
+  - **false**: failure
+
+- pv_session_memctx_detail(threadid tid, MemoryContextName text)
+
+    Description: Records information about the memory context **MemoryContextName** of the thread **tid** into the *threadid***_timestamp.log** file in the *$GAUSSLOG***/pg_log/***${node_name}***/dumpmem** directory. *threadid* can be obtained from *sessid* in the **GS_SESSION_MEMORY_DETAIL** view. In the officially released version, only the **MemoryContextName** that is an empty string (two single quotation marks indicate that the input is an empty string) is accepted. In this case, all memory context information is recorded. Otherwise, no operation is performed. For the DEBUG version for internal development and test personnel to debug, you can specify the **MemoryContextName** to be counted. In this case, all the memory usage of the context is recorded in the specified file. Only the administrator can execute this function.
+
+    Return type: Boolean
+
+  - **true**: success
+  - **false**: failure
+
+- pg_shared_memctx_detail(MemoryContextName text)
+
+    Description: Records information about the memory context **MemoryContextName** into the *threadid***_timestamp.log** file in the *$GAUSSLOG***/pg_log/***${node_name}***/dumpmem** directory. This function is provided only for internal development and test personnel to debug in the DEBUG version. Calling this function in the officially released version does not involve any operation. Only the administrator can execute this function.
+
+    Return type: Boolean
+
+  - **true**: success
+  - **false**: failure
+
+- local_bgwriter_stat()
+
+  Description: Displays the information about pages flushed by the bgwriter thread of this instance, number of pages in the candidate buffer chain, and buffer elimination information.
+
+  Return type: record
+
+- local_candidate_stat()
+
+  Description: Displays the number of pages in the candidate buffer chain of this instance and buffer elimination information, including the normal buffer pool and segment buffer pool.
+
+  Return type: record
+
+- local_ckpt_stat()
+
+  Description: Displays the information about checkpoints and flushing pages of the current instance.
+
+  Return type: record
+
+- local_double_write_stat()
+
+  Description: Displays the doublewrite file status of the current instance.
+
+  Return type: record
+
+- local_single_flush_dw_stat()
+
+  Description: Displays the elimination of dual-write files on a single page in the instance.
+
+  Return type: record
+
+- local_pagewriter_stat()
+
+  Description: Displays the page flushing information and checkpoint information of the current instance.
+
+  Return type: record
+
+- local_redo_stat()
+
+  Description: Displays the replay status of the current standby instance.
+
+  Return type: record
+
+  Note: The returned replay status includes the current replay position and the replay position of the minimum restoration point.
+
+- local_recovery_status()
+
+  Description: Displays log flow control information about the primary and standby nodes.
+
+  Return type: record
+
+- gs_wlm_node_recover(boolean isForce)
+
+  Description: Obtains top SQL query statement-level statistics recorded in the current memory. If the input parameter is not **0**, the information is cleared from the memory.
+
+  Return type: record
+
+- gs_wlm_node_clean(cstring nodename)
+
+  Description: Clears data after the dynamic load management node is faulty. Only administrators can execute this function. This function is called by the cluster management module. You are not advised to directly call this function. This view is not supported in a centralized or standalone system.
+
+  Return type: Boolean
+
+- gs_cgroup_map_ng_conf(group name)
+
+  Description: Reads the Cgroup configuration file of a specified logical database.
+
+  Return type: record
+
+- gs_wlm_switch_cgroup(sess_id int8, cgroup name)
+
+  Description: Switches the Cgroup of a specified session.
+
+  Return type: record
+
+- hdfs_fdw_handler()
+
+  Description: Rewrites a foreign table. It is a function to be defined when a foreign table is defined.
+
+  Return type: record
+
+- hdfs_fdw_validator(text[], oid)
+
+  Description: Rewrites a foreign table. It is a function to be defined when a foreign table is defined.
+
+  Return type: record
+
+- comm_client_info()
+
+  Description: Queries information about active client connections of a single node.
+
+  Return type: SETOF record
+
+- pg_sync_cstore_delta(text)
+
+  Description: Synchronizes the delta table structure of a specified column-store table with that of the column-store primary table.
+
+  Return type: bigint
+
+- pg_sync_cstore_delta()
+
+  Description: Synchronizes the delta table structure of all column-store tables with that of the column-store primary table.
+
+  Return type: bigint
+
+- pg_get_flush_lsn()
+
+  Description: Returns the location of the Xlog flushed from the current node.
+
+  Return type: text
+
+- pg_get_sync_flush_lsn()
+
+  Description: Returns the location of the Xlog flushed by the majority on the current node.
+
+  Return type: text
+
+- gs_create_log_tables()
+
+  Description: Creates foreign tables and views for run logs and performance logs.
+
+  Return type: void
+
+  Example:
+
+  ```
+  mogdb=# select gs_create_log_tables();
+   gs_create_log_tables
+  ----------------------
+
+  (1 row)
+  ```
+
+- dbe_perf.get_global_full_sql_by_timestamp(start_timestamp timestamp with time zone, end_timestamp timestamp with time zone)
+
+  Description: Obtains full SQL information at the database level. The result can be queried only in the system database but cannot be queried in the user database.
+
+  Return type: record
+
+  **Table 3** dbe_perf.get_global_full_sql_by_timestamp parameter description
+
+  | Parameter       | Type                     | Description                              |
+  | :-------------- | :----------------------- | :--------------------------------------- |
+  | start_timestamp | timestamp with time zone | Start point of the SQL start time range. |
+  | end_timestamp   | timestamp with time zone | End point of the SQL start time range.   |
+
+- dbe_perf.get_global_slow_sql_by_timestamp(start_timestamp timestamp with time zone, end_timestamp timestamp with time zone)
+
+  Description: Obtains slow SQL information at the database level. The result can be queried only in the system database but cannot be queried in the user database.
+
+  Return type: record
+
+  **Table 4** dbe_perf.get_global_slow_sql_by_timestamp parameter description
+
+  | Parameter       | Type                     | Description                              |
+  | :-------------- | :----------------------- | :--------------------------------------- |
+  | start_timestamp | timestamp with time zone | Start point of the SQL start time range. |
+  | end_timestamp   | timestamp with time zone | End point of the SQL start time range.   |
+
+- statement_detail_decode(detail text, format text, pretty boolean)
+
+  Description: Parses the **details** column in a full or slow SQL statement. The result can be queried only in the system database but cannot be queried in the user database.
+
+  Return type: text
+
+  **Table 5** statement_detail_decode parameter description
+
+  | Parameter  | Type    | Description                                                  |
+  | :--------- | :------ | :----------------------------------------------------------- |
+  | **detail** | text    | Set of events generated by the SQL statement (unreadable).   |
+  | format     | text    | Parsing output format. The value is **plaintext**.           |
+  | pretty     | boolean | Whether to display the text in pretty format when **format** is set to **plaintext**. The options are as follows:The value **true** indicates that events are separated by **\n**.The value **false** indicates that events are separated by commas (,). |
+
+- get_prepared_pending_xid
+
+  Description: Returns nextxid when restoration is complete.
+
+  Parameter: nan
+
+  Return type: text
+
+- pg_clean_region_info
+
+  Description: Clears the regionmap.
+
+  Parameter: nan
+
+  Return type: character varying
+
+- pg_get_delta_info
+
+  Description: Obtains delta information from a single DN.
+
+  Parameter: rel text, schema_name text
+
+  Return type: part_name text, live_tuple bigint, data_size bigint, and blocknum bigint
+
+- pg_get_replication_slot_name
+
+  Description: Obtains the slot name.
+
+  Parameter: nan
+
+  Return type: text
+
+- pg_get_running_xacts
+
+  Description: Obtains running transactions.
+
+  Parameter: **nan**
+
+  Return type: handle integer, gxid xid, state tinyint, node text, xmin xid, vacuum boolean, timeline bigint, prepare_xid xid, pid bigint, and next_xid xid
+
+- pg_get_variable_info
+
+  Description: Obtains the shared memory variable *cache*.
+
+  Parameter: nan
+
+  Return type: node_name text, nextOid oid, nextXid xid, oldestXid xid, xidVacLimit xid, oldestXidDB oid, lastExtendCSNLogpage xid, startExtendCSNLogpage xid, nextCommitSeqNo xid, latestCompletedXid xid, and startupMaxXid xid
+
+- pg_get_xidlimit
+
+  Description: Obtains transaction ID information from the shared memory.
+
+  Parameter: nan
+
+  Return type: nextXid xid, oldestXid xid, xidVacLimit xid, xidWarnLimit xid, xidStopLimit xid, xidWrapLimit xid, and oldestXidDB oid
+
+- get_global_user_transaction()
+
+  Description: Returns transaction information about each user on all nodes.
+
+  Return type: node_name name, usename name, commit_counter bigint, rollback_counter bigint, resp_min bigint, resp_max bigint, resp_avg bigint, resp_total bigint, bg_commit_counter bigint, bg_rollback_counter bigint, bg_resp_min bigint, bg_resp_max bigint, bg_resp_avg bigint, and bg_resp_total bigint
+
+- pg_collation_for
+
+  Description: Returns the sorting rule corresponding to the input parameter string.
+
+  Parameter: any (Explicit type conversion is required for constants.)
+
+  Return type: text
+
+- pgxc_unlock_for_sp_database(name Name)
+
+  Description: Releases a specified database lock.
+
+  Parameter: database name
+
+  Return type: Boolean
+
+- pgxc_lock_for_sp_database(name Name)
+
+  Description: Locks a specified database.
+
+  Parameter: database name
+
+  Return type: Boolean
+
+- copy_error_log_create()
+
+  Description: Creates the error table (**public.pgxc_copy_error_log**) required for creating the **COPY FROM** error tolerance mechanism.
+
+  Return type: Boolean
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > - This function attempts to create the **public.pgxc_copy_error_log** table. For details about the table, see Table 6.
+  > - Create the B-tree index on the **relname** column and execute **REVOKE ALL on public.pgxc_copy_error_log FROM public** to manage permissions for the error table (the permissions are the same as those of the **COPY** statement).
+  > - **public.pgxc_copy_error_log** is a row-store table. Therefore, this function can be executed and **COPY** error tolerance is available only when row-store tables can be created in the database instance. Note that after the GUC parameter **enable_hadoop_env** is enabled, row-store tables cannot be created in the database instance (the default value is **off** for MogDB).
+  > - Same as the error table and the **COPY** statement, the function requires **sysadmin** or higher permissions.
+  > - If the **public.pgxc_copy_error_log** table or the **copy_error_log_relname_idx** index exists before the function creates it, the function will report an error and roll back.
+
+  **Table 6** Error table public.pgxc_copy_error_log
+
+  | Column     | Type                     | Description                                                  |
+  | :--------- | :----------------------- | :----------------------------------------------------------- |
+  | relname    | character varying        | Table name in the form of *Schema name***.***Table name*     |
+  | begintime  | timestamp with time zone | Time when a data format error was reported                   |
+  | filename   | character varying        | Name of the source data file where a data format error occurs |
+  | lineno     | bigint                   | Number of the row where a data format error occurs in a source data file |
+  | rawrecord  | text                     | Raw record of a data format error in the source data file    |
+  | **detail** | text                     | Error details                                                |
+
+- gs_comm_proxy_thread_status()
+
+  Description: Collects statistics on data packets sent and received by the proxy communication library **comm_proxy** when a user-mode network is configured for the cluster.
+
+  Parameter: nan
+
+  Return type: record
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The query result of this function is displayed only when the user-mode network is deployed in a centralized environment and **enable_dfx in comm_proxy_attr** is set to **true**. In other scenarios, an error message is displayed, indicating that queries are not supported.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/9.1-segment-page-storage-functions.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/9.1-segment-page-storage-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..ae7df68db9701e8dc1d1363ec53a3e3c93533b55
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/9.1-segment-page-storage-functions.md
@@ -0,0 +1,113 @@
+---
+title: Segment-Page Storage Functions
+summary: Segment-Page Storage Functions
+author: Guo Huan
+date: 2021-10-28
+---
+
+# Segment-Page Storage Functions
+
+- local_segment_space_info(tablespacename TEXT, databasename TEXT)
+
+  Description: Generates usage information about all extent groups in the tablespace.
+
+  Return type:
+
+  | node_name        | Node name                                                    |
+  | ---------------- | ------------------------------------------------------------ |
+  | extent_size      | Extent specifications of an extent group. The unit is the number of blocks. |
+  | forknum          | Fork number                                                  |
+  | total_blocks     | Total number of extents in a physical file                   |
+  | meta_data_blocks | Number of blocks occupied by the metadata managed in a tablespace, including the space header and map page but excluding the segment head |
+  | used_data_blocks | Number of extents used for storing data, including the segment head |
+  | utilization      | Percentage of the number of used blocks to the total number of blocks, that is, (the value of **used_data_blocks** + the value of **meta_data_block**)/the value of **total_blocks** |
+  | high_water_mark  | High-water mark, indicating the number of allocated extents and maximum physical page number. Blocks that exceed the high-water mark are not used and can be directly recycled. |
+
+  Example:
+
+  ```sql
+  select * from local_segment_space_info('pg_default', 'postgres');
+       node_name     | extent_size | forknum | total_blocks | meta_data_blocks | used_data_blocks | utilization | high_water_mark
+  -------------------+-------------+---------+--------------+------------------+------------------+-------------+-----------------
+   dn_6001_6002_6003 |           1 |       0 |        16384 |             4157 |                1 |     .253784 |            4158
+   dn_6001_6002_6003 |           8 |       0 |        16384 |             4157 |                8 |     .254211 |            4165
+  (2 rows)
+  ```
+
+- pg_stat_segment_extent_usage(int4 tablespace oid, int4 database oid, int4 extent_type, int4 forknum)
+
+  Description: Specifies the usage information of each allocated extent in an extent group returned each time. **extent_type** indicates the type of the extent group. The value is an integer ranging from 1 to 5. If the value is not within the range, an error is reported. **forknum** indicates the fork number. The value is an integer ranging from 0 to 4. Currently, only the following values are valid: **0** for data files, **1** for FSM files, and **2** for visibility map files.
+
+  Return type:
+
+  | Name          | Description                                                  |
+  | :------------ | :----------------------------------------------------------- |
+  | start_block   | Start physical page number of an extent                      |
+  | extent_size   | Size of an extent                                            |
+  | usage_type    | Usage type of an extent, for example, **segment head** and **data extent** |
+  | ower_location | Object location of an extent to which a pointer points. For example, the owner of a data extent is the head of the segment to which the data extent belongs. |
+  | special_data  | Position of an extent in its owner. The value of this field is related to the usage type. For example, special data of a data extent is the extent ID in the segment to which the data extent belongs. |
+
+  The value of **usage_type** is enumerated. The meaning of each value is as follows:
+
+  - **Non-bucket table segment head**: data segment head of a non-hash bucket table
+  - **Non-bucket table fork head**: fork segment header of a non-segment-page table
+  - **Data extent**: data block
+
+  Example:
+
+  ```sql
+  select * from pg_stat_segment_extent_usage((select oid::int4 from pg_tablespace where spcname='pg_default'), (select oid::int4 from pg_database where datname='postgres'), 1, 0);
+  start_block | extent_size |       usage_type       | ower_location | special_data
+  -------------+-------------+------------------------+---------------+--------------
+  4157 |           1 | Data extent |    4294967295 |            0
+  4158 |           1 | Data extent |          4157 |            0
+  ```
+
+- local_space_shrink(tablespacename TEXT, databasename TEXT)
+
+  Description: Compresses specified physical segment-page space on the current node. Only the currently connected database can be shrank.
+
+  Return value: empty
+
+- gs_space_shrink(int4 tablespace, int4 database, int4 extent_type, int4 forknum)
+
+  Description: Works similar to **local_space_shrink**, that is, compresses specified physical segment-page space. However, the parameters are different. The input parameters are the OIDs of the tablespace and database, and the value of **extent_type** is an integer ranging from 2 to 5. Note: The value **1** of **extent_type** indicates segment-page metadata. Currently, the physical file that contains the metadata cannot be compressed. This function is used only by tools. You are not advised to use it directly.
+
+  Return value: empty
+
+- pg_stat_remain_segment_info()
+
+  Description: Displays residual extents on the current node due to faults. Residual extents are classified into two types: segments that are allocated but not used and extents that are allocated but not used. The main difference is that a segment contains multiple extents. During reclamation, all extents in the segment need to be recycled.
+
+  Return type:
+
+  | Name     | Description                                                  |
+  | -------- | ------------------------------------------------------------ |
+  | space_id | Tablespace ID                                                |
+  | db_id    | Database ID                                                  |
+  | block_id | Extent ID                                                    |
+  | type     | Extent type. The options are as follows: **ALLOC_SEGMENT**, **DROP_SEGMENT**, and **SHRINK_EXTENT**. |
+
+  The values of **type** are described as follows:
+
+  - **ALLOC_SEGMENT**: When a user creates a segment-page table and the segment is just allocated but the transaction of creating a table is not committed, the node is faulty. As a result, the segment is not used after being allocated.
+
+  - **DROP_SEGMENT**: When a user deletes a segment-page table and the transaction is successfully committed, the bit corresponding to the segment page of the table is not reset and a fault, such as power failure, occurs. As a result, the segment is not used or released.
+
+  - **SHRINK_EXTENT**: When a user shrinks a segment-page table and does not release the idle extent, a fault, such as power failure, occurs. As a result, the extent remains and cannot be reused.
+
+    Example:
+
+    ```sql
+    select * from pg_stat_remain_segment_info();
+    space_id | db_id | block_id | type
+    ----------+-------+----------+------
+    1663       |   16385|        4156| ALLOC_SEGMENT
+    ```
+
+- pg_free_remain_segment(int4 spaceId, int4 dbId, int4 segmentId)
+
+  Description: Releases a specified residual extent. The value must be obtained from the **pg_stat_remain_segment_info** function. The function verifies input values. If the specified extent is not among the recorded residual extents, an error message is returned. If the specified extent is a single extent, the extent is released independently. If it is a segment, the segment and all extents in the segment are released.
+
+  Return value: empty
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/25-statistics-information-functions.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/25-statistics-information-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..29526885ce49ffda73410a3ffe20a1df69af2873
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/25-statistics-information-functions.md
@@ -0,0 +1,1777 @@
+---
+title: Statistics Information Functions
+summary: Statistics Information Functions
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Statistics Information Functions
+
+Statistics information functions are divided into the following two categories: functions that access databases, using the OID of each table or index in a database to mark the database for which statistics are generated; functions that access servers, identified by the server process ID, whose value ranges from 1 to the number of currently active servers.
+
+- global_comm_get_status()
+
+  Description: Obtains the communication library status of all DNs.
+
+  Return type: record
+
+- global_comm_get_send_stream()
+
+  Description: Obtains the sending stream status of all communication libraries on all DNs.
+
+  Return type: record
+
+- global_comm_get_recv_stream()
+
+  Description: Obtains the receiving stream status of all communication libraries on all DNs.
+
+  Return type: record
+
+- global_comm_get_client_info()
+
+  Description: Obtains information about client connections of global nodes.
+
+  Return type: record
+
+- pg_stat_get_db_conflict_tablespace(oid)
+
+  Description: Specifies the number of queries canceled due to a conflict between the restored tablespace and the deleted tablespace in the database.
+
+  Return type: bigint
+
+- pg_control_group_config
+
+  Description: Prints Cgroup configurations on the current node.
+
+  Return type: record
+
+- pg_stat_get_db_stat_reset_time(oid)
+
+  Description: Specifies the most recent time when database statistics were reset. It is initialized to the system time during the first connection to each database. The reset time is updated when you call **pg_stat_reset** on the database and execute **pg_stat_reset_single_table_counters** against any table or index in it.
+
+  Return type: timestamptz
+
+- pg_stat_get_function_total_time(oid)
+
+  Description: Specifies the total wall clock time spent in the function, in microseconds. The time spent on this function calling other functions is included.
+
+  Return type: bigint
+
+- pg_stat_get_xact_tuples_returned(oid)
+
+  Description: Specifies the number of rows read through sequential scans when the parameter is a table in the current transaction or the number of index entries returned when the parameter is an index.
+
+  Return type: bigint
+
+- pg_lock_status()
+
+  Description: Queries information about locks held by open transactions. All users can execute this function.
+
+  Return type: For details, see **PG_LOCKS** which is obtained by querying this function.
+
+- pg_stat_get_xact_numscans(oid)
+
+  Description: Specifies the number of sequential scans performed when the parameter is a table in the current transaction or the number of index scans performed when the parameter is an index.
+
+  Return type: bigint
+
+- pg_stat_get_xact_blocks_fetched(oid)
+
+  Description: Specifies the number of disk block fetch requests for a table or an index in the current transaction.
+
+  Return type: bigint
+
+- pg_stat_get_xact_blocks_hit(oid)
+
+  Description: Specifies the number of disk block fetch requests for tables or indexes found in cache in the current transaction.
+
+  Return type: bigint
+
+- pg_stat_get_xact_function_calls(oid)
+
+  Description: Specifies the number of times the function is called in the current transaction.
+
+  Return type: bigint
+
+- pg_stat_get_xact_function_self_time(oid)
+
+  Description: Specifies the time spent on this function in the current transaction, excluding the time spent on this function internally calling other functions.
+
+  Return type: bigint
+
+- pg_stat_get_xact_function_total_time(oid)
+
+  Description: Specifies the total wall clock time (in microseconds) spent on the function in the current transaction, including the time spent on this function internally calling other functions.
+
+  Return type: bigint
+
+- pg_stat_get_wal_senders()
+
+  Description: Queries walsender information on the primary server.
+
+  Return type: setofrecord
+
+  The following table describes return columns.
+
+  **Table 1** Return column description
+
+  | Column                     | Type                     | Description                             |
+  | :------------------------- | :----------------------- | :-------------------------------------- |
+  | pid                        | bigint                   | Thread ID of the WAL sender             |
+  | sender_pid                 | integer                  | Lightweight thread ID of the WAL sender |
+  | local_role                 | text                     | Type of the primary node                |
+  | peer_role                  | text                     | Type of the standby node                |
+  | peer_state                 | text                     | Status of the standby node              |
+  | state                      | text                     | Status of the WAL sender                |
+  | catchup_start              | timestamp with time zone | Startup time of a catchup task          |
+  | catchup_end                | timestamp with time zone | End time of a catchup task              |
+  | sender_sent_location       | text                     | Sending position of the primary node    |
+  | sender_write_location      | text                     | Writing position of the primary node    |
+  | sender_flush_location      | text                     | Flushing position of the primary node   |
+  | sender_replay_location     | text                     | Redo position of the primary node       |
+  | receiver_received_location | text                     | Receiving position of the standby node  |
+  | receiver_write_location    | text                     | Writing position of the standby node    |
+  | receiver_flush_location    | text                     | Flushing position of the standby node   |
+  | receiver_replay_location   | text                     | Redo position of the standby node       |
+  | sync_percent               | text                     | Synchronization percentage              |
+  | sync_state                 | text                     | Synchronization status                  |
+  | sync_priority              | text                     | Priority of synchronous replication     |
+  | sync_most_available        | text                     | Maximum availability mode               |
+  | channel                    | text                     | Channel information of the WAL sender   |
+
+- get_paxos_replication_info()
+
+  Description: Queries the primary/standby replication status in Paxos mode.
+
+  Return type: setofrecord
+
+  The following table describes return columns.
+
+  **Table 2** Return column description
+
+  | Column                | Type | Description                                                  |
+  | :-------------------- | :--- | :----------------------------------------------------------- |
+  | paxos_write_location  | text | Location of the Xlog that has been written to the Distribute Consensus Framework (DCF) |
+  | paxos_commit_location | text | Location of the Xlog agreed in the DCF                       |
+  | local_write_location  | text | Writing position of a node                                   |
+  | local_flush_location  | text | Flushing position of a node                                  |
+  | local_replay_location | text | Redo position of a node                                      |
+  | dcf_replication_info  | text | DCF module information of a node                             |
+
+- pg_stat_get_stream_replications()
+
+  Description: Queries the primary/standby replication status.
+
+  Return type: setofrecord
+
+  The following table describes return values.
+
+  **Table 3** Return value description
+
+  | Return Parameter   | Type    | Description           |
+  | :----------------- | :------ | :-------------------- |
+  | local_role         | text    | Local role            |
+  | static_connections | integer | Connection statistics |
+  | db_state           | text    | Database status       |
+  | detail_information | text    | Detailed information  |
+
+- pg_stat_get_db_numbackends(oid)
+
+  Description: Specifies the number of active server processes for a database.
+
+  Return type: integer
+
+- pg_stat_get_db_xact_commit(oid)
+
+  Description: Specifies the number of transactions committed in a database.
+
+  Return type: bigint
+
+- pg_stat_get_db_xact_rollback(oid)
+
+  Description: Specifies the number of transactions rolled back in a database.
+
+  Return type: bigint
+
+- pg_stat_get_db_blocks_fetched(oid)
+
+  Description: Specifies the number of disk blocks fetch requests for a database.
+
+  Return type: bigint
+
+- pg_stat_get_db_blocks_hit(oid)
+
+  Description: Specifies the number of disk block fetch requests found in cache for a database.
+
+  Return type: bigint
+
+- pg_stat_get_db_tuples_returned(oid)
+
+  Description: Specifies the number of tuples returned for a database.
+
+  Return type: bigint
+
+- pg_stat_get_db_tuples_fetched(oid)
+
+  Description: Specifies the number of tuples fetched for a database.
+
+  Return type: bigint
+
+- pg_stat_get_db_tuples_inserted(oid)
+
+  Description: Specifies the number of tuples inserted in a database.
+
+  Return type: bigint
+
+- pg_stat_get_db_tuples_updated(oid)
+
+  Description: Specifies the number of tuples updated in a database.
+
+  Return type: bigint
+
+- pg_stat_get_db_tuples_deleted(oid)
+
+  Description: Specifies the number of tuples deleted in a database.
+
+  Return type: bigint
+
+- pg_stat_get_db_conflict_lock(oid)
+
+  Description: Specifies the number of lock conflicts in a database.
+
+  Return type: bigint
+
+- pg_stat_get_db_deadlocks(oid)
+
+  Description: Specifies the number of deadlocks in a database.
+
+  Return type: bigint
+
+- pg_stat_get_numscans(oid)
+
+  Description: Specifies the number of sequential row scans done if parameters are in a table or the number of index scans done if parameters are in an index.
+
+  Return type: bigint
+
+- pg_stat_get_role_name(oid)
+
+  Description: Obtains the username based on the user OID. Only users with the **sysadmin** or **monitor admin** permission can access the information.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# select pg_stat_get_role_name(10);
+   pg_stat_get_role_name
+  -----------------------
+   aabbcc
+  (1 row)
+  ```
+
+- pg_stat_get_tuples_returned(oid)
+
+  Description: Specifies the number of sequential row scans done if parameters are in a table or the number of index scans done if parameters are in an index.
+
+  Return type: bigint
+
+- pg_stat_get_tuples_fetched(oid)
+
+  Description: Specifies the number of table rows fetched by bitmap scans if parameters are in a table or the number of table rows fetched by simple index scans using the index if parameters are in an index.
+
+  Return type: bigint
+
+- pg_stat_get_tuples_inserted(oid)
+
+  Description: Specifies the number of rows inserted into a table.
+
+  Return type: bigint
+
+- pg_stat_get_tuples_updated(oid)
+
+  Description: Specifies the number of rows updated in a table.
+
+  Return type: bigint
+
+- pg_stat_get_tuples_deleted(oid)
+
+  Description: Specifies the number of rows deleted from a table.
+
+  Return type: bigint
+
+- pg_stat_get_tuples_changed(oid)
+
+  Description: Specifies the total number of inserted, updated, and deleted rows after a table was last analyzed or autoanalyzed.
+
+  Return type: bigint
+
+- pg_stat_get_tuples_hot_updated(oid)
+
+  Description: Specifies the number of rows hot updated in a table.
+
+  Return type: bigint
+
+- pg_stat_get_live_tuples(oid)
+
+  Description: Specifies the number of live rows in a table.
+
+  Return type: bigint
+
+- pg_stat_get_dead_tuples(oid)
+
+  Description: Specifies the number of dead rows in a table.
+
+  Return type: bigint
+
+- pg_stat_get_blocks_fetched(oid)
+
+  Description: Specifies the number of disk block fetch requests for a table or an index.
+
+  Return type: bigint
+
+- pg_stat_get_blocks_hit(oid)
+
+  Description: Specifies the number of disk block requests found in cache for a table or an index.
+
+  Return type: bigint
+
+- pg_stat_get_partition_tuples_inserted(oid)
+
+  Description: Specifies the number of rows in the corresponding table partition.
+
+  Return type: bigint
+
+- pg_stat_get_partition_tuples_updated(oid)
+
+  Description: Specifies the number of rows that have been updated in the corresponding table partition.
+
+  Return type: bigint
+
+- pg_stat_get_partition_tuples_deleted(oid)
+
+  Description: Specifies the number of rows deleted from the corresponding table partition.
+
+  Return type: bigint
+
+- pg_stat_get_partition_tuples_changed(oid)
+
+  Description: Specifies the total number of inserted, updated, and deleted rows after a table partition was last analyzed or autoanalyzed.
+
+  Return type: bigint
+
+- pg_stat_get_partition_live_tuples(oid)
+
+  Description: Specifies the number of live rows in a partitioned table.
+
+  Return type: bigint
+
+- pg_stat_get_partition_dead_tuples(oid)
+
+  Description: Specifies the number of dead rows in a partitioned table.
+
+  Return type: bigint
+
+- pg_stat_get_xact_tuples_fetched(oid)
+
+  Description: Specifies the number of tuple rows scanned in a transaction.
+
+  Return type: bigint
+
+- pg_stat_get_xact_tuples_inserted(oid)
+
+  Description: Specifies the number of tuple inserted into the active subtransactions related to a table.
+
+  Return type: bigint
+
+- pg_stat_get_xact_tuples_deleted(oid)
+
+  Description: Specifies the number of deleted tuples in the active subtransactions related to a table.
+
+  Return type: bigint
+
+- pg_stat_get_xact_tuples_hot_updated(oid)
+
+  Description: Specifies the number of hot updated tuples in the active subtransactions related to a table.
+
+  Return type: bigint
+
+- pg_stat_get_xact_tuples_updated(oid)
+
+  Description: Specifies the number of updated tuples in the active subtransactions related to a table.
+
+  Return type: bigint
+
+- pg_stat_get_xact_partition_tuples_inserted(oid)
+
+  Description: Specifies the number of inserted tuples in the active subtransactions related to a table partition.
+
+  Return type: bigint
+
+- pg_stat_get_xact_partition_tuples_deleted(oid)
+
+  Description: Specifies the number of deleted tuples in the active subtransactions related to a table partition.
+
+  Return type: bigint
+
+- pg_stat_get_xact_partition_tuples_hot_updated(oid)
+
+  Description: Specifies the number of hot updated tuples in the active subtransactions related to a table partition.
+
+  Return type: bigint
+
+- pg_stat_get_xact_partition_tuples_updated(oid)
+
+  Description: Specifies the number of updated tuples in the active subtransactions related to a table partition.
+
+  Return type: bigint
+
+- pg_stat_get_last_vacuum_time(oid)
+
+  Description: Specifies the most recent time when the autovacuum thread is manually started to clear a table.
+
+  Return type: timestamptz
+
+- pg_stat_get_last_autovacuum_time(oid)
+
+  Description: Specifies the time of the last vacuum initiated by the autovacuum daemon on a table.
+
+  Return type: timestamptz
+
+- pg_stat_get_vacuum_count(oid)
+
+  Description: Specifies the number of times a table is manually cleared.
+
+  Return type: bigint
+
+- pg_stat_get_autovacuum_count(oid)
+
+  Description: Specifies the number of times the autovacuum daemon is started to clear a table.
+
+  Return type: bigint
+
+- pg_stat_get_last_analyze_time(oid)
+
+  Description: Specifies the last time when a table starts to be analyzed manually or by the autovacuum thread.
+
+  Return type: timestamptz
+
+- pg_stat_get_last_autoanalyze_time(oid)
+
+  Description: Specifies the time when the last analysis initiated by the autovacuum daemon on a table.
+
+  Return type: timestamptz
+
+- pg_stat_get_analyze_count(oid)
+
+  Description: Specifies the number of times a table is manually analyzed.
+
+  Return type: bigint
+
+- pg_stat_get_autoanalyze_count(oid)
+
+  Description: Specifies the number of times the autovacuum daemon analyzes a table.
+
+  Return type: bigint
+
+- pg_total_autovac_tuples(bool,bool)
+
+  Description: Returns tuple records related to the total autovac, such as **nodename**, **nspname**, **relname**, and tuple IUDs. The input parameters specify whether to query **relation** and **local** information, respectively.
+
+  Return type: setofrecord
+
+  The following table describes return parameters.
+
+  **Table 4** Return parameter description
+
+  | Return Parameter      | Type   | Description                                             |
+  | :-------------------- | :----- | :------------------------------------------------------ |
+  | nodename              | name   | Node name                                               |
+  | nspname               | name   | Name of a namespace                                     |
+  | relname               | name   | Name of an object, such as a table, an index, or a view |
+  | partname              | name   | Partition name                                          |
+  | n_dead_tuples         | bigint | Number of dead rows in a table partition                |
+  | n_live_tuples         | bigint | Number of live rows in a table partition                |
+  | changes_since_analyze | bigint | Number of changes generated by ANALYZE                  |
+
+- pg_autovac_status(oid)
+
+  Description: Returns autovac information, such as **nodename**, **nspname**, **relname**, **analyze**, **vacuum**, thresholds of **analyze** and **vacuum**, and the number of analyzed or vacuumed tuples. Only users with the **sysadmin** permission can use this function.
+
+  Return type: setofrecord
+
+  The following table describes return parameters.
+
+  **Table 5** Return parameter description
+
+  | Return Parameter | Type    | Description                                             |
+  | :--------------- | :------ | :------------------------------------------------------ |
+  | nspname          | text    | Name of a namespace                                     |
+  | relname          | text    | Name of an object, such as a table, an index, or a view |
+  | nodename         | text    | Node name                                               |
+  | doanalyze        | Boolean | Whether to execute **ANALYZE**                          |
+  | anltuples        | bigint  | Number of ANALYZE tuples                                |
+  | anlthresh        | bigint  | ANALYZE threshold                                       |
+  | dovacuum         | Boolean | Whether to execute **VACUUM**                           |
+  | vactuples        | bigint  | Number of VACUUM tuples                                 |
+  | vacthresh        | bigint  | VACUUM threshold                                        |
+
+- pg_autovac_timeout(oid)
+
+  Description: Returns the number of consecutive timeouts during the autovac operation on a table. If the table information is invalid or the node information is abnormal, **NULL** will be returned.
+
+  Return type: bigint
+
+- pg_stat_get_last_data_changed_time(oid)
+
+  Description: Returns the time when **INSERT**, **UPDATE**, **DELETE**, or **EXCHANGE**/**TRUNCATE**/**DROP** **PARTITION** was last performed on a table. The data in the **last_data_changed** column of the PG_STAT_ALL_TABLES view is calculated by using this function. The performance of obtaining the last modification time by using the view is poor when the table has a large amount of data. In this case, you are advised to use the function.
+
+  Return type: timestamptz
+
+- pg_stat_set_last_data_changed_time(oid)
+
+  Description: Manually changes the time when **INSERT**, **UPDATE**, **DELETE**, or **EXCHANGE**/**TRUNCATE**/**DROP** **PARTITION** was last performed.
+
+  Return type: void
+
+- pg_backend_pid()
+
+  Description: Specifies the thread ID of the server thread attached to the current session.
+
+  Return type: integer
+
+- pg_stat_get_activity(integer)
+
+  Description: Returns a record about the backend with the specified PID. A record for each active backend in the system is returned if **NULL** is specified. The return results are a subnet of those (excluding the **connection_info** column) in the PG_STAT_ACTIVITY view.
+
+  Example:
+
+  ```sql
+  mogdb=# select * from pg_stat_get_activity(139754904483584);
+   datid |       pid       |    sessionid    | usesysid | application_name | state |                    query                     | waiting | xact_start |          query_start          |         backend_start         |         state_cha
+  nge          | client_addr | client_hostname | client_port | enqueue | query_id | srespool | global_sessionid
+  -------+-----------------+-----------------+----------+------------------+-------+----------------------------------------------+---------+------------+-------------------------------+-------------------------------+------------------
+  -------------+-------------+-----------------+-------------+---------+----------+----------+------------------
+   16099 | 139754904483584 | 139754904483584 |       10 | coordinator2     | idle  | SET SESSION AUTHORIZATION DEFAULT;RESET ALL; | f       |            | 2021-06-09 16:40:58.391727+08 | 2021-06-09 16:03:52.040929+08 | 2021-06-09 16:40:
+  58.392143+08 | ::1         |                 |       35210 |         |        0 | unknown  | 0#0#0
+  (1 row)
+  ```
+
+  Return type: setofrecord
+
+  The following table describes return parameters.
+
+  **Table 6** Return parameter description
+
+  | Return Parameter | Type                     | Description                                                  |
+  | :--------------- | :----------------------- | :----------------------------------------------------------- |
+  | datid            | oid                      | OID of the database that the user session connects to in the backend |
+  | pid              | bigint                   | Backend thread ID                                            |
+  | sessionid        | bigint                   | Session ID                                                   |
+  | usesysid         | oid                      | Name of the user logged in to the backend                    |
+  | application_name | text                     | Name of the application connected to the backend             |
+  | state            | text                     | Overall status of the backend                                |
+  | query            | text                     | Latest query at the backend. If **state** is **active**, this column shows the ongoing query. In all other states, it shows the last query that was executed. |
+  | waiting          | Boolean                  | Whether the backend is currently waiting on a lock. If yes, the value is **true**. |
+  | xact_start       | timestamp with time zone | Time when current transaction was started (null if no transaction is active). If the current query is the first of its transaction, the value of this column is the same as that of the **query_start** column. |
+  | query_start      | timestamp with time zone | Time when the currently active query was started, or time when the last query was started if **state** is not **active** |
+  | backend_start    | timestamp with time zone | Time when this process was started, that is, when the client connected to the server |
+  | state_change     | timestamp with time zone | Time when **state** was last modified                        |
+  | client_addr      | inet                     | IP address of the client connected to the backend. If this column is **NULL**, it indicates either the client is connected via a Unix socket on the server or this is an internal process, such as **AUTOVACUUM**. |
+  | client_hostname  | text                     | Host name of the connected client, as reported by a reverse DNS lookup of **client\_addr**. This column will be non-null only for IP connections and only when**log_hostname** is enabled. |
+  | client_port      | integer                  | TCP port number that the client uses for communication with this backend (**-1** if a Unix socket is used). |
+  | enqueue          | text                     | Unsupported currently                                        |
+  | query_id         | bigint                   | ID of a query                                                |
+  | global_sessionid | text                     | Global session ID                                            |
+
+- pg_stat_get_activity_with_conninfo(integer)
+
+  Description: Returns a record about the backend with the specified PID. A record for each active backend in the system is returned if **NULL** is specified. PG_STAT_ACTIVITY is a subset of the function.
+
+  Return type: setofrecord
+
+  The following table describes return values.
+
+  **Table 7** Return value description
+
+  | Return Value     | Return Type              | Description                                                  |
+  | :--------------- | :----------------------- | :----------------------------------------------------------- |
+  | datid            | oid                      | OID of the database that the user session connects to in the backend |
+  | pid              | bigint                   | Backend thread ID                                            |
+  | sessionid        | bigint                   | Session ID                                                   |
+  | usesysid         | oid                      | Name of the user logged in to the backend                    |
+  | application_name | text                     | Name of the application connected to the backend             |
+  | state            | text                     | Overall status of the backend                                |
+  | query            | text                     | Latest query at the backend. If **state** is **active**, this column shows the ongoing query. In all other states, it shows the last query that was executed. |
+  | waiting          | Boolean                  | Whether the backend is currently waiting on a lock. If yes, the value is **true** |
+  | xact_start       | timestamp with time zone | Time when current transaction was started (null if no transaction is active). If the current query is the first of its transaction, the value of this column is the same as that of the **query_start** column. |
+  | query_start      | timestamp with time zone | Time when the currently active query was started, or time when the last query was started if **state** is not **active** |
+  | backend_start    | timestamp with time zone | Time when this process was started, that is, when the client connected to the server |
+  | state_change     | timestamp with time zone | Time when **state** was last modified                        |
+  | client_addr      | inet                     | IP address of the client connected to the backend If this column is **NULL**, it indicates either the client is connected via a Unix socket on the server or this is an internal process, such as **AUTOVACUUM**. |
+  | client_hostname  | text                     | Host name of the connected client, as reported by a reverse DNS lookup of **client\_addr**. This column will be non-null only for IP connections and only when**log_hostname** is enabled. |
+  | client_port      | integer                  | TCP port number that the client uses for communication with this backend (**-1** if a Unix socket is used) |
+  | enqueue          | text                     | Unsupported currently                                        |
+  | query_id         | bigint                   | ID of a query                                                |
+  | connection_info  | text                     | A string in JSON format recording the driver type, driver version, driver deployment path, and process owner of the connected database |
+  | global_sessionid | text                     | Global session ID                                            |
+
+- pg_user_iostat(text)
+
+  Description: Displays the I/O load management information about the job currently executed by the user.
+
+  Return type: record
+
+  The following table describes return fields.
+
+  | Name           | Type | Description                                                  |
+  | :------------- | :--- | :----------------------------------------------------------- |
+  | userid         | oid  | User ID                                                      |
+  | min_curr_iops  | int4 | Minimum I/O of the current user across database nodes. The IOPS is counted by ones for column storage and by ten thousands for row storage. |
+  | max_curr_iops  | int4 | Maximum I/O of the current user across database nodes. The IOPS is counted by ones for column storage and by ten thousands for row storage. |
+  | min_peak_iops  | int4 | Minimum peak I/O of the current user across database nodes. The IOPS is counted by ones for column storage and by ten thousands for row storage. |
+  | max_peak_iops  | int4 | Maximum peak I/O of the current user across database nodes. The IOPS is counted by ones for column storage and by ten thousands for row storage. |
+  | io_limits      | int4 | **io_limits** set for the resource pool specified by the user. The IOPS is counted by ones for column storage and by ten thousands for row storage. |
+  | io_priority    | text | **io_priority** set for the user. The IOPS is counted by ones for column storage and by ten thousands for row storage. |
+  | curr_io_limits | int4 | Real-time **io_limits** value when **io_priority** is used to control I/Os |
+
+- pg_stat_get_function_calls(oid)
+
+  Description: Specifies the number of times the function has been called.
+
+  Return type: bigint
+
+- pg_stat_get_function_self_time(oid)
+
+  Description: Specifies the time spent in only this function. The time spent on this function calling other functions is excluded.
+
+  Return type: bigint
+
+- pg_stat_get_backend_idset()
+
+  Description: Sets the number of currently active server processes (from 1 to the number of active server processes).
+
+  Return type: setofinteger
+
+- pg_stat_get_backend_pid(integer)
+
+  Description: Specifies the ID of the given server thread.
+
+  Return type: bigint
+
+- pg_stat_get_backend_dbid(integer)
+
+  Description: Specifies the ID of the database connected to the given server process.
+
+  Return type: oid
+
+- pg_stat_get_backend_userid(integer)
+
+  Description: Specifies the user ID of the given server process.
+
+  Return type: oid
+
+- pg_stat_get_backend_activity(integer)
+
+  Description: Active command of the given server process, but only if the current user is a system administrator or the same user as that of the session being queried and **track_activities** is on
+
+  Return type: text
+
+- pg_stat_get_backend_waiting(integer)
+
+  Description: True if the given server process is waiting for a lock, but only if the current user is a system administrator or the same user as that of the session being queried and **track_activities** is on
+
+  Return type: Boolean
+
+- pg_stat_get_backend_activity_start(integer)
+
+  Description: Specifies the time when the given server process's currently executing query is started only if the current user is the system administrator or the user of the session being queried and **track_activities** is enabled.
+
+  Return type: timestamp with time zone
+
+- pg_stat_get_backend_xact_start(integer)
+
+  Description: Specifies the time when the given server process's currently executing transaction is started only if the current user is the system administrator or the user of the session being queried and **track_activities** is enabled.
+
+  Return type: timestamp with time zone
+
+- pg_stat_get_backend_start(integer)
+
+  Description: Specifies the time when the given server process is started. If the current user is neither the system administrator nor the user of the session being queried, NULL is **returned**.
+
+  Return type: timestamp with time zone
+
+- pg_stat_get_backend_client_addr(integer)
+
+  Description: Specifies the IP address of the client connected to the given server process. If the connection is over a Unix domain socket, or if the current user is neither a system administrator nor the same user as that of the session being queried, **NULL** will be returned.
+
+  Return type: inet
+
+- pg_stat_get_backend_client_port(integer)
+
+  Description: Specifies the TCP port number of the client connected to the given server process. If the connection is over a Unix domain socket, **-1** will be returned. If the current user is neither a system administrator nor the same user as that of the session being queried, **NULL** will be returned.
+
+  Return type: integer
+
+- pg_stat_get_bgwriter_timed_checkpoints()
+
+  Description: Specifies the time when the background writer starts scheduled checkpoints (because the **checkpoint_timeout** time has expired).
+
+  Return type: bigint
+
+- pg_stat_get_bgwriter_requested_checkpoints()
+
+  Description: Specifies the time when the background writer starts checkpoints based on requests from the backend because **checkpoint_segments** has been exceeded or the **CHECKPOINT** command has been executed.
+
+  Return type: bigint
+
+- pg_stat_get_bgwriter_buf_written_checkpoints()
+
+  Description: Specifies the number of buffers written by the background writer during checkpoints.
+
+  Return type: bigint
+
+- pg_stat_get_bgwriter_buf_written_clean()
+
+  Description: Specifies the number of buffers written by the background writer for routine cleaning of dirty pages.
+
+  Return type: bigint
+
+- pg_stat_get_bgwriter_maxwritten_clean()
+
+  Description: Specifies the time when the background writer stops its cleaning scan because it has written more buffers than specified in the **bgwriter_lru_maxpages** parameter.
+
+  Return type: bigint
+
+- pg_stat_get_buf_written_backend()
+
+  Description: Specifies the number of buffers written by the backend because they need to allocate a new buffer.
+
+  Return type: bigint
+
+- pg_stat_get_buf_alloc()
+
+  Description: Specifies the total number of the allocated buffers.
+
+  Return type: bigint
+
+- pg_stat_clear_snapshot()
+
+  Description: Discards the current statistics snapshot.
+
+  Return type: void
+
+- pg_stat_reset()
+
+  Description: Resets all statistics counters for the current database to zero (requires system administrator permissions).
+
+  Return type: void
+
+- pg_stat_reset_shared(text)
+
+  Description: Resets all statistics counters for the current database in each node in a shared cluster to zero (requires system administrator permissions).
+
+  Return type: void
+
+- pg_stat_reset_single_table_counters(oid)
+
+  Description: Resets statistics for a single table or index in the current database to zero (requires system administrator permissions).
+
+  Return type: void
+
+- pg_stat_reset_single_function_counters(oid)
+
+  Description: Resets statistics for a single function in the current database to zero (requires system administrator permissions).
+
+  Return type: void
+
+- pg_stat_session_cu(int, int, int)
+
+  Description: Obtains the compression unit (CU) hit statistics of sessions running on the current node.
+
+  Return type: record
+
+- pg_stat_get_cu_mem_hit(oid)
+
+  Description: Obtains the number of CU memory hits of a column storage table in the current database of the current node.
+
+  Return type: bigint
+
+- pg_stat_get_cu_hdd_sync(oid)
+
+  Description: Obtains the times CU is synchronously read from a disk by a column storage table in the current database of the current node.
+
+  Return type: bigint
+
+- pg_stat_get_cu_hdd_asyn(oid)
+
+  Description: Obtains the times CU is asynchronously read from a disk by a column storage table in the current database of the current node.
+
+  Return type: bigint
+
+- pg_stat_get_db_cu_mem_hit(oid)
+
+  Description: Obtains the CU memory hit in a database of the current node.
+
+  Return type: bigint
+
+- pg_stat_get_db_cu_hdd_sync(oid)
+
+  Description: Obtains the times CU is synchronously read from a disk by a database of the current node.
+
+  Return type: bigint
+
+- fenced_udf_process()
+
+  Description: Shows the number of local UDF Master and Work processes.
+
+  Return type: record
+
+- total_cpu()
+
+  Description: Obtains the CPU time used by the current node, in jiffies.
+
+  Return type: bigint
+
+- mot_global_memory_detail()
+
+  Description: Checks the size of the MOT global memory, including data and indexes.
+
+  Return type: record
+
+- mot_local_memory_detail()
+
+  Description: Checks the size of the MOT local memory, including data and indexes.
+
+  Return type: record
+
+- mot_session_memory_detail()
+
+  Description: Checks the MOT memory usage of all sessions.
+
+  Return type: record
+
+- total_memory()
+
+  Description: Obtains the size of the virtual memory used by the current node, in KB.
+
+  Return type: bigint
+
+- pg_stat_get_db_cu_hdd_asyn(oid)
+
+  Description: Obtains the times CU is asynchronously read from a disk by a database of the current node.
+
+  Return type: bigint
+
+- pg_stat_bad_block(text, int, int, int, int, int, timestamp with time zone, timestamp with time zone)
+
+  Description: Obtains damage information about pages or CUs after the current node is started.
+
+  Example: select * from pg_stat_bad_block();
+
+  Return type: record
+
+- pg_stat_bad_block_clear()
+
+  Description: Deletes the page and CU damage information that is read and recorded on the node (requires system administrator permissions).
+
+  Return type: void
+
+- gs_respool_exception_info(pool text)
+
+  Description: Queries the query rule of a specified resource pool.
+
+  Return type: record
+
+- gs_control_group_info(pool text)
+
+  Description: Queries information about Cgroups associated with a resource pool.
+
+  Return type: record
+
+  The command output is as follows:
+
+  | Attribute | Value               | Description                                             |
+  | :-------- | :------------------ | :------------------------------------------------------ |
+  | name      | class_a:workload_a1 | Class name and workload name                            |
+  | class     | class_a             | Class Cgroup name                                       |
+  | workload  | workload_a1         | Workload Cgroup name                                    |
+  | type      | DEFWD               | Cgroup type (Top, CLASS, BAKWD, DEFWD, and TSWD)        |
+  | gid       | 87                  | Cgroup ID                                               |
+  | shares    | 30                  | Percentage of CPU resources to those on the parent node |
+  | limits    | 0                   | Percentage of CPU cores to those on the parent node     |
+  | rate      | 0                   | Allocation ratio in Timeshare                           |
+  | cpucores  | 0-3                 | Number of CPU cores                                     |
+
+- gs_all_control_group_info()
+
+  Description: Collects information about all Cgroups in the database.
+
+  Return type: record
+
+- gs_get_control_group_info()
+
+  Description: Collects information about all Cgroups.
+
+  Return type: record
+
+- get_instr_workload_info(integer)
+
+  Description: Obtains the transaction volume and time information on the primary database node.
+
+  Return type: record
+
+  | Attribute           | Value        | Description                                                  |
+  | :------------------ | :----------- | :----------------------------------------------------------- |
+  | resourcepool_oid    | 10           | OID of the resource pool (the logic is equivalent to the load) |
+  | commit_counter      | 4            | Number of frontend transactions that were committed          |
+  | rollback_counter    | 1            | Number of frontend transactions that were rolled back        |
+  | resp_min            | 949          | Minimum response time of frontend transactions (unit: μs)    |
+  | resp_max            | 201891       | Maximum response time of frontend transactions (unit: μs)    |
+  | resp_avg            | 43564        | Average response time of frontend transactions (unit: μs)    |
+  | resp_total          | 217822       | Total response time of frontend transactions (unit: μs)      |
+  | bg_commit_counter   | 910          | Number of backend transactions that were committed           |
+  | bg_rollback_counter | 0            | Number of backend transactions that were rolled back         |
+  | bg_resp_min         | 97           | Minimum response time of backend transactions (unit: μs)     |
+  | bg_resp_max         | 678080687    | Maximum response time of backend transactions (unit: μs)     |
+  | bg_resp_avg         | 327847884    | Average response time of backend transactions (unit: μs)     |
+  | bg_resp_total       | 298341575300 | Total response time of backend transactions (unit: μs)       |
+
+- pv_instance_time()
+
+  Description: Obtains the time consumed in each execution phase on the current node.
+
+  Return type: record
+
+  | Stat_name Attribute | Value   | Description                                                  |
+  | :------------------ | :------ | :----------------------------------------------------------- |
+  | DB_TIME             | 1062385 | Total end-to-end wall time consumed by all threads (unit: μs) |
+  | CPU_TIME            | 311777  | Total CPU time consumed by all threads (unit: μs)            |
+  | EXECUTION_TIME      | 380037  | Total time consumed on the executor (unit: μs)               |
+  | PARSE_TIME          | 6033    | Total time consumed for parsing SQL statements (unit: μs)    |
+  | PLAN_TIME           | 173356  | Total time consumed for generating an execution plan (unit: μs) |
+  | REWRITE_TIME        | 2274    | Total time consumed on query rewriting (unit: μs)            |
+  | PL_EXECUTION_TIME   | 0       | Total time consumed for executing PL/SQL statements (unit: μs) |
+  | PL_COMPILATION_TIME | 557     | Total time consumed for SQL compilation (unit: μs)           |
+  | NET_SEND_TIME       | 1673    | Total time consumed for sending data over network (unit: μs) |
+  | DATA_IO_TIME        | 426622  | Total time consumed for data read and write (unit: μs)       |
+
+- DBE_PERF.get_global_instance_time()
+
+  Description: Provides the time consumed in each key phase in MogDB. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- get_instr_unique_sql()
+
+  Description: Obtains information about execution statements (normalized SQL statements) on the current node as a user with the **sysadmin** permission.
+
+  Return type: record
+
+- reset_unique_sql(text, text, bigint)
+
+  Description: Resets information about system execution statements (normalized SQL statements) information as a user with the **sysadmin** permission. The value of the first parameter can be **global** or **local**. **global** indicates that information on all nodes is cleared, and **local** indicates that only information on the current node is cleared. The value of the second parameter can be **ALL**, **BY_USERID**, or **BY_CNID**. **ALL** indicates that all information is cleared. **BY_USERID** indicates that the SQL information of the user specified by **USERID** is cleared. **BY_CNID** indicates that the SQL information related to the primary node of the database in the system is cleared. The third parameter indicates **CNID** and **USERID**. If the second parameter is set to **ALL**, the third parameter does not take effect and can be set to any value.
+
+  Return type: Boolean
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** This function involves distributed nodes. Currently, MogDB is a centralized database, for which the function of the value **global** is the same as that of the value **local** and the second parameter cannot set to be **BY_CNID**.
+
+- get_instr_wait_event(NULL)
+
+  Description: Obtains the statistics on wait events of the current node.
+
+  Return type: record
+
+- get_instr_user_login()
+
+  Description: Obtains the number of user login and logout times on the current node. Only users with the **sysadmin** or **monitor admin** permission can execute this function.
+
+  Return type: record
+
+- get_instr_rt_percentile(integer)
+
+  Description: Obtains the SQL response time P80 and P95 distribution information of the database.
+
+  Return type: record
+
+- get_node_stat_reset_time()
+
+  Description: Obtains statistics about reset (restart, primary/standby switchover, and database deletion) time of the current node.
+
+  Return type: record
+
+- DBE_PERF.get_global_os_runtime()
+
+  Description: Displays the running status of the current operating system. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_os_threads()
+
+  Description: Provides information about the threads under all normal nodes of MogDB. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_summary_workload_sql_count()
+
+  Description: Provides statistics about the number of SELECT, UPDATE, INSERT, DELETE, DDL, DML, and DCL statements of different service loads in MogDB. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_summary_workload_sql_elapse_time()
+
+  Description: Provides statistics about the number of SELECT, UPDATE, INSERT, and DELETE statements and response time information (TOTAL, AVG, MIN, and MAX) for different loads in MogDB. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_workload_transaction()
+
+  Description: Obtains the transaction volume and time information on all nodes of MogDB. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_session_stat()
+
+  Description: Obtains the session status information on all nodes of MogDB. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The status information contains the following 17 items: **commit**, **rollback**, **sql**, **table_scan**, **blocks_fetched**, **physical_read_operation**, **shared_blocks_dirtied**, **local_blocks_dirtied**, **shared_blocks_read**, **local_blocks_read**, **blocks_read_time**, **blocks_write_time, sort_imemory**, **sort_idisk**, **cu_mem_hit**, **cu_hdd_sync_read**, and **cu_hdd_asyread**.
+
+- DBE_PERF.get_global_session_time()
+
+  Description: Provides the time consumed in each key phase of each node in MogDB. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_session_memory()
+
+  Description: Displays statistics about memory usage at the session level on each node in the unit of MB, including all the memory allocated to Postgres and stream threads on DNs for jobs currently executed by users. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_session_memory_detail()
+
+  Description: Displays statistics about thread memory usage on each node by MemoryContext node. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- create_wlm_session_info(int flag)
+
+  Description: Clears top SQL query statement-level statistics recorded in the current memory. Only the administrator can execute this function.
+
+  Return type: int
+
+- pg_stat_get_wlm_session_info(int flag)
+
+  Description: Obtains top SQL query statement-level statistics recorded in the current memory. If the input parameter is not 0, the information is cleared from the memory. Only users with the **system admin** or **monitor admin** permission can execute this function.
+
+  Return type: record
+
+- gs_paxos_stat_replication()
+
+  Description: Queries the standby server information on the primary server. Currently, only the centralized DCF mode is supported.
+
+  Return type: setofrecord
+
+  The following table describes return columns.
+
+  | Column                   | Type | Description                                                  |
+  | ------------------------ | ---- | ------------------------------------------------------------ |
+  | local_role               | text | Role of the node that sends logs                             |
+  | peer_role                | text | Role of the node that receives logs                          |
+  | local_dcf_role           | text | DCF role of the node that sends logs                         |
+  | peer_dcf_role            | text | DCF role of the node that receives logs                      |
+  | peer_state               | text | Status of the node that receives logs                        |
+  | sender_write_location    | text | Location in the Xlog buffer where the node that sends logs is written |
+  | sender_commit_location   | text | Consistency point reached for the DCF logs of the node that sends logs |
+  | sender_flush_location    | text | Location in the Xlog disk where the node that sends logs is written |
+  | sender_replay_location   | text | Location where the node that sends logs replays logs         |
+  | receiver_write_location  | text | Location in the Xlog buffer where the node that receives logs is written |
+  | receiver_commit_location | text | Consistency point reached for the DCF logs of the node that receives logs |
+  | receiver_flush_location  | text | Location in the Xlog disk where the node that receives logs is written |
+  | receiver_replay_location | text | Location where the node that receives logs replays Xlogs     |
+  | sync_percent             | text | Synchronization percentage                                   |
+  | dcf_run_mode             | int4 | DCF synchronization mode                                     |
+  | channel                  | text | Channel information                                          |
+
+- gs_wlm_get_resource_pool_info(int)
+
+  Description: Obtains resource usage statistics of all users. The input parameter can be any value of the INT type or be null.
+
+  Return type: record
+
+- gs_wlm_get_all_user_resource_info()
+
+  Description: Obtains the resource usage statistics of all users.
+
+  Return type: record
+
+- gs_wlm_get_user_info(int)
+
+  Description: Obtains information about all users. The input parameter can be any value of the INT type or be null. Only users with the **sysadmin** permission can execute this function.
+
+  Return type: record
+
+- gs_wlm_get_workload_records()
+
+  Description: Obtains all job information in dynamic load management. This function is valid only when dynamic load management is enabled.
+
+  Return type: record
+
+- gs_wlm_readjust_user_space()
+
+  Description: Corrects the storage space usage of all users. Only the administrator can execute this function.
+
+  Return type: record
+
+- gs_wlm_readjust_user_space_through_username(text name)
+
+  Description: Corrects the storage space usage of a specified user. Common users can use this function to modify only their own usage. Only the administrator can modify the usage of all users. If the value of **name** is **0000**, the usage of all users needs to be modified.
+
+  Return type: record
+
+- gs_wlm_readjust_user_space_with_reset_flag(text name, boolean isfirst)
+
+  Description: Corrects the storage space usage of a specified user. If the input parameter **isfirst** is set to **true**, statistics are collected from 0. Otherwise, statistics are collected from the previous result. Common users can use this function to modify only their own usage. Only the administrator can modify the usage of all users. If the value of **name** is **0000**, the usage of all users needs to be modified.
+
+  Return type: record
+
+- gs_wlm_session_respool(bigint)
+
+  Description: Obtains the session resource pool information about all backend threads. The input parameter can be any value of the bigint type or can be null.
+
+  Return type: record
+
+- gs_wlm_get_session_info()
+
+  Description: This API has been discarded and is unavailable currently.
+
+- gs_wlm_get_user_session_info()
+
+  Description: This API has been discarded and is unavailable currently.
+
+- gs_io_wait_status()
+
+  Description: This API does not support single-node systems or centralized systems and is unavailable currently.
+
+- global_stat_get_hotkeys_info()
+
+  Description: Obtains the statistics of hot keys in the entire cluster. This API does not support single-node systems or centralized systems and is unavailable currently.
+
+- global_stat_clean_hotkeys()
+
+  Description: Clears statistics on hot keys in the entire cluster. This API does not support single-node systems or centralized systems and is unavailable currently.
+
+- DBE_PERF.get_global_session_stat_activity()
+
+  Description: Displays information about threads that are running on each node in MogDB. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_thread_wait_status()
+
+  Description: Displays the block waiting status of backend threads and auxiliary threads on all nodes. To query this function, you must have the **sysadmin** or **monitoradmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_operator_history_table()
+
+  Description: Displays the operator-related records (persistent) generated after jobs are executed on the primary database node of the current user. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_operator_history()
+
+  Description: Displays the operator-related records generated after jobs are executed on the primary database node of the current user. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_operator_runtime()
+
+  Description: Displays real-time operator-related records of jobs executed on the primary database node of the current user. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_statement_complex_history()
+
+  Description: Displays the historical records of complex queries on the primary database node of the current user. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_statement_complex_history_table()
+
+  Description: Displays the historical records (persistent) of complex queries on the primary database node of the current user. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_statement_complex_runtime()
+
+  Description: Displays the real-time information of complex queries on the primary database node of the current user. To query this function, you must have the **sysadmin** or **monadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_memory_node_detail()
+
+  Description: Displays the memory usage of a certain database on all nodes. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_shared_memory_detail()
+
+  Description: Displays the usage information about all the shared memory contexts of all nodes. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_statio_all_indexes()
+
+  Description: Displays statistics about each index displayed in a row in the current database, showing I/O statistics about accesses to that specific index. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_summary_stat_all_tables()
+
+  Description: Displays statistics about a row in each table (including the TOAST table) on each node.
+
+  Return type: record
+
+- DBE_PERF.get_global_stat_all_tables()
+
+  Description: Displays statistics about a row in each table (including the TOAST table) on each node.
+
+  Return type: record
+
+- DBE_PERF.get_local_toastname_and_toastindexname()
+
+  Description: Provides the mapping between the name and index of the local TOAST table and its associated table. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_summary_statio_all_indexes()
+
+  Description: Collects statistics about each index displayed in a row in the current databases of all nodes and displays the I/O statistics of a specific index. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_statio_all_sequences()
+
+  Description: Provides I/O status information about all sequences in the namespace. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_statio_all_tables()
+
+  Description: Displays the I/O statistics about each table in databases on each node. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_summary_statio_all_tables()
+
+  Description: Collects I/O statistics about each table in databases in MogDB. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_local_toast_relation()
+
+  Description: Provides the mapping between the name of the local TOAST table and its associated table. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_statio_sys_indexes()
+
+  Description: Displays the I/O status information about all system catalog indexes in namespaces on each node. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_summary_statio_sys_indexes()
+
+  Description: Collects the I/O status information about all system catalog indexes in namespaces on each node. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_statio_sys_sequences()
+
+  Description: Provides the I/O status information about all the system sequences in the namespace. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_statio_sys_tables()
+
+  Description: Provides I/O status information about all system catalogs in namespaces on each node. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_summary_statio_sys_tables()
+
+  Description: Displays the I/O status information of all system catalogs in the namespace in MogDB. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_statio_user_indexes()
+
+  Description: Displays the I/O status information about all user relationship table indexes in namespaces on each node. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_summary_statio_user_indexes()
+
+  Description: Displays the I/O status information about all user relationship table indexes in namespaces in MogDB. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_statio_user_sequences()
+
+  Description: Displays the I/O status information about all user sequences in the namespace of each node. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_statio_user_tables()
+
+  Description: Displays the I/O status information about all user relationship tables in namespaces on each node. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_summary_statio_user_tables()
+
+  Description: Displays the I/O status information about all user relationship tables in namespaces in MogDB. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_stat_db_cu()
+
+  Description: Queries CU hits in a database and in each node in MogDB. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_stat_all_indexes()
+
+  Description: Displays statistics of each index in databases on all nodes. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_summary_stat_all_indexes()
+
+  Description: Collects statistics of each index in all databases on all nodes. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_stat_sys_tables()
+
+  Description: Displays statistics about the system catalogs of all the namespaces in **pg_catalog** and **information_schema** schemas on each node. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_summary_stat_sys_tables()
+
+  Description: Collects statistics about the system catalogs of all the namespaces in **pg_catalog** and **information_schema** schemas on each node. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_stat_sys_indexes()
+
+  Description: Displays index status information about all the system catalogs in the **pg_catalog** and **information_schema** schemas on each node. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_summary_stat_sys_indexes()
+
+  Description: Collects statistics about index status information about all the system catalogs in the **pg_catalog** and **information_schema** schemas on each node. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_stat_user_tables()
+
+  Description: Displays the status information about customized ordinary tables in all namespaces. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_summary_stat_user_tables()
+
+  Description: Collects statistics about the status information about customized ordinary tables in all namespaces. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_stat_user_indexes()
+
+  Description: Displays the status information about the index of customized ordinary tables in all databases. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_summary_stat_user_indexes()
+
+  Description: Collects statistics about the status information about the index of customized ordinary tables in all databases. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_stat_database()
+
+  Description: Displays database statistics of all nodes. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_stat_database_conflicts()
+
+  Description: Collects statistics on the database of all nodes. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_stat_xact_all_tables()
+
+  Description: Displays transaction status information about all ordinary tables and TOAST tables in all namespaces. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_summary_stat_xact_all_tables()
+
+  Description: Collects statistics about transaction status information about all ordinary tables and TOAST tables in all namespaces. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_stat_xact_sys_tables()
+
+  Description: Displays transaction status information about all system catalogs in namespaces on all nodes. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_summary_stat_xact_sys_tables()
+
+  Description: Collects statistics about transaction status information about all system catalogs in namespaces on all nodes. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_stat_xact_user_tables()
+
+  Description: Displays the transaction status information of the user tables in the namespaces on all nodes. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_summary_stat_xact_user_tables()
+
+  Description: Collects statistics about the transaction status information of the user tables in the namespaces on all nodes. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_stat_user_functions()
+
+  Description: Displays the transaction status information of customized functions in the namespaces on all nodes. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_stat_xact_user_functions()
+
+  Description: Collects statistics about the transaction status information of customized functions in the namespaces on all nodes. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_stat_bad_block()
+
+  Description: Displays information about table and index read failures on all nodes. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_file_redo_iostat()
+
+  Description: Collects statistics on information about table and index read failures on all nodes. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_file_iostat()
+
+  Description: Displays statistics about data file I/Os on all nodes. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_locks()
+
+  Description: Displays lock information of all nodes. To query this function, you must have the **sysadmin** or **monadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_replication_slots()
+
+  Description: Displays logical replication information on all nodes. To query this function, you must have the **sysadmin** or **monadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_bgwriter_stat()
+
+  Description: Displays statistics about the background writer process's activities on all nodes. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_replication_stat()
+
+  Description: Displays information about log synchronization status on each node, such as the locations where the sender sends logs and where the receiver receives logs. To query this function, you must have the **sysadmin** or **monadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_transactions_running_xacts()
+
+  Description: Displays information about running transactions on each node. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_summary_transactions_running_xacts()
+
+  Description: Collects statistics of information about running transactions on each node. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_transactions_prepared_xacts()
+
+  Description: Displays information about transactions that are currently prepared for two-phase commit on each node. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_summary_transactions_prepared_xacts()
+
+  Description: Collects statistics information about transactions that are currently prepared for two-phase commit on each node. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_summary_statement()
+
+  Description: Displays the status information of the historically-executed statements on each node. To query this function, you must have the **sysadmin** or **monitoradmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_statement_count()
+
+  Description: Displays the number of **SELECT**, **UPDATE**, **INSERT**, and **DELETE** statements and response time information (TOTAL, AVG, MIN, and MAX) on each node. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_config_settings()
+
+  Description: Displays GUC parameter configuration information on each node. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_wait_events()
+
+  Description: Displays the wait event status information on each node. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_statement_responsetime_percentile()
+
+  Description: Obtains the response time distribution for 80% and 95% SQL statements of MogDB. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_summary_user_login()
+
+  Description: Collects statistics about number of user login and logout times on each node in MogDB. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.get_global_record_reset_time()
+
+  Description: Displays the statistics about reset (restart, primary/standby switchover, and database deletion) time of MogDB. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.track_memory_context(context_list text)
+
+  Description: Sets the memory context whose memory application details need to be collected. The input parameter is the memory context names, which are separated by commas (,), for example, **ThreadTopMemoryContext, SessionCacheMemoryContext**. Note that the memory context names are context-sensitive. In addition, the length of a single memory context is 63, and the excess part is truncated. The maximum number of memory contexts that can be collected at a time is 16. If the number of memory contexts exceeds 16, the setting fails. Each time this function is called, the previous statistics result is cleared. When the input parameter is set to **""**, the statistics function is disabled. Only the initial user (super user) or a user with the **monadmin**permission can execute this function.
+
+  Return type: Boolean
+
+- DBE_PERF.track_memory_context_detail()
+
+  Description: Obtains the memory application details of the memory context specified by the **DBE_PERF.track_memory_context** function. For details, see the **DBE_PERF.track_memory_context_detail** view. Only the initial user (super user) or a user with the **monadmin**permission can execute this function.
+
+  Return type: record
+
+- pg_stat_get_mem_mbytes_reserved(tid)
+
+  Description: Collects statistics on variables related to resource management, which is used only for fault locating.
+
+  Parameter: thread ID
+
+  Return type: text
+
+- gs_wlm_user_resource_info(name text)
+
+  Description: Queries a user's resource quota and resource usage.
+
+  Return type: record
+
+- pg_stat_get_file_stat()
+
+  Description: Rrecords statistics about data file I/Os to indicate I/O performance and detect performance problems such as abnormal I/O operations.
+
+  Return type: record
+
+- pg_stat_get_redo_stat()
+
+  Description: Displays statistics on the replay of session thread logs.
+
+  Return type: record
+
+- pg_stat_get_status(int8)
+
+  Description: Tests the block waiting status about the backend thread and auxiliary thread of the current instance.
+
+  Return type: record
+
+- get_local_rel_iostat()
+
+  Description: Queries the accumulated I/O status of data files on the current node.
+
+  Return type: record
+
+- DBE_PERF.get_global_rel_iostat()
+
+  Description: Displays statistics about data file I/Os on all nodes. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- DBE_PERF.global_threadpool_status()
+
+  Description: Displays the status of worker threads and sessions in thread pools on all nodes. For details about the columns returned by the function, see GLOBAL_THREADPOOL_STATUS.
+
+  Return type: record
+
+- remote_bgwriter_stat()
+
+  Description: Displays the information about pages flushed by the bgwriter threads of all instances in the database, number of pages in the candidate buffer chain, and buffer elimination information (except for the local node and not available on the DN).
+
+  Return type: record
+
+- pv_os_run_info
+
+  Description: Displays the running status of the current OS. For details about the columns, see GS_OS_RUN_INFO.
+
+  Parameter: nan
+
+  Return type: SETOF record
+
+- pv_session_stat
+
+  Description: Collects session status information by session thread or AutoVacuum thread. For details about the columns, see GS_SESSION_STAT.
+
+  Parameter: **nan**
+
+  Return type: SETOF record
+
+- pv_session_time
+
+  Description: Collects statistics on the running time of session threads and the time consumed in each execution phase. For details about the columns, see GS_SESSION_TIME.
+
+  Parameter: **nan**
+
+  Return type: SETOF record
+
+- pg_stat_get_db_temp_bytes
+
+  Description: Collects statistics on the total amount of data written to temporary files through database query. All temporary files are counted, regardless of why the temporary file was created, and regardless of the **log_temp_files** setting.
+
+  Parameter: **oid**
+
+  Return type: bigint
+
+- pg_stat_get_db_temp_files
+
+  Description: Queries the number of temporary files created in the database. All temporary files are counted, regardless of why the temporary file was created (for example, sorting or hashing), and regardless of the **log_temp_files** setting.
+
+  Parameter: **oid**
+
+  Return type: bigint
+
+- remote_candidate_stat()
+
+  Description: Displays the checkpoint information and log flushing information about all instances in the database (except the current node). Centralized systems are not supported.
+
+  Return type: record
+
+- dbe_perf.gs_stat_activity_timeout(int)
+
+  Description: Obtains information about query jobs whose execution time exceeds the timeout threshold on the current node. The correct result can be returned only when the GUC parameter **track_activities** is set to **on**. The timeout threshold ranges from 0 to 2147483.
+
+  Return type: SETOF record
+
+  | Name             | Type        | Description                                               |
+  | :--------------- | :---------- | :-------------------------------------------------------- |
+  | database         | name        | Name of the database to which a user session is connected |
+  | pid              | bigint      | Backend thread ID                                         |
+  | sessionid        | bigint      | Session ID                                                |
+  | usesysid         | oid         | OID of the user logged in to the backend                  |
+  | application_name | text        | Name of the application connected to the backend          |
+  | query            | text        | Query that is being executed on the backend               |
+  | xact_start       | timestamptz | Time when the current transaction is started              |
+  | query_start      | timestamptz | Time when the current query starts                        |
+  | query_id         | bigint      | Query statement ID                                        |
+
+- gs_wlm_user_resource_info(name text)
+
+  Description: Queries a user's resource quota and resource usage. Common users can query only their own information. Administrators can query information about all users.
+
+  Return type: record
+
+- create_wlm_instance_statistics_info
+
+  Description: Saves the historical monitoring data of the current instance persistently.
+
+  Parameter: **nan**
+
+  Return type: integer
+
+- gs_session_memory
+
+  Description: Collects statistics about memory usage at the session level in the unit of MB, including all the memory allocated to Postgres and Stream threads on DNs for tasks currently executed by users.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** If **enable_memory_limit** is set to **off**, this function cannot be used.
+
+  Return type: record
+
+  **Table 8** Return value description
+
+  | Name     | Type    | Description                                                  |
+  | :------- | :------ | :----------------------------------------------------------- |
+  | sessid   | text    | Thread start time and ID                                     |
+  | init_mem | integer | Memory allocated to the currently executed jobs before they enter the executor, in MB |
+  | used_mem | integer | Memory allocated to the currently executed jobs, in MB       |
+  | peak_mem | integer | Peak memory allocated to the currently executed jobs, in MB  |
+
+- gs_wlm_persistent_user_resource_info()
+
+  Description: Archives all user resource usage statistics to the **gs_wlm_user_resource_history** system catalog. To query this function, you must have the **sysadmin** permission.
+
+  Return type: record
+
+- create_wlm_operator_info(int flag)
+
+  Description: Clears top SQL operator-level statistics recorded in the current memory. If the input parameter is greater than 0, the information is archived to **gs_wlm_operator_info** and **gs_wlm_ec_operator_info**. Otherwise, the information is not archived. Only users with the **sysadmin** permission can execute this function.
+
+  Return type: int
+
+- GS_ALL_NODEGROUP_CONTROL_GROUP_INFO(text)
+
+  Description: Provides Cgroup information for all logical database instances. Before invoking this function, you need to specify the name of a logical database instance to be queried. For example, to query the Cgroup information for the installation logical database instance, run the following command:
+
+  ```sql
+  SELECT * FROM GS_ALL_NODEGROUP_CONTROL_GROUP_INFO('installation')
+  ```
+
+  Return type: record
+
+  The following table describes return columns.
+
+  | Name     | Type   | Description                                                  |
+  | :------- | :----- | :----------------------------------------------------------- |
+  | name     | text   | Cgroup name.                                                 |
+  | type     | text   | Cgroup type.                                                 |
+  | gid      | bigint | Cgroup ID.                                                   |
+  | classgid | bigint | ID of the **Class** cgroup where a **Workload** cgroup belongs. |
+  | class    | text   | **Class** cgroup.                                            |
+  | workload | text   | **Workload** cgroup.                                         |
+  | shares   | bigint | CPU quota allocated to the cgroup.                           |
+  | limits   | bigint | Limit of CPUs allocated to a cgroup.                         |
+  | wdlevel  | bigint | **Workload** cgroup level.                                   |
+  | cpucores | text   | Usage of CPU cores in a cgroup.                              |
+
+- gs_total_nodegroup_memory_detail
+
+  Description: Returns information about the memory used by the current logical database, in MB.
+
+  Return type: SETOF record
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/26-trigger-functions.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/26-trigger-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..db53263eb8a0d53831a5ab61b747cd8475435593
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/26-trigger-functions.md
@@ -0,0 +1,55 @@
+---
+title: Trigger Functions
+summary: Trigger Functions
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Trigger Functions
+
+- pg_get_triggerdef(oid)
+
+  Description: Obtains the definition information of a trigger.
+
+  Parameter: OID of the trigger to be queried
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# select pg_get_triggerdef(oid) from pg_trigger;
+                                                                                       pg_get_triggerdef
+  --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+   CREATE TRIGGER tg1 BEFORE INSERT ON gtest26 FOR EACH STATEMENT EXECUTE PROCEDURE gtest_trigger_func()
+   CREATE TRIGGER tg03 AFTER INSERT ON gtest26 FOR EACH ROW WHEN ((new.a IS NOT NULL)) EXECUTE PROCEDURE gtest_trigger_func()
+  (2 rows)
+  ```
+
+- pg_get_triggerdef(oid, boolean)
+
+  Description: Obtains the definition information of a trigger.
+
+  Parameter: OID of the trigger to be queried and whether it is displayed in pretty mode
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** Boolean parameters take effect only when the WHEN condition is specified during trigger creation.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# select pg_get_triggerdef(oid,true) from pg_trigger;
+                                                                                       pg_get_triggerdef
+  --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+   CREATE TRIGGER tg1 BEFORE INSERT ON gtest26 FOR EACH STATEMENT EXECUTE PROCEDURE gtest_trigger_func()
+   CREATE TRIGGER tg03 AFTER INSERT ON gtest26 FOR EACH ROW WHEN (new.a IS NOT NULL) EXECUTE PROCEDURE gtest_trigger_func()
+  (2 rows)
+
+  mogdb=# select pg_get_triggerdef(oid,false) from pg_trigger;
+                                                                                       pg_get_triggerdef
+  --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+   CREATE TRIGGER tg1 BEFORE INSERT ON gtest26 FOR EACH STATEMENT EXECUTE PROCEDURE gtest_trigger_func()
+   CREATE TRIGGER tg03 AFTER INSERT ON gtest26 FOR EACH ROW WHEN ((new.a IS NOT NULL)) EXECUTE PROCEDURE gtest_trigger_func()
+  (2 rows)
+  ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/27-global-temporary-table-functions.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/27-global-temporary-table-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..c824fa6b3e016162d060366d9ecd856696b7cb82
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/27-global-temporary-table-functions.md
@@ -0,0 +1,132 @@
+---
+title: Global Temporary Table Functions
+summary: Global Temporary Table Functions
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Global Temporary Table Functions
+
+- pg_get_gtt_relstats(relOid)
+
+  Description: Displays basic information about a global temporary table specified by the current session.
+
+  Parameter: OID of the global temporary table
+
+  Return type: record
+
+  Example:
+
+  ```sql
+  mogdb=# select * from pg_get_gtt_relstats(74069);
+   relfilenode | relpages | reltuples | relallvisible | relfrozenxid | relminmxid
+  -------------+----------+-----------+---------------+--------------+------------
+         74069 |       58 |     13000 |             0 |        11151 |          0
+  (1 row)
+  ```
+
+- pg_get_gtt_statistics(relOid, attnum, "::text)
+
+  Description: Displays statistics about a single column in a global temporary table specified by the current session.
+
+  Parameter: OID and the **attnum** attribute of the global temporary table
+
+  Return type: record
+
+  Example:
+
+  ```sql
+  mogdb=# select * from pg_get_gtt_statistics(74069,1,''::text);
+   starelid | starelkind | staattnum | stainherit | stanullfrac | stawidth | stadistinct | stakind1 | stakind2 | stakind3 | stakind4 | stakind5 | staop1 | staop2 | staop3 | staop4 | staop5 | stanumbers1 | stanumbers2 | stanumbers3 | stanu
+  mbers4 | stanumbers5 |
+                                            stavalues1
+                                                                          | stavalues2 | stavalues3 | stavalues4 | stavalues5 | stadndistinct | staextinfo
+  ----------+------------+-----------+------------+-------------+----------+-------------+----------+----------+----------+----------+----------+--------+--------+--------+--------+--------+-------------+-------------+-------------+------
+  -------+-------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+  --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+  ------------------------------------------------------------------------+------------+------------+------------+------------+---------------+------------
+      74069 | c          |         1 | f          |           0 |        4 |          -1 |        2 |        3 |        0 |        0 |        0 |     97 |     97 |      0 |      0 |      0 |             | {1}         |             |
+         |             | {1,130,260,390,520,650,780,910,1040,1170,1300,1430,1560,1690,1820,1950,2080,2210,2340,2470,2600,2730,2860,2990,3120,3250,3380,3510,3640,3770,3900,4030,4160,4290,4420,4550,4680,4810,4940,5070,5200,5330,5460,5590,57
+  20,5850,5980,6110,6240,6370,6500,6630,6760,6890,7020,7150,7280,7410,7540,7670,7800,7930,8060,8190,8320,8450,8580,8710,8840,8970,9100,9230,9360,9490,9620,9750,9880,10010,10140,10270,10400,10530,10660,10790,10920,11050,11180,11310,11440,1
+  1570,11700,11830,11960,12090,12220,12350,12480,12610,12740,12870,13000} |            |            |            |            |             0 |
+  (1 row)
+  ```
+
+- pg_gtt_attached_pid(relOid)
+
+  Description: Displays PIDs of all threads that are using the specified global temporary table.
+
+  Parameter: OID of the global temporary table
+
+  Return type: record
+
+  Example:
+
+  ```sql
+  mogdb=# select * from pg_gtt_attached_pid(74069);
+   relid |       pid
+  -------+-----------------
+   74069 | 139648170456832
+   74069 | 139648123270912
+  (2 rows)
+  ```
+
+- dbe_perf.get_global_full_sql_by_timestamp(start_timestamp timestamp, end_timestamp timestamp)
+
+  Description: Obtains full SQL information at the instance level.
+
+  Return type: record
+
+  **Table 1** dbe_perf.get_global_full_sql_by_timestamp parameter description
+
+  | Parameter       | Type      | Description                              |
+  | :-------------- | :-------- | :--------------------------------------- |
+  | start_timestamp | timestamp | Start point of the SQL start time range. |
+  | end_timestamp   | timestamp | End point of the SQL start time range.   |
+
+- dbe_perf.get_global_slow_sql_by_timestamp(start_timestamp timestamp, end_timestamp timestamp)
+
+  Description: Obtains slow SQL information at the instance level.
+
+  Return type: record
+
+  **Table 2** dbe_perf.get_global_slow_sql_by_timestamp parameter description
+
+  | Parameter       | Type      | Description                              |
+  | :-------------- | :-------- | :--------------------------------------- |
+  | start_timestamp | timestamp | Start point of the SQL start time range. |
+  | end_timestamp   | timestamp | End point of the SQL start time range.   |
+
+- statement_detail_decode(detail text, format text, pretty bool)
+
+  Parses the details column in a full or slow SQL statement.
+
+  **Table 3** statement_detail_decode parameter description
+
+  | Parameter | Type | Description                                                  |
+  | :-------- | :--- | :----------------------------------------------------------- |
+  | detail    | text | Set of events generated by the SQL statement (unreadable).   |
+  | format    | text | Parsing output format. <br />The value is **plaintext** or **json**. |
+  | pretty    | bool | Whether to display the text in pretty format when **format** is set to **plaintext**. <br />The options are as follows:<br />- The value **true** indicates that events are separated by `\n`.<br />- The value **false** indicates that events are separated by commas (,). |
+
+- pg_list_gtt_relfrozenxids()
+
+  Description: Displays the frozen XID of each session.
+
+  If the value of **pid** is **0**, the earliest frozen XID of all sessions is displayed.
+
+  Parameter: none
+
+  Return type: record
+
+  Example:
+
+  ```sql
+  mogdb=# select * from pg_list_gtt_relfrozenxids();
+         pid       | relfrozenxid
+  -----------------+--------------
+   139648123270912 |        11151
+   139648170456832 |        11155
+                 0 |        11151
+  (3 rows)
+  ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/27.1-hash-function.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/27.1-hash-function.md
new file mode 100644
index 0000000000000000000000000000000000000000..ca3b5c374f463a47c9dd04d557830e0e9967b775
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/27.1-hash-function.md
@@ -0,0 +1,595 @@
+---
+title: Hash Function
+summary: Hash Function
+author: Guo Huan
+date: 2021-10-28
+---
+
+# Hash Function
+
+- bucketabstime(value, flag)
+
+  Description: Hashes the value in the abstime format and finds the corresponding hash bucket.
+
+  Parameter: **value** indicates the value to be converted, which is of the abstime type. **flag** is of the int type, indicating the data distribution mode. The value **0** indicates hash distribution.
+
+  Return type: int32
+
+  Example:
+
+  ```
+  mogdb=# select bucketabstime('2011-10-01 10:10:10.112',1);
+   bucketabstime
+  ---------------
+           13954
+  (1 row)
+  ```
+
+- bucketbool(value, flag)
+
+  Description: Hashes the value in the bool format and finds the corresponding hash bucket.
+
+  Parameter: **value** indicates the value to be converted, which is of the bool type. **flag** is of the int type, indicating the data distribution mode. The value **0** indicates hash distribution.
+
+  Return type: int32
+
+  Example:
+
+  ```
+  mogdb=# select bucketbool(true,1);
+   bucketbool
+  ------------
+            1
+  (1 row)
+  mogdb=#  select bucketbool(false,1);
+   bucketbool
+  ------------
+            0
+  (1 row)
+  ```
+
+- bucketbpchar(value, flag)
+
+  Description: Hashes the value in the bpchar format and finds the corresponding hash bucket.
+
+  Parameter: **value** indicates the value to be converted, which is of the bpchar type. **flag** is of the int type, indicating the data distribution mode. The value **0** indicates hash distribution.
+
+  Return type: int32
+
+  Example:
+
+  ```
+  mogdb=# select bucketbpchar('test',1);
+   bucketbpchar
+  --------------
+           9761
+  (1 row)
+  ```
+
+- bucketbytea(value, flag)
+
+  Description: Hashes the value in the bytea format and finds the corresponding hash bucket.
+
+  Parameter: **value** indicates the value to be converted, which is of the bytea type. **flag** is of the int type, indicating the data distribution mode. The value **0** indicates hash distribution.
+
+  Return type: int32
+
+  Example:
+
+  ```
+  mogdb=# select bucketbytea('test',1);
+   bucketbytea
+  -------------
+          9761
+  (1 row)
+  ```
+
+- bucketcash(value, flag)
+
+  Description: Hashes the value in the money format and finds the corresponding hash bucket.
+
+  Parameter: **value** indicates the value to be converted, which is of the money type. **flag** is of the int type, indicating the data distribution mode. The value **0** indicates hash distribution.
+
+  Return type: int32
+
+  Example:
+
+  ```
+  mogdb=# select bucketcash(10::money,1);
+   bucketcash
+  ------------
+         8468
+  (1 row)
+  ```
+
+- getbucket(value, flag)
+
+  Description: Obtains the hash bucket from the distribution column.
+
+  **value** indicates the value to be entered, which can be of the following types:
+
+  "char", abstime, bigint, boolean, bytea, character varying, character, date, double precision, int2vector, integer, interval, money, name, numeric, nvarchar2, oid, oidvector, raw, real, record, reltime, smalldatetime, smallint, text, time with time zone, time without time zone, timestamp with time zone, timestamp without time zone, tinyint, and uuid
+
+  **flag** is of the int type, indicating the data distribution mode.
+
+  Return type: integer
+
+  Example:
+
+  ```
+  mogdb=# select getbucket(10,'H');
+   getbucket
+  -----------
+       14535
+  (1 row)
+
+  mogdb=# select getbucket(11,'H');
+   getbucket
+  -----------
+       13449
+  (1 row)
+
+  mogdb=# select getbucket(11,'R');
+   getbucket
+  -----------
+       13449
+  (1 row)
+
+  mogdb=# select getbucket(12,'R');
+   getbucket
+  -----------
+        9412
+  (1 row)
+
+  ```
+
+- hash_array(anyarray)
+
+  Description: Hashes an array, obtains the result of an array element using the hash function, and returns the combination result.
+
+  Parameter: data of the anyrange type
+
+  Return type: integer
+
+  Example:
+
+  ```
+  mogdb=# select hash_array(ARRAY[[1,2,3],[1,2,3]]);
+   hash_array
+  ------------
+   -382888479
+  (1 row)
+  ```
+
+- hash_group(key)
+
+  Description: Calculates the hash value of each column in the Group Clause in the streaming engine.
+
+  Parameter: **key** indicates the value of each column in the Group Clause.
+
+  Return type: 32-bit hash value
+
+  Example:
+
+  ```
+  Perform the following steps in sequence.
+  mogdb=# CREATE TABLE tt(a int, b int,c int,d int);
+  NOTICE:  The 'DISTRIBUTE BY' clause is not specified. Using 'a' as the distribution column by default.
+  HINT:  Please use 'DISTRIBUTE BY' clause to specify suitable data distribution column.
+  CREATE TABLE
+  mogdb=# select * from tt;
+   a | b | c | d
+  ---+---+---+---
+  (0 rows)
+
+  mogdb=# insert into tt values(1,2,3,4);
+  INSERT 0 1
+  mogdb=# select * from tt;
+   a | b | c | d
+  ---+---+---+---
+   1 | 2 | 3 | 4
+  (1 row)
+
+  mogdb=# insert into tt values(5,6,7,8);
+  INSERT 0 1
+  mogdb=# select * from tt;
+   a | b | c | d
+  ---+---+---+---
+   1 | 2 | 3 | 4
+   5 | 6 | 7 | 8
+  (2 rows)
+
+  mogdb=# select hash_group(a,b) from tt where a=1 and b=2;
+   hash_group
+  ------------
+    990882385
+  (1 row)
+  ```
+
+- hash_numeric(numeric)
+
+  Description: Calculates the hash value of numeric data.
+
+  Parameter: data of the numeric type.
+
+  Return type: integer
+
+  Example:
+
+  ```
+  mogdb=# select hash_numeric(30);
+   hash_numeric
+  --------------
+     -282860963
+  (1 row)
+  ```
+
+- hash_range(anyrange)
+
+  Description: Calculates the hash value of a range.
+
+  Parameter: data of the anyrange type
+
+  Return type: integer
+
+  Example:
+
+  ```
+  mogdb=# select hash_range(numrange(1.1,2.2));
+   hash_range
+  ------------
+    683508754
+  (1 row)
+  ```
+
+- hashbpchar(character)
+
+  Description: Calculates the hash value of bpchar.
+
+  Parameter: data of the character type
+
+  Return type: integer
+
+  Example:
+
+  ```
+  mogdb=# select hashbpchar('hello');
+   hashbpchar
+  -------------
+   -1870292951
+  (1 row)
+  ```
+
+- hashchar(char)
+
+  Description: Converts char and Boolean data into hash values.
+
+  Parameter: data of the char or bool type
+
+  Return type: integer
+
+  Example:
+
+  ```
+  mogdb=# select hashbpchar('hello');
+   hashbpchar
+  -------------
+   -1870292951
+  (1 row)
+
+  mogdb=# select hashchar('true');
+    hashchar
+  ------------
+   1686226652
+  (1 row)
+  ```
+
+- hashenum(anyenum)
+
+  Description: Converts enumerated values to hash values.
+
+  Parameter: data of the anyenum type
+
+  Return type: integer
+
+  Example:
+
+  ```
+  mogdb=# CREATE TYPE b1 AS ENUM('good', 'bad', 'ugly');
+  CREATE TYPE
+  mogdb=# call hashenum('good'::b1);
+    hashenum
+  ------------
+   1821213359
+  (1 row)
+  ```
+
+- hashfloat4(real)
+
+  Description: Converts float4 values to hash values.
+
+  Parameter: data of the real type
+
+  Return type: integer
+
+  Example:
+
+  ```
+  mogdb=# select hashfloat4(12.1234);
+   hashfloat4
+  ------------
+   1398514061
+  (1 row)
+  ```
+
+- hashfloat8(double precision)
+
+  Description: Converts float8 values to hash values.
+
+  Parameter: data of the double precision type
+
+  Return type: integer
+
+  Example:
+
+  ```
+  mogdb=# select hashfloat8(123456.1234);
+   hashfloat8
+  ------------
+   1673665593
+  (1 row)
+  ```
+
+- hashinet(inet)
+
+  Description: Supports hashing indexes on inet or cidr. Returns the hash value of inet.
+
+  Parameter: data of the inet type
+
+  Return type: integer
+
+  Example:
+
+  ```
+  mogdb=# select hashinet('127.0.0.1'::inet);
+    hashinet
+  -------------
+   -1435793109
+  (1 row)
+  ```
+
+- hashint1(tinyint)
+
+  Description: Converts INT1 values to hash values.
+
+  Parameter: data of the tinyint type
+
+  Return type: uint32
+
+  Example:
+
+  ```
+  mogdb=# select hashint1(20);
+    hashint1
+  -------------
+   -2014641093
+  (1 row)
+  ```
+
+- hashint2(smallint)
+
+  Description: Converts INT2 values to hash values.
+
+  Parameter: data of the smallint type
+
+  Return type: uint32
+
+  Example:
+
+  ```
+  mogdb=# select hashint2(20000);
+    hashint2
+  ------------
+   -863179081
+  (1 row)
+  ```
+
+- bucketchar
+
+  Description: Calculates the hash value of the input parameter.
+
+  Parameter: **char** and **integer**
+
+  Return type: integer
+
+- bucketdate
+
+  Description: Calculates the hash value of the input parameter.
+
+  Parameters: **date** and **integer**
+
+  Return type: integer
+
+- bucketfloat4
+
+  Description: Calculates the hash value of the input parameter.
+
+  Parameter: **real** and **integer**
+
+  Return type: integer
+
+- bucketfloat8
+
+  Description: Calculates the hash value of the input parameter.
+
+  Parameters: **double precision** and **integer**
+
+  Return type: integer
+
+- bucketint1
+
+  Description: Calculates the hash value of the input parameter.
+
+  Parameter: **tinyint** and **integer**
+
+  Return type: integer
+
+- bucketint2
+
+  Description: Calculates the hash value of the input parameter.
+
+  Parameters: **smallint** and **integer**
+
+  Return type: integer
+
+- bucketint2vector
+
+  Description: Calculates the hash value of the input parameter.
+
+  Parameter: **int2vector** and **integer**
+
+  Return type: integer
+
+- bucketint4
+
+  Description: Calculates the hash value of the input parameter.
+
+  Parameter: integer, integer
+
+  Return type: integer
+
+- bucketint8
+
+  Description: Calculates the hash value of the input parameter.
+
+  Parameter: bigint, integer
+
+  Return type: integer
+
+- bucketinterval
+
+  Description: Calculates the hash value of the input parameter.
+
+  Parameter: interval, integer
+
+  Return type: integer
+
+- bucketname
+
+  Description: Calculates the hash value of the input parameter.
+
+  Parameter: name, integer
+
+  Return type: integer
+
+- bucketnumeric
+
+  Description: Calculates the hash value of the input parameter.
+
+  Parameter: numeric, integer
+
+  Return type: integer
+
+- bucketnvarchar2
+
+  Description: Calculates the hash value of the input parameter.
+
+  Parameter: nvarchar2, integer
+
+  Return type: integer
+
+- bucketoid
+
+  Description: Calculates the hash value of the input parameter.
+
+  Parameters: oid, integer
+
+  Return type: integer
+
+- bucketoidvector
+
+  Description: Calculates the hash value of the input parameter.
+
+  Parameter: oidvector, integer
+
+  Return type: integer
+
+- bucketraw
+
+  Description: Calculates the hash value of the input parameter.
+
+  Parameter: raw, integer
+
+  Return type: integer
+
+- bucketreltime
+
+  Description: Calculates the hash value of the input parameter.
+
+  Parameter: reltime, integer
+
+  Return type: integer
+
+- bucketsmalldatetime
+
+  Description: Calculates the hash value of the input parameter.
+
+  Parameter: smalldatetime, integer
+
+  Return type: integer
+
+- buckettext
+
+  Description: Calculates the hash value of the input parameter.
+
+  Parameter: text, integer
+
+  Return type: integer
+
+- buckettime
+
+  Description: Calculates the hash value of the input parameter.
+
+  Parameter: time without time zone, integer
+
+  Return type: integer
+
+- buckettimestamp
+
+  Description: Calculates the hash value of the input parameter.
+
+  Parameter: timestamp without time zone, integer
+
+  Return type: integer
+
+- buckettimestamptz
+
+  Description: Calculates the hash value of the input parameter.
+
+  Parameter: timestamp with time zone, integer
+
+  Return type: integer
+
+- buckettimetz
+
+  Description: Calculates the hash value of the input parameter.
+
+  Parameter: time with time zone, integer
+
+  Return type: integer
+
+- bucketuuid
+
+  Description: Calculates the hash value of the input parameter.
+
+  Parameters: uuid, integer
+
+  Return type: integer
+
+- bucketvarchar
+
+  Description: Calculates the hash value of the input parameter.
+
+  Parameter: character varying, integer
+
+  Return type: integer
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/27.2-prompt-message-function.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/27.2-prompt-message-function.md
new file mode 100644
index 0000000000000000000000000000000000000000..27633ebec0b4eedcf0d4f140fc8541979ecc2f4e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/27.2-prompt-message-function.md
@@ -0,0 +1,21 @@
+---
+title: Prompt Message Function
+summary: Prompt Message Function
+author: Guo Huan
+date: 2021-10-28
+---
+
+# Prompt Message Function
+
+- report_application_error
+
+  Description: This function can be used to throw errors during PL execution.
+
+  Return type: void
+
+  **Table 1** report_application_error parameter description
+
+  | Parameter | Type | Description                                                  | Mandatory or Not |
+  | :-------- | :--- | :----------------------------------------------------------- | :--------------- |
+  | log       | text | Content of an error message.                                 | Yes              |
+  | code      | int4 | Error code corresponding to an error message. The value ranges from -20999 to -20000. | No               |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/28-ai-feature-functions.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/28-ai-feature-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..728c540cdf65851133c8e45d847521c112c03882
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/28-ai-feature-functions.md
@@ -0,0 +1,184 @@
+---
+title: AI Feature Functions
+summary: AI Feature Functions
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# AI Feature Functions
+
+- gs_index_advise(text)
+
+  Description: Recommends an index for a single query statement.
+
+  Parameter: SQL statement string
+
+  Return type: record
+
+  Single-query Index Recommendation describes the examples.
+
+- hypopg_create_index(text)
+
+  Description: Creates a virtual index.
+
+  Parameter: character string of the statement for creating an index
+
+  Return type: record
+
+  Virtual Index describes the examples.
+
+- hypopg_display_index()
+
+  Description: Displays information about all created virtual indexes.
+
+  Parameter: none
+
+  Return type: record
+
+  Virtual Index describes the examples.
+
+- hypopg_drop_index(oid)
+
+  Description: Deletes a specified virtual index.
+
+  Parameter: OID of the index
+
+  Return type: Boolean
+
+  Virtual Index describes the examples.
+
+- hypopg_reset_index()
+
+  Description: Clears all virtual indexes.
+
+  Parameter: none
+
+  Return type: none
+
+  Virtual Index describes the examples.
+
+- hypopg_estimate_size(oid)
+
+  Description: Estimates the space required for creating a specified index.
+
+  Parameter: OID of the index
+
+  Return type: int8
+
+  Virtual Index describes the examples.
+
+- check_engine_status(ip text, port text)
+
+  Description: Tests whether a predictor engine provides services on a specified IP address and port.
+
+  Parameter: IP address and port number of the predictor engine.
+
+  Return type: text
+
+  **User Guide** describes the examples.
+
+- encode_plan_node(optname text, orientation text, strategy text, options text, dop int8, quals text, projection text)
+
+  Description: Encodes the plan operator information in the input parameters.
+
+  Parameter: plan operator information
+
+  Return type: text.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** This function is an internal function. You are not advised to use it directly.
+
+- model_train_opt(template text, model text)
+
+  Description: Trains a given query performance prediction model.
+
+  Parameters: template name and model name of the performance prediction model
+
+  Return type: tartup_time_accuracy FLOAT8, total_time_accuracy FLOAT8, rows_accuracy FLOAT8, peak_memory_accuracy FLOAT8
+
+  **User Guide** describes the examples.
+
+- track_model_train_opt(ip text, port text)
+
+  Description: Returns the training log address of the specified IP address and port predictor engine.
+
+  Parameter: IP address and port number of the predictor engine
+
+  Return type: text
+
+  **User Guide** describes the examples.
+
+- encode_feature_perf_hist(datname text)
+
+  Description: Encodes historical plan operators collected in the target database.
+
+  Parameter: database name
+
+  Return type: queryid bigint, plan_node_id int, parent_node_id int, left_child_id int, right_child_id int, encode text, startup_time bigint, total_time bigint, rows bigint, and peak_memory int
+
+  **User Guide** describes the examples.
+
+- gather_encoding_info(datname text)
+
+  Description: Invokes **encode_feature_perf_hist** to save the encoded data persistently.
+
+  Parameter: database name
+
+  Return type: int
+
+  **User Guide** describes the examples.
+
+- db4ai_predict_by_bool (text, VARIADIC "any")
+
+    Description: Obtains a model whose return value is of the Boolean type for model inference. This function is an internal function. You are advised to use the  **PREDICT BY**  syntax for inference.
+
+    Parameter: model name and input column name of the inference task
+
+    Return type: Boolean
+
+- db4ai_predict_by_float4(text, VARIADIC "any")
+
+    Description: Obtains a model whose return value is of the float4 type for model inference. This function is an internal function. You are advised to use the  **PREDICT BY**  syntax for inference.
+
+    Parameter: model name and input column name of the inference task
+
+    Return type: float
+
+- db4ai_predict_by_float8(text, VARIADIC "any")
+
+    Description: Obtains a model whose return value is of the float8 type for model inference. This function is an internal function. You are advised to use the  **PREDICT BY**  syntax for inference.
+
+    Parameter: model name and input column name of the inference task
+
+    Return type: float
+
+- db4ai_predict_by_int32(text, VARIADIC "any")
+
+    Description: Obtains a model whose return value is of the int32 type for model inference. This function is an internal function. You are advised to use the  **PREDICT BY**  syntax for inference.
+
+    Parameter: model name and input column name of the inference task
+
+    Return type: int
+
+- db4ai_predict_by_int64(text, VARIADIC "any")
+
+    Description: Obtains a model whose return value is of the int64 type for model inference. This function is an internal function. You are advised to use the  **PREDICT BY**  syntax for inference.
+
+    Parameter: model name and input column name of the inference task
+
+    Return type: int
+
+- db4ai_predict_by_numeric(text, VARIADIC "any")
+
+    Description: Obtains a model whose return value is of the numeric type for model inference. This function is an internal function. You are advised to use the  **PREDICT BY**  syntax for inference.
+
+    Parameter: model name and input column name of the inference task
+
+    Return type: numeric
+
+- db4ai_predict_by_text(text, VARIADIC "any")
+
+    Description: Obtains a model whose return value is of the character type for model inference. This function is an internal function. You are advised to use the  **PREDICT BY**  syntax for inference.
+
+    Parameter: model name and input column name of the inference task
+
+    Return type: text
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/28.1-fault-injection-system-function.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/28.1-fault-injection-system-function.md
new file mode 100644
index 0000000000000000000000000000000000000000..66485a7a1b7d58944f48b482169db0bf21de34de
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/28.1-fault-injection-system-function.md
@@ -0,0 +1,20 @@
+---
+title: Fault Injection System Function
+summary: Fault Injection System Function
+author: Guo Huan
+date: 2021-10-28
+---
+
+# Fault Injection System Function
+
+- gs_fault_inject(int64, text, text, text, text, text)
+
+  Description: This function cannot be called. WARNING information "unsupported fault injection" is reported when this function is called, which does not affect or change the database.
+
+  Parameter: fault injection of the int64 type (**0**: CLOG extended page; **1**: CLOG page reading; **2**: forcible deadlock)
+
+  - If the first input parameter of text is set to **2** and the second input parameter of text is set to **1**, the second input parameter deadlock occurs. Other input parameters are not deadlocked. When the first input parameter is **0** or **1**, the second input parameter indicates the number of the start page from which the CLOG starts to be extended or read.
+  - The third input parameter of text indicates the number of extended or read pages when the first input parameter is **0** or **1**.
+  - The fourth to sixth input parameters of text are reserved.
+
+  Return type: int64
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/29-other-system-functions.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/29-other-system-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..bd6e6fa1bba5e7faa590be3d6d86b0f18249b5eb
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/29-other-system-functions.md
@@ -0,0 +1,682 @@
+---
+title: Other System Functions
+summary: Other System Functions
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Other System Functions
+
+The MogDB built-in functions and operators are inherited from the open-source PG. For details about the following functions, see the [official PG documents](https://www.postgresql.org/docs/9.2/functions.html).
+
+| _pg_char_max_length              | _pg_char_octet_length                    | _pg_datetime_precision            | _pg_expandarray                | _pg_index_position             | _pg_interval_type                  | _pg_numeric_precision                |
+| -------------------------------- | ---------------------------------------- | --------------------------------- | ------------------------------ | ------------------------------ | ---------------------------------- | ------------------------------------ |
+| _pg_numeric_precision_radix      | _pg_numeric_scale                        | _pg_truetypid                     | _pg_truetypmod                 | abbrev                         | abs                                | abstime                              |
+| abstimeeq                        | abstimege                                | abstimegt                         | abstimein                      | abstimele                      | abstimelt                          | abstimene                            |
+| abstimeout                       | abstimerecv                              | abstimesend                       | aclcontains                    | acldefault                     | aclexplode                         | aclinsert                            |
+| aclitemeq                        | aclitemin                                | aclitemout                        | aclremove                      | acos                           | age                                | akeys                                |
+| any_in                           | any_out                                  | anyarray_in                       | anyarray_out                   | anyarray_recv                  | anyarray_send                      | anyelement_in                        |
+| anyelement_out                   | anyenum_in                               | anyenum_out                       | anynonarray_in                 | anynonarray_out                | anyrange_in                        | anyrange_out                         |
+| anytextcat                       | area                                     | areajoinsel                       | areasel                        | array_agg                      | array_agg_finalfn                  | array_agg_transfn                    |
+| array_append                     | array_cat                                | array_dims                        | array_eq                       | array_fill                     | array_ge                           | array_gt                             |
+| array_in                         | array_larger                             | array_le                          | array_length                   | array_lower                    | array_lt                           | array_ndims                          |
+| array_ne                         | array_out                                | array_prepend                     | array_recv                     | array_send                     | array_smaller                      | array_to_json                        |
+| array_to_string                  | array_typanalyze                         | array_upper                       | arraycontained                 | arraycontains                  | arraycontjoinsel                   | arraycontsel                         |
+| arrayoverlap                     | ascii                                    | asin                              | atan                           | atan2                          | avals                              | avg                                  |
+| big5_to_euc_tw                   | big5_to_mic                              | big5_to_utf8                      | bit                            | bit_and                        | bit_in                             | bit_length                           |
+| bit_or                           | bit_out                                  | bit_recv                          | bit_send                       | bitand                         | bitcat                             | bitcmp                               |
+| biteq                            | bitge                                    | bitgt                             | bitle                          | bitlt                          | bitne                              | bitnot                               |
+| bitor                            | bitshiftleft                             | bitshiftright                     | bittypmodin                    | bittypmodout                   | bitxor                             | bool                                 |
+| bool_and                         | bool_or                                  | booland_statefunc                 | booleq                         | boolge                         | boolgt                             | boolin                               |
+| boolle                           | boollt                                   | boolne                            | boolor_statefunc               | boolout                        | boolrecv                           | boolsend                             |
+| box                              | box_above                                | box_above_eq                      | box_add                        | box_below                      | box_below_eq                       | box_center                           |
+| box_contain                      | box_contain_pt                           | box_contained                     | box_distance                   | box_div                        | box_eq                             | box_ge                               |
+| box_gt                           | box_in                                   | box_intersect                     | box_le                         | box_left                       | box_lt                             | box_mul                              |
+| box_out                          | box_overabove                            | box_overbelow                     | box_overlap                    | box_overleft                   | box_overright                      | box_recv                             |
+| box_right                        | box_same                                 | box_send                          | box_sub                        | bpchar                         | bpchar_larger                      | bpchar_pattern_ge                    |
+| bpchar_pattern_gt                | bpchar_pattern_le                        | bpchar_pattern_lt                 | bpchar_smaller                 | bpchar_sortsupport             | bpcharcmp                          | bpchareq                             |
+| bpcharge                         | bpchargt                                 | bpchariclike                      | bpcharicnlike                  | bpcharicregexeq                | bpcharicregexne                    | bpcharin                             |
+| bpcharle                         | bpcharlike                               | bpcharlt                          | bpcharne                       | bpcharnlike                    | bpcharout                          | bpcharrecv                           |
+| bpcharregexeq                    | bpcharregexne                            | bpcharsend                        | bpchartypmodin                 | bpchartypmodout                | broadcast                          | btabstimecmp                         |
+| btarraycmp                       | btbeginscan                              | btboolcmp                         | btbpchar_pattern_cmp           | btbuild                        | btbuildempty                       | btbulkdelete                         |
+| btcanreturn                      | btcharcmp                                | btcostestimate                    | btendscan                      | btfloat48cmp                   | btfloat4cmp                        | btfloat4sortsupport                  |
+| btfloat84cmp                     | btfloat8cmp                              | btfloat8sortsupport               | btgetbitmap                    | btgettuple                     | btinsert                           | btint24cmp                           |
+| btint28cmp                       | btint2cmp                                | btint2sortsupport                 | btint42cmp                     | btint48cmp                     | btint4cmp                          | btint4sortsupport                    |
+| btint82cmp                       | btint84cmp                               | btint8cmp                         | btint8sortsupport              | btmarkpos                      | btnamecmp                          | btnamesortsupport                    |
+| btoidcmp                         | btoidsortsupport                         | btoidvectorcmp                    | btoptions                      | btrecordcmp                    | btreltimecmp                       | btrescan                             |
+| btrestrpos                       | btrim                                    | bttext_pattern_cmp                | bttextcmp                      | bttextsortsupport              | bttidcmp                           | bttintervalcmp                       |
+| btvacuumcleanup                  | bytea_sortsupport                        | bytea_string_agg_finalfn          | bytea_string_agg_transfn       | byteacat                       | byteacmp                           | byteaeq                              |
+| byteage                          | byteagt                                  | byteain                           | byteale                        | bytealike                      | bytealt                            | byteane                              |
+| byteanlike                       | byteaout                                 | bytearecv                         | byteasend                      | cash_cmp                       | cash_div_cash                      | cash_div_flt4                        |
+| cash_div_flt8                    | cash_div_int2                            | cash_div_int4                     | cash_div_int8                  | cash_eq                        | cash_ge                            | cash_gt                              |
+| cash_in                          | cash_le                                  | cash_lt                           | cash_mi                        | cash_mul_flt4                  | cash_mul_flt8                      | cash_mul_int2                        |
+| cash_mul_int4                    | cash_mul_int8                            | cash_ne                           | cash_out                       | cash_pl                        | cash_recv                          | cash_send                            |
+| cashlarger                       | cashsmaller                              | cbrt                              | ceil                           | ceiling                        | center                             | char                                 |
+| char_length                      | character_length                         | chareq                            | charge                         | chargt                         | charin                             | charle                               |
+| charlt                           | charne                                   | charout                           | charrecv                       | charsend                       | chr                                | cideq                                |
+| cidin                            | cidout                                   | cidr                              | cidr_in                        | cidr_out                       | cidr_recv                          | cidr_send                            |
+| cidrecv                          | cidsend                                  | circle                            | circle_above                   | circle_add_pt                  | circle_below                       | circle_center                        |
+| circle_contain                   | circle_contain_pt                        | circle_contained                  | circle_distance                | circle_div_pt                  | circle_eq                          | circle_ge                            |
+| circle_gt                        | circle_in                                | circle_le                         | circle_left                    | circle_lt                      | circle_mul_pt                      | circle_ne                            |
+| circle_out                       | circle_overabove                         | circle_overbelow                  | circle_overlap                 | circle_overleft                | circle_overright                   | circle_recv                          |
+| circle_right                     | circle_same                              | circle_send                       | circle_sub_pt                  | clock_timestamp                | close_lb                           | close_ls                             |
+| close_lseg                       | close_pb                                 | close_pl                          | close_ps                       | close_sb                       | close_sl                           | col_description                      |
+| concat                           | concat_ws                                | contjoinsel                       | contsel                        | convert                        | convert_from                       | convert_to                           |
+| corr                             | cos                                      | cot                               | count                          | covar_pop                      | covar_samp                         | cstring_in                           |
+| cstring_out                      | cstring_recv                             | cstring_send                      | cume_dist                      | current_database               | current_query                      | current_schema                       |
+| xpath_exists                     | current_setting                          | current_user                      | currtid                        | currtid2                       | currval                            | cursor_to_xml                        |
+| cursor_to_xmlschema              | database_to_xml                          | database_to_xml_and_xmlschema     | database_to_xmlschema          | date                           | date_cmp                           | date_cmp_timestamp                   |
+| date_cmp_timestamptz             | date_eq                                  | date_eq_timestamp                 | date_eq_timestamptz            | date_ge                        | date_ge_timestamp                  | date_ge_timestamptz                  |
+| date_gt                          | date_gt_timestamp                        | date_gt_timestamptz               | date_in                        | date_larger                    | date_le                            | date_le_timestamp                    |
+| date_le_timestamptz              | date_lt                                  | date_lt_timestamp                 | date_lt_timestamptz            | date_mi                        | date_mi_interval                   | date_mii                             |
+| date_ne                          | date_ne_timestamp                        | date_ne_timestamptz               | date_out                       | date_pl_interval               | date_pli                           | date_recv                            |
+| date_send                        | date_smaller                             | date_sortsupport                  | daterange_canonical            | daterange_subdiff              | datetime_pl                        | datetimetz_pl                        |
+| dcbrt                            | decode                                   | defined                           | degrees                        | delete                         | dense_rank                         | dexp                                 |
+| diagonal                         | diameter                                 | dispell_init                      | dispell_lexize                 | dist_cpoly                     | dist_lb                            | dist_pb                              |
+| dist_pc                          | dist_pl                                  | dist_ppath                        | dist_ps                        | dist_sb                        | dist_sl                            | div                                  |
+| dlog1                            | dlog10                                   | domain_in                         | domain_recv                    | dpow                           | dround                             | dsimple_init                         |
+| dsimple_lexize                   | dsnowball_init                           | dsnowball_lexize                  | dsqrt                          | dsynonym_init                  | dsynonym_lexize                    | dtrunc                               |
+| each                             | enum_ne                                  | enum_out                          | enum_range                     | enum_recv                      | enum_send                          | enum_smaller                         |
+| eqjoinsel                        | eqsel                                    | euc_cn_to_mic                     | euc_cn_to_utf8                 | euc_jis_2004_to_shift_jis_2004 | euc_jis_2004_to_utf8               | euc_jp_to_mic                        |
+| euc_jp_to_sjis                   | euc_jp_to_utf8                           | euc_kr_to_mic                     | euc_kr_to_utf8                 | euc_tw_to_big5                 | euc_tw_to_mic                      | euc_tw_to_utf8                       |
+| every                            | exist                                    | exists_all                        | exists_any                     | exp                            | factorial                          | family                               |
+| fdw_handler_in                   | fdw_handler_out                          | fetchval                          | first_value                    | float4                         | float4_accum                       | float48div                           |
+| float48eq                        | float48ge                                | float48gt                         | float48le                      | float48lt                      | float48mi                          | float48mul                           |
+| float48ne                        | float48pl                                | float4abs                         | float4div                      | float4eq                       | float4ge                           | float4gt                             |
+| float4in                         | float4larger                             | float4le                          | float4lt                       | float4mi                       | float4mul                          | float4ne                             |
+| float4out                        | float4pl                                 | float4recv                        | float4send                     | float4smaller                  | float4um                           | float4up                             |
+| float8                           | float8_accum                             | float8_avg                        | float8_collect                 | float8_corr                    | float8_covar_pop                   | float8_covar_samp                    |
+| float8_regr_accum                | float8_regr_avgx                         | float8_regr_avgy                  | float8_regr_collect            | float8_regr_intercept          | float8_regr_r2                     | float8_regr_slope                    |
+| float8_regr_sxx                  | float8_regr_sxy                          | float8_regr_syy                   | float8_stddev_pop              | float8_stddev_samp             | float8_var_pop                     | float8_var_samp                      |
+| float84div                       | float84eq                                | float84ge                         | float84gt                      | float84le                      | float84lt                          | float84mi                            |
+| float84mul                       | float84ne                                | float84pl                         | float8abs                      | float8div                      | float8eq                           | float8ge                             |
+| float8gt                         | float8in                                 | float8larger                      | float8le                       | float8lt                       | float8mi                           | float8mul                            |
+| float8ne                         | float8out                                | float8pl                          | float8recv                     | float8send                     | float8smaller                      | float8um                             |
+| float8up                         | floor                                    | flt4_mul_cash                     | flt8_mul_cash                  | fmgr_c_validator               | fmgr_internal_validator            | fmgr_sql_validator                   |
+| format                           | format_type                              | gb18030_to_utf8                   | gbk_to_utf8                    | generate_series                | generate_subscripts                | get_bit                              |
+| get_byte                         | get_current_ts_config                    | -                                 | -                              | gin_clean_pending_list         | gin_cmp_prefix                     | gin_cmp_tslexeme                     |
+| gin_extract_tsquery              | gin_extract_tsvector                     | gin_tsquery_consistent            | gin_tsquery_triconsistent      | ginarrayconsistent             | ginarrayextract                    | ginarraytriconsistent                |
+| ginbeginscan                     | ginbuild                                 | ginbuildempty                     | ginbulkdelete                  | gincostestimate                | ginendscan                         | gingetbitmap                         |
+| gininsert                        | ginmarkpos                               | ginoptions                        | ginqueryarrayextract           | ginrescan                      | ginrestrpos                        | ginvacuumcleanup                     |
+| gist_box_compress                | gist_box_consistent                      | gist_box_decompress               | gist_box_penalty               | gist_box_picksplit             | gist_box_same                      | gist_box_union                       |
+| gist_circle_compress             | gist_circle_consistent                   | gist_point_compress               | gist_point_consistent          | gist_point_distance            | gist_poly_compress                 | gist_poly_consistent                 |
+| gistbeginscan                    | gistbuild                                | gistbuildempty                    | gistbulkdelete                 | gistcostestimate               | gistendscan                        | gistgetbitmap                        |
+| gistgettuple                     | gistinsert                               | gistmarkpos                       | gistoptions                    | gistrescan                     | gistrestrpos                       | gistvacuumcleanup                    |
+| gtsquery_compress                | gtsquery_consistent                      | gtsquery_decompress               | gtsquery_penalty               | gtsquery_picksplit             | gtsquery_same                      | gtsquery_union                       |
+| gtsvector_compress               | gtsvector_consistent                     | gtsvector_decompress              | gtsvector_penalty              | gtsvector_picksplit            | gtsvector_same                     | gtsvector_union                      |
+| gtsvectorin                      | gtsvectorout                             | has_tablespace_privilege          | has_type_privilege             | hash_aclitem                   | hashbeginscan                      | hashbuild                            |
+| hashbuildempty                   | hashbulkdelete                           | hashcostestimate                  | hashendscan                    | hashgetbitmap                  | hashgettuple                       | hashinsert                           |
+| hashint2vector                   | hashint4                                 | hashint8                          | hashmacaddr                    | hashmarkpos                    | hashname                           | hashoid                              |
+| hashoidvector                    | hashoptions                              | hashrescan                        | hashrestrpos                   | hashtext                       | hashvacuumcleanup                  | hashvarlena                          |
+| host                             | hostmask                                 | iclikejoinsel                     | iclikesel                      | icnlikejoinsel                 | icnlikesel                         | icregexeqjoinsel                     |
+| icregexeqsel                     | icregexnejoinsel                         | icregexnesel                      | inet_client_addr               | inet_client_port               | inet_in                            | inet_out                             |
+| inet_recv                        | inet_send                                | inet_server_addr                  | inet_server_port               | inetand                        | inetmi                             | inetmi_int8                          |
+| inetnot                          | inetor                                   | inetpl                            | initcap                        | int2_accum                     | int2_avg_accum                     | int2_mul_cash                        |
+| int2_sum                         | int24div                                 | int24eq                           | int24ge                        | int24gt                        | int24le                            | int24lt                              |
+| int24mi                          | int24mul                                 | int24ne                           | int24pl                        | int28div                       | int28eq                            | int28ge                              |
+| int28gt                          | int28le                                  | int28lt                           | int28mi                        | int28mul                       | int28ne                            | int28pl                              |
+| int2abs                          | int2and                                  | int2div                           | int2eq                         | int2ge                         | int2gt                             | int2in                               |
+| int2larger                       | int2le                                   | int2lt                            | int2mi                         | int2mod                        | int2mul                            | int2ne                               |
+| int2not                          | int2or                                   | int2out                           | int2pl                         | int2recv                       | int2send                           | int2shl                              |
+| int2shr                          | int2smaller                              | int2um                            | int2up                         | int2vectoreq                   | int2vectorin                       | int2vectorout                        |
+| int2vectorrecv                   | int2vectorsend                           | int2xor                           | int4_accum                     | int4_avg_accum                 | int4_mul_cash                      | int4_sum                             |
+| int42div                         | int42eq                                  | int42ge                           | int42gt                        | int42le                        | int42lt                            | int42mi                              |
+| int42mul                         | int42ne                                  | int42pl                           | int48div                       | int48eq                        | int48ge                            | int48gt                              |
+| int48le                          | int48lt                                  | int48mi                           | int48mul                       | int48ne                        | int48pl                            | int4abs                              |
+| int4and                          | int4div                                  | int4eq                            | int4ge                         | int4gt                         | int4in                             | int4inc                              |
+| int4larger                       | int4le                                   | int4lt                            | int4mi                         | int4mod                        | int4mul                            | int4ne                               |
+| int4not                          | int4or                                   | int4out                           | int4pl                         | int4range                      | int4range_canonical                | int4range_subdiff                    |
+| int4recv                         | int4send                                 | int4shl                           | int4shr                        | int4smaller                    | int4um                             | int4up                               |
+| int4xor                          | int8                                     | int8_avg                          | int8_avg_accum                 | int8_avg_collect               | int8_mul_cash                      | int8_sum                             |
+| int8_sum_to_int8                 | int8_accum                               | int82div                          | int82eq                        | int82ge                        | int82gt                            | int82le                              |
+| int82lt                          | int82mi                                  | int82mul                          | int82ne                        | int82pl                        | int84div                           | int84eq                              |
+| int84ge                          | int84gt                                  | int84le                           | int84lt                        | int84mi                        | int84mul                           | int84ne                              |
+| int84pl                          | int8abs                                  | int8and                           | int8div                        | int8eq                         | int8ge                             | int8gt                               |
+| int8in                           | int8inc                                  | int8inc_any                       | int8inc_float8_float8          | int8larger                     | int8le                             | int8lt                               |
+| int8mi                           | int8mod                                  | int8mul                           | int8ne                         | int8not                        | int8or                             | int8out                              |
+| int8pl                           | int8pl_inet                              | int8range                         | int8range_canonical            | int8range_subdiff              | int8recv                           | int8send                             |
+| int8shl                          | int8shr                                  | int8smaller                       | int8um                         | int8up                         | int8xor                            | integer_pl_date                      |
+| inter_lb                         | inter_sb                                 | inter_sl                          | internal_in                    | internal_out                   | interval                           | interval_accum                       |
+| interval_avg                     | interval_cmp                             | interval_collect                  | interval_div                   | interval_eq                    | interval_ge                        | interval_gt                          |
+| interval_hash                    | interval_in                              | interval_larger                   | interval_le                    | interval_lt                    | interval_mi                        | interval_mul                         |
+| interval_ne                      | interval_out                             | interval_pl                       | interval_pl_date               | interval_pl_time               | interval_pl_timestamp              | interval_pl_timestamptz              |
+| interval_pl_timetz               | interval_recv                            | interval_send                     | interval_smaller               | interval_transform             | interval_um                        | intervaltypmodin                     |
+| intervaltypmodout                | intinterval                              | isexists                          | ishorizontal                   | iso_to_koi8r                   | iso_to_mic                         | iso_to_win1251                       |
+| iso_to_win866                    | iso8859_1_to_utf8                        | iso8859_to_utf8                   | isparallel                     | isperp                         | isvertical                         | johab_to_utf8                        |
+| json_in                          | json_out                                 | json_recv                         | json_send                      | justify_days                   | justify_hours                      | justify_interval                     |
+| koi8r_to_iso                     | koi8r_to_mic                             | koi8r_to_utf8                     | koi8r_to_win1251               | koi8r_to_win866                | koi8u_to_utf8                      | language_handler_in                  |
+| language_handler_out             | latin1_to_mic                            | latin2_to_mic                     | latin2_to_win1250              | latin3_to_mic                  | latin4_to_mic                      | like_escape                          |
+| likejoinsel                      | likesel                                  | line                              | line_distance                  | line_eq                        | line_horizontal                    | line_in                              |
+| line_interpt                     | line_intersect                           | line_out                          | line_parallel                  | line_perp                      | line_recv                          | line_send                            |
+| line_vertical                    | ln                                       | lo_close                          | lo_creat                       | lo_create                      | lo_export                          | lo_import                            |
+| lo_lseek                         | lo_open                                  | lo_tell                           | lo_truncate                    | lo_unlink                      | log                                | loread                               |
+| lower                            | lower_inc                                | lower_inf                         | lowrite                        | lpad                           | lseg                               | lseg_center                          |
+| lseg_distance                    | lseg_eq                                  | lseg_ge                           | lseg_gt                        | lseg_horizontal                | lseg_in                            | lseg_interpt                         |
+| lseg_intersect                   | lseg_le                                  | lseg_length                       | lseg_lt                        | lseg_ne                        | lseg_out                           | lseg_parallel                        |
+| lseg_perp                        | lseg_recv                                | lseg_send                         | lseg_vertical                  | ltrim                          | macaddr_and                        | macaddr_cmp                          |
+| macaddr_eq                       | macaddr_ge                               | macaddr_gt                        | macaddr_in                     | macaddr_le                     | macaddr_lt                         | macaddr_ne                           |
+| macaddr_not                      | macaddr_or                               | macaddr_out                       | macaddr_recv                   | macaddr_send                   | makeaclitem                        | masklen                              |
+| max                              | md5                                      | mic_to_big5                       | mic_to_euc_cn                  | mic_to_euc_jp                  | mic_to_euc_kr                      | mic_to_euc_tw                        |
+| mic_to_iso                       | mic_to_koi8r                             | mic_to_latin1                     | mic_to_latin2                  | mic_to_latin3                  | mic_to_latin4                      | mic_to_sjis                          |
+| mic_to_win1250                   | mic_to_win1251                           | mic_to_win866                     | min                            | mktinterval                    | money                              | mul_d_interval                       |
+| name                             | nameeq                                   | namege                            | namegt                         | nameiclike                     | nameicnlike                        | nameicregexeq                        |
+| nameicregexne                    | namein                                   | namele                            | namelike                       | namelt                         | namene                             | namenlike                            |
+| nameout                          | namerecv                                 | nameregexeq                       | nameregexne                    | namesend                       | neqjoinsel                         | neqsel                               |
+| network_cmp                      | network_eq                               | network_ge                        | network_gt                     | network_le                     | network_lt                         | network_ne                           |
+| network_sub                      | network_subeq                            | network_sup                       | network_supeq                  | nlikejoinsel                   | nlikesel                           | numeric                              |
+| numeric_abs                      | numeric_accum                            | numeric_add                       | numeric_avg                    | numeric_avg_accum              | numeric_avg_collect                | numeric_cmp                          |
+| numeric_collect                  | numeric_div                              | numeric_div_trunc                 | numeric_eq                     | numeric_exp                    | numeric_fac                        | numeric_ge                           |
+| numeric_gt                       | numeric_in                               | numeric_inc                       | numeric_larger                 | numeric_le                     | numeric_ln                         | numeric_log                          |
+| numeric_lt                       | numeric_mod                              | numeric_mul                       | numeric_ne                     | numeric_out                    | numeric_power                      | numeric_recv                         |
+| numeric_send                     | numeric_smaller                          | numeric_sortsupport               | numeric_sqrt                   | numeric_stddev_pop             | numeric_stddev_samp                | numeric_sub                          |
+| numeric_transform                | numeric_uminus                           | numeric_uplus                     | numeric_var_pop                | numeric_var_samp               | numerictypmodin                    | numerictypmodout                     |
+| numrange_subdiff                 | oid                                      | oideq                             | oidge                          | oidgt                          | oidin                              | oidlarger                            |
+| oidle                            | oidlt                                    | oidne                             | oidout                         | oidrecv                        | oidsend                            | oidsmaller                           |
+| oidvectoreq                      | oidvectorge                              | oidvectorgt                       | oidvectorin                    | oidvectorle                    | oidvectorlt                        | oidvectorne                          |
+| oidvectorout                     | oidvectorrecv                            | oidvectorsend                     | oidvectortypes                 | on_pb                          | on_pl                              | on_ppath                             |
+| on_ps                            | on_sb                                    | on_sl                             | opaque_in                      | opaque_out                     | ordered_set_transition             | overlaps                             |
+| overlay                          | path                                     | path_add                          | path_add_pt                    | path_center                    | path_contain_pt                    | path_distance                        |
+| path_div_pt                      | path_in                                  | path_inter                        | path_length                    | path_mul_pt                    | path_n_eq                          | path_n_ge                            |
+| path_n_gt                        | path_n_le                                | path_n_lt                         | path_npoints                   | path_out                       | path_recv                          | path_send                            |
+| path_sub_pt                      | percentile_cont                          | percentile_cont_float8_final      | percentile_cont_interval_final | pg_char_to_encoding            | pg_cursor                          | pg_encoding_max_length               |
+| pg_encoding_to_char              | pg_extension_config_dump                 | -                                 | -                              | pg_node_tree_in                | pg_node_tree_out                   | pg_node_tree_recv                    |
+| pg_node_tree_send                | pg_prepared_statement                    | pg_prepared_xact                  | -                              | -                              | pg_show_all_settings               | pg_stat_get_bgwriter_stat_reset_time |
+| pg_stat_get_buf_fsync_backend    | pg_stat_get_checkpoint_sync_time         | pg_stat_get_checkpoint_write_time | pg_stat_get_db_blk_read_time   | pg_stat_get_db_blk_write_time  | pg_stat_get_db_conflict_all        | pg_stat_get_db_conflict_bufferpin    |
+| pg_stat_get_db_conflict_snapshot | pg_stat_get_db_conflict_startup_deadlock | pg_switch_xlog                    | xpath                          | pg_timezone_abbrevs            | pg_timezone_names                  | -                                    |
+| plpgsql_call_handler             | plpgsql_inline_handler                   | plpgsql_validator                 | point_above                    | point_add                      | point_below                        | point_distance                       |
+| point_div                        | point_eq                                 | point_horiz                       | point_in                       | point_left                     | point_mul                          | point_ne                             |
+| point_out                        | point_recv                               | point_right                       | point_send                     | point_sub                      | point_vert                         | poly_above                           |
+| poly_below                       | poly_center                              | poly_contain                      | poly_contain_pt                | poly_contained                 | poly_distance                      | poly_in                              |
+| poly_left                        | poly_npoints                             | poly_out                          | poly_overabove                 | poly_overbelow                 | poly_overlap                       | poly_overleft                        |
+| poly_overright                   | poly_recv                                | poly_right                        | poly_same                      | poly_send                      | polygon                            | position                             |
+| positionjoinsel                  | positionsel                              | postgresql_fdw_validator          | pow                            | power                          | prsd_end                           | prsd_headline                        |
+| prsd_lextype                     | prsd_nexttoken                           | prsd_start                        | pt_contained_circle            | pt_contained_poly              | query_to_xml                       | query_to_xml_and_xmlschema           |
+| query_to_xmlschema               | quote_ident                              | quote_literal                     | quote_nullable                 | radians                        | radius                             | random                               |
+| range_adjacent                   | range_after                              | range_before                      | range_cmp                      | range_contained_by             | range_contains                     | range_contains_elem                  |
+| range_eq                         | range_ge                                 | range_gist_compress               | range_gist_consistent          | range_gist_decompress          | range_gist_penalty                 | range_gist_picksplit                 |
+| range_gist_same                  | range_gist_union                         | range_gt                          | range_in                       | range_intersect                | range_le                           | range_lt                             |
+| range_minus                      | range_ne                                 | range_out                         | range_overlaps                 | range_overleft                 | range_overright                    | range_recv                           |
+| range_send                       | range_typanalyze                         | range_union                       | rank                           | record_eq                      | record_ge                          | record_gt                            |
+| record_in                        | record_le                                | record_lt                         | record_ne                      | record_out                     | record_recv                        | record_send                          |
+| regclass                         | regclassin                               | regclassout                       | regclassrecv                   | regclasssend                   | regconfigin                        | regconfigout                         |
+| regconfigrecv                    | regconfigsend                            | regdictionaryin                   | regdictionaryout               | regdictionaryrecv              | regdictionarysend                  | regexeqjoinsel                       |
+| regexeqsel                       | regexnejoinsel                           | regexnesel                        | regexp_matches                 | regexp_replace                 | regexp_split_to_array              | regexp_split_to_table                |
+| regoperatorin                    | regoperatorout                           | regoperatorrecv                   | regoperatorsend                | regoperin                      | regoperout                         | regoperrecv                          |
+| regopersend                      | regprocedurein                           | regprocedureout                   | regprocedurerecv               | regproceduresend               | regprocin                          | regprocout                           |
+| regprocrecv                      | regprocsend                              | regr_avgx                         | regr_avgy                      | regr_count                     | regr_intercept                     | regr_r2                              |
+| regr_slope                       | regr_sxx                                 | regr_sxy                          | regr_syy                       | regtypein                      | regtypeout                         | regtyperecv                          |
+| regtypesend                      | reltime                                  | reltimeeq                         | reltimege                      | reltimegt                      | reltimein                          | reltimele                            |
+| reltimelt                        | reltimene                                | reltimeout                        | reltimerecv                    | reltimesend                    | repeat                             | replace                              |
+| reverse                          | RI_FKey_cascade_del                      | RI_FKey_cascade_upd               | RI_FKey_check_ins              | RI_FKey_check_upd              | RI_FKey_noaction_del               | RI_FKey_noaction_upd                 |
+| RI_FKey_restrict_del             | RI_FKey_restrict_upd                     | RI_FKey_setdefault_del            | RI_FKey_setdefault_upd         | RI_FKey_setnull_del            | RI_FKey_setnull_upd                | right                                |
+| round                            | row_number                               | row_to_json                       | rpad                           | rtrim                          | scalargtjoinsel                    | scalargtsel                          |
+| scalarltjoinsel                  | scalarltsel                              | schema_to_xml                     | schema_to_xml_and_xmlschema    | schema_to_xmlschema            | session_user                       | set_bit                              |
+| set_byte                         | set_config                               | set_masklen                       | shift_jis_2004_to_euc_jis_2004 | shift_jis_2004_to_utf8         | sjis_to_euc_jp                     | sjis_to_mic                          |
+| sjis_to_utf8                     | smgrin                                   | smgrout                           | spg_kd_choose                  | spg_kd_config                  | spg_kd_inner_consistent            | spg_kd_picksplit                     |
+| spg_quad_choose                  | spg_quad_config                          | spg_quad_inner_consistent         | spg_quad_leaf_consistent       | spg_quad_picksplit             | spg_text_choose                    | spg_text_config                      |
+| spg_text_inner_consistent        | spg_text_leaf_consistent                 | spg_text_picksplit                | spgbeginscan                   | spgbuild                       | spgbuildempty                      | spgbulkdelete                        |
+| spgcanreturn                     | spgcostestimate                          | spgendscan                        | spggetbitmap                   | spggettuple                    | spginsert                          | spgmarkpos                           |
+| spgoptions                       | spgrescan                                | spgrestrpos                       | spgvacuumcleanup               | stddev                         | stddev_pop                         | stddev_samp                          |
+| string_agg                       | string_agg_finalfn                       | string_agg_transfn                | strip                          | sum                            | suppress_redundant_updates_trigger | table_to_xml                         |
+| table_to_xml_and_xmlschema       | table_to_xmlschema                       | tan                               | text                           | text_ge                        | text_gt                            | text_larger                          |
+| text_le                          | text_lt                                  | text_pattern_ge                   | text_pattern_gt                | text_pattern_le                | text_pattern_lt                    | text_smaller                         |
+| textanycat                       | textcat                                  | texteq                            | texticlike                     | texticnlike                    | texticregexeq                      | texticregexne                        |
+| textin                           | textlike                                 | textne                            | textnlike                      | textout                        | textrecv                           | textregexeq                          |
+| textregexne                      | textsend                                 | thesaurus_init                    | thesaurus_lexize               | tideq                          | tidge                              | tidgt                                |
+| tidin                            | tidlarger                                | tidle                             | tidlt                          | tidne                          | tidout                             | tidrecv                              |
+| tidsend                          | tidsmaller                               | time                              | time_cmp                       | time_eq                        | time_ge                            | time_gt                              |
+| time_hash                        | time_in                                  | time_larger                       | time_le                        | time_lt                        | time_mi_interval                   | time_mi_time                         |
+| time_ne                          | time_out                                 | time_pl_interval                  | time_recv                      | time_send                      | time_smaller                       | time_transform                       |
+| timedate_pl                      | timemi                                   | timepl                            | timestamp                      | timestamp_cmp                  | timestamp_cmp_date                 | timestamp_cmp_timestamptz            |
+| timestamp_eq                     | timestamp_eq_date                        | timestamp_eq_timestamptz          | timestamp_ge                   | timestamp_ge_date              | timestamp_ge_timestamptz           | timestamp_gt                         |
+| timestamp_gt_date                | timestamp_gt_timestamptz                 | timestamp_hash                    | timestamp_in                   | timestamp_larger               | timestamp_le                       | timestamp_le_date                    |
+| timestamp_le_timestamptz         | timestamp_lt                             | timestamp_lt_date                 | timestamp_lt_timestamptz       | timestamp_mi                   | timestamp_mi_interval              | timestamp_ne                         |
+| timestamp_ne_date                | timestamp_ne_timestamptz                 | timestamp_out                     | timestamp_pl_interval          | timestamp_recv                 | timestamp_send                     | timestamp_smaller                    |
+| timestamp_sortsupport            | timestamp_transform                      | timestamptypmodin                 | timestamptypmodout             | timestamptz                    | timestamptz_cmp                    | timestamptz_cmp_date                 |
+| timestamptz_cmp_timestamp        | timestamptz_eq                           | timestamptz_eq_date               | timestamptz_eq_timestamp       | timestamptz_ge                 | timestamptz_ge_date                | timestamptz_ge_timestamp             |
+| timestamptz_gt                   | timestamptz_gt_date                      | timestamptz_gt_timestamp          | timestamptz_in                 | timestamptz_larger             | timestamptz_le                     | timestamptz_le_date                  |
+| timestamptz_le_timestamp         | timestamptz_lt                           | timestamptz_lt_date               | timestamptz_lt_timestamp       | timestamptz_mi                 | timestamptz_mi_interval            | timestamptz_ne                       |
+| timestamptz_ne_date              | timestamptz_ne_timestamp                 | timestamptz_out                   | timestamptz_pl_interval        | timestamptz_recv               | timestamptz_send                   | timestamptz_smaller                  |
+| timestamptztypmodin              | timestamptztypmodout                     | timetypmodin                      | timetypmodout                  | timetz                         | timetz_cmp                         | timetz_eq                            |
+| timetz_ge                        | timetz_gt                                | timetz_hash                       | timetz_in                      | timetz_larger                  | timetz_le                          | timetz_lt                            |
+| timetz_mi_interval               | timetz_ne                                | timetz_out                        | timetz_pl_interval             | timetz_recv                    | timetz_send                        | timetz_smaller                       |
+| timetzdate_pl                    | timetztypmodin                           | timetztypmodout                   | timezone (2069)                | timezone (1159)                | timezone (2037)                    | timezone (2070)                      |
+| timezone (1026)                  | timezone (2038)                          | tintervalct                       | tintervaleq                    | tintervalge                    | tintervalgt                        | tintervalin                          |
+| tintervalle                      | tintervalleneq                           | tintervallenge                    | tintervallengt                 | tintervallenle                 | tintervallenlt                     | tintervallenne                       |
+| tintervallt                      | tintervalne                              | tintervalout                      | tintervalov                    | tintervalrecv                  | tintervalsame                      | tintervalsend                        |
+| tintervalstart                   | to_ascii (1845)                          | to_ascii (1847)                   | to_ascii (1846)                | trigger_in                     | trigger_out                        | ts_match_qv                          |
+| ts_match_tq                      | ts_match_tt                              | ts_match_vq                       | ts_rank                        | ts_rank_cd                     | ts_rewrite                         | ts_stat                              |
+| ts_token_type                    | ts_typanalyze                            | tsmatchjoinsel                    | tsmatchsel                     | tsq_mcontained                 | tsq_mcontains                      | tsquery_and                          |
+| tsquery_cmp                      | tsquery_eq                               | tsquery_ge                        | tsquery_gt                     | tsquery_le                     | tsquery_lt                         | tsquery_ne                           |
+| tsquery_not                      | tsquery_or                               | tsqueryin                         | tsqueryout                     | tsqueryrecv                    | tsquerysend                        | tsrange                              |
+| tsrange_subdiff                  | tstzrange                                | tstzrange_subdiff                 | tsvector_cmp                   | tsvector_concat                | tsvector_eq                        | tsvector_ge                          |
+| tsvector_gt                      | tsvector_le                              | tsvector_lt                       | tsvector_ne                    | tsvector_update_trigger        | tsvector_update_trigger_column     | tsvectorin                           |
+| tsvectorout                      | tsvectorrecv                             | tsvectorsend                      | txid_current                   | txid_current_snapshot          | txid_snapshot_in                   | txid_snapshot_out                    |
+| txid_snapshot_recv               | txid_snapshot_send                       | txid_snapshot_xip                 | txid_snapshot_xmax             | txid_snapshot_xmin             | txid_visible_in_snapshot           | uhc_to_utf8                          |
+| unique_key_recheck               | unknownin                                | unknownout                        | unknownrecv                    | unknownsend                    | unnest                             | utf8_to_big5                         |
+| utf8_to_euc_cn                   | utf8_to_euc_jis_2004                     | utf8_to_euc_jp                    | utf8_to_euc_kr                 | utf8_to_euc_tw                 | utf8_to_gb18030                    | utf8_to_gbk                          |
+| utf8_to_iso8859                  | utf8_to_iso8859_1                        | utf8_to_johab                     | utf8_to_koi8r                  | utf8_to_koi8u                  | utf8_to_shift_jis_2004             | utf8_to_sjis                         |
+| utf8_to_uhc                      | utf8_to_win                              | uuid_cmp                          | uuid_eq                        | uuid_ge                        | uuid_gt                            | uuid_hash                            |
+| uuid_in                          | uuid_le                                  | uuid_lt                           | uuid_ne                        | uuid_out                       | uuid_recv                          | uuid_send                            |
+| var_pop                          | var_samp                                 | varbit                            | varbit_in                      | varbit_out                     | varbit_recv                        | varbit_send                          |
+| varbit_transform                 | varbitcmp                                | varbiteq                          | varbitge                       | varbitgt                       | varbitle                           | varbitlt                             |
+| varbitne                         | varbittypmodin                           | varbittypmodout                   | varchar                        | varchar_transform              | varcharin                          | varcharout                           |
+| varcharrecv                      | varcharsend                              | varchartypmodin                   | varchartypmodout               | variance                       | void_in                            | void_out                             |
+| void_recv                        | void_send                                | win_to_utf8                       | win1250_to_latin2              | win1250_to_mic                 | win1251_to_iso                     | win1251_to_koi8r                     |
+| win1251_to_mic                   | win1251_to_win866                        | win866_to_iso                     | win866_to_koi8r                | win866_to_mic                  | win866_to_win1251                  | xideq                                |
+| xideqint4                        | xidin                                    | xidout                            | xidrecv                        | xidsend                        | xml                                | xml_in                               |
+| xml_is_well_formed               | xml_is_well_formed_content               | xml_is_well_formed_document       | xml_out                        | xml_recv                       | xml_send                           | xmlagg                               |
+| xmlcomment                       | xmlconcat2                               | xmlexists                         | xmlvalidate                    | pg_notify                      | pg_stat_get_wal_receiver           | -                                    |
+
+The following table lists the functions used by MogDB Kernel to implement internal system functions. You are not advised to use these functions. If you need to use them, contact Enmo technical support.
+
+- pv_compute_pool_workload()
+
+    Description: Provides the current load information about computing Node Groups on cloud.
+
+    Return type: record
+
+- locktag_decode(locktag text)
+
+    Description: Parses lock details from  **locktag**.
+
+    Return type: text
+
+- smgreq(a smgr, b smgr)
+
+  Description: Compares two smgrs to check whether they are the same.
+
+  Parameter: smgr, smgr
+  Return type: Boolean
+
+- smgrne(a smgr, b smgr)
+
+  Description: Checks whether the two smgrs are different.
+
+  Parameter: smgr, smgr
+
+  Return type: Boolean
+
+- xidin4
+
+  Description: Inputs a 4-byte xid.
+
+  Parameter: cstring
+
+  Return type: xid32
+
+- set_hashbucket_info
+
+  Description: Sets hash bucket information.
+
+  Parameter: text
+
+  Return type: Boolean
+
+- hs_concat
+
+  Description: Concatenates two pieces of hstore data.
+
+  Parameter: hstore, hstore
+
+  Return type: hstore
+
+- hs_contained
+
+  Description: Determines whether two hstore data records are included. The return value is of the Boolean type.
+
+  Parameter: hstore, hstore
+
+  Return type: Boolean
+
+- hs_contains
+
+  Description: Determines whether two hstore data records are included. The return value is of the Boolean type.
+
+  Parameter: hstore, hstore
+
+  Return type: Boolean
+
+- hstore
+
+  Description: Converts parameters to the hstore type.
+
+  Parameter: text, text
+
+  Return type: hstore
+
+- hstore_in
+
+  Description: Receives hstore data in string format.
+
+  Parameter: cstring
+
+  Return type: hstore
+
+- hstore_out
+
+  Description: Sends hstore data in string format.
+
+  Parameter: hstore
+
+  Return type: cstring
+
+- hstore_send
+
+  Description: Sends hstore data in bytea format.
+
+  Parameter: hstore
+
+  Return type: bytea
+
+- hstore_to_array
+
+  Description: Sends hstore data in text array format.
+
+  Parameter: hstore
+
+  Return type: text[]
+
+- hstore_to_matrix
+
+  Description: Sends hstore data in text array format.
+
+  Parameter: hstore
+
+  Return type: text[]
+
+- hstore_version_diag
+
+  Description: Sends hstore data in integer array format.
+
+  Parameter: hstore
+
+  Return type: integer
+
+- int1send
+
+  Description: Packs unsigned 1-byte integers into the internal data buffer stream.
+
+  Parameter: tinyint
+
+  Return type: bytea
+
+- isdefined
+
+  Description: Checks whether a specified key exists.
+
+  Parameter: hstore, text
+
+  Return type: Boolean
+
+- listagg
+
+  Description: Specifies aggregate functions of the list type.
+
+  Parameter: smallint, text
+
+  Return type: text
+
+- log_fdw_validator
+
+  Description: Specifies validation functions.
+
+  Parameter: text[], oid
+
+  Return type: void
+
+- nvarchar2typmodin
+
+  Description: Obtains the typmod information of the varchar type.
+
+  Parameter: cstring[]
+
+  Return type: integer
+
+- nvarchar2typmodout
+
+  Description: Obtains the typmod information of the varchar type, constructs a character string, and returns the character string.
+
+  Parameter: integer
+
+  Return type: cstring
+
+- read_disable_conn_file
+
+  Description: Reads forbidden connection files.
+
+  Parameter: nan
+
+  Return type: disconn_mode text, disconn_host text, disconn_port text, local_host text, local_port text, redo_finished text
+
+- regex_like_m
+
+  Description: Specifies the regular expression match, which is used to determine whether a character string complies with a specified regular expression.
+
+  Parameter: text, text
+
+  Return type: Boolean
+
+- update_pgjob
+
+  Description: Updates a job.
+
+  Parameter: bigint, "char", bigint, timestamp without time zone, timestamp without time zone, timestamp without time zone, timestamp without time zone, timestamp without time zone, smallint
+
+  Return type: void
+
+- enum_cmp
+
+  Description: Specifies the enumeration comparison function, which is used to determine whether two enumeration classes are equal and determine their relative sizes.
+
+  Parameter: anyenum, anyenum
+
+  Return type: integer
+
+- enum_eq
+
+  Description: Specifies the enumeration comparison function, which is used to implement the equal sign (=).
+
+  Parameter: anyenum, anyenum
+
+  Return type: Boolean
+
+- enum_first
+
+  Description: Returns the first element in the enumeration class.
+
+  Parameter: anyenum
+
+  Return type: anyenum
+
+- enum_ge
+
+  Description: Specifies the enumeration comparison function, which is used to implement the greater-than sign (\>) and equal sign (=).
+
+  Parameter: anyenum, anyenum
+
+  Return type: Boolean
+
+- enum_gt
+
+  Description: Specifies the enumeration comparison function, which is used to implement the greater-than sign (\>).
+
+  Parameter: anyenum, anyenum
+
+  Return type: Boolean
+
+- enum_in
+
+  Description: Specifies the enumeration comparison function, which is used to determine whether an element is in an enumeration class.
+
+  Parameter: cstring, oid
+
+  Return type: anyenum
+
+- enum_larger
+
+  Description: Specifies the enumeration comparison function, which is used to implement the greater-than sign (\>).
+
+  Parameter: anyenum, anyenum
+
+  Return type: anyenum
+
+- enum_last
+
+  Description: Returns the last element in the enumeration class.
+
+  Parameter: anyenum
+
+  Return type: anyenum
+
+- enum_le
+
+  Description: Specifies the enumeration comparison function, which is used to implement the less-than sign (<) and equal sign (=).
+
+  Parameter: anyenum, anyenum
+
+  Return type: Boolean
+
+- enum_lt
+
+  Description: Specifies the enumeration comparison function, which is used to implement the less-than sign (<).
+
+  Parameter: anyenum, anyenum
+
+  Return type: Boolean
+
+- enum_smaller
+
+  Description: Specifies the enumeration comparison function, which is used to implement the less-than sign (<).
+
+  Parameter: anyenum, anyenum
+
+  Return type: Boolean
+
+- node_oid_name
+
+  Description: Not supported.
+
+  Parameter: oid
+
+  Return type: cstring
+
+- pg_buffercache_pages
+
+  Description: Reads data from the shared buffer.
+
+  Parameter: nan
+
+  Return type: bufferid integer, relfilenode oid, bucketid smallint, reltablespace oid, reldatabase oid, relforknumber smallint, relblocknumber bigint, isdirty boolean, usage_count smallint
+
+- pg_check_xidlimit
+
+  Description: Checks whether nextxid is greater than or equal to xidwarnlimit.
+
+  Parameter: nan
+
+  Return type: Boolean
+
+- pg_comm_delay
+
+  Description: Displays the delay status of the communication library of a single DN.
+
+  Parameter: nan
+
+  Return type: text, text, integer, integer, integer, integer
+
+- pg_comm_recv_stream
+
+  Description: Displays the receiving stream status of all communication libraries on a single DN.
+
+  Parameter: nan
+
+  Return type: text, bigint, text, bigint, integer, integer, integer, text, bigint, integer, integer, integer, bigint, bigint, bigint, bigint, bigint
+
+- pg_comm_send_stream
+
+  Description: Displays the sending stream status of all communication libraries on a single DN.
+
+  Parameter: nan
+
+  Return type: text, bigint, text, bigint, integer, integer, integer, text, bigint, integer, integer, integer, bigint, bigint, bigint, bigint, bigint
+
+- pg_comm_status
+
+  Description: Displays the communication status of a single DN.
+
+  Parameter: nan
+
+  Return type: text, integer, integer, bigint, bigint, bigint, bigint, bigint, integer, integer, integer, integer, integer
+
+- pg_log_comm_status
+
+  Description: Prints some logs on the DN.
+
+  Parameter: nan
+
+  Return type: Boolean
+
+- pg_parse_clog
+
+  Description: Parses clog to obtain the status of xid.
+
+  Parameter: nan
+
+  Return type: xid xid, status text
+
+- pg_pool_ping
+
+  Description: Sets PoolerPing.
+
+  Parameter: Boolean
+
+  Return type: SETOF boolean
+
+- pg_resume_bkp_flag
+
+  Description: Obtains the delay xlong flag for backup and restoration.
+
+  Parameter: slot_name name
+
+  Return type: start_backup_flag boolean, to_delay boolean, ddl_delay_recycle_ptr text, rewind_time text
+
+- psortoptions
+
+  Description: Returns the psort attribute.
+
+  Parameter: text[], boolean
+
+  Return type: bytea
+
+- xideq4
+
+  Description: Compares two values of the xid type to check whether they are the same.
+
+  Parameter: xid32, xid32
+
+  Return type: Boolean
+
+- xideqint8
+
+  Description: Compares values of the xid type and int8 type to check whether they are the same.
+
+  Parameter: xid, bigint
+
+  Return type: Boolean
+
+- xidlt
+
+  Description: Returns whether xid1 < xid2 is true.
+
+  Parameter: xid, xid
+
+  Return type: Boolean
+
+- xidlt4
+
+  Description: Returns whether xid1 < xid2 is true.
+
+  Parameter: xid32, xid32
+
+  Return type: Boolean
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/29.1-dynamic-data-masking-functions.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/29.1-dynamic-data-masking-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..c9970222fc91852afedbeed81657764039429e53
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/29.1-dynamic-data-masking-functions.md
@@ -0,0 +1,58 @@
+---
+title: Dynamic Data Masking Functions
+summary: Dynamic Data Masking Functions
+author: Guo Huan
+date: 2021-10-28
+---
+
+# Dynamic Data Masking Functions
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** This function is an internal function. For details, see "Database Security > Dynamic Data Anonymization".
+
+- creditcardmasking(col text, letter char default 'x')
+
+  Description: Replaces the digits before the last four bits following the col string with letters.
+
+  Parameter: Character string to be replaced or character string used for replacement
+
+  Return type: text
+
+- basicmailmasking(col text, letter char default 'x')
+
+  Description: Replaces the characters before the first at sign (@) in the col string with letters.
+
+  Parameter: Character string to be replaced or character string used for replacement
+
+  Return type: text
+
+- fullmailmasking(col text, letter char default 'x')
+
+  Description: Replaces the characters (except **@**) before the last period (.) in the col string with letters.
+
+  Parameter: Character string to be replaced or character string used for replacement
+
+  Return type: text
+
+- alldigitsmasking(col text, letter char default '0')
+
+  Description: Replaces the digits in the col string with letters.
+
+  Parameter: Character string to be replaced or character string used for replacement
+
+  Return type: text
+
+- shufflemasking(col text)
+
+  Description: Sorts the characters in the col string out of order.
+
+  Parameter: Character string to be replaced or character string used for replacement
+
+  Return type: text
+
+- randommasking(col text)
+
+  Description: Randomizes the characters in the col string.
+
+  Parameter: Character string to be replaced or character string used for replacement
+
+  Return type: text
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/3-character-processing-functions-and-operators.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/3-character-processing-functions-and-operators.md
new file mode 100644
index 0000000000000000000000000000000000000000..7bc75139f66a163b0f6df6a3c174d070d88ba5eb
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/3-character-processing-functions-and-operators.md
@@ -0,0 +1,1613 @@
+---
+title: Character Processing Functions and Operators
+summary: Character Processing Functions and Operators
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Character Processing Functions and Operators
+
+String functions and operators provided by MogDB are for concatenating strings with each other, concatenating strings with non-strings, and matching the patterns of strings.
+
+- bit_length(string)
+
+  Description: Specifies the number of bits occupied by a string.
+
+  Return type: int
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT bit_length('world');
+   bit_length
+  ------------
+           40
+  (1 row)
+  ```
+
+- btrim(string text [, characters text])
+
+  Description: Removes the longest string consisting only of characters in **characters** (a space by default) from the start and end of **string**.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT btrim('sring' , 'ing');
+   btrim
+  -------
+   sr
+  (1 row)
+  ```
+
+- char_length(string) or character_length(string)
+
+  Description: Specifies the number of characters in a string.
+
+  Return type: int
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT char_length('hello');
+   char_length
+  -------------
+             5
+  (1 row)
+  ```
+
+- instr(text,text,int,int)
+
+  Description: **instr(string1,string2,int1,int2)**  returns the text from  **int1**  to  **int2**  in  **string1**. The first  **int**  indicates the start position for matching, and the second  **int**  indicates the number of matching times.
+
+  Return type: int
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT instr( 'abcdabcdabcd', 'bcd', 2, 2 );
+   instr
+  -------
+       6
+  (1 row)
+  ```
+
+- lengthb(text/bpchar)
+
+  Description: Obtains the number of bytes of a specified string.
+
+  Return type: int
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT lengthb('hello');
+   lengthb
+  ---------
+         5
+  (1 row)
+  ```
+
+- left(str text, n int)
+
+  Description: Returns the first  _n_  characters in a string. When  _n_  is negative, all but the last  **|n|**  characters are returned.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT left('abcde', 2);
+   left
+  ------
+   ab
+  (1 row)
+  ```
+
+- length(string bytea, encoding name )
+
+  Description: Specifies the number of characters in  **string**  in the given  **encoding**.  **string**  must be valid in this encoding.
+
+  Return type: int
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT length('jose', 'UTF8');
+   length
+  --------
+        4
+  (1 row)
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > If the length of the bytea type is queried and UTF8 encoding is specified, the maximum length can only be  **536870888**.
+
+- lpad(string text, length int [, fill text])
+
+  Description: Fills up  **string**  to  **length**  by appending the characters  **fill**  (a space by default). If  **string**  is already longer than  **length**, then it is truncated.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT lpad('hi', 5, 'xyza');
+   lpad
+  -------
+   xyzhi
+  (1 row)
+  ```
+
+- notlike(x bytea name text, y bytea text)
+
+    Description: Compares x and y to check whether they are inconsistent.
+
+    Return type: Boolean
+
+    Example:
+
+    ```sql
+    mogdb=# SELECT notlike(1,2);
+        notlike
+    --------------
+                t
+    (1 row)
+    mogdb=# SELECT notlike(1,1);
+        notlike
+    --------------
+                f
+    (1 row)
+    ```
+
+- octet_length(string)
+
+  Description: Specifies the number of bytes in a string.
+
+  Return type: int
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT octet_length('jose');
+   octet_length
+  --------------
+              4
+  (1 row)
+  ```
+
+- overlay(string placing string FROM int [for int])
+
+  Description: Replaces substrings. **FROM int** indicates the start position of the replacement in the first string. **for int** indicates the number of characters replaced in the first string.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT overlay('hello' placing 'world' from 2 for 3 );
+   overlay
+  ---------
+   hworldo
+  (1 row)
+  ```
+
+- position(substring in string)
+
+  Description: Specifies the position of a substring. Parameters are case-sensitive.
+
+  Return type: int. If the character string does not exist,  **0**  is returned.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT position('ing' in 'string');
+   position
+  ----------
+          4
+  (1 row)
+  ```
+
+- pg_client_encoding()
+
+  Description: Specifies the current client encoding name.
+
+  Return type: name
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT pg_client_encoding();
+   pg_client_encoding
+  --------------------
+   UTF8
+  (1 row)
+  ```
+
+- quote_ident(string text)
+
+  Description: Returns the given string suitably quoted to be used as an identifier in an SQL statement string (quotation marks are used as required). Quotation marks are added only if necessary (that is, if the string contains non-identifier characters or would be case-folded). Embedded quotation marks are properly doubled.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT quote_ident('hello world');
+   quote_ident
+  --------------
+   "hello world"
+  (1 row)
+  ```
+
+- quote_literal(string text)
+
+  Description: Returns the given string suitably quoted to be used as a string literal in an SQL statement string (quotation marks are used as required).
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT quote_literal('hello');
+   quote_literal
+  ---------------
+   'hello'
+  (1 row)
+  ```
+
+  If a command similar to the following exists, the text will be escaped.
+
+  ```sql
+  mogdb=# SELECT quote_literal(E'O\'hello');
+   quote_literal
+  ---------------
+   'O''hello'
+  (1 row)
+  ```
+
+  If a command similar to the following exists, the backslash will be properly doubled.
+
+  ```sql
+  mogdb=# SELECT quote_literal('O\hello');
+   quote_literal
+  ---------------
+   E'O\\hello'
+  (1 row)
+  ```
+
+  If the parameter is null,  **NULL**  is returned. If the parameter may be null, you are advised to use  **quote_nullable**.
+
+  ```sql
+  mogdb=# SELECT quote_literal(NULL);
+   quote_literal
+  ---------------
+
+  (1 row)
+  ```
+
+- quote_literal(value anyelement)
+
+  Description: Converts the given value to text and then quotes it as a literal.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT quote_literal(42.5);
+   quote_literal
+  ---------------
+   '42.5'
+  (1 row)
+  ```
+
+  If a command similar to the following exists, the given value will be escaped.
+
+  ```sql
+  mogdb=# SELECT quote_literal(E'O\'42.5');
+   quote_literal
+  ---------------
+   '0''42.5'
+  (1 row)
+  ```
+
+  If a command similar to the following exists, the backslash will be properly doubled.
+
+  ```sql
+  mogdb=# SELECT quote_literal('O\42.5');
+   quote_literal
+  ---------------
+   E'O\\42.5'
+  (1 row)
+  ```
+
+- quote_nullable(string text)
+
+  Description: Returns the given string suitably quoted to be used as a string literal in an SQL statement string (quotation marks are used as required).
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT quote_nullable('hello');
+   quote_nullable
+  ----------------
+   'hello'
+  (1 row)
+  ```
+
+  If a command similar to the following exists, the text will be escaped.
+
+  ```sql
+  mogdb=# SELECT quote_nullable(E'O\'hello');
+   quote_nullable
+  ----------------
+   'O''hello'
+  (1 row)
+  ```
+
+  If a command similar to the following exists, the backslash will be properly doubled.
+
+  ```sql
+  mogdb=# SELECT quote_nullable('O\hello');
+   quote_nullable
+  ----------------
+   E'O\\hello'
+  (1 row)
+  ```
+
+  If the parameter is null,  **NULL**  is returned.
+
+  ```sql
+  mogdb=# SELECT quote_nullable(NULL);
+   quote_nullable
+  ----------------
+   NULL
+  (1 row)
+  ```
+
+- quote_nullable(value anyelement)
+
+  Description: Converts the given value to text and then quotes it as a literal.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT quote_nullable(42.5);
+   quote_nullable
+  ----------------
+   '42.5'
+  (1 row)
+  ```
+
+  If a command similar to the following exists, the given value will be escaped.
+
+  ```sql
+  mogdb=# SELECT quote_nullable(E'O\'42.5');
+   quote_nullable
+  ----------------
+   'O''42.5'
+  (1 row)
+  ```
+
+  If a command similar to the following exists, the backslash will be properly doubled.
+
+  ```sql
+  mogdb=# SELECT quote_nullable('O\42.5');
+   quote_nullable
+  ----------------
+   E'O\\42.5'
+  (1 row)
+  ```
+
+  If the parameter is null,  **NULL**  is returned.
+
+  ```sql
+  mogdb=# SELECT quote_nullable(NULL);
+   quote_nullable
+  ----------------
+   NULL
+  (1 row)
+  ```
+
+- substring_inner(string [from int] [for int])
+
+    Description: Extracts a substring.  **from int**  indicates the start position of the truncation.  **for int**  indicates the number of characters truncated.
+
+    Return type: text
+
+    Example:
+
+    ```sql
+    mogdb=# select substring_inner('adcde', 2,3);
+     substring_inner
+    -----------------
+     dcd
+    (1 row)
+    ```
+
+- substring(string [from int] [for int])
+
+  Description: Extracts a substring. **from int** indicates the start position of the truncation. **for int** indicates the number of characters truncated.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT substring('Thomas' from 2 for 3);
+   substring
+  -----------
+   hom
+  (1 row)
+  ```
+
+- substring(string from *pattern*)
+
+  Description: Extracts substrings matching the POSIX regular expression. It returns the text that matches the pattern. If no match record is found, a null value is returned.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT substring('Thomas' from '...$');
+   substring
+  -----------
+   mas
+  (1 row)
+  mogdb=# SELECT substring('foobar' from 'o(.)b');
+   result
+  --------
+   o
+  (1 row)
+  mogdb=# SELECT substring('foobar' from '(o(.)b)');
+   result
+  --------
+   oob
+  (1 row)
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  > If the POSIX pattern contains any parentheses, the portion of the text that matched the first parenthesized sub-expression (the one whose left parenthesis comes first) is returned. You can put parentheses around the whole expression if you want to use parentheses within it without triggering this exception.
+
+- substring(string from *pattern* for *escape*)
+
+  Description: Extracts substrings matching the SQL regular expression. The declared schema must match the entire data string; otherwise, the function fails and returns a null value. To indicate the part of the pattern that should be returned on success, the pattern must contain two occurrences of the escape character followed by a double quotation mark ("). The text matching the portion of the pattern between these marks is returned.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT substring('Thomas' from '%#"o_a#"_' for '#');
+   substring
+  -----------
+   oma
+  (1 row)
+  ```
+
+- rawcat(raw,raw)
+
+  Description: Indicates the string concatenation function.
+
+  Return type: raw
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT rawcat('ab','cd');
+   rawcat
+  --------
+   ABCD
+  (1 row)
+  ```
+
+- regexp_like(text,text,text)
+
+  Description: Indicates the mode matching function of a regular expression.
+
+  Return type: Boolean
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT regexp_like('str','[ac]');
+   regexp_like
+  -------------
+   f
+  (1 row)
+  ```
+
+- regexp_substr(text,text)
+
+  Description: Extracts substrings from a regular expression. Its function is similar to **substr**. When a regular expression contains multiple parallel brackets, it also needs to be processed.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT regexp_substr('str','[ac]');
+   regexp_substr
+  ---------------
+
+  (1 row)
+  ```
+
+- regexp_matches(string text, pattern text [, flags text])
+
+  Description: Returns all captured substrings resulting from matching a POSIX regular expression against **string**. If the pattern does not match, the function returns no rows. If the pattern contains no parenthesized sub-expressions, then each row returned is a single-element text array containing the substring matching the whole pattern. If the pattern contains parenthesized sub-expressions, the function returns a text array whose _n_th element is the substring matching the _n_th parenthesized sub-expression of the pattern.
+
+  The optional **flags** argument contains zero or multiple single-letter flags that change function behavior. **i** indicates that the matching is not related to uppercase and lowercase. **g** indicates that each matching substring is replaced, instead of replacing only the first one.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+  > If the last parameter is provided but the parameter value is an empty string ('') and the SQL compatibility mode of the database is set to A, the returned result is an empty set. This is because the A compatibility mode treats the empty string ('') as  **NULL**. To resolve this problem, you can:
+  >
+  > - Change the database SQL compatibility mode to C.
+  > - Do not provide the last parameter or do not set the last parameter to an empty string.
+
+  Return type: SETOF text[]
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT regexp_matches('foobarbequebaz', '(bar)(beque)');
+   regexp_matches
+  ----------------
+   {bar,beque}
+  (1 row)
+  mogdb=# SELECT regexp_matches('foobarbequebaz', 'barbeque');
+   regexp_matches
+  ----------------
+   {barbeque}
+  (1 row)
+  mogdb=#  SELECT regexp_matches('foobarbequebazilbarfbonk', '(b[^b]+)(b[^b]+)', 'g');
+      result
+  --------------
+   {bar,beque}
+   {bazil,barf}
+  (2 rows)
+  ```
+
+- regexp_split_to_array(string text, pattern text [, flags text ])
+
+  Description: Splits  **string**  using a POSIX regular expression as the delimiter. The  **regexp_split_to_array**  function behaves the same as  **regexp_split_to_table**, except that  **regexp_split_to_array**  returns its result as an array of text.
+
+  Return type: text[]
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT regexp_split_to_array('hello world', E'\\s+');
+   regexp_split_to_array
+  -----------------------
+   {hello,world}
+  (1 row)
+  ```
+
+- regexp_split_to_table(string text, pattern text [, flags text])
+
+  Description: Splits **string** using a POSIX regular expression as the delimiter. If there is no match to the pattern, the function returns the string. If there is at least one match, for each match it returns the text from the end of the last match (or the beginning of the string) to the beginning of the match. When there are no more matches, it returns the text from the end of the last match to the end of the string.
+
+  The  **flags**  parameter is a text string containing zero or more single-letter flags that change the function's behavior.  **i**  indicates case-insensitive matching.
+
+  Return type: SETOF text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT regexp_split_to_table('hello world', E'\\s+');
+   regexp_split_to_table
+  -----------------------
+   hello
+   world
+  (2 rows)
+  ```
+
+- repeat(string text, number int )
+
+  Description: Repeats **string** the specified number of times.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT repeat('Pg', 4);
+    repeat
+  ----------
+   PgPgPgPg
+  (1 row)
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  > The maximum size of memory allocated at a time cannot exceed 1 GB due to the memory allocation mechanism of the database. Therefore, the maximum value of  **number**  cannot exceed (1 GB -  **x**)/**lengthb**  (**string**) - 1.  **x**  indicates the length of the header information, which is usually greater than 4 bytes. The value varies among different scenarios.
+
+- replace(string text, from text, to text)
+
+  Description: Replaces all occurrences in **string** of substring **from** with substring **to**.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT replace('abcdefabcdef', 'cd', 'XXX');
+      replace
+  ----------------
+   abXXXefabXXXef
+  (1 row)
+  ```
+
+- reverse(str)
+
+  Description: Returns the reversed string.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT reverse('abcde');
+   reverse
+  ---------
+   edcba
+  (1 row)
+  ```
+
+- right(str text, n int)
+
+  Description: Returns the last  _n_  characters in a string. When  _n_  is negative, all but the first  **|n|**  characters are returned.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT right('abcde', 2);
+   right
+  -------
+   de
+  (1 row)
+
+  mogdb=# SELECT right('abcde', -2);
+   right
+  -------
+   cde
+  (1 row)
+  ```
+
+- rpad(string text, length int [, fill text])
+
+  Description: Fills up  **string**  to  **length**  by appending the characters  **fill**  (a space by default). If  **string**  is already longer than  **length**, then it is truncated.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT rpad('hi', 5, 'xy');
+   rpad
+  -------
+   hixyx
+  (1 row)
+  ```
+
+- rtrim(string text [, characters text])
+
+  Description: Removes the longest string containing only characters from characters (a space by default) from the end of string.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT rtrim('trimxxxx', 'x');
+   rtrim
+  -------
+   trim
+  (1 row)
+  ```
+
+- substrb(text,int,int)
+
+  Description: Extracts a substring. The first  **int**indicates the start position of the subtraction. The second  **int**  indicates the number of characters extracted.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT substrb('string',2,3);
+   substrb
+  ---------
+   tri
+  (1 row)
+  ```
+
+- substrb(text,int)
+
+  Description: Extracts a substring.  **int**  indicates the start position of the extraction.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT substrb('string',2);
+   substrb
+  ---------
+   tring
+  (1 row)
+  ```
+
+- substr(bytea,from,count)
+
+  Description: Extracts a substring from **bytea**. **from** specifies the position where the extraction starts. **count** specifies the length of the extracted substring.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT substr('string',2,3);
+   substr
+  --------
+   tri
+  (1 row)
+  ```
+
+- string || string
+
+  Description: Concatenates strings.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT 'MPP'||'DB' AS RESULT;
+   result
+  --------
+   MPPDB
+  (1 row)
+  ```
+
+- string || non-string or non-string || string
+
+  Description: Concatenates strings and non-strings.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT 'Value: '||42 AS RESULT;
+    result
+  -----------
+   Value: 42
+  (1 row)
+  ```
+
+- split_part(string text, delimiter text, field int)
+
+  Description: Splits **string** on **delimiter** and returns the **field**th column (counting from text of the first appeared delimiter).
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT split_part('abc~@~def~@~ghi', '~@~', 2);
+   split_part
+  ------------
+   def
+  (1 row)
+  ```
+
+- strpos(string, substring)
+
+  Description: Specifies the position of a substring. It is the same as **position(substring in string)**. However, the parameter sequences of them are reversed.
+
+  Return type: int
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT strpos('source', 'rc');
+   strpos
+  --------
+        4
+  (1 row)
+  ```
+
+- to_hex(number int or bigint)
+
+  Description: Converts a number to a hexadecimal expression.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT to_hex(2147483647);
+    to_hex
+  ----------
+   7fffffff
+  (1 row)
+  ```
+
+- translate(string text, from text, to text)
+
+  Description: Any character in **string** that matches a character in the **from** set is replaced by the corresponding character in the **to** set. If **from** is longer than **to**, extra characters occurred in **from** are removed.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT translate('12345', '143', 'ax');
+   translate
+  -----------
+   a2x5
+  (1 row)
+  ```
+
+- length(string)
+
+  Description: Obtains the number of characters in a string.
+
+  Return type: integer
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT length('abcd');
+   length
+  --------
+        4
+  (1 row)
+  ```
+
+- lengthb(string)
+
+  Description: Obtains the number of characters in a string. The value depends on character sets (GBK and UTF8).
+
+  Return type: integer
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT lengthb('Chinese');
+   lengthb
+  ---------
+         7
+  (1 row)
+  ```
+
+- substr(string,from)
+
+  Description:
+
+  Extracts substrings from a string.
+
+  **from** indicates the start position of the extraction.
+
+  - If **from** starts at 0, the value **1** is used.
+  - If the value of **from** is positive, all characters from **from** to the end are extracted.
+  - If the value of  **from**  is negative, the last  _n_  characters in the string are extracted, in which  **n**  indicates the absolute value of  **from**.
+
+  Return type: varchar
+
+  Example:
+
+  If the value of **from** is positive:
+
+  ```sql
+  mogdb=# SELECT substr('ABCDEF',2);
+   substr
+  --------
+   BCDEF
+  (1 row)
+  ```
+
+  If the value of **from** is negative:
+
+  ```sql
+  mogdb=# SELECT substr('ABCDEF',-2);
+   substr
+  --------
+   EF
+  (1 row)
+  ```
+
+- substr(string,from,count)
+
+  Description:
+
+  Extracts substrings from a string.
+
+  **from** indicates the start position of the extraction.
+
+  **count**  indicates the length of the extracted substring.
+
+  - If **from** starts at 0, the value **1** is used.
+  - If the value of **from** is positive, extract **count** characters starting from **from**.
+  - If the value of **from** is negative, extract the last **n** **count** characters in the string, in which **n** indicates the absolute value of **from**.
+  - If the value of **count** is smaller than **1**, **null** is returned.
+
+  Return type: varchar
+
+  Example:
+
+  If the value of **from** is positive:
+
+  ```sql
+  mogdb=# SELECT substr('ABCDEF',2,2);
+   substr
+  --------
+   BC
+  (1 row)
+  ```
+
+  If the value of **from** is negative:
+
+  ```sql
+  mogdb=# SELECT substr('ABCDEF',-3,2);
+   substr
+  --------
+   DE
+  (1 row)
+  ```
+
+- substrb(string,from)
+
+  Description: The functionality of this function is the same as that of **SUBSTR(string,from)**. However, the calculation unit is byte.
+
+  Return type: bytea
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT substrb('ABCDEF',-2);
+   substrb
+  ---------
+   EF
+  (1 row)
+  ```
+
+- substrb(string,from,count)
+
+  Description: The functionality of this function is the same as that of **SUBSTR(string,from,count)**. However, the calculation unit is byte.
+
+  Return type: bytea
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT substrb('ABCDEF',2,2);
+   substrb
+  ---------
+   BC
+  (1 row)
+  ```
+
+- trim([leading |trailing |both] [characters] from string)
+
+  Description: Removes the longest string containing only the characters (a space by default) from the start/end/both ends of the string.
+
+  Return type: varchar
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT trim(BOTH 'x' FROM 'xTomxx');
+   btrim
+  -------
+   Tom
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT trim(LEADING 'x' FROM 'xTomxx');
+   ltrim
+  -------
+   Tomxx
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT trim(TRAILING 'x' FROM 'xTomxx');
+   rtrim
+  -------
+   xTom
+  (1 row)
+  ```
+
+- rtrim(string [, characters])
+
+  Description: Removes the longest string containing only characters from characters (a space by default) from the end of string.
+
+  Return type: varchar
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT rtrim('TRIMxxxx','x');
+   rtrim
+  -------
+   TRIM
+  (1 row)
+  ```
+
+- ltrim(string [, characters])
+
+  Description: Removes the longest string containing only characters from characters (a space by default) from the start of string.
+
+  Return type: varchar
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT ltrim('xxxxTRIM','x');
+   ltrim
+  -------
+   TRIM
+  (1 row)
+  ```
+
+- upper(string)
+
+  Description: Converts the string into the uppercase.
+
+  Return type: varchar
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT upper('tom');
+   upper
+  -------
+   TOM
+  (1 row)
+  ```
+
+- lower(string)
+
+  Description: Converts the string into the lowercase.
+
+  Return type: varchar
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT lower('TOM');
+   lower
+  -------
+   tom
+  (1 row)
+  ```
+
+- rpad(string varchar, length int [, fill varchar])
+
+  Description: Fills up  **string**  to  **length**  by appending the characters  **fill**  (a space by default). If  **string**  is already longer than  **length**, then it is truncated.
+
+  **length** in MogDB indicates the character length. One Chinese character is counted as one character.
+
+  Return type: varchar
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT rpad('hi',5,'xyza');
+   rpad
+  -------
+   hixyz
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT rpad('hi',5,'abcdefg');
+   rpad
+  -------
+   hiabc
+  (1 row)
+  ```
+
+- instr(string,substring[,position,occurrence])
+
+  Description: Queries and returns the value of the substring position that occurs the  **occurrence**  (1 by default) times from the  **position**  (1 by default) in the string.
+
+  - If the value of **position** is **0**, **0** is returned.
+  - If the value of  **position**  is negative, the search is performed backwards from the last  _n_th character in the string, in which  _n_  indicates the absolute value of  **position**.
+
+  In this function, the calculation unit is character. One Chinese character is one character.
+
+  Return type: integer
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT instr('corporate floor','or', 3);
+   instr
+  -------
+       5
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT instr('corporate floor','or',-3,2);
+   instr
+  -------
+       2
+  (1 row)
+  ```
+
+- initcap(string)
+
+  Description: Converts the first letter of each word in the string into the uppercase and the other letters into the lowercase.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT initcap('hi THOMAS');
+    initcap
+  -----------
+   Hi Thomas
+  (1 row)
+  ```
+
+- ascii(string)
+
+  Description: Indicates the ASCII code of the first character in the string.
+
+  Return type: integer
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT ascii('xyz');
+   ascii
+  -------
+     120
+  (1 row)
+  ```
+
+- replace(string varchar, search_string varchar, replacement_string varchar)
+
+  Description: Replaces all  **search_string**  in the string with  **replacement_string**.
+
+  Return type: varchar
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT replace('jack and jue','j','bl');
+      replace
+  ----------------
+   black and blue
+  (1 row)
+  ```
+
+- lpad(string varchar, length int[, repeat_string varchar])
+
+  Description: Adds a series of  **repeat_string**  (a space by default) on the left of the string to generate a new string with the total length of  _n_.
+
+  If the length of the string is longer than the specified length, the function truncates the string and returns the substrings with the specified length.
+
+  Return type: varchar
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT lpad('PAGE 1',15,'*.');
+        lpad
+  -----------------
+   *.*.*.*.*PAGE 1
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT lpad('hello world',5,'abcd');
+   lpad
+  -------
+   hello
+  (1 row)
+  ```
+
+- concat(str1,str2)
+
+  Description: Connects str1 and str2 and returns the string.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+  >
+  > If the SQL compatibility mode is set to  **MY**  and  **str1**  or  **str2**  is set to  **NULL**,  **NULL**  will be returned.
+
+  Return type: varchar
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT concat('Hello', ' World!');
+      concat
+  --------------
+   Hello World!
+  (1 row)
+  mogdb=# SELECT concat('Hello', NULL);
+   concat
+  --------
+   Hello
+  (1 row)
+  ```
+
+- chr(integer)
+
+  Description: Specifies the character of the ASCII code.
+
+  Return type: varchar
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT chr(65);
+   chr
+  -----
+   A
+  (1 row)
+  ```
+
+- regexp_substr(source_char, pattern)
+
+  Description: Extracts substrings from a regular expression.
+
+  Return type: varchar
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT regexp_substr('500 Hello World, Redwood Shores, CA', ',[^,]+,') "REGEXPR_SUBSTR";
+    REGEXPR_SUBSTR
+  -------------------
+   , Redwood Shores,
+  (1 row)
+  ```
+
+- regexp_replace(string, pattern, replacement [,flags ])
+
+  Description: Replaces substrings matching the POSIX regular expression. The source string is returned unchanged if there is no match to the pattern. If there is a match, the source string is returned with the replacement string substituted for the matching substring.
+
+  The replacement string can contain \n, where n is 1 through 9, to indicate that the source substring matching the _n_th parenthesized sub-expression of the pattern should be inserted, and it can contain \& to indicate that the substring matching the entire pattern should be inserted.
+
+  The optional **flags** argument contains zero or multiple single-letter flags that change function behavior. **i** indicates that the matching is not related to uppercase and lowercase. **g** indicates that each matching substring is replaced, instead of replacing only the first one.
+
+  Return type: varchar
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT regexp_replace('Thomas', '.[mN]a.', 'M');
+   regexp_replace
+  ----------------
+   ThM
+  (1 row)
+  mogdb=# SELECT regexp_replace('foobarbaz','b(..)', E'X\\1Y', 'g') AS RESULT;
+     result
+  -------------
+   fooXarYXazY
+  (1 row)
+  ```
+
+- concat_ws(sep text, str"any" [, str"any" [, …] ])
+
+  Description: Uses the first parameter as the separator, which is associated with all following parameters. The  **NULL**  parameter is ignored.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+  >
+  > - If the first parameter value is  **NULL**, the returned result is  **NULL**.
+  > - If the first parameter is provided but the parameter value is an empty string ('') and the SQL compatibility mode of the database is set to  **A**, the returned result is  **NULL**. This is because the A compatibility mode treats the empty string ('') as  **NULL**. To resolve this problem, you can change the SQL compatibility mode of the database to  **B**,  **C**, or  **PG**.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT concat_ws(',', 'ABCDE', 2, NULL, 22);
+   concat_ws
+  ------------
+   ABCDE,2,22
+  (1 row)
+  ```
+
+- convert(string bytea, src_encoding name, dest_encoding name)
+
+  Description: Converts the bytea string to **dest_encoding**. **src_encoding** specifies the source code encoding. The string must be valid in this encoding.
+
+  Return type: bytea
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT convert('text_in_utf8', 'UTF8', 'GBK');
+            convert
+  ----------------------------
+   \x746578745f696e5f75746638
+  (1 row)
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  > If the rule for converting between source to target encoding (for example, GBK and LATIN1) does not exist, the string is returned without conversion. See the **pg_conversion** system catalog for details.
+  > Example:
+  >
+  > ```sql
+  > mogdb=# show server_encoding;
+  > server_encoding
+  > -----------------
+  > LATIN1
+  > (1 row)
+  > mogdb=# SELECT convert_from('some text', 'GBK');
+  > convert_from
+  > --------------
+  > some text
+  > (1 row)
+  > db_latin1=# SELECT convert_to('some text', 'GBK');
+  >   convert_to
+  > ----------------------
+  > \x736f6d652074657874
+  > (1 row)
+  > db_latin1=# SELECT convert('some text', 'GBK', 'LATIN1');
+  >    convert
+  > ----------------------
+  > \x736f6d652074657874
+  > (1 row)
+  > ```
+
+- convert_from(string bytea, src_encoding name)
+
+  Description: Converts the long bytea using the coding mode of the database.
+
+  **src_encoding** specifies the source code encoding. The string must be valid in this encoding.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT convert_from('text_in_utf8', 'UTF8');
+   convert_from
+  --------------
+   text_in_utf8
+  (1 row)
+  ```
+
+- convert_to(string text, dest_encoding name)
+
+  Description: Converts a string to  **dest_encoding**.
+
+  Return type: bytea
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT convert_to('some text', 'UTF8');
+        convert_to
+  ----------------------
+   \x736f6d652074657874
+  (1 row)
+  ```
+
+- string [NOT] LIKE pattern [ESCAPE escape-character]
+
+  Description: Specifies the pattern matching function.
+
+  If the pattern does not include a percentage sign (%) or an underscore (_), this mode represents itself only. In this case, the behavior of LIKE is the same as the equal operator. The underscore (_) in the pattern matches any single character while one percentage sign (%) matches no or multiple characters.
+
+  To match with underscores (_) or percent signs (%), corresponding characters in  **pattern**  must lead escape characters. The default escape character is a backward slash () and can be specified using the  **ESCAPE**  clause. To match with escape characters, enter two escape characters.
+
+  Return type: Boolean
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT 'AA_BBCC' LIKE '%A@_B%' ESCAPE '@' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT 'AA_BBCC' LIKE '%A@_B%' AS RESULT;
+   result
+  --------
+   f
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT 'AA@_BBCC' LIKE '%A@_B%' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- REGEXP_LIKE(source_string, pattern [, match_parameter])
+
+  Description: Indicates the mode matching function of a regular expression.
+
+  **source_string** indicates the source string and **pattern** indicates the matching pattern of the regular expression. **match_parameter** indicates the matching items and the values are as follows:
+
+  - 'i': case-insensitive
+  - 'c': case-sensitive
+  - 'n': allowing the metacharacter "." in a regular expression to be matched with a linefeed.
+  - 'm': allows **source_string** to be regarded as multiple rows.
+
+  If **match_parameter** is ignored, **case-sensitive** is enabled by default, "." is not matched with a linefeed, and **source_string** is regarded as a single row.
+
+  Return type: Boolean
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT regexp_like('ABC', '[A-Z]');
+   regexp_like
+  -------------
+   t
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT regexp_like('ABC', '[D-Z]');
+   regexp_like
+  -------------
+   f
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT regexp_like('ABC', '[a-z]','i');
+   regexp_like
+  -------------
+   t
+  (1 row)
+  ```
+
+- format(formatstr text [, str"any" [, …] ])
+
+  Description: Formats a string.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT format('Hello %s, %1$s', 'World');
+         format
+  --------------------
+   Hello World, World
+  (1 row)
+  ```
+
+- md5(string)
+
+  Description: Encrypts a string in MD5 mode and returns a value in hexadecimal form.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  > The MD5 encryption algorithm is not recommended because it has lower security and poses security risks.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT md5('ABC');
+                 md5
+  ----------------------------------
+   902fbdd2b1df0c4f70b4a5d23525e932
+  (1 row)
+  ```
+
+- decode(string text, format text)
+
+  Description: Decodes binary data from textual representation.
+
+  Return type: bytea
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT decode('MTIzAAE=', 'base64');
+      decode
+  --------------
+   \x3132330001
+  (1 row)
+  ```
+
+- similar_escape(pat text, esc text)
+
+    Description: Converts a regular expression of the SQL:2008 style to the POSIX style.
+
+    Return type: text
+
+    Example:
+
+    ```sql
+    mogdb=# select similar_escape('\s+ab','2');
+     similar_escape
+    ----------------
+     ^(?:\\s+ab)$
+    (1 row)
+    ```
+
+- svals(hstore)
+
+    Description: Obtains the value of the hstore type.
+
+    Return type: SETOF text
+
+    Example:
+
+    ```sql
+    mogdb=# select svals('"aa"=>"bb"');
+     svals
+    -------
+     bb
+    (1 row)
+    ```
+
+- tconvert(key text, value text)
+
+    Description: Converts character strings to the hstore format.
+
+    Return type: hstore
+
+    Example:
+
+    ```sql
+    mogdb=# select tconvert('aa', 'bb');
+      tconvert
+    ------------
+     "aa"=>"bb"
+    (1 row)
+    ```
+
+- encode(data bytea, format text)
+
+  Description: Encodes binary data into a textual representation.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT encode(E'123\\000\\001', 'base64');
+    encode
+  ----------
+   MTIzAAE=
+  (1 row)
+  ```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - For a string containing newline characters, for example, a string consisting of a newline character and a space, the value of  **length**  and  **lengthb**  in MogDB is 2.
+> - In MogDB,  _n_  in the CHAR(n) type indicates the number of characters. Therefore, for multiple-octet coded character sets, the length returned by the LENGTHB function may be longer than  _n_.
+> - MogDB supports multiple types of databases, including A, B, C, and PG. If the database type is not specified, A is used by default. The lexical analyzer of A database is different from that of the other three databases. In A database, an empty character string is considered as  **NULL**. Therefore, when a type A database is used, if a  **NULL**  character string is used as a parameter in the preceding character operation function, no output is displayed. For example:
+>
+> ```sql
+>   mogdb=# SELECT translate('12345','123','');
+>     translate
+>    -----------
+>
+>    (1 row)
+> ```
+>
+> This is because the kernel checks whether the input parameter contains  **NULL**  before calling the corresponding function. If yes, the kernel does not call the corresponding function. As a result, no output is displayed. In PG mode, the processing of character strings is the same as that of PostgreSQL. Therefore, the preceding problem does not occur.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/30-internal-functions.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/30-internal-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..e86d32404d088557cca2bcc189b56ef5a500f60b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/30-internal-functions.md
@@ -0,0 +1,171 @@
+---
+title: Internal Functions
+summary: Internal Functions
+author: Zhang Cuiping
+date: 2021-06-15
+---
+
+# Internal Functions
+
+The following functions of MogDB use internal data types, which cannot be directly called by users.
+
+- Selection rate calculation functions
+
+  | areajoinsel      | areasel         | arraycontjoinsel | arraycontsel   | contjoinsel    | contsel          | eqjoinsel    |
+  | ---------------- | --------------- | ---------------- | -------------- | -------------- | ---------------- | ------------ |
+  | eqsel            | iclikejoinsel   | iclikesel        | icnlikejoinsel | icnlikesel     | icregexeqjoinsel | icregexeqsel |
+  | icregexnejoinsel | icregexnesel    | likejoinsel      | likesel        | neqjoinsel     | neqsel           | nlikejoinsel |
+  | nlikesel         | positionjoinsel | positionsel      | regexeqjoinsel | regexeqsel     | regexnejoinsel   | regexnesel   |
+  | scalargtjoinsel  | scalargtsel     | scalarltjoinsel  | scalarltsel    | tsmatchjoinsel | tsmatchsel       | -            |
+
+- Statistics collection functions
+
+  | array_typanalyze | range_typanalyze | ts_typanalyze |
+  | ---------------- | ---------------- | ------------- |
+  | local_rto_stat   |                  |               |
+
+- Internal functions for sorting
+
+  | bpchar_sortsupport | bytea_sortsupport | date_sortsupport | numeric_sortsupport | timestamp_sortsupport |
+  | ------------------ | ----------------- | ---------------- | ------------------- | --------------------- |
+
+- Internal functions for full-text retrieval
+
+  | dispell_init    | dispell_lexize    | dsimple_init        | dsimple_lexize      | dsnowball_init   | dsnowball_lexize   | dsynonym_init |
+  | --------------- | ----------------- | ------------------- | ------------------- | ---------------- | ------------------ | ------------- |
+  | dsynonym_lexize | gtsquery_compress | gtsquery_consistent | gtsquery_decompress | gtsquery_penalty | gtsquery_picksplit | gtsquery_same |
+  | gtsquery_union  | ngram_end         | ngram_lextype       | ngram_start         | pound_end        | pound_lextype      | pound_start   |
+  | prsd_end        | prsd_headline     | prsd_lextype        | prsd_start          | thesaurus_init   | thesaurus_lexize   | zhprs_end     |
+  | zhprs_getlexeme | zhprs_lextype     | zhprs_start         | -                   | -                | -                  | -             |
+
+- Internal type processing functions
+
+  | abstimerecv                       | euc_jis_2004_to_utf8 | int2recv           | line_recv         | oidvectorrecv_extend           | tidrecv              | utf8_to_koi8u          |
+  | --------------------------------- | -------------------- | ------------------ | ----------------- | ------------------------------ | -------------------- | ---------------------- |
+  | anyarray_recv                     | euc_jp_to_mic        | int2vectorrecv     | lseg_recv         | path_recv                      | time_recv            | utf8_to_shift_jis_2004 |
+  | array_recv                        | euc_jp_to_sjis       | int4recv           | macaddr_recv      | pg_node_tree_recv              | time_transform       | utf8_to_sjis           |
+  | ascii_to_mic                      | euc_jp_to_utf8       | int8recv           | mic_to_ascii      | point_recv                     | timestamp_recv       | utf8_to_uhc            |
+  | ascii_to_utf8                     | euc_kr_to_mic        | internal_out       | mic_to_big5       | poly_recv                      | timestamp_transform  | utf8_to_win            |
+  | big5_to_euc_tw                    | euc_kr_to_utf8       | interval_recv      | mic_to_euc_cn     | pound_nexttoken                | timestamptz_recv     | uuid_recv              |
+  | big5_to_mic                       | euc_tw_to_big5       | interval_transform | mic_to_euc_jp     | prsd_nexttoken                 | timetz_recv          | varbit_recv            |
+  | big5_to_utf8                      | euc_tw_to_mic        | iso_to_koi8r       | mic_to_euc_kr     | range_recv                     | tintervalrecv        | varbit_transform       |
+  | bit_recv                          | euc_tw_to_utf8       | iso_to_mic         | mic_to_euc_tw     | rawrecv                        | tsqueryrecv          | varchar_transform      |
+  | boolrecv                          | float4recv           | iso_to_win1251     | mic_to_iso        | record_recv                    | tsvectorrecv         | varcharrecv            |
+  | box_recv                          | float8recv           | iso_to_win866      | mic_to_koi8r      | regclassrecv                   | txid_snapshot_recv   | void_recv              |
+  | bpcharrecv                        | gb18030_to_utf8      | iso8859_1_to_utf8  | mic_to_latin1     | regconfigrecv                  | uhc_to_utf8          | win_to_utf8            |
+  | btoidsortsupport                  | gbk_to_utf8          | iso8859_to_utf8    | mic_to_latin2     | regdictionaryrecv              | unknownrecv          | win1250_to_latin2      |
+  | bytearecv                         | gin_extract_tsvector | johab_to_utf8      | mic_to_latin3     | regoperatorrecv                | utf8_to_ascii        | win1250_to_mic         |
+  | byteawithoutorderwithequalcolrecv | gtsvector_compress   | json_recv          | mic_to_latin4     | regoperrecv                    | utf8_to_big5         | win1251_to_iso         |
+  | cash_recv                         | gtsvector_consistent | koi8r_to_iso       | mic_to_sjis       | regprocedurerecv               | utf8_to_euc_cn       | win1251_to_koi8r       |
+  | charrecv                          | gtsvector_decompress | koi8r_to_mic       | mic_to_win1250    | regprocrecv                    | utf8_to_euc_jis_2004 | win1251_to_mic         |
+  | cidr_recv                         | gtsvector_penalty    | koi8r_to_utf8      | mic_to_win1251    | regtyperecv                    | utf8_to_euc_jp       | win1251_to_win866      |
+  | cidrecv                           | gtsvector_picksplit  | koi8r_to_win1251   | mic_to_win866     | reltimerecv                    | utf8_to_euc_kr       | win866_to_iso          |
+  | circle_recv                       | gtsvector_same       | koi8r_to_win866    | namerecv          | shift_jis_2004_to_euc_jis_2004 | utf8_to_euc_tw       | win866_to_koi8r        |
+  | cstring_recv                      | gtsvector_union      | koi8u_to_utf8      | ngram_nexttoken   | shift_jis_2004_to_utf8         | utf8_to_gb18030      | win866_to_mic          |
+  | date_recv                         | hll_recv             | latin1_to_mic      | numeric_recv      | sjis_to_euc_jp                 | utf8_to_gbk          | win866_to_win1251      |
+  | domain_recv                       | hll_trans_recv       | latin2_to_mic      | numeric_transform | sjis_to_mic                    | utf8_to_iso8859      | xidrecv                |
+  | euc_cn_to_mic                     | hstore_recv          | latin2_to_win1250  | nvarchar2recv     | sjis_to_utf8                   | utf8_to_iso8859_1    | xidrecv4               |
+  | euc_cn_to_utf8                    | inet_recv            | latin3_to_mic      | oidrecv           | smalldatetime_recv             | utf8_to_johab        | xml_recv               |
+  | euc_jis_2004_to_shift_jis_2004    | int1recv             | latin4_to_mic      | oidvectorrecv     | textrecv                       | utf8_to_koi8r        | cstore_tid_out         |
+  | i16toi1                           | int16                | int16_bool         | int16eq           | int16div                       | int16ge              | int16gt                |
+  | int16in                           | int16le              | int16lt            | int16mi           | int16mul                       | int16ne              | int16out               |
+  | int16pl                           | int16recv            | int16send          | numeric_bool      |                                |                      |                        |
+  | jsonb_in                          | jsonb_out            | jsonb_recv         | jsonb_send        |                                |                      |                        |
+
+- Internal functions for aggregation operations
+
+  | array_agg_finalfn            | array_agg_transfn              | bytea_string_agg_finalfn         | bytea_string_agg_transfn     | date_list_agg_noarg2_transfn      | date_list_agg_transfn        | float4_list_agg_noarg2_transfn      |
+  | ---------------------------- | ------------------------------ | -------------------------------- | ---------------------------- | --------------------------------- | ---------------------------- | ----------------------------------- |
+  | float4_list_agg_transfn      | float8_list_agg_noarg2_transfn | float8_list_agg_transfn          | int2_list_agg_noarg2_transfn | int2_list_agg_transfn             | int4_list_agg_noarg2_transfn | int4_list_agg_transfn               |
+  | int8_list_agg_noarg2_transfn | int8_list_agg_transfn          | interval_list_agg_noarg2_transfn | interval_list_agg_transfn    | list_agg_finalfn                  | list_agg_noarg2_transfn      | list_agg_transfn                    |
+  | median_float8_finalfn        | median_interval_finalfn        | median_transfn                   | mode_final                   | numeric_list_agg_noarg2_transfn   | numeric_list_agg_transfn     | ordered_set_transition              |
+  | percentile_cont_float8_final | percentile_cont_interval_final | string_agg_finalfn               | string_agg_transfn           | timestamp_list_agg_noarg2_transfn | timestamp_list_agg_transfn   | timestamptz_list_agg_noarg2_transfn |
+  | timestamptz_list_agg_transfn | checksumtext_agg_transfn       | -                                | -                            | -                                 | -                            | -                                   |
+  | json_agg_finalfn             | json_agg_transfn               | json_object_agg_finalfn          | json_object_agg_transfn      | -                                 | -                            | -                                   |
+
+- Hash internal functions
+
+  | hashbeginscan | hashbuild  | hashbuildempty | hashbulkdelete | hashcostestimate | hashendscan  | hashgetbitmap     |
+  | ------------- | ---------- | -------------- | -------------- | ---------------- | ------------ | ----------------- |
+  | hashgettuple  | hashinsert | hashmarkpos    | hashmerge      | hashrescan       | hashrestrpos | hashvacuumcleanup |
+  | hashvarlena   | -          | -              | -              | -                | -            | -                 |
+
+- Internal functions of the B-tree index
+
+  | cbtreebuild  | cbtreecanreturn   | cbtreecostestimate | cbtreegetbitmap   | cbtreegettuple    | btbeginscan         | btbuild             |
+  | ------------ | ----------------- | ------------------ | ----------------- | ----------------- | ------------------- | ------------------- |
+  | btbuildempty | btbulkdelete      | btcanreturn        | btcostestimate    | btendscan         | btfloat4sortsupport | btfloat8sortsupport |
+  | btgetbitmap  | btgettuple        | btinsert           | btint2sortsupport | btint4sortsupport | btint8sortsupport   | btmarkpos           |
+  | btmerge      | btnamesortsupport | btrescan           | btrestrpos        | bttextsortsupport | btvacuumcleanup     | cbtreeoptions       |
+
+- Internal functions of the GiST index
+
+  | gist_box_compress         | gist_box_consistent      | gist_box_decompress  | gist_box_penalty          | gist_box_picksplit       | gist_box_same      | gist_box_union       |
+  | ------------------------- | ------------------------ | -------------------- | ------------------------- | ------------------------ | ------------------ | -------------------- |
+  | gist_circle_compress      | gist_circle_consistent   | gist_point_compress  | gist_point_consistent     | gist_point_distance      | gist_poly_compress | gist_poly_consistent |
+  | gistbeginscan             | gistbuild                | gistbuildempty       | gistbulkdelete            | gistcostestimate         | gistendscan        | gistgetbitmap        |
+  | gistinsert                | gistmarkpos              | gistmerge            | gistrescan                | gistrestrpos             | gistvacuumcleanup  | range_gist_compress  |
+  | range_gist_decompress     | range_gist_penalty       | range_gist_picksplit | range_gist_same           | range_gist_union         | spg_kd_choose      | spg_kd_config        |
+  | spg_kd_picksplit          | spg_quad_choose          | spg_quad_config      | spg_quad_inner_consistent | spg_quad_leaf_consistent | spg_quad_picksplit | spg_text_choose      |
+  | spg_text_inner_consistent | spg_text_leaf_consistent | spg_text_picksplit   | spgbeginscan              | spgbuild                 | spgbuildempty      | spgbulkdelete        |
+  | spgcostestimate           | spgendscan               | spggetbitmap         | spggettuple               | spginsert                | spgmarkpos         | spgmerge             |
+  | spgrestrpos               | spgvacuumcleanup         | -                    | -                         | -                        | -                  | -                    |
+
+- Internal functions of the GIN index
+
+  | gin_cmp_prefix    | gin_extract_tsquery  | gin_tsquery_consistent    | gin_tsquery_triconsistent               | ginarrayconsistent | ginarrayextract         | ginarraytriconsistent   |
+  | ----------------- | -------------------- | ------------------------- | --------------------------------------- | ------------------ | ----------------------- | ----------------------- |
+  | ginbeginscan      | ginbuild             | ginbuildempty             | ginbulkdelete                           | gincostestimate    | ginendscan              | gingetbitmap            |
+  | gininsert         | ginmarkpos           | ginmerge                  | ginqueryarrayextract                    | ginrescan          | ginrestrpos             | ginvacuumcleanup        |
+  | cginbuild         | cgingetbitmap        | -                         | -                                       | -                  | -                       | -                       |
+  | gin_compare_jsonb | gin_consistent_jsonb | gin_consistent_jsonb_hash | gin_extract_jsonbgin_extract_jsonb_hash | cginbuild          | gin_extract_jsonb_query | gin_triconsistent_jsonb |
+
+- Internal functions of the Psort index
+
+  | psortbuild | psortcanreturn | psortcostestimate | psortgetbitmap | psortgettuple |
+  | ---------- | -------------- | ----------------- | -------------- | ------------- |
+
+- Internal functions of the UBTree index
+
+  | ubtbeginscan     | ubtbuild   | ubtbuildempty | ubtbulkdelete | ubtcanreturn |
+  | ---------------- | ---------- | ------------- | ------------- | ------------ |
+  | ubtcostestimate  | ubtendscan | ubtgetbitmap  | ubtgettuple   | ubtinsert    |
+  | ubtmarkpos       | ubtmerge   | ubtoptions    | ubtrescan     | ubtrestrpos  |
+  | ubtvacuumcleanup |            |               |               |              |
+
+- plpgsql internal function
+
+  plpgsql_inline_handler
+
+- External table-related internal functions
+
+  | dist_fdw_handler | roach_handler | streaming_fdw_handler | dist_fdw_validator | file_fdw_handler | file_fdw_validator | log_fdw_handler |
+  | ---------------- | ------------- | --------------------- | ------------------ | ---------------- | ------------------ | --------------- |
+
+- Auxiliary functions for the primary DN to remotely read data pages from the standby DN.
+
+  gs_read_block_from_remote
+
+- Ledger database functions
+
+  get_dn_hist_relhash
+
+- AI feature functions
+
+    | create_snapshot         | create_snapshot_internal | prepare_snapshot_internal | prepare_snapshot | manage_snapshot_internal | archive_snapshot | publish_snapshot |
+    | ----------------------- | ------------------------ | ------------------------- | ---------------- | ------------------------ | ---------------- | ---------------- |
+    | purge_snapshot_internal | purge_snapshot           | sample_snapshot           |                  |                          |                  |                  |
+
+  - Functions of **PKG_SERVICE**
+
+    | isubmit_on_nodes | submit_on_nodes |      |      |      |      |      |
+    | ---------------- | --------------- | ---- | ---- | ---- | ---- | ---- |
+
+- Other functions
+
+  | to_tsvector_for_batch      | value_of_percentile            | session_context   | bind_variable               | job_update         | job_cancel        | job_finish                 |
+  | -------------------------- | ------------------------------ | ----------------- | --------------------------- | ------------------ | ----------------- | -------------------------- |
+  | similar_escape             | table_skewness (unavailable)   | timetz_text       | time_text                   | reltime_text       | abstime_text      | _pg_keysequal              |
+  | analyze_query(unavailable) | analyze_workload (unavailable) | ssign_table_type  | gs_comm_proxy_thread_status | gs_txid_oldestxmin | pg_cancel_session | pg_stat_segment_space_info |
+  | remote_segment_space_info  | set_cost_params                | set_weight_params | start_collect_workload      | tdigest_in         | tdigest_merge     | tdigest_merge_to_one       |
+  | tdigest_mergep             | tdigest_out                    | pg_get_delta_info |                             |                    |                   |                            |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/31-obsolete-functions.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/31-obsolete-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..b9c0b934532af332b778dd8e15edc4783e23047d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/31-obsolete-functions.md
@@ -0,0 +1,18 @@
+---
+title: Obsolete Functions
+summary: Obsolete Functions
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# Obsolete Functions
+
+The following functions in MogDB have been discarded in the latest version:
+
+| gs_wlm_get_session_info     | gs_wlm_get_user_session_info       | pgxc_get_csn                          | pgxc_get_stat_dirty_tables                | pgxc_get_thread_wait_status              | pgxc_gtm_snapshot_status               | pgxc_is_committed                  |
+| --------------------------- | ---------------------------------- | ------------------------------------- | ----------------------------------------- | ---------------------------------------- | -------------------------------------- | ---------------------------------- |
+| pgxc_lock_for_backup        | pgxc_lock_for_sp_database          | pgxc_lock_for_transfer                | pgxc_log_comm_status                      | pgxc_max_datanode_size                   | pgxc_node_str                          | pgxc_pool_check                    |
+| pgxc_pool_connection_status | pgxc_pool_reload                   | pgxc_prepared_xact                    | pgxc_snapshot_status                      | pgxc_stat_dirty_tables                   | pgxc_unlock_for_sp_database            | pgxc_unlock_for_transfer           |
+| pgxc_version                | array_extend                       | prepare_statement_status              | remote_rto_stat                           | dbe_perf.global_slow_query_info          | dbe_perf.global_slow_query_info_bytime | dbe_perf.global_slow_query_history |
+| pg_stat_get_pooler_status   | pg_stat_get_wlm_node_resource_info | pg_stat_get_wlm_session_info_internal | DBE_PERF.get_wlm_controlgroup_ng_config() | DBE_PERF.get_wlm_user_resource_runtime() | global_space_shrink                    | pg_pool_validate                   |
+| gs_stat_ustore              | table_skewness(text)               | table_skewness(text, text, text)      | -                                         | -                                        | -                                      | -                                  |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/4-binary-string-functions-and-operators.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/4-binary-string-functions-and-operators.md
new file mode 100644
index 0000000000000000000000000000000000000000..69db15cf76710c23e075be6ccfc3b3effcbf22a8
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/4-binary-string-functions-and-operators.md
@@ -0,0 +1,192 @@
+---
+title: Binary String Functions and Operators
+summary: Binary String Functions and Operators
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Binary String Functions and Operators
+
+## String Operators
+
+SQL defines some string functions that use keywords, rather than commas, to separate arguments.
+
+- octet_length(string)
+
+  Description: Specifies the number of bytes in a binary string.
+
+  Return type: int
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT octet_length(E'jo\\000se'::bytea) AS RESULT;
+   result
+  --------
+        5
+  (1 row)
+  ```
+
+- overlay(string placing string from int [for int])
+
+  Description: Replaces substrings.
+
+  Return type: bytea
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT overlay(E'Th\\000omas'::bytea placing E'\\002\\003'::bytea from 2 for 3) AS RESULT;
+       result
+  ----------------
+   \x5402036d6173
+  (1 row)
+  ```
+
+- position(substring in string)
+
+  Description: Specifies the location of a specified substring.
+
+  Return type: int
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT position(E'\\000om'::bytea in E'Th\\000omas'::bytea) AS RESULT;
+   result
+  --------
+        3
+  (1 row)
+  ```
+
+- substring(string [from int] [for int])
+
+  Description: Truncates a substring.
+
+  Return type: bytea
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT substring(E'Th\\000omas'::bytea from 2 for 3) AS RESULT;
+    result
+  ----------
+   \x68006f
+  (1 row)
+  ```
+
+- substr(string, from int [, for int])
+
+  Description: Truncates a substring.
+
+  Return type: bytea
+
+  Example:
+
+  ```sql
+  mogdb=# select substr(E'Th\\000omas'::bytea,2, 3) as result;
+    result
+  ----------
+   \x68006f
+  (1 row)
+  ```
+
+- trim([both] bytes from string)
+
+  Description: Removes the longest string containing only bytes from **bytes** from the start and end of **string**.
+
+  Return type: bytea
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT trim(E'\\000'::bytea from E'\\000Tom\\000'::bytea) AS RESULT;
+    result
+  ----------
+   \x546f6d
+  (1 row)
+  ```
+
+## Other Binary String Functions
+
+MogDB provides common syntax used for calling functions.
+
+- btrim(string bytea,bytes bytea)
+
+  Description: Removes the longest string containing only bytes from **bytes** from the start and end of **string**.
+
+  Return type: bytea
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT btrim(E'\\000trim\\000'::bytea, E'\\000'::bytea) AS RESULT;
+     result
+  ------------
+   \x7472696d
+  (1 row)
+  ```
+
+- get_bit(string, offset)
+
+  Description: Extracts bits from a string.
+
+  Return type: int
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT get_bit(E'Th\\000omas'::bytea, 45) AS RESULT;
+   result
+  --------
+        1
+  (1 row)
+  ```
+
+- get_byte(string, offset)
+
+  Description: Extracts bytes from a string.
+
+  Return type: int
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT get_byte(E'Th\\000omas'::bytea, 4) AS RESULT;
+   result
+  --------
+      109
+  (1 row)
+  ```
+
+- set_bit(string,offset, newvalue)
+
+  Description: Sets bits in a string.
+
+  Return type: bytea
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT set_bit(E'Th\\000omas'::bytea, 45, 0) AS RESULT;
+        result
+  ------------------
+   \x5468006f6d4173
+  (1 row)
+  ```
+
+- set_byte(string,offset, newvalue)
+
+  Description: Sets bytes in a string.
+
+  Return type: bytea
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT set_byte(E'Th\\000omas'::bytea, 4, 64) AS RESULT;
+        result
+  ------------------
+   \x5468006f406173
+  (1 row)
+  ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/5-bit-string-functions-and-operators.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/5-bit-string-functions-and-operators.md
new file mode 100644
index 0000000000000000000000000000000000000000..e390b68dce10d7abf2a80ad0ec40be687fc8b0fb
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/5-bit-string-functions-and-operators.md
@@ -0,0 +1,153 @@
+---
+title: Bit String Functions and Operators
+summary: Bit String Functions and Operators
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Bit String Functions and Operators
+
+Aside from the usual comparison operators, the following operators can be used. Bit string operands of  **&**,  **|**, and  **\#**  must be of equal length. In case of bit shifting, the original length of the string is preserved by zero padding (if necessary).
+
+- ||
+
+  Description: Connects bit strings.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT B'10001' || B'011' AS RESULT;
+    result
+  ----------
+   10001011
+  (1 row)
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  > It is recommended that a column have no more than 180 consecutive internal joins. A column with over 180 joins will be split into joined consecutive strings.
+  > Example:**str1||str2||str3||str4** is split into **(str1||str2)||(str3||str4)**.
+
+- &
+
+  Description: Specifies the AND operation between bit strings.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT B'10001' & B'01101' AS RESULT;
+   result
+  --------
+   00001
+  (1 row)
+  ```
+
+- |
+
+  Description: Specifies the OR operation between bit strings.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT B'10001' | B'01101' AS RESULT;
+   result
+  --------
+   11101
+  (1 row)
+  ```
+
+- \#
+
+  Description: Specifies the OR operation between bit strings if they are inconsistent. If the same positions in the two bit strings are both 1 or 0, the position returns  **0**.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT B'10001' # B'01101' AS RESULT;
+   result
+  --------
+   11100
+  (1 row)
+  ```
+
+- ~
+
+  Description: Specifies the NOT operation between bit strings.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT ~B'10001'AS RESULT;
+   result
+  ----------
+   01110
+  (1 row)
+  ```
+
+- &lt;&lt;
+
+  Description: Shifts left in a bit string.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT B'10001' << 3 AS RESULT;
+   result
+  ----------
+   01000
+  (1 row)
+  ```
+
+- &gt;&gt;
+
+  Description: Shifts right in a bit string.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT B'10001' >> 2 AS RESULT;
+   result
+  ----------
+   00100
+  (1 row)
+  ```
+
+The following SQL-standard functions work on bit strings as well as strings:**length**, **bit_length**, **octet_length**, **position**, **substring**, and **overlay**.
+
+The following functions work on bit strings as well as binary strings:**get_bit** and **set_bit**. When working with a bit string, these functions number the first (leftmost) bit of the string as bit 0.
+
+In addition, it is possible to convert between integral values and type **bit**. Example:
+
+```sql
+mogdb=# SELECT 44::bit(10) AS RESULT;
+   result
+------------
+ 0000101100
+(1 row)
+
+mogdb=# SELECT 44::bit(3) AS RESULT;
+ result
+--------
+ 100
+(1 row)
+
+mogdb=# SELECT cast(-44 as bit(12)) AS RESULT;
+    result
+--------------
+ 111111010100
+(1 row)
+
+mogdb=# SELECT '1110'::bit(4)::integer AS RESULT;
+ result
+--------
+     14
+(1 row)
+
+mogdb=# select substring('10101111'::bit(8), 2);
+ substring
+-----------
+ 0101111
+(1 row)
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> Casting to just "bit" means casting to bit(1), and so will deliver only the least significant bit of the integer.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/6-mode-matching-operators.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/6-mode-matching-operators.md
new file mode 100644
index 0000000000000000000000000000000000000000..dd3cde33e4418ca048fa8e059660013b13d81c2a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/6-mode-matching-operators.md
@@ -0,0 +1,224 @@
+---
+title: Mode Matching Operators
+summary: Mode Matching Operators
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Mode Matching Operators
+
+There are three separate approaches to pattern matching provided by the database: the traditional SQL LIKE operator, the more recent SIMILAR TO operator, and POSIX-style regular expressions. Besides these basic operators, functions can be used to extract or replace matching substrings and to split a string at matching locations.
+
+- LIKE
+
+  Description: Specifies whether the string matches the mode string following  **LIKE**. The LIKE expression returns true if the string matches the supplied pattern. (As expected, the NOT LIKE expression returns false if LIKE returns true, and vice versa.)
+
+  Matching rules:
+
+  1. This operator can succeed only when its pattern matches the entire string. If you want to match a sequence in any position within the string, the pattern must begin and end with a percent sign.
+
+  2. The underscore (\_) represents (matching) any single character. Percentage (%) indicates the wildcard character of any string.
+
+  3. To match a literal underscore or percent sign without matching other characters, the respective character in **pattern** must be preceded by the escape character. The default escape character is the backslash but a different one can be selected by using the **ESCAPE** clause.
+
+  4. To match with escape characters, enter two escape characters. For example, to write a  **pattern**  constant containing a backslash (), you need to enter two backslashes in SQL statements.
+
+     > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+     > When  **standard_conforming_strings**  is set to  **off**, any backslashes you write in literal string constants will need to be doubled. So, writing a pattern that matches a single backslash actually involves writing four backslashes in the statement (you can avoid this by selecting a different escape character with  **ESCAPE**  so that the backslash is no longer a special character of  **LIKE**. But the backslash is still the special character of the character text analyzer, so you still need two backslashes.)
+     >
+     > In MySQL-compatible schema, it is also possible to select no escape character by writing  **ESCAPE ''**. This effectively disables the escape mechanism, which makes it impossible to turn off the special meaning of underscore and percent signs in the schema.
+
+  5. The keyword ILIKE can be used instead of LIKE to make the match case-insensitive.
+
+  6. Operator \~\~ is equivalent to LIKE, and operator \~\~* corresponds to ILIKE.
+
+  Example:
+
+  ```sql
+    mogdb=# SELECT 'abc' LIKE 'abc' AS RESULT;
+     result
+    -----------
+     t
+    (1 row)
+    mogdb=# SELECT 'abc' LIKE 'a%' AS RESULT;
+     result
+    -----------
+     t
+    (1 row)
+    mogdb=# SELECT 'abc' LIKE '_b_' AS RESULT;
+     result
+    -----------
+     t
+    (1 row)
+    mogdb=# SELECT 'abc' LIKE 'c' AS RESULT;
+     result
+    -----------
+     f
+    (1 row)
+  ```
+
+- SIMILAR TO
+
+  Description: Returns  **true**  or  **false**  depending on whether the pattern matches the given string. It is similar to  **LIKE**, but differs in that  **SIMILAR TO**  uses the regular expression understanding pattern defined by the SQL standard.
+
+  Matching rules:
+
+  1. Similar to LIKE, this operator succeeds only when its pattern matches the entire string. If you want to match a sequence in any position within the string, the pattern must begin and end with a percent sign.
+
+  2. The underscore (\_) represents (matching) any single character. Percentage (%) indicates the wildcard character of any string.
+
+  3. SIMILAR TO supports these pattern-matching metacharacters borrowed from POSIX regular expressions:
+
+     | Metacharacter | Description                                                  |
+     | ------------- | ------------------------------------------------------------ |
+     | \|            | Specifies alternation (either of two alternatives).          |
+     | *             | Specifies repetition of the previous item zero or more times. |
+     | +             | Specifies repetition of the previous item one or more times. |
+     | ?             | Specifies repetition of the previous item zero or one time.  |
+     | {m}           | Specifies repetition of the previous item exactly *m* times. |
+     | {m,}          | Specifies repetition of the previous item *m* or more times. |
+     | {m,n}         | Specifies repetition of the previous item at least *m* times and does not exceed *n* times. |
+     | ()            | Specifies that parentheses () can be used to group items into a single logical item. |
+     | […]           | Specifies a character class, just as in POSIX regular expressions. |
+
+  4. A preamble escape character disables the special meaning of any of these metacharacters. The rules for using escape characters are the same as those for LIKE.
+
+  Regular expressions:
+
+  The [substring(string from pattern) function](3-character-processing-functions-and-operators) extracts a substring that matches an SQL regular expression pattern.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT 'abc' SIMILAR TO 'abc' AS RESULT;
+   result
+  -----------
+   t
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT 'abc' SIMILAR TO 'a' AS RESULT;
+   result
+  -----------
+   f
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT 'abc' SIMILAR TO '%(b|d)%' AS RESULT;
+   result
+  -----------
+   t
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT 'abc' SIMILAR TO '(b|c)%'  AS RESULT;
+   result
+  -----------
+   f
+  (1 row)
+  ```
+
+- POSIX regular expressions
+
+  Description: A regular expression is a character sequence that is an abbreviated definition of a set of strings (a regular set). If a string is a member of a regular expression described by a regular expression, the string matches the regular expression. POSIX regular expressions provide a more powerful means for pattern matching than the LIKE and SIMILAR TO operators. [Table 1](#regular expression) lists all available operators for pattern matching using POSIX regular expressions.
+
+  **Table 1** Regular expression match operators<a id="regular expression"> </a>
+
+  | Operator | Description                                                  | Example                  |
+  | -------- | ------------------------------------------------------------ | ------------------------ |
+  | ~        | Matches a regular expression, which is case-sensitive.       | 'thomas' ~ '.*thomas.*'  |
+  | ~        | Matches a regular expression, which is case-insensitive.     | 'thomas' ~ '.*Thomas.*'  |
+  | ! ~      | Does not match a regular expression, which is case-sensitive. | 'thomas' !~ '.*Thomas.*' |
+  | ! ~      | Does not match a regular expression, which is case-sensitive. | 'thomas' !~ '.*vadim.*'  |
+
+  Matching rules:
+
+  1. Unlike LIKE patterns, a regular expression is allowed to match anywhere within a string, unless the regular expression is explicitly anchored to the beginning or end of the string.
+
+  2. Besides the metacharacters mentioned above, POSIX regular expressions also support the following pattern matching metacharacters:
+
+     | Metacharacter | Description                                 |
+     | ------------- | ------------------------------------------- |
+     | ^             | Specifies the match starting with a string. |
+     | $             | Specifies the match at the end of a string. |
+     | .             | Matches any single character.               |
+
+  Regular expressions:
+
+  POSIX regular expressions support the following functions:
+
+  - The [substring(string from pattern)](3-character-processing-functions-and-operators) function provides a method for extracting a substring that matches the POSIX regular expression pattern.
+
+  - The [regexp_replace(string, pattern, replacement [,flags ])](3-character-processing-functions-and-operators) function provides the functionality of replacing the substring matching the POSIX regular expression pattern with the new text.
+
+  - The [regexp_matches(string text, pattern text [, flags text])](3-character-processing-functions-and-operators) function returns a text array consisting of all captured substrings that match a POSIX regular expression pattern.
+
+  - The [regexp_split_to_table(string text, pattern text [, flags text])](3-character-processing-functions-and-operators) function splits a string using a POSIX regular expression pattern as a delimiter.
+
+  - The [regexp_split_to_array(string text, pattern text [, flags text ])](3-character-processing-functions-and-operators) function behaves the same as regexp_split_to_table, except that regexp_split_to_array returns its result as an array of text.
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+    > The regular expression split functions ignore zero-length matches, which occur at the beginning or end of a string or after the previous match. This is contrary to the strict definition of regular expression matching. The latter is implemented by regexp_matches, but the former is usually the most commonly used behavior in practice.
+
+  Example:
+
+  ```sql
+  mogdb=#  SELECT 'abc' ~ 'Abc' AS RESULT;
+  result
+  --------
+   f
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT 'abc' ~* 'Abc' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT 'abc' !~ 'Abc' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT 'abc'!~* 'Abc' AS RESULT;
+   result
+  --------
+   f
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT 'abc' ~ '^a' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT 'abc' ~ '(b|d)'AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT 'abc' ~ '^(b|c)'AS RESULT;
+   result
+  --------
+   f
+  (1 row)
+  ```
+
+  Although most regular expression searches can be executed quickly, regular expressions can still be artificially made up of memory that takes a long time and any amount of memory. It is not recommended that you accept the regular expression search mode from the non-security mode source. If you must do this, you are advised to add the statement timeout limit. The search with the SIMILAR TO mode has the same security risks as the SIMILAR TO provides many capabilities that are the same as those of the POSIX- style regular expression. The LIKE search is much simpler than the other two options. Therefore, it is more secure to accept the non-secure mode source search.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/7-mathematical-functions-and-operators.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/7-mathematical-functions-and-operators.md
new file mode 100644
index 0000000000000000000000000000000000000000..f661c4b9093b4581813fd91d3a4504bd240b0c3e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/7-mathematical-functions-and-operators.md
@@ -0,0 +1,1189 @@
+---
+title: Mathematical Functions and Operators
+summary: Mathematical Functions and Operators
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Mathematical Functions and Operators
+
+## Numeric Operators
+
+- \+
+
+  Description: Addition
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT 2+3 AS RESULT;
+   result
+  --------
+        5
+  (1 row)
+  ```
+
+- \-
+
+  Description: Subtraction
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT 2-3 AS RESULT;
+   result
+  --------
+       -1
+  (1 row)
+  ```
+
+- \*
+
+  Description: Multiplication
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT 2*3 AS RESULT;
+   result
+  --------
+        6
+  (1 row)
+  ```
+
+- /
+
+  Description: Division (The result is not rounded.)
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT 4/2 AS RESULT;
+   result
+  --------
+        2
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT 4/3 AS RESULT;
+        result
+  ------------------
+   1.33333333333333
+  (1 row)
+  ```
+
+- +/-
+
+  Description: Positive/Negative
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT -2 AS RESULT;
+   result
+  --------
+       -2
+  (1 row)
+  ```
+
+- %
+
+  Description: Model (to obtain the remainder)
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT 5%4 AS RESULT;
+   result
+  --------
+        1
+  (1 row)
+  ```
+
+- @
+
+  Description: Absolute value
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT @ -5.0 AS RESULT;
+   result
+  --------
+      5.0
+  (1 row)
+  ```
+
+- \^
+
+  Description: Power (exponent calculation)
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT 2.0^3.0 AS RESULT;
+         result
+  --------------------
+   8.0000000000000000
+  (1 row)
+  ```
+
+- |/
+
+  Description: Square root
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT |/ 25.0 AS RESULT;
+   result
+  --------
+        5
+  (1 row)
+  ```
+
+- ||/
+
+  Description: Cubic root
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT ||/ 27.0 AS RESULT;
+   result
+  --------
+        3
+  (1 row)
+  ```
+
+- !
+
+  Description: Factorial
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT 5! AS RESULT;
+   result
+  --------
+      120
+  (1 row)
+  ```
+
+- !!
+
+  Description: Factorial (prefix operator)
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT !!5 AS RESULT;
+   result
+  --------
+      120
+  (1 row)
+  ```
+
+- &
+
+  Description: Binary AND
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT 91&15  AS RESULT;
+   result
+  --------
+       11
+  (1 row)
+  ```
+
+- |
+
+  Description: Binary OR
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT 32|3  AS RESULT;
+   result
+  --------
+       35
+  (1 row)
+  ```
+
+- \#
+
+  Description: Binary XOR
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT 17#5  AS RESULT;
+   result
+  --------
+       20
+  (1 row)
+  ```
+
+- ~
+
+  Description: Binary NOT
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT ~1 AS RESULT;
+   result
+  --------
+       -2
+  (1 row)
+  ```
+
+- &lt;&lt;
+
+  Description: Binary shift left
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT 1<<4 AS RESULT;
+   result
+  --------
+       16
+  (1 row)
+  ```
+
+- &gt;&gt;
+
+  Description: Binary shift right
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT 8>>2 AS RESULT;
+   result
+  --------
+        2
+  (1 row)
+  ```
+
+## Numeric Operation Functions
+
+- abs(x)
+
+  Description: Absolute value
+
+  Return type: same as the input
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT abs(-17.4);
+   abs
+  ------
+   17.4
+  (1 row)
+  ```
+
+- acos(x)
+
+  Description: Arc cosine
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT acos(-1);
+         acos
+  ------------------
+   3.14159265358979
+  (1 row)
+  ```
+
+- asin(x)
+
+  Description: Arc sine
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT asin(0.5);
+         asin
+  ------------------
+   .523598775598299
+  (1 row)
+  ```
+
+- atan(x)
+
+  Description: Arc tangent
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT atan(1);
+         atan
+  ------------------
+   .785398163397448
+  (1 row)
+  ```
+
+- atan2(y, x)
+
+  Description: Arc tangent of y/x
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT atan2(2, 1);
+        atan2
+  ------------------
+   1.10714871779409
+  (1 row)
+  ```
+
+- bitand(integer, integer)
+
+  Description: Performs an AND (&) operation on two integers.
+
+  Return type: bigint
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT bitand(127, 63);
+   bitand
+  --------
+       63
+  (1 row)
+  ```
+
+- cbrt(dp)
+
+  Description: Cubic root
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT cbrt(27.0);
+   cbrt
+  ------
+      3
+  (1 row)
+  ```
+
+- ceil(x)
+
+  Description: Minimum integer greater than or equal to the parameter
+
+  Return type: integer
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT ceil(-42.8);
+   ceil
+  ------
+    -42
+  (1 row)
+  ```
+
+- ceiling(dp or numeric)
+
+  Description: Minimum integer (alias of ceil) greater than or equal to the parameter
+
+  Return type: dp or numeric. If implicit type conversion is not considered, the return type is the same as the input type.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT ceiling(-95.3);
+   ceiling
+  ---------
+       -95
+  (1 row)
+  ```
+
+- cos(x)
+
+  Description: Cosine
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT cos(-3.1415927);
+          cos
+  -------------------
+   -.999999999999999
+  (1 row)
+  ```
+
+- cot(x)
+
+  Description: Cotangent
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT cot(1);
+         cot
+  ------------------
+   .642092615934331
+  (1 row)
+  ```
+
+- degrees(dp)
+
+  Description: Converts radians to angles.
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT degrees(0.5);
+       degrees
+  ------------------
+   28.6478897565412
+  (1 row)
+  ```
+
+- div(y numeric, x numeric)
+
+  Description: Integer part of y/x
+
+  Return type: numeric
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT div(9,4);
+   div
+  -----
+     2
+  (1 row)
+  ```
+
+- exp(x)
+
+  Description: Natural exponent
+
+  Return type: dp or numeric. If implicit type conversion is not considered, the return type is the same as the input type.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT exp(1.0);
+          exp
+  --------------------
+   2.7182818284590452
+  (1 row)
+  ```
+
+- floor(x)
+
+  Description: Not larger than the maximum integer of the parameter
+
+  Return type: Maximum integer not larger than the parameter
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT floor(-42.8);
+   floor
+  -------
+     -43
+  (1 row)
+  ```
+
+- int1(in)
+
+    Description: Converts the input text parameter to a value of the int1 type and returns the value.
+
+    Return type: int1
+
+    Example:
+
+    ```sql
+    mogdb=# select int1('123');
+     int1
+    ------
+     123
+    (1 row)
+    mogdb=# select int1('a');
+     int1
+    ------
+       0
+    (1 row)
+    ```
+
+- int2(in)
+
+    Description: Converts the input parameter to a value of the int2 type and returns the value.
+
+    The supported input parameter types include float4, float8, numeric, and text.
+
+    Return type: int2
+
+    Example:
+
+    ```sql
+    mogdb=# select int2('1234');
+     int2
+    ------
+     1234
+    (1 row)
+    mogdb=# select int2(25.3);
+     int2
+    ------
+       25
+    (1 row)
+    ```
+
+- int4(in)
+
+    Description: Converts the input parameter to a value of the int4 type and returns the value.
+
+    The supported input parameter types include bit, boolean, char, double precision, numeric, real, smallint and text
+
+    Return type: int4
+
+    Example:
+
+    ```sql
+    mogdb=# select int4('789');
+     int4
+    ------
+     789
+    (1 row)
+    mogdb=# select int4(99.9);
+     int4
+    ------
+       99
+    (1 row)
+    ```
+
+- int1(in)
+
+  Description: Converts the input text parameter to the int1-type value and returns the value.
+
+  Return type: int1
+
+  Example:
+
+  ```sql
+  mogdb=# select int1('123');
+   int1
+  ------
+   123
+  (1 row)
+  mogdb=# select int1('a');
+   int1
+  ------
+     0
+  (1 row)
+  ```
+
+- int2(in)
+
+  Description: Converts the input parameter to the int2-type value and returns the value.
+
+  The input parameter type supported includes float4, float8, numeric and text.
+
+  Return type: int2
+
+  Example:
+
+  ```sql
+  mogdb=# select int2('1234');
+   int2
+  ------
+   1234
+  (1 row)
+  mogdb=# select int2(25.3);
+   int2
+  ------
+     25
+  (1 row)
+  ```
+
+- int4(in)
+
+  Description: Converts the input parameter to the int4-type value and returns the value.
+
+  The input parameter type supported includes bit, boolean, char, duoble precision, numeric, real, smallint and text.
+
+  Return type: int4
+
+  Example:
+
+  ```sql
+  mogdb=# select int4('789');
+   int4
+  ------
+   789
+  (1 row)
+  mogdb=# select int4(99.9);
+   int4
+  ------
+     99
+  (1 row)
+  ```
+
+- radians(dp)
+
+  Description: Converts angles to radians.
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT radians(45.0);
+       radians
+  ------------------
+   .785398163397448
+  (1 row)
+  ```
+
+- random()
+
+  Description: Random number between 0.0 and 1.0
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT random();
+        random
+  ------------------
+   .824823560658842
+  (1 row)
+  ```
+
+- multiply(x double precision or text, y double precision or text)
+
+  Description: Product of x and y.
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT multiply(9.0, '3.0');
+       multiply
+  -------------------
+                 27
+  (1 row)
+  mogdb=# SELECT multiply('9.0', 3.0);
+       multiply
+  -------------------
+                 27
+  (1 row)
+  ```
+
+- ln(x)
+
+  Description: Natural logarithm
+
+  Return type: dp or numeric. If implicit type conversion is not considered, the return type is the same as the input type.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT ln(2.0);
+          ln
+  -------------------
+   .6931471805599453
+  (1 row)
+  ```
+
+- log(x)
+
+  Description: Logarithm with 10 as the base
+
+  Return type: same as the input
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT log(100.0);
+          log
+  --------------------
+   2.0000000000000000
+  (1 row)
+  ```
+
+- log(b numeric, x numeric)
+
+  Description: Logarithm with b as the base
+
+  Return type: numeric
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT log(2.0, 64.0);
+          log
+  --------------------
+   6.0000000000000000
+  (1 row)
+  ```
+
+- mod(x,y)
+
+  Description: Remainder of x/y (model) If x equals to 0, 0 is returned.
+
+  Return type: same as the parameter type
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT mod(9,4);
+   mod
+  -----
+     1
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT mod(9,0);
+   mod
+  -----
+     9
+  (1 row)
+  ```
+
+- pi()
+
+  Description: π constant value
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT pi();
+          pi
+  ------------------
+   3.14159265358979
+  (1 row)
+  ```
+
+- power(a double precision, b double precision)
+
+  Description: b power of a
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT power(9.0, 3.0);
+          power
+  ----------------------
+   729.0000000000000000
+  (1 row)
+  ```
+
+- round(x)
+
+  Description: Integer closest to the input parameter
+
+  Return type: same as the input
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT round(42.4);
+   round
+  -------
+      42
+  (1 row)
+
+  mogdb=# SELECT round(42.6);
+   round
+  -------
+      43
+  (1 row)
+  ```
+
+- round(v numeric, s int)
+
+  Description:**s** digits are kept after the decimal point.
+
+  Return type: numeric
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT round(42.4382, 2);
+   round
+  -------
+   42.44
+  (1 row)
+  ```
+
+- setseed(dp)
+
+  Description: Sets seed for the following random() invoking (between -1.0 and 1.0, inclusive).
+
+  Return type: void
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT setseed(0.54823);
+   setseed
+  ---------
+
+  (1 row)
+  ```
+
+- sign(x)
+
+  Description: returns symbols of this parameter.
+
+  Return type:  **-1**  indicates minus.  **0**  indicates 0, and  **1**  indicates positive numbers.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT sign(-8.4);
+   sign
+  ------
+     -1
+  (1 row)
+  ```
+
+- sin(x)
+
+  Description: Sine
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT sin(1.57079);
+         sin
+  ------------------
+   .999999999979986
+  (1 row)
+  ```
+
+- sqrt(x)
+
+  Description: Square root
+
+  Return type: dp or numeric. If implicit type conversion is not considered, the return type is the same as the input type.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT sqrt(2.0);
+         sqrt
+  -------------------
+   1.414213562373095
+  (1 row)
+  ```
+
+- tan(x)
+
+  Description: Tangent
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT tan(20);
+         tan
+  ------------------
+   2.23716094422474
+  (1 row)
+  ```
+
+- trunc(x)
+
+  Description: Truncates (the integral part).
+
+  Return type: same as the input
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT trunc(42.8);
+   trunc
+  -------
+      42
+  (1 row)
+  ```
+
+- trunc(v numeric, s int)
+
+  Description: Truncates a number with **s** digits after the decimal point.
+
+  Return type: numeric
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT trunc(42.4382, 2);
+   trunc
+  -------
+   42.43
+  (1 row)
+  ```
+
+- smgrne(a smgr, b smgr)
+
+    Description: Compares two integers of the smgr type to check whether they are different.
+
+    Return type: Boolean
+
+- smgreq(a smgr, b smgr)
+
+    Description: Compares two integers of the smgr type to check whether they are equivalent.
+
+    Return type: Boolean
+
+- int1abs
+
+    Description: Returns the absolute value of data of the uint8 type.
+
+    Parameter: tinyint
+
+    Return type: tinyint
+
+- int1and
+
+    Description: Returns the bitwise AND result of two data records of the uint8 type.
+
+    Parameter: tinyint, tinyint
+
+    Return type: tinyint
+
+- int1cmp
+
+    Description: Returns the comparison result of two data records of the uint8 type. If the value of the first parameter is greater,  **1**  is returned. If the value of the second parameter is greater,  **-1**  is returned. If they are the same,  **0**  is returned.
+
+    Parameter: tinyint, tinyint
+
+    Return type: integer
+
+- int1div
+
+    Description: Returns the result of dividing two data records of the uint8 type. The result is of the float8 type.
+
+    Parameter: tinyint, tinyint
+
+    Return type: tinyint
+
+- int1eq
+
+    Description: Compares two pieces of data of the uint8 type to check whether they are the same.
+
+    Parameter: tinyint, tinyint
+
+    Return type: Boolean
+
+- int1ge
+
+    Description: Determines whether the value of the first parameter is greater than or equal to the value of the second parameter in two data records of the uint8 type.
+
+    Parameter: tinyint, tinyint
+
+    Return type: Boolean
+
+- int1gt
+
+    Description: Performs a greater-than operation on an unsigned 1-byte integer.
+
+    Parameter: tinyint, tinyint
+
+    Return type: Boolean
+
+- int1larger
+
+    Description: Returns the maximum value of an unsigned 1-byte integer.
+
+    Parameter: tinyint, tinyint
+
+    Return type: tinyint
+
+- int1le
+
+    Description: Performs a less-than or an equal-to operation on an unsigned 1-byte integer.
+
+    Parameter: tinyint, tinyint
+
+    Return type: Boolean
+
+- int1lt
+
+    Description: Performs a less-than operation on an unsigned 1-byte integer.
+
+    Parameter: tinyint, tinyint
+
+    Return type: Boolean
+
+- int1smaller
+
+    Description: Calculates the minimum value of an unsigned 1-byte integer.
+
+    Parameter: tinyint, tinyint
+
+    Return type: tinyint
+
+- int1inc
+
+    Description: Unsigned 1-byte integer plus 1.
+
+    Parameter: tinyint
+
+    Return type: tinyint
+
+- int1mi
+
+    Description: Performs a minus operation on an unsigned 1-byte integer.
+
+    Parameter: tinyint, tinyint
+
+    Return type: tinyint
+
+- int1mod
+
+    Description: Performs a reminder operation on an unsigned 1-byte integer.
+
+    Parameter: tinyint, tinyint
+
+    Return type: tinyint
+
+- int1mul
+
+    Description: Performs a multiplication operation on unsigned 1-byte integer.
+
+    Parameter: tinyint, tinyint
+
+    Return type: tinyint
+
+- int1ne
+
+    Description: Performs a not-equal-to operation on an unsigned 1-byte integer.
+
+    Parameter: tinyint, tinyint
+
+    Return type: Boolean
+
+- int1pl
+
+    Description: Performs an addition operation on an unsigned 1-byte integer.
+
+    Parameter: tinyint, tinyint
+
+    Return type: tinyint
+
+- int1um
+
+    Description: Returns an unsigned 2-byte integer after subtracting the opposite number from the unsigned 1-byte integer.
+
+    Parameter: tinyint
+
+    Return type: smallint
+
+- int1xor
+
+    Description: Performs an exclusive OR operation on an unsigned 1-byte integer.
+
+    Parameter: tinyint, tinyint
+
+    Return type: tinyint
+
+- cash_div_int1
+
+    Description: Performs a division operation on the money type.
+
+    Parameter: money, tinyint
+
+    Return type: money
+
+- cash_mul_int1
+
+    Description: Performs a multiplication operation on the money type.
+
+    Parameter: money, tinyint
+
+    Return type: money
+
+- int1not
+
+    Description: Reverts binary bits of an unsigned 1-byte integer.
+
+    Parameter: tinyint
+
+    Return type: tinyint
+
+- int1or
+
+    Description: Performs an OR operation on an unsigned 1-byte integer.
+
+    Parameter: tinyint, tinyint
+
+    Return type: tinyint
+
+- int1shl
+
+    Description: Shifts an unsigned 1-byte integer leftwards by a specified number of bits.
+
+    Parameter: tinyint, integer
+
+    Return type: tinyint
+
+- width_bucket(op numeric, b1 numeric, b2 numeric, count int)
+
+  Description: Returns a bucket to which the operand will be assigned in an equi-depth histogram with **count** buckets, ranging from **b1** to **b2**.
+
+  Return type: int
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT width_bucket(5.35, 0.024, 10.06, 5);
+   width_bucket
+  --------------
+              3
+  (1 row)
+  ```
+
+- width_bucket(op dp, b1 dp, b2 dp, count int)
+
+  Description: Returns a bucket to which the operand will be assigned in an equi-depth histogram with **count** buckets, ranging from **b1** to **b2**.
+
+  Return type: int
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT width_bucket(5.35, 0.024, 10.06, 5);
+   width_bucket
+  --------------
+              3
+  (1 row)
+  ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/8-date-and-time-processing-functions-and-operators.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/8-date-and-time-processing-functions-and-operators.md
new file mode 100644
index 0000000000000000000000000000000000000000..d59b90cd1b923a9d3fe5b9a24b982ad8c8a6b435
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/8-date-and-time-processing-functions-and-operators.md
@@ -0,0 +1,1320 @@
+---
+title: Date and Time Processing Functions and Operators
+summary: Date and Time Processing Functions and Operators
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Date and Time Processing Functions and Operators
+
+## Date and Time Operators
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-warning.gif) **WARNING:**
+> When the user uses date/time operators, explicit type prefixes are modified for corresponding operands to ensure that the operands parsed by the database are consistent with what the user expects, and no unexpected results occur.
+> For example, abnormal mistakes will occur in the following example without an explicit data type.
+>
+> ```sql
+> SELECT date '2001-10-01' - '7' AS RESULT;
+> ```
+
+**Table 1** Time and date operators
+
+| Operator | Example                                                      |
+| -------- | ------------------------------------------------------------ |
+| +        | `mogdb=# SELECT date '2001-09-28' + integer '7' AS RESULT; result 2001-10-05 (1 row)` |
+|          | `mogdb=# SELECT date '2001-09-28' + interval '1 hour' AS RESULT; result 2001-09-28 01:00:00 (1 row)` |
+|          | `mogdb=# SELECT date '2001-09-28' + time '03:00' AS RESULT; result 2001-09-28 03:00:00 (1 row)` |
+|          | `mogdb=# SELECT interval '1 day' + interval '1 hour' AS RESULT; result 1 day 01:00:00 (1 row)` |
+|          | `mogdb=# SELECT timestamp '2001-09-28 01:00' + interval '23 hours' AS RESULT; result 2001-09-29 00:00:00 (1 row)` |
+|          | `mogdb=# SELECT time '01:00' + interval '3 hours' AS RESULT; result 04:00:00 (1 row)` |
+| -        | `mogdb=# SELECT date '2001-10-01' - date '2001-09-28' AS RESULT; result 3 days (1 row)` |
+|          | `mogdb=# SELECT date '2001-10-01' - integer '7' AS RESULT; result 2001-09-24 00:00:00 (1 row)` |
+|          | `mogdb=# SELECT date '2001-09-28' - interval '1 hour' AS RESULT; result 2001-09-27 23:00:00 (1 row)` |
+|          | `mogdb=# SELECT time '05:00' - time '03:00' AS RESULT; result 02:00:00 (1 row)` |
+|          | `mogdb=# SELECT time '05:00' - interval '2 hours' AS RESULT; result 03:00:00 (1 row)` |
+|          | `mogdb=# SELECT timestamp '2001-09-28 23:00' - interval '23 hours' AS RESULT; result 2001-09-28 00:00:00 (1 row)` |
+|          | `mogdb=# SELECT interval '1 day' - interval '1 hour' AS RESULT; result 23:00:00 (1 row)` |
+|          | `mogdb=# SELECT timestamp '2001-09-29 03:00' - timestamp '2001-09-27 12:00' AS RESULT; result 1 day 15:00:00 (1 row)` |
+| *        | `mogdb=# SELECT 900 * interval '1 second' AS RESULT; result 00:15:00 (1 row)` |
+|          | `mogdb=# SELECT 21 * interval '1 day' AS RESULT; result 21 days (1 row)` |
+|          | `mogdb=# SELECT double precision '3.5' * interval '1 hour' AS RESULT; result 03:30:00 (1 row)` |
+| /        | `mogdb=# SELECT interval '1 hour' / double precision '1.5' AS RESULT; result 00:40:00 (1 row)` |
+
+## Time/Date Functions
+
+- age(timestamp, timestamp)
+
+  Description: Subtracts parameters, producing a result in YYYY-MM-DD format. If the result is negative, the returned result is also negative. The input parameters can contain timezone or not.
+
+  Return type: interval
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT age(timestamp '2001-04-10', timestamp '1957-06-13');
+             age
+  -------------------------
+   43 years 9 mons 27 days
+  (1 row)
+  ```
+
+- age(timestamp)
+
+  Description: Minuses the current time with the parameter. The input parameter can contain timezone or not.
+
+  Return type: interval
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT age(timestamp '1957-06-13');
+             age
+  -------------------------
+   60 years 2 mons 18 days
+  (1 row)
+  ```
+
+- clock_timestamp()
+
+  Description: Specifies the current timestamp of the real-time clock.
+
+  Return type: timestamp with time zone
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT clock_timestamp();
+          clock_timestamp
+  -------------------------------
+   2017-09-01 16:57:36.636205+08
+  (1 row)
+  ```
+
+- current_date
+
+  Description: Specifies the current date.
+
+  Return type: date
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT current_date;
+      date
+  ------------
+   2017-09-01
+  (1 row)
+  ```
+
+- current_time
+
+  Description: Specifies the current time.
+
+  Return type: time with time zone
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT current_time;
+         timetz
+  --------------------
+   16:58:07.086215+08
+  (1 row)
+  ```
+
+- current_timestamp
+
+  Description: Specifies the current date and time.
+
+  Return type: timestamp with time zone
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT current_timestamp;
+         pg_systimestamp
+  ------------------------------
+   2017-09-01 16:58:19.22173+08
+  (1 row)
+  ```
+
+- systimestamp <a id = 'systimestamp'> </a>
+
+  Description: Returns the system date of the system where the database is located, including fractional seconds and time zone.
+
+  Return type: timestamp with time zone
+
+  ```sql
+  mogdb=# select systimestamp;
+  pg_systimestamp
+  -----------------------------
+  2021-12-24 14:34:24.6903+08
+  (1 row)
+  ```
+
+- date_part(text, timestamp)
+
+  Description: Obtains the value of a subdomain in date or time, for example, the year or hour. It is equivalent to  **extract(field from timestamp)**.
+
+  Timestamp types: abstime, date, interval, reltime, time with time zone, time without time zone, timestamp with time zone, timestamp without time zone
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT date_part('hour', timestamp '2001-02-16 20:38:40');
+   date_part
+  -----------
+          20
+  (1 row)
+  ```
+
+- date_part(text, interval)
+
+  Description: Obtains the subdomain value of the date/time value. When obtaining the month value, if the value is greater than 12, obtain the remainder after it is divided by 12. It is equivalent to  **extract(field from timestamp)**.
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT date_part('month', interval '2 years 3 months');
+   date_part
+  -----------
+           3
+  (1 row)
+  ```
+
+- date_trunc(text, timestamp)
+
+  Description: Truncates to the precision specified by **text**.
+
+  Return type: interval, timestamp with time zone, timestamp without time zone
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT date_trunc('hour', timestamp  '2001-02-16 20:38:40');
+       date_trunc
+  ---------------------
+   2001-02-16 20:00:00
+  (1 row)
+  ```
+
+- trunc(timestamp)
+
+  Description: Truncates to day by default.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT trunc(timestamp  '2001-02-16 20:38:40');                                                                                                                                                                   trunc
+  ---------------------
+  2001-02-16 00:00:00
+  (1 row)
+  ```
+
+- daterange(arg1, arg2)
+
+    Description: Obtains time boundary information. The type of  **arg1**  and  **arg2**  is  **date**.
+
+    Return type: daterange
+
+    Example:
+
+    ```sql
+    mogdb=# select daterange('2000-05-06','2000-08-08');
+            daterange
+    -------------------------
+     [2000-05-06,2000-08-08)
+    (1 row)
+    ```
+
+- daterange(arg1, arg2, text)
+
+    Description: Obtains time boundary information. The type of  **arg1**  and  **arg2**  is  **date**, and the type of  **text**  is  **text**.
+
+    Return type: daterange
+
+    Example:
+
+    ```sql
+    mogdb=# select daterange('2000-05-06','2000-08-08','[]');
+            daterange
+    -------------------------
+     [2000-05-06,2000-08-09)
+    (1 row)
+    ```
+
+- extract(field from timestamp)
+
+  Description: Obtains the hour.
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT extract(hour from timestamp '2001-02-16 20:38:40');
+   date_part
+  -----------
+          20
+  (1 row)
+  ```
+
+- extract(field from interval)
+
+  Description: Obtains the month. If the value is greater than 12, obtain the remainder after it is divided by 12.
+
+  Return type: double precision
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT extract(month from interval '2 years 3 months');
+   date_part
+  -----------
+           3
+  (1 row)
+  ```
+
+- isfinite(date)
+
+  Description: Tests for a valid date.
+
+  Return type: Boolean
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT isfinite(date '2001-02-16');
+   isfinite
+  ----------
+   t
+  (1 row)
+  ```
+
+- isfinite(timestamp)
+
+  Description: Tests for a valid timestamp.
+
+  Return type: Boolean
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT isfinite(timestamp '2001-02-16 21:28:30');
+   isfinite
+  ----------
+   t
+  (1 row)
+  ```
+
+- isfinite(interval)
+
+  Description: Tests for a valid interval.
+
+  Return type: Boolean
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT isfinite(interval '4 hours');
+   isfinite
+  ----------
+   t
+  (1 row)
+  ```
+
+- justify_days(interval)
+
+  Description: Adjusts intervals to 30-day time periods, which are represented as months.
+
+  Return type: interval
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT justify_days(interval '35 days');
+   justify_days
+  --------------
+   1 mon 5 days
+  (1 row)
+  ```
+
+- justify_hours(interval)
+
+  Description: Sets the time interval in days (24 hours is one day).
+
+  Return type: interval
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT JUSTIFY_HOURS(INTERVAL '27 HOURS');
+   justify_hours
+  ----------------
+   1 day 03:00:00
+  (1 row)
+  ```
+
+- justify_interval(interval)
+
+  Description: Adjusts **interval** using **justify_days** and **justify_hours**.
+
+  Return type: interval
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT JUSTIFY_INTERVAL(INTERVAL '1 MON -1 HOUR');
+   justify_interval
+  ------------------
+   29 days 23:00:00
+  (1 row)
+  ```
+
+- localtime
+
+  Description: Specifies the current time.
+
+  Return type: time
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT localtime AS RESULT;
+       result
+  ----------------
+   16:05:55.664681
+  (1 row)
+  ```
+
+- localtimestamp
+
+  Description: Specifies the current date and time.
+
+  Return type: timestamp
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT localtimestamp;
+           timestamp
+  ----------------------------
+   2017-09-01 17:03:30.781902
+  (1 row)
+  ```
+
+- now()
+
+  Description: Specifies the current date and time.
+
+  Return type: timestamp with time zone
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT now();
+                now
+  -------------------------------
+   2017-09-01 17:03:42.549426+08
+  (1 row)
+  ```
+
+- timenow
+
+    Description: Specifies the current date and time.
+
+    Return type: timestamp with time zone
+
+    Example:
+
+    ```sql
+    mogdb=# select timenow();
+            timenow
+    ------------------------
+     2020-06-23 20:36:56+08
+    (1 row)
+    ```
+
+- numtodsinterval(num, interval_unit)
+
+  Description: Converts a number to the interval type. **num** is a numeric-typed number. **interval_unit** is a string in the following format: 'DAY' | 'HOUR' | 'MINUTE' | 'SECOND'
+
+  You can set the IntervalStyle parameter to **a** to be compatible with the interval output format of the function.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT numtodsinterval(100, 'HOUR');
+   numtodsinterval
+  -----------------
+   100:00:00
+  (1 row)
+
+  mogdb=# SET intervalstyle = a;
+  SET
+  mogdb=# SELECT numtodsinterval(100, 'HOUR');
+          numtodsinterval
+  -------------------------------
+   +000000004 04:00:00.000000000
+  (1 row)
+  ```
+
+- pg_sleep(seconds)
+
+  Description: Specifies the delay time of the server thread in unit of second.
+
+  Return type: void
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT pg_sleep(10);
+   pg_sleep
+  ----------
+
+  (1 row)
+  ```
+
+- statement_timestamp()
+
+  Description: Specifies the current date and time.
+
+  Return type: timestamp with time zone
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT statement_timestamp();
+        statement_timestamp
+  -------------------------------
+   2017-09-01 17:04:39.119267+08
+  (1 row)
+  ```
+
+- sysdate
+
+  Description: Specifies the current date and time.
+
+  Return type: timestamp
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT sysdate;
+         sysdate
+  ---------------------
+   2017-09-01 17:04:49
+  (1 row)
+  ```
+
+- timeofday()
+
+  Description: Specifies the current date and time (like  **clock_timestamp**, but returned as a  **text**  string)
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT timeofday();
+                timeofday
+  -------------------------------------
+   Fri Sep 01 17:05:01.167506 2017 CST
+  (1 row)
+  ```
+
+- transaction_timestamp()
+
+  Description: Specifies the current date and time (equivalent to  **current_timestamp**)
+
+  Return type: timestamp with time zone
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT transaction_timestamp();
+       transaction_timestamp
+  -------------------------------
+   2017-09-01 17:05:13.534454+08
+  (1 row)
+  ```
+
+- add_months(d,n)
+
+  Description: Returns the date *date* plus *integer* months.
+
+  Return type: timestamp
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT add_months(to_date('2017-5-29', 'yyyy-mm-dd'), 11) FROM dual;
+       add_months
+  ---------------------
+   2018-04-29 00:00:00
+  (1 row)
+  ```
+
+- last_day(d)
+
+  Description: Returns the date of the last day of the month that contains *date*.
+
+  Return type: timestamp
+
+  Example:
+
+  ```sql
+  mogdb=# select last_day(to_date('2017-01-01', 'YYYY-MM-DD')) AS cal_result;
+       cal_result
+  ---------------------
+   2017-01-31 00:00:00
+  (1 row)
+  ```
+
+- next_day(x,y)
+
+  Description: Calculates the time of the next week y started from x.
+
+  Return type: timestamp
+
+  Example:
+
+  ```sql
+  mogdb=# select next_day(timestamp '2017-05-25 00:00:00','Sunday')AS cal_result;
+       cal_result
+  ---------------------
+   2017-05-28 00:00:00
+  (1 row)
+  ```
+
+- tinterval(abstime, abstime )
+
+    Description: Creates a time interval with two pieces of absolute time.
+
+    Return type: tinterval
+
+    Example:
+
+    ```sql
+    mogdb=# call tinterval(abstime 'May 10, 1947 23:59:12', abstime 'Mon May  1 00:30:30 1995');
+                          tinterval
+    -----------------------------------------------------
+     ["1947-05-10 23:59:12+08" "1995-05-01 00:30:30+08"]
+    (1 row)
+    ```
+
+- tintervalend(tinterval)
+
+    Description: Returns the end time of  **tinterval**.
+
+    Return type: abstime
+
+    Example:
+
+    ```sql
+    mogdb=# select tintervalend('["Sep 4, 1983 23:59:12" "Oct4, 1983 23:59:12"]');
+          tintervalend
+    ------------------------
+     1983-10-04 23:59:12+08
+    (1 row)
+    ```
+
+- tintervalrel(tinterval)
+
+    Description: Calculates and returns the relative time of  **tinterval**.
+
+    Return type: reltime
+
+    Example:
+
+    ```sql
+    mogdb=# select tintervalrel('["Sep 4, 1983 23:59:12" "Oct4, 1983 23:59:12"]');
+     tintervalrel
+    --------------
+     1 mon
+    (1 row)
+    ```
+
+- smalldatetime_ge
+
+    Description: Checks whether the value of the first parameter is greater than or equal to that of the second parameter.
+
+    Parameter: smalldatetime, smalldatetime
+
+    Return type: Boolean
+
+- smalldatetime_cmp
+
+    Description: Compares two smalldatetime values to check whether they are the same.
+
+    Parameter: smalldatetime, smalldatetime
+
+    Return type: integer
+
+- smalldatetime_eq
+
+    Description: Compares two smalldatetime values to check whether they are the same.
+
+    Parameter: smalldatetime, smalldatetime
+
+    Return type: Boolean
+
+- smalldatetime_gt
+
+    Description: Determines whether the first parameter is greater than the second.
+
+    Parameter: smalldatetime, smalldatetime
+
+    Return type: Boolean
+
+- smalldatetime_hash
+
+    Description: Calculates the hash value corresponding to a timestamp.
+
+    Parameter: smalldatetime
+
+    Return type: integer
+
+- smalldatetime_in
+
+    Description: Inputs a timestamp.
+
+    Parameter: cstring, oid, integer
+
+    Return type: smalldatetime
+
+- smalldatetime_larger
+
+    Description: Returns a larger timestamp.
+
+    Parameter: smalldatetime, smalldatetime
+
+    Return type: smalldatetime
+
+- smalldatetime_le
+
+    Description: Checks whether the value of the first parameter is less than or equal to that of the second parameter.
+
+    Parameter: smalldatetime, smalldatetime
+
+    Return type: Boolean
+
+- smalldatetime_lt
+
+    Description: Determines whether the first parameter is less than the second parameter.
+
+    Parameter: smalldatetime, smalldatetime
+
+    Return type: Boolean
+
+- smalldatetime_ne
+
+    Description: Compares two timestamps to check whether they are different.
+
+    Parameter: smalldatetime, smalldatetime
+
+    Return type: Boolean
+
+- smalldatetime_out
+
+    Description: Converts a timestamp into the external form.
+
+    Parameter: smalldatetime
+
+    Return type: cstring
+
+- smalldatetime_send
+
+    Description: Converts a timestamp to the binary format.
+
+    Parameter: smalldatetime
+
+    Return type: bytea
+
+- smalldatetime_smaller
+
+    Description: Returns a smaller smalldatetime.
+
+    Parameter: smalldatetime, smalldatetime
+
+    Return type: smalldatetime
+
+- smalldatetime_to_abstime
+
+    Description: Converts smalldatetime to abstime.
+
+    Parameter: smalldatetime
+
+    Return type: abstime
+
+- smalldatetime_to_time
+
+    Description: Converts smalldatetime to time.
+
+    Parameter: smalldatetime
+
+    Return type: time without time zone
+
+- smalldatetime_to_timestamp
+
+    Description: Converts smalldatetime to timestamp.
+
+    Parameter: smalldatetime
+
+    Return type: timestamp without time zone
+
+- smalldatetime_to_timestamptz
+
+    Description: Converts smalldatetime to timestamptz.
+
+    Parameter: smalldatetime
+
+    Return type: timestamp with time zone
+
+- smalldatetime_to_varchar2
+
+    Description: Converts smalldatetime to varchar2.
+
+    Parameter: smalldatetime
+
+    Return type: character varying
+
+    >![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif)**NOTE:**
+    >
+    > There are multiple methods for obtaining the current time. Select an appropriate API based on the actual service scenario.
+    >
+    > 1. The following APIs return values based on the start time of the current transaction:
+    >
+    >    ```sql
+    >    CURRENT_DATE CURRENT_TIME CURRENT_TIMESTAMP CURRENT_TIME(precision) CURRENT_TIMESTAMP(precision) LOCALTIME LOCALTIMESTAMP LOCALTIME(precision) LOCALTIMESTAMP(precision)
+    >    ```
+    >
+    >    **CURRENT_TIME**  and  **CURRENT_TIMESTAMP**  transfer values with time zones. The values of  **LOCALTIME**  and  **LOCALTIMESTAMP**  do not contain time zone information.  **CURRENT_TIME**,  **CURRENT_TIMESTAMP**,  **LOCALTIME**, and  **LOCALTIMESTAMP**  can be optionally attached with a precision parameter, which rounds the second field of the result to the specified decimal place. If there is no precision parameter, the result is given the full precision that can be obtained.
+    >   Because these functions all return results by the start time of the current transaction, their values do not change throughout the transaction. We think this is a feature with the purpose to allow a transaction to have a consistent concept at the "current" time, so that multiple modifications in the same transaction can maintain the same timestamp.
+    >
+    > 2. The following APIs return the start time of the current statement:
+    >
+    >    ```sql
+    >    transaction_timestamp() statement_timestamp() now()
+    >    ```
+    >
+    >    **transaction_timestamp()**  is equivalent to  **CURRENT_TIMESTAMP**, and its name clearly reflects its return value.  **statement_timestamp()**  returns the start time of the current statement (more accurately, the time when the last instruction is received from the client). The return values of  **statement_timestamp()**  and  **transaction_timestamp()**  are the same during the execution of the first instruction of a transaction, but may be different in subsequent instructions.
+    >   **now()**  is equivalent to  **transaction_timestamp()**.
+    >
+    > 3. The following APIs return the actual current time when the function is invoked:
+    >
+    >    ```sql
+    >    clock_timestamp() timeofday()
+    >    ```
+    >
+    >    **clock_timestamp()**  returns the actual current time, and its value changes even in the same SQL instruction. Similar to  **clock_timestamp()**,  **timeofday()**  also returns the actual current time. However, the result of  **timeofday()**  is a formatted text string instead of a timestamp with time zone information.
+
+## TIMESTAMPDIFF
+
+- **TIMESTAMPDIFF(unit , timestamp_expr1, timestamp_expr2)**
+
+The timestampdiff function returns the result of **timestamp_expr2** - **timestamp_expr1** in the specified unit. **timestamp_expr1** and **timestamp_expr2** must be value expressions of the **timestamp**, **timestamptz**, or **date** type. **unit** indicates the unit of the difference between two dates.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> This function is valid only when MogDB is compatible with the MY type (that is, dbcompatibility = 'B').
+
+- year
+
+  Year.
+
+  ```sql
+  mogdb=#  SELECT TIMESTAMPDIFF(YEAR, '2018-01-01', '2020-01-01');
+   timestamp_diff
+  ----------------
+                2
+  (1 row)
+  ```
+
+- quarter
+
+  Quarter.
+
+  ```sql
+  mogdb=#  SELECT TIMESTAMPDIFF(QUARTER, '2018-01-01', '2020-01-01');
+   timestamp_diff
+  ----------------
+                8
+  (1 row)
+  ```
+
+- month
+
+  Month.
+
+  ```sql
+  mogdb=#  SELECT TIMESTAMPDIFF(MONTH, '2018-01-01', '2020-01-01');
+   timestamp_diff
+  ----------------
+               24
+  (1 row)
+  ```
+
+- week
+
+  Week.
+
+  ```sql
+  mogdb=#  SELECT TIMESTAMPDIFF(WEEK, '2018-01-01', '2020-01-01');
+   timestamp_diff
+  ----------------
+              104
+  (1 row)
+  ```
+
+- day
+
+  Day.
+
+  ```sql
+  mogdb=#  SELECT TIMESTAMPDIFF(DAY, '2018-01-01', '2020-01-01');
+   timestamp_diff
+  ----------------
+              730
+  (1 row)
+  ```
+
+- hour
+
+  Hour.
+
+  ```sql
+  mogdb=#  SELECT TIMESTAMPDIFF(HOUR, '2020-01-01 10:10:10', '2020-01-01 11:11:11');
+   timestamp_diff
+  ----------------
+                1
+  (1 row)
+
+  ```
+
+- minute
+
+  Minute.
+
+  ```sql
+  mogdb=#  SELECT TIMESTAMPDIFF(MINUTE, '2020-01-01 10:10:10', '2020-01-01 11:11:11');
+   timestamp_diff
+  ----------------
+               61
+  (1 row)
+
+  ```
+
+- second
+
+  Second.
+
+  ```sql
+  mogdb=#  SELECT TIMESTAMPDIFF(SECOND, '2020-01-01 10:10:10', '2020-01-01 11:11:11');
+   timestamp_diff
+  ----------------
+             3661
+  (1 row)
+
+  ```
+
+- microseconds
+
+  The seconds column, including fractional parts, is multiplied by 1,000,000.
+
+  ```sql
+  mogdb=#  SELECT TIMESTAMPDIFF(MICROSECOND, '2020-01-01 10:10:10.000000', '2020-01-01 10:10:10.111111');
+   timestamp_diff
+  ----------------
+           111111
+  (1 row)
+
+  ```
+
+- timestamp_expr with the time zone
+
+    ```sql
+    mogdb=# SELECT TIMESTAMPDIFF(HOUR,'2020-05-01 10:10:10-01','2020-05-01 10:10:10-03');
+     timestamp_diff
+    ----------------
+                  2
+    (1 row)
+    ```
+
+## EXTRACT
+
+- **EXTRACT(field FROM source)**
+
+  The  **extract**  function retrieves subcolumns such as year or hour from date/time values.  **source**  must be a value expression of type  **timestamp**,  **time**, or  **interval**. (Expressions of type  **date**  are cast to  **timestamp**  and can therefore be used as well.)  **field**  is an identifier or string that selects what column to extract from the source value. The  **extract**  function returns values of type  **double precision**. The following are valid  **field**  names:
+
+- century
+
+  The first century starts at 0001-01-01 00:00:00 AD. This definition applies to all Gregorian calendar countries. There is no century number 0. You go from **-1** century to **1** century.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT EXTRACT(CENTURY FROM TIMESTAMP '2000-12-16 12:21:13');
+   date_part
+  -----------
+          20
+  (1 row)
+  ```
+
+- day
+
+  - For **timestamp** values, the day (of the month) column (1-31)
+
+    ```sql
+    mogdb=# SELECT EXTRACT(DAY FROM TIMESTAMP '2001-02-16 20:38:40');
+     date_part
+    -----------
+            16
+    (1 row)
+    ```
+
+  - For **interval** values, the number of days
+
+    ```sql
+    mogdb=# SELECT EXTRACT(DAY FROM INTERVAL '40 days 1 minute');
+     date_part
+    -----------
+            40
+    (1 row)
+    ```
+
+- decade
+
+  Year column divided by 10
+
+  ```sql
+  mogdb=# SELECT EXTRACT(DECADE FROM TIMESTAMP '2001-02-16 20:38:40');
+   date_part
+  -----------
+         200
+  (1 row)
+  ```
+
+- dow
+
+  Day of the week as Sunday(**0**) to Saturday (**6**)
+
+  ```sql
+  mogdb=# SELECT EXTRACT(DOW FROM TIMESTAMP '2001-02-16 20:38:40');
+   date_part
+  -----------
+           5
+  (1 row)
+  ```
+
+- doy
+
+  Day of the year (1-365 or 366)
+
+  ```sql
+  mogdb=# SELECT EXTRACT(DOY FROM TIMESTAMP '2001-02-16 20:38:40');
+   date_part
+  -----------
+          47
+  (1 row)
+  ```
+
+- epoch
+
+  - For **timestamp with time zone** values, the number of seconds since 1970-01-01 00:00:00-00 UTC (can be negative).
+
+    For **date** and **timestamp** values, the number of seconds since 1970-01-01 00:00:00-00 local time.
+
+    For **interval** values, the total number of seconds in the interval.
+
+    ```sql
+    mogdb=# SELECT EXTRACT(EPOCH FROM TIMESTAMP WITH TIME ZONE '2001-02-16 20:38:40.12-08');
+      date_part
+    --------------
+     982384720.12
+    (1 row)
+    ```
+
+    ```sql
+    mogdb=# SELECT EXTRACT(EPOCH FROM INTERVAL '5 days 3 hours');
+     date_part
+    -----------
+        442800
+    (1 row)
+    ```
+
+  - Way to convert an epoch value back to a timestamp
+
+    ```sql
+    mogdb=# SELECT TIMESTAMP WITH TIME ZONE 'epoch' + 982384720.12 * INTERVAL '1 second' AS RESULT;
+              result
+    ---------------------------
+     2001-02-17 12:38:40.12+08
+    (1 row)
+    ```
+
+- hour
+
+  Hour column (0-23)
+
+  ```sql
+  mogdb=# SELECT EXTRACT(HOUR FROM TIMESTAMP '2001-02-16 20:38:40');
+   date_part
+  -----------
+          20
+  (1 row)
+  ```
+
+- isodow
+
+  Day of the week (1-7)
+
+  Monday is 1 and Sunday is 7.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  > This is identical to **dow** except for Sunday.
+
+  ```sql
+  mogdb=# SELECT EXTRACT(ISODOW FROM TIMESTAMP '2001-02-18 20:38:40');
+   date_part
+  -----------
+           7
+  (1 row)
+  ```
+
+- isoyear
+
+  The ISO 8601 year that the date falls in (not applicable to intervals).
+
+  Each ISO year begins with the Monday of the week containing January 4, so in early January or late December the ISO year may be different from the Gregorian year. See the **week** column for more information.
+
+  ```sql
+  mogdb=# SELECT EXTRACT(ISOYEAR FROM DATE '2006-01-01');
+   date_part
+  -----------
+        2005
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT EXTRACT(ISOYEAR FROM DATE '2006-01-02');
+   date_part
+  -----------
+        2006
+  (1 row)
+  ```
+
+- microseconds
+
+  The seconds column, including fractional parts, is multiplied by 1,000,000.
+
+  ```sql
+  mogdb=# SELECT EXTRACT(MICROSECONDS FROM TIME '17:12:28.5');
+   date_part
+  -----------
+    28500000
+  (1 row)
+  ```
+
+- millennium
+
+  Years in the 1900s are in the second millennium. The third millennium started from January 1, 2001.
+
+  ```sql
+  mogdb=# SELECT EXTRACT(MILLENNIUM FROM TIMESTAMP '2001-02-16 20:38:40');
+   date_part
+  -----------
+           3
+  (1 row)
+  ```
+
+- milliseconds
+
+  Seconds column, including fractional parts, is multiplied by 1000. Note that this includes full seconds.
+
+  ```sql
+  mogdb=# SELECT EXTRACT(MILLISECONDS FROM TIME '17:12:28.5');
+   date_part
+  -----------
+       28500
+  (1 row)
+  ```
+
+- minute
+
+  Minutes column (0-59).
+
+  ```sql
+  mogdb=# SELECT EXTRACT(MINUTE FROM TIMESTAMP '2001-02-16 20:38:40');
+   date_part
+  -----------
+          38
+  (1 row)
+  ```
+
+- month
+
+  For  **timestamp**  values, the specific month in the year (1-12).
+
+  ```sql
+  mogdb=# SELECT EXTRACT(MONTH FROM TIMESTAMP '2001-02-16 20:38:40');
+   date_part
+  -----------
+           2
+  (1 row)
+  ```
+
+  For **interval** values, the number of months, modulo 12 (0-11).
+
+  ```sql
+  mogdb=# SELECT EXTRACT(MONTH FROM INTERVAL '2 years 13 months');
+   date_part
+  -----------
+           1
+  (1 row)
+  ```
+
+- quarter
+
+  Quarter of the year (1-4) that the date is in.
+
+  ```sql
+  mogdb=# SELECT EXTRACT(QUARTER FROM TIMESTAMP '2001-02-16 20:38:40');
+   date_part
+  -----------
+           1
+  (1 row)
+  ```
+
+- second
+
+  Seconds column, including fractional parts (0-59).
+
+  ```sql
+  mogdb=# SELECT EXTRACT(SECOND FROM TIME '17:12:28.5');
+   date_part
+  -----------
+        28.5
+  (1 row)
+  ```
+
+- timezone
+
+  Time zone offset from UTC, measured in seconds. Positive values correspond to time zones east of UTC, negative values to zones west of UTC.
+
+- timezone_hour
+
+  Hour component of the time zone offset.
+
+- timezone_minute
+
+  Minute component of the time zone offset.
+
+- week
+
+  Number of the week of the year that the day is in. By definition (ISO 8601), the first week of a year contains January 4 of that year. (The ISO-8601 week starts on Monday.) In other words, the first Thursday of a year is in week 1 of that year.
+
+  Because of this, it is possible for early January dates to be part of the 52nd or 53rd week of the previous year, and late December dates to be part of the 1st week of the next year. For example, **2005-01-01** is part of the 53rd week of year 2004, **2006-01-01** is part of the 52nd week of year 2005, and **2012-12-31** is part of the 1st week of year 2013. You are advised to use the columns **isoyear** and **week** together to ensure consistency.
+
+  ```sql
+  mogdb=# SELECT EXTRACT(WEEK FROM TIMESTAMP '2001-02-16 20:38:40');
+   date_part
+  -----------
+           7
+  (1 row)
+  ```
+
+- year
+
+  Year column.
+
+  ```sql
+  mogdb=# SELECT EXTRACT(YEAR FROM TIMESTAMP '2001-02-16 20:38:40');
+   date_part
+  -----------
+        2001
+  (1 row)
+  ```
+
+## date_part
+
+The **date_part** function is modeled on the traditional Ingres equivalent to the SQL-standard function **extract**:
+
+- **date_part('***field***', ***source***)**
+
+Note that here the **field** parameter needs to be a string value, not a name. The valid field names for **field** are the same as for **extract**. For details, see [EXTRACT](#extract).
+
+Example:
+
+```sql
+mogdb=# SELECT date_part('day', TIMESTAMP '2001-02-16 20:38:40');
+ date_part
+-----------
+        16
+(1 row)
+```
+
+```sql
+mogdb=# SELECT date_part('hour', INTERVAL '4 hours 3 minutes');
+ date_part
+-----------
+         4
+(1 row)
+```
+
+Table 2 specifies the schema for formatting date and time values.
+
+**Table 2** Schema for formatting date and time<a id="2 schema"></a>
+
+| Category              | Format                                                       | Description                                                  |
+| --------------------- | ------------------------------------------------------------ | ------------------------------------------------------------ |
+| Hour                  | HH                                                           | Number of hours in one day (01-12)                           |
+| HH12                  | Number of hours in one day (01-12)                           |                                                              |
+| HH24                  | Number of hours in one day (00-23)                           |                                                              |
+| Minute                | MI                                                           | Minute (00-59)                                               |
+| Second                | SS                                                           | Second (00-59)                                               |
+| FF                    | Microsecond (000000-999999)                                  |                                                              |
+| SSSSS                 | Second after midnight (0-86399)                              |                                                              |
+| Morning and afternoon | AM or A.M.                                                   | Morning identifier                                           |
+| PM or P.M.            | Afternoon identifier                                         |                                                              |
+| Year                  | Y,YYY                                                        | Year with comma (with four digits or more)                   |
+| SYYYY                 | Year with four digits BC                                     |                                                              |
+| YYYY                  | Year (with four digits or more)                              |                                                              |
+| YYY                   | Last three digits of a year                                  |                                                              |
+| YY                    | Last two digits of a year                                    |                                                              |
+| Y                     | Last one digit of a year                                     |                                                              |
+| IYYY                  | ISO year (with four digits or more)                          |                                                              |
+| IYY                   | Last three digits of an ISO year                             |                                                              |
+| IY                    | Last two digits of an ISO year                               |                                                              |
+| I                     | Last one digit of an ISO year                                |                                                              |
+| RR                    | Last two digits of a year (A year of the 20th century can be stored in the 21st century.) |                                                              |
+| RRRR                  | Capable of receiving a year with four digits or two digits. If there are 2 digits, the value is the same as the returned value of RR. If there are 4 digits, the value is the same as YYYY. |                                                              |
+| BC or B.C.AD or A.D.  | Era indicator Before Christ (BC) and After Christ (AD)       |                                                              |
+| Month                 | MONTH                                                        | Full spelling of a month in uppercase (9 characters are filled in if the value is empty.) |
+| MON                   | Month in abbreviated format in uppercase (with three characters) |                                                              |
+| MM                    | Month (01-12)                                                |                                                              |
+| RM                    | Month in Roman numerals (I-XII; I=JAN) and uppercase         |                                                              |
+| Day                   | DAY                                                          | Full spelling of a date in uppercase (9 characters are filled in if the value is empty.) |
+| DY                    | Day in abbreviated format in uppercase (with three characters) |                                                              |
+| DDD                   | Day in a year (001-366)                                      |                                                              |
+| DD                    | Day in a month (01-31)                                       |                                                              |
+| D                     | Day in a week (1-7).                                         |                                                              |
+| Week                  | W                                                            | Week in a month (1-5) (The first week starts from the first day of the month.) |
+| WW                    | Week in a year (1-53) (The first week starts from the first day of the year.) |                                                              |
+| IW                    | Week in an ISO year (The first Thursday is in the first week.) |                                                              |
+| Century               | CC                                                           | Century (with two digits) (The 21st century starts from 2001-01-01.) |
+| Julian date           | J                                                            | Julian date (starting from January 1 of 4712 BC)             |
+| Quarter               | Q                                                            | Quarter                                                      |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> In the table, the rules for RR to calculate years are as follows:
+>
+> - If the range of the input two-digit year is between 00 and 49:
+>   If the last two digits of the current year are between 00 and 49, the first two digits of the returned year are the same as the first two digits of the current year.
+>   If the last two digits of the current year are between 50 and 99, the first two digits of the returned year equal to the first two digits of the current year plus 1.
+> - If the range of the input two-digit year is between 50 and 99:
+>   If the last two digits of the current year are between 00 and 49, the first two digits of the returned year equal to the first two digits of the current year minus 1.
+> - If the last two digits of the current year are between 50 and 99, the first two digits of the returned year are the same as the first two digits of the current year.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/9-type-conversion-functions.md b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/9-type-conversion-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..ac782b9d6630a981230a3ca1d2634bc30b88fcdb
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/functions-and-operators/9-type-conversion-functions.md
@@ -0,0 +1,1416 @@
+---
+title: Type Conversion Functions
+summary: Type Conversion Functions
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Type Conversion Functions
+
+- cash_words(money)
+
+    Description: Type conversion function, which converts money into text.
+
+    Example:
+
+    ```sql
+    mogdb=# SELECT cash_words('1.23');
+                cash_words
+    -----------------------------------
+     One dollar and twenty three cents
+    (1 row)
+    ```
+
+- cast(x as y)
+
+  Description: Converts x into the type specified by y.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT cast('22-oct-1997' as timestamp);
+        timestamp
+  ---------------------
+   1997-10-22 00:00:00
+  (1 row)
+  ```
+
+- hextoraw(raw)
+
+  Description: Converts a string in hexadecimal format into the raw type.
+
+  Return type: raw
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT hextoraw('7D');
+   hextoraw
+  ----------
+   7D
+  (1 row)
+  ```
+
+- numtoday(numeric)
+
+  Description: Converts values of the number type into the timestamp of the specified type.
+
+  Return type: timestamp
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT numtoday(2);
+   numtoday
+  ----------
+   2 days
+  (1 row)
+  ```
+
+- pg_systimestamp()
+
+  Description: Obtains the system timestamp.
+
+  Return type: timestamp with time zone
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT pg_systimestamp();
+          pg_systimestamp
+  -------------------------------
+   2015-10-14 11:21:28.317367+08
+  (1 row)
+  ```
+
+- rawtohex(string)
+
+  Description: Converts a string in binary format into hexadecimal format.
+
+  The result is the ACSII code of the input characters in hexadecimal format.
+
+  Return type: varchar
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT rawtohex('1234567');
+      rawtohex
+  ----------------
+   31323334353637
+  (1 row)
+  ```
+
+- to_bigint(varchar)
+
+    Description: Converts the character type to the bigint type.
+
+    Return type: bigint
+
+    Example:
+
+    ```sql
+    mogdb=# SELECT to_bigint('123364545554455');
+        to_bigint
+    ----------------
+     123364545554455
+    (1 row)
+    ```
+
+- to_char (datetime/interval [, fmt]) <a id = 'to_char'> </a>
+
+  Description: Converts a DATETIME or INTERVAL value of the DATE/TIMESTAMP/TIMESTAMP WITH TIME ZONE/TIMESTAMP WITH LOCAL TIME ZONE type into the VARCHAR type according to the format specified by **fmt**.
+
+  - The optional parameter **fmt** allows for the following types: date, time, week, quarter, and century. Each type has a unique template. The templates can be combined together. Common templates include: HH, MM, SS, YYYY, MM, and DD.
+  - A template may have a modification word. FM is a common modification word and is used to suppress the preceding zero or the following blank spaces.
+  - For TIMESTAMP WITH TIME ZONE, you can use TZH, TZM, TZD, TZR parameters in TO_CHAR to output time zone information.
+  
+  Return type: varchar
+  
+  Example:
+  
+  ```sql
+  mogdb=# SELECT to_char(current_timestamp,'HH12:MI:SS');
+   to_char
+  ----------
+   10:19:26
+  (1 row)
+  ```
+  
+  ```sql
+  mogdb=# SELECT to_char(current_timestamp,'FMHH12:FMMI:FMSS');
+   to_char
+  ----------
+   10:19:46
+  (1 row)
+  ```
+  
+  ```sql
+  mogdb=# select to_char(systimestamp, 'TZH'); 
+  to_char
+  --------- 
+  +08
+  (1 row)
+  
+  mogdb=# select to_char(systimestamp, 'TZM');
+  to_char
+  ---------
+  00
+  (1 row)
+  
+  mogdb=# select to_char(systimestamp, 'TZD');
+  to_char
+  ---------
+  CST
+  (1 row)
+  
+  mogdb=# select to_char(systimestamp, 'TZR');
+  to_char
+  ---------------
+  Asia/Shanghai
+  (1 row)
+  ```
+  
+  **Table 1** Template Patterns for Date/Time Formatting
+  
+  | Pattern                          | Description                                                  |
+  | :------------------------------- | :----------------------------------------------------------- |
+  | `HH`                             | hour of day (01-12)                                          |
+  | `HH12`                           | hour of day (01-12)                                          |
+  | `HH24`                           | hour of day (00-23)                                          |
+  | `MI`                             | minute (00-59)                                               |
+  | `SS`                             | second (00-59)                                               |
+  | `MS`                             | millisecond (000-999)                                        |
+  | `US`                             | microsecond (000000-999999)                                  |
+  | `SSSS`                           | seconds past midnight (0-86399)                              |
+  | `AM`, `am`, `PM` or `pm`         | meridiem indicator (without periods)                         |
+  | `A.M.`, `a.m.`, `P.M.` or `p.m.` | meridiem indicator (with periods)                            |
+  | `Y,YYY`                          | year (4 or more digits) with comma                           |
+  | `YYYY`                           | year (4 or more digits)                                      |
+  | `YYY`                            | last 3 digits of year                                        |
+  | `YY`                             | last 2 digits of year                                        |
+  | `Y`                              | last digit of year                                           |
+  | `IYYY`                           | ISO 8601 week-numbering year (4 or more digits)              |
+  | `IYY`                            | last 3 digits of ISO 8601 week-numbering year                |
+  | `IY`                             | last 2 digits of ISO 8601 week-numbering year                |
+  | `I`                              | last digit of ISO 8601 week-numbering year                   |
+  | `BC`, `bc`, `AD` or `ad`         | era indicator (without periods)                              |
+  | `B.C.`, `b.c.`, `A.D.` or `a.d.` | era indicator (with periods)                                 |
+  | `MONTH`                          | full upper case month name (blank-padded to 9 chars)         |
+  | `Month`                          | full capitalized month name (blank-padded to 9 chars)        |
+  | `month`                          | full lower case month name (blank-padded to 9 chars)         |
+  | `MON`                            | abbreviated upper case month name (3 chars in English, localized lengths vary) |
+  | `Mon`                            | abbreviated capitalized month name (3 chars in English, localized lengths vary) |
+  | `mon`                            | abbreviated lower case month name (3 chars in English, localized lengths vary) |
+  | `MM`                             | month number (01-12)                                         |
+  | `DAY`                            | full upper case day name (blank-padded to 9 chars)           |
+  | `Day`                            | full capitalized day name (blank-padded to 9 chars)          |
+  | `day`                            | full lower case day name (blank-padded to 9 chars)           |
+  | `DY`                             | abbreviated upper case day name (3 chars in English, localized lengths vary) |
+  | `Dy`                             | abbreviated capitalized day name (3 chars in English, localized lengths vary) |
+  | `dy`                             | abbreviated lower case day name (3 chars in English, localized lengths vary) |
+  | `DDD`                            | day of year (001-366)                                        |
+  | `IDDD`                           | day of ISO 8601 week-numbering year (001-371; day 1 of the year is Monday of the first ISO week) |
+  | `DD`                             | day of month (01-31)                                         |
+  | `D`                              | day of the week, Sunday (`1`) to Saturday (`7`)              |
+  | `ID`                             | ISO 8601 day of the week, Monday (`1`) to Sunday (`7`)       |
+  | `W`                              | week of month (1-5) (the first week starts on the first day of the month) |
+  | `WW`                             | week number of year (1-53) (the first week starts on the first day of the year) |
+  | `IW`                             | week number of ISO 8601 week-numbering year (01-53; the first Thursday of the year is in week 1) |
+  | `CC`                             | century (2 digits) (the twenty-first century starts on 2001-01-01) |
+  | `J`                              | Julian Day (integer days since November 24, 4714 BC at midnight UTC) |
+  | `Q`                              | quarter                                                      |
+  | `RM`                             | month in upper case Roman numerals (I-XII; I=January)        |
+  | `rm`                             | month in lower case Roman numerals (i-xii; i=January)        |
+  | `TZ`                             | upper case time-zone abbreviation (only supported in `to_char`) |
+  | `tz`                             | lower case time-zone abbreviation (only supported in `to_char`) |
+  | `TZH`                            | Time zone hour                                               |
+  | `TZM`                            | Time zone minute                                             |
+  | `TZD`                            | Time zone daylight saving time                               |
+  | `TZR`                            | Time zone region                                             |
+
+- to_char(double precision/real, text)
+
+  Description: Converts the values of the floating point type into the strings in the specified format.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT to_char(125.8::real, '999D99');
+   to_char
+  ---------
+    125.80
+  (1 row)
+  ```
+
+- to_char (numeric/smallint/integer/bigint/double precision/real[, fmt])
+
+  Descriptions: Converts an integer or a value in floating point format into a string in specified format.
+
+  - The optional parameter **fmt** allows for the following types: decimal characters, grouping characters, positive/negative sign and currency sign. Each type has a unique template. The templates can be combined together. Common templates include: 9, 0, millesimal sign (,), and decimal point (.).
+  - A template can have a modification word, similar to FM. However, FM does not suppress 0 which is output according to the template.
+  - Use the template X or x to convert an integer value into a string in hexadecimal format.
+
+  Return type: varchar
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT to_char(1485,'9,999');
+   to_char
+  ---------
+    1,485
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT to_char( 1148.5,'9,999.999');
+    to_char
+  ------------
+    1,148.500
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT to_char(148.5,'990999.909');
+     to_char
+  -------------
+      0148.500
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT to_char(123,'XXX');
+   to_char
+  ---------
+     7B
+  (1 row)
+  ```
+
+- to_char(interval, text)
+
+  Description: Converts the values of the time interval type into the strings in the specified format.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT to_char(interval '15h 2m 12s', 'HH24:MI:SS');
+   to_char
+  ----------
+   15:02:12
+  (1 row)
+  ```
+
+- to_char(int, text)
+
+  Description: Converts the values of the integer type into the strings in the specified format.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT to_char(125, '999');
+   to_char
+  ---------
+    125
+  (1 row)
+  ```
+
+- to_char(numeric, text)
+
+  Description: Converts the values of the numeric type into the strings in the specified format.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT to_char(-125.8, '999D99S');
+   to_char
+  ---------
+   125.80-
+  (1 row)
+  ```
+
+- to_char (string)
+
+  Description: Converts the CHAR/VARCHAR/VARCHAR2/CLOB type into the VARCHAR type.
+
+  If this function is used to convert data of the CLOB type, and the value to be converted exceeds the value range of the target type, an error is returned.
+
+  Return type: varchar
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT to_char('01110');
+   to_char
+  ---------
+   01110
+  (1 row)
+  ```
+
+- to_char(timestamp, text)
+
+  Description: Converts the values of the timestamp type into the strings in the specified format.
+
+  Return type: text
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT to_char(current_timestamp, 'HH12:MI:SS');
+   to_char
+  ----------
+   10:55:59
+  (1 row)
+  ```
+
+- to_clob(char/nchar/varchar/varchar2/nvarchar2/text/raw)
+
+  Description: Converts the RAW type or text character set type CHAR/NCHAR/VARCHAR/VARCHAR2/NVARCHAR2/TEXT into the CLOB type.
+
+  Return type: clob
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT to_clob('ABCDEF'::RAW(10));
+   to_clob
+  ---------
+   ABCDEF
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT to_clob('hello111'::CHAR(15));
+   to_clob
+  ----------
+   hello111
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT to_clob('gauss123'::NCHAR(10));
+   to_clob
+  ----------
+   gauss123
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT to_clob('gauss234'::VARCHAR(10));
+   to_clob
+  ----------
+   gauss234
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT to_clob('gauss345'::VARCHAR2(10));
+   to_clob
+  ----------
+   gauss345
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT to_clob('gauss456'::NVARCHAR2(10));
+   to_clob
+  ----------
+   gauss456
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT to_clob('World222!'::TEXT);
+    to_clob
+  -----------
+   World222!
+  (1 row)
+  ```
+
+- to_date(text)
+
+  Description: Converts values of the text type into the timestamp in the specified format. Currently, only the following two formats are supported:
+
+  - Format 1: Date without separators, for example, 20150814. The value must contain the complete year, month, and day.
+  - Format 2: Date with separators, for example, 2014-08-14. The separator can be any non-digit character.
+
+  Return type: timestamp without time zone
+
+  Example:
+
+  ```sql
+    mogdb=# SELECT to_date('2015-08-14');
+           to_date
+    ---------------------
+     2015-08-14 00:00:00
+    (1 row)
+  ```
+
+- to_date(text, text)
+
+  Description: Converts the values of the string type into the dates in the specified format.
+
+  Return type: timestamp without time zone
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT to_date('05 Dec 2000', 'DD Mon YYYY');
+         to_date
+  ---------------------
+   2000-12-05 00:00:00
+  (1 row)
+  ```
+
+- to_number ( expr [, fmt])
+
+  Description: Converts **expr** into a value of the NUMBER type according to the specified format.
+
+  For details about the type conversion formats, see [Table 2](#template-patterns).
+
+  If a hexadecimal string is converted into a decimal number, the hexadecimal string can include a maximum of 16 bytes if it is to be converted into a sign-free number.
+
+  During the conversion from a hexadecimal string to a decimal digit, the format string cannot have a character other than x or X. Otherwise, an error is reported.
+
+  Return type: number
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT to_number('12,454.8-', '99G999D9S');
+   to_number
+  -----------
+    -12454.8
+  (1 row)
+  ```
+
+- to_number(text, text)
+
+  Description: Converts the values of the string type into the numbers in the specified format.
+
+  Return type: numeric
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT to_number('12,454.8-', '99G999D9S');
+   to_number
+  -----------
+    -12454.8
+  (1 row)
+  ```
+
+- to_timestamp(double precision)
+
+  Description: Converts a UNIX century into a timestamp.
+
+  Return type: timestamp with time zone
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT to_timestamp(1284352323);
+        to_timestamp
+  ------------------------
+   2010-09-13 12:32:03+08
+  (1 row)
+  ```
+
+- to_timestamp(string [,fmt])
+
+  Description: Converts a string into a value of the timestamp type according to the format specified by **fmt**. When **fmt** is not specified, perform the conversion according to the format specified by **nls_timestamp_format**.
+
+  In **to_timestamp** in MogDB,
+
+  - If the input year *YYYY* is 0, an error will be reported.
+  - If the input year *YYYY* is less than 0, specify *SYYYY* in **fmt**. The year with the value of n (an absolute value) BC will be output correctly.
+
+  Characters in the **fmt** must match the schema for formatting the data and time. Otherwise, an error is reported.
+
+  Return type: timestamp without time zone
+
+  Example:
+
+  ```sql
+  mogdb=# SHOW nls_timestamp_format;
+      nls_timestamp_format
+  ----------------------------
+   DD-Mon-YYYY HH:MI:SS.FF AM
+  (1 row)
+
+  mogdb=# SELECT to_timestamp('12-sep-2014');
+      to_timestamp
+  ---------------------
+   2014-09-12 00:00:00
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT to_timestamp('12-Sep-10 14:10:10.123000','DD-Mon-YY HH24:MI:SS.FF');
+        to_timestamp
+  -------------------------
+   2010-09-12 14:10:10.123
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT to_timestamp('-1','SYYYY');
+        to_timestamp
+  ------------------------
+   0001-01-01 00:00:00 BC
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT to_timestamp('98','RR');
+      to_timestamp
+  ---------------------
+   1998-01-01 00:00:00
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT to_timestamp('01','RR');
+      to_timestamp
+  ---------------------
+   2001-01-01 00:00:00
+  (1 row)
+  ```
+
+- to_timestamp(text, text)
+
+  Description: Converts values of the string type into the timestamp of the specified type.
+
+  Return type: timestamp
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT to_timestamp('05 Dec 2000', 'DD Mon YYYY');
+      to_timestamp
+  ---------------------
+   2000-12-05 00:00:00
+  (1 row)
+  ```
+
+**Table 2** Template patterns for numeric formatting<a id="template-patterns"> </a>
+
+| Pattern    | Description                                                  |
+| ---------- | ------------------------------------------------------------ |
+| 9          | Value with specified digits                                  |
+| 0          | Values with leading zeros                                    |
+| Period (.) | Decimal point                                                |
+| Comma (,)  | Group (thousand) separator                                   |
+| PR         | Negative values in angle brackets                            |
+| S          | Sign anchored to number (uses locale)                        |
+| L          | Currency symbol (uses locale)                                |
+| D          | Decimal point (uses locale)                                  |
+| G          | Group separator (uses locale)                                |
+| MI         | Minus sign in the specified position (if the number is less than 0) |
+| PL         | Plus sign in the specified position (if the number is greater than 0) |
+| SG         | Plus or minus sign in the specified position                 |
+| RN         | Roman numerals (the input values are between 1 and 3999)     |
+| TH or th   | Ordinal number suffix                                        |
+| V          | Shifts specified number of digits (decimal)                  |
+
+- abstime_text
+
+    Description: Converts abstime to text.
+
+    Parameter: abstime
+
+    Return type: text
+
+- abstime_to_smalldatetime
+
+    Description: Converts abstime to smalldatatime.
+
+    Parameter: abstime
+
+    Return type: smalldatetime
+
+- bigint_tid
+
+    Description: Converts bigint to tid.
+
+    Parameter: bigint
+
+    Return type: tid
+
+- bool_int1
+
+    Description: Converts bool to int1.
+
+    Parameter: Boolean
+
+    Return type: tinyint
+
+- bool_int2
+
+    Description: Converts bool to int2.
+
+    Parameter: Boolean
+
+    Return type: smallint
+
+- bool_int8
+
+    Description: Converts bool to int8.
+
+    Parameter: Boolean
+
+    Return type: bigint
+
+- bpchar_date
+
+    Description: Converts a string to a date.
+
+    Parameter: character
+
+    Return type: date
+
+- bpchar_float4
+
+    Description: Converts a string to float4.
+
+    Parameter: character
+
+    Return type: real
+
+- bpchar_float8
+
+    Description: Converts a string to float8.
+
+    Parameter: character
+
+    Return type: double precision
+
+- bpchar_int4
+
+    Description: Converts a string to int4.
+
+    Parameter: character
+
+    Return type: integer
+
+- bpchar_int8
+
+    Description: Converts a string to int8.
+
+    Parameter: character
+
+    Return type: bigint
+
+- bpchar_numeric
+
+    Description: Converts a string to numeric.
+
+    Parameter: character
+
+    Return type: numeric
+
+- bpchar_timestamp
+
+    Description: Converts a string to a timestamp.
+
+    Parameter: character
+
+    Return type: timestamp without time zone
+
+- bpchar_to_smalldatetime
+
+    Description: Converts a string to smalldatetime.
+
+    Parameter: character
+
+    Return type: smalldatetime
+
+- cupointer_bigint
+
+    Description: Converts the column-store CU pointer type to the bigint type.
+
+    Parameter: text
+
+    Return type: bigint
+
+- date_bpchar
+
+    Description: Converts the date type to bpchar.
+
+    Parameter: date
+
+    Return type: character
+
+- date_text
+
+    Description: Converts date to text.
+
+    Parameter: date
+
+    Return type: text
+
+- date_varchar
+
+    Description: Converts date to varchar.
+
+    Parameter: date
+
+    Return type: character varying
+
+- f4toi1
+
+    Description: Forcibly converts float4 to uint8.
+
+    Parameter: real
+
+    Return type: tinyint
+
+- f8toi1
+
+    Description: Forcibly converts float8 to uint8.
+
+    Parameter: double precision
+
+    Return type: tinyint
+
+- float4_bpchar
+
+    Description: Converts float4 to bpchar.
+
+    Parameter: real
+
+    Return type: character
+
+- float4_text
+
+    Description: Converts float4 to text.
+
+    Parameter: real
+
+    Return type: text
+
+- float4_varchar
+
+    Description: Converts float4 to varchar.
+
+    Parameter: real
+
+    Return type: character varying
+
+- float8_bpchar
+
+    Description: Converts float4 to bpchar.
+
+    Parameter: double precision
+
+    Return type: character
+
+- float8_interval
+
+    Description: Converts float4 to interval.
+
+    Parameter: double precision
+
+    Return type: interval
+
+- float8_text
+
+    Description: Converts float8 to text.
+
+    Parameter: double precision
+
+    Return type: text
+
+- float8_varchar
+
+    Description: Converts float8 to varchar.
+
+    Parameter: double precision
+
+    Return type: character varying
+
+- i1tof4
+
+    Description: Converts uint8 to float4.
+
+    Parameter: tinyint
+
+    Return type: real
+
+- i1tof8
+
+    Description: Converts uint8 to float8.
+
+    Parameter: tinyint
+
+    Return type: double precision
+
+- i1toi2
+
+    Description: Converts uint8 to int16.
+
+    Parameter: tinyint
+
+    Return type: smallint
+
+- i1toi4
+
+    Description: Converts uint8 to int32.
+
+    Parameter: tinyint
+
+    Return type: integer
+
+- i1toi8
+
+    Description: Converts uint8 to int64.
+
+    Parameter: tinyint
+
+    Return type: bigint
+
+- i2toi1
+
+    Description: Converts int16 to uint8.
+
+    Parameter: smallint
+
+    Return type: tinyint
+
+- i4toi1
+
+    Description: Converts int32 to uint8.
+
+    Parameter: integer
+
+    Return type: tinyint
+
+- i8toi1
+
+    Description: Converts int64 to uint8.
+
+    Parameter: bigint
+
+    Return type: tinyint
+
+- int1_avg_accum
+
+    Description: Adds the second parameter of the uint8 type to the first parameter. The first parameter is an array of the bigint type.
+
+    Parameter: bigint[], tinyint
+
+    Return type: bigint[]
+
+- int1_bool
+
+    Description: Converts uint8 to bool.
+
+    Parameter: tinyint
+
+    Return type: Boolean
+
+- int1_bpchar
+
+    Description: Converts uint8 to bpchar.
+
+    Parameter: tinyint
+
+    Return type: character
+
+- int1_mul_cash
+
+    Description: Returns the product of a parameter of the int8 type and a parameter of the cash type. The return type is cash.
+
+    Parameter: tinyint, money
+
+    Return type: money
+
+- int1_numeric
+
+    Description: Converts uint8 to numeric.
+
+    Parameter: tinyint
+
+    Return type: numeric
+
+- int1_nvarchar2
+
+    Description: Converts uint8 to nvarchar2.
+
+    Parameter: tinyint
+
+    Return type: nvarchar2
+
+- int1_text
+
+    Description: Converts uint8 to text.
+
+    Parameter: tinyint
+
+    Return type: text
+
+- int1_varchar
+
+    Description: Converts uint8 to varchar.
+
+    Parameter: tinyint
+
+    Return type: character varying
+
+- int1in
+
+    Description: Converts a string into an unsigned 1-byte integer.
+
+    Parameter: cstring
+
+    Return type: tinyint
+
+- int1out
+
+    Description: Converts an unsigned 1-byte integer into a string.
+
+    Parameter: tinyint
+
+    Return type: cstring
+
+- int1up
+
+    Description: Converts an input integer to an unsigned 1-byte integer.
+
+    Parameter: tinyint
+
+    Return type: tinyint
+
+- int2_bool
+
+    Description: Converts a signed two-byte integer to the bool type.
+
+    Parameter: smallint
+
+    Return type: Boolean
+
+- int2_bpchar
+
+    Description: Converts a signed two-byte integer to the bpchar type.
+
+    Parameter: smallint
+
+    Return type: character
+
+- int2_text
+
+    Description: Converts a signed two-byte integer to the text type.
+
+    Parameter: smallint
+
+    Return type: text
+
+- int2_varchar
+
+    Description: Converts a signed two-byte integer to the varchar type.
+
+    Parameter: smallint
+
+    Return type: character varying
+
+- int8_text
+
+    Description: Converts an eight-byte signed integer to the text type.
+
+    Parameter: bigint
+
+    Return type: text
+
+- int8_varchar
+
+    Description: Converts an eight-byte signed integer to varchar.
+
+    Parameter: bigint
+
+    Return type: character varying
+
+- intervaltonum
+
+    Description: Converts the internal dats type date to numeric.
+
+    Parameter: interval
+
+    Return type: numeric
+
+- numeric_bpchar
+
+    Description: Converts numeric to bpchar.
+
+    Parameter: numeric
+
+    Return type: character
+
+- numeric_int1
+
+    Description: Converts numeric to a signed one-byte integer.
+
+    Parameter: numeric
+
+    Return type: tinyint
+
+- numeric_text
+
+    Description: Converts numeric to text.
+
+    Parameter: numeric
+
+    Return type: text
+
+- numeric_varchar
+
+    Description: Converts numeric to varchar.
+
+    Parameter: numeric
+
+    Return type: character varying
+
+- nvarchar2in
+
+    Description: Converts c string to varchar.
+
+    Parameter: cstring, oid, integer
+
+    Return type: nvarchar2
+
+- nvarchar2out
+
+    Description: Converts text into a c string.
+
+    Parameter: nvarchar2
+
+    Return type: cstring
+
+- nvarchar2send
+
+    Description: Converts varchar to binary.
+
+    Parameter: nvarchar2
+
+    Return type: bytea
+
+- oidvectorin_extend
+
+    Description: Converts a string to oidvector.
+
+    Parameter: cstring
+
+    Return type: oidvector_extend
+
+- oidvectorout_extend
+
+    Description: Converts oidvector to a string.
+
+    Parameter: oidvector_extend
+
+    Return type: cstring
+
+- oidvectorsend_extend
+
+    Description: Converts oidvector to a string.
+
+    Parameter: oidvector_extend
+
+    Return type: bytea
+
+- reltime_text
+
+    Description: Converts reltime to text.
+
+    Parameter: reltime
+
+    Return type: text
+
+- text_date
+
+    Description: Converts the text type to the date type.
+
+    Parameter: text
+
+    Return type: date
+
+- text_float4
+
+    Description: Converts text to float4.
+
+    Parameter: text
+
+    Return type: real
+
+- text_float8
+
+    Description: Converts the text type to float8.
+
+    Parameter: text
+
+    Return type: double precision
+
+- text_int1
+
+    Description: Converts the text type to int1.
+
+    Parameter: text
+
+    Return type: tinyint
+
+- text_int2
+
+    Description: Converts the text type to the int2 type.
+
+    Parameter: text
+
+    Return type: smallint
+
+- text_int4
+
+    Description: Converts the text type to int4.
+
+    Parameter: text
+
+    Return type: integer
+
+- text_int8
+
+    Description: Converts the text type to the int8 type.
+
+    Parameter: text
+
+    Return type: bigint
+
+- text_numeric
+
+    Description: Converts the text type to the numeric type.
+
+    Parameter: text
+
+    Return type: numeric
+
+- text_timestamp
+
+    Description: Converts the text type to the timestamp type.
+
+    Parameter: text
+
+    Return type: timestamp without time zone
+
+- time_text
+
+    Description: Converts the time type to the text type.
+
+    Parameter: time without time zone
+
+    Return type: text
+
+- timestamp_text
+
+    Description: Converts the timestamp type to the text type.
+
+    Parameter: timestamp without time zone
+
+    Return type: text
+
+- timestamp_to_smalldatetime
+
+    Description: Converts the timestamp type to the smalldatetime type.
+
+    Parameter: timestamp without time zone
+
+    Return type: smalldatetime
+
+- timestamp_varchar
+
+    Description: Converts the timestamp type to varchar.
+
+    Parameter: timestamp without time zone
+
+    Return type: character varying
+
+- timestamptz_to_smalldatetime
+
+    Description: Converts timestamptz to smalldatetime.
+
+    Parameter: timestamp with time zone
+
+    Return type: smalldatetime
+
+- timestampzone_text
+
+    Description: Converts the timestampzone type to the text type.
+
+    Parameter: timestamp with time zone
+
+    Return type: text
+
+- timetz_text
+
+    Description: Converts the timetz type to the text type.
+
+    Parameter: time with time zone
+
+    Return type: text
+
+- to_integer
+
+    Description: Converts data to the integer type.
+
+    Parameter: character varying
+
+    Return type: integer
+
+- to_interval
+
+    Description: Converts to the interval type.
+
+    Parameter: character varying
+
+    Return type: interval
+
+- to_numeric
+
+    Description: Converts to the numeric type.
+
+    Parameter: character varying
+
+    Return type: numeric
+
+- to_nvarchar2
+
+    Description: Converts to the nvarchar2 type.
+
+    Parameter: numeric
+
+    Return type: nvarchar2
+
+- to_text
+
+    Description: Converts to the text type.
+
+    Parameter: smallint
+
+    Return type: text
+
+- to_ts
+
+    Description: Converts to the ts type.
+
+    Parameter: character varying
+
+    Return type: timestamp without time zone
+
+- to_varchar2
+
+    Description: Converts to the varchar2 type.
+
+    Parameter: timestamp without time zone
+
+    Return type: character varying
+
+- varchar_date
+
+    Description: Converts varchar to date.
+
+    Parameter: character varying
+
+    Return type: date
+
+- varchar_float4
+
+    Description: Converts varchar to float4.
+
+    Parameter: character varying
+
+    Return type: real
+
+- varchar_float8
+
+    Description: Converts the varchar type to the float8 type.
+
+    Parameter: character varying
+
+    Return type: double precision
+
+- varchar_int4
+
+    Description: Converts the type from varchar to int4.
+
+    Parameter: character varying
+
+    Return type: integer
+
+- varchar_int8
+
+    Description: Converts the varchar type to the int8 type.
+
+    Parameter: character varying
+
+    Return type: bigint
+
+- varchar_numeric
+
+    Description: Converts varchar to numeric.
+
+    Parameter: character varying
+
+    Return type: numeric
+
+- varchar_timestamp
+
+    Description: Converts varchar to timestamp.
+
+    Parameter: character varying
+
+    Return type: timestamp without time zone
+
+- varchar2_to_smlldatetime
+
+    Description: Converts varchar2 to smlldatetime.
+
+    Parameter: character varying
+
+    Return type: smalldatetime
+
+- xidout4
+
+    Description: The xid output is a four-byte number.
+
+    Parameter: xid32
+
+    Return type: cstring
+
+- xidsend4
+
+    Description: Converts xid to the binary format.
+
+    Parameter: xid32
+
+    Return type: bytea
+
+## Encoding Type Conversion
+
+- convert_to_nocase(text, text)
+
+    Description: Converts a string into a specified encoding type.
+
+    Return type: bytea
+
+    Example:
+
+    ```sql
+    mogdb=# SELECT convert_to_nocase('12345', 'GBK');
+     convert_to_nocase
+    -------------------
+     \x3132333435
+    (1 row)
+    ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/1-guc-parameter-usage.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/1-guc-parameter-usage.md
new file mode 100644
index 0000000000000000000000000000000000000000..2e3004b51e4cc31e670da9514ac7815f19af3ef1
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/1-guc-parameter-usage.md
@@ -0,0 +1,18 @@
+---
+title: GUC Parameter Usage
+summary: GUC Parameter Usage
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# GUC Parameter Usage
+
+A database provides many operation parameters. Configurations of these parameters affect the behavior of the database system. Before modifying these parameters, learn the impact of these parameters on the database. Otherwise, unexpected results may occur.
+
+**Precautions**
+
+- If the value range of a parameter is a string, the string should comply with the naming conventions of the path and file name in the OS running the target database.
+
+- If the maximum value of a parameter is *INT_MAX*, the maximum parameter value varies by OS.
+
+- If the maximum value of a parameter is *DBL_MAX*, the maximum parameter value varies by OS.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/1-logging-destination.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/1-logging-destination.md
new file mode 100644
index 0000000000000000000000000000000000000000..17c206d367060197bd9c0b74a2e413de60747b6d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/1-logging-destination.md
@@ -0,0 +1,175 @@
+---
+title: Logging Destination
+summary: Logging Destination
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Logging Destination
+
+## log_destination
+
+**Parameter description**: MogDB supports several methods of logging server messages. Set this parameter to a list of desired log destinations separated by commas. (For example, log_destination="stderr,csvlog")
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string
+
+The valid values are **stderr**, **csvlog**, and **syslog**.
+
+- **stderr** indicates that logs are printed to the screen.
+
+- **csvlog** indicates that logs are output in comma separated value (CSV) format. The prerequisite for generating logs in CSV format is that **[logging_collector](#logging_collector)** must be set to **on**. For details, see **Using CSV Log Output**.
+
+- **syslog** indicates that logs are recorded using the syslog of the OS. MogDB can record logs using syslog from **LOCAL0** to **LOCAL7**. For details, see **[syslog_facility](#syslog_facility)**. To record logs using syslog, add the following information to syslog daemon's configuration file:
+
+  ```
+  local0.*  /var/log/omm
+  ```
+
+**Default value:** **stderr**
+
+## logging_collector
+
+**Parameter description**: Specifies whether to enable the logger process to collect logs. This process captures log messages sent to **stderr** or **csvlog** and redirects them into log files.
+
+This method is more effective than recording logs to syslog because some types of messages cannot be displayed in syslog output, such as messages indicating the loading failures of dynamic link libraries and error messages generated by scripts (for example, **archive_command**).
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> It is possible to log to **stderr** without using the logging collector and the log messages will go to where the server's **stderr** is directed. However, this method is only suitable for low log volumes due to difficulties in rotating log files.
+
+**Value range**: Boolean
+
+- **on** indicates that the log collection is enabled.
+- **off** indicates that the log collection is disabled.
+
+**Default value**: **on**
+
+## log_directory
+
+**Parameter description**: Specifies the directory for storing log files when **logging_collector** is set to **on**. The value can be an absolute path, or relative to the data directory. This parameter can be modified using the **gs_guc reload** command.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - If this parameter is set to an invalid path, MogDB cannot be started.
+> - If you modify the **log_directory** parameter using the **gs_guc reload** command, and the specified path is valid, the log files are output to this new path. If the specified path is invalid, the log files are output to the valid path set last time and the database operation is not affected. The invalid value is still written into the configuration file.
+> - In the sandbox environment, the path cannot contain /var/chroot. For example, if the absolute path of log is **/var/chroot/var/lib/log/Ruby/pg_log/cn_log**, you only need to set the path to **/var/lib/log/Ruby/pg_log/cn_log**.
+>
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - Valid path: You have read and write permissions on the path.
+> - Invalid path: You do not have read or write permission on the path.
+
+**Value range**: a string
+
+**Default value**: specified during installation
+
+## log_filename
+
+**Parameter description**: Specifies the names of generated log files when **logging_collector** is set to **on**. The value is treated as a strftime pattern, so %-escapes can be used to specify time-varying file names.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - You are advised to use %-escapes to specify the log file names for efficient management of log files.
+> - If **log_destination** is set to **csvlog**, log files are output in CSV format with timestamped names, for example, **server_log.1093827753.csv**.
+
+**Value range**: a string
+
+**Default value**: **postgresql**-**%Y**-**%m**-**%d**_**%H%M%S.log**
+
+## log_file_mode
+
+**Parameter description**: Specifies the permissions of log files when **logging_collector** is set to **on**. The parameter value is usually a number in the format acceptable to the **chmod** and **umask** system calls.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - Before setting this parameter, set **log_directory** to store the logs to a directory other than the data directory.
+> - Do not make the log files world-readable because they might contain sensitive data.
+
+**Value range**: an octal integer ranging from 0000 to 0777 (that is, 0 to 511 in the decimal format)
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - **0600** indicates that log files are readable and writable only to the server administrator.
+> - **0640** indicates that log files are readable and writable to members of the administrator's group.
+
+**Default value:** **0600**
+
+## log_truncate_on_rotation
+
+**Parameter description**: Specifies the writing mode of the log files when **logging_collector** is set to **on**.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+A setting example is as follows:
+
+Assume that you want logs to be kept for 7 days, a log file generated each day to be named **server_log.Mon** on Monday, **server_log.Tue** on Tuesday, and so forth, and this week's log files to be overwritten by next week's log files. Then you can set **log_filename** to **server_log.%a**, **log_truncate_on_rotation** to **on**, and **log_rotation_age** to **1440** (indicating that the valid duration of the log file is 24 hours).
+
+**Value range**: Boolean
+
+- **on** indicates that MogDB overwrites the existing log files of the same name on the server.
+- **off** indicates that MogDB appends the logging messages to the existing log files of the same name on the server.
+
+**Default value**: **off**
+
+## log_rotation_age
+
+**Parameter description**: Specifies the interval for creating a log file when **logging_collector** is set to **on**. If the duration from the time when the last log file was created to the current time is greater than the value of **log_rotation_age**, a new log file will be generated.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 35791394. The unit is min. **0** indicates that the time-based creation of new log files is disabled.
+
+**Default value**: **1440**
+
+## log_rotation_size
+
+**Parameter description**: Specifies the maximum size of a server log file when **logging_collector** is set to **on**. If the total size of messages in a log file exceeds the specified value, a log file will be generated.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to_INT_MAX_/1024. The unit is KB.
+
+**0** indicates that the capacity-based creation of new log files is disabled.
+
+It is recommended that the unit of the value be MB or bigger, so that log files can be of proper size.
+
+**Default value:** **20MB**
+
+## syslog_facility
+
+**Parameter description**: Specifies the syslog facility to be used when **log_destination** is set to **syslog**.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: enumerated values. Valid values are **local0**, **local1**, **local2**, **local3**, **local4**, **local5**, **local6**, and **local7**.
+
+**Default value:** **local0**
+
+## syslog_ident
+
+**Parameter description**: Specifies the identifier of MogDB messages in syslog logs when **[log_destination](#log_destination)** is set to **syslog**.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string
+
+**Default value**: **postgres**
+
+## event_source
+
+**Parameter description**: This parameter takes effect only in a Windows environment and is not supported in MogDB. It specifies the identifier of MogDB messages in logs when **log_destination** is set to **eventlog**.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string
+
+**Default value**: **PostgreSQL**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/2-logging-time.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/2-logging-time.md
new file mode 100644
index 0000000000000000000000000000000000000000..ff167b4817360ea09ad0cb17529d93b6bf6d5023
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/2-logging-time.md
@@ -0,0 +1,115 @@
+---
+title: Logging Time
+summary: Logging Time
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Logging Time
+
+## client_min_messages
+
+**Parameter description**: Specifies which level of messages will be sent to the client. Each level covers all the levels following it. The lower the level is, the fewer messages are sent.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> A same value for **client_min_messages** and **[log_min_messages](#log_min_messages)** does not indicate the same level.
+
+**Value range**: enumerated values. Valid values are **debug**, **debug5**, **debug4**, **debug3**, **debug2**, **debug1**, **info**, **log**, **notice**, **warning**, **error**, **fatal**, and **panic**. For details about the parameter, see **Table 1 Message severity levels**. If the configured level is higher than **error**, for example, **fatal** or **panic**, the system changes the level to **error** by default.
+
+**Default value**: **notice**
+
+## log_min_messages
+
+**Parameter description**: Specifies which level of messages will be written into the server log. Each level covers all the levels following it. The lower the level is, the fewer messages will be written into the log.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> A same value for **[client_min_messages](#client_min_messages)** and **log_min_messages** does not indicate the same level.
+
+**Value range**: enumerated values. Valid values are **debug**, **debug5**, **debug4**, **debug3**, **debug2**, **debug1**, **info**, **log**, **notice**, **warning**, **error**, **fatal**, and **panic**. For details about the parameter, see **Table 1 Message severity levels**.
+
+**Default value**: **warning**
+
+## log_min_error_statement
+
+**Parameter description**: Controls which SQL statements that cause an error condition are recorded in the server log.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: enumerated values. Valid values are **debug**, **debug5**, **debug4**, **debug3**, **debug2**, **debug1**, **info**, **log**, **notice**, **warning**, **error**, **fatal**, and **panic**. For details about the parameter, see **Table 1 Message severity levels**.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - The default is **error**, indicating that statements causing errors, log messages, fatal errors, or panics will be logged.
+> - **panic** indicates that SQL statements that cause an error condition will not be logged.
+
+**Default value**: **error**
+
+## log_min_duration_statement
+
+**Parameter description**: Specifies the threshold for logging the duration of a completed statement. If a statement runs for a period longer than or equal to the specified value, its duration will be logged.
+
+Setting this parameter can be helpful in tracking down unoptimized queries. For clients using extended query protocols, the time required for parsing, binding, and executing steps are logged independently.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> When using this option together with **log_statement**, the text of statements that are logged because of **log_statement** will not be repeated in the duration log message. If you are not using **syslog**, it is recommended that you log the process ID (PID) or session ID using **log_line_prefix** so that you can link the statement message to the later duration message.
+
+**Value range**: an integer ranging from -1 to *INT_MAX*. The unit is ms.
+
+- If this parameter is set to **250**, all SQL statements that run for 250 ms or longer will be logged.
+- **0** indicates that the execution durations of all the statements are logged.
+- **-1** indicates that the duration logging is disabled.
+
+**Default value**: **30min**
+
+## backtrace_min_messages
+
+**Parameter description**: Prints the function's stack information to the server's log file if the information generated is greater than or equal to the level specified by this parameter.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> This parameter is used to locate problems on-site. Frequent stack printing will affect the system's overhead and stability. Therefore, set the value of this parameter to a rank other than **fatal** or **panic** during problem location.
+
+**Value range**: enumerated values
+
+Valid values are **debug**, **debug5**, **debug4**, **debug3**, **debug2**, **debug1**, **info**, **log**, **notice**, **warning**, **error**, **fatal**, and **panic**. For details about the parameter, see **Table 1 Message severity levels**.
+
+**Default value**: **panic**
+
+[Table 1](#Message severity levels) explains message severities used by MogDB. If logging output is sent to **syslog** or **eventlog**, the severities are translated as shown in the table. Note that **backtrace_min_messages** takes effect only in a Windows environment and is not supported in MogDB.
+
+**Table 1** Message severity levels<a id="Message severity levels"> </a>
+
+| Severity   | Description                                                  | System Log | Event Log   |
+| ---------- | ------------------------------------------------------------ | ---------- | ----------- |
+| debug[1-5] | Provides detailed debug information.                         | DEBUG      | INFORMATION |
+| log        | Reports information of interest to administrators, for example, checkpoint activity. | INFO       | INFORMATION |
+| info       | Provides information implicitly requested by users, for example, output from **VACUUM VERBOSE**. | INFO       | INFORMATION |
+| notice     | Provides information that might be helpful to users, for example, notice of truncation of long identifiers and index created as part of the primary key. | NOTICE     | INFORMATION |
+| warning    | Provides warnings of likely problems, for example, **COMMIT** outside a transaction block. | NOTICE     | WARNING     |
+| error      | Reports an error that causes a command to terminate.         | WARNING    | ERROR       |
+| fatal      | Reports the reason that causes a session to terminate.       | ERR        | ERROR       |
+| panic      | Reports an error that caused all database sessions to terminate. | CRIT       | ERROR       |
+
+## plog_merge_age
+
+**Parameter description**: Specifies the output period of performance log data.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> The parameter value is in milliseconds. You are advised to set it to a multiple of 1000. That is, the value is in seconds. The performance log files controlled by this parameter are stored in the **$GAUSSLOG/gs_profile/**&lt;*node_name*&gt; directory in .prf format. *node_name* is the value of **pgxc_node_name** in the **postgres.conf** file.
+
+**Value range**: an integer ranging from 0 to 2147483647. The unit is ms.
+
+**0** indicates that the current session will not log performance data. A value other than 0 indicates that the current session will log performance data based on the period specified by this parameter.
+
+A small value indicates that much data is logged, which seriously affects performance.
+
+**Default value**: **0**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/3-logging-content.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/3-logging-content.md
new file mode 100644
index 0000000000000000000000000000000000000000..04ab0cc041292801e24256e53fd0d6fe92833ff2
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/3-logging-content.md
@@ -0,0 +1,334 @@
+---
+title: Logging Content
+summary: Logging Content
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Logging Content
+
+## debug_print_parse
+
+**Parameter description**: Specifies whether to print parsing tree results.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the printing is enabled.
+- **off** indicates that the printing is disabled.
+
+**Default value**: **off**
+
+## debug_print_rewritten
+
+**Parameter description**: Specifies whether to print query rewriting results.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the printing is enabled.
+- **off** indicates that the printing is disabled.
+
+**Default value**: **off**
+
+## debug_print_plan
+
+**Parameter description**: Used to set whether to print the execution plan of the query to the log.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the printing is enabled.
+- **off** indicates that the printing is disabled.
+
+**Default value**: **off**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - Debugging information about **debug_print_parse**, **debug_print_rewritten**, and **debug_print_plan** are printed only when the log level is set to **log** or higher. When these parameters are set to **on**, their debugging information will be recorded in server logs and will not be sent to client logs. You can change the log level by setting **client_min_messages** and **log_min_messages**.
+> - Do not invoke the **gs_encrypt_aes128** and **gs_decrypt_aes128** functions when **debug_print_plan** is set to **on**, preventing the risk of sensitive information disclosure. You are advised to filter parameter information of the **gs_encrypt_aes128** and **gs_decrypt_aes128** functions in the log files generated when **debug_print_plan** is set to **on** before providing the log files to external maintenance engineers for fault locating. After you finish using the logs, delete them as soon as possible.
+
+## debug_pretty_print
+
+**Parameter description**: Indents the logs produced by **debug_print_parse**, **debug_print_rewritten**, and **debug_print_plan**. The output format is more readable but much longer than that generated when this parameter is set to **off**.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the indentation is enabled.
+- **off** indicates that the indentation is disabled.
+
+**Default value**: **on**
+
+## log_checkpoints
+
+**Parameter description**: Specifies whether the statistics on checkpoints and restart points are recorded in the server logs. When this parameter is set to **on**, statistics on checkpoints and restart points are recorded in the log messages, including the number of buffers written and the time spent in writing them.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the statistics on checkpoints and restart points are recorded in the server logs.
+- **off** indicates that the statistics on checkpoints and restart points are not recorded in the server logs.
+
+**Default value**: **off**
+
+## log_connections
+
+**Parameter description**: Specifies whether to record connection request information of the client.
+
+This parameter is a BACKEND parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> Some client programs, such as gsql, attempt to connect twice while determining if a password is required. In this case, duplicate "connection receive" messages do not necessarily indicate a problem.
+
+**Value range**: Boolean
+
+- **on** indicates that the request information is recorded.
+- **off** indicates that the request information is not recorded.
+
+**Default value**: **off**
+
+## log_disconnections
+
+**Parameter description**: Specifies whether to record disconnection request information of the client.
+
+This parameter is a BACKEND parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the request information is recorded.
+- **off** indicates that the request information is not recorded.
+
+**Default value**: **off**
+
+## log_duration
+
+**Parameter description**: Specifies whether to record the duration of every completed SQL statement. For clients using extended query protocols, the time required for parsing, binding, and executing steps are logged independently.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- This option records the query duration whereas **log_min_duration_statement** logs both the duration and text of a query that exceeds the value set by **log_min_duration_statement**.
+- If this parameter is set to **on** and **log_min_duration_statement** is set to a positive value, the duration of each completed statement is logged but the query text is included only for statements exceeding the threshold. This behavior can be used for gathering statistics in high-load situation.
+
+**Default value**: **on**
+
+## log_error_verbosity
+
+**Parameter description**: Specifies the amount of detail written in the server log for each message that is logged.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: enumerated values
+
+- **terse** indicates that the output excludes the DETAIL, HINT, QUERY, and CONTEXT error information.
+- **verbose** indicates that the output includes the SQLSTATE error code, the source code file name, function name, and number of the line in which the error occurs.
+- **default** indicates that the output includes the DETAIL, HINT, QUERY, and CONTEXT error information, and excludes the SQLSTATE error code, the source code file name, function name, and number of the line in which the error occurs.
+
+**Default value**: **default**
+
+## log_hostname
+
+**Parameter description**: By default, connection log messages only show the IP address of the connecting host. The host name can be recorded when this parameter is set to **on**. It may take some time to parse the host name. Therefore, the database performance may be affected.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the host name is simultaneously recorded.
+- **off** indicates that the host name is not simultaneously recorded.
+
+**Default value**: **on**
+
+## log_line_prefix
+
+**Parameter description**: Specifies the prefix format of each log information. A prefix is a printf-style string that is output at the beginning of each line of the log. The "escape sequences" which begin with **%** are replaced with status information as listed in [Table 1](#Escape characters).
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Table 1** Escape characters<a id="Escape characters"> </a>
+
+| Escape Character | Effect                                                       |
+| ---------------- | ------------------------------------------------------------ |
+| %a               | Application name                                             |
+| %u               | Username                                                     |
+| %d               | Database name                                                |
+| %r               | Remote host name or IP address and remote port. If **log_hostname** is set to **off**, only the IP address and remote port are displayed. |
+| %h               | Remote host name or IP address. If **log_hostname** is set to **off**, only the IP address is displayed. |
+| %p               | Thread ID                                                    |
+| %t               | Time stamp without milliseconds                              |
+| %m               | Time stamp with milliseconds                                 |
+| %n               | Node from which an error is reported                         |
+| %i               | Command tag: type of command executed in the current session |
+| %e               | SQLSTATE error code                                          |
+| %c               | Session ID: For details, see the note below the table.       |
+| %l               | Number of the log line for each session or thread, starting at 1 |
+| %s               | Process startup time                                         |
+| %v               | Virtual transaction ID (backendID/ localXID)                 |
+| %x               | Transaction ID (**0** indicates that no transaction ID is assigned) |
+| %q               | Produces no output. If the current thread is a backend thread, this escape sequence is ignored and subsequent escape sequences are processed. Otherwise, this escape sequence and subsequent escape sequences are all ignored. |
+| %S               | session ID                                                   |
+| %%               | The character %                                              |
+
+The %c escape character prints a unique session ID consisting of two 4-byte hexadecimal numbers separated by a period (.). The numbers are the process startup time and the process ID. Therefore, %c can also be used as a space saving way of printing those items. For example, run the following query to generate the session ID from **pg_stat_activity**:
+
+```
+SELECT to_hex(EXTRACT(EPOCH FROM backend_start)::integer) || '.' ||
+       to_hex(pid)
+FROM pg_stat_activity;
+```
+
+- If you set a nonempty value for **log_line_prefix**, you should usually make its last character be a space, to provide visual separation from the rest of the log line. A punctuation character can be used, too.
+- Syslog generates its own time stamp and process ID information. Therefore, you do not need to include those escapes characters when you are logging in to syslog.
+
+**Value range**: a string
+
+**Default value**: **%m %c %d %p %a %x %n %e**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> The default value will be changed when **gs_initdb** is used to set system environments.
+
+**%m %c %d %p %a %x %n %e** indicates that session timestamps, session IDs, database names, thread IDs, application names, transaction IDs, error reporting nodes, and SQLSTATE error codes will be added to the beginning of log lines.
+
+## log_lock_waits
+
+**Parameter description**: If the time for which a session waits to acquire a lock is longer than the value of **deadlock_timeout**, this parameter specifies whether to record this message in the database. This is useful in determining if lock waits are causing poor performance.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the information is recorded.
+- **off** indicates that the information is not recorded.
+
+**Default value**: **off**
+
+## log_statement
+
+**Parameter description**: Specifies which SQL statements are recorded. For clients using extended query protocols, logging occurs when an Execute message is received, and values of the Bind parameters are included (with any embedded single quotation marks doubled).
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> Statements that contain simple syntax errors are not logged even if **log_statement** is set to **all**, because the log message is emitted only after basic parsing has been completed to determine the statement type. If an extended query protocol is used, statements that fail before the execution phase (during parse analysis or planning) are not logged, either. Set **log_min_error_statement** to **ERROR** or lower to log such statements.
+
+**Value range**: enumerated values
+
+- **none** indicates that no statement is recorded.
+- **ddl** indicates that all data definition statements, such as CREATE, ALTER, and DROP, are recorded.
+- **mod** indicates that all DDL statements and data modification statements, such as INSERT, UPDATE, DELETE, TRUNCATE, and COPY FROM, are recorded.
+- **all** indicates that all statements, including the PREPARE, EXECUTE, and EXPLAIN ANALYZE statements, are recorded.
+
+**Default value**: **none**
+
+## log_temp_files
+
+**Parameter description**: Specifies whether to record the deletion information of temporary files. Temporary files can be created for sorting, hashing, and storing temporary querying results. If the recording is enabled, a log entry is generated for each temporary file when it is deleted.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from -1 to 2147483647. The unit is KB.
+
+- A positive value indicates that the deletion information of temporary files whose size is larger than the specified value of **log_temp_files** is recorded.
+- **0** indicates that the delete information of all temporary files is recorded.
+- **-1** indicates that the delete information of any temporary files is not recorded.
+
+**Default value**: **-1**
+
+## log_timezone
+
+**Parameter description**: Specifies the time zone used for timestamps written in the server log. Different from **TimeZone**, this parameter takes effect for all sessions in the database.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string
+
+**Default value**: **PRC**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> The default value will be changed when **gs_initdb** is used to set system environments.
+
+## logging_module
+
+**Parameter description**: Specifies whether module logs are output on the server. This parameter is a session-level parameter, and you are advised not to use the **gs_guc** tool to set it.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string
+
+**Default value**: **off**. All the module logs are not output on the server. You can view the logs by running **show logging_module**. Example modules are displayed as follows: ALL,on(),off(DFS,GUC,ORC,SLRU,MEM_CTL,AUTOVAC,CACHE,ADIO,SSL,TBLSPC,WLM,EXECUTOR,OPFUSION,VEC_EXECUTOR,LLVM,OPT,OPT_REWRITE,OPT_JOIN,OPT_AGG,OPT_SUBPLAN,OPT_SETOP,OPT_SKEW,UDF,COOP_ANALYZE,WLMCP,ACCELERATE,,PLANHINT,SNAPSHOT,XACT,HANDLE,CLOG,EC,REMOTE,CN_RETRY,PLSQL,TEXTSEARCH,SEQ,REDO,FUNCTION,PARSER,INSTR,INCRE_CKPT,DBL_WRT,RTO,HEARTBEAT).
+
+**Setting method**: Run **show logging_module** to view which modules are controllable. For example, the query output result is as follows:
+
+```
+mogdb=# show logging_module;
+logging_module
+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+ALL,on(),off(DFS,GUC,ORC,SLRU,MEM_CTL,AUTOVAC,CACHE,ADIO,SSL,TBLSPC,WLM,EXECUTOR,VEC_EXECUTOR,LLVM,OPT,OPT_REWRITE,OPT_JOIN,OPT_AGG,OPT_SUBPLAN,OPT_SETOP,OPT_SKEW,UDF,COOP_ANALYZE,WLMCP,ACCELERATE,T,PLANHINT,SNAPSHOT,XACT,HANDLE,CLOG,EC,REMOTE,CN_RETRY,PLSQL,TEXTSEARCH,SEQ,REDO,FUNCTION,PARSER,INSTR,INCRE_CKPT,DBL_WRT,RTO,HEARTBEAT)
+(1 row)
+```
+
+Controllable modules are identified by uppercase letters, and the special ID **ALL** is used for setting all module logs. You can control the output of module logs by setting **logging_module** to **on** or **off**. Enable log output for SSL:
+
+```
+mogdb=# set logging_module='on(SSL)';
+SET
+mogdb=# show logging_module;                                                                                                                                              logging_module
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ALL,on(SSL),off(DFS,GUC,ORC,SLRU,MEM_CTL,AUTOVAC,CACHE,ADIO,TBLSPC,WLM,EXECUTOR,VEC_EXECUTOR,LLVM,OPT,OPT_REWRITE,OPT_JOIN,OPT_AGG,OPT_SUBPLAN,OPT_SETOP,OPT_SKEW,UDF,COOP_ANALYZE,WLMCP,ACCELERATE,,PLANHINT,SNAPSHOT,XACT,HANDLE,CLOG,EC,REMOTE,CN_RETRY,PLSQL,TEXTSEARCH,SEQ,REDO,FUNCTION,PARSER,INSTR,INCRE_CKPT,DBL_WRT,RTO,HEARTBEAT,COMM_IPC,COMM_PARAM)
+(1 row)
+```
+
+SSL log output is enabled.
+
+The **ALL** identifier can be used to quickly enable or disable log output for all modules.
+
+```
+mogdb=# set logging_module='off(ALL)';
+SET
+mogdb=# show logging_module;                                                                                                                                                logging_module
+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ALL,on(),off(DFS,GUC,ORC,SLRU,MEM_CTL,AUTOVAC,CACHE,ADIO,SSL,TBLSPC,WLM,EXECUTOR,VEC_EXECUTOR,LLVM,OPT,OPT_REWRITE,OPT_JOIN,OPT_AGG,OPT_SUBPLAN,OPT_SETOP,OPT_SKEW,UDF,COOP_ANALYZE,WLMCP,ACCELERATE,PLANHINT,SNAPSHOT,XACT,HANDLE,CLOG,EC,REMOTE,CN_RETRY,PLSQL,TEXTSEARCH,SEQ,REDO,FUNCTION,PARSER,INSTR,INCRE_CKPT,DBL_WRT,RTO,HEARTBEAT)
+(1 row)
+
+mogdb=# set logging_module='on(ALL)';
+SET
+mogdb=# show logging_module;                                                                                                                                               logging_module
+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ALL,on(DFS,GUC,ORC,SLRU,MEM_CTL,AUTOVAC,CACHE,ADIO,SSL,TBLSPC,WLM,EXECUTOR,VEC_EXECUTOR,LLVM,OPT,OPT_REWRITE,OPT_JOIN,OPT_AGG,OPT_SUBPLAN,OPT_SETOP,OPT_SKEW,UDF,COOP_ANALYZE,WLMCP,ACCELERATE,PLANHINT,SNAPSHOT,XACT,HANDLE,CLOG,EC,REMOTE,CN_RETRY,PLSQL,TEXTSEARCH,SEQ,REDO,FUNCTION,PARSER,INSTR,INCRE_CKPT,DBL_WRT,RTO,HEARTBEAT),off()
+(1 row)
+```
+
+**Dependency**: The value of this parameter depends on the settings of **log_min_messages**.
+
+## opfusion_debug_mode
+
+**Parameter description**: Checks whether simple queries are optimized for debugging. If this parameter is set to **log**, you can view the specific reasons why queries are not optimized in the execution plans of database nodes.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: enumerated values
+
+- **off** indicates that reasons why queries are not optimized are not included.
+- **log** indicates that reasons why queries are not optimized are included in the execution plans of database nodes.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> To view the reasons why queries are not optimized in the log, set **opfusion_debug_mode** to **log**, **log_min_messages** to **debug4**, and **logging_module** to **on(OPFUSION)**. Note that a large amount of log messages may be generated. Therefore, execute only a small number of jobs during debugging.
+
+**Default value**: **off**
+
+## enable_debug_vacuum
+
+**Parameter description**: Specifies whether to allow output of some VACUUM-related logs for problem locating. This parameter is used only by developers. Common users are advised not to use it.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on/true** indicates that output of VACUUM-related logs is allowed.
+- **off/false** indicates that output of VACUUM-related logs is disallowed.
+
+**Default value**: **off**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/4-using-csv-log-output.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/4-using-csv-log-output.md
new file mode 100644
index 0000000000000000000000000000000000000000..4d77a6529893242f35107a51e7df0df8fdb0bc13
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/4-using-csv-log-output.md
@@ -0,0 +1,88 @@
+---
+title: Using CSV Log Output
+summary: Using CSV Log Output
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Using CSV Log Output
+
+**Prerequisites**
+
+- The **log_destination** parameter is set to **csvlog**.
+- The **logging_collector** parameter is set to **on**.
+
+**Definition of csvlog**
+
+Log lines are emitted in comma separated values (CSV) format.
+
+An example table definition for storing CSV-format log output is shown as follows:
+
+```
+CREATE TABLE gaussdb_log
+(
+log_time timestamp(3) with time zone,
+node_name text,
+user_name text,
+database_name text,
+process_id bigint,
+connection_from text,
+"session_id" text,
+session_line_num bigint,
+command_tag text,
+session_start_time timestamp with time zone,
+virtual_transaction_id text,
+transaction_id bigint,
+query_id bigint,
+module text,
+error_severity text,
+sql_state_code text,
+message text,
+detail text,
+hint text,
+internal_query text,
+internal_query_pos integer,
+context text,
+query text,
+query_pos integer,
+location text,
+application_name text
+);
+```
+
+For details, see [Table 1](#meaning).
+
+**Table 1** Meaning of each csvlog field<a id="meaning"> </a>
+
+| Column                 | Description                     | Column             | Description                                                  |
+| :--------------------- | :------------------------------ | :----------------- | :----------------------------------------------------------- |
+| log_time               | Timestamp in milliseconds       | module             | Module to which the log belongs.                             |
+| node_name              | Node name                       | error_severity     | ERRORSTATE code                                              |
+| user_name              | Username                        | sql_state_code     | SQLSTATE code                                                |
+| database_name          | Database name                   | message            | Error message                                                |
+| process_id             | Process ID                      | detail             | Detailed error message                                       |
+| connection_from        | Port number of the client host  | hint               | Prompt message                                               |
+| session_id             | Session ID                      | internal_query     | Internal query (This field is used to query the information leading to errors if any.) |
+| session_line_num       | Number of lines in each session | internal_query_pos | Pointer for an internal query                                |
+| command_tag            | Command tag                     | context            | Environment                                                  |
+| session_start_time     | Start time of a session         | query              | Character count at the position where errors occur           |
+| virtual_transaction_id | Regular transaction             | query_pos          | Pointer at the position where errors occur                   |
+| transaction_id         | Transaction ID                  | location           | Position where errors occur in the MogDB source code if **log_error_verbosity** is set to **verbose** |
+| query_id               | Query ID                        | application_name   | Application name                                             |
+
+Run the following command to import a log file to this table:
+
+```
+COPY gaussdb_log FROM '/opt/data/pg_log/logfile.csv' WITH csv;
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> The log name (**logfile.csv**) here needs to be replaced with the name of a log generated.
+
+**Simplifying Input**
+
+Simplify importing CSV log files by performing the following operations:
+
+- Set **log_filename** and **log_rotation_age** to provide a consistent, predictable naming solution for log files. By doing this, you can predict when an individual log file is complete and ready to be imported.
+- Set **log_rotation_size** to **0** to disable size-based log rollback, as it makes the log file name difficult to predict.
+- Set **log_truncate_on_rotation** to **on** so that old log data cannot be mixed with the new one in the same file.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/11-alarm-detection.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/11-alarm-detection.md
new file mode 100644
index 0000000000000000000000000000000000000000..c56da191efa6e3826271c60aefae7e4739ddf9be
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/11-alarm-detection.md
@@ -0,0 +1,73 @@
+---
+title: Alarm Detection
+summary: Alarm Detection
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Alarm Detection
+
+During the running of the MogDB, error scenarios can be detected and informed to users in time.
+
+## enable_alarm
+
+**Parameter description**: Specifies whether to enable the alarm detection thread to detect fault scenarios that may occur in the database.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the alarm detection thread is enabled.
+- **off** indicates that the alarm detection thread is disabled.
+
+**Default value**: **on**
+
+## connection_alarm_rate
+
+**Parameter description**: Specifies the ratio restriction on the maximum number of allowed parallel connections to the database. The maximum number of concurrent connections to the database is **max_connections** x **connection_alarm_rate**.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range:** a floating point number ranging from 0.0 to 1.0
+
+**Default value**: **0.9**
+
+## alarm_report_interval
+
+**Parameter description**: specifies the interval at which an alarm is reported.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer. The unit is s.
+
+**Default value:** **10**
+
+## alarm_component
+
+**Parameter description**: Certain alarms are suppressed during alarm reporting. That is, the same alarm will not be repeatedly reported by an instance within the period specified by **alarm_report_interval**. Its default value is **10s**. In this case, the parameter specifies the location of the alarm component that is used to process alarm information.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string
+
+**Default value**: **/opt/huawei/snas/bin/snas_cm_cmd**
+
+## table_skewness_warning_threshold
+
+**Parameter description**: Specifies the threshold for triggering a table skew alarm.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a floating point number ranging from 0 to 1
+
+**Default value**: **1**
+
+## table_skewness_warning_rows
+
+**Parameter description**: Specifies the minimum number of rows for triggering a table skew alarm.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to *INT_MAX*
+
+**Default value**: **100000**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/12-statistics-during-the-database-running/1-query-and-index-statistics-collector.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/12-statistics-during-the-database-running/1-query-and-index-statistics-collector.md
new file mode 100644
index 0000000000000000000000000000000000000000..45078ef74b56e84fafa8dc8eb26373e3899815a2
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/12-statistics-during-the-database-running/1-query-and-index-statistics-collector.md
@@ -0,0 +1,139 @@
+---
+title: Query and Index Statistics Collector
+summary: Query and Index Statistics Collector
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Query and Index Statistics Collector
+
+The query and index statistics collector is used to collect statistics during database running. The statistics include the times of inserting and updating a table and index, the number of disk blocks and tuples, and the time required for the last cleanup and analysis on each table. The statistics can be viewed by querying system view families pg_stats and pg_statistic. The following parameters are used to set the statistics collection feature in the server scope.
+
+## track_activities
+
+**Parameter description:** Collects statistics about the commands that are being executed in session.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the statistics collection function is enabled.
+- **off** indicates that the statistics collection function is disabled.
+
+**Default value**: **on**
+
+## track_counts
+
+**Parameter description:** Collects statistics about database activities.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the statistics collection function is enabled.
+- **off** indicates that the statistics collection function is disabled.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> When the database to be cleaned up is selected from the AutoVacuum automatic cleanup process, the database statistics are required. In this case, the default value is set to **on**.
+
+**Default value**: **on**
+
+## track_io_timing
+
+**Parameter description:** Collects statistics about I/O timing in the database. The I/O timing statistics can be queried by using the **pg_stat_database** parameter.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- If this parameter is set to **on**, the collection function is enabled. In this case, the collector repeatedly queries the operating system at the current time. As a result, large number of costs may occur on some platforms. Therefore, the default value is set to **off**.
+- **off** indicates that the statistics collection function is disabled.
+
+**Default value**: **off**
+
+## track_functions
+
+**Parameter description:** Collects statistics of the number and duration of function invocations.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> When the SQL functions are set to inline functions queried by the invoking, these SQL functions cannot be traced no matter these functions are set or not.
+
+**Value range**: enumerated values
+
+- **pl** indicates that only procedural language functions are traced.
+- **all** indicates that SQL language functions area traced.
+- **none** indicates that the function tracing function is disabled.
+
+**Default value**: **none**
+
+## track_activity_query_size
+
+**Parameter description**: Specifies byte counts of the current running commands used to trace each active session.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 100 to 102400
+
+**Default value:** **1024**
+
+## stats_temp_directory
+
+**Parameter description**: Specifies the directory for saving temporary statistics.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> If a RAM-based file system directory is used, the actual I/O cost can be lowered and the performance can be improved.
+
+**Value range**: a string
+
+**Default value**: **pg_stat_tmp**
+
+## track_thread_wait_status_interval
+
+**Parameter description**: Specifies the interval of collecting the thread status information.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: 0 to 1 day. The unit is min.
+
+**Default value**: **30min**
+
+## enable_save_datachanged_timestamp
+
+**Parameter description**: Specifies whether to record the time when **INSERT**, **UPDATE**, **DELETE**, or **EXCHANGE**/**TRUNCATE**/**DROP** **PARTITION** is performed on table data.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the time when an operation is performed on table data will be recorded.
+- **off** indicates that the time when an operation is performed on table data will not be recorded.
+
+**Default value**: **on**
+
+## track_sql_count
+
+**Parameter description**: Collects statistics about the statements (**SELECT**, **INSERT**, **UPDATE**, **MERGE INTO**, and **DELETE**) that are being executed in a session.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the statistics collection function is enabled.
+- **off** indicates that the auditing function is disabled.
+
+**Default value: on**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - The **track_sql_count** parameter is restricted by the **track_activities** parameter when the **gs_sql_count** or **pgxc_sql_count** view is queried.
+> - If **track_activities** is set to **on** and **track_sql_count** is set to **off**, a warning message indicating that **track_sql_count** is disabled will be displayed in logs when the **gs_sql_count**view is queried.
+> - If both **track_activities** and **track_sql_count** are set to **off**, two warning messages indicating that **track_activities** is disabled and **track_sql_count** is disabled will be displayed in logs when the views are queried.
+> - If **track_activities** is set to **off** and **track_sql_count** is set to **on**, a warning message indicating that **track_activities** is disabled will be displayed in logs when the views are queried.
+> - If **track_sql_count** is set to **off**, querying the **gs_sql_count** or **pgxc_sql_count** view returns **0**.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/12-statistics-during-the-database-running/2-performance-statistics.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/12-statistics-during-the-database-running/2-performance-statistics.md
new file mode 100644
index 0000000000000000000000000000000000000000..3d9c597ad1363dd6ed440eb41113c57c23b34950
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/12-statistics-during-the-database-running/2-performance-statistics.md
@@ -0,0 +1,35 @@
+---
+title: Performance Statistics
+summary: Performance Statistics
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Performance Statistics
+
+During the running of the database, the lock access, disk I/O operation, and invalid message processing are involved. All these operations are the bottleneck of the database performance. The performance statistics provided by MogDB can facilitate the performance fault location.
+
+## Generating Performance Statistics Logs
+
+**Parameter description**: For each query, the following four parameters record the performance statistics of corresponding modules in the server log:
+
+- The **og_parser_stats** parameter records the performance statistics of a parser in the server log.
+- The **log_planner_stats** parameter records the performance statistics of a query optimizer in the server log.
+- The **log_executor_stats** parameter records the performance statistics of an executor in the server log.
+- The **log_statement_stats** parameter records the performance statistics of the whole statement in the server log.
+
+All these parameters can only provide assistant analysis for administrators, which are similar to the getrusage() of the Linux OS.
+
+These parameters are SUSET parameters. Set them based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - The **log_statement_stats** records the total statement statistics whereas other parameters record statistics only about their corresponding modules.
+> - The **log_statement_stats** parameter cannot be enabled together with any parameter recording statistics about a module.
+
+**Value range**: Boolean
+
+- **on** indicates that performance statistics are recorded.
+- **off** indicates that performance statistics are not recorded.
+
+**Default value**: **off**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/13-load-management.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/13-load-management.md
new file mode 100644
index 0000000000000000000000000000000000000000..287f289462f6cb3581f14cbe46c27f40161e9c2b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/13-load-management.md
@@ -0,0 +1,392 @@
+---
+title: Load Management
+summary: Load Management
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Load Management
+
+If database resource usage is not controlled, concurrent tasks easily preempt resources. As a result, the OS will be overloaded and cannot respond to user tasks; or even crash and cannot provide any services to users. The MogDB workload management balances the database workload based on available resources to prevent database overloads.
+
+## use_workload_manager
+
+**Parameter description**: specifies whether to enable the resource management function.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates the resource management function is enabled.
+
+- **off** indicates the resource management function is disabled.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > - If method 2 in Table 2 [Methods for setting GUC parameters](30-appendix) is used to change the parameter value, the new value takes effect only for the threads that are started after the change. In addition, the new value does not take effect for new jobs that are executed by backend threads and reused threads. You can make the new value take effect for these threads by using **kill session** or restarting the node.
+  > - After the value of **use_workload_manager** changes from **off** to **on**, statistics about storage resources when **use_workload_manager** is **off** are not collected. To collect statistics about such resources, run the following statement:
+  >
+  > ```
+  > select gs_wlm_readjust_user_space(0);
+  > ```
+
+**Default value**: **off**
+
+## cgroup_name
+
+**Parameter description**: Specifies the name of the Cgroup in use or changes the priority of items in the queue of the Cgroup.
+
+If you set **cgroup_name** and then **session_respool**, the Cgroups associated with **session_respool** take effect. If you reverse the order, Cgroups associated with **cgroup_name** take effect.
+
+If the Workload Cgroup level is specified during the **cgroup_name** change, the database does not check the Cgroup level. The level ranges from 1 to 10.
+
+This parameter is a USERSET parameter. Set it based on method 3 provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+You are not advised to set **cgroup_name** and **session_respool** at the same time.
+
+**Value range**: a string
+
+**Default value**: **InvalidGroup**
+
+## cpu_collect_timer
+
+**Parameter description**: Specifies how frequently CPU data is collected during statement execution on database node.
+
+The database administrator changes the value of this parameter based on system resources (for example, CPU, I/O, and memory resources) so that the system fully supports the concurrency tasks and avoids too many concurrency tasks resulting in system crash.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1 to *INT_MAX*. The unit is s.
+
+**Default value**: **30**
+
+## memory_tracking_mode
+
+**Parameter description**: Specifies the memory information recording mode.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+Value range:
+
+- **none**: Memory statistics are not collected.
+- **normal:** Only memory statistics are collected in real time and no file is generated.
+- **executor**: A statistics file is generated, containing the context information of all allocated memory used on the execution layer.
+- **fullexec**: The generated file includes the information about all memory contexts requested by the execution layer.
+
+**Default value**: **none**
+
+## memory_detail_tracking
+
+**Parameter description**: Sets the memory context allocation priority of a thread and the plannodeid of the query for which the current thread is running.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: a string
+
+**Default value**: empty
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** You are advised to retain the default value for this parameter.
+
+## enable_resource_track
+
+**Parameter description**: specifies whether the real-time resource monitoring function is enabled.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates the resource monitoring function is enabled.
+- **off** indicates the resource monitoring function is disabled.
+
+**Default value**: **on**
+
+## enable_resource_record
+
+**Parameter description**: Specifies whether resource monitoring records are archived.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the resource monitoring records are archived.
+- **off** indicates that the resource monitoring records are not archived.
+
+**Default value**: **off**
+
+## enable_logical_io_statistics
+
+**Parameter description**: Specifies whether the resource monitoring logical I/O statistics function is enabled. If this function is enabled, fields in the PG_TOTAL_USER_RESOURCE_INFO view such as **read_kbytes**, **write_kbytes**, **read_counts**, **write_counts**, **read_speed**, and **write_speed** collect statistics on the number of logical read/write bytes, number of read/write times, and the read/write speed.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the resource monitoring logical I/O statistics function is enabled.
+- **off** indicates that the resource monitoring logical I/O statistics function is disabled.
+
+**Default value**: **on**
+
+## enable_user_metric_persistent
+
+**Parameter description**: Specifies whether the user historical resource monitoring dumping function is enabled. If this function is enabled, data in view PG_TOTAL_USER_RESOURCE_INFO is periodically sampled and saved to system catalog **GS_WLM_USER_RESOURCE_HISTORY**.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+**on** indicates that the user historical resource monitoring dumping function is enabled.
+
+**off** indicates that the user historical resource monitoring dumping function is disabled.
+
+**Default value**: **on**
+
+## user_metric_retention_time
+
+**Parameter description**: Specifies the retention time of the user historical resource monitoring data. This parameter is valid only when **enable_user_metric_persistent** is set to **on**.
+
+This parameter is a USERSET parameter. Set it based on methods 1 and 2 provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 730. The unit is day.
+
+If this parameter is set to **0**, user historical resource monitoring data is permanently stored.
+
+If the value is greater than **0**, user historical resource monitoring data is stored for the specified number of days.
+
+**Default value**: **7**
+
+## enable_instance_metric_persistent
+
+**Parameter description**: Specifies whether the instance resource monitoring dumping function is enabled. When this function is enabled, the instance monitoring data is saved to the system catalog **GS_WLM_INSTANCE_HISTORY**.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the instance resource monitoring dumping function is enabled.
+- **off**: Specifies that the instance resource monitoring dumping function is disabled.
+
+**Default value**: **on**
+
+## instance_metric_retention_time
+
+**Parameter description**: Specifies the retention time of the instance historical resource monitoring data. This parameter is valid only when **enable_instance_metric_persistent** is set to **on**.
+
+This parameter is a USERSET parameter. Set it based on methods 1 and 2 provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 3650. The unit is day.
+
+- If this parameter is set to **0**, instance historical resource monitoring data is permanently stored.
+- If the value is greater than **0**, instance historical resource monitoring data is stored for the specified number of days.
+
+**Default value**: **7**
+
+## resource_track_level
+
+**Parameter description**: Specifies the resource monitoring level of the current session. This parameter is valid only when **enable_resource_track** is set to **on**.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Valid value**: enumerated values
+
+- **none**: Resources are not monitored.
+- **query**: Resources used at the query level are monitored.
+- **operator**: Resources used at query and operator levels are monitored.
+
+**Default value**: **query**
+
+## resource_track_cost
+
+**Parameter description**: Specifies the minimum execution cost for resource monitoring on statements in the current session. This parameter is valid only when **enable_resource_track** is set to **on**.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from -1 to *INT_MAX*
+
+- **-1** indicates that resource monitoring is disabled.
+- A value ranging from 0 to 9 indicates that statements whose execution cost is greater than or equal to 10 will be monitored.
+- A value greater than or equal to **10** indicates that statements whose execution cost exceeds this value will be monitored.
+
+**Default value**: **100000**
+
+## resource_track_duration
+
+**Parameter description**: Specifies the minimum statement execution time that determines whether information about jobs of a statement recorded in the real-time view will be dumped to a historical view after the statement is executed. Job information will be dumped from the real-time view (with the suffix **statistics**) to a historical view (with the suffix **history**) if the statement execution time is no less than this value. This parameter is valid only when **[enable_resource_track](#enable_resource_track)** is set to **on**.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to *INT_MAX*. The unit is s.
+
+- **0** indicates that historical information about all statements recorded in the real-time resource monitoring view are archived.
+- If the value is greater than **0**, historical information about a statement whose execution time exceeds this value will be archived.
+
+**Default value**: **1min**
+
+## disable_memory_protect
+
+**Parameter description**: Stops memory protection. To query system views when system memory is insufficient, set this parameter to **on** to stop memory protection. This parameter is used only to diagnose and debug the system when system memory is insufficient. Set it to **off** in other scenarios.
+
+This parameter is a USERSET parameter and is valid only for the current session. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that memory protection stops.
+- **off** indicates that memory is protected.
+
+**Default value**: **off**
+
+## query_band
+
+**Parameter description**: Specifies the job type of the current session.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: a string
+
+**Default value**: empty
+
+## enable_bbox_dump
+
+**Parameter description**: Specifies whether the black box function is enabled. The core files can be generated even through the core dump mechanism is not configured in the system.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the black box function is enabled.
+- **off** indicates that the black box function is disabled.
+
+**Default value**: **off**
+
+## bbox_dump_count
+
+**Parameter description**: Specifies the maximum number of core files that are generated by MogDB and can be stored in the path specified by **[bbox_dump_path](#bbox_dump_path)**. If the number of core files exceeds this value, old core files will be deleted. This parameter is valid only when **[enable_bbox_dump](#enable_bbox_dump)** is set to **on**.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1 to 20
+
+**Default value**: **8**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** When core files are generated during concurrent SQL statement execution, the number of files may be larger than the value of **bbox_dump_count**.
+
+## bbox_dump_path
+
+**Parameter description**: Specifies the path where the black box core files are generated. This parameter is valid only when **[enable_bbox_dump](#enable_bbox_dump)** is set to **on**.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: a string
+
+**Default value**: empty. The default path where the black box core files are generated is **/proc/sys/MogDB/core_pattern**. If the path is not a directory or you do not have the write permission for the directory, the black box core files will be generated in the data directory of the database. Alternatively, use the directory specified during installation.
+
+## enable_ffic_log
+
+**Parameter description**: specifies whether the FFIC (First Failure Info Capture) function is enabled.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the FFIC function is enabled.
+- **off** indicates that the FFIC function is disabled.
+
+**Default value**: **on**
+
+## io_limits
+
+**Parameter description**: Specifies the upper limit of IOPS triggered.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 1073741823
+
+**Default value**: **0**
+
+## io_priority
+
+**Parameter description**: Specifies the I/O priority for jobs that consume many I/O resources. It takes effect when the I/O usage reaches 50%.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Valid value**: enumerated values
+
+- **None** indicates no control.
+- **Low** indicates that the IOPS is reduced to 10% of the original value.
+- **Medium** indicates that the IOPS is reduced to 20% of the original value.
+- **High** indicates that the IOPS is reduced to 50% of the original value.
+
+**Default value**: **None**
+
+## io_control_unit
+
+**Parameter description**: Specifies the unit used to count the number of I/Os during I/O control in row-store scenarios.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+Set a certain number of I/Os as one unit. This unit is used during the I/O control.
+
+**Value range**: an integer ranging from 1000 to 1000000
+
+**Default value**: **6000**
+
+## session_respool
+
+**Parameter description**: Specifies the resource pool associated with the current session.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+If you set **cgroup_name** and then **session_respool**, the Cgroups associated with **session_respool** take effect. If you reverse the order, Cgroups associated with **cgroup_name** take effect.
+
+If the Workload Cgroup level is specified during the **cgroup_name** change, the database does not check the Cgroup level. The level ranges from 1 to 10.
+
+You are advised not to set **cgroup_name** and **session_respool** at the same time.
+
+**Value range**: a string. This parameter can be set to the resource pool configured through **create resource pool**.
+
+**Default value**: **invalid_pool**
+
+## session_statistics_memory
+
+**Parameter description**: Specifies the memory size of a real-time query view.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 5 x 1024 to 50% of **max_process_memory**. The unit is KB.
+
+**Default value**: **5MB**
+
+## topsql_retention_time
+
+**Parameter description**: Specifies the retention period of historical TopSQL data in the **gs_wlm_operator_info** table.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 730. The unit is day.
+
+- If it is set to **0**, the data is stored permanently.
+- If the value is greater than **0**, the data is stored for the specified number of days.
+
+**Default value**: **0**
+
+## session_history_memory
+
+**Parameter description**: Specifies the memory size of a historical query view.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 10 x 1024 to 50% of **max_process_memory**. The unit is KB.
+
+**Default value**: **10MB**
+
+## transaction_pending_time
+
+**Parameter description**: maximum queuing time of transaction block statements and stored procedure statements.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from -1 to *INT_MAX/2*. The unit is s.
+
+- **-1** or **0**: No queuing timeout is specified for transaction block statements and stored procedure statements. The statements can be executed when resources are available.
+- Value greater than **0**: If transaction block statements and stored procedure statements have been queued for a time longer than the specified value, they are forcibly executed regardless of the current resource situation.
+
+**Default value**: **0**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/14-automatic-vacuuming.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/14-automatic-vacuuming.md
new file mode 100644
index 0000000000000000000000000000000000000000..c385a7805c8cb5029819179549902b70c393aaa5
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/14-automatic-vacuuming.md
@@ -0,0 +1,186 @@
+---
+title: Automatic Vacuuming
+summary: Automatic Vacuuming
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Automatic Vacuuming
+
+The autovacuum process automatically runs the **VACUUM** and **ANALYZE** statements to reclaim the record space marked as deleted and update statistics about the table.
+
+## autovacuum
+
+**Parameter description**: Specifies whether to enable the autovacuum process in the database. Ensure that the **track_counts** parameter is set to **on** before enabling the automatic cleanup process.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - Set the **autovacuum** parameter to **on** if you want to enable the automatic cleanup of abnormal two-phase transactions when the system recovers from faults.
+> - If **autovacuum** is set to **on** and **[autovacuum_max_workers](#autovacuum_max_workers)** to **0**, the autovacuum process is enabled only when the system recovers from faults to clean up abnormal two-phase transactions.
+> - If **autovacuum** is set to **on** and **[autovacuum_max_workers](#autovacuum_max_workers)** to a value greater than **0**, the autovacuum process is enabled to clean up bloated tables during daily operations and abnormal two-phase transactions when the system recovers from faults.
+>
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> Even if the **autovacuum** parameter is set to **off**, the autovacuum process will be enabled automatically when a transaction ID wraparound is about to occur. When a CREATE DATABASE or DROP DATABASE operation fails, it is possible that the transaction has been committed or rolled back on some nodes whereas some nodes are still in the prepared status.
+
+**Value range**: Boolean
+
+- **on** indicates that the autovacuum process is enabled.
+- **off** indicates that the autovacuum process is disabled.
+
+**Default value**: **on**
+
+## autovacuum_mode
+
+**Parameter description**: Specifies whether the autoanalyze or autovacuum function is enabled. This parameter is valid only when **autovacuum** is set to **on**.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Valid value**: enumerated values
+
+- **analyze** indicates that only autoanalyze is performed.
+- **vacuum** indicates that only autovacuum is performed.
+- **mix** indicates that both autoanalyze and autovacuum are performed.
+- **none** indicates that neither of them is performed.
+
+**Default value**: **mix**
+
+## autoanalyze_timeout
+
+**Parameter description**: Specifies the timeout period of autoanalyze. If the duration of autoanalyze on a table exceeds the value of **autoanalyze_timeout**, the autoanalyze is automatically canceled.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 2147483. The unit is s.
+
+**Default value**: **5min** (300s)
+
+## autovacuum_io_limits
+
+**Parameter description**: Specifies the upper limit of I/Os triggered by the autovacuum process per second.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: an integer. The value can be **-1** or a number ranging from 0 to 1073741823. **-1** indicates that the default cgroup is used.
+
+**Default value**: **-1**
+
+## log_autovacuum_min_duration
+
+**Parameter description**: Records each step performed by the autovacuum process to the server log when the execution time of the autovacuum process is greater than or equal to a certain value. This parameter helps track the autovacuum behavior.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+A setting example is as follows:
+
+Set the **log_autovacuum_min_duration** parameter to 250 ms to record the actions of autovacuum if it runs for 250 ms or longer.
+
+**Value range**: an integer ranging from -1 to 2147483647. The unit is ms.
+
+- **0** indicates that all autovacuum actions are recorded in the log.
+- **-1** indicates that all autovacuum actions are not recorded in the log.
+- A value other than **-1** indicates that a message is recorded when an autovacuum action is skipped due to a lock conflict.
+
+**Default value**: **-1**
+
+## autovacuum_max_workers
+
+**Parameter description**: Specifies the maximum number of autovacuum worker threads that can run at the same time. The upper limit of this parameter is related to the values of **max_connections** and **job_queue_processes**.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: an integer. The minimum value is **0**, indicating that autovacuum is not enabled. The theoretical maximum value is **262143**, but the actual maximum value is a dynamic value calculated by the following formula: 262143 - **max_connections** - **job_queue_processes** - Number of auxiliary threads - Number of autovacuum launcher threads - 1. The number of auxiliary threads and the number of autovacuum launcher threads are specified by two macros. Their default values are **20** and **2** respectively.
+
+**Default value**: **3**
+
+## autovacuum_naptime
+
+**Parameter description**: Specifies the interval between activity rounds for the autovacuum process.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1 to 2147483. The unit is s.
+
+**Default value**: **10min** (600s)
+
+## autovacuum_vacuum_threshold
+
+**Parameter description**: Specifies the threshold for triggering the **VACUUM** operation. When the number of deleted or updated records in a table exceeds the specified threshold, the **VACUUM** operation is executed on this table.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 2147483647.
+
+**Default value**: **50**
+
+## autovacuum_analyze_threshold
+
+**Parameter description**: Specifies the threshold for triggering the **ANALYZE** operation. When the number of deleted, inserted, or updated records in a table exceeds the specified threshold, the **ANALYZE** operation is executed on this table.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 2147483647
+
+**Default value**: **50**
+
+## autovacuum_vacuum_scale_factor
+
+**Parameter description**: Specifies a fraction of the table size added to the **autovacuum_vacuum_threshold** parameter when deciding whether to vacuum a table.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: a floating point number ranging from 0.0 to 100.0
+
+**Default value**: **0.2**
+
+## autovacuum_analyze_scale_factor
+
+**Parameter description**: Specifies a fraction of the table size added to the **autovacuum_analyze_threshold** parameter when deciding whether to analyze a table.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: a floating point number ranging from 0.0 to 100.0
+
+**Default value**: **0.1**
+
+## autovacuum_freeze_max_age
+
+**Parameter description**: Specifies the maximum age (in transactions) that a table's **pg_class.relfrozenxid** field can attain before a VACUUM operation is performed.
+
+- The old files under the subdirectory of **pg_clog/** can also be deleted by the **VACUUM** operation.
+- Even if the autovacuum process is disabled, the system will invoke the process to prevent transaction ID wraparound.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: an integer from 100000 to 576460752303423487
+
+**Default value**: **20000000000**
+
+## autovacuum_vacuum_cost_delay
+
+**Parameter description**: Specifies the value of the cost delay used in the autovacuum operation.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from -1 to 100. The unit is ms. **-1** indicates that the normal vacuum cost delay is used.
+
+**Default value**: **20ms**
+
+## autovacuum_vacuum_cost_limit
+
+**Parameter description**: Specifies the value of the cost limit used in the autovacuum operation.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from -1 to 10000 **-1** indicates that the normal vacuum cost limit is used.
+
+**Default value**: **-1**
+
+## defer_csn_cleanup_time
+
+**Parameter description**: Specifies the interval of recycling transaction IDs.
+
+**Value range**: an integer ranging from 0 to *INT_MAX*. The unit is ms.
+
+**Default value**: **5s** (5000 ms)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/15-default-settings-of-client-connection/1-statement-behavior.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/15-default-settings-of-client-connection/1-statement-behavior.md
new file mode 100644
index 0000000000000000000000000000000000000000..e0955edb6d687cec401e3f729feec6ef05463573
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/15-default-settings-of-client-connection/1-statement-behavior.md
@@ -0,0 +1,255 @@
+---
+title: Statement Behavior
+summary: Statement Behavior
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Statement Behavior
+
+This section describes related default parameters involved in the execution of SQL statements.
+
+## search_path
+
+**Parameter description**: Sets the order in which schemas are searched when an object is referenced with no schema specified. The value of this parameter consists of one or more schema names. Different schema names are separated by commas (,).
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+- If the schema of a temporary table exists in the current session, the scheme can be listed in **search_path** by using the alias **pg_temp**, for example, **'pg_temp,public'**. The schema of a temporary table has the highest search priority and is always searched before all the schemas specified in **pg_catalog** and **search_path**. Therefore, do not explicitly specify **pg_temp** to be searched after other schemas in **search_path**. This setting will not take effect and an error message will be displayed. If the alias **pg_temp** is used, the temporary schema will be only searched for database objects, including tables, views, and data types. Functions or operator names will not be searched for.
+- The schema of a system catalog, **pg_catalog**, has the second highest search priority and is the first to be searched among all the schemas, excluding **pg_temp**, specified in **search_path**. Therefore, do not explicitly specify **pg_catalog** to be searched after other schemas in **search_path**. This setting will not take effect and an error message will be displayed.
+- When an object is created without specifying a particular schema, the object will be placed in the first valid schema listed in **search_path**. An error will be reported if the search path is empty.
+- The current effective value of the search path can be examined through the SQL function **current_schema**. This is different from examining the value of **search_path**, because the current_schema function displays the first valid schema name in **search_path**.
+
+**Value range**: a string
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - When this parameter is set to **"$user", public**, a database can be shared (where no users have private schemas, and all share use of public), and private per-user schemas and combinations of them are supported. Other effects can be obtained by modifying the default search path setting, either globally or per-user.
+> - When this parameter is set to a null string ("), the system automatically converts it into a pair of double quotation marks ("").
+> - If the content contains double quotation marks, the system considers them as insecure characters and converts each double quotation mark into a pair of double quotation marks.
+
+**Default value**: **"$user",public**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> **$user** indicates the name of the schema with the same name as the current session user. If the schema does not exist, **$user** will be ignored.
+
+## current_schema
+
+**Parameter description**: Sets the current schema.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: a string
+
+**Default value**: **"$user",public**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> **$user** indicates the name of the schema with the same name as the current session user. If the schema does not exist, **$user** will be ignored.
+
+## default_tablespace
+
+**Parameter description:** Specifies the default tablespace of the created objects (tables and indexes) when a **CREATE** command does not explicitly specify a tablespace.
+
+- The value of this parameter is either the name of a tablespace, or an empty string that specifies the use of the default tablespace of the current database. If a non-default tablespace is specified, users must have CREATE privilege for it. Otherwise, creation attempts will fail.
+
+- This parameter is not used for temporary tables. For them, the **[temp_tablespaces](#temp_tablespaces)** is used instead.
+
+- This parameter is not used when users create databases. By default, a new database inherits its tablespace setting from the template database.
+
+  This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: a string. An empty string indicates that the default tablespace is used.
+
+**Default value**: empty
+
+## default_storage_nodegroup
+
+**Parameter description**: Specifies the Node Group where a table is created by default. This parameter takes effect only for ordinary tables.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+- **installation** indicates that tables will be created in the Node Group created during database installation.
+- A value other than **installation** indicates that tables will be created in the Node Group specified by this parameter.
+
+**Value range**: a string
+
+**Default value**: **installation**
+
+## temp_tablespaces
+
+**Parameter description**: Specifies tablespaces to which temporary objects will be created (temporary tables and their indexes) when a CREATE command does not explicitly specify a tablespace. Temporary files for sorting large data are created in these tablespaces.
+
+The value of this parameter is a list of names of tablespaces. When there is more than one name in the list, MogDB chooses a random tablespace from the list upon the creation of a temporary object each time. Except that within a transaction, successively created temporary objects are placed in successive tablespaces in the list. If the element selected from the list is an empty string, MogDB will automatically use the default tablespace of the current database instead.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: a string. An empty string indicates that all temporary objects are created only in the default tablespace of the current database. For details, see **[default_tablespace](#default_tablespace)**.
+
+**Default value**: empty
+
+## check_function_bodies
+
+**Parameter description**: Sets whether to enable validation of the function body string during CREATE FUNCTION. Verification is occasionally disabled to avoid problems, such as forward references when you restore function definitions from a dump.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that validation of the function body string is enabled during the execution of **CREATE FUNCTION**.
+- **off** indicates that validation of the function body string is disabled during the execution of **CREATE FUNCTION**.
+
+**Default value**: **on**
+
+## default_transaction_isolation
+
+**Parameter description**: Controls the default isolation level of each transaction.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: enumerated values
+
+- **read committed** indicates that the transaction has been committed.
+- **repeatable read** indicates that the transaction can be repeatedly read.
+- **serializable**: Currently, this isolation level is not supported in MogDB. It is equivalent to **repeatable read**.
+
+**Default value:** **read committed**
+
+## default_transaction_read_only
+
+**Parameter description**: Specifies whether each new transaction is in read-only state.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates the transaction is in read-only state.
+- **off** indicates the transaction is in read/write state.
+
+**Default value**: **off**
+
+## default_transaction_deferrable
+
+**Parameter description**: controls the default deferrable status of each new transaction. It currently has no effect on read-only transactions or those running at isolation levels lower than serializable.
+
+MogDB does not support the serializable isolation level. Therefore, the parameter takes no effect.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates a transaction is delayed by default.
+- **off** indicates a transaction is not delayed by default.
+
+**Default value**: **off**
+
+## session_replication_role
+
+**Parameter description**: Controls the behavior of replication-related triggers and rules for the current session.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> Setting this parameter will discard all the cached execution plans.
+
+**Value range**: enumerated values
+
+- **origin** indicates that the system copies operations such as insert, delete, and update from the current session.
+- **replica** indicates that the system copies operations such as insert, delete, and update from other places to the current session.
+- **local** indicates that the system will detect the role that has logged in to the database when using the function to copy operations and will perform related operations.
+
+**Default value**: **origin**
+
+## statement_timeout
+
+**Parameter description**: If the statement execution time (starting from when the server receives the command) is longer than the duration specified by the parameter, error information is displayed when you attempt to execute the statement and the statement then exits.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 2147483647. The unit is ms.
+
+**Default value**: **0**
+
+## vacuum_freeze_min_age
+
+**Parameter description**: Specifies the minimum cutoff age (in the same transaction), based on which **VACUUM** decides whether to replace transaction IDs with FrozenXID while scanning a table.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: an integer from 0 to 576460752303423487.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> Although you can set this parameter to a value ranging from 0 to 1000000000 anytime, VACUUM will limit the effective value to half the value of **autovacuum_freeze_max_age** by default.
+
+**Default value**: **5000000000**
+
+## vacuum_freeze_table_age
+
+**Parameter description:** Specifies the time that VACUUM freezes tuples while scanning the whole table. VACUUM performs a whole-table scanning if the value of the **pg_class.relfrozenxid** field of the table has reached the specified time.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: an integer from 0 to 576460752303423487
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> Although users can set this parameter to a value ranging from **0** to **2000000000** anytime, **VACUUM** will limit the effective value to 95% of **autovacuum_freeze_max_age** by default. Therefore, a periodic manual VACUUM has a chance to run before an anti-wraparound autovacuum is launched for the table.
+
+**Default value**: **15000000000**
+
+## bytea_output
+
+**Parameter description:** Sets the output format for values of the bytea type.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: enumerated values
+
+- **hex** indicates the binary is converted to hexadecimal.
+- **escape** indicates the traditional PostgreSQL format is used. It takes the approach of representing a binary string as a sequence of ASCII characters, while converting those bytes that cannot be represented as an ASCII character into special escape sequences.
+
+**Default value**: **hex**
+
+## xmlbinary
+
+**Parameter description:** Sets how binary values are to be encoded in XML.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: enumerated values
+
+- base64
+- hex
+
+**Default value:** base64
+
+## xmloption
+
+**Parameter description:** Specifies whether DOCUMENT or CONTENT is implicit when converting between XML and string values.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: enumerated values
+
+- **document** indicates an HTML document.
+- **content** indicates a common string.
+
+**Default value**: **content**
+
+## max_compile_functions
+
+**Parameter description**: sets the maximum number of function compilation results stored in the server. Excessive functions and compilation results generated during the storage may occupy large memory space. Setting this parameter to a proper value can reduce the memory usage and improve system performance.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: an integer that is greater than or equal to 1
+
+**Default value**: **1000**
+
+## gin_pending_list_limit
+
+**Parameter description**: Specifies the maximum size of the GIN pending list which is used when **fastupdate** is enabled. If the list grows larger than this maximum size, it is cleaned up by moving the entries in it to the main GIN data structure in batches. This setting can be overridden for individual GIN indexes by changing index storage parameters.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Valid value**: an integer. The minimum value is 64 and the maximum value is INT_MAX. The default unit is KB.
+
+**Default value**: **4MB**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/15-default-settings-of-client-connection/2-zone-and-formatting.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/15-default-settings-of-client-connection/2-zone-and-formatting.md
new file mode 100644
index 0000000000000000000000000000000000000000..7540b6560e17aca36ab074213778a782070a65d3
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/15-default-settings-of-client-connection/2-zone-and-formatting.md
@@ -0,0 +1,190 @@
+---
+title: Zone and Formatting
+summary: Zone and Formatting
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Zone and Formatting
+
+This section describes parameters related to the time format setting.
+
+## DateStyle
+
+**Parameter description:** Specifies the display format for date and time values, as well as the rules for interpreting ambiguous date input values.
+
+This variable contains two independent components: the output format specifications (ISO, Postgres, SQL, or German) and the input/output order of year/month/day (DMY, MDY, or YMD). The two components can be set separately or together. The keywords Euro and European are synonyms for DMY; the keywords US, NonEuro, and NonEuropean are synonyms for MDY.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: a string
+
+**Default value**: **ISO, MDY**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> **gs_initdb** will initialize this parameter so that its value is the same as that of **[lc_time](#lc_time)**.
+
+**Suggestion**: The ISO format is recommended. Postgres, SQL, and German use abbreviations for time zones, such as **EST**, **WST**, and **CST**. These abbreviations can be ambiguous. For example, **CST** can represent Central Standard Time (USA) UT-6:00, Central Standard Time (Australia) UT+9:30, China Standard Time UT+8:00, and Cuba Standard Time UT-4:00. This may lead to incorrect time zone conversion and cause errors.
+
+## IntervalStyle
+
+**Parameter description:** sets the display format for interval values.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: enumerated values
+
+- **sql_standard** indicates that output matching SQL standards will be generated.
+- **postgres** indicates that output matching PostgreSQL 8.4 will be generated when the **[DateStyle](#DateStyle)** parameter is set to **ISO**.
+- **postgres_verbose** indicates that output matching PostgreSQL 8.4 will be generated when the **[DateStyle](#DateStyle)** parameter is set to **non_ISO**.
+- **iso_8601** indicates that output matching the time interval "format with designators" defined in ISO 8601 will be generated.
+- **a** indicates the output result that matches the numtodsinterval function. For details, see numtodsinterval.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> The IntervalStyle parameter also affects the interpretation of ambiguous interval input.
+
+**Default value**: **postgres**
+
+## TimeZone
+
+**Parameter description**: Specifies the time zone for displaying and interpreting time stamps.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Default value:** a string. You can obtain it by querying the PG_TIMEZONE_NAMES view.
+
+**Default value**: **PRC**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> **gs_initdb** will set a time zone value that is consistent with the system environment.
+
+## timezone_abbreviations
+
+**Parameter description:** sets the time zone abbreviations that will be accepted by the server.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Default value:** a string. You can obtain it by querying the pg_timezone_names view.
+
+**Default value**: **Default**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> **Default** indicates an abbreviation that works in most of the world, which is applicable to most cases. There are also other abbreviations, such as **Australia** and **India** that can be defined for a particular installation. For other time zone abbreviations, you need to set them in the corresponding configuration files before creating the database.
+
+## extra_float_digits
+
+**Parameter description:** adjusts the number of digits displayed for floating-point values, including float4, float8, and geometric data types. The parameter value is added to the standard number of digits (FLT_DIG or DBL_DIG as appropriate).
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from -15 to 3
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - This parameter can be set to **3** to include partially-significant digits. It is especially useful for dumping float data that needs to be restored exactly.
+> - This parameter can also be set to a negative value to suppress unwanted digits.
+
+**Default value**: **0**
+
+## client_encoding
+
+**Parameter description:** sets the client-side encoding (character set).
+
+Set this parameter as needed. Try to keep the client code and server code consistent to improve efficiency.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: encoding compatible with PostgreSQL. **UTF8** indicates that the database encoding is used.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - You can run the **locale -a** command to check and set the system-supported zone and the corresponding encoding format.
+> - By default, gs_initdb will initialize the setting of this parameter based on the current system environment. You can also run the **locale** command to check the current configuration environment.
+> - To use consistent encoding for communication within the MogDB, you are advised to retain the default value of **client_encoding**. Modification to this parameter in the **postgresql.conf** file (by using the **gs_guc** tool, for example) does not take effect.
+
+**Default value**: **UTF8**
+
+**Recommended value**:**SQL_ASCII** or **UTF8**
+
+## lc_messages
+
+**Parameter description:** sets the language in which messages are displayed.
+
+- Acceptable values are system-related.
+
+- On some systems, this zone category does not exist. Setting this variable will still work, but there will be no effect. In addition, translated messages for the desired language may not exist. In this case, you can still see the English messages.
+
+  This parameter is a SUSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: a string
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - You can run the **locale -a** command to check and set the system-supported zone and the corresponding encoding format.
+> - By default, gs_initdb will initialize the setting of this parameter based on the current system environment. You can also run the **locale** command to check the current configuration environment.
+
+**Default value**: **C**
+
+## lc_monetary
+
+**Parameter description**: Specifies the display format of monetary values. It affects the output of functions such as **to_char**. Acceptable values are system-related.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: a string
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - You can run the **locale -a** command to check and set the system-supported zone and the corresponding encoding format.
+> - By default, gs_initdb will initialize the setting of this parameter based on the current system environment. You can also run the **locale** command to check the current configuration environment.
+
+**Default value**: **C**
+
+## lc_numeric
+
+**Parameter description:** sets the display format of numbers. It affects the output of functions such as to_char. Acceptable values are system-related.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: a string
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - You can run the **locale -a** command to check and set the system-supported zone and the corresponding encoding format.
+> - By default, gs_initdb will initialize the setting of this parameter based on the current system environment. You can also run the **locale** command to check the current configuration environment.
+
+**Default value**: **C**
+
+## lc_time
+
+**Parameter description**: Specifies the display format of time and locale. It affects the output of functions such as **to_char**. Acceptable values are system-related.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: a string
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - You can run the **locale -a** command to check and set the system-supported zone and the corresponding encoding format.
+> - By default, gs_initdb will initialize the setting of this parameter based on the current system environment. You can also run the **locale** command to check the current configuration environment.
+
+**Default value**: **C**
+
+## default_text_search_config
+
+**Parameter description**: Specifies the text search configuration.
+
+If the specified text search configuration does not exist, an error will be reported. If the specified text search configuration is deleted, set **default_text_search_config** again. Otherwise, an error will be reported, indicating incorrect configuration.
+
+- The text search configuration is used by text search functions that do not have an explicit argument specifying the configuration.
+
+- When a configuration file matching the environment is determined, **gs_initdb** will initialize the configuration file with a setting that corresponds to the environment.
+
+  This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: a string
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> MogDB supports the following two configurations: pg_catalog.english and pg_catalog.simple.
+
+**Default value**: **pg_catalog.english**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/15-default-settings-of-client-connection/3-other-default-parameters.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/15-default-settings-of-client-connection/3-other-default-parameters.md
new file mode 100644
index 0000000000000000000000000000000000000000..52baf01304c0fd0419857fef583c19d6281229dc
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/15-default-settings-of-client-connection/3-other-default-parameters.md
@@ -0,0 +1,54 @@
+---
+title: Other Default Parameters
+summary: Other Default Parameters
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Other Default Parameters
+
+This section describes the default database loading parameters.
+
+## dynamic_library_path
+
+**Parameter description**: Specifies the path that the system will search for a shared database file that is dynamically loadable. When a dynamically loadable module needs to be opened and the file name specified in the **CREATE FUNCTION** or **LOAD** command does not have a directory component, the system will search this path for the required file.
+
+The value of **dynamic_library_path** must be a list of absolute paths separated by colons (:). When the name of a path starts with the special variable \$libdir, the variable will be replaced with the directory in which the module provided by the MogDB is installed. For example:
+
+```bash
+dynamic_library_path = '/usr/local/lib/gaussdb:/opt/testgs/lib:$libdir'
+```
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: a string
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> If the value of this parameter is set to an empty character string, the automatic path search is turned off.
+
+**Default value**: **$libdir**
+
+## gin_fuzzy_search_limit
+
+**Parameter description**: Specifies the upper limit of the size of the set returned by GIN indexes.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 2147483647
+
+**Default value**: **0**
+
+## local_preload_libraries
+
+**Parameter description**: Specifies one or more shared libraries that are to be preloaded at connection start. If multiple libraries are to be loaded, separate their names with commas (,). All library names are converted to lower case unless double-quoted.
+
+- Any user can change this option. Therefore, library files that can be loaded are restricted to those saved in the **plugins** subdirectory of the standard library installation directory. It is the database administrator's responsibility to ensure that libraries in this directory are all safe. Entries in **local_preload_libraries** can specify the library directory explicitly, for example, **$libdir/plugins/mylib**, or just specify the library name, for example, **mylib**. (**mylib** is equivalent to **$libdir/plugins/mylib**.)
+- Unlike **shared_preload_libraries**, there are no differences in performance between loading a module at session start or doing this during the session. The intent of this feature is to allow debugging or performance-measurement libraries to be loaded into specific sessions without an explicit LOAD command. For example, debugging can be enabled under a given user name by setting this parameter to **ALTER USER SET**.
+- If a specified library is not found, the connection attempt will fail.
+- Every MogDB-supported library has a "magic block" that is checked to guarantee compatibility. For this reason, non-MogDB-supported libraries cannot be loaded in this way.
+
+This parameter is a BACKEND parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: a string
+
+**Default value**: empty
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/16-lock-management.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/16-lock-management.md
new file mode 100644
index 0000000000000000000000000000000000000000..1222bc50bf44e3ce97b26d37591ace7b101856c8
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/16-lock-management.md
@@ -0,0 +1,152 @@
+---
+title: Lock Management
+summary: Lock Management
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Lock Management
+
+In MogDB, a deadlock may occur when concurrently executed transactions compete for resources. This section describes parameters used for managing transaction locks.
+
+## deadlock_timeout
+
+**Parameter description**: Specifies the time, in milliseconds, to wait on a lock before checking whether there is a deadlock condition. When the applied lock exceeds the preset value, the system will check whether a deadlock occurs.
+
+- The check for deadlock is relatively expensive. Therefore, the server does not check it when waiting for a lock every time. Deadlocks do not frequently occur when the system is running. Therefore, the system just needs to wait on the lock for a while before checking for a deadlock. Increasing this value reduces the time wasted in needless deadlock checks, but slows down reporting of real deadlock errors. On a heavily loaded server, you may need to raise it. The value you have set needs to exceed the transaction time. By doing this, the possibility that a lock will be checked for deadlocks before it is released will be reduced.
+- If you want to write the lock wait time during query execution to logs by setting **log_lock_waits**, ensure that the value of **log_lock_waits** is less than the specified value (or the default value) of **deadlock_timeout**.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1 to 2147483647. The unit is ms.
+
+**Default value**: **1s**
+
+## lockwait_timeout
+
+**Parameter description**: Specifies the timeout for attempts to acquire a lock. If the time spent in waiting for a lock exceeds the specified time, an error is reported.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to *INT_MAX*. The unit is ms.
+
+**Default value**: **20min**
+
+## update_lockwait_timeout
+
+**Parameter description**: Specifies the maximum duration that a lock waits for concurrent updates on a row to complete when the concurrent update feature is enabled. If the time spent in waiting for a lock exceeds the specified time, an error is reported.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to *INT_MAX*. The unit is ms.
+
+**Default value**: **2min**
+
+## max_locks_per_transaction
+
+**Parameter description**: Controls the average number of object locks allocated for each transaction.
+
+- The size of the shared lock table is calculated under the condition that a maximum of *N* independent objects need to be locked at any time. *N* = **max_locks_per_transaction** x (**max_connections** + **max_prepared_transactions**). Objects whose amount does not exceed the preset number can be locked simultaneously at any time. You may need to increase this value if many different tables are modified in a single transaction. This parameter can only be set at database start.
+- Increasing the value of this parameter may cause MogDB to request more System V-shared memory than the OS's default configuration allows.
+- When running a standby server, you must set this parameter to a value that is no less than that on the primary server. Otherwise, queries will not be allowed on the standby server.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range:** an integer ranging from 10 to *INT_MAX*
+
+**Default value**: **256**
+
+## max_pred_locks_per_transaction
+
+**Parameter description**: Controls the average number of predicate locks allocated for each transaction.
+
+- The size of the shared predicate lock table is calculated under the condition that a maximum of *N* independent objects need to be locked at any time. *N* = **max_pred_locks_per_transaction** x (**max_connections** + **max_prepared_transactions**). Objects whose amount does not exceed the preset number can be locked simultaneously at any time. You may need to increase this value if many different tables are modified in a single transaction. This parameter can only be set at server start.
+- Increasing the value of this parameter may cause MogDB to request more System V-shared memory than the OS's default configuration allows.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range:** an integer ranging from 10 to *INT_MAX*
+
+**Default value**: **64**
+
+## gs_clean_timeout
+
+**Parameter description**: Specifies the average interval for clearing temporary tables on the primary node.
+
+- When the database connection is terminated abnormally, temporary tables may exist. In this case, you need to call the **gs_clean** tool to clear the temporary tables in the database.
+- If this parameter is set to a larger value, the time for clearing MogDB temporary tables may be prolonged.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 2147483. The unit is s.
+
+**Default value**: **1min**
+
+## partition_lock_upgrade_timeout
+
+**Parameter description**: Specifies the timeout for attempts to upgrade an exclusive lock (read allowed) to an access exclusive lock (read/write blocked) on a partitioned table during the execution of some query statements. If there are concurrent read transactions running, the lock upgrade will need to wait. This parameter sets the waiting timeout for lock upgrade attempts.
+
+- When you do MERGE PARTITION and CLUSTER PARTITION on a partitioned table, temporary tables are used for data rearrangement and file exchange. To concurrently perform as many operations as possible on the partitions, exclusive locks are acquired for the partitions during data rearrangement and access exclusive locks are acquired during file exchange.
+
+- Generally, a partition waits until it acquires a lock, or a timeout occurs if the partition waits for a period longer than the value specified by the **[lockwait_timeout](#lockwait_timeout)** parameter.
+
+- When doing MERGE PARTITION or CLUSTER PARTITION on a partitioned table, an access exclusive lock needs to be acquired during file exchange. If the lock fails to be acquired, the acquisition is retried at an interval of 50 ms until timeout occurs. The **partition_lock_upgrade_timeout** parameter specifies the time to wait before the lock acquisition attempt times out.
+
+- If this parameter is set to **-1**, the lock upgrade never times out. The lock upgrade is continuously retried until it succeeds.
+
+  This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from -1 to 3000. The unit is s.
+
+**Default value**: **1800**
+
+## fault_mon_timeout
+
+**Parameter description**: Specifies the period for detecting lightweight deadlocks. This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 1440. The unit is minute.
+
+**Default value**: **5min**
+
+## enable_online_ddl_waitlock
+
+**Parameter description**: Specifies whether to block DDL operations to wait for the release of MogDB locks, such as **pg_advisory_lock** and **pgxc_lock_for_backup**. This parameter is mainly used in online OM operations and you are not advised to modify the settings.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that DDL operations will be blocked to wait for the lock release.
+- **off** indicates that DDL operations will not be blocked.
+
+**Default value**: **off**
+
+## xloginsert_locks
+
+**Parameter description**: Specifies the number of locks on concurrent write-ahead logging. This parameter is used to improve the efficiency of writing write-ahead logs.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range:** an integer ranging from 1 to 1000
+
+**Default value**: **8**
+
+## num_internal_lock_partitions
+
+**Parameter description**: Specifies the number of internal lightweight lock partitions. It is mainly used for performance optimization in various scenarios. The content is organized in the KV format of keywords and numbers. Different types of locks are separated by commas (,). The sequence does not affect the setting result. For example, **CLOG_PART=256,CSNLOG_PART=512** is equivalent to **CSNLOG_PART=512,CLOG_PART=256**. If you set the same keyword multiple times, only the latest setting takes effect. For example, if you set **CLOG_PART** to **256**and**CLOG_PART** to **2**, the value of **CLOG_PART** is **2**. If no keyword is set, the default value is used. The usage description, maximum value, minimum value, and default value of each lock type are as follows:
+
+- **CLOG_PART**: number of Clog file controllers. Increasing the value of this parameter improves the Clog writing efficiency and transaction submission performance, but increases the memory usage. Decreasing the value of this parameter reduces the memory usage, but may increase the conflict of writing Clogs and affect the performance. The value ranges from 1 to 256.
+- **CSNLOG_PART**: number of CSNLOG file controllers. Increasing the value of this parameter improves the CSNLOG log writing efficiency and transaction submission performance, but increases the memory usage. Decreasing the value of this parameter reduces the memory usage, but may increase the conflict of writing CSNLOG logs and affect the performance. The value ranges from 1 to 512.
+- **LOG2_LOCKTABLE_PART**: two logarithms of the number of common table lock partitions. Increasing the value can improve the concurrency of obtaining locks in the normal process, but may increase the time required for transferring and clearing locks. When waiting events occur in **LockMgrLock**, you can increase the value to improve the performance. The minimum value is 4, that is, the number of lock partitions is 16. The maximum value is 16, that is, the number of lock partitions is 65536.
+- **TWOPHASE_PART**: number of partitions of the two-phase transaction lock. Increasing the value can increase the number of concurrent two-phase transaction commits. The value ranges from 1 to 64.
+
+This parameter is a **POSTMASTER** parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: a string
+
+**Default value**:
+
+- **CLOG_PART**: **256**
+- **CSNLOG_PART**: **512**
+- **LOG2_LOCKTABLE_PART**: **4**
+- **TWOPHASE_PART**: **1**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/17-version-and-platform-compatibility/1-compatibility-with-earlier-versions.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/17-version-and-platform-compatibility/1-compatibility-with-earlier-versions.md
new file mode 100644
index 0000000000000000000000000000000000000000..ee95b774f6f31d1bd425bd52d9135b6f7e85aa86
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/17-version-and-platform-compatibility/1-compatibility-with-earlier-versions.md
@@ -0,0 +1,133 @@
+---
+title: Compatibility with Earlier Versions
+summary: Compatibility with Earlier Versions
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Compatibility with Earlier Versions
+
+This section describes the parameter control of the downward compatibility and external compatibility features of the MogDB database. A backward compatible database supports applications of earlier versions. This section describes parameters used for controlling backward compatibility of a database.
+
+## array_nulls
+
+**Parameter description**: controls whether the array input parser recognizes unquoted NULL as a null array element.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that null values can be entered in arrays.
+- **off** indicates backward compatibility with the old behavior. Arrays containing **NULL** values can still be created when this parameter is set to **off**.
+
+**Default value**: **on**
+
+## backslash_quote
+
+**Parameter description**: controls whether a single quotation mark can be represented by \' in a string text.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> When the string text meets the SQL standards, \ has no other meanings. This parameter only affects the handling of non-standard-conforming string texts, including escape string syntax (E'…').
+
+**Value range**: enumerated values
+
+- **on** indicates that the use of \' is always allowed.
+- **off** indicates that the use of \' is rejected.
+- **safe_encoding** indicates that the use of \' is allowed only when client encoding does not allow ASCII \ within a multibyte character.
+
+**Default value**: **safe_encoding**
+
+## escape_string_warning
+
+**Parameter description**: specifies a warning on directly using a backslash () as an escape in an ordinary string.
+
+- Applications that wish to use a backslash () as an escape need to be modified to use escape string syntax (E'…'). This is because the default behavior of ordinary strings is now to treat the backslash as an ordinary character in each SQL standard.
+- This variable can be enabled to help locate codes that need to be changed.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+**Default value**: **on**
+
+## lo_compat_privileges
+
+**Parameter description**: Specifies whether to enable backward compatibility for the privilege check of large objects.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+**on** indicates that the privilege check is disabled when users read or modify large objects. This setting is compatible with versions earlier than PostgreSQL 9.0.
+
+**Default value**: **off**
+
+## quote_all_identifiers
+
+**Parameter description:** When the database generates SQL, this parameter forcibly quotes all identifiers even if they are not keywords. This will affect the output of EXPLAIN as well as the results of functions, such as pg_get_viewdef. For details, see the **-quote-all-identifiers** parameter of **gs_dump**.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates the forcible quotation function is enabled.
+- **off** indicates the forcible quotation function is disabled.
+
+**Default value**: **off**
+
+## sql_inheritance
+
+**Parameter description**: Specifies whether to inherit semantics. This parameter specifies the access policy of descendant tables. **off** indicates that subtables cannot be accessed by commands. That is, the ONLY keyword is used by default. This setting is compatible with earlier versions.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the subtable can be accessed.
+- **off** indicates that the subtable cannot be accessed.
+
+**Default value**: **on**
+
+## standard_conforming_strings
+
+**Parameter description**: Specifies whether ordinary string texts ('…') treat backslashes as ordinary texts as specified in the SQL standard.
+
+- Applications can check this parameter to determine how string texts will be processed.
+- It is recommended that characters be escaped by using the escape string syntax (E'…').
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the function is enabled.
+- **off** indicates that the function is disabled.
+
+**Default value**: **on**
+
+## synchronize_seqscans
+
+**Parameter description**: Specifies sequential scans of tables to synchronize with each other. Concurrent scans read the same data block about at the same time and share the I/O workload.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that a scan may start in the middle of the table and then "wrap around" the end to cover all rows to synchronize with the activity of scans already in progress. This may result in unpredictable changes in the row ordering returned by queries that have no ORDER BY clause.
+- **off** indicates that the scan always starts from the table heading.
+
+**Default value**: **on**
+
+## enable_beta_features
+
+**Parameter description**: Specifies whether to enable some features that are not officially released and are used only for POC verification. Exercise caution when enabling these extended features because they may cause errors in some scenarios.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the features are enabled and forward compatible, but may incur errors in certain scenarios.
+- **off** indicates that the features are disabled.
+
+**Default value**: **off**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/17-version-and-platform-compatibility/2-platform-and-client-compatibility.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/17-version-and-platform-compatibility/2-platform-and-client-compatibility.md
new file mode 100644
index 0000000000000000000000000000000000000000..73586f57973cf5d44d996c4d5027218da1182fa0
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/17-version-and-platform-compatibility/2-platform-and-client-compatibility.md
@@ -0,0 +1,171 @@
+---
+title: Platform and Client Compatibility
+summary: Platform and Client Compatibility
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Platform and Client Compatibility
+
+Many platforms use the database system. External compatibility of the database system provides a lot of convenience for platforms.
+
+## convert_string_to_digit
+
+**Parameter description:** Specifies the implicit conversion priority, which determines whether to preferentially convert strings into numbers.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that strings are preferentially converted into numbers.
+- **off** indicates that strings are not preferentially converted into numbers.
+
+**Default value**: **on**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** Adjusting this parameter will change the internal data type conversion rule and cause unexpected behavior. Exercise caution when performing this operation.
+
+## nls_timestamp_format
+
+**Parameter description:** Specifies the default timestamp format.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string
+
+**Default value**: **DD-Mon-YYYY HH:MI:SS.FF AM**
+
+## max_function_args
+
+**Parameter description**: Specifies the maximum number of parameters allowed for a function.
+
+This parameter is a fixed INTERNAL parameter and cannot be modified.
+
+**Value range**: an integer.
+
+**Default value**: **8192**
+
+## transform_null_equals
+
+**Parameter description**: Specifies whether expressions of the form expr = NULL (or NULL = expr) are treated as expr IS NULL. They return true if expr evaluates to **NULL**, and false otherwise.
+
+- The correct SQL-standard-compliant behavior of expr = NULL is to always return null (unknown).
+- Filtered forms in Microsoft Access generate queries that appear to use expr = NULL to test for null values. If you enable this parameter, you can use this interface to access the database.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates expressions of the form expr = NULL (or NULL = expr) are treated as expr IS NULL.
+- **off** indicates expr = NULL always returns NULL.
+
+**Default value**: **off**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> New users are always confused about the semantics of expressions involving **NULL** values. Therefore, **off** is used as the default value.
+
+## support_extended_features
+
+**Parameter description**: Specifies whether extended database features are supported.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that extended database features are supported.
+- **off** indicates that extended database features are not supported.
+
+**Default value**: **off**
+
+## sql_compatibility
+
+**Parameter description**: Specifies the type of mainstream database with which the SQL syntax and statement behavior of the database is compatible. This parameter is an INTERNAL parameter. It can be viewed but cannot be modified.
+
+**Value range**: enumerated values
+
+- **A** indicates that the database is compatible with the O database.
+- **B** indicates that the database is compatible with the MY database.
+- **C** indicates that the database is compatible with the TD database.
+- **PG** indicates that the database is compatible with the PostgreSQL database.
+
+**Default value**: **A**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - This parameter can be set only when you run the CREATE DATABASE command to create a database.
+> - In the database, this parameter must be set to a specific value. It can be set to **A** or **B** and cannot be changed randomly. Otherwise, the setting is not consistent with the database behavior.
+
+## behavior_compat_options
+
+**Parameter description**: Specifies database compatibility behavior. Multiple items are separated by commas (,).
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string
+
+**Default value:** empty
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - Currently, only compatibility configuration items in Table 1 [GUC parameters](30-appendix) are supported.
+> - Multiple items are separated by commas (,), for example, **set behavior_compat_options='end_month_calculate,display_leading_zero';**.
+
+**Table 1** Compatibility configuration items
+
+| Configuration Item        | Behavior                                                     |
+| :------------------------ | :----------------------------------------------------------- |
+| display_leading_zero      | Specifies how floating point numbers are displayed.<br />- If this item is not specified, for a decimal number between -1 and 1, the 0 before the decimal point is not displayed. For example, 0.25 is displayed as **.25**.<br />- If this item is specified, for a decimal number between -1 and 1, the 0 before the decimal point is displayed. For example, 0.25 is displayed as **0.25**. |
+| end_month_calculate       | Specifies the calculation logic of the add_months function.<br />Assume that the two parameters of the add_months function are **param1** and **param2**, and that the month of **param1** and **param2** is **result**.<br />- If this item is not specified, and the **Day** of **param1** indicates the last day of a month shorter than **result**, the **Day** in the calculation result will equal that in **param1**. For example:<br />`mogdb=# select add_months('2018-02-28',3) from sys_dummy; add_months ---------------------- 2018-05-28 00:00:00 (1 row)`<br />- If this item is specified, and the **Day** of **param1** indicates the last day of a month shorter than **result**, the **Day** in the calculation result will equal that in **result**. For example:<br />`mogdb=# select add_months('2018-02-28',3) from sys_dummy; add_months ---------------------- 2018-05-31 00:00:00 (1 row)` |
+| compat_analyze_sample     | Specifies the sampling behavior of the ANALYZE operation.<br />If this item is specified, the sample collected by the ANALYZE operation will be limited to around 30,000 records, DBnode memory consumption and maintaining the stability of ANALYZE. |
+| bind_schema_tablespace    | Binds a schema with the tablespace with the same name.<br />If a tablespace name is the same as *sche_name*, **default_tablespace** will also be set to *sche_name* if **search_path** is set to *sche_name*. |
+| bind_procedure_searchpath | Specifies the search path of the database object for which no schema name is specified.<br />If no schema name is specified for a stored procedure, the search is performed in the schema to which the stored procedure belongs.<br />If the stored procedure is not found, the following operations are performed:<br />- If this item is not specified, the system reports an error and exits.<br />- If this item is specified, the search continues based on the settings of **search_path**. If the issue persists, the system reports an error and exits. |
+| correct_to_number         | Controls the compatibility of the to_number() result.<br />If this item is specified, the result of the to_number() function is the same as that of PG11. Otherwise, the result is the same as that of the O database. |
+| unbind_dive_bound         | Controls the range check on the result of integer division.<br />If this item is specified, you do not need to check the range of the division result. For example, the result of INT_MIN/(-1) can be *INT_MAX*+1. If this item is not specified, an out-of-bounds error is reported because the result is greater than*INT_MAX*. |
+| merge_update_multi        | Performs an update if multiple rows are matched for **MERGE INTO**.<br />If this item is specified, no error is reported if multiple rows are matched. Otherwise, an error is reported (same as the O database). |
+| return_null_string        | Specifies how to display the empty result (empty string ") of the lpad() and rpad() functions.<br />- If this item is not specified, the empty string is displayed as **NULL**.<br />`mogdb=# select length(lpad('123',0,'*')) from sys_dummy; length ---- (1 row)`<br />- If this item is specified, the empty string is displayed as single quotation marks (").<br />`mogdb=# select length(lpad('123',0,'*')) from sys_dummy; length ---- 0 (1 row)` |
+| compat_concat_variadic    | Specifies the compatibility of variadic results of the concat() and concat_ws() functions.<br />If this item is specified and a concat function has a parameter of the variadic type, different result formats in O and Teradata are retained. If this item is not specified and a concat function has a parameter of the variadic type, the result format of O is retained for both O and Teradata. This option has no effect on MY because MY has no variadic type. |
+| merge_update_multi        | When MERGE INTO… WHEN MATCHED THEN UPDATE (see **MERGE INTO**) and INSERT… ON DUPLICATE KEY UPDATE (see **INSERT**) are used, control the UPDATE behavior if a piece of target data in the target table conflicts with multiple pieces of source data.<br />If this item is specified and the preceding scenario exists, the system performs multiple UPDATE operations on the conflicting row. If this item is not specified and the preceding scenario exists, an error is reported, that is, the MERGE or INSERT operation fails. |
+| hide_tailing_zero         | Numeric shows the configuration item. If this parameter is not set, numeric shows the configuration item based on the specified precision. When this parameter is set, hide "0" at the end of the decimal point. <br />`set behavior_compat_options='hide_tailing_zero'; select cast(123.123 as numeric(15,10)); numeric ---- 123.123 (1 row)` |
+
+## plpgsql.variable_conflict
+
+**Parameter description**: Specifies the priority of a stored procedure variable and a table column that have the same name.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: String
+
+- **error** indicates that an error is reported during compilation if the name of a stored procedure variable and that of a table column are the same.
+- **use_variable** indicates that the variable is preferentially used if the name of a stored procedure variable and that of a table column are the same.
+- **use_column** indicates that the column is preferentially used if the name of a stored procedure variable and that of a table column are the same.
+
+**Default value**: **error**
+
+## td_compatible_truncation
+
+**Parameter description**: Specifies whether to enable features compatible with a Teradata database. You can set this parameter to **on** when connecting to a database compatible with the TD database, so that when you perform the INSERT operation, overlong strings are truncated based on the allowed maximum length before being inserted into char- and varchar-type columns in the target table. This ensures all data is inserted into the target table without errors reported.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> The string truncation function cannot be used if the INSERT statement includes a foreign table.
+> If inserting multi-byte character data (such as Chinese characters) to database with the character set byte encoding (SQL_ASCII, LATIN1), and the character data crosses the truncation position, the string is truncated based on its bytes instead of characters. Unexpected result will occur in tail after the truncation. If you want correct truncation result, you are advised to adopt encoding set such as UTF8, which has no character data crossing the truncation position.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates overlong strings are truncated.
+- **off** indicates overlong strings are not truncated.
+
+**Default value**: **off**
+
+## lastval_supported
+
+**Parameter description**: Specifies whether to enable the **lastval** function.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**:  Boolean
+
+- **on** indicates that the **lastval** function is supported. Additionally, the **nextval** function does not support push-down.
+- **off** indicates that the **lastval** function is not supported. Additionally, the **nextval** function supports push-down.
+
+**Default value**: **off**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/18-fault-tolerance.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/18-fault-tolerance.md
new file mode 100644
index 0000000000000000000000000000000000000000..ca415567a463371dfd5938ee1d9dff621c2898e7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/18-fault-tolerance.md
@@ -0,0 +1,109 @@
+---
+title: Fault Tolerance
+summary: Fault Tolerance
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Fault Tolerance
+
+This section describes parameters used for controlling the methods that the server processes an error occurring in the database system.
+
+## exit_on_error
+
+**Parameter description**: Specifies whether to terminate the current session.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that any error will terminate the current session.
+- **off** indicates that only a FATAL error will terminate the current session.
+
+**Default value**: **off**
+
+## restart_after_crash
+
+**Parameter description**: Specifies whether MogDB automatically reinitializes the backend process when a backend process crashes.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that MogDB automatically reinitializes the backend process when a backend process crashes.
+
+  In some circumstances (for example, when a management tool, such as xCAT, is used to manage MogDB), setting this parameter to **on** maximizes the availability of the database.
+
+- **off** indicates a management tool is enabled to obtain control permission and take proper measures when a backend process crashes.
+
+**Default value**: **on**
+
+## omit_encoding_error
+
+**Parameter description**: If this parameter is set to **on** and the client character set of the database is encoded in UTF-8 format, the occurring character encoding conversion errors will be recorded in logs. Additionally, converted characters that have conversion errors will be ignored and replaced with question marks (?).
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that characters that have conversion errors will be ignored and replaced with question marks (?), and error information will be recorded in logs.
+- **off** indicates that characters that have conversion errors cannot be converted and error information will be directly displayed.
+
+**Default value**: **off**
+
+## max_query_retry_times
+
+**Parameter description**: Specifies the maximum number of times that an **SQL** statement with errors can be re-executed. **SQL** statements with the following types of errors can be re-executed:**Connection reset by peer**, **Lock wait timeout**, and **Connection timed out**. If this parameter is set to **0**, the re-execution function is disabled.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 20
+
+**Default value**: **0**
+
+## cn_send_buffer_size
+
+**Parameter description**: Specifies the size of the data buffer used for data transmission on the primary database node.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 8 to 128. The unit is KB.
+
+**Default value**: **8KB**
+
+## retry_ecode_list
+
+**Parameter description**: Specifies the list of SQL error types that support automatic retry.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: a string
+
+**Default value**: **YY001 YY002 YY003 YY004 YY005 YY006 YY007 YY008 YY009 YY010 YY011 YY012 YY013 YY014 YY015 53200 08006 08000 57P01 XX003 XX009 YY016**
+
+## data_sync_retry
+
+**Parameter description**: Specifies whether to keep running the database when updated data fails to be written into disks by using the **fsync** function. In some OSs, no error is reported even if **fsync** has failed for multiple times. As a result, data is lost.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on**: The database keeps running and **fsync** is executed again after **fsync** fails.
+- **off**: **PANIC** is reported and the database is stopped after **fsync** fails.
+
+**Default value**: **off**
+
+## remote_read_mode
+
+**Parameter description**: Specifies whether to enable the remote read function. This function allows pages on the standby server to be read when reading pages on the primary server fails.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: enumerated values
+
+- **off** indicates that the remote read function is disabled.
+- **non_authentication** indicates that the remote read function is enabled but certificate authentication is not required.
+- **authentication** indicates that the remote read function is enabled and certificate authentication is required.
+
+**Default value**: **authentication**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/19-connection-pool-parameters.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/19-connection-pool-parameters.md
new file mode 100644
index 0000000000000000000000000000000000000000..e30a08a5b807a6633b22e2994e9c08057315dcba
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/19-connection-pool-parameters.md
@@ -0,0 +1,23 @@
+---
+title: Connection Pool Parameters
+summary: Connection Pool Parameters
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Connection Pool Parameters
+
+When a connection pool is used to access the database, database connections are established and then stored in the memory as objects during system running. When you need to access the database, no new connection is established. Instead, an existing idle connection is selected from the connection pool. After you finish accessing the database, the database does not disable the connection but puts it back into the connection pool. The connection can be used for the next access request.
+
+## cache_connection
+
+**Parameter description**: Specifies whether to reclaim the connections of a connection pool.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the connections of a connection pool will be reclaimed.
+- **off** indicates that the connections of a connection pool will not be reclaimed.
+
+**Default value**: **on**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/2-file-location.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/2-file-location.md
new file mode 100644
index 0000000000000000000000000000000000000000..e1a441b54d695065c441bc176f1f7d672915fef9
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/2-file-location.md
@@ -0,0 +1,69 @@
+---
+title: File Location
+summary: File Location
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# File Location
+
+After a database has been installed, three configuration files (**postgresql.conf**, **pg_hba.conf**, and **pg_ident.conf**) are automatically generated and saved in the data directory. You can use the methods described in this section to change the names and save paths of these configuration files.
+
+When changing the storage directory of a configuration file, set **data_directory** in **postgresql.conf** to the actual data directory.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> If a configuration file is incorrectly modified, the database will be seriously affected. Do not modify the configuration files mentioned in this section after installation.
+
+## data_directory
+
+**Parameter description**: Specifies the data directory of MogDB. You can set this parameter using one of the following methods:
+
+- Set it when you install MogDB.
+- This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string, consisting of one or more characters.
+
+**Default value**: Specify this parameter during installation. If this parameter is not specified during installation, the database is not initialized by default.
+
+## config_file
+
+**Parameter description**: Specifies the configuration file (**postgresql.conf**) of the primary server.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix). This parameter cannot be modified based on Method 4 in Table 2 [Methods for setting GUC parameters](30-appendix).
+
+**Value range**: a string, consisting of one or more characters.
+
+**Default value**: **postgresql.conf** (The absolute directory of this file may be displayed in the actual situation.)
+
+## hba_file
+
+**Parameter description**: Specifies the configuration file (**pg_hba.conf**) for host-based authentication (HBA). You can set this parameter only in the configuration file **postgresql.conf**.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string
+
+**Default value**: **pg_hba.conf** (The absolute directory of this file may be displayed in the actual situation.)
+
+## ident_file
+
+**Parameter description**: Specifies the configuration file (**pg_ident.conf)** for client authentication.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string
+
+**Default value**: **pg_ident.conf** (The absolute directory of this file may be displayed in the actual situation.)
+
+## external_pid_file
+
+**Parameter description**: Specifies the extra PID file that can be used by the server management program.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> This parameter takes effect only after the database restarts.
+
+**Value range**: a string
+
+**Default value**: empty
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/20-MogDB-transaction.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/20-MogDB-transaction.md
new file mode 100644
index 0000000000000000000000000000000000000000..ab720416b759cb7a7e8f1a49ff92b056c7c107e1
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/20-MogDB-transaction.md
@@ -0,0 +1,121 @@
+---
+title: MogDB Transaction
+summary: MogDB Transaction
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# MogDB Transaction
+
+This section describes the settings and value ranges of MogDB transaction parameters.
+
+## transaction_isolation
+
+**Parameter description**: Specifies the isolation level of the current transaction.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string of case-sensitive characters. The values include:
+
+- **serializable**: This value is equivalent to REPEATABLE READ in MogDB.
+- **read committed**: Only the data in committed transactions will be read.
+- **repeatable read**: Only the data committed before transaction start is read. Uncommitted data or data committed in other concurrent transactions cannot be read.
+- **default**: The value is the same as that of **default_transaction_isolation**.
+
+**Default value:** **read committed**
+
+## transaction_read_only
+
+**Parameter description:** Specifies that the current transaction is a read-only transaction.
+
+This parameter is fixed to on during the database recovery process or in the standby machine; otherwise, it is fixed to the value of default_transaction_read_only.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the current transaction is a read-only transaction.
+- **off** indicates that the current transaction can be a read/write transaction.
+
+**Default value**: **off**
+
+## xc_maintenance_mode
+
+**Parameter description:** Specifies whether the system is in maintenance mode.
+
+This parameter is a SUSET parameter. Set it based on method 3 in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that concurrent update is allowed.
+- **off** indicates that concurrent update is disallowed.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> Enable the maintenance mode with caution to avoid MogDB data inconsistencies.
+
+**Default value**: **off**
+
+## allow_concurrent_tuple_update
+
+**Parameter description**: Specifies whether to allow concurrent update.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that concurrent update is allowed.
+- **off** indicates that concurrent update is disallowed.
+
+**Default value**: **on**
+
+## transaction_deferrable
+
+**Parameter description:** specifies whether to delay the execution of a read-only serial transaction without incurring an execution failure. Assume this parameter is set to **on**. When the server detects that the tuples read by a read-only transaction are being modified by other transactions, it delays the execution of the read-only transaction until the other transactions finish modifying the tuples. Currently, this parameter is not used in MogDB. Similar to this parameter, the **default_transaction_deferrable** parameter is used to specify whether to allow delayed execution of a transaction.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the execution of a transaction can be delayed.
+- **off** indicates that the execution of a transaction cannot be delayed.
+
+**Default value**: **off**
+
+## enable_show_any_tuples
+
+**Parameter description:** This parameter is available only in a read-only transaction and is used for analysis. When this parameter is set to **on**/**true**, all versions of tuples in the table are displayed.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on/true** indicates that all versions of tuples in the table are displayed.
+- **off/false** indicates that no versions of tuples in the table are displayed.
+
+**Default value**: **off**
+
+## replication_type
+
+**Parameter description**: Specifies what nodes are deployed for the HA mode. The nodes can consist of a primary, a standby, and a secondary node; or consist of a primary and multiple standby nodes; or consist of a primary node.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+You are advised not to modify this parameter.
+
+**Value range**: 0 to 2
+
+- **0** indicates that the HA nodes consist of a primary, a standby, and a secondary node, This mode is not currently supported.
+- **1** indicates that the HA nodes consist of a primary and multiple standby nodes. Full scene coverage, this value is recommended.
+- **2** indicates that single host mode. This mode cannot expand the standby nodes.
+
+**Default value**: **1**
+
+## pgxc_node_name
+
+**Parameter description**: Specifies the name of a node.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string
+
+**Default value**: current node name
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/21-developer-options.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/21-developer-options.md
new file mode 100644
index 0000000000000000000000000000000000000000..f99ebb3128f2e6f72054862aa296d1320339c030
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/21-developer-options.md
@@ -0,0 +1,295 @@
+---
+title: Developer Options
+summary: Developer Options
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Developer Options
+
+## allow_system_table_mods
+
+**Parameter description**: Specifies whether the structures of system tables can be modified.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+It is not recommended to modify the default value of this parameter. If it is set to on, the system tables may be damaged and the database may not start.
+
+**Value range**: Boolean
+
+- **on** indicates that the structures of system tables can be modified.
+- **off** indicates that the structures of system tables cannot be modified.
+
+**Default value**: **off**
+
+## debug_assertions
+
+**Parameter description:** Specifies whether to enable various assertion checks. This parameter assists in debugging. If you are experiencing strange problems or crashes, set this parameter to **on** to identify programming defects. To use this parameter, the macro USE_ASSERT_CHECKING must be defined (through the configure option **-enable-cassert**) during the MogDB compilation.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that various assertion checks are enabled.
+- **off** indicates that various assertion checks are disabled.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** This parameter is set to **on** by default if MogDB is compiled with various assertion checks enabled.
+
+**Default value**: **off**
+
+## ignore_checksum_failure
+
+**Parameter description**: Specifies whether to ignore check failures (but still generates an alarm) and continues reading data. Continuing reading data may result in breakdown, damaged data being transferred or hidden, failure of data recovery from remote nodes, or other serious problems. You are not advised to modify the settings.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that data check errors are ignored.
+- **off** indicates that data check errors are reported.
+
+**Default value**: **off**
+
+## ignore_system_indexes
+
+**Parameter description**: Specifies whether to ignore system indexes when reading system tables (but still update the indexes when modifying the tables).
+
+This parameter is a BACKEND parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** This parameter is useful for recovering data from tables whose system indexes are damaged.
+
+**Value range**: Boolean
+
+- **on** indicates that system indexes are ignored.
+- **off** indicates that system indexes are not ignored.
+
+**Default value**: **off**
+
+## post_auth_delay
+
+**Parameter description**: Specifies the delay in the connection to the server after a successful authentication. Developers can attach a debugger to the server startup process.
+
+This parameter is a BACKEND parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range:** an integer ranging from 0 to 2147. The unit is s.
+
+**Default value**: **0**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** This parameter is used only for commissioning and fault locating. To prevent impact on service running, ensure that the default value **0** is used in the production environment. If this parameter is set to a value other than 0, the cluster status may be abnormal due to a long authentication delay.
+
+## pre_auth_delay
+
+**Parameter description**: Specifies the period of delaying authentication after the connection to the server is started. Developers can attach a debugger to the authentication procedure.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 60. The unit is s.
+
+**Default value**: **0**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** This parameter is used only for commissioning and fault locating. To prevent impact on service running, ensure that the default value 0 is used in the production environment. If this parameter is set to a value other than 0, the cluster status may be abnormal due to a long authentication delay.
+
+## trace_notify
+
+**Parameter description**: Specifies whether to enable the function of generating debugging output for the **LISTEN** and **NOTIFY** commands. The level of client_min_messages or log_min_messages must be **debug1** or lower so that debugging output can be recorded in the client or server logs, respectively.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the function is enabled.
+- **off** indicates that the function is disabled.
+
+**Default value**: **off**
+
+## trace_recovery_messages
+
+**Parameter description**: Specifies whether to enable logging of recovery-related debugging output. This parameter allows users to overwrite the normal setting of log_min_messages, but only for specific messages. This is intended for the use in debugging the standby server.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: enumerated values. Valid values include **debug5**, **debug4**, **debug3**, **debug2**, **debug1**, and **log**. For details about the parameter values, see log_min_messages.
+
+**Default value**: **log**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - **log** indicates that recovery-related debugging information will not be logged.
+> - Except the default value **log**, each of the other values indicates that recovery-related debugging information at the specified level will also be logged. Common settings of **log_min_messages** enables logs to be unconditionally recorded into server logs.
+
+## trace_sort
+
+**Parameter description**: Specifies whether to print information about resource usage during sorting operations. This parameter is available only when the macro TRACE_SORT is defined during the MogDB compilation. However, TRACE_SORT is currently defined by default.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the function is enabled.
+- **off** indicates that the function is disabled.
+
+**Default value**: **off**
+
+## zero_damaged_pages
+
+**Parameter description**: Specifies whether to detect a damaged page header that causes MogDB to report an error, aborting the current transaction.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+Setting this parameter to **on** causes the system to report a warning, zero out the damaged page, and continue processing. This behavior will destroy data, including all the rows on the damaged page. However, it allows you to bypass the error and retrieve rows from any undamaged pages that may be present in the table. Therefore, it is useful for restoring data if corruption has occurred due to a hardware or software error. In most cases, you are advised not to set this parameter to **on** if you want to restore data from damaged pages.
+
+**Default value**: **off**
+
+## remotetype
+
+**Parameter description**: Specifies the remote connection type.
+
+This parameter cannot be changed.
+
+**Value range**: enumerated values. Valid values are **application**, **datanode**, and **internaltool**.
+
+**Default value**: **application**
+
+## max_user_defined_exception
+
+**Parameter description**: Specifies the maximum number of exceptions. The default value cannot be changed.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+Value range: an integer. Currently, only the fixed value **1000** is supported.
+
+**Default value**: **1000**
+
+## enable_fast_numeric
+
+**Parameter description**: Specifies whether to enable optimization for numeric data calculation. Calculation of numeric data is time-consuming. Numeric data is converted into int64- or int128-type data to improve numeric data calculation performance.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** or **true** indicates that optimization for numeric data calculation is enabled.
+- **off** or **false** indicates that optimization for numeric data calculation is disabled.
+
+**Default value**: **on**
+
+## enable_compress_spill
+
+**Parameter description**: Specifies whether to enable the compression function of writing data to disk.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** or **true** indicates that optimization for writing data to disk is enabled.
+- **off** or **false** indicates that optimization for writing data to a disk is disabled.
+
+**Default value**: **on**
+
+## resource_track_log
+
+**Parameter description**: Specifies the log level of self-diagnosis. Currently, this parameter takes effect only in multi-column statistics.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string
+
+- **summary**: Brief diagnosis information is displayed.
+- **detail**: Detailed diagnosis information is displayed.
+
+Currently, the two parameter values differ only when there is an alarm about multi-column statistics not collected. If the parameter is set to **summary**, such an alarm will not be displayed. If it is set to **detail**, such an alarm will be displayed.
+
+**Default value**: **summary**
+
+## show_acce_estimate_detail
+
+**Parameter description**: The evaluation information is generally used by O&M personnel during maintenance, and it may affect the output display of the **EXPLAIN** statement. Therefore, this parameter is disabled by default. The evaluation information is displayed only if the **verbose** option of the **EXPLAIN** statement is enabled.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the evaluation information is displayed in the output of the **EXPLAIN** statement.
+- **off** indicates that the evaluation information is not displayed in the output of the **EXPLAIN** statement.
+
+**Default value**: **off**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The current version does not support database acceleration. Therefore, this parameter does not take effect after being set.
+
+## support_batch_bind
+
+**Parameter description**: Specifies whether to batch bind and execute PBE statements through interfaces such as JDBC, ODBC, and libpq.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that batch binding and execution are used.
+- **off** indicates that batch binding and execution are not used.
+
+**Default value**: **on**
+
+## numa_distribute_mode
+
+**Parameter description**: Specifies the distribution of some shared data and threads among NUMA nodes. This parameter is used to optimize the performance of large-scale ARM servers with multiple NUMA nodes. Generally, you do not need to set this parameter.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string. The valid values are **none** and **all**.
+
+- **none** indicates that this function is disabled.
+- **all** indicates that some shared data and threads are distributed to different NUMA nodes to reduce the number of remote access times and improve performance. Currently, this function applies only to ARM servers with multiple NUMA nodes. All NUMA nodes must be available for database processes. You cannot select only some NUMA nodes.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** In the current version, **numa_distribute_mode** cannot be set to **all** on the x86 platform.
+
+**Default value**: **none**
+
+## log_pagewriter
+
+**Parameter description**: Specifies whether to display the page refresh information of a thread and details about an incremental check point after the incremental check point is enabled. You are not advised to set this parameter to **true** because a large amount of information will be generated.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+**Default value**: **on**
+
+## advance_xlog_file_num
+
+**Parameter description**: Specifies the number of Xlog files that are periodically initialized in advance in the background. This parameter is used to prevent the Xlog file initialization from affecting the performance during transaction submission. However, such a fault may occur only when the system is overloaded. Therefore, you do not need to set this parameter.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 1000000. The value **0** indicates that initialization is not performed in advance. For example, the value **10** indicates that the background thread periodically initializes 10 Xlog files in advance based on the write location of the current xlog.
+
+**Default value**: **0**
+
+## enable_beta_opfusion
+
+**Parameter description**: Specifies whether to accelerate the execution of SQL statements, such as aggregate functions and sorting in TPC-C when **enable_opfusion** is set to **on**.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the functions are enabled.
+- **off** indicates that the function are disabled.
+
+**Default value**: **off**
+
+## string_hash_compatible
+
+**Parameter description**: Specifies whether to use the same method to calculate char-type hash values and varchar- or text-type hash values. Based on the setting of this parameter, you can determine whether a redistribution is required when a distribution column is converted from a char-type data distribution into a varchar- or text-type data distribution.
+
+This parameter is a **POSTMASTER** parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the same calculation method is used and a redistribution is not required.
+- **off** indicates that different calculation methods are used and a redistribution is required.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** Calculation methods differ in the length of input strings used for calculating hash values. (For a char-type hash value, spaces following a string are not counted as the length. For a text- or varchar-type hash value, the spaces are counted.) The hash value affects the calculation result of queries. To avoid query errors, do not modify this parameter during database running once it is set.
+
+**Default value**: **off**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/22-auditing/1-audit-switch.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/22-auditing/1-audit-switch.md
new file mode 100644
index 0000000000000000000000000000000000000000..ca4846efc8da59c69eea8f0232d7ec2041ce0a77
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/22-auditing/1-audit-switch.md
@@ -0,0 +1,113 @@
+---
+title: Audit Switch
+summary: Audit Switch
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Audit Switch
+
+## audit_enabled
+
+**Parameter description**: Specifies whether to enable or disable the audit process. After the audit process is enabled, the auditing information written by the background process can be read from the pipe and written into audit files.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the auditing function is enabled.
+- **off** indicates that the auditing function is disabled.
+
+**Default value**: **on**
+
+## audit_directory
+
+**Parameter description**: Specifies the storage directory of audit files. It is a customizable path related to the data directory.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string
+
+**Default value:** **pg_audit** If **om** is used for MogDB deployment, audit logs are stored in **$GAUSSLOG/pg_audit/\*Instance name\***.
+
+## audit_data_format
+
+**Parameter description**: Audits the format of log files. Currently, only the binary format is supported.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string
+
+**Default value**: **binary**
+
+## audit_rotation_interval
+
+**Parameter description**: Specifies the interval of creating an audit log file. If the difference between the current time and the time when the previous audit log file is created is greater than the value of **audit_rotation_interval**, a new audit log file will be generated.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1 to *INT_MAX*/60. The unit is min.
+
+**Default value:** **1d**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> Adjust this parameter only when required. Otherwise, **audit_resource_policy** may fail to take effect. To control the storage space and time of audit logs, set the **[audit_resource_policy](#audit_resource_policy)**, **[audit_space_limit](#audit_space_limit)**, and **[audit_file_remain_time](#audit_file_remain_time)** parameters.
+
+## audit_rotation_size
+
+**Parameter description**: Specifies the maximum capacity of an audit log file. If the total number of messages in an audit log exceeds the value of **audit_rotation_size**, the server will generate a new audit log file.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1024 to 1048576. The unit is KB.
+
+**Default value**: **10 MB**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> Adjust this parameter only when required. Otherwise, **audit_resource_policy** may fail to take effect. To control the storage space and time of audit logs, set the **audit_resource_policy**, **audit_space_limit**, and **audit_file_remain_time** parameters.
+
+## audit_resource_policy
+
+**Parameter description**: Specifies the policy for determining whether audit logs are preferentially stored by space or time.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that audit logs are preferentially stored by space. A maximum of **[audit_space_limit](#audit_space_limit)** logs can be stored.
+- **off** indicates that audit logs are preferentially stored by time. A minimum duration of **[audit_file_remain_time](#audit_file_remain_time)** logs must be stored.
+
+**Default value**: **on**
+
+## audit_file_remain_time
+
+**Parameter description**: Specifies the minimum duration required for recording audit logs. This parameter is valid only when **[audit_resource_policy](#audit_resource_policy)** is set to **off**.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 730. The unit is day. **0** indicates that the storage duration is not limited.
+
+**Default value**: **90**
+
+## audit_space_limit
+
+**Parameter description**: Specifies the total disk space occupied by audit files.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1024 KB to 1024 GB. The unit is KB.
+
+**Default value**: **1GB**
+
+## audit_file_remain_threshold
+
+**Parameter description**: Specifies the maximum number of audit files in the audit directory.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1 to 1048576
+
+**Default value**: **1048576**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> Ensure that this parameter is set to **1048576**. Adjust this parameter only when required. Otherwise, **audit_resource_policy** may fail to take effect. To control the storage space and time of audit logs, set the **audit_resource_policy**, **audit_space_limit**, and **audit_file_remain_time** parameters.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/22-auditing/2-user-and-permission-audit.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/22-auditing/2-user-and-permission-audit.md
new file mode 100644
index 0000000000000000000000000000000000000000..d10e48c7cd6ca03222a338fd4b97d34d42727e79
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/22-auditing/2-user-and-permission-audit.md
@@ -0,0 +1,83 @@
+---
+title: User and Permission Audit
+summary: User and Permission Audit
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# User and Permission Audit
+
+## audit_login_logout
+
+**Parameter description**: Specifies whether to audit the MogDB user's login (including login success and failure) and logout.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 7
+
+- **0** indicates that the function of auditing users' logins and logouts is disabled.
+- **1** indicates that only successful user logins are audited.
+- **2** indicates that only failed user logins are audited.
+- **3** indicates that successful and failed user logins are audited.
+- **4** indicates that only user logouts are audited.
+- **5** indicates that successful user logouts and logins are audited.
+- **6** indicates that failed user logouts and logins are audited.
+- **7** indicates that successful user logins, failed user logins, and logouts are audited.
+
+**Default value**: **7**
+
+## audit_database_process
+
+**Parameter description**: Specifies whether to audit the MogDB user's login (including login success and failure) and logout.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range:** **0** or **1**
+
+- **0** indicates that the function of auditing MogDB start, stop, recovery, and switchover operations of a database is disabled.
+- **1** indicates that the function of auditing MogDB start, stop, recovery, and switchover operations of a database is enabled.
+
+**Default value**: **1**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **Note**:
+>
+> When MogDB starts, DN performs the switchover process. Therefore, when DN starts, the type in the audit log is system_switch.
+
+## audit_user_locked
+
+**Parameter description**: Specifies whether to audit the MogDB user's locking and unlocking.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range:** **0** or **1**
+
+- **0** indicates that the function of auditing user's locking and unlocking is disabled.
+- **1** indicates that the function of auditing user's locking and unlocking is enabled.
+
+**Default value**: **1**
+
+## audit_user_violation
+
+**Parameter description**: Specifies whether to audit the access violation operations of a user.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range:** **0** or **1**
+
+- **0** indicates that the function of auditing the access violation operations of a user is disabled.
+- **1** indicates that the function of auditing the access violation operations of a user is enabled.
+
+**Default value**: **0**
+
+## audit_grant_revoke
+
+**Parameter description**: Specifies whether to audit the granting and reclaiming of the MogDB user's permission.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range:** **0** or **1**
+
+- **0** indicates that the function of auditing the granting and reclaiming of a user's permission is disabled.
+- **1** indicates that the function of auditing the granting and reclaiming of a user's permission is enabled.
+
+**Default value**: **1**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/22-auditing/3-operation-audit.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/22-auditing/3-operation-audit.md
new file mode 100644
index 0000000000000000000000000000000000000000..635fc598db2bbd914044f18e89b396efb5fa141e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/22-auditing/3-operation-audit.md
@@ -0,0 +1,160 @@
+---
+title: Operation Auditing
+summary: Operation Auditing
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Operation Auditing
+
+## audit_system_object
+
+**Parameter description**: Specifies whether to audit the CREATE, DROP, and ALTER operations on MogDB database objects. MogDB database objects include DATABASE, USER, Schema, and TABLE. The operations on the database object can be audited by changing the value of this parameter.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 524287
+
+- **0** indicates that the function of auditing the CREATE, DROP, and ALTER operations on MogDB database objects is disabled.
+- Other values indicate that the CREATE, DROP, and ALTER operations on a certain or some MogDB database objects are audited.
+
+**Value description:**
+
+The value of this parameter is calculated by 20 binary bits. The 20 binary bits represent 20 types of MogDB database objects. If the corresponding binary bit is set to **0**, the CREATE, DROP, and ALTER operations on corresponding database objects are not audited. If it is set to **1**, the CREATE, DROP, and ALTER operations are audited. For details about the audit contents represented by these 19 binary bits, see [Table 1](#audit_system_object).
+
+**Default value**: **12295**
+
+**Table 1** Meaning of each value for the **audit_system_object** parameter<a id="audit_system_object"> </a>
+
+| **Binary Bit** | Description                                                  | Value Description                                            |
+| -------------- | ------------------------------------------------------------ | ------------------------------------------------------------ |
+| Bit 0          | Whether to audit the CREATE, DROP, and ALTER operations on databases. | **0** indicates that the CREATE, DROP, and ALTER operations on these objects are not audited.<br />**1** indicates that the CREATE, DROP, and ALTER operations on these objects are audited. |
+| Bit 1          | Whether to audit the CREATE, DROP, and ALTER operations on schemas. | **0** indicates that the CREATE, DROP, and ALTER operations on these objects are not audited.<br />**1** indicates that the CREATE, DROP, and ALTER operations on these objects are audited. |
+| Bit 2          | Whether to audit the CREATE, DROP, and ALTER operations on users. | **0** indicates that the CREATE, DROP, and ALTER operations on these objects are not audited.<br />**1** indicates that the CREATE, DROP, and ALTER operations on these objects are audited. |
+| Bit 3          | Whether to audit the CREATE, DROP, ALTER, and TRUNCATE operations on tables. | **0** indicates that the CREATE, DROP, ALTER, and TRUNCATE operations on these objects are not audited.<br />**1** indicates that the CREATE, DROP, ALTER, and TRUNCATE operations on these objects are audited. |
+| Bit 4          | Whether to audit the CREATE, DROP, and ALTER operations on indexes. | **0** indicates that the CREATE, DROP, and ALTER operations on these objects are not audited.<br />**1** indicates that the CREATE, DROP, and ALTER operations on these objects are audited. |
+| Bit 5          | Whether to audit the CREATE and DROP operations on views.    | **0** indicates that the CREATE and DROP operations on these objects are not audited.<br />**1** indicates that the CREATE and DROP operations on these objects are audited. |
+| Bit 6          | Whether to audit the CREATE, DROP, and ALTER operations on triggers. | **0** indicates that the CREATE, DROP, and ALTER operations on these objects are not audited.<br />**1** indicates that the CREATE, DROP, and ALTER operations on these objects are audited. |
+| Bit 7          | Whether to audit the CREATE, DROP, and ALTER operations on procedures/functions. | **0** indicates that the CREATE, DROP, and ALTER operations on these objects are not audited.<br />**1** indicates that the CREATE, DROP, and ALTER operations on these objects are audited. |
+| Bit 8          | Whether to audit the CREATE, DROP, and ALTER operations on tablespaces. | **0** indicates that the CREATE, DROP, and ALTER operations on these objects are not audited.<br />**1** indicates that the CREATE, DROP, and ALTER operations on these objects are audited. |
+| Bit 9          | Whether to audit the CREATE, DROP, and ALTER operations on resource pools. | **0** indicates that the CREATE, DROP, and ALTER operations on these objects are not audited.<br />**1** indicates that the CREATE, DROP, and ALTER operations on these objects are audited. |
+| Bit 10         | Whether to audit the CREATE, DROP, and ALTER operations on workloads. | **0** indicates that the CREATE, DROP, and ALTER operations on these objects are not audited.<br />**1** indicates that the CREATE, DROP, and ALTER operations on these objects are audited. |
+| Bit 11         | Whether to audit the CREATE, DROP, and ALTER operations on SERVER FOR HADOOP objects. | **0** indicates that the CREATE, DROP, and ALTER operations on these objects are not audited.<br />**1** indicates that the CREATE, DROP, and ALTER operations on these objects are audited. |
+| Bit 12         | Whether to audit the CREATE, DROP, and ALTER operations on data sources. | **0** indicates that the CREATE, DROP, and ALTER operations on these objects are not audited.<br />**1** indicates that the CREATE, DROP, and ALTER operations on these objects are audited. |
+| Bit 13         | Whether to audit the CREATE and DROP operations on Node Group objects. | **0** indicates that the CREATE and DROP operations on these objects are not audited.<br />**1** indicates that the CREATE and DROP operations on these objects are audited. |
+| Bit 14         | Whether to audit the CREATE, DROP, and ALTER operations on ROW LEVEL SECURITY objects. | **0** indicates that the CREATE, DROP, and ALTER operations on these objects are not audited.<br />**1** indicates that the CREATE, DROP, and ALTER operations on these objects are audited. |
+| Bit 15         | Whether to audit the CREATE, DROP, and ALTER operations on types. | **0** indicates that the CREATE, DROP, and ALTER operations on types are not audited.<br />**1** indicates that the CREATE, DROP, and ALTER operations on types are audited. |
+| Bit 16         | Whether to audit the CREATE, DROP, and ALTER operations on text search objects (CONFIGURATION and DICTIONARY). | **0** indicates that the CREATE, DROP, and ALTER operations on text search objects are not audited.<br />**1** indicates that the CREATE, DROP, and ALTER operations on text search objects are audited. |
+| Bit 17         | Whether to audit the CREATE, DROP, and ALTER operations on directories. | **0** indicates that the CREATE, DROP, and ALTER operations on directories are not audited.<br />**1** indicates that the CREATE, DROP, and ALTER operations on directories are audited. |
+| Bit 18         | Whether to audit the CREATE, DROP, and ALTER operations on workloads. | **0** indicates that the CREATE, DROP, and ALTER operations on types are not audited.<br />**1** indicates that the CREATE, DROP, and ALTER operations on types are audited. |
+| Bit 19         | Whether to audit the CREATE, DROP, and ALTER operations on sequences. | **0** indicates that the operations are not audited.<br />**1** indicates that the operations are audited. |
+| Bit 20         | Whether to audit the CREATE and DROP operations on CMK and CEK objects. | **0** indicates that the CREATE and DROP operations on CMK and CEK objects are not audited.<br />**1** indicates that the CREATE and DROP operations on CMK and CEK objects are audited. |
+
+## audit_dml_state
+
+**Parameter description**: Specifies whether to audit the INSERT, UPDATE, and DELETE operations on a specific table.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range:** **0** or **1**
+
+- **0** indicates that the function of auditing the DML operations (except SELECT) is disabled.
+- **1** indicates that the function of auditing the DML operations (except SELECT) is enabled.
+
+**Default value**: **0**
+
+## audit_dml_state_select
+
+**Parameter description**: Specifies whether to audit the SELECT operation.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range:** **0** or **1**
+
+- **0** indicates that the SELECT auditing function is disabled.
+- **1** indicates that the SELECT auditing function is enabled.
+
+**Default value**: **0**
+
+## audit_function_exec
+
+**Parameter description**: Specifies whether to record the audit information during the execution of the stored procedures, anonymous blocks, or user-defined functions (excluding system functions).
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range:** **0** or **1**
+
+- **0** indicates that the function of auditing the procedure or function execution is disabled.
+- **1** indicates that the function of auditing the procedure or function execution is enabled.
+
+**Default value**: **0**
+
+## audit_copy_exec
+
+**Parameter description**: Specifies whether to audit the COPY operation.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range:** **0** or **1**
+
+- **0** indicates that the COPY auditing function is disabled.
+- **1** indicates that the COPY auditing function is enabled.
+
+**Default value**: **0**
+
+## audit_set_parameter
+
+**Parameter description**: Specifies whether to audit the SET operation.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range:** **0** or **1**
+
+- **0** indicates that the SET auditing function is disabled.
+- **1** indicates that the SET auditing function is enabled.
+
+**Default value**: **1**
+
+## enableSeparationOfDuty
+
+**Parameter description**: Specifies whether the separation of three duties is enabled.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the separation of three duties is enabled.
+- **off** indicates that the separation of three duties is disabled.
+
+**Default value**: **off**
+
+## enable_nonsysadmin_execute_direct
+
+**Parameter description**: Specifies whether non-system administrators are allowed to execute the EXECUTE DIRECT ON statement.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that any user is allowed to execute the EXECUTE DIRECT ON statement.
+- **off** indicates that only the system administrator is allowed to execute the EXECUTE DIRECT ON statement.
+
+**Default value**: **off**
+
+## enable_access_server_directory
+
+**Parameter description**: Specifies whether the system administrator has the permissions to create and delete DIRECTORY objects.
+
+This parameter is a **SIGHUP** parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the system administrator has the permission to create and delete DIRECTORY objects.
+- **off** indicates that the system administrator does not have the permissions to create and delete DIRECTORY objects.
+
+**Default value**: **off**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - For security purposes, only initial users can create and delete DIRECTORY objects by default.
+> - If **enable_access_server_directory** is set to **on**, system administrators (including initial users) can create and delete DIRECTORY objects when **enableSeparationOfDuty** is set to **off**. When **enableSeparationOfDuty** is set to **on**, only the initial users can create and delete DIRECTORY objects.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/23-upgrade-parameters.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/23-upgrade-parameters.md
new file mode 100644
index 0000000000000000000000000000000000000000..7669c0b46bf67d1d67f7bad8c9798efbe230fe9e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/23-upgrade-parameters.md
@@ -0,0 +1,43 @@
+---
+title: Upgrade Parameters
+summary: Upgrade Parameters
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Upgrade Parameters
+
+## IsInplaceUpgrade
+
+**Parameter description**: Specifies whether an upgrade is ongoing. This parameter cannot be modified by users.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates an upgrade is ongoing.
+- **off** indicates no upgrade is ongoing.
+
+**Default value**: **off**
+
+## inplace_upgrade_next_system_object_oids
+
+**Parameter description**: Indicates the OID of a new system object during the in-place upgrade. This parameter cannot be modified by users.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string
+
+**Default value**: empty
+
+## upgrade_mode
+
+**Parameter description**: Specifies the upgrade mode. You are advised not to modify this parameter.
+
+**Value range**: an integer ranging from 0 to *INT_MAX*
+
+- **0** indicates that no upgrade is ongoing.
+- **1** indicates that a local upgrade is ongoing.
+- **2** indicates that a grayscale upgrade is ongoing.
+
+**Default value**: **0**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/24-miscellaneous-parameters.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/24-miscellaneous-parameters.md
new file mode 100644
index 0000000000000000000000000000000000000000..944701989413993209adc3a01b93b82a8d290f79
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/24-miscellaneous-parameters.md
@@ -0,0 +1,206 @@
+---
+title: Miscellaneous Parameters
+summary: Miscellaneous Parameters
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Miscellaneous Parameters
+
+## enable_default_ustore_table
+
+**Parameter description:** Specifies whether to enable the UStore storage engine by default. If this parameter is set to **on**, all created tables are UStore tables.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range:** [off,on]
+
+**Default value**: **off**
+
+## reserve_space_for_nullable_atts
+
+**Parameter description**: Specifies whether to reserve space for the nullable attribute of an Ustore table. If this parameter is set to **on**, space is reserved for the nullable attribute of the Ustore table by default.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range:** [off,on]
+
+**Default value**: **on**
+
+## ustore_attr
+
+**Parameter description:** Specifies the UStore test parameters.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+You can set **enable_ustore_partial_seqscan** (copy selective columns only during sequential scanning in the ustore table), **enable_candidate_buf_usage_count** (whether dirty pages are evicted and added to the use count weight), and **ustats_tracker_naptime** (time for reloading the statistics file). **umax_search_length_for_prune** (number of blocks to be pruned before table extension) and **ustore_unit_test** (starting the UStore white box test). The setting method is ustore_att ='**enable_ustore_partial_seqscan**=on'.
+
+**Value range**: a string
+
+## server_version
+
+**Parameter description**: Specifies the server version number.
+
+This parameter is a fixed parameter of the INTERNAL type. It can be viewed but cannot be modified. This parameter is inherited from the PostgreSQL kernel, indicating that the current database kernel is compatible with the server_version version corresponding to PostgreSQL. This parameter is reserved to ensure the ecosystem compatibility of the northbound external tool interface (query when the tool is connected). This parameter is not recommended. To query the server version, use the opengauss_version() function.
+
+**Value range**: a string
+
+**Default value**: **9.2.4**
+
+## server_version_num
+
+**Parameter description**: Specifies the server version number.
+
+This parameter is a fixed parameter of the INTERNAL type. It can be viewed but cannot be modified. This parameter is inherited from the PostgreSQL kernel, indicating that the current database kernel is compatible with the server_version_num version corresponding to PostgreSQL. This parameter is reserved to ensure the ecosystem compatibility of the northbound external tool API. (query when the tool is connected).
+
+**Value range**: an integer
+
+**Default value**: **90204**
+
+## block_size
+
+**Parameter description**: Specifies the block size of the current database.
+
+This parameter is an INTERNAL parameter. The value of this parameter cannot be modified.
+
+**Value**:**8192**
+
+**Default value**: **8192**
+
+## segment_size
+
+**Parameter description**: Specifies the segment file size of the current database.
+
+This parameter is an INTERNAL parameter. The value of this parameter cannot be modified.
+
+**Unit**: 8 KB
+
+**Default value**: 131072, that is, 1 GB
+
+## max_index_keys
+
+**Parameter description**: Specifies the maximum number of index keys supported by the current database.
+
+This parameter is an INTERNAL parameter. The value of this parameter cannot be modified.
+
+**Default value**: **32**
+
+## integer_datetimes
+
+**Parameter description**: Specifies whether the date and time are in the 64-bit integer format.
+
+This parameter is an INTERNAL parameter. The value of this parameter cannot be modified.
+
+**Value range**: Boolean
+
+- **on** indicates that the 64-bit integer format is used.
+- **off** indicates that the 64-bit integer format is not used.
+
+**Default value**: **on**
+
+## lc_collate
+
+**Parameter description:** Specifies the locale in which sorting of textual data is done.
+
+This parameter is an INTERNAL parameter. The value of this parameter cannot be modified.
+
+**Default value**: Determined by the configuration set during the MogDB installation and deployment.
+
+## lc_ctype
+
+**Parameter description**: Specifies the locale that determines character classifications. For example, it specifies what a letter and its upper-case equivalent are.
+
+This parameter is an INTERNAL parameter. The value of this parameter cannot be modified.
+
+**Default value**: Determined by the configuration set during the MogDB installation and deployment.
+
+## max_identifier_length
+
+**Parameter description**: Specifies the maximum identifier length.
+
+This parameter is an INTERNAL parameter. The value of this parameter cannot be modified.
+
+**Value range**: an integer
+
+**Default value**: **63**
+
+## server_encoding
+
+**Parameter description**: Specifies the database encoding (character set).
+
+By default, gs_initdb will initialize the setting of this parameter based on the current system environment. You can also run the **locale** command to check the current configuration environment.
+
+This parameter is an INTERNAL parameter. The value of this parameter cannot be modified.
+
+**Default value:** determined by the current system environment when the database is created.
+
+## enable_upgrade_merge_lock_mode
+
+**Parameter description**: If this parameter is set to **on**, the delta merge operation internally increases the lock level, and errors can be prevented when update and delete operations are performed at the same time.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- If this parameter is set to **on**, the delta merge operation internally increases the lock level. In this way, when the **DELTAMERGE** operation is concurrently performed with the **UPDATE** or **DELETE** operation, one operation can be performed only after the previous one is complete.
+- If this parameter is set to **off**, and any two of the **DELTAMERGE**, **UPDATE**, and **DELETE** operations are concurrently performed to data in a row in the delta table of the HDFS table, errors will be reported during the later operation, and the operation will stop.
+
+**Default value**: **off**
+
+## transparent_encrypted_string
+
+**Parameter description**: Specifies a sample string that is transparently encrypted. Its value is generated by encrypting **TRANS_ENCRYPT_SAMPLE_STRING** using a database secret key. The ciphertext is used to check whether the DEK obtained during secondary startup is correct. If it is incorrect, database nodes will not be started. This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string. An empty string indicates that MogDB is a not encrypted.
+
+**Default value**: empty
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** Do not set this parameter manually. Otherwise, MogDB may become faulty.
+
+## transparent_encrypt_kms_url
+
+**Parameter description**: Specifies the URL for obtaining the database secret key to be transparently encrypted. It must contain only the characters specified in RFC3986, and the maximum length is 2047 bytes. The format is **kms://***Protocol***@***KMS host name 1***;***KMS host name 2***:***KMS port number***/kms**, for example, **kms://https@linux175:29800/**.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string
+
+**Default value**: empty
+
+## transparent_encrypt_kms_region
+
+**Parameter description**: Specifies the deployment region of MogDB. It must contain only the characters specified in RFC3986, and the maximum length is 2047 bytes.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string
+
+**Default value**: empty
+
+## basebackup_timeout
+
+**Parameter description**: Specifies the timeout period for connection during which no read/write operations are performed after backup transmission is complete. When the gs_basebackup tool is used for transmission, if a higher compression rate is specified, the timeout may occur after the tablespace transmission is complete. (The transmission data needs to be compressed in the client.)
+
+**Value range**: an integer ranging from 0 to *INT_MAX*. The unit is second. **0**: indicates that the parameter is disabled.
+
+**Default value**: 600s
+
+## datanode_heartbeat_interval
+
+**Parameter description**: Specifies the interval at which heartbeat messages are sent between heartbeat threads. You are advised to set this parameter to a value no more than wal_receiver_timeout/2.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1000 to 60000. The unit is ms.
+
+Default value: **1s**
+
+## max_concurrent_autonomous_transactions
+
+**Parameter description**: Specifies the maximum number of autonomous transaction connections, that is, the maximum number of concurrent autonomous transactions executed at the same time. If this parameter is set to **0**, autonomous transactions cannot be executed.
+
+This parameter is an INTERNAL parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: 0-1024
+
+**Default value:** **10**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/25-wait-events.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/25-wait-events.md
new file mode 100644
index 0000000000000000000000000000000000000000..fb80772fd6a704ac30b3d7fc8c7b3e86e3e31813
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/25-wait-events.md
@@ -0,0 +1,21 @@
+---
+title: Wait Events
+summary: Wait Events
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Wait Events
+
+## enable_instr_track_wait
+
+**Parameter description**: Specifies whether to enable real-time collection of wait event information.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the function of collecting wait event information is enabled.
+- **off** indicates that the function of collecting wait event information is disabled.
+
+**Default value**: **on**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/26-query.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/26-query.md
new file mode 100644
index 0000000000000000000000000000000000000000..32995336b25b3ecf622f0d6595a9132d61bc85ca
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/26-query.md
@@ -0,0 +1,179 @@
+---
+title: Query
+summary: Query
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Query
+
+## instr_unique_sql_count
+
+**Parameter description**: Specifies the maximum number of Unique SQL records to be collected. The value **0** indicates that the function of collecting Unique SQL information is disabled.
+
+If the value is changed from a larger one to a smaller one, Unique SQL statistics will be reset and re-collected. There is no impact if the value is changed from a smaller one to a larger one.
+
+If the number of unique SQL entries generated in the system is greater than **instr_unique_sql_count** and the function of automatically eliminating unique SQL entries is enabled, the system automatically eliminates a certain proportion of entries based on the update time of unique SQL statements in descending order. In this way, new unique SQL entries can be collected. If the automatic elimination function is not enabled, new unique SQL information generated by the system will not be collected.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 2147483647
+
+**Default value**: **100**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **CAUTION:**
+>
+> - If the automatic elimination function is enabled and this parameter is set to a small value, the system may frequently perform automatic elimination, which may affect the database system performance. Therefore, you are advised to set this parameter to **200000**.
+> - If automatic elimination is enabled and this parameter is set to a large value (for example, 38347922), a large memory problem may occur during the clearance. As a result, the clearance fails.
+
+## instr_unique_sql_track_type
+
+**Parameter description**: Specifies which SQL statements are recorded in Unique SQL.
+
+This parameter is an INTERNAL parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: enumerated values
+
+**top**: Only top-level SQL statements are recorded.
+
+**Default value**: **top**
+
+## enable_instr_rt_percentile
+
+**Parameter description**: Specifies whether to enable the function of calculating the response time of 80% and 95% SQL statements in the system.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the function of calculating the response time of 80% and 95% SQL statements is enabled.
+- **off** indicates that the function of calculating the response time of 80% and 95% SQL statements is disabled.
+
+**Default value**: **on**
+
+## percentile
+
+**Parameter description**: Specifies the percentage of SQL statements whose response time is to be calculated by the background calculation thread.
+
+This parameter is an INTERNAL parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string
+
+**Default value**: **80, 95**
+
+## instr_rt_percentile_interval
+
+**Parameter description**: Specifies the interval at which the background calculation thread calculates the SQL response time.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 3600. The unit is s.
+
+**Default value**: **10s**
+
+## enable_instr_cpu_timer
+
+**Parameter description**: Specifies whether to capture the CPU time consumed during SQL statement execution.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates the CPU time consumed during SQL statement execution is captured.
+- **off** indicates the CPU time consumed during SQL statement execution is not captured.
+
+**Default value**: **on**
+
+## enable_stmt_track
+
+**Parameter description**: Specifies whether to enable the full/slow SQL statement feature.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- on: Full/Slow SQL capture is enabled.
+- off: Full /Slow SQL capture is disabled.
+
+**Default value**: **on**
+
+## track_stmt_session_slot
+
+**Parameter description**: Specifies the maximum number of full/slow SQL statements that can be cached in a session. If the number of full/slow SQL statements exceeds this value, new statements will not be traced until the flush thread flushes the cached statements to the disk to reserve idle space.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 2147483647
+
+**Default value**: **1000**
+
+## track_stmt_details_size
+
+**Parameter description**: Specifies the maximum size (in bytes) of execution events that can be collected by a single statement.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 100000000
+
+**Default value**: **4096**
+
+## track_stmt_retention_time
+
+**Parameter description**: Specifies the retention period of full/slow SQL statement records. This parameter is a combination of parameters. This parameter is read every 60 seconds and records exceeding the retention period are deleted. Only the sysadmin user can access this parameter.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string
+
+This parameter consists of two parts in the format of 'full sql retention time, slow sql retention time'.
+
+**full sql retention time** indicates the retention time of full SQL statements. The value ranges from 0 to 86400.
+
+**slow sql retention time** indicates the retention time of slow SQL statements. The value ranges from 0 to 604800.
+
+**Default value**: **3600,604800**
+
+## track_stmt_stat_level
+
+**Parameter description**: Determines the level of statement execution tracing.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix). The value is case-insensitive.
+
+**Value range**: a string
+
+This parameter consists of two parts in the format of 'full sql stat level, slow sql stat level'.
+
+The first part indicates the tracing level of full SQL statements. The value can be **OFF**, **L0**, **L1**, or **L2**.
+
+The second part indicates the tracing level of slow SQL statements. The value can be **OFF**, **L0**, **L1**, or **L2**.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** If the full SQL tracing level is not **OFF**, the current SQL tracing level is the higher level (L2 &gt; L1 &gt; L0) of the full SQL and slow SQL statements. For details about the levels, see Table 1 [GUC parameters](30-appendix).
+
+**Default value**: **OFF,L0**
+
+## unique_sql_clean_ratio
+
+**Parameter description**: Specifies the ratio of the number of unique SQL entries that are automatically eliminated each time to the preset upper limit (**instr_unique_sql_count**) when the number of unique SQL entries generated in the system is greater than or equal to **instr_unique_sql_count**.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Double type ranging from 0 to 0.2.
+
+**Default value**: **0.1**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **CAUTION:**
+>
+> - If this parameter is set to a small value, only a few entries are cleared each time, which may cause frequent clearance. If this parameter is set to a large value, a large number of entries are cleared each time, which may cause frequent insertion. The recommended value is **0.1**.
+> - If **unique_sql_clean_ratio** is set to **0**, automatic elimination is not disabled. Use **enable_auto_clean_unique_sql** to determine whether to enable automatic elimination. When automatic elimination is enabled and **unique_sql_clean_ratio** is set to **0**, **unique_sql_clean_ratio** is automatically reset to the default value **0.1**.
+
+## enable_auto_clean_unique_sql
+
+**Parameter description**: Specifies whether to enable the automatic elimination function of unique SQL statements when the number of unique SQL statements generated in the system is greater than or equal to the value of **instr_unique_sql_count**.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+**Default value**: **off**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **CAUTION:** Some snapshot information comes from unique SQL statements. Therefore, when automatic elimination is enabled, if the selected start snapshot and end snapshot exceed the elimination time, the WDR report cannot be generated.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/27-system-performance-snapshot.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/27-system-performance-snapshot.md
new file mode 100644
index 0000000000000000000000000000000000000000..5351489b26a7be3fb0d1b53c3c1c1e3a2bd91323
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/27-system-performance-snapshot.md
@@ -0,0 +1,124 @@
+---
+title: System Performance Snapshot
+summary: System Performance Snapshot
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# System Performance Snapshot
+
+## enable_wdr_snapshot
+
+**Parameter description**: Specifies whether to enable the database monitoring snapshot function.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the database monitoring snapshot function is enabled.
+- **off** indicates that the database monitoring snapshot function is disabled.
+
+**Default value**: **off**
+
+## wdr_snapshot_retention_days
+
+**Parameter description**: Specifies the number of days database monitoring snapshots are retained. When the value of **wdr_snapshot_retention_days** is exceeded, the system cleans up snapshots with the smallest snapshot_id at the interval specified by **wdr_snapshot_interval**.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1 to 8
+
+**Default value**: **8**
+
+## wdr_snapshot_query_timeout
+
+**Parameter description**: Specifies the execution timeout for the SQL statements associated with database monitoring snapshot operations. If the SQL statement execution is not complete and a result is not returned within the specified time, the snapshot operation fails.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 100 to *INT_MAX*. The unit is s.
+
+**Default value**: **100s**
+
+## wdr_snapshot_interval
+
+**Parameter description**: Specifies the interval at which the background thread Snapshot automatically performs snapshot operations on the database monitoring data.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 10 to 60. The unit is m.
+
+**Default value**: **1h**
+
+## asp_flush_mode
+
+**Parameter description**: Specifies the mode for the ASP to update data to the disk. The value can be **file** (default value), **table** (system catalog), or **all** (system catalog and file). Only the sysadmin user can access this parameter.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string, which can be **table**, **file**, or **all**
+
+**Default value**: **table**
+
+## asp_flush_rate
+
+**Parameter description**: When the number of samples reaches the value of **asp_sample_num**, the samples in the memory are updated to the disk based on a certain proportion. **asp_flush_rate** indicates the update proportion. If this parameter is set to **10**, it indicates that the update ratio is 10:1.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1 to 10
+
+**Default value**: **10**
+
+## asp_log_filename
+
+**Parameter description**: Specifies the file name format when writing files using ASP. Only the sysadmin user can access this parameter.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string
+
+**Default value**: **asp-%Y-%m-%d_%H%M%S.log**
+
+## asp_retention_days
+
+**Parameter description**: Specifies the maximum number of days for reserving ASP samples when they are written to the system catalog.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1 to 7
+
+**Default value**: **2**
+
+## asp_sample_interval
+
+**Parameter description**: Specifies the sampling interval.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1 to 10. The unit is s.
+
+**Default value**: **1s**
+
+## asp_sample_num
+
+**Parameter description**: Specifies the maximum number of samples allowed in the LOCAL_ACTIVE_SESSION view. Only the sysadmin user can access this parameter.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 10000 to 100000
+
+**Default value**: **100000**
+
+## enable_asp
+
+**Parameter description:**Specifies whether to enable the active session profile function.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on**: The function is enabled.
+- **off**: The function is disabled.
+
+**Default value**: **on**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/27.1-security-configuration.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/27.1-security-configuration.md
new file mode 100644
index 0000000000000000000000000000000000000000..997c16cc5f883e3bd2751bad67d0e2e36d87c1a1
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/27.1-security-configuration.md
@@ -0,0 +1,84 @@
+---
+title: Security Configuration
+summary: Security Configuration
+author: Zhang Cuiping
+date: 2021-11-08
+---
+
+# Security Configuration
+
+## elastic_search_ip_addr
+
+**Parameter description**: Specifies the IP address of the Elasticsearch system.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string
+
+**Default value**: **'https:127.0.0.1'**
+
+## enable_security_policy
+
+**Parameter description**: Specifies whether the unified audit and dynamic data masking policies take effect.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+**on**: The security policy is enabled.
+
+**off**: The security policy is disabled.
+
+**Default value**: **off**
+
+## use_elastic_search
+
+**Parameter description**: Specifies whether to send unified audit logs to Elasticsearch. If **enable_security_policy** and this parameter are enabled, unified audit logs are sent to Elasticsearch through HTTP or HTTPS (used by default). After this parameter is enabled, ensure that the Elasticsearch service corresponding to **elastic_search_ip_addr**can be properly connected. Otherwise, the process fails to be started.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+**on**: Unified audit logs are sent to Elasticsearch.
+
+**off**: Unified audit logs are not sent to Elasticsearch.
+
+**Default value**: **off**
+
+## is_sysadmin
+
+**Parameter description**: Specifies whether the current user is an initial user.
+
+This parameter is a fixed INTERNAL parameter and cannot be modified.
+
+**Value range**: Boolean
+
+**on** indicates that the user is an initial user.
+
+**off** indicates that the user is not an initial user.
+
+**Default value**: **off**
+
+## enable_tde
+
+**Parameter description**: Specifies whether to enable the TDE function. Set this parameter to **on** before creating an encrypted table. If this parameter is set to **off**, new encrypted tables cannot be created. The created encrypted table is decrypted only when data is read and is not encrypted when the data is written.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+**on**: The TDE function is enabled.
+
+**off**: The TDE function is disabled.
+
+**Default value**: **off**
+
+## tde_cmk_id
+
+**Parameter description**: Specifies the CMK ID of the database instance used by the TDE function. The ID is generated by KMS. The CMK of the database instance is used to encrypt the DEK. When the DEK needs to be decrypted, a request packet needs to be sent to KMS. The DEK ciphertext and the ID of the corresponding CMK are sent to KMS.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string
+
+**Default value**: **""**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/28-equality-query-in-a-fully-encrypted-database.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/28-equality-query-in-a-fully-encrypted-database.md
new file mode 100644
index 0000000000000000000000000000000000000000..0a66a4f4ffc816d2b4f84946c888a9422ded0cf6
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/28-equality-query-in-a-fully-encrypted-database.md
@@ -0,0 +1,23 @@
+---
+title: Equality Query in a Fully-encrypted Database
+summary: Equality Query in a Fully-encrypted Database
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Equality Query in a Fully-encrypted Database
+
+## enable_full_encryption
+
+**Parameter description**: Specifies whether the fully-encrypted database takes effect.
+
+This parameter is a BACKEND parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+After enable_full_encryption is set to on, you need to enter the "-C" parameter or "-enable-client-encryption" when using gsql to connect to the database, otherwise the connection will not succeed.
+
+**Value range**: Boolean
+
+- **on**: The fully-encrypted database is enabled.
+- **off**: The fully-encrypted database is disabled.
+
+**Default value**: **off**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/29-global-temporary-table.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/29-global-temporary-table.md
new file mode 100644
index 0000000000000000000000000000000000000000..96b650da72c3d8efd5ea6a411257044d96582572
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/29-global-temporary-table.md
@@ -0,0 +1,31 @@
+---
+title: Global Temporary Table
+summary: Global Temporary Table
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Global Temporary Table
+
+## max_active_global_temporary_table
+
+**Parameter description**: Specifies whether global temporary tables can be created.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 1000000
+
+- **0**: The global temporary table function is disabled.
+- &gt; 0: The global temporary table function is enabled.
+
+**Default value**: **1000**
+
+## vacuum_gtt_defer_check_age
+
+**Parameter description**: Checks the differences between the global temporary table relfrozenxid and the ordinary table after VACUUM is executed. WARNING is generated if the difference value exceeds the specified parameter value. Use the default value for this parameter.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 1000000
+
+**Default value**: **10000**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/29.1-HyperLogLog.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/29.1-HyperLogLog.md
new file mode 100644
index 0000000000000000000000000000000000000000..7644c6b720d6d2febf56e9e030ff7caaa78f3f7e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/29.1-HyperLogLog.md
@@ -0,0 +1,101 @@
+---
+title: HyperLogLog
+summary: HyperLogLog
+author: Zhang Cuiping
+date: 2021-11-08
+---
+
+# HyperLogLog
+
+## hll_default_log2m
+
+**Parameter description**: Specifies the number of buckets for HLL data. The number of buckets affects the precision of distinct values calculated by HLL. The more buckets there are, the smaller the deviation is. The deviation range is as follows: [-1.04/2log2m\*1⁄2, +1.04/2log2m*1⁄2]
+
+This parameter is a **USERSET** parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 10 to 16
+
+**Default value**: **14**
+
+## hll_default_log2explicit
+
+**Parameter description**: Specifies the default threshold for switching from the explicit mode to the sparse mode.
+
+This parameter is a **USERSET** parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 12 The value **0** indicates that the explicit mode is skipped. The value 1 to 12 indicates that the mode is switched when the number of distinct values reaches 2hll_default_log2explicit.
+
+**Default value**: **10**
+
+## hll_default_log2sparse
+
+**Parameter description**: Specifies the default threshold for switching from the **sparse** mode to the **full** mode.
+
+This parameter is a **USERSET** parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 14 The value **0** indicates that the explicit mode is skipped. The value 1 to 14 indicates that the mode is switched when the number of distinct values reaches 2hll_default_log2sparse.
+
+**Default value**: **12**
+
+## hll_duplicate_check
+
+**Parameter description**: Specifies whether duplicatecheck is enabled by default.
+
+This parameter is a **USERSET** parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: **0** or **1** **0**: disabled; **1**: enabled
+
+**Default value**: **0**
+
+## hll_default_regwidth (Discarded)
+
+**Parameter description**: Specifies the number of bits in each bucket for HLL data. A larger value indicates more memory occupied by HLL. **hll_default_regwidth** and **hll_default_log2m** determine the maximum number of distinct values that can be calculated by HLL. Currently, **regwidth** is set to a fixed value and is no longer used.
+
+This parameter is a **USERSET** parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1 to 5
+
+**Default value**: **5**
+
+## hll_default_expthresh (Discarded)
+
+**Parameter description**: Specifies the default threshold for switching from the **explicit** mode to the **sparse** mode. Currently, the **hll_default_log2explicit** parameter is used to replace the similar function.
+
+This parameter is a **USERSET** parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from -1 to 7 **-1** indicates the auto mode; **0** indicates that the **explicit** mode is skipped; a value from 1 to 7 indicates that the mode is switched when the number of distinct values reaches 2hll_default_expthresh.
+
+**Default value**: **-1**
+
+## hll_default_sparseon (Discarded)
+
+**Parameter description**: Specifies whether to enable the **sparse** mode by default. Currently, the **hll_default_log2sparse** parameter is used to replace the similar function. When **hll_default_log2sparse** is set to **0**, the **sparse** mode is disabled.
+
+This parameter is a **USERSET** parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: **0** or **1** **0** indicates that the **sparse** mode is disabled by default. **1** indicates that the **sparse** mode is enabled by default.
+
+**Default value**: **1**
+
+## hll_max_sparse (Discarded)
+
+**Parameter description**: Specifies the size of **max_sparse**. Currently, the **hll_default_log2sparse** parameter is used to replace the similar function.
+
+This parameter is a **USERSET** parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from -1 to 2147483647
+
+**Default value**: **-1**
+
+## enable_compress_hll (Discarded)
+
+**Parameter description**: Specifies whether to enable memory optimization for HLL. Currently, the HLL memory has been optimized, and this parameter is no longer used.
+
+This parameter is a **USERSET** parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** or **true** indicates that memory optimization is enabled.
+- **off** or **false** indicates that memory optimization is disabled.
+
+**Default value**: **off**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/3-connection-and-authentication/1-connection-settings.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/3-connection-and-authentication/1-connection-settings.md
new file mode 100644
index 0000000000000000000000000000000000000000..965c9d4a4f2f96f655242505c7eadf252cf8226a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/3-connection-and-authentication/1-connection-settings.md
@@ -0,0 +1,189 @@
+---
+title: Connection Settings
+summary: Connection Settings
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Connection Settings
+
+This section describes parameters related to client-server connection modes.
+
+## listen_addresses
+
+**Parameter description**: Specifies the TCP/IP addresses that a server listens to for connections from the client. This parameter specifies the IP address used by the MogDB server to listen on, such as IPv4 address or IPv6 address(if supported). A server may have multiple NICs, and each NIC can be bound with multiple IP address. This parameter specifies the IP addresses which the MogDB server is bound. And the client can use the IP address specified in this parameter to connect to MogDB or send requests to MogDB.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**:
+
+- Host name or IP address. Multiple values are separated with commas (,).
+- Asterisk `*` or `0.0.0.0`, indicating that all IP addresses will be listened to, which is not recommended due to potential security risks. This parameter must be used together with valid addresses (for example, the local IP address). Otherwise, the build may fail. At the same time, when the configuration is `*` or `0.0.0.0` in the active/standby environment, the localport port number in the postgresql.conf file under the database path of the active node cannot be the database dataPortBase+1, otherwise the database cannot be started.
+- If the parameter is not specified, the server does not listen to any IP address. In this case, only Unix domain sockets can be used for database connections.
+
+**Default value**: After the database instance is installed, the default value is configured according to the IP address of different instances in the XML configuration file. The default value for the DN instance is **'x.x.x.x'**.
+
+## local_bind_address
+
+**Parameter description**: Specifies the host IP address bound to the current node for connecting to other nodes in MogDB.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Default value**: After the database instance is installed, the default value is configured according to the IP address of different instances in the XML configuration file. The default value for the DN instance is **'x.x.x.x'**.
+
+## port
+
+**Parameter description**: Specifies the TCP port listened on by the MogDB.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** This parameter is specified in the configuration file during installation. Do not modify this parameter unless absolutely necessary. Otherwise, database communication will be affected.
+
+**Value range**: an integer ranging from 1 to 65535
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - When setting the port number, ensure that the port number is not in use. When setting the port numbers of multiple instances, ensure that the port numbers do not conflict.
+> - Ports 1 to 1023 are reserved for the operating system. Do not use them.
+> - When the database instance is installed using the configuration file, pay attention to the ports reserved in the communication matrix in the configuration file. For example, *dataPortBase* + 1 needs to be reserved as the port used by internal tools, and *dataPortBase* + 6 needs to be reserved as the communication port of the flow engine message queue. Therefore, during database instance installation, the maximum port number is **65529** for DNs. Ensure that the port number does not conflict with each other.
+
+**Default value**: **5432** (The actual value is specified in the configuration file during installation.)
+
+## max_connections
+
+**Parameter description**: Specifies the maximum number of concurrent connections to the database. This parameter influences the concurrent processing capability of MogDB.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer. The minimum value is **10** (greater than *max_wal_senders*). The theoretical maximum value is **262143**. The actual maximum value is a dynamic value, which is calculated using the formula 262143 -_job_queue_processes_ - *autovacuum_max_workers* - *AUXILIARY_BACKENDS* - *AV_LAUNCHER_PROCS*. The values of job_queue_processes, autovacuum_max_workers, and max_inner_tool_connections depend on the settings of the corresponding GUC parameters. *AUXILIARY_BACKENDS*indicates the number of reserved auxiliary threads, which is fixed to 20.*AV_LAUNCHER_PROCS* indicates the number of reserved lancher threads for autovacuum, which is fixed to 2.
+
+**Default value**: **200**
+
+**Setting suggestions**:
+
+Retain the default value of this parameter on the primary node of the databases.
+
+**Impact of incorrect configuration:**
+
+- If the value of *max_connections* is too large and exceeds the dynamic maximum value described in the formula, the node fails to be started and the error message " invalid value for parameter "max_connections"" is displayed.
+- If only the value of *max_connections* is increased while the memory parameter is not adjusted in proportion according to the external egress specifications, when the service load is heavy, the memory may be insufficient, and the error message "memory is temporarily unavailable" is displayed.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - If the number of connections of the administrator exceeds the value of *max_connections*, the administrator can still connect to the database after the connections are used up by common users. If the number of connections exceeds the value of *sysadmin_reserved_connections*, an error is reported. That is, the maximum number of connections of the administrator is equal to the value of *max_connections* + *sysadmin_reserved_connections*.
+> - For common users, internal jobs use some connections. Therefore, the value of this parameter is slightly less than that of *max_connections*. The value depends on the number of internal connections.
+
+## max_inner_tool_connections
+
+**Parameter description**: Specifies the maximum number of concurrent connections of a tool which is allowed to connect to the database. This parameter influences the concurrent connection capability of the MogDB tool.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to *MIN* (which takes the smaller value between **262143** and *max_connections*). For details about how to calculate the value of *max_connection*, see the preceding description.
+
+**Default value**: **50** for each database node. If the default value is greater than the maximum value supported by the kernel (determined when the **gs_initdb** command is executed), an error message is displayed.
+
+**Setting suggestions**:
+
+Retain the default value of this parameter on the primary node of the databases.
+
+If this parameter is set to a large value, MogDB requires more System V shared memories or semaphores, which may exceed the default maximum configuration of the OS. In this case, modify the value as needed.
+
+## sysadmin_reserved_connections
+
+**Parameter description**: Specifies the minimum number of connections reserved for administrators. You are advised not to set this parameter to a large value. This parameter is used together with the *max_connections* parameter. The maximum number of connections of the administrator is equal to the value of *max_connections* + *sysadmin_reserved_connections*.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to *MIN* (which takes the smaller value between **262143** and *max_connections*). For details about how to calculate the value of *max_connection*, see the preceding description.
+
+**Default value**: **3**
+
+## unix_socket_directory
+
+**Parameter description**: Specifies the Unix domain socket directory that the MogDB server listens to for connections from the client.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+The parameter length limit varies by OS. If the length is exceeded, the error "Unix-domain socket path xxx is too long" will be reported.
+
+**Value range**: a string
+
+**Default value**: empty. The actual value is specified by the configuration file during installation.
+
+## unix_socket_group
+
+**Parameter description**: Specifies the group of the Unix domain socket (the user of a socket is the user that starts the server). This parameter can work with **[unix_socket_permissions](#unix_socket_permissions)** to control socket access.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string. If this parameter is set to an empty string, the default group of the current user is used.
+
+**Default value**: an empty string
+
+## unix_socket_permissions
+
+**Parameter description**: Specifies access permissions for the Unix domain socket.
+
+The Unix domain socket uses the usual permission set of the Unix file system. The value of this parameter should be a number (acceptable for the **chmod** and **umask** commands). If a user-defined octal format is used, the number must start with 0.
+
+You are advised to set it to **0770** (only allowing access from users connecting to the database and users in the same group as them) or **0700** (only allowing access from users connecting to the database).
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: 0000 to 0777
+
+**Default value**: 0777
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** In the Linux OS, a document has one document attribute and nine permission attributes, which consists of the read (r), write (w), and execute (x) permissions of the Owner, Group, and Others groups. The r, w, and x permissions are represented by the following numbers:
+>
+> r: 4
+>
+> w: 2
+>
+> x: 1
+>
+> -: 0
+>
+> The three attributes in a group are accumulative.
+>
+> For example, **-rwxrwx-** indicates the following permissions:
+>
+> owner = rwx = 4+2+1 = 7
+>
+> group = rwx = 4+2+1 = 7
+>
+> others = - = 0+0+0 = 0
+>
+> The permission of the file is 0770.
+
+## application_name
+
+**Parameter description**: Specifies the client name used in the current connection request.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range:** a string
+
+**Default value**: empty (The actual value is the name of the application connected to the backend.)
+
+## connection_info
+
+**Parameter description**: Specifies the database connection information, including the driver type, driver version, driver deployment path, and process owner.
+
+This parameter is a USERSET parameter used for O&M. You are advised not to change the parameter value.
+
+**Value range:** a string
+
+**Default value**: empty
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - An empty string indicates that the driver connected to the database does not support automatic setting of the **connection_info** parameter or the parameter is not set by users in applications.
+> - The following is an example of the concatenated value of **connection_info**:
+>
+> ```
+> {"driver_name":"ODBC","driver_version": "(MogDB 2.1.1 build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr","driver_path":"/usr/local/lib/psqlodbcw.so","os_user":"omm"}
+> ```
+>
+> **driver_name** and **driver_version** are displayed by default. Whether **driver_path** and **os_user** are displayed is determined by users.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/3-connection-and-authentication/2-security-and-authentication.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/3-connection-and-authentication/2-security-and-authentication.md
new file mode 100644
index 0000000000000000000000000000000000000000..032ac6bafbff449e6e387e444c0add954f1dfc65
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/3-connection-and-authentication/2-security-and-authentication.md
@@ -0,0 +1,402 @@
+---
+title: Security and Authentication (postgresql.conf)
+summary: Security and Authentication (postgresql.conf)
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Security and Authentication (postgresql.conf)
+
+This section describes parameters about client-to-server authentication.
+
+## authentication_timeout
+
+**Parameter description**: Specifies the longest duration to wait before the client authentication times out. If a client is not authenticated by the server within the period, the server automatically disconnects from the client so that the client does not occupy connection resources.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1 to 600. The smallest unit is s.
+
+**Default value**: **1min**
+
+## auth_iteration_count
+
+**Parameter description**: Specifies the number of iterations during the generation of encryption information for authentication.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 2048 to 134217728
+
+**Default value**: **10000**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> If the number of iterations is too small, the password storage security is reduced. If the number of iterations is too large, the performance deteriorates in scenarios involving password encryption, such as authentication and user creation. Set the number of iterations based on actual hardware conditions. You are advised to retain the default value.
+
+## session_authorization
+
+**Parameter description**: Specifies the user ID of the current session.
+
+This parameter is an internal parameter of the USERSET type and can be set only using the [SET SESSION AUTHORIZATION](130-SET-SESSION-AUTHORIZATION) syntax.
+
+**Value range**: a string
+
+**Default value**: **NULL**
+
+## session_timeout
+
+**Parameter description**: Specifies the longest duration allowed when no operations are performed on a client after it is connected to the server.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 86400. The smallest unit is s. **0** indicates that the timeout is disabled.
+
+**Default value**: **10min**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> The gsql client of MogDB has an automatic reconnection mechanism. For local connection of initialized users, the client reconnects to the server if the connection breaks after the timeout.
+
+## ssl
+
+**Parameter description**: Specifies whether the SSL connection is enabled. Read **Using gsql to Connect to a Database** before setting this parameter.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the SSL connection is enabled.
+- **off** indicates that the SSL connection is not enabled.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> MogDB supports SSL when a client connects to the primary node of the database. You are advised to enable SSL connections only on the primary node of the database. On database node, the default value is **off**. To enable SSL connections, you also need to configure parameters such as **ssl_cert_file**, **ssl_key_file**, and **ssl_ca_file** and the corresponding files. Incorrect configurations may cause startup failure of MogDB.
+
+**Default value**: **off**
+
+## require_ssl
+
+**Parameter description**: Specifies whether the server requires the SSL connection. This parameter is valid only when **[ssl](#ssl)** is set to **on**. Read **Using gsql to Connect to a Database** before setting this parameter.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the server requires the SSL connection.
+- **off** indicates that the server does not require the SSL connection.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> MogDB supports SSL when a client connects to the primary node of the database. It is recommended that the SSL connection be enabled only on the primary node of the database.
+
+**Default value**: **off**
+
+## ssl_ciphers
+
+**Parameter description**: Specifies the encryption algorithm list supported by the SSL.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string. Separate multiple encryption algorithms by semicolons (;). For details about supported encryption algorithms, see "Establishing Secure TCP/IP Connections in SSL Mode".
+
+**Default value**: **ALL**
+
+## ssl_renegotiation_limit
+
+**Parameter description**: Specifies the allowed traffic volume over an SSL-encrypted channel before the session key is renegotiated. The renegotiation mechanism reduces the probability that attackers use the password analysis method to crack the key based on a huge amount of data but causes big performance losses. The traffic indicates the sum of transmitted and received traffic. The SSL renegotiation mechanism has been disabled because of potential risks. This parameter is reserved for version compatibility and does not take effect.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 2147483647. The unit is KB. **0** indicates that the renegotiation mechanism is disabled.
+
+**Default value**: **0**
+
+## ssl_cert_file
+
+**Parameter description**: Specifies the name of the SSL server certificate file. The path depends on the data directory.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string
+
+**Default value**: **server.crt**
+
+## ssl_key_file
+
+**Parameter description**: Specifies the name of the SSL private key file. The path depends on the data directory.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string
+
+**Default value**: **server.key**
+
+## ssl_ca_file
+
+**Parameter description**: Specifies the name of the Certificate Authority (CA) file. The path depends on the data directory.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string
+
+**Default value**: **cacert.pem**
+
+## ssl_crl_file
+
+**Parameter description**: Specifies the name of the file that contains CRL information. A relative path must be used. The path depends on the data directory.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string. If the value is empty, no CA file containing CRL information is loaded and client certificate verification is not performed.
+
+**Default value**: empty
+
+## krb_server_keyfile
+
+**Parameter description**: Specifies the location of the main configuration file of the Kerberos service. For details, see **Configuring Client Access Authentication**.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string
+
+**Default value**: empty
+
+## krb_srvname
+
+**Parameter description**: Specifies the Kerberos service name. For details, see **Configuring Client Access Authentication**.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string
+
+**Default value**: **postgres**
+
+## krb_caseins_users
+
+**Parameter description**: Specifies whether the Kerberos username is case-sensitive.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the Kerberos username is case-insensitive.
+- **off** indicates that the Kerberos username is case-sensitive.
+
+**Default value**: **off**
+
+## modify_initial_password
+
+**Parameter description**: After MogDB is installed, there is only one initial user account (whose UID is 10) in the database. When a user logs in to the database using this initial account for the first time, this parameter determines whether the password of the initial account needs to be modified.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+If the initial user password is not specified during the installation process, the initial user password will be blank by default after installation. You need to set the initial user password through the gsql client before performing other operations. This parameter function no longer takes effect, and this parameter is reserved only for compatible upgrade scenarios.
+
+**Value range**: Boolean
+
+- **on** indicates that the password of the initial account needs to be modified upon the first login.
+- **off** indicates that the password of the initial account does not need to be modified.
+
+**Default value**: **off**
+
+## password_policy
+
+**Parameter description**: Specifies whether to check the password complexity when you run the **CREATE ROLE/USER** or **ALTER ROLE/USER** command to create or modify an account of MogDB. For details about the password complexity check policy, see **Setting Password Security Policies**.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> For security purposes, do not disable the password complexity policy.
+
+**Value range**: **0** and **1**
+
+- **0** indicates that no password complexity policy is enabled.
+- **1** indicates that the default password complexity policy is enabled.
+
+**Default value**: **1**
+
+## password_reuse_time
+
+**Parameter description**: Specifies whether to check the reuse interval of the new password when you run the **ALTER USER** or **ALTER ROLE** command to change a user password. For details about the password reuse policy, see **Setting Password Security Policies**.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> When you change the password, the system checks the values of **[password_reuse_time](#password_reuse_time)** and **[password_reuse_max](#password_reuse_max)**.
+>
+> - If the values of **[password_reuse_time](#password_reuse_time)** and **[password_reuse_max](#password_reuse_max)** are both positive numbers, an old password can be reused when it meets either of the reuse restrictions.
+> - If the value of **[password_reuse_time](#password_reuse_time)** is **0**, password reuse is restricted based on the number of reuse times, and not on the reuse interval.
+> - If the value of **[password_reuse_max](#password_reuse_max)** is **0**, password reuse is restricted based on the reuse interval, and not on the number of reuse times.
+> - If the values of both **[password_reuse_time](#password_reuse_time)** and **[password_reuse_max](#password_reuse_max)** are **0**, password reuse is not restricted.
+
+**Value range**: a floating point number ranging from 0 to 3650. The unit is day.
+
+- **0** indicates that the password reuse interval is not checked.
+- A positive number indicates that a new password cannot be chosen from passwords in history that are newer than the specified number of days.
+
+**Default value**: **60**
+
+## password_reuse_max
+
+**Parameter description**: Specifies whether to check the reuse times of the new password when you run the **ALTER USER** or **ALTER ROLE** command to change a user password. For details about the password reuse policy, see **Setting Password Security Policies**.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> When you change the password, the system checks the values of **[password_reuse_time](#password_reuse_time)** and **[password_reuse_max](#password_reuse_max)**.
+>
+> - If the values of **[password_reuse_time](#password_reuse_time)** and **[password_reuse_max](#password_reuse_max)** are both positive numbers, an old password can be reused when it meets either of the reuse restrictions.
+> - If the value of **[password_reuse_time](#password_reuse_time)** is **0**, password reuse is restricted based on the number of reuse times, and not on the reuse interval.
+> - If the value of **[password_reuse_max](#password_reuse_max)** is **0**, password reuse is restricted based on the reuse interval, and not on the number of reuse times.
+> - If the values of both **[password_reuse_time](#password_reuse_time)** and **[password_reuse_max](#password_reuse_max)** are **0**, password reuse is not restricted.
+
+**Value range**: an integer ranging from 0 to 1000
+
+- **0** indicates that the password reuse times are not checked.
+- A positive number indicates that the new password cannot be the one whose reuse times exceed the specified number.
+
+**Default value**: **0**
+
+## password_lock_time
+
+**Parameter description**: Specifies the duration before a locked account is automatically unlocked. For details about the policy, see **Setting Password Security Policies**.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> The locking and unlocking functions take effect only when the values of **password_lock_time** and **[failed_login_attempts](#failed_login_attempts)** are positive numbers.
+
+**Value range**: a floating point number ranging from 0 to 365. The unit is day.
+
+- **0** indicates that an account is not automatically locked if the password verification fails.
+- A positive number indicates the duration after which a locked account is automatically unlocked.
+
+**Default value**: **1d**
+
+## failed_login_attempts
+
+**Parameter description**: Specifies the maximum number of incorrect password attempts before an account is locked. The account will be automatically unlocked after the time specified by **password_lock_time**. Only the sysadmin user can access the account. The automatic account locking policy applies in scenarios such as login and password modification using the **ALTER USER** command. For details about the policy, see **Setting Password Security Policies**.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> The locking and unlocking functions take effect only when the values of **failed_login_attempts** and **[password_lock_time](#password_lock_time)** are positive numbers.
+
+**Value range**: an integer ranging from 0 to 1000
+
+- **0** indicates that the automatic locking function does not take effect.
+- A positive number indicates that an account is locked when the number of incorrect password attempts reaches the specified number.
+
+**Default value:** **10**
+
+## password_encryption_type
+
+**Parameter description**: Specifies the encryption type of a user password. Changing the value of this parameter does not change the password encryption type of existing users. The new encryption type is applied to passwords of new users or passwords modified after the parameter value is changed.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: **0**, **1**, **2**, and **3**
+
+- **0** indicates that passwords are encrypted with MD5.
+- **1** indicates that passwords are encrypted with SHA-256 and MD5.
+- **2** indicates that passwords are encrypted with SHA-256.
+- **3** indicates that the passwords are encrypted in sm3 mode.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> The MD5 encryption algorithm is not recommended because it has lower security and poses security risks.
+
+**Default value:** **2**
+
+## password_min_length
+
+**Parameter description**: Specifies the minimum password length.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer. A password can contain 6 to 999 characters.
+
+**Default value**: **8**
+
+## password_max_length
+
+**Parameter description**: Specifies the maximum password length.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer. A password can contain 6 to 999 characters.
+
+**Default value**: **32**
+
+## password_min_uppercase
+
+**Parameter description**: Specifies the minimum number of uppercase letters that an account password must contain.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 999
+
+- **0** means no limit.
+- A positive integer indicates the minimum number of uppercase letters required in a password when you create an account.
+
+**Default value**: **0**
+
+## password_min_lowercase
+
+**Parameter description**: Specifies the minimum number of lowercase letters that an account password must contain.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 999
+
+- **0** means no limit.
+- A positive integer indicates the minimum number of lowercase letters required in a password when you create an account.
+
+**Default value**: **0**
+
+## password_min_digital
+
+**Parameter description**: Specifies the minimum number of digits that an account password must contain.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 999
+
+- **0** means no limit.
+- A positive integer indicates the minimum number of digits required in a password when you create an account.
+
+**Default value**: **0**
+
+## password_min_special
+
+**Parameter description**: Specifies the minimum number of special characters that an account password must contain.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 999
+
+- **0** means no limit.
+- A positive integer indicates the minimum number of special characters required in a password when you create an account.
+
+**Default value**: **0**
+
+## password_effect_time
+
+**Parameter description**: Specifies the validity period of an account password.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a floating point number ranging from 0 to 999. The unit is day.
+
+- **0** indicates that the validity period restriction is disabled.
+- A floating point number from 1 to 999 indicates the number of days for which an account password is valid. When the password is about to expire or has expired, the system prompts the user to change the password.
+
+**Default value**: **90**
+
+## password_notify_time
+
+**Parameter description**: Specifies how many days in advance a user is notified before a password expires.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 999. The unit is day.
+
+- **0** indicates that the reminder is disabled.
+- A positive integer indicates the number of days prior to password expiration that a user will receive a reminder.
+
+**Default value**: **7**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/3-connection-and-authentication/3-communication-library-parameters.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/3-connection-and-authentication/3-communication-library-parameters.md
new file mode 100644
index 0000000000000000000000000000000000000000..1794016a6ca2b49eeea599dea5ee7bf75710b106
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/3-connection-and-authentication/3-communication-library-parameters.md
@@ -0,0 +1,86 @@
+---
+title: Communication Library Parameters
+summary: Communication Library Parameters
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Communication Library Parameters
+
+This section describes parameter settings and value ranges for communication libraries.
+
+## tcp_keepalives_idle
+
+**Parameter description**: Specifies the interval for transmitting keepalive signals on an OS that supports the **TCP_KEEPIDLE** socket option. If no keepalive signal is transmitted, the connection is in idle mode.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in **Table GUC Parameters**.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - If the OS does not support **TCP_KEEPIDLE**, set this parameter to **0**.
+> - The parameter is ignored on an OS where connections are established using the Unix domain socket.
+> - 0 selects the system default.
+> - This parameter is not shared between different sessions, which means that this parameter may have different values in different sessions.
+> - When showing this parameter, it is the parameter value in the current session connection, not the value of the guc copy.
+
+**Value range:** 0 to 3600. The unit is s.
+
+**Default value**: **0**
+
+## tcp_keepalives_interval
+
+**Parameter description:** Specifies the response time before retransmission on an OS that supports the **TCP_KEEPINTVL** socket option.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in **Table GUC Parameters**.
+
+**Value range**: 0 to 180. The unit is s.
+
+**Default value**: **0**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - If the OS does not support **TCP_KEEPINTVL**, set this parameter to **0**.
+> - The parameter is ignored on an OS where connections are established using the Unix domain socket.
+> - 0 selects the system default.
+> - This parameter is not shared between different sessions, which means that this parameter may have different values in different sessions.
+> - When showing this parameter, it is the parameter value in the current session connection, not the value of the guc copy.
+
+## tcp_keepalives_count
+
+**Parameter description**: Specifies the number of keepalive signals that can be waited before the MogDB server is disconnected from the client on an OS that supports the **TCP_KEEPCNT** socket option.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in **Table GUC Parameters**.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - If the OS does not support **TCP_KEEPCNT**, set this parameter to **0**.
+> - The parameter is ignored on an OS where connections are established using the Unix domain socket.
+> - 0 selects the system default.
+> - This parameter is not shared between different sessions, which means that this parameter may have different values in different sessions.
+> - When showing this parameter, it is the parameter value in the current session connection, not the value of the guc copy.
+
+**Value range**: 0 to 100. **0** indicates that the connection is immediately broken if MogDB does not receive a keepalived signal from the client.
+
+**Default value:** **0**
+
+## comm_proxy_attr
+
+**Parameter description**: Specifies the parameters related to the communication proxy library.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - This parameter applies only to the centralized ARM standalone system running EulerOS 2.9.
+> - This function takes effect when the thread pool is enabled, that is, **enable_thread_pool** is set to **on**.
+> - When setting this parameter, you need to set the GUC parameter **local_bind_address** to the IP address of the NIC of the **libos_kni**.
+> - **Parameter template**: comm_proxy_attr = '{enable_libnet:true, enable_dfx:false, numa_num:4, numa_bind:[[30,31],[62,63],[94,95],[126,127]]}'
+> - Parameters that need to be configured include:
+>   - **enable_libnet**: whether to enable the user-mode protocol. The options are as follows: **true** and **false**.
+>   - **enable_dfx**: whether to enable the communication proxy library view. The options are as follows: **true** and **false**.
+>   - **numa_num**: number of NUMA nodes in the system. 2P and 4P servers are supported. The value can be: **4** or **8**.
+>   - **numa_bind**: core binding parameter of the agent thread. Each numa has two CPUs. There are a total of **numa_num** groups. The value range is as follows: [0, Number of CPUs - 1].
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in **Table GUC Parameters**.
+
+**Value range**: a string, consisting of one or more characters
+
+**Default value**: **none**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/30-appendix.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/30-appendix.md
new file mode 100644
index 0000000000000000000000000000000000000000..4b3bcc59016be9299c6693e698d7bf48c72b327e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/30-appendix.md
@@ -0,0 +1,28 @@
+---
+title: Appendices
+summary: Appendices
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Appendices
+
+## **Table 1** GUC parameters<a id="GUC parameters"> </a>
+
+| Parameter type. | Remarks                                                      | How to Set                                                   |
+| --------------- | ------------------------------------------------------------ | ------------------------------------------------------------ |
+| INTERNAL        | Fixed parameter. It is set during database creation and cannot be modified. Users can only view the parameter by running the **SHOW** command or in the **pg_settings** view. | None                                                         |
+| POSTMASTER      | Database server parameter. It can be set when the database is started or in the configuration file. | Method 1 in Table 2 [Methods for setting GUC parameters](30-appendix).  |
+| SIGHUP          | Global database parameter. It can be set when the database is started or be modified later. | Method 1 or 2 in Table 2 [Methods for setting GUC parameters](30-appendix). |
+| BACKEND         | Session connection parameter. It is specified during session connection creation and cannot be modified after that. The parameter setting becomes invalid when the session is disconnected. This is an internal parameter and not recommended for users to set it. | Method 1 or 2 in Table 2 [Methods for setting GUC parameters](30-appendix).<br />NOTE: The parameter setting takes effect when the next session is created. |
+| SUSET           | Database administrator parameter. It can be set by common users when or after the database is started. It can also be set by database administrators using SQL statements. | Method 1 or 2 by a common user, or method 3 by a database administrator in Table 2 [Methods for setting GUC parameters](30-appendix). |
+| USERSET         | Common user parameter. It can be set by any user at any time. | Method 1, 2, or 3 in Table 2 [Methods for setting GUC parameters](30-appendix). |
+
+## **Table 2** Methods for setting GUC parameters <a id="Methods for setting GUC parameters"> </a>
+
+| No.       | Description                                                  |
+| --------- | ------------------------------------------------------------ |
+| Method 1  | 1. Run the following command to set a parameter:<br />`gs_guc set -D datadir -c "paraname=value"`<br />NOTE:<br />If the parameter is a string variable, use **-c** *parameter***="'**value**'"** or **-c "**parameter = 'value'".<br />Run the following command to set a parameter for database nodes at the same time:<br />`gs_guc set -Nall -I all -c "paraname=value"`<br />2. Restart the database to make the setting take effect.<br />NOTE:<br />Restarting MogDB results in operation interruption. Properly plan the restart to avoid affecting users.<br />`gs_om -t stop && gs_om -t start` |
+| Method 2  | `gs_guc reload -D datadir -c "paraname=value"`<br />NOTE:<br />Run the following command to set a parameter for database nodes at the same time:<br />`gs_guc reload -N all -I all -c "paraname=value"` |
+| Method 3: | Set parameters at database, user, or session levels.<br />- Set a database-level parameter.<br />`mogdb=# ALTER DATABASE dbname SET paraname TO value;`<br />The setting takes effect in the next session.<br />- Set a user-level parameter.<br />`mogdb=# ALTER USER username SET paraname TO value;`<br />The setting takes effect in the next session.<br />- Set a session-level parameter.<br />`mogdb=# SET paraname TO value;`<br />Parameter value in the current session is changed. After you exit the session, the setting becomes invalid. |
+| Method 4  | Modify database parameters using **ALTER SYSTEM SET**.<br />- Set a POSTMASTER-level parameter<br />`mogdb=# ALTER SYSTEM SET paraname TO value;`<br />Restart the system for the setting to take effect.<br />- Set a SIGHUP-level parameter.<br />`mogdb=# ALTER SYSTEM SET paraname TO value;`<br />The setting takes effect immediately. (Actually, there is a slight delay to wait for the thread reloading the parameter.)<br />- Set a BACKEND-level parameter.<br />`mogdb=# ALTER SYSTEM SET paraname TO value;`<br />The setting takes effect in the next session. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/31-scheduled-task.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/31-scheduled-task.md
new file mode 100644
index 0000000000000000000000000000000000000000..d1b8a5117f113ea81b39f46b3c7f4216bc50c257
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/31-scheduled-task.md
@@ -0,0 +1,42 @@
+---
+title: Scheduled Task
+summary: Scheduled Task
+author: Zhang Cuiping
+date: 2021-06-15
+---
+
+# Scheduled Task
+
+## job_queue_processes
+
+**Parameter description:** Specifies the number of jobs that can be concurrently executed. This parameter is a POSTMASTER parameter. You can set it using **gs_guc**, and you need to restart **gaussdb** to make the setting take effect.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: 0 to 1000
+
+Function:
+
+- Setting **job_queue_processes** to **0** indicates that the scheduled job function is disabled and that no job will be executed. (Enabling scheduled jobs may affect the system performance. At sites where this function is not required, you are advised to disable it.)
+- Setting **job_queue_processes** to a value that is greater than **0** indicates that the scheduled job function is enabled and this value is the maximum number of jobs that can be concurrently processed.
+
+After the scheduled job function is enabled, the job_scheduler thread polls the **pg_job** system catalog at a scheduled interval. The scheduled job check is performed every second by default.
+
+Too many concurrent jobs consume many system resources, so you need to set the number of concurrent jobs to be processed. If the current number of concurrent jobs reaches the value of **job_queue_processes** and some of them expire, these jobs will be postponed to the next polling period. Therefore, you are advised to set the polling interval (the **Interval** parameter of the **submit** interface) based on the execution duration of each job to avoid the problem that jobs in the next polling period cannot be properly processed because of overlong job execution time.
+
+Note: If the number of concurrent jobs is large and the value is too small, these jobs will wait in queues. However, a large parameter value leads to large resource consumption. You are advised to set this parameter to **100** and change it based on the system resource condition.
+
+**Default value**: **10**
+
+## enable_prevent_job_task_startup
+
+**Parameter description**: Specifies whether to start the job thread.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the job thread is not started.
+- **off** indicates that the job thread is started.
+
+**Default value**: **off**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/32-thread-pool.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/32-thread-pool.md
new file mode 100644
index 0000000000000000000000000000000000000000..5b8ad3518463239cd5d325634435e06ce3298786
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/32-thread-pool.md
@@ -0,0 +1,37 @@
+---
+title: Thread Pool
+summary: Thread Pool
+author: Zhang Cuiping
+date: 2021-06-15
+---
+
+# Thread Pool
+
+## enable_thread_pool
+
+**Parameter description**: Specifies whether to enable the thread pool function. This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the thread pool function is enabled.
+- **off** indicates that the thread pool function is disabled.
+
+**Default value**: off
+
+## thread_pool_attr
+
+**Parameter description**: Specifies the detailed attributes of the thread pool function. This parameter is valid only when **enable_thread_pool** is set to **on**. This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string, consisting of one or more characters.
+
+This parameter consists of three parts: thread_num, group_num, and cpubind_info. The meanings of the three parts are as follows:
+
+- **thread_num** indicates the total number of threads in the thread pool. The value ranges from 0 to 4096. The value **0** indicates that the database automatically configures the number of threads in the thread pool based on the number of CPU cores. If the value is greater than **0**, the number of threads in the thread pool is the same as the value of **thread_num**.
+- **group_num** indicates the number of thread groups in the thread pool. The value ranges from 0 to 64. The value **0** indicates that the database automatically configures the number of thread groups in the thread pool based on the number of NUMA groups. If the value is greater than **0**, the number of thread groups in the thread pool is the same as the value of **group_num**.
+- **cpubind_info** indicates whether the thread pool is bound to a core. The available configuration modes are as follows:
+  1. '(nobind)': The thread is not bound to a core.
+  2. '(allbind)': Use all CPU cores that can be queried in the current system to bind threads.
+  3. '(nodebind: 1, 2)': Use the CPU cores in NUMA groups 1 and 2 to bind threads.
+  4. '(cpubind: 0-30)': Use the CPU cores 0 to 30 to bind threads. This parameter is case-insensitive.
+
+**Default value**: **'16, 2, (nobind)'**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/33-user-defined-functions.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/33-user-defined-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..7f80b87b6940c5a167c2d8d4b1709b903662584f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/33-user-defined-functions.md
@@ -0,0 +1,54 @@
+---
+title: User-defined Functions
+summary: User-defined Functions
+author: Zhang Cuiping
+date: 2021-11-08
+---
+
+# User-defined Functions
+
+## udf_memory_limit
+
+**Parameter description**: Controls the maximum physical memory that can be used when each database node executes UDFs. This parameter does not take effect in the current version. Use **FencedUDFMemoryLimit** and **UDFWorkerMemHardLimit** to control virtual memory used by fenced udf worker.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer. The value range is from 200 x 1024 to *max_process_memory* and the unit is KB.
+
+**Default value**: **200 MB**
+
+## FencedUDFMemoryLimit
+
+**Parameter description**: Specifies the virtual memory used by each fenced udf worker process.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 KB to 2147483647 KB. The unit can also be MB or GB. **0** indicates that the memory is not limited.
+
+**Default value**: **0**
+
+## UDFWorkerMemHardLimit
+
+**Parameter description**: Specifies the maximum value of **fencedUDFMemoryLimit**.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+Value range: an integer ranging from 0KB to 2147483647KB. The unit can also be MB or GB.
+
+**Default value**: **1GB**
+
+## pljava_vmoptions
+
+**Parameter description**: Specifies the startup parameters for JVMs used by the PL/Java function. Only the sysadmin user can access this parameter.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string, supporting:
+
+- JDK8 JVM startup parameters. For details, see JDK [official](https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html)descriptions.
+- JDK8 JVM system attributes (starting with **-D**, for example, **-Djava.ext.dirs**). For details, see JDK [official](https://docs.oracle.com/javase/tutorial/deployment/doingMoreWithRIA/properties.html)descriptions.
+- User-defined parameters (starting with **-D**, for example, **-Duser.defined.option**).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** If **pljava_vmoptions** is set to a value beyond the value range, an error will be reported when PL/Java functions are used.
+
+**Default value:** empty
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/34-backup-and-restoration.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/34-backup-and-restoration.md
new file mode 100644
index 0000000000000000000000000000000000000000..8b43d14ce5cfb3ef8aeda7a203aad84cf0913c0f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/34-backup-and-restoration.md
@@ -0,0 +1,46 @@
+---
+title: Backup and Restoration
+summary: Backup and Restoration
+author: Zhang Cuiping
+date: 2021-11-08
+---
+
+# Backup and Restoration
+
+## operation_mode
+
+**Parameter description**: Specifies whether the system enters the backup and restoration mode.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the system is in the backup and restoration mode.
+- **off** indicates that the system is not in the backup and restoration mode.
+
+**Default value**: **off**
+
+## enable_cbm_tracking
+
+**Parameter description:** This parameter must be enabled when Roach is used to perform full and incremental backups. If this parameter is disabled, the backup will fail.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on**: The cbm tracking is enabled.
+- **off**: The cbm tracking is disabled.
+
+**Default value**: **off**
+
+## hadr_max_size_for_xlog_receiver
+
+**Parameter description**: Specifies the maximum difference between the OBS logs obtained by instances in the DR database instance and the local playback logs. If the difference is greater than the value of this parameter, the instances stop obtaining OBS logs.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Handling suggestion**: The value of this parameter is related to the local disk size. You are advised to set this parameter to 50% of the local disk size.
+
+**Value range**: an integer ranging from 0 to 2147483647
+
+**Default value**: **256 GB**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/35-undo.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/35-undo.md
new file mode 100644
index 0000000000000000000000000000000000000000..fe7f6380e03e9f70a738084a6e5aff6fa579c473
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/35-undo.md
@@ -0,0 +1,43 @@
+---
+title: Undo
+summary: Undo
+author: Zhang Cuiping
+date: 2021-11-08
+---
+
+# Undo
+
+## undo_space_limit_size
+
+**Parameter description**: Specifies the undo forcible reclamation threshold. If 80% of the threshold is reached, forcible reclamation is triggered.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 800 MB to 32 TB
+
+**Default value**: **32 GB**
+
+## undo_limit_size_per_transaction
+
+**Parameter description**: Specifies the undo space threshold of a single transaction. If the threshold is reached, the transaction is rolled back due to an error.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 100 MB to 32 TB
+
+**Default value**: **32 GB**
+
+## undo_zone_count
+
+**Parameter description**: Specifies the number of undo zones that can be allocated in the memory. If the number reaches the threshold or the value set this time is less than the value set last time, an error is reported. After a proper value is set based on the rule, the number of undo zones becomes normal. If this parameter is set to **0**, the undo function is disabled and Ustore tables cannot be created.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 1048576
+
+Value constraint:
+
+1. The value set this time must be greater than or equal to the value set last time. If the value is incorrect, the database cannot be restored. You need to reset the value and restart the database to restore the database.
+2. The value of **undo_zone_count** needs to be adjusted based on the value of **max_connections**. After changing the value of **max_connections**, you need to change the value of **undo_zone_count**, which must be four times that of **max_connections**.
+
+**Default value**: **0**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/36-DCF-parameters-settings.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/36-DCF-parameters-settings.md
new file mode 100644
index 0000000000000000000000000000000000000000..7c688b82d2fa9ced7c051fad023e63cff9296f39
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/36-DCF-parameters-settings.md
@@ -0,0 +1,344 @@
+---
+title: DCF Parameters Settings
+summary: DCF Parameters Settings
+author: Zhang Cuiping
+date: 2021-11-08
+---
+
+# DCF Parameters Settings
+
+## enable_dcf
+
+**Parameter description**: Specifies whether to enable the DCF mode. This parameter cannot be modified.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean. The value can be **on** or **off**. The value **on** indicates that the current installation mode is DCF, and the value **off** indicates that the current installation mode is not DCF.
+
+**Default value**: **off**
+
+## dcf_ssl
+
+**Parameter description**: Specifies whether to enable SSL. This parameter takes effect upon the system restart.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean. The value can be **on** or **off**. The value **on** indicates that SSL is used, and the value **off** indicates that SSL is not used.
+
+**Default value**: **on**
+
+## dcf_config
+
+**Parameter description**: Specifies the customized configuration information during installation. This parameter cannot be modified.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Default value**: a string, which is specified by users during installation
+
+## dcf_data_path
+
+**Parameter description**: Specifies the DCF data path. This parameter cannot be modified.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Default value**: a string, which is the **dcf_data** directory under the data directory of the DN
+
+## dcf_log_path
+
+**Parameter description**: Specifies the DCF log path. This parameter cannot be modified.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Default value**: a string, which is the **dcf_log** directory under the data directory of the DN.
+
+## dcf_node_id
+
+**Parameter description**: Specifies the ID of the DN where the DCF is located. This parameter is defined by users during installation and cannot be modified.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Default value**: an integer, which is specified by users during installation
+
+## dcf_max_workers
+
+**Parameter description**: Specifies the number of DCF callback function threads.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 10 to 262143
+
+**Default value**: **10**
+
+## dcf_truncate_threshold
+
+**Parameter description**: Specifies the threshold for a DN to truncate DCF logs.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1 to 2147483647
+
+**Default value**: **100000**
+
+## dcf_election_timeout
+
+**Parameter description**: Specifies the timeout interval for selecting the DCF leader and follower. The election timeout interval depends on the status of the network between DNs. If the timeout interval is short and the network quality is poor, timeout occurs. After the network recovers, the election becomes normal. You are advised to set a proper timeout interval based on the current network status.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1 to 600, in seconds
+
+**Default value**: **3**
+
+## dcf_run_mode
+
+**Parameter description**: Specifies the DCF election mode. The value **0** indicates that the automatic DCF election mode is enabled, and the value **2** indicates that the DCF election mode is disabled.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Enumerated type. The value can be **0** or **2**.
+
+**Default value**: **0**
+
+## dcf_log_level
+
+**Parameter description**: Specifies the DCF log level.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string
+
+- Disable the log function: **NONE**, indicating that the log function is disabled and cannot be used for the following log levels:
+
+- Enable the log function: **RUN_ERR|RUN_WAR|RUN_INF|DEBUG_ERR|DEBUG_WAR|DEBUG_INF|TRACE|PROFILE|OPER**
+
+  You can select a string from the preceding strings and use vertical bars (|) to combine the strings. The log level cannot be left blank.
+
+**Default value**: **RUN_ERR|RUN_WAR|DEBUG_ERR|OPER|RUN_INF|PROFILE**
+
+## dcf_log_backup_file_count
+
+**Parameter description**: Specifies the number of DCF run log backups.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range:** an integer ranging from 1 to 100
+
+**Default value**: **10**
+
+## dcf_max_log_file_size
+
+**Parameter description**: Specifies the maximum size of a DCF run log file.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1 to 1000, in MB
+
+**Default value**: **10**
+
+## dcf_socket_timeout
+
+**Parameter description**: Specifies the timeout interval for the DCF communication module to connect to the socket. This parameter takes effect upon the system restart. In an environment where the network quality is poor, if the timeout interval is set to a small value, a connection may fail to be set up. In this case, you need to increase the value.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 10 to 600000, in ms
+
+**Default value**: **5000**
+
+## dcf_connect_timeout
+
+**Parameter description**: Specifies the timeout interval for the DCF communication module to set up a connection. This parameter takes effect upon the system restart. In an environment where the network quality is poor, if the timeout interval is set to a small value, the connection may fail to be set up. In this case, you need to increase the value.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 10 to 600000, in ms
+
+**Default value:** **60000**
+
+## dcf_mec_fragment_size
+
+**Parameter description**: Specifies the fragment size of the DCF communication module. This parameter takes effect upon the system restart.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 32 to 10240, in KB
+
+**Default value**: **64**
+
+## dcf_stg_pool_max_size
+
+**Parameter description**: Specifies the maximum size of the memory pool of the DCF storage module. This parameter takes effect upon the system restart.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 32 to 2147483647, in MB
+
+**Default value**: **2048**
+
+## dcf_stg_pool_init_size
+
+**Parameter description**: Specifies the minimum size of the memory pool of the DCF storage module. This parameter takes effect upon the system restart.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 32 to 2147483647, in MB
+
+**Default value**: **32**
+
+## dcf_mec_pool_max_size
+
+**Parameter description**: Specifies the maximum size of the memory pool of the DCF communication module. This parameter takes effect upon the system restart.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 32 to 2147483647, in MB
+
+**Default value**: **200**
+
+## dcf_flow_control_disk_rawait_threshold
+
+**Parameter description**: Specifies the disk waiting threshold for DCF flow control.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 2147483647, in μs
+
+**Default value**: **100000**
+
+## dcf_flow_control_net_queue_message_num_threshold
+
+**Parameter description**: Specifies the threshold for the number of messages in a network queue for DCF flow control.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 2147483647
+
+**Default value:** **1024**
+
+## dcf_flow_control_cpu_threshold
+
+**Parameter description**: Specifies the threshold for DCF CPU flow control.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 2147483647, in percentage (%)
+
+**Default value**: **100**
+
+## dcf_mec_batch_size
+
+**Parameter description**: Specifies the number of batch messages for DCF communication. When the value is **0**, the DCF automatically adjusts the value based on the network and the amount of data to be written. This parameter takes effect upon the system restart.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1 to 1024
+
+**Default value**: **0**
+
+## dcf_mem_pool_max_size
+
+**Parameter description**: Specifies the maximum DCF memory. This parameter takes effect upon the system restart.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 32 to 2147483647, in MB
+
+**Default value**: **2048**
+
+## dcf_mem_pool_init_size
+
+**Parameter description**: Specifies the initial size of the DCF memory. This parameter takes effect upon the system restart.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 32 to 2147483647, in MB
+
+**Default value**: **32**
+
+## dcf_compress_algorithm
+
+**Parameter description**: Specifies the compression algorithm for DCF run log transmission. This parameter takes effect upon the system restart.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer
+
+- **0** indicates no compression.
+- **1** indicates the ZSTD compression algorithm.
+- **2** indicates the LZ4 compression algorithm.
+
+**Default value**: **0**
+
+## dcf_compress_level
+
+**Parameter description**: Specifies the compression level for DCF log transmission. This parameter takes effect upon the system restart. Before this parameter takes effect, a valid compression algorithm must be configured, that is, the **dcf_compress_algorithm** parameter is set.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer
+
+- If no compression algorithm is used, the value does not take effect.
+- If the ZSTD compression algorithm is used, the value ranges from 1 to 22.
+- If the LZ4 compression algorithm is used, the value ranges from 1 to 9.
+
+**Default value**: **1**
+
+## dcf_mec_channel_num
+
+**Parameter description**: Specifies the number of DCF communication channels. This parameter takes effect upon the system restart.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1 to 64
+
+**Default value**: **1**
+
+## dcf_rep_append_thread_num
+
+**Parameter description**: Specifies the number of DCF log replication threads. This parameter takes effect upon the system restart.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range:** an integer ranging from 1 to 1000
+
+**Default value**: **2**
+
+## dcf_mec_agent_thread_num
+
+**Parameter description**: Specifies the number of DCF communication working threads. This parameter takes effect upon the system restart. It is recommended that the value of **dcf_mec_agent_thread_num** be greater than or equal to 2 x Number of nodes x Value of **dcf_mec_channel_num**.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range:** an integer ranging from 1 to 1000
+
+**Default value**: **10**
+
+## dcf_mec_reactor_thread_num
+
+**Parameter description**: Specifies the number of reactor threads used by the DCF. This parameter takes effect upon the system restart. It is recommended that the ratio of the value of **dcf_mec_reactor_thread_num** to the value of **dcf_mec_agent_thread_num** be 1:40.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range:** an integer ranging from 1 to 100
+
+**Default value**: **1**
+
+## dcf_log_file_permission
+
+**Parameter description**: Specifies the attribute of a DCF run log file. This parameter takes effect upon the system restart. To allow other users in the same group to access logs, ensure that all parent directories can be accessed by other users in the same group.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: enumerated type. The value can be **600** or **640**.
+
+**Default value**: **600**
+
+## dcf_log_path_permission
+
+**Parameter description**: Specifies the attribute of the DCF run log directory. This parameter takes effect upon the system restart and cannot be modified.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: enumerated type. The value can be **700** or **750**.
+
+**Default value**: **700**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/37-flashback.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/37-flashback.md
new file mode 100644
index 0000000000000000000000000000000000000000..5b6ad68b8e05b941872c46491730548e7754e78a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/37-flashback.md
@@ -0,0 +1,67 @@
+---
+title: Flashback
+summary: Flashback
+author: Zhang Cuiping
+date: 2021-11-08
+---
+
+# Flashback
+
+This section describes parameters related to the flashback function.
+
+## enable_recyclebin
+
+**Parameter description**: Specifies whether the recycle bin is enabled or disabled in real time.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+**Default value**: **off**
+
+## timecapsule_mode
+
+**Parameter description**: Specifies whether to enable the flashback function.
+
+This parameter is a **SIGHUP** parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: enumerated values
+
+- **none** indicates that the flashback function is disabled.
+- **heap** indicates that only the flashback function of the Heap engine is enabled.
+- **ustore** indicates that only the flashback function of the UStore engine is enabled.
+- **all** indicates that the flashback function is enabled for both the Heap and UStore engines.
+
+**Default value**: **none**
+
+## recyclebin_retention_time
+
+**Parameter description**: Specifies the retention period of objects in the recycle bin. The objects will be automatically deleted after the retention period expires.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1 to 2147483647. The unit is s.
+
+Default value: **15 min** (900s)
+
+## version_retention_age
+
+**Parameter description**: Specifies the number of transactions retained in the old version. If the number of transactions exceeds the value of this parameter, the old version will be recycled and cleared.
+
+This parameter is a **SIGHUP** parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 576460752303423487. **0** means no delay.
+
+**Default value**: **0**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **CAUTION:** System catalogs use the Heap engine. To prevent unnecessary system catalog bloating (for example, only the Uheap flashback function is used in services), you need to set **version_retention_age** and **vacuum_defer_cleanup_age** to the same value so that the old version can be retained.
+
+## vacuum_defer_cleanup_age
+
+**Parameter description**: Specifies the number of transactions by which **VACUUM** will defer the cleanup of invalid row-store table records, so that **VACUUM** and **VACUUM FULL** do not clean up deleted tuples immediately. You can also set this parameter to configure the retention period of the flashback function in the old version.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 1000000. **0** means no delay. The value range needs to be extended to 100 million.
+
+**Default value**: **0**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/38-rollback-parameters.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/38-rollback-parameters.md
new file mode 100644
index 0000000000000000000000000000000000000000..7cb5098225ec4f0277b43ac1e69037b5b1317349
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/38-rollback-parameters.md
@@ -0,0 +1,18 @@
+---
+title: Rollback Parameters
+summary: Rollback Parameters
+author: Zhang Cuiping
+date: 2021-11-08
+---
+
+# Rollback Parameters
+
+## max_undo_workers
+
+**Parameter description**: Specifies the number of undo worker threads invoked during asynchronous rollback. The parameter setting takes effect after the system is restarted.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range:** an integer ranging from 1 to 100
+
+**Default value**: **5**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/39-reserved-parameters.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/39-reserved-parameters.md
new file mode 100644
index 0000000000000000000000000000000000000000..52a134bc25a40b4914966bae3ec541ed57898ffe
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/39-reserved-parameters.md
@@ -0,0 +1,26 @@
+---
+title: Reserved Parameters
+summary: Reserved Parameters
+author: Zhang Cuiping
+date: 2021-11-08
+---
+
+# Reserved Parameters
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The following parameters are reserved and do not take effect in this version.
+
+acce_min_datasize_per_thread
+
+cstore_insert_mode
+
+enable_constraint_optimization
+
+enable_hadoop_env
+
+enable_hdfs_predicate_pushdown
+
+enable_orc_cache
+
+schedule_splits_threshold
+
+backend_version
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/1-memory.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/1-memory.md
new file mode 100644
index 0000000000000000000000000000000000000000..02960a29d9896cdfc4ea90a35db6f00fcb7a32aa
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/1-memory.md
@@ -0,0 +1,326 @@
+---
+title: Memory
+summary: Memory
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Memory
+
+This section describes memory parameters.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> These parameters take effect only after the database restarts.
+
+## memorypool_enable
+
+**Parameter description**: Specifies whether to enable a memory pool.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the memory pool is enabled.
+- **off** indicates that the memory pool is disabled.
+
+**Default value**: **off**
+
+## memorypool_size
+
+**Parameter description**: Specifies the memory pool size.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 128 x 1024 to *INT_MAX*/2. The unit is KB.
+
+**Default value**: **512MB**
+
+## enable_memory_limit
+
+**Parameter description**: Specifies whether to enable the logical memory management module.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the logical memory management module is enabled.
+- **off** indicates that the logical memory management module is disabled.
+
+**Default value**:  **on**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **CAUTION:**
+>
+> - If the value of  **max_process_memory**  minus  **shared_buffer**  minus  **cstore_buffers**  minus metadata size is less than 2 GB, MogDB forcibly sets  **enable_memory_limit** to **off**. Metadata is the memory used in MogDB and is related to some concurrent parameters, such as max_connections, thread_pool_attr and max_prepared_transactions.
+>
+> - If this parameter is set to  **off**, the memory used by the database is not limited. When a large number of concurrent or complex queries are performed, too much memory is used, which may cause OS OOM problems.
+
+## max_process_memory
+
+**Parameter description**: Specifies the maximum physical memory of a database node.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 2 x 1024 x 1024 to *INT_MAX*. The unit is KB.
+
+**Default value**:12GB
+
+**Setting suggestions**:
+
+The value on the database node is determined based on the physical memory of the system and the number of master database nodes deployed on a single node. The recommended calculation formula is as follows: (Physical memory - vm.min_free_kbytes) \ x 0.7 /(1 + Number of primary nodes) This parameter is used to prevent node OOM caused by memory usage increase, ensuring system reliability. **vm.min_free_kbytes** indicates the OS memory reserved for the kernel to receive and send data. Its value is at least 5% of the total memory. That is, max_process_memory = Physical memory x 0.665 / (1 + Number of primary nodes)
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **CAUTION:** If this parameter is set to a value greater than the physical memory of the server, the OS OOM problem may occur.
+
+## enable_memory_context_control
+
+**Parameter description**: Specifies whether to enable the function of checking whether the amount of memory contexts exceeds the specified limit. This parameter applies only to the DEBUG version.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the function of checking the amount of memory contexts is enabled.
+- **off** indicates that the function of checking the amount of memory contexts is disabled.
+
+**Default value**: **off**
+
+## uncontrolled_memory_context
+
+**Parameter description**: Specifies which memory texts will not be checked when the **enable_memory_context_control** parameter is set to **on**. This parameter applies only to the DEBUG version.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+During the query, the title meaning string "MemoryContext white list:" is added to the beginning of the parameter value.
+
+**Value range**: a string
+
+**Default value**: empty
+
+## shared_buffers
+
+**Parameter description**: Specifies the size of shared memory used by MogDB. Increasing the value of this parameter causes MogDB to request more System V shared memory than the default configuration allows.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 16 to 1073741823. The unit is 8KB.
+
+The value of **shared_buffers** must be an integer multiple of **BLCKSZ**. Currently, **BLCKSZ** is set to **8 KB**. That is, the value of **shared_buffers** must be an integer multiple of 8 KB. The minimum value changes according to **BLCKSZ**.
+
+**Default value**: **8 MB**
+
+**Setting suggestions**:
+
+Set **shared_buffers** to a value less than 40% of the memory. Set it to a large value for row-store tables and a small value for column-store tables. For column-store tables: **shared_buffers** = (Memory of a single server/Number of database nodes on the server) x 0.4 x 0.25
+
+If **shared_buffers** is set to a larger value, increase the value of **checkpoint_segments** because a longer period of time is required to write a large amount of new or changed data.
+
+## segment_buffers
+
+**Parameter description**: Specifies the memory size of the metadata page of the MogDB segment buffer.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 16 to 1073741823. The unit is 8KB.
+
+The value of  **shared_buffers**  must be an integer multiple of  **BLCKSZ**. Currently,  **BLCKSZ**  is set to  **8 KB**. That is, the value of  **shared_buffers**  must be an integer multiple of 8 KB. The minimum value changes according to  **BLCKSZ**.
+
+**Default value**: **8MB**
+
+**Setting suggestions**:
+
+**segment_buffers** is used to cache segment headers, which is key metadata information. To improve performance, it is recommended that the segment headers of common tables are cached to buffers and are not swapped. You are advised to set this parameter in terms of the number of tables (including index and toast tables) x number of partitions x 3 + 128. Generally, a table includes 3 metadata segments, so multiplying 3 is needed. +128 is needed because segment-based tablespace management requires a certain number of buffers.
+
+## bulk_write_ring_size
+
+**Parameter description**: Specifies the size of a ring buffer used for parallel data import.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 16384 to 2147483647. The unit is KB.
+
+**Default value**: **2GB**
+
+**Setting suggestions**: Increase the value of this parameter on database nodes if a huge amount of data will be imported.
+
+## standby_shared_buffers_fraction
+
+**Parameter description**: Specifies the **shared_buffers** proportion used on the server where a standby instance is deployed.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a double-precision floating-point number ranging from 0.1 to 1.0
+
+**Default value:** **0.3**
+
+## temp_buffers
+
+**Parameter description**: Specifies the maximum size of local temporary buffers used by a database session.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+This parameter can be modified only before the first use of temporary tables within each session. Subsequent attempts to change the value of this parameter will not take effect on that session.
+
+A session allocates temporary buffers based on the value of **temp_buffers**. If a large value is set in a session that does not require many temporary buffers, only the overhead of one buffer descriptor is added. If a buffer is used, additional 8192 bytes will be consumed for it.
+
+**Value range**: an integer ranging from 100 to 1073741823. The unit is 8 KB.
+
+**Default value**: **1MB**
+
+## max_prepared_transactions
+
+**Parameter description**: Specifies the maximum number of transactions that can stay in the **prepared** state simultaneously. Increasing the value of this parameter causes MogDB to request more System V shared memory than the default configuration allows.
+
+When MogDB is deployed as an HA system, set this parameter on standby servers to a value greater than or equal to that on the primary server. Otherwise, queries will fail on the standby servers.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 262143
+
+> **Default value**: **10**
+>
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** Generally, explicit PREPARE operations are not required for transactions. If explicit PREPARE operations are performed for transactions, increase the value of this parameter to be greater than the number of concurrent services that require PREPARE to prevent preparation failures.
+
+## work_mem
+
+**Parameter description**: Specifies the amount of memory to be used by internal sort operations and hash tables before they write data into temporary disk files. Sort operations are required for **ORDER BY**, **DISTINCT**, and merge joins. Hash tables are used in hash joins, hash-based aggregation, and hash-based processing of **IN** subqueries.
+
+In a complex query, several sort or hash operations may run in parallel; each operation will be allowed to use as much memory as this parameter specifies. If the memory is insufficient, data will be written into temporary files. In addition, several running sessions could be performing such operations concurrently. Therefore, the total memory used may be many times the value of **work_mem**.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 64 to 2147483647. The unit is KB.
+
+**Default value**: **64MB**
+
+- **Default value**: **64 MB**
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** **Setting suggestions**: If the physical memory specified by **work_mem** is insufficient, additional operator calculation data will be written into temporary tables based on query characteristics and the degree of parallelism. This reduces performance by five to ten times, and prolongs the query response time from seconds to minutes.
+  >
+  > - For complex serial queries, each query requires five to ten associated operations. Set **work_mem** using the following formula: **work_mem** = 50% of the memory/10.
+  > - For simple serial queries, each query requires two to five associated operations. Set **work_mem** using the following formula: **work_mem** = 50% of the memory/5.
+  > - For concurrent queries, set **work_mem** using the following formula: **work_mem** = **work_mem** for serial queries/Number of concurrent SQL statements.
+
+## query_mem
+
+**Parameter description**: Specifies the memory used by a query. If the value of **query_mem** is greater than 0, the optimizer adjusts the memory cost estimate to this value when generating an execution plan.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: 0 or an integer greater than 32 MB. The default unit is KB. If the value is set to a negative value or is less than 32 MB, the default value **0** is used. In this case, the optimizer does not adjust the estimated query memory.
+
+**Default value**: **0**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - If the value of **query_mem** is greater than 0, the optimizer adjusts the memory cost estimate to this value when generating an execution plan.
+> - If the value is set to a negative value or a positive integer less than 32 MB, the default value **0** is used. In this case, the optimizer does not adjust the estimated query memory.
+
+## query_max_mem
+
+**Parameter description**: Specifies the maximum memory that can be used by a query. If the value of **query_max_mem** is greater than 0, an error is reported when the query memory usage exceeds the value.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: 0 or an integer greater than 32 MB. The default unit is KB. If the value is set to a negative value or a positive integer less than 32 MB, the default value **0** is used. In this case, the optimizer does not limit the query memory.
+
+**Default value**: **0**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - If the value of **query_max_mem** is greater than 0, an error is reported when the query memory usage exceeds the value.
+> - If the value is set to a negative value or a positive integer less than 32 MB, the default value **0** is used. In this case, the optimizer does not limit the query memory.
+
+## maintenance_work_mem
+
+**Parameter description:** Specifies the maximum amount of memory to be used by maintenance operations, such as **VACUUM**, **CREATE INDEX**, and **ALTER TABLE ADD FOREIGN KEY**. This parameter may affect the execution efficiency of **VACUUM**, **VACUUM FULL**, **CLUSTER**, and **CREATE INDEX**.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1024 to *INT_MAX*. The unit is KB.
+
+- **Default value**: **16MB**
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** **Setting suggestions**:
+  >
+  > - The value of this parameter must be greater than that of work_mem so that database dumps can be more quickly cleared or restored. In a database session, only one maintenance operation can be performed at a time. Maintenance is usually performed when there are not many running sessions.
+  > - When the Automatic Vacuuming process is running, up to autovacuum_max_workers times this memory may be allocated. In this case, set **maintenance_work_mem** to a value greater than or equal to that of work_mem.
+  > - If a large amount of data is to be clustered, increase the value of this parameter in the session.
+
+## psort_work_mem
+
+**Parameter description**: Specifies the memory capacity to be used for partial sorting in a column-store table before writing to temporary disk files. This parameter can be used for inserting tables with a partial cluster key or index, creating a table index, and deleting or updating a table.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> Several running sessions could be performing such operations concurrently. Therefore, the total memory used may be many times the value of **psort_work_mem**.
+
+**Value range**: an integer ranging from 64 to 2147483647. The unit is KB.
+
+**Default value**: **512MB**
+
+## max_loaded_cudesc
+
+**Parameter description**: Specifies the number of loaded CuDescs per column when a column-store table is scanned. Increasing the value will improve query performance and increase memory usage, particularly when there are many columns in the column-store table.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> If **max_loaded_cudesc** is set to a large value, memory may be insufficient.
+
+**Value range**: 100 to 1073741823
+
+**Default value:** **1024**
+
+## max_stack_depth
+
+**Parameter description**: Specifies the maximum safe depth of the MogDB execution stack. The safety margin is required because the stack depth is not checked in every routine in the server, but only in key potentially-recursive routines, such as expression evaluation.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 100 to *INT_MAX*. The unit is KB.
+
+**Default value**: **2 MB**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** When setting this parameter, comply with the following principles:
+>
+> - The database needs to reserve 640 KB stack depth. Therefore, the ideal setting for this parameter is the actual stack size limit enforced by the OS kernel (as set by **ulimit -s**) minus 640 KB.
+> - Setting this parameter to a value larger than the actual kernel limit means that a running recursive function may crash an individual backend process. In an OS where MogDB can determine the kernel limit, this parameter cannot be set to an unsafe value.
+> - Since not all OSs provide this function, you are advised to set a specific value for this parameter.
+> - **2 MB** is a small value and will hardly cause system breakdown,
+
+## cstore_buffers
+
+**Parameter description**: Specifies the shared buffer size used in column-store tables.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 16384 to 1073741823. The unit is KB.
+
+**Default value**: **1 GB**
+
+**Setting suggestions**:
+
+Column-store tables use the shared buffer specified by **cstore_buffers** instead of that specified by **shared_buffers**. When column-store tables are mainly used, reduce the value of **shared_buffers** and increase that of **cstore_buffers**.
+
+## bulk_read_ring_size
+
+**Parameter description**: Specifies the ring buffer size used for parallel data export.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 256 to 2147483647. The unit is KB.
+
+**Default value**: **16MB**
+
+## enable_early_free
+
+**Parameter description**: Specifies whether the operator memory can be released in advance.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the operator memory can be released in advance.
+- **off** indicates that the operator memory cannot be released in advance.
+
+**Default value**: **on**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/2-disk-space.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/2-disk-space.md
new file mode 100644
index 0000000000000000000000000000000000000000..60c0842a090db6f375acd25c1579968d8865ebb3
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/2-disk-space.md
@@ -0,0 +1,35 @@
+---
+title: Disk Space
+summary: Disk Space
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Disk Space
+
+This section describes the disk space parameters, which are used to set limits on the disk space for storing temporary files.
+
+## sql_use_spacelimit
+
+**Parameter description**: Specifies the space size for files to be flushed to disks when a single SQL statement is executed on a single database node. The managed space includes the space occupied by ordinary tables, temporary tables, and intermediate result sets to be flushed to disks.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from -1 to 2147483647. The unit is KB. **-1** indicates no limit.
+
+**Default value:** **-1**
+
+## temp_file_limit
+
+**Parameter description**: Specifies the limit on the size of a temporary file spilled to disk in a session. The temporary file can be a sort or hash temporary file, or the storage file for a held cursor.
+
+This is a session-level setting.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> This parameter does not apply to disk space used for temporary tables during the SQL query process.
+
+**Value range**: an integer ranging from -1 to 2147483647. The unit is KB. **-1** indicates no limit.
+
+**Default value**: **-1**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/3-kernel-resource-usage.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/3-kernel-resource-usage.md
new file mode 100644
index 0000000000000000000000000000000000000000..8d373b38513bea3793cbb859149d739a5c4649c7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/3-kernel-resource-usage.md
@@ -0,0 +1,41 @@
+---
+title: Kernel Resource Usage
+summary: Kernel Resource Usage
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Kernel Resource Usage
+
+This section describes kernel resource parameters. Whether these parameters take effect depends on OS settings.
+
+## max_files_per_process
+
+**Parameter description**: Specifies the maximum number of simultaneously open files allowed by each server process. If the kernel is enforcing a proper limit, setting this parameter is not required.
+
+However, on some platforms, such as most Berkeley Software Distribution (BSD) systems, the kernel allows individual processes to open much more files than the system can support. If the message "Too many open files" is displayed, set this parameter to a smaller value. Generally, the system must meet this requirement: Number of file descriptors >= Maximum number of concurrent statements x Number of database nodes x **max_files_per_process** x 3
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 25 to 2147483647
+
+**Default value**: **1000**
+
+## shared_preload_libraries
+
+**Parameter description:** Specifies one or more shared libraries to be preloaded at server start. If multiple libraries are to be loaded, separate their names using commas (,). For example, **$libdir/mylib** will cause **mylib.so** (or on some platforms, **mylib.sl**) to be preloaded before the loading of the standard library directory.
+
+You can preinstall the MogDB's stored procedure library using the **$libdir/pl** *XXX* syntax as described in the preceding text. *XXX* can only be **pgsql**, **perl**, **tcl**, or **python**.
+
+By preloading a shared library and initializing it as required, the library startup time is avoided when the library is first used. However, the time to start each new server process may increase, even if that process never uses the library. Therefore, set this parameter only for libraries that will be used in most sessions.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - If a specified library is not found, the MogDB service will fail to start.
+> - Each MogDB-supported library has a special mark that is checked to guarantee compatibility. Therefore, libraries that do not support MogDB cannot be loaded in this way.
+
+**Value range**: a string
+
+**Default value**: empty
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/4-cost-based-vacuum-delay.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/4-cost-based-vacuum-delay.md
new file mode 100644
index 0000000000000000000000000000000000000000..5b8fa4a7124a7cc5dcb94c5948517060876ca7cb
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/4-cost-based-vacuum-delay.md
@@ -0,0 +1,76 @@
+---
+title: Cost-based Vacuum Delay
+summary: Cost-based Vacuum Delay
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Cost-based Vacuum Delay
+
+This feature allows administrators to reduce the I/O impact of the **VACUUM** and **ANALYZE** statements on concurrent database activities. It is often more important to prevent maintenance statements, such as **VACUUM** and **ANALYZE**, from affecting other database operations than to run them quickly. Cost-based vacuum delay provides a way for administrators to achieve this purpose.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> Certain vacuum operations hold critical locks and should be complete as quickly as possible. In MogDB, cost-based vacuum delays do not take effect during such operations. To avoid uselessly long delays in such cases, the actual delay is the larger of the two calculated values:
+>
+> - **vacuum_cost_delay** x **accumulated_balance**/**vacuum_cost_limit**
+> - **vacuum_cost_delay** x 4
+
+**Background**
+
+During the execution of the ANALYZE | ANALYSE and VACUUM statements, the system maintains an internal counter that keeps track of the estimated cost of the various I/O operations that are performed. When the accumulated cost reaches a limit (specified by **vacuum_cost_limit**), the process performing the operation will sleep for a short period of time (specified by **vacuum_cost_delay**). Then, the counter resets and the operation continues.
+
+By default, this feature is disabled. To enable this feature, set **vacuum_cost_delay** to a positive value.
+
+## vacuum_cost_delay
+
+**Parameter description**: Specifies the length of time that a process will sleep when **vacuum_cost_limit** has been exceeded.
+
+In many systems, the effective resolution of the sleep length is 10 milliseconds. Therefore, setting this parameter to a value that is not a multiple of 10 has the same effect as setting it to the next higher multiple of 10.
+
+This parameter is usually set to a small value, such as 10 or 20 milliseconds. Adjusting vacuum's resource consumption is best done by changing other vacuum cost parameters.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 100 (unit: ms). A positive number enables cost-based vacuum delay and **0** disables cost-based vacuum delay.
+
+**Default value**: **0**
+
+## vacuum_cost_page_hit
+
+**Parameter description**: Specifies the estimated cost for vacuuming a buffer found in the shared buffer. It represents the cost to lock the buffer pool, look up the shared hash table, and scan the content of the page.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 10000
+
+**Default value**: **1**
+
+## vacuum_cost_page_miss
+
+**Parameter description**: Specifies the estimated cost for vacuuming a buffer read from the disk. It represents the cost to lock the buffer pool, look up the shared hash table, read the desired block from the disk, and scan the block.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 10000
+
+**Default value:** **10**
+
+## vacuum_cost_page_dirty
+
+**Parameter description**: Specifies the estimated cost charged when vacuum modifies a block that was previously clean. It represents the extra I/O required to flush the dirty block out to disk again.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 1000
+
+**Default value:** **20**
+
+## vacuum_cost_limit
+
+**Parameter description**: Specifies the cost limit. The vacuuming process will sleep if this limit is exceeded.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1 to 10000
+
+**Default value**: **200**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/5-background-writer.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/5-background-writer.md
new file mode 100644
index 0000000000000000000000000000000000000000..a0714f5cf8b0dfc69644f07e5a36db78b446e2a3
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/5-background-writer.md
@@ -0,0 +1,144 @@
+---
+title: Background Writer
+summary: Background Writer
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Background Writer
+
+This section describes background writer parameters. The background writer process is used to write dirty data (new or modified data) in shared buffers to disks. This mechanism ensures that database processes seldom or never need to wait for a write action to occur when handling user queries.
+
+It also mitigates performance deterioration caused by checkpoints because only a few of dirty pages need to be flushed to the disk when the checkpoints arrive. This mechanism, however, increases the overall net I/O load because while a repeatedly-dirtied page may otherwise be written only once per checkpoint interval, the background writer may write it several times as it is dirtied in the same interval. In most cases, continuous light loads are preferred, instead of periodical load peaks. The parameters discussed in this section can be set based on actual requirements.
+
+## bgwriter_thread_num
+
+**Parameter description**: Specifies the number of bgwriter threads for flushing pages after the incremental checkpoint is enabled. Dirty pages to be evicted are flushed to disks, and non-dirty pages are placed in the candidate buffer chain. This parameter helps accelerate buffer eviction and improve performance.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 8
+
+- To test the effect of disabling this feature during development, you can set this parameter to **0**. However, if this parameter is set to **0**, the value will be changed to **1** in the code and the feature cannot be disabled.
+- If this parameter is set to a value ranging from 1 to 8, the corresponding number of background threads are started to maintain the candidate buffer chain. Dirty pages that meet the conditions are flushed to disks, and non-dirty pages are added to the candidate list.
+
+**Default value**: **2**
+
+## bgwriter_delay
+
+**Parameter description**: Specifies the interval at which the background writer writes dirty shared buffers. The background writer initiates write operations for some dirty shared buffers (the volume of data to be written is specified by the **bgwriter_lru_maxpages** parameter), sleep for the milliseconds specified by **bgwriter_delay**, and then restarts.
+
+In many systems, the effective resolution of sleep delays is 10 milliseconds. Therefore, setting this parameter to a value that is not a multiple of 10 has the same effect as setting it to the next higher multiple of 10.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 10 to 10000. The unit is millisecond.
+
+**Default value**: **2s**
+
+**Setting suggestion:** Reduce this value in slow data writing scenarios to reduce the checkpoint load.
+
+bgwriter_delay
+
+**Parameter description**: Specifies the interval at which the background writer writes dirty shared buffers. The background writer initiates write operations for some dirty shared buffers (the volume of data to be written is specified by the **bgwriter_lru_maxpages** parameter), sleep for the milliseconds specified by **bgwriter_delay**, and then restarts.
+
+In many systems, the effective resolution of sleep delays is 10 milliseconds. Therefore, setting this parameter to a value that is not a multiple of 10 has the same effect as setting it to the next higher multiple of 10.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 10 to 10000. The unit is millisecond.
+
+**Default value**: **2s**
+
+**Setting suggestion:** Reduce this value in slow data writing scenarios to reduce the checkpoint load.
+
+## candidate_buf_percent_target
+
+**Parameter description**: Specifies the expected percentage of available buffers in the shared_buffer memory buffer in the candidate buffer chain when the incremental checkpoint is enabled. If the number of available buffers in the current candidate chain is less than the target value, the bgwriter thread starts flushing dirty pages that meet the requirements.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range:** a double-precision floating point number ranging from 0.1 to 0.85
+
+**Default value**: **0.3**
+
+## bgwriter_lru_maxpages
+
+**Parameter description**: Specifies the number of dirty buffers the background writer can write in each round.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 1000
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** When this parameter is set to **0**, the background writer is disabled. This setting does not affect checkpoints.
+
+**Default value**: **100**
+
+## bgwriter_lru_multiplier
+
+**Parameter description**: Specifies the coefficient used to estimate the number of dirty buffers the background writer can write in the next round.
+
+The number of dirty buffers written in each round depends on the number of buffers used by server processes during recent rounds. The estimated number of buffers required in the next round is calculated using the following formula: Average number of recently used buffers x **bgwriter_lru_multiplier**. The background writer writes dirty buffers until sufficient clean and reusable buffers are available. The number of buffers the background writer writes in each round is always equal to or less than **bgwriter_lru_maxpages**.
+
+Therefore, the value **1.0** represents a just-in-time policy of writing exactly the number of dirty buffers predicted to be required. Larger values provide some cushion against spikes in demand, whereas smaller values intentionally leave more writes to be done by server processes.
+
+Smaller values of **bgwriter_lru_maxpages** and **bgwriter_lru_multiplier** reduce the extra I/O load caused by the background writer, but make it more likely that server processes will have to issue writes for themselves, delaying interactive queries.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a floating point number ranging from 0 to 10
+
+**Default value:** **2**
+
+## pagewriter_thread_num
+
+**Parameter description**: Specifies the number of threads for background page flushing after the incremental checkpoint is enabled. Dirty pages are flushed in sequence to disks, promoting recovery points.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1 to 16
+
+**Default value**: **4**
+
+## dirty_page_percent_max
+
+**Parameter description**: Specifies the percentage of dirty pages to **shared_buffers**after the incremental checkpoint is enabled. When the value of this parameter is reached, the background page flush thread flushes dirty pages based on the maximum value of max_io_capacity.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a floating point number ranging from 0.1 to 1
+
+**Default value**: **0.9**
+
+## pagewriter_sleep
+
+**Parameter description**: Specifies the interval for the pagewriter thread to flush dirty pages to disks after the incremental checkpoint is enabled. When the ratio of dirty pages to shared_buffers reaches dirty_page_percent_max, the number of pages in each batch is calculated based on the value of max_io_capacity. In other cases, the number of pages in each batch decreases proportionally.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 3600000. The unit is ms.
+
+**Default value**: **2000ms(2s)**
+
+## max_io_capacity
+
+**Parameter description**: Specifies the maximum I/O per second for the backend write process to flush pages in batches. Set this parameter based on the service scenario and disk I/O capability of the host. If the RTO is short or the data volume is much larger than the shared memory, and the service access data volume is random, the value of this parameter cannot be too small. A small parameter value reduces the number of pages flushed by the backend write process. If a large number of pages are eliminated due to service triggering, the services are affected.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 30720 to 10485760. The unit is KB.
+
+**Default value**: **512000 KB** (500 MB)
+
+## enable_consider_usecount
+
+**Parameter description**: Specifies whether the backend thread considers the page popularity during page replacement. You are advised to enable this parameter in large-capacity scenarios.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on**/**true**: The page popularity is considered.
+- **off**/**false**: The page popularity is not considered.
+
+**Default value**: **off**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/6-asynchronous-io-operations.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/6-asynchronous-io-operations.md
new file mode 100644
index 0000000000000000000000000000000000000000..991315367c5502ccd10367d92de2121d08c3cbd9
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/6-asynchronous-io-operations.md
@@ -0,0 +1,117 @@
+---
+title: Asynchronous I/O Operations
+summary: Asynchronous I/O Operations
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Asynchronous I/O Operations
+
+## enable_adio_debug
+
+**Parameter description**: Specifies whether O&M personnel are allowed to generate some ADIO logs to locate ADIO issues. This parameter is used only by developers. Common users are advised not to use it.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** or **true** indicates that generation of ADIO logs is allowed.
+- **off** or **false** indicates that generation of ADIO logs is disallowed.
+
+**Default value**: **off**
+
+## enable_adio_function
+
+**Parameter description**: Specifies whether to enable the ADIO function.
+
+The current version does not support enabling the asynchronous IO function. By default, this function is disabled. Please do not modify it yourself.
+
+**Value range**: Boolean
+
+- **on** or **true** indicates that the function is enabled.
+- **off** or **false** indicates that the function is disabled.
+
+**Default value**: **off**
+
+## enable_fast_allocate
+
+**Parameter description**: Specifies whether the quick disk space allocation is enabled.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix). This function can be enabled only in the XFS file system.
+
+**Value range**: Boolean
+
+- **on** or **true** indicates that the function is enabled.
+- **off** or **false** indicates that the function is disabled.
+
+**Default value**: **off**
+
+## prefetch_quantity
+
+**Parameter description**: Specifies the amount of the I/O that the row-store prefetches using the ADIO.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 128 to 131072. The unit is 8 KB.
+
+**Default value**: **32MB** (4096 x 8 KB)
+
+## backwrite_quantity
+
+**Parameter description**: Specifies the amount of I/O that the row-store writes using the ADIO.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 128 to 131072. The unit is 8 KB.
+
+**Default value**: **8MB** (1024 x 8 KB)
+
+## cstore_prefetch_quantity
+
+**Parameter description**: Specifies the amount of I/O that the column-store prefetches using the ADIO.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1024 to 1048576. The unit is KB.
+
+**Default value**: **32MB**
+
+## cstore_backwrite_quantity
+
+**Parameter description**: Specifies the amount of I/O that the column-store writes using the ADIO.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1024 to 1048576. The unit is KB.
+
+**Default value**: **8MB**
+
+## cstore_backwrite_max_threshold
+
+**Parameter description**: Specifies the maximum amount of buffer I/O that the column-store writes in the database using the ADIO.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 4096 to *INT_MAX*/2. The unit is KB.
+
+**Default value**: **2GB**
+
+## fast_extend_file_size
+
+**Parameter description**: Specifies the disk size that the row-store pre-scales using the ADIO.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1024 to 1048576. The unit is KB.
+
+**Default value**: **8MB**
+
+## effective_io_concurrency
+
+**Parameter description**: Specifies the number of requests that can be simultaneously processed by a disk subsystem. For the RAID array, the parameter value must be the number of disk drive spindles in the array.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 1000
+
+**Default value**: **1**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/40-AI-features.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/40-AI-features.md
new file mode 100644
index 0000000000000000000000000000000000000000..60790bb3a58bc2ac7d587eb725f2801d4764763a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/40-AI-features.md
@@ -0,0 +1,64 @@
+---
+title: AI Features
+summary: AI Features
+author: Zhang Cuiping
+date: 2021-11-08
+---
+
+# AI Features
+
+## enable_hypo_index
+
+**Parameter description**: Specifies whether the database optimizer considers the created virtual index when executing the **EXPLAIN** statement. By executing **EXPLAIN** on a specific query statement, you can evaluate whether the index can improve the execution efficiency of the query statement based on the execution plan provided by the optimizer.
+
+This parameter is a **USERSET** parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that a virtual index is created during **EXPLAIN** execution.
+- **off** indicates that no virtual index is created during **EXPLAIN** execution.
+
+**Default value**: **off**
+
+## db4ai_snapshot_mode
+
+**Parameter description**: There are two snapshot modes: MSS (materialized mode, storing data entities) and CSS (computing mode, storing incremental information).
+
+This parameter is a **USERSET** parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string, which can be **MSS** or **CSS**
+
+- **MSS** indicates the materialized mode. The DB4AI stores data entities when snapshots are created.
+- **CSS** indicates the computing mode. The DB4AI stores incremental information when creating snapshots.
+
+**Default value:** **MSS**
+
+## db4ai_snapshot_version_delimiter
+
+**Parameter description**: Specifies the delimiter for the snapshot version of a data table.
+
+This parameter is a **USERSET** parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string, consisting of one or more characters.
+
+**Default value**: **@**
+
+## db4ai_snapshot_version_separator
+
+**Parameter description**: Specifies the subversion delimiter of a data table snapshot.
+
+This parameter is a **USERSET** parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string, consisting of one or more characters.
+
+**Default value**: .
+
+## unix_socket_directory
+
+**Parameter description:** Specifies the path for storing files in the unix_socket communication mode. You can set this parameter only in the configuration file **postgresql.conf**. Before enabling the fenced mode, you need to set this GUC parameter.
+
+This parameter is a **POSTMASTER** parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string of 0 or more characters
+
+**Default value:** **"**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/5-parallel-import.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/5-parallel-import.md
new file mode 100644
index 0000000000000000000000000000000000000000..ef49da287757cdfae497836f9c5210b093cb50c6
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/5-parallel-import.md
@@ -0,0 +1,58 @@
+---
+title: Parallel Data Import
+summary: Parallel Data Import
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Parallel Data Import
+
+MogDB provides a parallel data import function that enables a large amount of data to be imported in a fast and efficient manner. This section describes parameters for importing data in parallel.
+
+## raise_errors_if_no_files
+
+**Parameter description**: Specifies whether to distinguish between the problems "the number of imported file records is empty" and "the imported file does not exist". If this parameter is set to **on** and the problem "the imported file does not exist" occurs, MogDB will report the error message "file does not exist".
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the messages of "the number of imported file records is empty" and "the imported file does not exist" are distinguished when files are imported.
+- **off** indicates that the messages of "the number of imported file records is empty" and "the imported file does not exist" are the same when files are imported.
+
+**Default value**: **off**
+
+## partition_mem_batch
+
+**Parameter description**: In order to optimize the inserting of column-store partitioned tables in batches, the data is buffered during the inserting process and then written in the disk. You can specify the number of caches through **partition_mem_batch**. If the value is too large, much memory will be consumed. If it is too small, the performance of inserting column-store partitioned tables in batches will deteriorate.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: 1 to 65535
+
+**Default value**: **256**
+
+## partition_max_cache_size
+
+**Parameter description**: In order to optimize the inserting of column-store partitioned tables in batches, the data is buffered during the inserting process and then written in the disk. You can specify the data buffer cache size through **partition_max_cache_size**. If the value is too large, much memory will be consumed. If it is too small, the performance of inserting column-store partitioned tables in batches will deteriorate.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**:
+
+4096 to *INT_MAX*/2. The unit is KB.
+
+**Default value**: **2GB**
+
+## enable_delta_store
+
+**Parameter description**: Specifies whether to enable delta tables for column-store tables. Delta tables will improve the performance of importing a single piece of data to a column-store table and prevent table bloating. If this parameter is set to **on**, data to be imported to a column-store table will be stored in the delta table when the data volume is less than **DELTAROW_THRESHOLD** specified in table definition and otherwise will be stored in CUs of the main table. This parameter affects all operations involving data transfer of column-store tables, including **INSERT**, **COPY**, **VACUUM**, **VACUUM FULL**, **VACUUM DELTAMERGE**, and data redistribution.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**:
+
+- **on** indicates that delta tables are enabled.
+- **off** indicates that delta tables are disabled.
+
+**Default value**: **off**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/1-settings.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/1-settings.md
new file mode 100644
index 0000000000000000000000000000000000000000..85a89b044d58ab5a6f11e20329d8711486ff1fd3
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/1-settings.md
@@ -0,0 +1,256 @@
+---
+title: Settings
+summary: Settings
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Settings
+
+## wal_level
+
+**Parameter description**: Specifies the level of the information that is written to the write ahead log (WAL).
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - To enable WAL archiving and data streaming replication between primary and standby servers, set this parameter to **archive** or **hot_standby**.
+> - This parameter can be set to **minimal** only in a single-server system. When the parameter value is **minimal**, **archive_mode** must be set to **off**, **hot_standby** must be set to **off**, and **max_wal_senders** must be set to **0**. Otherwise, the database startup fails.
+> - If this parameter is set to **archive**, **hot_standby** must be set to **off**. Otherwise, the database startup fails. However, **hot_standby** cannot be set to **off** in a primary-standby deployment. For details, see the description of the **hot_standby** parameter.
+
+**Value range**: enumerated values
+
+- minimal
+
+  Advantages: Certain bulk operations (including creating tables and indexes, executing cluster operations, and copying tables) are safely skipped in logging, which can make those operations much faster.
+
+  Disadvantages: WALs contain only basic information required for recovery from a database server crash or an emergency shutdown. Data cannot be restored from archived WALs.
+
+- archive
+
+  Adds logging required for WAL archiving, supporting the database restoration from archives.
+
+- hot_standby
+
+  - Further adds information required to run SQL queries on a standby server and takes effect after a server restart.
+  - To enable read-only queries on a standby server, the **wal_level** parameter must be set to **hot_standby** on the primary server and the **hot_standby** parameter must be set to **on** on the standby server. There are few measurable differences in performance between using **hot_standby** and **archive** levels. However, feedback is welcome if any differences in their impacts on product performance are noticeable.
+
+- logical
+
+  This parameter indicates that WALs support logical replication.
+
+**Default value**: **hot_standby**
+
+## fsync
+
+**Parameter description:** Specifies whether the MogDB server uses the **fsync()** function (see **[wal_sync_method](#wal_sync_method)**) to ensure that updates can be written to disks in a timely manner.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - Using the **fsync()** function ensures that the data can be recovered to a known state when an OS or a hardware crashes.
+> - Setting this parameter to **off** may result in unrecoverable data corruption in a system crash.
+
+**Value range**: Boolean
+
+- **on** indicates that the **fsync()** function is used.
+- **off** indicates that the **fsync()** function is not used.
+
+**Default value**: **on**
+
+## synchronous_commit
+
+**Parameter description**: Specifies the synchronization mode of the current transaction.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: enumerated values
+
+- **on** indicates that synchronization logs of a standby server are flushed to disk.
+- **off** indicates asynchronous commit.
+- **local** indicates local commit.
+- **remote_write** indicates that synchronization logs of a standby server are written to disk.
+- **remote_receive** indicates that the standby server receives logs.
+- **remote_apply** indicates that the synchronization logs of the standby server are replayed.
+- **true** indicates that synchronization logs of a standby server are flushed to disk.
+- **false** indicates asynchronous commit.
+- **yes** indicates that synchronization logs of a standby server are flushed to disk.
+- **no** indicates asynchronous commit.
+- **1** indicates that synchronization logs of a standby server are flushed to disk.
+- **0** indicates asynchronous commit.
+- **2** indicates that the synchronization logs of the standby server are replayed.
+
+**Default value**: **off**
+
+## wal_sync_method
+
+**Parameter description**: Specifies the method used for forcing WAL updates out to disk.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** If **[fsync](#fsync)** is set to **off**, the setting of this parameter does not take effect because WAL file updates will not be forced out to disk.
+
+**Value range**: enumerated values
+
+- **open_datasync** indicates that WAL files are opened with the **O_DSYNC** option.
+
+- **fdatasync** indicates that **fdatasync()** is called at each commit. (SUSE Linux 10 and SUSE Linux 11 are supported.)
+
+- **fsync_writethrough** indicates that **fsync()** is called at each commit to force data in the buffer to be written to the disk.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** **wal_sync_method** can be set to **fsync_writethrough** on a Windows platform, but this setting has the same effect as setting the parameter to **fsync**.
+
+- **fsync** indicates that **fsync()** is called at each commit. (SUSE Linux 10 and SUSE Linux 11 are supported.)
+
+- **open_sync** indicates that WAL files are written with **open()** option **O_SYNC**. (SUSE Linux 10 and SUSE Linux 11 are supported.)
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** Not all platforms support the preceding parameters.
+
+**Default value:** **fdatasync**
+
+## full_page_writes
+
+**Parameter description**: Specifies whether the MogDB server writes the entire content of each disk page to WALs during the first modification of that page after a checkpoint. When the incremental checkpoint function and **enable_double_write** are enabled at the same time, **full_page_writes** is not used.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - This parameter is needed because a page write that is in process during an OS crash might be only partially completed, leading to an on-disk page that contains a mix of old and new data. The row-level change data normally stored in WALs will not be enough to completely restore such a page during post-crash recovery. Storing the full page image guarantees that the page can be correctly restored, but at the price of increasing the amount of data that must be written to WALs.
+> - Setting this parameter to **off** might lead to unrecoverable data corruption after a system failure. It might be safe to set this parameter to **off** if you have hardware (such as a battery-backed disk controller) or file-system software (such as ReiserFS 4) that reduces the risk of partial page writes to an acceptably low level.
+
+**Value range**: Boolean
+
+- **on** indicates that this feature is enabled.
+- **off** indicates that this feature is disabled.
+
+**Default value**: **on**
+
+## wal_log_hints
+
+**Parameter description**: Specifies whether to write an entire page to WALs during the first modification of that page after a checkpoint, even for non-critical modifications of so-called hint bits. You are advised not to modify the setting.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the entire page is written to WALs.
+- **off** indicates that the entire page is not written to WALs.
+
+**Default value**: **on**
+
+## wal_buffers
+
+**Parameter description**: Specifies the number of **XLOG_BLCKSZ**s used for storing WAL data. The size of each **XLOG_BLCKSZ** is 8 KB.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: -1 to 218
+
+- If this parameter is set to **-1**, the value of **wal_buffers** is automatically changed to 1⁄32 of **shared_buffers**. The minimum value is 8 x **XLOG_BLCKSZ**, and the maximum value is 2048 x **XLOG_BLCKSZ**. That means if the 1⁄32 of **shared_buffers** is smaller than 8 x **XLOG_BLCKSZ** or larger than 2048 x **XLOG_BLCKSZ**, the minimum value or the maximum value is taken.
+- If this parameter is set to a value other than **-1** and smaller than **4**, the value **4** is used.
+
+**Default value**: **16MB**
+
+**Setting suggestions**: The content of the WAL buffers is written to disk at every transaction commit, so extremely large values are unlikely to provide a significant increase in system performance. However, setting this parameter to hundreds of megabytes can improve the disk write performance on a server to which a large number of transactions are committed at the same time. The auto-tuning selected by the value **-1** should give reasonable results in most cases.
+
+## wal_writer_delay
+
+**Parameter description**: Specifies the delay between activity rounds for the WAL writer.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** A longer delay might lead to insufficient WAL buffer and a shorter delay leads to continuously writing of the WALs, thereby increasing the load of disk I/O.
+
+**Value range**: an integer ranging from 1 to 10000. The unit is millisecond.
+
+**Default value**: **200ms**
+
+## commit_delay
+
+**Parameter description**: Specifies the duration for committed data to be stored in the WAL buffer.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - When this parameter is set to a non-zero value, the committed transaction is stored in the WAL buffer instead of being written to the WAL immediately. Then the WAL writer process flushes the buffer out to disk periodically.
+> - If system load is high, other transactions are probably ready to be committed within the delay. If no other transactions are ready to be committed, the delay is a waste of time.
+
+**Value range**: an integer ranging from 0 to 100000. The unit is μs. **0** indicates no delay.
+
+**Default value**: **0**
+
+## commit_siblings
+
+**Parameter description**: Specifies a threshold on the number of concurrent open transactions. If the number of concurrent open transactions is greater than the value of this parameter, a transaction that initiates a commit request will wait for a period of time specified by **[commit_delay](#commit_delay)**. Otherwise, this transaction is written into WALs immediately.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 1000
+
+**Default value**: **5**
+
+## wal_block_size
+
+**Parameter description**: Specifies the size of a WAL disk block.
+
+This parameter is a fixed INTERNAL parameter and cannot be modified.
+
+**Value range**: an integer. The unit is byte.
+
+**Default value**: **8192**
+
+## wal_segment_size
+
+**Parameter description**: Specifies the size of a WAL segment file.
+
+This parameter is a fixed INTERNAL parameter and cannot be modified.
+
+**Value range**: an integer. The unit is 8 KB.
+
+**Default value**: **16 MB** (2048 x 8 KB)
+
+## walwriter_cpu_bind
+
+**Parameter description**: Specifies the CPU core bound to the WAL write thread. This parameter is used together with the thread pool parameter.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from -1 to the number of cores minus 1
+
+**Default value**: **-1**
+
+## walwriter_sleep_threshold
+
+**Parameter description**: Specifies the number of times that idle Xlogs are refreshed before the xlogflusher enters the sleep state. If the number of times reaches the threshold, the xlogflusher enters the sleep state.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1 to 50000
+
+**Default value**: **500**
+
+## wal_file_init_num
+
+**Parameter description**: Specifies the number of Xlog segment files to be created by the WAL writer.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 1000000
+
+**Default value**: **10**
+
+## force_promote
+
+**Parameter description**: Specifies whether to enable the forcible switchover function on the standby node.
+
+When a cluster is faulty, the forcible switchover enables the cluster to recover services as soon as possible at the cost of losing some data. This is an escape method used when the cluster is unavailable. You are not advised to trigger this method frequently. You are not advised not to use this function if you are not clear about the impact of data loss on services.
+
+**Value range**: **0** or **1**
+
+The value **0** indicates that the function is disabled and the value **1** indicates that the function is enabled.
+
+**Default value**: **0**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/2-checkpoints.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/2-checkpoints.md
new file mode 100644
index 0000000000000000000000000000000000000000..e35430edfdf7e66000fd47725b88c730de432a82
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/2-checkpoints.md
@@ -0,0 +1,130 @@
+---
+title: Checkpoints
+summary: Checkpoints
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Checkpoints
+
+## checkpoint_segments
+
+**Parameter description**: Specifies the minimum number of WAL segment files in the period specified by **[checkpoint_timeout](#checkpoint_timeout)**. The size of each log file is 16 MB.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer. The minimum value is **1**.
+
+Increasing the value of this parameter speeds up the export of a large amount of data. Set this parameter based on **[checkpoint_timeout](#checkpoint_timeout)** and **shared_buffers**. This parameter affects the number of WAL segment files that can be reused. Generally, the maximum number of reused files in the **pg_xlog** folder is twice the number of **checkpoint_segments**. The reused files are not deleted and are renamed to the WAL segment files which will be later used.
+
+**Default value**: **64**
+
+## checkpoint_timeout
+
+**Parameter description**: Specifies the maximum time between automatic WAL checkpoints.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range:** an integer ranging from 30 to 3600. The unit is second.
+
+If the value of **[checkpoint_segments](#checkpoint_segments)** is increased, you need to increase the value of this parameter. The increase of these two parameters further requires the increase of **shared_buffers**. Consider all these parameters during setting.
+
+**Default value**: **15min**
+
+## checkpoint_completion_target
+
+**Parameter description**: Specifies the completion target of each checkpoint, as a fraction of total time between checkpoints.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a floating point number ranging from 0.0 to 1.0
+
+**Default value**: **0.5**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> **0.5** indicates that each checkpoint should be complete within 50% of the interval between checkpoints.
+
+## checkpoint_warning
+
+**Parameter description**: Specifies a time in seconds. If the checkpoint interval is close to this time due to filling of checkpoint segment files, a message is sent to the server log to suggest an increase in the **[checkpoint_segments](#checkpoint_segments)** value.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to *INT_MAX*. The unit is second. **0** indicates that the warning is disabled.
+
+**Default value**: **5min**
+
+**Recommended value**: **5min**
+
+## checkpoint_wait_timeout
+
+**Parameter description**: Sets the longest time that the checkpoint waits for the checkpointer thread to start.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 2 to 3600. The unit is second.
+
+**Default value**: **1min**
+
+## enable_incremental_checkpoint
+
+**Parameter description**: Specifies whether to enable incremental checkpointing.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+**Default value**: **on**
+
+## enable_double_write
+
+**Parameter description**: Specifies whether to enable the doublewrite buffer. When the incremental checkpointing is enabled, **enable_double_write** is enabled at the same time and the doublewrite buffer instead of **full_page_writes** is used to prevent partial page writes.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+**Default value**: **on**
+
+## incremental_checkpoint_timeout
+
+**Parameter description**: Specifies the maximum interval between automatic WAL checkpoints when the incremental checkpointing is enabled.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range:** an integer ranging from 1 to 3600. The unit is second.
+
+**Default value**: **1min**
+
+## enable_xlog_prune
+
+**Parameter description**: Specifies whether the primary server reclaims logs when any standby server is disconnected.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- When set to on, the host will not reclaim logs when any of the standby machines is disconnected.
+- When set to off, the host will reclaim the log when any of the standby machines is disconnected.
+
+**Default value**: **on**
+
+## max_redo_log_size
+
+**Parameter description**: On the standby DN, this parameter specifies the maximum size of logs between the latest checkpoint and the current log replay location. On the primary DN, this parameter specifies the maximum size of logs between the recovery point and the latest log location. You are not advised to set this parameter to a large value if the RTO is concerned.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 163840 to 2147483647. The unit is KB.
+
+**Default value**: **1GB**
+
+## max_size_for_xlog_prune
+
+**Parameter description**: It takes effect when enable_xlog_prune is turned on. If the backup machine is disconnected and the xlog log size is greater than this threshold, the log will be recycled.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: integer, 0～2147483647, the unit is KB
+
+**Default value**: **2147483647,in KB**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/3-log-replay.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/3-log-replay.md
new file mode 100644
index 0000000000000000000000000000000000000000..20b9fa88272b24a32f403484c279441c4a9ead20
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/3-log-replay.md
@@ -0,0 +1,96 @@
+---
+title: Log Replay
+summary: Log Replay
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Log Replay
+
+## recovery_time_target
+
+**Parameter description**: Specifies the time for a standby server to write and replay logs.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 3600. The unit is second.
+
+**0** indicates that log flow control is disabled. A value from **1** to **3600** indicates that a standby server can write and replay logs within the period specified by the value, so that the standby server can quickly assume the primary role. If this parameter is set to a small value, the performance of the primary server is affected. If it is set to a large value, the log flow is not effectively controlled.
+
+**Default value**: **0**
+
+## recovery_max_workers
+
+**Parameter description**: Specifies the maximum number of concurrent replay threads.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 20
+
+**Default value**: **1** (it will be set to 4 by installation tool in default for better performance)
+
+## recovery_parse_workers
+
+**Parameter description**: Specifies the number of **ParseRedoRecord** threads for the extreme Recovery Time Objective (RTO) feature.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1 to 16
+
+This parameter can be set to a value greater than 1 only when the extreme RTO feature is enabled. In addition, it must be used together with **recovery_redo_workers**. If both **recovery_parse_workers** and **recovery_max_workers** are enabled, the setting of **recovery_parse_workers** prevails and the concurrent replay function is disabled. The extreme RTO feature does not support the hot standby mode or primary/standby/secondary mode. Therefore, **recovery_parse_workers** can be set to a value greater than 1 only when **hot_standby** is set to **off** and **replication_type** to **1**. This feature does not support column-store tables, either. Therefore, disable this feature in a system where column-store tables are used or are to be used.
+
+**Default value**: **1**
+
+## recovery_redo_workers
+
+**Parameter description**: Specifies the number of **PageRedoWorker** threads corresponding to each **ParseRedoRecord** thread when the ultimate RTO feature is enabled.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1 to 8
+
+This parameter must be used together with **recovery_parse_workers**, and it takes effect only when **recovery_parse_workers** is set to a value greater than 0.
+
+**Default value**: **1**
+
+## recovery_parallelism
+
+**Parameter description**: Specifies the actual number of replay threads. This parameter is read-only.
+
+**Value range**: an integer ranging from 1 to 2147483647
+
+This parameter is affected by the parameter: recovery_max_workers and parameter: recovery_parse_workers. When any of the above parameters is greater than 0, the parameter value will be recalculated.
+
+**Default value**: **1**
+
+## enable_page_lsn_check
+
+**Parameter description**: Specifies whether to enable the data page LSN check. During replay, the current LSN of the data page is checked to see if it is the expected one.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+**Default value**: **on**
+
+## recovery_min_apply_delay
+
+**Parameter description**: Specifies the replay delay of the standby node.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - This parameter is invalid on the primary node. It must be set on the standby node to be delayed.
+> - The delay time is calculated based on the timestamp of transaction submission on the primary server and the current time on the standby server. Therefore, ensure that the clocks of the primary and standby servers are the same.
+> - If the delay time is too long, the disk where the XLOG file is located on the standby node may be full. Therefore, you need to set the delay time based on the disk size.
+> - Operations without transactions are not delayed.
+> - After the primary/standby switchover, if the original primary node needs to be delayed, you need to manually set this parameter.
+> - When synchronous_commit is set to remote_apply, synchronous replication is affected by the delay. Each commit message is returned only after the replay on the standby node is complete.
+> - Using this feature also delays **hot_standby_feedback**, which may cause the primary server to bloat, so be careful when using both.
+> - If a DDL operation (such as DROP or TRUNCATE) that holds an AccessExclusive lock is performed on the primary node, the query operation on the operation object on the standby node will be returned only after the lock is released during the delayed replay of the record on the standby node.
+> - The MOT table is not supported.
+
+**Value range**: an integer ranging from 0 to INT_MAX. The unit is ms.
+
+**Default value**: 0 (no delay added)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/4-archiving.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/4-archiving.md
new file mode 100644
index 0000000000000000000000000000000000000000..dffc7de925b156da67b6625a3b537bcd7eab3c89
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/4-archiving.md
@@ -0,0 +1,91 @@
+---
+title: Archiving
+summary: Archiving
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Archiving
+
+## archive_mode
+
+**Parameter description**: Specifies whether to archive WALs.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** When **wal_level** is set to **minimal**, the **archive_mode** parameter is unavailable.
+
+**Value range**: Boolean
+
+- **on** indicates that the archiving is enabled.
+- **off** indicates that the archiving is disabled.
+
+**Default value**: **off**
+
+## archive_command
+
+**Parameter description:** Specifies the command set by the administrator to archive WALs. You are advised to set the archive log path to an absolute path.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - If both **archive_dest** and **archive_command**are configured, WALs are preferentially saved to the directory specified by **archive_dest**. The command configured by **archive_command**does not take effect.
+>
+> - Any **%p** in the string is replaced by the absolute path of the file to archive, and any **%f** is replaced by only the file name. (The relative path is relative to the data directory.) Use **%%** to embed an actual **%** character in the command.
+> - This command returns zero only if it succeeds. The following shows the command:
+>
+> ```
+> archive_command = 'cp --remove-destination %p /mnt/server/archivedir/%f'
+> ```
+>
+> - **-remove-destination** indicates that files will be overwritten during the archiving.
+>
+> - If there are multiple archive commands, write them to the shell script file and set **archive_command**to the command for executing the script. For example:
+>
+>   ```
+>   -- Assume that multiple commands are as follows:
+>   test ! -f dir/%f && cp %p dir/%f
+>   -- The content of the test.sh script is as follows:
+>   test ! -f dir/$2 && cp $1 dir/$2
+>   -- The archive command is as follows:
+>   archive_command='sh dir/test.sh %p %f'
+>   ```
+
+**Value range**: a string
+
+**Default value:** **(disabled)**
+
+## archive_dest
+
+**Parameter description:** Specifies the path set by the administrator to archive WALs. You are advised to set the archive log path to an absolute path.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - If both **archive_dest** and **archive_command**are configured, WALs are preferentially saved to the directory specified by **archive_dest**. The command configured by **archive_command**does not take effect.
+> - If the string is a relative path, it is relative to the data directory. The following is an example:
+>
+> ```
+> archive_dest = '/mnt/server/archivedir/'
+> ```
+
+**Value range**: a string
+
+**Default value**: an empty string
+
+## archive_timeout
+
+**Parameter description**: Specifies the archiving period.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - The server is forced to switch to a new WAL segment file when the period specified by this parameter has elapsed since the last file switch.
+> - Archived files that are closed early due to a forced switch are still of the same length as full files. Therefore, a very short **archive_timeout** will bloat the archive storage. You are advised to set **archive_timeout** to **60s**.
+
+**Value range**: an integer ranging from 0 to *INT_MAX*. The unit is second. **0** indicates that archiving timeout is disabled.
+
+**Default value**: **0**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/7-ha-replication/1-sending-server.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/7-ha-replication/1-sending-server.md
new file mode 100644
index 0000000000000000000000000000000000000000..32b7ee344734737744271cbc1f907fbbd433949b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/7-ha-replication/1-sending-server.md
@@ -0,0 +1,373 @@
+---
+title: Sending Server
+summary: Sending Server
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Sending Server
+
+## max_wal_senders
+
+**Parameter description**: Specifies the maximum number of simultaneously running WAL sender processes. The value cannot be greater than or equal to that of **max_connections**.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** **wal_level** must be set to **archive** or **hot_standby** to allow the connection from standby servers.
+
+**Value range**: an integer ranging from 0 to 262143
+
+**Default value:** **16**
+
+## wal_keep_segments
+
+**Parameter description**: Specifies the number of Xlog file segments. Specifies the minimum number of transaction log files stored in the **pg_xlog** directory. The standby server obtains log files from the primary server for streaming replication.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 2 to *INT_MAX*
+
+**Default value**: **16**
+
+**Setting suggestions**:
+
+- During WAL archiving or recovery from a checkpoint on the server, the system may retain more log files than the number specified by **wal_keep_segments**.
+- If this parameter is set to an excessively small value, a transaction log may have been overwritten by a new transaction before requested by the standby server. As a result, the request fails and the connection between the primary and standby servers is terminated.
+- If the HA system uses asynchronous transmission, increase the value of **wal_keep_segments** when data greater than 4 GB is continuously imported in COPY mode. Take T6000 board as an example. If the data to be imported reaches 50 GB, you are advised to set this parameter to **1000**. You can dynamically restore the setting of this parameter after data import is complete and the WAL synchronization is proper.
+
+## wal_sender_timeout
+
+**Parameter description**: Specifies the maximum duration that the sending server waits for the WAL reception in the receiver.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - If the data volume on the primary server is huge, the value of this parameter must be increased for the database rebuilding on a standby server. For example, if the data volume on the primary server reaches 500 GB, you are advised to set this parameter to 600 seconds.
+> - This parameter cannot be set to a value larger than the value of **wal_receiver_timeout** or the timeout parameter for database rebuilding.
+
+**Value range**: an integer ranging from 0 to *INT_MAX*. The unit is ms.
+
+**Default value**: **6s**
+
+## max_replication_slots
+
+**Parameter description**: Specifies the number of log replication slots in the primary server.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 262143.
+
+**Default value**: **8**
+
+**Setting suggestions**:
+
+When using logical replication, you are advised to set this parameter to: Number of current physical replication slots + Number of required logical replication slots.
+
+- Physical replication slots provide an automatic method to ensure that Xlogs are not removed from a primary node before they are received by all the standby nodes and secondary nodes. That is, physical replication slots are used to support primary/standby HA. The number of physical replication slots required by a database is equal to the ratio of standby and secondary nodes to the primary node. For example, if an HA database has 1 primary node, 1 standby node, and 1 secondary node, the number of required physical replication slots will be 2. If an HA database has 1 primary node and 3 standby nodes, the number of required physical replication slots will be 3.
+- Plan the number of logical replication slots as follows:
+  - A logical replication slot can carry changes of only one database for decoding. If multiple databases are involved, create multiple logical replication slots.
+  - If logical replication is needed by multiple target databases, create multiple logical replication slots in the source database. Each logical replication slot corresponds to one logical replication link.
+
+## enable_slot_log
+
+**Parameter description**: Specifies whether to enable primary/standby synchronization for logical replication slots.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that primary/standby synchronization is enabled for logical replication slots.
+- **off** indicates that primary/standby synchronization is disabled for logical replication slots.
+
+**Default value**: **off**
+
+## max_changes_in_memory
+
+**Parameter description**: Specifies the maximum size (bytes) of a single transaction buffered in the memory during logical decoding.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1 to 2147483647
+
+**Default value**: **4096**
+
+## max_cached_tuplebufs
+
+**Parameter description**: Specifies the maximum size (bytes) of the total tuple information buffered in the memory during logic decoding. You are advised to set this parameter to a value greater than or equal to twice of **[max_changes_in_memory](#max_changes_in_memory)**.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1 to 2147483647
+
+**Default value**: **8192**
+
+## replconninfo1
+
+**Parameter description**: Specifies the information about the first node to be listened to and authenticated by the current server.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string. An empty string indicates that no information about the first node is configured.
+
+**Default value**: empty
+
+## replconninfo2
+
+**Parameter description**: Specifies the information about the second node to be listened to and authenticated by the current server.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string. An empty string indicates that no information about the second node is configured.
+
+**Default value**: empty
+
+## replconninfo3
+
+**Parameter description**: Specifies the information about the third node to be listened to and authenticated by the current server.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string. An empty string indicates that no information about the third node is configured.
+
+**Default value**: empty
+
+## replconninfo4
+
+**Parameter description**: Specifies the information about the fourth node to be listened to and authenticated by the current server.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string. An empty string indicates that no information about the fourth node is configured.
+
+**Default value**: empty
+
+## replconninfo5
+
+**Parameter description**: Specifies the information about the fifth node to be listened to and authenticated by the current server.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string. An empty string indicates that no information about the fifth node is configured.
+
+**Default value**: empty
+
+## replconninfo6
+
+**Parameter description**: Specifies the information about the sixth node to be listened to and authenticated by the current server.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string. An empty string indicates that no information about the sixth node is configured.
+
+**Default value**: empty
+
+## replconninfo7
+
+**Parameter description**: Specifies the information about the seventh node to be listened to and authenticated by the current server.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string. An empty string indicates that no information about the seventh node is configured.
+
+**Default value**: empty
+
+## replconninfo8
+
+**Parameter description**: Specifies the information about the eighth node to be listened to and authenticated by the current server.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string. An empty string indicates that no information about the eighth node is configured.
+
+**Default value**: an empty string
+
+## replconninfo9
+
+**Parameter description**: Specifies the information about the ninth node to be listened on and authenticated by the current server.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string An empty string indicates that no information about the ninth node is configured.
+
+**Default value**: empty
+
+## replconninfo10
+
+**Parameter description**: Specifies the information about the tenth node to be listened on and authenticated by the current server.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string An empty string indicates that no information about the tenth node is configured.
+
+**Default value**: empty
+
+## replconninfo11
+
+**Parameter description**: Specifies the information about the eleventh node to be listened on and authenticated by the current server.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string An empty string indicates that no information about the eleventh node is configured.
+
+**Default value**: empty
+
+## replconninfo12
+
+**Parameter description**: Specifies the information about the twelfth node to be listened on and authenticated by the current server.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string An empty string indicates that no information about the twelfth node is configured.
+
+**Default value**: empty
+
+## replconninfo13
+
+**Parameter description**: Specifies the information about the thirteenth node to be listened on and authenticated by the current server.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string An empty string indicates that no information about the thirteenth node is configured.
+
+**Default value**: empty
+
+## replconninfo14
+
+**Parameter description**: Specifies the information about the fourteenth node to be listened on and authenticated by the current server.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string An empty string indicates that no information about the fourteenth node is configured.
+
+**Default value**: empty
+
+## replconninfo15
+
+**Parameter description**: Specifies the information about the fifteenth node to be listened on and authenticated by the current server.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string An empty string indicates that no information about the fifteenth node is configured.
+
+**Default value**: empty
+
+## replconninfo16
+
+**Parameter description**: Specifies the information about the sixteenth node to be listened on and authenticated by the current server.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string An empty string indicates that no information about the sixteenth node is configured.
+
+**Default value**: empty
+
+## replconninfo17
+
+**Parameter description**: Specifies the information about the seventeenth node to be listened on and authenticated by the current server.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string An empty string indicates that no information about the seventeenth node is configured.
+
+**Default value**: empty
+
+## replconninfo18
+
+**Parameter description**: Specifies the information about the eighteenth node to be listened on and authenticated by the current server.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string An empty string indicates that no information about the eighteenth node is configured.
+
+**Default value**: empty
+
+## cross_cluster_replconninfo1
+
+**Parameter description**: Specifies the information about the first node to be listened on and authenticated by the current server across clusters.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string. An empty string indicates that no information about the first node is configured.
+
+**Default value**: empty
+
+## cross_cluster_replconninfo2
+
+**Parameter description**: Specifies the information about the second node to be listened on and authenticated by the current server across clusters.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string. An empty string indicates that no information about the second node is configured.
+
+**Default value**: empty
+
+## cross_cluster_replconninfo3
+
+**Parameter description**: Specifies the information about the third node to be listened on and authenticated by the current server across clusters.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string. An empty string indicates that no information about the third node is configured.
+
+**Default value**: empty
+
+## cross_cluster_replconninfo4
+
+**Parameter description**: Specifies the information about the fourth node to be listened on and authenticated by the current server across clusters.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string. An empty string indicates that no information about the fourth node is configured.
+
+**Default value**: empty
+
+## cross_cluster_replconninfo5
+
+**Parameter description**: Specifies the information about the fifth node to be listened on and authenticated by the current server across clusters.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string An empty string indicates that no information about the fifth node is configured.
+
+**Default value**: empty
+
+## cross_cluster_replconninfo6
+
+**Parameter description**: Specifies the information about the sixth node to be listened on and authenticated by the current server across clusters.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string. An empty string indicates that no information about the sixth node is configured.
+
+**Default value**: empty
+
+## cross_cluster_replconninfo7
+
+**Parameter description**: Specifies the information about the seventh node to be listened on and authenticated by the current server across clusters.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string. An empty string indicates that no information about the seventh node is configured.
+
+**Default value**: empty
+
+## cross_cluster_replconninfo8
+
+**Parameter description**: Specifies the information about the eighth node to be listened on and authenticated by the current server across clusters.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string. An empty string indicates that no information about the eighth node is configured.
+
+**Default value**: empty
+
+## available_zone
+
+**Parameter description**: Specifies the region where the local node is located.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string. An empty string indicates that no information about the node is configured.
+
+**Default value**: empty
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/7-ha-replication/2-primary-server.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/7-ha-replication/2-primary-server.md
new file mode 100644
index 0000000000000000000000000000000000000000..b93fa380e3d0bec5db29a54f07afa03d1a66a77a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/7-ha-replication/2-primary-server.md
@@ -0,0 +1,210 @@
+---
+title: Primary Server
+summary: Primary Server
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Primary Server
+
+## synchronous_standby_names
+
+**Parameter description**: Specifies a comma-separated list of names of potential standby servers that support synchronous replication.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - The current synchronous standby server is on the top of the list. If the current synchronous standby server is disconnected, it will be replaced immediately with the next-highest-priority standby server. Name of the next-highest-priority standby server is added to the list.
+> - The standby server name can be specified by setting the environment variable **PGAPPNAME**.
+
+**Value range**: a string. If this parameter is set to *****, the name of any standby server that provides synchronous replication is matched. The value can be configured in the following format:
+
+- ANY *num_sync* (*standby_name* [, …])
+
+- [FIRST] *num_sync* (*standby_name* [, …])
+
+- *standby_name* [, …]
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > - In the preceding command, *num_sync* indicates the number of standby nodes that need to wait for responses from the transaction, *standby_name* indicates the name of the standby node, and FIRST and ANY specify the policies for selecting standby nodes for synchronous replication from the listed servers.
+  > - **ANY N (dn_instanceId1, dn_instanceId2,…)** indicates that any *N* host names in the brackets are selected as the name list of standby nodes for synchronous replication. For example, ANY 1(dn_instanceId1, dn_instanceId2) indicates that any one of dn_instanceId1 and dn_instanceId2 is used as the standby node for synchronous replication.
+  > - FIRST N (dn_instanceId1, dn_instanceId2, …) indicates that the first N primary node names in the brackets are selected as the standby node name list for synchronous replication based on the priority. For example, FIRST 1 (dn_instanceId1, dn_instanceId2) indicates that dn_instanceId1 is selected as the standby node for synchronous replication. - The meanings of dn_instanceId1, dn_instanceId2, … are the same as those of FIRST 1 (dn_instanceId1, dn_instanceId2, …).
+
+If you use the gs_guc tool to set this parameter, perform the following operations:
+
+```
+gs_guc reload -Z datanode -N @NODE_NAME@ -D @DN_PATH@ -c "synchronous_standby_names='ANY NODE 1(dn_instanceId1, dn_instanceId2)'";
+```
+
+or
+
+```
+gs_guc reload -Z datanode -N @NODE_NAME@ -D @DN_PATH@ -c "synchronous_standby_names='ANY 1(AZ1, AZ2)'";
+```
+
+**Default value**: *****
+
+## most_available_sync
+
+**Parameter description**: Specifies whether to block the primary server when the primary-standby synchronization fails.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the primary server is not blocked when the synchronization fails.
+- **off** indicates that the primary server is blocked when the synchronization fails.
+
+**Default value**: **off**
+
+## enable_stream_replication
+
+**Parameter description**: Specifies whether data and logs are synchronized between primary and standby servers, and between primary and secondary servers.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - This parameter is used for performance testing in scenarios where data synchronization to standby server is enabled and where it is disabled. If this parameter is set to **off**, tests on abnormal scenarios, such as switchover and faults, cannot be performed to prevent inconsistency between the primary, standby, and secondary servers.
+> - This parameter is a restricted parameter, and you are advised not to set it to **off** in normal service scenarios.
+
+**Value range**: Boolean
+
+- **on** indicates that data and log synchronization is enabled.
+- **off** indicates that data and log synchronization is disabled.
+
+**Default value**: **on**
+
+## enable_mix_replication
+
+**Parameter description**: Specifies how WAL files and data are replicated between primary and standby servers, and between primary and secondary servers.
+
+This parameter is an INTERNAL parameter. Its default value is **off** and cannot be modified.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> This parameter cannot be modified in normal service scenarios. That is, the WAL file and data page mixed replication mode is disabled.
+
+**Value range**: Boolean
+
+- **on** indicates that the WAL file and data page mixed replication mode is enabled.
+- **off** indicates that the WAL file and data page mixed replication mode is disabled.
+
+**Default value**: **off**
+
+## vacuum_defer_cleanup_age
+
+**Parameter description**: Specifies the number of transactions by which **VACUUM** will defer the cleanup of invalid row-store table records, so that **VACUUM** and **VACUUM FULL** do not clean up deleted tuples immediately.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 1000000. **0** means no delay.
+
+**Default value**: **0**
+
+## data_replicate_buffer_size
+
+**Parameter description**: Specifies the amount of memory used by queues when the sender sends data pages to the receiver. The value of this parameter affects the buffer size used during the replication from the primary server to the standby server.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 4096 to 1072693248. The unit is KB.
+
+**Default value**: **16MB** (16448 KB)
+
+## walsender_max_send_size
+
+**Parameter description**: Specifies the size of the WAL or Sender buffers on the primary server.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 8 to *INT_MAX*. The unit is KB.
+
+**Default value**: **8MB** (8192 KB)
+
+## enable_data_replicate
+
+**Parameter description**: Specifies how data is synchronized between primary and standby servers when the data is imported to a row-store table.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the primary and standby servers synchronize data using data pages when the data is imported to a row-store table. When **replication_type** is set to **1**, this parameter cannot be set to **on**. If this parameter is set to **on** using the GUC tool, its value will be forcibly changed to **off**.
+- **off** indicates that the primary and standby servers synchronize data using Xlogs when the data is imported to a row-store table.
+
+**Default value**: **off**
+
+## ha_module_debug
+
+**Parameter description**: Specifies the replication status log of a specific data block during data replication.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the status of each data block is recorded in logs during data replication.
+- **off** indicates that the status of each data block is not recorded in logs during data replication.
+
+**Default value**: **off**
+
+## enable_incremental_catchup
+
+**Parameter description**: Specifies the data catchup mode between the primary and standby servers.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the standby server uses the incremental catchup mode. That is, the standby server scans local data files on the standby server to obtain the list of differential data files between the primary and standby servers and then performs catchup between the primary and standby servers.
+- **off** indicates that the standby server uses the full catchup mode. That is, the standby server scans all local data files on the primary server to obtain the list of differential data files between the primary and standby servers and performs catchup between the primary and standby servers.
+
+**Default value**: **on**
+
+## wait_dummy_time
+
+**Parameter description**: Specifies the maximum duration for the primary server to wait for the standby and secondary servers to start and send the scanning lists when incremental data catchup is enabled in MogDB.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1 to *INT_MAX*. The unit is second.
+
+**Default value**: **300**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> The unit can only be second.
+
+## catchup2normal_wait_time
+
+**Parameter description**: Specifies the maximum duration that the primary server is blocked during the data catchup on the standby server in the case of a single synchronous standby server.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from -1 to 10000. The unit is ms.
+
+- The value **-1** indicates that the primary server is blocked until the data catchup on the standby server is complete.
+- The value **0** indicates that the primary server is not blocked during the data catchup on the standby server.
+- Other values indicate the maximum duration that the primary server is blocked during the data catchup on the standby server. For example, if this parameter is set to **5000**, the primary server is blocked until the data catchup on the standby server is complete in 5s.
+
+**Default value**: **-1**
+
+## sync_config_strategy
+
+**Parameter description**: Specifies the strategy for synchronizing configuration files between the primary and standby servers, and the standby and cascaded standby servers.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: enumerated values
+
+- **all_node**: If this parameter is set to **all_node** on a primary server, configuration files on the primary server can be automatically synchronized to all standby servers. If this parameter is set to **all_node** on a standby server, the current standby server is allowed to send a synchronization request to the primary server and configuration files on the current standby server can be automatically synchronized to all cascaded standby servers. If this parameter is set to **all_node** on a cascaded standby server, the current cascaded standby server is allowed to send a synchronization request to its standby server.
+- **only_sync_node**: If this parameter is set to **only_sync_node** on a primary server, configuration files on the primary server can be automatically synchronized to only all standby servers. If this parameter is set to **only_sync_node** on a standby server, the current standby server is allowed to send a synchronization request to the primary server and configuration files on the current standby server cannot be automatically synchronized to all cascaded standby servers. If this parameter is set to **only_sync_node** on a cascaded standby server, the current cascaded standby server is allowed to send a synchronization request to its standby server.
+- **none_node**: If this parameter is set to **none_node** on a primary server, configuration files on the primary server cannot be automatically synchronized to only all standby servers. If this parameter is set to **none_node** on a standby server, the current standby server is not allowed to send a synchronization request to the primary server and configuration files on the current standby server cannot be automatically synchronized to all cascaded standby servers. If this parameter is set to **none_node** on a cascaded standby server, the current cascaded standby server is not allowed to send a synchronization request to its standby server.
+
+**Default value**: **all_node**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> That the sender initiatively synchronizes the configuration file to the receiver and the receiver requests the sender to synchronize the configuration file is two separate events. Both of them will trigger configuration file synchronization. If you do not want to synchronize the configuration file, you need to configure the receiver as **none_node**. If the sender is a standby server, it can only be configured as **none_node**. If the sender is a primary server and configured as **none_node**, it will not synchronize with all the standby servers. If the sender is a primary server and configured as **only_sync_node**, it will synchronize with the standby servers and not synchronize with the asynchronous standby servers.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/7-ha-replication/3-standby-server.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/7-ha-replication/3-standby-server.md
new file mode 100644
index 0000000000000000000000000000000000000000..29ddad03c8b1e5d6e296c457077ba9eac0523e4e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/7-ha-replication/3-standby-server.md
@@ -0,0 +1,133 @@
+---
+title: Standby Server
+summary: Standby Server
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Standby Server
+
+## hot_standby
+
+**Parameter description**: Specifies whether to allow connections and queries on a standby server during its recovery.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - If this parameter is set to **on**, **wal_level** must be set to **hot_standby**. Otherwise, the database startup fails.
+> - In an HA system, **hot_standby** cannot be set to **off**, because this setting can affect other features of the HA system.
+
+**Value range**: Boolean
+
+- **on** indicates that connections and queries are allowed on the standby server during the recovery.
+- **off** indicates that connections and queries are not allowed on the standby server during the recovery.
+
+**Default value**: **on**
+
+## max_standby_archive_delay
+
+**Parameter description**: Specifies the wait period before queries on a standby server are canceled when the queries conflict with WAL processing and archiving in hot standby mode.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> **-1** indicates that the standby server waits until the conflicting queries are complete.
+
+**Value range**: an integer ranging from -1 to *INT_MAX*. The unit is ms.
+
+**Default value**: **3s** (3000 ms)
+
+## max_standby_streaming_delay
+
+**Parameter description**: Specifies the wait period before queries on a standby server are canceled when the queries conflict with WAL data receiving through streaming replication in hot standby mode.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> **-1** indicates that the standby server waits until the conflicting queries are complete.
+
+**Value range**: an integer ranging from -1 to *INT_MAX*. The unit is ms.
+
+**Default value**: **3s** (3000 ms)
+
+## wal_receiver_status_interval
+
+**Parameter description**: Specifies the maximum interval for notifying the primary server of the WAL Receiver status.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to *INT_MAX*. The unit is ms.
+
+**Default value**: **5s** (5000 ms)
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** If this parameter is set to **0**, the standby server does not send information, such as the log receiving location, to the primary server. As a result, the transaction commit on the primary server may be blocked, and the switchover may fail. In normal service scenarios, you are not advised to set this parameter to **0**.
+
+## hot_standby_feedback
+
+**Parameter description**: Specifies whether a standby server is allowed to send the result of a query performed on it to the primary server, preventing a query conflict.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the ID of the oldest transaction active on standby servers will be sent to the primary server.
+- **off** indicates that the ID of the oldest transaction active on standby servers will not be sent to the primary server.
+
+**Default value**: **off**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> If this parameter is set to **on**, VACUUM on the primary server will not clean up tuples modified in transactions later than the oldest transaction active on standby servers. Therefore, the performance of the primary server will be affected.
+
+## wal_receiver_timeout
+
+**Parameter description:** Specifies the maximum wait period for a standby server to receive data from the primary server.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to *INT_MAX*. The unit is ms.
+
+**Default value**: **6s** (6000 ms)
+
+## wal_receiver_connect_timeout
+
+**Parameter description**: Specifies the timeout period for a standby server to connect to the primary server.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to *INT_MAX*/1000. The unit is s.
+
+**Default value**: **2s**
+
+## wal_receiver_connect_retries
+
+**Parameter description**: Specifies the maximum attempts that a standby server connects to the primary server
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1 to *INT_MAX*
+
+**Default value**: **1**
+
+## wal_receiver_buffer_size
+
+**Parameter description**: Specifies the memory buffer size for the standby and secondary servers to store the received Xlog files.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 4096 to 1047552. The unit is KB.
+
+**Default value**: **64MB** (65536 KB)
+
+## primary_slotname
+
+**Parameter description**: Specifies the slot name of the primary server corresponding to a standby server. This parameter is used for the mechanisms to verify the primary-standby relationship and delete WALs.
+
+This parameter is a SIGHUP parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string
+
+**Default value**: empty
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/8-mot.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/8-mot.md
new file mode 100644
index 0000000000000000000000000000000000000000..d020dfda3fd1b8bd70caa351eeada15bb6e7d848
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/8-mot.md
@@ -0,0 +1,73 @@
+---
+title: Memory Table
+summary: Memory Table
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Memory Table
+
+This section describes the parameters in the memory table.
+
+## enable_codegen_mot
+
+**Parameter description**: Specifies whether to enable the native LLVM Lite to perform simple queries. If native LLVM is not supported on the current platform, pseudo LLVM will be used.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+**Default value**: **true**
+
+## force_pseudo_codegen_mot
+
+**Parameter description**: Specifies whether to force pseudo LLVM Lite to perform simple queries, even if the current platform supports native LLVM.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+**Default value**: **true**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> Even if **force_pseudo_codegen_mot** is set to **true**, the current platform does not support the native LLVM. In this case, the pseudo LLVM is still used.
+
+## enable_codegen_mot_print
+
+**Parameter description**: Specifies whether to print the IR byte code of the generation function. (If pseudo LLVM is used, the pseudo IR byte code is printed.)
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+**Default value**: **true**
+
+## codegen_mot_limit
+
+**Parameter description**: Specifies the maximum number of global cache plan sources and the clone plan of each session.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range:** uint32
+
+**Default value**: **100**
+
+## mot_allow_index_on_nullable_column
+
+**Parameter description**: Specifies whether indexes can be created on the **nullable** column in the memory table.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+**Default value**: **true**
+
+## mot_config_file
+
+**Parameter description**: Specifies the main configuration file of the MOT.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string
+
+**Default value**: **NULL**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/1-optimizer-method-configuration.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/1-optimizer-method-configuration.md
new file mode 100644
index 0000000000000000000000000000000000000000..356bd29cbce08813d17b4f7294eb92be35849a48
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/1-optimizer-method-configuration.md
@@ -0,0 +1,317 @@
+---
+title: Optimizer Method Configuration
+summary: Optimizer Method Configuration
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Optimizer Method Configuration
+
+These configuration parameters provide a crude method of influencing the query plans chosen by the query optimizer. If the default plan chosen by the optimizer for a particular query is not optimal, a temporary solution is to use one of these configuration parameters to force the optimizer to choose a different plan. Better ways include adjusting the optimizer cost constants, manually running **ANALYZE**, increasing the value of the **default_statistics_target** configuration parameter, and increasing the amount of the statistics collected in specific columns using **ALTER TABLE SET STATISTICS**.
+
+## enable_bitmapscan
+
+**Parameter description**: Controls the query optimizer's use of bitmap-scan plan types.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the query optimizer's use of bitmap-scan plan types is enabled.
+- **off** indicates that the query optimizer's use of bitmap-scan plan types is disabled.
+
+**Default value**: **on**
+
+## force_bitmapand
+
+**Parameter description**: Controls the query optimizer's use of BitmapAnd plan types.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the query optimizer's use of BitmapAnd plan types is enabled.
+- **off** indicates that the query optimizer's use of BitmapAnd plan types is disabled.
+
+**Default value**: **off**
+
+## enable_hashagg
+
+**Parameter description**: Controls the query optimizer's use of Hash aggregation plan types.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the query optimizer's use of Hash aggregation plan types is enabled.
+- **off** indicates that the query optimizer's use of Hash aggregation plan types is disabled.
+
+**Default value**: **on**
+
+## enable_hashjoin
+
+**Parameter description**: Controls the query optimizer's use of Hash-join plan types.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the query optimizer's use of Hash-join plan types is enabled.
+- **off** indicates that the query optimizer's use of Hash-join plan types is disabled.
+
+**Default value**: **on**
+
+## enable_indexscan
+
+**Parameter description**: Controls the query optimizer's use of index-scan plan types.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the query optimizer's use of index-scan plan types is enabled.
+- **off** indicates that the query optimizer's use of index-scan plan types is disabled.
+
+**Default value**: **on**
+
+## enable_indexonlyscan
+
+**Parameter description**: Controls the query optimizer's use of index-only-scan plan types.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the query optimizer's use of index-only-scan plan types is enabled.
+- **off** indicates that the query optimizer's use of index-only-scan plan types is disabled.
+
+**Default value**: **on**
+
+## enable_material
+
+**Parameter description**: Controls the query optimizer's use of materialization. It is impossible to suppress materialization entirely, but setting this variable to **off** prevents the optimizer from inserting materialized nodes.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the query optimizer's use of materialization is enabled.
+- **off** indicates that the query optimizer's use of materialization is disabled.
+
+**Default value**: **on**
+
+## enable_mergejoin
+
+**Parameter description**: Controls the query optimizer's use of merge-join plan types.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the query optimizer's use of merge-join plan types is enabled.
+- **off** indicates that the query optimizer's use of merge-join plan types is disabled.
+
+**Default value**: **off**
+
+## enable_nestloop
+
+**Parameter description**: Controls the query optimizer's use of nested-loop join plan types to fully scan internal tables. It is impossible to suppress nested-loop joins entirely, but setting this variable to **off** encourages the optimizer to choose other methods if available.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the query optimizer's use of nested-loop join plan types is enabled.
+- **off** indicates that the query optimizer's use of nested-loop join plan types is disabled.
+
+**Default value**: **off**
+
+## enable_index_nestloop
+
+**Parameter description**: Controls the query optimizer's use of the nested-loop join plan types to scan the parameterized indexes of internal tables.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the query optimizer's use of nested-loop join plan types is enabled.
+- **off** indicates that the query optimizer's use of nested-loop join plan types is disabled.
+
+**Default value**: **on**
+
+## enable_seqscan
+
+**Parameter description**: Controls the query optimizer's use of sequential scan plan types. It is impossible to suppress sequential scans entirely, but setting this variable to **off** encourages the optimizer to choose other methods if available.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the query optimizer's use of sequential scan plan types is enabled.
+- **off** indicates that the query optimizer's use of sequential scan plan types is disabled.
+
+**Default value**: **on**
+
+## enable_sort
+
+**Parameter description**: Controls the query optimizer's use of sort methods. It is impossible to suppress explicit sorts entirely, but setting this variable to **off** encourages the optimizer to choose other methods if available.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the query optimizer's use of sort methods is enabled.
+- **off** indicates that the query optimizer's use of sort methods is disabled.
+
+**Default value**: **on**
+
+## enable_tidscan
+
+**Parameter description**: Controls the query optimizer's use of Tuple ID (TID) scan plan types.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the query optimizer's use of TID scan plan types is enabled.
+- **off** indicates that the query optimizer's use of TID scan plan types is disabled.
+
+**Default value**: **on**
+
+## enable_kill_query
+
+**Parameter description**: In CASCADE mode, when a user is deleted, all the objects belonging to the user are deleted. This parameter specifies whether the queries of the objects belonging to the user can be unlocked when the user is deleted.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the unlocking is allowed.
+- **off** indicates that the unlocking is not allowed.
+
+**Default value**: **off**
+
+## enforce_a_behavior
+
+**Parameter description**: Controls the rule matching modes of regular expressions.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the O matching rule is used.
+- **off** indicates that the POSIX matching rule is used.
+
+**Default value**: **on**
+
+## max_recursive_times
+
+**Parameter description**: Specifies the maximum number of **WITH RECURSIVE** iterations.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to *INT_MAX*
+
+**Default value**: **200**
+
+## enable_vector_engine
+
+**Parameter description**: Controls the query optimizer's use of vectorized executor.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates the query optimizer's use of vectorized executor is enabled.
+- **off** indicates the query optimizer's use of vectorized executor is disabled.
+
+**Default value**: **on**
+
+## enable_change_hjcost
+
+**Parameter description**: Specifies whether the optimizer excludes internal table running costs when selecting the Hash Join cost path. If it is set to **on**, tables with a few records and high running costs are more possible to be selected.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the internal table running costs will be excluded.
+- **off** indicates that the internal table running costs will not be excluded.
+
+**Default value**: **off**
+
+## enable_absolute_tablespace
+
+**Parameter description**: Controls whether the tablespace can use an absolute path.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that an absolute path can be used.
+- **off** indicates that an absolute path cannot be used.
+
+**Default value**: **on**
+
+## enable_valuepartition_pruning
+
+**Parameter description**: Specifies whether the DFS partitioned table is dynamically or statically optimized.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the DFS partitioned table is dynamically or statically optimized.
+- **off** indicates that the DFS partitioned table is not dynamically or statically optimized.
+
+**Default value**: **on**
+
+## qrw_inlist2join_optmode
+
+**Parameter description**: Specifies whether to enable inlist-to-join (inlist2join) query rewriting.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string
+
+- **disable** indicates that the inlist2join query rewriting is disabled.
+- **cost_base** indicates that the cost-based inlist2join query rewriting is enabled.
+- **rule_base** indicates that the forcible rule-based inlist2join query rewriting is enabled.
+- A positive integer indicates the threshold of inlist2join query rewriting. If the number of elements in the list is greater than the threshold, the rewriting is performed.
+
+**Default value**: **cost_base**
+
+## skew_option
+
+**Parameter description**: Specifies whether an optimization policy is used.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string
+
+- **off** indicates that the policy is disabled.
+- **normal** indicates that a radical policy is used. All possible skews are optimized.
+- **lazy** indicates that a conservative policy is used. Uncertain skews are ignored.
+
+**Default value**: **normal**
+
+## default_limit_rows
+
+**Parameter description**: Specifies the default estimated number of limit rows for generating genericplan. If this parameter is set to a positive value, the positive value is used as the estimated number of limit rows. If this parameter is set to a negative value, the negative value is converted to a percentage and used as default estimated value, that is, -5 indicates 5%.
+
+**Value range**: a floating point number ranging from -100 to DBL_MAX
+
+**Default value**: **-10**
+
+## check_implicit_conversions
+
+**Parameter description**: Specifies whether to check candidate index paths generated for index columns that have implicit type conversions in a query.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that a check will be performed for candidate index paths generated for index columns that have implicit type conversion in a query.
+- **off** indicates that a check will not be performed.
+
+**Default value**: **off**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/2-optimizer-cost-constants.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/2-optimizer-cost-constants.md
new file mode 100644
index 0000000000000000000000000000000000000000..85360729ccacbb54aaf40daf1b6f1f39cc48b096
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/2-optimizer-cost-constants.md
@@ -0,0 +1,94 @@
+---
+title: Optimizer Cost Constants
+summary: Optimizer Cost Constants
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Optimizer Cost Constants
+
+This section describes the optimizer cost constants. The cost variables described here are measured on an arbitrary scale. Only their relative values matter, therefore scaling them all up or down by the same factor will result in no change in the optimizer's choices. By default, these cost variables are based on the cost of sequential page fetches, that is, **seq_page_cost** is conventionally set to **1.0** and the other cost variables are set with reference to the parameter. However, you can use a different scale, such as actual execution time in milliseconds.
+
+## seq_page_cost
+
+**Parameter description**: Specifies the optimizer's estimated cost of a disk page fetch that is part of a series of sequential fetches.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a floating point number ranging from 0 to *DBL_MAX*
+
+**Default value**: **1**
+
+## random_page_cost
+
+**Parameter description**: Specifies the optimizer's estimated cost of an out-of-sequence disk page fetch.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> Although the server allows you to set **random_page_cost** to a value less than that of **seq_page_cost**, it is not physically sensitive to do so. However, setting them equal makes sense if the database is entirely cached in RAM, because in that case there is no penalty for fetching pages out of sequence. Also, in a heavily-cached database you should lower both values relative to the CPU parameters, since the cost of fetching a page already in RAM is much smaller than it would normally be.
+
+**Value range**: a floating point number ranging from 0 to *DBL_MAX*
+
+**Default value**: **4**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - This value can be overwritten for tables and indexes in a particular tablespace by setting the tablespace parameter of the same name.
+> - Reducing this value relative to **seq_page_cost** will cause the system to prefer index scans and raising it will make index scans relatively more expensive. You can increase or decrease both values together to change the disk I/O costs relative to CPU costs.
+
+## cpu_tuple_cost
+
+**Parameter description**: Specifies the optimizer's estimated cost of processing each row during a query.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a floating point number ranging from 0 to *DBL_MAX*
+
+**Default value**: **0.01**
+
+## cpu_index_tuple_cost
+
+**Parameter description**: Specifies the optimizer's estimated cost of processing each index entry during an index scan.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a floating point number ranging from 0 to *DBL_MAX*
+
+**Default value:** **0.005**
+
+## cpu_operator_cost
+
+**Parameter description**: Specifies the optimizer's estimated cost of processing each operator or function executed during a query.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a floating point number ranging from 0 to *DBL_MAX*
+
+**Default value**: **0.0025**
+
+## effective_cache_size
+
+**Parameter description**: Specifies the optimizer's assumption about the effective size of the disk cache that is available to a single query.
+
+When setting this parameter you should consider both MogDB's shared buffers and the kernel's disk cache. Also, take into account the expected number of concurrent queries on different tables, since they will have to share the available space.
+
+This parameter has no effect on the size of shared memory allocated by MogDB. It is used only for estimation purposes and does not reserve kernel disk cache. The value is in the unit of disk page. Usually the size of each page is 8192 bytes.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1 to *INT_MAX*. The unit is 8 KB.
+
+A value greater than the default one makes index scans more likely to be used, whereas a value less than the default one makes sequential scans more likely to be used.
+
+**Default value**: **128MB**
+
+## allocate_mem_cost
+
+**Parameter description**: Specifies the query optimizer's estimated cost of creating a hash table for memory space using hash join. This parameter is used for optimization when the hash join estimation is inaccurate.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a floating point number ranging from 0 to *DBL_MAX*
+
+**Default value**: **0**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/3-genetic-query-optimizer.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/3-genetic-query-optimizer.md
new file mode 100644
index 0000000000000000000000000000000000000000..5af0f4bad61822d308bb0702cad41d56634761b7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/3-genetic-query-optimizer.md
@@ -0,0 +1,106 @@
+---
+title: Genetic Query Optimizer
+summary: Genetic Query Optimizer
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Genetic Query Optimizer
+
+This section describes parameters related to genetic query optimizer. The genetic query optimizer (GEQO) is an algorithm that plans queries by using heuristic searching. This algorithm reduces planning time for complex queries and the costs of producing plans are sometimes inferior to those found by the normal exhaustive-search algorithm.
+
+## geqo
+
+**Parameter description**: Specifies whether to enable the genetic query optimization.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> It is best not to turn it off in execution. **geqo_threshold** provides more subtle control of GEQO.
+
+**Value range**: Boolean
+
+- **on** indicates that the genetic query optimization is enabled.
+- **off** indicates that the genetic query optimization is disabled.
+
+**Default value**: **on**
+
+## geqo_threshold
+
+**Parameter description**: Specifies the number of **FROM** items. Genetic query optimization is used to plan queries when the number of statements executed is greater than this value.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - For simpler queries it is best to use the regular, exhaustive-search planner, but for queries with many tables it is better to use GEQO to manage the queries.
+> - A **FULL OUTER JOIN** construct counts as only one **FROM** item.
+
+**Value range**: an integer ranging from 2 to *INT_MAX*
+
+**Default value**: **12**
+
+## geqo_effort
+
+**Parameter description**: Controls the trade-off between planning time and query plan quality in GEQO.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> **geqo_effort** does not do anything directly. This parameter is only used to compute the default values for the other variables that influence GEQO behavior. If you prefer, you can manually set the other parameters instead.
+
+**Value range**: an integer ranging from 1 to 10
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> Larger values increase the time spent in query planning, but also increase the probability that an efficient query plan is chosen.
+
+**Default value**: **5**
+
+## geqo_pool_size
+
+**Parameter description**: Controls the pool size used by GEQO, that is, the number of individuals in the genetic population.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to *INT_MAX*
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> The value of this parameter must be at least **2**, and useful values are typically from **100** to **1000**. If this parameter is set to **0**, MogDB selects a proper value based on **geqo_effort** and the number of tables.
+
+**Default value**: **0**
+
+## geqo_generations
+
+**Parameter description**: Specifies the number of iterations of the GEQO.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to *INT_MAX*
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> The value of this parameter must be at least **1**, and useful values are typically from **100** to **1000**. If it is set to **0**, a suitable value is chosen based on **geqo_pool_size**.
+
+**Default value**: **0**
+
+## geqo_selection_bias
+
+**Parameter description**: Specifies the selection bias used by GEQO. The selection bias is the selective pressure within the population.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range:** a floating point number ranging from 1.5 to 2.0
+
+**Default value**: **2**
+
+## geqo_seed
+
+**Parameter description**: Specifies the initial value of the random number generator used by GEQO to select random paths through the join order search space.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range:** a floating point number ranging from 0.0 to 1.0
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> Varying the value changes the set of join paths explored, and may result in a better or worse best path being found.
+
+**Default value**: **0**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/4-other-optimizer-options.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/4-other-optimizer-options.md
new file mode 100644
index 0000000000000000000000000000000000000000..3e078f80765b9f603eab8ecd8bf132983e1135ed
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/4-other-optimizer-options.md
@@ -0,0 +1,685 @@
+---
+title: Other Optimizer Options
+summary: Other Optimizer Options
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Other Optimizer Options
+
+## explain_dna_file
+
+**Parameter description:** Sets explain_perf_mode to **run** to export object files in CSV format.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** The value of this parameter must be an absolute path plus a file name with the extension **.csv**.
+
+**Value range**: a string
+
+**Default value**: empty
+
+## explain_perf_mode
+
+**Parameter description:** Specifies the display format of the **explain** command.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range:** **normal**, **pretty**, **summary**, and **run**
+
+- **normal** indicates that the default printing format is used.
+- **pretty** indicates a new format improved by using . The new format contains a plan node ID, directly and effectively analyzing performance.
+- **summary** indicates that the analysis result on this information is printed in addition to the printed information specified by **pretty**.
+- **run** indicates that the system exports the printed information specified by **summary** as a CSV file for further analysis.
+
+**Default value**: **pretty** (In the current version, only the value **normal** takes effect. If the value is not **normal**, **normal** is still displayed.)
+
+## analysis_options
+
+**Parameter description**: Specifies whether to enable function options in the corresponding options to use the corresponding location functions, including data verification and performance statistics. For details, see the options in the value range.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix). Use 'on()' or 'off()' to enable or disable a function. If a function is not specified, its value remains unchanged. The reference format is 'on(option1, option2, …)'.
+
+**Value range**: a string
+
+- **LLVM_COMPILE** indicates that the codegen compilation time of each thread is displayed on the explain performance page.
+- **HASH_CONFLICT** indicates that the log file in the **pg_log** directory of the database node process displays the hash table statistics, including the hash table size, hash chain length, and hash conflict information.
+- **STREAM_DATA_CHECK** indicates that a CRC check is performed on data before and after network data transmission.
+
+**Default value**: **ALL,on(),off(LLVM_COMPILE,HASH_CONFLICT,STREAM_DATA_CHECK)**, which indicates that no location function is enabled.
+
+## cost_param
+
+**Parameter description:** Controls use of different estimation methods in specific customer scenarios, allowing estimated values approximating to onsite values. This parameter can control various methods simultaneously by performing AND (&) on the bit of each method. A method is selected if the result value is not **0**.
+
+When **cost_param & 1** is set to a value other than 0, an improved mechanism is used for connecting the selection rate of non-equi-joins. This method is more accurate for estimating the selection rate of joins between two identical tables. At present, **cost_param & 1=0** is not used. That is, a better formula is selected for calculation.
+
+When **cost_param & 2** is set to a value other than **0**, the selection rate is estimated based on multiple filter criteria. The lowest selection rate among all filter criteria, but not the product of the selection rates for two tables under a specific filter criterion, is used as the total selection rate. This method is more accurate when a close correlation exists between the columns to be filtered.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to *INT_MAX*
+
+**Default value**: **0**
+
+## enable_partitionwise
+
+**Parameter description:** Specifies whether to select an intelligent algorithm for joining partition tables.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that an intelligent algorithm is selected.
+- **off** indicates that an intelligent algorithm is not selected.
+
+**Default value**: **off**
+
+## rewrite_rule
+
+**Parameter description**: Specifies the rewriting rule for enabled optional queries. Some query rewrite rules are optional. Enabling them cannot always improve the query efficiency. In a specific customer scenario, you can set the query rewriting rules through this GUC parameter to achieve optimal query efficiency.
+
+This parameter can control the combination of query rewriting rules, for example, there are over one override rules: rule1, rule2, rule3, and rule4. You can perform the following settings:
+
+```sql
+set rewrite_rule=rule1;          -- Enable query rewriting rule rule1
+set rewrite_rule=rule2, rule3;     -- Enable the query rewriting rules rule2 and rule3
+set rewrite_rule=none;         -- Disable all optional query rewriting rules
+```
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string
+
+- none: Does not use any optional query rewriting rules
+- Lazyagg: Uses the Lazy Agg query rewriting rules for eliminating aggregation operations in subqueries
+- magicset: Uses the Magic Set query rewriting rules delivered from the main query to the subquery.
+- **partialpush**: Use Partial Push to query rewriting rules.
+- **uniquecheck**: Uses the Unique Check query rewriting rules. Optimize the subquery statements in target columns without agg and check whether the number of returned rows is 1.
+- **disablerep**: Use Disable Replicate to query the rewriting rule.
+- **intargetlist**: Uses the In Target List query rewriting rules (subquery optimization in the target column).
+- **predpushnormal**: Use the Predicate Push query rewriting rule (push the predicate condition to the subquery).
+- **predpushforce**: Uses the Predicate Push query rewriting rules. Push down predicate conditions to subqueries and use indexes as much as possible for acceleration.
+- **predpush**: Selects the optimal plan based on the cost in **predpushnormal** and **predpushforce**.
+
+**Default value**: **magicset**
+
+## enable_pbe_optimization
+
+**Parameter description**: Specifies whether the optimizer optimizes the query plan for statements executed in Parse Bind Execute (PBE) mode.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the optimizer optimizes the query plan.
+- **off** indicates that the optimizer does not optimize the execution.
+
+**Default value**: **on**
+
+## enable_light_proxy
+
+**Parameter description**: Specifies whether the optimizer optimizes the execution of simple queries on the primary node of the databases. This parameter does not take effect if the character set of the application side does not match that of the kernel side. You are advised to set the character set to UTF8 when creating a database.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the optimizer optimizes the execution of simple queries on the primary node of the databases.
+- **off** indicates that the optimizer does not optimize the execution.
+
+**Default value**: **on**
+
+## enable_global_plancache
+
+**Parameter description**: Specifies whether to share the cache of the PBE query execution plan. Enabling this function can reduce the memory usage of database nodes in high concurrency scenarios.
+
+When **enable_global_plancache** is enabled, the default value of **local_syscache_threshold** is greater than or equal to 16 MB to ensure that GPC takes effect. If the value of **local_syscache_threshold** is less than 16 MB, set it to 16 MB. If the value is greater than 16 MB, do not change it.
+
+This parameter is a POSTMASTER parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the execution plan of the PBE query is shared in the cache.
+- **off** indicates that the execution plan of the PBE query is not shared in the cache.
+
+**Default value**: **off**
+
+## enable_global_stats
+
+**Parameter description**: Specifies the current statistics collection mode, which can be global statistics collection or single-node statistics collection. By default, the global statistics collection mode is used. If this parameter is set to **off**, the statistics of the first node in  are collected by default. In this case, the quality of the generated query plan may be affected. However, the information collection performance is optimal. Therefore, exercise caution when disabling this parameter.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** or **true** indicates the global statistics mode.
+- **off** or **false** indicates the database node statistics.
+
+**Default value**: **on**
+
+## enable_opfusion
+
+**Parameter description:** Specifies whether to optimize simple addition, deletion, modification, and query operations.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+The restrictions on simple query are as follows:
+
+- Only indexscan and indexonlyscan are supported, and the filter criteria of all WHERE statements are on indexes.
+
+- Only single tables can be added, deleted, modified, and queried. Join and using are not supported.
+
+- Only row-store tables are supported. Partitioned tables and tables with triggers are not supported.
+
+- Information statistics features such as active sql and QPS are not supported.
+
+- Tables that are being scaled out or in are not supported.
+
+- The system column cannot be queried or modified.
+
+- Only simple SELECT statements are supported. For example:
+
+  ```sql
+  SELECT c3 FROM t1 WHERE c1 = ? and c2 =10;
+  ```
+
+  Only columns in the target table can be queried. Columns c1 and c2 are index columns, which can be followed by constants or parameters. You can use for update.
+
+- Only simple INSERT statements are supported. For example:
+
+  ```sql
+  INSERT INTO t1 VALUES (?,10,?);
+  ```
+
+  Only one VALUES is supported. The type in the VALUES can be a constant or a parameter. Returning is not supported.
+
+- Only simple DELETE statements are supported. For example:
+
+  ```sql
+  DELETE FROM t1 WHERE c1 = ? and c2 = 10;
+  ```
+
+  Columns c1 and c2 are index columns, which can be followed by constants or parameters.
+
+- Only simple UPDATE statements are supported. For example:
+
+  ```sql
+  UPDATE t1 SET c3 = c3+? WHERE c1 = ? and c2 = 10;
+  ```
+
+  The values modified in column c3 can be constants, parameters, or a simple expression. Columns c1 and c2 are index columns, followed by constants or parameters.
+
+**Value range**: Boolean
+
+- **on** indicates that the performance logs are output.
+- **off** indicates that the performance logs are not output.
+
+**Default value**: **off**
+
+## enable_partition_opfusion
+
+**Parameter description:** If this parameter is enabled when the enable_opfusion parameter is enabled, the simple query of the partitioned table can be optimized to improve the SQL execution performance.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the performance logs are output.
+- **off** indicates that the performance logs are not output.
+
+**Default value**: **off**
+
+## sql_beta_feature
+
+**Parameter description**: Specifies the SQL engine's optional beta features to be enabled, including optimization of row count estimation and query equivalence estimation.
+
+These optional features provide optimization for specific scenarios, but performance deterioration may occur in some scenarios for which testing is not performed. In a specific customer scenario, you can set the query rewriting rules through this GUC parameter to achieve optimal query efficiency.
+
+This parameter determines the combination of the SQL engine's beta features, for example, feature1, feature2, feature3, and feature4. You can perform the following settings:
+
+```sql
+-- Enable beta feature feature1 of the SQL engine.
+set sql_beta_feature=feature1;
+-- Enable beta features feature2 and feature3 of the SQL engine.
+set sql_beta_feature=feature2,feature3;
+-- Disable all optional beta features of the SQL engine.
+set sql_beta_feature=none;
+```
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: a string
+
+- **none**: None of the beta optimizer features is used.
+- **sel_semi_poisson**: Uses poisson distribution to calibrate the equivalent semi-join and anti-join selection rates.
+- **sel_expr_instr**: Uses the matching row count estimation method to provide more accurate estimation for **instr(col, 'const') &gt; 0, = 0, = 1**.
+- **param_path_gen**: Generates more possible parameterized paths.
+- **rand_cost_opt**: Optimizes the random read cost of tables that have a small amount of data.
+- **param_path_opt**: Uses the bloat ratio of the table to optimize the analyze information of indexes.
+- **page_est_opt**: Optimizes the relpages estimation for the analyze information of non-column-store table indexes.
+- **no_unique_index_first**: Disables optimization of the primary key index scanning path first.
+- **join_sel_with_cast_func**: Type conversion functions are supported when the number of join rows is estimated.
+- **canonical_pathkey**: after regularization pathkey is generated. (**pathkey**: a set of ordered key values of data.)
+- **index_cost_with_leaf_pages_only**: Considers index leaf nodes when the index cost is estimated.
+- **partition_opfusion**: Enables partitioned table optimization.
+
+**Default value**: **none**
+
+## ngram_gram_size
+
+**Parameter description**: Specifies the length of the ngram parser segmentation.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1 to 4
+
+**Default value**: **2**
+
+## ngram_grapsymbol_ignore
+
+**Parameter description**: Specifies whether the ngram parser ignores graphical characters.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on**: The ngram parser ignores graphical characters.
+- **off**: The ngram parser does not ignore graphical characters.
+
+**Default value**: **off**
+
+## ngram_punctuation_ignore
+
+**Parameter description**: Specifies whether the ngram parser ignores punctuations.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on**: The ngram parser ignores punctuations.
+- **off**: The ngram parser does not ignore punctuations.
+
+**Default value**: **on**
+
+## default_statistics_target
+
+**Parameter description**: Specifies the default statistics target for table columns without a column-specific target set via **ALTER TABLE SET STATISTICS**. If this parameter is set to a positive number, it indicates the number of samples of statistics information. If this parameter is set to a negative number, percentage is used to set the statistic target. The negative number converts to its corresponding percentage, for example, -5 means 5%.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range:** an integer ranging from -100 to 10000
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - A larger positive number than the default value increases the time required to do **ANALYZE**, but might improve the quality of the optimizer's estimates.
+> - Changing settings of this parameter may result in performance deterioration. If query performance deteriorates, you can:
+>   1. Restore to the default statistics.
+>   2. Use hints to force the optimizer to use the optimal query plan. For details, see **Hint-based Tuning**.
+> - If this parameter is set to a negative value, the number of samples is greater than or equal to 2% of the total data volume, and the number of records in user tables is less than 1.6 million, the time taken by running **ANALYZE** will be longer than when this parameter uses its default value.
+> - If this parameter is set to a negative value, the auto-analyze function is disabled.
+
+**Default value**: **100**
+
+## constraint_exclusion
+
+**Parameter description**: Controls the query optimizer's use of table constraints to optimize queries.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: enumerated values
+
+- **on** indicates that constraints for all tables are examined.
+
+- **off** indicates that constraints for any table are not examined.
+
+- **partition** indicates that only constraints for inheritance child tables and **UNION ALL** subqueries are examined.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** When **constraint_exclusion** is set to **on**, the optimizer compares query conditions with the table's **CHECK** constraints, and omits scanning tables for which the conditions contradict the constraints.
+
+**Default value**: **partition**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** Currently, constraint exclusion is enabled by default only for cases that are often used to implement table partitioning. Turning this feature on for all tables imposes extra planning on simple queries, and provides no benefit for simple queries. If you have no partitioned tables, set it to **off**.
+
+## cursor_tuple_fraction
+
+**Parameter description**: Specifies the optimizer's estimated fraction of a cursor's rows that are retrieved.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range:** a floating point number ranging from 0.0 to 1.0
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** Smaller values of this setting bias the optimizer towards using **fast start** plans for cursors, which will retrieve the first few rows quickly while perhaps taking a long time to fetch all rows. Larger values put more emphasis on the total estimated time. At the maximum setting of **1.0**, cursors are planned exactly like regular queries, considering only the total estimated time and how soon the first rows might be delivered.
+
+**Default value**: **0.1**
+
+## from_collapse_limit
+
+**Parameter description**: Specifies whether the optimizer merges sub-queries into upper queries based on the resulting FROM list. The optimizer merges sub-queries into upper queries if the resulting FROM list would have no more than this many items.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1 to *INT_MAX*
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** Smaller values reduce planning time but may lead to inferior execution plans.
+
+**Default value**: **8**
+
+## join_collapse_limit
+
+**Parameter description**: Specifies whether the optimizer rewrites **JOIN** constructs (except **FULL JOIN**) into lists of **FROM** items based on the number of the items in the result list.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1 to *INT_MAX*
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - Setting this parameter to **1** prevents join reordering. As a result, the join order specified in the query will be the actual order in which the relations are joined. The query optimizer does not always choose the optimal join order. Therefore, advanced users can temporarily set this variable to **1**, and then specify the join order they desire explicitly.
+> - Smaller values reduce planning time but lead to inferior execution plans.
+
+**Default value**: **8**
+
+## plan_mode_seed
+
+**Parameter description**: This is a commissioning parameter. Currently, it supports only **OPTIMIZE_PLAN** and **RANDOM_PLAN**. The value **0** (for **OPTIMIZE_PLAN**) indicates the optimized plan using the dynamic planning algorithm. Other values are for **RANDOM_PLAN**, which indicates that the plan is randomly generated. **-1** indicates that users do not specify the value of the seed identifier. In this case, the optimizer generates a random integer from **1** to **2147483647** and a random execution plan based on the generated integer. A value from **1** to **2147483647** is regarded as the seed identifier, based on which the optimizer generates a random execution plan.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from -1 to 2147483647
+
+**Default value**: **0**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - If **plan_mode_seed** is set to **RANDOM_PLAN**, the optimizer generates a random execution plan that may not be the optimal one. Therefore, to guarantee the query performance, the default value **0** is recommended during upgrade, scale-out, scale-in, and O&M.
+> - If this parameter is not set to **0**, the specified hint will not be used.
+
+## hashagg_table_size
+
+**Parameter description**: Specifies the hash table size during the execution of the HASH JOIN operation.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to *INT_MAX*/2
+
+**Default value**: **0**
+
+## enable_codegen
+
+**Parameter description**: Specifies whether code optimization is enabled. Currently, the code optimization uses the LLVM optimization.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that code optimization is enabled.
+
+- **off** indicates that code optimization is disabled.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** Currently, the LLVM optimization only supports the vectorized executor and SQL on Hadoop features. You are advised to set this parameter to **off** in other cases.
+
+**Default value**: **off**
+
+## codegen_strategy
+
+**Parameter description**: Specifies the codegen optimization strategy that is used when an expression is converted to be codegen-based.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range:** enumerated values
+
+- **partial** indicates that even if functions that are not codegen-based exist in an expression, you can still call the LLVM dynamic optimization strategy by using the entire codegen framework of the expression.
+
+- **pure** indicates that only when all functions in an expression can be codegen-based, the LLVM dynamic optimization strategy can be called.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** In the scenario where query performance reduces after the codegen function is enabled, you can set this parameter to **pure**. In other scenarios, do not change the default value **partial** of this parameter.
+
+**Default value**: **partial**
+
+## enable_codegen_print
+
+**Parameter description**: Specifies whether the LLVM IR function can be printed in logs.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the LLVM IR function can be printed in logs.
+- **off** indicates that the LLVM IR function cannot be printed in logs.
+
+**Default value**: **off**
+
+## codegen_cost_threshold
+
+**Parameter description**: The LLVM compilation takes some time to generate executable machine code. Therefore, LLVM compilation is beneficial only when the actual execution cost is more than the sum of the code required for generating machine code and the optimized execution cost. This parameter specifies a threshold. If the estimated execution cost exceeds the threshold, LLVM optimization is performed.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 0 to 2147483647
+
+**Default value**: **10000**
+
+## enable_bloom_filter
+
+**Parameter description**: Specifies whether the BloomFilter optimization can be used. This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the BloomFilter optimization can be used.
+- **off** indicates that the BloomFilter optimization cannot be used.
+
+**Default value**: **on**
+
+## enable_extrapolation_stats
+
+**Parameter description**: Specifies whether the extrapolation logic is used for data of DATE type based on historical statistics. The logic can increase the accuracy of estimation for tables whose statistics are not collected in time, but will possibly provide an overlarge estimation due to incorrect extrapolation. Enable the logic only in scenarios where the data of DATE type is periodically inserted. This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the extrapolation logic is used for data of DATE type based on historical statistics.
+- **off** indicates that the extrapolation logic is not used for data of DATE type based on historical statistics.
+
+**Default value**: **off**
+
+## autoanalyze
+
+**Parameter description**: Specifies whether to automatically collect statistics on tables that have no statistics when a plan is generated. **autoanalyze** cannot be used for foreign or temporary tables. To collect statistics, manually perform the ANALYZE operation. If an exception occurs in the database during the execution of autoanalyze on a table, after the database is recovered, the system may still prompt you to collect the statistics of the table when you run the statement again. In this case, manually perform the ANALYZE operation on the table to synchronize statistics. This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the table statistics are automatically collected.
+- **off** indicates that the table statistics are not automatically collected.
+
+**Default value**: **off**
+
+## enable_analyze_check
+
+**Parameter description**: Checks whether statistics were collected about tables whose **reltuples** and **relpages** are displayed as **0** in **pg_class** during plan generation.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the tables will be checked.
+- **off** indicates that the tables will not be checked.
+
+**Default value**: **off**
+
+## enable_sonic_hashagg
+
+**Parameter description**: Specifies whether to use the hash aggregation operator designed for column-oriented hash tables when certain constraints are met.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the hash aggregation operator designed for column-oriented hash tables is used when certain constraints are met.
+- **off** indicates that the hash aggregation operator designed for column-oriented hash tables is not used.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - When the hash aggregation operator designed for column-oriented hash tables is used, the memory usage of the query can be reduced. However, in scenarios when enable_codegen is set to **on** and the performance is significantly improved, the performance of the operator may deteriorate.
+> - If **enable_sonic_hashagg** is set to **on**, when certain constraints are met, the hash aggregation operator designed for column-oriented hash tables is used and its name is displayed as **Sonic Hash Aggregation** in the output of the Explain Analyze/Performance operation. When the constraints are not met, the operator name is displayed as **Hash Aggregation**. For details, see **Description**.
+
+**Default value**: **on**
+
+## enable_sonic_hashjoin
+
+**Parameter description**: Specifies whether to use the hash join operator designed for column-oriented hash tables when certain constraints are met.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the hash join operator designed for column-oriented hash tables is used when certain constraints are met.
+- **off** indicates that the hash join operator designed for column-oriented hash tables is not used.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - Currently, the parameter can be used only for Inner Join.
+> - If **enable_sonic_hashjoin** is enabled, the memory usage of query using the Hash Inner operator can be reduced. However, in scenarios where the code generation technology can significantly improve performance, the performance of the operator may deteriorate.
+> - If **enable_sonic_hashjoin** is set to **on**, when certain constraints are met, the hash join operator designed for column-oriented hash tables is used and its name is displayed as **Sonic Hash Join** in the output of the Explain Analyze/Performance operation. When the constraints are not met, the operator name is displayed as **Hash Join**. For details, see **Description**.
+
+**Default value**: **on**
+
+## enable_sonic_optspill
+
+**Parameter description**: Specifies whether to optimize the number of files to be written to disks for the Hash Join operator designed for column-oriented hash tables. If this parameter is set to **on**, the number of files written to disks does not increase significantly when the Hash Join operator writes a large number of files to disks.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the optimization is enabled.
+- **off** indicates that the optimization is disabled.
+
+**Default value**: **on**
+
+## log_parser_stats
+
+**Parameter description**: Specifies whether the optimizer outputs the performance logs of the parser module.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the performance logs are output.
+- **off** indicates that the performance logs are not output.
+
+**Default value**: **off**
+
+## log_planner_stats
+
+**Parameter description**: Specifies whether the optimizer outputs the performance logs of the planner module.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the performance logs are output.
+- **off** indicates that the performance logs are not output.
+
+**Default value**: **off**
+
+## log_executor_stats
+
+**Parameter description**: Specifies whether the optimizer outputs the performance logs of the executor module.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the performance logs are output.
+- **off** indicates that the performance logs are not output.
+
+**Default value**: **off**
+
+## log_statement_stats
+
+**Parameter description**: Specifies whether the optimizer outputs the performance logs of a statement.
+
+This parameter is a SUSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the performance logs are output.
+- **off** indicates that the performance logs are not output.
+
+**Default value**: **off**
+
+## plan_cache_mode
+
+**Parameter description**: Specifies the policy for generating an execution plan in the **prepare** statement.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: enumerated values
+
+- **auto** indicates that the **custom plan** or **generic plan** is selected by default.
+- **force_generic_plan** indicates that the **generic plan** is forcibly used.
+- **force_custom_plan** indicates that the **custom plan** is forcibly used.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - This parameter is valid only for the **prepare** statement. It is used when the parameterized field in the **prepare** statement has severe data skew.
+> - **custom plan** is a plan generated after you run the **prepare** statement where parameters in the **execute** statement is embedded. The **custom plan** generates a plan based on specific parameters in the **execute** statement. This scheme generates a preferred plan based on specific parameters each time and has good execution performance. The disadvantage is that the plan needs to be regenerated before each execution, resulting in a large amount of repeated optimizer overhead.
+> - **generic plan** is a plan generated after you run the **prepare** statement. The plan policy binds parameters to the plan when you run the **execute** statement and execute the plan. The advantage of this scheme is that repeated optimizer overheads can be avoided in each execution. The disadvantage is that the plan may not be optimal when data skew occurs for the bound parameters and may result in poor plan execution performance.
+
+**Default value**: **auto**
+
+## enable_hypo_index
+
+**Parameter description**: Controls whether the optimizer considers virtual indexes when executing the EXPLAIN command.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that the performance logs are output.
+- **off** indicates that the performance logs are not output.
+
+**Default value**: **off**
+
+## enable_force_vector_engine
+
+**Parameter description:** Specifies whether to forcibly generate vectorized execution plans for a vectorized execution operator if the operator's child node is a non-vectorized operator. When this parameter is set to **on**, vectorized execution plans are forcibly generated.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean
+
+- **on** indicates that vectorized operators are forcibly generated.
+- **off** indicates that the vectorized operator optimizer determines whether to perform vectorization.
+
+**Default value**: **off**
+
+## enable_auto_explain
+
+**Parameter description**: Specifies whether to enable the function of automatically printing execution plans. This parameter is used to locate slow stored procedures or slow queries and is valid only for the currently connected primary database node.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Boolean. The value **on** indicates that the function is enabled, and the value **off** indicates that the function is disabled.
+
+**Default value**: **off**
+
+## auto_explain_level
+
+**Parameter description**: Specifies the log level for automatically printing execution plans.
+
+This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: Enumeration type. The value can be **log** or **notice**. **log** indicates that the execution plan is printed in logs. **notice** indicates that the execution plan is printed in notification mode.
+
+**Default value**: **log**
+
+## query_dop
+
+**Parameter description**: Specifies the user-defined degree of parallelism (DOP). This parameter is a USERSET parameter. Set it based on instructions provided in Table 1 [GUC parameters](30-appendix).
+
+**Value range**: an integer ranging from 1 to 64 If the fixed SMP function is enabled, the system uses the fixed DOP.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** After enabling concurrent queries, ensure you have sufficient CPU, memory, and network to achieve the optimal performance.
+
+**Default value**: **1**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/introduction-to-query-planning.md b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/introduction-to-query-planning.md
new file mode 100644
index 0000000000000000000000000000000000000000..c7450e6911351f66568d2871d5d736bc49729934
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/introduction-to-query-planning.md
@@ -0,0 +1,16 @@
+---
+title: Introduction
+summary: Introduction
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+## Introduction
+
+This section describes the method configuration, cost constants, planning algorithm, and some configuration parameters for the optimizer.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> Two parameters are involved in the optimizer:
+>
+> - *INT_MAX* indicates the maximum value of the INT data type. The value is **2147483647**.
+> - *DBL_MAX* indicates the maximum value of the FLOAT data type.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/oracle-plugins/dblink-user-guide.md b/product/en/docs-mogdb/v3.0/reference-guide/oracle-plugins/dblink-user-guide.md
new file mode 100644
index 0000000000000000000000000000000000000000..ab3f9689d897b449400a1eddaa577f6d12d6535c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/oracle-plugins/dblink-user-guide.md
@@ -0,0 +1,65 @@
+---
+title: DBlink User Guide
+summary: DBlink User Guide
+author: Guo Huan
+date: 2021-11-29
+---
+
+# dblink
+
+## dblink Overview
+
+dblink is used to execute queries in a remote database. It usually refers to `SELECT`, and it can also be any SQL statement that returns rows.
+
+When two `text` parameters are given, the first one is searched by the name for persistent connection; if it is found, the command is executed on the connection. If not found, the first parameter is treated as the same connection information string as `dblink_connect`, and the connection is only implemented during execution of this command.
+
+<br/>
+
+## dblink Installation
+
+For details, please refer to [gs_install_plugin](gs_install_plugin) or [gs_install_plugin_local](gs_install_plugin_local).
+
+<br/>
+
+## dblink Usage
+
+### Create Extensions In the Database
+
+```sql
+create extension dblink;
+```
+
+### Check Whether the Extension Was Created Successfully
+
+```
+\dx
+```
+
+### Connect to the Remote Database to Perform Query Operations
+
+```sql
+select * from dblink('dbname=postgres host=127.0.0.1 port=12345 user=test password=Test123456'::text, 'select * from dblink_test'::text)t(id int, name varchar);
+```
+
+### Create Connections
+
+```sql
+select dblink_connect('dblink_conn','hostaddr=127.0.0.1 port=12345 dbname=postgres user=test password=Test123456');
+```
+
+### Operate on Database Tables
+
+(View does not support query operations)
+
+```sql
+select dblink_exec('dblink_conn', 'create table ss(id int, name int)');
+select dblink_exec('dblink_conn', 'insert into ss values(2,1)');
+select dblink_exec('dblink_conn', 'update ss set name=2 where id=1');
+select dblink_exec('dblink_conn', 'delete from ss where id=1');
+```
+
+### Close Connections
+
+```sql
+select dblink_disconnect('dblink_conn')
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/oracle-plugins/orafce-user-guide.md b/product/en/docs-mogdb/v3.0/reference-guide/oracle-plugins/orafce-user-guide.md
new file mode 100644
index 0000000000000000000000000000000000000000..10f445e2a584bab9a8f3b86f99769f20a22f8ed3
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/oracle-plugins/orafce-user-guide.md
@@ -0,0 +1,250 @@
+---
+title: orafce User Guide
+summary: orafce User Guide
+author: Guo Huan
+date: 2021-11-29
+---
+
+# orafce
+
+## orafce Overview
+
+orafce is MogDB compatibility package for Oracle, which can support some Oracle tables, functions, and data types. orafce provides functions and operators that emulate a subset of functions and packages from the Oracle RDBMS.
+
+This plugin contains some useful functions that can help with porting Oracle application to MogDB/PostgreSQL or that can be generally useful. Built-in Oracle date functions have been tested against Oracle 10 for conformance. Date ranges from 1960 to 2070 work correctly. Dates before 1100-03-01 cannot be verified due to a bug in Oracle.
+
+All functions are fully compatibles with Oracle and respect all known format strings. Detailed descriptions can be found on [GitHub orafce](https://github.com/orafce/orafce).
+
+ <br/>
+
+## Install orafce
+
+For details, please refer to [gs_install_plugin](gs_install_plugin) or [gs_install_plugin_local](gs_install_plugin_local).
+
+<br/>
+
+## Create and Use orafce
+
+```sql
+create extension orafce;
+```
+
+Check all schemas:
+
+```sql
+\dn
+```
+
+ <br/>
+
+### dbms_output Use Method
+
+Check functions where some functions include parameters and some functions do not include parameters. The parameter type is boolean.
+
+```sql
+\df dbms_output.*
+```
+
+Example of functions that do not include parameters:
+
+```sql
+select dbms_output.disable();
+```
+
+Example of functions that include parameters:
+
+```sql
+select dbms_output.put_line('sss');
+```
+
+Boolean: (here the value is 0 or 1)
+
+```sql
+select dbms_output.serveroutput(0);
+```
+
+<br/>
+
+### dbms_random Use Method
+
+Check functions where some functions include parameters and some functions do not include parameters.
+
+```sql
+\df
+```
+
+Example of functions that include parameters:
+
+```sql
+select dbms_random.initialize(1);
+select dbms_random.value(256.1243434351237831823812312,12333.3111);
+```
+
+**Value** does not have to have the parameter value inputted.
+
+Example of functions that do not include parameters:
+
+```sql
+select dbms_random.value();
+```
+
+<br/>
+
+### dbms_utility Use Method
+
+Check functions.
+
+```sql
+\df
+```
+
+```sql
+select dbms_utility.format_call_stack();
+select dbms_utility.format_call_stack('o');
+```
+
+Only [ops] is allowed for functions that include parameters.
+
+```sql
+select dbms_utility.get_time();
+```
+
+<br/>
+
+### oracle Function Usage
+
+Check functions.
+
+```sql
+\df
+```
+
+```sql
+select oracle.btrim('enmo');
+select oracle.get_full_version_num();
+select oracle.get_major_version();
+select oracle.get_major_version_num();
+select oracle.get_platform();
+select oracle.get_status();
+select oracle.length(1);
+select oracle.lpad('enmo', 1);
+select oracle.ltrim('enmo', 'enmo');
+select oracle.numtodsinterval(12.22,'1232');
+select oracle.nvl(1,2);
+select oracle.regexp_count('enmo', 'tech');
+select oracle.regexp_instr('enmo', 'tech');
+select oracle.regexp_replace('enmo', 'tech', 'sss', 1);
+select oracle.regexp_substr('enmo', 'tech', 1);
+```
+
+replace_empty_strings:
+
+```sql
+CREATE TABLE trg_test(a varchar, b int, c varchar, d date, e int);
+CREATE TRIGGER trg_test_xx BEFORE INSERT OR UPDATE ON trg_test FOR EACH ROW EXECUTE PROCEDURE oracle.replace_empty_strings(true);
+\pset null ***
+INSERT INTO trg_test VALUES('',10, 'AHOJ', NULL, NULL);
+INSERT INTO trg_test VALUES('AHOJ', NULL, '', '2020-01-01', 100);
+SELECT * FROM trg_test;
+```
+
+replace_null_strings:
+
+```sql
+CREATE TABLE trg_test(a varchar, b int, c varchar, d date, e int);
+CREATE TRIGGER trg_test_xx BEFORE INSERT OR UPDATE ON trg_test FOR EACH ROW EXECUTE PROCEDURE oracle.replace_null_strings();
+\pset null ***
+INSERT INTO trg_test VALUES(NULL, 10, 'AHOJ', NULL, NULL);
+INSERT INTO trg_test VALUES('AHOJ', NULL, NULL, '2020-01-01', 100);
+SELECT * FROM trg_test;
+```
+
+```sql
+SELECT * FROM trg_test;
+select oracle.round(1.212, 1);
+select oracle.rpad('enmo', 1);
+select oracle.rtrim('yunhe', 'enmo');
+select oracle.sessiontimezone();
+select oracle.substr(111.122,1);
+select oracle.to_char('14-Jan08 11:44:49+05:30');
+select oracle.translate_oracle_modifiers('icnsmx',true);
+```
+
+(The parameter must include one or more of 'icnsmx'. **m** will be converted to **n**, and **n** will be converted to **s**. If the parameter is set to **true**, **g** will be added to the end of the string. Otherwise, **g** is not added.)
+
+```sql
+select oracle.trunc(122.31, 1);
+select oracle.unistr('yunhe-enmo');
+```
+
+<br/>
+
+### utl_file Usage
+
+Check functions.
+
+```sql
+\df
+```
+
+<br/>
+
+### File Check Operation
+
+```sql
+CREATE OR REPLACE FUNCTION checkFlushFile(dir text) RETURNS void AS $$
+DECLARE
+ f utl_file.file_type;
+ f1 utl_file.file_type;
+ ret_val text;
+ i integer;
+BEGIN
+ f := utl_file.fopen(dir, 'regressflush_orafce.txt', 'a');
+ PERFORM utl_file.put_line(f, 'ABC');
+ PERFORM utl_file.new_line(f);
+ PERFORM utl_file.put_line(f, '123'::numeric);
+ PERFORM utl_file.new_line(f);
+ PERFORM utl_file.putf(f, '[1=%s, 2=%s, 3=%s, 4=%s, 5=%s]', '1', '2', '3', '4', '5');
+ PERFORM utl_file.fflush(f);
+ f1 := utl_file.fopen(dir, 'regressflush_orafce.txt', 'r');
+ ret_val=utl_file.get_nextline(f1);
+ i:=1;
+ WHILE ret_val IS NOT NULL LOOP
+  RAISE NOTICE '[%] >>%<<', i,ret_val;
+  ret_val := utl_file.get_nextline(f1);
+  i:=i+1;
+ END LOOP;
+ RAISE NOTICE '>>%<<', ret_val;
+ f1 := utl_file.fclose(f1);
+ f := utl_file.fclose(f);
+END;
+$$ LANGUAGE plpgsql
+```
+
+<br/>
+
+### File Read Operation
+
+```sql
+CREATE OR REPLACE FUNCTION read_file(dir text) RETURNS void AS $$
+DECLARE
+ f utl_file.file_type;
+BEGIN
+ f := utl_file.fopen(dir, 'regress_orafce.txt', 'r');
+ FOR i IN 1..11 LOOP
+  RAISE NOTICE '[%] >>%<<', i, utl_file.get_line(f);
+ END LOOP;
+ RAISE NOTICE '>>%<<', utl_file.get_line(f, 4);
+ RAISE NOTICE '>>%<<', utl_file.get_line(f, 4);
+ RAISE NOTICE '>>%<<', utl_file.get_line(f);
+ RAISE NOTICE '>>%<<', utl_file.get_line(f);
+ EXCEPTION
+  -- WHEN no_data_found THEN,  8.1 plpgsql doesn't know no_data_found
+  WHEN others THEN
+   RAISE NOTICE 'finish % ', sqlerrm;
+   RAISE NOTICE 'is_open = %', utl_file.is_open(f);
+   PERFORM utl_file.fclose_all();
+   RAISE NOTICE 'is_open = %', utl_file.is_open(f);
+ END;
+$$ LANGUAGE plpgsql;
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/oracle-plugins/pg_bulkload-user-guide.md b/product/en/docs-mogdb/v3.0/reference-guide/oracle-plugins/pg_bulkload-user-guide.md
new file mode 100644
index 0000000000000000000000000000000000000000..c37338a0f886e742b0e162cb9602063d908f3607
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/oracle-plugins/pg_bulkload-user-guide.md
@@ -0,0 +1,87 @@
+---
+title: pg_bulkloab User Guide
+summary: pg_bulkloab User Guide
+author: Guo Huan
+date: 2021-11-29
+---
+
+# pg_bulkload
+
+## pg_bulkload Overview
+
+pg_bulkload is a high-speed data loading tool for MogDB. It is faster than the copy command and can skip shared buffer and wal buffer to write data into files directly.
+
+<br/>
+
+## Install pg_bulkload
+
+For details, please refer to [gs_install_plugin](gs_install_plugin) or [gs_install_plugin_local](gs_install_plugin_local).
+
+<br/>
+
+## Use pg_bulkload
+
+```bash
+pg_bulkload --help
+gsql -p 5432 postgres -r
+```
+
+```sql
+CREATE EXTENSION pg_bulkload;
+create table test_bulkload(id int, name varchar(128));
+```
+
+Create a TXT file and write 100,000 lines of data.
+
+```bash
+seq 100000| awk '{print $0"|bulkload"}' > bulkload_output.txt
+```
+
+<br/>
+
+### Using Parameters
+
+After the file is successfully created, run the following command:
+
+```bash
+pg_bulkload -i ./bulkload_output.txt -O test_bulkload -l test_bulkload.log -p 5432 -o "TYPE=csv" -o "DELIMITER=|" -d postgres -U hlv
+```
+
+Connect to the database to check whether the data is imported successfully:
+
+ ```sql
+ select count(1) from test_bulkload;
+ ```
+
+<br/>
+
+### Using the Control File
+
+Before using the control file for data import, you need to clear the imported data in the previous table.
+
+Write a **.ctl** file.
+
+```bash
+INPUT=/vdb/MogDB-server/dest/bulkload_output.txt
+LOGFILE = /vdb/MogDB-server/dest/test_bulkload.log
+LIMIT = INFINITE
+PARSE_ERRORS = 0
+CHECK_CONSTRAINTS = NO
+TYPE = CSV
+SKIP = 5  (This parameter sets how many lines to skip)
+DELIMITER = |
+QUOTE = "\""
+ESCAPE = "\""
+OUTPUT = test_bulkload
+MULTI_PROCESS = NO
+WRITER = DIRECT
+DUPLICATE_ERRORS = 0
+ON_DUPLICATE_KEEP = NEW
+TRUNCATE = YES
+```
+
+Run following command：
+
+```bash
+pg_bulkload ./lottu.ctl -d postgres -U hlv
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/oracle-plugins/pg_prewarm-user-guide.md b/product/en/docs-mogdb/v3.0/reference-guide/oracle-plugins/pg_prewarm-user-guide.md
new file mode 100644
index 0000000000000000000000000000000000000000..d88eb7d99807be22531400e998d820998f6064f4
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/oracle-plugins/pg_prewarm-user-guide.md
@@ -0,0 +1,90 @@
+---
+title: pg_prewarm User Guide
+summary: pg_prewarm User Guide
+author: Guo Huan
+date: 2021-11-29
+---
+
+# pg_prewarm
+
+## pg_prewarm Overview
+
+The pg_prewarm module provides a convenient way to load relational data into the operating system buffer cache or MogDB buffer cache.
+
+<br/>
+
+## Install pg_prewarm
+
+For details, please refer to [gs_install_plugin](gs_install_plugin) or [gs_install_plugin_local](gs_install_plugin_local).
+
+<br/>
+
+## pg_prewarm loading mode
+
+- mode: The loading mode, the options are 'prefetch', 'read', 'buffer', the default is 'buffer'
+
+- prefetch: Asynchronously preload data into OS cache
+
+- read: The end result is the same as prefetch, but it is synchronous and supports all platforms
+
+- buffer: Preload data into database cache
+
+## Create and Use pg_prewarm
+
+1. Create extension pg_prewarm.
+
+    ```sql
+   create extension pg_prewarm; 
+   ```
+
+2. Create a test table. 
+
+   ```sql
+   create table test_pre (id int4,name character varying(64),creat_time timestamp(6) without time zone); 
+   ```
+
+3. Insert data into the test table.
+
+   ```sql
+   insert into test_pre select generate_series(1,100000),generate_series(1,100000)||  '_pre',clock_timestamp(); 
+   ```
+
+4. Check the table size. 
+
+   ```sql
+   mogdb=# select pg_size_pretty(pg_relation_size('test_pre'));
+   pg_size_pretty
+   ----------------
+   5136 kB
+   (1 row)
+   ```
+
+5. Load data to the database cache. The result shows that pg_prewarm divides data into 642 data blocks. 
+
+   ```sql
+   mogdb=# select pg_prewarm('test_pre','buffer');
+    pg_prewarm
+   ------------
+        642
+   (1 row)
+   ```
+
+6. Check the block size. 
+
+   ```sql
+   mogdb=# select current_setting('block_size');
+    current_setting
+   -----------------
+   8192
+   (1 row)
+   ```
+
+   The size of each data block is 8 KB in MogDB by default.  
+
+   ```sql
+   mogdb=# select 642*8; 
+    ?column?
+   ----------
+     5136
+   (1 row)
+   ```
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/oracle-plugins/pg_repack-user-guide.md b/product/en/docs-mogdb/v3.0/reference-guide/oracle-plugins/pg_repack-user-guide.md
new file mode 100644
index 0000000000000000000000000000000000000000..c6abd3116e3c15c2cb1bb7ecf775187714b93eab
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/oracle-plugins/pg_repack-user-guide.md
@@ -0,0 +1,91 @@
+---
+title: pg_repack User Guide
+summary: pg_repack User Guide
+author: Guo Huan
+date: 2021-11-29
+---
+
+# pg_repack
+
+## pg_repack Overview
+
+The pg_repack extension is used to clear the table space online, thereby effectively solving the problem of table expansion caused by the operation that a large amount of data in a table is updated. pg_repack does not need to acquire an exclusive lock, which is more lightweight than CLUSTER or VACUUM FULL.
+
+<br/>
+
+## Install pg_repack
+
+For details, please refer to [gs_install_plugin](gs_install_plugin) or [gs_install_plugin_local](gs_install_plugin_local).
+
+<br/>
+
+## Use pg_repack
+
+1. Connect to the database and create a user. 
+
+   ```bash
+   gsql postgres -r -p 5001
+   ```
+
+   ```sql
+   create user test password 'Test123456' login sysadmin;
+   ```
+
+2. In the database, create extension pg_repack.
+
+    ```sql
+    create extension pg_repack;
+    ```
+
+3. Create the pg_repack table which must contain a primary key.
+
+   ```sql
+   create table repack_test(id int primary key, name name);
+   ```
+
+4. Run **\dx** to check whether pg_repack is successfully created. 
+
+    ```
+    \dx
+    ```
+
+5. Insert 2,000,000 rows of data into the table **repack_test**.
+
+   ```sql
+   insert into repack_test select generate_series(1,2000000),'a';
+   ```
+
+6. Check the size of the table **repack_test**. 
+
+   ```sql
+   select pg_size_pretty(pg_relation_size('repack_test'));
+   ```
+
+7. Delete some data and then check the table size. 
+
+   ```sql
+   Delete from repack_test where id>1000000;
+   ```
+
+   The figure shows that the table size does not change after 1,000,000 rows of data is deleted. In this case, pg_repack needs to be used. 
+
+8. Use the pg_repack tool. 
+
+   ```bash
+   pg_repack -d postgres -t test.repack_test -h 127.0.0.1 -U test -p 5001
+   ```
+
+   Parameter introduction:
+
+   - -d dbname (Database name) 
+   - -t test.repack_test -h hostip (Server IP address) 
+   - -U user (Username) 
+   - -p port (Port) 
+   - -e (Output all SQLs executed when pg_repack is used) 
+   - -E DEBUG (Set the log level of the output information to DEBUG) 
+   
+   Check the size of the table **repack_test**. 
+   
+   ```sql
+   select pg_size_pretty(pg_relation_size('repack_test'));
+   ```
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/oracle-plugins/pg_trgm-user-guide.md b/product/en/docs-mogdb/v3.0/reference-guide/oracle-plugins/pg_trgm-user-guide.md
new file mode 100644
index 0000000000000000000000000000000000000000..a35d0017a92dd50b43c8320ebb839e370512820c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/oracle-plugins/pg_trgm-user-guide.md
@@ -0,0 +1,60 @@
+---
+title: pg_trgm User Guide
+summary: pg_trgm User Guide
+author: Guo Huan
+date: 2021-11-29
+---
+
+# pg_trgm
+
+## pg_trgm Overview
+
+The pg_trgm module provides functions and operators to determine the similarity of the alphanumeric text based on the matching of the ternary model, and an index operator class that supports quick search of similar strings.
+
+<br/>
+
+## Install pg_trgm
+
+For details, please refer to [gs_install_plugin](gs_install_plugin) or [gs_install_plugin_local](gs_install_plugin_local).
+
+<br/>
+
+## Use pg_trgm
+
+1. In the database, create the following extension:
+
+   ```sql
+   -- pg_trgm:
+   create extension pg_trgm;
+   ```
+
+2. Create a table and insert 1,000,000 rows of data into the table.
+
+   ```sql
+   create table trgm_test(id int, name varchar);
+   insert into trgm_test select generate_series(1,1000000),md5(random()::name);
+   ```
+
+3. Query the table without using pg_trgm.
+
+   ```sql
+   explain analyze select * from trgm_test where name like '%69089%';
+   ```
+
+   ```sql
+   select * from trgm_test where name like '%69089%';
+   ```
+
+4. Create an index.
+
+   ```sql
+   create index idx_trgm_test_1 on trgm_test using gin(name gin_trgm_ops);
+   ```
+
+   ```sql
+   explain analyze select * from trgm_test where name like '%ad44%';
+   ```
+
+   ```sql
+   select * from trgm_test where name like '%305696%';
+   ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/oracle-plugins/wal2json-user-guide.md b/product/en/docs-mogdb/v3.0/reference-guide/oracle-plugins/wal2json-user-guide.md
new file mode 100644
index 0000000000000000000000000000000000000000..caf672cb4f4739a8569a185e609512c5fd2d4705
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/oracle-plugins/wal2json-user-guide.md
@@ -0,0 +1,109 @@
+---
+title: wal2json User Guide
+summary: wal2json User Guide
+author: Guo Huan
+date: 2021-11-29
+---
+
+# wal2json
+
+## wal2json Overview
+
+wal2json is a logical decoding extension. With this extension, you can access the tuples generated by INSERT and UPDATE and parse the content in WAL.
+
+The wal2json extension will generate a JSON object in each transaction. All new/old tuples are provided in the JSON object, and additional options can also include such attributes as transaction timestamp, restricted structure, data type, and transaction ID.
+
+<br/>
+
+## Install wal2json
+
+For details, please refer to [gs_install_plugin](gs_install_plugin) or [gs_install_plugin_local](gs_install_plugin_local).
+
+<br/>
+
+## Configure Database Parameters
+
+1. Modify the **postgresql.conf** file in the data directory of the database (both the primary and standby databases need to be modified).
+
+   ```sql
+   wal_level = logical
+   max_replication_slots = 10
+   max_wal_senders = 10 
+   ```
+
+2. Modify **pg_hba.conf** (both the primary and standby databases need to be modified).
+
+   ```sql
+   host   replication   all     127.0.0.1/32       trust
+   ```
+
+3. Restart the database. 
+
+<br/>
+
+## Use wal2json
+
+1. Open a new terminal and use wal2json to connect to the database. 
+
+   ```bash
+   pg_recvlogical -d postgres --slot test2_slot --create -P wal2json -h 127.0.0.1 -p 5001 -U test
+   pg_recvlogical -d postgres -h 127.0.0.1 -p 5001 -U test --slot test2_slot --start  -f - 
+   ```
+   
+2. Operate with the database.
+
+   ```sql
+   create table ff(id int, name int);
+   insert into ff values(1,2);
+   insert into ff values(2,4);
+   select * from ff;
+   ```
+
+3. Output the operation process on wal2json.
+
+   ```json
+   {"change":[]}
+   {"change":[]}
+   {"change":[{"kind":"insert","schema":"test","table":"ff","columnnames":["id","name"],"columntypes":["integer","integer"],"columnvalues":[1,10]}]}
+   {"change":[{"kind":"insert","schema":"test","table":"ff","columnnames":["id","name"],"columntypes":["integer","integer"],"columnvalues":[2,2]}]}
+   ```
+   
+   <br/>
+
+## Wal2json Parameters
+
+Run the following command in the data directory of the database: 
+
+```sql
+pg_recvlogical --help
+ -f, --file=FILE     receive log into this file. - for stdout
+ -n, --no-loop      do not loop on connection lost
+ -v, --verbose      output verbose messages
+ -V, --version      output version information, then exit
+ -?, --help       show this help, then exit
+
+Connection options:
+ -d, --dbname=DBNAME   database to connect to
+ -h, --host=HOSTNAME   database server host or socket directory
+ -p, --port=PORT     database server port number
+ -U, --username=NAME   connect as specified database user
+ -w, --no-password    never prompt for password
+ -W, --password     force password prompt (should happen automatically)
+
+Replication options:
+ -F  --fsync-interval=INTERVAL
+            frequency of syncs to the output file (in seconds, defaults to 10)
+ -o, --option=NAME[=VALUE]
+            Specify option NAME with optional value VAL, to be passed
+            to the output plugin
+ -P, --plugin=PLUGIN   use output plugin PLUGIN (defaults to mppdb_decoding)
+ -s, --status-interval=INTERVAL
+            time between status packets sent to server (in seconds, defaults to 10)
+ -S, --slot=SLOT     use existing replication slot SLOT instead of starting a new one
+ -I, --startpos=PTR   Where in an existing slot should the streaming start
+
+Action to be performed:
+   --create      create a new replication slot (for the slotname see --slot)
+   --start       start streaming in a replication slot (for the slotname see --slot)
+   --drop       drop the replication slot (for the slotname see --slot)
+```
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.ARCHIVE_SNAPSHOT.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.ARCHIVE_SNAPSHOT.md
new file mode 100644
index 0000000000000000000000000000000000000000..19bdbbde7bca044f013ab83bd12def59872620b6
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.ARCHIVE_SNAPSHOT.md
@@ -0,0 +1,18 @@
+---
+title: DB4AI.ARCHIVE_SNAPSHOT
+summary: DB4AI.ARCHIVE_SNAPSHOT
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DB4AI.ARCHIVE_SNAPSHOT
+
+**ARCHIVE_SNAPSHOT** archives snapshots for the DB4AI feature. You can invoke **ARCHIVE SNAPSHOT** to implement this function. After taking effect, the snapshot cannot be used for training.
+
+**Table 1** DB4AI.ARCHIVE_SNAPSHOT input parameters and return values
+
+| Parameter | Type                    | Description                                                  |
+| :-------- | :---------------------- | :----------------------------------------------------------- |
+| i_schema  | IN NAME                 | Name of the schema storing snapshots. The default value is the current user. |
+| i_name    | IN NAME                 | Snapshot name                                                |
+| res       | OUT db4ai.snapshot_name | Result                                                       |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.CREATE_SNAPSHOT.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.CREATE_SNAPSHOT.md
new file mode 100644
index 0000000000000000000000000000000000000000..17fda004016ae6b2158de3ff63871cdf8787eba2
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.CREATE_SNAPSHOT.md
@@ -0,0 +1,21 @@
+---
+title: DB4AI.CREATE_SNAPSHOT
+summary: DB4AI.CREATE_SNAPSHOT
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DB4AI.CREATE_SNAPSHOT
+
+**CREATE_SNAPSHOT** creates snapshots for the DB4AI feature. You can invoke **CREATE SNAPSHOT** to implement this function.
+
+**Table 1** DB4AI.CREATE_SNAPSHOT input parameters and return values
+
+| Parameter  | Type                    | Description                                                  |
+| :--------- | :---------------------- | :----------------------------------------------------------- |
+| i_schema   | IN NAME                 | Name of the schema storing snapshots. The default value is the current user or **PUBLIC**. |
+| i_name     | IN NAME                 | Snapshot name                                                |
+| i_commands | IN TEXT[]               | SQL commands for obtaining data                              |
+| i_vers     | IN NAME                 | Version suffix                                               |
+| i_comment  | IN TEXT                 | Snapshot description                                         |
+| res        | OUT db4ai.snapshot_name | Result                                                       |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.CREATE_SNAPSHOT_INTERNAL.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.CREATE_SNAPSHOT_INTERNAL.md
new file mode 100644
index 0000000000000000000000000000000000000000..4e9c9ca23c611a32bfff1af50b6baae4b625129a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.CREATE_SNAPSHOT_INTERNAL.md
@@ -0,0 +1,21 @@
+---
+title: DB4AI.CREATE_SNAPSHOT_INTERNAL
+summary: DB4AI.CREATE_SNAPSHOT_INTERNAL
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DB4AI.CREATE_SNAPSHOT_INTERNAL
+
+**CREATE_SNAPSHOT_INTERNAL** is a built-in execution function of the DB4AI.CREATE_SNAPSHOT function. The function involves information verification and cannot be directly invoked.
+
+**Table 1** DB4AI.CREATE_SNAPSHOT_INTERNAL input parameters and return values
+
+| Parameter  | Type      | Description                     |
+| :--------- | :-------- | :------------------------------ |
+| s_id       | IN BIGINT | Snapshot ID                     |
+| i_schema   | IN NAME   | Namespace storing the snapshot  |
+| i_name     | IN NAME   | Snapshot name                   |
+| i_commands | IN TEXT[] | SQL commands for obtaining data |
+| i_comment  | IN TEXT   | Snapshot description            |
+| i_owner    | IN NAME   | Snapshot owner                  |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.MANAGE_SNAPSHOT_INTERNAL.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.MANAGE_SNAPSHOT_INTERNAL.md
new file mode 100644
index 0000000000000000000000000000000000000000..48f1e8dbb96f821767783a275049533cbaf815f2
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.MANAGE_SNAPSHOT_INTERNAL.md
@@ -0,0 +1,19 @@
+---
+title: DB4AI.MANAGE_SNAPSHOT_INTERNAL
+summary: DB4AI.MANAGE_SNAPSHOT_INTERNAL
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DB4AI.MANAGE_SNAPSHOT_INTERNAL
+
+**MANAGE_SNAPSHOT_INTERNAL** is a built-in execution function of the **DB4AI.PUBLISH_SNAPSHOT** and **DB4AI.ARCHIVE_SNAPSHOT** functions. The function involves information verification and cannot be directly invoked.
+
+**Table 1** DB4AI.MANAGE_SNAPSHOT_INTERNAL input parameters and return values
+
+| Parameter | Type                    | Description                          |
+| :-------- | :---------------------- | :----------------------------------- |
+| i_schema  | IN NAME                 | Name of the schema storing snapshots |
+| i_name    | IN NAME                 | Snapshot name                        |
+| publish   | IN BOOLEN               | Whether the snapshot is published    |
+| res       | OUT db4ai.snapshot_name | Result                               |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.PREPARE_SNAPSHOT.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.PREPARE_SNAPSHOT.md
new file mode 100644
index 0000000000000000000000000000000000000000..7a238b53e7c5f40eefb249ccd614cc62717535e9
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.PREPARE_SNAPSHOT.md
@@ -0,0 +1,21 @@
+---
+title: DB4AI.PREPARE_SNAPSHOT
+summary: DB4AI.PREPARE_SNAPSHOT
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DB4AI.PREPARE_SNAPSHOT
+
+**PREPARE_SNAPSHOT** prepares data for model training and interprets snapshots for the DB4AI feature. A snapshot provides a complete sequence of data and documents that are changed by all applications. You can invoke **PREPARE SNAPSHOT** to implement this function.
+
+**Table 1** DB4AI.PREPARE_SNAPSHOT input parameters and return values
+
+| Parameter  | Type                    | Description                                                  |
+| :--------- | :---------------------- | :----------------------------------------------------------- |
+| i_schema   | IN NAME                 | Name of the schema storing snapshots. The default value is the current user or **PUBLIC**. |
+| i_parent   | IN NAME                 | Parent snapshot name                                         |
+| i_commands | IN TEXT[]               | DDL and DML commands for modifying snapshots                 |
+| i_vers     | IN NAME                 | Version suffix                                               |
+| i_comment  | IN TEXT                 | Data comment                                                 |
+| res        | OUT db4ai.snapshot_name | Result                                                       |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.PREPARE_SNAPSHOT_INTERNAL.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.PREPARE_SNAPSHOT_INTERNAL.md
new file mode 100644
index 0000000000000000000000000000000000000000..6ec38c071902b1b406048e1863f60486a862794c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.PREPARE_SNAPSHOT_INTERNAL.md
@@ -0,0 +1,27 @@
+---
+title: DB4AI.PREPARE_SNAPSHOT_INTERNAL
+summary: DB4AI.PREPARE_SNAPSHOT_INTERNAL
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DB4AI.PREPARE_SNAPSHOT_INTERNAL
+
+**PREPARE_SNAPSHOT_INTERNAL** is a built-in execution function of the DB4AI.PREPARE_SNAPSHOT function. The function involves information verification and cannot be directly invoked.
+
+**Table 1** DB4AI.PREPARE_SNAPSHOT_INTERNAL input parameters and return values
+
+| Parameter   | Type         | Description                                                  |
+| :---------- | :----------- | :----------------------------------------------------------- |
+| s_id        | IN BIGINT    | Snapshot ID                                                  |
+| p_id        | IN BIGINT    | Parent snapshot ID                                           |
+| m_id        | IN BIGINT    | Matrix ID                                                    |
+| r_id        | IN BIGINT    | Root snapshot ID                                             |
+| i_schema    | IN NAME      | Snapshot schema                                              |
+| i_name      | IN NAME      | Snapshot name                                                |
+| i_commands  | IN TEXT[]    | DDL and DML commands for modifying snapshots                 |
+| i_comment   | IN TEXT      | Snapshot description                                         |
+| i_owner     | IN NAME      | Snapshot owner                                               |
+| i_idx       | INOUT INT    | Command index                                                |
+| i_exec_cmds | INOUT TEXT[] | DDL and DML commands for execution                           |
+| i_mapping   | IN NAME[]    | Maps user columns to backup columns. A rule is generated if the value is not **NULL**. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.PUBLISH_SNAPSHOT.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.PUBLISH_SNAPSHOT.md
new file mode 100644
index 0000000000000000000000000000000000000000..ce01d463006c86512589a401125b221d6d6a7bfe
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.PUBLISH_SNAPSHOT.md
@@ -0,0 +1,18 @@
+---
+title: DB4AI.PUBLISH_SNAPSHOT
+summary: DB4AI.PUBLISH_SNAPSHOT
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DB4AI.PUBLISH_SNAPSHOT
+
+**PUBLISH_SNAPSHOT** publishes snapshots for the DB4AI feature. You can invoke **PUBLISH SNAPSHOT** to implement this function.
+
+**Table 1** DB4AI.PUBLISH_SNAPSHOT input parameters and return values
+
+| Parameter | Type                    | Description                                                  |
+| :-------- | :---------------------- | :----------------------------------------------------------- |
+| i_schema  | IN NAME                 | Name of the schema storing snapshots. The default value is the current user or **PUBLIC**. |
+| i_name    | IN NAME                 | Snapshot name                                                |
+| res       | OUT db4ai.snapshot_name | Result                                                       |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.PURGE_SNAPSHOT.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.PURGE_SNAPSHOT.md
new file mode 100644
index 0000000000000000000000000000000000000000..252bf8d300bbf886cea25f41df873e25eb4b549d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.PURGE_SNAPSHOT.md
@@ -0,0 +1,18 @@
+---
+title: DB4AI.PURGE_SNAPSHOT
+summary: DB4AI.PURGE_SNAPSHOT
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DB4AI.PURGE_SNAPSHOT
+
+**PURGE_SNAPSHOT** deletes snapshots for the DB4AI feature. You can invoke **PURGE SNAPSHOT** to implement this function.
+
+**Table 1** DB4AI.PURGE_SNAPSHOT input parameters and return values
+
+| Parameter | Type                    | Description                          |
+| :-------- | :---------------------- | :----------------------------------- |
+| i_schema  | IN NAME                 | Name of the schema storing snapshots |
+| i_name    | IN NAME                 | Snapshot name                        |
+| res       | OUT db4ai.snapshot_name | Result                               |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.PURGE_SNAPSHOT_INTERNAL.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.PURGE_SNAPSHOT_INTERNAL.md
new file mode 100644
index 0000000000000000000000000000000000000000..547dfed9df9681b640911813606761d21901c221
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.PURGE_SNAPSHOT_INTERNAL.md
@@ -0,0 +1,17 @@
+---
+title: DB4AI.PURGE_SNAPSHOT_INTERNAL
+summary: DB4AI.PURGE_SNAPSHOT_INTERNAL
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DB4AI.PURGE_SNAPSHOT_INTERNAL
+
+**PURGE_SNAPSHOT_INTERNAL** is a built-in execution function of the DB4AI.PURGE_SNAPSHOT function. The function involves information verification and cannot be directly invoked.
+
+**Table 1** DB4AI.PURGE_SNAPSHOT_INTERNAL input parameters and return values
+
+| Parameter | Type    | Description                          |
+| :-------- | :------ | :----------------------------------- |
+| i_schema  | IN NAME | Name of the schema storing snapshots |
+| i_name    | IN NAME | Snapshot name                        |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.SAMPLE_SNAPSHOT.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.SAMPLE_SNAPSHOT.md
new file mode 100644
index 0000000000000000000000000000000000000000..8f00b50f2ea22f596d22c11ae428b0a60187b6df
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.SAMPLE_SNAPSHOT.md
@@ -0,0 +1,22 @@
+---
+title: DB4AI.SAMPLE_SNAPSHOT
+summary: DB4AI.SAMPLE_SNAPSHOT
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DB4AI.SAMPLE_SNAPSHOT
+
+**SAMPLE_SNAPSHOT** samples basic data to generate snapshots for the DB4AI feature. You can invoke **SAMPLE SNAPSHOT** to implement this function.
+
+**Table 1** DB4AI.SAMPLE_SNAPSHOT input parameters and return values
+
+| Parameter         | Type                    | Description                                                |
+| :---------------- | :---------------------- | :--------------------------------------------------------- |
+| i_schema          | IN NAME                 | Name of the schema storing snapshots                       |
+| i_parent          | IN NAME                 | Parent snapshot name                                       |
+| i_sample_infixes  | IN NAME[]               | Sample snapshot name infix                                 |
+| i_sample_ratios   | IN NUMBER[]             | Size of each sample, which is used as the sample set ratio |
+| i_stratify        | IN NAME[]               | Layering strategy                                          |
+| i_sample_comments | IN TEXT[]               | Sample snapshot description                                |
+| res               | OUT db4ai.snapshot_name | Result                                                     |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.SNAPSHOT.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.SNAPSHOT.md
new file mode 100644
index 0000000000000000000000000000000000000000..4878d5c42567f93380c8a167149c0316d5572c43
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.SNAPSHOT.md
@@ -0,0 +1,28 @@
+---
+title: DB4AI.SNAPSHOT
+summary: DB4AI.SNAPSHOT
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DB4AI.SNAPSHOT
+
+DB4AI.SNAPSHOT records the snapshots stored by the current user through the DB4AI.SNAPSHOT feature.
+
+**Table 1** Attributes of the DB4AI.SNAPSHOT table
+
+| Name      | Type                        | Description                                                  | Instance                   |
+| :-------- | :-------------------------- | :----------------------------------------------------------- | :------------------------- |
+| id        | bigint                      | ID of the current snapshot                                   | 1                          |
+| parent_id | bigint                      | ID of the parent snapshot                                    | 0                          |
+| matrix_id | bigint                      | Matrix ID of the snapshot in CSS mode. Otherwise, the value is **NULL**. | 0                          |
+| root_id   | bigint                      | ID of the initial snapshot, which is constructed from the operated data using db4ai.create_snapshot(). | 0                          |
+| schema    | name                        | Schema for exporting the snapshot view                       | public                     |
+| name      | name                        | Snapshot name, including the version suffix                  | example0@1.1.0             |
+| owner     | name                        | Name of the user who creates the snapshot                    | nw                         |
+| commands  | text[]                      | A complete list of SQL statements that record how to generate this snapshot from its root snapshot | {DELETE,"WHERE id > 7"}    |
+| comment   | text                        | Snapshot description                                         | inherits from @1.0.0       |
+| published | boolean                     | **TRUE**, only when the snapshot has been published          | f                          |
+| archived  | boolean                     | **TRUE**, only when the snapshot has been archived           | f                          |
+| created   | timestamp without time zone | Timestamp marking the snapshot creation date                 | 2021-08-25 10:59:52.955604 |
+| row_count | bigint                      | Number of data rows in the snapshot                          | 8                          |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/overview-of-DB4AI-schema.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/overview-of-DB4AI-schema.md
new file mode 100644
index 0000000000000000000000000000000000000000..975a60c221db963d10153851f91f075b054f20be
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/overview-of-DB4AI-schema.md
@@ -0,0 +1,10 @@
+---
+title: Overview of DB4AI Schema
+summary: Overview of DB4AI Schema
+author: Guo Huan
+date: 2021-11-15
+---
+
+# Overview of DB4AI Schema
+
+The DB4AI schema is used to store and manage dataset versions in the AI feature. The schema holds a snapshot of the original view of the data tables, a change record for each data version, and management information for the version snapshot. This schema is intended for common users. In this schema, users can query the snapshot version information created by DB4AI.SNAPSHOT.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/DBE_PERF_overview.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/DBE_PERF_overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..abfcfe9a16d6e2994cb51e9807ff6019ecdfd283
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/DBE_PERF_overview.md
@@ -0,0 +1,40 @@
+---
+title: Overview
+summary: Overview
+author: Guo Huan
+date: 2021-04-19
+---
+
+# Overview
+
+In the **DBE_PERF** schema, views are used to diagnose performance issues and are also the data source of WDR snapshots. After the database is installed, only the initial user has the permission for the **DBE_PERF** schema by default. If the database is upgraded from an earlier version, the permission for the **DBE_PERF** schema needs to be the same as that of the earlier version to ensure forward compatibility. Organization views are divided based on multiple dimensions, such as OS, instance, and memory. These views need to comply with the following naming rules:
+
+- Views starting with **GLOBAL_**: Request data from database nodes and return the data without processing them.
+- Views starting with **SUMMARY_**: Summarize data in MogDB. In most cases, data from database nodes (sometimes only the primary database node) is processed, collected, and returned.
+- Views that do not start with **GLOBAL_** or **SUMMARY_**: Local views that do not request data from other database nodes.
+
+<br/>
+
+## Grant DBE_PERF Access Permission to Other Users
+
+If the following error occurs during the query of the views in the **DBE_PERF** schema, it means that the permission is not granted:
+
+```sql
+mogdb=> select * from dbe_perf.statement;
+permission denied for schema dbe_perf
+LINE 1: select * from dbe_perf.statement
+                      ^
+mogdb=> select * from dbe_perf.statement;
+ERROR:  only system/monitor admin can query unique sql view
+```
+
+The solution is as follows:
+
+Use the omm user to change the user who needs to access the **DBE_PERF** schema to the monitoring administrator. For example:
+
+```sql
+mogdb=# ALTER USER mogdb_usr MONADMIN;
+ALTER ROLE
+```
+
+A monitoring administrator is an account with the **MONADMIN** attribute that has the permission to view views and functions in the **DBE_PERF** schema and to grant or revoke the permission to or from objects in **DBE_PERF** schema. For more information about users and permissions, please refer to [Managing Users and Their Permissions](2-managing-users-and-their-permissions).
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-1.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-1.md
new file mode 100644
index 0000000000000000000000000000000000000000..e41162b78f1037f78822b91e53da498db6116c2e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-1.md
@@ -0,0 +1,48 @@
+---
+title: Table 1
+summary: Table 1
+author: Guo Huan
+date: 2021-04-19
+---
+
+**Table 1** Waiting status list<a id="Table1"> </a>
+
+| Value                                   | Description                                                  |
+| :-------------------------------------- | :----------------------------------------------------------- |
+| none                                    | Waiting for no event                                         |
+| acquire lock                            | Waiting for locking until the locking succeeds or times out  |
+| acquire lwlock                          | Waiting for a lightweight lock                               |
+| wait io                                 | Waiting for I/O completion                                   |
+| wait cmd                                | Waiting for reading network communication packets to complete |
+| wait pooler get conn                    | Waiting for the pooler to obtain the connection              |
+| wait pooler abort conn                  | Waiting for the pooler to terminate the connection           |
+| wait pooler clean conn                  | Waiting for the pooler to clear connections                  |
+| pooler create conn: [nodename], total N | Waiting for the pooler to set up a connection. The connection is being established with the node specified by **nodename**, and there are *N* connections waiting to be set up. |
+| get conn                                | Obtaining the connection to other nodes                      |
+| set cmd: [nodename]                     | Waiting for running the **SET**, **RESET**, **TRANSACTION BLOCK LEVEL PARA SET**, or **SESSION LEVEL PARA SET** statement on the connection. The statement is being executed on the node specified by **nodename**. |
+| cancel query                            | Canceling the SQL statement that is being executed through the connection |
+| stop query                              | Stopping the query that is being executed through the connection |
+| wait node: nodename, total N, [phase]   | Waiting for receiving data from a connected node. The thread is waiting for data from the plevel thread of the node specified by **nodename**. The data of *N* connections is waiting to be returned. If *phase* is included, the possible phases are as follows:<br/>- **begin**: The transaction is being started.<br/>- **commit**: The transaction is being committed.<br/>- **rollback**: The transaction is being rolled back. |
+| wait transaction sync: xid              | Waiting for synchronizing the transaction specified by **xid** |
+| wait wal sync                           | Waiting for the completion of WAL of synchronization from the specified LSN to the standby instance |
+| wait data sync                          | Waiting for the completion of data page synchronization to the standby instance |
+| wait data sync queue                    | Waiting for putting the data pages that are in the row-store or the CU in the column-store into the synchronization queue |
+| flush data: nodename, [phase]           | Waiting for sending data to the plevel thread of the node specified by **nodename**. If **phase** is included, the possible phase is **wait quota**, indicating that the current communication flow is waiting for the quota value. |
+| stream get conn: [nodename], total N    | Waiting for connecting to the consumer object of the node specified by **nodename** when the stream flow is initialized. There are *N* consumers waiting to be connected. |
+| wait producer ready: nodename, total N  | Waiting for each producer to be ready when the stream flow is initialized. The thread is waiting for the procedure of the plevel thread on the **nodename** node to be ready. There are **N** producers waiting to be ready. |
+| synchronize quit                        | Waiting for the threads in the stream thread group to quit when the stream plan ends |
+| wait stream nodegroup destroy           | Waiting for destroying the stream node group when the stream plan ends |
+| wait active statement                   | Waiting for job execution under resource and load control    |
+| analyze: [relname], [phase]             | The thread is doing **ANALYZE** to the **relname** table. If **phase** is included, the possible phase is **autovacuum**, indicating that the database automatically enables the AutoVacuum thread to execute **ANALYZE**. |
+| vacuum: [relname], [phase]              | The thread is doing **VACUUM** to the **relname** table. If **phase** is included, the possible phase is **autovacuum**, indicating that the database automatically enables the AutoVacuum thread to execute **VACUUM**. |
+| vacuum full: [relname]                  | The thread is doing **VACUUM FULL** to the **relname** table. |
+| create index                            | An index is being created.                                   |
+| HashJoin - [ build hash \| write file ] | The **HashJoin** operator is being executed. In this phase, you need to pay attention to the execution time-consuming.<br/>- **build hash**: The **HashJoin** operator is creating a hash table.<br/>- **write file**: The **HashJoin** operator is writing data to disks. |
+| HashAgg - [ build hash \| write file ]  | The **HashAgg** operator is being executed. In this phase, you need to pay attention to the execution time-consuming.<br/>- **build hash**: The **HashAgg** operator is creating a hash table.<br/>- **write file**: The **HashAgg** operator is writing data to disks. |
+| HashSetop - [build hash \| write file ] | The **HashSetop** operator is being executed. In this phase, you need to pay attention to the execution time-consuming.<br/>- **build hash**: The **HashSetop** operator is creating a hash table.<br/>- **write file**: The **HashSetop** operator is writing data to disks. |
+| Sort \| Sort - write file               | The **Sort** operator is being executed. **write file** indicates that the **Sort** operator is writing data to disks. |
+| Material \| Material - write file       | The **Material** operator is being executed. **write file** indicates that the **Material** operator is writing data to disks. |
+| NestLoop                                | The **NestLoop** operator is being executed.                 |
+| wait memory                             | Waiting for obtaining the memory                             |
+| wait sync consumer next step            | Waiting for the consumer to execute the stream operator      |
+| wait sync producer next step            | Waiting for the producer to execute the stream operator      |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-2.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-2.md
new file mode 100644
index 0000000000000000000000000000000000000000..75fbf968ef442e65fec4c1a79ad8da06dcafb6e0
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-2.md
@@ -0,0 +1,131 @@
+---
+title: Table 2
+summary: Table 2
+author: Guo Huan
+date: 2021-04-19
+---
+
+**Table 2** List of wait events corresponding to lightweight locks<a id="Table2"> </a>
+
+| wait_event                               | Description                                                  |
+| :--------------------------------------- | :----------------------------------------------------------- |
+| ShmemIndexLock                           | Used to protect the primary index table, a hash table, in shared memory. |
+| OidGenLock                               | Used to prevent different threads from generating the same OID. |
+| XidGenLock                               | Used to prevent two transactions from obtaining the same transaction ID. |
+| ProcArrayLock                            | Used to prevent concurrent access to or concurrent modification on ProcArray shared arrays. |
+| SInvalReadLock                           | Used to prevent concurrent execution with invalid message deletion. |
+| SInvalWriteLock                          | Used to prevent concurrent execution with invalid message write and deletion. |
+| WALInsertLock                            | Used to prevent concurrent execution with WAL insertion.     |
+| WALWriteLock                             | Used to prevent concurrent write from a WAL buffer to a disk. |
+| ControlFileLock                          | Used to prevent concurrent read/write or concurrent write/write on the **pg_control** file. |
+| CheckpointLock                           | Used to prevent multi-checkpoint concurrent execution.       |
+| CLogControlLock                          | Used to prevent concurrent access to or concurrent modification on the Clog control data structure. |
+| SubtransControlLock                      | Used to prevent concurrent access to or concurrent modification on the subtransaction control data structure. |
+| MultiXactGenLock                         | Used to allocate a unique MultiXact ID in serial mode.       |
+| MultiXactOffsetControlLock               | Used to prevent concurrent read/write or concurrent write/write on **pg_multixact/offset**. |
+| MultiXactMemberControlLock               | Used to prevent concurrent read/write or concurrent write/write on **pg_multixact/members**. |
+| RelCacheInitLock                         | Used to add a lock before any operations are performed on the **init** file when messages are invalid. |
+| CheckpointerCommLock                     | Used to send file flush requests to a checkpointer. The request structure needs to be inserted to a request queue in serial mode. |
+| TwoPhaseStateLock                        | Used to prevent concurrent access to or modification on two-phase information sharing arrays. |
+| TablespaceCreateLock                     | Used to check whether a tablespace already exists.           |
+| BtreeVacuumLock                          | Used to prevent **VACUUM** from clearing pages that are being used by B-tree indexes. |
+| AutovacuumLock                           | Used to access the autovacuum worker array in serial mode.   |
+| AutovacuumScheduleLock                   | Used to distribute tables requiring **VACUUM** in serial mode. |
+| AutoanalyzeLock                          | Used to obtain and release resources related to a task that allows for autoanalyze execution. |
+| SyncScanLock                             | Used to determine the start position of a relfilenode during heap scanning. |
+| NodeTableLock                            | Used to protect a shared structure that stores database node information. |
+| PoolerLock                               | Used to prevent two threads from simultaneously obtaining the same connection from a connection pool. |
+| RelationMappingLock                      | Used to wait for the mapping file between system catalogs and storage locations to be updated. |
+| AsyncCtlLock                             | Used to prevent concurrent access to or concurrent modification on the sharing notification status. |
+| AsyncQueueLock                           | Used to prevent concurrent access to or concurrent modification on the sharing notification queue. |
+| SerializableXactHashLock                 | Used to prevent concurrent read/write or concurrent write/write on a sharing structure for serializable transactions. |
+| SerializableFinishedListLock             | Used to prevent concurrent read/write or concurrent write/write on a shared linked list for completed serial transactions. |
+| SerializablePredicateLockListLock        | Used to protect a linked list of serializable transactions that have locks. |
+| OldSerXidLock                            | Used to protect a structure that records serializable transactions that have conflicts. |
+| FileStatLock                             | Used to protect a data structure that stores statistics file information. |
+| SyncRepLock                              | Used to protect Xlog synchronization information during primary/standby replication. |
+| DataSyncRepLock                          | Used to protect data page synchronization information during primary/standby replication. |
+| CStoreColspaceCacheLock                  | Used to add a lock when CU space is allocated for a column-store table. |
+| CStoreCUCacheSweepLock                   | Used to add a lock when CU caches used by a column-store table are cyclically washed out. |
+| MetaCacheSweepLock                       | Used to add a lock when metadata is cyclically washed out.   |
+| ExtensionConnectorLibLock                | Adds a lock when a specific dynamic library is loaded or uninstalled in ODBC connection initialization scenarios. |
+| SearchServerLibLock                      | Used to add a lock on the file read operation when a specific dynamic library is initially loaded in GPU-accelerated scenarios. |
+| LsnXlogChkFileLock                       | Used to serially update the Xlog flush points for primary and standby servers recorded in a specific structure. |
+| ReplicationSlotAllocationLock            | Used to add a lock when a primary server allocates stream replication slots during primary/standby replication. |
+| ReplicationSlotControlLock               | Used to prevent concurrent update of stream replication slot status during primary/standby replication. |
+| ResourcePoolHashLock                     | Used to prevent concurrent access to or concurrent modification on a resource pool table, a hash table. |
+| WorkloadStatHashLock                     | Used to prevent concurrent access to or concurrent modification on a hash table that contains SQL requests from the primary node of the database side. |
+| WorkloadIoStatHashLock                   | Used to prevent concurrent access to or concurrent modification on a hash table that contains I/O information of the current database node. |
+| WorkloadCGroupHashLock                   | Used to prevent concurrent access to or concurrent modification on a hash table that contains Cgroup information. |
+| OBSGetPathLock                           | Used to prevent concurrent read/write or concurrent write/write on an OBS path. |
+| WorkloadUserInfoLock                     | Used to prevent concurrent access to or concurrent modification on a hash table that contains user information about load management. |
+| WorkloadRecordLock                       | Used to prevent concurrent access to or concurrent modification on a hash table that contains requests received by the primary node of the databases during adaptive memory management. |
+| WorkloadIOUtilLock                       | Used to protect a structure that records **iostat** and CPU load information. |
+| WorkloadNodeGroupLock                    | Used to prevent concurrent access to or concurrent modification on a hash table that contains node group information in memory. |
+| JobShmemLock                             | Used to protect global variables in the shared memory that is periodically read during a scheduled task. |
+| OBSRuntimeLock                           | Used to obtain environment variables, for example, **GASSHOME**. |
+| LLVMDumpIRLock                           | Used to export the assembly language for dynamically generating functions. |
+| LLVMParseIRLock                          | Used to compile and parse a finished IR function from the IR file at the start position of a query. |
+| CriticalCacheBuildLock                   | Used to load caches from a shared or local cache initialization file. |
+| WaitCountHashLock                        | Used to protect a shared structure in user statement counting scenarios. |
+| BufMappingLock                           | Used to protect operations on a shared-buffer mapping table. |
+| LockMgrLock                              | Used to protect the information about a common lock structure. |
+| PredicateLockMgrLock                     | Used to protect the information about a lock structure that has serializable transactions. |
+| OperatorRealTLock                        | Used to prevent concurrent access to or concurrent modification on a global structure that contains real-time data at the operator level. |
+| OperatorHistLock                         | Used to prevent concurrent access to or concurrent modification on a global structure that contains historical data at the operator level. |
+| SessionRealTLock                         | Used to prevent concurrent access to or concurrent modification on a global structure that contains real-time data at the query level. |
+| SessionHistLock                          | Used to prevent concurrent access to or concurrent modification on a global structure that contains historical data at the query level. |
+| CacheSlotMappingLock                     | Used to protect global CU cache information.                 |
+| BarrierLock                              | Used to ensure that only one thread is creating a barrier at a time. |
+| dummyServerInfoCacheLock                 | Used to protect a global hash table where the information about MogDB connections is cached. |
+| RPNumberLock                             | Used by a database node on a computing MogDB to count the number of threads for a task where plans are being executed. |
+| ClusterRPLock                            | Used to control concurrent access on MogDB load data maintained in a CCN of MogDB. |
+| CBMParseXlogLock                         | Used to protect the lock used when CBM parses Xlogs.         |
+| RelfilenodeReuseLock                     | Used to prevent the link to a reused column attribute file from being canceled by mistake. |
+| RcvWriteLock                             | Used to prevent concurrent call of **WalDataRcvWrite**.      |
+| PercentileLock                           | Used to protect global percentile buffers.                   |
+| CSNBufMappingLock                        | Used to protect CSN pages.                                   |
+| UniqueSQLMappingLock                     | Used to protect a unique SQL hash table.                     |
+| DelayDDLLock                             | Used to prevent concurrent DDL operations.                   |
+| CLOG Ctl                                 | Used to prevent concurrent access to or concurrent modification on the Clog control data structure. |
+| Async Ctl                                | Used to protect asynchronization buffers.                    |
+| MultiXactOffset Ctl                      | Used to protect SLRU buffers of a MultiXact offset.          |
+| MultiXactMember Ctl                      | Used to protect SLRU buffer of a MultiXact member.           |
+| OldSerXid SLRU Ctl                       | Used to protect SLRU buffers of old transaction IDs.         |
+| ReplicationSlotLock                      | Used to protect a replication slot.                          |
+| PGPROCLock                               | Used to protect the PGPROC structure.                        |
+| MetaCacheLock                            | Used to protect meta caches.                                 |
+| DataCacheLock                            | Used to protect data caches.                                 |
+| InstrUserLock                            | Used to protect a user hash table.                           |
+| BadBlockStatHashLock                     | Used to protect the hash table **global_bad_block_stat**     |
+| BufFreelistLock                          | Used to ensure the atomicity of free list operations in the shared buffer. |
+| CUSlotListLock                           | Used to control concurrent operations on the slot of the column-store buffer. |
+| AddinShmemInitLock                       | Used to protect the initialization of the shared memory object. |
+| AlterPortLock                            | Used to protect the coordinator node from changing the registration port number. |
+| FdwPartitionCaheLock                     | Management lock of the buffer of the HDFS partitioned table. |
+| DfsConnectorCacheLock                    | Management lock of the DFSConnector buffer.                  |
+| DfsSpaceCacheLock                        | Management lock of the HDFS tablespace management buffer.    |
+| FullBuildXlogCopyStartPtrLock            | Used to protect Xlog copy operations in the full build.      |
+| DfsUserLoginLock                         | Used for HDFS user login and authentication.                 |
+| LogicalReplicationSlotPersistentDataLock | Used to protect data in the replication slot during logical replication. |
+| WorkloadSessionInfoLock                  | Used to protect the access to the session info memory hash table of the load management module. |
+| InstrWorkloadLock                        | Used to protect the access to the memory hash table that stores load management statistics. |
+| PgfdwLock                                | Used by the management instance to establish a connection to the foreign server. |
+| InstanceTimeLock                         | Used to obtain time information of sessions in an instance.  |
+| XlogRemoveSegLock                        | Used to protect Xlog segment file recycling.                 |
+| DnUsedSpaceHashLock                      | Used to update space usage information corresponding to a session. |
+| CsnMinLock                               | Used to calculate CSNmin.                                    |
+| GPCCommitLock                            | Used to protect the addition of the global Plan Cache hash table. |
+| GPCClearLock                             | Used to protect the clearing of the global plan cache hash table. |
+| GPCTimelineLock                          | Used to protect the timeline check of the global plan cache hash table. |
+| TsTagsCacheLock                          | Used to manage the time series tag cache.                    |
+| InstanceRealTLock                        | Used to protect the update of the hash table that stores shared instance statistics. |
+| CLogBufMappingLock                       | Used to manage the cache of commit logs.                     |
+| GPCMappingLock                           | Used to manage the global plan cache.                        |
+| GPCPrepareMappingLock                    | Used to manage the global plan cache.                        |
+| BufferIOLock                             | Used to protect I/O operations on pages in the shared buffer. |
+| BufferContentLock                        | Used to protect the read and modification of the page content in the shared buffer. |
+| CSNLOG Ctl                               | Used for CSN log management.                                 |
+| DoubleWriteLock                          | Used to manage doublewrite operations.                       |
+| RowPageReplicationLock                   | Used to manage data page replication of row-store.           |
+| extension                                | Other lightweight locks                                      |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-3.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-3.md
new file mode 100644
index 0000000000000000000000000000000000000000..94c8cb92c1dad731ec2a19246f0926ab439ddbc2
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-3.md
@@ -0,0 +1,71 @@
+---
+title: Table 3
+summary: Table 3
+author: Guo Huan
+date: 2021-04-19
+---
+
+**Table 3** List of wait events corresponding to I/Os<a id="Table3"> </a>
+
+| wait_event                 | Description                                                  |
+| :------------------------- | :----------------------------------------------------------- |
+| BufFileRead                | Reads data from a temporary file to a specified buffer.      |
+| BufFileWrite               | Writes the content of a specified buffer to a temporary file. |
+| ControlFileRead            | Reads the **pg_control** file, mainly during database startup, checkpoint execution, and primary/standby verification. |
+| ControlFileSync            | Flushes the **pg_control** file to a disk, mainly during database initialization. |
+| ControlFileSyncUpdate      | Flushes the **pg_control** file to a disk, mainly during database startup, checkpoint execution, and primary/standby verification. |
+| ControlFileWrite           | Writes the **pg_control** file, mainly during database initialization. |
+| ControlFileWriteUpdate     | Updates the **pg_control** file, mainly during database startup, checkpoint execution, and primary/standby verification. |
+| CopyFileRead               | Reads a file during file copying.                            |
+| CopyFileWrite              | Writes a file during file copying.                           |
+| DataFileExtend             | Writes a file during file extension.                         |
+| DataFileFlush              | Flushes a table data file to a disk.                         |
+| DataFileImmediateSync      | Flushes a table data file to a disk immediately.             |
+| DataFilePrefetch           | Reads a table data file asynchronously.                      |
+| DataFileRead               | Reads a table data file synchronously.                       |
+| DataFileSync               | Flushes table data file modifications to a disk.             |
+| DataFileTruncate           | Truncates a table data file.                                 |
+| DataFileWrite              | Writes a table data file.                                    |
+| LockFileAddToDataDirRead   | Reads the **postmaster.pid** file.                           |
+| LockFileAddToDataDirSync   | Flushes the **postmaster.pid** file to a disk.               |
+| LockFileAddToDataDirWrite  | Writes PID information into the **postmaster.pid** file.     |
+| LockFileCreateRead         | Read the LockFile file **%s.lock**.                          |
+| LockFileCreateSync         | Flushes the LockFile file **%s.lock** to a disk.             |
+| LockFileCreateWRITE        | Writes PID information into the LockFile file **%s.lock**.   |
+| RelationMapRead            | Reads the mapping file between system catalogs and storage locations. |
+| RelationMapSync            | Flushes the mapping file between system catalogs and storage locations to a disk. |
+| RelationMapWrite           | Writes the mapping file between system catalogs and storage locations. |
+| ReplicationSlotRead        | Reads a stream replication slot file during a restart.       |
+| ReplicationSlotRestoreSync | Flushes a stream replication slot file to a disk during a restart. |
+| ReplicationSlotSync        | Flushes a temporary stream replication slot file to a disk during checkpoint execution. |
+| ReplicationSlotWrite       | Writes a temporary stream replication slot file during checkpoint execution. |
+| SLRUFlushSync              | Flushes the **pg_clog**, **pg_subtrans**, and **pg_multixact** files to a disk, mainly during checkpoint execution and database shutdown. |
+| SLRURead                   | Reads the **pg_clog**, **pg_subtrans**, and **pg_multixact** files. |
+| SLRUSync                   | Writes dirty pages into the **pg_clog**, **pg_subtrans**, and **pg_multixact** files, and flushes the files to a disk, mainly during checkpoint execution and database shutdown. |
+| SLRUWrite                  | Writes the **pg_clog**, **pg_subtrans**, and **pg_multixact** files. |
+| TimelineHistoryRead        | Reads the timeline history file during database startup.     |
+| TimelineHistorySync        | Flushes the timeline history file to a disk during database startup. |
+| TimelineHistoryWrite       | Writes to the timeline history file during database startup. |
+| TwophaseFileRead           | Reads the **pg_twophase** file, mainly during two-phase transaction commit and restoration. |
+| TwophaseFileSync           | Flushes the **pg_twophase** file to a disk, mainly during two-phase transaction commit and restoration. |
+| TwophaseFileWrite          | Writes the **pg_twophase** file, mainly during two-phase transaction commit and restoration. |
+| WALBootstrapSync           | Flushes an initialized WAL file to a disk during database initialization. |
+| WALBootstrapWrite          | Writes an initialized WAL file during database initialization. |
+| WALCopyRead                | Read operation generated when an existing WAL file is read for replication after archiving and restoration. |
+| WALCopySync                | Flushes a replicated WAL file to a disk after archiving and restoration. |
+| WALCopyWrite               | Write operation generated when an existing WAL file is read for replication after archiving and restoration. |
+| WALInitSync                | Flushes a newly initialized WAL file to a disk during log reclaiming or writing. |
+| WALInitWrite               | Initializes a newly created WAL file to **0** during log reclaiming or writing. |
+| WALRead                    | Reads data from Xlogs during redo operations on two-phase files. |
+| WALSyncMethodAssign        | Flushes all open WAL files to a disk.                        |
+| WALWrite                   | Writes a WAL file.                                           |
+| WALBufferAccess            | WAL Buffer access (for performance reasons, only the number of accesses are counted in the kernel code, and the access time is not counted). |
+| WALBufferFull              | When the WAL Buffer is full, write wal file related processing. |
+| DoubleWriteFileRead        | Doublewrites and reads a file.                               |
+| DoubleWriteFileSync        | Doublewrites a file and forcibly flushes files to disks.     |
+| DoubleWriteFileWrite       | Doublewrites a file and writes a file.                       |
+| PredoProcessPending        | Waits for the playback of other records to complete during parallel log playback. |
+| PredoApply                 | Waits for other threads to play back logs to the LSN of the current thread during parallel log playback. |
+| DisableConnectFileRead     | Reads the HA lock fragment logic file.                       |
+| DisableConnectFileSync     | Forcibly flushes the HA lock fragment logic file to disks.   |
+| DisableConnectFileWrite    | Writes the HA lock fragment logic file.                      |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-4.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-4.md
new file mode 100644
index 0000000000000000000000000000000000000000..99a88b86e586a08c8e75d54780b51333df2e2912
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-4.md
@@ -0,0 +1,23 @@
+---
+title: Table 4
+summary: Table 4
+author: Guo Huan
+date: 2021-04-19
+---
+
+**Table 4** List of wait events corresponding to transaction locks<a id="Table4"> </a>
+
+| wait_event       | Description                                        |
+| :--------------- | :------------------------------------------------- |
+| relation         | Adds a lock to a table.                            |
+| extend           | Adds a lock to a table being scaled out.           |
+| partition        | Adds a lock to a partitioned table.                |
+| partition_seq    | Adds a lock to a partition of a partitioned table. |
+| page             | Adds a lock to a table page.                       |
+| tuple            | Adds a lock to a tuple on a page.                  |
+| transactionid    | Adds a lock to a transaction ID.                   |
+| virtualxid       | Adds a lock to a virtual transaction ID.           |
+| object           | Adds a lock to an object.                          |
+| cstore_freespace | Adds a lock to idle column-store space.            |
+| userlock         | Adds a lock to a user.                             |
+| advisory         | Adds an advisory lock.                             |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-5.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-5.md
new file mode 100644
index 0000000000000000000000000000000000000000..5dad16370885df0ee8d0711325f78d375cfdf1bd
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-5.md
@@ -0,0 +1,79 @@
+---
+title: Table 5
+summary: Table 5
+author: Guo Huan
+date: 2021-04-19
+---
+
+**Table 5** GS_WLM_SESSION_HISTORY columns <a id="Table5"> </a>
+
+| Name                | Type                     | Description                                                  |
+| :------------------ | :----------------------- | :----------------------------------------------------------- |
+| datid               | oid                      | OID of the database that the backend is connected to         |
+| dbname              | text                     | Name of the database that the backend is connected to        |
+| schemaname          | text                     | Schema name                                                  |
+| nodename            | text                     | Name of the database node where the statement is executed    |
+| username            | text                     | Username used for connecting to the backend                  |
+| application_name    | text                     | Name of the application connected to the backend             |
+| client_addr         | inet                     | IP address of the client connected to the backend. If this column is null, it indicates either the client is connected via a Unix socket on the server or this is an internal process, such as autovacuum. |
+| client_hostname     | text                     | Host name of the connected client, as reported by a reverse DNS lookup of **client\_addr**. This column will be non-null only for IP connections and only when **log_hostname** is enabled. |
+| client_port         | integer                  | TCP port number that the client uses for communication with this backend (**-1** if a Unix socket is used) |
+| query_band          | text                     | Job type, which is specified by the GUC parameter **query_band**. The default value is a null string. |
+| block_time          | bigint                   | Duration that the statement is blocked before being executed, including the statement parsing and optimization duration (unit: ms) |
+| start_time          | timestamp with time zone | Time when the statement starts to be executed                |
+| finish_time         | timestamp with time zone | Time when the statement execution ends                       |
+| duration            | bigint                   | Execution time of the statement, in ms                       |
+| estimate_total_time | bigint                   | Estimated execution time of the statement, in ms             |
+| status              | text                     | Final statement execution status, which can be **finished** (normal) or **aborted** (abnormal). |
+| abort_info          | text                     | Exception information displayed if the final statement execution status is **aborted** |
+| resource_pool       | text                     | Resource pool used by the user                               |
+| control_group       | text                     | The function is not supported currently.                     |
+| estimate_memory     | integer                  | Estimated memory size of the statement.                      |
+| min_peak_memory     | integer                  | Minimum memory peak of the statement across the database nodes, in MB |
+| max_peak_memory     | integer                  | Maximum memory peak of the statement across the database nodes, in MB |
+| average_peak_memory | integer                  | Average memory usage during statement execution (unit: MB)   |
+| memory_skew_percent | integer                  | Memory usage skew of the statement among the database nodes  |
+| spill_info          | text                     | Information about statement spill to the database nodes<br/>- **None**: The statement has not been spilled to disks on the database nodes.<br/>- **All**: The statement has been spilled to disks on the database nodes.<br/>- **[a:b]**: The statement has been spilled to disks on **a** of **b** database nodes. |
+| min_spill_size      | integer                  | Minimum spilled data among database nodes when a spill occurs, in MB (default value:**0**) |
+| max_spill_size      | integer                  | Maximum spilled data among database nodes when a spill occurs, in MB (default value:**0**) |
+| average_spill_size  | integer                  | Average spilled data among database nodes when a spill occurs, in MB (default value:**0**) |
+| spill_skew_percent  | integer                  | database node spill skew when a spill occurs                 |
+| min_dn_time         | bigint                   | Minimum execution time of the statement across the database nodes, in ms |
+| max_dn_time         | bigint                   | Maximum execution time of the statement across the database nodes, in ms |
+| average_dn_time     | bigint                   | Average execution time of the statement across the database nodes, in ms |
+| dntime_skew_percent | integer                  | Execution time skew of the statement among the database nodes |
+| min_cpu_time        | bigint                   | Minimum CPU time of the statement across the database nodes, in ms |
+| max_cpu_time        | bigint                   | Maximum CPU time of the statement across the database nodes, in ms |
+| total_cpu_time      | bigint                   | Total CPU time of the statement across the database nodes, in ms |
+| cpu_skew_percent    | integer                  | CPU time skew of the statement among database nodes          |
+| min_peak_iops       | integer                  | Minimum IOPS peak of the statement across the database nodes. It is counted by ones in a column-store table and by ten thousands in a row-store table. |
+| max_peak_iops       | integer                  | Maximum IOPS peak of the statement across the database nodes. It is counted by ones in a column-store table and by ten thousands in a row-store table. |
+| average_peak_iops   | integer                  | Average IOPS peak of the statement across the database nodes. It is counted by ones in a column-store table and by ten thousands in a row-store table. |
+| iops_skew_percent   | integer                  | I/O skew across database nodes                               |
+| warning             | text                     | Warning. The following warnings are displayed:<br/>- Spill file size large than 256MB<br/>- Broadcast size large than 100MB<br/>- Early spill<br/>- Spill times is greater than 3<br/>- Spill on memory adaptive<br/>- Hash table conflict |
+| queryid             | bigint                   | Internal query ID used for statement execution               |
+| query               | text                     | Statement executed                                           |
+| query_plan          | text                     | Execution plan of the statement                              |
+| node_group          | text                     | Unsupported currently                                        |
+| cpu_top1_node_name  | text                     | Name of the current database node                            |
+| cpu_top2_node_name  | text                     | Unsupported currently                                        |
+| cpu_top3_node_name  | text                     | Unsupported currently                                        |
+| cpu_top4_node_name  | text                     | Unsupported currently                                        |
+| cpu_top5_node_name  | text                     | Unsupported currently                                        |
+| mem_top1_node_name  | text                     | Current database name                                        |
+| mem_top2_node_name  | text                     | Unsupported currently                                        |
+| mem_top3_node_name  | text                     | Unsupported currently                                        |
+| mem_top4_node_name  | text                     | Unsupported currently                                        |
+| mem_top5_node_name  | text                     | Unsupported currently                                        |
+| cpu_top1_value      | bigint                   | CPU usage of the current database node                       |
+| cpu_top2_value      | bigint                   | Unsupported currently                                        |
+| cpu_top3_value      | bigint                   | Unsupported currently                                        |
+| cpu_top4_value      | bigint                   | Unsupported currently                                        |
+| cpu_top5_value      | bigint                   | Unsupported currently                                        |
+| mem_top1_value      | bigint                   | Memory usage of the current database node                    |
+| mem_top2_value      | bigint                   | Unsupported currently                                        |
+| mem_top3_value      | bigint                   | Unsupported currently                                        |
+| mem_top4_value      | bigint                   | Unsupported currently                                        |
+| mem_top5_value      | bigint                   | Unsupported currently                                        |
+| top_mem_dn          | text                     | Memory usage information of the current database node        |
+| top_cpu_dn          | text                     | CPU usage information of the current database node           |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-6.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-6.md
new file mode 100644
index 0000000000000000000000000000000000000000..fbb4e67af0a00e7d1417a2bc9901b985ff8e8b57
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-6.md
@@ -0,0 +1,33 @@
+---
+title: Table 6
+summary: Table 6
+author: Guo Huan
+date: 2021-04-19
+---
+
+**Table 6** GS_WLM_OPERATOR_INFO columns<a id="Table6"> </a>
+
+| Name                | Type                     | Description                                                  |
+| :------------------ | :----------------------- | :----------------------------------------------------------- |
+| queryid             | bigint                   | Internal query ID used for statement execution               |
+| pid                 | bigint                   | Thread ID of the backend                                     |
+| plan_node_id        | integer                  | Plan node ID of the execution plan of a query                |
+| plan_node_name      | text                     | Name of the operator corresponding to the plan node ID       |
+| start_time          | timestamp with time zone | Time when an operator starts to process the first data record |
+| duration            | bigint                   | Total execution time of the operator, in ms                  |
+| query_dop           | integer                  | DOP of the operator                                          |
+| estimated_rows      | bigint                   | Number of rows estimated by the optimizer                    |
+| tuple_processed     | bigint                   | Number of elements returned by the operator                  |
+| min_peak_memory     | integer                  | Minimum peak memory used by the operator on database nodes (unit: MB) |
+| max_peak_memory     | integer                  | Maximum peak memory used by the operator on database nodes (unit: MB) |
+| average_peak_memory | integer                  | Average peak memory used by the operator on database nodes (unit: MB) |
+| memory_skew_percent | integer                  | Memory usage skew of the operator among database nodes       |
+| min_spill_size      | integer                  | Minimum spilled data among database nodes when a spill occurs (unit: MB) (default value:**0**) |
+| max_spill_size      | integer                  | Maximum spilled data among database nodes when a spill occurs (unit: MB) (default value:**0**) |
+| average_spill_size  | integer                  | Average spilled data among database nodes when a spill occurs (unit: MB) (default value:**0**) |
+| spill_skew_percent  | integer                  | Database node spill skew when a spill occurs                 |
+| min_cpu_time        | bigint                   | Minimum execution time of the operator on database nodes (unit: ms) |
+| max_cpu_time        | bigint                   | Maximum execution time of the operator on database nodes (unit: ms) |
+| total_cpu_time      | bigint                   | Total execution time of the operator on database nodes (unit: ms) |
+| cpu_skew_percent    | integer                  | Execution time skew among database nodes                     |
+| warning             | text                     | The following warnings are displayed:<br/>- Sort/SetOp/HashAgg/HashJoin spill<br/>- Spill file size large than 256MB<br/>- Broadcast size large than 100MB<br/>- Early spill<br/>- Spill times is greater than 3<br/>- Spill on memory adaptive<br/>- Hash table conflict |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_ALL_INDEXES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_ALL_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..f42286104db137f8070e414ddf5f9fa5aa6d1342
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_ALL_INDEXES.md
@@ -0,0 +1,23 @@
+---
+title: GLOBAL_STATIO_ALL_INDEXES
+summary: GLOBAL_STATIO_ALL_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STATIO_ALL_INDEXES
+
+**GLOBAL_STATIO_ALL_INDEXES** contains one row for each index in databases on each node, showing I/O statistics about specific indexes.
+
+**Table 1** GLOBAL_STATIO_ALL_INDEXES columns
+
+| **Name**      | **Type** | **Description**                                 |
+| :------------ | :------- | :---------------------------------------------- |
+| node_name     | name     | Node name                                       |
+| relid         | oid      | OID of the table that the index is created for  |
+| indexrelid    | oid      | OID of the index                                |
+| schemaname    | name     | Name of the schema that the index is in         |
+| relname       | name     | Name of the table that the index is created for |
+| indexrelname  | name     | Index name                                      |
+| idx_blks_read | numeric  | Number of disk blocks read from the index       |
+| idx_blks_hit  | numeric  | Number of cache hits in the index               |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_ALL_SEQUENCES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_ALL_SEQUENCES.md
new file mode 100644
index 0000000000000000000000000000000000000000..30b2f4ba88e185fd5548bc4ac8d768bbc00f07e7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_ALL_SEQUENCES.md
@@ -0,0 +1,21 @@
+---
+title: GLOBAL_STATIO_ALL_SEQUENCES
+summary: GLOBAL_STATIO_ALL_SEQUENCES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STATIO_ALL_SEQUENCES
+
+**GLOBAL_STATIO_ALL_SEQUENCES** contains every row of each sequence in databases on each node, showing I/O statistics about specific sequences.
+
+**Table 1** GLOBAL_STATIO_ALL_SEQUENCES columns
+
+| **Name**   | **Type** | **Description**                              |
+| :--------- | :------- | :------------------------------------------- |
+| node_name  | name     | Node name                                    |
+| relid      | oid      | OID of the sequence                          |
+| schemaname | name     | Name of the schema that the sequence is in   |
+| relname    | name     | Sequence name                                |
+| blks_read  | bigint   | Number of disk blocks read from the sequence |
+| blks_hit   | bigint   | Number of cache hits in the sequence         |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_ALL_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_ALL_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..7e0f7d62c3b1b2d29b2f3614bd1702aa227501cc
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_ALL_TABLES.md
@@ -0,0 +1,27 @@
+---
+title: GLOBAL_STATIO_ALL_TABLES
+summary: GLOBAL_STATIO_ALL_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STATIO_ALL_TABLES
+
+**GLOBAL_STATIO_ALL_TABLES** contains I/O statistics about each table (including TOAST tables) in databases on each node.
+
+**Table 1** GLOBAL_STATIO_ALL_TABLES columns
+
+| **Name**        | **Type** | **Description**                                              |
+| :-------------- | :------- | :----------------------------------------------------------- |
+| node_name       | name     | Node name                                                    |
+| relid           | oid      | Table OID                                                    |
+| schemaname      | name     | Name of the schema that contains the table                   |
+| relname         | name     | Table name                                                   |
+| heap_blks_read  | bigint   | Number of disk blocks read from the table                    |
+| heap_blks_hit   | bigint   | Number of cache hits in the table                            |
+| idx_blks_read   | bigint   | Number of disk blocks read from all indexes in the table     |
+| idx_blks_hit    | bigint   | Number of cache hits in the table                            |
+| toast_blks_read | bigint   | Number of disk blocks read from the TOAST table (if any) in the table |
+| toast_blks_hit  | bigint   | Number of buffer hits in the TOAST table (if any) in the table |
+| tidx_blks_read  | bigint   | Number of disk blocks read from the TOAST table index (if any) in the table |
+| tidx_blks_hit   | bigint   | Number of buffer-hits in the TOAST table index (if any) in the table |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_SYS_INDEXES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_SYS_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..b37680d29456dd405c96fa4ad5d1fc609be7188a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_SYS_INDEXES.md
@@ -0,0 +1,23 @@
+---
+title: GLOBAL_STATIO_SYS_INDEXES
+summary: GLOBAL_STATIO_SYS_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STATIO_SYS_INDEXES
+
+**GLOBAL_STATIO_SYS_INDEXES** displays I/O status information about all system catalog indexes in namespaces on each node.
+
+**Table 1** GLOBAL_STATIO_SYS_INDEXES columns
+
+| **Name**      | **Type** | **Description**                                 |
+| :------------ | :------- | :---------------------------------------------- |
+| node_name     | name     | Node name                                       |
+| relid         | oid      | OID of the table that the index is created for  |
+| indexrelid    | oid      | OID of the index                                |
+| schemaname    | name     | Name of the schema that the index is in         |
+| relname       | name     | Name of the table that the index is created for |
+| indexrelname  | name     | Index name                                      |
+| idx_blks_read | numeric  | Number of disk blocks read from the index       |
+| idx_blks_hit  | numeric  | Number of cache hits in the index               |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_SYS_SEQUENCES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_SYS_SEQUENCES.md
new file mode 100644
index 0000000000000000000000000000000000000000..b51b45ca660eb4eb329e4a62eff5023ca9202709
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_SYS_SEQUENCES.md
@@ -0,0 +1,21 @@
+---
+title: GLOBAL_STATIO_SYS_SEQUENCES
+summary: GLOBAL_STATIO_SYS_SEQUENCES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STATIO_SYS_SEQUENCES
+
+**GLOBAL_STATIO_SYS_SEQUENCES** displays I/O status information about all system sequences in namespaces on each node.
+
+**Table 1** GLOBAL_STATIO_SYS_SEQUENCES columns
+
+| **Name**   | **Type** | **Description**                              |
+| :--------- | :------- | :------------------------------------------- |
+| node_name  | name     | Node name                                    |
+| relid      | oid      | OID of the sequence                          |
+| schemaname | name     | Name of the schema that the sequence is in   |
+| relname    | name     | Sequence name                                |
+| blks_read  | bigint   | Number of disk blocks read from the sequence |
+| blks_hit   | bigint   | Number of cache hits in the sequence         |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_SYS_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_SYS_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..7df5ff8d321ffbe4eebfb2fc527cc342830ff513
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_SYS_TABLES.md
@@ -0,0 +1,27 @@
+---
+title: GLOBAL_STATIO_SYS_TABLES
+summary: GLOBAL_STATIO_SYS_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STATIO_SYS_TABLES
+
+**GLOBAL_STATIO_SYS_TABLES** displays I/O status information about all system catalogs in namespaces on each node.
+
+**Table 1** GLOBAL_STATIO_SYS_TABLES columns
+
+| **Name**        | **Type** | **Description**                                              |
+| :-------------- | :------- | :----------------------------------------------------------- |
+| node_name       | name     | Node name                                                    |
+| relid           | oid      | Table OID                                                    |
+| schemaname      | name     | Name of the schema that contains the table                   |
+| relname         | name     | Table name                                                   |
+| heap_blks_read  | bigint   | Number of disk blocks read from the table                    |
+| heap_blks_hit   | bigint   | Number of cache hits in the table                            |
+| idx_blks_read   | bigint   | Number of disk blocks read from all indexes in the table     |
+| idx_blks_hit    | bigint   | Number of cache hits in the table                            |
+| toast_blks_read | bigint   | Number of disk blocks read from the TOAST table (if any) in the table |
+| toast_blks_hit  | bigint   | Number of buffer hits in the TOAST table (if any) in the table |
+| tidx_blks_read  | bigint   | Number of disk blocks read from the TOAST table index (if any) in the table |
+| tidx_blks_hit   | bigint   | Number of buffer-hits in the TOAST table index (if any) in the table |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_USER_INDEXES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_USER_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..70be7badacda44d72ad54242887e9dcf9b073c77
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_USER_INDEXES.md
@@ -0,0 +1,23 @@
+---
+title: GLOBAL_STATIO_USER_INDEXES
+summary: GLOBAL_STATIO_USER_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STATIO_USER_INDEXES
+
+**GLOBAL_STATIO_USER_INDEXES** displays I/O status information about all user relationship table indexes in namespaces on each node.
+
+**Table 1** GLOBAL_STATIO_USER_INDEXES columns
+
+| **Name**      | **Type** | **Description**                                 |
+| :------------ | :------- | :---------------------------------------------- |
+| node_name     | name     | Node name                                       |
+| relid         | oid      | OID of the table that the index is created for  |
+| indexrelid    | oid      | OID of the index                                |
+| schemaname    | name     | Name of the schema that the index is in         |
+| relname       | name     | Name of the table that the index is created for |
+| indexrelname  | name     | Index name                                      |
+| idx_blks_read | numeric  | Number of disk blocks read from the index       |
+| idx_blks_hit  | numeric  | Number of cache hits in the index               |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_USER_SEQUENCES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_USER_SEQUENCES.md
new file mode 100644
index 0000000000000000000000000000000000000000..b062671de7ad855efacc0752f85c883064edf50c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_USER_SEQUENCES.md
@@ -0,0 +1,21 @@
+---
+title: GLOBAL_STATIO_USER_SEQUENCES
+summary: GLOBAL_STATIO_USER_SEQUENCES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STATIO_USER_SEQUENCES
+
+**GLOBAL_STATIO_USER_SEQUENCES** displays I/O status information about all user-defined sequences in namespaces on each node.
+
+**Table 1** GLOBAL_STATIO_USER_SEQUENCES columns
+
+| **Name**   | **Type** | **Description**                              |
+| :--------- | :------- | :------------------------------------------- |
+| node_name  | name     | Node name                                    |
+| relid      | oid      | OID of the sequence                          |
+| schemaname | name     | Name of the schema that the sequence is in   |
+| relname    | name     | Sequence name                                |
+| blks_read  | bigint   | Number of disk blocks read from the sequence |
+| blks_hit   | bigint   | Number of cache hits in the sequence         |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_USER_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_USER_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..ad52d83ee7100aa454d94c82c199106536600ba7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_USER_TABLES.md
@@ -0,0 +1,27 @@
+---
+title: GLOBAL_STATIO_USER_TABLES
+summary: GLOBAL_STATIO_USER_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STATIO_USER_TABLES
+
+**GLOBAL_STATIO_USER_TABLES** displays I/O status information about all user relationship tables in namespaces on each node.
+
+**Table 1** GLOBAL_STATIO_USER_TABLES columns
+
+| **Name**        | **Type** | **Description**                                              |
+| :-------------- | :------- | :----------------------------------------------------------- |
+| node_name       | name     | Node name                                                    |
+| relid           | oid      | Table OID                                                    |
+| schemaname      | name     | Name of the schema that contains the table                   |
+| relname         | name     | Table name                                                   |
+| heap_blks_read  | bigint   | Number of disk blocks read from the table                    |
+| heap_blks_hit   | bigint   | Number of cache hits in the table                            |
+| idx_blks_read   | bigint   | Number of disk blocks read from all indexes in the table     |
+| idx_blks_hit    | bigint   | Number of cache hits in the table                            |
+| toast_blks_read | bigint   | Number of disk blocks read from the TOAST table (if any) in the table |
+| toast_blks_hit  | bigint   | Number of buffer hits in the TOAST table (if any) in the table |
+| tidx_blks_read  | bigint   | Number of disk blocks read from the TOAST table index (if any) in the table |
+| tidx_blks_hit   | bigint   | Number of buffer-hits in the TOAST table index (if any) in the table |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STAT_DB_CU.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STAT_DB_CU.md
new file mode 100644
index 0000000000000000000000000000000000000000..cdf6f3ecac7c346cb0104953b2123bcb97fae3de
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STAT_DB_CU.md
@@ -0,0 +1,20 @@
+---
+title: GLOBAL_STAT_DB_CU
+summary: GLOBAL_STAT_DB_CU
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STAT_DB_CU
+
+**GLOBAL_STAT_DB_CU** is used to query CU hits in each database in MogDB. You can clear it using **pg_stat_reset()**.
+
+**Table 1** GLOBAL_STAT_DB_CU columns
+
+| **Name**      | **Type** | **Description**                        |
+| :------------ | :------- | :------------------------------------- |
+| node_name1    | text     | Node name                              |
+| db_name       | text     | Database name                          |
+| mem_hit       | bigint   | Number of memory hits                  |
+| hdd_sync_read | bigint   | Number of synchronous hard disk reads  |
+| hdd_asyn_read | bigint   | Number of asynchronous hard disk reads |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STAT_SESSION_CU.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STAT_SESSION_CU.md
new file mode 100644
index 0000000000000000000000000000000000000000..8a07ee062b8b14bdbe3cf90cb63ca90fcb1c0d3e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STAT_SESSION_CU.md
@@ -0,0 +1,18 @@
+---
+title: GLOBAL_STAT_SESSION_CU
+summary: GLOBAL_STAT_SESSION_CU
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STAT_SESSION_CU
+
+**GLOBAL_STAT_SESSION_CU** is used to query the CU hit rate of running sessions on each node in MogDB. The data about a session is cleared when you exit this session or restart MogDB.
+
+**Table 1** GLOBAL_STAT_SESSION_CU columns
+
+| **Name**      | **Type** | **Description**                        |
+| :------------ | :------- | :------------------------------------- |
+| mem_hit       | integer  | Number of memory hits                  |
+| hdd_sync_read | integer  | Number of synchronous hard disk reads  |
+| hdd_asyn_read | integer  | Number of asynchronous hard disk reads |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_ALL_INDEXES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_ALL_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..6ec55a7b4a8369d9489b11dd762e3ad5380d3658
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_ALL_INDEXES.md
@@ -0,0 +1,22 @@
+---
+title: STATIO_ALL_INDEXES
+summary: STATIO_ALL_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATIO_ALL_INDEXES
+
+**STATIO_ALL_INDEXES** contains one row for each index in the current database, showing I/O statistics about specific indexes.
+
+**Table 1** STATIO_ALL_INDEXES columns
+
+| Name          | Type   | Description                                     |
+| :------------ | :----- | :---------------------------------------------- |
+| relid         | oid    | OID of the table that the index is created for  |
+| indexrelid    | oid    | OID of the index                                |
+| schemaname    | name   | Name of the schema that the index is in         |
+| relname       | name   | Name of the table that the index is created for |
+| indexrelname  | name   | Index name                                      |
+| idx_blks_read | bigint | Number of disk blocks read from the index       |
+| idx_blks_hit  | bigint | Number of cache hits in the index               |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_ALL_SEQUENCES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_ALL_SEQUENCES.md
new file mode 100644
index 0000000000000000000000000000000000000000..2940a88076617718feb9b0f94b4d3282f0df96a8
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_ALL_SEQUENCES.md
@@ -0,0 +1,20 @@
+---
+title: STATIO_ALL_SEQUENCES
+summary: STATIO_ALL_SEQUENCES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATIO_ALL_SEQUENCES
+
+**STATIO_ALL_SEQUENCES** contains one row for each sequence in the current database, showing I/O statistics about specific sequences.
+
+**Table 1** STATIO_ALL_SEQUENCES columns
+
+| Name       | Type   | Description                                  |
+| :--------- | :----- | :------------------------------------------- |
+| relid      | oid    | OID of this sequence                         |
+| schemaname | name   | Name of the schema where the sequence is in  |
+| relname    | name   | Sequence name                                |
+| blks_read  | bigint | Number of disk blocks read from the sequence |
+| blks_hit   | bigint | Cache hits in the sequence                   |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_ALL_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_ALL_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..3267d00f397ca28ed453b83c79ec21ffbd62d567
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_ALL_TABLES.md
@@ -0,0 +1,26 @@
+---
+title: STATIO_ALL_TABLES
+summary: STATIO_ALL_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATIO_ALL_TABLES
+
+**STATIO_ALL_TABLES** contains one row for each table (including TOAST tables) in the current database, showing I/O statistics about specific tables.
+
+**Table 1** STATIO_ALL_TABLES columns
+
+| Name            | Type   | Description                                                  |
+| :-------------- | :----- | :----------------------------------------------------------- |
+| relid           | oid    | Table OID                                                    |
+| schemaname      | name   | Name of the schema that the table is in                      |
+| relname         | name   | Table name                                                   |
+| heap_blks_read  | bigint | Number of disk blocks read from the table                    |
+| heap_blks_hit   | bigint | Number of cache hits in the table                            |
+| idx_blks_read   | bigint | Number of disk blocks read from all indexes in the table     |
+| idx_blks_hit    | bigint | Number of cache hits in indexes in the table                 |
+| toast_blks_read | bigint | Number of disk blocks read from the TOAST table (if any) in the table |
+| toast_blks_hit  | bigint | Number of buffer hits in the TOAST table (if any) in the table |
+| tidx_blks_read  | bigint | Number of disk blocks read from the TOAST table index (if any) in the table |
+| tidx_blks_hit   | bigint | Number of buffer-hits in the TOAST table index (if any) in the table |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_SYS_INDEXES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_SYS_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..407d2d56aa342e0ba3dfb25d389bcf08323c27c7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_SYS_INDEXES.md
@@ -0,0 +1,22 @@
+---
+title: STATIO_SYS_INDEXES
+summary: STATIO_SYS_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATIO_SYS_INDEXES
+
+**STATIO_SYS_INDEXES** displays the I/O status information about all system catalog indexes in the current namespace.
+
+**Table 1** STATIO_SYS_INDEXES columns
+
+| Name          | Type   | Description                                     |
+| :------------ | :----- | :---------------------------------------------- |
+| relid         | oid    | OID of the table that the index is created for  |
+| indexrelid    | oid    | OID of the index                                |
+| schemaname    | name   | Name of the schema that the index is in         |
+| relname       | name   | Name of the table that the index is created for |
+| indexrelname  | name   | Index name                                      |
+| idx_blks_read | bigint | Number of disk blocks read from the index       |
+| idx_blks_hit  | bigint | Number of cache hits in the index               |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_SYS_SEQUENCES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_SYS_SEQUENCES.md
new file mode 100644
index 0000000000000000000000000000000000000000..44cd3ea4d6f7ad5a271cc58c4ec23b8d54df494d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_SYS_SEQUENCES.md
@@ -0,0 +1,20 @@
+---
+title: STATIO_SYS_SEQUENCES
+summary: STATIO_SYS_SEQUENCES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATIO_SYS_SEQUENCES
+
+**STATIO_SYS_SEQUENCES** shows the I/O status information about all the system sequences in the current namespace.
+
+**Table 1** STATIO_SYS_SEQUENCES columns
+
+| Name       | Type   | Description                                  |
+| :--------- | :----- | :------------------------------------------- |
+| relid      | oid    | OID of the sequence                          |
+| schemaname | name   | Name of the schema that the sequence is in   |
+| relname    | name   | Sequence name                                |
+| blks_read  | bigint | Number of disk blocks read from the sequence |
+| blks_hit   | bigint | Number of cache hits in the sequence         |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_SYS_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_SYS_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..171e4a84f542e78bdc7c9f5c536e397e490baef9
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_SYS_TABLES.md
@@ -0,0 +1,26 @@
+---
+title: STATIO_SYS_TABLES
+summary: STATIO_SYS_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATIO_SYS_TABLES
+
+**PG_STATIO_SYS_TABLES** displays I/O status information about all system catalogs in the current namespace.
+
+**Table 1** STATIO_SYS_TABLES columns
+
+| Name            | Type   | Description                                                  |
+| :-------------- | :----- | :----------------------------------------------------------- |
+| relid           | oid    | Table OID                                                    |
+| schemaname      | name   | Name of the schema that the table is in                      |
+| relname         | name   | Table name                                                   |
+| heap_blks_read  | bigint | Number of disk blocks read from the table                    |
+| heap_blks_hit   | bigint | Number of cache hits in the table                            |
+| idx_blks_read   | bigint | Number of disk blocks read from indexes in the table         |
+| idx_blks_hit    | bigint | Number of cache hits in indexes in the table                 |
+| toast_blks_read | bigint | Number of disk blocks read from the TOAST table (if any) in the table |
+| toast_blks_hit  | bigint | Number of buffer hits in the TOAST table (if any) in the table |
+| tidx_blks_read  | bigint | Number of disk blocks read from the TOAST table index (if any) in the table |
+| tidx_blks_hit   | bigint | Number of buffer-hits in the TOAST table index (if any) in the table |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_USER_INDEXES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_USER_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..89cab335a46accf2964697daedd5c829f76f0c85
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_USER_INDEXES.md
@@ -0,0 +1,22 @@
+---
+title: STATIO_USER_INDEXES
+summary: STATIO_USER_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATIO_USER_INDEXES
+
+**STATIO_USER_INDEXES** displays I/O status information about all user relationship table indexes in namespaces on the current node.
+
+**Table 1** STATIO_USER_INDEXES columns
+
+| Name          | Type   | Description                                     |
+| :------------ | :----- | :---------------------------------------------- |
+| relid         | oid    | OID of the table that the index is created for  |
+| indexrelid    | oid    | OID of the index                                |
+| schemaname    | name   | Name of the schema that the index is in         |
+| relname       | name   | Name of the table that the index is created for |
+| indexrelname  | name   | Index name                                      |
+| idx_blks_read | bigint | Number of disk blocks read from the index       |
+| idx_blks_hit  | bigint | Number of cache hits in the index               |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_USER_SEQUENCES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_USER_SEQUENCES.md
new file mode 100644
index 0000000000000000000000000000000000000000..8e437d947fba8d4d4e08f41782836e60c9609253
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_USER_SEQUENCES.md
@@ -0,0 +1,20 @@
+---
+title: STATIO_USER_SEQUENCES
+summary: STATIO_USER_SEQUENCES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATIO_USER_SEQUENCES
+
+**STATIO_USER_SEQUENCE** displays I/O status information about all user relationship table sequences in namespaces on the current node.
+
+**Table 1** STATIO_USER_SEQUENCE columns
+
+| Name       | Type   | Description                                  |
+| :--------- | :----- | :------------------------------------------- |
+| relid      | oid    | OID of the sequence                          |
+| schemaname | name   | Name of the schema that the sequence is in   |
+| relname    | name   | Sequence name                                |
+| blks_read  | bigint | Number of disk blocks read from the sequence |
+| blks_hit   | bigint | Number of cache hits in the sequence         |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_USER_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_USER_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..892a1d92d9e0a778281d93ef0b486747bccc3169
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_USER_TABLES.md
@@ -0,0 +1,26 @@
+---
+title: STATIO_USER_TABLES
+summary: STATIO_USER_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATIO_USER_TABLES
+
+**STATIO_USER_TABLES** displays I/O status information about all user relationship tables in the namespace.
+
+**Table 1** STATIO_USER_TABLES columns
+
+| Name            | Type   | Description                                                  |
+| :-------------- | :----- | :----------------------------------------------------------- |
+| relid           | oid    | Table OID                                                    |
+| schemaname      | name   | Name of the schema that the table is in                      |
+| relname         | name   | Table name                                                   |
+| heap_blks_read  | bigint | Number of disk blocks read from the table                    |
+| heap_blks_hit   | bigint | Number of cache hits in the table                            |
+| idx_blks_read   | bigint | Number of disk blocks read from indexes in the table         |
+| idx_blks_hit    | bigint | Number of cache hits in indexes in the table                 |
+| toast_blks_read | bigint | Number of disk blocks read from the TOAST table (if any) in the table |
+| toast_blks_hit  | bigint | Number of buffer hits in the TOAST table (if any) in the table |
+| tidx_blks_read  | bigint | Number of disk blocks read from the TOAST table index (if any) in the table |
+| tidx_blks_hit   | bigint | Number of buffer-hits in the TOAST table index (if any) in the table |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_ALL_INDEXES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_ALL_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..16deddf14ee65ff9a7da42e0906f81c51a0e51ea
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_ALL_INDEXES.md
@@ -0,0 +1,20 @@
+---
+title: SUMMARY_STATIO_ALL_INDEXES
+summary: SUMMARY_STATIO_ALL_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STATIO_ALL_INDEXES
+
+**SUMMARY_STATIO_ALL_INDEXES** contains every row of each index in databases in MogDB, showing I/O statistics about specific indexes.
+
+**Table 1** SUMMARY_STATIO_ALL_INDEXES columns
+
+| **Name**      | **Type** | **Description**                                 |
+| :------------ | :------- | :---------------------------------------------- |
+| schemaname    | name     | Name of the schema that the index is in         |
+| relname       | name     | Name of the table that the index is created for |
+| indexrelname  | name     | Index name                                      |
+| idx_blks_read | numeric  | Number of disk blocks read from the index       |
+| idx_blks_hit  | numeric  | Number of cache hits in the index               |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_ALL_SEQUENCES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_ALL_SEQUENCES.md
new file mode 100644
index 0000000000000000000000000000000000000000..9d7fbb82f0e0a343faec88dc0d98efcde8032b18
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_ALL_SEQUENCES.md
@@ -0,0 +1,19 @@
+---
+title: SUMMARY_STATIO_ALL_SEQUENCES
+summary: SUMMARY_STATIO_ALL_SEQUENCES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STATIO_ALL_SEQUENCES
+
+**SUMMARY_STATIO_ALL_SEQUENCES** contains one row for each sequence in databases in MogDB, showing I/O statistics about specific sequences.
+
+**Table 1** SUMMARY_STATIO_ALL_SEQUENCES columns
+
+| **Name**   | **Type** | **Description**                              |
+| :--------- | :------- | :------------------------------------------- |
+| schemaname | name     | Name of the schema that the sequence is in   |
+| relname    | name     | Sequence name                                |
+| blks_read  | numeric  | Number of disk blocks read from the sequence |
+| blks_hit   | numeric  | Number of cache hits in the sequence         |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_ALL_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_ALL_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..c580cadb00adaf7aea766d308c3296d126c97765
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_ALL_TABLES.md
@@ -0,0 +1,25 @@
+---
+title: SUMMARY_STATIO_ALL_TABLES
+summary: SUMMARY_STATIO_ALL_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STATIO_ALL_TABLES
+
+**SUMMARY_STATIO_ALL_TABLES** contains I/O statistics about each table (including TOAST tables) in databases in MogDB.
+
+**Table 1** SUMMARY_STATIO_ALL_TABLES columns
+
+| **Name**        | **Type** | **Description**                                              |
+| :-------------- | :------- | :----------------------------------------------------------- |
+| schemaname      | name     | Name of the schema that contains the table                   |
+| relname         | name     | Table name                                                   |
+| heap_blks_read  | numeric  | Number of disk blocks read from the table                    |
+| heap_blks_hit   | numeric  | Number of cache hits in the table                            |
+| idx_blks_read   | numeric  | Number of disk blocks read from all indexes in the table     |
+| idx_blks_hit    | numeric  | Number of cache hits in the table                            |
+| toast_blks_read | numeric  | Number of disk blocks read from the TOAST table (if any) in the table |
+| toast_blks_hit  | numeric  | Number of buffer hits in the TOAST table (if any) in the table |
+| tidx_blks_read  | numeric  | Number of disk blocks read from the TOAST table index (if any) in the table |
+| tidx_blks_hit   | numeric  | Number of buffer-hits in the TOAST table index (if any) in the table |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_SYS_INDEXES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_SYS_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..a2c1472319db02273b65e59e087b4c3054a73ab9
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_SYS_INDEXES.md
@@ -0,0 +1,20 @@
+---
+title: SUMMARY_STATIO_SYS_INDEXES
+summary: SUMMARY_STATIO_SYS_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STATIO_SYS_INDEXES
+
+**SUMMARY_STATIO_SYS_INDEXES** displays I/O status information about all system catalog indexes in namespaces in MogDB.
+
+**Table 1** SUMMARY_STATIO_SYS_INDEXES columns
+
+| **Name**      | **Type** | **Description**                                 |
+| :------------ | :------- | :---------------------------------------------- |
+| schemaname    | name     | Name of the schema that the index is in         |
+| relname       | name     | Name of the table that the index is created for |
+| indexrelname  | name     | Index name                                      |
+| idx_blks_read | numeric  | Number of disk blocks read from the index       |
+| idx_blks_hit  | numeric  | Number of cache hits in the index               |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_SYS_SEQUENCES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_SYS_SEQUENCES.md
new file mode 100644
index 0000000000000000000000000000000000000000..a4164993fac20ceecfe26b7857c90a173c811805
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_SYS_SEQUENCES.md
@@ -0,0 +1,19 @@
+---
+title: SUMMARY_STATIO_SYS_SEQUENCES
+summary: SUMMARY_STATIO_SYS_SEQUENCES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STATIO_SYS_SEQUENCES
+
+**SUMMARY_STATIO_SYS_SEQUENCES** displays I/O status information about all system sequences in namespaces in MogDB.
+
+**Table 1** SUMMARY_STATIO_SYS_SEQUENCES columns
+
+| **Name**   | **Type** | **Description**                              |
+| :--------- | :------- | :------------------------------------------- |
+| schemaname | name     | Name of the schema that the sequence is in   |
+| relname    | name     | Sequence name                                |
+| blks_read  | numeric  | Number of disk blocks read from the sequence |
+| blks_hit   | numeric  | Number of cache hits in the sequence         |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_SYS_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_SYS_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..30ae3418aad8b6c98278520440a15c02ad82200f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_SYS_TABLES.md
@@ -0,0 +1,25 @@
+---
+title: SUMMARY_STATIO_SYS_TABLES
+summary: SUMMARY_STATIO_SYS_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STATIO_SYS_TABLES
+
+**SUMMARY_STATIO_SYS_TABLES** displays I/O status information about all system catalogs in namespaces in MogDB.
+
+**Table 1** SUMMARY_STATIO_SYS_TABLES columns
+
+| **Name**        | **Type** | **Description**                                              |
+| :-------------- | :------- | :----------------------------------------------------------- |
+| schemaname      | name     | Name of the schema that contains the table                   |
+| relname         | name     | Table name                                                   |
+| heap_blks_read  | numeric  | Number of disk blocks read from the table                    |
+| heap_blks_hit   | numeric  | Number of cache hits in the table                            |
+| idx_blks_read   | numeric  | Number of disk blocks read from all indexes in the table     |
+| idx_blks_hit    | numeric  | Number of cache hits in the table                            |
+| toast_blks_read | numeric  | Number of disk blocks read from the TOAST table (if any) in the table |
+| toast_blks_hit  | numeric  | Number of buffer hits in the TOAST table (if any) in the table |
+| tidx_blks_read  | numeric  | Number of disk blocks read from the TOAST table index (if any) in the table |
+| tidx_blks_hit   | numeric  | Number of buffer-hits in the TOAST table index (if any) in the table |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_USER_INDEXES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_USER_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..46b7c8c33b83cc403d20b3ec9f22be1e54514319
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_USER_INDEXES.md
@@ -0,0 +1,20 @@
+---
+title: SUMMARY_STATIO_USER_INDEXES
+summary: SUMMARY_STATIO_USER_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STATIO_USER_INDEXES
+
+**SUMMARY_STATIO_USER_INDEXES** displays I/O status information about all user relationship table indexes in namespaces in MogDB.
+
+**Table 1** SUMMARY_STATIO_USER_INDEXES columns
+
+| **Name**      | **Type** | **Description**                                 |
+| :------------ | :------- | :---------------------------------------------- |
+| schemaname    | name     | Name of the schema that the index is in         |
+| relname       | name     | Name of the table that the index is created for |
+| indexrelname  | name     | Index name                                      |
+| idx_blks_read | numeric  | Number of disk blocks read from the index       |
+| idx_blks_hit  | numeric  | Number of cache hits in the index               |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_USER_SEQUENCES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_USER_SEQUENCES.md
new file mode 100644
index 0000000000000000000000000000000000000000..7464ca97ad5970822ca23662d52f7fe2264218c0
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_USER_SEQUENCES.md
@@ -0,0 +1,19 @@
+---
+title: SUMMARY_STATIO_USER_SEQUENCES
+summary: SUMMARY_STATIO_USER_SEQUENCES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STATIO_USER_SEQUENCES
+
+**SUMMARY_STATIO_USER_SEQUENCES** displays I/O status information about all user-defined sequences in namespaces in MogDB.
+
+**Table 1** SUMMARY_STATIO_USER_SEQUENCES columns
+
+| **Name**   | **Type** | **Description**                              |
+| :--------- | :------- | :------------------------------------------- |
+| schemaname | name     | Name of the schema that the sequence is in   |
+| relname    | name     | Sequence name                                |
+| blks_read  | numeric  | Number of disk blocks read from the sequence |
+| blks_hit   | numeric  | Number of cache hits in the sequence         |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_USER_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_USER_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..d0a0f2db30eeefb0dbbdf5a749737e2e8b9c38d8
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_USER_TABLES.md
@@ -0,0 +1,25 @@
+---
+title: SUMMARY_STATIO_USER_TABLES
+summary: SUMMARY_STATIO_USER_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STATIO_USER_TABLES
+
+**SUMMARY_STATIO_USER_TABLES** displays I/O status information about all user relationship tables in namespaces in MogDB.
+
+**Table 1** SUMMARY_STATIO_USER_TABLES columns
+
+| **Name**        | **Type** | **Description**                                              |
+| :-------------- | :------- | :----------------------------------------------------------- |
+| schemaname      | name     | Name of the schema that contains the table                   |
+| relname         | name     | Table name                                                   |
+| heap_blks_read  | numeric  | Number of disk blocks read from the table                    |
+| heap_blks_hit   | numeric  | Number of cache hits in the table                            |
+| idx_blks_read   | numeric  | Number of disk blocks read from all indexes in the table     |
+| idx_blks_hit    | numeric  | Number of cache hits in the table                            |
+| toast_blks_read | numeric  | Number of disk blocks read from the TOAST table (if any) in the table |
+| toast_blks_hit  | numeric  | Number of buffer hits in the TOAST table (if any) in the table |
+| tidx_blks_read  | numeric  | Number of disk blocks read from the TOAST table index (if any) in the table |
+| tidx_blks_hit   | numeric  | Number of buffer-hits in the TOAST table index (if any) in the table |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/configuration/CONFIG_SETTINGS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/configuration/CONFIG_SETTINGS.md
new file mode 100644
index 0000000000000000000000000000000000000000..6ea089419e9853368041fb959b97562cc873bb23
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/configuration/CONFIG_SETTINGS.md
@@ -0,0 +1,31 @@
+---
+title: CONFIG_SETTINGS
+summary: CONFIG_SETTINGS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# CONFIG_SETTINGS
+
+**CONFIG_SETTINGS** displays information about parameters of the running database.
+
+**Table 1** CONFIG_SETTINGS columns
+
+| Name       | Type    | Description                                                  |
+| :--------- | :------ | :----------------------------------------------------------- |
+| name       | text    | Parameter name                                               |
+| setting    | text    | Current parameter value                                      |
+| unit       | text    | Implicit unit of the parameter                               |
+| category   | text    | Logical group of the parameter                               |
+| short_desc | text    | Brief description of the parameter                           |
+| extra_desc | text    | Detailed description of the parameter                        |
+| context    | text    | Context required to set the parameter value, including **internal**, **postmaster**, **sighup**, **backend**, **superuser**, and **user** |
+| vartype    | text    | Parameter type, including **bool**, **enum**, **integer**, **real**, or **string** |
+| source     | text    | Method of assigning the parameter value                      |
+| min_val    | text    | Maximum value of the parameter. If the parameter type is not numeric, the value of this column is **null**. |
+| max_val    | text    | Minimum value of the parameter. If the parameter type is not numeric, the value of this column is **null**. |
+| enumvals   | text[]  | Valid values of an enum-type parameter. If the parameter type is not enum, the value of this column is **null**. |
+| boot_val   | text    | Default parameter value used upon the database startup       |
+| reset_val  | text    | Default parameter value used upon the database reset         |
+| sourcefile | text    | Configuration file used to set parameter values. If parameter values are not configured using the configuration file, the value of this column is **null**. |
+| sourceline | integer | Row number in the configuration file for setting parameter values. If parameter values are not configured using the configuration file, the value of this column is **null**. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/configuration/GLOBAL_CONFIG_SETTINGS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/configuration/GLOBAL_CONFIG_SETTINGS.md
new file mode 100644
index 0000000000000000000000000000000000000000..28cc0d0853dd787c6d71a17ef68dd36728c3bb2b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/configuration/GLOBAL_CONFIG_SETTINGS.md
@@ -0,0 +1,32 @@
+---
+title: GLOBAL_CONFIG_SETTINGS
+summary: GLOBAL_CONFIG_SETTINGS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_CONFIG_SETTINGS
+
+**GLOBAL_CONFIG_SETTINGS** displays information about parameters of running databases on each node.
+
+**Table 1** GLOBAL_CONFIG_SETTINGS columns
+
+| **Name**   | **Type** | **Description**                                              |
+| :--------- | :------- | :----------------------------------------------------------- |
+| node_name  | text     | Node name                                                    |
+| name       | text     | Parameter name                                               |
+| setting    | text     | Current parameter value                                      |
+| unit       | text     | Implicit unit of the parameter                               |
+| category   | text     | Logical group of the parameter                               |
+| short_desc | text     | Brief description of the parameter                           |
+| extra_desc | text     | Detailed description of the parameter                        |
+| context    | text     | Context required to set the parameter value, including **internal**, **postmaster**, **sighup**, **backend**, **superuser**, and **user** |
+| vartype    | text     | Parameter type, including **bool**, **enum**, **integer**, **real**, or **string** |
+| source     | text     | Method of assigning the parameter value                      |
+| min_val    | text     | Maximum value of the parameter. If the parameter type is not numeric, the value of this column is **null**. |
+| max_val    | text     | Minimum value of the parameter. If the parameter type is not numeric, the value of this column is **null**. |
+| enumvals   | text[]   | Valid values of an enum-type parameter. If the parameter type is not enum, the value of this column is **null**. |
+| boot_val   | text     | Default parameter value used upon the database startup       |
+| reset_val  | text     | Default parameter value used upon the database reset         |
+| sourcefile | text     | Configuration file used to set parameter values. If parameter values are not configured using the configuration file, the value of this column is **null**. |
+| sourceline | integer  | Row number in the configuration file for setting parameter values. If parameter values are not configured using the configuration file, the value of this column is **null**. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/FILE_IOSTAT.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/FILE_IOSTAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..55a8447e70031f92a8885ab067dbc0d5bb44b138
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/FILE_IOSTAT.md
@@ -0,0 +1,28 @@
+---
+title: FILE_IOSTAT
+summary: FILE_IOSTAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# FILE_IOSTAT
+
+**FILE_IOSTAT** records statistics about data file I/Os to indicate I/O performance and detect performance problems such as abnormal I/O operations.
+
+**Table 1** FILE_IOSTAT columns
+
+| Name      | Type   | Description                                          |
+| :-------- | :----- | :--------------------------------------------------- |
+| filenum   | oid    | File identifier                                      |
+| dbid      | oid    | Database ID                                          |
+| spcid     | oid    | Tablespace ID                                        |
+| phyrds    | bigint | Number of times of reading physical files            |
+| phywrts   | bigint | Number of times of writing into physical files       |
+| phyblkrd  | bigint | Number of times of reading physical file blocks      |
+| phyblkwrt | bigint | Number of times of writing into physical file blocks |
+| readtim   | bigint | Total duration of reading (unit: μs)                 |
+| writetim  | bigint | Total duration of writing (unit: μs)                 |
+| avgiotim  | bigint | Average duration of reading and writing (unit: μs)   |
+| lstiotim  | bigint | Duration of the last file reading (unit: μs)         |
+| miniotim  | bigint | Minimum duration of reading and writing (unit: μs)   |
+| maxiowtm  | bigint | Maximum duration of reading and writing (unit: μs)   |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/FILE_REDO_IOSTAT.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/FILE_REDO_IOSTAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..fef292cd2edfae3334cc8dd0969c2b711e665106
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/FILE_REDO_IOSTAT.md
@@ -0,0 +1,22 @@
+---
+title: FILE_REDO_IOSTAT
+summary: FILE_REDO_IOSTAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# FILE_REDO_IOSTAT
+
+**FILE_REDO_IOSTAT** records statistics about redo logs (WALs) on the current node.
+
+**Table 1** FILE_REDO_IOSTAT columns
+
+| Name      | Type   | Description                                                  |
+| :-------- | :----- | :----------------------------------------------------------- |
+| phywrts   | bigint | Number of times writing into the WAL buffer                  |
+| phyblkwrt | bigint | Number of blocks written into the WAL buffer                 |
+| writetim  | bigint | Duration of writing into XLOG files (unit: μs)               |
+| avgiotim  | bigint | Average duration of writing into XLOG files (unit: μs). **avgiotim** = **writetim**/**phywrts** |
+| lstiotim  | bigint | Duration of the last writing into XLOG files (unit: μs)      |
+| miniotim  | bigint | Minimum duration of writing into XLOG files (unit: μs)       |
+| maxiowtm  | bigint | Maximum duration of writing into XLOG files (unit: μs)       |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/GLOBAL_FILE_IOSTAT.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/GLOBAL_FILE_IOSTAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..de8c8e324ee09e3ea463dcc2cba79c351cc27aaf
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/GLOBAL_FILE_IOSTAT.md
@@ -0,0 +1,29 @@
+---
+title: GLOBAL_FILE_IOSTAT
+summary: GLOBAL_FILE_IOSTAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_FILE_IOSTAT
+
+**GLOBAL_FILE_IOSTAT** records statistics about data file I/Os on all nodes.
+
+**Table 1** GLOBAL_FILE_IOSTAT columns
+
+| **Name**  | **Type** | **Description**                                      |
+| :-------- | :------- | :--------------------------------------------------- |
+| node_name | name     | Node name                                            |
+| filenum   | oid      | File ID                                              |
+| dbid      | oid      | Database ID                                          |
+| spcid     | oid      | Tablespace ID                                        |
+| phyrds    | bigint   | Number of times of reading physical files            |
+| phywrts   | bigint   | Number of times of writing into physical files       |
+| phyblkrd  | bigint   | Number of times of reading physical file blocks      |
+| phyblkwrt | bigint   | Number of times of writing into physical file blocks |
+| readtim   | bigint   | Total duration of reading (unit: μs)                 |
+| writetim  | bigint   | Total duration of writing (unit: μs)                 |
+| avgiotim  | bigint   | Average duration of reading and writing (unit: μs)   |
+| lstiotim  | bigint   | Duration of the last file reading (unit: μs)         |
+| miniotim  | bigint   | Minimum duration of reading and writing (unit: μs)   |
+| maxiowtm  | bigint   | Maximum duration of reading and writing (unit: μs)   |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/GLOBAL_FILE_REDO_IOSTAT.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/GLOBAL_FILE_REDO_IOSTAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..1d47b198fdcc0cf8b4a11c95a0994ece03d1c5a9
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/GLOBAL_FILE_REDO_IOSTAT.md
@@ -0,0 +1,23 @@
+---
+title: GLOBAL_FILE_REDO_IOSTAT
+summary: GLOBAL_FILE_REDO_IOSTAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_FILE_REDO_IOSTAT
+
+**GLOBAL_FILE_REDO_IOSTAT** records statistics about redo logs and WALs on each node in MogDB.
+
+**Table 1** GLOBALXC_FILE_REDO_IOSTAT columns
+
+| **Name**  | **Type** | **Description**                                              |
+| :-------- | :------- | :----------------------------------------------------------- |
+| node_name | name     | Node name                                                    |
+| phywrts   | bigint   | Number of times writing into the WAL buffer                  |
+| phyblkwrt | bigint   | Number of blocks written into the WAL buffer                 |
+| writetim  | bigint   | Duration of writing into XLOG files (unit: μs)               |
+| avgiotim  | bigint   | Average duration of writing into XLOG files (unit: μs). **avgiotim** = **writetim**/**phywrts** |
+| lstiotim  | bigint   | Duration of the last writing into XLOG files (unit: μs)      |
+| miniotim  | bigint   | Minimum duration of writing into XLOG files (unit: μs)       |
+| maxiowtm  | bigint   | Maximum duration of writing into XLOG files (unit: μs)       |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/GLOBAL_REL_IOSTAT.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/GLOBAL_REL_IOSTAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..4161273ab5769d8f7aeb78232bf6cd8eb086857d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/GLOBAL_REL_IOSTAT.md
@@ -0,0 +1,20 @@
+---
+title: GLOBAL_REL_IOSTAT
+summary: GLOBAL_REL_IOSTAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_REL_IOSTAT
+
+**GLOBAL_REL_IOSTAT** is the aggregate statistics of MogDB on the cumulative value of the data file IO status, reflecting the IO performance of the data file access.
+
+**Table 1** GLOBAL_REL_IOSTAT columns
+
+| **Name**  | **Type** | **Description**                                      |
+| :-------- | :------- | :--------------------------------------------------- |
+| node_name | name     | Node name                                            |
+| phyrds    | bigint   | Number of times of reading physical files            |
+| phywrts   | bigint   | Number of times of writing into physical files       |
+| phyblkrd  | bigint   | Number of times of reading physical file blocks      |
+| phyblkwrt | bigint   | Number of times of writing into physical file blocks |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/LOCAL_REL_IOSTAT.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/LOCAL_REL_IOSTAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..080ef39fedb813eeb66c63e9fe336dd287bba4b8
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/LOCAL_REL_IOSTAT.md
@@ -0,0 +1,19 @@
+---
+title: LOCAL_REL_IOSTAT
+summary: LOCAL_REL_IOSTAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# LOCAL_REL_IOSTAT
+
+**LOCAL_REL_IOSTAT** displays the accumulated I/O status of all data files on the current node.
+
+**Table 1** LOCAL_REL_IOSTAT columns
+
+| Name      | Type   | Description                                          |
+| :-------- | :----- | :--------------------------------------------------- |
+| phyrds    | bigint | Number of times of reading physical files            |
+| phywrts   | bigint | Number of times of writing into physical files       |
+| phyblkrd  | bigint | Number of times of reading physical file blocks      |
+| phyblkwrt | bigint | Number of times of writing into physical file blocks |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/SUMMARY_FILE_IOSTAT.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/SUMMARY_FILE_IOSTAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..42a0e7ea6602af70e9d57f6f068c78f45405eb76
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/SUMMARY_FILE_IOSTAT.md
@@ -0,0 +1,28 @@
+---
+title: SUMMARY_FILE_IOSTAT
+summary: SUMMARY_FILE_IOSTAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_FILE_IOSTAT
+
+**SUMMARY_FILE_IOSTAT** records statistics about data file I/Os in MogDB to indicate I/O performance and detect performance problems such as abnormal I/O operations.
+
+**Table 1** SUMMARY_FILE_IOSTAT columns
+
+| **Name**  | **Type** | **Description**                                      |
+| :-------- | :------- | :--------------------------------------------------- |
+| filenum   | oid      | File ID                                              |
+| dbid      | oid      | Database ID                                          |
+| spcid     | oid      | Tablespace ID                                        |
+| phyrds    | numeric  | Number of times of reading physical files            |
+| phywrts   | numeric  | Number of times of writing into physical files       |
+| phyblkrd  | numeric  | Number of times of reading physical file blocks      |
+| phyblkwrt | numeric  | Number of times of writing into physical file blocks |
+| readtim   | numeric  | Total duration of reading (unit: μs)                 |
+| writetim  | numeric  | Total duration of writing (unit: μs)                 |
+| avgiotim  | bigint   | Average duration of reading and writing (unit: μs)   |
+| lstiotim  | bigint   | Duration of the last file reading (unit: μs)         |
+| miniotim  | bigint   | Minimum duration of reading and writing (unit: μs)   |
+| maxiowtm  | bigint   | Maximum duration of reading and writing (unit: μs)   |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/SUMMARY_FILE_REDO_IOSTAT.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/SUMMARY_FILE_REDO_IOSTAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..1e40a5225f972f56c2fa452677f38eb1f04a89b2
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/SUMMARY_FILE_REDO_IOSTAT.md
@@ -0,0 +1,22 @@
+---
+title: SUMMARY_FILE_REDO_IOSTAT
+summary: SUMMARY_FILE_REDO_IOSTAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_FILE_REDO_IOSTAT
+
+**SUMMARY_FILE_REDO_IOSTAT** records statistics about all redo logs and WALs in MogDB.
+
+**Table 1** SUMMARY_FILE_REDO_IOSTAT columns
+
+| **Name**  | **Type** | **Description**                                              |
+| :-------- | :------- | :----------------------------------------------------------- |
+| phywrts   | numeric  | Number of times writing into the WAL buffer                  |
+| phyblkwrt | numeric  | Number of blocks written into the WAL buffer                 |
+| writetim  | numeric  | Duration of writing into XLOG files (unit: μs)               |
+| avgiotim  | bigint   | Average duration of writing into XLOG files (unit: μs). **avgiotim** = **writetim**/**phywrts** |
+| lstiotim  | bigint   | Duration of the last writing into XLOG files (unit: μs)      |
+| miniotim  | bigint   | Minimum duration of writing into XLOG files (unit: μs)       |
+| maxiowtm  | bigint   | Maximum duration of writing into XLOG files (unit: μs)       |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/SUMMARY_REL_IOSTAT.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/SUMMARY_REL_IOSTAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..6291a9418fe4450151ecc707a982145335796cb8
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/SUMMARY_REL_IOSTAT.md
@@ -0,0 +1,19 @@
+---
+title: SUMMARY_REL_IOSTAT
+summary: SUMMARY_REL_IOSTAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_REL_IOSTAT
+
+**SUMMARY_REL_IOSTAT** obtains statistics about data file I/Os on all nodes.
+
+**Table 1** SUMMARY_REL_IOSTAT columns
+
+| **Name**  | **Type** | **Description**                                      |
+| :-------- | :------- | :--------------------------------------------------- |
+| phyrds    | numeric  | Number of times of reading physical files            |
+| phywrts   | numeric  | Number of times of writing into physical files       |
+| phyblkrd  | numeric  | Number of times of reading physical file blocks      |
+| phyblkwrt | numeric  | Number of times of writing into physical file blocks |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/global-plancache/GLOBAL_PLANCACHE_CLEAN.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/global-plancache/GLOBAL_PLANCACHE_CLEAN.md
new file mode 100644
index 0000000000000000000000000000000000000000..1fdab99cb48e92e11fece701b4f44e8793825888
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/global-plancache/GLOBAL_PLANCACHE_CLEAN.md
@@ -0,0 +1,10 @@
+---
+title: GLOBAL_PLANCACHE_CLEAN
+summary: GLOBAL_PLANCACHE_CLEAN
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_PLANCACHE_CLEAN
+
+**GLOBAL_PLANCACHE_CLEAN** clears the global plan cache that is not used on all nodes. The return value is of the Boolean type.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/global-plancache/GLOBAL_PLANCACHE_STATUS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/global-plancache/GLOBAL_PLANCACHE_STATUS.md
new file mode 100644
index 0000000000000000000000000000000000000000..317c055aadc007515b179790dd51e5062181ba19
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/global-plancache/GLOBAL_PLANCACHE_STATUS.md
@@ -0,0 +1,23 @@
+---
+title: GLOBAL_PLANCACHE_STATUS
+summary: GLOBAL_PLANCACHE_STATUS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_PLANCACHE_STATUS
+
+**GLOBAL_PLANCACHE_STATUS** displays the GPC status information.
+
+**Table 1** GLOBAL_PLANCACHE_STATUS columns
+
+| Name        | Type    | Description                                                  |
+| :---------- | :------ | :----------------------------------------------------------- |
+| nodename    | text    | Name of the node that the plan cache belongs to              |
+| query       | text    | Text of query statements                                     |
+| refcount    | integer | Number of times that the plan cache is referenced            |
+| valid       | bool    | Whether the plan cache is valid                              |
+| databaseid  | oid     | ID of the database that the plan cache belongs to            |
+| schema_name | text    | Schema that the plan cache belongs to                        |
+| params_num  | integer | Number of parameters                                         |
+| func_id     | oid     | OID of the stored procedure where the plan cache is located. If the plancache does not belong to the stored procedure, the value is **0**. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/global-plancache/global-plancache-overview.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/global-plancache/global-plancache-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..875145971795a7214a445c60edfcde1ab5a2d10b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/global-plancache/global-plancache-overview.md
@@ -0,0 +1,10 @@
+---
+title: Overview
+summary: Overview
+author: Guo Huan
+date: 2021-04-19
+---
+
+# Overview
+
+Global plan cache (GPC) views are valid only when **enable_global_plancache** and the thread pool are enabled.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/instance/GLOBAL_INSTANCE_TIME.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/instance/GLOBAL_INSTANCE_TIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..939c072089eb4a0b9325822c3edf88a26e412847
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/instance/GLOBAL_INSTANCE_TIME.md
@@ -0,0 +1,19 @@
+---
+title: GLOBAL_INSTANCE_TIME
+summary: GLOBAL_INSTANCE_TIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_INSTANCE_TIME
+
+**GLOBAL_INSTANCE_TIME** provides time consumption information about all normal nodes in MogDB. For details about the time types, see the **INSTANCE_TIME** view.
+
+**Table 1** GLOBAL_INSTANCE_TIME columns
+
+| **Name**  | **Type** | **Description**     |
+| :-------- | :------- | :------------------ |
+| node_name | name     | node name           |
+| stat_id   | integer  | Statistics ID       |
+| stat_name | text     | Type name           |
+| value     | bigint   | Duration (unit: μs) |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/instance/INSTANCE_TIME.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/instance/INSTANCE_TIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..0625ac5e848d3bc5a29da7158c1aae486232bded
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/instance/INSTANCE_TIME.md
@@ -0,0 +1,29 @@
+---
+title: INSTANCE_TIME
+summary: INSTANCE_TIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# INSTANCE_TIME
+
+**INSTANCE_TIME** records time consumption information on the current cluster node. The time consumption information is classified into the following types:
+
+- DB_TIME: effective time spent by jobs in multi-core scenarios
+- CPU_TIME: CPU time cost.
+- EXECUTION_TIME: time spent in the executor.
+- PARSE_TIME: time spent on parsing SQL statements
+- PLAN_TIME: time spent on generating plans
+- REWRITE_TIME: time spent on rewriting SQL statements
+- PL_COMPILATION_TIME: compilation time of the PL/pgSQL stored procedure.
+- PL_COMPILATION_TIME: compilation time of the PL/pgSQL stored procedure
+- NET_SEND_TIME: time spent on the network
+- DATA_IO_TIME: time spent on I/Os.
+
+**Table 1** INSTANCE_TIME columns
+
+| Name      | Type    | Description           |
+| :-------- | :------ | :-------------------- |
+| stat_id   | integer | Statistics ID         |
+| stat_name | text    | Type name             |
+| value     | bigint  | Time value (unit: μs) |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/lock/GLOBAL_LOCKS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/lock/GLOBAL_LOCKS.md
new file mode 100644
index 0000000000000000000000000000000000000000..5ba3bd64120589a9559fd8fa8ded50173a83e0be
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/lock/GLOBAL_LOCKS.md
@@ -0,0 +1,31 @@
+---
+title: GLOBAL_LOCKS
+summary: GLOBAL_LOCKS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_LOCKS
+
+**GLOBAL_LOCKS** displays information about locks held by open transactions on each node.
+
+**Table 1** GLOBAL_LOCKS columns
+
+| **Name**           | **Type** | **Description**                                              |
+| :----------------- | :------- | :----------------------------------------------------------- |
+| node_name          | name     | Node name                                                    |
+| locktype           | text     | Type of the locked object:**relation**, **extend**, **page**, **tuple**, **transactionid**, **virtualxid**, **object**, **userlock**, or **advisory** |
+| database           | oid      | OID of the database in which the locked object exists.<br/>- The OID is **0** if the object is a shared object.<br/>- The OID is **NULL** if the object is a transaction ID. |
+| relation           | oid      | OID of the relationship targeted by the lock. The value is **NULL** if the object is not a relationship or part of a relationship. |
+| page               | integer  | Page number targeted by the lock within the relationship. The value is **NULL** if the object is not a relationship page or row page. |
+| tuple              | smallint | Row number targeted by the lock within the page. The value is **NULL** if the object is not a row. |
+| virtualxid         | text     | Virtual ID of the transaction targeted by the lock. The value is **NULL** if the object is not a virtual transaction ID. |
+| transactionid      | xid      | ID of the transaction targeted by the lock. The value is **NULL** if the object is not a transaction ID. |
+| classid            | oid      | OID of the system catalog that contains the object. The value is **NULL** if the object is not a general database object. |
+| objid              | oid      | OID of the locked object within its system catalog. The value is **NULL** if the object is not a general database object. |
+| objsubid           | smallint | Column number for a column in the table. The value is **0** if the object is some other object type. The value is **NULL** if the object is not a general database object. |
+| virtualtransaction | text     | Virtual ID of the transaction holding or awaiting this lock  |
+| pid                | bigint   | Logical ID of the server thread holding or awaiting this lock The value is **NULL** if the lock is held by a prepared transaction. |
+| mode               | text     | Lock mode held or desired by this thread                     |
+| granted            | boolean  | - The value is **TRUE** if the lock is a held lock.<br/>- The value is **FALSE** if the lock is an awaited lock. |
+| fastpath           | boolean  | The value is **TRUE** if the lock is obtained through **fast-path**, and is **FALSE** if the lock is obtained through the main lock table. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/lock/LOCKS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/lock/LOCKS.md
new file mode 100644
index 0000000000000000000000000000000000000000..5ba13407bc40c82d0bd9f7a420fc061934f189c3
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/lock/LOCKS.md
@@ -0,0 +1,34 @@
+---
+title: LOCKS
+summary: LOCKS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# LOCKS
+
+**LOCKS** displays information about locks held by each open transaction.
+
+**Table 1** LOCKS columns
+
+| Name               | Type     | Description                                                  |
+| :----------------- | :------- | :----------------------------------------------------------- |
+| locktype           | text     | Type of the locked object:**relation**, **extend**, **page**, **tuple**, **transactionid**, **virtualxid**, **object**, **userlock**, or **advisory** |
+| database           | oid      | OID of the database in which the locked object exists.<br/>- The OID is **0** if the object is a shared object.<br/>- The OID is **NULL** if the object is a transaction ID. |
+| relation           | oid      | OID of the relationship targeted by the lock. The value is **NULL** if the object is not a relationship or part of a relationship. |
+| page               | integer  | Page number targeted by the lock within the relationship. The value is **NULL** if the object is not a relationship page or row page. |
+| tuple              | smallint | Row number targeted by the lock within the page. The value is **NULL** if the object is not a row. |
+| bucket             | integer  | Hash bucket ID.                                              |
+| virtualxid         | text     | Virtual ID of the transaction targeted by the lock. The value is **NULL** if the object is not a virtual transaction ID. |
+| transactionid      | xid      | ID of the transaction targeted by the lock. The value is **NULL** if the object is not a transaction ID. |
+| classid            | oid      | OID of the system catalog that contains the object. The value is **NULL** if the object is not a general database object. |
+| objid              | oid      | OID of the locked object within its system catalog. The value is **NULL** if the object is not a general database object. |
+| objsubid           | smallint | Column number for a column in the table. (**0** if the object is of other object type and **NULL** if the object is not a general database object) |
+| virtualtransaction | text     | Virtual ID of the transaction holding or awaiting this lock  |
+| pid                | bigint   | Logical ID of the server thread holding or awaiting this lock. The value is **NULL** if the lock is held by a prepared transaction. |
+| sessionid          | bigint   | ID of the session holding or awaiting this lock The value is **NULL** if the lock is held by a prepared transaction. |
+| mode               | text     | Lock mode held or desired by this thread                     |
+| granted            | Boolean  | - The value is **TRUE** if the lock is a held lock.<br/>- The value is **FALSE** if the lock is an awaited lock. |
+| fastpath           | Boolean  | The value is **TRUE** if the lock is obtained through **fast-path**, and is **FALSE** if the lock is obtained through the main lock table. |
+| locktag            | text     | Lock information that the session waits for. It can be parsed using the **locktag_decode()** function. |
+| global_sessionid   | text     | Global session ID                                            |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/memory/GLOBAL_MEMORY_NODE_DETAIL.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/memory/GLOBAL_MEMORY_NODE_DETAIL.md
new file mode 100644
index 0000000000000000000000000000000000000000..1d7b0aee132a1ab88e80a1b486c8f9731e8ac52b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/memory/GLOBAL_MEMORY_NODE_DETAIL.md
@@ -0,0 +1,18 @@
+---
+title: GLOBAL_MEMORY_NODE_DETAIL
+summary: GLOBAL_MEMORY_NODE_DETAIL
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_MEMORY_NODE_DETAIL
+
+The memory usage of all normal nodes in MogDB is displayed.
+
+**Table 1** GLOBAL_MEMORY_NODE_DETAIL fields
+
+| **Name**     | **Type** | **Description**                                              |
+| :----------- | :------- | :----------------------------------------------------------- |
+| nodename     | text     | Node name.                                                   |
+| memorytype   | text     | Memory name.<br/>- **max_process_memory**: memory occupied by the MogDB instance<br/>- **process_used_memory**: memory occupied by a process<br/>- **max_dynamic_memory**: maximum dynamic memory<br/>- **dynamic_used_memory**: used dynamic memory<br/>- **dynamic_peak_memory**: dynamic peak value of the memory<br/>- **dynamic_used_shrctx**: maximum dynamic shared memory context<br/>- **dynamic_peak_shrctx**: dynamic peak value of the shared memory context<br/>- **max_shared_memory**: maximum shared memory<br/>- **shared_used_memory**: used shared memory<br/>- **max_cstore_memory**: maximum memory allowed by the column<br/>- **cstore_used_memory**: memory used in column storage<br/>- **max_sctpcomm_memory**: maximum memory size allowed for the SCTP communications<br/>- **sctpcomm_used_memory**: memory used for SCTP communications<br/>- **sctpcomm_peak_memory**: memory peak of SCTP communications<br/>- **other_used_memory**: other used memory<br/>- **gpu_max_dynamic_memory**: maximum dynamic memory of GPU<br/>- **gpu_dynamic_used_memory**: used dynamic memory of GPU<br/>- **gpu_dynamic_peak_memory**: dynamic peak value of the GPU memory<br/>- **pooler_conn_memory**: applied memory in the connection pool<br/>- **pooler_freeconn_memory**: memory occupied by idle connections in the connection pool<br/>- **storage_compress_memory**: memory used by the storage module for compression<br/>- **udf_reserved_memory**: reserved memory for the UDF |
+| memorymbytes | integer  | Size of the used memory in the unit of MB.                   |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/memory/GLOBAL_SHARED_MEMORY_DETAIL.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/memory/GLOBAL_SHARED_MEMORY_DETAIL.md
new file mode 100644
index 0000000000000000000000000000000000000000..786105514176edb38b472b6a417065bb5be08d68
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/memory/GLOBAL_SHARED_MEMORY_DETAIL.md
@@ -0,0 +1,22 @@
+---
+title: GLOBAL_SHARED_MEMORY_DETAIL
+summary: GLOBAL_SHARED_MEMORY_DETAIL
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_SHARED_MEMORY_DETAIL
+
+**GLOBAL_SHARED_MEMORY_DETAIL** is used to query the usage of shared memory contexts on all normal nodes in MogDB.
+
+**Table 1** GLOBAL_SHARED_MEMORY_DETAIL columns
+
+| **Name**    | **Type** | **Description**                                  |
+| :---------- | :------- | :----------------------------------------------- |
+| node_name   | name     | Node name                                        |
+| contextname | text     | Name of the memory context                       |
+| level       | smallint | Level of the memory context                      |
+| parent      | text     | Name of the parent memory context                |
+| totalsize   | bigint   | Total size of the shared memory (unit: byte)     |
+| freesize    | bigint   | Remaining size of the shared memory (unit: byte) |
+| usedsize    | bigint   | Used size of the shared memory (unit: byte)      |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/memory/GS_SHARED_MEMORY_DETAIL.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/memory/GS_SHARED_MEMORY_DETAIL.md
new file mode 100644
index 0000000000000000000000000000000000000000..ec9af76e1dbd4952d7ed5ad5878d67dc0a599368
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/memory/GS_SHARED_MEMORY_DETAIL.md
@@ -0,0 +1,21 @@
+---
+title: GS_SHARED_MEMORY_DETAIL
+summary: GS_SHARED_MEMORY_DETAIL
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_SHARED_MEMORY_DETAIL
+
+**GS_SHARED_MEMORY_DETAIL** queries the usage information about shared memory contexts on the current node.
+
+**Table 1** GS_SHARED_MEMORY_DETAIL columns
+
+| Name        | Type     | Description                                      |
+| :---------- | :------- | :----------------------------------------------- |
+| contextname | text     | Name of the memory context                       |
+| level       | smallint | Level of the memory context                      |
+| parent      | text     | Name of the parent memory context                |
+| totalsize   | bigint   | Total size of the shared memory (unit: byte)     |
+| freesize    | bigint   | Remaining size of the shared memory (unit: byte) |
+| usedsize    | bigint   | Used size of the shared memory (unit: byte)      |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/memory/MEMORY_NODE_DETAIL.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/memory/MEMORY_NODE_DETAIL.md
new file mode 100644
index 0000000000000000000000000000000000000000..7b70f53c08c2248a7bc63517235ced47efd59860
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/memory/MEMORY_NODE_DETAIL.md
@@ -0,0 +1,18 @@
+---
+title: MEMORY_NODE_DETAIL
+summary: MEMORY_NODE_DETAIL
+author: Guo Huan
+date: 2021-04-19
+---
+
+# MEMORY_NODE_DETAIL
+
+**MEMORY_NODE_DETAIL** displays memory usage of a node in the database.
+
+**Table 1** MEMORY_NODE_DETAIL columns
+
+| **Name**     | **Type** | **Description**                                              |
+| :----------- | :------- | :----------------------------------------------------------- |
+| nodename     | text     | Node name                                                    |
+| memorytype   | text     | Memory name<br/>- **max_process_memory**: memory occupied by the MogDB instance<br/>- **process_used_memory**: memory occupied by a process<br/>- **max_dynamic_memory**: maximum dynamic memory<br/>- **dynamic_used_memory**: used dynamic memory<br/>- **dynamic_peak_memory**: dynamic peak value of the memory<br/>- **dynamic_used_shrctx**: maximum dynamic shared memory context<br/>- **dynamic_peak_shrctx**: dynamic peak value of the shared memory context<br/>- **max_shared_memory**: maximum shared memory<br/>- **shared_used_memory**: used shared memory<br/>- **max_cstore_memory**: maximum memory allowed by the column<br/>- **cstore_used_memory**: memory used in column storage<br/>- **max_sctpcomm_memory**: maximum memory size allowed for the SCTP communications<br/>- **sctpcomm_used_memory**: memory used for SCTP communications<br/>- **sctpcomm_peak_memory**: memory peak of SCTP communications<br/>- **other_used_memory**: other used memory<br/>- **gpu_max_dynamic_memory**: maximum dynamic GPU memory<br/>- **gpu_dynamic_used_memory**: used dynamic memory of GPU<br/>- **gpu_dynamic_peak_memory**: dynamic peak value of the GPU memory<br/>- **pooler_conn_memory**: applied memory in the connection pool<br/>- **pooler_freeconn_memory**: memory occupied by idle connections in the connection pool<br/>- **storage_compress_memory**: memory used by the storage module for compression<br/>- **udf_reserved_memory**: reserved memory for the UDF |
+| memorymbytes | integer  | Size of the used memory in the unit of MB.                   |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_ALL_INDEXES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_ALL_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..2a5445800d31daa190a4063cabf98ee0eef93d70
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_ALL_INDEXES.md
@@ -0,0 +1,24 @@
+---
+title: GLOBAL_STAT_ALL_INDEXES
+summary: GLOBAL_STAT_ALL_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STAT_ALL_INDEXES
+
+**GLOBAL_STAT_ALL_INDEXES** contains every row of each index in databases on each node, showing statistics about accesses to specific indexes.
+
+**Table 1** GLOBAL_STAT_ALL_INDEXES columns
+
+| **Name**      | **Type** | **Description**                                              |
+| :------------ | :------- | :----------------------------------------------------------- |
+| node_name     | name     | Node name                                                    |
+| relid         | oid      | OID of the table for this index                              |
+| indexrelid    | oid      | OID of the index                                             |
+| schemaname    | name     | Name of the schema that the index is in                      |
+| relname       | name     | Name of the table for the index                              |
+| indexrelname  | name     | Index name                                                   |
+| idx_scan      | bigint   | Number of index scans initiated on the index                 |
+| idx_tup_read  | bigint   | Number of index entries returned by scans on the index       |
+| idx_tup_fetch | bigint   | Number of live table rows fetched by simple index scans using the index |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_ALL_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_ALL_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..5914b4a8879b50b091d8a8c1abc5879ad6be578c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_ALL_TABLES.md
@@ -0,0 +1,37 @@
+---
+title: GLOBAL_STAT_ALL_TABLES
+summary: GLOBAL_STAT_ALL_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STAT_ALL_TABLES
+
+**GLOBAL_STAT_ALL_TABLES** displays statistics about one row for each table (including TOAST tables) in databases on each node.
+
+**Table 1** GLOBAL_STAT_ALL_TABLES columns
+
+| **Name**          | **Type**                 | **Description**                                              |
+| :---------------- | :----------------------- | :----------------------------------------------------------- |
+| node_name         | name                     | Node name                                                    |
+| relid             | oid                      | OID of the table                                             |
+| schemaname        | name                     | Name of the schema that contains the table                   |
+| relname           | name                     | Table name                                                   |
+| seq_scan          | bigint                   | Number of sequential scans initiated on this table           |
+| seq_tup_read      | bigint                   | Number of live rows fetched by sequential scans              |
+| idx_scan          | bigint                   | Number of index scans initiated on the table                 |
+| idx_tup_fetch     | bigint                   | Number of live rows fetched by index scans                   |
+| n_tup_ins         | bigint                   | Number of rows inserted                                      |
+| n_tup_upd         | bigint                   | Number of rows updated                                       |
+| n_tup_del         | bigint                   | Number of rows deleted                                       |
+| n_tup_hot_upd     | bigint                   | Number of rows HOT updated (with no separate index update required) |
+| n_live_tup        | bigint                   | Estimated number of live rows                                |
+| n_dead_tup        | bigint                   | Estimated number of dead rows                                |
+| last_vacuum       | timestamp with time zone | Last time at which this table was manually vacuumed (not counting **VACUUM FULL**) |
+| last_autovacuum   | timestamp with time zone | Last time at which this table was vacuumed by the autovacuum daemon |
+| last_analyze      | timestamp with time zone | Last time at which this table was manually analyzed          |
+| last_autoanalyze  | timestamp with time zone | Last time at which this table was analyzed by the autovacuum daemon |
+| vacuum_count      | bigint                   | Number of times the table has been manually vacuumed (not counting **VACUUM FULL**) |
+| autovacuum_count  | bigint                   | Number of times the table has been vacuumed by the autovacuum daemon |
+| analyze_count     | bigint                   | Number of times the table has been manually analyzed         |
+| autoanalyze_count | bigint                   | Number of times the table has been analyzed by the autovacuum daemon |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_BAD_BLOCK.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_BAD_BLOCK.md
new file mode 100644
index 0000000000000000000000000000000000000000..e3481af231c1199c189fbbb4e2093c362bf186ca
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_BAD_BLOCK.md
@@ -0,0 +1,23 @@
+---
+title: GLOBAL_STAT_BAD_BLOCK
+summary: GLOBAL_STAT_BAD_BLOCK
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STAT_BAD_BLOCK
+
+**GLOBAL_STAT_BAD_BLOCK** displays information about table and index read failures on each node.
+
+**Table 1** GLOBAL_STAT_BAD_BLOCK columns
+
+| **Name**     | **Type**                 | **Description**                        |
+| :----------- | :----------------------- | :------------------------------------- |
+| node_name    | text                     | Node name                              |
+| databaseid   | integer                  | OID of the database                    |
+| tablespaceid | integer                  | OID of the tablespace                  |
+| relfilenode  | integer                  | File node of this relation             |
+| forknum      | integer                  | Fork number                            |
+| error_count  | integer                  | Number of errors                       |
+| first_time   | timestamp with time zone | Time when the first bad block occurred |
+| last_time    | timestamp with time zone | Time when the last bad block occurred  |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_DATABASE.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_DATABASE.md
new file mode 100644
index 0000000000000000000000000000000000000000..708779f133a0a639f3cc50bb6b72967d9c6a4dee
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_DATABASE.md
@@ -0,0 +1,35 @@
+---
+title: GLOBAL_STAT_DATABASE
+summary: GLOBAL_STAT_DATABASE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STAT_DATABASE
+
+**GLOBAL_STAT_DATABASE** contains every row of each database on each node in MogDB, showing database-wide statistics.
+
+**Table 1** GLOBAL_STAT_DATABASE columns
+
+| **Name**       | **Type**                 | **Description**                                              |
+| :------------- | :----------------------- | :----------------------------------------------------------- |
+| node_name      | name                     | Node name                                                    |
+| datid          | oid                      | OID of the database                                          |
+| datname        | name                     | Name of the database                                         |
+| numbackends    | integer                  | Number of backends currently connected to this database. This is the only column in this view that returns a value reflecting the current state; all other columns return the accumulated values since the last reset. |
+| xact_commit    | bigint                   | Number of transactions in this database that have been committed |
+| xact_rollback  | bigint                   | Number of transactions in this database that have been rolled back |
+| blks_read      | bigint                   | Number of disk blocks read in this database                  |
+| blks_hit       | bigint                   | Number of times disk blocks were found in the buffer cache (unnecessary as the number includes only hits in the database kernel buffer cache) |
+| tup_returned   | bigint                   | Number of rows returned by queries in this database          |
+| tup_fetched    | bigint                   | Number of rows fetched by queries in this database           |
+| tup_inserted   | bigint                   | Number of rows inserted by queries in this database          |
+| tup_updated    | bigint                   | Number of rows updated by queries in this database           |
+| tup_deleted    | bigint                   | Number of rows deleted by queries in this database           |
+| conflicts      | bigint                   | Number of queries canceled due to database recovery conflicts (conflicts occurring only on the standby server). For details, see STAT_DATABASE_CONFLICTS. |
+| temp_files     | bigint                   | Number of temporary files created by queries in this database. All temporary files are counted, regardless of why the temporary file was created (for example, sorting or hashing), and regardless of the **log_temp_files** setting. |
+| temp_bytes     | bigint                   | Total amount of data written to temporary files by queries in this database. All temporary files are counted, regardless of why the temporary file was created, and regardless of the **log_temp_files** setting. |
+| deadlocks      | bigint                   | Number of deadlocks detected in this database                |
+| blk_read_time  | double precision         | Time spent reading data file blocks by backends in this database (unit: ms) |
+| blk_write_time | double precision         | Time spent writing into data file blocks by backends in this database (unit: ms) |
+| stats_reset    | timestamp with time zone | Time at which the current statistics were reset              |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_DATABASE_CONFLICTS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_DATABASE_CONFLICTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..0488c1c438ae58433c9c15593c4db51d868fdfce
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_DATABASE_CONFLICTS.md
@@ -0,0 +1,23 @@
+---
+title: GLOBAL_STAT_DATABASE_CONFLICTS
+summary: GLOBAL_STAT_DATABASE_CONFLICTS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STAT_DATABASE_CONFLICTS
+
+**GLOBAL_STAT_DATABASE_CONFLICTS** displays statistics about database conflicts on each node.
+
+**Table 1** GLOBAL_STAT_DATABASE_CONFLICTS columns
+
+| Name             | Type   | Description                       |
+| :--------------- | :----- | :-------------------------------- |
+| node_name        | name   | Node name                         |
+| datid            | oid    | Database ID                       |
+| datname          | name   | Database name                     |
+| confl_tablespace | bigint | Number of conflicting tablespaces |
+| confl_lock       | bigint | Number of conflicting locks       |
+| confl_snapshot   | bigint | Number of conflicting snapshots   |
+| confl_bufferpin  | bigint | Number of conflicting buffers     |
+| confl_deadlock   | bigint | Number of conflicting deadlocks   |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_SYS_INDEXES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_SYS_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..178f9a8137054bf90e064805d2460524f632fc56
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_SYS_INDEXES.md
@@ -0,0 +1,24 @@
+---
+title: GLOBAL_STAT_SYS_INDEXES
+summary: GLOBAL_STAT_SYS_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STAT_SYS_INDEXES
+
+**GLOBAL_STAT_SYS_INDEXES** displays index status information about all the system catalogs in the **pg_catalog**, **information_schema**, and **pg_toast** schemas on each node.
+
+**Table 1** GLOBAL_STAT_SYS_INDEXES columns
+
+| **Name**      | **Type** | **Description**                                              |
+| :------------ | :------- | :----------------------------------------------------------- |
+| node_name     | name     | Node name                                                    |
+| relid         | oid      | OID of the table for this index                              |
+| indexrelid    | oid      | OID of the index                                             |
+| schemaname    | name     | Name of the schema that the index is in                      |
+| relname       | name     | Name of the table for the index                              |
+| indexrelname  | name     | Index name                                                   |
+| idx_scan      | bigint   | Number of index scans initiated on the index                 |
+| idx_tup_read  | bigint   | Number of index entries returned by scans on the index       |
+| idx_tup_fetch | bigint   | Number of live table rows fetched by simple index scans using the index |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_SYS_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_SYS_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..04691c7fabd63dc122c2698927882761990e0333
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_SYS_TABLES.md
@@ -0,0 +1,37 @@
+---
+title: GLOBAL_STAT_SYS_TABLES
+summary: GLOBAL_STAT_SYS_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STAT_SYS_TABLES
+
+**GLOBAL_STAT_SYS_TABLES** displays statistics about the system catalogs of all the namespaces in **pg_catalog** and **information_schema** schemas on each node.
+
+**Table 1** GLOBAL_STAT_SYS_TABLES columns
+
+| **Name**          | **Type**                 | **Description**                                              |
+| :---------------- | :----------------------- | :----------------------------------------------------------- |
+| node_name         | name                     | Node name                                                    |
+| relid             | oid                      | OID of the table                                             |
+| schemaname        | name                     | Name of the schema that contains the table                   |
+| relname           | name                     | Table name                                                   |
+| seq_scan          | bigint                   | Number of sequential scans initiated on this table           |
+| seq_tup_read      | bigint                   | Number of live rows fetched by sequential scans              |
+| idx_scan          | bigint                   | Number of index scans initiated on the table                 |
+| idx_tup_fetch     | bigint                   | Number of live rows fetched by index scans                   |
+| n_tup_ins         | bigint                   | Number of rows inserted                                      |
+| n_tup_upd         | bigint                   | Number of rows updated                                       |
+| n_tup_del         | bigint                   | Number of rows deleted                                       |
+| n_tup_hot_upd     | bigint                   | Number of rows HOT updated (with no separate index update required) |
+| n_live_tup        | bigint                   | Estimated number of live rows                                |
+| n_dead_tup        | bigint                   | Estimated number of dead rows                                |
+| last_vacuum       | timestamp with time zone | Last time at which this table was manually vacuumed (not counting **VACUUM FULL**) |
+| last_autovacuum   | timestamp with time zone | Last time at which this table was vacuumed by the autovacuum daemon |
+| last_analyze      | timestamp with time zone | Last time at which this table was manually analyzed          |
+| last_autoanalyze  | timestamp with time zone | Last time at which this table was analyzed by the autovacuum daemon |
+| vacuum_count      | bigint                   | Number of times the table has been manually vacuumed (not counting **VACUUM FULL**) |
+| autovacuum_count  | bigint                   | Number of times the table has been vacuumed by the autovacuum daemon |
+| analyze_count     | bigint                   | Number of times the table has been manually analyzed         |
+| autoanalyze_count | bigint                   | Number of times the table has been analyzed by the autovacuum daemon |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_USER_FUNCTIONS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_USER_FUNCTIONS.md
new file mode 100644
index 0000000000000000000000000000000000000000..59f09c846e850aad2b42770b80e52d9012a4d4da
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_USER_FUNCTIONS.md
@@ -0,0 +1,22 @@
+---
+title: GLOBAL_STAT_USER_FUNCTIONS
+summary: GLOBAL_STAT_USER_FUNCTIONS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STAT_USER_FUNCTIONS
+
+**GLOBAL_STAT_USER_FUNCTIONS** displays statistics about the status of functions created by users on each node in MogDB.
+
+**Table 1** GLOBAL_STAT_USER_FUNCTIONS columns
+
+| **Name**   | **Type**         | **Description**                                              |
+| :--------- | :--------------- | :----------------------------------------------------------- |
+| node_name  | name             | Node name                                                    |
+| funcid     | oid              | ID of the function                                           |
+| schemaname | name             | Schema name                                                  |
+| funcname   | name             | Function name                                                |
+| calls      | bigint           | Number of times the function has been called                 |
+| total_time | double precision | Total time spent in this function and all other functions called by it (unit: ms) |
+| self_time  | double precision | Total time spent in this function, excluding other functions called by it (unit: ms) |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_USER_INDEXES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_USER_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..646c2125b822aedfb8893db3c82759825bc95642
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_USER_INDEXES.md
@@ -0,0 +1,24 @@
+---
+title: GLOBAL_STAT_USER_INDEXES
+summary: GLOBAL_STAT_USER_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STAT_USER_INDEXES
+
+**GLOBAL_STAT_USER_INDEXES** displays the status information about the index of user-defined ordinary tables in all databases of each node.
+
+**Table 1** GLOBAL_STAT_USER_INDEXES columns
+
+| **Name**      | **Type** | **Description**                                              |
+| :------------ | :------- | :----------------------------------------------------------- |
+| node_name     | name     | Node name                                                    |
+| relid         | oid      | OID of the table for this index                              |
+| indexrelid    | oid      | OID of the index                                             |
+| schemaname    | name     | Name of the schema that the index is in                      |
+| relname       | name     | Name of the table for the index                              |
+| indexrelname  | name     | Index name                                                   |
+| idx_scan      | bigint   | Number of index scans initiated on the index                 |
+| idx_tup_read  | bigint   | Number of index entries returned by scans on the index       |
+| idx_tup_fetch | bigint   | Number of live table rows fetched by simple index scans using the index |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_USER_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_USER_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..f8134977fcaacb03da7ac6645eb9e45537de5999
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_USER_TABLES.md
@@ -0,0 +1,37 @@
+---
+title: GLOBAL_STAT_USER_TABLES
+summary: GLOBAL_STAT_USER_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STAT_USER_TABLES
+
+**GLOBAL_STAT_USER_TABLES** displays the status information about user-defined ordinary tables in all namespaces on each node.
+
+**Table 1** GLOBAL_STAT_USER_TABLES columns
+
+| **Name**          | **Type**                 | **Description**                                              |
+| :---------------- | :----------------------- | :----------------------------------------------------------- |
+| node_name         | name                     | Node name                                                    |
+| relid             | oid                      | OID of the table                                             |
+| schemaname        | name                     | Name of the schema that contains the table                   |
+| relname           | name                     | Table name                                                   |
+| seq_scan          | bigint                   | Number of sequential scans initiated on this table           |
+| seq_tup_read      | bigint                   | Number of live rows fetched by sequential scans              |
+| idx_scan          | bigint                   | Number of index scans initiated on the table                 |
+| idx_tup_fetch     | bigint                   | Number of live rows fetched by index scans                   |
+| n_tup_ins         | bigint                   | Number of rows inserted                                      |
+| n_tup_upd         | bigint                   | Number of rows updated                                       |
+| n_tup_del         | bigint                   | Number of rows deleted                                       |
+| n_tup_hot_upd     | bigint                   | Number of rows HOT updated (with no separate index update required) |
+| n_live_tup        | bigint                   | Estimated number of live rows                                |
+| n_dead_tup        | bigint                   | Estimated number of dead rows                                |
+| last_vacuum       | timestamp with time zone | Last time at which this table was manually vacuumed (not counting **VACUUM FULL**) |
+| last_autovacuum   | timestamp with time zone | Last time at which this table was vacuumed by the autovacuum daemon |
+| last_analyze      | timestamp with time zone | Last time at which this table was manually analyzed          |
+| last_autoanalyze  | timestamp with time zone | Last time at which this table was analyzed by the autovacuum daemon |
+| vacuum_count      | bigint                   | Number of times the table has been manually vacuumed (not counting **VACUUM FULL**) |
+| autovacuum_count  | bigint                   | Number of times the table has been vacuumed by the autovacuum daemon |
+| analyze_count     | bigint                   | Number of times the table has been manually analyzed         |
+| autoanalyze_count | bigint                   | Number of times the table has been analyzed by the autovacuum daemon |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_ALL_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_ALL_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..7ac02759df7753cadf4febf8c268778093dd84fc
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_ALL_TABLES.md
@@ -0,0 +1,27 @@
+---
+title: GLOBAL_STAT_XACT_ALL_TABLES
+summary: GLOBAL_STAT_XACT_ALL_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STAT_XACT_ALL_TABLES
+
+**GLOBAL_STAT_XACT_ALL_TABLES** displays transaction status information about all ordinary tables and TOAST tables in namespaces on each node.
+
+**Table 1** GLOBAL_STAT_XACT_ALL_TABLES columns
+
+| **Name**      | **Type** | **Description**                                              |
+| :------------ | :------- | :----------------------------------------------------------- |
+| node_name     | name     | Node name                                                    |
+| relid         | oid      | OID of the table                                             |
+| schemaname    | name     | Name of the schema that contains the table                   |
+| relname       | name     | Table name                                                   |
+| seq_scan      | bigint   | Number of sequential scans initiated on this table           |
+| seq_tup_read  | bigint   | Number of live rows fetched by sequential scans              |
+| idx_scan      | bigint   | Number of index scans initiated on the table                 |
+| idx_tup_fetch | bigint   | Number of live rows fetched by index scans                   |
+| n_tup_ins     | bigint   | Number of rows inserted                                      |
+| n_tup_upd     | bigint   | Number of rows updated                                       |
+| n_tup_del     | bigint   | Number of rows deleted                                       |
+| n_tup_hot_upd | bigint   | Number of rows HOT updated (with no separate index update required) |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_SYS_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_SYS_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..f1455b91c6c6137c4e1fd714a34dc7311829ac58
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_SYS_TABLES.md
@@ -0,0 +1,27 @@
+---
+title: GLOBAL_STAT_XACT_SYS_TABLES
+summary: GLOBAL_STAT_XACT_SYS_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STAT_XACT_SYS_TABLES
+
+**GLOBAL_STAT_XACT_SYS_TABLES** displays transaction status information about the system catalogs in namespaces on each node.
+
+**Table 1** GLOBAL_STAT_XACT_SYS_TABLES columns
+
+| **Name**      | **Type** | **Description**                                              |
+| :------------ | :------- | :----------------------------------------------------------- |
+| node_name     | name     | Node name                                                    |
+| relid         | oid      | OID of the table                                             |
+| schemaname    | name     | Name of the schema that contains the table                   |
+| relname       | name     | Table name                                                   |
+| seq_scan      | bigint   | Number of sequential scans initiated on this table           |
+| seq_tup_read  | bigint   | Number of live rows fetched by sequential scans              |
+| idx_scan      | bigint   | Number of index scans initiated on the table                 |
+| idx_tup_fetch | bigint   | Number of live rows fetched by index scans                   |
+| n_tup_ins     | bigint   | Number of rows inserted                                      |
+| n_tup_upd     | bigint   | Number of rows updated                                       |
+| n_tup_del     | bigint   | Number of rows deleted                                       |
+| n_tup_hot_upd | bigint   | Number of rows HOT updated (with no separate index update required) |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_USER_FUNCTIONS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_USER_FUNCTIONS.md
new file mode 100644
index 0000000000000000000000000000000000000000..625314eccec0ad4237c0c128498df19402950dae
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_USER_FUNCTIONS.md
@@ -0,0 +1,22 @@
+---
+title: GLOBAL_STAT_XACT_USER_FUNCTIONS
+summary: GLOBAL_STAT_XACT_USER_FUNCTIONS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STAT_XACT_USER_FUNCTIONS
+
+**GLOBAL_STAT_XACT_USER_FUNCTIONS** displays statistics about function executions in transactions on each node.
+
+**Table 1** GLOBAL_STAT_XACT_USER_FUNCTIONS columns
+
+| **Name**   | **Type**         | **Description**                                              |
+| :--------- | :--------------- | :----------------------------------------------------------- |
+| node_name  | name             | Node name                                                    |
+| funcid     | oid              | OID of a function                                            |
+| schemaname | name             | Schema name                                                  |
+| funcname   | name             | Function name                                                |
+| calls      | bigint           | Number of times that the function has been called            |
+| total_time | double precision | Total time spent in this function and all other functions called by it |
+| self_time  | double precision | Total time spent in this function, excluding other functions called by it |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_USER_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_USER_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..e7f4e52740b1c25d523057141f70e99fe8a81a0b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_USER_TABLES.md
@@ -0,0 +1,27 @@
+---
+title: GLOBAL_STAT_XACT_USER_TABLES
+summary: GLOBAL_STAT_XACT_USER_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STAT_XACT_USER_TABLES
+
+**GLOBAL_STAT_XACT_USER_TABLES** displays transaction status information about the user tables in namespaces on each node.
+
+**Table 1** GLOBAL_STAT_XACT_USER_TABLES columns
+
+| **Name**      | **Type** | **Description**                                              |
+| :------------ | :------- | :----------------------------------------------------------- |
+| node_name     | name     | Node name                                                    |
+| relid         | oid      | OID of the table                                             |
+| schemaname    | name     | Name of the schema that contains the table                   |
+| relname       | name     | Table name                                                   |
+| seq_scan      | bigint   | Number of sequential scans initiated on this table           |
+| seq_tup_read  | bigint   | Number of live rows fetched by sequential scans              |
+| idx_scan      | bigint   | Number of index scans initiated on the table                 |
+| idx_tup_fetch | bigint   | Number of live rows fetched by index scans                   |
+| n_tup_ins     | bigint   | Number of rows inserted                                      |
+| n_tup_upd     | bigint   | Number of rows updated                                       |
+| n_tup_del     | bigint   | Number of rows deleted                                       |
+| n_tup_hot_upd | bigint   | Number of rows HOT updated (with no separate index update required) |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_ALL_INDEXES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_ALL_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..390776840ca46d0c071be57036d5577856d3d1d0
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_ALL_INDEXES.md
@@ -0,0 +1,23 @@
+---
+title: STAT_ALL_INDEXES
+summary: STAT_ALL_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STAT_ALL_INDEXES
+
+**STAT_ALL_INDEXES** contains every row of each index in databases on the current node, showing statistics about accesses to specific indexes.
+
+**Table 1** STAT_ALL_INDEXES columns
+
+| **Name**      | **Type** | **Description**                                              |
+| :------------ | :------- | :----------------------------------------------------------- |
+| relid         | oid      | OID of the table for this index                              |
+| indexrelid    | oid      | OID of the index                                             |
+| schemaname    | name     | Name of the schema that the index is in                      |
+| relname       | name     | Name of the table for the index                              |
+| indexrelname  | name     | Index name                                                   |
+| idx_scan      | bigint   | Number of index scans initiated on the index                 |
+| idx_tup_read  | bigint   | Number of index entries returned by scans on the index       |
+| idx_tup_fetch | bigint   | Number of live table rows fetched by simple index scans using the index |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_ALL_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_ALL_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..9edd8d354ca9f8e9b2668d05a312e90420ac7ae6
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_ALL_TABLES.md
@@ -0,0 +1,36 @@
+---
+title: STAT_ALL_TABLES
+summary: STAT_ALL_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STAT_ALL_TABLES
+
+**STAT_ALL_TABLES** displays statistics about one row for each table (including TOAST tables) in databases on this node.
+
+**Table 1** STAT_ALL_TABLES columns
+
+| Name              | Type                     | Description                                                  |
+| :---------------- | :----------------------- | :----------------------------------------------------------- |
+| relid             | oid                      | Table OID                                                    |
+| schemaname        | name                     | Name of the schema that the table is in                      |
+| relname           | name                     | Table name                                                   |
+| seq_scan          | bigint                   | Number of sequential scans initiated on the table            |
+| seq_tup_read      | bigint                   | Number of live rows fetched by sequential scans              |
+| idx_scan          | bigint                   | Number of index scans initiated on the table                 |
+| idx_tup_fetch     | bigint                   | Number of live rows fetched by index scans                   |
+| n_tup_ins         | bigint                   | Number of rows inserted                                      |
+| n_tup_upd         | bigint                   | Number of rows updated                                       |
+| n_tup_del         | bigint                   | Number of rows deleted                                       |
+| n_tup_hot_upd     | bigint                   | Number of rows HOT updated (with no separate index update required) |
+| n_live_tup        | bigint                   | Estimated number of live rows                                |
+| n_dead_tup        | bigint                   | Estimated number of dead rows                                |
+| last_vacuum       | timestamp with time zone | Last time at which this table was manually vacuumed (not counting **VACUUM FULL**) |
+| last_autovacuum   | timestamp with time zone | Last time at which this table was vacuumed by the autovacuum daemon |
+| last_analyze      | timestamp with time zone | Last time at which the table was manually analyzed           |
+| last_autoanalyze  | timestamp with time zone | Last time at which this table was analyzed by the autovacuum daemon |
+| vacuum_count      | bigint                   | Number of times the table has been manually vacuumed (not counting **VACUUM FULL**) |
+| autovacuum_count  | bigint                   | Number of times this table has been vacuumed by the autovacuum daemon |
+| analyze_count     | bigint                   | Number of times the table has been manually analyzed         |
+| autoanalyze_count | bigint                   | Number of times the table has been analyzed by the autovacuum daemon |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_BAD_BLOCK.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_BAD_BLOCK.md
new file mode 100644
index 0000000000000000000000000000000000000000..35f496191421550efd148b7883b5755a5c7715dd
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_BAD_BLOCK.md
@@ -0,0 +1,24 @@
+---
+title: STAT_BAD_BLOCK
+summary: STAT_BAD_BLOCK
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STAT_BAD_BLOCK
+
+**STAT_BAD_BLOCK** displays information about table and index read failures on the current node.
+
+**Table 1** STAT_BAD_BLOCK columns
+
+| **Name**     | **Type**                 | **Description**                         |
+| :----------- | :----------------------- | :-------------------------------------- |
+| nodename     | text                     | Database process name                   |
+| databaseid   | integer                  | OID of the database                     |
+| tablespaceid | integer                  | OID of the tablespace                   |
+| relfilenode  | integer                  | File node of this relation              |
+| bucketid     | smallint                 | ID of the bucket for consistent hashing |
+| forknum      | integer                  | Fork number                             |
+| error_count  | integer                  | Number of errors                        |
+| first_time   | timestamp with time zone | Time when the first bad block occurred  |
+| last_time    | timestamp with time zone | Time when the last bad block occurred   |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_DATABASE.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_DATABASE.md
new file mode 100644
index 0000000000000000000000000000000000000000..4d969416291887d412eea36e29353f9777b53fd1
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_DATABASE.md
@@ -0,0 +1,34 @@
+---
+title: STAT_DATABASE
+summary: STAT_DATABASE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STAT_DATABASE
+
+**STAT_DATABASE** contains statistics for each database on this node.
+
+**Table 1** STAT_DATABASE columns
+
+| Name           | Type                     | Description                                                  |
+| :------------- | :----------------------- | :----------------------------------------------------------- |
+| datid          | oid                      | OID of a database                                            |
+| datname        | name                     | Database name                                                |
+| numbackends    | integer                  | Number of backends currently connected to this database. This is the only column in this view that returns a value reflecting the current state; all other columns return the accumulated values since the last reset. |
+| xact_commit    | bigint                   | Number of transactions in this database that have been committed |
+| xact_rollback  | bigint                   | Number of transactions in this database that have been rolled back |
+| blks_read      | bigint                   | Number of disk blocks read in this database                  |
+| blks_hit       | bigint                   | Number of times disk blocks were found in the buffer cache (unnecessary as the number includes only hits in the PostgreSQL buffer cache) |
+| tup_returned   | bigint                   | Number of rows returned by queries in this database          |
+| tup_fetched    | bigint                   | Number of rows fetched by queries in this database           |
+| tup_inserted   | bigint                   | Number of rows inserted by queries in this database          |
+| tup_updated    | bigint                   | Number of rows updated by queries in this database           |
+| tup_deleted    | bigint                   | Number of rows deleted by queries in this database           |
+| conflicts      | bigint                   | Number of queries canceled due to database recovery conflicts (conflicts occurring only on the standby server). For details, see STAT_DATABASE_CONFLICTS. |
+| temp_files     | bigint                   | Number of temporary files created by queries in this database. All temporary files are counted, regardless of why the temporary file was created (for example, sorting or hashing), and regardless of the **log_temp_files** setting. |
+| temp_bytes     | bigint                   | Total amount of data written to temporary files by queries in this database. All temporary files are counted, regardless of why the temporary file was created, and regardless of the **log_temp_files** setting. |
+| deadlocks      | bigint                   | Number of deadlocks detected in this database                |
+| blk_read_time  | double precision         | Time spent reading data file blocks by backends in this database (unit: ms) |
+| blk_write_time | double precision         | Time spent reading data file blocks by backends in this database (unit: ms) |
+| stats_reset    | timestamp with time zone | Time at which the current statistics were reset              |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_DATABASE_CONFLICTS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_DATABASE_CONFLICTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..1c4487cb03244b515fd090c94953dfc97a67de6a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_DATABASE_CONFLICTS.md
@@ -0,0 +1,22 @@
+---
+title: STAT_DATABASE_CONFLICTS
+summary: STAT_DATABASE_CONFLICTS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STAT_DATABASE_CONFLICTS
+
+**STAT_DATABASE_CONFLICTS** displays statistics about database conflicts on the current node.
+
+**Table 1** STAT_DATABASE_CONFLICTS columns
+
+| **Name**         | **Type** | **Description**                   |
+| :--------------- | :------- | :-------------------------------- |
+| datid            | oid      | Database ID                       |
+| datname          | name     | Database name                     |
+| confl_tablespace | bigint   | Number of conflicting tablespaces |
+| confl_lock       | bigint   | Number of conflicting locks       |
+| confl_snapshot   | bigint   | Number of conflicting snapshots   |
+| confl_bufferpin  | bigint   | Number of conflicting buffers     |
+| confl_deadlock   | bigint   | Number of conflicting deadlocks   |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_SYS_INDEXES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_SYS_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..ca38e8ba160abac2471be4813e39e3a2cca054c5
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_SYS_INDEXES.md
@@ -0,0 +1,23 @@
+---
+title: STAT_SYS_INDEXES
+summary: STAT_SYS_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STAT_SYS_INDEXES
+
+**STAT_SYS_INDEXES** displays index status information about all the system catalogs in the **pg_catalog**, **information_schema**, and **pg_toast** schemas.
+
+**Table 1** STAT_SYS_INDEXES columns
+
+| Name          | Type   | Description                                                  |
+| :------------ | :----- | :----------------------------------------------------------- |
+| relid         | oid    | OID of the table for this index                              |
+| indexrelid    | oid    | OID of the index                                             |
+| schemaname    | name   | Name of the schema that the index is in                      |
+| relname       | name   | Name of the table that the index is created for              |
+| indexrelname  | name   | Index name                                                   |
+| idx_scan      | bigint | Number of index scans initiated on the index                 |
+| idx_tup_read  | bigint | Number of index entries returned by scans on the index       |
+| idx_tup_fetch | bigint | Number of live table rows fetched by simple index scans using the index |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_SYS_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_SYS_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..aed53176cebd980156594f6d3524a8bf2c327450
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_SYS_TABLES.md
@@ -0,0 +1,36 @@
+---
+title: STAT_SYS_TABLES
+summary: STAT_SYS_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STAT_SYS_TABLES
+
+**STAT_SYS_TABLES** displays statistics about the system catalogs of all the namespaces in **pg_catalog** and **information_schema** schemas.
+
+**Table 1** STAT_SYS_TABLES columns
+
+| Name              | Type                     | Description                                                  |
+| :---------------- | :----------------------- | :----------------------------------------------------------- |
+| relid             | oid                      | Table OID                                                    |
+| schemaname        | name                     | Name of the schema that the table is in                      |
+| relname           | name                     | Table name                                                   |
+| seq_scan          | bigint                   | Number of sequential scans initiated on the table            |
+| seq_tup_read      | bigint                   | Number of live rows fetched by sequential scans              |
+| idx_scan          | bigint                   | Number of index scans initiated on the table                 |
+| idx_tup_fetch     | bigint                   | Number of live rows fetched by index scans                   |
+| n_tup_ins         | bigint                   | Number of rows inserted                                      |
+| n_tup_upd         | bigint                   | Number of rows updated                                       |
+| n_tup_del         | bigint                   | Number of rows deleted                                       |
+| n_tup_hot_upd     | bigint                   | Number of rows HOT updated (with no separate index update required) |
+| n_live_tup        | bigint                   | Estimated number of live rows                                |
+| n_dead_tup        | bigint                   | Estimated number of dead rows                                |
+| last_vacuum       | timestamp with time zone | Last time at which this table was manually vacuumed (not counting **VACUUM FULL**) |
+| last_autovacuum   | timestamp with time zone | Last time at which this table was vacuumed by the autovacuum daemon |
+| last_analyze      | timestamp with time zone | Last time at which the table was manually analyzed           |
+| last_autoanalyze  | timestamp with time zone | Last time at which this table was analyzed by the autovacuum daemon |
+| vacuum_count      | bigint                   | Number of times this table has been manually vacuumed (not counting VACUUM FULL) |
+| autovacuum_count  | bigint                   | Number of times this table has been vacuumed by the autovacuum daemon |
+| analyze_count     | bigint                   | Number of times the table has been manually analyzed         |
+| autoanalyze_count | bigint                   | Number of times the table has been analyzed by the autovacuum daemon |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_USER_FUNCTIONS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_USER_FUNCTIONS.md
new file mode 100644
index 0000000000000000000000000000000000000000..d7abb3c604558e400cc12a6e3d5713cd4816b6cb
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_USER_FUNCTIONS.md
@@ -0,0 +1,21 @@
+---
+title: STAT_USER_FUNCTIONS
+summary: STAT_USER_FUNCTIONS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STAT_USER_FUNCTIONS
+
+**STAT_USER_FUNCTIONS** displays user-defined function status information in the current namespace. (The language of the function is non-internal language.)
+
+**Table 1** STAT_USER_FUNCTIONS columns
+
+| Name       | Type             | Description                                                  |
+| :--------- | :--------------- | :----------------------------------------------------------- |
+| funcid     | oid              | OID of the function                                          |
+| schemaname | name             | Schema name                                                  |
+| funcname   | name             | Rename the customized function.                              |
+| calls      | bigint           | Number of times the function has been called                 |
+| total_time | double precision | Total time spent in this function, including other functions called by it (unit: ms) |
+| self_time  | double precision | Total time spent in this function, excluding other functions called by it (unit: ms) |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_USER_INDEXES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_USER_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..fd976b94915e0eb22de2537b66ed538bf7d0212f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_USER_INDEXES.md
@@ -0,0 +1,23 @@
+---
+title: STAT_USER_INDEXES
+summary: STAT_USER_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STAT_USER_INDEXES
+
+**STAT_USER_INDEXES** displays the status information about the index of user-defined ordinary tables in the current database.
+
+**Table 1** STAT_USER_INDEXES columns
+
+| Name          | Type   | Description                                                  |
+| :------------ | :----- | :----------------------------------------------------------- |
+| relid         | oid    | OID of the table for this index                              |
+| indexrelid    | oid    | OID of the index                                             |
+| schemaname    | name   | Name of the schema that the index is in                      |
+| relname       | name   | Name of the table for the index                              |
+| indexrelname  | name   | Index name                                                   |
+| idx_scan      | bigint | Number of index scans initiated on the index                 |
+| idx_tup_read  | bigint | Number of index entries returned by scans on the index       |
+| idx_tup_fetch | bigint | Number of live table rows fetched by simple index scans using the index |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_USER_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_USER_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..72e52484ed7d68ca46a1e5892e4bc6e6fda85bff
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_USER_TABLES.md
@@ -0,0 +1,36 @@
+---
+title: STAT_USER_TABLES
+summary: STAT_USER_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STAT_USER_TABLES
+
+**STAT_USER_TABLES** displays the status information about user-defined ordinary tables in all namespaces on the current node.
+
+**Table 1** STAT_USER_TABLES columns
+
+| Name              | Type                     | Description                                                  |
+| :---------------- | :----------------------- | :----------------------------------------------------------- |
+| relid             | oid                      | Table OID                                                    |
+| schemaname        | name                     | Name of the schema that the table is in                      |
+| relname           | name                     | Table name                                                   |
+| seq_scan          | bigint                   | Number of sequential scans initiated on the table            |
+| seq_tup_read      | bigint                   | Number of live rows fetched by sequential scans              |
+| idx_scan          | bigint                   | Number of index scans initiated on the table                 |
+| idx_tup_fetch     | bigint                   | Number of live rows fetched by index scans                   |
+| n_tup_ins         | bigint                   | Number of rows inserted                                      |
+| n_tup_upd         | bigint                   | Number of rows updated                                       |
+| n_tup_del         | bigint                   | Number of rows deleted                                       |
+| n_tup_hot_upd     | bigint                   | Number of rows HOT updated (with no separate index update required) |
+| n_live_tup        | bigint                   | Estimated number of live rows                                |
+| n_dead_tup        | bigint                   | Estimated number of dead rows                                |
+| last_vacuum       | timestamp with time zone | Last time at which this table was manually vacuumed (not counting **VACUUM FULL**) |
+| last_autovacuum   | timestamp with time zone | Last time at which this table was vacuumed by the autovacuum daemon |
+| last_analyze      | timestamp with time zone | Last time at which the table was manually analyzed           |
+| last_autoanalyze  | timestamp with time zone | Last time at which this table was analyzed by the autovacuum daemon |
+| vacuum_count      | bigint                   | Number of times the table has been manually vacuumed (not counting **VACUUM FULL**) |
+| autovacuum_count  | bigint                   | Number of times this table has been vacuumed by the autovacuum daemon |
+| analyze_count     | bigint                   | Number of times the table has been manually analyzed         |
+| autoanalyze_count | bigint                   | Number of times the table has been analyzed by the autovacuum daemon |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_XACT_ALL_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_XACT_ALL_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..6b3a2d8936e607e75472a8f405cdc91beee2f534
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_XACT_ALL_TABLES.md
@@ -0,0 +1,26 @@
+---
+title: STAT_XACT_ALL_TABLES
+summary: STAT_XACT_ALL_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STAT_XACT_ALL_TABLES
+
+**STAT_XACT_ALL_TABLES** displays transaction status information about all ordinary tables and TOAST tables in the current namespace.
+
+**Table 1** STAT_XACT_ALL_TABLES columns
+
+| Name          | Type   | Description                                                  |
+| :------------ | :----- | :----------------------------------------------------------- |
+| relid         | oid    | Table OID                                                    |
+| schemaname    | name   | Name of the schema that the table is in                      |
+| relname       | name   | Table name                                                   |
+| seq_scan      | bigint | Number of sequential scans initiated on the table            |
+| seq_tup_read  | bigint | Number of live rows fetched by sequential scans              |
+| idx_scan      | bigint | Number of index scans initiated on the table                 |
+| idx_tup_fetch | bigint | Number of live rows fetched by index scans                   |
+| n_tup_ins     | bigint | Number of rows inserted                                      |
+| n_tup_upd     | bigint | Number of rows updated                                       |
+| n_tup_del     | bigint | Number of rows deleted                                       |
+| n_tup_hot_upd | bigint | Number of rows HOT updated (with no separate index update required) |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_XACT_SYS_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_XACT_SYS_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..f396c906d1eb260b69c2e5cbf538911f338d7f06
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_XACT_SYS_TABLES.md
@@ -0,0 +1,26 @@
+---
+title: STAT_XACT_SYS_TABLES
+summary: STAT_XACT_SYS_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STAT_XACT_SYS_TABLES
+
+**STAT_XACT_SYS_TABLES** displays transaction status information about the system catalogs in namespaces on the current node.
+
+**Table 1** STAT_XACT_SYS_TABLES columns
+
+| Name          | Type   | Description                                                  |
+| :------------ | :----- | :----------------------------------------------------------- |
+| relid         | oid    | Table OID                                                    |
+| schemaname    | name   | Name of the schema that the table is in                      |
+| relname       | name   | Table name                                                   |
+| seq_scan      | bigint | Number of sequential scans initiated on the table            |
+| seq_tup_read  | bigint | Number of live rows fetched by sequential scans              |
+| idx_scan      | bigint | Number of index scans initiated on the table                 |
+| idx_tup_fetch | bigint | Number of live rows fetched by index scans                   |
+| n_tup_ins     | bigint | Number of rows inserted                                      |
+| n_tup_upd     | bigint | Number of rows updated                                       |
+| n_tup_del     | bigint | Number of rows deleted                                       |
+| n_tup_hot_upd | bigint | Number of rows HOT updated (with no separate index update required) |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_XACT_USER_FUNCTIONS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_XACT_USER_FUNCTIONS.md
new file mode 100644
index 0000000000000000000000000000000000000000..523a5465e8ac20e024b8f990fdbc761fe019a72c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_XACT_USER_FUNCTIONS.md
@@ -0,0 +1,21 @@
+---
+title: STAT_XACT_USER_FUNCTIONS
+summary: STAT_XACT_USER_FUNCTIONS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STAT_XACT_USER_FUNCTIONS
+
+**STAT_XACT_USER_FUNCTIONS** displays statistics about function executions in the current transaction.
+
+**Table 1** STAT_XACT_USER_FUNCTIONS columns
+
+| Name       | Type             | Description                                                  |
+| :--------- | :--------------- | :----------------------------------------------------------- |
+| funcid     | oid              | OID of a function                                            |
+| schemaname | name             | Schema name                                                  |
+| funcname   | name             | Function name                                                |
+| calls      | bigint           | Number of times the function has been called                 |
+| total_time | double precision | Total time spent in the function and all other functions called by it |
+| self_time  | double precision | Total time spent in this function, excluding other functions called by it |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_XACT_USER_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_XACT_USER_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..78c4a309c8b50ee4cbf6b0bfc55c7f2dc1741cc9
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_XACT_USER_TABLES.md
@@ -0,0 +1,26 @@
+---
+title: STAT_XACT_USER_TABLES
+summary: STAT_XACT_USER_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STAT_XACT_USER_TABLES
+
+**STAT_XACT_USER_TABLES** displays transaction status information about the user tables in namespaces on the current node.
+
+**Table 1** STAT_XACT_USER_TABLES columns
+
+| Name          | Type   | Description                                                  |
+| :------------ | :----- | :----------------------------------------------------------- |
+| relid         | oid    | Table OID                                                    |
+| schemaname    | name   | Name of the schema that the table is in                      |
+| relname       | name   | Table name                                                   |
+| seq_scan      | bigint | Number of sequential scans initiated on the table            |
+| seq_tup_read  | bigint | Number of live rows fetched by sequential scans              |
+| idx_scan      | bigint | Number of index scans initiated on the table                 |
+| idx_tup_fetch | bigint | Number of live rows fetched by index scans                   |
+| n_tup_ins     | bigint | Number of rows inserted                                      |
+| n_tup_upd     | bigint | Number of rows updated                                       |
+| n_tup_del     | bigint | Number of rows deleted                                       |
+| n_tup_hot_upd | bigint | Number of rows HOT updated (with no separate index update required) |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_ALL_INDEXES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_ALL_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..77017b94fb30a6747fa8be81b94347d6ea1d0724
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_ALL_INDEXES.md
@@ -0,0 +1,21 @@
+---
+title: SUMMARY_STAT_ALL_INDEXES
+summary: SUMMARY_STAT_ALL_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STAT_ALL_INDEXES
+
+**SUMMARY_STAT_ALL_INDEXES** contains every row of each index in databases in MogDB, showing statistics about accesses to specific indexes.
+
+**Table 1** SUMMARY_STAT_ALL_INDEXES columns
+
+| **Name**      | **Type** | **Description**                                              |
+| :------------ | :------- | :----------------------------------------------------------- |
+| schemaname    | name     | Name of the schema that the index is in                      |
+| relname       | name     | Name of the table for the index                              |
+| indexrelname  | name     | Index name                                                   |
+| idx_scan      | numeric  | Number of index scans initiated on the index                 |
+| idx_tup_read  | numeric  | Number of index entries returned by scans on the index       |
+| idx_tup_fetch | numeric  | Number of live table rows fetched by simple index scans using the index |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_ALL_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_ALL_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..0f53d7da12d2778da567d7239e69dcb649023055
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_ALL_TABLES.md
@@ -0,0 +1,35 @@
+---
+title: SUMMARY_STAT_ALL_TABLES
+summary: SUMMARY_STAT_ALL_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STAT_ALL_TABLES
+
+**SUMMARY_STAT_ALL_TABLES** displays statistics about one row for each table (including TOAST tables) in databases in MogDB.
+
+**Table 1** SUMMARY_STAT_ALL_TABLES columns
+
+| **Name**          | **Type**                 | **Description**                                              |
+| :---------------- | :----------------------- | :----------------------------------------------------------- |
+| schemaname        | name                     | Name of the schema that contains the table                   |
+| relname           | name                     | Table name                                                   |
+| seq_scan          | numeric                  | Number of sequential scans initiated on this table           |
+| seq_tup_read      | numeric                  | Number of live rows fetched by sequential scans              |
+| idx_scan          | numeric                  | Number of index scans initiated on the table                 |
+| idx_tup_fetch     | numeric                  | Number of live rows fetched by index scans                   |
+| n_tup_ins         | numeric                  | Number of rows inserted                                      |
+| n_tup_upd         | numeric                  | Number of rows updated                                       |
+| n_tup_del         | numeric                  | Number of rows deleted                                       |
+| n_tup_hot_upd     | numeric                  | Number of rows HOT updated (with no separate index update required) |
+| n_live_tup        | numeric                  | Estimated number of live rows                                |
+| n_dead_tup        | numeric                  | Estimated number of dead rows                                |
+| last_vacuum       | timestamp with time zone | Last time at which this table was manually vacuumed (not counting **VACUUM FULL**) |
+| last_autovacuum   | timestamp with time zone | Last time at which this table was vacuumed by the autovacuum daemon |
+| last_analyze      | timestamp with time zone | Last time at which this table was manually analyzed          |
+| last_autoanalyze  | timestamp with time zone | Last time at which this table was analyzed by the autovacuum daemon |
+| vacuum_count      | numeric                  | Number of times the table has been manually vacuumed (not counting **VACUUM FULL**) |
+| autovacuum_count  | numeric                  | Number of times the table has been vacuumed by the autovacuum daemon |
+| analyze_count     | numeric                  | Number of times the table has been manually analyzed         |
+| autoanalyze_count | numeric                  | Number of times the table has been analyzed by the autovacuum daemon |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_BAD_BLOCK.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_BAD_BLOCK.md
new file mode 100644
index 0000000000000000000000000000000000000000..1cadfd146173c391c45a53c2511f9ecadfbc196b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_BAD_BLOCK.md
@@ -0,0 +1,22 @@
+---
+title: SUMMARY_STAT_BAD_BLOCK
+summary: SUMMARY_STAT_BAD_BLOCK
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STAT_BAD_BLOCK
+
+**SUMMARY_STAT_BAD_BLOCK** displays information about table and index read failures in MogDB.
+
+**Table 1** SUMMARY_STAT_BAD_BLOCK columns
+
+| **Name**     | **Type**                 | **Description**                        |
+| :----------- | :----------------------- | :------------------------------------- |
+| databaseid   | integer                  | OID of the database                    |
+| tablespaceid | integer                  | OID of the tablespace                  |
+| relfilenode  | integer                  | File node of this relation             |
+| forknum      | bigint                   | Fork number                            |
+| error_count  | bigint                   | Number of errors                       |
+| first_time   | timestamp with time zone | Time when the first bad block occurred |
+| last_time    | timestamp with time zone | Time when the last bad block occurred  |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_DATABASE.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_DATABASE.md
new file mode 100644
index 0000000000000000000000000000000000000000..406945b9829934de1203ca2a704d52fb4549a6c5
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_DATABASE.md
@@ -0,0 +1,33 @@
+---
+title: SUMMARY_STAT_DATABASE
+summary: SUMMARY_STAT_DATABASE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STAT_DATABASE
+
+**SUMMARY_STAT_DATABASE** contains every row of each database in the cluster, showing database-wide statistics.
+
+**Table 1** SUMMARY_STAT_DATABASE
+
+| **Name**       | **Type**                 | **Description**                                              |
+| :------------- | :----------------------- | :----------------------------------------------------------- |
+| datname        | name                     | Name of the database                                         |
+| numbackends    | bigint                   | Number of backends currently connected to this database. This is the only column in this view that returns a value reflecting the current state; all other columns return the accumulated values since the last reset. |
+| xact_commit    | numeric                  | Number of transactions in this database that have been committed |
+| xact_rollback  | numeric                  | Number of transactions in this database that have been rolled back |
+| blks_read      | numeric                  | Number of disk blocks read in this database                  |
+| blks_hit       | numeric                  | Number of times disk blocks were found in the buffer cache (unnecessary as the number includes only hits in the MogDB buffer cache) |
+| tup_returned   | numeric                  | Number of rows returned by queries in this database          |
+| tup_fetched    | numeric                  | Number of rows fetched by queries in this database           |
+| tup_inserted   | bigint                   | Number of rows inserted by queries in this database          |
+| tup_updated    | bigint                   | Number of rows updated by queries in this database           |
+| tup_deleted    | bigint                   | Number of rows deleted by queries in this database           |
+| conflicts      | bigint                   | Number of queries canceled due to database recovery conflicts (conflicts occurring only on the standby server). For details, see STAT_DATABASE_CONFLICTS. |
+| temp_files     | numeric                  | Number of temporary files created by queries in this database. All temporary files are counted, regardless of why the temporary file was created (for example, sorting or hashing), and regardless of the **log_temp_files** setting. |
+| temp_bytes     | numeric                  | Total amount of data written to temporary files by queries in this database. All temporary files are counted, regardless of why the temporary file was created, and regardless of the **log_temp_files** setting. |
+| deadlocks      | bigint                   | Number of deadlocks detected in this database                |
+| blk_read_time  | double precision         | Time spent reading data file blocks by backends in this database (unit: ms) |
+| blk_write_time | double precision         | Time spent writing into data file blocks by backends in this database (unit: ms) |
+| stats_reset    | timestamp with time zone | Time at which the current statistics were reset              |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_DATABASE_CONFLICTS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_DATABASE_CONFLICTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..1944f2ed294d931a0619b42284904e9c6885ae0d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_DATABASE_CONFLICTS.md
@@ -0,0 +1,21 @@
+---
+title: SUMMARY_STAT_DATABASE_CONFLICTS
+summary: SUMMARY_STAT_DATABASE_CONFLICTS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STAT_DATABASE_CONFLICTS
+
+**SUMMARY_STAT_DATABASE_CONFLICTS** displays statistics about database conflicts in MogDB.
+
+**Table 1** SUMMARY_STAT_DATABASE_CONFLICTS columns
+
+| **Name**         | **Type** | **Description**                   |
+| :--------------- | :------- | :-------------------------------- |
+| datname          | name     | Database name                     |
+| confl_tablespace | bigint   | Number of conflicting tablespaces |
+| confl_lock       | bigint   | Number of conflicting locks       |
+| confl_snapshot   | bigint   | Number of conflicting snapshots   |
+| confl_bufferpin  | bigint   | Number of conflicting buffers     |
+| confl_deadlock   | bigint   | Number of conflicting deadlocks   |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_SYS_INDEXES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_SYS_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..66961f0c2013563a16859a549279852a30afed7f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_SYS_INDEXES.md
@@ -0,0 +1,21 @@
+---
+title: SUMMARY_STAT_SYS_INDEXES
+summary: SUMMARY_STAT_SYS_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STAT_SYS_INDEXES
+
+**SUMMARY_STAT_SYS_INDEXES** displays index status information about all the system catalogs in the **pg_catalog**, **information_schema**, and **pg_toast** schemas in MogDB.
+
+**Table 1** SUMMARY_STAT_SYS_INDEXES columns
+
+| **Name**      | **Type** | **Description**                                              |
+| :------------ | :------- | :----------------------------------------------------------- |
+| schemaname    | name     | Name of the schema that the index is in                      |
+| relname       | name     | Name of the table for the index                              |
+| indexrelname  | name     | Index name                                                   |
+| idx_scan      | numeric  | Number of index scans initiated on the index                 |
+| idx_tup_read  | numeric  | Number of index entries returned by scans on the index       |
+| idx_tup_fetch | numeric  | Number of live table rows fetched by simple index scans using the index |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_SYS_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_SYS_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..7d21bcff73b3d9c5e935e229e1e4d976489f96e1
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_SYS_TABLES.md
@@ -0,0 +1,35 @@
+---
+title: SUMMARY_STAT_SYS_TABLES
+summary: SUMMARY_STAT_SYS_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STAT_SYS_TABLES
+
+**SUMMARY_STAT_SYS_TABLES** displays statistics about the system catalogs of all the namespaces in **pg_catalog** and **information_schema** schemas in MogDB.
+
+**Table 1** SUMMARY_STAT_SYS_TABLES columns
+
+| **Name**          | **Type**                 | **Description**                                              |
+| :---------------- | :----------------------- | :----------------------------------------------------------- |
+| schemaname        | name                     | Name of the schema that contains the table                   |
+| relname           | name                     | Table name                                                   |
+| seq_scan          | numeric                  | Number of sequential scans initiated on this table           |
+| seq_tup_read      | numeric                  | Number of live rows fetched by sequential scans              |
+| idx_scan          | numeric                  | Number of index scans initiated on the table                 |
+| idx_tup_fetch     | numeric                  | Number of live rows fetched by index scans                   |
+| n_tup_ins         | numeric                  | Number of rows inserted                                      |
+| n_tup_upd         | numeric                  | Number of rows updated                                       |
+| n_tup_del         | numeric                  | Number of rows deleted                                       |
+| n_tup_hot_upd     | numeric                  | Number of rows HOT updated (with no separate index update required) |
+| n_live_tup        | numeric                  | Estimated number of live rows                                |
+| n_dead_tup        | numeric                  | Estimated number of dead rows                                |
+| last_vacuum       | timestamp with time zone | Last time at which this table was manually vacuumed (not counting **VACUUM FULL**) |
+| last_autovacuum   | timestamp with time zone | Last time at which this table was vacuumed by the autovacuum daemon |
+| last_analyze      | timestamp with time zone | Last time at which this table was manually analyzed          |
+| last_autoanalyze  | timestamp with time zone | Last time at which this table was analyzed by the autovacuum daemon |
+| vacuum_count      | numeric                  | Number of times the table has been manually vacuumed (not counting **VACUUM FULL**) |
+| autovacuum_count  | numeric                  | Number of times the table has been vacuumed by the autovacuum daemon |
+| analyze_count     | numeric                  | Number of times the table has been manually analyzed         |
+| autoanalyze_count | numeric                  | Number of times the table has been analyzed by the autovacuum daemon |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_USER_FUNCTIONS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_USER_FUNCTIONS.md
new file mode 100644
index 0000000000000000000000000000000000000000..af40e24cd9e3ccaa9a057b4f3189a0451d6b6e9f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_USER_FUNCTIONS.md
@@ -0,0 +1,20 @@
+---
+title: SUMMARY_STAT_USER_FUNCTIONS
+summary: SUMMARY_STAT_USER_FUNCTIONS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STAT_USER_FUNCTIONS
+
+**SUMMARY_STAT_USER_FUNCTIONS** displays statistics about user-defined views on all database nodes.
+
+**Table 1** SUMMARY_STAT_USER_FUNCTIONS columns
+
+| **Name**   | **Type**         | **Description**                                              |
+| :--------- | :--------------- | :----------------------------------------------------------- |
+| schemaname | name             | Schema name                                                  |
+| funcname   | name             | Function name                                                |
+| calls      | numeric          | Number of times that the function has been called            |
+| total_time | double precision | Total time spent in this function and all other functions called by it (unit: ms) |
+| self_time  | double precision | Total time spent in this function, excluding other functions called by it (unit: ms) |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_USER_INDEXES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_USER_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..25d0b58b5e440e1b3a6cd32bd51e9f594150d39d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_USER_INDEXES.md
@@ -0,0 +1,21 @@
+---
+title: SUMMARY_STAT_USER_INDEXES
+summary: SUMMARY_STAT_USER_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STAT_USER_INDEXES
+
+**SUMMARY_STAT_USER_INDEXES** displays the status information about the index of user-defined ordinary tables in all databases in MogDB.
+
+**Table 1** SUMMARY_STAT_USER_INDEXES columns
+
+| **Name**      | **Type** | **Description**                                              |
+| :------------ | :------- | :----------------------------------------------------------- |
+| schemaname    | name     | Name of the schema that the index is in                      |
+| relname       | name     | Name of the table for the index                              |
+| indexrelname  | name     | Index name                                                   |
+| idx_scan      | numeric  | Number of index scans initiated on the index                 |
+| idx_tup_read  | numeric  | Number of index entries returned by scans on the index       |
+| idx_tup_fetch | numeric  | Number of live table rows fetched by simple index scans using the index |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_USER_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_USER_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..c12e3d41447c75d44dbe5b201e79c7adf8ba116a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_USER_TABLES.md
@@ -0,0 +1,35 @@
+---
+title: SUMMARY_STAT_USER_TABLES
+summary: SUMMARY_STAT_USER_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STAT_USER_TABLES
+
+**SUMMARY_STAT_USER_TABLES** displays the status information about user-defined ordinary tables in all namespaces in MogDB.
+
+**Table 1** SUMMARY_STAT_USER_TABLES columns
+
+| **Name**          | **Type**                 | **Description**                                              |
+| :---------------- | :----------------------- | :----------------------------------------------------------- |
+| schemaname        | name                     | Name of the schema that contains the table                   |
+| relname           | name                     | Table name                                                   |
+| seq_scan          | numeric                  | Number of sequential scans initiated on this table           |
+| seq_tup_read      | numeric                  | Number of live rows fetched by sequential scans              |
+| idx_scan          | numeric                  | Number of index scans initiated on the table                 |
+| idx_tup_fetch     | numeric                  | Number of live rows fetched by index scans                   |
+| n_tup_ins         | numeric                  | Number of rows inserted                                      |
+| n_tup_upd         | numeric                  | Number of rows updated                                       |
+| n_tup_del         | numeric                  | Number of rows deleted                                       |
+| n_tup_hot_upd     | numeric                  | Number of rows HOT updated (with no separate index update required) |
+| n_live_tup        | numeric                  | Estimated number of live rows                                |
+| n_dead_tup        | numeric                  | Estimated number of dead rows                                |
+| last_vacuum       | timestamp with time zone | Last time at which this table was manually vacuumed (not counting **VACUUM FULL**) |
+| last_autovacuum   | timestamp with time zone | Last time at which this table was vacuumed by the autovacuum daemon |
+| last_analyze      | timestamp with time zone | Last time at which this table was manually analyzed          |
+| last_autoanalyze  | timestamp with time zone | Last time at which this table was analyzed by the autovacuum daemon |
+| vacuum_count      | numeric                  | Number of times the table has been manually vacuumed (not counting **VACUUM FULL**) |
+| autovacuum_count  | numeric                  | Number of times the table has been vacuumed by the autovacuum daemon |
+| analyze_count     | numeric                  | Number of times the table has been manually analyzed         |
+| autoanalyze_count | numeric                  | Number of times the table has been analyzed by the autovacuum daemon |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_ALL_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_ALL_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..5b8a608fe6486153bde966bbb41f89ecf4b79d3f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_ALL_TABLES.md
@@ -0,0 +1,25 @@
+---
+title: SUMMARY_STAT_XACT_ALL_TABLES
+summary: SUMMARY_STAT_XACT_ALL_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STAT_XACT_ALL_TABLES
+
+**SUMMARY_STAT_XACT_ALL_TABLES** displays transaction status information about all ordinary tables and TOAST tables in all namespaces in MogDB.
+
+**Table 1** SUMMARY_STAT_XACT_ALL_TABLES columns
+
+| **Name**      | **Type** | **Description**                                              |
+| :------------ | :------- | :----------------------------------------------------------- |
+| schemaname    | name     | Name of the schema that contains the table                   |
+| relname       | name     | Table name                                                   |
+| seq_scan      | numeric  | Number of sequential scans initiated on this table           |
+| seq_tup_read  | numeric  | Number of live rows fetched by sequential scans              |
+| idx_scan      | numeric  | Number of index scans initiated on the table                 |
+| idx_tup_fetch | numeric  | Number of live rows fetched by index scans                   |
+| n_tup_ins     | numeric  | Number of rows inserted                                      |
+| n_tup_upd     | numeric  | Number of rows updated                                       |
+| n_tup_del     | numeric  | Number of rows deleted                                       |
+| n_tup_hot_upd | numeric  | Number of rows HOT updated (with no separate index update required) |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_SYS_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_SYS_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..6fe9ff7fda17eff80fcf929e9d2ff3c49406241e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_SYS_TABLES.md
@@ -0,0 +1,25 @@
+---
+title: SUMMARY_STAT_XACT_SYS_TABLES
+summary: SUMMARY_STAT_XACT_SYS_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STAT_XACT_SYS_TABLES
+
+**SUMMARY_STAT_XACT_SYS_TABLES** displays transaction status information about the system catalogs in namespaces in MogDB.
+
+**Table 1** SUMMARY_STAT_XACT_SYS_TABLES columns
+
+| **Name**      | **Type** | **Description**                                              |
+| :------------ | :------- | :----------------------------------------------------------- |
+| schemaname    | name     | Name of the schema that contains the table                   |
+| relname       | name     | Table name                                                   |
+| seq_scan      | numeric  | Number of sequential scans initiated on this table           |
+| seq_tup_read  | numeric  | Number of live rows fetched by sequential scans              |
+| idx_scan      | numeric  | Number of index scans initiated on the table                 |
+| idx_tup_fetch | numeric  | Number of live rows fetched by index scans                   |
+| n_tup_ins     | numeric  | Number of rows inserted                                      |
+| n_tup_upd     | numeric  | Number of rows updated                                       |
+| n_tup_del     | numeric  | Number of rows deleted                                       |
+| n_tup_hot_upd | numeric  | Number of rows HOT updated (with no separate index update required) |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_USER_FUNCTIONS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_USER_FUNCTIONS.md
new file mode 100644
index 0000000000000000000000000000000000000000..4239751eff25c193a2ae02b6a4c6a15d4b6cf08a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_USER_FUNCTIONS.md
@@ -0,0 +1,20 @@
+---
+title: SUMMARY_STAT_XACT_USER_FUNCTIONS
+summary: SUMMARY_STAT_XACT_USER_FUNCTIONS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STAT_XACT_USER_FUNCTIONS
+
+**SUMMARY_STAT_XACT_USER_FUNCTIONS** displays statistics about function executions in transactions in MogDB.
+
+**Table 1** SUMMARY_STAT_XACT_USER_FUNCTIONS columns
+
+| **Name**   | **Type**         | **Description**                                              |
+| :--------- | :--------------- | :----------------------------------------------------------- |
+| schemaname | name             | Schema name                                                  |
+| funcname   | name             | Function name                                                |
+| calls      | numeric          | Number of times that the function has been called            |
+| total_time | double precision | Total time spent in the function and all other functions called by it |
+| self_time  | double precision | Total time spent in the function itself, excluding other functions called by it |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_USER_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_USER_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..8c939fe3c01d41e946c7db28f6d60f9eb5b1929e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_USER_TABLES.md
@@ -0,0 +1,25 @@
+---
+title: SUMMARY_STAT_XACT_USER_TABLES
+summary: SUMMARY_STAT_XACT_USER_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STAT_XACT_USER_TABLES
+
+**SUMMARY_STAT_XACT_USER_TABLES** displays transaction status information about the user tables in namespaces in the cluster.
+
+**Table 1** SUMMARY_STAT_XACT_USER_TABLES columns
+
+| **Name**      | **Type** | **Description**                                              |
+| :------------ | :------- | :----------------------------------------------------------- |
+| schemaname    | name     | Name of the schema that contains the table                   |
+| relname       | name     | Table name                                                   |
+| seq_scan      | numeric  | Number of sequential scans initiated on this table           |
+| seq_tup_read  | numeric  | Number of live rows fetched by sequential scans              |
+| idx_scan      | numeric  | Number of index scans initiated on the table                 |
+| idx_tup_fetch | numeric  | Number of live rows fetched by index scans                   |
+| n_tup_ins     | numeric  | Number of rows inserted                                      |
+| n_tup_upd     | numeric  | Number of rows updated                                       |
+| n_tup_del     | numeric  | Number of rows deleted                                       |
+| n_tup_hot_upd | numeric  | Number of rows HOT updated (with no separate index update required) |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/GLOBAL_OPERATOR_HISTORY.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/GLOBAL_OPERATOR_HISTORY.md
new file mode 100644
index 0000000000000000000000000000000000000000..dea0467fa2724d8cac16ae6ee703071015d69424
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/GLOBAL_OPERATOR_HISTORY.md
@@ -0,0 +1,37 @@
+---
+title: GLOBAL_OPERATOR_HISTORY
+summary: GLOBAL_OPERATOR_HISTORY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_OPERATOR_HISTORY
+
+**GLOBAL_OPERATOR_HISTORY** displays records of operators in jobs that have been executed by the current user on the primary database node.
+
+**Table 1** GLOBAL_OPERATOR_HISTORY columns<a id="GLOBAL_OPERATOR_HISTORY columns"> </a>
+
+| Name                | Type                     | Description                                                  |
+| :------------------ | :----------------------- | :----------------------------------------------------------- |
+| queryid             | bigint                   | Internal query ID used for statement execution               |
+| pid                 | bigint                   | Thread ID of the backend                                     |
+| plan_node_id        | integer                  | Plan node ID of the execution plan                           |
+| plan_node_name      | text                     | Name of the operator corresponding to the plan node ID       |
+| start_time          | timestamp with time zone | Time when the operator starts to process the first data record |
+| duration            | bigint                   | Total execution time of the operator (unit: ms)              |
+| query_dop           | integer                  | DOP of the operator                                          |
+| estimated_rows      | bigint                   | Number of rows estimated by the optimizer                    |
+| tuple_processed     | bigint                   | Number of elements returned by the operator                  |
+| min_peak_memory     | integer                  | Minimum peak memory used by the operator on database nodes (unit: MB) |
+| max_peak_memory     | integer                  | Maximum peak memory used by the operator on database nodes (unit: MB) |
+| average_peak_memory | integer                  | Average peak memory used by the operator on database nodes (unit: MB) |
+| memory_skew_percent | integer                  | Memory usage skew of the operator among database nodes       |
+| min_spill_size      | integer                  | Minimum spilled data among database nodes when a spill occurs (unit: MB) (default value:**0**) |
+| max_spill_size      | integer                  | Maximum spilled data among database nodes when a spill occurs (unit: MB) (default value:**0**) |
+| average_spill_size  | integer                  | Average spilled data among database nodes when a spill occurs (unit: MB) (default value:**0**) |
+| spill_skew_percent  | integer                  | Database node spill skew when a spill occurs                 |
+| min_cpu_time        | bigint                   | Minimum execution time of the operator on database nodes (unit: ms) |
+| max_cpu_time        | bigint                   | Maximum execution time of the operator on database nodes (unit: ms) |
+| total_cpu_time      | bigint                   | Total execution time of the operator on database nodes (unit: ms) |
+| cpu_skew_percent    | integer                  | Execution time skew among database nodes                     |
+| warning             | text                     | Warning. The following warnings are displayed:<br/>- Sort/SetOp/HashAgg/HashJoin spill<br/>- Spill file size large than 256MB<br/>- Broadcast size large than 100MB<br/>- Early spill<br/>- Spill times is greater than 3<br/>- Spill on memory adaptive<br/>- Hash table conflict |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/GLOBAL_OPERATOR_HISTORY_TABLE.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/GLOBAL_OPERATOR_HISTORY_TABLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..6d3bb817ffde9bf567d78828f81c1c6ff852e88c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/GLOBAL_OPERATOR_HISTORY_TABLE.md
@@ -0,0 +1,10 @@
+---
+title: GLOBAL_OPERATOR_HISTORY_TABLE
+summary: GLOBAL_OPERATOR_HISTORY_TABLE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_OPERATOR_HISTORY_TABLE
+
+**GLOBAL_OPERATOR_HISTORY_TABLE** displays the records about operators of completed jobs on the primary database node. Data is dumped from the kernel to the system catalog **GS_WLM_OPERATOR_INFO**. **GLOBAL_OPERATOR_HISTORY_TABLE** is a collection view for querying the system catalog **GS_WLM_OPERATOR_INFO** on the primary database node. Columns in this view are the same as those in **[GLOBAL_OPERATOR_HISTORY -> Table 1](GLOBAL_OPERATOR_HISTORY)**.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/GLOBAL_OPERATOR_RUNTIME.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/GLOBAL_OPERATOR_RUNTIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..995149166d3a7c54cd205b06d878ec2503d1997c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/GLOBAL_OPERATOR_RUNTIME.md
@@ -0,0 +1,38 @@
+---
+title: GLOBAL_OPERATOR_RUNTIME
+summary: GLOBAL_OPERATOR_RUNTIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_OPERATOR_RUNTIME
+
+**GLOBAL_OPERATOR_RUNTIME** displays information about operators of the jobs that are being executed by the current user on the primary database node.
+
+**Table 1** GLOBAL_OPERATOR_RUNTIME columns
+
+| Name                | Type                     | Description                                                  |
+| :------------------ | :----------------------- | :----------------------------------------------------------- |
+| queryid             | bigint                   | Internal query ID used for statement execution               |
+| pid                 | bigint                   | Thread ID of the backend                                     |
+| plan_node_id        | integer                  | Plan node ID of the execution plan                           |
+| plan_node_name      | text                     | Name of the operator corresponding to the plan node ID       |
+| start_time          | timestamp with time zone | Time when the operator starts to process the first data record |
+| duration            | bigint                   | Total execution time of the operator (unit: ms)              |
+| status              | text                     | Execution status of the current operator, which can be **finished** or **running**. |
+| query_dop           | integer                  | DOP of the operator                                          |
+| estimated_rows      | bigint                   | Number of rows estimated by the optimizer                    |
+| tuple_processed     | bigint                   | Number of elements returned by the operator                  |
+| min_peak_memory     | integer                  | Minimum peak memory used by the operator on database nodes (unit: MB) |
+| max_peak_memory     | integer                  | Maximum peak memory used by the operator on database nodes (unit: MB) |
+| average_peak_memory | integer                  | Average peak memory used by the operator on database nodes (unit: MB) |
+| memory_skew_percent | integer                  | Memory usage skew of the operator among database nodes       |
+| min_spill_size      | integer                  | Minimum spilled data among database nodes when a spill occurs (unit: MB) (default value:**0**) |
+| max_spill_size      | integer                  | Maximum spilled data among database nodes when a spill occurs (unit: MB) (default value:**0**) |
+| average_spill_size  | integer                  | Average spilled data among database nodes when a spill occurs (unit: MB) (default value:**0**) |
+| spill_skew_percent  | integer                  | Database node spill skew when a spill occurs                 |
+| min_cpu_time        | bigint                   | Minimum execution time of the operator on database nodes (unit: ms) |
+| max_cpu_time        | bigint                   | Maximum execution time of the operator on database nodes (unit: ms) |
+| total_cpu_time      | bigint                   | Total execution time of the operator on database nodes (unit: ms) |
+| cpu_skew_percent    | integer                  | Execution time skew among database nodes                     |
+| warning             | text                     | Warning. The following warnings are displayed:<br/>- Sort/SetOp/HashAgg/HashJoin spill<br/>- Spill file size large than 256MB<br/>- Broadcast size large than 100MB<br/>- Early spill<br/>- Spill times is greater than 3<br/>- Spill on memory adaptive<br/>- Hash table conflict |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/OPERATOR_HISTORY.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/OPERATOR_HISTORY.md
new file mode 100644
index 0000000000000000000000000000000000000000..ae4b61c667b147412a4bb0232089d946514285d0
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/OPERATOR_HISTORY.md
@@ -0,0 +1,10 @@
+---
+title: OPERATOR_HISTORY
+summary: OPERATOR_HISTORY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# OPERATOR_HISTORY
+
+**OPERATOR_HISTORY** displays records of operators in jobs that have been executed by the current user on the current primary database node. Columns in this view are the same as those in **[Appendices-Table 6](table-6)**.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/OPERATOR_HISTORY_TABLE.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/OPERATOR_HISTORY_TABLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..6239febd9d5a51795580f8ae4b6c62ff4bae5a43
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/OPERATOR_HISTORY_TABLE.md
@@ -0,0 +1,37 @@
+---
+title: OPERATOR_HISTORY_TABLE
+summary: OPERATOR_HISTORY_TABLE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# OPERATOR_HISTORY_TABLE
+
+**OPERATOR_HISTORY_TABLE** displays records about operators of completed jobs. Data is dumped from the kernel to this system catalog.
+
+**Table 1** OPERATOR_HISTORY_TABLE columns
+
+| Name                | Type                     | Description                                                  |
+| :------------------ | :----------------------- | :----------------------------------------------------------- |
+| queryid             | bigint                   | Internal query ID used for statement execution               |
+| pid                 | bigint                   | Thread ID of the backend                                     |
+| plan_node_id        | integer                  | Plan node ID of the execution plan                           |
+| plan_node_name      | text                     | Name of the operator corresponding to the plan node ID       |
+| start_time          | timestamp with time zone | Time when an operator starts to process the first data record |
+| duration            | bigint                   | Total execution time of the operator, in ms                  |
+| query_dop           | integer                  | DOP of the operator                                          |
+| estimated_rows      | bigint                   | Number of rows estimated by the optimizer                    |
+| tuple_processed     | bigint                   | Number of elements returned by the operator                  |
+| min_peak_memory     | integer                  | Minimum peak memory used by the operator on database nodes (unit: MB) |
+| max_peak_memory     | integer                  | Maximum peak memory used by the operator on database nodes (unit: MB) |
+| average_peak_memory | integer                  | Average peak memory used by the operator on database nodes (unit: MB) |
+| memory_skew_percent | integer                  | Memory usage skew of the operator among database nodes       |
+| min_spill_size      | integer                  | Minimum spilled data among database nodes when a spill occurs (unit: MB) (default value:**0**) |
+| max_spill_size      | integer                  | Maximum spilled data among database nodes when a spill occurs (unit: MB) (default value:**0**) |
+| average_spill_size  | integer                  | Average spilled data among database nodes when a spill occurs (unit: MB) (default value:**0**) |
+| spill_skew_percent  | integer                  | Database node spill skew when a spill occurs                 |
+| min_cpu_time        | bigint                   | Minimum execution time of the operator on database nodes (unit: ms) |
+| max_cpu_time        | bigint                   | Maximum execution time of the operator on database nodes (unit: ms) |
+| total_cpu_time      | bigint                   | Total execution time of the operator on database nodes (unit: ms) |
+| cpu_skew_percent    | integer                  | Execution time skew among database nodes                     |
+| warning             | text                     | Warning. The following warnings are displayed:<br/>- Sort/SetOp/HashAgg/HashJoin spill<br/>- Spill file size large than 256MB<br/>- Broadcast size large than 100MB<br/>- Early spill<br/>- Spill times is greater than 3<br/>- Spill on memory adaptive<br/>- Hash table conflict |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/OPERATOR_RUNTIME.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/OPERATOR_RUNTIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..78a919fb05c6e26e481b058dcd1a4b0b3ab14769
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/OPERATOR_RUNTIME.md
@@ -0,0 +1,38 @@
+---
+title: OPERATOR_RUNTIME
+summary: OPERATOR_RUNTIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# OPERATOR_RUNTIME
+
+**OPERATOR_RUNTIME** displays information about operators of the jobs that are being executed by the current user.
+
+**Table 1** OPERATOR_RUNTIME columns
+
+| Name                | Type                     | Description                                                  |
+| :------------------ | :----------------------- | :----------------------------------------------------------- |
+| queryid             | bigint                   | Internal query ID used for statement execution               |
+| pid                 | bigint                   | Thread ID of the backend                                     |
+| plan_node_id        | integer                  | Plan node ID of the execution plan of a query                |
+| plan_node_name      | text                     | Name of the operator corresponding to the plan node ID       |
+| start_time          | timestamp with time zone | Time when the operator starts to process the first data record |
+| duration            | bigint                   | Total execution time of the operator (unit: ms)              |
+| status              | text                     | Execution status of the current operator, which can be **finished** or **running**. |
+| query_dop           | integer                  | DOP of the operator                                          |
+| estimated_rows      | bigint                   | Number of rows estimated by the optimizer                    |
+| tuple_processed     | bigint                   | Number of elements returned by the operator                  |
+| min_peak_memory     | integer                  | Minimum peak memory used by the operator on database nodes (unit: MB) |
+| max_peak_memory     | integer                  | Maximum peak memory used by the operator on database nodes (unit: MB) |
+| average_peak_memory | integer                  | Average peak memory used by the operator on database nodes (unit: MB) |
+| memory_skew_percent | integer                  | Memory usage skew of the operator among database nodes       |
+| min_spill_size      | integer                  | Minimum spilled data among database nodes when a spill occurs (unit: MB) (default value:**0**) |
+| max_spill_size      | integer                  | Maximum spilled data among database nodes when a spill occurs (unit: MB) (default value:**0**) |
+| average_spill_size  | integer                  | Average spilled data among database nodes when a spill occurs (unit: MB) (default value:**0**) |
+| spill_skew_percent  | integer                  | Database node spill skew when a spill occurs                 |
+| min_cpu_time        | bigint                   | Minimum execution time of the operator on database nodes (unit: ms) |
+| max_cpu_time        | bigint                   | Maximum execution time of the operator on database nodes (unit: ms) |
+| total_cpu_time      | bigint                   | Total execution time of the operator on database nodes (unit: ms) |
+| cpu_skew_percent    | integer                  | Execution time skew among database nodes                     |
+| warning             | text                     | Warning. The following warnings are displayed:<br/>- Sort/SetOp/HashAgg/HashJoin spill<br/>- Spill file size large than 256MB<br/>- Broadcast size large than 100MB<br/>- Early spill<br/>- Spill times is greater than 3<br/>- Spill on memory adaptive<br/>- Hash table conflict |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/os/GLOBAL_OS_RUNTIME.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/os/GLOBAL_OS_RUNTIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..7f6c0f2fffb43c430134b84eb862a885b503be81
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/os/GLOBAL_OS_RUNTIME.md
@@ -0,0 +1,21 @@
+---
+title: GLOBAL_OS_RUNTIME
+summary: GLOBAL_OS_RUNTIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_OS_RUNTIME
+
+**GLOBAL_OS_RUNTIME** provides OS running status information about all normal nodes in MogDB.
+
+**Table 1** GLOBAL_OS_RUNTIME columns
+
+| **Name**   | **Type** | **Description**                                          |
+| :--------- | :------- | :------------------------------------------------------- |
+| node_name  | name     | Node name                                                |
+| id         | integer  | ID                                                       |
+| name       | text     | Name of the OS running status                            |
+| value      | numeric  | Value of the OS running status                           |
+| comments   | text     | Remarks of the OS running status                         |
+| cumulative | boolean  | Whether the value of the OS running status is cumulative |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/os/GLOBAL_OS_THREADS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/os/GLOBAL_OS_THREADS.md
new file mode 100644
index 0000000000000000000000000000000000000000..59d5779444257eb0b35683d7e9ea5a88352655bb
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/os/GLOBAL_OS_THREADS.md
@@ -0,0 +1,20 @@
+---
+title: GLOBAL_OS_THREADS
+summary: GLOBAL_OS_THREADS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_OS_THREADS
+
+**GLOBAL_OS_THREADS** provides status information about threads on all normal nodes in MogDB.
+
+**Table 1** GLOBAL_OS_THREADS columns
+
+| **Name**      | **Type**                 | **Description**                                         |
+| :------------ | :----------------------- | :------------------------------------------------------ |
+| node_name     | text                     | Node name                                               |
+| pid           | bigint                   | ID of the thread running under the current node process |
+| lwpid         | integer                  | Lightweight thread ID corresponding to **pid**          |
+| thread_name   | text                     | Name of the thread corresponding to **pid**             |
+| creation_time | timestamp with time zone | Creation time of the thread corresponding to **pid**    |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/os/OS_RUNTIME.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/os/OS_RUNTIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..0257e212e6f3b3bdc661e3d55c19ffc07d84b4c7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/os/OS_RUNTIME.md
@@ -0,0 +1,20 @@
+---
+title: OS_RUNTIME
+summary: OS_RUNTIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# OS_RUNTIME
+
+**OS_RUNTIME** displays the running status of the current OS.
+
+**Table 1** OS_RUNTIME columns
+
+| Name       | Type    | Description                                              |
+| :--------- | :------ | :------------------------------------------------------- |
+| id         | integer | ID                                                       |
+| name       | text    | Name of the OS running status                            |
+| value      | numeric | Value of the OS running status                           |
+| comments   | text    | Remarks of the OS running status                         |
+| cumulative | boolean | Whether the value of the OS running status is cumulative |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/os/OS_THREADS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/os/OS_THREADS.md
new file mode 100644
index 0000000000000000000000000000000000000000..9adb12e14bb1ab91060cfb853b88e87781ad1ddc
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/os/OS_THREADS.md
@@ -0,0 +1,20 @@
+---
+title: OS_THREADS
+summary: OS_THREADS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# OS_THREADS
+
+**OS_THREADS** provides status information about all threads on the current node.
+
+**Table 1** OS_THREADS columns
+
+| **Name**      | **Type**                 | **Description**                                             |
+| :------------ | :----------------------- | :---------------------------------------------------------- |
+| node_name     | text                     | Database process name                                       |
+| pid           | bigint                   | ID of the thread running under the current database process |
+| lwpid         | integer                  | Lightweight thread ID corresponding to **pid**              |
+| thread_name   | text                     | Name of the thread corresponding to **pid**                 |
+| creation_time | timestamp with time zone | Creation time of the thread corresponding to **pid**        |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COMPLEX_HISTORY.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COMPLEX_HISTORY.md
new file mode 100644
index 0000000000000000000000000000000000000000..df2b3805a500631370e8fd8b8590e6eab4250dc4
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COMPLEX_HISTORY.md
@@ -0,0 +1,83 @@
+---
+title: GLOBAL_STATEMENT_COMPLEX_HISTORY
+summary: GLOBAL_STATEMENT_COMPLEX_HISTORY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STATEMENT_COMPLEX_HISTORY
+
+**GLOBAL_STATEMENT_COMPLEX_HISTORY** displays load management records after jobs are executed on each node.
+
+**Table 1** GLOBAL_STATEMENT_COMPLEX_HISTORY columns
+
+| Name                | Type                     | Description                                                  |
+| :------------------ | :----------------------- | :----------------------------------------------------------- |
+| datid               | oid                      | OID of the database that the backend is connected to         |
+| dbname              | text                     | Name of the database that the backend is connected to        |
+| schemaname          | text                     | Schema name                                                  |
+| nodename            | text                     | Node name                                                    |
+| username            | text                     | Username used for connecting to the backend                  |
+| application_name    | text                     | Name of the application connected to the backend             |
+| client_addr         | inet                     | IP address of the client connected to the backend. If this column is null, it indicates either the client is connected via a Unix socket on the server or this is an internal process, such as autovacuum. |
+| client_hostname     | text                     | Host name of the connected client, as reported by a reverse DNS lookup of **client\_addr**. This column will be non-null only for IP connections and only when **log_hostname** is enabled. |
+| client_port         | integer                  | TCP port number that the client uses for communication with this backend (**-1** if a Unix socket is used) |
+| query_band          | text                     | Job type, which is specified by the GUC parameter **query_band**. The default value is a null string. |
+| block_time          | bigint                   | Duration that the statement is blocked before being executed, including the statement parsing and optimization duration (unit: ms) |
+| start_time          | timestamp with time zone | Time when the statement starts to be executed                |
+| finish_time         | timestamp with time zone | Time when the statement execution ends                       |
+| duration            | bigint                   | Execution time of the statement (unit: ms)                   |
+| estimate_total_time | bigint                   | Estimated execution time of the statement (unit: ms)         |
+| status              | text                     | Final statement execution status, which can be **finished** (normal) or **aborted** (abnormal). |
+| abort_info          | text                     | Exception information displayed if the final statement execution status is **aborted** |
+| resource_pool       | text                     | Resource pool used by the user                               |
+| control_group       | text                     | Cgroup used by the statement                                 |
+| estimate_memory     | integer                  | Estimated memory used by the statement (unit: MB)            |
+| min_peak_memory     | integer                  | Minimum memory peak of the statement across the database nodes (unit: MB) |
+| max_peak_memory     | integer                  | Maximum memory peak of the statement across the database nodes (unit: MB) |
+| average_peak_memory | integer                  | Average memory usage during statement execution (unit: MB)   |
+| memory_skew_percent | integer                  | Memory usage skew of the statement among the database nodes  |
+| spill_info          | text                     | Information about statement spill to the database nodes<br/>- **None**: The statement has not been spilled to disks on the database nodes.<br/>- **All**: The statement has been spilled to disks on the database nodes.<br/>- **[a:b]**: The statement has been spilled to disks on **a** of **b** database nodes. |
+| min_spill_size      | integer                  | Minimum spilled data among database nodes when a spill occurs (unit: MB) (default value:**0**) |
+| max_spill_size      | integer                  | Maximum spilled data among database nodes when a spill occurs (unit: MB) (default value:**0**) |
+| average_spill_size  | integer                  | Average spilled data among database nodes when a spill occurs (unit: MB) (default value:**0**) |
+| spill_skew_percent  | integer                  | Database node spill skew when a spill occurs                 |
+| min_dn_time         | bigint                   | Minimum execution time of the statement across the database nodes (unit: ms) |
+| max_dn_time         | bigint                   | Maximum execution time of the statement across the database nodes (unit: ms) |
+| average_dn_time     | bigint                   | Average execution time of the statement across the database nodes (unit: ms) |
+| dntime_skew_percent | integer                  | Execution time skew of the statement among the database nodes |
+| min_cpu_time        | bigint                   | Minimum CPU time of the statement across the database nodes (unit: ms) |
+| max_cpu_time        | bigint                   | Maximum CPU time of the statement across the database nodes (unit: ms) |
+| total_cpu_time      | bigint                   | Total CPU time of the statement across the database nodes (unit: ms) |
+| cpu_skew_percent    | integer                  | CPU time skew of the statement among the database nodes      |
+| min_peak_iops       | integer                  | Minimum IOPS peak of the statement across the database nodes. It is counted by ones in a column-store table and by ten thousands in a row-store table. |
+| max_peak_iops       | integer                  | Maximum IOPS peak of the statement across the database nodes. It is counted by ones in a column-store table and by ten thousands in a row-store table. |
+| average_peak_iops   | integer                  | Average IOPS peak of the statement across the database nodes. It is counted by ones in a column-store table and by ten thousands in a row-store table. |
+| iops_skew_percent   | integer                  | I/O skew of the statement among the database nodes           |
+| warning             | text                     | Warning. The following warnings are displayed:<br/>- Spill file size large than 256MB<br/>- Broadcast size large than 100MB<br/>- Early spill<br/>- Spill times is greater than 3<br/>- Spill on memory adaptive<br/>- Hash table conflict |
+| queryid             | bigint                   | Internal query ID used for statement execution               |
+| query               | text                     | Statement executed                                           |
+| query_plan          | text                     | Execution plan of the statement                              |
+| node_group          | text                     | Logical MogDB of the user running the statement              |
+| cpu_top1_node_name  | text                     | Name of the node with the highest CPU usage                  |
+| cpu_top2_node_name  | text                     | Name of the node with the second highest CPU usage           |
+| cpu_top3_node_name  | text                     | Name of the node with the third highest CPU usage            |
+| cpu_top4_node_name  | text                     | Name of the node with the fourth highest CPU usage           |
+| cpu_top5_node_name  | text                     | Name of the node with the fifth highest CPU usage            |
+| mem_top1_node_name  | text                     | Name of the node with the highest memory usage               |
+| mem_top2_node_name  | text                     | Name of the node with the second highest CPU usage           |
+| mem_top3_node_name  | text                     | Name of the node with the third highest CPU usage            |
+| mem_top4_node_name  | text                     | Name of the node with the fourth highest CPU usage           |
+| mem_top5_node_name  | text                     | Name of the node with the fifth highest CPU usage            |
+| cpu_top1_value      | bigint                   | CPU usage                                                    |
+| cpu_top2_value      | bigint                   | CPU usage                                                    |
+| cpu_top3_value      | bigint                   | CPU usage                                                    |
+| cpu_top4_value      | bigint                   | CPU usage                                                    |
+| cpu_top5_value      | bigint                   | CPU usage                                                    |
+| mem_top1_value      | bigint                   | Memory usage                                                 |
+| mem_top2_value      | bigint                   | Memory usage                                                 |
+| mem_top3_value      | bigint                   | Memory usage                                                 |
+| mem_top4_value      | bigint                   | Memory usage                                                 |
+| mem_top5_value      | bigint                   | Memory usage                                                 |
+| top_mem_dn          | text                     | Top N memory usage                                           |
+| top_cpu_dn          | text                     | Top N CPU usage                                              |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COMPLEX_HISTORY_TABLE.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COMPLEX_HISTORY_TABLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..a55822d5569d0c81c5ca23eebc0c48231dff0054
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COMPLEX_HISTORY_TABLE.md
@@ -0,0 +1,10 @@
+---
+title: GLOBAL_STATEMENT_COMPLEX_HISTORY_TABLE
+summary: GLOBAL_STATEMENT_COMPLEX_HISTORY_TABLE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STATEMENT_COMPLEX_HISTORY_TABLE
+
+**GLOBAL_STATEMENT_COMPLEX_HISTORY_TABLE** displays load management information about completed jobs executed on each node. Data is dumped from the kernel to this system catalog. For details about the columns, see GLOBAL_STATEMENT_COMPLEX_HISTORY.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COMPLEX_RUNTIME.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COMPLEX_RUNTIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..956ed0bf32108031b404901eee5e70f9441b83c6
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COMPLEX_RUNTIME.md
@@ -0,0 +1,63 @@
+---
+title: GLOBAL_STATEMENT_COMPLEX_RUNTIME
+summary: GLOBAL_STATEMENT_COMPLEX_RUNTIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STATEMENT_COMPLEX_RUNTIME
+
+**GLOBAL_STATEMENT_COMPLEX_RUNTIME** displays load management information about jobs being executed by the current user on each node.
+
+**Table 1** GLOBAL_STATEMENT_COMPLEX_RUNTIME columns
+
+| Name                | Type                     | Description                                                  |
+| :------------------ | :----------------------- | :----------------------------------------------------------- |
+| datid               | oid                      | OID of the database that the backend is connected to         |
+| dbname              | name                     | Name of the database that the backend is connected to        |
+| schemaname          | text                     | Schema name                                                  |
+| nodename            | text                     | Node name                                                    |
+| username            | name                     | Username used for connecting to the backend                  |
+| application_name    | text                     | Name of the application connected to the backend             |
+| client_addr         | inet                     | IP address of the client connected to the backend. If this column is null, it indicates either the client is connected via a Unix socket on the server or this is an internal process, such as autovacuum. |
+| client_hostname     | text                     | Host name of the connected client, as reported by a reverse DNS lookup of **client\_addr**. This column will be non-null only for IP connections and only when **log_hostname** is enabled. |
+| client_port         | integer                  | TCP port number that the client uses for communication with this backend (**-1** if a Unix socket is used) |
+| query_band          | text                     | Job type, which is specified by the GUC parameter **query_band**. The default value is a null string. |
+| pid                 | bigint                   | Thread ID of the backend                                     |
+| block_time          | bigint                   | Block time before the statement is executed (unit: ms)       |
+| start_time          | timestamp with time zone | Time when the statement starts to be executed                |
+| duration            | bigint                   | Duration that a statement has been executed (unit: ms)       |
+| estimate_total_time | bigint                   | Estimated execution time of the statement (unit: ms)         |
+| estimate_left_time  | bigint                   | Estimated remaining execution time of the statement (unit: ms) |
+| enqueue             | text                     | Resource status in workload management                       |
+| resource_pool       | name                     | Resource pool used by the user                               |
+| control_group       | text                     | Cgroup used by the statement                                 |
+| estimate_memory     | integer                  | Estimated memory used by the statement (unit: MB).           |
+| min_peak_memory     | integer                  | Minimum memory peak of the statement across the database nodes (unit: MB) |
+| max_peak_memory     | integer                  | Maximum memory peak of the statement across the database nodes (unit: MB) |
+| average_peak_memory | integer                  | Average memory usage during statement execution (unit: MB)   |
+| memory_skew_percent | integer                  | Memory usage skew of the statement among the database nodes  |
+| spill_info          | text                     | Information about statement spill to the database nodes<br/>- **None**: The statement has not been spilled to disks on the database nodes.<br/>- **All**: The statement has been spilled to disks on the database nodes.<br/>- **[a:b]**: The statement has been spilled to disks on **a** of **b** database nodes. |
+| min_spill_size      | integer                  | Minimum spilled data among database nodes when a spill occurs (unit: MB) (default value:**0**) |
+| max_spill_size      | integer                  | Maximum spilled data among database nodes when a spill occurs (unit: MB) (default value:**0**) |
+| average_spill_size  | integer                  | Average spilled data among database nodes when a spill occurs (unit: MB) (default value:**0**) |
+| spill_skew_percent  | integer                  | Database node spill skew when a spill occurs                 |
+| min_dn_time         | bigint                   | Minimum execution time of the statement across the database nodes (unit: ms) |
+| max_dn_time         | bigint                   | Maximum execution time of the statement across the database nodes (unit: ms) |
+| average_dn_time     | bigint                   | Average execution time of the statement across the database nodes (unit: ms) |
+| dntime_skew_percent | integer                  | Execution time skew of the statement among the database nodes |
+| min_cpu_time        | bigint                   | Minimum CPU time of the statement across the database nodes (unit: ms) |
+| max_cpu_time        | bigint                   | Maximum CPU time of the statement across the database nodes (unit: ms) |
+| total_cpu_time      | bigint                   | Total CPU time of the statement across the database nodes (unit: ms) |
+| cpu_skew_percent    | integer                  | CPU time skew of the statement among the database nodes      |
+| min_peak_iops       | integer                  | Minimum IOPS peak of the statement across the database nodes. It is counted by ones in a column-store table and by ten thousands in a row-store table. |
+| max_peak_iops       | integer                  | Maximum IOPS peak of the statement across the database nodes. It is counted by ones in a column-store table and by ten thousands in a row-store table. |
+| average_peak_iops   | integer                  | Average IOPS peak of the statement across the database nodes. It is counted by ones in a column-store table and by ten thousands in a row-store table. |
+| iops_skew_percent   | integer                  | I/O skew of the statement among the database nodes           |
+| warning             | text                     | Warning. The following warnings are displayed:<br/>- Spill file size large than 256MB<br/>- Broadcast size large than 100MB<br/>- Early spill<br/>- Spill times is greater than 3<br/>- Spill on memory adaptive<br/>- Hash table conflict |
+| queryid             | bigint                   | Internal query ID used for statement execution               |
+| query               | text                     | Statement being executed                                     |
+| query_plan          | text                     | Execution plan of the statement                              |
+| node_group          | text                     | Logical MogDB of the user running the statement              |
+| top_cpu_dn          | text                     | Top N CPU usage                                              |
+| top_mem_dn          | text                     | Top N memory usage                                           |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COUNT.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COUNT.md
new file mode 100644
index 0000000000000000000000000000000000000000..a5cb90a93ea86e4f3ecc860798c558b187e278de
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COUNT.md
@@ -0,0 +1,41 @@
+---
+title: GLOBAL_STATEMENT_COUNT
+summary: GLOBAL_STATEMENT_COUNT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STATEMENT_COUNT
+
+**GLOBAL_STATEMENT_COUNT** displays statistics about five types of running statements (**SELECT**, **INSERT**, **UPDATE**, **DELETE**, and **MERGE INTO**) as well as DDL, DML, and DCL statements on each node of the database.
+
+**Table 1** GLOBAL_STATEMENT_COUNT columns
+
+| **Name**            | **Type** | **Description**                                           |
+| :------------------ | :------- | :-------------------------------------------------------- |
+| node_name           | text     | Node name                                                 |
+| user_name           | text     | Username                                                  |
+| select_count        | bigint   | Statistical result of the **SELECT** statement            |
+| update_count        | bigint   | Statistical result of the **UPDATE** statement            |
+| insert_count        | bigint   | Statistical result of the **INSERT** statement            |
+| delete_count        | bigint   | Statistical result of the **DELETE** statement            |
+| mergeinto_count     | bigint   | Statistical result of the **MERGE INTO** statement        |
+| ddl_count           | bigint   | Number of DDL statements                                  |
+| dml_count           | bigint   | Number of DML statements                                  |
+| dcl_count           | bigint   | Number of DCL statements                                  |
+| total_select_elapse | bigint   | Total response time of **SELECT** statements (unit: μs)   |
+| avg_select_elapse   | bigint   | Average response time of **SELECT** statements (unit: μs) |
+| max_select_elapse   | bigint   | Maximum response time of **SELECT** statements (unit: μs) |
+| min_select_elapse   | bigint   | Minimum response time of **SELECT** statements (unit: μs) |
+| total_update_elapse | bigint   | Total response time of **UPDATE** statements (unit: μs)   |
+| avg_update_elapse   | bigint   | Average response time of **UPDATE** statements (unit: μs) |
+| max_update_elapse   | bigint   | Maximum response time of **UPDATE** statements (unit: μs) |
+| min_update_elapse   | bigint   | Minimum response time of **UPDATE** statements (unit: μs) |
+| total_insert_elapse | bigint   | Total response time of **INSERT** statements (unit: μs)   |
+| avg_insert_elapse   | bigint   | Average response time of **INSERT** statements (unit: μs) |
+| max_insert_elapse   | bigint   | Maximum response time of **INSERT** statements (unit: μs) |
+| min_insert_elapse   | bigint   | Minimum response time of **INSERT** statements (unit: μs) |
+| total_delete_elapse | bigint   | Total response time of **DELETE** statements (unit: μs)   |
+| avg_delete_elapse   | bigint   | Average response time of **DELETE** statements (unit: μs) |
+| max_delete_elapse   | bigint   | Maximum response time of **DELETE** statements (unit: μs) |
+| min_delete_elapse   | bigint   | Minimum response time of **DELETE** statements (unit: μs) |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT.md
new file mode 100644
index 0000000000000000000000000000000000000000..fbc7731b8219d9d11dd6c8e3064bf5c39b096f88
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT.md
@@ -0,0 +1,55 @@
+---
+title: STATEMENT
+summary: STATEMENT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATEMENT
+
+**STATEMENT** obtains information about execution statements (normalized SQL statements) on the current node. To query this view, you must have the **sysadmin** permission. You can view all statistics about normalized SQL statements received by the primary database node and other database nodes, whereas you can view only the statistics about normalized SQL statements executed on other database nodes.
+
+**Table 1** STATEMENT columns
+
+| **Name**            | **Type** | **Description**                                              |
+| :------------------ | :------- | :----------------------------------------------------------- |
+| node_name           | name     | Database process name                                        |
+| node_id             | integer  | Node ID (**node\_id** in **pgxc_node**)                       |
+| user_name           | name     | Username                                                     |
+| user_id             | oid      | OID of the user                                              |
+| unique_sql_id       | bigint   | ID of the normalized SQL statement                           |
+| query               | text     | Normalized SQL statement                                     |
+| n_calls             | bigint   | Number of calls                                              |
+| min_elapse_time     | bigint   | Minimum execution time of the SQL statement in the kernel (unit: μs) |
+| max_elapse_time     | bigint   | Maximum execution time of the SQL statement in the kernel (unit: μs) |
+| total_elapse_time   | bigint   | Total execution time of the SQL statement in the kernel (unit: μs) |
+| n_returned_rows     | bigint   | Number of rows in the result set returned by the **SELECT** statement |
+| n_tuples_fetched    | bigint   | Number of rows randomly scanned                              |
+| n_tuples_returned   | bigint   | Number of rows sequentially scanned                          |
+| n_tuples_inserted   | bigint   | Number of rows inserted                                      |
+| n_tuples_updated    | bigint   | Number of rows updated                                       |
+| n_tuples_deleted    | bigint   | Number of rows deleted                                       |
+| n_blocks_fetched    | bigint   | Number of buffer block access times                          |
+| n_blocks_hit        | bigint   | Number of buffer block hits                                  |
+| n_soft_parse        | bigint   | Number of soft parsing times. The value of **n_soft_parse** plus the value of **n_hard_parse** may be greater than the value of **n_calls** because the number of subqueries is not counted in the value of **n_calls**. |
+| n_hard_parse        | bigint   | Number of hard parsing times. The value of **n_soft_parse** plus the value of **n_hard_parse** may be greater than the value of **n_calls** because the number of subqueries is not counted in the value of **n_calls**. |
+| db_time             | bigint   | Valid DB time, which is accumulated if multiple threads are involved (unit: μs) |
+| cpu_time            | bigint   | CPU time (unit: μs)                                          |
+| execution_time      | bigint   | Execution time in the executor (unit: μs)                    |
+| parse_time          | bigint   | SQL parsing time (unit: μs)                                  |
+| plan_time           | bigint   | SQL plan generation time (unit: μs)                          |
+| rewrite_time        | bigint   | SQL rewriting time (unit: μs)                                |
+| pl_execution_time   | bigint   | Execution time of PL/pgSQL (unit: μs)                        |
+| pl_compilation_time | bigint   | Compilation time of PL/pgSQL (unit: μs)                      |
+| net_send_time       | bigint   | Network time (unit: μs)                                      |
+| data_io_time        | bigint   | I/O time (unit: μs)                                          |
+| sort_count          | bigint   | Sorting count                                                |
+| sort_time           | bigint   | Sorting duration (unit: μs)                                  |
+| sort_mem_used       | bigint   | Size of work memory used during sorting (unit: KB)           |
+| sort_spill_count    | bigint   | Count of file writing when data is flushed to disks during sorting |
+| sort_spill_size     | bigint   | File size used when data is flushed to disks during sorting (unit: KB) |
+| hash_count          | bigint   | Hashing count                                                |
+| hash_time           | bigint   | Hashing duration (unit: μs)                                  |
+| hash_mem_used       | bigint   | Size of work memory used during hashing (unit: KB)           |
+| hash_spill_count    | bigint   | Count of file writing when data is flushed to disks during hashing |
+| hash_spill_size     | bigint   | File size used when data is flushed to disks during hashing (unit: KB) |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_COMPLEX_HISTORY.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_COMPLEX_HISTORY.md
new file mode 100644
index 0000000000000000000000000000000000000000..7d3a01e09c54fe16d23719f3dd14af04c4b7c067
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_COMPLEX_HISTORY.md
@@ -0,0 +1,10 @@
+---
+title: STATEMENT_COMPLEX_HISTORY
+summary: STATEMENT_COMPLEX_HISTORY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATEMENT_COMPLEX_HISTORY
+
+**STATEMENT_COMPLEX_HISTORY** displays load management information about a completed job executed on the primary database node. Columns in this view are the same as those in **[Appendices - Table 5](table-5)**.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_COMPLEX_HISTORY_TABLE.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_COMPLEX_HISTORY_TABLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..181da0c6fc25b9d7c48bc9563d8e243660d388f2
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_COMPLEX_HISTORY_TABLE.md
@@ -0,0 +1,10 @@
+---
+title: STATEMENT_COMPLEX_HISTORY_TABLE
+summary: STATEMENT_COMPLEX_HISTORY_TABLE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATEMENT_COMPLEX_HISTORY_TABLE
+
+**STATEMENT_COMPLEX_HISTORY_TABLE** displays load management information about completed jobs executed on the current primary database node. Data is dumped from the kernel to this system catalog. Columns in this view are the same as those in **Appendices -> Table 5**.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_COMPLEX_RUNTIME.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_COMPLEX_RUNTIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..59aee2dc4b9620012160bb8352751928f05e7213
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_COMPLEX_RUNTIME.md
@@ -0,0 +1,63 @@
+---
+title: STATEMENT_COMPLEX_RUNTIME
+summary: STATEMENT_COMPLEX_RUNTIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATEMENT_COMPLEX_RUNTIME
+
+**STATEMENT_COMPLEX_RUNTIME** displays load management information about jobs being executed by the current user on the primary database node.
+
+**Table 1** STATEMENT_COMPLEX_RUNTIME columns
+
+| Name                | Type                     | Description                                                  |
+| :------------------ | :----------------------- | :----------------------------------------------------------- |
+| datid               | oid                      | OID of the database that the backend is connected to         |
+| dbname              | name                     | Name of the database that the backend is connected to        |
+| schemaname          | text                     | Schema name                                                  |
+| nodename            | text                     | Database process name                                        |
+| username            | name                     | Username used for connecting to the backend                  |
+| application_name    | text                     | Name of the application connected to the backend             |
+| client_addr         | inet                     | IP address of the client connected to the backend. If this column is null, it indicates either the client is connected via a Unix socket on the server or this is an internal process, such as autovacuum |
+| client_hostname     | text                     | Host name of the connected client, as reported by a reverse DNS lookup of **client\_addr**. This column will be non-null only for IP connections and only when **log_hostname** is enabled |
+| client_port         | integer                  | TCP port number that the client uses for communication with this backend (**-1** if a Unix socket is used) |
+| query_band          | text                     | Job type, which is specified by the GUC parameter **query_band**. The default value is a null string |
+| pid                 | bigint                   | Thread ID of the backend                                     |
+| block_time          | bigint                   | Block time before the statement is executed (unit: ms)       |
+| start_time          | timestamp with time zone | Time when the statement starts to be executed                |
+| duration            | bigint                   | Duration that a statement has been executed (unit: ms)       |
+| estimate_total_time | bigint                   | Estimated execution time of the statement (unit: ms)         |
+| estimate_left_time  | bigint                   | Estimated remaining execution time of the statement (unit: ms) |
+| enqueue             | text                     | Resource status in workload management                       |
+| resource_pool       | name                     | Resource pool used by the user                               |
+| control_group       | text                     | Cgroup used by the statement                                 |
+| estimate_memory     | integer                  | Estimated memory used by the statement (unit: MB)            |
+| min_peak_memory     | integer                  | Minimum memory peak of the statement across the database nodes (unit: MB) |
+| max_peak_memory     | integer                  | Maximum memory peak of the statement across the database nodes (unit: MB) |
+| average_peak_memory | integer                  | Average memory usage during statement execution (unit: MB)   |
+| memory_skew_percent | integer                  | Memory usage skew of the statement among the database nodes  |
+| spill_info          | text                     | Information about statement spill to the database nodes<br/>- **None**: The statement has not been spilled to disks on the database nodes.<br/>- **All**: The statement has been spilled to disks on the database nodes.<br/>- **[a:b]**: The statement has been spilled to disks on **a** of **b** database nodes |
+| min_spill_size      | integer                  | Minimum spilled data among database nodes when a spill occurs (unit: MB) (default value:**0**) |
+| max_spill_size      | integer                  | Maximum spilled data among database nodes when a spill occurs (unit: MB) (default value:**0**) |
+| average_spill_size  | integer                  | Average spilled data among database nodes when a spill occurs (unit: MB) (default value:**0**) |
+| spill_skew_percent  | integer                  | Database node spill skew when a spill occurs                 |
+| min_dn_time         | bigint                   | Minimum execution time of the statement across the database nodes (unit: ms) |
+| max_dn_time         | bigint                   | Maximum execution time of the statement across the database nodes (unit: ms) |
+| average_dn_time     | bigint                   | Average execution time of the statement across the database nodes (unit: ms) |
+| dntime_skew_percent | integer                  | Execution time skew of the statement among the database nodes |
+| min_cpu_time        | bigint                   | Minimum CPU time of the statement across the database nodes (unit: ms) |
+| max_cpu_time        | bigint                   | Maximum CPU time of the statement across the database nodes (unit: ms) |
+| total_cpu_time      | bigint                   | Total CPU time of the statement across the database nodes (unit: ms) |
+| cpu_skew_percent    | integer                  | CPU time skew of the statement among the database nodes      |
+| min_peak_iops       | integer                  | Minimum IOPS peak of the statement across the database nodes. It is counted by ones in a column-store table and by ten thousands in a row-store table |
+| max_peak_iops       | integer                  | Maximum IOPS peak of the statement across the database nodes. It is counted by ones in a column-store table and by ten thousands in a row-store table |
+| average_peak_iops   | integer                  | Average IOPS peak of the statement across the database nodes. It is counted by ones in a column-store table and by ten thousands in a row-store table |
+| iops_skew_percent   | integer                  | I/O skew of the statement among the database nodes           |
+| warning             | text                     | Warning. The following warnings are displayed:<br/>- Spill file size large than 256MB<br/>- Broadcast size large than 100MB<br/>- Early spill<br/>- Spill times is greater than 3<br/>- Spill on memory adaptive<br/>- Hash table conflict |
+| queryid             | bigint                   | Internal query ID used for statement execution               |
+| query               | text                     | Statement being executed                                     |
+| query_plan          | text                     | Execution plan of the statement                              |
+| node_group          | text                     | Logical MogDB of the user running the statement              |
+| top_cpu_dn          | text                     | Top N CPU usage                                              |
+| top_mem_dn          | text                     | Top N memory usage                                           |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_COUNT.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_COUNT.md
new file mode 100644
index 0000000000000000000000000000000000000000..114225046bbf918e344d222df513859915cd83fe
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_COUNT.md
@@ -0,0 +1,44 @@
+---
+title: STATEMENT_COUNT
+summary: STATEMENT_COUNT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATEMENT_COUNT
+
+**STATEMENT_COUNT** displays statistics about five types of running statements (**SELECT**, **INSERT**, **UPDATE**, **DELETE**, and **MERGE INTO**) as well as DDL, DML, and DCL statements on the current node of the database.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> By querying the **STATEMENT_COUNT** view, a common user can view statistics only about this user on the current node, whereas an administrator can view statistics about all users on the current node. When MogDB or the node is restarted, the statistics are cleared and the counting restarts. The system counts when a node receives a query, including a query inside MogDB. For example, when the primary database node receives a query and distributes multiple queries to other database nodes, the queries are counted accordingly on the database nodes.
+
+**Table 1** STATEMENT_COUNT columns
+
+| **Name**            | **Type** | **Description**                                           |
+| :------------------ | :------- | :-------------------------------------------------------- |
+| node_name           | text     | Database process name                                     |
+| user_name           | text     | Username                                                  |
+| select_count        | bigint   | Statistical result of the **SELECT** statement            |
+| update_count        | bigint   | Statistical result of the **UPDATE** statement            |
+| insert_count        | bigint   | Statistical result of the **INSERT** statement            |
+| delete_count        | bigint   | Statistical result of the **DELETE** statement            |
+| mergeinto_count     | bigint   | Statistical result of the **MERGE INTO** statement        |
+| ddl_count           | bigint   | Number of DDL statements                                  |
+| dml_count           | bigint   | Number of DML statements                                  |
+| dcl_count           | bigint   | Number of DCL statements                                  |
+| total_select_elapse | bigint   | Total response time of **SELECT** statements (unit: μs)   |
+| avg_select_elapse   | bigint   | Average response time of **SELECT** statements (unit: μs) |
+| max_select_elapse   | bigint   | Maximum response time of **SELECT** statements (unit: μs) |
+| min_select_elapse   | bigint   | Minimum response time of **SELECT** statements (unit: μs) |
+| total_update_elapse | bigint   | Total response time of **UPDATE** statements (unit: μs)   |
+| avg_update_elapse   | bigint   | Average response time of **UPDATE** statements (unit: μs) |
+| max_update_elapse   | bigint   | Maximum response time of **UPDATE** statements (unit: μs) |
+| min_update_elapse   | bigint   | Minimum response time of **UPDATE** statements (unit: μs) |
+| total_insert_elapse | bigint   | Total response time of **INSERT** statements (unit: μs)   |
+| avg_insert_elapse   | bigint   | Average response time of **INSERT** statements (unit: μs) |
+| max_insert_elapse   | bigint   | Maximum response time of **INSERT** statements (unit: μs) |
+| min_insert_elapse   | bigint   | Minimum response time of **INSERT** statements (unit: μs) |
+| total_delete_elapse | bigint   | Total response time of **DELETE** statements (unit: μs)   |
+| avg_delete_elapse   | bigint   | Average response time of **DELETE** statements (unit: μs) |
+| max_delete_elapse   | bigint   | Maximum response time of **DELETE** statements (unit: μs) |
+| min_delete_elapse   | bigint   | Minimum response time of **DELETE** statements (unit: μs) |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_HISTORY.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_HISTORY.md
new file mode 100644
index 0000000000000000000000000000000000000000..47f47bfe63827aa093c6223deb36f39ac9a59f78
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_HISTORY.md
@@ -0,0 +1,492 @@
+---
+title: STATEMENT_HISTORY
+summary: STATEMENT_HISTORY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATEMENT_HISTORY
+
+**STATEMENT_HISTORY**  displays information about execution statements on the current node. To query this system catalog, you must have the  **sysadmin**permission. The result can be queried only in the system database but cannot be queried in the user database.
+
+The constraints on the query of this system catalog are as follows:
+
+- Data must be queried in the Postgres database. No data exists in other databases.
+- This system catalog is controlled by  **track_stmt_stat_level**. The default value is  **OFF,L0**, where the first part controls full SQL statements, and the second part controls slow SQL statements. For details about the record level of each field, see the following table.
+- For slow SQL statements, if the value of  **track_stmt_stat_level**  is not  **OFF**  and the SQL execution time exceeds the value of  **log_min_duration_statement**, the SQL statement is recorded as a slow SQL statement.
+
+**Table  1**  STATEMENT_HISTORY columns
+
+<table><thead align="left"><tr id="row44901885283"><th class="cellrowborder" valign="top"  id="mcps1.2.5.1.1"><p id="p204912089289"><a name="p204912089289"></a><a name="p204912089289"></a>Name</p>
+</th>
+<th class="cellrowborder" valign="top"  id="mcps1.2.5.1.2"><p id="p17491108122820"><a name="p17491108122820"></a><a name="p17491108122820"></a>Type</p>
+</th>
+<th class="cellrowborder" valign="top"  id="mcps1.2.5.1.3"><p id="p13491282281"><a name="p13491282281"></a><a name="p13491282281"></a>Description</p>
+</th>
+<th class="cellrowborder" valign="top"  id="mcps1.2.5.1.4"><p id="p1528612136307"><a name="p1528612136307"></a><a name="p1528612136307"></a>Record Level</p>
+</th>
+</tr>
+</thead>
+<tbody><tr id="row16491158192819"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p1149178122814"><a name="p1149178122814"></a><a name="p1149178122814"></a>db_name</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p124911782289"><a name="p124911782289"></a><a name="p124911782289"></a>name</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p1445326163513"><a name="p1445326163513"></a><a name="p1445326163513"></a>Database name.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p028618138308"><a name="p028618138308"></a><a name="p028618138308"></a>L0</p>
+</td>
+</tr>
+<tr id="row14915892817"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p174910812286"><a name="p174910812286"></a><a name="p174910812286"></a>schema_name</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p1949128172817"><a name="p1949128172817"></a><a name="p1949128172817"></a>name</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p164911589285"><a name="p164911589285"></a><a name="p164911589285"></a>Schema name.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p1328616134303"><a name="p1328616134303"></a><a name="p1328616134303"></a>L0</p>
+</td>
+</tr>
+<tr id="row749113817286"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p1749115882810"><a name="p1749115882810"></a><a name="p1749115882810"></a>origin_node</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p449148162820"><a name="p449148162820"></a><a name="p449148162820"></a>integer</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p16491108182819"><a name="p16491108182819"></a><a name="p16491108182819"></a>Node name.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p19286111393017"><a name="p19286111393017"></a><a name="p19286111393017"></a>L0</p>
+</td>
+</tr>
+<tr id="row649168132810"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p44917817289"><a name="p44917817289"></a><a name="p44917817289"></a>user_name</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p194912810285"><a name="p194912810285"></a><a name="p194912810285"></a>name</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p134914811289"><a name="p134914811289"></a><a name="p134914811289"></a>Username.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p9286161313016"><a name="p9286161313016"></a><a name="p9286161313016"></a>L0</p>
+</td>
+</tr>
+<tr id="row249116815283"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p165338590242"><a name="p165338590242"></a><a name="p165338590242"></a>application_name</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p195321859102416"><a name="p195321859102416"></a><a name="p195321859102416"></a>text</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p105321759202415"><a name="p105321759202415"></a><a name="p105321759202415"></a>Name of the application that sends a request.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p1528671363015"><a name="p1528671363015"></a><a name="p1528671363015"></a>L0</p>
+</td>
+</tr>
+<tr id="row7491288288"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p1353125916241"><a name="p1353125916241"></a><a name="p1353125916241"></a>client_addr</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p14530125919243"><a name="p14530125919243"></a><a name="p14530125919243"></a>text</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p153025992418"><a name="p153025992418"></a><a name="p153025992418"></a>IP address of the client that sends a request.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p0286181333019"><a name="p0286181333019"></a><a name="p0286181333019"></a>L0</p>
+</td>
+</tr>
+<tr id="row1749158112812"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p1652975902410"><a name="p1652975902410"></a><a name="p1652975902410"></a>client_port</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p2529859102410"><a name="p2529859102410"></a><a name="p2529859102410"></a>integer</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p252865911245"><a name="p252865911245"></a><a name="p252865911245"></a>Port number of the client that sends a request.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p132861413123018"><a name="p132861413123018"></a><a name="p132861413123018"></a>L0</p>
+</td>
+</tr>
+<tr id="row148912328303"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p452716597243"><a name="p452716597243"></a><a name="p452716597243"></a>unique_query_id</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p115271059112417"><a name="p115271059112417"></a><a name="p115271059112417"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p1752618596243"><a name="p1752618596243"></a><a name="p1752618596243"></a>ID of the normalized SQL statement.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p1528631383020"><a name="p1528631383020"></a><a name="p1528631383020"></a>L0</p>
+</td>
+</tr>
+<tr id="row3770204193018"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p3525059192414"><a name="p3525059192414"></a><a name="p3525059192414"></a>debug_query_id</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p19525195982418"><a name="p19525195982418"></a><a name="p19525195982418"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p9524359162416"><a name="p9524359162416"></a><a name="p9524359162416"></a>ID of the unique SQL statement.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p10286101318302"><a name="p10286101318302"></a><a name="p10286101318302"></a>L0</p>
+</td>
+</tr>
+<tr id="row1024411583535"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p124416583539"><a name="p124416583539"></a><a name="p124416583539"></a>query</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p024495835312"><a name="p024495835312"></a><a name="p024495835312"></a>text</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p192447585532"><a name="p192447585532"></a><a name="p192447585532"></a>Normalized SQL statement.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p1428681313019"><a name="p1428681313019"></a><a name="p1428681313019"></a>L0</p>
+</td>
+</tr>
+<tr id="row3114174743016"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p10523459142411"><a name="p10523459142411"></a><a name="p10523459142411"></a>start_time</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p1752305914246"><a name="p1752305914246"></a><a name="p1752305914246"></a>timestamp with time zone</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p952265920244"><a name="p952265920244"></a><a name="p952265920244"></a>Time when a statement starts.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p0286151314305"><a name="p0286151314305"></a><a name="p0286151314305"></a>L0</p>
+</td>
+</tr>
+<tr id="row769485863017"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p155224594242"><a name="p155224594242"></a><a name="p155224594242"></a>finish_time</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p752117599242"><a name="p752117599242"></a><a name="p752117599242"></a>timestamp with time zone</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p1952065952411"><a name="p1952065952411"></a><a name="p1952065952411"></a>Time when a statement ends.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p17286201317309"><a name="p17286201317309"></a><a name="p17286201317309"></a>L0</p>
+</td>
+</tr>
+<tr id="row254515130314"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p1752095917241"><a name="p1752095917241"></a><a name="p1752095917241"></a>slow_sql_threshold</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p185191059122416"><a name="p185191059122416"></a><a name="p185191059122416"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p35181759122420"><a name="p35181759122420"></a><a name="p35181759122420"></a>Standard for slow SQL statement execution.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p11286171373011"><a name="p11286171373011"></a><a name="p11286171373011"></a>L0</p>
+</td>
+</tr>
+<tr id="row4589123123110"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p4518559182412"><a name="p4518559182412"></a><a name="p4518559182412"></a>transaction_id</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p5517185952411"><a name="p5517185952411"></a><a name="p5517185952411"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p2517125922414"><a name="p2517125922414"></a><a name="p2517125922414"></a>Transaction ID.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p928621319302"><a name="p928621319302"></a><a name="p928621319302"></a>L0</p>
+</td>
+</tr>
+<tr id="row858902319313"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p15516145982414"><a name="p15516145982414"></a><a name="p15516145982414"></a>thread_id</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p20515659162415"><a name="p20515659162415"></a><a name="p20515659162415"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p55151659102410"><a name="p55151659102410"></a><a name="p55151659102410"></a>ID of an execution thread.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p1428651323019"><a name="p1428651323019"></a><a name="p1428651323019"></a>L0</p>
+</td>
+</tr>
+<tr id="row358810234313"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p1251416594243"><a name="p1251416594243"></a><a name="p1251416594243"></a>session_id</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p205131359172418"><a name="p205131359172418"></a><a name="p205131359172418"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p185131159202420"><a name="p185131159202420"></a><a name="p185131159202420"></a>Session ID of a user.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p12286813103010"><a name="p12286813103010"></a><a name="p12286813103010"></a>L0</p>
+</td>
+</tr>
+<tr id="row1858812314315"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p35121459142416"><a name="p35121459142416"></a><a name="p35121459142416"></a>n_soft_parse</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p105113599242"><a name="p105113599242"></a><a name="p105113599242"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p172795294391"><a name="p172795294391"></a><a name="p172795294391"></a>Number of soft parsing times. The value of <strong id="b66268154764928"><a name="b66268154764928"></a><a name="b66268154764928"></a>n_soft_parse</strong> plus the value of <strong id="b127293174064928"><a name="b127293174064928"></a><a name="b127293174064928"></a>n_hard_parse</strong> may be greater than the value of <strong id="b200453595164928"><a name="b200453595164928"></a><a name="b200453595164928"></a>n_calls</strong> because the number of subqueries is not counted in the value of <strong id="b204759808964928"><a name="b204759808964928"></a><a name="b204759808964928"></a>n_calls</strong>.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p1286161310302"><a name="p1286161310302"></a><a name="p1286161310302"></a>L0</p>
+</td>
+</tr>
+<tr id="row13775115215319"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p135106596249"><a name="p135106596249"></a><a name="p135106596249"></a>n_hard_parse</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p951015915249"><a name="p951015915249"></a><a name="p951015915249"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p18230133983919"><a name="p18230133983919"></a><a name="p18230133983919"></a>Number of hard parsing times. The value of <strong id="b125824156064928"><a name="b125824156064928"></a><a name="b125824156064928"></a>n_soft_parse</strong> plus the value of <strong id="b47274720064928"><a name="b47274720064928"></a><a name="b47274720064928"></a>n_hard_parse</strong> may be greater than the value of <strong id="b48720138464928"><a name="b48720138464928"></a><a name="b48720138464928"></a>n_calls</strong> because the number of subqueries is not counted in the value of <strong id="b195845435964928"><a name="b195845435964928"></a><a name="b195845435964928"></a>n_calls</strong>.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p3286181310305"><a name="p3286181310305"></a><a name="p3286181310305"></a>L0</p>
+</td>
+</tr>
+<tr id="row877515216319"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p135081059162412"><a name="p135081059162412"></a><a name="p135081059162412"></a>query_plan</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p18508185911243"><a name="p18508185911243"></a><a name="p18508185911243"></a>text</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p150795912247"><a name="p150795912247"></a><a name="p150795912247"></a>Statement execution plan.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p1328731383018"><a name="p1328731383018"></a><a name="p1328731383018"></a>L1</p>
+</td>
+</tr>
+<tr id="row17775052123118"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p1250610593248"><a name="p1250610593248"></a><a name="p1250610593248"></a>n_returned_rows</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p1150610599240"><a name="p1150610599240"></a><a name="p1150610599240"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p19505155942415"><a name="p19505155942415"></a><a name="p19505155942415"></a>Number of rows in the result set returned by the <strong id="b194137955564928"><a name="b194137955564928"></a><a name="b194137955564928"></a>SELECT</strong> statement.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p1628716136303"><a name="p1628716136303"></a><a name="p1628716136303"></a>L0</p>
+</td>
+</tr>
+<tr id="row1977515273114"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p45042059132410"><a name="p45042059132410"></a><a name="p45042059132410"></a>n_tuples_fetched</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p1450495913244"><a name="p1450495913244"></a><a name="p1450495913244"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p19503195917240"><a name="p19503195917240"></a><a name="p19503195917240"></a>Number of rows randomly scanned.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p42877136308"><a name="p42877136308"></a><a name="p42877136308"></a>L0</p>
+</td>
+</tr>
+<tr id="row1677535213111"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p250235912413"><a name="p250235912413"></a><a name="p250235912413"></a>n_tuples_returned</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p185021959192418"><a name="p185021959192418"></a><a name="p185021959192418"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p350120599248"><a name="p350120599248"></a><a name="p350120599248"></a>Number of rows sequentially scanned.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p8287413143018"><a name="p8287413143018"></a><a name="p8287413143018"></a>L0</p>
+</td>
+</tr>
+<tr id="row777417524311"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p16500195992414"><a name="p16500195992414"></a><a name="p16500195992414"></a>n_tuples_inserted</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p1150019594246"><a name="p1150019594246"></a><a name="p1150019594246"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p948105916244"><a name="p948105916244"></a><a name="p948105916244"></a>Number of rows inserted.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p22871135302"><a name="p22871135302"></a><a name="p22871135302"></a>L0</p>
+</td>
+</tr>
+<tr id="row677415293112"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p2498222251"><a name="p2498222251"></a><a name="p2498222251"></a>n_tuples_updated</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p749722192515"><a name="p749722192515"></a><a name="p749722192515"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p549713212254"><a name="p549713212254"></a><a name="p549713212254"></a>Number of rows updated.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p628721314301"><a name="p628721314301"></a><a name="p628721314301"></a>L0</p>
+</td>
+</tr>
+<tr id="row1774185218312"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p749611272519"><a name="p749611272519"></a><a name="p749611272519"></a>n_tuples_deleted</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p349513202519"><a name="p349513202519"></a><a name="p349513202519"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p17495923250"><a name="p17495923250"></a><a name="p17495923250"></a>Number of rows deleted.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p4287111343014"><a name="p4287111343014"></a><a name="p4287111343014"></a>L0</p>
+</td>
+</tr>
+<tr id="row277420523319"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p94943242512"><a name="p94943242512"></a><a name="p94943242512"></a>n_blocks_fetched</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p749317222510"><a name="p749317222510"></a><a name="p749317222510"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p449282182511"><a name="p449282182511"></a><a name="p449282182511"></a>Number of buffer block access times.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p5287131333016"><a name="p5287131333016"></a><a name="p5287131333016"></a>L0</p>
+</td>
+</tr>
+<tr id="row57742052153113"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p749211282517"><a name="p749211282517"></a><a name="p749211282517"></a>n_blocks_hit</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p849132102510"><a name="p849132102510"></a><a name="p849132102510"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p749012242515"><a name="p749012242515"></a><a name="p749012242515"></a>Number of buffer block hits.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p82871813143014"><a name="p82871813143014"></a><a name="p82871813143014"></a>L0</p>
+</td>
+</tr>
+<tr id="row777455214319"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p184893272519"><a name="p184893272519"></a><a name="p184893272519"></a>db_time</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p24891427257"><a name="p24891427257"></a><a name="p24891427257"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p1771542215411"><a name="p1771542215411"></a><a name="p1771542215411"></a>Valid DB time, which is accumulated if multiple threads are involved (unit: μs).</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p14287131318305"><a name="p14287131318305"></a><a name="p14287131318305"></a>L0</p>
+</td>
+</tr>
+<tr id="row197745525319"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p1448713252518"><a name="p1448713252518"></a><a name="p1448713252518"></a>cpu_time</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p15486922257"><a name="p15486922257"></a><a name="p15486922257"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p948622132512"><a name="p948622132512"></a><a name="p948622132512"></a>CPU time (unit: μs).</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p182871113103018"><a name="p182871113103018"></a><a name="p182871113103018"></a>L0</p>
+</td>
+</tr>
+<tr id="row7761050202716"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p14761650132718"><a name="p14761650132718"></a><a name="p14761650132718"></a>execution_time</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p1276125014277"><a name="p1276125014277"></a><a name="p1276125014277"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p1976118507270"><a name="p1976118507270"></a><a name="p1976118507270"></a>Execution time in the executor (unit: μs).</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p18287213183013"><a name="p18287213183013"></a><a name="p18287213183013"></a>L0</p>
+</td>
+</tr>
+<tr id="row96551157152710"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p765618575270"><a name="p765618575270"></a><a name="p765618575270"></a>parse_time</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p3656185752712"><a name="p3656185752712"></a><a name="p3656185752712"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p106561157142716"><a name="p106561157142716"></a><a name="p106561157142716"></a>SQL parsing time (unit: μs).</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p6287161319308"><a name="p6287161319308"></a><a name="p6287161319308"></a>L0</p>
+</td>
+</tr>
+<tr id="row386316372814"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p98641331289"><a name="p98641331289"></a><a name="p98641331289"></a>plan_time</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p1686416312283"><a name="p1686416312283"></a><a name="p1686416312283"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p198640320288"><a name="p198640320288"></a><a name="p198640320288"></a>SQL plan generation time (unit: μs).</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p728751313307"><a name="p728751313307"></a><a name="p728751313307"></a>L0</p>
+</td>
+</tr>
+<tr id="row1236810134287"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p12368141313288"><a name="p12368141313288"></a><a name="p12368141313288"></a>rewrite_time</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p143681413202810"><a name="p143681413202810"></a><a name="p143681413202810"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p936861372810"><a name="p936861372810"></a><a name="p936861372810"></a>SQL rewriting time (unit: μs).</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p1287191312304"><a name="p1287191312304"></a><a name="p1287191312304"></a>L0</p>
+</td>
+</tr>
+<tr id="row1831252022816"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p14312102010285"><a name="p14312102010285"></a><a name="p14312102010285"></a>pl_execution_time</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p63121020102811"><a name="p63121020102811"></a><a name="p63121020102811"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p33121020172816"><a name="p33121020172816"></a><a name="p33121020172816"></a>Execution time of PL/pgSQL (unit: μs).</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p128731312309"><a name="p128731312309"></a><a name="p128731312309"></a>L0</p>
+</td>
+</tr>
+<tr id="row12287162622811"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p18287182642811"><a name="p18287182642811"></a><a name="p18287182642811"></a>pl_compilation_time</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p1428782692815"><a name="p1428782692815"></a><a name="p1428782692815"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p628712617287"><a name="p628712617287"></a><a name="p628712617287"></a>Compilation time of PL/pgSQL (unit: μs).</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p102871113163013"><a name="p102871113163013"></a><a name="p102871113163013"></a>L0</p>
+</td>
+</tr>
+<tr id="row9895133272810"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p12895193212813"><a name="p12895193212813"></a><a name="p12895193212813"></a>data_io_time</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p6895103242810"><a name="p6895103242810"></a><a name="p6895103242810"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p10895203212289"><a name="p10895203212289"></a><a name="p10895203212289"></a>I/O time (unit: μs).</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p1287181383013"><a name="p1287181383013"></a><a name="p1287181383013"></a>L0</p>
+</td>
+</tr>
+<tr id="row19021825295"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p790215242915"><a name="p790215242915"></a><a name="p790215242915"></a>net_send_info</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p19022242917"><a name="p19022242917"></a><a name="p19022242917"></a>text</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p166675265421"><a name="p166675265421"></a><a name="p166675265421"></a>Network status of messages sent through a physical connection, including the time (unit: μs), number of calls, and throughput (unit: byte). This can be used to analyze the network overhead of SQL statements in a distributed system and is not supported in standalone system. Example: {"time":xxx, "n_calls":xxx, "size":xxx}.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p202871513143012"><a name="p202871513143012"></a><a name="p202871513143012"></a>L0</p>
+</td>
+</tr>
+<tr id="row1597621252919"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p129761512172910"><a name="p129761512172910"></a><a name="p129761512172910"></a>net_recv_info</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p19976131232915"><a name="p19976131232915"></a><a name="p19976131232915"></a>text</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p16967114513427"><a name="p16967114513427"></a><a name="p16967114513427"></a>Network status of messages received through a physical connection, including the time (unit: μs), number of calls, and throughput (unit: byte). This column can be used to analyze the network overhead of SQL in a distributed system. This column is not supported in a standalone mode. Example: {"time":xxx, "n_calls":xxx, "size":xxx}.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p15287413123014"><a name="p15287413123014"></a><a name="p15287413123014"></a>L0</p>
+</td>
+</tr>
+<tr id="row2051215917299"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p2051269132917"><a name="p2051269132917"></a><a name="p2051269132917"></a>net_stream_send_info</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p1451215911291"><a name="p1451215911291"></a><a name="p1451215911291"></a>text</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p695315818427"><a name="p695315818427"></a><a name="p695315818427"></a>Network status of messages sent through a logical connection, including the time (unit: μs), number of calls, and throughput (unit: byte). This column can be used to analyze the network overhead of SQL in a distributed system. This column is not supported in a standalone mode. Example: {"time":xxx, "n_calls":xxx, "size":xxx}.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p192871113113013"><a name="p192871113113013"></a><a name="p192871113113013"></a>L0</p>
+</td>
+</tr>
+<tr id="row1978203162913"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p167818317296"><a name="p167818317296"></a><a name="p167818317296"></a>net_stream_recv_info</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p1578173110298"><a name="p1578173110298"></a><a name="p1578173110298"></a>text</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p292014112436"><a name="p292014112436"></a><a name="p292014112436"></a>Network status of messages received through a logical connection, including the time (unit: μs), number of calls, and throughput (unit: byte). This column can be used to analyze the network overhead of SQL in a distributed system. This column is not supported in a standalone mode. Example: {"time":xxx, "n_calls":xxx, "size":xxx}.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p5287131303020"><a name="p5287131303020"></a><a name="p5287131303020"></a>L0</p>
+</td>
+</tr>
+<tr id="row15401123892910"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p154011138192918"><a name="p154011138192918"></a><a name="p154011138192918"></a>lock_count</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p1440123818299"><a name="p1440123818299"></a><a name="p1440123818299"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p840113386291"><a name="p840113386291"></a><a name="p840113386291"></a>Number of locks.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p16287141393017"><a name="p16287141393017"></a><a name="p16287141393017"></a>L0</p>
+</td>
+</tr>
+<tr id="row17958944152917"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p19958204410298"><a name="p19958204410298"></a><a name="p19958204410298"></a>lock_time</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p69582044122918"><a name="p69582044122918"></a><a name="p69582044122918"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p12958344142919"><a name="p12958344142919"></a><a name="p12958344142919"></a>Time required for locking.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p428713136307"><a name="p428713136307"></a><a name="p428713136307"></a>L1</p>
+</td>
+</tr>
+<tr id="row4438148112918"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p1043884818295"><a name="p1043884818295"></a><a name="p1043884818295"></a>lock_wait_count</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p1743816482294"><a name="p1743816482294"></a><a name="p1743816482294"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p11438144832911"><a name="p11438144832911"></a><a name="p11438144832911"></a>Number of lock waits.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p7287141313019"><a name="p7287141313019"></a><a name="p7287141313019"></a>L0</p>
+</td>
+</tr>
+<tr id="row12165137203010"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p01662710309"><a name="p01662710309"></a><a name="p01662710309"></a>lock_wait_time</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p11166379302"><a name="p11166379302"></a><a name="p11166379302"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p2016677173010"><a name="p2016677173010"></a><a name="p2016677173010"></a>Time required for lock waiting.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p228791343012"><a name="p228791343012"></a><a name="p228791343012"></a>L1</p>
+</td>
+</tr>
+<tr id="row1594391063014"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p139437103309"><a name="p139437103309"></a><a name="p139437103309"></a>lock_max_count</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p3943910163018"><a name="p3943910163018"></a><a name="p3943910163018"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p394311015303"><a name="p394311015303"></a><a name="p394311015303"></a>Maximum number of locks.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p228761311308"><a name="p228761311308"></a><a name="p228761311308"></a>L0</p>
+</td>
+</tr>
+<tr id="row15933436143016"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p199331936153019"><a name="p199331936153019"></a><a name="p199331936153019"></a>lwlock_count</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p5933183683016"><a name="p5933183683016"></a><a name="p5933183683016"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p893393612304"><a name="p893393612304"></a><a name="p893393612304"></a>Number of lightweight locks (reserved).</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p02879138309"><a name="p02879138309"></a><a name="p02879138309"></a>L0</p>
+</td>
+</tr>
+<tr id="row92451440133019"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p624512407308"><a name="p624512407308"></a><a name="p624512407308"></a>lwlock_wait_count</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p1024613403300"><a name="p1024613403300"></a><a name="p1024613403300"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p162462407306"><a name="p162462407306"></a><a name="p162462407306"></a>Number of lightweight lock waits.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p0288161316307"><a name="p0288161316307"></a><a name="p0288161316307"></a>L0</p>
+</td>
+</tr>
+<tr id="row10701104318302"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p1470184333016"><a name="p1470184333016"></a><a name="p1470184333016"></a>lwlock_time</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p870104318305"><a name="p870104318305"></a><a name="p870104318305"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p17701543103012"><a name="p17701543103012"></a><a name="p17701543103012"></a>Time required for lightweight locking (reserved).</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p17288111343017"><a name="p17288111343017"></a><a name="p17288111343017"></a>L1</p>
+</td>
+</tr>
+<tr id="row551915663018"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p25199565301"><a name="p25199565301"></a><a name="p25199565301"></a>lwlock_wait_time</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p8519145615307"><a name="p8519145615307"></a><a name="p8519145615307"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p195190563305"><a name="p195190563305"></a><a name="p195190563305"></a>Time required for lightweight lock waiting.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p628881320304"><a name="p628881320304"></a><a name="p628881320304"></a>L1</p>
+</td>
+</tr>
+<tr id="row1139711323112"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p73972034315"><a name="p73972034315"></a><a name="p73972034315"></a>details</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p339717319319"><a name="p339717319319"></a><a name="p339717319319"></a>bytea</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p43971231315"><a name="p43971231315"></a><a name="p43971231315"></a>List of statement lock events, which are recorded in time sequence. The number of records is affected by the <strong id="b15117850175510"><a name="b15117850175510"></a><a name="b15117850175510"></a>track_stmt_details_size </strong>parameter.</p>
+<p id="p206443813496"><a name="p206443813496"></a><a name="p206443813496"></a>Events include:</p>
+<a name="ul1619215224171"></a><a name="ul1619215224171"></a><ul id="ul1619215224171"><li>Start locking.</li><li>Complete locking.</li><li>Start lock waiting.</li><li>Complete lock waiting.</li><li>Start unlocking.</li><li>Complete unlocking.</li><li>Start lightweight lock waiting.</li><li>Complete lightweight lock waiting.</li></ul>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p162884132309"><a name="p162884132309"></a><a name="p162884132309"></a>L2</p>
+</td>
+</tr>
+<tr id="row1146417610552"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p174641163550"><a name="p174641163550"></a><a name="p174641163550"></a>is_slow_sql</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p44649617558"><a name="p44649617558"></a><a name="p44649617558"></a>boolean</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p13464660559"><a name="p13464660559"></a><a name="p13464660559"></a>Whether the SQL statement is a slow SQL statement.</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p17288713183018"><a name="p17288713183018"></a><a name="p17288713183018"></a>L0</p>
+</td>
+</tr>
+</tbody>
+</table>
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_RESPONSETIME_PERCENTILE.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_RESPONSETIME_PERCENTILE.md
new file mode 100644
index 0000000000000000000000000000000000000000..3591019727792cd297c803a65b4cad4b02e4c390
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_RESPONSETIME_PERCENTILE.md
@@ -0,0 +1,17 @@
+---
+title: STATEMENT_RESPONSETIME_PERCENTILE
+summary: STATEMENT_RESPONSETIME_PERCENTILE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATEMENT_RESPONSETIME_PERCENTILE
+
+**STATEMENT_RESPONSETIME_PERCENTILE** obtains the response times of 80% and 95% SQL statements in the MogDB.
+
+**Table 1** STATEMENT_RESPONSETIME_PERCENTILE columns
+
+| Name | Type   | Description                                                 |
+| :--- | :----- | :---------------------------------------------------------- |
+| p80  | bigint | Response time of 80% SQL statements in the MogDB (unit: μs) |
+| p95  | bigint | Response time of 95% SQL statements in the MogDB (unit: μs) |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_USER_COMPLEX_HISTORY.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_USER_COMPLEX_HISTORY.md
new file mode 100644
index 0000000000000000000000000000000000000000..4947c8efd544a28de48602ce4dec97d2d69e715f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_USER_COMPLEX_HISTORY.md
@@ -0,0 +1,10 @@
+---
+title: STATEMENT_USER_COMPLEX_HISTORY
+summary: STATEMENT_USER_COMPLEX_HISTORY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATEMENT_USER_COMPLEX_HISTORY
+
+**STATEMENT_USER_COMPLEX_HISTORY** displays load management information about completed jobs executed on the current primary database node. Data is dumped from the kernel to this system catalog. Columns in this view are the same as those in **Appendices -> Table 5**.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_WLMSTAT_COMPLEX_RUNTIME.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_WLMSTAT_COMPLEX_RUNTIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..75ae72f9f6788c2e547696894e5cc614b48b52be
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_WLMSTAT_COMPLEX_RUNTIME.md
@@ -0,0 +1,38 @@
+---
+title: STATEMENT_WLMSTAT_COMPLEX_RUNTIME
+summary: STATEMENT_WLMSTAT_COMPLEX_RUNTIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATEMENT_WLMSTAT_COMPLEX_RUNTIME
+
+**STATEMENT_WLMSTAT_COMPLEX_RUNTIME** displays load management information about ongoing jobs executed by the current user.
+
+**Table 1** STATEMENT_WLMSTAT_COMPLEX_RUNTIME columns
+
+| Name             | Type    | Description                                                  |
+| :--------------- | :------ | :----------------------------------------------------------- |
+| datid            | oid     | OID of the database that the backend is connected to         |
+| datname          | name    | Name of the database that the backend is connected to        |
+| threadid         | bigint  | Thread ID of the backend                                     |
+| processid        | integer | Process ID of the backend                                    |
+| usesysid         | oid     | OID of the user logged in to the backend                     |
+| appname          | text    | Name of the application connected to the backend             |
+| usename          | name    | Name of the user logged in to the backend                    |
+| priority         | bigint  | Priority of Cgroup where the statement is located            |
+| attribute        | text    | Attributes of the statement:<br/>- **Ordinary**: default attribute of a statement before it is parsed by the database<br/>- **Simple**: simple statement<br/>- **Complicated**: complicated statement<br/>- **Internal**: internal statement of the database |
+| block_time       | bigint  | Pending duration of the statement by now (unit: s)           |
+| elapsed_time     | bigint  | Actual execution duration of the statement by now (unit: s)  |
+| total_cpu_time   | bigint  | Total CPU usage duration of the statement on the database nodes in the last period (unit: s) |
+| cpu_skew_percent | integer | CPU usage skew percentage of the statement on the database nodes in the last period |
+| statement_mem    | integer | **statement_mem** used for executing the statement (reserved column) |
+| active_points    | integer | Number of concurrently active points occupied by the statement in the resource pool |
+| dop_value        | integer | DOP value obtained by the statement from the resource pool   |
+| control_group    | text    | Unsupported currently                                        |
+| status           | text    | Unsupported currently                                        |
+| enqueue          | text    | Queuing status of the statement, including:<br/>- **Global**: queuing in the global queue<br/>- **Respool**: queuing in the resource pool queue<br/>- **CentralQueue**: queuing on the CCN<br/>- **Transaction**: being in a transaction block<br/>- **StoredProc**: being in a stored procedure<br/>- **None**: not in the queue<br/>- **Forced None**: being forcibly executed (transaction block statement or stored procedure statement are) because the statement waiting time exceeds the specified value |
+| resource_pool    | name    | Current resource pool where the statements are located       |
+| query            | text    | Latest query at the backend. If **state** is **active**, this column shows the ongoing query. In all other states, it shows the last query that was executed |
+| is_plana         | boolean | Whether a statement occupies the resources of other logical MogDB in logical MogDB mode. The default value is **f** (does not occupy resources) |
+| node_group       | text    | Logical MogDB of the user running the statement              |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/SUMMARY_STATEMENT.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/SUMMARY_STATEMENT.md
new file mode 100644
index 0000000000000000000000000000000000000000..38a9b6095a92715958352602af51d5315560c290
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/SUMMARY_STATEMENT.md
@@ -0,0 +1,56 @@
+---
+title: SUMMARY_STATEMENT
+summary: SUMMARY_STATEMENT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STATEMENT
+
+**SUMMARY_STATEMENT** obtains all information about execution statements (normalized SQL statements) on the primary database node and other database nodes.
+
+**Table 1** SUMMARY_STATEMENT columns
+
+| **Name**            | **Type**                 | **Description**                                              |
+| :------------------ | :----------------------- | :----------------------------------------------------------- |
+| node_name           | name                     | Database process name                                        |
+| node_id             | integer                  | ID of a node                                                 |
+| user_name           | name                     | Username                                                     |
+| user_id             | oid                      | OID of the user                                              |
+| unique_sql_id       | bigint                   | ID of the normalized SQL statement                           |
+| query               | text                     | Normalized SQL statement                                     |
+| n_calls             | bigint                   | Number of calls                                              |
+| min_elapse_time     | bigint                   | Minimum execution time of the SQL statement in the kernel (unit: μs) |
+| max_elapse_time     | bigint                   | Maximum execution time of the SQL statement in the kernel (unit: μs) |
+| total_elapse_time   | bigint                   | Total execution time of the SQL statement in the kernel (unit: μs) |
+| n_returned_rows     | bigint                   | Number of rows in the result set returned by the **SELECT** statement |
+| n_tuples_fetched    | bigint                   | Number of rows randomly scanned                              |
+| n_tuples_returned   | bigint                   | Number of rows sequentially scanned                          |
+| n_tuples_inserted   | bigint                   | Number of rows inserted                                      |
+| n_tuples_updated    | bigint                   | Number of rows updated                                       |
+| n_tuples_deleted    | bigint                   | Number of rows deleted                                       |
+| n_blocks_fetched    | bigint                   | Number of buffer block access times                          |
+| n_blocks_hit        | bigint                   | Number of buffer block hits                                  |
+| n_soft_parse        | bigint                   | Number of soft parsing times                                 |
+| n_hard_parse        | bigint                   | Number of hard parsing times                                 |
+| db_time             | bigint                   | Valid DB time, which is accumulated if multiple threads are involved (unit: μs) |
+| cpu_time            | bigint                   | CPU time (unit: μs)                                          |
+| execution_time      | bigint                   | Execution time in the executor (unit: μs)                    |
+| parse_time          | bigint                   | SQL parsing time (unit: μs)                                  |
+| plan_time           | bigint                   | SQL plan generation time (unit: μs)                          |
+| rewrite_time        | bigint                   | SQL rewriting time (unit: μs)                                |
+| pl_execution_time   | bigint                   | Execution time of PL/pgSQL (unit: μs)                        |
+| pl_compilation_time | bigint                   | Compilation time of PL/pgSQL (unit: μs)                      |
+| net_send_time       | bigint                   | Network time (unit: μs)                                      |
+| data_io_time        | bigint                   | I/O time (unit: μs)                                          |
+| last_updated        | timestamp with time zone | Last time when the statement was updated                     |
+| sort_count          | bigint                   | Sorting count                                                |
+| sort_time           | bigint                   | Sorting duration (unit: μs)                                  |
+| sort_mem_used       | bigint                   | Size of work memory used during sorting (unit: KB)           |
+| sort_spill_count    | bigint                   | Count of file writing when data is flushed to disks during sorting |
+| sort_spill_size     | bigint                   | File size used when data is flushed to disks during sorting (unit: KB) |
+| hash_count          | bigint                   | Hashing count                                                |
+| hash_time           | bigint                   | Hashing duration (unit: μs)                                  |
+| hash_mem_used       | bigint                   | Size of work memory used during hashing (unit: KB)           |
+| hash_spill_count    | bigint                   | Count of file writing when data is flushed to disks during hashing |
+| hash_spill_size     | bigint                   | File size used when data is flushed to disks during hashing (unit: KB) |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/SUMMARY_STATEMENT_COUNT.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/SUMMARY_STATEMENT_COUNT.md
new file mode 100644
index 0000000000000000000000000000000000000000..a3fc67530d2e55a90216fccd2e5c945ae9adcede
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/SUMMARY_STATEMENT_COUNT.md
@@ -0,0 +1,40 @@
+---
+title: SUMMARY_STATEMENT_COUNT
+summary: SUMMARY_STATEMENT_COUNT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STATEMENT_COUNT
+
+**SUMMARY_STATEMENT_COUNT** displays statistics about five types of running statements (**SELECT**, **INSERT**, **UPDATE**, **DELETE**, and **MERGE INTO**) as well as DDL, DML, and DCL statements on all nodes (database nodes) of the database.
+
+**Table 1** SUMMARY_STATEMENT_COUNT columns
+
+| **Name**            | **Type** | **Description**                                           |
+| :------------------ | :------- | :-------------------------------------------------------- |
+| user_name           | text     | Username                                                  |
+| select_count        | numeric  | Statistical result of the **SELECT** statement            |
+| update_count        | numeric  | Statistical result of the **UPDATE** statement            |
+| insert_count        | numeric  | Statistical result of the **INSERT** statement            |
+| delete_count        | numeric  | Statistical result of the **DELETE** statement            |
+| mergeinto_count     | numeric  | Statistical result of the **MERGE INTO** statement        |
+| ddl_count           | numeric  | Number of DDL statements                                  |
+| dml_count           | numeric  | Number of DML statements                                  |
+| dcl_count           | numeric  | Number of DCL statements                                  |
+| total_select_elapse | numeric  | Total response time of **SELECT** statements (unit: μs)   |
+| avg_select_elapse   | bigint   | Average response time of **SELECT** statements (unit: μs) |
+| max_select_elapse   | bigint   | Maximum response time of **SELECT** statements (unit: μs) |
+| min_select_elapse   | bigint   | Minimum response time of **SELECT** statements (unit: μs) |
+| total_update_elapse | numeric  | Total response time of **UPDATE** statements (unit: μs)   |
+| avg_update_elapse   | bigint   | Average response time of **UPDATE** statements (unit: μs) |
+| max_update_elapse   | bigint   | Maximum response time of **UPDATE** statements (unit: μs) |
+| min_update_elapse   | bigint   | Minimum response time of **UPDATE** statements (unit: μs) |
+| total_insert_elapse | numeric  | Total response time of **INSERT** statements (unit: μs)   |
+| avg_insert_elapse   | bigint   | Average response time of **INSERT** statements (unit: μs) |
+| max_insert_elapse   | bigint   | Maximum response time of **INSERT** statements (unit: μs) |
+| min_insert_elapse   | bigint   | Minimum response time of **INSERT** statements (unit: μs) |
+| total_delete_elapse | numeric  | Total response time of **DELETE** statements (unit: μs)   |
+| avg_delete_elapse   | bigint   | Average response time of **DELETE** statements (unit: μs) |
+| max_delete_elapse   | bigint   | Maximum response time of **DELETE** statements (unit: μs) |
+| min_delete_elapse   | bigint   | Minimum response time of **DELETE** statements (unit: μs) |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/rto/global_rto_status.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/rto/global_rto_status.md
new file mode 100644
index 0000000000000000000000000000000000000000..89225dc002e00caf0c80be0b7ae3f2aedc98449b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/rto/global_rto_status.md
@@ -0,0 +1,19 @@
+---
+title: global_rto_status
+summary: global_rto_status
+author: Guo Huan
+date: 2021-11-15
+---
+
+# global_rto_status
+
+Displays log flow control information about the primary and standby nodes (except the current node and standby DNs).
+
+Return type: record
+
+**Table 1** remote_rto_status parameters
+
+| Parameter | Type | Description                                                  |
+| :-------- | :--- | :----------------------------------------------------------- |
+| node_name | text | Node name (including the primary and standby nodes)          |
+| rto_info  | text | Flow control information, including the current log flow control time (unit: second) of the standby node, the expected flow control time (unit: second) specified by the GUC parameter, and the primary node sleep time (unit: μs) required to reach the expectation |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_MEMORY.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_MEMORY.md
new file mode 100644
index 0000000000000000000000000000000000000000..0e20669ad937b9196ecc70539a815f86e5c3588e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_MEMORY.md
@@ -0,0 +1,20 @@
+---
+title: GLOBAL_SESSION_MEMORY
+summary: GLOBAL_SESSION_MEMORY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_SESSION_MEMORY
+
+**GLOBAL_SESSION_MEMORY** collects statistics about memory usage at the session level on each node in the unit of MB, including all the memory allocated to MogDB and stream threads on DNs for jobs currently executed by users.
+
+**Table 1** GLOBAL_SESSION_MEMORY columns
+
+| **Name**  | **Type** | **Description**                                              |
+| :-------- | :------- | :----------------------------------------------------------- |
+| node_name | name     | Node name                                                    |
+| sessid    | text     | Thread start time and ID                                     |
+| init_mem  | integer  | Memory allocated to the currently executed job before the job enters the executor |
+| used_mem  | integer  | Memory allocated to the currently executed job               |
+| peak_mem  | integer  | Peak memory allocated to the currently executed job          |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_MEMORY_DETAIL.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_MEMORY_DETAIL.md
new file mode 100644
index 0000000000000000000000000000000000000000..9045483560023c6acc6a33ad3fb1b940890e6dd0
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_MEMORY_DETAIL.md
@@ -0,0 +1,24 @@
+---
+title: GLOBAL_SESSION_MEMORY_DETAIL
+summary: GLOBAL_SESSION_MEMORY_DETAIL
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_SESSION_MEMORY_DETAIL
+
+**GLOBAL_SESSION_MEMORY_DETAIL** collects statistics about thread memory usage on each node by MemoryContext node.
+
+**Table 1** GLOBAL_SESSION_MEMORY_DETAIL columns
+
+| **Name**    | **Type** | **Description**                         |
+| :---------- | :------- | :-------------------------------------- |
+| node_name   | name     | Node name                               |
+| sessid      | text     | Thread start time and ID                |
+| sesstype    | text     | Thread name                             |
+| contextname | text     | Name of the memory context              |
+| level       | smallint | Level of memory context importance      |
+| parent      | text     | Name of the parent memory context       |
+| totalsize   | bigint   | Size of the applied memory (unit: byte) |
+| freesize    | bigint   | Size of the idle memory (unit: byte)    |
+| usedsize    | bigint   | Size of the used memory (unit: byte)    |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_STAT.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_STAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..30825ac6eaace996d0a05fe866b8600ac29cf974
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_STAT.md
@@ -0,0 +1,21 @@
+---
+title: GLOBAL_SESSION_STAT
+summary: GLOBAL_SESSION_STAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_SESSION_STAT
+
+**GLOBAL_SESSION_STAT** collects statistics about session status on each node based on session threads or the **AutoVacuum** thread.
+
+**Table 1** GLOBAL_SESSION_STAT columns
+
+| **Name**  | **Type** | **Description**                 |
+| :-------- | :------- | :------------------------------ |
+| node_name | name     | Node name                       |
+| sessid    | text     | Thread start time and ID        |
+| statid    | integer  | Statistics ID                   |
+| statname  | text     | Name of the statistics session  |
+| statunit  | text     | Unit of the statistics session  |
+| value     | bigint   | Value of the statistics session |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_STAT_ACTIVITY.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_STAT_ACTIVITY.md
new file mode 100644
index 0000000000000000000000000000000000000000..3d6745675a338289e94815dd6ba10af87c3ac9a4
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_STAT_ACTIVITY.md
@@ -0,0 +1,35 @@
+---
+title: GLOBAL_SESSION_STAT_ACTIVITY
+summary: GLOBAL_SESSION_STAT_ACTIVITY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_SESSION_STAT_ACTIVITY
+
+**GLOBAL_SESSION_STAT_ACTIVITY** displays information about threads that are running on each node in MogDB.
+
+**Table 1** GLOBAL_SESSION_STAT_ACTIVITY columns
+
+| **Name**         | **Type**                | **Description**                                              |
+| :--------------- | :---------------------- | :----------------------------------------------------------- |
+| coorname         | text                    | Node name                                                    |
+| datid            | oid                     | OID of the database that the user session connects to in the backend |
+| datname          | text                    | Name of the database that the user session connects to in the backend |
+| pid              | bigint                  | Thread ID of the backend                                     |
+| usesysid         | oid                     | OID of the user logged in to the backend                     |
+| usename          | text                    | Name of the user logged in to the backend                    |
+| application_name | text                    | Name of the application connected to the backend             |
+| client_addr      | inet                    | IP address of the client connected to the backend. If this column is null, it indicates either the client is connected via a Unix socket on the server or this is an internal process, such as autovacuum. |
+| client_hostname  | text                    | Host name of the connected client, as reported by a reverse DNS lookup of **client\_addr**. This column will be non-null only for IP connections and only when **log_hostname** is enabled. |
+| client_port      | integer                 | TCP port number that the client uses for communication with this backend (**-1** if a Unix socket is used) |
+| backend_start    | timestampwith time zone | Time when this process was started, that is, when the client connected to the server |
+| xact_start       | timestampwith time zone | Time when current transaction was started (null if no transaction is active). If the current query is the first of its transaction, the value of this column is the same as that of the **query_start** column. |
+| query_start      | timestampwith time zone | Time when the currently active query was started, or time when the last query was started if **state** is not **active** |
+| state_change     | timestampwith time zone | Time when the **state** was last changed                     |
+| waiting          | boolean                 | Whether the backend is currently waiting on a lock. If yes, the value is **true**. |
+| enqueue          | text                    | Unsupported currently                                        |
+| state            | text                    | Overall status of this backend. The value must be one of the following:<br/>- **active**: The backend is executing a query.<br/>- **idle**: The backend is waiting for a new client command.<br/>- **idle in transaction**: The backend is in a transaction, but is not currently executing a query.<br/>- **idle in transaction (aborted)**: This state is similar to **idle in transaction**, except that one of the statements in the transaction caused an error.<br/>- **fastpath function call**: The backend is executing a fast-path function.<br/>- **disabled**: This state is reported if **track_activities** is disabled in this backend.<br/>NOTE:<br/>Common users can view their own session status only. The state information of other accounts is empty. For example, after user **judy** is connected to the database, the state information of user **joe** and the initial user **omm** in **pg_stat_activity** is empty.<br/>postgres=# SELECT datname, usename, usesysid,state,pid FROM pg_stat_activity;<br/>datname \| usename \| usesysid \| state \| pid<br/>----+---+----+---+------<br/>postgres \| omm \| 10 \| \|139968752121616<br/>postgres \| omm \| 10 \| \|139968903116560<br/>db_tpcds \| judy \| 16398 \| active \|139968391403280<br/>postgres \| omm \| 10 \| \|139968643069712<br/>postgres \| omm \| 10 \| \|139968680818448<br/>postgres \| joe \| 16390 \| \|139968563377936<br/>(6 rows) |
+| resource_pool    | name                    | Resource pool used by the user                               |
+| query_id         | bigint                  | ID of a query                                                |
+| query            | text                    | Text of this backend's most recent query. If **state** is **active**, this column shows the ongoing query. In all other states, it shows the last query that was executed. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_TIME.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_TIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..e13b2dd85be93df3fca7f3d505236a43fa6eacad
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_TIME.md
@@ -0,0 +1,20 @@
+---
+title: GLOBAL_SESSION_TIME
+summary: GLOBAL_SESSION_TIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_SESSION_TIME
+
+**GLOBAL_SESSION_TIME** collects statistics about the running time of session threads and time consumed in each execution phase on each node.
+
+**Table 1** GLOBAL_SESSION_TIME columns
+
+| **Name**  | **Type** | **Description**          |
+| :-------- | :------- | :----------------------- |
+| node_name | name     | Node name                |
+| sessid    | text     | Thread start time and ID |
+| stat_id   | integer  | Statistics ID            |
+| stat_name | text     | Session type             |
+| value     | bigint   | Session value            |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_THREADPOOL_STATUS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_THREADPOOL_STATUS.md
new file mode 100644
index 0000000000000000000000000000000000000000..9984f7c9789f14f80f4a768d228a4027b41ea096
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_THREADPOOL_STATUS.md
@@ -0,0 +1,10 @@
+---
+title: GLOBAL_THREADPOOL_STATUS
+summary: GLOBAL_THREADPOOL_STATUS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_THREADPOOL_STATUS
+
+**GLOBAL_THREADPOOL_STATUS** displays the status of worker threads and sessions in thread pools on all nodes. Columns in this view are the same as those in LOCAL_THREADPOOL_STATUS -> Table 1.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_THREAD_WAIT_STATUS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_THREAD_WAIT_STATUS.md
new file mode 100644
index 0000000000000000000000000000000000000000..500882417a219550398f9586235640834275ea80
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_THREAD_WAIT_STATUS.md
@@ -0,0 +1,31 @@
+---
+title: GLOBAL_THREAD_WAIT_STATUS
+summary: GLOBAL_THREAD_WAIT_STATUS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_THREAD_WAIT_STATUS
+
+**GLOBAL_THREAD_WAIT_STATUS** allows you to test the block waiting status of backend threads and auxiliary threads on all nodes. For details about events, see Appendices-Table 1, Appendices-Table 2, Appendices-Table 3, and Appendices-Table 4.
+
+In **GLOBAL_THREAD_WAIT_STATUS**, you can see all the call hierarchy relationships between threads of the SQL statements on all nodes in MogDB, and the block waiting status for each thread. With this view, you can easily locate the causes of process hang and similar issues.
+
+The definitions of **GLOBAL_THREAD_WAIT_STATUS** and **THREAD_WAIT_STATUS** are the same, because the **GLOBAL_THREAD_WAIT_STATUS** view is essentially the query summary of the **THREAD_WAIT_STATUS** view on each node in MogDB.
+
+**Table 1** GLOBAL_THREAD_WAIT_STATUS columns
+
+| **Name**    | **Type** | **Description**                                              |
+| :---------- | :------- | :----------------------------------------------------------- |
+| node_name   | text     | Node name                                                    |
+| db_name     | text     | Database name                                                |
+| thread_name | text     | Thread name                                                  |
+| query_id    | bigint   | Query ID. The value of this column is the same as that of **debug_query_id**. |
+| tid         | bigint   | Thread ID of the current thread                              |
+| sessionid   | bigint   | Session ID                                                   |
+| lwtid       | integer  | Lightweight thread ID of the current thread                  |
+| psessionid  | bigint   | Parent thread of the streaming thread                        |
+| tlevel      | integer  | Level of the streaming thread                                |
+| smpid       | integer  | Concurrent thread ID                                         |
+| wait_status | text     | Waiting status of the current thread. For details about the waiting status, see Appendices-Table 2. |
+| wait_event  | text     | If **wait\_status** is **acquire lock**, **acquire lwlock**, or **wait io**, this column describes the lock, lightweight lock, and I/O information, respectively. If **wait\_status** is not any of the three values, this column is empty. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/LOCAL_ACTIVE_SESSION.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/LOCAL_ACTIVE_SESSION.md
new file mode 100644
index 0000000000000000000000000000000000000000..f9f0759be7d58277e6722e6c4e1b5ead464b36a9
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/LOCAL_ACTIVE_SESSION.md
@@ -0,0 +1,43 @@
+---
+title: LOCAL_ACTIVE_SESSION
+summary: LOCAL_ACTIVE_SESSION
+author: Guo Huan
+date: 2021-11-15
+---
+
+# LOCAL_ACTIVE_SESSION
+
+The **LOCAL_ACTIVE_SESSION** view displays the samples in the **ACTIVE SESSION PROFILE** memory on this node.
+
+**表 1** LOCAL_ACTIVE_SESSION field
+
+| Name                  | Type                     | Description                                                  |
+| :-------------------- | :----------------------- | :----------------------------------------------------------- |
+| sampleid              | bigint                   | Sample ID.                                                   |
+| sample_time           | timestamp with time zone | The time of sampling.                                        |
+| need_flush_sample     | boolean                  | Whether the sample needs to be refreshed on disk.            |
+| databaseid            | oid                      | Database ID.                                                 |
+| thread_id             | bigint                   | Thread ID.                                                   |
+| sessionid             | bigint                   | Session ID.                                                  |
+| start_time            | timestamp with time zone | The start time of the session.                               |
+| event                 | text                     | The specific event name.                                     |
+| lwtid                 | integer                  | The lightweight thread ID of the current thread.             |
+| psessionid            | bigint                   | The parent thread of the streaming thread.                   |
+| tlevel                | integer                  | The level of streaming threads. Correspond to the level (ID) of the execution plan. |
+| smpid                 | integer                  | The parallel ID of the parallel thread in the smp execution mode. |
+| userid                | oid                      | Session user ID。                                            |
+| application_name      | text                     | The name of the application.                                 |
+| client_addr           | inet                     | The address of the client.                                   |
+| client_hostname       | text                     | The name of the client.                                      |
+| client_port           | integer                  | The TCP port number used by the client to communicate with the backend. |
+| query_id              | bigint                   | debug query id。                                             |
+| unique_query_id       | bigint                   | unique query id。                                            |
+| user_id               | oid                      | The user_id in the key of the unique query.                  |
+| cn_id                 | integer                  | cn id, on the DN, it means the ID of the node that issued the unique sql, and the cn_id in the key of the unique query. |
+| unique_query          | text                     | UniqueSQL text string after normalization.                   |
+| locktag               | text                     | The session waiting lock information can be parsed by locktag_decode. |
+| lockmode              | text                     | The session waits for the lock mode.                         |
+| block_sessionid       | bigint                   | If the session is waiting for a lock, block the session ID from acquiring the lock. |
+| final_block_sessionid | bigint                   | Indicates the source blocking session ID.                    |
+| wait_status           | text                     | Describe more detailed information about the event column.   |
+| global_sessionid      | text                     | Global session ID.                                           |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/LOCAL_THREADPOOL_STATUS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/LOCAL_THREADPOOL_STATUS.md
new file mode 100644
index 0000000000000000000000000000000000000000..bab312aa98bb9d96061341d4f4247323e03ff664
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/LOCAL_THREADPOOL_STATUS.md
@@ -0,0 +1,22 @@
+---
+title: LOCAL_THREADPOOL_STATUS
+summary: LOCAL_THREADPOOL_STATUS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# LOCAL_THREADPOOL_STATUS
+
+**LOCAL_THREADPOOL_STATUS** displays the status of worker threads and sessions in a thread pool. This view is valid only when **enable_thread_pool** is set to **on**.
+
+**Table 1** LOCAL_THREADPOOL_STATUS columns<a id="LOCAL_THREADPOOL_STATUS"> </a>
+
+| Name            | Type    | Description                                                  |
+| :-------------- | :------ | :----------------------------------------------------------- |
+| node_name       | text    | Database process name                                        |
+| group_id        | integer | ID of the thread pool group                                  |
+| bind_numa_id    | integer | NUMA ID to which the thread pool group is bound              |
+| bind_cpu_number | integer | Information about the CPU to which the thread pool group is bound. If no CPUs are bound, the value is **NULL**. |
+| listener        | integer | Number of listener threads in the thread pool group          |
+| worker_info     | text    | Information about threads in the thread pool, including:<br/>- **default**: Number of initial threads in the thread pool group<br/>- **new**: Number of new threads in the thread pool group<br/>- **expect**: Expected number of threads in the thread pool group<br/>- **actual**: Actual number of threads in the thread pool group<br/>- **idle**: Number of idle threads in the thread pool group<br/>- **pending**: Number of pending threads in the thread pool group |
+| session_info    | text    | Information about sessions in the thread pool, including:<br/>- **total**: Total number of sessions in the thread pool group<br/>- **waiting**: Number of sessions pending scheduling in the thread pool group<br/>- **running**: Number of running sessions in the thread pool group<br/>- **idle**: Number of idle sessions in the thread pool group |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_CPU_RUNTIME.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_CPU_RUNTIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..72d09584b74884b974abb759e4fb9451b6e82be6
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_CPU_RUNTIME.md
@@ -0,0 +1,25 @@
+---
+title: SESSION_CPU_RUNTIME
+summary: SESSION_CPU_RUNTIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SESSION_CPU_RUNTIME
+
+**SESSION_CPU_RUNTIME** displays load management information about CPU usage of ongoing complex jobs executed by the current user.
+
+**Table 1** SESSION_CPU_RUNTIME columns
+
+| Name           | Type                     | Description                                                  |
+| :------------- | :----------------------- | :----------------------------------------------------------- |
+| datid          | oid                      | OID of the database that this backend is connected to        |
+| usename        | name                     | Name of the user logged in to the backend                    |
+| pid            | bigint                   | Thread ID of the backend                                     |
+| start_time     | timestamp with time zone | Time when the statement starts to be executed                |
+| min_cpu_time   | bigint                   | Minimum CPU time of the statement across the database nodes, in ms |
+| max_cpu_time   | bigint                   | Maximum CPU time of the statement across the database nodes, in ms |
+| total_cpu_time | bigint                   | Total CPU time of the statement across the database nodes, in ms |
+| query          | text                     | Statement being executed                                     |
+| node_group     | text                     | Logical MogDB of the user running the statement              |
+| top_cpu_dn     | text                     | Top N CPU usage                                              |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_MEMORY.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_MEMORY.md
new file mode 100644
index 0000000000000000000000000000000000000000..efa8dfe0e46155a887fedee6233c545b53fedfb5
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_MEMORY.md
@@ -0,0 +1,19 @@
+---
+title: SESSION_MEMORY
+summary: SESSION_MEMORY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SESSION_MEMORY
+
+**SESSION_MEMORY** collects statistics about memory usage at the session level in the unit of MB, including all the memory allocated to MogDB and stream threads on DNs for jobs currently executed by users.
+
+**Table 1** SESSION_MEMORY columns
+
+| Name     | Type    | Description                                                  |
+| :------- | :------ | :----------------------------------------------------------- |
+| sessid   | text    | Thread start time and ID                                     |
+| init_mem | integer | Memory allocated to the currently executed job before the job enters the executor |
+| used_mem | integer | Memory allocated to the currently executed job               |
+| peak_mem | integer | Peak memory allocated to the currently executed job          |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_MEMORY_DETAIL.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_MEMORY_DETAIL.md
new file mode 100644
index 0000000000000000000000000000000000000000..c1c10572ee56a3626204bc4a049fd761ff04cd59
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_MEMORY_DETAIL.md
@@ -0,0 +1,23 @@
+---
+title: SESSION_MEMORY_DETAIL
+summary: SESSION_MEMORY_DETAIL
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SESSION_MEMORY_DETAIL
+
+**SESSION_MEMORY_DETAIL** collects statistics about thread memory usage by MemoryContext node.
+
+**Table 1** SESSION_MEMORY_DETAIL columns
+
+| Name        | Type     | Description                             |
+| :---------- | :------- | :-------------------------------------- |
+| sessid      | text     | Thread start time and ID                |
+| sesstype    | text     | Thread name                             |
+| contextname | text     | Name of the memory context              |
+| level       | smallint | Level of memory context importance      |
+| parent      | text     | Name of the parent memory context       |
+| totalsize   | bigint   | Size of the applied memory (unit: byte) |
+| freesize    | bigint   | Size of the idle memory (unit: byte)    |
+| usedsize    | bigint   | Size of the used memory (unit: byte)    |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_MEMORY_RUNTIME.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_MEMORY_RUNTIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..6cf290574e1dddee6fe655da67716e386aadd86b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_MEMORY_RUNTIME.md
@@ -0,0 +1,25 @@
+---
+title: SESSION_MEMORY_RUNTIME
+summary: SESSION_MEMORY_RUNTIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SESSION_MEMORY_RUNTIME
+
+**SESSION_MEMORY_RUNTIME** displays load management information about memory usage of ongoing complex jobs executed by the current user.
+
+**Table 1** SESSION_MEMORY_RUNTIME columns
+
+| Name            | Type                     | Description                                                  |
+| :-------------- | :----------------------- | :----------------------------------------------------------- |
+| datid           | oid                      | OID of the database that this backend is connected to        |
+| usename         | name                     | Name of the user logged in to the backend                    |
+| pid             | bigint                   | Thread ID of the backend                                     |
+| start_time      | timestamp with time zone | Time when the statement starts to be executed                |
+| min_peak_memory | integer                  | Minimum memory peak of the statement across the database nodes, in MB |
+| max_peak_memory | integer                  | Maximum memory peak of the statement across the database nodes, in MB |
+| spill_info      | text                     | Information about statement spill to the database nodes<br/>- **None**: The statement has not been spilled to disks on the database nodes.<br/>- **All**: The statement has been spilled to disks on the database nodes.<br/>- **[a:b]**: The statement has been spilled to disks on **a** of **b** database nodes. |
+| query           | text                     | Statement being executed                                     |
+| node_group      | text                     | Logical MogDB of the user running the statement              |
+| top_mem_dn      | text                     | Top N memory usage                                           |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_STAT.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_STAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..3dae4edd62c67a3fe87e3864b79db8bab35b5cbd
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_STAT.md
@@ -0,0 +1,20 @@
+---
+title: SESSION_STAT
+summary: SESSION_STAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SESSION_STAT
+
+**SESSION_STAT** collects statistics about session status on the current node based on session threads or the **AutoVacuum** thread.
+
+**Table 1** SESSION_STAT columns
+
+| Name     | Type    | Description                     |
+| :------- | :------ | :------------------------------ |
+| sessid   | text    | Thread start time and ID        |
+| statid   | integer | Statistics ID                   |
+| statname | text    | Name of the statistics session  |
+| statunit | text    | Unit of the statistics session  |
+| value    | bigint  | Value of the statistics session |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_STAT_ACTIVITY.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_STAT_ACTIVITY.md
new file mode 100644
index 0000000000000000000000000000000000000000..cbf40ced8197845054f38b0e149e5bcbafd42299
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_STAT_ACTIVITY.md
@@ -0,0 +1,34 @@
+---
+title: SESSION_STAT_ACTIVITY
+summary: SESSION_STAT_ACTIVITY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SESSION_STAT_ACTIVITY
+
+**SESSION_STAT_ACTIVITY** displays information about threads that are running on the current node.
+
+**Table 1** SESSION_STAT_ACTIVITY columns
+
+| **Name**         | **Type**                | **Description**                                              |
+| :--------------- | :---------------------- | :----------------------------------------------------------- |
+| datid            | oid                     | OID of the database that the user session connects to in the backend |
+| datname          | name                    | Name of the database that the user session connects to in the backend |
+| pid              | bigint                  | Thread ID of the backend                                     |
+| usesysid         | oid                     | OID of the user logged in to the backend                     |
+| usename          | name                    | Name of the user logged in to the backend                    |
+| application_name | text                    | Name of the application connected to the backend             |
+| client_addr      | inet                    | IP address of the client connected to the backend. If this column is null, it indicates either the client is connected via a Unix socket on the server or this is an internal process, such as autovacuum. |
+| client_hostname  | text                    | Host name of the connected client, as reported by a reverse DNS lookup of **client\_addr**. This column will be non-null only for IP connections and only when **log_hostname** is enabled. |
+| client_port      | integer                 | TCP port number that the client uses for communication with this backend (**-1** if a Unix socket is used) |
+| backend_start    | timestampwith time zone | Time when this process was started, that is, when the client connected to the server |
+| xact_start       | timestampwith time zone | Time when current transaction was started (null if no transaction is active). If the current query is the first of its transaction, the value of this column is the same as that of the **query_start** column. |
+| query_start      | timestampwith time zone | Time when the currently active query was started, or time when the last query was started if **state** is not **active** |
+| state_change     | timestampwith time zone | Time when the **state** was last changed                     |
+| waiting          | boolean                 | Whether the backend is currently waiting on a lock. If yes, the value is **true**. |
+| enqueue          | text                    | Unsupported currently                                        |
+| state            | text                    | Overall status of this backend. The value must be one of the following:<br/>- **active**: The backend is executing a query.<br/>- **idle**: The backend is waiting for a new client command.<br/>- **idle in transaction**: The backend is in a transaction, but is not currently executing a query.<br/>- **idle in transaction (aborted)**: This state is similar to **idle in transaction**, except that one of the statements in the transaction caused an error.<br/>- **fastpath function call**: The backend is executing a fast-path function.<br/>- **disabled**: This state is reported if **track_activities** is disabled in this backend.<br/>NOTE:<br/>Common users can view their own session status only. The state information of other accounts is empty. For example, after user **judy** is connected to the database, the state information of user **joe** and the initial user **omm** in **pg_stat_activity** is empty.<br/>postgres=# SELECT datname, usename, usesysid,state,pid FROM pg_stat_activity;<br/>datname \| usename \| usesysid \| state \| pid<br/>----+---+----+---+------<br/>postgres \| omm \| 10 \| \|139968752121616<br/>postgres \| omm \| 10 \| \|139968903116560<br/>db_tpcds \| judy \| 16398 \| active \|139968391403280<br/>postgres \| omm \| 10 \| \|139968643069712<br/>postgres \| omm \| 10 \| \|139968680818448<br/>postgres \| joe \| 16390 \| \|139968563377936<br/>(6 rows) |
+| resource_pool    | name                    | Resource pool used by the user                               |
+| query_id         | bigint                  | ID of a query                                                |
+| query            | text                    | Text of this backend's most recent query. If **state** is **active**, this column shows the ongoing query. In all other states, it shows the last query that was executed. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_TIME.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_TIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..594f33fd04be5ea08b63a6a710be37d60ac87932
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_TIME.md
@@ -0,0 +1,19 @@
+---
+title: SESSION_TIME
+summary: SESSION_TIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SESSION_TIME
+
+**SESSION_TIME** collects statistics about the running time of session threads and time consumed in each execution phase on the current node.
+
+**Table 1** SESSION_TIME columns
+
+| Name      | Type    | Description              |
+| :-------- | :------ | :----------------------- |
+| sessid    | text    | Thread start time and ID |
+| stat_id   | integer | Statistics ID            |
+| stat_name | text    | Session type name        |
+| value     | bigint  | Session value            |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/STATEMENT_IOSTAT_COMPLEX_RUNTIME.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/STATEMENT_IOSTAT_COMPLEX_RUNTIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..5919a5edd11f4867586a3daab90406d162e4b7f3
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/STATEMENT_IOSTAT_COMPLEX_RUNTIME.md
@@ -0,0 +1,24 @@
+---
+title: STATEMENT_IOSTAT_COMPLEX_RUNTIME
+summary: STATEMENT_IOSTAT_COMPLEX_RUNTIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATEMENT_IOSTAT_COMPLEX_RUNTIME
+
+**STATEMENT_IOSTAT_COMPLEX_RUNTIME** displays I/O load management information about ongoing jobs executed by the current user. IOPS is counted by ones for column storage and by 10 thousands for row storage.
+
+**Table 1** STATEMENT_IOSTAT_COMPLEX_RUNTIME columns
+
+| Name        | Type    | Description                                               |
+| :---------- | :------ | :-------------------------------------------------------- |
+| query_id    | bigint  | Job ID                                                    |
+| mincurriops | integer | Minimum I/O of the job across database nodes              |
+| maxcurriops | integer | Maximum I/O of the job across database nodes              |
+| minpeakiops | integer | Minimum peak I/O of the current job across database nodes |
+| maxpeakiops | integer | Maximum peak I/O of the current job across database nodes |
+| io_limits   | integer | **io_limits** set for the job                             |
+| io_priority | text    | **io_priority** set for the job                           |
+| query       | text    | Job                                                       |
+| node_group  | text    | Logical MogDB of the user running the job                 |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/THREAD_WAIT_STATUS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/THREAD_WAIT_STATUS.md
new file mode 100644
index 0000000000000000000000000000000000000000..11191b184a2a346ed48414a7502a2d23852f68f0
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/THREAD_WAIT_STATUS.md
@@ -0,0 +1,27 @@
+---
+title: THREAD_WAIT_STATUS
+summary: THREAD_WAIT_STATUS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# THREAD_WAIT_STATUS
+
+**THREAD_WAIT_STATUS** allows you to test the block waiting status of the backend thread and auxiliary thread in the current instance. For details about events, see Appendices-[Table 1](table-1), Appendices-[Table 2](table-2), Appendices-[Table 3](table-3), and Appendices-[Table 4](table-4).
+
+**Table 1** THREAD_WAIT_STATUS columns
+
+| **Name**    | **Type** | **Description**                                              |
+| :---------- | :------- | :----------------------------------------------------------- |
+| node_name   | text     | Database process name                                        |
+| db_name     | text     | Database name                                                |
+| thread_name | text     | Thread name                                                  |
+| query_id    | bigint   | Query ID. The value of this column is the same as that of **debug_query_id**. |
+| tid         | bigint   | Thread ID of the current thread                              |
+| sessionid   | bigint   | Session ID                                                   |
+| lwtid       | integer  | Lightweight thread ID of the current thread                  |
+| psessionid  | bigint   | Parent thread of the streaming thread                        |
+| tlevel      | integer  | Level of the streaming thread                                |
+| smpid       | integer  | Concurrent thread ID                                         |
+| wait_status | text     | Waiting status of the current thread. For details about the waiting status, see Appendices-[Table 1](table-1). |
+| wait_event  | text     | If **wait\_status** is **acquire lock**, **acquire lwlock**, or **wait io**, this column describes the lock, lightweight lock, and I/O information, respectively. If **wait\_status** is not any of the three values, this column is empty. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/GLOBAL_TRANSACTIONS_PREPARED_XACTS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/GLOBAL_TRANSACTIONS_PREPARED_XACTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..1361e66497b9db71af15a6abf2dd5421b30f5e11
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/GLOBAL_TRANSACTIONS_PREPARED_XACTS.md
@@ -0,0 +1,20 @@
+---
+title: GLOBAL_TRANSACTIONS_PREPARED_XACTS
+summary: GLOBAL_TRANSACTIONS_PREPARED_XACTS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_TRANSACTIONS_PREPARED_XACTS
+
+**GLOBAL_TRANSACTIONS_PREPARED_XACTS** displays information about transactions that are currently prepared for two-phase commit on each node.
+
+**Table 1** GLOBAL_TRANSACTIONS_PREPARED_XACTS columns
+
+| **Name**    | **Type**                 | **Description**                                              |
+| :---------- | :----------------------- | :----------------------------------------------------------- |
+| transaction | xid                      | Numeric transaction identifier of the prepared transaction   |
+| gid         | text                     | Global transaction identifier that was assigned to the transaction |
+| prepared    | timestamp with time zone | Time at which the transaction is prepared for commit         |
+| owner       | name                     | Name of the user that executes the transaction               |
+| database    | name                     | Name of the database in which the transaction is executed    |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/GLOBAL_TRANSACTIONS_RUNNING_XACTS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/GLOBAL_TRANSACTIONS_RUNNING_XACTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..2997db8f9ebc84f63e1cc9abe2e1b653f359a874
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/GLOBAL_TRANSACTIONS_RUNNING_XACTS.md
@@ -0,0 +1,25 @@
+---
+title: GLOBAL_TRANSACTIONS_RUNNING_XACTS
+summary: GLOBAL_TRANSACTIONS_RUNNING_XACTS
+author: Guo Huan
+date: 2021-11-15
+---
+
+# GLOBAL_TRANSACTIONS_RUNNING_XACTS
+
+**GLOBAL_TRANSACTIONS_RUNNING_XACTS** displays information about the running transactions on each node in the cluster.
+
+**Table 1** GLOBAL_TRANSACTIONS_RUNNING_XACTS columns
+
+| **Name**    | **Type** | **Description**                                              |
+| :---------- | :------- | :----------------------------------------------------------- |
+| handle      | integer  | Handle corresponding to the transaction in GTM               |
+| gxid        | xid      | Transaction ID                                               |
+| state       | tinyint  | Transaction status (**3**: prepared or **0**: starting)      |
+| node        | text     | Node name                                                    |
+| xmin        | xid      | Minimum transaction ID on the node                           |
+| vacuum      | boolean  | Whether the current transaction is lazy vacuum               |
+| timeline    | bigint   | Number of database restarts                                  |
+| prepare_xid | xid      | Transaction ID in the **prepared** state. If the status is not **prepared**, the value is **0**. |
+| pid         | bigint   | Thread ID corresponding to the transaction                   |
+| next_xid    | xid      | Transaction ID sent from a CN to a DN                        |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/SUMMARY_TRANSACTIONS_PREPARED_XACTS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/SUMMARY_TRANSACTIONS_PREPARED_XACTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..f41197036f129d6d2acdfa16d6ea8a3258219a5e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/SUMMARY_TRANSACTIONS_PREPARED_XACTS.md
@@ -0,0 +1,20 @@
+---
+title: SUMMARY_TRANSACTIONS_PREPARED_XACTS
+summary: SUMMARY_TRANSACTIONS_PREPARED_XACTS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_TRANSACTIONS_PREPARED_XACTS
+
+**SUMMARY_TRANSACTIONS_PREPARED_XACTS** displays information about transactions that are currently prepared for two-phase commit on the primary database node in MogDB.
+
+**Table 1** SUMMARY_TRANSACTIONS_PREPARED_XACTS columns
+
+| **Name**    | **Type**                 | **Description**                                              |
+| :---------- | :----------------------- | :----------------------------------------------------------- |
+| transaction | xid                      | Numeric transaction identifier of the prepared transaction   |
+| gid         | text                     | Global transaction identifier that was assigned to the transaction |
+| prepared    | timestamp with time zone | Time at which the transaction is prepared for commit         |
+| owner       | name                     | Name of the user that executes the transaction               |
+| database    | name                     | Name of the database in which the transaction is executed    |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/SUMMARY_TRANSACTIONS_RUNNING_XACTS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/SUMMARY_TRANSACTIONS_RUNNING_XACTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..7f834c9ac6ea3f07c0bbc355d85dee250b1922fa
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/SUMMARY_TRANSACTIONS_RUNNING_XACTS.md
@@ -0,0 +1,25 @@
+---
+title: SUMMARY_TRANSACTIONS_RUNNING_XACTS
+summary: SUMMARY_TRANSACTIONS_RUNNING_XACTS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_TRANSACTIONS_RUNNING_XACTS
+
+**SUMMARY_TRANSACTIONS_RUNNING_XACTS** displays information about the running transactions on each CN in the cluster. The column content is the same as that of **TRANSACTIONS_RUNNING_XACTS**.
+
+**Table 1** SUMMARY_TRANSACTIONS_RUNNING_XACTS columns
+
+| **Name**    | **Type** | **Description**                                              |
+| :---------- | :------- | :----------------------------------------------------------- |
+| handle      | integer  | Handle corresponding to the transaction in GTM               |
+| gxid        | xid      | Transaction ID                                               |
+| state       | tinyint  | Transaction status (**3**: prepared or **0**: starting)      |
+| node        | text     | Node name                                                    |
+| xmin        | xid      | Minimum transaction ID on the node                           |
+| vacuum      | boolean  | Whether the current transaction is lazy vacuum               |
+| timeline    | bigint   | Number of database restarts                                  |
+| prepare_xid | xid      | Transaction ID in the **prepared** state. If the status is not **prepared**, the value is **0**. |
+| pid         | bigint   | Thread ID corresponding to the transaction                   |
+| next_xid    | xid      | Transaction ID sent from a CN to a DN                        |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/TRANSACTIONS_PREPARED_XACTS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/TRANSACTIONS_PREPARED_XACTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..0c9764669c23321c8785d5a437c99b697212f3db
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/TRANSACTIONS_PREPARED_XACTS.md
@@ -0,0 +1,20 @@
+---
+title: TRANSACTIONS_PREPARED_XACTS
+summary: TRANSACTIONS_PREPARED_XACTS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# TRANSACTIONS_PREPARED_XACTS
+
+**TRANSACTIONS_PREPARED_XACTS** displays information about transactions that are currently prepared for two-phase commit.
+
+**Table 1** TRANSACTIONS_PREPARED_XACTS columns
+
+| Name        | Type                     | Description                                                  |
+| :---------- | :----------------------- | :----------------------------------------------------------- |
+| transaction | xid                      | Numeric transaction identifier of the prepared transaction   |
+| gid         | text                     | Global transaction identifier that was assigned to the transaction |
+| prepared    | timestamp with time zone | Time at which the transaction is prepared for commit         |
+| owner       | name                     | Name of the user that executes the transaction               |
+| database    | name                     | Name of the database in which the transaction is executed    |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/TRANSACTIONS_RUNNING_XACTS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/TRANSACTIONS_RUNNING_XACTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..6cbd4ff6e2ca6a608709bab1d712befb25b1f1f8
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/TRANSACTIONS_RUNNING_XACTS.md
@@ -0,0 +1,25 @@
+---
+title: TRANSACTIONS_RUNNING_XACTS
+summary: TRANSACTIONS_RUNNING_XACTS
+author: Guo Huan
+date: 2021-11-15
+---
+
+# TRANSACTIONS_RUNNING_XACTS
+
+**TRANSACTIONS_RUNNING_XACTS** displays information about running transactions on the current node.
+
+**Table 1** TRANSACTIONS_RUNNING_XACTS columns
+
+| **Name**    | **Type** | **Description**                                              |
+| :---------- | :------- | :----------------------------------------------------------- |
+| handle      | integer  | Handle corresponding to the transaction in GTM               |
+| gxid        | xid      | Transaction ID                                               |
+| state       | tinyint  | Transaction status (**3**: prepared or **0**: starting)      |
+| node        | text     | Node name                                                    |
+| xmin        | xid      | Minimum transaction ID on the node                           |
+| vacuum      | boolean  | Whether the current transaction is lazy vacuum               |
+| timeline    | bigint   | Number of database restarts                                  |
+| prepare_xid | xid      | Transaction ID in the **prepared** state. If the status is not **prepared**, the value is **0**. |
+| pid         | bigint   | Thread ID corresponding to the transaction                   |
+| next_xid    | xid      | Transaction ID sent from a CN to a DN                        |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/BGWRITER_STAT.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/BGWRITER_STAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..98f565252a98a794629515ea5a48fc32f9da15e8
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/BGWRITER_STAT.md
@@ -0,0 +1,26 @@
+---
+title: BGWRITER_STAT
+summary: BGWRITER_STAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# BGWRITER_STAT
+
+**BGWRITER_STAT** displays statistics about the background writer process's activities.
+
+**Table 1** BGWRITER_STAT columns
+
+| Name                  | Type                     | Description                                                  |
+| :-------------------- | :----------------------- | :----------------------------------------------------------- |
+| checkpoints_timed     | bigint                   | Number of scheduled checkpoints that have been performed     |
+| checkpoints_req       | bigint                   | Number of requested checkpoints that have been performed     |
+| checkpoint_write_time | double precision         | Total time that has been spent in the portion of checkpoint processing where files are written to disk (unit: ms) |
+| checkpoint_sync_time  | double precision         | Total time that has been spent in the portion of checkpoint processing where files are synchronized to disk (unit: ms) |
+| buffers_checkpoint    | bigint                   | Number of buffers written during checkpoints                 |
+| buffers_clean         | bigint                   | Number of buffers written by the background writer           |
+| maxwritten_clean      | bigint                   | Number of times the background writer stopped a cleaning scan because it had written too many buffers |
+| buffers_backend       | bigint                   | Number of buffers written directly by a backend              |
+| buffers_backend_fsync | bigint                   | Number of times a backend had to execute its own fsync call (normally the background writer handles those even when the backend does its own write) |
+| buffers_alloc         | bigint                   | Number of buffers allocated                                  |
+| stats_reset           | timestamp with time zone | Time at which these statistics were last reset               |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/CLASS_VITAL_INFO.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/CLASS_VITAL_INFO.md
new file mode 100644
index 0000000000000000000000000000000000000000..ce95385324e2ac6d4e651816d87ebc346280b50c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/CLASS_VITAL_INFO.md
@@ -0,0 +1,19 @@
+---
+title: CLASS_VITAL_INFO
+summary: CLASS_VITAL_INFO
+author: Guo Huan
+date: 2021-04-19
+---
+
+# CLASS_VITAL_INFO
+
+**CLASS_VITAL_INFO** is used to check whether the OIDs of the same table or index are consistent for WDR snapshots.
+
+**Table 1** CLASS_VITAL_INFO columns
+
+| Name       | Type   | Description                                                  |
+| :--------- | :----- | :----------------------------------------------------------- |
+| relid      | oid    | Table OID                                                    |
+| schemaname | name   | Schema name                                                  |
+| relname    | name   | Table name                                                   |
+| relkind    | "char" | Object type. Its value can be:<br/>- **r**: ordinary table<br/>- **t**: TOAST table<br/>- **i**: index |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_BGWRITER_STAT.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_BGWRITER_STAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..742e4af1abf984480dd50040c513c0c625fca34e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_BGWRITER_STAT.md
@@ -0,0 +1,27 @@
+---
+title: GLOBAL_BGWRITER_STAT
+summary: GLOBAL_BGWRITER_STAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_BGWRITER_STAT
+
+**GLOBAL_BGWRITER_STAT** displays statistics about the background writer process's activities on each node.
+
+**Table 1** GLOBAL_BGWRITER_STAT columns
+
+| **Name**              | **Type**                 | **Description**                                              |
+| :-------------------- | :----------------------- | :----------------------------------------------------------- |
+| node_name             | name                     | Node name                                                    |
+| checkpoints_timed     | bigint                   | Number of scheduled checkpoints that have been performed     |
+| checkpoints_req       | bigint                   | Number of requested checkpoints that have been performed     |
+| checkpoint_write_time | double precision         | Total time that has been spent in the portion of checkpoint processing where files are written to disk (unit: ms) |
+| checkpoint_sync_time  | double precision         | Total time that has been spent in the portion of checkpoint processing where files are synchronized to disk (unit: ms) |
+| buffers_checkpoint    | bigint                   | Number of buffers written during checkpoints                 |
+| buffers_clean         | bigint                   | Number of buffers written by the background writer           |
+| maxwritten_clean      | bigint                   | Number of times the background writer stopped a cleaning scan because it had written too many buffers |
+| buffers_backend       | bigint                   | Number of buffers written directly by a backend              |
+| buffers_backend_fsync | bigint                   | Number of times the backend had to execute its own fsync call (normally the background writer handles those even when the backend does its own write) |
+| buffers_alloc         | bigint                   | Number of buffers allocated                                  |
+| stats_reset           | timestamp with time zone | Time at which these statistics were last reset               |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_CANDIDATE_STATUS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_CANDIDATE_STATUS.md
new file mode 100644
index 0000000000000000000000000000000000000000..2bffcbfc8e653065f72731d1248060cbb841e2e7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_CANDIDATE_STATUS.md
@@ -0,0 +1,22 @@
+---
+title: GLOBAL_CANDIDATE_STATUS
+summary: GLOBAL_CANDIDATE_STATUS
+author: Guo Huan
+date: 2021-11-15
+---
+
+# GLOBAL_CANDIDATE_STATUS
+
+**GLOBAL_CANDIDATE_STATUS** displays the number of candidate buffers and buffer eviction information of all instances in the database.
+
+**Table 1** GLOBAL_GET_BGWRITER_STATUS columns
+
+| Name                    | Type    | Description                                                  |
+| :---------------------- | :------ | :----------------------------------------------------------- |
+| node_name               | text    | Node name                                                    |
+| candidate_slots         | integer | Number of pages in the candidate buffer chain of the current normal buffer pool |
+| get_buf_from_list       | bigint  | Number of times that pages are obtained from the candidate buffer chain during buffer eviction in the current normal buffer pool |
+| get_buf_clock_sweep     | bigint  | Number of times that pages are obtained from the original eviction solution during buffer eviction in the current normal buffer pool |
+| seg_candidate_slots     | integer | Number of pages in the candidate buffer chain of the current segment buffer pool |
+| seg_get_buf_from_list   | bigint  | Number of times that pages are obtained from the candidate buffer chain during buffer eviction in the current segment buffer pool |
+| seg_get_buf_clock_sweep | bigint  | Number of times that pages are obtained from the original eviction solution during buffer eviction in the current segment buffer pool |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_CKPT_STATUS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_CKPT_STATUS.md
new file mode 100644
index 0000000000000000000000000000000000000000..9d775a8a18af2460bc918de781bb3fbe96ba3d28
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_CKPT_STATUS.md
@@ -0,0 +1,22 @@
+---
+title: GLOBAL_CKPT_STATUS
+summary: GLOBAL_CKPT_STATUS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_CKPT_STATUS
+
+**GLOBAL_CKPT_STATUS** displays the checkpoint information and log flushing information about all instances in MogDB.
+
+**Table 1** GLOBAL_CKPT_STATUS columns
+
+| Name                     | Type   | Description                                                  |
+| :----------------------- | :----- | :----------------------------------------------------------- |
+| node_name                | text   | Node name                                                    |
+| ckpt_redo_point          | test   | Checkpoint of the current instance                           |
+| ckpt_clog_flush_num      | bigint | Number of Clog flushing pages from the startup time to the current time |
+| ckpt_csnlog_flush_num    | bigint | Number of CSN log flushing pages from the startup time to the current time |
+| ckpt_multixact_flush_num | bigint | Number of MultiXact flushing pages from the startup time to the current time |
+| ckpt_predicate_flush_num | bigint | Number of predicate flushing pages from the startup time to the current time |
+| ckpt_twophase_flush_num  | bigint | Number of two-phase flushing pages from the startup time to the current time |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_DOUBLE_WRITE_STATUS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_DOUBLE_WRITE_STATUS.md
new file mode 100644
index 0000000000000000000000000000000000000000..ee1839ccf2545aa6c7c94ec41500c85c99ba8bd1
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_DOUBLE_WRITE_STATUS.md
@@ -0,0 +1,26 @@
+---
+title: GLOBAL_DOUBLE_WRITE_STATUS
+summary: GLOBAL_DOUBLE_WRITE_STATUS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_DOUBLE_WRITE_STATUS
+
+**GLOBAL_DOUBLE_WRITE_STATUS** displays doublewrite file status of all instances in MogDB.
+
+**Table 1** GLOBAL_DOUBLE_WRITE_STATUS columns
+
+| Name                  | Type   | Description                                                  |
+| :-------------------- | :----- | :----------------------------------------------------------- |
+| node_name             | text   | node name                                                    |
+| curr_dwn              | bigint | Sequence number of the doublewrite file                      |
+| curr_start_page       | bigint | Start page for restoring the doublewrite file                |
+| file_trunc_num        | bigint | Number of times that the doublewrite file is reused          |
+| file_reset_num        | bigint | Number of reset times after the doublewrite file is full     |
+| total_writes          | bigint | Total number of I/Os of the doublewrite file                 |
+| low_threshold_writes  | bigint | Number of I/Os for writing doublewrite files with low efficiency (the number of I/O flushing pages at a time is less than 16) |
+| high_threshold_writes | bigint | Number of I/Os for writing doublewrite files with high efficiency (the number of I/O flushing pages at a time is more than 421) |
+| total_pages           | bigint | Total number of pages that are flushed to the doublewrite file area |
+| low_threshold_pages   | bigint | Number of pages that are flushed with low efficiency         |
+| high_threshold_pages  | bigint | Number of pages that are flushed with high efficiency        |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_GET_BGWRITER_STATUS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_GET_BGWRITER_STATUS.md
new file mode 100644
index 0000000000000000000000000000000000000000..fe4482e6637bdb065d1d78e715612437e41b9a93
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_GET_BGWRITER_STATUS.md
@@ -0,0 +1,21 @@
+---
+title: GLOBAL_GET_BGWRITER_STATUS
+summary: GLOBAL_GET_BGWRITER_STATUS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_GET_BGWRITER_STATUS
+
+**GLOBAL_GET_BGWRITER_STATUS** displays the information about pages flushed by the bgwriter threads of all instances in the cluster, number of pages in the candidate buffer chain, and buffer eviction information.
+
+**Table 1** GLOBAL_GET_BGWRITER_STATUS columns
+
+| Name                        | Type    | Description                                                  |
+| :-------------------------- | :------ | :----------------------------------------------------------- |
+| node_name                   | text    | Instance name                                                |
+| bgwr_actual_flush_total_num | bigint  | Total number of dirty pages flushed by the bgwriter thread from the startup time to the current time |
+| bgwr_last_flush_num         | integer | Number of dirty pages flushed by the bgwriter thread in the previous batch |
+| candidate_slots             | integer | Number of pages in the current candidate buffer chain.       |
+| get_buffer_from_list        | bigint  | Number of times that pages are obtained from the candidate buffer chain during buffer eviction. |
+| get_buffer_clock_sweep      | bigint  | Number of times that pages are obtained from the original eviction solution during buffer eviction. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_PAGEWRITER_STATUS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_PAGEWRITER_STATUS.md
new file mode 100644
index 0000000000000000000000000000000000000000..14f9da5185cbb88db5c1107a6a4eb25e0b82f872
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_PAGEWRITER_STATUS.md
@@ -0,0 +1,23 @@
+---
+title: GLOBAL_PAGEWRITER_STATUS
+summary: GLOBAL_PAGEWRITER_STATUS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_PAGEWRITER_STATUS
+
+**GLOBAL_PAGEWRITER_STATUS** displays the page flushing information and checkpoint information about all instances in MogDB.
+
+**Table 1** GLOBAL_PAGEWRITER_STATUS columns
+
+| Name                        | Type    | Description                                                  |
+| :-------------------------- | :------ | :----------------------------------------------------------- |
+| node_name                   | text    | node name                                                    |
+| pgwr_actual_flush_total_num | bigint  | Total number of dirty pages flushed from the startup time to the current time |
+| pgwr_last_flush_num         | integer | Number of dirty pages flushed in the previous batch          |
+| remain_dirty_page_num       | bigint  | Estimated number of dirty pages that are not flushed         |
+| queue_head_page_rec_lsn     | text    | **recovery_lsn** of the first dirty page in the dirty page queue of the current instance |
+| queue_rec_lsn               | text    | **recovery_lsn** of the dirty page queue of the current instance |
+| current_xlog_insert_lsn     | text    | Write position of Xlogs in the current instance              |
+| ckpt_redo_point             | text    | Checkpoint of the current instance                           |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_RECORD_RESET_TIME.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_RECORD_RESET_TIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..3a54a837f23b272d972bdbdab8102ec048dcf60d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_RECORD_RESET_TIME.md
@@ -0,0 +1,17 @@
+---
+title: GLOBAL_RECORD_RESET_TIME
+summary: GLOBAL_RECORD_RESET_TIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_RECORD_RESET_TIME
+
+**GLOBAL_RECORD_RESET_TIME** displays statistics about reset time in MogDB. Restart, primary/standby switchover, and database deletion will cause the time to be reset.
+
+**Table 1** GLOBAL_RECORD_RESET_TIME columns
+
+| Name       | Type                     | Description      |
+| :--------- | :----------------------- | :--------------- |
+| node_name  | text                     | node name        |
+| reset_time | timestamp with time zone | Time to be reset |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_RECOVERY_STATUS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_RECOVERY_STATUS.md
new file mode 100644
index 0000000000000000000000000000000000000000..1c537e594b3d66871be4c54f0fa681936f613f71
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_RECOVERY_STATUS.md
@@ -0,0 +1,24 @@
+---
+title: GLOBAL_RECOVERY_STATUS
+summary: GLOBAL_RECOVERY_STATUS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_RECOVERY_STATUS
+
+**GLOBAL_RECOVERY_STATUS** displays log flow control information about the primary and standby nodes.
+
+**Table 1** GLOBAL_RECOVERY_STATUS columns
+
+| Name               | Type    | Description                                                  |
+| :----------------- | :------ | :----------------------------------------------------------- |
+| node_name          | text    | Node name (including the primary and standby nodes)          |
+| standby_node_name  | text    | Name of the standby node process                             |
+| source_ip          | text    | IP address of the primary node                               |
+| source_port        | integer | Port number of the primary node                              |
+| dest_ip            | text    | IP address of the standby node                               |
+| dest_port          | integer | Port number of the standby node                              |
+| current_rto        | bigint  | Current log flow control time of the standby node (unit: s)  |
+| target_rto         | bigint  | Expected flow control time of the standby node specified by the corresponding GUC parameter (unit: s) |
+| current_sleep_time | bigint  | Sleep time required to achieve the expected flow control time (unit: μs) |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_REDO_STATUS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_REDO_STATUS.md
new file mode 100644
index 0000000000000000000000000000000000000000..affc0da9d4e10619cea4d9cb3de4e328c5032206
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_REDO_STATUS.md
@@ -0,0 +1,38 @@
+---
+title: GLOBAL_REDO_STATUS
+summary: GLOBAL_REDO_STATUS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_REDO_STATUS
+
+**GLOBAL_REDO_STATUS** displays the log replay status of all instances in MogDB.
+
+**Table 1** GLOBAL_REDO_STATUS columns
+
+| Name                      | Type   | Description                                                  |
+| :------------------------ | :----- | :----------------------------------------------------------- |
+| node_name                 | text   | Node name                                                    |
+| redo_start_ptr            | bigint | Start point for replaying the instance logs                  |
+| redo_start_time           | bigint | Start time (UTC) when the instance logs are replayed         |
+| redo_done_time            | bigint | End time (UTC) when the instance logs are replayed           |
+| curr_time                 | bigint | Current time (UTC) of the instance                           |
+| min_recovery_point        | bigint | Position of the minimum consistency point for the instance logs |
+| read_ptr                  | bigint | Position for reading the instance logs                       |
+| last_replayed_read_ptr    | bigint | Position for replaying the instance logs                     |
+| recovery_done_ptr         | bigint | Replay position after the instance is started                |
+| read_xlog_io_counter      | bigint | Number of I/Os when the instance reads and replays logs      |
+| read_xlog_io_total_dur    | bigint | Total I/O latency when the instance reads and replays logs   |
+| read_data_io_counter      | bigint | Number of data page I/O reads during replay in the instance  |
+| read_data_io_total_dur    | bigint | Total I/O latency of data page reads during replay in the instance |
+| write_data_io_counter     | bigint | Number of data page I/O writes during replay in the instance |
+| write_data_io_total_dur   | bigint | Total I/O latency of data page writes during replay in the instance |
+| process_pending_counter   | bigint | Number of synchronization times of log distribution threads during replay in the instance |
+| process_pending_total_dur | bigint | Total synchronization latency of log distribution threads during replay in the instance |
+| apply_counter             | bigint | Number of synchronization times of replay threads during replay in the instance |
+| apply_total_dur           | bigint | Total synchronization latency of replay threads during replay in the instance |
+| speed                     | bigint | Log replay rate of the current instance                      |
+| local_max_ptr             | bigint | Maximum number of replay logs received by the local host after the instance is started |
+| primary_flush_ptr         | bigint | Log point where the host flushes logs to a disk              |
+| worker_info               | text   | Replay thread information of the instance. If concurrent replay is not enabled, the value is **NULL**. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_REPLICATION_SLOTS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_REPLICATION_SLOTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..803b5b50671c0448afa4c0eb617f47d4c8e4f4ad
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_REPLICATION_SLOTS.md
@@ -0,0 +1,26 @@
+---
+title: GLOBAL_REPLICATION_SLOTS
+summary: GLOBAL_REPLICATION_SLOTS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_REPLICATION_SLOTS
+
+**GLOBAL_REPLICATION_SLOTS** displays replication node information of each node in MogDB.
+
+**Table 1** GLOBAL_REPLICATION_SLOTS columns
+
+| **Name**      | **Type** | **Description**                                              |
+| :------------ | :------- | :----------------------------------------------------------- |
+| node_name     | name     | Node name                                                    |
+| slot_name     | text     | Replication node name                                        |
+| plugin        | text     | Plug-in name                                                 |
+| slot_type     | text     | Type of the replication node                                 |
+| datoid        | oid      | OID of the database on the replication node                  |
+| database      | name     | Name of the database on the replication node                 |
+| active        | boolean  | Whether the replication node is active                       |
+| x_min         | xid      | Transaction ID of the replication node                       |
+| catalog_xmin  | xid      | ID of the earliest decoded transaction corresponding to the logical replication slot |
+| restart_lsn   | text     | XLOG file information on the replication node                |
+| dummy_standby | boolean  | Whether the replication node is a dummy standby node         |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_REPLICATION_STAT.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_REPLICATION_STAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..4638d9dad622e98e3becd28c312d19d7d9ef4d83
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_REPLICATION_STAT.md
@@ -0,0 +1,31 @@
+---
+title: GLOBAL_REPLICATION_STAT
+summary: GLOBAL_REPLICATION_STAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_REPLICATION_STAT
+
+**GLOBAL_REPLICATION_STAT** displays information about log synchronization status on each node, such as the locations where the sender sends logs and where the receiver receives logs.
+
+**Table 1** GLOBAL_REPLICATION_STAT columns
+
+| **Name**                 | **Type**                 | **Description**                                              |
+| :----------------------- | :----------------------- | :----------------------------------------------------------- |
+| node_name                | name                     | Node name                                                    |
+| pid                      | bigint                   | PID of the thread                                            |
+| usesysid                 | oid                      | User system ID                                               |
+| usename                  | name                     | Username                                                     |
+| application_name         | text                     | Program name                                                 |
+| client_addr              | inet                     | Client address                                               |
+| client_hostname          | text                     | Client name                                                  |
+| client_port              | integer                  | Port of the client                                           |
+| backend_start            | timestamp with time zone | Start time of the program                                    |
+| state                    | text                     | Log replication status (catch-up or consistent streaming)    |
+| sender_sent_location     | text                     | Location where the transmit sends logs                       |
+| receiver_write_location  | text                     | Location where the receive end writes logs                   |
+| receiver_flush_location  | text                     | Location where the receive end flushes logs                  |
+| receiver_replay_location | text                     | Location where the receive end replays logs                  |
+| sync_priority            | integer                  | Priority of synchronous duplication (**0** indicates asynchronization.) |
+| sync_state               | text                     | Synchronization status:<br/>- Asynchronous replication<br/>- Synchronous replication<br/>- Potential synchronization |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_SINGLE_FLUSH_DW_STATUS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_SINGLE_FLUSH_DW_STATUS.md
new file mode 100644
index 0000000000000000000000000000000000000000..2cf2befbf6f1594d2bf4abc78e76f1ebe2bb7f70
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_SINGLE_FLUSH_DW_STATUS.md
@@ -0,0 +1,21 @@
+---
+title: GLOBAL_SINGLE_FLUSH_DW_STATUS
+summary: GLOBAL_SINGLE_FLUSH_DW_STATUS
+author: Guo Huan
+date: 2021-11-15
+---
+
+# GLOBAL_SINGLE_FLUSH_DW_STATUS
+
+**GLOBAL_SINGLE_FLUSH_DW_STATUS** displays information about doublewrite files eliminated on a single page of all instances in the database. In the displayed information, the information before the slash (/) indicates the page flushing status of the first version, and the information after the slash (/) indicates the page flushing status of the second version.
+
+**Table 1** GLOBAL_SINGLE_FLUSH_DW_STATUS columns
+
+| Name            | Type | Description                                                  |
+| :-------------- | :--- | :----------------------------------------------------------- |
+| node_name       | text | Instance name                                                |
+| curr_dwn        | text | Sequence number of the doublewrite file                      |
+| curr_start_page | text | Start position of the current doublewrite file               |
+| total_writes    | text | Total number of data write pages in the current doublewrite file |
+| file_trunc_num  | text | Number of times that the doublewrite file is reused          |
+| file_reset_num  | text | Number of reset times after the doublewrite file is full     |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/REPLICATION_SLOTS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/REPLICATION_SLOTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..bfe840b54aa2514648c78b4a5c25dfaa6d9ee9a1
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/REPLICATION_SLOTS.md
@@ -0,0 +1,25 @@
+---
+title: REPLICATION_SLOTS
+summary: REPLICATION_SLOTS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# REPLICATION_SLOTS
+
+**REPLICATION_SLOTS** displays replication node information.
+
+**Table 1** REPLICATION_SLOTS columns
+
+| Name          | Type    | Description                                                  |
+| :------------ | :------ | :----------------------------------------------------------- |
+| slot_name     | text    | Replication node name                                        |
+| plugin        | text    | Plug-in name                                                 |
+| slot_type     | text    | Replication node type                                        |
+| datoid        | oid     | OID of the database on the replication node                  |
+| database      | name    | Name of the database on the replication node                 |
+| active        | boolean | Whether the replication node is active                       |
+| xmin          | xid     | Transaction ID of the replication node                       |
+| catalog_xmin  | xid     | ID of the earliest decoded transaction corresponding to the logical replication slot |
+| restart_lsn   | text    | XLOG file information on the replication node                |
+| dummy_standby | boolean | Whether the replication node is a dummy standby node         |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/REPLICATION_STAT.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/REPLICATION_STAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..7f5272a1fd1ca1230b230dcd78c07b4a0370ce77
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/REPLICATION_STAT.md
@@ -0,0 +1,30 @@
+---
+title: REPLICATION_STAT
+summary: REPLICATION_STAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# REPLICATION_STAT
+
+**REPLICATION_STAT** describes information about log synchronization status, such as the locations where the sender sends logs and where the receiver receives logs.
+
+**Table 1** REPLICATION_STAT columns
+
+| Name                     | Type                     | Description                                                  |
+| :----------------------- | :----------------------- | :----------------------------------------------------------- |
+| pid                      | bigint                   | Process ID of the thread                                     |
+| usesysid                 | oid                      | User system ID                                               |
+| usename                  | name                     | Username                                                     |
+| application_name         | text                     | Program name                                                 |
+| client_addr              | inet                     | Client address                                               |
+| client_hostname          | text                     | Client name                                                  |
+| client_port              | integer                  | Port of the client                                           |
+| backend_start            | timestamp with time zone | Start time of the program                                    |
+| state                    | text                     | Log replication state (catch-up or consistent streaming)     |
+| sender_sent_location     | text                     | Location where the sender sends logs                         |
+| receiver_write_location  | text                     | Location where the receiver writes logs                      |
+| receiver_flush_location  | text                     | Location where the receiver flushes logs                     |
+| receiver_replay_location | text                     | Location where the receiver replays logs                     |
+| sync_priority            | integer                  | Priority of synchronous duplication (**0** indicates asynchronization.) |
+| sync_state               | text                     | Synchronization state (asynchronous duplication, synchronous duplication, or potential synchronization) |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/SUMMARY_USER_LOGIN.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/SUMMARY_USER_LOGIN.md
new file mode 100644
index 0000000000000000000000000000000000000000..30bdc1dcee748f4d0ecb85a3570453680559e2d6
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/SUMMARY_USER_LOGIN.md
@@ -0,0 +1,20 @@
+---
+title: SUMMARY_USER_LOGIN
+summary: SUMMARY_USER_LOGIN
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_USER_LOGIN
+
+**SUMMARY_USER_LOGIN** records the number of user logins and logouts on the primary database node.
+
+**Table 1** SUMMARY_USER_LOGIN columns
+
+| **Name**       | **Type** | **Description**                                              |
+| :------------- | :------- | :----------------------------------------------------------- |
+| node_name      | text     | Database process name                                        |
+| user_name      | text     | Username                                                     |
+| user_id        | integer  | User OID (Its value is the same as that of **oid** in **pg_authid**.) |
+| login_counter  | bigint   | Number of logins                                             |
+| logout_counter | bigint   | Number of logouts                                            |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/USER_LOGIN.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/USER_LOGIN.md
new file mode 100644
index 0000000000000000000000000000000000000000..f7d7f27350b83c796fca3d7af4b83b774e82bba5
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/USER_LOGIN.md
@@ -0,0 +1,20 @@
+---
+title: USER_LOGIN
+summary: USER_LOGIN
+author: Guo Huan
+date: 2021-04-19
+---
+
+# USER_LOGIN
+
+**USER_LOGIN** records the number of user logins and logouts.
+
+**Table 1** USER_LOGIN columns
+
+| **Name**       | **Type** | **Description**                                              |
+| :------------- | :------- | :----------------------------------------------------------- |
+| node_name      | text     | Database process name                                        |
+| user_name      | text     | Username                                                     |
+| user_id        | integer  | User OID (Its value is the same as that of **oid** in **pg_authid**.) |
+| login_counter  | bigint   | Number of logins                                             |
+| logout_counter | bigint   | Number of logouts                                            |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/wait-events/GLOBAL_WAIT_EVENTS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/wait-events/GLOBAL_WAIT_EVENTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..08afb75c30668c619ff24157a829a05cc942e3d5
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/wait-events/GLOBAL_WAIT_EVENTS.md
@@ -0,0 +1,25 @@
+---
+title: GLOBAL_WAIT_EVENTS
+summary: GLOBAL_WAIT_EVENTS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_WAIT_EVENTS
+
+**GLOBAL_WAIT_EVENTS** displays statistics about wait events on each node.
+
+**Table 1** GLOBAL_WAIT_EVENTS columns
+
+| **Name**        | **Type**                 | **Description**                      |
+| :-------------- | :----------------------- | :----------------------------------- |
+| nodename        | text                     | Database process name                |
+| type            | text                     | Event type                           |
+| event           | text                     | Event name                           |
+| wait            | bigint                   | Number of waiting times              |
+| failed_wait     | bigint                   | Number of waiting failures           |
+| total_wait_time | bigint                   | Total waiting time (unit: μs)        |
+| avg_wait_time   | bigint                   | Average waiting time (unit: μs)      |
+| max_wait_time   | bigint                   | Maximum waiting time (unit: μs)      |
+| min_wait_time   | bigint                   | Minimum waiting time (unit: μs)      |
+| last_updated    | timestamp with time zone | Last time when the event was updated |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/wait-events/WAIT_EVENTS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/wait-events/WAIT_EVENTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..26b9f97a4727621a79dd87c8bff369f584b03860
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/wait-events/WAIT_EVENTS.md
@@ -0,0 +1,25 @@
+---
+title: WAIT_EVENTS
+summary: WAIT_EVENTS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# WAIT_EVENTS
+
+**WAIT_EVENTS** displays statistics about wait events on the current node. For details about events, see **[Appendices-Table 1](table-1)**, **[Appendices-Table 2](table-2)**, **[Appendices-Table 3](table-3)**, and **[Appendices-Table 4](table-4)**. For details about the extent to which each transaction lock affects the services, see [LOCK](110-LOCK).
+
+**Table 1** WAIT_EVENTS columns
+
+| **Name**        | **Type**                 | **Description**                      |
+| :-------------- | :----------------------- | :----------------------------------- |
+| nodename        | text                     | Database process name                |
+| type            | text                     | Event type                           |
+| event           | text                     | Event name                           |
+| wait            | bigint                   | Number of waiting times              |
+| failed_wait     | bigint                   | Number of waiting failures           |
+| total_wait_time | bigint                   | Total waiting time (unit: μs)        |
+| avg_wait_time   | bigint                   | Average waiting time (unit: μs)      |
+| max_wait_time   | bigint                   | Maximum waiting time (unit: μs)      |
+| min_wait_time   | bigint                   | Minimum waiting time (unit: μs)      |
+| last_updated    | timestamp with time zone | Last time when the event was updated |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload-manager/WLM_USER_RESOURCE_CONFIG.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload-manager/WLM_USER_RESOURCE_CONFIG.md
new file mode 100644
index 0000000000000000000000000000000000000000..e883b3914fc4cacf2b7738529dc8d96c55b5eb59
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload-manager/WLM_USER_RESOURCE_CONFIG.md
@@ -0,0 +1,25 @@
+---
+title: WLM_USER_RESOURCE_CONFIG
+summary: WLM_USER_RESOURCE_CONFIG
+author: Guo Huan
+date: 2021-04-19
+---
+
+# WLM_USER_RESOURCE_CONFIG
+
+**WLM_USER_RESOURCE_CONFIG** displays the resource configuration information of a user.
+
+**Table 1** WLM_USER_RESOURCE_CONFIG columns
+
+| Name       | Type    | Description                                      |
+| :--------- | :------ | :----------------------------------------------- |
+| userid     | oid     | OID of the user                                  |
+| username   | name    | Username                                         |
+| sysadmin   | boolean | Whether the user has the **sysadmin** permission |
+| rpoid      | oid     | OID of the resource pool                         |
+| respool    | name    | Name of a resource pool                          |
+| parentid   | oid     | OID of the parent user                           |
+| totalspace | bigint  | Size of the occupied space                       |
+| spacelimit | bigint  | Upper limit of the space size                    |
+| childcount | integer | Number of child users                            |
+| childlist  | text    | Child user list                                  |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload-manager/WLM_USER_RESOURCE_RUNTIME.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload-manager/WLM_USER_RESOURCE_RUNTIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..86c810a04a9f67778e7b89d580233cd7263b7bc8
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload-manager/WLM_USER_RESOURCE_RUNTIME.md
@@ -0,0 +1,26 @@
+---
+title: WLM_USER_RESOURCE_RUNTIME
+summary: WLM_USER_RESOURCE_RUNTIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# WLM_USER_RESOURCE_RUNTIME
+
+**WLM_USER_RESOURCE_RUNTIME** displays resource usage of all users. Only administrators can query this view. This view is valid only when the GUC parameter **use_workload_manager** is set to **on**.
+
+**Table 1** WLM_USER_RESOURCE_RUNTIME columns
+
+| Name              | Type    | Description                                                  |
+| :---------------- | :------ | :----------------------------------------------------------- |
+| username          | name    | Username                                                     |
+| used_memory       | integer | Used memory (unit: MB)                                       |
+| total_memory      | integer | Available memory (unit: MB) The value **0** indicates that the available memory is not limited and depends on the maximum memory available in the database. |
+| used_cpu          | integer | Number of CPU cores in use                                   |
+| total_cpu         | integer | Total number of CPU cores of the Cgroup associated with the user on the node |
+| used_space        | bigint  | Used storage space (unit: KB)                                |
+| total_space       | bigint  | Available storage space (unit: KB). The value **-1** indicates that the space is not limited. |
+| used_temp_space   | bigint  | Used temporary space (reserved column; unit: KB)             |
+| total_temp_space  | bigint  | Available temporary space (reserved column; unit: KB). The value **-1** indicates that the maximum temporary storage space is not limited. |
+| used_spill_space  | bigint  | Used space for storing spilled data (reserved column; unit: KB) |
+| total_spill_space | bigint  | Available space for storing spilled data (reserved column; unit: KB). The value **-1** indicates that the maximum space for storing spilled data is not limited. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/GLOBAL_USER_TRANSACTION.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/GLOBAL_USER_TRANSACTION.md
new file mode 100644
index 0000000000000000000000000000000000000000..0709859c7b809395dab523b0f7d8a8f366a4db94
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/GLOBAL_USER_TRANSACTION.md
@@ -0,0 +1,29 @@
+---
+title: GLOBAL_USER_TRANSACTION
+summary: GLOBAL_USER_TRANSACTION
+author: Guo Huan
+date: 2021-11-15
+---
+
+# GLOBAL_USER_TRANSACTION
+
+**GLOBAL_USER_TRANSACTION** collects statistics about transactions executed by all users.
+
+**Table 1** GLOBAL_USER_TRANSACTION columns
+
+| **Name**            | **Type** | **Description**                                             |
+| :------------------ | :------- | :---------------------------------------------------------- |
+| node_name           | name     | Node name                                                   |
+| username            | name     | Username                                                    |
+| commit_counter      | bigint   | Number of user transactions committed                       |
+| rollback_counter    | bigint   | Number of user transactions rolled back                     |
+| resp_min            | bigint   | Minimum response time of user transactions (unit: μs)       |
+| resp_max            | bigint   | Maximum response time of user transactions (unit: μs)       |
+| resp_avg            | bigint   | Average response time of user transactions (unit: μs)       |
+| resp_total          | bigint   | Total response time of user transactions (unit: μs)         |
+| bg_commit_counter   | bigint   | Number of background transactions committed                 |
+| bg_rollback_counter | bigint   | Number of background transactions rolled back               |
+| bg_resp_min         | bigint   | Minimum response time of background transactions (unit: μs) |
+| bg_resp_max         | bigint   | Maximum response time of background transactions (unit: μs) |
+| bg_resp_avg         | bigint   | Average response time of background transactions (unit: μs) |
+| bg_resp_total       | bigint   | Total response time of background transactions (unit: μs)   |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/GLOBAL_WORKLOAD_TRANSACTION.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/GLOBAL_WORKLOAD_TRANSACTION.md
new file mode 100644
index 0000000000000000000000000000000000000000..eedb74082bb7e0e50f78a005b44d596c8bcbcf39
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/GLOBAL_WORKLOAD_TRANSACTION.md
@@ -0,0 +1,29 @@
+---
+title: GLOBAL_WORKLOAD_TRANSACTION
+summary: GLOBAL_WORKLOAD_TRANSACTION
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_WORKLOAD_TRANSACTION
+
+**GLOBAL_WORKLOAD_TRANSACTION** displays load information about workloads on each node.
+
+**Table 1** GLOBAL_WORKLOAD_TRANSACTION columns
+
+| **Name**            | **Type** | **Description**                                             |
+| :------------------ | :------- | :---------------------------------------------------------- |
+| node_name           | name     | Node name                                                   |
+| workload            | name     | Workload name                                               |
+| commit_counter      | bigint   | Number of user transactions committed                       |
+| rollback_counter    | bigint   | Number of user transactions rolled back                     |
+| resp_min            | bigint   | Minimum response time of user transactions (unit: μs)       |
+| resp_max            | bigint   | Maximum response time of user transactions (unit: μs)       |
+| resp_avg            | bigint   | Average response time of user transactions (unit: μs)       |
+| resp_total          | bigint   | Total response time of user transactions (unit: μs)         |
+| bg_commit_counter   | bigint   | Number of background transactions committed                 |
+| bg_rollback_counter | bigint   | Number of background transactions rolled back               |
+| bg_resp_min         | bigint   | Minimum response time of background transactions (unit: μs) |
+| bg_resp_max         | bigint   | Maximum response time of background transactions (unit: μs) |
+| bg_resp_avg         | bigint   | Average response time of background transactions (unit: μs) |
+| bg_resp_total       | bigint   | Total response time of background transactions (unit: μs)   |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/SUMMARY_WORKLOAD_SQL_COUNT.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/SUMMARY_WORKLOAD_SQL_COUNT.md
new file mode 100644
index 0000000000000000000000000000000000000000..abca291239295a4d6be42a8d37c1e6dab05fc84b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/SUMMARY_WORKLOAD_SQL_COUNT.md
@@ -0,0 +1,24 @@
+---
+title: SUMMARY_WORKLOAD_SQL_COUNT
+summary: SUMMARY_WORKLOAD_SQL_COUNT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_WORKLOAD_SQL_COUNT
+
+**SUMMARY_WORKLOAD_SQL_COUNT** displays the distribution of SQL statements in workloads on the primary database node in MogDB.
+
+**Table 1** SUMMARY_WORKLOAD_SQL_COUNT columns
+
+| **Name**     | **Type** | **Description**                 |
+| :----------- | :------- | :------------------------------ |
+| node_name    | name     | Database process name           |
+| workload     | name     | Workload name                   |
+| select_count | bigint   | Number of **SELECT** statements |
+| update_count | bigint   | Number of **UPDATE** statements |
+| insert_count | bigint   | Number of **INSERT** statements |
+| delete_count | bigint   | Number of **DELETE** statements |
+| ddl_count    | bigint   | Number of **DDL** statements    |
+| dml_count    | bigint   | Number of **DML** statements    |
+| dcl_count    | bigint   | Number of **DCL** statements    |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/SUMMARY_WORKLOAD_SQL_ELAPSE_TIME.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/SUMMARY_WORKLOAD_SQL_ELAPSE_TIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..0baaf46eb79d440426febcd4bd497d6c75f281e4
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/SUMMARY_WORKLOAD_SQL_ELAPSE_TIME.md
@@ -0,0 +1,33 @@
+---
+title: SUMMARY_WORKLOAD_SQL_ELAPSE_TIME
+summary: SUMMARY_WORKLOAD_SQL_ELAPSE_TIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_WORKLOAD_SQL_ELAPSE_TIME
+
+**SUMMARY_WORKLOAD_SQL_ELAPSE_TIME** collects statistics about SUIDs in workloads on the primary database node.
+
+**Table 1** SUMMARY_WORKLOAD_SQL_ELAPSE_TIM columns
+
+| **Name**            | **Type** | **Description**                                           |
+| :------------------ | :------- | :-------------------------------------------------------- |
+| node_name           | name     | Database process name                                     |
+| workload            | name     | Workload name                                             |
+| total_select_elapse | bigint   | Total response time of **SELECT** statements (unit: μs)   |
+| max_select_elapse   | bigint   | Maximum response time of **SELECT** statements (unit: μs) |
+| min_select_elapse   | bigint   | Minimum response time of **SELECT** statements (unit: μs) |
+| avg_select_elapse   | bigint   | Average response time of **SELECT** statements (unit: μs) |
+| total_update_elapse | bigint   | Total response time of **UPDATE** statements (unit: μs)   |
+| max_update_elapse   | bigint   | Maximum response time of **UPDATE** statements (unit: μs) |
+| min_update_elapse   | bigint   | Minimum response time of **UPDATE** statements (unit: μs) |
+| avg_update_elapse   | bigint   | Average response time of **UPDATE** statements (unit: μs) |
+| total_insert_elapse | bigint   | Total response time of **INSERT** statements (unit: μs)   |
+| max_insert_elapse   | bigint   | Maximum response time of **INSERT** statements (unit: μs) |
+| min_insert_elapse   | bigint   | Minimum response time of **INSERT** statements (unit: μs) |
+| avg_insert_elapse   | bigint   | Average response time of **INSERT** statements (unit: μs) |
+| total_delete_elapse | bigint   | Total response time of **DELETE** statements (unit: μs)   |
+| max_delete_elapse   | bigint   | Maximum response time of **DELETE** statements (unit: μs) |
+| min_delete_elapse   | bigint   | Minimum response time of **DELETE** statements (unit: μs) |
+| avg_delete_elapse   | bigint   | Average response time of **DELETE** statements (unit: μs) |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/SUMMARY_WORKLOAD_TRANSACTION.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/SUMMARY_WORKLOAD_TRANSACTION.md
new file mode 100644
index 0000000000000000000000000000000000000000..25692d70c7bafe497ecd77c6eb82d0a1a91aaa4f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/SUMMARY_WORKLOAD_TRANSACTION.md
@@ -0,0 +1,28 @@
+---
+title: SUMMARY_WORKLOAD_TRANSACTION
+summary: SUMMARY_WORKLOAD_TRANSACTION
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_WORKLOAD_TRANSACTION
+
+**SUMMARY_WORKLOAD_TRANSACTION** displays information about transactions loaded in MogDB.
+
+**Table 1** SUMMARY_WORKLOAD_TRANSACTION columns
+
+| **Name**            | **Type** | **Description**                                             |
+| :------------------ | :------- | :---------------------------------------------------------- |
+| workload            | name     | Workload name                                               |
+| commit_counter      | numeric  | Number of user transactions committed                       |
+| rollback_counter    | numeric  | Number of user transactions rolled back                     |
+| resp_min            | bigint   | Minimum response time of user transactions (unit: μs)       |
+| resp_max            | bigint   | Maximum response time of user transactions (unit: μs)       |
+| resp_avg            | bigint   | Average response time of user transactions (unit: μs)       |
+| resp_total          | numeric  | Total response time of user transactions (unit: μs)         |
+| bg_commit_counter   | numeric  | Number of background transactions committed                 |
+| bg_rollback_counter | numeric  | Number of background transactions rolled back               |
+| bg_resp_min         | bigint   | Minimum response time of background transactions (unit: μs) |
+| bg_resp_max         | bigint   | Maximum response time of background transactions (unit: μs) |
+| bg_resp_avg         | bigint   | Average response time of background transactions (unit: μs) |
+| bg_resp_total       | numeric  | Total response time of background transactions (unit: μs)   |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/USER_TRANSACTION.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/USER_TRANSACTION.md
new file mode 100644
index 0000000000000000000000000000000000000000..105e92f751cb90bac88e790308973bc5da68e103
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/USER_TRANSACTION.md
@@ -0,0 +1,28 @@
+---
+title: USER_TRANSACTION
+summary: USER_TRANSACTION
+author: Guo Huan
+date: 2021-11-15
+---
+
+# USER_TRANSACTION
+
+**USER_TRANSACTION** collects statistics about transactions executed by users. Common users can view only transactions executed by themselves, whereas user **monadmin** can view transactions executed by all users.
+
+**Table 1** USER_TRANSACTION columns
+
+| **Name**            | **Type** | **Description**                                             |
+| :------------------ | :------- | :---------------------------------------------------------- |
+| username            | name     | Username                                                    |
+| commit_counter      | bigint   | Number of user transactions committed                       |
+| rollback_counter    | bigint   | Number of user transactions rolled back                     |
+| resp_min            | bigint   | Minimum response time of user transactions (unit: μs)       |
+| resp_max            | bigint   | Maximum response time of user transactions (unit: μs)       |
+| resp_avg            | bigint   | Average response time of user transactions (unit: μs)       |
+| resp_total          | bigint   | Total response time of user transactions (unit: μs)         |
+| bg_commit_counter   | bigint   | Number of background transactions committed                 |
+| bg_rollback_counter | bigint   | Number of background transactions rolled back               |
+| bg_resp_min         | bigint   | Minimum response time of background transactions (unit: μs) |
+| bg_resp_max         | bigint   | Maximum response time of background transactions (unit: μs) |
+| bg_resp_avg         | bigint   | Average response time of background transactions (unit: μs) |
+| bg_resp_total       | bigint   | Total response time of background transactions (unit: μs)   |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/WORKLOAD_SQL_COUNT.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/WORKLOAD_SQL_COUNT.md
new file mode 100644
index 0000000000000000000000000000000000000000..9f243e140da4422c4fe97a54c9cdd91d96b3c61c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/WORKLOAD_SQL_COUNT.md
@@ -0,0 +1,23 @@
+---
+title: WORKLOAD_SQL_COUNT
+summary: WORKLOAD_SQL_COUNT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# WORKLOAD_SQL_COUNT
+
+**WORKLOAD_SQL_COUNT** displays the distribution of SQL statements in workloads on the current node. Common users can view only the distribution of SQL statements executed by themselves in workloads, whereas Initial user can view the overall load status of workloads.
+
+**Table 1** WORKLOAD_SQL_COUNT columns
+
+| **Name**     | **Type** | **Description**                 |
+| :----------- | :------- | :------------------------------ |
+| workload     | name     | Workload name                   |
+| select_count | bigint   | Number of **SELECT** statements |
+| update_count | bigint   | Number of **UPDATE** statements |
+| insert_count | bigint   | Number of **INSERT** statements |
+| delete_count | bigint   | Number of **DELETE** statements |
+| ddl_count    | bigint   | Number of **DDL** statements    |
+| dml_count    | bigint   | Number of **DML** statements    |
+| dcl_count    | bigint   | Number of **DCL** statements    |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/WORKLOAD_SQL_ELAPSE_TIME.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/WORKLOAD_SQL_ELAPSE_TIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..a2befdfeb813d52e7b556e6bf957a1b6da70fb31
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/WORKLOAD_SQL_ELAPSE_TIME.md
@@ -0,0 +1,32 @@
+---
+title: WORKLOAD_SQL_ELAPSE_TIME
+summary: WORKLOAD_SQL_ELAPSE_TIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# WORKLOAD_SQL_ELAPSE_TIME
+
+**WORKLOAD_SQL_ELAPSE_TIME** collects statistics about SUIDs in workloads.
+
+**Table 1** WORKLOAD_SQL_ELAPSE_TIME columns
+
+| Name                | Type   | Description                                               |
+| :------------------ | :----- | :-------------------------------------------------------- |
+| workload            | name   | Workload name                                             |
+| total_select_elapse | bigint | Total response time of **SELECT** statements (unit: μs)   |
+| max_select_elapse   | bigint | Maximum response time of **SELECT** statements (unit: μs) |
+| min_select_elapse   | bigint | Minimum response time of **SELECT** statements (unit: μs) |
+| avg_select_elapse   | bigint | Average response time of **SELECT** statements (unit: μs) |
+| total_update_elapse | bigint | Total response time of **UPDATE** statements (unit: μs)   |
+| max_update_elapse   | bigint | Maximum response time of **UPDATE** statements (unit: μs) |
+| min_update_elapse   | bigint | Minimum response time of **UPDATE** statements (unit: μs) |
+| avg_update_elapse   | bigint | Average response time of **UPDATE** statements (unit: μs) |
+| total_insert_elapse | bigint | Total response time of **INSERT** statements (unit: μs)   |
+| max_insert_elapse   | bigint | Maximum response time of **INSERT** statements (unit: μs) |
+| min_insert_elapse   | bigint | Minimum response time of **INSERT** statements (unit: μs) |
+| avg_insert_elapse   | bigint | Average response time of **INSERT** statements (unit: μs) |
+| total_delete_elapse | bigint | Total response time of **DELETE** statements (unit: μs)   |
+| max_delete_elapse   | bigint | Maximum response time of **DELETE** statements (unit: μs) |
+| min_delete_elapse   | bigint | Minimum response time of **DELETE** statements (unit: μs) |
+| avg_delete_elapse   | bigint | Average response time of **DELETE** statements (unit: μs) |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/WORKLOAD_TRANSACTION.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/WORKLOAD_TRANSACTION.md
new file mode 100644
index 0000000000000000000000000000000000000000..351ded37dfe9ed03d3ed905e936e48684c7f3056
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/WORKLOAD_TRANSACTION.md
@@ -0,0 +1,28 @@
+---
+title: WORKLOAD_TRANSACTION
+summary: WORKLOAD_TRANSACTION
+author: Guo Huan
+date: 2021-04-19
+---
+
+# WORKLOAD_TRANSACTION
+
+**WORKLOAD_TRANSACTION** displays information about transactions loaded on the current node.
+
+**Table 1** WORKLOAD_TRANSACTION columns
+
+| Name                | Type   | Description                                                 |
+| :------------------ | :----- | :---------------------------------------------------------- |
+| workload            | name   | Workload name                                               |
+| commit_counter      | bigint | Number of user transactions committed                       |
+| rollback_counter    | bigint | Number of user transactions rolled back                     |
+| resp_min            | bigint | Minimum response time of user transactions (unit: μs)       |
+| resp_max            | bigint | Maximum response time of user transactions (unit: μs)       |
+| resp_avg            | bigint | Average response time of user transactions (unit: μs)       |
+| resp_total          | bigint | Total response time of user transactions (unit: μs)         |
+| bg_commit_counter   | bigint | Number of background transactions committed                 |
+| bg_rollback_counter | bigint | Number of background transactions rolled back               |
+| bg_resp_min         | bigint | Minimum response time of background transactions (unit: μs) |
+| bg_resp_max         | bigint | Maximum response time of background transactions (unit: μs) |
+| bg_resp_avg         | bigint | Average response time of background transactions (unit: μs) |
+| bg_resp_total       | bigint | Total response time of background transactions (unit: μs)   |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.abort.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.abort.md
new file mode 100644
index 0000000000000000000000000000000000000000..0bad284c461620009ad227c63a256a5864146b1b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.abort.md
@@ -0,0 +1,23 @@
+---
+title: DBE_PLDEBUGGER.abort
+summary: DBE_PLDEBUGGER.abort
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DBE_PLDEBUGGER.abort
+
+This function is used to abort the stored procedure executed on the server and report an error. The return value indicates whether the abort message is successfully sent.
+
+The function prototype is as follows:
+
+```sql
+DBE_PLDEBUGGER.abort()
+RETURN boolean;
+```
+
+**Table 1** abort input parameters and return values
+
+| Name  | Type        | Description        |
+| :---- | :---------- | :----------------- |
+| abort | OUT boolean | Success or failure |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.add_breakpoint.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.add_breakpoint.md
new file mode 100644
index 0000000000000000000000000000000000000000..88c0a1a768babd8350694e6650f99d1c7452c0ee
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.add_breakpoint.md
@@ -0,0 +1,18 @@
+---
+title: DBE_PLDEBUGGER.add_breakpoint
+summary: DBE_PLDEBUGGER.add_breakpoint
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DBE_PLDEBUGGER.add_breakpoint
+
+During debugging on the debug end, call **add_breakpoint** to add a breakpoint. If **-1** is returned, the specified breakpoint is invalid. Determine the proper position of the breakpoint based on the **canbreak** column in [DBE_PLDEBUGGER.info_code](DBE_PLDEBUGGER.info_code).
+
+**Table 1** add_breakpoint input parameters and return values
+
+| Name         | Type        | Description       |
+| :----------- | :---------- | :---------------- |
+| funcoid      | IN text     | Function ID       |
+| lineno       | IN integer  | Line number       |
+| breakpointno | OUT integer | Breakpoint number |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.attach.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.attach.md
new file mode 100644
index 0000000000000000000000000000000000000000..e46b9bfd55923bf90b98308d11728f9f86fd74cd
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.attach.md
@@ -0,0 +1,23 @@
+---
+title: DBE_PLDEBUGGER.attach
+summary: DBE_PLDEBUGGER.attach
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DBE_PLDEBUGGER.attach
+
+When the server executes a stored procedure, the server hangs the execution before the first statement and waits for attaching with the debug end. The debug end invokes the attach function and transfers node name and port number to attach with the specified stored procedure.
+
+If an error is reported during debugging, the attach operation automatically becomes invalid. If the debug end is attached to another stored procedure during debugging, the debugging of the attached stored procedure becomes invalid.
+
+**Table 1** attach input parameters and return values
+
+| Name     | Type        | Description                                                  |
+| :------- | :---------- | :----------------------------------------------------------- |
+| nodename | IN text     | Node name                                                    |
+| port     | IN integer  | Number of the connected port                                 |
+| funcoid  | OUT oid     | Function ID                                                  |
+| funcname | OUT text    | Function name                                                |
+| lineno   | OUT integer | Number of the next line in the current debugging process     |
+| query    | OUT text    | Source code of the next line of the function that is being debugged |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.backtrace.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.backtrace.md
new file mode 100644
index 0000000000000000000000000000000000000000..f40ca8ec7b22d946e05853ef7a00787659e42503
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.backtrace.md
@@ -0,0 +1,20 @@
+---
+title: DBE_PLDEBUGGER.backtrace
+summary: DBE_PLDEBUGGER.backtrace
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DBE_PLDEBUGGER.backtrace
+
+During debugging on the debug end, call **backtrace** to view the current call stack.
+
+**Table 1** backtrace input parameters and return values
+
+| Name     | Type        | Description        |
+| :------- | :---------- | :----------------- |
+| frameno  | OUT integer | Call stack ID      |
+| funcname | OUT oid     | Function name      |
+| lineno   | OUT integer | Line number        |
+| query    | OUT text    | Breakpoint content |
+| funcoid  | OUT oid     | Function OID       |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.continue.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.continue.md
new file mode 100644
index 0000000000000000000000000000000000000000..dcfcb6af084afcda9e94288eabd09c969646f7ee
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.continue.md
@@ -0,0 +1,26 @@
+---
+title: DBE_PLDEBUGGER.continue
+summary: DBE_PLDEBUGGER.continue
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DBE_PLDEBUGGER.continue
+
+Executes the current stored procedure until reaching the next breakpoint or end, and returns the line number of the next execution and the corresponding query.
+
+The function prototype is as follows:
+
+```sql
+DBE_PLDEBUGGER.continue()
+RETURN Record;
+```
+
+**Table 1** continue input parameters and return values
+
+| Name     | Type        | Description                                                  |
+| :------- | :---------- | :----------------------------------------------------------- |
+| funcoid  | OUT oid     | Function ID                                                  |
+| funcname | OUT text    | Function name                                                |
+| lineno   | OUT integer | Number of the next line in the current debugging process     |
+| query    | OUT text    | Source code of the next line of the function that is being debugged |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.delete_breakpoint.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.delete_breakpoint.md
new file mode 100644
index 0000000000000000000000000000000000000000..dc53595a16306162f0181fe5b1f2265fafd98a9d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.delete_breakpoint.md
@@ -0,0 +1,17 @@
+---
+title: DBE_PLDEBUGGER.delete_breakpoint
+summary: DBE_PLDEBUGGER.delete_breakpoint
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DBE_PLDEBUGGER.delete_breakpoint
+
+During debugging on the debug end, call **delete_breakpoint** to delete the existing breakpoint.
+
+**Table 1** delete_breakpoint input parameters and return values
+
+| Name         | Type       | Description                                     |
+| :----------- | :--------- | :---------------------------------------------- |
+| breakpointno | IN integer | Breakpoint number                               |
+| result       | OUT bool   | Specifies whether this operation is successful. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.finish.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.finish.md
new file mode 100644
index 0000000000000000000000000000000000000000..4711366fb00ff07b87d4055eb2413c76b7a90dfa
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.finish.md
@@ -0,0 +1,19 @@
+---
+title: DBE_PLDEBUGGER.finish
+summary: DBE_PLDEBUGGER.finish
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DBE_PLDEBUGGER.finish
+
+Executes the current SQL statement in the stored procedure until the next breakpoint is triggered or the next line of the upper-layer stack is executed.
+
+**Table 1** finish input parameters and return values
+
+| Name     | Type        | Description                                                  |
+| :------- | :---------- | :----------------------------------------------------------- |
+| funcoid  | OUT oid     | Function ID                                                  |
+| funcname | OUT text    | Function name                                                |
+| lineno   | OUT integer | Number of the next line in the current debugging process     |
+| query    | OUT text    | Source code of the next line of the function that is being debugged |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.info_breakpoints.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.info_breakpoints.md
new file mode 100644
index 0000000000000000000000000000000000000000..c636fb8f856b7a79cde1c94bd374980e4aa2c7c2
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.info_breakpoints.md
@@ -0,0 +1,19 @@
+---
+title: DBE_PLDEBUGGER.info_breakpoints
+summary: DBE_PLDEBUGGER.info_breakpoints
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DBE_PLDEBUGGER.info_breakpoints
+
+During debugging on the debug end, call **info_breakpoints** to view the current function breakpoint.
+
+**Table 1** info_breakpoints input parameters and return values
+
+| Name         | Type        | Description        |
+| :----------- | :---------- | :----------------- |
+| breakpointno | OUT integer | Breakpoint number  |
+| funcoid      | OUT oid     | Function ID        |
+| lineno       | OUT integer | Line number        |
+| query        | OUT text    | Breakpoint content |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.info_code.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.info_code.md
new file mode 100644
index 0000000000000000000000000000000000000000..1e57aa96d822342f1074de78138610f42e80351c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.info_code.md
@@ -0,0 +1,19 @@
+---
+title: DBE_PLDEBUGGER.info_code
+summary: DBE_PLDEBUGGER.info_code
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DBE_PLDEBUGGER.info_code
+
+During debugging on the debug end, **info_code** is invoked to view the source statement of the specified stored procedure and the line number corresponding to each line. The line number starts from the function body, and the line number in the function header is empty.
+
+**Table 1** info_code input parameters and return values
+
+| Name     | Type        | Description                                              |
+| :------- | :---------- | :------------------------------------------------------- |
+| funcoid  | IN oid      | Function ID                                              |
+| lineno   | OUT integer | Line number                                              |
+| query    | OUT text    | Source statement                                         |
+| canbreak | OUT bool    | Specifies whether the current line supports breakpoints. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.local_debug_server_info.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.local_debug_server_info.md
new file mode 100644
index 0000000000000000000000000000000000000000..11a9b42aebebbfe86181e70191579cfcf6ce8507
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.local_debug_server_info.md
@@ -0,0 +1,18 @@
+---
+title: DBE_PLDEBUGGER.local_debug_server_info
+summary: DBE_PLDEBUGGER.local_debug_server_info
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DBE_PLDEBUGGER.local_debug_server_info
+
+This function is used to query the OID of the stored procedure that has been turned on in the current connection. You can use **funcoid** and **pg_proc** together to determine which stored procedures are to be debugged.
+
+**Table 1** local_debug_server_info returned input parameters and return values
+
+| Name     | Type       | Description          |
+| :------- | :--------- | :------------------- |
+| nodename | OUT text   | Node name            |
+| port     | OUT bigint | Port number          |
+| funcoid  | OUT oid    | Stored procedure OID |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.next.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.next.md
new file mode 100644
index 0000000000000000000000000000000000000000..15f456853acb2d2381bb0c0045761a08be7df6d8
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.next.md
@@ -0,0 +1,19 @@
+---
+title: DBE_PLDEBUGGER.next
+summary: DBE_PLDEBUGGER.next
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DBE_PLDEBUGGER.next
+
+This function is used to execute the current SQL statement in a stored procedure and return the number of the next SQL statement and the corresponding query.
+
+**Table 1** next input parameters and return values
+
+| Name     | Type        | Description                                                  |
+| :------- | :---------- | :----------------------------------------------------------- |
+| funcoid  | OUT oid     | Function ID                                                  |
+| funcname | OUT text    | Function name                                                |
+| lineno   | OUT integer | Number of the next line in the current debugging process     |
+| query    | OUT text    | Source code of the next line of the function that is being debugged |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.print_var.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.print_var.md
new file mode 100644
index 0000000000000000000000000000000000000000..902c7a849963ad8630427beed743598350b390cd
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.print_var.md
@@ -0,0 +1,22 @@
+---
+title: DBE_PLDEBUGGER.print_var
+summary: DBE_PLDEBUGGER.print_var
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DBE_PLDEBUGGER.print_var
+
+During debugging on the debug end, **print_var** is invoked to print the name and value of the specified variable in the current stored procedure. The input parameter **frameno** of this function indicates the stack layer to be traversed. This function can be invoked without **frameno**. By default, the top-layer stack variable is queried.
+
+**Table 1** print_var input parameters and return values
+
+| Name         | Type                  | Description                                                  |
+| :----------- | :-------------------- | :----------------------------------------------------------- |
+| var_name     | IN text               | Variable                                                     |
+| frameno      | IN integer (optional) | Specified stack layer. The default value is the top layer.   |
+| varname      | OUT text              | Variable name                                                |
+| vartype      | OUT text              | Variable type                                                |
+| value        | OUT text              | Variable value                                               |
+| package_name | OUT text              | Package name corresponding to the variable. This parameter is reserved and is left empty currently. |
+| isconst      | OUT boolean           | Whether it is a constant                                     |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.set_var.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.set_var.md
new file mode 100644
index 0000000000000000000000000000000000000000..df9932ead942b4b070d05f952b35108ec5782d07
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.set_var.md
@@ -0,0 +1,18 @@
+---
+title: DBE_PLDEBUGGER.set_var
+summary: DBE_PLDEBUGGER.set_var
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DBE_PLDEBUGGER.set_var
+
+Changes the variable on the top-layer stack in the specified debugging stored procedure to the value of the input parameter. If a stored procedure contains variables with the same name, set_var supports only the setting of the first variable value.
+
+**Table 1** set_var input parameters and return values
+
+| Name     | Type        | Description                 |
+| :------- | :---------- | :-------------------------- |
+| var_name | IN text     | Variable name               |
+| value    | IN text     | New value                   |
+| result   | OUT boolean | Result (success or failure) |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.step.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.step.md
new file mode 100644
index 0000000000000000000000000000000000000000..625c8f250f0cc280eb7f4ed58faa57f9f6a66ddf
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.step.md
@@ -0,0 +1,19 @@
+---
+title: DBE_PLDEBUGGER.step
+summary: DBE_PLDEBUGGER.step
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DBE_PLDEBUGGER.step
+
+During debugging on the debug end, if a stored procedure is being executed, the stored procedure continues to be executed and information such as the line number in the first line of the stored procedure is returned. If the executed object is not a stored procedure, the return is the same as that for **next**. After the SQL statement is executed, information such as the line number in the next line is returned.
+
+**Table 1** step input parameters and return values
+
+| Name     | Type        | Description                                                  |
+| :------- | :---------- | :----------------------------------------------------------- |
+| funcoid  | OUT oid     | Function ID                                                  |
+| funcname | OUT text    | Function name                                                |
+| lineno   | OUT integer | Number of the next line in the current debugging process     |
+| query    | OUT text    | Source code of the next line of the function that is being debugged |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.turn_off.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.turn_off.md
new file mode 100644
index 0000000000000000000000000000000000000000..42f2c1efbc6383a40fa5df37946e8b1f2800585f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.turn_off.md
@@ -0,0 +1,24 @@
+---
+title: DBE_PLDEBUGGER.turn_off
+summary: DBE_PLDEBUGGER.turn_off
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DBE_PLDEBUGGER.turn_off
+
+This function is used to remove the debugging flag added by **turn_on**. The return value indicates success or failure. You can run the **DBE_PLDEBUGGER.local_debug_server_info** command to query the OID of the stored procedure that has been turned on.
+
+The function prototype is as follows:
+
+```sql
+DBE_PLDEBUGGER.turn_off(Oid)
+RETURN boolean;
+```
+
+**Table 1** turn_off input parameters and return values
+
+| Name     | Type        | Description                    |
+| :------- | :---------- | :----------------------------- |
+| func_oid | IN oid      | Function OID                   |
+| turn_off | OUT boolean | Whether turn-off is successful |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.turn_on.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.turn_on.md
new file mode 100644
index 0000000000000000000000000000000000000000..3a0070f0a25987478f580046c08163d083e34fd4
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.turn_on.md
@@ -0,0 +1,25 @@
+---
+title: DBE_PLDEBUGGER.turn_on
+summary: DBE_PLDEBUGGER.turn_on
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DBE_PLDEBUGGER.turn_on
+
+This function is used to mark a stored procedure as debuggable. After **turn_on** is executed, the server can execute the stored procedure for debugging. You need to manually obtain the OID of the stored procedure based on the PG_PROC system catalog and transfer it to the function. After **turn_on** is executed, the execution of the stored procedure in the current session is hung before the first SQL statement to wait for the debugging instruction from the debug end. This setting is cleared by default after the session is disconnected. Currently, stored procedures and functions with autonomous transactions enabled cannot be debugged.
+
+The function prototype is as follows:
+
+```sql
+DBE_PLDEBUGGER.turn_on(Oid)
+RETURN Record;
+```
+
+**Table 1** turn_on input parameters and return values
+
+| Name     | Type        | Description                  |
+| :------- | :---------- | :--------------------------- |
+| func_oid | IN oid      | Function OID                 |
+| nodename | OUT text    | Node name                    |
+| port     | OUT integer | Number of the connected port |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/overview-of-DBE_PLDEBUGGER-schema.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/overview-of-DBE_PLDEBUGGER-schema.md
new file mode 100644
index 0000000000000000000000000000000000000000..fda592c9bc4db207dc0dac7b4b3901e2c565e14e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/overview-of-DBE_PLDEBUGGER-schema.md
@@ -0,0 +1,128 @@
+---
+title: Overview of DBE_PLDEBUGGER Schema
+summary: Overview of DBE_PLDEBUGGER Schema
+author: Guo Huan
+date: 2021-11-15
+---
+
+# Overview of DBE_PLDEBUGGER Schema
+
+DBE_PLDEBUGGER system functions are used to debug stored procedures in a standalone system. This chapter describes the interfaces supported by DBE_PLDEBUGGER. Only the administrator has the permission to execute these debugging interfaces.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** When a user is created in the function body, the plaintext password is returned when attach, next, continue, info_code, step, info_breakpoint, backtrace or finish is called. You are not advised to create a user in the function body.
+
+The administrator can run the following command to grant the **gs_role_pldebugger** role and debugger permissions to a user:
+
+```sql
+GRANT gs_role_pldebugger to user;
+```
+
+Two clients are required to connect to the database. One client is responsible for executing the debugging interface as the debug end, and the other client is responsible for executing the debugging function to control the execution of stored procedures on the server. The following is an example.
+
+- Prepare for debugging.
+
+  Use PG_PROC to find the OID of the stored procedure to be debugged and execute **DBE_PLDEBUGGER.turn_on(oid)**. In this case, the client functions as the server.
+
+  ```sql
+  mogdb=# CREATE OR REPLACE PROCEDURE test_debug ( IN  x INT)
+  AS
+  BEGIN
+        INSERT INTO t1 (a) VALUES (x);
+  END;
+  /
+  CREATE PROCEDURE
+  mogdb=# SELECT OID FROM PG_PROC WHERE PRONAME='test_debug';
+    oid
+  -------
+   16389
+  (1 row)
+  mogdb=# SELECT * FROM DBE_PLDEBUGGER.turn_on(16389);
+   nodename | port
+  ----------+------
+   datanode |    0
+  (1 row)
+  ```
+
+- Start debugging.
+
+  When the server executes the stored procedure, the server hangs before the first SQL statement in the stored procedure and waits for the debugging message sent by the debug end. Debugging is supported only by directly executing a stored procedure and cannot be achieved by invoking an executed stored procedure through a trigger.
+
+  ```sql
+  mogdb=# call test_debug(1);
+  ```
+
+  Start another client as the debug end and invoke **DBE_PLDEBUGGER.attach** to attach with the stored procedure for debugging based on the data returned by **turn_on**.
+
+  ```sql
+  mogdb=# SELECT * FROM DBE_PLDEBUGGER.attach('datanode',0);
+   funcoid |  funcname  | lineno |              query
+  ---------+------------+--------+----------------------------------
+     16389 | test_debug |      3 |   INSERT INTO t1 (a) VALUES (x);
+  (1 row)
+  ```
+
+  Execute the next statement on the client where the attach operation is performed.
+
+  ```sql
+  mogdb=# SELECT * FROM DBE_PLDEBUGGER.next();
+   funcoid |  funcname  | lineno |        query
+  ---------+------------+--------+----------------------
+     16389 | test_debug |      0 | [EXECUTION FINISHED]
+  (1 row)
+  ```
+
+  Output all the current variables on the client where the attach command is executed.
+
+  ```sql
+  mogdb=# SELECT * FROM DBE_PLDEBUGGER.info_locals();
+   varname | vartype | value | package_name
+  ---------+---------+-------+--------------
+   $1      | int4    | 1     |
+  (1 row)
+  ```
+
+  Directly execute the stored procedure that is being debugged.
+
+  ```sql
+  mogdb=# SELECT * FROM DBE_PLDEBUGGER.continue();
+   funcoid |  funcname  | lineno |        query
+  ---------+------------+--------+----------------------
+     16389 | test_debug |      0 | [EXECUTION FINISHED]
+  (1 row)
+  ```
+
+  Exit the stored procedure that is being debugged and do not execute statements that have not been executed before.
+
+  ```sql
+  mogdb=# SELECT * FROM DBE_PLDEBUGGER.abort();
+   abort
+  -------
+   t
+  (1 row)
+  ```
+
+  After the stored procedure is executed, the debugging automatically exits. To debug the stored procedure again, you need to attach again. If the server does not need to be debugged, run the **turn_off** command to disable the debugging or exit the session. For details about the debugging interfaces, see the following table.
+
+  **Table 1** DBE_PLDEBUGGER
+
+  | Interface                                                    | Description                                                  |
+  | :----------------------------------------------------------- | :----------------------------------------------------------- |
+  | [DBE_PLDEBUGGER.turn_on](DBE_PLDEBUGGER.turn_on)             | Invoked by the server, indicating that the stored procedure can be debugged. After the interface is invoked, the stored procedure is hung to wait for debugging information. |
+  | [DBE_PLDEBUGGER.turn_off](DBE_PLDEBUGGER.turn_off)           | Invoked by the server, indicating that debugging the stored procedure is disabled. |
+  | [DBE_PLDEBUGGER.local_debug_server_info](DBE_PLDEBUGGER.local_debug_server_info) | Invoked by the server to print all stored procedures that have been turned on in the current session. |
+  | [DBE_PLDEBUGGER.attach](DBE_PLDEBUGGER.attach)               | Invoked by the debug end to attach with the stored procedure that is being debugged. |
+  | [DBE_PLDEBUGGER.info_locals](DBE_PLDEBUGGER.info_locals)     | Invoked by the debug end to print the current values of variables in the stored procedure that is being debugged. |
+  | [DBE_PLDEBUGGER.next](DBE_PLDEBUGGER.next)                   | Invoked by the debug end to execute the next step.           |
+  | [DBE_PLDEBUGGER.continue](DBE_PLDEBUGGER.continue)           | Invoked by the debug end to continue the execution until the breakpoint or stored procedure ends. |
+  | [DBE_PLDEBUGGER.abort](DBE_PLDEBUGGER.abort)                 | Invoked by the debug end to stop debugging. The server reports a long jump error. |
+  | [DBE_PLDEBUGGER.print_var](DBE_PLDEBUGGER.print_var)         | Invoked by the debug end to print the current values of specified variables in the stored procedure that is being debugged. |
+  | [DBE_PLDEBUGGER.info_code](DBE_PLDEBUGGER.info_code)         | Invoked by the debug end or server to print the source statement of a specified stored procedure and the line number corresponding to each line. |
+  | [DBE_PLDEBUGGER.step](DBE_PLDEBUGGER.step)                   | Invoked by the debug end to execute step by step.            |
+  | [DBE_PLDEBUGGER.add_breakpoint](DBE_PLDEBUGGER.add_breakpoint) | Invoked by the debug end to add a breakpoint.                |
+  | [DBE_PLDEBUGGER.delete_breakpoint](DBE_PLDEBUGGER.delete_breakpoint) | Invoked by the debug end to delete a breakpoint.             |
+  | [DBE_PLDEBUGGER.info_breakpoints](DBE_PLDEBUGGER.info_breakpoints) | Invoked by the debug end to view all breakpoints.            |
+  | [DBE_PLDEBUGGER.backtrace](DBE_PLDEBUGGER.backtrace)         | Invoked by the debug end to check the current call stack.    |
+  | [DBE_PLDEBUGGER.enable_breakpoint](DBE_PLDEBUGGER.enable_breakpoint) | Invoked by the debug end to enable breakpoints.              |
+  | [DBE_PLDEBUGGER.disable_breakpoint](DBE_PLDEBUGGER.disable_breakpoint) | Invoked by the debug end to disable breakpoints.             |
+  | [DBE_PLDEBUGGER.finish](DBE_PLDEBUGGER.finish)               | Invoked by the debug end to continue the debugging until the breakpoint is reached or the upper-layer call stack is returned. |
+  | [DBE_PLDEBUGGER.set_var](DBE_PLDEBUGGER.set_var)             | Invoked by the debug end to assign a value to a variable.    |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/information-schema/1-information-schema-overview.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/information-schema/1-information-schema-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..a09727b057cdb2d3cb1909b011b58979bfca6160
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/information-schema/1-information-schema-overview.md
@@ -0,0 +1,18 @@
+---
+title: Overview
+summary: Overview
+author: Guo Huan
+date: 2021-06-23
+---
+
+# Overview
+
+An information schema named **INFORMATION_SCHEMA** automatically exists in all databases. An information schema consists of a group of views that contain information about objects defined in the current database. The owner of this schema is the initial database user, and the user naturally has all the privileges on this schema, including the ability to delete the schema.
+
+Information schemas are inherited from the open-source PGXC and PG. For details, visit the following links to see the official PGXC and PG documents:
+
+<http://postgres-xc.sourceforge.net/docs/1_1/information-schema.html>
+
+<https://www.postgresql.org/docs/9.2/information-schema.html>
+
+The following sections display only the views that are not listed in the preceding links.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/information-schema/2-_PG_FOREIGN_DATA_WRAPPERS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/information-schema/2-_PG_FOREIGN_DATA_WRAPPERS.md
new file mode 100644
index 0000000000000000000000000000000000000000..83233401323cdca5eb286d4437e9d3187575f4d9
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/information-schema/2-_PG_FOREIGN_DATA_WRAPPERS.md
@@ -0,0 +1,22 @@
+---
+title: _PG_FOREIGN_DATA_WRAPPERS
+summary: _PG_FOREIGN_DATA_WRAPPERS
+author: Guo Huan
+date: 2021-06-23
+---
+
+# _PG_FOREIGN_DATA_WRAPPERS
+
+**_PG_FOREIGN_DATA_WRAPPERS** displays information about a foreign-data wrapper. Only the sysadmin user has the permission to view this view.
+
+**Table 1** _PG_FOREIGN_DATA_WRAPPERS columns
+
+| Name                          | Type                              | Description                                                  |
+| ----------------------------- | --------------------------------- | ------------------------------------------------------------ |
+| oid                           | oid                               | OID of the foreign-data wrapper                              |
+| fdwowner                      | oid                               | OID of the owner of the foreign-data wrapper                 |
+| fdwoptions                    | text[]                            | Foreign-data wrapper specific option, expressed in a string in the format of **keyword=value** |
+| foreign_data_wrapper_catalog  | information_schema.sql_identifier | Name of the database where the foreign-data wrapper is located (always the current database) |
+| foreign_data_wrapper_name     | information_schema.sql_identifier | Name of the foreign-data wrapper                             |
+| authorization_identifier      | information_schema.sql_identifier | Role of the owner of the foreign-data wrapper                |
+| foreign_data_wrapper_language | information_schema.character_data | Programming language of the foreign-data wrapper             |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/information-schema/3-_PG_FOREIGN_SERVERS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/information-schema/3-_PG_FOREIGN_SERVERS.md
new file mode 100644
index 0000000000000000000000000000000000000000..1bf011915424983ed2eb8f4708377d50344ed30e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/information-schema/3-_PG_FOREIGN_SERVERS.md
@@ -0,0 +1,24 @@
+---
+title: _PG_FOREIGN_SERVERS
+summary: _PG_FOREIGN_SERVERS
+author: Guo Huan
+date: 2021-06-23
+---
+
+# _PG_FOREIGN_SERVERS
+
+**_PG_FOREIGN_SERVERS** displays information about a foreign server. Only the sysadmin user has the permission to view this view.
+
+**Table 1** _PG_FOREIGN_SERVERS columns
+
+| Name                         | Type                              | Description                                                  |
+| ---------------------------- | --------------------------------- | ------------------------------------------------------------ |
+| oid                          | oid                               | OID of the foreign server                                    |
+| srvoptions                   | text[]                            | Foreign server specific options, expressed in a string in the format of *keyword***=***value* |
+| foreign_server_catalog       | information_schema.sql_identifier | Name of the database where the foreign server is located (always the current database) |
+| foreign_server_name          | information_schema.sql_identifier | Name of the foreign server                                   |
+| foreign_data_wrapper_catalog | information_schema.sql_identifier | Name of the database where the foreign-data wrapper is located (always the current database) |
+| foreign_data_wrapper_name    | information_schema.sql_identifier | Name of the foreign-data wrapper                             |
+| foreign_server_type          | information_schema.character_data | Type of the foreign server                                   |
+| foreign_server_version       | information_schema.character_data | Version of the foreign server                                |
+| authorization_identifier     | information_schema.sql_identifier | Role of the owner of the foreign server                      |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/information-schema/4-_PG_FOREIGN_TABLE_COLUMNS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/information-schema/4-_PG_FOREIGN_TABLE_COLUMNS.md
new file mode 100644
index 0000000000000000000000000000000000000000..2037e95d9a05d70d476bcbe26c2a95c76fc03527
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/information-schema/4-_PG_FOREIGN_TABLE_COLUMNS.md
@@ -0,0 +1,19 @@
+---
+title: _PG_FOREIGN_TABLE_COLUMNS
+summary: _PG_FOREIGN_TABLE_COLUMNS
+author: Guo Huan
+date: 2021-06-23
+---
+
+# _PG_FOREIGN_TABLE_COLUMNS
+
+**_PG_FOREIGN_TABLE_COLUMNS** displays column information about a foreign table. Only the sysadmin user has the permission to view this view.
+
+**Table 1** _PG_FOREIGN_TABLE_COLUMNS columns
+
+| Name          | Type   | Description                                                  |
+| ------------- | ------ | ------------------------------------------------------------ |
+| nspname       | name   | Schema name                                                  |
+| relname       | name   | Table name                                                   |
+| attname       | name   | Column name                                                  |
+| attfdwoptions | text[] | Attribute-level foreign data wrapper options, expressed in a string in the format of *keyword***=***value* |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/information-schema/5-_PG_FOREIGN_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/information-schema/5-_PG_FOREIGN_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..524bfab9f25e70f920dc573f1b78737177cfa2a8
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/information-schema/5-_PG_FOREIGN_TABLES.md
@@ -0,0 +1,22 @@
+---
+title: _PG_FOREIGN_TABLES
+summary: _PG_FOREIGN_TABLES
+author: Guo Huan
+date: 2021-06-23
+---
+
+# _PG_FOREIGN_TABLES
+
+**_PG_FOREIGN_TABLES** stores information about all foreign tables defined in the current database, whereas displays information about foreign tables accessible to the current user. Only the sysadmin user has the permission to view this view.
+
+**Table 1** _PG_FOREIGN_TABLES columns
+
+| Name                     | Type                              | Description                                                  |
+| ------------------------ | --------------------------------- | ------------------------------------------------------------ |
+| foreign_table_catalog    | information_schema.sql_identifier | Name of the database where the foreign table is located (always the current database) |
+| foreign_table_schema     | name                              | Name of the schema that the foreign table is in              |
+| foreign_table_name       | name                              | Name of the foreign table                                    |
+| ftoptions                | text[]                            | Foreign table options                                        |
+| foreign_server_catalog   | information_schema.sql_identifier | Name of the database where the foreign server is located (always the current database) |
+| foreign_server_name      | information_schema.sql_identifier | Name of the foreign server                                   |
+| authorization_identifier | information_schema.sql_identifier | Role of the owner                                            |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/information-schema/6-_PG_USER_MAPPINGS.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/information-schema/6-_PG_USER_MAPPINGS.md
new file mode 100644
index 0000000000000000000000000000000000000000..7f5f31fc5230bd50933ee008c6244261e42e826f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/information-schema/6-_PG_USER_MAPPINGS.md
@@ -0,0 +1,22 @@
+---
+title: _PG_USER_MAPPINGS
+summary: _PG_USER_MAPPINGS
+author: Guo Huan
+date: 2021-06-23
+---
+
+# _PG_USER_MAPPINGS
+
+**_PG_USER_MAPPINGS** stores mappings from local users to remote users. Only the sysadmin user has the permission to view this view.
+
+**Table 1** _PG_USER_MAPPINGS columns
+
+| Name                     | Type                              | Description                                                  |
+| ------------------------ | --------------------------------- | ------------------------------------------------------------ |
+| oid                      | oid                               | OID of the mapping from the local user to a remote user      |
+| umoptions                | text[]                            | User mapping specific options, expressed in a string in the format of *keyword***=***value* |
+| umuser                   | oid                               | OID of the local user being mapped (**0** if the user mapping is public) |
+| authorization_identifier | information_schema.sql_identifier | Role of the local user                                       |
+| foreign_server_catalog   | information_schema.sql_identifier | Name of the database where the foreign server is defined in  |
+| foreign_server_name      | information_schema.sql_identifier | Name of the foreign server                                   |
+| srvowner                 | information_schema.sql_identifier | Owner of the foreign server                                  |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/schema/information-schema/7-INFORMATION_SCHEMA_CATALOG_NAME.md b/product/en/docs-mogdb/v3.0/reference-guide/schema/information-schema/7-INFORMATION_SCHEMA_CATALOG_NAME.md
new file mode 100644
index 0000000000000000000000000000000000000000..b92c4eaa367c977c50f8fd95c96e76570d7bbb3f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/schema/information-schema/7-INFORMATION_SCHEMA_CATALOG_NAME.md
@@ -0,0 +1,16 @@
+---
+title: INFORMATION_SCHEMA_CATALOG_NAME
+summary: INFORMATION_SCHEMA_CATALOG_NAME
+author: Guo Huan
+date: 2021-06-23
+---
+
+# INFORMATION_SCHEMA_CATALOG_NAME
+
+**INFORMATION_SCHEMA_CATALOG_NAME** displays the name of the current database.
+
+**Table 1** INFORMATION_SCHEMA_CATALOG_NAME columns
+
+| Name         | Type                              | Description           |
+| :----------- | :-------------------------------- | :-------------------- |
+| catalog_name | information_schema.sql_identifier | Current database name |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/1-mogdb-sql.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/1-mogdb-sql.md
new file mode 100644
index 0000000000000000000000000000000000000000..b1a21be045ac1a93c31461d44903cecd79b3bb2f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/1-mogdb-sql.md
@@ -0,0 +1,37 @@
+---
+title: MogDB SQL
+summary: MogDB SQL
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# MogDB SQL
+
+## What Is SQL?
+
+SQL is a standard computer language used to control the access to databases and manage data in databases.
+
+SQL provides different statements to enable you to:
+
+- Query data.
+- Insert, update, and delete rows.
+- Create, replace, modify, and delete objects.
+- Control the access to a database and its objects.
+- Maintain the consistency and integrity of a database.
+
+SQL consists of commands and functions that are used to manage databases and database objects. SQL can also forcibly implement the rules for data types, expressions, and texts. Therefore, **SQL Reference** describes data types, expressions, functions, and operators in addition to SQL syntax.
+
+## Development of SQL Standards
+
+The development history of SQL standards is as follows:
+
+- 1986: ANSI X3.135-1986, ISO/IEC 9075:1986, SQL-86
+- 1989: ANSI X3.135-1989, ISO/IEC 9075:1989, SQL-89
+- 1992: ANSI X3.135-1992, ISO/IEC 9075:1992, SQL-92 (SQL2)
+- 1999: ISO/IEC 9075:1999, SQL:1999 (SQL3)
+- 2003: ISO/IEC 9075:2003, SQL:2003 (SQL4)
+- 2011: ISO/IEC 9075:200N, SQL:2011 (SQL5)
+
+## SQL Standards Supported by MogDB
+
+MogDB supports major SQL2, SQL3, and SQL4 features by default.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/10-dml-syntax-overview.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/10-dml-syntax-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..ce6687f4d3017ce7041142c218c9970d3e1c6e4d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/10-dml-syntax-overview.md
@@ -0,0 +1,51 @@
+---
+title: DML Syntax Overview
+summary: DML Syntax Overview
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# DML Syntax Overview
+
+Data manipulation language (DML) is used to perform operations on data in database tables, such as inserting, updating, querying, or deleting data.
+
+## Inserting Data
+
+Inserting data refers to adding one or multiple records to a database table. For details, see [INSERT](109-INSERT).
+
+## Updating Data
+
+Updating data refers to modifying one or multiple records in a database table. For details, see [UPDATE](136-UPDATE).
+
+## Querying Data
+
+The database query statement **SELECT** is used to search required information in a database. For details, see [SELECT](125-SELECT).
+
+## Deleting Data
+
+MogDB provides two statements for deleting data from database tables. To delete data meeting specified conditions from a database table, see [DELETE](74-DELETE). To delete all data from a database table, see [TRUNCATE](135-TRUNCATE).
+
+**TRUNCATE** can quickly delete all data from a database table, which achieves the effect same as that running **DELETE** to delete data without specifying conditions from each table. Deletion efficiency using **TRUNCATE** is faster because **TRUNCATE** does not scan tables. Therefore, **TRUNCATE** is useful in large tables.
+
+## Copying Data
+
+MogDB provides a statement for copying data between tables and files. For details, see [COPY](41-COPY).
+
+## Locking a Table
+
+MogDB provides multiple lock modes to control concurrent accesses to table data. For details, see [LOCK](110-LOCK).
+
+## Calling a Function
+
+MogDB provides three statements for calling functions. These statements are the same in the syntax structure. For details, see [CALL](34-CALL).
+
+## Session Management
+
+A session is a connection established between the user and the database. [Table 1](#sqlstatement) lists the related SQL statements.
+
+**Table 1** SQL statements related to sessions <a id="sqlstatement"></a>
+
+| Function           | SQL Statement                                             |
+| :----------------- | :-------------------------------------------------------- |
+| Altering a session | [ALTER SESSION](18-ALTER-SESSION)                         |
+| Killing a session  | [ALTER SYSTEM KILL SESSION](20-ALTER-SYSTEM-KILL-SESSION) |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/11-dcl-syntax-overview.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/11-dcl-syntax-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..926ccbb22436db2a5fe4f167b18fffb32096ecbb
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/11-dcl-syntax-overview.md
@@ -0,0 +1,50 @@
+---
+title: DCL Syntax Overview
+summary: DCL Syntax Overview
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# DCL Syntax Overview
+
+Data control language (DCL) is used to create users and roles and set or modify database users or role rights.
+
+## Defining a Role
+
+A role is used to manage permissions. For database security, management and operation permissions can be granted to different roles. For details about related SQL statements, see [Table 1](#sqlstatement1).
+
+**Table 1** SQL statements for defining a role<a id="sqlstatement1"></a>
+
+| Description              | SQL Statement                 |
+| :----------------------- | :---------------------------- |
+| Creating a role          | [CREATE ROLE](54-CREATE-ROLE) |
+| Altering role attributes | [ALTER ROLE](12-ALTER-ROLE)   |
+| Dropping a role          | [DROP ROLE](89-DROP-ROLE)     |
+
+## Defining a User
+
+A user is used to log in to a database. Different permissions can be granted to users for managing data accesses and operations of the users. For details about related SQL statements, see [Table 2](#sqlstatement2).
+
+**Table 2** SQL statements for defining a user<a id="sqlstatement2"></a>
+
+| Description              | SQL Statement                 |
+| :----------------------- | :---------------------------- |
+| Creating a User          | [CREATE USER](68-CREATE-USER) |
+| Altering user attributes | [ALTER USER](29-ALTER-USER)   |
+| Dropping a user          | [DROP USER](101-DROP-USER)    |
+
+## Granting Rights
+
+MogDB provides a statement for granting rights to data objects and roles. For details, see [GRANT](108-GRANT).
+
+## Revoking Rights
+
+MogDB provides a statement for revoking rights. For details, see [REVOKE](120-REVOKE).
+
+## Setting Default Rights
+
+MogDB allows users to set rights for objects that will be created. For details, see [ALTER DEFAULT PRIVILEGES](4-ALTER-DEFAULT-PRIVILEGES).
+
+## Shutting Down The Current Node
+
+MogDB allows users to run the **shutdown** command to shut down the current database node. For details, see [SHUTDOWN](133-SHUTDOWN).
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/1-gin-indexes/1-introduction.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/1-gin-indexes/1-introduction.md
new file mode 100644
index 0000000000000000000000000000000000000000..b168203c2ea1503713f43152f628e9cb885c063e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/1-gin-indexes/1-introduction.md
@@ -0,0 +1,16 @@
+---
+title: Introduction
+summary: Introduction
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# Introduction
+
+Generalized Inverted Index (GIN) is designed for handling cases where the items to be indexed are composite values, and the queries to be handled by the index need to search for element values that appear within the composite items. For example, the items could be documents, and the queries could be searches for documents containing specific words.
+
+We use the word "item" to refer to a composite value that is to be indexed, and the word "key" to refer to an element value. GIN stores and searches for keys, not item values.
+
+A GIN index stores a set of (key, posting list) key-value pairs, where a posting list is a set of row IDs in which the key occurs. The same row ID can appear in multiple posting lists, since an item can contain more than one key. Each key value is stored only once, so a GIN index is very compact for cases where the same key appears many times.
+
+GIN is generalized in the sense that the GIN access method code does not need to know the specific operations that it accelerates. Instead, it uses custom strategies defined for particular data types. The strategy defines how keys are extracted from indexed items and query conditions, and how to determine whether a row that contains some of the key values in a query actually satisfies the query.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/1-gin-indexes/2-scalability.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/1-gin-indexes/2-scalability.md
new file mode 100644
index 0000000000000000000000000000000000000000..d88b6266bfbb927a7850e7f0794ceb7bb89a4228
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/1-gin-indexes/2-scalability.md
@@ -0,0 +1,50 @@
+---
+title: Scalability
+summary: Scalability
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# Scalability
+
+The GIN interface has a high level of abstraction, requiring the access method implementer only to implement the semantics of the data type being accessed. The GIN layer itself takes care of concurrency, logging and searching the tree structure.
+
+All it takes to get a GIN access method working is to implement multiple user-defined methods, which define the behavior of keys in the tree and the relationships between keys, indexed items, and indexable queries. In short, GIN combines extensibility with generality, code reuse, and a clean interface.
+
+There are four methods that an operator class for GIN must provide:
+
+- int compare(Datum a, Datum b)
+
+  Compares two keys (not indexed items) and returns an integer less than zero, zero, or greater than zero, indicating whether the first key is less than, equal to, or greater than the second. Null keys are never passed to this function.
+
+- Datum extractValue(Datum itemValue, int32 *nkeys, bool **nullFlags)
+
+  Returns an array of keys given an item to be indexed. The number of returned keys must be stored into ***nkeys**. If any of the keys can be null, also palloc an array of ***nkeys** bool fields, store its address at ***nullFlags**, and set these null flags as needed. ***nullFlags** can be left **NULL** (its initial value) if all keys are non-null. The returned value can be **NULL** if the item contains no keys.
+
+- Datum `extractQuery(Datum query, int32 *nkeys, StrategyNumber n, bool **pmatch, Pointer **extra_data, bool **nullFlags, int32 *searchMode)`
+
+  Returns a palloc'd array of keys given a value to be queried; that is, query is the value on the right-hand side of an indexable operator whose left-hand side is the indexed column. n is the strategy number of the operator within the operator class. Often, **extractQuery** will need to consult n to determine the data type of query and the method it should use to extract key values. The number of returned keys must be stored into ***nkeys**. If any of the keys can be null, also palloc an array of ***nkeys** bool fields, store its address at ***nullFlags**, and set these null flags as needed. ***nullFlags** can be left NULL (its initial value) if all keys are non-null. The returned value can be NULL if the query contains no keys.
+
+  **searchMode** is an output argument that allows **extractQuery** to specify details about how the search will be done. If ***searchMode** is set to **GIN_SEARCH_MODE_DEFAULT** (which is the value it is initialized to before call), only items that match at least one of the returned keys are considered candidate matches. If ***searchMode** is set to **GIN_SEARCH_MODE_INCLUDE_EMPTY**, then in addition to items containing at least one matching key, items that contain no keys at all are considered candidate matches. (This mode is useful for implementing is-subset-of operators, for example.) If ***searchMode** is set to **GIN_SEARCH_MODE_ALL**, then all non-null items in the index are considered candidate matches, whether they match any of the returned keys or not.
+
+  **pmatch** is an output argument for use when partial match is supported. To use it, **extractQuery** must allocate an array of nkeys Booleans and store its address at **pmatch**. Each element of the array should be set to **TRUE** if the corresponding key requires partial match, **FALSE** if not. If **pmatch** is set to **NULL** then GIN assumes partial match is not required. The variable is initialized to NULL before call, so this argument can simply be ignored by operator classes that do not support partial match.
+
+  **extra_data** is an output argument that allows **extractQuery** to pass additional data to the **consistent** and **comparePartial** methods. To use it, **extractQuery** must allocate an array of ***nkeys** pointers and store its address at ***extra_data**, then store whatever it wants to into the individual pointers. The variable is initialized to **NULL** before call, so this argument can simply be ignored by operator classes that do not require extra data. If ***extra_data** is set, the whole array is passed to the **consistent** method, and the appropriate element to the **comparePartial** method.
+
+- bool consistent(bool check[], StrategyNumber n, Datum query, int32 nkeys, Pointer extra_data[], bool *recheck, Datum queryKeys[], bool nullFlags[])
+
+  Returns **TRUE** if an indexed item satisfies the query operator with StrategyNumber **n** (or might satisfy it, if the recheck indication is returned). This function does not have direct access to the indexed item's value, since GIN does not store items explicitly. Rather, what is available is knowledge about which key values extracted from the query appear in a given indexed item. The check array has length **nkeys**, which is the same as the number of keys previously returned by **extractQuery** for this query datum. Each element of the check array is **TRUE** if the indexed item contains the corresponding query key, for example, if (check[i] == TRUE), the i-th key of the **extractQuery** result array is present in the indexed item. The original query datum is passed in case the **consistent** method needs to consult it, and so are the **queryKeys[]** and **nullFlags[]** arrays previously returned by **extractQuery**. **extra_data** is the extra-data array returned by **extractQuery**, or **NULL** if none.
+
+  When **extractQuery** returns a null key in **queryKeys[]**, the corresponding **check[]** element is **TRUE** if the indexed item contains a null key; that is, the semantics of **check[]** are like **IS NOT DISTINCT FROM**. The **consistent** function can examine the corresponding **nullFlags[]** element if it needs to tell the difference between a regular value match and a null match.
+
+  On success, ***recheck** should be set to **TRUE** if the heap tuple needs to be rechecked against the query operator, or **FALSE** if the index test is exact. That is, a **FALSE** return value guarantees that the heap tuple does not match the query; a **TRUE** return value with ***recheck** set to **FALSE** guarantees that the heap tuple matches the query; and a **TRUE** return value with ***recheck** set to **TRUE** means that the heap tuple might match the query, so it needs to be fetched and rechecked by evaluating the query operator directly against the originally indexed item.
+
+Optionally, an operator class for GIN can supply the following method:
+
+- int comparePartial(Datum partial_key, Datum key, StrategyNumber n, Pointer extra_data)
+
+  Compares a partial-match query key to an index key. Returns an integer whose sign indicates the result: less than zero means the index key does not match the query, but the index scan should continue; zero means that the index key matches the query; greater than zero indicates that the index scan should stop because no more matches are possible. The strategy number **n** of the operator that generated the partial match query is provided, in case its semantics are needed to determine when to end the scan. Also, **extra_data** is the corresponding element of the extra-data array made by **extractQuery**, or **NULL** if none. Null keys are never passed to this function.
+
+To support "partial match" queries, an operator class must provide the **comparePartial** method, and its **extractQuery** method must set the **pmatch** parameter when a partial-match query is encountered. For details, see [Partial Match Algorithm](3-implementation#partial-match-algorithm).
+
+The actual data types of the various Datum values mentioned in this section vary depending on the operator class. The item values passed to **extractValue** are always of the operator class's input type, and all key values must be of the class's **STORAGE** type. The type of the query argument passed to **extractQuery**, consistent and **triConsistent** is whatever is specified as the right-hand input type of the class member operator identified by the strategy number. This need not be the same as the item type, so long as key values of the correct type can be extracted from it.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/1-gin-indexes/3-implementation.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/1-gin-indexes/3-implementation.md
new file mode 100644
index 0000000000000000000000000000000000000000..6ad6cd4b9e3890d5ce280ab8cd08661d66bbaa62
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/1-gin-indexes/3-implementation.md
@@ -0,0 +1,24 @@
+---
+title: Implementation
+summary: Implementation
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# Implementation
+
+Internally, a GIN index contains a B-tree index constructed over keys, where each key is an element of one or more indexed items (a member of an array, for example) and where each tuple in a page contains either a pointer to a B-tree of heap pointers (a "posting tree"), or a simple list of heap pointers (a "posting list") when the list is small enough to fit into a single index tuple along with the key value.
+
+Multi-column GIN indexes are implemented by building a single B-tree over composite values (column number, key value). The key values for different columns can be of different types.
+
+## GIN Fast Update Technique
+
+Updating a GIN index tends to be slow because of the intrinsic nature of inverted indexes: inserting or updating one heap row can cause many inserts into the index. After the table is vacuumed or if the pending list becomes larger than **work_mem**, the entries are moved to the main GIN data structure using the same bulk insert techniques used during initial index creation. This greatly increases the GIN index update speed, even counting the additional vacuum overhead. Moreover the overhead work can be done by a background process instead of in foreground query processing.
+
+The main disadvantage of this approach is that searches must scan the list of pending entries in addition to searching the regular index, and so a large list of pending entries will slow searches significantly. Another disadvantage is that, while most updates are fast, an update that causes the pending list to become "too large" will incur an immediate cleanup cycle and be much slower than other updates. Proper use of autovacuum can minimize both of these problems.
+
+If consistent response time (of entity cleanup and of update) is more important than update speed, use of pending entries can be disabled by turning off the **fastupdate** storage parameter for a GIN index. For details, see [CREATE INDEX](50-CREATE-INDEX).
+
+## Partial Match Algorithm
+
+GIN can support "partial match" queries, in which the query does not determine an exact match for one or more keys, but the possible matches fall within a narrow range of key values (within the key sorting order determined by the **compare** support method). The **extractQuery** method, instead of returning a key value to be matched exactly, returns a key value that is the lower bound of the range to be searched, and sets the **pmatch** flag true. The key range is then scanned using the **comparePartial** method. **comparePartial** must return zero for a matching index key, less than zero for a non-match that is still within the range to be searched, or greater than zero if the index key is past the range that could match.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/1-gin-indexes/4-gin-tips-and-tricks.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/1-gin-indexes/4-gin-tips-and-tricks.md
new file mode 100644
index 0000000000000000000000000000000000000000..17ed886affcc0edcc1c91082fd739c952eff090e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/1-gin-indexes/4-gin-tips-and-tricks.md
@@ -0,0 +1,26 @@
+---
+title: GIN Tips and Tricks
+summary: Functions and Operators
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# GIN Tips and Tricks
+
+Create vs. Insert
+
+Insertion into a GIN index can be slow due to the likelihood of many keys being inserted for each item. So, for bulk insertions into a table it is advisable to drop the GIN index and recreate it after finishing bulk insertion. GUC parameters related to GIN index creation and query performance as follows:
+
+- maintenance_work_mem
+
+  Build time for a GIN index is very sensitive to the **maintenance_work_mem** setting.
+
+- work_mem
+
+  During a series of insertions into an existing GIN index that has **FASTUPDATE** enabled, the system will clean up the pending-entry list whenever the list grows larger than **work_mem**. To avoid fluctuations in observed response time, it is desirable to have pending-list cleanup occur in the background (that is, via autovacuum). Foreground cleanup operations can be avoided by increasing **work_mem** or making **autovacuum** more aggressive. However, increasing **work_mem** means that if a foreground cleanup occurs, it will take even longer.
+
+- gin_fuzzy_search_limit
+
+  The primary goal of developing GIN indexes was to support highly scalable full-text search in MogDB. A full-text search often returns a very large set of results. This often happens when the query contains very frequent words, so that the large result set is not even useful. Since reading many tuples from the disk and sorting them could take a lot of time, this is unacceptable for production.
+
+  To facilitate controlled execution of such queries, GIN has a configurable soft upper limit on the number of rows returned: the **gin_fuzzy_search_limit** configuration parameter. The default value **0** indicates that there is no limit on the returned set. If a non-zero limit is set, then the returned set is a subset of the whole result set, chosen at random. **Soft upper limit**  means that the actual number of returned results may deviate from the specified limit, depending on the quality of the query and the system random number generator.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/2-extended-functions.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/2-extended-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..f6e5583ab9791f598232f48ac6880a2ea724a29b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/2-extended-functions.md
@@ -0,0 +1,36 @@
+---
+title: Extended Functions
+summary: Extended Functions
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# Extended Functions
+
+The following table lists the extended functions supported by MogDB. These functions are for reference only.
+
+<table>
+    <tr>
+        <th>Category</th>
+        <th>Name</th>
+        <th>Description</th>
+    </tr>
+    <tr>
+        <td rowspan=2>Access privilege inquiry function</td>
+        <td>has_sequence_privilege(user, sequence, privilege)</td>
+        <td>Queries whether a specified user has privilege for sequences.</td>
+    </tr>
+    <tr>
+        <td>has_sequence_privilege(sequence, privilege)</td>
+        <td>Queries whether the current user has privilege for sequence.</td>
+    </tr>
+    <tr>
+        <td rowspan=2>Trigger function</td>
+        <td>pg_get_triggerdef(oid)</td>
+        <td>Gets CREATE [ CONSTRAINT ] TRIGGER command for triggers.</td>
+    </tr>
+    <tr>
+        <td>pg_get_triggerdef(oid, boolean)</td>
+        <td>Gets CREATE [ CONSTRAINT ] TRIGGER command for triggers.</td>
+    </tr>
+</table>
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/3-extended-syntax.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/3-extended-syntax.md
new file mode 100644
index 0000000000000000000000000000000000000000..8070c8426ec79079b80ad224ca8cec0596ee87d2
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/3-extended-syntax.md
@@ -0,0 +1,52 @@
+---
+title: Extended Syntax
+summary: Extended Syntax
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# Extended Syntax
+
+MogDB provides extended syntax .
+
+**Table 1** Extended SQL syntax
+
+<table>
+    <tr>
+        <th>Category</th>
+        <th>Keywords</th>
+        <th>Description</th>
+    </tr>
+    <tr>
+        <td rowspan=2>Creating a table</td>
+        <td>INHERITS ( parent_table [, … ] )</td>
+        <td>Specifies whether an inherited table is supported.</td>
+    </tr>
+    <tr>
+        <td>column_constraint：<br/>REFERENCES reftable<br/>[ ( refcolumn ) ] [ MATCH<br/>
+FULL | MATCH PARTIAL |<br/>MATCH SIMPLE ][ ON<br/>DELETE action ] [ ON<br/>UPDATE action ]</td>
+        <td>You can run REFERENCES reftable[(refcolumn)] [MATCH FULL |MATCH PARTIAL | MATCH SIMPLE] [ON DELETE action] [ON UPDATE action] to create foreign key constraints for tables.</td>
+    </tr>
+    <tr>
+        <td rowspan=2>Loading a module</td>
+        <td>CREATE EXTENSION</td>
+        <td>Loads a new module (such as DBLINK) to the current database.</td>
+    </tr>
+    <tr>
+        <td>DROP EXTENSION</td>
+        <td>Deletes the loaded module.</td>
+    </tr>
+    <tr>
+        <td rowspan=3>Aggregate functions</td>
+        <td>CREATE AGGREGATE</td>
+        <td>Defines a new aggregation function.</td>
+    </tr>
+    <tr>
+        <td>ALTER AGGREGATE</td>
+        <td>Modifies the definition of an aggregate function.</td>
+    </tr>
+    <tr>
+        <td>DROP AGGREGATE</td>
+        <td>Drops an existing function.</td>
+    </tr>
+</table>
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/2-keywords.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/2-keywords.md
new file mode 100644
index 0000000000000000000000000000000000000000..0963002b341f0f2b9ad816ac0b91714f255a834b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/2-keywords.md
@@ -0,0 +1,210 @@
+---
+title: Keywords
+summary: Keywords
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Keywords
+
+The SQL contains reserved and non-reserved words. Standards require that reserved keywords not be used as other identifiers. Non-reserved keywords have special meanings only in a specific environment and can be used as identifiers in other environments.
+
+The naming rules for identifiers are as follows:
+
+- An identifier name can only contain letters, underscores, digits (0-9), and dollar signs ($).
+
+- An identifier name must start with a letter (a to z) or an underscore (_).
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > - The naming rules are recommended but not mandatory.
+  > - In special cases, double quotation marks can be used to avoid special character errors.
+
+**Table 1** SQL keywords
+
+| 关键字                     | MogDB          |
+| :------------------------- | :------------- |
+| ALL                        | reserved       |
+| ANALYSE                    | reserved       |
+| ANALYZE                    | reserved       |
+| AND                        | reserved       |
+| ANY                        | reserved       |
+| ARRAY                      | reserved       |
+| AS                         | reserved       |
+| ASC                        | reserved       |
+| ASYMMETRIC                 | reserved       |
+| AUTHID                     | reserved       |
+| AUTHORIZATION              | type-func-name |
+| BETWEEN                    | col-name       |
+| BIGINT                     | col-name       |
+| BINARY                     | type-func-name |
+| BINARY_DOUBLE              | col-name       |
+| BINARY_FLOAT               | col-name       |
+| BINARY_INTEGER             | col-name       |
+| BIT                        | col-name       |
+| BOOLEAN                    | col-name       |
+| BOTH                       | reserved       |
+| BUCKETCNT                  | col-name       |
+| BUCKETS                    | reserved       |
+| BYTEAWITHOUTORDER          | col-name       |
+| BYTEAWITHOUTORDERWITHEQUAL | col-name       |
+| CASE                       | reserved       |
+| CAST                       | reserved       |
+| CHAR                       | col-name       |
+| CHARACTER                  | col-name       |
+| CHECK                      | reserved       |
+| COALESCE                   | col-name       |
+| COLLATE                    | reserved       |
+| COLLATION                  | type-func-name |
+| COLUMN                     | reserved       |
+| COMPACT                    | type-func-name |
+| CONCURRENTLY               | type-func-name |
+| CONSTRAINT                 | reserved       |
+| CREATE                     | reserved       |
+| CROSS                      | type-func-name |
+| CSN                        | type-func-name |
+| CURRENT_CATALOG            | reserved       |
+| CURRENT_DATE               | reserved       |
+| CURRENT_ROLE               | reserved       |
+| CURRENT_SCHEMA             | type-func-name |
+| CURRENT_TIME               | reserved       |
+| CURRENT_TIMESTAMP          | reserved       |
+| CURRENT_USER               | reserved       |
+| DATE                       | col-name       |
+| DEC                        | col-name       |
+| DECIMAL                    | col-name       |
+| DECODE                     | col-name       |
+| DEFAULT                    | reserved       |
+| DEFERRABLE                 | reserved       |
+| DELTAMERGE                 | type-func-name |
+| DESC                       | reserved       |
+| DISTINCT                   | reserved       |
+| DO                         | reserved       |
+| ELSE                       | reserved       |
+| END                        | reserved       |
+| EXCEPT                     | reserved       |
+| EXCLUDED                   | reserved       |
+| EXISTS                     | col-name       |
+| EXTRACT                    | col-name       |
+| FALSE                      | reserved       |
+| FENCED                     | reserved       |
+| FETCH                      | reserved       |
+| FLOAT                      | col-name       |
+| FOR                        | reserved       |
+| FOREIGN                    | reserved       |
+| FREEZE                     | type-func-name |
+| FROM                       | reserved       |
+| FULL                       | type-func-name |
+| GRANT                      | reserved       |
+| GREATEST                   | col-name       |
+| GROUP                      | reserved       |
+| GROUPING                   | col-name       |
+| GROUPPARENT                | reserved       |
+| HAVING                     | reserved       |
+| HDFSDIRECTORY              | type-func-name |
+| ILIKE                      | type-func-name |
+| IN                         | reserved       |
+| INITIALLY                  | reserved       |
+| INNER                      | type-func-name |
+| INOUT                      | col-name       |
+| INT                        | col-name       |
+| INTEGER                    | col-name       |
+| INTERSECT                  | reserved       |
+| INTERVAL                   | col-name       |
+| INTO                       | reserved       |
+| IS                         | reserved       |
+| JOIN                       | type-func-name |
+| LEADING                    | reserved       |
+| LEAST                      | col-name       |
+| LEFT                       | type-func-name |
+| LESS                       | reserved       |
+| LIKE                       | type-func-name |
+| LIMIT                      | reserved       |
+| LOCALTIME                  | reserved       |
+| LOCALTIMESTAMP             | reserved       |
+| MAXVALUE                   | reserved       |
+| MINUS                      | reserved       |
+| MODIFY                     | reserved       |
+| NATIONAL                   | col-name       |
+| NATURAL                    | type-func-name |
+| NCHAR                      | col-name       |
+| NLSSORT                    | reserved       |
+| NONE                       | col-name       |
+| NOT                        | reserved       |
+| NOTNULL                    | type-func-name |
+| NULL                       | reserved       |
+| NULLIF                     | col-name       |
+| NUMBER                     | col-name       |
+| NUMERIC                    | col-name       |
+| NVARCHAR2                  | col-name       |
+| NVL                        | col-name       |
+| OFFSET                     | reserved       |
+| ON                         | reserved       |
+| ONLY                       | reserved       |
+| OR                         | reserved       |
+| ORDER                      | reserved       |
+| OUT                        | col-name       |
+| OUTER                      | type-func-name |
+| OVERLAPS                   | type-func-name |
+| OVERLAY                    | col-name       |
+| PERFORMANCE                | reserved       |
+| PLACING                    | reserved       |
+| POSITION                   | col-name       |
+| PRECISION                  | col-name       |
+| PRIMARY                    | reserved       |
+| PROCEDURE                  | reserved       |
+| REAL                       | col-name       |
+| RECYCLEBIN                 | type-func-name |
+| REFERENCES                 | reserved       |
+| REJECT                     | reserved       |
+| RETURNING                  | reserved       |
+| RIGHT                      | type-func-name |
+| ROW                        | col-name       |
+| ROWNUM                     | reserved       |
+| SELECT                     | reserved       |
+| SESSION_USER               | reserved       |
+| SETOF                      | col-name       |
+| SIMILAR                    | type-func-name |
+| SMALLDATETIME              | col-name       |
+| SMALLINT                   | col-name       |
+| SOME                       | reserved       |
+| SUBSTRING                  | col-name       |
+| SYMMETRIC                  | reserved       |
+| SYSDATE                    | reserved       |
+| SYSTIMESTAMP               | reserved       |
+| TABLE                      | reserved       |
+| TABLESAMPLE                | type-func-name |
+| THEN                       | reserved       |
+| TIME                       | col-name       |
+| TIMECAPSULE                | type-func-name |
+| TIMESTAMP                  | col-name       |
+| TIMESTAMPDIFF              | col-name       |
+| TINYINT                    | col-name       |
+| TO                         | reserved       |
+| TRAILING                   | reserved       |
+| TREAT                      | col-name       |
+| TRIM                       | col-name       |
+| TRUE                       | reserved       |
+| UNION                      | reserved       |
+| UNIQUE                     | reserved       |
+| USER                       | reserved       |
+| USING                      | reserved       |
+| VALUES                     | col-name       |
+| VARCHAR                    | col-name       |
+| VARCHAR2                   | col-name       |
+| VARIADIC                   | reserved       |
+| VERBOSE                    | type-func-name |
+| VERIFY                     | reserved       |
+| WHEN                       | reserved       |
+| WHERE                      | reserved       |
+| WINDOW                     | reserved       |
+| WITH                       | reserved       |
+| XMLATTRIBUTES              | col-name       |
+| XMLCONCAT                  | col-name       |
+| XMLELEMENT                 | col-name       |
+| XMLEXISTS                  | col-name       |
+| XMLFOREST                  | col-name       |
+| XMLPARSE                   | col-name       |
+| XMLPI                      | col-name       |
+| XMLROOT                    | col-name       |
+| XMLSERIALIZE               | col-name       |
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/3-constant-and-macro.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/3-constant-and-macro.md
new file mode 100644
index 0000000000000000000000000000000000000000..8447eb6040dc7510afad39d40a0b42b50427a394
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/3-constant-and-macro.md
@@ -0,0 +1,24 @@
+---
+title: Constant and Macro
+summary: Constant and Macro
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Constant and Macro
+
+[Table 1](#constantandmacro) lists the constants and macros that can be used in openGauss.
+
+**Table 1** Constant and macro <a id="constantandmacro"> </a>
+
+| Parameter       | Description                                               | Example                                                      |
+| :------------- | :----------- | :--------------------------------|
+| CURRENT_CATALOG | Specifies the current database.                           | `postgres=# SELECT CURRENT_CATALOG; current_database ------------------- postgres (1 row)` |
+| CURRENT_ROLE    | Specifies the current user.                               | `postgres=# SELECT CURRENT_ROLE; current_user -------------------- omm (1 row)` |
+| CURRENT_SCHEMA  | Specifies the current database mode.                      | `postgres=# SELECT CURRENT_SCHEMA; current_schema ------------------- public (1 row)` |
+| CURRENT_USER    | Specifies the current user.                               | `postgres=# SELECT CURRENT_USER; current_user -------------------- omm (1 row)` |
+| LOCALTIMESTAMP  | Specifies the current session time (without time zone).   | `postgres=# SELECT LOCALTIMESTAMP;         timestamp ------------------- 2015-10-10 15:37:30.968538 (1 row)` |
+| NULL            | This parameter is left blank.                             | N/A                                                          |
+| SESSION_USER    | Specifies the current system user.                        | `postgres=# SELECT SESSION_USER; session_user -------------------- omm (1 row)` |
+| SYSDATE         | Specifies the current system date.                        | `postgres=# SELECT SYSDATE; sysdate ------------------- 2015-10-10 15:48:53 (1 row)` |
+| USER            | Specifies the current user, also called **CURRENT_USER**. | `postgres=# SELECT USER; current_user -------------------- omm (1 row)`    |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/4-expressions/1-simple-expressions.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/4-expressions/1-simple-expressions.md
new file mode 100644
index 0000000000000000000000000000000000000000..fab21481617ffee5620dd6bce200fc1c18bbff1c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/4-expressions/1-simple-expressions.md
@@ -0,0 +1,132 @@
+---
+title: Simple Expressions
+summary: Simple Expressions
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Simple Expressions
+
+## Logical Expressions
+
+[Logical Operators](1-logical-operators) lists the operators and calculation rules of logical expressions.
+
+## Comparative Expressions
+
+[Operators](2-operators) lists the common comparative operators.
+
+In addition to comparative operators, you can also use the following sentence structure:
+
+- BETWEEN operator
+
+  **a BETWEEN x AND y** is equivalent to **a &gt;= x AND a &lt;= y**.
+
+  **a NOT BETWEEN x AND y** is equivalent to **a &lt; x OR a &gt; y**.
+
+- To check whether a value is null, use:
+
+  expression IS NULL
+
+  expression IS NOT NULL
+
+  or an equivalent (non-standard) sentence structure:
+
+  expression ISNULL
+
+  expression NOTNULL
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** Do not write **expression=NULL** or **expression&lt;&gt;(!=)NULL**, because **NULL** represents an unknown value, and these expressions cannot determine whether two unknown values are equal.
+
+- is distinct from/is not distinct from
+
+  - is distinct from
+
+    If the data types and values of A and B are different, the value is **true**.
+
+    If the data types and values of A and B are the same, the value is **false**.
+
+    Empty values are considered the same.
+
+  - is not distinct from
+
+    If the data types and values of A and B are different, the value is **false**.
+
+    If the data types and values of A and B are the same, the value is **true**.
+
+    Empty values are considered the same.
+
+## Pseudocolumn
+
+**ROWNUM**
+
+**ROWNUM** is a pseudocolumn that returns a number indicating the row number of the result obtained from the query. The value of **ROWNUM** in the first row is **1**, the value of **ROWNUM** in the second row is **2**, and so on.
+
+The return type of **ROWNUM** is BIGINT. **ROWNUM** can be used to limit the total number of rows returned by a query. For example, the following statement limits the maximum number of records returned from the table **Students** to 10.
+
+```sql
+select * from Students where rownum <= 10;
+```
+
+## Examples
+
+```sql
+mogdb=# SELECT 2 BETWEEN 1 AND 3 AS RESULT;
+ result
+----------
+ t
+(1 row)
+
+mogdb=# SELECT 2 >= 1 AND 2 <= 3 AS RESULT;
+ result
+----------
+ t
+(1 row)
+
+mogdb=# SELECT 2 NOT BETWEEN 1 AND 3 AS RESULT;
+ result
+----------
+ f
+(1 row)
+
+mogdb=# SELECT 2 < 1 OR 2 > 3 AS RESULT;
+ result
+----------
+ f
+(1 row)
+
+mogdb=# SELECT 2+2 IS NULL AS RESULT;
+ result
+----------
+ f
+(1 row)
+
+mogdb=# SELECT 2+2 IS NOT NULL AS RESULT;
+ result
+----------
+ t
+(1 row)
+
+mogdb=# SELECT 2+2 ISNULL AS RESULT;
+ result
+----------
+ f
+(1 row)
+
+mogdb=# SELECT 2+2 NOTNULL AS RESULT;
+ result
+----------
+ t
+(1 row)
+
+mogdb=# SELECT 2+2 IS DISTINCT FROM NULL AS RESULT;
+ result
+----------
+ t
+(1 row)
+
+mogdb=# SELECT 2+2 IS NOT DISTINCT FROM NULL AS RESULT;
+ result
+----------
+ f
+(1 row)
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/4-expressions/2-condition-expressions.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/4-expressions/2-condition-expressions.md
new file mode 100644
index 0000000000000000000000000000000000000000..c459fb12b9dd310633d9d29fa072c6d118207774
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/4-expressions/2-condition-expressions.md
@@ -0,0 +1,226 @@
+---
+title: Condition Expressions
+summary: Condition Expressions
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Condition Expressions
+
+Data that meets the requirements specified by conditional expressions are filtered during SQL statement execution.
+
+Conditional expressions include the following types:
+
+- CASE
+
+  **CASE** expressions are similar to the **CASE** statements in other coding languages.
+
+  [Figure 1](#case) shows the syntax of a **CASE** expression.
+
+  **Figure 1** case::= <a id="case"> </a>
+
+  ![case](https://cdn-mogdb.enmotech.com/docs-media/mogdb/reference-guide/condition-expressions-1.png)
+
+  A **CASE** clause can be used in a valid expression. **condition** is an expression that returns a value of Boolean type.
+
+  - If the result is **true**, the result of the **CASE** expression is the required result.
+  - If the result is false, the following **WHEN** or **ELSE** clauses are processed in the same way.
+  - If every **WHEN condition** is false, the result of the expression is the result of the **ELSE** clause. If the **ELSE** clause is omitted and has no match condition, the result is NULL.
+
+  Example:
+
+  ```sql
+  mogdb=# CREATE TABLE tpcds.case_when_t1(CW_COL1 INT);
+
+  mogdb=# INSERT INTO tpcds.case_when_t1 VALUES (1), (2), (3);
+
+  mogdb=# SELECT * FROM tpcds.case_when_t1;
+  cw_col1
+  -------
+   1
+   2
+   3
+  (3 rows)
+
+  mogdb=# SELECT CW_COL1, CASE WHEN CW_COL1=1 THEN 'one' WHEN CW_COL1=2 THEN 'two' ELSE 'other' END FROM tpcds.case_when_t1 ORDER BY 1;
+   cw_col1 | case
+  ---------+-------
+         1 | one
+         2 | two
+         3 | other
+  (3 rows)
+
+  mogdb=# DROP TABLE tpcds.case_when_t1;
+  ```
+
+- DECODE
+
+  [Figure 2](#decode) shows the syntax of a **DECODE** expression.
+
+  **Figure 2** decode::= <a id="decode"></a>
+
+  ![decode](https://cdn-mogdb.enmotech.com/docs-media/mogdb/reference-guide/condition-expressions-2.png)
+
+  Compare each following **compare(n)** with **base_expr**, **value(n)** is returned if a **compare(n)** matches the **base_expr** expression. If base_expr does not match each **compare(n)**, the default value is returned.
+
+  **Conditional Expression Functions** describes the examples.
+
+  ```sql
+  mogdb=# SELECT DECODE('A','A',1,'B',2,0);
+   case
+  ------
+      1
+  (1 row)
+  ```
+
+- COALESCE
+
+  [Figure 3](#coalesce) shows the syntax of a **COALESCE** expression.
+
+  **Figure 3** coalesce::= <a id="coalesce"></a>
+
+  ![coalesce](https://cdn-mogdb.enmotech.com/docs-media/mogdb/reference-guide/condition-expressions-3.png)
+
+  **COALESCE**  returns its first not-**NULL**  value. If all the parameters are  **NULL**,  **NULL**  is returned. This value is replaced by the default value when data is displayed. Like a  **CASE**  expression,  **COALESCE**  only evaluates the parameters that are needed to determine the result. That is, parameters to the right of the first non-null parameter are not evaluated.
+
+  Example:
+
+  ```sql
+  mogdb=# CREATE TABLE tpcds.c_tabl(description varchar(10), short_description varchar(10), last_value varchar(10))
+  ;
+
+  mogdb=# INSERT INTO tpcds.c_tabl VALUES('abc', 'efg', '123');
+  mogdb=# INSERT INTO tpcds.c_tabl VALUES(NULL, 'efg', '123');
+
+  mogdb=# INSERT INTO tpcds.c_tabl VALUES(NULL, NULL, '123');
+
+  mogdb=# SELECT description, short_description, last_value, COALESCE(description, short_description, last_value) FROM tpcds.c_tabl ORDER BY 1, 2, 3, 4;
+   description | short_description | last_value | coalesce
+  -------------+-------------------+------------+----------
+   abc         | efg               | 123        | abc
+               | efg               | 123        | efg
+               |                   | 123        | 123
+  (3 rows)
+
+  mogdb=# DROP TABLE tpcds.c_tabl;
+  ```
+
+  If **description** is not **NULL**, the value of **description** is returned. Otherwise, parameter **short_description** is calculated. If **short_description** is not **NULL**, the value of **short_description** is returned. Otherwise, parameter **last_value** is calculated. If **last_value** is not **NULL**, the value of **last_value** is returned. Otherwise, **none** is returned.
+
+  ```sql
+  mogdb=# SELECT COALESCE(NULL,'Hello World');
+     coalesce
+  ---------------
+   Hello World
+  (1 row)
+  ```
+
+- NULLIF
+
+  [Figure 4](#nullif) shows the syntax of a **NULLIF** expression.
+
+  **Figure 4** nullif::= <a id="nullif"> </a>
+
+  ![nullif](https://cdn-mogdb.enmotech.com/docs-media/mogdb/reference-guide/condition-expressions-4.png)
+
+  Only if **value1** is equal to **value2** can **NULLIF** return the **NULL** value. Otherwise, **value1** is returned.
+
+  Example:
+
+  ```sql
+  mogdb=# CREATE TABLE tpcds.null_if_t1 (
+      NI_VALUE1 VARCHAR(10),
+      NI_VALUE2 VARCHAR(10)
+  );
+
+  mogdb=# INSERT INTO tpcds.null_if_t1 VALUES('abc', 'abc');
+  mogdb=# INSERT INTO tpcds.null_if_t1 VALUES('abc', 'efg');
+
+  mogdb=# SELECT NI_VALUE1, NI_VALUE2, NULLIF(NI_VALUE1, NI_VALUE2) FROM tpcds.null_if_t1 ORDER BY 1, 2, 3;
+
+   ni_value1 | ni_value2 | nullif
+  -----------+-----------+--------
+   abc       | abc       |
+   abc       | efg       | abc
+  (2 rows)
+  mogdb=# DROP TABLE tpcds.null_if_t1;
+  ```
+
+  If the value of  **value1**  is equal to that of  **value2**,  **NULL**  is returned. Otherwise, the value of  **value1**  is returned.
+
+  ```sql
+  mogdb=# SELECT NULLIF('Hello','Hello World');
+   nullif
+  --------
+   Hello
+  (1 row)
+  ```
+
+- GREATEST (maximum value) and LEAST (minimum value)
+
+  [Figure 5](#greatest) shows the syntax of a **GREATEST** expression.
+
+  **Figure 5** greatest::= <a id="greatest"> </a>
+
+  ![greatest](https://cdn-mogdb.enmotech.com/docs-media/mogdb/reference-guide/condition-expressions-5.png)
+
+  You can select the maximum value from any numerical expression list.
+
+  ```sql
+  mogdb=# SELECT greatest(9000,155555,2.01);
+   greatest
+  ----------
+     155555
+  (1 row)
+  ```
+
+  [Figure 6](#least) shows the syntax of a **LEAST** expression.
+
+  **Figure 6** least::= <a id="least"></a>
+
+  ![least](https://cdn-mogdb.enmotech.com/docs-media/mogdb/reference-guide/condition-expressions-6.png)
+
+  You can select the minimum value from any numerical expression list.
+
+  Each of the preceding numeric expressions can be converted into a common data type, which will be the data type of the result.
+
+  The NULL values in the list will be ignored. The result is **NULL** only if the results of all expressions are **NULL**.
+
+  ```sql
+  mogdb=# SELECT least(9000,2);
+   least
+  -------
+       2
+  (1 row)
+  ```
+
+  **Conditional Expression Functions** describes the examples.
+
+- NVL
+
+  [Figure 7](#nvl) shows the syntax of an **NVL** expression.
+
+  **Figure 7** nvl::= <a id="nvl"></a>
+
+  ![nvl](https://cdn-mogdb.enmotech.com/docs-media/mogdb/reference-guide/condition-expressions-7.png)
+
+  If the value of  **value1**  is  **NULL**, the value of  **value2**  is returned. Otherwise, the value of  **value1**  is returned.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT nvl(null,1);
+  nvl
+  -----
+   1
+  (1 row)
+
+  ```
+
+  ```sql
+  mogdb=# SELECT nvl ('Hello World' ,1);
+        nvl
+  ---------------
+   Hello World
+  (1 row)
+  ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/4-expressions/3-subquery-expressions.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/4-expressions/3-subquery-expressions.md
new file mode 100644
index 0000000000000000000000000000000000000000..1478c123010b4d62118f5e28f56cefa42b2f25b0
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/4-expressions/3-subquery-expressions.md
@@ -0,0 +1,146 @@
+---
+title: Subquery Expressions
+summary: Subquery Expressions
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Subquery Expressions
+
+Subquery expressions include the following types:
+
+- EXISTS/NOT EXISTS
+
+  [Figure 1](#existnotexist) shows the syntax of an **EXISTS/NOT EXISTS** expression.
+
+  **Figure 1** EXISTS/NOT EXISTS::= <a id="existnotexist"></a>.
+
+  ![exists-not-exists](https://cdn-mogdb.enmotech.com/docs-media/mogdb/reference-guide/subquery-expressions-1.png)
+
+  The parameter of an **EXISTS** expression is an arbitrary **SELECT** statement, or subquery. The subquery is evaluated to determine whether it returns any rows. If it returns at least one row, the result of **EXISTS** is "true". If the subquery returns no rows, the result of **EXISTS** is "false".
+
+  The subquery will generally only be executed long enough to determine whether at least one row is returned, not all the way to completion.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT sr_reason_sk,sr_customer_sk FROM tpcds.store_returns WHERE EXISTS (SELECT d_dom FROM tpcds.date_dim WHERE d_dom = store_returns.sr_reason_sk and sr_customer_sk <10);
+  sr_reason_sk | sr_customer_sk
+  --------------+----------------
+             13 |              2
+             22 |              5
+             17 |              7
+             25 |              7
+              3 |              7
+             31 |              5
+              7 |              7
+             14 |              6
+             20 |              4
+              5 |              6
+             10 |              3
+              1 |              5
+             15 |              2
+              4 |              1
+             26 |              3
+  (15 rows)
+  ```
+
+- IN/NOT IN
+
+  [Figure 2](#innotin) shows the syntax of an **IN/NOT IN** expression.
+
+  **Figure 2** IN/NOT IN::= <a id="innotin"></a>
+
+  ![in-not-in](https://cdn-mogdb.enmotech.com/docs-media/mogdb/reference-guide/subquery-expressions-2.png)
+
+  The right-hand side is a parenthesized subquery, which must return exactly one column. The left-hand expression is evaluated and compared to each row of the subquery result. The result of **IN** is "true" if any equal subquery row is found. The result is "false" if no equal row is found (including the case where the subquery returns no rows).
+
+  This is in accordance with SQL normal rules for Boolean combinations of null values. If the columns corresponding to two rows equal and are not empty, the two rows are equal to each other. If any columns corresponding to the two rows do not equal and are not empty, the two rows are not equal to each other. Otherwise, the result is **NULL**. If there are no equal right-hand values and at least one right-hand row yields null, the result of **IN** will be null, not false.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT sr_reason_sk,sr_customer_sk  FROM tpcds.store_returns WHERE sr_customer_sk IN (SELECT d_dom FROM tpcds.date_dim WHERE d_dom < 10);
+  sr_reason_sk | sr_customer_sk
+  --------------+----------------
+             10 |              3
+             26 |              3
+             22 |              5
+             31 |              5
+              1 |              5
+             32 |              5
+             32 |              5
+              4 |              1
+             15 |              2
+             13 |              2
+             33 |              4
+             20 |              4
+             33 |              8
+              5 |              6
+             14 |              6
+             17 |              7
+              3 |              7
+             25 |              7
+              7 |              7
+  (19 rows)
+  ```
+
+- ANY/SOME
+
+  [Figure 3](#anysome) shows the syntax of an **ANY/SOME** expression.
+
+  **Figure 3** any/some::= <a id="anysome"></a>
+
+  ![any-some](https://cdn-mogdb.enmotech.com/docs-media/mogdb/reference-guide/subquery-expressions-3.png)
+
+  The right-hand side is a parenthesized subquery, which must return exactly one column. The left-hand expression is evaluated and compared to each row of the subquery result using the given operator, which must yield a Boolean result. The result of **ANY** is "true" if any true result is obtained. The result is "false" if no true result is found (including the case where the subquery returns no rows). **SOME** is a synonym of **ANY**. **IN** can be equivalently replaced with **ANY**.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT sr_reason_sk,sr_customer_sk  FROM tpcds.store_returns WHERE sr_customer_sk < ANY (SELECT d_dom FROM tpcds.date_dim WHERE d_dom < 10);
+  sr_reason_sk | sr_customer_sk
+  --------------+----------------
+             26 |              3
+             17 |              7
+             32 |              5
+             32 |              5
+             13 |              2
+             31 |              5
+             25 |              7
+              5 |              6
+              7 |              7
+             10 |              3
+              1 |              5
+             14 |              6
+              4 |              1
+              3 |              7
+             22 |              5
+             33 |              4
+             20 |              4
+             33 |              8
+             15 |              2
+  (19 rows)
+  ```
+
+- ALL
+
+  [Figure 4](#all) shows the syntax of an **ALL** expression.
+
+  **Figure 4** all::= <a id="all"></a>
+
+  ![all](https://cdn-mogdb.enmotech.com/docs-media/mogdb/reference-guide/subquery-expressions-4.png)
+
+  The right-hand side is a parenthesized subquery, which must return exactly one column. The left-hand expression is evaluated and compared to each row of the subquery result using the given operator, which must yield a Boolean result. The result of **ALL** is "true" if all rows yield true (including the case where the subquery returns no rows). The result is "false" if any false result is found.
+
+  Example:
+
+  ```sql
+  mogdb=# SELECT sr_reason_sk,sr_customer_sk  FROM tpcds.store_returns WHERE sr_customer_sk < all(SELECT d_dom FROM tpcds.date_dim WHERE d_dom < 10);
+   sr_reason_sk | sr_customer_sk
+  --------------+----------------
+  (0 rows)
+
+  ```
+
+​
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/4-expressions/4-array-expressions.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/4-expressions/4-array-expressions.md
new file mode 100644
index 0000000000000000000000000000000000000000..ed3809ba82d39b866fd6e7a2acbb8b43563c2ceb
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/4-expressions/4-array-expressions.md
@@ -0,0 +1,94 @@
+---
+title: Array Expressions
+summary: Array Expressions
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Array Expressions
+
+## IN
+
+_expression **IN** (value [, …])
+
+The parentheses on the right contain an expression list. The expression result on the left is compared with the content in the expression list. If the content in the list meets the expression result on the left, the result of **IN** is **true**. If no result meets the requirements, the result of **IN** is **false**.
+
+Example:
+
+```sql
+mogdb=# SELECT 8000+500 IN (10000, 9000) AS RESULT;
+  result
+----------
+ f
+(1 row)
+```
+
+If the expression result is null or the expression list does not meet the expression conditions and at least one empty value is returned for the expression list on the right, the result of **IN** is **null** rather than **false**. This method is consistent with the Boolean rules used when SQL statements return empty values.
+
+## NOT IN
+
+_expression **NOT IN** (value [, …])_
+
+The parentheses on the right contain an expression list. The expression result on the left is compared with the content in the expression list. If the content in the list does not meet the expression result on the left, the result of **NOT IN** is **true**. If any content meets the expression result, the result of **NOT IN** is **false**.
+
+Example:
+
+```sql
+mogdb=# SELECT 8000+500 NOT IN (10000, 9000) AS RESULT;
+  result
+----------
+ t
+(1 row)
+```
+
+If the query statement result is null or the expression list does not meet the expression conditions and at least one empty value is returned for the expression list on the right, the result of **NOT IN** is **null** rather than **false**. This method is consistent with the Boolean rules used when SQL statements return empty values.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> In all situations, **X NOT IN Y** equals to **NOT(X IN Y)**.
+
+## ANY/SOME (array)
+
+_expression operator **ANY** (array expression)_
+
+_expression operator **SOME** (array expression)
+
+```sql
+mogdb=# SELECT 8000+500 < SOME (array[10000,9000]) AS RESULT;
+  result
+----------
+ t
+(1 row)
+mogdb=# SELECT 8000+500 < ANY (array[10000,9000]) AS RESULT;
+  result
+----------
+ t
+(1 row)
+```
+
+The right-hand side is a parenthesized expression, which must yield an array value. The result of the expression on the left uses operators to compute and compare the results in each row of the array expression. The comparison result must be a Boolean value.
+
+- If at least one comparison result is true, the result of **ANY** is **true**.
+- If no comparison result is true, the result of ANY is false.
+- If no comparison result is true and the array expression generates at least one null value, the value of ANY is NULL, rather than false. This method is consistent with the Boolean rules used when SQL statements return empty values.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> **SOME** is a synonym of **ANY**.
+
+## ALL (array)
+
+_expression operator **ALL** (array expression)_
+
+The right-hand side is a parenthesized expression, which must yield an array value. The result of the expression on the left uses operators to compute and compare the results in each row of the array expression. The comparison result must be a Boolean value.
+
+- The result of **ALL** is **true** if all comparisons yield **true** (including the case where the array has zero elements).
+- The result of **ALL** is **false** if one or multiple comparisons yield **false**.
+
+- If the array expression yields a null array, the result of **ALL** will be null. If the left-hand expression yields null, the result of **ALL** is ordinarily null (though a non-strict comparison operator could possibly yield a different result). Also, if the right-hand array contains any null elements and no false comparison result is obtained, the result of **ALL** will be null, not true (again, assuming a strict comparison operator). This method is consistent with the Boolean rules used when SQL statements return empty values.
+
+```sql
+mogdb=# SELECT 8000+500 < ALL (array[10000,9000]) AS RESULT;
+  result
+----------
+ t
+(1 row)
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/4-expressions/5-row-expressions.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/4-expressions/5-row-expressions.md
new file mode 100644
index 0000000000000000000000000000000000000000..8cfbb7d65803ee59791eab648879928d75dc11a7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/4-expressions/5-row-expressions.md
@@ -0,0 +1,28 @@
+---
+title: Row Expressions
+summary: Row Expressions
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Row Expressions
+
+Syntax:
+
+*row_constructor operator row_constructor*
+
+Both sides of the row expression are row constructors. The values of both rows must have the same number of fields and they are compared with each other. The row comparison allows operators including =, &lt;&gt;, &lt;, &lt;=, and &gt;= or a similar operator.
+
+The use of operators =&lt;&gt; is slightly different from other operators. If all fields of two rows are not empty and equal, the two rows are equal. If any field in two rows is not empty and not equal, the two rows are not equal. Otherwise, the comparison result is null.
+
+For operators &lt;, &lt;=, &gt;, and &gt; =, the fields in rows are compared from left to right until a pair of fields that are not equal or are empty are detected. If the pair of fields contains at least one null value, the comparison result is null. Otherwise, the comparison result of this pair of fields is the final result.
+
+Example:
+
+```sql
+mogdb=# SELECT ROW(1,2,NULL) < ROW(1,3,0) AS RESULT;
+  result
+----------
+ t
+(1 row)
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/5-type-conversion/1-type-conversion-overview.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/5-type-conversion/1-type-conversion-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..b70799f7559b4a48c7865c3f5dadd9569dee4755
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/5-type-conversion/1-type-conversion-overview.md
@@ -0,0 +1,52 @@
+---
+title: Overview
+summary: Overview
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Overview
+
+## Background
+
+SQL is a typed language. That is, every data item has an associated data type which determines its behavior and allowed usage. MogDB has an extensible type system that is more general and flexible than other SQL implementations. Hence, most type conversion behaviors in MogDB are governed by general rules. This allows the use of mixed-type expressions.
+
+The MogDB scanner/parser divides lexical elements into five fundamental categories: integers, floating-point numbers, strings, identifiers, and keywords. Constants of most non-numeric types are first classified as strings. The SQL language definition allows specifying type names with constant strings. For example, the query:
+
+```sql
+mogdb=# SELECT text 'Origin' AS "label", point '(0,0)' AS "value";
+ label  | value
+--------+-------
+ Origin | (0,0)
+(1 row)
+```
+
+has two literal constants, of type **text** and **point**. If a type is not specified for a string literal, then the placeholder type **unknown** is assigned initially.
+
+There are four fundamental SQL constructs requiring distinct type conversion rules in MogDB parser:
+
+- Function calls
+
+  Much of the SQL type system is built around a rich set of functions. Functions can have one or more arguments. Since SQL permits function overloading, the function name alone does not uniquely identify the function to be called. The parser must select the right function based on the data types of the supplied arguments.
+
+- Operators
+
+  SQL allows expressions with prefix and postfix unary (one-argument) operators, as well as binary (two-argument) operators. Like functions, operators can be overloaded, so the same problem of selecting the right operator exists.
+
+- Value storage
+
+  SQL **INSERT** and **UPDATE** statements place the results of expressions into a table. The expressions in the statement must be matched up with, and perhaps converted to, the types of the target columns.
+
+- UNION, CASE, and Related Constructs
+
+  Since all query results from a unionized **SELECT** statement must appear in a single set of columns, the types of the results of each **SELECT** clause must be matched up and converted to a uniform set. Similarly, the result expressions of a **CASE** construct must be converted to a common type so that the **CASE** expression as a whole has a known output type. The same holds for **ARRAY** constructs, and for the **GREATEST** and **LEAST** functions.
+
+The system catalog pg_cast stores information about which conversions, or casts, exist between which data types, and how to perform those conversions. For details, see **PG_CAST**.
+
+The return type and conversion behavior of an expression are determined during semantic analysis. Data types are divided into several basic type categories, including Boolean, **numeric**, **string**, **bitstring**, **datetime**, **timespan**, **geometric**, and **network**. Within each category there can be one or more preferred types, which are preferred when there is a choice of possible types. With careful selection of preferred types and available implicit casts, it is possible to ensure that ambiguous expressions (those with multiple candidate parsing solutions) can be resolved in a useful way.
+
+All type conversion rules are designed based on the following principles:
+
+- Implicit conversions should never have surprising or unpredictable outcomes.
+- There should be no extra overhead in the parser or executor if a query does not need implicit type conversion. That is, if a query is well-formed and the types already match, then the query should execute without spending extra time in the parser and without introducing unnecessary implicit conversion calls in the query.
+- Additionally, if a query usually requires an implicit conversion for a function, and if then the user defines a new function with the correct argument types, the parser should use this new function.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/5-type-conversion/2-operators.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/5-type-conversion/2-operators.md
new file mode 100644
index 0000000000000000000000000000000000000000..bbcd739271b853f6839920c7e71757ca304882b8
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/5-type-conversion/2-operators.md
@@ -0,0 +1,87 @@
+---
+title: Operators
+summary: Operators
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Operators
+
+## Operator Type Resolution
+
+1. Select the operators to be considered from the **pg_operator** system catalog. Considered operators are those with the matching name and argument count. If the search path finds multiple available operators, only the most suitable one is considered.
+2. Look for the best match.
+   a. Discard candidate operators for which the input types do not match and cannot be converted (using an implicit conversion) to match. **unknown** literals are assumed to be convertible to anything for this purpose. If only one candidate remains, use it; else continue to the next step.
+   b. Run through all candidates and keep those with the most exact matches on input types. Domains are considered the same as their base type for this purpose. Keep all candidates if none survives these tests. If only one candidate remains, use it; else continue to the next step.
+   c. Run through all candidates and keep those that accept preferred types (of the input data type's type category) at the most positions where type conversion will be required. Keep all candidates if none accepts preferred types. If only one candidate remains, use it; else continue to the next step.
+   d. If any input arguments are **unknown**, check the type categories accepted at those argument positions by the remaining candidates. At each position, select the string category if any candidate accepts that category. (This bias towards string is appropriate since an unknown-type literal looks like a string.) Otherwise, if all the remaining candidates accept the same type category, select that category; otherwise fail because the correct choice cannot be deduced without more clues. Now discard candidates that do not accept the selected type category. Furthermore, if any candidate accepts a preferred type in that category, discard candidates that accept non-preferred types for that argument. Keep all candidates if none survives these tests. If only one candidate remains, use it; else continue to the next step.
+   e. If there are both **unknown** and known-type arguments, and all the known-type arguments have the same type, assume that the **unknown** arguments are also of that type, and check which candidates can accept that type at the unknown-argument positions. If exactly one candidate passes this test, use it. Otherwise, an error occurs.
+
+## Examples
+
+Example 1: Use factorial operator type resolution. There is only one factorial operator (postfix !) defined in the system catalog, and it takes an argument of type **bigint**. The scanner assigns an initial type of **bigint** to the argument in this query expression:
+
+```sql
+mogdb=# SELECT 40 ! AS "40 factorial";
+
+                   40 factorial
+--------------------------------------------------
+ 815915283247897734345611269596115894272000000000
+(1 row)
+```
+
+So the parser does a type conversion on the operand and the query is equivalent to:
+
+```sql
+mogdb=# SELECT CAST(40 AS bigint) ! AS "40 factorial";
+```
+
+Example 2: String concatenation operator type resolution. A string-like syntax is used for working with string types and for working with complex extension types. Strings with unspecified type are matched with likely operator candidates. An example with one unspecified argument:
+
+```sql
+mogdb=# SELECT text 'abc' || 'def' AS "text and unknown";
+ text and unknown
+------------------
+ abcdef
+(1 row)
+```
+
+In this example, the parser looks for an operator whose parameters are of the text type. Such an operator is found.
+
+Here is a concatenation of two values of unspecified types:
+
+```sql
+mogdb=# SELECT 'abc' || 'def' AS "unspecified";
+ unspecified
+-------------
+ abcdef
+(1 row)
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> In this case there is no initial hint for which type to use, since no types are specified in the query. So, the parser looks for all candidate operators and finds that there are candidates accepting both string-category and bit-string-category inputs. Since string category is preferred when available, that category is selected, and then the preferred type for strings, **text**, is used as the specific type to resolve the unknown-type literals as.
+
+Example 3: Absolute-value and negation operator type resolution. The MogDB operator catalog has several entries for the prefix operator @. All the entries implement absolute-value operations for various numeric data types. One of these entries is for type **float8**, which is the preferred type in the numeric category. Therefore, MogDB will use that entry when faced with an unknown input:
+
+```sql
+mogdb=# SELECT @ '-4.5' AS "abs";
+ abs
+-----
+ 4.5
+(1 row)
+```
+
+Here the system has implicitly resolved the unknown-type literal as type **float8** before applying the chosen operator.
+
+Example 4: Use the array inclusion operator type resolution as an example. Here is another example of resolving an operator with one known and one unknown input:
+
+```sql
+mogdb=# SELECT array[1,2] <@ '{1,2,3}' as "is subset";
+ is subset
+-----------
+ t
+(1 row)
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> The MogDB operator catalog has several entries for the infix operator &lt;@, but the only two that could possibly accept an integer array on the left side are array inclusion (anyarray &lt;@ anyarray) and range inclusion (anyelement &lt;@ anyrange). Since none of these polymorphic pseudo-types (see section [Pseudo-Types](15-pseudo-types)) is considered preferred, the parser cannot resolve the ambiguity on that basis. However, the last resolution rule tells it to assume that the unknown-type literal is of the same type as the other input, that is, integer array. Now only one of the two operators can match, so array inclusion is selected. (Had range inclusion been selected, we would have gotten an error, because the string does not have the right format to be a range literal.)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/5-type-conversion/3-functions.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/5-type-conversion/3-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..d3f5622980998d339878bcb274b26149a35dbcfd
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/5-type-conversion/3-functions.md
@@ -0,0 +1,99 @@
+---
+title: Functions
+summary: Functions
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Functions
+
+## Function Type Resolution
+
+1. Select the functions to be considered from the **pg_proc** system catalog. If a non-schema-qualified function name was used, the functions in the current search path are considered. If a qualified function name was given, only functions in the specified schema are considered.
+
+   If the search path finds multiple functions of different argument types, a proper function in the path is considered.
+
+2. Check for a function accepting exactly the input argument types. If the function exists, use it. Cases involving **unknown** will never find a match at this step.
+
+3. If no exact match is found, see if the function call appears to be a special type conversion request.
+
+4. Look for the best match.
+
+   a. Discard candidate functions for which the input types do not match and cannot be converted (using an implicit conversion) to match. **unknown** literals are assumed to be convertible to anything for this purpose. If only one candidate remains, use it; else continue to the next step.
+   b. Run through all candidates and keep those with the most exact matches on input types. Domains are considered the same as their base type for this purpose. Keep all candidates if none has exact matches. If only one candidate remains, use it; else continue to the next step.
+   c. Run through all candidates and keep those that accept preferred types at the most positions where type conversion will be required. Keep all candidates if none accepts preferred types. If only one candidate remains, use it; else continue to the next step.
+   d. If any input arguments are **unknown**, check the type categories accepted at those argument positions by the remaining candidates. At each position, select the string category if any candidate accepts that category. (This bias towards string is appropriate since an unknown-type literal looks like a string.) Otherwise, if all the remaining candidates accept the same type category, select that category; otherwise fail because the correct choice cannot be deduced without more clues. Now discard candidates that do not accept the selected type category. Furthermore, if any candidate accepts a preferred type in that category, discard candidates that accept non-preferred types for that argument. Keep all candidates if none survives these tests. If only one candidate remains, use it; else continue to the next step.
+   e. If there are both **unknown** and known-type arguments, and all the known-type arguments have the same type, assume that the **unknown** arguments are also of that type, and check which candidates can accept that type at the **unknown**-argument positions. If exactly one candidate passes this test, use it. Otherwise, an error occurs.
+
+## Examples
+
+Example 1: Use the rounding function argument type resolution as the first example. There is only one **round** function that takes two arguments; it takes a first argument of type **numeric** and a second argument of type **integer**. So the following query automatically converts the first argument of type **integer** to **numeric**:
+
+```sql
+mogdb=# SELECT round(4, 4);
+ round
+--------
+ 4.0000
+(1 row)
+```
+
+That query is actually transformed by the parser to:
+
+```sql
+mogdb=# SELECT round(CAST (4 AS numeric), 4);
+```
+
+Since numeric constants with decimal points are initially assigned the type **numeric**, the following query will require no type conversion and therefore might be slightly more efficient:
+
+```sql
+mogdb=# SELECT round(4.0, 4);
+```
+
+Example 2: Use the substring function type resolution as the second example. There are several **substr** functions, one of which takes types **text** and **integer**. If called with a string constant of unspecified type, the system chooses the candidate function that accepts an argument of the preferred category **string** (namely of type **text**).
+
+```sql
+mogdb=# SELECT substr('1234', 3);
+ substr
+--------
+     34
+(1 row)
+```
+
+If the string is declared to be of type **varchar**, as might be the case if it comes from a table, then the parser will try to convert it to become **text**:
+
+```sql
+mogdb=# SELECT substr(varchar '1234', 3);
+ substr
+--------
+     34
+(1 row)
+```
+
+This is transformed by the parser to effectively become:
+
+```sql
+mogdb=# SELECT substr(CAST (varchar '1234' AS text), 3);
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> The parser learns from the **pg_cast** catalog that **text** and **varchar** are binary-compatible, meaning that one can be passed to a function that accepts the other without doing any physical conversion. Therefore, no type conversion is really inserted in this case.
+
+And, if the function is called with an argument of type **integer**, the parser will try to convert that to **text**:
+
+```sql
+mogdb=# SELECT substr(1234, 3);
+substr
+--------
+ 34
+(1 row)
+```
+
+This is transformed by the parser to effectively become:
+
+```sql
+mogdb=# SELECT substr(CAST (1234 AS text), 3);
+ substr
+--------
+     34
+(1 row)
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/5-type-conversion/4-value-storage.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/5-type-conversion/4-value-storage.md
new file mode 100644
index 0000000000000000000000000000000000000000..0c6f13c0fe701d524b0c865016dcb251eb88105d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/5-type-conversion/4-value-storage.md
@@ -0,0 +1,36 @@
+---
+title: Value Storage
+summary: Value Storage
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Value Storage
+
+## Value Storage Type Resolution
+
+1. Search for an exact match with the target column.
+2. Try to convert the expression to the target type. This will succeed if there is a registered cast between the two types. If the expression is an unknown-type literal, the content of the literal string will be fed to the input conversion routine for the target type.
+3. Check to see if there is a sizing cast for the target type. A sizing cast is a cast from that type to itself. If one is found in the **pg_cast** catalog, apply it to the expression before storing into the destination column. The implementation function for such a cast always takes an extra parameter of type **integer**. The parameter receives the destination column's **atttypmod** value (typically its declared length, although the interpretation of **atttypmod** varies for different data types), and may take a third Boolean parameter that says whether the cast is explicit or implicit. The cast function is responsible for applying any length-dependent semantics such as size checking or truncation.
+
+## Example
+
+Use the **character** storage type conversion as an example. For a target column declared as **character(20)** the following statement shows that the stored value is sized correctly:
+
+```sql
+mogdb=# CREATE TABLE tpcds.value_storage_t1 (
+    VS_COL1 CHARACTER(20)
+);
+mogdb=# INSERT INTO tpcds.value_storage_t1 VALUES('abcdef');
+mogdb=# SELECT VS_COL1, octet_length(VS_COL1) FROM tpcds.value_storage_t1;
+       vs_col1        | octet_length
+----------------------+--------------
+ abcdef               |           20
+(1 row)
+)
+
+mogdb=# DROP TABLE tpcds.value_storage_t1;
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> What has happened here is that the two unknown literals are resolved to **text** by default, allowing the **||** operator to be resolved as **text** concatenation. Then the **text** result of the operator is converted to **bpchar** ("blank-padded char", the internal name of the **character** data type) to match the target column type. Since the conversion from **text** to **bpchar** is binary-coercible, this conversion does not insert any real function call. Finally, the sizing function **bpchar(bpchar, integer, Boolean)** is found in the system catalog and used for the operator's result and the stored column length. This type-specific function performs the required length check and addition of padding spaces.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/5-type-conversion/5-union-case-and-related-constructs.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/5-type-conversion/5-union-case-and-related-constructs.md
new file mode 100644
index 0000000000000000000000000000000000000000..0c2e2a5368ca13c7b6534c5a805e8b3d55484f7b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/5-type-conversion/5-union-case-and-related-constructs.md
@@ -0,0 +1,125 @@
+---
+title: UNION, CASE, and Related Constructs
+summary: UNION, CASE, and Related Constructs
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# UNION, CASE, and Related Constructs
+
+SQL **UNION** constructs must match up possibly dissimilar types to become a single result set. The resolution algorithm is applied separately to each output column of a union query. The **INTERSECT** and **EXCEPT** construct resolve dissimilar types in the same way as **UNION**. The **CASE**, **ARRAY**, **VALUES**, **GREATEST** and **LEAST** constructs use the identical algorithm to match up their component expressions and select a result data type.
+
+## Type Resolution for UNION, CASE, and Related Constructs
+
+- If all inputs are of the same type, and it is not **unknown**, resolve as that type.
+
+- If all inputs are of type **unknown**, resolve as type **text** (the preferred type of the string category). Otherwise, **unknown** inputs are ignored.
+
+- If the inputs are not all of the same type category, a failure will be resulted. (Type **unknown** is not included in this case.)
+
+- If the inputs are all of the same type category, choose the top preferred type in that category. (Exception: The UNION operation regards the type of the first branch as the selected type.)
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  > **typcategory** in the **pg_type** system catalog indicates the data type category. **typispreferred** indicates whether a type is preferred in **typcategory**.
+
+- Convert all inputs to the selected type. (Retain the original lengths of strings). Fail if there is not an implicit conversion from a given input to the selected type.
+
+- If the input contains the json, txid_snapshot, sys_refcursor, or geometry type, **UNION** cannot be performed.
+
+## Type Resolution for CASE and COALESCE in TD Compatibility Type
+
+- If all inputs are of the same type, and it is not **unknown**, resolve as that type.
+- If all inputs are of type **unknown**, resolve as type **text**.
+- If inputs are of the string type (including **unknown** which is resolved as type **text**) and digit type, resolve as the string type. If the inputs are not of the two types, an error will be reported.
+- If the inputs are all of the same type category, choose the top preferred type in that category.
+- Convert all inputs to the selected type. Fail if there is not an implicit conversion from a given input to the selected type.
+
+## Example
+
+Example 1: Use type resolution with underspecified types in a union as the first example. Here, the unknown-type literal **'b'** will be resolved to type **text**.
+
+```sql
+mogdb=# SELECT text 'a' AS "text" UNION SELECT 'b';
+ text
+------
+ a
+ b
+(2 rows)
+```
+
+Example 2: Use type resolution in a simple union as the second example. The literal **1.2** is of type **numeric**, and the **integer** value **1** can be cast implicitly to **numeric**, so that type is used.
+
+```sql
+mogdb=# SELECT 1.2 AS "numeric" UNION SELECT 1;
+ numeric
+---------
+       1
+     1.2
+(2 rows)
+```
+
+Example 3: Use type resolution in a transposed union as the third example. Since type **real** cannot be implicitly cast to **integer**, but **integer** can be implicitly cast to **real**, the union result type is resolved as **real**.
+
+```sql
+mogdb=# SELECT 1 AS "real" UNION SELECT CAST('2.2' AS REAL);
+ real
+------
+    1
+  2.2
+(2 rows)
+```
+
+Example 4: In the **TD** type, if input parameters for **COALESCE** are of **int** and **varchar** types, resolve as type **varchar**. In the **A** type, an error is reported.
+
+```sql
+-- In the A type, create the a_1 database compatible with A.
+mogdb=# CREATE DATABASE a_1 dbcompatibility = 'A';
+
+-- Switch to the a_1 database.
+mogdb=# \c a_1
+
+-- Create the t1 table.
+a_1=# CREATE TABLE t1(a int, b varchar(10));
+
+-- Show the execution plan of a statement for querying the types int and varchar of input parameters for COALESCE.
+a_1=# EXPLAIN SELECT coalesce(a, b) FROM t1;
+ERROR:  COALESCE types integer and character varying cannot be matched
+LINE 1: EXPLAIN SELECT coalesce(a, b) FROM t1;
+                                   ^
+CONTEXT:  referenced column: coalesce
+
+-- Delete the table.
+a_1=# DROP TABLE t1;
+
+-- Switch to the mogdb database:
+a_1=# \c mogdb
+
+-- In the TD type, create the td_1 database compatible with Teradata.
+mogdb=# CREATE DATABASE td_1 dbcompatibility = 'C';
+
+-- Switch to the td_1 database.
+mogdb=# \c td_1
+
+-- Create the t2 table.
+td_1=# CREATE TABLE t2(a int, b varchar(10));
+
+-- Show the execution plan of a statement for querying the types int and varchar of input parameters for COALESCE.
+td_1=# EXPLAIN VERBOSE select coalesce(a, b) from t2;
+                                      QUERY PLAN
+---------------------------------------------------------------------------------------
+ Data Node Scan  (cost=0.00..0.00 rows=0 width=0)
+   Output: (COALESCE((t2.a)::character varying, t2.b))
+   Node/s: All dbnodes
+   Remote query: SELECT COALESCE(a::character varying, b) AS "coalesce" FROM public.t2
+(4 rows)
+
+-- Delete the table.
+td_1=# DROP TABLE t2;
+
+-- Switch to the mogdb database:
+td_1=# \c mogdb
+
+-- Delete databases in A and TD types.
+mogdb=# DROP DATABASE a_1;
+mogdb=# DROP DATABASE td_1;
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/1-introduction/1-full-text-retrieval.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/1-introduction/1-full-text-retrieval.md
new file mode 100644
index 0000000000000000000000000000000000000000..0fb61ca55ffca06c345f4423ae9c574c4f70a448
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/1-introduction/1-full-text-retrieval.md
@@ -0,0 +1,38 @@
+---
+title: Full-Text Retrieval
+summary: Full-Text Retrieval
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Full-Text Retrieval
+
+Textual search operators have been used in databases for years. MogDB has **~**, **~\***, **LIKE**, and **ILIKE** operators for textual data types, but they lack many essential properties required by modern information systems. They can be supplemented by indexes and dictionaries.
+
+Text search lacks the following essential properties required by information systems:
+
+- There is no linguistic support, even for English.
+
+  Regular expressions are not sufficient because they cannot easily handle derived words. For example, you might miss documents that contain **satisfies**, although you probably would like to find them when searching for **satisfy**. It is possible to use **OR** to search for multiple derived forms, but this is tedious and error-prone, because some words can have several thousand derivatives.
+
+- They provide no ordering (ranking) of search results, which makes them ineffective when thousands of matching documents are found.
+
+- They tend to be slow because there is no index support, so they must process all documents for every search.
+
+Full text indexing allows documents to be preprocessed and an index is saved for later rapid searching. Preprocessing includes:
+
+- Parsing documents into tokens
+
+  It is useful to identify various classes of tokens, for example, numbers, words, complex words, and email addresses, so that they can be processed differently. In principle, token classes depend on the specific application, but for most purposes it is adequate to use a predefined set of classes.
+
+- Converting tokens into lexemes
+
+  A lexeme is a string, just like a token, but it has been normalized so that different forms of the same word are made alike. For example, normalization almost always includes folding upper-case letters to lower-case, and often involves removal of suffixes (such as **s** or **es** in English). This allows searches to find variant forms of the same word, without tediously entering all the possible variants. Also, this step typically eliminates stop words, which are words that are so common that they are useless for searching. (In short, tokens are raw fragments of the document text, while lexemes are words that are believed useful for indexing and searching.) MogDB uses dictionaries to perform this step and provides various standard dictionaries.
+
+- Storing preprocessed documents optimized for searching
+
+  For example, each document can be represented as a sorted array of normalized lexemes. Along with the lexemes, it is often desirable to store positional information for proximity ranking. Therefore, a document that contains a more "dense" region of query words is assigned with a higher rank than the one with scattered query words.
+
+Dictionaries allow fine-grained control over how tokens are normalized. With appropriate dictionaries, you can define stop words that should not be indexed.
+
+A data type **tsvector** is provided for storing preprocessed documents, along with a type **tsquery** for storing query conditions. For details, see [Text Search Types](10-text-search-types). For details about the functions and operators available for these data types, see [Text Search Functions and Operators](12-text-search-functions-and-operators). The match operator **@@**, which is the most important among those functions and operators, is introduced in [Basic Text Matching](3-basic-text-matching).
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/1-introduction/2-what-is-a-document.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/1-introduction/2-what-is-a-document.md
new file mode 100644
index 0000000000000000000000000000000000000000..b6a0c10a8ce3c61694ebc86d73109b61fb6b2891
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/1-introduction/2-what-is-a-document.md
@@ -0,0 +1,33 @@
+---
+title: What Is a Document?
+summary: What Is a Document?
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# What Is a Document?
+
+A document is the unit of searching in a full text search system; for example, a magazine article or email message. The text search engine must be able to parse documents and store associations of lexemes (keywords) with their parent document. Later, these associations are used to search for documents that contain query words.
+
+For searches within MogDB, a document is normally a textual column within a row of a database table, or possibly a combination (concatenation) of such columns, perhaps stored in several tables or obtained dynamically. In other words, a document can be constructed from different parts for indexing and it might not be stored anywhere as a whole. Example:
+
+```sql
+mogdb=# SELECT d_dow || '-' || d_dom || '-' || d_fy_week_seq  AS identify_serials FROM tpcds.date_dim WHERE d_fy_week_seq = 1;
+identify_serials
+------------------
+ 5-6-1
+ 0-8-1
+ 2-3-1
+ 3-4-1
+ 4-5-1
+ 1-2-1
+ 6-7-1
+(7 rows)
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> Actually, in these example queries, **coalesce** should be used to prevent a single **NULL** attribute from causing a **NULL** result for the whole document.
+
+Another possibility is to store the documents as simple text files in the file system. In this case, the database can be used to store the full text index and to execute searches, and some unique identifier can be used to retrieve the document from the file system. However, retrieving files from outside the database requires system administrator permissions or special function support, so this is usually less convenient than keeping all the data inside the database. Also, keeping everything inside the database allows easy access to document metadata to assist in indexing and display.
+
+For text search purposes, each document must be reduced to the preprocessed **tsvector** format. Searching and relevance-based ranking are performed entirely on the **tsvector** representation of a document. The original text is retrieved only when the document has been selected for display to a user. We therefore often speak of the **tsvector** as being the document, but it is only a compact representation of the full document.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/1-introduction/3-basic-text-matching.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/1-introduction/3-basic-text-matching.md
new file mode 100644
index 0000000000000000000000000000000000000000..4df5762afb63b92cd6956715150c9d389f92bb6a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/1-introduction/3-basic-text-matching.md
@@ -0,0 +1,56 @@
+---
+title: Basic Text Matching
+summary: Basic Text Matching
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Basic Text Matching
+
+Full text search in MogDB is based on the match operator **@@**, which returns **true** if a **tsvector** (document) matches a **tsquery** (query). It does not matter which data type is written first:
+
+```
+postgres=# SELECT 'a fat cat sat on a mat and ate a fat rat'::tsvector @@ 'cat & rat'::tsquery AS RESULT;
+ result
+----------
+ t
+(1 row)
+Copy Codepostgres=# SELECT 'fat & cow'::tsquery @@ 'a fat cat sat on a mat and ate a fat rat'::tsvector AS RESULT;
+ result
+----------
+ f
+(1 row)
+```
+
+As the above example suggests, a **tsquery** is not raw text, any more than a **tsvector** is. A tsquery contains search terms, which must be already-normalized lexemes, and may combine multiple terms using **AND**, **OR**, and **NOT** operators. For details, see **Text Search Types**. There are functions **to_tsquery** and **plainto_tsquery** that are helpful in converting user-written text into a proper tsquery, for example by normalizing words appearing in the text. Similarly, **to_tsvector** is used to parse and normalize a document string. So in practice a text search match would look more like this:
+
+```
+postgres=# SELECT to_tsvector('fat cats ate fat rats') @@ to_tsquery('fat & rat') AS RESULT;
+result
+----------
+ t
+(1 row)
+```
+
+Observe that this match would not succeed if written as follows:
+
+```
+postgres=# SELECT 'fat cats ate fat rats'::tsvector @@ to_tsquery('fat & rat')AS RESULT;
+result
+----------
+ f
+(1 row)
+```
+
+In the preceding match, no normalization of the word **rats** will occur. Therefore, **rats** does not match **rat**.
+
+The **@@** operator also supports text input, allowing explicit conversion of a text string to **tsvector** or **tsquery** to be skipped in simple cases. The variants available are:
+
+```
+tsvector @@ tsquery
+tsquery  @@ tsvector
+text @@ tsquery
+text @@ text
+```
+
+We already saw the first two of these. The form **text @@ tsquery** is equivalent to **to_tsvector(text) @@ tsquery**. The form **text @@ text** is equivalent to **to_tsvector(text) @@ plainto_tsquery(text)**.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/1-introduction/4-configurations.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/1-introduction/4-configurations.md
new file mode 100644
index 0000000000000000000000000000000000000000..e5585ec123665a5e96f25464b07a90347ac571ab
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/1-introduction/4-configurations.md
@@ -0,0 +1,21 @@
+---
+title: Configurations
+summary: Configurations
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Configurations
+
+Full text search functionality includes the ability to do many more things: skip indexing certain words (stop words), process synonyms, and use sophisticated parsing, for example, parse based on more than just white space. This functionality is controlled by text search configurations. MogDB comes with predefined configurations for many languages, and you can easily create your own configurations. (The **\\dF** command of **gsql** shows all available configurations.)
+
+During installation an appropriate configuration is selected and **default_text_search_config** is set accordingly in **postgresql.conf**. If you are using the same text search configuration for MogDB, you can use the value in **postgresql.conf**. To use different configurations throughout MogDB but the same configuration within any one database, use **ALTER DATABASE …** **SET**. Otherwise, you can set **default_text_search_config** in each session.
+
+Each text search function that depends on a configuration has an optional argument, so that the configuration to use can be specified explicitly. **default_text_search_config** is used only when this argument is omitted.
+
+To make it easier to build custom text search configurations, a configuration is built up from simpler database objects. MogDB's text search facility provides the following types of configuration-related database objects:
+
+- Text search parsers break documents into tokens and classify each token (for example, as words or numbers).
+- Text search dictionaries convert tokens to normalized form and reject stop words.
+- Text search templates provide the functions underlying dictionaries. (A dictionary simply specifies a template and a set of parameters for the template.)
+- Text search configurations select a parser and a set of dictionaries to use to normalize the tokens produced by the parser.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/2-tables-and-indexes/1-searching-a-table.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/2-tables-and-indexes/1-searching-a-table.md
new file mode 100644
index 0000000000000000000000000000000000000000..577267b85ae87fcac0e27ab03e7c630f6f771e99
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/2-tables-and-indexes/1-searching-a-table.md
@@ -0,0 +1,91 @@
+---
+title: Searching a Table
+summary: Searching a Table
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Searching a Table
+
+It is possible to do a full text search without an index.
+
+- A simple query to print each row that contains the word **america** in its **body** column is as follows:
+
+  ```
+  postgres=# DROP SCHEMA IF EXISTS tsearch CASCADE;
+
+  postgres=# CREATE SCHEMA tsearch;
+
+  postgres=# CREATE TABLE tsearch.pgweb(id int, body text, title text, last_mod_date date);
+
+  postgres=# INSERT INTO tsearch.pgweb VALUES(1, 'China, officially the People''s Republic of China (PRC), located in Asia, is the world''s most populous state.', 'China', '2010-1-1');
+
+  postgres=# INSERT INTO tsearch.pgweb VALUES(2, 'America is a rock band, formed in England in 1970 by multi-instrumentalists Dewey Bunnell, Dan Peek, and Gerry Beckley.', 'America', '2010-1-1');
+
+  postgres=# INSERT INTO tsearch.pgweb VALUES(3, 'England is a country that is part of the United Kingdom. It shares land borders with Scotland to the north and Wales to the west.', 'England', '2010-1-1');
+
+  postgres=# INSERT INTO tsearch.pgweb VALUES(4, 'Australia, officially the Commonwealth of Australia, is a country comprising the mainland of the Australian continent, the island of Tasmania, and numerous smaller islands.', 'Australia', '2010-1-1');
+
+  postgres=# INSERT INTO tsearch.pgweb VALUES(5, 'Russia, also officially known as the Russian Federation, is a sovereign state in northern Eurasia.', 'Russia', '2010-1-1');
+
+  postgres=# INSERT INTO tsearch.pgweb VALUES(6, 'Japan is an island country in East Asia.', 'Japan', '2010-1-1');
+
+  postgres=# INSERT INTO tsearch.pgweb VALUES(7, 'Germany, officially the Federal Republic of Germany, is a sovereign state and federal parliamentary republic in central-western Europe.', 'Germany', '2010-1-1');
+
+  postgres=# INSERT INTO tsearch.pgweb VALUES(8, 'France, is a sovereign state comprising territory in western Europe and several overseas regions and territories.', 'France', '2010-1-1');
+
+  postgres=# INSERT INTO tsearch.pgweb VALUES(9, 'Italy officially the Italian Republic, is a unitary parliamentary republic in Europe.', 'Italy', '2010-1-1');
+
+  postgres=# INSERT INTO tsearch.pgweb VALUES(10, 'India, officially the Republic of India, is a country in South Asia.', 'India', '2010-1-1');
+
+  postgres=# INSERT INTO tsearch.pgweb VALUES(11, 'Brazil, officially the Federative Republic of Brazil, is the largest country in both South America and Latin America.', 'Brazil', '2010-1-1');
+
+  postgres=# INSERT INTO tsearch.pgweb VALUES(12, 'Canada is a country in the northern half of North America.', 'Canada', '2010-1-1');
+
+  postgres=# INSERT INTO tsearch.pgweb VALUES(13, 'Mexico, officially the United Mexican States, is a federal republic in the southern part of North America.', 'Mexico', '2010-1-1');
+
+  postgres=# SELECT id, body, title FROM tsearch.pgweb WHERE to_tsvector('english', body) @@ to_tsquery('english', 'america');
+   id |                                                          body                                                           |  title
+  ----+-------------------------------------------------------------------------------------------------------------------------+---------
+    2 | America is a rock band, formed in England in 1970 by multi-instrumentalists Dewey Bunnell, Dan Peek, and Gerry Beckley. | America
+   12 | Canada is a country in the northern half of North America.                                                              | Canada
+   13 | Mexico, officially the United Mexican States, is a federal republic in the southern part of North America.              | Mexico
+   11 | Brazil, officially the Federative Republic of Brazil, is the largest country in both South America and Latin America.   | Brazil
+  (4 rows)
+  ```
+
+  This will also find related words, such as **America**, since all these are reduced to the same normalized lexeme.
+
+  The query above specifies that the **english** configuration is to be used to parse and normalize the strings. Alternatively we could omit the configuration parameters, and use the configuration set by **default_text_search_config**.
+
+  ```
+  postgres=# SHOW default_text_search_config;
+   default_text_search_config
+  ----------------------------
+   pg_catalog.english
+  (1 row)
+
+  postgres=# SELECT id, body, title FROM tsearch.pgweb WHERE to_tsvector(body) @@ to_tsquery('america');
+   id |                                                          body                                                           |  title
+  ----+-------------------------------------------------------------------------------------------------------------------------+---------
+   11 | Brazil, officially the Federative Republic of Brazil, is the largest country in both South America and Latin America.   | Brazil
+    2 | America is a rock band, formed in England in 1970 by multi-instrumentalists Dewey Bunnell, Dan Peek, and Gerry Beckley. | America
+   12 | Canada is a country in the northern half of North America.                                                              | Canada
+   13 | Mexico, officially the United Mexican States, is a federal republic in the southern part of North America.              | Mexico
+  (4 rows)
+  ```
+
+- A more complex example to select the ten most recent documents that contain **north** and **america** in the **title** or **body** column is as follows:
+
+  ```
+  postgres=# SELECT title FROM tsearch.pgweb WHERE to_tsvector(title || ' ' || body) @@ to_tsquery('north & america') ORDER BY last_mod_date DESC LIMIT 10;
+   title
+  --------
+   Mexico
+   Canada
+  (2 rows)
+  ```
+
+  For clarity we omitted the **coalesce** function calls which would be needed to find rows that contain **NULL** in one of the two columns.
+
+  The preceding examples show queries without using indexes. Most applications will find this approach too slow. Therefore, practical use of text searching usually requires creating an index, except perhaps for occasional ad-hoc searches.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/2-tables-and-indexes/2-creating-an-index.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/2-tables-and-indexes/2-creating-an-index.md
new file mode 100644
index 0000000000000000000000000000000000000000..7fc4a4d4bfa92981c7fcde71d182b90c4960f97a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/2-tables-and-indexes/2-creating-an-index.md
@@ -0,0 +1,65 @@
+---
+title: Creating an Index
+summary: Creating an Index
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Creating an Index
+
+You can create a **GIN** index to speed up text searches:
+
+```sql
+mogdb=# CREATE INDEX pgweb_idx_1 ON tsearch.pgweb USING gin(to_tsvector('english', body));
+```
+
+The **to_tsvector** function comes in to two versions: the 1-argument version and the 2-argument version. When the 1-argument version is used, the system uses the configuration specified by **default_text_search_config** by default.
+
+Notice that the 2-argument version of **to_tsvector** is used for index creation. Only text search functions that specify a configuration name can be used in expression indexes. This is because the index contents must be unaffected by **default_text_search_config**, whose value can be changed at any time. If they were affected, the index contents might be inconsistent, because different entries could contain **tsvectors** that were created with different text search configurations, and there would be no way to guess which was which. It would be impossible to dump and restore such an index correctly.
+
+Because the two-argument version of **to_tsvector** was used in the index above, only a query reference that uses the 2-argument version of **to_tsvector** with the same configuration name will use that index. That is, **WHERE to_tsvector('english', body) @@ 'a & b'** can use the index, but **WHERE to_tsvector(body) @@ 'a & b'** cannot. This ensures that an index will be used only with the same configuration used to create the index entries.
+
+It is possible to set up more complex expression indexes wherein the configuration name is specified by another column. For example:
+
+```sql
+mogdb=# CREATE INDEX pgweb_idx_2 ON tsearch.pgweb USING gin(to_tsvector('ngram', body));
+```
+
+where **body** is a column in the **pgweb** table. This allows mixed configurations in the same index while recording which configuration was used for each index entry. This would be useful, for example, if the document collection contained documents in different languages. Again, queries that are meant to use the index must be phrased to match, for example, **WHERE to_tsvector(config_name, body) @@ 'a & b'** must match **to_tsvector** in the index.
+
+Indexes can even concatenate columns:
+
+```sql
+mogdb=# CREATE INDEX pgweb_idx_3 ON tsearch.pgweb USING gin(to_tsvector('english', title || ' ' || body));
+```
+
+Another approach is to create a separate **tsvector** column to hold the output of **to_tsvector**. This example is a concatenation of **title** and **body**, using **coalesce** to ensure that one column will still be indexed when the other is **NULL**:
+
+```sql
+mogdb=# ALTER TABLE tsearch.pgweb ADD COLUMN textsearchable_index_col tsvector;
+mogdb=# UPDATE tsearch.pgweb SET textsearchable_index_col = to_tsvector('english', coalesce(title,'') || ' ' || coalesce(body,''));
+```
+
+Then, create a GIN index to speed up the search:
+
+```sql
+mogdb=# CREATE INDEX textsearch_idx_4 ON tsearch.pgweb USING gin(textsearchable_index_col);
+```
+
+Now you are ready to perform a fast full text search:
+
+```sql
+mogdb=# SELECT title
+FROM tsearch.pgweb
+WHERE textsearchable_index_col @@ to_tsquery('north & america')
+ORDER BY last_mod_date DESC
+LIMIT 10;
+
+ title
+--------
+ Canada
+ Mexico
+(2 rows)
+```
+
+One advantage of the separate-column approach over an expression index is that it is unnecessary to explicitly specify the text search configuration in queries in order to use the index. As shown in the preceding example, the query can depend on **default_text_search_config**. Another advantage is that searches will be faster, since it will not be necessary to redo the **to_tsvector** calls to verify index matches. The expression-index approach is simpler to set up, however, and it requires less disk space since the **tsvector** representation is not stored explicitly.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/2-tables-and-indexes/3-constraints-on-index-use.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/2-tables-and-indexes/3-constraints-on-index-use.md
new file mode 100644
index 0000000000000000000000000000000000000000..bda944477f9c4b8e0b0ff2e3abe85c31adba151c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/2-tables-and-indexes/3-constraints-on-index-use.md
@@ -0,0 +1,44 @@
+---
+title: Constraints on Index Use
+summary: Constraints on Index Use
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Constraints on Index Use
+
+The following is an example of index use:
+
+```sql
+mogdb=# create table table1 (c_int int,c_bigint bigint,c_varchar varchar,c_text text) with(orientation=row);
+
+mogdb=# create text search configuration ts_conf_1(parser=POUND);
+mogdb=# create text search configuration ts_conf_2(parser=POUND) with(split_flag='%');
+
+mogdb=# set default_text_search_config='ts_conf_1';
+mogdb=# create index idx1 on table1 using gin(to_tsvector(c_text));
+
+mogdb=# set default_text_search_config='ts_conf_2';
+mogdb=# create index idx2 on table1 using gin(to_tsvector(c_text));
+
+mogdb=# select c_varchar,to_tsvector(c_varchar) from table1 where to_tsvector(c_text) @@ plainto_tsquery('￥#@……&**')   and to_tsvector(c_text) @@ plainto_tsquery('某公司 ')   and c_varchar is not null order by 1 desc limit 3;
+```
+
+In this example, **table1** has two GIN indexes created on the same column **c_text**, **idx1** and **idx2**, but these two indexes are created under different settings of **default_text_search_config**. Differences between this example and the scenario where one table has common indexes created on the same column are as follows:
+
+- GIN indexes use different parsers (that is, different delimiters). In this case, the index data of **idx1** is different from that of **idx2**.
+- In the specified scenario, the index data of multiple common indexes created on the same column is the same.
+
+As a result, using **idx1** and **idx2** for the same query returns different results.
+
+## Constraints
+
+Still use the above example. When:
+
+- Multiple GIN indexes are created on the same column of the same table.
+
+- The GIN indexes use different parsers (that is, different delimiters).
+
+- The column is used in a query, and an index scan is used in the execution plan.
+
+  To avoid different query results caused by different GIN indexes, ensure that only one GIN index is available on a column of the physical table.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/1-parsing-documents.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/1-parsing-documents.md
new file mode 100644
index 0000000000000000000000000000000000000000..a512c3ac07e9e3f99be50173999e34de9d67381b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/1-parsing-documents.md
@@ -0,0 +1,52 @@
+---
+title: Parsing Documents
+summary: Parsing Documents
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Parsing Documents
+
+MogDB provides function **to_tsvector** for converting a document to the **tsvector** data type.
+
+```sql
+to_tsvector([ config regconfig, ] document text) returns tsvector
+```
+
+**to_tsvector** parses a textual document into tokens, reduces the tokens to lexemes, and returns a **tsvector**, which lists the lexemes together with their positions in the document. The document is processed according to the specified or default text search configuration. Here is a simple example:
+
+```sql
+mogdb=# SELECT to_tsvector('english', 'a fat  cat sat on a mat - it ate a fat rats');
+                  to_tsvector
+-----------------------------------------------------
+ 'ate':9 'cat':3 'fat':2,11 'mat':7 'rat':12 'sat':4
+```
+
+In the preceding example we see that the resulting **tsvector** does not contain the words **a**, **on**, or **it**, the word **rats** became **rat**, and the punctuation sign (-) was ignored.
+
+The **to_tsvector** function internally calls a parser which breaks the document text into tokens and assigns a type to each token. For each token, a list of dictionaries is consulted. The list varies with the token type. The first dictionary that recognizes the token emits one or more normalized lexemes to represent the token. Example:
+
+- **rats** became **rat** because one of the dictionaries recognized that the word **rats** is a plural form of **rat**.
+- Some words are recognized as stop words (see [Stop Words](2-stop-words)), which causes them to be ignored since they occur too frequently to be useful in searching. In our example these are **a**, **on**, and **it**.
+- If no dictionary in the list recognizes the token then it is also ignored. In this example that happened to the punctuation sign (-) because there are no dictionaries assigned for its token type (**Space symbols**), meaning space tokens will never be indexed.
+
+The choices of parser, dictionaries and which types of tokens to index are determined by the selected text search configuration. It is possible to have many different configurations in the same database, and predefined configurations are available for various languages. In our example we used the default configuration **english** for the English language.
+
+The function **setweight** can be used to label the entries of a **tsvector** with a given weight, where a weight is one of the letters **A**, **B**, **C**, or **D**. This is typically used to mark entries coming from different parts of a document, such as title versus body. Later, this information can be used for ranking of search results.
+
+Because **to_tsvector(NULL)** will return **NULL**, you are advised to use **coalesce** whenever a column might be null. Here is the recommended method for creating a **tsvector** from a structured document:
+
+```sql
+mogdb=# CREATE TABLE tsearch.tt (id int, title text, keyword text, abstract text, body text, ti tsvector);
+
+mogdb=# INSERT INTO tsearch.tt(id, title, keyword, abstract, body) VALUES (1, 'China', 'Beijing', 'China','China, officially the People''s Republic of China (PRC), located in Asia, is the world''s most populous state.');
+
+mogdb=# UPDATE tsearch.tt SET ti =
+    setweight(to_tsvector(coalesce(title,'')), 'A')    ||
+    setweight(to_tsvector(coalesce(keyword,'')), 'B')  ||
+    setweight(to_tsvector(coalesce(abstract,'')), 'C') ||
+    setweight(to_tsvector(coalesce(body,'')), 'D');
+mogdb=# DROP TABLE tsearch.tt;
+```
+
+In this example, **setweight** is used to label the source of each lexeme in the finished **tsvector**, and then the labeled **tsvector** values are merged using the tsvector concatenation operator **||**. For details about these operations, see [Manipulating tsvector](1-manipulating-tsvector).
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/2-parsing-queries.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/2-parsing-queries.md
new file mode 100644
index 0000000000000000000000000000000000000000..539b130603d92249e56892d511779969ca1232bd
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/2-parsing-queries.md
@@ -0,0 +1,74 @@
+---
+title: Parsing Queries
+summary: Parsing Queries
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Parsing Queries
+
+MogDB provides functions **to_tsquery** and **plainto_tsquery** for converting a query to the **tsquery** data type. **to_tsquery** offers access to more features than **plainto_tsquery**, but is less forgiving about its input.
+
+```sql
+to_tsquery([ config regconfig, ] querytext text) returns tsquery
+```
+
+**to_tsquery** creates a **tsquery** value from **querytext**, which must consist of single tokens separated by the Boolean operators **&** (AND), **|** (OR), and **!** (NOT). These operators can be grouped using parentheses. In other words, the input to **to_tsquery** must follow the general rules for **tsquery** input, as described in **Text Search Types**. The difference is that while basic **tsquery** input takes the tokens at face value, **to_tsquery** normalizes each token to a lexeme using the specified or default configuration, and discards any tokens that are stop words according to the configuration. Example:
+
+```sql
+mogdb=# SELECT to_tsquery('english', 'The & Fat & Rats');
+   to_tsquery
+---------------
+ 'fat' & 'rat'
+(1 row)
+```
+
+As in basic **tsquery** input, **weight(s)** can be attached to each lexeme to restrict it to match only **tsvector** lexemes of those **weight(s)**. Example:
+
+```sql
+mogdb=# SELECT to_tsquery('english', 'Fat | Rats:AB');
+    to_tsquery
+------------------
+ 'fat' | 'rat':AB
+(1 row)
+```
+
+Also, the asterisk (*) can be attached to a lexeme to specify prefix matching:
+
+```sql
+mogdb=# SELECT to_tsquery('supern:*A & star:A*B');
+        to_tsquery
+--------------------------
+ 'supern':*A & 'star':*AB
+(1 row)
+```
+
+Such a lexeme will match any word having the specified string and weight in a **tsquery**.
+
+```sql
+plainto_tsquery([ config regconfig, ] querytext text) returns tsquery
+```
+
+**plainto_tsquery** transforms unformatted text **querytext** to **tsquery**. The text is parsed and normalized much as for **to_tsvector**, and then the **&** (AND) Boolean operator is inserted between surviving words.
+
+For example:
+
+```sql
+mogdb=# SELECT plainto_tsquery('english', 'The Fat Rats');
+ plainto_tsquery
+-----------------
+ 'fat' & 'rat'
+(1 row)
+```
+
+Note that **plainto_tsquery** cannot recognize Boolean operators, weight labels, or prefix-match labels in its input:
+
+```sql
+mogdb=# SELECT plainto_tsquery('english', 'The Fat & Rats:C');
+   plainto_tsquery
+---------------------
+ 'fat' & 'rat' & 'c'
+(1 row)
+```
+
+Here, all the input punctuation was discarded as being space symbols.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/3-ranking-search-results.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/3-ranking-search-results.md
new file mode 100644
index 0000000000000000000000000000000000000000..96fa4798f0c2c041e8447acbf5b9e904e38cd945
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/3-ranking-search-results.md
@@ -0,0 +1,108 @@
+---
+title: Ranking Search Results
+summary: Ranking Search Results
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Ranking Search Results
+
+Ranking attempts to measure how relevant documents are to a particular query, so that when there are many matches the most relevant ones can be shown first. MogDB provides two predefined ranking functions. The functions take into account lexical, proximity, and structural information; that is, they consider how often the query terms appear in the document, how close together the terms are in the document, and how important is the part of the document where they occur. However, the concept of relevancy is vague and application-specific. Different applications might require additional information for ranking, for example, document modification time. The built-in ranking functions are only examples. You can write your own ranking functions and/or combine their results with additional factors to fit your specific needs.
+
+The two ranking functions currently available are:
+
+```sql
+ts_rank([ weights float4[], ] vector tsvector, query tsquery [, normalization integer ]) returns float4
+```
+
+Ranks vectors based on the frequency of their matching lexemes.
+
+```sql
+ts_rank_cd([ weights float4[], ] vector tsvector, query tsquery [, normalization integer ]) returns float4
+```
+
+This function requires positional information in its input. Therefore, it will not work on "stripped" **tsvector** values. It will always return zero.
+
+For both these functions, the optional **weights** argument offers the ability to weigh word instances more or less heavily depending on how they are labeled. The weight arrays specify how heavily to weigh each category of word, in the order:
+
+```sql
+{D-weight, C-weight, B-weight, A-weight}
+```
+
+If no **weights** is provided, then these defaults are used: {0.1, 0.2, 0.4, 1.0}
+
+Typically weights are used to mark words from special areas of the document, like the title or an initial abstract, so they can be treated with more or less importance than words in the document body.
+
+Since a longer document has a greater chance of containing a query term it is reasonable to take into account document size. For example, a hundred-word document with five instances of a search word is probably more relevant than a thousand-word document with five instances. Both ranking functions take an integer **normalization** option that specifies whether and how a document's length should impact its rank. The integer option controls several behaviors, so it is a bit mask: you can specify one or more behaviors using a vertical bar (**|**) (for example, **2|4**).
+
+- **0** (default) ignores the document length.
+- **1** divides the rank by (1 + logarithm of the document length).
+- **2** divides the rank by the document length.
+- **4** divides the rank by the mean harmonic distance between extents. This is implemented only by **ts_rank_cd**.
+- **8** divides the rank by the number of unique words in document.
+- **16** divides the rank by (1 + Logarithm of the number of unique words in document).
+- **32** divides the rank by (itself + 1).
+
+If more than one flag bit is specified, the transformations are applied in the order listed.
+
+It is important to note that the ranking functions do not use any global information, so it is impossible to produce a fair normalization to 1% or 100% as sometimes desired. Normalization option 32 (**rank/(rank+1)**) can be applied to scale all ranks into the range zero to one, but of course this is just a cosmetic change; it will not affect the ordering of the search results.
+
+Here is an example that selects only the ten highest-ranked matches:
+
+```sql
+mogdb=# SELECT id, title, ts_rank_cd(to_tsvector(body), query) AS rank
+FROM tsearch.pgweb, to_tsquery('america') query
+WHERE query @@ to_tsvector(body)
+ORDER BY rank DESC
+LIMIT 10;
+ id |  title  | rank
+----+---------+------
+ 11 | Brazil  |   .2
+  2 | America |   .1
+ 12 | Canada  |   .1
+ 13 | Mexico  |   .1
+(4 rows)
+```
+
+This is the same example using normalized ranking:
+
+```sql
+mogdb=# SELECT id, title, ts_rank_cd(to_tsvector(body), query, 32 /* rank/(rank+1) */ ) AS rank
+FROM tsearch.pgweb, to_tsquery('america') query
+WHERE  query @@ to_tsvector(body)
+ORDER BY rank DESC
+LIMIT 10;
+ id |  title  |   rank
+----+---------+----------
+ 11 | Brazil  |  .166667
+  2 | America | .0909091
+ 12 | Canada  | .0909091
+ 13 | Mexico  | .0909091
+(4 rows)
+```
+
+The following example sorts query by Chinese word segmentation:
+
+```sql
+mogdb=# CREATE TABLE tsearch.ts_ngram(id int, body text);
+mogdb=# INSERT INTO tsearch.ts_ngram VALUES (1, 'Chinese');
+mogdb=# INSERT INTO tsearch.ts_ngram VALUES (2, 'Chinese search');
+mogdb=# INSERT INTO tsearch.ts_ngram VALUES (3 'Search Chinese');
+-- Exact match
+mogdb=# SELECT id, body, ts_rank_cd (to_tsvector ('ngram', body), query) AS rank FROM tsearch.ts_ngram, to_tsquery ('Chinese') query WHERE query @@ to_tsvector (body);
+ id | body | rank
+----+------+------
+  1 | Chinese |   .1
+(1 row)
+
+-- Fuzzy Match
+mogdb=# SELECT id, body, ts_rank_cd (to_tsvector ('ngram', body), query) AS rank FROM tsearch.ts_ngram, to_tsquery ('Chinese') query WHERE query @@ to_tsvector ('ngram', body);
+ id |   body   | rank
+----+----------+------
+  3 | Search Chinese |   .1
+  1 | Chinese     |   .1
+  2 | Chinese search |   .1
+(3 rows)
+```
+
+Ranking can be expensive since it requires consulting the **tsvector** of each matching document, which can be I/O bound and therefore slow. Unfortunately, it is almost impossible to avoid since practical queries often result in large numbers of matches.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/4-highlighting-results.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/4-highlighting-results.md
new file mode 100644
index 0000000000000000000000000000000000000000..c9d812178d8de2bc24aecca9570248a82eb72c79
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/4-highlighting-results.md
@@ -0,0 +1,66 @@
+---
+title: Highlighting Results
+summary: Highlighting Results
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Highlighting Results
+
+To present search results it is ideal to show a part of each document and how it is related to the query. Usually, search engines show fragments of the document with marked search terms. MogDB provides a function **ts_headline** that implements this functionality.
+
+```sql
+ts_headline([ config regconfig, ] document text, query tsquery [, options text ]) returns text
+```
+
+**ts_headline** accepts a document along with a query, and returns an excerpt from the document in which terms from the query are highlighted. The configuration to be used to parse the document can be specified by **config**. If **config** is omitted, the **default_text_search_config** configuration is used.
+
+If an options string is specified it must consist of a comma-separated list of one or more **option=value** pairs. The available options are:
+
+- **StartSel**, **StopSel**: The strings with which to delimit query words appearing in the document, to distinguish them from other excerpted words. You must double-quote these strings if they contain spaces or commas.
+- **MaxWords**, **MinWords**: These numbers determine the longest and shortest headlines to output.
+- **ShortWord**: Words of this length or less will be dropped at the start and end of a headline. The default value of three eliminates common English articles.
+- **HighlightAll**: Boolean flag. If **true** the whole document will be used as the headline, ignoring the preceding three parameters.
+- **MaxFragments**: Maximum number of text excerpts or fragments to display. The default value of zero selects a non-fragment-oriented headline generation method. A value greater than zero selects fragment-based headline generation. This method finds text fragments with as many query words as possible and stretches those fragments around the query words. As a result query words are close to the middle of each fragment and have words on each side. Each fragment will be of at most **MaxWords** and words of length **ShortWord** or less are dropped at the start and end of each fragment. If not all query words are found in the document, then a single fragment of the first **MinWords** in the document will be displayed.
+- **FragmentDelimiter**: When more than one fragment is displayed, the fragments will be separated by this string.
+
+Any unspecified options receive these defaults:
+
+```sql
+StartSel=<b>, StopSel=</b>,
+MaxWords=35, MinWords=15, ShortWord=3, HighlightAll=FALSE,
+MaxFragments=0, FragmentDelimiter=" ... "
+```
+
+Example:
+
+```sql
+mogdb=# SELECT ts_headline('english',
+'The most common type of search
+is to find all documents containing given query terms
+and return them in order of their similarity to the
+query.',
+to_tsquery('english', 'query & similarity'));
+                        ts_headline
+------------------------------------------------------------
+ containing given <b>query</b> terms
+ and return them in order of their <b>similarity</b> to the
+ <b>query</b>.
+(1 row)
+
+mogdb=# SELECT ts_headline('english',
+'The most common type of search
+is to find all documents containing given query terms
+and return them in order of their similarity to the
+query.',
+to_tsquery('english', 'query & similarity'),
+'StartSel = <, StopSel = >');
+                      ts_headline
+-------------------------------------------------------
+ containing given <query> terms
+ and return them in order of their <similarity> to the
+ <query>.
+(1 row)
+```
+
+**ts_headline** uses the original document, not a **tsvector** summary, so it can be slow and should be used with care.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/4-additional-features/1-manipulating-tsvector.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/4-additional-features/1-manipulating-tsvector.md
new file mode 100644
index 0000000000000000000000000000000000000000..48b6a2f1b80fa5a31e1515338811b79c25258d54
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/4-additional-features/1-manipulating-tsvector.md
@@ -0,0 +1,31 @@
+---
+title: Manipulating tsvector
+summary: Manipulating tsvector
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Manipulating tsvector
+
+MogDB provides functions and operators that can be used to manipulate documents that are already in **tsvector** type.
+
+- tsvector || tsvector
+
+  The tsvector concatenation operator returns a new tsvector which combines the lexemes and positional information of the two tsvectors given as arguments. Positions and weight labels are retained during the concatenation. Positions appearing in the right-hand tsvector are offset by the largest position mentioned in the left-hand tsvector, so that the result is nearly equivalent to the result of performing **to_tsvector** on the concatenation of the two original document strings. (The equivalence is not exact, because any stop-words removed from the end of the left-hand argument will not affect the result, whereas they would have affected the positions of the lexemes in the right-hand argument if textual concatenation were used.)
+
+  One advantage of using concatenation in the tsvector form, rather than concatenating text before applying **to_tsvector**, is that you can use different configurations to parse different sections of the document. Also, because the **setweight** function marks all lexemes of the given tsvector the same way, it is necessary to parse the text and do **setweight** before concatenating if you want to label different parts of the document with different weights.
+
+- setweight(vector tsvector, weight "char") returns tsvector
+
+  **setweight** returns a copy of the input tsvector in which every position has been labeled with the given weight, either **A**, **B**, **C**, or **D**. (**D** is the default for new tsvectors and as such is not displayed on output.) These labels are retained when tsvectors are concatenated, allowing words from different parts of a document to be weighted differently by ranking functions.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+  > Note that weight labels apply to positions, not lexemes. If the input tsvector has been stripped of positions then **setweight** does nothing.
+
+- length(vector tsvector) returns integer
+
+  Returns the number of lexemes stored in the tsvector.
+
+- strip(vector tsvector) returns tsvector
+
+  Returns a tsvector which lists the same lexemes as the given tsvector, but which lacks any position or weight information. While the returned tsvector is much less useful than an unstripped tsvector for relevance ranking, it will usually be much smaller.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/4-additional-features/2-manipulating-queries.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/4-additional-features/2-manipulating-queries.md
new file mode 100644
index 0000000000000000000000000000000000000000..9a513c38479c70f04da9923a6b9ff5a723bced01
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/4-additional-features/2-manipulating-queries.md
@@ -0,0 +1,52 @@
+---
+title: Manipulating Queries
+summary: Manipulating Queries
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Manipulating Queries
+
+MogDB provides functions and operators that can be used to manipulate queries that are already in **tsquery** type.
+
+- tsquery && tsquery
+
+  Returns the AND-combination of the two given queries.
+
+- tsquery || tsquery
+
+  Returns the OR-combination of the two given queries.
+
+- !! tsquery
+
+  Returns the negation (NOT) of the given query.
+
+- numnode(query tsquery) returns integer
+
+  Returns the number of nodes (lexemes plus operators) in a **tsquery**. This function is useful to determine if the query is meaningful (returns &gt; 0), or contains only stop words (returns 0). For example:
+
+  ```sql
+  mogdb=# SELECT numnode(plainto_tsquery('the any'));
+  NOTICE:  text-search query contains only stop words or doesn't contain lexemes, ignored
+  CONTEXT:  referenced column: numnode
+   numnode
+  ---------
+         0
+
+  mogdb=# SELECT numnode('foo & bar'::tsquery);
+   numnode
+  ---------
+         3
+  ```
+
+- querytree(query tsquery) returns text
+
+  Returns the portion of a **tsquery** that can be used for searching an index. This function is useful for detecting unindexable queries, for example those containing only stop words or only negated terms. For example:
+
+  ```sql
+  mogdb=# SELECT querytree(to_tsquery('!defined'));
+   querytree
+  -----------
+   T
+  (1 row)
+  ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/4-additional-features/3-rewriting-queries.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/4-additional-features/3-rewriting-queries.md
new file mode 100644
index 0000000000000000000000000000000000000000..5f8140495c2f714c26587ff3f06f41613fc7026b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/4-additional-features/3-rewriting-queries.md
@@ -0,0 +1,68 @@
+---
+title: Rewriting Queries
+summary: Rewriting Queries
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Rewriting Queries
+
+The **ts_rewrite** family of functions searches a given **tsquery** for occurrences of a target subquery, and replace each occurrence with a substitute subquery. In essence this operation is a **tsquery** specific version of substring replacement. A target and substitute combination can be thought of as a query rewrite rule. A collection of such rewrite rules can be a powerful search aid. For example, you can expand the search using synonyms (that is, new york, big apple, nyc, gotham) or narrow the search to direct the user to some hot topic.
+
+- ts_rewrite (query tsquery, target tsquery, substitute tsquery) returns tsquery
+
+  This form of **ts_rewrite** simply applies a single rewrite rule: **target** is replaced by **substitute** wherever it appears in query. Example:
+
+  ```sql
+  mogdb=# SELECT ts_rewrite('a & b'::tsquery, 'a'::tsquery, 'c'::tsquery);
+   ts_rewrite
+  ------------
+   'b' & 'c'
+  ```
+
+- ts_rewrite (query tsquery, select text) returns tsquery
+
+  This form of **ts_rewrite** accepts a starting query and a SQL select command, which is given as a text string. The **select** must yield two columns of **tsquery** type. For each row of the select result, occurrences of the first column value (the target) are replaced by the second column value (the substitute) within the current **query** value.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  > Note that when multiple rewrite rules are applied in this way, the order of application can be important; so in practice you will want the source query to **ORDER BY** some ordering key.
+
+  Consider a real-life astronomical example. We will expand query supernovae using table-driven rewriting rules:
+
+  ```sql
+  mogdb=# CREATE TABLE tsearch.aliases (id int, t tsquery, s tsquery);
+
+  mogdb=# INSERT INTO tsearch.aliases VALUES(1, to_tsquery('supernovae'), to_tsquery('supernovae|sn'));
+
+  mogdb=# SELECT ts_rewrite(to_tsquery('supernovae & crab'), 'SELECT t, s FROM tsearch.aliases');
+
+             ts_rewrite
+  ---------------------------------
+   'crab' & ( 'supernova' | 'sn' )
+  ```
+
+  We can change the rewriting rules just by updating the table:
+
+  ```sql
+  mogdb=# UPDATE tsearch.aliases
+  SET s = to_tsquery('supernovae|sn & !nebulae')
+  WHERE t = to_tsquery('supernovae');
+
+  mogdb=# SELECT ts_rewrite(to_tsquery('supernovae & crab'), 'SELECT t, s FROM tsearch.aliases');
+
+                   ts_rewrite
+  ---------------------------------------------
+   'crab' & ( 'supernova' | 'sn' & !'nebula' )
+  ```
+
+  Rewriting can be slow when there are many rewriting rules, since it checks every rule for a possible match. To filter out obvious non-candidate rules we can use the containment operators for the **tsquery** type. In the example below, we select only those rules which might match the original query:
+
+  ```sql
+  mogdb=# SELECT ts_rewrite('a & b'::tsquery, 'SELECT t,s FROM tsearch.aliases WHERE ''a & b''::tsquery @> t');
+
+   ts_rewrite
+  ------------
+   'b' & 'a'
+  (1 row)
+  mogdb=# DROP TABLE tsearch.aliases;
+  ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/4-additional-features/4-gathering-document-statistics.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/4-additional-features/4-gathering-document-statistics.md
new file mode 100644
index 0000000000000000000000000000000000000000..22b7825b1c50626e6c55e601a3c7dd2f2e20eef9
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/4-additional-features/4-gathering-document-statistics.md
@@ -0,0 +1,50 @@
+---
+title: Gathering Document Statistics
+summary: Gathering Document Statistics
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Gathering Document Statistics
+
+The function **ts_stat** is useful for checking your configuration and for finding stop-word candidates.
+
+```sql
+ts_stat(sqlquery text, [ weights text, ]
+        OUT word text, OUT ndoc integer,
+        OUT nentry integer) returns setof record
+```
+
+**sqlquery** is a text value containing an SQL query which must return a single **tsvector** column. **ts_stat** executes the query and returns statistics about each distinct lexeme (word) contained in the **tsvector** data. The columns returned are:
+
+- **word text**: the value of a lexeme
+- **ndoc integer**: number of documents (**tsvector**) the word occurred in
+- **nentry integer**: total number of occurrences of the word
+
+If **weights** is supplied, only occurrences having one of those weights are counted. For example, to find the ten most frequent words in a document collection:
+
+```sql
+mogdb=# SELECT * FROM ts_stat('SELECT to_tsvector(''english'', sr_reason_sk) FROM tpcds.store_returns WHERE sr_customer_sk < 10') ORDER BY nentry DESC, ndoc DESC, word LIMIT 10;
+   word | ndoc | nentry
+------+------+--------
+ 32   |    2 |      2
+ 33   |    2 |      2
+ 1    |    1 |      1
+ 10   |    1 |      1
+ 13   |    1 |      1
+ 14   |    1 |      1
+ 15   |    1 |      1
+ 17   |    1 |      1
+ 20   |    1 |      1
+ 22   |    1 |      1
+(10 rows)
+```
+
+The same, but counting only word occurrences with weight **A** or **B**:
+
+```sql
+mogdb=# SELECT * FROM ts_stat('SELECT to_tsvector(''english'', sr_reason_sk) FROM tpcds.store_returns WHERE sr_customer_sk < 10', 'a') ORDER BY nentry DESC, ndoc DESC, word LIMIT 10;
+ word | ndoc | nentry
+------+------+--------
+(0 rows)
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/5-parser.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/5-parser.md
new file mode 100644
index 0000000000000000000000000000000000000000..9a39ddeb73dbaf09c533afcb8a998a4bde1a7df1
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/5-parser.md
@@ -0,0 +1,108 @@
+---
+title: Parser
+summary: Parser
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Parser
+
+Text search parsers are responsible for splitting raw document text into tokens and identifying each token's type, where the type set is defined by the parser itself. Note that a parser does not modify the text; it simply identifies plausible word boundaries. Because of this limit, there is less need for application-specific custom parsers than there is for custom dictionaries.
+
+Currently, MogDB provides the following built-in parsers: pg_catalog.default for English configuration, and pg_catalog.ngram and pg_catalog.pound for full text search in texts containing Chinese, or both Chinese and English.
+
+The built-in parser is named **pg_catalog.default**. It recognizes 23 token types, shown in [Table 1](#defaultparser).
+
+**Table 1** Token types of the default parser <a id="defaultparser"></a>
+
+| Alias           | Description                              | Example                                                  |
+| :--------------------------------------- | :-------------- | :------------------------------------------------------- |
+| asciiword       | Word, all ASCII letters                  | elephant                                                 |
+| word            | Word, all letters                        | mañana                                                   |
+| numword         | Word, letters and digits                 | beta1                                                    |
+| asciihword      | Hyphenated word, all ASCII               | up-to-date                                               |
+| hword           | Hyphenated word, all letters             | lógico-matemática                                        |
+| numhword        | Hyphenated word, letters and digits      | mogdb-beta1                                              |
+| hword_asciipart | Hyphenated word part, all ASCII          | mogdb in the context mogdb-beta1                         |
+| hword_part      | Hyphenated word part, all letters        | lógico or matemática in the context lógico-matemática    |
+| hword_numpart   | Hyphenated word part, letters and digits | beta1 in the context mogdb-beta1                         |
+| email           | Email address                            | foo@example.com                                          |
+| protocol        | Protocol head                            | `http://`                                                 |
+| url             | URL                                      | example.com/stuff/index.html                             |
+| host            | Host                                     | example.com                                              |
+| url_path        | URL path                                 | /stuff/index.html, in the context of a URL               |
+| file            | File or path name                        | /usr/local/foo.txt, if not within a URL                  |
+| sfloat          | Scientific notation                      | -1.23E+56                                                |
+| float           | Decimal notation                         | -1.234                                                   |
+| int             | Signed integer                           | -1234                                                    |
+| uint            | Unsigned integer                         | 1234                                                     |
+| version         | Version number                           | 8.3.0                                                    |
+| tag             | XML tag                                  | &lt;a href="dictionaries.html"&gt;                       |
+| entity          | XML entity                               | &amp;                                                    |
+| blank           | Space symbols                            | (any whitespace or punctuation not otherwise recognized) |
+
+Note: The parser's notion of a "letter" is determined by the database's locale setting, specifically **lc_ctype**. Words containing only the basic ASCII letters are reported as a separate token type, since it is sometimes useful to distinguish them. In most European languages, token types word and asciiword should be treated alike.
+
+**email** does not support all valid email characters as defined by RFC 5322. Specifically, the only non-alphanumeric characters supported for email user names are period, dash, and underscore.
+
+It is possible for the parser to identify overlapping tokens in the same piece of text. For example, a hyphenated word will be reported both as the entire word and as each component.
+
+```sql
+mogdb=# SELECT alias, description, token FROM ts_debug('english','foo-bar-beta1');
+      alias      |               description                |     token
+-----------------+------------------------------------------+---------------
+ numhword        | Hyphenated word, letters and digits      | foo-bar-beta1
+ hword_asciipart | Hyphenated word part, all ASCII          | foo
+ blank           | Space symbols                            | -
+ hword_asciipart | Hyphenated word part, all ASCII          | bar
+ blank           | Space symbols                            | -
+ hword_numpart   | Hyphenated word part, letters and digits | beta1
+```
+
+This behavior is desirable since it allows searches to work for both the whole compound word and for components. Here is another instructive example:
+
+```sql
+mogdb=# SELECT alias, description, token FROM ts_debug('english','http://example.com/stuff/index.html');
+  alias   |  description  |            token
+----------+---------------+------------------------------
+ protocol | Protocol head | http://
+ url      | URL           | example.com/stuff/index.html
+ host     | Host          | example.com
+ url_path | URL path      | /stuff/index.html
+```
+
+N-gram is a mechanical word segmentation method, and applies to no semantic Chinese segmentation scenarios. The N-gram segmentation method ensures the completeness of the segmentation. However, to cover all the possibilities, it adds unnecessary words to the index, resulting in a large number of index items. N-gram supports Chinese coding, including GBK and UTF-8, and has six built-in token types, as shown in [Table 2](#tokentypes).
+
+**Table 2** Token types <a id="tokentypes"></a>
+
+| Alias       | Description     |
+| :---------- | :-------------- |
+| zh_words    | chinese words   |
+| en_word     | english word    |
+| numeric     | numeric data    |
+| alnum       | alnum string    |
+| grapsymbol  | graphic symbol  |
+| multisymbol | multiple symbol |
+
+Pound segments words in a fixed format. It is used to segment to-be-parsed nonsense Chinese and English words that are separated by fixed separators. It supports Chinese encoding (including GBK and UTF8) and English encoding (including ASCII). Six built-in token types are available, as listed in  [Table 3](#tokentypes3). Five types of delimiters are supported, as shown in  [Table 4](#separatortypes), and the default delimiter is \#. The maximum length of a token is 256 characters.
+
+**Table 3** Token types <a id="tokentypes3"></a>
+
+| Alias       | Description     |
+| :---------- | :-------------- |
+| zh_words    | chinese words   |
+| en_word     | english word    |
+| numeric     | numeric data    |
+| alnum       | alnum string    |
+| grapsymbol  | graphic symbol  |
+| multisymbol | multiple symbol |
+
+**Table 4** Separator types <a id="separatortypes"></a>
+
+| Separator | Description       |
+| :-------- | :---------------- |
+| @         | Special character |
+| #         | Special character |
+| $         | Special character |
+| %         | Special character |
+| /         | Special character |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/1-dictionaries-overview.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/1-dictionaries-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..2da0f824c4eb2bef8619ecb962158386a344e7da
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/1-dictionaries-overview.md
@@ -0,0 +1,36 @@
+---
+title: Overview
+summary: Overview
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Overview
+
+A dictionary is used to define stop words, that is, words to be ignored in full-text retrieval.
+
+A dictionary can also be used to normalize words so that different derived forms of the same word will match. A normalized word is called a lexeme.
+
+In addition to improving retrieval quality, normalization and removal of stop words can reduce the size of the **tsvector** representation of a document, thereby improving performance. Normalization and removal of stop words do not always have linguistic meaning. Users can define normalization and removal rules in dictionary definition files based on application environments.
+
+A dictionary is a program that receives a token as input and returns:
+
+- An array of lexemes if the input token is known to the dictionary (note that one token can produce more than one lexeme).
+- A single lexeme A new token is passed to the subsequent dictionary (the current dictionary may be referred to as a filter dictionary) in place of the input token.
+- An empty array if the input token is known to the dictionary but is a stop word.
+- **NULL** if the dictionary does not recognize the token.
+
+MogDB provides predefined dictionaries for many languages and also provides five predefined dictionary templates, **Simple**, **Synonym**, **Thesaurus**, **Ispell**, and **Snowball**. These templates can be used to create new dictionaries with custom parameters.
+
+When using full-text retrieval, you are advised to:
+
+- In the text search configuration, configure a parser together with a set of dictionaries to process the parser's output tokens. For each token type that the parser can return, a separate list of dictionaries is specified by the configuration. When a token of that type is found by the parser, each dictionary in the list is consulted in turn, until a dictionary recognizes it as a known word. If it is identified as a stop word, or no dictionary recognizes the token, it will be discarded and not indexed or searched for. Generally, the first dictionary that returns a non-**NULL** output determines the result, and any remaining dictionaries are not consulted. However, a filtering dictionary can replace the input token with a modified one, which is then passed to subsequent dictionaries.
+
+- The general rule for configuring a list of dictionaries is to place first the most narrow, most specific dictionary, then the more general dictionaries, finishing with a very general dictionary, like a **Snowball** stemmer dictionary or a **Simple** dictionary, which recognizes everything. In the following example, for an astronomy-specific search (**astro_en** configuration), you can configure the token type **asciiword** (ASCII word) with a **Synonym** dictionary of astronomical terms, a general English **Ispell** dictionary, and a **Snowball** English stemmer dictionary:
+
+  ```sql
+  mogdb=# ALTER TEXT SEARCH CONFIGURATION astro_en
+    ADD MAPPING FOR asciiword WITH astro_syn, english_ispell, english_stem;
+  ```
+
+  A filtering dictionary can be placed anywhere in the list, except at the end where it would be useless. Filtering dictionaries are useful to partially normalize words to simplify the task of later dictionaries.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/2-stop-words.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/2-stop-words.md
new file mode 100644
index 0000000000000000000000000000000000000000..0d8ec2685e2b750245e19d0289353b54d87b1f4e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/2-stop-words.md
@@ -0,0 +1,33 @@
+---
+title: Stop Words
+summary: Stop Words
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Stop Words
+
+Stop words are words that are very common, appear in almost every document, and have no discrimination value. Therefore, they can be ignored in the context of full text searching. Each type of dictionaries treats stop words in different ways. For example, **Ispell** dictionaries first normalize words and then check the list of stop words, while **Snowball** dictionaries first check the list of stop words.
+
+For example, every English text contains words like **a** and **the**, so it is useless to store them in an index. However, stop words affect the positions in **tsvector**, which in turn affect ranking.
+
+```sql
+mogdb=# SELECT to_tsvector('english','in the list of stop words');
+        to_tsvector
+----------------------------
+ 'list':3 'stop':5 'word':6
+```
+
+The missing positions 1, 2, and 4 are because of stop words. Ranks calculated for documents with and without stop words are quite different:
+
+```sql
+mogdb=# SELECT ts_rank_cd (to_tsvector('english','in the list of stop words'), to_tsquery('list & stop'));
+ ts_rank_cd
+------------
+        .05
+
+mogdb=# SELECT ts_rank_cd (to_tsvector('english','list stop words'), to_tsquery('list & stop'));
+ ts_rank_cd
+------------
+         .1
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/3-simple-dictionary.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/3-simple-dictionary.md
new file mode 100644
index 0000000000000000000000000000000000000000..b5a06e529ae7dcbbf428ba70c4b8f608a2b914ce
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/3-simple-dictionary.md
@@ -0,0 +1,64 @@
+---
+title: Simple Dictionary
+summary: Simple Dictionary
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Simple Dictionary
+
+A **Simple** dictionary operates by converting the input token to lower case and checking it against a list of stop words. If the token is found in the list, an empty array will be returned, causing the token to be discarded. If it is not found, the lower-cased form of the word is returned as the normalized lexeme. In addition, you can set **Accept** to **false** for **Simple** dictionaries (default: **true**) to report non-stop-words as unrecognized, allowing them to be passed on to the next dictionary in the list.
+
+## Precautions
+
+- Most types of dictionaries rely on dictionary configuration files. The name of a configuration file can only be lowercase letters, digits, and underscores (_).
+- A dictionary cannot be created in **pg_temp** mode.
+- Dictionary configuration files must be stored in UTF-8 encoding. They will be translated to the actual database encoding, if that is different, when they are read into the server.
+- Generally, a session will read a dictionary configuration file only once, when it is first used within the session. To modify a configuration file, run the **ALTER TEXT SEARCH DICTIONARY** statement to update and reload the file.
+
+## Procedure
+
+1. Create a **Simple** dictionary.
+
+   ```sql
+   mogdb=# CREATE TEXT SEARCH DICTIONARY public.simple_dict (
+        TEMPLATE = pg_catalog.simple,
+        STOPWORDS = english
+   );
+   ```
+
+   **english.stop** is the full name of a file of stop words. For details about the syntax and parameters for creating a **Simple** dictionary, see [CREATE TEXT SEARCH DICTIONARY](65-CREATE-TEXT-SEARCH-DICTIONARY).
+
+2. Use the **Simple** dictionary.
+
+   ```sql
+   mogdb=# SELECT ts_lexize('public.simple_dict','YeS');
+    ts_lexize
+   -----------
+    {yes}
+   (1 row)
+
+   mogdb=# SELECT ts_lexize('public.simple_dict','The');
+    ts_lexize
+   -----------
+    {}
+   (1 row)
+   ```
+
+3. Set **Accept=false** so that the **Simple** dictionary returns **NULL** instead of a lower-cased non-stop word.
+
+   ```sql
+   mogdb=# ALTER TEXT SEARCH DICTIONARY public.simple_dict ( Accept = false );
+   ALTER TEXT SEARCH DICTIONARY
+   mogdb=# SELECT ts_lexize('public.simple_dict','YeS');
+    ts_lexize
+   -----------
+
+   (1 row)
+
+   mogdb=# SELECT ts_lexize('public.simple_dict','The');
+    ts_lexize
+   -----------
+    {}
+   (1 row)
+   ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/4-synonym-dictionary.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/4-synonym-dictionary.md
new file mode 100644
index 0000000000000000000000000000000000000000..d841e2a83b16f909173508bbc1e318b13e6c77f8
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/4-synonym-dictionary.md
@@ -0,0 +1,116 @@
+---
+title: Synonym Dictionary
+summary: Synonym Dictionary
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Synonym Dictionary
+
+A **Synonym** dictionary is used to define, identify, and convert synonyms of a token. Phrases are not supported. Synonyms of phrases can be defined in a **Thesaurus** dictionary. For details, see [Thesaurus Dictionary](5-thesaurus-dictionary).
+
+## Examples
+
+- A **Synonym** dictionary can be used to overcome linguistic problems. For example, to prevent an English stemmer dictionary from reducing the word 'Paris' to 'pari', define a **Paris paris** line in the **Synonym** dictionary and put it before the **english_stem** dictionary.
+
+  ```sql
+  mogdb=# SELECT * FROM ts_debug('english', 'Paris');
+     alias   |   description   | token |  dictionaries  |  dictionary  | lexemes
+  -----------+-----------------+-------+----------------+--------------+---------
+   asciiword | Word, all ASCII | Paris | {english_stem} | english_stem | {pari}
+  (1 row)
+
+  mogdb=# CREATE TEXT SEARCH DICTIONARY my_synonym (
+      TEMPLATE = synonym,
+      SYNONYMS = my_synonyms,
+      FILEPATH = 'file:///home/dicts/'
+  );
+
+  mogdb=# ALTER TEXT SEARCH CONFIGURATION english
+      ALTER MAPPING FOR asciiword
+      WITH my_synonym, english_stem;
+
+  mogdb=# SELECT * FROM ts_debug('english', 'Paris');
+     alias   |   description   | token |       dictionaries        | dictionary | lexemes
+  -----------+-----------------+-------+---------------------------+------------+---------
+   asciiword | Word, all ASCII | Paris | {my_synonym,english_stem} | my_synonym | {paris}
+  (1 row)
+
+  mogdb=# SELECT * FROM ts_debug('english', 'paris');
+     alias   |   description   | token |       dictionaries        | dictionary | lexemes
+  -----------+-----------------+-------+---------------------------+------------+---------
+   asciiword | Word, all ASCII | Paris | {my_synonym,english_stem} | my_synonym | {paris}
+  (1 row)
+
+  mogdb=# ALTER TEXT SEARCH DICTIONARY my_synonym ( CASESENSITIVE=true);
+
+  mogdb=# SELECT * FROM ts_debug('english', 'Paris');
+     alias   |   description   | token |       dictionaries        | dictionary | lexemes
+  -----------+-----------------+-------+---------------------------+------------+---------
+   asciiword | Word, all ASCII | Paris | {my_synonym,english_stem} | my_synonym | {paris}
+  (1 row)
+
+  mogdb=# SELECT * FROM ts_debug('english', 'paris');
+     alias   |   description   | token |       dictionaries        | dictionary | lexemes
+  -----------+-----------------+-------+---------------------------+------------+---------
+   asciiword | Word, all ASCII | Paris | {my_synonym,english_stem} | my_synonym | {pari}
+  (1 row)
+
+  ```
+
+  The full name of the **Synonym** dictionary file is **my_synonyms.syn**, and the dictionary is stored in the **/home/dicts/** directory of the current database primary node. For details about the syntax and parameters for creating an **Ispell** dictionary, see [ALTER TEXT SEARCH DICTIONARY](26-ALTER-TEXT-SEARCH-DICTIONARY).
+
+- An asterisk (*) can be placed at the end of a synonym in the configuration file. This indicates that the synonym is a prefix. The asterisk is ignored when the entry is used in to_tsvector(), but when it is used in to_tsquery(), the result will be a query item with the prefix match marker (see [Manipulating Queries](2-manipulating-queries)).
+
+  Assume that the content in the dictionary file **synonym_sample.syn** is as follows:
+
+  ```sql
+  postgres        pgsql
+  postgresql      pgsql
+  postgre pgsql
+  gogle   googl
+  indices index*
+  ```
+
+  Create and use a dictionary.
+
+  ```sql
+  mogdb=# CREATE TEXT SEARCH DICTIONARY syn (
+      TEMPLATE = synonym,
+      SYNONYMS = synonym_sample
+  );
+
+  mogdb=# SELECT ts_lexize('syn','indices');
+   ts_lexize
+  -----------
+   {index}
+  (1 row)
+
+  mogdb=# CREATE TEXT SEARCH CONFIGURATION tst (copy=simple);
+
+  mogdb=# ALTER TEXT SEARCH CONFIGURATION tst ALTER MAPPING FOR asciiword WITH syn;
+
+  mogdb=# SELECT to_tsvector('tst','indices');
+   to_tsvector
+  -------------
+   'index':1
+  (1 row)
+
+  mogdb=# SELECT to_tsquery('tst','indices');
+   to_tsquery
+  ------------
+   'index':*
+  (1 row)
+
+  mogdb=# SELECT 'indexes are very useful'::tsvector;
+              tsvector
+  ---------------------------------
+   'are' 'indexes' 'useful' 'very'
+  (1 row)
+
+  mogdb=# SELECT 'indexes are very useful'::tsvector @@ to_tsquery('tst','indices');
+   ?column?
+  ----------
+   t
+  (1 row)
+  ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/5-thesaurus-dictionary.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/5-thesaurus-dictionary.md
new file mode 100644
index 0000000000000000000000000000000000000000..a1797c4a840a11dff3b22784b77140e627bf0b5f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/5-thesaurus-dictionary.md
@@ -0,0 +1,92 @@
+---
+title: Thesaurus Dictionary
+summary: Thesaurus Dictionary
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Thesaurus Dictionary
+
+A **Thesaurus** dictionary (sometimes abbreviated as TZ) is a collection of relationships between words and phrases, such as broader terms (BT), narrower terms (NT), preferred terms, non-preferred terms, and related terms. Based on definitions in the dictionary file, a TZ replaces all non-preferred terms by one preferred term and, optionally, preserves the original terms for indexing as well. A TZ is an extension of a **Synonym** dictionary with added phrase support.
+
+## Precautions
+
+- A TZ has the capability to recognize phrases and therefore it must remember its state and interact with the parser to determine whether to handle the next token or stop accumulation. A TZ must be configured carefully. For example, if a TZ is configured to handle only **asciiword** tokens, a TZ definition like **one 7** will not work because the token type **uint** is not assigned to the TZ.
+- TZs are used during indexing, so any change in the TZ's parameters requires reindexing. For most other dictionary types, small changes such as adding or removing stop words does not force reindexing.
+
+## Procedure
+
+1. Create a TZ named **thesaurus_astro**.
+
+   **thesaurus_astro** is a simple astronomical TZ that defines two astronomical word combinations (word+synonym).
+
+   ```sql
+   supernovae stars : sn
+   crab nebulae : crab
+   ```
+
+   Run the following statement to create the TZ:
+
+   ```sql
+   mogdb=# CREATE TEXT SEARCH DICTIONARY thesaurus_astro (
+       TEMPLATE = thesaurus,
+       DictFile = thesaurus_astro,
+       Dictionary = pg_catalog.english_stem,
+       FILEPATH = 'file:///home/dicts/'
+   );
+   ```
+
+   The full name of the TZ file is **thesaurus_astro.ths**, and the TZ is stored in the **/home/dicts/** directory of the current database primary node. **pg_catalog.english_stem** is the subdictionary (a **Snowball** English stemmer) used for input normalization. The subdictionary has its own configuration (for example, stop words), which is not shown here. For details about the syntax and parameters for creating an **Ispell** dictionary, see [CREATE TEXT SEARCH DICTIONARY](65-CREATE-TEXT-SEARCH-DICTIONARY).
+
+2. Bind the TZ to the desired token types in the text search configuration.
+
+   ```sql
+   mogdb=# ALTER TEXT SEARCH CONFIGURATION russian
+       ALTER MAPPING FOR asciiword, asciihword, hword_asciipart
+       WITH thesaurus_astro, english_stem;
+   ```
+
+3. Use the TZ.
+
+   - Test the TZ.
+
+     The **ts_lexize** function is not very useful for testing the TZ because the function processes its input as a single token. Instead, you can use the **plainto_tsquery**, **to_tsvector**, or **to_tsquery** function which will break their input strings into multiple tokens.
+
+     ```sql
+     mogdb=# SELECT plainto_tsquery('russian','supernova star');
+      plainto_tsquery
+     -----------------
+      'sn'
+     (1 row)
+
+     mogdb=# SELECT to_tsvector('russian','supernova star');
+      to_tsvector
+     -------------
+      'sn':1
+     (1 row)
+
+     mogdb=# SELECT to_tsquery('russian','''supernova star''');
+      to_tsquery
+     ------------
+      'sn'
+     (1 row)
+
+     ```
+
+     **supernova star** matches **supernovae stars** in **thesaurus_astro** because the Snowball **english_stem** stemmer is specified in the **thesaurus_astro** definition. The stemmer removed **e** and **s**.
+
+   - To index the original phrase, include it in the right-hand part of the definition.
+
+     ```sql
+     supernovae stars : sn supernovae stars
+
+     mogdb=# ALTER TEXT SEARCH DICTIONARY thesaurus_astro (
+         DictFile = thesaurus_astro,
+         FILEPATH = 'file:///home/dicts/');
+
+     mogdb=# SELECT plainto_tsquery('russian','supernova star');
+            plainto_tsquery
+     -----------------------------
+      'sn' & 'supernova' & 'star'
+     (1 row)
+     ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/6-ispell-dictionary.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/6-ispell-dictionary.md
new file mode 100644
index 0000000000000000000000000000000000000000..c79804ea0c7124f0a28302efe942b5212d7e6a49
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/6-ispell-dictionary.md
@@ -0,0 +1,49 @@
+---
+title: Ispell Dictionary
+summary: Ispell Dictionary
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Ispell Dictionary
+
+An **Ispell** dictionary is a morphological dictionary, which can normalize different linguistic forms of a word into the same lexeme. For example, an English **Ispell** dictionary can match all declensions and conjugations of the search term **bank**, such as, **banking**, **banked**, **banks**, **banks'**, and **bank's**.
+
+MogDB does not provide any predefined **Ispell** dictionaries or dictionary files. The .dict files and .affix files support multiple open-source dictionary formats, including **Ispell**, **MySpell**, and **Hunspell**.
+
+## Procedure
+
+1. Obtain the dictionary definition file (.dict) and affix file (.affix).
+
+   You can use an open-source dictionary. The name extensions of the open-source dictionary may be .aff and .dic. In this case, you need to change them to .affix and .dict. In addition, for some dictionary files (for example, Norwegian dictionary files), you need to run the following commands to convert the character encoding to UTF-8:
+
+   ```bash
+   iconv -f ISO_8859-1 -t UTF-8 -o nn_no.affix nn_NO.aff
+   iconv -f ISO_8859-1 -t UTF-8 -o nn_no.dict nn_NO.dic
+   ```
+
+2. Create an **Ispell** dictionary.
+
+   ```sql
+   mogdb=# CREATE TEXT SEARCH DICTIONARY norwegian_ispell (
+       TEMPLATE = ispell,
+       DictFile = nn_no,
+       AffFile = nn_no,
+       FilePath = 'file:///home/dicts'
+   );
+   ```
+
+   The full names of the **Ispell** dictionary files are **nn_no.dict** and **nn_no.affix**, and the dictionary is stored in the **/home/dicts/** directory of the current database primary node. For details about the syntax and parameters for creating an dictionary, see [CREATE TEXT SEARCH DICTIONARY](65-CREATE-TEXT-SEARCH-DICTIONARY).
+
+3. Use the **Ispell** dictionary to split compound words.
+
+   ```sql
+   mogdb=# SELECT ts_lexize('norwegian_ispell', 'sjokoladefabrikk');
+         ts_lexize
+   ---------------------
+    {sjokolade,fabrikk}
+   (1 row)
+
+   ```
+
+   **MySpell** does not support compound words. **Hunspell** supports compound words. MogDB supports only the basic compound word operations of **Hunspell**. Generally, **Ispell** dictionaries recognize a limited set of words, so they should be followed by another broader dictionary, for example, a **Snowball** dictionary, which recognizes everything.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/7-snowball-dictionary.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/7-snowball-dictionary.md
new file mode 100644
index 0000000000000000000000000000000000000000..91a2fff8c43e3be223a02be493b1332fa8ad7e51
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/7-snowball-dictionary.md
@@ -0,0 +1,14 @@
+---
+title: Snowball Dictionary
+summary: Snowball Dictionary
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Snowball Dictionary
+
+A **Snowball** dictionary is based on a project by Martin Porter and is used for stem analysis, providing stemming algorithms for many languages. MogDB provides predefined **Snowball** dictionaries of many languages. You can query the [PG_TS_DICT](PG_TS_DICT) system catalog to view the predefined **Snowball** dictionaries and supported stemming algorithms.
+
+A **Snowball** dictionary recognizes everything, no matter whether it is able to simplify the word. Therefore, it should be placed at the end of the dictionary list. It is useless to place it before any other dictionary because a token will never pass it through to the next dictionary.
+
+For details about the syntax of **Snowball** dictionaries, see [CREATE TEXT SEARCH DICTIONARY](65-CREATE-TEXT-SEARCH-DICTIONARY).
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/7-configuration-examples.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/7-configuration-examples.md
new file mode 100644
index 0000000000000000000000000000000000000000..04dea4a660b316796ef472090db885989b729bfd
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/7-configuration-examples.md
@@ -0,0 +1,116 @@
+---
+title: Configuration Examples
+summary: Configuration Examples
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Configuration Examples
+
+Text search configuration specifies the following components required for converting a document into a **tsvector**:
+
+- A parser, decomposes a text into tokens.
+- Dictionary list, converts each token into a lexeme.
+
+Each time when the **to_tsvector** or **to_tsquery** function is invoked, a text search configuration is required to specify a processing procedure. The GUC parameter **default_text_search_config** specifies the default text search configuration, which will be used if the text search function does not explicitly specify a text search configuration.
+
+MogDB provides some predefined text search configurations. You can also create user-defined text search configurations. In addition, to facilitate the management of text search objects, multiple **gsql** meta-commands are provided to display information about text search objects. For details, see "Client Tool &gt; [Meta-Command Reference](client-tool#meta-command-reference)" in *Tool Reference*.
+
+## Procedure
+
+1. Create a text search configuration **ts_conf** by copying the predefined text search configuration **english**.
+
+   ```sql
+   mogdb=# CREATE TEXT SEARCH CONFIGURATION ts_conf ( COPY = pg_catalog.english );
+   CREATE TEXT SEARCH CONFIGURATION
+   ```
+
+2. Create a **Synonym** dictionary.
+
+   Assume that the definition file **pg_dict.syn** of the **Synonym** dictionary contains the following contents:
+
+   ```sql
+   postgres    pg
+   pgsql       pg
+   postgresql  pg
+   ```
+
+   Run the following statement to create the **Synonym** dictionary:
+
+   ```sql
+   mogdb=# CREATE TEXT SEARCH DICTIONARY pg_dict (
+        TEMPLATE = synonym,
+        SYNONYMS = pg_dict,
+        FILEPATH = 'file:///home/dicts'
+    );
+   ```
+
+3. Create an **Ispell** dictionary **english_ispell** (the dictionary definition file is from the open source dictionary).
+
+   ```sql
+   mogdb=# CREATE TEXT SEARCH DICTIONARY english_ispell (
+       TEMPLATE = ispell,
+       DictFile = english,
+       AffFile = english,
+       StopWords = english,
+       FILEPATH = 'file:///home/dicts'
+   );
+   ```
+
+4. Modify the text search configuration **ts_conf** and change the dictionary list for tokens of certain types. For details about token types, see [Parser](5-parser).
+
+   ```sql
+   mogdb=# ALTER TEXT SEARCH CONFIGURATION ts_conf
+       ALTER MAPPING FOR asciiword, asciihword, hword_asciipart,
+                         word, hword, hword_part
+       WITH pg_dict, english_ispell, english_stem;
+   ```
+
+5. In the text search configuration, set non-index or set the search for tokens of certain types.
+
+   ```sql
+   mogdb=# ALTER TEXT SEARCH CONFIGURATION ts_conf
+       DROP MAPPING FOR email, url, url_path, sfloat, float;
+   ```
+
+6. Use the text retrieval commissioning function ts_debug() to test the text search configuration **ts_conf**.
+
+   ```sql
+   mogdb=# SELECT * FROM ts_debug('ts_conf', '
+   PostgreSQL, the highly scalable, SQL compliant, open source object-relational
+   database management system, is now undergoing beta testing of the next
+   version of our software.
+   ');
+   ```
+
+7. You can set the default text search configuration of the current session to **ts_conf**. This setting is valid only for the current session.
+
+   ```sql
+   mogdb=# \dF+ ts_conf
+         Text search configuration "public.ts_conf"
+   Parser: "pg_catalog.default"
+         Token      |            Dictionaries
+   -----------------+-------------------------------------
+    asciihword      | pg_dict,english_ispell,english_stem
+    asciiword       | pg_dict,english_ispell,english_stem
+    file            | simple
+    host            | simple
+    hword           | pg_dict,english_ispell,english_stem
+    hword_asciipart | pg_dict,english_ispell,english_stem
+    hword_numpart   | simple
+    hword_part      | pg_dict,english_ispell,english_stem
+    int             | simple
+    numhword        | simple
+    numword         | simple
+    uint            | simple
+    version         | simple
+    word            | pg_dict,english_ispell,english_stem
+
+   mogdb=# SET default_text_search_config = 'public.ts_conf';
+   SET
+   mogdb=# SHOW default_text_search_config;
+    default_text_search_config
+   ----------------------------
+    public.ts_conf
+   (1 row)
+   ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/8-testing-and-debugging-text-search/1-testing-a-configuration.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/8-testing-and-debugging-text-search/1-testing-a-configuration.md
new file mode 100644
index 0000000000000000000000000000000000000000..8ec7ee1bf261dd13b8fa393ea8b560c8021e903f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/8-testing-and-debugging-text-search/1-testing-a-configuration.md
@@ -0,0 +1,65 @@
+---
+title: Testing a Configuration
+summary: Testing a Configuration
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Testing a Configuration
+
+The  **ts_debug**  function allows easy testing of a text search configuration.
+
+```sql
+ts_debug([ config regconfig, ] document text,
+         OUT alias text,
+         OUT description text,
+         OUT token text,
+         OUT dictionaries regdictionary[],
+         OUT dictionary regdictionary,
+         OUT lexemes text[])
+         returns setof record
+```
+
+**ts_debug** displays information about every token of document as produced by the parser and processed by the configured dictionaries. It uses the configuration specified by **config**, or **default_text_search_config** if that argument is omitted.
+
+**ts_debug** returns one row for each token identified in the text by the parser. The columns returned are:
+
+- **alias text**: short name of the token type
+- **description text**: description of the token type
+- **token text**: text of the token
+- **dictionaries regdictionary[]**: dictionaries selected by the configuration for this token type
+- **dictionary regdictionary**: the dictionary that recognized the token, or NULL if none did
+- **lexemes text[]**: the lexeme(s) produced by the dictionary that recognized the token, or NULL if none did; an empty array ({}) means the token was recognized as a stop word
+
+Here is a simple example:
+
+```sql
+mogdb=# SELECT * FROM ts_debug('english','a fat  cat sat on a mat - it ate a fat rats');
+   alias   |   description   | token |  dictionaries  |  dictionary  | lexemes
+-----------+-----------------+-------+----------------+--------------+---------
+ asciiword | Word, all ASCII | a     | {english_stem} | english_stem | {}
+ blank     | Space symbols   |       | {}             |              |
+ asciiword | Word, all ASCII | fat   | {english_stem} | english_stem | {fat}
+ blank     | Space symbols   |       | {}             |              |
+ asciiword | Word, all ASCII | cat   | {english_stem} | english_stem | {cat}
+ blank     | Space symbols   |       | {}             |              |
+ asciiword | Word, all ASCII | sat   | {english_stem} | english_stem | {sat}
+ blank     | Space symbols   |       | {}             |              |
+ asciiword | Word, all ASCII | on    | {english_stem} | english_stem | {}
+ blank     | Space symbols   |       | {}             |              |
+ asciiword | Word, all ASCII | a     | {english_stem} | english_stem | {}
+ blank     | Space symbols   |       | {}             |              |
+ asciiword | Word, all ASCII | mat   | {english_stem} | english_stem | {mat}
+ blank     | Space symbols   |       | {}             |              |
+ blank     | Space symbols   | -     | {}             |              |
+ asciiword | Word, all ASCII | it    | {english_stem} | english_stem | {}
+ blank     | Space symbols   |       | {}             |              |
+ asciiword | Word, all ASCII | ate   | {english_stem} | english_stem | {ate}
+ blank     | Space symbols   |       | {}             |              |
+ asciiword | Word, all ASCII | a     | {english_stem} | english_stem | {}
+ blank     | Space symbols   |       | {}             |              |
+ asciiword | Word, all ASCII | fat   | {english_stem} | english_stem | {fat}
+ blank     | Space symbols   |       | {}             |              |
+ asciiword | Word, all ASCII | rats  | {english_stem} | english_stem | {rat}
+(24 rows)
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/8-testing-and-debugging-text-search/2-testing-a-parser.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/8-testing-and-debugging-text-search/2-testing-a-parser.md
new file mode 100644
index 0000000000000000000000000000000000000000..c880441f9207856ce965e88a93c648dfb8e5c8fd
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/8-testing-and-debugging-text-search/2-testing-a-parser.md
@@ -0,0 +1,69 @@
+---
+title: Testing a Parser
+summary: Testing a Parser
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Testing a Parser
+
+The **ts_parse** function allows direct testing of a text search parser.
+
+```
+ts_parse(parser_name text, document text,
+         OUT tokid integer, OUT token text) returns setof record
+```
+
+**ts_parse** parses the given **document** and returns a series of records, one for each token produced by parsing. Each record includes a **tokid** showing the assigned token type and a **token** which is the text of the token. For example:
+
+```sql
+mogdb=# SELECT * FROM ts_parse('default', '123 - a number');
+ tokid | token
+-------+--------
+    22 | 123
+    12 |
+    12 | -
+     1 | a
+    12 |
+     1 | number
+(6 rows)
+```
+
+The **ts_token_type** function returns the token type and description of the specified parser.
+
+```
+ts_token_type(parser_name text, OUT tokid integer,
+              OUT alias text, OUT description text) returns setof record
+```
+
+**ts_token_type** returns a table which describes each type of token the specified parser can recognize. For each token type, the table gives the integer **tokid** that the parser uses to label a token of that type, the **alias** that names the token type in configuration commands, and a short description. For example:
+
+```sql
+mogdb=# SELECT * FROM ts_token_type('default');
+ tokid |      alias      |               description
+-------+-----------------+------------------------------------------
+     1 | asciiword       | Word, all ASCII
+     2 | word            | Word, all letters
+     3 | numword         | Word, letters and digits
+     4 | email           | Email address
+     5 | url             | URL
+     6 | host            | Host
+     7 | sfloat          | Scientific notation
+     8 | version         | Version number
+     9 | hword_numpart   | Hyphenated word part, letters and digits
+    10 | hword_part      | Hyphenated word part, all letters
+    11 | hword_asciipart | Hyphenated word part, all ASCII
+    12 | blank           | Space symbols
+    13 | tag             | XML tag
+    14 | protocol        | Protocol head
+    15 | numhword        | Hyphenated word, letters and digits
+    16 | asciihword      | Hyphenated word, all ASCII
+    17 | hword           | Hyphenated word, all letters
+    18 | url_path        | URL path
+    19 | file            | File or path name
+    20 | float           | Decimal notation
+    21 | int             | Signed integer
+    22 | uint            | Unsigned integer
+    23 | entity          | XML entity
+(23 rows)
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/8-testing-and-debugging-text-search/3-testing-a-dictionary.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/8-testing-and-debugging-text-search/3-testing-a-dictionary.md
new file mode 100644
index 0000000000000000000000000000000000000000..cff76d01c13b7b46ca9e5a290c16d1bb682ac920
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/8-testing-and-debugging-text-search/3-testing-a-dictionary.md
@@ -0,0 +1,29 @@
+---
+title: Testing a Dictionary
+summary: Testing a Dictionary
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Testing a Dictionary
+
+The **ts_lexize** function facilitates dictionary testing.
+
+**ts_lexize(dict regdictionary, token text) returns text[]** **ts_lexize** returns an array of lexemes if the input **token** is known to the dictionary, or an empty array if the token is known to the dictionary but it is a stop word, or **NULL** if it is an unknown word.
+
+Example:
+
+```sql
+mogdb=# SELECT ts_lexize('english_stem', 'stars');
+ ts_lexize
+-----------
+ {star}
+
+mogdb=# SELECT ts_lexize('english_stem', 'a');
+ ts_lexize
+-----------
+ {}
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> The **ts_lexize** function expects a single **token**, not text.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/9-limitations.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/9-limitations.md
new file mode 100644
index 0000000000000000000000000000000000000000..9f0a1e5fdec13ea9fafeafae8d8c6a615083417c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/9-limitations.md
@@ -0,0 +1,16 @@
+---
+title: Limitations
+summary: Limitations
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Limitations
+
+The current limitations of MogDB's text search features are:
+
+- The length of each lexeme must be less than 2 KB.
+- The length of a **tsvector** (lexemes + positions) must be less than 1 megabyte.
+- Position values in **tsvector** must be greater than 0 and no more than 16383.
+- No more than 256 positions per lexeme. Excessive positions, if any, will be discarded.
+- The number of nodes (lexemes + operators) in a tsquery must be less than 32768.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/7-system-operation.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/7-system-operation.md
new file mode 100644
index 0000000000000000000000000000000000000000..d0fba906a3c39515f65b04aaad2c984f8065bd49
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/7-system-operation.md
@@ -0,0 +1,38 @@
+---
+title: System Operation
+summary: System Operation
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# System Operation
+
+MogDB text runs SQL statements to perform different system operations, such as setting variables, displaying the execution plan, and collecting garbage data.
+
+## Setting Variables
+
+For details about how to set various parameters for a session or transaction, see [SET](127-SET).
+
+## Displaying the Execution Plan
+
+For details about how to display the execution plan that MogDB makes for SQL statements, see [EXPLAIN](105-EXPLAIN).
+
+## Specifying a Checkpoint in Transaction Logs
+
+By default, WALs periodically specify checkpoints in a transaction log. **CHECKPOINT** forces an immediate checkpoint when the related command is issued, without waiting for a regular checkpoint scheduled by the system. See [CHECKPOINT](35-CHECKPOINT).
+
+## Collecting Unnecessary Data
+
+For details about how to collect garbage data and analyze a database as required, See [VACUUM](137-VACUUM).
+
+## Collecting Statistics
+
+For details about how to collect statistics on tables in databases, See [ANALYZE | ANALYSE](32-ANALYZE-ANALYSE).
+
+## Setting the Constraint Check Mode for the Current Transaction
+
+For details about how to set the constraint check mode for the current transaction, See [SET CONSTRAINTS](128-SET-CONSTRAINTS).
+
+## Shutting Down The Current Database Node
+
+For details about shutting down the current database node, see [SHUTDOWN](133-SHUTDOWN).
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/8-controlling-transactions.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/8-controlling-transactions.md
new file mode 100644
index 0000000000000000000000000000000000000000..08523e0e7a6a4093df3b0452b4d8b6f7eab6f0b0
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/8-controlling-transactions.md
@@ -0,0 +1,29 @@
+---
+title: Controlling Transactions
+summary: Controlling Transactions
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Controlling Transactions
+
+A transaction is a user-defined sequence of database operations, which form an integral unit of work.
+
+## Starting a Transaction
+
+MogDB starts a transaction using START TRANSACTION and **BEGIN**. For details, see [START TRANSACTION](134-START-TRANSACTION) and [BEGIN](33-BEGIN).
+
+## Setting a Transaction
+
+MogDB sets a transaction using **SET TRANSACTION** or **SET LOCAL TRANSACTION**. For details, see [SET TRANSACTION](131-SET-TRANSACTION).
+
+## Committing a Transaction
+
+MogDB commits all operations of a transaction using **COMMIT** or **END**. For details, see [COMMIT | END](39-COMMIT-END).
+
+## Rolling Back a Transaction
+
+If a fault occurs during a transaction and the transaction cannot proceed, the system performs rollback to cancel all the completed database operations related to the transaction. See [ROLLBACK](121-ROLLBACK).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> If an execution request (not in a transaction block) received in the database contains multiple statements, the request is packed into a transaction. If one of the statements fails, the entire request will be rolled back.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/9-ddl-syntax-overview.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/9-ddl-syntax-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..3d640b3074f6923489641d3391dd2e5ba462eef0
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-reference/9-ddl-syntax-overview.md
@@ -0,0 +1,226 @@
+---
+title: DDL Syntax Overview
+summary: DDL Syntax Overview
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# DDL Syntax Overview
+
+Data definition language (DDL) is used to define or modify an object in a database, such as a table, an index, or a view.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** openGauss does not support DDL when the primary node of the database is incomplete. For example, if the primary node of the database in openGauss is faulty, creating a database or a table will fail.
+
+## Defining a CMK
+
+CMKs are used to encrypt CEKs for the encrypted database feature. CMK definition includes creating and deleting a CMK. For details about related SQL statements, see Table 1.
+
+**Table 1** SQL statements for defining a CMK
+
+| Function       | SQL Statement                                           |
+| :------------- | :------------------------------------------------------ |
+| Creating a CMK | [CREATE CLIENT MASTER KEY](42-CREATE-CLIENT-MASTER-KEY) |
+| Deleting a CMK | [DROP CLIENT MASTER KEY](76-DROP-CLIENT-MASTER-KEY)     |
+
+## Defining a CEK
+
+CEKs are used to encrypt data for the encrypted database feature. CEK definition includes creating and deleting a CEK. For details about related SQL statements, see Table 2.
+
+**Table 2** SQL statements for defining a CEK
+
+| Function       | SQL Statement                                                |
+| :------------- | :----------------------------------------------------------- |
+| Creating a CEK | [CREATE COLUMN ENCRYPTION KEY](43-CREATE-COLUMN-ENCRYPTION-KEY) |
+| Deleting a CEK | [DROP COLUMN ENCRYPTION KEY](77-DROP-COLUMN-ENCRYPTION-KEY)  |
+
+## Defining a Database
+
+A database is the warehouse for organizing, storing, and managing data. Defining a database includes creating a database, altering the database attributes, and deleting the database. For details about related SQL statements, see Table 3.
+
+**Table 3** SQL statements for defining a database
+
+| Function                     | SQL Statement                         |
+| :--------------------------- | :------------------------------------ |
+| Creating a database          | [CREATE DATABASE](44-CREATE-DATABASE) |
+| Altering database attributes | [ALTER DATABASE](2-ALTER-DATABASE)    |
+| Deleting a database          | [DROP DATABASE](78-DROP-DATABASE)     |
+
+## Defining a schema
+
+A schema is the set of a group of database objects and is used to control the access to the database objects. For details about related SQL statements, see Table 4.
+
+**Table 4** SQL statements for defining a schema
+
+| Function                   | SQL Statement                     |
+| :------------------------- | :-------------------------------- |
+| Creating a schema          | [CREATE SCHEMA](56-CREATE-SCHEMA) |
+| Altering schema attributes | [ALTER SCHEMA](15-ALTER-SCHEMA)   |
+| Deleting a schema          | [DROP SCHEMA](91-DROP-SCHEMA)     |
+
+## Defining a Tablespace
+
+A tablespace is used to manage data objects and corresponds to a catalog on a disk. For details about related SQL statements, see Table 5.
+
+**Table 5** SQL statements for defining a tablespace
+
+| Function                       | SQL Statement                             |
+| :----------------------------- | :---------------------------------------- |
+| Creating a tablespace          | [CREATE TABLESPACE](63-CREATE-TABLESPACE) |
+| Altering tablespace attributes | [ALTER TABLESPACE](24-ALTER-TABLESPACE)   |
+| Deleting a tablespace          | [DROP TABLESPACE](96-DROP-TABLESPACE)     |
+
+## Defining a Table
+
+A table is a special data structure in a database and is used to store data objects and relationship between data objects. For details about related SQL statements, see Table 6.
+
+**Table 6** SQL statements for defining a table
+
+| Function                  | SQL Statement                   |
+| :------------------------ | :------------------------------ |
+| Creating a table          | [CREATE TABLE](60-CREATE-TABLE) |
+| Altering table attributes | [ALTER TABLE](22-ALTER-TABLE)   |
+| Deleting a table          | [DROP TABLE](95-DROP-TABLE)     |
+
+## Defining a Partitioned Table
+
+A partitioned table is a logical table used to improve query performance and does not store data (data is stored in common tables). For details about related SQL statements, see Table 7.
+
+**Table 7** SQL statements for defining a partitioned table
+
+| Function                              | SQL Statement                                       |
+| :------------------------------------ | :-------------------------------------------------- |
+| Creating a partitioned table          | [CREATE TABLE PARTITION](62-CREATE-TABLE-PARTITION) |
+| Creating a partition                  | [ALTER TABLE PARTITION](23-ALTER-TABLE-PARTITION)   |
+| Altering partitioned table attributes | [ALTER TABLE PARTITION](23-ALTER-TABLE-PARTITION)   |
+| Deleting a partition                  | [ALTER TABLE PARTITION](23-ALTER-TABLE-PARTITION)   |
+| Deleting a partitioned table          | [DROP TABLE](95-DROP-TABLE)                         |
+
+## Defining an Index
+
+An index indicates the sequence of values in one or more columns in a database table. It is a data structure that improves the speed of data access to specific information in a database table. For details about related SQL statements, see Table 8.
+
+**Table 8** SQL statements for defining an index
+
+| Function                  | SQL Statement                   |
+| :------------------------ | :------------------------------ |
+| Creating an index         | [CREATE INDEX](50-CREATE-INDEX) |
+| Altering index attributes | [ALTER INDEX](9-ALTER-INDEX)    |
+| Deleting an index         | [DROP INDEX](84-DROP-INDEX)     |
+| Rebuilding an index       | [REINDEX](117-REINDEX)          |
+
+## Defining a Stored Procedure
+
+A stored procedure is a set of SQL statements for achieving specific functions and is stored in the database after compiling. Users can specify a name and provide parameters (if necessary) to execute the stored procedure. For details about related SQL statements, see Table 9.
+
+**Table 9** SQL statements for defining a stored procedure
+
+| Function                    | SQL Statement                           |
+| :-------------------------- | :-------------------------------------- |
+| Creating a stored procedure | [CREATE PROCEDURE](53-CREATE-PROCEDURE) |
+| Deleting a stored procedure | [DROP PROCEDURE](88-DROP-PROCEDURE)     |
+
+## Defining a Function
+
+In openGauss, a function is similar to a stored procedure, which is a set of SQL statements. The function and stored procedure are used the same. For details about related SQL statements, see Table 10.
+
+**Table 10** SQL statements for defining a function
+
+| Function                     | SQL Statement                         |
+| :--------------------------- | :------------------------------------ |
+| Creating a function          | [CREATE FUNCTION](48-CREATE-FUNCTION) |
+| Altering function attributes | [ALTER FUNCTION](7-ALTER-FUNCTION)    |
+| Deleting a function          | [DROP FUNCTION](82-DROP-FUNCTION)     |
+
+## Defining a Package
+
+A package consists of the package specification and package body. It is used to manage stored procedures and functions by class, which is similar to classes in languages such as Java and C++.
+
+**Table 11** SQL statements for defining a package
+
+| Function           | SQL Statement                         |
+| :----------------- | :------------------------------------ |
+| Creating a package | [CREATE PACKAGE](51.2-CREATE-PACKAGE) |
+| Deleting a package | [DROP PACKAGE](86.3-DROP-PACKAGE)     |
+
+## Defining a View
+
+A view is a virtual table exported from one or more basic tables. It is used to control data accesses of users. Table 12 lists the related SQL statements.
+
+**Table 12** SQL statements for defining a view
+
+| Function        | SQL Statement                 |
+| :-------------- | :---------------------------- |
+| Creating a view | [CREATE VIEW](70-CREATE-VIEW) |
+| Deleting a view | [DROP VIEW](103-DROP-VIEW)    |
+
+## Defining a Cursor
+
+To process SQL statements, the stored procedure process assigns a memory segment to store context association. Cursors are handles or pointers to context regions. With a cursor, the stored procedure can control alterations in context areas. For details, see Table 13.
+
+**Table 13** SQL statements for defining a cursor
+
+| Function                    | SQL Statement       |
+| :-------------------------- | :------------------ |
+| Creating a cursor           | [CURSOR](71-CURSOR) |
+| Moving a cursor             | [MOVE](111-MOVE)    |
+| Fetching data from a cursor | [FETCH](107-FETCH)  |
+| Closing a cursor            | [CLOSE](36-CLOSE)   |
+
+## Defining an Aggregate Function
+
+**Table 14** SQL statements for defining an aggregate function
+
+| Function                        | SQL Statement                             |
+| :------------------------------ | :---------------------------------------- |
+| Creating an aggregate function  | [CREATE AGGREGATE](41.1-CREATE-AGGREGATE) |
+| Modifying an aggregate function | [ALTER AGGREGATE](1.1-ALTER-AGGREGATE)    |
+| Deleting an aggregate function  | [DROP AGGREGATE](75.1-DROP-AGGREGATE)     |
+
+## Defining Data Type Conversion
+
+**Table 15** SQL statements for defining a data type
+
+| Function                                   | SQL Statement                   |
+| :----------------------------------------- | :------------------------------ |
+| Creating user-defined data type conversion | [CREATE CAST](41.3-CREATE-CAST) |
+| Deleting user-defined data type conversion | [DROP CAST](75.3-DROP-CAST)     |
+
+## Defining a Plug-in Extension
+
+**Table 16** SQL statements for defining a plug-in extension
+
+| Function                      | SQL Statement                             |
+| :---------------------------- | :---------------------------------------- |
+| Creating a plug-in extension  | [CREATE EXTENSION](46.1-CREATE-EXTENSION) |
+| Modifying a plug-in extension | [ALTER EXTENSION](5.1-ALTER-EXTENSION)    |
+| Deleting a plug-in extension  | [DROP EXTENSION](80.1-DROP-EXTENSION)     |
+
+## Defining an Operator
+
+**Table 17** SQL statements for defining an operator
+
+| Function              | SQL Statement                           |
+| :-------------------- | :-------------------------------------- |
+| Creating an operator  | [CREATE OPERATOR](51.1-CREATE-OPERATOR) |
+| Modifying an operator | [ALTER OPERATOR](11.1-ALTER-OPERATOR)   |
+| Deleting an operator  | [DROP OPERATOR](85.1-DROP-OPERATOR)     |
+
+## Defining a Procedural Language
+
+**Table 18** SQL statements for defining a procedural language
+
+| Function                       | SQL Statement                           |
+| :----------------------------- | :-------------------------------------- |
+| Creating a procedural language | [CREATE LANGUAGE](50.1-CREATE-LANGUAGE) |
+| Changing a procedural language | [ALTER LANGUAGE](9.1-ALTER-LANGUAGE)    |
+| Deleting a procedural language | [DROP LANGUAGE](84.1-DROP-LANGUAGE)     |
+
+## Defining a Data Type
+
+**Table 19** SQL statements for defining a data type
+
+| Function              | SQL Statement                 |
+| :-------------------- | :---------------------------- |
+| Creating a data type  | [CREATE TYPE](67-CREATE-TYPE) |
+| Modifying a data type | [ALTER TYPE](28-ALTER-TYPE)   |
+| Deleting a data type  | [DROP TYPE](100-DROP-TYPE)    |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/1-ABORT.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/1-ABORT.md
new file mode 100644
index 0000000000000000000000000000000000000000..27d713827f996523c48d08a73e69c0ac3ccc71bf
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/1-ABORT.md
@@ -0,0 +1,76 @@
+---
+title: ABORT
+summary: ABORT
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ABORT
+
+## Function
+
+**ABORT** rolls back the current transaction and cancels the changes in the transaction.
+
+This command is equivalent to **ROLLBACK**, and is present only for historical reasons. Now **ROLLBACK** is recommended.
+
+## Precautions
+
+**ABORT**  has no impact outside a transaction, but will throw a NOTICE message.
+
+## Syntax
+
+```ebnf+diagram
+Abort ::= ABORT [ WORK | TRANSACTION ];
+```
+
+## Parameter Description
+
+**WORK | TRANSACTION**
+
+Specifies an optional keyword, which has no effect except increasing readability.
+
+## Examples
+
+```sql
+-- Create the customer_demographics_t1 table.
+mogdb=# CREATE TABLE customer_demographics_t1
+(
+    CD_DEMO_SK                INTEGER               NOT NULL,
+    CD_GENDER                 CHAR(1)                       ,
+    CD_MARITAL_STATUS         CHAR(1)                       ,
+    CD_EDUCATION_STATUS       CHAR(20)                      ,
+    CD_PURCHASE_ESTIMATE      INTEGER                       ,
+    CD_CREDIT_RATING          CHAR(10)                      ,
+    CD_DEP_COUNT              INTEGER                       ,
+    CD_DEP_EMPLOYED_COUNT     INTEGER                       ,
+    CD_DEP_COLLEGE_COUNT      INTEGER
+)
+WITH (ORIENTATION = COLUMN,COMPRESSION=MIDDLE)
+;
+
+-- Insert data.
+mogdb=# INSERT INTO customer_demographics_t1 VALUES(1920801,'M', 'U', 'DOCTOR DEGREE', 200, 'GOOD', 1, 0,0);
+
+-- Start a transaction.
+mogdb=# START TRANSACTION;
+
+-- Update the column.
+mogdb=# UPDATE customer_demographics_t1 SET cd_education_status= 'Unknown';
+
+-- Abort the transaction. All updates are rolled back.
+mogdb=# ABORT;
+
+-- Query data.
+mogdb=# SELECT * FROM customer_demographics_t1 WHERE cd_demo_sk = 1920801;
+cd_demo_sk | cd_gender | cd_marital_status | cd_education_status  | cd_purchase_estimate | cd_credit_rating | cd_dep_count | cd_dep_employed_count | cd_dep_college_count
+------------+-----------+-------------------+----------------------+----------------------+------------------+--------------+-----------------------+----------------------
+    1920801 | M         | U                 | DOCTOR DEGREE        |                  200 | GOOD             |            1 |                     0 |                    0
+(1 row)
+
+-- Delete the table.
+mogdb=# DROP TABLE customer_demographics_t1;
+```
+
+## Helpful Links
+
+[SET TRANSACTION](131-SET-TRANSACTION), [COMMIT | END](39-COMMIT-END), [ROLLBACK](121-ROLLBACK)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/1.1-ALTER-AGGREGATE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/1.1-ALTER-AGGREGATE.md
new file mode 100644
index 0000000000000000000000000000000000000000..3d391a6d74f516f332ebef2b65ccb7f2d2c10aaa
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/1.1-ALTER-AGGREGATE.md
@@ -0,0 +1,76 @@
+---
+title: ALTER AGGREGATE
+summary: ALTER AGGREGATE
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# ALTER AGGREGATE
+
+## Function
+
+**ALTER AGGREGATE** modifies the definition of an aggregate function.
+
+## Precautions
+
+To use **ALTER AGGREGATE**, you must be the owner of the aggregate function. To change the schema of an aggregate function, you must have the **CREATE** permission on the new schema. To change the owner, you must be a direct or indirect member of the new role, and the role must have the **CREATE** permission on the aggregate function's schema. (This restricts the owner from doing anything except for deleting and recreating aggregate functions. However, the super user can change the ownership of an aggregate function in any way.)
+
+## Syntax
+
+```ebnf+diagram
+AlterAggregate ::= ALTER AGGREGATE name ( argtype [ , ... ] ) RENAME TO new_name;
+```
+
+```ebnf+diagram
+AlterAggregate ::= ALTER AGGREGATE name ( argtype [ , ... ] ) OWNER TO new_owner;
+```
+
+```ebnf+diagram
+AlterAggregate ::= ALTER AGGREGATE name ( argtype [ , ... ] ) SET SCHEMA new_schema;
+```
+
+## Parameter Description
+
+- **name**
+
+  Name (optionally schema-qualified) of an existing aggregate function.
+
+- **argtype**
+
+  Input data type of the aggregate function. To reference a zero-parameter aggregate function, you can write an asterisk (*) instead of a list of input data types.
+
+- **new_name**
+
+  New name of the aggregate function.
+
+- **new_owner**
+
+  New owner of the aggregate function.
+
+- **new_schema**
+
+  New schema of the aggregate function.
+
+## Examples
+
+Rename the aggregate function **myavg** that accepts integer-type parameters to **my_average**.
+
+```sql
+ALTER AGGREGATE myavg(integer) RENAME TO my_average;
+```
+
+Change the owner of the aggregate function **myavg** that accepts integer-type parameters to **joe**.
+
+```sql
+ALTER AGGREGATE myavg(integer) OWNER TO joe;
+```
+
+Move the aggregate function **myavg** that accepts integer-type parameters to **myschema**.
+
+```sql
+ALTER AGGREGATE myavg(integer) SET SCHEMA myschema;
+```
+
+## Compatibility
+
+The SQL standard does not contain the **ALTER AGGREGATE** statement.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/1.2-ALTER-AUDIT-POLICY.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/1.2-ALTER-AUDIT-POLICY.md
new file mode 100644
index 0000000000000000000000000000000000000000..35ba50172f690988abc4dfe74a436cae8e484438
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/1.2-ALTER-AUDIT-POLICY.md
@@ -0,0 +1,98 @@
+---
+title: ALTER AUDIT POLICY
+summary: ALTER AUDIT POLICY
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# ALTER AUDIT POLICY
+
+## Function
+
+**ALTER AUDIT POLICY** modifies the unified audit policy.
+
+## Precautions
+
+- Only users with the  **poladmin**  or  **sysadmin**  permission, or the initial user can perform this operation.
+- The unified audit policy takes effect only after **enable_security_policy** is set to **on**.
+
+## Syntax
+
+```ebnf+diagram
+AlterAuditPolicy ::= ALTER AUDIT POLICY [ IF EXISTS ] policy_name { ADD | REMOVE } { [ privilege_audit_clause ] [ access_audit_clause ] };
+```
+
+```ebnf+diagram
+AlterAuditPolicy ::= ALTER AUDIT POLICY [ IF EXISTS ] policy_name MODIFY ( filter_group_clause );
+ALTER AUDIT POLICY [ IF EXISTS ] policy_name DROP FILTER;
+```
+
+```ebnf+diagram
+AlterAuditPolicy ::= ALTER AUDIT POLICY [ IF EXISTS ] policy_name COMMENTS policy_comments;
+```
+
+```ebnf+diagram
+AlterAuditPolicy ::= ALTER AUDIT POLICY [ IF EXISTS ] policy_name { ENABLE | DISABLE };
+```
+
+- privilege_audit_clause：
+
+  ```ebnf+diagram
+  privilege_audit_clause ::= PRIVILEGES { DDL | ALL };
+  ```
+
+- access_audit_clause：
+
+  ```ebnf+diagram
+  access_audit_clause ::= ACCESS { DML | ALL };
+  ```
+
+- filter_group_clause
+
+  ```ebnf+diagram
+  filter_group_clause ::= FILTER ON {(FILTER_TYPE (filter_value [, ...])) [, ...]};
+  ```
+
+## Parameter Description
+
+- **policy_name**
+
+  Specifies the audit policy name, which must be unique.
+
+  Value range: a string. It must comply with the identifier naming convention.
+
+- **DDL**
+
+  Specifies the operations that are audited in the database: **CREATE**, **ALTER**, **DROP**, **ANALYZE**, **COMMENT**, **GRANT**, **REVOKE**, **SET**, **SHOW**, **LOGIN_ANY**, **LOGIN_FAILURE**, **LOGIN_SUCCESS**, and **LOGOUT**.
+
+- **ALL**
+
+  Specifies all operations supported by the specified DDL statements in the database.
+
+- **DML**
+
+  Specifies the operations that are audited in the database: **SELECT**, **COPY**, **DEALLOCATE**, **DELETE**, **EXECUTE**, **INSERT**, **PREPARE**, **REINDEX**, **TRUNCATE**, and **UPDATE**.
+
+- **FILTER_TYPE**
+
+  Specifies the types of information to be filtered by the policy:  **IP**,  **ROLES**, and  **APP**.
+
+- **filter_value**
+
+  Specifies the detailed information to be filtered.
+
+- **policy_comments**
+
+  Records description information of the audit policy.
+
+- **ENABLE|DISABLE**
+
+  Enables or disables the unified audit policy. If **ENABLE|DISABLE** is not specified, **ENABLE** is used by default.
+
+## Examples
+
+See **Examples** in [CREATE AUDIT POLICY](41.2-CREATE-AUDIT-POLICY).
+
+## Helpful Links
+
+[CREATE AUDIT POLICY](41.2-CREATE-AUDIT-POLICY), [DROP AUDIT POLICY](75.2-DROP-AUDIT-POLICY).
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/10-ALTER-LARGE-OBJECT.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/10-ALTER-LARGE-OBJECT.md
new file mode 100644
index 0000000000000000000000000000000000000000..337447e34b24e3e16530e997f61cb640baba302c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/10-ALTER-LARGE-OBJECT.md
@@ -0,0 +1,41 @@
+---
+title: ALTER LARGE OBJECT
+summary: ALTER LARGE OBJECT
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER LARGE OBJECT
+
+## Function
+
+**ALTER LARGE OBJECT** changes the owner of a large object.
+
+## Precautions
+
+Only a system administrator or the owner of the to-be-modified large object can run **ALTER LARGE OBJECT**.
+
+## Syntax
+
+```ebnf+diagram
+AlterLargeObject ::= ALTER LARGE OBJECT large_object_oid
+    OWNER TO new_owner;
+```
+
+## Parameter Description
+
+- **large_object_oid**
+
+  Specifies the OID of the large object to be modified.
+
+  Value range: an existing large object name
+
+- **OWNER TO new_owner**
+
+  Specifies the new owner of an object.
+
+  Value range: an existing username or role name
+
+## Examples
+
+None
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/10.1-ALTER-MASKING-POLICY.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/10.1-ALTER-MASKING-POLICY.md
new file mode 100644
index 0000000000000000000000000000000000000000..c5492b7f7150008e54af56c2ffbb30832b244a5d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/10.1-ALTER-MASKING-POLICY.md
@@ -0,0 +1,140 @@
+---
+title: ALTER MASKING POLICY
+summary: ALTER MASKING POLICY
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# ALTER MASKING POLICY
+
+## Function
+
+**ALTER MASKING POLICY** modifies masking policies.
+
+## Precautions
+
+- Only users with the  **poladmin**  or  **sysadmin**  permission, or the initial user can perform this operation.
+- The masking policy takes effect only after **enable_security_policy** is set to **on**.
+
+## Syntax
+
+- Modify the policy description.
+
+  ```ebnf+diagram
+  AlterMaskingPolicy ::= ALTER MASKING POLICY policy_name COMMENTS policy_comments;
+  ```
+
+- Modify the masking method.
+
+  ```ebnf+diagram
+  AlterMaskingPolicy ::= ALTER MASKING POLICY policy_name [ADD | REMOVE | MODIFY] masking_actions[, ...]*;
+  ```
+
+  The syntax of masking_action.
+
+  ```ebnf+diagram
+  masking_action ::= masking_function ON LABEL(label_name[, ...]*)
+  ```
+
+- Modify the scenarios where the masking policies take effect.
+
+  ```ebnf+diagram
+  AlterMaskingPolicy ::= ALTER MASKING POLICY policy_name MODIFY(FILTER ON FILTER_TYPE(filter_value[, ...]*)[, ...]*);
+  ```
+
+- Removes the filters of the masking policies.
+
+  ```ebnf+diagram
+  AlterMaskingPolicy ::= ALTER MASKING POLICY policy_name DROP FILTER;
+  ```
+
+- Enable or disable the masking policies.
+
+  ```ebnf+diagram
+  AlterMaskingPolicy ::= ALTER MASKING POLICY policy_name [ENABLE | DISABLE];
+  ```
+
+## Parameter Description
+
+- **policy_name**
+
+  Specifies the masking policy name, which must be unique.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **policy_comments**
+
+  Adds or modifies description of masking policies.
+
+- **masking_function**
+
+  Specifies eight preset masking methods or user-defined functions. Schemas are supported.
+
+  **maskall**  is not a preset function. It is hard-coded and cannot be displayed by running  **\\df**.
+
+  The masking methods during presetting are as follows:
+
+  ```bash
+  maskall | randommasking | creditcardmasking | basicemailmasking | fullemailmasking | shufflemasking | alldigitsmasking | regexpmasking
+  ```
+
+- **label_name**
+
+  Specifies the resource label name.
+
+- **FILTER_TYPE**
+
+  Specifies the types of information to be filtered by the policies: **IP**, **ROLES**, and **APP**.
+
+- **filter_value**
+
+  Indicates the detailed information to be filtered, such as the IP address, app name, and username.
+
+- **ENABLE|DISABLE**
+
+  Enables or disables the masking policy. If **ENABLE|DISABLE** is not specified, **ENABLE** is used by default.
+
+## Examples
+
+```sql
+-- Create users dev_mask and bob_mask.
+mogdb=# CREATE USER dev_mask PASSWORD 'dev@1234';
+mogdb=# CREATE USER bob_mask PASSWORD 'bob@1234';
+
+-- Create table tb_for_masking.
+mogdb=# CREATE TABLE tb_for_masking(col1 text, col2 text, col3 text);
+
+-- Create a resource label for label sensitive column col1.
+mogdb=# CREATE RESOURCE LABEL mask_lb1 ADD COLUMN(tb_for_masking.col1);
+
+-- Create a resource label for label sensitive column col2.
+mogdb=# CREATE RESOURCE LABEL mask_lb2 ADD COLUMN(tb_for_masking.col2);
+
+-- Create a masking policy for the operation of accessing sensitive column col1.
+mogdb=# CREATE MASKING POLICY maskpol1 maskall ON LABEL(mask_lb1);
+
+-- Add description for masking policy maskpol1.
+mogdb=# ALTER MASKING POLICY maskpol1 COMMENTS 'masking policy for tb_for_masking.col1';
+
+-- Modify masking policy maskpol1 to add a masking method.
+mogdb=# ALTER MASKING POLICY maskpol1 ADD randommasking ON LABEL(mask_lb2);
+
+-- Modify masking policy maskpol1 to remove a masking method.
+mogdb=# ALTER MASKING POLICY maskpol1 REMOVE randommasking ON LABEL(mask_lb2);
+
+-- Modify masking policy maskpol1 to modify a masking method.
+mogdb=# ALTER MASKING POLICY maskpol1 MODIFY randommasking ON LABEL(mask_lb1);
+
+-- Modify masking policy maskpol1 so that it takes effect only for scenarios where users are dev_mask and bob_mask, client tools are psql and gsql, and the IP addresses are 10.20.30.40 and 127.0.0.0/24.
+mogdb=# ALTER MASKING POLICY maskpol1 MODIFY (FILTER ON ROLES(dev_mask, bob_mask), APP(psql, gsql), IP('10.20.30.40', '127.0.0.0/24'));
+
+-- Modify masking policy maskpol1 so that it takes effect for all user scenarios.
+mogdb=# ALTER MASKING POLICY maskpol1 DROP FILTER;
+
+-- Disable masking policy maskpol1.
+mogdb=# ALTER MASKING POLICY maskpol1 DISABLE;
+```
+
+## Helpful Links
+
+[CREATE MASKING POLICY](50.2-CREATE-MASKING-POLICY), [DROP MASKING POLICY](84.2-DROP-MASKING-POLICY).
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/100-DROP-TYPE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/100-DROP-TYPE.md
new file mode 100644
index 0000000000000000000000000000000000000000..d26cba03bb9e1e299c6b90f12de0e40fdd0c61d3
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/100-DROP-TYPE.md
@@ -0,0 +1,48 @@
+---
+title: DROP TYPE
+summary: DROP TYPE
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP TYPE
+
+## Function
+
+**DROP TYPE** deletes a user-defined data type.
+
+## Precautions
+
+Only the type owner or a user granted with the DROP permission can run the **DROP TYPE** command. The system administrator has this permission by default.
+
+## Syntax
+
+```ebnf+diagram
+DropType ::= DROP TYPE [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]
+```
+
+## Parameter Description
+
+- **IF EXISTS**
+
+  Reports a notice instead of an error if the specified type does not exist.
+
+- **name**
+
+  Specifies the name (optionally schema-qualified) of the type to be deleted.
+
+- **CASCADE**
+
+  Automatically deletes the objects (such as fields, functions, and operators) that depend on the type.
+
+  **RESTRICT**
+
+  Refuses to delete the type if any objects depend on it. This is the default action.
+
+## Example
+
+See **Examples** in **CREATE TYPE**.
+
+## Helpful Links
+
+[CREATE TYPE](67-CREATE-TYPE) and [ALTER TYPE](28-ALTER-TYPE)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/101-DROP-USER.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/101-DROP-USER.md
new file mode 100644
index 0000000000000000000000000000000000000000..1d34bf4dcb62deb619c66194b054309554abcc1a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/101-DROP-USER.md
@@ -0,0 +1,59 @@
+---
+title: DROP USER
+summary: DROP USER
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP USER
+
+## Function
+
+**DROP USER** deletes a user and the schema with the same name as the user.
+
+## Precautions
+
+- **CASCADE** is used to delete the objects (excluding databases) that depend on the user. **CASCADE** cannot delete locked objects unless the objects are unlocked or the processes locking the objects are killed.
+- In MogDB, the **enable_kill_query** configuration parameter exists in the **postgresql.conf** file. This parameter affects **CASCADE**.
+  - If **enable_kill_query** is **on** and **CASCADE** is used, the statement automatically kills the processes locking dependent objects and then deletes the specified user.
+  - If **enable_kill_query** is **off** and **CASCADE** is used, the statement waits until the processes locking dependent objects stop and then deletes the specified user.
+- If the dependent objects are other databases or reside in other databases, manually delete them before deleting the user from the current database. **DROP USER** cannot delete objects across databases.
+- If a data source depends on the user, the user cannot be deleted directly. You need to manually delete the data source first.
+
+## Syntax
+
+```ebnf+diagram
+DropUser ::= DROP USER [ IF EXISTS ] user_name [, ...] [ CASCADE | RESTRICT ];
+```
+
+## Parameter Description
+
+- **IF EXISTS**
+
+  Reports a notice instead of an error if the specified user does not exist.
+
+- **user_name**
+
+  Specifies the name of the user to be deleted.
+
+  Value range: an existing username
+
+- **CASCADE | RESTRICT**
+
+  - **CASCADE**: automatically deletes the objects that depend on the user.
+
+  - **RESTRICT**: refuses to delete the user if any objects depend on it. This is the default action.
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+    > In MogDB, the **enable_kill_query** configuration parameter exists in the **postgresql.conf** file. This parameter affects **CASCADE**.
+    >
+    > - If **enable_kill_query** is **on** and **CASCADE** is used, the statement automatically kills the processes locking dependent objects and then deletes the specified user.
+    > - If **enable_kill_query** is **off** and **CASCADE** is used, the statement waits until the processes locking dependent objects stop and then deletes the specified user.
+
+## Examples
+
+See **Example** in **CREATE USER**.
+
+## Helpful Links
+
+[ALTER USER](29-ALTER-USER) and [CREATE USER](68-CREATE-USER)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/102-DROP-USER-MAPPING.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/102-DROP-USER-MAPPING.md
new file mode 100644
index 0000000000000000000000000000000000000000..c5df5c41ff10a8267d79205c378076757a629736
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/102-DROP-USER-MAPPING.md
@@ -0,0 +1,38 @@
+---
+title: DROP USER MAPPING
+summary: DROP USER MAPPING
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP USER MAPPING
+
+## Function
+
+**DROP USER MAPPING** drops a user mapping for a foreign server.
+
+## Syntax
+
+```ebnf+diagram
+DropUserMapping ::= DROP USER MAPPING [ IF EXISTS ] FOR { user_name | USER | CURRENT_USER | PUBLIC } SERVER server_name;
+```
+
+## Parameter Description
+
+- **IF EXISTS**
+
+  Reports a notice instead of an error if the user mapping does not exist.
+
+- **user_name**
+
+  Specifies user name of the mapping.
+
+  CURRENT_USER and USER match the name of the current user. PUBLIC is used to match all current and future user names in the system.
+
+- **server_name**
+
+  Specifies name of the server to which the user is mapped.
+
+## Helpful Links
+
+[ALTER USER MAPPING](30-ALTER-USER-MAPPING) and [CREATE USER MAPPING](69-CREATE-USER-MAPPING)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/103-DROP-VIEW.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/103-DROP-VIEW.md
new file mode 100644
index 0000000000000000000000000000000000000000..8d59b53a2755ad8a5d0e764ed2fdd53b1d98d6b7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/103-DROP-VIEW.md
@@ -0,0 +1,47 @@
+---
+title: DROP VIEW
+summary: DROP VIEW
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP VIEW
+
+## Function
+
+**DROP VIEW** forcibly deletes a view from the database.
+
+## Precautions
+
+Only the view owner or a user granted with the DROP permission can run the **DROP VIEW** command. The system administrator has this permission by default.
+
+## Syntax
+
+```ebnf+diagram
+DropView ::= DROP VIEW [ IF EXISTS ] view_name [, ...] [ CASCADE | RESTRICT ];
+```
+
+## Parameter Description
+
+- **IF EXISTS**
+
+  Reports a notice instead of an error if the specified view does not exist.
+
+- **view_name**
+
+  Specifies the name of the view to be deleted.
+
+  Value range: an existing view name
+
+- **CASCADE | RESTRICT**
+
+  - **CASCADE**: automatically deletes the objects (such as other views) that depend on the view.
+  - **RESTRICT**: refuses to delete the view if any objects depend on it. This is the default action.
+
+## Examples
+
+See **Examples** in **CREATE VIEW**.
+
+## Helpful Links
+
+[ALTER VIEW](31-ALTER-VIEW) and [CREATE VIEW](70-CREATE-VIEW)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/103.1-DROP-WEAK-PASSWORD-DICTIONARY.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/103.1-DROP-WEAK-PASSWORD-DICTIONARY.md
new file mode 100644
index 0000000000000000000000000000000000000000..6782602de2526ef2e04ac3cada6266b9fffcd992
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/103.1-DROP-WEAK-PASSWORD-DICTIONARY.md
@@ -0,0 +1,34 @@
+---
+title: DROP WEAK PASSWORD DICTIONARY
+summary: DROP WEAK PASSWORD DICTIONARY
+author: Zhang Cuiping
+date: 2021-11-01
+---
+
+# DROP WEAK PASSWORD DICTIONARY
+
+## Function
+
+**DROP WEAK PASSWORD DICTIONARY** clears all weak passwords in **gs_global_config**.
+
+## Precautions
+
+Only the initial user, system administrator, and security administrator have the permission to execute this syntax.
+
+## Syntax
+
+```ebnf+diagram
+DropWeakPasswordDictionary ::= DROP WEAK PASSWORD DICTIONARY;
+```
+
+## Parameter Description
+
+None
+
+## Examples
+
+See the examples in **CREATE WEAK PASSWORD DICTIONARY**.
+
+## Helpful Links
+
+[CREATE WEAK PASSWORD DICTIONARY](70.1-CREATE-WEAK-PASSWORD-DICTIONARY)
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/104-EXECUTE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/104-EXECUTE.md
new file mode 100644
index 0000000000000000000000000000000000000000..365049edd04fc1e354dd8e7501ebc2cd27d85e31
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/104-EXECUTE.md
@@ -0,0 +1,59 @@
+---
+title: EXECUTE
+summary: EXECUTE
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# EXECUTE
+
+## Function
+
+**EXECUTE** executes a prepared statement. Because a prepared statement exists only in the lifetime of the session, the prepared statement must be created earlier in the current session by using the **PREPARE** statement.
+
+## Precautions
+
+If the **PREPARE** statement creating the prepared statement declares some parameters, the parameter set passed to the **EXECUTE** statement must be compatible. Otherwise, an error will occur.
+
+## Syntax
+
+```ebnf+diagram
+Execute ::= EXECUTE name [ ( parameter [, ...] ) ];
+```
+
+## Parameter Description
+
+- **name**
+
+  Specifies the name of the prepared statement to be executed.
+
+- **parameter**
+
+  Specifies a parameter of the prepared statement. It must be of the same data type as that specified parameter in creating and generating the prepared statement.
+
+## Examples
+
+```sql
+-- Create the reason table.
+mogdb=# CREATE TABLE tpcds.reason (
+    CD_DEMO_SK          INTEGER          NOT NULL,
+    CD_GENDER           character(16)            ,
+    CD_MARITAL_STATUS   character(100)
+)
+;
+
+-- Insert data.
+mogdb=# INSERT INTO tpcds.reason VALUES(51, 'AAAAAAAADDAAAAAA', 'reason 51');
+
+-- Create the reason_t1 table.
+mogdb=# CREATE TABLE tpcds.reason_t1 AS TABLE tpcds.reason;
+
+-- Create a prepared statement for an INSERT statement and execute the prepared statement.
+mogdb=# PREPARE insert_reason(integer,character(16),character(100)) AS INSERT INTO tpcds.reason_t1 VALUES($1,$2,$3);
+
+mogdb=# EXECUTE insert_reason(52, 'AAAAAAAADDAAAAAA', 'reason 52');
+
+-- Delete the reason and reason_t1 tables.
+mogdb=# DROP TABLE tpcds.reason;
+mogdb=# DROP TABLE tpcds.reason_t1;
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/104.1-EXECUTE-DIRECT.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/104.1-EXECUTE-DIRECT.md
new file mode 100644
index 0000000000000000000000000000000000000000..961cf319478a4030f6101636d9baf2ab8193b091
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/104.1-EXECUTE-DIRECT.md
@@ -0,0 +1,83 @@
+---
+title: EXECUTE DIRECT
+summary: EXECUTE DIRECT
+author: Zhang Cuiping
+date: 2021-11-01
+---
+
+# EXECUTE DIRECT
+
+## Function
+
+**EXECUTE DIRECT** executes an SQL statement on a specified node. Generally, the cluster automatically allocates an SQL statement to proper nodes. **EXECUTE DIRECT** is mainly used for database maintenance and testing.
+
+## Precautions
+
+- When **enable_nonsysadmin_execute_direct** is set to **off**, only the system administrator and monitoring administrator can execute **EXECUTE DIRECT**.
+- To ensure data consistency across nodes, only the **SELECT** statement can be used. Transaction statements, DDL, and DML cannot be used.
+- When the stddev aggregation calculation is performed on a specified DN using such statements, the result set is returned in triplet. For example, {3, 8, 30} indicates that the count result is 3, the sum result is 8, and the sum of squares is 30. When the AVG aggregation calculation is performed on a specified DN using such statements, the result set is returned in a binary tuple. For example, {4,2} indicates that the sum result is 4 and the count result is 2. Note: When data is stored in columns, the result of calling the AVG function is not defined. Use the **stddev_samp** function.
+- When multiple nodes are specified, aggregate functions are not supported. If the query contains an aggregate function, the message "EXECUTE DIRECT on multinode not support agg functions." is returned.
+- CNs do not store user table data. Therefore, do not execute **SELECT** for querying user tables on a CN.
+- If the SQL statement to be executed is also **EXECUTE DIRECT**, do not nest it into **EXECUTE DIRECT**; instead, directly execute the inner **EXECUTE DIRECT**.
+- The query result of the aggregate function is inconsistent with that on the CN. Multiple pieces of information are returned. The **array_avg** function is not supported.
+
+## Syntax
+
+```ebnf+diagram
+ExecuteDirect ::= EXECUTE DIRECT ON ( nodename [, ... ] ) query ;
+EXECUTE DIRECT ON { COORDINATORS | DATANODES | ALL } query;
+```
+
+## Parameter Description
+
+- nodename
+
+  Specifies the node name.
+
+  Value range: an existing node name
+
+- query
+
+  Specifies the SQL statement to be executed.
+
+- COORDINATORS
+
+  Runs the query statement on all CNs.
+
+- DATANODES
+
+  Runs the query statement on all DNs.
+
+- ALL
+
+  Runs the query statement on all CNs and DNs.
+
+## Examples
+
+```sql
+-- Query the node distribution status of the current database instance.
+mogdb=# SELECT * FROM pgxc_node;
+ node_name   | node_type | node_port |   node_host    | node_port1 |   node_host1   | hostis_primary | nodeis_primary | nodeis_preferred |   node_id   | sctp_port | control_port | sctp_port1 | control_port1 
+--------------+-----------+-----------+----------------+------------+----------------+----------------+----------------+------------------+-------------+-----------+--------------+------------+---------------
+ cn_5001      | C         |      8050 | 10.180.155.74  |       8050 | 10.180.155.74  | t              | f              | f                |  1120683504 |         0 |            0 |          0 |             0
+ cn_5003      | C         |      8050 | 10.180.157.130 |       8050 | 10.180.157.130 | t              | f              | f                |  -125853378 |         0 |            0 |          0 |             0
+ dn_6001_6002 | D         |     40050 | 10.180.155.74  |      45050 | 10.146.187.231 | t              | f              | f                |  1644780306 |     40052 |        40052 |      45052 |         45052
+ dn_6003_6004 | D         |     40050 | 10.146.187.231 |      45050 | 10.180.157.130 | t              | f              | f                |  -966646068 |     40052 |        40052 |      45052 |         45052
+ dn_6005_6006 | D         |     40050 | 10.180.157.130 |      45050 | 10.180.155.74  | t              | f              | f                |   868850011 |     40052 |        40052 |      45052 |         45052
+ cn_5002      | C         |      8050 | localhost      |       8050 | localhost      | t              | f              | f                | -1736975100 |         0 |            0 |          0 |             0
+(6 rows)
+
+-- Query records in the tpcds.customer_address table on dn_6001_6002.
+mogdb=# EXECUTE DIRECT ON(dn_6001_6002) 'select count(*) from tpcds.customer_address';
+ count 
+-------
+ 16922
+(1 row)
+
+-- Query all records in the tpcds.customer_address table.
+mogdb=# SELECT count(*) FROM tpcds.customer_address;
+ count 
+-------
+ 50000
+(1 row)
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/105-EXPLAIN.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/105-EXPLAIN.md
new file mode 100644
index 0000000000000000000000000000000000000000..12c91c11d776fb647cca8d56742c0f57eade8a9a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/105-EXPLAIN.md
@@ -0,0 +1,262 @@
+---
+title: EXPLAIN
+summary: EXPLAIN
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# EXPLAIN
+
+## Function
+
+**EXPLAIN** shows the execution plan of an SQL statement.
+
+The execution plan shows how the tables referenced by the statement will be scanned - by plain sequential scan, index scan, etc. - and if multiple tables are referenced, what join algorithms will be used to bring together the required rows from each input table.
+
+The most critical part of the display is the estimated statement execution cost, which is the planner's guess at how long it will take to run the statement.
+
+The **ANALYZE** option causes the statement to be actually executed, not only planned. The total elapsed time expended within each plan node (in milliseconds) and total number of rows it actually returned are added to the display. This is useful for seeing whether the planner's estimates are close to reality.
+
+## Precautions
+
+- The statement is actually executed when the **ANALYZE** option is used. If you want to use **EXPLAIN** to analyze **INSERT**, **UPDATE**, **DELETE**, **CREATE TABLE AS**, or **EXECUTE** statement without letting the statement affect your data, use this approach:
+
+  ```
+  START TRANSACTION;
+  EXPLAIN ANALYZE ...;
+  ROLLBACK;
+  ```
+
+- The **DETAIL**, **NODES**, and **NUM_NODES** parameters are disabled in standalone mode. They are available only in distributed mode. If the parameters are used, the following error is reported:
+
+  ```
+  mogdb=# create table student(id int, name char(20));
+  CREATE TABLE
+  mogdb=# explain (nodes true) insert into student values(5,'a'),(6,'b');
+  ERROR:  unrecognized EXPLAIN option "nodes"
+  mogdb=# explain (num_nodes true) insert into student values(5,'a'),(6,'b');
+  ERROR:  unrecognized EXPLAIN option "num_nodes"
+  ```
+
+## Syntax
+
+- Display the execution plan of an SQL statement, which supports multiple options and has no requirements for the order of options.
+
+  ```ebnf+diagram
+  Explain ::= EXPLAIN [ (  option  [, ...] )  ] statement;
+  ```
+
+  The syntax of the **option** clause is as follows:
+
+  ```ebnf+diagram
+  option ::= ANALYZE [ boolean ] |
+      ANALYSE [ boolean ] |
+      VERBOSE [ boolean ] |
+      COSTS [ boolean ] |
+      CPU [ boolean ] |
+      DETAIL [ boolean ] |
+      NODES [ boolean ] |
+      NUM_NODES [ boolean ] |
+      BUFFERS [ boolean ] |
+      TIMING [ boolean ] |
+      PLAN [ boolean ] |
+      FORMAT { TEXT | XML | JSON | YAML }
+  ```
+
+- Display the execution plan of an SQL statement, where options are in order.
+
+  ```ebnf+diagram
+  Explain ::= EXPLAIN  { [  { ANALYZE  | ANALYSE  }  ] [ VERBOSE  ]  | PERFORMANCE  } statement;
+  ```
+
+## Parameter Description
+
+- **statement**
+
+  Specifies the SQL statement to explain.
+
+- **ANALYZE boolean | ANALYSE boolean**
+
+  Specifies whether to display actual run times and other statistics.
+
+  Value range:
+
+  - **TRUE** (default): displays them.
+  - **FALSE**: does not display them.
+
+- **VERBOSE boolean**
+
+  Specifies whether to display additional information regarding the plan.
+
+  Value range:
+
+  - **TRUE** (default): displays it.
+  - **FALSE**: does not display it.
+
+- **COSTS boolean**
+
+  Specifies whether to display the estimated total cost of each plan node, estimated number of rows, estimated width of each row.
+
+  Value range:
+
+  - **TRUE** (default): displays them.
+  - **FALSE**: does not display them.
+
+- **CPU boolean**
+
+  Specifies whether to display CPU usage.
+
+  Value range:
+
+  - **TRUE** (default): displays it.
+  - **FALSE**: does not display it.
+
+- **DETAIL boolean** unavailable)
+
+  Displays information about database nodes.
+
+  Value range:
+
+  - **TRUE** (default): displays it.
+  - **FALSE**: does not display it.
+
+- **NODES boolean** (unavailable)
+
+  Specifies whether to display information about the nodes executed by query.
+
+  Value range:
+
+  - **TRUE** (default): displays it.
+  - **FALSE**: does not display it.
+
+- **NUM_NODES boolean** (unavailable)
+
+  Specifies whether to display the number of executing nodes.
+
+  Value range:
+
+  - **TRUE** (default): displays it.
+  - **FALSE**: does not display it.
+
+- **BUFFERS boolean**
+
+  Specifies whether to display buffer usage.
+
+  Value range:
+
+  - **TRUE** (default): displays it.
+  - **FALSE**: does not display it.
+
+- **TIMING boolean**
+
+  Specifies whether to display the actual startup time and time spent on the output node.
+
+  Value range:
+
+  - **TRUE** (default): displays them.
+  - **FALSE**: does not display them.
+
+- **PLAN**
+
+  Specifies whether to store the execution plan in **PLAN_TABLE**. If this parameter is set to **on**, the execution plan is stored in **PLAN_TABLE** and not displayed on the screen. Therefore, this parameter cannot be used together with other parameters when it is set to **on**.
+
+  Value range:
+
+  - **ON** (default): The execution plan is stored in **PLAN_TABLE** and not printed on the screen. If the plan is stored successfully, "EXPLAIN SUCCESS" is returned.
+  - **OFF**: The execution plan is not stored in **PLAN_TABLE** but is printed on the screen.
+
+- **FORMAT**
+
+  Specifies the output format.
+
+  Value range: **TEXT**, **XML**, **JSON**, and **YAML**
+
+  Default value: **TEXT**
+
+- **PERFORMANCE**
+
+  Prints all relevant information in execution.
+
+## Examples
+
+```
+-- Create the tpcds.customer_address_p1 table.
+mogdb=# CREATE TABLE tpcds.customer_address_p1 AS TABLE tpcds.customer_address;
+
+-- Change the value of explain_perf_mode to normal.
+mogdb=# SET explain_perf_mode=normal;
+
+-- Display an execution plan for simple queries in the table.
+mogdb=# EXPLAIN SELECT * FROM tpcds.customer_address_p1;
+QUERY PLAN
+--------------------------------------------------
+Data Node Scan  (cost=0.00..0.00 rows=0 width=0)
+Node/s: All dbnodes
+(2 rows)
+
+-- Generate an execution plan in JSON format (with explain_perf_mode being normal).
+mogdb=# EXPLAIN(FORMAT JSON) SELECT * FROM tpcds.customer_address_p1;
+              QUERY PLAN
+--------------------------------------
+ [                                   +
+   {                                 +
+     "Plan": {                       +
+       "Node Type": "Data Node Scan",+
+       "Startup Cost": 0.00,         +
+       "Total Cost": 0.00,           +
+       "Plan Rows": 0,               +
+       "Plan Width": 0,              +
+       "Node/s": "All dbnodes"     +
+     }                               +
+   }                                 +
+ ]
+(1 row)
+
+-- If there is an index and we use a query with an indexable WHERE condition, EXPLAIN might show a different plan.
+mogdb=# EXPLAIN SELECT * FROM tpcds.customer_address_p1 WHERE ca_address_sk=10000;
+QUERY PLAN
+--------------------------------------------------
+Data Node Scan  (cost=0.00..0.00 rows=0 width=0)
+Node/s: dn_6005_6006
+(2 rows)
+
+-- Generate an execution plan in YAML format (with explain_perf_mode being normal).
+mogdb=# EXPLAIN(FORMAT YAML) SELECT * FROM tpcds.customer_address_p1 WHERE ca_address_sk=10000;
+           QUERY PLAN
+---------------------------------
+ - Plan:                        +
+     Node Type: "Data Node Scan"+
+     Startup Cost: 0.00         +
+     Total Cost: 0.00           +
+     Plan Rows: 0               +
+     Plan Width: 0              +
+     Node/s: "dn_6005_6006"
+(1 row)
+
+-- Here is an example of a query plan with cost estimates suppressed:
+mogdb=# EXPLAIN(COSTS FALSE)SELECT * FROM tpcds.customer_address_p1 WHERE ca_address_sk=10000;
+       QUERY PLAN
+------------------------
+ Data Node Scan
+   Node/s: dn_6005_6006
+(2 rows)
+
+-- Here is an example of a query plan for a query using an aggregate function:
+mogdb=# EXPLAIN SELECT SUM(ca_address_sk) FROM tpcds.customer_address_p1 WHERE ca_address_sk<10000;
+                                      QUERY PLAN
+---------------------------------------------------------------------------------------
+ Aggregate  (cost=18.19..14.32 rows=1 width=4)
+   ->  Streaming (type: GATHER)  (cost=18.19..14.32 rows=3 width=4)
+         Node/s: All dbnodes
+         ->  Aggregate  (cost=14.19..14.20 rows=3 width=4)
+               ->  Seq Scan on customer_address_p1  (cost=0.00..14.18 rows=10 width=4)
+                     Filter: (ca_address_sk < 10000)
+(6 rows)
+
+-- Delete the tpcds.customer_address_p1 table.
+mogdb=# DROP TABLE tpcds.customer_address_p1;
+```
+
+## Helpful Links
+
+[ANALYZE | ANALYSE](32-ANALYZE-ANALYSE)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/106-EXPLAIN-PLAN.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/106-EXPLAIN-PLAN.md
new file mode 100644
index 0000000000000000000000000000000000000000..a4fdd418782dd2f32ad624181ce98f3a81201bf7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/106-EXPLAIN-PLAN.md
@@ -0,0 +1,86 @@
+---
+title: EXPLAIN PLAN
+summary: EXPLAIN PLAN
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# EXPLAIN PLAN
+
+## Function
+
+**EXPLAIN PLAN** saves information about an execution plan into the **PLAN_TABLE** table. Different from the **EXPLAIN** statement, **EXPLAIN PLAN** only saves plan information and does not print information on the screen.
+
+## Syntax
+
+```ebnf+diagram
+ExplainPlan ::= EXPLAIN PLAN
+[ SET STATEMENT_ID = string ]
+FOR statement ;
+```
+
+## Parameter Description
+
+- **PLAN**: saves plan information into **PLAN_TABLE**. If information is stored successfully, "EXPLAIN SUCCESS" is returned.
+
+- **STATEMENT_ID**: tags each query. The tag information will be stored in **PLAN_TABLE**.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  > If the **EXPLAIN PLAN** statement does not contain **SET STATEMENT_ID**, **STATEMENT_ID** is empty by default. In addition, the value of **STATEMENT_ID** cannot exceed 30 bytes. Otherwise, an error will be reported.
+
+## Precautions
+
+- **EXPLAIN PLAN** cannot be executed on a database node.
+
+- Plan information cannot be collected for SQL statements that failed to be executed.
+
+- Data in **PLAN_TABLE** is in a session-level lifecycle. Sessions are isolated from users, and therefore users can only view the data of the current session and current user.
+
+## Example 1
+
+You can perform the following steps to collect execution plans of SQL statements by running **EXPLAIN PLAN**:
+
+1. Run the **EXPLAIN PLAN** statement.
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+   > After the **EXPLAIN PLAN** statement is executed, plan information is automatically stored in **PLAN_TABLE**. **INSERT**, **UPDATE**, and **ANALYZE** cannot be performed on **PLAN_TABLE**.
+   > For details about **PLAN_TABLE**, see **PLAN_TABLE**.
+
+   ```sql
+   explain plan set statement_id='TPCH-Q4' for
+   select
+   o_orderpriority,
+   count(*) as order_count
+   from
+   orders
+   where
+   o_orderdate >= '1993-07-01'::date
+   and o_orderdate < '1993-07-01'::date + interval '3 month'
+   and exists (
+   select
+   *
+   from
+   lineitem
+   where
+   l_orderkey = o_orderkey
+   and l_commitdate < l_receiptdate
+   )
+   group by
+   o_orderpriority
+   order by
+   o_orderpriority;
+   ```
+
+2. Query **PLAN_TABLE**.
+
+   ```sql
+   SELECT * FROM PLAN_TABLE;
+   ```
+
+   ![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/reference-guide/EXPLAIN-PLAN.png)
+
+3. Delete data from **PLAN_TABLE**.
+
+   ```sql
+   DELETE FROM PLAN_TABLE WHERE xxx;
+   ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/107-FETCH.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/107-FETCH.md
new file mode 100644
index 0000000000000000000000000000000000000000..651699c0902bc3410cbf780c824bcf1b1e2c9037
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/107-FETCH.md
@@ -0,0 +1,218 @@
+---
+title: FETCH
+summary: FETCH
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# FETCH
+
+## Function
+
+**FETCH** retrieves rows using a previously created cursor.
+
+A cursor has an associated position, which is used by **FETCH**. The cursor position can be before the first row of the query result, on any particular row of the result, or after the last row of the result.
+
+- When created, a cursor is positioned before the first row.
+- After fetching some rows, the cursor is positioned on the row most recently retrieved.
+- If **FETCH** runs off the end of the available rows then the cursor is left positioned after the last row, or before the first row if fetching backward.
+- **FETCH ALL** or **FETCH BACKWARD ALL** will always leave the cursor positioned after the last row or before the first row.
+
+## Precautions
+
+- If the cursor is declared with **NO SCROLL**, backward fetches like **FETCH BACKWARD** are not allowed.
+- The forms **NEXT**, **PRIOR**, **FIRST**, **LAST**, **ABSOLUTE**, and **RELATIVE** fetch a single row after moving the cursor appropriately. If there is no such row, an empty result is returned, and the cursor is left positioned before the first row (backward fetch) or after the last row (forward fetch) as appropriate.
+- The forms using **FORWARD** and **BACKWARD** retrieve the indicated number of rows moving in the forward or backward direction, leaving the cursor positioned on the last-returned row or after (backward fetch)/before (forward fetch) all rows if the **count** exceeds the number of rows available.
+- **RELATIVE 0**, **FORWARD 0**, and **BACKWARD 0** all request fetching the current row without moving the cursor, that is, re-fetching the most recently fetched row. This will succeed unless the cursor is positioned before the first row or after the last row; in which case, no row is returned.
+- If the cursor of **FETCH** involves a column-store table, backward fetches like **BACKWARD** and **PRIOR** are not allowed.
+
+## Syntax
+
+```ebnf+diagram
+Fetch ::= FETCH [ direction { FROM | IN } ] cursor_name;
+```
+
+The **direction** clause specifies optional parameters.
+
+```ebnf+diagram
+direction ::= NEXT
+   | PRIOR
+   | FIRST
+   | LAST
+   | ABSOLUTE count
+   | RELATIVE count
+   | count
+   | ALL
+   | FORWARD
+   | FORWARD count
+   | FORWARD ALL
+   | BACKWARD
+   | BACKWARD count
+   | BACKWARD ALL
+```
+
+## Parameter Description
+
+- **direction_clause**
+
+  Defines the fetch direction.
+
+  Value range:
+
+  - **NEXT** (default value)
+
+    Fetches the next row.
+
+  - PRIOR
+
+    Fetches the prior row.
+
+  - FIRST
+
+    Fetches the first row of the query (same as **ABSOLUTE 1**).
+
+  - LAST
+
+    Fetches the last row of the query (same as **ABSOLUTE -1**).
+
+  - ABSOLUTE count
+
+    Fetches the *count*'th row of the query.
+
+    **ABSOLUTE** fetches are not any faster than navigating to the desired row with a relative move: the underlying implementation must traverse all the intermediate rows anyway.
+
+    Value range: a possibly-signed integer
+
+    - If *count* is positive, the *count*'th row of the query will be fetched.
+    - If *count* is negative, the **abs(count)**th row from the end of the query result will be fetched.
+    - If *count* is set to **0**, the cursor is positioned before the first row.
+
+  - RELATIVE count
+
+    Fetches the *count*'th succeeding row or the *count*'th prior row if count is negative.
+
+    Value range: a possibly-signed integer
+
+    - If *count* is positive, the _count_th succeeding row will be fetched.
+    - If **count** is a negative integer, fetches the abs(count)'th prior row.
+    - If the current row contains no data, **RELATIVE 0** returns null.
+
+  - count
+
+    Fetches the next *count* rows (same as **FORWARD** *count*).
+
+  - ALL
+
+    Fetches all remaining rows (same as **FORWARD ALL**).
+
+  - FORWARD
+
+    Fetches the next row (same as **NEXT**).
+
+  - FORWARD count
+
+    Fetches the *count* succeeding rows or *count* prior rows if *count* is negative.
+
+  - FORWARD ALL
+
+    Fetches all remaining rows.
+
+  - BACKWARD
+
+    Fetches the prior row (same as **PRIOR**).
+
+  - BACKWARD count
+
+    Fetches the prior *count* rows (scanning backwards).
+
+    Value range: a possibly-signed integer
+
+    - If *count* is positive, the prior *count* rows will be fetched.
+    - If *count* is a negative, the succeeding *abs (count)* rows will be fetched.
+    - **BACKWARD 0** re-fetches the current row, if any.
+
+  - BACKWARD ALL
+
+    Fetches all prior rows (scanning backwards).
+
+- **{ FROM | IN } cursor_name**
+
+  Specifies the cursor name using the keyword **FROM** or **IN**.
+
+  Value range: an existing cursor name
+
+## Examples
+
+```sql
+-- (For the SELECT statement, traverse a table using a cursor.) Start a transaction.
+mogdb=# START TRANSACTION;
+
+-- Set up cursor1.
+mogdb=# CURSOR cursor1 FOR SELECT * FROM tpcds.customer_address ORDER BY 1;
+
+-- Fetch the first three rows in cursor1.
+mogdb=# FETCH FORWARD 3 FROM cursor1;
+ ca_address_sk |  ca_address_id   | ca_street_number |   ca_street_name   | ca_street_type  | ca_suite_number |     ca_city     |    ca_county    | ca_state |   ca_zip   |  ca_country   | ca_gmt_offset |   ca_location_type
+---------------+------------------+------------------+--------------------+-----------------+-----------------+-----------------+-----------------+----------+------------+---------------+---------------+----------------------
+             1 | AAAAAAAABAAAAAAA | 18               | Jackson            | Parkway         | Suite 280       | Fairfield       | Maricopa County | AZ       | 86192      | United States |         -7.00 | condo
+             2 | AAAAAAAACAAAAAAA | 362              | Washington 6th     | RD              | Suite 80        | Fairview        | Taos County     | NM       | 85709      | United States |         -7.00 | condo
+             3 | AAAAAAAADAAAAAAA | 585              | Dogwood Washington | Circle          | Suite Q         | Pleasant Valley | York County     | PA       | 12477      | United States |         -5.00 | single family
+(3 rows)
+
+-- Close the cursor and commit the transaction.
+mogdb=# CLOSE cursor1;
+
+-- End the transaction.
+mogdb=# END;
+
+-- (For the VALUES clause, traverse the clause using a cursor.) Start a transaction.
+mogdb=# START TRANSACTION;
+
+-- Set up cursor2.
+mogdb=# CURSOR cursor2 FOR VALUES(1,2),(0,3) ORDER BY 1;
+
+-- Fetch the first two rows in cursor2.
+mogdb=# FETCH FORWARD 2 FROM cursor2;
+column1 | column2
+---------+---------
+0 |       3
+1 |       2
+(2 rows)
+
+-- Close the cursor and commit the transaction.
+mogdb=# CLOSE cursor2;
+
+-- End the transaction.
+mogdb=# END;
+
+-- (WITH HOLD cursor) Start a transaction.
+mogdb=# START TRANSACTION;
+
+-- Set up a WITH HOLD cursor.
+mogdb=# DECLARE cursor1 CURSOR WITH HOLD FOR SELECT * FROM tpcds.customer_address ORDER BY 1;
+
+-- Fetch the first two rows in cursor1.
+mogdb=# FETCH FORWARD 2 FROM cursor1;
+ ca_address_sk |  ca_address_id   | ca_street_number |   ca_street_name   | ca_street_type  | ca_suite_number |     ca_city     |    ca_county    | ca_state |   ca_zip   |  ca_country   | ca_gmt_offset |   ca_location_type
+---------------+------------------+------------------+--------------------+-----------------+-----------------+-----------------+-----------------+----------+------------+---------------+---------------+----------------------
+             1 | AAAAAAAABAAAAAAA | 18               | Jackson            | Parkway         | Suite 280       | Fairfield       | Maricopa County | AZ       | 86192      | United States |         -7.00 | condo
+             2 | AAAAAAAACAAAAAAA | 362              | Washington 6th     | RD              | Suite 80        | Fairview        | Taos County     | NM       | 85709      | United States |         -7.00 | condo
+(2 rows)
+
+-- End the transaction.
+mogdb=# END;
+
+-- Fetch the next row in cursor1.
+mogdb=# FETCH FORWARD 1 FROM cursor1;
+ ca_address_sk |  ca_address_id   | ca_street_number |   ca_street_name   | ca_street_type  | ca_suite_number |     ca_city     |    ca_county    | ca_state |   ca_zip   |  ca_country   | ca_gmt_offset |   ca_location_type
+---------------+------------------+------------------+--------------------+-----------------+-----------------+-----------------+-----------------+----------+------------+---------------+---------------+----------------------
+             3 | AAAAAAAADAAAAAAA | 585              | Dogwood Washington | Circle          | Suite Q         | Pleasant Valley | York County     | PA       | 12477      | United States |         -5.00 | single family
+(1 row)
+
+-- Close the cursor.
+mogdb=# CLOSE cursor1;
+```
+
+## Helpful Links
+
+[CLOSE](36-CLOSE) and [MOVE](111-MOVE)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/108-GRANT.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/108-GRANT.md
new file mode 100644
index 0000000000000000000000000000000000000000..eb17bce0619ca54e4ed9b592919d11d61b340de9
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/108-GRANT.md
@@ -0,0 +1,572 @@
+---
+title: GRANT
+summary: GRANT
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# GRANT
+
+## Function
+
+**GRANT** is used to grant permissions to roles and users.
+
+**GRANT** is used in the following scenarios:
+
+- **Granting system permissions to roles or users**
+
+  System permissions are also called user properties, including **SYSADMIN**, **CREATEDB**, **CREATEROLE**, **AUDITADMIN**, **MONADMIN**, **OPRADMIN**, **POLADMIN**, and **LOGIN**.
+
+  They can be specified only by the **CREATE ROLE** or **ALTER ROLE** statement. The **SYSADMIN** permissions can be granted and revoked using **GRANT ALL PRIVILEGE** and **REVOKE ALL PRIVILEGE**, respectively. System permissions cannot be inherited by a user from a role, and cannot be granted using **PUBLIC**.
+
+- **Granting database object permissions to roles or users**
+
+  Grant permissions related to database objects (tables, views, specified columns, databases, functions, schemas, and tablespaces) to specified roles or users.
+
+  **GRANT** gives specific permissions on a database object to one or more roles. These permissions are added to those already granted, if any.
+
+  The keyword **PUBLIC** indicates that the permissions are to be granted to all roles, including those that might be created later. **PUBLIC** can be thought of as an implicitly defined group that always includes all roles. Any particular role will have the sum of permissions granted directly to it, permissions granted to any role it is presently a member of, and permissions granted to **PUBLIC**.
+
+  If **WITH GRANT OPTION** is specified, the recipient of the permission can in turn grant it to others. Without a grant option, the recipient cannot do that. **GRANT** options cannot be granted to **PUBLIC**. Only MogDB supports this operation.
+
+  MogDB grants the permissions for objects of certain types to **PUBLIC**. By default, permissions on tables, columns, sequences, foreign data sources, foreign servers, schemas, and tablespaces are not granted to **PUBLIC**, but the following permissions are granted to **PUBLIC**: **CONNECT** and **CREATE TEMP TABLE** permissions on databases, **EXECUTE** permission on functions, and **USAGE** permission on languages and data types (including domains). An object owner can revoke the default permissions granted to **PUBLIC** and grant permissions to other users as needed. For security purposes, you are advised to create an object and set its permissions in the same transaction so that other users do not have time windows to use the object. In addition, you can run the **ALTER DEFAULT PRIVILEGES** statement to modify the default permissions.
+
+  By default, an object owner has all permissions on the object. For security purposes, the owner can discard some permissions. However, the ALTER, DROP, COMMENT, INDEX, VACUUM, and re-grantable permissions of the object are inherent permissions implicitly owned by the owner.
+
+- **Granting a role's or user's permissions to other roles or users**
+
+  Grant a role's or user's permissions to one or more roles or users. In this case, every role or user can be regarded as a set of one or more database permissions.
+
+  If **WITH ADMIN OPTION** is specified, the recipients can in turn grant the permissions to other roles or users or revoke the permissions they have granted to other roles or users. If recipients' permissions are changed or revoked later, the grantees' permissions will also change.
+
+  Database administrators can grant or revoke permissions for any roles or users. Roles with the **CREATEROLE** permission can grant or revoke permissions for non-admin roles.
+
+## Precautions
+
+None
+
+## Syntax
+
+- Grant the table access permission to a specified user or role.
+
+  ```ebnf+diagram
+  Grant ::= GRANT { { SELECT | INSERT | UPDATE | DELETE | TRUNCATE | REFERENCES | ALTER | DROP | COMMENT | INDEX | VACUUM } [, ...]
+        | ALL [ PRIVILEGES ] }
+      ON { [ TABLE ] table_name [, ...]
+         | ALL TABLES IN SCHEMA schema_name [, ...] }
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ];
+  ```
+
+- Grant the column access permission to a specified user or role.
+
+  ```ebnf+diagram
+  Grant ::= GRANT { {{ SELECT | INSERT | UPDATE | REFERENCES | COMMENT } ( column_name [, ...] )} [, ...]
+        | ALL [ PRIVILEGES ] ( column_name [, ...] ) }
+      ON [ TABLE ] table_name [, ...]
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ];
+  ```
+
+- Grant the sequence access permission to a specified user or role.
+
+  ```ebnf+diagram
+  Grant ::= GRANT { { SELECT | UPDATE | USAGE | ALTER | DROP | COMMENT } [, ...]
+        | ALL [ PRIVILEGES ] }
+      ON { [ [ LARGE ] SEQUENCE ] sequence_name [, ...]
+         | ALL SEQUENCES IN SCHEMA schema_name [, ...] }
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ];
+  ```
+
+- Grant the database access permission to a specified user or role.
+
+  ```ebnf+diagram
+  Grant ::= GRANT { { CREATE | CONNECT | TEMPORARY | TEMP | ALTER | DROP | COMMENT } [, ...]
+        | ALL [ PRIVILEGES ] }
+      ON DATABASE database_name [, ...]
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ];
+  ```
+
+- Grant the domain access permission to a specified user or role.
+
+  ```ebnf+diagram
+  Grant ::= GRANT { USAGE | ALL [ PRIVILEGES ] }
+      ON DOMAIN domain_name [, ...]
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ];
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** In the current version, the domain access permission cannot be granted.
+
+- Grant the client master key (CMK) access permission to a specified user or role.
+
+  ```ebnf+diagram
+  Grant ::= GRANT { { USAGE | DROP } [, ...] | ALL [ PRIVILEGES ] }
+      ON CLIENT_MASTER_KEY client_master_key [, ...]
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ];
+  ```
+
+- Grant the column encryption key (CEK) access permission to a specified user or role.
+
+  ```ebnf+diagram
+  Grant ::= GRANT { { USAGE | DROP } [, ...] | ALL [ PRIVILEGES ] }
+      ON COLUMN_ENCRYPTION_KEY column_encryption_key [, ...]
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ];
+  ```
+
+- Grant the external data source access permission to a specified user or role.
+
+  ```ebnf+diagram
+  Grant ::= GRANT { USAGE | ALL [ PRIVILEGES ] }
+      ON FOREIGN DATA WRAPPER fdw_name [, ...]
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ];
+  ```
+
+- Grant the external server access permission to a specified user or role.
+
+  ```ebnf+diagram
+  Grant ::= GRANT { { USAGE | ALTER | DROP | COMMENT } [, ...] | ALL [ PRIVILEGES ] }
+      ON FOREIGN SERVER server_name [, ...]
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ];
+  ```
+
+- Grant the function access permission to a specified user or role.
+
+  ```ebnf+diagram
+  Grant ::= GRANT { { EXECUTE | ALTER | DROP | COMMENT } [, ...] | ALL [ PRIVILEGES ] }
+      ON { FUNCTION {function_name ( [ {[ argmode ] [ arg_name ] arg_type} [, ...] ] )} [, ...]
+         | ALL FUNCTIONS IN SCHEMA schema_name [, ...] }
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ];
+  ```
+
+- Grant the procedural language access permission to a specified user or role.
+
+  ```ebnf+diagram
+  Grant ::= GRANT { USAGE | ALL [ PRIVILEGES ] }
+      ON LANGUAGE lang_name [, ...]
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ];
+  ```
+
+- Grant the large object access permission to a specified user or role.
+
+  ```ebnf+diagram
+  Grant ::= GRANT { { SELECT | UPDATE } [, ...] | ALL [ PRIVILEGES ] }
+      ON LARGE OBJECT loid [, ...]
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ];
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** In the current version, the large object access permission cannot be granted.
+
+- Grant the schema access permission to a specified user or role.
+
+  ```ebnf+diagram
+  Grant ::= GRANT { { CREATE | USAGE | ALTER | DROP | COMMENT } [, ...] | ALL [ PRIVILEGES ] }
+      ON SCHEMA schema_name [, ...]
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ];
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** When granting table or view permissions to other users, you also need to grant the **USAGE** permission on the containing schema. Without the **USAGE** permission, the recipients can only see the object names, but cannot access them. This syntax cannot be used to grant the permission to create tables in schemas with the same name, but you can use the syntax for granting permission of a role to another user or role to achieve the same effect.
+
+- Grant the tablespace access permission to a specified user or role.
+
+  ```ebnf+diagram
+  Grant ::= GRANT { { CREATE | ALTER | DROP | COMMENT } [, ...] | ALL [ PRIVILEGES ] }
+      ON TABLESPACE tablespace_name [, ...]
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ];
+  ```
+
+- Grant the type access permission to a specified user or role.
+
+  ```ebnf+diagram
+  Grant ::= GRANT { { USAGE | ALTER | DROP | COMMENT } [, ...] | ALL [ PRIVILEGES ] }
+      ON TYPE type_name [, ...]
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ];
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** In the current version, the type access permission cannot be granted.
+
+- Grant the data source permission to a role.
+
+  ```ebnf+diagram
+  Grant ::= GRANT { USAGE | ALL [PRIVILEGES]}
+     ON DATA SOURCE src_name [, ...]
+     TO { [GROUP] role_name | PUBLIC } [, ...]
+     [WITH GRANT OPTION];
+  ```
+
+- Grant the directory permission to a role.
+
+  ```ebnf+diagram
+  Grant ::= GRANT { { READ | WRITE | ALTER | DROP } [, ...] | ALL [PRIVILEGES] }
+     ON DIRECTORY directory_name [, ...]
+     TO { [GROUP] role_name | PUBLIC } [, ...]
+     [WITH GRANT OPTION];
+  ```
+
+- Grant the package permission to a role.
+
+  ```ebnf+diagram
+  Grant ::= GRANT { { EXECUTE | ALTER | DROP | COMMENT } [, ...] | ALL [PRIVILEGES] }
+     ON PACKAGE package_name [, ...]
+     TO { [GROUP] role_name | PUBLIC } [, ...]
+     [WITH GRANT OPTION];
+  ```
+
+- Grant a role's permissions to another user or role.
+
+  ```ebnf+diagram
+  Grant ::= GRANT role_name [, ...]
+     TO role_name [, ...]
+     [ WITH ADMIN OPTION ];
+  ```
+
+- Grant the **sysadmin** permission to a role.
+
+  ```ebnf+diagram
+  Grant ::= GRANT ALL { PRIVILEGES | PRIVILEGE }
+     TO role_name;
+  ```
+
+## Parameter Description
+
+The possible permissions are:
+
+- **SELECT**
+
+  Allows **SELECT** from any column, or the specific columns listed, of the specified table, view, or sequence. The **SELECT** permission on the corresponding field is also required for **UPDATE** or DELETE.
+
+- **INSERT**
+
+  Allows **INSERT** of a new row into a table.
+
+- **UPDATE**
+
+  Allows **UPDATE** of any column of a table. Generally, **UPDATE** also requires the SELECT permission to query which rows need to be updated. **SELECT … FOR UPDATE** and **SELECT … FOR SHARE** also require this permission on at least one column, in addition to the **SELECT** permission.
+
+- **DELETE**
+
+  Allows **DELETE** of a row from a table. Generally, **DELETE** also requires the SELECT permission to query which rows need to be deleted.
+
+- **TRUNCATE**
+
+  Allows **TRUNCATE** on a table.
+
+- **REFERENCES**
+
+  Allows creation of a foreign key constraint referencing a table. This permission is required on both referencing and referenced tables.
+
+- **CREATE**
+
+  - For databases, allows new schemas to be created within the database.
+  - For schemas, allows new objects to be created within the schema. To rename an existing object, you must own the object and have the **CREATE** permission on the schema of the object.
+  - For tablespaces, allows tables to be created within the tablespace, and allows databases and schemas to be created that have the tablespace as their default tablespace.
+
+- **CONNECT**
+
+  Allows the grantee to connect to the database.
+
+- **EXECUTE**
+
+  Allows calling a function, including use of any operators that are implemented on top of the function.
+
+- **USAGE**
+
+  - For procedural languages, allows use of the language for the creation of functions in that language.
+  - For schemas, allows access to objects contained in the schema. Without this permission, it is still possible to see the object names.
+  - For sequences, allows use of the **nextval** function.
+  - For data sources, specifies access permissions or is used as **ALL PRIVILEGES**.
+
+- **ALTER**
+
+  Allows users to modify properties of a specified object, excluding the owner and schema of the object.
+
+- **DROP**
+
+  Allows users to delete specified objects.
+
+- **COMMENT**
+
+  Allows users to define or modify comments of a specified object.
+
+- **INDEX**
+
+  Allows users to create indexes on specified tables, manage indexes on the tables, and perform REINDEX and CLUSTER operations on the tables.
+
+- **VACUUM**
+
+  Allows users to perform ANALYZE and VACUUM operations on specified tables.
+
+- **ALL PRIVILEGES**
+
+  Grants all available permissions to a user or role at a time. Only a system administrator has the **GRANT ALL PRIVILEGES** permission.
+
+**GRANT** parameters are as follows:
+
+- **role_name**
+
+  Specifies the username.
+
+- **table_name**
+
+  Specifies the table name.
+
+- **column_name**
+
+  Specifies the column name.
+
+- **schema_name**
+
+  Specifies the schema name.
+
+- **database_name**
+
+  Specifies the database name.
+
+- **function_name**
+
+  Specifies the function name.
+
+- **sequence_name**
+
+  Specifies the sequence name.
+
+- **domain_name**
+
+  Specifies the domain type name.
+
+- **fdw_name**
+
+  Specifies the foreign data wrapper name.
+
+- **lang_name**
+
+  Specifies the language name.
+
+- **type_name**
+
+  Specifies the type name.
+
+- **src_name**
+
+  Specifies the data source name.
+
+- **argmode**
+
+  Specifies the parameter mode.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **arg_name**
+
+  Parameter name.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **arg_type**
+
+  Parameter type.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **loid**
+
+  Specifies the identifier of the large object that includes this page.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **tablespace_name**
+
+  Specifies the tablespace name.
+
+- client_master_key
+
+  Name of the client master key.
+
+  Value range: a string. It must comply with the naming convention.
+
+- column_encryption_key
+
+  Name of the column encryption key.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **directory_name**
+
+  Specifies the name of the directory to be deleted.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **WITH GRANT OPTION**
+
+  If **WITH GRANT OPTION** is specified, the recipient of the permission can in turn grant it to others. Without a grant option, the recipient cannot do that. Grant options cannot be granted to **PUBLIC**.
+
+When a non-owner of an object attempts to GRANT permissions on the object:
+
+- The statement will fail outright if the user has no permissions whatsoever on the object.
+- As long as some permission is available, the statement will proceed, but it will grant only those permissions for which the user has grant options.
+- The **GRANT ALL PRIVILEGES** forms will issue a warning message if no grant options are held, while the other forms will issue a warning if grant options for any of the permissions specifically named in the statement are not held.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** Database administrators can access all objects, regardless of object permission settings. This is comparable to the permissions of **root** in a Unix system. As with **root**, it is unwise to operate as a system administrator except when necessary. **GRANT** to a table partition will cause alarms.
+
+## Examples
+
+**Example 1: Granting system permissions to a user or role**
+
+Create user **joe** and grant the sysadmin permissions to the user.
+
+```sql
+mogdb=# CREATE USER joe PASSWORD 'Bigdata@123';
+mogdb=# GRANT ALL PRIVILEGES TO joe;
+```
+
+Afterward, user **joe** has the sysadmin permissions.
+
+**Example 2: Granting object permissions to a user or role**
+
+1. Revoke the **sysadmin** permission from the **joe** user. Grant the usage permission of the **tpcds** schema and all permissions on the **tpcds.reason** table to **joe**.
+
+   ```sql
+   mogdb=# REVOKE ALL PRIVILEGES FROM joe;
+   mogdb=# GRANT USAGE ON SCHEMA tpcds TO joe;
+   mogdb=# GRANT ALL PRIVILEGES ON tpcds.reason TO joe;
+   ```
+
+   Then **joe** has all permissions on the **tpcds.reason** table, including create, retrieve, update, and delete.
+
+2. Grant the retrieve permission of **r_reason_sk**, **r_reason_id**, and **r_reason_desc** columns and the update permission of the **r_reason_desc** column in the **tpcds.reason** table to **joe**.
+
+   ```sql
+   mogdb=# GRANT select (r_reason_sk,r_reason_id,r_reason_desc),update (r_reason_desc) ON tpcds.reason TO joe;
+   ```
+
+   Then **joe** has the retrieve permission of **r_reason_sk** and **r_reason_id** columns in the **tpcds.reason** table. To enable user **joe** to grant these permissions to other users, execute the following statement:
+
+   ```sql
+   mogdb=# GRANT select (r_reason_sk, r_reason_id) ON tpcds.reason TO joe WITH GRANT OPTION;
+   ```
+
+   Grant the **mogdb** database connection permission and schema creation permission to user **joe**, and enable this user to grant these permissions to other users.
+
+   ```sql
+   mogdb=# GRANT create,connect on database mogdb TO joe WITH GRANT OPTION;
+   ```
+
+   Create role **tpcds_manager**, grant the **tpcds** schema access permission and object creation permission to this role, but do not enable this role to grant these permissions to others.
+
+   ```sql
+   mogdb=# CREATE ROLE tpcds_manager PASSWORD 'Bigdata@123';
+   mogdb=# GRANT USAGE,CREATE ON SCHEMA tpcds TO tpcds_manager;
+   ```
+
+   Grant all the permissions on the **tpcds_tbspc** tablespace to user **joe** but do not enable this user to grant these permissions to others.
+
+   ```sql
+   mogdb=# CREATE TABLESPACE tpcds_tbspc RELATIVE LOCATION 'tablespace/tablespace_1';
+   mogdb=# GRANT ALL ON TABLESPACE tpcds_tbspc TO joe;
+   ```
+
+**Example 3: Granting the permissions of one user or role to others**
+
+1. Create role **manager**, grant user **joe**'s permissions to the created role, and enable this role to grant its permissions to others.
+
+   ```sql
+   mogdb=# CREATE ROLE manager PASSWORD 'Bigdata@123';
+   mogdb=# GRANT joe TO manager WITH ADMIN OPTION;
+   ```
+
+2. Create role **senior_manager** and grant **manager**'s permissions to **senior_manager**.
+
+   ```sql
+   mogdb=# CREATE ROLE senior_manager PASSWORD 'Bigdata@123';
+   mogdb=# GRANT manager TO senior_manager;
+   ```
+
+3. Revoke permissions granted to **senior_manager** and **manager** and delete **manager**.
+
+   ```sql
+   mogdb=# REVOKE manager FROM joe;
+   mogdb=# REVOKE senior_manager FROM manager;
+   mogdb=# DROP USER manager;
+   ```
+
+**Example: Granting the CMK or CEK permission to other user or role**
+
+1. Connect to an encrypted database.
+
+   ```sql
+   gsql -p 57101 mogdb -r -C
+   mogdb=#  CREATE CLIENT MASTER KEY MyCMK1 WITH ( KEY_STORE = localkms , KEY_PATH = "key_path_value" , ALGORITHM = RSA_2048);
+   CREATE CLIENT MASTER KEY
+   mogdb=# CREATE COLUMN ENCRYPTION KEY MyCEK1 WITH VALUES (CLIENT_MASTER_KEY = MyCMK1, ALGORITHM = AEAD_AES_256_CBC_HMAC_SHA256);
+   CREATE COLUMN ENCRYPTION KEY
+   ```
+
+2. Create a role **newuser** and grant the key permission to **newuser**.
+
+   ```sql
+   mogdb=# CREATE USER newuser PASSWORD 'gauss@123';
+   CREATE ROLE
+   mogdb=# GRANT ALL ON SCHEMA public TO newuser;
+   GRANT
+   mogdb=# GRANT USAGE ON COLUMN_ENCRYPTION_KEY MyCEK1 to newuser;
+   GRANT
+   mogdb=# GRANT USAGE ON CLIENT_MASTER_KEY MyCMK1 to newuser;
+   GRANT
+   ```
+
+3. Set the user to connect to a database and use a CEK to create an encrypted table.
+
+   ```sql
+   mogdb=# SET SESSION AUTHORIZATION newuser PASSWORD 'gauss@123';
+   mogdb=>  CREATE TABLE acltest1 (x int, x2 varchar(50) ENCRYPTED WITH (COLUMN_ENCRYPTION_KEY = MyCEK1, ENCRYPTION_TYPE = DETERMINISTIC));
+   NOTICE:  The 'DISTRIBUTE BY' clause is not specified. Using 'x' as the distribution column by default.
+   HINT:  Please use 'DISTRIBUTE BY' clause to specify suitable data distribution column.
+   CREATE TABLE
+   mogdb=> SELECT has_cek_privilege('newuser', 'MyCEK1', 'USAGE');
+    has_cek_privilege
+   -------------------
+    t
+   (1 row)
+   ```
+
+4. Revoke permissions and delete users.
+
+   ```sql
+   mogdb=# REVOKE USAGE ON COLUMN_ENCRYPTION_KEY MyCEK1 FROM newuser;
+   mogdb=# REVOKE USAGE ON CLIENT_MASTER_KEY MyCMK1 FROM newuser;
+   mogdb=# DROP TABLE newuser.acltest1;
+   mogdb=# DROP COLUMN ENCRYPTION KEY MyCEK1;
+   mogdb=# DROP CLIENT MASTER KEY MyCMK1;
+   mogdb=# DROP SCHEMA IF EXISTS newuser CASCADE;
+   mogdb=# REVOKE ALL ON SCHEMA public FROM newuser ;
+   mogdb=# DROP ROLE IF EXISTS newuser;
+   ```
+
+**Example 4: Revoking permissions and deleting roles and users**
+
+```sql
+mogdb=# REVOKE ALL PRIVILEGES ON tpcds.reason FROM joe;
+mogdb=# REVOKE ALL PRIVILEGES ON SCHEMA tpcds FROM joe;
+mogdb=# REVOKE ALL ON TABLESPACE tpcds_tbspc FROM joe;
+mogdb=# DROP TABLESPACE tpcds_tbspc;
+mogdb=# REVOKE USAGE,CREATE ON SCHEMA tpcds FROM tpcds_manager;
+mogdb=# DROP ROLE tpcds_manager;
+mogdb=# DROP ROLE senior_manager;
+mogdb=# DROP USER joe CASCADE;
+```
+
+## Helpful Links
+
+[REVOKE](120-REVOKE) and [ALTER DEFAULT PRIVILEGES](4-ALTER-DEFAULT-PRIVILEGES)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/109-INSERT.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/109-INSERT.md
new file mode 100644
index 0000000000000000000000000000000000000000..89ae0e6675c0d4e9e04e737aa2db66ead0904960
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/109-INSERT.md
@@ -0,0 +1,162 @@
+---
+title: INSERT
+summary: INSERT
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# INSERT
+
+## Function
+
+**INSERT** inserts new rows into a table.
+
+## Precautions
+
+- You must have the **INSERT** permission on a table in order to insert rows into it.
+
+- Use of the **RETURNING** clause requires the **SELECT** permission on all columns mentioned in **RETURNING**.
+
+- If **ON DUPLICATE KEY UPDATE** is used, you must have the **SELECT** and **UPDATE** permissions on the table and the **SELECT** permission on the unique constraint (primary key or unique index).
+
+- If you use the **query** clause to insert rows from a query, you need to have the **SELECT** permission on any table or column used in the query.
+
+- When you connect to a database compatible to Teradata and **td_compatible_truncation** is **on**, a long string will be automatically truncated. If later **INSERT** statements (not involving foreign tables) insert long strings to columns of char- and varchar-typed columns in the target table, the system will truncate the long strings to ensure no strings exceed the maximum length defined in the target table.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > If inserting multi-byte character data (such as Chinese characters) to database with the character set byte encoding (SQL_ASCII, LATIN1), and the character data crosses the truncation position, the string is truncated based on its bytes instead of characters. Unexpected result will occur in tail after the truncation. If you want correct truncation result, you are advised to adopt encoding set such as UTF8, which has no character data crossing the truncation position.
+
+## Syntax
+
+```ebnf+diagram
+Insert ::= [ WITH [ RECURSIVE ] with_query [, ...] ]
+INSERT INTO table_name [ ( column_name [, ...] ) ]
+    { DEFAULT VALUES
+    | VALUES {( { expression | DEFAULT } [, ...] ) }[, ...]
+    | query }
+    [ ON DUPLICATE KEY UPDATE {{ column_name = { expression | DEFAULT } } [, ...] | NOTHING }]
+    [ RETURNING {* | {output_expression [ [ AS ] output_name ] }[, ...]} ];
+```
+
+## Parameter Description
+
+- **WITH [ RECURSIVE ] with_query [, …]**
+
+    Specifies one or more subqueries that can be referenced by name in the main query, which is equivalent to a temporary table.
+
+    If **RECURSIVE** is specified, it allows a **SELECT** subquery to reference itself by name.
+
+    The detailed format of **with_query** is as follows: with_query_name [ (column_name [,…]) ] AS
+
+    ( {select | values | insert | update | delete} )
+
+  - **with_query_name** specifies the name of the result set generated by a subquery. Such names can be used to access the result sets of subquery in the query.
+  - **column_name** specifies the column name displayed in the subquery result set.
+  - Each subquery can be a **SELECT**, **VALUES**, **INSERT**, **UPDATE** or **DELETE** statement.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** **INSERT ON DUPLICATE KEY UPDATE** does not support the **WITH** and **WITH RECURSIVE** clauses.
+
+- **table_name**
+
+  Specifies the name of the target table where data will be inserted.
+
+  Value range: an existing table name
+
+- **column_name**
+
+    Specifies the name of a column in the target table.
+
+  - The column name can be qualified with a subfield name or array subscript, if needed.
+  - Each column not present in the explicit or implicit column list will be filled with a default value, either its declared default value or **NULL** if there is none. Inserting into only some fields of a composite column leaves the other fields null.
+  - The target column names **column_name** can be listed in any order. If no list of column names is given at all, the default is all the columns of the table in their declared order.
+  - The target columns are the first *N* column names, if there are only *N* columns supplied by the **value** clause or **query**.
+  - The values provided by the **value** clause and query are associated with the corresponding columns from left to right in the table.
+
+    Value range: an existing column
+
+- **expression**
+
+    Specifies an expression or a value to assign to the corresponding column.
+
+  - In the **INSERT ON DUPLICATE KEY UPDATE** statement, **expression** can be **VALUES(column_name)** or **EXCLUDED.column_name**, indicating the value of the **column_name** field of the referenced conflicting rows. **VALUES(column_name)** cannot be nested in an expression (for example, **VALUES(column_name)+1**), but **EXCLUDED** is not limited by this restriction.
+  - If single-quotation marks are inserted in a column, the single-quotation marks need to be used for escape.
+  - If the expression for any column is not of the correct data type, automatic type conversion will be attempted. If the attempt fails, data insertion fails, and the system returns an error message.
+
+- **DEFAULT**
+
+  Specifies the default value of a field. The value is **NULL** if no specified default value has been assigned to it.
+
+- **query**
+
+  Specifies a query statement (**SELECT** statement) that uses the query result as the inserted data.
+
+- **RETURNING**
+
+  Returns the inserted rows. The syntax of the **RETURNING** list is identical to that of the output list of **SELECT**. The **INSERT ON DUPLICATE KEY UPDATE** statement does not support the RETURNING clause.
+
+- **output_expression**
+
+  Specifies an expression used to calculate the output result of the **INSERT** statement after each row is inserted.
+
+  Value range: The expression can use any field in the table. You can use the asterisk (*) to return all fields of the inserted row.
+
+- **output_name**
+
+  Specifies a name to use for a returned column.
+
+  Value range: a string. It must comply with the naming convention rule.
+
+- **ON DUPLICATE KEY UPDATE**
+
+  For a table with a unique constraint (**UNIQUE INDEX** or **PRIMARY KEY**), if the inserted data violates the unique constraint, the **UPDATE** clause is executed on the conflicting row to complete the update. For a table without a unique constraint, only the insert operation is performed. When **UPDATE** is used, if **NOTHING** is specified, this insertion is ignored. You can use **EXCLUDE.** or **VALUES()** to select the column corresponding to the source data.
+
+  - Triggers are supported. The triggering sequence is the same as the actual execution sequence.
+    - Run the **insert** command to trigger the **before insert** and **after insert** triggers.
+    - Run the **update** command to trigger the **before insert**, **before update**, and **after update** triggers.
+    - Run the **update nothing** command to trigger the **before insert** trigger.
+  - Deferrable unique constraints or primary keys are not supported.
+  - For a table with multiple unique constraints, if the inserted data violates multiple unique constraints, the **UPDATE** clause is executed to update only the first conflicting row. (The check sequence is closely related to index maintenance. Generally, the conflict check is preferentially performed on the index that is created first.)
+  - If multiple rows are inserted and these rows conflict with the same row in the table, the system inserts or updates the first row and then updates other rows in sequence.
+  - Primary keys and unique index columns cannot be updated.
+  - Column-store tables, foreign tables, and memory tables are not supported.
+  - Subquery expressions are supported. The syntax and function of the expressions are the same as those of **UPDATE**. In a subquery expression, **EXCLUDED** can be used to select the columns corresponding to the source data.
+
+## Examples
+
+```sql
+-- Create the tpcds.reason_t2 table.
+mogdb=# CREATE TABLE tpcds.reason_t2
+(
+  r_reason_sk    integer,
+  r_reason_id    character(16),
+  r_reason_desc  character(100)
+);
+
+-- Insert a record into a table.
+mogdb=# INSERT INTO tpcds.reason_t2(r_reason_sk, r_reason_id, r_reason_desc) VALUES (1, 'AAAAAAAABAAAAAAA', 'reason1');
+
+-- Insert a record into the table, which is equivalent to the previous syntax.
+mogdb=# INSERT INTO tpcds.reason_t2 VALUES (2, 'AAAAAAAABAAAAAAA', 'reason2');
+
+-- Insert multiple records into the table.
+mogdb=# INSERT INTO tpcds.reason_t2 VALUES (3, 'AAAAAAAACAAAAAAA','reason3'),(4, 'AAAAAAAADAAAAAAA', 'reason4'),(5, 'AAAAAAAAEAAAAAAA','reason5');
+
+-- Insert records whose r_reason_sk in the tpcds.tpcds.reason table is less than 5.
+mogdb=# INSERT INTO tpcds.reason_t2 SELECT * FROM tpcds.reason WHERE r_reason_sk <5;
+
+-- Create a unique index for the table.
+mogdb=# CREATE UNIQUE INDEX reason_t2_u_index ON tpcds.reason_t2(r_reason_sk);
+
+-- Insert multiple records into the table. If the records conflict, update the r_reason_id field in the conflicting row to 'BBBBBBBBCAAAAAAA'.
+mogdb=# INSERT INTO tpcds.reason_t2 VALUES (5, 'BBBBBBBBCAAAAAAA','reason5'),(6, 'AAAAAAAADAAAAAAA', 'reason6') ON DUPLICATE KEY UPDATE r_reason_id = 'BBBBBBBBCAAAAAAA';
+
+-- Delete the tpcds.reason_t2.
+mogdb=# DROP TABLE tpcds.reason_t2;
+```
+
+## Suggestions
+
+- VALUES
+
+  When you run the **INSERT** statement to insert data in batches, you are advised to combine multiple records into one statement to improve data loading performance. Example: **INSERT INTO sections VALUES (30, 'Administration', 31, 1900),(40, 'Development', 35, 2000), (50, 'Development' , 60 , 2001);**
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/11-ALTER-MATERIALIZED-VIEW.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/11-ALTER-MATERIALIZED-VIEW.md
new file mode 100644
index 0000000000000000000000000000000000000000..6a35939389614e8c7e7e902a8788deae665e48b3
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/11-ALTER-MATERIALIZED-VIEW.md
@@ -0,0 +1,79 @@
+---
+title: ALTER MATERIALIZED VIEW
+summary: ALTER MATERIALIZED VIEW
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER MATERIALIZED VIEW
+
+## Function
+
+**ALTER MATERIALIZED VIEW** changes multiple auxiliary attributes of an existing materialized view.
+
+Statements and actions that can be used for ALTER MATERIALIZED VIEW are a subset of ALTER TABLE and have the same meaning when used for materialized views. For details, see **ALTER TABLE**.
+
+## Precautions
+
+- Only the owner of a materialized view or a system administrator has the **ALTER TMATERIALIZED VIEW** permission.
+- The materialized view structure cannot be modified.
+
+## Syntax
+
+- Modify the definition of the materialized view.
+
+  ```ebnf+diagram
+  AlterMaterializedView ::= ALTER MATERIALIZED VIEW [ IF EXISTS ] mv_name
+      OWNER TO new_owner;
+  ```
+
+- Modify the column of a materialized view.
+
+  ```ebnf+diagram
+  AlterMaterializedView ::= ALTER MATERIALIZED VIEW [ IF EXISTS ] mv_name
+      RENAME [ COLUMN ] column_name TO new_column_name;
+  ```
+
+- Rename a materialized view.
+
+  ```ebnf+diagram
+  AlterMaterializedView ::= ALTER MATERIALIZED VIEW [ IF EXISTS ] mv_name
+      RENAME TO new_name;
+  ```
+
+## Parameter Description
+
+- **mv_name**
+
+  Specifies the name of an existing materialized view, which can be schema-qualified.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **column_name**
+
+  Specifies the name of a new or existing column.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **new_column_name**
+
+  Specifies the new name of an existing column.
+
+- **new_owner**
+
+  Specifies the user name of the new owner of a materialized view.
+
+- **new_name**
+
+  Specifies the user name of the new owner of a materialized view.
+
+## Example
+
+```sql
+-- Rename the materialized view foo to bar.
+mogdb=# ALTER MATERIALIZED VIEW foo RENAME TO bar;
+```
+
+## Helpful Links
+
+[CREATE MATERIALIZED VIEW](51-CREATE-MATERIALIZED-VIEW), [CREATE INCREMENTAL MATERIALIZED VIEW](49.1-CREATE-INCREMENTAL-MATERIALIZED-VIEW), [DROP MATERIALIZED VIEW](85-DROP-MATERIALIZED-VIEW), [REFRESH INCREMENTAL MATERIALIZED VIEW](115.1-REFRESH-INCREMENTAL-MATERIALIZED-VIEW) and  [REFRESH MATERIALIZED VIEW](116-REFRESH-MATERIALIZED-VIEW)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/11.1-ALTER-OPERATOR.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/11.1-ALTER-OPERATOR.md
new file mode 100644
index 0000000000000000000000000000000000000000..d243dfd9421cf9b9b91ca6b907980ae7c3fe4d5f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/11.1-ALTER-OPERATOR.md
@@ -0,0 +1,62 @@
+---
+title: ALTER OPERATOR
+summary: ALTER OPERATOR
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# ALTER OPERATOR
+
+## Function
+
+ALTER OPERATOR modifies the definition of an operator.
+
+## Precautions
+
+ALTER OPERATOR changes the definition of an operator. Currently, the only function available is to change the owner of the operator.
+
+To use ALTER OPERATOR, you must be the owner of the operator. To modify the owner, you must also be a direct or indirect member of the new owning role, and that member must have CREATE permission on the operator's schema. (These restrictions force the owner to do nothing that cannot be done by deleting and recreating the operator. However, the super user can modify the ownership of any operator in any way.)
+
+## Syntax
+
+```ebnf+diagram
+AlterOperator ::= ALTER OPERATOR name ( { left_type | NONE } , { right_type | NONE } ) OWNER TO new_owner;
+```
+
+```ebnf+diagram
+AlterOperator ::= ALTER OPERATOR name ( { left_type | NONE } , { right_type | NONE } ) SET SCHEMA new_schema;
+```
+
+## Parameter Description
+
+- **name**
+
+  Name of an existing operator.
+
+- **left_type**
+
+  Data type of the left operand for the operator; if there is no left operand, write NONE.
+
+- **right_type**
+
+  Data type of the right operand for the operator; if there is no right operand, write NONE.
+
+- **new_owner**
+
+  New owner of the operator.
+
+- **new_schema**
+
+  New schema name of the operator.
+
+## Example
+
+Change a user-defined operator for text a @@ b:
+
+```sql
+ALTER OPERATOR @@ (text, text) OWNER TO joe;
+```
+
+## Compatibility
+
+The SQL standard does not contain the ALTER OPERATOR statement.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/11.2-ALTER-RESOURCE-LABEL.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/11.2-ALTER-RESOURCE-LABEL.md
new file mode 100644
index 0000000000000000000000000000000000000000..74438087fd3553199394e2e3414a50e7cdc9d9f7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/11.2-ALTER-RESOURCE-LABEL.md
@@ -0,0 +1,71 @@
+---
+title: ALTER RESOURCE LABEL
+summary: ALTER RESOURCE LABEL
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# ALTER RESOURCE LABEL
+
+## Function
+
+**ALTER RESOURCE LABEL** modifies resource labels.
+
+## Precautions
+
+Only users with the  **poladmin**  or  **sysadmin**  permission, or the initial user can perform this operation.
+
+## Syntax
+
+```ebnf+diagram
+AlterResourceLabel ::= ALTER RESOURCE LABEL label_name (ADD|REMOVE)
+  label_item_list[, ...]*;
+```
+
+- label_item_list
+
+  ```ebnf+diagram
+  label_item_list ::= resource_type(resource_path[, ...]*)
+  ```
+
+- resource_type
+
+  ```ebnf+diagram
+  label_item_list ::= TABLE | COLUMN | SCHEMA | VIEW | FUNCTION
+  ```
+
+## Parameter Description
+
+- **label_name**
+
+  Specifies the resource label name.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **resource_type**
+
+  Specifies the type of database resources to be labeled.
+
+- **resource_path**
+
+  Specifies the path of database resources.
+
+## Examples
+
+```sql
+-- Create basic table table_for_label.
+mogdb=# CREATE TABLE table_for_label(col1 int, col2 text);
+
+-- Create resource label table_label.
+mogdb=# CREATE RESOURCE LABEL table_label ADD COLUMN(table_for_label.col1);
+
+-- Attach resource label table_label to col2.
+mogdb=# ALTER RESOURCE LABEL table_label ADD COLUMN(table_for_label.col2)
+
+-- Remove table_label from an item.
+mogdb=# ALTER RESOURCE LABEL table_label REMOVE COLUMN(table_for_label.col1);
+```
+
+## Helpful Links
+
+[CREATE RESOURCE LABEL](53.1-CREATE-RESOURCE-LABEL), [DROP RESOURCE LABEL](86.1-DROP-RESOURCE-LABEL).
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/11.3-ALTER-RESOURCE-POOL.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/11.3-ALTER-RESOURCE-POOL.md
new file mode 100644
index 0000000000000000000000000000000000000000..c10f2707977eef2bee0e2786e18632963576cfd0
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/11.3-ALTER-RESOURCE-POOL.md
@@ -0,0 +1,116 @@
+---
+title: ALTER RESOURCE POOL
+summary: ALTER RESOURCE POOL
+author: Zhang Cuiping
+date: 2021-11-01
+---
+
+# ALTER RESOURCE POOL
+
+## Function
+
+**ALTER RESOURCE POOL** changes the Cgroup of a resource pool.
+
+## Precautions
+
+Only a user with the **ALTER** permission on the current database can perform this operation.
+
+## Syntax
+
+```ebnf+diagram
+AlterResourcePool ::= ALTER RESOURCE POOL pool_name
+    WITH ({MEM_PERCENT= pct | CONTROL_GROUP="group_name" | ACTIVE_STATEMENTS=stmt | MAX_DOP = dop | MEMORY_LIMIT='memory_size' | io_limits=io_limits | io_priority='io_priority'}[, ... ]);
+```
+
+## Parameter Description
+
+- **pool_name**
+
+  Specifies the name of a resource pool.
+
+  The name of the resource pool is the name of an existing resource pool.
+
+  Value range: a string. It must comply with the identifier naming convention.
+
+- **group_name**
+
+  Specifies the name of a Cgroup.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > - You can use either double quotation marks ("") or single quotation marks (") in the syntax when setting the name of a Cgroup.
+  > - The value of **group_name** is case-sensitive.
+  > - If **group_name** is not specified, the string "Medium" will be used by default in the syntax, indicating the **Medium** Timeshare Cgroup under **DefaultClass**.
+  > - If a database administrator specifies a Workload Cgroup under **Class**, for example, **control_group** set to **class1:workload1**, the resource pool will be associated with the **workload1** Cgroup under **class1**. The level of the Workload Cgroup can also be specified. For example, **control_group** is set to **class1:workload1:1**.
+  > - If a database user specifies the Timeshare Cgroup string (**Rush**, **High**, **Medium**, or **Low**) in the syntax, for example, **control_group** is set to **High**, the resource pool will be associated with the **High** Timeshare Cgroup under **DefaultClass**.
+
+  Value range: an existing Cgroup.
+
+- **stmt**
+
+  Specifies the maximum number of statements that can be concurrently executed in a resource pool.
+
+  Value range: numeric data ranging from -1 to 2147483647
+
+- **dop**
+
+  Specifies the maximum statement concurrency degree for a resource pool, equivalent to the number of threads that can be created for executing a statement.
+
+  Value range: numeric data ranging from 1 to 2147483647
+
+- **memory_size**
+
+  Specifies the maximum memory size of a resource pool.
+
+  Value range: a string from 1 KB to 2047 GB
+
+- **mem_percent**
+
+  Specifies the proportion of available resource pool memory to the total memory or group user memory.
+
+  In multi-tenant scenarios, the value of **mem_percent** of group users or service users ranges from 1 to 100. The default value is **20**.
+
+  In common scenarios, the value of **mem_percent** of common users is an integer ranging from 0 to 100. The default value is **0**.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** When both **mem_percent** and **memory_limit** are specified, only **mem_percent** takes effect.
+
+- **io_limits**
+
+  Specifies the upper limit of IOPS in a resource pool.
+
+  The IOPS is counted by ones for column storage and by 10 thousands for row storage.
+
+- **io_priority**
+
+  Specifies the I/O priority for jobs that consume many I/O resources. It takes effect when the I/O usage reaches 90%.
+
+  There are three priorities: **Low**, **Medium**, and **High**. If you do not want to control I/O resources, use the default value **None**.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The settings of **io_limits** and **io_priority** are valid only for complex jobs, such as batch import (using **INSERT INTO SELECT**, **COPY FROM**, or **CREATE TABLE AS**), complex queries involving over 500 MB data on each DN, and **VACUUM FULL**.
+
+## Examples
+
+The example assumes that the user has created the **class1** Cgroup and three Workload Cgroups under **class1**: **Low**, **wg1**, and **wg2**.
+
+```sql
+-- Create a resource pool.
+mogdb=# CREATE RESOURCE POOL pool1;
+
+-- Update a resource pool and set its Cgroup to a High Timeshare Workload Cgroup under DefaultClass.
+mogdb=# ALTER RESOURCE POOL pool1 WITH (CONTROL_GROUP="High");
+
+-- Update a resource pool and set its Cgroup to a Low Timeshare Workload Cgroup under class1.
+mogdb=# ALTER RESOURCE POOL pool1 WITH (CONTROL_GROUP="class1:Low");
+
+-- Update a resource pool and set its Cgroup to a wg1 Workload Cgroup under class1.
+mogdb=# ALTER RESOURCE POOL pool1 WITH (CONTROL_GROUP="class1:wg1");
+
+-- Update a resource pool and set its Cgroup to a wg2 Workload Cgroup under class1.
+mogdb=# ALTER RESOURCE POOL pool1 WITH (CONTROL_GROUP="class1:wg2:3");
+-- Delete the resource pool pool1.
+mogdb=# DROP RESOURCE POOL pool1;
+```
+
+## Helpful Links
+
+[CREATE RESOURCE POOL](53.2-CREATE-RESOURCE-POOL) and [DROP RESOURCE POOL](86.2-DROP-RESOURCE-POOL)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/110-LOCK.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/110-LOCK.md
new file mode 100644
index 0000000000000000000000000000000000000000..d9e4a03baaa1255c9141150c475527c7a306c041
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/110-LOCK.md
@@ -0,0 +1,136 @@
+---
+title: LOCK
+summary: LOCK
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# LOCK
+
+## Function
+
+**LOCK TABLE** obtains a table-level lock.
+
+MogDB always tries to select the lock mode with minimum constraints when automatically requesting a lock for a statement referenced by a table. Use **LOCK** if users need a more strict lock mode. For example, suppose an application runs a transaction at the Read Committed isolation level and needs to ensure that data in a table remains stable in the duration of the transaction. To achieve this, you could obtain **SHARE** lock mode over the table before the query. This will prevent concurrent data changes and ensure subsequent reads of the table see a stable view of committed data. It is because the **SHARE** lock mode conflicts with the **ROW EXCLUSIVE** lock acquired by writers, and your **LOCK TABLE name IN SHARE MODE** statement will wait until any concurrent holders of **ROW EXCLUSIVE** mode locks commit or roll back. Therefore, once you obtain the lock, there are no uncommitted writes outstanding; furthermore none can begin until you release the lock.
+
+## Precautions
+
+- **LOCK TABLE** is useless outside a transaction block: the lock would remain held only to the completion of the statement. If **LOCK TABLE** is out of any transaction block, an error is reported.
+- If no lock mode is specified, then **ACCESS EXCLUSIVE**, the most restrictive mode, is used.
+- LOCK TABLE … **IN ACCESS SHARE MODE** requires the **SELECT** permission on the target table. All other forms of **LOCK** require table-level **UPDATE** and/or the **DELETE** permission.
+- There is no **UNLOCK TABLE** statement. Locks are always released at transaction end.
+- **LOCK TABLE** only deals with table-level locks, and so the mode names involving **ROW** are all misnomers. These mode names should generally be read as indicating the intention of the user to acquire row-level locks within the locked table. Also, **ROW EXCLUSIVE** mode is a shareable table lock. Note that all the lock modes have identical semantics so far as **LOCK TABLE** is concerned, differing only in the rules about which modes conflict with which. For details about the rules, see [Table 1](#lockmodec).
+- If the xc_maintenance_mode parameter is not enabled, an error is reported when an ACCESS EXCLUSIVE lock is applied for a system catalog.
+
+## Syntax
+
+```ebnf+diagram
+Lock ::= LOCK [ TABLE ] {[ ONLY ] name [, ...]| {name [ * ]} [, ...]}
+    [ IN {ACCESS SHARE | ROW SHARE | ROW EXCLUSIVE | SHARE UPDATE EXCLUSIVE | SHARE | SHARE ROW EXCLUSIVE | EXCLUSIVE | ACCESS EXCLUSIVE} MODE ]
+    [ NOWAIT ];
+```
+
+## Parameter Description
+
+**Table 1** Lock mode conflicts <a id="lockmodec"></a>
+
+| Requested Lock Mode/Current Lock Mode | ACCESS SHARE | ROW SHARE | ROW EXCLUSIVE | SHARE UPDATE EXCLUSIVE | SHARE | SHARE ROW EXCLUSIVE | EXCLUSIVE | ACCESS EXCLUSIVE |
+| :------------------------------------ | :----------- | :-------- | :------------ | :--------------------- | :---- | :------------------ | :-------- | :--------------- |
+| ACCESS SHARE                          | -            | -         | -             | -                      | -     | -                   | -         | X                |
+| ROW SHARE                             | -            | -         | -             | -                      | -     | -                   | X         | X                |
+| ROW EXCLUSIVE                         | -            | -         | -             | -                      | X     | X                   | X         | X                |
+| SHARE UPDATE EXCLUSIVE                | -            | -         | -             | X                      | X     | X                   | X         | X                |
+| SHARE                                 | -            | -         | X             | X                      | -     | X                   | X         | X                |
+| SHARE ROW EXCLUSIVE                   | -            | -         | X             | X                      | X     | X                   | X         | X                |
+| EXCLUSIVE                             | -            | X         | X             | X                      | X     | X                   | X         | X                |
+| ACCESS EXCLUSIVE                      | X            | X         | X             | X                      | X     | X                   | X         | X                |
+
+**LOCK** parameters are as follows:
+
+- **name**
+
+  Specifies the name (optionally schema-qualified) of an existing table to lock.
+
+  Tables are locked one-by-one in the order specified in the **LOCK TABLE** statement.
+
+  Value range: an existing table name
+
+- **ONLY**
+
+  If **ONLY** is specified, only that table is locked. If **ONLY** is not specified, the table and all its sub-tables are locked.
+
+- **ACCESS SHARE**
+
+  Conflicts with the ACCESS EXCLUSIVE lock mode only.
+
+  The **SELECT** statement acquires a lock of this mode on referenced tables. Typically, any command that reads a table without modifying it acquires this lock mode.
+
+- **ROW SHARE**
+
+  It conflicts with the EXCLUSIVE and ACCESS EXCLUSIVE lock modes.
+
+  **SELECT FOR UPDATE** and **SELECT FOR SHARE** automatically acquire the **ROW SHARE** lock on the target table and add the **ACCESS SHARE** lock to other referenced tables except **FOR SHARE** and **FOR UPDATE**.
+
+- **ROW EXCLUSIVE**
+
+  Allows concurrent read of a table but does not allow modification of data in the table like **ROW SHARE**. **UPDATE**, **DELETE**, and **INSERT** automatically acquire the **ROW SHARE** lock on the target table and add the **ACCESS SHARE** lock to other referenced tables. Generally, all statements that modify table data acquire the **ROW EXCLUSIVE** lock for tables.
+
+- **SHARE UPDATE EXCLUSIVE**
+
+  Protects a table against concurrent schema changes and VACUUM runs.
+
+  Acquired by **VACUUM** (without **FULL**), **ANALYZE** and **CREATE INDEX CONCURRENTLY** statements, and some forms of **ALTER TABLE**.
+
+- **SHARE**
+
+  Allows concurrent queries of a table but does not allow modification of the table.
+
+  Acquired by **CREATE INDEX** (without **CONCURRENTLY**).
+
+- **SHARE ROW EXCLUSIVE**
+
+  Protects a table against concurrent data changes, and is self-exclusive so that only one session can hold it at a time.
+
+  No SQL statements automatically acquire this lock mode.
+
+- **EXCLUSIVE**
+
+  Allows concurrent queries of the target table but does not allow any other operations.
+
+  This mode allows only concurrent **ACCESS SHARE** locks; that is, only reads from the table can proceed in parallel with a transaction holding this lock mode.
+
+  No SQL statements automatically acquire this lock mode on user tables. However, it will be acquired on some system catalogs in case of some operations.
+
+- **ACCESS EXCLUSIVE**
+
+  Guarantees that the holder is the only transaction accessing the table in any way.
+
+  Acquired by the **ALTER TABLE**, **DROP TABLE**, **TRUNCATE**, and **REINDEX** statements.
+
+  This is also the default lock mode for **LOCK TABLE** statements that do not specify a mode explicitly.
+
+- **NOWAIT**
+
+  Specifies that **LOCK TABLE** should not wait for any conflicting locks to be released: if the specified lock(s) cannot be acquired immediately without waiting, the transaction is aborted.
+
+  If **NOWAIT** is not specified, **LOCK TABLE** obtains a table-level lock, waiting if necessary for any conflicting locks to be released.
+
+## Example
+
+```sql
+-- Obtain a SHARE ROW EXCLUSIVE lock on a primary key table when going to perform a delete operation.
+mogdb=# CREATE TABLE tpcds.reason_t1 AS TABLE tpcds.reason;
+
+mogdb=# START TRANSACTION;
+
+mogdb=# LOCK TABLE tpcds.reason_t1 IN SHARE ROW EXCLUSIVE MODE;
+
+mogdb=# DELETE FROM tpcds.reason_t1 WHERE r_reason_desc IN(SELECT r_reason_desc FROM tpcds.reason_t1 WHERE r_reason_sk < 6 );
+
+mogdb=# DELETE FROM tpcds.reason_t1 WHERE r_reason_sk = 7;
+
+mogdb=# COMMIT;
+
+-- Delete the tpcds.reason_t1 table.
+mogdb=# DROP TABLE tpcds.reason_t1;
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/111-MOVE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/111-MOVE.md
new file mode 100644
index 0000000000000000000000000000000000000000..faf28aadaa6d749c8bff8b39af85f548689271bf
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/111-MOVE.md
@@ -0,0 +1,81 @@
+---
+title: MOVE
+summary: MOVE
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# MOVE
+
+## Function
+
+**MOVE** repositions a cursor without retrieving any data. **MOVE** works exactly like the **FETCH** statement, except it only repositions the cursor and does not return rows.
+
+## Precautions
+
+None
+
+## Syntax
+
+```ebnf+diagram
+Move ::= MOVE [ direction [ FROM | IN ] ] cursor_name;
+```
+
+The **direction** clause specifies optional parameters.
+
+```ebnf+diagram
+direction ::= NEXT
+   | PRIOR
+   | FIRST
+   | LAST
+   | ABSOLUTE count
+   | RELATIVE count
+   | count
+   | ALL
+   | FORWARD
+   | FORWARD count
+   | FORWARD ALL
+   | BACKWARD
+   | BACKWARD count
+   | BACKWARD ALL
+```
+
+## Parameter Description
+
+The parameters of **MOVE** and **FETCH** are the same. For details, see **Parameter Description** in **FETCH**.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> On successful completion, a **MOVE** statement returns a tag of the form **MOVE count**. The **count** is the number of rows that a **FETCH** statement with the same parameters would have returned (possibly zero).
+
+## Examples
+
+```sql
+-- Start a transaction.
+mogdb=# START TRANSACTION;
+
+-- Define a cursor cursor1.
+mogdb=# CURSOR cursor1 FOR SELECT * FROM tpcds.reason;
+
+-- Skip the first three rows of cursor1.
+mogdb=# MOVE FORWARD 3 FROM cursor1;
+
+-- Fetch the first four rows from cursor1.
+mogdb=# FETCH 4 FROM cursor1;
+ r_reason_sk |   r_reason_id    |                                            r_reason_desc
+-------------+------------------+------------------------------------------------------------------------------------------------------
+           4 | AAAAAAAAEAAAAAAA | Not the product that was ordred
+           5 | AAAAAAAAFAAAAAAA | Parts missing
+           6 | AAAAAAAAGAAAAAAA | Does not work with a product that I have
+           7 | AAAAAAAAHAAAAAAA | Gift exchange
+(4 rows)
+
+-- Close the cursor.
+mogdb=# CLOSE cursor1;
+
+-- End the transaction.
+mogdb=# END;
+```
+
+## Helpful Links
+
+[CLOSE](36-CLOSE) and [FETCH](107-FETCH)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/112-MERGE-INTO.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/112-MERGE-INTO.md
new file mode 100644
index 0000000000000000000000000000000000000000..49f68bab1d8c49614604d8e05cf8bda40cc57033
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/112-MERGE-INTO.md
@@ -0,0 +1,143 @@
+---
+title: MERGE INTO
+summary: MERGE INTO
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# MERGE INTO
+
+## Function
+
+**MERGE INTO** conditionally matches data in a target table with that in a source table. If data matches, **UPDATE** is executed on the target table; if data does not match, **INSERT** is executed. You can use this syntax to run **UPDATE** and **INSERT** at a time for convenience.
+
+## Precautions
+
+You have the **INSERT** and **UPDATE** permissions for the target table and the **SELECT** permission for the source table.
+
+## Syntax
+
+```ebnf+diagram
+MergeInto ::= MERGE [/*+ plan_hint */] INTO table_name [ [ AS ] alias ]
+USING { { table_name | view_name } | subquery } [ [ AS ] alias ]
+ON ( condition )
+[
+  WHEN MATCHED THEN
+  UPDATE SET { column_name = { expression | DEFAULT } |
+          ( column_name [, ...] ) = ( { expression | DEFAULT } [, ...] ) } [, ...]
+  [ WHERE condition ]
+]
+[
+  WHEN NOT MATCHED THEN
+  INSERT { DEFAULT VALUES |
+  [ ( column_name [, ...] ) ] VALUES ( { expression | DEFAULT } [, ...] ) [, ...] [ WHERE condition ] }
+];
+```
+
+## Parameter Description
+
+- **plan_hint** clause
+
+  Follows the **MERGE** keyword in the **/\*+ \*/** format. It is used to optimize the plan of a **MERGE** statement block. For details, see [Hint-based Tuning](9-hint-based-tuning). In each statement, only the first **/\*+** _plan_hint _***/** comment block takes effect as a hint. Multiple hints can be written.
+
+- **INTO** clause
+
+    Specifies the target table that is being updated or has data being inserted.
+
+  - **talbe_name**
+
+    Specifies the name of the target table.
+
+  - **alias**
+
+    Specifies the alias of the target table.
+
+    Value range: a string. It must comply with the naming convention rule.
+
+- **USING** clause
+
+  Specifies the source table, which can be a table, view, or subquery. If the target table is a replication table, the **USING** clause cannot contain non-replication tables.
+
+- **ON** clause
+
+  Specifies the condition used to match data between the source and target tables. Columns in the condition cannot be updated.
+
+- **WHEN MATCHED** clause
+
+  Performs **UPDATE** if data in the source table matches that in the target table based on the condition.
+
+  System catalogs and system columns cannot be updated.
+
+- **WHEN NOT MATCHED** clause
+
+  Performs **INSERT** if data in the source table does not match that in the target table based on the condition.
+
+  An **INSERT** clause can contain only one **VALUES**.
+
+  The order of **WHEN MATCHED** and **WHEN NOT MATCHED** clauses can be reversed. One of them can be used by default, but they cannot be both used at one time. Two **WHEN MATCHED** or **WHEN NOT MATCHED** clauses cannot be specified at the same time.
+
+- **DEFAULT**
+
+  Specifies the default value of a column.
+
+  The value is **NULL** if no default value is assigned to it.
+
+- **WHERE condition**
+
+  Specifies the conditions for the **UPDATE** and **INSERT** clauses. The two clauses will be executed only when the conditions are met. The default value can be used. System columns cannot be referenced in **WHERE condition**.
+
+## Examples
+
+```sql
+-- Create the target table products and source table newproducts, and insert data to them.
+mogdb=# CREATE TABLE products
+(
+product_id INTEGER,
+product_name VARCHAR2(60),
+category VARCHAR2(60)
+);
+
+mogdb=# INSERT INTO products VALUES (1501, 'vivitar 35mm', 'electrncs');
+mogdb=# INSERT INTO products VALUES (1502, 'olympus is50', 'electrncs');
+mogdb=# INSERT INTO products VALUES (1600, 'play gym', 'toys');
+mogdb=# INSERT INTO products VALUES (1601, 'lamaze', 'toys');
+mogdb=# INSERT INTO products VALUES (1666, 'harry potter', 'dvd');
+
+mogdb=# CREATE TABLE newproducts
+(
+product_id INTEGER,
+product_name VARCHAR2(60),
+category VARCHAR2(60)
+);
+
+mogdb=# INSERT INTO newproducts VALUES (1502, 'olympus camera', 'electrncs');
+mogdb=# INSERT INTO newproducts VALUES (1601, 'lamaze', 'toys');
+mogdb=# INSERT INTO newproducts VALUES (1666, 'harry potter', 'toys');
+mogdb=# INSERT INTO newproducts VALUES (1700, 'wait interface', 'books');
+
+-- Run MERGE INTO.
+mogdb=# MERGE INTO products p
+USING newproducts np
+ON (p.product_id = np.product_id)
+WHEN MATCHED THEN
+  UPDATE SET p.product_name = np.product_name, p.category = np.category WHERE p.product_name != 'play gym'
+WHEN NOT MATCHED THEN
+  INSERT VALUES (np.product_id, np.product_name, np.category) WHERE np.category = 'books';
+MERGE 4
+
+-- Query updates.
+mogdb=# SELECT * FROM products ORDER BY product_id;
+ product_id |  product_name  | category
+------------+----------------+-----------
+       1501 | vivitar 35mm   | electrncs
+       1502 | olympus camera | electrncs
+       1600 | play gym       | toys
+       1601 | lamaze         | toys
+       1666 | harry potter   | toys
+       1700 | wait interface | books
+(6 rows)
+
+-- Delete the table.
+mogdb=# DROP TABLE products;
+mogdb=# DROP TABLE newproducts;
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/112.1-PREDICT-BY.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/112.1-PREDICT-BY.md
new file mode 100644
index 0000000000000000000000000000000000000000..41741baa202c10ee6cf444ad7151cc4ac52cafb8
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/112.1-PREDICT-BY.md
@@ -0,0 +1,47 @@
+---
+title: PREDICT BY
+summary: PREDICT BY
+author: Zhang Cuiping
+date: 2021-11-01
+---
+
+# PREDICT BY
+
+## Function
+
+**PREDICT BY** uses a trained model to perform inference tasks.
+
+## Precautions
+
+The name of the invoked model can be viewed in the **gs_model_warehouse** system catalog.
+
+## Syntax
+
+```ebnf+diagram
+PredictBy ::= PREDICT BY model_name [ (FEATURES attribute [, attribute]) ]
+```
+
+## Parameter Description
+
+- model_name
+
+  Name of the model of a speculative task.
+
+  Value range: a string. It must comply with the identifier naming convention.
+
+- attribute
+
+  Name of the input feature column of a speculative task.
+
+  Value range: a string. It must comply with the identifier naming convention.
+
+## Examples
+
+```
+SELECT id, PREDICT BY price_model (FEATURES size,lot), price
+FROM houses;
+```
+
+## Helpful Links
+
+[CREATE MODEL](50.3-CREATE-MODEL) and [DROP MODEL](84.3-DROP-MODEL)
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/113-PREPARE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/113-PREPARE.md
new file mode 100644
index 0000000000000000000000000000000000000000..192cca6d2e52c20c7b629fabb5998605ce2e437a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/113-PREPARE.md
@@ -0,0 +1,46 @@
+---
+title: PREPARE
+summary: PREPARE
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# PREPARE
+
+## Function
+
+**PREPARE** creates a prepared statement.
+
+A prepared statement is a performance optimizing object on the server. When the **PREPARE** statement is executed, the specified query is parsed, analyzed, and rewritten. When **EXECUTE** is executed, the prepared statement is planned and executed. This avoids repetitive parsing and analysis. After the **PREPARE** statement is created, it exists throughout the database session. Once it is created (even if in a transaction block), it will not be deleted when a transaction is rolled back. It can only be deleted by explicitly invoking **DEALLOCATE** or automatically deleted when the session ends.
+
+## Precautions
+
+None
+
+## Syntax
+
+```ebnf+diagram
+Prepare ::= PREPARE name [ ( data_type [, ...] ) ] AS statement;
+```
+
+## Parameter Description
+
+- **name**
+
+  Specifies the name of a prepared statement. It must be unique in the session.
+
+- **data_type**
+
+  Specifies the type of an argument.
+
+- **statement**
+
+  Specifies a **SELECT**, **INSERT**, **UPDATE**, **DELETE**, **MERGE INTO**, or **VALUES** statement.
+
+## Examples
+
+See **Examples** in **EXECUTE**.
+
+## Helpful Links
+
+[DEALLOCATE](72-DEALLOCATE)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/114-PREPARE-TRANSACTION.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/114-PREPARE-TRANSACTION.md
new file mode 100644
index 0000000000000000000000000000000000000000..8d837f3e8082779b676f8744c4ea0d35cb255946
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/114-PREPARE-TRANSACTION.md
@@ -0,0 +1,43 @@
+---
+title: PREPARE TRANSACTION
+summary: PREPARE TRANSACTION
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# PREPARE TRANSACTION
+
+## Function
+
+**PREPARE TRANSACTION** prepares the current transaction for two-phase commit.
+
+After this statement, the transaction is no longer associated with the current session; instead, its state is fully stored on disk, and there is a high probability that it can be committed successfully, even if a database crash occurs before the commit is requested.
+
+Once prepared, a transaction can later be committed or rolled back with **COMMIT PREPARED** or **ROLLBACK PREPARED**, respectively. Those statements can be issued from any session, not only the one that executed the original transaction.
+
+From the point of view of the issuing session, **PREPARE TRANSACTION** is not unlike a **ROLLBACK** statement: after executing it, there is no active current transaction, and the effects of the prepared transaction are no longer visible. (The effects will become visible again if the transaction is committed.)
+
+If the **PREPARE TRANSACTION** statement fails for any reason, it becomes a **ROLLBACK** and the current transaction is canceled.
+
+## Precautions
+
+- The transaction function is maintained automatically by the database, and should be not visible to users.
+- When running the **PREPARE TRANSACTION** statement, increase the value of **max_prepared_transactions** in configuration file **postgresql.conf**. You are advised to set **max_prepared_transactions** to a value not less than that of **max_connections** so that one pending prepared transaction is available for each session.
+
+## Syntax
+
+```ebnf+diagram
+PrepareTransaction ::= PREPARE TRANSACTION transaction_id;
+```
+
+## Parameter Description
+
+**transaction_id**
+
+Specifies an arbitrary identifier that later identifies this transaction for **COMMIT PREPARED** or **ROLLBACK PREPARED**. The identifier must be different from those for current prepared transactions.
+
+Value range: The identifier must be written as a string literal, and must be less than 200 bytes long.
+
+## Helpful Links
+
+[COMMIT PREPARED](40-COMMIT-PREPARED) and [ROLLBACK PREPARED](122-ROLLBACK-PREPARED)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/114.1-PURGE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/114.1-PURGE.md
new file mode 100644
index 0000000000000000000000000000000000000000..8ac5fc31ca5a7f7056c391cb2533a3db0afbbb79
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/114.1-PURGE.md
@@ -0,0 +1,108 @@
+---
+title: PURGE
+summary: PURGE
+author: Zhang Cuiping
+date: 2021-11-01
+---
+
+# PURGE
+
+## Function
+
+The **PURGE** statement can be used to:
+
+- Clear tables or indexes from the recycle bin and release all space related to the objects.
+- Clear the recycle bin.
+- Clear the objects of a specified tablespace in the recycle bin.
+
+## Precautions
+
+- The purge operation supports tables (**PURGE TABLE**), indexes (**PURGE INDEX**), recycle bins (**PURGE RECYCLEBIN**), and tablespaces (**PURGE TABLESPACE**).
+- The permission requirements for performing the **PURGE** operation are as follows:
+  - **PURGE TABLE**: The user must be the owner of the table and must have the **USAGE** permission on the schema to which the table belongs. By default, the system administrator has this permission.
+  - **PURGE INDEX**: The user must be the owner of the index and have the **USAGE** permission on the schema to which the index belongs. By default, the system administrator has this permission.
+  - **PURGE TABLESPACE**: The user must be the owner of the tablespace and have the **USAGE** permission on the schema to which the object belongs. The common user can delete only the table owned by oneself in the recycle bin. By default, the system administrator can delete all the objects in the specified tablespace in the recycle bin.
+  - **PURGE RECYCLEBIN**: Common users can clear only the objects owned by themselves in the recycle bin. In addition, the user must have the **USAGE** permission of the schema to which the objects belong. By default, the system administrator can clear all objects in the recycle bin.
+
+## Syntax
+
+```ebnf+diagram
+Purge ::= PURGE { TABLE [schema_name'.']table_name
+        | INDEX index_name
+        | RECYCLEBIN
+      }
+```
+
+## Parameter Description
+
+- _[ **schema_name.** ]_
+
+  Schema name
+
+- TABLE *[ schema_name. ] table_name*
+
+  Clears a specified table in the recycle bin.
+
+- INDEX *index_name*
+
+  Clears a specified index in the recycle bin.
+
+- RECYCLEBIN
+
+  Clears the objects in the recycle bin.
+
+## Examples
+
+```
+-- Create the reason_table_space tablespace.
+mogdb=#  CREATE TABLESPACE REASON_TABLE_SPACE1 owner tpcds RELATIVE location 'tablespace/tsp_reason1';
+-- Create the tpcds.reason_t1 table in the tablespace.
+mogdb=#  CREATE TABLE tpcds.reason_t1
+ (
+  r_reason_sk    integer,
+  r_reason_id    character(16),
+  r_reason_desc  character(100)
+  ) tablespace reason_table_space1;
+-- Create the tpcds.reason_t2 table in the tablespace.
+mogdb=#  CREATE TABLE tpcds.reason_t2
+ (
+  r_reason_sk    integer,
+  r_reason_id    character(16),
+  r_reason_desc  character(100)
+  ) tablespace reason_table_space1;
+-- Create the tpcds.reason_t3 table in the tablespace.
+mogdb=#  CREATE TABLE tpcds.reason_t3
+ (
+  r_reason_sk    integer,
+  r_reason_id    character(16),
+  r_reason_desc  character(100)
+  ) tablespace reason_table_space1;
+mogdb=#  CREATE TABLE tpcds.reason_t4
+ (
+  r_reason_sk    integer,
+  r_reason_id    character(16),
+  r_reason_desc  character(100)
+  );
+mogdb=#  DROP TABLE tpcds.reason_t1;
+mogdb=#  DROP TABLE tpcds.reason_t2;
+mogdb=#  DROP TABLE tpcds.reason_t3;
+mogdb=#  DROP TABLE tpcds.reason_t4;
+-- View the recycle bin.
+mogdb=#  SELECT rcyname,rcyoriginname,rcytablespace FROM GS_RECYCLEBIN;
+        rcyname        | rcyoriginname | rcytablespace
+-----------------------+---------------+---------------
+ BIN$16409$2CEE988==$0 | reason_t1     |         16408
+ BIN$16412$2CF2188==$0 | reason_t2     |         16408
+ BIN$16415$2CF2EC8==$0 | reason_t3     |         16408
+ BIN$16418$2CF3EC8==$0 | reason_t4     |             0
+(4 rows)
+-- Clear the table.
+mogdb=#  PURGE TABLE tpcds.reason_t1;
+mogdb=#  SELECT rcyname,rcyoriginname,rcytablespace FROM GS_RECYCLEBIN;
+        rcyname        | rcyoriginname | rcytablespace
+-----------------------+---------------+---------------
+ BIN$16412$2CF2188==$0 | reason_t2     |         16408
+ BIN$16415$2CF2EC8==$0 | reason_t3     |         16408
+ BIN$16418$2CF3EC8==$0 | reason_t4     |             0
+(3 rows)
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/115-REASSIGN-OWNED.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/115-REASSIGN-OWNED.md
new file mode 100644
index 0000000000000000000000000000000000000000..aa51c80371f162cfe0ec15e292531a5772566bae
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/115-REASSIGN-OWNED.md
@@ -0,0 +1,39 @@
+---
+title: REASSIGN OWNED
+summary: REASSIGN OWNED
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# REASSIGN OWNED
+
+## Function
+
+**REASSIGN OWNED** changes the owner of the database object.
+
+**REASSIGN OWNED** requires that the system change owners of all the database objects owned by **old_roles** to **new_role**.
+
+## Precautions
+
+- **REASSIGN OWNED** is often executed before role deletion.
+- To run the REASSIGN OWNED statement, you must have the permissions of the original and target roles.
+
+## Syntax
+
+```ebnf+diagram
+ReassignOwned ::= REASSIGN OWNED BY old_role [, ...] TO new_role;
+```
+
+## Parameter Description
+
+- **old_role**
+
+  Specifies the role name of the old owner.
+
+- **new_role**
+
+  Specifies the role name of the new owner.
+
+## Examples
+
+None
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/115.1-REFRESH-INCREMENTAL-MATERIALIZED-VIEW.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/115.1-REFRESH-INCREMENTAL-MATERIALIZED-VIEW.md
new file mode 100644
index 0000000000000000000000000000000000000000..196bc93f652b15a33f234d824cca2c7ec4ec382a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/115.1-REFRESH-INCREMENTAL-MATERIALIZED-VIEW.md
@@ -0,0 +1,46 @@
+---
+title: REFRESH INCREMENTAL MATERIALIZED VIEW
+summary: REFRESH INCREMENTAL MATERIALIZED VIEW
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# REFRESH INCREMENTAL MATERIALIZED VIEW
+
+## Function
+
+REFRESH INCREMENTAL MATERIALIZED VIEW refreshes the materialized view in materialized mode.
+
+## Precautions
+
+- Incremental refresh supports only incremental materialized views.
+- To refresh a materialized view, you must have the SELECT permission on the base table.
+
+## Syntax
+
+```ebnf+diagram
+RefreshIncrementalMaterializedView ::= REFRESH INCREMENTAL MATERIALIZED VIEW mv_name;
+```
+
+## Parameter Description
+
+- **mv_name**
+
+  Name of the materialized view to be refreshed.
+
+## Example
+
+```sql
+-- Create an ordinary table.
+mogdb=# CREATE TABLE my_table (c1 int, c2 int);
+-- Create an incremental materialized view.
+mogdb=# CREATE INCREMENTAL MATERIALIZED VIEW my_imv AS SELECT * FROM my_table;
+-- Write data to the base table.
+mogdb=# INSERT INTO my_table VALUES(1,1),(2,2);
+-- Incrementally refresh the incremental materialized view my_imv.
+mogdb=# REFRESH INCREMENTAL MATERIALIZED VIEW my_imv;
+```
+
+## Helpful Links
+
+[ALTER MATERIALIZED VIEW](11-ALTER-MATERIALIZED-VIEW), [CREATE INCREMENTAL MATERIALIZED VIEW](49.1-CREATE-INCREMENTAL-MATERIALIZED-VIEW), [CREATE MATERIALIZED VIEW](51-CREATE-MATERIALIZED-VIEW), [CREATE TABLE](60-CREATE-TABLE), [DROP MATERIALIZED VIEW](85-DROP-MATERIALIZED-VIEW), and [REFRESH MATERIALIZED VIEW](116-REFRESH-MATERIALIZED-VIEW)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/116-REFRESH-MATERIALIZED-VIEW.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/116-REFRESH-MATERIALIZED-VIEW.md
new file mode 100644
index 0000000000000000000000000000000000000000..863c7d878a53d7934d88ae6daec0cc5f6615ea08
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/116-REFRESH-MATERIALIZED-VIEW.md
@@ -0,0 +1,50 @@
+---
+title: REFRESH MATERIALIZED VIEW
+summary: REFRESH MATERIALIZED VIEW
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# REFRESH MATERIALIZED VIEW
+
+## Function
+
+**REFRESH MATERIALIZED VIEW** refreshes materialized views in full refresh mode.
+
+## Precautions
+
+- Full refreshing can be performed on both full and incremental materialized views.
+- To refresh a materialized view, you must have the SELECT permission on the base table.
+
+## Syntax
+
+```
+REFRESH MATERIALIZED VIEW mv_name;
+```
+
+## Parameter Description
+
+- **mv_name**
+
+  Name of the materialized view to be refreshed.
+
+## Examples
+
+```
+-- Create an ordinary table.
+mogdb=# CREATE TABLE my_table (c1 int, c2 int);
+-- Create a full materialized view.
+mogdb=# CREATE MATERIALIZED VIEW my_mv AS SELECT * FROM my_table;
+-- Create an incremental materialized view.
+mogdb=# CREATE INCREMENTAL MATERIALIZED VIEW my_imv AS SELECT * FROM my_table;
+-- Write data to the base table.
+mogdb=# INSERT INTO my_table VALUES(1,1),(2,2);
+-- Refresh the full materialized view my_mv.
+mogdb=# REFRESH MATERIALIZED VIEW my_mv;
+-- Fully refresh the incremental materialized view my_imv.
+mogdb=# REFRESH MATERIALIZED VIEW my_imv;
+```
+
+## Helpful Links
+
+[ALTER MATERIALIZED VIEW](11-ALTER-MATERIALIZED-VIEW), [CREATE INCREMENTAL MATERIALIZED VIEW](49.1-CREATE-INCREMENTAL-MATERIALIZED-VIEW), [CREATE MATERIALIZED VIEW](51-CREATE-MATERIALIZED-VIEW), [CREATE TABLE](60-CREATE-TABLE), [DROP MATERIALIZED VIEW](85-DROP-MATERIALIZED-VIEW), and [REFRESH INCREMENTAL MATERIALIZED VIEW](115.1-REFRESH-INCREMENTAL-MATERIALIZED-VIEW)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/117-REINDEX.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/117-REINDEX.md
new file mode 100644
index 0000000000000000000000000000000000000000..ebe50b3a6e1a50cb8aa9dd7b87fe88205a7e6d44
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/117-REINDEX.md
@@ -0,0 +1,143 @@
+---
+title: REINDEX
+summary: REINDEX
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# REINDEX
+
+## Function
+
+**REINDEX** rebuilds an index using the data stored in the index's table, replacing the old copy of the index.
+
+There are several scenarios in which **REINDEX** can be used:
+
+- An index has become corrupted, and no longer contains valid data.
+- An index has become "bloated", that is, it contains many empty or nearly-empty pages.
+- You have altered a storage parameter (such as a fill factor) for an index, and wish that the change takes full effect.
+- An index build with the **CONCURRENTLY** option failed, leaving an "invalid" index.
+
+## Precautions
+
+**REINDEX DATABASE** and **REINDEX SYSTEM** type cannot be performed in transaction blocks.
+
+## Syntax
+
+- Rebuild a general index.
+
+  ```ebnf+diagram
+  Reindex ::= REINDEX { INDEX [ CONCURRENTLY ] | [INTERNAL] TABLE | DATABASE | SYSTEM } name [ FORCE ];
+  ```
+
+- Rebuild an index partition.
+
+  ```ebnf+diagram
+  Reindex ::= REINDEX  { INDEX|  [INTERNAL] TABLE} name
+      PARTITION partition_name [ FORCE  ];
+  ```
+
+## Parameter Description
+
+- **INDEX**
+
+  Recreates the specified index.
+
+- **CONCURRENTLY** <a id = 'CONCURRENTLY'> </a>
+
+  Reindex index in a way that does not block DML statement execution.
+
+- **INTERNAL TABLE**
+
+  Recreates the Desc table index of a column-store table or Hadoop internal table. The TOAST table (if any) of the table is reindexed as well.
+
+- **TABLE**
+
+  Recreates all indexes of a specified table. If a table has a TOAST table, the table will also be reindexed. If an index in the table has been invalidated by running **alter unusable**, the index cannot be recreated.
+
+- **DATABASE**
+
+  Recreates all indexes within the current database.
+
+- **SYSTEM**
+
+  Recreates all indexes on system catalogs within the current database. Indexes on user tables are not processed.
+
+- **name**
+
+  Specifies the name of the index, table, or database whose index needs to be recreated. Tables and indexes can be schema-qualified.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  > **REINDEX DATABASE** and **SYSTEM** can create indexes for only the current database. Therefore, **name** must be the same as the current database name.
+
+- **FORCE**
+
+  Specifies an invalid option, which will be ignored.
+
+- **partition_name**
+
+    Specifies the name of the partition or index partition to be recreated.
+
+    Value range:
+
+  - If **REINDEX INDEX** is used, specify the name of an index partition.
+  - If it is **REINDEX TABLE**, specify the name of a partition.
+  - If it is **REINDEX INTERNAL TABLE**, specify the name of a partition in a column-store partitioned table.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> **REINDEX DATABASE** and **REINDEX SYSTEM** type cannot be performed in transaction blocks.
+
+## Examples
+
+```sql
+-- Create a row-store table tpcds.customer_t1 and create an index on the c_customer_sk column in the table.
+mogdb=# CREATE TABLE tpcds.customer_t1
+(
+    c_customer_sk             integer               not null,
+    c_customer_id             char(16)              not null,
+    c_current_cdemo_sk        integer                       ,
+    c_current_hdemo_sk        integer                       ,
+    c_current_addr_sk         integer                       ,
+    c_first_shipto_date_sk    integer                       ,
+    c_first_sales_date_sk     integer                       ,
+    c_salutation              char(10)                      ,
+    c_first_name              char(20)                      ,
+    c_last_name               char(30)                      ,
+    c_preferred_cust_flag     char(1)                       ,
+    c_birth_day               integer                       ,
+    c_birth_month             integer                       ,
+    c_birth_year              integer                       ,
+    c_birth_country           varchar(20)                   ,
+    c_login                   char(13)                      ,
+    c_email_address           char(50)                      ,
+    c_last_review_date        char(10)
+)
+WITH (orientation = row);
+
+mogdb=# CREATE INDEX tpcds_customer_index1 ON tpcds.customer_t1 (c_customer_sk);
+
+mogdb=# INSERT INTO tpcds.customer_t1 SELECT * FROM tpcds.customer WHERE c_customer_sk < 10;
+
+-- Rebuild a single index.
+mogdb=# REINDEX INDEX tpcds.tpcds_customer_index1;
+
+-- Rebuild all indexes in the tpcds.customer_t1 table:
+mogdb=# REINDEX TABLE tpcds.customer_t1;
+
+Delete the tpcds.customer_t1 table.
+mogdb=# DROP TABLE tpcds.customer_t1;
+```
+
+## Suggestions
+
+- INTERNAL TABLE
+
+  This scenario is used for fault recovery. You are not advised to perform concurrent operations.
+
+- DATABASE
+
+  You can not reindex a database in a transaction.
+
+- SYSTEM
+
+  You can not reindex system catalogs in transactions.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/118-RELEASE-SAVEPOINT.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/118-RELEASE-SAVEPOINT.md
new file mode 100644
index 0000000000000000000000000000000000000000..c4bad2ee6032693837ec24b7689ae777f86936e9
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/118-RELEASE-SAVEPOINT.md
@@ -0,0 +1,69 @@
+---
+title: RELEASE SAVEPOINT
+summary: RELEASE SAVEPOINT
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# RELEASE SAVEPOINT
+
+## Function
+
+**RELEASE SAVEPOINT** destroys a savepoint previously defined in the current transaction.
+
+Destroying a savepoint makes it unavailable as a rollback point, but it has no other user visible behavior. It does not undo the effects of statements executed after the savepoint was established. To do that, use **ROLLBACK TO SAVEPOINT**. Destroying a savepoint when it is no longer needed allows the system to reclaim some resources earlier than transaction end.
+
+**RELEASE SAVEPOINT** also destroys all savepoints that were established after the named savepoint was established.
+
+## Precautions
+
+- Specifying a savepoint name that was not previously defined causes an error.
+- It is not possible to release a savepoint when the transaction is in an aborted state.
+- If multiple savepoints have the same name, only the one that was most recently defined is released.
+
+## Syntax
+
+```ebnf+diagram
+ReleaseSavepoint ::= RELEASE [ SAVEPOINT ] savepoint_name;
+```
+
+## Parameter Description
+
+**savepoint_name**
+
+Specifies the name of the savepoint you want to destroy.
+
+## Examples
+
+```sql
+-- Create a table.
+mogdb=# CREATE TABLE tpcds.table1(a int);
+
+-- Start a transaction.
+mogdb=# START TRANSACTION;
+
+-- Insert data.
+mogdb=# INSERT INTO tpcds.table1 VALUES (3);
+
+-- Establish a savepoint.
+mogdb=# SAVEPOINT my_savepoint;
+
+-- Insert data.
+mogdb=# INSERT INTO tpcds.table1 VALUES (4);
+
+-- Delete the savepoint.
+mogdb=# RELEASE SAVEPOINT my_savepoint;
+
+-- Commit the transaction.
+mogdb=# COMMIT;
+
+-- Query the table content, which should contain both 3 and 4.
+mogdb=# SELECT * FROM tpcds.table1;
+
+-- Delete the table.
+mogdb=# DROP TABLE tpcds.table1;
+```
+
+## Helpful Links
+
+[SAVEPOINT](124-SAVEPOINT) and [ROLLBACK TO SAVEPOINT](123-ROLLBACK-TO-SAVEPOINT)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/119-RESET.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/119-RESET.md
new file mode 100644
index 0000000000000000000000000000000000000000..196972730c267dc0a8e9ae9badcde95234afb8d8
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/119-RESET.md
@@ -0,0 +1,68 @@
+---
+title: RESET
+summary: RESET
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# RESET
+
+## Function
+
+**RESET** restores run-time parameters to their default values. The default values are parameter default values complied in the **postgresql.conf** configuration file.
+
+**RESET** is an alternative spelling for:
+
+SET configuration_parameter TO DEFAULT
+
+## Precautions
+
+**RESET** and **SET** have the same transaction behavior. Their impact will be rolled back.
+
+## Syntax
+
+```ebnf+diagram
+Reset ::= RESET {configuration_parameter | CURRENT_SCHEMA | TIME ZONE | TRANSACTION ISOLATION LEVEL | SESSION AUTHORIZATION | ALL };
+```
+
+## Parameter Description
+
+- **configuration_parameter**
+
+  Specifies the name of a settable run-time parameter.
+
+  Value range: run-time parameters. You can view them by running the **SHOW ALL** statement.
+
+- **CURRENT_SCHEMA**
+
+  Specifies the current schema.
+
+- **TIME ZONE**
+
+  Specifies the time zone.
+
+- **TRANSACTION ISOLATION LEVEL**
+
+  Specifies the transaction isolation level.
+
+- **SESSION AUTHORIZATION**
+
+  Specifies the session authorization.
+
+- **ALL**
+
+  Resets all settable run-time parameters to default values.
+
+## Examples
+
+```sql
+-- Reset timezone to the default value.
+mogdb=# RESET timezone;
+
+-- Set all parameters to their default values.
+mogdb=# RESET ALL;
+```
+
+## Helpful Links
+
+[SET](127-SET) and [SHOW](132-SHOW)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/12-ALTER-ROLE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/12-ALTER-ROLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..63c10283748f4e5a0526945bb9a4e558d302fec1
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/12-ALTER-ROLE.md
@@ -0,0 +1,120 @@
+---
+title: ALTER ROLE
+summary: ALTER ROLE
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER ROLE
+
+## Function
+
+**ALTER ROLE** modifies role attributes.
+
+## Precautions
+
+None
+
+## Syntax
+
+- Modify the permissions of a role.
+
+  ```ebnf+diagram
+  AlterRole ::= ALTER ROLE role_name [ [ WITH ] option [ ... ] ];
+  ```
+
+  The **option** clause for granting permissions is as follows:
+
+  ```ebnf+diagram
+  option ::= {CREATEDB | NOCREATEDB}
+      | {CREATEROLE | NOCREATEROLE}
+      | {INHERIT | NOINHERIT}
+      | {AUDITADMIN | NOAUDITADMIN}
+      | {SYSADMIN | NOSYSADMIN}
+      | {USEFT | NOUSEFT}
+      | {LOGIN | NOLOGIN}
+      | {REPLICATION | NOREPLICATION}
+      | {INDEPENDENT | NOINDEPENDENT}
+      | {VCADMIN | NOVCADMIN}
+      | CONNECTION LIMIT connlimit
+      | [ ENCRYPTED | UNENCRYPTED ] PASSWORD 'password' [EXPIRED]
+      | [ ENCRYPTED | UNENCRYPTED ] IDENTIFIED BY 'password' [ REPLACE 'old_password' | EXPIRED ]
+      | [ ENCRYPTED | UNENCRYPTED ] PASSWORD { 'password' | DISABLE | EXPIRED }
+      | [ ENCRYPTED | UNENCRYPTED ] IDENTIFIED BY { 'password' [ REPLACE 'old_password' ] | DISABLE }
+      | VALID BEGIN 'timestamp'
+      | VALID UNTIL 'timestamp'
+      | RESOURCE POOL 'respool'
+      | PERM SPACE 'spacelimit'
+      | ACCOUNT { LOCK | UNLOCK }
+      | PGUSER
+  ```
+
+- Rename a role.
+
+  ```ebnf+diagram
+  AlterRole ::= ALTER ROLE role_name
+      RENAME TO new_name;
+  ```
+
+- Set parameters for a role.
+
+  ```ebnf+diagram
+  AlterRole ::= ALTER ROLE role_name [ IN DATABASE database_name ]
+      SET configuration_parameter {{ TO | = } { value | DEFAULT } | FROM CURRENT};
+  ```
+
+- Reset parameters for a role.
+
+  ```ebnf+diagram
+  AlterRole ::= ALTER ROLE role_name
+      [ IN DATABASE database_name ] RESET {configuration_parameter|ALL};
+  ```
+
+## Parameter Description
+
+- **role_name**
+
+  Specifies a role name.
+
+  Value range: an existing username
+
+- **IN DATABASE database_name**
+
+  Modifies the parameters of a role in a specified database.
+
+- **SET configuration_parameter**
+
+  Sets parameters for a role. Session parameters modified by **ALTER ROLE** apply to a specified role and take effect in the next session triggered by the role.
+
+  Value range:
+
+  For details about the values of **configuration_parameter** and **value**, see **SET**.
+
+  **DEFAULT**: clears the value of **configuration_parameter**. **configuration_parameter** will inherit the default value of the new session generated for the role.
+
+  **FROM CURRENT**: uses the value of **configuration_parameter** of the current session.
+
+- **RESET configuration_parameter/ALL**
+
+  Clears the value of **configuration_parameter**. The statement has the same effect as that of **SET configuration_parameter TO DEFAULT**.
+
+  Value range: **ALL** indicates that the values of all parameters are cleared.
+
+- **ACCOUNT LOCK | ACCOUNT UNLOCK**
+
+  - **ACCOUNT LOCK**: locks an account to forbid login to databases.
+  - **ACCOUNT UNLOCK**: unlocks an account to allow login to databases.
+
+- **PGUSER**
+
+  In the current version, the **PGUSER** attribute of a role cannot be modified.
+
+For details about other parameters, see **Parameter Description** in [CREATE ROLE](54-CREATE-ROLE).
+
+## Example
+
+See **Example** in [CREATE ROLE](54-CREATE-ROLE).
+
+## Helpful Links
+
+[CREATE ROLE](54-CREATE-ROLE)，[DROP ROLE](89-DROP-ROLE)，[SET](127-SET)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/120-REVOKE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/120-REVOKE.md
new file mode 100644
index 0000000000000000000000000000000000000000..f57de0ef8f5d65093f4811d5a6044242ddce8add
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/120-REVOKE.md
@@ -0,0 +1,248 @@
+---
+title: REVOKE
+summary: REVOKE
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# REVOKE
+
+## Function
+
+**REVOKE** revokes permissions from one or more roles.
+
+## Precautions
+
+If a non-owner user of an object attempts to **REVOKE** permission on the object, the statement is executed based on the following rules:
+
+- If the user has no permissions whatsoever on the object, the statement will fail outright.
+- If an authorized user has some permissions, only the permissions with authorization options are revoked.
+- If the authorized user does not have the authorization option, the **REVOKE ALL PRIVILEGES** form will issue an error message. For other forms of statements, if the permission specified in the statement does not have the corresponding authorization option, the statement will issue a warning.
+- Do not perform **REVOKE** to a table partition. Otherwise, an alarm will be generated.
+
+## Syntax
+
+- Revoke the permission on a specified table or view.
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+      { { SELECT | INSERT | UPDATE | DELETE | TRUNCATE | REFERENCES | ALTER | DROP | COMMENT | INDEX | VACUUM }[, ...]
+      | ALL [ PRIVILEGES ] }
+      ON { [ TABLE ] table_name [, ...]
+         | ALL TABLES IN SCHEMA schema_name [, ...] }
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT ];
+  ```
+
+- Revoke the permission on a specified field in a table.
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+      { {{ SELECT | INSERT | UPDATE | REFERENCES | COMMENT } ( column_name [, ...] )}[, ...]
+      | ALL [ PRIVILEGES ] ( column_name [, ...] ) }
+      ON [ TABLE ] table_name [, ...]
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT ];
+  ```
+
+- Revoke the permission on a specified sequence.
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+      { { SELECT | UPDATE | ALTER | DROP | COMMENT }[, ...]
+      | ALL [ PRIVILEGES ] }
+      ON { [ SEQUENCE ] sequence_name [, ...]
+         | ALL SEQUENCES IN SCHEMA schema_name [, ...] }
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT ];
+  ```
+
+- Revoke the permission on a specified database.
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+      { { CREATE | CONNECT | TEMPORARY | TEMP | ALTER | DROP | COMMENT } [, ...]
+      | ALL [ PRIVILEGES ] }
+      ON DATABASE database_name [, ...]
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT ];
+  ```
+
+- Revoke the permission on a specified domain.
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+      { USAGE | ALL [ PRIVILEGES ] }
+      ON DOMAIN domain_name [, ...]
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT ];
+  ```
+
+- Revoke the specified CMK permission.
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+      { { USAGE | DROP } [, ...] | ALL [PRIVILEGES] }
+      ON CLIENT_MASTER_KEYS client_master_keys_name [, ...]
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT ];
+  ```
+
+- Revoke the specified CEK permission.
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+      { { USAGE | DROP } [, ...] | ALL [PRIVILEGES]}
+      ON COLUMN_ENCRYPTION_KEYS column_encryption_keys_name [, ...]
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT ];
+  ```
+
+- Revoke the permission on a specified directory.
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+      { { READ | WRITE  ALTER |DROP } [, ...] | ALL [ PRIVILEGES ] }
+      ON DIRECTORY directory_name [, ...]
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT ];
+  ```
+
+- Revoke the permission on a specified external data source.
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+     { USAGE | ALL [ PRIVILEGES ] }
+      ON FOREIGN DATA WRAPPER fdw_name [, ...]
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT ];
+  ```
+
+- Revoke the permission on a specified external server.
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+      { { USAGE | ALTER | DROP | COMMENT } [, ...] | ALL [ PRIVILEGES ] }
+      ON FOREIGN SERVER server_name [, ...]
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT ];
+  ```
+
+- Revoke the permission on a specified function.
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+      { { EXECUTE | ALTER | DROP | COMMENT } [, ...] | ALL [ PRIVILEGES ] }
+      ON { FUNCTION {function_name ( [ {[ argmode ] [ arg_name ] arg_type} [, ...] ] )} [, ...]
+         | ALL FUNCTIONS IN SCHEMA schema_name [, ...] }
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT ];
+  ```
+
+- Revoke the permission on a specified procedural language.
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+     { USAGE | ALL [ PRIVILEGES ] }
+      ON LANGUAGE lang_name [, ...]
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT ];
+  ```
+
+- Revoke the permission on a specified large object.
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+      { { SELECT | UPDATE } [, ...] | ALL [ PRIVILEGES ] }
+      ON LARGE OBJECT loid [, ...]
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT ];
+  ```
+
+- Revoke the permission on a specified schema.
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+      { { CREATE | USAGE | ALTER | DROP | COMMENT } [, ...] | ALL [ PRIVILEGES ] }
+      ON SCHEMA schema_name [, ...]
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT ];
+  ```
+
+- Revoke the permission on a specified tablespace.
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+      { { CREATE | ALTER | DROP | COMMENT } [, ...] | ALL [ PRIVILEGES ] }
+      ON TABLESPACE tablespace_name [, ...]
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT ];
+  ```
+
+- Revoke the permission on a specified type.
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+     { { USAGE | ALTER | DROP | COMMENT } [, ...] | ALL [ PRIVILEGES ] }
+      ON TYPE type_name [, ...]
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT ];
+  ```
+
+- Revoke the permission on a data source object.
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+     { USAGE | ALL [PRIVILEGES] }
+      ON DATA SOURCE src_name [, ...]
+      FROM {[GROUP] role_name | PUBLIC} [, ...]
+     [ CASCADE | RESTRICT ];
+  ```
+
+- Revoke the permission on a package object.
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+     { { EXECUTE | ALTER | DROP | COMMENT } [, ...] | ALL [PRIVILEGES] }
+     ON PACKAGE package_name [, ...]
+     FROM {[GROUP] role_name | PUBLIC} [, ...]
+     [ CASCADE | RESTRICT ];
+  ```
+
+- Revoke permissions from a role.
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ ADMIN OPTION FOR ]
+      role_name [, ...] FROM role_name [, ...]
+      [ CASCADE | RESTRICT ];
+  ```
+
+- Revoke the sysadmin permission from a role.
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE ALL { PRIVILEGES | PRIVILEGE } FROM role_name;
+  ```
+
+## Parameter Description
+
+The keyword **PUBLIC** indicates an implicitly defined group that has all roles.
+
+For details about the permission types and parameters, see **Parameter Description** in GRANT.
+
+Permissions of a role include the permissions directly granted to the role, permissions inherited from the parent role, and permissions granted to **PUBLIC**. Therefore, revoking the **SELECT** permission for an object from **PUBLIC** does not necessarily mean that the **SELECT** permission for the object has been revoked from all roles, because the **SELECT** permission directly granted to roles and inherited from parent roles remains. Similarly, if the **SELECT** permission is revoked from a user but is not revoked from **PUBLIC**, the user can still run the **SELECT** statement.
+
+If **GRANT OPTION FOR** is specified, the permission cannot be granted to others, but permission itself is not revoked.
+
+If user A holds the **UPDATE** permissions on a table and the **WITH GRANT OPTION** and has granted them to user B, the permissions that user B holds are called dependent permissions. When user A's permission or grant option is revoked, **CASCADE** must be specified to revoke all dependent permissions.
+
+A user can only revoke permissions that were granted directly by that user. For example, if user A has granted permission with grant option (**WITH ADMIN OPTION**) to user B, and user B has in turn granted it to user C, then user A cannot revoke the permission directly from C. However, user A can revoke the grant option held by user B and use **CASCADE**. In this way, the permission of user C is automatically revoked. For another example, if both user A and user B have granted the same permission to C, A can revoke his own grant but not B's grant, so C will still effectively have the permission.
+
+If the role executing **REVOKE** holds permissions indirectly via more than one role membership path, it is unspecified which containing role will be used to execute the statement. In such cases, it is best practice to use **SET ROLE** to become the specific role you want to do the **REVOKE** as, and then execute **REVOKE**. Failure to do so may lead to deleting permissions not intended to delete, or not deleting any permissions at all.
+
+## Examples
+
+See **Examples** in GRANT.
+
+## Helpful Links
+
+[GRANT](108-GRANT)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/121-ROLLBACK.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/121-ROLLBACK.md
new file mode 100644
index 0000000000000000000000000000000000000000..709949893bf5faf0dd610a6a8177bea49a32c9c4
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/121-ROLLBACK.md
@@ -0,0 +1,44 @@
+---
+title: ROLLBACK
+summary: ROLLBACK
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# ROLLBACK
+
+## Function
+
+**ROLLBACK** rolls back the current transaction and backs out all updates in the transaction.
+
+**ROLLBACK** backs out of all changes that a transaction makes to a database if the transaction fails to be executed due to a fault.
+
+## Precautions
+
+If a **ROLLBACK** statement is executed out of a transaction, no error occurs, but a notice is displayed.
+
+## Syntax
+
+```ebnf+diagram
+Rollback ::= ROLLBACK [ WORK | TRANSACTION ];
+```
+
+## Parameter Description
+
+**WORK | TRANSACTION**
+
+Specifies the optional keyword. that more clearly illustrates the syntax.
+
+## Example
+
+```sql
+-- Start a transaction.
+mogdb=# START TRANSACTION;
+
+-- Back out all changes.
+mogdb=# ROLLBACK;
+```
+
+## Helpful Links
+
+[COMMIT | END](39-COMMIT-END)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/122-ROLLBACK-PREPARED.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/122-ROLLBACK-PREPARED.md
new file mode 100644
index 0000000000000000000000000000000000000000..59ce4042c11f3964c912258e4024585b0dfc88a5
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/122-ROLLBACK-PREPARED.md
@@ -0,0 +1,34 @@
+---
+title: ROLLBACK PREPARED
+summary: ROLLBACK PREPARED
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# ROLLBACK PREPARED
+
+## Function
+
+**ROLLBACK PREPARED** cancels a transaction ready for two-phase committing.
+
+## Precautions
+
+- The function is only available in maintenance mode (when GUC parameter **xc_maintenance_mode** is **on**). Exercise caution when enabling the mode. It is used by maintenance engineers for troubleshooting. Common users should not use the mode.
+- Only the user that initiates a transaction or the system administrator can roll back the transaction.
+- The transaction function is maintained automatically by the database, and should be not visible to users.
+
+## Syntax
+
+```ebnf+diagram
+RollbackPrepared ::= ROLLBACK PREPARED transaction_id ;
+```
+
+## Parameter Description
+
+**transaction_id**
+
+Specifies the identifier of the transaction to be committed. The identifier must be different from those for current prepared transactions.
+
+## Helpful Links
+
+[COMMIT PREPARED](40-COMMIT-PREPARED) and [PREPARE TRANSACTION](114-PREPARE-TRANSACTION)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/123-ROLLBACK-TO-SAVEPOINT.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/123-ROLLBACK-TO-SAVEPOINT.md
new file mode 100644
index 0000000000000000000000000000000000000000..e13be9393b313fbdf381e1379cd7e1236f8443d2
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/123-ROLLBACK-TO-SAVEPOINT.md
@@ -0,0 +1,59 @@
+---
+title: ROLLBACK TO SAVEPOINT
+summary: ROLLBACK TO SAVEPOINT
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# ROLLBACK TO SAVEPOINT
+
+## Function
+
+**ROLLBACK TO SAVEPOINT** rolls back to a savepoint. It implicitly destroys all savepoints that were established after the named savepoint.
+
+Rolls back all statements that were executed after the savepoint was established. The savepoint remains valid and can be rolled back to again later, if needed.
+
+## Precautions
+
+- Specifying a savepoint name that has not been established is an error.
+- Cursors have somewhat non-transactional behavior with respect to savepoints. Any cursor that is opened inside a savepoint will be closed when the savepoint is rolled back. If a previously opened cursor is affected by a **FETCH** or **MOVE** statement inside a savepoint that is later rolled back, the cursor remains at the position that **FETCH** left it pointing to (that is, the cursor motion caused by **FETCH** is not rolled back). Closing a cursor is not undone by rolling back, either. A cursor whose execution causes a transaction to abort is put in a cannot-execute state, so while the transaction can be restored using **ROLLBACK TO SAVEPOINT**, the cursor can no longer be used.
+- Use **ROLLBACK TO SAVEPOINT** to roll back to a savepoint. Use **RELEASE SAVEPOINT** to destroy a savepoint but keep the effects of the statements executed after the savepoint was established.
+
+## Syntax
+
+```ebnf+diagram
+RollbackToSavepoint ::= ROLLBACK [ WORK | TRANSACTION ] TO [ SAVEPOINT ] savepoint_name;
+```
+
+## Parameter Description
+
+savepoint_name
+
+Rolls back to a savepoint.
+
+## Examples
+
+```sql
+-- Undo the effects of the statements executed after my_savepoint was established:
+mogdb=# START TRANSACTION;
+mogdb=# SAVEPOINT my_savepoint;
+mogdb=# ROLLBACK TO SAVEPOINT my_savepoint;
+-- Cursor positions are not affected by savepoint rollback.
+mogdb=# DECLARE foo CURSOR FOR SELECT 1 UNION SELECT 2;
+mogdb=# SAVEPOINT foo;
+mogdb=# FETCH 1 FROM foo;
+ ?column?
+----------
+        1
+mogdb=# ROLLBACK TO SAVEPOINT foo;
+mogdb=# FETCH 1 FROM foo;
+ ?column?
+----------
+        2
+mogdb=# RELEASE SAVEPOINT my_savepoint;
+mogdb=# COMMIT;
+```
+
+## Helpful Links
+
+[SAVEPOINT](124-SAVEPOINT) and [RELEASE SAVEPOINT](118-RELEASE-SAVEPOINT)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/124-SAVEPOINT.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/124-SAVEPOINT.md
new file mode 100644
index 0000000000000000000000000000000000000000..d3aff09fe5bdfac8d977e049f1ab29f6f57002c7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/124-SAVEPOINT.md
@@ -0,0 +1,98 @@
+---
+title: SAVEPOINT
+summary: SAVEPOINT
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# SAVEPOINT
+
+## Function
+
+**SAVEPOINT** establishes a new savepoint within the current transaction.
+
+A savepoint is a special mark inside a transaction. It allows all statements executed following its establishment to be rolled back, restoring the transaction state to what it was at the time of the savepoint.
+
+## Precautions
+
+- Use **ROLLBACK TO SAVEPOINT** to roll back to a savepoint. Use **RELEASE SAVEPOINT** to destroy a savepoint but keep the effects of the statements executed after the savepoint was established.
+- Savepoints can only be established when inside a transaction block. Multiple savepoints can be defined in a transaction.
+- In the case of an unexpected termination of a thread or process caused by a node or connection failure, or of an error caused by the inconsistency between source and destination table structures in a COPY FROM operation, the transaction cannot be rolled back to the established savepoint. Instead, the entire transaction will be rolled back.
+- According to the SQL standard, when a savepoint with the same name is created, the previous savepoint with the same name is automatically deleted. In MogDB, the old savepoint is retained, but only the latest one is used during rollback or release. Releasing the newer savepoint with **RELEASE SAVEPOINT** will cause the older one to again become accessible to **ROLLBACK TO SAVEPOINT** and **RELEASE SAVEPOINT**. In addition, **SAVEPOINT** fully complies with the SQL standard.
+
+## Syntax
+
+```ebnf+diagram
+Savepoint ::= SAVEPOINT savepoint_name;
+```
+
+## Parameter Description
+
+savepoint_name
+
+Specifies the name of the new savepoint.
+
+## Examples
+
+```sql
+-- Create a table.
+mogdb=# CREATE TABLE table1(a int);
+
+-- Start a transaction.
+mogdb=# START TRANSACTION;
+
+-- Insert data.
+mogdb=# INSERT INTO table1 VALUES (1);
+
+-- Create a savepoint.
+mogdb=# SAVEPOINT my_savepoint;
+
+-- Insert data.
+mogdb=# INSERT INTO table1 VALUES (2);
+
+-- Roll back a savepoint.
+mogdb=# ROLLBACK TO SAVEPOINT my_savepoint;
+
+-- Insert data.
+mogdb=# INSERT INTO table1 VALUES (3);
+
+-- Commit a transaction.
+mogdb=# COMMIT;
+
+-- Query the content of the table. You can see 1 and 3 at the same time, but cannot see 2 because 2 is rolled back.
+mogdb=# SELECT * FROM table1;
+
+-- Delete the table.
+mogdb=# DROP TABLE table1;
+
+-- Create a table.
+mogdb=# CREATE TABLE table2(a int);
+
+-- Start a transaction.
+mogdb=# START TRANSACTION;
+
+-- Insert data.
+mogdb=# INSERT INTO table2 VALUES (3);
+
+-- Create a savepoint.
+mogdb=# SAVEPOINT my_savepoint;
+
+-- Insert data.
+mogdb=# INSERT INTO table2 VALUES (4);
+
+-- Roll back a savepoint.
+mogdb=# RELEASE SAVEPOINT my_savepoint;
+
+-- Commit a transaction.
+mogdb=# COMMIT;
+
+-- Query the table content. You can see 3 and 4 at the same time.
+mogdb=# SELECT * FROM table2;
+
+-- Delete a table.
+mogdb=# DROP TABLE table2;
+```
+
+## Helpful Links
+
+[RELEASE SAVEPOINT](118-RELEASE-SAVEPOINT) and [ROLLBACK TO SAVEPOINT](123-ROLLBACK-TO-SAVEPOINT)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/125-SELECT.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/125-SELECT.md
new file mode 100644
index 0000000000000000000000000000000000000000..47238e79a3d008011430268d7485833fd6d6a024
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/125-SELECT.md
@@ -0,0 +1,642 @@
+---
+title: SELECT
+summary: SELECT
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# SELECT
+
+## Function
+
+**SELECT** retrieves data from a table or view.
+
+Serving as an overlaid filter for a database table, **SELECT** filters required data from the table using SQL keywords.
+
+## Precautions
+
+- You must have the **SELECT** permission on each field used in the SELECT statement.
+- **UPDATE** permission is required when **FOR UPDATE** or **FOR SHARE** is used.
+
+## Syntax
+
+- Query data.
+
+  ```ebnf+diagram
+  Select ::= [ WITH [ RECURSIVE ] with_query [, ...] ]
+  SELECT [/*+ plan_hint */] [ ALL | DISTINCT [ ON ( expression [, ...] ) ] ]
+  { * | {expression [ [ AS ] output_name ]} [, ...] }
+  [ FROM from_item [, ...] ]
+  [ WHERE condition ]
+  [ GROUP BY grouping_element [, ...] ]
+  [ HAVING condition [, ...] ]
+  [ WINDOW {window_name AS ( window_definition )} [, ...] ]
+  [ { UNION | INTERSECT | EXCEPT | MINUS } [ ALL | DISTINCT ] select ]
+  [ ORDER BY {expression [ [ ASC | DESC | USING operator ] | nlssort_expression_clause ] [ NULLS { FIRST | LAST } ]} [, ...] ]
+  [ LIMIT { [offset,] count | ALL } ]
+  [ OFFSET start [ ROW | ROWS ] ]
+  [ FETCH { FIRST | NEXT } [ count ] { ROW | ROWS } ONLY ]
+  [ {FOR { UPDATE | SHARE } [ OF table_name [, ...] ] [ NOWAIT ]} [...] ];
+  ```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** In condition and expression, you can use the aliases of expressions in **targetlist** in compliance with the following rules:
+>
+> - Reference only within the same level. - Only reference aliases in **targetlist**.
+> - Reference a prior expression in a subsequent expression.
+> - The **volatile** function cannot be used.
+> - The **Window** function cannot be used.
+> - Aliases cannot be referenced in the **join on** condition.
+> - An error is reported if **targetlist** contains multiple referenced aliases.
+
+- The subquery **with_query** is as follows:
+
+  ```ebnf+diagram
+  with_query ::= with_query_name [ ( column_name [, ...] ) ]
+      AS ( {select | values | insert | update | delete} )
+  ```
+
+- The specified query source **from_item** is as follows:
+
+  ```ebnf+diagram
+  from_item ::= {[ ONLY ] table_name [ * ] [ partition_clause ] [ [ AS ] alias [ ( column_alias [, ...] ) ] ]
+  [ TABLESAMPLE sampling_method ( argument [, ...] ) [ REPEATABLE ( seed ) ] ]
+  [TIMECAPSULE {TIMESTAMP|CSN} expression]
+  |( select ) [ AS ] alias [ ( column_alias [, ...] ) ]
+  |with_query_name [ [ AS ] alias [ ( column_alias [, ...] ) ] ]
+  |function_name ( [ argument [, ...] ] ) [ AS ] alias [ ( column_alias [, ...] | column_definition [, ...] ) ]
+  |function_name ( [ argument [, ...] ] ) AS ( column_definition [, ...] )
+  |from_item [ NATURAL ] join_type from_item [ ON join_condition | USING ( join_column [, ...] ) ]}
+  ```
+
+- The **group** clause is as follows:
+
+  ```ebnf+diagram
+    group ::= {
+    expression
+    | ( expression [, '...'] )
+    | ROLLUP ( { expression | ( expression [, '...'] ) } [, '...'] )
+    | CUBE ( { expression | ( expression [, '...'] ) } [, '...'] )
+    | GROUPING SETS ( grouping_element [, '...'] )};
+  ```
+
+- The specified partition **partition_clause** is as follows:
+
+  ```ebnf+diagram
+  partition_clause ::= PARTITION { ( partition_name ) |
+          FOR (  partition_value [, ...] ) };
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The specified partition applies only to ordinary tables.
+
+- The sorting order **nlssort_expression_clause** is as follows:
+
+  ```ebnf+diagram
+  nlssort_expression_clause ::= NLSSORT ( column_name, ' NLS_SORT = { SCHINESE_PINYIN_M | generic_m_ci } ' );
+  ```
+
+- Simplified query syntax, equivalent to **select \* from table_name**.
+
+  ```ebnf+diagram
+  SimpleSelect ::= TABLE { ONLY {(table_name)| table_name} | table_name [ * ]};
+  ```
+
+## Parameter Description
+
+- **WITH [ RECURSIVE ] with_query [, …]**
+
+    Specifies one or more subqueries that can be referenced by name in the main query, which is equivalent to a temporary table.
+
+    If **RECURSIVE** is specified, it allows a **SELECT** subquery to reference itself by name.
+
+    The detailed format of **with_query** is as follows: **with_query_name [ (column_name [, …])] AS ({select | values | insert | update | delete})**
+
+  - **with_query_name** specifies the name of the result set generated by a subquery. Such names can be used to access the result sets of subqueries in a query.
+  - **column_name** specifies the column name displayed in the subquery result set.
+  - Each subquery can be a **SELECT**, **VALUES**, **INSERT**, **UPDATE** or **DELETE** statement.
+
+- **plan_hint** clause
+
+  Follows the **SELECT** keyword in the /\*+&lt;*Plan hint*&gt; */ format. It is used to optimize the plan of a **SELECT** statement block. For details, see [Hint-based Tuning](9-hint-based-tuning). In each statement, only the first /\***+** _plan_hint _\*/ comment block takes effect as a hint. Multiple hints can be written.
+
+- **ALL**
+
+  Specifies that all rows that meet the conditions are returned. This is the default behavior and can be omitted.
+
+- **DISTINCT [ ON ( expression [, …] ) ]**
+
+  Removes all duplicate rows from the **SELECT** result set so one row is kept from each group of duplicates.
+
+  Retains only the first row in the set of rows that have the same result calculated on the given expression.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** **DISTINCT ON** expression is explained with the same rule of **ORDER BY**. Unless you use **ORDER BY** to guarantee that the required row appears first, you cannot know what the first row is.
+
+- **SELECT list**
+
+  Specifies the name of a column in the table to be queried. The value can be a part of the column name or all of the column names. The wildcard (*) is used to represent the column name.
+
+  You may use the **AS output_name** clause to give an alias for an output column. The alias is used for the displaying of the output column. The name, value, and type keywords can be used as column aliases.
+
+  Column names can be expressed in the following formats:
+
+  - Manually input column names which are spaced using commas (,).
+  - Columns computed in the **FROM** clause.
+
+- **FROM clause**
+
+    Specifies one or more source tables for **SELECT**.
+
+    The **FROM** clause can contain the following elements:
+
+  - table_name
+
+    Specifies the name of a table or view. The schema name can be added before the table name or view name, for example, schema_name.table_name.
+
+  - alias
+
+    Gives a temporary alias to a table to facilitate the quotation by other queries.
+
+    An alias is used for brevity or to eliminate ambiguity for self-joins. If an alias is provided, it completely hides the actual name of the table.
+
+  - TABLESAMPLE *sampling_method* ( *argument* [, …] ) [ REPEATABLE ( *seed* ) ]
+
+    The **TABLESAMPLE** clause following *table_name* specifies that the specified *sampling_method* should be used to retrieve the subset of rows in the table.
+
+    The optional **REPEATABLE** clause specifies the number of seeds used to generate random numbers in the sampling method. The seed value can be any non-null constant value. If the table was not changed during the query, the two queries having the same seed and *argument* values will select the same sampling in this table. However, different seed values usually generate different samples. If **REPEATABLE** is not specified, a new random sample will be selected for each query based on the seed generated by the system.
+
+  - TIMECAPSULE { TIMESTAMP | CSN } expression
+
+    Queries the table data of a specified CSN or at a specified time point.
+
+    Currently, the following tables do not support flashback query: system catalogs, column-store tables, memory tables, DFS tables, global temporary tables, local temporary tables, unlogged tables, partitioned tables, views, sequence tables, Hbkt tables, shared tables, inherited tables, and tables with **PARTIAL CLUSTER KEY** constraints.
+
+    - TIMECAPSULE TIMESTAMP
+
+        Searches for the result set of a specified time point based on the date as the flashback query flag. *date* must be a valid past timestamp
+
+    - TIMECAPSULE CSN
+
+        Searches for the result set of a specified CSN point based on the CSN flashback of the table as the flashback query flag. The CSN can be obtained from **snpcsn** recorded in **gs_txn_snapshot**.
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+    >
+    > - A flashback query cannot span statements that affect the table structure or physical storage. Otherwise, an error is reported. That is, between the flashback point and the current point, if a statement (**DDL**, **DCL**, or **VACUUM FULL**) that modifies the table structure or affects physical storage has been executed, the flashback fails and the error message "ERROR: The table definition of T1 has been changed." is displayed.
+    > - When the flashback point is too old, the old version cannot be obtained because the flashback version is recycled. As a result, the flashback fails and the error message "Restore point too old" is displayed. You can set **version_retention_age** and **vacuum_defer_cleanup_age** to the same value to configure the retention period of the flashback function in the earlier version. The value ranges from 0 to 1000000. The value **0** indicates that **VACUUM** does not delay clearing invalid row-store records.
+    > - The flashback point is specified by time. The maximum difference between the flashback point and the actual time is 3 seconds.
+
+  - column_alias
+
+    Specifies the column alias.
+
+  - PARTITION
+
+    Queries data in the specified partition in a partitioned table.
+
+  - partition_name
+
+    Specifies the name of a partition.
+
+  - partition_value
+
+    Specifies the value of the specified partition key. If there are many partition keys, use the **PARTITION FOR** clause to specify the value of the only partition key you want to use.
+
+  - subquery
+
+    Performs a subquery in the **FROM** clause. A temporary table is created to save subquery results.
+
+  - with_query_name
+
+    Specifies that the **WITH** clause can also be used as the source of the **FROM** clause and can be referenced by the name of the **WITH** query.
+
+  - function_name
+
+    Function name. Function calls can appear in the **FROM** clause.
+
+  - join_type
+
+    The options are as follows:
+
+    - [ INNER ] JOIN
+
+        A **JOIN** clause combines two **FROM** items. You can use parentheses to determine the order of nesting. In the absence of parentheses, **JOIN** nests left-to-right.
+
+        In any case, **JOIN** binds more tightly than the commas separating **FROM** items.
+
+    - LEFT [ OUTER ] JOIN
+
+        Returns all rows that meet join conditions in the Cartesian product, plus those rows that do not match the right table rows in the left table by join conditions. This left-hand row is extended to the full width of the joined table by inserting **NULL** values for the right-hand columns. Note that only the **JOIN** clause's own condition is considered while the system decides which rows have matches. Outer conditions are applied afterward.
+
+    - RIGHT [ OUTER ] JOIN
+
+        Returns all the joined rows, plus one row for each unmatched right-hand row (extended with **NULL** on the left).
+
+        This is just a notational convenience, since you could convert it to a **LEFT OUTER JOIN** by switching the left and right inputs.
+
+    - FULL [ OUTER ] JOIN
+
+        Returns all the joined rows, pluses one row for each unmatched left-hand row (extended with **NULL** on the right), and pluses one row for each unmatched right-hand row (extended with **NULL** on the left).
+
+    - CROSS JOIN
+
+        Is equivalent to **INNER JOIN ON (TRUE)**, which means no rows are removed by qualification. These join types are just a notational convenience, since they do nothing you could not do with plain **FROM** and **WHERE**.
+
+        > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** For the **INNER** and **OUTER** join types, a join condition must be specified, namely exactly one of **NATURAL ON**, **join_condition**, or **USING (join_column [, …])**. For **CROSS JOIN**, none of these clauses can appear.
+
+        **CROSS JOIN** and **INNER JOIN** produce a simple Cartesian product, the same result as you get from listing the two items at the top level of **FROM**.
+
+  - ON join_condition
+
+    Defines which rows have matches in joins. Example: ON left_table.a = right_table.a
+
+  - USING(join_column[, …])
+
+    Abbreviation of **ON left_table.a = right_table.a AND left_table.b = right_table.b ….**. The names of the corresponding columns must be the same.
+
+  - NATURAL
+
+    Is a shorthand for a **USING** list that mentions all columns in the two tables that have the same names.
+
+  - from item
+
+    Specifies the name of the query source object connected.
+
+- **WHERE clause**
+
+  Forms an expression for row selection to narrow down the query range of **SELECT**. The condition is any expression that evaluates to a result of Boolean type. Rows that do not satisfy this condition will be eliminated from the output.
+
+  In the **WHERE** clause, you can use the operator (+) to convert a table join to an outer join. However, this method is not recommended because it is not the standard SQL syntax and may raise syntax compatibility issues during platform migration. There are many restrictions on using the operator (+):
+
+  1. It can appear only in the **WHERE** clause.
+  2. If a table join has been specified in the **FROM** clause, the operator (+) cannot be used in the **WHERE** clause.
+  3. The operator (+) can work only on columns of tables or views, instead of on expressions.
+  4. If table A and table B have multiple join conditions, the operator (+) must be specified in all the conditions. Otherwise, the operator (+) will not take effect, and the table join will be converted into an inner join without any prompt information.
+  5. Tables specified in a join condition where the operator (+) works cannot cross queries or subqueries. If tables where the operator (+) works are not in the **FROM** clause of the current query or subquery, an error will be reported. If a peer table for the operator (+) does not exist, no error will be reported and the table join will be converted into an inner join.
+  6. Expressions where the operator (+) is used cannot be directly connected through **OR**.
+  7. If a column where the operator (+) works is compared with a constant, the expression becomes a part of the join condition.
+  8. A table cannot have multiple foreign tables.
+  9. The operator (+) can appear only in the following expressions: comparison, NOT, ANY, ALL, IN, NULLIF, IS DISTINCT FROM, and IS OF. It is not allowed in other types of expressions. In addition, these expressions cannot be connected through **AND** or **OR**.
+  10. The operator (+) can be used to convert a table join only to a left or right outer join, instead of a full join. That is, the operator (+) cannot be specified on both tables of an expression.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** For the **WHERE** clause, if special character **%**, **_**, or **\** is queried in **LIKE**, add the slash **\** before each character.
+
+- **START WITH**
+
+The START WITH clause usually appears at the same time as the CONNECT BY clause. It is a recursive statement for graph traversal of data. START WITH represents the initial number of recursive items, and the PRIOR keyword can be specified for the column in the CONNECT BY condition. Represents recursively using this column as recursion. The current constraint can only specify PRIOR for the columns in the table, and does not support specifying the PRIOR keyword for expressions and type conversions.
+
+- **GROUP BY clause**
+
+    Condenses query results into a single row all selected rows that share the same values for the grouped expressions.
+
+  - CUBE ( { expression | ( expression [, …] ) } [, …] )
+
+    A CUBE grouping is an extension to the GROUP BY clause that creates subtotals for all of the possible combinations of the given list of grouping columns (or expressions). In terms of multidimensional analysis, CUBE generates all the subtotals that could be calculated for a data cube with the specified dimensions. For example, given three expressions (n=3) in the CUBE clause, the operation results in 2n = 23 = 8 groupings. Rows grouped on the values of *n* expressions are called regular rows, and the rest are called superaggregate rows.
+
+  - GROUPING SETS ( grouping_element [, …] )
+
+    Another extension to the **GROUP BY** clause. It allows users to specify multiple **GROUP BY** clauses. This improves efficiency by trimming away unnecessary data. After you specify the set of groups that you want to create using a **GROUPING SETS** expression within a **GROUP BY** clause, the database does not need to compute a whole **ROLLUP** or **CUBE**.
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** If the **SELECT** list expression quotes some ungrouped fields and no aggregate function is used, an error is displayed. This is because multiple values may be returned for ungrouped fields.
+
+- **HAVING clause**
+
+  Selects special groups by working with the **GROUP BY** clause. The **HAVING** clause compares some attributes of groups with a constant. Only groups that matching the logical expression in the **HAVING** clause are extracted.
+
+- **WINDOW clause**
+
+  The general format is **WINDOW window_name AS ( window_definition ) [, …]**. **window_name** is a name can be referenced by **window_definition**. **window_definition** can be expressed in the following forms:
+
+  [ existing_window_name ]
+
+  [ PARTITION BY expression [, …] ]
+
+  [ ORDER BY expression [ ASC | DESC | USING operator ] [ NULLS { FIRST | LAST } ] [, …] ]
+
+  [ frame_clause ]
+
+  **frame_clause** defines a **window frame** for the window function. The window function (not all window functions) depends on **window frame** and **window frame** is a set of relevant rows of the current query row. **frame_clause** can be expressed in the following forms:
+
+  [ RANGE | ROWS ] frame_start
+
+  [ RANGE | ROWS ] BETWEEN frame_start AND frame_end
+
+  **frame_start** and **frame_end** can be expressed in the following forms:
+
+  UNBOUNDED PRECEDING
+
+  value PRECEDING
+
+  CURRENT ROW
+
+  value FOLLOWING
+
+  UNBOUNDED FOLLOWING
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** For the query of column storage table, only **row_number** window function is supported, and **frame_clause** is not supported.
+
+- **UNION clause**
+
+    Computes the set union of the rows returned by the involved **SELECT** statements.
+
+    The **UNION** clause has the following constraints:
+
+  - By default, the result of **UNION** does not contain any duplicate rows unless the **ALL** clause is declared.
+  - Multiple **UNION** operators in the same **SELECT** statement are evaluated left to right, unless otherwise specified by parentheses.
+  - **FOR UPDATE** cannot be specified either for a **UNION** result or for any input of a **UNION**.
+
+    General expression:
+
+    select_statement UNION [ALL] select_statement
+
+  - **select_statement** can be any **SELECT** statement without an **ORDER BY**, **LIMIT**, **FOR UPDATE**, or **FOR SHARE** statement.
+  - **ORDER BY** and **LIMIT** can be attached to the subexpression if it is enclosed in parentheses.
+
+- **INTERSECT clause**
+
+    Computes the set intersection of rows returned by the involved **SELECT** statements. The result of **INTERSECT** does not contain any duplicate rows.
+
+    The **INTERSECT** clause has the following constraints:
+
+  - Multiple **INTERSECT** operators in the same **SELECT** statement are evaluated left to right, unless otherwise specified by parentheses.
+  - Processing **INTERSECT** preferentially when **UNION** and **INTERSECT** operations are executed for results of multiple **SELECT** statements.
+
+    General format:
+
+    select_statement INTERSECT select_statement
+
+    **select_statement** can be any **SELECT** statement without a **FOR UPDATE** clause.
+
+- **EXCEPT clause**
+
+  Has the following common form:
+
+  select_statement EXCEPT [ ALL ] select_statement
+
+  **select_statement** can be any **SELECT** statement without a **FOR UPDATE** clause.
+
+  The **EXCEPT** operator computes the set of rows that are in the result of the left **SELECT** statement but not in the result of the right one.
+
+  The result of **EXCEPT** does not contain any duplicate rows unless the **ALL** clause is declared. To execute **ALL**, a row that has *m* duplicates in the left table and *n* duplicates in the right table will appear MAX(_m_-*n*, 0) times in the result set.
+
+  Multiple **EXCEPT** operators in the same **SELECT** statement are evaluated left to right, unless parentheses dictate otherwise. **EXCEPT** binds at the same level as **UNION**.
+
+  Currently, **FOR UPDATE** cannot be specified either for an **EXCEPT** result or for any input of an **EXCEPT**.
+
+- **MINUS clause**
+
+  Has the same function and syntax as **EXCEPT** clause.
+
+- **ORDER BY clause**
+
+    Sorts data retrieved by **SELECT** in descending or ascending order. If the **ORDER BY** expression contains multiple columns:
+
+  - If two columns are equal according to the leftmost expression, they are compared according to the next expression and so on.
+  - If they are equal according to all specified expressions, they are returned in an implementation-dependent order.
+  - When used with the **DISTINCT** keyword, the columns to be sorted in **ORDER BY** must be included in the columns of the result set retrieved by the SELECT statement.
+  - When used with the **GROUP BY** clause, the columns to be sorted in **ORDER BY** must be included in the columns of the result set retrieved by the SELECT statement.
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** To support Chinese pinyin order, specify the **UTF-8** or **GBK** encoding mode during database initiation. The statements are as follows: initdb -E UTF8 -D ../data -locale=zh_CN.UTF-8 or initdb -E GBK -D ../data -locale=zh_CN.GBK
+
+- **LIMIT clause**
+
+  Consists of two independent sub-clauses:
+
+  LIMIT { count | ALL }
+
+  **OFFSET start count** specifies the maximum number of rows to return, while **start** specifies the number of rows to skip before starting to return rows. When both are specified, **start** rows are skipped before starting to count the **count** rows to be returned.
+
+- **OFFSET clause**
+
+  The SQL: 2008 standard has introduced a different clause:
+
+  OFFSET start { ROW | ROWS }
+
+  **start** specifies the number of rows to skip before starting to return rows.
+
+- **FETCH { FIRST | NEXT } [ count ] { ROW | ROWS } ONLY**
+
+  If **count** is omitted in a **FETCH** clause, it defaults to **1**.
+
+- **FOR UPDATE clause**
+
+  Locks rows retrieved by **SELECT**. This ensures that the rows cannot be modified or deleted by other transactions until the current transaction ends. That is, other transactions that attempt **UPDATE**, **DELETE**, or **SELECT FOR UPDATE** of these rows will be blocked until the current transaction ends.
+
+  To avoid waiting for the committing of other transactions, you can apply **NOWAIT**. Rows to which **NOWAIT** applies cannot be immediately locked. After **SELECT FOR UPDATE NOWAIT** is executed, an error is reported.
+
+  **FOR SHARE** behaves similarly, except that it acquires a shared rather than exclusive lock on each retrieved row. A share lock blocks other transaction from performing **UPDATE**, **DELETE**, or **SELECT FOR UPDATE** on these rows, but it does not prevent them from performing **SELECT FOR SHARE**.
+
+  If specified tables are named in **FOR UPDATE** or **FOR SHARE**, then only rows coming from those tables are locked. Any other tables used in **SELECT** are simply read as usual. Otherwise, locking all tables in the statement.
+
+  If **FOR UPDATE** or **FOR SHARE** is applied to a view or sub-query, it affects all tables used in the view or sub-query.
+
+  Multiple **FOR UPDATE** and **FOR SHARE** clauses can be written if it is necessary to specify different locking behaviors for different tables.
+
+  If the same table is mentioned (or implicitly affected) by both **FOR UPDATE** and **FOR SHARE** clauses, it is processed as **FOR UPDATE**. Similarly, a table is processed as **NOWAIT** if that is specified in any of the clauses affecting it.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** The query of column-store tables does not support **for update/share**.
+
+- **NLS_SORT** <a id = 'nlssort'> </a>
+
+    Specifies that a field is sorted in a special order. Currently, Chinese Pinyin and case-insensitive sorting are supported. Uncommon characters in GBK character set sorted by pinyin is supported.
+
+    Value range:
+
+  - **SCHINESE_PINYIN_M**, sorted by Pinyin order. To use this sorting method, specify **UTF8** or **GBK** as the encoding format when you create a database. If you do not do so, this value is invalid.
+  - **generic_m_ci**, case-insensitive order.
+
+- **PARTITION clause**
+
+  Queries data in the specified partition in a partitioned table.
+
+## Examples
+
+```sql
+-- Obtain the temp_t temporary table by a subquery and query all records in this table.
+mogdb=# WITH temp_t(name,isdba) AS (SELECT usename,usesuper FROM pg_user) SELECT * FROM temp_t;
+
+-- Query all r_reason_sk records in the tpcds.reason table and delete duplicate records.
+mogdb=# SELECT DISTINCT(r_reason_sk) FROM tpcds.reason;
+
+-- Example of a LIMIT clause: Obtain a record from the table.
+mogdb=# SELECT * FROM tpcds.reason LIMIT 1;
+
+-- Query all records and sort them in alphabetic order.
+mogdb=# SELECT r_reason_desc FROM tpcds.reason ORDER BY r_reason_desc;
+
+-- Use table aliases to obtain data from the pg_user and pg_user_status tables:
+mogdb=# SELECT a.usename,b.locktime FROM pg_user a,pg_user_status b WHERE a.usesysid=b.roloid;
+
+-- Example of the FULL JOIN clause: Join data in the pg_user and pg_user_status tables.
+mogdb=# SELECT a.usename,b.locktime,a.usesuper FROM pg_user a FULL JOIN pg_user_status b on a.usesysid=b.roloid;
+
+-- Example of the GROUP BY clause: Filter data based on query conditions, and group the results.
+mogdb=# SELECT r_reason_id, AVG(r_reason_sk) FROM tpcds.reason GROUP BY r_reason_id HAVING AVG(r_reason_sk) > 25;
+
+-- Example of the GROUP BY CUBE clause: Filter data based on query conditions, and group the results.
+mogdb=# SELECT r_reason_id,AVG(r_reason_sk) FROM tpcds.reason GROUP BY CUBE(r_reason_id,r_reason_sk);
+
+-- Example of the GROUP BY GROUPING SETS clause: Filter data based on query conditions, and group the results.
+mogdb=# SELECT r_reason_id,AVG(r_reason_sk) FROM tpcds.reason GROUP BY GROUPING SETS((r_reason_id,r_reason_sk),r_reason_sk);
+
+-- Example of the UNION clause: Merge the names started with W and N in the r_reason_desc column in the tpcds.reason table.
+mogdb=# SELECT r_reason_sk, tpcds.reason.r_reason_desc
+    FROM tpcds.reason
+    WHERE tpcds.reason.r_reason_desc LIKE 'W%'
+UNION
+SELECT r_reason_sk, tpcds.reason.r_reason_desc
+    FROM tpcds.reason
+    WHERE tpcds.reason.r_reason_desc LIKE 'N%';
+
+-- Example of the NLS_SORT clause: Sort by Chinese Pinyin.
+mogdb=# SELECT * FROM tpcds.reason ORDER BY NLSSORT( r_reason_desc, 'NLS_SORT = SCHINESE_PINYIN_M');
+
+
+-- Case-insensitive order:
+mogdb=# SELECT * FROM tpcds.reason ORDER BY NLSSORT( r_reason_desc, 'NLS_SORT = generic_m_ci');
+
+-- Create a range-partitioned table tpcds.reason_p.
+mogdb=# CREATE TABLE tpcds.reason_p
+(
+  r_reason_sk integer,
+  r_reason_id character(16),
+  r_reason_desc character(100)
+)
+PARTITION BY RANGE (r_reason_sk)
+(
+  partition P_05_BEFORE values less than (05),
+  partition P_15 values less than (15),
+  partition P_25 values less than (25),
+  partition P_35 values less than (35),
+  partition P_45_AFTER values less than (MAXVALUE)
+)
+;
+
+-- Insert data.
+mogdb=# INSERT INTO tpcds.reason_p values(3,'AAAAAAAABAAAAAAA','reason 1'),(10,'AAAAAAAABAAAAAAA','reason 2'),(4,'AAAAAAAABAAAAAAA','reason 3'),(10,'AAAAAAAABAAAAAAA','reason 4'),(10,'AAAAAAAABAAAAAAA','reason 5'),(20,'AAAAAAAACAAAAAAA','reason 6'),(30,'AAAAAAAACAAAAAAA','reason 7');
+
+-- Example of the PARTITION clause: Obtain data from the P_05_BEFORE partition in the tpcds.reason_p table.
+mogdb=#  SELECT * FROM tpcds.reason_p PARTITION (P_05_BEFORE);
+ r_reason_sk |   r_reason_id    |   r_reason_desc
+-------------+------------------+------------------------------------
+           4 | AAAAAAAABAAAAAAA | reason 3
+           3 | AAAAAAAABAAAAAAA | reason 1
+(2 rows)
+
+-- Example of the GROUP BY clause: Group records in the tpcds.reason_p table by r_reason_id, and count the number of records in each group.
+mogdb=# SELECT COUNT(*),r_reason_id FROM tpcds.reason_p GROUP BY r_reason_id;
+ count |   r_reason_id
+-------+------------------
+     2 | AAAAAAAACAAAAAAA
+     5 | AAAAAAAABAAAAAAA
+(2 rows)
+
+-- Example of the GROUP BY CUBE clause: Filter data based on query conditions, and group the results.
+mogdb=# SELECT * FROM tpcds.reason GROUP BY  CUBE (r_reason_id,r_reason_sk,r_reason_desc);
+
+-- Example of the GROUP BY GROUPING SETS clause: Filter data based on query conditions, and group the results.
+mogdb=# SELECT * FROM tpcds.reason GROUP BY  GROUPING SETS ((r_reason_id,r_reason_sk),r_reason_desc);
+
+-- Example of the HAVING clause: Group records in the tpcds.reason_p table by r_reason_id, count the number of records in each group, and display only values whose number of r_reason_id is greater than 2.
+mogdb=# SELECT COUNT(*) c,r_reason_id FROM tpcds.reason_p GROUP BY r_reason_id HAVING c>2;
+ c |   r_reason_id
+---+------------------
+ 5 | AAAAAAAABAAAAAAA
+(1 row)
+
+-- Example of the IN clause: Group records in the tpcds.reason_p table by r_reason_id, count the number of records in each group, and display only the numbers of records whose r_reason_id is AAAAAAAABAAAAAAA or AAAAAAAADAAAAAAA.
+mogdb=# SELECT COUNT(*),r_reason_id FROM tpcds.reason_p GROUP BY r_reason_id HAVING r_reason_id IN('AAAAAAAABAAAAAAA','AAAAAAAADAAAAAAA');
+count |   r_reason_id
+-------+------------------
+     5 | AAAAAAAABAAAAAAA
+(1 row)
+
+-- Example of the INTERSECT clause: Query records whose r_reason_id is AAAAAAAABAAAAAAA and whose r_reason_sk is smaller than 5.
+mogdb=# SELECT * FROM tpcds.reason_p WHERE r_reason_id='AAAAAAAABAAAAAAA' INTERSECT SELECT * FROM tpcds.reason_p WHERE r_reason_sk<5;
+ r_reason_sk |   r_reason_id    |     r_reason_desc
+-------------+------------------+------------------------------------
+           4 | AAAAAAAABAAAAAAA | reason 3
+           3 | AAAAAAAABAAAAAAA | reason 1
+(2 rows)
+
+-- Example of the EXCEPT clause: Query records whose r_reason_id is AAAAAAAABAAAAAAA and whose r_reason_sk is greater than or equal to 4.
+mogdb=# SELECT * FROM tpcds.reason_p WHERE r_reason_id='AAAAAAAABAAAAAAA' EXCEPT SELECT * FROM tpcds.reason_p WHERE r_reason_sk<4;
+r_reason_sk |   r_reason_id    |      r_reason_desc
+-------------+------------------+------------------------------------
+          10 | AAAAAAAABAAAAAAA | reason 2
+          10 | AAAAAAAABAAAAAAA | reason 5
+          10 | AAAAAAAABAAAAAAA | reason 4
+           4 | AAAAAAAABAAAAAAA | reason 3
+(4 rows)
+
+-- Specify the operator (+) in the WHERE clause to indicate a left join.
+mogdb=# select t1.sr_item_sk ,t2.c_customer_id from store_returns t1, customer t2 where t1.sr_customer_sk  = t2.c_customer_sk(+)
+order by 1 desc limit 1;
+ sr_item_sk | c_customer_id
+------------+---------------
+      18000 |
+(1 row)
+
+-- Specify the operator (+) in the WHERE clause to indicate a right join.
+mogdb=# select t1.sr_item_sk ,t2.c_customer_id from store_returns t1, customer t2 where t1.sr_customer_sk(+)  = t2.c_customer_sk
+order by 1 desc limit 1;
+ sr_item_sk |  c_customer_id
+------------+------------------
+            | AAAAAAAAJNGEBAAA
+(1 row)
+
+-- Specify the operator (+) in the WHERE clause to indicate a left join and add a join condition.
+mogdb=# select t1.sr_item_sk ,t2.c_customer_id from store_returns t1, customer t2 where t1.sr_customer_sk  = t2.c_customer_sk(+) and t2.c_customer_sk(+) < 1 order by 1  limit 1;
+ sr_item_sk | c_customer_id
+------------+---------------
+          1 |
+(1 row)
+
+-- If the operator (+) is specified in the WHERE clause, do not use expressions connected through AND/OR.
+mogdb=# select t1.sr_item_sk ,t2.c_customer_id from store_returns t1, customer t2 where not(t1.sr_customer_sk  = t2.c_customer_sk(+) and t2.c_customer_sk(+) < 1);
+ERROR:  Operator "(+)" can not be used in nesting expression.
+LINE 1: ...tomer_id from store_returns t1, customer t2 where not(t1.sr_...
+                                                             ^
+-- If the operator (+) is specified in the WHERE clause which does not support expression macros, an error will be reported.
+mogdb=# select t1.sr_item_sk ,t2.c_customer_id from store_returns t1, customer t2 where (t1.sr_customer_sk  = t2.c_customer_sk(+))::bool;
+ERROR:  Operator "(+)" can only be used in common expression.
+
+-- If the operator (+) is specified on both sides of an expression in the WHERE clause, an error will be reported.
+mogdb=# select t1.sr_item_sk ,t2.c_customer_id from store_returns t1, customer t2 where t1.sr_customer_sk(+)  = t2.c_customer_sk(+);
+ERROR:  Operator "(+)" can't be specified on more than one relation in one join condition
+HINT:  "t1", "t2"...are specified Operator "(+)" in one condition.
+
+-- Delete the table.
+mogdb=# DROP TABLE tpcds.reason_p;
+
+-- Example of a flashback query
+-- Create the tpcds.time_table table.
+mogdb=#  create table tpcds.time_table(idx integer, snaptime timestamp, snapcsn bigint, timeDesc character(100));
+-- Insert records into the tpcds.time_table table.
+mogdb=#  INSERT INTO tpcds.time_table select 1, now(),int8in(xidout(next_csn)), 'time1' from gs_get_next_xid_csn();
+mogdb=#  INSERT INTO tpcds.time_table select 2, now(),int8in(xidout(next_csn)), 'time2' from gs_get_next_xid_csn();
+mogdb=#  INSERT INTO tpcds.time_table select 3, now(),int8in(xidout(next_csn)), 'time3' from gs_get_next_xid_csn();
+mogdb=#  INSERT INTO tpcds.time_table select 4, now(),int8in(xidout(next_csn)), 'time4' from gs_get_next_xid_csn();
+mogdb=#  select * from tpcds.time_table;
+
+ idx |          snaptime          | snapcsn |                                               timedesc
+-----+----------------------------+---------+------------------------------------------------------------------------------------------------------
+   1 | 2021-04-25 17:50:05.360326 |  107322 | time1
+   2 | 2021-04-25 17:50:10.886848 |  107324 | time2
+   3 | 2021-04-25 17:50:16.12921  |  107327 | time3
+   4 | 2021-04-25 17:50:22.311176 |  107330 | time4
+(4 rows)
+mogdb=#  delete tpcds.time_table;
+DELETE 4
+mogdb=#  SELECT * FROM tpcds.time_table TIMECAPSULE TIMESTAMP to_timestamp('2021-04-25 17:50:22.311176','YYYY-MM-DD HH24:MI:SS.FF');
+ idx |          snaptime          | snapcsn |                                               timedesc
+-----+----------------------------+---------+------------------------------------------------------------------------------------------------------
+   1 | 2021-04-25 17:50:05.360326 |  107322 | time1
+   2 | 2021-04-25 17:50:10.886848 |  107324 | time2
+   3 | 2021-04-25 17:50:16.12921  |  107327 | time3
+(3 rows)
+mogdb=#  SELECT * FROM tpcds.time_table TIMECAPSULE CSN 107330;
+ idx |          snaptime          | snapcsn |                                               timedesc
+-----+----------------------------+---------+------------------------------------------------------------------------------------------------------
+   1 | 2021-04-25 17:50:05.360326 |  107322 | time1
+   2 | 2021-04-25 17:50:10.886848 |  107324 | time2
+   3 | 2021-04-25 17:50:16.12921  |  107327 | time3
+(3 rows)
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/126-SELECT-INTO.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/126-SELECT-INTO.md
new file mode 100644
index 0000000000000000000000000000000000000000..9485dfcaac871aaed7f26e104702953e24ecd7c1
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/126-SELECT-INTO.md
@@ -0,0 +1,97 @@
+---
+title: SELECT INTO
+summary: SELECT INTO
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# SELECT INTO
+
+## Function
+
+**SELECT INTO** defines a new table based on a query result and inserts data obtained by query to the new table.
+
+Different from **SELECT**, data found by **SELECT INTO** is not returned to the client. The table columns have the same names and data types as the output columns of the **SELECT**.
+
+## Precautions
+
+**CREATE TABLE AS** provides functions similar to **SELECT INTO** in functions and provides a superset of functions provided by **SELECT INTO**. You are advised to use **CREATE TABLE AS**, because **SELECT INTO** cannot be used in a stored procedure.
+
+## Syntax
+
+```ebnf+diagram
+SelectInto ::= [ WITH [ RECURSIVE ] with_query [, ...] ]
+SELECT [ ALL | DISTINCT [ ON ( expression [, ...] ) ] ]
+    { * | {expression [ [ AS ] output_name ]} [, ...] }
+    INTO [ [ GLOBAL | LOCAL ] [ TEMPORARY | TEMP ] | UNLOGGED ] [ TABLE ] new_table
+    [ FROM from_item [, ...] ]
+    [ WHERE condition ]
+    [ GROUP BY expression [, ...] ]
+    [ HAVING condition [, ...] ]
+    [ WINDOW {window_name AS ( window_definition )} [, ...] ]
+    [ { UNION | INTERSECT | EXCEPT | MINUS } [ ALL | DISTINCT ] select ]
+    [ ORDER BY {expression [ [ ASC | DESC | USING operator ] | nlssort_expression_clause ] [ NULLS { FIRST | LAST } ]} [, ...] ]
+    [ LIMIT { count | ALL } ]
+    [ OFFSET start [ ROW | ROWS ] ]
+    [ FETCH { FIRST | NEXT } [ count ] { ROW | ROWS } ONLY ]
+    [ {FOR { UPDATE | SHARE } [ OF table_name [, ...] ] [ NOWAIT ]} [...] ];
+```
+
+## Parameter Description
+
+- **new_table**
+
+  **new_table** specifies the name of the new table.
+
+- **UNLOGGED**
+
+    Specifies that the table is created as an unlogged table. Data written to unlogged tables is not written to the WALs, which makes them considerably faster than ordinary tables. However, they are not crash-safe: an unlogged table is automatically truncated after a crash or unclean shutdown. The contents of an unlogged table are also not replicated to standby servers. Any indexes created on an unlogged table are automatically unlogged as well.
+
+  - Usage scenario: Unlogged tables do not ensure data security. Users can back up data before using unlogged tables; for example, users should back up the data before a system upgrade.
+  - Troubleshooting: If data is missing in the indexes of unlogged tables due to some unexpected operations such as an unclean shutdown, users should re-create the indexes with errors.
+
+- **GLOBAL | LOCAL**
+
+  When creating a temporary table, you can specify the **GLOBAL** or **LOCAL** keyword before **TEMP** or **TEMPORARY**. If the keyword **GLOBAL** is specified, MogDB creates a global temporary table. Otherwise, MogDB creates a local temporary table.
+
+- **TEMPORARY | TEMP**
+
+  If **TEMP** or **TEMPORARY** is specified, the created table is a temporary table. Temporary tables are classified into global temporary tables and local temporary tables. If the keyword **GLOBAL** is specified when a temporary table is created, the table is a global temporary table. Otherwise, the table is a local temporary table.
+
+  The metadata of the global temporary table is visible to all sessions. After the sessions end, the metadata still exists. The user data, indexes, and statistics of a session are isolated from those of another session. Each session can only view and modify the data submitted by itself. Global temporary tables have two schemas: **ON COMMIT PRESERVE ROWS** and **ON COMMIT PRESERVE ROWS**. In session-based **ON COMMIT PRESERVE ROWS** schema, user data is automatically cleared when a session ends. In transaction-based **ON COMMIT DELETE ROWS** schema, user data is automatically cleared when the commit or rollback operation is performed. If the **ON COMMIT** option is not specified during table creation, the session level is used by default. Different from local temporary tables, you can specify a schema that does not start with **pg_temp_** when creating a global temporary table.
+
+  A local temporary table is automatically dropped at the end of the current session. Therefore, you can create and use temporary tables in the current session as long as the connected database node in the session is normal. Temporary tables are created only in the current session. If a DDL statement involves operations on temporary tables, a DDL error will be generated. Therefore, you are not advised to perform operations on temporary tables in DDL statements. **TEMP** is equivalent to **TEMPORARY**.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+  >
+  > - Local temporary tables are visible to the current session through the schema starting with **pg_temp** start. Users should not delete schema started with **pg_temp** or **pg_toast_temp**.
+  > - If **TEMPORARY** or **TEMP** is not specified when you create a table but its schema is set to that starting with **pg_temp_** in the current session, the table will be created as a temporary table.
+  > - If global temporary tables and indexes are being used by other sessions, do not perform **ALTER** or **DROP**.
+  > - The DDL of a global temporary table affects only the user data and indexes of the current session. For example, **TRUNCATE**, **REINDEX**, and **ANALYZE** are valid only for the current session.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** For details about other **SELECT INTO** parameters, see **Parameter Description** in **SELECT**.
+
+## Examples
+
+```sql
+-- Add the values that are less than 5 in the r_reason_sk field in the tpcds.reason table to the new table.
+mogdb=# SELECT * INTO tpcds.reason_t1 FROM tpcds.reason WHERE r_reason_sk < 5;
+INSERT 0 6
+
+-- Delete the  tpcds.reason_t1 table.
+mogdb=# DROP TABLE tpcds.reason_t1;
+```
+
+## Helpful Links
+
+[SELECT](125-SELECT)
+
+## Suggestions
+
+- **DATABASE**
+
+  You are not advised to reindex a database in a transaction.
+
+- **SYSTEM**
+
+  You are not advised to reindex system catalogs in transactions.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/127-SET.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/127-SET.md
new file mode 100644
index 0000000000000000000000000000000000000000..58d18648abbaa515f580f664b51a4ab7fa273ff6
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/127-SET.md
@@ -0,0 +1,122 @@
+---
+title: SET
+summary: SET
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# SET
+
+## Function
+
+**SET** modifies a run-time parameter.
+
+## Precautions
+
+Most run-time parameters can be modified by executing **SET**. Some parameters cannot be modified after a server or session starts.
+
+## Syntax
+
+- Set the system time zone.
+
+  ```ebnf+diagram
+  Set ::= SET [ SESSION | LOCAL ] TIME ZONE { timezone | LOCAL | DEFAULT };
+  ```
+
+- Set the schema of the table.
+
+  ```ebnf+diagram
+  Set ::= SET [ SESSION | LOCAL ]
+      {CURRENT_SCHEMA { TO | = } { schema | DEFAULT }
+      | SCHEMA 'schema'};
+  ```
+
+- Set client encoding.
+
+  ```ebnf+diagram
+  Set ::= SET [ SESSION | LOCAL ] NAMES encoding_name;
+  ```
+
+- Set XML parsing mode.
+
+  ```ebnf+diagram
+  Set ::= SET [ SESSION | LOCAL ] XML OPTION { DOCUMENT | CONTENT };
+  ```
+
+- Set other run-time parameters.
+
+  ```ebnf+diagram
+  Set ::= SET [ LOCAL | SESSION ]
+      { {config_parameter { { TO | = } { value | DEFAULT }
+                          | FROM CURRENT }}};
+  ```
+
+## Parameter Description
+
+- **SESSION**
+
+  Specifies that the specified parameters take effect for the current session. This is the default value if neither **SESSION** nor **LOCAL** appears.
+
+  If **SET** or **SET SESSION** is executed within a transaction that is later aborted, the effects of the **SET** statement disappear when the transaction is rolled back. Once the surrounding transaction is committed, the effects will persist until the end of the session, unless overridden by another **SET**.
+
+- **LOCAL**
+
+  Specifies that the specified parameters take effect for the current transaction. After **COMMIT** or **ROLLBACK**, the session-level setting takes effect again.
+
+  The effects of **SET LOCAL** last only till the end of the current transaction, whether committed or not. A special case is **SET** followed by **SET LOCAL** within a single transaction: the **SET LOCAL** value will be seen until the end of the transaction, but afterward (if the transaction is committed) the **SET** value will take effect.
+
+- **TIME ZONE timezone**
+
+  Specifies the local time zone for the current session.
+
+  Value range: a valid local time zone. The corresponding run-time parameter is **TimeZone**. The default value is **PRC**.
+
+- **CURRENT_SCHEMA**
+
+  **schema**
+
+  Specifies the current schema.
+
+  Value range: an existing schema name. If the schema name does not exist, it will cause the CURRENT_SCHEMA value to be empty.
+
+- **SCHEMA schema**
+
+  Specifies the current schema. Here the schema is a string.
+
+  Example: set schema 'public';
+
+- **NAMES encoding_name**
+
+  Specifies the client character encoding. This statement is equivalent to **set client_encoding to encoding_name**.
+
+  Value range: a valid character encoding name. The run-time parameter corresponding to this option is **client_encoding**. The default encoding is **UTF8**.
+
+- **XML OPTION option**
+
+  Specifies the XML parsing mode.
+
+  Value range: **CONTENT** (default) and **DOCUMENT**
+
+- **config_parameter**
+
+  Specifies the name of a configurable run-time parameter. You can use **SHOW ALL** to view available run-time parameters.
+
+  >![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** Some parameters that viewed by **SHOW ALL** cannot be set by **SET**. For example, **max_datanodes**.
+
+- **value**
+
+  Specifies the new value of **config_parameter**. This parameter can be specified as string constants, identifiers, numbers, or comma-separated lists of these. **DEFAULT** can be written to indicate resetting the parameter to its default value.
+
+## Examples
+
+```sql
+-- Set the search path of a schema.
+mogdb=# SET search_path TO tpcds, public;
+
+-- Set the date style to the traditional POSTGRES style (date placed before month).
+mogdb=# SET datestyle TO postgres,dmy;
+```
+
+## Helpful Links
+
+[RESET](119-RESET) and [SHOW](132-SHOW)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/128-SET-CONSTRAINTS.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/128-SET-CONSTRAINTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..b2f1aa268794e1469193758d361ca91e94201974
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/128-SET-CONSTRAINTS.md
@@ -0,0 +1,59 @@
+---
+title: SET CONSTRAINTS
+summary: SET CONSTRAINTS
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# SET CONSTRAINTS
+
+## Function
+
+**SET CONSTRAINTS** sets the behavior of constraint checking within the current transaction.
+
+**IMMEDIATE** constraints are checked at the end of each statement. **DEFERRED** constraints are not checked until transaction commit. Each constraint has its own **IMMEDIATE** or **DEFERRED** mode.
+
+Upon creation, a constraint is given one of three characteristics **DEFERRABLE INITIALLY DEFERRED**, **DEFERRABLE INITIALLY IMMEDIATE**, or **NOT DEFERRABLE**. The third class is always **IMMEDIATE** and is not affected by the **SET CONSTRAINTS** statement. The first two classes start every transaction in specified modes, but its behaviors can be changed within a transaction by **SET CONSTRAINTS**.
+
+**SET CONSTRAINTS** with a list of constraint names changes the mode of just those constraints (which must all be deferrable). If multiple constraints match a name, the name is affected by all of these constraints. **SET CONSTRAINTS ALL** changes the modes of all deferrable constraints.
+
+When **SET CONSTRAINTS** changes the mode of a constraint from **DEFERRED** to **IMMEDIATE**, the new mode takes effect retroactively: any outstanding data modifications that would have been checked at the end of the transaction are instead checked during the execution of the **SET CONSTRAINTS** statement. If any such constraint is violated, the **SET CONSTRAINTS** fails (and does not change the constraint mode). Therefore, **SET CONSTRAINTS** can be used to force checking of constraints to occur at a specific point in a transaction.
+
+Constraints are always checked immediately when a row is inserted or modified.
+
+## Precautions
+
+**SET CONSTRAINTS** sets the behavior of constraint checking only within the current transaction. Therefore, if you execute this statement outside of a transaction block (**START TRANSACTION/COMMIT** pair), it will not appear to have any effect.
+
+## Syntax
+
+```ebnf+diagram
+SetConstraints ::= SET CONSTRAINTS  { ALL  |  { name  }  [, ...]  }  { DEFERRED  | IMMEDIATE  } ;
+```
+
+## Parameter Description
+
+- **name**
+
+  Specifies the constraint name.
+
+  Value range: an existing table name, which can be found in the system catalog **pg_constraint**.
+
+- **ALL**
+
+  Specifies all constraints.
+
+- **DEFERRED**
+
+  Specifies that constraints are not checked until transaction commit.
+
+- **IMMEDIATE**
+
+  Specifies that constraints are checked at the end of each statement.
+
+## Example
+
+```sql
+-- Set that constraints are checked when a transaction is committed.
+mogdb=# SET CONSTRAINTS ALL DEFERRED;
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/129-SET-ROLE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/129-SET-ROLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..6247e05d951ff5ed8c8f7377ef3826388d172a00
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/129-SET-ROLE.md
@@ -0,0 +1,74 @@
+---
+title: SET ROLE
+summary: SET ROLE
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# SET ROLE
+
+## Function
+
+**SET ROLE** sets the current user identifier of the current session.
+
+## Precautions
+
+- Users of the current session must be members of specified **rolename**, but the system administrator can choose any roles.
+- Executing this statement may add rights of a user or restrict rights of a user. If the role of a session user has the **INHERITS** attribute, it automatically has all rights of roles that **SET ROLE** enables the role to be. In this case, **SET ROLE** physically deletes all rights directly granted to session users and rights of its belonging roles and only leaves rights of the specified roles. If the role of the session user has the **NOINHERITS** attribute, **SET ROLE** deletes rights directly granted to the session user and obtains rights of the specified role.
+
+## Syntax
+
+- Set the current user identifier of the current session.
+
+  ```ebnf+diagram
+  SetRole ::= SET [ SESSION | LOCAL ] ROLE role_name PASSWORD 'password';
+  ```
+
+- Reset the current user identifier to that of the current session.
+
+  ```ebnf+diagram
+  ResetRole ::= RESET ROLE;
+  ```
+
+## Parameter Description
+
+- **SESSION**
+
+  Specifies that the statement takes effect only for the current session. This parameter is used by default.
+
+- **LOCAL**
+
+  Specifies that the specified statement takes effect only for the current transaction.
+
+- **role_name**
+
+  Indicates the role name.
+
+  Value range: a string. It must comply with the naming convention rule.
+
+- **password**
+
+  Specifies the password of a role. It must comply with the password convention.
+
+- **RESET ROLE**
+
+  Resets the current user identifier.
+
+## Examples
+
+```sql
+-- Create a role paul.
+mogdb=# CREATE ROLE paul IDENTIFIED BY 'Bigdata@123';
+
+-- Set the current user to paul.
+mogdb=# SET ROLE paul PASSWORD 'Bigdata@123';
+
+-- View the current session user and the current user.
+mogdb=# SELECT SESSION_USER, CURRENT_USER;
+
+-- Reset the current user.
+mogdb=# RESET role;
+
+-- Delete the user.
+mogdb=# DROP USER paul;
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/13-ALTER-ROW-LEVEL-SECURITY-POLICY.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/13-ALTER-ROW-LEVEL-SECURITY-POLICY.md
new file mode 100644
index 0000000000000000000000000000000000000000..9d25ad21556b8f6207eef27928a110eab3df1830
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/13-ALTER-ROW-LEVEL-SECURITY-POLICY.md
@@ -0,0 +1,114 @@
+---
+title: ALTER ROW LEVEL SECURITY POLICY
+summary: ALTER ROW LEVEL SECURITY POLICY
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER ROW LEVEL SECURITY POLICY
+
+## Function
+
+**ALTER ROW LEVEL SECURITY POLICY** modifies an existing row-level access control policy, including the policy name and the users and expressions affected by the policy.
+
+## Precautions
+
+Only the table owner or a system administrator can perform this operation.
+
+## Syntax
+
+```ebnf+diagram
+AlterRowLevelSecurityPolicy ::= ALTER [ ROW LEVEL SECURITY ] POLICY [ IF EXISTS ] policy_name ON table_name RENAME TO new_policy_name;
+```
+
+```ebnf+diagram
+AlterRowLevelSecurityPolicy ::= ALTER [ ROW LEVEL SECURITY ] POLICY policy_name ON table_name
+    [ TO { role_name | PUBLIC } [, ...] ]
+    [ USING ( using_expression ) ];
+```
+
+## Parameter Description
+
+- policy_name
+
+  Specifies the name of a row-level access control policy.
+
+- table_name
+
+  Specifies the name of a table to which a row-level access control policy is applied.
+
+- new_policy_name
+
+  Specifies the new name of a row-level access control policy.
+
+- role_name
+
+  Specifies names of users affected by a row-level access control policy. PUBLIC indicates that the row-level access control policy will affect all users.
+
+- using_expression
+
+  Specifies an expression defined for a row-level access control policy. The return value is of the boolean type.
+
+## Examples
+
+```sql
+-- Create the data table all_data.
+mogdb=# CREATE TABLE all_data(id int, role varchar(100), data varchar(100));
+
+--Create a row-level access control policy to specify that the current user can view only their own data.
+mogdb=# CREATE ROW LEVEL SECURITY POLICY all_data_rls ON all_data USING(role = CURRENT_USER);
+mogdb=# \d+ all_data
+                               Table "public.all_data"
+ Column |          Type          | Modifiers | Storage  | Stats target | Description
+--------+------------------------+-----------+----------+--------------+-------------
+ id     | integer                |           | plain    |              |
+ role   | character varying(100) |           | extended |              |
+ data   | character varying(100) |           | extended |              |
+Row Level Security Policies:
+    POLICY "all_data_rls"
+      USING (((role)::name = "current_user"()))
+Has OIDs: no
+Location Nodes: ALL DATANODES
+Options: orientation=row, compression=no
+
+-- Change the name of the all_data_rls policy.
+mogdb=# ALTER ROW LEVEL SECURITY POLICY all_data_rls ON all_data RENAME TO all_data_new_rls;
+
+-- Change the users affected by the row-level access control policy.
+mogdb=# ALTER ROW LEVEL SECURITY POLICY all_data_new_rls ON all_data TO alice, bob;
+mogdb=# \d+ all_data
+                               Table "public.all_data"
+ Column |          Type          | Modifiers | Storage  | Stats target | Description
+--------+------------------------+-----------+----------+--------------+-------------
+ id     | integer                |           | plain    |              |
+ role   | character varying(100) |           | extended |              |
+ data   | character varying(100) |           | extended |              |
+Row Level Security Policies:
+    POLICY "all_data_new_rls"
+      TO alice,bob
+      USING (((role)::name = "current_user"()))
+Has OIDs: no
+Location Nodes: ALL DATANODES
+Options: orientation=row, compression=no, enable_rowsecurity=true
+
+-- Modify the expression defined for the access control policy.
+mogdb=# ALTER ROW LEVEL SECURITY POLICY all_data_new_rls ON all_data USING (id > 100 AND role = current_user);
+mogdb=# \d+ all_data
+                               Table "public.all_data"
+ Column |          Type          | Modifiers | Storage  | Stats target | Description
+--------+------------------------+-----------+----------+--------------+-------------
+ id     | integer                |           | plain    |              |
+ role   | character varying(100) |           | extended |              |
+ data   | character varying(100) |           | extended |              |
+Row Level Security Policies:
+    POLICY "all_data_new_rls"
+      TO alice,bob
+      USING (((id > 100) AND ((role)::name = "current_user"())))
+Has OIDs: no
+Location Nodes: ALL DATANODES
+Options: orientation=row, compression=no, enable_rowsecurity=true
+```
+
+## Helpful Links
+
+[CREATE ROW LEVEL SECURITY POLICY](52-CREATE-ROW-LEVEL-SECURITY-POLICY)，[DROP ROW LEVEL SECURITY POLICY](87-DROP-ROW-LEVEL-SECURITY-POLICY)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/130-SET-SESSION-AUTHORIZATION.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/130-SET-SESSION-AUTHORIZATION.md
new file mode 100644
index 0000000000000000000000000000000000000000..7907901992fbeb9d3a0ef32f1e3a48bc75b001ba
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/130-SET-SESSION-AUTHORIZATION.md
@@ -0,0 +1,78 @@
+---
+title: SET SESSION AUTHORIZATION
+summary: SET SESSION AUTHORIZATION
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# SET SESSION AUTHORIZATION
+
+## Function
+
+**SET SESSION AUTHORIZATION** sets the session user identifier and the current user identifier of the current SQL session to a specified user.
+
+## Precautions
+
+The session identifier can be changed only when the initial session user has the system administrator rights. Otherwise, the system supports the statement only when the authenticated user name is specified.
+
+## Syntax
+
+- Set the session user identifier and the current user identifier of the current session.
+
+  ```ebnf+diagram
+  SetSessionAuthorization ::= SET [ SESSION | LOCAL ] SESSION AUTHORIZATION role_name PASSWORD 'password';
+  ```
+
+- Reset the identifiers of the session and current users to the initially authenticated user names.
+
+  ```ebnf+diagram
+  ResetSessionAuthorization ::= {SET [ SESSION | LOCAL ] SESSION AUTHORIZATION DEFAULT
+      | RESET SESSION AUTHORIZATION};
+  ```
+
+## Parameter Description
+
+- **SESSION**
+
+  Specifies that the specified parameters take effect for the current session.
+
+- **LOCAL**
+
+  Specifies that the specified statement takes effect only for the current transaction.
+
+- **role_name**
+
+  Username
+
+  Value range: a string. It must comply with the naming convention rule.
+
+- **password**
+
+  Specifies the password of a role. It must comply with the password convention.
+
+- **DEFAULT**
+
+  Resets the identifiers of the session and current users to the initially authenticated user names.
+
+## Examples
+
+```sql
+-- Create a role paul.
+mogdb=# CREATE ROLE paul IDENTIFIED BY 'Bigdata@123';
+
+-- Set the current user to paul.
+mogdb=# SET SESSION AUTHORIZATION paul password 'Bigdata@123';
+
+-- View the current session user and the current user.
+mogdb=# SELECT SESSION_USER, CURRENT_USER;
+
+-- Reset the current user.
+mogdb=# RESET SESSION AUTHORIZATION;
+
+-- Delete the user.
+mogdb=# DROP USER paul;
+```
+
+## Helpful Links
+
+[SET ROLE](129-SET-ROLE)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/131-SET-TRANSACTION.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/131-SET-TRANSACTION.md
new file mode 100644
index 0000000000000000000000000000000000000000..555220f7f13cfa86c3564e1f83e2522db0e42dcb
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/131-SET-TRANSACTION.md
@@ -0,0 +1,63 @@
+---
+title: SET TRANSACTION
+summary: SET TRANSACTION
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# SET TRANSACTION
+
+## Function
+
+**SET TRANSACTION** sets characteristics of a transaction. Available transaction characteristics include the transaction isolation level and transaction access mode (read/write or read only). You can set the current transaction characteristics using **LOCAL** or the default transaction characteristics of a session using **SESSION**.
+
+## Precautions
+
+The current transaction characteristics must be set in a transaction, that is, **START TRANSACTION** or **BEGIN** must be executed before **SET TRANSACTION** is executed. Otherwise, the setting does not take effect.
+
+## Syntax
+
+Set the isolation level and access mode of the transaction.
+
+```ebnf+diagram
+SetTransaction ::= { SET [ LOCAL ] TRANSACTION|SET SESSION CHARACTERISTICS AS TRANSACTION }
+  { ISOLATION LEVEL { READ COMMITTED | SERIALIZABLE | REPEATABLE READ }
+  | { READ WRITE | READ ONLY } } [, ...];
+```
+
+## Parameter Description
+
+- **LOCAL**
+
+  Specifies that the specified statement takes effect only for the current transaction.
+
+- **SESSION**
+
+  Specifies that the specified parameters take effect for the current session.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **ISOLATION_LEVEL**
+
+  Specifies the transaction isolation level that determines the data that a transaction can view if other concurrent transactions exist.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The isolation level cannot be changed after data is modified using **SELECT**, **INSERT**, **DELETE**, **UPDATE**, **FETCH**, or **COPY** in the current transaction.
+
+  Value range:
+
+  - **READ COMMITTED**: Only submitted data is read. It is the default value.
+  - **REPEATABLE READ**: Only the data committed before transaction start is read. Uncommitted data or data committed in other concurrent transactions cannot be read.
+  - **SERIALIZABLE**: Currently, this isolation level is not supported in MogDB. It is equivalent to **REPEATABLE READ**.
+
+- **READ WRITE | READ ONLY**
+
+  Specifies the transaction access mode (read/write or read only).
+
+## Examples
+
+```sql
+-- Start a transaction and set its isolation level to READ COMMITTED and access mode to READ ONLY.
+mogdb=# START TRANSACTION;
+mogdb=# SET LOCAL TRANSACTION ISOLATION LEVEL READ COMMITTED READ ONLY;
+mogdb=# COMMIT;
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/132-SHOW.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/132-SHOW.md
new file mode 100644
index 0000000000000000000000000000000000000000..6d56d619fb2e451bf2f548283982bc53cbe498e5
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/132-SHOW.md
@@ -0,0 +1,51 @@
+---
+title: SHOW
+summary: SHOW
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# SHOW
+
+## Function
+
+**SHOW** shows the current value of a run-time parameter.
+
+## Precautions
+
+None
+
+## Syntax
+
+```ebnf+diagram
+Show ::= SHOW
+  {
+    [VARIABLES LIKE] configuration_parameter |
+    CURRENT_SCHEMA |
+    TIME ZONE |
+    TRANSACTION ISOLATION LEVEL |
+    SESSION AUTHORIZATION |
+    ALL
+  };
+```
+
+## Parameter Description
+
+See **Parameter Description** in **RESET**.
+
+## Examples
+
+```sql
+-- Show the value of timezone.
+mogdb=# SHOW timezone;
+
+-- Show all parameters.
+mogdb=# SHOW ALL;
+
+-- Show all parameters whose names contain var.
+mogdb=# SHOW VARIABLES LIKE var;
+```
+
+## Helpful Links
+
+[SET](127-SET) and [RESET](119-RESET)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/133-SHUTDOWN.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/133-SHUTDOWN.md
new file mode 100644
index 0000000000000000000000000000000000000000..3e55fa409602cd1496cc0be45dd1c23873865b11
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/133-SHUTDOWN.md
@@ -0,0 +1,50 @@
+---
+title: SHUTDOWN
+summary: SHUTDOWN
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# SHUTDOWN
+
+## Function
+
+**SHUTDOWN** is used to shut down the currently connected database node.
+
+## Precautions
+
+Only the user with the administrator permission can run this command.
+
+## Syntax
+
+```ebnf+diagram
+Shutdown ::= SHUTDOWN
+  {
+    fast  |
+    immediate
+  };
+```
+
+## Parameter Description
+
+- **""**
+
+  If the shutdown mode is not specified, the default mode **fast** is used.
+
+- **fast**
+
+  Rolls back all active transactions, forcibly disconnects the client, and shuts down the database node without waiting for the client to disconnect.
+
+- **immediate**
+
+  Shuts down the server forcibly. Fault recovery will occur on the next startup.
+
+## Examples
+
+```sql
+-- Shut down the current database node.
+mogdb=# SHUTDOWN;
+
+-- Shut down the current database node in fast mode.
+mogdb=# SHUTDOWN FAST;
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/133.1-SNAPSHOT.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/133.1-SNAPSHOT.md
new file mode 100644
index 0000000000000000000000000000000000000000..68e0367b83a53673eadb0154655e3e9bfdc9a6b9
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/133.1-SNAPSHOT.md
@@ -0,0 +1,110 @@
+---
+title: SNAPSHOT
+summary: SNAPSHOT
+author: Zhang Cuiping
+date: 2021-11-01
+---
+
+# SNAPSHOT
+
+## Function
+
+**SNAPSHOT** controls data in a unified manner for multiple users.
+
+## Precautions
+
+- The GUC parameter **db4ai_snapshot_mode** classifies the snapshot storage model into MSS and CSS. The GUC parameter **db4ai_snapshot_version_delimiter** specifies the version separator and its default value is **@**. The GUC parameter **db4ai_snapshot_version_separator** specifies the sub-version separator and its default value is **.**.
+- When the incremental storage mode is used for snapshots, the snapshots are dependent on each other. Snapshots must be deleted in the dependency sequence.
+- The snapshot feature is used to maintain data between team members, involving data transcription between administrators and common users. Therefore, the snapshot feature is not supported in private user and separation of duty (**enableSeparationOfDuty** is set to **ON**) scenarios.
+- When you need a stable and available snapshot for tasks such as AI training, you need to publish the snapshot.
+
+## Syntax
+
+1. Create a snapshot.
+
+   You can run the **CREATE SNAPSHOT… AS** and **CREATE SNAPSHOT… FROM** statements to create a data table snapshot.
+
+   - CREATE SNAPSHOT AS
+
+        ```ebnf+diagram
+        CreateSnapshotAs ::= CREATE SNAPSHOT qualified_name '@'[ version | ident | sconst]
+            [COMMENT IS 'sconst' AS query];
+        ```
+
+    - CREATE SNAPSHOT FROM
+
+        ```ebnf+diagram
+        CreateSnapshotFrom ::= CREATE SNAPSHOT 'qualified_name'  '@' [ version | ident | sconst]
+            FROM '@'  [version | ident | sconst ]
+            [COMMENT IS 'sconst'
+                USING (
+                { INSERT [INTO SNAPSHOT] '…'
+                | UPDATE [SNAPSHOT] [AS 'alias'] SET '…' [FROM '…'] [WHERE' …']
+                | DELETE [FROM SNAPSHOT] [AS 'alias'] [USING '…'] [WHERE '…']
+                | ALTER [SNAPSHOT] { ADD '… '| DROP '…' } [, '…']
+            } [;'...'])];
+        ```
+
+2. Delete a snapshot.
+
+   PURGE SNAPSHOT
+
+   ```ebnf+diagram
+   PurgeSnapshot ::= PURGE SNAPSHOT 'qualified_name' '@'  [version | ident | sconst];
+   ```
+
+3. Sample snapshots.
+
+   SAMPLE SNAPSHOT
+
+   ```ebnf+diagram
+   SampleSnapshot ::= SAMPLE SNAPSHOT [qualified_name] '@' [version | ident | sconst]
+       [STRATIFY BY attr_list]
+       { AS [label] AT RATIO [num] [COMMENT IS [comment]] } [, '…']
+   ```
+
+4. Publish snapshots.
+
+   PUBLISH SNAPSHOT
+
+   ```ebnf+diagram
+   PublishSnapshot ::= PUBLISH SNAPSHOT [qualified_name] '@'  [version | ident | sconst];
+   ```
+
+5. Archive snapshots.
+
+   ARCHIVE SNAPSHOT
+
+   ```ebnf+diagram
+   ArchiveSnapshot ::= ARCHIVE SNAPSHOT [qualified_name] '@ '[version | ident | sconst];
+   ```
+
+## Parameter Description
+
+- qualified_name
+
+  Name of the snapshot to be created
+
+  Value range: a string. It must comply with the identifier naming convention.
+
+- version
+
+  (Optional) Version number of a snapshot. This parameter is optional. The system automatically extends the sequence number.
+
+  Value range: string, consisting of numbers and separators.
+
+## Examples
+
+```
+create snapshot s1@1.0 comment is 'first version' as select * from t1;
+create snapshot s1@3.0 from @1.0 comment is 'inherits from @1.0' using (INSERT VALUES(6, 'john'), (7, 'tim'); DELETE WHERE id = 1);
+SELECT * FROM s1@1.0;
+purge snapshot s1@1.0;
+sample snapshot s1@2.0 stratify by name as nick at ratio .5;
+publish snapshot s1@2.0;
+archive snapshot s1@2.0;
+```
+
+## Helpful Links
+
+None
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/134-START-TRANSACTION.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/134-START-TRANSACTION.md
new file mode 100644
index 0000000000000000000000000000000000000000..faec6d587a09c3a0770dd8378110a396dc55416c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/134-START-TRANSACTION.md
@@ -0,0 +1,88 @@
+---
+title: START TRANSACTION
+summary: START TRANSACTION
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# START TRANSACTION
+
+## Function
+
+**START TRANSACTION** starts a transaction. If the isolation level or read/write mode is specified, a new transaction will have those characteristics. You can also specify them using **SET TRANSACTION**.
+
+## Precautions
+
+None
+
+## Syntax
+
+Format 1: START TRANSACTION
+
+```ebnf+diagram
+StartTransaction ::= START TRANSACTION
+  [
+    {
+       ISOLATION LEVEL { READ COMMITTED | SERIALIZABLE | REPEATABLE READ }
+       | { READ WRITE | READ ONLY }
+     } [, ...]
+  ];
+```
+
+Format 2: BEGIN
+
+```ebnf+diagram
+Begin ::= BEGIN [ WORK | TRANSACTION ]
+  [
+    {
+       ISOLATION LEVEL { READ COMMITTED | SERIALIZABLE | REPEATABLE READ }
+       | { READ WRITE | READ ONLY }
+      } [, ...]
+  ];
+```
+
+## Parameter Description
+
+- **WORK | TRANSACTION**
+
+  Specifies the optional keyword in BEGIN format without functions.
+
+- **ISOLATION LEVEL**
+
+  Specifies the transaction isolation level that determines the data that a transaction can view if other concurrent transactions exist.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  > The isolation level of a transaction cannot be reset after the first clause (**SELECT**, **INSERT**, **DELETE**, **UPDATE**, **FETCH**, **COPY**) for modifying data is executed in the transaction.
+
+  Value range:
+
+  - **READ COMMITTED**: Only submitted data is read. It is the default value.
+  - **REPEATABLE READ**: Only the data committed before transaction start is read. Uncommitted data or data committed in other concurrent transactions cannot be read.
+  - **SERIALIZABLE**: Currently, this isolation level is not supported in MogDB. It is equivalent to **REPEATABLE READ**.
+
+- **READ WRITE | READ ONLY**
+
+  Specifies the transaction access mode (read/write or read only).
+
+## Examples
+
+```sql
+-- Start a transaction in default mode.
+mogdb=# START TRANSACTION;
+mogdb=# SELECT * FROM tpcds.reason;
+mogdb=# END;
+
+-- Start a transaction in default mode.
+mogdb=# BEGIN;
+mogdb=# SELECT * FROM tpcds.reason;
+mogdb=# END;
+
+-- Start a transaction with the isolation level being READ COMMITTED and the access mode being READ WRITE:
+mogdb=# START TRANSACTION ISOLATION LEVEL READ COMMITTED READ WRITE;
+mogdb=# SELECT * FROM tpcds.reason;
+mogdb=# COMMIT;
+```
+
+## Helpful Links
+
+[COMMIT | END](39-COMMIT-END), [ROLLBACK](121-ROLLBACK), and [SET TRANSACTION](131-SET-TRANSACTION)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/134.1-TIMECAPSULE-TABLE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/134.1-TIMECAPSULE-TABLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..bcaddf3077a687f4bd356b3a9e02462cdd526915
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/134.1-TIMECAPSULE-TABLE.md
@@ -0,0 +1,122 @@
+---
+title: TIMECAPSULE TABLE
+summary: TIMECAPSULE TABLE
+author: Zhang Cuiping
+date: 2021-11-01
+---
+
+# TIMECAPSULE TABLE
+
+## Function
+
+The **TIMECAPSULE TABLE** statement restores a table to an earlier state in the event of human or application errors.
+
+The table can flash back to a past point in time, depending on the old version of the data stored in the system. In addition, MogDB cannot restore a table to an earlier state through DDL operations that change the structure of the table.
+
+## Precautions
+
+- The **TIMECAPSULE TABLE** statement can be used to flash back the data of the old version or the data from the recycle bin.
+
+  - **TO TIMECAPSULE** and **TO CSN** can flash back a table to an earlier version.
+  - The recycle bin records the objects dropped or truncated by running **DROP** and **TRUNCATE**. **TO BEFORE DROP** and **TO BEFORE TRUNCATE** flash back from the recycle bin.
+
+- The following object types do not support flashback: system catalogs, column-store tables, memory tables, DFS tables, global temporary tables, local temporary tables, unlogged tables, sequence tables, and hash bucket tables.
+
+- Between the flashback point and the current point, a statement (**DDL**, **DCL**, or **VACUUM FULL**) that modifies the table structure or affects physical storage has been executed. Therefore, the flashback fails.
+
+- To run **DROP**, you must have the **create** or **usage** permission of the schema to which the junk object belongs, and you must be the owner of the schema or the owner of the junk object.
+
+  To run **TRUNCATE**, you must have the **create** or **usage** permission of the schema to which the junk object belongs, and you must be the owner of the schema or the junk object. In addition, you must have the **TRUNCATE** permission of the junk object.
+
+- Scenarios or tables that do not support DROP or TRUNCATE FLASHBACK
+
+  - Scenario where the recycle bin is disabled (**enable_recyclebin** is set to **off**)
+  - Scenario where the system is being maintained (**xc_maintenance_mode** is set to **on**) or is being upgraded
+  - Scenario where multiple objects are deleted (The **DROP** or **TRUNCATE TABLE** command is executed to delete multiple objects at the same time.)
+  - System catalogs, column-store tables, memory tables, DFS tables, global temporary tables, local temporary tables, unlogged tables, sequence tables, and hash bucket tables
+
+## Syntax
+
+```ebnf+diagram
+TimecapsuleTable ::= TIMECAPSULE TABLE [ schema_name'.']table_name TO {CSN expr | TIMESTAMP expr | BEFORE { DROP [RENAME TO table_name] | TRUNCATE } }
+```
+
+## Parameter Description
+
+- **schema_name**
+
+  Specifies a schema containing the table to be flashed back. If this parameter is not specified, the current schema is used.
+
+- **table_name**
+
+  Specifies a table name.
+
+- **TO CSN**
+
+  Specifies the CSN corresponding to the time point when the table is to be flashed back. *expr* must be a number representing a valid CSN.
+
+- **TO TIMESTAMP**
+
+  Specifies a timestamp value corresponding to the point in time to which you want to flash back the table. The result of *expr* must be a valid past timestamp (convert a string to a time type using the **TO_TIMESTAMP** function). The table will be flashed back to a time within approximately 3 seconds of the specified timestamp.
+
+  Note: When the flashback point is too old, the old version cannot be obtained because it is recycled. As a result, the flashback fails and the error message "Restore point too old" is displayed. You can set the retention period of the old version by setting **vacuum_defer_cleanup_age** and **version_retention_age** to the same value.
+
+- **TO BEFORE DROP**
+
+  Retrieves dropped tables and their subobjects from the recycle bin.
+
+  You can specify either the original user-specified name of the table or the system-generated name assigned to the object when it was deleted.
+
+  - System-generated recycle bin object names are unique. Therefore, if you specify the system-generated name, the database retrieves that specified object. To see the content in your recycle bin, run **select \* from gs_recyclebin;**.
+  - If you specify the user-specified name and the recycle bin contains more than one object of that name, the database retrieves the object that was moved to the recycle bin most recently. If you want to retrieve an older version of the table, then do one of these things:
+    - Specify the system-generated recycle bin name of the table you want to retrieve.
+    - Run the **TIMECAPSULE TABLE … TO BEFORE DROP** statement until you retrieve the table you want.
+  - When a dropped table is restored, only the base table name is restored, and the names of other subobjects remain the same as those in the recycle bin. You can run the DDL command to manually change the names of subobjects as required.
+  - The recycle bin does not support write operations such as DML, DCL, and DDL, and does not support DQL query operations (supported in later versions).
+  - The **recyclebin_retention_time** parameter has been set for specifying the retention period of objects in the recycle bin. The objects will be automatically deleted after the retention period expires.
+
+- **RENAME TO**
+
+  Specifies a new name for the table retrieved from the recycle bin.
+
+- **TRUNCATE**
+
+  Flashes back to the point in time before the TRUNCATE operation.
+
+## Examples
+
+```
+-- Delete the tpcds.reason_t2 table.
+DROP TABLE IF EXISTS tpcds.reason_t2;
+-- Create the tpcds.reason_t2 table.
+mogdb=# CREATE TABLE tpcds.reason_t2
+ (
+  r_reason_sk    integer,
+  r_reason_id    character(16),
+  r_reason_desc  character(100)
+  );
+-- Insert records into the tpcds.reason_t2 table.
+mogdb=#  INSERT INTO tpcds.reason_t2 VALUES (1, 'AA', 'reason1'),(2, 'AB', 'reason2'),(3, 'AC', 'reason3');
+INSERT 0 3
+-- Delete data from the tpcds.reason_t2 table.
+mogdb=#  TRUNCATE TABLE tpcds.reason_t2;
+-- Query data in the tpcds.reason_t2 table.
+mogdb=#  select * from tpcds.reason_t2;
+ r_reason_sk | r_reason_id | r_reason_desc
+-------------+-------------+---------------
+(0 rows)
+-- Perform the TRUNCATE FLASHBACK operation.
+mogdb=#  TIMECAPSULE TABLE tpcds.reason_t2 to BEFORE TRUNCATE;
+mogdb=#  select * from tpcds.reason_t2;
+ r_reason_sk |   r_reason_id    |                                            r_reason_desc
+-------------+------------------+------------------------------------------------------------------------------------------------------
+           1 | AA               | reason1
+           2 | AB               | reason2
+           3 | AC               | reason3
+(3 rows)
+-- Delete the tpcds.reason_t2 table.
+mogdb=#  DROP TABLE tpcds.reason_t2;
+-- Perform the DROP FLASHBACK operation.
+mogdb=#  TIMECAPSULE TABLE tpcds.reason_t2 to BEFORE DROP;
+TimeCapsule Table
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/135-TRUNCATE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/135-TRUNCATE.md
new file mode 100644
index 0000000000000000000000000000000000000000..d7d0509c2d96a3dd3f76896ff9d9c2969275b3c2
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/135-TRUNCATE.md
@@ -0,0 +1,130 @@
+---
+title: TRUNCATE
+summary: TRUNCATE
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# TRUNCATE
+
+## Function
+
+**TRUNCATE** quickly removes all rows from a database table.
+
+It has the same effect as an unqualified **DELETE** on each table, but it is faster since it does not actually scan the tables. This is most useful on large tables.
+
+## Precautions
+
+- **TRUNCATE TABLE** has the same function as a **DELETE** statement with no **WHERE** clause, emptying a table.
+- **TRUNCATE TABLE** uses less system and transaction log resources as compared with **DELETE**.
+  - **DELETE** deletes a row each time, and records the deletion of each row in the transaction log.
+  - **TRUNCATE TABLE** deletes all rows in a table by releasing the data page storing the table data, and records the releasing of the data page only in the transaction log.
+- The differences between **TRUNCATE**, **DELETE**, and **DROP** are as follows:
+  - **TRUNCATE TABLE** deletes content, releases space, but does not delete definitions.
+  - **DELETE TABLE** deletes content, but does not delete definitions nor release space.
+  - **DROP TABLE** deletes content and definitions, and releases space.
+
+## Syntax
+
+- Delete data from a table.
+
+  ```ebnf+diagram
+  Truncate ::= TRUNCATE {[ TABLE ] [ ONLY ] {table_name [ * ]} [, ... ]
+  [ CONTINUE IDENTITY ] [ CASCADE | RESTRICT][PURGE]};
+  ```
+
+- Truncate the data in a partition.
+
+  ```ebnf+diagram
+  TruncatePartition ::= ALTER TABLE [ IF EXISTS  ] { [ ONLY  ] table_name
+                         | table_name *
+                         | ONLY ( table_name )  }
+  TRUNCATE PARTITION { partition_name
+                     | FOR (  partition_value  [, ...] )  } [ UPDATE GLOBAL INDEX ];
+  ```
+
+## Parameter Description
+
+- **ONLY**
+
+  If **ONLY** is specified, only the specified table is cleared. Otherwise, the table and all its subtables (if any) are cleared.
+
+- **table_name**
+
+  Specifies the name (optionally schema-qualified) of the target table.
+
+  Value range: an existing table name
+
+- **CONTINUE IDENTITY**
+
+  Does not change the values of sequences. This is the default action.
+
+- **CASCADE | RESTRICT**
+
+  - **CASCADE**: clears all tables that are added to a group.
+  - **RESTRICT** (default value): clears all data.
+
+- **PURGE**: purges table data in the recycle bin by default.
+
+- **partition_name**
+
+  Specifies the partition in the target partitioned table.
+
+  Value range: an existing table name
+
+- **partition_value**
+
+  Specifies the value of the specified partition key.
+
+  The value specified by **PARTITION FOR** can uniquely identify a partition.
+
+  Value range: value range of the partition key for the partition to be renamed
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+  > When the **PARTITION FOR** clause is used, the entire partition where **partition_value** is located is cleared.
+
+- **UPDATE GLOBAL INDEX**
+
+  If this parameter is used, all global indexes in the partitioned table are updated to ensure that data can be queried correctly using global indexes. If this parameter is not used, all global indexes in the partitioned table will become invalid.
+
+## Example
+
+```sql
+-- Create a table.
+mogdb=# CREATE TABLE tpcds.reason_t1 AS TABLE tpcds.reason;
+
+-- Truncate the tpcds.reason_t1 table.
+mogdb=# TRUNCATE TABLE tpcds.reason_t1;
+
+-- Delete the table.
+mogdb=# DROP TABLE tpcds.reason_t1;
+Copy Code-- Create a partitioned table.
+mogdb=# CREATE TABLE tpcds.reason_p
+(
+  r_reason_sk integer,
+  r_reason_id character(16),
+  r_reason_desc character(100)
+)PARTITION BY RANGE (r_reason_sk)
+(
+  partition p_05_before values less than (05),
+  partition p_15 values less than (15),
+  partition p_25 values less than (25),
+  partition p_35 values less than (35),
+  partition p_45_after values less than (MAXVALUE)
+);
+
+-- Insert data.
+mogdb=# INSERT INTO tpcds.reason_p SELECT * FROM tpcds.reason;
+
+-- Clear the p_05_before partition.
+mogdb=# ALTER TABLE tpcds.reason_p TRUNCATE PARTITION p_05_before;
+
+-- Clear the p_15 partition.
+mogdb=# ALTER TABLE tpcds.reason_p TRUNCATE PARTITION for (13);
+
+-- Clear the partitioned table.
+mogdb=# TRUNCATE TABLE tpcds.reason_p;
+
+-- Delete the table.
+mogdb=# DROP TABLE tpcds.reason_p;
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/136-UPDATE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/136-UPDATE.md
new file mode 100644
index 0000000000000000000000000000000000000000..ae5c6977c8a40251eac719b8ffc23eb9db7ca5f8
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/136-UPDATE.md
@@ -0,0 +1,136 @@
+---
+title: UPDATE
+summary: UPDATE
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# UPDATE
+
+## Function
+
+**UPDATE** updates data in a table. **UPDATE** changes the values of the specified columns in all rows that satisfy the condition. The **WHERE** clause clarifies conditions. The columns to be modified need to be mentioned in the **SET** clause; columns not explicitly modified retain their previous values.
+
+## Precautions
+
+- You must have the **UPDATE** permission on a table to be updated.
+- You must have the **SELECT** permission on all tables involved in the expressions or conditions.
+- For column-store tables, the **RETURNING** clause is currently not supported.
+- Column-store tables do not support non-deterministic update. If you update data in one row with multiple rows of data in a column-store table, an error will be reported.
+- Memory space that records update operations in column-store tables is not reclaimed. You need to clean it by executing **VACUUM FULL table_name**.
+- Currently, **UPDATE** cannot be used in column-store replication tables.
+
+## Syntax
+
+```ebnf+diagram
+Update ::= UPDATE [/*+ plan_hint */] [ ONLY ] table_name [ * ] [ [ AS ] alias ]
+SET {column_name = { expression | DEFAULT }
+    |( column_name [, ...] ) = {( { expression | DEFAULT } [, ...] ) |sub_query }}[, ...]
+    [ FROM from_list] [ WHERE condition ]
+    [ RETURNING {*
+                | {output_expression [ [ AS ] output_name ]} [, ...] }];
+```
+
+Where sub_query can be:
+
+```ebnf+diagram
+sub_query ::= SELECT [ ALL | DISTINCT [ ON ( expression [, ...] ) ] ]
+{ * | {expression [ [ AS ] output_name ]} [, ...] }
+[ FROM from_item [, ...] ]
+[ WHERE condition ]
+[ GROUP BY grouping_element [, ...] ]
+[ HAVING condition [, ...] ]
+```
+
+## Parameter Description
+
+- **plan_hint** clause
+
+  Follows the **UPDATE** keyword in the **/\*+ \*/** format. It is used to optimize the plan of an **UPDATE** statement block. For details, see [Hint-based Tuning](9-hint-based-tuning). In each statement, only the first /\***+** _plan_hint _\*/ comment block takes effect as a hint. Multiple hints can be written.
+
+- **table_name**
+
+  Specifies the name (optionally schema-qualified) of the table to be updated.
+
+  Value range: an existing table name
+
+- **alias**
+
+  Specifies a substitute name for the target table.
+
+  Value range: a string. It must comply with the naming convention rule.
+
+- **column_name**
+
+  Specifies the name of the column to be modified.
+
+  You can refer to this column by specifying the target table alias and the column name. For example:
+
+  UPDATE foo AS f SET f.col_name = 'namecol';
+
+  Value range: an existing column
+
+- **expression**
+
+  Specifies a value assigned to a column or an expression that assigns the value.
+
+- **DEFAULT**
+
+  Specifies the default value of a column.
+
+  The value is **NULL** if no specified default value has been assigned to it.
+
+- **sub_query**
+
+  Specifies a subquery.
+
+  This statement can be executed to update a table with information for other tables in the same database. For details about clauses in the **SELECT** statement, see **SELECT**.
+
+- **from_list**
+
+  Specifies a list of table expressions, allowing columns from other tables to appear in the **WHERE** condition and the update expressions. This is similar to the list of tables that can be specified in the **FROM** clause of a **SELECT** statement.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+  > Note that the target table must not appear in the **from_list**, unless you intend a self-join (in which case it must appear with an alias in the **from_list**).
+
+- **condition**
+
+  Specifies an expression that returns a value of type Boolean. Only rows for which this expression returns **true** are updated.
+
+- **output_expression**
+
+  Specifies an expression to be computed and returned by the **UPDATE** statement after each row is updated.
+
+  Value range: The expression can use any column names of the table named by **table_name** or table(s) listed in **FROM**. Write * to return all columns.
+
+- **output_name**
+
+  Specifies a name to use for a returned column.
+
+## Examples
+
+```sql
+-- Create a table student1.
+mogdb=# CREATE TABLE student1
+(
+   stuno     int,
+   classno   int
+);
+
+-- Insert data.
+mogdb=# INSERT INTO student1 VALUES(1,1);
+mogdb=# INSERT INTO student1 VALUES(2,2);
+mogdb=# INSERT INTO student1 VALUES(3,3);
+
+-- View data.
+mogdb=# SELECT * FROM student1;
+
+-- Update the values of all records.
+mogdb=# UPDATE student1 SET classno = classno*2;
+
+-- View data.
+mogdb=# SELECT * FROM student1;
+
+-- Delete the table.
+mogdb=# DROP TABLE student1;
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/137-VACUUM.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/137-VACUUM.md
new file mode 100644
index 0000000000000000000000000000000000000000..cf183f106fafb6f2653bf8a85192323baec5acce
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/137-VACUUM.md
@@ -0,0 +1,119 @@
+---
+title: VACUUM
+summary: VACUUM
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# VACUUM
+
+## Function
+
+**VACUUM** recycles storage space occupied by tables or **B-Tree** indexes. In normal database operation, rows that have been deleted are not physically removed from their table; they remain present until a **VACUUM** is done. Therefore, it is necessary to do **VACUUM** periodically, especially on frequently-updated tables.
+
+## Precautions
+
+- With no table specified, **VACUUM** processes all the tables that the current user has permission to vacuum in the current database. With a parameter, **VACUUM** processes only that table.
+- To vacuum a table, you must ordinarily be the table's owner or the system administrator. However, database owners are allowed to **VACUUM** all tables in their databases, except shared catalogs. (The restriction for shared catalogs means that a true database-wide **VACUUM** can only be executed by the system administrator). **VACUUM** skips over any tables that the calling user does not have the permission to vacuum.
+- **VACUUM** cannot be executed inside a transaction block.
+- It is recommended that active production databases be vacuumed frequently (at least nightly), in order to remove dead rows. After adding or deleting a large number of rows, it might be a good idea to run **VACUUM ANALYZE** for the affected table. This will update the system catalogs with the results of all recent changes, and allow the query planner to make better choices in planning queries.
+- **FULL** is recommended only in special scenarios. For example, you wish to physically narrow the table to decrease the occupied disk space after deleting most rows of a table. **VACUUM FULL** usually shrinks a table more than **VACUUM** does. The **FULL** option does not clear indexes. You are advised to periodically run the **REINDEX** statement. Deleting all indexes, running **VACUUM FULL**, and rebuilding indexes is usually a faster choice. If the physical space usage does not decrease after you run the statement, check whether there are other active transactions (that have started before you delete data transactions and not ended before you run **VACUUM FULL**). If there are such transactions, run this statement again when the transactions quit.
+- **VACUUM** causes a substantial increase in I/O traffic, which might cause poor performance for other active sessions. Therefore, it is sometimes advisable to use the cost-based VACUUM delay feature.
+- When **VERBOSE** is specified, **VACUUM** prints progress messages to indicate which table is currently being processed. Various statistics about the tables are printed as well. However, if you execute **VACUUM** and specify the **VERBOSE** option for column-store tables, no information is returned.
+- When the option list is surrounded by parentheses, the options can be written in any order. If there are no brackets, the options must be given in the order displayed in the syntax.
+- **VACUUM** and **VACUUM FULL** clear deleted tuples after the delay specified by **vacuum_defer_cleanup_age**.
+- **VACUUM ANALYZE** executes a VACUUM operation and then an ANALYZE operation for each selected table. This is a handy combination form for routine maintenance scripts.
+- Plain **VACUUM** (without **FULL**) simply reclaims space and makes it available for reuse. This form of statement can operate in parallel with normal reading and writing of the table, as an exclusive lock is not obtained. **VACUUM FULL** executes wider processing, including moving rows across blocks to compress tables so they occupy the minimum number of disk blocks. This form is much slower and requires an exclusive lock on each table while it is being processed.
+- When you do **VACUUM** to a column-store table, the following operations are internally performed: data in the delta table is migrated to the primary table, and the delta and desc tables of the primary table are vacuumed. **VACUUM** does not reclaim the storage space of the delta table. To reclaim it, do **VACUUM DELTAMERGE** to the column-store table.
+- A deadlock may occur when multiple **VACUUM FULL** statements are executed simultaneously.
+- If the **xc_maintenance_mode** parameter is not enabled, the **VACUUM FULL** operation will skip all system catalogs.
+- If you run **VACUUM FULL** immediately after running **DELETE**, the space will not be recycled. After executing **DELETE**, execute 1000 non-SELECT transactions, or wait for 1s and then execute one transaction. Then, run **VACUUM FULL** to the space.
+
+## Syntax
+
+- Reclaim space and update statistics information, no requirements for keyword orders.
+
+  ```ebnf+diagram
+  Vacuum ::= VACUUM [ ( { FULL | FREEZE | VERBOSE | {ANALYZE | ANALYSE }} [,...] ) ]
+      [ table_name [ (column_name [, ...] ) ] ] [ PARTITION ( partition_name ) ];
+  ```
+
+- Reclaim space, without updating statistics information.
+
+  ```ebnf+diagram
+  Vacuum ::= VACUUM [ FULL [COMPACT] ] [ FREEZE ] [ VERBOSE ] [ table_name ] [ PARTITION ( partition_name ) ];
+  ```
+
+- Reclaim space and update statistics information, and require keywords in order.
+
+  ```ebnf+diagram
+  Vacuum ::= VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] { ANALYZE | ANALYSE } [ VERBOSE ]
+      [ table_name [ (column_name [, ...] ) ] ] [ PARTITION ( partition_name ) ];
+  ```
+
+## Parameter Description
+
+- **FULL**
+
+  Selects "FULL" vacuum, which can reclaim more space, but takes much longer and exclusively locks the table.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  > Using **FULL** will cause statistics missing. To collect statistics, add the keyword **ANALYZE** to **VACUUM FULL**.
+
+- **FREEZE**
+
+  Is equivalent to running **VACUUM** with the **vacuum_freeze_min_age** parameter set to **zero**.
+
+- **VERBOSE**
+
+  Prints a detailed VACUUM activity report for each table.
+
+- **ANALYZE | ANALYSE**
+
+  Updates statistics used by the planner to determine the most efficient way to execute a query.
+
+- **table_name**
+
+  Specifies the name (optionally schema-qualified) of a specific table to vacuum.
+
+  Value range: name of a specific table to vacuum Defaults are all tables in the current database.
+
+- **column_name**
+
+  Specifies the name of the column to be analyzed. This parameter must be used together with **ANALYZE**.
+
+  Value range: name of a specific field to analyze Defaults are all columns.
+
+- **PARTITION**
+
+  **COMPACT** and **PARTITION** cannot be used at the same time.
+
+- **partition_name**
+
+  Specifies the partition name of the table to be cleared. Defaults are all partitions.
+
+- **DELTAMERGE**
+
+  (For column-store tables) Migrates data from the delta table to primary tables. For a column-store table, this operation is controlled by **deltarow_threshold**. For details, see **enable_delta_store** and **Parameter Description**.
+
+## Examples
+
+```sql
+-- Create an index in the tpcds.reason tabletable:
+mogdb=# CREATE UNIQUE INDEX ds_reason_index1 ON tpcds.reason(r_reason_sk);
+
+-- Vacuum the tpcds.reason table that has indexes:
+mogdb=# VACUUM (VERBOSE, ANALYZE) tpcds.reason;
+
+-- Drop an index.
+mogdb=# DROP INDEX ds_reason_index1 CASCADE;
+mogdb=# DROP TABLE tpcds.reason;
+```
+
+## Suggestions
+
+- vacuum
+  - **VACUUM** cannot be executed inside a transaction block.
+  - It is recommended that active production databases be vacuumed frequently (at least nightly), in order to remove dead rows. It is strongly recommended that you run **VACUUM ANALYZE** after adding or deleting a large number of records.
+  - **FULL** is recommended only in special scenarios. For example, you wish to physically narrow the table to decrease the occupied disk space after deleting most rows of a table.
+  - Before performing the VACUUM FULL operation, you are advised to delete all indexes in related tables, run **VACUUM FULL**, and then re-create the index.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/138-VALUES.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/138-VALUES.md
new file mode 100644
index 0000000000000000000000000000000000000000..453023101f031699664445ea7da4415b3e18c6d9
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/138-VALUES.md
@@ -0,0 +1,67 @@
+---
+title: VALUES
+summary: VALUES
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# VALUES
+
+## Function
+
+**VALUES** computes a row or a set of rows based on given values. It is most commonly used to generate a constant table within a large statement.
+
+## Precautions
+
+- **VALUES** lists with large numbers of rows should be avoided, as you might encounter out-of-memory failures or poor performance. **VALUES** appearing within **INSERT** is a special case, because the desired column types are known from the **INSERT**'s target table, and need not be inferred by scanning the **VALUES** list. In this case, **VALUE** can handle larger lists than are practical in other contexts.
+- If more than one row is specified, all the rows must have the same number of elements.
+
+## Syntax
+
+```ebnf+diagram
+Values ::= VALUES {( expression [, ...] )} [, ...]
+    [ ORDER BY { sort_expression [ ASC | DESC | USING operator ] } [, ...] ]
+    [ LIMIT { count | ALL } ]
+    [ OFFSET start [ ROW | ROWS ] ]
+    [ FETCH { FIRST | NEXT } [ count ] { ROW | ROWS } ONLY ];
+```
+
+## Parameter Description
+
+- **expression**
+
+  Specifies a constant or expression to compute and insert at the indicated place in the resulting table or set of rows.
+
+  In a **VALUES** list appearing at the top level of an **INSERT**, an expression can be replaced by **DEFAULT** to indicate that the destination column's default value should be inserted. **DEFAULT** cannot be used when **VALUES** appears in other contexts.
+
+- **sort_expression**
+
+  Specifies an expression or integer constant indicating how to sort the result rows.
+
+- **ASC**
+
+  Specifies an ascending sort order.
+
+- **DESC**
+
+  Specifies a descending sort order.
+
+- **operator**
+
+  Specifies a sorting operator.
+
+- **count**
+
+  Specifies the maximum number of rows to return.
+
+- **OFFSET start { ROW | ROWS }**
+
+  Specifies the maximum number of returned rows, whereas **start** specifies the number of rows to skip before starting to return rows.
+
+- **FETCH { FIRST | NEXT } [ count ] { ROW | ROWS } ONLY**
+
+  The **FETCH** clause restricts the total number of rows starting from the first row of the return query result, and the default value of **count** is **1**.
+
+## Examples
+
+See [Examples](109-INSERT#examples) in **INSERT**.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/139-CONNECT-BY.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/139-CONNECT-BY.md
new file mode 100644
index 0000000000000000000000000000000000000000..04061a42d798e691fe5bd66f6aca29df1dc7eefb
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/139-CONNECT-BY.md
@@ -0,0 +1,207 @@
+---
+title: CONNECT BY
+summary: CONNECT BY
+author: Guo Huan
+date: 2021-01-11
+---
+
+# CONNECT BY
+
+## Function
+
+- Support oracle-compatible **connect by** syntax，support data query control of level structure and display level, loop, starting level, etc.
+- Provide oracle-compatible level query function, which can display data content, data level, path, etc. according to the specified connection relationship, starting conditions, etc. in a tree structure.
+- Specify the root rows of the level query by the **start with condition**, and perform a recursive query based on those rows to fetch all child rows, as well as child rows of child rows, etc.
+- The **connect by condition** specifies the parent-child relationship between the level to determine all child rows of each row that satisfy the condition.
+
+## Precautions
+
+- If a connection exists, either in the connect statement, or in the from or where clause, the result set after the connection is fetched first, and then the cascading query is performed.
+- If there is a **where** filter condition in the statement, execute the cascading query first before filtering the result set, instead of filtering out the unsatisfied rows and all their children.
+- You can use the **level pseudo-column** to view the level where the row is located, **sys_connect_by_path** to view the path from the root row to the row, and **connect_by_root** to view the root row, and other auxiliary functions.
+
+## Syntax
+
+```ebnf+diagram
+ConnectBy ::= [ START WITH condition ]  CONNECT BY [ NOCYCLE ] condition [ ORDER SIBLINGS BY expr ]
+```
+
+**condition** represents the parent column information by the **PRIOR** modifier, and there can have multiple conditions, as follows:
+
+- PRIOR expr = expr
+- expr = PRIOR expr
+
+## Parameter Description
+
+- **START WITH** is a condition that the root node data of the level data needs to meet.
+
+- **CONNECT BY condition** can be a compound condition and supports multiple **PRIOR**. For example:
+
+  ```sql
+  CONNECT BY last_name != 'King' AND PRIOR employee_id = manager_id ...
+  CONNECT BY PRIOR employee_id = manager_id and
+  PRIOR account_mgr_id = customer_id ...
+  ```
+
+- **NOCYCLE** means that the database returns data even if the data exists in a loop.
+
+- Pseudo columns such as level, sys_connect_by_path, connect_by_root, etc.
+
+  - **level** indicates the number of layers where the row of data is located.
+  - **sys_connect_by_path (cname,’delimiter’)** represents the path of the **cname** column from **root** to the row.
+  - The **connect_by_root** modifier modifies the column name and displays the root value of the column.
+
+    ```sql
+    SELECT last_name "Employee", CONNECT_BY_ROOT last_name "Manager",
+    LEVEL-1 "Pathlen", SYS_CONNECT_BY_PATH(last_name, '/') "Path"
+    FROM employees
+    WHERE LEVEL > 1 and department_id = 110
+    CONNECT BY PRIOR employee_id = manager_id;
+    Employee   Manager     Pathlen    Path
+    --------------- ------------ ---------- -----------------------------------
+    Higgins Kochhar 1 /Kochhar/Higgins
+    Gietz Kochhar 2 /Kochhar/Higgins/Gietz
+    Gietz Higgins 1 /Higgins/Gietz
+    Higgins King 2 /King/Kochhar/Higgins
+    Gietz King 3 /King/Kochhar/Higgins/Gietz
+    ```
+
+- **ORDER SIBLINGS BY**
+
+  Keep the returned data of the level query in order between the same levels. For example:
+
+  ```sql
+  select t.*, level from employee t
+  start with t.managerid = 'xx'
+  connect by prior t.empid = t.managerid
+  order siblings by name desc;
+  ```
+
+## Examples
+
+```sql
+create table mogdb210_connectby_01
+(id int,
+ pid int,
+ note varchar(20)
+);
+insert into mogdb210_connectby_01 values(1,null,'A01');
+insert into mogdb210_connectby_01 values(101,1,'X01');
+insert into mogdb210_connectby_01 values(201,101,'Y01');
+insert into mogdb210_connectby_01 values(202,101,'Y02');
+insert into mogdb210_connectby_01 values(301,201,'Z01');
+insert into mogdb210_connectby_01 values(302,201,'Z02');
+insert into mogdb210_connectby_01 values(303,202,'Z03');
+insert into mogdb210_connectby_01 values(304,202,'Z04');
+```
+
+**Only add the connect by keyword (each row of the base table is used as the root row to get all the lower rows according to the connect by condition)**
+
+```sql
+select id,pid,note,level,connect_by_root id,connect_by_root pid,connect_by_root note,sys_connect_by_path(note,'/') 
+from mogdb210_connectby_01
+connect by id = pid 
+order by id,pid;
+ id  | pid | note | level | connect_by_rootid | connect_by_rootpid | connect_by_rootnote | sys_connect_by_path 
+-----+-----+------+-------+-------------------+--------------------+---------------------+---------------------
+   1 |     | A01  |     1 |                 1 |                    | A01                 | /A01
+ 101 |   1 | X01  |     1 |               101 |                  1 | X01                 | /X01
+ 201 | 101 | Y01  |     1 |               201 |                101 | Y01                 | /Y01
+ 202 | 101 | Y02  |     1 |               202 |                101 | Y02                 | /Y02
+ 301 | 201 | Z01  |     1 |               301 |                201 | Z01                 | /Z01
+ 302 | 201 | Z02  |     1 |               302 |                201 | Z02                 | /Z02
+ 303 | 202 | Z03  |     1 |               303 |                202 | Z03                 | /Z03
+ 304 | 202 | Z04  |     1 |               304 |                202 | Z04                 | /Z04
+(8 rows)
+```
+
+**Add nocycle keyword (without the keyword, if there is a loop between levels will report an error, add the nocycle keyword, a line of the subline if there is a loop to skip the subline and continue to output other results)**
+
+```sql
+select id,pid,note,level,connect_by_root id,connect_by_root pid,connect_by_root note,sys_connect_by_path(note,'/') 
+from mogdb210_connectby_01
+connect by nocycle id = pid 
+order by id,pid;
+ id  | pid | note | level | connect_by_rootid | connect_by_rootpid | connect_by_rootnote | sys_connect_by_path 
+-----+-----+------+-------+-------------------+--------------------+---------------------+---------------------
+   1 |     | A01  |     1 |                 1 |                    | A01                 | /A01
+ 101 |   1 | X01  |     1 |               101 |                  1 | X01                 | /X01
+ 201 | 101 | Y01  |     1 |               201 |                101 | Y01                 | /Y01
+ 202 | 101 | Y02  |     1 |               202 |                101 | Y02                 | /Y02
+ 301 | 201 | Z01  |     1 |               301 |                201 | Z01                 | /Z01
+ 302 | 201 | Z02  |     1 |               302 |                201 | Z02                 | /Z02
+ 303 | 202 | Z03  |     1 |               303 |                202 | Z03                 | /Z03
+ 304 | 202 | Z04  |     1 |               304 |                202 | Z04                 | /Z04
+(8 rows)
+```
+
+**Add the siblings keyword (to keep the specified order between sub rows of the same line and between the sub rows of each of its sub rows)**
+
+```sql
+select id,pid,note,level,connect_by_root id,connect_by_root pid,connect_by_root note,sys_connect_by_path(note,'/') 
+from mogdb210_connectby_01
+connect by id = pid 
+order siblings by id,pid;
+ id  | pid | note | level | connect_by_rootid | connect_by_rootpid | connect_by_rootnote | sys_connect_by_path 
+-----+-----+------+-------+-------------------+--------------------+---------------------+---------------------
+   1 |     | A01  |     1 |                 1 |                    | A01                 | /A01
+ 101 |   1 | X01  |     1 |               101 |                  1 | X01                 | /X01
+ 201 | 101 | Y01  |     1 |               201 |                101 | Y01                 | /Y01
+ 202 | 101 | Y02  |     1 |               202 |                101 | Y02                 | /Y02
+ 301 | 201 | Z01  |     1 |               301 |                201 | Z01                 | /Z01
+ 302 | 201 | Z02  |     1 |               302 |                201 | Z02                 | /Z02
+ 303 | 202 | Z03  |     1 |               303 |                202 | Z03                 | /Z03
+ 304 | 202 | Z04  |     1 |               304 |                202 | Z04                 | /Z04
+(8 rows)
+```
+
+**Add the prior keyword (this keyword specifies the upper-level column information in the connect by connection condition)**
+
+```sql
+select id,pid,note,level,connect_by_root id,connect_by_root pid,connect_by_root note,sys_connect_by_path(note,'/') 
+from mogdb210_connectby_01
+connect by prior id = pid 
+order by connect_by_root id, level, id;
+ id  | pid | note | level | connect_by_rootid | connect_by_rootpid | connect_by_rootnote | sys_connect_by_path 
+-----+-----+------+-------+-------------------+--------------------+---------------------+---------------------
+   1 |     | A01  |     1 |                 1 |                    | A01                 | /A01
+ 101 |   1 | X01  |     2 |                 1 |                    | A01                 | /A01/X01
+ 201 | 101 | Y01  |     3 |                 1 |                    | A01                 | /A01/X01/Y01
+ 202 | 101 | Y02  |     3 |                 1 |                    | A01                 | /A01/X01/Y02
+ 301 | 201 | Z01  |     4 |                 1 |                    | A01                 | /A01/X01/Y01/Z01
+ 302 | 201 | Z02  |     4 |                 1 |                    | A01                 | /A01/X01/Y01/Z02
+ 303 | 202 | Z03  |     4 |                 1 |                    | A01                 | /A01/X01/Y02/Z03
+ 304 | 202 | Z04  |     4 |                 1 |                    | A01                 | /A01/X01/Y02/Z04
+ 101 |   1 | X01  |     1 |               101 |                  1 | X01                 | /X01
+ 201 | 101 | Y01  |     2 |               101 |                  1 | X01                 | /X01/Y01
+ 202 | 101 | Y02  |     2 |               101 |                  1 | X01                 | /X01/Y02
+ 301 | 201 | Z01  |     3 |               101 |                  1 | X01                 | /X01/Y01/Z01
+ 302 | 201 | Z02  |     3 |               101 |                  1 | X01                 | /X01/Y01/Z02
+ 303 | 202 | Z03  |     3 |               101 |                  1 | X01                 | /X01/Y02/Z03
+ 304 | 202 | Z04  |     3 |               101 |                  1 | X01                 | /X01/Y02/Z04
+ 201 | 101 | Y01  |     1 |               201 |                101 | Y01                 | /Y01
+ 301 | 201 | Z01  |     2 |               201 |                101 | Y01                 | /Y01/Z01
+ 302 | 201 | Z02  |     2 |               201 |                101 | Y01                 | /Y01/Z02
+ 202 | 101 | Y02  |     1 |               202 |                101 | Y02                 | /Y02
+ 303 | 202 | Z03  |     2 |               202 |                101 | Y02                 | /Y02/Z03
+ 304 | 202 | Z04  |     2 |               202 |                101 | Y02                 | /Y02/Z04
+ 301 | 201 | Z01  |     1 |               301 |                201 | Z01                 | /Z01
+ 302 | 201 | Z02  |     1 |               302 |                201 | Z02                 | /Z02
+ 303 | 202 | Z03  |     1 |               303 |                202 | Z03                 | /Z03
+ 304 | 202 | Z04  |     1 |               304 |                202 | Z04                 | /Z04
+(25 rows)
+```
+
+**Add start with keyword (the keyword is used to get the root line, the condition for the base table for filtering, so that the line to meet the conditions as the root line)**
+
+```sql
+select id,pid,note,level,connect_by_root id,connect_by_root pid,connect_by_root note,sys_connect_by_path(note,'/') 
+from mogdb210_connectby_01
+start with id = 101
+connect by id = pid 
+order by id,pid;
+ id  | pid | note | level | connect_by_rootid | connect_by_rootpid | connect_by_rootnote | sys_connect_by_path 
+-----+-----+------+-------+-------------------+--------------------+---------------------+---------------------
+ 101 |   1 | X01  |     1 |               101 |                  1 | X01                 | /X01
+(1 row)
+```
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/14-ALTER-RULE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/14-ALTER-RULE.md
new file mode 100644
index 0000000000000000000000000000000000000000..ed232625a2ee94fb98b123cb76104348ecd48ad7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/14-ALTER-RULE.md
@@ -0,0 +1,45 @@
+---
+title: ALTER RULE
+summary: ALTER RULE
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER RULE
+
+## Function
+
+**ALTER RULE** modifies rule definitions.
+
+## Precautions
+
+- Only the user who has applied a table or view of a specified rule can run the **ALTER RULE** command.
+- Currently, only the rule name can be modified.
+
+## Syntax
+
+```ebnf+diagram
+AlterRule ::= ALTER RULE name ON table_name RENAME TO new_name;
+```
+
+## Parameter Description
+
+- **name**
+
+  Specifies the name of the rule to be modified.
+
+- **table_name**
+
+  Specifies the name of the table for which the rule is to be created.
+
+  Value range: an existing table name in the database.
+
+- **new_name**
+
+  Specifies the new name of the rule.
+
+## Example
+
+```sql
+ALTER RULE notify_all ON emp RENAME TO notify_me;
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/15-ALTER-SCHEMA.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/15-ALTER-SCHEMA.md
new file mode 100644
index 0000000000000000000000000000000000000000..b7bf89e6700daa7a252f0fc8c57866ea419add30
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/15-ALTER-SCHEMA.md
@@ -0,0 +1,90 @@
+---
+title: ALTER SCHEMA
+summary: ALTER SCHEMA
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER SCHEMA
+
+## Function
+
+**ALTER SCHEMA** modifies schema properties.
+
+## Precautions
+
+Only the schema owner or a user granted with the ALTER permission can run the **ALTER SCHEMA** command. The system administrator has this permission by default. To modify a schema owner, you must be the schema owner or system administrator and a member of the new owner role.
+
+## Syntax
+
+- Modify the tamper-proof attribute of a schema.
+
+    ```ebnf+diagram
+    AlterSchema ::= ALTER SCHEMA schema_name { WITH | WITHOUT } BLOCKCHAIN
+    ```
+
+- Rename a schema.
+
+  ```ebnf+diagram
+  AlterSchema ::= ALTER SCHEMA schema_name
+      RENAME TO new_name;
+  ```
+
+- Change the owner of a schema.
+
+  ```ebnf+diagram
+  AlterSchema ::= ALTER SCHEMA schema_name
+      OWNER TO new_owner;
+  ```
+
+## Parameter Description
+
+- **schema_name**
+
+  Specifies the name of an existing schema.
+
+  Value range: an existing schema name
+
+- **RENAME TO new_name**
+
+  Rename a schema. If a non-administrator user wants to change the schema name, the user must have the  **CREATE**  permission on the database.
+
+  **new_name**: new name of the schema.
+
+  Value range: a string. It must comply with the naming convention rule.
+
+- **OWNER TO new_owner**
+
+  Change the owner of a schema. To do this as a non-administrator, you must be a direct or indirect member of the new owning role, and that role must have **CREATE** permission in the database.
+
+  **new_owner**: new owner of the schema.
+
+  Value range: an existing username or role name.
+
+- **{ WITH | WITHOUT } BLOCKCHAIN**
+
+    Modifies the tamper-proof attribute of a schema. Common row-store tables with the tamper-proof attribute are tamper-proof history tables, excluding foreign tables, temporary tables, and system catalogs. The tamper-proof attribute can be modified only when no table is contained in the schema. In addition, the temporary table mode is not supported. Modify the tamper-proof attribute in toast table mode, dbe_perf mode, and blockchain mode.
+
+## Examples
+
+```sql
+-- Create the ds schema.
+mogdb=# CREATE SCHEMA ds;
+
+-- Rename the current schema ds to ds_new.
+mogdb=# ALTER SCHEMA ds RENAME TO ds_new;
+
+-- Create user jack.
+mogdb=# CREATE USER jack PASSWORD 'xxxxxxxxx';
+
+-- Change the owner of ds_new to jack.
+mogdb=# ALTER SCHEMA ds_new OWNER TO jack;
+
+-- Delete user jack and schema ds_new.
+mogdb=# DROP SCHEMA ds_new;
+mogdb=# DROP USER jack;
+```
+
+## Helpful Links
+
+[CREATE SCHEMA](56-CREATE-SCHEMA)，[DROP SCHEMA](91-DROP-SCHEMA)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/16-ALTER-SEQUENCE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/16-ALTER-SEQUENCE.md
new file mode 100644
index 0000000000000000000000000000000000000000..08b29805dd490b0de09c517df57772914c253b7b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/16-ALTER-SEQUENCE.md
@@ -0,0 +1,94 @@
+---
+title: ALTER SEQUENCE
+summary: ALTER SEQUENCE
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER SEQUENCE
+
+## Function
+
+**ALTER SEQUENCE** modifies the parameters of an existing sequence.
+
+## Precautions
+
+- Only the sequence owner or a user granted with the ALTER permission can run the **ALTER SEQUENCE** command. The system administrator has this permission by default. To modify a sequence owner, you must be the sequence owner or system administrator and a member of the new owner role.
+- In the current version, you can modify only the owner, owning column, maximum value and increment. To modify other parameters, delete the sequence and create it again. Then, use the **Setval** function to restore parameter values.
+- **ALTER SEQUENCE MAXVALUE** cannot be used in transactions, functions, and stored procedures.
+- After the maximum value of a sequence is changed, the cache of the sequence in all sessions is cleared.
+- The  **ALTER SEQUENCE**  statement blocks the invocation of  **nextval**,  **setval**,  **currval**, and  **lastval**.
+
+## Syntax
+
+- Change the owning column of a sequence.
+
+  ```ebnf+diagram
+  AlterSequence ::= ALTER SEQUENCE [ IF EXISTS ] name
+      [MAXVALUE maxvalue | NO MAXVALUE | NOMAXVALUE | CACHE cache]
+      [ OWNED BY { table_name'.'column_name | NONE } ]
+  ```
+
+- Change the owner of a sequence.
+
+  ```ebnf+diagram
+  AlterSequence ::= ALTER SEQUENCE [ IF EXISTS ] name OWNER TO new_owner;
+  ```
+
+- Change the increment of sequence. <a id = 'increment'> </a>
+
+  ```ebnf+diagram
+  AlterSequence ::= ALTER SEQUENCE [ IF EXISTS ] name [ INCREMENT [ BY ] increment ];
+  ```
+
+## Parameter Description
+
+- name
+
+  Specifies the name of the sequence to be modified.
+
+- IF EXISTS
+
+  Sends a notice instead of an error when you are modifying a nonexistent sequence.
+
+- CACHE
+
+    For quick access, the number of serial numbers is pre-stored in the memory. If not specified, the old buffer value will be kept.
+
+- OWNED BY
+
+  Associates a sequence with a specified column included in a table. In this way, the sequence will be deleted when you delete its associated column or the table where the column belongs to.
+
+  If the sequence has been associated with another table before you use this option, the new association will overwrite the old one.
+
+  The associated table and sequence must be owned by the same user and in the same schema.
+
+  If **OWNED BY NONE** is used, all existing associations will be deleted.
+
+- new_owner
+
+  Specifies the username of the new owner of the sequence. To change the owner, you must also be a direct or indirect member of the new role, and this role must have **CREATE** permission on the sequence's schema.
+
+## Examples
+
+```sql
+-- Create an ascending sequence named serial, which starts from 101.
+mogdb=# CREATE SEQUENCE serial START 101;
+
+-- Create a table and specify default values for the sequence.
+mogdb=# CREATE TABLE T1(C1 bigint default nextval('serial'));
+
+-- Change the owning column of serial to T1.C1.
+mogdb=# ALTER SEQUENCE serial OWNED BY T1.C1;
+
+-- Change the increment of sequence.
+mogdb=# ALTER SEQUENCE serial increment by 5;
+
+-- Delete a sequence and a table.
+mogdb=# DROP SEQUENCE serial cascade;
+mogdb=# DROP TABLE T1;
+```
+
+## Helpful Links
+
+[CREATE SEQUENCE](57-CREATE-SEQUENCE)，[DROP SEQUENCE](92-DROP-SEQUENCE)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/17-ALTER-SERVER.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/17-ALTER-SERVER.md
new file mode 100644
index 0000000000000000000000000000000000000000..9270433965a3739530ccc70368aa20b6d8eefc90
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/17-ALTER-SERVER.md
@@ -0,0 +1,106 @@
+---
+title: ALTER SERVER
+summary: ALTER SERVER
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER SERVER
+
+## Function
+
+**ALTER SERVER** adds, modifies, or deletes the parameters of an existing server. You can query existing servers from the **pg_foreign_server** system catalog.
+
+## Precautions
+
+Only the server owner or a user granted with the ALTER permission can run the **ALTER SERVER** command. The system administrator has this permission by default. To modify a server owner, you must be the server owner or system administrator and a member of the new owner role.
+
+## Syntax
+
+- Change the parameters for a foreign server.
+
+  ```ebnf+diagram
+  AlterServer ::= ALTER SERVER server_name [ VERSION 'new_version' ]
+    [ OPTIONS ( {[ ADD | SET | DROP ] option ['value']} [, ... ] ) ];
+  ```
+
+  In **OPTIONS**, **ADD**, **SET**, and **DROP** are operations to be performed. If these operations are not specified, **ADD** operations will be performed by default. **option** and **value** are the parameters of the corresponding operation.
+
+- Change the name of a foreign server.
+
+  ```ebnf+diagram
+  AlterServer ::= ALTER SERVER server_name
+     RENAME TO new_name;
+  ```
+
+## Parameter Description
+
+- **server_name**
+
+  Specifies the name of the server to be modified.
+
+- **new_version**
+
+  Specifies the new version of the server.
+
+- **OPTIONS**
+
+  Change options of the server. **ADD**, **SET**, and **DROP** are operations to be performed. If the operation is not set explicitly, **ADD** is used. The option name must be unique, and the name and value are also validated with the foreign data wrapper library of the server.
+
+  - Options supported by oracle_fdw are as follows:
+
+    - **dbserver**
+
+        Connection string of the remote Oracle database.
+
+    - **isolation_level** (default value: **serializable**)
+
+        Oracle database transaction isolation level.
+
+        Value range: serializable, read_committed, read_only
+
+  - Options supported by mysql_fdw are as follows:
+
+    - **host** (default value: **127.0.0.1**)
+
+        IP address of the MySQL server or MariaDB.
+
+    - **port** (default value: **3306**)
+
+        Listening port number of the MySQL server or MariaDB.
+
+  - The options supported by postgres_fdw are the same as those supported by libpq. For details, see [Connection Characters](6-connection-characters). Note that the following options cannot be modified:
+
+    - **user** and **password**
+
+        The user name and password are specified when the user mapping is created.
+
+    - **client_encoding**
+
+        The encoding mode of the local server is automatically obtained and set.
+
+    - **application_name**
+
+        This option is always set to **postgres_fdw**.
+
+    In addition to the connection parameters supported by libpq, the following options are provided:
+
+  - **use_remote_estimate**
+
+    Controls whether postgres_fdw issues the EXPLAIN command to obtain the estimated run time. The default value is **false**.
+
+  - **fdw_startup_cost**
+
+    Estimates the startup time required for a foreign table scan, including the time to establish a connection, analyze the request at the remote server, and generate a plan. The default value is **100**.
+
+  - **fdw_typle_cost**
+
+    Specifies the additional consumption when each tuple is scanned on a remote server. The value specifies the extra consumption of data transmission between servers. The default value is **0.01**.
+
+- **new_name**
+
+  Specifies the new name of the server.
+
+## Helpful Links
+
+[CREATE SERVER](58-CREATE-SERVER)，[DROP SERVER](93-DROP-SERVER)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/18-ALTER-SESSION.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/18-ALTER-SESSION.md
new file mode 100644
index 0000000000000000000000000000000000000000..72bdf3f567d7f7f612e672258ccd05b5eb76fa0e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/18-ALTER-SESSION.md
@@ -0,0 +1,90 @@
+---
+title: ALTER SESSION
+summary: ALTER SESSION
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER SESSION
+
+## Function
+
+**ALTER SESSION** defines or modifies the conditions or parameters that affect the current session. Modified session parameters are kept until the current session is disconnected.
+
+## Precautions
+
+- If the **START TRANSACTION** statement is not executed before the **SET TRANSACTION** statement, the transaction is ended instantly and the statement does not take effect.
+- You can use the **transaction_mode(s)** method declared in the **START TRANSACTION** statement to avoid using the **SET TRANSACTION** statement.
+
+## Syntax
+
+- Set transaction parameters of a session.
+
+  ```ebnf+diagram
+  AlterSession ::= ALTER SESSION SET [ SESSION CHARACTERISTICS AS ] TRANSACTION
+      { ISOLATION LEVEL { READ COMMITTED } | { READ ONLY  | READ WRITE } } [, ...] ;
+  ```
+
+- Set other running parameters of a session.
+
+  ```ebnf+diagram
+  AlterSession ::= ALTER SESSION SET
+      {{config_parameter { { TO  | =  }  { value | DEFAULT }
+        | FROM CURRENT }}
+        | TIME ZONE time_zone
+        | CURRENT_SCHEMA schema
+        | NAMES encoding_name
+        | ROLE role_name PASSWORD 'password'
+        | SESSION AUTHORIZATION { role_name PASSWORD 'password' | DEFAULT }
+        | XML OPTION { DOCUMENT | CONTENT }
+      } ;
+  ```
+
+## Parameter Description
+
+For details about the descriptions of parameters related to **ALTER SESSION**, see **Parameter Description** of the SET syntax.
+
+## Examples
+
+```sql
+-- Create the ds schema.
+mogdb=# CREATE SCHEMA ds;
+
+-- Set the search path of the schema.
+mogdb=# SET SEARCH_PATH TO ds, public;
+
+-- Set the time/date type to the traditional postgres format (date before month).
+mogdb=# SET DATESTYLE TO mogdb, dmy;
+
+-- Set the character code of the current session to UTF8.
+mogdb=# ALTER SESSION SET NAMES 'UTF8';
+
+-- Set the time zone to Berkeley of California.
+mogdb=# SET TIME ZONE 'PST8PDT';
+
+-- Set the time zone to Italy.
+mogdb=# SET TIME ZONE 'Europe/Rome';
+
+-- Set the current schema.
+mogdb=# ALTER SESSION SET CURRENT_SCHEMA TO tpcds;
+
+-- Set XML OPTION to DOCUMENT.
+mogdb=# ALTER SESSION SET XML OPTION DOCUMENT;
+
+-- Create the role joe, and set the session role to joe.
+mogdb=# CREATE ROLE joe WITH PASSWORD 'xxxxxxxxx';
+mogdb=# ALTER SESSION SET SESSION AUTHORIZATION joe PASSWORD 'xxxxxxxxx';
+
+-- Switch to the default user.
+mogdb=> ALTER SESSION SET SESSION AUTHORIZATION default;
+
+-- Delete the ds schema.
+mogdb=# DROP SCHEMA ds;
+
+-- Delete the role joe.
+mogdb=# DROP ROLE joe;
+```
+
+## Helpful Links
+
+[SET](127-SET)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/19-ALTER-SYNONYM.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/19-ALTER-SYNONYM.md
new file mode 100644
index 0000000000000000000000000000000000000000..16e61dd7c4972e3f7bc402aa5259b5bc7c950531
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/19-ALTER-SYNONYM.md
@@ -0,0 +1,62 @@
+---
+title: ALTER SYNONYM
+summary: ALTER SYNONYM
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER SYNONYM
+
+## Function
+
+**ALTER SYNONYM** modifies the attributes of the **SYNONYM** object.
+
+## Precautions
+
+- Currently, only the owner of the **SYNONYM** object can be changed.
+- Only the system administrator has the permission to modify the owner of the **SYNONYM** object.
+- The new owner must have the **CREATE** permission on the schema where the **SYNONYM** object resides.
+
+## Syntax
+
+```ebnf+diagram
+AlterSynonym ::= ALTER SYNONYM synonym_name
+    OWNER TO new_owner;
+```
+
+## Parameter Description
+
+- **synonym**
+
+  Specifies the name of the synonym to be modified, which can contain the schema name.
+
+  Value range: a string. It must comply with the naming convention rule.
+
+- **new_owner**
+
+  Specifies the new owner of the **SYNONYM** object.
+
+  Value range: a string. It must be a valid username.
+
+## Examples
+
+```sql
+-- Create synonym t1.
+mogdb=#  CREATE OR REPLACE SYNONYM t1 FOR ot.t1;
+
+-- Create a user u1.
+mogdb=# CREATE USER u1 PASSWORD 'user@111';
+
+-- Change the owner of synonym t1 to u1.
+mogdb=# ALTER SYNONYM t1 OWNER TO u1;
+
+-- Delete synonym t1.
+mogdb=# DROP SYNONYM t1;
+
+-- Delete user u1.
+mogdb=# DROP USER u1;
+```
+
+## Helpful Links
+
+[CREATE SYNONYM](59-CREATE-SYNONYM)，[DROP SYNONYM](94-DROP-SYNONYM)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/2-ALTER-DATABASE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/2-ALTER-DATABASE.md
new file mode 100644
index 0000000000000000000000000000000000000000..0151d0931ba10aed4b427e1e59aaad3d279f9de8
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/2-ALTER-DATABASE.md
@@ -0,0 +1,144 @@
+---
+title: ALTER DATABASE
+summary: ALTER DATABASE
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER DATABASE
+
+## Function
+
+**ALTER DATABASE** modifies a database, including its name, owner, connection limitation, and object isolation.
+
+## Precautions
+
+- Only the database owner or a user granted with the ALTER permission can run the **ALTER DATABASE** command. The system administrator has this permission by default. The following is permission constraints depending on attributes to be modified:
+  - To modify the database name, you must have the **CREATEDB** permission.
+  - To modify a database owner, you must be a database owner or system administrator and a member of the new owner role, with the **CREATEDB** permission.
+  - To modify the default tablespace of a database, a user must have the permission to create a tablespace. This statement physically migrates tables and indexes in a default tablespace to a new tablespace. Note that tables and indexes outside the default tablespace are not affected.
+- You are not allowed to rename a database in use. To rename it, connect to another database.
+
+## Syntax
+
+- Modify the maximum number of connections to the database.
+
+  ```ebnf+diagram
+  AlterDatabase ::= ALTER DATABASE database_name
+      [ [ WITH ] CONNECTION LIMIT connlimit ];
+  ```
+
+- Rename the database.
+
+  ```ebnf+diagram
+  AlterDatabase ::= ALTER DATABASE database_name
+      RENAME TO new_name;
+  ```
+
+- Change the database owner.
+
+  ```ebnf+diagram
+  AlterDatabase ::= ALTER DATABASE database_name
+      OWNER TO new_owner;
+  ```
+
+- Change the default tablespace of the database.
+
+  ```ebnf+diagram
+  AlterDatabase ::= ALTER DATABASE database_name
+      SET TABLESPACE new_tablespace;
+  ```
+
+- Modify the session parameter value of the database.
+
+  ```ebnf+diagram
+  AlterDatabase ::= ALTER DATABASE database_name
+      SET configuration_parameter { { TO | = } { value | DEFAULT } | FROM CURRENT };
+  ```
+
+- Reset the database configuration parameter.
+
+  ```ebnf+diagram
+  AlterDatabase ::= ALTER DATABASE database_name RESET
+      { configuration_parameter | ALL };
+  ```
+
+- Modify the object isolation attribute of the database.
+
+  ```ebnf+diagram
+  AlterDatabase ::= ALTER DATABASE database_name [ WITH ] { ENABLE | DISABLE } PRIVATE OBJECT;
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > - To modify the object isolation attribute of a database, the database must be connected. Otherwise, the modification will fail.
+  > - For a new database, the object isolation attribute is disabled by default. After this attribute is enabled, common users can view only the objects (such as tables, functions, views, and columns) that they have the permission to access. This attribute does not take effect for administrators. After this attribute is enabled, administrators can still view all database objects.
+
+## Parameter Description
+
+- **database_name**
+
+  Specifies the name of the database whose attributes are to be modified.
+
+  Value range: a string. It must comply with the naming convention rule.
+
+- **connlimit**
+
+  Specifies the maximum number of concurrent connections that can be made to this database (excluding administrators' connections).
+
+  Value range: The value must be an integer, preferably from 1 to 50. The default value **-1** indicates that there is no restriction on the number of concurrent connections.
+
+- **new_name**
+
+  Specifies the new name of a database.
+
+  Value range: a string. It must comply with the naming convention rule.
+
+- **new_owner**
+
+  Specifies the new owner of a database.
+
+  Value range: a string. It must be a valid username.
+
+- **new_tablespace**
+
+  Specifies the new default tablespace of a database. The tablespace exists in the database. The default tablespace is **pg_default**.
+
+  Value range: a string. It must be a valid tablespace name.
+
+- **configuration_parameter**
+
+  **value**
+
+  Sets a specified database session parameter to a specified value. If the value is **DEFAULT** or **RESET**, the default setting is used in the new session. **OFF** closes the setting.
+
+  Value range: a string
+
+  - DEFAULT
+  - OFF
+  - RESET
+
+- **FROM CURRENT**
+
+  Sets the value of the database based on the current connected session.
+
+- **RESET configuration_parameter**
+
+  Resets the specified database session parameter.
+
+- **RESET ALL**
+
+  Resets all database session parameters.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - Modify the default tablespace of a database by moving the table or index in the old tablespace into the new tablespace. This operation does not affect the tables or indexes in other non-default tablespaces.
+> - The modified database session parameter values will take effect in the next session.
+
+## Examples
+
+See **Examples** in [CREATE DATABASE](44-CREATE-DATABASE).
+
+## Helpful Links
+
+[CREATE DATABASE](44-CREATE-DATABASE)，[DROP DATABASE](78-DROP-DATABASE)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/20-ALTER-SYSTEM-KILL-SESSION.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/20-ALTER-SYSTEM-KILL-SESSION.md
new file mode 100644
index 0000000000000000000000000000000000000000..45dc011094bc72fb943406f8b93ff788bfcf25a5
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/20-ALTER-SYSTEM-KILL-SESSION.md
@@ -0,0 +1,55 @@
+---
+title: ALTER SYSTEM KILL SESSION
+summary: ALTER SYSTEM KILL SESSION
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER SYSTEM KILL SESSION
+
+## Function
+
+**ALTER SYSTEM KILL SESSION** ends a session.
+
+## Precautions
+
+None
+
+## Syntax
+
+```ebnf+diagram
+AlterSystemKillSession ::= ALTER SYSTEM KILL SESSION 'session_sid, serial' [ IMMEDIATE ];
+```
+
+## Parameter Description
+
+- **session_sid, serial**
+
+  Specifies the SID and SERIAL of a session (To obtain the values, see the example.)
+
+- **IMMEDIATE**
+
+  Specifies that a session will be ended instantly after the statement is executed.
+
+## Example
+
+```sql
+-- Query session information.
+mogdb=#
+SELECT sa.sessionid AS sid,0::integer AS serial#,ad.rolname AS username FROM pg_stat_get_activity(NULL) AS sa
+LEFT JOIN pg_authid ad ON(sa.usesysid = ad.oid)WHERE sa.application_name <> 'JobScheduler';
+       sid       | serial# | username
+-----------------+---------+----------
+ 140131075880720 |       0 | omm
+ 140131025549072 |       0 | omm
+ 140131073779472 |       0 | omm
+ 140131071678224 |       0 | omm
+ 140131125774096 |       0 |
+ 140131127875344 |       0 |
+ 140131113629456 |       0 |
+ 140131094742800 |       0 |
+(8 rows)
+
+-- End the session whose SID is 140131075880720.
+mogdb=#  ALTER SYSTEM KILL SESSION '140131075880720,0' IMMEDIATE;
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/21-ALTER-SYSTEM-SET.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/21-ALTER-SYSTEM-SET.md
new file mode 100644
index 0000000000000000000000000000000000000000..425cd0bef6702f3c8b46cbaa327f823fa002b2d4
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/21-ALTER-SYSTEM-SET.md
@@ -0,0 +1,79 @@
+---
+title: ALTER SYSTEM SET
+summary: ALTER SYSTEM SET
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER SYSTEM SET
+
+## Function
+
+**ALTER SYSTEM SET** sets GUC parameters of the POSTMASTER, SIGHUP, and BACKEND levels. This command writes parameters into the configuration file. The time to take effect varies according to the level.
+
+## Precautions
+
+- This command can be used only by initial users and users with the  **sysadmin**  permission.
+
+- The effective time of GUC parameters at different levels is as follows:
+  - The GUC parameters at the POSTMASTER level take effect only after the system is restarted.
+  - The GUC parameters at the BACKEND level take effect only after the session is reconnected.
+  - The GUC parameters at the SIGHUP level take effect immediately. (Actually, there is a slight delay to wait for the thread reloading the parameter.)
+
+- You can set the [audit_set_parameter](3-operation-audit) parameter to specify whether the operation is audited.
+
+- The operation can be synchronized to the standby server.
+
+- The operation is the same as **gs_guc**, which does not pay attention to whether the database is a primary or standby node or whether the database is read-only.
+
+- The operation cannot be executed in a transaction because it cannot be rolled back.
+
+- The following parameters can be modified only by the initial user:
+
+    ```
+    audit_copy_exec, audit_data_format, audit_database_process, audit_directory, audit_dml_state,
+    audit_dml_state_select, audit_enabled, audit_file_remain_threshold, audit_file_remain_time,
+    audit_function_exec, audit_grant_revoke, audit_login_logout, audit_resource_policy,
+    audit_rotation_interval, audit_rotation_size, audit_set_parameter, audit_space_limit,
+    audit_system_object, audit_user_locked, audit_user_violation,
+    asp_log_directory, config_file, data_directory, enable_access_server_directory,
+    enable_copy_server_files, external_pid_file, hba_file, ident_file, log_directory, perf_directory,
+    query_log_directory, ssl_ca_file, ssl_cert_file, ssl_crl_file, ssl_key_file, stats_temp_directory,
+    unix_socket_directory, unix_socket_group, unix_socket_permissions,
+    krb_caseins_users, krb_server_keyfile, krb_srvname, allow_system_table_mods, enableSeparationOfDuty,
+    modify_initial_password, password_encryption_type, password_policy
+    ```
+
+## Syntax
+
+```ebnf+diagram
+AlterSystemSet ::= ALTER SYSTEM SET parameter TO value;
+```
+
+## Parameter Description
+
+- **parameter**
+
+  GUC parameter
+
+- **value**
+
+  GUC parameter value
+
+## Examples
+
+```sql
+-- Set the SIGHUP-level parameter audit_enabled.
+mogdb=#  alter system set audit_enabled to off;
+ALTER SYSTEM SET
+mogdb=#  show audit_enabled;
+ audit_enabled
+---------------
+ off
+(1 row)
+
+-- The setting of the POSTMASTER-level parameter enable_thread_pool takes effect after the system is restarted.
+mogdb=# alter system set enable_thread_pool to on;
+NOTICE:  please restart the database for the POSTMASTER level parameter to take effect.
+ALTER SYSTEM SET
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/22-ALTER-TABLE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/22-ALTER-TABLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..40d5dcfd6ee257f2b1830f438bc00b7f9e4af17a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/22-ALTER-TABLE.md
@@ -0,0 +1,449 @@
+---
+title: ALTER TABLE
+summary: ALTER TABLE
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER TABLE
+
+## Function
+
+**ALTER TABLE** modifies tables, including modifying table definitions, renaming tables, renaming specified columns in tables, renaming table constraints, setting table schemas, enabling or disabling row-level security policies, and adding or updating multiple columns.
+
+## Precautions
+
+- Only the table owner or a user granted with the ALTER permission can run the **ALTER TABLE** command. The system administrator has this permission by default. To modify the owner or schema of a table, you must be a table owner or system administrator and a member of the new owner role.
+- The tablespace of a partitioned table cannot be modified, but the tablespace of the partition can be modified.
+- The storage parameter **ORIENTATION** cannot be modified.
+- Currently, **SET SCHEMA** can only set schemas to user schemas. It cannot set a schema to a system internal schema.
+
+- Column-store tables support only the  **PARTIAL CLUSTER KEY**,  **UNIQUE**, and  **PRIMARY KEY**  table-level constraints, but do not support primary and foreign key table-level constraints.
+- In a column-store table, you can perform  **ADD COLUMN**,  **ALTER TYPE**,  **SET STATISTICS**,  **DROP COLUMN**  operations, and change table name and space. The types of new and modified columns should be the [Data Types](1-numeric-data-types) supported by column-store. The  **USING**  option of  **ALTER TYPE**  only supports constant expression and expression involved in the column.
+- The column constraints supported by column-store tables include  **NULL**,  **NOT NULL**, **DEFAULT**  constant values, **UNIQUE** and **PRIMARY KEY**. Only the  **DEFAULT**  value can be modified (by using  **SET DEFAULT**  and  **DROP DEFAULT**). Currently,  **NULL**  and  **NOT NULL**  constraints cannot be modified.
+
+- Auto-increment columns cannot be added, or a column whose **DEFAULT** value contains the **nextval()** expression cannot be added.
+- Row-access control cannot be enabled for foreign tables and temporary tables.
+- When you delete a **PRIMARY KEY** constraint by constraint name, the **NOT NULL** constraint is not deleted. If necessary, manually delete the **NOT NULL** constraint.
+- When JDBC is used, the **DEFAULT** value can be set through **PrepareStatement**.
+
+## Syntax
+
+- Modify the definition of a table.
+
+  ```ebnf+diagram
+  AlterTable ::= ALTER TABLE [ IF EXISTS ] { table_name [*] | ONLY table_name | ONLY ( table_name ) }
+      action [, ... ];
+  ```
+
+  There are several clauses of **action**:
+
+  ```ebnf+diagram
+  action ::= column_clause
+        | ADD table_constraint [ NOT VALID ]
+        | ADD table_constraint_using_index
+        | VALIDATE CONSTRAINT constraint_name
+        | DROP CONSTRAINT [ IF EXISTS ]  constraint_name [ RESTRICT | CASCADE ]
+        | ADD INDEX index_name (column_name)
+        | CLUSTER ON index_name
+        | SET WITHOUT CLUSTER
+        | SET ( {storage_parameter = value} [, ... ] )
+        | RESET ( storage_parameter [, ... ] )
+        | OWNER TO new_owner
+        | SET TABLESPACE new_tablespace
+        | SET {COMPRESS|NOCOMPRESS}
+        | TO { GROUP groupname | NODE ( nodename [, ... ] ) }
+        | ADD NODE ( nodename [, ... ] )
+        | DELETE NODE ( nodename [, ... ] )
+        | DISABLE TRIGGER [ trigger_name | ALL | USER ]
+        | ENABLE TRIGGER [ trigger_name | ALL | USER ]
+        | ENABLE REPLICA TRIGGER trigger_name
+        | ENABLE ALWAYS TRIGGER trigger_name
+        | DISABLE '/' ENABLE [ REPLICA | ALWAYS ] RULE
+        | DISABLE ROW LEVEL SECURITY
+        | ENABLE ROW LEVEL SECURITY
+        | FORCE ROW LEVEL SECURITY
+        | NO FORCE ROW LEVEL SECURITY
+        | ENCRYPTION KEY ROTATION
+        | SET WITH OIDS
+        | SET WITHOUT OIDS
+        | INHERIT parents
+        | NO INHERIT parents
+        | OF type_name
+        | NOT OF
+        | REPLICA IDENTITY { DEFAULT | USING INDEX index_name | FULL | NOTHING }
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > - **ADD table_constraint [ NOT VALID ]** Adds a table constraint.
+  > - **ADD table_constraint_using_index** Adds a primary key constraint or unique constraint to a table based on the existing unique index.
+  > - **VALIDATE CONSTRAINT constraint_name** Validates a check-class constraint created with the **NOT VALID** option, and scans the entire table to ensure that all rows meet the constraint. Nothing happens if the constraint is already marked valid.
+  > - **DROP CONSTRAINT [ IF EXISTS ] constraint_name [ RESTRICT | CASCADE ]** Deletes a table constraint.
+  > - **ADD INDEX index_name (column_name)** Creates an index named **index_name** in the **column_name** column of a table.
+  > - **CLUSTER ON index_name** Selects the default index for future CLUSTER operations. Actually, the table is not re-clustered.
+  > - **SET WITHOUT CLUSTER** Deletes the most recently used **CLUSTER** index from the table. This affects future **CLUSTER** operations that do not specify an index.
+  > - **SET ( {storage_parameter = value} [, … ] )** Changes one or more storage parameters for the table.
+  > - **RESET ( storage_parameter [, … ] )** Resets one or more storage parameters to their defaults. As with **SET**, a table rewrite might be needed to update the table entirely.
+  > - **OWNER TO new_owner** Changes the owner of a table, sequence, or view to the specified user.
+  > - **SET TABLESPACE new_tablespace** Changes the table's tablespace to the specified tablespace and moves the data files associated with the table to the new tablespace. Indexes on the table, if any, are not moved; but they can be moved separately with additional **SET TABLESPACE** option in **ALTER INDEX**.
+  > - **SET {COMPRESS|NOCOMPRESS}** Sets the compression feature of a table. The table compression feature affects only the storage mode of data inserted in a batch subsequently and does not affect storage of existing data. Setting the table compression feature will result in the fact that there are both compressed and uncompressed data in the table. <a id = 'COMPRESS'> </a>
+  > - **TO { GROUP groupname | NODE ( nodename [, … ] ) }** The syntax is only available in extended mode (when GUC parameter **support_extended_features** is **on**). Exercise caution when enabling the mode. It is mainly used for tools like internal dilatation tools. Common users should not use the mode.
+  > - **ADD NODE ( nodename [, … ] )** It is only available for internal scale-out tools. Common users should not use the syntax. - **DELETE NODE ( nodename [, … ] )** It is only available for internal scale-in tools. Common users should not use the syntax.
+  > - **DISABLE TRIGGER [ trigger_name | ALL | USER ]** Disables a single trigger specified by **trigger_name**, disables all triggers, or disables only user triggers (excluding internally generated constraint triggers, for example, deferrable unique constraint triggers and exclusion constraints triggers). Exercise caution when using this function because data integrity cannot be ensured as expected if the triggers are not executed.
+  > - **| ENABLE TRIGGER [ trigger_name | ALL | USER ]** Enables a single trigger specified by **trigger_name**, enables all triggers, or enables only user triggers.
+  > - **| ENABLE REPLICA TRIGGER trigger_name** Determines that the trigger firing mechanism is affected by the configuration variable [session_replication_role](1-statement-behavior). When the replication role is **origin** (default value) or **local**, a simple trigger is fired. When **ENABLE REPLICA** is configured for a trigger, it is fired only when the session is in replica mode.
+  > - **| ENABLE ALWAYS TRIGGER trigger_name** Determines that all triggers are fired regardless of the current replication mode.
+  > - **| DISABLE/ENABLE [ REPLICA | ALWAYS ] RULE** Enables or disables a rule for tables. Disabled rules are still visible in the system, but are not applied during query rewriting. The **ON SELECT** rule cannot be disabled because it is related to the view implementation. Rules configured as **ENABLE REPLICA** are enabled only when the session is in replica mode, while those configured as **ENABLE ALWAYS** can be enabled regardless of the replica mode. Rule triggering is also affected by configuration variables in [session_replication_role](1-statement-behavior), which is similar to the preceding trigger setting.
+  > - **| DISABLE/ENABLE ROW LEVEL SECURITY** Enables or disables row-level access control for a table. If row-level access control is enabled for a data table but no row-level access control policy is defined, the row-level access to the data table is not affected. If row-level access control for a table is disabled, the row-level access to the table is not affected even if a row-level access control policy has been defined. For details, see [CREATE ROW LEVEL SECURITY POLICY](52-CREATE-ROW-LEVEL-SECURITY-POLICY).
+  > - **| NO FORCE/FORCE ROW LEVEL SECURITY** Forcibly enables or disables row-level access control for a table. By default, the table owner is not affected by the row-level access control feature. However, if row-level access control is forcibly enabled, the table owner (excluding system administrators) will be affected. System administrators are not affected by any row-level access control policies.
+  > - **| REPLICA IDENTITY {DEFAULT | USING INDEX index_name | FULL | NOTHING}** Adjusts the amount of information written to WALs during logical replication. This option is valid only when **wal_level** is set to **logical**. When the original data table is updated, the default logical replication flow contains only the historical records of the primary key. If you need to output the historical records of column update or delete operations, you can modify this parameter. **DEFAULT** (not the default value in the system catalog) records the old value of the primary key column. **USING INDEX** records the old values of the columns contained in the **index_name** index. All columns of the index must be **NOT NULL**. **FULL** records the old values of all columns. **NOTHING** (default value in the system catalog) does not record information about old values.
+  > - **SET WITH OIDS** Adds an OID system column to a data table. If the OID already exists in the table, the syntax does not change anything.
+  > - **SET WITHOUT OIDS** Deletes an OID system column from a data table. If there is no OID in the table, the syntax does not change anything.
+  > - **INHERIT parent_table** Adds the target data table to a specified parent data table as a new child data table. After that, the query for the parent data table will contain the data in the target data table. Before being added as a child data table, the target data table must contain all the columns in the parent data table. These columns must have matching data categories, and if they have NOT NULL constraints in the parent data table, they must also have NOT NULL constraints in the child data table. For all CHECK constraints in the parent data table, there must be corresponding constraints in the child data table, unless the parent data table is marked as non-inheritable.
+  > - **NO INHERIT parent_table** Generates the target data table from the child data table of a specified parent data table. Queries for the parent data table will no longer contain records generated from the target data table.
+  > - **OF type_name** Joins a table to a composite type, which is similar to table creation by using the **CREATE TABLE OF** option. The name and type of a table column must exactly match those defined in the composite type, but the OID system column can be different. The table cannot be inherited from any other table. These restrictions ensure that the **CREATE TABLE OF** option allows the same table definition.
+  > - **NOT OF** Removes the association between a table and a type.
+  > - **REPLICA IDENTITY { DEFAULT | USING INDEX index_name | FULL | NOTHING }** **DEFAULT** records the old value of the primary key column. **USING INDEX** records the old values of columns covered by the named indexes. These values must be unique, non-local, and non-deferrable, and contain the values of columns marked **NOT NULL**. **FULL** records the old values of all columns in the row. **NOTHING** does not record information in old rows. In all cases, no old values are recorded unless at least one of the columns to be recorded in the new and old rows is different.
+
+  - There are several clauses of **column_clause**:
+
+    ```ebnf+diagram
+    column_clause ::= ADD [ COLUMN ] column_name data_type [ compress_mode ] [ COLLATE collation ] [ column_constraint [ ... ] ]
+    | MODIFY column_name data_type
+    | MODIFY column_name [ CONSTRAINT constraint_name ] NOT NULL [ ENABLE ]
+    | MODIFY column_name [ CONSTRAINT constraint_name ] NULL
+    | DROP [ COLUMN ] [ IF EXISTS ] column_name [ RESTRICT | CASCADE ]
+    | ALTER [ COLUMN ] column_name [ SET DATA ] TYPE data_type [ COLLATE collation ] [ USING expression ]
+    | ALTER [ COLUMN ] column_name { SET DEFAULT expression | DROP DEFAULT }
+    | ALTER [ COLUMN ] column_name { SET | DROP } NOT NULL
+    | ALTER [ COLUMN ] column_name SET STATISTICS [PERCENT] integer
+    | ADD STATISTICS (( column_1_name, column_2_name [, ...] ))
+    | DELETE STATISTICS (( column_1_name, column_2_name [, ...] ))
+    | ALTER [ COLUMN ] column_name SET ( {attribute_option = value} [, ... ] )
+    | ALTER [ COLUMN ] column_name RESET ( attribute_option [, ... ] )
+    | ALTER [ COLUMN ] column_name SET STORAGE { PLAIN | EXTERNAL | EXTENDED | MAIN }
+    ```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - **ADD [ COLUMN ] column_name data_type [ compress_mode ] [ COLLATE collation ] [ column_constraint [ … ] ]** Adds a column to a table. If a column is added with **ADD COLUMN**, all existing rows in the table are initialized with the column's default value (**NULL** if no **DEFAULT** clause is specified).
+>
+> - **ADD ( { column_name data_type [ compress_mode ] } [, …] )** Adds columns in the table. - **MODIFY ( { column_name data_type | column_name [ CONSTRAINT constraint_name ] NOT NULL [ ENABLE ] | column_name [ CONSTRAINT constraint_name ] NULL } [, …] )** Modifies the data type of an existing column in the table.
+>
+> - **DROP [ COLUMN ] [ IF EXISTS ] column_name [ RESTRICT | CASCADE ]** Drops a column from a table. Indexes and constraints related to the column are automatically dropped. If an object not belonging to the table depends on the column, **CASCADE** must be specified, such as a view. The **DROP COLUMN** statement does not physically remove the column, but simply makes it invisible to SQL operations. Subsequent **INSERT** and **UPDATE** operations in the table will store a **NULL** value for the column. Therefore, column deletion takes a short period of time but does not immediately release the tablespace on the disks, because the space occupied by the deleted column is not recycled. The space will be recycled when **VACUUM** is executed.
+>
+> - **ALTER [ COLUMN ] column_name [ SET DATA ] TYPE data_type [ COLLATE collation ] [ USING expression ]** Modifies the type of a column in a table. Indexes and simple table constraints on the column will automatically use the new data type by reparsing the originally supplied expression. **ALTER TYPE** requires an entire table be rewritten. This is an advantage sometimes, because it frees up unnecessary space from a table. For example, to recycle the space occupied by a deleted column, the fastest method is to use the following statement.
+>
+>    ```sql
+>    ALTER TABLE table ALTER COLUMN anycol TYPE anytype;
+>    ```
+>
+>    In this statement, **anycol** indicates any column existing in the table and **anytype** indicates the type of the prototype of the column. **ALTER TYPE** does not change the table except that the table is forcibly rewritten. In this way, the data that is no longer used is deleted.
+>
+> - **ALTER [ COLUMN ] column_name { SET DEFAULT expression | DROP DEFAULT }** Sets or removes the default value for a column. The default values only apply to subsequent **INSERT** operations; they do not cause rows already in the table to change. Defaults can also be created for views, in which case they are inserted into **INSERT** statements on the view before the view's **ON INSERT** rule is applied.
+>
+> - **ALTER [ COLUMN ] column_name { SET | DROP } NOT NULL** Changes whether a column is marked to allow null values or to reject null values. You can only use **SET NOT NULL** when the column contains no null values.
+>
+> - **ALTER [ COLUMN ] column_name SET STATISTICS [PERCENT] integer** Specifies the per-column statistics-gathering target for subsequent **ANALYZE** operations. The target can be set in the range from 0 to 10000. Set it to **-1** to revert to using the default system statistics target.
+>
+> - **{ADD | DELETE} STATISTICS ((column_1_name, column_2_name [, …]))** Adds or deletes the declaration of collecting multi-column statistics to collect multi-column statistics as needed when **ANALYZE** is performed for a table or a database. The statistics about a maximum of 32 columns can be collected at a time. You are not allowed to add or delete such declaration for system catalogs or foreign tables.
+>
+> - **ALTER [ COLUMN ] column_name SET ( {attribute_option = value} [, … ] )** **ALTER [ COLUMN ] column_name RESET ( attribute_option [, … ] )** Sets or resets per-attribute options. Currently, the only defined per-attribute options are **n_distinct** and **n_distinct_inherited**. **n_distinct** affects statistics of a table, while **n_distinct_inherited** affects the statistics of the table and its subtables. Currently, only **SET/RESET n_distinct** is supported, and **SET/RESET n_distinct_inherited** is forbidden.
+>
+> - **ALTER [ COLUMN ] column_name SET STORAGE { PLAIN | EXTERNAL | EXTENDED | MAIN }** Sets the storage mode for a column. This clause specifies whether this column is held inline or in a secondary TOAST table, and whether the data should be compressed. It is set only for row-store tables and is invalid for column-store tables. If it is set for column-store tables, an error will be displayed when the statement is executed. **SET STORAGE** itself does not change anything in the table. It sets the strategy to be pursued during future table updates.
+
+- **column_constraint** is as follows:
+
+  ```ebnf+diagram
+  column_constraint ::= [ CONSTRAINT constraint_name ]
+      { NOT NULL |
+        NULL |
+        CHECK ( expression ) |
+        DEFAULT default_expr  |
+        UNIQUE index_parameters |
+        PRIMARY KEY index_parameters |
+        ENCRYPTEDWITH(COLUMN_ENCRYPTION_KEY=column_encryption_key,ENCRYPTION_TYPE=encryption_type_value) |
+        REFERENCES reftable [ ( refcolumn ) ] [ MATCH FULL | MATCH PARTIAL | MATCH SIMPLE ]
+            [ ON DELETE action ] [ ON UPDATE action ] }
+      [ DEFERRABLE | NOT DEFERRABLE | INITIALLY DEFERRED | INITIALLY IMMEDIATE ]
+  ```
+
+- **compress_mode** is as follows:
+
+  ```ebnf+diagram
+  compress_mode ::= [ DELTA | PREFIX | DICTIONARY | NUMSTR | NOCOMPRESS ]
+  ```
+
+  - **table_constraint_using_index** used to add the primary key constraint or unique constraint based on the unique index is as follows:
+
+    ```ebnf+diagram
+    table_constraint_using_index ::= [ CONSTRAINT constraint_name ]
+        { UNIQUE | PRIMARY KEY } USING INDEX index_name
+        [ DEFERRABLE | NOT DEFERRABLE | INITIALLY DEFERRED | INITIALLY IMMEDIATE ]
+    ```
+
+  - **table_constraint** is as follows:
+
+    ```ebnf+diagram
+       table_constraint ::= [ CONSTRAINT constraint_name ]
+                { CHECK ( expression ) |
+                  UNIQUE ( column_name [, ... ] ) index_parameters |
+                  PRIMARY KEY ( column_name [, ... ] ) index_parameters |
+                  PARTIAL CLUSTER KEY ( column_name [, ... ] )
+                  FOREIGN KEY ( column_name [, ... ] )  REFERENCES reftable [ ( refcolumn [, ... ] ) ]
+                      [ MATCH FULL | MATCH PARTIAL | MATCH SIMPLE ] [ ON DELETE action ] [ ON UPDATE action ] }
+                [ DEFERRABLE | NOT DEFERRABLE | INITIALLY DEFERRED | INITIALLY IMMEDIATE ]
+    ```
+
+    **index_parameters** is as follows:
+
+    ```ebnf+diagram
+    index_parameters ::= [ WITH ( {storage_parameter = value} [, ... ] ) ]
+        [ USING INDEX TABLESPACE tablespace_name ]
+    ```
+
+- Rename a table. The renaming does not affect stored data.
+
+  ```ebnf+diagram
+  AlterTable ::= ALTER TABLE [ IF EXISTS ] table_name
+      RENAME TO new_table_name;
+  ```
+
+- Rename the specified column in the table.
+
+  ```ebnf+diagram
+  AlterTable ::= ALTER TABLE [ IF EXISTS ] { table_name [*] | ONLY table_name | ONLY ( table_name )}
+      RENAME [ COLUMN ] column_name TO new_column_name;
+  ```
+
+- Rename the constraint of the table.
+
+  ```ebnf+diagram
+  AlterTable ::= ALTER TABLE [ IF EXISTS ] { table_name [*] | ONLY table_name | ONLY ( table_name ) }
+      RENAME CONSTRAINT constraint_name TO new_constraint_name;
+  ```
+
+- Set the schema of the table.
+
+  ```ebnf+diagram
+  AlterTable ::= ALTER TABLE [ IF EXISTS ] table_name
+      SET SCHEMA new_schema;
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > - The schema setting moves the table into another schema. Associated indexes and constraints owned by table columns are migrated as well. Currently, the schema for sequences cannot be changed. If the table has sequences, delete the sequences, and create them again or delete the ownership between the table and sequences. In this way, the table schema can be changed.
+  > - To change the schema of a table, you must also have the **CREATE** permission on the new schema. To add the table as a new child of a parent table, you must own the parent table as well. To alter the owner, you must also be a direct or indirect member of the new owning role, and that role must have the **CREATE** permission on the table's schema. These restrictions enforce that the user can only recreate and delete the table. However, a system administrator can alter the ownership of any table anyway.
+  > - All the actions except for **RENAME** and **SET SCHEMA** can be combined into a list of multiple alterations to apply in parallel. For example, it is possible to add several columns or alter the type of several columns in a single statement. This is useful with large tables, since only one pass over the tables need to be made.
+  > - Adding a **CHECK** or **NOT NULL** constraint will scan the table to validate that existing rows meet the constraint.
+  > - Adding a column with a non-**NULL** default or changing the type of an existing column will rewrite the entire table. Rewriting a large table may take much time and temporarily needs doubled disk space.
+
+- Add columns.
+
+  ```ebnf+diagram
+  AlterTable ::= ALTER TABLE [ IF EXISTS ] table_name
+      ADD ( { column_name data_type [ compress_mode ] [ COLLATE collation ] [ column_constraint [ ... ] ]} [, ...] );
+  ```
+
+- Update columns.
+
+  ```ebnf+diagram
+  AlterTable ::= ALTER TABLE [ IF EXISTS ] table_name
+      MODIFY ( { column_name data_type | column_name [ CONSTRAINT constraint_name ] NOT NULL [ ENABLE ] | column_name [ CONSTRAINT constraint_name ] NULL } [, ...] );
+  ```
+
+## Parameter Description
+
+- **IF EXISTS**
+
+  Sends a notice instead of an error if no tables have identical names. The notice prompts that the table you are querying does not exist.
+
+- **table_name [\*] | ONLY table_name | ONLY ( table_name )**
+
+  **table_name** is the name of the table that you need to modify.
+
+  If **ONLY** is specified, only the table is modified. If **ONLY** is not specified, the table and all subtables are modified. You can add the asterisk (*) option following the table name to specify that all subtables are scanned, which is the default operation.
+
+- **constraint_name**
+
+  Specifies the name of an existing constraint to drop.
+
+- **index_name**
+
+  Specifies the name of an index.
+
+- **storage_parameter**
+
+  Specifies the name of a storage parameter.
+
+  The following option is added for creating an index:
+
+  - parallel_workers (int type)
+
+      Value range: [0,32]. The value  **0**  indicates that concurrency is disabled.
+
+      Number of bgworker threads started when an index is created. For example,  **2**  indicates that two bgworker threads are started to create indexes concurrently.
+
+      If this parameter is not set, the number of started bgworker threads is related to the table size. Generally, the number of started bgworker threads does not exceed four.
+
+- **new_owner**
+
+  Specifies the name of the new table owner.
+
+- **new_tablespace**
+
+  Specifies the new name of the tablespace to which the table belongs.
+
+- **column_name**, **column_1_name**, **column_2_name**
+
+  Specifies the name of a new or existing column.
+
+- **data_type**
+
+  Specifies the type of a new column or a new type of an existing column.
+
+- **compress_mode**
+
+  Compression option of a table field. The clause specifies the compression algorithm preferentially used by the column.
+
+- **collation**
+
+  Specifies the collation rule name of a column. The optional **COLLATE** clause specifies a collation for the new column; if omitted, the collation is the default for the new column. You can run the **select \* from pg_collation;** command to query collation rules from the **pg_collation** system catalog. The default collation rule is the row starting with **default** in the query result.
+
+- **USING expression**
+
+  Specifies how to compute the new column value from the old; if omitted, the default conversion is an assignment cast from old data type to new. A **USING** clause must be provided if there is no implicit or assignment cast from the old to new type.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** **USING** in **ALTER TYPE** can specify any expression involving the old values of the row; that is, it can refer to any columns other than the one being cast. This allows general casting to be done with the **ALTER TYPE** syntax. Because of this flexibility, the **USING** expression is not applied to the column's default value (if any); the result might not be a constant expression as required for a default. This means that when there is no implicit or assignment cast from old to new type, **ALTER TYPE** might fail to convert the default even though a **USING** clause is supplied. In such cases, drop the default with **DROP DEFAULT**, perform the **ALTER TYPE**, and then use **SET DEFAULT** to add a suitable new default. Similar considerations apply to indexes and constraints involving the column.
+
+- **NOT NULL | NULL**
+
+  Sets whether the column allows null values.
+
+- **integer**
+
+  Specifies the constant value of a signed integer. When using **PERCENT**, the range of **integer** is from 0 to 100.
+
+- **attribute_option**
+
+  Specifies an attribute option.
+
+- **PLAIN | EXTERNAL | EXTENDED | MAIN**
+
+  Specifies a column-store mode.
+
+  - **PLAIN** must be used for fixed-length values (such as integers). It must be inline and uncompressed.
+  - **MAIN** is for inline, compressible data.
+  - **EXTERNAL** is for external, uncompressed data. Use of **EXTERNAL** will make substring operations on **text** and **bytea** values run faster, at the penalty of increased storage space.
+  - **EXTENDED** is for external, compressed data. **EXTENDED** is the default for most data types that support non-**PLAIN** storage.
+
+- **CHECK ( expression )**
+
+  New rows or rows to be updated must satisfy for an expression to be true. If any row produces a false result, an error is raised and the database is not modified.
+
+  A check constraint specified as a column constraint should reference only the column's values, while an expression in a table constraint can reference multiple columns.
+
+  Currently, **CHECK ( expression )** does not include subqueries and cannot use variables apart from the current column.
+
+- **DEFAULT default_expr**
+
+  Assigns a default data value for a column.
+
+  The data type of the default expression must match the data type of the column.
+
+  The default expression will be used in any insert operation that does not specify a value for the column. If there is no default value for a column, then the default value is null.
+
+- **UNIQUE index_parameters**
+
+  **UNIQUE ( column_name [, … ] ) index_parameters**
+
+  Specifies that a group of one or more columns of a table can contain only unique values.
+
+- **PRIMARY KEY index_parameters**
+
+  **PRIMARY KEY ( column_name [, … ] ) index_parameters**
+
+  Specifies that a column or columns of a table can contain only unique (non-duplicate) and non-**NULL**  values.
+
+- **REFERENCES reftable [ ( refcolum ) ] [ MATCH matchtype ] [ ON DELETE action ] [ ON UPDATE action ] (column constraint)**
+
+    **FOREIGN KEY ( column_name [, ... ] ) REFERENCES reftable [ ( refcolumn [, ... ] ) ] [ MATCH matchtype ] [ ON DELETE action ] [ ON UPDATE action ] (table constraint)**
+
+    The foreign key constraint requires that the group consisting of one or more columns in the new table should contain and match only the referenced column values in the referenced table. If  **refcolum**  is omitted, the primary key of  **reftable**  is used. The referenced column should be the only column or primary key in the referenced table. A foreign key constraint cannot be defined between a temporary table and a permanent table.
+
+    There are three types of matching between a reference column and a referenced column:
+
+  - **MATCH FULL**: A column with multiple foreign keys cannot be  **NULL**  unless all foreign key columns are  **NULL**.
+  - **MATCH SIMPLE**  (default): Any unexpected foreign key column can be  **NULL**.
+  - **MATCH PARTIAL**: This option is not supported currently.
+
+    In addition, when you perform certain operations on the data in the referenced table, the operations are performed on the corresponding columns in the new table.  **ON DELETE**: specifies the actions to be executed after a referenced row in the referenced table is deleted.  **ON UPDATE**: specifies the operation to be performed when the referenced column data in the referenced table is updated. The possible actions of the  **ON DELETE**  and  **ON UPDATE**  clauses are as follows:
+
+  - **NO ACTION**  (default): When a foreign key is deleted or updated, an error indicating that the foreign key constraint is violated is created. If the constraint is deferrable and there are still any referenced rows, this error will occur when the constraint is checked.
+  - **RESTRICT**: When a foreign key is deleted or updated, an error indicating that the foreign key constraint is violated is created. It is the same as  **NO ACTION**  except that the action cannot be delayed.
+  - **CASCADE**: deletes any row that references the deleted row from the new table, or update the field value of the referenced row in the new table to the new value of the referenced column.
+  - **SET NULL**: sets the referenced field to  **NULL**.
+  - **SET DEFAULT**: sets referenced fields to their default values.
+
+- **DEFERRABLE | NOT DEFERRABLE | INITIALLY DEFERRED | INITIALLY IMMEDIATE**
+
+  Sets whether the constraint can be deferrable.
+
+  - **DEFERRABLE**: deferrable to the end of the transaction and checked using  **SET CONSTRAINTS**.
+  - **NOT DEFERRABLE**: checks immediately after the execution of each command.
+  - **INITIALLY IMMEDIATE**: checks immediately after the execution of each statement.
+  - **INITIALLY DEFERRED**: checks when the transaction ends.
+
+- **PARTIAL CLUSTER KEY**
+
+    Specifies a partial cluster key for storage. When importing data to a column-store table, you can perform local data sorting by specified columns (single or multiple).
+
+- **WITH ( {storage_parameter = value} [, … ] )**
+
+  Specifies an optional storage parameter for a table or an index.
+
+- **tablespace_name**
+
+  Specifies the name of the tablespace where the index locates.
+
+- **COMPRESS|NOCOMPRESS**
+
+  - **NOCOMPRESS**: If the **NOCOMPRESS** keyword is specified, the existing compression feature of the table will not be changed.
+  - **COMPRESS**: If the **COMPRESS** keyword is specified, the table compression feature will be triggered by batch tuple insertion.
+
+- **new_table_name**
+
+  Specifies the new table name.
+
+- **new_column_name**
+
+  Specifies the new name of a specific column in a table.
+
+- **new_constraint_name**
+
+  Specifies the new name of a table constraint.
+
+- **new_schema**
+
+  Specifies the new schema name.
+
+- **CASCADE**
+
+  Automatically drops objects that depend on the dropped column or constraint (for example, views referencing the column).
+
+- **RESTRICT**
+
+  Refuses to drop the column or constraint if there are any dependent objects. This is the default processing.
+
+- **schema_name**
+
+  Specifies the schema name of a table.
+
+## Examples
+
+See **Example** in [CREATE TABLE](60-CREATE-TABLE).
+
+## Helpful Links
+
+[CREATE TABLE](60-CREATE-TABLE)  and  [DROP TABLE](95-DROP-TABLE)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/23-ALTER-TABLE-PARTITION.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/23-ALTER-TABLE-PARTITION.md
new file mode 100644
index 0000000000000000000000000000000000000000..88c491ebadc88e1ef2b8f863f77e79f7ef78c3c8
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/23-ALTER-TABLE-PARTITION.md
@@ -0,0 +1,286 @@
+---
+title: ALTER TABLE PARTITION
+summary: ALTER TABLE PARTITION
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER TABLE PARTITION
+
+## Function
+
+**ALTER TABLE PARTITION** modifies table partition, including adding, deleting, splitting, merging partitions, and modifying partition attributes.
+
+## Precautions
+
+- The tablespace for the added partition cannot be **PG_GLOBAL**.
+- The name of the added partition must be different from names of existing partitions in the partition table.
+- The partition key of the added partition must be the same type as that of the partition table. The key value of the added partition must exceed the upper limit of the last partition range.
+- If the number of partitions in the target partitioned table has reached the maximum value, no more partitions can be added. (The maximum number of partitions in a range partitioned table is 32767, and that in a hash or list partitioned table is 64.)
+- If a partition table has only one partition, the partition cannot be deleted.
+- Use **PARTITION FOR()** to choose partitions. The number of specified values in the brackets should be the same as the column number in customized partition, and they must be consistent.
+- The **Value** partition table does not support the **Alter Partition** operation.
+
+- Column-store tables and row-store tables cannot be partitioned.
+- Partitions cannot be added to an interval partitioned table.
+- Hash partitioned tables do not support splitting, combination, addition, and deletion of partitions.
+- List partitioned tables do not support partition splitting or partition combination.
+
+- Only the partitioned table owner or a user granted with the ALTER permission can run the **ALTER TABLE PARTITION** command. The system administrator has this permission by default.
+
+## Syntax
+
+- Modify the syntax of the table partition.
+
+  ```ebnf+diagram
+  AlterTable ::= ALTER TABLE [ IF EXISTS ] { table_name  [*] | ONLY table_name | ONLY ( table_name  )}
+      action [, ... ];
+  ```
+
+  **action** indicates the following clauses for maintaining partitions. For the partition continuity when multiple clauses are used for partition maintenance, MogDB does **DROP PARTITION** and then **ADD PARTITION**, and finally runs the rest clauses in sequence.
+
+  ```ebnf+diagram
+  action ::= move_clause  |
+      exchange_clause  |
+      row_clause  |
+      merge_clause  |
+      modify_clause  |
+      split_clause  |
+      add_clause  |
+      drop_clause |
+      truncate_clause
+  ```
+
+  - The **move_clause** syntax is used to move the partition to a new tablespace.
+
+    ```ebnf+diagram
+    move_clause ::= MOVE PARTITION { partion_name | FOR ( partition_value [, ...] ) } TABLESPACE tablespacename
+    ```
+
+  - The **exchange_clause** syntax is used to move the data from a general table to a specified partition.
+
+    ```ebnf+diagram
+    exchange_clause ::= EXCHANGE PARTITION { ( partition_name ) | FOR ( partition_value [, ...] ) }
+        WITH TABLE {[ ONLY ] ordinary_table_name | ordinary_table_name * | ONLY ( ordinary_table_name )}
+        [ { WITH | WITHOUT } VALIDATION ] [ VERBOSE ][ UPDATE GLOBAL INDEX ]
+    ```
+
+    The ordinary table and partition whose data is to be exchanged must meet the following requirements:
+
+  - The number of columns of the ordinary table is the same as that of the partition, and their information should be consistent, including: column name, data type, constraint, collation information, storage parameter, and compression information.
+  - The compression information of the ordinary table and partition should be consistent.
+  - The number and information of indexes of the ordinary table and partition should be consistent.
+  - The number and information of constraints of the ordinary table and partition should be consistent.
+
+  - An ordinary table cannot be a temporary table. A partitioned table can only be a range partitioned table, list partitioned table, or hash partitioned table.
+
+  - Ordinary tables and partitioned tables do not support dynamic data masking and row-level access control constraints.
+  - List partitioned tables and hash partitioned tables cannot be column-store.
+
+    > **Notice:**
+    >
+    > - When the exchange is done, the data and tablespace of the ordinary table and partition are exchanged. The statistics about ordinary tables and partitions become unreliable, and they should be analyzed again.
+    > - A non-partition key cannot be used to create a local unique index. Therefore, if an ordinary table contains a unique index, data cannot be exchanged.
+
+  - The **row_clause** syntax is used to set row movement of a partitioned table.
+
+    ```ebnf+diagram
+    row_clause ::= { ENABLE | DISABLE } ROW MOVEMENT
+    ```
+
+  - The **merge_clause** syntax is used to merge partitions into one.
+
+    ```ebnf+diagram
+    merge_clause ::= MERGE PARTITIONS { partition_name } [, ...] INTO PARTITION partition_name
+        [ TABLESPACE tablespacename ][ UPDATE GLOBAL INDEX ]
+    ```
+
+  - The **modify_clause** syntax is used to set whether a partition index is usable.
+
+    ```ebnf+diagram
+    modify_clause ::= MODIFY PARTITION partition_name { UNUSABLE LOCAL INDEXES | REBUILD UNUSABLE LOCAL INDEXES }
+    ```
+
+  - The **split_clause** syntax is used to split one partition into partitions.
+
+    ```ebnf+diagram
+    split_clause ::= SPLIT PARTITION { partition_name | FOR ( partition_value [, ...] ) } { split_point_clause | no_split_point_clause }[ UPDATE GLOBAL INDEX ]
+    ```
+
+  - The **split_point_clause** syntax is used to specify a split point.
+
+      ```ebnf+diagram
+      split_point_clause ::= AT ( partition_value ) INTO ( PARTITION partition_name [ TABLESPACE tablespacename ] , PARTITION partition_name [ TABLESPACE tablespacename ] )
+      ```
+
+      > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+      >
+      > - Column-store tables and row-store tables cannot be partitioned.
+      > - The size of the split point should be in the range of partition keys of the partition of to be split. The split point can only split one partition into two new partitions.
+
+  - The **no_split_point_clause** syntax does not specify a split point.
+
+      ```ebnf+diagram
+      no_split_point_clause ::= INTO { ( partition_less_than_item [, ...] ) | ( partition_start_end_item [, ...] ) }
+      ```
+
+      > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+      >
+      > - The first new partition key specified by **partition_less_than_item** should be greater than that of the previously split partition (if any), and the last partition key specified by **partition_less_than_item** should equal that of the partition being split.
+      > - The first new partition key specified by **partition_start_end_item** should equal that of the former partition (if any), and the last partition key specified by **partition_start_end_item** should equal that of the partition being split.
+      > - **partition_less_than_item** supports a maximum of 4 partition keys, while **partition_start_end_item** supports only one partition key. For details about the supported data types, see [CREATE TABLE PARTITON](62-CREATE-TABLE-PARTITION).
+      > - **partition_less_than_item** and **partition_start_end_item** cannot be used in the same statement.
+
+  - The syntax of **partition_less_than_item** is as follows:
+
+      ```ebnf+diagram
+      partition_less_than_item ::= PARTITION partition_name VALUES LESS THAN ( { partition_value | MAXVALUE }  [, ...] )
+      [ TABLESPACE tablespacename ]
+      ```
+
+  - The syntax of **partition_start_end_item** is as follows. For details about the constraints, see [CREATE TABLE PARTITON](62-CREATE-TABLE-PARTITION).
+
+      ```ebnf+diagram
+      partition_start_end_item ::= PARTITION partition_name {
+              {START(partition_value) END (partition_value) EVERY (interval_value)} |
+              {START(partition_value) END ({partition_value | MAXVALUE})} |
+              {START(partition_value)} |
+              {END({partition_value | MAXVALUE})}
+      } [TABLESPACE tablespace_name]
+
+      ```
+
+  - The **add_clause** syntax is used to add one or more partitions to a specified partitioned table.
+
+    ```ebnf+diagram
+    add_clause ::= ADD PARTITION ( partition_col1_name = partition_col1_value [, partition_col2_name = partition_col2_value ] [, ...] )
+            [ LOCATION 'location1' ]
+                [ PARTITION (partition_colA_name = partition_colA_value [, partition_colB_name = partition_colB_value ] [, ...] ) ]
+                [ LOCATION 'location2' ]
+                ADD {partition_less_than_item | partition_start_end_item| partition_list_item }
+    ```
+
+    The syntax of **partition_list_item** is as follows:
+
+    ```ebnf+diagram
+    partition_list_item ::= PARTITION partition_name VALUES (list_values_clause)
+        [ TABLESPACE tablespacename ]
+    ```
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+    >
+    > - **partition_list_item** supports only one partition key. For details about the data types supported by **partition_list_item**, see **PARTITION BY LIST(partit…**.
+    >
+    > - Interval and hash partitioned tables do not support partition addition.
+
+  - The **drop_clause** syntax is used to remove a partition from a specified partitioned table.
+
+    ```ebnf+diagram
+    drop_clause ::= DROP PARTITION  { partition_name | FOR (  partition_value [, ...] )  } [ UPDATE GLOBAL INDEX ]
+    ```
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+    >
+    > - Hash partitioned table does not support partition deletion.
+    > - List partitioned table supports sub-partition deletion only by sub-partition name.
+
+  - The  **truncate_clause**  syntax is used to remove a specified partition from a partitioned table.
+
+    ```ebnf+diagram
+    truncate_clause ::= TRUNCATE PARTITION  { partition_name | FOR (  partition_value [, ...] )  } [ UPDATE GLOBAL INDEX ]
+    ```
+
+- The syntax for modifying the name of a partition is as follows:
+
+  ```ebnf+diagram
+  AlterTable ::= ALTER TABLE [ IF EXISTS ] { table_name [*] | ONLY table_name | ONLY ( table_name  )}
+      RENAME PARTITION { partion_name | FOR ( partition_value [, ...] ) } TO partition_new_name;
+  ```
+
+## Parameter Description
+
+- **table_name**
+
+  Specifies the name of a partitioned table.
+
+  Value range: an existing table name
+
+- **partition_name**
+
+  Specifies the name of a partition.
+
+  Value range: an existing partition name
+
+- **tablespacename**
+
+  Specifies which tablespace the partition moves to.
+
+  Value range: an existing tablespace name
+
+- **partition_value**
+
+  Specifies the key value of a partition.
+
+  The value specified by **PARTITION FOR ( partition_value [, …] )** can uniquely identify a partition.
+
+  Value range: partition keys for the partition to be renamed
+
+- **UNUSABLE LOCAL INDEXES**
+
+  Sets all the indexes unusable in the partition.
+
+- **REBUILD UNUSABLE LOCAL INDEXES**
+
+  Rebuilds all the indexes in the partition.
+
+- **ENABLE/DISABLE ROW MOVEMET**
+
+    Sets row movement.
+
+    If the tuple value is updated on the partition key during the **UPDATE** action, the partition where the tuple is located is altered. Setting this parameter enables error messages to be reported or movement of the tuple between partitions.
+
+    Value range:
+
+  - **ENABLE**: Row movement is enabled.
+  - **DISABLE**: Row movement is disabled.
+
+    The default value is **ENABLE**.
+
+- **ordinary_table_name**
+
+  Specifies the name of the ordinary table whose data is to be migrated.
+
+  Value range: an existing table name
+
+- **{ WITH | WITHOUT } VALIDATION**
+
+    Checks whether the ordinary table data meets the specified partition key range of the partition to be migrated.
+
+    Value range:
+
+  - **WITH**: checks whether the ordinary table data meets the partition key range of the partition to be migrated. If any data does not meet the required range, an error is reported.
+  - **WITHOUT**: does not check whether the ordinary table data meets the partition key range of the partition to be migrated.
+
+    The default value is **WITH**.
+
+    The check is time consuming, especially when the data volume is large. Therefore, use **WITHOUT** when you are sure that the current ordinary table data meets the partition key range of the partition to be migrated.
+
+- **VERBOSE**
+
+  When **VALIDATION** is **WITH**, if the ordinary table contains data that is out of the partition key range, insert the data to the correct partition. If there is no correct partition where the data can be inserted to, an error is reported.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** Only when **VALIDATION** is **WITH**, **VERBOSE** can be specified.
+
+- **partition_new_name**
+
+  Specifies the new name of a partition.
+
+  Value range: a string. It must comply with the identifier naming convention.
+
+## Example
+
+See **Examples** in [CREATE TABLE PARTITION](62-CREATE-TABLE-PARTITION).
+
+## Helpful Links
+
+[CREATE TABLE PARTITION](62-CREATE-TABLE-PARTITION)，[DROP TABLE](95-DROP-TABLE)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/23.1-ALTER-TABLE-SUBPARTITION.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/23.1-ALTER-TABLE-SUBPARTITION.md
new file mode 100644
index 0000000000000000000000000000000000000000..5056579ad3f0899e122b2b5ea8072ba29898d8e4
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/23.1-ALTER-TABLE-SUBPARTITION.md
@@ -0,0 +1,81 @@
+---
+title: ALTER TABLE SUBPARTITION
+summary: ALTER TABLE SUBPARTITION
+author: Zhang Cuiping
+date: 2021-11-01
+---
+
+# ALTER TABLE SUBPARTITION
+
+## Function
+
+**ALTER TABLE SUBPARTITION** modifies partitions from a level-2 partitioned table, including clearing the partitions and splitting the partitions.
+
+## Precautions
+
+- Currently, partitions from a level-2 partitioned table can be cleared or split only.
+- Only level-2 partitions (leaf nodes) can be split and only the range and list partitioning policies can be used. The list partitioning policy can be used only when default partitions are split.
+- Only the partitioned table owner or a user granted with the ALTER permission can run the **ALTER TABLE PARTITION** command. The system administrator has this permission by default.
+
+## Syntax
+
+- Modify the syntax of the table partition.
+
+  ```ebnf+diagram
+  AlterTable ::= ALTER TABLE [ IF EXISTS ] { table_name  [*] | ONLY table_name | ONLY ( table_name  )}
+      action [, ... ];
+  ```
+
+  **action** indicates the following clauses for maintaining partitions.
+
+  ```ebnf+diagram
+  action::= split_clause  |
+     truncate_clause
+  ```
+
+- The **split_clause** syntax is used to split one partition into different partitions.
+
+  ```ebnf+diagram
+  split_clause ::= SPLIT SUBPARTITION { subpartition_name} { split_point_clause  } [ UPDATE GLOBAL INDEX ]
+  ```
+
+  The **split_point_clause** syntax is used to specify a split point.
+
+  ```ebnf+diagram
+  split_point_clause ::= AT ( subpartition_value ) INTO ( SUBPARTITION subpartition_name [ TABLESPACE tablespacename ] , SUBPARTITION subpartition_name [ TABLESPACE tablespacename ] )
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+  >
+  > - The size of split point should be in the range of splitting partition key.
+  > - One partition can be split into only two new partitions.
+
+- The **truncate_clause** syntax is used to remove a specified partition from a partitioned table.
+
+  ```ebnf+diagram
+  truncate_clause ::= TRUNCATE SUBPARTITION  { subpartition_name } [ UPDATE GLOBAL INDEX ]
+  ```
+
+## Parameter Description
+
+- **table_name**
+
+  Specifies the name of a partitioned table.
+
+  Value range: an existing partitioned table name
+
+- **subpartition_name**
+
+  Specifies the name of a level-2 partition name.
+
+  Value range: an existing level-2 partition name
+
+- **tablespacename**
+
+  Specifies which tablespace the partition moves to.
+
+  Value range: an existing tablespace name
+
+## Examples
+
+See the examples in [CREATE TABLE SUBPARTITION](62.1-CREATE-TABLE-SUBPARTITION).
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/24-ALTER-TABLESPACE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/24-ALTER-TABLESPACE.md
new file mode 100644
index 0000000000000000000000000000000000000000..6d6dd4625041d8d62f125558c1698e26962f6b38
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/24-ALTER-TABLESPACE.md
@@ -0,0 +1,127 @@
+---
+title: ALTER TABLESPACE
+summary: ALTER TABLESPACE
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER TABLESPACE
+
+## Function
+
+**ALTER TABLESPACE** modifies the attributes of a tablespace.
+
+## Precautions
+
+- Only the tablespace owner or a user granted with the ALTER permission can run the **ALTER TABLESPACE** command. The system administrator has this permission by default. To modify a tablespace owner, you must be the tablespace owner or system administrator and a member of the new owner role.
+
+- To change the owner, you must also be a direct or indirect member of the new owning role.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** If **new_owner** is the same as **old_owner**, the current user will not be verified. A message indicating successful **ALTER** execution is displayed.
+
+## Syntax
+
+- The syntax of renaming a tablespace is as follows:
+
+  ```ebnf+diagram
+  AlterTablespace ::= ALTER TABLESPACE tablespace_name
+      RENAME TO new_tablespace_name;
+  ```
+
+- The syntax of setting the owner of a tablespace is as follows:
+
+  ```ebnf+diagram
+  AlterTablespace ::= ALTER TABLESPACE tablespace_name
+      OWNER TO new_owner;
+  ```
+
+- The syntax of setting the attributes of a tablespace is as follows:
+
+  ```ebnf+diagram
+  AlterTablespace ::= ALTER TABLESPACE tablespace_name
+      SET ( {tablespace_option = value} [, ... ] );
+  ```
+
+- The syntax of resetting the attributes of a tablespace is as follows:
+
+  ```ebnf+diagram
+  AlterTablespace ::= ALTER TABLESPACE tablespace_name
+      RESET ( { tablespace_option } [, ...] );
+  ```
+
+- The syntax of setting the quota of a tablespace is as follows:
+
+  ```ebnf+diagram
+  AlterTablespace ::= ALTER TABLESPACE tablespace_name
+      RESIZE MAXSIZE { UNLIMITED | 'space_size'};
+  ```
+
+## Parameter Description
+
+- **tablespace_name**
+
+  Specifies the tablespace to be modified.
+
+  Value range: an existing table name
+
+- **new_tablespace_name**
+
+  Specifies the new name of a tablespace.
+
+  The new name cannot start with **PG_**.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **new_owner**
+
+  Specifies the new owner of the tablespace.
+
+  Value range: an existing username
+
+- **tablespace_option**
+
+    Sets or resets the parameters of a tablespace.
+
+    Value range:
+
+  - seq_page_cost: sets the optimizer to calculate the cost of obtaining disk pages in sequence. The default value is **1.0**.
+
+  - **random_page_cost**: sets the optimizer to calculate the cost of obtaining disk pages in a non-sequential manner. The default value is **4.0**.
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+    >
+    > - The value of **random_page_cost** is relative to that of **seq_page_cost**. It is meaningless when the value is equal to or less than the value of **seq_page_cost**.
+    > - The prerequisite for the default value **4.0** is that the optimizer uses indexes to scan table data and the hit ratio of table data in the cache is about 90%.
+    > - If the size of the table data space is smaller than that of the physical memory, decrease the value to a proper level. On the contrary, if the hit ratio of table data in the cache is lower than 90%, increase the value.
+    > - If random-access memory like SSD is adopted, the value can be decreased to a certain degree to reflect the cost of true random scan.
+
+  Value range: a positive floating point number
+
+- **RESIZE MAXSIZE**
+
+  Resets the maximum size of tablespace.
+
+  Value range:
+
+  - **UNLIMITED**: No limit is set for the tablespace.
+
+  - Determined by **space_size**. For details about the format, see [CREATE TABLESPACE](63-CREATE-TABLESPACE).
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+    >
+    > - If the adjusted quota is smaller than the current tablespace usage, the adjustment is successful. You need to decrease the tablespace usage to a value less than the new quota before writing data to the tablespace.
+    >
+    > - You can also use the following statement to change the value of **MAXSIZE**:
+    >
+    > ```sql
+    > ALTER TABLESPACE tablespace_name RESIZE MAXSIZE
+    > { 'UNLIMITED' | 'space_size'};
+    > ```
+
+## Examples
+
+See **Examples** in [CREATE TABLESPACE](63-CREATE-TABLESPACE).
+
+## Helpful Links
+
+[CREATE TABLESPACE](63-CREATE-TABLESPACE)，[DROP TABLESPACE](96-DROP-TABLESPACE)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/25-ALTER-TEXT-SEARCH-CONFIGURATION.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/25-ALTER-TEXT-SEARCH-CONFIGURATION.md
new file mode 100644
index 0000000000000000000000000000000000000000..8a7025d9c5edf8cb3fe1eb3b380fc8e6dbbd7ef6
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/25-ALTER-TEXT-SEARCH-CONFIGURATION.md
@@ -0,0 +1,180 @@
+---
+title: ALTER TEXT SEARCH CONFIGURATION
+summary: ALTER TEXT SEARCH CONFIGURATION
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER TEXT SEARCH CONFIGURATION
+
+## Function
+
+**ALTER TEXT SEARCH CONFIGURATION** modifies the definition of a text search configuration. You can modify its mappings from token types to dictionaries, change the configuration's name or owner, or modify the parameters.
+
+The **ADD MAPPING FOR** form installs a list of dictionaries to be consulted for the specified token types; an error will be generated if there is already a mapping for any of the token types.
+
+The **ALTER MAPPING FOR** form removes existing mapping for those token types and then adds specified mappings.
+
+**ALTER MAPPING REPLACE …** **WITH …** and **ALTER MAPPING FOR…** **REPLACE …** **WITH …** options replace **old_dictionary** with **new_dictionary**. Note that only when **pg_ts_config_map** has tuples corresponding to **maptokentype** and **old_dictionary**, the update will succeed. If the update fails, no messages are returned.
+
+The **DROP MAPPING FOR** form deletes all dictionaries for the specified token types in the text search configuration. If **IF EXISTS** is not specified and the string type mapping specified by **DROP MAPPING FOR** does not exist in text search configuration, an error will occur in the database.
+
+## Precautions
+
+- If a search configuration is referenced (to create indexes), users are not allowed to modify the text search configuration.
+- To use **ALTER TEXT SEARCH CONFIGURATION**, you must be the owner of the configuration.
+
+## Syntax
+
+- Add text search configuration string mapping.
+
+  ```ebnf+diagram
+  AlterTextSearchConfiguration ::= ALTER TEXT SEARCH CONFIGURATION name
+  ADD MAPPING FOR token_type [, ... ] WITH dictionary_name [, ... ];
+  ```
+
+- Modify the text search configuration dictionary syntax.
+
+  ```ebnf+diagram
+  AlterTextSearchConfiguration ::= ALTER TEXT SEARCH CONFIGURATION name
+  ALTER MAPPING FOR token_type [, ... ] REPLACE old_dictionary WITH new_dictionary;
+  ```
+
+- Modify the text search configuration string.
+
+  ```ebnf+diagram
+  AlterTextSearchConfiguration ::= ALTER TEXT SEARCH CONFIGURATION name
+  ALTER MAPPING FOR token_type [, ... ] WITH dictionary_name [, ... ];
+  ```
+
+- Change the text search configuration dictionary.
+
+  ```ebnf+diagram
+  AlterTextSearchConfiguration ::= ALTER TEXT SEARCH CONFIGURATION name
+  ALTER MAPPING REPLACE old_dictionary WITH new_dictionary;
+  ```
+
+- Remove text search configuration string mapping.
+
+  ```ebnf+diagram
+  AlterTextSearchConfiguration ::= ALTER TEXT SEARCH CONFIGURATION name
+  DROP MAPPING [ IF EXISTS ] FOR token_type [, ... ];
+  ```
+
+- Rename the owner of text search configuration.
+
+  ```ebnf+diagram
+  AlterTextSearchConfiguration ::= ALTER TEXT SEARCH CONFIGURATION name OWNER TO new_owner;
+  ```
+
+- Rename the text search configuration.
+
+  ```ebnf+diagram
+  AlterTextSearchConfiguration ::= ALTER TEXT SEARCH CONFIGURATION name RENAME TO new_name;
+  ```
+
+- Rename the namespace of text search configuration.
+
+  ```ebnf+diagram
+  AlterTextSearchConfiguration ::= ALTER TEXT SEARCH CONFIGURATION name SET SCHEMA new_schema;
+  ```
+
+- Modify the attributes of the text search configuration.
+
+  ```ebnf+diagram
+  AlterTextSearchConfiguration ::= ALTER TEXT SEARCH CONFIGURATION name SET ( { configuration_option = value } [, ...] );
+  ```
+
+- Reset the attributes of text search configuration.
+
+  ```ebnf+diagram
+  AlterTextSearchConfiguration ::= ALTER TEXT SEARCH CONFIGURATION name RESET ( {configuration_option} [, ...] );
+  ```
+
+## Parameter Description
+
+- **name**
+
+  Specifies the name (optionally schema-qualified) of an existing text search configuration.
+
+- **token_type**
+
+  Specifies the name of a token type that is emitted by the configuration's parser. For details, see **Parser**.
+
+- **dictionary_name**
+
+  Specifies the name of a text search dictionary. If multiple dictionaries are listed, they are searched in the specified order.
+
+- **old_dictionary**
+
+  Specifies the name of a text search dictionary to be replaced in the mapping.
+
+- **new_dictionary**
+
+  Specifies the name of a text search dictionary to be substituted for **old_dictionary**.
+
+- **new_owner**
+
+  Specifies the new owner of the text search configuration.
+
+- **new_name**
+
+  Specifies the new name of the text search configuration.
+
+- **new_schema**
+
+  Specifies the new schema for the text search configuration.
+
+- **configuration_option**
+
+  Specifies the text search configuration option. For details, see **CREATE TEXT SEARCH CONFIGURATION**.
+
+- **value**
+
+  Specifies the value of text search configuration option.
+
+## Examples
+
+```sql
+-- Create a text search configuration.
+mogdb=# CREATE TEXT SEARCH CONFIGURATION english_1 (parser=default);
+CREATE TEXT SEARCH CONFIGURATION
+
+-- Add text search configuration string mapping.
+mogdb=# ALTER TEXT SEARCH CONFIGURATION english_1 ADD MAPPING FOR word WITH simple,english_stem;
+ALTER TEXT SEARCH CONFIGURATION
+
+-- Add text search configuration string mapping.
+mogdb=# ALTER TEXT SEARCH CONFIGURATION english_1 ADD MAPPING FOR email WITH english_stem, french_stem;
+ALTER TEXT SEARCH CONFIGURATION
+
+-- Query information about the text search configuration.
+mogdb=# SELECT b.cfgname,a.maptokentype,a.mapseqno,a.mapdict,c.dictname FROM pg_ts_config_map a,pg_ts_config b, pg_ts_dict c WHERE a.mapcfg=b.oid AND a.mapdict=c.oid AND b.cfgname='english_1' ORDER BY 1,2,3,4,5;
+  cfgname  | maptokentype | mapseqno | mapdict |   dictname
+-----------+--------------+----------+---------+--------------
+ english_1 |            2 |        1 |    3765 | simple
+ english_1 |            2 |        2 |   12960 | english_stem
+ english_1 |            4 |        1 |   12960 | english_stem
+ english_1 |            4 |        2 |   12964 | french_stem
+(4 rows)
+
+-- Add text search configuration string mapping.
+mogdb=# ALTER TEXT SEARCH CONFIGURATION english_1 ALTER MAPPING REPLACE french_stem with german_stem;
+ALTER TEXT SEARCH CONFIGURATION
+
+-- Query information about the text search configuration.
+mogdb=# SELECT b.cfgname,a.maptokentype,a.mapseqno,a.mapdict,c.dictname FROM pg_ts_config_map a,pg_ts_config b, pg_ts_dict c WHERE a.mapcfg=b.oid AND a.mapdict=c.oid AND b.cfgname='english_1' ORDER BY 1,2,3,4,5;
+  cfgname  | maptokentype | mapseqno | mapdict |   dictname
+-----------+--------------+----------+---------+--------------
+ english_1 |            2 |        1 |    3765 | simple
+ english_1 |            2 |        2 |   12960 | english_stem
+ english_1 |            4 |        1 |   12960 | english_stem
+ english_1 |            4 |        2 |   12966 | german_stem
+(4 rows)
+```
+
+See **Examples** in [CREATE TEXT SEARCH CONFIGURATION](64-CREATE-TEXT-SEARCH-CONFIGURATION).
+
+## Helpful Links
+
+[CREATE TEXT SEARCH CONFIGURATION](64-CREATE-TEXT-SEARCH-CONFIGURATION)，  [DROP TEXT SEARCH CONFIGURATION](97-DROP-TEXT-SEARCH-CONFIGURATION)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/26-ALTER-TEXT-SEARCH-DICTIONARY.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/26-ALTER-TEXT-SEARCH-DICTIONARY.md
new file mode 100644
index 0000000000000000000000000000000000000000..871c887430d0426ef386d42029357b6bdb22390b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/26-ALTER-TEXT-SEARCH-DICTIONARY.md
@@ -0,0 +1,105 @@
+---
+title: ALTER TEXT SEARCH DICTIONARY
+summary: ALTER TEXT SEARCH DICTIONARY
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER TEXT SEARCH DICTIONARY
+
+## Function
+
+**ALTER TEXT SEARCH DICTIONARY** modifies the definition of a full-text search dictionary, including its parameters, name, owner, and schema.
+
+## Precautions
+
+- Predefined dictionaries do not support the **ALTER** operations.
+- Only the owner of a dictionary or a system administrator can perform the **ALTER** operations.
+- After a dictionary is created or modified, any modification to the customized dictionary definition file in the **filepath** directory does not affect the dictionary in the database. To use these modifications in the database, run the **ALTER TEXT SEARCH DICTIONARY** statement to update the definition file of the corresponding dictionary.
+
+## Syntax
+
+- Modify the dictionary definition.
+
+  ```ebnf+diagram
+  AlterTextSearchDictionary ::= ALTER TEXT SEARCH DICTIONARY name (
+      option [ = value ] [, ... ]
+  );
+  ```
+
+- Rename a dictionary.
+
+  ```ebnf+diagram
+  AlterTextSearchDictionary ::= ALTER TEXT SEARCH DICTIONARY name RENAME TO new_name;
+  ```
+
+- Set the schema of the dictionary.
+
+  ```ebnf+diagram
+  AlterTextSearchDictionary ::= ALTER TEXT SEARCH DICTIONARY name SET SCHEMA new_schema;
+  ```
+
+- Change the owner of the dictionary.
+
+  ```ebnf+diagram
+  AlterTextSearchDictionary ::= ALTER TEXT SEARCH DICTIONARY name OWNER TO new_owner;
+  ```
+
+## Parameter Description
+
+- **name**
+
+  Specifies the name of an existing dictionary. (If you do not specify a schema name, the dictionary in the current schema will be used.)
+
+  Value range: an existing dictionary name
+
+- **option**
+
+  Specifies the parameter name to be modified. Each type of dictionaries has a template containing their custom parameters. Parameters function in a way irrelevant to their setting sequence. For details about the parameters, see **option**.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > - The value of **TEMPLATE** in the dictionary cannot be changed.
+  > - To specify a dictionary, specify both the dictionary definition file path (**FILEPATH**) and the file name.
+  > - The name of a dictionary definition file can contain only lowercase letters, digits, and underscores (_).
+
+- **value**
+
+  Specifies the new value of a parameter. If the equal sign (=) and *value* are omitted, the previous settings of the option are deleted and the default value is used.
+
+  Value range: valid values defined by **option**.
+
+- **new_name**
+
+  Specifies the new name of a dictionary.
+
+  Value range: a string, which complies with the identifier naming convention. A value can contain a maximum of 63 characters.
+
+- **new_owner**
+
+  Specifies the new owner of a dictionary.
+
+  Value range: an existing username
+
+- **new_schema**
+
+  Specifies the new schema of a dictionary.
+
+  Value range: an existing schema
+
+## Examples
+
+```sql
+-- Modify the definition of stop words in Snowball dictionaries. Retain the values of other parameters.
+mogdb=# ALTER TEXT SEARCH DICTIONARY my_dict ( StopWords = newrussian, FilePath = 'file:///home/dicts' );
+
+-- Modify the Language parameter in Snowball dictionaries and delete the definition of stop words.
+mogdb=# ALTER TEXT SEARCH DICTIONARY my_dict (Language = dutch, StopWords);
+
+-- Update the dictionary definition and do not change any other content.
+mogdb=# ALTER TEXT SEARCH DICTIONARY my_dict ( dummy );
+```
+
+## Helpful Links
+
+[CREATE TEXT SEARCH DICTIONARY](65-CREATE-TEXT-SEARCH-DICTIONARY)，[DROP TEXT SEARCH DICTIONARY](98-DROP-TEXT-SEARCH-DICTIONARY)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/27-ALTER-TRIGGER.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/27-ALTER-TRIGGER.md
new file mode 100644
index 0000000000000000000000000000000000000000..fe8e81616765056b6017397c5fb1479bd8d1bef4
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/27-ALTER-TRIGGER.md
@@ -0,0 +1,50 @@
+---
+title: ALTER TRIGGER
+summary: ALTER TRIGGER
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER TRIGGER
+
+## Function
+
+**ALTER TRIGGER** modifies the definition of a trigger.
+
+## Precautions
+
+Only the owner of a table where the trigger is created and a system administrator can run the **ALTER TRIGGER** statement.
+
+## Syntax
+
+```ebnf+diagram
+AlterTrigger ::= ALTER TRIGGER trigger_name ON table_name RENAME TO new_name;
+```
+
+## Parameter Description
+
+- **trigger_name**
+
+  Specifies the name of the trigger to be modified.
+
+  Value range: an existing trigger
+
+- **table_name**
+
+  Specifies the name of the table where the trigger to be modified is located.
+
+  Value range: an existing table having a trigger
+
+- **new_name**
+
+  Specifies the new name after modification.
+
+  Value range: a string, which complies with the identifier naming convention. A value contains a maximum of 63 characters and cannot be the same as other triggers on the same table.
+
+## Examples
+
+See examples in [CREATE TRIGGER](66-CREATE-TRIGGER).
+
+## Helpful Links
+
+[CREATE TRIGGER](66-CREATE-TRIGGER)，[DROP TRIGGER](99-DROP-TRIGGER)，[ALTER TABLE](27-ALTER-TRIGGER)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/28-ALTER-TYPE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/28-ALTER-TYPE.md
new file mode 100644
index 0000000000000000000000000000000000000000..a86aab44c963a150a277629f628a672645a44c5f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/28-ALTER-TYPE.md
@@ -0,0 +1,177 @@
+---
+title: ALTER TYPE
+summary: ALTER TYPE
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER TYPE
+
+## Function
+
+**ALTER TYPE** modifies the definition of a type.
+
+## Precautions
+
+Only the type owner or a user granted with the ALTER permission can run the **ALTER TYPE** command. The system administrator has this permission by default. To modify the owner or schema of a type, you must be a type owner or system administrator and a member of the new owner role.
+
+## Syntax
+
+- Modify a type.
+
+  ```ebnf+diagram
+  AlterType ::= ALTER TYPE name action [, ... ];
+  ```
+
+  ```ebnf+diagram
+  AlterType ::= ALTER TYPE name OWNER TO { new_owner | CURRENT_USER | SESSION_USER };
+  ```
+
+  ```ebnf+diagram
+  AlterType ::= ALTER TYPE name RENAME ATTRIBUTE attribute_name TO new_attribute_name [ CASCADE | RESTRICT ];
+  ```
+
+  ```ebnf+diagram
+  AlterType ::= ALTER TYPE name RENAME TO new_name;
+  ```
+
+  ```ebnf+diagram
+  AlterType ::= ALTER TYPE name SET SCHEMA new_schema;
+  ```
+
+  ```ebnf+diagram
+  AlterType ::= ALTER TYPE name ADD VALUE [ IF NOT EXISTS ] new_enum_value [ { BEFORE | AFTER } neighbor_enum_value ];
+  ```
+
+  ```ebnf+diagram
+  AlterType ::= ALTER TYPE name RENAME VALUE existing_enum_value TO new_enum_value;
+  ```
+
+  where action is one of:
+
+  ```ebnf+diagram
+  action ::= ADD ATTRIBUTE attribute_name data_type [ COLLATE collation ] [ CASCADE | RESTRICT ];
+  ```
+
+  ```ebnf+diagram
+  action ::= DROP ATTRIBUTE [ IF EXISTS ] attribute_name [ CASCADE | RESTRICT ];
+  ```
+
+  ```ebnf+diagram
+  action ::= ALTER ATTRIBUTE attribute_name [ SET DATA ] TYPE data_type [ COLLATE collation ] [ CASCADE | RESTRICT ];
+  ```
+
+- Add a new attribute to a composite type.
+
+  ```ebnf+diagram
+  AlterType ::= ALTER TYPE name ADD ATTRIBUTE attribute_name data_type [ COLLATE collation ] [ CASCADE | RESTRICT ];
+  ```
+
+- Delete an attribute from a composite type.
+
+  ```ebnf+diagram
+  AlterType ::= ALTER TYPE name DROP ATTRIBUTE [ IF EXISTS ] attribute_name [ CASCADE | RESTRICT ];
+  ```
+
+- Change the type of an attribute in a composite type.
+
+  ```ebnf+diagram
+  AlterType ::= ALTER TYPE name ALTER ATTRIBUTE attribute_name [ SET DATA ] TYPE data_type [ COLLATE collation ] [ CASCADE | RESTRICT ];
+  ```
+
+- Change the owner of a type.
+
+  ```ebnf+diagram
+  AlterType ::= ALTER TYPE name OWNER TO { new_owner | CURRENT_USER | SESSION_USER };
+  ```
+
+- Change the name of a type or the name of an attribute in a composite type.
+
+  ```ebnf+diagram
+  AlterType ::= ALTER TYPE name RENAME TO new_name;
+  ```
+
+  ```ebnf+diagram
+  AlterType ::= ALTER TYPE name RENAME ATTRIBUTE attribute_name TO new_attribute_name [ CASCADE | RESTRICT ];
+  ```
+
+- Move a type to a new schema.
+
+  ```ebnf+diagram
+  AlterType ::= ALTER TYPE name SET SCHEMA new_schema;
+  ```
+
+- Add a new value to an enumerated type.
+
+  ```ebnf+diagram
+  AlterType ::= ALTER TYPE name ADD VALUE [ IF NOT EXISTS ] new_enum_value [ { BEFORE | AFTER } neighbor_enum_value ];
+  ```
+
+- Change an enumerated value in the value list.
+
+  ```ebnf+diagram
+  AlterType ::= ALTER TYPE name RENAME VALUE existing_enum_value TO new_enum_value;
+  ```
+
+## Parameter Description
+
+- **name**
+
+  Specifies the name of an existing type that needs to be modified (optionally schema-qualified).
+
+- **new_name**
+
+  Specifies the new name of the type.
+
+- **new_owner**
+
+  Specifies the new owner of the type.
+
+- **new_schema**
+
+  Specifies the new schema of the type.
+
+- **attribute_name**
+
+  Specifies the name of the attribute to be added, modified, or deleted.
+
+- **new_attribute_name**
+
+  Specifies the new name of the attribute to be renamed.
+
+- **data_type**
+
+  Specifies the data type of the attribute to be added, or the new type of the attribute to be modified.
+
+- **new_enum_value**
+
+  Specifies a new enumerated value. It is a non-null string with a maximum length of 63 bytes.
+
+- **neighbor_enum_value**
+
+  Specifies an existing enumerated value before or after which a new enumerated value will be added.
+
+- **existing_enum_value**
+
+  Specifies an enumerated value to be changed. It is a non-null string with a maximum length of 63 bytes.
+
+- **CASCADE**
+
+  Determines that the type to be modified, its associated records, and subtables that inherit the type will all be updated.
+
+- **RESTRICT**
+
+  Refuses to update the associated records of the modified type. This is the default action.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+  >
+  > - **ADD ATTRIBUTE**, **DROP ATTRIBUTE**, and **ALTER ATTRIBUTE** can be combined for processing. For example, it is possible to add several attributes or change the types of several attributes at the same time in one command.
+  > - To modify a schema of a type, you must have the **CREATE** permission on the new schema. To change the owner, you must be a direct or indirect member of the new owning role, and the member must have the **CREATE** permission on the schema of this type. (These restrictions enforce that the user can only recreate and delete the type. However, the system administrator can change ownership of any type in any way.) To add an attribute or modify the type of an attribute, you must also have the **USAGE** permission of this type.
+
+## Example
+
+See **Examples** in [CREATE TYPE](67-CREATE-TYPE).
+
+## Helpful Links
+
+[CREATE TYPE](67-CREATE-TYPE)，[DROP TYPE](100-DROP-TYPE)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/29-ALTER-USER.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/29-ALTER-USER.md
new file mode 100644
index 0000000000000000000000000000000000000000..102a8a2999394117846a525acfa542af2172aea4
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/29-ALTER-USER.md
@@ -0,0 +1,113 @@
+---
+title: ALTER USER
+summary: ALTER USER
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER USER
+
+## Function
+
+**ALTER USER** modifies the attributes of a database user.
+
+## Precautions
+
+Session parameters modified by **ALTER USER** apply to a specified user and take effect in the next session.
+
+## Syntax
+
+- Modify user permissions or other information.
+
+  ```ebnf+diagram
+  AlterUser ::= ALTER USER user_name [ [ WITH ] option [ ... ] ];
+  ```
+
+  The **option** clause is as follows:
+
+  ```ebnf+diagram
+  option ::= { CREATEDB | NOCREATEDB }
+      | { CREATEROLE | NOCREATEROLE }
+      | { INHERIT | NOINHERIT }
+      | { AUDITADMIN | NOAUDITADMIN }
+      | { SYSADMIN | NOSYSADMIN }
+      | { USEFT | NOUSEFT }
+      | { LOGIN | NOLOGIN }
+      | { REPLICATION | NOREPLICATION }
+      | {INDEPENDENT | NOINDEPENDENT}
+      | {VCADMIN | NOVCADMIN}
+      | CONNECTION LIMIT connlimit
+      | [ ENCRYPTED | UNENCRYPTED ] PASSWORD { 'password' [EXPIRED] | DISABLE | EXPIRED }
+      | [ ENCRYPTED | UNENCRYPTED ] IDENTIFIED BY { 'password' [ REPLACE 'old_password' | EXPIRED ] | DISABLE }
+      | VALID BEGIN 'timestamp'
+      | VALID UNTIL 'timestamp'
+      | RESOURCE POOL 'respool'
+      | PERM SPACE 'spacelimit'
+      | ACCOUNT { LOCK | UNLOCK }
+      | PGUSER
+  ```
+
+- Change the username.
+
+  ```ebnf+diagram
+  AlterUser ::= ALTER USER user_name
+      RENAME TO new_name;
+  ```
+
+- Change the value of a specified parameter associated with the user.
+
+  ```ebnf+diagram
+  AlterUser ::= ALTER USER user_name
+      SET configuration_parameter { { TO | = } { value | DEFAULT } | FROM CURRENT };
+  ```
+
+- Reset the value of a specified parameter associated with the user.
+
+  ```ebnf+diagram
+  AlterUser ::= ALTER USER user_name
+      RESET { configuration_parameter | ALL };
+  ```
+
+## Parameter Description
+
+- **user_name**
+
+  Specifies the current username.
+
+  Value range: an existing username
+
+- **new_password**
+
+  Specifies a new password.
+
+  The new password must:
+
+  - Differ from the old password.
+  - Contain at least eight characters. This is the default length.
+  - Differ from the username or the username spelled backward.
+  - Contain at least three types of the following four types of characters: uppercase characters (A to Z), lowercase characters (a to z), digits (0 to 9), and special characters, including: ~!@#$%^&*()-_=+\|[{}];:,&lt;.&gt;/?
+
+  Value range: a string
+
+- **old_password**
+
+  Specifies the old password.
+
+- **ACCOUNT LOCK | ACCOUNT UNLOCK**
+
+  - **ACCOUNT LOCK**: locks an account to forbid login to databases.
+  - **ACCOUNT UNLOCK**: unlocks an account to allow login to databases.
+
+- **PGUSER**
+
+  In the current version, the **PGUSER** attribute of a user cannot be modified.
+
+For details about other parameters, see "Parameter Description" in [CREATE ROLE](54-CREATE-ROLE) and [ALTER ROLE](12-ALTER-ROLE).
+
+## Example
+
+See **Example** in [CREATE USER](68-CREATE-USER).
+
+## Helpful Links
+
+[CREATE ROLE](54-CREATE-ROLE),  [CREATE USER](68-CREATE-USER),  [DROP USER](101-DROP-USER)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/3-ALTER-DATA-SOURCE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/3-ALTER-DATA-SOURCE.md
new file mode 100644
index 0000000000000000000000000000000000000000..68275a790421d71a6d17f2c3a4058d5b505a7d84
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/3-ALTER-DATA-SOURCE.md
@@ -0,0 +1,114 @@
+---
+title: ALTER DATA SOURCE
+summary: ALTER DATA SOURCE
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER DATA SOURCE
+
+## Function
+
+**ALTER DATA SOURCE** modifies the attributes and content of the data source.
+
+The attributes include the name and owner. The content includes the type, version, and connection options.
+
+## Precautions
+
+- Only the initial user, system administrator, and owner have the permission to modify data sources.
+- To change the owner, the new owner must be the initial user or a system administrator.
+- If the **password** option is displayed, ensure that the **datasource.key.cipher** and **datasource.key.rand** files exist in the `$GAUSSHOME/bin` directory of each node. If the two files do not exist, use the **gs_guc** tool to generate them and use the **gs_ssh** tool to release them to the `$GAUSSHOME/bin` directory on each node.
+
+## Syntax
+
+```ebnf+diagram
+AlterDataSource ::= ALTER DATA SOURCE src_name
+    [TYPE  'type_str']
+    [VERSION  {'version_str' | NULL}]
+    [OPTIONS ( {[ ADD | SET | DROP ] optname ['optvalue']} [, ...] )];
+```
+
+```ebnf+diagram
+AlterDataSource ::= ALTER DATA SOURCE src_name RENAME TO src_new_name;
+```
+
+```ebnf+diagram
+AlterDataSource ::= ALTER DATA SOURCE src_name OWNER TO new_owner;
+```
+
+## Parameter Description
+
+- **src_name**
+
+  Specifies the data source name to be modified.
+
+  Value range: a string. It must comply with the identifier naming convention.
+
+- **TYPE**
+
+  Changes the original **TYPE** value of the data source to the specified value.
+
+  Value range: an empty string or a non-empty string
+
+- **VERSION**
+
+  Changes the original **VERSION** value of the data source to the specified value.
+
+  Value range: an empty string, a non-empty string, or null
+
+- **OPTIONS**
+
+  Specifies the column to be added, modified, or deleted. The value of  **optname**  should be unique. Comply with the following rules to set this parameter:
+
+  To add a column, you can omit **ADD** and simply specify the column name, which cannot be an existing column name.
+
+  To modify a column, specify **SET** and an existing column name.
+
+  To delete a column, specify **DROP** and an existing column name. Do not set **optvalue**.
+
+- **src_new_name**
+
+  Specifies the new data source name.
+
+  Value range: a string. It must comply with the naming convention rule.
+
+- **new_user**
+
+  Specifies the new owner of an object.
+
+  Value range: a string. It must be a valid username.
+
+## Examples
+
+```sql
+-- Create an empty data source.
+mogdb=# CREATE DATA SOURCE ds_test1;
+
+-- Rename the data source.
+mogdb=# ALTER DATA SOURCE ds_test1 RENAME TO ds_test;
+
+-- Change the owner.
+mogdb=# CREATE USER user_test1 IDENTIFIED BY 'Gs@123456';
+mogdb=# ALTER USER user_test1 WITH SYSADMIN;
+mogdb=# ALTER DATA SOURCE ds_test OWNER TO user_test1;
+
+-- Modify TYPE and VERSION.
+mogdb=# ALTER DATA SOURCE ds_test TYPE 'MPPDB_TYPE' VERSION 'XXX';
+
+-- Add a column.
+mogdb=# ALTER DATA SOURCE ds_test OPTIONS (add dsn 'gaussdb', username 'test_user');
+
+-- Modify a column.
+mogdb=# ALTER DATA SOURCE ds_test OPTIONS (set dsn 'unknown');
+
+-- Delete a column.
+mogdb=# ALTER DATA SOURCE ds_test OPTIONS (drop username);
+
+-- Delete the data source and user objects.
+mogdb=# DROP DATA SOURCE ds_test;
+mogdb=# DROP USER user_test1;
+```
+
+## Helpful Links
+
+[CREATE DATA SOURCE](45-CREATE-DATA-SOURCE)  and  [DROP DATA SOURCE](79-DROP-DATA-SOURCE)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/30-ALTER-USER-MAPPING.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/30-ALTER-USER-MAPPING.md
new file mode 100644
index 0000000000000000000000000000000000000000..f6f2ee6a6fabedb24ebadfea71c484ca3c8fafbc
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/30-ALTER-USER-MAPPING.md
@@ -0,0 +1,76 @@
+---
+title: ALTER USER MAPPING
+summary: ALTER USER MAPPING
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER USER MAPPING
+
+## Function
+
+**ALTER USER MAPPING** changes the definition of a user mapping.
+
+## Precautions
+
+If the  **password**  option is displayed, ensure that the  **usermapping.key.cipher**  and  **usermapping.key.rand**  files exist in the  `$GAUSSHOME/bin` directory of each node in MogDB. If the two files do not exist, use the  **gs_guc**  tool to generate them and use the  **gs_ssh**  tool to release them to the  `$GAUSSHOME/bin`  directory on each node.
+
+## Syntax
+
+```ebnf+diagram
+AlterUserMapping ::= ALTER USER MAPPING FOR { user_name | USER | CURRENT_USER | PUBLIC }
+    SERVER server_name
+    OPTIONS ( [ ADD | SET | DROP ] option ['value'] [, ... ] )
+```
+
+In **OPTIONS**, **ADD**, **SET**, and **DROP** are operations to be performed. If these operations are not specified, **ADD** operations will be performed by default. **option** and **value** are the parameters and values of the corresponding operation.
+
+## Parameter Description
+
+- **user_name**
+
+  Specifies user name of the mapping.
+
+  CURRENT_USER and USER match the name of the current user. PUBLIC is used to match all current and future user names in the system.
+
+- **server_name**
+
+  Specifies name of the server to which the user is mapped.
+
+- **OPTIONS**
+
+  Changes an option for the user mapping. The new option overwrites any previously specified option. **ADD**, **SET**, and **DROP** are operations to be performed. If the operation is not set explicitly, **ADD** is used. The option name must be unique and will be validated with the foreign data wrapper of the server.
+
+  - Options supported by **oracle_fdw** are as follows:
+
+    - **user**
+
+        Oracle server user name.
+
+    - **password**
+
+        Password of the Oracle user.
+
+  - Options supported by **mysql_fdw** are as follows:
+
+    - **username**
+
+        User name of the MySQL server or MariaDB.
+
+    - **password**
+
+        User password of the MySQL server or MariaDB.
+
+  - Options supported by **postgres_fdw** are as follows:
+
+    - **user**
+
+        User name of the remote MogDB database.
+
+    - **password**
+
+        User password of the remote MogDB database.
+
+## Helpful Links
+
+[CREATE USER MAPPING](69-CREATE-USER-MAPPING)，[DROP USER MAPPING](102-DROP-USER-MAPPING)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/31-ALTER-VIEW.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/31-ALTER-VIEW.md
new file mode 100644
index 0000000000000000000000000000000000000000..5b52c1a77b4d60ef158051ef8952094ed38488e2
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/31-ALTER-VIEW.md
@@ -0,0 +1,134 @@
+---
+title: ALTER VIEW
+summary: ALTER VIEW
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER VIEW
+
+## Function
+
+**ALTER VIEW** modifies all auxiliary attributes of a view. (To modify the query definition of a view, use **CREATE OR REPLACE VIEW**.)
+
+## Precautions
+
+Only the view owner or a user granted with the ALTER permission can run the **ALTER VIEW** command. The system administrator has this permission by default. The following is permission constraints depending on attributes to be modified:
+
+- To modify the schema of a view, you must be the owner of the view or system administrator and have the CREATE permission on the new schema.
+- To modify the owner of a view, you must be the owner of the view or system administrator and a member of the new owner role, with the CREATE permission on the schema of the view.
+
+## Syntax
+
+- Set the default value of a view column.
+
+  ```ebnf+diagram
+  AlterView ::= ALTER VIEW [ IF EXISTS ] view_name
+      ALTER [ COLUMN ] column_name SET DEFAULT expression;
+  ```
+
+- Remove the default value of a view column.
+
+  ```ebnf+diagram
+  AlterView ::= ALTER VIEW [ IF EXISTS ] view_name
+      ALTER [ COLUMN ] column_name DROP DEFAULT;
+  ```
+
+- Change the owner of a view.
+
+  ```ebnf+diagram
+  AlterView ::= ALTER VIEW [ IF EXISTS ] view_name
+      OWNER TO new_owner;
+  ```
+
+- Rename a view.
+
+  ```ebnf+diagram
+  AlterView ::= ALTER VIEW [ IF EXISTS ] view_name
+      RENAME TO new_name;
+  ```
+
+- Set the schema of a view.
+
+  ```ebnf+diagram
+  AlterView ::= ALTER VIEW [ IF EXISTS ] view_name
+      SET SCHEMA new_schema;
+  ```
+
+- Set the options of a view.
+
+  ```ebnf+diagram
+  AlterView ::= ALTER VIEW [ IF EXISTS ] view_name
+      SET ( { view_option_name [ = view_option_value ] } [, ... ] );
+  ```
+
+- Reset the options of a view.
+
+  ```ebnf+diagram
+  AlterView ::= ALTER VIEW [ IF EXISTS ] view_name
+      RESET ( view_option_name [, ... ] );
+  ```
+
+## Parameter Description
+
+- **IF EXISTS**
+
+  If this option is used, no error is generated when the view does not exist, and only a message is displayed.
+
+- **view_name**
+
+  Specifies the view name, which can be schema-qualified.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **column_name**
+
+  Specifies an optional list of names to be used for columns of the view. If not given, the column names are deduced from the query.
+
+  Value range: a string. It must comply with the naming convention rule.
+
+- **SET/DROP DEFAULT**
+
+  Sets or deletes the default value of a column. This parameter does not take effect.
+
+- **new_owner**
+
+  Specifies the new owner of a view.
+
+- **new_name**
+
+  Specifies the new view name.
+
+- **new_schema**
+
+  Specifies the new schema of the view.
+
+- **view_option_name [ = view_option_value ]**
+
+  Specifies an optional parameter for a view.
+
+  Currently, **view_option_name** supports only the **security_barrier** parameter. This parameter is used when the view attempts to provide row-level security.
+
+  Value range: Boolean type, **TRUE**, and **FALSE**.
+
+## Examples
+
+```sql
+-- Create a view consisting of rows with c_customer_sk less than 150.
+mogdb=# CREATE VIEW tpcds.customer_details_view_v1 AS
+    SELECT * FROM tpcds.customer
+    WHERE c_customer_sk < 150;
+
+-- Rename a view.
+mogdb=# ALTER VIEW tpcds.customer_details_view_v1 RENAME TO customer_details_view_v2;
+
+-- Change the schema of a view.
+mogdb=# ALTER VIEW tpcds.customer_details_view_v2 SET schema public;
+
+-- Delete a view.
+mogdb=# DROP VIEW public.customer_details_view_v2;
+```
+
+## Helpful Links
+
+[CREATE VIEW](70-CREATE-VIEW)  and  [DROP VIEW](103-DROP-VIEW)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/32-ANALYZE-ANALYSE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/32-ANALYZE-ANALYSE.md
new file mode 100644
index 0000000000000000000000000000000000000000..089483ee8f61b5ffcc22c7d195898d9f22d9553c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/32-ANALYZE-ANALYSE.md
@@ -0,0 +1,192 @@
+---
+title: ANALYZE | ANALYSE
+summary: ANALYZE | ANALYSE
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ANALYZE | ANALYSE
+
+## Function
+
+**ANALYZE** collects statistics about ordinary tables in a database, and stores the results in the **PG_STATISTIC** system catalog. The execution plan generator uses these statistics to determine which one is the most effective execution plan.
+
+If no parameter is specified, **ANALYZE** analyzes each table and partitioned table in the current database. You can also specify the **table_name**, **column**, and **partition_name** parameters to restrict the analysis to a specific table, column, or partitioned table.
+
+**ANALYZE | ANALYSE VERIFY** is used to check whether data files of common tables (row-store and column-store tables) in a database are damaged.
+
+## Precautions
+
+- Non-temporary tables cannot be analyzed in an anonymous block, transaction block, function, or stored procedure. Temporary tables in a stored procedure can be analyzed but their statistics updates cannot be rolled back.
+- The **ANALYZE VERIFY** operation is used to detect abnormal scenarios. The **RELEASE** version is required. In the **ANALYZE VERIFY** scenario, remote read is not triggered. Therefore, the remote read parameter does not take effect. If the system detects that a page is damaged due to an error in a key system table, the system directly reports an error and does not continue the detection.
+- With no table specified, **ANALYZE** processes all the tables that the current user has permission to analyze in the current database. With tables specified, **ANALYZE** processes only the specified tables.
+- To perform ANALYZE operation to a table, you must be a table owner or a user granted the VACUUM permission on the table. By default, the system administrator has this permission. However, database owners are allowed to **ANALYZE** all tables in their databases, except shared catalogs. (The restriction for shared catalogs means that a true database-wide **ANALYZE** can only be executed by the system administrator). **ANALYZE** skips tables on which users do not have permissions.
+
+## Syntax
+
+- Collect statistics information about a table.
+
+  ```ebnf+diagram
+  AnalyzeAnalyse ::= { ANALYZE | ANALYSE } [ VERBOSE ]
+      [ table_name [ ( column_name [, ...] ) ] ];
+  ```
+
+- Collect statistics about a partitioned table.
+
+  ```ebnf+diagram
+  AnalyzeAnalyse ::= { ANALYZE | ANALYSE } [ VERBOSE ]
+      [ table_name [ ( column_name [, ...] ) ] ]
+      PARTITION ( patrition_name ) ;
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** An ordinary partitioned table supports the syntax but not the function of collecting statistics about specified partitions.
+
+- Collect statistics about multiple columns.
+
+  ```ebnf+diagram
+  AnalyzeAnalyse ::= {ANALYZE | ANALYSE} [ VERBOSE ]
+      table_name (( column_1_name, column_2_name [, ...] ));
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > - When collecting statistics about multiple columns, set the GUC parameter **default_statistics_target** to a negative value to sample data in percentage.
+  > - The statistics about a maximum of 32 columns can be collected at a time.
+  > - You are not allowed to collect statistics about multiple columns in system catalogs.
+
+- Check the data files in the current database.
+
+  ```ebnf+diagram
+  AnalyzeAnalyse ::= {ANALYZE | ANALYSE} VERIFY {FAST|COMPLETE};
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > - In fast mode, DML operations need to be performed on the tables to be verified concurrently. As a result, an error is reported during the verification. In the current fast mode, data is directly read from the disk. When other threads modify files concurrently, the obtained data is incorrect. Therefore, you are advised to perform the verification offline.
+  > - You can perform operations on the entire database. Because a large number of tables are involved, you are advised to save the result **gsql -d database -p port -f "verify.sql"&gt; verify_warning.txt 2&gt;&1** in redirection mode.
+  > - NOTICE is used to check only tables that are visible to external systems. The detection of internal tables is included in the external tables on which NOTICE depends and is not displayed externally.
+  > - This statement can be executed with error tolerance. The **Assert** of the debug version may cause the core to fail to execute commands. Therefore, you are advised to perform the operations in release mode.
+  > - If a key system table is damaged during a full database operation, an error is reported and the operation stops.
+
+- Check data files of tables and indexes.
+
+  ```ebnf+diagram
+  AnalyzeAnalyse ::= {ANALYZE | ANALYSE} VERIFY {FAST|COMPLETE} table_name|index_name [CASCADE];
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > - Operations on ordinary tables and index tables are supported, but **CASCADE** operations on indexes of index tables are not supported. The **CASCADE** mode is used to process all index tables of the primary table. When the index tables are checked separately, the **CASCADE** mode is not required.
+  > - When the primary table is checked, the internal tables of the primary table, such as the toast table and cudesc table, are also checked.
+  > - When the system displays a message indicating that the index table is damaged, you are advised to run the **reindex** command to recreate the index.
+
+- Check the data files of the table partition.
+
+  ```ebnf+diagram
+  AnalyzeAnalyse ::= {ANALYZE | ANALYSE} VERIFY {FAST|COMPLETE} table_name PARTITION {(patrition_name)}[CASCADE];
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** You can check a single partition of a table, but cannot perform the **CASCADE** operation on the indexes of an index table.
+
+## Parameter Description
+
+- **VERBOSE**
+
+  Enables the display of progress messages.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** If **VERBOSE** is specified, **ANALYZE** displays the progress information, indicating the table that is being processed. Statistics about tables are also displayed.
+
+- **table_name**
+
+  Specifies the name (possibly schema-qualified) of a specific table to analyze. If omitted, all regular tables (but not foreign tables) in the current database are analyzed.
+
+  Currently, you can use **ANALYZE** to collect statistics only from row-store tables and column-store tables.
+
+  Value range: an existing table name
+
+- **column_name**, column_1_name, column_2_name
+
+  Specifies the name of a specific column to analyze. All columns are analyzed by default.
+
+  Value range: an existing column name
+
+- **partition_name**
+
+  Assumes the table is a partitioned table. You can specify **partition_name** following the keyword **PARTITION** to analyze the statistics of this table. Currently, **ANALYZE** can be performed on partitioned tables, but statistics of specified partitions cannot be analyzed.
+
+  Value range: a partition name of a table
+
+- **index_name**
+
+  Specifies the name of the specific index table to be analyzed (possibly schema-qualified).
+
+  Value range: an existing table name
+
+- **FAST|COMPLETE**
+
+  For a row-store table, the **FAST** mode verifies the CRC and page header of the row-store table. If the verification fails, an alarm is generated. In **COMPLETE** mode, the pointer and tuple of the row-store table are parsed and verified. For a column-store table, the **FAST** mode verifies the CRC and magic of the column-store table. If the verification fails, an alarm is generated. In **COMPLETE** mode, the CU of the column-store table is parsed and verified.
+
+- **CASCADE**
+
+  In **CASCADE** mode, all indexes of the current table are verified.
+
+## Examples
+
+- Create a table.
+
+```sql
+mogdb=# CREATE TABLE customer_info
+(
+WR_RETURNED_DATE_SK       INTEGER                       ,
+WR_RETURNED_TIME_SK       INTEGER                       ,
+WR_ITEM_SK                INTEGER               NOT NULL,
+WR_REFUNDED_CUSTOMER_SK   INTEGER
+)
+;
+```
+
+- Create a partitioned table.
+
+```sql
+mogdb=# CREATE TABLE customer_par
+(
+WR_RETURNED_DATE_SK       INTEGER                       ,
+WR_RETURNED_TIME_SK       INTEGER                       ,
+WR_ITEM_SK                INTEGER               NOT NULL,
+WR_REFUNDED_CUSTOMER_SK   INTEGER
+)
+PARTITION BY RANGE(WR_RETURNED_DATE_SK)
+(
+PARTITION P1 VALUES LESS THAN(2452275),
+PARTITION P2 VALUES LESS THAN(2452640),
+PARTITION P3 VALUES LESS THAN(2453000),
+PARTITION P4 VALUES LESS THAN(MAXVALUE)
+)
+ENABLE ROW MOVEMENT;
+```
+
+- Run **ANALYZE** to update statistics.
+
+```sql
+mogdb=# ANALYZE customer_info;
+mogdb=# ANALYZE customer_par;
+```
+
+- Run the **ANALYZE VERBOSE** statement to update statistics and display table information.
+
+```sql
+mogdb=# ANALYZE VERBOSE customer_info;
+INFO:  analyzing "cstore.pg_delta_3394584009"(cn_5002 pid=53078)
+INFO:  analyzing "public.customer_info"(cn_5002 pid=53078)
+INFO:  analyzing "public.customer_info" inheritance tree(cn_5002 pid=53078)
+ANALYZE
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** If any environment-related fault occurs, check the logs of the primary node of the database.
+
+- Delete the table.
+
+```sql
+mogdb=# DROP TABLE customer_info;
+mogdb=# DROP TABLE customer_par;
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/33-BEGIN.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/33-BEGIN.md
new file mode 100644
index 0000000000000000000000000000000000000000..f4afdb9f82561ed853edc471f02f39f2707a19ab
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/33-BEGIN.md
@@ -0,0 +1,62 @@
+---
+title: BEGIN
+summary: BEGIN
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# BEGIN
+
+## Function
+
+**BEGIN** may be used to initiate an anonymous block or a single transaction. This section describes the syntax of **BEGIN** used to initiate an anonymous block. For details about the **BEGIN** syntax that initiates transactions, see **START TRANSACTION**.
+
+An anonymous block is a structure that can dynamically create and execute stored procedure code instead of permanently storing code as a database object in the database.
+
+## Precautions
+
+None
+
+## Syntax
+
+- Enable an anonymous block.
+
+  ```ebnf+diagram
+  Begin ::= [DECLARE [declare_statements]]
+  BEGIN
+  execution_statements
+  END;
+
+  ```
+
+- Start a transaction.
+
+  ```ebnf+diagram
+  Begin ::= BEGIN [ WORK | TRANSACTION ]
+    [
+      {
+         ISOLATION LEVEL { READ COMMITTED | SERIALIZABLE | REPEATABLE READ }
+         | { READ WRITE | READ ONLY }
+        } [, ...]
+    ];
+  ```
+
+## Parameter Description
+
+- **declare_statements**
+
+  Declares a variable, including its name and type, for example, **sales_cnt int**.
+
+- **execution_statements**
+
+  Specifies the statement to be executed in an anonymous block.
+
+  Value range: DML operations (such as select, insert, delete, and update) or registered functions in the system catalog.
+
+## Examples
+
+None
+
+## Helpful Links
+
+[START TRANSACTION](134-START-TRANSACTION)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/34-CALL.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/34-CALL.md
new file mode 100644
index 0000000000000000000000000000000000000000..edf4bbf446207755be349c078b6a6c5983f7f111
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/34-CALL.md
@@ -0,0 +1,84 @@
+---
+title: CALL
+summary: CALL
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CALL
+
+## Function
+
+**CALL** can be used to call defined functions and stored procedures.
+
+## Precautions
+
+None
+
+## Syntax
+
+```ebnf+diagram
+Call ::= CALL [schema'.'|package'.'] {func_name| procedure_name} ( param_expr );
+```
+
+## Parameter Description
+
+- **schema**
+
+  Specifies the name of the schema where a function or stored procedure is located.
+
+- **package**
+
+    Specifies the name of the package where a function or stored procedure is located.
+
+- **func_name**
+
+  Specifies the name of the function or stored procedure to be called.
+
+  Value range: an existing function name
+
+- **param_expr**
+
+  Specifies a list of parameters in the function. Use := or => to separate a parameter name and its value. This method allows parameters to be placed in any order. If only parameter values are in the list, the value order must be the same as that defined in the function or stored procedure.
+
+  Value range: an existing function parameter name or stored procedure parameter name
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  > The parameters include input parameters (whose name and type are separated by IN) and output parameters (whose name and type are separated by OUT). When you run the **CALL** statement to call a function or stored procedure, the parameter list must contain an output parameter for non-overloaded functions. You can set the output parameter to a variable or any constant. For details, see **Examples**. For an overloaded package function, the parameter list can have no output parameter, but the function may not be found. If an output parameter is contained, it must be a constant.
+
+## Examples
+
+```sql
+-- Create the func_add_sql function, calculate the sum of two integers, and return the result.
+mogdb=# CREATE FUNCTION func_add_sql(num1 integer, num2 integer) RETURN integer
+AS
+BEGIN
+RETURN num1 + num2;
+END;
+/
+
+-- Transfer by parameter value.
+mogdb=# CALL func_add_sql(1, 3);
+
+-- Transfer by naming tag method.
+mogdb=# CALL func_add_sql(num1 => 1,num2 => 3);
+mogdb=# CALL func_add_sql(num2 := 2, num1 := 3);
+
+-- Delete the function.
+mogdb=# DROP FUNCTION func_add_sql;
+
+-- Create a function with output parameters.
+mogdb=# CREATE FUNCTION func_increment_sql(num1 IN integer, num2 IN integer, res OUT integer)
+RETURN integer
+AS
+BEGIN
+res := num1 + num2;
+END;
+/
+
+-- Transfer a constant as an output parameter.
+mogdb=# CALL func_increment_sql(1,2,1);
+
+-- Delete the function.
+mogdb=# DROP FUNCTION func_increment_sql;
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/35-CHECKPOINT.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/35-CHECKPOINT.md
new file mode 100644
index 0000000000000000000000000000000000000000..7516d5f3745729dbb31caff2fdebac2154f2b774
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/35-CHECKPOINT.md
@@ -0,0 +1,36 @@
+---
+title: CHECKPOINT
+summary: CHECKPOINT
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CHECKPOINT
+
+## Function
+
+A checkpoint is a point in the transaction log sequence at which all data files have been updated to reflect the information in the log. All data files will be flushed to a disk.
+
+**CHECKPOINT** forces a transaction log checkpoint. By default, WALs periodically specify checkpoints in a transaction log. You may use **gs_guc** to specify run-time parameters **checkpoint_segments** and **checkpoint_timeout** to adjust the atomized checkpoint intervals.
+
+## Precautions
+
+- Only a system administrator has the permission to call **CHECKPOINT**.
+- **CHECKPOINT** forces an immediate checkpoint when the related command is issued, without waiting for a regular checkpoint scheduled by the system.
+
+## Syntax
+
+```ebnf+diagram
+Checkpoint ::= CHECKPOINT;
+```
+
+## Parameter Description
+
+None
+
+## Examples
+
+```sql
+-- Set a checkpoint.
+mogdb=# CHECKPOINT;
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/35.1-CLEAN-CONNECTION.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/35.1-CLEAN-CONNECTION.md
new file mode 100644
index 0000000000000000000000000000000000000000..ff72e5769da09e5890350bc371e155171a612efb
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/35.1-CLEAN-CONNECTION.md
@@ -0,0 +1,76 @@
+---
+title: CLEAN CONNECTION
+summary: CLEAN CONNECTION
+author: Zhang Cuiping
+date: 2021-11-01
+---
+
+# CLEAN CONNECTION
+
+## Function
+
+**CLEAN CONNECTION** can be used to clean database connections. It is allowed to clean related connections of specified users with specified database.
+
+## Precautions
+
+1. MogDB does not support specifying nodes but only TO ALL.
+
+2. In the non-force mode, this function does not clean connections. In the force mode, this function can clean normal connections in use.
+
+## Syntax
+
+```ebnf+diagram
+CleanConnection ::= CLEAN CONNECTION
+      TO { COORDINATOR ( nodename [, ... ] ) | NODE ( nodename [, ... ] )| ALL [ CHECK ] [ FORCE ] }
+      [ FOR DATABASE dbname ]
+      [ TO USER username ];
+```
+
+## Parameter Description
+
+- **CHECK**
+
+  Checks whether a database is accessed by other sessions before cleaning connections. This parameter can be set only when the node list is TO ALL. This parameter is used for connection check before a database is deleted. If detecting a connection, it will report an error and stop deleting a database.
+
+- **FORCE**
+
+  Specifies that all threads related to specified databases and users will receive SIGTERM signals and are forcibly disabled. This parameter can be set only when the node list is TO ALL.
+
+- **COORDINATOR ( nodename [, … ] ) | NODE ( nodename [, … ] ) | ALL**
+
+  Deletes connections with a specified node. There are three scenarios:
+
+  - Deletes connection with a specified CN. MogDB does not support this scenario.
+  - Deletes connection with a specified DN. MogDB does not support this scenario.
+  - Deletes connections with all nodes (TO ALL). MogDB supports only this scenario.
+
+- **dbname**
+
+  Deletes connections with a specified database. If not specified, connections with all databases will be deleted.
+
+  Value range: an existing database name
+
+- **username**
+
+  Deletes connections with a specified user. If not specified, connections with all users will be deleted.
+
+  Value range: an existing user
+
+## Examples
+
+```sql
+--Create user jack.
+CREATE USER jack PASSWORD 'Bigdata123@';
+
+--Delete all connections of user jack with the template1 database.
+CLEAN CONNECTION TO ALL FOR DATABASE template1 TO USER jack;
+
+--Delete all connections with user jack.
+CLEAN CONNECTION TO ALL TO USER jack;
+
+--Delete all connections with the gaussdb database.
+CLEAN CONNECTION TO ALL FORCE FOR DATABASE gaussdb;
+
+--Delete user jack.
+DROP USER jack;
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/36-CLOSE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/36-CLOSE.md
new file mode 100644
index 0000000000000000000000000000000000000000..4a0fd0b34ee38ac7792fd8a12ceddce0eb72a283
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/36-CLOSE.md
@@ -0,0 +1,45 @@
+---
+title: CLOSE
+summary: CLOSE
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CLOSE
+
+## Function
+
+**CLOSE** frees the resources associated with an open cursor.
+
+## Precautions
+
+- After a cursor is closed, no subsequent operations are allowed on it.
+- A cursor should be closed when it is no longer needed.
+- Every non-holdable open cursor is implicitly closed when a transaction is terminated by **COMMIT** or **ROLLBACK**.
+- A holdable cursor is implicitly closed if the transaction that created it aborts by **ROLLBACK**.
+- If the cursor creation transaction is successfully committed, the holdable cursor remains open until an explicit **CLOSE** operation is executed, or the client disconnects.
+- openGauss does not have an explicit **OPEN** cursor statement. A cursor is considered open when it is declared. You can view all available cursors by querying the **pg_cursors** system view.
+
+## Syntax
+
+```ebnf+diagram
+Close ::= CLOSE { cursor_name | ALL } ;
+```
+
+## Parameter Description
+
+- **cursor_name**
+
+  Specifies the name of a cursor to be closed.
+
+- **ALL**
+
+  Closes all open cursors.
+
+## Examples
+
+See **Examples** in [FETCH](107-FETCH).
+
+## Helpful Links
+
+[FETCH](107-FETCH)，[MOVE](111-MOVE)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/37-CLUSTER.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/37-CLUSTER.md
new file mode 100644
index 0000000000000000000000000000000000000000..0716fc03fa0e947864316547d626dc5132e45967
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/37-CLUSTER.md
@@ -0,0 +1,128 @@
+---
+title: CLUSTER
+summary: CLUSTER
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CLUSTER
+
+## Function
+
+**CLUSTER** is used to cluster a table based on an index.
+
+**CLUSTER** instructs MogDB to cluster the table specified by **table_name** based on the index specified by **index_name**. The index must have been defined by **table_name**.
+
+When a table is clustered, it is physically reordered based on the index information. Clustering is a one-time operation. When the table is subsequently updated, the changes are not clustered. That is, no attempt is made to store new or updated rows according to their index order.
+
+When a table is clustered, MogDB records which index the table was clustered by. The form **CLUSTER table_name** reclusters the table using the same index as before. You can also use the **CLUSTER** or **SET WITHOUT CLUSTER** form of **ALTER TABLE** to set the index to be used for future cluster operations, or to clear any previous settings.
+
+**CLUSTER** without any parameter reclusters all the previously-clustered tables in the current database that the calling user owns, or all such tables if called by an administrator.
+
+When a table is being clustered, an **ACCESS EXCLUSIVE** lock is acquired on it. This prevents any other database operations (both read and write) from being performed on the table until the **CLUSTER** is finished.
+
+## Precautions
+
+- Only row-store B-tree indexes support **CLUSTER**.
+
+- In the case where you are accessing single rows randomly within a table, the actual order of the data in the table is unimportant. However, if you tend to access some data more than others, and there is an index that groups them together, it is helpful by using **CLUSTER**. If you are requesting a range of indexed values from a table, or a single indexed value that has multiple rows that match, **CLUSTER** will help because once the index identifies the table page for the first row that matches, all other rows that match are probably already on the same table page, and so you save disk accesses and speed up the query.
+
+- When an index scan is used, a temporary copy of the table is created that contains the table data in the index order. Temporary copies of each index on the table are created as well. Therefore, you need free space on disk at least equal to the sum of the table size and the total index size.
+
+- Because **CLUSTER** remembers which indexes are clustered, one can cluster the tables manually the first time, then set up a time like **VACUUM** without any parameters, so that the desired tables are periodically reclustered.
+
+- Because the optimizer records statistics about the ordering of tables, it is advisable to run **ANALYZE** on the newly clustered table. Otherwise, the optimizer might make poor choices of query plans.
+
+- **CLUSTER** cannot be executed in transactions.
+- If the  **xc_maintenance_mode**  parameter is not enabled, the CLUSTER operation will skip all system catalogs.
+
+## Syntax
+
+- Cluster a table.
+
+  ```ebnf+diagram
+  Cluster ::= CLUSTER [ VERBOSE ] table_name [ USING index_name ];
+  ```
+
+- Cluster a partition.
+
+  ```ebnf+diagram
+  Cluster ::= CLUSTER [ VERBOSE ] table_name PARTITION ( partition_name ) [ USING index_name ];
+  ```
+
+- Recluster a table.
+
+  ```ebnf+diagram
+  Cluster ::= CLUSTER [ VERBOSE ];
+  ```
+
+## Parameter Description
+
+- **VERBOSE**
+
+  Enables the display of progress messages.
+
+- **table_name**
+
+  Specifies the table name.
+
+  Value range: an existing table name
+
+- **index_name**
+
+  Specifies the index name.
+
+  Value range: an existing index name
+
+- **partition_name**
+
+  Specifies the partition name.
+
+  Value range: an existing partition name
+
+## Examples
+
+```sql
+-- Create a partitioned table.
+mogdb=# CREATE TABLE tpcds.inventory_p1
+(
+    INV_DATE_SK               INTEGER               NOT NULL,
+    INV_ITEM_SK               INTEGER               NOT NULL,
+    INV_WAREHOUSE_SK          INTEGER               NOT NULL,
+    INV_QUANTITY_ON_HAND      INTEGER
+)
+PARTITION BY RANGE(INV_DATE_SK)
+(
+        PARTITION P1 VALUES LESS THAN(2451179),
+        PARTITION P2 VALUES LESS THAN(2451544),
+        PARTITION P3 VALUES LESS THAN(2451910),
+        PARTITION P4 VALUES LESS THAN(2452275),
+        PARTITION P5 VALUES LESS THAN(2452640),
+        PARTITION P6 VALUES LESS THAN(2453005),
+        PARTITION P7 VALUES LESS THAN(MAXVALUE)
+);
+
+-- Create an index named ds_inventory_p1_index1.
+mogdb=# CREATE INDEX ds_inventory_p1_index1 ON tpcds.inventory_p1 (INV_ITEM_SK) LOCAL;
+
+-- Cluster the tpcds.inventory_p1 table.
+mogdb=# CLUSTER tpcds.inventory_p1 USING ds_inventory_p1_index1;
+
+-- Cluster the p3 partition.
+mogdb=# CLUSTER tpcds.inventory_p1 PARTITION (p3) USING ds_inventory_p1_index1;
+
+-- Cluster the tables that can be clustered in the database.
+mogdb=# CLUSTER;
+
+-- Delete the index.
+mogdb=# DROP INDEX tpcds.ds_inventory_p1_index1;
+
+-- Delete the partitioned table.
+mogdb=# DROP TABLE tpcds.inventory_p1;
+```
+
+## Suggestions
+
+- cluster
+  - It is recommended that you run **ANALYZE** on a newly clustered table. Otherwise, the optimizer might make poor choices of query plans.
+  - **CLUSTER** cannot be executed in transactions.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/38-COMMENT.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/38-COMMENT.md
new file mode 100644
index 0000000000000000000000000000000000000000..60b6559072a5d96ac4482efce265451853b73bb9
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/38-COMMENT.md
@@ -0,0 +1,159 @@
+---
+title: COMMENT
+summary: COMMENT
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# COMMENT
+
+## Function
+
+**COMMENT** defines or changes the comment of an object.
+
+## Precautions
+
+- Each object stores only one comment. Therefore, you need to modify a comment and issue a new **COMMENT** command to the same object. To delete the comment, write **NULL** at the position of the text string. When an object is deleted, the comment is automatically deleted.
+- Currently, there is no security protection for viewing comments. Any user connected to a database can view all the comments for objects in the database. For shared objects such as databases, roles, and tablespaces, comments are stored globally so any user connected to any database in the cluster can see all the comments for shared objects. Therefore, do not put security-critical information in comments.
+- To comment objects, you must be an object owner or user granted the COMMENT permission. The system administrator has this permission by default.
+- Roles do not have owners, so the rule for **COMMENT ON ROLE** is that you must be an administrator to comment on an administrator role, or have the **CREATEROLE** permission to comment on non-administrator roles. A system administrator can comment on all objects.
+
+## Syntax
+
+```ebnf+diagram
+Comment ::= COMMENT ON
+{
+  AGGREGATE agg_name (agg_type [, ...] ) |
+  CAST (source_type AS target_type) |
+  COLLATION object_name |
+  COLUMN { table_name'.'column_name | view_name'.'column_name } |
+  CONSTRAINT constraint_name ON table_name |
+  CONVERSION object_name |
+  DATABASE object_name |
+  DOMAIN object_name |
+  EXTENSION object_name |
+  FOREIGN DATA WRAPPER object_name |
+  FOREIGN TABLE object_name |
+  FUNCTION function_name ( [ {[ argmode ] [ argname ] argtype} [, ...] ] ) |
+  INDEX object_name |
+  LARGE OBJECT large_object_oid |
+  OPERATOR operator_name (left_type, right_type) |
+  OPERATOR CLASS object_name USING index_method |
+  OPERATOR FAMILY object_name USING index_method |
+  [ PROCEDURAL ] LANGUAGE object_name |
+  ROLE object_name |
+  SCHEMA object_name |
+  SERVER object_name |
+  TABLE object_name |
+  TABLESPACE object_name |
+  TEXT SEARCH CONFIGURATION object_name |
+  TEXT SEARCH DICTIONARY object_name |
+  TEXT SEARCH PARSER object_name |
+  TEXT SEARCH TEMPLATE object_name |
+  TYPE object_name |
+  VIEW object_name |
+  TRIGGER trigger_name ON table_name
+}
+   IS 'text';
+```
+
+## Parameter Description
+
+- **agg_name**
+
+  Specifies the new name of an aggregate function.
+
+- **agg_type**
+
+  Specifies the data type of the aggregate function parameters.
+
+- **source_type**
+
+  Specifies the source data type of the cast.
+
+- **target_type**
+
+  Specifies the target data type of the cast.
+
+- **object_name**
+
+  Specifies the name of an object.
+
+- **table_name.column_name**
+
+  **view_name.column_name**
+
+  Specifies the column whose comment is defined or modified. You can add the table name or view name as the prefix.
+
+- **constraint_name**
+
+  Specifies the table constraint whose comment is defined or modified.
+
+- **table_name**
+
+  Specifies the name of a table.
+
+- **function_name**
+
+  Specifies the function whose comment is defined or modified.
+
+- **argmode,argname,argtype**
+
+  Specifies the schema, name, and type of the function parameters.
+
+- **large_object_oid**
+
+  Specifies the OID of the large object whose comment is defined or modified.
+
+- **operator_name**
+
+  Specifies the name of the operator.
+
+- **left_type,right_type**
+
+  Specifies the data type of the operator parameters (optionally schema-qualified). If the prefix or suffix operator does not exist, the **NONE** option can be added.
+
+- **trigger_name**
+
+  Specifies the trigger name.
+
+- **text**
+
+  Specifies the comment content.
+
+## Examples
+
+```sql
+mogdb=# CREATE TABLE tpcds.customer_demographics_t2
+(
+    CD_DEMO_SK                INTEGER               NOT NULL,
+    CD_GENDER                 CHAR(1)                       ,
+    CD_MARITAL_STATUS         CHAR(1)                       ,
+    CD_EDUCATION_STATUS       CHAR(20)                      ,
+    CD_PURCHASE_ESTIMATE      INTEGER                       ,
+    CD_CREDIT_RATING          CHAR(10)                      ,
+    CD_DEP_COUNT              INTEGER                       ,
+    CD_DEP_EMPLOYED_COUNT     INTEGER                       ,
+    CD_DEP_COLLEGE_COUNT      INTEGER
+)
+WITH (ORIENTATION = COLUMN,COMPRESSION=MIDDLE)
+;
+
+-- Comment out the tpcds.customer_demographics_t2.cd_demo_sk column.
+mogdb=# COMMENT ON COLUMN tpcds.customer_demographics_t2.cd_demo_sk IS 'Primary key of customer demographics table.';
+
+-- Create a view consisting of rows with c_customer_sk less than 150.
+mogdb=# CREATE VIEW tpcds.customer_details_view_v2 AS
+    SELECT *
+    FROM tpcds.customer
+    WHERE c_customer_sk < 150;
+
+-- Comment out the tpcds.customer_details_view_v2 view.
+mogdb=# COMMENT ON VIEW tpcds.customer_details_view_v2 IS 'View of customer detail';
+
+-- Delete the view.
+mogdb=# DROP VIEW tpcds.customer_details_view_v2;
+
+-- Delete the tpcds.customer_demographics_t2 table.
+mogdb=# DROP TABLE tpcds.customer_demographics_t2;
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/39-COMMIT-END.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/39-COMMIT-END.md
new file mode 100644
index 0000000000000000000000000000000000000000..d7b7acec80289df5a0117c6589348062d33ea8d7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/39-COMMIT-END.md
@@ -0,0 +1,72 @@
+---
+title: COMMIT | END
+summary: COMMIT | END
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# COMMIT | END
+
+## Function
+
+**COMMIT** or **END** commits all operations of a transaction.
+
+## Precautions
+
+Only the creator of a transaction or a system administrator can run the **COMMIT** command. The creation and commit operations must be in different sessions.
+
+## Syntax
+
+```ebnf+diagram
+CommitEnd ::= { COMMIT | END } [ WORK | TRANSACTION ] ;
+```
+
+## Parameter Description
+
+- **COMMIT | END**
+
+  Commits the current transaction and makes all changes made by the transaction become visible to others.
+
+- **WORK | TRANSACTION**
+
+  Specifies an optional keyword, which has no effect except increasing readability.
+
+## Examples
+
+```sql
+-- Create a table.
+mogdb=# CREATE TABLE tpcds.customer_demographics_t2
+(
+    CD_DEMO_SK                INTEGER               NOT NULL,
+    CD_GENDER                 CHAR(1)                       ,
+    CD_MARITAL_STATUS         CHAR(1)                       ,
+    CD_EDUCATION_STATUS       CHAR(20)                      ,
+    CD_PURCHASE_ESTIMATE      INTEGER                       ,
+    CD_CREDIT_RATING          CHAR(10)                      ,
+    CD_DEP_COUNT              INTEGER                       ,
+    CD_DEP_EMPLOYED_COUNT     INTEGER                       ,
+    CD_DEP_COLLEGE_COUNT      INTEGER
+)
+WITH (ORIENTATION = COLUMN,COMPRESSION=MIDDLE)
+;
+
+-- Start a transaction.
+mogdb=# START TRANSACTION;
+
+-- Insert data.
+mogdb=# INSERT INTO tpcds.customer_demographics_t2 VALUES(1,'M', 'U', 'DOCTOR DEGREE', 1200, 'GOOD', 1, 0, 0);
+mogdb=# INSERT INTO tpcds.customer_demographics_t2 VALUES(2,'F', 'U', 'MASTER DEGREE', 300, 'BAD', 1, 0, 0);
+
+-- Commit the transaction to make all changes permanent.
+mogdb=# COMMIT;
+
+-- Query data.
+mogdb=# SELECT * FROM tpcds.customer_demographics_t2;
+
+-- Delete the tpcds.customer_demographics_t2 table.
+mogdb=# DROP TABLE tpcds.customer_demographics_t2;
+```
+
+## Helpful Links
+
+[ROLLBACK](121-ROLLBACK)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/4-ALTER-DEFAULT-PRIVILEGES.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/4-ALTER-DEFAULT-PRIVILEGES.md
new file mode 100644
index 0000000000000000000000000000000000000000..2c1e2a0f5954a4f9d5665aadefda0fae0e37abd7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/4-ALTER-DEFAULT-PRIVILEGES.md
@@ -0,0 +1,170 @@
+---
+title: ALTER DEFAULT PRIVILEGES
+summary: ALTER DEFAULT PRIVILEGES
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER DEFAULT PRIVILEGES
+
+## Function
+
+**ALTER DEFAULT PRIVILEGES** allows you to set the permissions that will be applied to objects created in the future. (It does not affect permissions granted to existing objects.)
+
+## Precautions
+
+Currently, you can change only the permissions for tables (including views), sequences, functions, types, CMKs of encrypted databases, and CEKs.
+
+## Syntax
+
+```ebnf+diagram
+AlterDafaultPrivileges ::= ALTER DEFAULT PRIVILEGES
+    [ FOR { ROLE | USER } target_role [, ...] ]
+    [ IN SCHEMA schema_name [, ...] ]
+    abbreviated_grant_or_revoke;
+```
+
+- **abbreviated_grant_or_revoke** grants or revokes permissions on some objects.
+
+  ```ebnf+diagram
+  abbreviated_grant_or_revoke ::= grant_on_tables_clause
+        | grant_on_sequences_clause
+        | grant_on_functions_clause
+        | grant_on_types_clause
+        | grant_on_client_master_keys_clause
+        | grant_on_column_encryption_keys_clause
+        | revoke_on_tables_clause
+        | revoke_on_sequences_clause
+        | revoke_on_functions_clause
+        | revoke_on_types_clause
+        | revoke_on_client_master_keys_clause
+        | revoke_on_column_encryption_keys_clause
+  ```
+
+- **grant_on_tables_clause** grants permissions on tables.
+
+  ```ebnf+diagram
+  grant_on_tables_clause ::= GRANT { { SELECT | INSERT | UPDATE | DELETE | TRUNCATE | REFERENCES | ALTER | DROP | COMMENT | INDEX | VACUUM }
+      [, ...] | ALL [ PRIVILEGES ] }
+      ON TABLES
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ]
+  ```
+
+- **grant_on_sequences_clause** grants permissions on sequences.
+
+  ```ebnf+diagram
+  grant_on_sequences_clause ::= GRANT { { SELECT | UPDATE | USAGE | ALTER | DROP | COMMENT }
+      [, ...] | ALL [ PRIVILEGES ] }
+      ON SEQUENCES
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ]
+  ```
+
+- **grant_on_functions_clause** grants permissions on functions.
+
+  ```ebnf+diagram
+  grant_on_functions_clause ::= GRANT { { EXECUTE | ALTER | DROP | COMMENT } [, ...] | ALL [ PRIVILEGES ] }
+      ON FUNCTIONS
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ]
+  ```
+
+- **grant_on_types_clause** grants permissions on types.
+
+  ```ebnf+diagram
+  grant_on_types_clause ::= GRANT { { USAGE | ALTER | DROP | COMMENT } [, ...] | ALL [ PRIVILEGES ] }
+      ON TYPES
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ]
+  ```
+
+- **revoke_on_tables_clause** revokes permissions on tables.
+
+  ```ebnf+diagram
+  revoke_on_tables_clause ::= REVOKE [ GRANT OPTION FOR ]
+      { { SELECT | INSERT | UPDATE | DELETE | TRUNCATE | REFERENCES | ALTER | DROP | COMMENT | INDEX | VACUUM }
+      [, ...] | ALL [ PRIVILEGES ] }
+      ON TABLES
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT | CASCADE CONSTRAINTS ]
+  ```
+
+- **revoke_on_sequences_clause** revokes permissions on sequences.
+
+  ```ebnf+diagram
+  revoke_on_sequences_clause ::= REVOKE [ GRANT OPTION FOR ]
+      { { SELECT | UPDATE | USAGE | ALTER | DROP | COMMENT }
+      [, ...] | ALL [ PRIVILEGES ] }
+      ON SEQUENCES
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT | CASCADE CONSTRAINTS ]
+  ```
+
+- **revoke_on_functions_clause** revokes permissions on functions.
+
+  ```ebnf+diagram
+  revoke_on_functions_clause ::= REVOKE [ GRANT OPTION FOR ]
+      { {EXECUTE | ALTER | DROP | COMMENT } [, ...] | ALL [ PRIVILEGES ] }
+      ON FUNCTIONS
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT | CASCADE CONSTRAINTS ]
+  ```
+
+- **revoke_on_types_clause** revokes permissions on types.
+
+  ```ebnf+diagram
+  revoke_on_types_clause ::= REVOKE [ GRANT OPTION FOR ]
+      { { USAGE | ALTER | DROP | COMMENT } [, ...] | ALL [ PRIVILEGES ] }
+      ON TYPES
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT | CASCADE CONSTRAINTS ]
+  ```
+
+## Parameter Description
+
+- **target_role**
+
+  Specifies the name of an existing role. If **FOR ROLE/USER** is omitted, the current role is assumed.
+
+  Value range: an existing role name
+
+- **schema_name**
+
+  Specifies the name of an existing schema.
+
+  **target_role** must have the **CREATE** permission for **schema_name**.
+
+  Value range: an existing schema name
+
+- **role_name**
+
+  Specifies the name of an existing role to grant or revoke permissions for.
+
+  Value range: an existing role name
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** To drop a role for which the default permissions have been granted, reverse the changes in its default permissions or use **DROP OWNED BY** to get rid of the default permission entry for the role.
+
+## Example
+
+```sql
+-- Grant the SELECT permission on all the tables (and views) in tpcds to every user.
+mogdb=# ALTER DEFAULT PRIVILEGES IN SCHEMA tpcds GRANT SELECT ON TABLES TO PUBLIC;
+
+-- Create a common user jack.
+mogdb=# CREATE USER jack PASSWORD 'xxxxxxx';
+
+-- Grant the INSERT permission on all the tables in tpcds to the user jack.
+mogdb=# ALTER DEFAULT PRIVILEGES IN SCHEMA tpcds GRANT INSERT ON TABLES TO jack;
+
+-- Revoke the preceding permissions.
+mogdb=# ALTER DEFAULT PRIVILEGES IN SCHEMA tpcds REVOKE SELECT ON TABLES FROM PUBLIC;
+mogdb=# ALTER DEFAULT PRIVILEGES IN SCHEMA tpcds REVOKE INSERT ON TABLES FROM jack;
+
+-- Delete user jack.
+mogdb=# DROP USER jack;
+```
+
+## Helpful Links
+
+[GRANT](108-GRANT)，[REVOKE](120-REVOKE)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/40-COMMIT-PREPARED.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/40-COMMIT-PREPARED.md
new file mode 100644
index 0000000000000000000000000000000000000000..4127420fa82780dc75966d6b1ec74a684ba6a69e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/40-COMMIT-PREPARED.md
@@ -0,0 +1,49 @@
+---
+title: COMMIT PREPARED
+summary: COMMIT PREPARED
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# COMMIT PREPARED
+
+## Function
+
+**COMMIT PREPARED** commits a prepared two-phase transaction.
+
+## Precautions
+
+- The function is only available in maintenance mode (when the GUC parameter **xc_maintenance_mode** is **on**). Exercise caution when enabling the mode. It is used by maintenance engineers for troubleshooting. Common users should not use the mode.
+- Only the transaction creators or system administrators can run the **COMMIT PREPARED** command. The creation and commit operations must be in different sessions.
+- The transaction function is maintained automatically by the database, and should be not visible to users.
+
+## Syntax
+
+```ebnf+diagram
+CommitPrepared ::= COMMIT PREPARED transaction_id ;
+```
+
+```ebnf+diagram
+CommitPrepared ::= COMMIT PREPARED transaction_id WITH CSN;
+```
+
+## Parameter Description
+
+- **transaction_id**
+
+  Specifies the identifier of the transaction to be committed. The identifier must be different from those for current prepared transactions.
+
+- **CSN(commit sequence number)**
+
+  Specifies the sequence number of the transaction to be committed. It is a 64-bit, incremental, unsigned number.
+
+## Example
+
+```sql
+-COMMIT PREPARED commits a transaction whose identifier is trans_test.
+mogdb=# COMMIT PREPARED 'trans_test';
+```
+
+## Helpful Links
+
+[PREPARE TRANSACTION](114-PREPARE-TRANSACTION), [ROLLBACK PREPARED](122-ROLLBACK-PREPARED).
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/41-COPY.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/41-COPY.md
new file mode 100644
index 0000000000000000000000000000000000000000..052b3d5d7df666d1d7ed63cf4c72589383026814
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/41-COPY.md
@@ -0,0 +1,638 @@
+---
+title: COPY
+summary: COPY
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# COPY
+
+## Function
+
+**COPY** copies data between tables and files.
+
+**COPY FROM** copies data from a file to a table, and **COPY TO** copies data from a table to a file.
+
+## Precautions
+
+- When the  **enable_copy_server_files**  parameter is disabled, only the initial user is allowed to run the  **COPY FROM FILENAME**  or  **COPY TO FILENAME**  statement. When the  **enable_copy_server_files**  parameter is enabled, users with the  **SYSADMIN**  permission or users who inherit the  **gs_role_copy_files**  permission of the built-in role are allowed to run the  **COPY FROM FILENAME**  or  **COPY TO FILENAME**  statement. By default,  **COPY FROM FILENAME**  or  **COPY TO FILENAME**  cannot be run for database configuration file, key files, certificate files, and audit logs to prevent unauthorized users from viewing or modifying sensitive files.
+- **COPY** applies only to tables but not views.
+- **COPY TO**  requires the select permission on the table to be read, and  **COPY FROM**  requires the insert permission on the table to be inserted.
+- If a list of columns is specified, **COPY** copies only the data of the specified columns between the file and the table. If a table has any columns that are not in the column list, **COPY FROM** inserts default values for those columns.
+- If a data source file is specified, the server must be able to access the file. If **STDIN** is specified, data flows between the client and the server. When entering data, use the **TAB** key to separate the columns of the table and use a backslash and a period (\.) in a new row to indicate the end of the input.
+- **COPY FROM** throws an error if any row in the data file contains more or fewer columns than expected.
+- The end of the data can be represented by a line that contains only backslashes and periods (\\.). If data is read from a file, the end flag is unnecessary. If data is copied between client applications, an end tag must be provided.
+- In **COPY FROM**, **\\N** is an empty string. To enter the actual value **\\N**, use **\\N**.
+- **COPY FROM** does not support data preprocessing during data import, such as expression operation and default value filling. If you need to preprocess data during the import, you need to import the data to a temporary table and then run SQL statements to insert the data to the table through operations. However, this method causes I/O expansion and reduces the import performance.
+- When a data format error occurs during **COPY FROM** execution, the transaction is rolled back. However, the error information is insufficient, making it difficult to locate the error data from a large amount of raw data.
+- **COPY FROM** and **COPY TO** apply to low concurrency and local import and export of a small amount of data.
+- If the target table has triggers,  **COPY**  is supported.
+
+## Syntax
+
+- Copy data from a file to a table.
+
+  ```ebnf+diagram
+  Copy ::= COPY table_name [ ( column_name [, ...] ) ]
+        FROM { 'filename' | STDIN }
+            [ [ USING ] DELIMITERS 'delimiters' ]
+            [ WITHOUT ESCAPING ]
+            [ LOG ERRORS ]
+            [ REJECT LIMIT 'limit' ]
+            [ WITH ( option [, ...] ) ]
+            | copy_option
+            | TRANSFORM  ( { column_name [ data_type ] [ AS transform_expr ] } [, ...] )
+            | FIXED FORMATTER ( { column_name( offset, length ) } [, ...] ) [ ( option [, ...] ) | copy_option [  ...] ] ;
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  > In the syntax,  **FIXED FORMATTER ({column_name(offset, length)} [, ...])**  and  **[(option [, ...]) | copy_option [...]]**  can be in any sequence.
+
+- Copy data from a table to a file.
+
+  ```ebnf+diagram
+  Copy ::= COPY table_name [ ( column_name [, ...] ) ]
+        TO { 'filename' | STDOUT }
+        [ [ USING ] DELIMITERS 'delimiters' ]
+        [ WITHOUT ESCAPING ]
+        [ WITH ( option [, ...] ) ]
+        | copy_option
+        | FIXED FORMATTER ( { column_name( offset, length ) } [, ...] ) [ ( option [, ...] ) | copy_option [  ...] ] ;
+  ```
+
+  ```ebnf+diagram
+  Copy ::= COPY query
+      TO { 'filename' | STDOUT }
+      [ WITHOUT ESCAPING ]
+      [ WITH ( option [, ...] ) ]
+      | copy_option
+      | FIXED FORMATTER ( { column_name( offset, length ) } [, ...] ) [ ( option [, ...] ) | copy_option [  ...] ] ;
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > 1. The syntax constraints of **COPY TO** are as follows:
+  >    **(query)** is incompatible with **[USING] DELIMITER**. If the data comes from a query result, **COPY TO** cannot specify **[USING] DELIMITERS**.
+  > 2. Use spaces to separate **copy_option** following **FIXED FORMATTTER**.
+  > 3. **copy_option** is the native parameter, while **option** is the parameter imported by a compatible foreign table.
+  > 4. In the syntax,  **FIXED FORMATTER ( { column_name( offset, length ) } [, ...] )**  and  **[ ( option [, ...] ) | copy_option [ ...] ]**  can be in any sequence.
+
+  The syntax of the optional parameter **option** is as follows:
+
+  ```ebnf+diagram
+  option ::= FORMAT 'format_name'
+  | OIDS [ boolean ]
+  | DELIMITER 'delimiter_character'
+  | NULL 'null_string'
+  | HEADER [ boolean ]
+  | FILEHEADER 'header_file_string'
+  | FREEZE [ boolean ]
+  | QUOTE 'quote_character'
+  | ESCAPE 'escape_character'
+  | EOL 'newline_character'
+  | NOESCAPING [ boolean ]
+  | FORCE_QUOTE { ( column_name [, ...] ) | * }
+  | FORCE_NOT_NULL ( column_name [, ...] )
+  | ENCODING 'encoding_name'
+  | IGNORE_EXTRA_DATA [ boolean ]
+  | FILL_MISSING_FIELDS [ boolean ]
+  | COMPATIBLE_ILLEGAL_CHARS [ boolean ]
+  | DATE_FORMAT 'date_format_string'
+  | TIME_FORMAT 'time_format_string'
+  | TIMESTAMP_FORMAT 'timestamp_format_string'
+  | SMALLDATETIME_FORMAT 'smalldatetime_format_string'
+  ```
+
+  The syntax of the optional parameter **copy_option** is as follows:
+
+  ```ebnf+diagram
+  copy_option ::= OIDS
+  | NULL 'null_string'
+  | HEADER
+  | FILEHEADER 'header_file_string'
+  | FREEZE
+  | FORCE_NOT_NULL column_name [, ...]
+  | FORCE_QUOTE { column_name [, ...] | * }
+  | BINARY
+  | CSV
+  | QUOTE [ AS ] 'quote_character'
+  | ESCAPE [ AS ] 'escape_character'
+  | EOL 'newline_character'
+  | ENCODING 'encoding_name'
+  | IGNORE_EXTRA_DATA
+  | FILL_MISSING_FIELDS
+  | COMPATIBLE_ILLEGAL_CHARS
+  | DATE_FORMAT 'date_format_string'
+  | TIME_FORMAT 'time_format_string'
+  | TIMESTAMP_FORMAT 'timestamp_format_string'
+  | SMALLDATETIME_FORMAT 'smalldatetime_format_string'
+  ```
+
+## Parameter Description
+
+- **query**
+
+  Specifies that the results are to be copied.
+
+  Valid value: a **SELECT** or **VALUES** command in parentheses
+
+- **table_name**
+
+  Specifies the name (possibly schema-qualified) of an existing table.
+
+  Value range: an existing table name
+
+- **column_name**
+
+  Specifies an optional list of columns to be copied.
+
+  Value range: any columns. All columns will be copied if no column list is specified.
+
+- **STDIN**
+
+  Specifies that input comes from the standard input.
+
+- **STDOUT**
+
+  Specifies that output goes to the standard output.
+
+- **FIXED**
+
+  Fixes column length. When the column length is fixed,  **DELIMITER**,  **NULL**, and  **CSV**  cannot be specified. When  **FIXED**  is specified,  **BINARY**,  **CSV**, and  **TEXT**  cannot be specified by  **option**  or  **copy_option**.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  > The definition of fixed length is as follows:
+  >
+  > 1. The column length of each record is the same.
+  > 2. Spaces are used for column padding. Columns of the numeric type are left-aligned and columns of the string type are right-aligned.
+  > 3. No delimiters are used between columns.
+
+- **[USING] DELIMITER 'delimiters'**
+
+  The string that separates columns within each row (line) of the file, and it cannot be larger than 10 bytes.
+
+  Value range: The delimiter cannot include any of the following characters: \.abcdefghijklmnopqrstuvwxyz0123456789
+
+  Value range: The default value is a tab character in text format and a comma in CSV format.
+
+- **WITHOUT ESCAPING**
+
+  Specifies, in text format, whether to escape the backslash () and its following characters.
+
+  Value range: text only
+
+- **LOG ERRORS**
+
+  If this parameter is specified, the error tolerance mechanism for data type errors in the **COPY FROM** statement is enabled.
+
+  Value range: a value set while data is imported using **COPY FROM**.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  > The restrictions of this error tolerance parameter are as follows:
+  >
+  > - This error tolerance mechanism captures only the data type errors (DATA_EXCEPTION) that occur during data parsing of **COPY FROM** on the primary node of the database.
+  > - If existing error tolerance parameters (for example, **IGNORE_EXTRA_DATA**) of the **COPY** statement are enabled, the error of the corresponding type will be processed as specified by the parameters and no error will be reported. Therefore, the error table does not contain such error data.
+
+- **LOG ERRORS DATA**
+
+  The differences between **LOG ERRORS DATA** and **LOG ERRORS** are as follows:
+
+  1. **LOG ERRORS DATA** fills the **rawrecord** column in the error tolerance table.
+
+  2. Only users with the **super** permission can use the **LOG ERRORS DATA** parameter.
+
+     > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **CAUTION:**
+     > If error content is too complex, it may fail to be written to the error tolerance table by using **LOG ERRORS DATA**, causing the task failure.
+
+- **REJECT LIMIT**'**limit'**
+
+  Used with the **LOG ERROR** parameter to set the upper limit of the tolerated errors in the **COPY FROM** statement. If the number of errors exceeds the limit, later errors will be reported based on the original mechanism.
+
+  Value range: a positive integer (1 to *INTMAX*) or **unlimited**
+
+  Default value: If **LOG ERRORS** is not specified, an error will be reported. If **LOG ERRORS** is specified, the default value is **0**.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  > In the error tolerance mechanism described in the description of **LOG ERRORS**, the count of **REJECT LIMIT** is calculated based on the number of data parsing errors on the primary node of the database where the **COPY FROM** statement is executed, not based on the number of all errors on the primary node.
+
+- **FORMATTER**
+
+  Defines the place of each column in the data file in fixed length mode. Defines the place of each column in the data file in the **column(***offset*,*length***)** format.
+
+  Value range:
+
+  - The value of **offset** must be larger than 0. The unit is byte.
+  - The value of **length** must be larger than 0. The unit is byte.
+
+  The total length of all columns must be less than 1 GB.
+
+  Replace columns that are not in the file with null.
+
+- **OPTION { option_name ' value ' }**
+
+    Specifies all types of parameters of a compatible foreign table.
+
+  - FORMAT
+
+    Specifies the format of the source data file in the foreign table.
+
+    Value range: **CSV**, **TEXT**, **FIXED**, and **BINARY**
+
+    - The CSV file can process newline characters efficiently, but cannot process certain special characters well.
+    - The TEXT file can process certain special characters efficiently, but cannot process newline characters well.
+    - In FIXED files, the column length of each record is the same. Spaces are used for padding, and the excessive part will be truncated.
+    - All data in the BINARY file is stored/read as binary format rather than as text. It is faster than the text and CSV formats, but a binary-format file is less portable.
+
+    Default value: **TEXT**
+
+  - DELIMITER
+
+    Specifies the character that separates columns within each row (line) of the file.
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+    >
+    > - The value of **delimiter** cannot be **\\r** or **\\n**.
+    > - A delimiter cannot be the same as the null value. The delimiter for the CSV format cannot be same as the **quote** value.
+    > - The delimiter for the TEXT format data cannot contain lowercase letters, digits, or special characters (.).
+    > - The data length of a single row should be less than 1 GB. A row that has many columns using long delimiters cannot contain much valid data.
+    > - You are advised to use multi-character delimiters or invisible delimiters. For example, you can use multi-characters (such as $^&) and invisible characters (such as 0x07, 0x08, and 0x1b).
+
+    Value range: a multi-character delimiter within 10 bytes
+
+    Default value:
+
+    - A tab character in text format
+    - A comma (,) in CSV format
+    - No delimiter in FIXED format
+
+  - NULL
+
+    Specifies the string that represents a null value.
+
+    Value range:
+
+    - A null value cannot be **\\r** or **\\n**. The maximum length is 100 characters.
+    - A null value cannot be the same as the  **delimiter**  or  **quote**  value.
+
+    Default value:
+
+    - The default value for the CSV format is an empty string without quotation marks.
+    - The default value for the TEXT format is **\\N**.
+
+  - HEADER
+
+    Specifies whether a file contains a header with the names of each column in the file. **header** is available only for CSV and FIXED files.
+
+    When data is imported, if **header** is **on**, the first row of the data file will be identified as the header and ignored. If **header** is **off**, the first row will be identified as a data row.
+
+    When data is exported, if header is  **on**,  **fileheader**  must be specified. If  **header**  is  **off**, an exported file does not contain a header.
+
+    Value range: **true**,  **on**,  **false**, and  **off**.
+
+    Default value: **false**
+
+  - QUOTE
+
+    Specifies a quoted character string for a CSV file.
+
+    Default value: single quotation marks (")
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+    >
+    > - The value of  **quote**  cannot be the same as that of the  **delimiter**  or  **null**  parameter.
+    > - The value of  **quote**  must be a single-byte character.
+    > - You are advised to set  **quote**  to an invisible character, such as  **0x07**,  **0x08**, or  **0x1b**.
+
+  - ESCAPE
+
+    Specifies an escape character for a CSV file. The value must be a single-byte character.
+
+    Default value: single quotation marks ('') If the value is the same as that of  **quote**, it will be replaced by  **\\0**.
+
+  - EOL 'newline_character'
+
+    Specifies the newline character style of the imported or exported data file.
+
+    Value range: multi-character newline characters within 10 bytes. Common newline characters include  **\\r**  (0x0D),  **\\n**  (0x0A), and  **\\r\\n**(0x0D0A). Special newline characters include  **$**  and  **\#**.
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+    >
+    > - The **EOL** parameter supports only the TEXT format for data import and export and does not support the CSV or FIXED format for data import. For forward compatibility, the EOL parameter can be set to **0x0D** or **0x0D0A** for data export in the CSV or FIXED format.
+    > - The value of  **EOL**  cannot be the same as that of the  **delimiter**  or  **null**  parameter.
+    > - The EOL parameter value cannot contain the following characters: .abcdefghijklmnopqrstuvwxyz0123456789.
+
+  - FORCE_QUOTE { ( column_name [, …] ) | * }
+
+    In  **CSV COPY TO**  mode, forces quotation marks to be used for all non-null values in each specified column. Null values are not quoted.
+
+    Value range: an existing column name
+
+  - FORCE_NOT_NULL ( column_name [, …] )
+
+    In  **CSV COPY FROM**  mode, the value for a specified column cannot be null.
+
+    Value range: an existing column name
+
+  - ENCODING
+
+    Specifies the encoding of data files. If this option is omitted, the current client encoding is used.
+
+  - IGNORE_EXTRA_DATA
+
+    Specifies whether to ignore excessive columns when the number of data source files exceeds the number of foreign table columns. This parameter is used only during data import.
+
+    Value range: **true**,  **on**,  **false**, and  **off**.
+
+    - If this parameter is set to  **true**  or  **on**  and the number of source data files exceeds the number of foreign table columns, excessive columns will be ignored.
+
+    - When the parameter is  **false**  or  **off**, and the number of data source files is more than the number of foreign table columns, the following error information will be displayed:
+
+    ```sql
+    extra data after last expected column
+    ```
+
+    Default value: **false**
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+    > If a newline character at the end of a row is missing and the row and another row are integrated into one, data in another row is ignored after the parameter is set to **true**.
+
+  - COMPATIBLE_ILLEGAL_CHARS
+
+    Specifies whether to tolerate invalid characters during data import. The parameter is valid only for data import using **COPY FROM**.
+
+    Value range: **true**,  **on**,  **false**, and  **off**.
+
+    - If this parameter is set to  **true**  or  **on**, invalid characters are tolerated and imported to the database after conversion.
+    - If this parameter is set to  **false**  or  **off**  and an error occurs when there are invalid characters, the import will be interrupted.
+
+    Default value: **false**  or  **off**
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+    > The rules for converting invalid characters are as follows:
+    >
+    > 1. **\0** is converted to a space.
+    > 2. Other invalid characters are converted to question marks.
+    > 3. If  **compatible_illegal_chars**  is set to  **true**  or  **on**, invalid characters are tolerated. If  **NULL**,  **DELIMITER**,  **QUOTE**, and  **ESCAPE**  are set to a spaces or question marks, errors like "illegal chars conversion may confuse COPY escape 0x20" will be displayed to prompt users to change parameter values that cause confusion, preventing import errors.
+
+  - FILL_MISSING_FIELDS
+
+    Specifies how to handle the problem that the last column of a row in a source data file is lost during data import.
+
+    Value range: **true**,  **on**,  **false**, and  **off**.
+
+    Default value: **false**  or  **off**
+
+  - DATE_FORMAT
+
+    Specifies the DATE format for data import. The BINARY format is not supported. When data of such format is imported, error "cannot specify bulkload compatibility options in BINARY mode" will occur. The parameter is valid only for data import using **COPY FROM**.
+
+    Value range: a valid DATE value For details, see [Date and Time Processing Functions and Operators](8-date-and-time-processing-functions-and-operators).
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+    > You can use the **TIMESTAMP_FORMAT** parameter to set the DATE format to **TIMESTAMP** for data import. For details, see **TIMESTAMP_FORMAT** below.
+
+  - TIME_FORMAT
+
+    Specifies the TIME format for data import. The BINARY format is not supported. When data of such format is imported, error "cannot specify bulkload compatibility options in BINARY mode" will occur. The parameter is valid only for data import using **COPY FROM**.
+
+    Value range: a valid TIME value. Time zones cannot be used. For details, see [Date and Time Processing Functions and Operators](8-date-and-time-processing-functions-and-operators).
+
+  - TIMESTAMP_FORMAT
+
+    Specifies the TIMESTAMP format for data import. The BINARY format is not supported. When data of such format is imported, error "cannot specify bulkload compatibility options in BINARY mode" will occur. The parameter is valid only for data import using **COPY FROM**.
+
+    Value range: a valid TIMESTAMP value. Time zones cannot be used. For details, see [Date and Time Processing Functions and Operators](8-date-and-time-processing-functions-and-operators).
+
+  - SMALLDATETIME_FORMAT
+
+    Specifies the SMALLDATETIME format for data import. The BINARY format is not supported. When data of such format is imported, error "cannot specify bulkload compatibility options in BINARY mode" will occur. The parameter is valid only for data import using **COPY FROM**.
+
+    Value range: a valid SMALLDATETIME value. For details, see [Date and Time Processing Functions and Operators](8-date-and-time-processing-functions-and-operators).
+
+- **COPY_OPTION { option_name ' value ' }**
+
+    Specifies all types of native parameters of **COPY**.
+
+  - NULL null_string
+
+    Specifies the string that represents a null value.
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+    > When using **COPY FROM**, any data item that matches this string will be stored as a null value, so make sure that you use the same string as you used with **COPY TO**.
+
+    Value range:
+
+    - A null value cannot be **\\r** or **\\n**. The maximum length is 100 characters.
+    - A null value cannot be the same as the  **delimiter**  or  **quote**  value.
+
+    Default value:
+
+    - The default value for the TEXT format is **\\N**.
+    - The default value for the CSV format is an empty string without quotation marks.
+
+  - HEADER
+
+    Specifies whether a file contains a header with the names of each column in the file. **header** is available only for CSV and FIXED files.
+
+    When data is imported, if **header** is **on**, the first row of the data file will be identified as the header and ignored. If **header** is **off**, the first row will be identified as a data row.
+
+    When data is exported, if header is  **on**,  **fileheader**  must be specified. If  **header**  is  **off**, an exported file does not contain a header.
+
+  - FILEHEADER
+
+    Specifies a file that defines the content in the header for exported data. The file contains data description of each column.
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+    >
+    > - This parameter is available only when **header** is **on** or **true**.
+    > - **fileheader** specifies an absolute path.
+    > - The file can contain only one row of header information, and ends with a newline character. Excess rows will be discarded. (Header information cannot contain newline characters.)
+    > - The length of the file including the newline character cannot exceed 1 MB.
+
+  - FREEZE
+
+    Sets the **COPY** loaded data row as **frozen**, like these data have executed **VACUUM FREEZE**.
+
+    This is a performance option of initial data loading. The data will be frozen only when the following three requirements are met:
+
+    - The table being loaded has been created or truncated in the same transaction before copying.
+    - There are no cursors open in the current transaction.
+    - There are no original snapshots in the current transaction.
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+    > When **COPY** is completed, all the other sessions will see the data immediately. However, this violates the general principle of MVCC visibility, and users should understand that this may cause potential risks.
+
+  - FORCE NOT NULL column_name [, …]
+
+    In **CSV COPY FROM** mode, the specified column is not null. If the column is null, its value is regarded as a string of 0 characters.
+
+    Value range: an existing column name
+
+  - FORCE QUOTE { column_name [, …] | * }
+
+    In  **CSV COPY TO**  mode, forces quotation marks to be used for all non-null values in each specified column.  Null values are not quoted.
+
+    Value range: an existing column name
+
+  - BINARY
+
+    Specifies that data is stored and read in binary mode instead of text mode. In binary mode, you cannot declare **DELIMITER**, **NULL**, or **CSV**. When **BINARY** is specified, **CSV**, **FIXED**, and **TEXT** cannot be specified through **option** or **copy_option**.
+
+  - CSV
+
+    Enables the CSV mode. When **CSV** is specified, **BINARY**, **FIXED**, and **TEXT** cannot be specified through **option** or **copy_option**.
+
+  - QUOTE [AS] 'quote_character'
+
+    Specifies a quoted character string for a CSV file.
+
+    Default value: single quotation marks (")
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+    >
+    > - The value of  **quote**  cannot be the same as that of the  **delimiter**  or  **null**  parameter.
+    > - The value of  **quote**  must be a single-byte character.
+    > - You are advised to set  **quote**  to an invisible character, such as  **0x07**,  **0x08**, or  **0x1b**.
+
+  - ESCAPE [AS] 'escape_character'
+
+    Specifies an escape character for a CSV file. The value must be a single-byte character.
+
+    The default value is single quotation marks ("). If the value is the same as that of **quote**, it will be replaced by **\0**.
+
+  - EOL 'newline_character'
+
+    Specifies the newline character style of the imported or exported data file.
+
+    Value range: multi-character newline characters within 10 bytes. Common newline characters include **\\r** (0x0D), **\\n** (0x0A), and **\\r\\n**(0x0D0A). Special newline characters include **$** and **#**.
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+    >
+    > - The  **EOL**  parameter supports only the TEXT format for data import and export and does not support the CSV or FIXED format. For forward compatibility, the  **EOL**  parameter can be set to  **0x0D**  or  **0x0D0A**  for data export in the CSV or FIXED format.
+    > - The value of  **EOL**  cannot be the same as that of the  **delimiter**  or  **null**  parameter.
+    > - The EOL parameter value cannot contain the following characters: .abcdefghijklmnopqrstuvwxyz0123456789.
+
+  - ENCODING 'encoding_name'
+
+    Specifies the name of a file encoding format.
+
+    Value range: a valid encoding format
+
+    Default value: current encoding format
+
+  - IGNORE_EXTRA_DATA
+
+    Specifies that when the number of data source files exceeds the number of foreign table columns, excess columns at the end of the row are ignored. This parameter is used only during data import.
+
+    If this parameter is not used and the number of columns in the data source file is greater than that defined in the foreign table, the following error information is displayed:
+
+    ```sql
+    extra data after last expected column
+    ```
+
+  - COMPATIBLE_ILLEGAL_CHARS
+
+    Specifies that invalid characters are tolerated during data import. Invalid characters are converted and then imported to the database. No error is reported and the import is not interrupted. The BINARY format is not supported. When data of such format is imported, error "cannot specify bulkload compatibility options in BINARY mode" will occur. The parameter is valid only for data import using **COPY FROM**.
+
+    If this parameter is not used, an error is reported when invalid characters are encountered during the import, and the import is interrupted.
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+    > The rules for converting invalid characters are as follows:
+    >
+    > 1. **\0** is converted to a space.
+    > 2. Other invalid characters are converted to question marks.
+    > 3. When  **compatible_illegal_chars**  is set to  **true**  or  **on**, after invalid characters such as  **NULL**,  **DELIMITER**,  **QUOTE**, and  **ESCAPE**  are converted to spaces or question marks, an error message like "illegal chars conversion may confuse COPY escape 0x20" will be displayed to remind you of possible parameter confusion caused by the conversion.
+
+  - FILL_MISSING_FIELDS
+
+    Specifies how to handle the problem that the last column of a row in a source data file is lost during data import.
+
+    Value range: **true**,  **on**,  **false**, and  **off**.
+
+    Default value: **false**  or  **off**
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+    > Do not specify this option. Currently, it does not enable error tolerance, but will make the parser ignore the said errors during data parsing on the primary node of the database. Such errors will not be recorded in the COPY error table (enabled using **LOG ERRORS REJECT LIMIT**) but will be reported later by the database node. Therefore, do not specify this option.
+
+  - DATE_FORMAT 'date_format_string'
+
+    Specifies the DATE format for data import. The BINARY format is not supported. When data of such format is imported, error "cannot specify bulkload compatibility options in BINARY mode" will occur. The parameter is valid only for data import using **COPY FROM**.
+
+    Value range: a valid DATE value For details, see [Date and Time Processing Functions and Operators](8-date-and-time-processing-functions-and-operators).
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+    > You can use the **TIMESTAMP_FORMAT** parameter to set the DATE format to **TIMESTAMP** for data import. For details, see **TIMESTAMP_FORMAT** below.
+
+  - TIME_FORMAT 'time_format_string'
+
+    Specifies the TIME format for data import. The BINARY format is not supported. When data of such format is imported, error "cannot specify bulkload compatibility options in BINARY mode" will occur. The parameter is valid only for data import using **COPY FROM**.
+
+    Value range: a valid TIME value. Time zones cannot be used. For details, see [Date and Time Processing Functions and Operators](8-date-and-time-processing-functions-and-operators).
+
+  - TIMESTAMP_FORMAT 'timestamp_format_string'
+
+    Specifies the TIMESTAMP format for data import. The BINARY format is not supported. When data of such format is imported, error "cannot specify bulkload compatibility options in BINARY mode" will occur. The parameter is valid only for data import using **COPY FROM**.
+
+    Value range: a valid TIMESTAMP value. Time zones cannot be used. For details, see [Date and Time Processing Functions and Operators](8-date-and-time-processing-functions-and-operators).
+
+  - SMALLDATETIME_FORMAT 'smalldatetime_format_string'
+
+    Specifies the SMALLDATETIME format for data import. The BINARY format is not supported. When data of such format is imported, error "cannot specify bulkload compatibility options in BINARY mode" will occur. The parameter is valid only for data import using **COPY FROM**.
+
+    Value range: a valid SMALLDATETIME value. For details, see [Date and Time Processing Functions and Operators](8-date-and-time-processing-functions-and-operators).
+
+  - TRANSFORM ( { column_name [ data_type ] [ AS transform_expr ] } [, ...] )
+
+    Specify the conversion expression of each column in the table.  **data_type**  specifies the data type of the column in the expression parameter.  **transform_expr**  is the target expression that returns the result value whose data type is the same as that of the target column in the table. For details about the expression, see  [Expressions](1-simple-expressions).
+
+  The following special backslash sequences are recognized by **COPY FROM**:
+
+  - **\\b**: Backslash (ASCII 8)
+  - **\\f**: Form feed (ASCII 12)
+  - **\\n**: Newline character (ASCII 10)
+  - **\\r**: Carriage return character (ASCII 13)
+  - **\\t**: Tab (ASCII 9)
+  - **\\v**: Vertical tab (ASCII 11)
+  - **\\digits**: Backslash followed by one to three octal digits specifies that the ASCII value is the character with that numeric code.
+  - **\\xdigits**: Backslash followed by an x and one or two hex digits specifies the character with that numeric code.
+
+## Examples
+
+```sql
+-- Copy data from the tpcds.ship_mode file to the /home/omm/ds_ship_mode.dat file:
+mogdb=# COPY tpcds.ship_mode TO '/home/omm/ds_ship_mode.dat';
+
+-- Output tpcds.ship_mode to stdout.
+mogdb=# COPY tpcds.ship_mode TO stdout;
+
+-- Copy data from the /home/omm/ds_ship_mode.dat file to the tpcds.ship_mode_t1 table, convert the data using the TRANSFORM expression, and insert the 10 characters on the left of the SM_TYPE column into the table.
+mogdb=# COPY tpcds.ship_mode_t1 FROM '/home/omm/ds_ship_mode.dat' TRANSFORM (SM_TYPE AS LEFT(SM_TYPE, 10));
+
+-- Create the tpcds.ship_mode_t1 table.
+mogdb=# CREATE TABLE tpcds.ship_mode_t1
+(
+    SM_SHIP_MODE_SK           INTEGER               NOT NULL,
+    SM_SHIP_MODE_ID           CHAR(16)              NOT NULL,
+    SM_TYPE                   CHAR(30)                      ,
+    SM_CODE                   CHAR(10)                      ,
+    SM_CARRIER                CHAR(20)                      ,
+    SM_CONTRACT               CHAR(20)
+)
+WITH (ORIENTATION = COLUMN,COMPRESSION=MIDDLE)
+;
+
+-- Copy data from stdin to the tpcds.ship_mode_t1 table.
+mogdb=# COPY tpcds.ship_mode_t1 FROM stdin;
+
+-- Copy data from the /home/omm/ds_ship_mode.dat file to the tpcds.ship_mode_t1 table.
+mogdb=# COPY tpcds.ship_mode_t1 FROM '/home/omm/ds_ship_mode.dat';
+
+-- Copy data from the /home/omm/ds_ship_mode.dat file to the tpcds.ship_mode_t1 table, with the import format set to TEXT (format 'text'), the delimiter set to \t' (delimiter E'\t'), excessive columns ignored (ignore_extra_data 'true'), and characters not escaped (noescaping 'true').
+mogdb=# COPY tpcds.ship_mode_t1 FROM '/home/omm/ds_ship_mode.dat' WITH(format 'text', delimiter E'\t', ignore_extra_data 'true', noescaping 'true');
+
+-- Copy data from the /home/omm/ds_ship_mode.dat file to the tpcds.ship_mode_t1 table, with the import format set to FIXED, fixed-length format specified (FORMATTER(SM_SHIP_MODE_SK(0, 2), SM_SHIP_MODE_ID(2,16), SM_TYPE(18,30), SM_CODE(50,10), SM_CARRIER(61,20), SM_CONTRACT(82,20))), excessive columns ignored (ignore_extra_data), and headers included (header).
+mogdb=# COPY tpcds.ship_mode_t1 FROM '/home/omm/ds_ship_mode.dat' FIXED FORMATTER(SM_SHIP_MODE_SK(0, 2), SM_SHIP_MODE_ID(2,16), SM_TYPE(18,30), SM_CODE(50,10), SM_CARRIER(61,20), SM_CONTRACT(82,20)) header ignore_extra_data;
+
+-- Delete the tpcds.ship_mode_t1 table.
+mogdb=# DROP TABLE tpcds.ship_mode_t1;
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/41.1-CREATE-AGGREGATE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/41.1-CREATE-AGGREGATE.md
new file mode 100644
index 0000000000000000000000000000000000000000..a03a8e5b8174ca83ec15d5b2fae85f88b3097ea2
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/41.1-CREATE-AGGREGATE.md
@@ -0,0 +1,88 @@
+---
+title: CREATE AGGREGATE
+summary: CREATE AGGREGATE
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# CREATE AGGREGATE
+
+## Function
+
+**CREATE AGGREGATE** defines a new aggregate function.
+
+## Syntax
+
+```ebnf+diagram
+CreateAggregate ::= CREATE AGGREGATE name ( input_data_type [ , ... ] ) (
+    SFUNC = sfunc,
+    STYPE = state_data_type
+    [ , FINALFUNC = ffunc ]
+    [ , INITCOND = initial_condition ]
+    [ , SORTOP = sort_operator ]
+)
+```
+
+or the old syntax
+
+```ebnf+diagram
+CreateAggregate ::= CREATE AGGREGATE name (
+    BASETYPE = base_type,
+    SFUNC = sfunc,
+    STYPE = state_data_type
+    [ , FINALFUNC = ffunc ]
+    [ , INITCOND = initial_condition ]
+    [ , SORTOP = sort_operator ]
+)
+```
+
+## Parameter Description
+
+- **name**
+
+  Name (optionally schema-qualified) of the aggregate function to be created.
+
+- **input_data_type**
+
+  Data type of the input to be processed by the aggregate function. To create a zero-parameter aggregate function, you can use an asterisk (*) instead of a list of input data types. (count(*) is an instance of this aggregate function.)
+
+- **base_type**
+
+  In the **CREATE AGGREGATE** syntax, the input data type is specified by the **basetype** parameter instead of following **name**. Note that the previous syntax allows only one input parameter. To create a zero-parameter aggregate function, you can set **basetype** to **ANY** instead of *****.
+
+- **sfunc**
+
+  Name of the state conversion function that will be called on each input line. For an aggregate function with N parameters, **sfunc** must have more than one parameter. The first parameter is of the **state_data_type** type, and the other parameters match the declared input data types. The function must return a value of the **state_data_type** type. This function accepts the current state value and the current input data, and returns the next state value.
+
+- **state_data_type**
+
+  Data type of the aggregation status value.
+
+- **ffunc**
+
+  Final processing function called after all the input lines have been converted, which calculates the result of aggregation. This function must accept a parameter of **state_data_type**. The output data type of the aggregation is defined as the return type of this function. If **ffunc** is not specified, the state value of the aggregation result is used as the aggregation result, and the output type is **state_data_type**.
+
+- **initial_condition**
+
+  Initial setting (value) of a state value. It must be a text constant value acceptable to **state_data_type**. If not specified, the initial state value is **NULL**.
+
+- **sort_operator**
+
+  Sort operator used for MIN or MAX aggregation. This is just an operator name (optionally schema-qualified). This operator assumes that the input data type is the same as that of aggregation.
+
+## Examples
+
+```sql
+CREATE AGGREGATE sum (complex)
+(
+    sfunc = complex_add,
+    stype = complex,
+    initcond = '(0,0)'
+);
+
+SELECT sum(a) FROM test_complex;
+
+   sum
+-----------
+ (34,53.9)
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/41.2-CREATE-AUDIT-POLICY.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/41.2-CREATE-AUDIT-POLICY.md
new file mode 100644
index 0000000000000000000000000000000000000000..762f495fc2bd79ed571847ec8d143d84f2337ad6
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/41.2-CREATE-AUDIT-POLICY.md
@@ -0,0 +1,108 @@
+---
+title: CREATE AUDIT POLICY
+summary: CREATE AUDIT POLICY
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# CREATE AUDIT POLICY
+
+## Function
+
+**CREATE AUDIT POLICY** creates a unified audit policy.
+
+## Precautions
+
+Only users with the  **poladmin**  or  **sysadmin**  permission, or the initial user can perform this operation.
+
+The masking policy takes effect only after the security policy is enabled, that is, **enable_security_policy** is set to **on**.
+
+## Syntax
+
+```ebnf+diagram
+CreateAuditPolicy ::= CREATE AUDIT POLICY [ IF NOT EXISTS ] policy_name { { privilege_audit_clause | access_audit_clause } [ filter_group_clause ] [ ENABLE | DISABLE ] };
+```
+
+- privilege_audit_clause
+
+  ```ebnf+diagram
+  privilege_audit_clause ::= PRIVILEGES { DDL | ALL } [ ON LABEL ( resource_label_name [, ... ] ) ]
+  ```
+
+- access_audit_clause
+
+  ```ebnf+diagram
+  access_audit_clause ::= ACCESS { DML | ALL } [ ON LABEL ( resource_label_name [, ... ] ) ]
+  ```
+
+- filter_group_clause
+
+  ```ebnf+diagram
+  filter_group_clause ::= FILTER ON { ( FILTER_TYPE ( filter_value [, ... ] ) ) [, ... ] }
+  ```
+
+## Parameter Description
+
+- **policy_name**
+
+  Specifies the audit policy name, which must be unique.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **DDL**
+
+  Specifies the operations that are audited within the database: **CREATE**, **ALTER**, **DROP**, **ANALYZE**, **COMMENT**, **GRANT**, **REVOKE**, **SET**, **SHOW**, **LOGIN_ANY**, **LOGIN_FAILURE**, **LOGIN_SUCCESS**, and **LOGOUT**.
+
+- **ALL**
+
+  Indicates all operations supported by the specified DDL statements in the database.
+
+- **resource_label_name**
+
+  Specifies the resource label name.
+
+- **DML**
+
+  Specifies the operations that are audited within the database: **SELECT**, **COPY**, **DEALLOCATE**, **DELETE**, **EXECUTE**, **INSERT**, **PREPARE**, **REINDEX**, **TRUNCATE**, and **UPDATE**.
+
+- **FILTER_TYPE**
+
+  Specifies the types of information to be filtered by the audit, including **IP**, **APP**, and **ROLES**.
+
+- **filter_value**
+
+  Indicates the detailed information to be filtered.
+
+- **ENABLE|DISABLE**
+
+  Enables or disables the unified audit policy. If **ENABLE|DISABLE** is not specified, **ENABLE** is used by default.
+
+## Examples
+
+```sql
+-- Create users dev_audit and bob_audit.
+mogdb=# CREATE USER dev_audit PASSWORD 'dev@1234';
+mogdb=# CREATE USER bob_audit password 'bob@1234';
+
+-- Create table tb_for_audit.
+mogdb=# CREATE TABLE tb_for_audit(col1 text, col2 text, col3 text);
+
+-- Create a resource label.
+mogdb=# CREATE RESOURCE LABEL adt_lb0 add TABLE(tb_for_audit);
+
+-- Perform the CREATE operation on the database to create an audit policy.
+mogdb=# CREATE AUDIT POLICY adt1 PRIVILEGES CREATE;
+
+-- Perform the SELECT operation on the database to create an audit policy.
+mogdb=# CREATE AUDIT POLICY adt2 ACCESS SELECT;
+
+-- Create an audit policy to audit only the CREATE operations performed on the adt_lb0 resource by users dev_audit and bob_audit.
+mogdb=# CREATE AUDIT POLICY adt3 PRIVILEGES CREATE ON LABEL(adt_lb0) FILTER ON ROLES(dev_audit, bob_audit);
+
+-- Create an audit policy to audit only the SELECT, INSERT, and DELETE operations performed on the adt_lb0 resource by users dev_audit and bob_audit using client tools psql and gsql on the servers whose IP addresses are 10.20.30.40 and 127.0.0.0/24.
+mogdb=# CREATE AUDIT POLICY adt4 ACCESS SELECT ON LABEL(adt_lb0), INSERT ON LABEL(adt_lb0), DELETE FILTER ON ROLES(dev_audit, bob_audit), APP(psql, gsql), IP('10.20.30.40', '127.0.0.0/24');
+```
+
+## Helpful Links
+
+[ALTER AUDIT POLICY](1.2-ALTER-AUDIT-POLICY), [DROP AUDIT POLICY](75.2-DROP-AUDIT-POLICY).
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/41.3-CREATE-CAST.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/41.3-CREATE-CAST.md
new file mode 100644
index 0000000000000000000000000000000000000000..dc3d75a98056fc0dfe766a0e8e560edd0a24bec6
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/41.3-CREATE-CAST.md
@@ -0,0 +1,90 @@
+---
+title: CREATE CAST
+summary: CREATE CAST
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# CREATE CAST
+
+## Function
+
+CREATE CAST defines a conversion.
+
+## Precautions
+
+DROP AGGREGATE deletes an existing aggregate function. Only the owner of the aggregate function can run this command.
+
+## Syntax
+
+```ebnf+diagram
+CreateCast ::= CREATE CAST (source_type AS target_type)
+    WITH FUNCTION function_name (argument_type [, ...])
+    [ AS ASSIGNMENT | AS IMPLICIT ]
+```
+
+```ebnf+diagram
+CreateCast ::= CREATE CAST (source_type AS target_type)
+    WITHOUT FUNCTION
+    [ AS ASSIGNMENT | AS IMPLICIT ]
+```
+
+```ebnf+diagram
+CreateCast ::= CREATE CAST (source_type AS target_type)
+    WITH INOUT
+    [ AS ASSIGNMENT | AS IMPLICIT ]
+```
+
+## Parameter Description
+
+- **source_type**
+
+  Type of the source data to be converted.
+
+- **target_type**
+
+  Type of the target data to be converted.
+
+- **function_name(argument_type [, …])**
+
+  Function used for conversion. The function name can be modified with a schema name. If it is not modified with a schema name, the function will be found in the schema search path. The result data type of the function must match the target type of the conversion. Its parameters are discussed below.
+
+- **WITHOUT FUNCTION**
+
+  Indicates that the source type is a binary castable to the target type, so no function is needed to perform this conversion.
+
+- **WITH INOUT**
+
+  Indicates that the conversion is an I/O conversion, which is performed by calling the output function of the source data type and transferring the result to the input function of the target data type.
+
+- **AS ASSIGNMENT**
+
+  Indicates that the conversion can be implicitly called in assignment mode.
+
+- **AS IMPLICIT**
+
+  Indicates that the transformation can be implicitly called in any environment.
+
+  A conversion implementation function can have one to three parameters. The type of the first parameter must be the same as that of the source type to be converted, or can be forcibly converted from the binary of the source type to be converted. If the second parameter exists, it must be of the integer type. It receives these type modifiers associated with the target type, or **-1** if nothing is present. If the third parameter exists, it must be of the Boolean type. If the conversion is an explicit type conversion, **true** is received. Otherwise, **false** is received.
+
+  The return type of a conversion function must be the same as the target type of the conversion, or the binary of the target type of the conversion can be forcibly converted.
+
+  Typically, a transformation must have different source and target data types. However, if there is a conversion implementation function with more than one parameter, it is allowed to declare a conversion with the same source and target types. This is used to represent a length enforcement function of a specific type in the system catalog. The named function is used to force a value of this type to be the type modifier value given by the second parameter.
+
+  If the source type and target type of a type conversion are different and more than one parameter is received, it indicates that only one step is required to convert one type to another and the length conversion is performed at the same time. If no such item is available, converting to a type that uses a type modifier involves two steps, one to convert between data types, and the other to apply a conversion specified by the modifier.
+
+  Currently, domain type conversion does not take effect. Transformations are typically targeted to the domain-related data types to which they belong.
+
+## Example
+
+To create an assignment mapping from type bigint to type int4, use the int4(bigint) function:
+
+```sql
+CREATE CAST (bigint AS int4) WITH FUNCTION int4(bigint) AS ASSIGNMENT;
+```
+
+(The conversion has been predefined in the system.)
+
+## Compatibility
+
+The CREATE CAST instruction complies with the SQL standard. Except that the SQL does not have extra parameters that can be forcibly converted to binary types or implement functions.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/42-CREATE-CLIENT-MASTER-KEY.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/42-CREATE-CLIENT-MASTER-KEY.md
new file mode 100644
index 0000000000000000000000000000000000000000..6c52d60dd30862b500d700a141f3bbc301d9decb
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/42-CREATE-CLIENT-MASTER-KEY.md
@@ -0,0 +1,59 @@
+---
+title: CREATE CLIENT MASTER KEY
+summary: CREATE CLIENT MASTER KEY
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE CLIENT MASTER KEY
+
+## Function
+
+**CREATE CLIENT MASTER KEY** creates a CMK object that can be used to encrypt a CEK object.
+
+## Precautions
+
+This syntax is specific to a fully-encrypted database.
+
+When using **gsql** to connect to a database server, you need to use the **-C** parameter to enable the fully-encrypted database.
+
+In the CMK object created using this syntax, only the method for reading keys from independent key management tools, services, or components is stored. The key itself is not stored.
+
+## Syntax
+
+```ebnf+diagram
+CreateClientMasterKey ::= CREATE CLIENT MASTER KEY client_master_key_name WITH (KEY_STORE = key_store_name, KEY_PATH = "key_path_value", ALGORITHM = algorithm_type)
+```
+
+## Parameter Description
+
+- **client_master_key_name**
+
+  This parameter is used as the name of a key object. In the same namespace, the value of this parameter must be unique.
+
+  Value range: a string. It must comply with the identifier naming convention.
+
+- **KEY_STORE**
+
+  Specifies the key tool or component that manages CMKs. Currently, only **localkms** is supported.
+
+- **KEY_PATH**
+
+  **KEY_STORE** manages multiple CMKs. The **KEY_PATH** option is used to uniquely identify a CMK in **KEY_STORE**. The value is similar to that of **key_path_value**.
+
+- **ALGORITHM**
+
+  Type of the encryption algorithm used to encrypt CEKs. Value range: **RSA_2048**, **RSA3072**, and **SM2**.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** **Key storage path**: By default, **localkms** generates, reads, or deletes a key file in the `$LOCALKMS_FILE_PATH` path. You can manually configure this environment variable. However, you do not need to configure this environment variable separately. When failing to obtain `$LOCALKMS_FILE_PATH`, **localkms** attempts to obtain the *$GAUSSHOME***/etc/localkms/** path. If the path exists, it is used as the key storage path. **Key-related file name**: When the **CREATE CMK** syntax is used, **localkms** creates four files related to key paths. For example, when **KEY_PATH** is set to **key_path_value**, the names of the four files are **key_path_value.pub**, **key_path_value.pub.rand**, **key_path_value.priv**, and **key_path_value.priv.rand**. Therefore, to successfully create key-related files, ensure that no file with the same name as the key-related files exists in the key path.
+
+## Examples
+
+```sql
+-- (1) Use the common account alice to connect to the fully-encrypted database.
+[cmd] gsql -U alice -h $host -p $port -d $database -C -r
+
+-- (2) Use this syntax to create a CMK object.
+mogdb=> CREATE CLIENT MASTER KEY a_cmk WITH (KEY_STORE = localkms, KEY_PATH = "key_path_value", ALGORITHM = RSA_2048);
+mogdb=> CREATE CLIENT MASTER KEY another_cmk WITH (KEY_STORE = localkms, KEY_PATH = "another_path_value", ALGORITHM = SM2);
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/43-CREATE-COLUMN-ENCRYPTION-KEY.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/43-CREATE-COLUMN-ENCRYPTION-KEY.md
new file mode 100644
index 0000000000000000000000000000000000000000..0473f00b048ff73c24e031be4dbadd7043cf261a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/43-CREATE-COLUMN-ENCRYPTION-KEY.md
@@ -0,0 +1,58 @@
+---
+title: CREATE COLUMN ENCRYPTION KEY
+summary: CREATE COLUMN ENCRYPTION KEY
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE COLUMN ENCRYPTION KEY
+
+## Function
+
+**CREATE COLUMN ENCRYPTION KEY** creates a CEK that can be used to encrypt a specified column in a table.
+
+## Precautions
+
+This syntax is specific to a fully-encrypted database.
+
+When using **gsql** to connect to a database server, you need to use the -C parameter to enable the fully-encrypted database.
+
+The CEK object created using this syntax can be used for column-level encryption. When defining a column in a table, you can specify a CEK object to encrypt the column.
+
+## Syntax
+
+```ebnf+diagram
+CreateColumnEncryptionKey ::= CREATE COLUMN ENCRYPTION KEY column_encryption_key_name WITH(CLIENT_MASTER_KEY = client_master_key_name, ALGORITHM = algorithm_type, ENCRYPTED_VALUE = encrypted_value);
+```
+
+## Parameter Description
+
+- **column_encryption_key_name**
+
+  This parameter is used as the name of a key object. In the same namespace, the value of this parameter must be unique.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **CLIENT_MASTER_KEY**
+
+  Specifies the CMK used to encrypt the CEK. The value is the CMK object name, which is created using the **CREATE CLIENT MASTER KEY** syntax.
+
+- **ALGORITHM**
+
+  Encryption algorithm to be used by the CEK. The value can be **AEAD_AES_256_CBC_HMAC_SHA256**, **AEAD_AES_128_CBC_HMAC_SHA256**, or **SM4_SM3**.
+
+- **ENCRYPTED_VALUE (optional)**
+
+  A key password specified by a user. The key password length ranges from 28 to 256 bits. The derived 28-bit key meets the AES128 security requirements. If the user needs to use AES256, the key password length must be 39 bits. If the user does not specify the key password length, a 256-bit key is automatically generated.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** Chinese National Cryptography Standard (Guomi) constraints: SM2, SM3, and SM4 are Chinese national cryptography standards. To avoid legal risks, these algorithms must be used together. That is, if the CEK is used in the SM4_SM3 algorithm, only the SM4 algorithm can be used to encrypt the CEK.
+
+## Examples
+
+```sql
+-- Create a CEK.
+mogdb=> CREATE COLUMN ENCRYPTION KEY a_cek WITH VALUES (CLIENT_MASTER_KEY = a_cmk, ALGORITHM  = AEAD_AES_256_CBC_HMAC_SHA256);
+CREATE COLUMN ENCRYPTION KEY
+mogdb=> CREATE COLUMN ENCRYPTION KEY another_cek WITH VALUES (CLIENT_MASTER_KEY = a_cmk, ALGORITHM  = SM4_SM3);
+CREATE COLUMN ENCRYPTION KEY
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/44-CREATE-DATABASE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/44-CREATE-DATABASE.md
new file mode 100644
index 0000000000000000000000000000000000000000..a4aead4bf7240744e7bd59ea1561e7250ec4b4ca
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/44-CREATE-DATABASE.md
@@ -0,0 +1,232 @@
+---
+title: CREATE DATABASE
+summary: CREATE DATABASE
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE DATABASE
+
+## Function
+
+**CREATE DATABASE** is used to create a database. By default, the new database will be created only by cloning the standard system database **template0**.
+
+## Precautions
+
+- A user that has the **CREATEDB** permission or a system administrator can create a database.
+- **CREATE DATABASE** cannot be executed inside a transaction block.
+- During the database creation, an error message indicating that permission denied is displayed, possibly because the permission on the data directory in the file system is insufficient. If an error message, indicating no space left on device is displayed, the possible cause is that the disk space is used up.
+
+## Syntax
+
+```ebnf+diagram
+CreateDatabase ::= CREATE DATABASE database_name
+    [ [ WITH ] { [ OWNER [=] user_name ] |
+               [ TEMPLATE [=] template ] |
+               [ ENCODING [=] encoding ] |
+               [ LC_COLLATE [=] lc_collate ] |
+               [ LC_CTYPE [=] lc_ctype ] |
+               [ DBCOMPATIBILITY [=] compatibilty_type ] |
+               [ TABLESPACE [=] tablespace_name ] |
+               [ CONNECTION LIMIT [=] connlimit ]}[...] ];
+```
+
+## Parameter Description
+
+- **database_name**
+
+  Specifies the database name.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **OWNER [ = ] user_name**
+
+  Specifies the owner of the new database. If omitted, the default owner is the current user.
+
+  Value range: an existing username
+
+- **TEMPLATE [ = ] template**
+
+  Specifies a template name. That is, the template from which the database is created. MogDB creates a database by copying data from a template database. MogDB has two default template databases **template0** and **template1** and a default user database **postgres**.
+
+  Value range: **template0**
+
+- **ENCODING [ = ] encoding**
+
+  Specifies the character encoding used by the database. The value can be a string (for example, **SQL_ASCII**) or an integer.
+
+  If this parameter is not specified, the encoding of the template database is used by default. By default, the codes of the template databases **template0** and **template1** are related to the operating system environment. The character encoding of **template1** cannot be changed. To change the encoding, use **template0** to create a database.
+
+  The common values are **GBK**, **UTF8**, and **Latin1**.
+
+  **Table 1** MogDB character set
+
+  | **Name**       | Description                       | **Language**                       | **Server Or Not** | **ICU Or Not** | **Byte/Character** | **Alias**                             |
+  | :---------------------------- | :-------------------------------- | :--------------------------------- | :---------------- | :------------- | :----------------- | :------------------------------------ |
+  | BIG5           | Big Five                          | Traditional Chinese                | No                | No             | 1-2                | WIN950, Windows950                    |
+  | EUC_CN         | Extended UNIX Code-CN             | Simplified Chinese                 | Yes               | Yes            | 1-3                | -                                     |
+  | EUC_JP         | Extended UNIX Code-JP             | Japanese                           | Yes               | Yes            | 1-3                | -                                     |
+  | EUC_JIS_2004   | Extended UNIX Code-JP, JIS X 0213 | Japanese                           | Yes               | No             | 1-3                | -                                     |
+  | EUC_KR         | Extended UNIX Code-KR             | Korean                             | Yes               | Yes            | 1-3                | -                                     |
+  | EUC_TW         | Extended UNIX Code-TW             | Traditional Chinese, Taiwan, China | Yes               | Yes            | 1-3                | -                                     |
+  | GB18030        | National Standard                 | Chinese                            | Yes               | No             | 1-4                | -                                     |
+  | GBK            | Extended National Standard        | Simplified Chinese                 | Yes               | No             | 1-2                | WIN936, Windows936                    |
+  | ISO_8859_5     | ISO 8859-5, ECMA 113              | Latin/Cyrillic                     | Yes               | Yes            | 1                  | -                                     |
+  | ISO_8859_6     | ISO 8859-6, ECMA 114              | Latin/Arabic                       | Yes               | Yes            | 1                  | -                                     |
+  | ISO_8859_7     | ISO 8859-7, ECMA 118              | Latin/Greek                        | Yes               | Yes            | 1                  | -                                     |
+  | ISO_8859_8     | ISO 8859-8, ECMA 121              | Latin/Hebrew                       | Yes               | Yes            | 1                  | -                                     |
+  | JOHAB          | JOHAB                             | Korean                             | No                | No             | 1-3                | -                                     |
+  | KOI8R          | KOI8-R                            | Cyrillic (Russian)                 | Yes               | Yes            | 1                  | KOI8                                  |
+  | KOI8U          | KOI8-U                            | Cyrillic (Ukrainian)               | Yes               | Yes            | 1                  | -                                     |
+  | LATIN1         | ISO 8859-1, ECMA 94               | Western European                   | Yes               | Yes            | 1                  | ISO88591                              |
+  | LATIN2         | ISO 8859-2, ECMA 94               | Central European                   | Yes               | Yes            | 1                  | ISO88592                              |
+  | LATIN3         | ISO 8859-3, ECMA 94               | South European                     | Yes               | Yes            | 1                  | ISO88593                              |
+  | LATIN4         | ISO 8859-4, ECMA 94               | North European                     | Yes               | Yes            | 1                  | ISO88594                              |
+  | LATIN5         | ISO 8859-9, ECMA 128              | Turkish                            | Yes               | Yes            | 1                  | ISO88599                              |
+  | LATIN6         | ISO 8859-10, ECMA 144             | Nordic                             | Yes               | Yes            | 1                  | ISO885910                             |
+  | LATIN7         | ISO 8859-13                       | Baltic                             | Yes               | Yes            | 1                  | ISO885913                             |
+  | LATIN8         | ISO 8859-14                       | Celtic                             | Yes               | Yes            | 1                  | ISO885914                             |
+  | LATIN9         | ISO 8859-15                       | LATIN1 with Euro and accents       | Yes               | Yes            | 1                  | ISO885915                             |
+  | LATIN10        | ISO 8859-16, ASRO SR 14111        | Romanian                           | Yes               | No             | 1                  | ISO885916                             |
+  | MULE_INTERNAL  | Mule internal code                | Multilingual Emacs                 | Yes               | No             | 1-4                | -                                     |
+  | SJIS           | Shift JIS                         | Japanese                           | No                | No             | 1-2                | Mskanji, ShiftJIS, WIN932, Windows932 |
+  | SHIFT_JIS_2004 | Shift JIS, JIS X 0213             | Japanese                           | No                | No             | 1-2                | -                                     |
+  | SQL_ASCII      | Unspecified (see the text)        | *Any*                              | Yes               | No             | 1                  | -                                     |
+  | UHC            | Unified Hangul Code               | Korean                             | No                | No             | 1-2                | WIN949, Windows949                    |
+  | UTF8           | Unicode, 8-bit                    | ***All***                          | Yes               | Yes            | 1-4                | Unicode                               |
+  | WIN866         | Windows CP866                     | Cyrillic                           | Yes               | Yes            | 1                  | ALT                                   |
+  | WIN874         | Windows CP874                     | Thai                               | Yes               | No             | 1                  | -                                     |
+  | WIN1250        | Windows CP1250                    | Central European                   | Yes               | Yes            | 1                  | -                                     |
+  | WIN1251        | Windows CP1251                    | Cyrillic                           | Yes               | Yes            | 1                  | WIN                                   |
+  | WIN1252        | Windows CP1252                    | Western European                   | Yes               | Yes            | 1                  | -                                     |
+  | WIN1253        | Windows CP1253                    | Greek                              | Yes               | Yes            | 1                  | -                                     |
+  | WIN1254        | Windows CP1254                    | Turkish                            | Yes               | Yes            | 1                  | -                                     |
+  | WIN1255        | Windows CP1255                    | Hebrew                             | Yes               | Yes            | 1                  | -                                     |
+  | WIN1256        | Windows CP1256                    | Arabic                             | Yes               | Yes            | 1                  | -                                     |
+  | WIN1257        | Windows CP1257                    | Baltic                             | Yes               | Yes            | 1                  | -                                     |
+  | WIN1258        | Windows CP1258                    | Vietnamese                         | Yes               | Yes            | 1                  | ABC, TCVN, TCVN5712, VSCII            |
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **CAUTION:** Note that not all client APIs support the preceding character sets. The SQL_ASCII setting performs quite differently from other settings. If the character set of the server is SQL_ASCII, the server interprets the byte values 0 to 127 according to the ASCII standard. The byte values 128 to 255 are regarded as the characters that cannot be parsed. If this parameter is set to SQL_ASCII, no code conversion occurs. Therefore, this setting is not basically used to declare the specified encoding used, because this declaration ignores the encoding. In most cases, if you use any non-ASCII data, it is unwise to use the SQL_ASCII setting because MogDB will not be able to help you convert or validate non-ASCII characters.
+  >
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+  >
+  > - The character set encoding of the new database must be compatible with the local settings (**LC_COLLATE** and **LC_CTYPE**).
+  > - When the specified character encoding set is **GBK**, some uncommon Chinese characters cannot be directly used as object names. This is because the byte encoding overlaps with the ASCII characters @A-Z[\^_`a-z{|} when the second byte of the GBK ranges from 0x40 to 0x7E. **@[]^\_'{|}** is an operator in the database. If it is directly used as an object name, a syntax error will be reported. For example, the GBK hexadecimal code is **0x8240**, and the second byte is **0x40**, which is the same as the ASCII character @. Therefore, the character cannot be used as an object name. If you do need to use this function, you can add double quotation marks ("") to avoid this problem when creating and accessing objects.
+  > - If the client-side encoding is A and the server-side encoding is B, the conversion between encoding format A and B in the database needs to be met. For example: if the server-side encoding is gb18030, since the current database does not support the conversion between gb18030 and gbk, When the client encoding format is set to gbk, the error "Conversion between GB18030 and GBK is not supported." will be reported. For all the encoding format conversions that the database can support, see the system table pg_conversion for details.
+
+- **LC_COLLATE [ = ] lc_collate**
+
+  Specifies the character set used by the new database. For example, set this parameter by using **lc_collate = 'zh_CN.gbk'**.
+
+  The use of this parameter affects the sort order of strings (for example, the order of using **ORDER BY** for execution and the order of using indexes on text columns). By default, the sorting order of the template database is used.
+
+  Value range: a valid sorting type
+
+- **LC_CTYPE [ = ] lc_ctype**
+
+  Specifies the character class used by the new database. For example, set this parameter by using **lc_ctype = 'zh_CN.gbk'**. The use of this parameter affects the classification of characters, such as uppercase letters, lowercase letters, and digits. By default, the character classification of the template database is used.
+
+  Value range: a valid character type
+
+- **DBCOMPATIBILITY [ = ] compatibility_type**
+
+  Specifies the compatible database type. The default compatible database is Oracle.
+
+  Value range: **A**, **B** and **PG**, indicating Oracle, MySQL and Postgres databases, respectively.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > - For A compatibility, the database treats empty strings as **NULL** and replaces **DATE** with **TIMESTAMP(0) WITHOUT TIME ZONE**.
+  > - When a character string is converted to an integer, if the input is invalid, the input will be converted to 0 due to B compatibility, and an error will be reported due to other compatibility issues.
+  > - For PG compatibility, CHAR and VARCHAR are counted by character. For other compatibility types, they are counted by byte. For example, for the UTF-8 character set, CHAR(3) can store three Chinese characters in PG compatibility scenarios, but can store only one Chinese character in other compatibility scenarios.
+
+- **TABLESPACE [ = ] tablespace_name**
+
+  Specifies the tablespace of the database.
+
+  Value range: an existing tablespace name
+
+- **CONNECTION LIMIT [ = ] connlimit**
+
+  Specifies the maximum number of concurrent connections that can be made to the new database.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+  >
+  > - The system administrator is not restricted by this parameter.
+  > - connlimit is calculated separately for each primary database node. Number of connections of MogDB = connlimit x Number of normal CN primary database nodes.
+
+  Value range: an integer greater than or equal to -1 The default value is **-1**, indicating that there is no limit.
+
+The restrictions on character encoding are as follows:
+
+- If the locale is set to **C** (or **POSIX**), all encoding types are allowed. For other locale settings, the character encoding must be the same as that of the locale.
+- If the character encoding mode is SQL_ASCII and the modifier is an administrator, the character encoding mode can be different from the locale setting.
+- The encoding and region settings must match the template database, except that **template0** is used as a template. This is because other databases may contain data that does not match the specified encoding, or may contain indexes whose sorting order is affected by **LC_COLLATE** and **LC_CTYPE**. Copying this data will invalidate the indexes in the new database. **template0** does not contain any data or indexes that may be affected.
+
+## Examples
+
+```sql
+-- Create users jim and tom.
+mogdb=# CREATE USER jim PASSWORD 'xxxxxxxxx';
+mogdb=# CREATE USER tom PASSWORD 'xxxxxxxxx';
+
+-- Create database music using GBK (the local encoding type is also GBK).
+mogdb=# CREATE DATABASE music ENCODING 'GBK' template = template0;
+
+-- Create database music2 and specify user jim as its owner.
+mogdb=# CREATE DATABASE music2 OWNER jim;
+
+-- Create database music3 using template template0 and specify user jim as its owner.
+mogdb=# CREATE DATABASE music3 OWNER jim TEMPLATE template0;
+
+-- Set the maximum number of connections to database music to 10.
+mogdb=# ALTER DATABASE music CONNECTION LIMIT= 10;
+
+-- Rename database music to music4.
+mogdb=# ALTER DATABASE music RENAME TO music4;
+
+-- Change the owner of database music2 to user tom.
+mogdb=# ALTER DATABASE music2 OWNER TO tom;
+
+-- Set the tablespace of database music3 to PG_DEFAULT.
+mogdb=# ALTER DATABASE music3 SET TABLESPACE PG_DEFAULT;
+
+-- Disable the default index scan on database music3.
+mogdb=# ALTER DATABASE music3 SET enable_indexscan TO off;
+
+-- Reset the enable_indexscan parameter.
+mogdb=# ALTER DATABASE music3 RESET enable_indexscan;
+
+-- Delete the database.
+mogdb=# DROP DATABASE music2;
+mogdb=# DROP DATABASE music3;
+mogdb=# DROP DATABASE music4;
+
+-- Delete the jim and tom users.
+mogdb=# DROP USER jim;
+mogdb=# DROP USER tom;
+
+-- Create a database compatible with the TD format.
+mogdb=# CREATE DATABASE td_compatible_db DBCOMPATIBILITY 'C';
+
+-- Create a database compatible with the A format.
+mogdb=# CREATE DATABASE ora_compatible_db DBCOMPATIBILITY 'A';
+
+-- Delete the databases that are compatible with the TD and A formats.
+mogdb=# DROP DATABASE td_compatible_db;
+mogdb=# DROP DATABASE ora_compatible_db;
+```
+
+## Helpful Links
+
+[ALTER DATABASE](2-ALTER-DATABASE) and [DROP DATABASE](78-DROP-DATABASE)
+
+## Suggestions
+
+- **create database**
+
+  Database cannot be created in a transaction.
+
+- **ENCODING LC_COLLATE LC_CTYPE**
+
+  If the new database Encoding, LC-Collate, or LC_Ctype does not match the template database (SQL_ASCII) (**'GBK'**, **'UTF8'**, or **'LATIN1'**), **template [=] template0** must be specified.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/45-CREATE-DATA-SOURCE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/45-CREATE-DATA-SOURCE.md
new file mode 100644
index 0000000000000000000000000000000000000000..1adf541ffac73a6ef772c6250199a39a7fe1bd14
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/45-CREATE-DATA-SOURCE.md
@@ -0,0 +1,97 @@
+---
+title: CREATE DATA SOURCE
+summary: CREATE DATA SOURCE
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE DATA SOURCE
+
+## Function
+
+**CREATE DATA SOURCE** creates an external data source, which defines the information about the database that MogDB will connect to.
+
+## Precautions
+
+- The data source name must be unique in the database and comply with the identifier naming rules. Its length cannot exceed 63 bytes. Otherwise, it will be truncated.
+- Only the system administrator or initial user has the permission to create data sources. The user who creates the object is the default owner of the object.
+- If the **password** option is displayed, ensure that the **datasource.key.cipher** and **datasource.key.rand** files exist in the `$GAUSSHOME/bin` directory of each node in MogDB. If the two files do not exist, use the **gs_guc** tool to generate them and use the **gs_ssh** tool to release them to the `$GAUSSHOME/bin` directory on each node in MogDB.
+
+## Syntax
+
+```ebnf+diagram
+CreateDataSource ::= CREATE DATA SOURCE src_name
+    [TYPE 'type_str']
+    [VERSION {'version_str' | NULL}]
+    [OPTIONS (optname 'optvalue')];
+```
+
+## Parameter Description
+
+- **src_name**
+
+  Specifies the name of the new data source, which must be unique in the database.
+
+  Value range: a string compliant with the identifier naming convention
+
+- **TYPE**
+
+  Specifies the type of the data source. This parameter can be left empty, and its default value will be used.
+
+  Value range: an empty string or a non-empty string
+
+- **VERSION**
+
+  Specifies the version number of the new data source. This parameter can be left empty or set to null.
+
+  Value range: an empty string, a non-empty string, or null
+
+- **OPTIONS**
+
+  Specifies the options of the data source. This parameter can be left empty or specified using the following keywords:
+
+  - optname
+
+    Specifies the option name.
+
+    Value range: **dsn**, **username**, **password**, and **encoding**. The value is case-insensitive.
+
+    - **dsn** corresponds to the DSN in the ODBC configuration file.
+
+    - **username**/**password** indicates the username and password for connecting to the destination database.
+
+    The user name and password entered by the user are encrypted in the MogDB background to ensure security. The key file required for encryption must be generated using the **gs_guc** tool and released to the *$GAUSSHOME***/bin** directory of each node in MogDB using the **gs_ssh** tool. The user name and password cannot contain the prefix "encryptOpt". Otherwise, they are considered as encrypted ciphertext.
+
+    - **encoding** indicates the character string encoding mode used for interaction with the destination database (including the sent SQL statements and returned data of the character type). Its validity is not checked during object creation. Whether data can be encoded and decoded depends on whether the encoding you specified can be used in the database.
+
+  - optvalue
+
+    Specifies the option value.
+
+    Value range: an empty string or a non-empty string
+
+## Examples
+
+```sql
+-- Create an empty data source that does not contain any information.
+mogdb=# CREATE DATA SOURCE ds_test1;
+
+-- Create a data source with TYPE information and VERSION being null.
+mogdb=# CREATE DATA SOURCE ds_test2 TYPE 'MPPDB' VERSION NULL;
+
+-- Create a data source that contains only OPTIONS.
+mogdb=#  CREATE DATA SOURCE ds_test3 OPTIONS (dsn 'MogDB', encoding 'utf8');
+
+-- Create a data source that contains TYPE, VERSION, and OPTIONS.
+mogdb=# CREATE DATA SOURCE ds_test4 TYPE 'unknown' VERSION '11.2.3' OPTIONS (dsn 'MogDB', username 'userid', password 'pwd@123456', encoding '');
+
+-- Delete the data source.
+mogdb=# DROP DATA SOURCE ds_test1;
+mogdb=# DROP DATA SOURCE ds_test2;
+mogdb=# DROP DATA SOURCE ds_test3;
+mogdb=# DROP DATA SOURCE ds_test4;
+```
+
+## Helpful Links
+
+[ALTER DATA SOURCE](3-ALTER-DATA-SOURCE),  [DROP DATA SOURCE](79-DROP-DATA-SOURCE)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/46-CREATE-DIRECTORY.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/46-CREATE-DIRECTORY.md
new file mode 100644
index 0000000000000000000000000000000000000000..6342390646df7fccfb40bbfecaeeb0503e814d6d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/46-CREATE-DIRECTORY.md
@@ -0,0 +1,58 @@
+---
+title: CREATE DIRECTORY
+summary: CREATE DIRECTORY
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE DIRECTORY
+
+## Function
+
+**CREATE DIRECTORY** creates a directory. The directory defines an alias for a path in the server file system and is used to store data files used by users.
+
+## Precautions
+
+- When enable_access_server_directory=off, only the initial user is allowed to create directory objects; when enable_access_server_directory=on, users with SYSADMIN permissions and users who inherit the built-in role gs_role_directory_create permissions can create directory objects.
+- By default, the user who creates a directory has the read and write permissions on the directory.
+- The default owner of a directory is the user who creates the directory.
+- A directory cannot be created for the following paths:
+  - The path contains special characters.
+  - The path is a relative path.
+  - The path is a symbolic link.
+- The following validity check is performed during directory creation:
+  - Check whether the path exists in the OS. If it does not exist, a message is displayed, indicating the potential risks.
+  - Check whether the database initial user omm has the R/W/X permissions for the OS path. If the user does not have all the permissions, a message is displayed, indicating the potential risks.
+- In MogDB, ensure that the path is the same on all the nodes. Otherwise, the path may fail to be found on some nodes when the directory is used.
+
+## Syntax
+
+```ebnf+diagram
+CreateDirectory ::= CREATE [OR REPLACE] DIRECTORY directory_name
+AS 'path_name';
+```
+
+## Parameter Description
+
+- **directory_name**
+
+  Specifies the name of a directory.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **path_name**
+
+  Specifies the OS path for which a directory is to be created.
+
+  Value range: a valid OS path
+
+## Examples
+
+```sql
+-- Create a directory.
+mogdb=# CREATE OR REPLACE DIRECTORY  dir  as '/tmp/';
+```
+
+## Helpful Links
+
+[ALTER DIRECTORY](5-ALTER-DIRECTORY)，[DROP DIRECTORY](80-DROP-DIRECTORY)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/46.1-CREATE-EXTENSION.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/46.1-CREATE-EXTENSION.md
new file mode 100644
index 0000000000000000000000000000000000000000..5227a16faaaef90e4cee4ff595f8c3a207f7f245
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/46.1-CREATE-EXTENSION.md
@@ -0,0 +1,59 @@
+---
+title: CREATE EXTENSION
+summary: CREATE EXTENSION
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# CREATE EXTENSION
+
+## Function
+
+**CREATE EXTENSION** installs an extension.
+
+## Precautions
+
+- The **CREATE EXTENSION** command installs a new extension to a database. Ensure that no extension with the same name has been installed.
+- Installing an extension means executing an extended script file that creates a new SQL entity, such as a function, data type, operator, and index-supported method.
+- Installing an extension requires the same permissions as creating its component objects. For most extensions, this means that the superuser or database owner's permissions are required. For subsequent permission checks and entities created by the extension script, the role that runs the **CREATE EXTENSION** command becomes the owner of the extension.
+
+## Syntax
+
+```ebnf+diagram
+CreateExtension ::= CREATE EXTENSION [ IF NOT EXISTS ] extension_name
+[ WITH ] [ SCHEMA schema_name ]
+[ VERSION version ]
+[ FROM old_version ]
+```
+
+## Parameter Description
+
+- **IF NOT EXISTS**
+
+  If an extension with the same name exists in the system, no error is reported. However, a message is displayed. Note that this parameter does not ensure that the existing extensions of the system are the same as those created by the script.
+
+- **extension_name**
+
+  Name of the extension to be installed.
+
+- **schema_name**
+
+  The extension instance installed in this schema, and the extended content can be reinstalled. The specified schema must exist. If it is not specified, the extended control file does not specify a schema either. In this case, the default schema is used.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **CAUTION:** Extensions are not considered to be in any schema (no restriction is posed on the name of extensions within the scope of a database), but an extension instance belongs to a schema.
+
+- **version**
+
+  Version of the extension to be installed, which can be written as an identifier or a string. The default version is specified in the extended control file.
+
+- **old_version**
+
+  If you want to upgrade the content that is not contained in the **old style** module, you must specify **FROM old_version**. This option makes **CREATE EXTENSION** run an installation script to install new content into the extension instead of creating an entity. Note that **SCHEMA** specifies the schema that includes these existing entities.
+
+## Examples
+
+Install the **hstore** extension in the current database.
+
+```sql
+CREATE EXTENSION hstore;
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/47-CREATE-FOREIGN-TABLE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/47-CREATE-FOREIGN-TABLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..0b70efdaaa748ab9f8b0a80f725bff69a3faa097
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/47-CREATE-FOREIGN-TABLE.md
@@ -0,0 +1,145 @@
+---
+title: CREATE FOREIGN TABLE
+summary: CREATE FOREIGN TABLE
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE FOREIGN TABLE
+
+## Function
+
+**CREATE FOREIGN TABLE** creates a foreign table.
+
+## Precautions
+
+- System columns (such as  **tableoid**  and  **ctid**) cannot be used in foreign tables.
+- Among them, the appearance of Private and Shares mode requires the initial user and operation and maintenance administrator authority in operation mode (operation_mode).
+
+## Syntax
+
+```ebnf+diagram
+CreateForeignTable ::= CREATE FOREIGN TABLE [ IF NOT EXISTS ] table_name ( [
+    column_name type_name [ OPTIONS ( option 'value') ] [ COLLATE collation ] [ column_constraint [ ... ] ]
+    [, ... ]
+] )
+  SERVER server_name
+[ OPTIONS ( option 'value' ) ]
+```
+
+The column_constraint can be:
+
+```ebnf+diagram
+column_constraint ::= [ CONSTRAINT constraint_name ]
+{ NOT NULL |
+  NULL |
+  DEFAULT default_expr }
+```
+
+## Parameter Description
+
+- **IF NOT EXISTS**
+
+  Sends a notice, but does not throw an error, if a table with the same name exists.
+
+- **table_name**
+
+  Specifies the name of a foreign table.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **column_name**
+
+  Specifies the name of a column in the foreign table.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **type_name**
+
+  Specifies the data type of the column.
+
+- **SERVER server_name**
+
+  Specifies the server name of the foreign table. The default value is **mot_server**.
+
+- **OPTIONS ( option 'value' [, … ] )**
+
+  Options are related to the new foreign table or the columns in the foreign table. The allowed option names and values are specified by each foreign data wrapper, and are also verified by the verification function of the foreign data wrapper. The option name must be unique (although table options and table column options can share the same name).
+
+  - Options supported by **oracle_fdw** are as follows:
+
+    - **table**
+
+        Name of a table on the Oracle server. The value must be the same as the table name recorded in the Oracle system catalog. Generally, the value consists of uppercase letters.
+
+    - **schema**
+
+        Schema (or owner) corresponding to the table. The value must be the same as the table name recorded in the Oracle system catalog. Generally, the value consists of uppercase letters.
+
+  - Options supported by **mysql_fdw** are as follows:
+
+    - **dbname**
+
+        Name of the MySQL database.
+
+    - **table_name**
+
+        Name of a table in the MySQL database.
+
+  - Options supported by **postgres_fdw** are as follows:
+
+    - **schema_name**
+
+        Schema name of a remote server. If this option is not specified, the schema name of the foreign table is used as the schema name of the remote server.
+
+    - **table_name**
+
+        Table name of a remote server. If this option is not specified, the name of the foreign table is used as the table name of the remote server.
+
+    - **column_name**
+
+        Column name of a table on a remote server. If this option is not specified, the column name of the foreign table is used as the column name of a table on a remote server.
+
+  - Options supported by **file_fdw** are as follows:
+
+    - filename
+
+        File to be read. This parameter is mandatory and must be an absolute path.
+
+    - format
+
+        File format of the remote server, which is the same as the **FORMAT** option in the **COPY** statement. The value can be **text**, **csv**, **binary**, or **fixed**.
+
+    - header
+
+        Specifies whether a specified file has a header, which is the same as the **HEADER** option of the **COPY** statement.
+
+    - delimiter
+
+        File delimiter, which is the same as the **DELIMITER** option of the **COPY** statement.
+
+    - quote
+
+        Quote character of a file, which is the same as the **QUOTE** option of the **COPY** statement.
+
+    - escape
+
+        Escape character of a file, which is the same as the **ESCAPE** option of the **COPY** statement.
+
+    - null
+
+        Null string of a file, which is the same as the **NULL** option of the **COPY** statement.
+
+    - encoding
+
+        Encoding of a file, which is the same as the **ENCODING** option of the **COPY** statement.
+
+    - force_not_null
+
+        This is a Boolean option. If it is true, the value of the declared field cannot be an empty string. This option is the same as the **FORCE_NOT_NULL** option of the **COPY** statement.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** For details about how to use **file_fdw**, see [file_fdw](file_fdw).
+
+## Helpful Links
+
+[ALTER FOREIGN TABLE](6-ALTER-FOREIGN-TABLE) and [DROP FOREIGN TABLE](81-DROP-FOREIGN-TABLE)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/48-CREATE-FUNCTION.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/48-CREATE-FUNCTION.md
new file mode 100644
index 0000000000000000000000000000000000000000..a080c18d5b4615a4c303cffc135bf13fef033c53
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/48-CREATE-FUNCTION.md
@@ -0,0 +1,318 @@
+---
+title: CREATE FUNCTION
+summary: CREATE FUNCTION
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE FUNCTION
+
+## Function
+
+**CREATE FUNCTION** creates a function.
+
+## Precautions
+
+- If the parameters or return values of a function have precision, the precision is not checked.
+- When creating a function, you are advised to explicitly specify the schemas of tables in the function definition. Otherwise, the function may fail to be executed.
+- **current_schema** and **search_path** specified by **SET** during function creation are invalid. **search_path** and **current_schema** before and after function execution should be the same.
+- If a function has output parameters, the **SELECT** statement uses the default values of the output parameters when calling the function. When the **CALL** statement calls the function, it requires that the output parameters must be specified. When the **CALL** statement calls an overloaded **PACKAGE** function, it can use the default values of the output parameters. For details, see examples in [CALL](34-CALL).
+- Only the functions compatible with PostgreSQL or those with the **PACKAGE** attribute can be overloaded. After **REPLACE** is specified, a new function is created instead of replacing a function if the number of parameters, parameter type, or return value is different.
+- You can use the **SELECT** statement to specify different parameters using identical functions, but cannot use the **CALL** statement to call identical functions without the **PACKAGE** attribute.
+- When you create a function, you cannot insert other agg functions out of the avg function or other functions.
+- By default, the permissions to execute new functions are granted to **PUBLIC**. For details, see [GRANT](108-GRANT). You can revoke the default execution permissions from **PUBLIC** and grant them to other users as needed. To avoid the time window during which new functions can be accessed by all users, create functions in transactions and set function execution permissions.
+- When calling functions without parameters inside another function, you can omit brackets and call functions using their names directly.
+- Oracle-compatible functions support viewing, exporting, and importing parameter comments.
+- Oracle-compatible functions support viewing, exporting, and importing comments between IS/AS and plsql_body.
+
+## Syntax
+
+- Syntax (compatible with PostgreSQL) for creating a customized function:
+
+  ```ebnf+diagram
+  CreateFunction ::= CREATE [ OR REPLACE  ] FUNCTION function_name
+        [ ( [  { argname [ argmode  ] argtype [  { DEFAULT  | ':='  | =  } expression  ]}  [, ...]  ] ) ]
+        [ RETURNS rettype [ DETERMINISTIC  ]  | RETURNS TABLE (  { column_name column_type  }  [, '...'] )]
+        LANGUAGE lang_name
+        [
+           {IMMUTABLE  | STABLE  | VOLATILE }
+      | {SHIPPABLE | NOT SHIPPABLE}
+            | WINDOW
+            | [ NOT  ] LEAKPROOF
+            | {CALLED ON NULL INPUT  | RETURNS NULL ON NULL INPUT | STRICT }
+            | {[ EXTERNAL  ] SECURITY INVOKER | [ EXTERNAL  ] SECURITY DEFINER | AUTHID DEFINER  | AUTHID CURRENT_USER}
+            | {fenced | not fenced}
+            | {PACKAGE}
+            | COST execution_cost
+            | ROWS result_rows
+            | SET configuration_parameter { {TO | =} value | FROM CURRENT }
+
+         ]['...']
+        {
+            AS 'definition'
+        }
+  ```
+
+- O syntax of creating a customized function:
+
+  ```ebnf+diagram
+  CreateFunction ::= CREATE [ OR REPLACE  ] FUNCTION function_name
+        ( [  { argname [ argmode  ] argtype [  { DEFAULT | ':=' | =  } expression  ] }  [, '...']  ] )
+        RETURN rettype [ DETERMINISTIC  ]
+
+  [
+
+            {IMMUTABLE  | STABLE  | VOLATILE }
+            | {SHIPPABLE | NOT SHIPPABLE}
+            | {PACKAGE}
+            | {FENCED | NOT FENCED}
+            | [ NOT  ] LEAKPROOF
+            | {CALLED ON NULL INPUT | RETURNS NULL ON NULL INPUT | STRICT }
+            | {[ EXTERNAL  ] SECURITY INVOKER  | [ EXTERNAL  ] SECURITY DEFINER |
+    AUTHID DEFINER | AUTHID CURRENT_USER
+    }
+
+            |{ COST execution_cost  }
+            | ROWS result_rows
+            | SET configuration_parameter { {TO | =} value
+            | FROM CURRENT}
+
+        ]
+
+  ['...']
+
+        {
+          IS  | AS
+    } plsql_body
+  ```
+
+## Parameter Description
+
+- **function_name**
+
+  Specifies the name of the function to create (optionally schema-qualified).
+
+  Value range: a string. It must comply with the naming convention, and can contain a maximum of 63 characters. If the value contains more than 63 characters, the database truncates it and retains the first 63 characters as the function name.
+
+- **argname**
+
+  Specifies the parameter name of the function.
+
+  Value range: a string. It must comply with the naming convention, and can contain a maximum of 63 characters. If the value contains more than 63 characters, the database truncates it and retains the first 63 characters as the function parameter name.
+
+- **argmode**
+
+  Specifies the parameter mode of the function.
+
+  Value range: **IN**, **OUT**, **INOUT**, and **VARIADIC**. The default value is **IN**. The parameters of **OUT** and **INOUT** cannot be used in the function definition of **RETURNS TABLE**.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** **VARIADIC** specifies parameters of the array type.
+
+- **argtype**
+
+  Specifies the data type of a function parameter. **%TYPE**  or  **%ROWTYPE**  can be used to indirectly reference a variable or table type. For details, see  [Variable Definition Statements](1-6-basic-statements).
+
+- **expression**
+
+  Specifies the default expression of a parameter.
+
+- **rettype**
+
+  Specifies the return data type.
+
+  When there is **OUT** or **INOUT** parameter, the **RETURNS** clause can be omitted. If the clause exists, the result type of the clause must be the same as that of the output parameter. If there are multiple output parameters, the result type of the clause is **RECORD**. Otherwise, the result type of the clause is the same as that of a single output parameter.
+
+  The **SETOF** modifier indicates that the function will return a set of items, rather than a single item.
+
+  Same as  **argtype**,  **%TYPE**  or  **%ROWTYPE**  can also be used to indirectly reference types.
+
+- **column_name**
+
+  Specifies the column name.
+
+- **column_type**
+
+  Specifies the column type.
+
+- **definition**
+
+  Specifies a string constant defining a function. Its meaning depends on the language. It can be an internal function name, a path pointing to a target file, a SQL query, or text in a procedural language.
+
+- **DETERMINISTIC**
+
+  Specifies an interface compatible with the SQL syntax. You are not advised to use it.
+
+- **LANGUAGE lang_name**
+
+  Specifies the name of the language that is used to implement the function. It can be **SQL**, **internal**, or the name of a customized process language. To ensure downward compatibility, the name can use single quotation marks. Contents in single quotation marks must be capitalized.
+
+- **WINDOW**
+
+  Indicates that this function is a window function. The **WINDOW** attribute cannot be changed when replacing an existing function definition.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** For a customized window function, the value of **LANGUAGE** can only be **internal**, and the referenced internal function must be a window function.
+
+- **IMMUTABLE**
+
+  Specifies that the function always returns the same result if the parameter values are the same.
+
+- **STABLE**
+
+  Specifies that the function cannot modify the database, and that within a single table scan it will consistently return the same result for the same parameter value, but its result varies by SQL statements.
+
+- **VOLATILE**
+
+  Specifies that the function value can change in a single table scan and no optimization is performed.
+
+- **SHIPPABLE**|**NOT SHIPPABLE**
+
+  Specifies whether the function can be pushed down for execution. This port is reserved and is not recommended.
+
+- **FENCED**|**NOT FENCED**
+
+  Specifies whether the user-defined C function is executed in fenced or not-fenced mode. This port is reserved and is not recommended.
+
+- **PACKAGE**
+
+  Specifies whether the function can be overloaded. PostgreSQL-style functions can be overloaded, and this parameter is designed for functions of other styles.
+
+  - All PACKAGE and non-PACKAGE functions cannot be overloaded or replaced.
+  - PACKAGE functions do not support parameters of the VARIADIC type.
+  - The **PACKAGE** attribute of functions cannot be modified.
+
+- **LEAKPROOF**
+
+  Specifies that the function has no side effects. **LEAKPROOF** can be set only by the system administrator.
+
+- **CALLED ON NULL INPUT**
+
+  Declares that some parameters of the function can be invoked in normal mode if the parameter values are null. This parameter can be omitted.
+
+- **RETURNS NULL ON NULL INPUT**
+
+  **STRICT**
+
+  Specifies that the function always returns null whenever any of its parameters is null. If this parameter is specified, the function is not executed when there are null parameters; instead a null result is returned automatically.
+
+  **RETURNS NULL ON NULL INPUT** and **STRICT** have the same functions.
+
+- **EXTERNAL**
+
+  The keyword **EXTERNAL** is allowed for SQL conformance, but it is optional since, unlike in SQL, this feature applies to all functions not only external ones.
+
+- **SECURITY INVOKER**
+
+  **AUTHID CURRENT_USER**
+
+  Specifies that the function will be executed with the permissions of the user who invokes it. This parameter can be omitted.
+
+  **SECURITY INVOKER** and **AUTHID CURRENT_USER** have the same functions.
+
+- **SECURITY DEFINER**
+
+  **AUTHID DEFINER**
+
+  Specifies that the function will be executed with the permissions of the user who created it.
+
+  **AUTHID DEFINER** and **SECURITY DEFINER** have the same functions.
+
+- **COST execution_cost**
+
+  Estimates the execution cost of a function.
+
+  The unit of **execution_cost** is **cpu_operator_cost**.
+
+  Value range: a positive integer
+
+- **ROWS result_rows**
+
+  Estimates the number of rows returned by the function. This is only allowed when the function is declared to return a set.
+
+  Value range: a positive number. The default value is **1000**.
+
+- **configuration_parameter**
+
+  - **value**
+
+    Sets a specified database session parameter to a specified value. If the value is **DEFAULT** or **RESET**, the default setting is used in the new session. **OFF** closes the setting.
+
+    Value range: a string
+
+    - DEFAULT
+    - OFF
+    - RESET
+
+    Specifies the default value.
+
+  - **from current**
+
+    Uses the value of **configuration_parameter** of the current session.
+
+- **plsql_body**
+
+  Specifies the PL/SQL stored procedure body.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** When a user is created in the function body, the plaintext password is recorded in the log. You are not advised to do it.
+
+## Examples
+
+```sql
+-- Define a function as SQL query.
+mogdb=# CREATE FUNCTION func_add_sql(integer, integer) RETURNS integer
+    AS 'select $1 + $2;'
+    LANGUAGE SQL
+    IMMUTABLE
+    RETURNS NULL ON NULL INPUT;
+
+-- Add an integer by parameter name using PL/pgSQL.
+mogdb=# CREATE OR REPLACE FUNCTION func_increment_plsql(i integer) RETURNS integer AS $$
+        BEGIN
+                RETURN i + 1;
+        END;
+$$ LANGUAGE plpgsql;
+
+-- Return the RECORD type.
+mogdb=# CREATE OR REPLACE FUNCTION func_increment_sql(i int, out result_1 bigint, out result_2 bigint)
+returns SETOF RECORD
+as $$
+begin
+    result_1 = i + 1;
+    result_2 = i * 10;
+return next;
+end;
+$$language plpgsql;
+
+-- Return a record containing multiple output parameters.
+mogdb=# CREATE FUNCTION func_dup_sql(in int, out f1 int, out f2 text)
+    AS $$ SELECT $1, CAST($1 AS text) || ' is text' $$
+    LANGUAGE SQL;
+
+mogdb=# SELECT * FROM func_dup_sql(42);
+
+-- Compute the sum of two integers and returning the result (if the input is null, the returned result is null):
+mogdb=# CREATE FUNCTION func_add_sql2(num1 integer, num2 integer) RETURN integer
+AS
+BEGIN
+RETURN num1 + num2;
+END;
+/
+-- Alter the execution rule of function func_add_sql2 to IMMUTABLE (that is, the same result is returned if the parameter remains unchanged).
+mogdb=# ALTER FUNCTION func_add_sql2(INTEGER, INTEGER) IMMUTABLE;
+
+-- Rename the func_add_sql2 function as add_two_number:
+mogdb=# ALTER FUNCTION func_add_sql2(INTEGER, INTEGER) RENAME TO add_two_number;
+
+-- Change the owner of function add_two_number to omm.
+mogdb=# ALTER FUNCTION add_two_number(INTEGER, INTEGER) OWNER TO omm;
+
+-- Delete the function.
+mogdb=# DROP FUNCTION add_two_number;
+mogdb=# DROP FUNCTION func_increment_sql;
+mogdb=# DROP FUNCTION func_dup_sql;
+mogdb=# DROP FUNCTION func_increment_plsql;
+mogdb=# DROP FUNCTION func_add_sql;
+```
+
+## Helpful Links
+
+[ALTER FUNCTION](7-ALTER-FUNCTION)，[DROP FUNCTION](82-DROP-FUNCTION)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/49-CREATE-GROUP.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/49-CREATE-GROUP.md
new file mode 100644
index 0000000000000000000000000000000000000000..80edc1cdbcfa3fbd6c0da6e38f7ac4a948c48239
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/49-CREATE-GROUP.md
@@ -0,0 +1,62 @@
+---
+title: CREATE GROUP
+summary: CREATE GROUP
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE GROUP
+
+## Function
+
+**CREATE GROUP** creates a user group.
+
+## Precautions
+
+**CREATE GROUP** is an alias for **CREATE ROLE**, and it is not a standard SQL syntax and not recommended. Users can use **CREATE ROLE** directly.
+
+## Syntax
+
+```ebnf+diagram
+CreateGroup ::= CREATE GROUP group_name [ [ WITH ] option [ ... ] ] [ ENCRYPTED | UNENCRYPTED ] { PASSWORD | IDENTIFIED BY } { 'password' [ EXPIRED ] | DISABLE };
+```
+
+The syntax of the **option** clause is as follows:
+
+```ebnf+diagram
+option ::= {SYSADMIN | NOSYSADMIN}
+    | {AUDITADMIN | NOAUDITADMIN}
+    | {CREATEDB | NOCREATEDB}
+    | {USEFT | NOUSEFT}
+    | {CREATEROLE | NOCREATEROLE}
+    | {INHERIT | NOINHERIT}
+    | {LOGIN | NOLOGIN}
+    | {REPLICATION | NOREPLICATION}
+    | {INDEPENDENT | NOINDEPENDENT}
+    | {VCADMIN | NOVCADMIN}
+    | CONNECTION LIMIT connlimit
+    | VALID BEGIN 'timestamp'
+    | VALID UNTIL 'timestamp'
+    | RESOURCE POOL 'respool'
+    | PERM SPACE 'spacelimit'
+    | TEMP SPACE 'tmpspacelimit'
+    | SPILL SPACE 'spillspacelimit'
+    | IN ROLE role_name [, ...]
+    | IN GROUP role_name [, ...]
+    | ROLE role_name [, ...]
+    | ADMIN rol e_name [, ...]
+    | USER role_name [, ...]
+    | SYSID uid
+    | DEFAULT TABLESPACE tablespace_name
+    | PROFILE DEFAULT
+    | PROFILE profile_name
+    | PGUSER
+```
+
+## Parameter Description
+
+See **Parameter Description** in [CREATE ROLE](54-CREATE-ROLE).
+
+## Helpful Links
+
+[ALTER GROUP](8-ALTER-GROUP),  [DROP GROUP](83-DROP-GROUP), and  [CREATE ROLE](54-CREATE-ROLE)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/49.1-CREATE-INCREMENTAL-MATERIALIZED-VIEW.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/49.1-CREATE-INCREMENTAL-MATERIALIZED-VIEW.md
new file mode 100644
index 0000000000000000000000000000000000000000..25e843c1b6ca1a788aeb621581445c2d3aec53b1
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/49.1-CREATE-INCREMENTAL-MATERIALIZED-VIEW.md
@@ -0,0 +1,71 @@
+---
+title: CREATE INCREMENTAL MATERIALIZED VIEW
+summary: CREATE INCREMENTAL MATERIALIZED VIEW
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# CREATE INCREMENTAL MATERIALIZED VIEW
+
+## Function
+
+**CREATE INCREMENTAL MATERIALIZED VIEW**  creates an incremental materialized view, and you can refresh the data of the materialized view by using  **REFRESH MATERIALIZED VIEW**  (full refresh) and  **REFRESH INCREMENTAL MATERIALIZED VIEW**  (incremental refresh).
+
+**CREATE INCREMENTAL MATERIALIZED VIEW**  is similar to  **CREATE TABLE AS**, but it remembers the query used to initialize the view, so it can refresh data later. A materialized view has many attributes that are the same as those of a table, but does not support temporary materialized views.
+
+## Precautions
+
+- Incremental materialized views cannot be created on temporary tables or global temporary tables.
+- Incremental materialized views support only simple filter queries and UNION ALL queries of base tables.
+- Distribution columns cannot be specified when an incremental MV is created.
+- After an incremental materialized view is created, most DDL operations in the base table are no longer supported.
+- IUD operations cannot be performed on incremental materialized views.
+- After an incremental materialized view is created, you need to run the  **REFRESH**  command to synchronize the materialized view with the base table when the base table data changes.
+
+## Syntax
+
+```ebnf+diagram
+CreateIncrementalMaterializedView ::= CREATE INCREMENTAL MATERIALIZED VIEW mv_name
+    [ (column_name [, ...] ) ]
+    [ TABLESPACE tablespace_name ]
+    AS query;
+```
+
+## Parameter Description
+
+- **mv_name**
+
+  Name (optionally schema-qualified) of the materialized view to be created.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **column_name**
+
+  Column name in the new materialized view. The materialized view supports specified columns. The number of specified columns must be the same as the number of columns in the result of the subsequent query statement. If no column name is provided, the column name is obtained from the output column name of the query.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **TABLESPACE tablespace_name**
+
+  Tablespace to which the new materialized view belongs. If not specified, the default tablespace is used.
+
+- **AS query**
+
+  **SELECT**, **TABLE**, or **VALUES** command This query will be run in a security-constrained operation.
+
+## Examples
+
+```sql
+-- Create an ordinary table.
+mogdb=# CREATE TABLE my_table (c1 int, c2 int);
+-- Create an incremental materialized view.
+mogdb=# CREATE INCREMENTAL MATERIALIZED VIEW my_imv AS SELECT * FROM my_table;
+-- Write data to the base table.
+mogdb=# INSERT INTO my_table VALUES(1,1),(2,2);
+-- Incrementally refresh the incremental materialized view my_imv.
+mogdb=# REFRESH INCREMENTAL MATERIALIZED VIEW my_imv;
+```
+
+## Helpful Links
+
+[ALTER MATERIALIZED VIEW](11-ALTER-MATERIALIZED-VIEW)，  [CREATE MATERIALIZED VIEW](51-CREATE-MATERIALIZED-VIEW)，[CREATE TABLE](60-CREATE-TABLE)，  [DROP MATERIALIZED VIEW](85-DROP-MATERIALIZED-VIEW)，[REFRESH INCREMENTAL MATERIALIZED VIEW](115.1-REFRESH-INCREMENTAL-MATERIALIZED-VIEW)  ，[REFRESH MATERIALIZED VIEW](116-REFRESH-MATERIALIZED-VIEW)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/5-ALTER-DIRECTORY.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/5-ALTER-DIRECTORY.md
new file mode 100644
index 0000000000000000000000000000000000000000..0aa53dca7e4cce8697150ffe860cd56b329be9a5
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/5-ALTER-DIRECTORY.md
@@ -0,0 +1,47 @@
+---
+title: ALTER DIRECTORY
+summary: ALTER DIRECTORY
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER DIRECTORY
+
+## Function
+
+**ALTER DIRECTORY** modifies a directory.
+
+## Precautions
+
+- Currently, only the directory owner can be changed.
+- When enable_access_server_directory=off, only the initial user is allowed to modify the owner of the directory; when enable_access_server_directory=on, users with SYSADMIN authority and the owner of the directory object can modify the directory, and the user is required to be a member of the new owner.
+
+## Syntax
+
+```ebnf+diagram
+AlterDirectory ::= ALTER DIRECTORY directory_name
+    OWNER TO new_owner;
+```
+
+## Parameter Description
+
+**directory_name**
+
+Specifies the name of a directory to be modified. The value must be an existing directory name.
+
+## Examples
+
+```sql
+-- Create a directory.
+mogdb=# CREATE OR REPLACE DIRECTORY  dir  as '/tmp/';
+
+-- Change the owner of the directory.
+mogdb=# ALTER DIRECTORY dir OWNER TO system;
+
+-- Delete a directory.
+mogdb=# DROP DIRECTORY dir;
+```
+
+## Helpful Links
+
+[CREATE DIRECTORY](46-CREATE-DIRECTORY)，[DROP DIRECTORY](80-DROP-DIRECTORY)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/5.1-ALTER-EXTENSION.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/5.1-ALTER-EXTENSION.md
new file mode 100644
index 0000000000000000000000000000000000000000..ff3428cfb8320cc68d10a85e48ff8defe234f398
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/5.1-ALTER-EXTENSION.md
@@ -0,0 +1,155 @@
+---
+title: ALTER EXTENSION
+summary: ALTER EXTENSION
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# ALTER EXTENSION
+
+## Function
+
+ALTER EXTENSION modifies the plug-in extension.
+
+## Precautions
+
+ALTER EXTENSION modifies the definition of an installed extension. Methods are as follows:
+
+- UPDATE
+
+  The extension is updated to a new version. The extension must be applicable to an update script (or a series of scripts) so that the current installation version can be modified to a required version.
+
+- SET SCHEMA
+
+  The extended object is moved to another schema. This extension must be relocatable to make the command successful.
+
+- ADD member_object
+
+  An existing object is added to the extension. This is mainly useful for extension update scripts. This object is then treated as a member of the extension. Obviously, the object can only be canceled by canceling the extension.
+
+- DROP member_object
+
+  A member object is removed from the extension. This method is useful in extension update scripts. The object is not canceled, but is simply separated from the extension.
+
+  You must have an extension before using ALTER EXTENSION. You must have the permission on adding or deleting an object before using the ADD or DROP statement.
+
+## Syntax
+
+```ebnf+diagram
+AlterExtension ::= ALTER EXTENSION name UPDATE [ TO new_version ];
+```
+
+```ebnf+diagram
+AlterExtension ::= ALTER EXTENSION name SET SCHEMA new_schema;
+```
+
+```ebnf+diagram
+AlterExtension ::= ALTER EXTENSION name ADD member_object;
+```
+
+```ebnf+diagram
+AlterExtension ::= ALTER EXTENSION name DROP member_object;
+```
+
+where member_object is:
+
+```ebnf+diagram
+member_object ::= AGGREGATE agg_name (agg_type [, ...] ) |
+  CAST (source_type AS target_type) |
+  COLLATION object_name |
+  CONVERSION object_name |
+  DOMAIN object_name |
+  EVENT TRIGGER object_name |
+  FOREIGN DATA WRAPPER object_name |
+  FOREIGN TABLE object_name |
+  FUNCTION function_name ( [ [ argmode ] [ argname ] argtype [, ...] ] ) |
+  MATERIALIZED VIEW object_name |
+  OPERATOR operator_name (left_type, right_type) |
+  OPERATOR CLASS object_name USING index_method |
+  OPERATOR FAMILY object_name USING index_method |
+  [ PROCEDURAL ] LANGUAGE object_name |
+  SCHEMA object_name |
+  SEQUENCE object_name |
+  SERVER object_name |
+  TABLE object_name |
+  TEXT SEARCH CONFIGURATION object_name |
+  TEXT SEARCH DICTIONARY object_name |
+  TEXT SEARCH PARSER object_name |
+  TEXT SEARCH TEMPLATE object_name |
+  TYPE object_name |
+  VIEW object_name
+```
+
+## Parameter Description
+
+- **name**
+
+  Name of an installed extension.
+
+- **new_version**
+
+  New version of the extension, which can be overridden by identifiers and string literals. If a new version of the extension is not specified, ALTER EXTENSION UPDATE updates to the default version shown in the extension's control file.
+
+- **new_schema**
+
+  New schema of the extension.
+
+- **object_name**
+
+  **agg_name**
+
+  **function_name**
+
+  **operator_name**
+
+  Names of objects that are added or removed from the extension, including names of tables, aggregations, domains, external linked lists, functions, operators, operator classes, operator families, sequences, text search objects, types, and views that can be schema-qualified.
+
+- **agg_type**
+
+  Input data type of the aggregate function. To reference a zero-parameter aggregate function, use  **\***  to replace the input data type list.
+
+- **source_type**
+
+  Name of the source data type to be forcibly converted.
+
+- **target_type**
+
+  Name of the target data type to be forcibly converted.
+
+- **argmode**
+
+  Model of the function parameter. The value can be  **IN**,  **OUT**,  **INOUT**, or  **VARIADIC**. The default value is  **IN**. ALTER EXTENSION does not relate to the  **OUT**  parameter, because you only need to enter parameters to confirm the consistency of functions. Therefore, the  **IN**,  **INOUT**, and  **VARIADIC**  parameters are enough.
+
+- **argname**
+
+  Name of a function parameter. ALTER EXTENSION does not relate to the parameter name. Only the parameter data type is required to confirm the consistency of the function.
+
+- **argtype**
+
+  Data type (optionally schema-qualified) of a function parameter.
+
+- **left_type**
+
+  **right_type**
+
+  Data type (optionally schema-qualified) of an operator parameter.  **NONE**  is written for a missing parameter of a prefix or suffix operator.
+
+## Example
+
+Update the hstore extension to version 2.0.
+
+```sql
+ALTER EXTENSION hstore UPDATE TO '2.0';
+```
+
+Run the following command to update the hstore extension mode to utils.
+
+```sql
+ALTER EXTENSION hstore SET SCHEMA utils;
+```
+
+Add an existing function for hstore extension.
+
+```sql
+ALTER EXTENSION hstore ADD FUNCTION populate_record(anyelement, hstore);
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/50-CREATE-INDEX.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/50-CREATE-INDEX.md
new file mode 100644
index 0000000000000000000000000000000000000000..c1cd6b1b1ed65512aae4161aae360ec33e41ecfd
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/50-CREATE-INDEX.md
@@ -0,0 +1,356 @@
+---
+title: CREATE INDEX
+summary: CREATE INDEX
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE INDEX
+
+## Function
+
+**CREATE INDEX**  defines a new index.
+
+Indexes are primarily used to enhance database performance (though inappropriate use can result in database performance deterioration). You are advised to create indexes on:
+
+- Columns that are often queried
+- Join conditions. For a query on joined columns, you are advised to create a composite index on the columns, For example, for  **select \* from t1 join t2 on t1.a=t2.a and t1.b=t2.b**, you can create a composite index on columns  **a**  and  **b**  in table  **t1**.
+- Columns having filter criteria (especially scope criteria) of a **where** clause
+- Columns that appear after **order by**, **group by**, and **distinct**
+
+Partitioned tables do not support concurrent index creation and partial index creation.
+
+## Precautions
+
+- Indexes consume storage and computing resources. Creating too many indexes has negative impact on database performance (especially the performance of data import. Therefore, you are advised to import the data before creating indexes). Therefore, create indexes only when they are necessary.
+- All functions and operators used in an index definition must be immutable, that is, their results must depend only on their parameters and never on any outside influence (such as the contents of another table or the current time). This restriction ensures that the behavior of the index is well-defined. To use a customized function in an index expression or **WHERE** clause, remember to mark the function **immutable** when you create it.
+- Partitioned table indexes are classified into LOCAL indexes and GLOBAL indexes. A LOCAL index binds to a specific partition, and a GLOBAL index corresponds to the entire partitioned table.
+- If the two indexes are used, you cannot create expression and partial indexes. If the PSORT index is used, you cannot create unique indexes. If the B-tree index is used, you can create unique indexes.
+- Column-store tables support GIN indexes, rather than partial indexes and unique indexes. If GIN indexes are used, you can create expression indexes. However, an expression in this situation cannot contain empty splitters, empty columns, or multiple columns.
+- Currently, only row-store table indexes, temporary table indexes, and local indexes of partitioned tables can be used as hash indexes. Multi-column indexes are not supported.
+
+## Syntax
+
+- Create an index on a table.
+
+  ```ebnf+diagram
+  CreateIndex ::= CREATE [ UNIQUE ] INDEX [ CONCURRENTLY ] [ [schema_name'.']index_name ] ON table_name [ USING method ]
+        ({ { column_name | ( expression ) } [ COLLATE collation ] [ opclass ] [ ASC | DESC ] [ NULLS { FIRST | LAST } ] }[, ...] )
+        [ WITH ( {storage_parameter = value} [, ... ] ) ]
+        [ TABLESPACE tablespace_name ]
+        [ WHERE predicate ];
+  ```
+
+- Create an index on a partitioned table.
+
+  ```ebnf+diagram
+  CreateIndex ::= CREATE [ UNIQUE ] INDEX [ [schema_name'.']index_name ] ON table_name [ USING method ]
+      ( {{ column_name | ( expression ) } [ COLLATE collation ] [ opclass ] [ ASC | DESC ] [ NULLS LAST ] }[, ...] )
+      [ LOCAL [ ( { PARTITION index_partition_name [ TABLESPACE index_partition_tablespace ] } [, ...] ) ] | GLOBAL ]
+      [ WITH ( { storage_parameter = value } [, ...] ) ]
+      [ TABLESPACE tablespace_name ];
+  ```
+
+## Parameter Description
+
+- **UNIQUE**
+
+  Creates a unique index. In this way, the system checks whether new values are unique in the index column. Attempts to insert or update data which would result in duplicate entries will generate an error.
+
+  Currently, only the B-tree index supports unique indexes.
+
+- **CONCURRENTLY** <a id = 'CONCURRENTLY'> </a>
+
+  Create an index (with ShareUpdateExclusiveLock) in non-blocking DML mode. A normal **CREATE INDEX** acquires exclusive lock on the table on which the index depends, blocking other accesses until the index drop can be completed. If this keyword is specified, DML is not blocked during the creation.
+
+  - This option can only specify a name of one index.
+  - The **CREATE INDEX** statement can be run within a transaction, but **CREATE INDEX CONCURRENTLY** cannot.
+  - Column-store tables, partitioned tables, and temporary tables do not support  **CREATE INDEX CONCURRENTLY**.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > - This keyword is specified when an index is created. The entire table needs to be scanned twice and built. When the table is scanned for the first time, an index is created and the read and write operations are not blocked. During the second scan, changes that have occurred since the first scan are merged and updated.
+  > - The table needs to be scanned and built twice, and all existing transactions that may modify the table must be completed. This means that the creation of the index takes a longer time than normal. In addition, the CPU and I/O consumption also affects other services.
+  > - If an index build fails, it leaves an "unusable" index. This index is ignored by the query, but it still consumes the update overhead. In this case, you are advised to delete the index and try **CREATE INDEX CONCURRENTLY** again.
+  > - After the second scan, index creation must wait for any transaction that holds a snapshot earlier than the snapshot taken by the second scan to terminate. In addition, the ShareUpdateExclusiveLock (level 4) added during index creation conflicts with a lock whose level is greater than or equal to 4. Therefore, when such an index is created, the system is prone to hang or deadlock. For example:
+  > - If two sessions create an index concurrently for the same table, a deadlock occurs.
+  > - If a session creates an index concurrently for a table and another session drops a table, a deadlock occurs.
+  > - There are three sessions. Session 1 locks table **a** and does not commit it. Session 2 creates an index concurrently for table **b**. Session 3 writes data to table **a**. Before the transaction of session 1 is committed, session 2 is blocked.
+  > - The transaction isolation level is set to repeatable read (read committed by default). Two sessions are started. Session 1 writes data to table **a** and does not commit it. Session 2 creates an index concurrently for table **b**. Before the transaction of session 1 is committed, session 2 is blocked.
+
+- **schema_name**
+
+  Specifies the schema name.
+
+  Value range: an existing schema name
+
+- **index_name**
+
+  Specifies the name of the index to be created. The schema of the index is the same as that of the table.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **table_name**
+
+  Specifies the name of the table to be indexed (optionally schema-qualified).
+
+  Value range: an existing table name
+
+- **USING method**
+
+  Specifies the name of the index method to be used.
+
+  Value range:
+
+  - **btree**: B-tree indexes store key values of data in a B+ tree structure. This structure helps users to quickly search for indexes. B-tree indexes support comparison queries with ranges specified.
+  - **hash**: Hash indexes use hash functions to hash index keywords. Only simple equivalence comparison can be processed. This value is applicable to scenarios where index values are long.
+  - **gin**: GIN indexes are reverse indexes and can process values that contain multiple keys (for example, arrays).
+  - **gist**: GiST indexes are suitable for the set data type and multidimensional data types, such as geometric and geographic data types. The following data types are supported: box, point, poly, circle, tsvector, tsquery, and range.
+  - **Psort**: psort index. It is used to perform partial sort on column-store tables.
+  - **ubtree**: Multi-version B-tree index used only for Ustore tables. The index page contains transaction information and can be recycled.
+
+  Row-store tables (Astore storage engine) support the following index types:  **btree**  (default),  **hash**,  **gin**, and  **gist**. Row-store tables (Ustore storage engine) support the following index type:  **ubtree**. Column-store tables support the following index types:  **Psort**  (default),  **btree**, and  **gin**.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** Column-store tables support GIN indexes only for the tsvector type. That is, the input parameter for creating a column-store GIN index must be the return value of the **to_tsvector** function. This method is commonly used for GIN indexes.
+
+- **column_name**
+
+  Specifies the name of the column on which an index is to be created.
+
+  Multiple columns can be specified if the index method supports multi-column indexes. A global index supports a maximum of 31 columns, and other indexes support a maximum of 32 columns.
+
+- **expression**
+
+  Specifies an expression based on one or more columns of the table. The expression usually must be written with surrounding parentheses, as shown in the syntax. However, the parentheses can be omitted if the expression has the form of a function call.
+
+  Expression can be used to obtain fast access to data based on some transformation of the basic data. For example, an index computed on **upper(col)** would allow the clause **WHERE upper(col) = 'JIM'** to use an index.
+
+  If an expression contains **IS NULL**, the index for this expression is invalid. In this case, you are advised to create a partial index.
+
+- **COLLATE collation**
+
+  Assigns a collation to the column (which must be of a collatable data type). If no collation is specified, the default collation is used. You can run the  **select \* from pg_collation**  command to query collation rules from the  **pg_collation**  system catalog. The default collation rule is the row starting with  **default**  in the query result.
+
+- **opclass**
+
+  Specifies the name of an operator class. An operator class can be specified for each column of an index. The operator class identifies the operators to be used by the index for that column. For example, a B-tree index on the type int4 would use the **int4_ops** class; this operator class includes comparison functions for values of type int4. In practice, the default operator class for the column's data type is sufficient. The operator class applies to data with multiple sorts. For example, users might want to sort a complex-number data type either by absolute value or by real part. They could do this by defining two operator classes for the data type and then selecting the proper class when making an index.
+
+- **ASC**
+
+  Specifies an ascending (default) sort order.
+
+- **DESC**
+
+  Specifies a descending sort order.
+
+- **NULLS FIRST**
+
+  Specifies that null values appear before non-null values in the sort ordering. This is the default when **DESC** is specified.
+
+- **NULLS LAST**
+
+  Specifies that null values appear after non-null values in the sort ordering. This is the default when **DESC** is not specified.
+
+- **LOCAL**
+
+  Specifies that the partitioned index to be created is a LOCAL index.
+
+- **GLOBAL**
+
+  Specifies the partitioned index to be created as a GLOBAL index. If no keyword is specified, a GLOBAL index is created by default.
+
+- **WITH ( {storage_parameter = value} [, … ] )**
+
+  Specifies the storage parameter used for an index.
+
+  Value range:
+
+  Only index GIN supports parameters **FASTUPDATE** and **GIN_PENDING_LIST_LIMIT**. Indexes other than GIN and psort support the **FILLFACTOR** parameter.
+
+  - FILLFACTOR
+
+    The fill factor of an index is a percentage from 10 to 100.
+
+    Value range: 10-100
+
+  - FASTUPDATE
+
+    Specifies whether fast update is enabled for the GIN index.
+
+    Value range: : **ON** and **OFF**
+
+    Default value: **ON**
+
+  - GIN_PENDING_LIST_LIMIT
+
+    Specifies the maximum capacity of the pending list of the GIN index when fast update is enabled for the GIN index.
+
+    Value range: 64-*INT_MAX*. The unit is KB.
+
+    Default value: The default value of  **gin_pending_list_limit**  depends on  **gin_pending_list_limit**  specified in GUC parameters. By default, the value is  **4**.
+
+- **TABLESPACE tablespace_name**
+
+  Specifies the tablespace for an index. If no tablespace is specified, the default tablespace is used.
+
+  Value range: an existing table name
+
+- **WHERE predicate**
+
+  Creates a partial index. A partial index is an index that contains entries for only a portion of a table, usually a portion that is more useful for indexing than the rest of the table. For example, if you have a table that contains both billed and unbilled orders where the unbilled orders take up a small fraction of the total table and yet that is an often used portion, you can improve performance by creating an index on just that portion. In addition, **WHERE** with **UNIQUE** can be used to enforce uniqueness over a subset for a table.
+
+  Value range: The predicate expression can only refer to columns of the underlying table, but it can use all columns, not just the ones being indexed. Currently, subqueries and aggregate expressions are forbidden in **WHERE**.
+
+- **PARTITION index_partition_name**
+
+  Specifies the name of an index partition.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **TABLESPACE index_partition_tablespace**
+
+  Specifies the tablespace of an index partition.
+
+  Value range: If this parameter is not specified, the value of **index_tablespace** is used.
+
+## Examples
+
+```sql
+-- Create the tpcds.ship_mode_t1 table.
+mogdb=# create schema tpcds;
+mogdb=# CREATE TABLE tpcds.ship_mode_t1
+(
+    SM_SHIP_MODE_SK           INTEGER               NOT NULL,
+    SM_SHIP_MODE_ID           CHAR(16)              NOT NULL,
+    SM_TYPE                   CHAR(30)                      ,
+    SM_CODE                   CHAR(10)                      ,
+    SM_CARRIER                CHAR(20)                      ,
+    SM_CONTRACT               CHAR(20)
+)
+;
+
+-- Create a common unique index on the SM_SHIP_MODE_SK column in the tpcds.ship_mode_t1 table.
+mogdb=# CREATE UNIQUE INDEX ds_ship_mode_t1_index1 ON tpcds.ship_mode_t1(SM_SHIP_MODE_SK);
+
+-- Create a B-tree index on the SM_SHIP_MODE_SK column in the tpcds.ship_mode_t1 table.
+mogdb=# CREATE INDEX ds_ship_mode_t1_index4 ON tpcds.ship_mode_t1 USING btree(SM_SHIP_MODE_SK);
+
+-- Create an expression index on the SM_CODE column in the tpcds.ship_mode_t1 table:
+mogdb=# CREATE INDEX ds_ship_mode_t1_index2 ON tpcds.ship_mode_t1(SUBSTR(SM_CODE,1 ,4));
+
+-- Create a partial index on the SM_SHIP_MODE_SK column where SM_SHIP_MODE_SK is greater than 10 in the tpcds.ship_mode_t1 table.
+mogdb=# CREATE UNIQUE INDEX ds_ship_mode_t1_index3 ON tpcds.ship_mode_t1(SM_SHIP_MODE_SK) WHERE SM_SHIP_MODE_SK>10;
+
+-- Rename an existing index.
+mogdb=# ALTER INDEX tpcds.ds_ship_mode_t1_index1 RENAME TO ds_ship_mode_t1_index5;
+
+-- Set the index as unusable.
+mogdb=# ALTER INDEX tpcds.ds_ship_mode_t1_index2 UNUSABLE;
+
+-- Rebuild an index.
+mogdb=# ALTER INDEX tpcds.ds_ship_mode_t1_index2 REBUILD;
+
+-- Delete an existing index.
+mogdb=# DROP INDEX tpcds.ds_ship_mode_t1_index2;
+
+-- Delete the table.
+mogdb=# DROP TABLE tpcds.ship_mode_t1;
+
+-- Create a tablespace.
+mogdb=# CREATE TABLESPACE example1 RELATIVE LOCATION 'tablespace1/tablespace_1';
+mogdb=# CREATE TABLESPACE example2 RELATIVE LOCATION 'tablespace2/tablespace_2';
+mogdb=# CREATE TABLESPACE example3 RELATIVE LOCATION 'tablespace3/tablespace_3';
+mogdb=# CREATE TABLESPACE example4 RELATIVE LOCATION 'tablespace4/tablespace_4';
+-- Create the tpcds.customer_address_p1 table.
+mogdb=# CREATE TABLE tpcds.customer_address_p1
+(
+    CA_ADDRESS_SK             INTEGER               NOT NULL,
+    CA_ADDRESS_ID             CHAR(16)              NOT NULL,
+    CA_STREET_NUMBER          CHAR(10)                      ,
+    CA_STREET_NAME            VARCHAR(60)                   ,
+    CA_STREET_TYPE            CHAR(15)                      ,
+    CA_SUITE_NUMBER           CHAR(10)                      ,
+    CA_CITY                   VARCHAR(60)                   ,
+    CA_COUNTY                 VARCHAR(30)                   ,
+    CA_STATE                  CHAR(2)                       ,
+    CA_ZIP                    CHAR(10)                      ,
+    CA_COUNTRY                VARCHAR(20)                   ,
+    CA_GMT_OFFSET             DECIMAL(5,2)                  ,
+    CA_LOCATION_TYPE          CHAR(20)
+)
+TABLESPACE example1
+PARTITION BY RANGE(CA_ADDRESS_SK)
+(
+   PARTITION p1 VALUES LESS THAN (3000),
+   PARTITION p2 VALUES LESS THAN (5000) TABLESPACE example1,
+   PARTITION p3 VALUES LESS THAN (MAXVALUE) TABLESPACE example2
+)
+ENABLE ROW MOVEMENT;
+-- Create the partitioned table index ds_customer_address_p1_index1 without specifying the index partition name.
+mogdb=# CREATE INDEX ds_customer_address_p1_index1 ON tpcds.customer_address_p1(CA_ADDRESS_SK) LOCAL;
+-- Create the partitioned table index ds_customer_address_p1_index2 with the name of the index partition specified.
+mogdb=# CREATE INDEX ds_customer_address_p1_index2 ON tpcds.customer_address_p1(CA_ADDRESS_SK) LOCAL
+(
+    PARTITION CA_ADDRESS_SK_index1,
+    PARTITION CA_ADDRESS_SK_index2 TABLESPACE example3,
+    PARTITION CA_ADDRESS_SK_index3 TABLESPACE example4
+)
+TABLESPACE example2;
+
+-- Create a global partitioned index.
+mogdb=CREATE INDEX ds_customer_address_p1_index3 ON tpcds.customer_address_p1(CA_ADDRESS_ID) GLOBAL;
+
+-- If no keyword is specified, a global partitioned index is created by default.
+mogdb=CREATE INDEX ds_customer_address_p1_index4 ON tpcds.customer_address_p1(CA_ADDRESS_ID);
+
+-- Change the tablespace of the partitioned table index CA_ADDRESS_SK_index2 to example1.
+mogdb=# ALTER INDEX tpcds.ds_customer_address_p1_index2 MOVE PARTITION CA_ADDRESS_SK_index2 TABLESPACE example1;
+
+-- Change the tablespace of the partitioned table index CA_ADDRESS_SK_index3 to example2.
+mogdb=# ALTER INDEX tpcds.ds_customer_address_p1_index2 MOVE PARTITION CA_ADDRESS_SK_index3 TABLESPACE example2;
+
+-- Rename a partitioned table index.
+mogdb=# ALTER INDEX tpcds.ds_customer_address_p1_index2 RENAME PARTITION CA_ADDRESS_SK_index1 TO CA_ADDRESS_SK_index4;
+
+-- Delete the created indexes and the partitioned table.
+mogdb=# DROP INDEX tpcds.ds_customer_address_p1_index1;
+mogdb=# DROP INDEX tpcds.ds_customer_address_p1_index2;
+mogdb=# DROP TABLE tpcds.customer_address_p1;
+-- Delete the tablespace.
+mogdb=# DROP TABLESPACE example1;
+mogdb=# DROP TABLESPACE example2;
+mogdb=# DROP TABLESPACE example3;
+mogdb=# DROP TABLESPACE example4;
+
+-- Create a column-store table and its GIN index:
+mogdb=# create table cgin_create_test(a int, b text) with (orientation = column);
+CREATE TABLE
+mogdb=# create index cgin_test on cgin_create_test using gin(to_tsvector('ngram', b));
+CREATE INDEX
+```
+
+## Helpful Links
+
+[ALTER INDEX](9-ALTER-INDEX)，[DROP INDEX](84-DROP-INDEX)
+
+## Suggestions
+
+- create index
+
+  You are advised to create indexes on:
+
+  - Columns that are often queried
+  - Join conditions. For a query on joined columns, you are advised to create a composite index on the columns, For example, for  **select \* from t1 join t2 on t1.a=t2.a and t1.b=t2.b**, you can create a composite index on columns  **a**  and  **b**  in table  **t1**.
+  - Columns having filter criteria (especially scope criteria) of a **where** clause
+  - Columns that appear after **order by**, **group by**, and **distinct**
+
+  Constraints:
+
+  - Partial indexes cannot be created in a partitioned table.
+  - When a GLOBAL index is created on a partitioned table, the following constraints apply:
+    - Expression indexes and partial indexes are not supported.
+    - Row-store tables are not supported.
+    - Only B-tree indexes are supported.
+  - In the same attribute column, the LOCAL index and GLOBAL index of a partition cannot coexist.
+  - GLOBAL index supports a maximum of 31 columns.
+  - If the  **ALTER**  statement does not contain  **UPDATE GLOBAL INDEX**, the original GLOBAL index is invalid. In this case, other indexes are used for query. If the ALTER statement contains UPDATE GLOBAL INDEX, the original GLOBAL index is still valid and the index function is correct.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/50.1-CREATE-LANGUAGE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/50.1-CREATE-LANGUAGE.md
new file mode 100644
index 0000000000000000000000000000000000000000..6f70d29f301cc90c569d3a7b4da8048b28b629b5
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/50.1-CREATE-LANGUAGE.md
@@ -0,0 +1,71 @@
+---
+title: CREATE LANGUAGE
+summary: CREATE LANGUAGE
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# CREATE LANGUAGE
+
+## Function
+
+**CREATE LANGUAGE**  defines a new procedural language. A single-node system or centralized system does not support creating procedural languages.
+
+## Syntax
+
+```ebnf+diagram
+CreateLanguage ::= CREATE [ OR REPLACE ] [ PROCEDURAL ] LANGUAGE name;
+```
+
+```ebnf+diagram
+CreateLanguage ::= CREATE [ OR REPLACE ] [ TRUSTED ] [ PROCEDURAL ] LANGUAGE name
+    HANDLER call_handler [ INLINE inline_handler ] [ VALIDATOR valfunction ];
+```
+
+## Parameter Description
+
+- **TRUSTED**
+
+  Specifies that the language does not authorize users who do not have permissions to access data. If this keyword is ignored when the language is registered, only the super user has the permission to use the language.
+
+- **PROCEDURAL**
+
+  It's a useless word.
+
+- **name**
+
+  Specifies the name of the new procedural language. This name should be unique across all languages of the database.
+
+  For downward compatibility, the name can be enclosed in single quotation marks (').
+
+- **HANDLER call_handler**
+
+  **call_handler**  is a previously registered function that will be used to execute the procedural language. The call handler of the procedural language must be written in a compiled language (such as C), the call style must be version 1, and the function must be registered as a function that does not accept parameters and returns the language_handler type.  **language_handler**  is a placeholder for declaring a function as a call handler.
+
+- **INLINE inline_handler**
+
+  **inline_handler**  is the name of a previously registered function that executes an anonymous block of code (**DO**  command) in the language. If the  **inline_handler**  function is not specified, the language does not support anonymous code blocks. The handler function must accept a parameter of the internal type, which will be the internal representation of the  **DO**  command, and it usually returns a void value. Ignore the return value of the handler.
+
+- **VALIDATOR valfunction**
+
+  **valfunction**  is a previously registered function name, which is used to verify a new function when it is created in the language. If the verification function is not declared, it will not be checked when a new function is created. The verification function must accept a parameter of the oid type, which is the OID of the function to be created and usually returns a void value.
+
+  A check function usually checks the function body for syntax errors, but it can also check other attributes of the function, for example, whether the language can process a certain parameter type. The verification function should use the  **ereport()**  function to report errors. The return value of this function will be ignored.
+
+## Examples
+
+A good way to create a standard procedural language:
+
+```sql
+CREATE LANGUAGE plperl;
+```
+
+For languages that pg_pltemplate does not yet know, the following sequence is needed:
+
+```sql
+CREATE FUNCTION plsample_call_handler() RETURNS language_handler
+    AS '$libdir/plsample'
+    LANGUAGE C;
+CREATE LANGUAGE plsample
+    HANDLER plsample_call_handler;
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/50.2-CREATE-MASKING-POLICY.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/50.2-CREATE-MASKING-POLICY.md
new file mode 100644
index 0000000000000000000000000000000000000000..54ed22cb7aa2d26af0ea58f7cd71e58f1a7674ed
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/50.2-CREATE-MASKING-POLICY.md
@@ -0,0 +1,111 @@
+---
+title: CREATE MASKING POLICY
+summary: CREATE MASKING POLICY
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# CREATE MASKING POLICY
+
+## Function
+
+**CREATE MASKING POLICY**  creates a masking policy.
+
+## Precautions
+
+Only users with the  **poladmin**  or  **sysadmin**  permission, or the initial user can perform this operation.
+
+The masking policy takes effect only after the security policy is enabled, that is, **enable_security_policy** is set to **on**.
+
+## Syntax
+
+```ebnf+diagram
+CreateMaskingPolicy ::= CREATE MASKING POLICY policy_name masking_clause[, ...]* policy_filter [ENABLE | DISABLE];
+```
+
+- masking_clause
+
+  ```ebnf+diagram
+  masking_clause ::= masking_function ON LABEL(label_name[, ...]*)
+  ```
+
+- masking_function
+
+  **maskall**  is not a preset function. It is hard-coded and cannot be displayed by running  **\\df**.
+
+  The masking methods during presetting are as follows:
+
+  ```ebnf+diagram
+  masking_function ::= maskall | randommasking | creditcardmasking | basicemailmasking | fullemailmasking | shufflemasking | alldigitsmasking | regexpmasking
+  ```
+
+- policy_filter:
+
+  ```ebnf+diagram
+  policy_filter ::= FILTER ON FILTER_TYPE(filter_value [,...]*)[,...]*
+  ```
+
+- FILTER_TYPE:
+
+  ```ebnf+diagram
+  filter_IP | APP | ROLES
+  ```
+
+## Parameter Description
+
+- **policy_name**
+
+  Specifies the audit policy name, which must be unique.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **label_name**
+
+  Specifies the resource label name.
+
+- **masking_clause**
+
+  Specifies the masking function to be used to anonymize database resources labeled by  **label_name**.  **schema.function**  can be used to specify the masking function.
+
+- **policy_filter**
+
+  Specifies the users for which the masking policy takes effect. If this parameter is left empty, the masking policy takes effect for all users.
+
+- **FILTER_TYPE**
+
+  Specifies the types of information to be filtered by the policy, including **IP**, **APP**, and **ROLES**.
+
+- **filter_value**
+
+  Indicates the detailed information to be filtered, such as the IP address, app name, and username.
+
+- **ENABLE|DISABLE**
+
+  Enables or disables the masking policy. If **ENABLE|DISABLE** is not specified, **ENABLE** is used by default.
+
+## Examples
+
+```sql
+-- Create users dev_mask and bob_mask.
+mogdb=# CREATE USER dev_mask PASSWORD 'dev@1234';
+mogdb=# CREATE USER bob_mask PASSWORD 'bob@1234';
+
+-- Create table tb_for_masking.
+mogdb=# CREATE TABLE tb_for_masking(col1 text, col2 text, col3 text);
+
+-- Create a resource label for label sensitive column col1.
+mogdb=# CREATE RESOURCE LABEL mask_lb1 ADD COLUMN(tb_for_masking.col1);
+
+-- Create a resource label for label sensitive column col2.
+mogdb=# CREATE RESOURCE LABEL mask_lb2 ADD COLUMN(tb_for_masking.col2);
+
+-- Create a masking policy for the operation of accessing sensitive column col1.
+mogdb=# CREATE MASKING POLICY maskpol1 maskall ON LABEL(mask_lb1);
+
+-- Create a masking policy that takes effect only for scenarios where users are dev_mask and bob_mask, client tools are psql and gsql, and IP addresses are 10.20.30.40, and 127.0.0.0/24.
+mogdb=# CREATE MASKING POLICY maskpol2 randommasking ON LABEL(mask_lb2) FILTER ON ROLES(dev_mask, bob_mask), APP(psql, gsql), IP('10.20.30.40', '127.0.0.0/24');
+```
+
+## Helpful Links
+
+[ALTER MASKING POLICY](10.1-ALTER-MASKING-POLICY)，[DROP MASKING POLICY](84.2-DROP-MASKING-POLICY)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/50.3-CREATE-MODEL.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/50.3-CREATE-MODEL.md
new file mode 100644
index 0000000000000000000000000000000000000000..4e966ab8bcf59a841e814bd2008ee433afeecfdd
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/50.3-CREATE-MODEL.md
@@ -0,0 +1,85 @@
+---
+title: CREATE MODEL
+summary: CREATE MODEL
+author: Zhang Cuiping
+date: 2021-11-01
+---
+
+# CREATE MODEL
+
+## Function
+
+**CREATE MODEL** trains a machine learning model and saves the model.
+
+## Precautions
+
+- The model name must be unique. Pay attention to the naming format.
+- The AI training duration fluctuates greatly, and in some cases, the training duration is long. If the duration specified by the GUC parameter **statement_timeout** is too long, the training will be interrupted. You are advised to set **statement_timeout** to **0** so that the statement execution duration is not limited.
+
+## Syntax
+
+```ebnf+diagram
+CreateModel ::= CREATE MODEL model_name USING algorithm_name
+[FEATURES { {expression [ [ AS ] output_name ]} [, ...] }]
+[TARGET { {expression [ [ AS ] output_name ]} [, ...] }]
+FROM { table_name | select_query }
+WITH hyperparameter_name = { hyperparameter_value | DEFAULT } [, ...]
+```
+
+## Parameter Description
+
+- **model_name**
+
+  Name of the training model, which must be unique.
+
+  Value range: a string. It must comply with the identifier naming convention.
+
+- **architecture_name**
+
+  Algorithm type of the training model.
+
+  Value range: a string. Currently, the value can be **logistic_regression**, **linear_regression**, **svm_classification**, or **kmeans**.
+
+- **attribute_list**
+
+  Enumerated input column name of the training model.
+
+  Value range: a string. It must comply with the naming convention of data attributes.
+
+- **attribute_name**
+
+  Target column name of the retraining model in a supervised learning task (simple expression processing can be performed).
+
+  Value range: a string. It must comply with the naming convention of data attributes.
+
+- **subquery**
+
+  Data source.
+
+  Value range: a string. It must comply with the SQL syntax of databases.
+
+- **hyper_parameter_name**
+
+  Hyperparameter name of the machine learning model.
+
+  Value range: a string. The value range varies depending on the algorithms.
+
+- **hp_value**
+
+  Hyperparameter value.
+
+  Value range: a string. The value range varies depending on the algorithms.
+
+## Examples
+
+```sql
+CREATE MODEL price_model USING logistic_regression
+ FEATURES size, lot
+ TARGET price
+ FROM HOUSES
+ (WITH learning_rate=0.88, max_iterations=default);
+```
+
+## Helpful Links
+
+[DROP MODEL](84.3-DROP-MODEL) and [PREDICT BY](112.1-PREDICT-BY)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/51-CREATE-MATERIALIZED-VIEW.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/51-CREATE-MATERIALIZED-VIEW.md
new file mode 100644
index 0000000000000000000000000000000000000000..11acacaa98848c160dd84e4dd4d7ed1a641a0e9d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/51-CREATE-MATERIALIZED-VIEW.md
@@ -0,0 +1,76 @@
+---
+title: CREATE MATERIALIZED VIEW
+summary: CREATE MATERIALIZED VIEW
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE MATERIALIZED VIEW
+
+## Function
+
+CREATE MATERIALIZED VIEW creates a full materialized view, and you can use REFRESH MATERIALIZED VIEW (full refresh) to refresh the data in the materialized view.
+
+CREATE MATERIALIZED VIEW is similar to CREATE TABLE AS, but it remembers the query used to initialize the view, so it can refresh data later. A materialized view has many attributes that are the same as those of a table, but does not support temporary materialized views.
+
+## Precautions
+
+- Full materialized views cannot be created in temporary tables or global temporary tables.
+- Full materialized views do not support NodeGroups.
+- After an full materialized view is created, most DDL operations in the base table are no longer supported.
+- The IUD operation cannot be performed on full materialized views.
+- After a full materialized view is created, if the base table data changes, you need to run the refresh command to synchronize the materialized view with the base table.
+
+## Syntax
+
+```ebnf+diagram
+CreateMaterializedView ::= CREATE MATERIALIZED VIEW mv_name
+    [ (column_name [, ...] ) ]
+    [ WITH ( {storage_parameter = value} [, ... ] ) ]
+      [ TABLESPACE tablespace_name ]
+    AS query
+    [ WITH [ NO ] DATA ];
+```
+
+## Parameter Description
+
+- **mv_name**
+
+  Name (optionally schema-qualified) of the materialized view to be created.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **column_name**
+
+  Specifies a column name in the new materialized view. The materialized view supports specified columns. The number of specified columns must be the same as the number of columns in the result of the subsequent query statement. If no column name is provided, the column name is obtained from the output column name of the query.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **WITH ( storage_parameter [= value] [, … ] )**
+
+  Specifies an optional storage parameter for a table or an index. For details, see [CREATE TABLE](60-CREATE-TABLE).
+
+- **TABLESPACE tablespace_name**
+
+  Tablespace to which the new materialized view belongs. If not specified, the default tablespace is used.
+
+- **AS query**
+
+  Specifies the **SELECT**, **TABLE**, or **VALUES** command. This query will be run in a security-constrained operation.
+
+## Example
+
+```sql
+-- Create an ordinary table.
+mogdb=# CREATE TABLE my_table (c1 int, c2 int);
+-- Create a full materialized view.
+mogdb=# CREATE MATERIALIZED VIEW my_mv AS SELECT * FROM my_table;
+-- Write data to the base table.
+mogdb=# INSERT INTO my_table VALUES(1,1),(2,2);
+-- Refresh the full materialized view my_mv.
+mogdb=# REFRESH MATERIALIZED VIEW my_mv;
+```
+
+## Helpful Links
+
+[ALTER MATERIALIZED VIEW](11-ALTER-MATERIALIZED-VIEW),  [CREATE INCREMENTAL MATERIALIZED VIEW](49.1-CREATE-INCREMENTAL-MATERIALIZED-VIEW), [CREATE TABLE](60-CREATE-TABLE), [DROP MATERIALIZED VIEW](85-DROP-MATERIALIZED-VIEW), [REFRESH INCREMENTAL MATERIALIZED VIEW](115.1-REFRESH-INCREMENTAL-MATERIALIZED-VIEW), [REFRESH MATERIALIZED VIEW](116-REFRESH-MATERIALIZED-VIEW)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/51.1-CREATE-OPERATOR.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/51.1-CREATE-OPERATOR.md
new file mode 100644
index 0000000000000000000000000000000000000000..2233f51dc12346a652e793af6a4d91d44ffe6dcb
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/51.1-CREATE-OPERATOR.md
@@ -0,0 +1,117 @@
+---
+title: CREATE OPERATOR
+summary: CREATE OPERATOR
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# CREATE OPERATOR
+
+## Function
+
+CREATE OPERATOR defines a new operator.
+
+## Precautions
+
+CREATE OPERATOR defines a new name operator. The user who defines the operator becomes the owner of the operator. If a schema name is given, the operator is created in the specified schema. Otherwise, it will be created in the current schema.
+
+The operator name is a character string consisting of the following characters:
+
+- \- * / &lt; &gt; = ~ ! @ # % ^ & | \` ?
+
+    When selecting a name, note the following restrictions:
+
+- \- and /* cannot appear anywhere in the operator name, because they are regarded as the beginning of a comment.
+
+- A multi-character operator cannot end with + or - unless the name contains at least one of the following characters:
+
+    \~ ! @ # % ^ & | \` ?
+
+- =&gt; The operator name is no longer used.
+
+Operator! = is mapped to &lt;&gt; when being entered. Therefore, the two names are always equivalent.
+
+At least one LEFTARG and one RIGHTARG must be defined. For binocular operators, both need to be defined. For the right operator, only LEFTARG needs to be defined. For the left operator, only RIGHTARG needs to be defined.
+
+Also, the function_name procedure must have been defined with CREATE FUNCTION, and must be defined to accept the correct number of specified type parameters (one or two).
+
+Other clauses declare optional operator optimization clauses. Their meanings are defined in [Section 35.13](https://www.postgresql.org/docs/9.3/xoper-optimization.html).
+
+To create an operator, you must have the USAGE permission on the parameter type and return type, and the EXECUTE permission on the underlying function. If exchange or negative operators are specified, you must have them.
+
+## Syntax
+
+```ebnf+diagram
+CreateOperator ::= CREATE OPERATOR name (
+    PROCEDURE = function_name
+    [, LEFTARG = left_type ] [, RIGHTARG = right_type ]
+    [, COMMUTATOR = com_op ] [, NEGATOR = neg_op ]
+    [, RESTRICT = res_proc ] [, JOIN = join_proc ]
+    [, HASHES ] [, MERGES ]
+);
+```
+
+## Parameter Description
+
+- **name**
+
+  Operator to be defined. The available characters are listed above. The name can be schema-qualified, for example, CREATE OPERATOR myschema.+ (…). If there is no schema, the operator is created in the current schema. Two operators in the same schema can have the same name as long as they operate on different data types. This is a reloading process.
+
+- **function_name**
+
+  Function used to implement the operator.
+
+- **left_type**
+
+  Parameter data type on the left of the operator, if any. This parameter can be omitted if the left operator is used.
+
+- **right_type**
+
+  Parameter data type on the right of the operator, if any. This parameter can be omitted if the right-view operator is used.
+
+- **com_op**
+
+  Exchange operator corresponding to the operator.
+
+- **neg_op**
+
+  Negative operator corresponding to the operator.
+
+- **res_proc**
+
+  This operator constrains the selectivity evaluation function.
+
+- **join_proc**
+
+  This operator joins the selectivity evaluation function.
+
+- **HASHES**
+
+  Indicates that the operator supports hash joins.
+
+- **MERGES**
+
+  Indicates that this operator supports a merge join.
+
+  Use the OPERATOR() syntax to provide a schema-qualified operator name in com_op or other optional parameters. For example:
+
+  ```
+  COMMUTATOR = OPERATOR(myschema.===) ,
+  ```
+
+## Example
+
+The following command defines a new operator: equal area for the box data type.
+
+```sql
+CREATE OPERATOR === (
+    LEFTARG = box,
+    RIGHTARG = box,
+    PROCEDURE = area_equal_procedure,
+    COMMUTATOR = ===,
+    NEGATOR = !==,
+    RESTRICT = area_restriction_procedure,
+    JOIN = area_join_procedure,
+    HASHES, MERGES
+);
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/51.2-CREATE-PACKAGE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/51.2-CREATE-PACKAGE.md
new file mode 100644
index 0000000000000000000000000000000000000000..d6ef1fd1a785ef6f72feb2dfbdb3d64108946f8b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/51.2-CREATE-PACKAGE.md
@@ -0,0 +1,88 @@
+---
+title: CREATE PACKAGE
+summary: CREATE PACKAGE
+author: Zhang Cuiping
+date: 2021-11-01
+---
+
+# CREATE PACKAGE
+
+## Function
+
+**CREATE PACKAGE** creates a package.
+
+## Precautions
+
+- Due to upgrade restrictions, in V500R002C00, stored procedures with the same name and parameters cannot be created even in different packages.
+- The package can be used only in centralized databases and cannot be used in distributed databases.
+- The functions or stored procedures declared in the package specification must be defined in the package body.
+- During instantiation, the stored procedure with **commit** or **rollback** cannot be invoked.
+- Package functions cannot be invoked in triggers.
+- Variables in a package cannot be directly used in external SQL statements.
+- Private variables and stored procedures in a package cannot be invoked outside the package.
+- Usage that other stored procedures do not support are not supported. For example, if **commit** or **rollback** cannot be invoked in a function, **commit** or **rollback** cannot be invoked in the function of a package.
+- The name of a schema cannot be the same as that of a package.
+- Only A-version stored procedures and function definitions are supported.
+- Variables with the same name in a package, including parameters with the same name in a package, are not supported.
+- The global variables in a package are at the session level. The variables in packages cannot be shared in different sessions.
+- When a function of an autonomous transaction is invoked in a package, public variables and recursive functions that use public variables are not allowed.
+- The package does not declare the ref cursor type.
+
+## Syntax
+
+- **CREATE PACKAGE SPECIFICATION**
+
+  ```ebnf+diagram
+  CreatePackage ::= CREATE [ OR REPLACE ] PACKAGE [ schema ] package_name
+      [ invoker_rights_clause ] { IS | AS } item_list_1 END package_name;
+  ```
+
+  invoker_rights_clause can be declared as AUTHID DEFINER or AUTHID INVOKER, which indicate the definer permission and invoker permission, respectively.
+  item_list_1 can be a declared variable, stored procedure, or function.
+
+  The package specification declares public variables, functions, and exceptions in a package, which can be invoked by external functions or stored procedures. It can only declare stored procedures and functions but cannot define them.
+
+- **CREATE PACKAGE BODY**
+
+  ```ebnf+diagram
+  CreatePackageBody ::= CREATE [ OR REPLACE ] PACKAGE BODY [ schema ] package_name
+      { IS | AS } declare_section [ initialize_section ] END package_name;
+  ```
+
+  The package body defines private variables and functions in a package. If a variable or function is not declared by the package specification, it is a private variable or function.
+
+  The package body also has an initialization part to initialize the package. For details, see the example.
+
+## Examples
+
+- **CREATE PACKAGE SPECIFICATION**
+
+  ```sql
+  CREATE OR REPLACE PACKAGE emp_bonus IS
+  var1 int:=1;-- Public variable
+  var2 int:=2;
+  PROCEDURE testpro1(var3 int);-- Public stored procedure, which can be invoked by external systems.
+  END emp_bonus;
+  /
+  ```
+
+- **CREATE PACKAGE BODY**
+
+  ```sql
+  drop table if exists test1;
+  create or replace package body emp_bonus is
+  var3 int:=3;
+  var4 int:=4;
+  procedure testpro1(var5 int)
+  is
+  begin
+  create table if not exists test1(col1 int);
+  insert into test1 values(var1);
+  insert into test1 values(var5);
+  end;
+  begin: --The instantiation starts.
+  var4:=9;
+  testpro1(var4);
+  end emp_bonus;
+  /
+  ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/52-CREATE-ROW-LEVEL-SECURITY-POLICY.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/52-CREATE-ROW-LEVEL-SECURITY-POLICY.md
new file mode 100644
index 0000000000000000000000000000000000000000..e3ff76d4d7827139c4e7975a4731610f6bae554c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/52-CREATE-ROW-LEVEL-SECURITY-POLICY.md
@@ -0,0 +1,175 @@
+---
+title: CREATE ROW LEVEL SECURITY POLICY
+summary: CREATE ROW LEVEL SECURITY POLICY
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE ROW LEVEL SECURITY POLICY
+
+## Function
+
+**CREATE ROW LEVEL SECURITY POLICY** creates a row-level access control policy for a table.
+
+The policy takes effect only after row-level access control is enabled (by running **ALTER TABLE… ENABLE ROW LEVEL SECURITY**). Otherwise, this statement does not take effect.
+
+Currently, row-level access control affects the read (**SELECT**, **UPDATE**, **DELETE**) of data tables and does not affect the write (**INSERT** and **MERGE INTO**) of data tables. The table owner or system administrators can create an expression in the **USING** clause. When the client reads the data table, the database server combines the expressions that meet the condition and applies it to the execution plan in the statement rewriting phase of a query. For each tuple in a data table, if the expression returns **TRUE**, the tuple is visible to the current user; if the expression returns **FALSE** or **NULL**, the tuple is invisible to the current user.
+
+A row-level access control policy name is specific to a table. A data table cannot have row-level access control policies with the same name. Different data tables can have the same row-level access control policy.
+
+Row-level access control policies can be applied to specified operations (**SELECT**, **UPDATE**, **DELETE**, and **ALL**). **ALL** indicates that **SELECT**, **UPDATE**, and **DELETE** will be affected. For a new row-level access control policy, the default value **ALL** will be used if you do not specify the operations that will be affected.
+
+Row-level access control policies can be applied to a specified user (role) or to all users (**PUBLIC**). For a new row-level access control policy, the default value **PUBLIC** will be used if you do not specify the user that will be affected.
+
+## Precautions
+
+- Row-level access control policies can be defined for row-store tables, row-store partitioned tables, column-store tables, column-store partitioned tables, unlogged tables, and hash tables.
+- Row-level access control policies cannot be defined for foreign tables and local temporary tables.
+- Row-level access control policies cannot be defined for views.
+- A maximum of 100 row-level access control policies can be defined for a table.
+- System administrators are not affected by row-level access control policies and can view all data in a table.
+- Tables queried by using SQL statements, views, functions, and stored procedures are affected by row-level access control policies.
+
+## Syntax
+
+```ebnf+diagram
+CreateRowLevelSecurityPolicy ::= CREATE [ ROW LEVEL SECURITY ] POLICY policy_name ON table_name
+     [ AS { PERMISSIVE | RESTRICTIVE } ]
+     [ FOR { ALL | SELECT | UPDATE | DELETE } ]
+     [ TO { role_name | PUBLIC | CURRENT_USER | SESSION_USER } [, ...] ]
+     USING ( using_expression )
+```
+
+## Parameter Description
+
+- **policy_name**
+
+  Specifies the name of a row-level access control policy to be created. The names of row-level access control policies for a table must be unique.
+
+- **table_name**
+
+  Specifies the name of a table to which a row-level access control policy is applied.
+
+- **PERMISSIVE | RESTRICTIVE**
+
+  **PERMISSIVE** enables the permissive policy for row-level access control. The conditions of the permissive policy are joined through the OR expression.
+
+  **RESTRICTIVE** enables the restrictive policy for row-level access control. The conditions of the restrictive policy are joined through the AND expression. The join methods are as follows:
+
+  ```sql
+  (using_expression_permissive_1 OR using_expression_permissive_2 ...) AND (using_expression_restrictive_1 AND using_expression_restrictive_2 ...)
+  ```
+
+  The default value is **PERMISSIVE**.
+
+- **command**
+
+  Specifies the SQL operations affected by a row-level access control policy, including **ALL**, **SELECT**, **UPDATE**, and **DELETE**. If this parameter is not specified, the default value **ALL** will be used, covering **SELECT**, **UPDATE**, and **DELETE**.
+
+  If *command* is set to **SELECT**, only tuple data that meets the condition (the return value of *using_expression* is **TRUE**) can be queried. The operations that are affected include **SELECT**, **UPDATE…. RETURNING**, and **DELETE… RETURNING**.
+
+  If *command* is set to **UPDATE**, only tuple data that meets the condition (the return value of *using_expression* is **TRUE**) can be updated. The operations that are affected include **UPDATE**, **UPDATE … RETURNING**, and **SELECT … FOR UPDATE/SHARE**.
+
+  If *command* is set to **DELETE**, only tuple data that meets the condition (the return value of *using_expression* is **TRUE**) can be deleted. The operations that are affected include **DELETE** and **DELETE … RETURNING**.
+
+  The following table describes the relationship between row-level access control policies and SQL statements.
+
+  **Table 1** Relationship between row-level access control policies and SQL statements
+
+  | **Command**                 | **SELECT/ALL policy** | **UPDATE/ALL policy** | **DELETE/ALL policy** |
+  | :-------------------------- | :-------------------- | :-------------------- | :-------------------- |
+  | **SELECT**                  | Existing row          | No                    | No                    |
+  | **SELECT FOR UPDATE/SHARE** | Existing row          | Existing row          | No                    |
+  | **UPDATE**                  | No                    | Existing row          | No                    |
+  | **UPDATE RETURNING**        | Existing row          | Existing row          | No                    |
+  | **DELETE**                  | No                    | No                    | Existing row          |
+  | **DELETE RETURNING**        | Existing row          | No                    | Existing row          |
+
+- **role_name**
+
+  Specifies database users affected by a row-level access control policy.
+
+  If this parameter is not specified, the default value **PUBLIC** will be used, indicating that all database users will be affected. You can specify multiple affected database users.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** System administrators are not affected by row access control.
+
+- **using_expression**
+
+  Specifies an expression defined for a row-level access control policy (return type: boolean).
+
+  The expression cannot contain aggregate functions or window functions. In the statement rewriting phase of a query, if row-level access control for a data table is enabled, the expressions that meet the specified conditions will be added to the plan tree. The expression is calculated for each tuple in the data table. For **SELECT**, **UPDATE**, and **DELETE**, row data is visible to the current user only when the return value of the expression is **TRUE**. If the expression returns **FALSE**, the tuple is invisible to the current user. In this case, the user cannot view the tuple through the **SELECT** statement, update the tuple through the **UPDATE** statement, or delete the tuple through the **DELETE** statement.
+
+## Examples
+
+```sql
+-- Create user alice.
+mogdb=# CREATE USER alice PASSWORD 'xxxxxxxxx';
+
+-- Create user bob.
+mogdb=# CREATE USER bob PASSWORD 'xxxxxxxxx';
+
+-- Create the data table all_data.
+mogdb=# CREATE TABLE all_data(id int, role varchar(100), data varchar(100));
+
+--Insert data into the data table.
+mogdb=# INSERT INTO all_data VALUES(1, 'alice', 'alice data');
+mogdb=# INSERT INTO all_data VALUES(2, 'bob', 'bob data');
+mogdb=# INSERT INTO all_data VALUES(3, 'peter', 'peter data');
+
+-- Grant the read permission on the all_data table to users alice and bob.
+mogdb=# GRANT SELECT ON all_data TO alice, bob;
+
+--Enable row-level access control.
+mogdb=# ALTER TABLE all_data ENABLE ROW LEVEL SECURITY;
+
+--Create a row-level access control policy to specify that the current user can view only their own data.
+mogdb=# CREATE ROW LEVEL SECURITY POLICY all_data_rls ON all_data USING(role = CURRENT_USER);
+
+-- View information about the all_data table.
+mogdb=# \d+ all_data
+                               Table "public.all_data"
+ Column |          Type          | Modifiers | Storage  | Stats target | Description
+--------+------------------------+-----------+----------+--------------+-------------
+ id     | integer                |           | plain    |              |
+ role   | character varying(100) |           | extended |              |
+ data   | character varying(100) |           | extended |              |
+Row Level Security Policies:
+    POLICY "all_data_rls"
+      USING (((role)::name = "current_user"()))
+Has OIDs: no
+Options: orientation=row, compression=no, enable_rowsecurity=true
+
+-- Run SELECT.
+mogdb=# SELECT * FROM all_data;
+ id | role  |    data
+----+-------+------------
+  1 | alice | alice data
+  2 | bob   | bob data
+  3 | peter | peter data
+(3 rows)
+
+mogdb=# EXPLAIN(COSTS OFF) SELECT * FROM all_data;
+      QUERY PLAN
+----------------------
+ Seq Scan on all_data
+(1 row)
+
+-- Switch to user alice and run SELECT.
+mogdb=# SELECT * FROM all_data;
+ id | role  |    data
+----+-------+------------
+  1 | alice | alice data
+(1 row)
+
+mogdb=# EXPLAIN(COSTS OFF) SELECT * FROM all_data;
+ QUERY PLAN
+----------------------------------------------------------------
+ Seq Scan on all_data
+   Filter: ((role)::name = 'alice'::name)
+ Notice: This query is influenced by row level security feature
+(3 rows)
+```
+
+## Helpful Links
+
+[DROP ROW LEVEL SECURITY POLICY](87-DROP-ROW-LEVEL-SECURITY-POLICY)，[ALTER ROW LEVEL SECURITY POLICY](13-ALTER-ROW-LEVEL-SECURITY-POLICY)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/53-CREATE-PROCEDURE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/53-CREATE-PROCEDURE.md
new file mode 100644
index 0000000000000000000000000000000000000000..f2e7daebb01ca9e2e822bd588c29fe77c8591caf
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/53-CREATE-PROCEDURE.md
@@ -0,0 +1,114 @@
+---
+title: CREATE PROCEDURE
+summary: CREATE PROCEDURE
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE PROCEDURE
+
+## Function
+
+**CREATE PROCEDURE** creates a stored procedure.
+
+## Precautions
+
+- If the parameters or return values of a stored procedure have precision, the precision is not checked.
+- When creating a stored procedure, you are advised to explicitly specify the schemas of all operations on table objects in the stored procedure definition. Otherwise, the stored procedure may fail to be executed.
+- **current_schema** and **search_path** specified by **SET** during stored procedure creation are invalid. **search_path** and **current_schema** before and after function execution should be the same.
+- If a stored procedure has output parameters, the **SELECT** statement uses the default values of the output parameters when calling the procedure. When the **CALL** statement calls the stored procedure or a non-overloaded function, output parameters must be specified. When the **CALL** statement calls an overloaded **PACKAGE** function, it can use the default values of the output parameters. For details, see examples in [CALL](34-CALL).
+- A stored procedure with the **PACKAGE** attribute can use overloaded functions.
+- When you create a procedure, you cannot insert aggregate functions or other functions out of the average function.
+- When calling stored procedures without parameters inside another stored procedure, you can omit brackets and call stored procedures using their names directly.
+
+- The stored procedure supports viewing, exporting, and importing parameter comments.
+- The stored procedure supports viewing, exporting, and importing parameter comments between IS/AS and plsql_body.
+
+## Syntax
+
+```ebnf+diagram
+CreateProcedure ::= CREATE [ OR REPLACE ] PROCEDURE procedure_name
+    [ ( {[ argmode ] [ argname ] argtype [ { DEFAULT | ':=' | = } expression ]}[, '...']) ]
+    [
+       { IMMUTABLE | STABLE | VOLATILE }
+       | { SHIPPABLE | NOT SHIPPABLE }
+       | {PACKAGE}
+       | [ NOT ] LEAKPROOF
+       | { CALLED ON NULL INPUT | RETURNS NULL ON NULL INPUT | STRICT }
+       | {[ EXTERNAL ] SECURITY INVOKER | [ EXTERNAL ] SECURITY DEFINER | AUTHID DEFINER | AUTHID CURRENT_USER}
+       | COST execution_cost
+       | SET configuration_parameter { TO value | = value | FROM CURRENT }
+    ][ '...' ]
+ { IS | AS }
+plsql_body
+```
+
+## Parameter Description
+
+- **OR REPLACE**
+
+  Replaces the original definition when two stored procedures are with the same name.
+
+- **procedure_name**
+
+  Specifies the name of the stored procedure that is created (optionally with schema names).
+
+  Value range: a string. It must comply with the naming convention.
+
+- **argmode**
+
+  Specifies the mode of an argument.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** **VARIADIC** specifies parameters of the array type.
+
+  Value range: **IN**, **OUT**, **INOUT**, and **VARIADIC**. The default value is **IN**. Only the parameters in **OUT** mode can follow the **VARIADIC** parameter.
+
+- **argname**
+
+  Specifies the argument name.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **argtype**
+
+  Specifies the type of an argument.  **%TYPE**  or  **%ROWTYPE**  can be used to indirectly reference a variable or table type. For details, see  [Variable Definition Statements](1-6-basic-statements).
+
+  Value range: a valid data type
+
+- **configuration_parameter**
+
+  - **value**
+
+    Sets the specified configuration parameter to a specified value. If the **value** is **DEFAULT**, the default setting is used in the new session. **OFF** disables the setting.
+
+    Value range: a string
+
+    - DEFAULT
+    - OFF
+    - Specified default value
+
+  - **from current**
+
+    Uses the value of **configuration_parameter** of the current session.
+
+- **IMMUTABLE, STABLE,**…
+
+  Specifies a constraint. The function of each parameter is similar to that of **CREATE FUNCTION**. For details, see [CREATE FUNCTION](48-CREATE-FUNCTION).
+
+- **plsql_body**
+
+  Specifies the PL/SQL stored procedure body.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** When you create a user, or perform other operations requiring password input in a stored procedure, the system catalog and CSV log record the password in plaintext. Therefore, you are advised not to perform such operations in the stored procedure.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** No specific order is applied to **argument_name** and **argmode**. The following order is advised: **argument_name**, **argmode**, and **argument_type**.
+
+## Helpful Links
+
+[DROP PROCEDURE](88-DROP-PROCEDURE)
+
+## Suggestions
+
+- analyse | analyze
+  - Do not run **ANALYZE** in a transaction or anonymous block.
+  - Do not run **ANALYZE** in a function or stored procedure.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/53.1-CREATE-RESOURCE-LABEL.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/53.1-CREATE-RESOURCE-LABEL.md
new file mode 100644
index 0000000000000000000000000000000000000000..c46e06080ec6ceb732e9d4209f28d931df2b2de7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/53.1-CREATE-RESOURCE-LABEL.md
@@ -0,0 +1,85 @@
+---
+title: CREATE RESOURCE LABEL
+summary: CREATE RESOURCE LABEL
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# CREATE RESOURCE LABEL
+
+## Function
+
+**CREATE RESOURCE LABEL** creates a resource label.
+
+## Precautions
+
+Only users with the  **poladmin**  or  **sysadmin**  permission, or the initial user can perform this operation.
+
+## Syntax
+
+```ebnf+diagram
+CreateResourceLabel ::= CREATE RESOURCE LABEL [IF NOT EXISTS] label_name ADD label_item_list[, ...]*;
+```
+
+- label_item_list
+
+  ```ebnf+diagram
+  label_item_list ::= resource_type(resource_path[, ...]*)
+  ```
+
+- resource_type
+
+  ```ebnf+diagram
+  resource_type ::= TABLE | COLUMN | SCHEMA | VIEW | FUNCTION
+  ```
+
+## Parameter Description
+
+- **label_name**
+
+  Specifies the resource label name, which must be unique.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **resource_type**
+
+  Specifies the type of database resources to be labeled.
+
+- **resource_path**
+
+  Specifies the path of database resources.
+
+## Examples
+
+```sql
+-- Create table tb_for_label.
+mogdb=# CREATE TABLE tb_for_label(col1 text, col2 text, col3 text);
+
+-- Create schema schema_for_label.
+mogdb=# CREATE SCHEMA schema_for_label;
+
+-- Create view view_for_label.
+mogdb=# CREATE VIEW view_for_label AS SELECT 1;
+
+-- Create function func_for_label.
+mogdb=# CREATE FUNCTION func_for_label RETURNS TEXT AS $$ SELECT col1 FROM tb_for_label; $$ LANGUAGE SQL;
+
+-- Create a resource label based on the table.
+mogdb=# CREATE RESOURCE LABEL IF NOT EXISTS table_label add TABLE(public.tb_for_label);
+
+-- Create a resource label based on the columns.
+mogdb=# CREATE RESOURCE LABEL IF NOT EXISTS column_label add COLUMN(public.tb_for_label.col1);
+
+-- Create a resource label based on the schema.
+mogdb=# CREATE RESOURCE LABEL IF NOT EXISTS schema_label add SCHEMA(schema_for_label);
+
+-- Create a resource label based on the view.
+mogdb=# CREATE RESOURCE LABEL IF NOT EXISTS view_label add VIEW(view_for_label);
+
+-- Create a resource label based on the function.
+mogdb=# CREATE RESOURCE LABEL IF NOT EXISTS func_label add FUNCTION(func_for_label);
+```
+
+## Helpful Links
+
+[ALTER RESOURCE LABEL](11.2-ALTER-RESOURCE-LABEL)，[DROP RESOURCE LABEL](86.1-DROP-RESOURCE-LABEL)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/53.2-CREATE-RESOURCE-POOL.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/53.2-CREATE-RESOURCE-POOL.md
new file mode 100644
index 0000000000000000000000000000000000000000..75e254b15f61c40a0a3ab213f2643e17801d9d61
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/53.2-CREATE-RESOURCE-POOL.md
@@ -0,0 +1,136 @@
+---
+title: CREATE RESOURCE POOL
+summary: CREATE RESOURCE POOL
+author: Zhang Cuiping
+date: 2021-11-01
+---
+
+# CREATE RESOURCE POOL
+
+## Function
+
+**CREATE RESOURCE POOL** creates a resource pool and specifies the Cgroup of the resource pool.
+
+## Precautions
+
+Only a user with the **CREATE** permission on the current database can perform this operation.
+
+## Syntax
+
+```ebnf+diagram
+CreateResourcePool ::= CREATE RESOURCE POOL pool_name
+    [WITH ({MEM_PERCENT=pct | CONTROL_GROUP="group_name" | ACTIVE_STATEMENTS=stmt | MAX_DOP = dop | MEMORY_LIMIT='memory_size' | io_limits=io_limits | io_priority='io_priority' | nodegroup="nodegroupname" | is_foreign=boolean }[, ... ])];
+```
+
+## Parameter Description
+
+- **pool_name**
+
+  Specifies the name of a resource pool.
+
+  The name of a resource pool cannot be same as that of an existing resource pool.
+
+  Value range: a string. It must comply with the identifier naming convention.
+
+- **group_name**
+
+  Specifies the name of a Cgroup.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > - You can use either double quotation marks ("") or single quotation marks (") in the syntax when setting the name of a Cgroup.
+  > - The value of **group_name** is case-sensitive.
+  > - If **group_name** is not specified, the string "Medium" will be used by default in the syntax, indicating the **Medium** Timeshare Cgroup under **DefaultClass**.
+  > - If a database administrator specifies a Workload Cgroup under **Class**, for example, **control_group** set to **class1:workload1**, the resource pool will be associated with the **workload1** Cgroup under **class1**. The level of the Workload Cgroup can also be specified. For example, **control_group** is set to **class1:workload1:1**.
+  > - If a database user specifies the Timeshare Cgroup string (**Rush**, **High**, **Medium**, or **Low**) in the syntax, for example, **control_group** is set to **High**, the resource pool will be associated with the **High** Timeshare Cgroup under **DefaultClass**.
+
+  Value range: a string. It must comply with the rule in the description, which specifies the created Cgroup.
+
+- **stmt**
+
+  Specifies the maximum number of statements that can be concurrently executed in a resource pool.
+
+  Value range: numeric data ranging from -1 to 2147483647
+
+- **dop**
+
+  Specifies the maximum statement concurrency degree for a resource pool, equivalent to the number of threads that can be created for executing a statement.
+
+  Value range: numeric data ranging from 1 to 2147483647
+
+- **memory_size**
+
+  Specifies the maximum memory size of a resource pool.
+
+  Value range: a string from 1 KB to 2047 GB
+
+- **mem_percent**
+
+  Specifies the proportion of available resource pool memory to the total memory or group user memory.
+
+  In multi-tenant scenarios, the value of **mem_percent** of group users or service users ranges from 1 to 100. The default value is **20**.
+
+  In common scenarios, the value of **mem_percent** of common users ranges from 0 to 100. The default value is **0**.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** When both **mem_percent** and **memory_limit** are specified, only **mem_percent** takes effect.
+
+- **io_limits**
+
+  Specifies the upper limit of IOPS in a resource pool.
+
+  The IOPS is counted by ones for column storage and by 10 thousands for row storage.
+
+- **io_priority**
+
+  Specifies the I/O priority for jobs that consume many I/O resources. It takes effect when the I/O usage reaches 90%.
+
+  There are three priorities: **Low**, **Medium**, and **High**. If you do not want to control I/O resources, use the default value **None**.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The settings of **io_limits** and **io_priority** are valid only for complex jobs, such as batch import (using **INSERT INTO SELECT**, **COPY FROM**, or **CREATE TABLE AS**), complex queries involving over 500 MB data on each DN, and **VACUUM FULL**.
+
+- **nodegroup**
+
+  Specifies the name of a logical cluster. The logical cluster must already exist.
+
+  If the logical cluster name contains uppercase letters or special characters or begins with a digit, enclose the name with double quotation marks ("") in SQL statements.
+
+- **is_foreign**
+
+  In logical cluster mode, specifies the current resource pool to control the resources of common users that are not associated with the logical cluster specified by **nodegroup**.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > - **nodegroup** must specify an existing logical cluster, and cannot be **elastic_group** or the default node group (**group_version1**), which is generated during cluster installation.
+  > - If **is_foreign** is set to **true**, the resource pool cannot be associated with users. That is, **CREATE USER … RESOURCE POOL** cannot be used to configure resource pools for users. The resource pool automatically checks whether the users are associated with its logical cluster. If they are not, they will be controlled by the resource pool when performing operations on DNs in the logical cluster.
+
+## Examples
+
+This example assumes that Cgroups have been created by users in advance.
+
+```sql
+-- Create a default resource pool, and associate it with the Medium Timeshare Cgroup under Workload under DefaultClass.
+mogdb=# CREATE RESOURCE POOL pool1;
+
+-- Create a resource pool, and associate it with the High Timeshare Workload Cgroup under DefaultClass.
+mogdb=# CREATE RESOURCE POOL pool2 WITH (CONTROL_GROUP="High");
+
+-- Create a resource pool, and associate it with the Low Timeshare Workload Cgroup under class1.
+mogdb=# CREATE RESOURCE POOL pool3 WITH (CONTROL_GROUP="class1:Low");
+
+-- Create a resource pool, and associate it with the wg1 Workload Cgroup under class1.
+mogdb=# CREATE RESOURCE POOL pool4 WITH (CONTROL_GROUP="class1:wg1");
+
+-- Create a resource pool, and associate it with the wg2 Workload Cgroup under class1.
+mogdb=# CREATE RESOURCE POOL pool5 WITH (CONTROL_GROUP="class1:wg2:3");
+
+-- Delete the resource pool.
+mogdb=# DROP RESOURCE POOL pool1;
+mogdb=# DROP RESOURCE POOL pool2;
+mogdb=# DROP RESOURCE POOL pool3;
+mogdb=# DROP RESOURCE POOL pool4;
+mogdb=# DROP RESOURCE POOL pool5;
+```
+
+## Helpful Links
+
+[ALTER RESOURCE POOL](11.3-ALTER-RESOURCE-POOL)，[DROP RESOURCE POOL](86.2-DROP-RESOURCE-POOL)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/54-CREATE-ROLE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/54-CREATE-ROLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..46f56788d5e944ee0e4cb544880e1e0aefaddb9a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/54-CREATE-ROLE.md
@@ -0,0 +1,260 @@
+---
+title: CREATE ROLE
+summary: CREATE ROLE
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE ROLE
+
+## Function
+
+**CREATE ROLE** is used to create a role.
+
+A role is an entity that owns database objects and permissions. In different environments, a role can be considered a user, a group, or both.
+
+## Precautions
+
+- **CREATE ROLE** adds a role to a database. The role does not have the **LOGIN** permission.
+- Only the user who has the **CREATE ROLE** permission or a system administrator is allowed to create roles.
+
+## Syntax
+
+```ebnf+diagram
+CreateRole ::= CREATE ROLE role_name [ [ WITH ] option [ ... ] ] [ ENCRYPTED | UNENCRYPTED ] { PASSWORD | IDENTIFIED BY } { 'password' [EXPIRED] | DISABLE };
+```
+
+The syntax of role information configuration clause **option** is as follows:
+
+```ebnf+diagram
+option ::= {SYSADMIN | NOSYSADMIN}
+    | {MONADMIN | NOMONADMIN}
+    | {OPRADMIN | NOOPRADMIN}
+    | {POLADMIN | NOPOLADMIN}
+    | {AUDITADMIN | NOAUDITADMIN}
+    | {CREATEDB | NOCREATEDB}
+    | {USEFT | NOUSEFT}
+    | {CREATEROLE | NOCREATEROLE}
+    | {INHERIT | NOINHERIT}
+    | {LOGIN | NOLOGIN}
+    | {REPLICATION | NOREPLICATION}
+    | {INDEPENDENT | NOINDEPENDENT}
+    | {VCADMIN | NOVCADMIN}
+    | CONNECTION LIMIT connlimit
+    | VALID BEGIN 'timestamp'
+    | VALID UNTIL 'timestamp'
+    | RESOURCE POOL 'respool'
+    | PERM SPACE 'spacelimit'
+    | TEMP SPACE 'tmpspacelimit'
+    | SPILL SPACE 'spillspacelimit'
+    | IN ROLE role_name [, ...]
+    | IN GROUP role_name [, ...]
+    | ROLE role_name [, ...]
+    | ADMIN rol e_name [, ...]
+    | USER role_name [, ...]
+    | SYSID uid
+    | DEFAULT TABLESPACE tablespace_name
+    | PROFILE DEFAULT
+    | PROFILE profile_name
+    | PGUSER
+```
+
+## Parameter Description
+
+- **role_name**
+
+  Specifies the name of a role.
+
+  Value range: a string. It must comply with the naming convention rule, and can contain a maximum of 63 characters. If the value contains more than 63 characters, the database truncates it and retains the first 63 characters as the role name. When a role is created, the database will display a message.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The identifier must be letters, underscores (_), digits (0-9), or dollar signs ($) and must start with a letter (a-z) or underscore (_).
+
+- **password**
+
+  Specifies the login password.
+
+  A new password must:
+
+  - Contain at least eight characters. This is the default length.
+  - Differ from the username or the username spelled backward.
+  - Contain at least three of the following character types: uppercase characters, lowercase characters, digits, and special characters (limited to \~!@\#$ %^&\*()-_=+\\|[\{\}];:,<.\>/?).
+  - The password can also be a ciphertext character string that meets the format requirements. This mode is mainly used to import user data. You are not advised to use it directly. If a ciphertext password is used, the user must know the plaintext corresponding to the ciphertext password and ensure that the plaintext password meets the complexity requirements. The database does not verify the complexity of the ciphertext password. Instead, the security of the ciphertext password is ensured by the user.
+  - Be enclosed by single or double quotation marks.
+
+  Value range: a string
+
+- **EXPIRED**
+
+  When creating a user, you can specify the **EXPIRED** parameter to create a user whose password is invalid. The user cannot perform simple or extended queries. The statement can be executed only after the password is changed.
+
+- **DISABLE**
+
+  By default, you can change your password unless it is disabled. To disable the password of a user, use this parameter. After the password of a user is disabled, the password will be deleted from the system. The user can connect to the database only through external authentication, for example, Kerberos authentication. Only administrators can enable or disable a password. Common users cannot disable the password of an initial user. To enable a password, run **ALTER USER** and specify the password.
+
+- **ENCRYPTED | UNENCRYPTED**
+
+  Controls whether the password is stored encrypted in the system catalogs. According to product security requirement, the password must be stored encrypted. Therefore,  **UNENCRYPTED**  is forbidden in MogDB. If the password string has already been encrypted in the SHA256 format, it is stored encrypted as it was, regardless of whether  **ENCRYPTED**  or  **UNENCRYPTED**  is specified (since the system cannot decrypt the specified encrypted password string). This allows reloading of encrypted passwords during dump/restore.
+
+- **SYSADMIN | NOSYSADMIN**
+
+  Determines whether a new role is a system administrator. Roles having the **SYSADMIN** attribute have the highest permission.
+
+  Value range: If not specified, **NOSYSADMIN** is the default.
+
+- **AUDITADMIN | NOAUDITADMIN**
+
+  Determines whether a role has the audit and management attributes.
+
+  If not specified, **NOAUDITADMIN** is the default.
+
+- **CREATEDB | NOCREATEDB**
+
+  Determines a role's permission to create databases.
+
+  A new role does not have the permission to create databases.
+
+  Value range: If not specified, **NOCREATEDB** is the default.
+
+- **USEFT | NOUSEFT**
+
+  This parameter is reserved and not used in this version.
+
+- **CREATEROLE | NOCREATEROLE**
+
+  Determines whether a role will be permitted to create new roles (that is, execute **CREATE ROLE** and **CREATE USER**). A role with the **CREATEROLE** permission can also modify and delete other roles.
+
+  Value range: If not specified, **NOCREATEROLE** is the default.
+
+- **INHERIT | NOINHERIT**
+
+  Determines whether a role "inherits" the permissions of roles in the same group. It is not recommended.
+
+- **LOGIN | NOLOGIN**
+
+  Determines whether a role is allowed to log in to a database. A role having the **LOGIN** attribute can be considered as a user.
+
+  Value range: If not specified, **NOLOGIN** is the default.
+
+- **REPLICATION | NOREPLICATION**
+
+  Determines whether a role is allowed to initiate streaming replication or put the system in and out of backup mode. A role having the **REPLICATION** attribute is specific to replication.
+
+  If not specified, **NOREPLICATION** is the default.
+
+- **INDEPENDENT | NOINDEPENDENT**
+
+  Defines private, independent roles. For a role with the **INDEPENDENT** attribute, administrators' permissions to control and access this role are separated. The rules are as follows:
+
+  - Administrators have no permission to add, delete, query, modify, copy, or authorize the corresponding table objects without the authorization from the **INDEPENDENT** role.
+  - If permissions related to private user tables are granted to non-private users, the system administrator will obtain the same permissions.
+  - System administrators and security administrators with the **CREATEROLE** attribute have no permission to modify the inheritance relationship of the **INDEPENDENT** role without the authorization of the **INDEPENDENT** role.
+  - System administrators have no permission to modify the owner of the table objects for the **INDEPENDENT** role.
+  - System administrators and security administrators with the **CREATEROLE** attribute have no permission to remove the **INDEPENDENT** attribute of the **INDEPENDENT** role.
+  - System administrators and security administrators with the **CREATEROLE** attribute have no permission to change the database password of the **INDEPENDENT** role. The **INDEPENDENT** role must manage its own password. If the password is lost, it cannot be reset.
+  - The **SYSADMIN** attribute of a user cannot be changed to the **INDEPENDENT** attribute.
+
+- **CONNECTION LIMIT**
+
+  Specifies how many concurrent connections the role can make.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+  >
+  > - The system administrator is not restricted by this parameter.
+  > - The number of concurrent connections of each primary database node is calculated separately (which is the value of **connlimit**). The number of all connections of MogDB = Value of **connlimit** x Number of normal primary database nodes.
+
+  Value range: an integer greater than or equal to -1. The default value is **-1**, which means unlimited.
+
+- **VALID BEGIN**
+
+  Sets a date and time when the role's password takes effect. If this clause is omitted, the password takes effect immediately.
+
+- **VALID UNTIL**
+
+  Sets a date and time after which the role's password is no longer valid. If this clause is omitted, the password will be valid for all time.
+
+- **RESOURCE POOL**
+
+  Sets the name of resource pool used by the role. The name belongs to the system catalog **pg_resource_pool**.
+
+- **PERM SPACE**
+
+  Sets the space available for a user, the space size is in 'number + unit' format, see below for an example.
+
+- **TEMP SPACE**
+
+  Sets the space allocated to the temporary table of a user, the space size is in 'number + unit' format, see below for an example.
+
+- **SPILL SPACE**
+
+  Sets the operator disk flushing space of a user, the space size is in 'number + unit' format, see below for an example.
+
+- **IN ROLE**
+
+  Lists one or more existing roles to which the new role will be immediately added as a new member. It is not recommended.
+
+- **IN GROUP**
+
+  Specifies an obsolete spelling of  **IN ROLE**. It is not recommended.
+
+- **ROLE**
+
+  Lists one or more existing roles which are automatically added as members of the new role.
+
+- **ADMIN**
+
+  Similar to **ROLE**. However, **ADMIN** grants permissions of new roles to other roles.
+
+- **USER**
+
+  Specifies an obsolete spelling of the **ROLE** clause.
+
+- **SYSID**
+
+  The **SYSID** clause is ignored.
+
+- **DEFAULT TABLESPACE**
+
+  The **DEFAULT TABLESPACE** clause is ignored.
+
+- **PROFILE**
+
+  The **PROFILE** clause is ignored.
+
+- **PGUSER**
+
+  In the current version, this attribute is reserved only for forward compatibility.
+
+## Examples
+
+```sql
+-- Create role manager whose password is xxxxxxxxx.
+mogdb=# CREATE ROLE manager IDENTIFIED BY 'xxxxxxxxx';
+
+-- Create a role with its validity from January 1, 2015 to January 1, 2026.
+mogdb=# CREATE ROLE miriam WITH LOGIN PASSWORD 'xxxxxxxxx' VALID BEGIN '2015-01-01' VALID UNTIL '2026-01-01';
+
+-- Change the password of role manager to abcd@123.
+mogdb=# ALTER ROLE manager IDENTIFIED BY 'abcd@123' REPLACE 'xxxxxxxxx';
+
+-- Change role manager to the system administrator.
+mogdb=# ALTER ROLE manager SYSADMIN;
+
+-- Delete role manager.
+mogdb=# DROP ROLE manager;
+
+-- Delete role miriam.
+mogdb=# DROP ROLE miriam;
+
+--Create role r1 and set the available space to 1k.
+mogdb=# CREATE ROLE r1 PERM SPACE '1k' IDENTIFIED BY "Enmo@123";
+
+--Create role r2 and set the allocated space of the temporary table to 1k。
+mogdb=# CREATE ROLE r2 TEMP SPACE '1k' IDENTIFIED BY "Enmo@123";
+
+--Create role r3 and set the operator disk flushing space to 1M。
+mogdb=# CREATE ROLE r3 SPILL SPACE '1M' IDENTIFIED BY "Enmo@123";
+```
+
+## Helpful Links
+
+[SET ROLE](129-SET-ROLE)，[ALTER ROLE](12-ALTER-ROLE)，[DROP ROLE](89-DROP-ROLE)，[GRANT](108-GRANT)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/55-CREATE-RULE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/55-CREATE-RULE.md
new file mode 100644
index 0000000000000000000000000000000000000000..79438c38b855710082a60071a2c910b364fa1839
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/55-CREATE-RULE.md
@@ -0,0 +1,72 @@
+---
+title: CREATE RULE
+summary: CREATE RULE
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE RULE
+
+## Function
+
+**CREATE RULE** defines a new rewrite rule.
+
+## Precautions
+
+- To define or modify rules of a table, you must be the owner of the table.
+- If multiple rules of the same type are defined for a table, trigger them in alphabetical order of the rule name.
+- A RETURNING clause can be added to the INSERT, UPDATE, or DELETE rule of a view. If a rule is triggered by INSERT RETURNING, UPDATE RETURNING, or DELETE RETURNING, these clauses will be used for calculating the output. If a rule is triggered by a command without RETURNING, the RETURNING clause of the rule will be ignored. Currently, only the INSTEAD rule without conditions is allowed to contain a RETURNING clause. Additionally, only one RETURNING clause can exist among all rules of the same event. This can make sure that only one RETURNING clause is used for calculating the output. If no RETURNING clause exist in any valid rules, the RETURNING query on the view will be rejected.
+
+## Syntax
+
+```ebnf+diagram
+CreateRule ::= CREATE [ OR REPLACE ] RULE name AS ON event
+    TO table_name [ WHERE condition ]
+    DO [ ALSO | INSTEAD ] { NOTHING | command | ( command ; command '...' ) }
+```
+
+Event is one of the following:
+
+```sql
+   SELECT
+   INSERT
+   DELETE
+   UPDATE
+```
+
+## Parameter Description
+
+- **name**
+
+  Specifies the name of the rule to be created. This must be distinct from the name of any other rule for the same table.
+
+  Value range: a string that meets the identifier naming rule and contains at most 63 characters.
+
+- **table_name**
+
+  Specifies the name of the table or view the rule applies to (optionally schema-qualified).
+
+- **condition**
+
+  Specifies any SQL conditional expression (returning `boolean`), which determines whether to perform the rule actually. The condition expression may not refer to any tables except new and old, and may not contain aggregate functions.
+
+- **INSTEAD**
+
+  Specifies that the initial event is replaced using this command.
+
+- **ALSO**
+
+  Specifies that this command should be run after the initial event is performed. If both ALSO and INSTEAD are not defined, ALSO is the default value.
+
+- **command**
+
+  Specifies the command for rule action. The valid command is one of SELECT, INSERT, UPDATE, and DELETE.
+
+## Example
+
+```sql
+CREATE RULE "_RETURN" AS
+    ON SELECT TO t1
+    DO INSTEAD
+        SELECT * FROM t2;
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/56-CREATE-SCHEMA.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/56-CREATE-SCHEMA.md
new file mode 100644
index 0000000000000000000000000000000000000000..d7bc3606c6f1c989ac036fe927ba5b0f98240fa1
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/56-CREATE-SCHEMA.md
@@ -0,0 +1,89 @@
+---
+title: CREATE SCHEMA
+summary: CREATE SCHEMA
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE SCHEMA
+
+## Function
+
+**CREATE SCHEMA** creates a schema.
+
+Named objects are accessed either by "qualifying" their names with the schema name as a prefix, or by setting a search path that includes the desired schema. When creating named objects, you can also use the schema name as a prefix.
+
+Optionally, **CREATE SCHEMA** can include sub-commands to create objects within the new schema. The sub-commands are treated essentially the same as separate commands issued after creating the schema. If the **AUTHORIZATION** clause is used, all the created objects are owned by this user.
+
+## Precautions
+
+- Only a user with the **CREATE** permission on the current database can perform this operation.
+- The owner of an object created by a system administrator in a schema with the same name as a common user is the common user, not the system administrator.
+
+## Syntax
+
+- Create a schema based on a specified name.
+
+  ```ebnf+diagram
+  CreateSchema ::= CREATE SCHEMA schema_name
+      [ AUTHORIZATION user_name ] [WITH BLOCKCHAIN] [ schema_element [ ... ] ];
+  ```
+
+- Create a schema based on a username.
+
+  ```ebnf+diagram
+  CreateSchema ::= CREATE SCHEMA AUTHORIZATION user_name [ schema_element [ ... ] ];
+  ```
+
+## Parameter Description
+
+- **schema_name**
+
+  Specifies the schema name.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+  > The name must be unique.
+  > The schema name cannot start with **pg_**.
+
+  Value range: a string. It must comply with the naming convention rule.
+
+- **AUTHORIZATION user_name**
+
+  Specifies the owner of a schema. If **schema_name** is not specified, **user_name** will be used as the schema name. In this case, **user_name** can only be a role name.
+
+  Value range: an existing username or role name
+
+- **WITH BLOCKCHAIN**
+
+    Specifies the tamper-proof attribute of a schema. In this mode, a row-store common user table is automatically extended to tamper-proof user table.
+
+- **schema_element**
+
+  Specifies an SQL statement defining an object to be created within the schema. Currently, only the  **CREATE TABLE**,  **CREATE VIEW**,  **CREATE INDEX**,  **CREATE PARTITION**,  **CREATE SEQUENCE**,  **CREATE TRIGGER**  and  **GRANT**  clauses are supported.
+
+  Objects created by sub-commands are owned by the user specified by **AUTHORIZATION**.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> If objects in the schema on the current search path are with the same name, specify the schemas for different objects. You can run **SHOW SEARCH_PATH** to check the schemas on the current search path.
+
+## Examples
+
+```sql
+-- Create the role1 role.
+mogdb=# CREATE ROLE role1 IDENTIFIED BY 'xxxxxxxxx';
+
+-- Create a schema named role1 for the role1 role. The owner of the films and winners tables created by the clause is role1.
+mogdb=# CREATE SCHEMA AUTHORIZATION role1
+     CREATE TABLE films (title text, release date, awards text[])
+     CREATE VIEW winners AS
+     SELECT title, release FROM films WHERE awards IS NOT NULL;
+
+-- Delete the schema.
+mogdb=# DROP SCHEMA role1 CASCADE;
+-- Delete the user.
+mogdb=# DROP USER role1 CASCADE;
+```
+
+## Helpful Links
+
+[ALTER SCHEMA](15-ALTER-SCHEMA)，[DROP SCHEMA](91-DROP-SCHEMA)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/57-CREATE-SEQUENCE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/57-CREATE-SEQUENCE.md
new file mode 100644
index 0000000000000000000000000000000000000000..ebee542298adcf1f327048be1676b0105b4bb633
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/57-CREATE-SEQUENCE.md
@@ -0,0 +1,145 @@
+---
+title: CREATE SEQUENCE
+summary: CREATE SEQUENCE
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE SEQUENCE
+
+## Function
+
+**CREATE SEQUENCE** adds a sequence to the current database. The owner of a sequence is the user who creates the sequence.
+
+## Precautions
+
+- A sequence is a special table that stores arithmetic progressions. It has no actual meaning and is usually used to generate unique identifiers for rows or tables.
+- If a schema name is given, the sequence is created in the specified schema; otherwise, it is created in the current schema. The sequence name must be different from the names of other sequences, tables, indexes, views in the same schema.
+- After the sequence is created, functions **nextval()** and **generate_series(1,N)** insert data to the table. Make sure that the number of times for invoking **nextval** is greater than or equal to N+1. Otherwise, errors will be reported because the number of times for invoking function **generate_series()** is N+1.
+
+## Syntax
+
+```ebnf+diagram
+CreateSequence ::= CREATE SEQUENCE name [ INCREMENT [ BY ] increment ]
+    [ MINVALUE minvalue | NO MINVALUE | NOMINVALUE ] [ MAXVALUE maxvalue | NO MAXVALUE | NOMAXVALUE]
+    [ START [ WITH ] start ] [ CACHE cache ] [ [ NO ] CYCLE | NOCYCLE ]
+    [ OWNED BY { table_name'.'column_name | NONE } ];
+```
+
+## Parameter Description
+
+- **name**
+
+  Specifies the name of a sequence to be created.
+
+  Value range: a sting containing only lowercase letters, uppercase letters, special characters #_$, and digits
+
+- **increment**
+
+  Specifies the step for a sequence. A positive number generates an ascending sequence, and a negative number generates a decreasing sequence.
+
+  The default value is **1**.
+
+- **MINVALUE minvalue | NO MINVALUE| NOMINVALUE**
+
+  Specifies the minimum value of the sequence. If **MINVALUE** is not declared, or **NO MINVALUE** is declared, the default value of the ascending sequence is **1**, and that of the descending sequence is **-263-1**. **NOMINVALUE** is equivalent to **NO MINVALUE**.
+
+- **MAXVALUE maxvalue | NO MAXVALUE| NOMAXVALUE**
+
+  Specifies the maximum value of the sequence. If **MAXVALUE** is not declared, or **NO MAXVALUE** is declared, the default value of the ascending sequence is **263-1**, and that of the descending sequence is **-1**. **NOMAXVALUE** is equivalent to **NO MAXVALUE**.
+
+- **start**
+
+  Specifies the start value of the sequence. The default value for an ascending sequence is **minvalue** and that for a descending sequence is **maxvalue**.
+
+- **cache**
+
+  Specifies the number of sequences stored in the memory for quick access purposes.
+
+  Default value **1** indicates that one sequence can be generated each time.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  > It is not recommended that you define **cache** and **maxvalue** or **minvalue** at the same time. The continuity of sequences cannot be ensured after **cache** is defined because unacknowledged sequences may be generated, causing waste of sequences.
+
+- **CYCLE**
+
+  Recycles sequences after the number of sequences reaches **maxvalue** or **minvalue**.
+
+  If **NO CYCLE** is specified, any invocation of **nextval** would return an error after the number of sequences reaches **maxvalue** or **minvalue**.
+
+  **NOCYCLE** is equivalent to **NO CYCLE**.
+
+  The default value is **NO CYCLE**.
+
+  If **CYCLE** is specified, the sequence uniqueness cannot be ensured.
+
+- **OWNED BY**
+
+  Associates a sequence with a specified column included in a table. In this way, the sequence will be deleted when you delete its associated column or the table where the column belongs to. The associated table and sequence must be owned by the same user and in the same schema. **OWNED BY** only establishes the association between a table column and the sequence. Sequences on the column do not increase automatically when data is inserted.
+
+  The default value **OWNED BY NONE** indicates that such association does not exist.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+  > You are not advised to use the sequence created using **OWNED BY** in other tables. If multiple tables need to share a sequence, the sequence must not belong to a specific table.
+
+## Examples
+
+Create an ascending sequence named **serial**, which starts from 101.
+
+```sql
+mogdb=# CREATE SEQUENCE serial
+ START 101
+ CACHE 20;
+```
+
+Select the next number from the sequence.
+
+```sql
+mogdb=# SELECT nextval('serial');
+ nextval
+ ---------
+      101
+```
+
+Select the next number from the sequence.
+
+```sql
+mogdb=# SELECT nextval('serial');
+ nextval
+ ---------
+      102
+```
+
+Create a sequence associated with the table.
+
+```sql
+mogdb=# CREATE TABLE customer_address
+(
+    ca_address_sk             integer               not null,
+    ca_address_id             char(16)              not null,
+    ca_street_number          char(10)                      ,
+    ca_street_name            varchar(60)                   ,
+    ca_street_type            char(15)                      ,
+    ca_suite_number           char(10)                      ,
+    ca_city                   varchar(60)                   ,
+    ca_county                 varchar(30)                   ,
+    ca_state                  char(2)                       ,
+    ca_zip                    char(10)                      ,
+    ca_country                varchar(20)                   ,
+    ca_gmt_offset             decimal(5,2)                  ,
+    ca_location_type          char(20)
+);
+
+mogdb=# CREATE SEQUENCE serial1
+ START 101
+ CACHE 20
+OWNED BY customer_address.ca_address_sk;
+-- Delete a table and sequence
+mogdb=# DROP TABLE customer_address;
+mogdb=# DROP SEQUENCE serial cascade;
+mogdb=# DROP SEQUENCE serial1 cascade;
+```
+
+## Helpful Links
+
+[DROP SEQUENCE](92-DROP-SEQUENCE)，[ALTER SEQUENCE](16-ALTER-SEQUENCE)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/58-CREATE-SERVER.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/58-CREATE-SERVER.md
new file mode 100644
index 0000000000000000000000000000000000000000..04e764894b77c72600bd9812727c0f82d600968b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/58-CREATE-SERVER.md
@@ -0,0 +1,120 @@
+---
+title: CREATE SERVER
+summary: CREATE SERVER
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE SERVER
+
+## Function
+
+**CREATE SERVER** defines a new foreign server.
+
+## Syntax
+
+```ebnf+diagram
+CreateServer ::= CREATE SERVER server_name
+    FOREIGN DATA WRAPPER fdw_name
+    OPTIONS ( { option_name ' value ' } [, ...] ) ;
+```
+
+## Parameter Description
+
+- **server_name**
+
+  Specifies the server name.
+
+  Value range: a string containing no more than 63 characters
+
+- **fdw_name**
+
+  Specifies the name of the foreign data wrapper.
+
+  Value range:  **oracle_fdw**,  **mysql_fdw**,  **postgres_fdw**,  **mot_fdw**, and  **file_fdw**
+
+- **OPTIONS ( { option_name ' value ' } [, …] )**
+
+    Specifies options for the server. These options typically define the connection details of the server, but the actual names and values depend on the foreign data wrapper of the server.
+
+  - Options supported by  **oracle_fdw**  are as follows:
+
+    - **dbserver**
+
+        Connection string of the remote Oracle database.
+
+    - **isolation_level** (default value: **serializable**)
+
+        Oracle database transaction isolation level.
+
+        Value range: serializable, read_committed, and read_only
+
+  - Options supported by mysql_fdw are as follows:
+
+    - **host** (default value: **127.0.0.1**)
+
+        IP address of the MySQL server or MariaDB.
+
+    - **port** (default value: **3306**)
+
+        Listening port number of the MySQL server or MariaDB.
+
+  - The options supported by postgres_fdw are the same as those supported by libpq. For details, see [Connection Character Strings](6-connection-characters). Note that the following options cannot be set:
+
+    - **user** and **password**
+
+        The user name and password are specified when the user mapping is created.
+
+    - **client_encoding**
+
+        The encoding mode of the local server is automatically obtained and set.
+
+    - **application_name**
+
+        This option is always set to **postgres_fdw**.
+
+  - Specifies the parameters for the foreign server. The detailed parameter description is as follows:
+
+    - encrypt
+
+        Specifies whether data is encrypted. This parameter is available only when **type** is **OBS**. The default value is **on**.
+
+         Value range:
+
+      - **on** indicates that data is encrypted and HTTPS is used for communication.
+      - **off** indicates that data is not encrypted and HTTP is used for communication.
+
+    - access_key
+
+        Specifies the access key (AK) (obtained by users from the OBS console) used for the OBS access protocol. When you create a foreign table, the AK value is encrypted and saved to the metadata table of the database. This parameter is available only when **type** is set to **OBS**.
+
+    - secret_access_key
+
+        Specifies the secret key (SK) value (obtained by users from the OBS console) used for the OBS access protocol. When you create a foreign table, the SK value is encrypted and saved to the metadata table of the database. This parameter is available only when **type** is set to **OBS**.
+
+In addition to the connection parameters supported by libpq, the following options are provided:
+
+- **use_remote_estimate**
+
+  Controls whether  **postgres_fdw**  issues the EXPLAIN command to obtain the estimated run time. The default value is  **false**.
+
+- **fdw_startup_cost**
+
+  Estimates the startup time required for a foreign table scan, including the time to establish a connection, analyzes the request at the remote server, and generates a plan. The default value is  **100**.
+
+- **fdw_typle_cost**
+
+  Specifies the additional consumption when each tuple is scanned on a remote server. The value specifies the extra consumption of data transmission between servers. The default value is **0.01**.
+
+## Examples
+
+Create a server.
+
+```sql
+mogdb=# create server my_server foreign data wrapper log_fdw;
+CREATE SERVER
+```
+
+## Helpful Links
+
+[ALTER SERVER](17-ALTER-SERVER)  and  [DROP SERVER](93-DROP-SERVER)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/59-CREATE-SYNONYM.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/59-CREATE-SYNONYM.md
new file mode 100644
index 0000000000000000000000000000000000000000..15350c9be686c164346b20c114675002f48f6e03
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/59-CREATE-SYNONYM.md
@@ -0,0 +1,112 @@
+---
+title: CREATE SYNONYM
+summary: CREATE SYNONYM
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE SYNONYM
+
+## Function
+
+**CREATE SYNONYM** creates a synonym object. A synonym is an alias of a database object and is used to record the mapping between database object names. You can use synonyms to access associated database objects.
+
+## Precautions
+
+- The user of a synonym should be its owner.
+- If the schema name is specified, create a synonym in the specified schema. Otherwise create a synonym in the current schema.
+- Database objects that can be accessed using synonyms include tables, views, functions, and stored procedures.
+- To use synonyms, you must have the required permissions on associated objects.
+- The following DML statements support synonyms: **SELECT**, **INSERT**, **UPDATE**, **DELETE**, **EXPLAIN**, and **CALL**.
+- It is not recommended to create synonyms for temporary tables. If you need to create it, you need to specify the schema name of the target temporary table of the synonym, responsible for the inability to use the synonym, and execute the DROP SYNONYM command before the end of the current session.
+
+## Syntax
+
+```ebnf+diagram
+CreateSynonym ::= CREATE [ OR REPLACE ] SYNONYM synonym_name
+    FOR object_name;
+```
+
+## Parameter Description
+
+- **synonym**
+
+  Specifies the name of the synonym to be created, which can contain the schema name.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **object_name**
+
+  Specifies the name of an object that is associated (optionally with schema names).
+
+  Value range: a string. It must comply with the naming convention.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  > **object_name** can be the name of an object that does not exist.
+
+## Examples
+
+```sql
+-- Create schema ot.
+mogdb=# CREATE SCHEMA ot;
+
+-- Create table ot.t1 and its synonym t1.
+mogdb=# CREATE TABLE ot.t1(id int, name varchar2(10));
+mogdb=# CREATE OR REPLACE SYNONYM t1 FOR ot.t1;
+
+-- Use synonym t1.
+mogdb=# SELECT * FROM t1;
+mogdb=# INSERT INTO t1 VALUES (1, 'ada'), (2, 'bob');
+mogdb=# UPDATE t1 SET t1.name = 'cici' WHERE t1.id = 2;
+
+-- Create synonym v1 and its associated view ot.v_t1.
+mogdb=# CREATE SYNONYM v1 FOR ot.v_t1;
+mogdb=# CREATE VIEW ot.v_t1 AS SELECT * FROM ot.t1;
+
+-- Use synonym v1.
+mogdb=# SELECT * FROM v1;
+
+-- Create overloaded function ot.add and its synonym add.
+mogdb=# CREATE OR REPLACE FUNCTION ot.add(a integer, b integer) RETURNS integer AS
+$$
+SELECT $1 + $2
+$$
+LANGUAGE sql;
+
+mogdb=# CREATE OR REPLACE FUNCTION ot.add(a decimal(5,2), b decimal(5,2)) RETURNS decimal(5,2) AS
+$$
+SELECT $1 + $2
+$$
+LANGUAGE sql;
+
+mogdb=# CREATE OR REPLACE SYNONYM add FOR ot.add;
+
+-- Use synonym add.
+mogdb=# SELECT add(1,2);
+mogdb=# SELECT add(1.2,2.3);
+
+-- Create stored procedure ot.register and its synonym register.
+mogdb=# CREATE PROCEDURE ot.register(n_id integer, n_name varchar2(10))
+SECURITY INVOKER
+AS
+BEGIN
+    INSERT INTO ot.t1 VALUES(n_id, n_name);
+END;
+/
+
+mogdb=# CREATE OR REPLACE SYNONYM register FOR ot.register;
+
+-- Use synonym register to invoke the stored procedure.
+mogdb=# CALL register(3,'mia');
+
+-- Delete the synonym.
+mogdb=# DROP SYNONYM t1;
+mogdb=# DROP SYNONYM IF EXISTS v1;
+mogdb=# DROP SYNONYM IF EXISTS add;
+mogdb=# DROP SYNONYM register;
+mogdb=# DROP SCHEMA ot CASCADE;
+```
+
+## Helpful Links
+
+[ALTER SYNONYM](19-ALTER-SYNONYM)，[DROP SYNONYM](94-DROP-SYNONYM)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/6-ALTER-FOREIGN-TABLE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/6-ALTER-FOREIGN-TABLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..a1c799abac6efcd21472cec574bbc2bd8ec4f0e9
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/6-ALTER-FOREIGN-TABLE.md
@@ -0,0 +1,118 @@
+---
+title: ALTER FOREIGN TABLE
+summary: ALTER FOREIGN TABLE
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER FOREIGN TABLE
+
+## Function
+
+**ALTER FOREIGN TABLE** modifies a foreign table.
+
+## Syntax
+
+```ebnf+diagram
+AlterForeignTable ::= ALTER FOREIGN TABLE [ IF EXISTS ]  table_name
+    OPTIONS ( {[ ADD | SET | DROP ] option ['value']}[, ... ]);
+```
+
+```ebnf+diagram
+AlterForeignTable ::= ALTER FOREIGN TABLE [ IF EXISTS ] table_name
+    ALTER column_name OPTIONS;
+```
+
+## Parameter Description
+
+- **table_name**
+
+  Specifies the name of an existing foreign table to be modified.
+
+  Value range: an existing foreign table name.
+
+- **option**
+
+    Specifies the option of a foreign table or foreign table column to be modified. **ADD**, **SET**, and **DROP** are operations to be performed. If no operation is set explicitly, the default value **ADD** is used. The option name must be unique (although table options and table column options can share the same name). The name and value of the option are also validated by a class library of a foreign data wrapper.
+
+  - Options supported by **oracle_fdw** are as follows:
+
+    - **table**
+
+        Name of a table on the Oracle server. The value must be the same as the table name recorded in the Oracle system catalog. Generally, the value consists of uppercase letters.
+
+    - **schema**
+
+        Schema (or owner) corresponding to the table. The value must be the same as the table name recorded in the Oracle system catalog. Generally, the value consists of uppercase letters.
+
+  - Options supported by **mysql_fdw** are as follows:
+
+    - **dbname**
+
+        Name of the MySQL database.
+
+    - **table_name**
+
+        Name of a table in the MySQL database.
+
+  - Options supported by **postgres_fdw** are as follows:
+
+    - **schema_name**
+
+        Schema name of a remote server. If this option is not specified, the schema name of the foreign table is used as the schema name of the remote server.
+
+    - **table_name**
+
+        Table name of a remote server. If this option is not specified, the name of the foreign table is used as the table name of the remote server.
+
+    - **column_name**
+
+        Column name of a table on a remote server. If this option is not specified, the column name of the foreign table is used as the column name of a table on a remote server.
+
+- Options supported by **file_fdw** are as follows:
+
+  - filename
+
+    File to be read. This parameter is mandatory and must be an absolute path.
+
+  - format
+
+    File format of the remote server, which is the same as the **FORMAT** option in the **COPY** statement. The value can be **text**, **csv**, **binary**, or **fixed**.
+
+  - header
+
+    Specifies whether a specified file has a header, which is the same as the **HEADER** option of the **COPY** statement.
+
+  - delimiter
+
+      File delimiter, which is the same as the **DELIMITER** option of the **COPY** statement.
+
+  - quote
+
+      Quote character of a file, which is the same as the **QUOTE** option of the **COPY** statement.
+
+  - escape
+
+      Escape character of a file, which is the same as the **ESCAPE** option of the **COPY** statement.
+
+  - null
+
+      Null string of a file, which is the same as the **NULL** option of the **COPY** statement.
+
+  - encoding
+
+      Encoding of a file, which is the same as the **ENCODING** option of the **COPY** statement.
+
+  - force_not_null
+
+      This is a Boolean option. If it is true, the value of the declared field cannot be an empty string. This option is the same as the **FORCE_NOT_NULL** option of the **COPY** statement.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** For details about how to use **file_fdw**, see [file_fdw](file_fdw).
+
+- **value**
+
+  Specifies the new value of **option**.
+
+## Helpful Links
+
+[CREATE FOREIGN TABLE](47-CREATE-FOREIGN-TABLE)，[DROP FOREIGN TABLE](81-DROP-FOREIGN-TABLE)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/60-CREATE-TABLE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/60-CREATE-TABLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..c44d4d7a55ca6c6b04096fa1cfdb4492e971764a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/60-CREATE-TABLE.md
@@ -0,0 +1,962 @@
+---
+title: CREATE TABLE
+summary: CREATE TABLE
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE TABLE
+
+## Function
+
+**CREATE TABLE** is used to create an initially empty table in the current database. The table will be owned by the creator.
+
+## Precautions
+
+- For details about the data types supported by column-store tables, see [Data Types Supported by Column-store Tables](16-data-types-supported-by-column-store-tables).
+- Column-store tables do not support the array.
+- Column-store tables do not support column generation.
+- Column-store tables cannot be created as global temporary tables.
+- It is recommended that the number of column-store tables do not exceed 1000.
+- If an error occurs during table creation, after it is fixed, the system may fail to delete the empty disk files created before the last automatic clearance. This problem seldom occurs and does not affect system running of the database.
+- Only  **PARTIAL CLUSTER KEY**,  **UNIQUE**, and  **PRIAMRY KEY**  can be used as the table-level constraint of column-store tables. Table-level primary key and foreign key constraints are not supported.
+- Only the  **NULL**,  **NOT NULL**, **DEFAULT**  constant values, **UNIQUE** and **PRIMARY KEY** can be used as column-store table constraints.
+- Whether column-store tables support a delta table is specified by the  enable_delta_store  parameter. The threshold for storing data into a delta table is specified by the  **deltarow_threshold**  parameter.
+- When JDBC is used, the **DEFAULT** value can be set through **PrepareStatement**.
+- The maximum number of columns on each table is 1600, which depends on the column type. The total size of all columns cannot exceed 8192 bytes, except for the columns of variable data types, such as text, varchar, and char.
+
+## Syntax
+
+Create a table.
+
+```ebnf+diagram
+CreateTable ::= CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXISTS ] table_name
+    ({ column_name data_type [ compress_mode ] [ COLLATE collation ] [ column_constraint [ ... ] ]
+        | table_constraint
+        | LIKE source_table [ like_option [...] ] }
+        [, ... ])
+    [ WITH ( {storage_parameter = value} [, ... ] ) ]
+    [ ON COMMIT { PRESERVE ROWS | DELETE ROWS | DROP } ]
+    [ COMPRESS | NOCOMPRESS ]
+    [ TABLESPACE tablespace_name ];
+```
+
+- **column_constraint** is as follows:
+
+  ```ebnf+diagram
+  column_constraint ::= [ CONSTRAINT constraint_name ]
+  { NOT NULL |
+    NULL |
+    CHECK ( expression ) |
+    DEFAULT default_expr |
+    UNIQUE index_parameters |
+    PRIMARY KEY index_parameters |
+    REFERENCES reftable [ ( refcolumn ) ] [ MATCH FULL | MATCH PARTIAL | MATCH SIMPLE ]
+        [ ON DELETE action ] [ ON UPDATE action ] }
+  [ DEFERRABLE | NOT DEFERRABLE | INITIALLY DEFERRED | INITIALLY IMMEDIATE ]
+  ```
+
+- **compress_mode** is as follows:
+
+  ```ebnf+diagram
+  compress_mode ::= { DELTA | PREFIX | DICTIONARY | NUMSTR | NOCOMPRESS }
+  ```
+
+- **table_constraint** is as follows:
+
+  ```ebnf+diagram
+   table_constraint ::= [ CONSTRAINT constraint_name ]
+    { CHECK ( expression ) |
+      UNIQUE ( column_name [, ... ] ) index_parameters |
+      PRIMARY KEY ( column_name [, ... ] ) index_parameters |
+      FOREIGN KEY ( column_name [, ... ] ) REFERENCES reftable [ (refcolumn [, ... ] ) ]
+          [ MATCH FULL | MATCH PARTIAL | MATCH SIMPLE ] [ ON DELETE action ] [ ON UPDATE action ] |
+      PARTIAL CLUSTER KEY ( column_name [, ... ] ) }
+    [ DEFERRABLE | NOT DEFERRABLE | INITIALLY DEFERRED | INITIALLY IMMEDIATE ]
+  ```
+
+- **like_option** is as follows:
+
+  ```ebnf+diagram
+  like_option ::= { INCLUDING | EXCLUDING } { DEFAULTS | GENERATED | CONSTRAINTS | INDEXES | STORAGE | COMMENTS | PARTITION | RELOPTIONS | ALL }
+  ```
+
+- **index_parameters** is as follows:
+
+  ```ebnf+diagram
+  index_parameters ::= [ WITH ( {storage_parameter = value} [, ... ] ) ]
+  [ USING INDEX TABLESPACE tablespace_name ]
+  ```
+
+## Parameter Description
+
+- **UNLOGGED**
+
+  If this keyword is specified, the created table is an unlogged table. Data written to unlogged tables is not written to the WALs, which makes them considerably faster than ordinary tables. However, an unlogged table is automatically truncated after a crash or unclean shutdown, incurring data loss risks. Contents of an unlogged table are also not replicated to standby servers. Any indexes created on an unlogged table are not automatically logged as well.
+
+  Usage scenario: Unlogged tables do not ensure data security. Users can back up data before using unlogged tables; for example, users should back up the data before a system upgrade.
+
+  Troubleshooting: If data is missing in the indexes of unlogged tables due to some unexpected operations such as an unclean shutdown, users should re-create the indexes with errors.
+
+- **GLOBAL | LOCAL**
+
+  When creating a temporary table, you can specify the **GLOBAL** or **LOCAL** keyword before **TEMP** or **TEMPORARY**. If the keyword **GLOBAL** is specified, MogDB creates a global temporary table. Otherwise, MogDB creates a local temporary table.
+
+- **TEMPORARY | TEMP**
+
+  If **TEMP** or **TEMPORARY** is specified, the created table is a temporary table. Temporary tables are classified into global temporary tables and local temporary tables. If the keyword **GLOBAL** is specified when a temporary table is created, the table is a global temporary table. Otherwise, the table is a local temporary table.
+
+  The metadata of the global temporary table is visible to all sessions. After the sessions end, the metadata still exists. The user data, indexes, and statistics of a session are isolated from those of another session. Each session can only view and modify the data submitted by itself. Global temporary tables have two schemas: **ON COMMIT PRESERVE ROWS** and **ON COMMIT PRESERVE ROWS**. In session-based **ON COMMIT PRESERVE ROWS** schema, user data is automatically cleared when a session ends. In transaction-based **ON COMMIT DELETE ROWS** schema, user data is automatically cleared when the commit or rollback operation is performed. If the **ON COMMIT** option is not specified during table creation, the session level is used by default. Different from local temporary tables, you can specify a schema that does not start with **pg_temp_** when creating a global temporary table.
+
+  A local temporary table is automatically dropped at the end of the current session. Therefore, you can create and use temporary tables in the current session as long as the connected database node in the session is normal. Temporary tables are created only in the current session. If a DDL statement involves operations on temporary tables, a DDL error will be generated. Therefore, you are not advised to perform operations on temporary tables in DDL statements. **TEMP** is equivalent to **TEMPORARY**.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+  >
+  > - Local temporary tables are visible to the current session through the schema starting with **pg_temp** start. Users should not delete schema started with **pg_temp** or **pg_toast_temp**.
+  > - If **TEMPORARY** or **TEMP** is not specified when you create a table but its schema is set to that starting with **pg_temp_** in the current session, the table will be created as a temporary table.
+  > - If global temporary tables and indexes are being used by other sessions, do not perform **ALTER** or **DROP**.
+  > - The DDL of a global temporary table affects only the user data and indexes of the current session. For example, **TRUNCATE**, **REINDEX**, and **ANALYZE** are valid only for the current session.
+  > - You can set the GUC parameter  **max_active_global_temporary_table**  to determine whether to enable the global temporary table function. If  **max_active_global_temporary_table**  is set to  **0**, the global temporary table function is disabled.
+  > - A temporary table is visible only to the current session. Therefore, it cannot be used together with  **\\parallel on**.
+  > - **\\parallel on**: The temporary table does not support primary/standby switchover.
+
+- **IF NOT EXISTS**
+
+  Sends a notice, but does not throw an error, if a table with the same name exists.
+
+- **table_name**
+
+  Specifies the name of the table to be created.
+
+- **column_name**
+
+  Specifies the name of a column to be created in the new table.
+
+- **data_type**
+
+  Specifies the data type of the column.
+
+- **compress_mode**
+
+  Specifies the compression option of the table. The option specifies the algorithm preferentially used by table columns.
+
+  Value range: **DELTA**, **PREFIX**, **DICTIONARY**, **NUMSTR**, and **NOCOMPRESS**
+
+- **COLLATE collation**
+
+    Assigns a collation to the column (which must be of a collatable data type). If no collation is specified, the default collation is used. You can run the **select \* from pg_collation;** command to query collation rules from the **pg_collation** system catalog. The default collation rule is the row starting with **default** in the query result.
+
+- **LIKE source_table [ like_option … ]**
+
+    Specifies a table from which the new table automatically copies all column names, their data types, and their not-null constraints.
+
+    The new table and the original table are decoupled after creation is complete. Changes to the original table will not be applied to the new table, and it is not possible to include data of the new table in scans of the original table.
+
+    Columns and constraints copied by **LIKE** are not merged with the same name. If the same name is specified explicitly or in another **LIKE** clause, an error is reported.
+
+  - The default expressions are copied from the original table to the new table only if **INCLUDING DEFAULTS** is specified. The default behavior is to exclude default expressions, resulting in the copied columns in the new table having default values null.
+  - The **CHECK** constraints are copied from the original table to the new table only when **INCLUDING CONSTRAINTS** is specified. Other types of constraints are never copied to the new table. Not-null constraints are always copied to the new table. These rules also apply to column constraints and table constraints.
+  - Any indexes on the original table will not be created on the new table, unless the **INCLUDING INDEXES** clause is specified.
+  - **STORAGE** settings for the copied column definitions are copied only if **INCLUDING STORAGE** is specified. The default behavior is to exclude **STORAGE** settings.
+  - If **INCLUDING COMMENTS** is specified, comments for the copied columns, constraints, and indexes are copied. The default behavior is to exclude comments.
+  - If **INCLUDING PARTITION** is specified, the partition definitions of the source table are copied to the new table, and the new table no longer uses the **PARTITION BY** clause. The default behavior is to exclude partition definition of the original table. If the source table has an index, you can use the  **INCLUDING PARTITION INCLUDING INDEXES**  syntax. If only  **INCLUDING INDEXES**  is used for a partitioned table, the target table will be defined as an ordinary table, but the index is a partitioned index. In this case, an error will be reported because ordinary tables do not support partitioned indexes.
+  - If **INCLUDING RELOPTIONS** is specified, the new table will copy the storage parameter (that is, **WITH** clause) of the source table. The default behavior is to exclude partition definition of the storage parameter of the original table.
+  - **INCLUDING ALL** contains the meaning of **INCLUDING DEFAULTS**, **INCLUDING CONSTRAINTS**, **INCLUDING INDEXES**, **INCLUDING STORAGE**, **INCLUDING COMMENTS**, **INCLUDING PARTITION**, and **INCLUDING RELOPTIONS**.
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+    >
+    > - If the source table contains a sequence with the **SERIAL**, **BIGSERIAL**, or **SMALLSERIAL** data type, or a column in the source table is a sequence by default and the sequence is created for this table by using **CREATE SEQUENCE…** **OWNED BY**, these sequences will not be copied to the new table, and another sequence specific to the new table will be created. This is different from earlier versions. To share a sequence between the source table and new table, create a shared sequence (do not use **OWNED BY**) and set a column in the source table to this sequence.
+    > - You are not advised to set a column in the source table to the sequence specific to another table especially when the table is distributed in specific node groups, because doing so may result in **CREATE TABLE … LIKE** execution failures. In addition, doing so may cause the sequence to become invalid in the source sequence because the sequence will also be deleted from the source table when it is deleted from the table that the sequence is specific to. To share a sequence among multiple tables, you are advised to create a shared sequence for them.
+    > - **EXCLUDING**  of a partitioned table must be used together with  **INCLUDING ALL**, for example,  **INCLUDING ALL EXCLUDING DEFAULTS**, except for  **DEFAULTS**  of the source partitioned table.
+
+- **WITH ( { storage_parameter = value } [, … ] )**
+
+    Specifies an optional storage parameter for a table or an index.
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** When using **Numeric** of any precision to define a column, specifies precision **p** and scale **s**. When precision and scale are not specified, the input will be displayed.
+
+    The description of parameters is as follows:
+
+  - FILLFACTOR
+
+    The fill factor of a table is a percentage from 10 to 100. **100** (complete filling) is the default value. When a smaller fill factor is specified, **INSERT** operations pack table pages only to the indicated percentage. The remaining space on each page is reserved for updating rows on that page. This gives **UPDATE** a chance to place the updated copy of a row on the same page, which is more efficient than placing it on a different page. For a table whose entries are never updated, setting the fill factor to **100** (complete filling) is the best choice, but in heavily updated tables a smaller fill factor would be appropriate. The parameter has no meaning for column-store tables.
+
+    Value range: 10-100
+
+  - ORIENTATION
+
+    Specifies the storage mode (row-store, column-store, or ORC) of table data. This parameter cannot be modified once it is set.
+
+    Value range:
+
+    - **ROW** indicates that table data is stored in rows.
+
+        **ROW** applies to OLTP service and scenarios with a large number of point queries or addition/deletion operations.
+
+    - **COLUMN** indicates that the data is stored in columns.
+
+        **COLUMN** applies to the data warehouse service, which has a large amount of aggregation computing, and involves a few column operations.
+
+        Default value:
+
+        If an ordinary tablespace is specified, the default is **ROW**.
+
+  - STORAGE_TYPE
+
+    Specifies the storage engine type. This parameter cannot be modified once it is set.
+
+    Value range:
+
+    - **USTORE**  indicates that tables support the Inplace-Update storage engine.
+    - **ASTORE**  indicates that tables support the Append-Only storage engine.
+
+    Default value:
+
+    If no table is specified, data is stored in Append-Only mode by default.
+
+  - COMPRESSION <a id = 'COMPRESSION'> </a>
+
+    Specifies the compression level of table data. It determines the compression ratio and time. Generally, the higher the level of compression, the higher the ratio, the longer the time; and the lower the level of compression, the lower the ratio, the shorter the time. The actual compression ratio depends on the distribution mode of table data loaded. MogDB supports compression of row-store tables since version 2.1.
+
+    Value range:
+
+    The valid values for column-store tables are **YES**, **NO**, **LOW**, **MIDDLE**, and **HIGH**, and the default value is **LOW**.
+
+  - COMPRESSLEVEL
+
+    Specifies the table data compression ratio and duration at the same compression level. This divides a compression level into sublevels, providing more choices for compression ratio and duration. As the value becomes greater, the compression ratio becomes higher and duration longer at the same compression level.
+
+    Value range: 0 to 3. The default value is **0**.
+
+  - MAX_BATCHROW
+
+    Specifies the maximum number of rows in a storage unit during data loading. The parameter is only valid for column-store tables.
+
+    Value range: 10000 to 60000. The default value is **60000**.
+
+  - PARTIAL_CLUSTER_ROWS
+
+    Specifies the number of records to be partially clustered for storage during data loading. The parameter is only valid for column-store tables.
+
+    Value range: greater than or equal to **MAX_BATCHROW**. You are advised to set this parameter to an integer multiple of **MAX_BATCHROW**.
+
+  - DELTAROW_THRESHOLD
+
+    Specifies the upper limit of to-be-imported rows for triggering the data import to a delta table when data of a column-store table is to be imported. This parameter takes effect only if **enable_delta_store** is set to **on**. The parameter is only valid for column-store tables.
+
+    Value range: from 0 to 9999. The default value is **100**.
+
+  - VERSION
+
+    Specifies the version of ORC storage format.
+
+    Value range: 0.12. ORC 0.12 format is supported currently. More formats will be supported as the development of ORC format.
+
+    Default value: **0.12**
+
+  - segment
+
+    The data is stored in segment-page mode. This parameter supports only row-store tables. Column-store tables, temporary tables, and unlogged tables are not supported. The ustore storage engine is not supported.
+
+    Value range:  **on**  and  **off**
+
+    Default value:  **off**
+
+  - dek_cipher
+
+    Ciphertext of the key used for transparent data encryption. When  **enable_tde**  is enabled, the system automatically applies for ciphertext creation. You cannot specify the ciphertext. The key rotation function can be used to update the key.
+
+    Value range: a string.
+
+    If encryption is disabled, the default value is null by default.
+
+- **ON COMMIT { PRESERVE ROWS | DELETE ROWS | DROP }**
+
+    **ON COMMIT** determines what to do when you commit a temporary table creation operation. The three options are as follows. Currently, only **PRESERVE ROWS** and **DELETE ROWS** can be used.
+
+  - **PRESERVE ROWS** (default): No special action is taken at the ends of transactions. The temporary table and its table data are unchanged.
+  - **DELETE ROWS**: All rows in the temporary table will be deleted at the end of each transaction block.
+  - **DROP**: The temporary table will be dropped at the end of the current transaction block. Only local temporary tables can be dropped. Global temporary tables cannot be dropped.
+
+- **COMPRESS | NOCOMPRESS**
+
+  If you specify **COMPRESS** in the **CREATE TABLE** statement, the compression feature is triggered in case of a bulk **INSERT** operation. If this feature is enabled, a scan is performed for all tuple data within the page to generate a dictionary and then the tuple data is compressed and stored. If **NOCOMPRESS** is specified, the table is not compressed.
+
+  Default value: **NOCOMPRESS**, that is, tuple data is not compressed before storage.
+
+- **TABLESPACE tablespace_name**
+
+  Specifies the tablespace where the new table is created. If not specified, the default tablespace is used.
+
+- **CONSTRAINT constraint_name**
+
+    Specifies the name of a column or table constraint. The optional constraint clauses specify constraints that new or updated rows must satisfy for an insert or update operation to succeed.
+
+    There are two ways to define constraints:
+
+  - A column constraint is defined as part of a column definition, and it is bound to a particular column.
+  - A table constraint is not bound to a particular column but can apply to more than one column.
+
+- **NOT NULL**
+
+    The column is not allowed to contain null values.
+
+- **NULL**
+
+    The column is allowed to contain null values. This is the default setting.
+
+    This clause is only provided for compatibility with non-standard SQL databases. It is not recommended.
+
+- **CHECK ( expression )**
+
+    Specifies an expression producing a Boolean result where the insert or update operation of new or updated rows can succeed only when the expression result is **TRUE** or **UNKNOWN**; otherwise, an error is thrown and the database is not altered.
+
+    A check constraint specified as a column constraint should reference only the column's values, while an expression appearing in a table constraint can reference multiple columns.
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** **&lt;&gt;NULL** and **!=NULL** are invalid in an expression. Change them to **IS NOT NULL**.
+
+- **DEFAULT default_expr**
+
+    Assigns a default data value for a column. The value can be any variable-free expressions. (Subqueries and cross-references to other columns in the current table are not allowed.) The data type of the default expression must match the data type of the column.
+
+    The default expression will be used in any insert operation that does not specify a value for the column. If there is no default value for a column, then the default value is null.
+
+- **UNIQUE index_parameters**
+
+  **UNIQUE ( column_name [, … ] ) index_parameters**
+
+  Specifies that a group of one or more columns of a table can contain only unique values.
+
+  For the purpose of a unique constraint, null is not considered equal.
+
+- **PRIMARY KEY index_parameters**
+
+  **PRIMARY KEY ( column_name [, … ] ) index_parameters**
+
+  Specifies that a column or columns of a table can contain only unique (non-duplicate) and non-null values.
+
+  Only one primary key can be specified for a table.
+
+- **DEFERRABLE | NOT DEFERRABLE**
+
+  They determine whether the constraint is deferrable. A constraint that is not deferrable will be checked immediately after every command. Checking of constraints that are deferrable can be postponed until the end of the transaction using the **SET CONSTRAINTS** command. **NOT DEFERRABLE** is the default value. Currently, only UNIQUE constraints, primary key constraints, and foreign key constraints accept this clause. All the other constraints are not deferrable.
+
+- **PARTIAL CLUSTER KEY**
+
+  Specifies a partial cluster key for storage. When importing data to a column-store table, you can perform local data sorting by specified columns (single or multiple).
+
+- **INITIALLY IMMEDIATE | INITIALLY DEFERRED**
+
+    If a constraint is deferrable, this clause specifies the default time to check the constraint.
+
+  - If the constraint is **INITIALLY IMMEDIATE** (default value), it is checked after each statement.
+  - If the constraint is **INITIALLY DEFERRED**, it is checked only at the end of the transaction.
+
+    The constraint check time can be altered using the **SET CONSTRAINTS** statement.
+
+- **USING INDEX TABLESPACE tablespace_name**
+
+  Allows selection of the tablespace in which the index associated with a **UNIQUE** or **PRIMARY KEY** constraint will be created. If not specified, **default_tablespace** is consulted, or the default tablespace in the database if **default_tablespace** is empty.
+
+- **ENCRYPTION_TYPE = encryption_type_value**
+
+  For the encryption type in the ENCRYPTED WITH constraint, the value of  **encryption_type_value**  is  **DETERMINISTIC**  or  **RANDOMIZED**.
+
+## Example
+
+```sql
+-- Create a simple table.
+mogdb=# CREATE TABLE tpcds.warehouse_t1
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2)
+);
+
+mogdb=# CREATE TABLE tpcds.warehouse_t2
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)         DICTIONARY,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2)
+);
+-- Create a table and set the default value of the W_STATE column to GA.
+mogdb=# CREATE TABLE tpcds.warehouse_t3
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)           DEFAULT 'GA',
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2)
+);
+
+-- Create a table and check whether the W_WAREHOUSE_NAME column is unique at the end of its creation.
+mogdb=# CREATE TABLE tpcds.warehouse_t4
+(
+    W_WAREHOUSE_SK            INTEGER                NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)               NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)   UNIQUE DEFERRABLE,
+    W_WAREHOUSE_SQ_FT         INTEGER                        ,
+    W_STREET_NUMBER           CHAR(10)                       ,
+    W_STREET_NAME             VARCHAR(60)                    ,
+    W_STREET_TYPE             CHAR(15)                       ,
+    W_SUITE_NUMBER            CHAR(10)                       ,
+    W_CITY                    VARCHAR(60)                    ,
+    W_COUNTY                  VARCHAR(30)                    ,
+    W_STATE                   CHAR(2)                        ,
+    W_ZIP                     CHAR(10)                       ,
+    W_COUNTRY                 VARCHAR(20)                    ,
+    W_GMT_OFFSET              DECIMAL(5,2)
+);
+-- Create a table with its fill factor set to 70%.
+mogdb=# CREATE TABLE tpcds.warehouse_t5
+(
+    W_WAREHOUSE_SK            INTEGER                NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)               NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                    ,
+    W_WAREHOUSE_SQ_FT         INTEGER                        ,
+    W_STREET_NUMBER           CHAR(10)                       ,
+    W_STREET_NAME             VARCHAR(60)                    ,
+    W_STREET_TYPE             CHAR(15)                       ,
+    W_SUITE_NUMBER            CHAR(10)                       ,
+    W_CITY                    VARCHAR(60)                    ,
+    W_COUNTY                  VARCHAR(30)                    ,
+    W_STATE                   CHAR(2)                        ,
+    W_ZIP                     CHAR(10)                       ,
+    W_COUNTRY                 VARCHAR(20)                    ,
+    W_GMT_OFFSET              DECIMAL(5,2),
+    UNIQUE(W_WAREHOUSE_NAME) WITH(fillfactor=70)
+);
+
+-- Alternatively, user the following syntax:
+mogdb=# CREATE TABLE tpcds.warehouse_t6
+(
+    W_WAREHOUSE_SK            INTEGER                NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)               NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)              UNIQUE,
+    W_WAREHOUSE_SQ_FT         INTEGER                        ,
+    W_STREET_NUMBER           CHAR(10)                       ,
+    W_STREET_NAME             VARCHAR(60)                    ,
+    W_STREET_TYPE             CHAR(15)                       ,
+    W_SUITE_NUMBER            CHAR(10)                       ,
+    W_CITY                    VARCHAR(60)                    ,
+    W_COUNTY                  VARCHAR(30)                    ,
+    W_STATE                   CHAR(2)                        ,
+    W_ZIP                     CHAR(10)                       ,
+    W_COUNTRY                 VARCHAR(20)                    ,
+    W_GMT_OFFSET              DECIMAL(5,2)
+) WITH(fillfactor=70);
+
+-- Create a table and specify that its data is not written to WALs.
+mogdb=# CREATE UNLOGGED TABLE tpcds.warehouse_t7
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2)
+);
+
+-- Create a temporary table.
+mogdb=# CREATE TEMPORARY TABLE warehouse_t24
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2)
+);
+
+-- Create a local temporary table and specify that this table is dropped when the transaction is committed.
+mogdb=# CREATE TEMPORARY TABLE warehouse_t25
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2)
+) ON COMMIT DELETE ROWS;
+
+-- Create a global temporary table and specify that this table data is deleted when the session ends.
+mogdb=# CREATE GLOBAL TEMPORARY TABLE gtt1
+(
+    ID                        INTEGER               NOT NULL,
+    NAME                      CHAR(16)              NOT NULL,
+    ADDRESS                   VARCHAR(50)                   ,
+    POSTCODE                  CHAR(6)
+) ON COMMIT PRESERVE ROWS;
+
+-- Create a table and specify that no error is reported for duplicate tables (if any).
+mogdb=# CREATE TABLE IF NOT EXISTS tpcds.warehouse_t8
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2)
+);
+
+-- Create a general tablespace.
+mogdb=# CREATE TABLESPACE DS_TABLESPACE1 RELATIVE LOCATION 'tablespace/tablespace_1';
+-- Specify a tablespace when creating a table.
+mogdb=# CREATE TABLE tpcds.warehouse_t9
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2)
+) TABLESPACE DS_TABLESPACE1;
+
+-- Separately specify the index tablespace for W_WAREHOUSE_NAME when creating the table.
+mogdb=# CREATE TABLE tpcds.warehouse_t10
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)           UNIQUE USING INDEX TABLESPACE DS_TABLESPACE1,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2)
+);
+-- Create a table with a primary key constraint.
+mogdb=# CREATE TABLE tpcds.warehouse_t11
+(
+    W_WAREHOUSE_SK            INTEGER            PRIMARY KEY,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2)
+);
+
+-- An alternative for the preceding syntax is as follows:
+mogdb=# CREATE TABLE tpcds.warehouse_t12
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2),
+    PRIMARY KEY(W_WAREHOUSE_SK)
+);
+
+-- Or use the following statement to specify the name of the constraint:
+mogdb=# CREATE TABLE tpcds.warehouse_t13
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2),
+    CONSTRAINT W_CSTR_KEY1 PRIMARY KEY(W_WAREHOUSE_SK)
+);
+
+-- Create a table with a compound primary key constraint.
+mogdb=# CREATE TABLE tpcds.warehouse_t14
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2),
+    CONSTRAINT W_CSTR_KEY2 PRIMARY KEY(W_WAREHOUSE_SK, W_WAREHOUSE_ID)
+);
+
+-- Create a column-store table.
+mogdb=# CREATE TABLE tpcds.warehouse_t15
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2)
+) WITH (ORIENTATION = COLUMN);
+
+-- Create a column-store table using partial clustered storage.
+mogdb=# CREATE TABLE tpcds.warehouse_t16
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2),
+    PARTIAL CLUSTER KEY(W_WAREHOUSE_SK, W_WAREHOUSE_ID)
+) WITH (ORIENTATION = COLUMN);
+
+-- Define a column-store table with compression enabled.
+mogdb=# CREATE TABLE tpcds.warehouse_t17
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2)
+) WITH (ORIENTATION = COLUMN, COMPRESSION=HIGH);
+
+-- Define a row-store table with compression enabled.
+mogdb=# CREATE TABLE table_3213
+(
+  c_w_id         integer        not null,
+  c_d_id         integer        not null,
+  c_id           integer        not null,
+  c_discount     decimal(4,4),
+  c_credit       char(2),
+  c_last         varchar(16),
+  c_first        varchar(16),
+  c_credit_lim   decimal(12,2),
+  c_balance      decimal(12,2),
+  c_ytd_payment  decimal(12,2),
+  c_payment_cnt  integer,
+  c_delivery_cnt integer,
+  c_street_1     varchar(20),
+  c_street_2     varchar(20),
+  c_city         varchar(20),
+  c_state        char(2),
+  c_zip          char(9),
+  c_phone        char(16),
+  c_since        timestamp,
+  c_middle       char(2),
+  c_data         varchar(500)
+) WITH (COMPRESSION = YES);
+
+--specify the column mode when creating a row-compressed table.
+mogdb=# CREATE TABLE compress_18
+(
+  a00 int DELTA,
+  a01 int DICTIONARY,
+  a02 int NOCOMPRESS,
+  a03 varchar(100) PREFIX,
+  a04 int
+) WITH (COMPRESSION = YES);
+
+--For a row-compressed table created by WITH (COMPRESSION = YES), or a row-compressed table modified by SET COMPRESS, the mode of the new column can be specified in the following way.
+mogdb=# ALTER TABLE test1 ADD COLUMN al char(5) PREFIX;
+
+-- Define a column check constraint.
+mogdb=# CREATE TABLE tpcds.warehouse_t19
+(
+    W_WAREHOUSE_SK            INTEGER               PRIMARY KEY CHECK (W_WAREHOUSE_SK > 0),
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)           CHECK (W_WAREHOUSE_NAME IS NOT NULL),
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2)
+);
+
+mogdb=# CREATE TABLE tpcds.warehouse_t20
+(
+    W_WAREHOUSE_SK            INTEGER               PRIMARY KEY,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)           CHECK (W_WAREHOUSE_NAME IS NOT NULL),
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2),
+    CONSTRAINT W_CONSTR_KEY2 CHECK(W_WAREHOUSE_SK > 0 AND W_WAREHOUSE_NAME IS NOT NULL)
+);
+
+-- Define a hash table.
+mogdb=# CREATE TABLE tpcds.warehouse_t22
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2),
+    CONSTRAINT W_CONSTR_KEY3 UNIQUE(W_WAREHOUSE_SK)
+);
+
+-- Add a varchar column to the tpcds.warehouse_t19 table.
+mogdb=# ALTER TABLE tpcds.warehouse_t19 ADD W_GOODS_CATEGORY varchar(30);
+
+-- Add a check constraint to the tpcds.warehouse_t19 table.
+mogdb=# ALTER TABLE tpcds.warehouse_t19 ADD CONSTRAINT W_CONSTR_KEY4 CHECK (W_STATE IS NOT NULL);
+
+-- Use one statement to alter the types of two existing columns.
+mogdb=# ALTER TABLE tpcds.warehouse_t19
+    ALTER COLUMN W_GOODS_CATEGORY TYPE varchar(80),
+    ALTER COLUMN W_STREET_NAME TYPE varchar(100);
+
+-- This statement is equivalent to the preceding statement.
+mogdb=# ALTER TABLE tpcds.warehouse_t19 MODIFY (W_GOODS_CATEGORY varchar(30), W_STREET_NAME varchar(60));
+
+-- Add a not-null constraint to an existing column.
+mogdb=# ALTER TABLE tpcds.warehouse_t19 ALTER COLUMN W_GOODS_CATEGORY SET NOT NULL;
+
+-- Drop not-null constraints from an existing column.
+mogdb=# ALTER TABLE tpcds.warehouse_t19 ALTER COLUMN W_GOODS_CATEGORY DROP NOT NULL;
+
+-- If no partial cluster is specified in a column-store table, add a partial cluster to the table.
+mogdb=# ALTER TABLE tpcds.warehouse_t17 ADD PARTIAL CLUSTER KEY(W_WAREHOUSE_SK);
+
+-- View the constraint name and drop the partial cluster column of a column-store table.
+mogdb=# \d+ tpcds.warehouse_t17
+                              Table "tpcds.warehouse_t17"
+      Column       |         Type          | Modifiers | Storage  | Stats target | Description
+-------------------+-----------------------+-----------+----------+--------------+-------------
+ w_warehouse_sk    | integer               | not null  | plain    |              |
+ w_warehouse_id    | character(16)         | not null  | extended |              |
+ w_warehouse_name  | character varying(20) |           | extended |              |
+ w_warehouse_sq_ft | integer               |           | plain    |              |
+ w_street_number   | character(10)         |           | extended |              |
+ w_street_name     | character varying(60) |           | extended |              |
+ w_street_type     | character(15)         |           | extended |              |
+ w_suite_number    | character(10)         |           | extended |              |
+ w_city            | character varying(60) |           | extended |              |
+ w_county          | character varying(30) |           | extended |              |
+ w_state           | character(2)          |           | extended |              |
+ w_zip             | character(10)         |           | extended |              |
+ w_country         | character varying(20) |           | extended |              |
+ w_gmt_offset      | numeric(5,2)          |           | main     |              |
+Partial Cluster :
+    "warehouse_t17_cluster" PARTIAL CLUSTER KEY (w_warehouse_sk)
+Has OIDs: no
+Location Nodes: ALL DATANODES
+Options: compression=no, version=0.12
+mogdb=# ALTER TABLE tpcds.warehouse_t17 DROP CONSTRAINT warehouse_t17_cluster;
+
+-- Move a table to another tablespace.
+mogdb=# ALTER TABLE tpcds.warehouse_t19 SET TABLESPACE PG_DEFAULT;
+-- Create the joe schema.
+mogdb=# CREATE SCHEMA joe;
+
+-- Move a table to another schema.
+mogdb=# ALTER TABLE tpcds.warehouse_t19 SET SCHEMA joe;
+
+-- Rename an existing table.
+mogdb=# ALTER TABLE joe.warehouse_t19 RENAME TO warehouse_t23;
+
+-- Drop a column from the warehouse_t23 table.
+mogdb=# ALTER TABLE joe.warehouse_t23 DROP COLUMN W_STREET_NAME;
+
+-- Drop the tablespace, schema joe, and schema tables warehouse.
+mogdb=# DROP TABLE tpcds.warehouse_t1;
+mogdb=# DROP TABLE tpcds.warehouse_t2;
+mogdb=# DROP TABLE tpcds.warehouse_t3;
+mogdb=# DROP TABLE tpcds.warehouse_t4;
+mogdb=# DROP TABLE tpcds.warehouse_t5;
+mogdb=# DROP TABLE tpcds.warehouse_t6;
+mogdb=# DROP TABLE tpcds.warehouse_t7;
+mogdb=# DROP TABLE tpcds.warehouse_t8;
+mogdb=# DROP TABLE tpcds.warehouse_t9;
+mogdb=# DROP TABLE tpcds.warehouse_t10;
+mogdb=# DROP TABLE tpcds.warehouse_t11;
+mogdb=# DROP TABLE tpcds.warehouse_t12;
+mogdb=# DROP TABLE tpcds.warehouse_t13;
+mogdb=# DROP TABLE tpcds.warehouse_t14;
+mogdb=# DROP TABLE tpcds.warehouse_t15;
+mogdb=# DROP TABLE tpcds.warehouse_t16;
+mogdb=# DROP TABLE tpcds.warehouse_t17;
+mogdb=# DROP TABLE tpcds.warehouse_t18;
+mogdb=# DROP TABLE tpcds.warehouse_t20;
+mogdb=# DROP TABLE tpcds.warehouse_t21;
+mogdb=# DROP TABLE tpcds.warehouse_t22;
+mogdb=# DROP TABLE joe.warehouse_t23;
+mogdb=# DROP TABLE tpcds.warehouse_t24;
+mogdb=# DROP TABLE tpcds.warehouse_t25;
+mogdb=# DROP TABLESPACE DS_TABLESPACE1;
+mogdb=# DROP SCHEMA IF EXISTS joe CASCADE;
+```
+
+## Helpful Links
+
+[ALTER TABLE](22-ALTER-TABLE),  [DROP TABLE](95-DROP-TABLE), and  [CREATE TABLESPACE](63-CREATE-TABLESPACE)
+
+## Suggestions
+
+- UNLOGGED
+  - The unlogged table and its indexes do not use the WAL log mechanism during data writing. Their write speed is much higher than that of ordinary tables. Therefore, they can be used for storing intermediate result sets of complex queries to improve query performance.
+  - The unlogged table has no primary/standby mechanism. In case of system faults or abnormal breakpoints, data loss may occur. Therefore, the unlogged table cannot be used to store basic data.
+- TEMPORARY | TEMP
+  - A temporary table is automatically dropped at the end of a session.
+- LIKE
+  - The new table automatically inherits all column names, data types, and not-null constraints from this table. The new table is irrelevant to the original table after the creation.
+- LIKE INCLUDING DEFAULTS
+  - The default expressions are copied from the original table to the new table only if **INCLUDING DEFAULTS** is specified. The default behavior is to exclude default expressions, resulting in the copied columns in the new table having default values null.
+- LIKE INCLUDING CONSTRAINTS
+  - The **CHECK** constraints are copied from the original table to the new table only when **INCLUDING CONSTRAINTS** is specified. Other types of constraints are never copied to the new table. Not-null constraints are always copied to the new table. These rules also apply to column constraints and table constraints.
+- LIKE INCLUDING INDEXES
+  - Any indexes on the original table will not be created on the new table, unless the **INCLUDING INDEXES** clause is specified.
+- LIKE INCLUDING STORAGE
+  - **STORAGE** settings for the copied column definitions are copied only if **INCLUDING STORAGE** is specified. The default behavior is to exclude **STORAGE** settings.
+- LIKE INCLUDING COMMENTS
+  - If **INCLUDING COMMENTS** is specified, comments for the copied columns, constraints, and indexes are copied. The default behavior is to exclude comments.
+- LIKE INCLUDING PARTITION
+  - If **INCLUDING PARTITION** is specified, the partition definitions of the source table are copied to the new table, and the new table no longer uses the **PARTITION BY** clause. The default behavior is to exclude partition definition of the original table.
+- LIKE INCLUDING RELOPTIONS
+  - If **INCLUDING RELOPTIONS** is specified, the new table will copy the storage parameter (that is, **WITH** clause) of the source table. The default behavior is to exclude partition definition of the storage parameter of the original table.
+- LIKE INCLUDING ALL
+  - **INCLUDING ALL** contains the meaning of **INCLUDING DEFAULTS**, **INCLUDING CONSTRAINTS**, **INCLUDING INDEXES**, **INCLUDING STORAGE**, **INCLUDING COMMENTS**, **INCLUDING PARTITION**, and **INCLUDING RELOPTIONS**.
+- ORIENTATION ROW
+  - Creates a row-store table. Row-store applies to the OLTP service, which has many interactive transactions. An interaction involves many columns in the table. Using row-store can improve the efficiency.
+- ORIENTATION COLUMN
+  - Creates a column-store table. Column-store applies to the DWS, which has a large amount of aggregation computing, and involves a few column operations.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/61-CREATE-TABLE-AS.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/61-CREATE-TABLE-AS.md
new file mode 100644
index 0000000000000000000000000000000000000000..29dd34850dc4c5d11e663ff44c9931c1f91e3001
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/61-CREATE-TABLE-AS.md
@@ -0,0 +1,161 @@
+---
+title: CREATE TABLE AS
+summary: CREATE TABLE AS
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE TABLE AS
+
+## Function
+
+**CREATE TABLE AS** creates a table from the results of a query.
+
+It creates a table and fills it with data obtained using **SELECT**. The table columns have the names and data types associated with the output columns of **SELECT** (except that you can override the **SELECT** output column names by giving an explicit list of new column names).
+
+**CREATE TABLE AS** queries a source table once and writes the data in a new table. The result in the query view changes with the source table. In contrast, the view re-computes and defines its **SELECT** statement at each query.
+
+## Precautions
+
+- This statement cannot be used to create a partitioned table.
+- If an error occurs during table creation, after it is fixed, the system may fail to delete the disk files that are created before the last automatic clearance and whose size is not 0. This problem seldom occurs and does not affect system running of the database.
+
+## Syntax
+
+```ebnf+diagram
+CreateTableAs ::= CREATE [ [ GLOBAL | LOCAL ] [ TEMPORARY | TEMP ] | UNLOGGED ] TABLE table_name
+    [ (column_name [, ...] ) ]
+    [ WITH ( {storage_parameter = value} [, ... ] ) ]
+    [ ON COMMIT { PRESERVE ROWS | DELETE ROWS | DROP } ]
+    [ COMPRESS | NOCOMPRESS ]
+    [ TABLESPACE tablespace_name ]
+    AS query
+    [ WITH [ NO ] DATA ];
+```
+
+## Parameter Description
+
+- **UNLOGGED**
+
+  Specifies that the table is created as an unlogged table. Data written to unlogged tables is not written to the WALs, which makes them considerably faster than ordinary tables. However, they are not crash-safe: an unlogged table is automatically truncated after a crash or unclean shutdown. Contents of an unlogged table are also not replicated to standby servers. Any indexes created on an unlogged table are automatically unlogged as well.
+
+  - Usage scenario: Unlogged tables do not ensure data security. Users can back up data before using unlogged tables; for example, users should back up the data before a system upgrade.
+  - Troubleshooting: If data is missing in the indexes of unlogged tables due to some unexpected operations such as an unclean shutdown, users should re-create the indexes with errors.
+
+- **GLOBAL | LOCAL**
+
+  When creating a temporary table, you can specify the **GLOBAL** or **LOCAL** keyword before **TEMP** or **TEMPORARY**. If the keyword **GLOBAL** is specified, MogDB creates a global temporary table. Otherwise, MogDB creates a local temporary table.
+
+- **TEMPORARY | TEMP**
+
+  If **TEMP** or **TEMPORARY** is specified, the created table is a temporary table. Temporary tables are classified into global temporary tables and local temporary tables. If the keyword **GLOBAL** is specified when a temporary table is created, the table is a global temporary table. Otherwise, the table is a local temporary table.
+
+  The metadata of the global temporary table is visible to all sessions. After the sessions end, the metadata still exists. The user data, indexes, and statistics of a session are isolated from those of another session. Each session can only view and modify the data submitted by itself. Global temporary tables have two schemas: **ON COMMIT PRESERVE ROWS** and **ON COMMIT PRESERVE ROWS**. In session-based **ON COMMIT PRESERVE ROWS** schema, user data is automatically cleared when a session ends. In transaction-based **ON COMMIT DELETE ROWS** schema, user data is automatically cleared when the commit or rollback operation is performed. If the **ON COMMIT** option is not specified during table creation, the session level is used by default. Different from local temporary tables, you can specify a schema that does not start with **pg_temp_** when creating a global temporary table.
+
+  A local temporary table is automatically dropped at the end of the current session. Therefore, you can create and use temporary tables in the current session as long as the connected database node in the session is normal. Temporary tables are created only in the current session. If a DDL statement involves operations on temporary tables, a DDL error will be generated. Therefore, you are not advised to perform operations on temporary tables in DDL statements. **TEMP** is equivalent to **TEMPORARY**.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+  >
+  > - Local temporary tables are visible to the current session through the schema starting with **pg_temp** start. Users should not delete schema started with **pg_temp** or **pg_toast_temp**.
+  > - If **TEMPORARY** or **TEMP** is not specified when you create a table but its schema is set to that starting with **pg_temp_** in the current session, the table will be created as a temporary table.
+  > - If global temporary tables and indexes are being used by other sessions, do not perform **ALTER** or **DROP**.
+  > - The DDL of a global temporary table affects only the user data and indexes of the current session. For example, **TRUNCATE**, **REINDEX**, and **ANALYZE** are valid only for the current session.
+
+- **table_name**
+
+  Specifies the name of the table to be created.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **column_name**
+
+  Specifies the name of a column to be created in the new table.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **WITH ( storage_parameter [= value] [, … ] )**
+
+  Specifies an optional storage parameter for a table or an index. See details of parameters below.
+
+  - FILLFACTOR
+
+    The fill factor of a table is a percentage from 10 to 100. **100** (complete filling) is the default value. When a smaller fill factor is specified, **INSERT** operations pack table pages only to the indicated percentage. The remaining space on each page is reserved for updating rows on that page. This gives **UPDATE** a chance to place the updated copy of a row on the same page, which is more efficient than placing it on a different page. For a table whose entries are never updated, setting the fill factor to **100** (complete filling) is the best choice, but in heavily updated tables a smaller fill factor would be appropriate. The parameter is only valid for row-store tables.
+
+    Value range: 10-100
+
+  - ORIENTATION
+
+    Value range:
+
+    **COLUMN**: The data will be stored in columns.
+
+    **ROW** (default value): The data will be stored in rows.
+
+  - COMPRESSION
+
+    Specifies the compression level of table data. It determines the compression ratio and time. Generally, the higher the level of compression, the higher the ratio, the longer the time; and the lower the level of compression, the lower the ratio, the shorter the time. The actual compression ratio depends on the distribution mode of table data loaded.
+
+    Value range:
+
+    The valid values for column-store tables are **YES**, **NO**, **LOW**, **MIDDLE**, and **HIGH**, and the default value is **LOW**.
+
+    Row-store tables do not support compression.
+
+  - MAX_BATCHROW
+
+    Specifies the maximum number of rows in a storage unit during data loading. The parameter is only valid for column-store tables.
+
+    Value range: 10000 to 60000
+
+- **ON COMMIT { PRESERVE ROWS | DELETE ROWS | DROP }**
+
+  **ON COMMIT** determines what to do when you commit a temporary table creation operation. The three options are as follows. Currently, only **PRESERVE ROWS** and **DELETE ROWS** can be used.
+
+  - **PRESERVE ROWS** (default): No special action is taken at the ends of transactions. The temporary table and its table data are unchanged.
+  - **DELETE ROWS**: All rows in the temporary table will be deleted at the end of each transaction block.
+  - **DROP**: The temporary table will be dropped at the end of the current transaction block. Only local temporary tables can be dropped. Global temporary tables cannot be dropped.
+
+- **COMPRESS / NOCOMPRESS**
+
+  Specifies keyword **COMPRESS** during the creation of a table, so that the compression feature is triggered in case of bulk **INSERT** operations. If this feature is enabled, a scan is performed for all tuple data within the page to generate a dictionary and then the tuple data is compressed and stored. If **NOCOMPRESS** is specified, the table is not compressed. Row-store tables do not support compression.
+
+  Default value: **NOCOMPRESS**, that is, tuple data is not compressed before storage.
+
+- **TABLESPACE tablespace_name**
+
+  Specifies that the new table will be created in the **tablespace_name** tablespace. If not specified, the default tablespace is used.
+
+- **AS query**
+
+  Specifies a **SELECT** or **VALUES** command, or an **EXECUTE** command that runs a prepared **SELECT** or **VALUES** query.
+
+- **[ WITH [ NO ] DATA ]**
+
+  Specifies whether the data produced by the query should be copied to the new table. By default, the data will be copied. If the value **NO** is used, only the table structure will be copied.
+
+## Example
+
+```sql
+-- Create the tpcds.store_returns table.
+mogdb=# CREATE TABLE tpcds.store_returns
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    sr_item_sk                VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER
+);
+-- Create the tpcds.store_returns_t1 table and insert numbers that are greater than 16 in the sr_item_sk column of the tpcds.store_returns table.
+mogdb=# CREATE TABLE tpcds.store_returns_t1 AS SELECT * FROM tpcds.store_returns WHERE sr_item_sk > '4795';
+
+-- Copy tpcds.store_returns to create the tpcds.store_returns_t2 table.
+mogdb=# CREATE TABLE tpcds.store_returns_t2 AS table tpcds.store_returns;
+
+-- Delete the table.
+mogdb=# DROP TABLE tpcds.store_returns_t1 ;
+mogdb=# DROP TABLE tpcds.store_returns_t2 ;
+mogdb=# DROP TABLE tpcds.store_returns;
+```
+
+## Helpful Links
+
+[CREATE TABLE](60-CREATE-TABLE)，[SELECT](125-SELECT)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/62-CREATE-TABLE-PARTITION.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/62-CREATE-TABLE-PARTITION.md
new file mode 100644
index 0000000000000000000000000000000000000000..b741cbe25afbdc7bd02b70b56c2325b9d656b06b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/62-CREATE-TABLE-PARTITION.md
@@ -0,0 +1,929 @@
+---
+title: CREATE TABLE PARTITION
+summary: CREATE TABLE PARTITION
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE TABLE PARTITION
+
+## Function
+
+**CREATE TABLE PARTITION** creates a partitioned table. Partitioning refers to splitting what is logically one large table into smaller physical pieces based on specific schemes. The table based on the logic is called a partitioned table, and each physical piece is called a partition. Data is stored on these physical partitions, instead of the logical partitioned table.
+
+The common forms of partitioning include range partitioning, interval partitioning, hash partitioning, list partitioning, and value partitioning. Currently, row-store tables support range partitioning, interval partitioning, hash partitioning, and list partitioning. Column-store tables support only range partitioning.
+
+In range partitioning, a table is partitioned based on ranges defined by one or more columns, with no overlap between the ranges of values assigned to different partitions. Each range has a dedicated partition for data storage.
+
+The partitioning policy for range partitioning refers to how data is inserted into partitions. Currently, range partitioning only allows the use of the range partitioning policy.
+
+In range partitioning, a table is partitioned based on partition key values. If a record can be mapped to a partition, it is inserted into the partition; if it cannot, an error message is returned. Range partitioning is the most commonly used partitioning policy.
+
+Interval partitioning is a special type of range partitioning. Compared with range partitioning, interval value definition is added. When no matching partition can be found for an inserted record, a partition can be automatically created based on the interval value.
+
+Interval partitioning supports only table-based partitioning of a list where the data type can be TIMESTAMP[(p)] [WITHOUT TIME ZONE], TIMESTAMP[(p)] [WITH TIME ZONE] and DATE.
+
+Interval partitioning policy: A record is mapped to a created partition based on the partition key value. If the record can be mapped to a created partition, the record is inserted into the corresponding partition. Otherwise, a partition is automatically created based on the partition key value and table definition information, and then the record is inserted into the new partition. The data range of the new partition is equal to the interval value.
+
+In hash partitioning, a modulus and a remainder are specified for each partition based on a column in the table, and records to be inserted into the table are allocated to the corresponding partition, the rows in each partition must meet the following condition: The value of the partition key divided by the specified modulus generates the remainder specified for the partition key.
+
+In hash partitioning, table is partitioned based on partition key values. If a record can be mapped to a partition, it is inserted into the partition; if it cannot, an error message is returned.
+
+List partitioning is to allocate the records to be inserted into a table to the corresponding partition based on the key values in each partition. The key values do not overlap in different partitions. Create a partition for each group of key values to store corresponding data.
+
+In list partitioning, table is partitioned based on partition key values. If a record can be mapped to a partition, it is inserted into the partition; if it cannot, an error message is returned.
+
+Partitioning can provide several benefits:
+
+- Query performance can be improved drastically in certain situations, particularly when most of the heavily accessed rows of the table are in a single partition or a small number of partitions. Partitioning narrows the range of data search and improves data access efficiency.
+- In the case of an insert or update operation on most portions of a single partition, performance can be improved by taking advantage of continuous scan of that partition instead of partitions scattered across the whole table.
+- Frequent loading or deletion operations on records in a separate partition can be accomplished by reading or removing that partition. It also entirely avoids the **VACUUM** overload caused by bulk **DELETE** operations (only for range partitioning).
+
+## Precautions
+
+- If the constraint key of the unique constraint and primary key constraint contains all partition keys, a local index is created for the constraints. Otherwise, a global index is created.
+- Currently, hash partitioning and list partitioning support only single-column partitioning, and do not support multi-column partitioning.
+- When you have the **INSERT** permission on an interval partitioned table, partitions can be automatically created when you run **INSERT** to write data to the table.
+
+## Syntax
+
+```ebnf+diagram
+CreateTablePartition ::= CREATE TABLE [ IF NOT EXISTS ] partition_table_name
+( [
+    { column_name data_type [ COLLATE collation ] [ column_constraint [ ... ] ]
+    | table_constraint
+    | LIKE source_table [ like_option [...] ] }[, ... ]
+] )
+    [ WITH ( {storage_parameter = value} [, ... ] ) ]
+    [ COMPRESS | NOCOMPRESS ]
+    [ TABLESPACE tablespace_name ]
+     PARTITION BY {
+        {RANGE (partition_key) [ INTERVAL ('interval_expr') [ STORE IN (tablespace_name [, ... ] ) ] ] ( partition_less_than_item [, ... ] )} |
+        {RANGE (partition_key) [ INTERVAL ('interval_expr') [ STORE IN (tablespace_name [, ... ] ) ] ] ( partition_start_end_item [, ... ] )} |
+        {LIST | HASH (partition_key) (PARTITION partition_name [VALUES (list_values_clause)] opt_table_space )}
+    } [ { ENABLE | DISABLE } ROW MOVEMENT ];
+```
+
+- **column_constraint** is as follows:
+
+  ```ebnf+diagram
+  column_constraint ::= [ CONSTRAINT constraint_name ]
+  { NOT NULL |
+    NULL |
+    CHECK ( expression ) |
+    DEFAULT default_expr |
+    GENERATED ALWAYS AS ( generation_expr ) STORED |
+    UNIQUE index_parameters |
+    PRIMARY KEY index_parameters |
+    REFERENCES reftable [ ( refcolumn ) ] [ MATCH FULL | MATCH PARTIAL | MATCH SIMPLE ]
+        [ ON DELETE action ] [ ON UPDATE action ] }
+  [ DEFERRABLE | NOT DEFERRABLE | INITIALLY DEFERRED | INITIALLY IMMEDIATE ]
+  ```
+
+- **table_constraint** is as follows:
+
+  ```ebnf+diagram
+  table_constraint ::= [ CONSTRAINT constraint_name ]
+  { CHECK ( expression ) |
+    UNIQUE ( column_name [, ... ] ) index_parameters |
+    PRIMARY KEY ( column_name [, ... ] ) index_parameters |
+    FOREIGN KEY ( column_name [, ... ] ) REFERENCES reftable [ ( refcolumn [, ... ] ) ]
+        [ MATCH FULL | MATCH PARTIAL | MATCH SIMPLE ] [ ON DELETE action ] [ ON UPDATE action ] }
+  [ DEFERRABLE | NOT DEFERRABLE | INITIALLY DEFERRED | INITIALLY IMMEDIATE ]
+  ```
+
+- **like_option** is as follows:
+
+  ```ebnf+diagram
+  like_option ::= { INCLUDING | EXCLUDING } { DEFAULTS | GENERATED | CONSTRAINTS | INDEXES | STORAGE | COMMENTS | RELOPTIONS| ALL }
+  ```
+
+- **index_parameters** is as follows:
+
+  ```ebnf+diagram
+  index_parameters ::= [ WITH ( {storage_parameter = value} [, ... ] ) ]
+  [ USING INDEX TABLESPACE tablespace_name ]
+  ```
+
+- partition_less_than_item:
+
+  ```ebnf+diagram
+  partition_less_than_item ::= PARTITION partition_name VALUES LESS THAN ( { partition_value | MAXVALUE } ) [TABLESPACE tablespace_name]
+  ```
+
+- partition_start_end_item:
+
+  ```ebnf+diagram
+  partition_start_end_item ::= PARTITION partition_name {
+          {START(partition_value) END (partition_value) EVERY (interval_value)} |
+          {START(partition_value) END ({partition_value | MAXVALUE})} |
+          {START(partition_value)} |
+          {END({partition_value | MAXVALUE})}
+  } [TABLESPACE tablespace_name]
+  ```
+
+## Parameter Description
+
+- **IF NOT EXISTS**
+
+  Sends a notice, but does not throw an error, if a table with the same name exists.
+
+- **partition_table_name**
+
+  Specifies the name of the partitioned table.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **column_name**
+
+  Specifies the name of a column to be created in the new table.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **data_type**
+
+  Specifies the data type of the column.
+
+- **COLLATE collation**
+
+  Assigns a collation to the column (which must be of a collatable data type). If no collation is specified, the default collation is used. You can run the **select \* from pg_collation;** command to query collation rules from the **pg_collation** system catalog. The default collation rule is the row starting with **default** in the query result.
+
+- **CONSTRAINT constraint_name**
+
+  Specifies the name of a column or table constraint. The optional constraint clauses specify constraints that new or updated rows must satisfy for an insert or update operation to succeed.
+
+  There are two ways to define constraints:
+
+  - A column constraint is defined as part of a column definition, and it is bound to a particular column.
+  - A table constraint is not bound to a particular column but can apply to more than one column.
+
+- **LIKE source_table [ like_option … ]**
+
+  Specifies a table from which the new table automatically copies all column names, their data types, and their not-null constraints.
+
+  Unlike **INHERITS**, the new table and original table are decoupled after creation is complete. Changes to the original table will not be applied to the new table, and it is not possible to include data of the new table in scans of the original table.
+
+  - Default expressions for the copied column definitions will be copied only if **INCLUDING DEFAULTS** is specified. The default behavior is to exclude default expressions, resulting in the copied columns in the new table having default values **NULL**.
+  - If **INCLUDING GENERATED** is specified, the generated expression of the source table column is copied to the new table. By default, the generated expression is not copied.
+  - Not-null constraints are always copied to the new table. **CHECK** constraints will only be copied if **INCLUDING CONSTRAINTS** is specified; other types of constraints will never be copied. These rules also apply to column constraints and table constraints.
+  - Unlike those of **INHERITS**, columns and constraints copied by **LIKE** are not merged with similarly named columns and constraints. If the same name is specified explicitly or in another **LIKE** clause, an error is reported.
+  - Any indexes on the original table will not be created on the new table, unless the **INCLUDING INDEXES** clause is specified.
+  - **STORAGE** settings for the copied column definitions are copied only if **INCLUDING STORAGE** is specified. The default behavior is to exclude **STORAGE** settings.
+  - If **INCLUDING COMMENTS** is specified, comments for the copied columns, constraints, and indexes are copied. The default behavior is to exclude comments.
+  - If **INCLUDING RELOPTIONS** is specified, the new table will copy the storage parameter (that is, **WITH** clause) of the source table. The default behavior is to exclude partition definition of the storage parameter of the source table.
+  - **INCLUDING ALL** contains the meaning of **INCLUDING DEFAULTS**, **INCLUDING CONSTRAINTS**, **INCLUDING INDEXES**, **INCLUDING STORAGE**, **INCLUDING COMMENTS**, **INCLUDING PARTITION**, and **INCLUDING RELOPTIONS**.
+
+- **WITH ( storage_parameter [= value] [, … ] )**
+
+  Specifies an optional storage parameter for a table or an index. Optional parameters are as follows:
+
+  - FILLFACTOR
+
+    The fill factor of a table is a percentage from 10 to 100. **100** (complete filling) is the default value. When a smaller fill factor is specified, **INSERT** operations pack table pages only to the indicated percentage. The remaining space on each page is reserved for updating rows on that page. This gives **UPDATE** a chance to place the updated copy of a row on the same page, which is more efficient than placing it on a different page. For a table whose entries are never updated, setting the fill factor to **100** (complete filling) is the best choice, but in heavily updated tables a smaller fill factor would be appropriate. The parameter has no meaning for column-store tables.
+
+    Value range: 10-100
+
+  - ORIENTATION
+
+    Determines the storage mode of the data in the table.
+
+    Value range:
+
+    - **COLUMN**: The data will be stored in columns.
+
+    - **ROW** (default value): The data will be stored in rows.
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** **orientation** cannot be modified.
+
+  - COMPRESSION
+
+    - Valid values for column-store tables are **LOW**, **MIDDLE**, **HIGH**, **YES**, and **NO**, and the compression level increases accordingly. The default is **LOW**.
+    - Row-store tables do not support compression.
+
+  - MAX_BATCHROW
+
+    Specifies the maximum number of rows in a storage unit during data loading. The parameter is only valid for column-store tables.
+
+    Value range: 10000 to 60000. The default value is **60000**.
+
+  - PARTIAL_CLUSTER_ROWS
+
+    Specifies the number of records to be partially clustered for storage during data loading. The parameter is only valid for column-store tables.
+
+    Value range: greater than or equal to **MAX_BATCHROW**. You are advised to set this parameter to an integer multiple of **MAX_BATCHROW**.
+
+  - DELTAROW_THRESHOLD
+
+    A reserved parameter. The parameter is only valid for column-store tables.
+
+    Value range: 0 to 9999
+
+- **COMPRESS / NOCOMPRESS**
+
+  Specifies keyword **COMPRESS** during the creation of a table, so that the compression feature is triggered in case of bulk **INSERT** operations. If this feature is enabled, a scan is performed for all tuple data within the page to generate a dictionary and then the tuple data is compressed and stored. If **NOCOMPRESS** is specified, the table is not compressed. Row-store tables do not support compression.
+
+  Default value: **NOCOMPRESS**, that is, tuple data is not compressed before storage.
+
+- **TABLESPACE tablespace_name**
+
+  Specifies that the new table will be created in the **tablespace_name** tablespace. If not specified, the default tablespace is used.
+
+- **PARTITION BY RANGE(partition_key)**
+
+  Creates a range partition. **partition_key** is the name of the partition key.
+
+  (1) Assume that the **VALUES LESS THAN** syntax is used.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** In this case, a maximum of four partition keys are supported.
+
+  Data types supported by the partition keys are as follows: **SMALLINT**, **INTEGER**, **BIGINT**, **DECIMAL**, **NUMERIC**, **REAL**, **DOUBLE PRECISION**, **CHARACTER VARYING**(*n*), **VARCHAR**(*n*), **CHARACTER**(*n*), **CHAR**(*n*), **CHARACTER**, **CHAR**, **TEXT**, **NVARCHAR2**, **NAME**, **TIMESTAMP[(p)] [WITHOUT TIME ZONE]**, **TIMESTAMP[(p)] [WITH TIME ZONE]**, and **DATE**.
+
+  (2) Assume that the **START END** syntax is used.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** In this case, only one partition key is supported.
+
+  Data types supported by the partition key are as follows: **SMALLINT**, **INTEGER**, **BIGINT**, **DECIMAL**, **NUMERIC**, **REAL**, **DOUBLE PRECISION**, **TIMESTAMP[(p)] [WITHOUT TIME ZONE]**, **TIMESTAMP[(p)] [WITH TIME ZONE]**, and **DATE**.
+
+  (3) Assume that the **INTERVAL** syntax is used.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** In this case, only one partition key is supported.
+
+  In this case, the data types supported by the partition key are TIMESTAMP[(p)] [WITHOUT TIME ZONE], TIMESTAMP[(p)] [WITH TIME ZONE] and DATE.
+
+- **PARTITION partition_name VALUES LESS THAN ( { partition_value | MAXVALUE } )**
+
+  Specifies the information of partitions. **partition_name** is the name of a range partition. **partition_value** is the upper limit of a range partition, and the value depends on the type of **partition_key**. *MAXVALUE* usually specifies the upper limit of the last range partition.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+  >
+  > - Each partition requires an upper limit.
+  > - The data type of the upper limit must be the same as that of the partition key.
+  > - In a partition list, partitions are arranged in ascending order of upper limits. A partition with a smaller upper limit value is placed before another partition with a larger one.
+
+- **PARTITION partition_name {START (partition_value) END (partition_value) EVERY (interval_value)} |** {START (partition_value) END (partition_value|MAXVALUE)} | {START(partition_value)} | **{END (partition_value | MAXVALUE)**}
+
+  Specifies information of partitions.
+
+  - **partition_name**: name or name prefix of a range partition. It is the name prefix only in the following cases (assuming that **partition_name** is **p1**):
+    - If **START**+**END**+**EVERY** is used, the names of partitions will be defined as **p1_1**, **p1_2**, and the like. For example, if **PARTITION p1 START(1) END(4) EVERY(1)** is defined, the generated partitions are [1, 2), [2, 3), and [3, 4), and their names are **p1_1**, **p1_2**, and **p1_3**. In this case, **p1** is a name prefix.
+    - If the defined statement is in the first place and has **START** specified, the range (*MINVALUE*, **START**) will be automatically used as the first actual partition, and its name will be **p1_0**. The other partitions are then named **p1_1**, **p1_2**, and the like. For example, if **PARTITION p1 START(1), PARTITION p2 START(2)** is defined, generated partitions are (*MINVALUE*, 1), [1, 2), and [2, *MAXVALUE*), and their names will be **p1_0**, **p1_1**, and **p2**. In this case, **p1** is a name prefix and **p2** is a partition name. **MINVALUE** means the minimum value.
+  - **partition_value**: start value or end value of a range partition. The value depends on **partition_key** and cannot be *MAXVALUE*.
+  - **interval_value**: width of each partition for dividing the [**START**, **END**) range. It cannot be *MAXVALUE*. If the value of (**END** - **START**) divided by **EVERY** has a remainder, the width of only the last partition is less than the value of **EVERY**.
+  - *MAXVALUE* usually specifies the upper limit of the last range partition.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+  >
+  > 1. If the defined statement is in the first place and has **START** specified, the range (*MINVALUE*, **START**) will be automatically used as the first actual partition.
+  > 2. The **START END** syntax must comply with the following rules:
+  >    - The value of **START** (if any, same for the following situations) in each **partition_start_end_item** must be smaller than that of **END**.
+  >    - In two adjacent **partition_start_end_item** statements, the value of the first **END** must be equal to that of the second **START**.
+  >    - The value of **EVERY** in each **partition_start_end_item** must be a positive number (in ascending order) and must be smaller than **END** minus **START**.
+  >    - Each partition includes the start value (unless it is *MINVALUE*) and excludes the end value. The format is as follows: [**START**, **END**).
+  >    - Partitions created by the same **partition_start_end_item** belong to the same tablespace.
+  >    - If **partition_name** is a name prefix of a partition, the length must not exceed 57 bytes. If there are more than 57 bytes, the prefix will be automatically truncated.
+  >    - When creating or modifying a partitioned table, ensure that the total number of partitions in the table does not exceed the maximum value **1048575**.
+  > 3. In statements for creating partitioned tables, **START END** and **LESS THAN** cannot be used together.
+  > 4. The **START END** syntax in a partitioned table creation SQL statement will be replaced by the **VALUES LESS THAN** syntax when **gs_dump** is executed.
+
+- **INTERVAL ('interval_expr') [ STORE IN (tablespace_name [, … ] ) ]**
+
+  Defines interval partitioning.
+
+  - **interval_expr**: interval for automatically creating partitions, for example, 1 day or 1 month.
+  - **STORE IN (tablespace_name [, … ] )**: Specifies the list of tablespaces for storing automatically created partitions. If this parameter is specified, the automatically created partitions are cyclically selected from the tablespace list. Otherwise, the default tablespace of the partition table is used.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** Column-store tables do not support interval partitioning.
+
+- **PARTITION BY LIST(partition_key)**
+
+  Create a list partition. **partition_key** is the name of the partition key.
+
+  - For **partition_key**, the list partitioning policy supports only one column of partition keys.
+  - If the clause is **VALUES (list_values_clause)**, **list_values_clause** contains the key values of the corresponding partition. It is recommended that the number of key values of each partition be less than or equal to 1048575.
+
+  Partition keys support the following data types: INT1, INT2, INT4, INT8, NUMERIC, VARCHAR(*n*), CHAR, BPCHAR, NVARCHAR2, TIMESTAMP[(*p*)] [WITHOUT TIME ZONE], TIMESTAMP[(*p*)] [WITH TIME ZONE] and DATE. The number of partitions cannot exceed 64.
+
+- **PARTITION BY HASH(partition_key)**
+
+  Create a hash partition. **partition_key** is the name of the partition key.
+
+  For **partition_key**, the hash partitioning policy supports only one column of partition keys.
+
+  Partition keys support the following data types: INT1, INT2, INT4, INT8, NUMERIC, VARCHAR(n), CHAR, BPCHAR, NVARCHAR2, TIMESTAMP[(p)] [WITHOUT TIME ZONE], TIMESTAMP[(p)] [WITH TIME ZONE] and DATE. The number of partitions cannot exceed 1048575.
+
+- **{ ENABLE | DISABLE } ROW MOVEMENT**
+
+  Sets row movement.
+
+  If the tuple value is updated on the partition key during the **UPDATE** action, the partition where the tuple is located is altered. Setting this parameter enables error messages to be reported or movement of the tuple between partitions.
+
+  Value range:
+
+  - **ENABLE** (default value): Row movement is enabled.
+  - **DISABLE**: Row movement is disabled.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** Currently, list and hash partitioned tables do not support **ROW MOVEMENT**.
+
+- **NOT NULL**
+
+  The column is not allowed to contain null values. **ENABLE** can be omitted.
+
+- **NULL**
+
+  Specifies that the column is allowed to contain null values. This is the default setting.
+
+  This clause is only provided for compatibility with non-standard SQL databases. It is not recommended.
+
+- **CHECK (condition) [ NO INHERIT ]**
+
+  Specifies an expression producing a Boolean result where the insert or update operation of new or updated rows can succeed only when the expression result is **TRUE** or **UNKNOWN**; otherwise, an error is thrown and the database is not altered.
+
+  A check constraint specified as a column constraint should reference only the column's values, while an expression appearing in a table constraint can reference multiple columns.
+
+  A constraint marked with **NO INHERIT** will not propagate to child tables.
+
+  **ENABLE** can be omitted.
+
+- **DEFAULT default_expr**
+
+  Assigns a default data value for a column. The value can be any variable-free expressions. (Subqueries and cross-references to other columns in the current table are not allowed.) The data type of the default expression must match the data type of the column.
+
+  The default expression will be used in any insert operation that does not specify a value for the column. If there is no default value for a column, then the default value is null.
+
+- GENERATED ALWAYS AS ( generation_expr ) STORED
+
+  This clause creates a column as a generated column. The value of the generated column is calculated by **generation_expr** when data is written (inserted or updated). **STORED** indicates that the value of the generated column is stored as a common column.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > - The generation expression cannot refer to data other than the current row in any way. The generation expression cannot reference other generation columns or system columns. The generation expression cannot return a result set. No subquery, aggregate function, or window function can be used. The function called by the generation expression can only be an immutable function.
+  > - Default values cannot be specified for generated columns.
+  > - The generated column cannot be used as a part of the partition key.
+  > - Do not specify the generated column and the CASCADE, SET NULL, and SET DEFAULT actions of the ON UPDATE constraint at the same time. Do not specify the generated column and the SET NULL, and SET DEFAULT actions of the ON DELETE constraint at the same time.
+  > - The method of modifying and deleting generated columns is the same as that of common columns. Delete the common column that the generated column depends on. The generated column is automatically deleted. The type of the column on which the generated column depends cannot be changed.
+  > - The generated column cannot be directly written. In the INSERT or UPDATE statement, values cannot be specified for generated columns, but the keyword DEFAULT can be specified.
+  > - The permission control for generated columns is the same as that for common columns.
+  > - Columns cannot be generated for column-store tables and MOTs. In foreign tables, only **postgres_fdw** supports generated columns.
+
+- **UNIQUE index_parameters**
+
+  **UNIQUE ( column_name [, … ] ) index_parameters**
+
+  Specifies that a group of one or more columns of a table can contain only unique values.
+
+  For the purpose of a unique constraint, null is not considered equal.
+
+- **PRIMARY KEY index_parameters**
+
+  **PRIMARY KEY ( column_name [, … ] ) index_parameters**
+
+  Specifies that a column or columns of a table can contain only unique (non-duplicate) and non-null values.
+
+  Only one primary key can be specified for a table.
+
+- **DEFERRABLE | NOT DEFERRABLE**
+
+  Controls whether the constraint can be deferred. A constraint that is not deferrable will be checked immediately after every command. Checking of constraints that are deferrable can be postponed until the end of the transaction using the **SET CONSTRAINTS** command. **NOT DEFERRABLE** is the default value. Currently, only UNIQUE constraints, primary key constraints, and foreign key constraints accept this clause. All the other constraints are not deferrable.
+
+- **INITIALLY IMMEDIATE | INITIALLY DEFERRED**
+
+  If a constraint is deferrable, this clause specifies the default time to check the constraint.
+
+  - If the constraint is **INITIALLY IMMEDIATE** (default value), it is checked after each statement.
+  - If the constraint is **INITIALLY DEFERRED**, it is checked only at the end of the transaction.
+
+  The constraint check time can be altered using the **SET CONSTRAINTS** statement.
+
+- **USING INDEX TABLESPACE tablespace_name**
+
+  Allows selection of the tablespace in which the index associated with a **UNIQUE** or **PRIMARY KEY** constraint will be created. If not specified, **default_tablespace** is consulted, or the default tablespace in the database if **default_tablespace** is empty.
+
+## Examples
+
+- Example 1: Create a range-partitioned table **tpcds.web_returns_p1**. The table has eight partitions and their partition keys are of the integer type. The ranges of the partitions are: wr_returned_date_sk < 2450815, 2450815 ≤ wr_returned_date_sk < 2451179, 2451179 ≤ wr_returned_date_sk < 2451544, 2451544 ≤ wr_returned_date_sk < 2451910, 2451910 ≤ wr_returned_date_sk < 2452275, 2452275 ≤ wr_returned_date_sk < 2452640, 2452640 ≤ wr_returned_date_sk < 2453005, and wr_returned_date_sk ≥ 2453005.
+
+  ```sql
+  -- Create the tpcds.web_returns table.
+  mogdb=# CREATE TABLE tpcds.web_returns
+  (
+      W_WAREHOUSE_SK            INTEGER               NOT NULL,
+      W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+      W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+      W_WAREHOUSE_SQ_FT         INTEGER                       ,
+      W_STREET_NUMBER           CHAR(10)                      ,
+      W_STREET_NAME             VARCHAR(60)                   ,
+      W_STREET_TYPE             CHAR(15)                      ,
+      W_SUITE_NUMBER            CHAR(10)                      ,
+      W_CITY                    VARCHAR(60)                   ,
+      W_COUNTY                  VARCHAR(30)                   ,
+      W_STATE                   CHAR(2)                       ,
+      W_ZIP                     CHAR(10)                      ,
+      W_COUNTRY                 VARCHAR(20)                   ,
+      W_GMT_OFFSET              DECIMAL(5,2)
+  );
+  -- Create a range-partitioned table tpcds.web_returns_p1.
+  mogdb=# CREATE TABLE tpcds.web_returns_p1
+  (
+      WR_RETURNED_DATE_SK       INTEGER                       ,
+      WR_RETURNED_TIME_SK       INTEGER                       ,
+      WR_ITEM_SK                INTEGER               NOT NULL,
+      WR_REFUNDED_CUSTOMER_SK   INTEGER                       ,
+      WR_REFUNDED_CDEMO_SK      INTEGER                       ,
+      WR_REFUNDED_HDEMO_SK      INTEGER                       ,
+      WR_REFUNDED_ADDR_SK       INTEGER                       ,
+      WR_RETURNING_CUSTOMER_SK  INTEGER                       ,
+      WR_RETURNING_CDEMO_SK     INTEGER                       ,
+      WR_RETURNING_HDEMO_SK     INTEGER                       ,
+      WR_RETURNING_ADDR_SK      INTEGER                       ,
+      WR_WEB_PAGE_SK            INTEGER                       ,
+      WR_REASON_SK              INTEGER                       ,
+      WR_ORDER_NUMBER           BIGINT                NOT NULL,
+      WR_RETURN_QUANTITY        INTEGER                       ,
+      WR_RETURN_AMT             DECIMAL(7,2)                  ,
+      WR_RETURN_TAX             DECIMAL(7,2)                  ,
+      WR_RETURN_AMT_INC_TAX     DECIMAL(7,2)                  ,
+      WR_FEE                    DECIMAL(7,2)                  ,
+      WR_RETURN_SHIP_COST       DECIMAL(7,2)                  ,
+      WR_REFUNDED_CASH          DECIMAL(7,2)                  ,
+      WR_REVERSED_CHARGE        DECIMAL(7,2)                  ,
+      WR_ACCOUNT_CREDIT         DECIMAL(7,2)                  ,
+      WR_NET_LOSS               DECIMAL(7,2)
+  )
+  WITH (ORIENTATION = COLUMN,COMPRESSION=MIDDLE)
+  PARTITION BY RANGE(WR_RETURNED_DATE_SK)
+  (
+          PARTITION P1 VALUES LESS THAN(2450815),
+          PARTITION P2 VALUES LESS THAN(2451179),
+          PARTITION P3 VALUES LESS THAN(2451544),
+          PARTITION P4 VALUES LESS THAN(2451910),
+          PARTITION P5 VALUES LESS THAN(2452275),
+          PARTITION P6 VALUES LESS THAN(2452640),
+          PARTITION P7 VALUES LESS THAN(2453005),
+          PARTITION P8 VALUES LESS THAN(MAXVALUE)
+  );
+
+  -- Import data from the example data table.
+  mogdb=# INSERT INTO tpcds.web_returns_p1 SELECT * FROM tpcds.web_returns;
+
+  -- Delete the P8 partition.
+  mogdb=# ALTER TABLE tpcds.web_returns_p1 DROP PARTITION P8;
+
+  -- Add a partition WR_RETURNED_DATE_SK with values ranging from 2453005 to 2453105.
+  mogdb=# ALTER TABLE tpcds.web_returns_p1 ADD PARTITION P8 VALUES LESS THAN (2453105);
+
+  -- Add a partition WR_RETURNED_DATE_SK with values ranging from 2453105 to MAXVALUE.
+  mogdb=# ALTER TABLE tpcds.web_returns_p1 ADD PARTITION P9 VALUES LESS THAN (MAXVALUE);
+
+  -- Delete the P8 partition.
+  mogdb=# ALTER TABLE tpcds.web_returns_p1 DROP PARTITION FOR (2453005);
+
+  -- Rename the P7 partition to P10.
+  mogdb=# ALTER TABLE tpcds.web_returns_p1 RENAME PARTITION P7 TO P10;
+
+  -- Rename the P6 partition to P11.
+  mogdb=# ALTER TABLE tpcds.web_returns_p1 RENAME PARTITION FOR (2452639) TO P11;
+
+  -- Query the number of rows in the P10 partition.
+  mogdb=# SELECT count(*) FROM tpcds.web_returns_p1 PARTITION (P10);
+   count
+  --------
+   0
+  (1 row)
+
+  -- Query the number of rows in the P1 partition.
+  mogdb=# SELECT COUNT(*) FROM tpcds.web_returns_p1 PARTITION FOR (2450815);
+   count
+  --------
+   0
+  (1 row)
+  ```
+
+- Example 2: Create a range-partitioned table **tpcds.web_returns_p2**. The table has eight partitions and their partition keys are of the integer type. The upper limit of the eighth partition is *MAXVALUE*.
+
+  The ranges of the partitions are: wr_returned_date_sk < 2450815, 2450815 ≤ wr_returned_date_sk < 2451179, 2451179 ≤ wr_returned_date_sk < 2451544, 2451544 ≤ wr_returned_date_sk < 2451910, 2451910 ≤ wr_returned_date_sk < 2452275, 2452275 ≤ wr_returned_date_sk < 2452640, 2452640 ≤ wr_returned_date_sk < 2453005, and wr_returned_date_sk ≥ 2453005.
+
+  The tablespace of the **tpcds.web_returns_p2** partitioned table is **example1**. Partitions **P1** to **P7** have no specified tablespaces, and use the **example1** tablespace of the **tpcds.web_returns_p2** partitioned table. The tablespace of the **P8** partitioned table is **example2**.
+
+  Assume that the following data directories of the database nodes are empty directories for which user **dwsadmin** has the read and write permissions: **/pg_location/mount1/path1**, **/pg_location/mount2/path2**, **/pg_location/mount3/path3**, and **/pg_location/mount4/path4**.
+
+  ```sql
+  mogdb=# CREATE TABLESPACE example1 RELATIVE LOCATION 'tablespace1/tablespace_1';
+  mogdb=# CREATE TABLESPACE example2 RELATIVE LOCATION 'tablespace2/tablespace_2';
+  mogdb=# CREATE TABLESPACE example3 RELATIVE LOCATION 'tablespace3/tablespace_3';
+  mogdb=# CREATE TABLESPACE example4 RELATIVE LOCATION 'tablespace4/tablespace_4';
+
+  mogdb=# CREATE TABLE tpcds.web_returns_p2
+  (
+      WR_RETURNED_DATE_SK       INTEGER                       ,
+      WR_RETURNED_TIME_SK       INTEGER                       ,
+      WR_ITEM_SK                INTEGER               NOT NULL,
+      WR_REFUNDED_CUSTOMER_SK   INTEGER                       ,
+      WR_REFUNDED_CDEMO_SK      INTEGER                       ,
+      WR_REFUNDED_HDEMO_SK      INTEGER                       ,
+      WR_REFUNDED_ADDR_SK       INTEGER                       ,
+      WR_RETURNING_CUSTOMER_SK  INTEGER                       ,
+      WR_RETURNING_CDEMO_SK     INTEGER                       ,
+      WR_RETURNING_HDEMO_SK     INTEGER                       ,
+      WR_RETURNING_ADDR_SK      INTEGER                       ,
+      WR_WEB_PAGE_SK            INTEGER                       ,
+      WR_REASON_SK              INTEGER                       ,
+      WR_ORDER_NUMBER           BIGINT                NOT NULL,
+      WR_RETURN_QUANTITY        INTEGER                       ,
+      WR_RETURN_AMT             DECIMAL(7,2)                  ,
+      WR_RETURN_TAX             DECIMAL(7,2)                  ,
+      WR_RETURN_AMT_INC_TAX     DECIMAL(7,2)                  ,
+      WR_FEE                    DECIMAL(7,2)                  ,
+      WR_RETURN_SHIP_COST       DECIMAL(7,2)                  ,
+      WR_REFUNDED_CASH          DECIMAL(7,2)                  ,
+      WR_REVERSED_CHARGE        DECIMAL(7,2)                  ,
+      WR_ACCOUNT_CREDIT         DECIMAL(7,2)                  ,
+      WR_NET_LOSS               DECIMAL(7,2)
+  )
+  TABLESPACE example1
+  PARTITION BY RANGE(WR_RETURNED_DATE_SK)
+  (
+          PARTITION P1 VALUES LESS THAN(2450815),
+          PARTITION P2 VALUES LESS THAN(2451179),
+          PARTITION P3 VALUES LESS THAN(2451544),
+          PARTITION P4 VALUES LESS THAN(2451910),
+          PARTITION P5 VALUES LESS THAN(2452275),
+          PARTITION P6 VALUES LESS THAN(2452640),
+          PARTITION P7 VALUES LESS THAN(2453005),
+          PARTITION P8 VALUES LESS THAN(MAXVALUE) TABLESPACE example2
+  )
+  ENABLE ROW MOVEMENT;
+
+  -- Create a partitioned table using LIKE.
+  mogdb=# CREATE TABLE tpcds.web_returns_p3 (LIKE tpcds.web_returns_p2 INCLUDING PARTITION);
+
+  -- Change the tablespace of the P1 partition to example2.
+  mogdb=# ALTER TABLE tpcds.web_returns_p2 MOVE PARTITION P1 TABLESPACE example2;
+
+  -- Change the tablespace of the P2 partition to example3.
+  mogdb=# ALTER TABLE tpcds.web_returns_p2 MOVE PARTITION P2 TABLESPACE example3;
+
+  -- Split the P8 partition at 2453010.
+  mogdb=# ALTER TABLE tpcds.web_returns_p2 SPLIT PARTITION P8 AT (2453010) INTO
+  (
+          PARTITION P9,
+          PARTITION P10
+  );
+
+  -- Merge the P6 and P7 partitions into one.
+  mogdb=# ALTER TABLE tpcds.web_returns_p2 MERGE PARTITIONS P6, P7 INTO PARTITION P8;
+
+  -- Modify the migration attribute of the partitioned table.
+  mogdb=# ALTER TABLE tpcds.web_returns_p2 DISABLE ROW MOVEMENT;
+  -- Delete tables and tablespaces.
+  mogdb=# DROP TABLE tpcds.web_returns_p1;
+  mogdb=# DROP TABLE tpcds.web_returns_p2;
+  mogdb=# DROP TABLE tpcds.web_returns_p3;
+  mogdb=# DROP TABLESPACE example1;
+  mogdb=# DROP TABLESPACE example2;
+  mogdb=# DROP TABLESPACE example3;
+  mogdb=# DROP TABLESPACE example4;
+  ```
+
+- Example 3: Use **START END** to create and modify a range-partitioned table.
+
+  Assume that **/home/omm/startend_tbs1**, **/home/omm/startend_tbs2**, **/home/omm/startend_tbs3**, and **/home/omm/startend_tbs4** are empty directories for which user omm has the read and write permissions.
+
+  ```sql
+  -- Create tablespaces.
+  mogdb=# CREATE TABLESPACE startend_tbs1 LOCATION '/home/omm/startend_tbs1';
+  mogdb=# CREATE TABLESPACE startend_tbs2 LOCATION '/home/omm/startend_tbs2';
+  mogdb=# CREATE TABLESPACE startend_tbs3 LOCATION '/home/omm/startend_tbs3';
+  mogdb=# CREATE TABLESPACE startend_tbs4 LOCATION '/home/omm/startend_tbs4';
+
+  -- Create a temporary schema.
+  mogdb=# CREATE SCHEMA tpcds;
+  mogdb=# SET CURRENT_SCHEMA TO tpcds;
+
+  -- Create a partitioned table with the partition key of the integer type.
+  mogdb=# CREATE TABLE tpcds.startend_pt (c1 INT, c2 INT)
+  TABLESPACE startend_tbs1
+  PARTITION BY RANGE (c2) (
+      PARTITION p1 START(1) END(1000) EVERY(200) TABLESPACE startend_tbs2,
+      PARTITION p2 END(2000),
+      PARTITION p3 START(2000) END(2500) TABLESPACE startend_tbs3,
+      PARTITION p4 START(2500),
+      PARTITION p5 START(3000) END(5000) EVERY(1000) TABLESPACE startend_tbs4
+  )
+  ENABLE ROW MOVEMENT;
+
+  -- View the information of the partitioned table.
+  mogdb=# SELECT relname, boundaries, spcname FROM pg_partition p JOIN pg_tablespace t ON p.reltablespace=t.oid and p.parentid='tpcds.startend_pt'::regclass ORDER BY 1;
+     relname   | boundaries |    spcname
+  -------------+------------+---------------
+   p1_0        | {1}        | startend_tbs2
+   p1_1        | {201}      | startend_tbs2
+   p1_2        | {401}      | startend_tbs2
+   p1_3        | {601}      | startend_tbs2
+   p1_4        | {801}      | startend_tbs2
+   p1_5        | {1000}     | startend_tbs2
+   p2          | {2000}     | startend_tbs1
+   p3          | {2500}     | startend_tbs3
+   p4          | {3000}     | startend_tbs1
+   p5_1        | {4000}     | startend_tbs4
+   p5_2        | {5000}     | startend_tbs4
+   startend_pt |            | startend_tbs1
+  (12 rows)
+
+  -- Import data and check the data volume in a partition.
+  mogdb=# INSERT INTO tpcds.startend_pt VALUES (GENERATE_SERIES(0, 4999), GENERATE_SERIES(0, 4999));
+  mogdb=# SELECT COUNT(*) FROM tpcds.startend_pt PARTITION FOR (0);
+   count
+  -------
+       1
+  (1 row)
+
+  mogdb=# SELECT COUNT(*) FROM tpcds.startend_pt PARTITION (p3);
+   count
+  -------
+     500
+  (1 row)
+
+  -- Add partitions [5000, 5300), [5300, 5600), [5600, 5900), and [5900, 6000).
+  mogdb=# ALTER TABLE tpcds.startend_pt ADD PARTITION p6 START(5000) END(6000) EVERY(300) TABLESPACE startend_tbs4;
+
+  -- Add the partition p7, specified by MAXVALUE.
+  mogdb=# ALTER TABLE tpcds.startend_pt ADD PARTITION p7 END(MAXVALUE);
+
+  -- Rename the partition p7 to p8.
+  mogdb=# ALTER TABLE tpcds.startend_pt RENAME PARTITION p7 TO p8;
+
+  -- Delete the partition p8.
+  mogdb=# ALTER TABLE tpcds.startend_pt DROP PARTITION p8;
+
+  -- Rename the partition where 5950 is located to p71.
+  mogdb=# ALTER TABLE tpcds.startend_pt RENAME PARTITION FOR(5950) TO p71;
+
+  -- Split the partition [4000, 5000) where 4500 is located.
+  mogdb=# ALTER TABLE tpcds.startend_pt SPLIT PARTITION FOR(4500) INTO(PARTITION q1 START(4000) END(5000) EVERY(250) TABLESPACE startend_tbs3);
+
+  -- Change the tablespace of the partition p2 to startend_tbs4.
+  mogdb=# ALTER TABLE tpcds.startend_pt MOVE PARTITION p2 TABLESPACE startend_tbs4;
+
+  -- View the partition status.
+  mogdb=# SELECT relname, boundaries, spcname FROM pg_partition p JOIN pg_tablespace t ON p.reltablespace=t.oid and p.parentid='tpcds.startend_pt'::regclass ORDER BY 1;
+     relname   | boundaries |    spcname
+  -------------+------------+---------------
+   p1_0        | {1}        | startend_tbs2
+   p1_1        | {201}      | startend_tbs2
+   p1_2        | {401}      | startend_tbs2
+   p1_3        | {601}      | startend_tbs2
+   p1_4        | {801}      | startend_tbs2
+   p1_5        | {1000}     | startend_tbs2
+   p2          | {2000}     | startend_tbs4
+   p3          | {2500}     | startend_tbs3
+   p4          | {3000}     | startend_tbs1
+   p5_1        | {4000}     | startend_tbs4
+   p6_1        | {5300}     | startend_tbs4
+   p6_2        | {5600}     | startend_tbs4
+   p6_3        | {5900}     | startend_tbs4
+   p71         | {6000}     | startend_tbs4
+   q1_1        | {4250}     | startend_tbs3
+   q1_2        | {4500}     | startend_tbs3
+   q1_3        | {4750}     | startend_tbs3
+   q1_4        | {5000}     | startend_tbs3
+   startend_pt |            | startend_tbs1
+  (19 rows)
+
+  -- Delete tables and tablespaces.
+  mogdb=# DROP SCHEMA tpcds CASCADE;
+  mogdb=# DROP TABLESPACE startend_tbs1;
+  mogdb=# DROP TABLESPACE startend_tbs2;
+  mogdb=# DROP TABLESPACE startend_tbs3;
+  mogdb=# DROP TABLESPACE startend_tbs4;
+  ```
+
+- Example 4: Create an interval-partitioned table **sales**. The table initially contains two partitions and the partition key is of the DATE type.
+
+  Ranges of the two partitions are as follows: 2019-02-01 00:00:00 ≤ **time_id** < 2019-02-02 00:00:00.
+
+  ```sql
+  -- Create table sales:
+  mogdb=# CREATE TABLE sales
+  (prod_id NUMBER(6),
+   cust_id NUMBER,
+   time_id DATE,
+   channel_id CHAR(1),
+   promo_id NUMBER(6),
+   quantity_sold NUMBER(3),
+   amount_sold NUMBER(10,2)
+  )
+  PARTITION BY RANGE (time_id)
+  INTERVAL('1 day')
+  ( PARTITION p1 VALUES LESS THAN ('2019-02-01 00:00:00'),
+    PARTITION p2 VALUES LESS THAN ('2019-02-02 00:00:00')
+  );
+
+  -- Insert data into partition p1.
+  mogdb=# INSERT INTO sales VALUES(1, 12, '2019-01-10 00:00:00', 'a', 1, 1, 1);
+
+  -- Insert data into partition p2.
+  mogdb=# INSERT INTO sales VALUES(1, 12, '2019-02-01 00:00:00', 'a', 1, 1, 1);
+
+  -- View the partition information.
+  mogdb=# SELECT t1.relname, partstrategy, boundaries FROM pg_partition t1, pg_class t2 WHERE t1.parentid = t2.oid AND t2.relname = 'sales' AND t1.parttype = 'p';
+   relname | partstrategy |       boundaries
+  ---------+--------------+-------------------------
+   p1      | r            | {"2019-02-01 00:00:00"}
+   p2      | r            | {"2019-02-02 00:00:00"}
+  (2 rows)
+
+  -- If the data to be inserted does not match any partition, create a partition and insert the data into the new partition.
+  -- The range of the new partition is '2019-02-05 00:00:00' ≤ time_id < '2019-02-06 00:00:00'.
+  mogdb=# INSERT INTO sales VALUES(1, 12, '2019-02-05 00:00:00', 'a', 1, 1, 1);
+
+  -- If the data to be inserted does not match any partition, create a partition and insert the data into the new partition.
+  -- The range of the new partition is '2019-02-03 00:00:00' ≤ time_id < '2019-02-04 00:00:00'.
+  mogdb=# INSERT INTO sales VALUES(1, 12, '2019-02-03 00:00:00', 'a', 1, 1, 1);
+
+  -- View the partition information.
+  mogdb=# SELECT t1.relname, partstrategy, boundaries FROM pg_partition t1, pg_class t2 WHERE t1.parentid = t2.oid AND t2.relname = 'sales' AND t1.parttype = 'p';
+   relname | partstrategy |       boundaries
+  ---------+--------------+-------------------------
+   sys_p1  | i            | {"2019-02-06 00:00:00"}
+   sys_p2  | i            | {"2019-02-04 00:00:00"}
+   p1      | r            | {"2019-02-01 00:00:00"}
+   p2      | r            | {"2019-02-02 00:00:00"}
+  (4 rows)
+
+  ```
+
+- Example 5: Create a list partitioned table **test_list**. The table initially contains four partitions and the partition key is of the INT type. The ranges of the four partitions are 2000, 3000, 4000, and 5000 respectively.
+
+  ```sql
+  -- Create the test_list table.
+  mogdb=# create table test_list (col1 int, col2 int)
+  partition by list(col1)
+  (
+  partition p1 values (2000),
+  partition p2 values (3000),
+  partition p3 values (4000),
+  partition p4 values (5000)
+  );
+
+  -- Insert data.
+  mogdb=# INSERT INTO test_list VALUES(2000, 2000);
+  INSERT 0 1
+  mogdb=# INSERT INTO test_list VALUES(3000, 3000);
+  INSERT 0 1
+
+  -- View the partition information.
+  mogdb=# SELECT t1.relname, partstrategy, boundaries FROM pg_partition t1, pg_class t2 WHERE t1.parentid = t2.oid AND t2.relname = 'test_list' AND t1.parttype = 'p';
+   relname | partstrategy | boundaries
+  ---------+--------------+------------
+   p1      | l            | {2000}
+   p2      | l            | {3000}
+   p3      | l            | {4000}
+   p4      | l            | {5000}
+  (4 rows)
+
+  -- The inserted data does not match the partition, and an error is reported.
+  mogdb=# INSERT INTO test_list VALUES(6000, 6000);
+  ERROR:  inserted partition key does not map to any table partition
+
+  -- Add a partition.
+  mogdb=# alter table test_list add partition p5 values (6000);
+  ALTER TABLE
+  mogdb=# SELECT t1.relname, partstrategy, boundaries FROM pg_partition t1, pg_class t2 WHERE t1.parentid = t2.oid AND t2.relname = 'test_list' AND t1.parttype = 'p';
+   relname | partstrategy | boundaries
+  ---------+--------------+------------
+   p5      | l            | {6000}
+   p4      | l            | {5000}
+   p1      | l            | {2000}
+   p2      | l            | {3000}
+   p3      | l            | {4000}
+  (5 rows)
+  mogdb=# INSERT INTO test_list VALUES(6000, 6000);
+  INSERT 0 1
+
+  -- Exchange data between the partitioned table and ordinary table.
+  mogdb=# create table t1 (col1 int, col2 int);
+  CREATE TABLE
+  mogdb=# select * from test_list partition (p1);
+   col1 | col2
+  ------+------
+   2000 | 2000
+  (1 row)
+  mogdb=# alter table test_list exchange partition (p1) with table t1;
+  ALTER TABLE
+  mogdb=# select * from test_list partition (p1);
+   col1 | col2
+  ------+------
+  (0 rows)
+  mogdb=# select * from t1;
+   col1 | col2
+  ------+------
+   2000 | 2000
+  (1 row)
+
+  -- Truncate the partition.
+  mogdb=# select * from test_list partition (p2);
+   col1 | col2
+  ------+------
+   3000 | 3000
+  (1 row)
+  mogdb=# alter table test_list truncate partition p2;
+  ALTER TABLE
+  mogdb=# select * from test_list partition (p2);
+   col1 | col2
+  ------+------
+  (0 rows)
+
+  -- Delete the partition.
+  mogdb=# alter table test_list drop partition p5;
+  ALTER TABLE
+  mogdb=# SELECT t1.relname, partstrategy, boundaries FROM pg_partition t1, pg_class t2 WHERE t1.parentid = t2.oid AND t2.relname = 'test_list' AND t1.parttype = 'p';
+   relname | partstrategy | boundaries
+  ---------+--------------+------------
+   p4      | l            | {5000}
+   p1      | l            | {2000}
+   p2      | l            | {3000}
+   p3      | l            | {4000}
+  (4 rows)
+
+  mogdb=# INSERT INTO test_list VALUES(6000, 6000);
+  ERROR:  inserted partition key does not map to any table partition
+
+  -- Delete the partitioned table.
+  mogdb=# drop table test_list;
+  ```
+
+- Example 6: Create a hash partitioned table **test_hash**. The table initially contains two partitions and the partition key is of the INT type.
+
+  ```sql
+  -- Create the test_hash table.
+  mogdb=# create table test_hash (col1 int, col2 int)
+  partition by hash(col1)
+  (
+  partition p1,
+  partition p2
+  );
+
+  -- Insert data.
+  mogdb=# INSERT INTO test_hash VALUES(1, 1);
+  INSERT 0 1
+  mogdb=# INSERT INTO test_hash VALUES(2, 2);
+  INSERT 0 1
+  mogdb=# INSERT INTO test_hash VALUES(3, 3);
+  INSERT 0 1
+  mogdb=# INSERT INTO test_hash VALUES(4, 4);
+  INSERT 0 1
+
+  -- View the partition information.
+  mogdb=# SELECT t1.relname, partstrategy, boundaries FROM pg_partition t1, pg_class t2 WHERE t1.parentid = t2.oid AND t2.relname = 'test_hash' AND t1.parttype = 'p';
+   relname | partstrategy | boundaries
+  ---------+--------------+------------
+   p1      | h            | {0}
+   p2      | h            | {1}
+  (2 rows)
+
+  -- View the data.
+  mogdb=# select * from test_hash partition (p1);
+   col1 | col2
+  ------+------
+      3 |    3
+      4 |    4
+  (2 rows)
+
+  mogdb=# select * from test_hash partition (p2);
+   col1 | col2
+  ------+------
+      1 |    1
+      2 |    2
+  (2 rows)
+
+  -- Exchange data between the partitioned table and ordinary table.
+  mogdb=# create table t1 (col1 int, col2 int);
+  CREATE TABLE
+  mogdb=# alter table test_hash exchange partition (p1) with table t1;
+  ALTER TABLE
+  mogdb=# select * from test_hash partition (p1);
+   col1 | col2
+  ------+------
+  (0 rows)
+  mogdb=# select * from t1;
+   col1 | col2
+  ------+------
+      3 |    3
+      4 |    4
+  (2 rows)
+
+  -- Truncate the partition.
+  mogdb=# alter table test_hash truncate partition p2;
+  ALTER TABLE
+  mogdb=#  select * from test_hash partition (p2);
+   col1 | col2
+  ------+------
+  (0 rows)
+
+  -- Delete the partitioned table.
+  mogdb=# drop table test_hash;
+  ```
+
+## Helpful Links
+
+[ALTER TABLE PARTITION](23-ALTER-TABLE-PARTITION) and [DROP TABLE](95-DROP-TABLE)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/62.1-CREATE-TABLE-SUBPARTITION.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/62.1-CREATE-TABLE-SUBPARTITION.md
new file mode 100644
index 0000000000000000000000000000000000000000..32a6223979ae137e4b55492198cca28edaf5462d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/62.1-CREATE-TABLE-SUBPARTITION.md
@@ -0,0 +1,775 @@
+---
+title: CREATE TABLE SUBPARTITION
+summary: CREATE TABLE SUBPARTITION
+author: Zhang Cuiping
+date: 2021-11-01
+---
+
+# CREATE TABLE SUBPARTITION
+
+## Function
+
+Creates a level-2 partitioned table. A partitioned table is a logical table that is divided into several physical partitions for storage based on a specific plan. A partitioned table is a logical table and does not store data. Data is stored in physical partitions. For a level-2 partitioned table, the top-level node table and level-1 partitioned table are logical tables and do not store data. Only the level-2 partitioned (leaf node) stores data.
+
+The partitioning solution of a level-2 partitioned table is a combination of the partitioning solutions of two level-1 partitions. For details about the partitioning solution of a level-1 partitioned table, see [CREATE TABLE PARTITION](62-CREATE-TABLE-PARTITION).
+
+Common combination solutions for level-2 partitioned tables include range-range partitioning, range-list partitioning, range-hash partitioning, list-range partitioning, list-list partitioning, list-hash partitioning. Currently, level-2 partitioned tables can only be row-store tables.
+
+## Precautions
+
+- A level-2 partitioned table has two partition keys, and each partition key supports only one column.
+- If the constraint key of the unique constraint and primary key constraint contains all partition keys, a local index is created for the constraints. Otherwise, a global index is created.
+- The number of level-2 partitions (leaf nodes) in a level-2 partitioned table cannot exceed 1048575. The number of level-1 partitions cannot exceed 64, and there must be at least one level-2 partition under a level-1 partition.
+- Level-2 partitioned tables support only row store and do not support column-store, segment-page, or hash bucket.
+- UPSERT and MERGE INTO into are not supported.
+- When specifying a partition for query, for example, **select \* from tablename partition/subpartition** (*partitionname*), ensure that the keywords **partition** and **subpartition** are correct. If they are incorrect, an error is reported during the query. In this case, the query is performed based on the table alias.
+- Level-2 partitioned tables do not support the subpartition for (values) query, for example, **select \* from tablename subpartition for** (*values*).
+- Does not support secret database, ledger database and row-level access control.
+- Does not support subpartitions under INTERVAL partitions.
+
+## Syntax
+
+```ebnf+diagram
+CreateTableSubpartition ::= CREATE TABLE [ IF NOT EXISTS ] subpartition_table_name
+(
+{ column_name data_type [ COLLATE collation ] [ column_constraint [ ... ] ]
+| table_constraint
+| LIKE source_table [ like_option [...] ] }[, ... ]
+)
+[ WITH ( {storage_parameter = value} [, ... ] ) ]
+[ COMPRESS | NOCOMPRESS ]
+[ TABLESPACE tablespace_name ]
+PARTITION BY {RANGE | LIST} (partition_key) SUBPARTITION BY {RANGE | LIST | HASH} (subpartition_key)
+(
+  PARTITION partition_name1 [ VALUES LESS THAN (val1) | VALUES (val1[, ...]) ] [ TABLESPACE tablespace ]
+  (
+       { SUBPARTITION subpartition_name1 [ VALUES LESS THAN (val1_1) | VALUES (val1_1[, ...])]  [ TABLESPACE tablespace ] } [, ...]
+  )[, ...]
+)[ { ENABLE | DISABLE } ROW MOVEMENT ];
+```
+
+- Column constraint:
+
+  ```ebnf+diagram
+  column_constraint ::= [ CONSTRAINT constraint_name ]
+  { NOT NULL |
+    NULL |
+    CHECK ( expression ) |
+    DEFAULT default_e xpr |
+    GENERATED ALWAYS AS ( generation_expr ) STORED |
+    UNIQUE index_parameters |
+    PRIMARY KEY index_parameters |
+    REFERENCES reftable [ ( refcolumn ) ] [ MATCH FULL | MATCH PARTIAL | MATCH SIMPLE ]
+          [ ON DELETE action ] [ ON UPDATE action ] }
+  [ DEFERRABLE | NOT DEFERRABLE | INITIALLY DEFERRED | INITIALLY IMMEDIATE ]
+  ```
+
+- Table constraint:
+
+  ```ebnf+diagram
+  table_constraint ::= [ CONSTRAINT constraint_name ]
+  { CHECK ( expression ) |
+    UNIQUE ( column_name [, ... ] ) index_parameters |
+    PRIMARY KEY ( column_name [, ... ] ) index_parameters |
+    FOREIGN KEY ( column_name [, ... ] ) REFERENCES reftable [ ( refcolumn [, ... ] ) ]
+        [ MATCH FULL | MATCH PARTIAL | MATCH SIMPLE ] [ ON DELETE action ] [ ON UPDATE action ] }
+  [ DEFERRABLE | NOT DEFERRABLE | INITIALLY DEFERRED | INITIALLY IMMEDIATE ]
+  ```
+
+- LIKE options:
+
+  ```ebnf+diagram
+  like_option ::= { INCLUDING | EXCLUDING } { DEFAULTS | GENERATED | CONSTRAINTS | INDEXES | STORAGE | COMMENTS | RELOPTIONS| ALL }
+  ```
+
+- Index parameters:
+
+  ```ebnf+diagram
+  index_parameters ::= [ WITH ( {storage_parameter = value} [, ... ] ) ]
+  [ USING INDEX TABLESPACE tablespace_name ]
+  ```
+
+## Parameter Description
+
+- **IF NOT EXISTS**
+
+  Does not throw an error if a relationship with the same name existed. A notice is issued in this case.
+
+- **subpartition_table_name**
+
+  Specifies the name of a level-2 partitioned table.
+
+  Value range: a string. It must comply with the identifier naming convention.
+
+- **column_name**
+
+  Specifies the name of a column to be created in the new table.
+
+  Value range: a string. It must comply with the identifier naming convention.
+
+- **data_type**
+
+  Specifies the data type of the column.
+
+- **COLLATE collation**
+
+  Assigns a collation to the column (which must be of a collatable data type). If no collation is specified, the default collation is used. You can run the **select \* from pg_collation;** command to query collation rules from the **pg_collation** system catalog. The default collation rule is the row starting with **default** in the query result.
+
+- **CONSTRAINT constraint_name**
+
+  Specifies the name of a column or table constraint. The optional constraint clauses specify constraints that new or updated rows must satisfy for an INSERT or UPDATE operation to succeed.
+
+  There are two ways to define constraints:
+
+  - A column constraint is defined as part of a column definition, and it is bound to a particular column.
+  - A table constraint is not bound to a particular column and can apply to more than one column.
+
+- **LIKE source_table [ like_option … ]**
+
+The secondary partition table does not support this function temporarily.
+
+- **WITH ( storage_parameter [= value] [, … ] )**
+
+  Specifies an optional storage parameter for a table or an index. Optional parameters are as follows:
+
+  - FILLFACTOR
+
+    The fill factor of a table is a percentage from 10 to 100. **100** (complete filling) is the default value. When a smaller fill factor is specified, INSERT operations fill table pages only to the indicated percentage. The remaining space on each page is reserved for updating rows on that page. This gives UPDATE a chance to place the updated copy of a row on the same page, which is more efficient than placing it on a different page. For a table whose entries are never updated, setting the fill factor to **100** (complete filling) is the best choice, but in heavily updated tables a smaller fill factor would be appropriate. The parameter has no meaning for column-store tables.
+
+    Value range: 10-100
+
+  - ORIENTATION
+
+    Determines the data storage mode of the table.
+
+    Value range:
+
+    - **COLUMN**: The data will be stored in columns.
+
+    - **ROW** (default value): The data will be stored in rows.
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** **ORIENTATION** cannot be modified.
+
+  - COMPRESSION
+
+    - Value range: **LOW**, **MIDDLE**, **HIGH**, **YES**, and **NO** for column-store tables, with compression level increasing in ascending order. The default value is **LOW**.
+    - Row-store tables cannot be compressed.
+
+  - MAX_BATCHROW
+
+    Specifies the maximum number of records in a storage unit during data loading. The parameter is only valid for column-store tables.
+
+    Value range: 10000 to 60000. The default value is **60000**.
+
+  - PARTIAL_CLUSTER_ROWS
+
+    Specifies the number of records to be partially clustered for storage during data loading. The parameter is only valid for column-store tables.
+
+    Value range: greater than or equal to **MAX_BATCHROW**. You are advised to set this parameter to an integer multiple of **MAX_BATCHROW**.
+
+  - DELTAROW_THRESHOLD
+
+    A reserved parameter. The parameter is only valid for column-store tables.
+
+    Value range: 0 to 9999
+
+- **COMPRESS / NOCOMPRESS**
+
+  Specifies keyword COMPRESS during the creation of a table, so that the compression feature is triggered in case of BULK INSERT operations. If this feature is enabled, a scan is performed for all tuple data within the page to generate a dictionary and then the tuple data is compressed and stored. If **NOCOMPRESS** is specified, the table is not compressed. Row-store tables cannot be compressed.
+
+  Default value: **NOCOMPRESS**, that is, tuple data is not compressed before storage.
+
+- **TABLESPACE tablespace_name**
+
+  Specifies that the new table will be created in the **tablespace_name** tablespace. If the tablespace is not specified, the default tablespace is used.
+
+- **PARTITION BY {RANGE | LIST | HASH} (partition_key)**
+
+  - For **partition_key**, the partitioning policy supports only one column of partition keys.
+  - The data types supported by the partition key are the same as those supported by the level-1 partitioned table.
+
+- **SUBPARTITION BY {RANGE | LIST | HASH} (subpartition_key)**
+
+  - For **subpartition_key**, the partitioning policy supports only one column of partition keys.
+  - The data types supported by the partition key are the same as those supported by the level-1 partitioned table.
+
+- **{ ENABLE | DISABLE } ROW MOVEMENT**
+
+    Specifies whether to enable row movement.
+
+    If the tuple value is updated on the partition key during the UPDATE operation, the partition where the tuple is located is altered. Setting this parameter enables error messages to be reported or movement of the tuple between partitions.
+
+    Value range:
+
+  - **ENABLE** (default value): Row movement is enabled.
+  - **DISABLE**: Row movement is disabled.
+
+- **NOT NULL**
+
+  The column is not allowed to contain null values. **ENABLE** can be omitted.
+
+- **NULL**
+
+  Indicates that the column is allowed to contain **NULL** values. This is the default setting.
+
+  This clause is only provided for compatibility with non-standard SQL databases. It is not recommended.
+
+- **CHECK (condition) [ NO INHERIT ]**
+
+  Specifies an expression producing a Boolean result where the INSERT or UPDATE operation of new or updated rows can succeed only when the expression result is **TRUE** or **UNKNOWN**; otherwise, an error is thrown and the database is not altered.
+
+  A check constraint specified as a column constraint should reference only the column's values, while an expression in a table constraint can reference multiple columns.
+
+  A constraint marked with **NO INHERIT** will not propagate to child tables.
+
+  **ENABLE** can be omitted.
+
+- **DEFAULT default_expr**
+
+  Assigns a default data value to a column. The value can be any variable-free expressions. (Subqueries and cross-references to other columns in the current table are not allowed.) The data type of the default expression must match that of the column.
+
+  The default expression will be used in any INSERT operation that does not specify a value for the column. If there is no default value for a column, then the default value is **NULL**.
+
+- **GENERATED ALWAYS AS ( generation_expr ) STORED**
+
+  This clause creates a column as a generated column. The value of the generated column is calculated by **generation_expr** when data is written (inserted or updated). **STORED** indicates that the value of the generated column is stored as a common column.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > - The generation expression cannot refer to data other than the current row in any way. The generation expression cannot reference other generation columns or system columns. The generation expression cannot return a result set. No subquery, aggregate function, or window function can be used. The function called by the generation expression can only be an immutable function.
+  > - Default values cannot be specified for generated columns.
+  > - The generated column cannot be used as a part of the partition key.
+  > - Do not specify the generated column and the CASCADE, SET NULL, and SET DEFAULT actions of the ON UPDATE constraint at the same time. Do not specify the generated column and the SET NULL, and SET DEFAULT actions of the ON DELETE constraint at the same time.
+  > - The method of modifying and deleting generated columns is the same as that of common columns. Delete the common column that the generated column depends on. The generated column is automatically deleted. The type of the column on which the generated column depends cannot be changed.
+  > - The generated column cannot be directly written. In the INSERT or UPDATE statement, values cannot be specified for generated columns, but the keyword DEFAULT can be specified.
+  > - The permission control for generated columns is the same as that for common columns.
+  > - Columns cannot be generated for column-store tables and MOTs. In foreign tables, only **postgres_fdw** supports generated columns.
+
+- **UNIQUE index_parameters**
+
+  **UNIQUE ( column_name [, … ] ) index_parameters**
+
+  Specifies that a group of one or more columns of a table can contain only unique values.
+
+  For the purpose of a unique constraint, null is not considered equal.
+
+- **PRIMARY KEY index_parameters**
+
+  **PRIMARY KEY ( column_name [, … ] ) index_parameters**
+
+  Specifies that a column or columns of a table can contain only unique (non-duplicate) and non-**NULL** values.
+
+  Only one primary key can be specified for a table.
+
+- **DEFERRABLE | NOT DEFERRABLE**
+
+  They determine whether the constraint is deferrable. A constraint that is not deferrable will be checked immediately after every command. Checking of constraints that are deferrable can be postponed until the end of the transaction using the **SET CONSTRAINTS** command. **NOT DEFERRABLE** is the default value. Currently, only UNIQUE constraints, primary key constraints, and foreign key constraints accept this clause. All the other constraints are not deferrable.
+
+- **INITIALLY IMMEDIATE | INITIALLY DEFERRED**
+
+    If a constraint is deferrable, this clause specifies the default time to check the constraint.
+
+  - If the constraint is **INITIALLY IMMEDIATE** (default value), it is checked after each statement.
+  - If the constraint is **INITIALLY DEFERRED**, it is checked only at the end of the transaction.
+
+    The constraint check time can be altered using the **SET CONSTRAINTS** statement.
+
+- **USING INDEX TABLESPACE tablespace_name**
+
+  Allows selection of the tablespace in which the index associated with a **UNIQUE** or **PRIMARY KEY** constraint will be created. If not specified, the index is created in **default_tablespace**. If **default_tablespace** is empty, the default tablespace of the database is used.
+
+## Examples
+
+- Example 1: Create level-2 partitioned tables of various combination types.
+
+  ```sql
+  CREATE TABLE list_list
+  (
+      month_code VARCHAR2 ( 30 ) NOT NULL ,
+      dept_code  VARCHAR2 ( 30 ) NOT NULL ,
+      user_no    VARCHAR2 ( 30 ) NOT NULL ,
+      sales_amt  int
+  )
+  PARTITION BY LIST (month_code) SUBPARTITION BY LIST (dept_code)
+  (
+    PARTITION p_201901 VALUES ( '201902' )
+    (
+      SUBPARTITION p_201901_a VALUES ( '1' ),
+      SUBPARTITION p_201901_b VALUES ( '2' )
+    ),
+    PARTITION p_201902 VALUES ( '201903' )
+    (
+      SUBPARTITION p_201902_a VALUES ( '1' ),
+      SUBPARTITION p_201902_b VALUES ( '2' )
+    )
+  );
+  insert into list_list values('201902', '1', '1', 1);
+  insert into list_list values('201902', '2', '1', 1);
+  insert into list_list values('201902', '1', '1', 1);
+  insert into list_list values('201903', '2', '1', 1);
+  insert into list_list values('201903', '1', '1', 1);
+  insert into list_list values('201903', '2', '1', 1);
+  select * from list_list;
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201903     | 2         | 1       |         1
+   201903     | 2         | 1       |         1
+   201903     | 1         | 1       |         1
+   201902     | 2         | 1       |         1
+   201902     | 1         | 1       |         1
+   201902     | 1         | 1       |         1
+  (6 rows)
+  
+  drop table list_list;
+  CREATE TABLE list_hash
+  (
+      month_code VARCHAR2 ( 30 ) NOT NULL ,
+      dept_code  VARCHAR2 ( 30 ) NOT NULL ,
+      user_no    VARCHAR2 ( 30 ) NOT NULL ,
+      sales_amt  int
+  )
+  PARTITION BY LIST (month_code) SUBPARTITION BY HASH (dept_code)
+  (
+    PARTITION p_201901 VALUES ( '201902' )
+    (
+      SUBPARTITION p_201901_a,
+      SUBPARTITION p_201901_b
+    ),
+    PARTITION p_201902 VALUES ( '201903' )
+    (
+      SUBPARTITION p_201902_a,
+      SUBPARTITION p_201902_b
+    )
+  );
+  insert into list_hash values('201902', '1', '1', 1);
+  insert into list_hash values('201902', '2', '1', 1);
+  insert into list_hash values('201902', '3', '1', 1);
+  insert into list_hash values('201903', '4', '1', 1);
+  insert into list_hash values('201903', '5', '1', 1);
+  insert into list_hash values('201903', '6', '1', 1);
+  select * from list_hash;
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201903     | 4         | 1       |         1
+   201903     | 5         | 1       |         1
+   201903     | 6         | 1       |         1
+   201902     | 2         | 1       |         1
+   201902     | 3         | 1       |         1
+   201902     | 1         | 1       |         1
+  (6 rows)
+  
+  drop table list_hash;
+  CREATE TABLE list_range
+  (
+      month_code VARCHAR2 ( 30 ) NOT NULL ,
+      dept_code  VARCHAR2 ( 30 ) NOT NULL ,
+      user_no    VARCHAR2 ( 30 ) NOT NULL ,
+      sales_amt  int
+  )
+  PARTITION BY LIST (month_code) SUBPARTITION BY RANGE (dept_code)
+  (
+    PARTITION p_201901 VALUES ( '201902' )
+    (
+      SUBPARTITION p_201901_a values less than ('4'),
+      SUBPARTITION p_201901_b values less than ('6')
+    ),
+    PARTITION p_201902 VALUES ( '201903' )
+    (
+      SUBPARTITION p_201902_a values less than ('3'),
+      SUBPARTITION p_201902_b values less than ('6')
+    )
+  );
+  insert into list_range values('201902', '1', '1', 1);
+  insert into list_range values('201902', '2', '1', 1);
+  insert into list_range values('201902', '3', '1', 1);
+  insert into list_range values('201903', '4', '1', 1);
+  insert into list_range values('201903', '5', '1', 1);
+  insert into list_range values('201903', '6', '1', 1);
+  ERROR:  inserted partition key does not map to any table partition
+  select * from list_range;
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201903     | 4         | 1       |         1
+   201903     | 5         | 1       |         1
+   201902     | 1         | 1       |         1
+   201902     | 2         | 1       |         1
+   201902     | 3         | 1       |         1
+  (5 rows)
+  
+  drop table list_range;
+  CREATE TABLE range_list
+  (
+      month_code VARCHAR2 ( 30 ) NOT NULL ,
+      dept_code  VARCHAR2 ( 30 ) NOT NULL ,
+      user_no    VARCHAR2 ( 30 ) NOT NULL ,
+      sales_amt  int
+  )
+  PARTITION BY RANGE (month_code) SUBPARTITION BY LIST (dept_code)
+  (
+    PARTITION p_201901 VALUES LESS THAN( '201903' )
+    (
+      SUBPARTITION p_201901_a values ('1'),
+      SUBPARTITION p_201901_b values ('2')
+    ),
+    PARTITION p_201902 VALUES LESS THAN( '201904' )
+    (
+      SUBPARTITION p_201902_a values ('1'),
+      SUBPARTITION p_201902_b values ('2')
+    )
+  );
+  insert into range_list values('201902', '1', '1', 1);
+  insert into range_list values('201902', '2', '1', 1);
+  insert into range_list values('201902', '1', '1', 1);
+  insert into range_list values('201903', '2', '1', 1);
+  insert into range_list values('201903', '1', '1', 1);
+  insert into range_list values('201903', '2', '1', 1);
+  select * from range_list;
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201902     | 2         | 1       |         1
+   201902     | 1         | 1       |         1
+   201902     | 1         | 1       |         1
+   201903     | 2         | 1       |         1
+   201903     | 2         | 1       |         1
+   201903     | 1         | 1       |         1
+  (6 rows)
+  
+  drop table range_list;
+  CREATE TABLE range_hash
+  (
+      month_code VARCHAR2 ( 30 ) NOT NULL ,
+      dept_code  VARCHAR2 ( 30 ) NOT NULL ,
+      user_no    VARCHAR2 ( 30 ) NOT NULL ,
+      sales_amt  int
+  )
+  PARTITION BY RANGE (month_code) SUBPARTITION BY HASH (dept_code)
+  (
+    PARTITION p_201901 VALUES LESS THAN( '201903' )
+    (
+      SUBPARTITION p_201901_a,
+      SUBPARTITION p_201901_b
+    ),
+    PARTITION p_201902 VALUES LESS THAN( '201904' )
+    (
+      SUBPARTITION p_201902_a,
+      SUBPARTITION p_201902_b
+    )
+  );
+  insert into range_hash values('201902', '1', '1', 1);
+  insert into range_hash values('201902', '2', '1', 1);
+  insert into range_hash values('201902', '1', '1', 1);
+  insert into range_hash values('201903', '2', '1', 1);
+  insert into range_hash values('201903', '1', '1', 1);
+  insert into range_hash values('201903', '2', '1', 1);
+  select * from range_hash;
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201902     | 2         | 1       |         1
+   201902     | 1         | 1       |         1
+   201902     | 1         | 1       |         1
+   201903     | 2         | 1       |         1
+   201903     | 2         | 1       |         1
+   201903     | 1         | 1       |         1
+  (6 rows)
+  
+  drop table range_hash;
+  CREATE TABLE range_range
+  (
+      month_code VARCHAR2 ( 30 ) NOT NULL ,
+      dept_code  VARCHAR2 ( 30 ) NOT NULL ,
+      user_no    VARCHAR2 ( 30 ) NOT NULL ,
+      sales_amt  int
+  )
+  PARTITION BY RANGE (month_code) SUBPARTITION BY RANGE (dept_code)
+  (
+    PARTITION p_201901 VALUES LESS THAN( '201903' )
+    (
+      SUBPARTITION p_201901_a VALUES LESS THAN( '2' ),
+      SUBPARTITION p_201901_b VALUES LESS THAN( '3' )
+    ),
+    PARTITION p_201902 VALUES LESS THAN( '201904' )
+    (
+      SUBPARTITION p_201902_a VALUES LESS THAN( '2' ),
+      SUBPARTITION p_201902_b VALUES LESS THAN( '3' )
+    )
+  );
+  insert into range_range values('201902', '1', '1', 1);
+  insert into range_range values('201902', '2', '1', 1);
+  insert into range_range values('201902', '1', '1', 1);
+  insert into range_range values('201903', '2', '1', 1);
+  insert into range_range values('201903', '1', '1', 1);
+  insert into range_range values('201903', '2', '1', 1);
+  select * from range_range;
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201902     | 1         | 1       |         1
+   201902     | 1         | 1       |         1
+   201902     | 2         | 1       |         1
+   201903     | 1         | 1       |         1
+   201903     | 2         | 1       |         1
+   201903     | 2         | 1       |         1
+  (6 rows)
+  
+  drop table range_range;
+  ```
+  
+- Example 2: Truncate a level-2 partitioned table.
+
+  ```sql
+  CREATE TABLE list_list
+  (
+      month_code VARCHAR2 ( 30 ) NOT NULL ,
+      dept_code  VARCHAR2 ( 30 ) NOT NULL ,
+      user_no    VARCHAR2 ( 30 ) NOT NULL ,
+      sales_amt  int
+  )
+  PARTITION BY LIST (month_code) SUBPARTITION BY LIST (dept_code)
+  (
+    PARTITION p_201901 VALUES ( '201902' )
+    (
+      SUBPARTITION p_201901_a VALUES ( '1' ),
+      SUBPARTITION p_201901_b VALUES ( default )
+    ),
+    PARTITION p_201902 VALUES ( '201903' )
+    (
+      SUBPARTITION p_201902_a VALUES ( '1' ),
+      SUBPARTITION p_201902_b VALUES ( '2' )
+    )
+  );
+  insert into list_list values('201902', '1', '1', 1);
+  insert into list_list values('201902', '2', '1', 1);
+  insert into list_list values('201902', '1', '1', 1);
+  insert into list_list values('201903', '2', '1', 1);
+  insert into list_list values('201903', '1', '1', 1);
+  insert into list_list values('201903', '2', '1', 1);
+  select * from list_list;
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201903     | 2         | 1       |         1
+   201903     | 2         | 1       |         1
+   201903     | 1         | 1       |         1
+   201902     | 2         | 1       |         1
+   201902     | 1         | 1       |         1
+   201902     | 1         | 1       |         1
+  (6 rows)
+
+  select * from list_list partition (p_201901);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201902     | 2         | 1       |         1
+   201902     | 1         | 1       |         1
+   201902     | 1         | 1       |         1
+  (3 rows)
+
+  alter table list_list truncate partition p_201901;
+  select * from list_list partition (p_201901);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+  (0 rows)
+
+  select * from list_list partition (p_201902);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201903     | 2         | 1       |         1
+   201903     | 2         | 1       |         1
+   201903     | 1         | 1       |         1
+  (3 rows)
+
+  alter table list_list truncate partition p_201902;
+  select * from list_list partition (p_201902);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+  (0 rows)
+
+  select * from list_list;
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+  (0 rows)
+
+  insert into list_list values('201902', '1', '1', 1);
+  insert into list_list values('201902', '2', '1', 1);
+  insert into list_list values('201902', '1', '1', 1);
+  insert into list_list values('201903', '2', '1', 1);
+  insert into list_list values('201903', '1', '1', 1);
+  insert into list_list values('201903', '2', '1', 1);
+  select * from list_list subpartition (p_201901_a);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201902     | 1         | 1       |         1
+   201902     | 1         | 1       |         1
+  (2 rows)
+
+  alter table list_list truncate subpartition p_201901_a;
+  select * from list_list subpartition (p_201901_a);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+  (0 rows)
+
+  select * from list_list subpartition (p_201901_b);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201902     | 2         | 1       |         1
+  (1 row)
+
+  alter table list_list truncate subpartition p_201901_b;
+  select * from list_list subpartition (p_201901_b);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+  (0 rows)
+
+  select * from list_list subpartition (p_201902_a);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201903     | 1         | 1       |         1
+  (1 row)
+
+  alter table list_list truncate subpartition p_201902_a;
+  select * from list_list subpartition (p_201902_a);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+  (0 rows)
+
+  select * from list_list subpartition (p_201902_b);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201903     | 2         | 1       |         1
+   201903     | 2         | 1       |         1
+  (2 rows)
+
+  alter table list_list truncate subpartition p_201902_b;
+  select * from list_list subpartition (p_201902_b);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+  (0 rows)
+
+  select * from list_list;
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+  (0 rows)
+
+  drop table list_list;
+
+  ```
+
+- Example 3: Split a level-2 partitioned table.
+
+  ```sql
+  CREATE TABLE list_list
+  (
+      month_code VARCHAR2 ( 30 ) NOT NULL ,
+      dept_code  VARCHAR2 ( 30 ) NOT NULL ,
+      user_no    VARCHAR2 ( 30 ) NOT NULL ,
+      sales_amt  int
+  )
+  PARTITION BY LIST (month_code) SUBPARTITION BY LIST (dept_code)
+  (
+    PARTITION p_201901 VALUES ( '201902' )
+    (
+      SUBPARTITION p_201901_a VALUES ( '1' ),
+      SUBPARTITION p_201901_b VALUES ( default )
+    ),
+    PARTITION p_201902 VALUES ( '201903' )
+    (
+      SUBPARTITION p_201902_a VALUES ( '1' ),
+      SUBPARTITION p_201902_b VALUES ( default )
+    )
+  );
+  insert into list_list values('201902', '1', '1', 1);
+  insert into list_list values('201902', '2', '1', 1);
+  insert into list_list values('201902', '1', '1', 1);
+  insert into list_list values('201903', '2', '1', 1);
+  insert into list_list values('201903', '1', '1', 1);
+  insert into list_list values('201903', '2', '1', 1);
+  select * from list_list;
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201903     | 2         | 1       |         1
+   201903     | 2         | 1       |         1
+   201903     | 1         | 1       |         1
+   201902     | 2         | 1       |         1
+   201902     | 1         | 1       |         1
+   201902     | 1         | 1       |         1
+  (6 rows)
+  
+  select * from list_list subpartition (p_201901_a);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201902     | 1         | 1       |         1
+   201902     | 1         | 1       |         1
+  (2 rows)
+  
+  select * from list_list subpartition (p_201901_b);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201902     | 2         | 1       |         1
+  (1 row)
+  
+  alter table list_list split subpartition p_201901_b values (2) into
+  (
+   subpartition p_201901_b,
+   subpartition p_201901_c
+  );
+  select * from list_list subpartition (p_201901_a);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201902     | 1         | 1       |         1
+   201902     | 1         | 1       |         1
+  (2 rows)
+  
+  select * from list_list subpartition (p_201901_b);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201902     | 2         | 1       |         1
+  (1 row)
+  
+  select * from list_list subpartition (p_201901_c);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+  (0 rows)
+  
+  select * from list_list partition (p_201901);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201902     | 2         | 1       |         1
+   201902     | 1         | 1       |         1
+   201902     | 1         | 1       |         1
+  (3 rows)
+  
+  select * from list_list subpartition (p_201902_a);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201903     | 1         | 1       |         1
+  (1 row)
+  
+  select * from list_list subpartition (p_201902_b);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201903     | 2         | 1       |         1
+   201903     | 2         | 1       |         1
+  (2 rows)
+  
+  alter table list_list split subpartition p_201902_b values (3) into
+  (
+   subpartition p_201902_b,
+   subpartition p_201902_c
+  );
+  select * from list_list subpartition (p_201902_a);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201903     | 1         | 1       |         1
+  (1 row)
+  
+  select * from list_list subpartition (p_201902_b);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+  (0 rows)
+  
+  select * from list_list subpartition (p_201902_c);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201903     | 2         | 1       |         1
+   201903     | 2         | 1       |         1
+  (2 rows)
+  
+  drop table list_list;
+  ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/63-CREATE-TABLESPACE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/63-CREATE-TABLESPACE.md
new file mode 100644
index 0000000000000000000000000000000000000000..bcaf6307ca879e3a772911d5bc97fc0fecc6219b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/63-CREATE-TABLESPACE.md
@@ -0,0 +1,136 @@
+---
+title: CREATE TABLESPACE
+summary: CREATE TABLESPACE
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE TABLESPACE
+
+## Function
+
+**CREATE TABLESPACE** creates a tablespace in a database.
+
+## Precautions
+
+- The system administrator or a user who inherits the  **gs_roles_tablespace**  permission of the built-in role can create a tablespace.
+- Do not run **CREATE TABLESPACE** in a transaction block.
+- If executing **CREATE TABLESPACE** fails but the internal directory (or file) has been created, the directory (or file) will remain. You need to manually clear it before creating the tablespace again. If there are residual files of soft links for the tablespace in the data directory, delete the residual files, and then perform O&M operations.
+- **CREATE TABLESPACE** cannot be used for two-phase transactions. If it fails on some nodes, the execution cannot be rolled back.
+- For details about how to prepare for creating tablespaces, see the description of parameters below.
+- In scenarios such as HCS, you are not advised to use user-defined tablespaces. This is because user-defined tablespaces are usually used with storage media other than the main storage (storage device where the default tablespace is located, such as a disk) to isolate I/O resources that can be used by different services. In HCS scenarios, storage devices use standard configurations and do not have other available storage media. If the customized tablespace is not properly used, the system cannot run stably for a long time and the overall performance is affected. Therefore, you are advised to use the default tablespace.
+
+## Syntax
+
+```ebnf+diagram
+CreateTablespace ::= CREATE TABLESPACE tablespace_name
+    [ OWNER user_name ] [RELATIVE] LOCATION 'directory' [ MAXSIZE 'space_size' ]
+    [with_option_clause];
+```
+
+The **with_option_clause** syntax for creating a general tablespace is as follows:
+
+```ebnf+diagram
+with_option_clause ::= WITH ( {filesystem= { 'general'| "general" | general} |
+    random_page_cost = { 'value ' | value } |
+    seq_page_cost = { 'value ' | value }}[,...]);
+```
+
+## Parameter Description
+
+- **tablespace_name**
+
+  Specifies name of a tablespace to be created.
+
+  The tablespace name must be distinct from the name of any existing tablespace in MogDB and cannot start with "pg", which are reserved for system catalog spaces.
+
+  Value range: a string. It must comply with the identifier naming convention.
+
+- **OWNER user_name**
+
+  Specifies the name of the user who will own the tablespace. If omitted, the default owner is the current user.
+
+  Only system administrators can create tablespaces, but they can use the **OWNER** clause to assign ownership of tablespaces to non-**Sysadmin** administrators.
+
+  Value range: a string. It must be an existing user.
+
+- **RELATIVE**
+
+  Relative path. The **LOCATION** directory is relative to the data directory in each database node.
+
+  Directory hierarchy: the relative path of the database node directory **/pg_location/**
+
+  A relative path contains a maximum of two levels.
+
+- **LOCATION directory**
+
+    Specifies the directory used for the tablespace. The directory must meet the following requirements:
+
+  - The MogDB system user must have the read and write permissions on the directory, and the directory must be empty. If the directory does not exist, the system automatically creates it.
+  - The directory must be an absolute path, and does not contain special characters, such as dollar sign ($) and greater-than sign (&gt;).
+  - The directory cannot be specified under the database data directory.
+  - The directory must be a local path.
+
+    Value range: a string. It must be a valid directory.
+
+- **MAXSIZE 'space_size'**
+
+  Specifies the maximum value of the tablespace in a single database node.
+
+  Value range: a string consisting of a positive integer and unit. The unit can be KB, MB, GB, TB, or PB currently. The unit of parsed value is KB and cannot exceed the range that can be expressed in 64 bits, which is 1 KB to 9007199254740991 KB.
+
+- **random_page_cost**
+
+  Specifies the cost of randomly reading the page overhead.
+
+  Value range: 0 to 1.79769e+308
+
+  Default value: value of the GUC parameter **random_page_cost**
+
+- **seq_page_cost**
+
+  Specifies the cost of reading the page overhead in specified order.
+
+  Value range: 0 to 1.79769e+308
+
+  Default value: value of GUC parameter **seq_page_cost**
+
+## Examples
+
+```sql
+-- Create a tablespace.
+mogdb=# CREATE TABLESPACE ds_location1 RELATIVE LOCATION 'tablespace/tablespace_1';
+
+-- Create user joe.
+mogdb=# CREATE ROLE joe IDENTIFIED BY 'xxxxxxxxx';
+
+-- Create user jay.
+mogdb=# CREATE ROLE jay IDENTIFIED BY 'xxxxxxxxx';
+
+-- Create a tablespace and set its owner to user joe.
+mogdb=# CREATE TABLESPACE ds_location2 OWNER joe RELATIVE LOCATION 'tablespace/tablespace_1';
+
+-- Rename the ds_location1 tablespace to ds_location3.
+mogdb=# ALTER TABLESPACE ds_location1 RENAME TO ds_location3;
+
+-- Change the owner of the ds_location2 tablespace.
+mogdb=# ALTER TABLESPACE ds_location2 OWNER TO jay;
+
+-- Delete the tablespace.
+mogdb=# DROP TABLESPACE ds_location2;
+mogdb=# DROP TABLESPACE ds_location3;
+
+-- Delete users.
+mogdb=# DROP ROLE joe;
+mogdb=# DROP ROLE jay;
+```
+
+## Helpful Links
+
+[CREATE DATABASE](44-CREATE-DATABASE)，[CREATE TABLE](60-CREATE-TABLE)，[CREATE INDEX](50-CREATE-INDEX)，[DROP TABLESPACE](96-DROP-TABLESPACE)，[ALTER TABLESPACE](24-ALTER-TABLESPACE)
+
+## Suggestions
+
+- create tablespace
+
+  You are not advised to create tablespaces in a transaction.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/64-CREATE-TEXT-SEARCH-CONFIGURATION.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/64-CREATE-TEXT-SEARCH-CONFIGURATION.md
new file mode 100644
index 0000000000000000000000000000000000000000..5a74f46faf61107b96c52b46308cfa3b14aa75c6
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/64-CREATE-TEXT-SEARCH-CONFIGURATION.md
@@ -0,0 +1,96 @@
+---
+title: CREATE TEXT SEARCH CONFIGURATION
+summary: CREATE TEXT SEARCH CONFIGURATION
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE TEXT SEARCH CONFIGURATION
+
+## Function
+
+**CREATE TEXT SEARCH CONFIGURATION** creates a text search configuration. A text search configuration specifies a text search parser that can divide a string into tokens, plus dictionaries that can be used to determine which tokens are of interest for searching.
+
+## Precautions
+
+- If only the parser is specified, the new text search configuration initially has no mapping from token types to dictionaries, and therefore will ignore all words. Subsequently, **ALTER TEXT SEARCH CONFIGURATION** must be used to create mapping to make the configuration useful. If **COPY** is specified, the parser, mapping and parameters of the text search configuration is copied automatically.
+- If the schema name is given, the text search configuration will be created in the specified schema. Otherwise, the configuration will be created in the current schema.
+- The user who defines a text search configuration becomes its owner.
+- **PARSER** and **COPY** options are mutually exclusive, because when an existing configuration is copied, its parser selection is copied too.
+- If only the parser is specified, the new text search configuration initially has no mapping from token types to dictionaries, and therefore will ignore all words.
+
+## Syntax
+
+```ebnf+diagram
+CreateTextSearchConfiguration ::= CREATE TEXT SEARCH CONFIGURATION name
+    ( PARSER = parser_name | COPY = source_config )
+    [ WITH ( {configuration_option = value} [, ...] )];
+```
+
+## Parameter Description
+
+- **name**
+
+  Specifies the name of the text search configuration to be created. The name can be schema-qualified.
+
+- **parser_name**
+
+  Specifies the name of the text search parser to use for this configuration.
+
+- **source_config**
+
+  Specifies the name of an existing text search configuration to copy.
+
+- **configuration_option**
+
+  Specifies parameters for the text search configuration, particularly for the parser executed by **parser_name** or contained by **source_config**.
+
+  Value range: The default and **ngram** parsers are supported. The parser of default type has no corresponding **configuration_option**. Table 1 lists **configuration_option** for **ngram** parsers.
+
+  **Table 1** Configuration parameters for **ngram** parsers <a id="configurationparameter"> </a>
+
+  | Parser             | Parameter                              | Description                                                  | Value Range                               |
+  | :------------------------------------- | :------------------------------------- | :----------------------------------------------------------- | :---------------------------------------- |
+  | ngram              | gram_size                              | Length of word segmentation                                  | Integer, 1 to 4<br />Default value: **2** |
+  | punctuation_ignore | Whether to ignore punctuations         | - **true** (default value): Ignore punctuations.<br />- **false**: Do not ignore punctuations. |                                           |
+  | grapsymbol_ignore  | Whether to ignore graphical characters | - **true**: Ignore graphical characters.<br />- **false** (default value): Do not ignore graphical characters. |                                           |
+
+## Examples
+
+```sql
+-- Create a text search configuration.
+mogdb=# CREATE TEXT SEARCH CONFIGURATION ngram2 (parser=ngram) WITH (gram_size = 2, grapsymbol_ignore = false);
+
+-- Create a text search configuration.
+mogdb=# CREATE TEXT SEARCH CONFIGURATION ngram3 (copy=ngram2) WITH (gram_size = 2, grapsymbol_ignore = false);
+
+-- Add type mapping.
+mogdb=# ALTER TEXT SEARCH CONFIGURATION ngram2 ADD MAPPING FOR multisymbol WITH simple;
+
+-- Create user joe.
+mogdb=# CREATE USER joe IDENTIFIED BY 'xxxxxxxxx';
+
+-- Change the owner of the text search configuration.
+mogdb=# ALTER TEXT SEARCH CONFIGURATION ngram2 OWNER TO joe;
+
+-- Change the schema of the text search configuration.
+mogdb=# ALTER TEXT SEARCH CONFIGURATION ngram2 SET SCHEMA joe;
+
+-- Rename the text search configuration.
+mogdb=# ALTER TEXT SEARCH CONFIGURATION joe.ngram2 RENAME TO ngram_2;
+
+-- Delete the type mapping.
+mogdb=# ALTER TEXT SEARCH CONFIGURATION joe.ngram_2 DROP MAPPING IF EXISTS FOR multisymbol;
+
+-- Delete the text search configuration.
+mogdb=# DROP TEXT SEARCH CONFIGURATION joe.ngram_2;
+mogdb=# DROP TEXT SEARCH CONFIGURATION ngram3;
+
+-- Delete the schema and user joe.
+mogdb=# DROP SCHEMA IF EXISTS joe CASCADE;
+mogdb=# DROP ROLE IF EXISTS joe;
+```
+
+## Helpful Links
+
+[ALTER TEXT SEARCH CONFIGURATION](25-ALTER-TEXT-SEARCH-CONFIGURATION)，  [DROP TEXT SEARCH CONFIGURATION](97-DROP-TEXT-SEARCH-CONFIGURATION)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/65-CREATE-TEXT-SEARCH-DICTIONARY.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/65-CREATE-TEXT-SEARCH-DICTIONARY.md
new file mode 100644
index 0000000000000000000000000000000000000000..2686e4f0d2692af7d26d5f85615aeea183928a3c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/65-CREATE-TEXT-SEARCH-DICTIONARY.md
@@ -0,0 +1,152 @@
+---
+title: CREATE TEXT SEARCH DICTIONARY
+summary: CREATE TEXT SEARCH DICTIONARY
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE TEXT SEARCH DICTIONARY
+
+## Function
+
+**CREATE TEXT SEARCH DICTIONARY** creates a full-text retrieval dictionary. A dictionary is used to identify and process particular words during full-text retrieval.
+
+Dictionaries are created by using predefined templates (defined in the **PG_TS_TEMPLATE** system catalog). Five types of dictionaries can be created, **Simple**, **Ispell**, **Synonym**, **Thesaurus**, and **Snowball**. These dictionaries are used to handle different types of tasks.
+
+## Precautions
+
+- A user with the **SYSADMIN** permission can create a dictionary. Then, the user automatically becomes the owner of the dictionary.
+- A dictionary cannot be created in **pg_temp** mode.
+- After a dictionary is created or modified, any modification to the customized dictionary definition file will not affect the dictionary in the database. To make such modifications take effect in the dictionary in the database, run the **ALTER** statement to update the definition file of the dictionary.
+
+## Syntax
+
+```ebnf+diagram
+CreateTextSearchDictionary ::= CREATE TEXT SEARCH DICTIONARY name (
+    TEMPLATE = template
+    [, option = value [, ... ]]
+);
+```
+
+## Parameter Description
+
+- **name**
+
+  Specifies the name of a dictionary to be created. (If you do not specify a schema name, the dictionary will be created in the current schema.)
+
+  Value range: a string, which complies with the identifier naming convention. A value can contain a maximum of 63 characters.
+
+- **template**
+
+  Specifies a template name.
+
+  Value range: templates (**Simple**, **Synonym**, **Thesaurus**, **Ispell**, and **Snowball**) defined in the **PG_TS_TEMPLATE** system catalog
+
+- **option**
+
+  Specifies a parameter name. Each type of dictionaries has a template containing their custom parameters. Parameters function in a way irrelevant to their setting sequence.
+
+  - Parameters for a **Simple** dictionary
+
+    - **STOPWORDS**
+
+        Specifies the name of a file listing stop words. The default file name extension is .stop. In the file, each line defines a stop word. Dictionaries will ignore blank lines and spaces in the file and convert stop-word phrases into lowercase.
+
+    - **ACCEPT**
+
+        Specifies whether to accept a non-stop word as recognized. Default value: **true**
+
+        If **ACCEPT=true** is set for a **Simple** dictionary, no token will be passed to subsequent dictionaries. In this case, you are advised to place the **Simple** dictionary at the end of the dictionary list. If **ACCEPT=false** is set, you are advised to place the **Simple** dictionary before at least one dictionary in the list.
+
+    - **FILEPATH**
+
+        Specifies the directory for storing dictionary files. The directory can be a local directory or an OBS directory. (The OBS directory can be specified only in security mode. You can add the securitymode option during startup to enter the security mode.) The local directory format is  **file://**_absolute_path_. The OBS directory format is  **obs://**_bucket_name_**/path accesskey=ak secretkey=sk region=rg**. The default value is the directory where predefined dictionary files are located. If any of the  **FILEPATH**  and  **STOPWORDS**  parameters is specified, the other one must also be specified.
+
+  - Parameters for a **Synonym** dictionary
+
+    - **SYNONYM**
+
+        Specifies the name of the definition file for a **Synonym** dictionary. The default file name extension is .syn.
+
+        The file is a list of synonyms. Each line is in the format of *token synonym*, that is, token and its synonym separated by a space.
+
+    - **CASESENSITIVE**
+
+        Specifies whether tokens and their synonyms are case sensitive. The default value is **false**, indicating that tokens and synonyms in dictionary files will be converted into lowercase. If this parameter is set to **true**, they will not be converted into lowercase.
+
+    - **FILEPATH**
+
+        Specifies the directory for storing  **Synonym**  dictionary files. The directory can be a local directory or an OBS directory. (The OBS directory can be specified only in security mode. You can add the  **securitymode**  option during startup to enter the security mode.) The local directory format is  **file://**_absolute_path_. The OBS directory format is  **obs://**_bucket_name_**/path accesskey=ak secretkey=sk region=rg**. The default value is the directory where predefined dictionary files are located.
+
+  - Parameters for a **Thesaurus** dictionary
+
+    - **DICTFILE**
+
+        Specifies the name of a dictionary definition file. The default file name extension is .ths.
+
+        The file is a list of synonyms. Each line is in the format of *sample words***:** *indexed words*. The colon (:) is used as a separator between a phrase and its substitute word. If multiple sample words are matched, the TZ selects the longest one.
+
+    - **DICTIONARY**
+
+        Specifies the name of a subdictionary used for word normalization. This parameter is mandatory and only one subdictionary name can be specified. The specified subdictionary must exist. It is used to identify and normalize input text before phrase matching.
+
+        If an input word cannot be recognized by the subdictionary, an error will be reported. In this case, remove the word or update the subdictionary to make the word recognizable. In addition, an asterisk (*) can be placed at the beginning of an indexed word to skip the application of a subdictionary on it, but all sample words must be recognizable by the subdictionary.
+
+        If the sample words defined in the dictionary file contain stop words defined in the subdictionary, use question marks (?) to replace them. Assume that **a** and **the** are stop words defined in the subdictionary.
+
+        ```sql
+        ? one ? two : swsw
+        ```
+
+        **a one the two** and **the one a two** will be matched and output as **swsw**.
+
+    - **FILEPATH**
+
+        Specifies the directory for storing dictionary definition files. The directory can be a local directory or an OBS directory. (The OBS directory can be specified only in security mode. You can add the securitymode option during startup to enter the security mode.) The local directory format is  **file://**_absolute_path_. The OBS directory format is  **obs://**_bucket_name_**/path accesskey=ak secretkey=sk region=rg**. The default value is the directory where predefined dictionary files are located.
+
+  - Parameters for an **Ispell** dictionary
+
+    - **DICTFILE**
+
+        Specifies the name of a dictionary definition file. The default file name extension is .dict.
+
+    - **AFFFILE**
+
+        Specifies the name of an affix file. The default file name extension is .affix.
+
+    - **STOPWORDS**
+
+        Specifies the name of a file listing stop words. The default file name extension is .stop. The file content format is the same as that of the file for a **Simple** dictionary.
+
+    - **FILEPATH**
+
+        Specifies the directory for storing dictionary files. The directory can be a local directory or an OBS directory. (The OBS directory can be specified only in security mode. You can add the  **securitymode**  option during startup to enter the security mode.) The local directory format is  **file://**_absolute_path_. The OBS directory format is  **obs://**_bucket_name_**/path accesskey=ak secretkey=sk region=rg**. The default value is the directory where predefined dictionary files are located.
+
+  - Parameters for a **Snowball** dictionary
+
+    - **LANGUAGE**
+
+        Specifies the name of a language whose stemming algorithm will be used. According to spelling rules in the language, the algorithm normalizes the variants of an input word into a basic word or a stem.
+
+    - **STOPWORDS**
+
+        Specifies the name of a file listing stop words. The default file name extension is .stop. The file content format is the same as that of the file for a **Simple** dictionary.
+
+    - **FILEPATH**
+
+        Specifies the directory for storing dictionary definition files. You can specify a local directory or an OBS directory. (The OBS directory can be specified only in security mode. You can enter the security mode by adding the  **securitymode**  option during startup.) The local directory format is  **file://**_absolute_path_. The OBS directory format is  **obs://**_bucket_name_**/path accesskey=ak secretkey=sk region=rg**. The default value is the directory where predefined dictionary files are located. If any of the  **FILEPATH**  and  **STOPWORDS**  parameters is specified, the other one must also be specified.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  > The name of a dictionary definition file can contain only lowercase letters, digits, and underscores (_).
+
+- **value**
+
+  Specifies a parameter value. If the value is not an identifier or a number, enclose it with single quotation marks ("). You can also enclose identifiers and numbers.
+
+## Examples
+
+See examples in [Configuration Examples](7-configuration-examples).
+
+## Helpful Links
+
+[ALTER TEXT SEARCH DICTIONARY](26-ALTER-TEXT-SEARCH-DICTIONARY)，[CREATE TEXT SEARCH DICTIONARY](65-CREATE-TEXT-SEARCH-DICTIONARY)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/66-CREATE-TRIGGER.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/66-CREATE-TRIGGER.md
new file mode 100644
index 0000000000000000000000000000000000000000..3130bf6392870ff7747ef90f43f4efa5d9eeaf47
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/66-CREATE-TRIGGER.md
@@ -0,0 +1,250 @@
+---
+title: CREATE TRIGGER
+summary: CREATE TRIGGER
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE TRIGGER
+
+## Function
+
+**CREATE TRIGGER** creates a trigger. The trigger will be associated with the specified table or view, and will execute the specified function operations are performed.
+
+## Precautions
+
+- Currently, triggers can be created only on ordinary row-store tables, instead of on column-store tables, temporary tables, or unlogged tables.
+- If multiple triggers of the same kind are defined for the same event, they will be fired in alphabetical order by name.
+- Triggers are usually used for data association and synchronization between multiple tables. SQL execution performance is greatly affected. Therefore, you are advised not to use this statement when a large amount of data needs to be synchronized and performance requirements are high.
+
+## Syntax
+
+```ebnf+diagram
+CreateTrigger ::= CREATE [ CONSTRAINT ] TRIGGER trigger_name { BEFORE | AFTER | INSTEAD OF } { event [ OR '...'] }
+    ON table_name
+    [ FROM referenced_table_name ]
+    { NOT DEFERRABLE | [ DEFERRABLE ] { INITIALLY IMMEDIATE | INITIALLY DEFERRED } }
+    [ FOR [ EACH ] { ROW | STATEMENT } ]
+    [ WHEN ( condition ) ]
+    EXECUTE PROCEDURE function_name ( arguments );
+```
+
+Event include:
+
+```ebnf+diagram
+   INSERT
+   UPDATE [ OF column_name [, ... ] ]
+   DELETE
+   TRUNCATE
+```
+
+## Parameter Description
+
+- **CONSTRAINT**
+
+  (Optional) Creates a constraint trigger. That is, the trigger is used as a constraint. This is the same as a regular trigger except that the timing of the trigger firing can be adjusted using **SET CONSTRAINTS**. Constraint triggers must be **AFTER ROW** triggers.
+
+- **trigger_name**
+
+  Specifies the name of the trigger to be created. This must be distinct from the name of any other trigger for the same table. The name cannot be schema-qualified - the trigger inherits the schema of its table. For a constraint trigger, this is also the name to use when modifying the trigger's behavior using **SET CONSTRAINTS**.
+
+  Value range: a string, which complies with the identifier naming convention and contains a maximum of 63 characters.
+
+- **BEFORE**
+
+  Specifies that the function is called before the event.
+
+- **AFTER**
+
+  Specifies that the function is called after the event. A constraint trigger can only be specified as **AFTER**.
+
+- **INSTEAD OF**
+
+  Specifies that the function is called instead of the event.
+
+- **event**
+
+  Specifies the event that will fire the trigger. Values are **INSERT**, **UPDATE**, **DELETE**, and **TRUNCATE**. Multiple events can be specified using **OR**.
+
+  For **UPDATE** events, it is possible to specify a list of columns using this syntax:
+
+  ```sql
+  UPDATE OF column_name1 [, column_name2 ... ]
+  ```
+
+  The trigger will only fire if at least one of the listed columns is mentioned as a target of the  **UPDATE**  statement.  **INSTEAD OF UPDATE**  events do not support lists of columns. If the column specified by  **UPDATE OF**  contains a generated column, the trigger is also fired when the column on which the generated column depends is the target column of the  **UPDATE**  statement.
+
+- **table_name**
+
+  Specifies the name of the table for which the trigger is created.
+
+  Value range: name of an existing table in the database
+
+- **referenced_table_name**
+
+  Specifies the name of another table referenced by the constraint. This option is used for foreign-key constraints. It can only be specified for constraint triggers.
+
+  Value range: name of an existing table in the database
+
+- **DEFERRABLE | NOT DEFERRABLE**
+
+  Specifies the start time of the trigger. It can only be specified for constraint triggers. They determine whether the constraint is deferrable.
+
+  For details, see **CREATE TABLE**.
+
+- **INITIALLY IMMEDIATE** **| INITIALLY DEFERRED**
+
+  If the constraint is deferrable, the two clauses specify the default time to check the constraint. It can only be specified for constraint triggers.
+
+  For details, see **CREATE TABLE**.
+
+- **FOR EACH ROW | FOR EACH STATEMENT**
+
+    Specifies the frequency of firing the trigger.
+
+  - **FOR EACH ROW** indicates that the trigger should be fired once for every row affected by the trigger event.
+  - **FOR EACH STATEMENT** indicates that the trigger should be fired just once per SQL statement.
+
+    If neither is specified, the default is **FOR EACH STATEMENT**. Constraint triggers can only be marked as **FOR EACH ROW**.
+
+- **condition**
+
+  Specifies whether the trigger function will actually be executed. If **WHEN** is specified, the function will be called only when **condition** returns **true**.
+
+  In **FOR EACH ROW** triggers, the **WHEN** condition can refer to columns of the old and/or new row values by writing **OLD.column name** or **NEW.column name** respectively. In addition, **INSERT** triggers cannot refer to **OLD**, and **DELETE** triggers cannot refer to **NEW**.
+
+  **INSTEAD OF** triggers do not support **WHEN** conditions.
+
+  Currently, **WHEN** expressions cannot contain subqueries.
+
+  Note that for constraint triggers, evaluation of the **WHEN** condition is not deferred, but occurs immediately after the row update operation is performed. If the condition does not evaluate to **true**, then the trigger is not queued for deferred execution.
+
+- **function_name**
+
+  Specifies a user-defined function, which must be declared as taking no parameters and returning type trigger. This is executed when a trigger fires.
+
+- **arguments**
+
+  Specifies an optional comma-separated list of parameters to be provided to the function when the trigger is executed. The parameters are literal string constants. Simple names and numeric constants can also be written here, but they will all be converted to strings. Check the description of the implementation language of the trigger function to find out how these parameters can be accessed within the function.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  > The following details trigger types:
+  >
+  > - **INSTEAD OF** triggers must be marked as **FOR EACH ROW** and can be defined only on views.
+  > - **BEFORE** and **AFTER** triggers on a view must be marked as **FOR EACH STATEMENT**.
+  > - **TRUNCATE** triggers must be marked as **FOR EACH STATEMENT**.
+
+  **Table 1** Types of triggers supported on tables and views
+
+  | When       | Event                | Row-Level      | Statement-Level  |
+  | :--------- | :------------------- | :------------- | :--------------- |
+  | BEFORE     | INSERT/UPDATE/DELETE | Tables         | Tables and views |
+  | TRUNCATE   | Not supported.       | Tables         |                  |
+  | AFTER      | INSERT/UPDATE/DELETE | Tables         | Tables and views |
+  | TRUNCATE   | Not supported.       | Tables         |                  |
+  | INSTEAD OF | INSERT/UPDATE/DELETE | Views          | Not supported.   |
+  | TRUNCATE   | Not supported.       | Not supported. |                  |
+
+  **Table 2** Special variables in PL/pgSQL functions
+
+  | Variable        | Description                                                  |
+  | :-------------- | :----------------------------------------------------------- |
+  | NEW             | New tuple for **INSERT** and **UPDATE** operations. This variable is **NULL** for **DELETE** operations. |
+  | OLD             | Old tuple for **UPDATE** and **DELETE** operations. This variable is **NULL** for **INSERT** operations. |
+  | TG_NAME         | Trigger name.                                                |
+  | TG_WHEN         | Trigger timing (**BEFORE**, **AFTER**, or **INSTEAD OF**).   |
+  | TG_LEVEL        | Trigger frequency (**ROW** or **STATEMENT**).                |
+  | TG_OP           | Trigger event (**INSERT**, **UPDATE**, **DELETE**, or **TRUNCATE**). |
+  | TG_RELID        | OID of the table where the trigger resides.                  |
+  | TG_RELNAME      | Name of the table where the trigger resides. (This variable has been replaced by **TG_TABLE_NAME**.) |
+  | TG_TABLE_NAME   | Name of the table where the trigger resides.                 |
+  | TG_TABLE_SCHEMA | Schema of the table where the trigger resides.               |
+  | TG_NARGS        | Number of parameters for the trigger function.               |
+  | TG_ARGV[]       | List of parameters for the trigger function.                 |
+
+## Examples
+
+```sql
+-- Create a source table and a destination table.
+mogdb=# CREATE TABLE test_trigger_src_tbl(id1 INT, id2 INT, id3 INT);
+mogdb=# CREATE TABLE test_trigger_des_tbl(id1 INT, id2 INT, id3 INT);
+
+-- Create a trigger function.
+mogdb=# CREATE OR REPLACE FUNCTION tri_insert_func() RETURNS TRIGGER AS
+           $$
+           DECLARE
+           BEGIN
+                   INSERT INTO test_trigger_des_tbl VALUES(NEW.id1, NEW.id2, NEW.id3);
+                   RETURN NEW;
+           END
+           $$ LANGUAGE PLPGSQL;
+
+mogdb=# CREATE OR REPLACE FUNCTION tri_update_func() RETURNS TRIGGER AS
+           $$
+           DECLARE
+           BEGIN
+                   UPDATE test_trigger_des_tbl SET id3 = NEW.id3 WHERE id1=OLD.id1;
+                   RETURN OLD;
+           END
+           $$ LANGUAGE PLPGSQL;
+
+mogdb=# CREATE OR REPLACE FUNCTION TRI_DELETE_FUNC() RETURNS TRIGGER AS
+           $$
+           DECLARE
+           BEGIN
+                   DELETE FROM test_trigger_des_tbl WHERE id1=OLD.id1;
+                   RETURN OLD;
+           END
+           $$ LANGUAGE PLPGSQL;
+
+-- Create an INSERT trigger.
+mogdb=# CREATE TRIGGER insert_trigger
+           BEFORE INSERT ON test_trigger_src_tbl
+           FOR EACH ROW
+           EXECUTE PROCEDURE tri_insert_func();
+
+-- Create an UPDATE trigger.
+mogdb=# CREATE TRIGGER update_trigger
+           AFTER UPDATE ON test_trigger_src_tbl
+           FOR EACH ROW
+           EXECUTE PROCEDURE tri_update_func();
+
+-- Create a DELETE trigger.
+mogdb=# CREATE TRIGGER delete_trigger
+           BEFORE DELETE ON test_trigger_src_tbl
+           FOR EACH ROW
+           EXECUTE PROCEDURE tri_delete_func();
+
+-- Execute the INSERT event and check the trigger results.
+mogdb=# INSERT INTO test_trigger_src_tbl VALUES(100,200,300);
+mogdb=# SELECT * FROM test_trigger_src_tbl;
+mogdb=# SELECT * FROM test_trigger_des_tbl;  //Check whether the trigger operation takes effect.
+
+-- Execute the UPDATE event and check the trigger results.
+mogdb=# UPDATE test_trigger_src_tbl SET id3=400 WHERE id1=100;
+mogdb=# SELECT * FROM test_trigger_src_tbl;
+mogdb=# SELECT * FROM test_trigger_des_tbl;  //Check whether the trigger operation takes effect.
+
+-- Execute the DELETE event and check the trigger results.
+mogdb=# DELETE FROM test_trigger_src_tbl WHERE id1=100;
+mogdb=# SELECT * FROM test_trigger_src_tbl;
+mogdb=# SELECT * FROM test_trigger_des_tbl;  //Check whether the trigger operation takes effect.
+
+-- Modify a trigger.
+mogdb=# ALTER TRIGGER delete_trigger ON test_trigger_src_tbl RENAME TO delete_trigger_renamed;
+
+-- Disable insert_trigger.
+mogdb=# ALTER TABLE test_trigger_src_tbl DISABLE TRIGGER insert_trigger;
+
+-- Disable all triggers on the current table.
+mogdb=# ALTER TABLE test_trigger_src_tbl DISABLE TRIGGER ALL;
+
+-- Delete triggers.
+mogdb=# DROP TRIGGER insert_trigger ON test_trigger_src_tbl;
+mogdb=# DROP TRIGGER update_trigger ON test_trigger_src_tbl;
+mogdb=# DROP TRIGGER delete_trigger_renamed ON test_trigger_src_tbl;
+```
+
+## Helpful Links
+
+[ALTER TRIGGER](27-ALTER-TRIGGER)，[DROP TRIGGER](99-DROP-TRIGGER)，[ALTER TABLE](22-ALTER-TABLE)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/67-CREATE-TYPE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/67-CREATE-TYPE.md
new file mode 100644
index 0000000000000000000000000000000000000000..1ad85127cc1a1d8cd26b5e0285987fc32380b6de
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/67-CREATE-TYPE.md
@@ -0,0 +1,285 @@
+---
+title: CREATE TYPE
+summary: CREATE TYPE
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE TYPE
+
+## Function
+
+**CREATE TYPE** registers a new data type for use in the current database. The user who defines a type becomes its owner. Types are designed only for row-store tables.
+
+The following data types can be created: composite type, base type, shell type, and enumerated type.
+
+- Composite type
+
+  A composite type is specified by a list of attribute names and data types. If the data type of an attribute is collatable, the attribute's collation rule can also be specified. This is essentially the same as the row type of a table, but using **CREATE TYPE** avoids the need to create an actual table when all that is wanted is to define a type. A stand-alone composite type is useful as the parameter or return type of a function.
+
+  To create a composite type, you must have the **USAGE** permission on all of its attribute types.
+
+- Base type
+
+  You can create a base type (scalar type). Generally, these functions must be written in the underlying language.
+
+- Shell type
+
+  A shell type is simply a placeholder for a type to be defined later; it is created by issuing **CREATE TYPE** with no parameters except for the type name. Shell types are needed as forward references when base types are created.
+
+- Enumerated type
+
+  An enumerated type is a list of one or more quoted labels, each of which must be 1 to 63 bytes long.
+
+## Precautions
+
+If a schema name is given then the type is created in the specified schema. Otherwise, it is created in the current schema. The type name must be distinct from the name of any existing type or domain in the same schema. (Because tables have associated data types, the type name must also be distinct from the name of any existing table in the same schema.)
+
+## Syntax
+
+```ebnf+diagram
+CreateType ::= CREATE TYPE name AS
+    ( [ attribute_name data_type [ COLLATE collation ] [, ... ] ] )
+```
+
+```ebnf+diagram
+CreateType ::= CREATE TYPE name (
+    INPUT = input_function,
+    OUTPUT = output_function
+    [ , RECEIVE = receive_function ]
+    [ , SEND = send_function ]
+    [ , TYPMOD_IN =
+type_modifier_input_function ]
+    [ , TYPMOD_OUT =
+type_modifier_output_function ]
+    [ , ANALYZE = analyze_function ]
+    [ , INTERNALLENGTH = { internallength |
+VARIABLE } ]
+    [ , PASSEDBYVALUE ]
+    [ , ALIGNMENT = alignment ]
+  [ , STORAGE = storage ]
+    [ , LIKE = like_type ]
+    [ , CATEGORY = category ]
+    [ , PREFERRED = preferred ]
+    [ , DEFAULT = default ]
+    [ , ELEMENT = element ]
+    [ , DELIMITER = delimiter ]
+    [ , COLLATABLE = collatable ]
+)
+```
+
+```ebnf+diagram
+CreateType ::= CREATE TYPE name
+```
+
+```ebnf+diagram
+CreateType ::= CREATE TYPE name AS ENUM
+    ( [ 'label' [, '... '] ] )
+```
+
+## Parameter Description
+
+Composite type
+
+- **name**
+
+  Specifies the name (optionally schema-qualified) of the type to be created.
+
+- **attribute_name**
+
+  Specifies the name of an attribute (column) for the composite type.
+
+- **data_type**
+
+  Specifies the name of an existing data type to become a column of the composite type.
+
+- **collation**
+
+  Specifies the name of an existing collation rule to be associated with a column of the composite type. You can run the  **select \* from pg_collation**  command to query collation rules from the  **pg_collation**  system catalog. The default collation rule is the row starting with  **default**  in the query result.
+
+Base type
+
+  When creating a base type, you can place parameters in any order. The **input_function** and **output_function** parameters are mandatory, and other parameters are optional.
+
+- **input_function**
+
+  Specifies the name of a function that converts data from the type's external textual form to its internal form.
+
+  The input function may be declared as taking one parameter of type cstring or taking three parameters of types cstring, oid, and integer.
+
+  - The first parameter is the input text as a C string,
+  - the second parameter is the type's own OID (except for array types, which instead receive their element type's OID),
+  - and the third is the typmod of the destination column, if known (**-1** will be passed if not).
+
+  The input function must return a value of the data type itself. Usually, an input function should be declared **STRICT**; if it is not, it will be called with a **NULL** first parameter when reading a **NULL** input value. The function must still return **NULL** in this case, unless it raises an error. (This case is mainly meant to support domain input functions, which might need to reject **NULL** inputs.)
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  > The input and output functions can be declared to have results or parameters of the new type, when they have to be created before the new type can be created. The type should first be defined as a shell type, which is a placeholder type that has no attributes except a name and an owner. This is done by issuing the **CREATE TYPE** *name* statement, with no additional parameters. Then the I/O functions can be defined referencing the shell type. Finally, **CREATE TYPE** with a full definition replaces the shell entry with a complete, valid type definition, after which the new type can be used normally.
+
+- **output_function**
+
+  Specifies the name of a function that converts data from the type's internal form to its external textual form.
+
+  The output function must be declared as taking one parameter of the new data type. The output function must return type cstring. Output functions are not invoked for **NULL** values.
+
+- **receive_function**
+
+  (Optional) Specifies the name of a function that converts data from the type's external binary form to its internal form.
+
+  If this function is not supplied, the type cannot participate in binary input. The binary representation should be chosen to be cheap to convert to internal form, while being reasonably portable. (For example, the standard integer data types use network byte order as the external binary representation, while the internal representation is in the machine's native byte order.) The receive function should perform adequate checking to ensure that the value is valid.
+
+  The receive function may be declared as taking one parameter of type internal or taking three parameters of types internal, oid, integer.
+
+  - The first parameter is a pointer to a StringInfo buffer holding the received byte string;
+  - the latter two are the same as for the text input function.
+
+  The receive function must return a value of the data type itself. Usually, a receive function should be declared **STRICT**; if it is not, it will be called with a **NULL** first parameter when reading a **NULL** input value. The function must still return **NULL** in this case, unless it raises an error. (This case is mainly meant to support domain receive functions, which might need to reject **NULL** inputs.)
+
+- **send_function**
+
+  (Optional) Specifies the name of a function that converts data from the type's internal form to its external binary form.
+
+  If this function is not supplied, the type cannot participate in binary output. The send function must be declared as taking one parameter of the new data type. The send function must return type bytea. Send functions are not invoked for **NULL** values.
+
+- **type_modifier_input_function**
+
+  (Optional) Specifies the name of a function that converts an array of modifier(s) for the type to an internal form.
+
+- **type_modifier_output_function**
+
+  (Optional) Specifies the name of a function that converts the internal form of the type's modifier(s) to its external textual form.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  > **type_modifier_input_function** and **type_modifier_output_function** are needed if the type supports modifiers, that is optional constraints attached to a type declaration, such as char(5) or numeric(30,2). openGauss allows user-defined types to take one or more simple constants or identifiers as modifiers. However, this information must be capable of being packed into a single non-negative integer value for storage in the system catalogs. The **type_modifier_input_function** is passed the declared modifier(s) in the form of a cstring array. It must check the values for validity (throwing an error if they are wrong), and if they are correct, return a single non-negative integer value that will be stored as the column "typmod". Type modifiers will be rejected if the type does not have a **type_modifier_input_function**. The **type_modifier_output_function** converts the internal integer typmod value back to the correct form for user display. It must return a cstring value that is the exact string to append to the type name; for example numeric's function might return (30,2). It is allowed to omit the **type_modifier_output_function**, in which case the default display format is just the stored typmod integer value enclosed in parentheses.
+
+- **analyze_function**
+
+  (Optional) Specifies the name of a function that performs statistical analysis for the data type.
+
+  By default, **ANALYZE** will attempt to gather statistics using the type's "equals" and "less-than" operators, if there is a default b-tree operator class for the type. For non-scalar types, this behavior is likely to be unsuitable, so it can be overridden by specifying a custom analysis function. The analysis function must be declared to take one parameter of type internal and return a boolean result.
+
+- **internallength**
+
+  (Optional) Specifies the length in bytes of the new type's internal representation. The default assumption is that it is variable-length.
+
+  While the details of the new type's internal representation are only known to the I/O functions and other functions you create to work with the type, there are several attributes of the internal representation that must be declared to openGauss. Foremost of these is  **internallength**. Base data types can be fixed-length, in which case  **internallength**  is a positive integer, or variable length, indicated by setting  **internallength**  to  **VARIABLE**. (Internally, this is represented by setting  **typlen**  to  **-1**.) The internal representation of all variable-length types must start with a 4-byte integer giving the total length of this value of the type.
+
+- **PASSEDBYVALUE**
+
+  (Optional) Indicates that values of this data type are passed by value, rather than by reference. You cannot pass by value types whose internal representation is larger than the size of the Datum type (4 bytes on most machines, 8 bytes on a few).
+
+- **alignment**
+
+  (Optional) Specifies the storage alignment requirement of the data type. If specified, it must be **char**, **int2**, **int4**, or **double**; the default is **int4**.
+
+  The allowed values equate to alignment on 1, 2, 4, or 8 byte boundaries. Note that variable-length types must have an alignment of at least 4, since they necessarily contain an int4 as their first component.
+
+- **storage**
+
+  (Optional) Specifies the storage strategy for the data type.
+
+  If specified, it must be **plain**, **external**, **extended**, or **main**; the default is **plain**.
+
+  - **plain** specifies that data of the type will always be stored in-line and not compressed. (Only **plain** is allowed for fixed-length types.)
+
+  - **extended** specifies that the system will first try to compress a long data value, and will move the value out of the main table row if it is still too long.
+
+  - **external** allows the value to be moved out of the main table, but the system will not try to compress it.
+
+  - **main** allows compression, but discourages moving the value out of the main table. (Data items with this storage strategy might still be moved out of the main table if there is no other way to make a row fit, but they will be kept in the main table preferentially over **extended** and **external** items.)
+
+    All **storage** values other than **plain** imply that the functions of the data type can handle values that have been toasted. The specific other value given merely determines the default **TOAST** storage strategy for columns of a toastable data type; users can pick other strategies for individual columns using **ALTER TABLE SET STORAGE**.
+
+- **like_type**
+
+  (Optional) Specifies the name of an existing data type that the new type will have the same representation as. The values of **internallength**, **passedbyvalue**, **alignment**, and **storage** are copied from that type, unless overridden by explicit specification elsewhere in this **CREATE TYPE** statement.
+
+  Specifying representation in this way is especially useful when the low-level implementation of a new type references an existing type.
+
+- **category**
+
+  (Optional) Specifies the category code (a single ASCII character) for this type. The default is **U** for a user-defined type. You may also choose other ASCII characters to create custom categories.
+
+- **preferred**
+
+  (Optional) Specifies whether a type is preferred within its type category. If it is, the value will be **TRUE**, else **FALSE**. The default is **FALSE**. Be very careful about creating a preferred type within an existing type category, as this could cause surprising changes in behavior.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  > The **category** and **preferred** parameters can be used to help control which implicit cast will be applied in ambiguous situations. Each data type belongs to a category named by a single ASCII character, and each type is either preferred or not within its category. The parser will prefer casting to preferred types (but only from other types within the same category) when this rule is helpful in resolving overloaded functions or operators. For types that have no implicit casts to or from any other types, it is sufficient to leave these settings at the defaults. However, for a group of related types that have implicit casts, it is often helpful to mark them all as belonging to a category and select one or two of the most general types as being preferred within the category. The **category** parameter is especially useful when adding a user-defined type to an existing built-in category, such as the numeric or string types. However, it is also possible to create entirely-user-defined type categories. Select any ASCII character other than an uppercase letter to name such a category.
+
+- **default**
+
+  (Optional) Specifies the default value for the data type. If this is omitted, the default is null.
+
+  A default value can be specified, in case a user wants columns of the data type to default to something other than the null value. Specify the default with the **DEFAULT** keyword. (Such a default can be overridden by an explicit **DEFAULT** clause attached to a particular column.)
+
+- **element**
+
+  (Optional) Specifies the type of array elements when an array type is created. For example, to define an array of 4-byte integers (int4), specify **ELEMENT = int4**.
+
+- **delimiter**
+
+  (Optional) Specifies the delimiter character to be used between values in arrays made of this type.
+
+  **delimiter** can be set to a specific character. The default delimiter is the comma (,). Note that the delimiter is associated with the array element type, not the array type itself.
+
+- **collatable**
+
+  (Optional) Specifies whether this type's operations can use collation information. If they can, the value will be **TRUE**, else **FALSE** (default).
+
+  If  **collatable**  is  **TRUE**, column definitions and expressions of the type may carry collation information through use of the  **COLLATE**  clause. It is up to the implementations of the functions operating on the type to actually make use of the collation information; this does not happen automatically merely by marking the type collatable.
+
+- **lable**
+
+  (Optional) Represents the textual label associated with one value of an enumerated type. It is a string of 1 to 63 characters.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> Whenever a user-defined type is created, openGauss automatically creates an associated array type whose name consists of the element type's name prepended with an underscore (_).
+
+## Examples
+
+```sql
+-- Create a composite type, create a table, insert data, and make a query.
+mogdb=# CREATE TYPE compfoo AS (f1 int, f2 text);
+mogdb=# CREATE TABLE t1_compfoo(a int, b compfoo);
+mogdb=# CREATE TABLE t2_compfoo(a int, b compfoo);
+mogdb=# INSERT INTO t1_compfoo values(1,(1,'demo'));
+mogdb=# INSERT INTO t2_compfoo select * from t1_compfoo;
+mogdb=# SELECT (b).f1 FROM t1_compfoo;
+mogdb=# SELECT * FROM t1_compfoo t1 join t2_compfoo t2 on (t1.b).f1=(t1.b).f1;
+
+-- Rename the data type.
+mogdb=# ALTER TYPE compfoo RENAME TO compfoo1;
+
+-- Change the owner of the user-defined type compfoo1 to usr1.
+mogdb=# CREATE USER usr1 PASSWORD 'xxxxxxxxx';
+mogdb=# ALTER TYPE compfoo1 OWNER TO usr1;
+
+-- Change the schema of the user-defined type compfoo1 to usr1.
+mogdb=# ALTER TYPE compfoo1 SET SCHEMA usr1;
+
+-- Add a new attribute to the data type.
+mogdb=# ALTER TYPE usr1.compfoo1 ADD ATTRIBUTE f3 int;
+
+-- Delete the compfoo1 type.
+mogdb=# DROP TYPE usr1.compfoo1 cascade;
+
+-- Delete related tables and users.
+mogdb=# DROP TABLE t1_compfoo;
+mogdb=# DROP TABLE t2_compfoo;
+mogdb=# DROP SCHEMA usr1;
+mogdb=# DROP USER usr1;
+
+-- Create an enumerated type.
+mogdb=# CREATE TYPE bugstatus AS ENUM ('create', 'modify', 'closed');
+
+-- Add a label.
+mogdb=# ALTER TYPE bugstatus ADD VALUE IF NOT EXISTS 'regress' BEFORE 'closed';
+
+-- Rename a label.
+mogdb=# ALTER TYPE bugstatus RENAME VALUE 'create' TO 'new';
+```
+
+## Helpful Links
+
+[ALTER TYPE](28-ALTER-TYPE)，[DROP TYPE](100-DROP-TYPE)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/68-CREATE-USER.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/68-CREATE-USER.md
new file mode 100644
index 0000000000000000000000000000000000000000..c8d585cf9c71fef1391bc045ba018fe31556851b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/68-CREATE-USER.md
@@ -0,0 +1,120 @@
+---
+title: CREATE USER
+summary: CREATE USER
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE USER
+
+## Function
+
+**CREATE USER** creates a user.
+
+## Precautions
+
+- A user created using the **CREATE USER** statement has the **LOGIN** permission by default.
+- When you run the  **CREATE USER**  command to create a user, the system creates a schema with the same name as the user in the database where the command is executed.
+- The owner of an object created by a system administrator in a schema with the same name as a common user is the common user, not the system administrator.
+
+## Syntax
+
+```ebnf+diagram
+CreateUser ::= CREATE USER user_name [ [ WITH ] option [ ... ] ] [ ENCRYPTED | UNENCRYPTED ] { PASSWORD | IDENTIFIED BY } { 'password' [EXPIRED] | DISABLE };
+```
+
+The **option** clause is used to configure information, including permissions and properties.
+
+```ebnf+diagram
+option ::= {SYSADMIN | NOSYSADMIN}
+ | {MONADMIN | NOMONADMIN}
+    | {OPRADMIN | NOOPRADMIN}
+    | {POLADMIN | NOPOLADMIN}
+    | {AUDITADMIN | NOAUDITADMIN}
+    | {CREATEDB | NOCREATEDB}
+    | {USEFT | NOUSEFT}
+    | {CREATEROLE | NOCREATEROLE}
+    | {INHERIT | NOINHERIT}
+    | {LOGIN | NOLOGIN}
+    | {REPLICATION | NOREPLICATION}
+    | {INDEPENDENT | NOINDEPENDENT}
+    | {VCADMIN | NOVCADMIN}
+    | CONNECTION LIMIT connlimit
+    | VALID BEGIN 'timestamp'
+    | VALID UNTIL 'timestamp'
+    | RESOURCE POOL 'respool'
+    | PERM SPACE 'spacelimit'
+    | TEMP SPACE 'tmpspacelimit'
+    | SPILL SPACE 'spillspacelimit'
+    | IN ROLE role_name [, ...]
+    | IN GROUP role_name [, ...]
+    | ROLE role_name [, ...]
+    | ADMIN role_name [, ...]
+    | USER role_name [, ...]
+    | SYSID uid
+    | DEFAULT TABLESPACE tablespace_name
+    | PROFILE DEFAULT
+    | PROFILE profile_name
+    | PGUSER
+```
+
+## Parameter Description
+
+- **user_name**
+
+  Specifies the name of the user to be created.
+
+  Value range: a string. It must comply with the naming convention. A value can contain a maximum of 63 characters.
+
+- **password**
+
+  Specifies the login password.
+
+  The new password must:
+
+  - Contain at least eight characters. This is the default length.
+  - Differ from the username or the username spelled backward.
+  - Contain at least three of the following character types: uppercase characters, lowercase characters, digits, and special characters (limited to \~!@\#$ %^&\*()-_=+\\|[\{\}];:,<.\>/?).
+  - The password can also be a ciphertext character string that meets the format requirements. This mode is mainly used to import user data. You are not advised to use it directly. If a ciphertext password is directly used, the user must know the plaintext corresponding to the ciphertext password and ensure the complexity of the plaintext password. The database does not verify the complexity of the ciphertext password. The security of the ciphertext password is ensured by the user.
+- Be enclosed by single or double quotation marks.
+
+  Value range: a string
+
+For other parameters, see [CREATE ROLE](54-CREATE-ROLE#parameter-description).
+
+## Examples
+
+```sql
+-- Create user jim whose login password is xxxxxxxxx:
+mogdb=# CREATE USER jim PASSWORD 'xxxxxxxxx';
+
+-- Alternatively, you can run the following statement:
+mogdb=# CREATE USER kim IDENTIFIED BY 'xxxxxxxxx';
+
+-- To create a user with the CREATEDB permission, add the CREATEDB keyword.
+mogdb=# CREATE USER dim CREATEDB PASSWORD 'xxxxxxxxx';
+
+-- Change user jim's login password from xxxxxxxxx to Abcd@123:
+mogdb=# ALTER USER jim IDENTIFIED BY 'Abcd@123' REPLACE 'xxxxxxxxx';
+
+-- Add the CREATEROLE permission to jim.
+mogdb=# ALTER USER jim CREATEROLE;
+
+-- Set enable_seqscan to on. (The setting will take effect in the next session.)
+mogdb=# ALTER USER jim SET enable_seqscan TO on;
+
+-- Reset the enable_seqscan parameter for jim.
+mogdb=# ALTER USER jim RESET enable_seqscan;
+
+-- Lock jim.
+mogdb=# ALTER USER jim ACCOUNT LOCK;
+
+-- Delete users.
+mogdb=# DROP USER kim CASCADE;
+mogdb=# DROP USER jim CASCADE;
+mogdb=# DROP USER dim CASCADE;
+```
+
+## Helpful Links
+
+[ALTER USER](68-CREATE-USER)，[CREATE ROLE](54-CREATE-ROLE)，[DROP USER](101-DROP-USER)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/69-CREATE-USER-MAPPING.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/69-CREATE-USER-MAPPING.md
new file mode 100644
index 0000000000000000000000000000000000000000..dba60375beb73cd5f03fd0a9d67065a3ad67ac2f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/69-CREATE-USER-MAPPING.md
@@ -0,0 +1,87 @@
+---
+title: CREATE USER MAPPING
+summary: CREATE USER MAPPING
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE USER MAPPING
+
+## Function
+
+**CREATE USER MAPPING** defines a new mapping from a user to a foreign server.
+
+## Precautions
+
+If the  **password**  option is displayed, ensure that the  **usermapping.key.cipher**  and  **usermapping.key.rand**  files exist in the  `$GAUSSHOME/bin`  directory of each node in MogDB. If the two files do not exist, use the  `gs_guc`  tool to generate them and use the  `gs_ssh`  tool to release them to the  `$GAUSSHOME/bin`  directory on each node in MogDB.
+
+## Syntax
+
+```ebnf+diagram
+CreateUserMapping ::= CREATE USER MAPPING FOR { user_name | USER | CURRENT_USER | PUBLIC }
+    SERVER server_name
+    [ OPTIONS ( option 'value' [ ,' ... '] ) ];
+```
+
+## Parameter Description
+
+- **user_name**
+
+  Specifies the name of an existing user to map to a foreign server.
+
+  CURRENT_USER and USER match the name of the current user. When PUBLIC is specified, a public mapping is created and used when no mapping for a particular user is available.
+
+- **server_name**
+
+  Specifies the name of the existing server for which a user mapping will be created.
+
+- **OPTIONS ( { option_name ' value ' } [, …] )**
+
+  Specifies options for user mapping. These options typically define the actual user name and password for this mapping. The option name must be unique. The allowed option names and values are related to the foreign data wrapper of the server.
+
+  >**NOTE:**
+  >
+  >- User passwords are encrypted and stored in the system catalog  [PG_USER_MAPPING](PG_USER_MAPPING). During the encryption,  **usermapping.key.cipher**  and  **usermapping.key.rand**  are used as the encryption password file and encryption factor. Before using the tool for the first time, run the following command to create the two files, save the files to the  _$GAUSSHOME_**/bin**  directory on each node, and ensure that you have the read permission on the files.  **gs_ssh**  helps you quickly place files in the specified directory of each node.
+  >
+  >   ```bash
+  >   gs_ssh -c "gs_guc generate -o usermapping -S default -D $GAUSSHOME/bin"
+  >   ```
+  >
+  >- If the  **-S**  parameter is set to default, a password is randomly generated. You can also specify a password for the  **-S**  parameter to ensure the security and uniqueness of the generated password file. You do not need to save or memorize the password. For details about other parameters, see the description of the  **gs_guc**  tool in the "Tool Reference".
+
+  - Options supported by oracle_fdw are as follows:
+
+    - user
+
+        Oracle server user name.
+
+    - password
+
+        Password of the Oracle user.
+
+  - Options supported by mysql_fdw are as follows:
+
+    - username
+
+        User name of the MySQL server or MariaDB.
+
+    - password
+
+        User password of the MySQL server or MariaDB.
+
+  - Options supported by postgres_fdw are as follows:
+
+    - user
+
+        User name of the remote MogDB database.
+
+    - password
+
+        User password of the remote MogDB database.
+
+        >**NOTE:**
+        >The password entered by the user is encrypted in the MogDB background to ensure security. The key file required for encryption must be generated using the  **gs_guc**  tool and released to the  _$GAUSSHOME_**/bin**  directory of each node in MogDB using the  **gs_ssh**  tool. The password cannot contain the prefix 'encryptOpt'. Otherwise, it is considered as encrypted ciphertext.
+
+## Helpful Links
+
+[ALTER USER MAPPING](30-ALTER-USER-MAPPING)，[DROP USER MAPPING](102-DROP-USER-MAPPING)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/7-ALTER-FUNCTION.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/7-ALTER-FUNCTION.md
new file mode 100644
index 0000000000000000000000000000000000000000..dbe201e80ae554aaa16a77c8c7109ecaba48aa91
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/7-ALTER-FUNCTION.md
@@ -0,0 +1,197 @@
+---
+title: ALTER FUNCTION
+summary: ALTER FUNCTION
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER FUNCTION
+
+## Function
+
+**ALTER FUNCTION** modifies the attributes of a customized function.
+
+## Precautions
+
+Only the function owner or a user granted with the ALTER permission can run the **ALTER FUNCTION** command. The system administrator has this permission by default. The following is permission constraints depending on attributes to be modified:
+
+- If a function involves operations on temporary tables, **ALTER FUNCTION** cannot be used.
+- To modify the owner or schema of a function, you must be a function owner or system administrator and a member of the new owner role.
+
+- Only the system administrator and initial user can change the schema of a function to  **public**.
+
+## Syntax
+
+- Modify the additional parameters of the customized function.
+
+  ```ebnf+diagram
+  AlterFunction ::= ALTER FUNCTION function_name ( [ { [ argmode ] [ argname ] argtype} [, ...] ] )
+      action [ ... ] [ RESTRICT ];
+  ```
+
+  The syntax of the **action** clause is as follows:
+
+  ```ebnf+diagram
+  action ::= {CALLED ON NULL INPUT | RETURNS NULL ON NULL INPUT | STRICT}
+   | {IMMUTABLE | STABLE | VOLATILE}
+   | {SHIPPABLE | NOT SHIPPABLE}
+   | {NOT FENCED | FENCED}
+   | [ NOT ] LEAKPROOF
+   | { [ EXTERNAL ] SECURITY INVOKER | [ EXTERNAL ] SECURITY DEFINER }
+   | AUTHID { DEFINER | CURRENT_USER }
+   | COST execution_cost
+   | ROWS result_rows
+   | SET configuration_parameter { { TO | = } { value | DEFAULT }| FROM CURRENT}
+   | RESET {configuration_parameter | ALL}
+  ```
+
+- Rename the customized function.
+
+  ```ebnf+diagram
+  AlterFunction ::= ALTER FUNCTION funname ( [ { [ argmode ] [ argname ] argtype} [, ...] ] )
+      RENAME TO new_name;
+  ```
+
+- Change the owner of the customized function.
+
+  ```ebnf+diagram
+  AlterFunction ::= ALTER FUNCTION funname ( [ { [ argmode ] [ argname ] argtype} [, ...] ] )
+      OWNER TO new_owner;
+  ```
+
+- Modify the schema of the customized function.
+
+  ```ebnf+diagram
+  AlterFunction ::= ALTER FUNCTION funname ( [ { [ argmode ] [ argname ] argtype} [, ...] ] )
+      SET SCHEMA new_schema;
+  ```
+
+## Parameter Description
+
+- **function_name**
+
+  Specifies the name of the function to be modified.
+
+  Value range: an existing function name
+
+- **argmode**
+
+  Specifies whether a parameter is an input or output parameter.
+
+  Value range: **IN**, **OUT**, **INOUT**, and **VARIADIC**
+
+- **argname**
+
+  Parameter name.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **argtype**
+
+  Specifies the data type of a function parameter.
+
+- **CALLED ON NULL INPUT**
+
+  Declares that some parameters of the function can be invoked in normal mode if the parameter values are null. Omitting this parameter is the same as specifying it.
+
+- **RETURNS NULL ON NULL INPUT**
+
+  **STRICT**
+
+  Specifies that the function always returns null whenever any of its parameters is null. If **STRICT** is specified, the function will not be executed when there are null parameters; instead a null result is assumed automatically.
+
+  **RETURNS NULL ON NULL INPUT** and **STRICT** have the same functions.
+
+- **IMMUTABLE**
+
+  Specifies that the function always returns the same result if the parameter values are the same.
+
+- **STABLE**
+
+  Specifies that the function cannot modify the database, and that within a single table scan it will consistently return the same result for the same parameter value, but its result varies by SQL statements.
+
+- **VOLATILE**
+
+  Specifies that the function value can change in a single table scan and no optimization is performed.
+
+- **LEAKPROOF**
+
+  Specifies that the function has no side effect and the parameter contains only the return value. **LEAKPROOF** can be set only by the system administrator.
+
+- **EXTERNAL**
+
+  (Optional) The purpose is to be compatible with SQL. This feature applies to all functions, not only external functions.
+
+- **SECURITY INVOKER**
+
+  **AUTHID CURRENT_USER**
+
+  Specifies that the function will be executed with the permissions of the user who invokes it. Omitting this parameter is the same as specifying it.
+
+  **SECURITY INVOKER** and **AUTHID CURRENT_USER** have the same functions.
+
+- **SECURITY DEFINER**
+
+  **AUTHID DEFINER**
+
+  Specifies that the function will be executed with the permissions of the user who created it.
+
+  **AUTHID DEFINER** and **SECURITY DEFINER** have the same function.
+
+- **COST execution_cost**
+
+  Estimates the execution cost of a function.
+
+  The unit of **execution_cost** is **cpu_operator_cost**.
+
+  Value range: a positive integer
+
+- **ROWS result_rows**
+
+  Estimates the number of rows returned by the function. This is only allowed when the function is declared to return a set.
+
+  Value range: a positive number. The default value is **1000**.
+
+- **configuration_parameter**
+
+  - **value**
+
+    Sets a specified database session parameter to a specified value. If the value is **DEFAULT** or **RESET**, the default setting is used in the new session. **OFF** closes the setting.
+
+    Value range: a string
+
+    - DEFAULT
+    - OFF
+    - RESET
+
+    Specifies the default value.
+
+  - **from current**
+
+    Uses the value of **configuration_parameter** of the current session.
+
+- **new_name**
+
+  Specifies the new name of a function. To change the schema of a function, you must have the **CREATE** permission on the new schema.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **new_owner**
+
+  Specifies the new owner of a function. To change the owner of a function, the new owner must have the **CREATE** permission on the schema to which the function belongs.
+
+  Value range: an existing user role
+
+- **new_schema**
+
+  Specifies the new schema of a function.
+
+  Value range: an existing schema
+
+## Examples
+
+See **Examples** in [CREATE FUNCTION](48-CREATE-FUNCTION).
+
+## Helpful Links
+
+[CREATE FUNCTION](48-CREATE-FUNCTION)，[DROP FUNCTION](82-DROP-FUNCTION)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/70-CREATE-VIEW.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/70-CREATE-VIEW.md
new file mode 100644
index 0000000000000000000000000000000000000000..0a5de8f6de264096dcd2b8abd2c13ca9e9ed7df2
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/70-CREATE-VIEW.md
@@ -0,0 +1,81 @@
+---
+title: CREATE VIEW
+summary: CREATE VIEW
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE VIEW
+
+## Function
+
+**CREATE VIEW** creates a view. A view is a virtual table, not a base table. Only view definition is stored in the database and view data is not. The data is stored in a base table. If data in the base table changes, the data in the view changes accordingly. In this sense, a view is like a window through which users can know their interested data and data changes in the database.
+
+## Precautions
+
+None
+
+## Syntax
+
+```ebnf+diagram
+CreateView ::= CREATE [ OR REPLACE ] [ TEMP | TEMPORARY ] VIEW view_name [ ( column_name [, ...] ) ]
+    [ WITH ( {view_option_name [= view_option_value]} [, ... ] ) ]
+    AS query;
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - You can use **WITH (security_barriers)** to create a relatively secure view. This prevents attackers from printing hidden base table data by using the **RAISE** statement of low-cost functions.
+> - In MogDB old version, when a view is created by executing `create or replace` statement, if there are views with the same name, you cannot modify or delete column information when replacing it. You can only add columns. Since version 2.1, MogDB supports REPLACE VIEW syntax to update or delete column information. 
+
+## Parameter Description
+
+- **OR REPLACE** <a id = 'replace'> </a>
+
+  Redefines the view if it already exists. Supports operations to delete columns and change column names, only valid for non-materialized views.
+
+- **TEMP | TEMPORARY**
+
+  Creates a temporary view.
+
+- **view_name**
+
+  Specifies the name (optionally schema-qualified) of the view to be created.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **column_name**
+
+  Specifies an optional list of names to be used for columns of the view. If not given, the column names are deduced from the query.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **view_option_name [= view_option_value]**
+
+  Specifies an optional parameter for a view.
+
+  Currently, **view_option_name** supports only the **security_barrier** parameter. This parameter is used when the view attempts to provide row-level security.
+
+  Value range: Boolean type, **TRUE**, and **FALSE**.
+
+- **query**
+
+  Specifies a **SELECT** or **VALUES** statement that will provide the columns and rows of the view.
+
+## Examples
+
+```sql
+-- Create a view consisting of columns whose spcname is pg_default.
+mogdb=# CREATE VIEW myView AS
+    SELECT * FROM pg_tablespace WHERE spcname = 'pg_default';
+
+-- Query the view.
+mogdb=# SELECT * FROM myView ;
+
+-- Delete the view.
+mogdb=# DROP VIEW myView;
+```
+
+## Helpful Links
+
+[ALTER VIEW](31-ALTER-VIEW) and [DROP VIEW](103-DROP-VIEW)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/70.1-CREATE-WEAK-PASSWORD-DICTIONARY.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/70.1-CREATE-WEAK-PASSWORD-DICTIONARY.md
new file mode 100644
index 0000000000000000000000000000000000000000..b63b34f4ed2d492c5812679e8f6b3182384bb71d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/70.1-CREATE-WEAK-PASSWORD-DICTIONARY.md
@@ -0,0 +1,54 @@
+---
+title: CREATE WEAK PASSWORD DICTIONARY
+summary: CREATE WEAK PASSWORD DICTIONARY
+author: Zhang Cuiping
+date: 2021-11-01
+---
+
+# CREATE WEAK PASSWORD DICTIONARY
+
+## Function
+
+**CREATE WEAK PASSWORD DICTIONARY** inserts one or more weak passwords into the **gs_global_config** table.
+
+## Precautions
+
+- Only the initial user, system administrator, and security administrator have the permission to execute this syntax.
+- Passwords in the weak password dictionary are stored in the **gs_global_config** system catalog.
+- The weak password dictionary is empty by default. You can use this syntax to add one or more weak passwords.
+- When a user attempts to execute this syntax to insert a weak password that already exists in the **gs_global_config** table, only one weak password is retained in the table.
+
+## Syntax
+
+```ebnf+diagram
+CreateWeakPasswordDictionary ::= CREATE WEAK PASSWORD DICTIONARY
+       [WITH VALUES] ( {'weak_password'} [, ...] );
+```
+
+## Parameter Description
+
+weak_password
+
+Specifies a weak password.
+
+Value range: a character string
+
+## Examples
+
+```sql
+-- Insert a single weak password into the gs_global_config system catalog.
+mogdb=# CREATE WEAK PASSWORD DICTIONARY WITH VALUES ('password1');
+
+-- Insert multiple weak passwords into the gs_global_config system catalog.
+mogdb=# CREATE WEAK PASSWORD DICTIONARY WITH VALUES ('password2'),('password3');
+
+-- Clear all weak passwords in the gs_global_config system catalog.
+mogdb=# DROP WEAK PASSWORD DICTIONARY;
+
+-- View existing weak passwords.
+mogdb=# SELECT * FROM gs_global_config WHERE NAME LIKE 'weak_password';
+```
+
+## Helpful Links
+
+[DROP WEAK PASSWORD DICTIONARY](103.1-DROP-WEAK-PASSWORD-DICTIONARY)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/71-CURSOR.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/71-CURSOR.md
new file mode 100644
index 0000000000000000000000000000000000000000..416aec9eddf0a2fc8946e8e5d891aa01b3a5d2a2
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/71-CURSOR.md
@@ -0,0 +1,70 @@
+---
+title: CURSOR
+summary: CURSOR
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CURSOR
+
+## Function
+
+**CURSOR** defines a cursor to retrieve a small number of rows at a time out of a larger query.
+
+To process SQL statements, the stored procedure process assigns a memory segment to store context association. Cursors are handles or pointers pointing to context regions. With cursors, stored procedures can control alterations in context regions.
+
+## Precautions
+
+- **CURSOR** is used only in transaction blocks.
+- Generally, **CURSOR** and **SELECT** both have text returns. Since data is stored in binary format in the system, the system needs to convert the data from the binary format to the text format. If data is returned in text format, client applications need to convert the data back to the binary format for processing. **FETCH** implements conversion between binary data and text data.
+- Binary cursors should be used carefully. Text usually occupies larger space than binary data. A binary cursor returns internal binary data, which is easier to operate. A text cursor returns text, which is easier to retrieve and therefore reduces workload on the client. As an example, if a query returns a value of one from an integer column, you would get a string of 1 with a default cursor, whereas with a binary cursor you would get a 4-byte field containing the internal representation of the value (in big-endian byte order).
+
+## Syntax
+
+```ebnf+diagram
+Cursor ::= CURSOR cursor_name
+    [ BINARY ]  [ NO SCROLL ]  [ { WITH | WITHOUT } HOLD ]
+    FOR query ;
+```
+
+## Parameter Description
+
+- **cursor_name**
+
+  Specifies the name of the cursor to be created.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **BINARY**
+
+  Causes the cursor to return data in binary rather than in text format.
+
+- **NO SCROLL**
+
+  Specifies how the cursor retrieves rows.
+
+  - **NO SCROLL**: specifies that the cursor cannot be used to retrieve rows in a nonsequential fashion.
+  - Unspecified: Based on the query's execution plan, the system automatically determines whether the cursor can be used to retrieve rows in a nonsequential fashion.
+
+- **WITH HOLD | WITHOUT HOLD**
+
+  Specifies whether the cursor can continue to be used after the transaction that created it successfully commits.
+
+  - **WITH HOLD**: The cursor can continue to be used after the transaction that created it successfully commits.
+  - **WITHOUT HOLD**: The cursor cannot be used outside of the transaction that created it.
+  - If neither **WITH HOLD** nor **WITHOUT HOLD** is specified, the default is **WITHOUT HOLD**.
+  - Cross-node transactions (for example, DDL-contained transactions created in openGauss with multiple DBnode) do not support **WITH HOLD**.
+
+- **query**
+
+  Uses a **SELECT** or **VALUES** clause to specify the rows to be returned by the cursor.
+
+  Value range: **SELECT** or **VALUES** clause
+
+## Examples
+
+See **Examples** in **FETCH**.
+
+## Helpful Links
+
+[FETCH](107-FETCH)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/72-DEALLOCATE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/72-DEALLOCATE.md
new file mode 100644
index 0000000000000000000000000000000000000000..a46f73411d59c05dd004dcaacdf87ab60be823ef
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/72-DEALLOCATE.md
@@ -0,0 +1,38 @@
+---
+title: DEALLOCATE
+summary: DEALLOCATE
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# DEALLOCATE
+
+## Function
+
+**DEALLOCATE** deallocates a previously prepared statement. If you do not explicitly deallocate a prepared statement, it is deallocated when the session ends.
+
+The **PREPARE** keyword is always ignored.
+
+## Precautions
+
+None
+
+## Syntax
+
+```ebnf+diagram
+Deallocate ::= DEALLOCATE [ PREPARE ] { name | ALL };
+```
+
+## Parameter Description
+
+- **name**
+
+  Specifies the name of the prepared statement to be deallocated.
+
+- **ALL**
+
+  Deallocates all prepared statements.
+
+## Examples
+
+None
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/73-DECLARE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/73-DECLARE.md
new file mode 100644
index 0000000000000000000000000000000000000000..0f514623f7bd72c847414d58e5a77d135eb6b38c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/73-DECLARE.md
@@ -0,0 +1,94 @@
+---
+title: DECLARE
+summary: DECLARE
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# DECLARE
+
+## Function
+
+**DECLARE** defines a cursor to retrieve a small number of rows at a time out of a larger query and can be the start of an anonymous block.
+
+This section describes usage of cursors. The usage of anonymous blocks is available in **BEGIN**.
+
+To process SQL statements, the stored procedure process assigns a memory segment to store context association. Cursors are handles or pointers pointing to context regions. With cursors, stored procedures can control alterations in context regions.
+
+Generally, **CURSOR** and **SELECT** both have text returns. Since data is stored in binary format in the system, the system needs to convert the data from the binary format to the text format. If data is returned in text format, client applications need to convert the data back to the binary format for processing. **FETCH** implements conversion between binary data and text data.
+
+## Precautions
+
+- **CURSOR** is used only in transaction blocks.
+- Binary cursors should be used carefully. Text usually occupies larger space than binary data. A binary cursor returns internal binary data, which is easier to operate. A text cursor returns text, which is easier to retrieve and therefore reduces workload on the client. As an example, if a query returns a value of one from an integer column, you would get a string of 1 with a default cursor, whereas with a binary cursor you would get a 4-byte field containing the internal representation of the value (in big-endian byte order).
+
+## Syntax
+
+- Define a cursor.
+
+  ```ebnf+diagram
+  Declare ::= DECLARE cursor_name [ BINARY ] [ NO SCROLL ]
+      CURSOR [ { WITH | WITHOUT } HOLD ] FOR query ;
+  ```
+
+- Enable an anonymous block.
+
+  ```ebnf+diagram
+  Declare ::= [DECLARE [declare_statements]]
+  BEGIN
+  execution_statements
+  END;
+  ```
+
+## Parameter Description
+
+- **cursor_name**
+
+  Specifies the name of the cursor to be created.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **BINARY**
+
+  Causes the cursor to return data in binary rather than in text format.
+
+- **NO SCROLL**
+
+  Specifies how the cursor retrieves rows.
+
+  - **NO SCROLL**: specifies that the cursor cannot be used to retrieve rows in a nonsequential fashion.
+  - Unspecified: Based on the query's execution plan, the system automatically determines whether the cursor can be used to retrieve rows in a nonsequential fashion.
+
+- **WITH HOLD**
+
+  **WITHOUT HOLD**
+
+  Specifies whether the cursor can continue to be used after the transaction that created it successfully commits.
+
+  - **WITH HOLD**: The cursor can continue to be used after the transaction that created it successfully commits.
+  - **WITHOUT HOLD**: The cursor cannot be used outside of the transaction that created it.
+  - If neither **WITH HOLD** nor **WITHOUT HOLD** is specified, the default is **WITHOUT HOLD**.
+
+- **query**
+
+  Uses a **SELECT** or **VALUES** clause to specify the rows to be returned by the cursor.
+
+  Value range: **SELECT** or **VALUES** clause
+
+- **declare_statements**
+
+  Declares a variable, including its name and type, for example, **sales_cnt int**.
+
+- **execution_statements**
+
+  Specifies the statement to be executed in an anonymous block.
+
+  Value range: an existing function name
+
+## Examples
+
+For details about how to define a cursor, see **Examples** in **FETCH**.
+
+## Helpful Links
+
+[BEGIN](33-BEGIN) and [FETCH](107-FETCH)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/74-DELETE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/74-DELETE.md
new file mode 100644
index 0000000000000000000000000000000000000000..14b6e177965eb05eda574695ee545557e8e33117
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/74-DELETE.md
@@ -0,0 +1,110 @@
+---
+title: DELETE
+summary: DELETE
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# DELETE
+
+## Function
+
+**DELETE** deletes rows that satisfy the **WHERE** clause from the specified table. If the **WHERE** clause is absent, the effect is to delete all rows in the table. The result is a valid, but an empty table.
+
+## Precautions
+
+- You must have the **DELETE** permission on the table to delete from it, as well as the **SELECT** permission for any table in the **USING** clause or whose values are read in the **condition**.
+- For column-store tables, the **RETURNING** clause is currently not supported.
+
+## Syntax
+
+```ebnf+diagram
+Delete ::= [ WITH [ RECURSIVE ] with_query [, ...] ]
+DELETE [/*+ plan_hint */] [ FROM ] [ ONLY ] table_name [ * ] [ [ AS ] alias ]
+    [ USING using_list ]
+    [ WHERE condition | WHERE CURRENT OF cursor_name ]
+    [ RETURNING { * | { output_expr [ [ AS ] output_name ] } [, ...] } ];
+```
+
+## Parameter Description
+
+- **WITH [ RECURSIVE ] with_query [, …]**
+
+  Specifies one or more subqueries that can be referenced by name in the main query, which is equivalent to a temporary table.
+
+  If **RECURSIVE** is specified, it allows a **SELECT** subquery to reference itself by name.
+
+  Format of **with_query**:
+
+  ```ebnf+diagram
+  with_query_name ::= with_query_name [ ( column_name [, ...] ) ] AS
+  ( {select | values | insert | update | delete} )
+  ```
+  
+  - **with_query_name** specifies the name of the result set generated by a subquery. Such names can be used to access the subquery result set.
+  - **column_name** specifies the column name displayed in the subquery result set.
+  - Each subquery can be a **SELECT**, **VALUES**, **INSERT**, **UPDATE** or **DELETE** statement.
+  
+- **plan_hint** clause
+
+  Follows the **DELETE** keyword in the **/\*+ \*/** format. It is used to optimize the plan of a **DELETE** statement block. For details, see [Hint-based Tuning](9-hint-based-tuning). In each statement, only the first **/\*+** _plan_hint _***/** comment block takes effect as a hint. Multiple hints can be written.
+
+- **ONLY**
+
+  If **ONLY** is specified before the table name, matching rows are deleted from the named table only. If **ONLY** is not specified, matching rows are also deleted from any tables inheriting from the named table.
+
+- **table_name**
+
+  Specifies the name (optionally schema-qualified) of the target table.
+
+  Value range: an existing table name
+
+- **alias**
+
+  Specifies a substitute name for the target table.
+
+  Value range: a string. It must comply with the naming convention rule.
+
+- **using_list**
+
+  Specifies the **USING** clause.
+
+- **condition**
+
+  Specifies an expression that returns a Boolean value. Only rows for which this expression returns **true** will be deleted.
+
+- **WHERE CURRENT OF cursor_name**
+
+  This parameter is reserved.
+
+- **output_expr**
+
+  Specifies an expression to be computed and returned by the **DELETE** statement after each row is deleted. The expression can use any column names of the table. Write ***** to return all columns.
+
+- **output_name**
+
+  Specifies a name to use for a returned column.
+
+  Value range: a string. It must comply with the naming convention rule.
+
+## Examples
+
+```sql
+-- Create the tpcds.customer_address_bak table.
+mogdb=# CREATE TABLE tpcds.customer_address_bak AS TABLE tpcds.customer_address;
+
+-- Delete employees whose ca_address_sk is smaller than 14888 from the tpcds.customer_address_bak table.
+mogdb=# DELETE FROM tpcds.customer_address_bak WHERE ca_address_sk < 14888;
+
+-- Delete all data from the tpcds.customer_address_bak table.
+mogdb=# DELETE FROM tpcds.customer_address_bak;
+
+Delete the tpcds.customer_address_bak table.
+mogdb=# DROP TABLE tpcds.customer_address_bak;
+```
+
+## Suggestions
+
+- delete
+
+  To delete all records in a table, use the **truncate** syntax.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/75-DO.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/75-DO.md
new file mode 100644
index 0000000000000000000000000000000000000000..3d315b9a12d50db09b3daa1d8d6d456a127ec530
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/75-DO.md
@@ -0,0 +1,56 @@
+---
+title: DO
+summary: DO
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# DO
+
+## Function
+
+**DO** executes an anonymous code block.
+
+The code block is treated as though it were the body of a function with no parameters, returning **void**. It is parsed and executed a single time.
+
+## Precautions
+
+- The procedural language to be used must already have been installed into the current database by means of **CREATE LANGUAGE**. **plpgsql** is installed by default, but other languages are not.
+- The user must have the **USAGE** permission on the procedural language, or must be a system administrator if the language is untrusted.
+
+## Syntax
+
+```ebnf+diagram
+Do ::= DO [ LANGUAGE lang_name ] code;
+```
+
+## Parameter Description
+
+- **lang_name**
+
+  Specifies the name of the procedural language the code is written in. If omitted, the default is **plpgsql**.
+
+- **code**
+
+  Specifies the procedural language code to be executed. This must be specified as a string literal.
+
+## Example
+
+```sql
+-- Create the webuser user.
+mogdb=# CREATE USER webuser PASSWORD 'xxxxxx';
+
+-- Grant all permissions on all views in the tpcds schema to the webuser user.
+mogdb=# DO $$DECLARE r record;
+BEGIN
+    FOR r IN SELECT c.relname table_name,n.nspname table_schema FROM pg_class c,pg_namespace n
+             WHERE c.relnamespace = n.oid AND n.nspname = 'tpcds' AND relkind IN ('r','v')
+    LOOP
+        EXECUTE 'GRANT ALL ON ' || quote_ident(r.table_schema) || '.' || quote_ident(r.table_name) || ' TO webuser';
+    END LOOP;
+END$$;
+
+
+-- Delete the webuser user.
+mogdb=# DROP USER webuser CASCADE;
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/75.1-DROP-AGGREGATE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/75.1-DROP-AGGREGATE.md
new file mode 100644
index 0000000000000000000000000000000000000000..a8539edb078c5a821c407f55577a9316fc25d7e3
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/75.1-DROP-AGGREGATE.md
@@ -0,0 +1,56 @@
+---
+title: DROP AGGREGATE
+summary: DROP AGGREGATE
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# DROP AGGREGATE
+
+## Function
+
+**DROP AGGREGATE** deletes an aggregate function.
+
+## Precautions
+
+**DROP AGGREGATE** deletes an existing aggregate function. Only the owner of the aggregate function can run this command.
+
+## Syntax
+
+```ebnf+diagram
+DropAggregate ::= DROP AGGREGATE [ IF EXISTS ] name ( argtype [ , ... ] ) [ CASCADE | RESTRICT ];
+```
+
+## Parameter Description
+
+- **IF EXISTS**
+
+  Do not throw an error if the specified aggregation does not exist. A notice is issued in this case.
+
+- **name**
+
+  Existing aggregate function name (optionally schema-qualified).
+
+- **argtype**
+
+  Input data type of the aggregate function. To reference a zero-parameter aggregate function, use * to replace the input data type list.
+
+- **CASCADE**
+
+  Cascade deletes objects that depend on the aggregate function.
+
+- **RESTRICT**
+
+  Refuses to delete the aggregate function if any objects depend on it. This is a default processing.
+
+## Examples
+
+Delete the aggregate function **myavg** of the integer type:
+
+```sql
+DROP AGGREGATE myavg(integer);
+```
+
+## Compatibility
+
+The SQL standard does not provide the **DROP AGGREGATE** statement.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/75.2-DROP-AUDIT-POLICY.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/75.2-DROP-AUDIT-POLICY.md
new file mode 100644
index 0000000000000000000000000000000000000000..73b598bffaf54e9d707244d45ba6eea21c8e8182
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/75.2-DROP-AUDIT-POLICY.md
@@ -0,0 +1,89 @@
+---
+title: DROP AUDIT POLICY
+summary: DROP AUDIT POLICY
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# DROP AUDIT POLICY
+
+## Function
+
+**ALTER AUDIT POLICY** modifies the unified audit policy.
+
+## Precautions
+
+- Only user **poladmin**, user **sysadmin**, or the initial user can perform this operation.
+- The unified audit policy takes effect only after **enable_security_policy** is set to **on**. For details, see "Database Configuration &gt; Database Security Management Policies &gt; Unified Auditing" in the *Security Hardening Guide*.
+
+## Syntax
+
+```ebnf+diagram
+DropAuditPolicy ::= ALTER AUDIT POLICY [ IF EXISTS ] policy_name { ADD | REMOVE } { [ privilege_audit_clause ] [ access_audit_clause ] };
+ALTER AUDIT POLICY [ IF EXISTS ] policy_name MODIFY ( filter_group_clause );
+ALTER AUDIT POLICY [ IF EXISTS ] policy_name DROP FILTER;
+ALTER AUDIT POLICY [ IF EXISTS ] policy_name COMMENTS policy_comments;
+ALTER AUDIT POLICY [ IF EXISTS ] policy_name { ENABLE | DISABLE };
+```
+
+- privilege_audit_clause
+
+  ```
+  PRIVILEGES { DDL | ALL }
+  ```
+
+- access_audit_clause
+
+  ```
+  ACCESS { DML | ALL }
+  ```
+
+- filter_group_clause
+
+  ```
+  FILTER ON { ( FILTER_TYPE ( filter_value [, ... ] ) ) [, ... ] }
+  ```
+
+## Parameter Description
+
+- **policy_name**
+
+  Specifies the audit policy name, which must be unique.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **DDL**
+
+  Specifies the operations that are audited within the database: **CREATE**, **ALTER**, **DROP**, **ANALYZE**, **COMMENT**, **GRANT**, **REVOKE**, **SET**, **SHOW**, **LOGIN_ANY**, **LOGIN_FAILURE**, **LOGIN_SUCCESS**, and **LOGOUT**.
+
+- **ALL**
+
+  Indicates all operations supported by the specified DDL statements in the database.
+
+- **DML**
+
+  Specifies the operations that are audited within the database: **SELECT**, **COPY**, **DEALLOCATE**, **DELETE**, **EXECUTE**, **INSERT**, **PREPARE**, **REINDEX**, **TRUNCATE**, and **UPDATE**.
+
+- **FILTER_TYPE**
+
+  Specifies the types of information to be filtered by the audit: **IP**, **ROLES**, and **APP**.
+
+- **filter_value**
+
+  Indicates the detailed information to be filtered.
+
+- **policy_comments**
+
+  Records description information of audit policies.
+
+- **ENABLE|DISABLE**
+
+  Enables or disables the unified audit policy. If **ENABLE|DISABLE** is not specified, **ENABLE** is used by default.
+
+## Examples
+
+See **Examples** in **CREATE AUDIT POLICY**.
+
+## Helpful Links
+
+[ALTER AUDIT POLICY](1.2-ALTER-AUDIT-POLICY) and [CREATE AUDIT POLICY](41.2-CREATE-AUDIT-POLICY)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/75.3-DROP-CAST.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/75.3-DROP-CAST.md
new file mode 100644
index 0000000000000000000000000000000000000000..a1d4c0fb561a1a3c27ffdc497292840446e9d820
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/75.3-DROP-CAST.md
@@ -0,0 +1,56 @@
+---
+title: DROP CAST
+summary: DROP CAST
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# DROP CAST
+
+## Function
+
+DROP CAST deletes a type conversion.
+
+## Precautions
+
+DROP CAST deletes a previously defined type conversion.
+
+To delete a type conversion, you must have a source or destination data type. This is the same permission as creating a type conversion.
+
+## Syntax
+
+```ebnf+diagram
+DropCast ::= DROP CAST [ IF EXISTS ] (source_type AS target_type) [ CASCADE | RESTRICT ]
+```
+
+## Parameter Description
+
+- I**F EXISTS**
+
+  Do not throw an error if the specified conversion does not exist. A notice is issued in this case.
+
+- **source_type**
+
+  Source data type in the type conversion.
+
+- **target_type**
+
+  Type of the target data in the type conversion.
+
+- **CASCADE**
+
+  **RESTRICT**
+
+  These keys have no effect because there is no dependency on type conversion.
+
+## Example
+
+Delete the conversion from text to int.
+
+```sql
+DROP CAST (text AS int);
+```
+
+## Compatibility
+
+DROP CAST complies with the SQL standard.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/76-DROP-CLIENT-MASTER-KEY.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/76-DROP-CLIENT-MASTER-KEY.md
new file mode 100644
index 0000000000000000000000000000000000000000..41f9603c4f09a9fa6647afe7251f53acbb53c6af
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/76-DROP-CLIENT-MASTER-KEY.md
@@ -0,0 +1,50 @@
+---
+title: DROP CLIENT MASTER KEY
+summary: DROP CLIENT MASTER KEY
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# DROP CLIENT MASTER KEY
+
+## Function
+
+**DROP CLIENT MASTER KEY** deletes a client master key (CMK).
+
+## Precautions
+
+- Only the CMK owner or a user who has been granted the DROP permission can run this command. By default, the system administrator has the permission.
+- This command not only deletes the key object in the database, but also deletes the key file corresponding to the key object in the specified path on the client.
+
+## Syntax
+
+```ebnf+diagram
+DropClientMasterKey ::= DROP CLIENT MASTER KEY [ IF EXISTS ] client_master_key_name [CASCADE];
+```
+
+## Parameter Description
+
+- **IF EXISTS**
+
+  If a specified CMK does not exist, a notice rather than an error is issued.
+
+- **client_master_key_name**
+
+  Name of a CMK to be deleted.
+
+  Value range: a string. It is the name of an existing CMK object.
+
+- **CASCADE**
+
+  - **CASCADE**: automatically deletes objects that depend on the CMK.
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** During the life cycle of the syntax, the status of both client and server needs to be changed. When an exception occurs, the key information may have been deleted from the server, but the key file is not deleted from the client. In this case, the client does not check whether there are unexpected key files retain due to exceptions during the lifecycle of the next syntax. You need to periodically check the key folder and confirm and process the key files that are not used.
+
+## **Examples**
+
+```sql
+-- Delete a CMK object.
+mogdb=> DROP CLIENT MASTER KEY ImgCMK CASCADE;
+NOTICE:  drop cascades to column setting: imgcek
+DROP CLIENT MASTER KEY
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/77-DROP-COLUMN-ENCRYPTION-KEY.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/77-DROP-COLUMN-ENCRYPTION-KEY.md
new file mode 100644
index 0000000000000000000000000000000000000000..1f6e604f27b8f42b7164855a1969d92a659a03a9
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/77-DROP-COLUMN-ENCRYPTION-KEY.md
@@ -0,0 +1,43 @@
+---
+title: DROP COLUMN ENCRYPTION KEY
+summary: DROP COLUMN ENCRYPTION KEY
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# DROP COLUMN ENCRYPTION KEY
+
+## Function
+
+**CREATE COLUMN ENCRYPTION KEY** deletes a column encryption key (CEK).
+
+## Precautions
+
+Only the CEK owner or a user who has been granted the DROP permission can run this command. By default, the system administrator has the permission.
+
+## Syntax
+
+```ebnf+diagram
+DropColumnEncryptionKey ::= DROP COLUMN ENCRYPTION KEY [ IF EXISTS ] column_encryption_key_name [CASCADE];
+```
+
+## Parameter Description
+
+- **IF EXISTS**
+
+  If a specified CEK does not exist, a notice rather than an error is issued.
+
+- **column_encryption_key_name**
+
+  Name of a CEK to be deleted.
+
+  Value range: a string. It is the name of an existing CEK.
+
+## Examples
+
+```sql
+-- Delete a CEK.
+mogdb=# DROP COLUMN ENCRYPTION KEY ImgCEK CASCADE;
+ERROR:  cannot drop column setting: imgcek cascadely because encrypted column depend on it.
+HINT:  we have to drop encrypted column: name, ... before drop column setting: imgcek cascadely.
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/78-DROP-DATABASE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/78-DROP-DATABASE.md
new file mode 100644
index 0000000000000000000000000000000000000000..fe822fc7ba9093939fe31df9789c77267adb9e40
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/78-DROP-DATABASE.md
@@ -0,0 +1,54 @@
+---
+title: DROP DATABASE
+summary: DROP DATABASE
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# DROP DATABASE
+
+## Function
+
+**DROP DATABASE** deletes a database.
+
+## Precautions
+
+- Only the database owner or a user granted with the DROP permission can run the **DROP DATABASE** command. The system administrator has this permission by default.
+- The preinstalled POSTGRES, TEMPLATE0, and TEMPLATE1 databases are protected and therefore cannot be deleted. To check databases in the current service, run the gsql statement **\l**.
+- If any users are connected to the database, the database cannot be deleted.
+- **DROP DATABASE** cannot be executed within a transaction block.
+- If **DROP DATABASE** fails and is rolled back, run **DROP DATABASE IF EXISTS** again.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** **DROP DATABASE** cannot be undone.
+
+## Syntax
+
+```ebnf+diagram
+DropDatabase ::= DROP DATABASE [ IF EXISTS ] database_name ;
+```
+
+## Parameter Description
+
+- **IF EXISTS**
+
+  Reports a notice instead of an error if the specified database does not exist.
+
+- **database_name**
+
+  Specifies the name of the database to be deleted.
+
+  Value range: an existing database name
+
+## Examples
+
+See **Examples** in **CREATE DATABASE**.
+
+## Helpful Links
+
+[CREATE DATABASE](44-CREATE-DATABASE)
+
+## Suggestions
+
+- drop database
+
+  Do not delete databases during transactions.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/79-DROP-DATA-SOURCE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/79-DROP-DATA-SOURCE.md
new file mode 100644
index 0000000000000000000000000000000000000000..b54c670078b4c141e84a3d616c7093c6a145afc8
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/79-DROP-DATA-SOURCE.md
@@ -0,0 +1,57 @@
+---
+title: DROP DATA SOURCE
+summary: DROP DATA SOURCE
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# DROP DATA SOURCE
+
+## Function
+
+**DROP DATA SOURCE** deletes a data source.
+
+## Important Notes
+
+Only an owner, system administrator, or initial user can delete a data source.
+
+## Syntax
+
+```ebnf+diagram
+DropDataSource ::= DROP DATA SOURCE [IF EXISTS] src_name [CASCADE | RESTRICT];
+```
+
+## Parameter Description
+
+- **src_name**
+
+  Specifies the name of the data source to be deleted.
+
+  Value range: a string. It must comply with the naming convention.
+
+- **IF EXISTS**
+
+  Reports a notice instead of an error if the specified data source does not exist.
+
+- **CASCADE | RESTRICT**
+
+  - **CASCADE**: automatically deletes the objects that depend on the data source.
+
+  - **RESTRICT**: refuses to delete the data source if any objects depend on it. This is the default action.
+
+    Currently, no objects depend on data sources. Therefore, **CASCADE** is equivalent to **RESTRICT**, and they are reserved to ensure backward compatibility.
+
+## Examples
+
+```sql
+-- Create a data source.
+mogdb=# CREATE DATA SOURCE ds_tst1;
+
+-- Delete the data source.
+mogdb=# DROP DATA SOURCE ds_tst1 CASCADE;
+mogdb=# DROP DATA SOURCE IF EXISTS ds_tst1 RESTRICT;
+```
+
+## Helpful Links
+
+[CREATE DATA SOURCE](45-CREATE-DATA-SOURCE) and [ALTER DATA SOURCE](3-ALTER-DATA-SOURCE)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/8-ALTER-GROUP.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/8-ALTER-GROUP.md
new file mode 100644
index 0000000000000000000000000000000000000000..cefd9c85f1ad676482a359ffa12af4fd4daea9b1
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/8-ALTER-GROUP.md
@@ -0,0 +1,60 @@
+---
+title: ALTER GROUP
+summary: ALTER GROUP
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER GROUP
+
+## Function
+
+**ALTER GROUP** modifies the attributes of a user group.
+
+## Precautions
+
+**ALTER GROUP** is an alias for **ALTER ROLE**, and it is not a standard SQL syntax and not recommended. Users can use **ALTER ROLE** directly.
+
+## Syntax
+
+- Add users to a group.
+
+  ```sql
+  AlterGroup ::= ALTER GROUP group_name
+      ADD USER user_name [, ... ];
+  ```
+
+- Remove users from a group.
+
+  ```sql
+  AlterGroup ::= ALTER GROUP group_name
+      DROP USER user_name [, ... ];
+  ```
+
+- Change the name of the group.
+
+  ```ebnf+diagram
+  AlterGroup ::= ALTER GROUP group_name
+      RENAME TO new_name;
+  ```
+
+## Parameter Description
+
+See **Parameter Description** in [ALTER ROLE](12-ALTER-ROLE).
+
+## Example
+
+```sql
+-- Add users to a group.
+mogdb=# ALTER GROUP super_users ADD USER lche, jim;
+
+-- Remove users from a group.
+mogdb=# ALTER GROUP super_users DROP USER jim;
+
+-- Change the name of the group.
+mogdb=# ALTER GROUP super_users RENAME TO normal_users;
+```
+
+## Helpful Links
+
+[ALTER GROUP](8-ALTER-GROUP)，[DROP GROUP](83-DROP-GROUP)，[ALTER ROLE](12-ALTER-ROLE)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/80-DROP-DIRECTORY.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/80-DROP-DIRECTORY.md
new file mode 100644
index 0000000000000000000000000000000000000000..9e02a83f22758f75512d18d5947e62df950d6abf
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/80-DROP-DIRECTORY.md
@@ -0,0 +1,44 @@
+---
+title: DROP DIRECTORY
+summary: DROP DIRECTORY
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# DROP DIRECTORY
+
+## Function
+
+**DROP Directory** deletes a synonym.
+
+## Precautions
+
+When enable_access_server_directory=off, only the initial user is allowed to delete the directory object; when enable_access_server_directory=on, the user with SYSADMIN permission, the owner of the directory object, the user who has been granted the DROP permission of the directory, or the user who has inherited the built-in role gs_rloe_directory_drop permission The user can delete the directory.
+
+## Syntax
+
+```ebnf+diagram
+DropDirectory ::= DROP DIRECTORY [ IF EXISTS ] directory_name;
+```
+
+## Parameter Description
+
+- **directory_name**
+
+  Specifies the name of the directory to be deleted.
+
+  Value range: an existing directory name
+
+## Example
+
+```sql
+-- Create a directory.
+mogdb=# CREATE OR REPLACE DIRECTORY  dir  as '/tmp/';
+
+-- Delete a directory.
+mogdb=# DROP DIRECTORY dir;
+```
+
+## Helpful Links
+
+[CREATE DIRECTORY](46-CREATE-DIRECTORY) and [ALTER DIRECTORY](5-ALTER-DIRECTORY)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/80.1-DROP-EXTENSION.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/80.1-DROP-EXTENSION.md
new file mode 100644
index 0000000000000000000000000000000000000000..ba06f4801926e31f4627377b4c9f262dcccba48b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/80.1-DROP-EXTENSION.md
@@ -0,0 +1,51 @@
+---
+title: DROP EXTENSION
+summary: DROP EXTENSION
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# DROP EXTENSION
+
+## Function
+
+**DROP EXTENSION** deletes an extension.
+
+## Precautions
+
+- **DROP EXTENSION** deletes an extension from the database. When you delete an extension, the components that make up the extension are also deleted.
+- The **DROP EXTENSION** command can be used only by the owner of the extension.
+
+## Syntax
+
+```ebnf+diagram
+DropExtension ::= DROP EXTENSION [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]
+```
+
+## Parameter Description
+
+- **IF EXISTS**
+
+  If the **IF EXISTS** parameter is used and the extension does not exist, no error is reported. Instead, a **NOTICE** is generated.
+
+- **name**
+
+  Name of an installed extension.
+
+- **CASCADE**
+
+  Automatically deletes objects that depend on the extension.
+
+- **RESTRICT**
+
+  If any object depends on an extension, the extension cannot be deleted (unless all its member objects and other extension objects are deleted at a time using the **DROP** command). This is the default processing.
+
+## Examples
+
+Delete extension **hstore** from the current database.
+
+```sql
+DROP EXTENSION hstore;
+```
+
+In the current database, if an object that uses **hstore** exists, this command will fail. For example, a column in any table is of the **hstore** type. Adding the **CASCADE** option can forcibly delete the extension and objects that depend on it.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/81-DROP-FOREIGN-TABLE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/81-DROP-FOREIGN-TABLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..5192fd72073f6c3b7b88843d3e8224e6241e41b4
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/81-DROP-FOREIGN-TABLE.md
@@ -0,0 +1,44 @@
+---
+title: DROP FOREIGN TABLE
+summary: DROP FOREIGN TABLE
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# DROP FOREIGN TABLE
+
+## Function
+
+**DROP FOREIGN TABLE** drops a foreign table.
+
+## Precautions
+
+**DROP FOREIGN TABLE** forcibly drops the specified table and the indexes depending on the table. After the table is dropped, the functions and stored procedures that need to use this table cannot be executed.
+
+## Syntax
+
+```ebnf+diagram
+DropForeignTable ::= DROP FOREIGN TABLE [ IF EXISTS ]
+    table_name [, ...] [ CASCADE | RESTRICT ];
+```
+
+## Parameter Description
+
+- **IF EXISTS**
+
+  Reports a notice instead of an error if the specified table does not exist.
+
+- **table_name**
+
+  Table name
+
+  Value range: an existing table name
+
+- **CASCADE | RESTRICT**
+
+  - **CASCADE**: automatically drops the objects (such as views) that depend on the table.
+  - **RESTRICT**: refuses to drop the table if any objects depend on it. This is the default action.
+
+## Helpful Links
+
+[ALTER FOREIGN TABLE](6-ALTER-FOREIGN-TABLE) and [CREATE FOREIGN TABLE](47-CREATE-FOREIGN-TABLE)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/82-DROP-FUNCTION.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/82-DROP-FUNCTION.md
new file mode 100644
index 0000000000000000000000000000000000000000..d0090238a1544cdee9aa3ff954a156eab29c10df
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/82-DROP-FUNCTION.md
@@ -0,0 +1,56 @@
+---
+title: DROP FUNCTION
+summary: DROP FUNCTION
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# DROP FUNCTION
+
+## Function
+
+**DROP FUNCTION** deletes a function.
+
+## Precautions
+
+- If a function involves operations on temporary tables, **DROP FUNCTION** cannot be used.
+- Only the function owner or a user granted with the DROP permission can run the **DROP FUNCTION** command. The system administrator has this permission by default.
+
+## Syntax
+
+```ebnf+diagram
+DropFunction ::= DROP FUNCTION [ IF EXISTS ] function_name
+[ ( [ {[ argmode ] [ argname ] argtype} [, ...] ] ) [ CASCADE | RESTRICT ] ];
+```
+
+## Parameter Description
+
+- **IF EXISTS**
+
+  Reports a notice instead of an error if the specified function does not exist.
+
+- **function_name**
+
+  Specifies the name of the function to be deleted.
+
+  Value range: an existing function name
+
+- **argmode**
+
+  Specifies the parameter mode of the function.
+
+- **argname**
+
+  Specifies the parameter name of the function.
+
+- **argtype**
+
+  Specifies the parameter type of the function.
+
+## Examples
+
+For details, see **Examples**.
+
+## Helpful Links
+
+[ALTER FUNCTION](7-ALTER-FUNCTION) and [CREATE FUNCTION](48-CREATE-FUNCTION)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/83-DROP-GROUP.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/83-DROP-GROUP.md
new file mode 100644
index 0000000000000000000000000000000000000000..2f49c130120c7e1d8d5b6db8dcb25f0b90c85d53
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/83-DROP-GROUP.md
@@ -0,0 +1,32 @@
+---
+title: DROP GROUP
+summary: DROP GROUP
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP GROUP
+
+## Function
+
+**DROP GROUP** deletes a user group.
+
+**DROP GROUP** is an alias for **DROP ROLE**.
+
+## Precautions
+
+**DROP GROUP** is an interface of the MogDB management tool. You are not advised to use this interface, because doing so affects MogDB.
+
+## Syntax
+
+```ebnf+diagram
+DropGroup ::= DROP GROUP [ IF EXISTS ] group_name [, ...];
+```
+
+## Parameter Description
+
+See **Parameter Description** in **DROP ROLE**.
+
+## Helpful Links
+
+[CREATE GROUP](49-CREATE-GROUP), [ALTER GROUP](8-ALTER-GROUP), and [DROP ROLE](89-DROP-ROLE)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/84-DROP-INDEX.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/84-DROP-INDEX.md
new file mode 100644
index 0000000000000000000000000000000000000000..354d9d915292a2ac401bf1251bed93e9ce2865dc
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/84-DROP-INDEX.md
@@ -0,0 +1,56 @@
+---
+title: DROP INDEX
+summary: DROP INDEX
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP INDEX
+
+## Function
+
+**DROP INDEX** deletes an index.
+
+## Precautions
+
+Only the index owner or a user who has the INDEX permission on the table where the index resides can run the **DROP INDEX** command. The system administrator has this permission by default.
+
+## Syntax
+
+```ebnf+diagram
+DropIndex ::= DROP INDEX [ CONCURRENTLY ] [ IF EXISTS ]
+    index_name [, ...] [ CASCADE | RESTRICT ];
+```
+
+## Parameter Description
+
+- **CONCURRENTLY**
+
+  Deletes an index without locking it. A normal **DROP INDEX** acquires exclusive lock on the table on which the index depends, blocking other accesses until the index drop can be completed. With this option, the statement does not lock the table during index deletion.
+
+  This parameter allows only one index name and does not support **CASCADE**.
+
+  The **DROP INDEX** statement can be run within a transaction, but **DROP INDEX CONCURRENTLY** cannot.
+
+- **IF EXISTS**
+
+  Reports a notice instead of an error if the specified index does not exist.
+
+- **index_name**
+
+  Specifies the index name to be deleted.
+
+  Value range: an existing index
+
+- **CASCADE | RESTRICT**
+
+  - **CASCADE**: automatically deletes the objects that depend on the index.
+  - **RESTRICT**: refuses to delete the index if any objects depend on it. This is the default action.
+
+## Examples
+
+See **Examples** in **CREATE INDEX**.
+
+## Helpful Links
+
+[ALTER INDEX](9-ALTER-INDEX) and [CREATE INDEX](50-CREATE-INDEX)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/84.1-DROP-LANGUAGE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/84.1-DROP-LANGUAGE.md
new file mode 100644
index 0000000000000000000000000000000000000000..ec7fd90c2e674974deb39f433ec12928df064675
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/84.1-DROP-LANGUAGE.md
@@ -0,0 +1,48 @@
+---
+title: DROP LANGUAGE
+summary: DROP LANGUAGE
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# DROP LANGUAGE
+
+## Function
+
+DROP LANGUAGE deletes a procedural language.
+
+## Syntax
+
+```ebnf+diagram
+DropLanguage ::= DROP [ PROCEDURAL ] LANGUAGE [ IF EXISTS ] name [ CASCADE | RESTRICT ]
+```
+
+## Parameter Description
+
+- **IF EXISTS**
+
+  Do not throw an error if the specified procedural language does not exist. A notice is issued in this case.
+
+- **name**
+
+  Name of an existing language. For downward compatibility, the name can be enclosed in single quotes.
+
+- **CASCADE**
+
+  Automatically deletes objects that depend on the language (for example, functions written in the language).
+
+- **RESTRICT**
+
+  Refuses to delete the object if any objects depend on it. This is a default parameter.
+
+## Example
+
+Run the following command to delete the plsample language:
+
+```sql
+DROP LANGUAGE plsample;
+```
+
+## Compatibility
+
+The SQL standard does not contain the **DROP LANGUAGE** statement.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/84.2-DROP-MASKING-POLICY.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/84.2-DROP-MASKING-POLICY.md
new file mode 100644
index 0000000000000000000000000000000000000000..40682f4517a73901eb38947d0995643563e32179
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/84.2-DROP-MASKING-POLICY.md
@@ -0,0 +1,44 @@
+---
+title: DROP MASKING POLICY
+summary: DROP MASKING POLICY
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# DROP MASKING POLICY
+
+## Function
+
+**DROP MASKING POLICY** deletes an anonymization policy.
+
+## Precautions
+
+Only user **poladmin**, user **sysadmin**, or the initial user can perform this operation.
+
+## Syntax
+
+```ebnf+diagram
+DropMaskingPolicy ::= DROP MASKING POLICY [IF EXISTS] policy_name;
+```
+
+## Parameter Description
+
+**policy_name**
+
+Specifies the audit policy name, which must be unique.
+
+Value range: a string. It must comply with the naming convention.
+
+## Examples
+
+```sql
+-- Delete an anonymization policy.
+mogdb=# DROP MASKING POLICY IF EXISTS maskpol1;
+
+-- Delete a group of anonymization policies.
+mogdb=# DROP MASKING POLICY IF EXISTS maskpol1, maskpol2, maskpol3;
+```
+
+## Helpful Links
+
+[ALTER MASKING POLICY](10.1-ALTER-MASKING-POLICY) and [CREATE MASKING POLICY](50.2-CREATE-MASKING-POLICY)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/84.3-DROP-MODEL.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/84.3-DROP-MODEL.md
new file mode 100644
index 0000000000000000000000000000000000000000..cfa766eb709056b974da047aa2dcdc67c4761a7e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/84.3-DROP-MODEL.md
@@ -0,0 +1,34 @@
+---
+title: DROP MODEL
+summary: DROP MODEL
+author: Zhang Cuiping
+date: 2021-11-01
+---
+
+# DROP MODEL
+
+## Function
+
+**DROP MODEL** deletes a model object that has been trained and saved.
+
+## Precautions
+
+The deleted model can be viewed in the **gs_model_warehouse** system catalog.
+
+## Syntax
+
+```ebnf+diagram
+DropModel ::= DROP MODEL model_name;
+```
+
+## Parameter Description
+
+model_name
+
+Specifies a model name.
+
+Value range: a string. It must comply with the identifier naming convention.
+
+## Helpful Links
+
+[CREATE MODEL](50.3-CREATE-MODEL) and [PREDICT BY](112.1-PREDICT-BY)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/85-DROP-MATERIALIZED-VIEW.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/85-DROP-MATERIALIZED-VIEW.md
new file mode 100644
index 0000000000000000000000000000000000000000..3c5078b9b29d9e74dc0cc7b2bddeb21a7a1ccfd0
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/85-DROP-MATERIALIZED-VIEW.md
@@ -0,0 +1,48 @@
+---
+title: DROP MATERIALIZED VIEW
+summary: DROP MATERIALIZED VIEW
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP MATERIALIZED VIEW
+
+## Function
+
+**DROP MATERIALIZED VIEW** forcibly deletes an existing materialized view from the database.
+
+## Precautions
+
+Only the owner of a materialized view or a system administrator has the **DROP MATERIALIZED VIEW** permission.
+
+## Syntax
+
+```ebnf+diagram
+DropMaterializedView ::= DROP MATERIALIZED VIEW [ IF EXISTS ] mv_name [, ...] [ CASCADE | RESTRICT ];
+```
+
+## Parameter Description
+
+- **IF EXISTS**
+
+  Reports a notice instead of an error if the specified materialized view does not exist.
+
+- **mv_name**
+
+  Name of the materialized view to be deleted.
+
+- **CASCADE | RESTRICT**
+
+  - **CASCADE**: automatically deletes the objects that depend on the materialized view.
+  - **RESTRICT**: refuses to delete the materialized view if any objects depend on it. This is the default action.
+
+## Example
+
+```sql
+-- Delete the materialized view named my_mv.
+mogdb=# DROP MATERIALIZED VIEW my_mv;
+```
+
+## Helpful Links
+
+[ALTER MATERIALIZED VIEW](11-ALTER-MATERIALIZED-VIEW), [CREATE INCREMENTAL MATERIALIZED VIEW](49.1-CREATE-INCREMENTAL-MATERIALIZED-VIEW), [CREATE MATERIALIZED VIEW](51-CREATE-MATERIALIZED-VIEW), [CREATE TABLE](60-CREATE-TABLE), [REFRESH INCREMENTAL MATERIALIZED VIEW](115.1-REFRESH-INCREMENTAL-MATERIALIZED-VIEW), and [REFRESH MATERIALIZED VIEW](116-REFRESH-MATERIALIZED-VIEW)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/85.1-DROP-OPERATOR.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/85.1-DROP-OPERATOR.md
new file mode 100644
index 0000000000000000000000000000000000000000..bee310bb79526ceb8f6ec77d4008171f498bb1e1
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/85.1-DROP-OPERATOR.md
@@ -0,0 +1,72 @@
+---
+title: DROP OPERATOR
+summary: DROP OPERATOR
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# DROP OPERATOR
+
+## Function
+
+DROP OPERATOR deletes an operator.
+
+## Precautions
+
+The DROP OPERATOR statement deletes an existing operator from the database. To execute this command, you must be the owner of the operator.
+
+## Syntax
+
+```ebnf+diagram
+DropOperator ::= DROP OPERATOR [ IF EXISTS ] name ( { left_type | NONE } , { right_type | NONE } ) [ CASCADE | RESTRICT ]
+```
+
+## Parameter Description
+
+- **IF EXISTS**
+
+  Do not throw an error if the specified operator does not exist. A notice is issued in this case.
+
+- **name**
+
+  Name (optionally schema-qualified) of an existing operator.
+
+- **left_type**
+
+  Type of the left operand for the operator. If no, set this parameter to **NONE**.
+
+- **right_type**
+
+  Type of the right operand for the operator. If no, set this parameter to **NONE**.
+
+- **CASCADE**
+
+  Automatically drops all objects that depend on this operator.
+
+- **RESTRICT**
+
+  Refuses to delete the operator if any objects depend on it. This is a default parameter.
+
+## Example
+
+Delete the power operator a^b used for integer.
+
+```sql
+DROP OPERATOR ^ (integer, integer);
+```
+
+Delete the left unary bit operator ~b for the bit type.
+
+```sql
+DROP OPERATOR ~ (none, bit);
+```
+
+Delete the factorial x used for bigint.:
+
+```sql
+DROP OPERATOR ! (bigint, none);
+```
+
+## Compatibility
+
+The SQL standard does not contain the DROP OPERATOR statement.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/86-DROP-OWNED.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/86-DROP-OWNED.md
new file mode 100644
index 0000000000000000000000000000000000000000..691ef77b69d79e239241db2a8a4e06f2d2abc069
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/86-DROP-OWNED.md
@@ -0,0 +1,40 @@
+---
+title: DROP OWNED
+summary: DROP OWNED
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP OWNED
+
+## Function
+
+**DROP OWNED** deletes the database objects owned by a database role.
+
+## Precautions
+
+- This interface will revoke the role's permissions on all objects in the current database and shared objects (databases and tablespaces).
+- **DROP OWNED** is often used to prepare for removing one or more roles. Because **DROP OWNED** affects only the objects in the current database, you need to run this statement in each database that contains the objects owned by the role to be removed.
+- Using the **CASCADE** option may cause this statement to recursively remove objects owned by other users.
+- The databases and tablespaces owned by the role will not be removed.
+
+## Syntax
+
+```ebnf+diagram
+DropOwned ::= DROP OWNED BY name [, ...] [ CASCADE | RESTRICT ];
+```
+
+## Parameter Description
+
+- **name**
+
+  Specifies the role name.
+
+- **CASCADE | RESTRICT**
+
+  - **CASCADE**: automatically deletes the objects that depend on the objects to be deleted.
+  - **RESTRICT**: refuses to delete the objects if other objects depend on them. This is the default action.
+
+## Helpful Links
+
+[REASSIGN OWNED](115-REASSIGN-OWNED) and [DROP ROLE](89-DROP-ROLE)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/86.1-DROP-RESOURCE-LABEL.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/86.1-DROP-RESOURCE-LABEL.md
new file mode 100644
index 0000000000000000000000000000000000000000..fefa276587083882bebda1b57025135d82b228b2
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/86.1-DROP-RESOURCE-LABEL.md
@@ -0,0 +1,44 @@
+---
+title: DROP RESOURCE LABEL
+summary: DROP RESOURCE LABEL
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# DROP RESOURCE LABEL
+
+## Function
+
+**DROP RESOURCE LABEL** deletes a resource label.
+
+## Precautions
+
+Only user **poladmin**, user **sysadmin**, or the initial user can perform this operation.
+
+## Syntax
+
+```ebnf+diagram
+DropResourceLabel ::= DROP RESOURCE LABEL [IF EXISTS] policy_name[, ...]*;
+```
+
+## Parameter Description
+
+**label_name**
+
+Specifies the resource label name.
+
+Value range: a string. It must comply with the naming convention.
+
+## Examples
+
+```sql
+-- Delete a resource label.
+mogdb=# DROP RESOURCE LABEL IF EXISTS res_label1;
+
+-- Delete a group resource label.
+mogdb=# DROP RESOURCE LABEL IF EXISTS res_label1, res_label2, res_label3;
+```
+
+## Helpful Links
+
+[ALTER RESOURCE LABEL](11.2-ALTER-RESOURCE-LABEL) and [CREATE RESOURCE LABEL](53.1-CREATE-RESOURCE-LABEL)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/86.2-DROP-RESOURCE-POOL.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/86.2-DROP-RESOURCE-POOL.md
new file mode 100644
index 0000000000000000000000000000000000000000..6e296fc6411b2c0e9bb85d013d0ea2389b3902b9
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/86.2-DROP-RESOURCE-POOL.md
@@ -0,0 +1,44 @@
+---
+title: DROP RESOURCE POOL
+summary: DROP RESOURCE POOL
+author: Zhang Cuiping
+date: 2021-11-01
+---
+
+# DROP RESOURCE POOL
+
+## Function
+
+**DROP RESOURCE POOL** deletes a resource pool.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The resource pool cannot be deleted if it is associated with a role.
+
+## Precautions
+
+Only a user with the **DROP** permission on the current database can perform this operation.
+
+## Syntax
+
+```ebnf+diagram
+DropResourcePool ::= DROP RESOURCE POOL [ IF EXISTS ] pool_name;
+```
+
+## Parameter Description
+
+- **IF EXISTS**
+
+  Reports a notice instead of an error if a specified resource pool does not exist.
+
+- **pool_name**
+
+  Specifies the name of a created resource pool.
+
+  Value range: a string. It must comply with the identifier naming convention.
+
+## Examples
+
+See **Examples** in **CREATE RESOURCE POOL**.
+
+## Helpful Links
+
+[ALTER RESOURCE POOL](11.3-ALTER-RESOURCE-POOL) and [CREATE RESOURCE POOL](53.2-CREATE-RESOURCE-POOL)
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/86.3-DROP-PACKAGE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/86.3-DROP-PACKAGE.md
new file mode 100644
index 0000000000000000000000000000000000000000..f0cd1b8fb4324e45e2ecfe131a14d204c61d6969
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/86.3-DROP-PACKAGE.md
@@ -0,0 +1,23 @@
+---
+title: DROP PACKAGE
+summary: DROP PACKAGE
+author: Zhang Cuiping
+date: 2021-11-08
+---
+
+# DROP PACKAGE
+
+## Function
+
+**DROP PACKAGE** deletes the existing package or package body.
+
+## Precautions
+
+After the package body is deleted, the stored procedures and functions in the package become invalid at the same time.
+
+## Syntax
+
+```sql
+DROP PACKAGE [ IF EXISTS ] package_name;
+DROP PACKAGE BODY [ IF EXISTS ] package_name;
+```
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/87-DROP-ROW-LEVEL-SECURITY-POLICY.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/87-DROP-ROW-LEVEL-SECURITY-POLICY.md
new file mode 100644
index 0000000000000000000000000000000000000000..17ddff9011465370e5a1bf993c663c3512d2a084
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/87-DROP-ROW-LEVEL-SECURITY-POLICY.md
@@ -0,0 +1,57 @@
+---
+title: DROP ROW LEVEL SECURITY POLICY
+summary: DROP ROW LEVEL SECURITY POLICY
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP ROW LEVEL SECURITY POLICY
+
+## Function
+
+**DROP ROW LEVEL SECURITY POLICY** deletes a row-level access control policy from a table.
+
+## Precautions
+
+Only the owner of a table or a system administrator has the **DROP ROW LEVEL SECURITY POLICY** permission.
+
+## Syntax
+
+```ebnf+diagram
+DropRowLevelSecurityPolicy ::= DROP [ ROW LEVEL SECURITY ] POLICY [ IF EXISTS ] policy_name ON table_name [ CASCADE | RESTRICT ]
+```
+
+## Parameter Description
+
+- **IF EXISTS**
+
+  Reports a notice instead of an error if the specified row-level access control policy does not exist.
+
+- **policy_name**
+
+    Specifies the name of the row-level access control policy to be deleted.
+
+  - table_name
+
+    Specifies the name of the table containing the row-level access control policy.
+
+  - CASCADE/RESTRICT
+
+    Currently, no objects depend on row-level access control policies. Therefore, **CASCADE** is equivalent to **RESTRICT**, and they are reserved to ensure backward compatibility.
+
+## Examples
+
+```sql
+-- Create the data table all_data.
+mogdb=# CREATE TABLE all_data(id int, role varchar(100), data varchar(100));
+
+-- Create a row-level access control policy.
+mogdb=# CREATE ROW LEVEL SECURITY POLICY all_data_rls ON all_data USING(role = CURRENT_USER);
+
+-- Delete a row-level access control policy.
+mogdb=# DROP ROW LEVEL SECURITY POLICY all_data_rls ON all_data;
+```
+
+## Helpful Links
+
+[ALTER ROW LEVEL SECURITY POLICY](13-ALTER-ROW-LEVEL-SECURITY-POLICY) and [CREATE ROW LEVEL SECURITY POLICY](52-CREATE-ROW-LEVEL-SECURITY-POLICY)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/88-DROP-PROCEDURE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/88-DROP-PROCEDURE.md
new file mode 100644
index 0000000000000000000000000000000000000000..20ed7ddf40b11ad752f828b59981fafc63f01eb9
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/88-DROP-PROCEDURE.md
@@ -0,0 +1,38 @@
+---
+title: DROP PROCEDURE
+summary: DROP PROCEDURE
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP PROCEDURE
+
+## Function
+
+**DROP PROCEDURE** deletes a stored procedure.
+
+## Precautions
+
+None
+
+## Syntax
+
+```ebnf+diagram
+DropProcedure ::= DROP PROCEDURE [ IF EXISTS  ] procedure_name ;
+```
+
+## Parameter Description
+
+- **IF EXISTS**
+
+  Reports a notice instead of an error if the specified stored procedure does not exist.
+
+- **procedure_name**
+
+  Specifies the name of the stored procedure to be deleted.
+
+  Value range: an existing stored procedure name
+
+## Helpful Links
+
+[CREATE PROCEDURE](53-CREATE-PROCEDURE)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/89-DROP-ROLE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/89-DROP-ROLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..cf63855d235e8905cd30638e954461be287456b2
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/89-DROP-ROLE.md
@@ -0,0 +1,42 @@
+---
+title: DROP ROLE
+summary: DROP ROLE
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP ROLE
+
+## Function
+
+**DROP ROLE** deletes a role.
+
+## Precautions
+
+None
+
+## Syntax
+
+```ebnf+diagram
+DropRole ::= DROP ROLE [ IF EXISTS ] role_name [, ...];
+```
+
+## Parameter Description
+
+- **IF EXISTS**
+
+  Reports a notice instead of an error if the specified role does not exist.
+
+- **role_name**
+
+  Specifies the name of the role to be deleted.
+
+  Value range: an existing role name
+
+## Examples
+
+See **Example** in **CREATE ROLE**.
+
+## Helpful Links
+
+[CREATE ROLE](54-CREATE-ROLE), [ALTER ROLE](12-ALTER-ROLE), and [SET ROLE](129-SET-ROLE)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/9-ALTER-INDEX.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/9-ALTER-INDEX.md
new file mode 100644
index 0000000000000000000000000000000000000000..c72de185c69b58e0c135c7849cde1c94e143aa1a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/9-ALTER-INDEX.md
@@ -0,0 +1,160 @@
+---
+title: ALTER INDEX
+summary: ALTER INDEX
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER INDEX
+
+## Function
+
+**ALTER INDEX** modifies the definition of an existing index.
+
+It has the following forms:
+
+- IF EXISTS
+
+  Sends a notice instead of an error if the specified index does not exist.
+
+- RENAME TO
+
+  Changes only the name of the index. The stored data is not affected.
+
+- SET TABLESPACE
+
+  This option changes the index tablespace to the specified tablespace and moves index-related data files to the new tablespace.
+
+- SET ( { STORAGE_PARAMETER = value } [, …] )
+
+  Changes one or more index-method-specific storage parameters of an index. Note that the index content will not be modified immediately by this statement. You may need to use **REINDEX** to recreate the index based on different parameters to achieve the expected effect.
+
+- RESET ( { storage_parameter } [, …] )
+
+  Resets one or more index-method-specific storage parameters of an index to the default value. Similar to the **SET** statement, **REINDEX** may be used to completely update the index.
+
+- [ MODIFY PARTITION index_partition_name ] UNUSABLE
+
+  Sets the indexes on a table or index partition to be unavailable.
+
+- REBUILD [ PARTITION index_partition_name ]
+
+  Rebuilds indexes on a table or an index partition.
+
+- RENAME PARTITION
+
+  Renames an index partition.
+
+- MOVE PARTITION
+
+  Modifies the tablespace to which an index partition belongs.
+
+## Precautions
+
+Only the index owner or a user who has the INDEX permission on the table where the index resides can run the **ALTER INDEX** command. The system administrator has this permission by default.
+
+## Syntax
+
+- Rename a table index.
+
+  ```ebnf+diagram
+  AlterIndex ::= ALTER INDEX [ IF EXISTS ] index_name
+      RENAME TO new_name;
+  ```
+
+- Change the tablespace to which a table index belongs.
+
+  ```ebnf+diagram
+  AlterIndex ::= ALTER INDEX [ IF EXISTS ] index_name
+      SET TABLESPACE tablespace_name;
+  ```
+
+- Modify the storage parameter of a table index.
+
+  ```ebnf+diagram
+  AlterIndex ::= ALTER INDEX [ IF EXISTS ] index_name
+      SET ( {storage_parameter = value} [, ... ] );
+  ```
+
+- Reset the storage parameter of a table index.
+
+  ```ebnf+diagram
+  AlterIndex ::= ALTER INDEX [ IF EXISTS ] index_name
+      RESET ( storage_parameter [, ... ] ) ;
+  ```
+
+- Set a table index or an index partition to be unavailable.
+
+  ```ebnf+diagram
+  AlterIndex ::= ALTER INDEX [ IF EXISTS ] index_name
+      [ MODIFY PARTITION index_partition_name ] UNUSABLE;
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The syntax cannot be used for column-store tables.
+
+- Rebuild a table index or index partition.
+
+  ```ebnf+diagram
+  AlterIndex ::= ALTER INDEX index_name
+      REBUILD [ PARTITION index_partition_name ];
+  ```
+
+- Rename an index partition.
+
+  ```ebnf+diagram
+  AlterIndex ::= ALTER INDEX [ IF EXISTS ] index_name
+      RENAME PARTITION index_partition_name TO new_index_partition_name;
+  ```
+
+- Modify the tablespace to which an index partition belongs.
+
+  ```ebnf+diagram
+  AlterIndex ::= ALTER INDEX [ IF EXISTS ] index_name
+      MOVE PARTITION index_partition_name TABLESPACE new_tablespace;
+  ```
+
+## Parameter Description
+
+- **index_name**
+
+  Specifies the index name to be modified.
+
+- **new_name**
+
+  Specifies the new name of the index.
+
+  Value range: a string. It must comply with the naming convention rule.
+
+- **tablespace_name**
+
+  Specifies the tablespace name.
+
+  Value range: an existing tablespace name
+
+- **storage_parameter**
+
+  Specifies the name of an index-method-specific parameter.
+
+- **value**
+
+  Specifies the new value for an index-method-specific storage parameter. This might be a number or a word depending on the parameter.
+
+- **new_index_partition_name**
+
+  Specifies the new name of the index partition.
+
+- **index_partition_name**
+
+  Specifies the name of an index partition.
+
+- **new_tablespace**
+
+  Specifies a new tablespace.
+
+## Examples
+
+See **Examples** in [CREATE INDEX](50-CREATE-INDEX).
+
+## Helpful Links
+
+[CREATE INDEX](50-CREATE-INDEX)，[DROP INDEX](84-DROP-INDEX)，[REINDEX](117-REINDEX)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/9.1-ALTER-LANGUAGE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/9.1-ALTER-LANGUAGE.md
new file mode 100644
index 0000000000000000000000000000000000000000..a73e056df9ac53634a6172681fdcb9f7896308ba
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/9.1-ALTER-LANGUAGE.md
@@ -0,0 +1,36 @@
+---
+title: ALTER LANGUAGE
+summary: ALTER LANGUAGE
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# ALTER LANGUAGE
+
+## Function
+
+**ALTER LANGUAGE**  modifies the definition of a procedural language. A single-node system or centralized system does not support modifying procedural languages.
+
+## Syntax
+
+```ebnf+diagram
+AlterLanguage ::= ALTER [ PROCEDURAL ] LANGUAGE name RENAME TO new_name ALTER [ PROCEDURAL ] LANGUAGE name OWNER TO new_owner;
+```
+
+## Parameter Description
+
+- **name**
+
+  Name of a language.
+
+- **new_name**
+
+  New name of a language.
+
+- **new_owner**
+
+  New owner of a language.
+
+## Compatibility
+
+The SQL standard does not contain the **ALTER LANGUAGE** statement.
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/90-DROP-RULE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/90-DROP-RULE.md
new file mode 100644
index 0000000000000000000000000000000000000000..740678a11f172dab8e642ac6a9bb113cc84a9975
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/90-DROP-RULE.md
@@ -0,0 +1,47 @@
+---
+title: DROP RULE
+summary: DROP RULE
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP RULE
+
+## Function
+
+**DROP RULE** deletes a rule.
+
+## Syntax
+
+```ebnf+diagram
+DropRule ::= DROP RULE [ IF EXISTS ] name ON table_name [ CASCADE | RESTRICT ]
+```
+
+## Parameter Description
+
+- **IF EXISTS**
+
+  Reports a notice If a rule does not exist.
+
+- **name**
+
+  Specifies the name of the current rule to be deleted.
+
+- **table_name**
+
+  Specifies the name of a table to which the rule is applied.
+
+- **CASCADE**
+
+  Automatically deletes the objects that depend on the rule.
+
+- **RESTRICT**
+
+  Refuses to delete the rule if any objects depend on it. This is the default action.
+
+## Example
+
+```sql
+--Delete the rule named newrule.
+DROP RULE newrule ON mytable;
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/91-DROP-SCHEMA.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/91-DROP-SCHEMA.md
new file mode 100644
index 0000000000000000000000000000000000000000..90d424bde2e52b3b68855eddfb14f48419ccf304
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/91-DROP-SCHEMA.md
@@ -0,0 +1,51 @@
+---
+title: DROP SCHEMA
+summary: DROP SCHEMA
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP SCHEMA
+
+## Function
+
+**DROP SCHEMA** deletes a schema from the current database.
+
+## Precautions
+
+Only the schema owner or a user granted with the DROP permission can run the **DROP SCHEMA** command. The system administrator has this permission by default.
+
+## Syntax
+
+```ebnf+diagram
+DropSchema ::= DROP SCHEMA [ IF EXISTS ] schema_name [, ...] [ CASCADE | RESTRICT ];
+```
+
+## Parameter Description
+
+- **IF EXISTS**
+
+  Reports a notice instead of an error if the specified schema does not exist.
+
+- **schema_name**
+
+  Specifies the name of the schema to be deleted.
+
+  Value range: an existing schema name
+
+- **CASCADE | RESTRICT**
+
+  - **CASCADE**: automatically deletes all the objects contained in the schema.
+  - **RESTRICT**: refuses to delete the schema if the schema contains objects. This is the default action.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** Schemas beginning with **pg_temp** or **pg_toast_temp** are for internal use. Do not delete them. Otherwise, unexpected consequences may be incurred.
+>
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The schema currently being used cannot be deleted. To delete it, switch to another schema first.
+
+## Examples
+
+See **Examples** in **CREATE SCHEMA**.
+
+## Helpful Links
+
+[ALTER SCHEMA](15-ALTER-SCHEMA) and [CREATE SCHEMA](56-CREATE-SCHEMA)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/92-DROP-SEQUENCE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/92-DROP-SEQUENCE.md
new file mode 100644
index 0000000000000000000000000000000000000000..f62cdd1851dc69c60cf8862a494f1f73ac7b5598
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/92-DROP-SEQUENCE.md
@@ -0,0 +1,54 @@
+---
+title: DROP SEQUENCE
+summary: DROP SEQUENCE
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP SEQUENCE
+
+## Function
+
+**DROP SEQUENCE** deletes a sequence from the current database.
+
+## Precautions
+
+Only the sequence owner or a user granted with the DROP permission can run the **DROP SEQUENCE** command. The system administrator has this permission by default.
+
+## Syntax
+
+```ebnf+diagram
+DropSequence ::= DROP SEQUENCE [ IF EXISTS ] {[schema'.']sequence_name} [ , ... ] [ CASCADE | RESTRICT ];
+```
+
+## Parameter Description
+
+- **IF EXISTS**
+
+  Reports a notice instead of an error if the specified sequence does not exist.
+
+- **name**
+
+  Specifies the name of the sequence to be deleted.
+
+- **CASCADE**
+
+  Automatically deletes the objects that depend on the sequence.
+
+- **RESTRICT**
+
+  Refuses to delete the sequence if any objects depend on it. This is the default action.
+
+## Examples
+
+```sql
+-- Create an ascending sequence named serial, starting from 101.
+mogdb=# CREATE SEQUENCE serial START 101;
+
+-- Delete a sequence.
+mogdb=# DROP SEQUENCE serial;
+```
+
+## Helpful Links
+
+[ALTER SEQUENCE](16-ALTER-SEQUENCE) and [CREATE SEQUENCE](57-CREATE-SEQUENCE)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/93-DROP-SERVER.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/93-DROP-SERVER.md
new file mode 100644
index 0000000000000000000000000000000000000000..9cfb0c772dd4f420d16a99468814c8637062839e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/93-DROP-SERVER.md
@@ -0,0 +1,41 @@
+---
+title: DROP SERVER
+summary: DROP SERVER
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP SERVER
+
+## Function
+
+**DROP SERVER** drops a data server.
+
+## Precautions
+
+Only the server owner or a user granted with the DROP permission can run the **DROP SERVER** command. The system administrator has this permission by default.
+
+## Syntax
+
+```ebnf+diagram
+DropServer ::= DROP SERVER [ IF EXISTS ] server_name [ {CASCADE | RESTRICT} ] ;
+```
+
+## Parameter Description
+
+- **IF EXISTS**
+
+  Reports a notice instead of an error if the specified data server does not exist.
+
+- **server_name**
+
+  Specifies the name of the data server to be dropped.
+
+- **CASCADE | RESTRICT**
+
+  - **CASCADE**: automatically drops the objects that depend on the data server.
+  - **RESTRICT**: refuses to drop the server if any objects depend on it. This is the default action.
+
+## Helpful Links
+
+[ALTER SERVER](17-ALTER-SERVER) and [CREATE SERVER](58-CREATE-SERVER)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/94-DROP-SYNONYM.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/94-DROP-SYNONYM.md
new file mode 100644
index 0000000000000000000000000000000000000000..b16f505a2e7b93b917a624adae151de1ef9dd2bf
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/94-DROP-SYNONYM.md
@@ -0,0 +1,45 @@
+---
+title: DROP SYNONYM
+summary: DROP SYNONYM
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP SYNONYM
+
+## Function
+
+**DROP SYNONYM** deletes a synonym.
+
+## Precautions
+
+Only the owner of a synonym or a system administrator has the **DROP SYNONYM** permission.
+
+## Syntax
+
+```ebnf+diagram
+DropSynonym ::= DROP SYNONYM [ IF EXISTS ] synonym_name [ CASCADE | RESTRICT ];
+```
+
+## Parameter Description
+
+- **IF EXISTS**
+
+  Reports a notice instead of an error if the specified synonym does not exist.
+
+- **synonym_name**
+
+  Specifies the name (optionally schema-qualified) of the synonym to be deleted.
+
+- **CASCADE | RESTRICT**
+
+  - **CASCADE**: automatically deletes the objects (such as views) that depend on the synonym.
+  - **RESTRICT**: refuses to delete the synonym if any objects depend on it. This is the default action.
+
+## Examples
+
+See **Example** in **CREATE SYNONYM**.
+
+## Helpful Links
+
+[ALTER SYNONYM](19-ALTER-SYNONYM) and [CREATE SYNONYM](59-CREATE-SYNONYM)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/95-DROP-TABLE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/95-DROP-TABLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..da7061d9d022482124806c8a10f02fc22ede17ac
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/95-DROP-TABLE.md
@@ -0,0 +1,51 @@
+---
+title: DROP TABLE
+summary: DROP TABLE
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP TABLE
+
+## Function
+
+**DROP TABLE** deletes a table.
+
+## Precautions
+
+- **DROP TABLE** forcibly deletes the specified table and the indexes depending on the table. After the table is deleted, the functions and stored procedures that need to use this table cannot be executed. Deleting a partitioned table also deletes all partitions in the table.
+- Only the table owner or a user granted with the DROP permission can run the **DROP TABLE** command. The system administrator has this permission by default.
+
+## Syntax
+
+```ebnf+diagram
+DropTable ::= DROP TABLE [ IF EXISTS ]
+    { [schema'.']table_name } [, ...] [ CASCADE | RESTRICT ];
+```
+
+## Parameter Description
+
+- **IF EXISTS**
+
+  Reports a notice instead of an error if the specified table does not exist.
+
+- **schema**
+
+  Specifies the schema name.
+
+- **table_name**
+
+  Specifies the name of the table to be deleted.
+
+- **CASCADE | RESTRICT**
+
+  - **CASCADE**: automatically deletes the objects (such as views) that depend on the table.
+  - **RESTRICT**: refuses to delete the table if any objects depend on it. This is the default action.
+
+## Examples
+
+See **Example** in **CREATE TABLE**.
+
+## Helpful Links
+
+[ALTER TABLE](22-ALTER-TABLE) and [CREATE TABLE](60-CREATE-TABLE)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/96-DROP-TABLESPACE.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/96-DROP-TABLESPACE.md
new file mode 100644
index 0000000000000000000000000000000000000000..5f34ece151d0de77371766e32e297f92ce2d3bba
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/96-DROP-TABLESPACE.md
@@ -0,0 +1,52 @@
+---
+title: DROP TABLESPACE
+summary: DROP TABLESPACE
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP TABLESPACE
+
+## Function
+
+**DROP TABLESPACE** deletes a tablespace.
+
+## Precautions
+
+- Only the tablespace owner or a user granted with the DROP permission can run the **DROP TABLESPACE** command. The system administrator has this permission by default.
+- The tablespace to be deleted should not contain any database objects. Otherwise, an error will be reported.
+- **DROP TABLESPACE** cannot be rolled back and therefore cannot be run in transaction blocks.
+- During execution of **DROP TABLESPACE**, database queries by other sessions using **\db** may fail and need to be reattempted.
+- If **DROP TABLESPACE** fails to be executed, run **DROP TABLESPACE IF EXISTS**.
+
+## Syntax
+
+```ebnf+diagram
+DropTablespace ::= DROP TABLESPACE [ IF EXISTS ] tablespace_name;
+```
+
+## Parameter Description
+
+- **IF EXISTS**
+
+  Reports a notice instead of an error if the specified tablespace does not exist.
+
+- **tablespace_name**
+
+  Specifies the name of the tablespace to be deleted.
+
+  Value range: an existing tablespace name
+
+## Examples
+
+See **Examples** in **CREATE TABLESPACE**.
+
+## Helpful Links
+
+[ALTER TABLESPACE](24-ALTER-TABLESPACE) and [CREATE TABLESPACE](63-CREATE-TABLESPACE)
+
+## Suggestions
+
+- drop database
+
+  Do not delete databases during transactions.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/97-DROP-TEXT-SEARCH-CONFIGURATION.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/97-DROP-TEXT-SEARCH-CONFIGURATION.md
new file mode 100644
index 0000000000000000000000000000000000000000..19190ced136fd84f3176afc577403bf2c8b862a6
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/97-DROP-TEXT-SEARCH-CONFIGURATION.md
@@ -0,0 +1,48 @@
+---
+title: DROP TEXT SEARCH CONFIGURATION
+summary: DROP TEXT SEARCH CONFIGURATION
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP TEXT SEARCH CONFIGURATION
+
+## Function
+
+**DROP TEXT SEARCH CONFIGURATION** deletes a text search configuration.
+
+## Precautions
+
+Only the owner of a text search configuration has the **DROP TEXT SEARCH CONFIGURATION** permission.
+
+## Syntax
+
+```ebnf+diagram
+DropTextSearchConfiguration ::= DROP TEXT SEARCH CONFIGURATION [ IF EXISTS ] name [ CASCADE | RESTRICT ];
+```
+
+## Parameter Description
+
+- **IF EXISTS**
+
+  Reports a notice instead of an error if the specified text search configuration does not exist.
+
+- **name**
+
+  Specifies the name (optionally schema-qualified) of the text search configuration to be deleted.
+
+- **CASCADE**
+
+  Automatically deletes the objects that depend on the text search configuration.
+
+- **RESTRICT**
+
+  Refuses to delete the text search configuration if any objects depend on it. This is the default action.
+
+## Examples
+
+See **Examples** in **CREATE TEXT SEARCH CONFIGURATION**.
+
+## Helpful Links
+
+[ALTER TEXT SEARCH CONFIGURATION](25-ALTER-TEXT-SEARCH-CONFIGURATION) and [CREATE TEXT SEARCH CONFIGURATION](64-CREATE-TEXT-SEARCH-CONFIGURATION)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/98-DROP-TEXT-SEARCH-DICTIONARY.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/98-DROP-TEXT-SEARCH-DICTIONARY.md
new file mode 100644
index 0000000000000000000000000000000000000000..8e8f0aba224de5aca52ecd63b19da97f5a5ecf02
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/98-DROP-TEXT-SEARCH-DICTIONARY.md
@@ -0,0 +1,57 @@
+---
+title: DROP TEXT SEARCH DICTIONARY
+summary: DROP TEXT SEARCH DICTIONARY
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP TEXT SEARCH DICTIONARY
+
+## Function
+
+**DROP TEXT SEARCH DICTIONARY** deletes a full-text retrieval dictionary.
+
+## Precautions
+
+- Predefined dictionaries do not support the **DROP** operations.
+- Only the owner of a dictionary or a system administrator has the **DROP TEXT SEARCH DICTIONARY** permission.
+- Execute **DROP…CASCADE** only when necessary because this operation will delete the text search configurations that use this dictionary.
+
+## Syntax
+
+```ebnf+diagram
+DropTextSearchDictionary ::= DROP TEXT SEARCH DICTIONARY [ IF EXISTS ] name [ CASCADE | RESTRICT ]
+```
+
+## Parameter Description
+
+- **IF EXISTS**
+
+  Reports a notice instead of an error if the specified full-text retrieval dictionary does not exist.
+
+- **name**
+
+  Specifies the name of the dictionary to be deleted. (If you do not specify a schema name, the dictionary in the current schema will be used.)
+
+  Value range: an existing dictionary name
+
+- **CASCADE**
+
+  Automatically deletes the objects that depend on the full-text retrieval dictionary and other objects that depend on these objects.
+
+  If any text search configuration uses the dictionary, the **DROP** statement will fail. You can add **CASCADE** to delete all text search configurations and dictionaries that use this dictionary.
+
+- **RESTRICT**
+
+  Refuses to delete the full-text retrieval dictionary if any object depends on it. This is the default action.
+
+## Examples
+
+```sql
+-- Delete the english dictionary.
+mogdb=# DROP TEXT SEARCH DICTIONARY english;
+```
+
+## Helpful Links
+
+[ALTER TEXT SEARCH DICTIONARY](26-ALTER-TEXT-SEARCH-DICTIONARY) and [CREATE TEXT SEARCH DICTIONARY](65-CREATE-TEXT-SEARCH-DICTIONARY)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/99-DROP-TRIGGER.md b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/99-DROP-TRIGGER.md
new file mode 100644
index 0000000000000000000000000000000000000000..c95a78a4f621ac7aa8da6e7263fc58078f40d21f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/sql-syntax/99-DROP-TRIGGER.md
@@ -0,0 +1,53 @@
+---
+title: DROP TRIGGER
+summary: DROP TRIGGER
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP TRIGGER
+
+## Function
+
+**DROP TRIGGER** deletes a trigger.
+
+## Precautions
+
+Only the owner of a trigger or a system administrator has the **DROP TRIGGER** permission.
+
+## Syntax
+
+```ebnf+diagram
+DropTrigger ::= DROP TRIGGER [ IF EXISTS ] trigger_name ON table_name [ CASCADE | RESTRICT ];
+```
+
+## Parameter Description
+
+- **IF EXISTS**
+
+  Reports a notice instead of an error if the specified trigger does not exist.
+
+- **trigger_name**
+
+  Specifies the name of the trigger to be deleted.
+
+  Value range: an existing trigger name
+
+- **table_name**
+
+  Specifies the name of the table containing the trigger.
+
+  Value range: name of the table containing the trigger
+
+- **CASCADE | RESTRICT**
+
+  - **CASCADE**: automatically deletes the objects that depend on the trigger.
+  - **RESTRICT**: refuses to delete the trigger if any objects depend on it. This is the default action.
+
+## Examples
+
+For details, see **Examples** in CREATE TRIGGER.
+
+## Helpful Links
+
+[CREATE TRIGGER](66-CREATE-TRIGGER), [ALTER TRIGGER](27-ALTER-TRIGGER), and [ALTER TABLE](22-ALTER-TABLE)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/1-numeric-data-types.md b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/1-numeric-data-types.md
new file mode 100644
index 0000000000000000000000000000000000000000..702fcf530e2ebff995ba1e827faf5b8beb94ee60
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/1-numeric-data-types.md
@@ -0,0 +1,245 @@
+---
+title: Numeric Data Types
+summary: Numeric Data Types
+author: Guo Huan
+date: 2021-04-06
+---
+
+# Numeric Data Types
+
+Table 1 lists all available types. For digit operators and related built-in functions, see [Mathematical Functions and Operators](7-mathematical-functions-and-operators).
+
+**Table 1** Integer types
+
+| Name                                   | Description                                            | Storage Space | Range                                                        |
+| :------------------------------------- | :----------------------------------------------------- | :------------ | :----------------------------------------------------------- |
+| TINYINT        | Tiny integer, also called INT1                         | 1 byte        | 0-255                                                        |
+| SMALLINT       | Small integer, also called INT2                        | 2 bytes       | -32,768 to +32,767                                           |
+| INTEGER        | Typical choice for integers, also called INT4          | 4 bytes       | -2,147,483,648 to +2,147,483,647                             |
+| BINARY_INTEGER | Alias of INTEGER.                                      | 4 bytes       | -2,147,483,648 to +2,147,483,647                             |
+| BIGINT         | Big integer, also called INT8                          | 8 bytes       | -9,223,372,036,854,775,808 to +9,223,372,036,854,775,807     |
+| int16          | A 16-byte certificate cannot be used to create tables. | 16 bytes      | -170,141,183,460,469,231,731,687,303,715,884,105,728 to +170,141,183,460,469,231,731,687,303,715,884,105,727 |
+
+Example:
+
+```sql
+-- Create a table containing TINYINT data.
+mogdb=# CREATE TABLE int_type_t1
+           (
+            IT_COL1 TINYINT
+           );
+
+-- Insert data to the created table.
+mogdb=# INSERT INTO int_type_t1 VALUES(10);
+
+-- View data.
+mogdb=# SELECT * FROM int_type_t1;
+ it_col1
+---------
+ 10
+(1 row)
+
+-- Delete the table.
+mogdb=# DROP TABLE int_type_t1;
+
+```
+
+```sql
+-- Create a table containing TINYINT, INTEGER, and BIGINT data.
+mogdb=# CREATE TABLE int_type_t2
+(
+    a TINYINT,
+    b TINYINT,
+    c INTEGER,
+    d BIGINT
+);
+
+-- Insert data.
+mogdb=# INSERT INTO int_type_t2 VALUES(100, 10, 1000, 10000);
+
+-- View data.
+mogdb=# SELECT * FROM int_type_t2;
+  a  | b  |  c   |   d
+-----+----+------+-------
+ 100 | 10 | 1000 | 10000
+(1 row)
+
+-- Delete the table.
+mogdb=# DROP TABLE int_type_t2;
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - Only numbers of the TINYINT, SMALLINT, INTEGER, BIGINT, or INT16 type, that is, integers can be stored. Saving a number with a decimal in any of the data types will result in errors.
+> - The INTEGER type is the common choice, as it offers the best balance between range, storage size, and performance. Generally, use the SMALLINT type only if you are sure that the value range is within the SMALLINT value range. The storage speed of INTEGER is much faster. BIGINT is used only when the range of INTEGER is not large enough.
+
+**Table 2** Any-precision types
+
+| Name                                     | Description                         | Storage Space                               | Range                                      |
+| :--------------------------------------- | :---------------------------------- | :---------------------------------- | :---------------------------------- |
+| NUMERIC[(p[,s])],DECIMAL[(p[,s])] | The value range of **p** (precision) is [1,1000], and the value range of **s** (scale) is [0,*p*].<br />NOTE:<br />**p** indicates the total digits, and **s** indicates the decimal digit. | The precision is specified by users. Every four decimal digits occupy two bytes, and an extra eight-byte overhead is added to the entire data. | Up to 131,072 digits before the decimal point; and up to 16,383 digits after the decimal point when no precision is specified |
+| NUMBER[(p[,s])]                   | Alias of the NUMERIC type.                                   | The precision is specified by users. Every four decimal digits occupy two bytes, and an extra eight-byte overhead is added to the entire data. | Up to 131,072 digits before the decimal point; and up to 16,383 digits after the decimal point when no precision is specified |
+
+Example:
+
+```sql
+-- Create a table.
+mogdb=# CREATE TABLE decimal_type_t1
+(
+    DT_COL1 DECIMAL(10,4)
+);
+
+-- Insert data.
+mogdb=# INSERT INTO decimal_type_t1 VALUES(123456.122331);
+
+-- Query data in the table.
+mogdb=# SELECT * FROM decimal_type_t1;
+   dt_col1
+-------------
+ 123456.1223
+(1 row)
+
+-- Delete the table.
+mogdb=# DROP TABLE decimal_type_t1;
+
+```
+
+```sql
+-- Create a table.
+mogdb=# CREATE TABLE numeric_type_t1
+(
+    NT_COL1 NUMERIC(10,4)
+);
+
+-- Insert data.
+mogdb=# INSERT INTO numeric_type_t1 VALUES(123456.12354);
+
+-- Query data in the table.
+mogdb=# SELECT * FROM numeric_type_t1;
+   nt_col1
+-------------
+ 123456.1235
+(1 row)
+
+-- Delete the table.
+mogdb=# DROP TABLE numeric_type_t1;
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - Compared to the integer types, the arbitrary precision numbers require larger storage space and have lower storage efficiency, operation efficiency, and poorer compression ratio results. The INTEGER type is the common choice when number types are defined. Arbitrary precision numbers are used only when numbers exceed the maximum range indicated by the integers.
+> - When NUMERIC/DECIMAL is used for defining a column, you are advised to specify the precision (p) and scale (s) for the column.
+
+**Table 3** Sequence integer
+
+| Name                 | Description     | Storage Space | Range                |
+| :------------------- | :------------------- | :------------ | :----------------------------------|
+| SMALLSERIAL | Two-byte auto-incrementing integer   | 2 bytes       | -32,768 to +32,767                                           |
+| SERIAL      | Four-byte auto-incrementing integer  | 4 bytes       | -2,147,483,648 to +2,147,483,647                             |
+| BIGSERIAL   | Eight-byte auto-incrementing integer | 8 bytes       | -9,223,372,036,854,775,808 to +9,223,372,036,854,775,807     |
+| LARGESERIAL | 16-byte serial integer               | 16 bytes      | -170,141,183,460,469,231,731,687,303,715,884,105,728 to +170,141,183,460,469,231,731,687,303,715,884,105,727 |
+
+Example:
+
+```sql
+-- Create a table.
+mogdb=# CREATE TABLE smallserial_type_tab(a SMALLSERIAL);
+
+-- Insert data.
+mogdb=# INSERT INTO smallserial_type_tab VALUES(default);
+
+-- Insert data again.
+mogdb=# INSERT INTO smallserial_type_tab VALUES(default);
+
+-- View data.
+mogdb=# SELECT * FROM smallserial_type_tab;
+ a
+---
+ 1
+ 2
+(2 rows)
+
+-- Create a table.
+mogdb=# CREATE TABLE serial_type_tab(b SERIAL);
+
+-- Insert data.
+mogdb=# INSERT INTO serial_type_tab VALUES(default);
+
+-- Insert data again.
+mogdb=# INSERT INTO serial_type_tab VALUES(default);
+
+-- View data.
+mogdb=# SELECT * FROM serial_type_tab;
+ b
+---
+ 1
+ 2
+(2 rows)
+
+-- Create a table.
+mogdb=# CREATE TABLE bigserial_type_tab(c BIGSERIAL);
+
+-- Insert data.
+mogdb=# INSERT INTO bigserial_type_tab VALUES(default);
+
+-- Insert data.
+mogdb=# INSERT INTO bigserial_type_tab VALUES(default);
+
+-- View data.
+mogdb=# SELECT * FROM bigserial_type_tab;
+ c
+---
+ 1
+ 2
+(2 rows)
+
+-- Delete the table.
+mogdb=# DROP TABLE smallserial_type_tab;
+
+mogdb=# DROP TABLE serial_type_tab;
+
+mogdb=# DROP TABLE bigserial_type_tab;
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> SMALLSERIAL, SERIAL and BIGSERIAL are not real types. They are concepts used for setting a unique identifier for a table. Therefore, an integer column is created and its default value plans to be read from a sequencer. A NOT NULL constraint is used to ensure NULL is not inserted. In most cases you would also want to attach a **UNIQUE** or **PRIMARY KEY** constraint to prevent duplicate values from being inserted unexpectedly, but this is not automatic. The sequencer is set so that it belongs to the column. In this case, when the column or the table is deleted, the sequencer is also deleted. Currently, the **SERIAL** column can be specified only when you create a table. You cannot add the **SERIAL** column in an existing table. In addition, **SERIAL** columns cannot be created in temporary tables. Because SERIAL is not a data type, columns cannot be converted to this type.
+
+**Table 4** Floating point types
+
+| Name                    | Description         | Storage Space       | Range               |
+| :---------------------- | :------------------ | :------------------ | :------------------ |
+| REAL,FLOAT4             | Single precision floating points, inexact                    | 4 bytes                                                      | -3.402E+38 to 3.402E+38, 6-bit decimal digits                |
+| DOUBLE PRECISION,FLOAT8 | Double precision floating points, inexact                    | 8 bytes                                                      | -1.79E+308 to 1.79E+308, 15-bit decimal digits               |
+| FLOAT[(p)]              | Floating points, inexact. The value range of **p** (precision) is [1,53].<br />NOTE:<br />**p** is the precision, indicating the total decimal digits. | 4 or 8 bytes                                                 | **REAL** or **DOUBLE PRECISION** is selected as an internal identifier based on precision (p). If no precision is specified, DOUBLE PRECISION is used as the internal identifier. |
+| BINARY_DOUBLE           | Alias of DOUBLE PRECISION.                                   | 8 bytes                                                      | -1.79E+308 to 1.79E+308, 15-bit decimal digits               |
+| DEC[(p[,s])]            | The value range of **p** (precision) is [1,1000], and the value range of **s** (scale) is [0,*p*].<br />NOTE:<br />**p** indicates the total digits, and **s** indicates the decimal digit. | The precision is specified by users. Every four decimal digits occupy two bytes, and an extra eight-byte overhead is added to the entire data. | Up to 131,072 digits before the decimal point; and up to 16,383 digits after the decimal point when no precision is specified |
+| INTEGER[(p[,s])]        | The value range of **p** (precision) is [1,1000], and the value range of **s** (scale) is [0,*p*]. | The precision is specified by users. Every four decimal digits occupy two bytes, and an extra eight-byte overhead is added to the entire data. | -                                                            |
+
+Example:
+
+```sql
+-- Create a table.
+mogdb=# CREATE TABLE float_type_t2
+(
+    FT_COL1 INTEGER,
+    FT_COL2 FLOAT4,
+    FT_COL3 FLOAT8,
+    FT_COL4 FLOAT(3),
+    FT_COL5 BINARY_DOUBLE,
+    FT_COL6 DECIMAL(10,4),
+    FT_COL7 INTEGER(6,3)
+);
+
+-- Insert data.
+mogdb=# INSERT INTO float_type_t2 VALUES(10,10.365456,123456.1234,10.3214, 321.321, 123.123654, 123.123654);
+
+-- View data.
+mogdb=# SELECT * FROM float_type_t2 ;
+ ft_col1 | ft_col2 |   ft_col3   | ft_col4 | ft_col5 | ft_col6  | ft_col7
+---------+---------+-------------+---------+---------+----------+---------
+      10 | 10.3655 | 123456.1234 | 10.3214 | 321.321 | 123.1237 | 123.124
+(1 row)
+
+-- Delete the table.
+mogdb=# DROP TABLE float_type_t2;
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/10-text-search-types.md b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/10-text-search-types.md
new file mode 100644
index 0000000000000000000000000000000000000000..2bcec096d402376880158179fdb675627b87a99a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/10-text-search-types.md
@@ -0,0 +1,168 @@
+---
+title: Text Search Types
+summary: Text Search Types
+author: Guo Huan
+date: 2021-04-06
+---
+
+# Text Search Types
+
+MogDB **tsvector** type represents a document in a form optimized for text search. The **tsquery** type similarly represents a text query.
+
+## tsvector
+
+The **tsvector** type represents a retrieval unit, usually a textual column within a row of a database table, or a combination of such columns. A **tsvector** value is a sorted list of distinct lexemes, which are words that have been normalized to merge different variants of the same word. Sorting and deduplication are done automatically during input. The **to_tsvector** function is used to parse and normalize a document string. The **to_tsvector** function is used to parse and normalize a document string.
+
+A **tsvector** value is a sorted list of distinct lexemes, which are words that have been formatted different entries. During segmentation, **tsvector** automatically performs duplicate-elimination to the entries for input in a certain order. For example:
+
+```sql
+mogdb=# SELECT 'a fat cat sat on a mat and ate a fat rat'::tsvector;
+                      tsvector
+----------------------------------------------------
+ 'a' 'and' 'ate' 'cat' 'fat' 'mat' 'on' 'rat' 'sat'
+(1 row)
+```
+
+It can be seen from the preceding example that **tsvector** segments a string by spaces, and segmented lexemes are sorted based on their length and alphabetical order. To represent lexemes containing whitespace or punctuation, surround them with quotes:
+
+```sql
+mogdb=# SELECT $$the lexeme '    ' contains spaces$$::tsvector;
+                 tsvector
+-------------------------------------------
+ '    ' 'contains' 'lexeme' 'spaces' 'the'
+(1 row)
+```
+
+Use double dollar signs ($$) to mark entries containing single quotation marks (").
+
+```sql
+mogdb=# SELECT $$the lexeme 'Joe''s' contains a quote$$::tsvector;
+                    tsvector
+------------------------------------------------
+ 'Joe''s' 'a' 'contains' 'lexeme' 'quote' 'the'
+(1 row)
+```
+
+Optionally, integer positions can be attached to lexemes:
+
+```sql
+mogdb=# SELECT 'a:1 fat:2 cat:3 sat:4 on:5 a:6 mat:7 and:8 ate:9 a:10 fat:11 rat:12'::tsvector;
+                                   tsvector
+-------------------------------------------------------------------------------
+ 'a':1,6,10 'and':8 'ate':9 'cat':3 'fat':2,11 'mat':7 'on':5 'rat':12 'sat':4
+(1 row)
+```
+
+A position normally indicates the source word's location in the document. Positional information can be used for proximity ranking. Position values range from 1 to 16383. The default maximum value is **16383**. Duplicate positions for the same lexeme are discarded.
+
+Lexemes that have positions can further be labeled with a weight, which can be **A**, **B**, **C**, or **D**. **D** is the default and hence is not shown on output:
+
+```sql
+mogdb=# SELECT 'a:1A fat:2B,4C cat:5D'::tsvector;
+          tsvector
+----------------------------
+ 'a':1A 'cat':5 'fat':2B,4C
+(1 row)
+```
+
+Weights are typically used to reflect document structure, for example, by marking title words differently from body words. Text search ranking functions can assign different priorities to the different weight markers.
+
+The following example is the standard usage of the **tsvector** type. For example:
+
+```sql
+mogdb=# SELECT 'The Fat Rats'::tsvector;
+      tsvector
+--------------------
+ 'Fat' 'Rats' 'The'
+(1 row)
+```
+
+For most English-text-searching applications the above words would be considered non-normalized, which should usually be passed through **to_tsvector** to normalize the words appropriately for searching:
+
+```sql
+mogdb=# SELECT to_tsvector('english', 'The Fat Rats');
+   to_tsvector
+-----------------
+ 'fat':2 'rat':3
+(1 row)
+```
+
+## tsquery
+
+The **tsquery** type represents a retrieval condition. A **tsquery** value stores lexemes that are to be searched for, and combines them honoring the **Boolean** operators **& (AND)**, **| (OR)**, and **! (NOT)**. Parentheses can be used to enforce grouping of the operators. The **to_tsquery** and **plainto_tsquery** functions will normalize lexemes before the lexemes are converted to the **tsquery** type.
+
+```sql
+mogdb=# SELECT 'fat & rat'::tsquery;
+    tsquery
+---------------
+ 'fat' & 'rat'
+(1 row)
+
+mogdb=# SELECT 'fat & (rat | cat)'::tsquery;
+          tsquery
+---------------------------
+ 'fat' & ( 'rat' | 'cat' )
+(1 row)
+
+mogdb=# SELECT 'fat & rat & ! cat'::tsquery;
+        tsquery
+------------------------
+ 'fat' & 'rat' & !'cat'
+(1 row)
+```
+
+In the absence of parentheses, **! (NOT)** binds most tightly, and **& (AND)** binds more tightly than **| (OR)**.
+
+Lexemes in a **tsquery** can be labeled with one or more weight letters, which restrict them to match only **tsvector** lexemes with matching weights:
+
+```sql
+mogdb=# SELECT 'fat:ab & cat'::tsquery;
+     tsquery
+------------------
+ 'fat':AB & 'cat'
+(1 row)
+```
+
+Also, lexemes in a **tsquery** can be labeled with * to specify prefix matching:
+
+```sql
+mogdb=# SELECT 'super:*'::tsquery;
+  tsquery
+-----------
+ 'super':*
+(1 row)
+```
+
+This query will match any word in a **tsvector** that begins with "super".
+
+Note that prefixes are first processed by text search configurations, which means the following example returns true:
+
+```sql
+mogdb=# SELECT to_tsvector( 'postgraduate' ) @@ to_tsquery( 'mogdb:*' ) AS RESULT;
+  result
+----------
+ t
+(1 row)
+```
+
+This is because **mogdb** gets stemmed to **postgr**:
+
+```sql
+mogdb=# SELECT to_tsquery('mogdb:*');
+ to_tsquery
+------------
+ 'postgr':*
+(1 row)
+```
+
+It then matches **postgraduate**.
+
+**'Fat:ab & Cats'** is normalized to the **tsquery** type as follows:
+
+```sql
+mogdb=# SELECT to_tsquery('Fat:ab & Cats');
+    to_tsquery
+------------------
+ 'fat':AB & 'cat'
+(1 row)
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/11-uuid-type.md b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/11-uuid-type.md
new file mode 100644
index 0000000000000000000000000000000000000000..2d7878f1a5ac7185a002ac7b7414fc6fad905a8e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/11-uuid-type.md
@@ -0,0 +1,27 @@
+---
+title: UUID Type
+summary: UUID Type
+author: Guo Huan
+date: 2021-04-06
+---
+
+# UUID Type
+
+The data type **UUID** stores Universally Unique Identifiers (UUID) as defined by RFC 4122, ISO/IEF 9834-8:2005, and related standards. This identifier is a 128-bit quantity that is generated by an algorithm chosen to make it very unlikely that the same identifier will be generated by anyone else in the known universe using the same algorithm.
+
+A UUID is written as a sequence of lower-case hexadecimal digits, in several groups separated by hyphens, specifically a group of 8 digits followed by three groups of 4 digits followed by a group of 12 digits, for a total of 32 digits representing the 128 bits. An example of a UUID in this standard form is:
+
+```sql
+a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11
+```
+
+openGauss also accepts the following alternative forms for input: use of upper-case letters and digits, the standard format surrounded by braces, omitting some or all hyphens, adding a hyphen after any group of four digits. An example is provided as follows:
+
+```sql
+A0EEBC99-9C0B-4EF8-BB6D-6BB9BD380A11
+{a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11}
+a0eebc999c0b4ef8bb6d6bb9bd380a11
+a0ee-bc99-9c0b-4ef8-bb6d-6bb9-bd38-0a11
+```
+
+Output is always in the standard form.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/12-json-types.md b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/12-json-types.md
new file mode 100644
index 0000000000000000000000000000000000000000..e35e661802b5479452a5ab9c26b00ba48cacf342
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/12-json-types.md
@@ -0,0 +1,138 @@
+---
+title: JSON/JSONB Types
+summary: JSON/JSONB Types
+author: Guo Huan
+date: 2021-04-06
+---
+
+# JSON/JSONB Types
+
+JavaScript Object Notation (JSON) data can be a single scalar, an array, or a key-value pair object. The array and object can be called a container:
+
+- Scalar: a number, Boolean, string, or null
+- Array: defined in a pair of square brackets ([]), in which elements can be any type of JSON data, and are not necessarily of the same type.
+- Object: defined in a pair of braces ({}), in which objects are stored in the format of **key:value**. Each key must be a string enclosed by a pair of double quotation marks (""), and its value can be any type of JSON data. In case of duplicate keys, the last key-value pair will be used.
+
+MogDB supports two types JSON and JSONB to store JSON data. JSON data is a complete copy of the input, retaining the entered spaces, duplicate keys, and sequence, while JSONB stores data in a decomposed binary form, removing semantic-irrelevant details and duplicate keys, and sorting key-values. Therefore, JSONB data does not need to be parsed.
+
+Basically, both are JSON data types. However, they differ greatly in efficiency. Because JSON data is an exact copy of the input text, the data must be parsed on every execution; in contrast, JSONB data is stored in a decomposed binary form and can be processed faster, though this makes it slightly slower to input due to the conversion mechanism. In addition, because the JSONB data form is unified, it better supports more powerful functions, for example, comparing sizes according to a specific rule. JSONB also supports indexing, which is a significant advantage.
+
+## Input Format
+
+An input must be a JSON-compliant string, which is enclosed in single quotation marks (").
+
+Null (null-json): Only null is supported, and all letters are in lowercase.
+
+```sql
+select 'null'::json;   -- sucselect 'NULL'::jsonb;  -- err
+```
+
+Number (num-json): The value can be a positive or negative integer, decimal fraction, or 0. The scientific notation is supported.
+
+```sql
+select '1'::json;select '-1.5'::json;select '-1.5e-5'::jsonb, '-1.5e+2'::jsonb;select '001'::json, '+15'::json, 'NaN'::json; -- Redundant leading zeros, plus signs (+), NaN, and infinity are not supported.
+```
+
+Boolean (bool-json): The value can only be **true** or **false** in lowercase.
+
+```sql
+select 'true'::json;select 'false'::jsonb;
+```
+
+String (str-json): The value must be a string enclosed in double quotation marks ("").
+
+```sql
+select '"a"'::json;select '"abc"'::jsonb;
+```
+
+Array (array-json): Arrays are enclosed in square brackets ([]). Elements in the array can be any valid JSON data, and are unnecessarily of the same type.
+
+```sql
+select '[1, 2, "foo", null]'::json;select '[]'::json;select '[1, 2, "foo", null, [[]], {}]'::jsonb;
+```
+
+Object (object-json): The value is enclosed in braces ({}). The key must be a JSON-compliant string, and the value can be any valid JSON string.
+
+```sql
+select '{}'::json;select '{"a": 1, "b": {"a": 2,  "b": null}}'::json;select '{"foo": [true, "bar"], "tags": {"a": 1, "b": null}}'::jsonb;
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **CAUTION:**
+>
+> - Note that 'null'::json and null::json are different, which are similar to the strings str="" and str=null.
+> - For numbers, when scientific notation is used, JSONB expands them, while JSON stores an exact copy of the input text.
+
+## JSONB Advanced Features
+
+- Precautions
+  - Row-store tables are not supported.
+  - It cannot be used as a partition key.
+  - Foreign tables and MOTs are not supported.
+
+The main difference between JSON and JSONB lies in the storage mode. JSONB stores parsed binary data, which reflects the JSON hierarchy and facilitates direct access. Therefore, JSONB has many advanced features that JSON does not have.
+
+- Format normalization
+
+  - After the input object-json string is parsed into JSONB binary, semantically irrelevant details are naturally discarded, for example, spaces:
+
+    ```sql
+    mogdb=# select '   [1, " a ", {"a"   :1    }]  '::jsonb;        jsonb
+    ----------------------
+    [1, " a ", {"a": 1}](1 row)
+    ```
+
+  - For object-json, duplicate key-values are deleted and only the last key-value is retained. For example:
+
+    ```sql
+    mogdb=# select '{"a" : 1, "a" : 2}'::jsonb;  jsonb---------- {"a": 2}(1 row)
+    ```
+
+  - For object-json, key-values will be re-sorted. The sorting rule is as follows: 1. Longer key-values are sorted last. 2. If the key-values are of the same length, the key-values with a larger ASCII code are sorted after the key-values with a smaller ASCII code:
+
+    ```sql
+    mogdb=# select '{"aa" : 1, "b" : 2, "a" : 3}'::jsonb;           jsonb
+    ---------------------------
+    {"a": 3, "b": 2, "aa": 1}(1 row)
+    ```
+
+- Size comparison
+
+    Format normalization ensures that only one form of JSONB data exists in the same semantics. Therefore, sizes may be compared according to a specific rule.
+
+  - First, type comparison: **object-jsonb** &gt; **array-jsonb** &gt; **bool-jsonb** &gt; **num-jsonb** &gt; **str-jsonb** &gt; **null-jsonb**
+
+  - Content comparison if the data type is the same:
+
+    - **str-json**: The default text sorting rule of the database is used for comparison. A positive value indicates greater than, a negative value indicates less than, and **0** indicates equal.
+    - **num-json**: numeric comparison
+    - **bool-json**: **true** &gt; **false**
+    - **array-jsonb**: long elements &gt; short elements. If the lengths are the same, compare each element in sequence.
+    - **object-jsonb**: If the length of a key-value pair is longer than that of a short key-value pair, the key is compared first, and then the value is compared.
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **CAUTION:** For comparison within the **object-jsonb** type, the final result after format sorting is used for comparison. Therefore, the comparison result may not be intuitive compared with the direct input.
+
+- Creating indexes, primary keys, and foreign keys
+
+  - B-tree index
+
+    B-tree indexes, primary keys, and foreign keys can be created for the **JSONB** type.
+
+  - GIN index
+
+    GIN indexes can be used to effectively search for keys or key-value pairs that appear in a large number of JSONB documents (datums). Two GIN operator classes (**jsonb_ops** and **jsonb_hash_ops**) are provided for different performance and flexibility choices. The default GIN operator class supports **@&gt;**, **&lt;@**, **?**, **?&** and **?|** operator query. The non-default GIN operator class **jsonb_path_ops** supports only the **@&gt;** and **&lt;@** operators.
+
+    For details about the operators, see [JSON/JSONB Functions and Operators](13-json-functions).
+
+- Inclusion and existence
+
+  Querying whether a JSON contains some elements or whether some elements exist in a JSON is an important capability of JSONB.
+
+  ```
+  -- A simple scalar/original value contains only the same value: SELECT '"foo"'::jsonb @> '"foo"'::jsonb; -- The array on the left contains the string on the right. SELECT' [ 1, "aa", 3 ] '::jsonb? 'aa'; -- The array on the left contains all elements in the array on the right. The sequence and repetition are not specified. SELECT '[1, 2, 3]'::jsonb @> '[1, 3, 1]'::jsonb; -- The object-json on the left contains all key-values of the object-json on the right. SELECT '{"product": "PostgreSQL", "version": 9.4, "jsonb":true}'::jsonb @> '{"version":9.4}'::jsonb; -- The array on the left does not contain all elements of the array on the right, because the three elements of the array on the left are 1, 2, and [1,3], and the elements on the right are 1 and 3. SELECT'[1, 2, [1, 3] ]. '::jsonb @>' [1, 3] '::jsonb; -- Produces a false. SELECT '{"foo": {"bar": "baz"}}'::jsonb @> '{"bar": "baz"}'::jsonb; -- Similarly, false is produced.
+  ```
+
+  For details about the operators, see [JSON/JSONB Functions and Operators](13-json-functions).
+
+- Functions and operators
+
+  For details about the functions and operators supported by the JSON/JSONB type, see [JSON/JSONB Functions and Operators](13-json-functions).
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/13-HLL.md b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/13-HLL.md
new file mode 100644
index 0000000000000000000000000000000000000000..a578842c26b30a86bd0e2c568598ce43d354fd8f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/13-HLL.md
@@ -0,0 +1,206 @@
+---
+title: HLL
+summary: HLL
+author: Guo Huan
+date: 2021-04-06
+---
+
+# HLL
+
+HyperLoglog (HLL) is an approximation algorithm for efficiently counting the number of distinct values in a data set. It features faster computing and lower space usage. You only need to store HLL data structures, instead of data sets. When new data is added to a data set, make hash calculation on the data and insert the result to an HLL. Then, you can obtain the final result based on the HLL.
+
+[Table 1](#biao1) compares HLL with other algorithms.
+
+**Table 1** Comparison between HLL and other algorithms <a id="biao1"> </a>
+
+| Item                      | Sorting Algorithm     | Hash Algorithm        | HLL                                   |
+| :------------------------ | :-------------------- | :-------------------- | :------------------------------------ |
+| Time complexity           | O(nlogn)              | O(n)                  | O(n)                                  |
+| Space complexity          | O(n)                  | O(n)                  | log(logn)                             |
+| Error rate                | 0                     | 0                     | ≈0.8%                                 |
+| Storage space requirement | Size of original data | Size of original data | The maximum size is 16 KB by default. |
+
+HLL has advantages over others in the computing speed and storage space requirement. In terms of time complexity, the sorting algorithm needs O(nlogn) time for sorting, and the hash algorithm and HLL need O(n) time for full table scanning. In terms of storage space requirements, the sorting algorithm and hash algorithm need to store raw data before collecting statistics, whereas the HLL algorithm needs to store only the HLL data structures rather than the raw data, and thereby occupying a fixed space of about 16 KB.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - In the current default specifications, the maximum number of distinct values that can be calculated is about 1.1e + 15, and the error rate is 0.8%. If the calculation result exceeds the maximum, the error rate of the calculation result will increase, or the calculation will fail and an error will be reported.
+> - When using this feature for the first time, you need to evaluate the distinct values of the service, properly select configuration parameters, and perform verification to ensure that the accuracy meets requirements.
+>   - By default, the distinct value is 1.1e + 15. If the distinct value is NaN, you need to adjust log2m or use another algorithm to calculate the distinct value.
+>   - The hash algorithm has an extremely low probability of collision. However, you are still advised to select 2 or 3 hash seeds for verification when using the hash algorithm for the first time. If there is only a small difference between the distinct values, you can select any one of the seeds as the hash seed.
+
+[Table 2](#hyper) describes main HLL data structures.
+
+**Table 2** Main HLL data structures <a id="hyper"> </a>
+
+| Data Type | Description                                                  |
+| :-------- | :----------------------------------------------------------- |
+| hll       | The HLL header is a 27-byte field. By default, the data length ranges from 0 KB to 16 KB. The distinct value can be obtained. |
+
+When you create an HLL data type, 0 to 4 input parameters are supported. The parameter meanings and specifications are the same as those of the **hll_empty** function. The first parameter is **log2m**, indicating the logarithm of the number of buckets, and its value ranges from 10 to 16. The second parameter is **log2explicit**, indicating the threshold in explicit mode, and its value ranges from 0 to 12. The third parameter is **log2sparse**, indicating the threshold of the Sparse mode, and its value ranges from 0 to 14. The fourth parameter is **duplicatecheck**, indicating whether to enable duplicatecheck, and its value ranges from 0 to 1. When the input parameter is set to **-1**, the default value of the HLL parameter is used. You can run the **\d** or **\d+** command to view the parameters of the HLL type.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** When the HLL data type is created, the result varies depending on the input parameter behavior:
+>
+> - When creating an HLL type, do not set the input parameter or set it to **-1**. Use the default value of the corresponding HLL parameter.
+> - If a valid value is set for the input parameter, the corresponding HLL parameter uses the input value.
+> - If the input value is invalid, an error is reported when the HLL type is created.
+
+```sql
+-- Create an HLL table without specifying input parameters.
+mogdb=# create table t1 (id integer, set hll);
+mogdb=# \d t1
+      Table "public.t1"
+ Column |  Type   | Modifiers
+--------+---------+-----------
+ c1     | integer |
+ c2     | hll     |
+
+-- Create an HLL table, specify the first two input parameters, and use the default values for the last two input parameters.
+mogdb=# create table t2 (id integer, set hll(12,4));
+          Table "public.t2"
+ Column |      Type      | Modifiers
+--------+----------------+-----------
+ c1     | integer        |
+ c2     | hll(12,4,12,0) |
+
+-- Create an HLL table, specify the third input parameter, and use default values for other parameters.
+mogdb=# create table t3(id int, set hll(-1,-1,8,-1));
+mogdb=# \d t3
+          Table "public.t3"
+ Column |      Type      | Modifiers
+--------+----------------+-----------
+ c1     | integer        |
+ c2     | hll(14,10,8,0) |
+
+-- When a user creates an HLL table and specifies an invalid input parameter, an error is reported.
+mogdb=# create table t4(id int, set hll(5,-1));
+ERROR:  log2m = 5 is out of range, it should be in range 10 to 16, or set -1 as default
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** When inserting an HLL object to an HLL table, ensure that the parameters of the HLL type are the same as those of the inserted object. Otherwise, an error is reported.
+
+```sql
+-- Create an HLL table:
+mogdb=# create table t1(id integer, set hll(14));
+
+-- Insert an HLL object to a table. The insertion succeeds because parameter types are consistent.
+mogdb=# insert into t1 values (1, hll_empty(14,-1));
+
+-- Insert an HLL object to a table. The insertion fails because parameter types are inconsistent.
+mogdb=# insert into t1(id, set) values (1, hll_empty(14,5));
+ERROR:  log2explicit does not match: source is 5 and dest is 10
+```
+
+The following describes HLL application scenarios.
+
+- Scenario 1: "Hello World"
+
+  The following example shows how to use the HLL data type:
+
+  ```sql
+  -- Create a table with the HLL type:
+  mogdb=# create table helloworld (id integer, set hll);
+
+  -- Insert an empty HLL to the table:
+  mogdb=# insert into helloworld(id, set) values (1, hll_empty());
+
+  -- Add a hashed integer to the HLL:
+  mogdb=# update helloworld set set = hll_add(set, hll_hash_integer(12345)) where id = 1;
+
+  -- Add a hashed string to the HLL:
+  mogdb=# update helloworld set set = hll_add(set, hll_hash_text('hello world')) where id = 1;
+
+  -- Obtain the number of distinct values of the HLL:
+  mogdb=# select hll_cardinality(set) from helloworld where id = 1;
+   hll_cardinality
+  -----------------
+                 2
+  (1 row)
+
+  -- Delete the table.
+  mogdb=#  drop table helloworld;
+  ```
+
+- Scenario 2: Collect statistics about website visitors.
+
+  The following example shows how an HLL collects statistics on the number of users visiting a website within a period of time:
+
+  ```sql
+  -- Create a raw data table to show that a user has visited the website at a certain time:
+  mogdb=# create table facts (
+           date            date,
+           user_id         integer
+  );
+
+   -- Create a raw data table to show that a user has visited the website at a certain time:
+  mogdb=# insert into facts values ('2019-02-20', generate_series(1,100));
+  mogdb=# insert into facts values ('2019-02-21', generate_series(1,200));
+  mogdb=# insert into facts values ('2019-02-22', generate_series(1,300));
+  mogdb=# insert into facts values ('2019-02-23', generate_series(1,400));
+  mogdb=# insert into facts values ('2019-02-24', generate_series(1,500));
+  mogdb=# insert into facts values ('2019-02-25', generate_series(1,600));
+  mogdb=# insert into facts values ('2019-02-26', generate_series(1,700));
+  mogdb=# insert into facts values ('2019-02-27', generate_series(1,800));
+
+  -- Create another table and specify an HLL column:
+  mogdb=# create table daily_uniques (
+      date            date UNIQUE,
+      users           hll
+  );
+
+  -- Group data by date and insert the data into the HLL:
+  mogdb=# insert into daily_uniques(date, users)
+      select date, hll_add_agg(hll_hash_integer(user_id))
+      from facts
+      group by 1;
+
+  -- Calculate the numbers of users visiting the website every day:
+  mogdb=# select date, hll_cardinality(users) from daily_uniques order by date;
+      date    | hll_cardinality
+  ------------+------------------
+   2019-02-20 |              100
+   2019-02-21 | 200.217913059312
+   2019-02-22 |  301.76494508014
+   2019-02-23 | 400.862858326446
+   2019-02-24 | 502.626933349694
+   2019-02-25 | 601.922606454213
+   2019-02-26 | 696.602316769498
+   2019-02-27 | 798.111731634412
+  (8 rows)
+
+  -- Calculate the number of users who had visited the website in the week from February 20, 2019 to February 26, 2019:
+  mogdb=# select hll_cardinality(hll_union_agg(users)) from daily_uniques where date >= '2019-02-20'::date and date <= '2019-02-26'::date;
+   hll_cardinality
+  ------------------
+   702.941844662509
+  (1 row)
+
+  -- Calculate the number of users who had visited the website yesterday but have not visited the website today:
+  mogdb=# SELECT date, (#hll_union_agg(users) OVER two_days) - #users AS lost_uniques FROM daily_uniques WINDOW two_days AS (ORDER BY date ASC ROWS 1 PRECEDING);
+      date    | lost_uniques
+  ------------+--------------
+   2019-02-20 |            0
+   2019-02-21 |            0
+   2019-02-22 |            0
+   2019-02-23 |            0
+   2019-02-24 |            0
+   2019-02-25 |            0
+   2019-02-26 |            0
+   2019-02-27 |            0
+  (8 rows)
+
+  -- Delete the table.
+  mogdb=# drop table facts;
+  mogdb=# drop table daily_uniques;
+  ```
+
+- Scenario 3: The data to be inserted does not meet the requirements of the HLL data structure.
+
+  When inserting data into a column of the HLL type, ensure that the data meets the requirements of the HLL data structure. If the data does not meet the requirements after being parsed, an error will be reported. In the following example, **E\\1234** to be inserted does not meet the requirements of the HLL data structure after being parsed. As a result, an error is reported.
+
+  ```sql
+  mogdb=# create table test(id integer, set hll);
+  mogdb=# insert into test values(1, 'E\\1234');
+  ERROR:  not a hll type, size=6 is not enough
+  mogdb=# drop table test;
+  ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/13.0-array-types.md b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/13.0-array-types.md
new file mode 100644
index 0000000000000000000000000000000000000000..a2397ca3861bd0a6eecf8153977d412a146b50c0
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/13.0-array-types.md
@@ -0,0 +1,477 @@
+---
+title: Array Types
+summary: Array Types
+author: Guo Huan
+date: 2021-11-19
+---
+
+# Array Types
+
+MogDB allows columns of a table to be defined as variable-length multidimensional arrays. Arrays of any built-in or user-defined base type, enum type, or composite type can be created. Arrays of domains are not yet supported.
+
+## Declaration of Array Types
+
+To illustrate the use of array types, we create this table:
+
+```sql
+CREATE TABLE sal_emp (
+    name            text,
+    pay_by_quarter  integer[],
+    schedule        text[][]
+);
+```
+
+As shown, an array data type is named by appending square brackets (`[]`) to the data type name of the array elements. The above command will create a table named `sal_emp` with a column of type `text` (`name`), a one-dimensional array of type `integer` (`pay_by_quarter`), which represents the employee's salary by quarter, and a two-dimensional array of `text` (`schedule`), which represents the employee's weekly schedule.
+
+The syntax for `CREATE TABLE` allows the exact size of arrays to be specified, for example:
+
+```sql
+CREATE TABLE tictactoe (
+    squares   integer[3][3]
+);
+```
+
+However, the current implementation ignores any supplied array size limits, i.e., the behavior is the same as for arrays of unspecified length.
+
+The current implementation does not enforce the declared number of dimensions either. Arrays of a particular element type are all considered to be of the same type, regardless of size or number of dimensions. So, declaring the array size or number of dimensions in `CREATE TABLE` is simply documentation; it does not affect run-time behavior.
+
+An alternative syntax, which conforms to the SQL standard by using the keyword `ARRAY`, can be used for one-dimensional arrays. `pay_by_quarter` could have been defined as:
+
+```sql
+pay_by_quarter  integer ARRAY[4],
+```
+
+Or, if no array size is to be specified:
+
+```sql
+pay_by_quarter  integer ARRAY,
+```
+
+As before, however, MogDB does not enforce the size restriction in any case.
+
+## Array Value Input
+
+To write an array value as a literal constant, enclose the element values within curly braces and separate them by commas. (If you know C, this is not unlike the C syntax for initializing structures.) You can put double quotes around any element value, and must do so if it contains commas or curly braces. (More details appear below.) Thus, the general format of an array constant is the following:
+
+```sql
+'{ val1 delim val2 delim ... }'
+```
+
+where `delim` is the delimiter character for the type, as recorded in its `pg_type` entry. Among the standard data types provided in the MogDB distribution, all use a comma (`,`), except for type `box` which uses a semicolon (`;`). Each `val` is either a constant of the array element type, or a subarray. An example of an array constant is:
+
+```sql
+'{{1,2,3},{4,5,6},{7,8,9}}'
+```
+
+This constant is a two-dimensional, 3-by-3 array consisting of three subarrays of integers.
+
+To set an element of an array constant to NULL, write `NULL` for the element value. (Any upper- or lower-case variant of `NULL` will do.) If you want an actual string value "NULL", you must put double quotes around it.
+
+The constant is initially treated as a string and passed to the array input conversion routine. An explicit type specification might be necessary.
+
+Now we can show some `INSERT` statements:
+
+```sql
+INSERT INTO sal_emp
+    VALUES ('Bill',
+    '{10000, 10000, 10000, 10000}',
+    '{{"meeting", "lunch"}, {"training", "presentation"}}');
+
+INSERT INTO sal_emp
+    VALUES ('Carol',
+    '{20000, 25000, 25000, 25000}',
+    '{{"breakfast", "consulting"}, {"meeting", "lunch"}}');
+```
+
+The result of the previous two inserts looks like this:
+
+```sql
+SELECT * FROM sal_emp;
+ name  |      pay_by_quarter       |                 schedule
+-------+---------------------------+-------------------------------------------
+ Bill  | {10000,10000,10000,10000} | {{meeting,lunch},{training,presentation}}
+ Carol | {20000,25000,25000,25000} | {{breakfast,consulting},{meeting,lunch}}
+(2 rows)
+```
+
+Multidimensional arrays must have matching extents for each dimension. A mismatch causes an error, for example:
+
+```sql
+INSERT INTO sal_emp
+    VALUES ('Bill',
+    '{10000, 10000, 10000, 10000}',
+    '{{"meeting", "lunch"}, {"meeting"}}');
+ERROR:  multidimensional arrays must have array expressions with matching dimensions
+```
+
+The `ARRAY` constructor syntax can also be used:
+
+```sql
+INSERT INTO sal_emp
+    VALUES ('Bill',
+    ARRAY[10000, 10000, 10000, 10000],
+    ARRAY[['meeting', 'lunch'], ['training', 'presentation']]);
+
+INSERT INTO sal_emp
+    VALUES ('Carol',
+    ARRAY[20000, 25000, 25000, 25000],
+    ARRAY[['breakfast', 'consulting'], ['meeting', 'lunch']]);
+```
+
+Notice that the array elements are ordinary SQL constants or expressions; for instance, string literals are single quoted, instead of double quoted as they would be in an array literal.
+
+## Accessing Arrays
+
+Now, we can run some queries on the table. First, we show how to access a single element of an array. This query retrieves the names of the employees whose pay changed in the second quarter:
+
+```sql
+SELECT name FROM sal_emp WHERE pay_by_quarter[1] <> pay_by_quarter[2];
+
+ name
+-------
+ Carol
+(1 row)
+```
+
+The array subscript numbers are written within square brackets. By default MogDB uses a one-based numbering convention for arrays, that is, an array of `n` elements starts with `array[1]` and ends with `array[n]`.
+
+This query retrieves the third quarter pay of all employees:
+
+```sql
+SELECT pay_by_quarter[3] FROM sal_emp;
+
+ pay_by_quarter
+----------------
+          10000
+          25000
+(2 rows)
+```
+
+We can also access arbitrary rectangular slices of an array, or subarrays. An array slice is denoted by writing `lower-bound:upper-bound` for one or more array dimensions. For example, this query retrieves the first item on Bill's schedule for the first two days of the week:
+
+```sql
+SELECT schedule[1:2][1:1] FROM sal_emp WHERE name = 'Bill';
+
+        schedule
+------------------------
+ {{meeting},{training}}
+(1 row)
+```
+
+If any dimension is written as a slice, i.e., contains a colon, then all dimensions are treated as slices. Any dimension that has only a single number (no colon) is treated as being from 1 to the number specified. For example, `[2]` is treated as `[1:2]`, as in this example:
+
+```sql
+SELECT schedule[1:2][2] FROM sal_emp WHERE name = 'Bill';
+
+                 schedule
+-------------------------------------------
+ {{meeting,lunch},{training,presentation}}
+(1 row)
+```
+
+To avoid confusion with the non-slice case, it's best to use slice syntax for all dimensions, e.g., `[1:2][1:1]`, not `[2][1:1]`.
+
+It is possible to omit the `lower-bound` and/or `upper-bound` of a slice specifier; the missing bound is replaced by the lower or upper limit of the array's subscripts. For example:
+
+```sql
+SELECT schedule[:2][2:] FROM sal_emp WHERE name = 'Bill';
+
+        schedule
+------------------------
+ {{lunch},{presentation}}
+(1 row)
+
+SELECT schedule[:][1:1] FROM sal_emp WHERE name = 'Bill';
+
+        schedule
+------------------------
+ {{meeting},{training}}
+(1 row)
+```
+
+An array subscript expression will return null if either the array itself or any of the subscript expressions are null. Also, null is returned if a subscript is outside the array bounds (this case does not raise an error). For example, if `schedule` currently has the dimensions `[1:3][1:2]` then referencing `schedule[3][3]` yields NULL. Similarly, an array reference with the wrong number of subscripts yields a null rather than an error.
+
+An array slice expression likewise yields null if the array itself or any of the subscript expressions are null. However, in other cases such as selecting an array slice that is completely outside the current array bounds, a slice expression yields an empty (zero-dimensional) array instead of null. (This does not match non-slice behavior and is done for historical reasons.) If the requested slice partially overlaps the array bounds, then it is silently reduced to just the overlapping region instead of returning null.
+
+The current dimensions of any array value can be retrieved with the `array_dims` function:
+
+```sql
+SELECT array_dims(schedule) FROM sal_emp WHERE name = 'Carol';
+
+ array_dims
+------------
+ [1:2][1:2]
+(1 row)
+```
+
+`array_dims` produces a `text` result, which is convenient for people to read but perhaps inconvenient for programs. Dimensions can also be retrieved with `array_upper` and `array_lower`, which return the upper and lower bound of a specified array dimension, respectively:
+
+```sql
+SELECT array_upper(schedule, 1) FROM sal_emp WHERE name = 'Carol';
+
+ array_upper
+-------------
+           2
+(1 row)
+```
+
+`array_length` will return the length of a specified array dimension:
+
+```sql
+SELECT array_length(schedule, 1) FROM sal_emp WHERE name = 'Carol';
+
+ array_length
+--------------
+            2
+(1 row)
+```
+
+`cardinality` returns the total number of elements in an array across all dimensions. It is effectively the number of rows a call to `unnest` would yield:
+
+```sql
+SELECT cardinality(schedule) FROM sal_emp WHERE name = 'Carol';
+
+ cardinality
+-------------
+           4
+(1 row)
+```
+
+## Modifying Arrays
+
+An array value can be replaced completely:
+
+```sql
+UPDATE sal_emp SET pay_by_quarter = '{25000,25000,27000,27000}'
+    WHERE name = 'Carol';
+```
+
+or using the `ARRAY` expression syntax:
+
+```sql
+UPDATE sal_emp SET pay_by_quarter = ARRAY[25000,25000,27000,27000]
+    WHERE name = 'Carol';
+```
+
+An array can also be updated at a single element:
+
+```sql
+UPDATE sal_emp SET pay_by_quarter[4] = 15000
+    WHERE name = 'Bill';
+```
+
+or updated in a slice:
+
+```sql
+UPDATE sal_emp SET pay_by_quarter[1:2] = '{27000,27000}'
+    WHERE name = 'Carol';
+```
+
+The slice syntaxes with omitted `lower-bound` and/or `upper-bound` can be used too, but only when updating an array value that is not NULL or zero-dimensional (otherwise, there is no existing subscript limit to substitute).
+
+A stored array value can be enlarged by assigning to elements not already present. Any positions between those previously present and the newly assigned elements will be filled with nulls. For example, if array `myarray` currently has 4 elements, it will have six elements after an update that assigns to `myarray[6]`; `myarray[5]` will contain null. Currently, enlargement in this fashion is only allowed for one-dimensional arrays, not multidimensional arrays.
+
+Subscripted assignment allows creation of arrays that do not use one-based subscripts. For example one might assign to `myarray[-2:7]` to create an array with subscript values from -2 to 7.
+
+New array values can also be constructed using the concatenation operator, `||`:
+
+```sql
+SELECT ARRAY[1,2] || ARRAY[3,4];
+ ?column?
+-----------
+ {1,2,3,4}
+(1 row)
+
+SELECT ARRAY[5,6] || ARRAY[[1,2],[3,4]];
+      ?column?
+---------------------
+ {{5,6},{1,2},{3,4}}
+(1 row)
+```
+
+The concatenation operator allows a single element to be pushed onto the beginning or end of a one-dimensional array. It also accepts two `N`-dimensional arrays, or an `N`-dimensional and an `N+1`-dimensional array.
+
+When a single element is pushed onto either the beginning or end of a one-dimensional array, the result is an array with the same lower bound subscript as the array operand. For example:
+
+```sql
+SELECT array_dims(1 || '[0:1]={2,3}'::int[]);
+ array_dims
+------------
+ [0:2]
+(1 row)
+
+SELECT array_dims(ARRAY[1,2] || 3);
+ array_dims
+------------
+ [1:3]
+(1 row)
+```
+
+When two arrays with an equal number of dimensions are concatenated, the result retains the lower bound subscript of the left-hand operand's outer dimension. The result is an array comprising every element of the left-hand operand followed by every element of the right-hand operand. For example:
+
+```sql
+SELECT array_dims(ARRAY[1,2] || ARRAY[3,4,5]);
+ array_dims
+------------
+ [1:5]
+(1 row)
+
+SELECT array_dims(ARRAY[[1,2],[3,4]] || ARRAY[[5,6],[7,8],[9,0]]);
+ array_dims
+------------
+ [1:5][1:2]
+(1 row)
+```
+
+When an `N`-dimensional array is pushed onto the beginning or end of an `N+1`-dimensional array, the result is analogous to the element-array case above. Each `N`-dimensional sub-array is essentially an element of the `N+1`-dimensional array's outer dimension. For example:
+
+```sql
+SELECT array_dims(ARRAY[1,2] || ARRAY[[3,4],[5,6]]);
+ array_dims
+------------
+ [1:3][1:2]
+(1 row)
+```
+
+An array can also be constructed by using the functions `array_prepend`, `array_append`, or `array_cat`. The first two only support one-dimensional arrays, but `array_cat` supports multidimensional arrays. Some examples:
+
+```sql
+SELECT array_prepend(1, ARRAY[2,3]);
+ array_prepend
+---------------
+ {1,2,3}
+(1 row)
+
+SELECT array_append(ARRAY[1,2], 3);
+ array_append
+--------------
+ {1,2,3}
+(1 row)
+
+SELECT array_cat(ARRAY[1,2], ARRAY[3,4]);
+ array_cat
+-----------
+ {1,2,3,4}
+(1 row)
+
+SELECT array_cat(ARRAY[[1,2],[3,4]], ARRAY[5,6]);
+      array_cat
+---------------------
+ {{1,2},{3,4},{5,6}}
+(1 row)
+
+SELECT array_cat(ARRAY[5,6], ARRAY[[1,2],[3,4]]);
+      array_cat
+---------------------
+ {{5,6},{1,2},{3,4}}
+```
+
+In simple cases, the concatenation operator discussed above is preferred over direct use of these functions. However, because the concatenation operator is overloaded to serve all three cases, there are situations where use of one of the functions is helpful to avoid ambiguity. For example consider:
+
+```sql
+SELECT ARRAY[1, 2] || '{3, 4}';  -- the untyped literal is taken as an array
+ ?column?
+-----------
+ {1,2,3,4}
+
+SELECT ARRAY[1, 2] || '7';                 -- so is this one
+ERROR:  malformed array literal: "7"
+
+SELECT ARRAY[1, 2] || NULL;                -- so is an undecorated NULL
+ ?column?
+----------
+ {1,2}
+(1 row)
+
+SELECT array_append(ARRAY[1, 2], NULL);    -- this might have been meant
+ array_append
+--------------
+ {1,2,NULL}
+```
+
+In the examples above, the parser sees an integer array on one side of the concatenation operator, and a constant of undetermined type on the other. The heuristic it uses to resolve the constant's type is to assume it's of the same type as the operator's other input - in this case, integer array. So the concatenation operator is presumed to represent `array_cat`, not `array_append`. When that's the wrong choice, it could be fixed by casting the constant to the array's element type; but explicit use of `array_append` might be a preferable solution.
+
+## Searching in Arrays
+
+To search for a value in an array, each value must be checked. This can be done manually, if you know the size of the array. For example:
+
+```sql
+SELECT * FROM sal_emp WHERE pay_by_quarter[1] = 10000 OR
+                            pay_by_quarter[2] = 10000 OR
+                            pay_by_quarter[3] = 10000 OR
+                            pay_by_quarter[4] = 10000;
+```
+
+However, this quickly becomes tedious for large arrays, and is not helpful if the size of the array is unknown. The above query could be replaced by:
+
+```sql
+SELECT * FROM sal_emp WHERE 10000 = ANY (pay_by_quarter);
+```
+
+In addition, you can find rows where the array has all values equal to 10000 with:
+
+```sql
+SELECT * FROM sal_emp WHERE 10000 = ALL (pay_by_quarter);
+```
+
+Alternatively, the `generate_subscripts` function can be used. For example:
+
+```sql
+SELECT * FROM
+   (SELECT pay_by_quarter,
+           generate_subscripts(pay_by_quarter, 1) AS s
+      FROM sal_emp) AS foo
+ WHERE pay_by_quarter[s] = 10000;
+```
+
+You can also search an array using the `&&` operator, which checks whether the left operand overlaps with the right operand. For instance:
+
+```sql
+SELECT * FROM sal_emp WHERE pay_by_quarter && ARRAY[10000];
+```
+
+This and other array operators are further described in [Array Functions and Operators](15-array-functions-and-operators).
+
+You can also search for specific values in an array using the `array_position` and `array_positions` functions. The former returns the subscript of the first occurrence of a value in an array; the latter returns an array with the subscripts of all occurrences of the value in the array. For example:
+
+```sql
+SELECT array_position(ARRAY['sun','mon','tue','wed','thu','fri','sat'], 'mon');
+ array_positions
+-----------------
+ 2
+
+SELECT array_positions(ARRAY[1, 4, 3, 1, 3, 4, 2, 1], 1);
+ array_positions
+-----------------
+ {1,4,8}
+```
+
+> **Tip:** Arrays are not sets; searching for specific array elements can be a sign of database misdesign. Consider using a separate table with a row for each item that would be an array element. This will be easier to search, and is likely to scale better for a large number of elements.
+
+## Array Input and Output Syntax
+
+The external text representation of an array value consists of items that are interpreted according to the I/O conversion rules for the array's element type, plus decoration that indicates the array structure. The decoration consists of curly braces (`{` and `}`) around the array value plus delimiter characters between adjacent items. The delimiter character is usually a comma (`,`) but can be something else: it is determined by the `typdelim` setting for the array's element type. Among the standard data types provided in the MogDB distribution, all use a comma, except for type `box`, which uses a semicolon (`;`). In a multidimensional array, each dimension (row, plane, cube, etc.) gets its own level of curly braces, and delimiters must be written between adjacent curly-braced entities of the same level.
+
+The array output routine will put double quotes around element values if they are empty strings, contain curly braces, delimiter characters, double quotes, backslashes, or white space, or match the word `NULL`. Double quotes and backslashes embedded in element values will be backslash-escaped. For numeric data types it is safe to assume that double quotes will never appear, but for textual data types one should be prepared to cope with either the presence or absence of quotes.
+
+By default, the lower bound index value of an array's dimensions is set to one. To represent arrays with other lower bounds, the array subscript ranges can be specified explicitly before writing the array contents. This decoration consists of square brackets (`[]`) around each array dimension's lower and upper bounds, with a colon (`:`) delimiter character in between. The array dimension decoration is followed by an equal sign (`=`). For example:
+
+```sql
+SELECT f1[1][-2][3] AS e1, f1[1][-1][5] AS e2
+ FROM (SELECT '[1:1][-2:-1][3:5]={{{1,2,3},{4,5,6}}}'::int[] AS f1) AS ss;
+
+ e1 | e2
+----+----
+  1 |  6
+(1 row)
+```
+
+The array output routine will include explicit dimensions in its result only when there are one or more lower bounds different from one.
+
+If the value written for an element is `NULL` (in any case variant), the element is taken to be NULL. The presence of any quotes or backslashes disables this and allows the literal string value "NULL" to be entered. Also, for backward compatibility with pre-versions of MogDB, the [array_nulls](1-compatibility-with-earlier-versions) configuration parameter can be turned `off` to suppress recognition of `NULL` as a NULL.
+
+As shown previously, when writing an array value you can use double quotes around any individual array element. You must do so if the element value would otherwise confuse the array-value parser. For example, elements containing curly braces, commas (or the data type's delimiter character), double quotes, backslashes, or leading or trailing whitespace must be double-quoted. Empty strings and strings matching the word `NULL` must be quoted, too. To put a double quote or backslash in a quoted array element value, precede it with a backslash. Alternatively, you can avoid quotes and use backslash-escaping to protect all data characters that would otherwise be taken as array syntax.
+
+You can add whitespace before a left brace or after a right brace. You can also add whitespace before or after any individual item string. In all of these cases the whitespace will be ignored. However, whitespace within double-quoted elements, or surrounded on both sides by non-whitespace characters of an element, is not ignored.
+
+> **Tip:** The `ARRAY` constructor syntax is often easier to work with than the array-literal syntax when writing array values in SQL commands. In `ARRAY`, individual element values are written the same way they would be written when not members of an array.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/13.1-range.md b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/13.1-range.md
new file mode 100644
index 0000000000000000000000000000000000000000..b448396489aa1c43ba214f1b6024e39fdd6683a5
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/13.1-range.md
@@ -0,0 +1,163 @@
+---
+title: Range
+summary: Range
+author: Zhang Cuiping
+date: 2021-10-25
+---
+
+# Range
+
+A range type is a data type that represents the range of a value of an element type (called the subtype of a range). For example, the range of timestamp may be used to express a time range in which a conference room is reserved. In this case, the data type is tsrange and timestamp is the subtype. The subtype must have an overall order so that the element value can be clearly specified within a range, before, or after.
+
+Range types are useful because they can express multiple element values in a single range value and can clearly express concepts such as range overlapping. The time and date range used for scheduling is the best example, as the range of an instrument are also examples of range type.
+
+## Built-in Range
+
+The following built-in ranges are available:
+
+- int4range: integer range.
+- int8range: bigint range.
+- numrange: numeric range.
+- tsrange: range of timestamp without the time zone.
+- tstzrange: range of timestamp with the time zone
+- daterange: date range.
+
+In addition, you can define your own range types. For details, see [CREATE TYPE](67-CREATE-TYPE).
+
+## Example
+
+```sql
+CREATE TABLE reservation (room int, during tsrange);
+INSERT INTO reservation VALUES (1108, '[2010-01-01 14:30, 2010-01-01 15:30)');
+-- Inclusion
+SELECT int4range(10, 20) @> 3;
+-- Overlapping
+SELECT numrange(11.1, 22.2) && numrange(20.0, 30.0);
+-- Upper bound extraction
+SELECT upper(int8range(15, 25));
+-- Intersection set
+SELECT int4range(10, 20) * int4range(15, 25);
+-- Empty range
+SELECT isempty(numrange(1, 5));
+```
+
+See the complete list of operators and functions on a range type in [Range Functions and Operators](16-range-functions-and-operators).
+
+## Including and Excluding Bounds
+
+Each non-empty range has two bounds, a lower bound and an upper bound. All values between the upper and lower bounds are included in the range. An inclusion bound means that the bound value itself is included in the range, while an exclusion bound means that the bound value is not included in the range.
+
+In a textual form of a range, the inclusion lower bound is expressed as "[" and an exclusion lower bound is expressed as "(". Similarly, one containing the upper bound is expressed as "]" and one excluding the upper bound is expressed as ")" (for details, see [Range Input/Output](range-inputoutput)).
+
+The lower_inc and upper_inc functions test the upper and lower bounds of a range value, respectively.
+
+## Infinite (Unbounded) Range
+
+When the lower bound of a range is unbounded, it means that all values less than the upper bound are included in the range, for example, (,3] meaning all values less than the upper bound 3 are included in the range. Similarly, when the upper bound of a range is unbounded, all values greater than the upper bound are included in the range. When both the upper and lower bounds are unbounded, all values of the element type are considered within the range. The missing bounds are automatically converted to exclusions, for example, [,] is converted to (,). You can think of these missing values as positive infinity or negative infinity, but they are special range type values and are considered to be positive and negative infinity values that go beyond any range element type.
+
+Element types with the infinity values can be used as explicit bound values. For example, in the timestamp range, [today, infinity) does not include a special timestamp value infinity.
+
+The lower_inf and upper_inf functions test the infinite upper and lower bounds of a range, respectively.
+
+## Range Input/Output
+
+The input of a range value must follow one of the following formats:
+
+```sql
+(lower-bound, upper-bound)
+(lower-bound, upper-bound]
+[lower-bound, upper-bound)
+[lower-bound, upper-bound]
+Empty
+```
+
+Parentheses () or square brackets [] indicate whether the upper and lower bounds are excluded or included. Note that the last format is empty, which represents an empty range (a range that does not contain values).
+
+The value of *lower-bound* can be a valid input character string of the subtype or null, indicating that there is no lower bound. Similarly, *upper-bound* can be a valid input character string of the subtype or null, indicating that there is no upper bound.
+
+Each bound value can be referenced using the quotation marks("") character. This is necessary if the bounds value contains parentheses (), square brackets [], commas (,), quotation marks (""), or backslashes (), because otherwise those characters will be considered part of the range syntax. To put the quotation mark or backslash in a referenced bound value, put a backslash in front of it (and a pair of double quotation marks in its quoted bound value represents one quotation mark character, which is similar to the single quotation mark rule in SQL character strings). In addition, you can avoid referencing and use backslash escapes to protect all data characters, otherwise they will be used as part of the return syntax. Also, if you want to write a bound value that is an empty string, write **""**, indicating infinite bounds.
+
+Spaces are allowed before and after a range value, but any space between parentheses() or square brackets[] is used as part of the upper or lower bound value (depending on the element type, the space may or may not represent a value).
+
+Examples:
+
+```sql
+-- 3 is included, 7 is not included, and all values between 3 and 7 are included.
+SELECT '[3,7)'::int4range;
+-- Neither 3 nor 7 is included, but all values between them are included.
+SELECT '(3,7)'::int4range;
+-- Only value 4 is included.
+SELECT '[4,4]'::int4range;
+-- Exclude any value (and will be normalized to empty)
+SELECT '[4,4)'::int4range;
+```
+
+## Constructing Range
+
+Each range type has a constructor function with the same name. Using constructor functions is often more convenient than writing a range literal constant because it avoids extra references to bound values. Constructor functions accept two or three parameters. Two parameters form a range in the standard form, where the lower bound is included and the upper bound is excluded, and three parameters form a range according to the bound specified by the third parameter. The third parameter must be one of the following character strings: (), (], [], or []. For example:
+
+```sql
+-- The complete form is: lower bound, upper bound, and textual parameters indicating the inclusion/exclusion of bounds.
+SELECT numrange(1.0, 14.0, '(]');
+-- If the third parameter is ignored, it is assumed to be '[)'.
+SELECT numrange(1.0, 14.0);
+-- Although '(]' is specified here, the value will be converted to the standard format when displayed, because int8range is a discrete range type (see below).
+SELECT int8range(1, 14, '(]');
+-- Using NULL for a bound causes the range to be unbounded on that side.
+SELECT numrange(NULL, 2.2);
+```
+
+## Discrete Range
+
+A range element type has a well-defined "step" such as integer or date. In these types, if there is no valid value between two elements, they can be said to be adjacent. This is in contrast to a continuous range in which other element values can always be identified between two given values. For example, a range above the numeric type is continuous, and the range of timestamp is also continuous. (Although timestamp has limited precision and can be considered as discrete in theory, it is better to consider it as continuous because the step is not normally considered.)
+
+Another way to consider discrete range types is to have a clear "next" or "previous" value for each element value. With this idea in mind, you can switch between inclusion and exclusion expressions of a range bound by replacing it with the original given next or previous element value. For example, in an integer range type, [4,8] and (3,9) represent the same set of values, but not for numeric ranges.
+
+A discrete range type should have a *regularization* function that knows the expected step size of the element type. The regularization function can convert the equivalents of the range type to the same expression, in particular consistent with the inclusion or exclusion bounds. If you do not specify a regularization function, ranges with different formats will always be considered as unequal, even if they actually express the same set of values.
+
+The built-in range types int4range, int8range, and daterange use a regularized form that includes the lower bound and excludes the upper bound, that is, [). However, user-defined range types can use other conventions.
+
+## Defining New Range
+
+Users can define their own range types. The most common reason is to use the range on the subtype that is not provided in the built-in range type. For example, to create the range type subtype float8, run the following command:
+
+```sql
+CREATE TYPE floatrange AS RANGE (
+     subtype = float8,
+     subtype_diff = float8mi
+);
+SELECT '[1.234, 5.678]'::floatrange;
+```
+
+Because float8 does not have a meaningful "step", we did not define a regularization function in this example.
+
+Defining your own range type also allows you to specify a different subtype B-tree operator class or collection to change the sort order to determine which values fall within the given range.
+
+If the subtype is considered to have a discrete value instead of a continuous value, the **CREATE TYPE** command should specify a canonical function. The regularization function receives an input range value and must return an equivalent range value that may have different bounds and formats. For two ranges, for example, [1, 7] and [1, 8) that represent the same value set, the output must be the same. There is no relationship between choosing which expression to use as the regularization function, as long as two values of equal value in different formats can always be mapped to the same value in the same format. In addition to adjusting the inclusion/exclusion bound format, if the expected compensation is larger than the subtype can store, a regularization function may round the bound value. For example, a range type above a timestamp might be defined as having a one-hour epoch, so the regularization function might need to round off bounds that are not multiples of an hour, or might throw an error directly.
+
+In addition, any range type intended to be used with a GiST or SP-GiST index should define a subtype difference or subtype_diff function (the index can still work without subtype_diff, but may be less efficient than when a difference function is provided). The subtype difference function uses two subtype input values and returns a difference expressed as a float8 value (X minus Y). In the example above, we can use functions under the regular float8 subtraction operator. However, for any other subtype, some type conversion may be required. There may also be a need for innovative ideas on how to express differences as numbers. For maximum extensibility, the subtype_diff function should agree with the sort order of the selected operator class and sort rules. That is, if the first parameter of the sort order is greater than the second parameter, the result should be a positive value.
+
+The following is an example of a less simplified subtype_diff function:
+
+```sql
+CREATE FUNCTION time_subtype_diff(x time, y time) RETURNS float8 AS 'SELECT EXTRACT(EPOCH FROM (x - y))' LANGUAGE sql STRICT IMMUTABLE;
+CREATE TYPE timerange AS RANGE (
+     subtype = time,
+     subtype_diff = time_subtype_diff
+ );
+SELECT '[11:10, 23:00]'::timerange;
+```
+
+For details about how to create a range type, see [CREATE TYPE](67-CREATE-TYPE).
+
+## Index
+
+GiST and SP-GiST indexes can be created for table columns of the range type. For example, to create a GiST index, run the following command:
+
+```sql
+CREATE INDEX reservation_idx ON reservation USING GIST (during);
+```
+
+A GiST or SP-GiST index can accelerate queries involving the following range operators: =, &&, &lt;@, @&gt;, &lt;&lt;, &gt;&gt;, -|-, &&lt;, and &&gt; (see [Range Functions and Operators](16-range-functions-and-operators)).
+
+In addition, the B-tree and hash index can be created on table columns of the range type. For these index types, basically the only useful range operation is equivalence. Using the corresponding &lt; and &gt; operators, there is a B-tree sort oder for range value definitions, but that order is fairly arbitrary and is often less useful in the reality. The B-tree and hash support for range types is primarily designed to allow sorting and hashing within a query, rather than creating an index.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/14-object-identifier-types.md b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/14-object-identifier-types.md
new file mode 100644
index 0000000000000000000000000000000000000000..7c329d7d79719cc638f6fbe195c26ba00c352a25
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/14-object-identifier-types.md
@@ -0,0 +1,90 @@
+---
+title: OID Types
+summary: OID Types
+author: Guo Huan
+date: 2021-04-06
+---
+
+# OID Types
+
+OIDs are used internally by MogDB as primary keys for various system catalogs. OIDs are not added to user-created tables by the system. The **OID** type represents an object identifier.
+
+The **OID** type is currently implemented as an unsigned four-byte integer. So, using a user-created table's **OID** column as a primary key is discouraged.
+
+**Table 1** Object identifier types
+
+| Name          | Reference    | Description                                                  | Example                               |
+| :------------ | :----------- | :----------------------------------------------------------- | :------------------------------------ |
+| OID           | N/A          | Numeric object identifier                                    | 564182                                |
+| CID           | N/A          | A command identifier. This is the data type of the system columns **cmin** and **cmax**. Command identifiers are 32-bit quantities. | N/A                                   |
+| XID           | N/A          | A transaction identifier. This is the data type of the system columns **xmin** and **xmax**. Transaction identifiers are 64-bit quantities. | N/A                                   |
+| TID           | N/A          | A row identifier. This is the data type of the system column **ctid**. A row ID is a pair (block number, tuple index within block) that identifies the physical location of the row within its table. | N/A                                   |
+| REGCONFIG     | pg_ts_config | Text search configuration                                    | english                               |
+| REGDICTIONARY | pg_ts_dict   | Text search dictionary                                       | simple                                |
+| REGOPER       | pg_operator  | Operator name                                                | N/A                                   |
+| REGOPERATOR   | pg_operator  | Operator with argument types                                 | *(integer,integer) or -(NONE,integer) |
+| REGPROC       | pg_proc      | Function name                                                | sum                                   |
+| REGPROCEDURE  | pg_proc      | Function with argument types                                 | sum(int4)                             |
+| REGCLASS      | pg_class     | Relation name                                                | pg_type                               |
+| REGTYPE       | pg_type      | Data type name                                               | integer                               |
+
+The **OID** type is used for a column in the database system catalog.
+
+Example:
+
+```sql
+mogdb=# SELECT oid FROM pg_class WHERE relname = 'pg_type';
+ oid
+------
+ 1247
+(1 row)
+```
+
+The alias type for **OID** is **REGCLASS** which allows simplified search for **OID** values.
+
+Example:
+
+```sql
+mogdb=# SELECT attrelid,attname,atttypid,attstattarget FROM pg_attribute WHERE attrelid = 'pg_type'::REGCLASS;
+ attrelid |  attname   | atttypid | attstattarget
+----------+------------+----------+---------------
+     1247 | xc_node_id     |       23 |             0
+     1247 | tableoid       |       26 |             0
+     1247 | cmax           |       29 |             0
+     1247 | xmax           |       28 |             0
+     1247 | cmin           |       29 |             0
+     1247 | xmin           |       28 |             0
+     1247 | oid            |       26 |             0
+     1247 | ctid           |       27 |             0
+     1247 | typname        |       19 |            -1
+     1247 | typnamespace   |       26 |            -1
+     1247 | typowner       |       26 |            -1
+     1247 | typlen         |       21 |            -1
+     1247 | typbyval       |       16 |            -1
+     1247 | typtype        |       18 |            -1
+     1247 | typcategory    |       18 |            -1
+     1247 | typispreferred |       16 |            -1
+     1247 | typisdefined   |       16 |            -1
+     1247 | typdelim       |       18 |            -1
+     1247 | typrelid       |       26 |            -1
+     1247 | typelem        |       26 |            -1
+     1247 | typarray       |       26 |            -1
+     1247 | typinput       |       24 |            -1
+     1247 | typoutput      |       24 |            -1
+     1247 | typreceive     |       24 |            -1
+     1247 | typsend        |       24 |            -1
+     1247 | typmodin       |       24 |            -1
+     1247 | typmodout      |       24 |            -1
+     1247 | typanalyze     |       24 |            -1
+     1247 | typalign       |       18 |            -1
+     1247 | typstorage     |       18 |            -1
+     1247 | typnotnull     |       16 |            -1
+     1247 | typbasetype    |       26 |            -1
+     1247 | typtypmod      |       23 |            -1
+     1247 | typndims       |       23 |            -1
+     1247 | typcollation   |       26 |            -1
+     1247 | typdefaultbin  |      194 |            -1
+     1247 | typdefault     |       25 |            -1
+     1247 | typacl         |     1034 |            -1
+(38 rows)
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/15-pseudo-types.md b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/15-pseudo-types.md
new file mode 100644
index 0000000000000000000000000000000000000000..36dffb9cdffc9b5d375fc9b4a6bde128b922a67d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/15-pseudo-types.md
@@ -0,0 +1,65 @@
+---
+title: Pseudo-Types
+summary: Pseudo-Types
+author: Guo Huan
+date: 2021-04-06
+---
+
+# Pseudo-Types
+
+MogDB type system contains a number of special-purpose entries that are collectively called pseudo-types. A pseudo-type cannot be used as a column data type, but it can be used to declare a function's argument or result type.
+
+Each of the available pseudo-types is useful in situations where a function's behavior does not correspond to simply taking or returning a value of a specific SQL data type. Table 1 lists all pseudo-types.
+
+**Table 1** Pseudo-types
+
+| Name             | Description                                                  |
+| :--------------- | :----------------------------------------------------------- |
+| any              | Indicates that a function accepts any input data type.       |
+| anyelement       | Indicates that a function accepts any data type.             |
+| anyarray         | Indicates that a function accepts any array data type.       |
+| anynonarray      | Indicates that a function accepts any non-array data type.   |
+| anyenum          | Indicates that a function accepts any enum data type.        |
+| anyrange         | Indicates that a function accepts any range data type.       |
+| cstring          | Indicates that a function accepts or returns a null-terminated C string. |
+| internal         | Indicates that a function accepts or returns a server-internal data type. |
+| language_handler | Indicates that a procedural language call handler is declared to return **language_handler**. |
+| fdw_handler      | Indicates that a foreign-data wrapper handler is declared to return **fdw_handler**. |
+| record           | Identifies a function returning an unspecified row type.     |
+| trigger          | Indicates that a trigger function is declared to return **trigger**. |
+| void             | Indicates that a function returns no value.                  |
+| opaque           | Indicates an obsolete type name that formerly served all the above purposes. |
+
+Functions coded in C (whether built in or dynamically loaded) can be declared to accept or return any of these pseudo data types. It is up to the function author to ensure that the function will behave safely when a pseudo-type is used as an argument type.
+
+Functions coded in procedural languages can use pseudo-types only as allowed by their implementation languages. At present the procedural languages all forbid use of a pseudo-type as argument type, and allow only **void** and **record** as a result type. Some also support polymorphic functions using the **anyelement**, **anyarray**, **anynonarray**, **anyenum**, and **anyrange** types.
+
+The **internal** pseudo-type is used to declare functions that are meant only to be called internally by the database system, and not by direct invocation in an SQL query. If a function has at least one **internal**-type argument then it cannot be called from SQL. You are advised not to create any function that is declared to return internal unless it has at least one **internal** argument.
+
+Example:
+
+```sql
+-- Create a table.
+mogdb=# create table t1 (a int);
+
+-- Insert two data records.
+mogdb=# insert into t1 values(1),(2);
+
+-- Create the showall() function:
+mogdb=# CREATE OR REPLACE FUNCTION showall() RETURNS SETOF record
+AS $$ SELECT count(*) from t1; $$
+LANGUAGE SQL;
+
+-- Invoke the showall() function:
+mogdb=# SELECT showall();
+ showall
+---------
+ (2)
+(1 row)
+
+-- Delete the function:
+mogdb=# DROP FUNCTION showall();
+
+-- Delete the table.
+mogdb=# drop table t1;
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/16-data-types-supported-by-column-store-tables.md b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/16-data-types-supported-by-column-store-tables.md
new file mode 100644
index 0000000000000000000000000000000000000000..7116b32eb96c3ff88d4c90bb79fefaefcb313dfb
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/16-data-types-supported-by-column-store-tables.md
@@ -0,0 +1,219 @@
+---
+title: Data Types Supported by Column-store Tables
+summary: Data Types Supported by Column-store Tables
+author: Guo Huan
+date: 2021-04-06
+---
+
+# Data Types Supported by Column-store Tables
+
+Table 1 lists the data types supported by column-store tables.
+
+**Table 1** Data types supported by column-store tables
+
+<table><thead align="left"><tr id="zh-cn_topic_0237121962_row829010145541"><th class="cellrowborder" id="mcps1.2.5.1.1"><p id="zh-cn_topic_0237121962_p182901514135411"><a name="zh-cn_topic_0237121962_p182901514135411"></a><a name="zh-cn_topic_0237121962_p182901514135411"></a>Category</p>
+</th>
+<th class="cellrowborder" id="mcps1.2.5.1.2"><p id="zh-cn_topic_0237121962_p15290191416548"><a name="zh-cn_topic_0237121962_p15290191416548"></a><a name="zh-cn_topic_0237121962_p15290191416548"></a>Data Type</p>
+</th>
+<th class="cellrowborder" id="mcps1.2.5.1.3"><p id="zh-cn_topic_0237121962_p16290114125415"><a name="zh-cn_topic_0237121962_p16290114125415"></a><a name="zh-cn_topic_0237121962_p16290114125415"></a>Length</p>
+</th>
+<th class="cellrowborder" valign="top" id="mcps1.2.5.1.4"><p id="zh-cn_topic_0237121962_p10290131475415"><a name="zh-cn_topic_0237121962_p10290131475415"></a><a name="zh-cn_topic_0237121962_p10290131475415"></a>Supported or Not</p>
+</th>
+</tr>
+</thead>
+<tbody><tr id="zh-cn_topic_0237121962_row729018142548"><td class="cellrowborder" rowspan="10" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p4290171415543"><a name="zh-cn_topic_0237121962_p4290171415543"></a><a name="zh-cn_topic_0237121962_p4290171415543"></a>Numeric Types</p>
+</td>
+<td class="cellrowborder" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p142901314175410"><a name="zh-cn_topic_0237121962_p142901314175410"></a><a name="zh-cn_topic_0237121962_p142901314175410"></a>smallint</p>
+</td>
+<td class="cellrowborder" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p1629011148541"><a name="zh-cn_topic_0237121962_p1629011148541"></a><a name="zh-cn_topic_0237121962_p1629011148541"></a>2</p>
+</td>
+<td class="cellrowborder" headers="mcps1.2.5.1.4 "><p id="zh-cn_topic_0237121962_p729031415540">Supported</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row17290191415415"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p12290101405412"><a name="zh-cn_topic_0237121962_p12290101405412"></a><a name="zh-cn_topic_0237121962_p12290101405412"></a>integer</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p929001420541"><a name="zh-cn_topic_0237121962_p929001420541"></a><a name="zh-cn_topic_0237121962_p929001420541"></a>4</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p17290114165413"><a name="zh-cn_topic_0237121962_p17290114165413"></a><a name="zh-cn_topic_0237121962_p17290114165413"></a>Supported</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row329091415410"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p1929011418548"><a name="zh-cn_topic_0237121962_p1929011418548"></a><a name="zh-cn_topic_0237121962_p1929011418548"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p1129018145546"><a name="zh-cn_topic_0237121962_p1129018145546"></a><a name="zh-cn_topic_0237121962_p1129018145546"></a>8</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p529021435416"><a name="zh-cn_topic_0237121962_p529021435416"></a><a name="zh-cn_topic_0237121962_p529021435416"></a>Supported</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row6290161445410"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p16290614175414"><a name="zh-cn_topic_0237121962_p16290614175414"></a><a name="zh-cn_topic_0237121962_p16290614175414"></a>decimal</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p13290151417543"><a name="zh-cn_topic_0237121962_p13290151417543"></a><a name="zh-cn_topic_0237121962_p13290151417543"></a>-1</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p1029031418543"><a name="zh-cn_topic_0237121962_p1029031418543"></a><a name="zh-cn_topic_0237121962_p1029031418543"></a>Supported</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row629041410543"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p1129031485418"><a name="zh-cn_topic_0237121962_p1129031485418"></a><a name="zh-cn_topic_0237121962_p1129031485418"></a>numeric</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p1329071465410"><a name="zh-cn_topic_0237121962_p1329071465410"></a><a name="zh-cn_topic_0237121962_p1329071465410"></a>-1</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p1629001435418"><a name="zh-cn_topic_0237121962_p1629001435418"></a><a name="zh-cn_topic_0237121962_p1629001435418"></a>Supported</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row1290114155417"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p1290101435412"><a name="zh-cn_topic_0237121962_p1290101435412"></a><a name="zh-cn_topic_0237121962_p1290101435412"></a>real</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p1729012143548"><a name="zh-cn_topic_0237121962_p1729012143548"></a><a name="zh-cn_topic_0237121962_p1729012143548"></a>4</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p15290514175418"><a name="zh-cn_topic_0237121962_p15290514175418"></a><a name="zh-cn_topic_0237121962_p15290514175418"></a>Supported</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row1829015147548"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p6290101411549"><a name="zh-cn_topic_0237121962_p6290101411549"></a><a name="zh-cn_topic_0237121962_p6290101411549"></a>double precision</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p16290114165416"><a name="zh-cn_topic_0237121962_p16290114165416"></a><a name="zh-cn_topic_0237121962_p16290114165416"></a>8</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p72901414155413"><a name="zh-cn_topic_0237121962_p72901414155413"></a><a name="zh-cn_topic_0237121962_p72901414155413"></a>Supported</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row11290201411546"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p142901014115417"><a name="zh-cn_topic_0237121962_p142901014115417"></a><a name="zh-cn_topic_0237121962_p142901014115417"></a>smallserial</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p14290141414543"><a name="zh-cn_topic_0237121962_p14290141414543"></a><a name="zh-cn_topic_0237121962_p14290141414543"></a>2</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p2290181419545"><a name="zh-cn_topic_0237121962_p2290181419545"></a><a name="zh-cn_topic_0237121962_p2290181419545"></a>Supported</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row329031414544"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p16290121416541"><a name="zh-cn_topic_0237121962_p16290121416541"></a><a name="zh-cn_topic_0237121962_p16290121416541"></a>serial</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p17290101435418"><a name="zh-cn_topic_0237121962_p17290101435418"></a><a name="zh-cn_topic_0237121962_p17290101435418"></a>4</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p129020141544"><a name="zh-cn_topic_0237121962_p129020141544"></a><a name="zh-cn_topic_0237121962_p129020141544"></a>Supported</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row122901114185414"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p1229051411545"><a name="zh-cn_topic_0237121962_p1229051411545"></a><a name="zh-cn_topic_0237121962_p1229051411545"></a>bigserial</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p8290314155413"><a name="zh-cn_topic_0237121962_p8290314155413"></a><a name="zh-cn_topic_0237121962_p8290314155413"></a>8</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p329061475416"><a name="zh-cn_topic_0237121962_p329061475416"></a><a name="zh-cn_topic_0237121962_p329061475416"></a>Supported</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row152905140543"><td class="cellrowborder" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p129081465413"><a name="zh-cn_topic_0237121962_p129081465413"></a><a name="zh-cn_topic_0237121962_p129081465413"></a>Monetary Types</p>
+</td>
+<td class="cellrowborder" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p2029014148549"><a name="zh-cn_topic_0237121962_p2029014148549"></a><a name="zh-cn_topic_0237121962_p2029014148549"></a>money</p>
+</td>
+<td class="cellrowborder" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p14290181475411"><a name="zh-cn_topic_0237121962_p14290181475411"></a><a name="zh-cn_topic_0237121962_p14290181475411"></a>8</p>
+</td>
+<td class="cellrowborder" headers="mcps1.2.5.1.4 "><p id="zh-cn_topic_0237121962_p1729041412543"><a name="zh-cn_topic_0237121962_p1729041412543"></a><a name="zh-cn_topic_0237121962_p1729041412543"></a>Supported</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row17290141495413"><td class="cellrowborder" rowspan="6" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p6290171485411"><a name="zh-cn_topic_0237121962_p6290171485411"></a><a name="zh-cn_topic_0237121962_p6290171485411"></a>Character Types</p>
+</td>
+<td class="cellrowborder" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p1629015140543"><a name="zh-cn_topic_0237121962_p1629015140543"></a><a name="zh-cn_topic_0237121962_p1629015140543"></a>character varying(n), varchar(n)</p>
+</td>
+<td class="cellrowborder" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p14290181415418"><a name="zh-cn_topic_0237121962_p14290181415418"></a><a name="zh-cn_topic_0237121962_p14290181415418"></a>-1</p>
+</td>
+<td class="cellrowborder" headers="mcps1.2.5.1.4 "><p id="zh-cn_topic_0237121962_p16290171418540"><a name="zh-cn_topic_0237121962_p16290171418540"></a><a name="zh-cn_topic_0237121962_p16290171418540"></a>Supported</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row172904145544"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p929015143540"><a name="zh-cn_topic_0237121962_p929015143540"></a><a name="zh-cn_topic_0237121962_p929015143540"></a>character(n), char(n)</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p16290111418547"><a name="zh-cn_topic_0237121962_p16290111418547"></a><a name="zh-cn_topic_0237121962_p16290111418547"></a>n</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p8290111419540"><a name="zh-cn_topic_0237121962_p8290111419540"></a><a name="zh-cn_topic_0237121962_p8290111419540"></a>Supported</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row20290914115417"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p32901214145415"><a name="zh-cn_topic_0237121962_p32901214145415"></a><a name="zh-cn_topic_0237121962_p32901214145415"></a>character、char</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p142901914115411"><a name="zh-cn_topic_0237121962_p142901914115411"></a><a name="zh-cn_topic_0237121962_p142901914115411"></a>1</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p1429001418542"><a name="zh-cn_topic_0237121962_p1429001418542"></a><a name="zh-cn_topic_0237121962_p1429001418542"></a>Supported</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row12290814125418"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p4290101485417"><a name="zh-cn_topic_0237121962_p4290101485417"></a><a name="zh-cn_topic_0237121962_p4290101485417"></a>text</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p1229020141546"><a name="zh-cn_topic_0237121962_p1229020141546"></a><a name="zh-cn_topic_0237121962_p1229020141546"></a>-1</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p1529016148543"><a name="zh-cn_topic_0237121962_p1529016148543"></a><a name="zh-cn_topic_0237121962_p1529016148543"></a>Supported</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row7290101405415"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p029012140542"><a name="zh-cn_topic_0237121962_p029012140542"></a><a name="zh-cn_topic_0237121962_p029012140542"></a>nvarchar2</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p129014147548"><a name="zh-cn_topic_0237121962_p129014147548"></a><a name="zh-cn_topic_0237121962_p129014147548"></a>-1</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p202901614135412"><a name="zh-cn_topic_0237121962_p202901614135412"></a><a name="zh-cn_topic_0237121962_p202901614135412"></a>Supported</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row172907148542"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p5290914125415"><a name="zh-cn_topic_0237121962_p5290914125415"></a><a name="zh-cn_topic_0237121962_p5290914125415"></a>name</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p629081412547"><a name="zh-cn_topic_0237121962_p629081412547"></a><a name="zh-cn_topic_0237121962_p629081412547"></a>64</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p142908146549"><a name="zh-cn_topic_0237121962_p142908146549"></a><a name="zh-cn_topic_0237121962_p142908146549"></a>Not supported</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row19290141414543"><td class="cellrowborder" rowspan="6" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p14290131412540"><a name="zh-cn_topic_0237121962_p14290131412540"></a><a name="zh-cn_topic_0237121962_p14290131412540"></a>Date/Time Types</p>
+</td>
+<td class="cellrowborder" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p3290151495415"><a name="zh-cn_topic_0237121962_p3290151495415"></a><a name="zh-cn_topic_0237121962_p3290151495415"></a>timestamp with time zone</p>
+</td>
+<td class="cellrowborder" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p20290111495420"><a name="zh-cn_topic_0237121962_p20290111495420"></a><a name="zh-cn_topic_0237121962_p20290111495420"></a>8</p>
+</td>
+<td class="cellrowborder" headers="mcps1.2.5.1.4 "><p id="zh-cn_topic_0237121962_p132908147546"><a name="zh-cn_topic_0237121962_p132908147546"></a><a name="zh-cn_topic_0237121962_p132908147546"></a>Supported</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row172901014155417"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p1829041445411"><a name="zh-cn_topic_0237121962_p1829041445411"></a><a name="zh-cn_topic_0237121962_p1829041445411"></a>timestamp without time zone</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p192902145542"><a name="zh-cn_topic_0237121962_p192902145542"></a><a name="zh-cn_topic_0237121962_p192902145542"></a>8</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p5290121485410"><a name="zh-cn_topic_0237121962_p5290121485410"></a><a name="zh-cn_topic_0237121962_p5290121485410"></a>Supported</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row132901514165419"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p14290181415547"><a name="zh-cn_topic_0237121962_p14290181415547"></a><a name="zh-cn_topic_0237121962_p14290181415547"></a>date</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p929071410545"><a name="zh-cn_topic_0237121962_p929071410545"></a><a name="zh-cn_topic_0237121962_p929071410545"></a>4</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p102900146546"><a name="zh-cn_topic_0237121962_p102900146546"></a><a name="zh-cn_topic_0237121962_p102900146546"></a>Supported</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row13290181445412"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p1929020147545"><a name="zh-cn_topic_0237121962_p1929020147545"></a><a name="zh-cn_topic_0237121962_p1929020147545"></a>time without time zone</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p12290114145411"><a name="zh-cn_topic_0237121962_p12290114145411"></a><a name="zh-cn_topic_0237121962_p12290114145411"></a>8</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p10290614175411"><a name="zh-cn_topic_0237121962_p10290614175411"></a><a name="zh-cn_topic_0237121962_p10290614175411"></a>Supported</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row102901714155411"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p13290131485413"><a name="zh-cn_topic_0237121962_p13290131485413"></a><a name="zh-cn_topic_0237121962_p13290131485413"></a>time with time zone</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p92902014105420"><a name="zh-cn_topic_0237121962_p92902014105420"></a><a name="zh-cn_topic_0237121962_p92902014105420"></a>12</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p82901814155415"><a name="zh-cn_topic_0237121962_p82901814155415"></a><a name="zh-cn_topic_0237121962_p82901814155415"></a>Supported</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row1029061411542"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p1729012141543"><a name="zh-cn_topic_0237121962_p1729012141543"></a><a name="zh-cn_topic_0237121962_p1729012141543"></a>interval</p>
+</td>
+<td class="cellrowborder" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p172901314105418"><a name="zh-cn_topic_0237121962_p172901314105418"></a><a name="zh-cn_topic_0237121962_p172901314105418"></a>16</p>
+</td>
+<td class="cellrowborder" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p1529071414545"><a name="zh-cn_topic_0237121962_p1529071414545"></a><a name="zh-cn_topic_0237121962_p1529071414545"></a>Supported</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row1729021435410"><td class="cellrowborder" rowspan="2" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p1290191455417"><a name="zh-cn_topic_0237121962_p1290191455417"></a><a name="zh-cn_topic_0237121962_p1290191455417"></a>big object</p>
+</td>
+<td class="cellrowborder" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p11290314165418"><a name="zh-cn_topic_0237121962_p11290314165418"></a><a name="zh-cn_topic_0237121962_p11290314165418"></a>clob</p>
+</td>
+<td class="cellrowborder" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p172901143541"><a name="zh-cn_topic_0237121962_p172901143541"></a><a name="zh-cn_topic_0237121962_p172901143541"></a>-1</p>
+</td>
+<td class="cellrowborder" headers="mcps1.2.5.1.4 "><p id="zh-cn_topic_0237121962_p629020143542"><a name="zh-cn_topic_0237121962_p629020143542"></a><a name="zh-cn_topic_0237121962_p629020143542"></a>Supported</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row7290121435417"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p629019144544"><a name="zh-cn_topic_0237121962_p629019144544"></a><a name="zh-cn_topic_0237121962_p629019144544"></a>blob</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p1729091425412"><a name="zh-cn_topic_0237121962_p1729091425412"></a><a name="zh-cn_topic_0237121962_p1729091425412"></a>-1</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p0290514105414"><a name="zh-cn_topic_0237121962_p0290514105414"></a><a name="zh-cn_topic_0237121962_p0290514105414"></a>Not supported</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row12290514165416"><td class="cellrowborder" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p1229011417541"><a name="zh-cn_topic_0237121962_p1229011417541"></a><a name="zh-cn_topic_0237121962_p1229011417541"></a>other types</p>
+</td>
+<td class="cellrowborder" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p3290191475416"><a name="zh-cn_topic_0237121962_p3290191475416"></a><a name="zh-cn_topic_0237121962_p3290191475416"></a>…</p>
+</td>
+<td class="cellrowborder" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p1029013140546"><a name="zh-cn_topic_0237121962_p1029013140546"></a><a name="zh-cn_topic_0237121962_p1029013140546"></a>…</p>
+</td>
+<td class="cellrowborder" headers="mcps1.2.5.1.4 "><p id="zh-cn_topic_0237121962_p1229019143547"><a name="zh-cn_topic_0237121962_p1229019143547"></a><a name="zh-cn_topic_0237121962_p1229019143547"></a>Not supported</p>
+</td>
+</tr>
+</tbody>
+</table>
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/17-xml-type.md b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/17-xml-type.md
new file mode 100644
index 0000000000000000000000000000000000000000..919f55f7727dd9652313e8224a77bab4442e218e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/17-xml-type.md
@@ -0,0 +1,34 @@
+---
+title: XML Type
+summary: XML Type
+author: Guo Huan
+date: 2021-04-06
+---
+
+# XML Type
+
+MogDB supports the XML type. The following is an example:
+
+```sql
+mogdb= CREATE TABLE xmltest ( id int, data xml );
+mogdb= INSERT INTO xmltest VALUES (1, 'one');
+mogdb= INSERT INTO xmltest VALUES (2, 'two');
+mogdb= SELECT * FROM xmltest ORDER BY 1;
+ id | data
+----+--------------------
+1 | one
+2 | two
+(2 rows)
+mogdb= SELECT xmlconcat('', NULL, '');
+xmlconcat
+(1 row)
+mogdb= SELECT xmlconcat('', NULL, '');
+xmlconcat
+(1 row)
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - This function is disabled by default. To use this function, you need to use the **build.sh** script to compile the database again and add the **-with-libxml** parameter to the **./configure** configuration parameter.
+> - Before compilation, you need to run the **yum install -y libxml2-devel** command. Otherwise, the "configure: error: library 'xml2' (version &gt;= 2.6.23) is required for XML support" error will be reported.
+> - Before compilation, you need to add the **dependency/operating system environment/libobs/comm/lib** in the binary file of the third-party library to the system environment variable **LD_LIBRARY_PATH**. Otherwise, an error message is displayed, indicating that **libiconv.so** does not exist.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/18-data-type-used-by-the-ledger-database.md b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/18-data-type-used-by-the-ledger-database.md
new file mode 100644
index 0000000000000000000000000000000000000000..cadf006d99c2402ebfa21d1314000dd81321be4a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/18-data-type-used-by-the-ledger-database.md
@@ -0,0 +1,31 @@
+---
+title: Data Type Used by the Ledger Database
+summary: Data Type Used by the Ledger Database
+author: Zhang Cuiping
+date: 2021-10-25
+---
+
+# Data Type Used by the Ledger Database
+
+The ledger database uses the hash16 data type to store row-level hash digests or table-level hash digests, and uses the hash32 data type to store global hash digests or history table verification hashes.
+
+**Table 1** Hash type of the ledger database
+
+| Name   | Description         | Storage Space | Value Range                     |
+| :---------- | :------------------------ | :------------ | :-------------------------------- |
+| HASH16 | Stored as an unsigned 64-bit integer              | 8 bytes       | 0 to +18446744073709551615                              |
+| HASH32 | Stored as a group of 16 unsigned integer elements | 16 bytes      | Value range of an unsigned integer array of 16 elements |
+
+The hash16 data type is used to store row-level or table-level hash digests in the ledger database. After obtaining the hash sequence of a 16-character hexadecimal string, the system invokes the **hash16in** function to convert the sequence into an unsigned 64-bit integer and stores the integer in a hash16 variable. For example:
+
+```sql
+Hexadecimal string: e697da2eaa3a775b; 64-bit unsigned integer: 16615989244166043483
+Hexadecimal string: ffffffffffffffff; 64-bit unsigned integer: 18446744073709551615
+```
+
+The hash32 data type is used to store the global hash digest or history table verification hash in the ledger database. After obtaining the hash sequence of a 32-character hexadecimal string, the system invokes the **hash32in** function to convert the sequence to an array containing 16 unsigned integer elements. For example:
+
+```sql
+Hexadecimal string: 685847ed1fe38e18f6b0e2b18c00edee
+Hash32 array: [104,88,71,237,31,227,142,24,246,176,226,177,140,0,237,238]
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/2-monetary.md b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/2-monetary.md
new file mode 100644
index 0000000000000000000000000000000000000000..c1708109dab11f928296b0c82fa235ba0ac9d371
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/2-monetary.md
@@ -0,0 +1,34 @@
+---
+title: Monetary Types
+summary: Monetary Types
+author: Guo Huan
+date: 2021-04-06
+---
+
+# Monetary Types
+
+The money type stores a currency amount with fixed fractional precision.
+
+The range shown in Table 1 assumes there are two fractional digits. Input is accepted in a variety of formats, including integer and floating-point literals, as well as typical currency formatting, such as "$1,000.00". Output is generally in the last format but depends on the locale.
+
+**Table 1** Monetary type
+
+| Name  | Storage Space | Description     | Range                                          |
+| :---- | :------------ | :-------------- | :--------------------------------------------- |
+| money | 8 bytes       | Currency amount | -92233720368547758.08 to +92233720368547758.07 |
+
+Values of the numeric, int, and bigint data types can be cast to money. Conversion from the real and double precision data types can be done by casting to numeric first, for example:
+
+```sql
+mogdb=# SELECT '12.34'::float8::numeric::money;
+```
+
+However, this is not recommended. Floating point numbers should not be used to handle money due to the potential for rounding errors.
+
+A money value can be cast to numeric without loss of precision. Conversion to other types could potentially lose precision, and must also be done in two stages:
+
+```sql
+mogdb=# SELECT '52093.89'::money::numeric::float8;
+```
+
+When a money value is divided by another money value, the result is double precision (that is, a pure number, not money); the currency units cancel each other out in the division.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/3-boolean-data-types.md b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/3-boolean-data-types.md
new file mode 100644
index 0000000000000000000000000000000000000000..f671029fae83642632c29af38645726397635194
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/3-boolean-data-types.md
@@ -0,0 +1,59 @@
+---
+title: Boolean Data Types
+summary: Boolean Data Types
+author: Guo Huan
+date: 2021-04-06
+---
+
+# Boolean Data Types
+
+**Table 1** Boolean types
+
+| Name    | Description  | Storage Space | Value                                               |
+| :------ | :----------- | :------------ | :-------------------------------------------------- |
+| BOOLEAN | Boolean type | 1 byte        | - **true**<br/>- **false**<br/>- **null** (unknown) |
+
+Valid literal values for the "true" state include:
+
+**TRUE**, **'t'**, **'true'**, **'y'**, **'yes'**, **'1'**, **'TRUE'**, **true**, and an integer ranging from 1 to 2^63 - 1 or from -1 to -2^63.
+
+Valid literal values for the "false" state include:
+
+**FALSE**, **'f'**, **'false'**, **'n'**, **'no'**, **'0'**, **0**, **'FALSE'**, and **false**.
+
+**TRUE** and **FALSE** are standard expressions, compatible with SQL statements.
+
+## Example
+
+Boolean values are displayed using the letters t and f.
+
+```sql
+-- Create a table.
+mogdb=# CREATE TABLE bool_type_t1
+(
+    BT_COL1 BOOLEAN,
+    BT_COL2 TEXT
+);
+
+-- Insert data.
+mogdb=# INSERT INTO bool_type_t1 VALUES (TRUE, 'sic est');
+
+mogdb=# INSERT INTO bool_type_t1 VALUES (FALSE, 'non est');
+
+-- View data.
+mogdb=# SELECT * FROM bool_type_t1;
+ bt_col1 | bt_col2
+---------+---------
+ t       | sic est
+ f       | non est
+(2 rows)
+
+mogdb=# SELECT * FROM bool_type_t1 WHERE bt_col1 = 't';
+ bt_col1 | bt_col2
+---------+---------
+ t       | sic est
+(1 row)
+
+-- Delete the table.
+mogdb=# DROP TABLE bool_type_t1;
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/4-character-data-types.md b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/4-character-data-types.md
new file mode 100644
index 0000000000000000000000000000000000000000..f3c5eefb52e501393bde3a79dd941f8982663906
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/4-character-data-types.md
@@ -0,0 +1,89 @@
+---
+title: Character Data Types
+summary: Character Data Types
+author: Guo Huan
+date: 2021-04-06
+---
+
+# Character Data Types
+
+Table 1 lists the character data types supported by MogDB. For string operators and related built-in functions, see [Character Processing Functions and Operators](3-character-processing-functions-and-operators).
+
+**Table 1** Character data types
+
+| Name                           | Description                                                  | Storage Space                                                |
+| :----------------------------- | :----------------------------------------------------------- | :----------------------------------------------------------- |
+| CHAR(n)CHARACTER(n)NCHAR(n)    | Fixed-length character string, blank padded. **n** indicates the string length. If it is not specified, the default precision **1** is used. | The maximum size is 10 MB.                                   |
+| VARCHAR(n)CHARACTER VARYING(n) | Variable-length string. **n** indicates the string length.   | The maximum size is 10 MB.                                   |
+| VARCHAR2(n)                    | Variable-length string. It is the alias of the VARCHAR(n) type. **n** indicates the string length. | The maximum size is 10 MB.                                   |
+| NVARCHAR2(n)                   | Variable-length string. **n** indicates the string length.   | The maximum size is 10 MB.                                   |
+| TEXT                           | Variable-length string.                                      | The maximum size is 1 GB - 1 byte. However, the size of the column description header and the size of the tuple (less than 1 GB - 1 byte) where the column is located must also be considered. Therefore, the maximum size of the TEXT type may be less than 1 GB - 1 byte. |
+| CLOB                           | A big text object. It is the alias of the TEXT type.         | The maximum size is 1 GB - 1 byte. However, the size of the column description header and the size of the tuple (less than 1 GB - 1 byte) where the column is located must also be considered. Therefore, the maximum size of the CLOB type may be less than 1 GB-1. |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> In addition to the size limitation on each column, the total size of each tuple is 8,203 bytes less than 1 GB, namely, 1,073,733,621 bytes.
+
+In MogDB, there are two other fixed-length character types, as shown in Table 2. The **name** type exists only for the storage of identifiers in the internal system catalogs and is not intended for use by general users. Its length is currently defined as 64 bytes (63 usable characters plus terminator). The type **"char"** only uses one byte of storage. It is internally used in the system catalogs as a simplistic enumeration type.
+
+**Table 2** Special character types
+
+| Name   | Description                    | Storage Space |
+| :----- | :----------------------------- | :------------ |
+| name   | Internal type for object names | 64 bytes      |
+| "char" | Single-byte internal type      | 1 byte        |
+
+## Example
+
+```sql
+-- Create a table.
+mogdb=# CREATE TABLE char_type_t1
+(
+    CT_COL1 CHARACTER(4)
+);
+
+-- Insert data.
+mogdb=# INSERT INTO char_type_t1 VALUES ('ok');
+
+-- Query data in the table.
+mogdb=# SELECT ct_col1, char_length(ct_col1) FROM char_type_t1;
+ ct_col1 | char_length
+---------+-------------
+ ok      |           4
+(1 row)
+
+-- Delete the table.
+mogdb=# DROP TABLE char_type_t1;
+```
+
+```sql
+-- Create a table.
+mogdb=# CREATE TABLE char_type_t2
+(
+    CT_COL1 VARCHAR(5)
+);
+
+-- Insert data.
+mogdb=# INSERT INTO char_type_t2 VALUES ('ok');
+
+mogdb=# INSERT INTO char_type_t2 VALUES ('good');
+
+-- Specify the type length. An error is reported if an inserted string exceeds this length.
+mogdb=# INSERT INTO char_type_t2 VALUES ('too long');
+ERROR:  value too long for type character varying(5)
+CONTEXT:  referenced column: ct_col1
+
+-- Specify the type length. A string exceeding this length is truncated.
+mogdb=# INSERT INTO char_type_t2 VALUES ('too long'::varchar(5));
+
+-- Query data.
+mogdb=# SELECT ct_col1, char_length(ct_col1) FROM char_type_t2;
+ ct_col1 | char_length
+---------+-------------
+ ok      |           2
+ good    |           4
+ too l   |           5
+(3 rows)
+
+-- Delete data.
+mogdb=# DROP TABLE char_type_t2;
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/4.1-enumerated-types.md b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/4.1-enumerated-types.md
new file mode 100644
index 0000000000000000000000000000000000000000..c6ac9be9e9dd3bb03dec8189a96cfebfdf54f212
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/4.1-enumerated-types.md
@@ -0,0 +1,101 @@
+---
+title: Enumerated Types
+summary: Enumerated Types
+author: Guo Huan
+date: 2021-11-19
+---
+
+# Enumerated Types
+
+Enumerated (enum) types are data types that comprise a static, ordered set of values. They are equivalent to the `enum` types supported in a number of programming languages. An example of an enum type might be the days of the week, or a set of status values for a piece of data.
+
+## Declaration of Enumerated Types
+
+Enum types are created using the [CREATE TYPE](67-CREATE-TYPE) command, for example:
+
+```sql
+CREATE TYPE mood AS ENUM ('sad', 'ok', 'happy');
+```
+
+Once created, the enum type can be used in table and function definitions much like any other type:
+
+```sql
+CREATE TYPE mood AS ENUM ('sad', 'ok', 'happy');
+CREATE TABLE person (
+    name text,
+    current_mood mood
+);
+INSERT INTO person VALUES ('Moe', 'happy');
+SELECT * FROM person WHERE current_mood = 'happy';
+ name | current_mood 
+------+--------------
+ Moe  | happy
+(1 row)
+```
+
+## Ordering
+
+The ordering of the values in an enum type is the order in which the values were listed when the type was created. All standard comparison operators and related aggregate functions are supported for enums. For example:
+
+```sql
+INSERT INTO person VALUES ('Larry', 'sad');
+INSERT INTO person VALUES ('Curly', 'ok');
+SELECT * FROM person WHERE current_mood > 'sad';
+ name  | current_mood 
+-------+--------------
+ Moe   | happy
+ Curly | ok
+(2 rows)
+
+SELECT * FROM person WHERE current_mood > 'sad' ORDER BY current_mood;
+ name  | current_mood 
+-------+--------------
+ Curly | ok
+ Moe   | happy
+(2 rows)
+
+SELECT name
+FROM person
+WHERE current_mood = (SELECT MIN(current_mood) FROM person);
+ name  
+-------
+ Larry
+(1 row)
+```
+
+## Type Safety
+
+Each enumerated data type is separate and cannot be compared with other enumerated types. See this example:
+
+```sql
+CREATE TYPE happiness AS ENUM ('happy', 'very happy', 'ecstatic');
+CREATE TABLE holidays (
+    num_weeks integer,
+    happiness happiness
+);
+INSERT INTO holidays(num_weeks,happiness) VALUES (4, 'happy');
+INSERT INTO holidays(num_weeks,happiness) VALUES (6, 'very happy');
+INSERT INTO holidays(num_weeks,happiness) VALUES (8, 'ecstatic');
+INSERT INTO holidays(num_weeks,happiness) VALUES (2, 'sad');
+ERROR:  invalid input value for enum happiness: "sad"
+SELECT person.name, holidays.num_weeks FROM person, holidays
+  WHERE person.current_mood = holidays.happiness;
+ERROR:  operator does not exist: mood = happiness
+```
+
+If you really need to do something like that, you can either write a custom operator or add explicit casts to your query:
+
+```sql
+SELECT person.name, holidays.num_weeks FROM person, holidays
+  WHERE person.current_mood::text = holidays.happiness::text;
+ name | num_weeks 
+------+-----------
+ Moe  |         4
+(1 row)
+```
+
+## Implementation Details
+
+An enum value occupies four bytes on disk. The length of an enum value's textual label is limited by the `NAMEDATALEN` setting compiled into MogDB; in standard builds this means at most 63 bytes.
+
+Enum labels are case sensitive, so `'happy'` is not the same as `'HAPPY'`. White space in the labels is significant too.
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/5-binary-data-types.md b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/5-binary-data-types.md
new file mode 100644
index 0000000000000000000000000000000000000000..222eec60e385feb82592b8d903de92f9719b0374
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/5-binary-data-types.md
@@ -0,0 +1,54 @@
+---
+title: Binary Data Types
+summary: Binary Data Types
+author: Guo Huan
+date: 2021-04-06
+---
+
+# Binary Data Types
+
+Table 1 lists the binary data types supported by MogDB.
+
+**Table 1** Binary data types
+
+| Name                           | Description                | Storage Space              |
+| :----------------------------- | :------------------------- | :------------------------- |
+| BLOB                           | Binary large object (BLOB).<br />NOTE:<br />Column storage cannot be used for the BLOB type. | Its maximum length is 1073733621 bytes (1 GB - 8203 bytes).  |
+| RAW                            | Variable-length hexadecimal string.<br />NOTE:<br />Column storage cannot be used for the raw type. | 4 bytes plus the actual hexadecimal string. Its maximum length is 1073733621 bytes (1 GB - 8203 bytes). |
+| BYTEA                          | Variable-length binary string.                               | 4 bytes plus the actual binary string. Its maximum length is 1073733621 bytes (1 GB - 8203 bytes). |
+| BYTEAWITHOUTORDERWITHEQUALCOL  | Variable-length binary character string (new type for the encryption feature. If the encryption type of the encrypted column is specified as deterministic encryption, the column type is BYTEAWITHOUTORDERWITHEQUALCOL). The original data type is displayed when the encrypted table is printed by running the meta command. | 4 bytes plus the actual binary string. The maximum value is 1073741771 bytes (1 GB - 53 bytes). |
+| BYTEAWITHOUTORDERCOL           | Variable-length binary character string (new type for the encryption feature. If the encryption type of the encrypted column is specified as random encryption, the column type is BYTEAWITHOUTORDERCOL). The original data type is displayed when the encrypted table is printed by running the meta command. | 4 bytes plus the actual binary string. The maximum value is 1073741771 bytes (1 GB - 53 bytes). |
+| _BYTEAWITHOUTORDERWITHEQUALCOL | Variable-length binary character string, which is a new type for the encryption feature. | 4 bytes plus the actual binary string. The maximum value is 1073741771 bytes (1 GB - 53 bytes). |
+| _BYTEAWITHOUTORDERCOL          | Variable-length binary character string, which is a new type for the encryption feature. | 4 bytes plus the actual binary string. The maximum value is 1073741771 bytes (1 GB - 53 bytes). |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - In addition to the size limitation on each column, the total size of each tuple is 1073733621 bytes (1 GB to 8203 bytes).
+> - BYTEAWITHOUTORDERWITHEQUALCOL, BYTEAWITHOUTORDERCOL, BYTEAWITHOUTORDERWITHEQUALCOL, and BYTEAWITHOUTORDERCOL cannot be directly used to create a table.
+
+An example is provided as follows:
+
+```sql
+-- Create a table.
+mogdb=# CREATE TABLE blob_type_t1
+(
+    BT_COL1 INTEGER,
+    BT_COL2 BLOB,
+    BT_COL3 RAW,
+    BT_COL4 BYTEA
+) ;
+
+-- Insert data.
+mogdb=# INSERT INTO blob_type_t1 VALUES(10,empty_blob(),
+HEXTORAW('DEADBEEF'),E'\\xDEADBEEF');
+
+-- Query data in the table.
+mogdb=# SELECT * FROM blob_type_t1;
+ bt_col1 | bt_col2 | bt_col3  |  bt_col4
+---------+---------+----------+------------
+      10 |         | DEADBEEF | \xdeadbeef
+(1 row)
+
+-- Delete the table.
+mogdb=# DROP TABLE blob_type_t1;
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/6-date-time-types.md b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/6-date-time-types.md
new file mode 100644
index 0000000000000000000000000000000000000000..00babf5dc203c6105c666ead836faaee0622ffd2
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/6-date-time-types.md
@@ -0,0 +1,323 @@
+---
+title: Date/Time
+summary: Date/Time
+author: Guo Huan
+date: 2021-04-06
+---
+
+# Date/Time
+
+Table 1 lists the date/time types supported by MogDB. For the operators and built-in functions of the types, see Date and Time Processing Functions and Operators.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** If the time format of another database is different from that of MogDB, modify the value of the **DateStyle** parameter to keep them consistent.
+
+**Table 1** Date/Time types
+
+| Name                               | Description                                                  | Storage Space                                  |
+| :--------------------------------- | :----------------------------------------------------------- | :--------------------------------------------- |
+| DATE                               | Date and time.                                               | 4 bytes (The actual storage space is 8 bytes.) |
+| TIME [(p)] [WITHOUT TIME ZONE]     | Time within one day.<br/>**p** indicates the precision after the decimal point. The value ranges from 0 to 6. | 8 bytes                                        |
+| TIME [(p)] [WITH TIME ZONE]        | Time within one day (with time zone).<br/>**p** indicates the precision after the decimal point. The value ranges from 0 to 6. | 12 bytes                                       |
+| TIMESTAMP[(p)] [WITHOUT TIME ZONE] | Date and time.<br/>**p** indicates the precision after the decimal point. The value ranges from 0 to 6. | 8 bytes                                        |
+| TIMESTAMP[(p)][WITH TIME ZONE]    | Date and time (with time zone). TIMESTAMP is also called TIMESTAMPTZ.<br/>**p** indicates the precision after the decimal point. The value ranges from 0 to 6. | 8 bytes                                        |
+| SMALLDATETIME                      | Date and time (without time zone).<br/>The precision level is minute. 31s to 59s are rounded into 1 minute. | 8 bytes                                        |
+| INTERVAL DAY (l) TO SECOND (p)     | Time interval (X days X hours X minutes X seconds).<br/>- **l**: indicates the precision of days. The value ranges from 0 to 6. For compatibility, the precision functions are not supported.<br/>- **p**: indicates the precision of seconds. The value ranges from 0 to 6. The digit 0 at the end of a decimal number is not displayed. | 16 bytes                                       |
+| INTERVAL [FIELDS] [ (p) ]          | Time interval.<br/>- fields:**YEAR**, **MONTH**, **DAY**, **HOUR**, **MINUTE**, **SECOND**, **DAY TO HOUR**, **DAY TO MINUTE**, **DAY TO SECOND**, **HOUR TO MINUTE**, **HOUR TO SECOND**, and **MINUTE TO SECOND**.<br/>- **p**: indicates the precision of seconds. The value ranges from 0 to 6. **p** takes effect only when fields are **SECOND**, **DAY TO SECOND**, **HOUR TO SECOND**, or **MINUTE TO SECOND**. The digit 0 at the end of a decimal number is not displayed. | 12 bytes                                       |
+| reltime                            | Relative time interval. The format is as follows:<br/>**X** years **X** mons **X** days **XX:XX:XX**<br/>The Julian calendar is used. It specifies that a year has 365.25 days and a month has 30 days. The relative time interval needs to be calculated based on the input value. The output format is POSTGRES. | 4 bytes                                        |
+| abstime                            | Date and time. The format is as follows:<br/>YYYY-MM-DD hh:mm:ss+timezone<br/>The value range is from 1901-12-13 20:45:53 GMT to 2038-01-18 23:59:59 GMT. The precision level is second. | 4 bytes                                        |
+
+Examples
+
+```sql
+-- Create a table.
+mogdb=# CREATE TABLE date_type_tab(coll date);
+
+-- Insert data.
+mogdb=# INSERT INTO date_type_tab VALUES (date '12-10-2010');
+
+-- View data.
+mogdb=# SELECT * FROM date_type_tab;
+        coll
+---------------------
+ 2010-12-10 00:00:00
+(1 row)
+
+-- Drop the table.
+mogdb=# DROP TABLE date_type_tab;
+
+-- Create a table.
+mogdb=# CREATE TABLE time_type_tab (da time without time zone ,dai time with time zone,dfgh timestamp without time zone,dfga timestamp with time zone, vbg smalldatetime);
+
+-- Insert data.
+mogdb=# INSERT INTO time_type_tab VALUES ('21:21:21','21:21:21 pst','2010-12-12','2013-12-11 pst','2003-04-12 04:05:06');
+
+-- View data.
+mogdb=# SELECT * FROM time_type_tab;
+    da    |     dai     |        dfgh         |          dfga          |         vbg
+----------+-------------+---------------------+------------------------+---------------------
+ 21:21:21 | 21:21:21-08 | 2010-12-12 00:00:00 | 2013-12-11 16:00:00+08 | 2003-04-12 04:05:00
+(1 row)
+
+-- Drop the table.
+mogdb=# DROP TABLE time_type_tab;
+
+-- Create a table.
+mogdb=# CREATE TABLE day_type_tab (a int,b INTERVAL DAY(3) TO SECOND (4));
+
+-- Insert data.
+mogdb=# INSERT INTO day_type_tab VALUES (1, INTERVAL '3' DAY);
+
+-- View data.
+mogdb=# SELECT * FROM day_type_tab;
+ a |   b
+---+--------
+ 1 | 3 days
+(1 row)
+
+-- Drop the table.
+mogdb=# DROP TABLE day_type_tab;
+
+-- Create a table.
+mogdb=# CREATE TABLE year_type_tab(a int, b interval year (6));
+
+-- Insert data.
+mogdb=# INSERT INTO year_type_tab VALUES(1,interval '2' year);
+
+-- View data.
+mogdb=# SELECT * FROM year_type_tab;
+ a |    b
+---+---------
+ 1 | 2 years
+(1 row)
+
+-- Drop the table.
+mogdb=# DROP TABLE year_type_tab;
+```
+
+## Date Input
+
+Date and time input is accepted in almost any reasonable formats, including ISO 8601, SQL-compatible, and traditional POSTGRES. The system allows you to customize the sequence of day, month, and year in the date input. Set the **DateStyle** parameter to **MDY** to select month-day-year interpretation, **DMY** to select day-month-year interpretation, or **YMD** to select year-month-day interpretation.
+
+Remember that any date or time literal input needs to be enclosed with single quotes, and the syntax is as follows:
+
+type [ ( p ) ] 'value'
+
+The **p** that can be selected in the precision statement is an integer, indicating the number of fractional digits in the **seconds** column. Table 2 shows some possible inputs for the **date** type.
+
+**Table 2** Date input
+
+| Example          | Description                                                  |
+| :--------------- | :----------------------------------------------------------- |
+| 1999-01-08       | ISO 8601 (recommended format). January 8, 1999 in any mode   |
+| January 8, 1999  | Unambiguous in any **datestyle** input mode                  |
+| 1/8/1999         | January 8 in **MDY** mode. August 1 in **DMY** mode          |
+| 1/18/1999        | January 18 in **MDY** mode, rejected in other modes          |
+| 01/02/03         | - January 2, 2003 in **MDY** mode<br/>- February 1, 2003 in **DMY** mode<br/>- February 3, 2001 in **YMD** mode |
+| 1999-Jan-08      | January 8 in any mode                                        |
+| Jan-08-1999      | January 8 in any mode                                        |
+| 08-Jan-1999      | January 8 in any mode                                        |
+| 99-Jan-08        | January 8 in **YMD** mode, else error                        |
+| 08-Jan-99        | January 8, except error in **YMD** mode                      |
+| Jan-08-99        | January 8, except error in **YMD** mode                      |
+| 19990108         | ISO 8601. January 8, 1999 in any mode                        |
+| 990108           | ISO 8601. January 8, 1999 in any mode                        |
+| 1999.008         | Year and day of year                                         |
+| J2451187         | Julian date                                                  |
+| January 8, 99 BC | Year 99 BC                                                   |
+
+Examples
+
+```sql
+-- Create a table.
+mogdb=# CREATE TABLE date_type_tab(coll date);
+
+-- Insert data.
+mogdb=# INSERT INTO date_type_tab VALUES (date '12-10-2010');
+
+-- View data.
+mogdb=# SELECT * FROM date_type_tab;
+        coll
+---------------------
+ 2010-12-10 00:00:00
+(1 row)
+
+-- View the date format.
+mogdb=# SHOW datestyle;
+ DateStyle
+-----------
+ ISO, MDY
+(1 row)
+
+-- Set the date format.
+mogdb=# SET datestyle='YMD';
+SET
+
+-- Insert data.
+mogdb=# INSERT INTO date_type_tab VALUES(date '2010-12-11');
+
+-- View data.
+mogdb=# SELECT * FROM date_type_tab;
+        coll
+---------------------
+ 2010-12-10 00:00:00
+ 2010-12-11 00:00:00
+(2 rows)
+
+-- Drop the table.
+mogdb=# DROP TABLE date_type_tab;
+```
+
+## Time
+
+The time-of-day types are **TIME [(p)] [WITHOUT TIME ZONE]** and **TIME [(p)] [WITH TIME ZONE]**. **TIME** alone is equivalent to **TIME WITHOUT TIME ZONE**.
+
+If a time zone is specified in the input for **TIME WITHOUT TIME ZONE**, it is silently ignored.
+
+For details about the time input types, see Table 3. For details about time zone input types, see Table 4.
+
+**Table 3** Time input types
+
+| Example                              | Description                             |
+| :----------------------------------- | :-------------------------------------- |
+| 05:06.8                              | ISO 8601                                |
+| 4:05:06                              | ISO 8601                                |
+| 4:05                                 | ISO 8601                                |
+| 40506                                | ISO 8601                                |
+| 4:05 AM                              | Same as 04:05. AM does not affect value |
+| 4:05 PM                              | Same as 16:05. Input hour must be <= 12 |
+| 04:05:06.789-8                       | ISO 8601                                |
+| 04:05:06-08:00                       | ISO 8601                                |
+| 04:05-08:00                          | ISO 8601                                |
+| 040506-08                            | ISO 8601                                |
+| 04:05:06 PST                         | Time zone specified by abbreviation     |
+| 2003-04-12 04:05:06 America/New_York | Time zone specified by full name        |
+
+**Table 4** Time zone input types
+
+| Example          | Description                              |
+| :--------------- | :--------------------------------------- |
+| PST              | Abbreviation (for Pacific Standard Time) |
+| America/New_York | Full time zone name                      |
+| -8:00            | ISO-8601 offset for PST                  |
+| -800             | ISO-8601 offset for PST                  |
+| -8               | ISO-8601 offset for PST                  |
+
+Examples
+
+```sql
+mogdb=# SELECT time '04:05:06';
+   time
+----------
+ 04:05:06
+(1 row)
+
+mogdb=# SELECT time '04:05:06 PST';
+   time
+----------
+ 04:05:06
+(1 row)
+
+mogdb=# SELECT time with time zone '04:05:06 PST';
+   timetz
+-------------
+ 04:05:06-08
+(1 row)
+```
+
+## Special Values
+
+The special values supported by MogDB are converted to common date/time values when being read. For details, see Table 5.
+
+**Table 5** Special values
+
+| Input String | Applicable Type       | Description                                    |
+| :----------- | :-------------------- | :--------------------------------------------- |
+| epoch        | date, timestamp       | 1970-01-01 00:00:00+00 (Unix system time zero) |
+| infinity     | timestamp             | Later than any other timestamps                |
+| -infinity    | timestamp             | Earlier than any other timestamps              |
+| now          | date, time, timestamp | Start time of the current transaction          |
+| today        | date, timestamp       | Midnight today                                 |
+| tomorrow     | date, timestamp       | Midnight tomorrow                              |
+| yesterday    | date, timestamp       | Midnight yesterday                             |
+| allballs     | time                  | 00:00:00.00 UTC                                |
+
+## Interval Input
+
+The input of **reltime** can be any valid interval in text format. It can be a number (negative numbers and decimals are also allowed) or a specific time, which must be in SQL standard format, ISO-8601 format, or POSTGRES format. In addition, the text input needs to be enclosed with single quotation marks (").
+
+For details, see Table 6 Interval input.
+
+**Table 6** Interval input
+
+<table>
+    <tr>
+        <th>Input</th>
+        <th>Output</th>
+        <th>Description</th>
+    </tr>
+    <tr>
+        <td>60</td>
+        <td>2 mons</td>
+        <td rowspan="3">Numbers are used to indicate intervals. The default unit is day. Decimals and negative numbers are allowed. Particularly, a negative interval syntactically means how long before.</td>
+    </tr>
+    <tr>
+        <td>31.25</td>
+        <td>1 mons 1 days 06:00:00</td>
+    </tr>
+    <tr>
+        <td>-365</td>
+        <td>-12 mons -5 days</td>
+    </tr>
+    <tr>
+        <td>1 years 1 mons 8 days 12:00:00</td>
+        <td>1 years 1 mons 8 days 12:00:00</td>
+        <td rowspan="3">Intervals are in POSTGRES format. They can contain both positive and negative numbers and are case-insensitive. Output is a simplified POSTGRES interval converted from the input.</td>
+    </tr>
+    <tr>
+        <td>-13 months -10 hours</td>
+        <td>-1 years -25 days -04:00:00</td>
+    </tr>
+    <tr>
+        <td>-2 YEARS +5 MONTHS 10 DAYS</td>
+        <td>-1 years -6 mons -25 days -06:00:00</td>
+    </tr>
+    <tr>
+        <td>P-1.1Y10M</td>
+        <td>-3 mons -5 days -06:00:00</td>
+        <td rowspan="2">Intervals are in ISO-8601 format. They can contain both positive and negative numbers and are case-insensitive. Output is a simplified POSTGRES interval converted from the input.</td>
+    </tr>
+    <tr>
+        <td>-12H</td>
+        <td>-12:00:00</td>
+    </tr>
+</table>
+
+Examples
+
+```sql
+-- Create a table.
+mogdb=# CREATE TABLE reltime_type_tab(col1 character(30), col2 reltime);
+
+-- Insert data.
+mogdb=# INSERT INTO reltime_type_tab VALUES ('90', '90');
+mogdb=# INSERT INTO reltime_type_tab VALUES ('-366', '-366');
+mogdb=# INSERT INTO reltime_type_tab VALUES ('1975.25', '1975.25');
+mogdb=# INSERT INTO reltime_type_tab VALUES ('-2 YEARS +5 MONTHS 10 DAYS', '-2 YEARS +5 MONTHS 10 DAYS');
+mogdb=# INSERT INTO reltime_type_tab VALUES ('30 DAYS 12:00:00', '30 DAYS 12:00:00');
+mogdb=# INSERT INTO reltime_type_tab VALUES ('P-1.1Y10M', 'P-1.1Y10M');
+
+-- View data.
+mogdb=# SELECT * FROM reltime_type_tab;
+              col1              |                col2
+--------------------------------+-------------------------------------
+ 1975.25                        | 5 years 4 mons 29 days
+ -2 YEARS +5 MONTHS 10 DAYS     | -1 years -6 mons -25 days -06:00:00
+ P-1.1Y10M                      | -3 mons -5 days -06:00:00
+ -366                           | -1 years -18:00:00
+ 90                             | 3 mons
+ 30 DAYS 12:00:00               | 1 mon 12:00:00
+(6 rows)
+
+-- Drop the table.
+mogdb=# DROP TABLE reltime_type_tab;
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/7-geometric.md b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/7-geometric.md
new file mode 100644
index 0000000000000000000000000000000000000000..97fa4ea7b9516c68ea35bc4b5b1c5d676a4f53eb
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/7-geometric.md
@@ -0,0 +1,118 @@
+---
+title: Geometric
+summary: Geometric
+author: Guo Huan
+date: 2021-04-06
+---
+
+# Geometric
+
+Table 1 lists the geometric types that can be used in MogDB. The most fundamental type, the point, forms the basis for all of the other types.
+
+**Table 1** Geometric types
+
+| Name    | Storage Space | Description                      | Representation                      |
+| :------ | :------------ | :------------------------------- | :---------------------------------- |
+| point   | 16 bytes      | Point on a plane                 | (x,y)                               |
+| lseg    | 32 bytes      | Finite line segment              | ((x1,y1),(x2,y2))                   |
+| box     | 32 bytes      | Rectangle                        | ((x1,y1),(x2,y2))                   |
+| path    | 16+16n bytes  | Closed path (similar to polygon) | ((x1,y1),…)                         |
+| path    | 16+16n bytes  | Open path                        | [(x1,y1),…]                         |
+| polygon | 40+16n bytes  | Polygon (similar to closed path) | ((x1,y1),…)                         |
+| circle  | 24 bytes      | Circle                           | <(x,y),r> (center point and radius) |
+
+A rich set of functions and operators is available in MogDB to perform various geometric operations, such as scaling, translation, rotation, and determining intersections. For details, see Geometric Functions and Operators.
+
+## Points
+
+Points are the fundamental two-dimensional building block for geometric types. Values of the **point** type are specified using either of the following syntax:
+
+```sql
+( x , y )
+x , y
+```
+
+where x and y are the respective coordinates, as floating-point numbers.
+
+Points are output using the first syntax.
+
+## Line Segments
+
+Line segments (**lseg**) are represented by pairs of points. Values of the **lseg** type are specified using any of the following syntax:
+
+```sql
+[ ( x1 , y1 ) , ( x2 , y2 ) ]
+( ( x1 , y1 ) , ( x2 , y2 ) )
+( x1 , y1 ) , ( x2 , y2 )
+x1 , y1   ,   x2 , y2
+```
+
+where (x1,y1) and (x2,y2) are the end points of the line segment.
+
+Line segments are output using the first syntax.
+
+## Boxes
+
+Boxes are represented by pairs of points that are opposite corners of the box. Values of the **box** type are specified using any of the following syntax:
+
+```
+( ( x1 , y1 ) , ( x2 , y2 ) )
+( x1 , y1 ) , ( x2 , y2 )
+x1 , y1   ,   x2 , y2
+```
+
+where (x1,y1) and (x2,y2) are any two opposite corners of the box.
+
+Boxes are output using the second syntax.
+
+Any two opposite corners can be supplied on input, but in this order, the values will be reordered as needed to store the upper right and lower left corners.
+
+## Paths
+
+Paths are represented by lists of connected points. Paths can be open, where the first and last points in the list are considered not connected, or closed, where the first and last points are considered connected.
+
+Values of the **path** type are specified using any of the following syntax:
+
+```
+[ ( x1 , y1 ) , ... , ( xn , yn ) ]
+( ( x1 , y1 ) , ... , ( xn , yn ) )
+( x1 , y1 ) , ... , ( xn , yn )
+( x1 , y1   , ... ,   xn , yn )
+x1 , y1   , ... ,   xn , yn
+```
+
+where the points are the end points of the line segments comprising the path. Square brackets ([]) indicate an open path, while parentheses (()) indicate a closed path. When the outermost parentheses are omitted, as in the third through fifth syntax, a closed path is assumed.
+
+Paths are output using the first or second syntax.
+
+## Polygons
+
+Polygons are represented by lists of points (the vertexes of the polygon). Polygons are very similar to closed paths, but are stored differently and have their own set of support functions.
+
+Values of the **polygon** type are specified using any of the following syntax:
+
+```
+( ( x1 , y1 ) , ... , ( xn , yn ) )
+( x1 , y1 ) , ... , ( xn , yn )
+( x1 , y1   , ... ,   xn , yn )
+x1 , y1   , ... ,   xn , yn
+```
+
+where the points are the end points of the line segments comprising the boundary of the polygon.
+
+Polygons are output using the first syntax.
+
+## Circles
+
+Circles are represented by a center point and radius. Values of the **circle** type are specified using any of the following syntax:
+
+```
+< ( x , y ) , r >
+( ( x , y ) , r )
+( x , y ) , r
+x , y   , r
+```
+
+where **(x,y)** is the center point and **r** is the radius of the circle.
+
+Circles are output using the first syntax.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/8-network-address.md b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/8-network-address.md
new file mode 100644
index 0000000000000000000000000000000000000000..ca8b613e060d60e73bb9f15cb75b474341f9aad7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/8-network-address.md
@@ -0,0 +1,67 @@
+---
+title: Network Address
+summary: Network Address
+author: Guo Huan
+date: 2021-04-06
+---
+
+# Network Address
+
+MogDB offers data types to store IPv4, IPv6, and MAC addresses.
+
+It is better to use these types instead of plain text types to store network addresses, because these types offer input error checking and specialized operators and functions.
+
+**Table 1** Network address types
+
+| Name    | Storage Space | Description                     |
+| :------ | :------------ | :------------------------------ |
+| cidr    | 7 or 19 bytes | IPv4 or IPv6 networks           |
+| inet    | 7 or 19 bytes | IPv4 or IPv6 hosts and networks |
+| macaddr | 6 bytes       | MAC address                     |
+
+When sorting **inet** or **cidr** data types, IPv4 addresses will always sort before IPv6 addresses, including IPv4 addresses encapsulated or mapped to IPv6 addresses, such as ::10.2.3.4 or ::ffff:10.4.3.2.
+
+## cidr
+
+The **cidr** type (Classless Inter-Domain Routing) holds an IPv4 or IPv6 network specification. The format for specifying networks is **address/y** where **address** is the network represented as an IPv4 or IPv6 address, and **y** is the number of bits in the netmask. If **y** is omitted, it is calculated using assumptions from the older classful network numbering system, except it will be at least large enough to include all of the octets written in the input.
+
+**Table 2** **cidr** type input examples
+
+| cidr Input                           | cidr Output                          | abbrev(cidr)                     |
+| :----------------------------------- | :----------------------------------- | :------------------------------- |
+| 192.168.100.128/25                   | 192.168.100.128/25                   | 192.168.100.128/25               |
+| 192.168/24                           | 192.168.0.0/24                       | 192.168.0/24                     |
+| 192.168/25                           | 192.168.0.0/25                       | 192.168.0.0/25                   |
+| 192.168.1                            | 192.168.1.0/24                       | 192.168.1/24                     |
+| 192.168                              | 192.168.0.0/24                       | 192.168.0/24                     |
+| 10.1.2                               | 10.1.2.0/24                          | 10.1.2/24                        |
+| 10.1                                 | 10.1.0.0/16                          | 10.1/16                          |
+| 10                                   | 10.0.0.0/8                           | 10/8                             |
+| 10.1.2.3/32                          | 10.1.2.3/32                          | 10.1.2.3/32                      |
+| 2001:4f8:3:ba::/64                   | 2001:4f8:3:ba::/64                   | 2001:4f8:3:ba::/64               |
+| 2001:4f8:3:ba:2e0:81ff:fe22:d1f1/128 | 2001:4f8:3:ba:2e0:81ff:fe22:d1f1/128 | 2001:4f8:3:ba:2e0:81ff:fe22:d1f1 |
+| ::ffff:1.2.3.0/120                   | ::ffff:1.2.3.0/120                   | ::ffff:1.2.3⁄120                 |
+| ::ffff:1.2.3.0/128                   | ::ffff:1.2.3.0/128                   | ::ffff:1.2.3.0/128               |
+
+## inet
+
+The **inet** type holds an IPv4 or IPv6 host address, and optionally its subnet, all in one field. The subnet is represented by the number of network address bits present in the host address (the "netmask"). If the netmask is 32 and the address is IPv4, then the value does not indicate a subnet, only a single host. In IPv6, the address length is 128 bits, so 128 bits specify a unique host address.
+
+The input format for this type is **address/y** where address is an IPv4 or IPv6 address and **y** is the number of bits in the netmask. If the **/y** portion is missing, the netmask is 32 for IPv4 and 128 for IPv6, so the value represents just a single host. On display, the **/y** portion is suppressed if the netmask specifies a single host.
+
+The essential difference between the **inet** and **cidr** data types is that **inet** accepts values with nonzero bits to the right of the netmask, whereas **cidr** does not.
+
+## macaddr
+
+The **macaddr** type stores MAC addresses, known for example from Ethernet card hardware addresses (although MAC addresses are used for other purposes as well). Input is accepted in the following formats:
+
+```
+'08:00:2b:01:02:03'
+'08-00-2b-01-02-03'
+'08002b:010203'
+'08002b-010203'
+'0800.2b01.0203'
+'08002b010203'
+```
+
+These examples would all specify the same address. Upper and lower cases are accepted for the digits a through f. Output is always in the first of the forms shown.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/9-bit-string-types.md b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/9-bit-string-types.md
new file mode 100644
index 0000000000000000000000000000000000000000..ea92164a698570b117b290b716d78d6a5fd09bea
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/supported-data-types/9-bit-string-types.md
@@ -0,0 +1,50 @@
+---
+title: Bit String Types
+summary: Bit String Types
+author: Guo Huan
+date: 2021-04-06
+---
+
+# Bit String Types
+
+Bit strings are strings of 1's and 0's. They can be used to store bit masks.
+
+MogDB supports two bit string types: bit(n) and bit varying(n), in which **n** is a positive integer.
+
+The **bit** type data must match the length **n** exactly. It is an error to attempt to store shorter or longer bit strings. The **bit varying** data is of variable length up to the maximum length **n**; longer strings will be rejected. Writing **bit** without a length is equivalent to **bit(1)**, while **bit varying** without a length specification means unlimited length.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> If one explicitly casts a bit-string value to **bit(n)**, it will be truncated or zero-padded on the right to be exactly **n** bits, without raising an error.
+> Similarly, if one explicitly casts a bit-string value to **bit varying(n)**, it will be truncated on the right if it is more than **n** bits.
+
+```sql
+-- Create a table.
+mogdb=# CREATE TABLE bit_type_t1
+(
+    BT_COL1 INTEGER,
+    BT_COL2 BIT(3),
+    BT_COL3 BIT VARYING(5)
+) ;
+
+-- Insert data.
+mogdb=# INSERT INTO bit_type_t1 VALUES(1, B'101', B'00');
+
+-- Specify the type length. An error is reported if an inserted string exceeds this length.
+mogdb=# INSERT INTO bit_type_t1 VALUES(2, B'10', B'101');
+ERROR:  bit string length 2 does not match type bit(3)
+CONTEXT:  referenced column: bt_col2
+
+-- Specify the type length. Data is converted if it exceeds this length.
+mogdb=# INSERT INTO bit_type_t1 VALUES(2, B'10'::bit(3), B'101');
+
+-- View data.
+mogdb=# SELECT * FROM bit_type_t1;
+ bt_col1 | bt_col2 | bt_col3
+---------+---------+---------
+       1 | 101     | 00
+       2 | 100     | 101
+(2 rows)
+
+-- Delete the table.
+mogdb=# DROP TABLE bit_type_t1;
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/overview-of-system-catalogs-and-system-views.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/overview-of-system-catalogs-and-system-views.md
new file mode 100644
index 0000000000000000000000000000000000000000..f7475b4afacb79493422fd2244c8bec830703a3e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/overview-of-system-catalogs-and-system-views.md
@@ -0,0 +1,110 @@
+---
+title: Overview of System Catalogs and System Views
+summary: Overview of System Catalogs and System Views
+author: Guo Huan
+date: 2021-04-19
+---
+
+# Overview of System Catalogs and System Views
+
+System catalogs store structured metadata of MogDB. They are the source of information used by MogDB to control system running and are a core component of the database system.
+
+System views provide ways to query the system catalogs and internal database status.
+
+System catalogs and views are visible to either system administrators or all users. Some system catalogs and views have marked the need of administrator permissions, so they are accessible only to administrators.
+
+You can delete and re-create system catalogs, add columns to them, and insert and update values in them, but doing so may make system information inconsistent and cause system faults. Generally, users should not modify system catalogs or system views, or rename their schemas. They are automatically maintained by the system.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> Do not add, delete, or modify system catalogs because doing so will result in exceptions or even MogDB unavailability.
+
+## Updatable-views Supported
+
+View updatable means that the user can perform INSERT/UPDATE/DELETE operations on the base table corresponding to the view through the view to update the data of the base table.
+
+In order to make the view updatable, the rows in the view must have one-to-one mapping relationship with the data rows in the base table. Specifically, the view cannot be updated when the following content exists in the view:
+
++ Aggregate functions or window functions, such as sum, count, min, max, avg, etc.
++ DISTINCT statement
++ HAVING, GROUP BY, START WITH, CONNECT BY
++ UNION, UNION ALL, INTERSECT, EXCEPT
++ There is a subquery in the selected column.
++ There are non-updatable views in the FROM clause.
++ The table in the FROM clause is referenced in the subquery of the WHERE clause.
++ The columns defined in the view are generated by functions or expressions, such as `decode(...)`.
++ For JOIN views
+
+  + There must be no less than one base table with a unique key or primary key when DML is executed for a view on multiple jointed tables.
+  + Any INSERT, UPDATE or DELETE operation on a view on multiple joined tables can only modify one base table at a time.
+
+## Examples
+
+### INSERT VIEW
+
+```sql
+CREATE TABLE IF NOT EXISTS table1(id int, a char(6), b varchar(6), c varchar(6));
+
+INSERT INTO table1 VALUES(1, reverse('123A78'), '123A78', '1sdfBB');
+INSERT INTO table1 VALUES(2, reverse('E3gw78'), 'E3g78', 'lkoier');
+INSERT INTO table1 VALUES(3, reverse('HHiiw6'), 'Hiw6', '23fdsg');
+
+CREATE VIEW test_view AS SELECT * FROM table1 WHERE id > 1;
+
+INSERT INTO test_view VALUES(4, '2sdafd', '23ata', 'dstsee'); 
+
+SELECT * FROM table1 WHERE id = 4;
+ id |   a    |   b   |   c    
+----+--------+-------+--------
+  4 | 2sdafd | 23ata | dstsee
+(1 row)
+
+DROP VIEW IF EXISTS test_view;
+DROP TABLE IF EXISTS table1;
+```
+
+### UPDATE VIEW
+
+```sql
+CREATE TABLE IF NOT EXISTS table1(id int, a char(6), b varchar(6), c varchar(6));
+INSERT INTO table1 VALUES(1, reverse('123A78'), '123A78', '1sdfBB');
+INSERT INTO table1 VALUES(2, reverse('E3gw78'), 'E3g78', 'lkoier');
+INSERT INTO table1 VALUES(3, reverse('HHiiw6'), 'Hiw6', '23fdsg');
+
+CREATE VIEW test_view AS SELECT * FROM table1 WHERE id > 1;
+
+UPDATE test_view SET a = '2222' WHERE id = 2;
+
+SELECT * FROM table1;
+ id |   a    |   b    |   c    
+----+--------+--------+--------
+  1 | 87A321 | 123A78 | 1sdfBB
+  3 | 6wiiHH | Hiw6   | 23fdsg
+  2 | 2222   | E3g78  | lkoier
+(3 rows)
+
+DROP VIEW IF EXISTS test_view;
+DROP TABLE IF EXISTS table1;
+```
+
+### DELETE VIEW
+
+```sql
+CREATE TABLE IF NOT EXISTS table1(id int, a char(6), b varchar(6), c varchar(6));
+
+INSERT INTO table1 VALUES(1, reverse('123A78'), '123A78', '1sdfBB');
+INSERT INTO table1 VALUES(2, reverse('E3gw78'), 'E3g78', 'lkoier');
+INSERT INTO table1 VALUES(3, reverse('HHiiw6'), 'Hiw6', '23fdsg');
+
+CREATE VIEW test_view AS SELECT * FROM table1 WHERE id > 1;
+
+DELETE FROM test_view WHERE id = 2; 
+
+SELECT * FROM table1 WHERE id > 1;
+ id |   a    |  b   |   c    
+----+--------+------+--------
+  3 | 6wiiHH | Hiw6 | 23fdsg
+(1 row)
+
+DROP VIEW IF EXISTS test_view;
+DROP TABLE IF EXISTS table1;
+```
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY.md
new file mode 100644
index 0000000000000000000000000000000000000000..e66ac830612b5a3474ef90ae9011b15ac7087de7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY.md
@@ -0,0 +1,20 @@
+---
+title: GS_AUDITING_POLICY
+summary: GS_AUDITING_POLICY
+author: Guo Huan
+date: 2021-06-15
+---
+
+# GS_AUDITING_POLICY
+
+**GS_AUDITING_POLICY** records the main information about the unified audit. Each record corresponds to a design policy. Only the system administrator or security policy administrator can access this system catalog.
+
+**Table 1** GS_AUDITING_POLICY columns
+
+| Name        | Type                        | Description                         |
+| :---------- | :-------------------------- | :-----------------------------------|
+| oid         | oid                         | Row identifier (hidden attribute, which must be specified)   |
+| polname     | name                        | Policy name, which must be unique                            |
+| polcomments | name                        | Policy description field, which records policy-related description information and is represented by the **COMMENTS** keyword |
+| modifydate  | timestamp without time zone | The latest timestamp when a policy is created or modified    |
+| polenabled  | boolean                     | Specifies whether to enable the policy.                      |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY_ACCESS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY_ACCESS.md
new file mode 100644
index 0000000000000000000000000000000000000000..46d5e63f0c47d1bf246ac59e7615542fc6d2b26b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY_ACCESS.md
@@ -0,0 +1,20 @@
+---
+title: GS_AUDITING_POLICY_ACCESS
+summary: GS_AUDITING_POLICY_ACCESS
+author: Guo Huan
+date: 2021-06-15
+---
+
+# GS_AUDITING_POLICY_ACCESS
+
+**GS_AUDITING_POLICY_ACCESS** records the DML database operations about the unified audit. Only the system administrator or security policy administrator can access this system catalog.
+
+**Table 1** GS_AUDITING_POLICY_ACCESS columns
+
+| Name       | Type                        | Description                                                  |
+| :--------- | :-------------------------- | :----------------------------------------------------------- |
+| oid        | oid                         | Row identifier (hidden attribute, which must be specified)   |
+| accesstype | name                        | DML database operation type. For example, SELECT, INSERT, and DELETE. |
+| labelname  | name                        | Specifies the resource label name. This parameter corresponds to the **polname** column in the **GS_AUDITING_POLICY** system catalog. |
+| policyoid  | oid                         | This parameter corresponds to OIDs in the **GS_AUDITING_POLICY** system catalog. |
+| modifydate | timestamp without time zone | The latest creation or modification timestamp.               |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY_FILTERS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY_FILTERS.md
new file mode 100644
index 0000000000000000000000000000000000000000..3a169ab81fe1f50be964429121396d32533fc166
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY_FILTERS.md
@@ -0,0 +1,21 @@
+---
+title: GS_AUDITING_POLICY_FILTERS
+summary: GS_AUDITING_POLICY_FILTERS
+author: Guo Huan
+date: 2021-06-15
+---
+
+# GS_AUDITING_POLICY_FILTERS
+
+**GS_AUDITING_POLICY_FILTERS** records the filtering policies about the unified audit. Each record corresponds to a design policy. Only the system administrator or security policy administrator can access this system catalog.
+
+**Table 1** GS_AUDITING_POLICY_FILTERS columns
+
+| Name            | Type      | Description                                                  |
+| :-------------- | :-------- | :----------------------------------------------------------- |
+| oid             | oid       | Row identifier (hidden attribute, which must be specified)   |
+| filtertype      | name      | Filter type. Currently, the value is **logical_expr**.       |
+| labelname       | name      | Name. Currently, the value is **logical_expr**.              |
+| policyoid       | oid       | OID of the audit policy, corresponding to the OID in the **GS_AUDITING_POLICY** system catalog |
+| modifydate      | timestamp | The latest creation or modification timestamp.               |
+| logicaloperator | text      | Logical character string of a filter criterion.              |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY_PRIVILEGES.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY_PRIVILEGES.md
new file mode 100644
index 0000000000000000000000000000000000000000..5b39989dbe383d63ed07322316b9da3915d66889
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY_PRIVILEGES.md
@@ -0,0 +1,20 @@
+---
+title: GS_AUDITING_POLICY_PRIVILEGES
+summary: GS_AUDITING_POLICY_PRIVILEGES
+author: Guo Huan
+date: 2021-06-07
+---
+
+# GS_AUDITING_POLICY_PRIVILEGES
+
+**GS_AUDITING_POLICY_PRIVILEGES** records the DDL database operations about the unified audit. Each record corresponds to a design policy. Only the system administrator or security policy administrator can access this system catalog.
+
+**Table 1** GS_AUDITING_POLICY_PRIVI columns
+
+| Name          | Type      | Description                                                  |
+| :------------ | :-------- | :----------------------------------------------------------- |
+| oid           | oid       | Row identifier (hidden attribute, which must be specified)   |
+| privilegetype | name      | DDL database operation type. For example, CREATE, ALTER, and DROP. |
+| labelname     | name      | Specifies the resource label name. This parameter corresponds to the **polname** column in the **GS_AUDITING_POLICY** system catalog. |
+| policyoid     | oid       | This parameter corresponds to OIDs in the **GS_AUDITING_POLICY** system catalog. |
+| modifydate    | timestamp | Latest creation or modification timestamp.                   |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_CLIENT_GLOBAL_KEYS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_CLIENT_GLOBAL_KEYS.md
new file mode 100644
index 0000000000000000000000000000000000000000..3bb194fd019f45123eaec74e56335ba5402632fc
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_CLIENT_GLOBAL_KEYS.md
@@ -0,0 +1,21 @@
+---
+title: GS_CLIENT_GLOBAL_KEYS
+summary: GS_CLIENT_GLOBAL_KEYS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_CLIENT_GLOBAL_KEYS
+
+**GS_CLIENT_GLOBAL_KEYS** records information about the CMK in the encrypted equality feature. Each record corresponds to a CMK.
+
+**Table 1** GS_CLIENT_GLOBAL_KEYS columns
+
+| Name            | Type      | Description                                              |
+| :-------------- | :-------- | :------------------------------------------------------- |
+| oid             | oid       | Row identifier (hidden column)                           |
+| global_key_name | name      | CMK name                                                 |
+| key_namespace   | oid       | A namespace OID that contains this CMK                   |
+| key_owner       | oid       | CMK owner                                                |
+| key_acl         | aclitem[] | Access permissions that this key should have on creation |
+| create_date     | timestamp | Time when a key is created                               |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_CLIENT_GLOBAL_KEYS_ARGS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_CLIENT_GLOBAL_KEYS_ARGS.md
new file mode 100644
index 0000000000000000000000000000000000000000..e483d5f82dc490e8be5b4683aa299cb40f41524f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_CLIENT_GLOBAL_KEYS_ARGS.md
@@ -0,0 +1,20 @@
+---
+title: GS_CLIENT_GLOBAL_KEYS_ARGS
+summary: GS_CLIENT_GLOBAL_KEYS_ARGS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_CLIENT_GLOBAL_KEYS_ARGS
+
+**GS_CLIENT_GLOBAL_KEYS_ARGS** records the metadata about the CMK in the encrypted equality feature. Each record corresponds to a key-value pair of the CMK.
+
+**Table 1** GS_CLIENT_GLOBAL_KEYS_ARGS columns
+
+| Name          | Type  | Description                    |
+| :------------ | :---- | :----------------------------- |
+| oid           | oid   | Row identifier (hidden column) |
+| global_key_id | oid   | CMK OID                        |
+| function_name | name  | The value is **encryption**.   |
+| key           | name  | CMK metadata name              |
+| value         | bytea | Value of the CMK metadata name |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_COLUMN_KEYS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_COLUMN_KEYS.md
new file mode 100644
index 0000000000000000000000000000000000000000..c966a19a4838bd6fd3aa3a9c8f30e6a020f24a64
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_COLUMN_KEYS.md
@@ -0,0 +1,23 @@
+---
+title: GS_COLUMN_KEYS
+summary: GS_COLUMN_KEYS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_COLUMN_KEYS
+
+**GS_COLUMN_KEYS** records information about the CEK in the encrypted equality feature. Each record corresponds to a CEK.
+
+**Table 1** GS_COLUMN_KEYS columns
+
+| Name                      | Type      | Description                                                  |
+| :------------------------ | :-------- | :----------------------------------------------------------- |
+| oid                       | oid       | Row identifier (hidden column)                               |
+| column_key_name           | name      | CEK name                                                     |
+| column_key_distributed_id | oid       | ID obtained based on the hash value of the fully qualified domain name (FQDN) of the CEK |
+| global_key_id             | oid       | A foreign key, which is the CMK OID.                         |
+| key_namespace             | oid       | A namespace OID that contains this CEK                       |
+| key_owner                 | oid       | CEK owner                                                    |
+| create_date               | timestamp | Time when a CEK is created                                   |
+| key_acl                   | aclitem[] | Access permissions that this CEK should have on creation     |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_COLUMN_KEYS_ARGS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_COLUMN_KEYS_ARGS.md
new file mode 100644
index 0000000000000000000000000000000000000000..21c3d0c050a4c43c10d18f2dbee5c7e7d16cc825
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_COLUMN_KEYS_ARGS.md
@@ -0,0 +1,20 @@
+---
+title: GS_COLUMN_KEYS_ARGS
+summary: GS_COLUMN_KEYS_ARGS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_COLUMN_KEYS_ARGS
+
+**GS_COLUMN_KEYS_ARGS** records the metadata about the CMK in the encrypted equality feature. Each record corresponds to a key-value pair of the CMK.
+
+**Table 1** GS_COLUMN_KEYS_ARGS columns
+
+| Name          | Type  | Description                    |
+| :------------ | :---- | :----------------------------- |
+| oid           | oid   | Row identifier (hidden column) |
+| column_key_id | oid   | CEK OID                        |
+| function_name | name  | The value is **encryption**.   |
+| key           | name  | CEK metadata name              |
+| value         | bytea | Value of the CEK metadata name |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_ENCRYPTED_COLUMNS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_ENCRYPTED_COLUMNS.md
new file mode 100644
index 0000000000000000000000000000000000000000..fedcd1cddd923dfccbb0ba73b25420ba8d4f3d70
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_ENCRYPTED_COLUMNS.md
@@ -0,0 +1,23 @@
+---
+title: GS_ENCRYPTED_COLUMNS
+summary: GS_ENCRYPTED_COLUMNS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_ENCRYPTED_COLUMNS
+
+**GS_ENCRYPTED_COLUMNS** records information about encrypted columns in the encrypted equality feature. Each record corresponds to an encrypted column.
+
+**Table 1** GS_ENCRYPTED_COLUMNS columns
+
+| Name                   | Type      | Description                                                  |
+| :--------------------- | :-------- | :----------------------------------------------------------- |
+| oid                    | oid       | Row identifier (hidden column)                               |
+| rel_id                 | oid       | Table OID                                                    |
+| column_name            | name      | Name of an encrypted column.                                 |
+| column_key_id          | oid       | A foreign key, which is the CEK OID                          |
+| encryption_type        | int1      | Encryption type. The value can be **2 (DETERMINISTIC)** or **1 (RANDOMIZED)**. |
+| data_type_original_oid | oid       | ID of the original data type of the encrypted column. For details about the value, see **oid** in the [PG_TYPE](PG_TYPE) system catalog. |
+| data_type_original_mod | int4      | Original data type modifier of the encrypted column. For details about the value, see **atttypmod** in the [PG_ATTRIBUTE](PG_ATTRIBUTE) system catalog. The value of **data\_type\_original\_mod** is generally **-1** when data types are not specific. |
+| create_date            | timestamp | Time when an encrypted column is created                     |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_ENCRYPTED_PROC.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_ENCRYPTED_PROC.md
new file mode 100644
index 0000000000000000000000000000000000000000..31b486945602d0694d1466d52a0a09870cfdce5f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_ENCRYPTED_PROC.md
@@ -0,0 +1,20 @@
+---
+title: GS_ENCRYPTED_PROC
+summary: GS_ENCRYPTED_PROC
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# GS_ENCRYPTED_PROC
+
+**GS_ENCRYPTED_PROC** provides information such as the parameters of encrypted functions and stored procedure functions, original data type of return values, and encrypted columns.
+
+**Table 1** GS_ENCRYPTED_PROC columns
+
+| Name                | Type      | Description                                                  |
+| :------------------ | :-------- | :----------------------------------------------------------- |
+| oid                 | oid       | Row identifier (hidden column)                               |
+| func_id             | oid       | OID of the function, corresponding to the OID row identifier in the **pg_proc** system catalog |
+| prorettype_orig     | int4      | Original data type of the return value                       |
+| proargcachedcol     | oidvector | OID of the encrypted column corresponding to the **INPUT** parameter of the function, corresponding to the OID row identifier in the **gs_encrypted_columns** system catalog |
+| proallargtypes_orig | oid[]     | Original data type of all function parameters                |
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_GLOBAL_CHAIN.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_GLOBAL_CHAIN.md
new file mode 100644
index 0000000000000000000000000000000000000000..ce7a27acc2ff3ad33525131eacfff5ee33478880
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_GLOBAL_CHAIN.md
@@ -0,0 +1,26 @@
+---
+title: GS_GLOBAL_CHAIN
+summary: GS_GLOBAL_CHAIN
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# GS_GLOBAL_CHAIN
+
+**GS_GLOBAL_CHAIN** records information about modification operations performed by users on the tamper-proof user table. Each record corresponds to a table-level modification operation. Users with the audit administrator permission can query this system catalog, but no user is allowed to modify this system catalog.
+
+**Table 1** GS_GLOBAL_CHAIN columns
+
+| Name       | Type                     | Description                                                  |
+| :--------- | :----------------------- | :----------------------------------------------------------- |
+| oid        | oid                      | Row identifier (hidden attribute, which must be specified)   |
+| blocknum   | bigint                   | Block number, which is the sequence number of the current user operation recorded in the ledger |
+| dbname     | name                     | Name of the database, to which the modified tamper-proof user table belongs |
+| username   | name                     | Username, which is the name of the user who performs the operation of modifying the user table |
+| starttime  | timestamp with time zone | Latest timestamp when a user performs an operation           |
+| relid      | oid                      | OID of the modified tamper-proof user table                  |
+| relnsp     | name                     | OID of the namespace to which the modified tamper-proof user table belongs |
+| relname    | name                     | User table name, which is the name of the modified tamper-proof user table |
+| relhash    | hash16                   | Table-level hash change amount generated by the current operation |
+| globalhash | hash32                   | Global digest, which is calculated based on the information of the current row and the **globalhash** of the previous row. It connects the entire table to verify the integrity of **GS_GLOBAL_CHAIN** data. |
+| txcommand  | text                     | SQL statement whose operations are recorded                  |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MASKING_POLICY.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MASKING_POLICY.md
new file mode 100644
index 0000000000000000000000000000000000000000..3f0119d88af0f7939b3973309ab895ca37c7db41
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MASKING_POLICY.md
@@ -0,0 +1,20 @@
+---
+title: GS_MASKING_POLICY
+summary: GS_MASKING_POLICY
+author: Guo Huan
+date: 2021-06-15
+---
+
+# GS_MASKING_POLICY
+
+**GS_MASKING_POLICY** records the main information about dynamic data masking policies. Each record corresponds to a masking policy. Only the system administrator or security policy administrator can access this system catalog.
+
+**Table 1** GS_MASKING_POLICY columns
+
+| Name        | Type      | Description                                                  |
+| :---------- | :-------- | :----------------------------------------------------------- |
+| oid         | oid       | Row identifier (hidden attribute, which must be specified)   |
+| polname     | name      | Policy name, which must be unique                            |
+| polcomments | name      | Policy description field, which records policy-related description information and is represented by the **COMMENTS** keyword |
+| modifydate  | timestamp | Latest timestamp when a policy is created or modified.       |
+| polenabled  | Boolean   | Specifies whether to enable the policy.                      |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MASKING_POLICY_ACTIONS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MASKING_POLICY_ACTIONS.md
new file mode 100644
index 0000000000000000000000000000000000000000..d569ad4b3fa6140d2211dc5c564277b3da0d460c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MASKING_POLICY_ACTIONS.md
@@ -0,0 +1,21 @@
+---
+title: GS_MASKING_POLICY_ACTIONS
+summary: GS_MASKING_POLICY_ACTIONS
+author: Guo Huan
+date: 2021-06-15
+---
+
+# GS_MASKING_POLICY_ACTIONS
+
+**GS_MASKING_POLICY_ACTIONS** records the masking actions of a masking policy in the dynamic data masking policies. One masking policy corresponds to one or more rows of records in the catalog. Only the system administrator or security policy administrator can access this system catalog.
+
+**Table 1** GS_MASKING_POLICY_ACTIONS columns
+
+| Name         | Type      | Description                                                  |
+| :----------- | :-------- | :----------------------------------------------------------- |
+| oid          | oid       | Row identifier (hidden attribute, which must be specified)   |
+| actiontype   | name      | Name of a masking function used by a masking policy          |
+| actparams    | name      | Parameter information transferred to a masking function      |
+| actlabelname | name      | Name of a masked label                                       |
+| policyoid    | oid       | OID of a masking policy to which a record belongs, corresponding to the OID in [GS_MASKING_POLICY](GS_MASKING_POLICY) |
+| modifydate   | timestamp | The latest timestamp when a record is created or modified    |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MASKING_POLICY_FILTERS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MASKING_POLICY_FILTERS.md
new file mode 100644
index 0000000000000000000000000000000000000000..f044a61d9ec5675cae9a6f59049bb168b4cf1a81
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MASKING_POLICY_FILTERS.md
@@ -0,0 +1,21 @@
+---
+title: GS_MASKING_POLICY_FILTERS
+summary: GS_MASKING_POLICY_FILTERS
+author: Guo Huan
+date: 2021-06-15
+---
+
+# GS_MASKING_POLICY_FILTERS
+
+**GS_MASKING_POLICY_FILTERS** records the user filtering criteria corresponding to the dynamic data masking policies. The corresponding masking policy takes effect only when the user information meets the filter criteria. Only the system administrator or security policy administrator can access this system catalog.
+
+**Table 1** GS_MASKING_POLICY_FILTERS columns
+
+| Name            | Type      | Description                                                  |
+| :-------------- | :-------- | :----------------------------------------------------------- |
+| oid             | oid       | Row identifier (hidden attribute, which must be specified)   |
+| filtertype      | name      | Filter type. Currently, the value is **logical_expr**.       |
+| filterlabelname | name      | Filtering range. Currently, the value is **logical_expr**.   |
+| policyoid       | oid       | OID of the masking policy to which a user filter criterion belongs, which corresponds to the OID in [GS_MASKING_POLICY](GS_MASKING_POLICY) |
+| modifydate      | timestamp | The latest timestamp when a user filter criterion is created or modified. |
+| logicaloperator | text      | Polish notation of the filter criteria.                      |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MATVIEW.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MATVIEW.md
new file mode 100644
index 0000000000000000000000000000000000000000..aefa12d39d063be599c524595a6eae5c2f4c61dd
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MATVIEW.md
@@ -0,0 +1,21 @@
+---
+title: GS_MATVIEW
+summary: GS_MATVIEW
+author: Guo Huan
+date: 2021-06-15
+---
+
+# GS_MATVIEW
+
+**GS_MATVIEW** provides information about each materialized view in the database.
+
+**Table 1** GS_MATVIEW columns
+
+| Name        | Type      | Description                                                  |
+| :---------- | :-------- | :----------------------------------------------------------- |
+| oid         | oid       | Row identifier (hidden attribute, which must be specified)   |
+| matviewid   | oid       | OID of a materialized view.                                  |
+| mapid       | oid       | OID of a map table associated with a materialized view. Each map table corresponds to one materialized view. If a full materialized view does not correspond to a map table, the value of this column is **0**. |
+| ivm         | boolean   | Type of a materialized view. The value **t** indicates an incremental materialized view, and the value **f** indicates a full materialized view. |
+| needrefresh | boolean   | Reserved column                                              |
+| refreshtime | timestamp | Last time when a materialized view was refreshed. If the materialized view is not refreshed, the value is null. This column is maintained only for incremental materialized views. For full materialized views, the value is null. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MATVIEW_DEPENDENCY.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MATVIEW_DEPENDENCY.md
new file mode 100644
index 0000000000000000000000000000000000000000..7640ca33fa5fe5a6940c4ec086e876b2e993c2fc
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MATVIEW_DEPENDENCY.md
@@ -0,0 +1,20 @@
+---
+title: GS_MATVIEW_DEPENDENCY
+summary: GS_MATVIEW_DEPENDENCY
+author: Guo Huan
+date: 2021-06-07
+---
+
+# GS_MATVIEW_DEPENDENCY
+
+**GS_MATVIEW_DEPENDENCY** provides association information about the base table and mlog table of each materialized view in the database.
+
+**Table 1** GS_MATVIEW_DEPENDENCY columns
+
+| Name      | Type | Description                                                  |
+| :-------- | :--- | :----------------------------------------------------------- |
+| oid       | oid  | Row identifier (hidden attribute, which must be specified)   |
+| matviewid | oid  | OID of a materialized view.                                  |
+| relid     | oid  | OID of a base table of a materialized view.                  |
+| mlogid    | oid  | OID of a mlog table which is the log table of a materialized view. Each mlog table corresponds to one base table. |
+| mxmin     | int4 | Reserved column                                              |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_OPT_MODEL.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_OPT_MODEL.md
new file mode 100644
index 0000000000000000000000000000000000000000..44df73e625e1888101ecaae496e6e3b188fc3623
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_OPT_MODEL.md
@@ -0,0 +1,33 @@
+---
+title: GS_OPT_MODEL
+summary: GS_OPT_MODEL
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_OPT_MODEL
+
+**GS_OPT_MODEL** is a data table used when the AI engine is enabled to predict the planned time. It records the configurations, training results, features, corresponding system functions, and training history of machine learning models.
+
+**Table 1** GS_OPT_MODEL columns
+
+| Name          | Type     | Description                                                  |
+| :------------ | :------- | :----------------------------------------------------------- |
+| oid           | oid      | ID of the database object                                    |
+| template_name | name     | Template name of the machine learning model, which determines the interfaces invoked for training and prediction. Currently, only rlstm is implemented. |
+| model_name    | name     | Model name. Each model corresponds to a set of parameters, training logs, and model coefficients in the AI engine online learning process. The name must be unique. |
+| datname       | name     | Name of the database served by the model. Each model is specific to a single database. This parameter determines data used for training. |
+| ip            | name     | IP address of the host where the AI engine is deployed       |
+| port          | integer  | Listening port number of the AI engine                       |
+| max_epoch     | integer  | Maximum number of iterations in an epoch                     |
+| learning_rate | real     | Learning rate of model training. The default value **1** is recommended. |
+| dim_red       | real     | Number of model feature dimensions whose retention is reduced |
+| hidden_units  | integer  | Number of neurons in the model's hidden layer. If the model cannot be converged for a long time, increase the value of this parameter. |
+| batch_size    | integer  | Size of a batch in each iteration. It is recommended that the size be greater than or equal to the total training data volume to accelerate model convergence. |
+| feature_size  | integer  | Length of the model feature, which is used to trigger retraining. This parameter is automatically updated after model training and does not need to be specified. |
+| available     | boolean  | Whether the model is converged. This parameter does not need to be specified. |
+| Is_training   | boolean  | Whether the model is being trained. This parameter does not need to be specified. |
+| label         | "char"[] | Target task of the model.<br/>- S: startup time<br/>- T: total time<br/>- R: rows<br/>- M: peak memory<br/>Currently, {S, T} or {R} is recommended due to model performance restrictions. |
+| max           | bigint[] | Maximum value of each task label of the model, which is used to trigger retraining. This parameter does not need to be specified. |
+| acc           | real[]   | Accuracy of each model task. This parameter does not need to be specified. |
+| description   | text     | Model comment                                                |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_POLICY_LABEL.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_POLICY_LABEL.md
new file mode 100644
index 0000000000000000000000000000000000000000..8ed16c2c597344fcdb0457b86da99ea0c509d863
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_POLICY_LABEL.md
@@ -0,0 +1,24 @@
+---
+title: GS_POLICY_LABEL
+summary: GS_POLICY_LABEL
+author: Guo Huan
+date: 2021-06-15
+---
+
+# GS_POLICY_LABEL
+
+**GS_POLICY_LABEL** records the resource label configuration information. One resource label corresponds to one or more records, and each record identifies the resource label to which a database resource belongs. Only the system administrator or security policy administrator can access this system catalog.
+
+Fully Qualified Domain Name (FQDN) identifies an absolute path of a database resource.
+
+**Table 1** GS_POLICY_LABEL columns
+
+| Name          | Type | Description                                                  |
+| :------------ | :--- | :----------------------------------------------------------- |
+| oid           | oid  | Row identifier (hidden attribute, which must be specified)   |
+| labelname     | name | Resource label name                                          |
+| labeltype     | name | Resource tag type. Currently, the value is **RESOURCE**.     |
+| fqdnnamespace | oid  | OID of a namespace to which an identified database resource belongs |
+| fqdnid        | oid  | OID of an identified database resource. If the database resource is a column, this column is the OID of the catalog. |
+| relcolumn     | name | Column name. If the identified database resource is a column, this column indicates the column name. Otherwise, this column is empty. |
+| fqdntype      | name | Type of the identified database resource, for example, schema, table, column, or view |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_RECYCLEBIN.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_RECYCLEBIN.md
new file mode 100644
index 0000000000000000000000000000000000000000..dbc3591697a3e032d5aec5ff4a42d69ff202e01a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_RECYCLEBIN.md
@@ -0,0 +1,35 @@
+---
+title: GS_RECYCLEBIN
+summary: GS_RECYCLEBIN
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# GS_RECYCLEBIN
+
+**gs_recyclebin** describes details about objects in the recycle bin.
+
+**Table 1** gs_recyclebin columns
+
+| Name           | Type        | Description                             |
+| :------------- | :---------- | :---------------------------------------|
+| oid            | oid         | System column                                                |
+| rcybaseid      | oid         | Base table object ID, which references **gs_recyclebin.oid** |
+| rcydbid        | oid         | OID of the database to which the current object belongs      |
+| rcyrelid       | oid         | OID of the current object                                    |
+| rcyname        | name        | Name of the object in the recycle bin. The format is `BIN$unique_id$oid$0`. **unique_id** indicates the unique identifier with a maximum of 16 characters, and **oid** indicates the OID. |
+| rcyoriginname  | name        | Original object name                                         |
+| rcyoperation   | "char"      | Operation type<br />- **d**: drop<br />- **t**: truncate     |
+| rcytype        | int         | Object type<br />- **0**: table<br />- **1**: index<br />- **2**: TOAST table<br />- **3**: TOAST index<br />- **4**: sequence, indicating the sequence object that is automatically associated with the serial and bigserial types. |
+| rcyrecyclecsn  | bigint      | CSN when an object is dropped or truncated                   |
+| rcyrecycletime | timestamptz | Time when an object is dropped or truncated                  |
+| rcycreatecsn   | bigint      | CSN when an object is created                                |
+| rcychangecsn   | bigint      | SCN when an object definition is modified                    |
+| rcynamespace   | oid         | OID of the namespace that contains this relationship         |
+| rcyowner       | oid         | Relationship owner                                           |
+| rcytablespace  | oid         | Tablespace where the relationship is stored. If the value is **0**, the default tablespace of the database is used. This column is meaningless if the relationship has no on-disk file. |
+| rcyrelfilenode | oid         | File name of the recycle bin object on a disk, or **0** if none, used to restore the texture file when the **TRUNCATE** object is restored. |
+| rcycanrestore  | bool        | Whether flashback can be performed separately                |
+| rcycanpurge    | bool        | Whether the purge operation can be performed independently   |
+| rcyfrozenxid   | xid32       | All transaction IDs before this one have been replaced with a permanent (frozen) transaction ID in the table. |
+| rcyfrozenxid64 | xid         | All transaction IDs before this one have been replaced with a permanent (frozen) transaction ID in the table. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_TXN_SNAPSHOT.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_TXN_SNAPSHOT.md
new file mode 100644
index 0000000000000000000000000000000000000000..8ad4be96f8b2033781d231e6aec89ce5ac43c09f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_TXN_SNAPSHOT.md
@@ -0,0 +1,19 @@
+---
+title: GS_TXN_SNAPSHOT
+summary: GS_TXN_SNAPSHOT
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# GS_TXN_SNAPSHOT
+
+**GS_TXN_SNAPSHOT** is a timestamp-CSN mapping table. It periodically samples and maintains an appropriate time range to estimate the CSN value corresponding to the timestamp in the range.
+
+**Table 1** GS_TXN_SNAPSHOT columns
+
+| Name        | Data Type   | Description                            |
+| :---------- | :---------- | :------------------------------------- |
+| snptime     | timestamptz | Snapshot time                          |
+| snpxmin     | bigint      | Minimum transaction ID snapshots       |
+| snpcsn      | bigint      | Commit sequence number (CSN) snapshots |
+| snpsnapshot | TEXT        | Serialized snapshot text               |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_EC_OPERATOR_INFO.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_EC_OPERATOR_INFO.md
new file mode 100644
index 0000000000000000000000000000000000000000..e646b9f07146ce982f3ff1491df4dada92848c8c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_EC_OPERATOR_INFO.md
@@ -0,0 +1,29 @@
+---
+title: GS_WLM_EC_OPERATOR_INFO
+summary: GS_WLM_EC_OPERATOR_INFO
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_WLM_EC_OPERATOR_INFO
+
+**GS_WLM_EC_OPERATOR_INFO** records operator information after an Extension Connector job ends. If **enable_resource_record** is set to **on**, the system imports records from **GS_WLM_EC_OPERATOR_HISTORY** to this system catalog every 3 minutes. This operation occupies storage space and affects performance. Only users with the **sysadmin** permission can query this system catalog.
+
+**Table 1** GS_WLM_EC_OPERATOR_INFO columns
+
+| Name                | Type                     | Description                                                  |
+| :------------------ | :----------------------- | :----------------------------------------------------------- |
+| queryid             | bigint                   | Internal query ID used for Extension Connector statement execution |
+| plan_node_id        | integer                  | Plan node ID of the execution plan of an Extension Connector operator |
+| start_time          | timestamp with time zone | Time when the Extension Connector operator starts to process the first data record |
+| duration            | bigint                   | Total execution time of the Extension Connector operator (unit: ms) |
+| tuple_processed     | bigint                   | Number of elements returned by the Extension Connector operator |
+| min_peak_memory     | integer                  | Minimum peak memory used by the Extension Connector operator on all DNs (unit: MB) |
+| max_peak_memory     | integer                  | Maximum peak memory used by the Extension Connector operator on all DNs (unit: MB) |
+| average_peak_memory | integer                  | Average peak memory used by the Extension Connector operator on all DNs (unit: MB) |
+| ec_status           | text                     | Status of the Extension Connector job                        |
+| ec_execute_datanode | text                     | Name of the DN executing the Extension Connector job         |
+| ec_dsn              | text                     | DSN used by the Extension Connector job                      |
+| ec_username         | text                     | Username used by the Extension Connector job to access a remote database instance (the value is null if the remote database instance is SPARK.) |
+| ec_query            | text                     | Statement sent by the Extension Connector job to a remote database instance |
+| ec_libodbc_type     | text                     | Type of the unixODBC driver used by the Extension Connector job |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_INSTANCE_HISTORY.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_INSTANCE_HISTORY.md
new file mode 100644
index 0000000000000000000000000000000000000000..0dbd39a37ad3cdb01d793bf8690b88517efee0db
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_INSTANCE_HISTORY.md
@@ -0,0 +1,30 @@
+---
+title: GS_WLM_INSTANCE_HISTORY
+summary: GS_WLM_INSTANCE_HISTORY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_WLM_INSTANCE_HISTORY
+
+**GS_WLM_INSTANCE_HISTORY** records information about resource usage related to instances (primary database node or database node). Each record in this system catalog indicates resource usage of an instance at a specific time point, including the memory, number of CPU cores, disk I/O, physical I/O of the process, and logical I/O of the process. This system catalog can be queried by users with the **sysadmin** permission only in Postgres.
+
+**Table 1** GS_WLM_INSTANCE_HISTORY columns
+
+| Name          | Type                     | Description                                                  |
+| :------------ | :----------------------- | :----------------------------------------------------------- |
+| instancename  | text                     | Instance name                                                |
+| timestamp     | timestamp with time zone | Timestamp                                                    |
+| used_cpu      | int                      | CPU usage of the instance                                    |
+| free_mem      | int                      | Unused memory of the instance, in MB                         |
+| used_mem      | int                      | Used memory of the instance, in MB                           |
+| io_await      | real                     | Average wait time for an I/O operation on the disk used by the instance. The average value is within 10 seconds. |
+| io_util       | real                     | io_util value of the disk used by the instance. The average value is within 10 seconds. |
+| disk_read     | real                     | Disk read rate of the instance, in KB/s. The average value is within 10 seconds. |
+| disk_write    | real                     | Disk write rate of the instance, in KB/s. The average value is within 10 seconds. |
+| process_read  | bigint                   | Read rate (excluding the number of bytes read from the disk pagecache) of the corresponding instance process that reads data from a disk within 10 seconds, in KB/s |
+| process_write | bigint                   | Write rate (excluding the number of bytes written to the disk pagecache) of the corresponding instance process that writes data to a disk within 10 seconds, in KB/s |
+| logical_read  | bigint                   | Primary database node instance: not collected<br/>Database node instance: logical read byte rate of the instance within the statistical interval (10 seconds), in KB/s |
+| logical_write | bigint                   | Primary database node instance: not collected<br/>Database node instance: logical write byte rate of the instance within the statistical interval (10 seconds), in KB/s |
+| read_counts   | bigint                   | Primary database node instance: not collected<br/>Database node instance: total number of logical read operations of the instance within the statistical interval (10 seconds) |
+| write_counts  | bigint                   | Primary database node instance: not collected<br/>Database node instance: total number of logical write operations of the instance within the statistical interval (10 seconds) |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_OPERATOR_INFO.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_OPERATOR_INFO.md
new file mode 100644
index 0000000000000000000000000000000000000000..fc7506e607fd83a5fb265925e41dc7eb29856fb7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_OPERATOR_INFO.md
@@ -0,0 +1,37 @@
+---
+title: GS_WLM_OPERATOR_INFO
+summary: GS_WLM_OPERATOR_INFO
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_WLM_OPERATOR_INFO
+
+**GS_WLM_OPERATOR_INFO** displays records about operators of completed jobs. The data is dumped from the kernel to the system catalog. This system catalog can be queried by users with the **sysadmin** permission only in Postgres.
+
+**Table 1** GS_WLM_OPERATOR_INFO columns<a id="GS_WLM_OPERATOR_INFO columns"> </a>
+
+| Name                | Type                     | Description                    |
+| :------------------ | :----------------------- | :------------------------------|
+| queryid             | bigint                   | Internal query ID used for statement execution               |
+| pid                 | bigint                   | Thread ID of the backend                                     |
+| plan_node_id        | integer                  | Plan node ID of the execution plan of a query                |
+| plan_node_name      | text                     | Name of the operator corresponding to the plan node ID       |
+| start_time          | timestamp with time zone | Time when an operator starts to process the first data record |
+| duration            | bigint                   | Total execution time of the operator, in ms                  |
+| query_dop           | integer                  | DOP of the operator                                          |
+| estimated_rows      | bigint                   | Number of rows estimated by the optimizer                    |
+| tuple_processed     | bigint                   | Number of elements returned by the operator                  |
+| min_peak_memory     | integer                  | Minimum peak memory used by the operator on database nodes (unit: MB) |
+| max_peak_memory     | integer                  | Maximum peak memory used by the operator on database nodes (unit: MB) |
+| average_peak_memory | integer                  | Average peak memory used by the operator on database nodes (unit: MB) |
+| memory_skew_percent | integer                  | Memory usage skew of the operator among database nodes       |
+| min_spill_size      | integer                  | Minimum spilled data among database nodes when a spill occurs (unit: MB) (default value: **0**) |
+| max_spill_size      | integer                  | Maximum spilled data among database nodes when a spill occurs (unit: MB) (default value: **0**) |
+| average_spill_size  | integer                  | Average spilled data among database nodes when a spill occurs (unit: MB) (default value: **0**) |
+| spill_skew_percent  | integer                  | Database node spill skew when a spill occurs                 |
+| min_cpu_time        | bigint                   | Minimum execution time of the operator on database nodes (unit: ms) |
+| max_cpu_time        | bigint                   | Maximum execution time of the operator on database nodes (unit: ms) |
+| total_cpu_time      | bigint                   | Total execution time of the operator on database nodes (unit: ms) |
+| cpu_skew_percent    | integer                  | Execution time skew among database nodes                     |
+| warning             | text                     | The following warnings are displayed:<br/>- Sort/SetOp/HashAgg/HashJoin spill<br/>- Spill file size large than 256MB<br/>- Broadcast size large than 100MB<br/>- Early spill<br/>- Spill times is greater than 3<br/>- Spill on memory adaptive<br/>- Hash table conflict |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_PLAN_ENCODING_TABLE.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_PLAN_ENCODING_TABLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..f19e46011b7cd51c9aa5dc488b5b71ad8db1e13d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_PLAN_ENCODING_TABLE.md
@@ -0,0 +1,23 @@
+---
+title: GS_WLM_PLAN_ENCODING_TABLE
+summary: GS_WLM_PLAN_ENCODING_TABLE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_WLM_PLAN_ENCODING_TABLE
+
+**GS_WLM_PLAN_ENCODING_TABLE** displays encoding information of the plan operator level and provides the training and prediction sets of label values such as startup time, total time, peak memory, and rows for machine learning models.
+
+**Table 1** GS_WLM_PLAN_ENCODING_TABLE columns
+
+| Name           | Type    | Description                                                  |
+| :------------- | :------ | :----------------------------------------------------------- |
+| queryid        | bigint  | Internal query ID used for statement execution               |
+| plan_node_id   | integer | Plan node ID of the execution plan                           |
+| parent_node_id | integer | Parent node ID of the operator                               |
+| startup_time   | bignit  | Time when the operator starts to process the first data record |
+| total_time     | bigint  | Total execution time of the operator, in ms                  |
+| rows           | bigint  | Number of rows executed by the operator                      |
+| peak_memory    | integer | Maximum peak memory used by the operator on database nodes, in MB |
+| encode         | text    | Encoding information of the operator                         |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_PLAN_OPERATOR_INFO.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_PLAN_OPERATOR_INFO.md
new file mode 100644
index 0000000000000000000000000000000000000000..28895e56976218730cc97f82b9e197a1920cf83e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_PLAN_OPERATOR_INFO.md
@@ -0,0 +1,32 @@
+---
+title: GS_WLM_PLAN_OPERATOR_INFO
+summary: GS_WLM_PLAN_OPERATOR_INFO
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_WLM_PLAN_OPERATOR_INFO
+
+**GS_WLM_PLAN_OPERATOR_INFO** displays records about plan operator levels of completed jobs. Data is dumped from the kernel to this system catalog.
+
+**Table 1** GS_WLM_PLAN_OPERATOR_INFO columns<a id="GS_WLM_PLAN_OPERATOR_INFO columns"> </a>
+
+| Name            | Type    | Description                                                  |
+| :-------------- | :------ | :----------------------------------------------------------- |
+| datname         | name    | Name of the database where the collected plan information is located |
+| queryid         | bigint  | Internal query ID used for statement execution               |
+| plan_node_id    | integer | Plan node ID of the execution plan                           |
+| startup_time    | bigint  | Time when the operator starts to process the first data record |
+| total_time      | bigint  | Total execution time of the operator, in ms                  |
+| actual_rows     | bigint  | Number of rows that are actually executed                    |
+| max_peak_memory | integer | Maximum peak memory used by the operator on database nodes, in MB |
+| query_dop       | integer | DOP of the operator                                          |
+| parent_node_id  | integer | Parent node ID of the operator                               |
+| left_child_id   | integer | Left child node ID of the operator                           |
+| right_child_id  | integer | Right child node ID of the operator                          |
+| operation       | text    | Name of the operation performed by the operator              |
+| orientation     | text    | Alignment mode of the operator                               |
+| strategy        | text    | Implementation method of the operator                        |
+| options         | text    | Selection mode of the operator                               |
+| condition       | text    | Filter criteria of the operator                              |
+| projection      | text    | Mapping relationship of the operator                         |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AGGREGATE.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AGGREGATE.md
new file mode 100644
index 0000000000000000000000000000000000000000..e2b27c85f6a1a5b08e6f366c55a65e322e718161
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AGGREGATE.md
@@ -0,0 +1,25 @@
+---
+title: PG_AGGREGATE
+summary: PG_AGGREGATE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_AGGREGATE
+
+PG_AGGREGATE records information about aggregate functions. Each entry in **PG\_AGGREGATE** is an extension of an entry in **PG\_PROC**. The **PG_PROC** entry carries the aggregate's name, input and output data types, and other information that is similar to ordinary functions.
+
+**Table 1** PG_AGGREGATE columns
+
+| Name             | Type     | Reference       | Description                                                  |
+| :--------------- | :------- | :-------------- | :----------------------------------------------------------- |
+| aggfnoid         | regproc  | PG_PROC.proname | PG_PROC proname of the aggregate function                    |
+| aggtransfn       | regproc  | PG_PROC.proname | Transition function                                          |
+| aggcollectfn     | regproc  | PG_PROC.proname | Collect function                                             |
+| aggfinalfn       | regproc  | PG_PROC.proname | Final function (**0** if none)                               |
+| aggsortop        | oid      | PG_OPERATOR.oid | Associated sort operator (**0** if none)                     |
+| aggtranstype     | oid      | PG_TYPE.oid     | Data type of the aggregate function's internal transition (state) data |
+| agginitval       | text     | -               | Initial value of the transition state. This is a text column containing the initial value in its external string representation. If this column is null, the transition state value starts from null. |
+| agginitcollect   | text     | -               | Initial value of the collection state. This is a text column containing the initial value in its external string representation. If this column is null, the collection state value starts from null. |
+| aggkind          | "char"   | -               | Type of the aggregate function:<br/>- **n**: normal aggregate<br/>- **o**: ordered set aggregate |
+| aggnumdirectargs | smallint | -               | Number of direct parameters (non-aggregation-related parameters) of the aggregate function of the ordered set aggregate type. For an aggregate function of the normal aggregate type, the value is **0**. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AM.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AM.md
new file mode 100644
index 0000000000000000000000000000000000000000..9ebfd7c1ecf0eeaef6cfd28b41fac73256fc8dcb
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AM.md
@@ -0,0 +1,47 @@
+---
+title: PG_AM
+summary: PG_AM
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_AM
+
+**PG_AM** records information about index access methods. There is one row for each index access method supported by the system.
+
+**Table 1** PG_AM columns
+
+| Name            | Type     | Reference       | Description                                                  |
+| :-------------- | :------- | :-------------- | :----------------------------------------------------------- |
+| oid             | oid      | -               | Row identifier (hidden attribute, which must be specified)   |
+| amname          | name     | -               | Name of the access method                                    |
+| amstrategies    | smallint | -               | Number of operator strategies for the access method (**0** if the access method does not have a fixed set of operator strategies) |
+| amsupport       | smallint | -               | Number of support routines for the access method             |
+| amcanorder      | Boolean  | -               | Whether the access method supports ordered scans sorted by the indexed column's value |
+| amcanorderbyop  | Boolean  | -               | Whether the access method supports ordered scans sorted by the result of an operator on the indexed column |
+| amcanbackward   | Boolean  | -               | Whether the access method supports backward scanning         |
+| amcanunique     | Boolean  | -               | Whether the access method supports unique indexes            |
+| amcanmulticol   | Boolean  | -               | Whether the access method supports multi-column indexes      |
+| amoptionalkey   | Boolean  | -               | Whether the access method supports scanning without any constraint for the first index column |
+| amsearcharray   | Boolean  | -               | Whether the access method supports **ScalarArrayOpExpr** searches |
+| amsearchnulls   | Boolean  | -               | Whether the access method supports **IS NULL/NOT NULL** searches |
+| amstorage       | Boolean  | -               | Whether the index storage data type can differ from the column data type |
+| amclusterable   | Boolean  | -               | Whether an index of this type can be clustered on            |
+| ampredlocks     | Boolean  | -               | Whether an index of this type manages fine-grained predicate locks |
+| amkeytype       | oid      | PG_TYPE.oid     | Type of data stored in index (**0** if it is not a fixed type) |
+| aminsert        | regproc  | PG_PROC.proname | "Insert this tuple" function                                 |
+| ambeginscan     | regproc  | PG_PROC.proname | "Prepare for index scan" function                            |
+| amgettuple      | regproc  | PG_PROC.proname | "Next valid tuple" function (**0** if none)                  |
+| amgetbitmap     | regproc  | PG_PROC.proname | "Fetch all valid tuples" function (**0** if none)            |
+| amrescan        | regproc  | PG_PROC.proname | "(Re)start index scan" function                              |
+| amendscan       | regproc  | PG_PROC.proname | "Clean up after index scan" function                         |
+| ammarkpos       | regproc  | PG_PROC.proname | "Mark current scan position" function                        |
+| amrestrpos      | regproc  | PG_PROC.proname | "Restore marked scan position" function                      |
+| ammerge         | regproc  | PG_PROC.proname | "Merge multiple indexes" function                            |
+| ambuild         | regproc  | PG_PROC.proname | "Build new index" function                                   |
+| ambuildempty    | regproc  | PG_PROC.proname | "Build empty index" function                                 |
+| ambulkdelete    | regproc  | PG_PROC.proname | Bulk-delete function                                         |
+| amvacuumcleanup | regproc  | PG_PROC.proname | Post-**VACUUM** cleanup function                             |
+| amcanreturn     | regproc  | PG_PROC.proname | Function to check whether the index supports index-only scans (**0** if none) |
+| amcostestimate  | regproc  | PG_PROC.proname | Function to estimate cost of an index scan                   |
+| amoptions       | regproc  | PG_PROC.proname | Function to parse and validate **reloptions** for an index   |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AMOP.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AMOP.md
new file mode 100644
index 0000000000000000000000000000000000000000..f453b4b10d8cd5c5f6b01089559351dbcf8fb283
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AMOP.md
@@ -0,0 +1,28 @@
+---
+title: PG_AMOP
+summary: PG_AMOP
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_AMOP
+
+**PG_AMOP** records information about operators associated with access method operator families. There is one row for each operator that is a member of an operator family. A family member can be either a search operator or an ordering operator. An operator can appear in more than one family, but cannot appear in more than one search position nor more than one ordering position within a family.
+
+**Table 1** PG_AMOP columns
+
+| Name           | Type     | Reference       | Description                                                  |
+| :------------- | :------- | :-------------- | :----------------------------------------------------------- |
+| oid            | oid      | -               | Row identifier (hidden attribute, which must be specified)   |
+| amopfamily     | oid      | PG_OPFAMILY.oid | Operator family of this entry                                |
+| amoplefttype   | oid      | PG_TYPE.oid     | Left-hand input data type of the operator. For details about the possible values and their description, see **pg_type.h**. |
+| amoprighttype  | oid      | PG_TYPE.oid     | Right-hand input data type of the operator. For details about the possible values and their description, see **pg_type.h**. |
+| amopstrategy   | smallint | -               | Number of operator strategies                                |
+| amoppurpose    | "char"   | -               | Operator purpose, either **s** for search or **o** for ordering |
+| amopopr        | oid      | PG_OPERATOR.oid | OID of the operator                                          |
+| amopmethod     | oid      | PG_AM.oid       | Operator family of the index access method                   |
+| amopsortfamily | oid      | PG_OPFAMILY.oid | The B-tree operator family according to which this entry sorts for an ordering operator (**0** for a search operator) |
+
+A search operator entry indicates that an index of this operator family can be searched to find all rows satisfying **WHERE indexed_column operator constant**. Obviously, such an operator must return a Boolean value, and its left-hand input type must match the index's column data type.
+
+An ordering operator entry indicates that an index of this operator family can be scanned to return rows in the order represented by **ORDER BY indexed_column operator constant**. Such an operator could return any sortable data type, though again its left-hand input type must match the index's column data type. The exact semantics of **ORDER BY** are specified by the **amopsortfamily** column, which must reference the B-tree operator family for the operator's result type.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AMPROC.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AMPROC.md
new file mode 100644
index 0000000000000000000000000000000000000000..2a588eb93f5aa7fecc14b6529d23bd75ccd5d121
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AMPROC.md
@@ -0,0 +1,23 @@
+---
+title:  PG_AMPROC
+summary:  PG_AMPROC
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_AMPROC
+
+**PG_AMPROC** records information about the support procedures associated with the access method operator families. There is one row for each support procedure that belongs to an operator family.
+
+**Table 1** PG_AMPROC columns
+
+| Name            | Type     | Reference       | Description                                                  |
+| :-------------- | :------- | :-------------- | :----------------------------------------------------------- |
+| oid             | oid      | -               | Row identifier (hidden attribute, which must be specified)   |
+| amprocfamily    | oid      | PG_OPFAMILY.oid | Operator family of this entry                                |
+| amproclefttype  | oid      | PG_TYPE.oid     | Left-hand input data type of the associated operator. For details about the possible values and their description, see **pg_type.h**. |
+| amprocrighttype | oid      | PG_TYPE.oid     | Right-hand input data type of the associated operator. For details about the possible values and their description, see **pg_type.h**. |
+| amprocnum       | smallint | -               | Support procedure number                                     |
+| amproc          | regproc  | PG_PROC.proname | OID of the procedure                                         |
+
+The usual interpretation of the **amproclefttype** and **amprocrighttype** columns is that they identify the left and right input types of the operator(s) that a particular support procedure supports. For some access methods, these match the input data type(s) of the support procedure itself; for others not. There is a notion of "default" support procedures for an index, which are those with **amproclefttype** and **amprocrighttype** both equal to the index opclass's **opcintype**.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_APP_WORKLOADGROUP_MAPPING.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_APP_WORKLOADGROUP_MAPPING.md
new file mode 100644
index 0000000000000000000000000000000000000000..493120164ab6637ce5390e27ce8d5ccd5d560942
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_APP_WORKLOADGROUP_MAPPING.md
@@ -0,0 +1,18 @@
+---
+title: PG_APP_WORKLOADGROUP_MAPPING
+summary: PG_APP_WORKLOADGROUP_MAPPING
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_APP_WORKLOADGROUP_MAPPING
+
+**PG_APP_WORKLOADGROUP_MAPPING** provides load mapping group information in the database.
+
+**Table 1** PG_APP_WORKLOADGROUP_MAPPING columns
+
+| Name            | Type | Description                                                |
+| :-------------- | :--- | :--------------------------------------------------------- |
+| oid             | oid  | Row identifier (hidden attribute, which must be specified) |
+| appname         | name | Application name                                           |
+| workload_gpname | name | Mapped workload group name                                 |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_ATTRDEF.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_ATTRDEF.md
new file mode 100644
index 0000000000000000000000000000000000000000..ccf6779e9642e3f8cd1df654648ca7b2f24650f8
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_ATTRDEF.md
@@ -0,0 +1,21 @@
+---
+title: PG_ATTRDEF
+summary: PG_ATTRDEF
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_ATTRDEF
+
+**PG_ATTRDEF** records default values of columns.
+
+**Table 1** PG_ATTRDEF columns
+
+| Name     | Type         | Description                                                  |
+| :------- | :----------- | :----------------------------------------------------------- |
+| oid      | oid          | Row identifier (hidden attribute, which must be specified)   |
+| adrelid  | oid          | Table to which a column belongs                              |
+| adnum    | smallint     | Number of columns                                            |
+| adbin    | pg_node_tree | Internal representation of the default value of a column or of a generated expression |
+| adsrc    | text         | Internal representation of a readable default value or of a generated expression |
+| adgencol | char         | Specifies whether a column is a generated column. The value **s** indicates that the column is a generated column, and the value **'\0** indicates that the column is a common column. The default value is **'\0**. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_ATTRIBUTE.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_ATTRIBUTE.md
new file mode 100644
index 0000000000000000000000000000000000000000..0628387f393d0dc875219fa31b6e880ca5554356
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_ATTRIBUTE.md
@@ -0,0 +1,39 @@
+---
+title: PG_ATTRIBUTE
+summary: PG_ATTRIBUTE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_ATTRIBUTE
+
+**PG_ATTRIBUTE** records information about table columns.
+
+**Table 1** PG_ATTRIBUTE columns
+
+| Name          | Type      | Description                                                  |
+| :------------ | :-------- | :----------------------------------------------------------- |
+| attrelid      | oid       | Table to which a column belongs                              |
+| attname       | name      | Column name                                                  |
+| atttypid      | oid       | Column type                                                  |
+| attstattarget | integer   | Level of details of statistics collected for this column by **ANALYZE**.<br/>- The value **0** indicates that no statistics should be collected.<br/>- A negative value indicates that the system default statistic object is used.<br/>- The exact meaning of positive values is data type-dependent.<br/>For scalar data types, **attstattarget** is both the target number of "most common values" to collect, and the target number of histogram bins to create. |
+| attlen        | smallint  | Copy of **typlen** in **PG_TYPE** of the column's type       |
+| attnum        | smallint  | Number of the column                                         |
+| attndims      | integer   | Number of dimensions if the column is an array (**0** in other cases) |
+| attcacheoff   | integer   | This column is always **-1** on disk. When it is loaded into a row descriptor in the memory, it may be updated to cache the offset of the columns in the row. |
+| atttypmod     | integer   | Type-specific data supplied at the table creation time (for example, the maximum length of a **varchar** column). This column is used as the third parameter when passing to type-specific input functions and length coercion functions. The value will generally be **-1** for types that do not need ATTTYPMOD. |
+| attbyval      | Boolean   | Copy of **typbyval** in **PG_TYPE** of this column's type    |
+| attstorage    | "char"    | Copy of **typstorage** in **PG_TYPE** of this column's type  |
+| attalign      | "char"    | Copy of **typalign** in **PG_TYPE** of this column's type    |
+| attnotnull    | Boolean   | A non-null constraint. It is possible to change this column to enable or disable the constraint. |
+| atthasdef     | Boolean   | This column has a default value, in which case there will be a corresponding entry in the **PG_ATTRDEF** table that actually defines the value. |
+| attisdropped  | Boolean   | Indicates that this column has been deleted and is no longer valid. A deleted column is still physically present in the table but is ignored by the analyzer, so it cannot be accessed through SQL. |
+| attislocal    | Boolean   | Indicates that this column is locally defined in the relationship. Note that a column can be locally defined and inherited simultaneously. |
+| attcmprmode   | tinyint   | Compressed modes for a specific column. The compressed mode includes:<br/>- ATT_CMPR_NOCOMPRESS<br/>- ATT_CMPR_DELTA<br/>- ATT_CMPR_DICTIONARY<br/>- ATT_CMPR_PREFIX<br/>- ATT_CMPR_NUMSTR |
+| attinhcount   | integer   | Number of direct ancestors that this column has. A column with an ancestor cannot be dropped nor renamed. |
+| attcollation  | oid       | Defined collation of a column                                |
+| attacl        | aclitem[] | Permissions for column-level access                          |
+| attoptions    | text[]    | Column attribute. Currently, the following attributes are supported:<br />**n_distinct**: number of **distinct** values of a column (excluding subtables).<br />**n_distinct_inherited**: number of **distinct** values of a column (including subtables). |
+| attfdwoptions | text[]    | Column attribute of a foreign table. Currently, **dist_fdw**, **file_fdw**, and **log_fdw** do not use foreign table column attributes. |
+| attinitdefval | bytea     | **attinitdefval** stores the default value expression. **ADD COLUMN** in the row-store table must use this column. |
+| attkvtype     | tinyint   | Specifies the key value type for a column. Value:<br/>0. ATT_KV_UNDEFINED: default value<br/>1. ATT_KV_TAG: dimension<br/>2. ATT_KV_FIELD: indicator<br/>3. ATT_KV_TIMETAG: time column |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AUTHID.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AUTHID.md
new file mode 100644
index 0000000000000000000000000000000000000000..51a9cc6af26d57334cba274071781cd3bb0519c6
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AUTHID.md
@@ -0,0 +1,44 @@
+---
+title: PG_AUTHID
+summary: PG_AUTHID
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_AUTHID
+
+**PG_AUTHID** records information about database authentication identifiers (roles). The concept of users is contained in that of roles. A user is actually a role whose **rolcanlogin** has been set. Any role, whether its **rolcanlogin** is set or not, can use other roles as members.
+
+For MogDB, only one **PG_AUTHID** exists, which is not available for every database. This system catalog is accessible only to system administrators.
+
+**Table 1** PG_AUTHID columns
+
+| Name             | Type                     | Description                                                  |
+| :--------------- | :----------------------- | :----------------------------------------------------------- |
+| oid              | oid                      | Row identifier (hidden attribute, which must be specified)   |
+| rolname          | name                     | Name of a role                                               |
+| rolsuper         | Boolean                  | Whether the role is the initial system administrator with the highest permission<br />- **t** (true): yes<br />- **f** (false): no |
+| rolinherit       | Boolean                  | Whether the role automatically inherits permissions of roles of which it is a member<br />- **t** (true): automatically inherited<br />- **f** (false): not automatically inherited |
+| rolcreaterole    | Boolean                  | Whether the role can create more roles<br />- **t** (true): yes<br />- **f** (false): no |
+| rolcreatedb      | Boolean                  | Whether the role can create databases<br />- **t** (true): yes<br />- **f** (false): no |
+| rolcatupdate     | Boolean                  | Whether the role can directly update system catalogs Only the initial system administrator whose **usesysid** is set to **10** has this permission. It is unavailable for other users.<br />- **t** (true): yes<br />- **f** (false): no |
+| rolcanlogin      | Boolean                  | Whether the role can log in (whether this role can be given as the initial session authorization identifier)<br />- **t** (true): yes<br />- **f** (false): no |
+| rolreplication   | Boolean                  | Whether the role has the replication permission<br />- **t** (true): yes<br />- **f** (false): no |
+| rolauditadmin    | Boolean                  | Whether the role has the audit administrator permission<br />- **t** (true): yes<br />- **f** (false): no |
+| rolsystemadmin   | Boolean                  | Whether the role has system administrator permissions<br />- **t** (true): yes<br />- **f** (false): no |
+| rolconnlimit     | integer                  | Maximum number of concurrent connections that the role can make (valid for roles that can log in)<br />The value **-1** indicates there is no limit. |
+| rolpassword      | text                     | Password (possibly encrypted); **NULL** if no password       |
+| rolvalidbegin    | timestamp with time zone | Account validity start time (**NULL** if no start time)      |
+| rolvaliduntil    | timestamp with time zone | Password expiry time (**NULL** if no expiration)             |
+| rolrespool       | name                     | Resource pool that a user can use                            |
+| roluseft         | Boolean                  | Whether the role can perform operations on foreign tables<br />- **t** (true): yes<br />- **f** (false): no |
+| rolparentid      | oid                      | OID of a group user to which the user belongs                |
+| roltabspace      | text                     | Maximum size of a user data table                            |
+| rolkind          | char                     | Special user types, including private users and common users |
+| rolnodegroup     | oid                      | Unsupported currently                                        |
+| roltempspace     | text                     | Maximum size of a user's temporary table, in KB              |
+| rolspillspace    | text                     | Maximum size of data that can be written to disks when a user executes a job, in KB |
+| rolexcpdata      | text                     | Query rules that can be set by users (reserved)              |
+| rolmonitoradmin  | Boolean                  | Whether the role has monitor administrator permissions<br />- **t** (true): yes<br />- **f** (false): no |
+| roloperatoradmin | Boolean                  | Whether the role has the O&M administrator permission<br />- **t** (true): yes<br />- **f** (false): no |
+| rolpolicyadmin   | Boolean                  | Whether the role has the security policy administrator permission<br />- **t** (true): yes<br />- **f** (false): no |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AUTH_HISTORY.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AUTH_HISTORY.md
new file mode 100644
index 0000000000000000000000000000000000000000..d0a47a8b62c3ba0f3308fc3330b003d17c21f2e1
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AUTH_HISTORY.md
@@ -0,0 +1,19 @@
+---
+title: PG_AUTH_HISTORY
+summary: PG_AUTH_HISTORY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_AUTH_HISTORY
+
+**PG_AUTH_HISTORY** records the authentication history of a role. This system catalog is accessible only to system administrators.
+
+**Table 1** PG_AUTH_HISTORY columns
+
+| Name         | Type                     | Description                                                  |
+| :----------- | :----------------------- | :----------------------------------------------------------- |
+| oid          | oid                      | Row identifier (hidden attribute, which must be specified)   |
+| roloid       | oid                      | ID of a role                                                 |
+| passwordtime | timestamp with time zone | Time of password creation and change                         |
+| rolpassword  | text                     | Ciphertext of the role password. The encryption mode is determined by the GUC parameter **password_encryption_type**. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AUTH_MEMBERS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AUTH_MEMBERS.md
new file mode 100644
index 0000000000000000000000000000000000000000..e81b3d6014738e14df53835a8c9c228c1655b353
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AUTH_MEMBERS.md
@@ -0,0 +1,19 @@
+---
+title: PG_AUTH_MEMBERS
+summary: PG_AUTH_MEMBERS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_AUTH_MEMBERS
+
+**PG_AUTH_MEMBERS** records the membership between roles.
+
+**Table 1** PG_AUTH_MEMBERS columns
+
+| Name         | Type    | Description                                               |
+| :----------- | :------ | :-------------------------------------------------------- |
+| roleid       | oid     | ID of a role that has a member                            |
+| member       | oid     | ID of a role that is a member of ROLEID                   |
+| grantor      | oid     | ID of a role that grants this membership                  |
+| admin_option | Boolean | Whether a member can grant membership in ROLEID to others |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CAST.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CAST.md
new file mode 100644
index 0000000000000000000000000000000000000000..d0dfc8024d5d71ac6fefa6dd2b2495e940974f99
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CAST.md
@@ -0,0 +1,21 @@
+---
+title: PG_CAST
+summary: PG_CAST
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_CAST
+
+**PG_CAST** records the conversion relationship between data types.
+
+**Table 1** PG_CAST columns
+
+| Name        | Type   | Description                                                  |
+| :---------- | :----- | :----------------------------------------------------------- |
+| oid         | oid    | Row identifier (hidden attribute, which must be specified)   |
+| castsource  | oid    | OID of the source data type                                  |
+| casttarget  | oid    | OID of the target data type                                  |
+| castfunc    | oid    | OID of the conversion function (**0** if no conversion function is required) |
+| castcontext | "char" | Conversion mode between the source and target data types.<br/>- 'e': Only explicit conversion can be performed (using the CAST or :: syntax).<br/>- 'i': Only implicit conversion can be performed.<br/>- 'a': Both explicit and implicit conversion can be performed between data types. |
+| castmethod  | "char" | Conversion method.<br/>- 'f': Conversion is performed using the specified function in the **castfunc** column.<br/>- 'b': Binary forcible conversion rather than the specified function in the **castfunc** column is performed between data types. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CLASS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CLASS.md
new file mode 100644
index 0000000000000000000000000000000000000000..889935687f06d4d5c79e279800ad9b929da1c93b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CLASS.md
@@ -0,0 +1,77 @@
+---
+title: PG_CLASS
+summary: PG_CLASS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_CLASS
+
+**PG_CLASS** records database objects and their relationship.
+
+**Table 1** PG_CLASS columns
+
+| Name             | Type             | Description                                                  |
+| :--------------- | :--------------- | :----------------------------------------------------------- |
+| oid              | oid              | Row identifier (hidden attribute, which must be specified)   |
+| relname          | name             | Name of an object, such as a table, index, or view           |
+| relnamespace     | oid              | OID of the namespace that contains the relationship          |
+| reltype          | oid              | Data type that corresponds to the table's row type. The index is 0 because the index does not have **PG_TYPE** records. |
+| reloftype        | oid              | OID of the composite type (**0** for other types)            |
+| relowner         | oid              | Owner of the relationship                                    |
+| relam            | oid              | Access method used, such as B-tree and hash, if this is an index |
+| relfilenode      | oid              | Name of the on-disk file of this relationship (**0** if such file does not exist) |
+| reltablespace    | oid              | Tablespace in which this relationship is stored. If the value is **0**, the default tablespace in this database is used. This column is meaningless if the relationship has no on-disk file. |
+| relpages         | double precision | Size of the on-disk representation of the table in pages (of size BLCKSZ). This is only an estimate used by the optimizer. |
+| reltuples        | double precision | Number of rows in the table. This is only an estimate used by the optimizer. |
+| relallvisible    | integer          | Number of pages marked as all visible in the table. This column is used by the optimizer for optimizing SQL execution. It is updated by **VACUUM**, **ANALYZE**, and a few DDL statements such as **CREATE INDEX**. |
+| reltoastrelid    | oid              | OID of the TOAST table associated with the table (**0** if no TOAST table exists).<br/>The TOAST table stores large columns "offline" in a secondary table. |
+| reltoastidxid    | oid              | OID of the index for a TOAST table (**0** for a table other than a TOAST table) |
+| reldeltarelid    | oid              | OID of a Delta table<br/>Delta tables are attached to column-store tables. They store long tail data generated during storage data import. |
+| reldeltaidx      | oid              | OID of the index for a Delta table                           |
+| relcudescrelid   | oid              | OID of a CU description table.<br/>CU description tables (Desc tables) belong to column-store tables. They control whether storage data in the HDFS table directory is visible. |
+| relcudescidx     | oid              | OID of the index for a CU description table                  |
+| relhasindex      | Boolean          | Its value is **true** if this column is a table and has (or recently had) at least one index.<br/>It is set by **CREATE INDEX** but is not immediately cleared by **DROP INDEX**. If the **VACUUM** process detects that a table has no index, it clears the **relhasindex** column and sets the value to **false**. |
+| relisshared      | Boolean          | Its value is **true** if the table is shared across all database nodes in MogDB. Only certain system catalogs (such as **PG_DATABASE**) are shared. |
+| relpersistence   | "char"           | - **p**: permanent table<br/>- **u**: non-log table<br/>- **g**: temporary table |
+| relkind          | "char"           | - **r**: ordinary table<br/>- **i**: index<br/>- **I**: GLOBAL index of a partitioned table<br/>- **s**: sequence<br/>- **v**: view<br/>- **c**: composite type<br/>- **t**: TOAST table<br/>- **f**: foreign table |
+| relnatts         | smallint         | Number of user columns in the relationship (excluding system columns). **PG_ATTRIBUTE** has the same number of rows as the user columns. |
+| relchecks        | smallint         | Number of check constraints in the table. For details, see the system catalog **PG_CONSTRAINT**. |
+| relhasoids       | Boolean          | Its value is **true** if an OID is generated for each row of the relationship. |
+| relhaspkey       | Boolean          | Its value is **true** if the table has (or once had) a primary key. |
+| relhasrules      | Boolean          | Its value is **true** if the table has rules. For details, see the system catalog **PG_REWRITE**. |
+| relhastriggers   | Boolean          | The value is **true** if the table has (or once had) triggers. Triggers of the table and view are recorded in the system catalog **PG_TRIGGER**. |
+| relhassubclass   | Boolean          | Its value is **true** if the table has (or once had) any inheritance child table. |
+| relcmprs         | tinyint          | Whether the compression feature is enabled for the table. Note that only batch insertion triggers compression, so ordinary CRUD does not trigger compression.<br/>- **0**: Tables that do not support compression (primarily system catalogs, on which the compression attribute cannot be modified).<br/>- **1**: The compression feature of the table data is NOCOMPRESS or has no specified keyword.<br/>- **2**: The compression feature of the table data is COMPRESS. |
+| relhasclusterkey | Boolean          | Whether the local cluster storage is used                    |
+| relrowmovement   | Boolean          | Whether row migration is allowed when the partitioned table is updated.<br/>- **true**: Row migration is allowed.<br/>- **false**: Row migration is not allowed. |
+| parttype         | "char"           | Whether the table or index has the property of a partitioned table.<br/>- **p**: The table or index has the property of a partitioned table.<br/>- **n**: The table or index does not have the property of a partitioned table.<br/>- **v**: The table is a value partitioned table in HDFS. |
+| relfrozenxid     | xid32            | All transaction IDs before this one have been replaced with a permanent ("frozen") transaction ID in the table. This column is used to track whether the table needs to be vacuumed to prevent transaction ID wraparound (or to allow **PG_CLOG** to be shrunk). The value is **0** (**InvalidTransactionId**) if the relationship is not a table.<br/>To ensure forward compatibility, this column is reserved. The **relfrozenxid64** column is added to record the information. |
+| relacl           | aclitem[]        | Access permissions.<br/>The command output of the query is as follows:<br/>`rolename=xxxx/yyyy  - Assigning permissions to a role`<br/>`=xxxx/yyyy - Assigning the permission to public`<br/>**xxxx** indicates assigned permissions, and **yyyy** indicates roles with the assigned permissions. For details on permission descriptions, see [Table 2](#Description of permissions). |
+| relreplident     | "char"           | Identifier of a decoding column in logical decoding:<br/>- **d**: default (primary key, if any)<br/>- **n**: none<br/>- **f**: all columns<br/>- **i**: The indisreplident of the index is specified or the default index is used. |
+| relfrozenxid64   | xid              | All transaction IDs before this one have been replaced with a permanent ("frozen") transaction ID in the table. This column is used to track whether the table needs to be vacuumed to prevent transaction ID wraparound (or to allow **PG_CLOG** to be shrunk). The value is **0** (**InvalidTransactionId**) if the relationship is not a table. |
+| relbucket        | oid              | Bucket information in **pg_hashbucket**.                     |
+| relbucketkey     | int2vector       | Column number of a hash partition.                           |
+
+**Table 2** Description of permissions<a id="Description of permissions"> </a>
+
+| Parameter | Parameter Description                           |
+| :-------- | :---------------------------------------------- |
+| r         | SELECT (read)                                   |
+| w         | UPDATE (write)                                  |
+| a         | INSERT (insert)                                 |
+| d         | DELETE                                          |
+| D         | TRUNCATE                                        |
+| x         | REFERENCES                                      |
+| t         | TRIGGER                                         |
+| X         | EXECUTE                                         |
+| U         | USAGE                                           |
+| C         | CREATE                                          |
+| c         | CONNECT                                         |
+| T         | TEMPORARY                                       |
+| A         | ALTER                                           |
+| P         | DROP                                            |
+| m         | COMMENT                                         |
+| i         | INDEX                                           |
+| v         | VACUUM                                          |
+| *         | Authorization options for preceding permissions |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_COLLATION.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_COLLATION.md
new file mode 100644
index 0000000000000000000000000000000000000000..1e22f5e9b05c7bc5b11ed379f86362eab21436f7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_COLLATION.md
@@ -0,0 +1,22 @@
+---
+title: PG_COLLATION
+summary: PG_COLLATION
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_COLLATION
+
+**PG_COLLATION** describes available collations, which are essentially mappings from an SQL name to operating system locale categories.
+
+**Table 1** PG_COLLATION columns
+
+| Name          | Type    | Reference        | Description                                                  |
+| :------------ | :------ | :--------------- | :----------------------------------------------------------- |
+| oid           | oid     | -                | Row identifier (hidden attribute, which must be specified)   |
+| collname      | name    | -                | Collation name (unique per namespace and encoding)           |
+| collnamespace | oid     | PG_NAMESPACE.oid | OID of the namespace that contains this collation            |
+| collowner     | oid     | PG_AUTHID.oid    | Owner of the collation                                       |
+| collencoding  | integer | -                | Encoding in which the collation is applicable, or **-1** if it works for any encoding. It is compatible with PostgreSQL. |
+| collcollate   | name    | -                | **LC_COLLATE** for this collation object                     |
+| collctype     | name    | -                | **LC_CTYPE** for this collation object                       |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CONSTRAINT.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CONSTRAINT.md
new file mode 100644
index 0000000000000000000000000000000000000000..9918f7f986125453948fdddbdb7eccda70038bbb
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CONSTRAINT.md
@@ -0,0 +1,48 @@
+---
+title: PG_CONSTRAINT
+summary: PG_CONSTRAINT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_CONSTRAINT
+
+**PG_CONSTRAINT** records check, primary key, and unique constraints on tables.
+
+**Table 1** PG_CONSTRAINT columns
+
+| Name          | Type         | Description                                                  |
+| :------------ | :----------- | :----------------------------------------------------------- |
+| oid           | oid          | Row identifier (hidden attribute, which must be specified)   |
+| conname       | name         | Constraint name (not necessarily unique)                     |
+| connamespace  | oid          | OID of the namespace that contains the constraint            |
+| contype       | "char"       | - **c**: check constraint<br/>- **p**: primary key constraint<br/>- **u**: unique constraint<br/>- **t**: trigger constraint |
+| condeferrable | Boolean      | Whether the constraint can be deferrable                     |
+| condeferred   | Boolean      | Whether the constraint can be deferrable by default          |
+| convalidated  | Boolean      | Whether the constraint is valid. Currently, it can be set to **false** only for foreign key and check constraints. |
+| conrelid      | oid          | Table containing this constraint (**0** if it is not a table constraint) |
+| contypid      | oid          | Domain containing this constraint (**0** if it is not a domain constraint) |
+| conindid      | oid          | ID of the index associated with the constraint               |
+| confrelid     | oid          | Referenced table if this constraint is a foreign key. Otherwise, the value is **0**. Currently, foreign keys are not supported. Therefore, the value is fixed at **0**. |
+| confupdtype   | "char"       | Foreign key update action code<br/>- **a**: no action<br/>- **r**: restriction<br/>- **c**: cascading<br/>- **n**: The parameter is set to **null**.<br/>- **d**: The default value is used. The value is empty because foreign keys are not supported currently. |
+| confdeltype   | "char"       | Foreign key deletion action code<br/>- **a**: no action<br/>- **r**: restriction<br/>- **c**: cascading<br/>- **n**: The parameter is set to **null**.<br/>- **d**: The default value is used. The value is empty because foreign keys are not supported currently. |
+| confmatchtype | "char"       | Foreign key match type<br/>- **f**: full match<br/>- **p**: partial match<br/>- **u**: simple match (not specified). The value is empty because foreign keys are not supported currently. |
+| conislocal    | Boolean      | Whether the local constraint is defined for the relationship |
+| coninhcount   | integer      | Number of direct inheritance parent tables that this constraint has. When the value is not **0**, the constraint cannot be deleted or renamed. |
+| connoinherit  | Boolean      | Whether the constraint can be inherited                      |
+| consoft       | Boolean      | Whether the column indicates an informational constraint     |
+| conopt        | Boolean      | Whether you can use the informational constraint to optimize the execution plan |
+| conkey        | smallint[]   | Column list of the constrained control if this column is a table constraint |
+| confkey       | smallint[]   | List of referenced columns if this column is a foreign key. The value is empty because foreign keys are not supported currently. |
+| conpfeqop     | oid[]        | ID list of the equality operators for PK = FK comparisons if this column is a foreign key. The value is empty because foreign keys are not supported currently. |
+| conppeqop     | oid[]        | ID list of the equality operators for PK = PK comparisons if this column is a foreign key. The value is empty because foreign keys are not supported currently. |
+| conffeqop     | oid[]        | ID list of the equality operators for FK = FK comparisons if this column is a foreign key. The value is empty because foreign keys are not supported currently. |
+| conexclop     | oid[]        | ID list of the per-column exclusion operators if this column is an exclusion constraint |
+| conbin        | pg_node_tree | Internal representation of the expression if this column is a check constraint |
+| consrc        | text         | Human-readable representation of the expression if this column is a check constraint |
+| conincluding  | smallint[]   | Not for constraint, but will be included in the attribute column of **INDEX**. |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - **consrc** is not updated when referenced objects change and does not track new column names. Instead of relying on this column to update, you are advised to use **pg_get_constraintdef()** to extract the definition of a check constraint.
+> - **pg_class.relchecks** must agree with the number of check-constraint entries found in the table for each relationship.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CONVERSION.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CONVERSION.md
new file mode 100644
index 0000000000000000000000000000000000000000..1892557a3a0528ad7b40d9bb3b724c82aa1dead3
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CONVERSION.md
@@ -0,0 +1,23 @@
+---
+title: PG_CONVERSION
+summary: PG_CONVERSION
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_CONVERSION
+
+**PG_CONVERSION** describes encoding conversion information.
+
+**Table 1** PG_CONVERSION columns
+
+| Name           | Type    | Reference        | Description                                                |
+| :------------- | :------ | :--------------- | :--------------------------------------------------------- |
+| oid            | oid     | -                | Row identifier (hidden attribute, which must be specified) |
+| conname        | name    | -                | Conversion name (unique within a namespace)                |
+| connamespace   | oid     | PG_NAMESPACE.oid | OID of the namespace that contains this conversion         |
+| conowner       | oid     | PG_AUTHID.oid    | Owner of the conversion                                    |
+| conforencoding | integer | -                | Source encoding ID                                         |
+| contoencoding  | integer | -                | Destination encoding ID                                    |
+| conproc        | regproc | PG_PROC.proname  | Conversion procedure                                       |
+| condefault     | Boolean | -                | Whether the default conversion is used                     |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DATABASE.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DATABASE.md
new file mode 100644
index 0000000000000000000000000000000000000000..c322813d4d44607d44c52e171c8b22c73216fc39
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DATABASE.md
@@ -0,0 +1,30 @@
+---
+title: PG_DATABASE
+summary: PG_DATABASE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_DATABASE
+
+**PG_DATABASE** records information about available databases.
+
+**Table 1** PG_DATABASE columns
+
+| Name             | Type      | Description                                                  |
+| :--------------- | :-------- | :----------------------------------------------------------- |
+| oid              | oid       | Row identifier (hidden attribute, which must be specified)   |
+| datname          | name      | Database name                                                |
+| datdba           | oid       | Owner of the database, usually the user who created it       |
+| encoding         | integer   | Character encoding for the database                          |
+| datcollate       | name      | Sequence used by the database                                |
+| datctype         | name      | Character type used by the database                          |
+| datistemplate    | Boolean   | Whether the database can be used as a template database      |
+| datallowconn     | Boolean   | If the value is **false**, no one can connect to this database. This column is used to protect the **template0** database from being altered. |
+| datconnlimit     | integer   | Maximum number of concurrent connections allowed on this database. The value **-1** indicates no limit. |
+| datlastsysoid    | oid       | Last system OID in the database                              |
+| datfrozenxid     | xid32     | Tracks whether the database needs to be vacuumed to prevent transaction ID wraparound.<br/>To ensure forward compatibility, this column is reserved. The **datfrozenxid64** column is added to record the information. |
+| dattablespace    | oid       | Default tablespace of the database                           |
+| datcompatibility | name      | Database compatibility mode. Currently, four compatibility modes are supported: A, B, C, and PG, indicating that the Oracle, MySQL, Teradata, and Postgres databases are compatible. |
+| datacl           | aclitem[] | Access permissions                                           |
+| datfrozenxid64   | xid       | Tracks whether the database needs to be vacuumed to prevent transaction ID wraparound. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DB_ROLE_SETTING.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DB_ROLE_SETTING.md
new file mode 100644
index 0000000000000000000000000000000000000000..720f403365e622c45542a0d04f65cf5a6d970e97
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DB_ROLE_SETTING.md
@@ -0,0 +1,18 @@
+---
+title: PG_DB_ROLE_SETTING
+summary: PG_DB_ROLE_SETTING
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_DB_ROLE_SETTING
+
+**PG_DB_ROLE_SETTING** records the default values of configuration items bound to each role and database when the database is running.
+
+**Table 1** PG_DB_ROLE_SETTING columns
+
+| Name        | Type   | Description                                                  |
+| :---------- | :----- | :----------------------------------------------------------- |
+| setdatabase | oid    | Database corresponding to the configuration items (**0** if no database is specified) |
+| setrole     | oid    | Role corresponding to the configuration items (**0** if no role is specified) |
+| setconfig   | text[] | Default value of configuration items when the database is running |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DEFAULT_ACL.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DEFAULT_ACL.md
new file mode 100644
index 0000000000000000000000000000000000000000..20bda6b745f54e838a466e4883e333b80bc7dd8d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DEFAULT_ACL.md
@@ -0,0 +1,20 @@
+---
+title: PG_DEFAULT_ACL
+summary: PG_DEFAULT_ACL
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_DEFAULT_ACL
+
+**PG_DEFAULT_ACL** records initial permissions assigned to newly created objects.
+
+**Table 1** PG_DEFAULT_ACL columns
+
+| Name            | Type      | Description                                                  |
+| :-------------- | :-------- | :----------------------------------------------------------- |
+| oid             | oid       | Row identifier (hidden attribute, which must be specified)   |
+| defaclrole      | oid       | ID of the role associated with the permission                |
+| defaclnamespace | oid       | Namespace associated with the permission (**0** if no ID)    |
+| defaclobjtype   | "char"    | Object type of the permission<br />- **r** indicates a table or view.<br />- **S** indicates a sequence.<br />- **f** indicates a function.<br />- **T** indicates a type.<br />- **K** indicates the client master key.<br />- **k** indicates the column encryption key. |
+| defaclacl       | aclitem[] | Access permissions that this type of object should have on creation |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DEPEND.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DEPEND.md
new file mode 100644
index 0000000000000000000000000000000000000000..2687c91695d006bf9d2d9c542014a5e9ca95d8b6
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DEPEND.md
@@ -0,0 +1,32 @@
+---
+title: PG_DEPEND
+summary: PG_DEPEND
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_DEPEND
+
+**PG_DEPEND** records the dependency between database objects. This information allows **DROP** commands to find which other objects must be dropped by **DROP CASCADE** or prevent dropping in the **DROP RESTRICT** case.
+
+See also PG_SHDEPEND, which performs a similar function for dependencies involving objects that are shared across MogDB.
+
+**Table 1** PG_DEPEND columns
+
+| Name        | Type    | Reference      | Description                                                  |
+| :---------- | :------ | :------------- | :----------------------------------------------------------- |
+| classid     | oid     | PG_CLASS.oid   | OID of the system catalog where a dependent object resides   |
+| objid       | oid     | Any OID column | OID of the dependent object                                  |
+| objsubid    | integer | -              | Column number for a table column (**objid** and **classid** refer to the table itself); The value is **0** for all other object types. |
+| refclassid  | oid     | PG_CLASS.oid   | OID of the system catalog where a referenced object resides  |
+| refobjid    | oid     | Any OID column | OID of the referenced object                                 |
+| refobjsubid | integer | -              | Column number for a table column (**refobjid** and **refclassid** refer to the table itself); **0** for all other object types |
+| deptype     | "char"  | -              | A code defining the specific semantics of this dependency    |
+
+In all cases, a **PG_DEPEND** entry indicates that the referenced object cannot be dropped without also dropping the dependent object. However, there are several subflavors identified by **deptype**:
+
+- DEPENDENCY_NORMAL (n): A normal relationship between separately created objects. The dependent object can be dropped without affecting the referenced object. The referenced object can only be dropped by specifying **CASCADE**, in which case the dependent object is dropped too. Example: a table column has a normal dependency on its data type.
+- DEPENDENCY_AUTO (a): The dependent object can be dropped separately from the referenced object, and should be automatically dropped (regardless of RESTRICT or CASCADE mode) if the referenced object is dropped. Example: a named constraint on a table is made autodependent on the table, so that it will go away if the table is dropped.
+- DEPENDENCY_INTERNAL (i): The dependent object was created as part of creation of the referenced object, and is only a part of its internal implementation. A DROP of the dependent object will be disallowed outright (We'll tell the user to issue a DROP against the referenced object, instead). A **DROP** of the referenced object will be propagated through to drop the dependent object whether **CASCADE** is specified or not.
+- DEPENDENCY_EXTENSION (e): The dependent object is a member of the extension of the referenced object (see PG_EXTENSION). The dependent object can be dropped only via **DROP EXTENSION** on the referenced object. Functionally this dependency type acts the same as an internal dependency, but it is kept separate for clarity and to simplify **GS_DUMP**.
+- DEPENDENCY_PIN (p): There is no dependent object; this type of entry is a signal that the system itself depends on the referenced object, and so that object must never be deleted. Entries of this type are created only by **initdb**. The columns for the dependent object contain zeroes.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DESCRIPTION.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DESCRIPTION.md
new file mode 100644
index 0000000000000000000000000000000000000000..a5e396d82af3323e6e83214d4f3ed2253a8f5530
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DESCRIPTION.md
@@ -0,0 +1,21 @@
+---
+title: PG_DESCRIPTION
+summary: PG_DESCRIPTION
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_DESCRIPTION
+
+**PG_DESCRIPTION** records optional descriptions (comments) for each database object. Descriptions of many built-in system objects are provided in the initial contents of **PG_DESCRIPTION**.
+
+See also PG_SHDESCRIPTION, which provides a similar function for descriptions involving objects that are shared across MogDB.
+
+**Table 1** PG_DESCRIPTION columns
+
+| Name        | Type    | Reference      | Description                                                  |
+| :---------- | :------ | :------------- | :----------------------------------------------------------- |
+| objoid      | oid     | Any OID column | OID of the object that this description pertains to          |
+| classoid    | oid     | PG_CLASS.oid   | OID of the system catalog where the object appears           |
+| objsubid    | integer | -              | Column number for a comment on a table column (**objoid** and **classoid** refer to the table itself); **0** for all other object types |
+| description | text    | -              | Arbitrary text that serves as the description of the object  |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DIRECTORY.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DIRECTORY.md
new file mode 100644
index 0000000000000000000000000000000000000000..914979a4c05347b2bd8c70a24b2322e73df98578
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DIRECTORY.md
@@ -0,0 +1,20 @@
+---
+title: PG_DIRECTORY
+summary: PG_DIRECTORY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_DIRECTORY
+
+**PG_DIRECTORY** stores directories added by users. You can run the **CREATE DIRECTORY** statement to add directories to the system catalog. Currently, only system administrators can perform this operation.
+
+**Table 1** PG_DIRECTORY columns
+
+| Name    | Type      | Description                                                |
+| :------ | :-------- | :--------------------------------------------------------- |
+| oid     | oid       | Row identifier (hidden attribute, which must be specified) |
+| dirname | name      | Name of a directory object                                 |
+| owner   | oid       | Owner of a directory object                                |
+| dirpath | text      | Directory path.                                            |
+| diracl  | aclitem[] | Access permissions.                                        |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_ENUM.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_ENUM.md
new file mode 100644
index 0000000000000000000000000000000000000000..5e7b1bfc71f4e5f2d3cec72eae7f66bef1cdaecf
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_ENUM.md
@@ -0,0 +1,23 @@
+---
+title: PG_ENUM
+summary: PG_ENUM
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_ENUM
+
+**PG_ENUM** contains entries showing the values and labels for each enumerated type. The internal representation of a given enumerated value is actually the OID of its associated row in **PG_ENUM**.
+
+**Table 1** PG_ENUM columns
+
+| Name          | Type | Reference   | Description                                                  |
+| :------------ | :--- | :---------- | :----------------------------------------------------------- |
+| oid           | oid  | -           | Row identifier (hidden attribute, which must be specified)   |
+| enumtypid     | oid  | PG_TYPE.oid | OID of the **PG_TYPE** entry owning this enumerated value    |
+| enumsortorder | real | -           | Sort position of this enumerated value within its enumerated type |
+| enumlabel     | name | -           | Textual label for this enumerated value                      |
+
+The OIDs for **PG_ENUM** rows follow a special rule: even-numbered OIDs are guaranteed to be ordered in the same way as the sort ordering of their enumerated type. If two even OIDs belong to the same enumerated type, the smaller OID must have the smaller **enumsortorder** value. Odd-numbered OID values need bear no relationship to the sort order. This rule allows the enumerated comparison routines to avoid catalog lookups in many common cases. The routines that create and alter enumerated types attempt to assign even OIDs to enumerated values whenever possible.
+
+When an enumerated type is created, its members are assigned sort-order positions from 1 to *n*. However, members added later might be given negative or fractional values of **enumsortorder**. The only requirement on these values is that they be correctly ordered and unique within each enumerated type.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_EXTENSION.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_EXTENSION.md
new file mode 100644
index 0000000000000000000000000000000000000000..71f673bbacac8143ac6b27be19f372e54ecff525
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_EXTENSION.md
@@ -0,0 +1,23 @@
+---
+title: PG_EXTENSION
+summary: PG_EXTENSION
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_EXTENSION
+
+**PG_EXTENSION** records information about the installed extensions. Default extensions of openGauss: PLPGSQL and MOT_FDW.
+
+**Table 1** PG_EXTENSION
+
+| Name           | Type    | Description                                                  |
+| :------------- | :------ | :----------------------------------------------------------- |
+| oid            | oid     | Database object ID                                           |
+| extname        | name    | Extension name                                               |
+| extowner       | oid     | Owner of the extension                                       |
+| extnamespace   | oid     | Namespace containing the extension's exported objects        |
+| extrelocatable | Boolean | Whether the extension can be relocated to another namespace. **true** indicates that relocation is allowed. |
+| extversion     | text    | Version number of the extension                              |
+| extconfig      | oid[]   | Configuration information about the extension                |
+| extcondition   | text[]  | Filter conditions for the extension's configuration information |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_EXTENSION_DATA_SOURCE.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_EXTENSION_DATA_SOURCE.md
new file mode 100644
index 0000000000000000000000000000000000000000..23d6ef105b24744424cdd60d0d0d980652b7c2fd
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_EXTENSION_DATA_SOURCE.md
@@ -0,0 +1,22 @@
+---
+title: PG_EXTENSION_DATA_SOURCE
+summary: PG_EXTENSION_DATA_SOURCE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_EXTENSION_DATA_SOURCE
+
+**PG_EXTENSION_DATA_SOURCE** records information about external data sources. An external data source contains information about an external database, such as its password encoding. It is mainly used with Extension Connector.
+
+**Table 1** PG_EXTENSION_DATA_SOURCE columns
+
+| Name       | Type      | Reference     | Description                                                  |
+| :--------- | :-------- | :------------ | :----------------------------------------------------------- |
+| oid        | oid       | -             | Row identifier (hidden attribute, which must be specified)   |
+| srcname    | name      | -             | Name of an external data source                              |
+| srcowner   | oid       | PG_AUTHID.oid | Owner of a foreign data source                               |
+| srctype    | text      | -             | Type of an external data source. It is **NULL** by default.  |
+| srcversion | text      | -             | Version of an external data source. It is **NULL** by default. |
+| srcacl     | aclitem[] | -             | Access permissions.                                          |
+| srcoptions | text[]    | -             | Option used for foreign data sources, expressed in a string in the format of keyword=value |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_FOREIGN_DATA_WRAPPER.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_FOREIGN_DATA_WRAPPER.md
new file mode 100644
index 0000000000000000000000000000000000000000..6ef3f30433572371b1a5450bce35e848fb939d37
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_FOREIGN_DATA_WRAPPER.md
@@ -0,0 +1,22 @@
+---
+title: PG_FOREIGN_DATA_WRAPPER
+summary: PG_FOREIGN_DATA_WRAPPER
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_FOREIGN_DATA_WRAPPER
+
+**PG_FOREIGN_DATA_WRAPPER** records foreign-data wrapper definitions. A foreign-data wrapper is the mechanism by which external data, residing on foreign servers, is accessed.
+
+**Table 1** PG_FOREIGN_DATA_WRAPPER columns
+
+| Name         | Type      | Reference     | Description                                                  |
+| :----------- | :-------- | :------------ | :----------------------------------------------------------- |
+| oid          | oid       | -             | Row identifier (hidden attribute, which must be specified)   |
+| fdwname      | name      | -             | Name of a foreign-data wrapper                               |
+| fdwowner     | oid       | PG_AUTHID.oid | Owner of the foreign-data wrapper                            |
+| fdwhandler   | oid       | PG_PROC.oid   | References a handler function that is responsible for supplying execution routines for the foreign-data wrapper (**0** if no handler is provided) |
+| fdwvalidator | oid       | PG_PROC.oid   | References a validator function that is responsible for checking the validity of the options given to the foreign-data wrapper, as well as options for foreign servers and user mappings using the foreign-data wrapper. The value is **0** if no validator is provided. |
+| fdwacl       | aclitem[] | -             | Access permissions.                                          |
+| fdwoptions   | text[]    | -             | Foreign-data wrapper specific option, expressed in a string in the format of keyword=value |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_FOREIGN_SERVER.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_FOREIGN_SERVER.md
new file mode 100644
index 0000000000000000000000000000000000000000..ae1b92504303abe3e784eb594837183cbd9ecc5d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_FOREIGN_SERVER.md
@@ -0,0 +1,23 @@
+---
+title: PG_FOREIGN_SERVER
+summary: PG_FOREIGN_SERVER
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_FOREIGN_SERVER
+
+**PG_FOREIGN_SERVER** records foreign server definitions. A foreign server describes a source of external data, such as a remote server. Foreign servers are accessed via foreign-data wrappers.
+
+**Table 1** PG_FOREIGN_SERVER columns
+
+| Name       | Type      | Reference                   | Description                                                  |
+| :--------- | :-------- | :-------------------------- | :----------------------------------------------------------- |
+| oid        | oid       | -                           | Row identifier (hidden attribute, which must be specified)   |
+| srvname    | name      | -                           | Name of a foreign server                                     |
+| srvowner   | oid       | PG_AUTHID.oid               | Owner of the foreign server                                  |
+| srvfdw     | oid       | PG_FOREIGN_DATA_WRAPPER.oid | OID of the foreign-data wrapper on this foreign server       |
+| srvtype    | text      | -                           | Type of the server (optional)                                |
+| srvversion | text      | -                           | Version of the server (optional)                             |
+| srvacl     | aclitem[] | -                           | Access permissions                                           |
+| srvoptions | text[]    | -                           | Option used for foreign servers, expressed in a string in the format of keyword=value |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_FOREIGN_TABLE.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_FOREIGN_TABLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..aeb37e8986c40b0a6c518609b06bb1bd1862866e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_FOREIGN_TABLE.md
@@ -0,0 +1,19 @@
+---
+title: PG_FOREIGN_TABLE
+summary: PG_FOREIGN_TABLE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_FOREIGN_TABLE
+
+**PG_FOREIGN_TABLE** records auxiliary information about foreign tables.
+
+**Table 1** PG_FOREIGN_TABLE columns
+
+| Name        | Type    | Description                                                  |
+| :---------- | :------ | :----------------------------------------------------------- |
+| ftrelid     | oid     | ID of a foreign table                                        |
+| ftserver    | oid     | Server where the foreign table is located                    |
+| ftwriteonly | Boolean | Whether data can be written in the foreign table. Value range:<br />- **t** (true): yes<br />- **f** (false): no |
+| ftoptions   | text[]  | Options of a foreign table. For details, see the description of **CREATE FOREIGN TABLE**. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_INDEX.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_INDEX.md
new file mode 100644
index 0000000000000000000000000000000000000000..f3df5444afb56f0c81acd6b82ad0b2e55cd90beb
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_INDEX.md
@@ -0,0 +1,35 @@
+---
+title: PG_INDEX
+summary: PG_INDEX
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_INDEX
+
+**PG_INDEX** records part of index information. The rest is mostly recorded in **PG_CLASS**.
+
+**Table 1** PG_INDEX columns
+
+| Name           | Type         | Description                                                  |
+| :------------- | :----------- | :----------------------------------------------------------- |
+| indexrelid     | oid          | OID of the **PG_CLASS** entry for the index                  |
+| indrelid       | oid          | OID of the **PG_CLASS** entry for the table that uses the index |
+| indnatts       | smallint     | Number of columns in the index                               |
+| indisunique    | Boolean      | This index is a unique index if the value is **true**.<br />This index is not a unique index if the value is **false**. |
+| indisprimary   | Boolean      | Primary key of the table if the value is **true**. **indisunique** should always be **true** when the value of this column is **true**.<br />This index is not the primary key of the table if the value is **false**. |
+| indisexclusion | Boolean      | Whether the index supports exclusion constraints<br />This index does not support exclusion constraints if the value is **false**. |
+| indimmediate   | Boolean      | Whether a uniqueness check is performed upon data insertion<br />A uniqueness check is not performed upon data insertion if the value is **false**. |
+| indisclustered | Boolean      | Whether the table was last clustered on the index<br />The table is not clustered on this index if the value is **false**. |
+| indisusable    | Boolean      | Whether the index supports INSERT/SELECT<br />This index does not support INSERT/SELECT if the value is **false**. |
+| indisvalid     | Boolean      | Whether the index is valid for queries. If this column is **false**, the index is possibly incomplete and must still be modified by INSERT/UPDATE operations, but it cannot safely be used for queries. <br />If it is a unique index, the uniqueness property is also not **true**. |
+| indcheckxmin   | Boolean      | If the value is **true**, queries must not use the index until the xmin of this row in **PG_INDEX** is below their **TransactionXmin**, because the table may contain broken HOT chains with incompatible rows that they can see.If the value is **false**, queries can use indexes. |
+| indisready     | Boolean      | The index is available for inserted data if the value is **true**. Otherwise, this index is ignored when data is inserted or modified. |
+| indkey         | int2vector   | This is an array of **indnatts** values indicating that this index creates table columns. For example, a value of **1 3** indicates that the first and the third columns make up the index key. The value **0** in this array indicates that the corresponding index attribute is an expression over the table columns, rather than a simple column reference. |
+| indcollation   | oidvector    | ID of each column used by the index                          |
+| indclass       | oidvector    | For each column in the index key, this contains the OID of the operator class to use. See **PG_OPCLASS** for details. |
+| indoption      | int2vector   | Array of values that store per-column flag bits. The meaning of the bits is defined by the index's access method. |
+| indexprs       | pg_node_tree | Expression trees (in **nodeToString()** representation) for index attributes that are not simple column references. It is a list with one element for each zero entry in **INDKEY**. The value is **NULL** if all index attributes are simple references. |
+| indpred        | pg_node_tree | Expression tree (in **nodeToString()** representation) for partial index predicate. If the index is not a partial index, this column is an empty string. |
+| indisreplident | Boolean      | If the value is **true**, the column of this index becomes the decoded column of logical decoding.<br />If the value is **false**, the column of this index is not the decoded column of logical decoding. |
+| indnkeyatts    | smallint     | Total number of columns in the index. The columns that exceed the value of **indnatts** are not involved in the index query. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_INHERITS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_INHERITS.md
new file mode 100644
index 0000000000000000000000000000000000000000..3c56c4aa9607e01aa19d06868020a4e092d95959
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_INHERITS.md
@@ -0,0 +1,18 @@
+---
+title: PG_INHERITS
+summary: PG_INHERITS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_INHERITS
+
+**PG_INHERITS** records information about table inheritance hierarchies. There is one entry for each direct child table in the database. Indirect inheritance can be determined by following chains of entries.
+
+**Table 1** PG_INHERITS columns
+
+| Name      | Type    | Reference    | Description                                                  |
+| :-------- | :------ | :----------- | :----------------------------------------------------------- |
+| inhrelid  | oid     | PG_CLASS.oid | OID of a child table                                         |
+| inhparent | oid     | PG_CLASS.oid | OID of a parent table                                        |
+| inhseqno  | integer | -            | If there is more than one direct parent for a child table (multiple inheritances), this number tells the order in which the inherited columns are to be arranged. The count starts at 1. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_JOB.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_JOB.md
new file mode 100644
index 0000000000000000000000000000000000000000..13773c8d6b29778d5fc2208681fefb9df38cb483
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_JOB.md
@@ -0,0 +1,32 @@
+---
+title: PG_JOB
+summary: PG_JOB
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_JOB
+
+**PG_JOB** records detailed information about jobs created by users. Dedicated threads poll the system catalog **PG_JOB** and trigger jobs based on scheduled job execution time, and update job status in **PG_JOB**. This system catalog belongs to the Shared Relation category. All job records are visible to all databases.
+
+**Table 1** PG_JOB columns
+
+| Name                 | Type                        | Description                                                  |
+| :------------------- | :-------------------------- | :----------------------------------------------------------- |
+| oid                  | oid                         | Row identifier (hidden attribute, which must be specified)   |
+| job_id               | bigint                      | Job ID, primary key, unique (with a unique index)            |
+| current_postgres_pid | bigint                      | postgres thread ID of the job if the job has been executed. The default value is **-1**, indicating that the job has not yet been executed. |
+| log_user             | name                        | Username of the job creator                                  |
+| priv_user            | name                        | Username of the job executor                                 |
+| dbname               | name                        | Name of the database in which the job will be executed       |
+| node_name            | name                        | Primary database node on which the job will be executed      |
+| job_status           | "char"                      | Status of the job. The value can be **r**, **s**, **f**, or **d**. The default value is **s**. The indications are as follows:<br/>Status of job step: r=running, s=successfully finished, f=job failed, d=disable<br/>If a job fails to be executed for 16 consecutive times, **job\_status** is automatically set to **d**, and no more attempt will be made on this job.<br/>Note: When you disable a scheduled task (by setting **job_queue_processes** to **0**), the thread that monitors the job execution is not started, and the job status will not be updated. You can ignore this status. Only when the scheduled task function is enabled (**job_queue_processes** is not **0**), the system updates the value of this column based on the real-time job status. |
+| start_date           | timestamp without time zone | Start time of the first job execution, accurate to millisecond |
+| next_run_date        | timestamp without time zone | Scheduled time of the next job execution, accurate to millisecond |
+| failure_count        | smallint                    | Number of times the job has started and failed. If a job fails to be executed for 16 consecutive times, no more attempt will be made on it. |
+| interval             | text                        | Job execution interval                                       |
+| last_start_date      | timestamp without time zone | Start time of the last job execution, accurate to millisecond |
+| last_end_date        | timestamp without time zone | End time of the last job execution, accurate to millisecond  |
+| last_suc_date        | timestamp without time zone | Start time of the last successful job execution, accurate to millisecond |
+| this_run_date        | timestamp without time zone | Start time of the ongoing job execution, accurate to millisecond |
+| nspname              | name                        | Name of the schema used for job execution                    |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_JOB_PROC.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_JOB_PROC.md
new file mode 100644
index 0000000000000000000000000000000000000000..bf734dc2973f8cb8f96b650aab160296c83336d5
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_JOB_PROC.md
@@ -0,0 +1,19 @@
+---
+title: PG_JOB_PROC
+summary: PG_JOB_PROC
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_JOB_PROC
+
+**PG_JOB_PROC** records the content of each job in the **PG_JOB** table, including the PL/SQL code blocks and anonymous blocks. Storing such information in the system catalog **PG_JOB** and loading it to the shared memory will result in excessive memory usage. Therefore, such information is stored in a separate table and is retrieved when needed.
+
+**Table 1** PG_JOB_PROC columns
+
+| Name     | Type    | Description                                                  |
+| :------- | :------ | :----------------------------------------------------------- |
+| oid      | oid     | Row identifier (hidden attribute, which must be specified)   |
+| job_oid  | integer | Foreign key, which is associated with **job\_id** in the system catalog **PG_JOB** |
+| what     | text    | Job content                                                  |
+| job_name | text    | Job name                                                     |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_LANGUAGE.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_LANGUAGE.md
new file mode 100644
index 0000000000000000000000000000000000000000..ca8604a644d9969572163567b6fb294498f06de0
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_LANGUAGE.md
@@ -0,0 +1,24 @@
+---
+title: PG_LANGUAGE
+summary: PG_LANGUAGE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_LANGUAGE
+
+**PG_LANGUAGE** registers programming languages. You can use them and interfaces to write functions or stored procedures.
+
+**Table 1** PG_LANGUAGE columns
+
+| Name          | Type      | Reference     | Description                                                  |
+| :------------ | :-------- | :------------ | :----------------------------------------------------------- |
+| oid           | oid       | -             | Row identifier (hidden attribute, which must be specified)   |
+| lanname       | name      | -             | Language name                                                |
+| lanowner      | oid       | PG_AUTHID.oid | Owner of the language                                        |
+| lanispl       | Boolean   | -             | The value is **false** for internal languages (such as SQL) and **true** for user-defined languages. Currently, **GS_DUMP** still uses this column to determine which languages need to be dumped, but this might be replaced by a different mechanism in the future. |
+| lanpltrusted  | Boolean   | -             | The value is **true** if this is a trusted language, which means that it is believed not to grant access to anything outside the normal SQL execution environment. Only the initial user can create functions in untrusted languages. |
+| lanplcallfoid | oid       | PG_PROC.oid   | For non-internal languages, this column references the language handler, which is a special function responsible for executing all functions that are written in the particular language. |
+| laninline     | oid       | PG_PROC.oid   | This column references a function responsible for executing "inline" anonymous code blocks (DO blocks). The value is **0** if inline blocks are not supported. |
+| lanvalidator  | oid       | PG_PROC.oid   | This column references a language validator function responsible for checking the syntax and validity of new functions when they are created. The value is **0** if no validator is provided. |
+| lanacl        | aclitem[] | -             | Access permissions                                           |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_LARGEOBJECT.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_LARGEOBJECT.md
new file mode 100644
index 0000000000000000000000000000000000000000..f554ef29d755779110981a884b5b953900f30557
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_LARGEOBJECT.md
@@ -0,0 +1,22 @@
+---
+title: PG_LARGEOBJECT
+summary: PG_LARGEOBJECT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_LARGEOBJECT
+
+**PG_LARGEOBJECT** records data making up large objects. A large object is identified by an OID assigned when it is created. Each large object is broken into segments or "pages" small enough to be conveniently stored as rows in **PG_LARGEOBJECT**. The amount of data per page is defined as **LOBLKSIZE**.
+
+This system catalog is accessible only to system administrators.
+
+**Table 1** PG_LARGEOBJECT columns
+
+| Name   | Type    | Reference                   | Description                                                  |
+| :----- | :------ | :-------------------------- | :----------------------------------------------------------- |
+| loid   | oid     | PG_LARGEOBJECT_METADATA.oid | Identifier of the large object that includes this page       |
+| pageno | integer | -                           | Page number of this page within its large object (counting from zero) |
+| data   | bytea   | -                           | Data stored in the large object. This will never be more than **LOBLKSIZE** bytes and might be less. |
+
+Each row of **PG_LARGEOBJECT** holds data for one page of a large object, beginning at byte offset (**pageno \* LOBLKSIZE**) within the object. The implementation allows sparse storage: pages might be missing, and might be shorter than **LOBLKSIZE** bytes even if they are not the last page of the object. Missing regions within a large object read as zeroes.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_LARGEOBJECT_METADATA.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_LARGEOBJECT_METADATA.md
new file mode 100644
index 0000000000000000000000000000000000000000..24ed8ecbea9a4217259d4f7d5721338976a4f3d6
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_LARGEOBJECT_METADATA.md
@@ -0,0 +1,18 @@
+---
+title: PG_LARGEOBJECT_METADATA
+summary: PG_LARGEOBJECT_METADATA
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_LARGEOBJECT_METADATA
+
+**PG_LARGEOBJECT_METADATA** records metadata associated with large objects. The actual large object data is stored in **PG_LARGEOBJECT**.
+
+**Table 1** PG_LARGEOBJECT_METADATA columns
+
+| Name     | Type      | Reference     | Description                                                |
+| :------- | :-------- | :------------ | :--------------------------------------------------------- |
+| oid      | oid       | -             | Row identifier (hidden attribute, which must be specified) |
+| lomowner | oid       | PG_AUTHID.oid | Owner of the large object                                  |
+| lomacl   | aclitem[] | -             | Access permissions                                         |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_NAMESPACE.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_NAMESPACE.md
new file mode 100644
index 0000000000000000000000000000000000000000..f861e09a4154aa489e75bb2810101c023dc01df0
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_NAMESPACE.md
@@ -0,0 +1,22 @@
+---
+title: PG_NAMESPACE
+summary: PG_NAMESPACE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_NAMESPACE
+
+**PG_NAMESPACE** records namespaces, that is, schema-related information.
+
+**Table 1** PG_NAMESPACE columns
+
+| Name              | Type      | Description                                                  |
+| :---------------- | :-------- | :----------------------------------------------------------- |
+| oid               | oid       | Row identifier (hidden attribute, which must be specified)   |
+| nspname           | name      | Name of a namespace                                          |
+| nspowner          | oid       | Owner of the namespace                                       |
+| nsptimeline       | bigint    | Timeline when the namespace is created on the database node. This column is for internal use and valid only on the database node. |
+| nspacl            | aclitem[] | Access permissions                                           |
+| in_redistribution | "char"    | Whether the content is in the redistribution state           |
+| nspblockchain     | Boolean   | - If the value is **true**, the tamper-proof mode is used.<br />- If the value is **false**, the non-tamper-proof mode is used. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OBJECT.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OBJECT.md
new file mode 100644
index 0000000000000000000000000000000000000000..0fbb09144fa16bf9e69fb5b2425c5456d0cd665c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OBJECT.md
@@ -0,0 +1,30 @@
+---
+title: PG_OBJECT
+summary: PG_OBJECT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_OBJECT
+
+**PG_OBJECT** records the creator, creation time, and last modification time of objects of specified types (ordinary tables, indexes, sequences, views, stored procedures, and functions).
+
+**Table 1** PG_OBJECT columns
+
+| Name        | Type                     | Description                                                  |
+| :---------- | :----------------------- | :----------------------------------------------------------- |
+| object_oid  | oid                      | Object identifier                                            |
+| object_type | "char"                   | Object type<br/>- **r**: ordinary table<br/>- **i**: index<br/>- **s**: sequence<br/>- **v**: view<br/>- **p**: stored procedure and function |
+| creator     | oid                      | ID of the creator                                            |
+| ctime       | timestamp with time zone | Creation time of the object                                  |
+| mtime       | timestamp with time zone | Last modification time of the object. The modification operations include **ALTER**, **GRANT**, and **REVOKE**. |
+| createcsn   | int8                     | CSN when an object is created                                |
+| changecsn   | int8                     | CSN when DDL operations are performed on a table or an index |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - Objects created or modified during database initialization (initdb) cannot be recorded. **PG_OBJECT** does not contain these object records.
+> - When an object created before the upgrade is modified again, the modification time (specified by **mtime**) is recorded. When DDL operations are performed on a table or an index, the transaction commit sequence number (specified by **changecsn**) of the transaction to which the table or index belongs is recorded. Because the creation time of the object cannot be obtained, **ctime** and **createcsn** are empty.
+> - The time recorded by **ctime** and **mtime** is the start time of the transaction to which the current operation belongs.
+> - The time of object modification due to capacity expansion is also recorded.
+> - **createcsn** and **changecsn** record the transaction commit sequence number of the transaction to which the current operation belongs.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OPCLASS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OPCLASS.md
new file mode 100644
index 0000000000000000000000000000000000000000..afa5822c09c20b42561473513e70d18a45809f10
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OPCLASS.md
@@ -0,0 +1,28 @@
+---
+title: PG_OPCLASS
+summary: PG_OPCLASS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_OPCLASS
+
+**PG_OPCLASS** defines index access method operator classes.
+
+Each operator class defines semantics for index columns of a particular data type and a particular index access method. An operator class essentially specifies that a particular operator family is applicable to a particular indexable column data type. The set of operators from the family that are actually usable with the indexed column are whichever ones accept the column's data type as their left-hand input.
+
+**Table 1** PG_OPCLASS columns
+
+| Name         | Type    | Reference        | Description                                                  |
+| :----------- | :------ | :--------------- | :----------------------------------------------------------- |
+| oid          | oid     | -                | Row identifier (hidden attribute, which must be specified)   |
+| opcmethod    | oid     | PG_AM.oid        | Index access method operator class served by an operator class |
+| opcname      | name    | -                | Name of the operator class                                   |
+| opcnamespace | oid     | PG_NAMESPACE.oid | Namespace of the operator class                              |
+| opcowner     | oid     | PG_AUTHID.oid    | Owner of the operator class                                  |
+| opcfamily    | oid     | PG_OPFAMILY.oid  | Operator family containing the operator class                |
+| opcintype    | oid     | PG_TYPE.oid      | Data type that the operator class indexes                    |
+| opcdefault   | Boolean | -                | The value is **true** if this operator class is the default for **opcintype**. |
+| opckeytype   | oid     | PG_TYPE.oid      | Type of data stored in index, or zero if same as **opcintype** |
+
+An operator class's **opcmethod** must match the **opfmethod** of its containing operator family.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OPERATOR.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OPERATOR.md
new file mode 100644
index 0000000000000000000000000000000000000000..bc6b4f93dc0c5703a57b2d5ea3005d2d18e27f1d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OPERATOR.md
@@ -0,0 +1,30 @@
+---
+title: PG_OPERATOR
+summary: PG_OPERATOR
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_OPERATOR
+
+**PG_OPERATOR** records information about operators.
+
+**Table 1** PG_OPERATOR columns
+
+| Name         | Type    | Reference        | Description                                                  |
+| :----------- | :------ | :--------------- | :----------------------------------------------------------- |
+| oid          | oid     | -                | Row identifier (hidden attribute, which must be specified)   |
+| oprname      | name    | -                | Name of an operator                                          |
+| oprnamespace | oid     | PG_NAMESPACE.oid | OID of the namespace that contains the operator              |
+| oprowner     | oid     | PG_AUTHID.oid    | Owner of the operator                                        |
+| oprkind      | "char"  | -                | - **b**: infix ("both")<br/>- **l**: prefix ("left")<br/>- **r**: postfix ("right") |
+| oprcanmerge  | Boolean | -                | Whether the operator supports merge joins<br />- **t (true)**: yes<br />- **f (false)**: no |
+| oprcanhash   | Boolean | -                | Whether the operator supports hash joins<br />- **t (true)**: yes<br />- **f (false)**: no |
+| oprleft      | oid     | PG_TYPE.oid      | Type of the left operand                                     |
+| oprright     | oid     | PG_TYPE.oid      | Type of the right operand                                    |
+| oprresult    | oid     | PG_TYPE.oid      | Type of the result                                           |
+| oprcom       | oid     | PG_OPERATOR.oid  | Commutator of this operator, if any                          |
+| oprnegate    | oid     | PG_OPERATOR.oid  | Negator of this operator, if any                             |
+| oprcode      | regproc | PG_PROC.proname  | Function that implements the operator                        |
+| oprrest      | regproc | PG_PROC.proname  | Restriction selectivity estimation function for the operator |
+| oprjoin      | regproc | PG_PROC.proname  | Join selectivity estimation function for the operator        |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OPFAMILY.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OPFAMILY.md
new file mode 100644
index 0000000000000000000000000000000000000000..9664fdf6d689d741da7da549c366a8391f60ff18
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OPFAMILY.md
@@ -0,0 +1,24 @@
+---
+title: PG_OPFAMILY
+summary: PG_OPFAMILY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_OPFAMILY
+
+**PG_OPFAMILY** defines operator families.
+
+Each operator family is a collection of operators and associated support routines that implement semantics specified for a particular index access method. Furthermore, the operators in a family are all compatible, in a way that is specified by the access method. The operator family allows cross-data-type operators to be used with indexes and to be reasoned about using knowledge of access method semantics.
+
+**Table 1** PG_OPFAMILY columns
+
+| Name         | Type | Reference        | Description                                                |
+| :----------- | :--- | :--------------- | :--------------------------------------------------------- |
+| oid          | oid  | -                | Row identifier (hidden attribute, which must be specified) |
+| opfmethod    | oid  | PG_AM.oid        | Index access method used by an operator family             |
+| opfname      | name | -                | Name of the operator family                                |
+| opfnamespace | oid  | PG_NAMESPACE.oid | Namespace of the operator family                           |
+| opfowner     | oid  | PG_AUTHID.oid    | Owner of the operator family                               |
+
+The majority of the information defining an operator family is not in its **PG_OPFAMILY** row, but in the associated rows in PG_AMOP, PG_AMPROC, and PG_OPCLASS.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_PARTITION.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_PARTITION.md
new file mode 100644
index 0000000000000000000000000000000000000000..207b7f7e6f02cc912ff4d0cdcaa3addb7d45f82d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_PARTITION.md
@@ -0,0 +1,44 @@
+---
+title: PG_PARTITION
+summary: PG_PARTITION
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_PARTITION
+
+**PG_PARTITION** records all partitioned tables, table partitions, TOAST tables on table partitions, and index partitions in the database. Partitioned index information is not stored in the system catalog **PG_PARTITION**.
+
+**Table 1** PG_PARTITION columns
+
+| Name               | Type             | Description                                                  |
+| :----------------- | :--------------- | :----------------------------------------------------------- |
+| oid                | oid              | Row identifier (hidden attribute, which must be specified)   |
+| relname            | name             | Names of the partitioned tables, table partitions, TOAST tables on table partitions, and index partitions |
+| parttype           | "char"           | Object type<br />- **r**: partitioned table<br />- **p**: table partition<br />- **x**: index partition<br />- **t**: TOAST table |
+| parentid           | oid              | OID of the partitioned table in **PG_CLASS** when the object is a partitioned table or table partition<br />OID of the partitioned index when the object is an index partition |
+| rangenum           | integer          | Reserved                                                     |
+| intervalnum        | integer          | Reserved                                                     |
+| partstrategy       | "char"           | Partition policy of the partitioned table<br />- **r**: range partition<br />- **v**: numeric partition<br />- **i**: interval partition<br />- **l**: list partition<br />- **h**: hash partition<br />- **n**: invalid partition |
+| relfilenode        | oid              | Physical storage locations of the table partition, index partition, and TOAST table on the table partition |
+| reltablespace      | oid              | OID of the tablespace containing the table partition, index partition, and TOAST table on the table partition |
+| relpages           | double precision | Statistics: numbers of data pages of the table partition and index partition |
+| reltuples          | double precision | Statistics: numbers of tuples of the table partition and index partition |
+| relallvisible      | integer          | Statistics: number of visible data pages of the table partition and index partition |
+| reltoastrelid      | oid              | OID of the TOAST table corresponding to the table partition  |
+| reltoastidxid      | oid              | OID of the TOAST table index corresponding to the table partition |
+| indextblid         | oid              | OID of the table partition corresponding to the index partition |
+| indisusable        | Boolean          | Whether the index partition is available                     |
+| reldeltarelid      | oid              | OID of a Delta table                                         |
+| reldeltaidx        | oid              | OID of the index for a Delta table                           |
+| relcudescrelid     | oid              | OID of a CU description table                                |
+| relcudescidx       | oid              | OID of the index for a CU description table                  |
+| relfrozenxid       | xid32            | Frozen transaction ID<br />To ensure forward compatibility, this column is reserved. The **relfrozenxid64** column is added to record the information. |
+| intspnum           | integer          | Number of tablespaces that the interval partition belongs to |
+| partkey            | int2vector       | Column number of the partition key                           |
+| intervaltablespace | oidvector        | Tablespace that the interval partition belongs to. Interval partitions fall in the tablespaces in the round-robin manner. |
+| interval           | text[]           | Interval value of the interval partition                     |
+| boundaries         | text[]           | Upper boundary of the range partition and interval partition |
+| transit            | text[]           | Transit of the interval partition                            |
+| reloptions         | text[]           | Storage property of a partition used for collecting online scale-out information. Same as **pg_class.reloptions**, it is expressed in a string in the format of keyword=value. |
+| relfrozenxid64     | xid              | Frozen transaction ID                                        |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_PLTEMPLATE.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_PLTEMPLATE.md
new file mode 100644
index 0000000000000000000000000000000000000000..adb19007b3c9d4497f719d2d6d72b61a448631cc
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_PLTEMPLATE.md
@@ -0,0 +1,23 @@
+---
+title: PG_PLTEMPLATE
+summary: PG_PLTEMPLATE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_PLTEMPLATE
+
+**PG_PLTEMPLATE** records template information for procedural languages.
+
+**Table 1** PG_PLTEMPLATE columns
+
+| Name          | Type      | Description                                                  |
+| :------------ | :-------- | :----------------------------------------------------------- |
+| tmplname      | name      | Name of the language for which this template is used         |
+| tmpltrusted   | Boolean   | The value is **true** if the language is considered trusted. |
+| tmpldbacreate | Boolean   | The value is **true** if the language is created by the owner of the database. |
+| tmplhandler   | text      | Name of the call handler function                            |
+| tmplinline    | text      | Name of the anonymous block handler (**NULL** if no name of the block handler exists) |
+| tmplvalidator | text      | Name of the verification function (**NULL** if no verification function is available) |
+| tmpllibrary   | text      | Path of the shared library that implements languages         |
+| tmplacl       | aclitem[] | Access permissions for template (not yet used)               |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_PROC.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_PROC.md
new file mode 100644
index 0000000000000000000000000000000000000000..f3fd4bbd022fbbfb99c3fc4f57f15d4b0c7c9a8f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_PROC.md
@@ -0,0 +1,53 @@
+---
+title: PG_PROC
+summary: PG_PROC
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_PROC
+
+**PG_PROC** records information about functions or procedures.
+
+**Table 1** PG_PROC columns
+
+| Name                | Type              | Description                                                  |
+| :------------------ | :---------------- | :----------------------------------------------------------- |
+| oid                 | oid               | Row identifier (hidden attribute, which must be specified)   |
+| proname             | name              | Function name                                                |
+| pronamespace        | oid               | OID of the namespace that contains the function              |
+| proowner            | oid               | Owner of the function                                        |
+| prolang             | oid               | Implementation language or call interface of the function    |
+| procost             | real              | Estimated execution cost                                     |
+| prorows             | real              | Estimated number of rows that are influenced                 |
+| provariadic         | oid               | Data type of parameter element                               |
+| protransform        | regproc           | Simplified call method for the function                      |
+| proisagg            | Boolean           | Whether the function is an aggregate function<br />- **t** (true): yes<br />- **f** (false): no |
+| proiswindow         | Boolean           | Whether the function is a window function<br />- **t** (true): yes<br />- **f** (false): no |
+| prosecdef           | Boolean           | Whether the function is a security definer (or a "setuid" function)<br />- **t** (true): yes<br />- **f** (false): no |
+| proleakproof        | Boolean           | This function has no side effect. If no leakproof treatment is provided for parameters, the function throws errors.<br />- **t** (true): There is no side effect.<br />- **f** (false): There are side effects. |
+| proisstrict         | Boolean           | The function returns null if any call parameter is null. In that case, the function is actually not called at all. Functions that are not "strict" must be prepared to process null inputs. |
+| proretset           | Boolean           | The function returns a set (multiple values of a specified data type). |
+| provolatile         | "char"            | Whether the function's result depends only on its input parameters, or is affected by outside factors.<br />- **i**: for "immutable" functions, which always deliver the same result for the same inputs.<br />- **s**: for "stable" functions, whose results (for fixed inputs) do not change within a scan.<br />- **v**: for "volatile" functions, whose results may change at any time. Use **v** also for functions with side-effects, so that the engine cannot get optimized if volatile functions are called. |
+| pronargs            | smallint          | Number of parameters                                         |
+| pronargdefaults     | smallint          | Number of parameters that have default values                |
+| prorettype          | oid               | Data type of return values                                   |
+| proargtypes         | oidvector         | Array that stores the data types of function parameters. This array includes only input parameters (including **INOUT** parameters), and indicates the call signature (interface) of the function. |
+| proallargtypes      | oid[]             | Array that contains the data types of function parameters. This array includes all parameter types (including **OUT** and **INOUT** parameters); however, if all the parameters are **IN** parameters, this column is null. Note that array subscripting is 1-based, whereas for historical reasons, **proargtypes** is subscripted from 0. |
+| proargmodes         | "char"[]          | Array with the modes of the function parameters, encoded as follows:<br />- **i** indicates the IN parameter.<br />- **o** indicates the OUT parameter.<br />- **b** indicates the INOUT parameter.<br />- **v** indicates the VARIADIC parameter.<br />If all the parameters are **IN** parameters, this column is null. Note that subscripts correspond to positions of **proallargtypes**, not **proargtypes**. |
+| proargnames         | text[]            | Array that stores the names of the function parameters. Parameters without a name are set to empty strings in the array. If none of the parameters have a name, this column is null. Note that subscripts correspond to positions of **proallargtypes**, not **proargtypes**. |
+| proargdefaults      | pg_node_tree      | Expression tree of the default value. This is the list of **pronargdefaults** elements. |
+| prosrc              | text              | A definition that describes a function or stored procedure. In an interpreting language, it is the function source code, a link symbol, a file name, or any body content specified when a function or stored procedure is created, depending on how a language or call is used. |
+| probin              | text              | Additional information about how to call the function. Again, the interpretation is language-specific. |
+| proconfig           | text[]            | Function's local settings for run-time configuration variables. |
+| proacl              | aclitem[]         | Access permissions. For details, see GRANT and REVOKE.       |
+| prodefaultargpos    | int2vector        | Position of the input parameter of a function with a default value. |
+| fencedmode          | Boolean           | Execution mode of a function, indicating whether the function is executed in fence or not fence mode. If the execution mode is **fence,** the function is executed in the fork process that is reworked.<br />In the C function created by the user, the default value of fencedmode is **true**, indicating the fence mode. For built-in functions in the system, the fencedmode field is set to **false**, indicating the not fence mode. |
+| proshippable        | Boolean           | Whether the function can be pushed down to database nodes. The default value is **false**.<br />- Functions of the IMMUTABLE type can always be pushed down to the database nodes.<br />- A STABLE or VOLATILE function can be pushed down to the database nodes only if SHIPPABLE is specified for it. |
+| propackage          | Boolean           | Whether the function supports overloading. The default value is **false**.<br />- **t** (true): supported.<br />- **f** (false): not supported. |
+| prokind             | "char"            | Whether the object is a function or a stored procedure.<br />- **f** indicates that the object is a function.<br />- **p** indicates that the object is a stored procedure. |
+| proargsrc           | text              | Describes the parameter input strings of functions or stored procedures that are compatible with Oracle syntax, including parameter comments. The default value is **NULL**. |
+| proisprivate        | Boolean           | Whether a function is a private function in the package. The default value is **false**. |
+| propackageid        | oid               | OID of the package to which the function belongs. If the function is not in the package, the value is **0**. |
+| proargtypesext      | oidvector_extend  | Data type array used to store function parameters when there are a large number of function parameters. This array includes only input parameters (including **INOUT** parameters), and indicates the call signature (interface) of the function. |
+| prodefaultargposext | int2vector_extend | Position of the input parameter with a default value when the function has a large number of parameters. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_RANGE.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_RANGE.md
new file mode 100644
index 0000000000000000000000000000000000000000..d433b1434bf078c81ec71c910d99988339671b2d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_RANGE.md
@@ -0,0 +1,23 @@
+---
+title: PG_RANGE
+summary: PG_RANGE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_RANGE
+
+**PG_RANGE** records information about range types. Entries in PG_TYPE are excluded.
+
+**Table 1** PG_RANGE columns
+
+| Name         | Type    | Reference        | Description                                                  |
+| :----------- | :------ | :--------------- | :----------------------------------------------------------- |
+| rngtypid     | oid     | PG_TYPE.oid      | OID of the range type                                        |
+| rngsubtype   | oid     | PG_TYPE.oid      | OID of the element type (subtype) of this range type         |
+| rngcollation | oid     | PG_COLLATION.oid | OID of the collation used for range comparisons (**0** if none) |
+| rngsubopc    | oid     | PG_OPCLASS.oid   | OID of the subtype's operator class used for range comparisons |
+| rngcanonical | regproc | PG_PROC.proname  | Name of the function to convert a range value into canonical form (**0** if none) |
+| rngsubdiff   | regproc | PG_PROC.proname  | Name of the function to return the difference between two element values as **double precision** (**0** if none) |
+
+**rngsubopc** (together with **rngcollation**, if the element type is collatable) determines the sort ordering used by the range type. **rngcanonical** is used when the element type is discrete.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_RESOURCE_POOL.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_RESOURCE_POOL.md
new file mode 100644
index 0000000000000000000000000000000000000000..9f6d65b3832cae4b6a48688c714c60ccc51b95e4
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_RESOURCE_POOL.md
@@ -0,0 +1,31 @@
+---
+title: PG_RESOURCE_POOL
+summary: PG_RESOURCE_POOL
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_RESOURCE_POOL
+
+**PG_RESOURCE_POOL** provides information about database resource pools.
+
+**Table 1** PG_RESOURCE_POOL columns
+
+| Name              | Type    | Description                                                  |
+| :---------------- | :------ | :----------------------------------------------------------- |
+| oid               | oid     | Row identifier (hidden attribute, which must be specified)   |
+| respool_name      | name    | Name of a resource pool                                      |
+| mem_percent       | integer | Percentage of the memory configuration                       |
+| cpu_affinity      | bigint  | Value of cores bound to the CPU                              |
+| control_group     | name    | Name of the Cgroup where the resource pool is located        |
+| active_statements | integer | Maximum number of concurrent statements in the resource pool |
+| max_dop           | integer | Maximum scanning concurrency during data redistribution. This column is used for scaling. |
+| memory_limit      | name    | Maximum memory of the resource pool                          |
+| parentid          | oid     | OID of the parent resource pool                              |
+| io_limits         | integer | Upper limit of I/O operations per second. It is counted by ones for column storage and by 10 thousands for row storage. |
+| io_priority       | name    | I/O priority set for jobs that consume many I/O resources. It takes effect when I/O usage reaches 90%. |
+| nodegroup         | name    | Name of the logical MogDB to which the resource pool belongs |
+| is_foreign        | boolean | Whether the resource pool can be used for users outside the logical MogDB. If it is set to **true**, the resource pool controls the resources of common users who do not belong to the current resource pool. |
+| max_worker        | integer | Concurrency in a table during data redistribution. This column is used only for scaling. |
+
+Note: max_dop and max_worker user expansion is not applicable to MogDB.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_REWRITE.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_REWRITE.md
new file mode 100644
index 0000000000000000000000000000000000000000..e5835278d3b8993891328d2293af7ea40a201115
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_REWRITE.md
@@ -0,0 +1,24 @@
+---
+title: PG_REWRITE
+summary: PG_REWRITE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_REWRITE
+
+**PG_REWRITE** records rewrite rules defined for tables and views.
+
+**Table 1** PG_REWRITE columns
+
+| Name       | Type         | Description                                                  |
+| :--------- | :----------- | :----------------------------------------------------------- |
+| oid        | oid          | Row identifier (hidden attribute, which must be specified)   |
+| rulename   | name         | Name of a rule                                               |
+| ev_class   | oid          | Name of the table that uses the rule                         |
+| ev_attr    | smallint     | Column to which this rule applies (always **0** to indicate the entire table) |
+| ev_type    | "char"       | Event type for this rule<br/>- 1 = SELECT<br/>- 2 = UPDATE<br/>- 3 = INSERT<br/>- 4 = DELETE |
+| ev_enabled | "char"       | Controls the mode in which the rule is triggered.<br/>- **O**: The rule is triggered in origin and local modes.<br/>- **D**: The rule is disabled.<br/>- **R**: The rule is triggered in replica mode.<br/>- **A**: The rule is always triggered. |
+| is_instead | Boolean      | The value is **true** if the rule is of the **INSTEAD** type. |
+| ev_qual    | pg_node_tree | Expression tree (in the form of a **nodeToString**() representation) for the rule's qualifying condition |
+| ev_action  | pg_node_tree | Query tree (in the form of a **nodeToString**() representation) for the rule's action |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_RLSPOLICY.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_RLSPOLICY.md
new file mode 100644
index 0000000000000000000000000000000000000000..0cfb41f8c5d42b4aba93729a04cf2c562e823cff
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_RLSPOLICY.md
@@ -0,0 +1,22 @@
+---
+title: PG_RLSPOLICY
+summary: PG_RLSPOLICY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_RLSPOLICY
+
+**PG_RLSPOLICY** records row-level access control policies.
+
+**Table 1** PG_RLSPOLICY columns
+
+| Name          | Type         | Description                                                  |
+| :------------ | :----------- | :----------------------------------------------------------- |
+| oid           | oid          | Row identifier (hidden attribute, which must be specified)   |
+| polname       | name         | Name of an access control policy                             |
+| polrelid      | oid          | OID of the table object on which the row-level access control policy takes effect |
+| polcmd        | "char"       | SQL operations affected by the row-level access control policy |
+| polpermissive | boolean      | Attribute of the row-level access control policy. **t** indicates an expression that uses the OR condition, and **f** indicates an expression that uses the AND condition. |
+| polroles      | oid[]        | OID list of users affected by the row-level access control policy. If this parameter is not specified, all users are affected. |
+| polqual       | pg_node_tree | Expression of the row-level access control policy            |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SECLABEL.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SECLABEL.md
new file mode 100644
index 0000000000000000000000000000000000000000..e76097985c780bc163852b40c7a02be3d4481af5
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SECLABEL.md
@@ -0,0 +1,22 @@
+---
+title: PG_SECLABEL
+summary: PG_SECLABEL
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_SECLABEL
+
+**PG_SECLABEL** records security labels on database objects.
+
+See also PG_SHSECLABEL, which provides a similar function for security labels of database objects that are shared across MogDB.
+
+**Table 1** PG_SECLABEL columns
+
+| Name     | Type    | Reference      | Description                                            |
+| :------- | :------ | :------------- | :----------------------------------------------------- |
+| objoid   | oid     | Any OID column | OID of the object that this security label pertains to |
+| classoid | oid     | PG_CLASS.oid   | OID of the system catalog where the object appears     |
+| objsubid | integer | -              | Column number for a security label on a table column   |
+| provider | text    | -              | Label provider associated with the label               |
+| label    | text    | -              | Security label applied to the object                   |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SHDEPEND.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SHDEPEND.md
new file mode 100644
index 0000000000000000000000000000000000000000..49d3830a5d0ff7e9c0169284a7ccf53771110c53
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SHDEPEND.md
@@ -0,0 +1,41 @@
+---
+title: PG_SHDEPEND
+summary: PG_SHDEPEND
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_SHDEPEND
+
+**PG_SHDEPEND** records the dependency between database objects and shared objects, such as roles. Based on this information, MogDB can ensure that those objects are unreferenced before attempting to delete them.
+
+See also PG_DEPEND, which provides a similar function for dependencies involving objects within a single database.
+
+Unlike most system catalogs, **PG_SHDEPEND** is shared across all databases of MogDB. There is only one copy of **PG_SHDEPEND** per MogDB, not one per database.
+
+**Table 1** PG_SHDEPEND columns
+
+| Name       | Type    | Reference       | Description                                                  |
+| :--------- | :------ | :-------------- | :----------------------------------------------------------- |
+| dbid       | oid     | PG_DATABASE.oid | OID of the database where a dependent object is (**0** for a shared object) |
+| classid    | oid     | PG_CLASS.oid    | OID of the system catalog where a dependent object resides   |
+| objid      | oid     | Any OID column  | OID of the dependent object                                  |
+| objsubid   | integer | -               | Column number for a table column (**objid** and **classid** refer to the table itself); The value is **0** for all other object types. |
+| refclassid | oid     | PG_CLASS.oid    | OID of the system catalog where a referenced object is (must be a shared catalog) |
+| refobjid   | oid     | Any OID column  | OID of the referenced object                                 |
+| deptype    | "char"  | -               | Code segment defining the specific semantics of this dependency relationship. See the following for details. |
+| objfile    | text    | -               | Path of a user-defined function library file                 |
+
+In all cases, a **PG_SHDEPEND** entry indicates that the referenced object cannot be dropped without also dropping the dependent object. However, there are several subflavors identified by **deptype**:
+
+- SHARED_DEPENDENCY_OWNER (o)
+
+  The referenced object (which must be a role) is the owner of the dependent object.
+
+- SHARED_DEPENDENCY_ACL (a)
+
+  The referenced object (which must be a role) is mentioned in the access control list (ACL) of the dependent object. A **SHARED_DEPENDENCY_ACL** entry is not made for the owner of the object, since the owner will have a **SHARED_DEPENDENCY_OWNER** entry anyway.
+
+- SHARED_DEPENDENCY_PIN (p)
+
+  There is no dependent object. This type of entry is a signal that the system itself depends on the referenced object, and so that object must never be deleted. Entries of this type are created only by **initdb**. The columns for the dependent object contain zeroes.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SHDESCRIPTION.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SHDESCRIPTION.md
new file mode 100644
index 0000000000000000000000000000000000000000..e741d7d3fa063c63a4e5eefd936b06c44d0cf8c5
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SHDESCRIPTION.md
@@ -0,0 +1,22 @@
+---
+title: PG_SHDESCRIPTION
+summary: PG_SHDESCRIPTION
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_SHDESCRIPTION
+
+**PG_SHDESCRIPTION** records optional comments for shared database objects. Descriptions can be manipulated with the **COMMENT** command and viewed with psql's **\d** commands.
+
+See also **PG_DESCRIPTION**, which provides a similar function for descriptions involving objects within a single database.
+
+Unlike most system catalogs, **PG_SHDESCRIPTION** is shared across all databases of a MogDB. There is only one copy of **PG_SHDESCRIPTION** per MogDB, not one per database.
+
+**Table 1** PG_SHDESCRIPTION columns
+
+| Name        | Type | Reference      | Description                                                 |
+| :---------- | :--- | :------------- | :---------------------------------------------------------- |
+| objoid      | oid  | Any OID column | OID of the object that this description pertains to         |
+| classoid    | oid  | PG_CLASS.oid   | OID of the system catalog where the object appears          |
+| description | text | -              | Arbitrary text that serves as the description of the object |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SHSECLABEL.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SHSECLABEL.md
new file mode 100644
index 0000000000000000000000000000000000000000..99724097ff3db009da8e879ff13489d3532500ce
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SHSECLABEL.md
@@ -0,0 +1,25 @@
+---
+title: PG_SHSECLABEL
+summary: PG_SHSECLABEL
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_SHSECLABEL
+
+**PG_SHSECLABEL** records security labels on shared database objects. Security labels can be manipulated with the **SECURITY LABEL** command.
+
+For an easier way to view security labels, see PG_SECLABELS.
+
+See also PG_SECLABEL, which provides a similar function for security labels involving objects within a single database.
+
+Unlike most system catalogs, **PG_SHSECLABEL** is shared across all databases of MogDB. There is only one copy of **PG_SHSECLABEL** per MogDB, not one per database.
+
+**Table 1** PG_SHSECLABEL columns
+
+| Name     | Type | Reference      | Description                                            |
+| :------- | :--- | :------------- | :----------------------------------------------------- |
+| objoid   | oid  | Any OID column | OID of the object that this security label pertains to |
+| classoid | oid  | PG_CLASS.oid   | OID of the system catalog where the object appears     |
+| provider | text | -              | Label provider associated with the label               |
+| label    | text | -              | Security label applied to the object                   |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_STATISTIC.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_STATISTIC.md
new file mode 100644
index 0000000000000000000000000000000000000000..65dda48cbe9704d03a9419866055d65baa184fe1
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_STATISTIC.md
@@ -0,0 +1,28 @@
+---
+title: PG_STATISTIC
+summary: PG_STATISTIC
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STATISTIC
+
+**PG_STATISTIC** records statistics about tables and index columns in a database. By default, only the system administrator can access the system catalog. Common users can access the system catalog only after being authorized.
+
+**Table 1** PG_STATISTIC columns
+
+| Name          | Type     | Description                                                  |
+| :------------ | :------- | :----------------------------------------------------------- |
+| starelid      | oid      | Table or index that the described column belongs to          |
+| starelkind    | "char"   | Type of an object                                            |
+| staattnum     | smallint | Number of the described column in the table, starting from 1 |
+| stainherit    | Boolean  | Whether to collect statistics for objects that have inheritance relationship |
+| stanullfrac   | real     | Percentage of column entries that are null                   |
+| stawidth      | integer  | Average stored width, in bytes, of non-null entries          |
+| stadistinct   | real     | Number of distinct, non-**NULL** data values in the column for database nodes<br/>- A value greater than 0 is the actual number of distinct values.<br/>- A value less than 0 is the negative of a multiplier for the number of rows in the table. (For example, **stadistinct=-0.5** indicates that values in a column appear twice on average.)<br/>- The value **0** indicates that the number of distinct values is unknown. |
+| stakindN      | smallint | Code number stating that the type of statistics is stored in slot N of the **pg_statistic** row<br/>Value range: 1 to 5 |
+| staopN        | oid      | Operator used to generate the statistics stored in slot N. For example, a histogram slot shows the < operator that defines the sort order of the data.<br/>Value range: 1 to 5 |
+| stanumbersN   | real[]   | Numerical statistics of the appropriate type for slot N. The value is **NULL** if the slot does not involve numerical values.<br/>Value range: 1 to 5 |
+| stavaluesN    | anyarray | Column data values of the appropriate type for slot N. The value is **NULL** if the slot type does not store any data values. Each array's element values are actually of the specific column's data type so there is no way to define these columns' type more specifically than anyarray.<br/>Value range: 1 to 5 |
+| stadndistinct | real     | Number of unique non-null data values in the **dn1** column<br/>- A value greater than 0 is the actual number of distinct values.<br/>- A value less than 0 is the negative of a multiplier for the number of rows in the table. (For example, **stadistinct=-0.5** indicates that values in a column appear twice on average.)<br/>- The value **0** indicates that the number of distinct values is unknown. |
+| staextinfo    | text     | Information about extension statistics. This is reserved.    |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_STATISTIC_EXT.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_STATISTIC_EXT.md
new file mode 100644
index 0000000000000000000000000000000000000000..a298464e3178e2843ed8cb88913f86f694a0bc77
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_STATISTIC_EXT.md
@@ -0,0 +1,28 @@
+---
+title: PG_STATISTIC_EXT
+summary: PG_STATISTIC_EXT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STATISTIC_EXT
+
+**PG_STATISTIC_EXT** records extended statistics of tables in a database, such as statistics of multiple columns. Statistics of expressions will be supported later. You can specify the extended statistics to collect. This system catalog is accessible only to system administrators.
+
+**Table 1** PG_STATISTIC_EXT columns
+
+| Name          | Type         | Description                                                  |
+| :------------ | :----------- | :----------------------------------------------------------- |
+| starelid      | oid          | Table or index that the described column belongs to          |
+| starelkind    | "char"       | Type of the object to which a table belongs. **c** indicates an ordinary table, and **p** indicates a partitioned table. |
+| stainherit    | Boolean      | Whether to collect statistics for objects that have inheritance relationship |
+| stanullfrac   | real         | Percentage of column entries that are null                   |
+| stawidth      | integer      | Average stored width, in bytes, of non-null entries          |
+| stadistinct   | real         | Number of distinct, non-**NULL** data values in the column for database nodes<br/>- A value greater than 0 is the actual number of distinct values.<br/>- A value less than 0 is the negative of a multiplier for the number of rows in the table. (For example, **stadistinct=-0.5** indicates that values in a column appear twice on average.)<br/>- The value **0** indicates that the number of distinct values is unknown. |
+| stadndistinct | real         | Number of unique non-null data values in the **dn1** column<br/>- A value greater than 0 is the actual number of distinct values.<br/>- A value less than 0 is the negative of a multiplier for the number of rows in the table. (For example, **stadistinct=-0.5** indicates that values in a column appear twice on average.)<br/>- The value **0** indicates that the number of distinct values is unknown. |
+| stakindN      | smallint     | Code number stating that the type of statistics is stored in slot N of the **pg_statistic** row<br/>Value range: 1 to 5 |
+| staopN        | oid          | Operator used to generate the statistics stored in slot N. For example, a histogram slot shows the < operator that defines the sort order of the data.<br/>Value range: 1 to 5 |
+| stakey        | int2vector   | Array of a column ID                                         |
+| stanumbersN   | real[]       | Numerical statistics of the appropriate type for slot N. The value is **NULL** if the slot does not involve numerical values.<br/>Value range: 1 to 5 |
+| stavaluesN    | anyarray     | Column data values of the appropriate type for slot N. The value is **NULL** if the slot type does not store any data values. Each array's element values are actually of the specific column's data type so there is no way to define these columns' type more specifically than anyarray.<br/>Value range: 1 to 5 |
+| staexprs      | pg_node_tree | Expression corresponding to the extended statistics information. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SYNONYM.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SYNONYM.md
new file mode 100644
index 0000000000000000000000000000000000000000..64d9d4fe2f4dd330dc53a610f578facbe8f56839
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SYNONYM.md
@@ -0,0 +1,21 @@
+---
+title: PG_SYNONYM
+summary: PG_SYNONYM
+author: Guo Huan
+date: 2021-07-26
+---
+
+# PG_SYNONYM
+
+**PG_SYNONYM** records the mapping between synonym object names and other database object names.
+
+**Table 1** **PG_SYNONYM** columns
+
+| Name         | Type | Description                                                  |
+| :----------- | :--- | :----------------------------------------------------------- |
+| oid-         | oid  | Database object ID                                           |
+| synname      | name | Synonym name                                                 |
+| synnamespace | oid  | OID of the namespace that contains the synonym               |
+| synowner     | oid  | Owner of the synonym, usually the OID of the user who created it |
+| synobjschema | name | Schema name specified by the associated object               |
+| synobjname   | name | Name of the associated object                                |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TABLESPACE.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TABLESPACE.md
new file mode 100644
index 0000000000000000000000000000000000000000..b63f17a286da912a88305447994afabeec706f79
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TABLESPACE.md
@@ -0,0 +1,22 @@
+---
+title: PG_TABLESPACE
+summary: PG_TABLESPACE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_TABLESPACE
+
+**PG_TABLESPACE** records tablespace information.
+
+**Table 1** PG_TABLESPACE columns
+
+| Name       | Type      | Description                                                  |
+| :--------- | :-------- | :----------------------------------------------------------- |
+| oid        | oid       | Row identifier (hidden attribute, which must be specified)   |
+| spcname    | name      | Tablespace name                                              |
+| spcowner   | oid       | Owner of the tablespace, usually the user who created it     |
+| spcacl     | aclitem[] | Access permissions. For details, see [GRANT](108-GRANT) and [REVOKE](120-REVOKE). |
+| spcoptions | text[]    | Options of the tablespace                                    |
+| spcmaxsize | text      | Maximum size of the available disk space, in bytes           |
+| relative   | boolean   | Whether the storage path specified by the tablespace is a relative path |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TRIGGER.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TRIGGER.md
new file mode 100644
index 0000000000000000000000000000000000000000..673cbe3b606b3599b0a4112eabf22ed121c89dab
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TRIGGER.md
@@ -0,0 +1,32 @@
+---
+title: PG_TRIGGER
+summary: PG_TRIGGER
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_TRIGGER
+
+**PG_TRIGGER** records trigger information.
+
+**Table 1** PG_TRIGGER columns
+
+| Name           | Type         | Description                                                  |
+| :------------- | :----------- | :----------------------------------------------------------- |
+| oid            | oid          | Row identifier (hidden attribute, which must be specified)   |
+| tgrelid        | oid          | OID of the table where the trigger is located                |
+| tgname         | name         | Trigger name                                                 |
+| tgfoid         | oid          | The function to be called by the trigger.                    |
+| tgtype         | smallint     | Trigger type                                                 |
+| tgenabled      | "char"       | - **O**: The trigger is triggered in origin or local mode.<br/>- **D**: The trigger is disabled.<br/>- **R**: The trigger is triggered in replica mode.<br/>- **A**: The trigger is always triggered. |
+| tgisinternal   | boolean      | Whether the trigger is an internal trigger                   |
+| tgconstrrelid  | oid          | Table referenced by the integrity constraint                 |
+| tgconstrindid  | oid          | Index of the integrity constraint                            |
+| tgconstraint   | oid          | OID of the constraint trigger in **PG_CONSTRAINT**           |
+| tgdeferrable   | boolean      | Whether the constraint trigger is of the DEFERRABLE type     |
+| tginitdeferred | boolean      | Whether the trigger is of the INITIALLY DEFERRED type        |
+| tgnargs        | smallint     | Number of input parameters of the trigger function           |
+| tgattr         | int2vector   | Column ID specified by the trigger. If no column is specified, an empty array is used. |
+| tgargs         | bytea        | Parameter transferred to the trigger                         |
+| tgqual         | pg_node_tree | WHEN condition of the trigger (**NULL** if the WHEN condition does not exist) |
+| tgowner        | oid          | trigger owner                                                |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_CONFIG.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_CONFIG.md
new file mode 100644
index 0000000000000000000000000000000000000000..eb6114c2c1a61d865ea38a27efbaff7ff647793f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_CONFIG.md
@@ -0,0 +1,23 @@
+---
+title: PG_TS_CONFIG
+summary: PG_TS_CONFIG
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_TS_CONFIG
+
+**PG_TS_CONFIG** contains entries representing text search configurations. A configuration specifies a particular text search parser and a list of dictionaries to use for each of the parser's output token types.
+
+The parser is shown in the **PG_TS_CONFIG** entry, but the token-to-dictionary mapping is defined by subsidiary entries in PG_TS_CONFIG_MAP.
+
+**Table 1** PG_TS_CONFIG columns
+
+| Name         | Type   | Reference        | Description                                                |
+| :----------- | :----- | :--------------- | :--------------------------------------------------------- |
+| oid          | oid    | -                | Row identifier (hidden attribute, which must be specified) |
+| cfgname      | name   | -                | Text search configuration name                             |
+| cfgnamespace | oid    | PG_NAMESPACE.oid | OID of the namespace that contains the configuration       |
+| cfgowner     | oid    | PG_AUTHID.oid    | Owner of the configuration                                 |
+| cfgparser    | oid    | PG_TS_PARSER.oid | OID of the text search parser for this configuration       |
+| cfoptions    | text[] | -                | Configuration options                                      |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_CONFIG_MAP.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_CONFIG_MAP.md
new file mode 100644
index 0000000000000000000000000000000000000000..9819bdceefddcb6ba782f2fa0c54cec47799a40c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_CONFIG_MAP.md
@@ -0,0 +1,19 @@
+---
+title: PG_TS_CONFIG_MAP
+summary: PG_TS_CONFIG_MAP
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_TS_CONFIG_MAP
+
+**PG_TS_CONFIG_MAP** contains entries showing which text search dictionaries should be consulted, and in what order, for each output token type of each text search configuration's parser.
+
+**Table 1** PG_TS_CONFIG_MAP columns
+
+| Name         | Type    | Reference           | Description                                                  |
+| :----------- | :------ | :------------------ | :----------------------------------------------------------- |
+| mapcfg       | oid     | OID in PG_TS_CONFIG | OID of the PG_TS_CONFIG entry owning this map entry          |
+| maptokentype | integer | -                   | Token type generated by the configuration's parser           |
+| mapseqno     | integer | -                   | Sequence number of a token type when the values of **mapcfg** or **maptokentype** are the same |
+| mapdict      | oid     | OID in PG_TS_DICT   | OID of the text search dictionary to consult                 |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_DICT.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_DICT.md
new file mode 100644
index 0000000000000000000000000000000000000000..324fbab0a60c28d81ddfbcc1a9cdb105b66ae003
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_DICT.md
@@ -0,0 +1,23 @@
+---
+title: PG_TS_DICT
+summary: PG_TS_DICT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_TS_DICT
+
+**PG_TS_DICT** contains entries that define text search dictionaries. A dictionary depends on a text search template, which specifies all the implementation functions needed; the dictionary itself provides values for the user-settable parameters supported by the template.
+
+This division of labor allows dictionaries to be created by unprivileged users. The parameters are specified by a text string **dictinitoption**, whose format and meaning vary depending on the template.
+
+**Table 1** PG_TS_DICT columns
+
+| Name           | Type | Reference          | Description                                                |
+| :------------- | :--- | :----------------- | :--------------------------------------------------------- |
+| oid            | oid  | -                  | Row identifier (hidden attribute, which must be specified) |
+| dictname       | name | -                  | Text search dictionary name                                |
+| dictnamespace  | oid  | PG_NAMESPACE.oid   | OID of the namespace that contains the dictionary          |
+| dictowner      | oid  | PG_AUTHID.oid      | Owner of the dictionary                                    |
+| dicttemplate   | oid  | PG_TS_TEMPLATE.oid | OID of the text search template for the dictionary         |
+| dictinitoption | text | -                  | Initialization option string for the template              |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_PARSER.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_PARSER.md
new file mode 100644
index 0000000000000000000000000000000000000000..447a5b67867434647d37f21c60530643aed8fb89
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_PARSER.md
@@ -0,0 +1,23 @@
+---
+title: PG_TS_PARSER
+summary: PG_TS_PARSER
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_TS_PARSER
+
+**PG_TS_PARSER** contains entries defining text search parsers. A parser is responsible for splitting input text into lexemes and assigning a token type to each lexeme. The new parser must be created by the database system administrator.
+
+**Table 1** PG_TS_PARSER columns
+
+| Name         | Type    | Reference        | Description                                                |
+| :----------- | :------ | :--------------- | :--------------------------------------------------------- |
+| oid          | oid     | -                | Row identifier (hidden attribute, which must be specified) |
+| prsname      | name    | -                | Text search parser name                                    |
+| prsnamespace | oid     | PG_NAMESPACE.oid | OID of the namespace that contains the parser              |
+| prsstart     | regproc | PG_PROC.proname  | Name of the parser's startup function                      |
+| prstoken     | regproc | PG_PROC.proname  | Name of the parser's next-token function                   |
+| prsend       | regproc | PG_PROC.proname  | Name of the parser's shutdown function                     |
+| prsheadline  | regproc | PG_PROC.proname  | Name of the parser's headline function                     |
+| prslextype   | regproc | PG_PROC.proname  | Name of the parser's lextype function                      |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_TEMPLATE.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_TEMPLATE.md
new file mode 100644
index 0000000000000000000000000000000000000000..b8fa4c52d054e631e65c2f537f47c461795ff9c9
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_TEMPLATE.md
@@ -0,0 +1,20 @@
+---
+title: PG_TS_TEMPLATE
+summary: PG_TS_TEMPLATE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_TS_TEMPLATE
+
+**PG_TS_TEMPLATE** contains entries defining text search templates. A template provides a framework for text search dictionaries. Since a template must be implemented by C-language-level functions, templates can be created only by database administrators.
+
+**Table 1** PG_TS_TEMPLATE columns
+
+| Name          | Type    | Reference        | Description                                                |
+| :------------ | :------ | :--------------- | :--------------------------------------------------------- |
+| oid           | oid     | -                | Row identifier (hidden attribute, which must be specified) |
+| tmplname      | name    | -                | Text search template name                                  |
+| tmplnamespace | oid     | PG_NAMESPACE.oid | OID of the namespace that contains the template            |
+| tmplinit      | regproc | PG_PROC.proname  | Name of the template's initialization function             |
+| tmpllexize    | regproc | PG_PROC.proname  | Name of the template's lexize function                     |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TYPE.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TYPE.md
new file mode 100644
index 0000000000000000000000000000000000000000..f1bbb0a3b011f05ff70955dd448c667a30f648c6
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TYPE.md
@@ -0,0 +1,46 @@
+---
+title: PG_TYPE
+summary: PG_TYPE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_TYPE
+
+**PG_TYPE** stores information about data types.
+
+**Table 1** PG_TYPE columns
+
+| Name           | Type         | Description                                                  |
+| :------------- | :----------- | :----------------------------------------------------------- |
+| oid            | oid          | Row identifier (hidden attribute, which must be specified)   |
+| typname        | name         | Data type name                                               |
+| typnamespace   | oid          | OID of the namespace that contains the type                  |
+| typowner       | oid          | Owner of the type                                            |
+| typlen         | smallint     | Number of bytes in the internal representation of the type for a fixed-size type. It is a negative number for a variable-length type.<br/>- The value **-1** indicates a "varlena" type (one that has a length word).<br/>- The value **-2** indicates a null-terminated C string. |
+| typbyval       | Boolean      | Whether the value of this type is passed by a parameter or reference of this column. **typbyval** is **false** if the type of **typlen** is not **1**, **2**, **4**, or **8**, because values of this type are always passed by reference of this column. **typbyval** can be **false** even if the **typlen** is passed by a parameter of this column. |
+| typtype        | "char"       | - **b**: base type.<br/>- **c**: composite type (for example, a table's row type)<br/>- **d**: domain<br/>- **p**: pseudo<br/>For details, see **typrelid** and **typbasetype**. |
+| typcategory    | "char"       | **typcategory** is an arbitrary classification of data types that is used by the parser to determine which implicit casts should be preferred. |
+| typispreferred | Boolean      | The value is **true** if conversion is performed when data meets conversion rules specified by **typcategory**. |
+| typisdefined   | Boolean      | Whether a type has been defined. It is **true** if the type is defined, and **false** if this is a placeholder entry for a not-yet-defined type. When it is **false**, nothing except the type name, namespace, and OID can be relied on. |
+| typdelim       | "char"       | Character that separates two values of this type when parsing an array input. Note that the delimiter is associated with the array element data type, not the array data type. |
+| typrelid       | oid          | If this is a composite type (see **typtype**), then this column points to the **PG_CLASS** entry that defines the corresponding table. For a free-standing composite type, the **PG_CLASS** entry does not represent a table, but it is required for the type's **PG_ATTRIBUTE** entries to link to. It is **0** for non-composite type. |
+| typelem        | oid          | If **typelem** is not **0**, it identifies another row in **PG_TYPE**. The current type can be described as an array yielding values of type **typelem**. A "true" array type has a variable length (**typlen** = **-1**), but some fixed-length types (**typlen** > **0**) also have non-zero **typelem**, for example **name** and **point**. If a fixed-length type has a **typelem**, its internal representation must be a number of values of the **typelem** data type with no other data. Variable-length array types have a header defined by the array subroutines. |
+| typarray       | oid          | If the value is not **0**, the corresponding type record is available in **PG_TYPE**. |
+| typinput       | regproc      | Input conversion function (text format)                      |
+| typoutput      | regproc      | Output conversion function (text format)                     |
+| typreceive     | regproc      | Input conversion function (binary format); **0** for non-input conversion function |
+| typsend        | regproc      | output conversion function (binary format); **0** for non-output conversion function |
+| typmodin       | regproc      | Type modifier input function; **0** if the type does not support modifiers |
+| typmodout      | regproc      | Type modifier output function; **0** if the type does not support modifiers |
+| typanalyze     | regproc      | Custom **ANALYZE** function; **0** if the standard function is used |
+| typalign       | "char"       | Alignment required when storing a value of this type. It applies to storage on disks as well as most representations of the value inside PostgreSQL. When multiple values are stored consecutively, such as in the representation of a complete row on disk, padding is inserted before a data of this type so that it begins on the specified boundary. The alignment reference is the beginning of the first datum in the sequence. Possible values are:<br/>- **c**: char alignment, that is, no alignment needed<br/>- **s**: short alignment (2 bytes on most machines)<br/>- **i**: integer alignment (4 bytes on most machines)<br/>- **d**: double alignment (8 bytes on many machines, but by no means all)<br/>NOTICE:<br/>For types used in system tables, the size and alignment defined in **PG_TYPE** must agree with the way that the compiler lays out the column in a structure representing a table row. |
+| typstorage     | "char"       | **typstorage** tells for varlena types (those with **typlen = -1**) if the type is prepared for toasting and what the default strategy for attributes of this type should be. Possible values are:<br/>- **p**: Values are always stored plain.<br/>- **e**: Value can be stored in a secondary relationship (if the relation has one, see **pg_class.reltoastrelid**).<br/>- **m**: Values can be stored compressed inline.<br/>- **x**: Values can be stored compressed inline or stored in secondary storage.<br/>NOTICE:<br/>**m** domains can also be moved out to secondary storage, but only as a last resort (**e** and **x** domains are moved first). |
+| typenotnull    | Boolean      | Whether the type has a NOTNULL constraint. Currently, it is used for domains only. |
+| typbasetype    | oid          | If this is a domain (see **typtype**), then **typbasetype** identifies the type that this one is based on. The value is **0** if this type is not a derived type. |
+| typtypmod      | integer      | Records the **typtypmod** to be applied to domains' base types by domains (the value is **-1** if the base type does not use **typmod**). This is **-1** if this type is not a domain. |
+| typndims       | integer      | Number of array dimensions for a domain that is an array (**typbasetype** is an array type; the domain's **typelem** matches the base type's **typelem**). This is **0** for types other than domains over array types. |
+| typcollation   | oid          | Sequence rule for specified types (**0** if sequencing is not supported) |
+| typdefaultbin  | pg_node_tree | **nodeToString()** representation of a default expression for the type if the value is non-null. Currently, this column is only used for domains. |
+| typdefault     | text         | The value is **NULL** if a type has no associated default value.<br/>- If **typdefaultbin** is not **NULL**, **typdefault** must contain a default expression represented by **typdefaultbin**.<br/>- If **typdefaultbin** is **NULL** and **typdefault** is not, then **typdefault** is the external representation of the type's default value, which can be fed to the type's input converter to produce a constant. |
+| typacl         | aclitem[]    | Access permissions                                           |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_USER_MAPPING.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_USER_MAPPING.md
new file mode 100644
index 0000000000000000000000000000000000000000..cfa06277c2d787ea19dabd0c34d72de51991fe49
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_USER_MAPPING.md
@@ -0,0 +1,21 @@
+---
+title: PG_USER_MAPPING
+summary: PG_USER_MAPPING
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_USER_MAPPING
+
+**PG_USER_MAPPING** records mappings from local users to remote.
+
+This system catalog is accessible only to system administrators. Common users can query the PG_USER_MAPPINGS view.
+
+**Table 1** PG_USER_MAPPING columns
+
+| Name      | Type   | Reference             | Description                                                  |
+| :-------- | :----- | :-------------------- | :----------------------------------------------------------- |
+| oid       | oid    | -                     | Row identifier (hidden attribute, which must be specified)   |
+| umuser    | oid    | PG_AUTHID.oid         | OID of the local role being mapped (**0** if the user mapping is public) |
+| umserver  | oid    | PG_FOREIGN_SERVER.oid | OID of the foreign server that contains the mapping          |
+| umoptions | text[] | -                     | User mapping specific options, expressed in a string in the format of keyword=value |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_USER_STATUS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_USER_STATUS.md
new file mode 100644
index 0000000000000000000000000000000000000000..321f189d76e669751860880a399b71b578ea21b4
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_USER_STATUS.md
@@ -0,0 +1,23 @@
+---
+title: PG_USER_STATUS
+summary: PG_USER_STATUS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_USER_STATUS
+
+**PG_USER_STATUS** provides the states of users who access the database. This system catalog is accessible only to system administrators.
+
+**Table 1** PG_USER_STATUS columns
+
+| Name            | Type                     | Description                                                  |
+| :-------------- | :----------------------- | :----------------------------------------------------------- |
+| oid             | oid                      | Row identifier (hidden attribute, which must be specified)   |
+| roloid          | oid                      | ID of a role                                                 |
+| failcount       | integer                  | Number of failed attempts                                    |
+| locktime        | timestamp with time zone | Time at which the role is locked                             |
+| rolstatus       | smallint                 | Role state<br/>- **0**: normal<br/>- **1**: The role is locked for a specific period of time because the failed login attempts exceed the threshold.<br/>- **2**: The role is locked by the administrator. |
+| permspace       | bigint                   | Size of the permanent table storage space used by a role     |
+| tempspace       | bigint                   | Size of the temporary table storage space used by a role     |
+| passwordexpired | smallint                 | Whether a password is valid.<br/>- **0**: The password is valid.<br/>- **1**: The password is invalid. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_WORKLOAD_GROUP.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_WORKLOAD_GROUP.md
new file mode 100644
index 0000000000000000000000000000000000000000..0d4e8f70b74879edde6195aefbceb85e4512d0d2
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_WORKLOAD_GROUP.md
@@ -0,0 +1,19 @@
+---
+title: PG_WORKLOAD_GROUP
+summary: PG_WORKLOAD_GROUP
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_WORKLOAD_GROUP
+
+**PG_WORKLOAD_GROUP** provides workload group information in the database.
+
+**Table 1** PG_WORKLOAD_GROUP columns
+
+| Name            | Type    | Description                                                |
+| :-------------- | :------ | :--------------------------------------------------------- |
+| oid             | oid     | Row identifier (hidden attribute, which must be specified) |
+| workload_gpname | name    | Workload group name                                        |
+| respool_oid     | oid     | ID bound to the resource pool                              |
+| act_statements  | integer | Maximum number of active statements in the workload group  |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PLAN_TABLE_DATA.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PLAN_TABLE_DATA.md
new file mode 100644
index 0000000000000000000000000000000000000000..34034add1bcbe2b05446df6cc3e18c0033740093
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PLAN_TABLE_DATA.md
@@ -0,0 +1,32 @@
+---
+title: PLAN_TABLE_DATA
+summary: PLAN_TABLE_DATA
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PLAN_TABLE_DATA
+
+**PLAN_TABLE_DATA** stores plan information collected by **EXPLAIN PLAN**. Different from the **PLAN_TABLE** view, the system catalog **PLAN_TABLE_DATA** stores **EXPLAIN PLAN** information collected by all sessions and users.
+
+**Table 1** PLAN_TABLE_DATA columns
+
+| Name         | Type           | Description                                                  |
+| :----------- | :------------- | :----------------------------------------------------------- |
+| session_id   | text           | Session that inserts the data. Its value consists of a service thread start timestamp and a service thread ID. Values are constrained by **NOT NULL**. |
+| user_id      | oid            | User who inserts the data. Values are constrained by **NOT NULL**. |
+| statement_id | varchar2(30)   | Query tag specified by a user                                |
+| plan_id      | bigint         | Query ID The ID is automatically generated in the plan generation phase and is used by kernel engineers for debugging. |
+| id           | int            | Node ID in a plan                                            |
+| operation    | varchar2(30)   | Operation description                                        |
+| options      | varchar2(255)  | Operation action                                             |
+| object_name  | name           | Name of an operated object. It is defined by users.          |
+| object_type  | varchar2(30)   | Object type                                                  |
+| object_owner | name           | Schema to which the object belongs. It is defined by users.  |
+| projection   | varchar2(4000) | Returned column information                                  |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - **PLAN_TABLE_DATA** records data of all users and sessions on the current node. Only administrators can access all the data. Common users can view their own data in the PLAN_TABLE view.
+> - Data is automatically inserted into **PLAN_TABLE_DATA** after **EXPLAIN PLAN** is executed. Therefore, do not manually insert data into or update data in **PLAN_TABLE_DATA**. Otherwise, data in **PLAN_TABLE_DATA** may be disordered. To delete data from **PLAN_TABLE_DATA**, you are advised to use the PLAN_TABLE view.
+> - Information in the **statement_id**, **object_name**, **object_owner**, and **projection** columns is stored in letter cases specified by users and information in other columns is stored in uppercase.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/STATEMENT_HISTORY.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/STATEMENT_HISTORY.md
new file mode 100644
index 0000000000000000000000000000000000000000..03d9a3c888a9b3db0148aa8439368cbdb064a9b3
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/STATEMENT_HISTORY.md
@@ -0,0 +1,72 @@
+---
+title: STATEMENT_HISTORY
+summary: STATEMENT_HISTORY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATEMENT_HISTORY
+
+**STATEMENT_HISTORY** displays information about execution statements on the current node. To query this system catalog, you must have the **sysadmin** permission. The result can be queried only in the system database but cannot be queried in the user database.
+
+The constraints on the query of this system catalog are as follows:
+
+- Data must be queried in the Postgres database. No data exists in other databases.
+- This system catalog is controlled by **track_stmt_stat_level**. The default value is **OFF,L0**, where the first part controls full SQL statements, and the second part controls slow SQL statements. For details about the record level of each field, see the following table.
+- For slow SQL statements, if the value of **track_stmt_stat_level** is not **OFF** and the SQL execution time exceeds the value of **log_min_duration_statement**, the SQL statement is recorded as a slow SQL statement.
+
+**Table 1** STATEMENT_HISTORY columns
+
+| Name                 | Type                     | Description                                                  | Record Level |
+| :------------------- | :----------------------- | :----------------------------------------------------------- | :----------- |
+| db_name              | name                     | Database name.                                               | L0           |
+| schema_name          | name                     | Schema name.                                                 | L0           |
+| origin_node          | integer                  | Node name.                                                   | L0           |
+| user_name            | name                     | Username.                                                    | L0           |
+| application_name     | text                     | Name of the application that sends a request.                | L0           |
+| client_addr          | text                     | IP address of the client that sends a request.               | L0           |
+| client_port          | integer                  | Port number of the client that sends a request.              | L0           |
+| unique_query_id      | bigint                   | ID of the normalized SQL statement.                          | L0           |
+| debug_query_id       | bigint                   | ID of the unique SQL statement.                              | L0           |
+| query                | text                     | Normalized SQL statement.                                    | L0           |
+| start_time           | timestamp with time zone | Time when a statement starts.                                | L0           |
+| finish_time          | timestamp with time zone | Time when a statement ends.                                  | L0           |
+| slow_sql_threshold   | bigint                   | Standard for slow SQL statement execution.                   | L0           |
+| transaction_id       | bigint                   | Transaction ID.                                              | L0           |
+| thread_id            | bigint                   | ID of an execution thread.                                   | L0           |
+| session_id           | bigint                   | Session ID of a user.                                        | L0           |
+| n_soft_parse         | bigint                   | Number of soft parsing times. The value of **n_soft_parse** plus the value of **n_hard_parse** may be greater than the value of **n_calls** because the number of subqueries is not counted in the value of **n_calls**. | L0           |
+| n_hard_parse         | bigint                   | Number of hard parsing times. The value of **n_soft_parse** plus the value of **n_hard_parse** may be greater than the value of **n_calls** because the number of subqueries is not counted in the value of **n_calls**. | L0           |
+| query_plan           | text                     | Statement execution plan.                                    | L1           |
+| n_returned_rows      | bigint                   | Number of rows in the result set returned by the **SELECT** statement. | L0           |
+| n_tuples_fetched     | bigint                   | Number of rows randomly scanned.                             | L0           |
+| n_tuples_returned    | bigint                   | Number of rows sequentially scanned.                         | L0           |
+| n_tuples_inserted    | bigint                   | Number of rows inserted.                                     | L0           |
+| n_tuples_updated     | bigint                   | Number of rows updated.                                      | L0           |
+| n_tuples_deleted     | bigint                   | Number of rows deleted.                                      | L0           |
+| n_blocks_fetched     | bigint                   | Number of buffer block access times.                         | L0           |
+| n_blocks_hit         | bigint                   | Number of buffer block hits.                                 | L0           |
+| db_time              | bigint                   | Valid DB time, which is accumulated if multiple threads are involved (unit: μs). | L0           |
+| cpu_time             | bigint                   | CPU time (unit: μs).                                         | L0           |
+| execution_time       | bigint                   | Execution time in the executor (unit: μs).                   | L0           |
+| parse_time           | bigint                   | SQL parsing time (unit: μs).                                 | L0           |
+| plan_time            | bigint                   | SQL plan generation time (unit: μs).                         | L0           |
+| rewrite_time         | bigint                   | SQL rewriting time (unit: μs).                               | L0           |
+| pl_execution_time    | bigint                   | Execution time of PL/pgSQL (unit: μs).                       | L0           |
+| pl_compilation_time  | bigint                   | Compilation time of PL/pgSQL (unit: μs).                     | L0           |
+| data_io_time         | bigint                   | I/O time (unit: μs).                                         | L0           |
+| net_send_info        | text                     | Network status of messages sent through a physical connection, including the time (unit: μs), number of calls, and throughput (unit: byte). This can be used to analyze the network overhead of SQL statements in a distributed system and is not supported in standalone system. Example: {"time":xxx, "n_calls":xxx, "size":xxx}. | L0           |
+| net_recv_info        | text                     | Network status of messages received through a physical connection, including the time (unit: μs), number of calls, and throughput (unit: byte). This column can be used to analyze the network overhead of SQL in a distributed system. This column is not supported in a standalone mode. Example: {"time":xxx, "n_calls":xxx, "size":xxx}. | L0           |
+| net_stream_send_info | text                     | Network status of messages sent through a logical connection, including the time (unit: μs), number of calls, and throughput (unit: byte). This column can be used to analyze the network overhead of SQL in a distributed system. This column is not supported in a standalone mode. Example: {"time":xxx, "n_calls":xxx, "size":xxx}. | L0           |
+| net_stream_recv_info | text                     | Network status of messages received through a logical connection, including the time (unit: μs), number of calls, and throughput (unit: byte). This column can be used to analyze the network overhead of SQL in a distributed system. This column is not supported in a standalone mode. Example: {"time":xxx, "n_calls":xxx, "size":xxx}. | L0           |
+| lock_count           | bigint                   | Number of locks.                                             | L0           |
+| lock_time            | bigint                   | Time required for locking.                                   | L1           |
+| lock_wait_count      | bigint                   | Number of lock waits.                                        | L0           |
+| lock_wait_time       | bigint                   | Time required for lock waiting.                              | L1           |
+| lock_max_count       | bigint                   | Maximum number of locks.                                     | L0           |
+| lwlock_count         | bigint                   | Number of lightweight locks (reserved).                      | L0           |
+| lwlock_wait_count    | bigint                   | Number of lightweight lock waits.                            | L0           |
+| lwlock_time          | bigint                   | Time required for lightweight locking (reserved).            | L1           |
+| lwlock_wait_time     | bigint                   | Time required for lightweight lock waiting.                  | L1           |
+| details              | bytea                    | List of statement lock events, which are recorded in time sequence. The number of records is affected by the **track_stmt_details_size** parameter.<br />Events include:<br />- Start locking.<br />- Complete locking.<br />- Start lock waiting.<br />- Complete lock waiting.<br />- Start unlocking.<br />- Complete unlocking.<br />- Start lightweight lock waiting.<br />- Complete lightweight lock waiting. | L2           |
+| is_slow_sql          | boolean                  | Whether the SQL statement is a slow SQL statement.           | L0           |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GET_GLOBAL_PREPARED_XACTS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GET_GLOBAL_PREPARED_XACTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..87e95f578d824913d29f135fe0bc32ce84f724e0
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GET_GLOBAL_PREPARED_XACTS.md
@@ -0,0 +1,10 @@
+---
+title: GET_GLOBAL_PREPARED_XACTS
+summary: GET_GLOBAL_PREPARED_XACTS
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# GET_GLOBAL_PREPARED_XACTS (Discarded)
+
+This view is not supported in centralized and MogDB systems.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_AUDITING.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_AUDITING.md
new file mode 100644
index 0000000000000000000000000000000000000000..8dc92bddbd01f0c862c30e8629ff1fdc4f3e4867
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_AUDITING.md
@@ -0,0 +1,22 @@
+---
+title: GS_AUDITING
+summary: GS_AUDITING
+author: Guo Huan
+date: 2021-06-15
+---
+
+# GS_AUDITING
+
+**GS_AUDITING** displays all audit information about database-related operations. Only the users with system administrator or security policy administrator permission can access this view.
+
+**Table 1** GS_AUDITING columns
+
+| Name        | Type    | Description                                                  |
+| :---------- | :------ | :----------------------------------------------------------- |
+| polname     | name    | Policy name, which must be unique                            |
+| pol_type    | text    | Audit policy type. The value can be **access** or **privilege**.<br />- **access**: DML operations are audited.<br />- **privilege**: DDL operations are audited. |
+| polenabled  | boolean | Specifies whether to enable a policy.<br />- **t** (true): enabled<br />- **f** (false): disabled |
+| access_type | bigint  | DML database operation type. For example, SELECT, INSERT, and DELETE. |
+| label_name  | name    | Specifies the resource label name. This parameter corresponds to the **polname** column in the **GS_AUDITING_POLICY** system catalog. |
+| priv_object | name    | Describes the path of the database asset.                    |
+| filter_name | text    | Logical character string of a filter criterion.              |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_AUDITING_ACCESS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_AUDITING_ACCESS.md
new file mode 100644
index 0000000000000000000000000000000000000000..d3dbabbc5e4221d7e6e9de83801f0a7e05bc3cd2
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_AUDITING_ACCESS.md
@@ -0,0 +1,22 @@
+---
+title: GS_AUDITING_ACCESS
+summary: GS_AUDITING_ACCESS
+author: Guo Huan
+date: 2021-06-15
+---
+
+# GS_AUDITING_ACCESS
+
+**GS_AUDITING_ACCESS** displays all audit information about database DML-related operations. Only the users with system administrator or security policy administrator permission can access this view.
+
+**Table 1** GS_AUDITING_ACCESS columns
+
+| Name          | Type    | Description                                                  |
+| :------------ | :------ | :----------------------------------------------------------- |
+| polname       | name    | Policy name, which must be unique                            |
+| pol_type      | text    | Audit policy type. The value **access** indicates that DML operations are audited. |
+| polenabled    | boolean | Specifies whether to enable the policy.                      |
+| access_type   | name    | DML database operation type. For example, SELECT, INSERT, and DELETE. |
+| label_name    | name    | Specifies the resource label name. This parameter corresponds to the **polname** column in the **GS_AUDITING_POLICY** system catalog. |
+| access_object | text    | Describes the path of the database asset.                    |
+| filter_name   | text    | Logical character string of a filter criterion.              |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_AUDITING_PRIVILEGE.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_AUDITING_PRIVILEGE.md
new file mode 100644
index 0000000000000000000000000000000000000000..3a827e2307fae78f89be8d596684e5206d4b8523
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_AUDITING_PRIVILEGE.md
@@ -0,0 +1,20 @@
+---
+title: GS_AUDITING_PRIVILEGE
+summary: GS_AUDITING_PRIVILEGE
+author: Guo Huan
+date: 2021-06-15
+---
+
+# GS_AUDITING_PRIVILEGE
+
+**GS_AUDITING_PRIVILEGE** displays all audit information about database DDL-related operations. Only the users with system administrator or security policy administrator permission can access this view.
+
+| Name        | Type    | Description                                                  |
+| :---------- | :------ | :----------------------------------------------------------- |
+| polname     | name    | Policy name, which must be unique                            |
+| pol_type    | text    | Audit policy type. The value **privilege** indicates that DDL operations are audited. |
+| polenabled  | boolean | Specifies whether to enable the policy.                      |
+| access_type | name    | DDL database operation type. For example, CREATE, ALTER, and DROP. |
+| label_name  | name    | Specifies the resource label name. This parameter corresponds to the **polname** column in the **GS_AUDITING_POLICY** system catalog. |
+| priv_object | text    | Full domain name of a database object.                       |
+| filter_name | text    | Logical character string of a filter criterion.              |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_CLUSTER_RESOURCE_INFO.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_CLUSTER_RESOURCE_INFO.md
new file mode 100644
index 0000000000000000000000000000000000000000..18f949300fbf8ee5bca7f7c5fabc2cc0a2f5c302
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_CLUSTER_RESOURCE_INFO.md
@@ -0,0 +1,22 @@
+---
+title: GS_CLUSTER_RESOURCE_INFO
+summary: GS_CLUSTER_RESOURCE_INFO
+author: Guo Huan
+date: 2021-06-07
+---
+
+# GS_CLUSTER_RESOURCE_INFO
+
+**GS_CLUSTER_RESOURCE_INFO** displays all DNs resource summaries. This view can be queried only when **enable_dynamic_workload** is set to **on** and the view cannot be executed on DNs. Only the user with sysadmin permission can query this view.
+
+**Table 1** GS_CLUSTER_RESOURCE_INFO columns
+
+| Name          | Type    | Description                             |
+| :------------ | :------ | :-------------------------------------- |
+| min_mem_util  | integer | Minimum memory usage of a DN            |
+| max_mem_util  | integer | Maximum memory usage of a DN            |
+| min_cpu_util  | integer | Minimum CPU usage of a DN               |
+| max_cpu_util  | integer | Maximum CPU usage of a DN               |
+| min_io_util   | integer | Minimum I/O usage of a DN               |
+| max_io_util   | integer | Maximum I/O usage of a DN               |
+| used_mem_rate | integer | Maximum memory usage of a physical node |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_FILE_STAT.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_FILE_STAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..28e4fc25648a638ae38942377c50ef47ea27d361
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_FILE_STAT.md
@@ -0,0 +1,28 @@
+---
+title: GS_FILE_STAT
+summary: GS_FILE_STAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_FILE_STAT
+
+**GS_FILE_STAT** records statistics about data file I/O to indicate I/O performance and detect performance problems such as abnormal I/O operations.
+
+**Table 1** GS_FILE_STAT columns
+
+| Name      | Type   | Description                                              |
+| :-------- | :----- | :------------------------------------------------------- |
+| filenum   | oid    | File identifier                                          |
+| dbid      | oid    | Database ID                                              |
+| spcid     | oid    | Tablespace ID                                            |
+| phyrds    | bigint | Number of times of reading physical files                |
+| phywrts   | bigint | Number of times of writing into physical files           |
+| phyblkrd  | bigint | Number of times of reading physical file blocks          |
+| phyblkwrt | bigint | Number of times of writing into physical file blocks     |
+| readtim   | bigint | Total duration of reading, in microseconds               |
+| writetim  | bigint | Total duration of writing, in microseconds               |
+| avgiotim  | bigint | Average duration of reading and writing, in microseconds |
+| lstiotim  | bigint | Duration of the last file reading, in microseconds       |
+| miniotim  | bigint | Minimum duration of reading and writing, in microseconds |
+| maxiowtm  | bigint | Maximum duration of reading and writing, in microseconds |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_INSTANCE_TIME.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_INSTANCE_TIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..52528b7d0bce42e12dd37e8f481465e521a39c1d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_INSTANCE_TIME.md
@@ -0,0 +1,29 @@
+---
+title: GS_INSTANCE_TIME
+summary: GS_INSTANCE_TIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_INSTANCE_TIME
+
+**PV_INSTANCE_TIME** records time consumption information of the current node. The time consumption information is classified into the following types:
+
+- DB_TIME: effective time spent by jobs in multi-core scenarios
+- CPU_TIME: CPU time spent
+- EXECUTION_TIME: time spent within executors
+- PARSE_TIME: time spent on parsing SQL statements
+- PLAN_TIME: time spent on generating plans
+- REWRITE_TIME: time spent on rewriting SQL statements
+- PL_EXECUTION_TIME: execution time of the PL/pgSQL stored procedure
+- PL_COMPILATION_TIME: compilation time of the PL/pgSQL stored procedure
+- NET_SEND_TIME: time spent on the network
+- DATA_IO_TIME: I/O time spent
+
+**Table 1** GS_INSTANCE_TIME columns
+
+| **Name**  | **Type** | **Description**   |
+| :-------- | :------- | :---------------- |
+| stat_id   | integer  | Statistics ID     |
+| stat_name | text     | Type name         |
+| value     | bigint   | Time value, in μs |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_LABELS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_LABELS.md
new file mode 100644
index 0000000000000000000000000000000000000000..ba6eee8f24f32713f5964e2a1f6532bc6b2a119c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_LABELS.md
@@ -0,0 +1,19 @@
+---
+title: GS_LABELS
+summary: GS_LABELS
+author: Guo Huan
+date: 2021-06-15
+---
+
+# GS_LABELS
+
+**GS_LABELS** displays all configured resource labels. Only the users with system administrator or security policy administrator permission can access this view.
+
+| Name       | Type | Description                                                  |
+| :--------- | :--- | :----------------------------------------------------------- |
+| labelname  | name | Resource label name                                          |
+| labeltype  | name | Resource label type This parameter corresponds to the **labeltype** column in the GS_POLICY_LABEL system catalog |
+| fqdntype   | name | Database resource type, such as table, schema, and index     |
+| schemaname | name | Name of the schema to which the database resource belongs    |
+| fqdnname   | name | Database resource name                                       |
+| columnname | name | Name of the database resource column. If the marked database resource is not a column, this parameter is left blank. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_MASKING.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_MASKING.md
new file mode 100644
index 0000000000000000000000000000000000000000..daea64d543b0e83dc85affd2ae58be371c5a902c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_MASKING.md
@@ -0,0 +1,19 @@
+---
+title: GS_MASKING
+summary: GS_MASKING
+author: Guo Huan
+date: 2021-06-15
+---
+
+# GS_MASKING
+
+**GS_MASKING** displays all configured dynamic masking policies. Only the users with system administrator or security policy administrator permission can access this view.
+
+| Name           | Type    | Description                                              |
+| :------------- | :------ | :------------------------------------------------------- |
+| polname        | name    | Name of the masking policy                               |
+| polenabled     | boolean | Specifies whether to enable the masking policy.          |
+| maskaction     | name    | Masking function                                         |
+| labelname      | name    | Name of the label to which the masking function applies. |
+| masking_object | text    | Masking database resource object                         |
+| filter_name    | text    | Logical expression of a filter criterion                 |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_MATVIEWS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_MATVIEWS.md
new file mode 100644
index 0000000000000000000000000000000000000000..a5d1d8f3bf09e94354236594701ea3cbe5358310
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_MATVIEWS.md
@@ -0,0 +1,21 @@
+---
+title: GS_MATVIEWS
+summary: GS_MATVIEWS
+author: Guo Huan
+date: 2021-06-15
+---
+
+# GS_MATVIEWS
+
+**GS_MATVIEWS** provides information about each materialized view in the database.
+
+**Table 1** GS_MATVIEWS columns
+
+| Name         | Type    | Reference             | Description                                                  |
+| :----------- | :------ | :-------------------- | :----------------------------------------------------------- |
+| schemaname   | name    | PG_NAMESPACE.nspname  | Name of the schema of a materialized view.                   |
+| matviewname  | name    | PG_CLASS.relname      | Name of a materialized view.                                 |
+| matviewowner | name    | PG_AUTHID.Erolname    | Owner of a materialized view.                                |
+| tablespace   | name    | PG_TABLESPACE.spcname | Tablespace name of a materialized view. If the default tablespace of the database is used, the value is null. |
+| hasindexes   | boolean | -                     | This column is true if the materialized view has (or has recently had) any indexes. |
+| definition   | text    | -                     | Definition of a materialized view (a reconstructed SELECT query). |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_OS_RUN_INFO.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_OS_RUN_INFO.md
new file mode 100644
index 0000000000000000000000000000000000000000..b1b52c93e268cb8c003f15d04b7a60dd7d6c0010
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_OS_RUN_INFO.md
@@ -0,0 +1,20 @@
+---
+title: GS_OS_RUN_INFO
+summary: GS_OS_RUN_INFO
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_OS_RUN_INFO
+
+**GS_OS_RUN_INFO** displays the running status of the OS.
+
+**Table 1** GS_OS_RUN_INFO columns
+
+| Name       | Type    | Description                                              |
+| :--------- | :------ | :------------------------------------------------------- |
+| id         | integer | ID                                                       |
+| name       | text    | Name of the OS running status                            |
+| value      | numeric | Value of the OS running status.                          |
+| comments   | text    | Remarks of the OS running status                         |
+| cumulative | Boolean | Whether the value of the OS running status is cumulative |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_REDO_STAT.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_REDO_STAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..d9244c268d8884259b3e92fe17a59ef0412da37f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_REDO_STAT.md
@@ -0,0 +1,22 @@
+---
+title: GS_REDO_STAT
+summary: GS_REDO_STAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_REDO_STAT
+
+**GS_REDO_STAT** displays statistics on the replay of session thread logs.
+
+**Table 1** GS_REDO_STAT columns
+
+| Name      | Type   | Description                                                  |
+| :-------- | :----- | :----------------------------------------------------------- |
+| phywrts   | bigint | Number of times that data is written during log replay       |
+| phyblkwrt | bigint | Number of data blocks written during log replay              |
+| writetim  | bigint | Total time required for writing data during log replay       |
+| avgiotim  | bigint | Average time required for writing data during log replay     |
+| lstiotim  | bigint | Time consumed by the last data write operation during log replay |
+| miniotim  | bigint | Minimum time consumed by a single data write operation during log replay |
+| maxiowtm  | bigint | Maximum time consumed by a single data write operation during log replay |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_CPU_STATISTICS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_CPU_STATISTICS.md
new file mode 100644
index 0000000000000000000000000000000000000000..953ea30ce0de4926a77bf96203202b9d0eaaec71
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_CPU_STATISTICS.md
@@ -0,0 +1,25 @@
+---
+title: GS_SESSION_CPU_STATISTICS
+summary: GS_SESSION_CPU_STATISTICS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_SESSION_CPU_STATISTICS
+
+**GS_SESSION_CPU_STATISTICS** shows load management information about CPU usage of ongoing complex jobs executed by the current user.
+
+**Table 1** GS_SESSION_CPU_STATISTICS columns
+
+| Name           | Type                     | Description                                                  |
+| :------------- | :----------------------- | :----------------------------------------------------------- |
+| datid          | oid                      | OID of the database that the backend is connected to         |
+| usename        | name                     | Name of the user logged in to the backend                    |
+| pid            | bigint                   | Thread ID of the backend                                     |
+| start_time     | timestamp with time zone | Time when the statement starts to be executed                |
+| min_cpu_time   | bigint                   | Minimum CPU time of the statement across the database nodes, in ms |
+| max_cpu_time   | bigint                   | Maximum CPU time of the statement across the database nodes, in ms |
+| total_cpu_time | bigint                   | Total CPU time of the statement across the database nodes, in ms |
+| query          | text                     | Statement being executed                                     |
+| node_group     | text                     | Unsupported currently                                        |
+| top_cpu_dn     | text                     | CPU usage                                                    |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY.md
new file mode 100644
index 0000000000000000000000000000000000000000..c2abd9c426b13e3a825fcd7c1cf868d09a88e624
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY.md
@@ -0,0 +1,19 @@
+---
+title: GS_SESSION_MEMORY
+summary: GS_SESSION_MEMORY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_SESSION_MEMORY
+
+**GS_SESSION_MEMORY** collects statistics about memory usage at the session level, including all the memory allocated to Postgres and Stream threads on DNs for jobs currently executed by users. This view is unavailable when **enable_memory_limit** is set to **off**.
+
+**Table 1** GS_SESSION_MEMORY columns
+
+| Name     | Type    | Description                                                  |
+| :------- | :------ | :----------------------------------------------------------- |
+| sessid   | text    | Thread start time and ID                                     |
+| init_mem | integer | Memory allocated to the currently executed jobs before they enter the executor, in MB |
+| used_mem | integer | Memory allocated to the currently executed jobs, in MB       |
+| peak_mem | integer | Peak memory allocated to the currently executed jobs, in MB  |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY_CONTEXT.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY_CONTEXT.md
new file mode 100644
index 0000000000000000000000000000000000000000..b119506535feba6ead82882e3619674e5a295500
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY_CONTEXT.md
@@ -0,0 +1,25 @@
+---
+title: GS_SESSION_MEMORY_CONTEXT
+summary: GS_SESSION_MEMORY_CONTEXT
+author: Guo Huan
+date: 2021-06-15
+---
+
+# GS_SESSION_MEMORY_CONTEXT
+
+**GS_SESSION_MEMORY_CONTEXT** displays statistics on memory usage of all sessions based on the MemoryContext node. This view is valid only when **enable_thread_pool** is set to **on**. This view is unavailable when **enable_memory_limit** is set to **off**.
+
+The memory context **TempSmallContextGroup** collects information about all memory contexts whose value in the **totalsize** column is less than 8192 bytes in the current thread, and the number of the collected memory contexts is recorded in the **usedsize** column. Therefore, the **totalsize** and **freesize** columns for **TempSmallContextGroup** in the view display the corresponding information about all the memory contexts whose value in the **totalsize** column is less than 8192 bytes in the current thread, and the **usedsize** column displays the number of these memory contexts.
+
+**Table 1** GS_SESSION_MEMORY_CONTEXT columns
+
+| Name        | Type     | Description                                                  |
+| :---------- | :------- | :----------------------------------------------------------- |
+| sessid      | text     | Session start time + session ID (character string: *timestamp.sessionid*) |
+| threadid    | bigint   | ID of the thread bound to a session (**-1** if no thread is bound) |
+| contextname | text     | Name of the memory context                                   |
+| level       | smallint | Hierarchy of the memory context                              |
+| parent      | text     | Name of the parent memory context                            |
+| totalsize   | bigint   | Total size of the memory context, in bytes                   |
+| freesize    | bigint   | Total size of released memory in the memory context, in bytes |
+| usedsize    | bigint   | Size of used memory in the memory context, in bytes. For **TempSmallContextGroup**, this parameter specifies the number of collected memory contexts. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY_DETAIL.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY_DETAIL.md
new file mode 100644
index 0000000000000000000000000000000000000000..366ab6168dcdf49a1b5f4f3f69917344f0cbe74a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY_DETAIL.md
@@ -0,0 +1,27 @@
+---
+title: GS_SESSION_MEMORY_DETAIL
+summary: GS_SESSION_MEMORY_DETAIL
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_SESSION_MEMORY_DETAIL
+
+**GS_SESSION_MEMORY_DETAIL** collects statistics about thread memory usage by MemoryContext node. When **enable_thread_pool** is set to **on**, this view contains memory usage of all threads and sessions. This view is unavailable when **enable_memory_limit** is set to **off**.
+
+The memory context **TempSmallContextGroup** collects information about all memory contexts whose value in the **totalsize** column is less than 8192 bytes in the current thread, and the number of the collected memory contexts is recorded in the **usedsize** column. Therefore, the **totalsize** and **freesize** columns for **TempSmallContextGroup** in the view display the corresponding information about all the memory contexts whose value in the **totalsize** column is less than 8192 bytes in the current thread, and the **usedsize** column displays the number of these memory contexts.
+
+You can run the **"select \* from gs_session_memctx_detail(threadid,");** statement to record information about all memory contexts of a thread into the **threadid*_*timestamp.log** file in the **/tmp/dumpmem** directory. **threadid** can be obtained from the following table.
+
+**Table 1** GS_SESSION_MEMORY_DETAIL columns
+
+| Name        | Type     | Description                                                  |
+| :---------- | :------- | :----------------------------------------------------------- |
+| sessid      | text     | Thread start time + thread ID (string:**timestamp*.*threadid**) |
+| sesstype    | text     | Thread name                                                  |
+| contextname | text     | Name of the memory context                                   |
+| level       | smallint | Hierarchy of the memory context                              |
+| parent      | text     | Name of the parent memory context                            |
+| totalsize   | bigint   | Total size of the memory context, in bytes                   |
+| freesize    | bigint   | Total size of released memory in the current memory context, in bytes |
+| usedsize    | bigint   | Size of used memory in the memory context, in bytes. For **TempSmallContextGroup**, this parameter specifies the number of collected memory contexts. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY_STATISTICS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY_STATISTICS.md
new file mode 100644
index 0000000000000000000000000000000000000000..7118e73a89dd6247bf8844a852466fe8be53df52
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY_STATISTICS.md
@@ -0,0 +1,25 @@
+---
+title: GS_SESSION_MEMORY_STATISTICS
+summary: GS_SESSION_MEMORY_STATISTICS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_SESSION_MEMORY_STATISTICS
+
+**GS_SESSION_MEMORY_STATISTICS** displays load management information about memory usage of ongoing complex jobs executed by the current user.
+
+**Table 1** GS_SESSION_MEMORY_STATISTICS columns
+
+| Name            | Type                     | Description                                                  |
+| :-------------- | :----------------------- | :----------------------------------------------------------- |
+| datid           | oid                      | OID of the database that the backend is connected to         |
+| usename         | name                     | Name of the user logged in to the backend                    |
+| pid             | bigint                   | Thread ID of the backend                                     |
+| start_time      | timestamp with time zone | Time when the statement starts to be executed                |
+| min_peak_memory | integer                  | Minimum memory peak of the statement across the database nodes, in MB |
+| max_peak_memory | integer                  | Maximum memory peak of the statement across the database nodes, in MB |
+| spill_info      | text                     | Information about statement spill to the database nodes<br/>**None**: The statement has not been spilled to disks on the database nodes.<br/>**All**: The statement has been spilled to disks on the database nodes.<br/>**[a:b]**: The statement has been spilled to disks on *a* of *b* database nodes. |
+| query           | text                     | Statement being executed                                     |
+| node_group      | text                     | Unsupported currently                                        |
+| top_mem_dn      | text                     | Memory usage                                                 |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_STAT.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_STAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..f8ccbbda642bfe4104154aa6e267cf72f97fecce
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_STAT.md
@@ -0,0 +1,20 @@
+---
+title: GS_SESSION_STAT
+summary: GS_SESSION_STAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_SESSION_STAT
+
+**GS_SESSION_STAT** collects statistics about session states based on session threads or the **AutoVacuum** thread.
+
+**Table 1** GS_SESSION_STAT columns
+
+| Name     | Type    | Description                     |
+| :------- | :------ | :------------------------------ |
+| sessid   | text    | Thread ID and start time        |
+| statid   | integer | Statistics ID                   |
+| statname | text    | Name of the statistics session  |
+| statunit | text    | Unit of the statistics session  |
+| value    | bigint  | Value of the statistics session |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_TIME.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_TIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..18a670493a38846704404dabe979fb4a3941cbc7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_TIME.md
@@ -0,0 +1,19 @@
+---
+title: GS_SESSION_TIME
+summary: GS_SESSION_TIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_SESSION_TIME
+
+**GS_SESSION_TIME** collects statistics about the running time of session threads and time consumed in each execution phase.
+
+**Table 1** GS_SESSION_TIME columns
+
+| Name      | Type    | Description              |
+| :-------- | :------ | :----------------------- |
+| sessid    | text    | Thread ID and start time |
+| stat_id   | integer | Statistics ID            |
+| stat_name | text    | Session type             |
+| value     | bigint  | Session value            |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SQL_COUNT.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SQL_COUNT.md
new file mode 100644
index 0000000000000000000000000000000000000000..6d99b2a4a6fc31c690583c235895ef34479fdaf7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SQL_COUNT.md
@@ -0,0 +1,45 @@
+---
+title: GS_SQL_COUNT
+summary: GS_SQL_COUNT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_SQL_COUNT
+
+**GS_SQL_COUNT** displays statistics about five types of running statements (**SELECT**, **INSERT**, **UPDATE**, **DELETE**, and **MERGE INTO**) on the current node of the database.
+
+- When a common user queries the **GS_SQL_COUNT** view, statistics about the current node of the user are displayed. When an administrator queries the **GS_SQL_COUNT** view, statistics about the current node of all users are displayed.
+- When MogDB or the node is restarted, the statistics are cleared and will be measured again.
+- The system counts when a node receives a query, including a query inside MogDB.
+
+**Table 1** GS_SQL_COUNT columns
+
+| Name                | Type   | Description                                               |
+| :------------------ | :----- | :-------------------------------------------------------- |
+| node_name           | text   | Node name                                                 |
+| user_name           | text   | Username                                                  |
+| select_count        | bigint | Statistical result of the **SELECT** statement            |
+| update_count        | bigint | Statistical result of the **UPDATE** statement            |
+| insert_count        | bigint | Statistical result of the **INSERT** statement            |
+| delete_count        | bigint | Statistical result of the **DELETE** statement            |
+| mergeinto_count     | bigint | Statistical result of the **MERGE INTO** statement        |
+| ddl_count           | bigint | Number of DDL statements                                  |
+| dml_count           | bigint | Number of DML statements                                  |
+| dcl_count           | bigint | Number of DML statements                                  |
+| total_select_elapse | bigint | Total response time of **SELECT** statements (unit: μs)   |
+| avg_select_elapse   | bigint | Average response time of **SELECT** statements (unit: μs) |
+| max_select_elapse   | bigint | Maximum response time of **SELECT** statements (unit: μs) |
+| min_select_elapse   | bigint | Minimum response time of **SELECT** statements (unit: μs) |
+| total_update_elapse | bigint | Total response time of **UPDATE** statements (unit: μs)   |
+| avg_update_elapse   | bigint | Average response time of **UPDATE** statements (unit: μs) |
+| max_update_elapse   | bigint | Maximum response time of **UPDATE** statements (unit: μs) |
+| min_update_elapse   | bigint | Minimum response time of **UPDATE** statements (unit: μs) |
+| total_insert_elapse | bigint | Total response time of **INSERT** statements (unit: μs)   |
+| avg_insert_elapse   | bigint | Average response time of **INSERT** statements (unit: μs) |
+| max_insert_elapse   | bigint | Maximum response time of **INSERT** statements (unit: μs) |
+| min_insert_elapse   | bigint | Minimum response time of **INSERT** statements (unit: μs) |
+| total_delete_elapse | bigint | Total response time of **DELETE** statements (unit: μs)   |
+| avg_delete_elapse   | bigint | Average response time of **DELETE** statements (unit: μs) |
+| max_delete_elapse   | bigint | Maximum response time of **DELETE** statements (unit: μs) |
+| min_delete_elapse   | bigint | Minimum response time of **DELETE** statements (unit: μs) |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_STAT_SESSION_CU.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_STAT_SESSION_CU.md
new file mode 100644
index 0000000000000000000000000000000000000000..d9346176fa5d555fae43467e490e1bf2aeadbd1a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_STAT_SESSION_CU.md
@@ -0,0 +1,18 @@
+---
+title: GS_STAT_SESSION_CU
+summary: GS_STAT_SESSION_CU
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_STAT_SESSION_CU
+
+**GS_STAT_SESSION_CU** queries the CU hit rate of running sessions on each MogDB node. This data about a session is cleared when you exit this session or restart MogDB.
+
+**Table 1** GS_STAT_SESSION_CU columns
+
+| Name          | Type    | Description                            |
+| :------------ | :------ | :------------------------------------- |
+| mem_hit       | integer | Number of memory hits                  |
+| hdd_sync_read | integer | Number of synchronous hard disk reads  |
+| hdd_asyn_read | integer | Number of asynchronous hard disk reads |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_THREAD_MEMORY_CONTEXT.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_THREAD_MEMORY_CONTEXT.md
new file mode 100644
index 0000000000000000000000000000000000000000..07e7b6d3d35cb144d1ae012755a686c7ef578edf
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_THREAD_MEMORY_CONTEXT.md
@@ -0,0 +1,26 @@
+---
+title: GS_THREAD_MEMORY_CONTEXT
+summary: GS_THREAD_MEMORY_CONTEXT
+author: Guo Huan
+date: 2021-06-15
+---
+
+# GS_THREAD_MEMORY_CONTEXT
+
+**GS_THREAD_MEMORY_CONTEXT** displays statistics about memory usage of all threads based on MemoryContext nodes. This view is equivalent to the **GS_SESSION_MEMORY_CONTEXT** view when **enable_thread_pool** is set to **off**. If the GUC parameter **enable_memory_limit** is set to **off**, this view is unavailable.
+
+The memory context **TempSmallContextGroup** collects information about all memory contexts whose value in the **totalsize** column is less than 8192 bytes in the current thread, and the number of the collected memory contexts is recorded in the **usedsize** column. Therefore, the **totalsize** and **freesize** columns for **TempSmallContextGroup** in the view display the corresponding information about all the memory contexts whose value in the **totalsize** column is less than 8192 bytes in the current thread, and the **usedsize** column displays the number of these memory contexts.
+
+**Table 1** GS_THREAD_MEMORY_CONTEXT columns
+
+| Name        | Type     | Description                                                  |
+| :---------- | :------- | :----------------------------------------------------------- |
+| threadid    | text     | Thread start time + thread ID (string: **timestamp.tsessionid**) |
+| tid         | bigint   | Thread ID                                                    |
+| thrdtype    | text     | Thread type                                                  |
+| contextname | text     | Name of the memory context                                   |
+| level       | smallint | Hierarchy of the memory context                              |
+| parent      | text     | Name of the parent memory context                            |
+| totalsize   | bigint   | Total size of the memory context, in bytes                   |
+| freesize    | bigint   | Total size of released memory in the current memory context, in bytes |
+| usedsize    | bigint   | Size of used memory in the memory context, in bytes. For **TempSmallContextGroup**, this parameter specifies the number of collected memory contexts. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_TOTAL_MEMORY_DETAIL.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_TOTAL_MEMORY_DETAIL.md
new file mode 100644
index 0000000000000000000000000000000000000000..31c84c9df7f01e4e235c8e59a2723a9247e9ad4a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_TOTAL_MEMORY_DETAIL.md
@@ -0,0 +1,18 @@
+---
+title: GS_TOTAL_MEMORY_DETAIL
+summary: GS_TOTAL_MEMORY_DETAIL
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_TOTAL_MEMORY_DETAIL
+
+**GS_TOTAL_MEMORY_DETAIL** collects statistics about memory usage of the current database node. This view is unavailable when **enable_memory_limit** is set to **off**.
+
+**Table 1** GS_TOTAL_MEMORY_DETAIL columns
+
+| Name         | Type    | Description                                                  |
+| :----------- | :------ | :----------------------------------------------------------- |
+| nodename     | text    | Node name                                                    |
+| memorytype   | text    | Memory type. The value must be one of the following:<br/>- **max_process_memory**: memory occupied by a MogDB instance<br/>- **process_used_memory**: memory occupied by a MogDB process<br/>- **max_dynamic_memory**: maximum dynamic memory<br/>- **dynamic_used_memory**: used dynamic memory<br/>- **dynamic_peak_memory**: dynamic peak value of the memory<br/>- **dynamic_used_shrctx**: maximum dynamic shared memory context<br/>- **dynamic_peak_shrctx**: dynamic peak value of the shared memory context<br/>- **max_shared_memory**: maximum shared memory<br/>- **shared_used_memory**: used shared memory<br/>- **max_cstore_memory**: maximum memory allowed by the column<br/>- **cstore_used_memory**: memory used in column storage<br/>- **max_sctpcomm_memory**: maximum memory allowed for the communication library<br/>- **sctpcomm_used_memory**: memory used by the communication library<br/>- **sctpcomm_peak_memory**: memory peak of the communication library<br/>- **other_used_memory**: other used memory |
+| memorymbytes | integer | Size of allocated memory-typed memory                        |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_CGROUP_INFO.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_CGROUP_INFO.md
new file mode 100644
index 0000000000000000000000000000000000000000..3aba35f8f4700b0f9616685aba9078ba3cb95149
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_CGROUP_INFO.md
@@ -0,0 +1,24 @@
+---
+title: GS_WLM_CGROUP_INFO
+summary: GS_WLM_CGROUP_INFO
+author: Guo Huan
+date: 2021-06-15
+---
+
+# GS_WLM_CGROUP_INFO
+
+**GS_WLM_CGROUP_INFO** displays information about a Cgroup for a job that is being executed.
+
+**Table 1** GS_WLM_CGROUP_INFO columns
+
+| Name         | Type     | Description                                |
+| :----------- | :------- | :----------------------------------------- |
+| cgoup_name   | text     | Cgroup name                                |
+| priority     | interger | Priority of the job                        |
+| usage_pecent | interger | Percentage of resources used by the Cgroup |
+| shares       | bigint   | CPU quota allocated to the Cgroup          |
+| cpuacct      | bigint   | Allocated CPU quota                        |
+| cpuset       | text     | Allocated CPU cores                        |
+| relpath      | text     | Relative path of the Cgroup                |
+| valid        | text     | Whether the Cgroup is valid                |
+| node_group   | text     | Name of the logical cluster                |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_PLAN_OPERATOR_HISTORY.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_PLAN_OPERATOR_HISTORY.md
new file mode 100644
index 0000000000000000000000000000000000000000..9f7ecc114b3fc5e54248472cf4677f11a492c2e1
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_PLAN_OPERATOR_HISTORY.md
@@ -0,0 +1,35 @@
+---
+title: GS_WLM_PLAN_OPERATOR_HISTORY
+summary: GS_WLM_PLAN_OPERATOR_HISTORY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_WLM_PLAN_OPERATOR_HISTORY
+
+**GS_WLM_PLAN_OPERATOR_HISTORY** displays the execution plan operator-level records of the current user on the primary database node after the job is complete.
+
+| Name                | Type                     | Description                                                  |
+| :------------------ | :----------------------- | :----------------------------------------------------------- |
+| queryid             | bigint                   | Internal query ID used for statement execution               |
+| pid                 | bigint                   | Thread ID of the backend                                     |
+| plan_node_id        | integer                  | Plan node ID of the execution plan of a query                |
+| plan_node_name      | text                     | Name of the operator corresponding to the plan node ID       |
+| start_time          | timestamp with time zone | Time when the operator starts to process the first data record |
+| duration            | bigint                   | Total execution time of the operator, in ms                  |
+| query_dop           | integer                  | DOP of the operator                                          |
+| estimated_rows      | bigint                   | Number of rows estimated by the optimizer                    |
+| tuple_processed     | bigint                   | Number of elements returned by the operator                  |
+| min_peak_memory     | integer                  | Minimum peak memory used by the operator on database nodes (unit: MB) |
+| max_peak_memory     | integer                  | Maximum peak memory used by the operator on database nodes (unit: MB) |
+| average_peak_memory | integer                  | Average peak memory used by the operator on database nodes (unit: MB) |
+| memory_skew_percent | integer                  | Memory usage skew of the operator among database nodes       |
+| min_spill_size      | integer                  | Minimum spilled data among database nodes when a spill occurs (unit: MB) (default value: **0**) |
+| max_spill_size      | integer                  | Maximum spilled data among database nodes when a spill occurs (unit: MB) (default value: **0**) |
+| average_spill_size  | integer                  | Average spilled data among database nodes when a spill occurs (unit: MB) (default value: **0**) |
+| spill_skew_percent  | integer                  | Database node spill skew when a spill occurs                 |
+| min_cpu_time        | bigint                   | Minimum execution time of the operator on database nodes (unit: ms) |
+| max_cpu_time        | bigint                   | Maximum execution time of the operator on database nodes (unit: ms) |
+| total_cpu_time      | bigint                   | Total execution time of the operator on database nodes (unit: ms) |
+| cpu_skew_percent    | integer                  | Execution time skew among database nodes                     |
+| warning             | text                     | Warning. The following warnings are displayed:<br />- Sort/SetOp/HashAgg/HashJoin spill<br />- Spill file size large than 256MB<br />- Broadcast size large than 100MB<br />- Early spillSpill times is greater than 3<br />- Spill on memory adaptive<br />- Hash table conflict |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_REBUILD_USER_RESOURCE_POOL.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_REBUILD_USER_RESOURCE_POOL.md
new file mode 100644
index 0000000000000000000000000000000000000000..1973251119d63a6a0c78fced82e8980d52f77e19
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_REBUILD_USER_RESOURCE_POOL.md
@@ -0,0 +1,16 @@
+---
+title: GS_WLM_REBUILD_USER_RESOURCE_POOL
+summary: GS_WLM_REBUILD_USER_RESOURCE_POOL
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_WLM_REBUILD_USER_RESOURCE_POOL
+
+**GS_WLM_REBUILD_USER_RESOURCE_POOL** is used to rebuild a user's resource pool information in memory on the current connection node, with no output. This view is only used as a remedy when resource pool information is missing or misplaced. Only the user with sysadmin permission can query this view.
+
+**Table 1** **GS_WLM_REBUILD_USER_RESOURCE_POOL** columns
+
+| Name                              | Type    | Description                                                  |
+| :-------------------------------- | :------ | :----------------------------------------------------------- |
+| gs_wlm_rebuild_user_resource_pool | Boolean | Rebuilds information about the user resource pool in the memory. **t** indicates success, and **f** indicates failure. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_RESOURCE_POOL.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_RESOURCE_POOL.md
new file mode 100644
index 0000000000000000000000000000000000000000..0b7b31a81878c57067f0edef54f8cab90a847719
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_RESOURCE_POOL.md
@@ -0,0 +1,25 @@
+---
+title: GS_WLM_RESOURCE_POOL
+summary: GS_WLM_RESOURCE_POOL
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_WLM_RESOURCE_POOL
+
+**GS_WLM_RESOURCE_POOL** records statistics on a resource pool.
+
+**Table 1** GS_WLM_RESOURCE_POOL columns
+
+| Name          | Type    | Description                                      |
+| :------------ | :------ | :----------------------------------------------- |
+| rpoid         | oid     | OID of the resource pool                         |
+| respool       | name    | Name of the resource pool                        |
+| control_group | name    | Unsupported currently                            |
+| parentid      | oid     | OID of the parent resource pool                  |
+| ref_count     | integer | Number of jobs associated with the resource pool |
+| active_points | integer | Number of used points in the resource pool       |
+| running_count | integer | Number of jobs running in the resource pool      |
+| waiting_count | integer | Number of jobs queuing in the resource pool      |
+| io_limits     | integer | IOPS upper limit of the resource pool            |
+| io_priority   | integer | I/O priority of the resource pool                |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_USER_INFO.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_USER_INFO.md
new file mode 100644
index 0000000000000000000000000000000000000000..78c8f52adafe2ef03e2220d2a38653e192ee18b6
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_USER_INFO.md
@@ -0,0 +1,25 @@
+---
+title: GS_WLM_USER_INFO
+summary: GS_WLM_USER_INFO
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_WLM_USER_INFO
+
+**GS_WLM_USER_INFO** displays user statistics.
+
+**Table 1** GS_WLM_USER_INFO columns
+
+| Name       | Type     | Description                           |
+| :--------- | :------- | :------------------------------------ |
+| userid     | oid      | OID of a user                         |
+| username   | name     | Username                              |
+| sysadmin   | boolean  | Whether the user is the administrator |
+| rpoid      | oid      | OID of the associated resource pool   |
+| respool    | name     | Name of the associated resource pool  |
+| parentid   | oid      | OID of the user group                 |
+| totalspace | bigint   | Available space limit of the user     |
+| spacelimit | bigint   | User table space limit                |
+| childcount | interger | Number of child users                 |
+| childlist  | text     | Child user list                       |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/MPP_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/MPP_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..e0e78a964f21f972da58f4af2bc08a0127063b11
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/MPP_TABLES.md
@@ -0,0 +1,21 @@
+---
+title: MPP_TABLES
+summary: MPP_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# MPP_TABLES
+
+The following information is displayed in the **MPP_TABLES** view.
+
+**Table 1** MPP_TABLES columns
+
+| Name       | Type             | Description                              |
+| :--------- | :--------------- | :--------------------------------------- |
+| schemaname | name             | Name of the schema that contains a table |
+| tablename  | name             | Table name                               |
+| tableowner | name             | Table owner                              |
+| tablespace | name             | Tablespace containing the table          |
+| pgroup     | name             | Name of a node cluster                   |
+| nodeoids   | oidvector_extend | List of distributed table node OIDs      |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_AVAILABLE_EXTENSIONS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_AVAILABLE_EXTENSIONS.md
new file mode 100644
index 0000000000000000000000000000000000000000..ac0f016a8d764aca2a1397eb95e47cf171b4693f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_AVAILABLE_EXTENSIONS.md
@@ -0,0 +1,19 @@
+---
+title: PG_AVAILABLE_EXTENSIONS
+summary: PG_AVAILABLE_EXTENSIONS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_AVAILABLE_EXTENSIONS
+
+**PG_AVAILABLE_EXTENSIONS** displays extended information about certain database features.
+
+**Table 1** PG_AVAILABLE_EXTENSIONS columns
+
+| Name              | Type | Description                                                  |
+| :---------------- | :--- | :----------------------------------------------------------- |
+| name              | name | Extension name                                               |
+| default_version   | text | Name of the default version (**NULL** if none is specified)  |
+| installed_version | text | Currently installed version of the extension (**NULL** if no version is installed) |
+| comment           | text | Comment string from the extension's control file             |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_AVAILABLE_EXTENSION_VERSIONS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_AVAILABLE_EXTENSION_VERSIONS.md
new file mode 100644
index 0000000000000000000000000000000000000000..58e6accbfe467e984f6640d8bb629f2a1159a2ca
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_AVAILABLE_EXTENSION_VERSIONS.md
@@ -0,0 +1,23 @@
+---
+title: PG_AVAILABLE_EXTENSION_VERSIONS
+summary: PG_AVAILABLE_EXTENSION_VERSIONS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_AVAILABLE_EXTENSION_VERSIONS
+
+**PG_AVAILABLE_EXTENSION_VERSIONS** displays extension versions of certain database features.
+
+**Table 1** PG_AVAILABLE_EXTENSION_VERSIONS columns
+
+| Name        | Type    | Description                                                  |
+| :---------- | :------ | :----------------------------------------------------------- |
+| name        | name    | Extension name                                               |
+| version     | text    | Version name                                                 |
+| installed   | Boolean | Whether this extension version is installed                  |
+| superuser   | Boolean | Whether only system administrators are allowed to install the extension |
+| relocatable | Boolean | Whether the extension can be relocated to another schema     |
+| schema      | name    | Name of the schema that the extension must be installed into (**NULL** if the extension is partially or fully relocatable) |
+| requires    | name[]  | Names of prerequisite extensions (**NULL** if none)          |
+| comment     | text    | Comment string from the extension's control file             |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_DELAY.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_DELAY.md
new file mode 100644
index 0000000000000000000000000000000000000000..d4ae6ddf86a8f036af640b6169e157865bbc90db
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_DELAY.md
@@ -0,0 +1,22 @@
+---
+title: PG_COMM_DELAY
+summary: PG_COMM_DELAY
+author: Guo Huan
+date: 2021-06-15
+---
+
+# PG_COMM_DELAY
+
+**PG_COMM_DELAY** displays the communication library delay status for a single node.
+
+**Table 1** PG_COMM_DELAY columns
+
+| Name        | Type    | Description                                                  |
+| :---------- | :------ | :----------------------------------------------------------- |
+| node_name   | text    | Node name                                                    |
+| remote_name | text    | Name of the peer node                                        |
+| remote_host | text    | IP address of the peer node                                  |
+| stream_num  | integer | Number of logical stream connections used by the current physical connection |
+| min_delay   | integer | Minimum delay of the current physical connection within 1 minute, in microsecond<br/>NOTE:<br/>A negative result is invalid. Wait until the delay status is updated and query again. |
+| average     | integer | Average delay of the current physical connection within 1 minute, in microsecond |
+| max_delay   | integer | Maximum delay of the current physical connection within 1 minute, in microsecond |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_RECV_STREAM.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_RECV_STREAM.md
new file mode 100644
index 0000000000000000000000000000000000000000..a1ce6b655bbecb5a505e9671a47e1d7c6522ce16
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_RECV_STREAM.md
@@ -0,0 +1,32 @@
+---
+title: PG_COMM_RECV_STREAM
+summary: PG_COMM_RECV_STREAM
+author: Guo Huan
+date: 2021-06-15
+---
+
+# PG_COMM_RECV_STREAM
+
+**PG_COMM_RECV_STREAM** displays the receiving stream status of all the communication libraries for a single node.
+
+**Table 1** PG_COMM_RECV_STREAM columns
+
+| Name        | Type    | Description                                                  |
+| :---------- | :------ | :----------------------------------------------------------- |
+| node_name   | text    | Node name                                                    |
+| local_tid   | bigint  | ID of the thread using this stream                           |
+| remote_name | text    | Name of the peer node                                        |
+| remote_tid  | bigint  | Peer thread ID                                               |
+| idx         | integer | Peer DN ID in the local DN                                   |
+| sid         | integer | Stream ID in the physical connection                         |
+| tcp_sock    | integer | TCP socket used in the stream                                |
+| state       | text    | Status of the stream<br />- **UNKNOWN**: The logical connection status is unknown.<br />- **READY**: The logical connection is ready.<br />- **RUN**: The logical connection sends packets normally.<br />- **HOLD**: The logical connection is waiting to send packets.<br />- **CLOSED**: The logical connection is closed.<br />- **TO_CLOSED**: The logical connection will be closed. |
+| query_id    | bigint  | **debug_query_id** corresponding to the stream               |
+| pn_id       | integer | **plan_node_id** of the query executed by the stream         |
+| send_smp    | integer | **smpid** of the sender of the query executed by the stream  |
+| recv_smp    | integer | **smpid** of the receiver of the query executed by the stream |
+| recv_bytes  | bigint  | Total data volume received from the stream, in byte          |
+| time        | bigint  | Current lifecycle service duration of the stream, in ms      |
+| speed       | bigint  | Average receiving rate of the stream, in byte/s              |
+| quota       | bigint  | Current communication quota value of the stream, in byte     |
+| buff_usize  | bigint  | Current size of the data cache of the stream, in byte        |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_SEND_STREAM.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_SEND_STREAM.md
new file mode 100644
index 0000000000000000000000000000000000000000..71a1bee3695d9a37429aa7bef5d5bef1c3e9cd5c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_SEND_STREAM.md
@@ -0,0 +1,32 @@
+---
+title: PG_COMM_SEND_STREAM
+summary: PG_COMM_SEND_STREAM
+author: Guo Huan
+date: 2021-06-15
+---
+
+# PG_COMM_SEND_STREAM
+
+**PG_COMM_SEND_STREAM** displays the sending stream status of all the communication libraries for a single node.
+
+**Table 1** PG_COMM_SEND_STREAM columns
+
+| Name        | Type    | Description                                                  |
+| :---------- | :------ | :----------------------------------------------------------- |
+| node_name   | text    | Node name                                                    |
+| local_tid   | bigint  | ID of the thread using this stream                           |
+| remote_name | text    | Name of the peer node                                        |
+| remote_tid  | bigint  | Peer thread ID                                               |
+| idx         | integer | Peer DN ID in the local DN                                   |
+| sid         | integer | Stream ID in the physical connection                         |
+| tcp_sock    | integer | TCP socket used in the stream                                |
+| state       | text    | Status of the stream<br />- **UNKNOWN**: The logical connection status is unknown.<br />- **READY**: The logical connection is ready.<br />- **RUN**: The logical connection sends packets normally.<br />- **HOLD**: The logical connection is waiting to send packets.<br />- **CLOSED**: The logical connection is closed.<br />- **TO_CLOSED**: The logical connection will be closed. |
+| query_id    | bigint  | **debug_query_id** corresponding to the stream               |
+| pn_id       | integer | **plan_node_id** of the query executed by the stream         |
+| send_smp    | integer | **smpid** of the sender of the query executed by the stream  |
+| recv_smp    | integer | **smpid** of the receiver of the query executed by the stream |
+| send_bytes  | bigint  | Total data volume sent by the stream, in byte                |
+| time        | bigint  | Current lifecycle service duration of the stream, in ms      |
+| speed       | bigint  | Average sending rate of the stream, in byte/s                |
+| quota       | bigint  | Current communication quota value of the stream, in byte     |
+| wait_quota  | bigint  | Extra time generated when the stream waits the quota value, in ms |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_STATUS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_STATUS.md
new file mode 100644
index 0000000000000000000000000000000000000000..73bf2a53f4ba91bdbb7fdb103b1f028a43973233
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_STATUS.md
@@ -0,0 +1,28 @@
+---
+title: PG_COMM_STATUS
+summary: PG_COMM_STATUS
+author: Guo Huan
+date: 2021-06-15
+---
+
+# PG_COMM_STATUS
+
+**PG_COMM_STATUS** displays the communication library status for a single node.
+
+**Table 1** PG_COMM_STATUS columns
+
+| Name          | Type    | Description                                                  |
+| :------------ | :------ | :----------------------------------------------------------- |
+| node_name     | text    | Node name                                                    |
+| rxpck_rate    | integer | Receiving rate of the communication library on the node, in byte/s |
+| txpck_rate    | integer | Sending rate of the communication library on the node, in byte/s |
+| rxkB_rate     | bigint  | Receiving rate of the communication library on the node, in kbyte/s |
+| txkB_rate     | bigint  | Sending rate of the communication library on the node, in kbyte/s |
+| buffer        | bigint  | Size of the buffer of the Cmailbox                           |
+| memKB_libcomm | bigint  | Communication memory size of the **libcomm** process, in bytes |
+| memKB_libpq   | bigint  | Communication memory size of the **libpq** process, in bytes |
+| used_PM       | integer | Real-time usage of the **postmaster** thread                 |
+| used_sflow    | integer | Real-time usage of the **gs_sender_flow_controller** thread  |
+| used_rflow    | integer | Real-time usage of the **gs_receiver_flow_controller** thread |
+| used_rloop    | integer | Highest real-time usage among multiple **gs_receivers_loop** threads |
+| stream        | integer | Total number of used logical connections.                    |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_CONTROL_GROUP_CONFIG.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_CONTROL_GROUP_CONFIG.md
new file mode 100644
index 0000000000000000000000000000000000000000..cdd277226ec4f86d90e6ca16a08d15b525e8d1aa
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_CONTROL_GROUP_CONFIG.md
@@ -0,0 +1,16 @@
+---
+title: PG_CONTROL_GROUP_CONFIG
+summary: PG_CONTROL_GROUP_CONFIG
+author: Guo Huan
+date: 2021-06-15
+---
+
+# PG_CONTROL_GROUP_CONFIG
+
+**PG_CONTROL_GROUP_CONFIG** stores Cgroup configuration information in the system. Only the user with sysadmin permission can query this view.
+
+**Table 1** PG_CONTROL_GROUP_CONFIG columns
+
+| Name                    | Type | Description                             |
+| :---------------------- | :--- | :-------------------------------------- |
+| pg_control_group_config | text | Configuration information of the Cgroup |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_CURSORS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_CURSORS.md
new file mode 100644
index 0000000000000000000000000000000000000000..d7bc489e3633f1243399501e9a98c29f2edefa37
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_CURSORS.md
@@ -0,0 +1,21 @@
+---
+title: PG_CURSORS
+summary: PG_CURSORS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_CURSORS
+
+**PG_CURSORS** displays cursors that are currently available.
+
+**Table 1** PG_CURSORS columns
+
+| Name          | Type                     | Description                                                  |
+| :------------ | :----------------------- | :----------------------------------------------------------- |
+| name          | text                     | Cursor name                                                  |
+| statement     | text                     | Query statement when the cursor is declared to change        |
+| is_holdable   | Boolean                  | **True** if the cursor is holdable (it can be accessed after the transaction that declared the cursor has committed); **false** otherwise |
+| is_binary     | Boolean                  | Whether the cursor was declared BINARY. If it was, the value is **true**. |
+| is_scrollable | Boolean                  | Whether the cursor is scrollable (it allows rows to be retrieved in a nonsequential manner). If it is, the value is **true**. |
+| creation_time | timestamp with time zone | Timestamp at which the cursor is declared                    |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_EXT_STATS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_EXT_STATS.md
new file mode 100644
index 0000000000000000000000000000000000000000..bcda9c3cfdd6393bc2a8f6e8378cf7175c94d21e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_EXT_STATS.md
@@ -0,0 +1,28 @@
+---
+title: PG_EXT_STATS
+summary: PG_EXT_STATS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_EXT_STATS
+
+**PG_EXT_STATS** allows for access to extension statistics stored in the PG_STATISTIC_EXT system catalog. The extension statistics means multiple columns of statistics.
+
+**Table 1** PG_EXT_STATS columns
+
+| Name                   | Type       | Reference               | Description                                                  |
+| :--------------------- | :--------- | :---------------------- | :----------------------------------------------------------- |
+| schemaname             | name       | PG_NAMESPACE.nspname    | Name of the schema that contains a table                     |
+| tablename              | name       | PG_CLASS.relname        | Table name                                                   |
+| attname                | int2vector | PG_STATISTIC_EXT.stakey | Columns to be combined for collecting statistics             |
+| inherited              | Boolean    | -                       | Includes inherited sub-columns if the value is **true**; otherwise, it indicates the column in a specified table. |
+| null_frac              | real       | -                       | Percentage of column combinations that are null to all records |
+| avg_width              | integer    | -                       | Average width of column combinations, in byte                |
+| n_distinct             | real       | -                       | - Estimated number of distinct values in a column combination if the value is greater than 0<br/>- Negative of the number of distinct values divided by the number of rows if the value is less than 0<br/>    1. The negated form is used when **ANALYZE** believes that the number of distinct values is likely to increase as the table grows.<br/>    2. The positive form is used when the column seems to have a fixed number of possible values. For example, **-1** indicates that the number of distinct values is the same as the number of rows for a column combination.<br/>- The number of distinct values is unknown if the value is **0**. |
+| n_dndistinct           | real       | -                       | Number of unique not-null data values in the **dn1** column combination<br/>- Exact number of distinct values if the value is greater than **0**.<br/>- Negative of the number of distinct values divided by the number of rows if the value is less than **0**. For example, if a value in a column combination appears twice in average, **n\_dndistinct** equals **-0.5**.<br/>- The number of distinct values is unknown if the value is **0**. |
+| most_common_vals       | anyarray   | -                       | List of the most common values in a column combination. If this combination does not have the most common values, **most_common_vals** will be **NULL**. None of the most common values in **most_common_vals** is **NULL**. |
+| most_common_freqs      | real[]     | -                       | List of the frequencies of the most common values, that is, the number of occurrences of each value divided by the total number of rows (**NULL** if **most_common_vals** is **NULL**) |
+| most_common_vals_null  | anyarray   | -                       | List of the most common values in a column combination. If this combination does not have the most common values, **most\_common\_vals\_null** will be **NULL**. At least one of the common values in **most\_common\_vals\_null** is **NULL**. |
+| most_common_freqs_null | real[]     | -                       | List of the frequencies of the most common values, that is, the number of occurrences of each value divided by the total number of rows (**NULL** if **most\_common\_vals\_null** is **NULL**) |
+| histogram_bounds       | anyarray   | -                       | Boundary value list of the histogram                         |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GET_INVALID_BACKENDS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GET_INVALID_BACKENDS.md
new file mode 100644
index 0000000000000000000000000000000000000000..22d51dc8210148b555630e4e8b50b8e48c93abfb
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GET_INVALID_BACKENDS.md
@@ -0,0 +1,20 @@
+---
+title: PG_GET_INVALID_BACKENDS
+summary: PG_GET_INVALID_BACKENDS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_GET_INVALID_BACKENDS
+
+**PG_GET_INVALID_BACKENDS** provides information about background threads on the primary database node that are connected to the current standby server.
+
+**Table 1** PG_GET_INVALID_BACKENDS columns
+
+| Name          | Type                     | Description                                         |
+| :------------ | :----------------------- | :-------------------------------------------------- |
+| pid           | bigint                   | Thread ID                                           |
+| node_name     | text                     | Node information connected to the background thread |
+| dbname        | name                     | Name of the connected database                      |
+| backend_start | timestamp with time zone | Background thread startup time                      |
+| query         | text                     | Query statement executed by the background thread   |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GET_SENDERS_CATCHUP_TIME.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GET_SENDERS_CATCHUP_TIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..28f17bf3f02345fcf875dce59136578f7b576f2d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GET_SENDERS_CATCHUP_TIME.md
@@ -0,0 +1,23 @@
+---
+title: PG_GET_SENDERS_CATCHUP_TIME
+summary: PG_GET_SENDERS_CATCHUP_TIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_GET_SENDERS_CATCHUP_TIME
+
+**PG_GET_SENDERS_CATCHUP_TIME** provides catchup information of the currently active primary/standby instance sender thread on the database node.
+
+**Table 1** PG_GET_SENDERS_CATCHUP_TIME columns
+
+| Name          | Type                     | Description                         |
+| :------------ | :----------------------- | :---------------------------------- |
+| pid           | bigint                   | Current sender thread ID            |
+| lwpid         | integer                  | Current sender lwpid                |
+| local_role    | text                     | Local role                          |
+| peer_role     | text                     | Peer role                           |
+| state         | text                     | Current sender's replication status |
+| type          | text                     | Current sender type                 |
+| catchup_start | timestamp with time zone | Startup time of a catchup task      |
+| catchup_end   | timestamp with time zone | End time of a catchup task          |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GROUP.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GROUP.md
new file mode 100644
index 0000000000000000000000000000000000000000..ad622559db6b1761e7c5285aab1f521edff6acd0
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GROUP.md
@@ -0,0 +1,18 @@
+---
+title: PG_GROUP
+summary: PG_GROUP
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_GROUP
+
+**PG_GROUP** displays the database role authentication and the relationship between roles.
+
+**Table 1** PG_GROUP columns
+
+| Name     | Type  | Description                                        |
+| :------- | :---- | :------------------------------------------------- |
+| groname  | name  | Group name                                         |
+| grosysid | oid   | Group ID                                           |
+| grolist  | oid[] | An array, including all the role IDs in this group |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GTT_ATTACHED_PIDS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GTT_ATTACHED_PIDS.md
new file mode 100644
index 0000000000000000000000000000000000000000..5e821412375994adedab54c18364e7560ecb7599
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GTT_ATTACHED_PIDS.md
@@ -0,0 +1,19 @@
+---
+title: PG_GTT_ATTACHED_PIDS
+summary: PG_GTT_ATTACHED_PIDS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_GTT_ATTACHED_PIDS
+
+**PG_GTT_ATTACHED_PIDS** checks which sessions are using global temporary tables by calling the **pg_get_attached_pid** function.
+
+**Table 1** PG_GTT_ATTACHED_PIDS columns
+
+| Name       | Type     | Description                       |
+| :--------- | :------- | :-------------------------------- |
+| schemaname | name     | Schema name.                      |
+| tablename  | name     | Name of a global temporary table. |
+| relid      | oid      | OID of a global temporary table.  |
+| pids       | bigint[] | Thread PID list.                  |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GTT_RELSTATS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GTT_RELSTATS.md
new file mode 100644
index 0000000000000000000000000000000000000000..3927f5449dbad4cf25413cb5616478a54fd9c39a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GTT_RELSTATS.md
@@ -0,0 +1,23 @@
+---
+title: PG_GTT_RELSTATS
+summary: PG_GTT_RELSTATS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_GTT_RELSTATS
+
+**PG_GTT_RELSTATS** displays basic information about all global temporary tables of the current session by calling **pg_get_gtt_relstats**.
+
+**Table 1** PG_GTT_RELSTATS columns
+
+| Name          | Type    | Description                                                  |
+| :------------ | :------ | :----------------------------------------------------------- |
+| schemaname    | name    | Schema name.                                                 |
+| tablename     | name    | Name of a global temporary table.                            |
+| relfilenode   | oid     | File object ID.                                              |
+| relpages      | integer | Number of disk pages of a global temporary table.            |
+| reltuples     | real    | Number of records in a global temporary table.               |
+| relallvisible | integer | Number of pages that are marked as all visible.              |
+| relfrozenxid  | xid     | All transaction IDs before this one have been replaced with a permanent ("frozen") transaction ID in the table. |
+| relminmxid    | xid     | This interface is reserved.                                  |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GTT_STATS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GTT_STATS.md
new file mode 100644
index 0000000000000000000000000000000000000000..0936bc43ca15a3b2d7f6796b16efd302faf8fdff
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GTT_STATS.md
@@ -0,0 +1,29 @@
+---
+title: PG_GTT_STATS
+summary: PG_GTT_STATS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_GTT_STATS
+
+**PG_GTT_STATS** displays statistics about a single column in all global temporary tables of the current session by calling **pg_get_gtt_relstats**.
+
+**Table 1** PG_GTT_STATS columns
+
+| Name                   | Type    | Description                                                  |
+| :--------------------- | :------ | :----------------------------------------------------------- |
+| schemaname             | name    | Schema name.                                                 |
+| tablename              | name    | Name of a global temporary table.                            |
+| attname                | name    | Attribute name.                                              |
+| inherited              | boolean | Specifies whether to collect statistics for objects that have inheritance relationship. |
+| null_frac              | real    | Percentage of column entries that are null.                  |
+| avg_width              | integer | Average stored width, in bytes, of non-null entries.         |
+| n_distinct             | real    | Number of distinct, non-null data values in the column.      |
+| most_common_vals       | text[]  | List of the most common values, which is sorted by occurrence frequency. |
+| most_common_freqs      | real[]  | Frequencies of the most common values.                       |
+| histogram_bounds       | text[]  | Data distribution (excluding the most common values) in a frequency histogram description column. |
+| correlation            | real    | Correlation coefficient.                                     |
+| most_common_elems      | text[]  | List of the most common element values, which is used for the array type or some other type. |
+| most_common_elem_freqs | real[]  | Frequencies of the most common element values.               |
+| elem_count_histogram   | real[]  | Array type histogram.                                        |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_INDEXES.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..d123c0da9a4c7f8a6f50e0b49227aed8c7c59476
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_INDEXES.md
@@ -0,0 +1,20 @@
+---
+title: PG_INDEXES
+summary: PG_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_INDEXES
+
+**PG_INDEXES** provides access to useful information about each index in the database.
+
+**Table 1** PG_INDEXES columns
+
+| Name       | Type | Reference             | Description                                                 |
+| :--------- | :--- | :-------------------- | :---------------------------------------------------------- |
+| schemaname | name | PG_NAMESPACE.nspname  | Name of the schema that contains tables and indexes         |
+| tablename  | name | PG_CLASS.relname      | Name of the table for which the index serves                |
+| indexname  | name | PG_CLASS.relname      | Index name                                                  |
+| tablespace | name | PG_TABLESPACE.nspname | Name of the tablespace that contains the index              |
+| indexdef   | text | -                     | Index definition (a reconstructed **CREATE INDEX** command) |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_LOCKS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_LOCKS.md
new file mode 100644
index 0000000000000000000000000000000000000000..3510a80f1107c07586115689ba240bc8e9e9cac3
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_LOCKS.md
@@ -0,0 +1,34 @@
+---
+title: PG_LOCKS
+summary: PG_LOCKS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_LOCKS
+
+**PG_LOCKS** displays information about locks held by open transactions.
+
+**Table 1** PG_LOCKS columns
+
+| Name               | Type     | Reference       | Description                                                  |
+| :----------------- | :------- | :-------------- | :----------------------------------------------------------- |
+| locktype           | text     | -               | Type of the locked object:**relation**, **extend**, **page**, **tuple**, **transactionid**, **virtualxid**, **object**, **userlock**, or **advisory** |
+| database           | oid      | PG_DATABASE.oid | OID of the database in which the locked object exists.<br/>- The OID is **0** if the object is a shared object.<br/>- The OID is **NULL** if the object is a transaction ID. |
+| relation           | oid      | PG_CLASS.oid    | OID of the relationship targeted by the lock. The value is **NULL** if the object is not a relationship or part of a relationship. |
+| page               | integer  | -               | Page number targeted by the lock within the relation (**NULL** if the object is not a relation page or row page) |
+| tuple              | smallint | -               | Row number targeted by the lock within the page (**NULL** if the object is not a row) |
+| bucket             | integer  | -               | Bucket number corresponding to the child table. The value is **NULL** if the target is not a table. |
+| virtualxid         | text     | -               | Virtual ID of the transaction targeted by the lock. The value is **NULL** if the object is not a virtual transaction ID. |
+| transactionid      | xid      | -               | ID of the transaction targeted by the lock. The value is **NULL** if the object is not a transaction ID. |
+| classid            | oid      | PG_CLASS.oid    | OID of the system catalog that contains the object (**NULL** if the object is not a general database object) |
+| objid              | oid      | -               | OID of the lock target within its system table (**NULL** if the target is not a general database object) |
+| objsubid           | smallint | -               | Column number for a column in the table. The value is **0** if the object is some other object type. The value is **NULL** if the object is not a general database object. |
+| virtualtransaction | text     | -               | Virtual ID of the transaction holding or awaiting this lock  |
+| pid                | bigint   | -               | Logical ID of the server thread holding or awaiting this lock (**NULL** if the lock is held by a prepared transaction) |
+| sessionid          | bigint   | -               | ID of the session holding or awaiting this lock              |
+| mode               | text     | -               | Lock mode held or desired by this thread                     |
+| granted            | Boolean  | -               | - The value is **TRUE** if the lock is a held lock.<br/>- The value is **FALSE** if the lock is an awaited lock. |
+| fastpath           | Boolean  | -               | The value is **TRUE** if the lock is obtained through **fast-path**, and is **FALSE** if the lock is obtained through the main lock table. |
+| locktag            | text     | -               | Lock information that the session waits for. It can be parsed using the **locktag_decode()** function. |
+| global_sessionid   | text     |                 | Global session ID                                            |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_NODE_ENV.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_NODE_ENV.md
new file mode 100644
index 0000000000000000000000000000000000000000..808c9eda8d85943e367b2ef96a31c9dc5371f56c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_NODE_ENV.md
@@ -0,0 +1,22 @@
+---
+title: PG_NODE_ENV
+summary: PG_NODE_ENV
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_NODE_ENV
+
+**PG_NODE_ENV** obtains environmental variable information about the current node.
+
+**Table 1** PG_NODE_ENV columns
+
+| Name          | Type    | Description                        |
+| :------------ | :------ | :--------------------------------- |
+| node_name     | text    | Current node name                  |
+| host          | text    | Host name of the node              |
+| process       | integer | Number of the node process         |
+| port          | integer | Port ID of the node                |
+| installpath   | text    | Installation directory of the node |
+| datapath      | text    | Data directory of the node         |
+| log_directory | text    | Log directory of the node          |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_OS_THREADS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_OS_THREADS.md
new file mode 100644
index 0000000000000000000000000000000000000000..0006b8e555185dc81baf7bd521243b5ad6de14a3
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_OS_THREADS.md
@@ -0,0 +1,20 @@
+---
+title: PG_OS_THREADS
+summary: PG_OS_THREADS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_OS_THREADS
+
+**PG_OS_THREADS** provides status information about all the threads under the current node.
+
+**Table 1** PG_OS_THREADS columns
+
+| Name          | Type                     | Description                                              |
+| :------------ | :----------------------- | :------------------------------------------------------- |
+| node_name     | text                     | Current node name                                        |
+| pid           | bigint                   | PID of the thread running under the current node process |
+| lwpid         | integer                  | Lightweight thread ID corresponding to the PID           |
+| thread_name   | text                     | Thread name corresponding to the PID                     |
+| creation_time | timestamp with time zone | Thread creation time corresponding to the PID            |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_PREPARED_STATEMENTS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_PREPARED_STATEMENTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..31bc933bb8daccf5163a42f77d8571bccbf7152e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_PREPARED_STATEMENTS.md
@@ -0,0 +1,20 @@
+---
+title: PG_PREPARED_STATEMENTS
+summary: PG_PREPARED_STATEMENTS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_PREPARED_STATEMENTS
+
+**PG_PREPARED_STATEMENTS** displays all prepared statements that are available in the current session.
+
+**Table 1** PG_PREPARED_STATEMENTS columns
+
+| Name            | Type                     | Description                                                  |
+| :-------------- | :----------------------- | :----------------------------------------------------------- |
+| name            | text                     | Identifier of the prepared statement                         |
+| statement       | text                     | Query string for creating this prepared statement. For prepared statements created through SQL, this is the PREPARE statement submitted by the client. For prepared statements created through the frontend/backend protocol, this is the text of the prepared statement itself. |
+| prepare_time    | timestamp with time zone | Timestamp when the prepared statement is created             |
+| parameter_types | regtype[]                | Expected parameter types for the prepared statement in the form of an array of **regtype**. The OID corresponding to an element of this array can be obtained by converting the **regtype** value to **oid**. |
+| from_sql        | Boolean                  | - **True** if the prepared statement was created through the PREPARE statement<br/>- **False** if the statement was prepared through the frontend/backend protocol |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_PREPARED_XACTS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_PREPARED_XACTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..5459bfcf1041f948d36e03e71aacfa8fb865a6ce
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_PREPARED_XACTS.md
@@ -0,0 +1,20 @@
+---
+title: PG_PREPARED_XACTS
+summary: PG_PREPARED_XACTS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_PREPARED_XACTS
+
+**PG_PREPARED_XACTS** displays information about transactions that are currently prepared for two-phase commit.
+
+**Table 1** PG_PREPARED_XACTS columns
+
+| Name        | Type                     | Reference           | Description                                                  |
+| :---------- | :----------------------- | :------------------ | :----------------------------------------------------------- |
+| transaction | xid                      | -                   | Numeric transaction identifier of the prepared transaction   |
+| gid         | text                     | -                   | Global transaction identifier that was assigned to the transaction |
+| prepared    | timestamp with time zone | -                   | Time at which the transaction is prepared for commit         |
+| owner       | name                     | PG_AUTHID.rolname   | Name of the user that executes the transaction               |
+| database    | name                     | PG_DATABASE.datname | Name of the database in which the transaction is executed    |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_REPLICATION_SLOTS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_REPLICATION_SLOTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..918432dfa1d8f8d39a4e2bcf926688145b0d69a4
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_REPLICATION_SLOTS.md
@@ -0,0 +1,25 @@
+---
+title: PG_REPLICATION_SLOTS
+summary: PG_REPLICATION_SLOTS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_REPLICATION_SLOTS
+
+**PG_REPLICATION_SLOTS** contains replication node information.
+
+**Table 1** PG_REPLICATION_SLOTS columns
+
+| Name          | Type    | Description                                                  |
+| :------------ | :------ | :----------------------------------------------------------- |
+| slot_name     | text    | Name of a replication node                                   |
+| plugin        | text    | Name of the output plug-in corresponding to the logical replication slot |
+| slot_type     | text    | Type of the replication node                                 |
+| datoid        | oid     | OID of the database on the replication node                  |
+| database      | name    | Name of the database on the replication node                 |
+| active        | Boolean | Whether the replication node is active                       |
+| xmin          | xid     | Transaction ID of the replication node                       |
+| catalog_xmin  | xid     | ID of the earliest-decoded transaction corresponding to the logical replication slot |
+| restart_lsn   | text    | XLOG file information on the replication node                |
+| dummy_standby | Boolean | Whether the replication node is a dummy standby node         |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_RLSPOLICIES.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_RLSPOLICIES.md
new file mode 100644
index 0000000000000000000000000000000000000000..e59690ef1b746dff33d7260ce244dc85a1145e65
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_RLSPOLICIES.md
@@ -0,0 +1,22 @@
+---
+title: PG_RLSPOLICIES
+summary: PG_RLSPOLICIES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_RLSPOLICIES
+
+**PG_RLSPOLICIES** contains row-level access control policies.
+
+**Table 1** PG_RLSPOLICIES columns
+
+| Name             | Type   | Description                                                  |
+| :--------------- | :----- | :----------------------------------------------------------- |
+| schemaname       | name   | Name of the schema of the table object to which a row-level access control policy is applied |
+| tablename        | name   | Name of the table object to which the row-level access control policy is applied |
+| policyname       | name   | Name of the row-level access control policy                  |
+| policypermissive | text   | Attribute of the row-level access control policy             |
+| policyroles      | name[] | List of users affected by the row-level access control policy. If this parameter is not specified, all users are affected. |
+| policycmd        | text   | SQL operations affected by the row-level access control policy |
+| policyqual       | text   | Expression of the row-level access control policy            |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_ROLES.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_ROLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..0a1e751f6187eb099ef194d73956e1a6a25f510a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_ROLES.md
@@ -0,0 +1,39 @@
+---
+title: PG_ROLES
+summary: PG_ROLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_ROLES
+
+PG_ROLES provides information about database roles. Initialization users and users with the sysadmin or createrole attribute can view information about all roles. Other users can view only their own information.
+
+**Table 1** PG_ROLES columns
+
+| Name           | Type                     | Reference             | Description              |
+| :------------- | :----------------------- | :-------------------- | :----------------------- |
+| rolname        | name                     | -                     | Role name                                                    |
+| rolsuper       | Boolean                  | -                     | Whether the role is the initial system administrator with the highest permission |
+| rolinherit     | Boolean                  | -                     | Whether the role inherits the permissions for this type of roles |
+| rolcreaterole  | Boolean                  | -                     | Whether the role can create other roles                      |
+| rolcreatedb    | Boolean                  | -                     | Whether the role can create databases                        |
+| rolcatupdate   | Boolean                  | -                     | Whether the role can update system tables directly. Only the initial system administrator whose **usesysid** is **10** has this permission. It is unavailable for other users. |
+| rolcanlogin    | Boolean                  | -                     | Whether the role can log in to the database                  |
+| rolreplication | Boolean                  | -                     | Whether the role can be replicated                           |
+| rolauditadmin  | Boolean                  | -                     | Whether the role is an audit system administrator            |
+| rolsystemadmin | Boolean                  | -                     | Whether the role is a system administrator                   |
+| rolconnlimit   | integer                  | -                     | Sets the maximum number of concurrent connections that this role can initiate if this role can log in. The value **-1** indicates no limit. |
+| rolpassword    | text                     | -                     | Not the password (always reads as `******`)          |
+| rolvalidbegin  | timestamp with time zone | -                     | Start time of the account validity period (null if no start time) |
+| rolvaliduntil  | timestamp with time zone | -                     | End time for account validity (null if no end time)          |
+| rolrespool     | name                     | -                     | Resource pool that a user can use                            |
+| rolparentid    | oid                      | PG_AUTHID.rolparentid | OID of a group user to which the user belongs                |
+| roltabspace    | text                     | -                     | Storage space of the user permanent table                    |
+| roltempspace   | text                     | -                     | Storage space of the user temporary table                    |
+| rolspillspace  | text                     | -                     | Operator disk spill space of the user                        |
+| rolconfig      | text[]                   | -                     | Session defaults for runtime configuration variables         |
+| oid            | oid                      | PG_AUTHID.oid         | Role ID                                                      |
+| roluseft       | Boolean                  | PG_AUTHID.roluseft    | Whether the role can perform operations on foreign tables    |
+| rolkind        | "char"                   | -                     | Role type                                                    |
+| nodegroup      | name                     | -                     | Unsupported currently                                        |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_RULES.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_RULES.md
new file mode 100644
index 0000000000000000000000000000000000000000..74816c5212da9b193b1527b45e521e31b9efe169
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_RULES.md
@@ -0,0 +1,19 @@
+---
+title: PG_RULES
+summary: PG_RULES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_RULES
+
+**PG_RULES** provides access to query useful information about rewrite rules.
+
+**Table 1** PG_RULES columns
+
+| Name       | Type | Description                                        |
+| :--------- | :--- | :------------------------------------------------- |
+| schemaname | name | Name of the schema that contains a table           |
+| tablename  | name | Name of the table to which the rule applies        |
+| rulename   | name | Name of a rule                                     |
+| definition | text | Rule definition (a reconstructed creation command) |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_SECLABELS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_SECLABELS.md
new file mode 100644
index 0000000000000000000000000000000000000000..d164df32e8800e04d75db256766179828c7a2322
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_SECLABELS.md
@@ -0,0 +1,23 @@
+---
+title: PG_SECLABELS
+summary: PG_SECLABELS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_SECLABELS
+
+**PG_SECLABELS** provides information about security labels.
+
+**Table 1** PG_SECLABELS columns
+
+| Name         | Type    | Reference            | Description                                                  |
+| :----------- | :------ | :------------------- | :----------------------------------------------------------- |
+| objoid       | oid     | Any OID column       | OID of the object that this security label pertains to       |
+| classoid     | oid     | PG_CLASS.oid         | OID of the system catalog where the object appears           |
+| objsubid     | integer | -                    | Column number for the security label on a table column (**objoid** and **classoid** refer to the table itself). The value is **0** for all other object types. |
+| objtype      | text    | -                    | Type of object to which this label applies, as text          |
+| objnamespace | oid     | PG_NAMESPACE.oid     | OID of the namespace for this object, if applicable; otherwise **NULL** |
+| objname      | text    | -                    | Text-typed name of the object to which this label applies    |
+| provider     | text    | PG_SECLABEL.provider | Label provider associated with the label                     |
+| label        | text    | PG_SECLABEL.label    | Security label applied to the object                         |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_SETTINGS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_SETTINGS.md
new file mode 100644
index 0000000000000000000000000000000000000000..641033c4611e70aaac1251b9136342c49004471d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_SETTINGS.md
@@ -0,0 +1,31 @@
+---
+title: PG_SETTINGS
+summary: PG_SETTINGS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_SETTINGS
+
+**PG_SETTINGS** displays information about parameters of the running database.
+
+**Table 1** PG_SETTINGS columns
+
+| Name       | Type    | Description                                                  |
+| :--------- | :------ | :----------------------------------------------------------- |
+| name       | text    | Parameter name                                               |
+| setting    | text    | Current parameter value                                      |
+| unit       | text    | Implicit unit of the parameter                               |
+| category   | text    | Logical group of the parameter                               |
+| short_desc | text    | Brief description of the parameter                           |
+| extra_desc | text    | Detailed description of the parameter                        |
+| context    | text    | Context required to set the parameter value, including **internal**, **postmaster**, **sighup**, **backend**, **superuser**, and **user** |
+| vartype    | text    | Parameter type, including **bool**, **enum**, **integer**, **real**, or **string** |
+| source     | text    | Method of assigning the parameter value                      |
+| min_val    | text    | Minimum value of the parameter. If the parameter type is not numeric, the value of this column is **null**. |
+| max_val    | text    | Maximum value of the parameter. If the parameter type is not numeric, the value of this column is **null**. |
+| enumvals   | text[]  | Valid values of an enum-type parameter. If the parameter type is not enum, the value of this column is **null**. |
+| boot_val   | text    | Default parameter value used upon the database startup       |
+| reset_val  | text    | Default parameter value used upon the database reset         |
+| sourcefile | text    | Configuration file used to set parameter values. If parameter values are not configured using the configuration file, the value of this column is **null**. |
+| sourceline | integer | Row number of the configuration file for setting parameter values. If parameter values are not configured using the configuration file, the value of this column is **null**. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_SHADOW.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_SHADOW.md
new file mode 100644
index 0000000000000000000000000000000000000000..7f0ebe4f583c5054008d3f93eaeca6c8a7cb8b6b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_SHADOW.md
@@ -0,0 +1,31 @@
+---
+title: PG_SHADOW
+summary: PG_SHADOW
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_SHADOW
+
+**PG_SHADOW** displays properties of all roles that are marked as **rolcanlogin** in **PG_AUTHID**.
+
+The name stems from the fact that this view should not be readable by the public since it contains passwords. PG_USER is a publicly readable view on **PG_SHADOW** that blanks out the password column.
+
+**Table 1** PG_SHADOW columns
+
+| Name            | Type                     | Reference         | Description                                                  |
+| :-------------- | :----------------------- | :---------------- | :----------------------------------------------------------- |
+| usename         | name                     | PG_AUTHID.rolname | Username                                                     |
+| usesysid        | oid                      | PG_AUTHID.oid     | ID of this user                                              |
+| usecreatedb     | Boolean                  | -                 | Indicates that the user can create databases.                |
+| usesuper        | Boolean                  | -                 | Indicates that the user is an administrator.                 |
+| usecatupd       | Boolean                  | -                 | Users can update a view. Even the system administrator cannot do this unless this column is **true**. |
+| userepl         | Boolean                  | -                 | User can initiate streaming replication and put the system in and out of backup mode. |
+| passwd          | text                     | -                 | Password (possibly encrypted); **null** if none. See PG_AUTHID for details about how encrypted passwords are stored. |
+| valbegin        | timestamp with time zone | -                 | Account validity period start time (**null** if no start time) |
+| valuntil        | timestamp with time zone | -                 | Password expiry time (**null** if no expiration)             |
+| respool         | name                     | -                 | Resource pool used by the user                               |
+| parent          | oid                      | -                 | Parent resource pool                                         |
+| spacelimit      | text                     | -                 | Storage space of the permanent table                         |
+| tempspacelimit  | text                     | -                 | Storage space of the temporary table                         |
+| spillspacelimit | text                     | -                 | Operator disk flushing space                                 |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_ALL_INDEXES.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_ALL_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..f089586fa98511680d9b82a004704f4f7497201d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_ALL_INDEXES.md
@@ -0,0 +1,22 @@
+---
+title: PG_STATIO_ALL_INDEXES
+summary: PG_STATIO_ALL_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STATIO_ALL_INDEXES
+
+**PG_STATIO_ALL_INDEXES** contains one row for each index in the current database, showing I/O statistics about accesses to that specific index.
+
+**Table 1** PG_STATIO_ALL_INDEXES columns
+
+| Name          | Type   | Description                                     |
+| :------------ | :----- | :---------------------------------------------- |
+| relid         | oid    | OID of the table for this index                 |
+| indexrelid    | oid    | OID of the index                                |
+| schemaname    | name   | Name of the schema that the index is in         |
+| relname       | name   | Name of the table that the index is created for |
+| indexrelname  | name   | Index name                                      |
+| idx_blks_read | bigint | Number of disk blocks read from the index       |
+| idx_blks_hit  | bigint | Number of cache hits in the index               |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_ALL_SEQUENCES.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_ALL_SEQUENCES.md
new file mode 100644
index 0000000000000000000000000000000000000000..1cb97d269b31f4538b7fa53f117ef8d9d5444afb
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_ALL_SEQUENCES.md
@@ -0,0 +1,20 @@
+---
+title: PG_STATIO_ALL_SEQUENCES
+summary: PG_STATIO_ALL_SEQUENCES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STATIO_ALL_SEQUENCES
+
+**PG_STATIO_ALL_SEQUENCES** contains the I/O statistics of each sequence in the current database.
+
+**Table 1** PG_STATIO_ALL_SEQUENCES columns
+
+| Name       | Type   | Description                                  |
+| :--------- | :----- | :------------------------------------------- |
+| relid      | oid    | OID of this sequence                         |
+| schemaname | name   | Name of the schema where the sequence is in  |
+| relname    | name   | Name of the sequence                         |
+| blks_read  | bigint | Number of disk blocks read from the sequence |
+| blks_hit   | bigint | Cache hits in the sequence                   |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_ALL_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_ALL_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..1f7e3fded51b4a9c75f8c58400ddf02ac54e3e76
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_ALL_TABLES.md
@@ -0,0 +1,26 @@
+---
+title: PG_STATIO_ALL_TABLES
+summary: PG_STATIO_ALL_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STATIO_ALL_TABLES
+
+**PG_STATIO_ALL_TABLES** contains I/O statistics for each table (including the TOAST table) in the current database.
+
+**Table 1** PG_STATIO_ALL_TABLES columns
+
+| Name            | Type   | Description                                                  |
+| :-------------- | :----- | :----------------------------------------------------------- |
+| relid           | oid    | Table OID                                                    |
+| schemaname      | name   | Name of the schema that the table is in                      |
+| relname         | name   | Table name                                                   |
+| heap_blks_read  | bigint | Number of disk blocks read from the table                    |
+| heap_blks_hit   | bigint | Number of cache hits in the table                            |
+| idx_blks_read   | bigint | Number of disk blocks read from all indexes in the table     |
+| idx_blks_hit    | bigint | Number of cache hits in indexes in the table                 |
+| toast_blks_read | bigint | Number of disk blocks read from the TOAST table (if any) in the table |
+| toast_blks_hit  | bigint | Number of buffer hits in the TOAST table (if any) in the table |
+| tidx_blks_read  | bigint | Number of disk blocks read from the TOAST table index (if any) in the table |
+| tidx_blks_hit   | bigint | Number of buffer-hits in the TOAST table index (if any) in the table |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_SYS_INDEXES.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_SYS_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..6b80364ed30e70444fc548dbd5088dba4e50f774
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_SYS_INDEXES.md
@@ -0,0 +1,22 @@
+---
+title: PG_STATIO_SYS_INDEXES
+summary: PG_STATIO_SYS_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STATIO_SYS_INDEXES
+
+**PG_STATIO_SYS_INDEXES** displays I/O status information for all system catalog indexes in a namespace.
+
+**Table 1** PG_STATIO_SYS_INDEXES columns
+
+| Name          | Type   | Description                                     |
+| :------------ | :----- | :---------------------------------------------- |
+| relid         | oid    | OID of the table for this index                 |
+| indexrelid    | oid    | OID of the index                                |
+| schemaname    | name   | Name of the schema that the index is in         |
+| relname       | name   | Name of the table that the index is created for |
+| indexrelname  | name   | Index name                                      |
+| idx_blks_read | bigint | Number of disk blocks read from the index       |
+| idx_blks_hit  | bigint | Number of cache hits in the index               |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_SYS_SEQUENCES.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_SYS_SEQUENCES.md
new file mode 100644
index 0000000000000000000000000000000000000000..b4e37c5e52b3f11beddf4c76514d9d944e19b6dc
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_SYS_SEQUENCES.md
@@ -0,0 +1,20 @@
+---
+title: PG_STATIO_SYS_SEQUENCES
+summary: PG_STATIO_SYS_SEQUENCES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STATIO_SYS_SEQUENCES
+
+**PG_STATIO_SYS_SEQUENCES** displays I/O status information about all the sequences in the namespace.
+
+**Table 1** PG_STATIO_SYS_SEQUENCES columns
+
+| Name       | Type   | Description                                  |
+| :--------- | :----- | :------------------------------------------- |
+| relid      | oid    | OID of this sequence                         |
+| schemaname | name   | Name of the schema where the sequence is in  |
+| relname    | name   | Name of the sequence                         |
+| blks_read  | bigint | Number of disk blocks read from the sequence |
+| blks_hit   | bigint | Cache hits in the sequence                   |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_SYS_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_SYS_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..eae4d0e19a68116abac7d861393148bfcfa1f202
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_SYS_TABLES.md
@@ -0,0 +1,26 @@
+---
+title: PG_STATIO_SYS_TABLES
+summary: PG_STATIO_SYS_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STATIO_SYS_TABLES
+
+**PG_STATIO_SYS_TABLES** shows I/O status information about all the system catalogs in the namespace.
+
+**Table 1** PG_STATIO_SYS_TABLES columns
+
+| Name            | Type   | Description                                                  |
+| :-------------- | :----- | :----------------------------------------------------------- |
+| relid           | oid    | Table OID                                                    |
+| schemaname      | name   | Name of the schema the table is in                           |
+| relname         | name   | Table name                                                   |
+| heap_blks_read  | bigint | Number of disk blocks read from the table                    |
+| heap_blks_hit   | bigint | Number of cache hits in the table                            |
+| idx_blks_read   | bigint | Number of disk blocks read from all indexes in the table     |
+| idx_blks_hit    | bigint | Number of cache hits in indexes in the table                 |
+| toast_blks_read | bigint | Number of disk blocks read from the TOAST table (if any) in the table |
+| toast_blks_hit  | bigint | Number of buffer hits in the TOAST table (if any) in the table |
+| tidx_blks_read  | bigint | Number of disk blocks read from the TOAST table index (if any) in the table |
+| tidx_blks_hit   | bigint | Number of buffer-hits in the TOAST table index (if any) in the table |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_USER_INDEXES.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_USER_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..27021923446feea32294afe5325fc75d22573716
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_USER_INDEXES.md
@@ -0,0 +1,22 @@
+---
+title: PG_STATIO_USER_INDEXES
+summary: PG_STATIO_USER_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STATIO_USER_INDEXES
+
+**PG_STATIO_USER_INDEXES** displays I/O status information about all the user relationship table indexes in the namespace.
+
+**Table 1** PG_STATIO_USER_INDEXES columns
+
+| Name          | Type   | Description                                    |
+| :------------ | :----- | :--------------------------------------------- |
+| relid         | oid    | OID of the table that the index is created for |
+| indexrelid    | oid    | OID of the index                               |
+| schemaname    | name   | Name of the schema that the index is in        |
+| relname       | name   | Name of the table for the index                |
+| indexrelname  | name   | Index name                                     |
+| idx_blks_read | bigint | Number of disk blocks read from the index      |
+| idx_blks_hit  | bigint | Number of cache hits in the index              |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_USER_SEQUENCES.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_USER_SEQUENCES.md
new file mode 100644
index 0000000000000000000000000000000000000000..a5ecfd192b23f75d924d2aab584aaeec6ad4fd0d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_USER_SEQUENCES.md
@@ -0,0 +1,20 @@
+---
+title: PG_STATIO_USER_SEQUENCES
+summary: PG_STATIO_USER_SEQUENCES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STATIO_USER_SEQUENCES
+
+**PG_STATIO_USER_SEQUENCES** shows I/O status information about all the user relationship table sequences in the namespace.
+
+**Table 1** PG_STATIO_USER_SEQUENCES columns
+
+| Name       | Type   | Description                                  |
+| :--------- | :----- | :------------------------------------------- |
+| relid      | oid    | OID of this sequence                         |
+| schemaname | name   | Name of the schema where the sequence is in  |
+| relname    | name   | Name of the sequence                         |
+| blks_read  | bigint | Number of disk blocks read from the sequence |
+| blks_hit   | bigint | Cache hits in the sequence                   |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_USER_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_USER_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..43ff6c46e8ed2ba1463a779af42138ce0a1c268b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_USER_TABLES.md
@@ -0,0 +1,26 @@
+---
+title: PG_STATIO_USER_TABLES
+summary: PG_STATIO_USER_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STATIO_USER_TABLES
+
+**PG_STATIO_USER_TABLES** displays I/O status information about all the user relationship tables in the namespace.
+
+**Table 1** PG_STATIO_USER_TABLES columns
+
+| Name            | Type   | Description                                                  |
+| :-------------- | :----- | :----------------------------------------------------------- |
+| relid           | oid    | Table OID                                                    |
+| schemaname      | name   | Name of the schema that the table is in                      |
+| relname         | name   | Table name                                                   |
+| heap_blks_read  | bigint | Number of disk blocks read from the table                    |
+| heap_blks_hit   | bigint | Number of cache hits in the table                            |
+| idx_blks_read   | bigint | Number of disk blocks read from all indexes in the table     |
+| idx_blks_hit    | bigint | Number of cache hits in indexes in the table                 |
+| toast_blks_read | bigint | Number of disk blocks read from the TOAST table (if any) in the table |
+| toast_blks_hit  | bigint | Number of buffer hits in the TOAST table (if any) in the table |
+| tidx_blks_read  | bigint | Number of disk blocks read from the TOAST table index (if any) in the table |
+| tidx_blks_hit   | bigint | Number of buffer-hits in the TOAST table index (if any) in the table |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATS.md
new file mode 100644
index 0000000000000000000000000000000000000000..7717bb588f0ff1d81bdcb49708afc850fd8fe9e7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATS.md
@@ -0,0 +1,30 @@
+---
+title: PG_STATS
+summary: PG_STATS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STATS
+
+**PG_STATS** provides access to the single-column statistics stored in the **pg_statistic** table. The **autovacuum_naptime** parameter specifies the interval for updating statistics recorded in the view.
+
+**Table 1** PG_STATS columns
+
+| Name                   | Type     | Reference            | Description                                                  |
+| :--------------------- | :------- | :------------------- | :----------------------------------------------------------- |
+| schemaname             | name     | PG_NAMESPACE.nspname | Name of the schema that contains a table                     |
+| tablename              | name     | PG_CLASS.relname     | Table name                                                   |
+| attname                | name     | PG_ATTRIBUTE.attname | Field name                                                   |
+| inherited              | Boolean  | -                    | Includes inherited sub-columns if the value is **true**; otherwise, it indicates the column in a specified table. |
+| null_frac              | real     | -                    | Percentage of column entries that are null                   |
+| avg_width              | integer  | -                    | Average width in bytes of column's entries                   |
+| n_distinct             | real     | -                    | - Estimated number of distinct values in the column if the value is greater than 0<br/>- Negative of the number of distinct values divided by the number of rows if the value is less than 0<br/>    1. The negated form is used when **ANALYZE** believes that the number of distinct values is likely to increase as the table grows.<br/>    2. The positive form is used when the column seems to have a fixed number of possible values. For example, **-1** indicates that the number of distinct values is the same as the number of rows for a unique column. |
+| n_dndistinct           | real     | -                    | Number of unique non-null data values in the **dn1** column<br/>- Exact number of distinct values if the value is greater than **0**.<br/>- Negative of the number of distinct values divided by the number of rows if the value is less than 0 For example, if the value of a column appears twice in average, set **n\_dndistinct=-0.5**.<br/>- The number of distinct values is unknown if the value is **0**. |
+| most_common_vals       | anyarray | -                    | List of the most common values in a column. (**NULL** if no values in the column seem to be more common than any others) |
+| most_common_freqs      | real[]   | -                    | List of the frequencies of the most common values, that is, number of occurrences of each divided by total number of rows. (**NULL** if **most_common_vals** is **NULL**) |
+| histogram_bounds       | anyarray | -                    | List of values that divide the column's values into groups of equal proportion. The values in **most_common_vals**, if present, are omitted from this histogram calculation. This field is null if the field data type does not have a **<** operator or if the **most_common_vals** list accounts for the entire population. |
+| correlation            | real     | -                    | Statistical correlation between physical row ordering and logical ordering of the column values. It ranges from -1 to +1. When the value is near to -1 or +1, an index scan on the column is estimated to be cheaper than when it is near to zero, due to reduction of random access to the disk. This column is null if the column data type does not have a < operator. |
+| most_common_elems      | anyarray | -                    | A list of non-null element values most often appearing       |
+| most_common_elem_freqs | real[]   | -                    | A list of the frequencies of the most common element values  |
+| elem_count_histogram   | real[]   | -                    | A histogram of the counts of distinct non-null element values |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_ACTIVITY.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_ACTIVITY.md
new file mode 100644
index 0000000000000000000000000000000000000000..4de8834806803b1e9e27655387ebc9edc703e357
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_ACTIVITY.md
@@ -0,0 +1,36 @@
+---
+title: PG_STAT_ACTIVITY
+summary: PG_STAT_ACTIVITY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STAT_ACTIVITY
+
+**PG_STAT_ACTIVITY** shows information about the current user's queries. The columns save information about the last query.
+
+**Table 1** PG_STAT_ACTIVITY columns
+
+| Name             | Type                     | Description                                                  |
+| :--------------- | :----------------------- | :----------------------------------------------------------- |
+| datid            | oid                      | OID of the database that the user session connects to in the backend |
+| datname          | name                     | Name of the database that the user session connects to in the backend |
+| pid              | bigint                   | Thread ID of the backend                                     |
+| sessionid        | bigint                   | Session ID                                                   |
+| usesysid         | oid                      | OID of the user logged in to the backend                     |
+| usename          | name                     | Name of the user logged in to the backend                    |
+| application_name | text                     | Name of the application connected to the backend             |
+| client_addr      | inet                     | IP address of the client connected to the backend. If this column is null, it indicates either the client is connected via a Unix socket on the server or this is an internal process, such as autovacuum. |
+| client_hostname  | text                     | Host name of the connected client, as reported by a reverse DNS lookup of **client\_addr**. This column will be non-null only for IP connections and only when **log_hostname** is enabled. |
+| client_port      | integer                  | TCP port number that the client uses for communication with this backend (**-1** if a Unix socket is used) |
+| backend_start    | timestamp with time zone | Time when this process was started, that is, when the client connected to the server |
+| xact_start       | timestamp with time zone | Time when current transaction was started (null if no transaction is active) If the current query is the first of its transaction, the value of this column is the same as that of the **query_start** column. |
+| query_start      | timestamp with time zone | Time when the currently active query was started, or if **state** is not **active**, when the last query was started |
+| state_change     | timestamp with time zone | Time when the **state** was last changed                     |
+| waiting          | Boolean                  | Whether the backend is currently waiting on a lock. If yes, the value is **true**. |
+| enqueue          | text                     | Unsupported currently                                        |
+| state            | text                     | Overall status of this backend. The value must be one of the following:<br/>- **active**: The backend is executing a query.<br/>- **idle**: The backend is waiting for a new client command.<br/>- **idle in transaction**: The backend is in a transaction, but there is no statement being executed in the transaction.<br/>- **idle in transaction** (aborted): The backend is in a transaction, but there are statements failed in the transaction.<br/>- **fastpath function call**: The backend is executing a fast-path function.<br/>- **disabled**: This state is reported if **track_activities** is disabled in this backend.<br/>NOTE:<br/>Common users can view their own session status only. The state information of other accounts is empty. For example, after user **judy** is connected to the database, the state information of user **joe** and the initial user omm in **pg_stat_activity** is empty.<br/>`SELECT datname, usename, usesysid, state,pid FROM pg_stat_activity;`<br/><br/>datname  \| usename \| usesysid \| state  \|       pid<br/>----+---+----+---+------<br/>postgres \| omm     \|       10 \|        \| 139968752121616<br/>postgres \| omm     \|       10 \|        \| 139968903116560<br/>db_tpcc \| judy    \|    16398 \| active \| 139968391403280<br/>postgres \| omm     \|       10 \|        \| 139968643069712<br/>postgres \| omm     \|       10 \|        \| 139968680818448<br/>postgres \| joe     \|    16390 \|        \| 139968563377936<br/>(6 rows) |
+| resource_pool    | name                     | Resource pool used by the user                               |
+| query_id         | bigint                   | ID of a query                                                |
+| query            | text                     | Text of this backend's most recent query. If **state** is **active**, this column shows the ongoing query. In all other states, it shows the last query that was executed. |
+| connection_info  | text                     | A string in JSON format recording the driver type, driver version, driver deployment path, and process owner of the connected database. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_ALL_INDEXES.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_ALL_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..b52e9c5c8a56600ae732a91e4bd0d50555b6f5fc
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_ALL_INDEXES.md
@@ -0,0 +1,25 @@
+---
+title: PG_STAT_ALL_INDEXES
+summary: PG_STAT_ALL_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STAT_ALL_INDEXES
+
+**PG_STAT_ALL_INDEXES** contains one row for each index in the current database, showing statistics about accesses to that specific index.
+
+Indexes can be used via either simple index scans or "bitmap" index scans. In a bitmap scan the output of several indexes can be combined via AND or OR rules, so it is difficult to associate individual heap row fetches with specific indexes when a bitmap scan is used. Therefore, a bitmap scan increments the **pg_stat_all_indexes.idx_tup_read** count(s) for the index(es) it uses, and it increments the **pg_stat_all_tables.idx_tup_fetch** count for the table, but it does not affect **pg_stat_all_indexes.idx_tup_fetch**.
+
+**Table 1** PG_STAT_ALL_INDEXES columns
+
+| Name          | Type   | Description                                                  |
+| :------------ | :----- | :----------------------------------------------------------- |
+| relid         | oid    | OID of the table for this index                              |
+| indexrelid    | oid    | OID of this index                                            |
+| schemaname    | name   | Name of the schema that the index is in                      |
+| relname       | name   | Name of the table for the index                              |
+| indexrelname  | name   | Index name                                                   |
+| idx_scan      | bigint | Number of index scans initiated on the index                 |
+| idx_tup_read  | bigint | Number of index entries returned by scans on the index       |
+| idx_tup_fetch | bigint | Number of live table rows fetched by simple index scans using the index |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_ALL_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_ALL_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..36b22d603723c08d07bd4756e84d37f971f72082
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_ALL_TABLES.md
@@ -0,0 +1,37 @@
+---
+title: PG_STAT_ALL_TABLES
+summary: PG_STAT_ALL_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STAT_ALL_TABLES
+
+**PG_STAT_ALL_TABLES** contains one row for each table in the current database (including TOAST tables), showing statistics about accesses to that specific table.
+
+**Table 1** PG_STAT_ALL_TABLES columns
+
+| Name              | Type                     | Description                                                  |
+| :---------------- | :----------------------- | :----------------------------------------------------------- |
+| relid             | oid                      | OID of the table                                             |
+| schemaname        | name                     | Name of the schema that the table is in                      |
+| relname           | name                     | Table name                                                   |
+| seq_scan          | bigint                   | Number of sequential scans initiated on the table            |
+| seq_tup_read      | bigint                   | Number of live rows fetched by sequential scans              |
+| idx_scan          | bigint                   | Number of index scans initiated on the table                 |
+| idx_tup_fetch     | bigint                   | Number of live rows fetched by index scans                   |
+| n_tup_ins         | bigint                   | Number of rows inserted                                      |
+| n_tup_upd         | bigint                   | Number of rows updated                                       |
+| n_tup_del         | bigint                   | Number of rows deleted                                       |
+| n_tup_hot_upd     | bigint                   | Number of rows HOT updated (that is, with no separate index update required) |
+| n_live_tup        | bigint                   | Estimated number of live rows                                |
+| n_dead_tup        | bigint                   | Estimated number of dead rows                                |
+| last_vacuum       | timestamp with time zone | Last time when the table is cleared                          |
+| last_autovacuum   | timestamp with time zone | Last time at which the table was vacuumed by the autovacuum daemon |
+| last_analyze      | timestamp with time zone | Last time when the table is analyzed                         |
+| last_autoanalyze  | timestamp with time zone | Last time at which the table was analyzed by the autovacuum daemon |
+| vacuum_count      | bigint                   | Number of times the table is cleared                         |
+| autovacuum_count  | bigint                   | Number of times the table has been vacuumed by the autovacuum daemon |
+| analyze_count     | bigint                   | Number of times the table is analyzed                        |
+| autoanalyze_count | bigint                   | Number of times the table has been analyzed by the autovacuum daemon |
+| last_data_changed | timestamp with time zone | Last time at which the table was updated (by **INSERT**/**UPDATE**/**DELETE** or **EXCHANGE**/**TRUNCATE**/**DROP** **partition**). This column is recorded only on the local primary database node. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_BAD_BLOCK.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_BAD_BLOCK.md
new file mode 100644
index 0000000000000000000000000000000000000000..b7fd613cd764d82a5d1fe06b346011c09a1cdcfe
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_BAD_BLOCK.md
@@ -0,0 +1,24 @@
+---
+title: PG_STAT_BAD_BLOCK
+summary: PG_STAT_BAD_BLOCK
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STAT_BAD_BLOCK
+
+**PG_STAT_BAD_BLOCK** shows statistics about Page or CU verification failures after a node is started.
+
+**Table 1** PG_STAT_BAD_BLOCK columns
+
+| Name         | Type                     | Description                                                  |
+| :----------- | :----------------------- | :----------------------------------------------------------- |
+| nodename     | text                     | Node name                                                    |
+| databaseid   | integer                  | OID of a database                                            |
+| tablespaceid | integer                  | Tablespace OID                                               |
+| relfilenode  | integer                  | File object ID                                               |
+| bucketid     | smallint                 | ID of the bucket for consistent hashing                      |
+| forknum      | integer                  | File type. The values are as follows:<br />- **0**: main data file<br />- **1**: FSM file<br />- **2**: VM file<br />- **3**: BCM file<br />If the value is greater than 4, it indicates a data file of each column in a column-store table. |
+| error_count  | integer                  | Number of verification failures                              |
+| first_time   | timestamp with time zone | Time of the first verification failure                       |
+| last_time    | timestamp with time zone | Time of the latest verification failure                      |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_BGWRITER.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_BGWRITER.md
new file mode 100644
index 0000000000000000000000000000000000000000..9bcb723b414bd254911531dbc00b64e1fbf322b9
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_BGWRITER.md
@@ -0,0 +1,26 @@
+---
+title: PG_STAT_BGWRITER
+summary: PG_STAT_BGWRITER
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STAT_BGWRITER
+
+**PG_STAT_BGWRITER** showing statistics about the background writer process's activity.
+
+**Table 1** PG_STAT_BGWRITER columns
+
+| Name                  | Type                     | Description                                                  |
+| :-------------------- | :----------------------- | :----------------------------------------------------------- |
+| checkpoints_timed     | bigint                   | Number of scheduled checkpoints that have been performed     |
+| checkpoints_req       | bigint                   | Number of requested checkpoints that have been performed     |
+| checkpoint_write_time | double precision         | Total time that has been spent in the portion of checkpoint processing where files are written to disk (unit: ms) |
+| checkpoint_sync_time  | double precision         | Total time that has been spent in the portion of checkpoint processing where files are synchronized to disk (unit: ms) |
+| buffers_checkpoint    | bigint                   | Number of buffers written during checkpoints                 |
+| buffers_clean         | bigint                   | Number of buffers written by the background writer           |
+| maxwritten_clean      | bigint                   | Number of times the background writer stopped a cleaning scan because it had written too many buffers |
+| buffers_backend       | bigint                   | Number of buffers written directly by a backend              |
+| buffers_backend_fsync | bigint                   | Number of times a backend had to execute its own fsync call (normally the background writer handles those even when the backend does its own write) |
+| buffers_alloc         | bigint                   | Number of buffers allocated                                  |
+| stats_reset           | timestamp with time zone | Time at which these statistics were last reset               |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_DATABASE.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_DATABASE.md
new file mode 100644
index 0000000000000000000000000000000000000000..d4d621dcb83bb342ebbb7233582739488170027e
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_DATABASE.md
@@ -0,0 +1,34 @@
+---
+title: PG_STAT_DATABASE
+summary: PG_STAT_DATABASE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STAT_DATABASE
+
+**PG_STAT_DATABASE** contains database statistics for each database in the MogDB.
+
+**Table 1** PG_STAT_DATABASE columns
+
+| Name           | Type                     | Description                                                  |
+| :------------- | :----------------------- | :----------------------------------------------------------- |
+| datid          | oid                      | OID of a database                                            |
+| datname        | name                     | Name of the database                                         |
+| numbackends    | integer                  | Number of backends currently connected to this database. This is the only column in this view that returns a value reflecting the current state; all other columns return the accumulated values since the last reset. |
+| xact_commit    | bigint                   | Number of transactions in this database that have been committed |
+| xact_rollback  | bigint                   | Number of transactions in this database that have been rolled back |
+| blks_read      | bigint                   | Number of disk blocks read in this database                  |
+| blks_hit       | bigint                   | Number of times disk blocks were found already in the buffer cache, so that a read was not necessary (this only includes hits in the PostgreSQL buffer cache, not the operating system's file system cache) |
+| tup_returned   | bigint                   | Number of rows returned by queries in this database          |
+| tup_fetched    | bigint                   | Number of rows fetched by queries in this database           |
+| tup_inserted   | bigint                   | Number of rows inserted by queries in this database          |
+| tup_updated    | bigint                   | Number of rows updated by queries in this database           |
+| tup_deleted    | bigint                   | Number of rows deleted by queries in this database           |
+| conflicts      | bigint                   | Number of queries canceled due to database recovery conflicts (conflicts occurring only on the standby server). For details, see PG_STAT_DATABASE_CONFLICTS. |
+| temp_files     | bigint                   | Number of temporary files created by queries in this database. All temporary files are counted, regardless of why the temporary file was created (for example, sorting or hashing), and regardless of the **log_temp_files** setting. |
+| temp_bytes     | bigint                   | Total amount of data written to temporary files by queries in this database. All temporary files are counted, regardless of why the temporary file was created, and regardless of the **log_temp_files** setting. |
+| deadlocks      | bigint                   | Number of deadlocks detected in this database                |
+| blk_read_time  | double precision         | Time spent reading data file blocks by backends in this database (unit: ms) |
+| blk_write_time | double precision         | Time spent writing into data file blocks by backends in this database (unit: ms) |
+| stats_reset    | timestamp with time zone | Time at which the current statistics were reset              |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_DATABASE_CONFLICTS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_DATABASE_CONFLICTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..a5502602522ba28946c81aea5dc82c3fe88e44be
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_DATABASE_CONFLICTS.md
@@ -0,0 +1,22 @@
+---
+title: PG_STAT_DATABASE_CONFLICTS
+summary: PG_STAT_DATABASE_CONFLICTS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STAT_DATABASE_CONFLICTS
+
+**PG_STAT_DATABASE_CONFLICTS** displays statistics about database conflicts.
+
+**Table 1** PG_STAT_DATABASE_CONFLICTS columns
+
+| Name             | Type   | Description                       |
+| :--------------- | :----- | :-------------------------------- |
+| datid            | oid    | Database ID                       |
+| datname          | name   | Database name                     |
+| confl_tablespace | bigint | Number of conflicting tablespaces |
+| confl_lock       | bigint | Number of conflicting locks       |
+| confl_snapshot   | bigint | Number conflicting snapshots      |
+| confl_bufferpin  | bigint | Number of conflicting buffers     |
+| confl_deadlock   | bigint | Number of conflicting deadlocks   |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_REPLICATION.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_REPLICATION.md
new file mode 100644
index 0000000000000000000000000000000000000000..c1690e40e53462cc5a032aaf8614d3f9c41806d9
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_REPLICATION.md
@@ -0,0 +1,30 @@
+---
+title: PG_STAT_REPLICATION
+summary: PG_STAT_REPLICATION
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STAT_REPLICATION
+
+**PG_STAT_REPLICATION** displays information about log synchronization status, such as the locations of the sender sending logs and the receiver receiving logs.
+
+**Table 1** PG_STAT_REPLICATION columns
+
+| Name                     | Type                     | Description                                                  |
+| :----------------------- | :----------------------- | :----------------------------------------------------------- |
+| pid                      | bigint                   | Process ID of the thread                                     |
+| usesysid                 | oid                      | User system ID                                               |
+| usename                  | name                     | Username                                                     |
+| application_name         | text                     | Program name                                                 |
+| client_addr              | inet                     | Client address                                               |
+| client_hostname          | text                     | Client name                                                  |
+| client_port              | integer                  | Port of the client                                           |
+| backend_start            | timestamp with time zone | Start time of the program                                    |
+| state                    | text                     | Log replication state (catch-up or consistent streaming)     |
+| sender_sent_location     | text                     | Location where the sender sends logs                         |
+| receiver_write_location  | text                     | Location where the receiver writes logs                      |
+| receiver_flush_location  | text                     | Location where the receive end flushes logs                  |
+| receiver_replay_location | text                     | Location where the receive end replays logs                  |
+| sync_priority            | integer                  | Priority of synchronous duplication (**0** indicates asynchronization.) |
+| sync_state               | text                     | Synchronization state (asynchronous duplication, synchronous duplication, or potential synchronization) |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_SYS_INDEXES.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_SYS_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..bbb03375237826ecab538a12dd1c5a7f102580ff
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_SYS_INDEXES.md
@@ -0,0 +1,23 @@
+---
+title: PG_STAT_SYS_INDEXES
+summary: PG_STAT_SYS_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STAT_SYS_INDEXES
+
+**PG_STAT_SYS_INDEXES** displays index status information about all the system catalogs in the **pg_catalog** and **information_schema** schemas.
+
+**Table 1** PG_STAT_SYS_INDEXES columns
+
+| Name          | Type   | Description                                                  |
+| :------------ | :----- | :----------------------------------------------------------- |
+| relid         | oid    | OID of the table for this index                              |
+| indexrelid    | oid    | OID of the index                                             |
+| schemaname    | name   | Name of the schema that the index is in                      |
+| relname       | name   | Name of the table for the index                              |
+| indexrelname  | name   | Index name                                                   |
+| idx_scan      | bigint | Number of index scans initiated on the index                 |
+| idx_tup_read  | bigint | Number of index entries returned by scans on the index       |
+| idx_tup_fetch | bigint | Number of live table rows fetched by simple index scans using the index |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_SYS_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_SYS_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..c20295c3cb258689279f0e42f0f43c23719798ad
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_SYS_TABLES.md
@@ -0,0 +1,37 @@
+---
+title: PG_STAT_SYS_TABLES
+summary: PG_STAT_SYS_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STAT_SYS_TABLES
+
+**PG_STAT_SYS_TABLES** displays statistics about the system catalogs of all the namespaces in **pg_catalog** and **information_schema** schemas.
+
+**Table 1** PG_STAT_SYS_TABLES columns
+
+| Name              | Type                     | Description                                                  |
+| :---------------- | :----------------------- | :----------------------------------------------------------- |
+| relid             | oid                      | OID of a table                                               |
+| schemaname        | name                     | Schema name of the table                                     |
+| relname           | name                     | Table name                                                   |
+| seq_scan          | bigint                   | Number of sequential scans initiated on the table            |
+| seq_tup_read      | bigint                   | Number of live rows fetched by sequential scans              |
+| idx_scan          | bigint                   | Number of index scans initiated on the table                 |
+| idx_tup_fetch     | bigint                   | Number of live rows fetched by index scans                   |
+| n_tup_ins         | bigint                   | Number of rows inserted                                      |
+| n_tup_upd         | bigint                   | Number of rows updated                                       |
+| n_tup_del         | bigint                   | Number of rows deleted                                       |
+| n_tup_hot_upd     | bigint                   | Number of rows HOT updated (with no separate index update required) |
+| n_live_tup        | bigint                   | Estimated number of live rows                                |
+| n_dead_tup        | bigint                   | Estimated number of dead rows                                |
+| last_vacuum       | timestamp with time zone | Last time when the table was manually vacuumed (excluding **VACUUM FULL**) |
+| last_autovacuum   | timestamp with time zone | Last time when the table was vacuumed by the autovacuum daemon |
+| last_analyze      | timestamp with time zone | Last time when the table was manually analyzed               |
+| last_autoanalyze  | timestamp with time zone | Last time when the table was analyzed by the autovacuum daemon |
+| vacuum_count      | bigint                   | Number of times the table has been manually vacuumed (not counting **VACUUM FULL**) |
+| autovacuum_count  | bigint                   | Number of times the table has been vacuumed by the autovacuum daemon |
+| analyze_count     | bigint                   | Number of times the table has been manually analyzed         |
+| autoanalyze_count | bigint                   | Number of times the table has been analyzed by the autovacuum daemon |
+| last_data_changed | timestamp with time zone | Last modification time of the table data                     |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_USER_FUNCTIONS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_USER_FUNCTIONS.md
new file mode 100644
index 0000000000000000000000000000000000000000..6db360f832c068b86dd6b6c90fec91f065b70a4d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_USER_FUNCTIONS.md
@@ -0,0 +1,21 @@
+---
+title: PG_STAT_USER_FUNCTIONS
+summary: PG_STAT_USER_FUNCTIONS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STAT_USER_FUNCTIONS
+
+**PG_STAT_USER_FUNCTIONS** shows user-defined function status information in the namespace. (The language of the function is non-internal language.)
+
+**Table 1** PG_STAT_USER_FUNCTIONS columns
+
+| Name       | Type             | Description                                                  |
+| :--------- | :--------------- | :----------------------------------------------------------- |
+| funcid     | oid              | OID of a function                                            |
+| schemaname | name             | Schema name                                                  |
+| funcname   | name             | Function name                                                |
+| calls      | bigint           | Number of times the function has been called                 |
+| total_time | double precision | Total time spent in the function and all other functions called by it |
+| self_time  | double precision | Total time spent in the function itself, excluding other functions called by it |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_USER_INDEXES.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_USER_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..32e9d5258f584ccf41cf6015f647168357850f3f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_USER_INDEXES.md
@@ -0,0 +1,23 @@
+---
+title: PG_STAT_USER_INDEXES
+summary: PG_STAT_USER_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STAT_USER_INDEXES
+
+**PG_STAT_USER_INDEXES** displays information about the index status of user-defined ordinary tables and TOAST tables.
+
+**Table 1** PG_STAT_USER_INDEXES columns
+
+| Name          | Type   | Description                                                  |
+| :------------ | :----- | :----------------------------------------------------------- |
+| relid         | oid    | OID of the table for this index                              |
+| indexrelid    | oid    | OID of the index                                             |
+| schemaname    | name   | Name of the schema that the index is in                      |
+| relname       | name   | Name of the table for the index                              |
+| indexrelname  | name   | Index name                                                   |
+| idx_scan      | bigint | Number of index scans initiated on the index                 |
+| idx_tup_read  | bigint | Number of index entries returned by scans on the index       |
+| idx_tup_fetch | bigint | Number of live table rows fetched by simple index scans using the index |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_USER_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_USER_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..374a5e80175f8b3f1a823b911022e71cd82e0eee
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_USER_TABLES.md
@@ -0,0 +1,37 @@
+---
+title: PG_STAT_USER_TABLES
+summary: PG_STAT_USER_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STAT_USER_TABLES
+
+**PG_STAT_USER_TABLES** displays information about user-defined ordinary tables and TOAST tables in the namespaces.
+
+**Table 1** PG_STAT_USER_TABLES columns
+
+| Name              | Type                     | Description                                                  |
+| :---------------- | :----------------------- | :----------------------------------------------------------- |
+| relid             | oid                      | OID of the table                                             |
+| schemaname        | name                     | Name of the schema that the table is in                      |
+| relname           | name                     | Table name                                                   |
+| seq_scan          | bigint                   | Number of sequential scans initiated on the table            |
+| seq_tup_read      | bigint                   | Number of live rows fetched by sequential scans              |
+| idx_scan          | bigint                   | Number of index scans initiated on the table                 |
+| idx_tup_fetch     | bigint                   | Number of live rows fetched by index scans                   |
+| n_tup_ins         | bigint                   | Number of rows inserted                                      |
+| n_tup_upd         | bigint                   | Number of rows updated                                       |
+| n_tup_del         | bigint                   | Number of rows deleted                                       |
+| n_tup_hot_upd     | bigint                   | Number of rows HOT updated (with no separate index update required) |
+| n_live_tup        | bigint                   | Estimated number of live rows                                |
+| n_dead_tup        | bigint                   | Estimated number of dead rows                                |
+| last_vacuum       | timestamp with time zone | Last time at which the table was manually vacuumed (excluding **VACUUM FULL**) |
+| last_autovacuum   | timestamp with time zone | Last time at which the table was vacuumed by the autovacuum daemon |
+| last_analyze      | timestamp with time zone | Last time at which the table was manually analyzed           |
+| last_autoanalyze  | timestamp with time zone | Last time at which the table was analyzed by the autovacuum daemon |
+| vacuum_count      | bigint                   | Number of times the table has been manually vacuumed (not counting **VACUUM FULL**) |
+| autovacuum_count  | bigint                   | Number of times the table has been vacuumed by the autovacuum daemon |
+| analyze_count     | bigint                   | Number of times the table has been manually analyzed         |
+| autoanalyze_count | bigint                   | Number of times the table has been analyzed by the autovacuum daemon |
+| last_data_changed | timestamp with time zone | Last modification time of the table data                     |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_ALL_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_ALL_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..da2f01fa6507b6e549428dbd237a7295174fdc98
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_ALL_TABLES.md
@@ -0,0 +1,26 @@
+---
+title: PG_STAT_XACT_ALL_TABLES
+summary: PG_STAT_XACT_ALL_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STAT_XACT_ALL_TABLES
+
+**PG_STAT_XACT_ALL_TABLES** displays transaction status information about all ordinary tables and TOAST tables in the namespaces.
+
+**Table 1** PG_STAT_XACT_ALL_TABLES columns
+
+| Name          | Type   | Description                                                  |
+| :------------ | :----- | :----------------------------------------------------------- |
+| relid         | oid    | OID of the table                                             |
+| schemaname    | name   | Name of the schema that the table is in                      |
+| relname       | name   | Table name                                                   |
+| seq_scan      | bigint | Number of sequential scans initiated on the table            |
+| seq_tup_read  | bigint | Number of live rows fetched by sequential scans              |
+| idx_scan      | bigint | Number of index scans initiated on the table                 |
+| idx_tup_fetch | bigint | Number of live rows fetched by index scans                   |
+| n_tup_ins     | bigint | Number of rows inserted                                      |
+| n_tup_upd     | bigint | Number of rows updated                                       |
+| n_tup_del     | bigint | Number of rows deleted                                       |
+| n_tup_hot_upd | bigint | Number of rows HOT updated (with no separate index update required) |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_SYS_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_SYS_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..8d83a6c334816cc7f45c3cca87f5aa10177c4b69
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_SYS_TABLES.md
@@ -0,0 +1,26 @@
+---
+title: PG_STAT_XACT_SYS_TABLES
+summary: PG_STAT_XACT_SYS_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STAT_XACT_SYS_TABLES
+
+**PG_STAT_XACT_SYS_TABLES** displays transaction status information of the system catalog in the namespace.
+
+**Table 1** PG_STAT_XACT_SYS_TABLES columns
+
+| Name          | Type   | Description                                                  |
+| :------------ | :----- | :----------------------------------------------------------- |
+| relid         | oid    | OID of the table                                             |
+| schemaname    | name   | Name of the schema that the table is in                      |
+| relname       | name   | Table name                                                   |
+| seq_scan      | bigint | Number of sequential scans initiated on the table            |
+| seq_tup_read  | bigint | Number of live rows fetched by sequential scans              |
+| idx_scan      | bigint | Number of index scans initiated on the table                 |
+| idx_tup_fetch | bigint | Number of live rows fetched by index scans                   |
+| n_tup_ins     | bigint | Number of rows inserted                                      |
+| n_tup_upd     | bigint | Number of rows updated                                       |
+| n_tup_del     | bigint | Number of rows deleted                                       |
+| n_tup_hot_upd | bigint | Number of rows HOT updated (with no separate index update required) |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_USER_FUNCTIONS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_USER_FUNCTIONS.md
new file mode 100644
index 0000000000000000000000000000000000000000..0777bb4334a575ebbc02236f1838f53c203a6b1b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_USER_FUNCTIONS.md
@@ -0,0 +1,21 @@
+---
+title: PG_STAT_XACT_USER_FUNCTIONS
+summary: PG_STAT_XACT_USER_FUNCTIONS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STAT_XACT_USER_FUNCTIONS
+
+**PG_STAT_XACT_USER_FUNCTIONS** contains statistics on the execution of each function.
+
+**Table 1** PG_STAT_XACT_USER_FUNCTIONS columns
+
+| Name       | Type             | Description                                                  |
+| :--------- | :--------------- | :----------------------------------------------------------- |
+| funcid     | oid              | OID of a function                                            |
+| schemaname | name             | Schema name                                                  |
+| funcname   | name             | Function name                                                |
+| calls      | bigint           | Number of times the function has been called                 |
+| total_time | double precision | Total time spent in the function and all other functions called by it |
+| self_time  | double precision | Total time spent in the function itself, excluding other functions called by it |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_USER_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_USER_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..20b265a7373b6a0f3bfc8c2f3f8fb217a2117160
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_USER_TABLES.md
@@ -0,0 +1,26 @@
+---
+title: PG_STAT_XACT_USER_TABLES
+summary: PG_STAT_XACT_USER_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STAT_XACT_USER_TABLES
+
+**PG_STAT_XACT_USER_TABLES** displays transaction status information of the user table in the namespace.
+
+**Table 1** PG_STAT_XACT_USER_TABLES columns
+
+| Name          | Type   | Description                                                  |
+| :------------ | :----- | :----------------------------------------------------------- |
+| relid         | oid    | OID of the table                                             |
+| schemaname    | name   | Name of the schema that the table is in                      |
+| relname       | name   | Table name                                                   |
+| seq_scan      | bigint | Number of sequential scans initiated on the table            |
+| seq_tup_read  | bigint | Number of live rows fetched by sequential scans              |
+| idx_scan      | bigint | Number of index scans initiated on the table                 |
+| idx_tup_fetch | bigint | Number of live rows fetched by index scans                   |
+| n_tup_ins     | bigint | Number of rows inserted                                      |
+| n_tup_upd     | bigint | Number of rows updated                                       |
+| n_tup_del     | bigint | Number of rows deleted                                       |
+| n_tup_hot_upd | bigint | Number of rows HOT updated (with no separate index update required) |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TABLES.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..35b16bab1c8875d700ce9902f2dfda6626c77c29
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TABLES.md
@@ -0,0 +1,25 @@
+---
+title: PG_TABLES
+summary: PG_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_TABLES
+
+**PG_TABLES** provides access to each table in the database.
+
+**Table 1** PG_TABLES columns
+
+| Name          | Type                     | Reference                          | Description                                                  |
+| :------------ | :----------------------- | :--------------------------------- | :----------------------------------------------------------- |
+| schemaname    | name                     | PG_NAMESPACE.nspname               | Name of the schema that contains a table                     |
+| tablename     | name                     | PG_CLASS.relname                   | Table name                                                   |
+| tableowner    | name                     | pg_get_userbyid(PG_CLASS.relowner) | Table owner                                                  |
+| tablespace    | name                     | PG_TABLESPACE.spcname              | Tablespace that contains the table (default value:**null**) |
+| hasindexes    | Boolean                  | PG_CLASS.relhasindex               | The value is **true** if the table has (or recently had) an index; otherwise, the value is **false**. |
+| hasrules      | Boolean                  | PG_CLASS.relhasruls                | The value is **true** if the table has rules; otherwise, the value is **false**. |
+| hastriggers   | Boolean                  | PG_CLASS.RELHASTRIGGERS            | The value is **TRUE** if the table has triggers; otherwise, the value is **FALSE**. |
+| tablecreator  | name                     | pg_get_userbyid(po.creator)        | Table creator.                                               |
+| created       | timestamp with time zone | pg_object.ctime                    | Creation time of the object                                  |
+| last_ddl_time | timestamp with time zone | pg_object.mtime                    | Last modification time of the object                         |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TDE_INFO.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TDE_INFO.md
new file mode 100644
index 0000000000000000000000000000000000000000..e84405f0450100ff3c13d6a96e80c3bb71c1edd5
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TDE_INFO.md
@@ -0,0 +1,18 @@
+---
+title: PG_TDE_INFO
+summary: PG_TDE_INFO
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_TDE_INFO
+
+**PG_TDE_INFO** provides MogDB encryption information.
+
+**Table 1** PG_TDE_INFO columns
+
+| Name       | Type    | Description                                                  |
+| :--------- | :------ | :----------------------------------------------------------- |
+| is_encrypt | Boolean | Whether to enable MogDB encryption.<br/>- **f**: Non-encryption MogDB<br/>- **t**: Encryption MogDB |
+| g_tde_algo | text    | Encryption algorithm<br/>- SM4-CTR-128<br/>- AES-CTR-128     |
+| remain     | text    | This is reserved.                                            |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_THREAD_WAIT_STATUS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_THREAD_WAIT_STATUS.md
new file mode 100644
index 0000000000000000000000000000000000000000..c4c5df45b0a11927452374796956ba0e07a5a042
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_THREAD_WAIT_STATUS.md
@@ -0,0 +1,290 @@
+---
+title: PG_THREAD_WAIT_STATUS
+summary: PG_THREAD_WAIT_STATUS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_THREAD_WAIT_STATUS
+
+**PG_THREAD_WAIT_STATUS** allows you to test the block waiting status about the backend thread and auxiliary thread of the current instance.
+
+**Table 1** PG_THREAD_WAIT_STATUS columns
+
+| Name             | Type    | Description                                                  |
+| :--------------- | :------ | :----------------------------------------------------------- |
+| node_name        | text    | Current node name                                            |
+| db_name          | text    | Database name                                                |
+| thread_name      | text    | Thread name                                                  |
+| query_id         | bigint  | Query ID. The value of this column is the same as that of **debug_query_id**. |
+| tid              | bigint  | Current thread ID                                            |
+| sessionid        | bigint  | Current session ID                                           |
+| lwtid            | integer | Lightweight thread ID                                        |
+| psessionid       | bigint  | Parent session ID                                            |
+| tlevel           | integer | Level of the streaming thread                                |
+| smpid            | integer | Concurrent thread ID                                         |
+| wait_status      | text    | Waiting status of the current thread. For details about the waiting status, see [Table 2](#Waiting status list). |
+| wait_event       | text    | If **wait\_status** is **acquire lock**, **acquire lwlock**, or **wait io**, this column describes the lock, lightweight lock, and I/O information, respectively. If **wait\_status** is not any of the three values, this column is empty. |
+| locktag          | text    | Information about the lock that the current thread is waiting for |
+| lockmode         | text    | Lock mode that the current thread is waiting to obtain The values include modes in the table-level lock, row-level lock, and page-level lock. |
+| block_sessionid  | bigint  | ID of the session that blocks the current thread from obtaining the lock |
+| global_sessionid | text    | Global session ID                                            |
+
+The waiting statuses in the **wait\_status** column are as follows:
+
+**Table 2** Waiting status list<a id="Waiting status list"> </a>
+
+| Value                                   | Description                                                  |
+| :-------------------------------------- | :----------------------------------------------------------- |
+| none                                    | Waiting for no event                                         |
+| acquire lock                            | Waiting for locking until the locking succeeds or times out  |
+| acquire lwlock                          | Waiting for a lightweight lock                               |
+| wait io                                 | Waiting for I/O completion                                   |
+| wait cmd                                | Waiting for reading network communication packets to complete |
+| wait pooler get conn                    | Waiting for the pooler to obtain the connection              |
+| wait pooler abort conn                  | Waiting for the pooler to terminate the connection           |
+| wait pooler clean conn                  | Waiting for the pooler to clear connections                  |
+| pooler create conn: [nodename], total N | Waiting for the pooler to set up a connection. The connection is being established with the node specified by **nodename**, and there are *N* connections waiting to be set up. |
+| get conn                                | Obtaining the connection to other nodes                      |
+| set cmd: [nodename]                     | Waiting for running the **SET**, **RESET**, **TRANSACTION BLOCK LEVEL PARA SET**, or **SESSION LEVEL PARA SET** statement on the connection. The statement is being executed on the node specified by **nodename**. |
+| cancel query                            | Canceling the SQL statement that is being executed through the connection |
+| stop query                              | Stopping the query that is being executed through the connection |
+| wait node: nodename, total N, [phase]   | Waiting for receiving data from a connected node. The thread is waiting for data from the plevel thread of the node specified by **nodename**. The data of **N** connections is waiting to be returned. If **phase** is included, the possible phases are as follows:<br/>- **begin**: The transaction is being started.<br/>- **commit**: The transaction is being committed.<br/>- **rollback**: The transaction is being rolled back. |
+| wait transaction sync: xid              | Waiting for synchronizing the transaction specified by **xid** |
+| wait wal sync                           | Waiting for the completion of WAL of synchronization from the specified LSN to the standby instance |
+| wait data sync                          | Waiting for the completion of data page synchronization to the standby instance |
+| wait data sync queue                    | Waiting for putting the data pages that are in the row-store or the CU in the column-store into the synchronization queue |
+| flush data: nodename, [phase]           | Waiting for sending data to the plevel thread of the node specified by **nodename**. If **phase** is included, the possible phase is **wait quota**, indicating that the current communication flow is waiting for the quota value. |
+| stream get conn: [nodename], total N    | Waiting for connecting to the consumer object of the node specified by **nodename** when the stream flow is initialized. There are **N** consumers waiting to be connected. |
+| wait producer ready: nodename, total N  | Waiting for each producer to be ready when the stream flow is initialized. The thread is waiting for the procedure of the plevel thread on the **nodename** node to be ready. There are **N** producers waiting to be ready. |
+| synchronize quit                        | Waiting for the threads in the stream thread group to quit when the stream plan ends |
+| wait stream nodegroup destroy           | Waiting for destroying the stream node group when the stream plan ends |
+| wait active statement                   | Waiting for job execution under resource and load control    |
+| analyze: [relname], [phase]             | The thread is doing **ANALYZE** to the **relname** table. If **phase** is included, the possible phase is **autovacuum**, indicating that the database automatically enables the AutoVacuum thread to execute **ANALYZE**. |
+| vacuum: [relname], [phase]              | The thread is doing **VACUUM** to the **relname** table. If **phase** is included, the possible phase is **autovacuum**, indicating that the database automatically enables the AutoVacuum thread to execute **VACUUM**. |
+| vacuum full: [relname]                  | The thread is doing **VACUUM FULL** to the **relname** table. |
+| create index                            | An index is being created.                                   |
+| HashJoin - [ build hash \| write file ] | The **HashJoin** operator is being executed. In this phase, you need to pay attention to the execution time-consuming.<br/>- **build hash**: The **HashJoin** operator is creating a hash table.<br/>- **write file**: The **HashJoin** operator is writing data to disks. |
+| HashAgg - [ build hash \| write file ]  | The **HashAgg** operator is being executed. In this phase, you need to pay attention to the execution time-consuming.<br/>- **build hash**: The **HashAgg** operator is creating a hash table.<br/>- **write file**: The **HashAgg** operator is writing data to disks. |
+| HashSetop - [build hash \| write file ] | The **HashSetop** operator is being executed. In this phase, you need to pay attention to the execution time-consuming.<br/>- **build hash**: The **HashSetop** operator is creating a hash table.<br/>- **write file**: The **HashSetop** operator is writing data to disks. |
+| Sort \| Sort - write file               | The **Sort** operator is being executed. **write file** indicates that the **Sort** operator is writing data to disks. |
+| Material \| Material - write file       | The **Material** operator is being executed. **write file** indicates that the **Material** operator is writing data to disks. |
+| NestLoop                                | The **NestLoop** operator is being executed.                 |
+| wait memory                             | Waiting for obtaining the memory                             |
+| wait sync consumer next step            | Waiting for the consumer to execute the stream operator      |
+| wait sync producer next step            | Waiting for the producer to execute the stream operator      |
+
+If **wait\_status** is **acquire lwlock**, **acquire lock**, or **wait io**, there is an event performing I/O operations or waiting for obtaining the corresponding lightweight lock or transaction lock.
+
+The following table describes the corresponding wait events when **wait\_status** is **acquire lwlock**. If **wait_event** is **extension**, the lightweight lock is dynamically allocated and is not monitored.
+
+**Table 3** List of wait events corresponding to lightweight locks
+
+| wait_event                               | Description                                                  |
+| :--------------------------------------- | :----------------------------------------------------------- |
+| ShmemIndexLock                           | Used to protect the primary index table, a hash table, in shared memory. |
+| OidGenLock                               | Used to prevent different threads from generating the same OID. |
+| XidGenLock                               | Used to prevent two transactions from obtaining the same transaction ID. |
+| ProcArrayLock                            | Used to prevent concurrent access to or concurrent modification on ProcArray shared arrays. |
+| SInvalReadLock                           | Used to prevent concurrent execution with invalid message deletion. |
+| SInvalWriteLock                          | Used to prevent concurrent execution with invalid message write and deletion. |
+| WALInsertLock                            | Used to prevent concurrent execution with WAL insertion.     |
+| WALWriteLock                             | Used to prevent concurrent write from a WAL buffer to a disk. |
+| ControlFileLock                          | Used to prevent concurrent read/write or concurrent write/write on the **pg_control** file. |
+| CheckpointLock                           | Used to prevent multi-checkpoint concurrent execution.       |
+| CLogControlLock                          | Used to prevent concurrent access to or concurrent modification on the Clog control data structure. |
+| SubtransControlLock                      | Used to prevent concurrent access to or concurrent modification on the subtransaction control data structure. |
+| MultiXactGenLock                         | Used to allocate a unique MultiXact ID in serial mode.       |
+| MultiXactOffsetControlLock               | Used to prevent concurrent read/write or concurrent write/write on **pg_multixact/offset**. |
+| MultiXactMemberControlLock               | Used to prevent concurrent read/write or concurrent write/write on **pg_multixact/members**. |
+| RelCacheInitLock                         | Used to add a lock before any operations are performed on the **init** file when messages are invalid. |
+| CheckpointerCommLock                     | Used to send file flush requests to a checkpointer. The request structure needs to be inserted to a request queue in serial mode. |
+| TwoPhaseStateLock                        | Used to prevent concurrent access to or modification on two-phase information sharing arrays. |
+| TablespaceCreateLock                     | Used to check whether a tablespace already exists.           |
+| BtreeVacuumLock                          | Used to prevent **VACUUM** from clearing pages that are being used by B-tree indexes. |
+| AutovacuumLock                           | Used to access the autovacuum worker array in serial mode.   |
+| AutovacuumScheduleLock                   | Used to distribute tables requiring **VACUUM** in serial mode. |
+| AutoanalyzeLock                          | Used to obtain and release resources related to a task that allows for autoanalyze execution. |
+| SyncScanLock                             | Used to determine the start position of a relfilenode during heap scanning. |
+| NodeTableLock                            | Used to protect a shared structure that stores database node information. |
+| PoolerLock                               | Used to prevent two threads from simultaneously obtaining the same connection from a connection pool. |
+| RelationMappingLock                      | Used to wait for the mapping file between system catalogs and storage locations to be updated. |
+| AsyncCtlLock                             | Used to prevent concurrent access to or concurrent modification on the sharing notification status. |
+| AsyncQueueLock                           | Used to prevent concurrent access to or concurrent modification on the sharing notification queue. |
+| SerializableXactHashLock                 | Used to prevent concurrent read/write or concurrent write/write on a sharing structure for serializable transactions. |
+| SerializableFinishedListLock             | Used to prevent concurrent read/write or concurrent write/write on a shared linked list for completed serial transactions. |
+| SerializablePredicateLockListLock        | Used to protect a linked list of serializable transactions that have locks. |
+| OldSerXidLock                            | Used to protect a structure that records serializable transactions that have conflicts. |
+| FileStatLock                             | Used to protect a data structure that stores statistics file information. |
+| SyncRepLock                              | Used to protect Xlog synchronization information during primary/standby replication. |
+| DataSyncRepLock                          | Used to protect data page synchronization information during primary/standby replication. |
+| CStoreColspaceCacheLock                  | Used to add a lock when CU space is allocated for a column-store table. |
+| CStoreCUCacheSweepLock                   | Used to add a lock when CU caches used by a column-store table are cyclically washed out. |
+| MetaCacheSweepLock                       | Used to add a lock when metadata is cyclically washed out.   |
+| ExtensionConnectorLibLock                | Adds a lock when a specific dynamic library is loaded or uninstalled in ODBC connection initialization scenarios. |
+| SearchServerLibLock                      | Used to add a lock on the file read operation when a specific dynamic library is initially loaded in GPU-accelerated scenarios. |
+| LsnXlogChkFileLock                       | Used to serially update the Xlog flush points for primary and standby servers recorded in a specific structure. |
+| ReplicationSlotAllocationLock            | Used to add a lock when a primary server allocates stream replication slots during primary/standby replication. |
+| ReplicationSlotControlLock               | Used to prevent concurrent update of stream replication slot status during primary/standby replication. |
+| ResourcePoolHashLock                     | Used to prevent concurrent access to or concurrent modification on a resource pool table, a hash table. |
+| WorkloadStatHashLock                     | Used to prevent concurrent access to or concurrent modification on a hash table that contains SQL requests from the primary node of the database side. |
+| WorkloadIoStatHashLock                   | Used to prevent concurrent access to or concurrent modification on a hash table that contains I/O information of the current database node. |
+| WorkloadCGroupHashLock                   | Used to prevent concurrent access to or concurrent modification on a hash table that contains Cgroup information. |
+| OBSGetPathLock                           | Used to prevent concurrent read/write or concurrent write/write on an OBS path. |
+| WorkloadUserInfoLock                     | Used to prevent concurrent access to or concurrent modification on a hash table that contains user information about load management. |
+| WorkloadRecordLock                       | Used to prevent concurrent access to or concurrent modification on a hash table that contains requests received by the primary node of the databases during adaptive memory management. |
+| WorkloadIOUtilLock                       | Used to protect a structure that records **iostat** and CPU load information. |
+| WorkloadNodeGroupLock                    | Used to prevent concurrent access to or concurrent modification on a hash table that contains node group information in memory. |
+| JobShmemLock                             | Used to protect global variables in the shared memory that is periodically read during a scheduled task. |
+| OBSRuntimeLock                           | Used to obtain environment variables, for example, **GASSHOME**. |
+| LLVMDumpIRLock                           | Used to export the assembly language for dynamically generating functions. |
+| LLVMParseIRLock                          | Used to compile and parse a finished IR function from the IR file at the start position of a query. |
+| CriticalCacheBuildLock                   | Used to load caches from a shared or local cache initialization file. |
+| WaitCountHashLock                        | Used to protect a shared structure in user statement counting scenarios. |
+| BufMappingLock                           | Used to protect operations on a shared-buffer mapping table. |
+| LockMgrLock                              | Used to protect the information about a common lock structure. |
+| PredicateLockMgrLock                     | Used to protect the information about a lock structure that has serializable transactions. |
+| OperatorRealTLock                        | Used to prevent concurrent access to or concurrent modification on a global structure that contains real-time data at the operator level. |
+| OperatorHistLock                         | Used to prevent concurrent access to or concurrent modification on a global structure that contains historical data at the operator level. |
+| SessionRealTLock                         | Used to prevent concurrent access to or concurrent modification on a global structure that contains real-time data at the query level. |
+| SessionHistLock                          | Used to prevent concurrent access to or concurrent modification on a global structure that contains historical data at the query level. |
+| CacheSlotMappingLock                     | Used to protect global CU cache information.                 |
+| BarrierLock                              | Used to ensure that only one thread is creating a barrier at a time. |
+| dummyServerInfoCacheLock                 | Used to protect a global hash table where the information about MogDB connections is cached. |
+| RPNumberLock                             | Used by a database node on a computing MogDB to count the number of threads for a task where plans are being executed. |
+| ClusterRPLock                            | Used to control concurrent access on MogDB load data maintained in a CCN of MogDB. |
+| CBMParseXlogLock                         | Used to protect the lock used when CBM parses Xlogs.         |
+| RelfilenodeReuseLock                     | Used to prevent the link to a reused column attribute file from being canceled by mistake. |
+| RcvWriteLock                             | Used to prevent concurrent call of **WalDataRcvWrite**.      |
+| PercentileLock                           | Used to protect global percentile buffers.                   |
+| CSNBufMappingLock                        | Used to protect CSN pages.                                   |
+| UniqueSQLMappingLock                     | Used to protect a unique SQL hash table.                     |
+| DelayDDLLock                             | Used to prevent concurrent DDL operations.                   |
+| CLOG Ctl                                 | Used to prevent concurrent access to or concurrent modification on the Clog control data structure. |
+| Async Ctl                                | Used to protect asynchronization buffers.                    |
+| MultiXactOffset Ctl                      | Used to protect SLRU buffers of a MultiXact offset.          |
+| MultiXactMember Ctl                      | Used to protect SLRU buffer of a MultiXact member.           |
+| OldSerXid SLRU Ctl                       | Used to protect SLRU buffers of old transaction IDs.         |
+| ReplicationSlotLock                      | Used to protect a replication slot.                          |
+| PGPROCLock                               | Used to protect the PGPROC structure.                        |
+| MetaCacheLock                            | Used to protect meta caches.                                 |
+| DataCacheLock                            | Used to protect data caches.                                 |
+| InstrUserLock                            | Used to protect a user hash table.                           |
+| BadBlockStatHashLock                     | Used to protect the hash table **global_bad_block_stat**     |
+| BufFreelistLock                          | Used to ensure the atomicity of free list operations in the shared buffer. |
+| CUSlotListLock                           | Used to control concurrent operations on the slot of the column-store buffer. |
+| AddinShmemInitLock                       | Used to protect the initialization of the shared memory object. |
+| AlterPortLock                            | Used to protect the coordinator node from changing the registration port number. |
+| FdwPartitionCaheLock                     | Management lock of the buffer of the HDFS partitioned table. |
+| DfsConnectorCacheLock                    | Management lock of the DFSConnector buffer.                  |
+| DfsSpaceCacheLock                        | Management lock of the HDFS tablespace management buffer.    |
+| FullBuildXlogCopyStartPtrLock            | Used to protect Xlog copy operations in the full build.      |
+| DfsUserLoginLock                         | Used for HDFS user login and authentication.                 |
+| LogicalReplicationSlotPersistentDataLock | Used to protect data in the replication slot during logical replication. |
+| WorkloadSessionInfoLock                  | Used to protect the access to the session info memory hash table of the load management module. |
+| InstrWorkloadLock                        | Used to protect the access to the memory hash table that stores load management statistics. |
+| PgfdwLock                                | Used by the management instance to establish a connection to the foreign server. |
+| InstanceTimeLock                         | Used to obtain time information of sessions in an instance.  |
+| XlogRemoveSegLock                        | Used to protect Xlog segment file recycling.                 |
+| DnUsedSpaceHashLock                      | Used to update space usage information corresponding to a session. |
+| CsnMinLock                               | Used to calculate CSNmin.                                    |
+| GPCCommitLock                            | Used to protect the addition of the global Plan Cache hash table. |
+| GPCClearLock                             | Used to protect the clearing of the global plan cache hash table. |
+| GPCTimelineLock                          | Used to protect the timeline check of the global plan cache hash table. |
+| TsTagsCacheLock                          | Used to manage the time series tag cache.                    |
+| InstanceRealTLock                        | Used to protect the update of the hash table that stores shared instance statistics. |
+| CLogBufMappingLock                       | Used to manage the cache of commit logs.                     |
+| GPCMappingLock                           | Used to manage the global plan cache.                        |
+| GPCPrepareMappingLock                    | Used to manage the global plan cache.                        |
+| BufferIOLock                             | Used to protect I/O operations on pages in the shared buffer. |
+| BufferContentLock                        | Used to protect the read and modification of the page content in the shared buffer. |
+| CSNLOG Ctl                               | Used for CSN log management.                                 |
+| DoubleWriteLock                          | Used to manage doublewrite operations.                       |
+| RowPageReplicationLock                   | Used to manage data page replication of row-store.           |
+| extension                                | Other lightweight locks                                      |
+
+The following table describes the corresponding wait events when **wait\_status** is **wait io**.
+
+**Table 4** List of wait events corresponding to I/Os
+
+| wait_event                 | Description                                                  |
+| :------------------------- | :----------------------------------------------------------- |
+| BufFileRead                | Reads data from a temporary file to a specified buffer.      |
+| BufFileWrite               | Writes the content of a specified buffer to a temporary file. |
+| ControlFileRead            | Reads the **pg_control** file, mainly during database startup, checkpoint execution, and primary/standby verification. |
+| ControlFileSync            | Flushes the **pg_control** file to a disk, mainly during database initialization. |
+| ControlFileSyncUpdate      | Flushes the **pg_control** file to a disk, mainly during database startup, checkpoint execution, and primary/standby verification. |
+| ControlFileWrite           | Writes the **pg_control** file, mainly during database initialization. |
+| ControlFileWriteUpdate     | Updates the **pg_control** file, mainly during database startup, checkpoint execution, and primary/standby verification. |
+| CopyFileRead               | Reads a file during file copying.                            |
+| CopyFileWrite              | Writes a file during file copying.                           |
+| DataFileExtend             | Writes a file during file extension.                         |
+| DataFileFlush              | Flushes a table data file to a disk.                         |
+| DataFileImmediateSync      | Flushes a table data file to a disk immediately.             |
+| DataFilePrefetch           | Reads a table data file asynchronously.                      |
+| DataFileRead               | Reads a table data file synchronously.                       |
+| DataFileSync               | Flushes table data file modifications to a disk.             |
+| DataFileTruncate           | Truncates a table data file.                                 |
+| DataFileWrite              | Writes a table data file.                                    |
+| LockFileAddToDataDirRead   | Reads the **postmaster.pid** file.                           |
+| LockFileAddToDataDirSync   | Flushes the **postmaster.pid** file to a disk.               |
+| LockFileAddToDataDirWrite  | Writes PID information into the **postmaster.pid** file.     |
+| LockFileCreateRead         | Read the LockFile file **%s.lock**.                          |
+| LockFileCreateSync         | Flushes the LockFile file **%s.lock** to a disk.             |
+| LockFileCreateWRITE        | Writes PID information into the LockFile file **%s.lock**.   |
+| RelationMapRead            | Reads the mapping file between system catalogs and storage locations. |
+| RelationMapSync            | Flushes the mapping file between system catalogs and storage locations to a disk. |
+| RelationMapWrite           | Writes the mapping file between system catalogs and storage locations. |
+| ReplicationSlotRead        | Reads a stream replication slot file during a restart.       |
+| ReplicationSlotRestoreSync | Flushes a stream replication slot file to a disk during a restart. |
+| ReplicationSlotSync        | Flushes a temporary stream replication slot file to a disk during checkpoint execution. |
+| ReplicationSlotWrite       | Writes a temporary stream replication slot file during checkpoint execution. |
+| SLRUFlushSync              | Flushes the **pg_clog**, **pg_subtrans**, and **pg_multixact** files to a disk, mainly during checkpoint execution and database shutdown. |
+| SLRURead                   | Reads the **pg_clog**, **pg_subtrans**, and **pg_multixact** files. |
+| SLRUSync                   | Writes dirty pages into the **pg_clog**, **pg_subtrans**, and **pg_multixact** files, and flushes the files to a disk, mainly during checkpoint execution and database shutdown. |
+| SLRUWrite                  | Writes the **pg_clog**, **pg_subtrans**, and **pg_multixact** files. |
+| TimelineHistoryRead        | Reads the timeline history file during database startup.     |
+| TimelineHistorySync        | Flushes the timeline history file to a disk during database startup. |
+| TimelineHistoryWrite       | Writes to the timeline history file during database startup. |
+| TwophaseFileRead           | Reads the **pg_twophase** file, mainly during two-phase transaction commit and restoration. |
+| TwophaseFileSync           | Flushes the **pg_twophase** file to a disk, mainly during two-phase transaction commit and restoration. |
+| TwophaseFileWrite          | Writes the **pg_twophase** file, mainly during two-phase transaction commit and restoration. |
+| WALBootstrapSync           | Flushes an initialized WAL file to a disk during database initialization. |
+| WALBootstrapWrite          | Writes an initialized WAL file during database initialization. |
+| WALCopyRead                | Read operation generated when an existing WAL file is read for replication after archiving and restoration. |
+| WALCopySync                | Flushes a replicated WAL file to a disk after archiving and restoration. |
+| WALCopyWrite               | Write operation generated when an existing WAL file is read for replication after archiving and restoration. |
+| WALInitSync                | Flushes a newly initialized WAL file to a disk during log reclaiming or writing. |
+| WALInitWrite               | Initializes a newly created WAL file to **0** during log reclaiming or writing. |
+| WALRead                    | Reads data from Xlogs during redo operations on two-phase files. |
+| WALSyncMethodAssign        | Flushes all open WAL files to a disk.                        |
+| WALWrite                   | Writes a WAL file.                                           |
+| WALBufferAccess            | WAL Buffer access (for performance reasons, only the number of accesses are counted in the kernel code, and the access time is not counted). |
+| WALBufferFull              | When the WAL Buffer is full, write wal file related processing. |
+| DoubleWriteFileRead        | Doublewrites and reads a file.                               |
+| DoubleWriteFileSync        | Doublewrites a file and forcibly flushes files to disks.     |
+| DoubleWriteFileWrite       | Doublewrites a file and writes a file.                       |
+| PredoProcessPending        | Waits for the playback of other records to complete during parallel log playback. |
+| PredoApply                 | Waits for other threads to play back logs to the LSN of the current thread during parallel log playback. |
+| DisableConnectFileRead     | Reads the HA lock fragment logic file.                       |
+| DisableConnectFileSync     | Forcibly flushes the HA lock fragment logic file to disks.   |
+| DisableConnectFileWrite    | Writes the HA lock fragment logic file.                      |
+
+The following table describes the corresponding wait events when **wait\_status** is **acquire lock**.
+
+**Table 5** List of wait events corresponding to transaction locks
+
+| wait_event       | Description                                        |
+| :--------------- | :------------------------------------------------- |
+| relation         | Adds a lock to a table.                            |
+| extend           | Adds a lock to a table being scaled out.           |
+| partition        | Adds a lock to a partitioned table.                |
+| partition_seq    | Adds a lock to a partition of a partitioned table. |
+| page             | Adds a lock to a table page.                       |
+| tuple            | Adds a lock to a tuple on a page.                  |
+| transactionid    | Adds a lock to a transaction ID.                   |
+| virtualxid       | Adds a lock to a virtual transaction ID.           |
+| object           | Adds a lock to an object.                          |
+| cstore_freespace | Adds a lock to idle column-store space.            |
+| userlock         | Adds a lock to a user.                             |
+| advisory         | Adds an advisory lock.                             |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TIMEZONE_ABBREVS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TIMEZONE_ABBREVS.md
new file mode 100644
index 0000000000000000000000000000000000000000..dce658f4119db688f3f485ad8c335ad4ea451d77
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TIMEZONE_ABBREVS.md
@@ -0,0 +1,18 @@
+---
+title: PG_TIMEZONE_ABBREVS
+summary: PG_TIMEZONE_ABBREVS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_TIMEZONE_ABBREVS
+
+**PG_TIMEZONE_ABBREVS** displays information about all available time zones.
+
+**Table 1** PG_TIMEZONE_ABBREVS columns
+
+| Name       | Type     | Description                                                  |
+| :--------- | :------- | :----------------------------------------------------------- |
+| abbrev     | text     | Time zone name abbreviation                                  |
+| utc_offset | interval | Offset from UTC                                              |
+| is_dst     | Boolean  | Whether DST is used. If DST is used, the value is **true**. Otherwise, the value is **false**. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TIMEZONE_NAMES.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TIMEZONE_NAMES.md
new file mode 100644
index 0000000000000000000000000000000000000000..e1ad52ae93ee7d129d01fe513554ed338525074b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TIMEZONE_NAMES.md
@@ -0,0 +1,19 @@
+---
+title: PG_TIMEZONE_NAMES
+summary: PG_TIMEZONE_NAMES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_TIMEZONE_NAMES
+
+**PG_TIMEZONE_NAMES** provides all time zone names that can be recognized by **SET TIMEZONE**, along with their abbreviations, UTC offsets, and daylight saving time (DST) statuses.
+
+**Table 1** PG_TIMEZONE_NAMES columns
+
+| Name       | Type     | Description                                                  |
+| :--------- | :------- | :----------------------------------------------------------- |
+| name       | text     | Name of the time zone                                        |
+| abbrev     | text     | Abbreviation of the ime zone name                            |
+| utc_offset | interval | Offset from UTC                                              |
+| is_dst     | Boolean  | Whether DST is used. If DST is used, the value is **true**. Otherwise, the value is **false**. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TOTAL_MEMORY_DETAIL.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TOTAL_MEMORY_DETAIL.md
new file mode 100644
index 0000000000000000000000000000000000000000..ff15361a6db5db5684a35c2ea8ddff1ce70c1890
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TOTAL_MEMORY_DETAIL.md
@@ -0,0 +1,18 @@
+---
+title: PG_TOTAL_MEMORY_DETAIL
+summary: PG_TOTAL_MEMORY_DETAIL
+author: Guo Huan
+date: 2021-06-15
+---
+
+# PG_TOTAL_MEMORY_DETAIL
+
+**PG_TOTAL_MEMORY_DETAIL** displays memory usage of a node in the database.
+
+**Table 1** PG_TOTAL_MEMORY_DETAIL columns
+
+| Name         | Type    | Description                                |
+| :----------- | :------ | :----------------------------------------- |
+| nodename     | text    | Specifies the node name.                   |
+| memorytype   | text    | Memory name                                |
+| memorymbytes | integer | Size of the used memory in the unit of MB. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TOTAL_USER_RESOURCE_INFO.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TOTAL_USER_RESOURCE_INFO.md
new file mode 100644
index 0000000000000000000000000000000000000000..75f2538230ff5fd06c61b194fd500dbd97efe64d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TOTAL_USER_RESOURCE_INFO.md
@@ -0,0 +1,32 @@
+---
+title: PG_TOTAL_USER_RESOURCE_INFO
+summary: PG_TOTAL_USER_RESOURCE_INFO
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_TOTAL_USER_RESOURCE_INFO
+
+**PG_TOTAL_USER_RESOURCE_INFO** displays resource usage of all users. Only administrators can query this view. This view is valid only when use_workload_manager is set to **on**. I/O monitoring items are valid only when **enable_logical_io_statistics** is set to **on**.
+
+**Table 1** PG_TOTAL_USER_RESOURCE_INFO columns
+
+| Name              | Type             | Description                                                  |
+| :---------------- | :--------------- | :----------------------------------------------------------- |
+| username          | name             | Username                                                     |
+| used_memory       | integer          | Used memory, in MB                                           |
+| total_memory      | integer          | Available memory, in MB. The value **0** indicates that the available memory is not limited and depends on the maximum memory available in the database. |
+| used_cpu          | double precision | Number of CPU cores in use. CPU usage data is collected only in complex jobs, and the value is the CPU usage of the related Cgroup. |
+| total_cpu         | integer          | Total number of CPU cores of the Cgroup associated with the user on the node |
+| used_space        | bigint           | Used permanent table storage space, in KB                    |
+| total_space       | bigint           | Available permanent table storage space, in KB (**-1** if the storage space is not limited) |
+| used_temp_space   | bigint           | Used temporary space, in KB                                  |
+| total_temp_space  | bigint           | Total available temporary space, in KB (**-1** if the temporary space is not limited) |
+| used_spill_space  | bigint           | Size of the used operator flushing space, in KB              |
+| total_spill_space | bigint           | Total size of the available operator flushing space, in KB (**-1** if the space is not limited) |
+| read_kbytes       | bigint           | Primary database node: total bytes read by the user's complex jobs on all database nodes in the last 5 seconds, in KB<br/>Database node: total bytes read by the user's complex jobs from the instance startup time to the current time, in KB |
+| write_kbytes      | bigint           | Primary database node: total bytes written by the user's complex jobs on all database nodes in the last 5 seconds, in KB<br/>Database node: total bytes written by the user's complex jobs from the instance startup time to the current time, in KB |
+| read_counts       | bigint           | Primary database node: total number of read times of the user's complex jobs on all database nodes in the last 5 seconds<br/>Database node: total number of read times of the user's complex jobs from the instance startup time to the current time |
+| write_counts      | bigint           | Primary database node: total number of write times of the user's complex jobs on all database nodes in the last 5 seconds<br/>Database node: total number of write times of the user's complex jobs from the instance startup time to the current time |
+| read_speed        | double precision | Primary database node: average read rate of the user's complex jobs on a single database node in the last 5 seconds, in KB/s<br/>Database node: average read rate of the user's complex jobs on the database node in the last 5 seconds, in KB/s |
+| write_speed       | double precision | Primary database node: average write rate of the user's complex jobs on a single database node in the last 5 seconds, in KB/s<br/>Database node: average write rate of the user's complex jobs on the database node in the last 5 seconds, in KB/s |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TOTAL_USER_RESOURCE_INFO_OID.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TOTAL_USER_RESOURCE_INFO_OID.md
new file mode 100644
index 0000000000000000000000000000000000000000..d9ccc8b0447467c9077c9a0d84c07aca90985683
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TOTAL_USER_RESOURCE_INFO_OID.md
@@ -0,0 +1,32 @@
+---
+title: PG_TOTAL_USER_RESOURCE_INFO_OID
+summary: PG_TOTAL_USER_RESOURCE_INFO_OID
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_TOTAL_USER_RESOURCE_INFO_OID
+
+**PG_TOTAL_USER_RESOURCE_INFO_OID** displays resource usage of all users. Only administrators can query this view. This view is valid only when **use_workload_manager** is set to **on**.
+
+**Table 1** PG_TOTAL_USER_RESOURCE_INFO_OID columns
+
+| Name              | Type             | Description                                                  |
+| :---------------- | :--------------- | :----------------------------------------------------------- |
+| userid            | oid              | User ID.                                                     |
+| used_memory       | integer          | Size of the memory being used, in MB.                        |
+| total_memory      | integer          | Available memory (unit: MB) The value **0** indicates that the available memory is not limited and depends on the maximum memory available in the database. |
+| used_cpu          | double precision | Number of CPU cores in use.                                  |
+| total_cpu         | integer          | Total number of CPU cores of the Cgroup associated with the user on the node. |
+| used_space        | bigint           | Used storage space, in KB.                                   |
+| total_space       | bigint           | Available storage space (unit: KB). The value **-1** indicates that the space is not limited. |
+| used_temp_space   | bigint           | Used temporary storage space, in KB.                         |
+| total_temp_space  | bigint           | Total available temporary space, in KB (**-1** if the temporary space is not limited). |
+| used_spill_space  | bigint           | Used disk space for spilling, in KB.                         |
+| total_spill_space | bigint           | Total available disk space for spilling, in KB. The value **-1** indicates that the space is not limited. |
+| read_kbytes       | bigint           | Amount of data read from the disk, in KB.                    |
+| write_kbytes      | bigint           | Amount of data written to the disk, in KB.                   |
+| read_counts       | bigint           | Number of disk read times.                                   |
+| write_counts      | bigint           | Number of disk write times.                                  |
+| read_speed        | double precision | Disk read rate, in B/ms.                                     |
+| write_speed       | double precision | Disk write rate, in B/ms.                                    |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_USER.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_USER.md
new file mode 100644
index 0000000000000000000000000000000000000000..f226e2d200aee06efe9333c57dfe57b8def905af
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_USER.md
@@ -0,0 +1,31 @@
+---
+title: PG_USER
+summary: PG_USER
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_USER
+
+**PG_USER** provides information about database users. By default, only the initial user and users with the sysadmin attribute can view the information. Other users can view the information only after being granted permissions.
+
+**Table 1** PG_USER columns
+
+| Name            | Type                     | Description                                                  |
+| :-------------- | :----------------------- | :----------------------------------------------------------- |
+| usename         | name                     | Username                                                     |
+| usesysid        | oid                      | ID of this user                                              |
+| usecreatedb     | Boolean                  | Whether the user has the permissions to create databases     |
+| usesuper        | Boolean                  | whether the user is the initial system administrator with the highest rights |
+| usecatupd       | Boolean                  | whether the user can directly update system tables. Only the initial system administrator whose **usesysid** is **10** has this permission. It is unavailable for other users. |
+| userepl         | Boolean                  | Whether the user has the permissions to duplicate data streams |
+| passwd          | text                     | Encrypted user password. The value is displayed as \*\*\*\*\*\*\*\*. |
+| valbegin        | timestamp with time zone | Start time for account validity (**null** if no start time)  |
+| valuntil        | timestamp with time zone | End time for account validity (**null** if no end time)      |
+| respool         | name                     | Resource pool where the user is in                           |
+| parent          | oid                      | Parent user OID                                              |
+| spacelimit      | text                     | Storage space of the permanent table                         |
+| tempspacelimit  | text                     | Storage space of the temporary table                         |
+| spillspacelimit | text                     | Operator disk flushing space                                 |
+| useconfig       | text[]                   | Session defaults for runtime configuration variables         |
+| nodegroup       | name                     | Name of the logical MogDB associated with the user. If the user does not manage the logical MogDB, this parameter is left blank. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_USER_MAPPINGS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_USER_MAPPINGS.md
new file mode 100644
index 0000000000000000000000000000000000000000..547e388b9717427b8059a060e831ba13b75e4322
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_USER_MAPPINGS.md
@@ -0,0 +1,23 @@
+---
+title: PG_USER_MAPPINGS
+summary: PG_USER_MAPPINGS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_USER_MAPPINGS
+
+**PG_USER_MAPPINGS** provides access to information about user mappings.
+
+This is essentially a publicly readable view of PG_USER_MAPPING that leaves out the options column if the user has no rights to use it. Common users must be authorized to access this view.
+
+**Table 1** PG_USER_MAPPINGS columns
+
+| Name      | Type    | Reference                 | Description                                                  |
+| :-------- | :------ | :------------------------ | :----------------------------------------------------------- |
+| umid      | oid     | PG_USER_MAPPING.oid       | OID of the user mapping                                      |
+| srvid     | oid     | PG_FOREIGN_SERVER.oid     | OID of the foreign server that contains the mapping          |
+| srvname   | name    | PG_FOREIGN_SERVER.srvname | Name of the foreign server                                   |
+| umuser    | oid     | PG_AUTHID.oid             | OID of the local role being mapped (**0** if the user mapping is public) |
+| usename   | name    | -                         | Name of the local user to be mapped                          |
+| umoptions | text[ ] | -                         | User mapping specific options. If the current user is the owner of the foreign server, the value is **keyword=value strings**. Otherwise, the value is **null**. |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_VARIABLE_INFO.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_VARIABLE_INFO.md
new file mode 100644
index 0000000000000000000000000000000000000000..33cffaae79bc565aabcfdc24d3969362eb67f994
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_VARIABLE_INFO.md
@@ -0,0 +1,26 @@
+---
+title: PG_VARIABLE_INFO
+summary: PG_VARIABLE_INFO
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_VARIABLE_INFO
+
+**PGXC_VARIABLE_INFO** records information about transaction IDs and OIDs of the current node in openGauss.
+
+**Table 1** PG_VARIABLE_INFO columns
+
+| Name                     | Type | Description                                                  |
+| :----------------------- | :--- | :----------------------------------------------------------- |
+| node_name                | text | Node name                                                    |
+| next_oid                 | oid  | OID generated next time for the node                         |
+| next_xid                 | xid  | Transaction ID generated next time for the node              |
+| oldest_xid               | xid  | Oldest transaction ID on the node                            |
+| xid_vac_limit            | xid  | Critical point (transaction ID) that triggers forcible autovacuum |
+| oldest_xid_db            | oid  | OID of the database that has the minimum datafrozenxid on the node |
+| last_extend_csn_logpage  | xid  | Number of the last extended csnlog page                      |
+| start_extend_csn_logpage | xid  | Number of the page from which csnlog extending starts        |
+| next_commit_seqno        | xid  | CSN generated next time for the node                         |
+| latest_completed_xid     | xid  | Latest transaction ID on the node after the transaction commission or rollback |
+| startup_max_xid          | xid  | Last transaction ID before the node is powered off           |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_VIEWS.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_VIEWS.md
new file mode 100644
index 0000000000000000000000000000000000000000..afeca9ff9691ba81db1d0536f3147f214bbafb98
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_VIEWS.md
@@ -0,0 +1,19 @@
+---
+title: PG_VIEWS
+summary: PG_VIEWS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_VIEWS
+
+**PG_VIEWS** provides access to basic information about each view in the database.
+
+**Table 1** PG_VIEWS columns
+
+| Name       | Type | Reference            | Description                               |
+| :--------- | :--- | :------------------- | :---------------------------------------- |
+| schemaname | name | PG_NAMESPACE.nspname | Name of the schema that contains the view |
+| viewname   | name | PG_CLASS.relname     | View name                                 |
+| viewowner  | name | PG_AUTHID.Erolname   | Owner of the view                         |
+| definition | text | -                    | Definition of the view                    |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PLAN_TABLE.md b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PLAN_TABLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..5bad937edf1bcf5a3510f6bf20e556e416c3b0ba
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PLAN_TABLE.md
@@ -0,0 +1,31 @@
+---
+title: PLAN_TABLE
+summary: PLAN_TABLE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PLAN_TABLE
+
+**PLAN_TABLE** displays plan information collected by **EXPLAIN PLAN**. Plan information is in a session-level lifecycle. After a session exits, the data will be deleted. Data is isolated between sessions and between users.
+
+**Table 1** PLAN_TABLE columns
+
+| Name         | Type           | Description                                                  |
+| :----------- | :------------- | :----------------------------------------------------------- |
+| statement_id | varchar2(30)   | Query tag specified by a user                                |
+| plan_id      | bigint         | Query ID                                                     |
+| id           | int            | ID of each operator in a generated plan                      |
+| operation    | varchar2(30)   | Operation description of an operator in a plan               |
+| options      | varchar2(255)  | Operation action                                             |
+| object_name  | name           | Object name corresponding to the operation, which is not the object alias used in the query. The object name is defined by users. |
+| object_type  | varchar2(30)   | Object type                                                  |
+| object_owner | name           | Schema to which the object belongs. It is defined by users.  |
+| projection   | varchar2(4000) | Returned column information                                  |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - A valid **object_type** value consists of a relkind type defined in PG_CLASS (**TABLE**, **INDEX**, **SEQUENCE**, **VIEW**, **COMPOSITE TYPE**, or **TOASTVALUE TOAST**) and the rtekind type used in the plan (**SUBQUERY**, **JOIN**, **FUNCTION**, **VALUES**, **CTE**, or **REMOTE_QUERY**).
+> - For RangeTableEntry (RTE), **object_owner** is the object description used in the plan. Non-user-defined objects do not have **object_owner**.
+> - Information in the **statement_id**, **object_name**, **object_owner**, and **projection** columns is stored in letter cases specified by users and information in other columns is stored in uppercase.
+> - **PLAN_TABLE** supports only **SELECT** and **DELETE** and does not support other DML operations.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/FAQ.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/FAQ.md
new file mode 100644
index 0000000000000000000000000000000000000000..6a1b15970c4bc89dfc5fdc9f825aff5e2f783f17
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/FAQ.md
@@ -0,0 +1,134 @@
+---
+title: FAQs
+summary: FAQs
+author: Zhang Cuiping
+date: 2021-11-17
+---
+
+# FAQs
+
+## An Error Is Reported Displaying "Failed to obtain the GPHOME" When a Command Is Executed
+
+### Symptom
+
+The following information is displayed if user **root** runs a command.
+
+```
+Failed to obtain the GPHOME.
+```
+
+### Possible Cause
+
+The *GPHOME* environment variable is not correctly configured. You need to check whether the *GPHOME* environment variable contains **gaussdbToolPath** in the XML file of the cluster.
+
+### Procedure
+
+Check the *$GPHOME* path.
+
+```
+echo $GPHOME
+```
+
+Modify the *$GPHOME* path in the configuration file if it is not the default installation path.
+
+```
+vim /etc/profile
+```
+
+## Restoration Method for Incomplete Key Files Caused by Interruption During Standby Instance Rebuilding Using gs_ctl
+
+### Symptom
+
+The standby instance fails to be rebuilt because the rebuilding process is interrupted. The following error information is displayed:
+
+```
+CRC checksum does not match value stored in file, maybe the cipher file is corrupt
+non obs cipher file or random parameter file is invalid.
+read cipher file or random parameter file failed.
+2020-06-18 20:58:12.080 5eeb64e3.1 [unknown] 140697304617088 [unknown] 0 dn_6001_6002 F0000 0 [BACKEND] FATAL:  could not load server certificate file "server.crt": no start line
+[2020-06-18 20:58:12.086][24066][dn_6001_6002][gs_ctl]:  waitpid 24446 failed, exitstatus is 256, ret is 2
+```
+
+### Possible Cause
+
+The certificate file is incomplete when the rebuilding is interrupted. The rebuilding fails again due to the incomplete certificate file.
+
+### Procedure
+
+1. Check the size of the certificate file in the data directory.
+
+   ```
+   ll
+   Check the size of the key file.
+   -rw------- 1 omm omm       0 Jun 18 20:58 server.crt
+   -rw------- 1 omm omm       0 Jun 18 20:58 server.key
+   -rw------- 1 omm omm       0 Jun 18 20:58 server.key.cipher
+   -rw------- 1 omm omm       0 Jun 18 20:58 server.key.rand
+   ```
+
+2. If the certificate file size is 0, delete the certificate file.
+
+   ```
+   rm -rf server.crt server.key server.key.cipher server.key.rand
+   ```
+
+3. Rebuild the standby instance.
+
+   ```
+   gs_ctl build -D data_dir
+   ```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> If the database on the standby node is stopped, you need to regenerate a certificate file or copy the certificate file (in *$GAUSSHOME***/share**) to the data directory, start the standby node, and rebuild the standby instance. For details about how to generate a certificate file, see the *Developer Guide*.
+
+## No Response Is Returned for a Long Time When gs_om -t status --all Is Used to Query Database Status
+
+### Symptom
+
+The system does not respond for a long time after the **gs_om -t status --all** command is executed.
+
+### Cause Analysis
+
+The possible cause is that the GaussDB process is hung. The query operation calls the **gsql** or **gs_ctl** tool to query the database status. After the process is hung, no response is returned until the query times out.
+
+### Procedure
+
+1. Check whether **gsql** can access the database. If the following information is displayed, the GaussDB process is hung and the database is abnormal.
+
+   ```
+   gsql -d postgres -p 29776        
+   gsql: wait (null):29776 timeout expired, errno: Success
+   ```
+
+2. Check whether the **postgresql-\*.log** file contains error information. If yes, rectify the fault based on the error information.
+
+   ```
+   cd $GAUSSLOG/pg_log/dn_6001;grep "ERROR\|FATAL" postgresql-*.log   
+   ```
+
+3. If the database has been hung, and the **gs_om** command does not take effect, search for the process ID on each node and kill the process.
+
+   ```
+   ps -ef|grep $GAUSSHOME/bin/gaussdb|grep -v grep       
+   kill -9 $pid
+   ```
+
+4. After the processes on all nodes are killed, run the following command on a node to start the processes: In the test environment, directly restart the database. In the manufacturer environment, contact Enmo technical support.
+
+   ```
+   gs_om -t start
+   ```
+
+## gs_sshexkey Reports an Error When the Same User Has Different Passwords
+
+### Symptom
+
+In the openEuler environment, gs_sshexkey supports mutual trust between different passwords of the same user. However, the authentication fails after the correct password is entered.
+
+### Cause Analysis
+
+Open the system log file **/var/log/secure** and check whether the **pam_faillock(sshd:auth): Consecutive login failures for user** log exists. If yes, the user account is locked because the number of incorrect password attempts exceeds the upper limit.
+
+### Procedure
+
+In the **/etc/pam.d** directory, modify the **system-auth**, **password-auth**, and **password-auth-crond** configuration files, increase the value of deny=3 in the files, and restore the value after the mutual trust relationships are established.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/client-tool.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/client-tool.md
new file mode 100644
index 0000000000000000000000000000000000000000..45f9d637ece5b6fb3f7e599a35ed282d9bfc1622
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/client-tool.md
@@ -0,0 +1,939 @@
+---
+title: Client Tool
+summary: Client Tool
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# Client Tool
+
+After the database is deployed, you need certain tools to conveniently connect to a database for operations and commissioning. MogDB provides some tools for database connections. You can use these tools to easily connect to the database and perform operations on it.
+
+## gsql
+
+**gsql** is a database connection tool provided by MogDB and runs in the command-line interface (CLI). Users can use **gsql** to connect to a server and perform operations and maintenance on the server. In addition to basic functions for performing operations on a database, **gsql** provides several advanced features for users.
+
+## Overview
+
+**Basic Features**
+
+- **Connect to the database**: For details, see "[Using the gsql Client for Connection](using-the-gsql-client-for-connection)" in the *Administrator Guide*.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** If the **gsql** client is used to connect to a database, the connection timeout period will be 5 minutes by default. If the database has not correctly set up a connection and authenticated the identity of the client within this period, **gsql** will time out and exit. To resolve this problem, see [FAQs](#FAQs).
+
+- **Run SQL statements**: Interactively entered SQL statements and specified SQL statements in a file can be run.
+
+- **Run meta-commands**: Meta-commands help the administrator view database object information, query cache information, format SQL output, and connect to a new database. For details about meta-commands, see [Meta-Command Reference](#Meta-Command Reference).
+
+**Advanced Features**
+
+[Table 1](#advanced) lists the advanced features of **gsql**.
+
+**Table 1** Advanced features of gsql <a id="advanced"> </a>
+
+| Feature Name                        | Description                                                  |
+| :---------------------------------- | :----------------------------------------------------------- |
+| Environment variable                | **gsql** provides a variable feature that is similar to the **shell** command of Linux. The following **\\set** meta-command of **gsql** can be used to set a variable:<br />`\set varname value`<br />To delete a variable, run the following command:<br />`\unset varname`<br />NOTE:<br />- A variable is a simple name-value pair, where the value can be any characters in any length.<br />- Variable names must consist of case-sensitive letters (including non-Latin letters), digits, and underscores(_).<br />- If the **\\set** *varname* meta-command (without the second parameter) is used, the variable is set without a value specified.<br />- If the **\\set** meta-command without parameters is used, values of all variables are displayed.<br />For details about variable examples and descriptions, see **variables**. |
+| SQL substitution                    | Common SQL statements can be set to variables using the variable feature of **gsql** to simplify operations.<br />For details about examples and descriptions about SQL substitution, see **SQL substitution**. |
+| Customized prompt                   | Prompts of **gsql** can be customized. Prompts can be modified by changing the reserved variables of **gsql**: *PROMPT1*, *PROMPT2*, and *PROMPT3*.<br />These variables can be set to customized values or the values predefined by **gsql**. For details, see **Prompt**. |
+| Historical client operation records | **gsql** can record historical client operations. This function is enabled by specifying the **-r** parameter when a client is connected. The number of historical records can be set using the **\\set** command. For example, **\\set HISTSIZE 50** indicates that the number of historical records is set to **50**. **\\set HISTSIZE 0** indicates that the operation history is not recorded.<br />NOTE:<br />- The default number of historical records is **32**. The maximum number of historical records is **500**. If interactively entered SQL commands contain Chinese characters, only the UTF-8 encoding environment is supported.<br />- For security reasons, the records containing sensitive words, such as **PASSWORD** and **IDENTIFIED**, are regarded sensitive and not recorded in historical information. This indicates that you cannot view these records in command output histories. |
+
+- Environment variables
+
+  To set a variable, run the **\\set** meta-command of **gsql**. For example, to set variable *foo* to **bar**, run the following command:
+
+  ```
+  mogdb=# \set foo bar
+  ```
+
+  To reference the value of a variable, add a colon (:) before the variable. For example, to view the value of variable *foo*, run the following command:
+
+  ```
+  mogdb=# \echo :foo
+  bar
+  ```
+
+  The variable reference method is suitable for regular SQL statements and meta-commands.
+
+  **gsql** pre-defines some special variables and plans the values of these variables. To ensure compatibility with later versions, do not use these variables for other purposes. For details about special variables, see [Table 2](#settings).
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > - All the special variables consist of upper-case letters, digits, and underscores(_).
+  > - To view the default value of a special variable, run the `\echo : varname` meta-command, for example, `\echo : DBNAME`.
+
+  **Table 2** Settings of special variables <a id="settings"> </a>
+
+  | Environment Variable | Setting Method                                    | Description                                                  |
+  | :------------------- | :------------------------------------------------ | :----------------------------------------------------------- |
+  | DBNAME               | `\set DBNAME dbname`                              | Name of the connected database. This variable is set again when a database is connected. |
+  | ECHO                 | `\set ECHO all | queries`                         | - If this variable is set to **all**, only the query information is displayed. This has the same effect as specifying the **-a** parameter when **gsql** is used to connect to a database.<br />- If this variable is set to **queries**, the command line and query information are displayed. This has the same effect as specifying the **-e** parameter when **gsql** is used to connect to a database. |
+  | ECHO_HIDDEN          | `\set ECHO_HIDDEN  on | off | noexec`             | When a meta-command (such as **\\dg**) is used to query database information, the value of this variable determines the query behavior.<br />- If this variable is set to **on**, the query statements that are called by the meta-command are displayed, and then the query result is displayed. This has the same effect as specifying the **-E** parameter when **gsql** is used to connect to a database.<br />- If this variable is set to **off**, only the query result is displayed.<br />- If this variable is set to **noexec**, only the query information is displayed, and the query is not run. |
+  | ENCODING             | `\set ENCODING   encoding`                        | Character set encoding of the current client.                |
+  | FETCH_COUNT          | `\set FETCH_COUNT *variable*`                     | - If the value is an integer greater than **0**, for example, *n*, *n* lines will be selected from the result set to the cache and displayed on the screen when the **SELECT** statement is run.<br />- If this variable is not set or set to a value less than or equal to **0**, all results are selected at a time to the cache when the **SELECT** statement is run.<br />NOTE:<br />A proper variable value helps reduce the memory usage. The recommended value range is from 100 to 1000. |
+  | HOST                 | `\set HOST hostname`                              | Specifies the name of a connected host.                      |
+  | IGNOREEOF            | `\set IGNOREEOF variable`                         | - If this variable is set to a number, for example, **10**, the first nine EOF characters entered (generally by pressing **Ctrl**+**D**) in **gsql** are ignored and the **gsql** program exits when **Ctrl**+**D** is pressed tenth times.<br />- If this variable is set to a non-numeric value, the default value is **10**.<br />- If this variable is deleted, **gsql** exits when an EOF is entered. |
+  | LASTOID              | `\set LASTOID oid`                                | Specifies the last OID, which is the value returned by an **INSERT** or **lo_import** command. This variable is valid only before the output of the next SQL statement is displayed. |
+  | ON_ERROR_ROLLBACK    | `\set  ON_ERROR_ROLLBACK  on | interactive | off` | - If the value is **on**, an error that may occur in a statement in a transaction block is ignored and the transaction continues.<br />- If the value is **interactive**, the error is ignored only in an interactive session.<br />- If the value is **off** (default value), the error triggers the rollback of the transaction block. In **on_error_rollback-on** mode, a **SAVEPOINT** is set before each statement of a transaction block, and an error triggers the rollback of the transaction block. |
+  | ON_ERROR_STOP        | `\set ON_ERROR_STOP on | off`                     | - **on**: specifies that the execution stops if an error occurs. In interactive mode, **gsql** returns the output of executed commands immediately.<br />- **off** (default value): specifies that an error, if occurring during the execution, is ignored, and the execution continues. |
+  | PORT                 | `\set PORT port`                                  | Specifies the port number of a connected database.           |
+  | USER                 | `\set USER username`                              | Specifies the database user you are currently connected as.  |
+  | VERBOSITY            | `\set VERBOSITY   terse | default | verbose`      | This variable can be set to **terse**, **default**, or **verbose** to control redundant lines of error reports.<br />- **terse**: Only critical and major error texts and text locations are returned (which is generally suitable for single-line error information).<br />- **default**: Critical and major error texts and text locations, error details, and error messages (possibly involving multiple lines) are all returned.<br />- **verbose**: All error information is returned. |
+
+- SQL substitution
+
+  **gsql**, like a parameter of a meta-command, provides a key feature that enables you to substitute a standard SQL statement for a **gsql** variable. **gsql** also provides a new alias or identifier for the variable. To replace the value of a variable using the SQL substitution method, add a colon (:) before the variable. For example:
+
+  ```sql
+  mogdb=# \set foo 'HR.areaS'
+  mogdb=# select * from :foo;
+   area_id |       area_name
+  ---------+------------------------
+         4 | Middle East and Africa
+         3 | Asia
+         1 | Europe
+         2 | Americas
+  (4 rows)
+  ```
+
+  The above command queries the HR.areaS table.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** The value of the variable is copied literally, so it can even contain unbalanced quotation marks or backslash commands. Therefore, the input content must be meaningful.
+
+- Prompt
+
+  The **gsql** prompt can be set using the three variables in [Table 3](#prompt). These variables consist of characters and special escape characters.
+
+  **Table 3** Prompt variables <a id="prompt"> </a>
+
+  | Variable | Description                                                  | Example                                                      |
+  | :------- | :----------------------------------------------------------- | :----------------------------------------------------------- |
+  | PROMPT1  | Specifies the normal prompt used when **gsql** requests a new command.<br />The default value of *PROMPT1* is:<br />`%/%R%#` | *PROMPT1* can be used to change the prompt.<br />- Change the prompt to **[local]**:<br />`mogdb=> \set PROMPT1 %M [local:/tmp/gaussdba_mppdb]`<br />- Change the prompt to **name**:<br />`mogdb=> \set PROMPT1 name name`<br />- Change the prompt to **=**:<br />`mogdb=> \set PROMPT1 %R =` |
+  | PROMPT2  | Specifies the prompt displayed when more input is expected because the command that is not terminated with a semicolon (;) or a quote (") is not closed. | *PROMPT2* can be used to display the prompt.<br />`mogdb=# \set PROMPT2 TEST`<br />`mogdb=# select * from HR.areaS TEST;`<br />`area_id |   area_name`<br />`---------+-------------------`<br />`1 |Europe`<br />`2 |Americas`<br />`4 |Middle East and Africa`<br />`3 |Asia (4 rows))` |
+  | PROMPT3  | Specifies the prompt displayed when the **COPY** statement (such as **COPY FROM STDIN**) is run and data input is expected. | **PROMPT3** can be used to display the **COPY** prompt.<br />`mogdb=#  \set PROMPT3 '>>>>'`<br />`mogdb=#  copy HR.areaS from STDIN;`<br />`Enter data to be copied followed by a newline.`<br />`End with a backslash and a period on a line by itself.`<br />`>>>>1 aa`<br />`>>>>2 bb`<br />`>>>>.` |
+
+  The value of the selected prompt variable is printed literally. However, a value containing a percent sign (%) is replaced by the predefined contents depending on the character following the percent sign (%). For details about the defined substitutions, see [Table 4](#defined).
+
+  **Table 4** Defined substitutions <a id="defined"></a>
+
+  | Symbol   | Description                                                  |
+  | :------- | :----------------------------------------------------------- |
+  | %M       | Specifies the full host name (with domain name). The full name is **[local]** if the connection is over a Unix domain socket, or **[local:/dir/name]** if the Unix domain socket is not at the compiled default location. |
+  | %m       | Specifies the host name truncated at the first dot. It is **[local]** if the connection is over a Unix domain socket. |
+  | %&gt;    | Specifies the number of the port that the host is listening on. |
+  | %n       | Replaced with the database session username.                 |
+  | %/       | Replaced with the name of the current database.              |
+  | %~       | Similar to **%/**. However, the output is tilde (\~) if the database is your default database. |
+  | %#       | Uses **#** if the session user is the database administrator. Otherwise, uses **&gt;**. |
+  | %R       | - In PROMPT1 normally **=**, but **^** if in single-line mode, or **!** if the session is disconnected from the database (which can happen if **\\connect** fails).<br />- In PROMPT2 %R is replaced with a hyphen (-), an asterisk (\*), a single or double quotation mark, or a dollar sign ($), depending on whether **gsql** expects more input because the query is inside a /*…*/ comment or inside a quoted or dollar-escaped string.* |
+  | %x       | Replaced with the transaction status.<br />- An empty string when it is not in a transaction block<br />- An asterisk () when it is in a transaction block<br />- An exclamation mark (!) when it is in a failed transaction block<br />- A question mark (?) when the transaction status is indefinite (for example, because there is no connection). |
+  | %digits  | Replaced with the character with the specified byte.         |
+  | %:name   | Specifies the value of the *name* variable of **gsql**.      |
+  | %command | Specifies command output, similar to substitution with the "^" symbol. |
+  | %[ … %]  | Prompts may contain terminal control characters which, for example, change the color, background, or style of the prompt text, or change the title of the terminal window. For example:<br />`mogdb=> \set PROMPT1 '%[%033[1;33;40m%]%n@%/%R%[%033[0m%]%#'`<br />The output is a boldfaced (1;) yellow-on-black (33;40) prompt on VT100-compatible, color-capable terminals. |
+
+  **Environment Variables**
+
+  **Table 5** Environment variables related to **gsql**
+
+  | Name                       | Description                                                  |
+  | :------------------------- | :----------------------------------------------------------- |
+  | COLUMNS                    | If **\\set columns** is set to **0**, this parameter controls the width of the wrapped format. This width determines whether to change the wide output mode into the vertical output mode if automatic expansion is enabled. |
+  | PAGER                      | If the query results do not fit on the screen, they are redirected through this command. You can use the **\\pset** command to disable the pager. Typically, the **more** or **less** command is used for viewing the query result page by page. The default is platform-dependent.<br />NOTE:<br />Display of the **less** command is affected by the *LC_CTYPE* environment variable. |
+  | PSQL_EDITOR                | The **\\e** and **\\ef** commands use the editor specified by the environment variables. The variables are examined in the order listed. The default editor on Unix is vi. |
+  | EDITOR                     |                                                              |
+  | VISUAL                     |                                                              |
+  | PSQL_EDITOR_LINENUMBER_ARG | When the **\\e** or **\\ef** command is used with a line number parameter, this variable specifies the command-line parameter used to pass the starting line number to the editor. For editors, such as Emacs or vi, this is a plus sign. Include a space in the value of the variable if space is needed between the option name and the line number. For example:<br />`PSQL_EDITOR_LINENUMBER_ARG = '+' PSQL_EDITOR_LINENUMBER_ARG='-line '`<br />A plus sign (+) is used by default on Unix. |
+  | PSQLRC                     | Specifies the location of the user's .gsqlrc file.           |
+  | SHELL                      | Has the same effect as the **!** command.                    |
+  | TMPDIR                     | Specifies the directory for storing temporary files. The default value is **/tmp**. |
+
+## Usage Guidelines
+
+**Prerequisites**
+
+The user has the permission to access the database.
+
+**Background**
+
+Use the **gsql** command to connect to the remote database service. When connecting to the remote database service, enable remote connection on the server. For details, see "Database Usage &gt; Connecting to a Database &gt; Using gsql to Connect to a Database &gt; Remotely Connecting to a Database" in the *Developer Guide*.
+
+**Procedure**
+
+1. Connect to the MogDB server using the **gsql** tool.
+
+   The **gsql** tool uses the **-d** parameter to specify the target database name, the **-U** parameter to specify the database username, the **-h** parameter to specify the host name, and the **-p** parameter to specify the port number.
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** If the database name is not specified, the default database name generated during initialization will be used. If the database username is not specified, the current OS username will be used by default. If a variable does not belong to any parameter (such as **-d** and **-U**), and **-d** is not specified, the variable will be used as the database name. If **-d** is specified but **-U** is not specified, the variable will be used as the database username.
+
+   Example 1: Connect to port 15400 of the mogdb database on the local PC as user **omm**:
+
+   ```sql
+   gsql -d mogdb -p 15400
+   ```
+
+   Example 2: Connect to the port 15400 of the remote mogdb database as user **jack**.
+
+   ```sql
+   gsql -h 10.180.123.163 -d mogdb -U jack -p 15400
+   ```
+
+   Example 3: *mogdb* and *omm* do not belong to any parameter, and they are used as the database name and the username, respectively.
+
+   ```sql
+   gsql mogdb omm -p 15400
+   ```
+
+   **Equals**
+
+   ```sql
+   gsql -d mogdb -U omm -p 15400
+   ```
+
+   For details about the **gsql** parameters, see [Command Reference](#command-reference).
+
+2. Run a SQL statement.
+
+   The following takes creating database **human_staff** as an example:
+
+   ```sql
+   CREATE DATABASE human_staff;
+   ```
+
+Ordinarily, input lines end when a command-terminating semicolon is reached. If the command is sent and executed without any error, the command output is displayed on the screen.
+
+1. Execute gsql meta-commands.
+
+   The following takes the listing of all MogDB databases and description information as an example.
+
+   ```sql
+   mogdb=#  \l
+                                   List of databases
+         Name      |  Owner   | Encoding  | Collate | Ctype |   Access privileges
+   ----------------+----------+-----------+---------+-------+-----------------------
+    human_resource | omm | SQL_ASCII | C       | C     |
+    mogdb       | omm | SQL_ASCII | C       | C     |
+    template0      | omm | SQL_ASCII | C       | C     | =c/omm         +
+                   |          |           |         |       | omm=CTc/omm
+    template1      | omm | SQL_ASCII | C       | C     | =c/omm          +
+                   |          |           |         |       | omm=CTc/omm
+    human_staff    | omm | SQL_ASCII | C       | C     |
+   (5 rows)
+   ```
+
+   For details about **gsql** meta-commands, see [Meta-Command Reference](#meta-command-reference) .
+
+**Example**
+
+Run the following command to create a tablespace EXAMPLE:
+
+```sql
+mogdb=# CREATE TABLESPACE EXAMPLE RELATIVE LOCATION 'tablespace1/tablespace_1';
+CREATE TABLESPACE
+```
+
+After the tablespace is created, run the following command to create a schema HR:
+
+```sql
+mogdb=# CREATE schema HR;
+CREATE SCHEMA
+```
+
+The example shows how to spread a command over several lines of input. Note the prompt change:
+
+```sql
+mogdb=# CREATE TABLE HR.areaS(
+mogdb(# area_ID   NUMBER,
+mogdb(# area_NAME VARCHAR2(25)
+mogdb(# )tablespace EXAMPLE;
+CREATE TABLE
+```
+
+Query the table definition:
+
+```sql
+mogdb=# \d HR.areaS
+               Table "hr.areas"
+  Column   |         Type          | Modifiers
+-----------+-----------------------+-----------
+ area_id   | numeric               |
+ area_name | character varying(25) |
+Tablespace: "example"
+```
+
+Insert four lines of data into **HR.areaS**.
+
+```sql
+mogdb=# INSERT INTO HR.areaS (area_ID, area_NAME) VALUES (1, 'Europe');
+INSERT 0 1
+mogdb=# INSERT INTO HR.areaS (area_ID, area_NAME) VALUES (2, 'Americas');
+INSERT 0 1
+mogdb=# INSERT INTO HR.areaS (area_ID, area_NAME) VALUES (3, 'Asia');
+INSERT 0 1
+mogdb=# INSERT INTO HR.areaS (area_ID, area_NAME) VALUES (4, 'Middle East and Africa');
+INSERT 0 1
+```
+
+Change the prompt.
+
+```sql
+mogdb=# \set PROMPT1 '%n@%m %~%R%#'
+omm@[local] mogdb=#
+```
+
+Query the table:
+
+```sql
+omm@[local] mogdb=#SELECT * FROM HR.areaS;
+ area_id |       area_name
+---------+------------------------
+       1 | Europe
+       4 | Middle East and Africa
+       2 | Americas
+       3 | Asia
+(4 rows)
+```
+
+Use the **\\pset** command to display the table in different ways:
+
+```sql
+omm@[local] mogdb=#\pset border 2
+Border style is 2.
+omm@[local] mogdb=#SELECT * FROM HR.areaS;
++---------+------------------------+
+| area_id |       area_name        |
++---------+------------------------+
+|       1 | Europe                 |
+|       2 | Americas               |
+|       3 | Asia                   |
+|       4 | Middle East and Africa |
++---------+------------------------+
+(4 rows)
+omm@[local] mogdb=#\pset border 0
+Border style is 0.
+omm@[local] mogdb=#SELECT * FROM HR.areaS;
+area_id       area_name
+------- ----------------------
+      1 Europe
+      2 Americas
+      3 Asia
+      4 Middle East and Africa
+(4 rows)
+omm@[local] mogdb=#\pset border 2
+Border style is 2.
+omm@[local] mogdb=#SELECT * FROM HR.areaS;
++---------+------------------------+
+| area_id |       area_name        |
++---------+------------------------+
+|       1 | Europe                 |
+|       2 | Americas               |
+|       3 | Asia                   |
+|       4 | Middle East and Africa |
++---------+------------------------+
+(4 rows)
+omm@[local] mogdb=#\pset border 0
+Border style is 0.
+omm@[local] mogdb=#SELECT * FROM HR.areaS;
+area_id       area_name
+------- ----------------------
+      1 Europe
+      2 Americas
+      3 Asia
+      4 Middle East and Africa
+(4 rows)
+omm@[local] mogdb=#\pset border 2
+Border style is 2.
+omm@[local] mogdb=#SELECT * FROM HR.areaS;
++---------+------------------------+
+| area_id |       area_name        |
++---------+------------------------+
+|       1 | Europe                 |
+|       2 | Americas               |
+|       3 | Asia                   |
+|       4 | Middle East and Africa |
++---------+------------------------+
+(4 rows)
+omm@[local] mogdb=#\pset border 0
+Border style is 0.
+omm@[local] mogdb=#SELECT * FROM HR.areaS;
+area_id       area_name
+------- ----------------------
+      1 Europe
+      2 Americas
+      3 Asia
+      4 Middle East and Africa
+(4 rows)
+```
+
+Use the meta-command:
+
+```sql
+omm@[local] mogdb=#\a \t \x
+Output format is unaligned.
+Showing only tuples.
+Expanded display is on.
+omm@[local] mogdb=#SELECT * FROM HR.areaS;
+area_id|2
+area_name|Americas
+
+area_id|1
+area_name|Europe
+
+area_id|4
+area_name|Middle East and Africa
+
+area_id|3
+area_name|Asia
+omm@[local] mogdb=#
+```
+
+## Obtaining Help Information
+
+**Procedure**
+
+- After connecting to the database, run the following command to obtain the help information:
+
+  ```sql
+  gsql --help
+  ```
+
+  The following help information is displayed:
+
+  ```sql
+  ......
+  Usage:
+    gsql [OPTION]... [DBNAME [USERNAME]]
+
+  General options:
+    -c, --command=COMMAND    run only single command (SQL or internal) and exit
+    -d, --dbname=DBNAME      database name to connect to (default: "omm")
+    -f, --file=FILENAME      execute commands from file, then exit
+  ......
+  ```
+
+- After connecting to the database, run the following command to obtain the help information:
+
+  ```sql
+  help
+  ```
+
+  The following help information is displayed:
+
+  ```
+  You are using gsql, the command-line interface to gaussdb.
+  Type:  \copyright for distribution terms
+         \h for help with SQL commands
+         \? for help with gsql commands
+         \g or terminate with semicolon to execute query
+         \q to quit
+  ```
+
+**Examples**
+
+1. Run the following command to connect to the database:
+
+   ```sql
+   gsql -d mogdb -p 15400
+   ```
+
+   **mogdb** is the name of the database to be connected, and **15400** is the port number of the primary database node.
+
+   If information similar to the following is displayed, the connection succeeds:
+
+   ```sql
+   gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+   Non-SSL connection (SSL connection is recommended when requiring high-security)
+   Type "help" for help.
+
+   mogdb=#
+   ```
+
+2. View the **gsql** help information. For details, see [Table gsql online help](#gsql).
+
+   **Table 6** gsql online help <a id="gsql"></a>
+
+   | Description              | Example                            |
+   | :------------------------ | :------------------------------- |
+   | Query the copyright.                               | \\copyright                                                   |
+   | View SQL statements supported by MogDB.            | View SQL statements supported by MogDB.<br />To query all SQL statements supported by MogDB, run the following command:<br />`mogdb=# \h` <br />`Available help:`<br /> `ABORT`<br />`ALTER APP WORKLOAD GROUP`<br />`… …`<br />For example, view parameters of the **CREATE DATABASE** command:<br />`mogdb=# \help CREATE DATABASE`<br />`Command:     CREATE DATABASE`<br />`Description: create a new database`<br />`Syntax:`<br />`CREATE DATABASE database_name`<br />`[ [ WITH ] {[ OWNER [=] user_name ]|`<br />`[ TEMPLATE [=] template ]|`<br />`[ ENCODING [=] encoding ]|`<br />`[ LC_COLLATE [=] lc_collate ]|`<br />`[ LC_CTYPE [=] lc_ctype ]|`<br />`[ DBCOMPATIBILITY [=] compatibility_type ]|`<br />`[ TABLESPACE [=] tablespace_name ]|`<br />`[ CONNECTION LIMIT [=] connlimit ]}[…] ];` |
+   | View the help information about **gsql** commands. | For example, view commands supported by **gsql**.<br />`mogdb=# \?`<br />`General`<br />`\copyright       show FusionInsight LibrA usage and distribution terms`<br />`\g [FILE] or ;         execute query (and send results to file or |pipe)`<br />`\h(\help) [NAME]              help on syntax of SQL commands, * for all commands`<br />`\parallel [on [num]|off] toggle status of execute (currently off)`<br />`\q                     quit gsql`<br />`… …` |
+
+For details about gsql parameters, see [Table Common parameters](#common), [Table Input and output parameters](#inputandoutput), [Table Output format parameters](#output), and [Table Connection parameters](#connection).
+
+**Table 7** Common parameters <a id="common"></a>
+
+| Parameter             | Description                      | Value Range                  |
+| :---------------------- | :------------------------- | :---------------------------------|
+| -c, -command=COMMAND            | Specifies that **gsql** is to run a string command and then exit. | -                                                            |
+| -d, -dbname=DBNAME              | Specifies the name of the database to connect to.            | A character string                                           |
+| -f, -file=FILENAME              | Specifies that files are used as the command source instead of interactively-entered commands. After the files are processed, **gsql** exits. If *FILENAME* is - (hyphen), then standard input is read.<br />NOTE:<br />Environment scenario: one primary and one standby (8 CPUs and 32 GB memory)<br />Test result: It takes about 8 minutes and 21 seconds to read a 200 MB data file.<br />It takes about 18 minutes and 41 seconds to read a 500 MB data file.<br />Suggestion: The file read time increases with the file data volume. If the file size is too large, the file needs to be read again when an exception occurs. In addition, the I/O of the system OS will be overloaded. It is recommended that the file size be about 500 MB. | An absolute path or relative path that meets the OS path naming convention |
+| -l, -list                       | Lists all available databases and then exits.                | -                                                            |
+| -v, -set, -variable=NAME=VALUE  | Sets variable *NAME* to *VALUE*.<br />For details about variable examples and descriptions, see **variables**. | -                                                            |
+| -X, -no-gsqlrc                  | Does not read the startup file (neither the system-wide **gsqlrc** file nor the user's **\~/.gsqlrc** file).<br />NOTE:<br />The startup file is **\~/.gsqlrc** by default or it can be specified by the environment variable *PSQLRC*. | -                                                            |
+| -1 ("one"), -single-transaction | When **gsql** uses the **-f** parameter to execute a script, **START TRANSACTION** and **COMMIT** are added to the start and end of the script, respectively, so that the script is executed as one transaction. This ensures that the script is executed successfully. If the script cannot be executed, the script is invalid.<br />NOTE:<br />If the script has used **START TRANSACTION**, **COMMIT**, or **ROLLBACK**, this parameter is invalid. | -                                                            |
+| -?, -help                       | Displays help information about **gsql** command parameters, and exits. | -                                                            |
+| -V, -version                    | Prints the **gsql** version and exits.                       | -                                                            |
+| -C, -enable-client-encryption   | When **-C** is used to connect to a local or remote database, you can use this option to enable the encrypted database function. | -                                                            |
+
+**Table 8** Input and output parameters<a id="inputandoutput"></a>
+
+| Parameter              | Description                  | **Value Range**               |
+| :--------------------- | :---------------------------- | :----------------------------- |
+| -a, -echo-all          | Prints all input lines to standard output as they are read.<br />CAUTION:<br />When this parameter is used in some SQL statements, the sensitive information, such as user password, may be disclosed. Use this parameter with caution. | -                                                            |
+| -e, -echo-queries      | Displays all SQL commands sent to the server to the standard output as well.<br />CAUTION:<br />When this parameter is used in some SQL statements, the sensitive information, such as user password, may be disclosed. Use this parameter with caution. | -                                                            |
+| -E, -echo-hidden       | Echoes the actual queries generated by **\\d** and other backslash commands. | -                                                            |
+| -k, -with-key=KEY      | Uses **gsql** to decrypt imported encrypted files.<br />NOTICE:<br />- For key characters, such as the single quotation mark (') or double quotation mark (") in shell commands, Linux shell checks whether the input single quotation mark (') or double quotation mark (") matches. If no match is found, Linux shell does not enter the gsql program until input is complete.<br />- Stored procedures and functions cannot be decrypted and imported. | -                                                            |
+| -L, -log-file=FILENAME | Writes normal output source and all query output into the **FILENAME** file.<br />CAUTION:<br />- When this parameter is used in some SQL statements, the sensitive information, such as user password, may be disclosed. Use this parameter with caution.<br />- This parameter retains only the query result in the corresponding file, so that the result can be easily found and parsed by other invokers (for example, automatic O&M scripts). Logs about **gsql** operations are not retained. | An absolute path or relative path that meets the OS path naming convention |
+| -m, -maintenance       | Allows MogDB to be connected during two-phase transaction recovery.<br />NOTE:<br />The parameter is for engineers only. When this parameter is used, **gsql** can be connected to the standby server to check data consistency between the primary server and standby server. | -                                                            |
+| -n, -no-libedit        | Closes command line editing.                                 | -                                                            |
+| -o, -output=FILENAME   | Puts all query output into the **FILENAME** file.            | An absolute path or relative path that meets the OS path naming convention |
+| -q, -quiet             | Indicates the quiet mode and no additional information will be printed. | By default, **gsql** displays various information.           |
+| -s, -single-step       | Runs in single-step mode. It indicates that the user is prompted before each command is sent to the server. This option can be also used for canceling execution. Use this option to debug scripts.<br />CAUTION:<br />When this parameter is used in some SQL statements, the sensitive information, such as user password, may be disclosed. Use this parameter with caution. | -                                                            |
+| -S, -single-line       | Runs in single-line mode where a line break terminates an SQL command, as a semicolon does. | -                                                            |
+
+**Table 9** Output format parameters<a id="output"></a>
+
+| Parameter            | Description             | **Value Range**               |
+| :------------------- | :---------------------- | :-------------------------- |
+| -A, -no-align                | Switches to unaligned output mode.                           | The default output mode is aligned.   |
+| -F, -field-separator=STRING  | Specifies the field separator. The default is the vertical bar (|). | -                                     |
+| -H, -html                    | Turns on the HTML tabular output.                            | -                                     |
+| -P, -pset=VAR[=ARG]          | Specifies the print option in the **\\pset** format in the command line.<br />NOTE:<br />The equal sign (=), instead of the space, is used here to separate the name and value. For example, enter **-P format=latex** to set the output format to **LaTeX**. | -                                     |
+| -R, -record-separator=STRING | Sets the record separator.                                   | -                                     |
+| -r                           | Enables the function of recording historical client operations. | This function is disabled by default. |
+| -t, -tuples-only             | Prints only tuples.                                          | -                                     |
+| -T, -table-attr=TEXT         | Specifies options to be placed within the HTML table tag.<br />Use this parameter with the **-H,-html** parameter to specify the output to the HTML format. | -                                     |
+| -x, -expanded                | Turns on the expanded table formatting mode.                 | -                                     |
+| -z, -field-separator-zero    | Sets the field separator in the unaligned output mode to be blank.<br />Use this parameter with the **-A, -no-align** parameter to switch to unaligned output mode. | -                                     |
+| -0, -record-separator-zero   | Sets the record separator in the unaligned output mode to be blank.<br />Use this parameter with the **-A, -no-align** parameter to switch to unaligned output mode. | -                                     |
+
+**Table 10** Connection parameters<a id="connection"></a>
+
+| Parameter   | Description           | Value Range                               |
+| :--------------------- | :------------------------ | :--------------------------|
+| -h, -host=HOSTNAME     | Specifies the host name of the machine on which the server is running or the directory for the Unix-domain socket. | If the host name is omitted, **gsql** connects to the server of the local host over the Unix domain socket or over TCP/IP to connect to local host without the Unix domain socket. |
+| -p, -port=PORT         | Specifies the port number of the database server.<br />You can modify the default port number using the **-p, -port=PORT** parameter. | The default value is 15400.                                  |
+| -U, -username=USERNAME | Specifies the user that connects to the database.<br />NOTE:<br />- If this parameter is specified, you also need to enter your password for identity authentication when connecting to the database. You can enter the password interactively or use the **-W** parameter to specify a password.<br />- To connect to a database, add an escape character before any dollar sign ($) in the user name. | A character string. The default user is the current user that operates the system. |
+| -W, -password=PASSWORD | Specifies the password when the **-U** parameter is used to connect to a remote database.<br />NOTE:<br />When the server where the primary database node is located connects to the local primary database node, the trust connection is used by default and this parameter is ignored.<br />To connect to a database.<br />If this parameter is not specified but database connection requires your password, you will be prompted to enter your password in interactive mode. The maximum length of the password is 999 bytes, which is restricted by the maximum value of the GUC parameter **password_max_length**. | The password must meet the complexity requirement.           |
+
+## Meta-Command Reference
+
+This section describes meta-commands provided by **gsql** after the MogDB database CLI tool is used to connect to a database. A **gsql** meta-command can be anything that you enter in **gsql** and begins with an unquoted backslash.
+
+**Precautions**
+
+- The format of the **gsql** meta-command is a backslash () followed by a command verb, and then a parameter. The parameters are separated from the command verb and from each other by any number of whitespace characters.
+- To include whitespace in a parameter, you can quote it with single quotation marks ("). To include single quotation marks in a parameter, add a backslash in front of it. Anything contained in single quotation marks is furthermore subject to C-like substitutions for \\n (new line), \\t (tab), \\b (backspace), \\r (carriage return), \\f (form feed), \\digits (octal), and \\xdigits (hexadecimal).
+- Within a parameter, text enclosed in double quotation marks ("") is taken as a command line input to the shell. The command output (with any trailing newline removed) is taken as a parameter.
+- If an unquoted parameter begins with a colon (:), the parameter is taken as a **gsql** variable and the value of the variable is used as the parameter value instead.
+- Some commands take an SQL identifier (such as a table name) as a parameter. These parameters follow the SQL syntax rules: Unquoted letters are forced to lowercase, while double quotation marks ("") protect letters from case conversion and allow incorporation of whitespace into the identifier. Within double quotation marks, paired double quotation marks reduce to a single double quotation mark in the result name. For example, **FOO"BAR"BAZ** is interpreted as **fooBARbaz**, and **"Aweird""name"** becomes **A weird"name**.
+- Parameter parsing stops when another unquoted backslash appears. An unquoted backslash is taken as the beginning of a new meta-command. The special sequence \\ (two backslashes) marks the end of parameters and continues parsing SQL statements if any. In this way, SQL statements and **gsql** commands can be freely mixed in a line. However, the parameters of a meta-command cannot continue beyond the end of a line in any situations.
+
+**Meta-Commands**
+
+For details about meta-commands, see [Table Common meta-commands](#meta), [Table Query buffer meta-commands](#query), [Table Input and output meta-commands](#metacommand), [Table Information display meta-commands](#information), [Table Formatting meta-commands](#formatting),[Table Connection meta-commands](#connect) , [Table OS meta-commands](#os), [Table Variable meta-commands](#varia), and [Table Large object meta-commands](#large).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** *FILE* mentioned in the following commands indicates a file path. This path can be an absolute path such as **/home/gauss/file.txt** or a relative path, such as **file.txt**. By default, a **file.txt** is created in the path where the user runs **gsql** commands.
+
+**Table 11** Common meta-commands <a id="meta"></a>
+
+| Parameter                 | Description                    | Value Range                  |
+| :------------------------ | :----------------------------- | :-----------------------|
+| \\copyright                | Displays the MogDB version and copyright information.        | -                                                            |
+| \\g [FILE] or ;            | Performs a query operation and sends the result to a file or pipe. | -                                                            |
+| \\h(\\help) [NAME]          | Provides syntax help on the specified SQL statement.         | If **NAME** is not specified, then **gsql** will list all the commands for which syntax help is available. <br />If **NAME** is an asterisk (*), syntax help on all SQL statements is displayed. |
+| \\parallel [on [num]\|off] | Controls the parallel execution function.<br />- **on**: The switch is enabled and the maximum number of concurrently executed tasks is *num*.<br />- **off**: This switch is disabled.<br />NOTE:<br />- Parallel execution is not allowed in a running transaction and a transaction is not allowed to be stared during parallel execution.<br />- Parallel execution of **\\d** meta-commands is not allowed.<br />- If **SELECT** statements are run concurrently, customers can accept the problem that the return results are displayed randomly but they cannot accept it if a core dump or process response failure occurs.<br />- **SET** statements are not allowed in concurrent tasks because they may cause unexpected results.<br />- Temporary tables cannot be created. If temporary tables are required, create them before parallel execution is enabled, and use them only in the parallel execution. Temporary tables cannot be created in parallel execution.<br />- When **\\parallel** is executed, *num* independent gsql processes can be connected to the database server.<br />- The duration of all the jobs specified using **\\parallel** cannot exceed **session_timeout**. Otherwise, the database may be disconnected during parallel execution. | The default value of *num* is **1024**.<br />NOTICE:<br />- The maximum number of connections allowed by the server is determined based on **max_connection** and the number of current connections.<br />- Set the value of *num* based on the allowed number of connections. |
+| \\q                        | Exits the gsql program. In a script file, this command is run only when a script terminates. | -                                                            |
+
+**Table 12** Query buffer meta-commands<a id="query"></a>
+
+| Parameter             | Description                                                  |
+| :-------------------- | :----------------------------------------------------------- |
+| \\e [FILE] [LINE]      | Uses an external editor to edit the query buffer or file.    |
+| \\ef [FUNCNAME [LINE]] | Uses an external editor to edit the function definition. If **LINE** is specified, the cursor will point to the specified line of the function body. |
+| \\p                    | Prints the current query buffer to the standard output.      |
+| \\r                    | Resets (clears) the query buffer.                            |
+| \\w FILE               | Outputs the current query buffer to a file.                  |
+
+**Table 13** Input and output meta-commands<a id="metacommand"></a>
+
+| Parameter                      | Description                     |
+| :----------------------------- | :------------------------------------ |
+| \\copy { table [ ( column_list ) ] \| ( query ) } { from \| to } { filename \| stdin \| stdout \| pstdin \| pstdout } [ with ] [ binary ] [ oids ] [ delimiter [ as ] 'character' ] [ null [ as ] 'string' ] [ csv [ header ] [ quote [ as ] 'character' ] [ escape [ as ] 'character' ] [ force quote column_list \| * ] [ force not null column_list ] ] [parallel integer] | After logging in to the database on any psql client, you can import and export data. This is an operation of running the **SQL COPY** command, but not the server that reads or writes data to a specified file. Instead, data is transferred between the server and the local file system. This means that the accessibility and permissions of the file are the permissions of the local user rather than the server. The initial database user permission is not required.<br />NOTE:<br />**\\copy** applies only to small-scale data import in good format. It does not preprocess invalid characters or provide error tolerance. **COPY** is preferred for data import.<br />\\COPY specifies the number of clients to import data to implement parallel import of data files. Currently, the value ranges from 1 to 8.<br />The parallel import using \\COPY has the following constraints: Parallel import of temporary tables is not supported. Parallel import within transactions is not supported. Parallel import of binary files is not supported. Parallel import of data encrypted using AES-128 is not supported. In these cases, even if the parallel parameter is specified, a non-parallel process is performed. |
+| \\echo [STRING]                                               | Writes a character string to the standard output.            |
+| \\i FILE                                                      | Reads content from *FILE* and uses them as the input for a query. |
+| \\i+ FILE KEY                                                 | Runs commands in an encrypted file.                          |
+| \\ir FILE                                                     | Is similar to **\\i**, but resolves relative path names differently. |
+| \\ir+ FILE KEY                                                | Is similar to **\\i+**, but resolves relative path names differently. |
+| \\o [FILE]                                                    | Saves all query results to a file.                           |
+| \\qecho [STRING]                                              | Prints a character string to the query result output.        |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** In [Table 14](#information), option **S** indicates displaying the system object and **PATTERN** indicates displaying the additional description information and the name of the object to be displayed.
+
+**Table 14** Information display meta-commands<a id="information"></a>
+
+| Parameter           | Description          | Value Range          | Example             |
+| :------------------ | :------------------  | :------------------- | :------------------ |
+| \\d[S+]                                                       | Lists all tables, views, and sequences of all schemas in **search_path**. When objects with the same name exist in different schemas in **search_path**, only the object in the schema that ranks first in **search_path** is displayed. | -                                                            | List all tables, views, and sequences of all schemas in **search_path**.<br />`mogdb=# \d` |
+| \\d[S+] NAME                                                  | Lists the structure of specified tables, views, and indexes. | -                                                            | List the structure of table **a**.<br />`mogdb=#  \dtable+ a` |
+| \\d+ [PATTERN]                                                | Lists all tables, views, and indexes.                        | If **PATTERN** is specified, only tables, views, and indexes whose names match **PATTERN** are displayed. | List all tables, views, and indexes whose names start with **f**.<br />`mogdb=# \d+ f` |
+| \\da[S] [PATTERN]                                             | Lists all available aggregate functions, together with their return value types and the data types. | If **PATTERN** is specified, only aggregate functions whose names match **PATTERN** are displayed. | List all available aggregate functions whose names start with **f**, together with their return value types and the data types.<br />`mogdb=# \da f` |
+| \\db[+] [PATTERN]                                             | Lists all available tablespaces.                             | If **PATTERN** is specified, only tablespaces whose names match **PATTERN** are displayed. | List all available tablespaces whose names start with **p**.<br />`mogdb=# \db p*` |
+| \\dc[S+] [PATTERN]                                            | Lists all available conversions between character sets.      | If **PATTERN** is specified, only conversions whose names match **PATTERN** are displayed. | List all available conversions between character sets.<br />`mogdb=# \d`
+| \\dC[+] [PATTERN]                                             | Lists all type conversions.                                  | If **PATTERN** is specified, only conversions whose names match **PATTERN** are displayed. | List all type conversion whose patten names start with **c**`# \dC c` |
+| \\dd[S] [PATERN]                                             | Lists descriptions about objects matching **PATTERN**.       | If **PATTERN** is not specified, all visible objects are displayed. The objects include aggregations, functions, operators, types, relations (table, view, index, sequence, and large object), and rules. | List all visible objects.<br />`mogdb=# \dd`                 |
+| \\ddp [PATTERN]                                               | Lists all default permissions.                               | If **PATTERN** is specified, only permissions whose names match **PATTERN** are displayed. | List all default permissions.<br />`mogdb=# \ddp`            |
+| \\dD[S+] [PATTERN]                                            | Lists all available domains.                                 | If **PATTERN** is specified, only domains whose names match **PATTERN** are displayed. | List all available domains.<br />`mogdb=# \dD`               |
+| \\ded[+] [PATTERN]                                            | Lists all Data Source objects.                               | If **PATTERN** is specified, only objects whose names match **PATTERN** are displayed. | List all Data Source objects.<br />`mogdb=# \ded`            |
+| \\det[+] [PATTERN]                                            | Lists all external tables.                                   | If **PATTERN** is specified, only tables whose names match **PATTERN** are displayed. | List all external tables.<br />`mogdb=# \det`                |
+| \\des[+] [PATTERN]                                            | Lists all external servers.                                  | If **PATTERN** is specified, only servers whose names match **PATTERN** are displayed. | List all external servers.<br />`mogdb=# \des`               |
+| \\deu[+] [PATTERN]                                            | Lists user mappings.                                         | If **PATTERN** is specified, only mappings whose names match **PATTERN** are displayed. | List user mappings.<br />`mogdb=# \deu`                      |
+| \\dew[+] [PATTERN]                                            | Lists foreign-data wrappers.                                 | If **PATTERN** is specified, only wrappers whose names match **PATTERN** are displayed. | List foreign-data wrappers.<br />`mogdb=# \dew`              |
+| \\df[antw][S+] [PATTERN]                                      | Lists all available functions, together with their parameters and return types. **a** indicates an aggregate function, **n** indicates a common function, **t** indicates a trigger, and **w** indicates a window function. | If **PATTERN** is specified, only functions whose names match **PATTERN** are displayed. | List all available functions, together with their parameters and return types.<br />`mogdb=# \df` |
+| \\dF[+] [PATTERN]                                             | Lists all text search configurations.                        | If **PATTERN** is specified, only configurations whose names match **PATTERN** are displayed. | List all text search configurations.<br />`mogdb=# \dF+`     |
+| \\dFd[+] [PATTERN]                                            | Lists all text search dictionaries.                          | If **PATTERN** is specified, only dictionaries whose names match **PATTERN** are displayed. | List all text search dictionaries.<br />`mogdb=# \dFd`       |
+| \\dFp[+] [PATTERN]                                            | Lists all text search parsers.                               | If **PATTERN** is specified, only parsers whose names match **PATTERN** are displayed. | List all text search parsers.<br />`mogdb=# \dFp`            |
+| \\dFt[+] [PATTERN]                                            | Lists all text search templates.                             | If **PATTERN** is specified, only templates whose names match **PATTERN** are displayed. | List all text search templates.<br />`mogdb=# \dFt`          |
+| \\dg[+] [PATTERN]                                             | Lists all database roles.<br />NOTE:<br />Since the concepts of "users" and "groups" have been unified into "roles", this command is now equivalent to **\\du**. The two commands are all reserved for forward compatibility. | If **PATTERN** is specified, only roles whose names match **PATTERN** are displayed. | List all database roles whose names start with **j** and end with **e**.<br />`mogdb=# \dg j?e` |
+| \\dl                                                          | An alias for **\\lo_list**, which shows a list of large objects. | -                                                            | List all large objects.<br />`mogdb=# \dl`                   |
+| \\dL[S+] [PATTERN]                                            | Lists available procedural languages.                        | If **PATTERN** is specified, only languages whose names match **PATTERN** are displayed. | List available procedural languages.<br />`mogdb=# \dL`      |
+| \\dn[S+] [PATTERN]                                            | Lists all schemas (namespace).                               | If **PATTERN** is specified, only schemas whose names match **PATTERN** are displayed. By default, only schemas you created are displayed. | List information about all schemas whose names start with **d**.<br />`mogdb=#  \dn+ d` |
+| \\do[S] [PATTERN]                                             | Lists all available operators with their operand and return types. | If **PATTERN** is specified, only operators whose names match **PATTERN** are displayed. By default, only operators you created are displayed. | List all available operators with their operand and return types.<br />`mogdb=# \do` |
+| \\dO[S+] [PATTERN]                                            | Lists collations.                                            | If **PATTERN** is specified, only collations whose names match **PATTERN** are displayed. By default, only collations you created are displayed. | List collations.<br />`mogdb=# \dO`                          |
+| \\dp [PATTERN]                                                | Lists tables, views, and related permissions.<br />The following result about **\\dp** is displayed:<br />`rolename=xxxx/yyyy  - Assigning permissions to a role`<br />`=xxxx/yyyy  -Assigning permissions to public`<br />*xxxx* indicates assigned permissions, and *yyyy* indicates roles with the assigned permissions. For details about permission descriptions, see [Table Description of permissions](#description). | If **PATTERN** is specified, only tables and views whose names match **PATTERN** are displayed. | List tables, views, and related permissions.<br />`mogdb=# \dp` |
+| \\drds [PATTERN1 [PATTERN2]]                                  | Lists all modified configuration parameters. These settings can be for roles, for databases, or for both. **PATTERN1** and **PATTERN2** indicate a role pattern and a database pattern, respectively. | If **PATTERN** is specified, only collations whose names match **PATTERN** are displayed. If the default value is used or is specified, all settings are listed. | List all modified configuration parameters of the **mogdb** database.<br />`mogdb=# \drds * mogdb` |
+| \\dT[S+] [PATTERN]                                            | Lists all data types.                                        | If **PATTERN** is specified, only types whose names match **PATTERN** are displayed. | List all data types.<br />`mogdb=# \dT`                      |
+| \\du[+] [PATTERN]                                             | Lists all database roles.<br />NOTE:<br />Since the concepts of "users" and "groups" have been unified into "roles", this command is now equivalent to **\\dg**. The two commands are all reserved for forward compatibility. | If **PATTERN** is specified, only roles whose names match **PATTERN** are displayed. | List all database roles.<br />`mogdb=# \du`                  |
+| \\dE[S+] [PATTERN]\\di[S+] [PATTERN]\\ds[S+] [PATTERN]\\dt[S+] [PATTERN]\\dv[S+] [PATTERN] | In this group of commands, the letters E, i, s, t, and v stand for a foreign table, index, sequence, table, or view, respectively. You can specify any or a combination of these letters sequenced in any order to obtain an object list. For example, **\\dit** lists all indexes and tables. If a command is suffixed with a plus sign (+), physical dimensions and related descriptions of each object will be displayed. | If **PATTERN** is specified, only objects whose names match **PATTERN** are displayed. By default, only objects you created are displayed. You can specify **PATTERN** or **S** to view other system objects. | List all indexes and views.<br />`mogdb=# \div`              |
+| \\dx[+] [PATTERN]                                             | Lists the extensions of the installed database.              | If **PATTERN** is specified, only extensions whose names match **PATTERN** are displayed. | List the extensions of the installed database.<br />`mogdb=# \dx` |
+| \\l[+]                                                        | Lists the names, owners, character set encodings, and permissions of all the databases in the server. | -                                                            | List the names, owners, character set encodings, and permissions of all the databases in the server.<br />`mogdb=#  \l` |
+| \\sf[+] FUNCNAME                                              | Displays function definitions.<br />NOTE:<br />If the function name contains parentheses, enclose the function name with quotation marks and add the parameter type list following the double quotation marks. Also enclose the list with parentheses. | -                                                            | Assume a function function_a and a function func()name. This parameter will be as follows:<br />`mogdb=# \sf function_a mogdb=# \sf "func()name"(argtype1, argtype2)` |
+| \\z [PATTERN]                                                 | Lists all tables, views, and sequences in the database and their access permissions. | If a pattern is given, it is a regular expression, and only matched tables, views, and sequences are displayed. | List all tables, views, and sequences in the database and their access permissions.<br />`mogdb=# \z` |
+
+**Table 15** Description of permissions <a id="description"></a>
+
+| Parameter | Description                     |
+| :-------- | :------------------------------ |
+| r         | SELECT: allows you to read data from specified tables and views. |
+| w         | UPDATE: allows you to update columns for specified tables.   |
+| a         | INSERT: allows you to insert data to specified tables.       |
+| d         | DELETE: allows you to delete data from specified tables.     |
+| D         | TRUNCATE: allows you to delete all data from specified tables. |
+| x         | REFERENCES: allows you to create foreign key constraints. This parameter does not take effect because foreign keys are not supported. |
+| t         | TRIGGER: allows you to create a trigger on specified tables. |
+| X         | EXECUTE: allows you to use specified functions and the operators that are realized by the functions. |
+| U         | USAGE:<br />- For procedural languages, allows you to specify a procedural language when creating a function.<br />- For schemas, allows you to access objects included in specified schemas.<br />- For sequences, allows you to use the nextval function. |
+| C         | CREATE:<br />- For databases, allows you to create schemas within a database.<br />- For schemas, allows you to create objects in a schema.<br />- For tablespaces, allows you to create tables in a tablespace and set the tablespace to default one when creating databases and schemas. |
+| c         | CONNECT: allows you to access specified databases.           |
+| T         | TEMPORARY: allows you to create temporary tables.            |
+| A         | ALTER: allows users to modify the attributes of a specified object. |
+| P         | DROP: allows users to delete a specified object.             |
+| m         | COMMENT: allows users to define or modify comments of a specified object. |
+| i         | INDEX: allows users to create indexes on specified tables.   |
+| v         | VACUUM: allows users to perform ANALYZE and VACUUM operations on specified tables. |
+| *         | Authorization options for preceding permissions.             |
+
+**Table 16** Formatting meta-commands<a id="formatting"></a>
+
+| Parameter          | Description                                                  |
+| :----------------- | :----------------------------------------------------------- |
+| \\a                 | Controls the switchover between unaligned mode and aligned mode. |
+| \\C [STRING]        | Sets the title of any table being printed as the result of a query or cancels such a setting. |
+| \\f [STRING]        | Sets a field separator for unaligned query output.           |
+| \\H                 | If the text format schema is used, switches to the HTML format.If the HTML format schema is used, switches to the text format. |
+| \\pset NAME [VALUE] | Sets options affecting the output of query result tables. For details about the value of **NAME**, see [Table Adjustable printing options](#adjustable). |
+| \\t [on|off]       | Switches the information and row count footer of the output column name. |
+| \\T [STRING]        | Specifies attributes to be placed within the table tag in HTML output format. If the parameter is not configured, the attributes are not set. |
+| \\x [on|off|auto] | Switches expanded table formatting modes.                    |
+
+**Table 17** Adjustable printing options <a id="adjustable"></a>
+
+| Option             | Description                 | Value Range                         |
+| :----------------- | :-----------------------------| :------------------------ |
+| border             | The value must be a number. In general, a larger number indicates wider borders and more table lines. | The value is an integer greater than 0 in HTML format.<br />The value range in other formats is as follows:<br />- **0**: no border<br />- **1**: internal dividing line<br />- **2**: table frame |
+| expanded (or x)    | Switches between regular and expanded formats.               | - When the expanded format is enabled, query results are displayed in two columns, with the column name on the left and the data on the right. This format is useful if the data does not fit the screen in the normal "horizontal" format.<br />- The expanded format is used when the query output is wider than the screen. Otherwise, the regular format is used. The regular format is effective only in the aligned and wrapped formats. |
+| fieldsep           | Specifies the field separator to be used in unaligned output format. In this way, you can create tab- or comma-separated output required by other programs. To set a tab as field separator, type **\\pset fieldsep '\\t'**. The default field separator is a vertical bar (\|). | -                                                            |
+| fieldsep_zero      | Sets the field separator to be used in unaligned output format to zero bytes. | -                                                            |
+| footer             | Enables or disables the display of table footers.            | -                                                            |
+| format             | Selects the output format. Unique abbreviations are allowed. (This means a single letter is sufficient.) | Value range:<br />- **unaligned**: Write all columns of a row on one line, separated by the currently active column separator.<br />- **aligned**: This format is standard and human-readable.<br />- **wrapped**: This format is similar to **aligned**, but includes the packaging cross-line width data value to suit the width of the target field output.<br />- **html**: This format outputs table to the markup language for a document. The output is not a complete document.<br />- **latex**: This format outputs table to the markup language for a document. The output is not a complete document.<br />- **troff-ms**: This format outputs table to the markup language for a document. The output is not a complete document. |
+| null               | Sets a character string to be printed in place of a null value. | By default, nothing is printed, which can easily be mistaken for an empty character string. |
+| numericlocale      | Enables or disables the display of a locale-specific character to separate groups of digits to the left of the decimal marker. | - **on**: The specified separator is displayed.<br />- **off**: The specified separator is not displayed.<br />If this parameter is ignored, the default separator is displayed. |
+| pager              | Controls the use of a pager for query and gsql help outputs. If the **PAGER** environment variable is set, the output is piped to the specified program. Otherwise, a platform-dependent default is used. | - **on**: The pager is used for terminal output that does not fit the screen.<br />- **off**: The pager is not used.<br />- **always**: The pager is used for all terminal output regardless of whether it fits the screen. |
+| recordsep          | Specifies the record separator to be used in unaligned output format. | -                                                            |
+| recordsep_zero     | Specifies the record separator to be used in unaligned output format to zero bytes. | -                                                            |
+| tableattr (or T)   | Specifies attributes to be placed inside the HTML table tag in HTML output format (such as cellpadding or bgcolor). Note that you do not need to specify border here because it has been used by **\\pset border**. If no value is given, the table attributes do not need to be set. | -                                                            |
+| title              | Specifies the table title for any subsequently printed tables. This can be used to give your output descriptive tags. If no value is given, the title does not need to be set. | -                                                            |
+| tuples_only (or t) | Enables or disables the tuples-only mode. Full display may show extra information, such as column headers, titles, and footers. In tuples-only mode, only the table data is displayed. | -                                                            |
+
+**Table 18** Connection meta-commands<a id="connect"></a>
+
+| Parameter                | Description                 | Value Range                  |
+| :----------------------- | :---------------------------| :--------------------------|
+|\\c[onnect] [DBNAME|- USER|- HOST|- PORT|-] | Connects to a new database. The current database is mogdb. If a database name contains more than 63 bytes, only the first 63 bytes are valid and are used for connection. However, the database name displayed in the command line of **gsql** is still the name before the truncation.<br />NOTE:<br />If the database login user is changed during reconnection, you need to enter the password for the new user. The maximum length of the password is 999 bytes, which is restricted by the maximum value of the GUC parameter **password_max_length**. | -                                                            |
+| \\encoding [ENCODING]                           | Sets the client character set encoding.                      | This command shows the current encoding if it has no parameter. |
+| \\conninfo                                      | Outputs information about the current database connection.   | -                                                            |
+
+**Table 19** OS meta-commands<a id="os"></a>
+
+| Parameter            | Description                                                  | Value Range                                                  |
+| :------------------- | :----------------------------------------------------------- | :----------------------------------------------------------- |
+| \\cd [DIR]            | Changes the current working directory.                       | An absolute path or relative path that meets the OS path naming convention |
+| \\setenv NAME [VALUE] | Sets the **NAME** environment variable to **VALUE**. If **VALUE** is not provided, do not set the environment variable. | -                                                            |
+| \\timing [on|off]    | Toggles a display of how long each SQL statement takes, in milliseconds. | - **on**: enables the display function.<br />- **off**: disables the display function. |
+| ! [COMMAND]          | Escapes to a separate Unix shell or runs a Unix command.     | -                                                            |
+
+**Table 20** Variable meta-commands<a id="varia"></a>
+
+| Parameter           | Description                                                  |
+| :------------------ | :----------------------------------------------------------- |
+| \\prompt [TEXT] NAME | Prompts the user to use texts to specify a variable name.    |
+| \\set [NAME [VALUE]] | Sets the **NAME** internal variable to **VALUE**. If more than one value is provided, **NAME** is set to the concatenation of all of them. If only one parameter is provided, the variable is set with an empty value.<br />Some common variables are processed in another way in **gsql**, and they are the combination of uppercase letters, numbers, and underscores. [Table 21](#set) describes a list of variables that are processed in a way different from other variables. |
+| \\unset NAME         | Unsets or deletes the variable name of **gsql**.             |
+
+**Table 21** Common \\set commands<a id="set"></a>
+
+| Command              | Description                 | Value Range |
+| :------------------- | :---------------------- | :---------------------------------- |
+| \\set VERBOSITY value     | This variable can be set to **default**, **verbose**, or **terse** to control redundant lines of error reports. | Value range: **default**, **verbose**, **terse**             |
+| \\set ON_ERROR_STOP value | If this variable is set, the script execution stops immediately. If this script is invoked from another script, that script will be stopped immediately as well. If the primary script is invoked using the **-f** option rather than from one **gsql** session, **gsql** will return error code 3, indicating the difference between the current error and critical errors. (The error code for critical errors is 1.) | Value range: **on/off**, **true/ false**, **yes/no**, **1⁄0** |
+| \\set RETRY [retry_times] | Determines whether to enable the retry function if statement execution encounters errors. The parameter **retry_times** specifies the maximum number of retry times and the default value is **5**. Its value ranges from 5 to 10. If the retry function has been enabled, when you run the **\\set RETRY** command again, the retry function will be disabled.<br />The configuration file **retry_errcodes.conf** shows a list of errors. If these errors occur, retry is required. This configuration file is placed in the same directory as that for executable gsql programs. This configuration file is configured by the system rather than by users and cannot be modified by the users.<br />The retry function can be used in the following error scenarios:<br />- YY001: TCP communication errors. Print information: **Connection reset by peer**.<br />- YY002: TCP communication errors. Print information: **Connection reset by peer**.<br />- YY003: Lock timeout. Print information: **Lock wait timeout…/wait transaction** *xxx* **sync time exceed** *xxx*.<br />- YY004: TCP communication errors. Print information: **Connection timed out**.<br />- YY005: Failed to deliver the **SET** query command. Print information: **ERROR SET query**.<br />- YY006: Failed to apply for memory. Print information: **memory is temporarily unavailable**.<br />- YY007: Communication library error. Print information: **Memory allocate error**.<br />- YY008: Communication library error. Print information: **No data in buffer**.<br />- YY009: Communication library error. Print information: **Close because release memory**.<br />- YY010: Communication library error. Print information: **TCP disconnect**.<br />- YY011: Communication library error. Print information: **SCTP disconnect**.<br />- YY012: Communication library error. Print information: **Stream closed by remote**.<br />- YY013: Communication library error. Print information: **Wait poll unknown error**.<br />- YY014, YY015, 53200, 08006, 08000, 57P01, XX003, XX009<br />If an error occurs, **gsql** queries connection status of every database node. If the connection status is abnormal, **gsql** sleeps for 1 minute and tries again. In this case, the retries in most of the primary/standby switchover scenarios are involved.<br />NOTE:<br />1. Statements in transaction blocks cannot be retried upon a failure.<br />2. Retry is not supported if errors are found using ODBC or JDBC.<br />3. For SQL statements with unlogged tables, the retry is not supported if a node is faulty.<br />4. For **gsql** client faults, the retry is not supported. | Value range of **retry_times**: 5-10                         |
+
+**Table 22** Large object meta-commands<a id="large"></a>
+
+| Parameter | Description                                                  |
+| :-------- | :----------------------------------------------------------- |
+| \\lo_list  | Displays a list of all MogDB large objects stored in the database, along with comments provided for them. |
+
+**PATTERN**
+
+The various **\\d** commands accept a **PATTERN** parameter to specify the object name to be displayed. In the simplest case, a pattern is just the exact name of the object. The characters within a pattern are normally folded to lower case, similar to those in SQL names. For example, **\\dt FOO** will display the table named **foo**. As in SQL names, placing double quotation marks (") around a pattern prevents them being folded to lower case. If you need to include a double quotation mark (") in a pattern, write it as a pair of double quotation marks ("") within a double-quote sequence, which is in accordance with the rules for SQL quoted identifiers. For example, `\dt "FOO""BAR"` will be displayed as a table named **FOO"BAR** instead of **foo"bar**. You cannot put double quotation marks around just part of a pattern, which is different from the normal rules for SQL names. For example, `\dt FOO"FOO"BAR` will be displayed as a table named **fooFOObar** if just part of a pattern is quoted.
+
+Whenever the **PATTERN** parameter is omitted completely, the **\d** commands display all objects that are visible in the current schema search path, which is equivalent to using an asterisk (\*) as the pattern. An object is regarded to be visible if it can be referenced by name without explicit schema qualification. To see all objects in the database regardless of their visibility, use a dot within double asterisks (*.*) as the pattern.
+
+Within a pattern, the asterisk (\*) matches any sequence of characters (including no characters) and a question mark (?) matches any single character. This notation is comparable to Unix shell file name patterns. For example, `\\dt` displays tables whose names begin with **int**. But within double quotation marks, the asterisk (\*) and the question mark (?) lose these special meanings and are just matched literally.
+
+A pattern that contains a dot (.)s interpreted as a schema name pattern followed by an object name pattern. For example, **\\dt foo.bar** displays all tables (whose names include **bar**) in schemas starting with **foo**. If no dot appears, then the pattern matches only visible objects in the current schema search path. Again, a dot within double quotation marks loses its special meaning and is matched literally.
+
+Advanced users can use regular-expression notations, such as character classes. For example [0-9] can be used to match any digit. All regular expression special characters, except the following, work as specified in POSIX regular expressions:
+
+- A dot (.) is used as a separator.
+- An asterisk (\*) is translated into an asterisk prefixed with a dot (.*), which is a regular-expression marking.
+- A question mark (?) is translated into a dot (.).
+- A dollar sign ($) is matched literally.
+
+You can, as required, write `?`, (`R+|`), (`R|`), and R to the following **PATTERN** characters: `.`, `R*`, and `R?`. The dollar sign ($) does not need to work as a regular-expression character since the pattern must match the whole name, which is different from the usual interpretation of regular expressions. In other words, the dollar sign ($) is automatically appended to your pattern. If you do not expect a pattern to be anchored, write an asterisk (\*) at its beginning or end. All regular-expression special characters within double quotation marks lose their special meanings and are matched literally. Regular-expression special characters in operator name patterns (such as the **\\do** parameter) are also matched literally.
+
+## FAQs
+
+**Low Connection Performance**
+
+- **log_hostname** is enabled, but DNS is incorrect.
+
+  Connect to the database, and run **show log_hostname** to check whether **log_hostname** is enabled in the database.
+
+  If it is enabled, the database kernel will use DNS to check the name of the host where the client is deployed. If the primary database node is configured with an incorrect or unreachable DNS server, the database connection will take a long time to set up. For details about this parameter, see the description of log_hostname in section "GUC Parameter Description &gt; Error Reports and Logs &gt; Log Content" in the *Developer Guide*.
+
+- The database kernel slowly runs the initialization statement.
+
+  Problems are difficult to locate in this scenario. Try using the **strace** Linux trace command.
+
+  ```bash
+  strace gsql -U MyUserName -W MyPassWord -d mogdb -h 127.0.0.1 -p 23508 -r -c '\q'
+  ```
+
+  The database connection process will be printed on the screen. If the following statement takes a long time to run:
+
+  ```bash
+  sendto(3, "Q\0\0\0\25SELECT VERSION()\0", 22, MSG_NOSIGNAL, NULL, 0) = 22
+  poll([{fd=3, events=POLLIN|POLLERR}], 1, -1) = 1 ([{fd=3, revents=POLLIN}])
+  ```
+
+  It indicates that the **SELECT VERSION()** statement was run slowly.
+
+  After the database is connected, you can run the **explain performance select version()** statement to find the reason why the initialization statement was run slowly. For more information, see "Performance Tuning &gt; SQL Tuning Guide &gt; SQL Execution Plan" in the *Developer Guide*.
+
+  An uncommon scenario is that the disk of the machine where the primary database node resides is full or faulty, affecting queries and leading to user authentication failures. As a result, the connection process is suspended. To solve this problem, simply clear the data disk space of the primary database node.
+
+- TCP connection is set up slowly.
+
+  Adapt the steps of troubleshooting slow initialization statement execution. Use **strace**. If the following statement is run slowly:
+
+  ```bash
+  connect(3, {sa_family=AF_FILE, path="/home/test/tmp/gaussdb_llt1/.s.PGSQL.61052"}, 110) = 0
+  ```
+
+  Or,
+
+  ```bash
+  connect(3, {sa_family=AF_INET, sin_port=htons(61052), sin_addr=inet_addr("127.0.0.1")}, 16) = -1 EINPROGRESS (Operation now in progress)
+  ```
+
+  It indicates that the physical connection between the client and the database is set up slowly. In this case, check whether the network is unstable or has high throughput.
+
+**Problems in Setting Up Connections**
+
+- gsql: could not connect to server: No route to host
+
+  This problem occurs generally because an unreachable IP address or port number was specified. Check whether the values of **-h** and **-p** parameters are correct.
+
+- gsql: FATAL: Invalid username/password,login denied.
+
+  This problem occurs generally because an incorrect username or password was entered. Contact the database administrator to check whether the username and password are correct.
+
+- gsql: FATAL: Forbid remote connection with trust method!
+
+  For security purposes, remote login in trust mode is forbidden. In this case, you need to modify the connection authentication information in the **pg_hba.conf** file. For details, see "Database Security Management &gt; Client Access Authentication &gt; Configuration File Reference" in the *Developer Guide*.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** Do not modify the configurations of the MogDB host in the **pg_hba. conf** file. Otherwise, the database may become faulty. It is recommended that service applications be deployed outside the MogDB.
+
+- If **-h 127.0.0.1** is specified, the database connection is successful. If **-h 127.0.0.1** is removed, the connection fails.
+
+  Run the **show unix_socket_directory** SQL statement to check whether the Unix socket directory used by the primary database node is the same as that specified by *$PGHOST* in the **shell** directory.
+
+  If they are different, set **$PGHOST** to the directory specified by **unix_socket_directory**.
+
+  For more information about **unix_socket_directory**, see "GUC Parameter Description &gt; Connection and Authentication &gt; Connection Settings" in the *Developer Guide*.
+
+- The "libpq.so" loaded mismatch the version of gsql, please check it.
+
+  This problem occurs because the version of **libpq.so** used in the environment does not match that of **gsql**. Run the **ldd gsql** command to check the version of the loaded **libpq.so**, and then load correct **libpq.so** by modifying the environment variable **LD_LIBRARY_PATH**.
+
+- gsql: symbol lookup error: xxx/gsql: undefined symbol: libpqVersionString
+
+  This problem occurs because the version of **libpq.so** used in the environment does not match that of **gsql** (or the PostgreSQL **libpq.so** exists in the environment). Run the **ldd gsql** command to check the version of the loaded **libpq.so**, and then load correct **libpq.so** by modifying the environment variable **LD_LIBRARY_PATH**.
+
+- gsql: connect to server failed: Connection timed out
+
+  Is the server running on host "xx.xxx.xxx.xxx" and accepting TCP/IP connections on port xxxx?
+
+  This problem is caused by network connection faults. Check the network connection between the client and the database server. If you cannot ping from the client to the database server, the network connection is abnormal. Contact network management personnel for troubleshooting.
+
+  ```bash
+  ping -c 4 10.10.10.1
+  PING 10.10.10.1 (10.10.10.1) 56(84) bytes of data.
+  From 10.10.10.1: icmp_seq=2 Destination Host Unreachable
+  From 10.10.10.1 icmp_seq=2 Destination Host Unreachable
+  From 10.10.10.1 icmp_seq=3 Destination Host Unreachable
+  From 10.10.10.1 icmp_seq=4 Destination Host Unreachable
+  --- 10.10.10.1 ping statistics ---
+  4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 2999ms
+  ```
+
+- gsql: FATAL: permission denied for database "mogdb"
+
+  DETAIL: User does not have CONNECT privilege.
+
+  This problem occurs because the user does not have the permission to access the database. To solve this problem, perform the following steps:
+
+  1. Connect to the database as the system administrator **dbadmin**.
+
+      ```bash
+      gsql -d mogdb -U dbadmin -p 15400
+      ```
+
+  2. Grant the user with the permission to access the database.
+
+      ```sql
+      GRANT CONNECT ON DATABASE mogdb TO user1;
+      ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** Actually, some common misoperations may also cause a database connection failure, for example, entering an incorrect database name, username, or password. Misoperations are accompanied with an error information on the client tool.
+  >
+  > ```bash
+  > gsql -d mogdb -p 15400
+  > gsql: FATAL:  database "mogdb" does not exist
+  > gsql -d mogdb -U user1 -W gauss@789 -p 15400
+  > gsql: FATAL:  Invalid username/password,login denied.
+  > ```
+
+- gsql: FATAL: sorry, too many clients already, active/non-active: 2/10/3.
+
+    This problem occurs because the number of system connections exceeds the upper limit. Contact the database administrator to release unnecessary sessions.
+
+    For details about how to view the number of user session connections.
+
+    You can view the session status in the **PG_STAT_ACTIVITY** view. To release unnecessary sessions, use the **pg_terminate_backend** function.
+
+    ```sql
+    select datid,pid,state from pg_stat_activity;
+     datid |       pid       | state
+    -------+-----------------+--------
+    13205 | 139834762094352 | active
+    13205 | 139834759993104 | idle
+    (2 rows)
+    ```
+
+    The value of **pid** is the thread ID of the session. Terminate the session using its thread ID.
+
+    ```sql
+    SELECT PG_TERMINATE_BACKEND(139834759993104);
+    PG_TERMINATE_BACKEND
+    ----------------------
+     t
+    (1 row)
+    ```
+
+  - View the maximum number of sessions connected to a specific user
+
+    Run the following command to view the upper limit of the number of **USER1**'s session connections. **-1** indicates that no upper limit is set for the number of **user1**'s session connections
+
+    ```sql
+    SELECT ROLNAME,ROLCONNLIMIT FROM PG_ROLES WHERE ROLNAME='user1';
+    rolname | rolconnlimit
+    --------+-----
+    user1    |           -1
+    (1 row)
+    ``
+
+  - View the maximum number of sessions connected to a specific database
+
+    Run the following command to view the upper limit of the number of **mogdb**'s session connections. **-1** indicates that no upper limit is set for the number of **mogdb**'s session connections
+
+    ```sql
+    SELECT DATNAME,DATCONNLIMIT FROM PG_DATABASE WHERE DATNAME='mogdb';
+    datname  | datconnlimit
+    ------+-----
+    mogdb |           -1 (1 row)
+    (1 row)
+    ```
+
+  - View the number of session connections that have been used by a specific database
+
+    Run the following command to view the number of session connections that have been used by **mogdb**. **1** indicates the number of session connections that have been used by **mogdb**.
+
+    ```sql
+    SELECT COUNT(*) FROM PG_STAT_ACTIVITY WHERE DATNAME='mogdb';
+    count
+    ------
+    1
+    (1 row)
+    ```
+
+- gsql: wait xxx.xxx.xxx.xxx:xxxx timeout expired
+
+    When **gsql** initiates a connection request to the database, a 5-minute timeout period is used. If the database cannot correctly authenticate the client request and client identity within this period, **gsql** will exit the connection process for the current session, and will report the above error.
+
+    Generally, this problem is caused by the incorrect host and port (that is, the *xxx* part in the error information) specified by the **-h** and **-p** parameters. As a result, the communication fails. Occasionally, this problem is caused by network faults. To resolve this problem, check whether the host name and port number of the database are correct.
+
+- gsql: could not receive data from server: Connection reset by peer.
+
+    Check whether primary database node logs contain information similar to "FATAL: cipher file "/data/dbnode/server.key.cipher" has group or world access". This error is usually caused by tampering with the permissions for data directories or some key files by mistake. For details about how to correct the permissions, see related permissions for files on other normal instances.
+
+- gsql: FATAL: GSS authentication method is not allowed because XXXX user password is not disabled.
+
+    In **pg_hba.conf** of the target primary database node, the authentication mode is set to **gss** for authenticating the IP address of the current client. However, this authentication algorithm cannot authenticate clients. Change the authentication algorithm to **sha256** and try again. For details, see "Database Security Management &gt; Client Access Authentication &gt; Configuration File Reference" in the *Developer Guide*.
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+    >
+    > - Do not modify the configurations of the MogDB host in the **pg_hba. conf** file. Otherwise, the database may become faulty.
+    > - It is recommended that service applications be deployed outside the MogDB.
+
+**Other Faults**
+
+- There is a core dump or abnormal exit due to the bus error.
+
+    Generally, this problem is caused by changes in loading the shared dynamic library (.so file in Linux) during process running. Alternatively, if the process binary file changes, the execution code for the OS to load machines or the entry for loading a dependent library will change accordingly. In this case, the OS kills the process for protection purposes, generating a core dump file.
+
+    To resolve this problem, try again. In addition, do not run service programs in MogDB during O&M operations, such as an upgrade, preventing such a problem caused by file replacement during the upgrade.
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** A possible stack of the core dump file contains dl_main and its function calling. The file is used by the OS to initialize a process and load the shared dynamic library. If the process has been initialized but the shared dynamic library has not been loaded, the process cannot be considered completely started.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/0-gs_cgroup.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/0-gs_cgroup.md
new file mode 100644
index 0000000000000000000000000000000000000000..2b3d4343dfc010c96fd208c4a5d09c4a2faed796
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/0-gs_cgroup.md
@@ -0,0 +1,421 @@
+---
+title: gs_cgroup
+summary: gs_cgroup
+author: Zhang Cuiping
+date: 2021-11-17
+---
+
+# gs_cgroup
+
+## Background
+
+When jobs are batch processed in a cluster, loads on servers significantly vary due to the complexity of batch processing. To fully use cluster resources, you need to manage loads. **gs_cgroup** is a load management tool provided by MogDB. It can create default Cgroups and user-defined Cgroups, delete default and user-defined Cgroups, update resource quotas and allocations, display the configuration files of Cgroups and the Cgroup tree, and delete all Cgroups.
+
+**gs_cgroup** creates Cgroups configuration files for the OS user of a database and generates Cgroups that the OS user sets in the OS. **gs_cgroup** also allows users to add or delete Cgroups, update Cgroup resource quotas, allocate CPU cores or I/O resources, set exception thresholds, and handle the exceptions. **gs_cgroup** is responsible only for Cgroups operations performed on the node where the current OS resides, and needs to be centrally configured across nodes by invoking the same statement.
+
+For details, see "Resource Load Management" in *Developer Guide*.
+
+## Examples
+
+- Commands executed by a common user or the database administrator:
+
+  1. Prerequisites: The *GAUSSHOME* environment variable is used as the database installation directory and user **root** has created default Cgroups for common users.
+
+  2. Create Cgroups and set corresponding resource quota so that jobs of the database can be specified to a Cgroup and use its resources. The database administrator creates Class Cgroups for each database user.
+
+     1. Create class and workload Cgroups.
+
+        ```
+        gs_cgroup -c -S class1 -s 40
+        ```
+
+        Create the **class1** Cgroup and allocate 40% of Class resources to it.
+
+        ```
+        gs_cgroup -c -S class1 -G grp1 -g 20
+        ```
+
+        Create the **grp1** Workload Cgroup under the **class1** Cgroup and allocate 20% of **class1** Cgroup resources to the Workload Cgroup.
+
+     2. Delete the created **grp1** Cgroup and **class1** Cgroup.
+
+        ```
+        gs_cgroup -d -S class1 -G grp1
+        ```
+
+        Delete the created **grp1** Cgroup.
+
+        ```
+        gs_cgroup -d -S class1
+        ```
+
+        Delete the created **class1** Cgroup.
+
+        > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** If a Class Cgroup is deleted, its Workload Cgroups will be deleted as well.
+
+  3. Update the resource quota for created Cgroups.
+
+     1. Update dynamic resource quota.
+
+        ```
+        gs_cgroup -u -S class1 -G grp1 -g 30
+        ```
+
+        Update the resources allocated to the **grp1** Workload Cgroup under the **class1** Cgroup for the current user to 30% of **class1** resources.
+
+     2. Update the resource limitation quota.
+
+        ```
+        gs_cgroup --fixed -u -S class1 -G grp1 -g 30
+        ```
+
+        Set the number of CPU cores allocated to the **grp1** Cgroup to 30% of cores allocated to its parent Cgroup **class1**.
+
+  4. Update the range of the CPU cores in the **Gaussdb** Cgroup.
+
+     ```
+     gs_cgroup -u -T Gaussdb -f 0-20
+     ```
+
+     Update the number of CPU cores used by the GaussDB process to 0-20.
+
+     > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The **-f** parameter can only be used to set the range of the CPU cores in the **Gaussdb** Cgroup. For other Cgroups, if you need to set the number of cores, use the **-fixed** parameter.
+
+  5. Set exception handling information. (**class:wg** group must exist.)
+
+     1. Terminate a job under the **class:wg** Cgroup when job congestion lasts for 1200s or job execution lasts for 2400s.
+
+        ```
+        gs_cgroup -S class -G wg -E "blocktime=1200,elapsedtime=2400" -a
+        ```
+
+     2. Specify the termination action performed when the size of spilled job data in the **class:wg** group reaches 256 MB or the size of broadcast job data in the group reaches 100 MB.
+
+        ```
+        gs_cgroup -S class -G wg -E "spillsize=256,broadcastsize=100" -a
+        ```
+
+     3. Demote a job under the Class Cgroup when the total CPU time taken to execute the job on all DNs reaches 100s.
+
+        ```
+        gs_cgroup -S class -E "allcputime=100" --penalty
+        ```
+
+     4. Demote a job under the Class Cgroup when the total time taken to execute the job on all DNs reaches 2400s and the skew of the CPU time reaches 90 percent.
+
+        ```
+        gs_cgroup -S class -E "qualificationtime=2400,cpuskewpercnt=90"
+        ```
+
+        > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** To set exception handling information for a Cgroup, ensure that the Cgroup has been created. Multiple specified thresholds are separated by commas (,). If no operation is specified, **-penalty** is used by default.
+
+  6. Set the number of cores per CPU have for a Cgroup.
+
+     Set the range of cores for the **class:wg** Cgroup to 20% of Class cores.
+
+     ```
+     gs_cgroup -S class -G wg -g 20 --fixed -u
+     ```
+
+     > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** The range of cores for the Class or Workload Cgroup must be specified by the **-fixed** parameter.
+
+  7. Roll back the previous step.
+
+     ```
+     gs_cgroup --recover
+     ```
+
+     > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The **-recover** parameter can only roll back the latest addition, deletion, or modification made to the Class and Workload Cgroups.
+
+  8. View information about Cgroups that have been created.
+
+     1. View Cgroup information in configuration files.
+
+        ```bash
+        gs_cgroup -p
+        ```
+
+        Cgroup configuration
+
+        ```bash
+        gs_cgroup -p
+
+        Top Group information is listed:
+        GID:   0 Type: Top    Percent(%): 1000( 50) Name: Root                  Cores: 0-47
+        GID:   1 Type: Top    Percent(%):  833( 83) Name: Gaussdb:omm           Cores: 0-20
+        GID:   2 Type: Top    Percent(%):  333( 40) Name: Backend               Cores: 0-20
+        GID:   3 Type: Top    Percent(%):  499( 60) Name: Class                 Cores: 0-20
+
+        Backend Group information is listed:
+        GID:   4 Type: BAKWD  Name: DefaultBackend   TopGID:   2 Percent(%): 266(80) Cores: 0-20
+        GID:   5 Type: BAKWD  Name: Vacuum           TopGID:   2 Percent(%):  66(20) Cores: 0-20
+
+        Class Group information is listed:
+        GID:  20 Type: CLASS  Name: DefaultClass     TopGID:   3 Percent(%): 166(20) MaxLevel: 1 RemPCT: 100 Cores: 0-20
+        GID:  21 Type: CLASS  Name: class1           TopGID:   3 Percent(%): 332(40) MaxLevel: 2 RemPCT:  70 Cores: 0-20
+
+        Workload Group information is listed:
+        GID:  86 Type: DEFWD  Name: grp1:2           ClsGID:  21 Percent(%):  99(30) WDLevel:  2 Quota(%): 30 Cores: 0-5
+
+        Timeshare Group information is listed:
+        GID: 724 Type: TSWD   Name: Low              Rate: 1
+        GID: 725 Type: TSWD   Name: Medium           Rate: 2
+        GID: 726 Type: TSWD   Name: High             Rate: 4
+        GID: 727 Type: TSWD   Name: Rush             Rate: 8
+
+        Group Exception information is listed:
+        GID:  20 Type: EXCEPTION Class: DefaultClass
+        PENALTY: QualificationTime=1800 CPUSkewPercent=30
+
+        GID:  21 Type: EXCEPTION Class: class1
+        PENALTY: AllCpuTime=100 QualificationTime=2400 CPUSkewPercent=90
+
+        GID:  86 Type: EXCEPTION Group: class1:grp1:2
+        ABORT: BlockTime=1200 ElapsedTime=2400
+        ```
+
+     2. View the Cgroup tree in the OS.
+
+        **gs_cgroup -P** displays a Cgroup tree. In the tree, **shares** indicates the value of **cpu.shares**, which specifies the dynamic quota of CPU resources in the OS, and **cpus** indicates the value of **cpuset.cpus**, which specifies the dynamic quota of CPUSET resources in the OS (number of cores that a Cgroup can use).
+
+        ```bash
+        gs_cgroup -P
+        Mount Information:
+        cpu:/dev/cgroup/cpu
+        blkio:/dev/cgroup/blkio
+        cpuset:/dev/cgroup/cpuset
+        cpuacct:/dev/cgroup/cpuacct
+
+        Group Tree Information:
+        - Gaussdb:wangrui (shares: 5120, cpus: 0-20, weight: 1000)
+                - Backend (shares: 4096, cpus: 0-20, weight: 400)
+                        - Vacuum (shares: 2048, cpus: 0-20, weight: 200)
+                        - DefaultBackend (shares: 8192, cpus: 0-20, weight: 800)
+                - Class (shares: 6144, cpus: 0-20, weight: 600)
+                        - class1 (shares: 4096, cpus: 0-20, weight: 400)
+                                - RemainWD:1 (shares: 1000, cpus: 0-20, weight: 100)
+                                        - RemainWD:2 (shares: 7000, cpus: 0-20, weight: 700)
+                                                - Timeshare (shares: 1024, cpus: 0-20, weight: 500)
+                                                        - Rush (shares: 8192, cpus: 0-20, weight: 800)
+                                                        - High (shares: 4096, cpus: 0-20, weight: 400)
+                                                        - Medium (shares: 2048, cpus: 0-20, weight: 200)
+                                                        - Low (shares: 1024, cpus: 0-20, weight: 100)
+                                        - grp1:2 (shares: 3000, cpus: 0-5, weight: 300)
+                                - TopWD:1 (shares: 9000, cpus: 0-20, weight: 900)
+                        - DefaultClass (shares: 2048, cpus: 0-20, weight: 200)
+                                - RemainWD:1 (shares: 1000, cpus: 0-20, weight: 100)
+                                        - Timeshare (shares: 1024, cpus: 0-20, weight: 500)
+                                                - Rush (shares: 8192, cpus: 0-20, weight: 800)
+                                                - High (shares: 4096, cpus: 0-20, weight: 400)
+                                                - Medium (shares: 2048, cpus: 0-20, weight: 200)
+                                                - Low (shares: 1024, cpus: 0-20, weight: 100)
+                                - TopWD:1 (shares: 9000, cpus: 0-20, weight: 900)
+        ```
+
+## Parameter Description
+
+- -a [-abort]
+
+  Terminates a job when it exceeds an exception threshold.
+
+- -b pct
+
+  Specifies the percentage of resources of the **Top Backend** Cgroup taken by a Backend Cgroup. The **-B** *backendname* parameter must be specified as well.
+
+  Value Range
+
+  The value ranges from 1 to 99.
+
+  If this parameter is not set, the default CPU quota accounts for 20% of the Vacuum Cgroup and **80%** of the DefaultBackend Cgroup, respectively. The quota sum for the Vacuum and DefaultBackend Cgroups must be less than 100%.
+
+- -B name
+
+  Specifies the name of a Backend Cgroup. Only the **-u** parameter can be used to change the resource quota for this Cgroup.
+
+  The **-b percent** and **-B** *backendname* parameters need to be specified to set the resource proportion of database backend threads.
+
+  Value range: a string with a maximum of 64 bytes.
+
+- -c
+
+  Creates a Cgroup and specifies its name.
+
+  A common user can specify **-c** and **-S** *classname* to create a Class Cgroup. If **-G** *groupname* is specified as well, a Workload Cgroup will be created under the Class Cgroup. The Workload Cgroup is at the bottom layer in the Class Cgroup (Layer-4 is the bottom layer.)
+
+- -d
+
+  Deletes Cgroups.
+
+  A common user can specify **-d** and **-S** *classname* parameters to delete the created **Class** Cgroups. If the **-G** *groupname* parameter is specified as well, a **Workload** Cgroup under the **Class** Cgroup is deleted, and related threads are put into the **DefaultClass:DefaultWD:1** Cgroup. If the **Workload** Cgroups to be deleted locate at a high level (Level 1 is the top level), adjust hierarchy of lower-level Cgroups, create the new Cgroups-related threads, and load them to the new Cgroups.
+
+- -E data
+
+  Specifies the exception thresholds, including **blocktime**, **elapsedtime**, **allcputime**, **spillsize**, **broadcastsize**, **qualificationtime**, and **cpuskewpercent**. The thresholds are separated by commas (,). **0** indicates that the setting is canceled. If the parameter is set to an invalid value, an error will be prompted.
+
+  **Table 2** Exception threshold types
+
+  | Exception Threshold Type | Description                                                  | Value Range (**0** Indicates Setting Canceled) | Operation upon Exception |
+  | :----------------------- | :----------------------------------------------------------- | :--------------------------------------------- | :----------------------- |
+  | blocktime                | Job blocking duration. The unit is second. **blocktime** includes the total time spent in global and local concurrent queuing. | 0-UINT_MAX                                     | abort                    |
+  | elapsedtime              | Execution time of a job that has not been finished. The unit is second. The time indicates the duration from the start point of execution to the current time point. | 0-UINT_MAX                                     | abort                    |
+  | allcputime               | Total CPU time spent in executing a job on all DNs. The unit is second. | 0-UINT_MAX                                     | abort, penalty           |
+  | cpuskewpercent           | CPU time skew of a job executed on DNs. The value depends on the setting of **qualificationtime**. | 0~100                                          | abort, penalty           |
+  | qualificationtime        | Interval for checking the CPU skew. The unit is second. This parameter must be set together with **cpuskewpercent**. | 0-UINT_MAX                                     | none                     |
+  | spillsize                | Amount of job data spilled to disks on DNs. The unit is MB.  | 0-UINT_MAX                                     | abort                    |
+  | broadcastsize            | Size of broadcast operators of a job on DNs. The unit is MB. | 0-UINT_MAX                                     | abort                    |
+
+- -h [-help]
+
+  Displays the command help information.
+
+- -H
+
+  Collects **$GAUSSHOME** information among the current users.
+
+  Value range: a string with a maximum of 1023 characters.
+
+- -f
+
+  Specifies the range of core quantity used by the **Gaussdb** Cgroup. The range format can be *a-b* or *a*. For other Cgroups, use the **-fixed** parameter to set the range of core quantity.
+
+- -fixed
+
+  Specifies the percentage of cores allocated for a Cgroup's parent group that the Cgroup can use, or specifies the I/O resources.
+
+  **-fixed** is set together with **-s**, **-g**, **-t**, and **-b** when the kernel range ratio is set.
+
+  The ratio is between 0 and 100. The sum of kernels of the same level is less than or equal to 100. The value **0** indicates that the kernel number of a level is same as that of the upper level. The CPU quota for all the Cgroups is set to **0** by default. **-f** and **-fixed** cannot be configured at the same time. After **-fixed** is set, the **-f** range will be automatically invalid. The ratio will be displayed in **-p** as the quota value.
+
+  When the I/O resource quota is set, **-R**, **-r**, **-W**, and **-w** are used together.
+
+- -g pct
+
+  Specifies the percentage of resources in a Class Cgroup taken by a Workload Cgroup. The **-G** *groupname* parameter needs to be specified as well. The **-g pct** parameter can be used with the **-c** parameter to create a Cgroup or with the **-u** parameter to update a Workload Cgroup.
+
+  Value range: 1 to 99. By default, the CPU quota of a Workload Cgroup is 20%. The sum of CPU quotas for all Workload Cgroups must be less than 99%.
+
+- -G name
+
+  Specifies the name of a Workload Cgroup. The **-S** *classname* parameter needs to be set to specify the Class Cgroup to which the Workload Cgroup belongs. The **-G** *name* parameter can be used with **-c** to create a Cgroup, with **-d** to delete a Cgroup, and with **-u** to update the resource quota for a Cgroup. Note that *name* in the **-G** *name* parameter cannot be a default Timeshare Cgroup name, including **Low**, **Medium**, **High**, and **Rush**.
+
+  If a user creates a Workload Cgroup, the name must contain any colons (:). Names of Cgroups must be different.
+
+  Value range: a string with a maximum of 28 bytes
+
+- -N [-group] name
+
+  Shows the Cgroup name, **class:wg** for short.
+
+- -p
+
+  Shows information about Cgroup configuration files.
+
+- -P
+
+  Shows the structure of the Cgroup tree.
+
+- -penalty
+
+  Demotes a job when the job exceeds an exception threshold. If no operation is specified, **-penalty** is used by default.
+
+- -r data
+
+  Only updates the upper limit of data reading for I/O resources, that is, sets the value of **blkio.throttle.read_bps_device**. This parameter is a string consisting of **major:minor value**, in which **major** indicates the major device number of the disk to be accessed,**minor** indicates the minor device number, and **value** indicates the upper limit of the number of read operations. The upper limit ranges from **0** to **ULONG_MAX**, and **0** indicates that the number of read operations is not restricted. This parameter needs to be used with the **-u** parameter and Cgroup names. If both the **Class** Cgroup name and **Workload** Cgroup name are specified, this parameter is used for the **Workload** Cgroup.
+
+  Value range: a string with a maximum of 32 characters.
+
+- -R data
+
+  Only updates the upper limit of I/O resources used to read data per second, that is, sets the value of **blkio.throttle.read_iops_device**. The value of this parameter is the same as that of the **-r** parameter. This parameter needs to be used with the **-u** parameter and Cgroup names. If both the **Class** Cgroup name and **Workload** Cgroup name are specified, this parameter is used for the **Workload** Cgroup.
+
+  Value range: a string with a maximum of 32 characters.
+
+- -recover
+
+  Rolls back only the latest addition, deletion, or modification made to the Class and Workload Cgroups.
+
+- -revert
+
+  Restores to the default status of the Cgroup.
+
+- -D mpoint
+
+  Specifies a mount point. The default mount point is **/dev/cgroup/subsystem**.
+
+- -m
+
+  Mounts the Cgroup.
+
+- -M
+
+  Unmounts the Cgroup.
+
+- -U
+
+  Specifies the database username.
+
+- -refresh
+
+  Updates the status of the Cgroup.
+
+- -s pct
+
+  Specifies the percentage of resources in the top **Class** Cgroup taken by a **Class** Cgroup. The **-S** *classname* parameter needs to be specified as well. The **-s pct** parameter can be used with the **-c** parameter to create a Cgroup or with the **-u** parameter to update a **Class** Cgroup.
+
+  Value range: 1 to 99. By default, the CPU quota of the Class Cgroup is set to 20%. In R6C10, the CPU quota of the Class Cgroup is set to 40%. During the upgrade, the quota is not updated. The sum of the CPU quota of the newly created Class Cgroup and the default **DefaultClass** quota must be less than 100%.
+
+- -S name
+
+  Specifies the name of a Class Cgroup. This parameter can be used with **-c** to create a Cgroup, with **-d** to delete a Cgroup, or with **-u** to update resource quota for a Cgroup. The name of a sub-Class Cgroup cannot contain the colon (:).
+
+  Value range: a string with a maximum of 31 bytes.
+
+- -t percent
+
+  Specifies the percentage of resources for top Cgroups (**Root**, **Gaussdb**: omm, Backend, and Class Cgroups). The **-T name** parameter needs to be specified as well. If this parameter is used to specify resource percentage for the **-T Root** Cgroup, the name shown in the Cgroup configuration file is **Root**. *percent* indicates the percentage of the value of **blkio.weight**, and its minimum value is **10%**. The CPU resource quota, such as the value of **cpu.shares** cannot be changed. If this parameter is used to specify resource percentage for the **Gaussdb:omm** Cgroup, the parameter value indicates the percentage of CPU resources taken by the **Gaussdb:omm** Cgroup. (The **cpu.shares** value for the **Gaussdb:omm** Cgroup can be obtained based on the quota 1024 for the **Root** Cgroup and the condition that only one database is available for the current system.) The I/O resource quota is 1000 and will not change. If this parameter is used to specify resource percentage for the **Class** or **Backend** Cgroup, the parameter value indicates the percentage of resources in the **Gaussdb** Cgroup taken by the **Class** or **Backend** Cgroup.
+
+  Value range: 1 to 99. By default, the quota of the Class Cgroup is 60%, and the quota of the Backend Cgroup is 40%. Modify the quota of the Class Cgroup and automatically update the quota of the Backend Cgroup so that the sum quota of the Backend and Class Cgroups is 100%.
+
+- -T name
+
+  Specifies the names of top Cgroups.
+
+  Value range: a string with a maximum of 64 bytes.
+
+- -u
+
+  Updates Cgroups.
+
+- -V [-version]
+
+  Displays version information about the **gs_cgroup** tool.
+
+- -w data
+
+  Only updates the upper limit of I/O resources used to write data per second, that is, sets the value of **blkio.throttle.write_bps_device**. The value of this parameter is the same as that of the **-r** parameter. The **-u** parameter and the Cgroup name need to be specified as well. If both the **Class** Cgroup name and **Workload** Cgroup name are specified, this parameter is used for the **Workload** Cgroup.
+
+  Value range: a string with a maximum of 32 characters.
+
+- -W data
+
+  Only updates the upper limit of I/O resources used to write data per second, that is, sets the value of **blkio.throttle.write_iops_device**. The value of this parameter is the same as that of the **-r** parameter. The **-u** parameter and the Cgroup name need to be specified as well. If both the **Class** Cgroup name and **Workload** Cgroup name are specified, this parameter is used for the **Workload** Cgroup.
+
+  Value range: a string with a maximum of 32 characters.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** Use the following method to obtain the **major:minor** value for the disk. For example, obtain the number of the disk corresponding to the **/mpp** directory.
+>
+> ```bash
+> df
+> Filesystem      1K-blocks      Used  Available Use% Mounted on
+> /dev/sda1       524173248  41012784  456534008   9% /
+> devtmpfs         66059264       236   66059028   1% /dev
+> tmpfs            66059264        88   66059176   1% /dev/shm
+> /dev/sdb1      2920486864 135987592 2784499272   5% /data
+> /dev/sdc1      2920486864  24747868 2895738996   1% /data1
+> /dev/sdd1      2920486864  24736704 2895750160   1% /mpp
+> /dev/sde1      2920486864  24750068 2895736796   1% /mpp1
+> ls -l /dev/sdd
+> brw-rw---- 1 root disk 8, 48 Feb 26 11:20 /dev/sdd
+> ```
+>
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** Check the disk number of sdd rather than sdd1. Otherwise, an error will be reported. If the length of I/O quota limitation after the upgrade exceeds the allowed maximum length of the string, the update will not be saved in the configuration file. If the maximum length of the string is set to 96 and I/O resources of more than eight disks are updated, the string limitation may be exceeded. The update will not be saved in the configuration file though the update succeeds.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/1-gs_check.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/1-gs_check.md
new file mode 100644
index 0000000000000000000000000000000000000000..3874e58d966a463d075fb139adcd92abc59937fb
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/1-gs_check.md
@@ -0,0 +1,1373 @@
+---
+title: gs_check
+summary: gs_check
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_check
+
+## Background
+
+**gs_check** has been enhanced to unify functions of various check tools, such as gs_check and gs_checkos. It helps you fully check MogDB runtime, OS, network, and database running environments; as well as perform comprehensive checks on various environments before major operations in MogDB, ensuring smooth operation.
+
+## Precautions
+
+- Parameter **-i** or **-e** must be set. **-i** specifies a single item to be checked, and **-e** specifies an inspection scenario where multiple items will be checked.
+- If **-i** is not set to a root item or no such items are contained in the check item list of the scenario specified by **-e**, you do not need to enter the name or password of a user with the root permissions.
+- You can run **-skip-root-items** to skip root items.
+- If the MTU values are inconsistent, the check may be slow or the check process may fail to respond. When the inspection tool displays a message, change the MTU values of the nodes to be the same and then perform the inspection.
+- If the switch does not support the configured MTU value, process response failures may be caused due to communication problems even if the MTU values are the same. In this case, you need to adjust the MTU based on the switch.
+
+## Syntax
+
+- Check a single-item.
+
+  ```bash
+  gs_check -i ITEM [...] [-U USER] [-L] [-l LOGFILE] [-o OUTPUTDIR] [--skip-root-items][--set][--routing]
+  ```
+
+- Check a scenario.
+
+  ```bash
+  gs_check -e SCENE_NAME [-U USER] [-L] [-l LOGFILE] [-o OUTPUTDIR] [--skip-root-items] [--time-out=SECS][--set][--routing][--skip-items]
+  ```
+
+- Display help information.
+
+  ```bash
+  gs_check -? | --help
+  ```
+
+- Display version information.
+
+  ```bash
+  gs_check -V | --version
+  ```
+
+## Parameter Description
+
+- -U
+
+  Specifies the name of the user for running MogDB.
+
+  Value range: Name of the user for running MogDB
+
+- -L
+
+  Specifies that the check is locally performed.
+
+- -i
+
+  Specifies a check item. Its format is **-i Check** *XX*. For details about check items, see [MogDB status checklist](#mogdb-status-checklist).
+
+- -e
+
+  Specifies scenario check items. Default scenarios include **inspect** (routine inspection), **upgrade** (pre-upgrade inspection), **binary_upgrade** (local pre-upgrade inspection), **health** (health check inspection), and **install** (installation). You can also compile scenarios as required.
+
+- -l
+
+  Specifies a log file path, Add the .log suffix when specifying the path.
+
+- -o
+
+  Specifies the path of the check result output folder.
+
+- -skip-root-items
+
+  Skips the check items that require root permissions.
+
+- -skip-items
+
+  Skips specified check items.
+
+- -format
+
+  Specifies the format of the result report.
+
+- -set
+
+  Specifies abnormal items that can be fixed.
+
+- -cid
+
+  Checks the ID used only by the internal check process.
+
+- -time-out
+
+  Specifies the timeout period. The unit is second. If the user-defined timeout period is not less than 1500 seconds, the default value (1500 seconds) is used.
+
+- -routing
+
+  Specifies the network segment for service IP addresses. The format is *IP address*:*Subnet mask*.
+
+- -disk-threshold=PERCENT
+
+  Specifies the alarm threshold when you check disk usage. You can specify the integer value that ranges from 1 to 99. The default value is **90**. This parameter is not mandatory for other check items.
+
+- -?, -help
+
+  Displays help information.
+
+- -V, -version
+
+    Displays version information.
+
+### MogDB status checklist
+
+- OS
+    <table>
+        <tr>
+            <td>Check Item</td>
+            <td>Description</td>
+            <td>-set Supported or Not</td>
+        </tr>
+        <tr>
+            <td>CheckCPU</td>
+            <td>
+            Checks the CPU usage of the host. If <b>idle</b> is greater than 30% and
+            <b>iowait</b> is less than 30%, this item passes the check. Otherwise,
+            this item fails the check.
+            </td>
+            <td>No</td>
+        </tr>
+        <tr>
+            <td>CheckFirewall</td>
+            <td>
+            Checks the firewall status of the host. If the firewall is disabled, this
+            item passes the check. Otherwise, this item fails the check.
+            </td>
+            <td>Yes</td>
+        </tr>
+        <tr>
+            <td>CheckTimeZone</td>
+            <td>
+            Checks whether nodes in openGauss use the same time zone. If they do, this
+            item passes the check. Otherwise, this item fails the check.
+            </td>
+            <td>No</td>
+        </tr>
+        <tr>
+            <td>CheckSysParams</td>
+            <td>
+            Checks whether the values of OS parameters for each node are as expected.
+            If the parameters do not meet the requirements of the warning field, a
+            warning is reported. If the parameters do not meet the requirements of the
+            NG field, this item fails the check, and the failed parameters are
+            printed.
+            </td>
+            <td>Yes</td>
+        </tr>
+        <tr>
+            <td>CheckOSVer</td>
+            <td>
+            Check the OS version of each node in openGauss. If versions are consistent
+            with those in the version compatibility list and information about
+            versions of OSs running on nodes in openGauss is included in the same
+            version list, the item passes the check. Otherwise, this item fails the
+            check.
+            </td>
+            <td>No</td>
+        </tr>
+        <tr>
+            <td>CheckNTPD</td>
+            <td>
+            Checks the NTPD service. If the service is enabled and the time difference
+            across nodes is within 1 minute, this item passes the check. Otherwise,
+            this item fails the check.
+            </td>
+            <td>No</td>
+        </tr>
+        <tr>
+            <td>CheckTHP</td>
+            <td>
+            Checks the THP service. If the service is enabled, this item passes the
+            check. Otherwise, this item fails the check.
+            </td>
+            <td>Yes</td>
+        </tr>
+        <tr>
+            <td>CheckSshdService</td>
+            <td>
+            Checks whether the sshd service is started. If yes, this item passes the
+            check. Otherwise, this item fails the check.
+            </td>
+            <td>No</td>
+        </tr>
+        <tr>
+            <td>CheckCrondService</td>
+            <td>
+            Checks whether the crontab service is started. If yes, this item passes
+            the check. Otherwise, this item fails the check.
+            </td>
+            <td>Yes<br /></td>
+        </tr>
+        <tr>
+            <td>CheckCrontabLeft</td>
+            <td>
+            Checks whether the crontab file contains remaining Gauss information. If
+            no, this item passes the check. Otherwise, this item fails the check.
+            </td>
+            <td>Yes</td>
+        </tr>
+        <tr>
+            <td>CheckDirLeft</td>
+            <td>
+            Checks whether the <b>/opt/enmo/Bigdata/</b>, <b>/var/log/Bigdata/</b>,
+            and <b>/home/omm</b> directories exist. If they do not exist or exist only
+            in the <b>mount</b> directory, this item passes the check. Otherwise, this
+            item fails the check.
+            </td>
+            <td>Yes</td>
+        </tr>
+        <tr>
+            <td>CheckProcessLeft</td>
+            <td>
+            Checks whether the gaussdb and omm processes exist. If no, this item
+            passes the check. Otherwise, this item fails the check.
+            </td>
+            <td>Yes</td>
+        </tr>
+        <tr>
+            <td>CheckStack</td>
+            <td>
+            Checks stack depths. If the stack depths across nodes are inconsistent, a
+            warning is reported. If the stack depths are consistent and greater than
+            or equal to 3072, this item passes the check. If the stack depths are
+            consistent but less than 3072, this item fails the check.
+            </td>
+            <td>Yes</td>
+        </tr>
+        <tr>
+            <td>CheckOmmUserExist</td>
+            <td>
+            Checks whether user <b>omm</b> exists. If no, this item passes the check.
+            Otherwise, this item fails the check.
+            </td>
+            <td>Yes</td>
+        </tr>
+        <tr>
+            <td>CheckPortConflict</td>
+            <td>
+            Checks whether database node ports are occupied. If they are not, this
+            item passes the check. Otherwise, this item fails the check.
+            </td>
+            <td>Yes</td>
+        </tr>
+        <tr>
+            <td>CheckSysPortRange</td>
+            <td>
+            Checks the value range of the system parameter <b>ip_local_port_range</b>.
+            If the value range is 26000 to 65535, this item passes the check.
+            Otherwise, this item fails the check.
+            </td>
+            <td>Yes</td>
+        </tr>
+        <tr>
+            <td>CheckEtcHosts</td>
+            <td>
+            If <b>localhost</b> is not configured for <b>/etc/hosts,</b> there is a
+            mapping whose comment contains <b>#openGauss</b>, or the names of hosts
+            having the same IP address are different, this item fails the check.
+            Otherwise, this item passes the check. In addition, if host names are the
+            same but IP addresses are different, this item also fails the check.
+            </td>
+            <td>No</td>
+        </tr>
+        <tr>
+            <td>CheckCpuCount</td>
+            <td>
+            Checks the number of CPU cores. If the number is different from that of
+            available CPUs, this item fails the check. If the two numbers are the same
+            but unavailability messages exist, a warning is reported. If the CPU
+            information of all nodes is different, this item fails the check.
+            </td>
+            <td>No</td>
+        </tr>
+        <tr>
+            <td>CheckHyperThread</td>
+            <td>
+            Checks hyper-threading. If it is started, this item passes the check.
+            Otherwise, this item fails the check.
+            </td>
+            <td>No</td>
+        </tr>
+        <tr>
+            <td>CheckMemInfo</td>
+            <td>
+            Checks whether the total memory size of each node is the same. If yes,
+            this item passes the check. Otherwise, a warning is reported.
+            </td>
+            <td>No</td>
+        </tr>
+        <tr>
+            <td>CheckSshdConfig</td>
+            <td>
+            Checks the <b>/etc/ssh/sshd_config</b> file.<br />
+            (a)PasswordAuthentication=yes; <br />
+            (b)MaxStartups=1000; <br />
+            (c)UseDNS=no; <br />
+            (d) <b>ClientAliveInterval</b> is greater than 10800 or equal to 0. <br />
+            If the above information is configured, this item passes the check. If a
+            and c configurations are incorrect, a warning is reported. If b and d
+            configurations are incorrect, this item fails the check.
+            </td>
+            <td>Yes</td>
+        </tr>
+        <tr>
+            <td>CheckMaxHandle</td>
+            <td>
+            Checks the maximum handle value of the OS. If the value is greater than or
+            equal to 1 million, this item passes the check. Otherwise, this item fails
+            the check.
+            </td>
+            <td>Yes</td>
+        </tr>
+        <tr>
+            <td>CheckKernelVer</td>
+            <td>
+            Checks the kernel version of each node. If the version information is
+            consistent, this item passes the check. Otherwise, a warning is reported.
+            </td>
+            <td>No</td>
+        </tr>
+        <tr>
+            <td>CheckEncoding</td>
+            <td>
+            Checks the system code of each node in openGauss. If the codes are
+            consistent, this item passes the check. Otherwise, this item fails the
+            check.
+            </td>
+            <td>No</td>
+        </tr>
+        <tr>
+            <td>CheckBootItems</td>
+            <td>
+            Checks whether there are manually added startup items. If no, this item
+            passes the check. Otherwise, this item fails the check.
+            </td>
+            <td>No</td>
+        </tr>
+        <tr>
+            <td>CheckDropCache</td>
+            <td>
+            Checks whether there is a dropcache process running on each node. If yes,
+            this item passes the check. Otherwise, this item fails the check.
+            </td>
+            <td>No</td>
+        </tr>
+        <tr>
+            <td>CheckFilehandle</td>
+            <td>
+            Checks the following conditions. If both the conditions are met, this item
+            passes the check. Otherwise, this item fails the check.<br />- The number
+            of processes opened by each gaussdb process does not exceed 800,000.<br />-
+            The number of handles used by the slave process does not exceed that of
+            handles used by the master process.
+            </td>
+            <td>No</td>
+        </tr>
+        <tr>
+            <td>CheckKeyProAdj</td>
+            <td>
+            Checks all key processes. If the <b>omm_adj</b> value for all key
+            processes is <b>0</b>, this item passes the check. Otherwise, this item
+            fails the check.
+            </td>
+            <td>No</td>
+        </tr>
+        <tr>
+            <td>CheckMaxProcMemory</td>
+            <td>
+            Checks whether the value of <b>max_process_memory</b> on the database
+            nodes is greater than 1 GB. If no, this item passes the check. Otherwise,
+            this item fails the check.
+            </td>
+            <td>Yes</td>
+        </tr>
+    </table>
+
+- Device
+
+    <table>
+      <tr>
+        <td>Check Item</td>
+        <td>Description</td>
+        <td>-set Supported or Not</td>
+      </tr>
+      <tr>
+        <td>CheckSwapMemory</td>
+        <td>
+          Checks the swap memory and total memory sizes. If the check result is 0,
+          this item passes the check. Otherwise, a warning is reported. If the
+          result is greater than the total memory, this item fails the check.
+        </td>
+        <td>Yes</td>
+      </tr>
+      <tr>
+        <td>CheckLogicalBlock</td>
+        <td>
+          Checks the logical block size of a disk. If the result is <b>512</b>, this
+          item passes the check. Otherwise, this item fails the check.
+        </td>
+        <td>Yes</td>
+      </tr>
+      <tr>
+        <td>CheckIOrequestqueue</td>
+        <td>
+          Checks the I/O value. If the value is <b>32768</b>, this item passes the
+          check. Otherwise, this item fails the check.
+        </td>
+        <td>Yes</td>
+      </tr>
+      <tr>
+        <td>CheckMaxAsyIOrequests</td>
+        <td>
+          Checks the maximum number of asynchronous requests. If the number of
+          asynchronous I/O requests is greater than 104857600 and greater than the
+          number of database instances on the current node x 1048576, this item
+          passes the check. Otherwise, this item fails the check.
+        </td>
+        <td>Yes</td>
+      </tr>
+      <tr>
+        <td>CheckIOConfigure</td>
+        <td>
+          Checks the I/O configuration. If the result is <b>deadline</b>, this item
+          passes the check. Otherwise, this item fails the check.
+        </td>
+        <td>Yes</td>
+      </tr>
+      <tr>
+        <td>CheckBlockdev</td>
+        <td>
+          Checks the size of the pre-read block. If the result is <b>16384</b>, this
+          item passes the check. Otherwise, this item fails the check.
+        </td>
+        <td>Yes</td>
+      </tr>
+      <tr>
+        <td>CheckDiskFormat</td>
+        <td>
+          Checks the XFS format information about a disk. If the result is
+          <b>rw,noatime,inode64,allocsize=16m</b>, this item passes the check.
+          Otherwise, a warning is reported.
+        </td>
+        <td>No</td>
+      </tr>
+      <tr>
+        <td>CheckInodeUsage</td>
+        <td>
+          Checks openGauss paths <b>GAUSSHOME/PGHOST/GPHOMEE/GAUSSLOG/tmp</b> and
+          instance directories.<br />
+          Checks the usage of the above directories. If the usage exceeds the
+          warning threshold (60% by default), a warning is reported. If the usage
+          exceeds the NG threshold (80% by default), this item fails the check. If
+          the usage is less than or equal to the NG threshold, this item passes the
+          check.
+        </td>
+        <td>No</td>
+      </tr>
+      <tr>
+        <td>CheckSpaceUsage</td>
+        <td>
+          Checks openGauss paths <b>GAUSSHOME/PGHOST/GPHOME/GAUSSLOG/tmp </b>and
+          instance directories.<br />
+          Checks the usage of the above directories. If the usage exceeds the
+          warning threshold (70% by default), a warning is reported. If the usage
+          exceeds the NG threshold (90% by default), this item fails the check. Also
+          checks the available space of the
+          <b>GAUSSHOME/PGHOST/GPHOME/GAUSSLOG/tmp/data</b> directory. If the space
+          is less than the threshold, this item fails the check. Otherwise, this
+          item passes the check.
+        </td>
+        <td>No</td>
+      </tr>
+      <tr>
+        <td>CheckDiskConfig</td>
+        <td>
+          Checks whether disk configurations are consistent. If the names, sizes,
+          and mount points of disks are the same, this item passes the check. If any
+          of them is inconsistent, a warning is reported.
+        </td>
+        <td>No</td>
+      </tr>
+      <tr>
+        <td>CheckXid</td>
+        <td>
+          Checks the value of <b>xid</b>. If the value is greater than 1 billion, a
+          warning is reported. If the value is greater than 1.8 billion, this item
+          fails the check.
+        </td>
+        <td>No</td>
+      </tr>
+      <tr>
+        <td>CheckSysTabSize</td>
+        <td>
+          Checks the system catalog capacity of each instance. If the available
+          capacity of each disk is greater than the total capacity of system
+          catalogs for all instances on the disk, this item passes the check.
+          Otherwise, this item fails the check.
+        </td>
+        <td>No</td>
+      </tr>
+    </table>
+
+- Cluster
+
+    <table>
+        <tr>
+            <td>Check Item</td>
+            <td>Description</td>
+            <td>-set Supported or Not</td>
+        </tr>
+        <tr>
+            <td>CheckClusterState</td>
+            <td>
+            Checks the fencedUDF status. If it is <b>down</b>, a warning is reported.
+            In this case, check the openGauss status. If it is <b>Normal</b>, this
+            item passes the check. Otherwise, this item fails the check.
+            </td>
+            <td>No</td>
+        </tr>
+        <tr>
+            <td>CheckDBParams</td>
+            <td>
+            For the primary database node, checks the size of the shared buffer and
+            the <b>Sem</b> parameter.<br />
+            For database nodes, checks the size of the shared buffer and the maximum
+            number of connections.<br />The shared buffer size should be greater than
+            128 KB, greater than <b>shmmax</b>, and greater than <b>shmall</b> x
+            <b>PAGESIZE</b>. <br />
+            If there is the primary database node, <b>Sem</b> must be greater than the
+            rounded up result of (Maximum number of database node connections +
+            150)/16.<br />If the above items are met, this item passes the check. If
+            any of them is not met, this item fails the check.
+            </td>
+            <td>Yes</td>
+        </tr>
+        <tr>
+            <td>CheckDebugSwitch</td>
+            <td>
+            Checks the value of the <b>log_min_messages</b> parameter in the
+            configuration file of each instance on each node. If the value is empty,
+            the default log level <b>warning</b> is used. In this case, if the actual
+            log level is not <b>warning</b>, a warning is reported.
+            </td>
+            <td>Yes</td>
+        </tr>
+        <tr>
+            <td>CheckUpVer</td>
+            <td>
+            Checks the version of the upgrade package on each node in openGauss. If
+            the versions are consistent, this item passes the check. Otherwise, this
+            item fails the check. You need to specify the path of the upgrade software
+            package.
+            </td>
+            <td>No</td>
+        </tr>
+        <tr>
+            <td>CheckDirPermissions</td>
+            <td>
+            Checks permissions for the node directories (instance Xlog path,
+            <b>GAUSSHOME</b>, <b>GPHOME</b>, <b>PGHOST</b>, and <b>GAUSSLOG</b>). If
+            the directories allow for the write permission and at most 750 permission,
+            this item passes the check. Otherwise, this item fails the check.
+            </td>
+            <td>Yes</td>
+        </tr>
+        <tr>
+            <td>CheckEnvProfile</td>
+            <td>
+            Checks the environment variables (<b>$GAUSSHOME</b>,
+            <b>$LD_LIBRARY_PATH</b>, and <b>$PATH</b>) of nodes and those of the CMS,
+            CMA, and database node processes. If there are node environment variables
+            that are correctly configured and process environment variables exist,
+            this item passes the check. Otherwise, this item fails the check.
+            </td>
+            <td>No</td>
+        </tr>
+        <tr>
+            <td>CheckGaussVer</td>
+            <td>
+            Checks whether the gaussdb version of each node is consistent. If the
+            versions are consistent, this item passes the check. Otherwise, this item
+            fails the check.
+            </td>
+            <td>No</td>
+        </tr>
+        <tr>
+            <td>CheckPortRange</td>
+            <td>
+            Checks the port range. If the value of <b>ip_local_port_range</b> is
+            within the threshold (26000 to 65535 by default) and an instance port is
+            out of the range, this item passes the check. Otherwise, this item fails
+            the check.
+            </td>
+            <td>No</td>
+        </tr>
+        <tr>
+            <td>CheckReadonlyMode</td>
+            <td>
+            Checks the read only mode. If the value of
+            <b>default_transaction_read_only</b> on the database nodes in openGauss is
+            <b>off</b>, this item passes the check. Otherwise, this item fails the
+            check.
+            </td>
+            <td>No</td>
+        </tr>
+        <tr>
+            <td>CheckCatchup</td>
+            <td>
+            Checks whether the CatchupMain function can be found in the gaussdb
+            process stack. If no, this item passes the check. Otherwise, this item
+            fails the check.
+            </td>
+            <td>No</td>
+        </tr>
+        <tr>
+            <td>CheckProcessStatus</td>
+            <td>
+            Checks the owner of the gaussdb processes. If their owner is only user
+            <b>omm</b>, this item passes the check. Otherwise, this item fails the
+            check.
+            </td>
+            <td>No</td>
+        </tr>
+        <tr>
+            <td>CheckSpecialFile</td>
+            <td>
+            Checks whether the files in the <b>tmp</b> directory (<b>PGHOST</b>), OM
+            directory (<b>GPHOME</b>), log directory (<b>GAUSSLOG</b>), data
+            directory, and program directory (<b>GAUSSHOME</b>) contain special
+            characters or whether there are files that do not belong to user
+            <b>omm</b>. If none of them exists, this item passes the check. Otherwise,
+            this item fails the check.
+            </td>
+            <td>No</td>
+        </tr>
+        <tr>
+            <td>CheckCollector</td>
+            <td>
+            Checks whether information is successfully collected in the output
+            directory. If yes, this item passes the check. Otherwise, this item fails
+            the check.
+            </td>
+            <td>No</td>
+        </tr>
+        <tr>
+            <td>CheckLargeFile</td>
+            <td>
+            Checks whether there is a file over 4 GB in the directory of each database
+            node. If there is such a file in any database node directory and its
+            subdirectories, this item fails the check. Otherwise, this item passes the
+            check.
+            </td>
+            <td>No</td>
+        </tr>
+        <tr>
+            <td>CheckProStartTime</td>
+            <td>
+            Checks whether the interval for starting key processes exceeds 5 minutes.
+            If no, this item passes the check. Otherwise, this item fails the check.
+            </td>
+            <td>No</td>
+        </tr>
+        <tr>
+            <td>CheckDilateSysTab</td>
+            <td>
+            Checks whether a system catalog is bloated. If no, this item passes the
+            check. Otherwise, this item fails the check.
+            </td>
+            <td>Yes</td>
+        </tr>
+        <tr>
+            <td>CheckMpprcFile</td>
+            <td>
+            Checks whether the environment variable isolation file is modified. If no,
+            this item passes the check. Otherwise, this item fails the check.
+            </td>
+            <td>No</td>
+        </tr>
+    </table>
+
+- Database
+
+    <table>
+        <tr>
+            <td>Check Item</td>
+            <td>Description</td>
+            <td>-set Supported or Not</td>
+        </tr>
+        <tr>
+          <td>CheckLockNum</td>
+          <td>
+            Checks the number of database locks. If a result is returned, this item
+            passes the check.
+          </td>
+          <td>No</td>
+        </tr>
+        <tr>
+          <td>CheckArchiveParameter</td>
+          <td>
+            Checks the database archive parameter. If the parameter is not enabled or
+            is enabled for database nodes, this item passes the check. If it is
+            enabled but not for database nodes, this item fails the check.
+          </td>
+          <td>Yes</td>
+        </tr>
+        <tr>
+          <td>CheckCurConnCount</td>
+          <td>
+            Checks the number of database connections. If the number is less than 90%
+            of the maximum connection quantity, this item passes the check. Otherwise,
+            this item fails the check.
+          </td>
+          <td>No</td>
+        </tr>
+        <tr>
+          <td>CheckCursorNum</td>
+          <td>
+            Checks the number of cursors in the database. If a result is returned,
+            this item passes the check. Otherwise, this item fails the check.
+          </td>
+          <td>No</td>
+        </tr>
+        <tr>
+          <td>CheckMaxDatanode</td>
+          <td>
+            Checks the maximum number of database nodes. If the number is less than
+            the number of nodes configured in the XML file multiplied by the number of
+            database nodes (90 x 5 by default), a warning is reported. Otherwise, this
+            item passes the check.
+          </td>
+          <td>Yes</td>
+        </tr>
+        <tr>
+          <td>CheckPgPreparedXacts</td>
+          <td>
+            Checks the <b>pgxc_prepared_xacts</b> parameter. If no 2PC transactions
+            are found, this item passes the check. Otherwise, this item fails the
+            check.
+          </td>
+          <td>Yes</td>
+        </tr>
+        <tr>
+          <td>CheckPgxcgroup</td>
+          <td>
+            Checks the number of redistributed records in the <b>pgxc_group</b> table.
+            If the result is 0, this item passes the check. Otherwise, this item fails
+            the check.
+          </td>
+          <td>No</td>
+        </tr>
+        <tr>
+          <td>CheckLockState</td>
+          <td>
+            Checks whether openGauss is locked. If no, this item passes the check.
+            Otherwise, this item fails the check.
+          </td>
+          <td>No</td>
+        </tr>
+        <tr>
+          <td>CheckIdleSession</td>
+          <td>
+            Checks the number of non-idle sessions. If the result is 0, this item
+            passes the check. Otherwise, this item fails the check.
+          </td>
+          <td>No</td>
+        </tr>
+        <tr>
+          <td>CheckDBConnection</td>
+          <td>
+            Checks whether the database can be connected. If yes, this item passes the
+            check. Otherwise, this item fails the check.
+          </td>
+          <td>No</td>
+        </tr>
+        <tr>
+          <td>CheckGUCValue</td>
+          <td>
+            Checks the result of [(<b>max_connections</b> +
+            <b>max_prepared_transactions</b>) x <b>max_locks_per_transaction</b>]. If
+            it is greater than or equal to 1 million, this item passes the check.
+            Otherwise, this item fails the check.
+          </td>
+          <td>Yes</td>
+        </tr>
+        <tr>
+          <td>CheckPMKData</td>
+          <td>
+            Checks whether the PMK schema of the database contains abnormal data. If
+            no, this item passes the check. Otherwise, this item fails the check.
+          </td>
+          <td>Yes</td>
+        </tr>
+        <tr>
+          <td>CheckSysTable</td>
+          <td>
+            Checks the system catalog. If the check can be performed, this item passes
+            the check.
+          </td>
+          <td>No</td>
+        </tr>
+        <tr>
+          <td>CheckSysTabSize</td>
+          <td>
+            Checks the system catalog capacity of each instance. If the available
+            capacity of each disk is greater than the total capacity of system
+            catalogs for all instances on the disk, this item passes the check.
+            Otherwise, this item fails the check.
+          </td>
+          <td>No</td>
+        </tr>
+        <tr>
+          <td>CheckTableSpace</td>
+          <td>
+            Checks tablespace paths. If no tablespace path and openGauss path are
+            nested and no tablespace paths are nested, this item passes the check.
+            Otherwise, this item fails the check.
+          </td>
+          <td>No</td>
+        </tr>
+        <tr>
+          <td>CheckTableSkew</td>
+          <td>
+            Checks the skew of table data. If a table has unbalanced data distribution
+            among openGauss database nodes, and the database node with the most data
+            has over 100,000 records more than the database node with the least data,
+            this item fails the check. Otherwise, this item passes the check.
+          </td>
+          <td>No</td>
+        </tr>
+        <tr>
+          <td>CheckDNSkew</td>
+          <td>
+            Checks the skew of table data at the database node level. If the database
+            node with the most amount of data has 5% more than the database node with
+            the smallest amount of data, this item fails the check. Otherwise, this
+            item passes the check.
+          </td>
+          <td>No</td>
+        </tr>
+        <tr>
+          <td>CheckUnAnalyzeTable</td>
+          <td>
+            Checks for a table that has not been analyzed. If there is such a table
+            and the table contains at least one record, this item fails the check.
+            Otherwise, this item passes the check.
+          </td>
+          <td>Yes</td>
+        </tr>
+        <tr>
+          <td>CheckCreateView</td>
+          <td>
+            If the query statement for creating a view contains sub-queries, and
+            parsing and rewriting sub-query results lead to duplicate aliases, the
+            check result is failed. Otherwise, the check result is passed.
+          </td>
+          <td>No</td>
+        </tr>
+        <tr>
+          <td>CheckHashIndex</td>
+          <td>
+            Checks whether there are hash indexes. If yes, this item fails the check.
+            Otherwise, this item passes the check.
+          </td>
+          <td>No</td>
+        </tr>
+        <tr>
+          <td>CheckNextvalInDefault</td>
+          <td>
+            Checks whether a DEFAULT expression contains <b>nextval</b> (sequence). If
+            yes, this item fails the check. Otherwise, this item passes the check.
+          </td>
+          <td>No</td>
+        </tr>
+        <tr>
+          <td>CheckNodeGroupName</td>
+          <td>
+            Checks whether the name of a Node Group contains non-SQL_ASCII characters.
+            If yes, this item fails the check. Otherwise, this item passes the check.
+          </td>
+          <td>Yes</td>
+        </tr>
+        <tr>
+          <td>CheckPgxcRedistb</td>
+          <td>
+            Checks whether any temporary table remains in the database after data
+            redistribution. If yes, this item fails the check. Otherwise, this item
+            passes the check.
+          </td>
+          <td>No</td>
+        </tr>
+        <tr>
+          <td>CheckReturnType</td>
+          <td>
+            Checks whether a user-defined function contains invalid return value
+            types. If yes, this item fails the check. Otherwise, this item passes the
+            check.
+          </td>
+          <td>No</td>
+        </tr>
+        <tr>
+          <td>CheckSysadminUser</td>
+          <td>
+            Checks whether there are database administrators in addition to the owner
+            of openGauss. If yes, this item fails the check. Otherwise, this item
+            passes the check.
+          </td>
+          <td>No</td>
+        </tr>
+        <tr>
+          <td>CheckTDDate</td>
+          <td>
+            Checks whether the ORC table in a Teradata database contains columns of
+            the date type. If yes, this item fails the check. Otherwise, this item
+            passes the check.
+          </td>
+          <td>No</td>
+        </tr>
+        <tr>
+          <td>CheckDropColumn</td>
+          <td>
+            Checks whether there are tables on which <b>DROP COLUMN</b> has been
+            performed. If yes, this item fails the check. Otherwise, this item passes
+            the check.
+          </td>
+          <td>No</td>
+        </tr>
+        <tr>
+          <td>CheckDiskFailure</td>
+          <td>
+            Checks for disk faults. If there is an error during full data query in
+            openGauss, this item fails the check. Otherwise, this item passes the
+            check.
+          </td>
+          <td>No</td>
+        </tr>
+    </table>
+
+- Network
+
+    <table>
+        <tr>
+            <td>Check Item</td>
+            <td>Description</td>
+            <td>-set Supported or Not</td>
+        </tr>
+        <tr>
+          <td>CheckPing</td>
+          <td>
+            Checks the connectivity of all nodes in openGauss. If all their IP
+            addresses can be pinged from each other, this item passes the check.
+            Otherwise, this item fails the check.
+          </td>
+          <td>No</td>
+        </tr>
+        <tr>
+          <td>CheckRXTX</td>
+          <td>
+            Checks the RX/TX value for <b>backIP</b> of a node. If it is <b>4096</b>,
+            this item passes the check. Otherwise, this item fails the check.
+          </td>
+          <td>Yes</td>
+        </tr>
+        <tr>
+          <td>CheckMTU</td>
+          <td>
+            Checks the MTU value of a NIC corresponding to <b>backIP</b> of a node
+            (ensure consistent PICs after bonding). If the result is not 8192 or 1500,
+            a warning is reported. In this case, if MTU values in openGauss are the
+            same, this item passes the check. Otherwise, this item fails the check.
+          </td>
+          <td>Yes</td>
+        </tr>
+        <tr>
+          <td>CheckNetWorkDrop</td>
+          <td>
+            Checks the packet loss rate of each IP address within 1 minute. If the
+            rate does not exceed 1%, this item passes the check. Otherwise, this item
+            fails the check.
+          </td>
+          <td>No</td>
+        </tr>
+        <tr>
+          <td>CheckBond</td>
+          <td>
+            Checks whether <b>BONDING_OPTS</b> or <b>BONDING_MODULE_OPTS</b> is
+            configured. If no, a warning is reported. In this case, checks whether the
+            bond mode of each node is the same. If yes, this item passes the check.
+            Otherwise, this item fails the check.
+          </td>
+          <td>Yes</td>
+        </tr>
+        <tr>
+          <td>CheckMultiQueue</td>
+          <td>
+            Checks <b>cat /proc/interrupts</b>. If multiqueue is enabled for NICs and
+            different CPUs are bound, this item passes the check. Otherwise, this item
+            fails the check.
+          </td>
+          <td>Yes</td>
+        </tr>
+        <tr>
+          <td>CheckUsedPort</td>
+          <td>
+            Checks the value of <b>net.ipv4.ip_local_port_range</b>. If the value is
+            greater than or equal to the default value of the OS (32768 to 61000),
+            this item passes the check. <br />Checks the number of random TCP ports.
+            If the number is less than 80% of the total number of random ports, this
+            item passes the check.
+          </td>
+          <td>No</td>
+        </tr>
+        <tr>
+          <td>CheckNICModel</td>
+          <td>
+            Checks whether NIC models or driver versions are consistent across nodes.
+            If yes, this item passes the check. Otherwise, a warning is reported.
+          </td>
+          <td>No</td>
+        </tr>
+        <tr>
+          <td>CheckRouting</td>
+          <td>
+            Checks the number of IP addresses on the service network segment for each
+            node. If the number exceeds 1, a warning is reported. Otherwise, this item
+            passes the check.
+          </td>
+          <td>No</td>
+        </tr>
+        <tr>
+          <td>CheckNetSpeed</td>
+          <td>
+            When the network is fully loaded, checks whether the average NIC receiving
+            bandwidth is greater than 600 MB. If yes, this item passes the check.<br />
+            When the network is fully loaded, checks the network ping value. If it is
+            shorter than 1s, this item passes the check.<br />
+            When the network is fully loaded, checks the NIC packet loss rate. If it
+            is less than 1%, this item passes the check.
+          </td>
+          <td>No</td>
+        </tr>
+    </table>
+
+- Others
+
+    <table>
+        <tr>
+            <td>Check Item</td>
+            <td>Description</td>
+            <td>-set Supported or Not</td>
+        </tr>
+        <tr>
+            <td>CheckDataDiskUsage</td>
+            <td>
+            Checks the usage of the disk database node directory. If the usage is
+            lower than 90%, this item passes the check. Otherwise, this item fails the
+            check.
+            </td>
+            <td>No</td>
+        </tr>
+    </table>
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** Constraints on the CheckNetSpeed check item are as follows:
+>
+> - Do not use **-L** to check CheckNetSpeed, because doing so cannot produce enough network load and the check result will be inaccurate.
+> - If the number of nodes is less than six, the network load produced by **speed_test** may not fully occupy the bandwidth, and the check result will be inaccurate.
+
+## Defining a Scenario
+
+1. Log in as the OS user **omm** to the primary node of the database.
+
+2. Create the scenario configuration file **scene_***XXX***.xml** in the **script/gspylib/inspection/config** directory.
+
+3. Write check items to the scenario configuration file in the following format:
+
+   ```xml
+   <?xml version="1.0" encoding="utf-8" ?>
+   <scene name="XXX" desc="check cluster parameters before XXX.">
+   <configuration/>
+   <allowitems>
+   <item name="CheckXXX"/>
+   <item name="CheckXXX"/>
+   </allowitems>
+   </scene>
+   ```
+
+   **item name** indicates the check item name.
+
+   Note: You need to ensure that the user-defined XML file is correct.
+
+4. Run the following command in the **home/package/script/gspylib/inspection/config** directory to deploy the file on each node where the check is to be performed:
+
+   ```bash
+   scp scene_upgrade.xml SIA1000068994: home/package/script/gspylib/inspection/config/
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** **home/package/script/gspylib/inspection/config** is the absolute path of the new scenario configuration file.
+
+5. Switch to user **omm** and run the following command on an old node to view the check result:
+
+   ```bash
+   gs_check  -e XXX
+   ```
+
+## Defining a Check Item
+
+1. Add a check item. Modify the **script/gspylib/inspection/config/items.xml** file in the following format:
+
+   ```xml
+   <checkitem id="10010" name="CheckCPU">
+   <title>
+   <zh>Check the CPU usage.</zh>
+   <en>Check CPU Idle and I/O wait</en>
+   </title>
+   <threshold>
+   StandardCPUIdle=30;
+   StandardWIO=30
+   </threshold>
+   <suggestion>
+   <zh>If the available space is insufficient and the CPU is heavily loaded, scale out the nodes. If iowait is too high, expand the disk capacity, which is the current performance bottleneck.</zh>.
+   </suggestion>
+   <standard>
+   <zh>Check the CPU usage of the host. If the value of idle is greater than 30% and the value of iowait is less than 30%, this item passes the check. Otherwise, this item fails the check.</zh>
+   </standard>
+   <category>os</category>
+   <permission>user</permission>
+   <scope>all</scope>
+   <analysis>default</analysis>
+   </checkitems>
+   ```
+
+   - **id**: specifies the check item ID.
+
+   - **name**: specifies the name of the check script.
+
+   - **title**: specifies the check item description. It allows multiple languages.
+
+     : checks content of Chinese version.
+
+     : checks content of English version.
+
+   - **standard**: specifies the check standards. It allows multiple languages.
+
+   - **suggestion**: provides advice on how to fix check item problems. It allows multiple languages.
+
+   - **threshold**: specifies the check item threshold. Multiple values are separated using semicolons (;), for example, **Key1=Value1;Key2=Value2**.
+
+   - **category**: specifies the check item type. It is optional. Its value can be **os**, **device**, **network**, **cluster**, **database**, or **other**.
+
+   - **permission**: specifies the permission required for checking an item. It is optional. Its value can be **root** or **user** (default).
+
+   - **scope**: specifies the node scope where an item is checked. It is optional. **cn-** indicates that only the primary database node resides is checked. **local-** indicates that only the current node is checked. **all-** is the default value, indicating that all nodes in MogDB are checked.
+
+   - **analysis**: specifies how the check result is analyzed. **default-** is the default value, indicating that the result on every node is checked, and that an item passes the check only if it passes the check on all the nodes. **consistent-** indicates that each node returns a result, and that an item passes the check if all the results are consistent. **custom-** indicates other ways.
+
+   Note: You need to ensure that the user-defined XML file is correct.
+
+2. Create a check script named **Check** *XXXX***.py** in the **script/gspylib/inspection/items** directory. The directory should contain multiple folders, each storing a type of scripts. The format is as follows:
+
+   ```
+   class CheckCPU(BaseItem):
+   def __init__(self):
+   super(CheckCPU, self).__init__(self.__class__.__name__)
+   self.idle = None
+   self.wio = None
+   self.standard = None
+
+   def preCheck(self):
+   # check the threshold was set correctly
+   if (not self.threshold.has_key('StandardCPUIdle')
+   or not self.threshold.has_key('StandardWIO')):
+   raise Exception("threshold can not be empty")
+   self.idle = self.threshold['StandardCPUIdle']
+   self.wio = self.threshold['StandardWIO']
+
+   # format the standard by threshold
+   self.standard = self.standard.format(idle=self.idle, iowait=self.wio)
+
+   def doCheck(self):
+   cmd = "sar 1 5 2>&1"
+   output = SharedFuncs.runShellCmd(cmd)
+   self.result.raw = output
+   # check the result with threshold
+   d = next(n.split() for n in output.splitlines() if "Average" in n)
+   iowait = d[-3]
+   idle = d[-1]
+   rst = ResultStatus.OK
+   vals = []
+   if (iowait > self.wio):
+   rst = ResultStatus.NG
+   vals.append("The %s actual value %s is greater than expected value %s" % ("IOWait", iowait, self.wio))
+   if (idle < self.idle):
+   rst = ResultStatus.NG
+   vals.append("The %s actual value %s is less than expected value %s" % ("Idle", idle, self.idle))
+   self.result.rst = rst
+   if (vals):
+   self.result.val = "\n".join(vals)
+   ```
+
+   A script is developed based on the BaseItem class, which defines the common check process, result analysis method, and default output format. Extended parameters:
+
+   - **doCheck**: contains specific ways to check an item. The check result is in the following format:
+
+     **result.rst**: (optional) specifies the check result. Its value can be:
+
+     - **OK**: indicates that the item passes the check.
+     - **NA**: indicates that the check does not cover the node.
+     - **NG**: indicates that the item failed the check.
+     - **WARNING**: indicates that the check is complete and that a warning is reported.
+     - **ERROR**: indicates that the check is interrupted due to an internal error.
+
+   - **preCheck**: checks prerequisites. Its value can be **cnPreCheck**, which checks whether a primary database node instance is deployed on the current execution node; or **localPreCheck**, which checks whether the current execution node is specified for the check. You can set it using **scope** in the check item configuration file. This method can be reloaded to perform customized pre-checks.
+
+   - **postAnalysis** specifies how the check result is analyzed. Its value can be **default** or **consistent**. You can set it using **analysis** in the check item configuration file. This method can be reloaded to perform customized result analysis.
+
+   Note: The name of a user-defined check item cannot be the same as the name of an existing check item. In addition, you need to ensure that the user-defined check item script is standard.
+
+3. Deploy the script on all execution nodes.
+
+4. Log in to the nodes added in a scale-out as user **root** or to old nodes as user **omm**. Run the following commands as required and view the result:
+
+   To locally perform a check, run the following command:
+
+   ```bash
+   gs_check -i CheckXXX  -L
+   ```
+
+   To remotely perform a check, run the following command:
+
+   ```bash
+   gs_check -i CheckXXX
+   ```
+
+## OS Parameters
+
+**Table 2** OS parameters
+
+| Parameter                     | Description                                                  | Recommended Value             |
+| :---------------------------- | :----------------------------------------------------------- | :---------------------------- |
+| net.ipv4.tcp_max_tw_buckets   | Specifies the maximum number of TCP/IP connections concurrently remaining in the `TIME_WAIT` state. If the number of TCP/IP connections concurrently remaining in the `TIME_WAIT`state exceeds the value of this parameter, the TCP/IP connections in the `TIME_WAIT` state will be released immediately, and alarm information will be printed. | 10000                         |
+| net.ipv4.tcp_tw_reuse         | Reuses sockets whose status is `TIME-WAIT` for new TCP connections.<br />- **0**: This function is disabled.<br />- **1**: This function is enabled. | 1                             |
+| net.ipv4.tcp_tw_recycle       | Rapidly reclaims sockets whose status is `TIME-WAIT` in TCP connections.<br />- **0**: This function is disabled.<br />- **1**: This function is enabled. | 1                             |
+| net.ipv4.tcp_keepalive_time   | Specifies how often Keepalived messages are sent through TCP connections when Keepalived is enabled. | 30                            |
+| net.ipv4.tcp_keepalive_probes | Specifies the number of Keepalived detection packets sent through a TCP connection before the connection is regarded invalid. The product of the parameter value multiplied by the value of the **tcp_keepalive_intvl** parameter determines the response timeout duration after a Keepalived message is sent through a connection. | 9                             |
+| net.ipv4.tcp_keepalive_intvl  | Specifies how often a detection packet is re-sent when the previous packets are not acknowledged. | 30                            |
+| net.ipv4.tcp_retries1         | Specifies the maximum TCP reattempts during connection establishment. | 5                             |
+| net.ipv4.tcp_syn_retries      | Specifies the maximum SYN packet reattempts in the TCP.      | 5                             |
+| net.ipv4.tcp_synack_retries   | Specifies the maximum SYN response packet reattempts in the TCP. | 5                             |
+| net.ipv4.tcp_retries2         | Specifies the number of times that the kernel re-sends data to a connected remote host. A smaller value leads to earlier detection of an invalid connection to the remote host, and the server can quickly release this connection.<br />If "connection reset by peer" is displayed, increase the value of this parameter to avoid the problem. | 12                            |
+| vm.overcommit_memory          | Specifies the kernel check method during memory allocation.<br />- **0**: The system accurately calculates the current available memory.<br />- **1**: The system returns a success message without a kernel check.<br />- **2**: The system returns a failure message if the memory size you have applied for exceeds the result of the following formula: Total memory size x Value of `vm.overcommit_ratio` / 100 + Total SWAP size.<br />The default value for a kernel is **2**, which is too conservative. The recommended value is **0**. If system loads are high, set this parameter to**1**. | 0                             |
+| net.ipv4.tcp_rmem             | Specifies the free memory in the TCP receiver buffer. Three memory size ranges in the unit of page are provided: **min**, **default**, and **max**. | 8192 250000 16777216          |
+| net.ipv4.tcp_wmem             | Specifies the free memory in the TCP sender buffer. Three memory size ranges in the unit of page are provided: **min**, **default**, and **max**. | 8192 250000 16777216          |
+| net.core.wmem_max             | Specifies the maximum size of the socket sender buffer.      | 21299200                      |
+| net.core.rmem_max             | Specifies the maximum size of the socket receiver buffer.    | 21299200                      |
+| net.core.wmem_default         | Specifies the default size of the socket sender buffer.      | 21299200                      |
+| net.core.rmem_default         | Specifies the default size of the socket receiver buffer.    | 21299200                      |
+| net.ipv4.ip_local_port_range  | Specifies the range of temporary ports that can be used by a physical server. | 26000-65535                   |
+| kernel.sem                    | Specifies the kernel semaphore.                              | 250 6400000 1000 25600        |
+| vm.min_free_kbytes            | Specifies the minimum free physical memory reserved for unexpected page breaks. | 5% of the total system memory |
+| net.core.somaxconn            | Specifies the maximum length of the listening queue of each port. This is a global parameter. | 65535                         |
+| net.ipv4.tcp_syncookies       | Specifies whether to enable SYN cookies to guard the OS against SYN attacks when the SYN waiting queue overflows.<br />- **0**: The SYN cookies are disabled.<br />- **1**: The SYN cookies are enabled. | 1                             |
+| net.core.netdev_max_backlog   | Specifies the maximum number of data packets that can be sent to the queue when the rate at which the network device receives data packets is higher than that at which the kernel processes the data packets. | 65535                         |
+| net.ipv4.tcp_max_syn_backlog  | Specifies the maximum number of unacknowledged connection requests to be recorded. | 65535                         |
+| net.ipv4.tcp_fin_timeout      | Specifies the default timeout.                               | 60                            |
+| kernel.shmall                 | Specifies the total shared free memory of the kernel.        | 1152921504606846720           |
+| kernel.shmmax                 | Specifies the maximum value of a shared memory segment.      | 18446744073709551615          |
+| net.ipv4.tcp_sack             | Specifies whether selective acknowledgment is enabled. The selective acknowledgment on out-of-order packets can increase system performance. Restricting users to sending only lost packets (for wide area networks) should be enabled, but this will increase CPU usage.<br />- **0**: This function is disabled.<br />- **1**: This function is enabled. | 1                             |
+| net.ipv4.tcp_timestamps       | Specifies whether the TCP timestamp (12 bytes are added in the TCP packet header) enables a more accurate RTT calculation than the retransmission timeout (for details, see RFC 1323) for better performance.<br />- **0**: This function is disabled.<br />- **1**: This function is enabled. | 1                             |
+| vm.extfrag_threshold          | When system memory is insufficient, Linux will score the current system memory fragments. If the score is higher than the value of `vm.extfrag_threshold`,`kswapd` triggers memory compaction. When the value of this parameter is close to **1000**, the system tends to swap out old pages when processing memory fragments to meet the application requirements. When the value of this parameter is close to**0**, the system tends to do memory compaction when processing memory fragments. | 500                           |
+| vm.overcommit_ratio           | When the system uses the algorithms where memory usage never exceeds the thresholds, the total memory address space of the system cannot exceed the value of **swap+RAM** multiplied by the percentage specified by this parameter. When the value of `vm.overcommit_memory` is set to **2**, this parameter takes effect. | 90                            |
+| MTU                           | Specifies the maximum transmission unit (MTU) for a node NIC. The default value in the OS is **1500**. You can set it to **8192** to improve the performance of sending and receiving data using SCTP. | 8192                          |
+
+## File System Parameters
+
+- soft nofile
+
+  Indicates the soft limit. The number of file handles used by a user can exceed this parameter value. However, an alarm will be reported.
+
+  Recommended value: **1000000**
+
+- hard nofile
+
+  Indicates the hard limit. The number of file handles used by a user cannot exceed this parameter value.
+
+  Recommended value: **1000000**
+
+- stack size
+
+  Specifies the thread stack size.
+
+  Recommended value: **3072**
+
+## Examples
+
+Check result of a single item:
+
+```bash
+perfadm@lfgp000700749:/opt/huawei/perfadm/tool/script> gs_check -i CheckCPU
+Parsing the check items config file successfully
+Distribute the context file to remote hosts successfully
+Start to health check for the cluster. Total Items:1 Nodes:3
+
+Checking...               [=========================] 1/1
+Start to analysis the check result
+CheckCPU....................................OK
+The item run on 3 nodes.  success: 3
+
+Success. All check items run completed. Total:1  Success:1  Failed:0
+For more information please refer to /opt/mogdb/tools/script/gspylib/inspection/output/CheckReport_201902193704661604.tar.gz
+```
+
+Local execution result:
+
+```bash
+perfadm@lfgp000700749:/opt/huawei/perfadm/tool/script> gs_check -i CheckCPU -L
+
+2017-12-29 17:09:29 [NAM] CheckCPU
+2017-12-29 17:09:29 [STD] Check the CPU usage of the host. If the value of idle is greater than 30% and the value of iowait is less than 30%, this item passes the check. Otherwise, this item fails the check.
+2017-12-29 17:09:29 [RST] OK
+
+2017-12-29 17:09:29 [RAW]
+Linux 4.4.21-69-default (lfgp000700749)  12/29/17  _x86_64_
+
+17:09:24        CPU     %user     %nice   %system   %iowait    %steal     %idle
+17:09:25        all      0.25      0.00      0.25      0.00      0.00     99.50
+17:09:26        all      0.25      0.00      0.13      0.00      0.00     99.62
+17:09:27        all      0.25      0.00      0.25      0.13      0.00     99.37
+17:09:28        all      0.38      0.00      0.25      0.00      0.13     99.25
+17:09:29        all      1.00      0.00      0.88      0.00      0.00     98.12
+Average:        all      0.43      0.00      0.35      0.03      0.03     99.17
+```
+
+Check result of a scenario:
+
+```bash
+[perfadm@SIA1000131072 Check]$ gs_check -e inspect
+Skip CheckHdfsForeignTabEncoding because it only applies to V1R5 upgrade V1R6 with cluster.
+Parsing the check items config file successfully
+The below items require root privileges to execute:[CheckBlockdev CheckIOConfigure CheckMTU CheckRXTX CheckMultiQueue CheckFirewall CheckSshdService CheckSshdConfig CheckCrondService CheckMaxProcMemory CheckBootItems CheckFilehandle CheckNICModel CheckDropCache]
+Please enter root privileges user[root]:
+Please enter password for user[root]:
+Check root password connection successfully
+Distribute the context file to remote hosts successfully
+Start to health check for the cluster. Total Items:57 Nodes:3
+Checking...               [=========================] 57/57
+Start to analysis the check result
+CheckClusterState...........................OK
+The item run on 3 nodes.  success: 3
+CheckDBParams...............................OK
+.........................................................................
+CheckMpprcFile..............................OK
+The item run on 3 nodes.  success: 3
+
+Analysis the check result successfully
+Failed. All check items run completed. Total:57   Success:49   Warning:5   NG:3   Error:0
+For more information please refer to /opt/huawei/wisequery/script/gspylib/inspection/output/CheckReport_inspect_201902207129254785.tar.gz
+```
+
+## Helpful Links
+
+[gs_checkos](2-gs_checkos), [gs_checkperf](3-gs_checkperf)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/10-gs_ssh.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/10-gs_ssh.md
new file mode 100644
index 0000000000000000000000000000000000000000..fbcf2e0d79e47fed211dd27344ce946c9dc483c0
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/10-gs_ssh.md
@@ -0,0 +1,76 @@
+---
+title: gs_ssh
+summary: gs_ssh
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_ssh
+
+## Background
+
+**gs_ssh**, provided by MogDB, helps users run the same command on multiple nodes in MogDB.
+
+## Precautions
+
+- **gs_ssh** can only run the command which the OS user **omm** has permission
+- The command to be run will not affect the current session where **gs_ssh** is executed. For example, the command such as **cd** or **source** will not affect the current session as it will only be run in the environment within the process of **gs_ssh** itself
+
+## Prerequisites
+
+- The trust relationship among the hosts is normal.
+- MogDB has been correctly installed and deployed.
+- The command to be run can be found by the **which** command, and the current user has the required execution permission.
+- Log in to the OS as the OS user **omm** to run the **gs_ssh** command.
+
+## Syntax
+
+- Run commands synchronously.
+
+  ```
+  gs_ssh -c cmd
+  ```
+
+- Display help information.
+
+  ```
+  gs_ssh -? | --help
+  ```
+
+- Display version information.
+
+  ```
+  gs_ssh -V | --version
+  ```
+
+## Parameter Description
+
+- -c
+
+  Specifies the command name of Linux shell on the hosts of MogDB.
+
+- -?, -help
+
+  Displays help information.
+
+- -V, -version
+
+  Displays version information.
+
+## Example
+
+Run the same command on each host of MogDB. Take the **hostname** command as an example.
+
+```
+gs_ssh -c "hostname"
+Successfully execute command on all nodes.
+Output:
+[SUCCESS] plat1:
+plat1
+[SUCCESS] plat2:
+plat2
+[SUCCESS] plat3:
+plat3
+[SUCCESS] plat4:
+plat4
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/2-gs_checkos.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/2-gs_checkos.md
new file mode 100644
index 0000000000000000000000000000000000000000..762b51e5ba786c264277648f65e0f15ab0f3881c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/2-gs_checkos.md
@@ -0,0 +1,226 @@
+---
+title: gs_checkos
+summary: gs_checkos
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_checkos
+
+## Context
+
+**gs_checkos** helps you check the OS version information, control parameters, and disk configurations, and configure control parameters, I/O parameters, network parameters, and THP services.
+
+## Prerequisites
+
+- The hardware and network are working properly.
+- The trust relationship of user **root** among the hosts is normal.
+- Only user **root** is authorized to run the **gs_checkos** command.
+
+## Syntax
+
+- Check OS information.
+
+  ```
+  gs_checkos -i ITEM [-f HOSTFILE] [-h HOSTNAME] [-X XMLFILE] [--detail] [-o OUTPUT] [-l LOGFILE]
+  ```
+
+- Display help information.
+
+  ```
+  gs_checkos -? | --help
+  ```
+
+- Display version information.
+
+  ```
+  gs_checkos -V | --version
+  ```
+
+## Parameter Description
+
+- -i
+
+  Specifies the number of a check item. The format is -i A, -i B1, -i A1 -i A2, or - i A1,A2.
+
+  Value range: A1…A14 and B1…B8
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  > Items from A1 to A14 indicate that OS parameters need to be checked but not to be set.
+  > Items from B1 to B8 indicate that system parameters need to be set to expected values.
+  > Items A and items B cannot be simultaneously set.
+
+  For details, see [Table 1](#oscheck).
+
+- -f
+
+  Specifies the file of a host name list.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The **-f** and **-h** parameters cannot be used together.
+
+  Value range: a host name list
+
+- -h
+
+  Specifies the name of a host to be checked. You can specify multiple hosts and separate the hosts with commas (,).
+
+  Value range: a host name of MogDB. If no host is specified, the current host is checked.
+
+- -X
+
+  Specifies the XML configuration file of MogDB.
+
+- -detail
+
+  Displays detailed check results.
+
+- -o
+
+  Specifies the file for saving OS check reports.
+
+  If this parameter is not specified, OS check results are displayed on the screen.
+
+- -l
+
+  Specifies a log file and its save path.
+
+  Default value: **/tmp/gs_checkos/gs_checkos-YYYY-MM-DD_hhmmss.log**
+
+- -?, -help
+
+  Displays help information.
+
+- -V, -version
+
+  Displays version information.
+
+**Table 1** OS check items <a id="oscheck"> </a>
+
+| Number | Check Item                           | Description                                                  |
+| :----- | :----------------------------------- | :----------------------------------------------------------- |
+| A1     | OS version status                    | Check the OS version. Ensure that the host platform supports openEuler or CentOS. In addition, you need to ensure that the all host platforms of MogDB belong to the same hybrid range. |
+| A2     | Kernel version status                | Check the kernel version.                                    |
+| A3     | Unicode status                       | Check the character set. Ensure that the character sets of MogDB hosts are consistent. |
+| A4     | Time zone status                     | Checks the time zone setting. Ensure that the time zones of MogDB hosts are consistent. |
+| A5     | Swap memory status                   | Check the swap partition. Ensure that the swap partition size of each host is less than or equals to the total memory size of the host. |
+| A6     | System control parameters status     | Check the kernel parameter. Ensure that the parameter value of the current kernel is consistent with the default value.<br />For details, see **OS Parameters**. |
+| A7     | File system configuration status     | Check the system file handle. Ensure that the parameter value of the system file handle is greater than or equal to **1000000**.<br />Check the thread stack size: Ensure that the thread size is greater than or equal to 3072 KB.<br />Check the maximum available virtual memory of processes. Ensure that the maximum available virtual memory of system processes is **unlimited**. |
+| A8     | Disk configuration status            | Check the hard disk mounting parameter. Ensure that the disk format is XFS and its mounting mode is "rw,noatime,inode64,allocsize=16m". |
+| A9     | Pre-read block size status           | Check the pre-read parameter. Ensure that the expected value of the pre-read parameter is **16384**. |
+| A10    | IO scheduler status                  | Check the I/O scheduling policy. Ensure that the I/O scheduling policy is **deadline**. |
+| A11    | Network card configuration status    | Check the NIC smaller than 10GE.<br />- Ensure that **mtu** of the NIC is **1500**.<br />Check the NIC larger than 10GE.<br />- When the NIC is in unbinding mode and is a 10GE card, ensure that the value of **mtu** is **1500** and the value of **rx/tx** is greater than or equal to **4096**.<br />- When the NIC is in binding mode, ensure that the type of each binding NIC is 10GE, the value of **mtu** is **1500**, and the value of **rx/tx** is greater than or equal to **4096**.<br />- The NIC of MogDB's peripheral devices (such as switches) should be set to the same as that of the MogDB hosts. |
+| A12    | Time consistency status              | Check the time consistency status. Ensure that the NTP service is started and the system time deviation of each MogDB host does not exceed 60s. |
+| A13    | Firewall service status              | Check the firewall status. Ensure that the firewall is disabled. |
+| A14    | THP service status                   | Check the THP service status. Ensure that the THP service is disabled. |
+| B1     | Set system control parameters        | Sets the kernel parameter. When the actual value does not meet check requirements, reset the parameter whose result is **Abnormal**. Do not set the **Warning** parameter here. You can set the value of **Warning** as needed. |
+| B2     | Set file system configuration value  | Set the parameter of system file handles. Set the number of system file handles if it is less than **1000000**.<br />Set the thread stack size. Set the thread stack size if it is less than 3072 KB.<br />Set the maximum available virtual memory of processes: If the maximum available virtual memory of system processes is not **unlimited**, change it to **unlimited**. |
+| B3     | Set pre-read block size value        | Set the hard disk pre-read parameter: When the actual value is less than **16384**, reset the parameter. |
+| B4     | Set IO scheduler value               | Set the I/O configuration item. If the actual value of the system is not **deadline**, reset the parameter. |
+| B5     | Set network card configuration value | Set the 10GE NIC parameters. Set the **rx** and **tx** parameters that do not meet 10GE NIC requirements. Do not set the **mtu** parameter. |
+| B6     | Set THP service                      | Set the THP service. If the THP service is enabled, disable it. |
+| B7     | Set RemoveIPC value                  | Check EulerOS attributes. Set the value of RemoveIPC in files **/usr/lib/systemd/system/systemd-logind.service** and **/etc/systemd/logind.conf** to **no**. |
+| B8     | Set Session Process                  | Set a remote device to inherit default system resources. Modify the **/etc/pam.d/sshd** service file and add the **session required pam_limits.so** configuration item to control resources used by users. |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - Item A6 needs to be checked based on the **[/etc/sysctl.conf]** and **[SUGGEST:/etc/sysctl.conf]** domains in the **check_list.conf** configuration file.
+>   If the parameter value in **[/etc/sysctl.conf]** differs from the actual value, an **Abnormal** message is displayed during the check of item A6. You can set the parameter in item B1.
+>   If the parameter value in **[SUGGEST:/etc/sysctl.conf]** differs from the actual value, a Warning message is displayed during the check of item A6. You can manually set the parameter in item B1 as needed.
+> - Item A7 checks items specified by the **open file** parameter in the **[/etc/security/ limits.conf]** domain in the **check_list.conf** configuration file. You can set the parameter in item B2.
+> - The **mtu**, **rx**, and **tx** parameters of item A11 need to be checked based on the **[/sbin/ifconfig]** domain in the **check_list.conf** configuration file. You can set the **rx** and **tx** parameters using item B5 and set the **mtu** parameter manually.
+> - Use configured **gs_checkos** kernel parameter value and file handles parameter value to restart the new session.
+
+## OS Parameters
+
+**Table 2** OS parameters
+
+| Parameter                     | Description               | Recommended Value             |
+| :---------------------------- | :-------------------------| :---------------------------- |
+| net.ipv4.tcp_max_tw_buckets   | Specifies the maximum number of TCP/IP connections concurrently remaining in the 、  `TIME_WAIT` state. If the number of TCP/IP connections concurrently remaining in the `TIME_WAIT` state exceeds the value of this parameter, the TCP/IP connections in the **TIME\_WAIT** state will be released immediately, and alarm information will be printed. | 10000                         |
+| net.ipv4.tcp_tw_reuse         | Reuses sockets whose status is **TIME-WAIT** for new TCP connections.<br />- **0**: This function is disabled.<br />- **1**: This function is enabled. | 1                             |
+| net.ipv4.tcp_tw_recycle       | Rapidly reclaims sockets whose status is **TIME-WAIT** in TCP connections.<br />- **0**: This function is disabled.<br />- **1**: This function is enabled. | 1                             |
+| net.ipv4.tcp_keepalive_time   | Specifies how often Keepalived messages are sent through TCP connections when Keepalived is enabled. | 30                            |
+| net.ipv4.tcp_keepalive_probes | Specifies the number of Keepalived detection packets sent through a TCP connection before the connection is regarded invalid. The product of the parameter value multiplied by the value of the **tcp_keepalive_intvl** parameter determines the response timeout duration after a Keepalived message is sent through a connection. | 9                             |
+| net.ipv4.tcp_keepalive_intvl  | Specifies how often a detection packet is re-sent when the previous packets are not acknowledged. | 30                            |
+| net.ipv4.tcp_retries1         | Specifies the maximum TCP reattempts during the connection establishment process. | 5                             |
+| net.ipv4.tcp_syn_retries      | Specifies the maximum SYN packet reattempts in the TCP.      | 5                             |
+| net.ipv4.tcp_synack_retries   | Specifies the maximum SYN response packet reattempts in the TCP. | 5                             |
+| net.ipv4.tcp_retries2         | Specifies the number of times that the kernel re-sends data to a connected remote host. A smaller value leads to earlier detection of an invalid connection to the remote host, and the server can quickly release this connection.<br />If "connection reset by peer" is displayed, increase the value of this parameter to avoid the problem. | 12                            |
+| vm.overcommit_memory          | Specifies the kernel check method during memory allocation.<br />- **0**: The system accurately calculates the current available memory.<br />- **1**: The system returns a success message without a kernel check.<br />- **2**: The system returns a failure message if the memory size you have applied for exceeds the result of the following formula: Total memory size x Value of `vm.overcommit_ratio`/100 + Total SWAP size.<br />The default value for is **2**, which is too conservative. The recommended value is **0**. If memory usage is high, set this parameter to **1**. | 0                             |
+| net.ipv4.tcp_rmem             | Specifies the free memory in the TCP receiver buffer. Three memory size ranges in the unit of page are provided: **min**, **default**, and **max**. | 8192 250000 16777216          |
+| net.ipv4.tcp_wmem             | Specifies the free memory in the TCP sender buffer. Three memory size ranges in the unit of page are provided: **min**, **default**, and **max**. | 8192 250000 16777216          |
+| net.core.wmem_max             | Specifies the maximum size of the socket sender buffer.      | 21299200                      |
+| net.core.rmem_max             | Specifies the maximum size of the socket receiver buffer.    | 21299200                      |
+| net.core.wmem_default         | Specifies the default size of the socket sender buffer.      | 21299200                      |
+| net.core.rmem_default         | Specifies the default size of the socket receiver buffer.    | 21299200                      |
+| net.ipv4.ip_local_port_range  | Specifies the range of temporary ports that can be used by a physical server. | 26000-65535                   |
+| kernel.sem                    | Specifies the kernel semaphore.                              | 250 6400000 1000 25600        |
+| vm.min_free_kbytes            | Specifies the minimum free physical memory reserved for unexpected page breaks. | 5% of the total system memory |
+| net.core.somaxconn            | Specifies the maximum length of the listening queue of each port. This is a global parameter. | 65535                         |
+| net.ipv4.tcp_syncookies       | Specifies whether to enable SYN cookies to guard the OS against SYN attacks when the SYN waiting queue overflows.<br />- **0**: The SYN cookies are disabled.<br />- **1**: The SYN cookies are enabled. | 1                             |
+| net.core.netdev_max_backlog   | Specifies the maximum number of data packets that can be sent to the queue when the rate at which the network device receives data packets is higher than that at which the kernel processes the data packets. | 65535                         |
+| net.ipv4.tcp_max_syn_backlog  | Specifies the maximum number of unacknowledged connection requests to be recorded. | 65535                         |
+| net.ipv4.tcp_fin_timeout      | Specifies the default timeout duration.                      | 60                            |
+| kernel.shmall                 | Specifies the total shared free memory of the kernel.        | 1152921504606846720           |
+| kernel.shmmax                 | Specifies the maximum value of a shared memory segment.      | 18446744073709551615          |
+| net.ipv4.tcp_sack             | Specifies whether selective acknowledgment is enabled. The selective acknowledgment on out-of-order packets can increase system performance. Restricting users to sending only lost packets (for wide area networks) should be enabled, but this will increase CPU usage.<br />- **0**: This function is disabled.<br />- **1**: This function is enabled. | 1                             |
+| net.ipv4.tcp_timestamps       | Specifies whether the TCP timestamp (12 bytes are added in the TCP packet header) enables a more accurate RTT calculation than the retransmission timeout (for details, see RFC 1323) for better performance.<br />- **0**: This function is disabled.<br />- **1**: This function is enabled. | 1                             |
+| vm.extfrag_threshold          | When system memory is insufficient, Linux will score the current system memory fragments. If the score is higher than the value of `vm.extfrag_threshold`, **kswapd** triggers memory compaction. When the value of this parameter is close to **1000**, the system tends to swap out old pages when processing memory fragments to meet the application requirements. When the value of this parameter is close to **0**, the system tends to do memory compaction when processing memory fragments. | 500                           |
+| vm.overcommit_ratio           | When the system uses the algorithms where memory usage never exceeds the thresholds, the total memory address space of the system cannot exceed the value of **swap+RAM** multiplied by the percentage specified by this parameter. When the value of `vm.overcommit_memory`~ is set to **2**, this parameter takes effect. | 90                            |
+| MTU                           | Specifies the maximum transmission unit (MTU) for a node NIC. The default value is **1500** in the OS. You can set it to **8192** to improve the performance of sending and receiving data using SCTP. | 8192                          |
+
+## File System Parameters
+
+- soft nofile
+
+  Indicates the soft restriction. The number of file handles used by a user can exceed this setting value, but an alarm message will be sent if the value is exceeded.
+
+  Recommended value: **1000000**
+
+- hard nofile
+
+  Indicates the hard restriction. The number of file handles used by a user cannot exceed this setting value.
+
+  Recommended value: **1000000**
+
+- stack size
+
+  Indicates the thread stack size.
+
+  Recommended value: **3072**
+
+## Examples
+
+Run the following commands to check the OS parameters:
+
+```bash
+gs_checkos -i A -h plat1 -X /opt/software/mogdb/clusterconfig.xml --detail -o /var/log/checkos
+Performing operation system check/set. Output the result to the file /var/log/checkos.
+Operation system check/set is completed.
+Total numbers:14. Abnormal numbers:0. Warning number:1.
+```
+
+Query check results.
+
+```bash
+vim /var/log/checkos
+Checking items:
+    A1. [ OS version status ]                                   : Normal
+    A2. [ MogDB version status ]                               : Normal
+    A3. [ Unicode status ]                                      : Normal
+    A4. [ Time zone status ]                                    : Normal
+    A5. [ Swap memory status ]                                  : Normal
+    A6. [ System control parameters status ]                    : Normal
+    A7. [ File system configuration status ]                    : Normal
+    A8. [ Disk configuration status ]                           : Normal
+    A9. [ Pre-read block size status ]                          : Normal
+    A10.[ IO scheduler status ]                                 : Normal
+    A11.[ Network card configuration status ]                   : Normal
+    A12.[ Time consistency status ]                             : Warning
+    A13.[ Firewall service status ]                             : Normal
+    A14.[ THP service status ]                                  : Normal
+```
+
+## Helpful Links
+
+[gs_check](1-gs_check), [gs_checkperf](3-gs_checkperf)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/3-gs_checkperf.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/3-gs_checkperf.md
new file mode 100644
index 0000000000000000000000000000000000000000..90b2a63d20d48807400bd535d318728bc7b4d284
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/3-gs_checkperf.md
@@ -0,0 +1,289 @@
+---
+title: gs_checkperf
+summary: gs_checkperf
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_checkperf
+
+## Background
+
+MogDB provides the **gs_checkperf** tool for you to routinely check the MogDB-level performance (such as host CPU, Gauss GPU, and I/O usage), host-level performance (CPU, memory, and I/O usage), session-/process-level performance (CPU, memory, and I/O usage), and SSD performance (write and read performance). This helps you learn the MogDB load and fine-tune database performance accordingly.
+
+## Prerequisites
+
+- MogDB running status is normal and is not the read-only mode.
+- Services are running properly on the database.
+
+## Precautions
+
+- The monitoring information of **gs_checkperf** comes from tables in PMK mode. If the ANALYZE operation is not performed on such tables, **gs_checkperf** may fail to be executed. An example of the error information is as follows:
+
+  ```
+  LOG:  Statistics in some tables or columns(pmk.pmk_snapshot.snapshot_id) are not collected.
+  HINT:  Do analyze for them in order to generate optimized plan.
+  ```
+
+  To fix this error, log in to a node where a master database node is deployed, connect to the **postgres** database, and run the following SQL statements:
+
+  ```
+  analyze pmk.pmk_configuration;
+  analyze pmk.pmk_meta_data;
+  analyze pmk.pmk_snapshot;
+  analyze pmk.pmk_snapshot_dbnode_stat;
+  analyze pmk.pmk_snapshot_datanode_stat;
+  ```
+
+## Syntax
+
+- Check the SSD performance (as user **root**).
+
+  ```
+  gs_checkperf -U USER [-o OUTPUT] -i SSD [-l LOGFILE]
+  ```
+
+- Check the MogDB performance (as the user for installing MogDB).
+
+  ```
+  gs_checkperf [-U USER] [-o OUTPUT] [-i PMK] [--detail] [-l LOGFILE]
+  ```
+
+- Display help information.
+
+  ```
+  gs_checkperf -? | --help
+  ```
+
+- Display version information.
+
+  ```
+  gs_checkperf -V | --version
+  ```
+
+## Parameter Description
+
+- -U
+
+  Specifies the name of the user for running MogDB.
+
+  Value range: name of the user for running MogDB
+
+  Specify this parameter when you run the command as user **root**.
+
+- -o
+
+  Specifies the file for saving performance check reports.
+
+  Value range: the name of a specified file
+
+  If this parameter is not specified, OS check results are displayed on the screen.
+
+- -i
+
+  Specifies the number of a check item. This parameter is case-insensitive. Format: -i PMK and -i SSD
+
+  Value range: PMK and SSD
+
+  Check the PMK item as an MogDB user.
+
+  Check the SSD item as user **root**.
+
+  If this parameter is not specified, the PMK item is checked by default as the MogDB user, and SSD item is checked by default as user **root**.
+
+- -detail
+
+  Displays detailed PMK check results.
+
+- -l
+
+  Specifies the path for saving log files.
+
+  The default path is **/var/log/gaussdb/omm/om/gs_checkperf-YYYY-MM-DD_hhmmss.log**.
+
+- -?, -help
+
+  Displays help information.
+
+- -V, -version
+
+  Displays version information.
+
+**Table 1** Performance check items
+
+| Type                                              | Performance Parameter                                        | Description                                                  |
+| :------------------------------------------------ | :----------------------------------------------------------- | :----------------------------------------------------------- |
+| MogDB level                                       | Host CPU Usage                                               | CPU usage of the host                                        |
+| Gauss CPU Usage                                   | Usage of the Gauss CPU                                       |                                                              |
+| Shared Memory Hit Rate                            | Hit rate of the shared memory                                |                                                              |
+| Memory Sorting Ratio                              | Ratio of completed sorts in memory                           |                                                              |
+| I/O Usage                                         | Number and time of file reads and writes                     |                                                              |
+| Disk Usage                                        | Number of file writes, average write duration, and maximum write duration |                                                              |
+| Transaction Statistics                            | Number of current SQL executions and sessions                |                                                              |
+| Host level                                        | CPU Usage                                                    | Host CPU usage, including CPU busy time and CPU idle time    |
+| Memory Usage                                      | Host memory usage, including total physical memory and used memory |                                                              |
+| I/O Usage                                         | Number and time of file reads and writes                     |                                                              |
+| Session/Process level                             | CPU Usage                                                    | Session CPU usage, including CPU busy time and CPU idle time |
+| Memory Usage                                      | Session memory usage, including total physical memory and used memory |                                                              |
+| I/O Usage                                         | Number of shared buffer hits in a session                    |                                                              |
+| SSD performance (Only user **root** can view it.) | Write Performance                                            | The **dd** command (**flag=direct bs=8M count=2560**) is used to write data into an SSD every 10s. |
+| Read Performance                                  | The **dd** command (**flag=direct bs=8M count=2560**) is used to read data from an SSD every 7s. |                                                              |
+
+## Examples
+
+Example 1: Run the following command to display performance statistics in simple mode on the screen:
+
+```
+gs_checkperf -i pmk -U omm
+Cluster statistics information:
+    Host CPU busy time ratio                     :    1.43       %
+    GaussDB CPU time % in busy time                :    1.88       %
+    Shared Buffer Hit ratio                      :    99.96      %
+    In-memory sort ratio                         :    100.00     %
+    Physical Reads                               :    4
+    Physical Writes                              :    25
+    DB size                                      :    70         MB
+    Total Physical writes                        :    25
+    Active SQL count                             :    2
+    Session count                                :    3
+```
+
+Example 2: Run the following command to display performance statistics in detailed mode on the screen:
+
+```
+gs_checkperf -i pmk -U omm --detail
+Cluster statistics information:
+Host CPU usage rate:
+    Host total CPU time                          :    42386.667  Jiffies
+    Host CPU busy time                           :    1873.333   Jiffies
+    Host CPU iowait time                         :    20.000     Jiffies
+    Host CPU busy time ratio                     :    4.42       %
+    Host CPU iowait time ratio                   :    .05        %
+GaussDB CPU usage rate:
+    GaussDB CPU time % in busy time                :    19.04      %
+    GaussDB CPU time % in total time               :    .84        %
+Shared buffer hit rate:
+    Shared Buffer Reads                          :    0
+    Shared Buffer Hits                           :    24129
+    Shared Buffer Hit ratio                      :    100.00     %    In-memory sort ratio                         :    100.00     %I/O usage:
+    Number of files                              :    537
+    Physical Reads                               :    0
+    Physical Writes                              :    0
+    Read Time                                    :    0          ms
+    Write Time                                   :    0          ms
+Disk usage:
+    DB size                                      :    70         MB
+    Total Physical writes                        :    0
+    Average Physical write                       :    0
+    Maximum Physical write                       :    0
+Activity statistics:
+    Active SQL count                             :    2
+    Session count                                :    3
+Node statistics information:
+dn_6001_6002:
+    GaussDB CPU Time                               :    200        Jiffies
+    Host CPU Busy Time                           :    3490       Jiffies
+    Host CPU Total Time                          :    42330      Jiffies
+    GaussDB CPU Time % in Busy Time                :    5.73       %
+    GaussDB CPU Time % in Total Time               :    .47        %
+    Physical memory                              :    8231776256 Bytes
+    DB Memory usage                              :    877236224  Bytes
+    Shared buffer size                           :    33554432   Bytes
+    Shared buffer hit ratio                      :    100.00     %
+    Sorts in memory                              :    123
+    Sorts in disk                                :    0
+    In-memory sort ratio                         :    100.00     %
+    Number of files                              :    149
+    Physical Reads                               :    0
+    Physical Writes                              :    0
+    Read Time                                    :    0
+    Write Time                                   :    0
+dn_6003_6004:
+    GaussDB CPU Time                               :    170        Jiffies    Host CPU Busy Time                           :    1030       Jiffies
+    Host CPU Total Time                          :    42470      Jiffies    GaussDB CPU Time % in Busy Time                :    16.50      %
+    GaussDB CPU Time % in Total Time               :    .40        %
+    Physical memory                              :    8231776256 Bytes
+    DB Memory usage                              :    881434624  Bytes    Shared buffer size                           :    33554432   Bytes
+    Shared buffer hit ratio                      :    100.00     %
+    Sorts in memory                              :    119
+    Sorts in disk                                :    0
+    In-memory sort ratio                         :    100.00     %
+    Number of files                              :    165
+    Physical Reads                               :    0
+    Physical Writes                              :    0
+    Read Time                                    :    0
+    Write Time                                   :    0
+dn_6005_6006:
+    GaussDB CPU Time                               :    220        Jiffies
+    Host CPU Busy Time                           :    1100       Jiffies
+    Host CPU Total Time                          :    42360      Jiffies
+    GaussDB CPU Time % in Busy Time                :    20.00      %
+    GaussDB CPU Time % in Total Time               :    .52        %
+    Physical memory                              :    8231776256 Bytes
+    DB Memory usage                              :    881430528  Bytes
+    Shared buffer size                           :    33554432   Bytes
+    Shared buffer hit ratio                      :    100.00     %
+    Sorts in memory                              :    122
+    Sorts in disk                                :    0
+    In-memory sort ratio                         :    100.00     %
+    Number of files                              :    115
+    Physical Reads                               :    0
+    Physical Writes                              :    0
+    Read Time                                    :    0
+    Write Time                                   :    0
+Session statistics information(Top 10):
+Session CPU statistics:
+1 dn_6003_6004-postgres-dbazt:
+    Session CPU time                             :    1211
+    Database CPU time                            :    37670
+    Session CPU time %                           :    3.21       %
+2 dn_6005_6006-postgres-dbazt:
+    Session CPU time                             :    1204
+    Database CPU time                            :    35730
+    Session CPU time %                           :    3.37       %
+3 dn_6001_6002-postgres-dbazt:
+    Session CPU time                             :    1064
+    Database CPU time                            :    34120
+    Session CPU time %                           :    3.12       %
+
+Session Memory statistics:
+1 dn_6005_6006-postgres-dbazt:
+    Buffer Reads                                 :    8989
+    Shared Buffer Hit ratio                      :    96.97
+    In Memory sorts                              :    136
+    In Disk sorts                                :    0
+    In Memory sorts ratio                        :    100.00
+    Total Memory Size                            :    21593048
+    Used Memory Size                             :    18496600
+2 dn_6003_6004-postgres-dbazt:
+    Buffer Reads                                 :    9030
+    Shared Buffer Hit ratio                      :    96.94
+    In Memory sorts                              :    133
+    In Disk sorts                                :    0
+    In Memory sorts ratio                        :    100.00
+    Total Memory Size                            :    21576664
+    Used Memory Size                             :    18495688
+3 dn_6001_6002-postgres-dbazt:
+    Buffer Reads                                 :    8668
+    Shared Buffer Hit ratio                      :    96.97
+    In Memory sorts                              :    138
+    In Disk sorts                                :    0
+    In Memory sorts ratio                        :    100.00
+    Total Memory Size                            :    21258856
+    Used Memory Size                             :    18159736
+
+Session IO statistics:
+1 dn_6003_6004-postgres-dbazt:
+    Physical Reads                               :    285
+    Read Time                                    :    5320
+2 dn_6005_6006-postgres-dbazt:
+    Physical Reads                               :    281
+    Read Time                                    :    5811
+3 dn_6001_6002-postgres-dbazt:
+    Physical Reads                               :    271
+    Read Time                                    :    4662
+```
+
+## Helpful Links
+
+[gs_check](1-gs_check), [gs_checkos](2-gs_checkos)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/3.1-gs_clean.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/3.1-gs_clean.md
new file mode 100644
index 0000000000000000000000000000000000000000..157805d3921db312edbacf022c52ccafb34c30c0
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/3.1-gs_clean.md
@@ -0,0 +1,100 @@
+---
+title: gs_clean
+summary: gs_clean
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_clean
+
+## Background
+
+If the database breaks down unexpectedly, residual temporary tables may exist. gs_clean can be used to clear the residual temporary tables.
+
+## Syntax
+
+Connect to the primary DN and clear the residual temporary table of the primary DN transaction.
+
+```
+gs_clean [OPTION ...] [USERNAME]
+```
+
+## Parameter Description
+
+*OPTION* is described as follows:
+
+- -a, -all
+
+  Clears all residual temporary tables in available databases.
+
+- -h, -host=HOSTADDRESS
+
+  Specifies the IP address of the host where the target DN is located.
+
+  Value range: the IP address of the host where the target DN is located.
+
+  Default value: **localhost**
+
+- -p, -port=PORT
+
+  Specifies the port number of the primary DN.
+
+  Value range: port number of the target DN.
+
+  The default value is 5432. If the environment variable *PGPORT* of the OS has been set, the value of *PGPORT* is used by default.
+
+- -q, -quiet
+
+  Prints only error information in quiet mode.
+
+- -r, -rollback
+
+  Rolls back all abnormal transactions.
+
+- -t, -timeout=SECS
+
+  Specifies the timeout mechanism.
+
+  Default value: **5s** Unit: s
+
+- -U, -username=USERNAME
+
+  Specifies the name of the user for connecting to the database.
+
+  Value range: a valid username in the database
+
+  Default value: *OS username*
+
+- -v, -verbose
+
+  Prints detailed restoration information.
+
+- -V, -version
+
+  Prints version information about **gs_clean**.
+
+- -w, -no-password
+
+  Specifies that no password authentication is required.
+
+- -W, -password=PASSWORD
+
+  Specifies that password authentication is required.
+
+  Value range: a valid string. The password must meet the complexity requirement.
+
+- -e, -exclusive
+
+  Cleans temporary tables only.
+
+- -j, -jobs
+
+  Specifies the number of jobs for cleaning two-phase residual files.
+
+  Value range: 1-10
+
+  Default value: **3**
+
+- -?, -help
+
+  Displays help information.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/4-gs_collector.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/4-gs_collector.md
new file mode 100644
index 0000000000000000000000000000000000000000..74320966439913e11aca05845228d65451f4f8e3
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/4-gs_collector.md
@@ -0,0 +1,230 @@
+---
+title: gs_collector
+summary: gs_collector
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_collector
+
+## Background
+
+When MogDB is faulty, **gs_collector** can be used to collect information about the OS, logs, and configuration file of the cluster, helping you locate the fault. You can use the **-C** parameter to specify the information to be collected. [Table 1](#info) describes the information that can be collected.
+
+**Table 1** Information to be collected by gs_collector <a id="info"></a>.
+
+| TypeName | Content                 | Description             | Default Collection              |
+| :------- | :------------------------ | :-----------------------| :-------------------------------- |
+| System   | HardWareInfoRunTimeInfo                                      | Collect the status information about the current OS.<br />- HardWareInfo<br />- CPU (cat /proc/cpuinfo)<br />- Memory (cat /proc/meminfo)<br />- Disk (df -h)<br />- RunTimeInfo:<br />- topStatus (ps ux)<br />- ioStat (iostat -xm 2 3)<br />- Network status (cat /proc/net/dev)<br />- Memory usage (free -m) | Yes                                                          |
+| Database | For details, see **System catalogs and views supported by** **gs_collector**. | Collect system views or system catalogs.                     | Yes. Information about the **pg_locks**, **pg_stat_activity**, and **pg_thread_wait_status** views is collected by default. |
+| Log      | DataNodeClusterManager                                       | Collect **pg_log** and **gs_profile** of the data node.<br />The ClusterManager log information to be collected:<br />- om<br />- gs_ctl<br />- gs_guc<br />- gs_initdb | Yes                                                          |
+| Config   | DataNode                                                     | Collect the data node configuration information:<br />- postgresql.conf<br />- gaussdb.state<br />- pg_hba.conf<br />- pg_control<br />- pg_replslot<br />- pg_ident.conf | Yes                                                          |
+| Gstack   | DataNode                                                     | Run the **gstack** command to obtain the current stack information of the data node. | No                                                           |
+| CoreDump | gs_ctl, gaussdb, GaussMaster, AioWorker, AlarmChecker, Archiver, Auditor, AutoVacLauncher, AutoVacWorker, AuxMain, BackendMode, BgWriter, BootStrap, Catchup, CBMWriter, Checkpointer, CommAuxStream, CommPoolCleane, CommRcvStream, CommRcvWorker, CommSendStream, CpMonitor, DataRcvWriter, DataReceiver, DataSender, ExtremeRTO, FencedUDFMaster, Heartbeater, JobExecutor, JobScheduler, LWLockMonitor, PageWriter, ParallelRecov, PercentileJob, Reaper, RemoteSrv, StartupProcess, StatCollector, Stream, SysLogger, ThdPoolListener, TwoPhaseCleaner, WalRcvWriter, WalReceiver, WalSender, WalWriter, WDRSnapshot, WlmArbiter, WlmCollector, WlmMonitor | Filter the core files of the gaussdb process by time.<br />CAUTION:<br />Configure the core as follows: Add the core file format **core-%e-%p-%t** to the **/proc/sys/mogdb/core_pattern** file. | No                                                           |
+| XLog     | DataNode                                                     | Collect Xlogs that are filtered by time.                     | No                                                           |
+| Plan     |                                                              | Collect planned reproduction information:<br />- If you enter an asterisk (), the planned reproduction information of all databases is collected.<br />- If you enter a specific database name, the planned reproduction information of the specified database is collected. | No                                                           |
+
+## Prerequisites
+
+An OS tool (such as **gstack**) that **gs_collector** requires has been installed. If it is not installed, an error message is displayed, and this collection item is skipped.
+
+## Syntax
+
+- Collect logs (as a non-**root** user).
+
+  ```bash
+  gs_collector --begin-time="BEGINTIME" --end-time="ENDTIME" [-h HOSTNAME | -f HOSTFILE] [--keyword=KEYWORD] [--speed-limit=SPEED] [-o OUTPUT] [-l LOGFILE] [-C CONFIGFILE]
+  ```
+
+- Display help information.
+
+  ```bash
+  gs_collector -? | --help
+  ```
+
+- Display version information.
+
+  ```bash
+  gs_collector -V | --version
+  ```
+
+## Parameter Description
+
+- -h
+
+  Specifies the name of the host whose information is to be collected.
+
+  Value range: host name
+
+  If this parameter is not specified, information about all hosts is collected by default.
+
+- -f
+
+  Specifies the file of a host name list. The file is a plain text file.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The **-f** and **-h** parameters cannot be used together.
+
+  Value range: a host name list
+
+- -o
+
+  Saves collected logs as a package into a specified folder.
+
+  If this parameter is not specified, the check results are saved as a package into the directory specified by **tmpMppdbPath** in the configuration file.
+
+  If **tmpMppdbPath** is not configured in the configuration file, the check results are saved as a package into the **/tmp/***user name***_mppdb/** directory by default.
+
+- -l
+
+  Specifies a log file and its save path.
+
+- -C
+
+  Specifies the configuration file of the information to be collected. **TypeName** is used to specify the type of the information to be collected. **Content** is used to specify the content of each type of information. **Count** is used to specify the number of times for collecting the information. **Interval** is used to specify the collection interval, in seconds.
+
+  The values of **TypeName** and **Content** cannot be empty.
+
+  **Interval** and **Count** are optional. If **Count** is not specified, the information is collected once by default. If **Interval** is not specified, the interval is 0 seconds. The values of **Interval** and **Count** cannot be smaller than 0.
+
+  If the preceding parameters are not specified, the default configuration file is used.
+
+  The configuration file is in JSON format. The template is as follows:
+
+  ```
+  {
+      "Collect":
+      [
+          {"TypeName": "name", "Content":"value","Interval":"seconds", "Count":"count"}
+      ]
+  }
+  ```
+
+  ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+
+  For details about the value ranges of **TypeName** and corresponding **Content**, see [Table 1](#info). The **Interval** and **Count** parameters do not take effect when **TypeName** is **Log**, **CoreDump**, **Config**, or **XLog**.
+
+  The content of the default configuration file is as follows:
+
+  ```
+  {
+   "Collect":
+   [
+   {"TypeName": "System", "Content":"RunTimeInfo, HardWareInfo","Interval":"0", "Count":"1"},
+   {"TypeName": "Log", "Content" : "DataNode,ClusterManager", "Interval":"0", "Count":"1"},
+   {"TypeName": "Database", "Content": "pg_locks,pg_stat_activity,pg_thread_wait_status","Interval":"0", "Count":"1"},
+   {"TypeName": "Config", "Content": "DataNode", "Interval":"0", "Count":"1"}
+   ]
+   }
+  ```
+
+- -keyword=KEYWORD
+
+  Specifies a log file containing the keyword.
+
+  If the keyword contains spaces, quote the keyword with double quotations marks ("").
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** Logs about the performance are binary logs. The keyword collection function does not support performance log collection.
+
+- -begin-time
+
+  Start time of the search time range. The input format: yyyymmdd hh:mm
+
+- -end-time
+
+  End time of the search time range. The input format: yyyymmdd hh:mm
+
+- -speed-limit
+
+  Specifies the log collection rate. The value is a non-negative integer in the unit of MB/s.
+
+  This parameter is used to prevent high disk or network I/O from being generated during log collection. If database nodes are deployed on the same disk where the **$GAUSSLOG/$PGHOST** path is located, they may become faulty due to high I/O. The value of this parameter must not exceed 1⁄3 of the minimum value of the disk and network I/O in MogDB.
+
+- -?, -help
+
+  Displays help information.
+
+- -V, -version
+
+  Displays version information.
+
+## Examples
+
+Run the following command to collect OS and log information:
+
+```
+gs_collector --begin-time="20180131 23:00" --end-time="20180201 20:00" -h plat1
+Successfully parsed the configuration file.
+create Dir.
+Successfully create dir.
+do system check interval 0 : count 1
+Collecting OS information.
+Successfully collected OS information.
+do database check interval 0 : count 1
+Collecting catalog statistics.
+Successfully collected catalog statistics.
+do log check interval 0 : count 1
+Collecting Log files.
+Successfully collected Log files.
+do Config check 0:1
+Collecting Config files.
+Successfully collected Config files.
+Collecting files.
+Successfully collected files.
+All results are stored in $PGHOST/collector_20200624_134541.tar.gz.
+```
+
+Run the following command to query the collected statistics:
+
+```
+tar -zxvf $PGHOST/collector_20200624_134541.tar.gz
+collector_20200624_134541/
+collector_20200624_134541/plat1.tar.gz
+collector_20200624_134541/Detail.log
+collector_20200624_134541/Summary.log
+cd collector_20200624_134541
+tar -zxvf plat1.tar.gz
+plat1/
+plat1/catalogfiles/
+plat1/catalogfiles/gs_clean_20200624_134548283647.txt
+plat1/catalogfiles/dn_6001_pg_locks_20200624_134547746215.csv
+plat1/catalogfiles/dn_6001_pg_thread_wait_status_20200624_134548068716.csv
+plat1/catalogfiles/dn_6001_pg_stat_activity_20200624_134547851117.csv
+plat1/configfiles/
+plat1/logfiles/
+plat1/logfiles/log_20200624_134548540916.tar.gz
+plat1/coreDumpfiles/
+plat1/gstackfiles/
+plat1/systemfiles/
+plat1/systemfiles/OS_information_20200624_134542218134.txt
+plat1/systemfiles/database_system_info_20200624_134546282006.txt
+plat1/planSimulatorfiles/
+plat1/xlogfiles/
+cd plat1/logfiles/
+tar -zxvf log_20200624_134548540916.tar.gz
+./
+./om/
+./om/gs_preinstall-2020-06-24_113654.log
+./om/gs_local-2020-06-24_113710.log
+./om/gs_install-2020-06-24_113911.log
+./om/gs_checkperf-2020-06-24_114311.log
+./om/gs_collector-2020-06-24_114240.log
+./om/gs_backup-2020-06-24_114101.log
+./om/gs_om-2020-06-24_114052.log
+./bin/
+./bin/gs_initdb/
+./bin/gs_initdb/gs_initdb-2020-06-24_114010-current.log
+./bin/gs_guc/
+./bin/gs_guc/gs_guc-2020-06-24_114033-current.log
+./bin/gs_ctl/
+./bin/gs_ctl/gs_ctl-2020-06-24_114041-current.log
+./pg_log/
+./pg_log/dn_6001/
+./pg_log/dn_6001/postgresql-2020-06-24_114043.log
+./pg_log/dn_6001/postgresql-2020-06-24_114330.log
+./pg_log/dn_6001/postgresql-2020-06-24_114316.log
+./gs_profile/
+./gs_profile/dn_6001_6002/
+./gs_profile/dn_6001_6002/postgresql-2020-06-24_114330.prf
+./gs_profile/dn_6001_6002/postgresql-2020-06-24_114316.prf
+./gs_profile/dn_6001_6002/postgresql-2020-06-24_114043.prf
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/5-gs_dump.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/5-gs_dump.md
new file mode 100644
index 0000000000000000000000000000000000000000..793910f2d31e109458896898b80be84e2899fdc6
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/5-gs_dump.md
@@ -0,0 +1,556 @@
+---
+title: gs_dump
+summary: gs_dump
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_dump
+
+## Background
+
+gs_dump, provided by MogDB, is used to export database information. You can export a database or its objects (such as schemas, tables, and views). The database can be the default postgres database or a user-specified database.
+
+**gs_dump** is executed by OS user **omm**.
+
+When **gs_dump** is used to export data, other users can still access (read and write) MogDB databases.
+
+**gs_dump** can export complete, consistent data. For example, if **gs_dump** is started to export database A at T1, data of the database at that time point will be exported, and modifications on the database after that time point will not be exported.
+
+The generated columns are not dumped when gs_dump is used.
+
+gs_dump can export data to**txt** files that are compatible with the database of v1.
+
+**gs_dump** can export database information to a plain-text SQL script file or archive file.
+
+- Plain-text SQL script: It contains the SQL statements required to restore the database. You can use **gsql** to execute the SQL script. With only a little modification, the SQL script can rebuild a database on other hosts or database products.
+- Archive file: It contains data required to restore the database. It can be a tar-, directory-, or custom-format archive. For details, see [Table 1](#formats). The export result must be used with **gs_restore** to restore the database. The system allows users to select or even to sort the content to be imported.
+
+## Functions
+
+**gs_dump** can create export files in four formats, which are specified by **-F** or **-format=**, as listed in [Table 1](#formats).
+
+**Table 1** Formats of exported files <a id="formats"> </a>
+
+| Format     | Value of **-F** | Description                                                  | Suggestion                                                   | Corresponding Import Tool                                    |
+| :--------- | :-------------- | :----------------------------------------------------------- | :----------------------------------------------------------- | :----------------------------------------------------------- |
+| Plain-text | p               | A plain-text script file containing SQL statements and commands. The commands can be executed on **gsql**, a command line terminal, to recreate database objects and load table data. | You are advised to use plain-text exported files for small databases. | Before using **gsql** to restore database objects, you can use a text editor to edit the plain-text export file as required. |
+| Custom     | c               | A binary file that allows the restoration of all or selected database objects from an exported file. | You are advised to use custom-format archive files for medium or large database. | You can use **gs_restore** to import database objects from a custom-format archive. |
+| Directory  | d               | A directory containing directory files and the data files of tables and BLOB objects. | -                                                            |                                                              |
+| .tar       | t               | A tar-format archive that allows the restoration of all or selected database objects from an exported file. It cannot be further compressed and has an 8-GB limitation on the size of a single table. | -                                                            |                                                              |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> You can use the gs_dump program to compress the file into a directory archive or custom archive export file to reduce the size of the export file. When generating catalog archives or custom archive export files, medium-level compression is performed by default. The gs_dump program cannot compress the archived export file.
+
+## Precautions
+
+- Do not modify an exported file or its content. Otherwise, restoration may fail.
+
+- To ensure the data consistency and integrity, **gs_dump** acquires a share lock on a table to be dumped. If another transaction has acquired a share lock on the table, **gs_dump** waits until this lock is released and then locks the table for dumping. If the table cannot be locked within the specified time, the dump fails. You can customize the timeout duration to wait for lock release by specifying the **-lock-wait-timeout** parameter.
+- Stored procedures and functions cannot be exported in encrypted mode.
+
+## Syntax
+
+```bash
+gs_dump [OPTION]... [DBNAME]
+```
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** *DBNAME* does not follow a short or long option. It specifies the database to be connected. For example: Specify *DBNAME* without a **-d** option preceding it.
+
+```bash
+gs_dump -p port_number  postgres -f dump1.sql
+```
+
+or
+
+```
+export PGDATABASE=postgres
+gs_dump -p port_number -f dump1.sql
+```
+
+Environment variable: *PGDATABASE*
+
+## Parameter Description
+
+Common parameters
+
+- -f, -file=FILENAME
+
+  Sends the output to the specified file or directory. If this parameter is omitted, the standard output is generated. If the output format is **(-F c/-F d/-F t)**, the **-f** parameter must be specified. If the value of the **-f** parameter contains a directory, the current user must have the read and write permissions on the directory, and the directory cannot be an existing one.
+
+- -F, -format=c|d|t|p
+
+    Selects the exported file format. The format can be:
+
+  - **p|plain**: Generates a text SQL script file. This is the default value.
+
+  - **c|custom**: Outputs a custom-format archive as a directory to be used as the input of **gs_restore**. This is the most flexible output format in which users can manually select it and reorder the archived items during restoration. An archive in this format is compressed by default.
+
+  - **d|directory**: Creates a directory containing directory files and the data files of tables and BLOBs.
+
+  - **t|tar**: Outputs a .tar archive as the input of **gs_restore**. The .tar format is compatible with the directory format. Extracting a .tar archive generates a valid directory-format archive. However, the .tar archive cannot be further compressed and has an 8-GB limitation on the size of a single table. The order of table data items cannot be changed during restoration.
+
+    A .tar archive can be used as input of **gsql**.
+
+- -v, -verbose
+
+  Specifies the verbose mode. If it is specified, **gs_dump** writes detailed object comments and the number of startups/stops to the dump file, and progress messages to standard error.
+
+- -V, -version
+
+  Prints the **gs_dump** version and exits.
+
+- -Z, -compress=0-9
+
+    Specifies the used compression level.
+
+    Value range: 0-9
+
+  - **0** indicates no compression.
+  - **1** indicates that the compression ratio is the lowest and processing speed the fastest.
+  - **9** indicates that the compression ratio is the highest and processing speed the slowest.
+
+    For the custom-format archive, this option specifies the compression level of a single table data segment. By default, data is compressed at a medium level. The plain text format or .tar archive formats do not support compression currently.
+
+- -lock-wait-timeout=TIMEOUT
+
+  Do not keep waiting to obtain shared table locks since the beginning of the dump. Consider it as failed if you are unable to lock a table within the specified time. The timeout period can be specified in any of the formats accepted by **SET statement_timeout**.
+
+- -?, -help
+
+  Displays help about **gs_dump** parameters and exits.
+
+Dump parameters:
+
+- -a, -data-only
+
+  Generates only the data, not the schema (data definition). Dump the table data, big objects, and sequence values.
+
+- -b, -blobs
+
+  Specifies a reserved port for function expansion. This parameter is not recommended.
+
+- -c, -clean
+
+  Before writing the command of creating database objects into the backup file, writes the command of clearing (deleting) database objects to the backup files. (If no objects exist in the target database, **gs_restore** probably displays some error information.)
+
+  This parameter is used only for the plain-text format. For the archive format, you can specify the option when using **gs_restore**.
+
+- -C, -create
+
+  The backup file content starts with the commands of creating the database and connecting to the created database. (If the command script is executed in this mode, you can specify any database to run the command for creating a database. The data is restored to the created database instead of the specified database.)
+
+  This parameter is used only for the plain-text format. For the archive format, you can specify the option when using **gs_restore**.
+
+- -E, -encoding=ENCODING
+
+  Creates a dump file in the specified character set encoding. By default, the dump file is created in the database encoding. (Alternatively, you can set the environment variable **PGCLIENTENCODING** to the required dump encoding.)
+
+- -n, -schema=SCHEMA
+
+    Dumps only schemas matching the schema names. This option contains the schema and all its contained objects. If this option is not specified, all non-system schemas in the target database will be dumped. Multiple schemas can be selected by specifying multiple **-n** options. The schema parameter is interpreted as a pattern according to the same rules used by the **\d** command of **gsql**. Therefore, multiple schemas can also be selected by writing wildcard characters in the pattern. When you use wildcard characters, quote the pattern to prevent the shell from expanding the wildcard characters.
+
+    ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+
+  - If **-n** is specified, **gs_dump** does not dump any other database objects which the selected schemas might depend upon. Therefore, there is no guarantee that the results of a specific-schema dump can be automatically restored to an empty database.
+  - If **-n** is specified, the non-schema objects are not dumped.
+
+    Multiple schemas can be dumped. Entering **-n** *schemaname* multiple times dumps multiple schemas.
+
+    For example:
+
+    ```bash
+    gs_dump -h host_name -p port_number postgres -f backup/bkp_shl2.sql -n sch1 -n sch2
+    ```
+
+    In the preceding example, **sch1** and **sch2** are dumped.
+
+- -N, -exclude-schema=SCHEMA
+
+  Does not dump any schemas matching the schemas pattern. The pattern is interpreted according to the same rules as for **-n**. **-N** can be specified multiple times to exclude schemas matching any of the specified patterns.
+
+  When both **-n** and **-N** are specified, the schemas that match at least one **-n** option but no **-N** is dumped. If **-N** is specified and **-n** is not, the schemas matching **-N** are excluded from what is normally dumped.
+
+  Dump allows you to exclude multiple schemas during dumping.
+
+  Specify **-N exclude schema name** to exclude multiple schemas during dumping.
+
+  For example:
+
+  ```bash
+  gs_dump -h host_name -p port_number postgres -f backup/bkp_shl2.sql -N sch1 -N sch2
+  ```
+
+  In the preceding example, **sch1** and **sch2** will be excluded during the dumping.
+
+- -o, -oids
+
+  Dumps object identifiers (OIDs) as parts of the data in each table. Use this option if your application references the OID columns in some way. If the preceding situation does not occur, do not use this parameter.
+
+- -O, -no-owner
+
+  Do not output commands to set ownership of objects to match the original database. By default, **gs_dump** issues the **ALTER OWNER** or **SET SESSION AUTHORIZATION** statement to set ownership of created database objects. These statements will fail when the script is running unless it is started by a system administrator (or the same user that owns all of the objects in the script). To make a script that can be stored by any user and give the user ownership of all objects, specify **-O**.
+
+  This parameter is used only for the plain-text format. For the archive format, you can specify the option when using **gs_restore**.
+
+- -s, -schema-only <a id="schema-only"> </a>
+
+  Dumps only the object definition (schema) but not data.
+
+- -S, -sysadmin=NAME
+
+  Specifies a reserved port for function expansion. This parameter is not recommended.
+
+- -t, -table=TABLE
+
+    Specifies a list of tables, views, sequences, or foreign tables to be dumped. You can use multiple **-t** parameters or wildcard characters to specify tables.
+
+    When you use wildcard characters, quote patterns to prevent the shell from expanding the wildcard characters.
+
+    The **-n** and **-N** options have no effect when **-t** is used, because tables selected by using **-t** will be dumped regardless of those options.
+
+    ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+
+  - The number of **-t** parameters must be less than or equal to 100.
+  - If the number of **-t** parameters is greater than 100, you are advised to use the **-include-table-file** parameter to replace some **-t** parameters.
+  - If **-t** is specified, **gs_dump** does not dump any other database objects which the selected tables might depend upon. Therefore, there is no guarantee that the results of a specific-table dump can be automatically restored to an empty database.
+  - **-t tablename** only dumps visible tables in the default search path. **-t '\*.tablename'** dumps *tablename* tables in all the schemas of the dumped database. **-t schema.table** dumps tables in a specific schema.
+  - **-t tablename** does not export trigger information from a table.
+
+    For example:
+
+    ```bash
+    gs_dump -h host_name -p port_number postgres -f backup/bkp_shl2.sql -t schema1.table1 -t schema2.table2
+    ```
+
+    In the preceding example, **schema1.table1** and **schema2.table2** are dumped.
+
+- -include-table-file=FILENAME
+
+  Specifies the table file to be dumped.
+
+- -T, -exclude-table=TABLE
+
+  Specifies a list of tables, views, sequences, or foreign tables not to be dumped. You can use multiple **-T** parameters or wildcard characters to specify tables.
+
+  When **-t** and **-T** are input, the object will be stored in **-t** list not **-T** table object.
+
+  For example:
+
+  ```bash
+  gs_dump -h host_name -p port_number postgres -f backup/bkp_shl2.sql -T table1 -T table2
+  ```
+
+  In the preceding example, **table1** and **table2** are excluded from the dumping.
+
+- -exclude-table-file=FILENAME
+
+  Specifies the table files that do not need to be dumped.
+
+  ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  Same as **-include-table-file**, the content format of this parameter is as follows:
+  schema1.table1
+  schema2.table2
+  ……
+
+- -x, -no-privileges|-no-acl
+
+  Prevents the dumping of access permissions (grant/revoke commands).
+
+- -q, -target
+
+  Specifies the exported TXT files that are compatible with databases of other versions. Currently, v1 and v5 parameters are supported. The v1 parameter is used to export v5 database data to a text file that is compatible with v1. The v5 parameter is used to export v5 database data to a text file in the v5 format, and this can reduce possible errors.
+
+  When using the v1 parameter, you are advised to use it together with -exclude-guc="enable_cluster_resize", -exclude-function, and -exclude-with. Otherwise, an error may be reported when data is exported to v1.
+
+- -exclude-guc
+
+  Specifies that the exported TXT file does not include GUC-related set commands. Currently, only **enable_cluster_resize** is supported.
+
+- -exclude-function
+
+  Does not export functions and stored procedures.
+
+- -exclude-with
+
+  Defines the table to be exported where the table does not add such description as WITH(orientation=row，compression=on) at the end.
+
+- -binary-upgrade
+
+  Specifies a reserved port for function expansion. This parameter is not recommended.
+
+- -binary-upgrade-usermap="USER1=USER2"
+
+  Specifies a reserved port for function expansion. This parameter is not recommended.
+
+- -column-inserts|-attribute-inserts
+
+  Exports data by running the **INSERT** command with explicit column names **{INSERT INTO table (column, …) VALUES …}**. This will cause a slow restoration. However, since this option generates an independent command for each row, an error in reloading a row causes only the loss of the row rather than the entire table content.
+
+- -disable-dollar-quoting
+
+  Disables the use of dollar sign ($) for function bodies, and forces them to be quoted using the SQL standard string syntax.
+
+- -disable-triggers
+
+  Specifies a reserved port for function expansion. This parameter is not recommended.
+
+- -exclude-table-data=TABLE
+
+  Does not dump data that matches any of table patterns. The pattern is interpreted according to the same rules as for **-t**.
+
+  **-exclude-table-data** can be entered more than once to exclude tables matching any of several patterns. When you need the specified table definition rather than data in the table, this option is helpful.
+
+  To exclude data of all tables in the database, see [-schema-only](#schema-only).
+
+- -inserts
+
+  Dumps data by the **INSERT** statement (rather than **COPY**). This will cause a slow restoration.
+
+  However, since this option generates an independent command for each row, an error in reloading a row causes only the loss of the row rather than the entire table content. The restoration may fail if you rearrange the column order. The **-column-inserts** option is unaffected against column order changes, though even slower.
+
+- -no-security-labels
+
+  Specifies a reserved port for function expansion. This parameter is not recommended.
+
+- -no-tablespaces
+
+  Does not issue commands to select tablespaces. All the objects will be created during restoration, no matter which tablespace is selected when using this option.
+
+  This parameter is used only for the plain-text format. For the archive format, you can specify the option when using **gs_restore**.
+
+- -no-unlogged-table-data
+
+  Specifies a reserved port for function expansion. This parameter is not recommended.
+
+- -non-lock-table
+
+  Specifies a reserved port for function expansion. This parameter is not recommended.
+
+- -include-alter-table
+
+  Dumps deleted columns of tables. This option records deleted columns.
+
+- -quote-all-identifiers
+
+  Forcibly quotes all identifiers. This parameter is useful when you dump a database for migration to a later version, in which additional keywords may be introduced.
+
+- -section=SECTION
+
+  Specifies dumped name sections (pre-data, data, or post-data).
+
+- -serializable-deferrable
+
+  Uses a serializable transaction for the dump to ensure that the used snapshot is consistent with later database status. Perform this operation at a time point in the transaction flow, at which everything is normal. This ensures successful transaction and avoids serialization failures of other transactions, which requires serialization again.
+
+  This option has no benefits for disaster recovery. During the upgrade of the original database, loading a database copy as a report or loading other shared read-only dump is helpful. If the option does not exist, dump reveals a status which is different from the submitted sequence status of any transaction.
+
+  This option will make no difference if there are no active read-write transactions when **gs_dump** is started. If the read-write transactions are in active status, the dump start time will be delayed for an uncertain period.
+
+- -use-set-session-authorization
+
+  Specifies that the standard SQL **SET SESSION AUTHORIZATION** command rather than **ALTER OWNER** is returned to ensure the object ownership. This makes dumping more standard. However, if a dump file contains objects that have historical problems, restoration may fail. A dump using **SET SESSION AUTHORIZATION** requires the system administrator permissions, whereas **ALTER OWNER** requires lower permissions.
+
+- -with-encryption=AES128
+
+  Specifies that dumping data needs to be encrypted using AES128.
+
+- -with-key=KEY
+
+    AES128 key length rules are as follows:
+
+  - The key length is 8 ~ 16 characters.
+  - At least three of the four types of characters are included: uppercase letters (A-Z), lowercase letters (A-Z), numbers (0-9), non alphanumeric characters (limited to ~! @ #$% ^ & * () - = + \ | [] {};:, &lt;. &gt; /?).
+
+    **NOTE:**
+
+  - When using the gs_dump tool for encrypted export, only plain format export is supported. The data exported through -F plain needs to be imported through the gsql tool, and if it is imported through encryption, the -with-key parameter must be specified when importing through gsql.
+  - Stored procedures and functions cannot be exported in encrypted mode.
+
+- -with-salt=RANDVALUES
+
+  gs_dumpall uses this parameter to pass random values.
+
+- -include-extension
+
+  Include extensions in the dump.
+
+- -include-depend-objs
+
+  Includes information about the objects that depend on the specified object in the backup result. This parameter takes effect only if the **-t** or **-include-table-file** parameter is specified.
+
+- -exclude-self
+
+  Excludes information about the specified object from the backup result. This parameter takes effect only if the **-t** or **-include-table-file** parameter is specified.
+
+- -dont-overwrite-file
+
+  The existing files in plain-text, .tar, and custom formats will be overwritten. This option is not used for the directory format.
+
+  For example:
+
+  Assume that the **backup.sql** file exists in the current directory. If you specify **-f backup.sql** in the input command, and the **backup.sql** file is generated in the current directory, the original file will be overwritten.
+
+  If the backup file already exists and **-dont-overwrite-file** is specified, an error will be reported with the message that the dump file exists.
+
+  ```bash
+  gs_dump -p port_number postgres -f backup.sql -F plain --dont-overwrite-file
+  ```
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+
+- The **-s/-schema-only** and **-a/-data-only** parameters do not coexist.
+- The **-c/-clean** and **-a/-data-only** parameters do not coexist.
+- **-inserts/-column-inserts** and **-o/-oids** do not coexist, because **OIDS** cannot be set using the **INSERT** statement.
+- **-role** must be used in conjunction with **-rolepassword**.
+- **-binary-upgrade-usermap** must be used in conjunction with **-binary-upgrade**.
+- **-include-depend-objs** or **-exclude-self** takes effect only when **-t** or **-include-table-file** is specified.
+- **-exclude-self** must be used in conjunction with **-include-depend-objs**.
+
+Connection parameters:
+
+- -h, -host=HOSTNAME
+
+  Specifies the host name. If the value begins with a slash (/), it is used as the directory for the UNIX domain socket. The default value is taken from the **PGHOST** environment variable (if available). Otherwise, a Unix domain socket connection is attempted.
+
+  This parameter is used only for defining names of the hosts outside MogDB. The names of the hosts inside MogDB must be 127.0.0.1.
+
+  Example: *host name*
+
+  Environment variable: **PGHOST**
+
+- -p, -port=PORT
+
+  Specifies the host port number. If the thread pool function is enabled, you are advised to use **pooler port**, that is, the host port number plus 1.
+
+  Environment variable: **PGPORT**
+
+- -U, -username=NAME
+
+  Specifies the username of the host to be connected.
+
+  If the username of the host to be connected is not specified, the system administrator is used by default.
+
+  Environment variable: **PGUSER**
+
+- -w, -no-password
+
+  Never issues a password prompt. The connection attempt fails if the host requires password verification and the password is not provided in other ways. This parameter is useful in batch jobs and scripts in which no user password is required.
+
+- -W, -password=PASSWORD
+
+  Specifies the user password for connection. If the host uses the trust authentication policy, the administrator does not need to enter the **-W** option. If the **-W** option is not provided and you are not a system administrator, the Dump Restore tool will ask you to enter a password.
+
+- -role=ROLENAME
+
+  Specifies a role name to be used for creating the dump. If this option is selected, the **SET ROLE** command will be issued after the database is connected to **gs_dump**. It is useful when the authenticated user (specified by **-U**) lacks the permissions required by **gs_dump**. It allows the user to switch to a role with the required permissions. Some installations have a policy against logging in directly as a super administrator. This option allows dumping data without violating the policy.
+
+- -rolepassword=ROLEPASSWORD
+
+  Specifies the password for a role.
+
+## Notice
+
+If any local additions need to be added to the template1 database in MogDB, restore the output of **gs_dump** into an empty database with caution. Otherwise, you are likely to obtain errors due to duplicate definitions of the added objects. To create an empty database without any local additions, copy data from template0 rather than template1. Example:
+
+```
+CREATE DATABASE foo WITH TEMPLATE template0;
+```
+
+The .tar file size must be smaller than 8 GB. (This is the .tar file format limitations.) The total size of a .tar archive and any of the other output formats are not limited, except possibly by the OS.
+
+The dump file generated by **gs_dump** does not contain the statistics used by the optimizer to make execution plans. Therefore, you are advised to run **ANALYZE** after restoring from a dump file to ensure optimal performance. The dump file does not contain any **ALTER DATABASE … SET** commands. These settings are dumped by **gs_dumpall**, along with database users and other installation settings.
+
+## Examples
+
+Use **gs_dump** to dump a database as a SQL text file or a file in other formats.
+
+In the following examples, **Bigdata@123** indicates the password for the database user. **backup/MPPDB_backup.sql** indicates an exported file where **backup** indicates the relative path of the current directory. **37300** indicates the port number of the database server. **postgres** indicates the name of the database to be accessed.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** Before exporting files, ensure that the directory exists and you have the read and write permissions on the directory.
+
+Example 1: Use **gs_dump** to export the full information of the postgres database. The exported **MPPDB_backup.sql** file is in plain-text format.
+
+```bash
+gs_dump -U omm -W Bigdata@123 -f backup/MPPDB_backup.sql -p 37300 postgres -F p
+gs_dump[port='37300'][postgres][2018-06-27 09:49:17]: The total objects number is 356.
+gs_dump[port='37300'][postgres][2018-06-27 09:49:17]: [100.00%] 356 objects have been dumped.
+gs_dump[port='37300'][postgres][2018-06-27 09:49:17]: dump database postgres successfully
+gs_dump[port='37300'][postgres][2018-06-27 09:49:17]: total time: 1274  ms
+```
+
+Use **gsql** to import data from the exported plain-text file.
+
+Example 2: Use **gs_dump** to export the full information of the postgres database. The exported **MPPDB_backup.tar** file is in .tar format.
+
+```bash
+gs_dump -U omm -W Bigdata@123 -f backup/MPPDB_backup.tar -p 37300 postgres -F t
+gs_dump[port='37300'][postgres][2018-06-27 10:02:24]: The total objects number is 1369.
+gs_dump[port='37300'][postgres][2018-06-27 10:02:53]: [100.00%] 1369 objects have been dumped.
+gs_dump[port='37300'][postgres][2018-06-27 10:02:53]: dump database postgres successfully
+gs_dump[port='37300'][postgres][2018-06-27 10:02:53]: total time: 50086  ms
+```
+
+Example 3: Use **gs_dump** to export the full information of the postgres database. The exported **MPPDB_backup.dmp** file is in custom format.
+
+```bash
+gs_dump -U omm -W Bigdata@123 -f backup/MPPDB_backup.dmp -p 37300 postgres -F c
+gs_dump[port='37300'][postgres][2018-06-27 10:05:40]: The total objects number is 1369.
+gs_dump[port='37300'][postgres][2018-06-27 10:06:03]: [100.00%] 1369 objects have been dumped.
+gs_dump[port='37300'][postgres][2018-06-27 10:06:03]: dump database postgres successfully
+gs_dump[port='37300'][postgres][2018-06-27 10:06:03]: total time: 36620  ms
+```
+
+Example 4: Use **gs_dump** to export the full information of the postgres database. The exported **MPPDB_backup** file is in directory format.
+
+```bash
+gs_dump -U omm -W Bigdata@123 -f backup/MPPDB_backup -p 37300  postgres -F d
+gs_dump[port='37300'][postgres][2018-06-27 10:16:04]: The total objects number is 1369.
+gs_dump[port='37300'][postgres][2018-06-27 10:16:23]: [100.00%] 1369 objects have been dumped.
+gs_dump[port='37300'][postgres][2018-06-27 10:16:23]: dump database postgres successfully
+gs_dump[port='37300'][postgres][2018-06-27 10:16:23]: total time: 33977  ms
+```
+
+Example 5: Use **gs_dump** to export the information of the postgres database, excluding the information of the table specified in the **/home/MPPDB_temp.sql** file. The exported **MPPDB_backup.sql** file is in plain-text format.
+
+```bash
+gs_dump -U omm -W Bigdata@123 -p 37300 postgres --exclude-table-file=/home/MPPDB_temp.sql -f backup/MPPDB_backup.sql
+gs_dump[port='37300'][postgres][2018-06-27 10:37:01]: The total objects number is 1367.
+gs_dump[port='37300'][postgres][2018-06-27 10:37:22]: [100.00%] 1367 objects have been dumped.
+gs_dump[port='37300'][postgres][2018-06-27 10:37:22]: dump database postgres successfully
+gs_dump[port='37300'][postgres][2018-06-27 10:37:22]: total time: 37017  ms
+```
+
+Example 6: Use **gs_dump** to export only the information about the views that depend on the **testtable** table. Create another **testtable** table, and then restore the views that depend on it.
+
+- Back up only the views that depend on the **testtable** table.
+
+  ```bash
+  gs_dump -s -p 37300 postgres -t PUBLIC.testtable --include-depend-objs --exclude-self -f backup/MPPDB_backup.sql -F p
+  gs_dump[port='37300'][postgres][2018-06-15 14:12:54]: The total objects number is 331.
+  gs_dump[port='37300'][postgres][2018-06-15 14:12:54]: [100.00%] 331 objects have been dumped.
+  gs_dump[port='37300'][postgres][2018-06-15 14:12:54]: dump database postgres successfully
+  gs_dump[port='37300'][postgres][2018-06-15 14:12:54]: total time: 327  ms
+  ```
+
+- Change the name of the **testtable** table.
+
+  ```
+  gsql -p 37300 postgres -r -c "ALTER TABLE PUBLIC.testtable RENAME TO testtable_bak;"
+  ```
+
+- Create another **testtable** table.
+
+  ```
+  CREATE TABLE PUBLIC.testtable(a int, b int, c int);
+  ```
+
+- Restore the views for the new **testtable** table.
+
+  ```
+  gsql -p 37300 postgres -r -f backup/MPPDB_backup.sql
+  ```
+
+## Helpful Links
+
+[gs_dumpall](6-gs_dumpall) and [gs_restore](9-gs_restore)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/6-gs_dumpall.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/6-gs_dumpall.md
new file mode 100644
index 0000000000000000000000000000000000000000..1e8f4b36629e57f1fcd43d073d6f566fc6ac0414
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/6-gs_dumpall.md
@@ -0,0 +1,274 @@
+---
+title: gs_dumpall
+summary: gs_dumpall
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_dumpall
+
+## Background
+
+**gs_dumpall**, provided by MogDB, is used to export all MogDB database information, including data of the default database postgres, user-defined databases, and common global objects of all MogDB databases.
+
+**gs_dumpall** is executed by OS user **omm**.
+
+When **gs_dumpall** is used to export data, other users can still access (read and write) MogDB databases.
+
+**gs_dumpall** can export complete, consistent data. For example, if **gs_dumpall** is started to export MogDB database at T1, data of the database at that time point will be exported, and modifications on the database after that time point will not be exported.
+
+The generated columns are not dumped when gs_dumpall is used.
+
+**gs_dumpall** exports all MogDB databases in two parts:
+
+- **gs_dumpall** exports all global objects, including information about database users and groups, tablespaces, and attributes (for example, global access permissions).
+- **gs_dumpall** invokes **gs_dump** to export SQL scripts from each MogDB database, which contain all the SQL statements required to restore databases.
+
+The exported files are both plain-text SQL scripts. Use gsql to execute them to restore MogDB databases.
+
+## Precautions
+
+- Do not modify an exported file or its content. Otherwise, restoration may fail.
+- To ensure the data consistency and integrity, **gs_dumpall** acquires a share lock on a table to be dumped. If another transaction has acquired a share lock on the table, **gs_dumpall** waits until this lock is released and then locks the table for dumping. If the table cannot be locked within the specified time, the dump fails. You can customize the timeout duration to wait for lock release by specifying the **-lock-wait-timeout** parameter.
+- During an export, **gs_dumpall** reads all tables in a database. Therefore, you need to connect to the database as an MogDB administrator to export a complete file. When you use **gsql** to execute SQL scripts, cluster administrator permissions are also required to add users and user groups, and create databases.
+
+## Syntax
+
+```bash
+gs_dumpall [OPTION]...
+```
+
+## Parameter Description
+
+Common parameters:
+
+- -f, -filename=FILENAME
+
+  Sends the output to the specified file. If this parameter is omitted, the standard output is generated.
+
+- -v, -verbose
+
+  Specifies the verbose mode. If it is specified, **gs_dumpall** writes detailed object comments and number of startups/stops to the dump file, and progress messages to standard error.
+
+- -V, -version
+
+  Prints the *gs_dumpall* version and exits.
+
+- -lock-wait-timeout=TIMEOUT
+
+  Do not keep waiting to obtain shared table locks at the beginning of the dump. Consider it as failed if you are unable to lock a table within the specified time. The timeout period can be specified in any of the formats accepted by **SET statement_timeout**.
+
+- -?, -help
+
+  Displays help about **gs_dumpall** parameters and exits.
+
+Dump parameters:
+
+- -a, -data-only
+
+  Dumps only the data, not the schema (data definition).
+
+- -c, -clean
+
+  Runs SQL statements to delete databases before rebuilding them. Statements for dumping roles and tablespaces are added.
+
+- -g, -globals-only
+
+  Dumps only global objects (roles and tablespaces) but no databases.
+
+- -o, -oids
+
+  Dumps object identifiers (OIDs) as parts of the data in each table. Use this parameter if your application references the OID columns in some way. If the preceding situation does not occur, do not use this parameter.
+
+- -O, -no-owner
+
+  Do not output commands to set ownership of objects to match the original database. By default, **gs_dumpall** issues the **ALTER OWNER** or **SET SESSION AUTHORIZATION** command to set ownership of created schema objects. These statements will fail when the script is running unless it is started by a system administrator (or the same user that owns all of the objects in the script). To make a script that can be stored by any user and give the user ownership of all objects, specify **-O**.
+
+- -r, -roles-only
+
+  Dumps only roles but not databases or tablespaces.
+
+- -s, -schema-only
+
+  Dumps only the object definition (schema) but not data.
+
+- -S, -sysadmin=NAME
+
+  Name of the system administrator during the dump.
+
+- -t, -tablespaces-only
+
+  Dumps only tablespaces but not databases or roles.
+
+- -x, -no-privileges
+
+  Prevents the dumping of access permissions (grant/revoke commands).
+
+- -column-inserts|-attribute-inserts
+
+  Exports data by running the **INSERT** command with explicit column names **{INSERT INTO table (column, …) VALUES …}**. This will cause a slow restoration. However, since this option generates an independent command for each row, an error in reloading a row causes only the loss of the row rather than the entire table content.
+
+- -disable-dollar-quoting
+
+  Disables the use of dollar sign ($) for function bodies, and forces them to be quoted using the SQL standard string syntax.
+
+- -disable-triggers
+
+  Specifies a reserved port for function expansion. This parameter is not recommended.
+
+- -inserts
+
+  Dumps data by the **INSERT** statement (rather than **COPY**). This will cause a slow restoration. The restoration may fail if you rearrange the column order. The **-column-inserts** option is unaffected against column order changes, though even slower.
+
+- -no-security-labels
+
+  Specifies a reserved port for function expansion. This parameter is not recommended.
+
+- -no-tablespaces
+
+  Does not generate output statements to create tablespaces or select tablespaces for objects. All the objects will be created during the restoration process, no matter which tablespace is selected when using this option.
+
+- -no-unlogged-table-data
+
+  Specifies a reserved port for function expansion. This parameter is not recommended.
+
+- -include-alter-table
+
+  Export the deleted column information in the table.
+
+- -quote-all-identifiers
+
+  Forcibly quotes all identifiers. This parameter is useful when you dump a database for migration to a later version, in which additional keywords may be introduced.
+
+- -dont-overwrite-file
+
+  Does not overwrite the current file.
+
+- -use-set-session-authorization
+
+  Specifies that the standard SQL **SET SESSION AUTHORIZATION** command rather than **ALTER OWNER** is returned to ensure the object ownership. This makes dumping more standard. However, if a dump file contains objects that have historical problems, restoration may fail. A dump using **SET SESSION AUTHORIZATION** requires the system administrator rights, whereas **ALTER OWNER** requires lower permissions.
+
+- -with-encryption=AES128
+
+  Specifies that dumping data needs to be encrypted using AES128.
+
+- -with-key=KEY
+
+    AES128 key length rules are as follows:
+
+  - The key length is 8 ~ 16 characters.
+  - At least three of the four types of characters are included: uppercase letters (A-Z), lowercase letters (A-Z), numbers (0-9), non alphanumeric characters (limited to ~! @ #$% ^ & * () - = + \ | [] {};:, &lt;. &gt; /?).
+
+- -include-extension
+
+  If the -include-extension parameter is set, all CREATE EXTENSION statements will be backed up.
+
+- -include-templatedb
+
+  Includes template databases during the dump.
+
+- -binary-upgrade
+
+  Specifies a reserved port for function expansion. This parameter is not recommended.
+
+- -binary-upgrade-usermap="USER1=USER2"
+
+  Specifies a reserved port for function expansion. This parameter is not recommended.
+
+- -non-lock-table
+
+  This parameter is only used by the OM tool.
+
+- -tablespaces-postfix
+
+  Specifies a reserved port for function expansion. This parameter is not recommended.
+
+- -parallel-jobs
+
+  Specifies the number of concurrent backup processes. The value range is 1-1000.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - The **-g/-globals-only** and **-r/-roles-only** parameters do not coexist.
+> - The **-g/-globals-only** and **-t/-tablespaces-only** parameters do not coexist.
+> - The **-r/-roles-only** and **-t/-tablespaces-only** parameters do not coexist.
+> - The **-s/-schema-only** and **-a/-data-only** parameters do not coexist.
+> - The **-r/-roles-only** and **-a/-data-only** parameters do not coexist.
+> - The **-t/-tablespaces-only** and **-a/-data-only** parameters do not coexist.
+> - The **-g/-globals-only** and **-a/-data-only** parameters do not coexist.
+> - **-tablespaces-postfix** must be used in conjunction with **-binary-upgrade**.
+> - **-binary-upgrade-usermap** must be used in conjunction with **-binary-upgrade**.
+> - **-parallel-jobs** must be used in conjunction with **-f/-file**.
+
+Connection parameters:
+
+- -h, -host
+
+  Specifies the host name. If the value begins with a slash (/), it is used as the directory for the UNIX domain socket. The default value is taken from the PGHOST environment (if variable). Otherwise, a Unix domain socket connection is attempted.
+
+  This parameter is used only for defining names of the hosts outside MogDB. The names of the hosts inside MogDB must be 127.0.0.1.
+
+  Environment Variable: *PGHOST*
+
+- -l, -database
+
+  Specifies the name of the database connected to dump all objects and discover other databases to be dumped. If this parameter is not specified, the **postgres** database will be used. If the **postgres** database does not exist, **template1** will be used.
+
+- -p, -port
+
+  TCP port or the local Unix-domain socket file extension on which the server is listening for connections. The default value is the *PGPORT* environment variable.
+
+  If the thread pool function is enabled, you are advised to use **pooler port**, that is, the listening port number plus 1.
+
+  Environment variable: *PGPORT*
+
+- -U, -username
+
+  Specifies the user name to connect to.
+
+  Environment variable: *PGUSER*
+
+- -w, -no-password
+
+  Never issues a password prompt. The connection attempt fails if the host requires password verification and the password is not provided in other ways. This parameter is useful in batch jobs and scripts in which no user password is required.
+
+- -W, -password
+
+  Specifies the user password for connection. If the host uses the trust authentication policy, the administrator does not need to enter the **-W** option. If the **-W** option is not provided and you are not a system administrator, the Dump Restore tool will ask you to enter a password.
+
+- -role
+
+  Specifies a role name to be used for creating the dump. This option causes **gs_dumpall** to issue the **SET ROLE** statement after connecting to the database. It is useful when the authenticated user (specified by **-U**) lacks the permissions required by the **gs_dumpall**. It allows the user to switch to a role with the required permissions. Some installations have a policy against logging in directly as a system administrator. This option allows dumping data without violating the policy.
+
+- -rolepassword
+
+  Specifies the password of the specific role.
+
+## Notice
+
+**gs_dumpall** internally invokes **gs_dump**. For details about the diagnosis information, see [gs_dump](5-gs_dump).
+
+Once **gs_dumpall** is restored, run ANALYZE on each database so that the optimizer can provide useful statistics.
+
+**gs_dumpall** requires all needed tablespace directories to exit before the restoration. Otherwise, database creation will fail if the databases are in non-default locations.
+
+## Examples
+
+Use **gs_dumpall** to export all MogDB databases at a time.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> **gs_dumpall** supports only plain-text format export. Therefore, only **gsql** can be used to restore a file exported using **gs_dumpall**.
+
+```bash
+gs_dumpall -f backup/bkp2.sql -p 37300
+gs_dump[port='37300'][dbname='postgres'][2018-06-27 09:55:09]: The total objects number is 2371.
+gs_dump[port='37300'][dbname='postgres'][2018-06-27 09:55:35]: [100.00%] 2371 objects have been dumped.
+gs_dump[port='37300'][dbname='postgres'][2018-06-27 09:55:46]: dump database dbname='postgres' successfully
+gs_dump[port='37300'][dbname='postgres'][2018-06-27 09:55:46]: total time: 55567  ms
+gs_dumpall[port='37300'][2018-06-27 09:55:46]: dumpall operation successful
+gs_dumpall[port='37300'][2018-06-27 09:55:46]: total time: 56088  ms
+```
+
+## Helpful Links
+
+[gs_dump](5-gs_dump), [gs_restore](9-gs_restore)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/7-gs_guc.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/7-gs_guc.md
new file mode 100644
index 0000000000000000000000000000000000000000..0f3020416f82a9446688e13c3dfed7011909695c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/7-gs_guc.md
@@ -0,0 +1,375 @@
+---
+title: gs_guc
+summary: gs_guc
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_guc
+
+## Background
+
+Currently, the default values of parameters in MogDB configuration files (**postgresql.conf** and **pg_hba.conf**) are in single-node mode. You can set application parameters by using gs_guc.
+
+**gs_guc** is executed by OS user **omm**.
+
+- gs_guc-current.log
+
+  This file records the logs generated by gs_guc.
+
+  Default directory: $GAUSSLOG/bin/gs_guc
+
+- gs_guc-Year-Month-Day_HHMMSS.log
+
+  A backup file is generated based on the current time when the size of the gs_guc-current.log file reaches 16 MB.
+
+- server.key.cipher and server.key.rand
+
+  When you encrypt a user password using the gs_guc encrypt command and the -M option is set to server, the server.key.cipher and server.key.rand files are generated. server.key.cipher stores the encrypted password. server.key.rand stores the encryption factor.
+
+- client.key.cipher and client.key.rand
+
+  When you encrypt a user password using the gs_guc encrypt command and the -M option is set to client, the client.key.cipher and client.key.rand files are generated. client.key.cipher stores the encrypted password. client.key.rand stores the encryption factor.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** client.key.cipher and client.key.rand indicate the ciphertext file and encryption factor files generated when the -U option is not specified. When you specify the username using the -U option, a file whose name starts with the username is generated. Taking -U test as an example, the names of the files generated are test.key.cipher and test.key.rand.
+
+- datasource.key.cipher and datasource.key.rand
+
+  When you encrypt a user password using the gs_guc encrypt command and the -M option is set to source, the datasource.key.cipher and datasource.key.rand files are generated. datasource.key.cipher stores the encrypted password. datasource.key.rand stores the encryption factor.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > - datasource.key.cipher and datasource.key.rand are key files invoked during data source creation. gs_guc has the read permission when the files are generated. Before using the two files, place them in the *$GAUSSHOME***/bin** directory on each node and ensure that they are readable. **gs_ssh** helps you quickly place files in the specified directory of each node in the cluster.
+  > - You can also run the **gs_guc generate** command to generate the two files using either of the following methods and enter the password as prompted. Method 1: **gs_guc encrypt -M source -D ./** Method 2: **gs_guc generate -o datasource -D ./**
+
+## Syntax
+
+- Check parameters in the configuration file.
+
+  ```
+  gs_guc check [-N NODE-NAME] [-I INSTANCE-NAME | -D DATADIR] -c "parameter"
+  ```
+
+- Modify parameters in a configuration file.
+
+  ```
+  gs_guc set [-N NODE-NAME] [-I INSTANCE-NAME | -D DATADIR] -c "parameter = value"
+  ```
+
+- Reset parameters to their default values.
+
+  ```
+  gs_guc [ set | reload ] [-N NODE-NAME] [-I INSTANCE-NAME | -D DATADIR] -c "parameter"
+  ```
+
+- Modify parameters in the configuration file and send semaphore to the **postgresql.conf** configuration file.
+
+  ```
+  gs_guc reload [-N NODE-NAME] [-I INSTANCE-NAME | -D DATADIR] -c parameter=value
+  ```
+
+- Modify the client authentication policy. If **reload** is set, semaphores are sent to **pg_hba.conf** at the same time. That is, the configuration takes effect without restart.
+
+  ```
+  gs_guc {set | reload} -Z NODE-TYPE [-N NODE-NAME] {-I INSTANCE-NAME | -D DATADIR} -h "HOSTTYPE DATABASE USERNAME IPADDR IPMASK AUTHMEHOD authentication-options"
+  gs_guc {set | reload} -Z NODE-TYPE [-N NODE-NAME] {-I INSTANCE-NAME | -D DATADIR} -h "HOSTTYPE DATABASE USERNAME IPADDR-WITH-IPMASK AUTHMEHOD authentication-options"
+  gs_guc {set | reload} -Z NODE-TYPE [-N NODE-NAME] {-I INSTANCE-NAME | -D DATADIR} -h "HOSTTYPE DATABASE USERNAME HOSTNAME AUTHMEHOD authentication-options"
+  ```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - The **authentication-options** parameter following **AUTHMEHOD** is optional. **AUTHMEHOD** supports the following options:
+> - **trust**: No authentication is required. Remote hosts are not allowed to access the database in trust mode.
+> - **reject**: access denied.
+> - **md5**: MD5 authentication, which is not supported by default. (The MD5 encryption algorithm is not recommended because it has lower security and poses security risks.)
+> - **sha256**: SHA256 authentication (recommended).
+> - **sm3**：sm3 certification (national secret sm3).
+> - **cert**: Client certificate-based authentication.
+> - **gss**: Kerberos authentication, which is used only for authentication between internal nodes.
+> - The authentication policy in the **pg_hba.conf** file has a higher priority. When the gs_guc tool is used for configuration, new policies are inserted into the original authentication policy based on a certain rule. The field comparison sequence is as follows: IPADDR/HOSTNAME &gt; HOSTTYPE &gt; DATABASE &gt; USERNAME. That is, the IP addresses or host names are compared first. If the priorities cannot be distinguished, the host types are compared. For each configuration field, a stricter configuration parameter has a higher priority and a looser configuration parameter has a lower priority. The details are as follows:
+>   - **IPADDR**: An IP address of all zeros is not restricted and will be placed after the policy for specifying an IP address.
+>   - **DATABASE**: The value **all** indicates that the database is not restricted and is placed after the policy for specifying a database. The value **replication** indicates that the database is placed after other policies.
+>   - **USERNAME**: The value **all** indicates that the user is not restricted and is placed after the policy for specifying a user.
+>   - HOSTTYPE: local &gt; hostssl &gt; hostnossl &gt; host
+
+- Comment out the configured client authentication policy. If **reload** is set, semaphores are sent to **pg_hba.conf** at the same time. That is, the configuration takes effect without restart.
+
+  ```
+  gs_guc [ set | reload ] [-N NODE-NAME] [-I INSTANCE-NAME | -D DATADIR] -h "HOSTTYPE DATABASE USERNAME IPADDR-WITH-IPMASK AUTHMEHOD"
+  ```
+
+- Display help information.
+
+  ```
+  gs_guc -? | --help
+  ```
+
+- Display the version number.
+
+  ```
+  gs_guc -V | --version
+  ```
+
+- Use **gs_guc encrypt** to generate an encrypted password and encryption factor file.
+
+  ```
+  gs_guc encrypt [-M keymode] -K password [-U username] -D DATADIR
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > - **-K** indicates a user-specified password. **gs_guc** specifies the requirements of the password length (ranging from 8 to 16) and complexity. If the requirements are not meet, an error is reported. This password is used to ensure the security and uniqueness of the generated password file. You do not need to save or memorize the password.
+  > - **-M** indicates the encryption type. Its value can be **server**, **client** or **source**. The default value is server.
+
+- **gs_guc generate** generates the encrypted password and encryption factor file with a prefix.
+
+  ```
+  gs_guc generate [-o prefix] [-S cipherkey] -D DATADIR
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > - **-o** indicates a file name prefix, pertaining to output cipher and rand files. The default prefix is **obsserver**. The value can contain only digits, letters, and underscores (_).
+  > - **-S** indicates the password specified by the user. The password must meet the length (8 ≤ len ≤ 16) and complexity requirements. If the password does not meet the requirements, an error is reported. If the value is **default**, a randomly generated string will be used as the password, and the password length is 13 characters. If the **-S** parameter is not specified, the system prompts you to enter the password in interactive mode. To ensure system security, you are advised to enter the password in interactive mode.
+  > - Only the parameters are different when the **gs_guc encrypt** or **gs_guc generate** command is used to generate the encrypted password and encryption factor file. During the generation, a random number is used as the encryption key material and salt. Therefore, the file generated each time is different. The encryption password and encryption factor file generated each time must be used in pairs and cannot be changed or used alternately. The same encryption password and encryption factor file must be used for encryption and decryption.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - Parameter values set using gs_guc cannot contain the number sign (#). To set such values, you can use vi to manually modify the configuration file.
+> - If the environment variable PGDATA has been set, the -D parameter can be omitted. Otherwise, a parameter setting failure will be reported.
+> - Set the environment variable PGDATA as follows: Set */gaussdb/data*, and then execute export PGDATA to make the setting effective.
+> - authpolicy contains a series of authentication parameters: HOSTTYPE DATABASE USERNAME IPADDR IPMASK, HOSTTYPE DATABASE USERNAME IPADDR-WITH-IPMASK, or HOSTTYPE DATABASE USERNAME HOSTNAME.
+> - If you use -c "Parameter" to set a GUC parameter, this parameter will be reset to its default value. Note that the log_directory and audit_directory parameters will be reset to $GAUSSLOG/pg_audit/instance_name, instead of their default values. GUC parameters are dependent on each other. Therefore, exercise caution when using -c " Parameter".
+> - When setting the **-c** parameter, the double quotation marks can be omitted.
+> - If the value contains special characters, such as $, escape the character first.
+> - If a configuration parameter occurs in multiple rows of a configuration file and two or more rows take effect at the same time (which means that the configuration parameter is not commented out using "#"), only the last configuration parameter is set and the others are ignored.
+> - If modification validation is delayed after the parameters in the cluster node configuration file **postgresql.conf** are set or modified in reload mode, the parameter settings for instances in the cluster may be inconsistent for a short period of time.
+
+## Command Reference
+
+- set
+
+  Modifies only parameters in the configuration file.
+
+- check
+
+  Checks only the parameters in the configuration file.
+
+- reload
+
+  Modifies parameters in the configuration file and sends semaphore to the database process for reloading the configuration file.
+
+- encrypt/generate
+
+  Generates the encrypted password file.
+
+- -N
+
+  Specifies the name of the host to be set.
+
+  Value range: name of an existing host
+
+  When this parameter is set to **ALL**, all the hosts in the cluster are to be set.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** It depends on the static file and is valid only when the OM is installed. The compilation and installation are invalid because there is no static file.
+
+- -I INSTANCE-NAME
+
+  Specifies the name of the instance to be set.
+
+  Value range: name of an existing instance
+
+  When this parameter is set to ALL, all the instances in the host are to be set.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** It depends on the static file and is valid only when the OM is installed. The compilation and installation are invalid because there is no static file.
+
+- -D
+
+Specifies the cluster instance path of the commands to be run. When the encrypt command is used, this parameter indicates the path for storing the generated password file.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - -D cannot be used together with -I.
+
+- -c parameter=value
+
+  Specifies the name and value of the cluster configuration parameter to be set.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > - If the parameter is a string variable, use **-c** parameter="'**value**'" or **-c**" *parameter* = '**value'"**.
+  > - When gs_guc set or reload is set to log_directory, the default value is restored and set to a specific data directory.
+  > - When **gs_guc reload** is used to set parameters and the **-N** parameter is set to the primary node, the parameter values of both the primary and standby nodes will be modified. If the **-N** parameter is set to the standby node, the parameter values of only the standby node will be modified.
+  > - When **gs_guc reload** is used to set parameters and the **-N** parameter is not set, the parameter values of both the primary and standby nodes will be modified if you run the command on the primary node. If the **-N** parameter is not set and you run the command on the standby node, the parameter values of only the standby node will be modified.
+
+  Value range: all the parameters in the postgresql.conf file
+
+- -lcname=LCNAME
+
+  Specifies the name of the logical database to be set.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > - This parameter must be used together with **-Z datanode**. That is, gs_guc can be used only for logical database instances of DNs.
+  > - The parameters that can be operated on a logical database are different from those on a complete database. For details, see **$GAUSSHOME/bin/cluster_guc.conf**.
+
+  Value range: name of an existing logical database.
+
+- -c parameter
+
+  Specifies the name of the parameter to be checked. When you perform the set or reload operation, the parameter value cannot be null. Otherwise, the default value of the database parameter is not restored.
+
+- -h host-auth-policy
+
+Specifies the client authentication policy added to the pg_hba.conf configuration file.
+
+Value range:
+
+- HOSTTYPE DATABASE USERNAME IPADDR IPMASK [authmehod-options]
+- HOSTTYPE DATABASE USERNAME IPADDR-WITH-IPMASK [authmehod-options ]
+- HOSTTYPE DATABASE USERNAME HOSTNAME [authmehod-options ]
+
+**HOSTTYPE** is a mandatory parameter. Value range:
+
+- local
+- host
+- hostssl
+- hostnossl
+
+local is a Unix domain socket. host is a common or SSL-encrypted TCP/IP socket. hostssl is an SSL-encrypted TCP/IP socket. hostnossl is a TCP/IP-only socket.
+
+authmehod-options is an optional parameter. Value range:
+
+- trust
+- reject
+- md5
+- sha256
+- sm3
+- cert
+- gss
+
+For details about the parameters, see their description in the pg_hba.conf configuration file.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** If **-h** is specified, the system attempts to modify the **pg_hba** file of all nodes by default. If compilation and installation are performed without static files, the **pg_hba** file of the current node can be successfully modified, but a message is displayed indicating that the static file does not exist.
+
+- -?, -help
+
+  Display help information.
+
+- -V, -version
+
+  Display version information.
+
+- -M, -keymode=MODE
+
+  Specifies that the password is invoked to create which object. Its value can be server, client or source.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** Using the SSL function involves the encrypted passwords of the server certificates and private key files as well as those of the client certificates and private key files. When these passwords are stored in encrypted mode, this parameter must be specified. Otherwise, a server password file will be generated.
+
+  Value range:
+
+  - server (default value)
+  - client
+  - source
+
+- -K PASSWORD
+
+  Specifies the plaintext password to be encrypted.
+
+  Value range: a character string. The value must meet the password complexity requirements.
+
+- -U, -keyuser=USER
+
+  Specifies the user to be encrypted. The user belongs to the OS user.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** MogDB can configure different SSL licenses and private files for each user. When this option is specified, user-specific password files can be generated.
+
+- -S CIPHERKEY
+
+  Specifies the string to be encrypted.
+
+  Value range: a string.
+
+- -o PREFIX
+
+  Specifies the file name prefix for output cipher and rand files of the OBS type. The default prefix is obsserver.
+
+  Value range: a string containing only digits, letters, and underscores (_).
+
+- -Z NODE-TYPE
+
+  Specifies the node type of a database instance. The default value is datanode. NODE-TYPE is used to identify a configuration file.
+
+  Value range: datanode.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** Database instance node types include coordinator, datanode, cmserver, cmagent, and gtm. The value of MogDB can only be datanode. If NODE-TYPE is set to datanode, the configuration file in the data directory of the corresponding database is postgresql.conf.
+
+## Example
+
+Example 1: Change the maximum number of connections allowed by a database to 800. The database must be restarted to make the change take effect.
+
+```
+gs_guc set -D /gaussdb/data/dbnode -c "max_connections = 800" -N plat1
+
+Total instances: 1. Failed instances: 0.
+Success to perform gs_guc!
+```
+
+Example 2: Change the maximum number of connections allowed by a database to the default value. The database must be restarted to make the change take effect.
+
+```
+gs_guc set -D /gaussdb/data/dbnode -c "max_connections" -N plat1
+
+Total instances: 1. Failed instances: 0.
+Success to perform gs_guc!
+```
+
+Example 3: Set a client authentication policy.
+
+```
+gs_guc set -N all -I all -h "host replication testuser 10.252.95.191/32 sha256"
+
+Total instances: 2. Failed instances: 0.
+Success to perform gs_guc!
+```
+
+Example 4: Comment out a configured client authentication policy.
+
+```
+gs_guc set -N all -I all -h "host replication testuser 10.252.95.191/32"
+
+Total instances: 2. Failed instances: 0.
+Success to perform gs_guc!
+```
+
+Example 5: Encrypt a plaintext user password stored on a server to avoid password leakage.
+
+```
+gs_guc encrypt -K Gauss@123 -D /data/xzg/wisequery/gaussdb
+gs_guc encrypt -K ***
+```
+
+Example 6: Check the parameter configurations of each instance in MogDB.
+
+```
+gs_guc check -D /gaussdb/data/dbnode -c "max_connections" -N plat1
+
+Total GUC values: 1. Failed GUC values: 0.
+The value of parameter max_connections is same on all instances.
+    max_connections=800
+```
+
+Example 7: Modify **archive_command** to ensure the validity of the archiving path. The database must be restarted to make the change take effect. This method is recomended.
+
+```
+gs_guc set -N all -D /data/datanode  -c "archive_command= 'cp %p /data/datanode/pg_xlog/archive_status/%f'"
+Total instances: 3. Failed instances: 0.
+Success to perform gs_guc!
+```
+
+Example 8: Use an entered plaintext password to customize and generate the **test.key.cipher** and **test.key.rand** files.
+
+```
+gs_guc generate -S Mppdb@123 -D data/xzg/wisequery/gaussdb -o test
+gs_guc encrypt -S ***
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/7.1-gs_encrypt.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/7.1-gs_encrypt.md
new file mode 100644
index 0000000000000000000000000000000000000000..78afb73145dfe1ae6e260984f46939086aab18f3
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/7.1-gs_encrypt.md
@@ -0,0 +1,135 @@
+---
+title: gs_encrypt
+summary: gs_encrypt
+author: Zhang Cuiping
+date: 2021-11-17
+---
+
+# gs_encrypt
+
+## Background
+
+**gs_encrypt** provided by MogDB is used to encrypt the entered plaintext strings.
+
+## Syntax
+
+```
+gs_encrypt [OPTION]... PLAINTEXT
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - *PLAINTEXT* does not follow a short or long option.
+> - *PLAINTEXT* indicates the plaintext string to be encrypted.
+
+## Parameter Description
+
+- -?, -help
+
+  Displays help information.
+
+- -V, -version
+
+  Displays version information.
+
+- -k *PASSWORD*, -key=*PASSWORD*
+
+  Password entered by a user. It is used to derive the key for encryption. The password must contain 8 to 16 characters, including at least three types of the following: uppercase letters, lowercase letters, digits, and special characters.
+
+- -v *VectorValue*, -vector=*VectorValue*
+
+  Salt value entered by a user. It is used to scramble passwords during one-way password hash calculation. The string must contain 16 characters.
+
+- -f *FilePrefix*, -file-prefix=*FilePrefix*
+
+  Prefix of the cipher and rand files used for encryption. The cipher and rand files must be stored in **$GAUSSHOME/bin**.
+
+- -B *Value*, -key-base64=*Value*
+
+  Base64 plaintext key used for encryption.
+
+- -D *Value*, -vector-base64=*Value*
+
+  Base64 random string used for encryption. The length of the string before base64 encoding must be 16 characters.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** For security purposes, you are advised to set **HISTCONTROL** to **ignorespace** before using the gs_encrypt tool to forcibly not record sensitive historical commands and add a space before the **gs_encrypt** command.
+
+## Examples
+
+Example 1: Encrypt a plaintext string by using a plaintext key and a plaintext vector. The IV value used for each encryption is randomly generated. Therefore, the ciphertext strings are different even though the same key, vector, and plaintext character string are used for encryption. The maximum length of a plaintext character string that can be encrypted at a time is 335 bytes.
+
+```
+gs_encrypt -k password@123 -v 1234567890123456 test_encrypt
+```
+
+Command output:
+
+```
+G0R7Y2oROfuiEjWtUBx9+eHP3I21A1wMOJ2onVQIiAsxMjM0NTY3ODkwMTIzNDU2
+```
+
+Example 2: Encrypt a plaintext string by using cipher and rand files (invoke the files by entering their prefixes).
+
+1. Run the following commands to generate the cipher and rand files:
+
+   ```
+   gs_guc generate -S Mppdb@123 -D $GAUSSHOME/bin -o test
+   ```
+
+   Command output:
+
+   ```
+   gs_guc encrypt -S ***
+   ```
+
+2. Perform the encryption operation.
+
+   ```
+   gs_encrypt -f test test_encrypt
+   ```
+
+   Command output:
+
+   ```
+   tSWpR8aFyF4GHVIVO7QNXhEMNlTcqRMrk172nAf2hLgSQwhcFWyP7X0QVS0SONon
+   ```
+
+Example 3: Encrypt a plaintext string by using a Base64 key and a Base64 vector.
+
+1. Enter the key encrypted using Base64.
+
+   ```
+   python
+   >>> import base64
+   >>> print base64.b64encode("XXXXXXXXX");
+   ```
+
+   Command output:
+
+   ```
+   R2F1c3NAMTIz
+   ```
+
+2. Enter the vector ciphertext encrypted using Base64.
+
+   ```
+   >>> print base64.b64encode("1234567890abcdef");
+   ```
+
+   Command output:
+
+   ```
+   MTIzNDU2Nzg5MGFiY2RlZg==
+   ```
+
+3. Perform the encryption operation.
+
+   ```
+   gs_encrypt -B R2F1c3NAMTIz -D MTIzNDU2Nzg5MGFiY2RlZg==  test_encrypt
+   ```
+
+   Command output:
+
+   ```
+   V7mpnsfIHTjVTYGw1YHI0c6aY0N4J5L7BtU4CqDoeIkxMjM0NTY3ODkwYWJjZGVm
+   ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/8-gs_om.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/8-gs_om.md
new file mode 100644
index 0000000000000000000000000000000000000000..d6c079ea8f90b0f58527be7a4780721c83df21d7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/8-gs_om.md
@@ -0,0 +1,402 @@
+---
+title: gs_om
+summary: gs_om
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_om
+
+## Background
+
+**gs_om**, provided by MogDB, is used to maintain MogDB. You can use it to start and stop MogDB, query the MogDB status, query static configurations, query MogDB status details, generate static configuration file and dynamic configuration file, replace SSL certificates, query help information, and query the version number.
+
+## Prerequisites
+
+Log in to the OS as the OS user **omm** to run the **gs_om** command.
+
+## Syntax
+
+- Start MogDB.
+
+  ```
+  gs_om -t start [-h HOSTNAME] [-D dataDir] [--time-out=SECS] [--security-mode=MODE] [-l LOGFILE]
+  ```
+
+- Stop MogDB.
+
+  ```
+  gs_om -t stop [-h HOSTNAME] [-D dataDir]  [--time-out=SECS] [-m MODE] [-l LOGFILE]
+  ```
+
+- Restart MogDB.
+
+  ```
+  gs_om -t restart [-h HOSTNAME] [-D dataDir] [--time-out=SECS] [--security-mode=MODE] [-l LOGFILE] [-m MODE]
+  ```
+
+- Query the MogDB status.
+
+  ```
+  gs_om -t status [-h HOSTNAME] [-o OUTPUT] [--detail] [--all] [-l LOGFILE]
+  ```
+
+- Generate a static configuration file.
+
+  ```
+  gs_om -t generateconf -X XMLFILE [--distribute] [-l LOGFILE]
+  ```
+
+- Generate a dynamic configuration file. Perform this operation after the failover or switchover from the standby node to the primary node.
+
+  ```
+  gs_om -t refreshconf
+  ```
+
+- Display the static configurations.
+
+  ```
+  gs_om -t view [-o OUTPUT]
+  ```
+
+- Query the MogDB status details.
+
+  ```
+  gs_om -t query [-o OUTPUT]
+  ```
+
+- Replace SSL certificates.
+
+  ```
+  gs_om -t cert --cert-file=CERTFILE [-l LOGFILE]
+  gs_om -t cert --rollback
+  ```
+
+- Enable or disable the Kerberos authentication in the cluster.
+
+  ```
+  gs_om -t kerberos -m [install|uninstall] -U USER [-l LOGFILE] [--krb-client|--krb-server]
+  ```
+
+- Display help information.
+
+  ```
+  gs_om -? | --help
+  ```
+
+- Display version information.
+
+  ```
+  gs_om -V | --version
+  ```
+
+## Parameter Description
+
+The **gs_om** tool can use the following types of parameters:
+
+- Common parameters
+
+  - -t
+
+    Specifies the command types of **gs_om**.
+
+    Value range: **start**, **stop**, **status**, **generateconf**, **cert**, **view**, **query**, **refreshconf**, and **kerberos**
+
+  - -l
+
+    Specifies a log file and its storage path.
+
+    Default value: **$GAUSSLOG/om/gs_om**-*YYYY*-*MM*-*DD*_*hhmmss***.log** (default value for **virtualip**: **/tmp/gs_virtualip/gs_om**-*YYYY*-*MM*-*DD*_*hhmmss***.log**)
+
+  - -?, -help
+
+    Displays help information.
+
+  - -V, -version
+
+    Displays version information.
+
+  - MogDB startup parameters
+
+  - -h
+
+    Specifies the name of the server to be started. Only one server can be started at a time.
+
+    Value range: a server name
+
+    If no server name is specified, MogDB is started.
+
+  - -D
+
+    Specifies the DN path.
+
+    Value range: a DN path
+
+    If the DN path is not specified, the DN path in the static file is used.
+
+  - -time-out=SECS
+
+    Specifies the timeout threshold. **gs_om** exits when times out. Unit: s
+
+    Value range: a positive integer. The recommended value is **300**.
+
+    Default value: **300**
+
+  - -security-mode
+
+    Specifies whether to start the database in secure mode.
+
+    Value range: **on**: Start the database in secure mode. **off**: Not start the database in secure mode.
+
+    The secure mode is disabled by default.
+
+- MogDB stop parameters
+
+  - -h
+
+    Specifies the name of the server where the instance to be stopped is located. Only one server can be stopped at a time.
+
+    Value range: the name of the server where the instance is located
+
+    If no server name is specified, MogDB is stopped.
+
+  - -m, -mode=MODE
+
+    Sets the stop mode.
+
+    Value range: the following two stop modes are supported:
+
+    - **fast**: The data of the primary and standby instance relationship is ensured to be consistent.
+    - **immediate**: The data of the primary and standby instance relationship is not ensured to be consistent.
+
+    Default value: **fast**
+
+- -time-out=SECS
+
+  Specifies the timeout threshold. **gs_om** exits when times out. Unit: s
+
+  Value range: a positive integer. The recommended value is **300**.
+
+  Default value: **300**
+
+- Parameters for checking status
+
+  [Table 1](#status) describes parameters in the query result.
+
+  - -h
+
+    Specifies the name of the server to be queried.
+
+    Value range: a server name
+
+    If no server name is specified, MogDB is queried.
+
+  - -az
+
+    Specify the name of the AZ to be queried, such as -az=AZ1.
+
+    Value range: AZ name. If AZ name is not specified, it means to query all AZs.
+
+  - -o
+
+    Outputs status information to the specified output file.
+
+    If the parameter is not output to the specified file, it is displayed on the screen.
+
+  - -detail
+
+    Displays detailed information. If the parameter is not specified, only a prompt is displayed indicating whether the server is normal.
+
+    -all
+
+    Displays information about all MogDB nodes.
+
+- Parameters for generating the configuration file:
+
+  - -X
+
+    Selects the path of the MogDB configuration file.
+
+    Value range: path of the **clusterconfig.xml** file
+
+  - -distribute
+
+    Publishes the static configuration file to the installation directory of the MogDB instance.
+
+- Parameters for enabling or disabling the Kerberos authentication in the cluster
+
+  - -U
+
+    Specifies a database cluster user.
+
+    Value range: a database cluster deployment user
+
+  - -m
+
+    Specifies the operations to be performed.
+
+    Value range:
+
+    **install**: Enables the Kerberos authentication in a cluster is enabled.
+
+    **uninstall**: Disables the Kerberos authentication in a cluster is disabled.
+
+  - **-krb-server**: Installs the Kerberos server authentication.
+
+  - **-krb-client**: Installs the Kerberos client authentication.
+
+    Note: You need to use **-krb-server** to install the server authentication first. These two parameters are not required during the uninstallation because the server and client are uninstalled at the same time.
+
+- Parameters for replacing SSL certificates
+
+  - -cert-file
+
+    Specifies the path of the local SSL certificate .zip package.
+
+  - -rollback
+
+    Rolls back the certificates to the last backup.
+
+  - -L
+
+    When setting this parameter, only the current node is performed.
+
+**Table 1** Status description <a id="status"></a>
+
+| Field          | Field Description                                            | Field Value                                                  |
+| :------------- | :----------------------------------------------------------- | :----------------------------------------------------------- |
+| cluster_state  | MogDB status, which indicates whether MogDB is running properly. | - **Normal**: MogDB is available and the data has redundancy backup. All the processes are running and the primary/standby relationship is normal.<br />- **Unavailable**: MogDB is unavailable.<br />- **Degraded**: MogDB is available but the data does not have redundancy backup. |
+| redistributing | Data redistribution status.                                  | - **Yes**: MogDB is in data redistribution status.<br />- **No**: MogDB is not in data redistribution status. |
+| balanced       | Load balancing status, which indicates whether a primary/standby switchover has occurred in the MogDB instance and made the host load unbalanced. | - **Yes**: The host loading is balanced in MogDB.<br />- **No**: The host loading is not balanced in MogDB. |
+| node           | Host name.                                                   | Specifies the name of a host where an instance is located. If multiple AZs exist, the AZ IDs will be displayed. |
+| node_ip        | Host IP address.                                             | Specifies the IP address of a host where an instance is located. |
+| instance       | Instance ID.                                                 | Specifies the instance ID.                                   |
+| state          | Instance status.                                             | - **P**: The initial role of the node is **Primary**. After the database is installed, the role does not change and is read from the system static file.<br />- **S**: The initial role of the node is **Standby**. After the database is installed, the role does not change and is read from the system static file.<br />- **C**: The initial role of the node is **Cascade Standby**. After the database is installed, the role does not change and is read from the system static file.<br />- **Primary**: The instance is a primary instance.<br />- **Standby**: The instance is a standby instance.<br />- **Cascade Standby**: The instance is a cascaded standby instance.<br />- **Secondary**: The instance is a secondary instance.<br />- **Pending**: The instance is in arbitration.<br />- **Unknown**: The instance status is unknown.<br />- **Down**: The instance is down. |
+
+**Table 2** Feature IDs
+
+| Feature Name                                               | ID   | MogDB Product                 |
+| :--------------------------------------------------------- | :--- | :---------------------------- |
+| Multi-value column                                         | 0    | Basic edition                 |
+| JSON                                                       | 1    | License control not supported |
+| XML                                                        | 2    | Not supported                 |
+| Data storage format ORC                                    | 3    | Basic edition                 |
+| One primary and multiple readable standbys on single-node  | 5    | Invalid                       |
+| Multidimensional collision and analysis (GPU acceleration) | 7    | Advanced feature              |
+| Full-text indexing                                         | 8    | Basic edition                 |
+| EXTENSION_CONNECTOR                                        | 9    | Basic edition                 |
+| EXPRESS_CLUSTER                                            | 12   | Advanced edition              |
+| Cross-DC collaboration                                     | 13   | Advanced edition              |
+| Figure                                                     | 14   | Not supported                 |
+| Time sequence                                              | 15   | Not supported                 |
+| PostGIS interconnection                                    | 16   | Basic edition                 |
+| HA in MogDB (one primary and multiple standbys)            | 17   | Invalid                       |
+| Row-level permission control                               | 18   | Advanced edition              |
+| Transparent encryption                                     | 19   | Advanced edition              |
+| Private table                                              | 20   | Advanced edition              |
+
+## Example
+
+- Start MogDB.
+
+  ```
+  gs_om -t start
+  Starting cluster.
+  ======================================================================
+  .
+  ======================================================================
+
+  Successfully started .
+  ```
+
+- Stop MogDB.
+
+  ```
+  gs_om -t stop
+  Stopping cluster.
+  =========================================
+  Successfully stopped cluster.
+  =========================================
+  End stop cluster.
+  ```
+
+- View MogDB status details, including instance status.
+
+  ```
+  gs_om -t status --detail
+
+  [   Cluster State   ]
+
+  cluster_state   : Normal
+  redistributing  : No
+  current_az      : AZ_ALL
+
+  [  Datanode State   ]
+
+      node             node_ip         port      instance                            state
+  --------------------------------------------------------------------------------------------------
+  1  pekpopgsci00235  10.244.62.204    5432      6001 /home/wuqw/cluster/dn1/   P Primary Normal
+  2  pekpopgsci00238  10.244.61.81     5432      6002 /home/wuqw/cluster/dn1/   S Standby Normal
+  ```
+
+- Run the following commands on MogDB to generate the configuration file:
+
+  ```
+  gs_om -t generateconf -X  /opt/software/mogdb/clusterconfig.xml  --distribute
+  Generating static configuration files for all nodes.
+  Creating temp directory to store static configuration files.
+  Successfully created the temp directory.
+  Generating static configuration files.
+  Successfully generated static configuration files.
+  Static configuration files for all nodes are saved in /opt/mogdb/Bigdata/gaussdb/wisequery/script/static_config_files.
+  Distributing static configuration files to all nodes.
+  Successfully distributed static configuration files.
+  ```
+
+  Open the generated configuration file directory. You can see three new files.
+
+  ```
+  cd /opt/mogdb/Bigdata/gaussdb/wisequery/script/static_config_files
+  ll
+  total 456
+  -rwxr-xr-x 1 omm dbgrp 155648 2016-07-13 15:51 cluster_static_config_plat1
+  -rwxr-xr-x 1 omm dbgrp 155648 2016-07-13 15:51 cluster_static_config_plat2
+  -rwxr-xr-x 1 omm dbgrp 155648 2016-07-13 15:51 cluster_static_config_plat3
+  ```
+
+- Roll back SSL certificates.
+
+  ```
+  gs_om -t cert --rollback
+  [plat1] SSL cert files rollback successfully.
+  [plat2] SSL cert files rollback successfully.
+  [plat3] SSL cert files rollback successfully.
+  ```
+
+- Register a license.
+
+  ```
+  gs_om -t license -m register -f MTgsMTkK
+  Preparing for the program initialization.
+  Lock the OPS operation of OM components.
+  Check and make sure the consistency of the license file.
+  Backup the license file on all of the cluster hosts.
+  Encrypt the product feature information and generate the license file.
+  Send message to the database node instances to reload the license file.
+  Remove the backup license file on all of the cluster hosts.
+  License register successfully.
+  ```
+
+- Deregister a license.
+
+  ```
+  gs_om -t license -m unregister -f MTgsMTkK
+  Preparing for the program initialization.
+  Lock the OPS operation of OM components.
+  Check and make sure the consistency of the license file.
+  Backup the license file on all of the cluster hosts.
+  Encrypt the product feature information and generate the license file.
+  Send message to the database node instances to reload the license file.
+  Remove the backup license file on all of the cluster hosts.
+  License unregister successfully.
+  ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/8.1-gs_plan_simulator.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/8.1-gs_plan_simulator.md
new file mode 100644
index 0000000000000000000000000000000000000000..09a7ffe2a408105f0dcf0d350e346a793e91aceb
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/8.1-gs_plan_simulator.md
@@ -0,0 +1,115 @@
+---
+title: gs_plan_simulator
+summary: gs_plan_simulator
+author: Zhang Cuiping
+date: 2021-11-17
+---
+
+# gs_plan_simulator
+
+## Background
+
+Maintenance personnel are not allowed to locate and analyze problems in the production environment of some users. Therefore, the only method for this scenario is to collect various data in the production environment and analyze and locate problems based on the collected data. gs_plan_simulator collects data related to execution plans and reproduces execution plans in other environments to locate problems related to execution plans.
+
+## Prerequisites
+
+- The user database is running properly.
+- The user can connect to the database and execute functions properly.
+- The OS environment used for fault reproduction must be the same as the production environment.
+- The MogDB installation package used for fault reproduction must be the same as that used in the production environment.
+
+## Precautions
+
+- The data collection function has been integrated into the gs_collector tool. You need to use the gs_collector tool to collect related data and then use the gs_plan_simulator tool to reproduce the execution plan.
+- When gs_collector is used to collect data, data related to the execution plan is not collected by default because it may take a long time to collect such data. To collect execution plan data, you need to modify the configuration file. For details, see the procedure.
+- Configure *GAUSSHOME* and *LD_LIBRARY_PATH* in the reproduction environment.
+- Do not use this tool if the cluster status or scaling status affects the data related to the execution plan.
+
+## Procedure
+
+1. Use gs_collector to collect data. Before collecting execution plan data, you need to write a configuration file, for example, **plan.json**. The content of the configuration file is recommended as follows:
+
+   ```
+   {
+   "Collect":
+   [
+   {"TypeName": "Plan", "Content": "*", "Interval":"0", "Count":"1"}
+   ]
+   }
+   ```
+
+   **Content** is set to ***** to collect data of all databases. You can also specify a database to collect data, for example,**test1,test2**.
+
+   The following is an example of the collection command:
+
+   ```
+   gs_collector --begin-time="20191219 15:00" --end-time="20191219 15:15" -C ../plan.json -l plan.log -o ./
+   ```
+
+   For details, see section [gs_collector](4-gs_collector).
+
+2. Copy the data folder to the reproduction environment.
+
+   After the data collection is successful, the collected data is stored in the specified compressed package. Decompress the package to obtain the compressed package of each node. Decompress any compressed package. The target data is stored in the **planSimulatorfiles** folder. Go to the **planSimulatorfiles** folder and view the folder named after the database. Copy the **planSimulatorfiles** folder to the reproduction environment.
+
+3. Configure the reproduction environment.
+
+   1. Create a directory for reproducing the execution plan as a common user. For example, the **plan** folder.
+   2. Decompress the GaussDB installation package in the directory, and then decompress the BIN file in the installation package.
+   3. Set *GAUSSHOME* to the path of the **plan** folder and **LD_LIBRARY_PATH** to the path of the *plan/lib* folder.
+
+4. Use gs_plan_simulator to reproduce the execution plan.
+
+   Run the following command in the reproduction environment:
+
+   ```
+   $GAUSSHOME/bin/gs_plan_simulator.sh -m restore -p 39000 -A planSimulatorfiles/
+   ```
+
+   This command creates a database in the reproduction environment and the CN port number is 39000. In addition, a message is displayed indicating how to connect to the database. You can run **EXPLAIN** *SQL statement* to locate the fault. For details about the command parameters, see parameter description.
+
+## Syntax
+
+- Reproduce the database environment.
+
+  ```
+  $GAUSSHOME/bin/gs_plan_simulator.sh -m OPTION -p PORT -A DATADIR
+  ```
+
+- Stop the database.
+
+  ```
+  $GAUSSHOME/bin/gs_plan_simulator.sh -m off
+  ```
+
+- Start the database.
+
+  ```
+  $GAUSSHOME/bin/gs_plan_simulator.sh -m start
+  ```
+
+- Display the help information.
+
+  ```
+  $GAUSSHOME/bin/gs_plan_simulator.sh --help
+  ```
+
+## Parameter Description
+
+- -m
+
+  Specifies the operation to be performed by the tool.
+
+  Value range:
+
+  - **restore**: uses the collected database information to reproduce the database environment and create a database.
+  - **off**: stops the database that is reproduced by the tool.
+  - **start**: starts the database that is reproduced by the tool.
+
+- -p
+
+  Creates a CN port for the database.
+
+- -A
+
+  Specifies the data folder copied from the user environment.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/9-gs_restore.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/9-gs_restore.md
new file mode 100644
index 0000000000000000000000000000000000000000..93a4e0d9bd29f9f526920c7975ae60cf69b0707f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/9-gs_restore.md
@@ -0,0 +1,383 @@
+---
+title: gs_restore
+summary: gs_restore
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_restore
+
+## Background
+
+**gs_restore**, provided by MogDB, is used to import data that was exported using **gs_dump**. It can also be used to import files exported by **gs_dump**.
+
+**gs_restore** is executed by OS user **omm**.
+
+It has the following functions:
+
+- Importing data to the database
+
+  If a database is specified, data is imported to the database. For parallel import, the password for connecting to the database is required. During data import, the generated columns are automatically updated and saved as common columns.
+
+- Importing data to the script file
+
+  If the database storing imported data is not specified, a script containing the SQL statement to recreate the database is created and written to a file or standard output. This script output is equivalent to the plain text output format of **gs_dump**.
+
+## Command Format
+
+```
+gs_restore [OPTION]... FILE
+```
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+
+- **FILE** does not have a short or long parameter. It is used to specify the location for the archive files.
+- The **dbname** or **-l** parameter is required as prerequisites. Users cannot enter **dbname** and **-l** parameters at the same time.
+- **gs_restore** incrementally imports data by default. To prevent data exceptions caused by multiple import operations, you are advised to use the **-c** parameter during the import. Before recreating database objects, delete the database objects that already exist in the database to be restored.
+- There is no option to control log printing. To hide logs, redirect the logs to the log file. If a large amount of table data needs to be restored, the table data will be restored in batches. Therefore, the log indicating that the table data has been imported is generated for multiple times.
+
+## Parameter Description
+
+Common parameters
+
+- -d, -dbname=NAME
+
+  Connects to the **dbname** database and imports data to the database.
+
+- -f, -file=FILENAME
+
+  Specifies the output file for the generated script, or uses the output file in the list specified using **-l**.
+
+  The default is the standard output.
+
+  ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+
+  **-f** cannot be used in conjunction with **-d**.
+
+- -F, -format=c|d|t
+
+    Specifies the format of the archive. The format does not need to be specified because the *gs_restore* determines the format automatically.
+
+    Value range:
+
+  - **c/custom**: The archive form is the customized format in **gs_dump**.
+  - **d/directory**: The archive form is a directory archive format.
+  - **t/tar**: The archive form is a .tar archive format.
+
+- -l, -list
+
+  Lists the forms of the archive. The operation output can be used for the input of the **-L** parameter. If filtering parameters, such as **-n** or **-t**, are used together with **-l**, they will restrict the listed items.
+
+- -v, -verbose
+
+  Specifies the verbose mode.
+
+- -V, -version
+
+  Prints the **gs_restore** version and exits.
+
+- -?, -help
+
+  Displays help information about the parameters of **gs_restore** and exits.
+
+Parameters for importing data
+
+- -a, -data-only
+
+  Imports only the data, not the schema (data definition). **gs_restore** incrementally imports data.
+
+- -c, -clean
+
+  Cleans (deletes) existing database objects in the database to be restored before recreating them.
+
+- -C, -create
+
+  Before importing to the database, CREATE DATABASE will be used to create the database (after specifying this option, the database specified by **-d** is only used to execute the CREATE DATABASE command, and all data will be imported into the created database).
+
+- -e, -exit-on-error
+
+  Exits if an error occurs when you send the SQL statement to the database. If you do not exit, the commands will still be sent and error information will be displayed when the import ends.
+
+- -I, -index=NAME
+
+  Imports only the definition of the specified index. Multiple indexes can be imported. Enter **-I** _index_ multiple times to import multiple indexes.
+
+  For example:
+
+  ```
+  gs_restore -h host_name -p port_number -d postgres -I Index1 -I Index2 backup/MPPDB_backup.tar
+  ```
+
+  In this example, *Index1* and *Index2* will be imported.
+
+- -j, -jobs=NUM
+
+  Specifies the number of concurrent, the most time-consuming jobs of **gs_restore** (such as loading data, creating indexes, or creating constraints). This parameter can greatly reduce the time to import a large database to a server running on a multiprocessor machine.
+
+  Each job is one process or one thread, depending on the OS; and uses a separate connection to the server.
+
+  The optimal value for this option depends on the server hardware setting, the client, the network, the number of CPU cores, and disk settings. It is recommended that the parameter be set to the number of CPU cores on the server. In addition, a larger value can also lead to faster import in many cases. However, an overly large value will lead to decreased performance because of thrashing.
+
+  This parameter supports custom-format archives only. The input file must be a regular file (not the pipe file). This parameter can be ignored when you select the script method rather than connect to a database server. In addition, multiple jobs cannot be used in conjunction with the **-single-transaction** parameter.
+
+- -L, -use-list=FILENAME
+
+  Imports only archive elements that are listed in **list-file** and imports them in the order that they appear in the file. If filtering parameters, such as **-n** or **-t**, are used in conjunction with **-L**, they will further limit the items to be imported.
+
+  **list-file** is normally created by editing the output of a previous **-l** parameter. File lines can be moved or removed, and can also be commented out by placing a semicolon (;) at the beginning of the row.
+
+- -n, -schema=NAME
+
+  Restores only objects that are listed in schemas.
+
+  This parameter can be used in conjunction with the **-t** parameter to import a specific table.
+
+  Entering **-n** *schemaname* multiple times can import multiple schemas.
+
+  For example:
+
+  ```
+  gs_restore -h host_name -p port_number -d postgres -n sch1 -n sch2 backup/MPPDB_backup.tar
+  ```
+
+  In this example, **sch1** and **sch2** will be imported.
+
+- -O, -no-owner
+
+  Do not output commands to set ownership of objects to match the original database. By default, **gs_restore** issues the **ALTER OWNER** or **SET SESSION AUTHORIZATION** statement to set ownership of created schema elements. Unless the system administrator or the user who has all the objects in the script initially accesses the database. Otherwise, the statement will fail. Any user name can be used for the initial connection using **-O**, and this user will own all the created objects.
+
+- -P, -function=NAME(args)
+
+  Imports only listed functions. You need to correctly spell the function name and the parameter based on the contents of the dump file in which the function exists.
+
+  Entering **-P** alone means importing all function-name(args) functions in a file. Entering **-P** with **-n** means importing the function-name(args) functions in a specified schema. Entering **-P** multiple times and using **-n** once means that all imported functions are in the **-n** schema by default.
+
+  You can enter **-n schema-name -P 'function-name(args)'** multiple times to import functions in specified schemas.
+
+  For example:
+
+  ```
+  gs_restore -h host_name -p port_number -d postgres -n test1 -P 'Func1(integer)' -n test2 -P 'Func2(integer)' backup/MPPDB_backup.tar
+  ```
+
+  In this example, both **Func1 (i integer)** in the **test1** schema and **Func2 (j integer)** in the **test2** schema will be imported.
+
+- -s, -schema-only
+
+  Imports only schemas (data definitions), instead of data (table content). The current sequence value will not be imported.
+
+- -S, -sysadmin=NAME
+
+  Specifies a reserved port for function expansion. This parameter is not recommended.
+
+- -t, -table=NAME
+
+Imports only listed table definitions or data, or both. This parameter can be used in conjunction with the **-n** parameter to specify a table object in a schema. When **-n** is not entered, the default schema is PUBLIC. Entering **-n** *schemaname* **-t** *tablename* multiple times can import multiple tables in a specified schema.
+
+For example:
+
+Import **table1** in the **PUBLIC** schema.
+
+```
+  gs_restore -h host_name -p port_number -d postgres -t table1 backup/MPPDB_backup.tar
+```
+
+Import **test1** in the **test1** schema and **test2** in the **test2** schema.
+
+```
+  gs_restore -h host_name -p port_number -d postgres -n test1 -t test1 -n test2 -t test2 backup/MPPDB_backup.tar
+```
+
+Import **table1** in the **PUBLIC** schema and **test1** in the **table1** schema.
+
+```
+  gs_restore -h host_name -p port_number -d postgres -n PUBLIC -t table1 -n test1 -t table1 backup/MPPDB_backup.tar
+```
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+
+The -t parameter does not support the input format of schema_name.table_name.
+
+- -T, -trigger=NAME
+
+  This parameter is reserved for extension.
+
+- -x, -no-privileges/-no-acl
+
+  Prevents the import of access permissions (**GRANT**/**REVOKE** commands).
+
+- -1, -single-transaction
+
+  Executes import as a single transaction (that is, commands are wrapped in **BEGIN**/**COMMIT**).
+
+  This parameter ensures that either all the commands are completed successfully or no application is changed. This parameter means **-exit-on-error**.
+
+- -disable-triggers
+
+  Specifies a reserved port for function expansion. This parameter is not recommended.
+
+- -no-data-for-failed-tables
+
+  By default, table data will be imported even if the statement to create a table fails (for example, the table already exists). Data in such table is skipped using this parameter. This operation is useful if the target database already contains the desired table contents.
+
+  This parameter takes effect only when you import data directly into a database, not when you output SQL scripts.
+
+- -no-security-labels
+
+  Specifies a reserved port for function expansion. This parameter is not recommended.
+
+- -no-tablespaces
+
+  Tablespaces excluding specified ones All objects will be created during the import process no matter which tablespace is selected when using this option.
+
+- -section=SECTION
+
+  Imports the listed sections (such as pre-data, data, or post-data).
+
+- -use-set-session-authorization
+
+    Is used for plain-text backup.
+
+    Outputs the **SET SESSION AUTHORIZATION** statement instead of the **ALTER OWNER** statement to determine object ownership. This parameter makes dump more standards-compatible. If the records of objects in exported files are referenced, import may fail. Only administrators can use the **SET SESSION AUTHORIZATION** statement to dump data, and the administrators must manually change and verify the passwords of exported files by referencing the **SET SESSION AUTHORIZATION** statement before import. The **ALTER OWNER** statement requires lower permissions.
+
+    ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+
+  - If any local additions need to be added to the template1 database during the installation, restore the output of **gs_restore** into an empty database with caution. Otherwise, you are likely to obtain errors due to duplicate definitions of the added objects. To create an empty database without any local additions, copy data from template0 rather than template1. Example:
+
+    ```
+    CREATE DATABASE foo WITH TEMPLATE template0;
+    ```
+
+  - **gs_restore** cannot import large objects selectively. For example, it can only import the objects of a specified table. If an archive contains large objects, all large objects will be imported, or none of them will be restored if they are excluded by using **-L**, **-t**, or other parameters.
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+
+1. The **-d/-dbname** and **-f/-file** parameters do not coexist.
+2. The **-s/-schema-only** and **-a/-data-only** parameters do not coexist.
+3. The **-c/-clean** and **-a/-data-only** parameters do not coexist.
+4. When **-single-transaction** is used, **-j/-jobs** must be a single job.
+5. **-role** must be used in conjunction with **-rolepassword**.
+
+Connection parameters:
+
+- -h, -host=HOSTNAME
+
+  Specifies the host name. If the value begins with a slash (/), it is used as the directory for the UNIX domain socket. The default value is taken from the *PGHOST* environment variable. If it is not set, a UNIX domain socket connection is attempted.
+
+  This parameter is used only for defining names of the hosts outside MogDB. The names of the hosts inside MogDB must be 127.0.0.1.
+
+- -p, -port=PORT
+
+  TCP port or the local Unix-domain socket file extension on which the server is listening for connections. The default value is the *PGPORT* environment variable.
+
+  If the thread pool function is enabled, you are advised to use **pooler port**, that is, the listening port number plus 1.
+
+- -U, -username=NAME
+
+  Specifies the user name to connect to.
+
+- -w, -no-password
+
+  Never issues a password prompt. The connection attempt fails if the host requires password verification and the password is not provided in other ways. This parameter is useful in batch jobs and scripts in which no user password is required.
+
+- -W, -password=PASSWORD
+
+  User password for database connection. If the host uses the trust authentication policy, the administrator does not need to enter the **-W** parameter. If the **-W** parameter is not provided and you are not a system administrator, **gs_restore** will ask you to enter a password.
+
+- -role=ROLENAME
+
+  Specifies a role name for the import operation. If this parameter is selected, the **SET ROLE** statement will be issued after **gs_restore** connects to the database. It is useful when the authenticated user (specified by **-U**) lacks the permissions required by **gs_restore**. This parameter allows the user to switch to a role with the required permissions. Some installations have a policy against logging in directly as the initial user. This parameter allows data to be imported without violating the policy.
+
+- -rolepassword=ROLEPASSWORD
+
+  Role password.
+
+## Example
+
+Special case: Execute the **gsql** tool. Run the following commands to import the **MPPDB_backup.sql** file in the export folder (in plain-text format) generated by **gs_dump**/**gs_dumpall** to the **postgres** database:
+
+```
+gsql -d postgres -p 5432 -W Bigdata@123 -f /home/omm/test/MPPDB_backup.sql
+SET
+SET
+SET
+SET
+SET
+ALTER TABLE
+ALTER TABLE
+ALTER TABLE
+ALTER TABLE
+ALTER TABLE
+CREATE INDEX
+CREATE INDEX
+CREATE INDEX
+SET
+CREATE INDEX
+REVOKE
+REVOKE
+GRANT
+GRANT
+total time: 30476  ms
+```
+
+**gs_restore** is used to import the files exported by **gs_dump**.
+
+Example 1: Execute the **gs_restore** tool to import the exported **MPPDB_backup.dmp** file (custom format) to the **postgres** database.
+
+```
+gs_restore -W Bigdata@123 backup/MPPDB_backup.dmp -p 5432 -d postgres
+gs_restore: restore operation successful
+gs_restore: total time: 13053  ms
+```
+
+Example 2: Execute the **gs_restore** tool to import the exported **MPPDB_backup.tar** file (.tar format) to the **postgres** database.
+
+```
+gs_restore backup/MPPDB_backup.tar -p 5432 -d postgres
+gs_restore[2017-07-21 19:16:26]: restore operation successful
+gs_restore[2017-07-21 19:16:26]: total time: 21203  ms
+```
+
+Example 3: Execute the **gs_restore** tool to import the exported **MPPDB_backup** file (directory format) to the **postgres** database.
+
+```
+gs_restore backup/MPPDB_backup -p 5432 -d postgres
+gs_restore[2017-07-21 19:16:26]: restore operation successful
+gs_restore[2017-07-21 19:16:26]: total time: 21003  ms
+```
+
+Example 4: Execute the **gs_restore** tool and run the following commands to import the **MPPDB_backup.dmp** file (in custom format). Specifically, import all the object definitions and data in the **PUBLIC** schema. Existing objects are deleted from the target database before the import. If an existing object references to an object in another schema, you need to manually delete the referenced object first.
+
+```
+gs_restore backup/MPPDB_backup.dmp -p 5432 -d postgres -e -c -n PUBLIC
+gs_restore: [archiver (db)] Error while PROCESSING TOC:
+gs_restore: [archiver (db)] Error from TOC entry 313; 1259 337399 TABLE table1 gaussdba
+gs_restore: [archiver (db)] could not execute query: ERROR:  cannot drop table table1 because other objects depend on it
+DETAIL:  view t1.v1 depends on table table1
+HINT:  Use DROP ... CASCADE to drop the dependent objects too.
+    Command was: DROP TABLE public.table1;
+```
+
+Manually delete the referenced object and create it again after the import is complete.
+
+```
+gs_restore backup/MPPDB_backup.dmp -p 5432 -d postgres -e -c -n PUBLIC
+gs_restore[2017-07-21 19:16:26]: restore operation successful
+gs_restore[2017-07-21 19:16:26]: total time: 2203  ms
+```
+
+Example 5: Execute the **gs_restore** tool and run the following commands to import the **MPPDB_backup.dmp** file (in custom format). Specifically, import only the definition of **table1** in the **PUBLIC** schema.
+
+```
+gs_restore backup/MPPDB_backup.dmp -p 5432 -d postgres -e -c -s -n PUBLIC -t table1
+gs_restore[2017-07-21 19:16:26]: restore operation successful
+gs_restore[2017-07-21 19:16:26]: total time: 21000  ms
+```
+
+Example 6: Execute the **gs_restore** tool and run the following commands to import the **MPPDB_backup.dmp** file (in custom format). Specifically, import only the data of **table1** in the **PUBLIC** schema.
+
+```
+gs_restore backup/MPPDB_backup.dmp -p 5432 -d postgres -e -a -n PUBLIC -t table1
+gs_restore[2017-07-21 19:16:26]: restore operation successful
+gs_restore[2017-07-21 19:16:26]: total time: 20203  ms
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/system-catalogs-and-views-supported-by-gs_collector.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/system-catalogs-and-views-supported-by-gs_collector.md
new file mode 100644
index 0000000000000000000000000000000000000000..299c7d714f96568cecb5514fc702b5c6fad4b313
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/system-catalogs-and-views-supported-by-gs_collector.md
@@ -0,0 +1,92 @@
+---
+title: System Catalogs and Views Supported by gs_collector
+summary: System Catalogs and Views Supported by gs_collector
+author: Zhang Cuiping
+date: 2021-11-17
+---
+
+# System Catalogs and Views Supported by gs_collector
+
+- OS
+  - gs_os_run_info
+  - pg_os_threads
+- Session/Thread
+  - gs_session_stat
+  - gs_session_time
+  - gs_session_cpu_statistics
+  - gs_session_memory_statistics
+  - gs_session_memory_context
+  - gs_session_memory
+  - gs_session_memory_detail
+  - pg_stat_activity
+  - gs_thread_memory_context
+- WLM
+  - gs_cluster_resource_info
+  - pg_total_user_resource_info
+  - pg_total_user_resource_info_oid
+  - gs_wlm_rebuild_user_resource_pool
+  - gs_wlm_resource_pool
+  - gs_wlm_workload_records
+  - pg_wlm_statistics
+  - pg_app_workloadgroup_mapping
+- Query-AP Operator
+  - gs_wlm_operator_info
+  - gs_wlm_operator_history
+  - gs_wlm_operator_statistics
+- Query-AP
+  - gs_wlm_session_info_all
+  - gs_wlm_session_history
+  - gs_wlm_session_info
+  - gs_wlm_user_session_info
+  - gs_wlm_session_statistics
+  - pg_session_iostat
+  - pg_session_wlmstat
+- Cache I/O
+  - pg_statio_all_indexes
+  - pg_statio_all_sequences
+  - pg_statio_all_tables
+  - pg_statio_sys_indexes
+  - pg_statio_sys_sequences
+  - pg_statio_sys_tables
+  - pg_statio_user_indexes
+  - pg_statio_user_sequences
+  - pg_statio_user_tables
+  - gs_stat_db_cu
+  - gs_stat_session_cu
+- Memory
+  - pg_total_memory_detail
+  - pg_shared_memory_detail
+  - gs_total_memory_detail
+- File
+  - gs_file_stat
+  - gs_redo_stat
+  - pg_stat_bad_block
+- Object
+  - pg_stat_user_tables
+  - pg_stat_user_indexes
+  - pg_stat_sys_tables
+  - pg_stat_sys_indexes
+  - pg_stat_all_tables
+  - pg_stat_all_indexes
+  - pg_stat_database
+  - pg_stat_database_conflicts
+  - pg_stat_xact_all_tables
+  - pg_stat_xact_sys_tables
+  - pg_stat_xact_user_tables
+  - pg_stat_xact_user_functions
+- Lock
+  - pg_locks
+- Utility
+  - pg_stat_replication
+  - pg_replication_slots
+  - pg_stat_bgwriter
+- Transaction
+  - pg_running_xacts
+  - pg_prepared_xacts
+- Waits
+  - pg_thread_wait_status
+
+<!--
+**Table 1** System catalogs and views supported by **gs_collector**
+
+<table>    <tr>          <td>Class</td>          <td>View Name</td>           </tr>       <tr>           <td rowspan="2" >OS</td>           <td>gs_os_run_info</td>           </tr>        <tr>          <td>pg_os_threads</td>           </tr>       <tr >         <td rowspan="9">Session/Thread</td>            <td> gs_session_stat</td>           </tr>       <tr>          <td>gs_session_time</td>          </tr>     <tr>          <td>gs_session_cpu_statistics</td>          </tr>     <tr>          <td>gs_session_memory_statistics</td>          </tr>     <tr>          <td>gs_session_memory_context</td>          </tr>     <tr>          <td>gs_session_memory</td>          </tr>     <tr>          <td>gs_session_memory_detail</td>          </tr>       <tr>          <td>pg_stat_activity</td>          </tr>       <tr>          <td>gs_thread_memory_context</td>          </tr>     <tr >         <td rowspan="8">WLM</td>            <td>gs_cluster_resource_info</td>           </tr>       <tr>          <td>pg_total_user_resource_info</td>          </tr>     <tr>          <td>pg_total_user_resource_info_oid</td>          </tr>     <tr>          <td>gs_wlm_rebuild_user_resource_pool</td>          </tr>     <tr>          <td>gs_wlm_resource_pool</td>          </tr>     <tr>          <td>gs_wlm_workload_records</td>          </tr>     <tr>          <td>pg_wlm_statistics</td>          </tr>       <tr>          <td>pg_app_workloadgroup_mapping</td>          </tr>     <tr >         <td rowspan="3">Query-AP Operator</td>            <td>gs_wlm_operator_info</td>           </tr>       <tr>          <td>gs_wlm_operator_history</td>          </tr>     <tr>         <td>gs_wlm_operator_statistics</td>          </tr>     <tr >         <td rowspan="7">Query-AP</td>            <td>gs_wlm_session_info_all</td>           </tr>       <tr>          <td>gs_wlm_session_history</td>          </tr>     <tr>          <td>gs_wlm_session_info</td>          </tr>     <tr>          <td>gs_wlm_user_session_info</td>          </tr>     <tr>          <td>gs_wlm_session_statistics</td>          </tr>     <tr>          <td>pg_session_iostat</td>          </tr>     <tr>          <td>pg_session_wlmstat</td>          </tr>     <tr >         <td rowspan="11">Cache I/O</td>            <td>pg_statio_all_indexes</td>           </tr>       <tr>          <td>pg_statio_all_sequences</td>          </tr>     <tr>          <td>pg_statio_all_tables</td>          </tr>     <tr>          <td>pg_statio_sys_indexes</td>          </tr>     <tr>          <td>pg_statio_sys_sequences</td>          </tr>     <tr>          <td>pg_statio_sys_tables</td>          </tr>     <tr>          <td>pg_statio_user_indexes</td>          </tr>     <tr>          <td>pg_statio_user_sequences</td>          </tr>     <tr>          <td>pg_statio_user_tables</td>          </tr>     <tr>          <td>gs_stat_db_cu</td>          </tr>     <tr>          <td>gs_stat_session_cu</td>          </tr>     <tr >         <td rowspan="3">Memory</td>            <td>pg_total_memory_detail</td>           </tr>       <tr>          <td>pg_shared_memory_detail</td>          </tr>     <tr>         <td>gs_total_memory_detail</td>          </tr>     <tr >         <td rowspan="3">File</td>            <td>gs_file_stat</td>           </tr>       <tr>          <td>gs_redo_stat</td>          </tr>     <tr>         <td>pg_stat_bad_block</td>          </tr>     <tr >         <td rowspan="12">Object</td>            <td>pg_stat_user_tables</td>           </tr>       <tr>          <td>pg_stat_user_indexes</td>          </tr>     <tr>          <td>pg_stat_sys_tables</td>          </tr>     <tr>          <td>pg_stat_sys_indexes</td>          </tr>     <tr>          <td>pg_stat_all_tables</td>          </tr>     <tr>          <td>pg_stat_all_indexes</td>          </tr>     <tr>          <td>pg_stat_database</td>          </tr>     <tr>          <td>pg_stat_database_conflicts</td>          </tr>     <tr>          <td>pg_stat_xact_all_tables</td>          </tr>     <tr>          <td>pg_stat_xact_sys_tables</td>          </tr>     <tr>          <td>pg_stat_xact_user_tables</td>          </tr>    <tr>          <td>pg_stat_xact_user_functions</td>          </tr>     <tr>          <td>Lock</td>            <td>pg_locks</td>          </tr>     <tr >         <td rowspan="3">Utility</td>            <td>pg_stat_replication</td>           </tr>       <tr>          <td>pg_replication_slots</td>          </tr>     <tr>          <td>pg_stat_bgwriter</td>          </tr>     <tr >         <td rowspan="2">Transaction</td>            <td>pg_running_xacts</td>           </tr>       <tr>          <td>pg_prepared_xacts</td>          </tr>     <tr>          <td>Waits</td>            <td>pg_thread_wait_status</td>          </tr>       </table> -->
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tool-overview.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tool-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..7f0f4b45cc1212ee9028d8b15a05e5b493863bef
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tool-overview.md
@@ -0,0 +1,77 @@
+---
+title: Tool Overview
+summary: Tool Overview
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# Tool Overview
+
+MogDB provides client and server applications (tools) to help users better maintain MogDB. [Table 1](#tooloverview) lists all the tools provided by MogDB. The tools are stored in **$GPHOME/script** and **$GAUSSHOME/bin** where database servers are installed.
+
+**Table 1** Tool overview <a id="tooloverview"> </a>
+
+<table>
+    <tr>
+        <th>Category</th>
+        <th>Name</th>
+        <th>Description</th>
+    </tr>
+    <tr>
+        <td>Client tool</td>
+        <td>gsql</td>
+        <td>gsql is a database connection tool provided by MogDB and runs in the command-line interface (CLI). Users can use gsql to connect to a server and perform operations and maintenance on the server. In addition to basic functions for performing operations on a database, gsql provides several advanced features for users.</td>
+    </tr>
+    <tr>
+        <td rowspan="13">Server tool</td>
+        <td>gs_cgroup</td>
+        <td>gs_cgroup is a load management tool provided by MogDB. It can create default Cgroups and user-defined Cgroups, delete default and user-defined Cgroups, update resource quotas and allocations, display the configuration files of Cgroups and the Cgroup tree, and delete all Cgroups.</td>
+    </tr>
+    <tr>
+        <td >gs_check</td>
+        <td> gs_check has been enhanced to unify functions of various check tools, such as gs_check and gs_checkos. It helps users fully check MogDB runtime, OS, network, and database running environments; as well as perform comprehensive checks on various environments before major operations in MogDB, ensuring smooth operation.</td>
+    </tr>
+    <tr>
+        <td>gs_checkos</td>
+        <td>gs_checkos checks OS information, control parameters, and disk configurations, and configures control parameters, I/O parameters, network parameters, and THP services.</td>
+    </tr>
+    <tr>
+        <td>gs_checkperf</td>
+        <td>gs_checkperf routinely checks MogDB-level performance (host CPU, MogDB GPU, and I/O usage), node-level performance (CPU, memory, and I/O usage), session-/process-level performance (CPU, memory, and I/O usage), and SSD performance (read and write performance). It provides MogDB load information for users so that they can fine-tune database performance accordingly.</td>
+    </tr>
+    <tr>
+        <td>gs_collector</td>
+        <td>When MogDB is faulty, gs_collector collects OS information, log information, and configuration file information to locate the fault. </td>
+    </tr>
+    <tr>
+        <td>gs_dump</td>
+        <td>gs_dump exports database information. It can export complete, consistent data of database objects (such as databases, schemas, tables, and views) without affecting the normal access of users to the databases.</td> </tr>
+    <tr>
+        <td>gs_dumpall</td>
+        <td>gs_dumpall exports database information. It can export complete, consistent data of MogDB database objects without affecting the normal access of users to the database.</td>
+    </tr>
+    <tr>
+        <td>gs_guc</td>
+        <td>gs_guc is used to set parameters in MogDB configuration files (postgresql.conf or pg_hba.conf). The default parameter values in a configuration file are consistent with those for a standalone database.</td>
+    </tr>
+    <tr>
+        <td>gs_encrypt</td>
+        <td>gs_encrypt is used to encrypt entered plaintext strings.</td>
+    </tr>
+    <tr>
+        <td>gs_om</td>
+        <td>gs_om, provided by MogDB, helps you maintain MogDB, including starting and stopping MogDB, querying the MogDB status, generating static configuration files, updating dynamic configuration files, replacing SSL certificates, starting and stopping Kerberos authentication, and showing help information and version numbers.</td>
+    </tr>
+    <tr>
+        <td>gs_plan_simulator</td>
+        <td>gs_plan_simulator collects data related to execution plans and reproduces execution plans in other environments to locate execution plan problems.</td>
+    </tr>
+    <tr>
+        <td>gs_restore</td>
+        <td>gs_restore, provided by MogDB, is used to import data that was exported using gs_dump. It can also be used to import files exported by gs_dump.</td>
+    </tr>
+    <tr>
+        <td>gs_ssh</td>
+        <td>gs_ssh, provided by MogDB, helps users run the same command on multiple nodes in MogDB.</td>
+    </tr>
+</table>
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/1-gaussdb.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/1-gaussdb.md
new file mode 100644
index 0000000000000000000000000000000000000000..1159c69e8810ae71e653fc2a17c2a8dc7b229366
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/1-gaussdb.md
@@ -0,0 +1,176 @@
+---
+title: gaussdb
+summary: gaussdb
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gaussdb
+
+## Background
+
+**gaussdb** is a major process of MogDB and also an executable command. A database process can be started using gaussdb.
+
+## Syntax
+
+```
+gaussdb [OPTION]...
+```
+
+## Description
+
+To access the database, the client application connects (over a local network or the Internet) to a running gaussdb process. Then the process starts an independent thread to handle the connection.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> When starting the database using **gaussdb**, you also need to open another window to connect to the database or use & to enable the application to run in the background.
+
+A **gaussdb** process manages all data in a database. A system can operate multiple **gaussdb** processes using different data directories and port numbers. When **gaussdb** is started, the data directory must be specified using the **-data-dir** option. Typically, **-D** points directly to the database directory created by **gs_initdb**.
+
+By default, **gaussdb** starts in the foreground and prints log messages to the standard error stream. In practical applications, **gaussdb** should be automatically started as a background process at boot time in most cases.
+
+The **gaussdb** command can also be called in single-user mode. The primary use for this mode is during the initialization of gs_initdb. Sometimes, it is used for debugging or disaster recovery. However, running a single-user server is not truly suitable for debugging the server, because no realistic inter-process communication and locking happens. When the **gaussdb** command is called in single-user mode from the shell, you can enter queries, and the results will be printed to the screen, but in a form that is more useful for developers rather than common users. In single user mode, the session user ID is set to **1** and given the administrator rights. The user does not need to be existent. Therefore, servers in single user mode can be used to manually recover damaged system catalogs.
+
+## Options
+
+**gaussdb** supports command-line parameters listed in [Table 1](#parameter).
+
+**Table 1** Parameter description <a id="parameter"></a>
+
+| Parameter          | Parameter Description                                        | Value Range                                                  |
+| :----------------- | :----------------------------------------------------------- | :----------------------------------------------------------- |
+| -B NBUFFERS        | Sets the number of shared buffers to be used by the server processes. | -                                                            |
+| -b BINARY UPGRADES | Specifies binary upgrade.                                    | -                                                            |
+| -c NAME=VALUE      | Assigns a value to a running parameter. **-c** can appear multiple times to set multiple parameters. | -                                                            |
+| -C NAME            | Prints the value of a named run-time parameter and then exits. It can be used on a running server, and returns values from **postgresql.conf**. | The value can be the value of any parameter in the **postgresql.conf** file. |
+| -d 1-5             | Sets the debug level. The value ranges from **1** to **5** indicates debug level information recorded. The higher this value is set, the more debugging output is written to the server logs. | Value range: 1 to 5<br />NOTE:<br />If the value is less than or equal to **0**, only notice-level information is recorded. |
+| -D DATADIR         | Specifies the data directory or location of configuration files. | User-defined value.                                          |
+| -e                 | Sets the default date style to **European**, that is DMY ordering of input date fields. It also prints the day before the month in certain date output formats. | -                                                            |
+| -F                 | Disables fsync calls for improved performance, at the risk of data corruption in the event of a system crash. Specifying this option is equivalent to disabling the fsync parameter. | -                                                            |
+| -h HOSTNAME        | Specifies the host name or IP address on which **gaussdb** listens to TCP/IP connections from client applications. | Existing host name or IP address at the front-end.           |
+| -i                 | Allows remote clients to communicate with the server through TCP/IP (Internet domain socket) connections. | -                                                            |
+| -k DIRECTORY       | Specifies the directory of the Unix domain socket on which gaussdb listens to connections from client applications. | The default value is normally **/tmp**, but it can be changed during compilation. |
+| -l                 | Allows remote clients to connect to the server via secure socket layer (SSL). | -                                                            |
+| -N MAX-CONNECT     | Sets the maximum number of client connections that this server will accept. The default value of this parameter is automatically chosen by gs_initdb. Specifying this option is equivalent to setting the max_connections configuration parameter. | Value range: a positive integer.                             |
+| -M SERVERMODE      | Specifies the startup mode.                                  | Values:<br />- **primary**: The server starts in primary mode.<br />- **standby**: The server starts in standby mode.<br />- **cascade_standby**: The local server starts as a cascaded standby server.<br />- **pending**: The server is in pending mode to be promoted to a primary server or a standby server. |
+| -p PORT            | Specifies the TCP/IP port or local Unix domain socket file extension on which gaussdb is to listen for connections from client applications. The default port ID is 5432. | A positive integer within the port range supported by the OS. |
+| -s                 | Prints time information and other statistics at the end of each command. | -                                                            |
+| -S WORK-MEM        | Specifies the size of memory to be used by internal sorts and hashes before resorting to temporary disk files. | The unit is KB.                                              |
+| -single_node       | Start a single-node database.                                | -                                                            |
+| -V, -version       | Prints the **gaussdb** version and exits.                    | -                                                            |
+| -NAME=VALUE        | Assigns a value to a running parameter.                      | -                                                            |
+| -describe-config   | Describes configuration parameters and then exits.           | -                                                            |
+| -?, -help          | Displays help about the **gaussdb** command line arguments and then exits. | -                                                            |
+
+Parameters described in [Table 2](#developer) are used for debugging purposes, and in some cases for assisting in recovering severely damaged databases. Do not use these parameters for debugging if databases are providing services for applications.
+
+**Table 2** Developer options <a id="developer"></a>
+
+| Parameter        | Parameter Description                                        | Value Range                                                  |
+| :--------------- | :----------------------------------------------------------- | :----------------------------------------------------------- |
+| -f s\|i\|n\|m\|h | Forbids the use of particular scan and join methods.         | Value range:<br />- **s**: stop sequence<br />- **i**: index scanning<br />- **n**: nested loop is disabled.<br />- **m**: merge join<br />- **h**: hash join |
+| -n               | Debugs problems that cause a server process breakdown. The ordinary strategy in this situation is to instruct all other server processes to terminate and then reinitialize the shared memory and semaphores. This option specifies that **gaussdb** will not reinitialize shared memory. | -                                                            |
+| -P               | Ignores system indexes when reading system tables, but still updates the indexes when modifying the tables. | -                                                            |
+| -t pa\|pl\|ex    | Prints timing statistics for each query relating to each of the major system modules. | -                                                            |
+| -T               | Debugs problems that cause a server process breakdown. This option specifies that gaussdb will stop all other server processes by sending the signal SIGSTOP, but will not cause them to exit. This permits system programmers to manually collect core dumps from all server processes. | -                                                            |
+| -W NUM           | Specifies the number of seconds to wait before a new server process is started. | Unit: second                                                 |
+| -localxid        | Uses the local transaction ID instead of the global transaction ID.<br />NOTICE:<br />This option is used only for **gs_initdb**. Using this option may cause database inconsistency. | Existing local transaction ID.                               |
+
+Options listed in [Table 3](#options) apply only to the single user mode.
+
+**Table 3** Options for the single-user mode <a id="options"></a>
+
+| Parameter   | Parameter Description                                        | Value Range                                             |
+| :---------- | :----------------------------------------------------------- | :------------------------------------------------------ |
+| -single     | Selects the single user mode. This must be the first argument on the command line. | -                                                       |
+| DBNAME      | Specifies the name of the database to be accessed.This must be the last argument on the command line. | A character string. The default value is the user name. |
+| -d 0-5      | Re-specifies the debug level.                                | 0-5                                                     |
+| -E          | Echoes all commands.                                         | -                                                       |
+| -j          | Disables use of newline as a statement delimiter.            | -                                                       |
+| -r FILENAME | Saves all server standard output and standard errors to **filename**. | -                                                       |
+
+**Table 4** Automatic startup mode options
+
+| Parameter   | Parameter Description                                        | Value Range |
+| :---------- | :----------------------------------------------------------- | :---------- |
+| -boot       | Enables the automatic startup mode. This must be the first argument on the command line. This parameter initializes parameter variables and related configurations. It is usually used in the database installation process and is unperceivable. | -           |
+| -r FILENAME | Saves all server standard output and standard errors to **filename**. | -           |
+| -x NUM      | Specifies a new server thread type. The automatic startup mode can be used during database initialization. This parameter starts various threads to execute different logics. Generally, this parameter is not used because the automatic startup mode is seldom used. | -           |
+
+**Table 5** Upgrade mode options
+
+| Parameter | Parameter Description                                     | Value Range |
+| :-------- | :-------------------------------------------------------- | :---------- |
+| -u NUM    | Specifies the database kernel version before the upgrade. | -           |
+
+In addition to the preceding parameters, all parameters in postgres.conf can be transferred to **gaussdb** using -**guc_name=guc_value** when **gaussdb** is started. For example: **-enable_fast_query_shipping=off**
+
+## Environment Variables
+
+- **PGLINETENCODING**: default character encoding used by clients. Clients can overwrite it individually. This value can also be set in the configuration file.
+- **PGDATESTYLE**: default value of the run-time **DateStyle** parameter. The use of this environment variable is deprecated.
+- **TZ**: server time zone.
+
+## Error Handling
+
+A failure message mentioning **semget** or **shmget** probably indicates that you need to reconfigure your kernel to provide adequate shared memory and semaphores. You can decrease **shared_buffers** to reduce the shared memory consumption of MogDB, or decrease **max_connections** to reduce the semaphore consumption of MogDB.
+
+If a failure message suggesting that another server is running is reported, check the system using the following command based on your system:
+
+```
+ps ax | grep gaussdb
+```
+
+or
+
+```
+ps -ef | grep gaussdb
+```
+
+If you are certain that no conflicting server is running, you can remove the lock file mentioned in the message and try again.
+
+A failure message indicating inability to bind to a port might indicate that the port is already in use by a non-MogDB process. This message may also be reported if you terminate **gaussdb** and immediately restart it using the same port. In this case, you must simply wait a few seconds until the operating system closes the port before trying again. Finally, you may get this error if you specify a port number that your operating system considers it to be reserved. For example, the Unix considers ports whose IDs are under 1024 to be "trusted" and permits only Unix administrators to access the Unix.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - If possible, do not use SIGKILL to stop the main process. because the operation prevents **gaussdb** from releasing system resources (such as shared memory and semaphores) that it holds before terminating. This might cause problems for starting a fresh process.
+> - To properly terminate the server process, signals **SIGTERM**, **SIGINT**, and **SIGQUIT** can be used. **SIGTERM** will wait for all clients to terminate before exit. **SIGINT** will forcibly disconnect all clients, and **SIGQUIT** will exit immediately without proper shutdown, resulting in a recovery run during restart.
+> - The SIGHUP signal will reload the server configuration files. It is also possible to send **SIGHUP** to an individual server process, but that is usually not sensible.
+> - To cancel a running query, send the **SIGINT** signal to the process running that command.
+> - The main server process uses **SIGTERM** to tell its subordinate server processes to quit properly and SIGQUIT to terminate without a cleanup. These signals should not be used by users. It is also unwise to send SIGKILL to a server process: The main process will interpret this as a crash and will force all the subordinate processes to quit as part of its standard crash-recovery pocedure.
+
+## **Usage**
+
+Run the following command to start a server in single-user mode:
+
+```
+gaussdb --single -D /usr/local/pgsql/data other-options my_database
+```
+
+Use **-D** to provide the correct path of the database directory for the server. Besides, specify the name of the existing particular database.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+>
+> - In most cases, the single-user mode server treats newline as the command entry terminator. To continue a command across multiple lines, you must type a backslash just before each newline except the last one.
+> - If you use the -j command line option, then newline does not terminate command entry. In this case, the server will read the standard input until the end-of-file (EOF) marker, then process the input as a single command string. Backslashes and newlines are treated as common characters in this case.
+> - To quit the session, type EOF (Control+D). If you have used -j, two consecutive EOFs are needed to exit.
+> - The single-user mode server does not provide complex line-editing functions (no command history, for example). The single-user mode also does not do any background processing, like automatic checkpoints.
+
+## Example
+
+1. Run the following command to start gaussdb in the background using default values:
+
+   ```
+   nohup gaussdb >logfile 2>&1 </dev/null  &
+   ```
+
+2. Run the following command to start gaussdb with a specified port, for example, 1234:
+
+   ```
+   gaussdb --single_node -p -D data_dir
+   ```
+
+   To connect to this server using gsql, specify this port with the -p option:
+
+   ```
+   gsql -d postgres -p 1234
+   ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/10-gs_tar.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/10-gs_tar.md
new file mode 100644
index 0000000000000000000000000000000000000000..126cb2d16e050de867b73e6b502ce45639180545
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/10-gs_tar.md
@@ -0,0 +1,49 @@
+---
+title: gs_tar
+summary: gs_tar
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_tar
+
+## Background
+
+After the backup is compressed using **gs_basebackup**, the primary data directory is written to a file named **base.tar**, and other tablespaces are named after their OIDs. The generated data file needs to be decompressed using the **gs_tar** command.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - Currently, the **gs_tar** command can only be used to decompress archive files generated by **gs_basebackup**.
+> - If a compression level is specified by **gs_basebackup**, a file ended with gz will be generated. In this case, you need to run the **gzip** command to decompress the generated .tar package, and then run the **gs_tar** command to decompress the generated .tar file.
+
+## Syntax
+
+Display help information.
+
+```
+gs_tar -? | --help
+```
+
+Display version information.
+
+```
+gs_tar -V | --version
+```
+
+## Parameter Description
+
+**gs_tar** parameters are as follows:
+
+- -F, -filename=FILENAME
+
+Decompresses a file. This parameter is mandatory.
+
+- -D, -destination=DIRECTORY
+
+Directory for storing decompressed files. This parameter is mandatory.
+
+## Example
+
+```
+gs_tar -D /home/test/dn1 -F /home/test/trunk/install/data/backup/base.tar
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/11-gs_uninstall.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/11-gs_uninstall.md
new file mode 100644
index 0000000000000000000000000000000000000000..a22a6b2fd4ba595cee9383c45f987f40fbb3a480
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/11-gs_uninstall.md
@@ -0,0 +1,80 @@
+---
+title: gs_uninstall
+summary: gs_uninstall
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_uninstall
+
+## Background
+
+gs_uninstall, provided by , can be used to uninstall a cluster.
+
+## Syntax
+
+- Uninstalling MogDB
+
+  ```
+  gs_uninstall [--delete-data] [-L] [-l LOGFILE]
+  ```
+
+- Display help information.
+
+  ```
+  gs_uninstall -? | --help
+  ```
+
+- Display the version number.
+
+  ```
+  gs_uninstall -V | --version
+  ```
+
+## Parameter Description
+
+- -delete-data
+
+  Deletes the data file.
+
+- -L
+
+  Uninstalls the local host only. If a host in MogDB is uninstalled, MogDB cannot be performed full uninstallation.
+
+- -l
+
+    Specifies a log file name and its absolute path that can be accessed. A timestamp will be added automatically to the log file name.
+
+  - When **-l** is not specified and **gaussdbLogPath** is not set in the XML file, the default value of the **-l** parameter is *$GAUSSLOG***/om/gs_uninstall-YYYY-MM-DD_hhmmss.log**.
+
+  - When **-l** is not specified but **gaussdbLogPath** is set in the XML file, the default value of the **-l** parameter is **gaussdbLogPath/***Username***/om/gs_uninstall-YYYY-MM-DD_hhmmss.log**.
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** When executing **gs_uninstall**, the system will automatically delete the directories related to MogDB. You are advised to set the log file path to a path outside the MogDB database.
+
+- -?, -help
+
+  Displays help information.
+
+- -V, -version
+
+  Displays version information.
+
+## Example
+
+Execute the **gs_uninstall** script as a database user to uninstall MogDB.
+
+```
+gs_uninstall --delete-data
+Checking uninstallation.
+Successfully checked uninstallation.
+Stopping the cluster.
+Successfully stopped the cluster.
+Successfully deleted instances.
+Uninstalling application.
+Successfully uninstalled application.
+Uninstallation succeeded.
+```
+
+## Related Commands
+
+[gs_install](6-gs_install) and [gs_postuninstall](7-gs_postuninstall)
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/12-gs_upgradectl.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/12-gs_upgradectl.md
new file mode 100644
index 0000000000000000000000000000000000000000..e63211e5e085973604e72a149e7a576b3a1e5c32
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/12-gs_upgradectl.md
@@ -0,0 +1,249 @@
+---
+title: gs_upgradectl
+summary: gs_upgradectl
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_upgradectl
+
+## Context
+
+You can determine whether to upgrade the existing system based on the new features provided by the MogDB and the current database status.
+
+Currently, in-place upgrade and gray upgrade are supported. The upgrade modes are classified into major version upgrade and minor version upgrade.
+
+After you select an upgrade mode, the system automatically determines and selects a proper upgrade policy.
+
+In-place upgrade: During the upgrade, services must be stopped and all nodes must be upgraded at a time.
+
+Gray upgrade: supports operations on all service during the upgrade and upgrades all nodes at a time. (This function is supported in versions later than MogDB 1.1.0.)
+
+## Precautions
+
+- Do not perform the upgrade, scale-out, and scale-in at the same time.
+- Virtual IP addresses are not supported.
+- During the upgrade, do not change the values of the **wal_level**, **max_connections**, **max_prepared_transactions**, and **max_locks_per_transaction** GUC parameters. If the value is changed, the instance fails to be started after the rollback.
+- You are advised to perform upgrade when the database system is idle. You can determine the upgrade time (for example, holidays) based on experience.
+- Before the upgrade, ensure that the database is normal. You can run the **gs_om -t status** command to query the database status. If the value of **cluster_state** in the query result is **Normal**, the database is normal.
+- Ensure that the database mutual trust is normal before the upgrade. You can run the **ssh hostname** command on any node to connect to another node for verification. If no password is required for the interconnection between hosts, the mutual trust relationship is normal. (Generally, the mutual trust relationship is normal when the database is running properly.)
+- Before and after the upgrade, the database deployment mode (configuration file) cannot be changed. Before the upgrade, the deployment mode is verified. If the deployment mode is changed, an error is reported.
+- Ensure that the OS is healthy before the upgrade. You can use the **gs_checkos** tool to check the OS status.
+- Services need to be stopped during in-place upgrade. Online upgrade supports all service operations.
+- The database is running properly and data on the primary DN has been fully synchronized to standby DNs.
+- Do not enable Kerberos during the upgrade.
+- Do not modify the **version.cfg** file decompressed from the installation package.
+- If the upgrade fails due to an exception, you need to manually roll back the upgrade. The next upgrade can be performed only after the rollback is successful.
+- If the second upgrade is successful after the rollback, the GUC parameters that are set at the uncommitted stage become invalid.
+- Do not manually set GUC parameters during the upgrade.
+- In gray upgrade, services are interrupted for less than 10s during the upgrade.
+- During the upgrade, ensure that the kernel version is the same as the OM version before OM operations. That is, the kernel code and OM code are from the same software package. If the preinstallation script of an upgrade package is executed but the upgrade fails or the preinstallation script of a baseline package is not executed after the upgrade rollback, the kernel code is inconsistent with the OM code.
+- If new columns are added to the system catalog during the upgrade, you cannot view these new columns by running the **\d** command after the upgrade. However, you can run the **SELECT** command to query the new columns.
+- The GUC parameter **enable_stream_replication** must be set to **on** for the upgrade. If this parameter is set to **off**, the upgrade is not allowed.
+- In gray upgrade, ensure that there are less than 200 concurrent reads and 200 concurrent writes.
+- In a cluster with one primary node and multiple standby nodes, after the cluster is upgraded to a version later than MogDB 1.1.0, if listen_addresses in the configuration file is changed to '*', you need to change values of localport in replconninfo1, ……replconninfo* to the original values plus 5. For example, if the original value is 16000, you need to change it to 16005. Otherwise, the cluster fails to be restarted.
+- You are advised to perform the upgrade when the disk usage of the database node is less than 80%.
+- After executing gs_upgradectl -t auto-upgrade, snapshot generation cannot be performed before it is submitted, that is, snapshot generation cannot be performed during upgrade.
+
+## Syntax
+
+- Display help information.
+
+  ```
+  gs_upgradectl -? | --help
+  ```
+
+- Display version information.
+
+  ```
+  gs_upgradectl -V | --version
+  ```
+
+- Select an upgrade policy.
+
+  ```
+  gs_upgradectl -t chose-strategy [-l LOGFILE]
+  ```
+
+- Automatically upgrade MogDB
+
+  ```
+  gs_upgradectl -t auto-upgrade -X XMLFILE  [-l LOGFILE] [--grey]
+  ```
+
+- Automatically roll back the upgrade.
+
+  ```
+  gs_upgradectl -t auto-rollback -X XMLFILE [-l LOGFILE] [--force]
+  ```
+
+- Submit the upgrade project.
+
+  ```
+  gs_upgradectl -t commit-upgrade -X XMLFILE [-l LOGFILE]
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > - Once the operation is complete, the rollback operation cannot be performed.
+
+## Parameter Description
+
+- -t
+
+  Specifies the **gs_upgradectl** command type.
+
+  Valid value: chose-strategy, auto-upgrade, auto-rollback, and commit-upgrade
+
+- -l
+
+  Records log information during the upgrade or rollback.
+
+  Value range: any existing absolute path that can be accessed
+
+  Default value: **/var/log/gaussdb/***User name***/om/gs_upgradectl-YYYY-MM-DD_hhmmss.log**
+
+- -?, -help
+
+  Displays help information.
+
+- -V, -version
+
+  Displays version information.
+
+- -X
+
+  Specifies the MogDB configuration file.
+
+  Value range: storage paths of XML files
+
+- -grey
+
+  Perform gray upgrade.
+
+- -force
+
+  If MogDB is abnormal and does not support normal rollback, use this parameter to perform a forcible rollback.
+
+## Examples
+
+Example 1: Use the new package to perform pre-upgrade operations.
+
+```
+./gs_preinstall -U roach -G users -X /data/xml/3node_3c3d_1m2s_etcd.xml
+Parsing the configuration file.
+Successfully parsed the configuration file.
+Installing the tools on the local node.
+Successfully installed the tools on the local node.
+Setting pssh path
+Successfully set core path.
+Distributing package.
+Begin to distribute package to tool path.
+Successfully distribute package to tool path.
+Begin to distribute package to package path.
+Successfully distribute package to package path.
+Successfully distributed package.
+Installing the tools in the cluster.
+Successfully installed the tools in the cluster.
+Checking hostname mapping.
+Successfully checked hostname mapping.
+Checking OS version.
+Successfully checked OS version.
+Creating cluster's path.
+Successfully created cluster's path.
+Set and check OS parameter.
+Setting OS parameters.
+Successfully set OS parameters.
+Set and check OS parameter completed.
+Preparing CRON service.
+Successfully prepared CRON service.
+Preparing SSH service.
+Successfully prepared SSH service.
+Setting user environmental variables.
+Successfully set user environmental variables.
+Configuring alarms on the cluster nodes.
+Successfully configured alarms on the cluster nodes.
+Setting the dynamic link library.
+Successfully set the dynamic link library.
+Setting pssh path
+Successfully set pssh path.
+Setting Cgroup.
+Successfully set Cgroup.
+Set ARM Optimization.
+Successfully set ARM Optimization.
+Preinstalling secbox.
+Successfully installed secbox.
+Setting finish flag.
+Successfully set finish flag.
+Preinstallation succeeded.
+```
+
+Example 2: Execute the **gs_upgradectl** script to perform the upgrade.
+
+```
+gs_upgradectl -t upgrade -X /data/xml/3node_3c3d_1m2s_etcd.xml
+Static configuration matched with old static configuration files.
+Performing inplace rollback.
+Rollback succeeded.
+Checking upgrade environment.
+Successfully checked upgrade environment.
+Successfully checked upgrade environment.
+Successfully started cluster.
+Start to do health check.
+Successfully checked cluster status.
+Backing up current application and configurations.
+Successfully backed up current application and configurations.
+Stopping the cluster.
+Successfully stopped cluster.
+Backing up cluster configuration.
+Successfully backup hotpatch config file.
+Successfully backed up cluster configuration.
+Installing new binary.
+Restoring cluster configuration.
+Successfully restored cluster configuration.
+Modifying the socket path.
+Successfully modified socket path.
+Switch symbolic link to new binary directory.
+Successfully switch symbolic link to new binary directory.
+Successfully started cluster.
+Start to do health check.
+Successfully checked cluster status.
+Upgrade main process has been finished, user can do some check now.
+Once the check done, please execute following command to commit upgrade:
+
+    gs_upgradectl -t commit-upgrade -X /data/xml/3node_3c3d_1m2s_etcd.xml
+```
+
+Example 3: Execute the **gs_upgradectl** script to perform automatic rollback on the upgrade.
+
+```
+gs_upgradectl -t rollback -X /data/xml/3node_3c3d_1m2s_etcd.xml
+Static configuration matched with old static configuration files.
+Performing inplace rollback.
+Checking static configuration files.
+Successfully checked static configuration files.
+Restoring cluster configuration.
+Successfully rollback hotpatch config file.
+Successfully restored cluster configuration.
+Switch symbolic link to old binary directory.
+Successfully switch symbolic link to old binary directory.
+Stopping the cluster.
+Successfully stopped cluster.
+Restoring application and configurations.
+Successfully restored application and configuration.
+Restoring cluster configuration.
+Successfully rollback hotpatch config file.
+Successfully restored cluster configuration.
+Successfully started cluster.
+Successfully cleaned new install path.
+Rollback succeeded.
+```
+
+Example 4: Execute the **gs_upgradectl** script to submit the upgrade in in-place mode.
+
+```
+gs_upgradectl -t commit -X /data/xml/3node_3c3d_1m2s_etcd.xml
+Old cluster app path is /data/gauss/app_e67b8bcd
+Successfully Cleaned old install path.
+Commit binary upgrade succeeded.
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/13-gs_expansion.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/13-gs_expansion.md
new file mode 100644
index 0000000000000000000000000000000000000000..6418410e563c4a101d1388a7614f3a4b8c6f457a
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/13-gs_expansion.md
@@ -0,0 +1,164 @@
+---
+title: gs_expansion
+summary: gs_expansion
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_expansion
+
+## Background
+
+MogDB provides the **gs_expansion** tool to scale out the standby database node. A standalone node or a node with one primary and multiple standbys can be scaled to a node with one primary and four standbys.
+
+## Precautions
+
+- The parameter **synchronous_standby_names** will not automatically be updated after expansion. If you add a standby node for this parameter, please update manually after expansion.
+- Before expanding a cascade_standby, it is necessary to ensure that there has been already standby in Normal state in the same AZ(Available Zone) as the cascade_standby in current cluster, or that standby in the same AZ as the cascade_standby is being expanding at the same time.
+- Before scaling out the database cluster, you need to pay attention to the CPU, I/O, and network conditions of the primary node and new nodes. You are not advised to perform scale-out when the hardware load is heavy. Otherwise, the scale-out may take a long time or even fail.
+- If the original cluster contains a large amount of data, run the checkpoint on the primary node before the scale-out. Otherwise, the scale-out may take a long time or even fail.
+
+## Prerequisites
+
+- The MogDB image package exists on the database host and is decompressed. The capacity is scaled out by running the **./gs_expansion** command in the **script/** directory.
+- The same users and user groups as those on the primary node have been created on the new standby node.
+- The mutual trust of user **root** and the database management user **omm** has been established between the existing database nodes and the new nodes.
+- The XML file has been created correctly and information about the standby node to be scaled has been added to the installed database configuration file.
+- Only user **root** is authorized to run the **gs_expansion** command.
+- Do not run **gs_dropnode** command on the primary node at the same time.
+- The environment variables of the primary database node have been imported before the scale-out command is run. If the current database cluster is installed in a separate environment variable mode, run the **source** command to imports the spilt environment variable. If they are not spilt, run the **source** command to import the **.bashrc** configuration file of the sub-user. Generally, the file path is: **/home/[user]/.bashrc**.
+- The operating system of the new standby node is the same as that of the primary node.
+- Do not perform an primary/standby switchover or failover on other standby nodes at the same time.
+- Do not run **gs_expansion** command with same parameters at the same time.
+- Perform standby node expansion only on the primary node.
+
+## Syntax
+
+- Scale out the standby node.
+
+  ```
+  ./gs_expansion -U USER -G GROUP -X XMLFILE -h hostlist [-L]
+  ```
+
+- Show help information.
+
+  ```
+  ./gs_expansion -? | --help
+  ```
+
+- Show version information.
+
+  ```
+  ./gs_expansion -V | --version
+  ```
+
+## Description
+
+- -U
+
+  Specifies the OS username of MogDB.
+
+  The user name of the new standby node must be the same as that of the primary node where the database has been installed and must be created in advance.
+
+- -G
+
+  Specifies the OS user group of MogDB.
+
+  The user group of the new standby node must be the same as that of the primary node where the database has been installed.
+
+- -X
+
+  Specifies the path of the MogDB configuration file.
+
+  Value range: storage paths of XML files. The XML file must contain the configuration information about the installed database and all nodes of the new database.
+
+- -h
+
+  Specifies the IP address of the standby node to be scaled.
+
+  The value must be the same as the value of **backip** in the XML configuration file. If there are multiple nodes, use commas (,) to separate them.
+
+- -L
+
+  If the standalone database has been installed on the node to be scaled, skip the step of installing the database on the new standby node and directly establish the primary/standby relationship by adding the **-L** parameter during scaling.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > - The databases installed on the primary and standby nodes must use the same user and user group, and the paths for separating environment variables must be the same.
+  > - When the primary and standby nodes are installed, the values of **gaussdbAppPath**, **gaussdbLogPath**, **gaussdbToolPath**, and **corePath** in the XML configuration file must be the same.
+  > - The data on the scaled standby node must be installed in om mode. The database started in compilation mode does not support scaling out with the primary node.
+  > - The database version of new instance need to be same as the primary instance.
+
+- -?, -help
+
+  Shows help information.
+
+- -V, -version
+
+  Shows version information.
+
+## Examples
+
+Use **gs_expansion** for scaling:
+
+```
+[root@MogDB173 script]# ./gs_expansion -U gsexpa -G xuemn -X /home/gsexpa/cas.xml -h 90.90.44.171
+Start to preinstall database on new nodes.
+Start to send soft to each standby nodes.
+End to send soft to each standby nodes.
+Start to preinstall database step.
+Preinstall 90.90.44.171 success
+End to preinstall database step.
+End to preinstall database on new nodes.
+
+Start to install database on new nodes.
+Installing database on node 90.90.44.171:
+Please enter the password of user [gsexpa] on node [90.90.44.171]:
+Parsing the configuration file.
+Check preinstall on every node.
+Successfully checked preinstall on every node.
+Creating the backup directory.
+Successfully created the backup directory.
+begin deploy..
+Installing the cluster.
+begin prepare Install Cluster..
+Checking the installation environment on all nodes.
+begin install Cluster..
+Installing applications on all nodes.
+Successfully installed APP.
+begin init Instance..
+encrypt cipher and rand files for database.
+Please enter password for database:
+Please repeat for database:
+begin to create CA cert files
+The sslcert will be generated in /data/gsexpa/mogdb/cluster/app/share/sslcert/om
+Cluster installation is completed.
+Configuring.
+Deleting instances from all nodes.
+Successfully deleted instances from all nodes.
+Checking node configuration on all nodes.
+Initializing instances on all nodes.
+Updating instance configuration on all nodes.
+Check consistence of memCheck and coresCheck on database nodes.
+Configuring pg_hba on all nodes.
+Configuration is completed.
+Successfully started cluster.
+Successfully installed application.
+end deploy..
+90.90.44.171 install success.
+Finish to install database on all nodes.
+Database on standby nodes installed finished.
+
+Checking gaussdb and gs_om version.
+End to check gaussdb and gs_om version.
+
+Start to establish the relationship.
+Start to build standby 90.90.44.171.
+Build standby 90.90.44.171 success.
+Start to generate and send cluster static file.
+End to generate and send cluster static file.
+
+Expansion results:
+90.90.44.171:   Success
+Expansion Finish.
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/14-gs_dropnode.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/14-gs_dropnode.md
new file mode 100644
index 0000000000000000000000000000000000000000..c43eb988ec8a020acd3f58eecbb9048e23b4800b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/14-gs_dropnode.md
@@ -0,0 +1,129 @@
+---
+title: gs_dropnode
+summary: gs_dropnode
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_dropnode
+
+## Background
+
+**gs_dropnode**, provided by MogDB, is used to drop unnecessary standby nodes from a database with one primary node and multiple standby nodes. You can delete unnecessary standby nodes until only the primary node is left.
+
+## Precautions
+
+- When a standby database instance that can be connected is removed, the database service running on this standby database instance is automatically stopped, and the GRPC certificate (stored in *$GAUSSHOME***/share/sslcert/grpc/**) on the standby database instance is automatically deleted. However, the applications on the standby database instance are not deleted.
+
+- If only one primary node is left in the database after the deletion, the system prompts you to restart the current node. In this case, you are advised to restart the node based on the service operating environment.
+
+- If the target standby database instance cannot be connected before the operation, you need to manually stop or delete the database service on the database instance after it is restored, and delete the GRPC certificate (stored in *$GAUSSHOME***/share/sslcert/grpc/**) from the standby database instance.
+
+- The standby node can be dropped only from the primary/standby database installed in OM mode. The database installed in compilation mode is not supported.
+
+- If the standby node to be removed is in synchronous replication mode and a transaction is being performed on the primary node when the deletion command is executed, the transaction submission will be suspended for a short period of time. After the deletion is complete, the transaction processing can continue.
+
+- After the target standby node is removed, if you are not sure whether the target standby node is required anymore, use the following method to reject the remote connection through SSH from the target standby node to avoid misoperations:
+
+  - On the current primary node, modify the **/etc/ssh/sshd_config** file as user **root** and add the following record. If a DenyUsers record exists, append the following record after the existing one.
+
+    ```
+    `DenyUsers omm@10.11.12.13`
+    ```
+
+    After the modification, you need to restart the SSH service for the modification to take effect. After the modification, user **omm** cannot remotely log in to the primary node from the target standby node.
+
+  - On the current primary node, add the target standby node to the **/etc/hosts.deny** file (for example, **sshd:10.11.12.13:deny**) to reject the remote connection through SSH from the target standby node (valid for all users). This method requires that the sshd service be bound to the libwrap library.
+
+- After the target standby node is removed and is no longer required, run the **gs_uninstall -delete-data -L** command on the target standby node to uninstall MogDB. Note that the **-L** option must be added.
+
+## Prerequisite
+
+- Perform standby node deletion only on the primary node.
+- Do not perform an primary/standby switchover or failover on other standby nodes at the same time.
+- Do not run the **gs_expansion** command on the primary node for scale-out at the same time.
+- Do not run the **gs_dropnode** command twice at the same time.
+- Before deletion, ensure that the database management user **omm** trust relationship has been established between the primary and standby nodes.
+- Run this command as a database administrator, for example, **omm**.
+- Before running commands, run the **source** command to import environment variables of a database on the primary node. If the database is installed in separate environment variable mode, run the **source** command to import the separate environment variables. If they are not separated, run the **source** command to import the .bashrc configuration file of the sub-user. Generally, the file path is **/home/[user]/.bashrc**.
+
+## Syntax
+
+- Drop a standby node.
+
+  ```
+  gs_dropnode -U USER -G GROUP -h hostlist
+  ```
+
+- Display help information.
+
+  ```
+  gs_dropnode -? | --help
+  ```
+
+- Display version information.
+
+  ```
+  gs_dropnode -V | --version
+  ```
+
+## Parameter Description
+
+- -U
+
+  Specifies the OS username of MogDB.
+
+- -G
+
+  Specifies the OS user group of MogDB.
+
+- -h
+
+  Specifies IP address of the standby node to be dropped. If there are multiple nodes, use commas (,) to separate them.
+
+- -?, -help
+
+  Displays help information.
+
+- -V, -version
+
+  Displays version information.
+
+## Example
+
+Use **gs_dropnode** to drop nodes.
+
+```
+gs_dropnode -U omm -G dbgrp -h 10.11.12.13
+The target node to be dropped is (['StandbyNode1'])
+Do you want to continue to drop the target node (yes/no)? yes
+[gs_dropnode]Start to drop nodes of the cluster.
+[gs_dropnode]Start to stop the target node StandbyNode3.
+[gs_dropnode]End of stop the target node StandbyNode3.
+[gs_dropnode]Start to backup parameter config file on PrimaryNode.
+[gs_dropnode]End to backup parameter config file on PrimaryNode.
+[gs_dropnode]The backup file of PrimaryNode is /tmp/gs_dropnode_backup20201119205019/parameter_PrimaryNode.tar
+[gs_dropnode]Start to parse parameter config file on PrimaryNode.
+[gs_dropnode]End to parse parameter config file on PrimaryNode.
+[gs_dropnode]Start to parse backup parameter config file on PrimaryNode.
+[gs_dropnode]End to parse backup parameter config file on PrimaryNode.
+[gs_dropnode]Start to set postgresql config file on PrimaryNode.
+[gs_dropnode]End of set postgresql config file on PrimaryNode.
+[gs_dropnode]Start to backup parameter config file on StandbyNode2.
+[gs_dropnode]End to backup parameter config file on StandbyNode2.
+[gs_dropnode]The backup file of StandbyNode2 is /tmp/gs_dropnode_backup20201119205019/parameter_StandbyNode2.tar
+[gs_dropnode]Start to parse parameter config file on StandbyNode2.
+[gs_dropnode]End to parse parameter config file on StandbyNode2.
+[gs_dropnode]Start to parse backup parameter config file on StandbyNode2.
+[gs_dropnode]End to parse backup parameter config file on StandbyNode2.
+[gs_dropnode]Start to set postgresql config file on StandbyNode2.
+[gs_dropnode]End of set postgresql config file on StandbyNode2.
+[gs_dropnode]Start to get repl slot on PrimaryNode.
+[gs_dropnode]Start to set repl slot on PrimaryNode.
+[gs_dropnode]End of set repl slot on PrimaryNode.
+[gs_dropnode]Start to set pg_hba config file on PrimaryNode.
+[gs_dropnode]End of set pg_hba config file on PrimaryNode.
+[gs_dropnode]Start to modify the cluster static conf.
+[gs_dropnode]End of modify the cluster static conf.
+[gs_dropnode]Success to drop the target nodes.
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/15-gs_probackup.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/15-gs_probackup.md
new file mode 100644
index 0000000000000000000000000000000000000000..fc2c0b2847dc710b9331a6cf12bbb7e6fc5dc840
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/15-gs_probackup.md
@@ -0,0 +1,624 @@
+---
+title: gs_probackup
+summary: gs_probackup
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_probackup
+
+## Background
+
+**gs_probackup** is a tool used to manage MogDB database backup and restoration. It periodically backs up the MogDB instances so that the server can be restored when the database is faulty.
+
+- It supports the physical backup of a standalone database or a primary node in a database.
+- It supports the backup of contents in external directories, such as script files, configuration files, log files, and dump files.
+- It supports incremental backup, periodic backup, and remote backup.
+- It supports settings on the backup retention policy.
+
+## Prerequisites
+
+- The MogDB database can be connected.
+- To use PTRACK incremental backup, manually add **enable_cbm_tracking = on** to **postgresql.conf**.
+- In order to prevent the xlog from being cleaned up before the end of the transfer, please increase the value of wal_keep_segements in the postgresql.conf file appropriately.
+
+## Important Notes
+
+- The backup must be performed by the user who runs the database server.
+- The major version number of the database server to be backed up must be the same as that of the database server to be restored.
+- To back up a database in remote mode using SSH, install the database of the same major version on the local and remote hosts, and run the **ssh-copy-id remote_user@remote_host** command to set an SSH connection without a password between the local host backup user and the remote host database user.
+- In remote mode, only the subcommands **add-instance**, **backup**, and **restore** can be executed.
+- Before running the **restore** subcommand, stop the gaussdb process.
+- If a user-defined tablespace exists, add the **-external-dirs** parameter when backing up the tablespace. Otherwise, the tablespace will not be backed up.
+- If a large amount of data needs to be backed up, adjust the values of **session_timeout** and **wal_sender_timeout** in the **postgresql.conf** file to prevent backup timeout. In addition, adjust the value of **-rw-timeout** in the backup command line parameters.
+- When using the **-T** option to redirect the external directory in the backup to a new directory during restoration, specify the **-external-mapping** parameter.
+- After an incremental backup is restored, the created logical replication slot is unavailable and needs to be deleted and recreated.
+
+## Command Description
+
+- Print the **gs_probackup** version.
+
+  ```bash
+  gs_probackup -V|--version
+  gs_probackup version
+  ```
+
+- Display brief information about the **gs_probackup** command. Alternatively, display details about parameters of a specified subcommand of **gs_probackup**.
+
+  ```bash
+  gs_probackup -?|--help
+  gs_probackup help [command]
+  ```
+
+- Initialize the backup directory in **backup-path**. The backup directory stores the contents that have been backed up. If the **backup-path** backup path exists, it must be empty.
+
+  ```bash
+  gs_probackup init -B backup-path [--help]
+  ```
+
+- Initialize a new backup instance in the backup directory of **backup-path** and generate the **pg_probackup.conf** configuration file, which saves the **gs_probackup**settings of the specified data directory **pgdata-path**.
+
+  ```bash
+  gs_probackup add-instance -B backup-path -D pgdata-path --instance=instance_name
+  [-E external-directories-paths]
+  [remote_options]
+  [--help]
+  ```
+
+- Delete the backup content related to the specified instance from the **backup-path** directory.
+
+  ```bash
+  gs_probackup del-instance -B backup-path --instance=instance_name
+  [--help]
+  ```
+
+- Add the specified connection, compression, and log-related settings to the **pg_probackup.conf** configuration file or modify the existing settings. You are not advised to manually edit the **pg_probackup.conf** configuration file.
+
+  ```bash
+  gs_probackup set-config -B backup-path --instance=instance_name
+  [-D pgdata-path] [-E external-directories-paths] [--archive-timeout=timeout]
+  [--retention-redundancy=retention-redundancy] [--retention-window=retention-window] [--wal-depth=wal-depth]
+  [--compress-algorithm=compress-algorithm] [--compress-level=compress-level]
+  [-d dbname] [-h hostname] [-p port] [-U username]
+  [logging_options] [remote_options]
+  [--help]
+  ```
+
+- Add the backup-related settings to the **backup.control** configuration file or modify the settings.
+
+  ```bash
+  gs_probackup set-backup -B backup-path --instance=instance_name -i backup-id
+  [--note=text] [pinning_options]
+  [--help]
+  ```
+
+- Display the content of the **pg_probackup.conf** configuration file in the backup directory. You can specify **-format=json** to display the information in JSON format. By default, the plain text format is used.
+
+  ```bash
+  gs_probackup show-config -B backup-path --instance=instance_name
+  [--format=plain|json]
+  [--help]
+  ```
+
+- Display the contents of the backup directory. If **instance_name** and **backup_id** are specified, detailed information about the backup is displayed. You can specify **-format=json** to display the information in JSON format. By default, the plain text format is used.
+
+  ```bash
+  gs_probackup show -B backup-path
+  [--instance=instance_name [-i backup-id]] [--archive] [--format=plain|json]
+  [--help]
+  ```
+
+- Create a backup for a specified database instance.
+
+  ```bash
+  gs_probackup backup -B backup-path --instance=instance_name -b backup-mode
+  [-D pgdata-path] [-C] [-S slot-name] [--temp-slot] [--backup-pg-log] [-j threads_num] [--progress]
+  [--no-validate] [--skip-block-validation] [-E external-directories-paths] [--no-sync] [--note=text]
+  [--archive-timeout=timeout] [-t rwtimeout]
+  [logging_options] [retention_options] [compression_options]
+  [connection_options] [remote_options] [pinning_options]
+  [--help]
+  ```
+
+- Restore a specified instance from the backup copy in the **backup-path** directory. If an instance to be restored is specified, **gs_probackup** will look for its latest backup and restore it to the specified recovery objective. Otherwise, the latest backup of any instance is used.
+
+  ```bash
+  gs_probackup restore -B backup-path --instance=instance_name
+  [-D pgdata-path] [-i backup_id] [-j threads_num] [--progress] [--force] [--no-sync] [--no-validate] [--skip-block-validation]
+  [--external-mapping=OLDDIR=NEWDIR] [-T OLDDIR=NEWDIR] [--skip-external-dirs] [-I incremental_mode]
+  [recovery_options] [remote_options] [logging_options]
+  [--help]
+  ```
+
+- Merge all incremental backups between the specified incremental backup and its parent full backup into the parent full backup. The parent full backup will receive all merged data, while the merged incremental backup will be deleted as redundancy.
+
+  ```bash
+  gs_probackup merge -B backup-path --instance=instance_name -i backup_id
+  [-j threads_num] [--progress] [logging_options]
+  [--help]
+  ```
+
+- Delete a specified backup or delete backups that do not meet the current retention policy.
+
+  ```bash
+  gs_probackup delete -B backup-path --instance=instance_name
+  [-i backup-id | --delete-expired | --merge-expired | --status=backup_status]
+  [--delete-wal] [-j threads_num] [--progress]
+  [--retention-redundancy=retention-redundancy] [--retention-window=retention-window]
+  [--wal-depth=wal-depth] [--dry-run]
+  [logging_options]
+  [--help]
+  ```
+
+- Verify that all files required for restoring the database exist and are not damaged. If **instance_name**is not specified, **gs_probackup**verifies all available backups in the backup directory. If **instance_name**is specified and no additional options are specified, **gs_probackup**verifies all available backups for this backup instance. If both **instance_name** and **backup-id**or recovery objective-related options are specified, **gs_probackup**checks whether these options can be used to restore the database.
+
+  ```bash
+  gs_probackup validate -B backup-path
+  [--instance=instance_name] [-i backup-id]
+  [-j threads_num] [--progress] [--skip-block-validation]
+  [--recovery-target-time=time | --recovery-target-xid=xid | --recovery-target-lsn=lsn | --recovery-target-name=target-name]
+  [--recovery-target-inclusive=boolean]
+  [logging_options]
+  [--help]
+  ```
+
+## Parameter Description
+
+**Common parameters**
+
+- command
+
+  Specifies subcommands except **version** and **help**: **init**, **add-instance**, **del-instance**, **set-config**, **set-backup**, **show-config**, **show**, **backup**, **restore**, **merge**, **delete**, and **validate**.
+
+- -?, -help
+
+  Displays help information about the command line parameters of **gs_probackup** and exits.
+
+  Only **-help** can be used in subcommands; **-?** is forbidden.
+
+- -V, -version
+
+  Prints the **gs_probackup** version and exits.
+
+- -B *backup-path*, -backup-path=*backup-path*
+
+  Backup path.
+
+  System environment variable: *$BACKUP_PATH*
+
+- -D *pgdata-path*, -pgdata=*pgdata-path*
+
+  Path of the data directory.
+
+  System environment variable: *$PGDATA*
+
+- -instance=*instance_name*
+
+  Instance name.
+
+- -i *backup-id*, -backup-id=*backup-id*
+
+  Unique identifier of a backup.
+
+- -format=*format*
+
+  Specifies format of the backup information to be displayed. The plain and JSON formats are supported.
+
+  Default value: **plain**
+
+- -status=*backup_status*
+
+  Deletes all backups in a specified state. The states are as follows:
+
+  - **OK**: Backup is complete and valid.
+  - **DONE**: Backup has been completed but not verified.
+  - **RUNNING**: Backup is in progress.
+  - **MERGING**: Backups are being merged.
+  - **DELETING**: Backup is being deleted.
+  - **CORRUPT**: Some backup files are damaged.
+  - **ERROR**: Backup fails due to an unexpected error.
+  - **ORPHAN**: Backup is invalid because one of its parent backups is corrupted or lost.
+
+- -j *threads_num*, -threads=*threads_num*
+
+  Sets the number of concurrent threads for the backup, restoration, and combination processes.
+
+- -archive
+
+  Displays WAL archiving information.
+
+- -progress
+
+  Displays progress.
+
+- -note=*text*
+
+  Adds a note to the backup.
+
+**Backup-related parameters**
+
+- -b *backup-mode*, -backup-mode=*backup-mode*
+
+  Specifies the backup mode. The value can be **FULL** or **PTRACK**.
+
+  **FULL**: creates a full backup. The full backup contains all data files.
+
+  **PTRACK**: creates a PTRACK incremental backup.
+
+- -C, -smooth-checkpoint
+
+  Expands checkpoints within a period of time. By default, **gs_probackup** attempts to complete checkpoints as soon as possible.
+
+- -S *slot-name*, -slot=*slot-name*
+
+  Specifies the replication slot for WAL stream processing.
+
+- -temp-slot
+
+  Creates a temporary physical replication slot for WAL stream processing in the backup instance to ensure that all required WAL segments are still available during the backup.
+
+  The default slot name is **pg_probackup_slot**, which can be changed using the **-slot/-S** option.
+
+- -backup-pg-log
+
+  Includes the log directory in the backup. This directory typically contains log messages. By default, the log directory is included, but the log file is not included. If the default log path is changed, you can use the **-E** parameter to back up log files. The following describes how to use the **-E** parameter.
+
+- -E *external-directories-paths*, -external-dirs=*external-directories-paths*
+
+  Includes the specified directory in the backup. This option is useful for backing up scripts in external data directories, sql dumps, and configuration files. To back up multiple external directories, use colons (:) to separate their paths in Unix.
+
+  Example: -E /tmp/dir1:/tmp/dir2
+
+- -skip-block-validation
+
+  Disables block-level verification to speed up backup.
+
+- -no-validate
+
+  Skips the automatic verification when the backup is complete.
+
+- -no-sync
+
+  Disables backup file synchronization to the disk.
+
+- -archive-timeout=*timeout*
+
+  Specifies timeout interval for streaming processing, in seconds.
+
+  Default value: **300**
+
+- -t rwtimeout
+
+  Specifies timeout interval for a connection, in seconds.
+
+  Default value: **120**
+
+**Restoration-related parameters**
+
+- -I, -incremental-mode=none|checksum|lsn
+
+  Reuses the valid pages available in PGDATA if they are not modified.
+
+  Default value: **none**
+
+- -external-mapping=*OLDDIR=NEWDIR*
+
+  During restoration, the external directory contained in the backup is moved from **OLDDIR** to **NEWDIR**. **OLDDIR** and **NEWDIR** must be absolute paths. If the path contains an equal sign (=), use a backslash () to escape. This option can be specified for multiple directories.
+
+- -T *OLDDIR=NEWDIR*, -tablespace-mapping=*OLDDIR=NEWDIR*
+
+  Relocates the tablespace from the **OLDDIR** directory to the **NEWDIR** directory during the restoration. **OLDDIR** and **NEWDIR** must be absolute paths. If the path contains an equal sign (=), use a backslash () to escape. This parameter can be specified multiple times for multiple tablespaces. This parameter must be used together with **-external-mapping**.
+
+- -skip-external-dirs
+
+  Skips the external directories in the backup that are specified using the **-external-dirs** option. The contents of these directories will not be restored.
+
+- -skip-block-validation
+
+  Skips block-level verification to speed up verification. During the automatic verification before the restoration, only file-level verification is performed.
+
+- -no-validate
+
+  Skips the backup verification.
+
+- -force
+
+  Specifies the invalid state that allows ignoring backup. This flag can be used if data needs to be restored from a damaged or invalid backup. Exercise caution when using it.
+
+**Recovery objective-related parameters (recovery_options)**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** Currently, continuous WAL archiving PITR cannot be configured. Therefore, parameter usage is restricted as follows: To use continuously archived WAL logs for PITR, perform the following steps: 1. Replace the target database directory with the physical backup files. 2. Delete all files in the database directory **pg_xlog/**. 3. Copy the archived WAL log file to the **pg_xlog** file. (Or you can configure **restore_command** in the **recovery.conf** file to skip this step.) 4. Create the **recovery.conf** file in the database directory and specify the database restoration degree. 5. Start the database. 6. Connect to the database and check whether the database is recovered to the expected status. If the expected status is reached, run the **pg_xlog_replay_resume()** command so that the primary node can provide services externally.
+
+- -recovery-target-lsn=*lsn*
+
+  Specifies LSN to be restored. Currently, only the backup stop LSN can be specified.
+
+- -recovery-target-name=*target-name*
+
+  Specifies named savepoint to which data is restored. You can obtain the savepoint by viewing the recovery-name column in the backup.
+
+- -recovery-target-time=*time*
+
+  Specifies time to which data is restored. Currently, only recovery-time can be specified.
+
+- -recovery-target-xid=*xid*
+
+  Specifies transaction ID to which data is restored. Currently, only recovery-xid can be specified.
+
+- -recovery-target-inclusive=*boolean*
+
+  When this parameter is set to **true**, the recovery objective will include the specified content.
+
+  When this parameter is set to **false**, the recovery objective will not include the specified content.
+
+  This parameter must be used together with **-recovery-target-name**, **-recovery-target-time**, **-recovery-target-lsn**, or **-recovery-target-xid**.
+
+**Retention-related parameters (retention_options)**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The following parameters can be used together with the **backup** and **delete** commands.
+
+- -retention-redundancy=*retention-redundancy*
+
+  Number of full backups retained in the data directory. The value must be a positive integer. The value **0** indicates that the setting is disabled.
+
+  Default value: **0**
+
+- -retention-window=*retention-window*
+
+  Specifies the retention period. The value must be a positive integer. The value **0** indicates that the setting is disabled.
+
+  Default value: **0**
+
+- -wal-depth=*wal-depth*
+
+  Latest number of valid backups that must be retained on each timeline to perform the PITR capability. The value must be a positive integer. The value **0** indicates that the setting is disabled.
+
+  Default value: **0**
+
+- -delete-wal
+
+  Deletes unnecessary WAL files from any existing backup.
+
+- -delete-expired
+
+  Deletes the backups that do not comply with the retention policy defined in the **pg_probackup.conf** configuration file.
+
+- -merge-expired
+
+  Merges the oldest incremental backup that meets the retention policy requirements with its expired parent backup.
+
+- -dry-run
+
+  Displays the status of all available backups. Expired backups will not be deleted or merged.
+
+**Fixed backup-related parameters (pinning_options)**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** To exclude certain backups from the established retention policy, you can use the following parameters with the **backup** and **set-backup** commands.
+
+- -ttl=*interval*
+
+  Specifies a fixed amount of time to back up data from the restoration time. The value must be a positive integer. The value **0** indicates that the backup is canceled.
+
+  Supported unit: ms, s, min, h, d (default value: **s**)
+
+  For example, **-ttl=30d**.
+
+- -expire-time=*time*
+
+  Specifies the timestamp when the backup is invalid. The time stamp must comply with the ISO-8601 standard.
+
+  For example, **-expire-time='2020-01-01 00:00:00+03'**.
+
+**Log-related parameters (logging_options)**
+
+Log levels: **verbose**, **log**, **info**, **warning**, **error**, and **off**.
+
+- -log-level-console=*log-level-console*
+
+  Sets the level of logs to be sent to the console. Each level contains all the levels following it. A higher level indicates fewer messages sent. If this parameter is set to **off**, the log recording function of the console is disabled.
+
+  Default value: **info**
+
+- -log-level-file=*log-level-file*
+
+  Sets the level of logs to be sent to the log file. Each level contains all the levels following it. A higher level indicates fewer messages sent. If this parameter is set to **off**, the log file recording function is disabled.
+
+  Default value: **off**
+
+- -log-filename=*log-filename*
+
+  Specifies the name of the log file to be created. The file name can use the strftime mode. Therefore, **%-escapes** can be used to specify the file name that changes with time.
+
+  For example, if the **pg_probackup-%u.log** mode is specified, pg_probackup generates a log file each day of the week, with **%u** replaced by the corresponding decimal number, that is, **pg_probackup-1.log**indicates Monday.**pg_probackup-2.log** indicates Tuesday, and so on.
+
+  This parameter is valid if the **-log-level-file** parameter is specified to enable log file recording.
+
+  Default value: **pg_probackup.log**
+
+- -error-log-filename=*error-log-filename*
+
+  Specifies the name of the log file that is used only for error logs. The specifying method is the same as that of the **-log-filename** parameter.
+
+  It is used for troubleshooting and monitoring.
+
+- -log-directory=*log-directory*
+
+  Specifies the directory where log files are created. The value must be an absolute path. This directory is created when the first log is written.
+
+  Default value: **$BACKUP_PATH/log**
+
+- -log-rotation-size=*log-rotation-size*
+
+  Specifies the maximum size of a log file. If the maximum size is reached, the log file will be circulated after the **gs_probackup** command is executed. The **help** and **version** commands will not lead to a log file circulation. The value **0** indicates that the file size-based loop is disabled.
+
+  The unit can be KB, MB, GB, or TB. The default unit is **KB**.
+
+  Default value: **0**
+
+- -log-rotation-age=*log-rotation-age*
+
+  Maximum life cycle of a log file. If the maximum size is reached, the log file will be circulated after the **gs_probackup** command is executed. The **help** and **version** commands will not lead to a log file circulation. The **$BACKUP_PATH/log/log_rotation** directory saves the time of the last created log file. The value **0** indicates that the time-based loop is disabled.
+
+  Supported unit: ms, s, min, h, d (default value: **min**)
+
+  Default value: **0**
+
+**Connection-related parameters (connection_options)**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The following parameters can be used together with the **backup** command.
+
+- -d *dbname*, -pgdatabase=*dbname*
+
+  Specifies the name of the database to connect to. This connection is only used to manage the backup process. Therefore, you can connect to any existing database. If this parameter is not specified in the command line, the *PGDATABASE* environment variable, or the **pg_probackup.conf** configuration file, **gs_probackup** attempts to obtain the value from the *PGUSER* environment variable. If the *PGUSER* variable is not set, the value is obtained from the current user name.
+
+  System environment variable: *$PGDATABASE*
+
+- -h *hostname*, -pghost=*hostname*
+
+  Specifies the host name of the system on which the server is running. If the value begins with a slash (/), it is used as the directory for the UNIX domain socket.
+
+  System environment variable: *$PGHOST*
+
+  Default value: **local socket**
+
+- -p *port*, -pgport=_p_*ort*
+
+  Specifies the TCP port or local Unix domain socket file name extension on which the server is listening for connections.
+
+  System environment variable: *$PGPORT*
+
+  Default value: **5432**
+
+- -U *username*, -pguser=*username*
+
+  Specifies the username of the host to be connected.
+
+  System environment variable: *$PGUSER*
+
+- -w, -no-password
+
+  Never issues a password prompt. The connection attempt fails if the host requires password verification and the password is not provided in other ways. This option is useful in batch jobs and scripts in which no user password is required.
+
+- -W *password*, -password=*password*
+
+  Specifies the user password for connection. If the host uses the trust authentication policy, the administrator does not need to enter the **-W** option. If the **-W** option is not provided and you are not a system administrator, the system will ask you to enter a password.
+
+**Compression-related parameters (compression_options)**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The following parameters can be used together with the **backup** command.
+
+- -compress-algorithm=*compress-algorithm*
+
+  Specifies the algorithm used to compress data file.
+
+  The value can be **zlib**, **pglz**, or **none**. If **zlib** or **pglz** is set, compression is enabled. By default, the compression function is disabled.
+
+  Default value: **none**
+
+- -compress-level=*compress-level*
+
+  Specifies the compression level. Value range: 0-9
+
+  - **0** indicates no compression.
+  - **1** indicates that the compression ratio is the lowest and processing speed the fastest.
+  - **9** indicates that the compression ratio is the highest and processing speed the slowest.
+  - This parameter can be used together with **-compress-algorithm**.
+
+  Default value: **1**
+
+- -compress
+
+  Compresses with **-compress-algorithm=zlib** and **-compress-level=1**.
+
+**Remote mode-related parameters (remote_options)**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The following are parameters that remotely run **gs_probackup** through SSH, and can be used together with the **add-instance**, **set-config**, **backup**, and **restore** commands.
+
+- -remote-proto=*protocol*
+
+  Specifies the protocol used for remote operations. Currently, only the SSH protocol is supported. Valid value:
+
+  **ssh**: enables the remote backup mode through SSH. This is the default.
+
+  **none**: The remote mode is disabled explicitly.
+
+  If **-remote-host** is specified, this parameter can be omitted.
+
+- -remote-host=*destination*
+
+  Specifies the IP address or host name of the remote host to be connected.
+
+- -remote-port=*port*
+
+  Specifies the port number of the remote host to be connected.
+
+  Default value: **22**
+
+- -remote-user=*username*
+
+  Specifies the remote host user for SSH connection. If this parameter is not specified, the user who initiates the SSH connection is used.
+
+  Default value: the current user.
+
+- -remote-path=*path*
+
+  Specifies the installation directory of **gs_probackup** in the remote system.
+
+  Default value: current path
+
+- -remote-lib=*libpath*
+
+  Specifies the lib directory where gs_probackup is installed in the remote system.
+
+- -ssh-options=*ssh_options*
+
+  Specifies the character string of the SSH command line parameter.
+
+  Example: -ssh-options='-c cipher_spec -F configfile'
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > - If the server does not respond due to a temporary network fault, **gs_probackup**will exit after waiting for *archive-timeout* seconds (300 seconds is set by default).
+  > - If the LSN of the standby server is different from that of the primary server, the database continuously updates the following log information. In this case, you need to rebuild the standby server.
+  >
+  > ```
+  > LOG: walsender thread shut down
+  > LOG: walsender thread started
+  > LOG: received wal replication command: IDENTIFY_VERSION
+  > LOG: received wal replication command: IDENTIFY_MODE
+  > LOG: received wal replication command: IDENTIFY_SYSTEM
+  > LOG: received wal replication command: IDENTIFY_CONSISTENCE 0/D0002D8
+  > LOG: remote request lsn/crc: [xxxxx] local max lsn/crc: [xxxxx]
+  > ```
+
+## Backup Process
+
+1. Initialize the backup directory. Create the **backups/** and **wal/** subdirectories in the specified directory to store backup files and WAL files respectively.
+
+   ```bash
+   gs_probackup init -B backup_dir
+   ```
+
+2. Add a new backup instance. **gs_probackup** can store backups of multiple database instances in the same backup directory.
+
+   ```bash
+   gs_probackup add-instance -B backup_dir -D data_dir --instance instance_name
+   ```
+
+3. Create a backup for a specified database instance. Before performing an incremental backup, you must create at least one full backup.
+
+   ```bash
+   gs_probackup backup -B backup_dir --instance instance_name -b backup_mode
+   ```
+
+4. Restore data from the backup of a specified instance.
+
+   ```bash
+   gs_probackup restore -B backup_dir --instance instance_name -D pgdata-path -i backup_id
+   ```
+
+## Troubleshooting
+
+| Problem Description                                          | Cause and Solution                                           |
+| :----------------------------------------------------------- | :----------------------------------------------------------- |
+| ERROR: query failed: ERROR: canceling statement due to conflict with recovery | **Cause**: The operation performed on the standby node is accessing the storage row. The corresponding row is modified or deleted on the primary node, and the Xlog is replayed on the standby node. As a result, the operation is canceled on the standby node.<br />Solution:<br />1. Increase the values of the following parameters:<br />max_standby_archive_delay<br />max_standby_streaming_delay<br />2. Add the following configuration item:<br />hot_standby_feedback = on |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/16-gstrace.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/16-gstrace.md
new file mode 100644
index 0000000000000000000000000000000000000000..b3afd6527c325295346401722646e5660131b626
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/16-gstrace.md
@@ -0,0 +1,98 @@
+---
+title: gstrace
+summary: gstrace
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gstrace
+
+## Function Description
+
+**gstrace**, provided by MogDB, is used to trace the kernel code execution path, record kernel data structure, and analyze code performance. The number of trace points and data are fixed in the version and cannot be dynamically added or deleted.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-warning.gif) **WARNING:**
+>
+> 1. The specified memory variables dumped from the kernel are used only for diagnosis and analysis. Registers or memory addresses will not be randomly and directly specified. The read memory addresses are hard-coded in the development, and no register or memory is read or modified randomly.
+> 2. Trace points may involve sensitive data. Before collecting information to be traced, you need to obtain authorization and permission from the customer.
+> 3. MogDB does not point on sensitive information or trace user-related data.
+> 4. The trace is used only for diagnosis. Enabling the trace function affects the performance, and the impact depends on the load and the modules to be traced.
+> 5. The permission of the trace tool is **0700**, which indicates that only database users can read, write, and execute the trace tool.
+>
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** If the process is stopped abnormally, the **gstrace_trace_cfg_*** file will exist in the **/dev/shm** directory. You can manually delete the file.
+
+## Syntax
+
+```
+gstrace [start|stop|config|dump|detailcodepath|analyze] [-p <port>][-s <BUFFER_SIZE>] [-f <DUMP_FILE>] [-o <OUTPUT_FILE>] [-t <STEP_SIZE>]
+```
+
+## Parameter Description
+
+**Table 1** gs_trace parameters
+
+| Parameter      | Description                                                  |
+| :------------- | :----------------------------------------------------------- |
+| start          | Starts tracing.                                              |
+| stop           | Stops tracing and releases the shared memory trace buffer. Note: This will cause the traced information in the trace buffer to be lost. |
+| config         | Displays configurations of the tracing tool.                 |
+| dump           | Writes the traced information frm the shared memory to a specified file. If the tracing is not started, an error message will be displayed. |
+| detail         | Parses the dumped binary file to a text file, so that traced threads and time information are displayed. |
+| codepath       | Extracts the function calling information from the dumped file and displays the information in the call stack mode. |
+| analyze        | Collects statistics on the number of execution times, total duration, average duration, maximum duration, and minimum duration of each function. |
+| -p PORT        | Specifies the listening port number of an instance on which the trace function is enabled. |
+| -f DUMP_FILE   | Specifies the trace file to be dumped.                       |
+| -o OUTPUT_FILE | Specifies the file to be written.                            |
+| -t STEP_SIZE   | Specifies the time span for segment analysis, in seconds. This parameter is optional. A separate *{OUTPUT_FILE}***.step** file will be generated. |
+| -m MASK        | Specifies the modules and functions to be traced. If this parameter is left blank, all functions of all modules with the **trace** interface added are traced.<br />Format: [comp…][ALL].[func…][ALL]<br />Description:<br />- **comp** indicates the module list, which is separated by commas (,). For example, **executer,opengauss**. You can also use a sequence number, for example, **executer,2**.<br />- **func** indicates a function list, which is separated by commas (,). For example, **sql_execute_ddl, sql_execute_dcl**. You can also use a sequence number to indicate the sequence number of a function in a module, for example, **2**.<br />- The value **ALL** indicates that all modules or functions are traced.<br />Examples:<br />- **executer,opengauss.ALL**: All functions defined in the executer and opengauss modules are traced.<br />- **executer,opengauss.sql_execute_ddl**: The **sql_execute_ddl** function defined in the executer is traced. The opengauss module is ignored because this function does not exist.<br />- **executer,opengauss.1**: The first functions in the executer and opengauss modules are traced.<br />**ALL.1,2**: The first and second functions in all modules are traced. |
+| -s BUFFER_SIZE | Specifies the size of the shared memory used for the trace function. The default value is 1 GB. If the specified value of BUFFER_SIZE is less than the minimum value 2048, the system automatically adjusts the value to the minimum value. If the value specified by BUFFER_SIZE is not 2^N (2 to the power of N), 2^N is aligned downwards. For example, if BUFFER_SIZE is set to 3072, the system changes the value to 2048 because 2^11 < 3072 < 2^12. |
+
+## Example
+
+1. Start the tracing.
+
+   ```bash
+   gstrace start -p 8000
+   ```
+
+2. Stop the tracing.
+
+   ```bash
+   gstrace stop -p 8000
+   ```
+
+3. Check the configurations for tracing.
+
+   ```bash
+   gstrace config -p 8000
+   ```
+
+4. dump trace
+
+   ```bash
+   gstrace dump -p 8000 -o /data/8000.dump
+   ```
+
+5. Parses dumped details.
+
+   ```bash
+   gstrace detail -f /data/8000.dump -o /data/8000.detail
+   ```
+
+6. Parse dumped codepath.
+
+   ```bash
+   gstrace codepath -f /data/8000.dump -o /data/8000.codepath
+   ```
+
+7. Analyze the global performance.
+
+   ```bash
+   gstrace analyze -f /data/8000.dump -o /data/8000.perf
+   ```
+
+8. Analyze the segment performance.
+
+   ```bash
+   gstrace analyze -f /data/8000.dump -o /data/8000.perf -t 1
+   ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/17-kdb5_util.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/17-kdb5_util.md
new file mode 100644
index 0000000000000000000000000000000000000000..44ec6c8a561440a2115401b2c29286f580b11aaa
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/17-kdb5_util.md
@@ -0,0 +1,16 @@
+---
+title: kdb5_util
+summary: kdb5_util
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# kdb5_util
+
+## Function
+
+**kdb5_util**, provided by the cluster authentication service Kerberos, is a database management tool used to create, destroy, import, and export databases.
+
+## Parameter Description
+
+The Kerberos tool is provided by an open-source third party. For details about the parameters, see the Kerberos official document at <https://web.mit.edu/kerberos/krb5-1.17/doc/admin/admin_commands/index.html>.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/18-kadmin-local.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/18-kadmin-local.md
new file mode 100644
index 0000000000000000000000000000000000000000..9bd2d640a2fe86a02f202ab19deb905853aab6ad
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/18-kadmin-local.md
@@ -0,0 +1,16 @@
+---
+title: kadmin.local
+summary: kadmin.local
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# kadmin.local
+
+## Function
+
+**kadmin.local**, provided by the cluster authentication service Kerberos, is used to directly access the **kdc** service database and perform operations such as adding, deleting, and modifying Kerberos users.
+
+## Parameter Description
+
+The Kerberos tool is provided by an open-source third party. For details about the parameters, see the Kerberos official document at <https://web.mit.edu/kerberos/krb5-1.17/doc/admin/admin_commands/index.html>.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/19-kinit.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/19-kinit.md
new file mode 100644
index 0000000000000000000000000000000000000000..7772d6cffbb15e1c4fee4fc4fdbf4f0204647dbe
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/19-kinit.md
@@ -0,0 +1,16 @@
+---
+title: kinit
+summary: kinit
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# kinit
+
+## Function
+
+**kinit**, provided by the cluster authentication service Kerberos, is used for specific users to obtain and cache TGT capabilities.
+
+## Parameter Description
+
+The Kerberos tool is provided by an open-source third party. For details about the parameters, see the Kerberos official document at <https://web.mit.edu/kerberos/krb5-1.17/doc/admin/admin_commands/index.html>.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/2-gs_backup.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/2-gs_backup.md
new file mode 100644
index 0000000000000000000000000000000000000000..d2463e1fadc9569ac042d4f38225d87a12e766a2
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/2-gs_backup.md
@@ -0,0 +1,150 @@
+---
+title: gs_backup
+summary: gs_backup
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_backup
+
+## Background
+
+After MogDB is deployed, problems and exceptions may occur during database running. **gs_backup** is provided by MogDB to back up MogDB, restore important data, and display help and version information.
+
+## Prerequisites
+
+- The MogDB database can be connected.
+- There are backup files in the backup directory for each node when the restoration is performed. If the backup file of a node is missing, copy a backup file from other nodes (for binary files, the node name in the file name needs to be changed).
+- Log in to the OS as the OS user **omm** to run the **gs_backup** command.
+
+## Syntax
+
+- Back up the database host.
+
+  ```bash
+  gs_backup -t backup --backup-dir=BACKUPDIR [-h HOSTNAME] [--parameter] [--binary] [--all] [-l LOGFILE]
+  ```
+
+- Restore the database host.
+
+  ```bash
+  gs_backup -t restore --backup-dir=BACKUPDIR [-h HOSTNAME] [--parameter] [--binary] [--all] [-l LOGFILE]
+  ```
+
+- Display help information.
+
+  ```bash
+  gs_backup -? | --help
+  ```
+
+- Display version information.
+
+  ```bash
+  gs_backup -V | --version
+  ```
+
+## Parameter Description
+
+The **gs_backup** tool can use the following types of parameters:
+
+- Parameters for backing up the database host:
+
+  - -h
+
+    Specifies the host name for storing the backup files
+
+    Value range: a host name If the host name is not specified, the current cluster will be backed up.
+
+  - -backup-dir=BACKUPDIR
+
+    Specifies the backup file path.
+
+  - -parameter
+
+    Backs up parameter files. If **-parameter**, **-binary**, and **-all** are not specified, only parameters files are backed up.
+
+  - -binary
+
+    Backs up the binary files in the **app** directory.
+
+  - -all
+
+    Backs up binary files in the **app** directory, the **pg_hba.conf** file, and the **postgsql.conf** file.
+
+  - -l
+
+    Specifies a log file and its storage path.
+
+    Default value: **$GAUSSLOG/om/gs_backup-YYYY-MM-DD_hhmmss.log**.
+
+- Parameters for restoring the database host:
+
+  - -h
+
+    Specifies the name of the host to restore.
+
+    Value range: a host name If the host is not specified, the corresponding backup node is restored.
+
+  - -backup-dir=BACKUPDIR
+
+    Restores the file obtaining path.
+
+  - -parameter
+
+    Restores parameter files. If **-parameter**, **-binary**, and **-all** are not specified, only parameters files are restored.
+
+  - -binary
+
+    Restores binary files.
+
+  - -all
+
+    Restores binary files and parameter files.
+
+  - -l
+
+    Specifies a log file and its storage path.
+
+    Default value: **$GAUSSLOG/om/gs_backup-YYYY-MM-DD_hhmmss.log**.
+
+- Other parameters:
+
+  - -?, -help
+
+    Displays help information.
+
+  - -V, -version
+
+    Displays version information.
+
+  - -t
+
+    Specify the type of operation.
+
+    Value range: backup or restore.
+
+## Example
+
+- Back up the database host.
+
+  ```bash
+  gs_backup -t backup --backup-dir=/opt/software/gaussdb/backup_dir -h plat1 --parameter
+  Backing up MogDB.
+  Parsing configuration files.
+  Successfully parsed the configuration file.
+  Performing remote backup.
+  Remote backup succeeded.
+  Successfully backed up MogDB.
+  ```
+
+- Execute the **gs_backup** script to restore the database host.
+
+  ```bash
+  gs_backup -t restore --backup-dir=/opt/software/gaussdb/backup_dir -h plat1 --parameter
+  Restoring MogDB.
+  Parsing the configuration file.
+  Successfully parsed configuration files.
+  Performing remote restoration.
+  Remote restoration succeeded.
+  Successfully restored MogDB.
+  ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/20-klist.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/20-klist.md
new file mode 100644
index 0000000000000000000000000000000000000000..7d49a176fa04ab59862bc0216f0eb78999f29322
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/20-klist.md
@@ -0,0 +1,16 @@
+---
+title: klist
+summary: klist
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# klist
+
+## Function
+
+**klist**, provided by the cluster authentication service Kerberos, is used to list users and tickets in the credential cache.
+
+## Parameter Description
+
+The Kerberos tool is provided by an open-source third party. For details about the parameters, see the Kerberos official document at <https://web.mit.edu/kerberos/krb5-1.17/doc/admin/admin_commands/index.html>.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/21-krb5kdc.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/21-krb5kdc.md
new file mode 100644
index 0000000000000000000000000000000000000000..b9ba525c864f3e11cba9068b0434f2ec4b820dbe
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/21-krb5kdc.md
@@ -0,0 +1,16 @@
+---
+title: krb5kdc
+summary: krb5kdc
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# krb5kdc
+
+## Function
+
+**krb5kdc**, provided by the cluster authentication service Kerberos, is used to provide column authentication and key management services.
+
+## Parameter Description
+
+The Kerberos tool is provided by an open-source third party. For details about the parameters, see the Kerberos official document at <https://web.mit.edu/kerberos/krb5-1.17/doc/admin/admin_commands/index.html>.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/22-kdestroy.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/22-kdestroy.md
new file mode 100644
index 0000000000000000000000000000000000000000..109117698a35fbd59818318e218e7c17647d59c7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/22-kdestroy.md
@@ -0,0 +1,16 @@
+---
+title: kdestroy
+summary: kdestroy
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# kdestroy
+
+## Function
+
+**kdestroy**, provided by the cluster authentication service Kerberos, is used to destroy the user's authorization tickets.
+
+## Parameter Description
+
+The Kerberos tool is provided by an open-source third party. For details about the parameters, see the Kerberos official document at <https://web.mit.edu/kerberos/krb5-1.17/doc/admin/admin_commands/index.html>.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/23-pg_config.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/23-pg_config.md
new file mode 100644
index 0000000000000000000000000000000000000000..55bdd5b289f4a3c7b48686a21d29c20978ed314b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/23-pg_config.md
@@ -0,0 +1,118 @@
+---
+title: pg_config
+summary: pg_config
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# pg_config
+
+## Function
+
+**pg_config** is used to print the configuration parameters of the installed database, which helps find the header file and library corresponding to the software package connected to the database.
+
+## Syntax
+
+```
+pg_config [option...]
+```
+
+## Parameter Description
+
+The **pg_config** tool supports one or more of the following options. If more than one option is provided, the information is printed in sequence. Each line contains one option. If no option is given, all available information is printed with the label.
+
+- -bindir
+
+  Prints the path of the executable file of a user. For example, you can use this option to find the **psql** program. Generally, this is the path of the **pg_config** program.
+
+- -docdir
+
+  Prints the location of a document.
+
+- -htmldir
+
+  Prints the location of the HTML file.
+
+- -includedir
+
+  Prints the path of the C header file of the client interface.
+
+- -pkgincludedir
+
+  Prints the location of other C header files.
+
+- -includedir-server
+
+  Prints the location of the C header files used for server programming.
+
+- -libdir
+
+  Prints the path of the target code library.
+
+- -pkglibdir
+
+  Prints the location of dynamically loaded modules, or where the server looks for them. Data files related to other systems may also be stored in this directory.
+
+- -localedir
+
+  Prints the location of the locale support file. If the locale support is not configured when the database is compiled, the value is an empty string.
+
+- -mandir
+
+  Prints the location of the manual page.
+
+- -sharedir
+
+  Prints the location of system-independent support files.
+
+- -sysconfdir
+
+  Prints the location of the system-wide configuration file.
+
+- -pgxs
+
+  Prints the location of the extended makefiles file.
+
+- -configure
+
+  Prints the options passed to the configure script during configuration and database compilation. The options are used to copy the same configuration or find out which options are used to compile the binary package. However, note that binary packages usually contain vendor-provided patches.
+
+- -cc
+
+  Prints the values of the CC variables used to compile the database. This option displays the C compiler in use.
+
+- -cppflags
+
+  Prints the value of the *CPPFLAGS* variable used to compile the database. This option displays the C compiler switch (usually **-I**) needed for preprocessing.
+
+- -cflags
+
+  Prints the value of the *CFLAGS* variable used during database compilation. This option displays the C compiler switch.
+
+- -cflags_sl
+
+  Prints the value of the *CFLAGS_SL* variable used during database compilation. This option shows the additional C compiler switch for compiling the shared library.
+
+- -ldflags
+
+  Prints the value of the *LDFLAGS* variable used during database compilation. It shows the linker's switch.
+
+- -ldflags_ex
+
+  Prints the value of the *LDFLAGS_EX* variable used to create the database. This shows the linker switch for building executable files.
+
+- -ldflags_sl
+
+  Prints the value of the *LDFLAGS_SL* variable used during database compilation. It shows the switch of the linker used to compile the shared library.
+
+- -libs
+
+  Prints the value of the *LIBS* variable used during database compilation. It usually contains the **-l** switch of the external library connected to the database.
+
+- -version
+
+  Prints the database version.
+
+- -?, -help
+
+  Displays help information about **pg_config** command parameters and exits.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/24-pg_controldata.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/24-pg_controldata.md
new file mode 100644
index 0000000000000000000000000000000000000000..57a3ab80b0eaef482f373bf56ec44ea615913ab0
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/24-pg_controldata.md
@@ -0,0 +1,50 @@
+---
+title: pg_controldata
+summary: pg_controldata
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# pg_controldata
+
+## Function
+
+The **pg_controldata** tool is used to display information about control files in the database directory.
+
+## Prerequisites
+
+Ensure that the data directory is correct and the **pg_control** file exists in the corresponding data directory.
+
+## Syntax
+
+- Check the control file information.
+
+  ```
+  pg_controldata [DATADIR]
+  ```
+
+- Display the version number.
+
+  ```
+  pg_controldata -V | --version
+  ```
+
+- Display help information.
+
+  ```
+  pg_controldata -? | --help
+  ```
+
+## Parameter Description
+
+- DATADIR
+
+  Parameter used for viewing the control file information. **DATADIR** indicates the database directory corresponding to the instance.
+
+- -V, -version
+
+  Displays version information.
+
+- -?,-help
+
+  Displays help information.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/24.1-pg_recvlogical.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/24.1-pg_recvlogical.md
new file mode 100644
index 0000000000000000000000000000000000000000..a4252c92a0807059920fddeac68f145f5558ec3b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/24.1-pg_recvlogical.md
@@ -0,0 +1,153 @@
+---
+title: pg_recvlogical
+summary: pg_recvlogical
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# pg_recvlogical
+
+## Function
+
+**pg_recvlogical** connects to a specified node to create and delete logical replication slots, obtains the intermediate result of logic decoding from the node continuously in real time, and outputs the result to a file or in standard mode.
+
+## Syntax
+
+```
+pg_recvlogical [OPTION]...
+```
+
+Logical replication slot behavior parameters are mandatory and must be specified. Other parameters are optional. If you do not specify them, the default values will be read.
+
+## Parameter Description
+
+- Logical replication slot behavior parameters (mandatory):
+
+  - -create
+
+    Creates a logical replication slot.
+
+  - -start
+
+    Starts the flow replication of a logic replication slot.
+
+  - -drop
+
+    Deletes a logical replication slot.
+
+- Connection options:
+
+  - -d, -dbname=DBNAME
+
+    Connects to the target database.
+
+  - -h, -host=HOSTNAME
+
+    Specifies the name or socket of the connected host.
+
+  - -p, -port=PORT
+
+    Specifies the HA port number for connecting to the target DN.
+
+  - -U, -username=NAME
+
+    Specifies the user name for connecting to the target database.
+
+  - -w, -no-password
+
+    Performs connection without a password.
+
+  - -W, -password
+
+    Performs connection with a specified password.
+
+- Replication parameters:
+
+  - -F -fsync-interval=INTERVAL
+
+    Specifies an interval for synchronizing data to the target output file.
+
+    The unit is s. The default value is **10**.
+
+  - -o, -option=NAME[=VALUE]
+
+    Adds parameters to the output plug-in of a logical replication slot.
+
+    The values are **include-xids**, **skip-empty-xacts**, and **include-timestamp**.
+
+    For details, see "SQL Reference &gt; Functions and Operators &gt; System Administration Functions &gt; Logical Replication Functions &gt; options" in the *Developer Guide*.
+
+  - -P, -plugin=PLUGIN
+
+    Specifies the logical replication slot output plug-in.
+
+    The default value is **mppdb_decoding**.
+
+  - -s, -status-interval=INTERVAL
+
+    Specifies an interval for sending heartbeat packets.
+
+    The unit is s. The default value is **10**.
+
+  - -S, -slot=SLOT
+
+    Specifies the name of a logical replication slot.
+
+  - -I, -startpos=PTR
+
+    LSN location of the initial replication when an existing logical replication slot is used
+
+- Other parameters:
+
+  - -f, -file=FILE
+
+    Specifies the output file.
+
+    If **-** is used, data is output to stdout.
+
+  - -n, -no-loop
+
+    If this parameter is specified, the system does not retry after the connection fails.
+
+  - -v, -verbose
+
+    Displays detailed information.
+
+  - -V, -version
+
+    Displays the version and exits immediately.
+
+  - -?, -help
+
+    Displays help information and exits immediately.
+
+## Examples
+
+1. Create a logical replication slot named **test_slot**.
+
+   ```bash
+   pg_recvlogical -d postgres -S test_slot -p 26000 --create
+   ```
+
+2. Enable stream decoding, and use **stdout** for output.
+
+   ```bash
+   pg_recvlogical -d postgres -S test_slot -p 26000 --start -v -f -
+   pg_recvlogical: starting log streaming at 0/0 (slot test_slot)
+   pg_recvlogical: initiated streaming
+   pg_recvlogical: confirming write up to 0/0, flush to 0/0 (slot test_slot)
+   pg_recvlogical: confirming write up to 0/2A342E8, flush to 0/2A342E8 (slot test_slot)
+   pg_recvlogical: confirming write up to 0/2A34320, flush to 0/2A34320 (slot test_slot)
+   pg_recvlogical: confirming write up to 0/2A34320, flush to 0/2A34320 (slot test_slot)
+   BEGIN 16039
+   table public.t: INSERT: a[integer]:4 b[integer]:4
+   COMMIT 16039
+   pg_recvlogical: confirming write up to 0/2A34450, flush to 0/2A34450 (slot test_slot)
+   pg_recvlogical: confirming write up to 0/2A34450, flush to 0/2A34450 (slot test_slot)
+   ```
+
+3. Delete the logical replication slot.
+
+   ```bash
+   pg_recvlogical -d postgres -S test_slot -p 26000 --drop
+   ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/25-pg_resetxlog.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/25-pg_resetxlog.md
new file mode 100644
index 0000000000000000000000000000000000000000..c2baa20bba534714b7c668fb21fdd6ffb5c827f4
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/25-pg_resetxlog.md
@@ -0,0 +1,70 @@
+---
+title: pg_resetxlog
+summary: pg_resetxlog
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# pg_resetxlog
+
+## Function
+
+**pg_resetxlog** is a tool for re-setting database transaction files.
+
+## Prerequisites
+
+Ensure that the database directory exists and is correct.
+
+## Syntax
+
+```
+pg_resetxlog [OPTION]... DATADIR
+```
+
+## Parameter Description
+
+*OPTION* is described as follows:
+
+- DATADIR
+
+  Database directory to be modified. Ensure that the directory is correct.
+
+- -e XIDEPOCH
+
+  Sets the period of the next transaction ID.
+
+- -f
+
+  Forcibly updates transaction files.
+
+- -l xlogfile
+
+  Forcibly specifies the minimum point of the new transaction log in the Xlog file.
+
+- -m XID
+
+  Sets the next multitransaction ID.
+
+- -n
+
+  Displays the value in the configuration file without update.
+
+- -o OID
+
+  Sets the next OID.
+
+- -O OFFSET
+
+  Sets the offset of the next multitransaction.
+
+- -V, -version
+
+  Displays version information.
+
+- -x XID
+
+  Sets the next transaction ID.
+
+- -?, -help
+
+  Displays help information.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/26-pg_archivecleanup.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/26-pg_archivecleanup.md
new file mode 100644
index 0000000000000000000000000000000000000000..50f128b8d4eed5a75240e983194a1907b4354962
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/26-pg_archivecleanup.md
@@ -0,0 +1,58 @@
+---
+title: pg_archivecleanup
+summary: pg_archivecleanup
+author: Zhang Cuiping
+date: 2021-11-17
+---
+
+# pg_archivecleanup
+
+## Function
+
+pg_archivecleanup is a tool used to clear old archive logs.
+
+## Syntax
+
+```
+pg_archivecleanup [OPTION]... ARCHIVELOCATION OLDESTKEPTWALFILE
+```
+
+## Parameter Description
+
+- -d
+
+  Displays debug logs on the stderr.
+
+- -n
+
+  Displays the name of the file to be deleted.
+
+- -V,-version
+
+  Displays the version of **pg_archivecleanup** and exits.
+
+- -x extension
+
+  Provides an extension option to select only files with the corresponding extension format when the program is used as a separate tool.
+
+- -?,-help
+
+  Displays the help information related to the **pg_archivecleanup** command line parameters.
+
+## Examples
+
+Delete logs generated earlier than 000000010000000000000010.
+
+```
+pg_archivecleanup [OPTION]... ARCHIVELOCATION OLDESTKEPTWALFILE
+```
+
+## Extended Applications
+
+Set the **archive_cleanup_command** parameter in the **recovery.conf** file during the standby node recovery.
+
+```
+archive_cleanup_command = 'pg_archivecleanup /mnt/server/archiverdir %r'
+```
+
+After the recovery is complete, delete unnecessary files from the archive directory.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/27-pssh.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/27-pssh.md
new file mode 100644
index 0000000000000000000000000000000000000000..a495120dc6e9e8200e659ac45223faed4ef2f021
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/27-pssh.md
@@ -0,0 +1,68 @@
+---
+title: pssh
+summary: pssh
+author: Zhang Cuiping
+date: 2021-11-17
+---
+
+# pssh
+
+## Basic Function
+
+This tool is used to execute access between database nodes and send commands to remote nodes.
+
+## Syntax
+
+```
+python3 pssh [OPTIONS]
+```
+
+## Parameter Description
+
+- -help
+
+  Displays help information.
+
+- -H HOSTNAME
+
+  Specifies the host list.
+
+- -h HOSTFILE
+
+  Specifies the full path of the file to be written into the host list.
+
+- -t TIMEOUT
+
+  Specifies the connection timeout interval, in seconds. The default value is **300s**.
+
+- -p PARALLEL
+
+  Specifies the maximum number of concurrent tasks. The default value is **32**.
+
+- -o OUTDIR
+
+  Specifies the full file path of the execution result.
+
+- -e ERRDIR
+
+  Specifies the full path of the error information output file.
+
+- -P
+
+  Specifies the command executed on the online remote host.
+
+- -s
+
+  Displays the execution result.
+
+- -x EXTRA
+
+  Specifies the extra command line parameters.
+
+- -i
+
+  Displays the output and errors of all nodes.
+
+- -O OPT
+
+  Specifies the added SSH parameters in offline mode.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/28-pscp.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/28-pscp.md
new file mode 100644
index 0000000000000000000000000000000000000000..1dc315c65553ba6c6757c4fe0053d4a399998011
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/28-pscp.md
@@ -0,0 +1,72 @@
+---
+title: pscp
+summary: pscp
+author: Zhang Cuiping
+date: 2021-11-17
+---
+
+# pscp
+
+## Basic Function
+
+This tool is used to transfer files between database nodes.
+
+## Syntax
+
+```
+python3 pscp [OPTIONS]
+```
+
+## Parameter Description
+
+- -help
+
+  Displays help information.
+
+- -H HOSTNAME
+
+  Specifies the host list.
+
+- -h HOSTFILE
+
+  Specifies the full path of the file to be written into the host list.
+
+- -t TIMEOUT
+
+  Specifies the connection timeout interval, in seconds. The default value is **300s**.
+
+- -p PARALLEL
+
+  Specifies the maximum number of concurrent tasks. The default value is **256**.
+
+- -o OUTDIR
+
+  Specifies the full file path of the execution result.
+
+- -e ERRDIR
+
+  Specifies the full path of the error information output file.
+
+- -r
+
+  Recursively copies a directory.
+
+- -v
+
+  Enables the diagnosis message function.
+
+- -s
+
+  Displays the execution result.
+
+- -x EXTRA
+
+  Specifies the extra command line parameters.
+
+- -i
+
+  Displays the output and errors of all nodes.
+
+- -O OPT
+
+  Specifies the added SCP parameters in offline mode.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/29-transfer.py.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/29-transfer.py.md
new file mode 100644
index 0000000000000000000000000000000000000000..24060b1bfac9bdcb9d93db9abb16eac7774c32de
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/29-transfer.py.md
@@ -0,0 +1,60 @@
+---
+title: transfer.py
+summary: transfer.py
+author: Zhang Cuiping
+date: 2021-11-17
+---
+
+# transfer.py
+
+## Function
+
+In non-single-node mode, you can use the **transfer.py** tool to send the dictionary file used for full-text search and the files required by the PostGIS plug-in to other nodes.
+
+## Prerequisites
+
+- Before running this tool, ensure that the following files exist in the **$GAUSSHOME** directory. Otherwise, an error will be reported. The error code is 52200:
+  - script/gspylib/common/DbClusterInfo.py
+  - script/gspylib/common/Common.py
+  - script/gspylib/common/GaussLog.py
+  - script/gspylib/threads/SshTool.py
+- The environment variable *$GPHOME* is set correctly.
+
+## Syntax
+
+- Send the sourcefile to the **destinationpath** path of all nodes.
+
+  ```
+  transfer.py 1 sourcefile destinationpath
+  ```
+
+- Send the sourcefile to the same path on the standby node of **pgxc_node_name**.
+
+  ```
+  transfer.py 2 sourcefile pgxc_node_name
+  ```
+
+- Display the help information.
+
+  ```
+  transfer.py -? | --help
+  ```
+
+## Parameter Description
+
+- Options are as follows:
+
+  - **1**: sends the current file to the destination file paths of all nodes.
+  - **2**: sends the current file to the same path on the standby node of the destination node.
+
+- sourcefile
+
+  Path of the source file to be sent.
+
+- destinationpath
+
+  Destination file path.
+
+- pgxc_node_name
+
+  Destination node name.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/3-gs_basebackup.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/3-gs_basebackup.md
new file mode 100644
index 0000000000000000000000000000000000000000..3ca0cd667eba4ee24639e5f7f8d39c3c3120a9ab
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/3-gs_basebackup.md
@@ -0,0 +1,166 @@
+---
+title: gs_basebackup
+summary: gs_basebackup
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_basebackup
+
+## Background
+
+After MogDB is deployed, problems and exceptions may occur during database running. **gs_basebackup**, provided by MogDB, is used to perform basic physical backup. **gs_basebackup** copies the binary files of the database on the server using a replication protocol. To remotely execute **gs_basebackup**, you need to use the system administrator account. **gs_basebackup** supports hot backup and compressed backup.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - **gs_basebackup** supports only full backup of the primary and standby nodes.
+> - **gs_basebackup** supports hot backup and compressed backup.
+> - If you use gs_basebackup to back up a tablespace that contains an absolute path on the same server, you can use tablespace-mapping to redirect the tablespace path or use the archive mode to back up the tablespace.
+> - If the functions of incremental checkpoint and dual-write are enabled, **gs_basebackup** also backs up dual-write files.
+> - If the **pg_xlog** directory is a soft link, no soft link is created during backup. Data is directly backed up to the **pg_xlog** directory in the destination path.
+> - If the backup permission is revoked during the backup, the backup may fail or the backup data may be unavailable.
+> - If the server does not respond due to a temporary network fault, **gs_basebackup** will exit after waiting for a maximum of 120 seconds.
+
+## Prerequisites
+
+- The MogDB database can be connected.
+- User permissions are not revoked during the backup.
+- In the **pg_hba.conf** file, the replication connection is allowed and the connection is established by a system administrator.
+- If the Xlog transmission mode is **stream**, the number of **max_wal_senders** must be configured to at least one.
+- If the Xlog transmission mode is **fetch**, the **wal_keep_segments** parameter must be set to a large value so that logs are not removed before the backup ends.
+- During the restoration, backup files exist in the backup directory on all the nodes. If backup files are lost on any node, copy them to it from another node.
+
+## Syntax
+
+- Display help information.
+
+  ```
+  gs_basebackup -? | --help
+  ```
+
+- Display version information.
+
+  ```
+  gs_basebackup -V | --version
+  ```
+
+## Parameter Description
+
+The **gs_basebackup** tool can use the following types of parameters:
+
+- -D directory
+
+  Directory for storing backup files. This parameter is mandatory.
+
+- Common parameters
+
+  - -c, -checkpoint=fast|spread
+
+    Sets the checkpoint mode to **fast** or **spread** (default).
+
+  - -l, -label=LABEL
+
+    Adds tags for the backup.
+
+  - -P, -progress
+
+    Enables the progress report.
+
+  - -v, -verbose
+
+    Enables the verbose mode.
+
+  - -V, -version
+
+    Prints the version and exits.
+
+  - -?, -help
+
+    Displays **gs_basebackup** command parameters.
+
+  - -T, -tablespace-mapping=olddir=newdir
+
+    During the backup, the tablespace in the **olddir** directory is relocated to the **newdir** directory. For this to take effect, **olddir** must exactly match the path where the tablespace is located (but it is not an error if the backup does not contain the tablespaces in **olddir**). **olddir** and **newdir** must be absolute paths. If a path happens to contain an equal sign (=), you can escape it with a backslash (). This option can be used multiple times for multiple tablespaces.
+
+  - -F, -format=plain|tar
+
+    Sets the output format to **plain** (default) or **tar**. If this parameter is not set, the default value **-format=plain** is used. The plain format writes the output as a flat file, using the same layout as the current data directory and tablespace. When the cluster has no extra tablespace, the entire database is placed in the target directory. If the cluster contains additional tablespaces, the primary data directory will be placed in the target directory, but all other tablespaces will be placed in the same absolute path on the server. The tar mode writes the output as a tar file in the target directory. The primary data directory is written to a file named **base.tar**, and other tablespaces are named after their OIDs. The generated .tar package must be decompressed using the **gs_tar** command.
+
+  - -X, -xlog-method=fetch|stream
+
+    Sets the Xlog transmission mode. If this parameter is not set, the default value **-xlog-method=stream** is used. The required write-ahead log files (WALs) are included in the backup. This includes all WALs generated during the backup. In fetch mode, WAL files are collected at the end of the backup. Therefore, the **wal_keep_segments** parameter must be set to a large value so that logs are not removed before the backup ends. If it has been rotated when the log is to be transmitted, the backup fails and is unavailable. In stream mode, WALs are streamed when a backup is created. This will open a second connection to the server and start streaming WALs while the backup is running. Therefore, it will use up to two connections configured by the **max_wal_senders** parameter. As long as the client can receive WALs, no additional WALs need to be stored on the host.
+
+  - -x, -xlog
+
+    Equivalent to using **-X** with the fetch method.
+
+  - -Z -compress=level
+
+    Enables gzip compression for the output of the tar file and sets the compression level (0 to 9, where 0 indicates no compression and 9 indicates the best compression). The compression is available only when the tar format is used. The suffix .gz is automatically added to the end of all .tar file names.
+
+  - -z
+
+    Enables gzip compression for tar file output and uses the default compression level. The compression is available only when the tar format is used. The suffix .gz is automatically added to the end of all .tar file names.
+
+  - -t, -rw-timeout
+
+    Sets the checkpoint time limit during backup. The default value is 120s. If the full checkpoint of the database is time-consuming, you can increase the value of **rw-timeout**.
+
+- Connection parameters
+
+  - -h, -host=HOSTNAME
+
+    Specifies the host name of the machine on which the server is running or the directory for the Unix-domain socket.
+
+  - -p, -port=PORT
+
+    Specifies the port number of the database server.
+
+    You can modify the default port number using this parameter.
+
+  - -U, -username=USERNAME
+
+    Specifies the user that connects to the database.
+
+  - -s, -status-interval=INTERVAL
+
+    Specifies the time for sending status packets to the server, in seconds.
+
+  - -w,-no-password
+
+    Never issues a password prompt.
+
+  - -W, -password
+
+    Issues a password prompt when the **-U** parameter is used to connect to a local or remote database.
+
+## Example
+
+```bash
+gs_basebackup -D /home/test/trunk/install/data/backup -h 127.0.0.1 -p 21233
+INFO:  The starting position of the xlog copy of the full build is: 0/1B800000. The slot minimum LSN is: 0/1B800000.
+```
+
+## Restoring Data from Backup Files
+
+If a database is faulty, restore it from backup files. **gs_basebackup** backs up the database in binary mode. Therefore, you can directly copy and replace the original files or start the database on the backup database.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - If the current database instance is running, a port conflict may occur when you start the database from the backup file. In this case, you need to modify the port parameter in the configuration file or specify a port when starting the database.
+> - If the current backup file is a primary/standby database, you may need to modify the replication connections between the primary and standby databases. That is, **replconninfo1** and **replconninfo2** in the **postgre.conf** file.
+> - If the parameter data_directory of the configuration file postgresql.conf is opened and configured, when the database is started using the backup directory, the difference between the data_directory and the backup directory will cause the startup to fail. You can modify the value of data_directory to the new data directory, or comment out this parameter.
+
+To restore the original database, perform the following steps:
+
+1. Stop the database server. For details, see *Administrator Guide*.
+2. Copy the original database and all tablespaces to another location for future use.
+3. Delete all or part of the files from the original database.
+4. Use the database system user rights to restore the required database files from the backup.
+5. If a link file exists in the database, modify the link file so that it can be linked to the correct file.
+6. Restart the database server and check the database content to ensure that the database is restored to the required status.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - Incremental restoration from backup files is not supported.
+> - After the restoration, check that the link file in the database is linked to the correct file.
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/4-gs_ctl.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/4-gs_ctl.md
new file mode 100644
index 0000000000000000000000000000000000000000..3705558a7a61fccee860e6d0595d190dcbbd8415
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/4-gs_ctl.md
@@ -0,0 +1,106 @@
+---
+title: gs_ctl
+summary: gs_ctl
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_ctl
+
+## Background
+
+**gs_ctl**, provided by MogDB, is used to control the database service. It can be used to start and stop the database service and to query the database status. **gs_ctl** is used by the MogDB management module.
+
+**gs_ctl** is executed by OS user **omm**.
+
+- Start, stop, and restart the MogDB node.
+- Reload the configuration files (**postgresql.conf** and **pg_hba.conf**) without stopping the database.
+- Perform primary/standby switchover, query primary/standby status, rebuild the database instance, and query the rebuilding status.
+
+## Description
+
+The **gs_ctl** tool can use the following types of parameters:
+
+- Parameters for **option**. For details, see [Table 1](#1).
+
+- Common parameters. For details, see [Table 2](#2).
+
+- Parameters for **start** and **restart**. For details, see [Table 3](#3).
+
+- Parameters for **stop** and **restart**. For details, see [Table 4](#4).
+
+- Parameters for **switchover**. For details, see [Table 5](#5).
+
+- Parameters for **build**. For details, see [Table 6](#6).
+**Table 1** Parameters for option <a id="1"></a>
+
+| Parameter  | Description                                                  |
+| :--------- | :----------------------------------------------------------- |
+| init       | Creates a database.                                          |
+| start      | Starts the database.                                         |
+| restart    | Restarts the database.                                       |
+| build      | Rebuilds the standby or cascaded standby server on the primary server. |
+| stop       | Stops the database.                                          |
+| reload     | Reloads the configuration files (**postgresql.conf** and **pg_hba.conf**). |
+| status     | Displays the running status of the database services.        |
+| promote    | Exits the faulty restoration when the running standby server is instructed in the specified data directory, and starts to perform the read and write operations. |
+| finishredo | Specifies that the standby server stops playback and is forcibly switched to the primary when the primary server is faulty. |
+| failover   | When the primary server is abnormal, switches the standby server to a primary server.<br />After the switchover is successful, run the **gs_om -t refreshconf** command to record the information about the primary and standby servers. Ensure that the **gs_om -t refreshconf** command is executed successfully. Otherwise, the database status will be affected when the database is restarted. |
+| switchover | When the primary/standby server relationship is normal, switches the standby server to primary for maintenance purposes. Data will not be lost during the switchover.<br />The **switchover** command takes effect only when it is executed on the standby server to be switched to the primary server. If the **switchover** command is executed on the primary server, it is used only for query.<br />After the switchover is successful, run the **gs_om -t refreshconf** command to record the information about the primary and standby servers. Ensure that the **gs_om -t refreshconf** command is executed successfully. Otherwise, the database status will be affected when the database is restarted.<br />After the **switchover** command is delivered, if the command execution times out, the execution status of the background process may be uncertain. |
+| query      | Queries the status between the primary and standby server.   |
+| notify     | Specifies the primary and standby servers after startup.     |
+| kill       | Sends semaphore to a specified process.                      |
+| querybuild | Checks the rebuilding process of the database.               |
+
+**Table 2** Common parameters <a id="2"></a>
+
+| Parameter           | Description                                                  | Value Range                                                  |
+| :------------------ | :----------------------------------------------------------- | :----------------------------------------------------------- |
+| -D, -pgdata=DATADIR | Specifies the data directory.                                | The value of **DATADIR** must be a valid data directory.     |
+| -s, -silent         | Displays partial prompt information only for the **promote**, **reload**, **restart**, and **stop** commands. For example, information such as "server promoting" and "server shutting down" is displayed while "waiting for server to shut down" or "server stopped" is not displayed. | -                                                            |
+| -t, -timeout=SECS   | Maximum seconds for waiting the completion of database startup, shutdown, or switchover. If the waiting times out, the command ends and exits with a notification that the waiting is not required anymore. Then, you can run the gs_om -t status -detail command or other commands to check whether the database is started, shut down, or switched over successfully. | Value range: an integer (second).<br />Default value: 60 seconds (waiting the completion of database startup, shutdown, or switchover) |
+| -V , -version       | Prints the **gs_ctl** version information and exits.         | -                                                            |
+| -w                  | Waits until the operation is complete.                       | By default, you need to wait until the operation is complete when the database is started, stopped, or restarted. |
+| -W                  | Specifies that you do not need to wait for the operation to complete. | -                                                            |
+| -M                  | **-M** must be followed by the **SERVERMODE** parameter, which specifies the startup mode of a database upon startup. | Value range of **SERVERMODE**:<br />- **primary**: The server starts in primary mode.<br />- **standby**: The server starts in standby mode.<br />- **cascade_standby**: The local server starts as a cascaded standby server.<br />- **pending**: The server is in pending mode to be promoted to a primary server or a standby server. |
+| -T                  | **-T** is followed by a term. The term is used as the host term when the command for switching the standby server to primary is executed. During the rebuilding, hosts greater than the term will be connected. | Value range of term: an unsigned integer.                    |
+| -d                  | Prints more debugging information.                           | None                                                         |
+| -q                  | After the generation is completed, it does not start automatically, and needs to be started by the caller. | None                                                         |
+| -P PASSWORD         | Specifies the password of the user connecting to the local database. It is used in conjunction with the **-U** parameter.<br />NOTE:<br />When **-U** is not specified, and the authentication mode is **trust**, the setting of the **-P** parameter is invalid. | -                                                            |
+| -U USERNAME         | Specifies the user that connects to the database. This parameter can be used only in conjunction with the parameter **notify**, **query**, **failover**, **switchover**, or **querybuild**.<br />For domain users, use the DOMAIN\username format. | Value range: users existing in MogDB.<br />Default value: If this parameter is not specified, the current OS user is used. |
+| -?, -help           | Displays the help information related to the **gs_ctl** command line parameters. | -                                                            |
+
+**Table 3** Common parameters for **start** and **restart**<a id="3"></a>
+
+| Parameter           | Description                                                  | Value Range                                                  |
+| :------------------ | :----------------------------------------------------------- | :----------------------------------------------------------- |
+| -c, -core-file      | Allows the **gaussdb** process to generate core files.       | -                                                            |
+| -l, -log=FILENAME   | Appends the server log output to the **FILENAME** file.      | The value of **FILENAME** is a file that the user who starts the database service has the permission to operate.<br />For example, the value is a file in the **data** directory. |
+| -o OPTIONS          | Specifies options to be passed from MogDB directly to the **gaussdb** command.<br />The options should usually be surrounded by single or double quotation marks to ensure that they are transferred as a whole. | Parameters supported in **gaussdb**.                         |
+| -p PATH-TO-POSTGRES | Specifies the location of the executable file of the **gaussdb**. | By default, the gaussdb executable file is taken from the same directory as **gs_ctl**. |
+
+**Table 4** Common parameters for **stop** and **restart**<a id="4"></a>
+
+| Parameter      | Description                  | Value Range                                                  |
+| :------------- | :--------------------------- | :----------------------------------------------------------- |
+| -m, -mode=MODE | Specifies the disabled mode. | Values of **mode**:<br />- **fast**: All active transactions are rolled back and all clients are disconnected forcibly, and then the server is disabled.<br />- **immediate**: The server is shut down forcibly and fault recovery occurs on the next startup.<br />Default value: **fast** |
+
+**Table 5** Parameters for switchover<a id="5"></a>
+
+| Parameter          | Description                                                  | Value Range                                                  |
+| :----------------- | :----------------------------------------------------------- | :----------------------------------------------------------- |
+| -m SWITCHOVER-MODE | Specifies the HA switchover mode when the primary and standby servers are normal. | Values of **mode**:<br />- **fast**: All active transactions are rolled back and all clients are disconnected forcibly, and then the server is switched.<br />- **smart**: This mode is not supported in this version.<br />Default value: **fast** |
+
+**Table 6** Parameters for build<a id="6"></a>
+
+| Parameter                 | Description                                                  | Value Range                                                  |
+| :------------------------ | :----------------------------------------------------------- | :----------------------------------------------------------- |
+| -b MODE                   | Specifies the mode of the standby server to be rebuilt.      | Values of **mode**:<br />- **full**: Fully resynchronizes the data directory of the primary server using an image.<br />- **incremental**: Incrementally restores the standby server based on the differences between the data of primary and standby DNs found in Xlogs.<br />NOTE:<br />Incremental rebuilding applies to scenarios where logs are inconsistent between the primary and standby nodes.<br />Incremental rebuilding does not apply to the scenario where one primary and one standby are deployed and the maximum HA is not enabled. In this scenario, you need to perform full rebuilding or enable the maximum HA before performing the incremental rebuilding.<br />The server cannot be restored using the incremental rebuilding method if the standby server data file is damaged or the data directory is lost. Restore the standby server using the incremental rebuilding method.<br />- **auto** (not specified): Selects **incremental** first and then **full** after **incremental** fails for three times.<br />Default value: **auto**<br />NOTE:<br />To rebuild a cascaded standby server, add the **-M cascade_standby** parameter. |
+| -r, -recvtimeout=INTERVAL | Specifies the timeout duration that the log of the standby server receives the host response during the rebuilding process. | Value range: an integer (second).<br />Default value: **120s**<br />Note: <br />The timeout interval needs to be set based on the service load. If the service load is heavy, the timeout interval for waiting for a response from the host needs to be prolonged. It is recommended that the timeout interval be equal to the checkpoint execution time plus 1 minute. |
+| -q                        | Specifies whether to automatically restart after the rebuilding is complete.<br />If this parameter is specified, the system does not automatically restart.<br />If no scenario is specified, the system automatically restarts. The default maximum waiting time is 60 seconds. If the database fails to be started within this period, the system displays a message indicating that the waiting is not required and the command exits. Then, you can run the gs_om -t status -detail command or other commands to check whether the database is started successfully. | None                                                         |
+
+**Table 7** Parameters for query
+
+| Parameter | Description                                      | Value Range |
+| :-------- | :----------------------------------------------- | :---------- |
+| -L        | Queries the LSN and displays the maximum length. | None        |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/5-gs_initdb.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/5-gs_initdb.md
new file mode 100644
index 0000000000000000000000000000000000000000..90b07ef1b8d04c9aedfdd3328d5f8014eec9d860
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/5-gs_initdb.md
@@ -0,0 +1,120 @@
+---
+title: gs_initdb
+summary: gs_initdb
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_initdb
+
+## Overview
+
+**Background**
+
+When a database is initialized using **gs_initdb**, a database directory is created, a system catalog is generated, and a default database and a template database are created.
+
+**System catalog**
+
+A large number of system catalogs and views are generated when a database is initialized, many of which allow access from any database user.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> Permissions on **pg_user_status** and **pg_auth_history** system catalogs are granted only to initialized users and **sysadmin** users.
+
+**Generated database**
+
+- template1: a template database. When you create a database, all content in the template1 database is copied. The settings of template1 are determined by the parameters of **gs_initdb**.
+- template0: Is the initial backup database provided by MogDB. template0 can be used to generate an empty database if necessary.
+- postgres: a default database provided for users, tools, and third-party applications.
+
+## Usage Guide
+
+**Background**
+
+During installation, you are advised to use the **-D** parameter to call **gs_initdb** to initialize a database. If a database needs to be initialized to rectify a fault, run **gs_initdb**.
+
+- Although **gs_initdb** attempts to create the corresponding data directory, it may not have the permission to do so, because in most cases, the parent directory is owned by user **root**. To create a data directory, create an empty data directory as user **root** first and deliver the ownership of this directory to the database user using **chown**.
+- **gs_initdb** is used to set the template1 database and the setting becomes the default setting of other databases.
+- **gs_initdb** initializes the default locale and character set encoding of a database. The character set encoding, character encoding sequence (LC_COLLATE), and character set class (LC_CTYPE, such as uppercase letters, lowercase letters, and digits) can be separately set for databases when you create them.
+
+**syntax**
+
+```
+gs_initdb [OPTION]... [DATADIR]
+```
+
+**Procedure**
+
+1. Log in as the OS user **omm** to the primary database node.
+
+2. Plan the database directory.
+
+   a. Switch to user **root**.
+
+   ```bash
+    su - root
+   ```
+
+   b. Enter the username and password as prompted.
+
+3. Go to the **/opt/gaussdb** directory and create the **data1** directory.
+
+   ```bash
+   cd /opt/gaussdb
+   mkdir data1
+   ```
+
+   a. Allocate the ownership of the **data1** directory to the database user omm. dbgrp is the user group that the omm belongs to.
+
+   ```bash
+   chown omm:dbgrp data1
+   ```
+
+   b. Exit user **root**.
+
+   ```sql
+   exit
+   ```
+
+4. Run the **gs_initdb** command to initialize the database.
+
+   ```bash
+   gs_initdb -D /opt/gaussdb/data1 -w "Gauss@123" --nodename='data1'
+   ```
+
+## Command Reference
+
+For details about common parameters and uncommon parameters supported by **gs_initdb**, see [Table 1](#parameters) and [Table 2](#uncommon).
+
+**Table 1** Common parameters <a id="parameters"></a>
+
+| Parameter                                                    | Description                                                  | Value Range                                                  |
+| :----------------------------------------------------------- | :----------------------------------------------------------- | :----------------------------------------------------------- |
+| -A, --auth=METHOD                                            | Specifies the authentication method for local users used in **pg_hba.conf** (host and local rows).Do not use **trust**, which is the default value, unless you trust all local users on your system.<br />NOTICE:<br />If the value is **md5**, manually change the value of **password_encryption_type** in the **postgresql.conf.sample** file to **0** and comment out the parameter for the change to take effect. **gs_initdb** must be used in conjunction with **-W**. | Values of **METHOD**:<br />- trust<br />- reject<br />- **md5** (an insecure algorithm, used for compatibility with earlier versions)<br />- sha256<br />- sm3<br />Default value: **trust** |
+| --auth-host=METHOD                                           | Specifies the authentication method for local users over TCP/IP used in **pg_hba.conf** (host rows).<br />The value specified in the **-A** parameter is overwritten when this parameter is specified. | Values of **METHOD**:<br />- trust<br />- reject<br />- **md5** (an insecure algorithm, used for compatibility with earlier versions)<br />- sha256<br />- sm3<br />Default value: **trust** |
+| --auth-local=METHOD                                          | Specifies the authentication method for local users using Unix-domain socket connections used in **pg_hba.conf** (local rows).<br />The value specified in the **-A** parameter is overwritten when this parameter is specified. | Values of **METHOD**:<br />- trust<br />- reject<br />- **md5** (an insecure algorithm, used for compatibility with earlier versions)<br />- sha256<br />- sm3<br />Default value: **trust** |
+| [-D, --pgdata=]DATADIR                                       | Specifies the data directory.                                | Set **DATADIR** as required.                                 |
+| --nodename=NODENAME                                          | Specifies the name of an initialized node.                   | The naming rules for nodes are as follows:<br />- The node name can only be lowercase letters (a-z), underscores (_), number signs (#), digits (0-9), and dollar signs ($).<br />- The node name must start with a lowercase letter (a-z), or underscore (_).<br />- The nodename cannot be an empty string, and cannot exceed 64 characters. |
+| -E, --encoding=ENCODING                                      | Specifies the encoding format for a new database.            | If this parameter is specified, the **--locale** option must be added to specify the locale that supports the encoding format. If the **--locale** option is not added, the system default locale is used. If the encoding format in the system default locale is inconsistent with the encoding format specified in this parameter, the database initialization failed.<br />If this parameter is not specified, the encoding format of the system default locale is used. The system default locale and encoding format can be checked using the **locale** command as follows:<br />`omm@linux:~> locale|grep LC_CTYPE LC_CTYPE="en_US.UTF-8"`<br />**UTF-8** indicates the encoding format of the system default locale. |
+| --locale=LOCALE                                              | Specifies the default locale for the new database. You can run the **locale -a** command to view available locales, for example, `zh_CN.gbk`. If you do not want to specify a locale, set the parameter to **C**.<br />NOTICE:<br />If the encoding format of the database is set, the encoding format of the user specified area must be consistent with the encoding format set by the user. Otherwise, database initialization fails. | For example, to set the database encoding format to GBK, perform the following steps:<br />1. Run the `locale -a |grep gbk` command to check the locale that supports GBK encoding:<br />`omm@linux:~>  locale -a|grep gbk zh_CN.gbk zh_SG.gbk`<br />2. Add the `--locale=zh_CN.gbk` option when the database is initialized. |
+| --dbcompatibility=DBCOMPATIBILITY                            | Specifies the type of the compatible database.               | Value range: A, B, C, and PG, indicating **O**, **MY**, **TD**, and **POSTGRES** databases, respectively. |
+| --lc-collate=LOCALE--lc-ctype=LOCALE--lc-messages=LOCALE--lc-monetary=LOCALE--lc-numeric=LOCALE--lc-time=LOCALE | Sets the specified locale for a new database.                | The parameter values must be supported by the OS.<br />NOTE:<br />If the **--lc-collate** parameter is not specified when the database is installed, the default value of **--lc-collate** is **C**. |
+| --no-locale                                                  | Equivalent to **--locale=C**.                                | -                                                            |
+| --pwfile=FILE                                                | Reads the password for the database administrator from **FILE** during the running of **gs_initdb**. The first row of the file is taken as the password. | The format of **FILE** can be "a relative path+file" or "an absolute path+file". The relative path is relative to the current path. |
+| -T, --text-search-config=CFG                                 | Specifies the default text search mode. The value of this parameter is not verified. After the configuration is successful, a log is recorded to notify you of the value of this parameter. | Values of **text-search-config**:<br />- **english**: full-document search<br />- **simple**: common text search<br />Default value: **simple** |
+| -U, --username=NAME                                          | Selects the username of the database administrator.          | Value range: normal database users<br />Default value: OS user who runs **gs_initdb** |
+| -W, --pwprompt                                               | Prompts users to enter the password for the database administrator during the running of **gs_initdb**. | -                                                            |
+| -w, --pwpasswd=PASSWD                                        | Specifies the password of the database administrator by running commands during the running of **gs_initdb** instead of interactive input. | The password must meet the following complexity requirements:<br />- Contain at least eight characters.<br />- Cannot be the same as the username, the current password (ALTER), or the current password in an inverted sequence.<br />- Contain at least three of the following: uppercase characters (A to Z), lowercase characters (a to z), digits (0 to 9), and other characters |
+| -C, --enpwdfiledir=DIR                                       | Specifies the directory where the password encrypted is located, using the AES128 encryption algorithm during the running of **gs_initdb**. **gs_initdb** decrypts the password file in this directory and performs the password complexity check on the decrypted password. The password is used as the user's password if the check passes.<br />NOTE:<br />- The decrypted password file must use **gs_guc** to generate **gs_guc encrypt -K Gauss@123 -D Dir**.<br />- If multiple **-w** and **-C** parameters are specified, **gs_initdb** regards the last **-w** or **-C** parameter as the user's requirement (entering a plain-text password or a password encrypted using AES128). | -                                                            |
+| -X, --xlogdir=XLOGDIR                                        | Specifies the directory where the transaction logs are stored.<br />The directory must be a directory where an MogDB user has the read and write permissions. | The value must be an absolute path.                          |
+| -S, --security                                               | Initializes a database in a secure mode.                     | After the database is initialized using **-S**, the created database user permissions are restricted, and the **public schema** permission cannot be used any more by default. |
+
+**Table 2** Uncommon parameters <a id="uncommon"></a>
+
+| Parameter    | Description                                                  | Value Range                                               |
+| :----------- | :----------------------------------------------------------- | :-------------------------------------------------------- |
+| -d, -debug   | Prints debugging output from the bootstrap backend. The bootstrap backend is used by **gs_initdb** to create system catalogs. | -                                                         |
+| -L DIRECTORY | Specifies the input file path where the database is initialized using **gs_initdb**. This is unnecessary. You will be told if you need to specify their location explicitly. This parameter is used to create a database with specified configuration information. You are advised to copy all subdirectories and files related to startup in the **share/postgresql** directory to avoid impact of other factors. | Path of input files required by the initialized database. |
+| -n, -noclean | If this parameter is not specified and **gs_initdb** determines that an error prevents it from creating a database, it removes any files it might have created before discovering that it cannot finish the job. This option inhibits tidying-up and is useful for debugging. | -                                                         |
+| -s, -show    | Displays internal settings.                                  | -                                                         |
+| -V, -version | Prints the **gs_initdb** version and exits.                  | -                                                         |
+| -?, -help    | Displays help about **gs_initdb** command line parameters and exits. | -                                                         |
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/6-gs_install.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/6-gs_install.md
new file mode 100644
index 0000000000000000000000000000000000000000..de3e7ee0008b9ce2e44706a57ac319939feca382
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/6-gs_install.md
@@ -0,0 +1,127 @@
+---
+title: gs_install
+summary: gs_install
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_install
+
+## Background
+
+Database deployment is a complex process. **gs_install**, provided by MogDB, is used to install and deploy MogDB.
+
+Installation and deployment of MogDB require you to specify a configuration file, in which the program installation path, instance data directory, the primary/standby relationship, the number of instances, and the service IP address of each instance are specified.
+
+## Prerequisites
+
+- You have successfully executed the **gs_preinstall** script.
+- The **locale** parameter for each server is set to the same value.
+- MogDB users must be set during the preinstallation process.
+
+## Syntax
+
+- Install MogDB.
+
+  ```
+  gs_install -X XMLFILE [--gsinit-parameter="PARAMETER" [...]] [--dn-guc="PARAMETER" [...]] [--alarm-component=ALARMCOMPONENT] [--time-out=SECS] [-l LOGFILE]
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+
+- Display help information.
+
+  ```
+  gs_install -? | --help
+  ```
+
+- Display version information.
+
+  ```
+  gs_install -V | --version
+  ```
+
+## Parameter Description
+
+- -X
+
+  Specifies the MogDB configuration file.
+
+  Value range: XML configuration file
+
+- -l
+
+  Specifies a log file and its path.
+
+  When **-l** is not specified but **gaussdbLogPath** is set in the XML file, the default value of the **-l** parameter is the combination value of **gaussdbLogPath/User name/om/gs_install-YYYY-MM-DD_hhmmss.log**.
+
+- -gsinit-parameter=PARAM
+
+  Specifies the data instance parameters.
+
+  For details about the value range, see parameter description in **gs_initdb**. Among which, the settings of the **-A**, **-D**, **-U**, **-C**, and **-X** parameters do not take effect.
+
+- -dn-guc=PARAM
+
+  Set a parameter.
+
+  For details about the value range, see parameter description in **gs_guc**.
+
+- -time-out=SECS
+
+  Specifies the timeout threshold for startup. Unit: s
+
+  If the value of **-time-out** is too small, the instance startup may time out due to a large number of instances. If the instance failed to be started within the specified timeout period, an error will be reported. MogDB still runs at the backend. You can wait for a while and then query the MogDB status to check whether MogDB is started successfully.
+
+  Value range: a positive integer. If there is no special requirement, you do not need to set this parameter. The system automatically adjusts the timeout threshold.
+
+- -alarm-component=alarm_component
+
+  Specifies the absolute path of the component to report alarms.
+
+- -?, -help
+
+  Displays help information.
+
+- -V, -version
+
+  Displays version information.
+
+## Example
+
+Use **gs_install** to install MogDB.
+
+```
+gs_install -X /opt/software/mogdb/clusterconfig.xml
+Parsing the configuration file.
+Check preinstall on every node.
+Successfully checked preinstall on every node.
+Creating the backup directory.
+Successfully created the backup directory.
+begin deploy..
+Installing the cluster.
+begin prepare Install Cluster..
+Checking the installation environment on all nodes.
+begin install Cluster..
+Installing applications on all nodes.
+Successfully installed APP.
+begin init Instance..
+encrypt cipher and rand files for database.
+Please enter password for database:
+Please repeat for database:
+begin to create CA cert files
+The sslcert will be generated in /opt/gaussdb/cluster/app/share/sslcert/om
+Cluster installation is completed.
+Configuring.
+Deleting instances from all nodes.
+Successfully deleted instances from all nodes.
+Checking node configuration on all nodes.
+Initializing instances on all nodes.
+Updating instance configuration on all nodes.
+Check consistence of memCheck and coresCheck on DN nodes.
+Successful check consistence of memCheck and coresCheck on all nodes.
+Configuring pg_hba on all nodes.
+Configuration is completed.
+Successfully started cluster.
+Successfully installed application.
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/7-gs_postuninstall.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/7-gs_postuninstall.md
new file mode 100644
index 0000000000000000000000000000000000000000..9612a720dd7ec17950c0fa70760ce72f6264b9ae
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/7-gs_postuninstall.md
@@ -0,0 +1,121 @@
+---
+title: gs_postuninstall
+summary: gs_postuninstall
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_postuninstall
+
+## Background
+
+**gs_postuninstall**, provided by MogDB, is used to delete data configured before MogDB installation.
+
+## Prerequisites
+
+- The uninstallation of MogDB is successful.
+- User **root** is trustworthy and available.
+- Only user **root** is authorized to run the **gs_postuninstall** command.
+
+## Syntax
+
+- Delete the user, user group, and virtual IP address in MogDB.
+
+  ```
+  gs_postuninstall -U USER -X XMLFILE [-L] [--delete-user] [--delete-group] [-l LOGFILE]
+  ```
+
+- Display help information.
+
+  ```
+  gs_postuninstall -? | --help
+  ```
+
+- Display version information.
+
+  ```
+  gs_postuninstall -V | --version
+  ```
+
+## Parameter Description
+
+- -U
+
+  Specifies the OS username of MogDB.
+
+  Value range: a string. It must comply with the naming convention.
+
+- -X
+
+  Specifies the path of the MogDB configuration file.
+
+  Value range: storage paths of XML files
+
+- -L
+
+  Clears only the host environment.
+
+  If a host environment in MogDB is cleared, MogDB cannot perform full environment clearance.
+
+- -delete-user
+
+  Deletes the OS user specified by the **-U** parameter.
+
+  In the Red Hat environment, the username and the user group name are the same. If this parameter is specified, the **-delete-group** parameter must be specified.
+
+- -delete-group
+
+  Deletes the user group where the OS user belongs to (the **-delete-user** parameter must be specified when selecting this option).
+
+- -l
+
+Specifies a log file name and its path. A timestamp will be added automatically to the log file name.
+
+When **-l** is not specified and **gaussdbLogPath** is not set in the XML file, the default value of the **-l** parameter is **/var/log/gaussdb/om/gs_local-YYYY-MMDD_hhmmss.log**.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** After executing gs_postuninstall, the system will automatically delete the directories related to MogDB (including $GAUSSLOG). You are advised to set the log file path to a path outside the MogDB database.
+
+- -?, -help
+
+  Displays help information.
+
+- -V, -version
+
+  Displays version information.
+
+## Example
+
+Clear the host environment.
+
+```
+gs_postuninstall -U omm  -X /opt/software/mogdb/clusterconfig.xml --delete-user
+Parsing the configuration file.
+Successfully parsed the configuration file.
+Check log file path.
+Successfully checked log file path.
+Checking unpreinstallation.
+Successfully checked unpreinstallation.
+Deleting the instance's directory.
+Successfully deleted the instance's directory.
+Deleting the installation directory.
+Successfully deleted the installation directory.
+Deleting the temporary directory.
+Successfully deleted the temporary directory.
+Deleting remote OS user.
+Successfully deleted remote OS user.
+Deleting software packages and environmental variables of other nodes.
+Successfully deleted software packages and environmental variables of other nodes.
+Deleting logs of other nodes.
+Successfully deleted logs of other nodes.
+Deleting software packages and environmental variables of the local node.
+Successfully deleted software packages and environmental variables of the local nodes.
+Deleting local OS user.
+Successfully deleted local OS user.
+Deleting local node's logs.
+Successfully deleted local node's logs.
+Successfully cleaned environment.
+```
+
+## Helpful Links
+
+gs_preinstall and gs_uninstall
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/8-gs_preinstall.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/8-gs_preinstall.md
new file mode 100644
index 0000000000000000000000000000000000000000..cdf636a39263b1b9f68cc16003d615baa11dc8cb
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/8-gs_preinstall.md
@@ -0,0 +1,298 @@
+---
+title: gs_preinstall
+summary: gs_preinstall
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_preinstall
+
+## Background
+
+**gs_preinstall**, provided by MogDB, is used to configure the MogDB environment so that MogDB can be properly installed.
+
+## Precautions
+
+- You need to check the upper-layer directory permissions to ensure that the user has the read, write, and execution permissions on the installation package and configuration file directory.
+
+- The mapping between each host name and IP address in the XML configuration file must be correct.
+
+- Only user **root** is authorized to run the **gs_preinstall** command.
+
+- This product supports hybrid deployment of minor versions under major versions in the same OS. The supported list is as follows:
+
+  ```
+  CentOS 6.4/6.5/6.6/6.7/6.8/6.9
+  CentOS 7.0/7.1/7.2/7.3/7.4
+  openEuler
+  ```
+
+## Syntax
+
+- Prepare the MogDB environment.
+
+  ```
+  gs_preinstall -U USER -G GROUP -X XMLFILE [-L] [--skip-os-set] [--env-var="ENVVAR" [...]] [--sep-env-file=ENVFILE] [--skip-hostname-set] [-l LOGFILE] [--non-interactive]
+  ```
+
+- Display help information.
+
+  ```
+  gs_preinstall -? | --help
+  ```
+
+- Display version information.
+
+  ```
+  gs_preinstall -V | --version
+  ```
+
+## Parameter Description
+
+- -U
+
+  Specifies the name of the OS user running MogDB.
+
+  Value range: a string. It must comply with the naming convention.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The value of **-U** cannot contain double backslashes () or the following characters: |;&$&lt;&gt;`'\"{}()[]~*?"
+
+- -G
+
+  Specifies the name of the OS user group running MogDB.
+
+  Value range: a string. It must comply with the naming convention.
+
+- -X
+
+  Specifies the path of the MogDB configuration file.
+
+  Value range: storage paths of XML files
+
+- -L
+
+  Prepares MogDB installation environment for the current nodes only. This parameter is used in the scenarios where the trust relationship of user **root** is not allowed and where the security hardening parameter **PermitRootLogin** is set to **no**. The following prerequisites must be met:
+
+  1. The installation package and MogDB configuration file have been uploaded to all the hosts.
+  2. The MogDB installation user has been created and mutual trust relationships have been established.
+  3. All the commands executed on all the hosts are consistent.
+  4. The mapping relationships between hostnames and IP addresses of all nodes need to be manually written to /etc/hosts on each host, and the comment content **#Gauss OM IP Hosts Mapping** must be added.
+
+- -skip-os-set
+
+  Specifies whether to set the parameter for the OS. By default, the parameter is set for the OS. If the parameter is specified, the configuration is dropped.
+
+- -env-var="ENVVAR"
+
+  Sets the environment variable for common users. You can specify multiple environment variables.
+
+  Value range: a string.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** This parameter cannot be set to the environment variable created by MogDB by default. Otherwise, the environment variables of the MogDB will be overwritten. [Table 1](#environment) lists the environment variables created by MogDB by default.
+
+- -sep-env-file=ENVFILE
+
+  Saves environment variable files. If this parameter is specified, the split version of environment variable is used.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The environment variable file name cannot be specified the same as that of the corresponding MogDB directories or those directories, or the directory of the MogDB user.
+
+- -skip-hostname-set
+
+  Specifies whether to write the mapping relationship between the host name and IP address of the XML configuration file to the **/etc/hosts** file. By default, the relationship is written to the file. If this parameter is specified, the relationship is not written to the file.
+
+- -l
+
+Specifies a log file name and its path. A timestamp will be added automatically to the log file name.
+
+Default value: **/var/log/gaussdb/\*user name\*/om/gs_preinstall.log**
+
+When **-l** is not specified but **gaussdbLogPath** is set in the XML file, the default value of the **-l** parameter is a combination of **gaussdbLogPath** value, the user name, and **om/gs_preinstall-YYYY-MM-DD_hhmmss.log**.
+
+- -non-interactive
+
+  Specifies the preinstallation execution mode.
+
+  - When this parameter is not specified, the secure interactive mode is used where you need to enter the password for man-machine interaction.
+  - If this parameter is specified, the non-interactive mode is used and man-machine interaction is not required.
+
+- -?, -help
+
+  Displays help information.
+
+- -V, -version
+
+  Displays version information.
+
+  **Table 1** Environment variables created by MogDB by default <a id="environment"></a>
+
+  | Environment Variable    | Description                                           |
+  | :---------------------- | :---------------------------------------------------- |
+  | MPPDB_ENV_SEPARATE_PATH | Split file path of the MogDB environment variable     |
+  | GPHOME                  | MogDB tool directory                                  |
+  | PATH                    | MogDB tool script directory                           |
+  | LD_LIBRARY_PATH         | Third-party dynamic database path referenced by MogDB |
+  | PYTHONPATH              | Python software path                                  |
+  | GAUSS_WARNING_TYPE      | Alarm type                                            |
+  | GAUSSHOME               | MogDB installation path                               |
+  | GAUSS_VERSION           | MogDB version                                         |
+  | PGHOST                  | Temporary directory of the user in MogDB              |
+  | GS_CLUSTER_NAME         | MogDB name                                            |
+  | GAUSSLOG                | MogDB log path                                        |
+  | GAUSS_ENV               | Environment variable flag of MogDB                    |
+
+## Manually Setting Syslog on the Server
+
+Add the following content to the **/etc/syslog-ng/syslog-ng.conf** file:
+
+```bash
+template t_gaussdb {template("$DATE $SOURCEIP $MSGONLY\n");template_escape(no);};
+source s_gaussdb{ udp(); };
+filter f_gaussdb    { level(err,  crit) and match('GaussDB'); };
+destination d_gaussdb { file("/var/log/syslog_MPPDB", template(t_gaussdb)); };
+log { source(s_gaussdb); filter(f_gaussdb); destination(d_gaussdb); };
+```
+
+Add the following content to the **/etc/sysconfig/syslog** file:
+
+```bash
+SYSLOGD_OPTIONS="-r -m 0"
+KLOGD_OPTIONS="-x"
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** You need to perform the operations on every host in MogDB.
+
+## Example
+
+Prepare MogDB environment in non-interactive mode.
+
+```bash
+./gs_preinstall -U omm -G dbgrp -X /opt/software/mogdb/clusterconfig.xml --non-interactive
+Parsing the configuration file.
+Successfully parsed the configuration file.
+Installing the tools on the local node.
+Successfully installed the tools on the local node.
+Distributing package.
+Successfully distributed package.
+Installing the tools in the cluster.
+Successfully installed the tools in the cluster.
+Checking hostname mapping.
+Successfully checked hostname mapping.
+Checking OS version.
+Successfully checked OS version.
+Creating cluster's path.
+Successfully created cluster's path.
+Set and check OS parameter.
+Setting OS parameters.
+Successfully set OS parameters.
+Warning: Installation environment contains some warning messages.
+Please get more details by "/package_r8/sudo/gs_checkos -i A -h host179174,host179175,host179176".
+Set and check OS parameter completed.
+Preparing CRON service.
+Successfully prepared CRON service.
+Preparing SSH service.
+Successfully prepared SSH service.
+Setting user environmental variables.
+Successfully set user environmental variables.
+Configuring alarms on the cluster nodes.
+Successfully configured alarms on the cluster nodes.
+Setting the dynamic link library.
+Successfully set the dynamic link library.
+Setting finish flag.
+Successfully set finish flag.
+Preinstallation succeeded.
+```
+
+Prepare MogDB environment in interactive mode.
+
+```bash
+./gs_preinstall -U omm -G dbgrp -X /opt/software/mogdb/clusterconfig.xml
+Parsing the configuration file.
+Successfully parsed the configuration file.
+Installing the tools on the local node.
+Successfully installed the tools on the local node.
+Are you sure you want to create trust for root (yes/no)? yes
+Please enter password for root.
+Password:
+Creating SSH trust for the root permission user.
+Please enter password for current user[root].
+Password:
+Checking network information.
+All nodes in the network are Normal.
+Successfully checked network information.
+Creating SSH trust.
+Creating the local key file.
+Successfully created the local key files.
+Appending local ID to authorized_keys.
+Successfully appended local ID to authorized_keys.
+Updating the known_hosts file.
+Successfully updated the known_hosts file.
+Appending authorized_key on the remote node.
+Successfully appended authorized_key on all remote node.
+Checking common authentication file content.
+Successfully checked common authentication content.
+Distributing SSH trust file to all node.
+Successfully distributed SSH trust file to all node.
+Verifying SSH trust on all hosts.
+Successfully verified SSH trust on all hosts.
+Successfully created SSH trust.
+Successfully created SSH trust for the root permission user.
+Distributing package.
+Successfully distributed package.
+Are you sure you want to create the user[omm] and create trust for it (yes/no)? yes
+Please enter password for cluster user.
+Password:
+Please enter password for cluster user again.
+Password:
+Creating [omm] user on all nodes.
+Successfully created [omm] user on all nodes.
+Installing the tools in the cluster.
+Successfully installed the tools in the cluster.
+Checking hostname mapping.
+Successfully checked hostname mapping.
+Creating SSH trust for [omm] user.
+Please enter password for current user[omm].
+Password:
+Checking network information.
+All nodes in the network are Normal.
+Successfully checked network information.
+Creating SSH trust.
+Creating the local key file.
+Successfully created the local key files.
+Appending local ID to authorized_keys.
+Successfully appended local ID to authorized_keys.
+Updating the known_hosts file.
+Successfully updated the known_hosts file.
+Appending authorized_key on the remote node.
+Successfully appended authorized_key on all remote node.
+Checking common authentication file content.
+Successfully checked common authentication content.
+Distributing SSH trust file to all node.
+Successfully distributed SSH trust file to all node.
+Verifying SSH trust on all hosts.
+Successfully verified SSH trust on all hosts.
+Successfully created SSH trust.
+Successfully created SSH trust for [omm] user.
+Checking OS version.
+Successfully checked OS version.
+Creating cluster's path.
+Successfully created cluster's path.
+Set and check OS parameter.
+Setting OS parameters.
+Successfully set OS parameters.
+Warning: Installation environment contains some warning messages.
+Please get more details by "/package_r8/sudo/gs_checkos -i A -h host179174,host179175,host179176".
+Set and check OS parameter completed.
+Preparing CRON service.
+Successfully prepared CRON service.
+Preparing SSH service.
+Successfully prepared SSH service.
+Setting user environmental variables.
+Successfully set user environmental variables.
+Configuring alarms on the cluster nodes.
+Successfully configured alarms on the cluster nodes.
+Setting the dynamic link library.
+Successfully set the dynamic link library.
+Setting finish flag.
+Successfully set finish flag.
+Preinstallation succeeded.
+```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/9-gs_sshexkey.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/9-gs_sshexkey.md
new file mode 100644
index 0000000000000000000000000000000000000000..1228004ed1475564395b13d3d57ac24e5753c10d
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/9-gs_sshexkey.md
@@ -0,0 +1,161 @@
+---
+title: gs_sshexkey
+summary: gs_sshexkey
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_sshexkey
+
+## Background
+
+During the MogDB installation, you need to perform operations such as running commands and transferring files between hosts in MogDB. Establish mutual trust among the hosts before the installation. gs_sshexkey, provided by MogDB, is used to establish such relationships.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** The mutual trust between users **root** may incur security risks. You are advised to delete the mutual trust between users **root** after the installation is complete.
+
+## Prerequisites
+
+- The SSH service has been enabled.
+
+- You have verified that SSH ports will not be disabled by firewalls.
+
+- Each host name and IP address have been correctly configured in the XML file.
+
+- Communication among all the hosts is normal.
+
+- If the mutual trust is to be established for common users, the same user needs to be created and password set on each host.
+
+- If the SELinux service is installed and has been started on each host, ensure that the security context of the **/root** directory is set to the default value **system_u:object_r:home_root_t:s0** and that of the **/home** directory is set to the default value **system_u:object_r:admin_home_t:s0**, or disable the SELinux service.
+
+  To check the SELinux status, run the **getenforce** command. If the command output is **Enforcing**, SELinux is installed and has been enabled.
+
+  To check the security contexts of the directories, run the following commands:
+
+  ```
+  ls -ldZ  /root | awk '{print $4}'
+  ```
+
+  ```
+  ls -ldZ  /home | awk '{print $4}'
+  ```
+
+  To restore the security contexts of the directories, run the following commands:
+
+  ```
+  restorecon -r -vv /home/
+  ```
+
+  ```
+  restorecon -r -vv /root/
+  ```
+
+## Syntax
+
+- Establish mutual trust.
+
+  ```
+  gs_sshexkey -f HOSTFILE  [...] [--skip-hostname-set] [-l LOGFILE]
+  ```
+
+- Display help information.
+
+  ```
+  gs_sshexkey -? | --help
+  ```
+
+- Display version information.
+
+  ```
+  gs_sshexkey -V | --version
+  ```
+
+## Parameter Description
+
+- -f
+
+  Lists the IP addresses of all the hosts among which mutual trust relationships need to be established.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** You need to ensure that only correct IP addresses are configured in the **hostfile** file without containing other information.
+
+- -h
+
+  Host IP list, separated by commas between multiple nodes.
+
+- -l
+
+  Specifies the path for saving log files.
+
+  Value range: existing, accessible absolute paths
+
+- -skip-hostname-set
+
+  Specifies whether to write the mapping relationship between the host name and IP address of the **-f** parameter file to the **/etc/hosts** file. By default, the relationship is written to the file. If this parameter is specified, the relationship is not written to the file.
+
+- -?, -help
+
+  Displays help information.
+
+- -V, -version
+
+  Displays version information.
+
+## Example
+
+The following examples describe how to establish mutual trust relationships for user **root**. Passwords can be entered only in interactive mode.
+
+- In interactive mode, if the user passwords are the same, run the following commands to establish mutual trust:
+
+  ```
+  gs_sshexkey -f /opt/software/hostfile
+  Please enter password for current user[root].
+  Password:
+  Checking network information.
+  All nodes in the network are Normal.
+  Successfully checked network information.
+  Creating SSH trust.
+  Creating the local key file.
+  Appending local ID to authorized_keys.
+  Successfully appended local ID to authorized_keys.
+  Updating the known_hosts file.
+  Successfully updated the known_hosts file.
+  Appending authorized_key on the remote node.
+  Successfully appended authorized_key on all remote node.
+  Checking common authentication file content.
+  Successfully checked common authentication content.
+  Distributing SSH trust file to all node.
+  Successfully distributed SSH trust file to all node.
+  Verifying SSH trust on all hosts.
+  Successfully verified SSH trust on all hosts.
+  Successfully created SSH trust.
+  ```
+
+- In interactive mode, if the user passwords are different, run the following commands to establish mutual trust:
+
+  ```
+  gs_sshexkey -f /opt/software/hostfile
+  Please enter password for current user[root].
+  Password:
+  Notice :The password of some nodes is incorrect.
+  Please enter password for current user[root] on the node[10.180.10.112].
+  Password:
+  Please enter password for current user[root] on the node[10.180.10.113].
+  Password:
+  Checking network information.
+  All nodes in the network are Normal.
+  Successfully checked network information.
+  Creating SSH trust.
+  Creating the local key file.
+  Appending local ID to authorized_keys.
+  Successfully appended local ID to authorized_keys.
+  Updating the known_hosts file.
+  Successfully updated the known_hosts file.
+  Appending authorized_key on the remote node.
+  Successfully appended authorized_key on all remote node.
+  Checking common authentication file content.
+  Successfully checked common authentication content.
+  Distributing SSH trust file to all node.
+  Successfully distributed SSH trust file to all node.
+  Verifying SSH trust on all hosts.
+  Successfully verified SSH trust on all hosts.
+  Successfully created SSH trust.
+  ```
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/gs_install_plugin.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/gs_install_plugin.md
new file mode 100644
index 0000000000000000000000000000000000000000..826b4c9e80ae356c1fdcbeec469ab20ffdd8a4eb
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/gs_install_plugin.md
@@ -0,0 +1,166 @@
+---
+title: gs_install_plugin
+summary: gs_install_plugin
+author: Guo Huan
+date: 2021-11-29
+---
+
+# gs_install_plugin
+
+## Background
+
+MogDB provides gs_install_plugin for installing plugins. Currently, the supported plugins include pg_repack, pg_trgm, dblink, wal2json, orafce, pg_bulkload, and pg_prewarm. This tool is suitable for MogDB deployed with one primary node and multiple standby nodes.
+
+&nbsp;
+
+## Prerequisites
+
+The deployment of MogDB with one primary node and multiple standby nodes has been completed.
+
+## Syntax
+
+```
+gs_install_plugin [-h] [-X XML] [--all] [--dblink] [--pg_trgm] [--wal2json] [--pg_repack] [--orafce] [--pg_bulkload] [--pg_prewarm] [--plugins PLUGINS [PLUGINS ...]]
+```
+
+&nbsp;
+
+## Parameter Description
+
+- -h
+
+  show help message and exit
+
+- -X
+
+  Add the location of the MogDB clusterconfig.xml file.
+
+- --all
+
+  Install all plugins.
+
+- --plugins
+
+  Multiple parameters can be accepted, for example: --plugins dblink pg_repack wal2json
+
+- --dblink
+
+  Install dblink plugin.
+
+- --pg_trgm
+
+  Install pg_trgm plugin.
+
+- --wal2json
+
+  Install wal2json plugin.
+
+- --pg_repack
+
+  Install pg_repack plugin.
+
+- --orafce
+
+  Install orafce plugin.
+
+- --pg_bulkload
+
+  Install pg_bulkload plugin.
+
+&nbsp;
+
+## Example
+
+1. Go to the **script** folder of the database installation directory.
+
+   ```bash
+   cd /opt/software/mogdb/script/
+   ```
+
+2. Create the **static** folder.
+
+   ```bash
+   mkdir -p static
+   ```
+
+    > Note: Please do not change the folder name.
+
+3. Visit [MogDB official website download page](https://www.mogdb.io/en/downloads/mogdb/), download the corresponding version of the plugin according to your operating system and CPU architecture, and put the plugin in the **static** folder.
+
+4. Set permissions.
+
+    ```
+    chmod -R 755 /opt/software/mogdb/script
+    chown -R omm:dbgrp /opt/software/mogdb/script
+    ```
+
+5. Configure XML File. The XML file configuration uses one primary and one standby configuration file as an example. `backIp1s` is the IP address of a node, and `dataNode1` is the data directory. The data directory obtained by this program by default is the data directory of the first node.
+
+    ```xml
+    <?xml version="1.0" encoding="UTF-8"?>
+    <ROOT>
+        <!-- Overall information about MogDB -->
+        <CLUSTER>
+            <PARAM name="clusterName" value="dbCluster" />
+            <PARAM name="nodeNames" value="node1,node2" />
+            <PARAM name="backIp1s" value="192.168.0.11,192.168.0.12"/>
+            <PARAM name="gaussdbAppPath" value="/opt/mogdb/app" />
+            <PARAM name="gaussdbLogPath" value="/var/log/mogdb" />
+            <PARAM name="gaussdbToolPath" value="/opt/mogdb/tools" />
+            <PARAM name="corePath" value="/opt/mogdb/corefile"/>
+            <PARAM name="clusterType" value="single-inst"/>
+        </CLUSTER>
+        <!-- Information about node deployment on each server -->
+        <DEVICELIST>
+            <!-- Information about the node deployment on node1 -->
+            <DEVICE sn="1000001">
+                <PARAM name="name" value="node1"/>
+                <PARAM name="azName" value="AZ1"/>
+                <PARAM name="azPriority" value="1"/>
+                <!-- If only one NIC is available for the server, set backIP1 and sshIP1 to the same IP address. -->
+                <PARAM name="backIp1" value="192.168.0.11"/>
+                <PARAM name="sshIp1" value="192.168.0.11"/>
+
+                <!--dbnode-->
+                <PARAM name="dataNum" value="1"/>
+                <PARAM name="dataPortBase" value="26000"/>
+                <PARAM name="dataNode1" value="/mogdb/data/db1,node2,/mogdb/data/db1"/>
+            </DEVICE>
+
+            <!-- Node deployment information on node2. The value of name is the host name.  -->
+            <DEVICE sn="1000002">
+                <PARAM name="name" value="node2"/>
+                <PARAM name="azName" value="AZ1"/>
+                <PARAM name="azPriority" value="1"/>
+                <!-- If only one NIC is available for the server, set backIP1 and sshIP1 to the same IP address. -->
+                <PARAM name="backIp1" value="192.168.0.12"/>
+                <PARAM name="sshIp1" value="192.168.0.12"/>
+            </DEVICE>
+        </DEVICELIST>
+    </ROOT>
+    ```
+
+6. Switch to omm user.
+
+    ```
+    su - omm
+    ```
+
+7. Install all plugins.
+
+    ```bash
+    /opt/software/mogdb/script/gs_install_plugin -X /opt/software/mogdb/clusterconfig.xml --all
+
+    # When the installation is successful, the output is as follows:
+    SUCCESS: dblink.
+    SUCCESS: pg_trgm.
+    SUCCESS: pg_repack.
+    SUCCESS: wal2json.
+    SUCCESS: orafce.
+    SUCCESS: pg_bulkload.
+    SUCCESS: pg_prewarm.
+    ```
+
+## Related Pages
+
+[orafce](orafce-user-guide), [dblink](dblink-user-guide), [pg_repack](pg_repack-user-guide), [pg_trgm](pg_trgm-user-guide), [wal2json](wal2json-user-guide), [pg_bulkload](pg_bulkload-user-guide), [pg_prewarm](pg_prewarm-user-guide).
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/gs_install_plugin_local.md b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/gs_install_plugin_local.md
new file mode 100644
index 0000000000000000000000000000000000000000..b8454731b5be75b32b237250a4425cfa046779f2
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/gs_install_plugin_local.md
@@ -0,0 +1,157 @@
+---
+title: gs_install_plugin_local
+summary: gs_install_plugin_local
+author: Guo Huan
+date: 2021-11-29
+---
+
+# gs_install_plugin_local
+
+## Background
+
+MogDB provides gs_install_plugin_local for installing plugins. Currently, the supported plugins include pg_repack, pg_trgm, dblink, wal2json, orafce, pg_bulkload, and pg_prewarm. This tool is suitable for MogDB single node deployment.
+
+&nbsp;
+
+## Prerequisites
+
+The deployment of MogDB single node has been completed.
+
+## Syntax
+
+```
+gs_install_plugin_local [-h] [-X XML] [--all] [--dblink] [--pg_trgm] [--wal2json] [--pg_repack] [--orafce] [--pg_bulkload] [--pg_prewarm] [--plugins PLUGINS [PLUGINS ...]]
+```
+
+&nbsp;
+
+## Parameter Description
+
+- -h
+
+  show help message and exit
+
+- -X
+
+  Add the location of the MogDB clusterconfig.xml file.
+
+- --all
+
+  Install all plugins.
+
+- --plugins
+
+  Multiple parameters can be accepted, for example: --plugins dblink pg_repack wal2json
+
+- --dblink
+
+  Install dblink plugin.
+
+- --pg_trgm
+
+  Install pg_trgm plugin.
+
+- --wal2json
+
+  Install wal2json plugin.
+
+- --pg_repack
+
+  Install pg_repack plugin.
+
+- --orafce
+
+  Install orafce plugin.
+
+- --pg_bulkload
+
+  Install pg_bulkload plugin.
+
+&nbsp;
+
+## Example
+
+1. Go to the **script** folder of the database installation directory.
+
+   ```bash
+   cd /opt/software/mogdb/script/
+   ```
+
+2. Create the **static** folder.
+
+   ```bash
+   mkdir -p static
+   ```
+
+    > Note: Please do not change the folder name.
+
+3. Visit [MogDB official website download page](https://www.mogdb.io/en/downloads/mogdb/), download the corresponding version of the plugin according to your operating system and CPU architecture, and put the plugin in the **static** folder.
+
+4. Set permissions.
+
+    ```
+    chmod -R 755 /opt/software/mogdb/script
+    chown -R omm:dbgrp /opt/software/mogdb/script
+    ```
+
+5. Configure XML File. The XML file configuration uses single node configuration file as an example. `backIp1s` is the IP address of a node, and `dataNode1` is the data directory. The data directory obtained by this program by default is the data directory of the first node.
+
+    ```xml
+    <?xml version="1.0" encoding="UTF-8"?>
+    <ROOT>
+        <!-- Overall information about MogDB -->
+        <CLUSTER>
+            <PARAM name="clusterName" value="dbCluster" />
+            <PARAM name="nodeNames" value="node1" />
+            <PARAM name="backIp1s" value="192.168.0.11"/>
+            <PARAM name="gaussdbAppPath" value="/opt/mogdb/app" />
+            <PARAM name="gaussdbLogPath" value="/var/log/mogdb" />
+            <PARAM name="gaussdbToolPath" value="/opt/mogdb/tools" />
+            <PARAM name="corePath" value="/opt/mogdb/corefile"/>
+            <PARAM name="clusterType" value="single-inst"/>
+        </CLUSTER>
+
+        <!-- Information about node deployment on each server  -->
+        <DEVICELIST>
+            <!-- Information about the node deployment on node1  -->
+            <DEVICE sn="1000001">
+                <PARAM name="name" value="node1"/>
+                <PARAM name="azName" value="AZ1"/>
+                <PARAM name="azPriority" value="1"/>
+                <!-- If only one NIC is available for the server, set backIP1 and sshIP1 to the same IP address. -->
+                <PARAM name="backIp1" value="192.168.0.11"/>
+                <PARAM name="sshIp1" value="192.168.0.11"/>
+
+                <!--dbnode-->
+                <PARAM name="dataNum" value="1"/>
+                <PARAM name="dataPortBase" value="26000"/>
+                <PARAM name="dataNode1" value="/mogdb/data/db1"/>
+            </DEVICE>
+        </DEVICELIST>
+    </ROOT>
+    ```
+
+6. Switch to omm user.
+
+    ```
+    su - omm
+    ```
+
+7. Install all plugins.
+
+    ```bash
+    /opt/software/mogdb/script/gs_install_plugin_local -X /opt/software/mogdb/clusterconfig.xml --all
+
+    # When the installation is successful, the output is as follows:
+    SUCCESS: dblink.
+    SUCCESS: pg_trgm.
+    SUCCESS: pg_repack.
+    SUCCESS: wal2json.
+    SUCCESS: orafce.
+    SUCCESS: pg_bulkload.
+    SUCCESS: pg_prewarm.
+    ```
+
+## Related Pages
+
+[orafce](orafce-user-guide), [dblink](dblink-user-guide), [pg_repack](pg_repack-user-guide), [pg_trgm](pg_trgm-user-guide), [wal2json](wal2json-user-guide), [pg_bulkload](pg_bulkload-user-guide), [pg_prewarm](pg_prewarm-user-guide).
diff --git a/product/en/docs-mogdb/v3.0/security-guide/security/1-client-access-authentication.md b/product/en/docs-mogdb/v3.0/security-guide/security/1-client-access-authentication.md
new file mode 100644
index 0000000000000000000000000000000000000000..88d29cd401273468c44d7f2d8447c6b2af305846
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/security-guide/security/1-client-access-authentication.md
@@ -0,0 +1,769 @@
+---
+title: Client Access Authentication
+summary: Client Access Authentication
+author: Guo Huan
+date: 2021-04-26
+---
+
+# Client Access Authentication
+
+## Configuring Client Access Authentication
+
+**Background**
+
+If a host needs to connect to a database remotely, you need to add information about the host in configuration file of the database system and perform client access authentication. The configuration file (**pg_hba.conf** by default) is stored in the data directory of the database. HBA is short for host-based authentication.
+
+- The system supports the following three authentication methods, which all require the **pg_hba.conf** file.
+
+  - Host-based authentication: A server checks the configuration file based on the IP address, username, and target database of the client to determine whether the user can be authenticated.
+  - Password authentication: A password can be an encrypted password for remote connection or a non-encrypted password for local connection.
+  - SSL encryption: The OpenSSL is used to provide a secure connection between the server and the client.
+
+- In the **pg_hba.conf** file, each record occupies one row and specifies an authentication rule. An empty row or a row started with a number sign (#) is neglected.
+
+- Each authentication rule consists of multiple columns separated by spaces and forward slashes (/), or spaces and tab characters. If a field is enclosed with quotation marks ("), it can contain spaces. One record cannot span different rows.
+
+**Procedure**
+
+1. Log in as the OS user **omm** to the primary node of the database.
+
+2. Configure the client authentication mode and enable the client to connect to the host as user **jack**. User **omm** cannot be used for remote connection.
+
+   Assume you are to allow the client whose IP address is **10.10.0.30** to access the current host.
+
+   ```bash
+   gs_guc set -N all -I all -h "host all jack 10.10.0.30/32 sha256"
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+   >
+   > - Before using user **jack**, connect to the database locally and run the following command in the database to create user **jack**:
+   >
+   >     ```sql
+   >     mogdb=# CREATE USER jack PASSWORD 'Test@123';
+   >     ```
+   >
+   > - **-N all** indicates all hosts in MogDB.
+   > - **-I all** indicates all instances on the host.
+   > - **-h** specifies statements that need to be added in the **pg_hba.conf** file.
+   > - **all** indicates that a client can connect to any database.
+   > - **jack** indicates the user that accesses the database.
+   > - **10.10.0.30*/*32** indicates that only the client whose IP address is **10.10.0.30** can connect to the host. The specified IP address must be different from those used in MogDB. **32** indicates that there are 32 bits whose value is 1 in the subnet mask. That is, the subnet mask is 255.255.255.255.
+   > - **sha256** indicates that the password of user **jack** is encrypted using the SHA-256 algorithm.
+
+This command adds a rule to the **pg_hba.conf** file corresponds to the primary node of the database. The rule is used to authenticate clients that access primary node.
+
+Each record in the **pg_hba.conf** file can be in one of the following four formats. For parameter description of the four formats, see [Configuration File Reference](#configuration-file-reference).
+
+```text
+local     DATABASE USER METHOD [OPTIONS]
+host      DATABASE USER ADDRESS METHOD [OPTIONS]
+hostssl   DATABASE USER ADDRESS METHOD [OPTIONS]
+hostnossl DATABASE USER ADDRESS METHOD [OPTIONS]
+```
+
+During authentication, the system checks records in the **pg_hba.conf** file in sequence for connection requests, so the record sequence is vital.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> Configure records in the **pg_hba.conf** file from top to bottom based on communication and format requirements in the descending order of priorities. The IP addresses of the MogDB cluster and added hosts are of the highest priority and should be configured prior to those manually configured by users. If the IP addresses manually configured by users and those of added hosts are in the same network segment, delete the manually configured IP addresses before the scale-out and configure them after the scale-out.
+
+The suggestions on configuring authentication rules are as follows:
+
+- Records placed at the front have strict connection parameters but weak authentication methods.
+- Records placed at the end have weak connection parameters but strict authentication methods.
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - If a user wants to connect to a specified database, the user must be authenticated by the rules in the **pg_hba.conf** file and have the **CONNECT** permission for the database. If you want to restrict a user from connecting to certain databases, you can grant or revoke the user's **CONNECT** permission, which is easier than setting rules in the **pg_hba.conf** file.
+> - The **trust** authentication mode is insecure for a connection between the MogDB and a client outside the cluster. In this case, set the authentication mode to **sha256**.
+
+**Exception Handling**
+
+There are many reasons for a user authentication failure. You can view an error message returned from a server to a client to determine the exact cause. [Table 1](#Table-1.1.1) lists common error messages and solutions to these errors.
+
+**Table 1** Error messages<a id="Table-1.1.1"> </a>
+
+| Symptom                                        | Solution                                         |
+| :---------------------------------------------- | :-------------------------------------------------- |
+| The username or password is incorrect.<br/>`FATAL: invalid username/password,login denied`                                  | Retry the authentication with the correct username and password.                                                                                                                                                                             |
+| The database to connect does not exist.<br/>`FATAL: database "TESTDB" does not exist`                                       | Retry the authentication with the correct database name.                                                                                                                                                                                     |
+| No matched client record is found.<br/>`FATAL: no pg_hba.conf entry for host "10.10.0.60", user "ANDYM", database "TESTDB"` | This message indicates that the server is connected but denies the connection request, because it does not find a matched record in **pg_hba.conf**. Contact the database administrator to add user information to the **pg_hba.conf** file. |
+
+**Example**
+
+```
+TYPE  DATABASE        USER            ADDRESS                 METHOD
+
+#Allow only the user specified by the -U parameter (omm as default) during installation to establish a connection from the local server.
+local   all             omm                                     trust
+IPv4 local connections:
+#User  jack  is allowed to connect to any database from the 10.10.0.50 host. The SHA-256 algorithm is used to encrypt the password.
+host    all           jack             10.10.0.50/32            sha256
+#Any user is allowed to connect to any database from a host on the 10.10.0.0/24 network segment. The SHA-256 algorithm is used to encrypt the password and SSL transmission is used.
+hostssl    all             all             10.10.0.0/24            sha256
+#Any user is allowed to connect to any database from a host on the 10.10.0.0/24 network segment. The Kerberos authentication is used. In the current version, Kerberos authentication cannot be used to connect to external clients.
+host    all             all             10.10.0.0/24            gss         include_realm=1        krb_realm=HADOOP.COM
+```
+
+## Configuration File Reference
+
+**Table 2** Parameter description
+
+| Parameter   | Description                  | Value Range                      |
+| :---------- | :--------------------------- | :----------------------------------|
+| local       | Indicates that this record accepts only the Unix-domain-socket connection. If no such type of record exists, Unix-domain-socket connections are not allowed.<br/>When **gsql** is used to initiate a connection from a local server and the **-U** parameter is not specified, a Unix-domain-socket connection is established. | -                                                            |
+| host        | Indicates that this record accepts either a common TCP/IP-socket connection or a TCP/IP-socket connection encrypted through SSL. | -                                                            |
+| hostssl     | Indicates that this record accepts only a TCP/IP socket connection encrypted through SSL. | For the connection encrypted through SSL, you need to apply for a digital certificate and configure related parameters. For details, see [Establishing Secure TCP/IP Connections in SSL Mode](#establishing-secure-tcpip-connections-in-ssl-mode). |
+| hostnossl   | Indicates that this record accepts only a common TCP/IP socket connection. | -                                                            |
+| DATABASEGUC | Database that a record matches and can access                | - **all**: indicates that this record matches all databases.<br/>- **sameuser**: indicates that the database must have the same name as the user who requests database access.<br/>- **samerole**: indicates that this record matches a database if the user who requests the database is a member of a role having the same name as the database.<br/>- **samegroup**: is the same as that of **samerole** and indicates that this record matches a database if the user who requests the database is a member of a role having the same name as the database.<br/>- A file containing database names with an at sign (@) added before the file name, or a database list in a file using commas (,) or line feeds to separate databases.<br/>- A specific database name or a list of databases separated by commas (,)<br/>NOTE:<br/>**replication** indicates that if a replication link is requested, the records match the link. But this does not mean the record matches any specific database. To use a database named **replication**, specify it in the database column. |
+| USER        | Users who match the record and are allowed to access databases | - **all**: indicates that this record matches all users.<br/>- **+User role**: indicates that this record matches all members that directly or indirectly belong to the role.<br/>NOTE:<br/>**+** is a prefix character.<br/>- A file containing usernames, with an at sign (@) added before the file name. Users in the file are separated by commas (,) or line feeds.<br/>- A specific database username or a list of users separated by commas (,) |
+| ADDRESS     | Range of IP addresses that match the record and can be visited | IPv4 and IPv6 are supported. The IP address range can be expressed in the following two formats:<br/>- **IP address/mask length** Example: 10.10.0.0/24<br/>- **IP address Subnet mask** Example: 10.10.0.0 255.255.255.0<br/>NOTE:<br/>An IPv4 address matches the IPv6 connection with the corresponding address. For example, 127.0.0.1 matches IPv6 address ::ffff:127.0.0.1. |
+| METHOD      | Authentication method used for connection                    | The following authentication modes are supported. For details, see [Table 3](#Table 1.2.2).<br/>- **trust**<br/>- **reject**<br/>- **md5** (not recommended and not supported by default. This authentication mode can be configured using the **password_encryption_type** parameter.)<br/>NOTE:<br />The MD5 encryption algorithm has lower security and poses security risks. Therefore, you are advised to use a more secure encryption algorithm.<br />- **sha256**<br/>- **sm3**<br />- **cert**<br/>- **gss** (only for authentication within MogDB)<br />- **peer** (only for the local mode) |
+
+**Table 3** Authentication modes<a id="Table-1.2.2"> </a>
+
+| Authentication Mode | Remarks                                                      |
+| :------------------ | :----------------------------------------------------------- |
+| trust               | In trust mode, only the connection initiated from the local server using **gsql** with the **-U** parameter not specified is trusted. In this case, no password is required.<br/>The trust authentication mode applies to local connection of a single-user workstation, but not of a multi-user workstation. To use the trust authentication, you can use the file system permissions to control the access to the Unix-domain socket file on the server. You can use either of the following methods to control the access:<br/>- Set the **unix_socket_permissions** and **unix_socket_group** parameters.<br/>- Set the **unix_socket_directory** parameter to place Unix-domain socket files into a directory requiring certain access permissions.<br/>NOTICE:<br/>Setting the file system permission imposes restrictions on only Unix-domain socket connections, and does not affect local TCP/IP connections. To ensure local TCP/IP security, MogDB does not allow the trust authentication for remote connection. |
+| reject              | Rejects connection unconditionally. This authentication mode is usually used for filtering certain hosts. |
+| md5                 | Requires that the client must provide an MD5-encrypted password for authentication.<br/>NOTICE:<br/>- The MD5 encryption algorithm has lower security and poses security risks. Therefore, you are advised to use a more secure encryption algorithm. <br />- MogDB retains MD5 authentication and password storage to facilitate use of third-party tools (such as the TPCC test tool). |
+| sha256              | Requires that the client must provide a sha256-encrypted password for authentication. The password is encrypted based on the unidirectional sha256 of salt (a random number sent from the server to the client) when being transmitted, enhancing the security. |
+| sm3                 | The client is required to provide an SM3 encryption password for authentication. The password is encrypted using the salt (a random number sent by the server to the client) to enhance security. |
+| cert                | Client certificate authentication mode. In this mode, the SSL connection must be configured and the client must provide a valid SSL certificate. The user password is not required.<br/>NOTICE:<br/>This authentication mode supports only hostssl rules. |
+| gss                 | Uses the GSSAPI-based Kerberos authentication.<br/>NOTICE:<br/>- This authentication mode depends on components such as the Kerberos server. It supports only authentication for communication within MogDB. In the current version, Kerberos authentication cannot be used to connect to external clients.<br/>- Enabling Kerberos authentication within MogDB slows down the connection setup among nodes in MogDB. The performance of SQL operations during the setup is affected, but later operations are not. |
+| peer                | Obtains the username of the OS where the client is located and checks whether the username is the same as the initial username of the database. This mode supports only local connections. You can configure **pg_ident.conf** to establish the mapping between OS users and database users.<br />Assume that the OS username is **omm**, the initial database user is **dbAdmin**, and the local mode is set to peer authentication in **pg_hba.conf**.<br />`local   all    all        peer    map=mymap`<br />In the preceding information, **map=mymap** specifies the username mapping, and the mapping name **mymap** is added to **pg_ident.conf**. The following shows the mapping.<br />`# MAPNAME       SYSTEM-USERNAME         PG-USERNAME mymap                omm                                  dbAdmin`<br />NOTE:<br />You can run the **gs_guc reload** command to modify **pg_hba.conf** for the modification to take effect immediately without restarting the database. After **pg_ident.conf** is modified, the modification automatically takes effect upon the next connection. You do not need to restart the database. |
+
+## Establishing Secure TCP/IP Connections in SSL Mode
+
+**Background**
+
+MogDB supports the standard SSL (TLS 1.2). As a highly secure protocol, SSL authenticates bidirectional identification between the server and client using digital signatures and digital certificates to ensure secure data transmission.
+
+**Prerequisites**
+
+Obtain formal certificates and keys for servers and clients from the Certificate Authority (CA). Assume the private key and certificate for the server are **server.key** and **server.crt**, the private key and certificate for the client are **client.key** and **client.crt**, and the CA root certificate is **cacert.pem**.
+
+**Precautions**
+
+- When a user remotely accesses the primary node of the database, the SHA-256 authentication method is used.
+- If internal servers are connected with each other, the trust authentication mode must be used. IP address whitelist authentication is supported.
+
+**Procedure**
+
+After a cluster is deployed, MogDB enables the SSL authentication mode by default. The server certificate, key, and root certificates have been configured. You need to set client parameters.
+
+Set digital certificate parameters related to SSL authentication. For details, see [Table 4](#Table-1.3.1).
+
+- Configure client parameters.
+
+  The default client certificate, key, root certificate, and key encrypted file have been obtained from the CA authentication center. Assume that the certificate, key, and root certificate are stored in the **/home/omm** directory.
+
+  For bidirectional authentication, set the following parameters:
+
+  ```bash
+  export PGSSLCERT="/home/omm/client.crt"
+  export PGSSLKEY="/home/omm/client.key"
+  export PGSSLMODE="verify-ca"
+  export PGSSLROOTCERT="/home/omm/cacert.pem"
+  ```
+
+  For unidirectional authentication, set the following parameters:
+
+  ```bash
+  export PGSSLMODE="verify-ca"
+  export PGSSLROOTCERT="/home/omm/cacert.pem"
+  ```
+
+- Change the client key permission.
+
+  The permission of the client root certificate, key, certificate, and encrypted key file should be 600. Otherwise, the client cannot connect to MogDB through SSL.
+
+  ```bash
+  chmod 600 client.key
+  chmod 600 client.crt
+  chmod 600 client.key.cipher
+  chmod 600 client.key.rand
+  chmod 600 cacert.pem
+  ```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+> You are advised to use bidirectional authentication for security purposes.
+> The environment variables configured for a client must contain the absolute file paths.
+
+**Table 4** Authentication modes<a id="Table-1.3.1"> </a>
+
+| Authentication Mode                        | Description                           | Client Environment Variable Setting      | Maintenance Suggestion      |
+| :----------------------------------------- | :------------------------------------ | :-------------------------------------------| :-------------------------------------------- |
+| Bidirectional authentication (recommended) | The client verifies the server's certificate and the server verifies the client's certificate. Connection can be set up after the verification is successful.                                                                                                       | Set the following environment variables:<br/>- PGSSLCERT<br/>- PGSSLKEY<br/>- PGSSLROOTCERT<br/>- PGSSLMODE | This authentication mode is applicable to scenarios that require high data security. When using this method, you are advised to set the **PGSSLMODE** client variable to **verify-ca** for network data security purposes.           |
+| Unidirectional authentication              | The client verifies the server's certificate, whereas the server does not verify the client's certificate. The server loads the certificate information and sends it to the client. The client verifies the server's certificate according to the root certificate. | Set the following environment variables:<br/>- PGSSLROOTCERT<br/>- PGSSLMODE                                | To prevent TCP-based link spoofing, you are advised to use the SSL certificate authentication. In addition to configuring client root certificate, you are advised to set the **PGSSLMODE** variable to **verify-ca** on the client. |
+
+**Reference**
+
+In the **postgresql.conf** file on the server, set the related parameters. For details, see [Table 5](#Table-1.3.2).
+
+**Table 5** Server parameters<a id="Table-1.3.2"> </a>
+
+| Parameter            | Description                                                  | Value Range                                                  |
+| :------------------- | :----------------------------------------------------------- | :----------------------------------------------------------- |
+| ssl                  | Specifies whether to enable the SSL function.                | - **on**: indicates that SSL is enabled.<br/>- **off**: indicates that SSL is disabled.<br/>**Default value**: **on** |
+| require_ssl          | Specifies whether the server requires the SSL connection. This parameter is valid only when **ssl** is set to **on**. | - **on**: The server requires the SSL connection.<br/>- **off**: The server does not require the SSL connection.<br/>**Default value**: **off** |
+| ssl_cert_file        | Server certificate file, including the server public key. The certificate proves the legal identity of the server and the public key is sent to the peer end for data encryption. | Use the actual certificate name. The relative path is relative to the data directory.<br/>**Default value**: **server.crt** |
+| ssl_key_file         | Private key file of the server, used to decrypt data encrypted using the public key. | Use the actual private key name of the server. The relative path is relative to the data directory.<br/>**Default value**: **server.key** |
+| ssl_ca_file          | Root certificate of the CA server. This parameter is optional and needs to be set only when the certificate of a client must be verified. | Refer to the name of the actual root certificate.<br/>**Default value**: **cacert.pem** |
+| ssl_crl_file         | Certificate revocation list (CRL). If the certificate of a client is in the list, the certificate is invalid. | Refer to the actual name of the certificate revocation list.<br/>**Default value**: empty, indicating that there is no certificate revocation list. |
+| ssl_ciphers          | Encryption algorithm used for SSL communication              | For details about the supported encryption algorithms, see [Table 7](#Table-1.3.4).<br/>**Default value**: **ALL**, indicating that all supported encryption algorithms, excluding ADH, LOW, EXP, and MD5 |
+| ssl_cert_notify_time | Number of days left for giving a warning before the SSL server certificate expires | Please configure the number of days left for giving a warning before the SSL certificate expires on demand. <br/>**Default value:** 90 |
+
+Configure environment variables related to SSL authentication on the client. For details, see [Table 6](#table1.3.3).
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> The path of environment variables is set to **/home/omm** as an example. Replace it with the actual path.
+
+**Table 6** Client parameters<a id="table1.3.3"> </a>
+
+| Environment Variable | Description               | Value Range                                   |
+| :------------------- | :------------------------------------------| :------------------------------------------------|
+| PGSSLCERT            | Client certificate file, including the client public key. The certificate proves the legal identity of the client and the public key is sent to the peer end for data encryption. | Absolute path of a certificate file, for example:<br/>**`export PGSSLCERT='/home/omm/client.crt'`**<br/>**Default value**: empty                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| PGSSLKEY             | Private key file of the client, used to decrypt data encrypted using the public key                                                                                               | Absolute path of a certificate file, for example:<br/>**`export PGSSLKEY='/home/omm/client.key'`**<br/>**Default value**: empty                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| PGSSLMODE            | Specifies whether to negotiate with the server about SSL connection and specifies the priority of the SSL connection.                                                             | **Values and description:**<br/>- **disable**: only tries to establish a non-SSL connection.<br/>- **allow**: tries establishing a non-SSL connection first, and then an SSL connection if the attempt fails.<br/>- **prefer**: tries establishing an SSL connection first, and then a non-SSL connection if the attempt fails.<br/>- **require**: only tries establishing an SSL connection. If there is a CA file, perform the verification according to the scenario in which the parameter is set to **verify-ca**.<br/>- **verify-ca**: tries setting up an SSL connection, checking whether the server certificate is issued by a trusted CA.<br/>- **verify-full**: tries setting up an SSL connection, checking whether the server certificate is issued by a trusted CA, and checking whether the host name of the server is the same as that in the certificate.**<br/>Default value**:**prefer** |
+| PGSSLROOTCERT        | Root certificate file for issuing client certificates. The root certificate is used to verify the server certificate.                                                             | Absolute path of a certificate file, for example:<br/>**`export PGSSLROOTCERT='/home/omm/certca.pem'`**<br/>**Default value**: empty                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| PGSSLCRL             | CRL file for checking whether the server certificate is in the CRL. If it is, the certificate is invalid.                                                                         | Absolute path of a certificate file, for example:<br/>**`export PGSSLCRL='/home/omm/sslcrl-file.crl'`**<br/>**Default value**: empty                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+
+The following tables describe the connection results based on the settings of the server parameters **ssl** and **require_ssl** and the client parameter **sslmode**.
+
+- Server ssl = on
+
+    | sslmode (Client) | require_ssl (Client) | Result                                      |
+    |:----------------|:--------------------|:-------------------------------------------|
+    | disable          | on                   | The connection fails, because the server requires SSL but the client has disabled it. |
+    | allow            | on                   | The connection is encrypted.                                                          |
+    | prefer           | on                   | The connection is encrypted.                                                          |
+    | require          | on                   | The connection is encrypted.                                                          |
+    | verify-ca        | on                   | The connection is encrypted and the server certificate is verified.                   |
+    | verify-full      | on                   | The connection is encrypted and the server certificate and host name are verified.    |
+    | verify-full      | off                  | The connection is encrypted and the server certificate and host name are verified.    |
+
+- Server ssl = off
+
+    | sslmode (Client) | require_ssl (Client) | Result                                      |
+    |:----------------|:--------------------|:-------------------------------------------|
+    | disable     | on  | The connection is not encrypted.              |
+    | allow       | on  | The connection is not encrypted.                                                      |
+    | prefer      | on  | The connection is not encrypted.                                                      |
+    | require     | on  | The connection fails, because the client requires SSL but the server has disabled it. |
+    | verify-ca   | on  | The connection fails, because the client requires SSL but the server has disabled it. |
+    | verify-full | on  | The connection fails, because the client requires SSL but the server has disabled it. |
+    | verify-full | off | The connection fails, because the client requires SSL but the server has disabled it. |
+
+A series of encryption and authentication algorithms with different strength are supported for SSL transmission. You can modify **ssl_ciphers** in **postgresql.conf** to specify the encryption algorithm used by the database server. [Table 7](#Table-1.3.4) lists the encryption algorithms supported by the SSL.
+
+**Table 7** Encryption algorithms<a id="Table-1.3.4"> </a>
+
+| Encryption Strength | Security | Encryption Algorithm      |
+| :------------------ | :------- | :------------------------ |
+| stronger            | high     | DHE-RSA-AES256-GCM-SHA384 |
+| stronger            | high     | DHE-RSA-AES128-GCM-SHA256 |
+| stronger            | high     | DHE-DSS-AES256-GCM-SHA384 |
+| stronger            | high     | DHE-DSS-AES128-GCM-SHA256 |
+| stronger            | medium   | DHE-RSA-AES256-SHA256     |
+| stronger            | medium   | DHE-RSA-AES128-SHA256     |
+| stronger            | medium   | DHE-DSS-AES256-SHA256     |
+| stronger            | medium   | DHE-DSS-AES128-SHA256     |
+| stronger            | high     | DHE-RSA-AES256-CCM        |
+| stronger            | high     | DHE-RSA-AES128-CCM        |
+| stronger            | medium   | DHE-RSA-AES256-SHA        |
+| stronger            | medium   | DHE-RSA-AES128-SHA        |
+| stronger            | medium   | DHE-DSS-AES256-SHA        |
+| stronger            | medium   | DHE-DSS-AES128-SHA        |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - Currently, SSL transmission supports encryption algorithms with the encryption strength higher than strong.
+> - The default value of **ssl_ciphers** is **ALL**, indicating that all encryption algorithms listed in the table are supported. You are advised to retain the default value, unless there are other special requirements on the encryption algorithm.
+> - If multiple encryption algorithms are specified, use semicolons (;) to separate them.
+>   For example, set **ssl_ciphers='DHE-RSA-AES256-GCM-SHA384;DHE-RSA-AES256-SHA256;DHE-RSA-AES256-CCM'** in **postgresql.conf**.
+> - If a DSS-related algorithm is to be used (such as DHE-DSS-AES256-GCM-SHA384, DHE-DSS-AES256-SHA256, and DHE-DSS-AES256-SHA), a certificate file with the DSA algorithm signature must be loaded. For details about how to use OpenSSL to generate a certificate file with the DSA algorithm signature, see the official OpenSSL documents.
+> - SSL authentication increases the time spent for login (creating the SSL environment) and logout processes (clearing the SSL environment), and requires extra time for encrypting the data to be transferred. It affects performance especially in frequent login, logout, and short-time query scenarios.
+> - If the certificate will expire in seven days, an alarm is generated in logs during connection.
+
+## Establishing Secure TCP/IP Connections in SSH Tunnel Mode
+
+**Background**
+
+To ensure secure communication between the database server and its clients, secure SSH tunnels can be established between the database server and clients. SSH is a reliable security protocol dedicated to remote login session and other network services.
+
+Regarding the SSH client, the SSH provides the following two security authentication levels:
+
+- Password-based security authentication: Use an account and a password to log in to a remote host. All transmitted data is encrypted. However, the connected server may not be the target server. Another server may pretend to be the real server and perform the man-in-the-middle attack.
+- Key-based security authentication: A user must create a pair of keys and put the public key on the target server. This mode prevents man-in-the-middle attacks while encrypting all transmitted data. However, the entire login process may last 10s.
+
+**Prerequisites**
+
+The SSH service and the database must run on the same server.
+
+**Procedure**
+
+OpenSSH is used as an example to describe how to configure SSH tunnels. The process of configuring key-based security authentication is not described here. OpenSSH provides multiple configurations to adapt to different networks. For more details, see documents related to OpenSSH.
+
+Establish the SSH tunnel from a local host to the database server.
+
+```bash
+ssh -L 63333:localhost:8000 username@hostIP
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - The first digit string (**63333**) of the **-L** parameter indicates the local port ID of the tunnel and can be randomly selected.
+> - The second digit string (**8000**) indicates the remote port ID of the tunnel, which is the port ID on the server.
+> - **localhost** is the IP address of the local host, **username** is the username on the database server to be connected, and **hostIP** is the IP address of the database server to be connected.
+
+## Checking the Number of Database Connections
+
+**Background**
+
+If the number of connections reaches its upper limit, new connections cannot be created. Therefore, if a user fails to connect a database, the administrator must check whether the number of connections has reached the upper limit. The following are details about database connections:
+
+- The maximum number of global connections is specified by the **max_connections** parameter. Its default value is **5000**.
+- The number of a user's connections is specified by **CONNECTION LIMIT connlimit** in the **CREATE ROLE** statement and can be changed using **CONNECTION LIMIT connlimit** in the **ALTER ROLE** statement.
+- The number of a database's connections is specified by the **CONNECTION LIMIT connlimit** parameter in the **CREATE DATABASE** statement.
+
+**Procedure**
+
+1. Log in as the OS user **omm** to the primary node of the database.
+
+2. Run the following command to connect to the database:
+
+    ```bash
+    gsql -d mogdb -p 8000
+    ```
+
+    **mogdb** is the name of the database to be connected, and **8000** is the port number of the database primary node.
+
+3. View the upper limit of the number of global connections.
+
+    ```sql
+    mogdb=# SHOW max_connections;
+        max_connections
+    -----------------
+        800
+    (1 row)
+    ```
+
+    **800** is the maximum number of session connections.
+
+4. View the number of connections that have been used.
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:**
+   >
+   > Except for database and usernames that are enclosed in double quotation marks (") during creation, uppercase letters are not allowed in the database and usernames in the commands in the following table.
+
+   - View the maximum number of sessions connected to a specific user.
+
+     Run the following commands to view the upper limit of the number of omm's session connections. -1 indicates that no upper limit is set for the number of omm's session connections.
+
+        ```sql
+        mogdb=# SELECT ROLNAME,ROLCONNLIMIT FROM PG_ROLES WHERE ROLNAME='omm';
+         rolname | rolconnlimit
+        ---------+--------------
+         omm     |           -1
+        (1 row)
+        ```
+
+   - View the number of session connections that have been used by a user.
+
+     Run the following commands to view the number of session connections that have been used by omm. 1 indicates the number of session connections that have been used by omm.
+
+        ```sql
+        mogdb=# CREATE OR REPLACE VIEW DV_SESSIONS AS
+        SELECT
+        sa.sessionid AS SID,
+        0::integer AS SERIAL#,
+        sa.usesysid AS USER#,
+        ad.rolname AS USERNAME
+        FROM pg_stat_get_activity(NULL) AS sa
+        LEFT JOIN pg_authid ad ON(sa.usesysid = ad.oid)
+        WHERE sa.application_name <> 'JobScheduler';
+        mogdb=# SELECT COUNT() FROM DV_SESSIONS WHERE USERNAME='omm';
+         count
+        -------
+            1
+        (1 row)
+        ```
+
+   - View the maximum number of sessions connected to a specific database
+
+     Run the following commands to view the upper limit of the number of mogdb's session connections. -1 indicates that no upper limit is set for the number of mogdb's session connections.
+
+        ```sql
+        mogdb=# SELECT DATNAME,DATCONNLIMIT FROM PG_DATABASE WHERE DATNAME='mogdb';
+         datname | datconnlimit
+        ---------+--------------
+         mogdb   |           -1
+        (1 row)
+        ```
+
+   - View the number of session connections that have been used by a specific database.
+
+     Run the following commands to view the number of session connections that have been used by mogdb. 1 indicates the number of session connections that have been used by mogdb.
+
+        ```sql
+        mogdb=# SELECT COUNT(*) FROM PG_STAT_ACTIVITY WHERE DATNAME='mogdb';
+         count
+        -------
+            1
+        (1 row)
+        ```
+
+    - View the number of session connections that have been used by all users.
+
+      Run the following commands to view the number of session connections that have been used by all users:
+
+        ```sql
+        mogdb=# CREATE OR REPLACE VIEW DV_SESSIONS AS
+        SELECT
+        sa.sessionid AS SID,
+        0::integer AS SERIAL#,
+        sa.usesysid AS USER#,
+        ad.rolname AS USERNAME
+        FROM pg_stat_get_activity(NULL) AS sa
+        LEFT JOIN pg_authid ad ON(sa.usesysid = ad.oid)
+        WHERE sa.application_name <>'JobScheduler';
+        mogdb=# SELECT COUNT(*) FROM DV_SESSIONS;
+         count
+        -------
+            23
+        (1 row)
+        ```
+
+## Managing SSL Certificates
+
+Security certificates and keys generated using OpenSSL are configured in MogDB by default. In addition, MogDB provides certificate replacement interfaces to allow users to replace their certificates.
+
+### Generating Certificates
+
+**Scenarios**
+
+In the test environment, users can use either of the following methods to test digital certificates. In a customer's operating environment, only a digital certificate obtained from a CA can be used.
+
+**Prerequisites**
+
+The OpenSSL component has been installed in the Linux environment.
+
+**Generating an Automatic Authentication Certificate**
+
+1. Establish a CA environment.
+
+   ```
+   #  Suppose that user omm exists, and the CA path is test.
+   #  Log in to the Linux environment as user root and switch to user omm:
+   mkdir test
+   cd /etc/pki/tls
+   #  Copy the configuration file openssl.cnf to test.
+   cp openssl.cnf ~/test
+   cd ~/test
+   # Establish the CA environment under the test folder.
+   # Create folder demoCA./demoCA/newcerts./demoCA/private.
+   mkdir ./demoCA ./demoCA/newcerts ./demoCA/private
+   chmod 700 ./demoCA/private
+   # Create the serial file and write it to 01.
+   echo '01'>./demoCA/serial
+   #  Create the index.txt file.
+   touch ./demoCA/index.txt
+   #  Modify parameters in the openssl.cnf configuration file.
+   dir  = ./demoCA
+   default_md      = sha256
+   # The CA environment has been established.
+   ```
+
+2. Generate a root private key.
+
+   ```
+   # Generate a CA private key.
+   openssl genrsa -aes256 -out demoCA/private/cakey.pem 2048
+   Generating RSA private key, 2048 bit long modulus
+   .................+++
+   ..................+++
+   e is 65537 (0x10001)
+   # Set the protection password of the root private key, for example, Test@123.
+   Enter pass phrase for demoCA/private/cakey.pem:
+   # Enter the private key password Test@123 again.
+   Verifying - Enter pass phrase for demoCA/private/cakey.pem:
+   ```
+
+3. Generate a root certificate request file.
+
+   ```
+   # Generate a CA root certificate application file named careq.pem.
+   openssl req -config openssl.cnf -new -key demoCA/private/cakey.pem -out demoCA/careq.pem
+   Enter pass phrase for demoCA/private/cakey.pem:
+   # Enter the root private key password Test@123.
+   You are about to be asked to enter information that will be incorporated
+   into your certificate request.
+   What you are about to enter is what is called a Distinguished Name or a DN.
+   There are quite a few fields but you can leave some blank
+   For some fields there will be a default value,
+   If you enter '.', the field will be left blank.
+   -----
+
+   # Note down the following names and use them when entering information in the generated server certificate and client certificate.
+   Country Name (2 letter code) [AU]:CN
+   State or Province Name (full name) [Some-State]:shanxi
+   Locality Name (eg, city) []:xian
+   Organization Name (eg, company) [Internet Widgits Pty Ltd]:Abc
+   Organizational Unit Name (eg, section) []:hello
+   # Common Name can be randomly set.
+   Common Name (eg, YOUR name) []:world
+   # The email address is optional.
+   Email Address []:
+
+   Please enter the following 'extra' attributes
+   to be sent with your certificate request
+   A challenge password []:
+   An optional company name []:
+   ```
+
+4. Generate a self-signed root certificate.
+
+   ```
+   # When generating the root certificate, modify the openssl.cnf file and set basicConstraints to CA:TRUE.
+   vi openssl.cnf
+   #  Generate a CA self-signed root certificate.
+   openssl ca -config openssl.cnf -out demoCA/cacert.pem -keyfile demoCA/private/cakey.pem -selfsign -infiles demoCA/careq.pem
+   Using configuration from openssl.cnf
+   Enter pass phrase for demoCA/private/cakey.pem:
+   # Enter the root private key password Test@123.
+   Check that the request matches the signature
+   Signature ok
+   Certificate Details:
+           Serial Number: 1 (0x1)
+           Validity
+               Not Before: Feb 28 02:17:11 2017 GMT
+               Not After : Feb 28 02:17:11 2018 GMT
+           Subject:
+               countryName               = CN
+               stateOrProvinceName       = shanxi
+               organizationName          = Abc
+               organizationalUnitName    = hello
+               commonName                = world
+           X509v3 extensions:
+               X509v3 Basic Constraints:
+                   CA:FALSE
+               Netscape Comment:
+                   OpenSSL Generated Certificate
+               X509v3 Subject Key Identifier:
+                   F9:91:50:B2:42:8C:A8:D3:41:B0:E4:42:CB:C2:BE:8D:B7:8C:17:1F
+               X509v3 Authority Key Identifier:
+                   keyid:F9:91:50:B2:42:8C:A8:D3:41:B0:E4:42:CB:C2:BE:8D:B7:8C:17:1F
+
+   Certificate is to be certified until Feb 28 02:17:11 2018 GMT (365 days)
+   Sign the certificate? [y/n]:y
+
+   1 out of 1 certificate requests certified, commit? [y/n]y
+   Write out database with 1 new entries
+   Data Base Updated
+   # A CA root certificate named demoCA/cacert.pem has been issued.
+   ```
+
+5. Generate a private key for the server certificate.
+
+   ```
+   # Generate a private key file named server.key.
+   openssl genrsa -aes256 -out server.key 2048
+   Generating a 2048 bit RSA private key
+   .......++++++
+   ..++++++
+   e is 65537 (0x10001)
+   Enter pass phrase for server.key:
+   # Password of the server private key, for example, Test@123.
+   Verifying - Enter pass phrase for server.key:
+   # Confirm the protection password for the server private key Test@123 again.
+   ```
+
+6. Generate a server certificate request file.
+
+   ```
+   # Generate a server certificate request file server.req.
+   openssl req -config openssl.cnf -new -key server.key -out server.req
+   Enter pass phrase for server.key:
+   You are about to be asked to enter information that will be incorporated
+   into your certificate request.
+   What you are about to enter is what is called a Distinguished Name or a DN.
+   There are quite a few fields but you can leave some blank
+   For some fields there will be a default value,
+   If you enter '.', the field will be left blank.
+   -----
+
+   # Set the following information and make sure that it is same as that when CA is created.
+   Country Name (2 letter code) [AU]:CN
+   State or Province Name (full name) [Some-State]:shanxi
+   Locality Name (eg, city) []:xian
+   Organization Name (eg, company) [Internet Widgits Pty Ltd]:Abc
+   Organizational Unit Name (eg, section) []:hello
+   # Common Name can be randomly set.
+   Common Name (eg, YOUR name) []:world
+   Email Address []:
+   # The following information is optional.
+   Please enter the following 'extra' attributes
+   to be sent with your certificate request
+   A challenge password []:
+   An optional company name []:
+   ```
+
+7. Generate a server certificate.
+
+   ```
+   # When generating the server certificate or client certificate, modify the openssl.cnf file and set basicConstraints to CA:FALSE.
+   vi openssl.cnf
+   # Change the demoCA/index.txt.attr attribute to no.
+   vi demoCA/index.txt.attr
+
+   # Issue the generated server certificate request file. After it is issued, an official server certificate server.crt is generated.
+   openssl ca  -config openssl.cnf -in server.req -out server.crt -days 3650 -md sha256
+   Using configuration from /etc/ssl/openssl.cnf
+   Enter pass phrase for ./demoCA/private/cakey.pem:
+   Check that the request matches the signature
+   Signature ok
+   Certificate Details:
+           Serial Number: 2 (0x2)
+           Validity
+               Not Before: Feb 27 10:11:12 2017 GMT
+               Not After : Feb 25 10:11:12 2027 GMT
+           Subject:
+               countryName               = CN
+               stateOrProvinceName       = shanxi
+               organizationName          = Abc
+               organizationalUnitName    = hello
+               commonName                = world
+           X509v3 extensions:
+               X509v3 Basic Constraints:
+                   CA:FALSE
+               Netscape Comment:
+                   OpenSSL Generated Certificate
+               X509v3 Subject Key Identifier:
+                   EB:D9:EE:C0:D2:14:48:AD:EB:BB:AD:B6:29:2C:6C:72:96:5C:38:35
+               X509v3 Authority Key Identifier:
+                   keyid:84:F6:A1:65:16:1F:28:8A:B7:0D:CB:7E:19:76:2A:8B:F5:2B:5C:6A
+
+   Certificate is to be certified until Feb 25 10:11:12 2027 GMT (3650 days)
+   # Enter y to sign and issue the certificate.
+   Sign the certificate? [y/n]:y
+
+   # Enter y. The certificate singing and issuing is complete.
+   1 out of 1 certificate requests certified, commit? [y/n]y
+   Write out database with 1 new entries
+   Data Base Updated
+   ```
+
+   Disable password protection for the private key.
+
+   ```
+   # Disable the password protection for the server private key.
+   openssl rsa -in server.key -out server.key
+   # If the password protection for the server private key is not disabled, you need to use the gs_guc tool to encrypt the password.
+   gs_guc encrypt -M server -D ./
+   # Enter the passowrd of the the server private key as prompted. After the password is encrypted, two private key password protection files server.key.cipher and server.key.rand are generated.
+   ```
+
+8. Generate the client certificate and private key.
+
+   Methods and requirements for generating client certificates and private keys are the same as that for server certificates and private keys.
+
+   ```
+   # Generate a client private key.
+   openssl genrsa -aes256 -out client.key 2048
+   # Generate a certificate request file for a client.
+   openssl req -config openssl.cnf -new -key client.key -out client.req
+   # After the generated certificate request file for client is signed and issued, a formal client certificate client.crt is generated.
+   openssl ca -config openssl.cnf -in client.req -out client.crt -days 3650 -md sha256
+   ```
+
+   Disable password protection for the private key:
+
+   ```
+   # Disable the protection for a client private key password.
+   openssl rsa -in client.key -out client.key
+   # If password protection for a client private key is not removed, you need to use the gs_guc tool to encrypt the password.
+   gs_guc encrypt -M client -D ./
+   Enter the passowrd of the the client private key as prompted. After the password is encrypted, two private key password protection files client.key.cipher and client.key.rand are generated.
+   ```
+
+   Convert the client key to the DER format.
+
+   ```bash
+   openssl pkcs8 -topk8 -outform DER -in client.key -out client.key.pk8 -nocrypt
+   ```
+
+9. Generate a CRL.
+
+   If the CRL is required, you can generate it by following the following procedure:
+
+   ```
+   # Create a crlnumber file.
+   echo '00'>./demoCA/crlnumber
+   # Revoke a server certificate.
+   openssl ca -config openssl.cnf -revoke server.crt
+   # Generate the CRL sslcrl-file.crl.
+   openssl ca -config openssl.cnf -gencrl -out sslcrl-file.crl
+   ```
+
+### Replacing Certificates
+
+**Scenarios**
+
+Default security certificates and private keys required for SSL connection are configured in MogDB. You can change them as needed.
+
+**Prerequisites**
+
+The formal certificates and keys for the server and client have been obtained from the CA.
+
+**Precautions**
+
+Currently, MogDB supports only the X509v3 certificate in PEM format.
+
+**Procedure**
+
+1. Prepare for a certificate and a key.
+
+   Conventions for configuration file names on the server:
+
+   - Certificate name: server.crt
+   - Key name: server.key
+   - Key password and encrypted file: server.key.cipher and server.key.rand
+
+   Conventions for configuration file names on the client:
+
+   - Certificate name: client.crt
+   - Key name: client.key
+   - Key password and encrypted file: client.key.cipher and client.key.rand
+   - Certificate name: cacert.pem
+   - CRL file name: sslcrl-file.crl
+
+2. Create a compressed package.
+
+   Package name: db-cert-replacement.zip
+
+   Package format: ZIP
+
+   Package file list: server.crt, server.key, server.key.cipher, server.key.rand, client.crt, client.key, client.key.cipher, client.key.rand, cacert.pem If you need to configure the CRL, the list must contain sslcrl-file.crl.
+
+3. Invoke the certificate replacement interface to replace a certificate.
+
+   a. Upload the prepared package **db-cert-replacement.zip** to any path of an MogDB user.
+
+   For example: /home/**xxxx**/db-cert-replacement.zip
+
+   b. Run the following command to perform the replacement:
+
+   ```bash
+   gs_om -t cert --cert-file=/home/xxxx/db-cert-replacement.zip
+   ```
+
+4. Restart the MogDB.
+
+   ```bash
+   gs_om -t stop
+   gs_om -t start
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+   > Certificates can be rolled back to the version before the replacement. You can run the **gs_om -t cert -rollback** command to remotely invoke the interface or **gs_om -t cert -rollback -L** to locally invoke the interface. The certificate will be rolled back to the latest version that was successfully replaced.
diff --git a/product/en/docs-mogdb/v3.0/security-guide/security/2-managing-users-and-their-permissions.md b/product/en/docs-mogdb/v3.0/security-guide/security/2-managing-users-and-their-permissions.md
new file mode 100644
index 0000000000000000000000000000000000000000..2743d863dcda025c8d3b53248acdd3570154b827
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/security-guide/security/2-managing-users-and-their-permissions.md
@@ -0,0 +1,1023 @@
+---
+title: Managing Users and Their Permissions
+summary: Managing Users and Their Permissions
+author: Guo Huan
+date: 2021-04-26
+---
+
+# Managing Users and Their Permissions
+
+## Default Permission Mechanism
+
+A user who creates an object is the owner of this object. By default, Separation of Duties is disabled after database installation. A database system administrator has the same permissions as object owners. After an object is created, only the object owner or system administrator can query, modify, and delete the object, and grant permissions for the object to other users through GRANT by default.
+
+To enable another user to use the object, grant required permissions to the user or the role that contains the user.
+
+MogDB supports the following permissions: SELECT, INSERT, UPDATE, DELETE, TRUNCATE, REFERENCES, CREATE, CONNECT, EXECUTE, USAGE, ALTER, DROP, COMMENT, INDEX, and VACUUM. Permission types are associated with object types. For permission details, see GRANT.
+
+To remove permissions, run **REVOKE**. Object owners have implicit permissions (such as ALTER, DROP, COMMENT, INDEX, VACUUM, GRANT, and REVOKE) on objects. That is, once becoming the owner of an object, the owner is immediately granted the implicit permissions on the object. Object owners can remove their own common permissions, for example, making tables read-only to themselves or others, except the system administrator.
+
+System catalogs and views are visible to either system administrators or all users. System catalogs and views that require system administrator permissions can be queried only by system administrators. For details, see System Catalogs and System Views.
+
+The database provides the object isolation feature. If this feature is enabled, users can view only the objects (tables, views, columns, and functions) that they have the permission to access. System administrators are not affected by this feature. For details, see ALTER DATABASE.
+
+## Administrators
+
+### Initial Users
+
+The account automatically generated during MogDB installation is called an initial user. An initial user is the system, monitoring, O&M, and security policy administrator who has the highest-level permissions in the system and can perform all operations. This account has the same name as the OS user used for MogDB installation. You need to manually set the password during the installation. After the first login, change the initial user's password in time.
+
+An initial user bypasses all permission checks. You are advised to use an initial user as a database administrator only for database management other than service running.
+
+### System Administrators
+
+A system administrator is an account with the **SYSADMIN** attribute. By default, a database system administrator has the same permissions as object owners but does not have the object permissions in **dbe_perf** mode.
+
+To create a system administrator, connect to the database as the initial user or a system administrator and run the **CREATE USER** or **ALTER USER** statement with **SYSADMIN** specified.
+
+```sql
+mogdb=# CREATE USER sysadmin WITH SYSADMIN password "xxxxxxxxx";
+```
+
+or
+
+```sql
+mogdb=# ALTER USER joe SYSADMIN;
+```
+
+To run the **ALTER USER** statement, the user must exist.
+
+### Monitor Administrators
+
+A monitoring administrator is an account with the **MONADMIN** attribute that has the privilege to view views and functions in **dbe_perf** mode and to grant or withdraw privileges to objects in **dbe_perf** mode.
+
+To create a monitor administrator, connect to the database as the system administrator and run the **CREATE USER** or **ALTER USER** statement with **MONADMIN** specified.
+
+```sql
+mogdb=# CREATE USER monadmin WITH MONADMIN password "xxxxxxxxx";
+```
+
+or
+
+```sql
+mogdb=# ALTER USER joe MONADMIN;
+```
+
+To run the **ALTER USER** statement, the user must exist.
+
+### O&M Administrators
+
+An O&M administrator is an account with the **OPRADMIN** attribute and has permission to perform backup restores using the Roach tool.
+
+To create an O&M administrator, connect to the database as the initial user and run the **CREATE USER** or **ALTER USER** statement with **OPRADMIN** specified.
+
+```sql
+mogdb=# CREATE USER opradmin WITH OPRADMIN password "xxxxxxxxx";
+```
+
+or
+
+```sql
+mogdb=# ALTER USER joe OPRADMIN;
+```
+
+To run the **ALTER USER** statement, the user must exist.
+
+### Security Policy Administrators
+
+A security policy administrator is an account with **POLADMIN** attributes and has permission to create resource tags, desensitization policies, and unified audit policies.
+
+To create an security policy administrator, connect to the database as the system administrator and run the **CREATE USER** or **ALTER USER** statement with **POLADMIN** specified.
+
+```sql
+mogdb=# CREATE USER poladmin WITH POLADMIN password "xxxxxxxxx";
+```
+
+or
+
+```sql
+mogdb=# ALTER USER joe POLADMIN;
+```
+
+To run the **ALTER USER** statement, the user must exist.
+
+## Separation of Duties
+
+Descriptions in Default Permission Mechanism and Administrators are about the initial situation after a cluster is created. By default, a system administrator with the **SYSADMIN** attribute has the highest-level permissions.
+
+In actual service management, you can set separation of duties to prevent system administrators from having excessive centralized permissions, which may cause high risks. Some permissions of the system administrator are transferred to the security administrator and audit administrator, implementing separation of duties among the system administrator, security administrator, and audit administrator.
+
+After separation of duties is enabled, a system administrator does not have the **CREATEROLE** attribute (security administrator) and **AUDITADMIN** attribute (audit administrator). That is, the system administrator does not have the permissions to create roles and users and the permissions to view and maintain database audit logs. For details about the **CREATEROLE** and **AUDITADMIN** attributes, see CREATE ROLE.
+
+After separation of duties is enabled, system administrators have the permissions only for the objects owned by them.
+
+Separation of duties does not take effect for an initial user. Therefore, you are advised to use an initial user as a database administrator only for database management other than service running.
+
+To enable separation of duties, set **enableSeparationOfDuty** to **on**.
+
+For details about permission changes before and after enabling separation of duties, see [Table 1](#Table-2.3.1) and [Table 2](#Table-2.3.2).
+
+**Table 1** Default user permissions<a id="Table-2.3.1"> </a>
+
+<table>
+    <tr>
+        <th>Object Name</th>
+        <th>Initial User (ID: 10)</th>
+        <th>System Administrator</th>
+        <th>Monitor Administrator</th>
+        <th>O&M Administrator</th>
+        <th>Security Policy Administrator</th>
+        <th>Security Administrator</th>
+        <th>Audit Administrator</th>
+        <th>Common User</th>
+    </tr>
+    <tr>
+     <td>Tablespaces</td>
+        <td rowspan="7">Has all permissions except the one to access private tables.</td>
+        <td>Can create, modify, delete, access, or grant permissions for tablespaces.</td>
+        <td colspan="6">Cannot create, modify, delete, or grant permissions for tablespaces and can access tablespaces if the access permission is granted.</td>
+    </tr>
+    <tr>
+     <td>Tables</td>
+        <td>Has permissions for all tables.</td>
+        <td colspan="6">Has all permissions for their own tables, but does not have permissions for other users' tables.</td>
+    </tr>
+    <tr>
+        <td>Indexes</td>
+        <td>Can create indexes on all tables.</td>
+        <td colspan="6">Can create indexes on their own tables.</td>
+    </tr>
+    <tr>
+        <td>Schemas</td>
+        <td>Has all permissions for all schemas except dbe_perf.</td>
+        <td>Has all permissions for their own schemas and dbe_perf, but does not have permissions for other users' schemas.</td>
+        <td colspan="5">Has all permissions for their own schemas, but does not have permissions for other users' schemas.</td>
+    </tr>
+    <tr>
+        <td>Functions</td>
+        <td>Has all permissions for all functions except those in the dbe_perf schema.</td>
+        <td>Has permissions for their own functions and those in the dbe_perf schema, has the call permission for other users' functions in the public schema, but does not have permissions for other users' functions in other schemas.</td>
+        <td colspan="5">Has permissions for their own functions, has the call permission for other users' functions in the public schema, but does not have permissions for other users' functions in other schemas.</td>
+    </tr>
+    <tr>
+        <td>Customized views</td>
+        <td>Has all permissions on all views except the dbe_perf schema view.</td>
+        <td>Has permissions for their own views and the dbe_perf schema view, but does not have permissions for other users' views.</td>
+        <td colspan="5">Has permissions for their own views, but does not have permissions for other users' views.</td>
+    </tr>
+    <tr>
+     <td>System catalogs and system views</td>
+        <td>Has permissions to query all system catalogs and views.</td>
+        <td colspan="6">Has permissions to query only some system catalogs and views. For details, see System Catalogs and System Views.</td>
+    </tr>
+</table>
+**Table 2** Changes in permissions after separation of duties<a id="Table-2.3.2"> </a>
+
+<table>
+    <tr>
+        <th>Object Name</th>
+        <th>Initial User (ID: 10)</th>
+        <th>System Administrator</th>
+        <th>Monitor Administrator</th>
+        <th>O&M Administrator</th>
+        <th>Security Policy Administrator</th>
+        <th>Security Administrator</th>
+        <th>Audit Administrator</th>
+        <th>Common User</th>
+    </tr>
+    <tr>
+     <td>Tablespaces</td>
+        <td rowspan="7">N/A.<br/>Has all permissions except the one to access private tables.</td>
+        <td>N/A</td>
+        <td colspan="6">N/A</td>
+    </tr>
+    <tr>
+     <td>Tables</td>
+        <td>Permissions reduced<br/>Has all permissions for their own tables and other users' tables in the public schema, but does not have permissions for other users' tables in other schemas.</td>
+        <td colspan="6">N/A</td>
+    </tr>
+    <tr>
+        <td>Indexes</td>
+        <td>Permissions reduced<br/>Can create indexes for their own tables and other users' tables in the public schema.</td>
+        <td colspan="6">N/A</td>
+    </tr>
+    <tr>
+        <td>Schemas</td>
+        <td>Permissions reduced<br/>Has all permissions for their own schemas, but does not have permissions for other users' schemas.</td>
+        <td>N/A</td>
+        <td colspan="5">N/A</td>
+    </tr>
+    <tr>
+        <td>Functions</td>
+        <td>Permissions reduced<br/>Has all permissions for their own functions and other users' functions in the public schema, but does not have permissions for other users' functions in other schemas.</td>
+        <td>N/A</td>
+        <td colspan="5">N/A</td>
+    </tr>
+    <tr>
+        <td>Customized views</td>
+        <td>Permissions reduced<br/>Has all permissions for their own views and other users' views in the public schema, but does not have permissions for other users' views in other schemas.</td>
+        <td>N/A</td>
+        <td colspan="5">N/A</td>
+    </tr>
+    <tr>
+     <td>System catalogs and system views</td>
+        <td>N/A</td>
+        <td colspan="6">N/A</td>
+    </tr>
+</table>
+
+## Users
+
+You can use **CREATE USER** and **ALTER USER** to create and manage database users, respectively. MogDB has one or more named databases. Users and roles are shared within the entire MogDB, but their data is not shared. That is, a user can connect to any database, but after the connection is successful, any user can access only the database declared in the connection request.
+
+In non-separation-of-duties scenarios, MogDB user accounts can be created and deleted only by a system administrator or a security administrator with the **CREATEROLE** attribute. In separation-of-duties scenarios, a user account can be created only by an initial user or a security administrator.
+
+When a user logs in, MogDB authenticates the user. A user can own databases and database objects (such as tables), and grant permissions of these objects to other users and roles. In addition to system administrators, users with the **CREATEDB** attribute can create databases and grant permissions on these databases.
+
+**Adding, Modifying, and Deleting Users**
+
+- To create a user, use the SQL statement **CREATE USER**.
+
+  For example, create a user **joe** and set the **CREATEDB** attribute for the user.
+
+  ```sql
+  mogdb=# CREATE USER joe WITH CREATEDB PASSWORD "XXXXXXXXX";
+  CREATE ROLE
+  ```
+
+- To create a system administrator, use the **CREATE USER** statement with the **SYSADMIN** parameter.
+
+- To delete an existing user, use **DROP USER**.
+
+- To change a user account (for example, rename the user or change the password), use **ALTER USER**.
+
+- To view a user list, query the **PG_USER** view.
+
+  ```sql
+  mogdb=# SELECT * FROM pg_user;
+  ```
+
+- To view user attributes, query the system catalog **PG_AUTHID**.s
+
+  ```sql
+  mogdb=# SELECT * FROM pg_authid;
+  ```
+
+**Private Users**
+
+If multiple service departments use different database user accounts to perform service operations and a database maintenance department at the same level uses database administrator accounts to perform maintenance operations, service departments may require that database administrators, without specific authorization, can manage (**DROP**, **ALTER**, and **TRUNCATE**) their data but cannot access (**INSERT**, **DELETE**, **UPDATE**, **SELECT**, and **COPY**) the data. That is, the management permissions of database administrators for tables need to be isolated from their access permissions to improve the data security of common users.
+
+In separation-of-duties mode, a database administrator does not have permissions for the tables in schemas of other users. In this case, database administrators have neither management permissions nor access permissions, which does not meet the requirements of the service departments mentioned above. Therefore, MogDB provides private users to solve the problem. That is, create private users with the **INDEPENDENT** attribute in non-separation-of-duties mode.
+
+```sql
+mogdb=# CREATE USER user_independent WITH INDEPENDENT IDENTIFIED BY "1234@abc";
+```
+
+System administrators and security administrators with the **CREATEROLE** attribute can manage (**DROP**, **ALTER**, and **TRUNCATE**) objects of private users but cannot access (**INSERT**, **DELETE**, **SELECT**, **UPDATE**, **COPY**, **GRANT**, **REVOKE**, and **ALTER OWNER**) the objects before being authorized.
+
+**Permanent Users**
+
+MogDB provides the permanent user solution, that is, MogDB allows you to create a permanent user with the PERSISTENCE property.
+
+```sql
+mogdb=# CREATE USER user_persistence WITH persistence IDENTIFIED BY "1234@abc";
+```
+
+Only initial users are allowed to create, modify, and delete permanent users with the PERSISTENCE property.
+
+## Roles
+
+A role is a set of users. After a role is granted to a user through **GRANT**, the user will have all the permissions of the role. It is recommended that roles be used to efficiently grant permissions. For example, you can create different roles of design, development, and maintenance personnel, grant the roles to users, and then grant specific data permissions required by different users. When permissions are granted or revoked at the role level, these changes take effect on all members of the role.
+
+MogDB provides an implicitly defined group **PUBLIC** that contains all roles. By default, all new users and roles have the permissions of **PUBLIC**. For details about the default permissions of **PUBLIC**, see GRANT. To revoke permissions of **PUBLIC** from a user or role, or re-grant these permissions to them, add the **PUBLIC** keyword in the **REVOKE** or **GRANT** statement.
+
+To view all roles, query the system catalog **PG_ROLES**.
+
+```sql
+SELECT * FROM PG_ROLES;
+```
+
+**Adding, Modifying, and Deleting Roles**
+
+In non-separation-of-duties scenarios, a role can be created, modified, and deleted only by a system administrator or a user with the **CREATEROLE** attribute. In separation-of-duties scenarios, a role can be created, modified, and deleted only by an initial user or a user with the **CREATEROLE** attribute.
+
+- To create a role, use **CREATE ROLE**.
+- To add or delete users in an existing role, use **ALTER ROLE**.
+- To delete a role, use **DROP ROLE**. **DROP ROLE** deletes only a role, rather than member users in the role.
+
+## Built-in roles
+
+MogDB provides a group of default roles whose names start with **gs_role_**. These roles are provided to access to specific, typically high-privileged operations. You can grant these roles to other users or roles within the database so that they can use specific functions. These roles should be given with great care to ensure that they are used where they are needed. [Table 3](#table1) describes the permissions of built-in roles.
+
+**Table 3** Permission description of built-in roles <a id="table1"></a>
+
+| Role                   | Permission                                                   |
+| :--------------------- | :----------------------------------------------------------- |
+| gs_role_copy_files     | Permission to run the **copy… to/from filename** command. However, the GUC parameter **enable_copy_server_files** must be set first to enable the function of copying server files. |
+| gs_role_signal_backend | Permission to call the **pg_cancel_backend**, **pg_terminate_backend**, and **pg_terminate_session** functions to cancel or terminate other sessions. However, this role cannot perform operations on sessions of the initial user or **PERSISTENCE** user. |
+| gs_role_tablespace     | Permission to create a tablespace.                           |
+| gs_role_replication    | Permission to call logical replication functions, such as **kill_snapshot**, **pg_create_logical_replication_slot**, **pg_create_physical_replication_slot**, **pg_drop_replication_slot**, **pg_replication_slot_advance**, **pg_create_physical_replication_slot_extern**, **pg_logical_slot_get_changes**, **pg_logical_slot_peek_changes**, **pg_logical_slot_get_binary_changes**, and **pg_logical_slot_peek_binary_changes**. |
+| gs_role_account_lock   | Permission to lock and unlock users. However, this role cannot lock or unlock the initial user or users with the **PERSISTENCE** attribute. |
+| gs_role_pldebugger     | Permission to debug functions in **dbe_pldebugger**.         |
+
+The restrictions on built-in roles are as follows:
+
+- The role names starting with **gs_role_** are reserved for built-in roles in the database. Do not create users or roles starting with **gs_role_** or rename existing users or roles starting with **gs_role_**.
+
+- Do not perform **ALTER** or **DROP** operations on built-in roles.
+
+- By default, built-in roles do not have the **LOGIN** permission and do not have preset passwords.
+
+- The **gsql** meta-commands **\\du** and **\\dg** do not display information about built-in roles. However, if *pattern* is set to a specific built-in role, the information is displayed.
+
+- When separation-of-duty is disabled, the initial user, users with the **SYSADMIN** permission, and users with the **ADMIN OPTION** built-in role permission have the permission to perform **GRANT** and **REVOKE** operations on built-in roles. When separation of duty is enabled, the initial user and users with the **ADMIN OPTION** built-in role permission have the permission to perform **GRANT** and **REVOKE** operations on built-in roles. Example:
+
+  ```sql
+  GRANT gs_role_signal_backend TO user1;
+  REVOKE gs_role_signal_backend FROM user1;
+  ```
+
+## Schemas
+
+Schemas allow multiple users to use the same database without interference. In this way, database objects can be organized into logical groups that are easy to manage, and third-party applications can be added to corresponding schemas without causing conflicts.
+
+Each database has one or more schemas. Each schema contains tables and other types of objects. When a database is initially created, it has a schema named **public** by default, and all users have the usage permission on the schema. Only the system administrator and initial users can create functions, stored procedures, and synonyms in the public schema. Other users cannot create the three types of objects even if they have the create permission. You can group database objects by schema. A schema is similar to an OS directory but cannot be nested.
+
+The same database object name can be used in different schemas of the same database without causing conflicts. For example, both **a_schema** and **b_schema** can contain a table named **mytable**. Users with required permissions can access objects across multiple schemas of the same database.
+
+When you run the **CREATE USER** command to create a user, the system creates a schema with the same name as the user in the database where the command is executed.
+
+Database objects are generally created in the first schema in a database search path. For details about the first schema and how to change the schema order, see [Search Path](#Search-Path).
+
+**Creating, Modifying, and Deleting Schemas**
+
+- To create a schema, use **CREATE SCHEMA**. By default, the initial user and system administrator can create schemas. Other users can create schemas in the database only when they have the CREATE permission on the database. For details about how to grant the permission, see the syntax in GRANT.
+
+- To change the name or owner of a schema, use **ALTER SCHEMA**. The schema owner can change the schema.
+
+- To delete a schema and its objects, use **DROP SCHEMA**. Schema owners can delete schemas.
+
+- To create a table in a schema, use the **schema_name.table_name** format to specify the table. If *schema_name* is not specified, the table will be created in the first schema in search path.
+
+- To view the owner of a schema, perform the following join query on the system catalogs **PG_NAMESPACE** and **PG_USER**. Replace **schema_name** in the statement with the name of the schema to be queried.
+
+  ```sql
+  mogdb=# SELECT s.nspname,u.usename AS nspowner FROM pg_namespace s, pg_user u WHERE nspname='schema_name' AND s.nspowner = u.usesysid;
+  ```
+
+- To view a list of all schemas, query the system catalog **PG_NAMESPACE**.
+
+  ```sql
+  mogdb=# SELECT * FROM pg_namespace;
+  ```
+
+- To view a list of tables in a schema, query the system catalog **PG_TABLES**. For example, the following query will return a table list from **PG_CATALOG** in the schema.
+
+  ```sql
+  mogdb=# SELECT distinct(tablename),schemaname from pg_tables where schemaname = 'pg_catalog';
+  ```
+
+**Search Path<a id="Search-Path"> </a>**
+
+A search path is defined in the **search_path** parameter. The parameter value is a list of schema names separated by commas (,). If no target schema is specified during object creation, the object will be added to the first schema listed in the search path. If there are objects with the same name across different schemas and no schema is specified for an object query, the object will be returned from the first schema containing the object in the search path.
+
+- To view the current search path, use **SHOW**.
+
+  ```sql
+  mogdb=# SHOW SEARCH_PATH;
+   search_path
+  ----------------
+   "$user",public
+  (1 row)
+  ```
+
+  The default value of **search_path** is `"$user",public.` **$user** indicates the name of the schema with the same name as the current session user. If the schema does not exist, **$user** will be ignored. By default, after a user connects to a database that has schemas with the same name, objects will be added to all the schemas. If there are no such schemas, objects will be added to only the **public** schema.
+
+- To change the default schema of the current session, run the **SET** statement.
+
+  Run the following command to set **search_path** to **myschema** and **public** (**myschema** will be searched first):
+
+  ```sql
+  mogdb=# SET SEARCH_PATH TO myschema, public;
+  SET
+  ```
+
+## Setting User Permissions
+
+- To grant permissions for an object to a user, see GRANT.
+
+  When permissions for a table or view in a schema are granted to a user or role, the **USAGE** permission of the schema must be granted together. Otherwise, the user or role can only see these objects but cannot access them.
+
+  In the following example, permissions for the schema **tpcds** are first granted to user **joe**, and then the **SELECT** permission for the **tpcds.web_returns** table is also granted.
+
+  ```sql
+  mogdb=# GRANT USAGE ON SCHEMA tpcds TO joe;
+  mogdb=# GRANT SELECT ON TABLE tpcds.web_returns to joe;
+  ```
+
+- Grant a role to a user to allow the user to inherit the object permissions of the role.
+
+  1. Create a role.
+
+     Create a role **lily** and grant the system permission **CREATEDB** to the role.
+
+     ```sql
+     mogdb=# CREATE ROLE lily WITH CREATEDB PASSWORD "XXXXXXXXX";
+     ```
+
+  2. Grant object permissions to the role by using **GRANT**.
+
+     For example, first grant permissions for the schema **tpcds** to the role **lily**, and then grant the **SELECT** permission of the **tpcds.web_returns** table to **lily**.
+
+     ```sql
+     mogdb=# GRANT USAGE ON SCHEMA tpcds TO lily;
+     mogdb=# GRANT SELECT ON TABLE tpcds.web_returns to lily;
+     ```
+
+  3. Grant the role permissions to a user.
+
+     ```sql
+     mogdb=# GRANT lily to joe;
+     ```
+
+     > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+     > When the permissions of a role are granted to a user, the attributes of the role are not transferred together.
+
+- To revoke user permissions, use **REVOKE**.
+
+## Row-Level Access Control
+
+The row-level access control feature enables database access control to be accurate to each row of data tables. In this way, the same SQL query may return different results for different users.
+
+You can create a row-level access control policy for a data table. The policy defines an expression that takes effect only for specific database users and SQL operations. When a database user accesses the data table, if a SQL statement meets the specified row-level access control policies of the data table, the expressions that meet the specified condition will be combined by using **AND** or **OR** based on the attribute type (**PERMISSIVE** | **RESTRICTIVE**) and applied to the execution plan in the query optimization phase.
+
+Row-level access control is used to control the visibility of row-level data in tables. By predefining filters for data tables, the expressions that meet the specified condition can be applied to execution plans in the query optimization phase, which will affect the final execution result. Currently, the SQL statements that can be affected include **SELECT**, **UPDATE**, and **DELETE**.
+
+Scenario 1: A table summarizes the data of different users. Users can view only their own data.
+
+```sql
+--Create users alice, bob, and peter.
+mogdb=# CREATE ROLE alice PASSWORD 'Gauss@123';
+mogdb=# CREATE ROLE bob PASSWORD 'Gauss@123';
+mogdb=# CREATE ROLE peter PASSWORD 'Gauss@123';
+
+--Create the all_data table that contains user information.
+mogdb=# CREATE TABLE all_data(id int, role varchar(100), data varchar(100));
+
+--Insert data into the data table.
+mogdb=# INSERT INTO all_data VALUES(1, 'alice', 'alice data');
+mogdb=# INSERT INTO all_data VALUES(2, 'bob', 'bob data');
+mogdb=# INSERT INTO all_data VALUES(3, 'peter', 'peter data');
+
+--Grant the read permission for the all_data table to users alice, bob, and peter.
+mogdb=# GRANT SELECT ON all_data TO alice, bob, peter;
+
+--Enable row-level access control.
+mogdb=# ALTER TABLE all_data ENABLE ROW LEVEL SECURITY;
+
+--Create a row-level access control policy to specify that the current user can view only their own data.
+mogdb=# CREATE ROW LEVEL SECURITY POLICY all_data_rls ON all_data USING(role = CURRENT_USER);
+
+--View table details.
+mogdb=# \d+ all_data
+                               Table "public.all_data"
+ Column |          Type          | Modifiers | Storage  | Stats target | Description
+--------+------------------------+-----------+----------+--------------+-------------
+ id     | integer                |           | plain    |              |
+ role   | character varying(100) |           | extended |              |
+ data   | character varying(100) |           | extended |              |
+Row Level Security Policies:
+    POLICY "all_data_rls"
+      USING (((role)::name = "current_user"()))
+Has OIDs: no
+Location Nodes: ALL DATANODES
+Options: orientation=row, compression=no, enable_rowsecurity=true
+
+--Switch to user alice and run SELECT * FROM public.all_data.
+mogdb=# SELECT * FROM public.all_data;
+ id | role  |    data
+----+-------+------------
+  1 | alice | alice data
+(1 row)
+
+mogdb=# EXPLAIN(COSTS OFF) SELECT * FROM public.all_data;
+                           QUERY PLAN
+----------------------------------------------------------------
+ Streaming (type: GATHER)
+   Node/s: All datanodes
+   ->  Seq Scan on all_data
+         Filter: ((role)::name = 'alice'::name)
+ Notice: This query is influenced by row level security feature
+(5 rows)
+
+--Switch to user peter and run SELECT * FROM public.all_data.
+mogdb=# SELECT * FROM public.all_data;
+ id | role  |    data
+----+-------+------------
+  3 | peter | peter data
+(1 row)
+
+mogdb=#  EXPLAIN(COSTS OFF) SELECT * FROM public.all_data;
+                           QUERY PLAN
+----------------------------------------------------------------
+ Streaming (type: GATHER)
+   Node/s: All datanodes
+   ->  Seq Scan on all_data
+         Filter: ((role)::name = 'peter'::name)
+ Notice: This query is influenced by row level security feature
+(5 rows)
+```
+
+## Setting Security Policies
+
+### Setting Account Security Policies
+
+**Background**
+
+For data security purposes, MogDB provides a series of security measures, such as automatically locking and unlocking accounts, manually locking and unlocking abnormal accounts, and deleting accounts that are no longer used.
+
+**Automatically Locking and Unlocking Accounts**
+
+- If the number of incorrect password attempts (**failed_login_attempts**) of an account reaches the upper limit (**10** by default), the system automatically locks the account. Smaller parameter values result in higher account security. However, if the value of this parameter is set too small, inconvenience may occur.
+
+- If the time during which a user is locked exceeds the preset value (**password_lock_time**, one day by default), the system automatically unlocks the user. Larger parameter values bring higher account security. However, if the value of this parameter is set too large, inconvenience may occur.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > - The integral part of the **password_lock_time** value indicates the number of days and its decimal part can be converted into hours, minutes, and seconds.
+  > - If the **failed_login_attempts** parameter is set to **0**, an account is never locked due to incorrect password attempts. If the **password_lock_time** parameter is set to **0**, an account is quickly unlocked after it is locked due to incorrect password attempts. Therefore, only when both parameters are set to positive values, the following operations can be performed: password failure check, account locking, and account unlocking.
+  > - The default values of the two parameters meet the security requirements. You can change the parameter values as needed for higher security. You are advised to retain the default values.
+
+Configure the **failed_login_attempts** parameter.
+
+1. Log in as the OS user **omm** to the primary node of the database.
+
+2. Run the following command to connect to the database:
+
+   ```bash
+   gsql -d mogdb -p 8000
+   ```
+
+   **mogdb** is the name of the database to be connected, and **8000** is the port number of the database primary node.
+
+3. View the current value.
+
+   ```sql
+   mogdb=# SHOW failed_login_attempts;
+    failed_login_attempts
+   -----------------------
+    10
+   (1 row)
+   ```
+
+   If the command output is not **10**, run the **\q** command to exit the database.
+
+4. Run the following command to set the parameter to its default value **10**:
+
+   ```bash
+   gs_guc reload -D /mogdb/data/dbnode -c "failed_login_attempts=10"
+   ```
+
+Configure the **password_lock_time** parameter.
+
+1. Log in as the OS user **omm** to the primary node of the database.
+
+2. Run the following command to connect to the database:
+
+   ```bash
+   gsql -d mogdb -p 8000
+   ```
+
+   **mogdb** is the name of the database to be connected, and **8000** is the port number of the database primary node.
+
+3. View the current value.
+
+   ```sql
+   mogdb=# SHOW password_lock_time;
+    password_lock_time
+   -----------------------
+    1
+   (1 row)
+   ```
+
+   If the command output is not **1**, run the **\q** command to exit the database.
+
+4. Run the following command to set the parameter to its default value **1**:
+
+   ```bash
+   gs_guc reload -N all -I all -c "password_lock_time=1"
+   ```
+
+**Manually Locking and Unlocking Accounts**
+
+Once detecting that an account is stolen or the account is used to access the database without being authorized, administrators can manually lock the account.
+
+Administrators can manually unlock the account if the account becomes normal again.
+
+For details about how to create a user, see Users. To manually lock and unlock user **joe**, run commands in the following format:
+
+- To manually lock the account, run the following command:
+
+  ```sql
+  mogdb=# ALTER USER joe ACCOUNT LOCK;
+  ALTER ROLE
+  ```
+
+- To manually unlock the account, run the following command:
+
+  ```sql
+  mogdb=# ALTER USER joe ACCOUNT UNLOCK;
+  ALTER ROLE
+  ```
+
+**Deleting Accounts That Are No Longer Used**
+
+Administrators can delete an account that is no longer used. This operation cannot be rolled back.
+
+When an account to be deleted is in the active state, it is deleted after the session is disconnected.
+
+For example, if you want to delete account **joe**, run the following command:
+
+```sql
+mogdb=# DROP USER joe  CASCADE;
+DROP ROLE
+```
+
+### Setting the Validity Period of an Account
+
+**Precautions**
+
+When creating a user, you need to specify the validity period of the user, including the start time and end time.
+
+To enable a user not within the validity period to use its account, set a new validity period.
+
+**Procedure**
+
+1. Log in as the OS user **omm** to the primary node of the database.
+
+2. Run the following command to connect to the database:
+
+   ```bash
+   gsql -d mogdb -p 8000
+   ```
+
+   **mogdb** is the name of the database to be connected, and **8000** is the port number of the database primary node.
+
+3. Run the following command to create a user and specify the start time and end time:
+
+   ```sql
+   CREATE USER joe WITH PASSWORD 'XXXXXXXXX' VALID BEGIN '2015-10-10 08:00:00' VALID UNTIL '2016-10-10 08:00:00';
+   ```
+
+   The user is created if the following information is displayed:
+
+   ```sql
+   CREATE ROLE
+   ```
+
+4. If the user is not within the specified validity period, run the following command to set the start time and end time of a new validity period.
+
+   ```sql
+   ALTER USER joe WITH VALID BEGIN '2016-11-10 08:00:00' VALID UNTIL '2017-11-10 08:00:00';
+   ```
+
+   The start time and end time of the new validity period is set successfully if the following information is displayed:
+
+   ```sql
+   ALTER ROLE
+   ```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+> If **VALID BEGIN** is not specified in the **CREATE ROLE** or **ALTER ROLE** statement, the start time of the validity period is not limited. If **VALID UNTIL** is not specified, the end time of the validity period is not limited. If both of the parameters are not specified, the user is always valid.
+
+### Setting Password Security Policies
+
+**Procedure**
+
+User passwords are stored in the system catalog **pg_authid**. To prevent password leakage, MogDB encrypts user passwords before storing them. The encryption algorithm is determined by the configuration parameter **password_encryption_type**.
+
+- If parameter **password_encryption_type** is set to **0**, passwords are encrypted using MD5. MD5 is not recommended because it is insecure.
+- If parameter **password_encryption_type** is set to **1**, passwords are encrypted using SHA-256 and MD5. MD5 is not recommended because it is insecure.
+- If parameter **password_encryption_type** is set to **2**, passwords are encrypted using SHA-256. This is the default configuration.
+- If parameter **password_encryption_type** is set to **3**, passwords are encrypted using sm3. This is the default configuration.
+
+1. Log in as the OS user **omm** to the primary node of the database.
+
+2. Run the following command to connect to the database:
+
+   ```bash
+   gsql -d postgres -p 8000
+   ```
+
+   **postgres** is the name of the database to be connected, and **8000** is the port number of the database primary node.
+
+3. View the configured encryption algorithm.
+
+   ```sql
+   mogdb=# SHOW password_encryption_type;
+    password_encryption_type
+   --------------------------
+    2
+   (1 row)
+   ```
+
+   If the command output is **0** or **1**, run the **\q** command to exit the database.
+
+4. Set **gs_guc reload -Z coordinator -D** using a secure encryption algorithm:
+
+   ```bash
+   gs_guc reload -N all -I all -c "password_encryption_type=2"
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **NOTICE:** To prevent password leakage, when running **CREATE USER/ROLE** to create a database user, do not specify the **UNENCRYPTED** attribute. In this way, the password of the newly created user must be encrypted for storage.
+
+5. Configure password security parameters.
+
+   - Password complexity
+
+     You need to specify a password when initializing a database, creating a user, or modifying a user. The password must meet the complexity check rules (see password_policy). Otherwise, you are prompted to enter the password again.
+
+     - If parameter **password_policy** is set to **1**, the default password complexity rule is used to check passwords.
+     - If parameter **password_policy** is set to **0**, the password complexity is not verified. You are not advised to set the parameter to this value because it is insecure. Password complexity is skipped only if the **password_policy** parameter is set to **0** for all MogDB nodes.
+
+     Configure the **password_policy** parameter.
+
+     a. Run the following command to connect to the database:
+
+     ```bash
+     gsql -d postgres -p 8000
+     ```
+
+     **postgres** is the name of the database to be connected, and **8000** is the port number of the database primary node.
+
+     b. View the current value.
+
+     ```sql
+     mogdb=# SHOW password_policy;
+      password_policy
+     ---------------------
+       1
+     (1 row)
+     ```
+
+     If the command output is not **1**, run the **\q** command to exit the database.
+
+     c. Run the following command to set the parameter to its default value **1**:
+
+     ```bash
+     gs_guc reload -N all -I all -c "password_policy=1"
+     ```
+
+     > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **Note:**
+     >
+     > The password complexity requirements are as follows:
+     >
+     > - Minimum number of uppercase letters (A-Z) (**password_min_uppercase**)
+     >
+     > - Minimum number of lowercase letters (a-z) (**password_min_lowercase**)
+     >
+     > - Minimum number of digits (0-9) (**password_min_digital**)
+     >
+     > - Minimum number of special characters (**password_min_special**) ([Table 4](#Table-2.9.3.1) lists special characters.)
+     >
+     > - Minimum password length (**password_min_length**)
+     >
+     > - Maximum password length (**password_max_length**)
+     >
+     > - A password must contain at least three types of the characters (uppercase letters, lowercase letters, digits, and special characters)
+     >
+     > - A password is case insensitive and cannot be the username or the username spelled backwards.
+     >
+     > - A new password cannot be the current password and the current password spelled backwards.
+     >
+     > - A weak password is not allowed.
+     >
+     > - A weak password means that the password complexity is low and is easily cracked. For different users or groups, the definition of a weak password varies. Users need to define the weak password rule.
+     >
+     > - The password of a weak password dictionary is stored in the gs_global_config system table. When a user needs to set a password during user creation or modification, the system will compare the password set by a user with the passwords in the weak password dictionary. If the set password is defined as a weak password, the system prompts the user of changing the password.
+     >
+     > - The weak password dictionary is left blank by default. The user can run the following command to create or delete a weak password dictionary.
+     >
+     >   ```sql
+     >   mogdb=# CREATE WEAK PASSWORD DICTIONARY WITH VALUES ('password1'), ('password2');
+     >   mogdb=# DROP WEAK PASSWORD DICTIONARY;
+     >   ```
+
+   - Password reuse
+
+     An old password can be reused only when it meets the requirements on reuse days (**password_reuse_time**) and reuse times (**password_reuse_max**). [Table 5](#Table-2.9.3.2) lists the parameter configurations.
+
+     > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** The default values of the **password_reuse_time** and **password_reuse_max** parameters are **60** and **0**, respectively. Large values of the two parameters bring higher security. However, if the values of the parameters are set too large, inconvenience may occur. The default values of the two parameters meet the security requirements. You can change the parameter values as needed for higher security.
+
+     Configure the **password_reuse_time** parameter.
+
+     a. Run the following command to connect to the database:
+
+     ```bash
+     gsql -d postgres -p 8000
+     ```
+
+     **postgres** is the name of the database to be connected, and **8000** is the port number of the database primary node.
+
+     b. View the current value.
+
+     ```sql
+     mogdb=# SHOW password_reuse_time;
+      password_reuse_time
+     ---------------------
+      60
+     (1 row)
+     ```
+
+     If the command output is not **60**, run the **\q** command to exit the database.
+
+     c. Run the following command to set the parameter to its default value **60**:
+
+     > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** You are not advised to set the parameter to **0**. This value is valid only when **password_reuse_time** for all MogDB nodes is set to **0**.
+
+     ```bash
+     gs_guc reload -N all -I all -c "password_reuse_time=60"
+     ```
+
+     Configure the **password_reuse_max** parameter.
+
+     a. Run the following command to connect to the database:
+
+     ```bash
+     gsql -d postgres -p 8000
+     ```
+
+     **postgres** is the name of the database to be connected, and **8000** is the port number of the database primary node.
+
+     b. View the current value.
+
+     ```sql
+     mogdb=# SHOW password_reuse_max;
+      password_reuse_max
+     --------------------
+      0
+     (1 row)
+     ```
+
+     If the command output is not **0**, run the **\q** command to exit the database.
+
+     c. Run the following command to set the parameter to its default value **0**:
+
+     ```bash
+     gs_guc reload -N all -I all -c "password_reuse_max = 0"
+     ```
+
+   - Password validity period
+
+     A validity period (**password_effect_time**) is set for each database user password. If the password is about to expire (**password_notify_time**), the system displays a message to remind the user to change it upon login.
+
+     > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** Considering the usage and service continuity of a database, the database still allows a user to log in after the password expires. A password change notification is displayed every time the user logs in to the database until the password is changed.
+
+     Configure the **password_effect_time** parameter.
+
+     a. Run the following command to connect to the database:
+
+     ```bash
+     gsql -d postgres -p 8000
+     ```
+
+     **postgres** is the name of the database to be connected, and **8000** is the port number of the database primary node.
+
+     b. View the current value.
+
+     ```sql
+     mogdb=# SHOW password_effect_time;
+      password_effect_time
+     ----------------------
+      90
+     (1 row)
+     ```
+
+     If the command output is not **90**, run the **\q** command to exit the database.
+
+     c. Run the following command to set the parameter to **90** (**0** is not recommended):
+
+     ```bash
+     gs_guc reload -N all -I all -c "password_effect_time = 90"
+     ```
+
+     Configure the **password_notify_time** parameter.
+
+     a. Run the following command to connect to the database:
+
+     ```bash
+     gsql -d postgres -p 8000
+     ```
+
+     **postgres** is the name of the database to be connected, and **8000** is the port number of the database primary node.
+
+     b. View the current value.
+
+     ```sql
+     mogdb=# SHOW password_notify_time;
+      password_notify_time
+     ----------------------
+      7
+     (1 row)
+     ```
+
+     c. If **7** is not displayed, run the following command to set the parameter to **7** (**0** is not recommended):
+
+     ```bash
+     gs_guc reload -N all -I all -c "password_notify_time = 7"
+     ```
+
+   - Password change
+
+     - During database installation, an OS user with the same name as the initial user is created. The password of the OS user needs to be periodically changed for account security.
+
+       To change the password of user **user1**, run the following command:
+
+     ```sql
+       passwd user1
+     ```
+
+     Change the password as prompted.
+
+     - System administrators and common users need to periodically change their passwords to prevent the accounts from being stolen.
+
+     For example, to change the password of user **user1**, connect to the database as the system administrator and run the following commands:
+
+     ```sql
+       mogdb=# ALTER USER user1 IDENTIFIED BY "1234@abc" REPLACE "5678@def";
+     ALTER ROLE
+     ```
+
+       > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** **1234@abc** and **5678@def** represent the new password and the original password of user **user1**, respectively. If the new password does not have the required complexity, the change will not take effect.
+
+   - Administrators can change their own and common users' passwords. If common users forget their passwords, they can ask administrators to change the passwords.
+
+       To change the password of user **joe**, run the following command:
+
+        ```sql
+        mogdb=# ALTER USER joe IDENTIFIED BY "xxxxxxxx";
+        ALTER ROLE
+        ```
+
+       > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+       >
+       > - System administrators are not allowed to change passwords for each other.
+       > - A system administrator can change the password of a common user without being required to provide the common user's old password.
+       > - A system administrator can change their own password but is required to provide the old password.
+
+   - Password verification
+
+     Password verification is required when you set the user or role in the current session. If the entered password is inconsistent with the stored password of the user, an error is reported.
+
+     If user **joe** needs to be set, run the following command:
+
+     ```sql
+     mogdb=# SET ROLE joe PASSWORD "abc@1234";
+     ERROR:  Invalid username/password,set role denied.
+     ```
+
+     **Table 4** Special characters<a id="Table-2.9.3.1"> </a>
+
+     | No.  | Character | No.  | Character  | No.  | Character | No.  | Character |
+     | :--- | :-------- | :--- | :--------- | :--- | :-------- | :--- | :-------- |
+     | 1    | ~         | 9    | *          | 17   | \|        | 25   | &lt;      |
+     | 2    | !         | 10   | (          | 18   | [         | 26   | .         |
+     | 3    | @         | 11   | )          | 19   | {         | 27   | &gt;      |
+     | 4    | #         | 12   | -          | 20   | }         | 28   | /         |
+     | 5    | $         | 13   | _          | 21   | ]         | 29   | ?         |
+     | 6    | %         | 14   | =          | 22   | ;         | -    | -         |
+     | 7    | ^         | 15   | +          | 23   | :         | -    | -         |
+     | 8    | &         | 16   | &lt;/p&gt; | 24   | ,         | -    | -         |
+
+     **Table 5** Parameter description for reuse days and reuse times<a id="Table-2.9.3.2"> </a>
+
+     | Parameter                                                    | Value Range                                                  | Description                                                  |
+     | :----------------------------------------------------------- | :----------------------------------------------------------- | :----------------------------------------------------------- |
+     | Number of days during which a password cannot be reused (**password_reuse_time**) | Positive number or **0**. The integral part of a positive number indicates the number of days and its decimal part can be converted into hours, minutes, and seconds.<br/>By default, the number of days is set to **60**. | - If the parameter value is changed to a smaller one, new passwords will be checked based on the new parameter value.<br/>- If the parameter value is changed to a larger one (for example, changed from **a** to **b**), the historical passwords before **b** days probably can be reused because these historical passwords may have been deleted. New passwords will be checked based on the new parameter value.<br/>NOTE:<br/>The absolute time is used. Historical passwords are recorded using absolute time and unaffected by local time changes. |
+     | Number of consecutive times that a password cannot be reused (**password_reuse_max**) | Positive integer or **0**.The value **0** indicates that the number of consecutive times that a password cannot be reused is not checked. | - If the parameter value is changed to a smaller one, new passwords will be checked based on the new parameter value.<br/>- If the parameter value is changed to a larger one (for example, changed from **a** to **b**), the historical passwords before the last **b** passwords probably can be reused because these historical passwords may have been deleted. New passwords will be checked based on the new parameter value. |
+
+6. Set user password expiration.
+
+   A user with the CREATEROLE permission can create a user with the password expiration feature. The command format is as follows:
+
+   ```sql
+   mogdb=# CREATE USER joe PASSWORD "abc@1234" EXPIRED;
+      CREATE ROLE
+   ```
+
+   A user with the CREATEROLE permission can force a user password to expire or force a user to change the forcibly expired password. The command format is as follows:
+
+      ```sql
+      mogdb=# ALTER USER joe PASSWORD EXPIRED;
+      ALTER ROLE
+      ```
+
+      ```sql
+      mogdb=# ALTER USER joe PASSWORD "abc@2345" EXPIRED;
+      ALTER ROLE
+      ```
+
+      > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+      >
+      > - After logging in to the database, a user with the password expiration feature is prompted to change the password when the user tries to perform a simple or extended query. The user can then execute the statement after changing the password.
+      > - Only initial users, system administrators, or users who have permission to create users can set password expiration. Password expiration can be set by system administrators for themselves and other system administrators. Additionally, the password expiration cannot be set for initial users.
diff --git a/product/en/docs-mogdb/v3.0/security-guide/security/3-configuring-database-audit.md b/product/en/docs-mogdb/v3.0/security-guide/security/3-configuring-database-audit.md
new file mode 100644
index 0000000000000000000000000000000000000000..c7aecc16bfccebc213e85fbd56ee4ee714aa8076
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/security-guide/security/3-configuring-database-audit.md
@@ -0,0 +1,359 @@
+---
+title: Configuring Database Audit
+summary: Configuring Database Audit
+author: Guo Huan
+date: 2021-04-26
+---
+
+# Configuring Database Audit
+
+## Overview
+
+**Background**
+
+Database security is essential for a database system. MogDB writes all user operations in the database to audit logs. Database security administrators can use the audit logs to reproduce a series of events that cause faults in the database and identify unauthorized users, unauthorized operations, and the time when these operations are performed.
+
+You need to know the following about the audit function:
+
+- The overall audit switch **audit_enabled** supports dynamic loading. After you change the switch status when the database is running, the change takes effect immediately and you do not need to restart the database. Its default value is **on**, indicating that the audit function is enabled.
+- In addition to the overall audit switch, each audit item has an independent switch. The audit function takes effect only after its own switch is enabled.
+- The switch of each audit supports dynamic loading. After changing the switch status of an audit item when the database is running, the modification takes effect immediately and you do not need to restart the database.
+
+[Table 1](#Table-3.1.1) describes the audit items supported by MogDB.
+
+**Table 1** Audit items<a id="Table-3.1.1"> </a>
+
+| Configuration Item                                           | Description                                                  |
+| :----------------------------------------------------------- | :----------------------------------------------------------- |
+| User login and logout audit                                  | Parameter:**audit_login_logout**<br/>Its default value is **7**, which indicates that the function of user login and logout audit is enabled. **0** indicates that the function of user login and logout audit is disabled. Other values are not recommended. |
+| Database startup, stop, recovery, and switchover audit       | Parameter:**audit_database_process**<br/>Its default value is **1**, which indicates that the audit of database startup, stop, recovery, and switchover is enabled. |
+| User locking and unlocking audit                             | Parameter:**audit_user_locked**<br/>Its default value is **1**, which indicates that the audit of user locking and unlocking is enabled. |
+| Unauthorized access audit                                    | Parameter:**audit_user_violation**<br/>Its default value is **0**, which indicates that the audit of unauthorized access is disabled. |
+| Permission granting and revoking audit                       | Parameter:**audit_grant_revoke**<br/>Its default value is **1**, which indicates that the audit of permission granting and revoking is enabled. |
+| Audit of **CREATE**, **ALTER**, and **DROP** operations on database objects | Parameter:**audit_system_object**<br/>Its default value is **12295**, which indicates that the **CREATE**, **ALTER**, and **DROP** operations only on databases, schemas, users, data sources, and node groups are audited. |
+| Audit of **INSERT**, **UPDATE**, and **DELETE** operations on a specific table | Parameter:**audit_dml_state**<br/>Its default value is **0**, which indicates that the audit of DML operations (except **SELECT**) on a specific table is disabled. |
+| **SELECT** operation audit                                   | Parameter:**audit_dml_state_select**<br/>Its default value is **0**, which indicates that the audit of the **SELECT** operation is disabled. |
+| **COPY** operation audit                                     | Parameter:**audit_copy_exec**<br/>Its default value is **0**, which indicates that the audit of the **COPY** operation is disabled. |
+| Execution of stored procedures and customized functions      | Parameter:**audit_function_exec**<br/>Its default value is **0**, which indicates that no execution audit logs of stored procedures and customized functions are recorded. |
+| **SET** operation audit                                      | Parameter:**audit_set_parameter**<br/>Its default value is **1**, which indicates that the audit of the **SET** operation is enabled. |
+
+[Table 2](#Table-3.1.2) lists security-related parameters and their default values.
+
+**Table 2** Security-related parameters and their default values <a id="Table-3.1.2"> </a>
+
+| Parameter                   | Default Value | Description                                                  |
+| :-------------------------- | :------------ | :----------------------------------------------------------- |
+| ssl                         | on            | Specifies whether the SSL connection is enabled.             |
+| require_ssl                 | off           | Specifies whether the server requires the SSL connection.    |
+| ssl_ciphers                 | ALL           | Encryption algorithm list supported by the SSL               |
+| ssl_cert_file               | server.crt    | File containing the SSL server certificate                   |
+| ssl_key_file                | server.key    | File containing the SSL private key                          |
+| ssl_ca_file                 | cacert.pem    | File containing CA information                               |
+| ssl_crl_file                | NULL          | File containing CRL information                              |
+| password_policy             | 1             | Specifies whether to check the password complexity.          |
+| password_reuse_time         | 60            | Specifies whether to check the reuse days of a new password. |
+| password_reuse_max          | 0             | Specifies whether to check the reuse times of a new password. |
+| password_lock_time          | 1             | Duration before a locked account is automatically unlocked   |
+| failed_login_attempts       | 10            | If the number of consecutive login attempts with incorrect passwords reaches this value, the account is locked. |
+| password_encryption_type    | 2             | Password storage encryption mode                             |
+| password_min_uppercase      | 0             | Minimum number of uppercase letters in a password            |
+| password_min_lowercase      | 0             | Minimum number of lowercase letters in a password            |
+| password_min_digital        | 0             | Minimum number of digits in a password                       |
+| password_min_special        | 0             | Minimum number of special characters in a password           |
+| password_min_length         | 8             | Minimum password length<br/>NOTE:<br/>The value of this parameter must be less than or equal to that of **password_max_length**. Otherwise, a password length error message is displayed upon all password-related operations. |
+| password_max_length         | 32            | Maximum password length<br/>NOTE:<br/>The value of this parameter must be greater than or equal to that of **password_min_length**. Otherwise, a password length error message is displayed upon all password-related operations. |
+| password_effect_time        | 90            | Password validity period                                     |
+| password_notify_time        | 7             | Number of days prior to account password expiration that a user is notified |
+| audit_enabled               | on            | Specifies whether the audit process is enabled or disabled.  |
+| audit_directory             | pg_audit      | Audit file storage directory                                 |
+| audit_data_format           | binary        | Audit log file format. Currently, only the binary format is supported. |
+| audit_rotation_interval     | 1d            | Time interval of creating an audit log file. If the interval between the creation time of the last audit log file and the current time exceeds the parameter value, the server generates a new audit log file. |
+| audit_rotation_size         | 10MB          | Maximum capacity of an audit log file. If the total number of messages in an audit log exceeds the value of **audit_rotation_size**, the server will generate a new audit log file. |
+| audit_resource_policy       | on            | Policy for determining whether audit logs are preferentially stored by space or time. **on** indicates that audit logs are preferentially stored by space. |
+| audit_file_remain_time      | 90            | Minimum duration required for recording audit logs. This parameter is valid only when **audit_resource_policy** is set to **off**. |
+| audit_space_limit           | 1GB           | Maximum total size of audit log files in a disk              |
+| audit_file_remain_threshold | 1048576       | Maximum number of audit files in the audit directory         |
+| audit_login_logout          | 7             | Specifies whether to audit user logins (including login successes and failures) and logouts. |
+| audit_database_process      | 1             | Specifies whether to audit database startup, stop, switchover, and restoration operations. |
+| audit_user_locked           | 1             | Specifies whether to audit database user locking and unlocking. |
+| audit_user_violation        | 0             | Specifies whether to audit unauthorized access of database users. |
+| audit_grant_revoke          | 1             | Specifies whether to audit user permission granting and reclaiming operations. |
+| audit_system_object         | 12295         | Specifies whether to audit the **CREATE**, **DROP**, and **ALTER** operations on database objects. |
+| audit_dml_state             | 0             | Specifies whether to audit the **INSERT**, **UPDATE**, and **DELETE** operations on a specific table. |
+| audit_dml_state_select      | 0             | Specifies whether to audit the **SELECT** operation.         |
+| audit_copy_exec             | 0             | Specifies whether to audit the **COPY** operation.           |
+| audit_function_exec         | 0             | Specifies whether to record audit information during execution of stored procedures, anonymous blocks, or customized functions (excluding system functions). |
+| audit_set_parameter         | 1             | Specifies whether to audit the **SET** operation.            |
+| enableSeparationOfDuty      | off           | Specifies whether the separation of duties is enabled.       |
+| session_timeout             | 10min         | If the duration of a connection session exceeds the parameter value, the session is automatically disconnected. |
+| auth_iteration_count        | 10000         | Number of iterations during the generation of encrypted information for authentication |
+
+**Procedure**
+
+1. Log in as the OS user **omm** to the primary node of the database.
+
+2. Run the following command to connect to the database:
+
+   ```bash
+   gsql -d mogdb -p 8000
+   ```
+
+   **mogdb** is the name of the database to be connected, and **8000** is the port number of the database primary node.
+
+3. Check the status of the overall audit switch.
+
+   1. Run the **show** command to view the value of **audit_enabled**.
+
+      ```sql
+      mogdb=# SHOW audit_enabled;
+      ```
+
+      If the status is **off**, run the **\q** command to exit the database.
+
+   2. Run the following command to enable the audit function. The parameter settings take effect immediately.
+
+      ```bash
+      gs_guc set -N all -I all -c "audit_enabled=on"
+      ```
+
+4. Configure specific audit items.
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+   >
+   > - After the audit function is enabled, user operations can be recorded into an audit file.
+   > - The default parameter value of each audit item meets security standards. You can enable other audit functions, but doing so may affect the system performance.
+
+   For example, you can enable the audit switch of the **CREATE**, **DROP**, and **ALTER** operations on all database objects. The methods of modifying other configuration items are similar to it.
+
+   ```bash
+   gs_guc reload -N all -I all -c "audit_system_object=12295"
+   ```
+
+   **audit_system_object** indicates the switch of the audit item, and **12295** indicates the value of the audit switch.
+
+## Querying Audit Results
+
+**Prerequisites**
+
+- Audit has been enabled.
+- Audit of required items has been enabled.
+- The database is running properly and a series of addition, modification, deletion, and query operations have been executed in the database. Otherwise, no audit result is generated.
+- Audit logs are separately recorded on the database nodes.
+
+**Background**
+
+- Only users with the **AUDITADMIN** permission can view audit records. For details about database users and how to create users, see [Users](2-managing-users-and-their-permissions#users).
+
+- The SQL function **pg_query_audit** is provided by the database for audit query. Its syntax is as follows:
+
+  ```bash
+  pg_query_audit(timestamptz startime,timestamptz endtime,audit_log)
+  ```
+
+  **startime** and **endtime** indicate the start time and end time of the audit record, respectively. **audit_log** indicates the physical file path of the queried audit logs. If **audit_log** is not specified, the audit log information of the current instance is queried.
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  > The difference between the values of the **startime** and **endtime** parameters indicates the query period, which can be any value ranging from 00:00:00 of the **startime** parameter to 23:59:9 of the **endtime** parameter. Therefore, the **startime** and **endtime** parameters must be properly set to ensure that the required audit information is displayed.
+
+**Procedure**
+
+1. Log in as the OS user **omm** to the primary node of the database.
+
+2. Run the following command to connect to the database:
+
+   ```bash
+   gsql -d mogdb -p 8000
+   ```
+
+   **mogdb** is the name of the database to be connected, and **8000** is the port number of the database primary node.
+
+3. Run the following command to query the audit record:
+
+   ```sql
+   mogdb=# select * from pg_query_audit('2021-03-04 08:00:00','2021-03-04 17:00:00');
+   ```
+
+   The command output is similar to the following:
+
+   ```
+   time          |      type      | result | userid | username  | database  |     client_conninfo     |    object_name    |  detail_info |     node_name     |            thread_id            | local_port | remote_port
+   ------------------------+----------------+--------+--------+-----------+-----------+-------------------------+-------------------+--------------+-------------------+---------------------------------+------------+-------------
+   2021-03-04 08:00:08+08 | login_success  | ok     | 10     | omm  | mogdb | gsql@::1 | mogdb    | login db(postgres) success,the current user is:omm | dn_6001_6002_6003 | 140477687527168@668131208211425 |   17778      | 46946
+   ```
+
+   This audit record indicates that user **omm** logged in to the **mogdb** at the time specified by the **time** column. After the host specified by **log_hostname** is started and a client is connected to its IP address, the host name found by reverse DNS resolution is displayed following the at sign (@) in the value of **client_conninfo**.
+
+## Maintaining Audit Logs
+
+**Prerequisites**
+
+You have the audit permission.
+
+**Background**
+
+- [Table 1](#Table-3.3.1) lists the configuration parameters related to audit logs and the parameter descriptions.
+
+  **Table 1** Configuration parameters of audit logs<a id="Table-3.3.1"> </a>
+
+  | Parameter                   | Description                                          | Default Value                                                |
+  | :-------------------------- | :--------------------------------------------------- | :----------------------------------------------------------- |
+  | audit_directory             | Audit file storage directory                         | /var/log/mogdb/**User name**/pg_audit                        |
+  | audit_resource_policy       | Policy for saving audit logs                         | **on** (indicating that the space configuration policy is used) |
+  | audit_space_limit           | Maximum storage space occupied by audit files        | 1GB                                                          |
+  | audit_file_remain_time      | Minimum period for storing audit log files           | 90                                                           |
+  | audit_file_remain_threshold | Maximum number of audit files in the audit directory | 1048576                                                      |
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+  >
+  > If **gs_om** is used for MogDB deployment, audit logs are stored in **/var/log/mogdb/Username/pg_audit**.
+
+- The **pg_delete_audit** function is used to delete audit logs and is an internal SQL function of the database. Its syntax is as follows:
+
+  ```bash
+  pg_delete_audit(timestamp startime,timestamp endtime)
+  ```
+
+  **startime** and **endtime** indicate the audit record start time and end time, respectively.
+
+- Audit content is commonly recorded to database tables or OS files. [Table 2](#Table-3.3.2) lists the advantages and disadvantages of the two record methods.
+
+  **Table 2** Comparison between the two record methods<a id="Table-3.3.2"> </a>
+
+  | Mode               | Advantage                                                    | Disadvantage                                                 |
+  | :----------------- | :----------------------------------------------------------- | :----------------------------------------------------------- |
+  | Record in tables   | Users do not need to maintain audit logs.                    | Any users having certain permissions to access database objects can access the audit tables. If a user illegally performs operations on the audit tables, the audit records may become inaccurate. |
+  | Record in OS files | This method has higher security because a user with the permission to access the database may not have the permission to access the OS files. | Users need to maintain audit logs.                           |
+
+  For database security purposes, MogDB adopts the second method to save audit results for reliability.
+
+**Procedure**
+
+1. Log in as the OS user **omm** to the primary node of the database.
+
+2. Run the following command to connect to the database:
+
+   ```bash
+   gsql -d mogdb -p 8000
+   ```
+
+   **mogdb** is the name of the database to be connected, and **8000** is the port number of the database primary node.
+
+3. Select a method to maintain audit logs.
+
+   - Automatic deletion of audit logs
+
+     If the storage space occupied by audit files or the number of audit files reaches the upper limit, the system automatically deletes the oldest audit files and records deletion information to audit logs.
+
+     > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+     > By default, the allowed maximum storage space that can be occupied by audit files is set to 1024 MB. Users can set the value as required.
+
+     Configure the allowed maximum size of storage space occupied by audit files (**audit_space_limit**).
+
+     a. View the current value.
+
+     ```sql
+     mogdb=# SHOW audit_space_limit;
+      audit_space_limit
+     -------------------
+      1GB
+     (1 row)
+     ```
+
+     If the command output is not 1 GB (1024 MB), run the **\q** command to exit the database.
+
+     b. Run the following command to set the parameter to its default value **1024MB**:
+
+     ```bash
+     gs_guc reload -N all -I all -c "audit_space_limit=1024MB"
+     ```
+
+     Configure the maximum number of audit files (**audit_file_remain_threshold**).
+
+     a. View the current value.
+
+     ```sql
+     mogdb=# SHOW audit_file_remain_threshold;
+      audit_file_remain_threshold
+     -----------------------------
+      1048576
+     (1 row)
+     ```
+
+     If the command output is not 1048576, run the **\q** command to exit the database.
+
+     b. Run the following command to set the parameter to its default value **1048576**:
+
+     ```bash
+     gs_guc reload -N all -I all -c "audit_file_remain_threshold=1048576"
+     ```
+
+   - Manual backup of audit files
+
+     If the storage space occupied by audit files or the number of audit logs exceeds the threshold specified by the configuration file, the system automatically deletes the oldest audit files. Therefore, you are advised to periodically save important audit logs.
+
+     a. Run the **show** command to view the directory (**audit_directory**) where audit files are saved.
+
+     ```sql
+     mogdb=# SHOW audit_directory;
+     ```
+
+     b. Copy the entire audit directory elsewhere to save it.
+
+   - Manual deletion of audit files
+
+     Run the **pg_delete_audit** command to manually delete the audit records generated during a specified period of time.
+
+     Example: Manually delete the audit records generated from September 20, 2012 to September 21, 2012.
+
+     ```sql
+     SELECT pg_delete_audit('2012-09-20 00:00:00','2012-09-21 23:59:59');
+     ```
+
+## Configuring File Permission Security Policies
+
+**Background**
+
+During its installation, the database sets permissions for its files, including files (such as log files) generated during the running process. File permissions are set as follows:
+
+- The permission of program directories in the database is set to **0750**.
+
+- The permission for data file directories in the database is set to **0700**.
+
+  During MogDB deployment, the directory specified by the **tmpMppdbPath** parameter in the XML configuration file is created for storing **.s.PGSQL.\*** files. If the parameter is not specified, the **/tmp/$USER_mppdb** directory is created. The directory and file permission is set to **0700**.
+
+- The permissions of data files and audit logs of the database, as well as data files generated by other database programs, are set to **0600**. The permission of run logs is equal to or lower than **0640** by default.
+
+- Common OS users are not allowed to modify or delete database files and log files.
+
+**Directory and File Permissions of Database Programs**
+
+[Table 1](#Table-3.4.1) lists some of program directories and file permissions of the installed database.
+
+**Table 1** Program directories and file permissions<a id="Table-3.4.1"> </a>
+
+| File or Directory                          | Parent Contents                        | Permissions |
+| :----------------------------------------- | :------------------------------------- | :---------- |
+| bin                                        | -                                      | 0700        |
+| lib                                        | -                                      | 0700        |
+| share                                      | -                                      | 0700        |
+| data (database node/primary database node) | -                                      | 0700        |
+| base                                       | Instance data directory                | 0700        |
+| global                                     | Instance data directory                | 0700        |
+| pg_audit                                   | Instance data directory (configurable) | 0700        |
+| pg_log                                     | Instance data directory (configurable) | 0700        |
+| pg_xlog                                    | Instance data directory                | 0700        |
+| postgresql.conf                            | Instance data directory                | 0600        |
+| pg_hba.conf                                | Instance data directory                | 0600        |
+| postmaster.opts                            | Instance data directory                | 0600        |
+| pg_ident.conf                              | Instance data directory                | 0600        |
+| gs_initdb                                  | bin                                    | 0700        |
+| gs_dump                                    | bin                                    | 0700        |
+| gs_ctl                                     | bin                                    | 0700        |
+| gs_guc                                     | bin                                    | 0700        |
+| gsql                                       | bin                                    | 0700        |
+| archive_status                             | pg_xlog                                | 0700        |
+| libpq.so.5.5                               | lib                                    | 0600        |
+
+**Suggestion**
+
+During the installation, the database automatically sets permissions for its files, including files (such as log files) generated during the running process. The specified permissions meet permission requirements in most scenarios. If you have any special requirements for the related permissions, you are advised to periodically check the permission settings to ensure that the permissions meet the product requirements.
diff --git a/product/en/docs-mogdb/v3.0/security-guide/security/4-setting-encrypted-equality-query.md b/product/en/docs-mogdb/v3.0/security-guide/security/4-setting-encrypted-equality-query.md
new file mode 100644
index 0000000000000000000000000000000000000000..614108c4d47dc78eb6096687a6cfefbcae1129b3
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/security-guide/security/4-setting-encrypted-equality-query.md
@@ -0,0 +1,324 @@
+---
+title: Setting Encrypted Equality Query
+summary: Setting Encrypted Equality Query
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# Setting Encrypted Equality Query
+
+## Overview
+
+As enterprise data is migrated to the cloud, data security and privacy protection are facing increasingly severe challenges. The encrypted database will solve the privacy protection issues in the entire data lifecycle, covering network transmission, data storage, and data running status. Furthermore, the encrypted database can implement data privacy permission separation in a cloud scenario, that is, separate data owners from data administrators in terms of the read permission. The encrypted equality query is used to solve equality query issues of ciphertext data. The encrypted equality query supports the client tool GSQL and JDBC. The following describes how to use the client tool to perform operations related to encrypted equality query.
+
+## Using GSQL to Operate an Encrypted Database
+
+1. Log in as the OS user **omm** to the primary node of the database.
+
+2. When you use gsql to connect to database server, you need to use "-C" parameter or "--enable-client-encryption" to enable the encryption function. Run the following command to enable the encryption function and connect to the encrypted database:
+
+   ```bash
+   gsql -p PORT postgres -r -C
+   ```
+
+3. Create a CMK and a CEK. For details about the syntax for creating a CMK and CEK, see [CREATE CLIENT MASTER KEY](42-CREATE-CLIENT-MASTER-KEY) and [CREATE COLUMN ENCRYPTION KEY](43-CREATE-COLUMN-ENCRYPTION-KEY).
+
+   ```sql
+   -- Create a CMK.
+   mogdb=# CREATE CLIENT MASTER KEY ImgCMK1 WITH (KEY_STORE = localkms, KEY_PATH = "key_path_value1", ALGORITHM = RSA_2048);
+   mogdb=# CREATE CLIENT MASTER KEY ImgCMK WITH (KEY_STORE = localkms, KEY_PATH = "key_path_value2", ALGORITHM = RSA_2048);
+   mogdb=# CREATE COLUMN ENCRYPTION KEY ImgCEK1 WITH VALUES (CLIENT_MASTER_KEY = ImgCMK1, ALGORITHM  = AEAD_AES_256_CBC_HMAC_SHA256);
+   CREATE COLUMN ENCRYPTION KEY
+   mogdb=# CREATE COLUMN ENCRYPTION KEY ImgCEK WITH VALUES (CLIENT_MASTER_KEY = ImgCMK, ALGORITHM  = AEAD_AES_256_CBC_HMAC_SHA256);
+   CREATE COLUMN ENCRYPTION KEY
+   ```
+
+   The query result of the system catalog that stores the key information is as follows.
+
+   ```sql
+   mogdb=# SELECT * FROM gs_client_global_keys;
+    global_key_name | key_namespace | key_owner | key_acl |        create_date
+   -----------------+---------------+-----------+---------+----------------------------
+    imgcmk1         |          2200 |        10 |         | 2021-04-21 11:04:00.656617
+    imgcmk          |          2200 |        10 |         | 2021-04-21 11:04:05.389746
+   (2 rows)
+   mogdb=# SELECT column_key_name,column_key_distributed_id ,global_key_id,key_owner  FROM gs_column_keys;
+    column_key_name | column_key_distributed_id | global_key_id | key_owner
+   -----------------+---------------------------+---------------+-----------
+    imgcek1         |                 760411027 |         16392 |        10
+    imgcek          |                3618369306 |         16398 |        10
+   (2 rows)
+   ```
+
+4. Create an encrypted table.
+
+   ```sql
+   mogdb=# CREATE TABLE creditcard_info (id_number    int, name         text encrypted with (column_encryption_key = ImgCEK, encryption_type = DETERMINISTIC),
+   credit_card  varchar(19) encrypted with (column_encryption_key = ImgCEK1, encryption_type = DETERMINISTIC));
+   NOTICE:  The 'DISTRIBUTE BY' clause is not specified. Using 'id_number' as the distribution column by default.
+   HINT:  Please use 'DISTRIBUTE BY' clause to specify suitable data distribution column.
+   CREATE TABLE
+   ```
+
+   Query the detailed information about the table. If the value of **Modifiers** is **encrypted**, the column is encrypted.
+
+   ```sql
+   mogdb=# \d creditcard_info
+           Table "public.creditcard_info"
+      Column    |       Type        | Modifiers
+   -------------+-------------------+------------
+    id_number   | integer           |
+    name        | text              |  encrypted
+    credit_card | character varying |  encrypted
+   ```
+
+5. Insert data into the encrypted table and perform an equality query.
+
+   ```sql
+   mogdb=# INSERT INTO creditcard_info VALUES (1,'joe','6217986500001288393');
+   INSERT 0 1
+   mogdb=# INSERT INTO creditcard_info VALUES (2, 'joy','6219985678349800033');
+   INSERT 0 1
+   mogdb=# select * from creditcard_info where name = 'joe';
+    id_number | name |     credit_card
+   -----------+------+---------------------
+            1 | joe  | 6217986500001288393
+   (1 row)
+   -- Note: The data in the encrypted table is displayed in ciphertext when you use a non-encrypted client to view the data.
+   mogdb=# select id_number,name from creditcard_info;
+    id_number |                                                                         name
+   -----------+------------------------------------------------------------------------------------------------------------------------------------------------------
+            1 | \x011aefabd754ded0a536a96664790622487c4d366d313aecd5839e410a46d29cba96a60e4831000000ee79056a114c9a6c041bb552b78052e912a8b730609142074c63791abebd0d38
+            2 | \x011aefabd76853108eb406c0f90e7c773b71648fa6e2b8028cf634b49aec65b4fcfb376f3531000000f7471c8686682de215d09aa87113f6fb03884be2031ef4dd967afc6f7901646b
+   (2 rows)
+   ```
+
+6. (Optional) Alter and update the encrypted table if necessary.
+
+   ```sql
+   mogdb=# ALTER TABLE creditcard_info ADD COLUMN age int ENCRYPTED WITH (COLUMN_ENCRYPTION_KEY = ImgCEK, ENCRYPTION_TYPE = DETERMINISTIC);
+   ALTER TABLE
+   mogdb=# \d creditcard_info
+           Table "public.creditcard_info"
+      Column    |       Type        | Modifiers
+   -------------+-------------------+------------
+    id_number   | integer           |
+    name        | text              |  encrypted
+    credit_card | character varying |  encrypted
+    age         | integer           |  encrypted
+   mogdb=# ALTER TABLE creditcard_info DROP COLUMN age;
+   ALTER TABLE
+   mogdb=# update creditcard_info set credit_card = '80000000011111111' where name = 'joy';
+   UPDATE 1
+   mogdb=# select * from creditcard_info  where name = 'joy';
+    id_number | name |    credit_card
+   -----------+------+-------------------
+            2 | joy  | 80000000011111111
+   (1 row)
+   ```
+
+## Using JDBC to Operate an Encrypted Database
+
+### Connecting to an Encrypted Database
+
+For details about the JDBC connection parameters, see [Development Based on JDBC](1-development-based-on-jdbc-overview). To support JDBC operations on an encrypted database, set **enable_ce** to **1**. The following is an example:
+
+```java
+public static Connection getConnect(String username, String passwd)
+    {
+        // Set the driver class.
+        String driver = "org.postgresql.Driver";
+        // Set the database connection descriptor.
+        String sourceURL = "jdbc:postgresql://10.10.0.13:8000/postgres?enable_ce=1";
+        Connection conn = null;
+
+        try
+        {
+            // Load the driver.
+            Class.forName(driver);
+        }
+        catch( Exception e )
+        {
+            e.printStackTrace();
+            return null;
+        }
+
+        try
+        {
+             // Establish a connection.
+            conn = DriverManager.getConnection(sourceURL, username, passwd);
+            System.out.println("Connection succeed!");
+        }
+        catch(Exception e)
+        {
+            e.printStackTrace();
+            return null;
+        }
+
+        return conn;
+    };
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - [Proposal] When JDBC is used to perform operations on an encrypted database, one database connection object corresponds to one thread. Otherwise, conflicts may occur due to thread changes.
+> - [Proposal] When JDBC is used to perform operations on an encrypted database, different connections change the encrypted configuration data. The client invokes the **IsValid** method to ensure that the connections can hold the changed encrypted configuration data. In this case, the **refreshClientEncryption** parameter must be set to **1** (default value). In a scenario where a single client performs operations on encrypted data, the **refreshClientEncryption** parameter can be set to **0**.
+
+### Example of Calling the IsValid Method to Refresh the Cache
+
+```java
+// Create a CMK.
+Connection conn1 = DriverManager.getConnection("url","user","password");
+
+// Connection 1 calls the IsValid method to refresh the cache.
+try {
+ if (!conn1.isValid(60)) {
+  System.out.println("isValid Failed for connection 1");
+ }
+} catch (SQLException e) {
+ e.printStackTrace();
+        return null;
+}
+```
+
+### Creating Keys for Executing Encrypted Equality Query
+
+```java
+// Create a CMK.
+Connection conn = DriverManager.getConnection("url","user","password");
+Statement stmt = conn.createStatement();
+int rc = stmt.executeUpdate("CREATE CLIENT MASTER KEY ImgCMK1 WITH ( KEY_STORE = localkms, KEY_PATH = \"key_path_value\" , ALGORITHM = RSA_2048);
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** Before creating a CMK, you need to use the **gs_ktool** tool to generate a key.
+
+```java
+// Create a CEK.
+int rc2 = stmt.executeUpdate("CREATE COLUMN ENCRYPTION KEY ImgCEK1 WITH VALUES (CLIENT_MASTER_KEY = ImgCMK1, ALGORITHM  = AEAD_AES_256_CBC_HMAC_SHA256);");
+```
+
+### Creating an Encrypted Table for Executing Encrypted Equality Query
+
+```java
+int rc3 = stmt.executeUpdate("CREATE TABLE creditcard_info (id_number    int, name  varchar(50) encrypted with (column_encryption_key = ImgCEK1, encryption_type = DETERMINISTIC),credit_card  varchar(19) encrypted with (column_encryption_key = ImgCEK1, encryption_type = DETERMINISTIC));");
+// Insert data.
+int rc4 = stmt.executeUpdate("INSERT INTO creditcard_info VALUES (1,'joe','6217986500001288393');");
+// Query the encrypted table.
+ResultSet rs = null;
+rs = stmt.executeQuery("select * from creditcard_info where name = 'joe';");
+// Close the statement object.
+stmt.close();
+```
+
+### Precompiling the Encrypted Table
+
+```java
+// Create a prepared statement object by calling the prepareStatement method in Connection.
+PreparedStatement pstmt = con.prepareStatement("INSERT INTO creditcard_info VALUES (?, ?, ?);");
+// Set parameters by triggering the setShort method in PreparedStatement.
+pstmt.setInt(1, 2);
+pstmt.setString(2, "joy");
+pstmt.setString(3, "6219985678349800033");
+// Execute the precompiled SQL statement by triggering the executeUpdate method in PreparedStatement.
+int rowcount = pstmt.executeUpdate();
+// Close the precompiled statement object by calling the close method in PreparedStatement.
+pstmt.close();
+```
+
+### Batch Processing on Encrypted Tables
+
+```java
+// Create a prepared statement object by calling the prepareStatement method in Connection.
+Connection conn = DriverManager.getConnection("url","user","password");
+PreparedStatement pstmt = conn.prepareStatement("INSERT INTO batch_table (id, name, address) VALUES (?,?,?)");
+// Call the setShort method for each piece of data, and call addBatch to confirm that the setting is complete.
+int loopCount = 20;
+ for (int i = 1; i < loopCount + 1; ++i) {
+      statemnet.setInt(1, i);
+      statemnet.setString(2, "Name " + i);
+      statemnet.setString(3, "Address " + i);
+      // Add row to the batch.
+      statemnet.addBatch();
+}
+// Execute batch processing by calling the executeBatch method in PreparedStatement.
+int[] rowcount = pstmt.executeBatch();
+// Close the precompiled statement object by calling the close method in PreparedStatement.
+pstmt.close();
+```
+
+## Encrypted Functions and Stored Procedures
+
+In the current version, only encrypted functions and stored procedures in SQL or PL/pgSQL are supported. Because users are unaware of the creation and execution of functions or stored procedures in an encrypted stored procedure, the syntax has no difference from that of non-encrypted functions and stored procedures.
+
+The **gs_encrypted_proc** system catalog is added to the function or stored procedure for encrypted equality query to store the returned original data type.
+
+### Creating and Executing a Function or Stored Procedure that Involves Encrypted Columns
+
+1. Create a key. For details, see [Using GSQL to Operate an Encrypted Database](#Using GSQL to Operate an Encrypted Database) and [Using JDBC to Operate an Encrypted Database](#Using JDBC to Operate an Encrypted Database).
+
+2. Create an encrypted table.
+
+   ```sql
+   mogdb=# CREATE TABLE creditcard_info (
+   mogdb(#   id_number int,
+   mogdb(#   name  text,
+   mogdb(#   credit_card varchar(19) encrypted with (column_encryption_key = ImgCEK1, encryption_type = DETERMINISTIC)
+   mogdb(# ) with (orientation=row) distribute by hash(id_number);
+   CREATE TABLE
+   ```
+
+3. Insert data.
+
+   ```sql
+   mogdb=# insert into creditcard_info values(1, 'Avi', '1234567890123456');
+   INSERT 0 1
+   mogdb=# insert into creditcard_info values(2, 'Eli', '2345678901234567');
+   INSERT 0 1
+   ```
+
+4. Create a function supporting encrypted equality query.
+
+   ```sql
+   mogdb=# CREATE FUNCTION f_encrypt_in_sql(val1 text, val2 varchar(19)) RETURNS text AS 'SELECT name from creditcard_info where name=$1 or credit_card=$2 LIMIT 1' LANGUAGE SQL;
+   CREATE FUNCTION
+   mogdb=# CREATE FUNCTION f_encrypt_in_plpgsql (val1 text, val2 varchar(19))
+   mogdb-# RETURNS text AS $$
+   mogdb$# DECLARE
+   mogdb$# c text;
+   mogdb$# BEGIN
+   mogdb$#     SELECT into c name from creditcard_info where name=$1 or credit_card =$2 LIMIT 1;
+   mogdb$#     RETURN c;
+   mogdb$# END; $$
+   mogdb-# LANGUAGE plpgsql;
+   CREATE FUNCTION
+   ```
+
+5. Execute the function.
+
+   ```sql
+   mogdb=# SELECT f_encrypt_in_sql('Avi','1234567890123456');
+    f_encrypt_in_sql
+   ------------------
+    Avi
+   (1 row)
+   
+   mogdb=# SELECT f_encrypt_in_plpgsql('Avi', val2=>'1234567890123456');
+    f_encrypt_in_plpgsql
+   ----------------------
+    Avi
+   (1 row)
+   ```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+>
+> - Because the query, that is, the dynamic query statement executed in a function or stored procedure, is compiled during execution, the table name and column name in the function or stored procedure must be known in the creation phase. The input parameter cannot be used as a table name or column name, or any connection mode.
+> - Among the **RETURNS**, **IN**, and **OUT** parameters, encrypted and non-encrypted parameters cannot be used together. Although the parameter types are all original, the actual types are different.
+> - For advanced package interfaces, for example, **dbe_output.print_line()**, decryption is not performed on the interfaces whose output is printed on the server. This is because when the encrypted data type is forcibly converted into the plaintext original data type, the default value of the data type is printed.
+> - In the current version, **LANGUAGE** of functions and stored procedures can only be **SQL** and **PL/pgSQL**, and does not support other procedural languages such as **C** and **Java**.
+> - Other functions or stored procedures for querying encrypted columns cannot be executed in a function or stored procedure.
+> - In the current version, default values cannot be assigned to variables in **DEFAULT** or **DECLARE** statements, and return values in **DECLARE** statements cannot be decrypted. You can use input parameters and output parameters instead when executing functions.
+> - **gs_dump** cannot be used to back up functions involving encrypted columns.
+> - Keys cannot be created in functions or stored procedures.
+> - In this version, encrypted functions and stored procedures do not support triggers.
+> - Encrypted equality query functions and stored procedures do not support the escape of the PL/pgSQL syntax. The **CREATE FUNCTION AS** '*Syntax body*' syntax whose syntax body is marked with single quotation marks (") can be replaced with the **CREATE FUNCTION AS** '*Syntax body*' syntax.
+> - The definition of an encrypted column cannot be modified in an encrypted equality query function or stored procedure, including creating an encrypted table and adding an encrypted column. Because the function is executed on the server, the client cannot determine whether the cache needs to be refreshed. The column can be encrypted only after the client is disconnected or the cache of the encrypted column on the client is refreshed.
diff --git a/product/en/docs-mogdb/v3.0/security-guide/security/5-setting-a-ledger-database.md b/product/en/docs-mogdb/v3.0/security-guide/security/5-setting-a-ledger-database.md
new file mode 100644
index 0000000000000000000000000000000000000000..9db5aaa0f2708f4fffc3c1bde4b5db378a00a2ec
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/security-guide/security/5-setting-a-ledger-database.md
@@ -0,0 +1,400 @@
+---
+title: Setting a Ledger Database
+summary: Setting a Ledger Database
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# Setting a Ledger Database
+
+## Overview
+
+### Background
+
+The ledger database, which integrates a blockchain idea, records a user operation in two types of historical tables: a user history table and a global blockchain table. When a user creates a tamper-proof user table, the system automatically adds a hash column to the table to save the hash summary of each row of data. In blockchain mode, a user history table is created to record the change behavior of each data record in the user table. The user's modification to the tamper-proof user table will be recorded in the global blockchain table. Because the history table can only be appended and cannot be modified, the records in the history table are connected to form the modification history of the tamper-proof user table.
+
+The name and structure of the user history table are as follows:
+
+**Table 1** Columns in the blockchain._hist user history table<a id="table1"></a>
+
+| Column Name | Data Type | Description                                                  |
+| :---------- | :-------- | :----------------------------------------------------------- |
+| rec_num     | bigint    | Sequence number of a row-level modification operation in the history table |
+| hash_ins    | hash16    | Hash value of the data row inserted by the INSERT or UPDATE operation |
+| hash_del    | hash16    | Hash value of the data row deleted by the DELETE or UPDATE operation |
+| pre_hash    | hash32    | Summary of the data in the history table of the current user |
+
+**Table 2** Mapping between hash_ins and hash_del
+
+| -      | hash_ins                                  | hash_del                                  |
+| ------ | ----------------------------------------- | ----------------------------------------- |
+| INSERT | (√) Hash value of the inserted row        | Empty                                     |
+| DELETE | Empty                                     | (√) Hash value of the deleted row         |
+| UPDATE | (√) Hash value of the newly inserted data | (√) Hash value of the row before deletion |
+
+### Procedure
+
+1. Create a schema in tamper-proof mode.
+
+   For example, create **ledgernsp** in tamper-proof mode.
+
+   ```sql
+   mogdb=# CREATE SCHEMA ledgernsp WITH BLOCKCHAIN;
+   ```
+
+2. Create a tamper-proof user table in tamper-proof mode.
+
+   For example, create a tamper-proof user table **ledgernsp.usertable**.
+
+   ```sql
+   mogdb=# CREATE TABLE ledgernsp.usertable(id int, name text);
+   ```
+
+   Check the structure of the tamper-proof user table and the corresponding user history table.
+
+   ```sql
+   mogdb=# \d+ ledgernsp.usertable;
+                        Table "ledgernsp.usertable"
+    Column |  Type   | Modifiers | Storage  | Stats target | Description
+   --------+---------+-----------+----------+--------------+-------------
+    id     | integer |           | plain    |              |
+    name   | text    |           | extended |              |
+    hash   | hash16  |           | plain    |              |
+   Has OIDs: no
+   Distribute By: HASH(id)
+   Location Nodes: ALL DATANODES
+   Options: orientation=row, compression=no
+   History table name: ledgernsp_usertable_hist
+
+   mogdb=# \d+ blockchain.ledgernsp_usertable_hist;
+                Table "blockchain.ledgernsp_usertable_hist"
+     Column  |  Type  | Modifiers | Storage | Stats target | Description
+   ----------+--------+-----------+---------+--------------+-------------
+    rec_num  | bigint |           | plain   |              |
+    hash_ins | hash16 |           | plain   |              |
+    hash_del | hash16 |           | plain   |              |
+    pre_hash | hash32 |           | plain   |              |
+   Indexes:
+       "gs_hist_16388_index" PRIMARY KEY, btree (rec_num int4_ops) TABLESPACE pg_default
+   Has OIDs: no
+   Distribute By: HASH(rec_num)
+   Location Nodes: ALL DATANODES
+   Options: internal_mask=263
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+   >
+   > - Tamper-proof tables cannot be non-row-store tables, temporary tables, foreign tables, or unlogged tables. Non-row-store tables do not have the temper-proof attribute.
+   > - When a temper-proof table is created, a system column named **hash** is automatically added. Therefore, the maximum number of columns in the temper-proof table is 1599.
+
+3. Modify the data in the tamper-proof user table.
+
+   For example, execute **INSERT**, **UPDATE**, or **DELETE** on the tamper-proof user table.
+
+   ```sql
+   mogdb=# INSERT INTO ledgernsp.usertable VALUES(1, 'alex'), (2, 'bob'), (3, 'peter');
+   INSERT 0 3
+   mogdb=# SELECT *, hash FROM ledgernsp.usertable ORDER BY id;
+    id | name  |       hash
+   ----+-------+------------------
+     1 | alex  | 1f2e543c580cb8c5
+     2 | bob   | 8fcd74a8a6a4b484
+     3 | peter | f51b4b1b12d0354b
+   (3 rows)
+
+   mogdb=# UPDATE ledgernsp.usertable SET name = 'bob2' WHERE id = 2;
+   UPDATE 1
+   mogdb=# SELECT *, hash FROM ledgernsp.usertable ORDER BY id;
+    id | name  |       hash
+   ----+-------+------------------
+     1 | alex  | 1f2e543c580cb8c5
+     2 | bob2  | 437761affbb7c605
+     3 | peter | f51b4b1b12d0354b
+   (3 rows)
+
+   mogdb=# SELECT *, hash FROM ledgernsp.usertable ORDER BY id;
+    id | name  |       hash
+   ----+-------+------------------
+     1 | alex  | 1f2e543c580cb8c5
+     2 | bob2  | 437761affbb7c605
+     3 | peter | f51b4b1b12d0354b
+   (3 rows)
+
+   mogdb=# DELETE FROM ledgernsp.usertable WHERE id = 3;
+   DELETE 1
+   mogdb=# SELECT *, hash FROM ledgernsp.usertable ORDER BY id;
+    id | name |       hash
+   ----+------+------------------
+     1 | alex | 1f2e543c580cb8c5
+     2 | bob2 | 437761affbb7c605
+   (2 rows)
+   ```
+
+## Viewing Historical Operation Records in the Ledger
+
+### Prerequisites
+
+- You are an audit administrator or a role that has the audit administrator permissions.
+- The database is running properly, and a series of addition, deletion, and modification operations are performed on the tamper-proof database to ensure that operation records are generated in the ledger for query.
+
+### Background
+
+- Only users with the **AUDITADMIN** attribute can view historical operation records in the ledger. For details about database users and how to create users, see [Managing Users and Their Permissions](2-managing-users-and-their-permissions).
+
+- To query the global blockchain table **gs_global_chain**, run the following command:
+
+  ```sql
+  SELECT * FROM gs_global_chain;
+  ```
+
+  This table contains 11 fields. For details about the meaning of each field, see [GS_GLOBAL_CHAIN](GS_GLOBAL_CHAIN).
+
+- To query the user history table in **BLOCKCHAIN** mode,
+
+  for example, the schema of the user table is **ledgernsp**, the table name is **usertable**, and the name of the corresponding user history table is **blockchain.ledgernsp_usertable_hist**, you can run the following command:
+
+  ```sql
+  SELECT * FROM blockchain.ledgernsp_usertable_hist;
+  ```
+
+  The user history table contains four fields. For details about the meaning of each field, see [Table 1](#table1).
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:** Generally, the name of a user history table is in the format of blockchain.hist. If the schema name or table name of the tamper-proof user table is too long, the length of the table name generated using the preceding format may exceed the upper limit. In this case, the blockchain.hist format is used to name the table.
+
+### Procedure
+
+1. Log in as the OS user **omm** to the primary node of the database.
+
+2. Run the following command to connect to the database:
+
+   ```bash
+   gsql -d postgres -p 8000
+   ```
+
+   **postgres** is the name of the database, and **8000** is the port number.
+
+3. View records in the global blockchain table.
+
+   ```sql
+   mogdb=# SELECT * FROM gs_global_chain;
+    blocknum |  dbname  | username |           starttime           | relid |  relnsp   |  relname  |     relhash      |            globalhash            |
+                  txcommand
+   ----------+----------+----------+-------------------------------+-------+-----------+-----------+------------------+----------------------------------+------------------
+   ------------------------------------------------------------
+          0 | postgres | omm      | 2021-04-14 07:00:46.32757+08  | 16393 | ledgernsp | usertable | a41714001181a294 | 6b5624e039e8aee36bff3e8295c75b40 | insert into ledge
+   rnsp.usertable values(1, 'alex'), (2, 'bob'), (3, 'peter');
+          1 | postgres | omm      | 2021-04-14 07:01:19.767799+08 | 16393 | ledgernsp | usertable | b3a9ed0755131181 | 328b48c4370faed930937869783c23e0 | update ledgernsp.
+   usertable set name = 'bob2' where id = 2;
+          2 | postgres | omm      | 2021-04-14 07:01:29.896148+08 | 16393 | ledgernsp | usertable | 0ae4b4e4ed2fcab5 | aa8f0a236357cac4e5bc1648a739f2ef | delete from ledge
+   rnsp.usertable where id = 3;
+   ```
+
+   The query result indicates that user **omm** has consecutively executed three DML commands, including **INSERT**, **UPDATE**, and **DELETE**.
+
+4. View records in the user history table.
+
+   ```sql
+   mogdb=# SELECT * FROM blockchain.ledgernsp_usertable_hist;
+    rec_num |     hash_ins     |     hash_del     |             pre_hash
+   ---------+------------------+------------------+----------------------------------
+         0 | 1f2e543c580cb8c5 |                  | e1b664970d925d09caa295abd38d9b35
+         1 | 8fcd74a8a6a4b484 |                  | dad3ed8939a141bf3682043891776b67
+         2 | f51b4b1b12d0354b |                  | 53eb887fc7c4302402343c8914e43c69
+         3 | 437761affbb7c605 | 8fcd74a8a6a4b484 | c2868c5b49550801d0dbbbaa77a83a10
+         4 |                  | f51b4b1b12d0354b | 9c512619f6ffef38c098477933499fe3
+   (5 rows)
+   ```
+
+   The query result shows that user **omm** inserts three rows of data to the **ledgernsp.usertable** table, updates one row of data, deletes one row of data, and leaves two rows of data, and the hash values are **1f2e543c580cb8c5** and **437761affbb7c605**.
+
+5. Query user table data and hash verification columns.
+
+   ```sql
+   mogdb=# SELECT *, hash FROM ledgernsp.usertable;
+    id | name |       hash
+   ----+------+------------------
+    1 | alex | 1f2e543c580cb8c5
+    2 | bob2 | 437761affbb7c605
+   (2 rows)
+   ```
+
+   The query result indicates that the remaining two records in the user table are the same as those in step 4.
+
+## Checking Ledger Data Consistency
+
+### Prerequisites
+
+The database is running properly, and a series of addition, deletion, and modification operations are performed on the tamper-proof database to ensure that operation records are generated in the ledger for query.
+
+### Background
+
+- Currently, the ledger database provides two verification interfaces: [ledger_hist_check(text, text)](20.1-ledger-database-functions) and [ledger_gchain_check(text, text)](20.1-ledger-database-functions). When a common user invokes a verification interface, only the tables that the user has the permission to access can be verified.
+
+- The interface for verifying the tamper-proof user table and user history table is **pg_catalog.ledger_hist_check**. To verify a table, run the following command:
+
+  ```sql
+  SELECT pg_catalog.ledger_hist_check(schema_name text,table_name text);
+  ```
+
+  If the verification is successful, the function returns **t**. Otherwise, the function returns **f**.
+
+- The **pg_catalog.ledger_gchain_check** interface is used to check whether the tamper-proof user table, user history table, and global blockchain table are consistent. To verify consistency, run the following command:
+
+  ```sql
+  SELECT pg_catalog.ledger_gchain_check(schema_name text, table_name text);
+  ```
+
+  If the verification is successful, the function returns **t**. Otherwise, the function returns **f**.
+
+### Procedure
+
+1. Check whether the tamper-proof user table **ledgernsp.usertable** is consistent with the corresponding user history table.
+
+   ```sql
+   mogdb=# SELECT pg_catalog.ledger_hist_check('ledgernsp', 'usertable');
+    ledger_hist_check
+   -------------------
+   t
+   (1 row)
+   ```
+
+   The query result shows that the results recorded in the tamper-proof user table and user history table are consistent.
+
+2. Check whether the records in the tamper-proof **ledgernsp.usertable** table are the same as those in the corresponding user history table and global blockchain table.
+
+   ```sql
+   mogdb=#  SELECT pg_catalog.ledger_gchain_check('ledgernsp', 'usertable');
+    ledger_gchain_check
+   ---------------------
+   t
+   (1 row)
+   ```
+
+   The query result shows that the records of **ledgernsp.usertable** in the preceding three tables are consistent and no tampering occurs.
+
+## Archiving a Ledger Database
+
+### Prerequisites
+
+- You are an audit administrator or a role that has the audit administrator permissions.
+- The database is running properly, and a series of addition, deletion, and modification operations are performed on the tamper-proof database to ensure that operation records are generated in the ledger for query.
+- The storage path **audit_directory** of audit files has been correctly configured in the database.
+
+### Context
+
+- Currently, the ledger database provides two archiving interfaces: [ledger_hist_archive(text, text)](20.1-ledger-database-functions) and [ledger_gchain_archive(void)](20.1-ledger-database-functions). Only the audit administrator can invoke the ledger database interfaces.
+
+- The interface for archiving the user history table is **pg_catalog.ledger_hist_archive**. To archive the table, run the following command:
+
+  ```sql
+  SELECT pg_catalog.ledger_hist_archive(schema_name text,table_name text);
+  ```
+
+  If the archiving is successful, the function returns **t**. Otherwise, the function returns **f**.
+
+- The interface for archiving the global blockchain table is **pg_catalog.ledger_gchain_archive**. To archive the table, run the following command:
+
+  ```sql
+  SELECT pg_catalog.ledger_gchain_archive();
+  ```
+
+  If the archiving is successful, the function returns **t**. Otherwise, the function returns **f**.
+
+### Procedure
+
+1. Archive a specified user history table.
+
+   ```sql
+   mogdb=# SELECT pg_catalog.ledger_hist_archive('ledgernsp', 'usertable')
+    ledger_hist_archive
+   ---------------------
+   t
+   (1 row)
+   ```
+
+   The user history table is archived as a record:
+
+   ```sql
+   mogdb=# SELECT * FROM blockchain.ledgernsp_usertable_hist;
+    rec_num |     hash_ins     |     hash_del     |             pre_hash
+   ---------+------------------+------------------+----------------------------------
+          3 | e78e75b00d396899 | 8fcd74a8a6a4b484 | fd61cb772033da297d10c4e658e898d7
+   (1 row)
+   ```
+
+   The command output indicates that the user history table of the current node is exported successfully.
+
+2. Export the global blockchain table.
+
+   ```sql
+   mogdb=# SELECT pg_catalog.ledger_gchain_archive();
+    ledger_gchain_archive
+   -----------------------
+   t
+   (1 row)
+   ```
+
+   The global history table will be archived to *n* (number of user tables) data records by user table:
+
+   ```sql
+   mogdb=# SELECT * FROM gs_global_chain;
+    blocknum |  dbname  | username |           starttime           | relid |  relnsp   |  relname  |     relhash      |            globalhash            | txcommand
+   ----------+----------+----------+-------------------------------+-------+-----------+-----------+------------------+----------------------------------+-----------
+           1 | postgres | libc     | 2021-05-10 19:59:38.619472+08 | 16388 | ledgernsp | usertable | 57c101076694b415 | be82f98ee68b2bc4e375f69209345406 | Archived.
+   (1 row)
+   ```
+
+   The command output indicates that the global blockchain table of the current node is successfully exported.
+
+## Repairing a Ledger Database
+
+### Prerequisites
+
+- You are an audit administrator or a role that has the audit administrator permissions.
+- The database is running properly, and a series of addition, deletion, and modification operations are performed on the tamper-proof database to ensure that operation records are generated in the ledger for query.
+
+### Context
+
+- When an exception occurs or a global blockchain table or user history table is damaged, you can use the ledger_gchain_repair(text, text) or ledger_hist_repair(text, text) interface to repair the table. After the fault is rectified, the result of invoking the global blockchain table or user history table verification interface is **true**.
+
+- The interface for repairing a user history table is **pg_catalog.ledger_hist_repair**. To repair the table, run the following command:
+
+  ```sql
+  SELECT pg_catalog.ledger_hist_repair(schema_name text,table_name text);
+  ```
+
+  If the repair is successful, the function returns the hash increment of the user history table during the repair.
+
+- The interface for repairing the global blockchain table is **pg_catalog.ledger_gchain_repair**. To repair the table, run the following command:
+
+  ```sql
+  SELECT pg_catalog.ledger_gchain_repair(schema_name text,table_name text);
+  ```
+
+  If the repair is successful, the function returns the hash increment of the global blockchain table during the repair.
+
+### Procedure
+
+1. Repair a specified user history table.
+
+   ```sql
+   mogdb=# SELECT pg_catalog.ledger_hist_repair('ledgernsp', 'usertable');
+    ledger_hist_repair
+   --------------------
+   84e8bfc3b974e9cf
+   (1 row)
+   ```
+
+   The query result indicates that the user history table on the current node is successfully repaired. The hash increment of the user history table is **84e8bfc3b974e9cf**.
+
+2. Repair a specified global blockchain table.
+
+   ```sql
+   mogdb=# SELECT pg_catalog.ledger_gchain_repair('ledgernsp', 'usertable');
+    ledger_gchain_repair
+   ----------------------
+   a41714001181a294
+   (1 row)
+   ```
+
+   The query result indicates that the global blockchain table is successfully repaired and a piece of repair data is inserted. The hash value is **a41714001181a294**.
diff --git a/product/en/docs-mogdb/v3.0/source-code-parsing.md b/product/en/docs-mogdb/v3.0/source-code-parsing.md
new file mode 100644
index 0000000000000000000000000000000000000000..634eeb4c852698d95c2e657b4050341b66bfea23
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/source-code-parsing.md
@@ -0,0 +1,88 @@
+---
+title: Source Code Parsing
+summary: Source Code Parsing
+author: Guo Huan
+date: 2022-02-07
+---
+
+# Source Code Parsing
+
+This series of articles parses the source code of the openGauss database module by module. It can be used as a reference tutorial for kernel developers to understand the openGauss database and develop database based on openGauss.
+
+You can click the links below to view this series of articles.
+
+## Introduction to openGauss
+
+[Introduction to openGauss (Part 1)](https://www.modb.pro/db/47895)
+
+[Introduction to openGauss (Part 2)](https://www.modb.pro/db/48291)
+
+## Quick Start to openGauss Development
+
+[Quick Start to openGauss Development (Part 1)](https://www.modb.pro/db/48657)
+
+[Quick Start to openGauss Development (Part 2)](https://www.modb.pro/db/48870)
+
+[Quick Start to openGauss Development (Part 3)](https://www.modb.pro/db/49118)
+
+## Parsing of Public Component Source Code
+
+[Parsing of public component source code (Part 1)](https://www.modb.pro/db/49242)
+
+[Parsing of public component source code (Part 2)](https://www.modb.pro/db/49711)
+
+## Parsing of Storage Engine Source Code
+
+[Parsing of storage engine source code (Part 1)](https://www.modb.pro/db/51541)
+
+[Parsing of storage engine source code (Part 2)](https://www.modb.pro/db/53926)
+
+[Parsing of storage engine source code (Part 3)](https://www.modb.pro/db/57991)
+
+[Parsing of storage engine source code (Part 4)](https://www.modb.pro/db/64255)
+
+[Parsing of storage engine source code (Part 5)](https://www.modb.pro/db/77848)
+
+## Parsing of Transaction Mechanism Source Code
+
+[Parsing of transaction mechanism source code (Part 1)](https://www.modb.pro/db/78553)
+
+[Parsing of transaction mechanism source code (Part 2)](https://www.modb.pro/db/79534)
+
+[Parsing of transaction mechanism source code (Part 3)](https://www.modb.pro/db/81991)
+
+## Parsing of SQL Engine Source Code
+
+[Parsing of SQL engine source code (Part 1)](https://www.modb.pro/db/86068)
+
+[Parsing of SQL engine source code (Part 2)](https://www.modb.pro/db/100257)
+
+## Executor Parsing
+
+[Executor Parsing (Part 1)](https://www.modb.pro/db/103591)
+
+[Executor Parsing (Part 2)](https://www.modb.pro/db/106997)
+
+[Executor Parsing (Part 3)](https://www.modb.pro/db/111770)
+
+## AI Technology
+
+[AI Technology (Part 1): Self-tuning](https://www.modb.pro/db/162007)
+
+[AI Technology (Part 2): Slow SQL discovery](https://www.modb.pro/db/171668)
+
+[AI Technology (Part 3): Index Recommendation](https://www.modb.pro/db/210235)
+
+[AI Technology (Part 4): Metrics Collection, Prediction, and Anomaly Detection](https://www.modb.pro/db/245341)
+
+[AI Technology (Part 5): AI Query Time Prediction](https://www.modb.pro/db/251405)
+
+[AI Technology (Part 6): DeepSQL](https://www.modb.pro/db/329691)
+
+## Parsing of Security Management Source Code
+
+[Parsing of Security Management Source Code (Part 1)](https://www.modb.pro/db/335331)
+
+[Parsing of Security Management Source Code (Part 2)](https://www.modb.pro/db/337160)
+
+[Parsing of Security Management Source Code (Part 3)](https://www.modb.pro/db/378249)
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/toc.md b/product/en/docs-mogdb/v3.0/toc.md
new file mode 100644
index 0000000000000000000000000000000000000000..cf0d4f6c3ff0f4949004d565e0f9558216904e15
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/toc.md
@@ -0,0 +1,1414 @@
+<!-- markdownlint-disable MD007 -->
+<!-- markdownlint-disable MD041 -->
+# MogDB Documentation 3.0
+
+## Documentation List
+
++ About MogDB
+  + [MogDB Introduction](/overview.md)
+  + [Comparison Between MogDB and openGauss](/about-mogdb/MogDB-compared-to-openGauss.md)
+  + [MogDB Release Notes](/about-mogdb/mogdb-release-notes.md)
+  + High Availability and Performance
+    + [HA Test](/about-mogdb/test-report/ha/MogDB-ha-test-report.md)
+    + Performance Test
+      + [Performance Test Overview](/about-mogdb/test-report/performance/1-performance-test-overview.md)
+      + [Performance Test for MogDB on Kunpeng Servers](/about-mogdb/test-report/performance/2-mogdb-on-kunpeng-performance-test-report.md)
+      + [Performance Test for MogDB on x86 Servers](/about-mogdb/test-report/performance/3-mogdb-on-x86-performance-test-report.md)
+  + Open Source Components
+    + [Docker-based MogDB](/about-mogdb/open-source-components/2-docker-based-mogdb.md)
+    + [compat-tools](/about-mogdb/open-source-components/compat-tools.md)
+    + [mogdb-monitor](/about-mogdb/open-source-components/mogdb-monitor.md)
+    + [wal2json](/about-mogdb/open-source-components/5-wal2json-extention-for-mogdb&opengauss.md)
+    + [mog_filedump](/about-mogdb/open-source-components/mog_filedump.md)
+    + [mog_xlogdump](/about-mogdb/open-source-components/mog_xlogdump.md)
+  + [Usage Limitations](/about-mogdb/usage-limitations.md)
+  + [Terms of Use](/about-mogdb/terms-of-use.md)
++ Quick Start
+  + [MogDB Playground](/quick-start/mogdb-playground.md)
+  + [Container-based MogDB Installation](/quick-start/container-based-installation.md)
+  + [Installation on a Single Node](/quick-start/installation-on-a-single-node.md)
+  + MogDB Access
+    + Use CLI to Access MogDB
+      + [gsql](/quick-start/mogdb-access/use-cli-to-access-mogdb/gsql.md)
+      + [pgcli](/quick-start/mogdb-access/use-cli-to-access-mogdb/pgcli.md)
+    + Use GUI to Access MogDB
+      + [Data Studio](/quick-start/mogdb-access/use-gui-tools-to-access-mogdb/datastudio.md)
+      + [DBeaver](/quick-start/mogdb-access/use-gui-tools-to-access-mogdb/dbeaver.md)
+    + Use Middleware to Access MogDB
+      + [Use WebLogic to Configure MogDB Data Sources](/quick-start/mogdb-access/use-middleware-to-access-mogdb/weblogic-configures-mogdb(postgresql)-data-source-reference.md)
+      + [Use WebSphere to Configure MogDB Data Sources](/quick-start/mogdb-access/use-middleware-to-access-mogdb/websphere-configures-mogdb(postgresql)-data-source-reference.md)
+    + Use Programming Language to Access MogDB
+      + [Java](/quick-start/mogdb-access/use-programming-language-to-access-mogdb/java.md)
+      + [C/C++](/quick-start/mogdb-access/use-programming-language-to-access-mogdb/c-cpp.md)
+      + [Python](/quick-start/mogdb-access/use-programming-language-to-access-mogdb/python.md)
+      + [Go](/quick-start/mogdb-access/use-programming-language-to-access-mogdb/go.md)
+      + [Rust](/quick-start/mogdb-access/use-programming-language-to-access-mogdb/rust.md)
+      + [NodeJS](/quick-start/mogdb-access/use-programming-language-to-access-mogdb/nodejs.md)
+  + [Using Sample Dataset Mogila](/quick-start/mogila.md)
++ Installation Guide
+  + [Container Installation](/installation-guide/docker-installation/docker-installation.md)
+  + Simplified Installation Process
+    + [Preparing for Installation](/installation-guide/simplified-installation-process/1-installation-preparation.md)
+    + [Installation on a Single Node](/installation-guide/simplified-installation-process/2-installation-on-a-single-node.md)
+    + [Installation on Primary/Standby Nodes](/installation-guide/simplified-installation-process/3-installation-on-primary-standby-nodes.md)
+  + Standard Installation
+    + [Installation Overview](/installation-guide/standard-installation/1-installation-overview.md)
+    + Preparing for Installation
+      + [Environment Requirement](/installation-guide/standard-installation/2-environment-requirement.md)
+      + [Modifying OS Configuration](/installation-guide/standard-installation/3-modifying-os-configuration.md)
+    + [Installing MogDB](/installation-guide/standard-installation/4-installing-mogdb.md)
+    + [Verifying the Installation](/installation-guide/standard-installation/5-verifying-installation.md)
+    + [Recommended Parameter Settings](/installation-guide/standard-installation/7-recommended-parameter-settings.md)
+    + [Uninstalling MogDB](/installation-guide/standard-installation/6-uninstallation.md)
+  + [Manual Installation](/installation-guide/manual-installation.md)
++ Administrator Guide
+  + Routine Maintenance
+    + [Starting and Stopping MogDB](/administrator-guide/routine-maintenance/0-starting-and-stopping-mogdb.md)
+    + [Using the gsql Client for Connection](/administrator-guide/routine-maintenance/using-the-gsql-client-for-connection.md)
+    + [Routine Maintenance](/administrator-guide/routine-maintenance/1-routine-maintenance-check-items.md)
+    + [Checking OS Parameters](/administrator-guide/routine-maintenance/2-checking-os-parameters.md)
+    + [Checking MogDB Health Status](/administrator-guide/routine-maintenance/3-checking-mogdb-health-status.md)
+    + [Checking Database Performance](/administrator-guide/routine-maintenance/4-checking-database-performance.md)
+    + [Checking and Deleting Logs](/administrator-guide/routine-maintenance/5-checking-and-deleting-logs.md)
+    + [Checking Time Consistency](/administrator-guide/routine-maintenance/6-checking-time-consistency.md)
+    + [Checking The Number of Application Connections](/administrator-guide/routine-maintenance/7-checking-the-number-of-application-connections.md)
+    + [Routinely Maintaining Tables](/administrator-guide/routine-maintenance/8-routinely-maintaining-tables.md)
+    + [Routinely Recreating an Index](/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md)
+    + [Data Security Maintenance Suggestions](/administrator-guide/routine-maintenance/10-data-security-maintenance-suggestions.md)
+    + [Log Reference](/administrator-guide/routine-maintenance/11-log-reference.md)
+  + [Primary and Standby Management](/administrator-guide/primary-and-standby-management.md)
+  + MOT Engine
+    + Introducing MOT
+      + [MOT Introduction](/administrator-guide/mot-engine/1-introducing-mot/1-mot-introduction.md)
+      + [MOT Features and Benefits](/administrator-guide/mot-engine/1-introducing-mot/2-mot-features-and-benefits.md)
+      + [MOT Key Technologies](/administrator-guide/mot-engine/1-introducing-mot/3-mot-key-technologies.md)
+      + [MOT Usage Scenarios](/administrator-guide/mot-engine/1-introducing-mot/4-mot-usage-scenarios.md)
+      + [MOT Performance Benchmarks](/administrator-guide/mot-engine/1-introducing-mot/5-mot-performance-benchmarks.md)
+    + Using MOT
+      + [Using MOT Overview](/administrator-guide/mot-engine/2-using-mot/1-using-mot-overview.md)
+      + [MOT Preparation](/administrator-guide/mot-engine/2-using-mot/2-mot-preparation.md)
+      + [MOT Deployment](/administrator-guide/mot-engine/2-using-mot/3-mot-deployment.md)
+      + [MOT Usage](/administrator-guide/mot-engine/2-using-mot/4-mot-usage.md)
+      + [MOT Administration](/administrator-guide/mot-engine/2-using-mot/5-mot-administration.md)
+      + [MOT Sample TPC-C Benchmark](/administrator-guide/mot-engine/2-using-mot/6-mot-sample-tpcc-benchmark.md)
+    + Concepts of MOT
+      + [MOT Scale-up Architecture](/administrator-guide/mot-engine/3-concepts-of-mot/3-1.md)
+      + [MOT Concurrency Control Mechanism](/administrator-guide/mot-engine/3-concepts-of-mot/3-2.md)
+      + [Extended FDW and Other MogDB Features](/administrator-guide/mot-engine/3-concepts-of-mot/3-3.md)
+      + [NUMA Awareness Allocation and Affinity](/administrator-guide/mot-engine/3-concepts-of-mot/3-4.md)
+      + [MOT Indexes](/administrator-guide/mot-engine/3-concepts-of-mot/3-5.md)
+      + [MOT Durability Concepts](/administrator-guide/mot-engine/3-concepts-of-mot/3-6.md)
+      + [MOT Recovery Concepts](/administrator-guide/mot-engine/3-concepts-of-mot/3-7.md)
+      + [MOT Query Native Compilation (JIT)](/administrator-guide/mot-engine/3-concepts-of-mot/3-8.md)
+      + [Comparison - Disk vs. MOT](/administrator-guide/mot-engine/3-concepts-of-mot/3-9.md)
+    + Appendix
+      + [References](/administrator-guide/mot-engine/4-appendix/1-references.md)
+      + [Glossary](/administrator-guide/mot-engine/4-appendix/2-glossary.md)
+  + [Column-store Tables Management](/administrator-guide/column-store-tables-management.md)
+  + Backup and Restoration
+    + [Overview](/administrator-guide/br/1-1-br.md)
+    + [Physical Backup and Restoration](/administrator-guide/br/1-2-br.md)
+    + [Logical Backup and Restoration](/administrator-guide/br/1-3-br.md)
+    + [Flashback Restoration](/administrator-guide/br/1-4-br.md)
+  + Importing and Exporting Data
+    + Importing Data
+      + [Import Modes](/administrator-guide/importing-and-exporting-data/importing-data/1-import-modes.md)
+      + [Running the INSERT Statement to Insert Data](/administrator-guide/importing-and-exporting-data/importing-data/2-running-the-INSERT-statement-to-insert-data.md)
+      + [Running the COPY FROM STDIN Statement to Import Data](/administrator-guide/importing-and-exporting-data/importing-data/3-running-the-COPY-FROM-STDIN-statement-to-import-data.md)
+      + [Using a gsql Meta-Command to Import Data](/administrator-guide/importing-and-exporting-data/importing-data/4-using-a-gsql-meta-command-to-import-data.md)
+      + [Using gs_restore to Import Data](/administrator-guide/importing-and-exporting-data/importing-data/5-using-gs_restore-to-import-data.md)
+      + [Updating Data in a Table](/administrator-guide/importing-and-exporting-data/importing-data/6-updating-data-in-a-table.md)
+      + [Deep Copy](/administrator-guide/importing-and-exporting-data/importing-data/7-deep-copy.md)
+      + [ANALYZE Table](/administrator-guide/importing-and-exporting-data/importing-data/8-ANALYZE-table.md)
+      + [Doing VACUUM to a Table](/administrator-guide/importing-and-exporting-data/importing-data/9-doing-VACUUM-to-a-table.md)
+      + [Managing Concurrent Write Operations](/administrator-guide/importing-and-exporting-data/importing-data/10-managing-concurrent-write-operations.md)
+    + Exporting Data
+      + [Using gs_dump and gs_dumpall to Export Data Overview](/administrator-guide/importing-and-exporting-data/exporting-data/1-using-gs_dump-and-gs_dumpall-to-export-data-overview.md)
+      + [Exporting a Single Database](/administrator-guide/importing-and-exporting-data/exporting-data/2-exporting-a-single-database.md)
+      + [Exporting All Databases](/administrator-guide/importing-and-exporting-data/exporting-data/3-exporting-all-databases.md)
+      + [Data Export By a User Without Required Permissions](/administrator-guide/importing-and-exporting-data/exporting-data/4-data-export-by-a-user-without-required-permissions.md)
+  + [Upgrade Guide](/administrator-guide/upgrade-guide.md)
++ Common Faults and Identification
+  + [Common Fault Locating Methods](/common-faults-and-identification/common-fault-locating-methods.md)
+  + Common Fault Locating Cases
+    + Core Fault Locating
+      + [Core Dump Occurs due to Full Disk Space](/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/1-core-dump-occurs-due-to-full-disk-space.md)
+      + [Core Dump Occurs Due to Incorrect Settings of GUC Parameter log_directory](/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/2-core-dump-occurs-due-to-incorrect-settings-of-guc-parameter-log-directory.md)
+      + [Core Dump Occurs when RemoveIPC Is Enabled](/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/3-core-dump-occurs-when-removeipc-is-enabled.md)
+      + [Core Dump Occurs After Installation on x86](/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/4-core-dump-occurs-after-installation-on-x86.md)
+    + Permission/Session/Data Type Fault Location
+      + [Forcibly Terminating a Session](/common-faults-and-identification/common-fault-locating-cases/13-forcibly-terminating-a-session.md)
+      + [Different Data Is Displayed for the Same Table Queried By Multiple Users](/common-faults-and-identification/common-fault-locating-cases/19-different-data-is-displayed.md)
+      + [An Error Occurs During Integer Conversion](/common-faults-and-identification/common-fault-locating-cases/22-an-error-occurs-during-integer-conversion.md)
+    + Service/High Availability/Concurrency Fault Location
+      + [Standby Node in the Need Repair (WAL) State](/common-faults-and-identification/common-fault-locating-cases/3-standby-node-in-the-need-repair-state.md)
+      + [Service Startup Failure](/common-faults-and-identification/common-fault-locating-cases/5-service-startup-failure.md)
+      + [Primary Node Is Hung in Demoting During a Switchover](/common-faults-and-identification/common-fault-locating-cases/9-primary-node-is-hung-in-demoting.md)
+      + ["too many clients already" Is Reported or Threads Failed To Be Created in High Concurrency Scenarios](/common-faults-and-identification/common-fault-locating-cases/23-too-many-clients-already.md)
+    + Table/Partition Table Fault Location
+      + [Table Size Does not Change After VACUUM FULL Is Executed on the Table](/common-faults-and-identification/common-fault-locating-cases/17-table-size-does-not-change.md)
+      + [An Error Is Reported When the Table Partition Is Modified](/common-faults-and-identification/common-fault-locating-cases/18-an-error-is-reported-when-the-table-partition-is-modified.md)
+    + File System/Disk/Memory Fault Location
+      + [After You Run the du Command to Query Data File Size In the XFS File System, the Query Result Is Greater than the Actual File Size](/common-faults-and-identification/common-fault-locating-cases/7-after-you-run-the-du-command.md)
+      + [File Is Damaged in the XFS File System](/common-faults-and-identification/common-fault-locating-cases/8-file-is-damaged-in-the-xfs-file-system.md)
+      + [Insufficient Memory](/common-faults-and-identification/common-fault-locating-cases/4-insufficient-memory.md)
+      + ["Error:No space left on device" Is Displayed](/common-faults-and-identification/common-fault-locating-cases/6-error-no-space-left-on-device-is-displayed.md)
+      + [When the TPC-C is running and a disk to be injected is full, the TPC-C stops responding](/common-faults-and-identification/common-fault-locating-cases/2-when-the-tpcc-is-running.md)
+      + [Disk Space Usage Reaches the Threshold and the Database Becomes Read-only](/common-faults-and-identification/common-fault-locating-cases/10-disk-space-usage-reaches-the-threshold.md)
+    + SQL Fault Location
+      + ["Lock wait timeout" Is Displayed When a User Executes an SQL Statement](/common-faults-and-identification/common-fault-locating-cases/16-lock-wait-timeout-is-displayed.md)
+      + [Analyzing Whether a Query Statement Is Blocked](/common-faults-and-identification/common-fault-locating-cases/14-analyzing-whether-a-query-statement-is-blocked.md)
+      + [Low Query Efficiency](/common-faults-and-identification/common-fault-locating-cases/15-low-query-efficiency.md)
+      + [Slow Response to a Query Statement](/common-faults-and-identification/common-fault-locating-cases/11-slow-response-to-a-query-statement.md)
+      + [Analyzing the Status of a Query Statement](/common-faults-and-identification/common-fault-locating-cases/12-analyzing-the-status-of-a-query-statement.md)
+    + Index Fault Location
+      + [When a User Specifies Only an Index Name to Modify the Index, A Message Indicating That the Index Does Not Exist Is Displayed](/common-faults-and-identification/common-fault-locating-cases/20-when-a-user-specifies-only-an-index-name.md)
+      + [Reindexing Fails](/common-faults-and-identification/common-fault-locating-cases/21-reindexing-fails.md)
+      + [B-tree Index Faults](/common-faults-and-identification/common-fault-locating-cases/24-b-tree-index-faults.md)
++ Security Guide
+  + Database Security Management
+    + [Client Access Authentication](security-guide/security/1-client-access-authentication.md)
+    + [Managing Users and Their Permissions](security-guide/security/2-managing-users-and-their-permissions.md)
+    + [Configuring Database Audit](security-guide/security/3-configuring-database-audit.md)
+    + [Setting Encrypted Equality Query](/security-guide/security/4-setting-encrypted-equality-query.md)
+    + [Setting a Ledger Database](/security-guide/security/5-setting-a-ledger-database.md)
++ Performance Tuning
+  + System Optimization
+    + [Optimizing OS Parameters](/performance-tuning/1-system/1-optimizing-os-parameters.md)
+    + [Optimizing Database Parameters](/performance-tuning/1-system/2-optimizing-database-parameters.md)
+    + [Configuring SMP](/performance-tuning/1-system/4-configuring-smp.md)
+    + [Configuring LLVM](/performance-tuning/1-system/3-configuring-llvm.md)
+  + SQL Optimization
+    + [Query Execution Process](/performance-tuning/2-sql/1-query-execution-process.md)
+    + [Introduction to the SQL Execution Plan](/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md)
+    + [Tuning Process](/performance-tuning/2-sql/3-tuning-process.md)
+    + [Updating Statistics](/performance-tuning/2-sql/4-updating-statistics.md)
+    + [Reviewing and Modifying a Table Definition](/performance-tuning/2-sql/5-reviewing-and-modifying-a-table-definition.md)
+    + [Typical SQL Optimization Methods](/performance-tuning/2-sql/6-typical-sql-optimization-methods.md)
+    + [Experience in Rewriting SQL Statements](/performance-tuning/2-sql/7-experience-in-rewriting-sql-statements.md)
+    + [Resetting Key Parameters During SQL Tuning](/performance-tuning/2-sql/8-resetting-key-parameters-during-sql-tuning.md)
+    + [Hint-based Tuning](/performance-tuning/2-sql/9-hint-based-tuning.md)
+  + [WDR Snapshot Schema](/performance-tuning/wdr-snapshot-schema.md)
+  + [TPCC Performance Tuning Guide](/performance-tuning/TPCC-performance-tuning-guide.md)
++ Developer Guide
+  + Development and Design Proposal
+    + [Overview](/developer-guide/development-and-design-proposal/overview-of-development-and-design-proposal.md)
+    + [Database Object Naming Conventions](/developer-guide/development-and-design-proposal/database-object-naming-conventions.md)
+    + Database Object Design
+      + [Database and Schema Design](/developer-guide/development-and-design-proposal/database-object-design/database-and-schema-design.md)
+      + [Table Design](/developer-guide/development-and-design-proposal/database-object-design/table-design.md)
+      + [Field Design](/developer-guide/development-and-design-proposal/database-object-design/field-design.md)
+      + [Constraint Design](/developer-guide/development-and-design-proposal/database-object-design/constraint-design.md)
+      + [View and Joined Table Design](/developer-guide/development-and-design-proposal/database-object-design/view-and-joined-table-design.md)
+    + Tool Interconnection
+      + [JDBC Configuration](/developer-guide/development-and-design-proposal/tool-interconnection/jdbc-configuration.md)
+    + [SQL Compilation](/developer-guide/development-and-design-proposal/sql-compilation.md)
+  + Application Development Guide
+    + [Development Specifications](/developer-guide/dev/1-development-specifications.md)
+    + Development Based on JDBC
+      + [Overview](/developer-guide/dev/2-development-based-on-jdbc/1-development-based-on-jdbc-overview.md)
+      + [JDBC Package, Driver Class, and Environment Class](/developer-guide/dev/2-development-based-on-jdbc/2-jdbc-package-driver-class-and-environment-class.md)
+      + [Development Process](/developer-guide/dev/2-development-based-on-jdbc/3-development-process.md)
+      + [Loading the Driver](/developer-guide/dev/2-development-based-on-jdbc/4-loading-the-driver.md)
+      + [Connecting to a Database](/developer-guide/dev/2-development-based-on-jdbc/5-connecting-to-a-database.md)
+      + [Connecting to the Database (Using SSL)](/developer-guide/dev/2-development-based-on-jdbc/6-connecting-to-a-database-using-ssl.md)
+      + [Running SQL Statements](/developer-guide/dev/2-development-based-on-jdbc/7-running-sql-statements.md)
+      + [Processing Data in a Result Set](/developer-guide/dev/2-development-based-on-jdbc/8-processing-data-in-a-result-set.md)
+      + [Closing a Connection](/developer-guide/dev/2-development-based-on-jdbc/9-closing-a-connection.md)
+      + [Managing Logs](/developer-guide/dev/2-development-based-on-jdbc/8.1-log-management.md)
+      + [Example: Common Operations](/developer-guide/dev/2-development-based-on-jdbc/10-example-common-operations.md)
+      + [Example: Retrying SQL Queries for Applications](/developer-guide/dev/2-development-based-on-jdbc/11-example-retrying-sql-queries-for-applications.md)
+      + [Example: Importing and Exporting Data Through Local Files](/developer-guide/dev/2-development-based-on-jdbc/12-example-importing-and-exporting-data-through-local-files.md)
+      + [Example 2: Migrating Data from a MY Database to MogDB](/developer-guide/dev/2-development-based-on-jdbc/13-example-2-migrating-data-from-a-my-database-to-mogdb.md)
+      + [Example: Logic Replication Code](/developer-guide/dev/2-development-based-on-jdbc/14-example-logic-replication-code.md)
+      + [Example: Parameters for Connecting to the Database in Different Scenarios](/developer-guide/dev/2-development-based-on-jdbc/14.1-example-parameters-for-connecting-to-the-database-in-different-scenarios.md)
+      + JDBC API Reference
+        + [java.sql.Connection](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/1-java-sql-Connection.md)
+        + [java.sql.CallableStatement](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/2-java-sql-CallableStatement.md)
+        + [java.sql.DatabaseMetaData](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/3-java-sql-DatabaseMetaData.md)
+        + [java.sql.Driver](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/4-java-sql-Driver.md)
+        + [java.sql.PreparedStatement](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/5-java-sql-PreparedStatement.md)
+        + [java.sql.ResultSet](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/6-java-sql-ResultSet.md)
+        + [java.sql.ResultSetMetaData](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/7-java-sql-ResultSetMetaData.md)
+        + [java.sql.Statement](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/8-java-sql-Statement.md)
+        + [javax.sql.ConnectionPoolDataSource](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/9-javax-sql-ConnectionPoolDataSource.md)
+        + [javax.sql.DataSource](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/10-javax-sql-DataSource.md)
+        + [javax.sql.PooledConnection](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/11-javax-sql-PooledConnection.md)
+        + [javax.naming.Context](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/12-javax-naming-Context.md)
+        + [javax.naming.spi.InitialContextFactory](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/13-javax-naming-spi-InitialContextFactory.md)
+        + [CopyManager](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/14-CopyManager.md)
+    + Development Based on ODBC
+      + [Overview](/developer-guide/dev/3-development-based-on-odbc/1-development-based-on-odbc-overview.md)
+      + [ODBC Packages, Dependent Libraries, and Header Files](/developer-guide/dev/3-development-based-on-odbc/2-odbc-packages-dependent-libraries-and-header-files.md)
+      + [Configuring a Data Source in the Linux OS](/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md)
+      + [Development Process](/developer-guide/dev/3-development-based-on-odbc/4-development-process.md)
+      + [Example: Common Functions and Batch Binding](/developer-guide/dev/3-development-based-on-odbc/5-example-common-functions-and-batch-binding.md)
+      + [Typical Application Scenarios and Configurations](/developer-guide/dev/3-development-based-on-odbc/5.1-typical-application-scenarios-and-configurations.md)
+      + ODBC API Reference
+        + [Overview](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-0-odbc-overview.md)
+        + [SQLAllocEnv](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-1-SQLAllocEnv.md)
+        + [SQLAllocConnect](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-2-SQLAllocConnect.md)
+        + [SQLAllocHandle](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-3-SQLAllocHandle.md)
+        + [SQLAllocStmt](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-4-SQLAllocStmt.md)
+        + [SQLBindCol](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-5-SQLBindCol.md)
+        + [SQLBindParameter](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-6-SQLBindParameter.md)
+        + [SQLColAttribute](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-7-SQLColAttribute.md)
+        + [SQLConnect](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-8-SQLConnect.md)
+        + [SQLDisconnect](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-9-SQLDisconnect.md)
+        + [SQLExecDirect](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-10-SQLExecDirect.md)
+        + [SQLExecute](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-11-SQLExecute.md)
+        + [SQLFetch](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-12-SQLFetch.md)
+        + [SQLFreeStmt](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-13-SQLFreeStmt.md)
+        + [SQLFreeConnect](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-14-SQLFreeConnect.md)
+        + [SQLFreeHandle](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-15-SQLFreeHandle.md)
+        + [SQLFreeEnv](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-16-SQLFreeEnv.md)
+        + [SQLPrepare](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-17-SQLPrepare.md)
+        + [SQLGetData](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-18-SQLGetData.md)
+        + [SQLGetDiagRec](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-19-SQLGetDiagRec.md)
+        + [SQLSetConnectAttr](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-20-SQLSetConnectAttr.md)
+        + [SQLSetEnvAttr](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-21-SQLSetEnvAttr.md)
+        + [SQLSetStmtAttr](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-22-SQLSetStmtAttr.md)
+        + [Examples](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-23-Examples.md)
+    + Development Based on libpq
+      + [Development Based on libpq](/developer-guide/dev/4-development-based-on-libpq/1-development-based-on-libpq.md)
+      + libpq API Reference
+        + Database Connection Control Functions
+          + [Description](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/1-database-connection-control-functions-overview.md)
+          + [PQconnectdbParams](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/2-PQconnectdbParams.md)
+          + [PQconnectdb](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/3-PQconnectdb.md)
+          + [PQconninfoParse](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/4-PQconninfoParse.md)
+          + [PQconnectStart](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/5-PQconnectStart.md)
+          + [PQerrorMessage](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/6-PQerrorMessage.md)
+          + [PQsetdbLogin](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/7-PQsetdbLogin.md)
+          + [PQfinish](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/8-PQfinish.md)
+          + [PQreset](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/9-PQreset.md)
+          + [PQstatus](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/10-PQstatus.md)
+        + Database Statement Execution Functions
+          + [PQclear](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/1-PQclear.md)
+          + [PQexec](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/2-PQexec.md)
+          + [PQexecParams](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/3-PQexecParams.md)
+          + [PQexecParamsBatch](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/4-PQexecParamsBatch.md)
+          + [PQexecPrepared](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/5-PQexecPrepared.md)
+          + [PQexecPreparedBatch](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/6-PQexecPreparedBatch.md)
+          + [PQfname](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/7-PQfname.md)
+          + [PQgetvalue](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/8-PQgetvalue.md)
+          + [PQnfields](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/9-PQnfields.md)
+          + [PQntuples](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/10-PQntuples.md)
+          + [PQprepare](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/11-PQprepare.md)
+          + [PQresultStatus](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/12-PQresultStatus.md)
+        + Functions for Asynchronous Command Processing
+          + [Description](/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/1-functions-for-asynchronous-command-processing-overview.md)
+          + [PQsendQuery](/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/2-PQsendQuery.md)
+          + [PQsendQueryParams](/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/3-PQsendQueryParams.md)
+          + [PQsendPrepare](/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/4-PQsendPrepare.md)
+          + [PQsendQueryPrepared](/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/5-PQsendQueryPrepared.md)
+          + [PQflush](/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/6-PQflush.md)
+        + Functions for Canceling Queries in Progress
+          + [PQgetCancel](/developer-guide/dev/4-development-based-on-libpq/2-libpq/4-functions-for-canceling-queries-in-progress/1-PQgetCancel.md)
+          + [PQfreeCancel](/developer-guide/dev/4-development-based-on-libpq/2-libpq/4-functions-for-canceling-queries-in-progress/2-PQfreeCancel.md)
+          + [PQcancel](/developer-guide/dev/4-development-based-on-libpq/2-libpq/4-functions-for-canceling-queries-in-progress/3-PQcancel.md)
+        + [Example](/developer-guide/dev/4-development-based-on-libpq/2-libpq/5-libpq-example.md)
+        + [Connection Characters](/developer-guide/dev/4-development-based-on-libpq/2-libpq/6-connection-characters.md)
+    + Psycopg-Based Development
+      + [Psycopg-Based Development](/developer-guide/dev/4.1-psycopg-based-development/1-psycopg-based-development.md)
+      + [Psycopg Package](/developer-guide/dev/4.1-psycopg-based-development/2-psycopg-package.md)
+      + [Development Process](/developer-guide/dev/4.1-psycopg-based-development/3.1-development-process.md)
+      + [Loading a Driver](/developer-guide/dev/4.1-psycopg-based-development/4-loading-a-driver.md)
+      + [Connecting to a Database](/developer-guide/dev/4.1-psycopg-based-development/5.1-connecting-to-a-database.md)
+      + [Executing SQL Statements](/developer-guide/dev/4.1-psycopg-based-development/6-executing-sql-statements.md)
+      + [Processing the Result Set](/developer-guide/dev/4.1-psycopg-based-development/7-processing-the-result-set.md)
+      + [Closing the Connection](/developer-guide/dev/4.1-psycopg-based-development/8-closing-the-connection.md)
+      + [Connecting to the Database (Using SSL)](/developer-guide/dev/4.1-psycopg-based-development/9-connecting-to-the-database-using-ssl.md)
+      + [Examples: Common Operations](/developer-guide/dev/4.1-psycopg-based-development/10.1-example-common-operations.md)
+      + Psycopg API Reference
+        + [psycopg2.connect()](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/1-psycopg2-connect.md)
+        + [connection.cursor()](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/2-connection-cursor.md)
+        + [cursor.execute(query,vars_list)](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/3-cursor-execute-query-vars-list.md)
+        + [curosr.executemany(query,vars_list)](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/4-curosr-executemany-query-vars-list.md)
+        + [connection.commit()](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/5-connection-commit.md)
+        + [connection.rollback()](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/6-connection-rollback.md)
+        + [cursor.fetchone()](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/7-cursor-fetchone.md)
+        + [cursor.fetchall()](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/8-cursor-fetchall.md)
+        + [cursor.close()](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/9-cursor-close.md)
+        + [connection.close()](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/10-connection-close.md)
+    + [Commissioning](/developer-guide/dev/5-commissioning.md)
+    + [Appendices](/developer-guide/dev/6-appendix.md)
+  + [Stored Procedure](/developer-guide/1-1-stored-procedure.md)
+  + [User Defined Functions](/developer-guide/user-defined-functions.md)
+  + PL/pgSQL-SQL Procedural Language
+    + [Overview of PL/pgSQL Functions](/developer-guide/plpgsql/1-1-plpgsql-overview.md)
+    + [Data Types](/developer-guide/plpgsql/1-2-data-types.md)
+    + [Data Type Conversion](/developer-guide/plpgsql/1-3-data-type-conversion.md)
+    + [Arrays and Records](/developer-guide/plpgsql/1-4-arrays-and-records.md)
+    + [DECLARE Syntax](/developer-guide/plpgsql/1-5-declare-syntax.md)
+    + [Basic Statements](/developer-guide/plpgsql/1-6-basic-statements.md)
+    + [Dynamic Statements](/developer-guide/plpgsql/1-7-dynamic-statements.md)
+    + [Control Statements](/developer-guide/plpgsql/1-8-control-statements.md)
+    + [Transaction Management](/developer-guide/plpgsql/1-9-transaction-management.md)
+    + [Other Statements](/developer-guide/plpgsql/1-10-other-statements.md)
+    + [Cursors](/developer-guide/plpgsql/1-11-cursors.md)
+    + [PKG_SERVICE API](/developer-guide/plpgsql/1-14-pkg-service.md)
+    + [Retry Management](/developer-guide/plpgsql/1-12-retry-management.md)
+    + [Debugging](/developer-guide/plpgsql/1-13-debugging.md)
+  + Scheduled Jobs
+    + [PKG_SERVICE API](/developer-guide/scheduled-jobs/pkg-service.md)
+  + Autonomous Transaction
+    + [Introduction](/developer-guide/autonomous-transaction/1-introduction-to-autonomous-transaction.md)
+    + [Stored Procedure Supporting Autonomous Transaction](/developer-guide/autonomous-transaction/3-stored-procedure-supporting-autonomous-transaction.md)
+    + [Anonymous Block Supporting Autonomous Transaction](/developer-guide/autonomous-transaction/anonymous-block-supporting-autonomous-transaction.md)
+    + [Function Supporting Autonomous Transaction](/developer-guide/autonomous-transaction/2-function-supporting-autonomous-transaction.md)
+    + [Restrictions](/developer-guide/autonomous-transaction/4-restrictions.md)
+  + Logical Replication
+    + Logical Decoding
+      + [Overview](/developer-guide/logical-replication/1-logical-decoding.md)
+      + [Logical Decoding by SQL Function Interfaces](/developer-guide/logical-replication/2-logical-decoding-by-sql-function-interfaces.md)
+  + Foreign Data Wrapper
+    + [Introduction](/developer-guide/foreign-data-wrapper/fdw-introduction.md)
+    + [oracle_fdw](/developer-guide/foreign-data-wrapper/1-oracle_fdw.md)
+    + [mysql_fdw](/developer-guide/foreign-data-wrapper/2-mysql_fdw.md)
+    + [postgres_fdw](/developer-guide/foreign-data-wrapper/3-postgres_fdw.md)
+    + [file_fdw](/developer-guide/foreign-data-wrapper/file_fdw.md)
+    + [dblink](/developer-guide/foreign-data-wrapper/dblink.md)
+  + Materialized View
+    + [Materialized View Overview](/developer-guide/materialized-view/1-materialized-view-overview.md)
+    + Full Materialized View
+      + [Overview](/developer-guide/materialized-view/2-full-materialized-view/1-full-materialized-view-overview.md)
+      + [Usage](/developer-guide/materialized-view/2-full-materialized-view/2-full-materialized-view-usage.md)
+      + [Support and Constraints](/developer-guide/materialized-view/2-full-materialized-view/3-full-materialized-view-support-and-constraints.md)
+    + Incremental Materialized View
+      + [Overview](/developer-guide/materialized-view/3-incremental-materialized-view/1-incremental-materialized-view-overview.md)
+      + [Usage](/developer-guide/materialized-view/3-incremental-materialized-view/2-incremental-materialized-view-usage.md)
+      + [Support and Constraints](/developer-guide/materialized-view/3-incremental-materialized-view/3-incremental-materialized-view-support-and-constraints.md)
+  + AI Features
+    + [Overview](/developer-guide/AI-features/1-AI-features-overview.md)
+    + Predictor: AI Query Time Forecasting
+      + [Overview](/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-1-ai-query-time-forecasting-overview.md)
+      + [Environment Deployment](/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-2-environment-deployment.md)
+      + [Usage Guide](/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-3-usage-guide.md)
+      + [Best Practices](/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-4-best-practices.md)
+      + [FAQs](/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-5-faqs.md)
+    + X-Tuner: Parameter Optimization and Diagnosis
+      + [Overview](/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-1-x-tuner-overview.md)
+      + [Preparations](/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-2-preparations.md)
+      + [Examples](/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-3-examples.md)
+      + [Obtaining Help Information](/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-4-obtaining-help-information.md)
+      + [Command Reference](/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-5-command-reference.md)
+      + [Troubleshooting](/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-6-Troubleshooting.md)
+    + SQLdiag: Slow SQL Discovery
+      + [Overview](/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-1-overview.md)
+      + [Usage Guide](/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-2-usage-guide.md)
+      + [Obtaining Help Information](/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-3-obtaining-help-information.md)
+      + [Command Reference](/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-4-command-reference.md)
+      + [Troubleshooting](/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-5-troubleshooting.md)
+    + A-Detection: Status Monitoring
+      + [Overview](/developer-guide/AI-features/5-a-detection-status-monitoring/5-1-overview.md)
+      + [Preparations](/developer-guide/AI-features/5-a-detection-status-monitoring/5-2-preparations.md)
+      + [Adding Monitoring Parameters](/developer-guide/AI-features/5-a-detection-status-monitoring/5-3-adding-monitoring-parameters.md)
+      + [Obtaining Help Information](/developer-guide/AI-features/5-a-detection-status-monitoring/5-4-obtaining-help-information.md)
+      + [Examples](/developer-guide/AI-features/5-a-detection-status-monitoring/5-6-examples.md)
+      + [Command Reference](/developer-guide/AI-features/5-a-detection-status-monitoring/5-5-command-reference.md)
+      + [AI_SERVER](/developer-guide/AI-features/5-a-detection-status-monitoring/5-7-ai-server.md)
+      + [AI_MANAGER](/developer-guide/AI-features/5-a-detection-status-monitoring/5-8-ai-manager.md)
+    + Index-advisor: Index Recommendation
+      + [Single-query Index Recommendation](/developer-guide/AI-features/6-index-advisor-index-recommendation/6-1-single-query-index-recommendation.md)
+      + [Virtual Index](/developer-guide/AI-features/6-index-advisor-index-recommendation/6-2-virtual-index.md)
+      + [Workload-level Index Recommendation](/developer-guide/AI-features/6-index-advisor-index-recommendation/6-3-workload-level-index-recommendation.md)
+    + DeepSQL
+      + [Overview](/developer-guide/AI-features/7-deepsql/7-1-overview.md)
+      + [Environment Deployment](/developer-guide/AI-features/7-deepsql/7-2-environment-deployment.md)
+      + [Usage Guide](/developer-guide/AI-features/7-deepsql/7-3-usage-guide.md)
+      + [Best Practices](/developer-guide/AI-features/7-deepsql/7-4-best-practices.md)
+      + [Troubleshooting](/developer-guide/AI-features/7-deepsql/7-5-troubleshooting.md)
+    + AI-Native Database (DB4AI)
+      + [Overview](/developer-guide/AI-features/8-db4ai/8-1-overview.md)
+      + [DB4AI-Snapshots for Data Version Management](/developer-guide/AI-features/8-db4ai/8-2-db4ai-snapshots-for-data-version-management.md)
+      + [DB4AI-Query for Model Training and Prediction](/developer-guide/AI-features/8-db4ai/8-3-db4ai-query-for-model-training-and-prediction.md)
+      + [PL/Python Fenced Mode](/developer-guide/AI-features/8-db4ai/8-4-pl-python-fenced-mode.md)
+  + Resource Load Management
+    + [Overview](/developer-guide/resource-load-management/resource-load-management-overview.md)
+    + Resource Management Preparation
+      + [Planning Resources](/developer-guide/resource-load-management/resource-management-preparation/planning-resources.md)
+      + [Enabling Resource Load Management](/developer-guide/resource-load-management/resource-management-preparation/enabling-resource-load-management.md)
+      + [Setting a Cgroup](/developer-guide/resource-load-management/resource-management-preparation/setting-a-cgroup.md)
+      + [Creating a Resource Pool](/developer-guide/resource-load-management/resource-management-preparation/creating-a-resource-pool.md)
++ Reference Guide
+  + System Catalogs and System Views
+    + [Overview of System Catalogs and System Views](/reference-guide/system-catalogs-and-system-views/overview-of-system-catalogs-and-system-views.md)
+    + System Catalogs
+      + [GS_AUDITING_POLICY](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY.md)
+      + [GS_AUDITING_POLICY_ACCESS](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY_ACCESS.md)
+      + [GS_AUDITING_POLICY_FILTERS](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY_FILTERS.md)
+      + [GS_AUDITING_POLICY_PRIVILEGES](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY_PRIVILEGES.md)
+      + [GS_CLIENT_GLOBAL_KEYS](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_CLIENT_GLOBAL_KEYS.md)
+      + [GS_CLIENT_GLOBAL_KEYS_ARGS](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_CLIENT_GLOBAL_KEYS_ARGS.md)
+      + [GS_COLUMN_KEYS](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_COLUMN_KEYS.md)
+      + [GS_COLUMN_KEYS_ARGS](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_COLUMN_KEYS_ARGS.md)
+      + [GS_ENCRYPTED_COLUMNS](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_ENCRYPTED_COLUMNS.md)
+      + [GS_ENCRYPTED_PROC](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_ENCRYPTED_PROC.md)
+      + [GS_GLOBAL_CHAIN](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_GLOBAL_CHAIN.md)
+      + [GS_MASKING_POLICY](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MASKING_POLICY.md)
+      + [GS_MASKING_POLICY_ACTIONS](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MASKING_POLICY_ACTIONS.md)
+      + [GS_MASKING_POLICY_FILTERS](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MASKING_POLICY_FILTERS.md)
+      + [GS_MATVIEW](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MATVIEW.md)
+      + [GS_MATVIEW_DEPENDENCY](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MATVIEW_DEPENDENCY.md)
+      + [GS_OPT_MODEL](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_OPT_MODEL.md)
+      + [GS_POLICY_LABEL](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_POLICY_LABEL.md)
+      + [GS_RECYCLEBIN](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_RECYCLEBIN.md)
+      + [GS_TXN_SNAPSHOT](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_TXN_SNAPSHOT.md)
+      + [GS_WLM_INSTANCE_HISTORY](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_INSTANCE_HISTORY.md)
+      + [GS_WLM_OPERATOR_INFO](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_OPERATOR_INFO.md)
+      + [GS_WLM_PLAN_ENCODING_TABLE](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_PLAN_ENCODING_TABLE.md)
+      + [GS_WLM_PLAN_OPERATOR_INFO](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_PLAN_OPERATOR_INFO.md)
+      + [GS_WLM_EC_OPERATOR_INFO](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_EC_OPERATOR_INFO.md)
+      + [PG_AGGREGATE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AGGREGATE.md)
+      + [PG_AM](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AM.md)
+      + [PG_AMOP](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AMOP.md)
+      + [PG_AMPROC](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AMPROC.md)
+      + [PG_APP_WORKLOADGROUP_MAPPING](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_APP_WORKLOADGROUP_MAPPING.md)
+      + [PG_ATTRDEF](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_ATTRDEF.md)
+      + [PG_ATTRIBUTE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_ATTRIBUTE.md)
+      + [PG_AUTHID](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AUTHID.md)
+      + [PG_AUTH_HISTORY](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AUTH_HISTORY.md)
+      + [PG_AUTH_MEMBERS](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AUTH_MEMBERS.md)
+      + [PG_CAST](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CAST.md)
+      + [PG_CLASS](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CLASS.md)
+      + [PG_COLLATION](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_COLLATION.md)
+      + [PG_CONSTRAINT](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CONSTRAINT.md)
+      + [PG_CONVERSION](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CONVERSION.md)
+      + [PG_DATABASE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DATABASE.md)
+      + [PG_DB_ROLE_SETTING](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DB_ROLE_SETTING.md)
+      + [PG_DEFAULT_ACL](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DEFAULT_ACL.md)
+      + [PG_DEPEND](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DEPEND.md)
+      + [PG_DESCRIPTION](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DESCRIPTION.md)
+      + [PG_DIRECTORY](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DIRECTORY.md)
+      + [PG_ENUM](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_ENUM.md)
+      + [PG_EXTENSION](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_EXTENSION.md)
+      + [PG_EXTENSION_DATA_SOURCE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_EXTENSION_DATA_SOURCE.md)
+      + [PG_FOREIGN_DATA_WRAPPER](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_FOREIGN_DATA_WRAPPER.md)
+      + [PG_FOREIGN_SERVER](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_FOREIGN_SERVER.md)
+      + [PG_FOREIGN_TABLE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_FOREIGN_TABLE.md)
+      + [PG_INDEX](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_INDEX.md)
+      + [PG_INHERITS](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_INHERITS.md)
+      + [PG_JOB](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_JOB.md)
+      + [PG_JOB_PROC](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_JOB_PROC.md)
+      + [PG_LANGUAGE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_LANGUAGE.md)
+      + [PG_LARGEOBJECT](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_LARGEOBJECT.md)
+      + [PG_LARGEOBJECT_METADATA](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_LARGEOBJECT_METADATA.md)
+      + [PG_NAMESPACE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_NAMESPACE.md)
+      + [PG_OBJECT](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OBJECT.md)
+      + [PG_OPCLASS](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OPCLASS.md)
+      + [PG_OPERATOR](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OPERATOR.md)
+      + [PG_OPFAMILY](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OPFAMILY.md)
+      + [PG_PARTITION](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_PARTITION.md)
+      + [PG_PLTEMPLATE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_PLTEMPLATE.md)
+      + [PG_PROC](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_PROC.md)
+      + [PG_RANGE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_RANGE.md)
+      + [PG_RESOURCE_POOL](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_RESOURCE_POOL.md)
+      + [PG_REWRITE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_REWRITE.md)
+      + [PG_RLSPOLICY](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_RLSPOLICY.md)
+      + [PG_SECLABEL](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SECLABEL.md)
+      + [PG_SHDEPEND](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SHDEPEND.md)
+      + [PG_SHDESCRIPTION](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SHDESCRIPTION.md)
+      + [PG_SHSECLABEL](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SHSECLABEL.md)
+      + [PG_STATISTIC](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_STATISTIC.md)
+      + [PG_STATISTIC_EXT](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_STATISTIC_EXT.md)
+      + [PG_SYNONYM](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SYNONYM.md)
+      + [PG_TABLESPACE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TABLESPACE.md)
+      + [PG_TRIGGER](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TRIGGER.md)
+      + [PG_TS_CONFIG](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_CONFIG.md)
+      + [PG_TS_CONFIG_MAP](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_CONFIG_MAP.md)
+      + [PG_TS_DICT](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_DICT.md)
+      + [PG_TS_PARSER](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_PARSER.md)
+      + [PG_TS_TEMPLATE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_TEMPLATE.md)
+      + [PG_TYPE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TYPE.md)
+      + [PG_USER_MAPPING](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_USER_MAPPING.md)
+      + [PG_USER_STATUS](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_USER_STATUS.md)
+      + [PG_WORKLOAD_GROUP](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_WORKLOAD_GROUP.md)
+      + [PLAN_TABLE_DATA](/reference-guide/system-catalogs-and-system-views/system-catalogs/PLAN_TABLE_DATA.md)
+      + [STATEMENT_HISTORY](/reference-guide/system-catalogs-and-system-views/system-catalogs/STATEMENT_HISTORY.md)
+    + System Views
+      + [GET_GLOBAL_PREPARED_XACTS](/reference-guide/system-catalogs-and-system-views/system-views/GET_GLOBAL_PREPARED_XACTS.md)
+      + [GS_AUDITING](/reference-guide/system-catalogs-and-system-views/system-views/GS_AUDITING.md)
+      + [GS_AUDITING_ACCESS](/reference-guide/system-catalogs-and-system-views/system-views/GS_AUDITING_ACCESS.md)
+      + [GS_AUDITING_PRIVILEGE](/reference-guide/system-catalogs-and-system-views/system-views/GS_AUDITING_PRIVILEGE.md)
+      + [GS_CLUSTER_RESOURCE_INFO](/reference-guide/system-catalogs-and-system-views/system-views/GS_CLUSTER_RESOURCE_INFO.md)
+      + [GS_INSTANCE_TIME](/reference-guide/system-catalogs-and-system-views/system-views/GS_INSTANCE_TIME.md)
+      + [GS_LABELS](/reference-guide/system-catalogs-and-system-views/system-views/GS_LABELS.md)
+      + [GS_MASKING](/reference-guide/system-catalogs-and-system-views/system-views/GS_MASKING.md)
+      + [GS_MATVIEWS](/reference-guide/system-catalogs-and-system-views/system-views/GS_MATVIEWS.md)
+      + [GS_SESSION_MEMORY](/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY.md)
+      + [GS_SESSION_CPU_STATISTICS](/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_CPU_STATISTICS.md)
+      + [GS_SESSION_MEMORY_CONTEXT](/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY_CONTEXT.md)
+      + [GS_SESSION_MEMORY_DETAIL](/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY_DETAIL.md)
+      + [GS_SESSION_MEMORY_STATISTICS](/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY_STATISTICS.md)
+      + [GS_SQL_COUNT](/reference-guide/system-catalogs-and-system-views/system-views/GS_SQL_COUNT.md)
+      + [GS_WLM_CGROUP_INFO](/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_CGROUP_INFO.md)
+      + [GS_WLM_PLAN_OPERATOR_HISTORY](/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_PLAN_OPERATOR_HISTORY.md)
+      + [GS_WLM_REBUILD_USER_RESOURCE_POOL](/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_REBUILD_USER_RESOURCE_POOL.md)
+      + [GS_WLM_RESOURCE_POOL](/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_RESOURCE_POOL.md)
+      + [GS_WLM_USER_INFO](/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_USER_INFO.md)
+      + [GS_STAT_SESSION_CU](/reference-guide/system-catalogs-and-system-views/system-views/GS_STAT_SESSION_CU.md)
+      + [GS_TOTAL_MEMORY_DETAIL](/reference-guide/system-catalogs-and-system-views/system-views/GS_TOTAL_MEMORY_DETAIL.md)
+      + [MPP_TABLES](/reference-guide/system-catalogs-and-system-views/system-views/MPP_TABLES.md)
+      + [PG_AVAILABLE_EXTENSION_VERSIONS](/reference-guide/system-catalogs-and-system-views/system-views/PG_AVAILABLE_EXTENSION_VERSIONS.md)
+      + [PG_AVAILABLE_EXTENSIONS](/reference-guide/system-catalogs-and-system-views/system-views/PG_AVAILABLE_EXTENSIONS.md)
+      + [PG_COMM_DELAY](/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_DELAY.md)
+      + [PG_COMM_RECV_STREAM](/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_RECV_STREAM.md)
+      + [PG_COMM_SEND_STREAM](/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_SEND_STREAM.md)
+      + [PG_COMM_STATUS](/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_STATUS.md)
+      + [PG_CONTROL_GROUP_CONFIG](/reference-guide/system-catalogs-and-system-views/system-views/PG_CONTROL_GROUP_CONFIG.md)
+      + [PG_CURSORS](/reference-guide/system-catalogs-and-system-views/system-views/PG_CURSORS.md)
+      + [PG_EXT_STATS](/reference-guide/system-catalogs-and-system-views/system-views/PG_EXT_STATS.md)
+      + [PG_GET_INVALID_BACKENDS](/reference-guide/system-catalogs-and-system-views/system-views/PG_GET_INVALID_BACKENDS.md)
+      + [PG_GET_SENDERS_CATCHUP_TIME](/reference-guide/system-catalogs-and-system-views/system-views/PG_GET_SENDERS_CATCHUP_TIME.md)
+      + [PG_GROUP](/reference-guide/system-catalogs-and-system-views/system-views/PG_GROUP.md)
+      + [PG_GTT_RELSTATS](/reference-guide/system-catalogs-and-system-views/system-views/PG_GTT_RELSTATS.md)
+      + [PG_GTT_STATS](/reference-guide/system-catalogs-and-system-views/system-views/PG_GTT_STATS.md)
+      + [PG_GTT_ATTACHED_PIDS](/reference-guide/system-catalogs-and-system-views/system-views/PG_GTT_ATTACHED_PIDS.md)
+      + [PG_INDEXES](/reference-guide/system-catalogs-and-system-views/system-views/PG_INDEXES.md)
+      + [PG_LOCKS](/reference-guide/system-catalogs-and-system-views/system-views/PG_LOCKS.md)
+      + [PG_NODE_ENV](/reference-guide/system-catalogs-and-system-views/system-views/PG_NODE_ENV.md)
+      + [PG_OS_THREADS](/reference-guide/system-catalogs-and-system-views/system-views/PG_OS_THREADS.md)
+      + [PG_PREPARED_STATEMENTS](/reference-guide/system-catalogs-and-system-views/system-views/PG_PREPARED_STATEMENTS.md)
+      + [PG_PREPARED_XACTS](/reference-guide/system-catalogs-and-system-views/system-views/PG_PREPARED_XACTS.md)
+      + [PG_REPLICATION_SLOTS](/reference-guide/system-catalogs-and-system-views/system-views/PG_REPLICATION_SLOTS.md)
+      + [PG_RLSPOLICIES](/reference-guide/system-catalogs-and-system-views/system-views/PG_RLSPOLICIES.md)
+      + [PG_ROLES](/reference-guide/system-catalogs-and-system-views/system-views/PG_ROLES.md)
+      + [PG_RULES](/reference-guide/system-catalogs-and-system-views/system-views/PG_RULES.md)
+      + [PG_SECLABELS](/reference-guide/system-catalogs-and-system-views/system-views/PG_SECLABELS.md)
+      + [PG_SETTINGS](/reference-guide/system-catalogs-and-system-views/system-views/PG_SETTINGS.md)
+      + [PG_SHADOW](/reference-guide/system-catalogs-and-system-views/system-views/PG_SHADOW.md)
+      + [PG_STATS](/reference-guide/system-catalogs-and-system-views/system-views/PG_STATS.md)
+      + [PG_STAT_ACTIVITY](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_ACTIVITY.md)
+      + [PG_STAT_ALL_INDEXES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_ALL_INDEXES.md)
+      + [PG_STAT_ALL_TABLES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_ALL_TABLES.md)
+      + [PG_STAT_BAD_BLOCK](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_BAD_BLOCK.md)
+      + [PG_STAT_BGWRITER](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_BGWRITER.md)
+      + [PG_STAT_DATABASE](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_DATABASE.md)
+      + [PG_STAT_DATABASE_CONFLICTS](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_DATABASE_CONFLICTS.md)
+      + [PG_STAT_USER_FUNCTIONS](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_USER_FUNCTIONS.md)
+      + [PG_STAT_USER_INDEXES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_USER_INDEXES.md)
+      + [PG_STAT_USER_TABLES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_USER_TABLES.md)
+      + [PG_STAT_REPLICATION](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_REPLICATION.md)
+      + [PG_STAT_SYS_INDEXES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_SYS_INDEXES.md)
+      + [PG_STAT_SYS_TABLES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_SYS_TABLES.md)
+      + [PG_STAT_XACT_ALL_TABLES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_ALL_TABLES.md)
+      + [PG_STAT_XACT_SYS_TABLES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_SYS_TABLES.md)
+      + [PG_STAT_XACT_USER_FUNCTIONS](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_USER_FUNCTIONS.md)
+      + [PG_STAT_XACT_USER_TABLES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_USER_TABLES.md)
+      + [PG_STATIO_ALL_INDEXES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_ALL_INDEXES.md)
+      + [PG_STATIO_ALL_SEQUENCES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_ALL_SEQUENCES.md)
+      + [PG_STATIO_ALL_TABLES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_ALL_TABLES.md)
+      + [PG_STATIO_SYS_INDEXES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_SYS_INDEXES.md)
+      + [PG_STATIO_SYS_SEQUENCES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_SYS_SEQUENCES.md)
+      + [PG_STATIO_SYS_TABLES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_SYS_TABLES.md)
+      + [PG_STATIO_USER_INDEXES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_USER_INDEXES.md)
+      + [PG_STATIO_USER_SEQUENCES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_USER_SEQUENCES.md)
+      + [PG_STATIO_USER_TABLES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_USER_TABLES.md)
+      + [PG_TABLES](/reference-guide/system-catalogs-and-system-views/system-views/PG_TABLES.md)
+      + [PG_TDE_INFO](/reference-guide/system-catalogs-and-system-views/system-views/PG_TDE_INFO.md)
+      + [PG_THREAD_WAIT_STATUS](/reference-guide/system-catalogs-and-system-views/system-views/PG_THREAD_WAIT_STATUS.md)
+      + [PG_TIMEZONE_ABBREVS](/reference-guide/system-catalogs-and-system-views/system-views/PG_TIMEZONE_ABBREVS.md)
+      + [PG_TIMEZONE_NAMES](/reference-guide/system-catalogs-and-system-views/system-views/PG_TIMEZONE_NAMES.md)
+      + [PG_TOTAL_MEMORY_DETAIL](/reference-guide/system-catalogs-and-system-views/system-views/PG_TOTAL_MEMORY_DETAIL.md)
+      + [PG_TOTAL_USER_RESOURCE_INFO](/reference-guide/system-catalogs-and-system-views/system-views/PG_TOTAL_USER_RESOURCE_INFO.md)
+      + [PG_TOTAL_USER_RESOURCE_INFO_OID](/reference-guide/system-catalogs-and-system-views/system-views/PG_TOTAL_USER_RESOURCE_INFO_OID.md)
+      + [PG_USER](/reference-guide/system-catalogs-and-system-views/system-views/PG_USER.md)
+      + [PG_USER_MAPPINGS](/reference-guide/system-catalogs-and-system-views/system-views/PG_USER_MAPPINGS.md)
+      + [PG_VARIABLE_INFO](/reference-guide/system-catalogs-and-system-views/system-views/PG_VARIABLE_INFO.md)
+      + [PG_VIEWS](/reference-guide/system-catalogs-and-system-views/system-views/PG_VIEWS.md)
+      + [PLAN_TABLE](/reference-guide/system-catalogs-and-system-views/system-views/PLAN_TABLE.md)
+      + [GS_FILE_STAT](/reference-guide/system-catalogs-and-system-views/system-views/GS_FILE_STAT.md)
+      + [GS_OS_RUN_INFO](/reference-guide/system-catalogs-and-system-views/system-views/GS_OS_RUN_INFO.md)
+      + [GS_REDO_STAT](/reference-guide/system-catalogs-and-system-views/system-views/GS_REDO_STAT.md)
+      + [GS_SESSION_STAT](/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_STAT.md)
+      + [GS_SESSION_TIME](/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_TIME.md)
+      + [GS_THREAD_MEMORY_CONTEXT](/reference-guide/system-catalogs-and-system-views/system-views/GS_THREAD_MEMORY_CONTEXT.md)
+  + Functions and Operators
+    + [Logical Operators](/reference-guide/functions-and-operators/1-logical-operators.md)
+    + [Comparison Operators](/reference-guide/functions-and-operators/2-comparison-operators.md)
+    + [Character Processing Functions and Operators](/reference-guide/functions-and-operators/3-character-processing-functions-and-operators.md)
+    + [Binary String Functions and Operators](/reference-guide/functions-and-operators/4-binary-string-functions-and-operators.md)
+    + [Bit String Functions and Operators](/reference-guide/functions-and-operators/5-bit-string-functions-and-operators.md)
+    + [Mode Matching Operators](/reference-guide/functions-and-operators/6-mode-matching-operators.md)
+    + [Mathematical Functions and Operators](/reference-guide/functions-and-operators/7-mathematical-functions-and-operators.md)
+    + [Date and Time Processing Functions and Operators](/reference-guide/functions-and-operators/8-date-and-time-processing-functions-and-operators.md)
+    + [Type Conversion Functions](/reference-guide/functions-and-operators/9-type-conversion-functions.md)
+    + [Geometric Functions and Operators](/reference-guide/functions-and-operators/10-geometric-functions-and-operators.md)
+    + [Network Address Functions and Operators](/reference-guide/functions-and-operators/11-network-address-functions-and-operators.md)
+    + [Text Search Functions and Operators](/reference-guide/functions-and-operators/12-text-search-functions-and-operators.md)
+    + [JSON/JSONB Functions and Operators](/reference-guide/functions-and-operators/13-json-functions.md)
+    + [HLL Functions and Operators](/reference-guide/functions-and-operators/13.1-hll-functions-and-operators.md)
+    + [SEQUENCE Functions](/reference-guide/functions-and-operators/14-sequence-functions.md)
+    + [Array Functions and Operators](/reference-guide/functions-and-operators/15-array-functions-and-operators.md)
+    + [Range Functions and Operators](/reference-guide/functions-and-operators/16-range-functions-and-operators.md)
+    + [Aggregate Functions](/reference-guide/functions-and-operators/17-aggregate-functions.md)
+    + [Window Functions](/reference-guide/functions-and-operators/18-window-functions.md)
+    + [Security Functions](/reference-guide/functions-and-operators/19-security-functions.md)
+    + [Ledger Database Functions](/reference-guide/functions-and-operators/20.1-ledger-database-functions.md)
+    + [Encrypted Equality Functions](/reference-guide/functions-and-operators/20-encrypted-equality-functions.md)
+    + [Set Returning Functions](/reference-guide/functions-and-operators/21-set-returning-functions.md)
+    + [Conditional Expression Functions](/reference-guide/functions-and-operators/22-conditional-expressions-functions.md)
+    + [System Information Functions](/reference-guide/functions-and-operators/23-system-information-functions.md)
+    + System Administration Functions
+      + [Configuration Settings Functions](/reference-guide/functions-and-operators/24-system-management-functions/1-configuration-settings-functions.md)
+      + [Universal File Access Functions](/reference-guide/functions-and-operators/24-system-management-functions/2-universal-file-access-functions.md)
+      + [Server Signal Functions](/reference-guide/functions-and-operators/24-system-management-functions/3-server-signal-functions.md)
+      + [Backup and Restoration Control Functions](/reference-guide/functions-and-operators/24-system-management-functions/4-backup-and-restoration-control-functions.md)
+      + [Snapshot Synchronization Functions](/reference-guide/functions-and-operators/24-system-management-functions/5-snapshot-synchronization-functions.md)
+      + [Database Object Functions](/reference-guide/functions-and-operators/24-system-management-functions/6-database-object-functions.md)
+      + [Advisory Lock Functions](/reference-guide/functions-and-operators/24-system-management-functions/7-advisory-lock-functions.md)
+      + [Logical Replication Functions](/reference-guide/functions-and-operators/24-system-management-functions/8-logical-replication-functions.md)
+      + [Segment-Page Storage Functions](/reference-guide/functions-and-operators/24-system-management-functions/9.1-segment-page-storage-functions.md)
+      + [Other Functions](/reference-guide/functions-and-operators/24-system-management-functions/9-other-functions.md)
+      + [Undo System Functions](/reference-guide/functions-and-operators/24-system-management-functions/10-undo-system-functions.md)
+    + [Statistics Information Functions](/reference-guide/functions-and-operators/25-statistics-information-functions.md)
+    + [Trigger Functions](/reference-guide/functions-and-operators/26-trigger-functions.md)
+    + [Hash Function](/reference-guide/functions-and-operators/27.1-hash-function.md)
+    + [Prompt Message Function](/reference-guide/functions-and-operators/27.2-prompt-message-function.md)
+    + [Global Temporary Table Functions](/reference-guide/functions-and-operators/27-global-temporary-table-functions.md)
+    + [Fault Injection System Function](/reference-guide/functions-and-operators/28.1-fault-injection-system-function.md)
+    + [AI Feature Functions](/reference-guide/functions-and-operators/28-ai-feature-functions.md)
+    + [Dynamic Data Masking Functions](/reference-guide/functions-and-operators/29.1-dynamic-data-masking-functions.md)
+    + [Other System Functions](/reference-guide/functions-and-operators/29-other-system-functions.md)
+    + [Internal Functions](/reference-guide/functions-and-operators/30-internal-functions.md)
+    + [Obsolete Functions](/reference-guide/functions-and-operators/31-obsolete-functions.md)
+  + Supported Data Types
+    + [Numeric Types](/reference-guide/supported-data-types/1-numeric-data-types.md)
+    + [Monetary Types](/reference-guide/supported-data-types/2-monetary.md)
+    + [Boolean Types](/reference-guide/supported-data-types/3-boolean-data-types.md)
+    + [Enumerated Types](/reference-guide/supported-data-types/4.1-enumerated-types.md)
+    + [Character Types](/reference-guide/supported-data-types/4-character-data-types.md)
+    + [Binary Types](/reference-guide/supported-data-types/5-binary-data-types.md)
+    + [Date/Time Types](/reference-guide/supported-data-types/6-date-time-types.md)
+    + [Geometric](/reference-guide/supported-data-types/7-geometric.md)
+    + [Network Address Types](/reference-guide/supported-data-types/8-network-address.md)
+    + [Bit String Types](/reference-guide/supported-data-types/9-bit-string-types.md)
+    + [Text Search Types](/reference-guide/supported-data-types/10-text-search-types.md)
+    + [UUID](/reference-guide/supported-data-types/11-uuid-type.md)
+    + [JSON/JSONB Types](/reference-guide/supported-data-types/12-json-types.md)
+    + [HLL](/reference-guide/supported-data-types/13-HLL.md)
+    + [Array Types](/reference-guide/supported-data-types/13.0-array-types.md)
+    + [Range](/reference-guide/supported-data-types/13.1-range.md)
+    + [OID Types](/reference-guide/supported-data-types/14-object-identifier-types.md)
+    + [Pseudo-Types](/reference-guide/supported-data-types/15-pseudo-types.md)
+    + [Data Types Supported by Column-store Tables](/reference-guide/supported-data-types/16-data-types-supported-by-column-store-tables.md)
+    + [XML Types](/reference-guide/supported-data-types/17-xml-type.md)
+    + [Data Type Used by the Ledger Database](/reference-guide/supported-data-types/18-data-type-used-by-the-ledger-database.md)
+  + SQL Syntax
+    + [ABORT](/reference-guide/sql-syntax/1-ABORT.md)
+    + [ALTER AGGREGATE](/reference-guide/sql-syntax/1.1-ALTER-AGGREGATE.md)
+    + [ALTER AUDIT POLICY](/reference-guide/sql-syntax/1.2-ALTER-AUDIT-POLICY.md)
+    + [ALTER DATABASE](/reference-guide/sql-syntax/2-ALTER-DATABASE.md)
+    + [ALTER DATA SOURCE](/reference-guide/sql-syntax/3-ALTER-DATA-SOURCE.md)
+    + [ALTER DEFAULT PRIVILEGES](/reference-guide/sql-syntax/4-ALTER-DEFAULT-PRIVILEGES.md)
+    + [ALTER DIRECTORY](/reference-guide/sql-syntax/5-ALTER-DIRECTORY.md)
+    + [ALTER EXTENSION](/reference-guide/sql-syntax/5.1-ALTER-EXTENSION.md)
+    + [ALTER FOREIGN TABLE](/reference-guide/sql-syntax/6-ALTER-FOREIGN-TABLE.md)
+    + [ALTER FUNCTION](/reference-guide/sql-syntax/7-ALTER-FUNCTION.md)
+    + [ALTER GROUP](/reference-guide/sql-syntax/8-ALTER-GROUP.md)
+    + [ALTER INDEX](/reference-guide/sql-syntax/9-ALTER-INDEX.md)
+    + [ALTER LANGUAGE](/reference-guide/sql-syntax/9.1-ALTER-LANGUAGE.md)
+    + [ALTER LARGE OBJECT](/reference-guide/sql-syntax/10-ALTER-LARGE-OBJECT.md)
+    + [ALTER MASKING POLICY](/reference-guide/sql-syntax/10.1-ALTER-MASKING-POLICY.md)
+    + [ALTER MATERIALIZED VIEW](/reference-guide/sql-syntax/11-ALTER-MATERIALIZED-VIEW.md)
+    + [ALTER OPERATOR](/reference-guide/sql-syntax/11.1-ALTER-OPERATOR.md)
+    + [ALTER RESOURCE LABEL](/reference-guide/sql-syntax/11.2-ALTER-RESOURCE-LABEL.md)
+    + [ALTER RESOURCE POOL](/reference-guide/sql-syntax/11.3-ALTER-RESOURCE-POOL.md)
+    + [ALTER ROLE](/reference-guide/sql-syntax/12-ALTER-ROLE.md)
+    + [ALTER ROW LEVEL SECURITY POLICY](/reference-guide/sql-syntax/13-ALTER-ROW-LEVEL-SECURITY-POLICY.md)
+    + [ALTER RULE](/reference-guide/sql-syntax/14-ALTER-RULE.md)
+    + [ALTER SCHEMA](/reference-guide/sql-syntax/15-ALTER-SCHEMA.md)
+    + [ALTER SEQUENCE](/reference-guide/sql-syntax/16-ALTER-SEQUENCE.md)
+    + [ALTER SERVER](/reference-guide/sql-syntax/17-ALTER-SERVER.md)
+    + [ALTER SESSION](/reference-guide/sql-syntax/18-ALTER-SESSION.md)
+    + [ALTER SYNONYM](/reference-guide/sql-syntax/19-ALTER-SYNONYM.md)
+    + [ALTER SYSTEM KILL SESSION](/reference-guide/sql-syntax/20-ALTER-SYSTEM-KILL-SESSION.md)
+    + [ALTER SYSTEM SET](/reference-guide/sql-syntax/21-ALTER-SYSTEM-SET.md)
+    + [ALTER TABLE](/reference-guide/sql-syntax/22-ALTER-TABLE.md)
+    + [ALTER TABLE PARTITION](/reference-guide/sql-syntax/23-ALTER-TABLE-PARTITION.md)
+    + [ALTER TABLE SUBPARTITION](/reference-guide/sql-syntax/23.1-ALTER-TABLE-SUBPARTITION.md)
+    + [ALTER TABLESPACE](/reference-guide/sql-syntax/24-ALTER-TABLESPACE.md)
+    + [ALTER TEXT SEARCH CONFIGURATION](/reference-guide/sql-syntax/25-ALTER-TEXT-SEARCH-CONFIGURATION.md)
+    + [ALTER TEXT SEARCH DICTIONARY](/reference-guide/sql-syntax/26-ALTER-TEXT-SEARCH-DICTIONARY.md)
+    + [ALTER TRIGGER](/reference-guide/sql-syntax/27-ALTER-TRIGGER.md)
+    + [ALTER TYPE](/reference-guide/sql-syntax/28-ALTER-TYPE.md)
+    + [ALTER USER](/reference-guide/sql-syntax/29-ALTER-USER.md)
+    + [ALTER USER MAPPING](/reference-guide/sql-syntax/30-ALTER-USER-MAPPING.md)
+    + [ALTER VIEW](/reference-guide/sql-syntax/31-ALTER-VIEW.md)
+    + [ANALYZE | ANALYSE](/reference-guide/sql-syntax/32-ANALYZE-ANALYSE.md)
+    + [BEGIN](/reference-guide/sql-syntax/33-BEGIN.md)
+    + [CALL](/reference-guide/sql-syntax/34-CALL.md)
+    + [CHECKPOINT](/reference-guide/sql-syntax/35-CHECKPOINT.md)
+    + [CLEAN CONNECTION](/reference-guide/sql-syntax/35.1-CLEAN-CONNECTION.md)
+    + [CLOSE](/reference-guide/sql-syntax/36-CLOSE.md)
+    + [CLUSTER](/reference-guide/sql-syntax/37-CLUSTER.md)
+    + [COMMENT](/reference-guide/sql-syntax/38-COMMENT.md)
+    + [COMMIT | END](/reference-guide/sql-syntax/39-COMMIT-END.md)
+    + [COMMIT PREPARED](/reference-guide/sql-syntax/40-COMMIT-PREPARED.md)
+    + [CONNECT BY](/reference-guide/sql-syntax/139-CONNECT-BY.md)
+    + [COPY](/reference-guide/sql-syntax/41-COPY.md)
+    + [CREATE AGGREGATE](/reference-guide/sql-syntax/41.1-CREATE-AGGREGATE.md)
+    + [CREATE AUDIT POLICY](/reference-guide/sql-syntax/41.2-CREATE-AUDIT-POLICY.md)
+    + [CREATE CAST](/reference-guide/sql-syntax/41.3-CREATE-CAST.md)
+    + [CREATE CLIENT MASTER KEY](/reference-guide/sql-syntax/42-CREATE-CLIENT-MASTER-KEY.md)
+    + [CREATE COLUMN ENCRYPTION KEY](/reference-guide/sql-syntax/43-CREATE-COLUMN-ENCRYPTION-KEY.md)
+    + [CREATE DATABASE](/reference-guide/sql-syntax/44-CREATE-DATABASE.md)
+    + [CREATE DATA SOURCE](/reference-guide/sql-syntax/45-CREATE-DATA-SOURCE.md)
+    + [CREATE DIRECTORY](/reference-guide/sql-syntax/46-CREATE-DIRECTORY.md)
+    + [CREATE EXTENSION](/reference-guide/sql-syntax/46.1-CREATE-EXTENSION.md)
+    + [CREATE FOREIGN TABLE](/reference-guide/sql-syntax/47-CREATE-FOREIGN-TABLE.md)
+    + [CREATE FUNCTION](/reference-guide/sql-syntax/48-CREATE-FUNCTION.md)
+    + [CREATE GROUP](/reference-guide/sql-syntax/49-CREATE-GROUP.md)
+    + [CREATE INCREMENTAL MATERIALIZED VIEW](/reference-guide/sql-syntax/49.1-CREATE-INCREMENTAL-MATERIALIZED-VIEW.md)
+    + [CREATE INDEX](/reference-guide/sql-syntax/50-CREATE-INDEX.md)
+    + [CREATE LANGUAGE](/reference-guide/sql-syntax/50.1-CREATE-LANGUAGE.md)
+    + [CREATE MASKING POLICY](/reference-guide/sql-syntax/50.2-CREATE-MASKING-POLICY.md)
+    + [CREATE MATERIALIZED VIEW](/reference-guide/sql-syntax/51-CREATE-MATERIALIZED-VIEW.md)
+    + [CREATE MODEL](/reference-guide/sql-syntax/50.3-CREATE-MODEL.md)
+    + [CREATE OPERATOR](/reference-guide/sql-syntax/51.1-CREATE-OPERATOR.md)
+    + [CREATE PACKAGE](/reference-guide/sql-syntax/51.2-CREATE-PACKAGE.md)
+    + [CREATE ROW LEVEL SECURITY POLICY](/reference-guide/sql-syntax/52-CREATE-ROW-LEVEL-SECURITY-POLICY.md)
+    + [CREATE PROCEDURE](/reference-guide/sql-syntax/53-CREATE-PROCEDURE.md)
+    + [CREATE RESOURCE LABEL](/reference-guide/sql-syntax/53.1-CREATE-RESOURCE-LABEL.md)
+    + [CREATE RESOURCE POOL](/reference-guide/sql-syntax/53.2-CREATE-RESOURCE-POOL.md)
+    + [CREATE ROLE](/reference-guide/sql-syntax/54-CREATE-ROLE.md)
+    + [CREATE RULE](/reference-guide/sql-syntax/55-CREATE-RULE.md)
+    + [CREATE SCHEMA](/reference-guide/sql-syntax/56-CREATE-SCHEMA.md)
+    + [CREATE SEQUENCE](/reference-guide/sql-syntax/57-CREATE-SEQUENCE.md)
+    + [CREATE SERVER](/reference-guide/sql-syntax/58-CREATE-SERVER.md)
+    + [CREATE SYNONYM](/reference-guide/sql-syntax/59-CREATE-SYNONYM.md)
+    + [CREATE TABLE](/reference-guide/sql-syntax/60-CREATE-TABLE.md)
+    + [CREATE TABLE AS](/reference-guide/sql-syntax/61-CREATE-TABLE-AS.md)
+    + [CREATE TABLE PARTITION](/reference-guide/sql-syntax/62-CREATE-TABLE-PARTITION.md)
+    + [CREATE TABLE SUBPARTITION](/reference-guide/sql-syntax/62.1-CREATE-TABLE-SUBPARTITION.md)
+    + [CREATE TABLESPACE](/reference-guide/sql-syntax/63-CREATE-TABLESPACE.md)
+    + [CREATE TEXT SEARCH CONFIGURATION](/reference-guide/sql-syntax/64-CREATE-TEXT-SEARCH-CONFIGURATION.md)
+    + [CREATE TEXT SEARCH DICTIONARY](/reference-guide/sql-syntax/65-CREATE-TEXT-SEARCH-DICTIONARY.md)
+    + [CREATE TRIGGER](/reference-guide/sql-syntax/66-CREATE-TRIGGER.md)
+    + [CREATE TYPE](/reference-guide/sql-syntax/67-CREATE-TYPE.md)
+    + [CREATE USER](/reference-guide/sql-syntax/68-CREATE-USER.md)
+    + [CREATE USER MAPPING](/reference-guide/sql-syntax/69-CREATE-USER-MAPPING.md)
+    + [CREATE VIEW](/reference-guide/sql-syntax/70-CREATE-VIEW.md)
+    + [CREATE WEAK PASSWORD DICTIONARY](/reference-guide/sql-syntax/70.1-CREATE-WEAK-PASSWORD-DICTIONARY.md)
+    + [CURSOR](/reference-guide/sql-syntax/71-CURSOR.md)
+    + [DEALLOCATE](/reference-guide/sql-syntax/72-DEALLOCATE.md)
+    + [DECLARE](/reference-guide/sql-syntax/73-DECLARE.md)
+    + [DELETE](/reference-guide/sql-syntax/74-DELETE.md)
+    + [DO](/reference-guide/sql-syntax/75-DO.md)
+    + [DROP AGGREGATE](/reference-guide/sql-syntax/75.1-DROP-AGGREGATE.md)
+    + [DROP AUDIT POLICY](/reference-guide/sql-syntax/75.2-DROP-AUDIT-POLICY.md)
+    + [DROP CAST](/reference-guide/sql-syntax/75.3-DROP-CAST.md)
+    + [DROP CLIENT MASTER KEY](/reference-guide/sql-syntax/76-DROP-CLIENT-MASTER-KEY.md)
+    + [DROP COLUMN ENCRYPTION KEY](/reference-guide/sql-syntax/77-DROP-COLUMN-ENCRYPTION-KEY.md)
+    + [DROP DATABASE](/reference-guide/sql-syntax/78-DROP-DATABASE.md)
+    + [DROP DATA SOURCE](/reference-guide/sql-syntax/79-DROP-DATA-SOURCE.md)
+    + [DROP DIRECTORY](/reference-guide/sql-syntax/80-DROP-DIRECTORY.md)
+    + [DROP EXTENSION](/reference-guide/sql-syntax/80.1-DROP-EXTENSION.md)
+    + [DROP FOREIGN TABLE](/reference-guide/sql-syntax/81-DROP-FOREIGN-TABLE.md)
+    + [DROP FUNCTION](/reference-guide/sql-syntax/82-DROP-FUNCTION.md)
+    + [DROP GROUP](/reference-guide/sql-syntax/83-DROP-GROUP.md)
+    + [DROP INDEX](/reference-guide/sql-syntax/84-DROP-INDEX.md)
+    + [DROP LANGUAGE](/reference-guide/sql-syntax/84.1-DROP-LANGUAGE.md)
+    + [DROP MASKING POLICY](/reference-guide/sql-syntax/84.2-DROP-MASKING-POLICY.md)
+    + [DROP MATERIALIZED VIEW](/reference-guide/sql-syntax/85-DROP-MATERIALIZED-VIEW.md)
+    + [DROP MODEL](/reference-guide/sql-syntax/84.3-DROP-MODEL.md)
+    + [DROP OPERATOR](/reference-guide/sql-syntax/85.1-DROP-OPERATOR.md)
+    + [DROP OWNED](/reference-guide/sql-syntax/86-DROP-OWNED.md)
+    + [DROP PACKAGE](/reference-guide/sql-syntax/86.3-DROP-PACKAGE.md)
+    + [DROP PROCEDURE](/reference-guide/sql-syntax/88-DROP-PROCEDURE.md)
+    + [DROP RESOURCE LABEL](/reference-guide/sql-syntax/86.1-DROP-RESOURCE-LABEL.md)
+    + [DROP RESOURCE POOL](/reference-guide/sql-syntax/86.2-DROP-RESOURCE-POOL.md)
+    + [DROP ROW LEVEL SECURITY POLICY](/reference-guide/sql-syntax/87-DROP-ROW-LEVEL-SECURITY-POLICY.md)
+    + [DROP ROLE](/reference-guide/sql-syntax/89-DROP-ROLE.md)
+    + [DROP RULE](/reference-guide/sql-syntax/90-DROP-RULE.md)
+    + [DROP SCHEMA](/reference-guide/sql-syntax/91-DROP-SCHEMA.md)
+    + [DROP SEQUENCE](/reference-guide/sql-syntax/92-DROP-SEQUENCE.md)
+    + [DROP SERVER](/reference-guide/sql-syntax/93-DROP-SERVER.md)
+    + [DROP SYNONYM](/reference-guide/sql-syntax/94-DROP-SYNONYM.md)
+    + [DROP TABLE](/reference-guide/sql-syntax/95-DROP-TABLE.md)
+    + [DROP TABLESPACE](/reference-guide/sql-syntax/96-DROP-TABLESPACE.md)
+    + [DROP TEXT SEARCH CONFIGURATION](/reference-guide/sql-syntax/97-DROP-TEXT-SEARCH-CONFIGURATION.md)
+    + [DROP TEXT SEARCH DICTIONARY](/reference-guide/sql-syntax/98-DROP-TEXT-SEARCH-DICTIONARY.md)
+    + [DROP TRIGGER](/reference-guide/sql-syntax/99-DROP-TRIGGER.md)
+    + [DROP TYPE](/reference-guide/sql-syntax/100-DROP-TYPE.md)
+    + [DROP USER](/reference-guide/sql-syntax/101-DROP-USER.md)
+    + [DROP USER MAPPING](/reference-guide/sql-syntax/102-DROP-USER-MAPPING.md)
+    + [DROP VIEW](/reference-guide/sql-syntax/103-DROP-VIEW.md)
+    + [DROP WEAK PASSWORD DICTIONARY](/reference-guide/sql-syntax/103.1-DROP-WEAK-PASSWORD-DICTIONARY.md)
+    + [EXECUTE](/reference-guide/sql-syntax/104-EXECUTE.md)
+    + [EXECUTE DIRECT](/reference-guide/sql-syntax/104.1-EXECUTE-DIRECT.md)
+    + [EXPLAIN](/reference-guide/sql-syntax/105-EXPLAIN.md)
+    + [EXPLAIN PLAN](/reference-guide/sql-syntax/106-EXPLAIN-PLAN.md)
+    + [FETCH](/reference-guide/sql-syntax/107-FETCH.md)
+    + [GRANT](/reference-guide/sql-syntax/108-GRANT.md)
+    + [INSERT](/reference-guide/sql-syntax/109-INSERT.md)
+    + [LOCK](/reference-guide/sql-syntax/110-LOCK.md)
+    + [MOVE](/reference-guide/sql-syntax/111-MOVE.md)
+    + [MERGE INTO](/reference-guide/sql-syntax/112-MERGE-INTO.md)
+    + [PREDICT BY](/reference-guide/sql-syntax/112.1-PREDICT-BY.md)
+    + [PREPARE](/reference-guide/sql-syntax/113-PREPARE.md)
+    + [PREPARE TRANSACTION](/reference-guide/sql-syntax/114-PREPARE-TRANSACTION.md)
+    + [PURGE](/reference-guide/sql-syntax/114.1-PURGE.md)
+    + [REASSIGN OWNED](/reference-guide/sql-syntax/115-REASSIGN-OWNED.md)
+    + [REFRESH INCREMENTAL MATERIALIZED VIEW](/reference-guide/sql-syntax/115.1-REFRESH-INCREMENTAL-MATERIALIZED-VIEW.md)
+    + [REFRESH MATERIALIZED VIEW](/reference-guide/sql-syntax/116-REFRESH-MATERIALIZED-VIEW.md)
+    + [REINDEX](/reference-guide/sql-syntax/117-REINDEX.md)
+    + [RELEASE SAVEPOINT](/reference-guide/sql-syntax/118-RELEASE-SAVEPOINT.md)
+    + [RESET](/reference-guide/sql-syntax/119-RESET.md)
+    + [REVOKE](/reference-guide/sql-syntax/120-REVOKE.md)
+    + [ROLLBACK](/reference-guide/sql-syntax/121-ROLLBACK.md)
+    + [ROLLBACK PREPARED](/reference-guide/sql-syntax/122-ROLLBACK-PREPARED.md)
+    + [ROLLBACK TO SAVEPOINT](/reference-guide/sql-syntax/123-ROLLBACK-TO-SAVEPOINT.md)
+    + [SAVEPOINT](/reference-guide/sql-syntax/124-SAVEPOINT.md)
+    + [SELECT](/reference-guide/sql-syntax/125-SELECT.md)
+    + [SELECT INTO](/reference-guide/sql-syntax/126-SELECT-INTO.md)
+    + [SET](/reference-guide/sql-syntax/127-SET.md)
+    + [SET CONSTRAINTS](/reference-guide/sql-syntax/128-SET-CONSTRAINTS.md)
+    + [SET ROLE](/reference-guide/sql-syntax/129-SET-ROLE.md)
+    + [SET SESSION AUTHORIZATION](/reference-guide/sql-syntax/130-SET-SESSION-AUTHORIZATION.md)
+    + [SET TRANSACTION](/reference-guide/sql-syntax/131-SET-TRANSACTION.md)
+    + [SHOW](/reference-guide/sql-syntax/132-SHOW.md)
+    + [SHUTDOWN](/reference-guide/sql-syntax/133-SHUTDOWN.md)
+    + [SNAPSHOT](/reference-guide/sql-syntax/133.1-SNAPSHOT.md)
+    + [START TRANSACTION](/reference-guide/sql-syntax/134-START-TRANSACTION.md)
+    + [TIMECAPSULE TABLE](/reference-guide/sql-syntax/134.1-TIMECAPSULE-TABLE.md)
+    + [TRUNCATE](/reference-guide/sql-syntax/135-TRUNCATE.md)
+    + [UPDATE](/reference-guide/sql-syntax/136-UPDATE.md)
+    + [VACUUM](/reference-guide/sql-syntax/137-VACUUM.md)
+    + [VALUES](/reference-guide/sql-syntax/138-VALUES.md)
+  + SQL Reference
+    + [MogDB SQL](/reference-guide/sql-reference/1-mogdb-sql.md)
+    + [Keywords](/reference-guide/sql-reference/2-keywords.md)
+    + [Constant and Macro](/reference-guide/sql-reference/3-constant-and-macro.md)
+    + Expressions
+      + [Simple Expressions](/reference-guide/sql-reference/4-expressions/1-simple-expressions.md)
+      + [Condition Expressions](/reference-guide/sql-reference/4-expressions/2-condition-expressions.md)
+      + [Subquery Expressions](/reference-guide/sql-reference/4-expressions/3-subquery-expressions.md)
+      + [Array Expressions](/reference-guide/sql-reference/4-expressions/4-array-expressions.md)
+      + [Row Expressions](/reference-guide/sql-reference/4-expressions/5-row-expressions.md)
+    + Type Conversion
+      + [Overview](/reference-guide/sql-reference/5-type-conversion/1-type-conversion-overview.md)
+      + [Operators](/reference-guide/sql-reference/5-type-conversion/2-operators.md)
+      + [Functions](/reference-guide/sql-reference/5-type-conversion/3-functions.md)
+      + [Value Storage](/reference-guide/sql-reference/5-type-conversion/4-value-storage.md)
+      + [UNION, CASE, and Related Constructs](/reference-guide/sql-reference/5-type-conversion/5-union-case-and-related-constructs.md)
+    + Full Text Search
+      + Introduction
+        + [Full-Text Retrieval](/reference-guide/sql-reference/6-full-text-search/1-introduction/1-full-text-retrieval.md)
+        + [What Is a Document?](/reference-guide/sql-reference/6-full-text-search/1-introduction/2-what-is-a-document.md)
+        + [Basic Text Matching](/reference-guide/sql-reference/6-full-text-search/1-introduction/3-basic-text-matching.md)
+        + [Configurations](/reference-guide/sql-reference/6-full-text-search/1-introduction/4-configurations.md)
+      + Tables and Indexes
+        + [Searching a Table](/reference-guide/sql-reference/6-full-text-search/2-tables-and-indexes/1-searching-a-table.md)
+        + [Creating an Index](/reference-guide/sql-reference/6-full-text-search/2-tables-and-indexes/2-creating-an-index.md)
+        + [Constraints on Index Use](/reference-guide/sql-reference/6-full-text-search/2-tables-and-indexes/3-constraints-on-index-use.md)
+      + Controlling Text Search
+        + [Parsing Documents](/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/1-parsing-documents.md)
+        + [Parsing Queries](/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/2-parsing-queries.md)
+        + [Ranking Search Results](/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/3-ranking-search-results.md)
+        + [Highlighting Results](/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/4-highlighting-results.md)
+      + Additional Features
+        + [Manipulating tsvector](/reference-guide/sql-reference/6-full-text-search/4-additional-features/1-manipulating-tsvector.md)
+        + [Manipulating Queries](/reference-guide/sql-reference/6-full-text-search/4-additional-features/2-manipulating-queries.md)
+        + [Rewriting Queries](/reference-guide/sql-reference/6-full-text-search/4-additional-features/3-rewriting-queries.md)
+        + [Gathering Document Statistics](/reference-guide/sql-reference/6-full-text-search/4-additional-features/4-gathering-document-statistics.md)
+      + [Parser](/reference-guide/sql-reference/6-full-text-search/5-parser.md)
+      + Dictionaries
+        + [Overview](/reference-guide/sql-reference/6-full-text-search/6-dictionaries/1-dictionaries-overview.md)
+        + [Stop Words](/reference-guide/sql-reference/6-full-text-search/6-dictionaries/2-stop-words.md)
+        + [Simple Dictionary](/reference-guide/sql-reference/6-full-text-search/6-dictionaries/3-simple-dictionary.md)
+        + [Synonym Dictionary](/reference-guide/sql-reference/6-full-text-search/6-dictionaries/4-synonym-dictionary.md)
+        + [Thesaurus Dictionary](/reference-guide/sql-reference/6-full-text-search/6-dictionaries/5-thesaurus-dictionary.md)
+        + [Ispell Dictionary](/reference-guide/sql-reference/6-full-text-search/6-dictionaries/6-ispell-dictionary.md)
+        + [Snowball Dictionary](/reference-guide/sql-reference/6-full-text-search/6-dictionaries/7-snowball-dictionary.md)
+      + [Configuration Examples](/reference-guide/sql-reference/6-full-text-search/7-configuration-examples.md)
+      + Testing and Debugging Text Search
+        + [Testing a Configuration](/reference-guide/sql-reference/6-full-text-search/8-testing-and-debugging-text-search/1-testing-a-configuration.md)
+        + [Testing a Parser](/reference-guide/sql-reference/6-full-text-search/8-testing-and-debugging-text-search/2-testing-a-parser.md)
+        + [Testing a Dictionary](/reference-guide/sql-reference/6-full-text-search/8-testing-and-debugging-text-search/3-testing-a-dictionary.md)
+      + [Limitations](/reference-guide/sql-reference/6-full-text-search/9-limitations.md)
+    + [System Operation](/reference-guide/sql-reference/7-system-operation.md)
+    + [Controlling Transactions](/reference-guide/sql-reference/8-controlling-transactions.md)
+    + [DDL Syntax Overview](/reference-guide/sql-reference/9-ddl-syntax-overview.md)
+    + [DML Syntax Overview](/reference-guide/sql-reference/10-dml-syntax-overview.md)
+    + [DCL Syntax Overview](/reference-guide/sql-reference/11-dcl-syntax-overview.md)
+    + Appendix
+      + GIN Indexes
+        + [Introduction](/reference-guide/sql-reference/13-appendix/1-gin-indexes/1-introduction.md)
+        + [Scalability](/reference-guide/sql-reference/13-appendix/1-gin-indexes/2-scalability.md)
+        + [Implementation](/reference-guide/sql-reference/13-appendix/1-gin-indexes/3-implementation.md)
+        + [GIN Tips and Tricks](/reference-guide/sql-reference/13-appendix/1-gin-indexes/4-gin-tips-and-tricks.md)
+      + [Extended Functions](/reference-guide/sql-reference/13-appendix/2-extended-functions.md)
+      + [Extended Syntax](/reference-guide/sql-reference/13-appendix/3-extended-syntax.md)
+  + GUC Parameters
+    + [GUC Parameter Usage](/reference-guide/guc-parameters/1-guc-parameter-usage.md)
+    + [File Location](/reference-guide/guc-parameters/2-file-location.md)
+    + Connection and Authentication
+      + [Connection Settings](/reference-guide/guc-parameters/3-connection-and-authentication/1-connection-settings.md)
+      + [Security and Authentication (postgresql.conf)](/reference-guide/guc-parameters/3-connection-and-authentication/2-security-and-authentication.md)
+      + [Communication Library Parameters](/reference-guide/guc-parameters/3-connection-and-authentication/3-communication-library-parameters.md)
+    + Resource Consumption
+      + [Memory](/reference-guide/guc-parameters/4-resource-consumption/1-memory.md)
+      + [Disk Space](/reference-guide/guc-parameters/4-resource-consumption/2-disk-space.md)
+      + [Kernel Resource Usage](/reference-guide/guc-parameters/4-resource-consumption/3-kernel-resource-usage.md)
+      + [Cost-based Vacuum Delay](/reference-guide/guc-parameters/4-resource-consumption/4-cost-based-vacuum-delay.md)
+      + [Background Writer](/reference-guide/guc-parameters/4-resource-consumption/5-background-writer.md)
+      + [Asynchronous I/O Operations](/reference-guide/guc-parameters/4-resource-consumption/6-asynchronous-io-operations.md)
+    + [Parallel Import](/reference-guide/guc-parameters/5-parallel-import.md)
+    + Write Ahead Log
+      + [Settings](/reference-guide/guc-parameters/6-write-ahead-log/1-settings.md)
+      + [Checkpoints](/reference-guide/guc-parameters/6-write-ahead-log/2-checkpoints.md)
+      + [Log Replay](/reference-guide/guc-parameters/6-write-ahead-log/3-log-replay.md)
+      + [Archiving](/reference-guide/guc-parameters/6-write-ahead-log/4-archiving.md)
+    + HA Replication
+      + [Sending Server](/reference-guide/guc-parameters/7-ha-replication/1-sending-server.md)
+      + [Primary Server](/reference-guide/guc-parameters/7-ha-replication/2-primary-server.md)
+      + [Standby Server](/reference-guide/guc-parameters/7-ha-replication/3-standby-server.md)
+    + [Memory Table](/reference-guide/guc-parameters/8-mot.md)
+    + Query Planning
+      + [Introduction](/reference-guide/guc-parameters/9-query-planning/introduction-to-query-planning.md)
+      + [Optimizer Method Configuration](/reference-guide/guc-parameters/9-query-planning/1-optimizer-method-configuration.md)
+      + [Optimizer Cost Constants](/reference-guide/guc-parameters/9-query-planning/2-optimizer-cost-constants.md)
+      + [Genetic Query Optimizer](/reference-guide/guc-parameters/9-query-planning/3-genetic-query-optimizer.md)
+      + [Other Optimizer Options](/reference-guide/guc-parameters/9-query-planning/4-other-optimizer-options.md)
+    + Error Reporting and Logging
+      + [Logging Destination](/reference-guide/guc-parameters/10-error-reporting-and-logging/1-logging-destination.md)
+      + [Logging Time](/reference-guide/guc-parameters/10-error-reporting-and-logging/2-logging-time.md)
+      + [Logging Content](/reference-guide/guc-parameters/10-error-reporting-and-logging/3-logging-content.md)
+      + [Using CSV Log Output](/reference-guide/guc-parameters/10-error-reporting-and-logging/4-using-csv-log-output.md)
+    + [Alarm Detection](/reference-guide/guc-parameters/11-alarm-detection.md)
+    + Statistics During the Database Running
+      + [Query and Index Statistics Collector](/reference-guide/guc-parameters/12-statistics-during-the-database-running/1-query-and-index-statistics-collector.md)
+      + [Performance Statistics](/reference-guide/guc-parameters/12-statistics-during-the-database-running/2-performance-statistics.md)
+    + [Load Management](/reference-guide/guc-parameters/13-load-management.md)
+    + [Automatic Vacuuming](/reference-guide/guc-parameters/14-automatic-vacuuming.md)
+    + Default Settings of Client Connection
+      + [Statement Behavior](/reference-guide/guc-parameters/15-default-settings-of-client-connection/1-statement-behavior.md)
+      + [Zone and Formatting](/reference-guide/guc-parameters/15-default-settings-of-client-connection/2-zone-and-formatting.md)
+      + [Other Default Parameters](/reference-guide/guc-parameters/15-default-settings-of-client-connection/3-other-default-parameters.md)
+    + [Lock Management](/reference-guide/guc-parameters/16-lock-management.md)
+    + Version and Platform Compatibility
+      + [Compatibility with Earlier Versions](/reference-guide/guc-parameters/17-version-and-platform-compatibility/1-compatibility-with-earlier-versions.md)
+      + [Platform and Client Compatibility](/reference-guide/guc-parameters/17-version-and-platform-compatibility/2-platform-and-client-compatibility.md)
+    + [Faut Tolerance](/reference-guide/guc-parameters/18-fault-tolerance.md)
+    + [Connection Pool Parameters](/reference-guide/guc-parameters/19-connection-pool-parameters.md)
+    + [MogDB Transaction](/reference-guide/guc-parameters/20-MogDB-transaction.md)
+    + [Developer Options](/reference-guide/guc-parameters/21-developer-options.md)
+    + Auditing
+      + [Audit Switch](/reference-guide/guc-parameters/22-auditing/1-audit-switch.md)
+      + [User and Permission Audit](/reference-guide/guc-parameters/22-auditing/2-user-and-permission-audit.md)
+      + [Operation Auditing](/reference-guide/guc-parameters/22-auditing/3-operation-audit.md)
+    + [Upgrade Parameters](/reference-guide/guc-parameters/23-upgrade-parameters.md)
+    + [Miscellaneous Parameters](/reference-guide/guc-parameters/24-miscellaneous-parameters.md)
+    + [Wait Events](/reference-guide/guc-parameters/25-wait-events.md)
+    + [Query](/reference-guide/guc-parameters/26-query.md)
+    + [System Performance Snapshot](/reference-guide/guc-parameters/27-system-performance-snapshot.md)
+    + [Security Configuration](/reference-guide/guc-parameters/27.1-security-configuration.md)
+    + [Global Temporary Table](/reference-guide/guc-parameters/29-global-temporary-table.md)
+    + [HyperLogLog](/reference-guide/guc-parameters/29.1-HyperLogLog.md)
+    + [Scheduled Task](/reference-guide/guc-parameters/31-scheduled-task.md)
+    + [Thread Pool](/reference-guide/guc-parameters/32-thread-pool.md)
+    + [User-defined Functions](/reference-guide/guc-parameters/33-user-defined-functions.md)
+    + [Backup and Restoration](/reference-guide/guc-parameters/34-backup-and-restoration.md)
+    + [Undo](/reference-guide/guc-parameters/35-undo.md)
+    + [DCF Parameters Settings](/reference-guide/guc-parameters/36-DCF-parameters-settings.md)
+    + [Flashback](/reference-guide/guc-parameters/37-flashback.md)
+    + [Rollback Parameters](/reference-guide/guc-parameters/38-rollback-parameters.md)
+    + [Reserved Parameters](/reference-guide/guc-parameters/39-reserved-parameters.md)
+    + [AI Features](/reference-guide/guc-parameters/40-AI-features.md)
+    + [Appendix](/reference-guide/guc-parameters/30-appendix.md)
+  + Schema
+    + Information Schema
+      + [Overview](/reference-guide/schema/information-schema/1-information-schema-overview.md)
+      + [_PG_FOREIGN_DATA_WRAPPERS](/reference-guide/schema/information-schema/2-_PG_FOREIGN_DATA_WRAPPERS.md)
+      + [_PG_FOREIGN_SERVERS](/reference-guide/schema/information-schema/3-_PG_FOREIGN_SERVERS.md)
+      + [_PG_FOREIGN_TABLE_COLUMNS](/reference-guide/schema/information-schema/4-_PG_FOREIGN_TABLE_COLUMNS.md)
+      + [_PG_FOREIGN_TABLES](/reference-guide/schema/information-schema/5-_PG_FOREIGN_TABLES.md)
+      + [_PG_USER_MAPPINGS](/reference-guide/schema/information-schema/6-_PG_USER_MAPPINGS.md)
+      + [INFORMATION_SCHEMA_CATALOG_NAME](/reference-guide/schema/information-schema/7-INFORMATION_SCHEMA_CATALOG_NAME.md)
+    + DBE_PERF
+      + [Overview](/reference-guide/schema/DBE_PERF/DBE_PERF_overview.md)
+      + OS
+        + [OS_RUNTIME](/reference-guide/schema/DBE_PERF/os/OS_RUNTIME.md)
+        + [GLOBAL_OS_RUNTIME](/reference-guide/schema/DBE_PERF/os/GLOBAL_OS_RUNTIME.md)
+        + [OS_THREADS](/reference-guide/schema/DBE_PERF/os/OS_THREADS.md)
+        + [GLOBAL_OS_THREADS](/reference-guide/schema/DBE_PERF/os/GLOBAL_OS_THREADS.md)
+      + Instance
+        + [INSTANCE_TIME](/reference-guide/schema/DBE_PERF/instance/INSTANCE_TIME.md)
+        + [GLOBAL_INSTANCE_TIME](/reference-guide/schema/DBE_PERF/instance/GLOBAL_INSTANCE_TIME.md)
+      + Memory
+        + [MEMORY_NODE_DETAIL](/reference-guide/schema/DBE_PERF/memory/MEMORY_NODE_DETAIL.md)
+        + [GLOBAL_MEMORY_NODE_DETAIL](/reference-guide/schema/DBE_PERF/memory/GLOBAL_MEMORY_NODE_DETAIL.md)
+        + [GS_SHARED_MEMORY_DETAIL](/reference-guide/schema/DBE_PERF/memory/GS_SHARED_MEMORY_DETAIL.md)
+        + [GLOBAL_SHARED_MEMORY_DETAIL](/reference-guide/schema/DBE_PERF/memory/GLOBAL_SHARED_MEMORY_DETAIL.md)
+      + File
+        + [FILE_IOSTAT](/reference-guide/schema/DBE_PERF/file/FILE_IOSTAT.md)
+        + [SUMMARY_FILE_IOSTAT](/reference-guide/schema/DBE_PERF/file/SUMMARY_FILE_IOSTAT.md)
+        + [GLOBAL_FILE_IOSTAT](/reference-guide/schema/DBE_PERF/file/GLOBAL_FILE_IOSTAT.md)
+        + [FILE_REDO_IOSTAT](/reference-guide/schema/DBE_PERF/file/FILE_REDO_IOSTAT.md)
+        + [SUMMARY_FILE_REDO_IOSTAT](/reference-guide/schema/DBE_PERF/file/SUMMARY_FILE_REDO_IOSTAT.md)
+        + [GLOBAL_FILE_REDO_IOSTAT](/reference-guide/schema/DBE_PERF/file/GLOBAL_FILE_REDO_IOSTAT.md)
+        + [LOCAL_REL_IOSTAT](/reference-guide/schema/DBE_PERF/file/LOCAL_REL_IOSTAT.md)
+        + [GLOBAL_REL_IOSTAT](/reference-guide/schema/DBE_PERF/file/GLOBAL_REL_IOSTAT.md)
+        + [SUMMARY_REL_IOSTAT](/reference-guide/schema/DBE_PERF/file/SUMMARY_REL_IOSTAT.md)
+      + Object
+        + [STAT_USER_TABLES](/reference-guide/schema/DBE_PERF/object/STAT_USER_TABLES.md)
+        + [SUMMARY_STAT_USER_TABLES](/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_USER_TABLES.md)
+        + [GLOBAL_STAT_USER_TABLES](/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_USER_TABLES.md)
+        + [STAT_USER_INDEXES](/reference-guide/schema/DBE_PERF/object/STAT_USER_INDEXES.md)
+        + [SUMMARY_STAT_USER_INDEXES](/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_USER_INDEXES.md)
+        + [GLOBAL_STAT_USER_INDEXES](/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_USER_INDEXES.md)
+        + [STAT_SYS_TABLES](/reference-guide/schema/DBE_PERF/object/STAT_SYS_TABLES.md)
+        + [SUMMARY_STAT_SYS_TABLES](/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_SYS_TABLES.md)
+        + [GLOBAL_STAT_SYS_TABLES](/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_SYS_TABLES.md)
+        + [STAT_SYS_INDEXES](/reference-guide/schema/DBE_PERF/object/STAT_SYS_INDEXES.md)
+        + [SUMMARY_STAT_SYS_INDEXES](/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_SYS_INDEXES.md)
+        + [GLOBAL_STAT_SYS_INDEXES](/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_SYS_INDEXES.md)
+        + [STAT_ALL_TABLES](/reference-guide/schema/DBE_PERF/object/STAT_ALL_TABLES.md)
+        + [SUMMARY_STAT_ALL_TABLES](/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_ALL_TABLES.md)
+        + [GLOBAL_STAT_ALL_TABLES](/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_ALL_TABLES.md)
+        + [STAT_ALL_INDEXES](/reference-guide/schema/DBE_PERF/object/STAT_ALL_INDEXES.md)
+        + [SUMMARY_STAT_ALL_INDEXES](/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_ALL_INDEXES.md)
+        + [GLOBAL_STAT_ALL_INDEXES](/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_ALL_INDEXES.md)
+        + [STAT_DATABASE](/reference-guide/schema/DBE_PERF/object/STAT_DATABASE.md)
+        + [SUMMARY_STAT_DATABASE](/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_DATABASE.md)
+        + [GLOBAL_STAT_DATABASE](/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_DATABASE.md)
+        + [STAT_DATABASE_CONFLICTS](/reference-guide/schema/DBE_PERF/object/STAT_DATABASE_CONFLICTS.md)
+        + [SUMMARY_STAT_DATABASE_CONFLICTS](/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_DATABASE_CONFLICTS.md)
+        + [GLOBAL_STAT_DATABASE_CONFLICTS](/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_DATABASE_CONFLICTS.md)
+        + [STAT_XACT_ALL_TABLES](/reference-guide/schema/DBE_PERF/object/STAT_XACT_ALL_TABLES.md)
+        + [SUMMARY_STAT_XACT_ALL_TABLES](/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_ALL_TABLES.md)
+        + [GLOBAL_STAT_XACT_ALL_TABLES](/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_ALL_TABLES.md)
+        + [STAT_XACT_SYS_TABLES](/reference-guide/schema/DBE_PERF/object/STAT_XACT_SYS_TABLES.md)
+        + [SUMMARY_STAT_XACT_SYS_TABLES](/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_SYS_TABLES.md)
+        + [GLOBAL_STAT_XACT_SYS_TABLES](/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_SYS_TABLES.md)
+        + [STAT_XACT_USER_TABLES](/reference-guide/schema/DBE_PERF/object/STAT_XACT_USER_TABLES.md)
+        + [SUMMARY_STAT_XACT_USER_TABLES](/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_USER_TABLES.md)
+        + [GLOBAL_STAT_XACT_USER_TABLES](/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_USER_TABLES.md)
+        + [STAT_XACT_USER_FUNCTIONS](/reference-guide/schema/DBE_PERF/object/STAT_XACT_USER_FUNCTIONS.md)
+        + [SUMMARY_STAT_XACT_USER_FUNCTIONS](/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_USER_FUNCTIONS.md)
+        + [GLOBAL_STAT_XACT_USER_FUNCTIONS](/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_USER_FUNCTIONS.md)
+        + [STAT_BAD_BLOCK](/reference-guide/schema/DBE_PERF/object/STAT_BAD_BLOCK.md)
+        + [SUMMARY_STAT_BAD_BLOCK](/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_BAD_BLOCK.md)
+        + [GLOBAL_STAT_BAD_BLOCK](/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_BAD_BLOCK.md)
+        + [STAT_USER_FUNCTIONS](/reference-guide/schema/DBE_PERF/object/STAT_USER_FUNCTIONS.md)
+        + [SUMMARY_STAT_USER_FUNCTIONS](/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_USER_FUNCTIONS.md)
+        + [GLOBAL_STAT_USER_FUNCTIONS](/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_USER_FUNCTIONS.md)
+      + Workload
+        + [WORKLOAD_SQL_COUNT](/reference-guide/schema/DBE_PERF/workload/WORKLOAD_SQL_COUNT.md)
+        + [SUMMARY_WORKLOAD_SQL_COUNT](/reference-guide/schema/DBE_PERF/workload/SUMMARY_WORKLOAD_SQL_COUNT.md)
+        + [WORKLOAD_TRANSACTION](/reference-guide/schema/DBE_PERF/workload/WORKLOAD_TRANSACTION.md)
+        + [SUMMARY_WORKLOAD_TRANSACTION](/reference-guide/schema/DBE_PERF/workload/SUMMARY_WORKLOAD_TRANSACTION.md)
+        + [GLOBAL_WORKLOAD_TRANSACTION](/reference-guide/schema/DBE_PERF/workload/GLOBAL_WORKLOAD_TRANSACTION.md)
+        + [WORKLOAD_SQL_ELAPSE_TIME](/reference-guide/schema/DBE_PERF/workload/WORKLOAD_SQL_ELAPSE_TIME.md)
+        + [SUMMARY_WORKLOAD_SQL_ELAPSE_TIME](/reference-guide/schema/DBE_PERF/workload/SUMMARY_WORKLOAD_SQL_ELAPSE_TIME.md)
+        + [USER_TRANSACTION](/reference-guide/schema/DBE_PERF/workload/USER_TRANSACTION.md)
+        + [GLOBAL_USER_TRANSACTION](/reference-guide/schema/DBE_PERF/workload/GLOBAL_USER_TRANSACTION.md)
+      + Session/Thread
+        + [SESSION_STAT](/reference-guide/schema/DBE_PERF/session-thread/SESSION_STAT.md)
+        + [GLOBAL_SESSION_STAT](/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_STAT.md)
+        + [SESSION_TIME](/reference-guide/schema/DBE_PERF/session-thread/SESSION_TIME.md)
+        + [GLOBAL_SESSION_TIME](/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_TIME.md)
+        + [SESSION_MEMORY](/reference-guide/schema/DBE_PERF/session-thread/SESSION_MEMORY.md)
+        + [GLOBAL_SESSION_MEMORY](/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_MEMORY.md)
+        + [SESSION_MEMORY_DETAIL](/reference-guide/schema/DBE_PERF/session-thread/SESSION_MEMORY_DETAIL.md)
+        + [GLOBAL_SESSION_MEMORY_DETAIL](/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_MEMORY_DETAIL.md)
+        + [SESSION_STAT_ACTIVITY](/reference-guide/schema/DBE_PERF/session-thread/SESSION_STAT_ACTIVITY.md)
+        + [GLOBAL_SESSION_STAT_ACTIVITY](/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_STAT_ACTIVITY.md)
+        + [THREAD_WAIT_STATUS](/reference-guide/schema/DBE_PERF/session-thread/THREAD_WAIT_STATUS.md)
+        + [GLOBAL_THREAD_WAIT_STATUS](/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_THREAD_WAIT_STATUS.md)
+        + [LOCAL_THREADPOOL_STATUS](/reference-guide/schema/DBE_PERF/session-thread/LOCAL_THREADPOOL_STATUS.md)
+        + [GLOBAL_THREADPOOL_STATUS](/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_THREADPOOL_STATUS.md)
+        + [SESSION_CPU_RUNTIME](/reference-guide/schema/DBE_PERF/session-thread/SESSION_CPU_RUNTIME.md)
+        + [SESSION_MEMORY_RUNTIME](/reference-guide/schema/DBE_PERF/session-thread/SESSION_MEMORY_RUNTIME.md)
+        + [STATEMENT_IOSTAT_COMPLEX_RUNTIME](/reference-guide/schema/DBE_PERF/session-thread/STATEMENT_IOSTAT_COMPLEX_RUNTIME.md)
+        + [LOCAL_ACTIVE_SESSION](/reference-guide/schema/DBE_PERF/session-thread/LOCAL_ACTIVE_SESSION.md)
+      + Transaction
+        + [TRANSACTIONS_PREPARED_XACTS](/reference-guide/schema/DBE_PERF/transaction/TRANSACTIONS_PREPARED_XACTS.md)
+        + [SUMMARY_TRANSACTIONS_PREPARED_XACTS](/reference-guide/schema/DBE_PERF/transaction/SUMMARY_TRANSACTIONS_PREPARED_XACTS.md)
+        + [GLOBAL_TRANSACTIONS_PREPARED_XACTS](/reference-guide/schema/DBE_PERF/transaction/GLOBAL_TRANSACTIONS_PREPARED_XACTS.md)
+        + [TRANSACTIONS_RUNNING_XACTS](/reference-guide/schema/DBE_PERF/transaction/TRANSACTIONS_RUNNING_XACTS.md)
+        + [SUMMARY_TRANSACTIONS_RUNNING_XACTS](/reference-guide/schema/DBE_PERF/transaction/SUMMARY_TRANSACTIONS_RUNNING_XACTS.md)
+        + [GLOBAL_TRANSACTIONS_RUNNING_XACTS](/reference-guide/schema/DBE_PERF/transaction/GLOBAL_TRANSACTIONS_RUNNING_XACTS.md)
+      + Query
+        + [STATEMENT](/reference-guide/schema/DBE_PERF/query/STATEMENT.md)
+        + [SUMMARY_STATEMENT](/reference-guide/schema/DBE_PERF/query/SUMMARY_STATEMENT.md)
+        + [STATEMENT_COUNT](/reference-guide/schema/DBE_PERF/query/STATEMENT_COUNT.md)
+        + [GLOBAL_STATEMENT_COUNT](/reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COUNT.md)
+        + [SUMMARY_STATEMENT_COUNT](/reference-guide/schema/DBE_PERF/query/SUMMARY_STATEMENT_COUNT.md)
+        + [GLOBAL_STATEMENT_COMPLEX_HISTORY](/reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COMPLEX_HISTORY.md)
+        + [GLOBAL_STATEMENT_COMPLEX_HISTORY_TABLE](/reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COMPLEX_HISTORY_TABLE.md)
+        + [GLOBAL_STATEMENT_COMPLEX_RUNTIME](/reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COMPLEX_RUNTIME.md)
+        + [STATEMENT_RESPONSETIME_PERCENTILE](/reference-guide/schema/DBE_PERF/query/STATEMENT_RESPONSETIME_PERCENTILE.md)
+        + [STATEMENT_USER_COMPLEX_HISTORY](/reference-guide/schema/DBE_PERF/query/STATEMENT_USER_COMPLEX_HISTORY.md)
+        + [STATEMENT_COMPLEX_RUNTIME](/reference-guide/schema/DBE_PERF/query/STATEMENT_COMPLEX_RUNTIME.md)
+        + [STATEMENT_COMPLEX_HISTORY_TABLE](/reference-guide/schema/DBE_PERF/query/STATEMENT_COMPLEX_HISTORY_TABLE.md)
+        + [STATEMENT_COMPLEX_HISTORY](/reference-guide/schema/DBE_PERF/query/STATEMENT_COMPLEX_HISTORY.md)
+        + [STATEMENT_WLMSTAT_COMPLEX_RUNTIME](/reference-guide/schema/DBE_PERF/query/STATEMENT_WLMSTAT_COMPLEX_RUNTIME.md)
+        + [STATEMENT_HISTORY](/reference-guide/schema/DBE_PERF/query/STATEMENT_HISTORY.md)
+      + Cache/IO
+        + [STATIO_USER_TABLES](/reference-guide/schema/DBE_PERF/cache-io/STATIO_USER_TABLES.md)
+        + [SUMMARY_STATIO_USER_TABLES](/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_USER_TABLES.md)
+        + [GLOBAL_STATIO_USER_TABLES](/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_USER_TABLES.md)
+        + [STATIO_USER_INDEXES](/reference-guide/schema/DBE_PERF/cache-io/STATIO_USER_INDEXES.md)
+        + [SUMMARY_STATIO_USER_INDEXES](/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_USER_INDEXES.md)
+        + [GLOBAL_STATIO_USER_INDEXES](/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_USER_INDEXES.md)
+        + [STATIO_USER_SEQUENCES](/reference-guide/schema/DBE_PERF/cache-io/STATIO_USER_SEQUENCES.md)
+        + [SUMMARY_STATIO_USER_SEQUENCES](/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_USER_SEQUENCES.md)
+        + [GLOBAL_STATIO_USER_SEQUENCES](/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_USER_SEQUENCES.md)
+        + [STATIO_SYS_TABLES](/reference-guide/schema/DBE_PERF/cache-io/STATIO_SYS_TABLES.md)
+        + [SUMMARY_STATIO_SYS_TABLES](/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_SYS_TABLES.md)
+        + [GLOBAL_STATIO_SYS_TABLES](/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_SYS_TABLES.md)
+        + [STATIO_SYS_INDEXES](/reference-guide/schema/DBE_PERF/cache-io/STATIO_SYS_INDEXES.md)
+        + [SUMMARY_STATIO_SYS_INDEXES](/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_SYS_INDEXES.md)
+        + [GLOBAL_STATIO_SYS_INDEXES](/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_SYS_INDEXES.md)
+        + [STATIO_SYS_SEQUENCES](/reference-guide/schema/DBE_PERF/cache-io/STATIO_SYS_SEQUENCES.md)
+        + [SUMMARY_STATIO_SYS_SEQUENCES](/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_SYS_SEQUENCES.md)
+        + [GLOBAL_STATIO_SYS_SEQUENCES](/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_SYS_SEQUENCES.md)
+        + [STATIO_ALL_TABLES](/reference-guide/schema/DBE_PERF/cache-io/STATIO_ALL_TABLES.md)
+        + [SUMMARY_STATIO_ALL_TABLES](/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_ALL_TABLES.md)
+        + [GLOBAL_STATIO_ALL_TABLES](/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_ALL_TABLES.md)
+        + [STATIO_ALL_INDEXES](/reference-guide/schema/DBE_PERF/cache-io/STATIO_ALL_INDEXES.md)
+        + [SUMMARY_STATIO_ALL_INDEXES](/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_ALL_INDEXES.md)
+        + [GLOBAL_STATIO_ALL_INDEXES](/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_ALL_INDEXES.md)
+        + [STATIO_ALL_SEQUENCES](/reference-guide/schema/DBE_PERF/cache-io/STATIO_ALL_SEQUENCES.md)
+        + [SUMMARY_STATIO_ALL_SEQUENCES](/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_ALL_SEQUENCES.md)
+        + [GLOBAL_STATIO_ALL_SEQUENCES](/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_ALL_SEQUENCES.md)
+        + [GLOBAL_STAT_DB_CU](/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STAT_DB_CU.md)
+        + [GLOBAL_STAT_SESSION_CU](/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STAT_SESSION_CU.md)
+      + Utility
+        + [REPLICATION_STAT](/reference-guide/schema/DBE_PERF/utility/REPLICATION_STAT.md)
+        + [GLOBAL_REPLICATION_STAT](/reference-guide/schema/DBE_PERF/utility/GLOBAL_REPLICATION_STAT.md)
+        + [REPLICATION_SLOTS](/reference-guide/schema/DBE_PERF/utility/REPLICATION_SLOTS.md)
+        + [GLOBAL_REPLICATION_SLOTS](/reference-guide/schema/DBE_PERF/utility/GLOBAL_REPLICATION_SLOTS.md)
+        + [BGWRITER_STAT](/reference-guide/schema/DBE_PERF/utility/BGWRITER_STAT.md)
+        + [GLOBAL_BGWRITER_STAT](/reference-guide/schema/DBE_PERF/utility/GLOBAL_BGWRITER_STAT.md)
+        + [GLOBAL_CKPT_STATUS](/reference-guide/schema/DBE_PERF/utility/GLOBAL_CKPT_STATUS.md)
+        + [GLOBAL_DOUBLE_WRITE_STATUS](/reference-guide/schema/DBE_PERF/utility/GLOBAL_DOUBLE_WRITE_STATUS.md)
+        + [GLOBAL_PAGEWRITER_STATUS](/reference-guide/schema/DBE_PERF/utility/GLOBAL_PAGEWRITER_STATUS.md)
+        + [GLOBAL_RECORD_RESET_TIME](/reference-guide/schema/DBE_PERF/utility/GLOBAL_RECORD_RESET_TIME.md)
+        + [GLOBAL_REDO_STATUS](/reference-guide/schema/DBE_PERF/utility/GLOBAL_REDO_STATUS.md)
+        + [GLOBAL_RECOVERY_STATUS](/reference-guide/schema/DBE_PERF/utility/GLOBAL_RECOVERY_STATUS.md)
+        + [CLASS_VITAL_INFO](/reference-guide/schema/DBE_PERF/utility/CLASS_VITAL_INFO.md)
+        + [USER_LOGIN](/reference-guide/schema/DBE_PERF/utility/USER_LOGIN.md)
+        + [SUMMARY_USER_LOGIN](/reference-guide/schema/DBE_PERF/utility/SUMMARY_USER_LOGIN.md)
+        + [GLOBAL_GET_BGWRITER_STATUS](/reference-guide/schema/DBE_PERF/utility/GLOBAL_GET_BGWRITER_STATUS.md)
+        + [GLOBAL_SINGLE_FLUSH_DW_STATUS](/reference-guide/schema/DBE_PERF/utility/GLOBAL_SINGLE_FLUSH_DW_STATUS.md)
+        + [GLOBAL_CANDIDATE_STATUS](/reference-guide/schema/DBE_PERF/utility/GLOBAL_CANDIDATE_STATUS.md)
+      + Lock
+        + [LOCKS](/reference-guide/schema/DBE_PERF/lock/LOCKS.md)
+        + [GLOBAL_LOCKS](/reference-guide/schema/DBE_PERF/lock/GLOBAL_LOCKS.md)
+      + Wait Events
+        + [WAIT_EVENTS](/reference-guide/schema/DBE_PERF/wait-events/WAIT_EVENTS.md)
+        + [GLOBAL_WAIT_EVENTS](/reference-guide/schema/DBE_PERF/wait-events/GLOBAL_WAIT_EVENTS.md)
+      + Configuration
+        + [CONFIG_SETTINGS](/reference-guide/schema/DBE_PERF/configuration/CONFIG_SETTINGS.md)
+        + [GLOBAL_CONFIG_SETTINGS](/reference-guide/schema/DBE_PERF/configuration/GLOBAL_CONFIG_SETTINGS.md)
+      + Operator
+        + [OPERATOR_HISTORY_TABLE](/reference-guide/schema/DBE_PERF/operator/OPERATOR_HISTORY_TABLE.md)
+        + [OPERATOR_HISTORY](/reference-guide/schema/DBE_PERF/operator/OPERATOR_HISTORY.md)
+        + [OPERATOR_RUNTIME](/reference-guide/schema/DBE_PERF/operator/OPERATOR_RUNTIME.md)
+        + [GLOBAL_OPERATOR_HISTORY](/reference-guide/schema/DBE_PERF/operator/GLOBAL_OPERATOR_HISTORY.md)
+        + [GLOBAL_OPERATOR_HISTORY_TABLE](/reference-guide/schema/DBE_PERF/operator/GLOBAL_OPERATOR_HISTORY_TABLE.md)
+        + [GLOBAL_OPERATOR_RUNTIME](/reference-guide/schema/DBE_PERF/operator/GLOBAL_OPERATOR_RUNTIME.md)
+      + Workload Manager
+        + [WLM_USER_RESOURCE_CONFIG](/reference-guide/schema/DBE_PERF/workload-manager/WLM_USER_RESOURCE_CONFIG.md)
+        + [WLM_USER_RESOURCE_RUNTIME](/reference-guide/schema/DBE_PERF/workload-manager/WLM_USER_RESOURCE_RUNTIME.md)
+      + Global Plancache
+        + [Overview](/reference-guide/schema/DBE_PERF/global-plancache/global-plancache-overview.md)
+        + [GLOBAL_PLANCACHE_STATUS](/reference-guide/schema/DBE_PERF/global-plancache/GLOBAL_PLANCACHE_STATUS.md)
+        + [GLOBAL_PLANCACHE_CLEAN](/reference-guide/schema/DBE_PERF/global-plancache/GLOBAL_PLANCACHE_CLEAN.md)
+      + RTO
+        + [global_rto_status](/reference-guide/schema/DBE_PERF/rto/global_rto_status.md)
+      + Appendix
+        + [Waiting status list](/reference-guide/schema/DBE_PERF/appendices/table-1.md)
+        + [List of wait events corresponding to lightweight locks](/reference-guide/schema/DBE_PERF/appendices/table-2.md)
+        + [List of wait events corresponding to I/Os](/reference-guide/schema/DBE_PERF/appendices/table-3.md)
+        + [List of wait events corresponding to transaction locks](/reference-guide/schema/DBE_PERF/appendices/table-4.md)
+        + [GS_WLM_SESSION_HISTORY columns](/reference-guide/schema/DBE_PERF/appendices/table-5.md)
+        + [GS_WLM_OPERATOR_INFO columns](/reference-guide/schema/DBE_PERF/appendices/table-6.md)
+    + DBE_PLDEBUGGER Schema
+      + [Overview](/reference-guide/schema/DBE_PLDEBUGGER-schema/overview-of-DBE_PLDEBUGGER-schema.md)
+      + [DBE_PLDEBUGGER.turn_on](/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.turn_on.md)
+      + [DBE_PLDEBUGGER.turn_off](/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.turn_off.md)
+      + [DBE_PLDEBUGGER.local_debug_server_info](/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.local_debug_server_info.md)
+      + [DBE_PLDEBUGGER.attach](/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.attach.md)
+      + [DBE_PLDEBUGGER.next](/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.next.md)
+      + [DBE_PLDEBUGGER.continue](/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.continue.md)
+      + [DBE_PLDEBUGGER.abort](/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.abort.md)
+      + [DBE_PLDEBUGGER.print_var](/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.print_var.md)
+      + [DBE_PLDEBUGGER.info_code](/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.info_code.md)
+      + [DBE_PLDEBUGGER.step](/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.step.md)
+      + [DBE_PLDEBUGGER.add_breakpoint](/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.add_breakpoint.md)
+      + [DBE_PLDEBUGGER.delete_breakpoint](/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.delete_breakpoint.md)
+      + [DBE_PLDEBUGGER.info_breakpoints](/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.info_breakpoints.md)
+      + [DBE_PLDEBUGGER.backtrace](/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.backtrace.md)
+      + [DBE_PLDEBUGGER.finish](/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.finish.md)
+      + [DBE_PLDEBUGGER.set_var](/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.set_var.md)
+    + DB4AI Schema
+      + [Overview](/reference-guide/schema/DB4AI-schema/overview-of-DB4AI-schema.md)
+      + [DB4AI.SNAPSHOT](/reference-guide/schema/DB4AI-schema/DB4AI.SNAPSHOT.md)
+      + [DB4AI.CREATE_SNAPSHOT](/reference-guide/schema/DB4AI-schema/DB4AI.CREATE_SNAPSHOT.md)
+      + [DB4AI.CREATE_SNAPSHOT_INTERNAL](/reference-guide/schema/DB4AI-schema/DB4AI.CREATE_SNAPSHOT_INTERNAL.md)
+      + [DB4AI.PREPARE_SNAPSHOT](/reference-guide/schema/DB4AI-schema/DB4AI.PREPARE_SNAPSHOT.md)
+      + [DB4AI.PREPARE_SNAPSHOT_INTERNAL](/reference-guide/schema/DB4AI-schema/DB4AI.PREPARE_SNAPSHOT_INTERNAL.md)
+      + [DB4AI.ARCHIVE_SNAPSHOT](/reference-guide/schema/DB4AI-schema/DB4AI.ARCHIVE_SNAPSHOT.md)
+      + [DB4AI.PUBLISH_SNAPSHOT](/reference-guide/schema/DB4AI-schema/DB4AI.PUBLISH_SNAPSHOT.md)
+      + [DB4AI.MANAGE_SNAPSHOT_INTERNAL](/reference-guide/schema/DB4AI-schema/DB4AI.MANAGE_SNAPSHOT_INTERNAL.md)
+      + [DB4AI.SAMPLE_SNAPSHOT](/reference-guide/schema/DB4AI-schema/DB4AI.SAMPLE_SNAPSHOT.md)
+      + [DB4AI.PURGE_SNAPSHOT](/reference-guide/schema/DB4AI-schema/DB4AI.PURGE_SNAPSHOT.md)
+      + [DB4AI.PURGE_SNAPSHOT_INTERNAL](/reference-guide/schema/DB4AI-schema/DB4AI.PURGE_SNAPSHOT_INTERNAL.md)
+  + Tool Reference
+    + [Tool Overview](/reference-guide/tool-reference/tool-overview.md)
+    + [Client Tool](/reference-guide/tool-reference/client-tool.md)
+    + Server Tools
+      + [gs_cgroup](/reference-guide/tool-reference/server-tools/0-gs_cgroup.md)
+      + [gs_check](/reference-guide/tool-reference/server-tools/1-gs_check.md)
+      + [gs_checkos](/reference-guide/tool-reference/server-tools/2-gs_checkos.md)
+      + [gs_checkperf](/reference-guide/tool-reference/server-tools/3-gs_checkperf.md)
+      + [gs_collector](/reference-guide/tool-reference/server-tools/4-gs_collector.md)
+      + [gs_dump](/reference-guide/tool-reference/server-tools/5-gs_dump.md)
+      + [gs_dumpall](/reference-guide/tool-reference/server-tools/6-gs_dumpall.md)
+      + [gs_guc](/reference-guide/tool-reference/server-tools/7-gs_guc.md)
+      + [gs_encrypt](/reference-guide/tool-reference/server-tools/7.1-gs_encrypt.md)
+      + [gs_om](/reference-guide/tool-reference/server-tools/8-gs_om.md)
+      + [gs_plan_simulator](/reference-guide/tool-reference/server-tools/8.1-gs_plan_simulator.md)
+      + [gs_restore](/reference-guide/tool-reference/server-tools/9-gs_restore.md)
+      + [gs_ssh](/reference-guide/tool-reference/server-tools/10-gs_ssh.md)
+    + Tools Used in the Internal System
+      + [gaussdb](/reference-guide/tool-reference/tools-used-in-the-internal-system/1-gaussdb.md)
+      + [gs_backup](/reference-guide/tool-reference/tools-used-in-the-internal-system/2-gs_backup.md)
+      + [gs_basebackup](/reference-guide/tool-reference/tools-used-in-the-internal-system/3-gs_basebackup.md)
+      + [gs_ctl](/reference-guide/tool-reference/tools-used-in-the-internal-system/4-gs_ctl.md)
+      + [gs_initdb](/reference-guide/tool-reference/tools-used-in-the-internal-system/5-gs_initdb.md)
+      + [gs_install](/reference-guide/tool-reference/tools-used-in-the-internal-system/6-gs_install.md)
+      + [gs_install_plugin](/reference-guide/tool-reference/tools-used-in-the-internal-system/gs_install_plugin.md)
+      + [gs_install_plugin_local](/reference-guide/tool-reference/tools-used-in-the-internal-system/gs_install_plugin_local.md)
+      + [gs_postuninstall](/reference-guide/tool-reference/tools-used-in-the-internal-system/7-gs_postuninstall.md)
+      + [gs_preinstall](/reference-guide/tool-reference/tools-used-in-the-internal-system/8-gs_preinstall.md)
+      + [gs_sshexkey](/reference-guide/tool-reference/tools-used-in-the-internal-system/9-gs_sshexkey.md)
+      + [gs_tar](/reference-guide/tool-reference/tools-used-in-the-internal-system/10-gs_tar.md)
+      + [gs_uninstall](/reference-guide/tool-reference/tools-used-in-the-internal-system/11-gs_uninstall.md)
+      + [gs_upgradectl](/reference-guide/tool-reference/tools-used-in-the-internal-system/12-gs_upgradectl.md)
+      + [gs_expansion](/reference-guide/tool-reference/tools-used-in-the-internal-system/13-gs_expansion.md)
+      + [gs_dropnode](/reference-guide/tool-reference/tools-used-in-the-internal-system/14-gs_dropnode.md)
+      + [gs_probackup](/reference-guide/tool-reference/tools-used-in-the-internal-system/15-gs_probackup.md)
+      + [gstrace](/reference-guide/tool-reference/tools-used-in-the-internal-system/16-gstrace.md)
+      + [kdb5_util](/reference-guide/tool-reference/tools-used-in-the-internal-system/17-kdb5_util.md)
+      + [kadmin.local](/reference-guide/tool-reference/tools-used-in-the-internal-system/18-kadmin-local.md)
+      + [kinit](/reference-guide/tool-reference/tools-used-in-the-internal-system/19-kinit.md)
+      + [klist](/reference-guide/tool-reference/tools-used-in-the-internal-system/20-klist.md)
+      + [krb5kdc](/reference-guide/tool-reference/tools-used-in-the-internal-system/21-krb5kdc.md)
+      + [kdestroy](/reference-guide/tool-reference/tools-used-in-the-internal-system/22-kdestroy.md)
+      + [pg_config](/reference-guide/tool-reference/tools-used-in-the-internal-system/23-pg_config.md)
+      + [pg_controldata](/reference-guide/tool-reference/tools-used-in-the-internal-system/24-pg_controldata.md)
+      + [pg_recvlogical](/reference-guide/tool-reference/tools-used-in-the-internal-system/24.1-pg_recvlogical.md)
+      + [pg_resetxlog](/reference-guide/tool-reference/tools-used-in-the-internal-system/25-pg_resetxlog.md)
+      + [pg_archivecleanup](/reference-guide/tool-reference/tools-used-in-the-internal-system/26-pg_archivecleanup.md)
+      + [pssh](/reference-guide/tool-reference/tools-used-in-the-internal-system/27-pssh.md)
+      + [pscp](/reference-guide/tool-reference/tools-used-in-the-internal-system/28-pscp.md)
+      + [transfer.py](/reference-guide/tool-reference/tools-used-in-the-internal-system/29-transfer.py.md)
+    + [FAQ](/reference-guide/tool-reference/FAQ.md)
+    + [System Catalogs and Views Supported by gs_collector](/reference-guide/tool-reference/system-catalogs-and-views-supported-by-gs_collector.md)
+  + Extension Reference
+    + [dblink](/reference-guide/oracle-plugins/dblink-user-guide.md)
+    + [orafce](/reference-guide/oracle-plugins/orafce-user-guide.md)
+    + [pg_bulkload](/reference-guide/oracle-plugins/pg_bulkload-user-guide.md)
+    + [pg_prewarm](/reference-guide/oracle-plugins/pg_prewarm-user-guide.md)
+    + [pg_repack](/reference-guide/oracle-plugins/pg_repack-user-guide.md)
+    + [pg_trgm](/reference-guide/oracle-plugins/pg_trgm-user-guide.md)
+    + [wal2json](/reference-guide/oracle-plugins/wal2json-user-guide.md)
+  + Error Code Reference
+    + [Description of SQL Error Codes](/reference-guide/error-code-reference/description-of-sql-error-codes.md)
+    + [Third-Party Library Error Codes](/reference-guide/error-code-reference/third-party-library-error-codes.md)
+    + [GAUSS-00001 - GAUSS-00100](/reference-guide/error-code-reference/1-GAUSS-00001-GAUSS-00100.md)
+    + [GAUSS-00101 - GAUSS-00200](/reference-guide/error-code-reference/2-GAUSS-00101-GAUSS-00200.md)
+    + [GAUSS 00201 - GAUSS 00300](/reference-guide/error-code-reference/3-GAUSS-00201-GAUSS-00300.md)
+    + [GAUSS 00301 - GAUSS 00400](/reference-guide/error-code-reference/4-GAUSS-00301-GAUSS-00400.md)
+    + [GAUSS 00401 - GAUSS 00500](/reference-guide/error-code-reference/5-GAUSS-00401-GAUSS-00500.md)
+    + [GAUSS 00501 - GAUSS 00600](/reference-guide/error-code-reference/6-GAUSS-00501-GAUSS-00600.md)
+    + [GAUSS 00601 - GAUSS 00700](/reference-guide/error-code-reference/7-GAUSS-00601-GAUSS-00700.md)
+    + [GAUSS 00701 - GAUSS 00800](/reference-guide/error-code-reference/8-GAUSS-00701-GAUSS-00800.md)
+    + [GAUSS 00801 - GAUSS 00900](/reference-guide/error-code-reference/9-GAUSS-00801-GAUSS-00900.md)
+    + [GAUSS 00901 - GAUSS 01000](/reference-guide/error-code-reference/10-GAUSS-00901-GAUSS-01000.md)
+    + [GAUSS 01001 - GAUSS 01100](/reference-guide/error-code-reference/11-GAUSS-01001-GAUSS-01100.md)
+    + [GAUSS 01101 - GAUSS 01200](/reference-guide/error-code-reference/12-GAUSS-01101-GAUSS-01200.md)
+    + [GAUSS 01201 - GAUSS 01300](/reference-guide/error-code-reference/13-GAUSS-01201-GAUSS-01300.md)
+    + [GAUSS 01301 - GAUSS 01400](/reference-guide/error-code-reference/14-GAUSS-01301-GAUSS-01400.md)
+    + [GAUSS 01401 - GAUSS 01500](/reference-guide/error-code-reference/15-GAUSS-01401-GAUSS-01500.md)
+    + [GAUSS 01501 - GAUSS 01600](/reference-guide/error-code-reference/16-GAUSS-01501-GAUSS-01600.md)
+    + [GAUSS 01601 - GAUSS 01700](/reference-guide/error-code-reference/17-GAUSS-01601-GAUSS-01700.md)
+    + [GAUSS 01701 - GAUSS 01800](/reference-guide/error-code-reference/18-GAUSS-01701-GAUSS-01800.md)
+    + [GAUSS 01801 - GAUSS 01900](/reference-guide/error-code-reference/19-GAUSS-01801-GAUSS-01900.md)
+    + [GAUSS 01901 - GAUSS 02000](/reference-guide/error-code-reference/20-GAUSS-01901-GAUSS-02000.md)
+    + [GAUSS 02001 - GAUSS 02100](/reference-guide/error-code-reference/21-GAUSS-02001-GAUSS-02100.md)
+    + [GAUSS 02101 - GAUSS 02200](/reference-guide/error-code-reference/22-GAUSS-02101-GAUSS-02200.md)
+    + [GAUSS 02201 - GAUSS 02300](/reference-guide/error-code-reference/23-GAUSS-02201-GAUSS-02300.md)
+    + [GAUSS 02301 - GAUSS 02400](/reference-guide/error-code-reference/24-GAUSS-02301-GAUSS-02400.md)
+    + [GAUSS 02401 - GAUSS 02500](/reference-guide/error-code-reference/25-GAUSS-02401-GAUSS-02500.md)
+    + [GAUSS 02501 - GAUSS 02600](/reference-guide/error-code-reference/26-GAUSS-02501-GAUSS-02600.md)
+    + [GAUSS 02601 - GAUSS 02700](/reference-guide/error-code-reference/27-GAUSS-02601-GAUSS-02700.md)
+    + [GAUSS 02701 - GAUSS 02800](/reference-guide/error-code-reference/28-GAUSS-02701-GAUSS-02800.md)
+    + [GAUSS 02801 - GAUSS 02900](/reference-guide/error-code-reference/29-GAUSS-02801-GAUSS-02900.md)
+    + [GAUSS 02901 - GAUSS 03000](/reference-guide/error-code-reference/30-GAUSS-02901-GAUSS-03000.md)
+    + [GAUSS 03001 - GAUSS 03100](/reference-guide/error-code-reference/31-GAUSS-03001-GAUSS-03100.md)
+    + [GAUSS 03101 - GAUSS 03200](/reference-guide/error-code-reference/32-GAUSS-03101-GAUSS-03200.md)
+    + [GAUSS 03201 - GAUSS 03300](/reference-guide/error-code-reference/33-GAUSS-03201-GAUSS-03300.md)
+    + [GAUSS 03301 - GAUSS 03400](/reference-guide/error-code-reference/34-GAUSS-03301-GAUSS-03400.md)
+    + [GAUSS 03401 - GAUSS 03500](/reference-guide/error-code-reference/35-GAUSS-03401-GAUSS-03500.md)
+    + [GAUSS 03501 - GAUSS 03600](/reference-guide/error-code-reference/36-GAUSS-03501-GAUSS-03600.md)
+    + [GAUSS 03601 - GAUSS 03700](/reference-guide/error-code-reference/37-GAUSS-03601-GAUSS-03700.md)
+    + [GAUSS 03701 - GAUSS 03800](/reference-guide/error-code-reference/38-GAUSS-03701-GAUSS-03800.md)
+    + [GAUSS 03801 - GAUSS 03900](/reference-guide/error-code-reference/39-GAUSS-03801-GAUSS-03900.md)
+    + [GAUSS 03901 - GAUSS 04000](/reference-guide/error-code-reference/40-GAUSS-03901-GAUSS-04000.md)
+    + [GAUSS 04001 - GAUSS 04100](/reference-guide/error-code-reference/41-GAUSS-04001-GAUSS-04100.md)
+    + [GAUSS 04101 - GAUSS 04200](/reference-guide/error-code-reference/42-GAUSS-04101-GAUSS-04200.md)
+    + [GAUSS 04201 - GAUSS 04300](/reference-guide/error-code-reference/43-GAUSS-04201-GAUSS-04300.md)
+    + [GAUSS 04301 - GAUSS 04400](/reference-guide/error-code-reference/44-GAUSS-04301-GAUSS-04400.md)
+    + [GAUSS 04401 - GAUSS 04500](/reference-guide/error-code-reference/45-GAUSS-04401-GAUSS-04500.md)
+    + [GAUSS 04501 - GAUSS 04600](/reference-guide/error-code-reference/46-GAUSS-04501-GAUSS-04600.md)
+    + [GAUSS 04601 - GAUSS 04700](/reference-guide/error-code-reference/47-GAUSS-04601-GAUSS-04700.md)
+    + [GAUSS 04701 - GAUSS 04800](/reference-guide/error-code-reference/48-GAUSS-04701-GAUSS-04800.md)
+    + [GAUSS 04801 - GAUSS 04900](/reference-guide/error-code-reference/49-GAUSS-04801-GAUSS-04900.md)
+    + [GAUSS 04901 - GAUSS 05000](/reference-guide/error-code-reference/50-GAUSS-04901-GAUSS-05000.md)
+    + [GAUSS 05001 - GAUSS 05100](/reference-guide/error-code-reference/51-GAUSS-05001-GAUSS-05100.md)
+    + [GAUSS 05101 - GAUSS 05200](/reference-guide/error-code-reference/52-GAUSS-05101-GAUSS-05200.md)
+    + [GAUSS 05201 - GAUSS 05300](/reference-guide/error-code-reference/53-GAUSS-05201-GAUSS-05300.md)
+    + [GAUSS 05301 - GAUSS 05400](/reference-guide/error-code-reference/54-GAUSS-05301-GAUSS-05400.md)
+    + [GAUSS 05401 - GAUSS 05500](/reference-guide/error-code-reference/55-GAUSS-05401-GAUSS-05500.md)
+    + [GAUSS 05501 - GAUSS 05600](/reference-guide/error-code-reference/56-GAUSS-05501-GAUSS-05600.md)
+    + [GAUSS 05601 - GAUSS 05700](/reference-guide/error-code-reference/57-GAUSS-05601-GAUSS-05700.md)
+    + [GAUSS 05701 - GAUSS 05800](/reference-guide/error-code-reference/58-GAUSS-05701-GAUSS-05800.md)
+    + [GAUSS 05801 - GAUSS 05900](/reference-guide/error-code-reference/59-GAUSS-05801-GAUSS-05900.md)
+    + [GAUSS 05901 - GAUSS 06000](/reference-guide/error-code-reference/60-GAUSS-05901-GAUSS-06000.md)
+    + [GAUSS 06001 - GAUSS 06100](/reference-guide/error-code-reference/61-GAUSS-06001-GAUSS-06100.md)
+    + [GAUSS 06101 - GAUSS 06200](/reference-guide/error-code-reference/62-GAUSS-06101-GAUSS-06200.md)
+    + [GAUSS 06201 - GAUSS 06300](/reference-guide/error-code-reference/63-GAUSS-06201-GAUSS-06300.md)
+    + [GAUSS 06301 - GAUSS 06400](/reference-guide/error-code-reference/64-GAUSS-06301-GAUSS-06400.md)
+    + [GAUSS 06401 - GAUSS 06500](/reference-guide/error-code-reference/65-GAUSS-06401-GAUSS-06500.md)
+    + [GAUSS 06501 - GAUSS 06600](/reference-guide/error-code-reference/66-GAUSS-06501-GAUSS-06600.md)
+    + [GAUSS 06601 - GAUSS 06700](/reference-guide/error-code-reference/67-GAUSS-06601-GAUSS-06700.md)
+    + [GAUSS 06701 - GAUSS 06800](/reference-guide/error-code-reference/68-GAUSS-06701-GAUSS-06800.md)
+    + [GAUSS 06801 - GAUSS 06900](/reference-guide/error-code-reference/69-GAUSS-06801-GAUSS-06900.md)
+    + [GAUSS 06901 - GAUSS 07000](/reference-guide/error-code-reference/70-GAUSS-06901-GAUSS-07000.md)
+    + [GAUSS 07001 - GAUSS 07100](/reference-guide/error-code-reference/71-GAUSS-07001-GAUSS-07100.md)
+    + [GAUSS 07101 - GAUSS 07200](/reference-guide/error-code-reference/72-GAUSS-07101-GAUSS-07200.md)
+    + [GAUSS 07201 - GAUSS 07300](/reference-guide/error-code-reference/73-GAUSS-07201-GAUSS-07300.md)
+    + [GAUSS 07301 - GAUSS 07400](/reference-guide/error-code-reference/74-GAUSS-07301-GAUSS-07400.md)
+    + [GAUSS 07401 - GAUSS 07480](/reference-guide/error-code-reference/75-GAUSS-07401-GAUSS-07480.md)
+    + [GAUSS 50000 - GAUSS 50999](/reference-guide/error-code-reference/76-GAUSS-50000-GAUSS-50999.md)
+    + [GAUSS 51000 - GAUSS 51999](/reference-guide/error-code-reference/77-GAUSS-51000-GAUSS-51999.md)
+    + [GAUSS 52000 - GAUSS 52999](/reference-guide/error-code-reference/78-GAUSS-52000-GAUSS-52999.md)
+    + [GAUSS 53000 - GAUSS 53699](/reference-guide/error-code-reference/79-GAUSS-53000-GAUSS-53699.md)
+  + Error Log Reference
+    + [Kernel Error Message](/reference-guide/error-log-reference/kernel-error-message.md)
++ [Source Code Parsing](/source-code-parsing.md)
++ FAQs
+  + [Product FAQs](/faqs/product-faqs.md)
+  + [Application Development FAQs](/faqs/application-development-faqs.md)
+  + [Deployment and Maintenance FAQs](/faqs/deployment-and-maintenance-faqs.md)
+  + [Upgrade FAQs](/faqs/upgrade-faqs.md)
+  + [High Availability FAQs](/faqs/high-availability-faqs.md)
+  + [Migration FAQs](/faqs/migration-faqs.md)
++ [Glossary](/glossary.md)
diff --git a/product/en/docs-mogdb/v3.0/toc_about.md b/product/en/docs-mogdb/v3.0/toc_about.md
new file mode 100644
index 0000000000000000000000000000000000000000..0a75bdd88fcf44b14efa389b31cfa912325819c5
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/toc_about.md
@@ -0,0 +1,24 @@
+<!-- markdownlint-disable MD007 -->
+<!-- markdownlint-disable MD041 -->
+# MogDB Documentation 3.0
+
+## About MogDB
+
++ [MogDB Introduction](/overview.md)
++ [Comparison Between MogDB and openGauss](/about-mogdb/MogDB-compared-to-openGauss.md)
++ [MogDB Release Notes](/about-mogdb/mogdb-release-notes.md)
++ High Availability and Performance
+  + [HA Test](/about-mogdb/test-report/ha/MogDB-ha-test-report.md)
+  + Performance Test
+    + [Performance Test Overview](/about-mogdb/test-report/performance/1-performance-test-overview.md)
+    + [Performance Test for MogDB on Kunpeng Servers](/about-mogdb/test-report/performance/2-mogdb-on-kunpeng-performance-test-report.md)
+    + [Performance Test for MogDB on x86 Servers](/about-mogdb/test-report/performance/3-mogdb-on-x86-performance-test-report.md)
++ Open Source Components
+  + [Docker-based MogDB](/about-mogdb/open-source-components/2-docker-based-mogdb.md)
+  + [compat-tools](/about-mogdb/open-source-components/compat-tools.md)
+  + [mogdb-monitor](/about-mogdb/open-source-components/mogdb-monitor.md)
+  + [wal2json](/about-mogdb/open-source-components/5-wal2json-extention-for-mogdb&opengauss.md)
+  + [mog_filedump](/about-mogdb/open-source-components/mog_filedump.md)
+  + [mog_xlogdump](/about-mogdb/open-source-components/mog_xlogdump.md)
++ [Usage Limitations](/about-mogdb/usage-limitations.md)
++ [Terms of Use](/about-mogdb/terms-of-use.md)
diff --git a/product/en/docs-mogdb/v3.0/toc_common-faults-and-identification.md b/product/en/docs-mogdb/v3.0/toc_common-faults-and-identification.md
new file mode 100644
index 0000000000000000000000000000000000000000..4a2ffc10fed5ffef41cb1e161b29c16bf0eb86e0
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/toc_common-faults-and-identification.md
@@ -0,0 +1,42 @@
+<!-- markdownlint-disable MD007 -->
+<!-- markdownlint-disable MD041 -->
+# MogDB Documentation 3.0
+
+## Common Faults and Identification
+
++ [Common Fault Locating Methods](/common-faults-and-identification/common-fault-locating-methods.md)
++ Common Fault Locating Cases
+  + Core Fault Locating
+    + [Core Dump Occurs due to Full Disk Space](/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/1-core-dump-occurs-due-to-full-disk-space.md)
+    + [Core Dump Occurs Due to Incorrect Settings of GUC Parameter log_directory](/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/2-core-dump-occurs-due-to-incorrect-settings-of-guc-parameter-log-directory.md)
+    + [Core Dump Occurs when RemoveIPC Is Enabled](/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/3-core-dump-occurs-when-removeipc-is-enabled.md)
+    + [Core Dump Occurs After Installation on x86](/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/4-core-dump-occurs-after-installation-on-x86.md)
+  + Permission/Session/Data Type Fault Location
+    + [Forcibly Terminating a Session](/common-faults-and-identification/common-fault-locating-cases/13-forcibly-terminating-a-session.md)
+    + [Different Data Is Displayed for the Same Table Queried By Multiple Users](/common-faults-and-identification/common-fault-locating-cases/19-different-data-is-displayed.md)
+    + [An Error Occurs During Integer Conversion](/common-faults-and-identification/common-fault-locating-cases/22-an-error-occurs-during-integer-conversion.md)
+  + Service/High Availability/Concurrency Fault Location
+    + [Standby Node in the Need Repair (WAL) State](/common-faults-and-identification/common-fault-locating-cases/3-standby-node-in-the-need-repair-state.md)
+    + [Service Startup Failure](/common-faults-and-identification/common-fault-locating-cases/5-service-startup-failure.md)
+    + [Primary Node Is Hung in Demoting During a Switchover](/common-faults-and-identification/common-fault-locating-cases/9-primary-node-is-hung-in-demoting.md)
+    + ["too many clients already" Is Reported or Threads Failed To Be Created in High Concurrency Scenarios](/common-faults-and-identification/common-fault-locating-cases/23-too-many-clients-already.md)
+  + Table/Partition Table Fault Location
+    + [Table Size Does not Change After VACUUM FULL Is Executed on the Table](/common-faults-and-identification/common-fault-locating-cases/17-table-size-does-not-change.md)
+    + [An Error Is Reported When the Table Partition Is Modified](/common-faults-and-identification/common-fault-locating-cases/18-an-error-is-reported-when-the-table-partition-is-modified.md)
+  + File System/Disk/Memory Fault Location
+    + [After You Run the du Command to Query Data File Size In the XFS File System, the Query Result Is Greater than the Actual File Size](/common-faults-and-identification/common-fault-locating-cases/7-after-you-run-the-du-command.md)
+    + [File Is Damaged in the XFS File System](/common-faults-and-identification/common-fault-locating-cases/8-file-is-damaged-in-the-xfs-file-system.md)
+    + [Insufficient Memory](/common-faults-and-identification/common-fault-locating-cases/4-insufficient-memory.md)
+    + ["Error:No space left on device" Is Displayed](/common-faults-and-identification/common-fault-locating-cases/6-error-no-space-left-on-device-is-displayed.md)
+    + [When the TPC-C is running and a disk to be injected is full, the TPC-C stops responding](/common-faults-and-identification/common-fault-locating-cases/2-when-the-tpcc-is-running.md)
+    + [Disk Space Usage Reaches the Threshold and the Database Becomes Read-only](/common-faults-and-identification/common-fault-locating-cases/10-disk-space-usage-reaches-the-threshold.md)
+  + SQL Fault Location
+    + ["Lock wait timeout" Is Displayed When a User Executes an SQL Statement](/common-faults-and-identification/common-fault-locating-cases/16-lock-wait-timeout-is-displayed.md)
+    + [Analyzing Whether a Query Statement Is Blocked](/common-faults-and-identification/common-fault-locating-cases/14-analyzing-whether-a-query-statement-is-blocked.md)
+    + [Low Query Efficiency](/common-faults-and-identification/common-fault-locating-cases/15-low-query-efficiency.md)
+    + [Slow Response to a Query Statement](/common-faults-and-identification/common-fault-locating-cases/11-slow-response-to-a-query-statement.md)
+    + [Analyzing the Status of a Query Statement](/common-faults-and-identification/common-fault-locating-cases/12-analyzing-the-status-of-a-query-statement.md)
+  + Index Fault Location
+    + [When a User Specifies Only an Index Name to Modify the Index, A Message Indicating That the Index Does Not Exist Is Displayed](/common-faults-and-identification/common-fault-locating-cases/20-when-a-user-specifies-only-an-index-name.md)
+    + [Reindexing Fails](/common-faults-and-identification/common-fault-locating-cases/21-reindexing-fails.md)
+    + [B-tree Index Faults](/common-faults-and-identification/common-fault-locating-cases/24-b-tree-index-faults.md)
diff --git a/product/en/docs-mogdb/v3.0/toc_datatypes-and-sql.md b/product/en/docs-mogdb/v3.0/toc_datatypes-and-sql.md
new file mode 100644
index 0000000000000000000000000000000000000000..03de82525f8a986a64263d03b4aa2d5fe1644516
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/toc_datatypes-and-sql.md
@@ -0,0 +1,275 @@
+<!-- markdownlint-disable MD007 -->
+<!-- markdownlint-disable MD041 -->
+
+# MogDB Documentation 3.0
+
+## Data Types and SQL
+
++ Supported Data Types
+  + [Numeric Types](/reference-guide/supported-data-types/1-numeric-data-types.md)
+  + [Monetary Types](/reference-guide/supported-data-types/2-monetary.md)
+  + [Boolean Types](/reference-guide/supported-data-types/3-boolean-data-types.md)
+  + [Enumerated Types](/reference-guide/supported-data-types/4.1-enumerated-types.md)
+  + [Character Types](/reference-guide/supported-data-types/4-character-data-types.md)
+  + [Binary Types](/reference-guide/supported-data-types/5-binary-data-types.md)
+  + [Date/Time Types](/reference-guide/supported-data-types/6-date-time-types.md)
+  + [Geometric](/reference-guide/supported-data-types/7-geometric.md)
+  + [Network Address Types](/reference-guide/supported-data-types/8-network-address.md)
+  + [Bit String Types](/reference-guide/supported-data-types/9-bit-string-types.md)
+  + [Text Search Types](/reference-guide/supported-data-types/10-text-search-types.md)
+  + [UUID](/reference-guide/supported-data-types/11-uuid-type.md)
+  + [JSON/JSONB Types](/reference-guide/supported-data-types/12-json-types.md)
+  + [HLL](/reference-guide/supported-data-types/13-HLL.md)
+  + [Array Types](/reference-guide/supported-data-types/13.0-array-types.md)
+  + [Range](/reference-guide/supported-data-types/13.1-range.md)
+  + [OID Types](/reference-guide/supported-data-types/14-object-identifier-types.md)
+  + [Pseudo-Types](/reference-guide/supported-data-types/15-pseudo-types.md)
+  + [Data Types Supported by Column-store Tables](/reference-guide/supported-data-types/16-data-types-supported-by-column-store-tables.md)
+  + [XML Types](/reference-guide/supported-data-types/17-xml-type.md)
+  + [Data Type Used by the Ledger Database](/reference-guide/supported-data-types/18-data-type-used-by-the-ledger-database.md)
++ SQL Syntax
+  + [ABORT](/reference-guide/sql-syntax/1-ABORT.md)
+  + [ALTER AGGREGATE](/reference-guide/sql-syntax/1.1-ALTER-AGGREGATE.md)
+  + [ALTER AUDIT POLICY](/reference-guide/sql-syntax/1.2-ALTER-AUDIT-POLICY.md)
+  + [ALTER DATABASE](/reference-guide/sql-syntax/2-ALTER-DATABASE.md)
+  + [ALTER DATA SOURCE](/reference-guide/sql-syntax/3-ALTER-DATA-SOURCE.md)
+  + [ALTER DEFAULT PRIVILEGES](/reference-guide/sql-syntax/4-ALTER-DEFAULT-PRIVILEGES.md)
+  + [ALTER DIRECTORY](/reference-guide/sql-syntax/5-ALTER-DIRECTORY.md)
+  + [ALTER EXTENSION](/reference-guide/sql-syntax/5.1-ALTER-EXTENSION.md)
+  + [ALTER FOREIGN TABLE](/reference-guide/sql-syntax/6-ALTER-FOREIGN-TABLE.md)
+  + [ALTER FUNCTION](/reference-guide/sql-syntax/7-ALTER-FUNCTION.md)
+  + [ALTER GROUP](/reference-guide/sql-syntax/8-ALTER-GROUP.md)
+  + [ALTER INDEX](/reference-guide/sql-syntax/9-ALTER-INDEX.md)
+  + [ALTER LANGUAGE](/reference-guide/sql-syntax/9.1-ALTER-LANGUAGE.md)
+  + [ALTER LARGE OBJECT](/reference-guide/sql-syntax/10-ALTER-LARGE-OBJECT.md)
+  + [ALTER MASKING POLICY](/reference-guide/sql-syntax/10.1-ALTER-MASKING-POLICY.md)
+  + [ALTER MATERIALIZED VIEW](/reference-guide/sql-syntax/11-ALTER-MATERIALIZED-VIEW.md)
+  + [ALTER OPERATOR](/reference-guide/sql-syntax/11.1-ALTER-OPERATOR.md)
+  + [ALTER RESOURCE LABEL](/reference-guide/sql-syntax/11.2-ALTER-RESOURCE-LABEL.md)
+  + [ALTER RESOURCE POOL](/reference-guide/sql-syntax/11.3-ALTER-RESOURCE-POOL.md)
+  + [ALTER ROLE](/reference-guide/sql-syntax/12-ALTER-ROLE.md)
+  + [ALTER ROW LEVEL SECURITY POLICY](/reference-guide/sql-syntax/13-ALTER-ROW-LEVEL-SECURITY-POLICY.md)
+  + [ALTER RULE](/reference-guide/sql-syntax/14-ALTER-RULE.md)
+  + [ALTER SCHEMA](/reference-guide/sql-syntax/15-ALTER-SCHEMA.md)
+  + [ALTER SEQUENCE](/reference-guide/sql-syntax/16-ALTER-SEQUENCE.md)
+  + [ALTER SERVER](/reference-guide/sql-syntax/17-ALTER-SERVER.md)
+  + [ALTER SESSION](/reference-guide/sql-syntax/18-ALTER-SESSION.md)
+  + [ALTER SYNONYM](/reference-guide/sql-syntax/19-ALTER-SYNONYM.md)
+  + [ALTER SYSTEM KILL SESSION](/reference-guide/sql-syntax/20-ALTER-SYSTEM-KILL-SESSION.md)
+  + [ALTER SYSTEM SET](/reference-guide/sql-syntax/21-ALTER-SYSTEM-SET.md)
+  + [ALTER TABLE](/reference-guide/sql-syntax/22-ALTER-TABLE.md)
+  + [ALTER TABLE PARTITION](/reference-guide/sql-syntax/23-ALTER-TABLE-PARTITION.md)
+  + [ALTER TABLE SUBPARTITION](/reference-guide/sql-syntax/23.1-ALTER-TABLE-SUBPARTITION.md)
+  + [ALTER TABLESPACE](/reference-guide/sql-syntax/24-ALTER-TABLESPACE.md)
+  + [ALTER TEXT SEARCH CONFIGURATION](/reference-guide/sql-syntax/25-ALTER-TEXT-SEARCH-CONFIGURATION.md)
+  + [ALTER TEXT SEARCH DICTIONARY](/reference-guide/sql-syntax/26-ALTER-TEXT-SEARCH-DICTIONARY.md)
+  + [ALTER TRIGGER](/reference-guide/sql-syntax/27-ALTER-TRIGGER.md)
+  + [ALTER TYPE](/reference-guide/sql-syntax/28-ALTER-TYPE.md)
+  + [ALTER USER](/reference-guide/sql-syntax/29-ALTER-USER.md)
+  + [ALTER USER MAPPING](/reference-guide/sql-syntax/30-ALTER-USER-MAPPING.md)
+  + [ALTER VIEW](/reference-guide/sql-syntax/31-ALTER-VIEW.md)
+  + [ANALYZE | ANALYSE](/reference-guide/sql-syntax/32-ANALYZE-ANALYSE.md)
+  + [BEGIN](/reference-guide/sql-syntax/33-BEGIN.md)
+  + [CALL](/reference-guide/sql-syntax/34-CALL.md)
+  + [CHECKPOINT](/reference-guide/sql-syntax/35-CHECKPOINT.md)
+  + [CLEAN CONNECTION](/reference-guide/sql-syntax/35.1-CLEAN-CONNECTION.md)
+  + [CLOSE](/reference-guide/sql-syntax/36-CLOSE.md)
+  + [CLUSTER](/reference-guide/sql-syntax/37-CLUSTER.md)
+  + [COMMENT](/reference-guide/sql-syntax/38-COMMENT.md)
+  + [COMMIT | END](/reference-guide/sql-syntax/39-COMMIT-END.md)
+  + [COMMIT PREPARED](/reference-guide/sql-syntax/40-COMMIT-PREPARED.md)
+  + [CONNECT BY](/reference-guide/sql-syntax/139-CONNECT-BY.md)
+  + [COPY](/reference-guide/sql-syntax/41-COPY.md)
+  + [CREATE AGGREGATE](/reference-guide/sql-syntax/41.1-CREATE-AGGREGATE.md)
+  + [CREATE AUDIT POLICY](/reference-guide/sql-syntax/41.2-CREATE-AUDIT-POLICY.md)
+  + [CREATE CAST](/reference-guide/sql-syntax/41.3-CREATE-CAST.md)
+  + [CREATE CLIENT MASTER KEY](/reference-guide/sql-syntax/42-CREATE-CLIENT-MASTER-KEY.md)
+  + [CREATE COLUMN ENCRYPTION KEY](/reference-guide/sql-syntax/43-CREATE-COLUMN-ENCRYPTION-KEY.md)
+  + [CREATE DATABASE](/reference-guide/sql-syntax/44-CREATE-DATABASE.md)
+  + [CREATE DATA SOURCE](/reference-guide/sql-syntax/45-CREATE-DATA-SOURCE.md)
+  + [CREATE DIRECTORY](/reference-guide/sql-syntax/46-CREATE-DIRECTORY.md)
+  + [CREATE EXTENSION](/reference-guide/sql-syntax/46.1-CREATE-EXTENSION.md)
+  + [CREATE FOREIGN TABLE](/reference-guide/sql-syntax/47-CREATE-FOREIGN-TABLE.md)
+  + [CREATE FUNCTION](/reference-guide/sql-syntax/48-CREATE-FUNCTION.md)
+  + [CREATE GROUP](/reference-guide/sql-syntax/49-CREATE-GROUP.md)
+  + [CREATE INCREMENTAL MATERIALIZED VIEW](/reference-guide/sql-syntax/49.1-CREATE-INCREMENTAL-MATERIALIZED-VIEW.md)
+  + [CREATE INDEX](/reference-guide/sql-syntax/50-CREATE-INDEX.md)
+  + [CREATE LANGUAGE](/reference-guide/sql-syntax/50.1-CREATE-LANGUAGE.md)
+  + [CREATE MASKING POLICY](/reference-guide/sql-syntax/50.2-CREATE-MASKING-POLICY.md)
+  + [CREATE MATERIALIZED VIEW](/reference-guide/sql-syntax/51-CREATE-MATERIALIZED-VIEW.md)
+  + [CREATE MODEL](/reference-guide/sql-syntax/50.3-CREATE-MODEL.md)
+  + [CREATE OPERATOR](/reference-guide/sql-syntax/51.1-CREATE-OPERATOR.md)
+  + [CREATE PACKAGE](/reference-guide/sql-syntax/51.2-CREATE-PACKAGE.md)
+  + [CREATE ROW LEVEL SECURITY POLICY](/reference-guide/sql-syntax/52-CREATE-ROW-LEVEL-SECURITY-POLICY.md)
+  + [CREATE PROCEDURE](/reference-guide/sql-syntax/53-CREATE-PROCEDURE.md)
+  + [CREATE RESOURCE LABEL](/reference-guide/sql-syntax/53.1-CREATE-RESOURCE-LABEL.md)
+  + [CREATE RESOURCE POOL](/reference-guide/sql-syntax/53.2-CREATE-RESOURCE-POOL.md)
+  + [CREATE ROLE](/reference-guide/sql-syntax/54-CREATE-ROLE.md)
+  + [CREATE RULE](/reference-guide/sql-syntax/55-CREATE-RULE.md)
+  + [CREATE SCHEMA](/reference-guide/sql-syntax/56-CREATE-SCHEMA.md)
+  + [CREATE SEQUENCE](/reference-guide/sql-syntax/57-CREATE-SEQUENCE.md)
+  + [CREATE SERVER](/reference-guide/sql-syntax/58-CREATE-SERVER.md)
+  + [CREATE SYNONYM](/reference-guide/sql-syntax/59-CREATE-SYNONYM.md)
+  + [CREATE TABLE](/reference-guide/sql-syntax/60-CREATE-TABLE.md)
+  + [CREATE TABLE AS](/reference-guide/sql-syntax/61-CREATE-TABLE-AS.md)
+  + [CREATE TABLE PARTITION](/reference-guide/sql-syntax/62-CREATE-TABLE-PARTITION.md)
+  + [CREATE TABLE SUBPARTITION](/reference-guide/sql-syntax/62.1-CREATE-TABLE-SUBPARTITION.md)
+  + [CREATE TABLESPACE](/reference-guide/sql-syntax/63-CREATE-TABLESPACE.md)
+  + [CREATE TEXT SEARCH CONFIGURATION](/reference-guide/sql-syntax/64-CREATE-TEXT-SEARCH-CONFIGURATION.md)
+  + [CREATE TEXT SEARCH DICTIONARY](/reference-guide/sql-syntax/65-CREATE-TEXT-SEARCH-DICTIONARY.md)
+  + [CREATE TRIGGER](/reference-guide/sql-syntax/66-CREATE-TRIGGER.md)
+  + [CREATE TYPE](/reference-guide/sql-syntax/67-CREATE-TYPE.md)
+  + [CREATE USER](/reference-guide/sql-syntax/68-CREATE-USER.md)
+  + [CREATE USER MAPPING](/reference-guide/sql-syntax/69-CREATE-USER-MAPPING.md)
+  + [CREATE VIEW](/reference-guide/sql-syntax/70-CREATE-VIEW.md)
+  + [CREATE WEAK PASSWORD DICTIONARY](/reference-guide/sql-syntax/70.1-CREATE-WEAK-PASSWORD-DICTIONARY.md)
+  + [CURSOR](/reference-guide/sql-syntax/71-CURSOR.md)
+  + [DEALLOCATE](/reference-guide/sql-syntax/72-DEALLOCATE.md)
+  + [DECLARE](/reference-guide/sql-syntax/73-DECLARE.md)
+  + [DELETE](/reference-guide/sql-syntax/74-DELETE.md)
+  + [DO](/reference-guide/sql-syntax/75-DO.md)
+  + [DROP AGGREGATE](/reference-guide/sql-syntax/75.1-DROP-AGGREGATE.md)
+  + [DROP AUDIT POLICY](/reference-guide/sql-syntax/75.2-DROP-AUDIT-POLICY.md)
+  + [DROP CAST](/reference-guide/sql-syntax/75.3-DROP-CAST.md)
+  + [DROP CLIENT MASTER KEY](/reference-guide/sql-syntax/76-DROP-CLIENT-MASTER-KEY.md)
+  + [DROP COLUMN ENCRYPTION KEY](/reference-guide/sql-syntax/77-DROP-COLUMN-ENCRYPTION-KEY.md)
+  + [DROP DATABASE](/reference-guide/sql-syntax/78-DROP-DATABASE.md)
+  + [DROP DATA SOURCE](/reference-guide/sql-syntax/79-DROP-DATA-SOURCE.md)
+  + [DROP DIRECTORY](/reference-guide/sql-syntax/80-DROP-DIRECTORY.md)
+  + [DROP EXTENSION](/reference-guide/sql-syntax/80.1-DROP-EXTENSION.md)
+  + [DROP FOREIGN TABLE](/reference-guide/sql-syntax/81-DROP-FOREIGN-TABLE.md)
+  + [DROP FUNCTION](/reference-guide/sql-syntax/82-DROP-FUNCTION.md)
+  + [DROP GROUP](/reference-guide/sql-syntax/83-DROP-GROUP.md)
+  + [DROP INDEX](/reference-guide/sql-syntax/84-DROP-INDEX.md)
+  + [DROP LANGUAGE](/reference-guide/sql-syntax/84.1-DROP-LANGUAGE.md)
+  + [DROP MASKING POLICY](/reference-guide/sql-syntax/84.2-DROP-MASKING-POLICY.md)
+  + [DROP MATERIALIZED VIEW](/reference-guide/sql-syntax/85-DROP-MATERIALIZED-VIEW.md)
+  + [DROP MODEL](/reference-guide/sql-syntax/84.3-DROP-MODEL.md)
+  + [DROP OPERATOR](/reference-guide/sql-syntax/85.1-DROP-OPERATOR.md)
+  + [DROP OWNED](/reference-guide/sql-syntax/86-DROP-OWNED.md)
+  + [DROP PACKAGE](/reference-guide/sql-syntax/86.3-DROP-PACKAGE.md)
+  + [DROP PROCEDURE](/reference-guide/sql-syntax/88-DROP-PROCEDURE.md)
+  + [DROP RESOURCE LABEL](/reference-guide/sql-syntax/86.1-DROP-RESOURCE-LABEL.md)
+  + [DROP RESOURCE POOL](/reference-guide/sql-syntax/86.2-DROP-RESOURCE-POOL.md)
+  + [DROP ROW LEVEL SECURITY POLICY](/reference-guide/sql-syntax/87-DROP-ROW-LEVEL-SECURITY-POLICY.md)
+  + [DROP ROLE](/reference-guide/sql-syntax/89-DROP-ROLE.md)
+  + [DROP RULE](/reference-guide/sql-syntax/90-DROP-RULE.md)
+  + [DROP SCHEMA](/reference-guide/sql-syntax/91-DROP-SCHEMA.md)
+  + [DROP SEQUENCE](/reference-guide/sql-syntax/92-DROP-SEQUENCE.md)
+  + [DROP SERVER](/reference-guide/sql-syntax/93-DROP-SERVER.md)
+  + [DROP SYNONYM](/reference-guide/sql-syntax/94-DROP-SYNONYM.md)
+  + [DROP TABLE](/reference-guide/sql-syntax/95-DROP-TABLE.md)
+  + [DROP TABLESPACE](/reference-guide/sql-syntax/96-DROP-TABLESPACE.md)
+  + [DROP TEXT SEARCH CONFIGURATION](/reference-guide/sql-syntax/97-DROP-TEXT-SEARCH-CONFIGURATION.md)
+  + [DROP TEXT SEARCH DICTIONARY](/reference-guide/sql-syntax/98-DROP-TEXT-SEARCH-DICTIONARY.md)
+  + [DROP TRIGGER](/reference-guide/sql-syntax/99-DROP-TRIGGER.md)
+  + [DROP TYPE](/reference-guide/sql-syntax/100-DROP-TYPE.md)
+  + [DROP USER](/reference-guide/sql-syntax/101-DROP-USER.md)
+  + [DROP USER MAPPING](/reference-guide/sql-syntax/102-DROP-USER-MAPPING.md)
+  + [DROP VIEW](/reference-guide/sql-syntax/103-DROP-VIEW.md)
+  + [DROP WEAK PASSWORD DICTIONARY](/reference-guide/sql-syntax/103.1-DROP-WEAK-PASSWORD-DICTIONARY.md)
+  + [EXECUTE](/reference-guide/sql-syntax/104-EXECUTE.md)
+  + [EXECUTE DIRECT](/reference-guide/sql-syntax/104.1-EXECUTE-DIRECT.md)
+  + [EXPLAIN](/reference-guide/sql-syntax/105-EXPLAIN.md)
+  + [EXPLAIN PLAN](/reference-guide/sql-syntax/106-EXPLAIN-PLAN.md)
+  + [FETCH](/reference-guide/sql-syntax/107-FETCH.md)
+  + [GRANT](/reference-guide/sql-syntax/108-GRANT.md)
+  + [INSERT](/reference-guide/sql-syntax/109-INSERT.md)
+  + [LOCK](/reference-guide/sql-syntax/110-LOCK.md)
+  + [MOVE](/reference-guide/sql-syntax/111-MOVE.md)
+  + [MERGE INTO](/reference-guide/sql-syntax/112-MERGE-INTO.md)
+  + [PREDICT BY](/reference-guide/sql-syntax/112.1-PREDICT-BY.md)
+  + [PREPARE](/reference-guide/sql-syntax/113-PREPARE.md)
+  + [PREPARE TRANSACTION](/reference-guide/sql-syntax/114-PREPARE-TRANSACTION.md)
+  + [PURGE](/reference-guide/sql-syntax/114.1-PURGE.md)
+  + [REASSIGN OWNED](/reference-guide/sql-syntax/115-REASSIGN-OWNED.md)
+  + [REFRESH INCREMENTAL MATERIALIZED VIEW](/reference-guide/sql-syntax/115.1-REFRESH-INCREMENTAL-MATERIALIZED-VIEW.md)
+  + [REFRESH MATERIALIZED VIEW](/reference-guide/sql-syntax/116-REFRESH-MATERIALIZED-VIEW.md)
+  + [REINDEX](/reference-guide/sql-syntax/117-REINDEX.md)
+  + [RELEASE SAVEPOINT](/reference-guide/sql-syntax/118-RELEASE-SAVEPOINT.md)
+  + [RESET](/reference-guide/sql-syntax/119-RESET.md)
+  + [REVOKE](/reference-guide/sql-syntax/120-REVOKE.md)
+  + [ROLLBACK](/reference-guide/sql-syntax/121-ROLLBACK.md)
+  + [ROLLBACK PREPARED](/reference-guide/sql-syntax/122-ROLLBACK-PREPARED.md)
+  + [ROLLBACK TO SAVEPOINT](/reference-guide/sql-syntax/123-ROLLBACK-TO-SAVEPOINT.md)
+  + [SAVEPOINT](/reference-guide/sql-syntax/124-SAVEPOINT.md)
+  + [SELECT](/reference-guide/sql-syntax/125-SELECT.md)
+  + [SELECT INTO](/reference-guide/sql-syntax/126-SELECT-INTO.md)
+  + [SET](/reference-guide/sql-syntax/127-SET.md)
+  + [SET CONSTRAINTS](/reference-guide/sql-syntax/128-SET-CONSTRAINTS.md)
+  + [SET ROLE](/reference-guide/sql-syntax/129-SET-ROLE.md)
+  + [SET SESSION AUTHORIZATION](/reference-guide/sql-syntax/130-SET-SESSION-AUTHORIZATION.md)
+  + [SET TRANSACTION](/reference-guide/sql-syntax/131-SET-TRANSACTION.md)
+  + [SHOW](/reference-guide/sql-syntax/132-SHOW.md)
+  + [SHUTDOWN](/reference-guide/sql-syntax/133-SHUTDOWN.md)
+  + [SNAPSHOT](/reference-guide/sql-syntax/133.1-SNAPSHOT.md)
+  + [START TRANSACTION](/reference-guide/sql-syntax/134-START-TRANSACTION.md)
+  + [TIMECAPSULE TABLE](/reference-guide/sql-syntax/134.1-TIMECAPSULE-TABLE.md)
+  + [TRUNCATE](/reference-guide/sql-syntax/135-TRUNCATE.md)
+  + [UPDATE](/reference-guide/sql-syntax/136-UPDATE.md)
+  + [VACUUM](/reference-guide/sql-syntax/137-VACUUM.md)
+  + [VALUES](/reference-guide/sql-syntax/138-VALUES.md)
++ SQL Reference
+  + [MogDB SQL](/reference-guide/sql-reference/1-mogdb-sql.md)
+  + [Keywords](/reference-guide/sql-reference/2-keywords.md)
+  + [Constant and Macro](/reference-guide/sql-reference/3-constant-and-macro.md)
+  + Expressions
+    + [Simple Expressions](/reference-guide/sql-reference/4-expressions/1-simple-expressions.md)
+    + [Condition Expressions](/reference-guide/sql-reference/4-expressions/2-condition-expressions.md)
+    + [Subquery Expressions](/reference-guide/sql-reference/4-expressions/3-subquery-expressions.md)
+    + [Array Expressions](/reference-guide/sql-reference/4-expressions/4-array-expressions.md)
+    + [Row Expressions](/reference-guide/sql-reference/4-expressions/5-row-expressions.md)
+  + Type Conversion
+    + [Overview](/reference-guide/sql-reference/5-type-conversion/1-type-conversion-overview.md)
+    + [Operators](/reference-guide/sql-reference/5-type-conversion/2-operators.md)
+    + [Functions](/reference-guide/sql-reference/5-type-conversion/3-functions.md)
+    + [Value Storage](/reference-guide/sql-reference/5-type-conversion/4-value-storage.md)
+    + [UNION, CASE, and Related Constructs](/reference-guide/sql-reference/5-type-conversion/5-union-case-and-related-constructs.md)
+  + Full Text Search
+    + Introduction
+      + [Full-Text Retrieval](/reference-guide/sql-reference/6-full-text-search/1-introduction/1-full-text-retrieval.md)
+      + [What Is a Document?](/reference-guide/sql-reference/6-full-text-search/1-introduction/2-what-is-a-document.md)
+      + [Basic Text Matching](/reference-guide/sql-reference/6-full-text-search/1-introduction/3-basic-text-matching.md)
+      + [Configurations](/reference-guide/sql-reference/6-full-text-search/1-introduction/4-configurations.md)
+    + Tables and Indexes
+      + [Searching a Table](/reference-guide/sql-reference/6-full-text-search/2-tables-and-indexes/1-searching-a-table.md)
+      + [Creating an Index](/reference-guide/sql-reference/6-full-text-search/2-tables-and-indexes/2-creating-an-index.md)
+      + [Constraints on Index Use](/reference-guide/sql-reference/6-full-text-search/2-tables-and-indexes/3-constraints-on-index-use.md)
+    + Controlling Text Search
+      + [Parsing Documents](/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/1-parsing-documents.md)
+      + [Parsing Queries](/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/2-parsing-queries.md)
+      + [Ranking Search Results](/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/3-ranking-search-results.md)
+      + [Highlighting Results](/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/4-highlighting-results.md)
+    + Additional Features
+      + [Manipulating tsvector](/reference-guide/sql-reference/6-full-text-search/4-additional-features/1-manipulating-tsvector.md)
+      + [Manipulating Queries](/reference-guide/sql-reference/6-full-text-search/4-additional-features/2-manipulating-queries.md)
+      + [Rewriting Queries](/reference-guide/sql-reference/6-full-text-search/4-additional-features/3-rewriting-queries.md)
+      + [Gathering Document Statistics](/reference-guide/sql-reference/6-full-text-search/4-additional-features/4-gathering-document-statistics.md)
+    + [Parser](/reference-guide/sql-reference/6-full-text-search/5-parser.md)
+    + Dictionaries
+      + [Overview](/reference-guide/sql-reference/6-full-text-search/6-dictionaries/1-dictionaries-overview.md)
+      + [Stop Words](/reference-guide/sql-reference/6-full-text-search/6-dictionaries/2-stop-words.md)
+      + [Simple Dictionary](/reference-guide/sql-reference/6-full-text-search/6-dictionaries/3-simple-dictionary.md)
+      + [Synonym Dictionary](/reference-guide/sql-reference/6-full-text-search/6-dictionaries/4-synonym-dictionary.md)
+      + [Thesaurus Dictionary](/reference-guide/sql-reference/6-full-text-search/6-dictionaries/5-thesaurus-dictionary.md)
+      + [Ispell Dictionary](/reference-guide/sql-reference/6-full-text-search/6-dictionaries/6-ispell-dictionary.md)
+      + [Snowball Dictionary](/reference-guide/sql-reference/6-full-text-search/6-dictionaries/7-snowball-dictionary.md)
+    + [Configuration Examples](/reference-guide/sql-reference/6-full-text-search/7-configuration-examples.md)
+    + Testing and Debugging Text Search
+      + [Testing a Configuration](/reference-guide/sql-reference/6-full-text-search/8-testing-and-debugging-text-search/1-testing-a-configuration.md)
+      + [Testing a Parser](/reference-guide/sql-reference/6-full-text-search/8-testing-and-debugging-text-search/2-testing-a-parser.md)
+      + [Testing a Dictionary](/reference-guide/sql-reference/6-full-text-search/8-testing-and-debugging-text-search/3-testing-a-dictionary.md)
+    + [Limitations](/reference-guide/sql-reference/6-full-text-search/9-limitations.md)
+  + [System Operation](/reference-guide/sql-reference/7-system-operation.md)
+  + [Controlling Transactions](/reference-guide/sql-reference/8-controlling-transactions.md)
+  + [DDL Syntax Overview](/reference-guide/sql-reference/9-ddl-syntax-overview.md)
+  + [DML Syntax Overview](/reference-guide/sql-reference/10-dml-syntax-overview.md)
+  + [DCL Syntax Overview](/reference-guide/sql-reference/11-dcl-syntax-overview.md)
+  + Appendix
+    + GIN Indexes
+      + [Introduction](/reference-guide/sql-reference/13-appendix/1-gin-indexes/1-introduction.md)
+      + [Scalability](/reference-guide/sql-reference/13-appendix/1-gin-indexes/2-scalability.md)
+      + [Implementation](/reference-guide/sql-reference/13-appendix/1-gin-indexes/3-implementation.md)
+      + [GIN Tips and Tricks](/reference-guide/sql-reference/13-appendix/1-gin-indexes/4-gin-tips-and-tricks.md)
+    + [Extended Functions](/reference-guide/sql-reference/13-appendix/2-extended-functions.md)
+    + [Extended Syntax](/reference-guide/sql-reference/13-appendix/3-extended-syntax.md)
diff --git a/product/en/docs-mogdb/v3.0/toc_dev.md b/product/en/docs-mogdb/v3.0/toc_dev.md
new file mode 100644
index 0000000000000000000000000000000000000000..60e398adbc4a5da40ff90623afac2cfd8214bf12
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/toc_dev.md
@@ -0,0 +1,246 @@
+<!-- markdownlint-disable MD007 -->
+<!-- markdownlint-disable MD041 -->
+# MogDB Documentation 3.0
+
+## Developer Guide
+
++ Development and Design Proposal
+  + [Overview](/developer-guide/development-and-design-proposal/overview-of-development-and-design-proposal.md)
+  + [Database Object Naming Conventions](/developer-guide/development-and-design-proposal/database-object-naming-conventions.md)
+  + Database Object Design
+    + [Database and Schema Design](/developer-guide/development-and-design-proposal/database-object-design/database-and-schema-design.md)
+    + [Table Design](/developer-guide/development-and-design-proposal/database-object-design/table-design.md)
+    + [Field Design](/developer-guide/development-and-design-proposal/database-object-design/field-design.md)
+    + [Constraint Design](/developer-guide/development-and-design-proposal/database-object-design/constraint-design.md)
+    + [View and Joined Table Design](/developer-guide/development-and-design-proposal/database-object-design/view-and-joined-table-design.md)
+  + Tool Interconnection
+    + [JDBC Configuration](/developer-guide/development-and-design-proposal/tool-interconnection/jdbc-configuration.md)
+  + [SQL Compilation](/developer-guide/development-and-design-proposal/sql-compilation.md)
++ Application Development Guide
+  + [Development Specifications](/developer-guide/dev/1-development-specifications.md)
+  + Development Based on JDBC
+    + [Overview](/developer-guide/dev/2-development-based-on-jdbc/1-development-based-on-jdbc-overview.md)
+    + [JDBC Package, Driver Class, and Environment Class](/developer-guide/dev/2-development-based-on-jdbc/2-jdbc-package-driver-class-and-environment-class.md)
+    + [Development Process](/developer-guide/dev/2-development-based-on-jdbc/3-development-process.md)
+    + [Loading the Driver](/developer-guide/dev/2-development-based-on-jdbc/4-loading-the-driver.md)
+    + [Connecting to a Database](/developer-guide/dev/2-development-based-on-jdbc/5-connecting-to-a-database.md)
+    + [Connecting to the Database (Using SSL)](/developer-guide/dev/2-development-based-on-jdbc/6-connecting-to-a-database-using-ssl.md)
+    + [Running SQL Statements](/developer-guide/dev/2-development-based-on-jdbc/7-running-sql-statements.md)
+    + [Processing Data in a Result Set](/developer-guide/dev/2-development-based-on-jdbc/8-processing-data-in-a-result-set.md)
+    + [Closing a Connection](/developer-guide/dev/2-development-based-on-jdbc/9-closing-a-connection.md)
+    + [Managing Logs](/developer-guide/dev/2-development-based-on-jdbc/8.1-log-management.md)
+    + [Example: Common Operations](/developer-guide/dev/2-development-based-on-jdbc/10-example-common-operations.md)
+    + [Example: Retrying SQL Queries for Applications](/developer-guide/dev/2-development-based-on-jdbc/11-example-retrying-sql-queries-for-applications.md)
+    + [Example: Importing and Exporting Data Through Local Files](/developer-guide/dev/2-development-based-on-jdbc/12-example-importing-and-exporting-data-through-local-files.md)
+    + [Example 2: Migrating Data from a MY Database to MogDB](/developer-guide/dev/2-development-based-on-jdbc/13-example-2-migrating-data-from-a-my-database-to-mogdb.md)
+    + [Example: Logic Replication Code](/developer-guide/dev/2-development-based-on-jdbc/14-example-logic-replication-code.md)
+    + [Example: Parameters for Connecting to the Database in Different Scenarios](/developer-guide/dev/2-development-based-on-jdbc/14.1-example-parameters-for-connecting-to-the-database-in-different-scenarios.md)
+    + JDBC API Reference
+      + [java.sql.Connection](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/1-java-sql-Connection.md)
+      + [java.sql.CallableStatement](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/2-java-sql-CallableStatement.md)
+      + [java.sql.DatabaseMetaData](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/3-java-sql-DatabaseMetaData.md)
+      + [java.sql.Driver](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/4-java-sql-Driver.md)
+      + [java.sql.PreparedStatement](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/5-java-sql-PreparedStatement.md)
+      + [java.sql.ResultSet](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/6-java-sql-ResultSet.md)
+      + [java.sql.ResultSetMetaData](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/7-java-sql-ResultSetMetaData.md)
+      + [java.sql.Statement](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/8-java-sql-Statement.md)
+      + [javax.sql.ConnectionPoolDataSource](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/9-javax-sql-ConnectionPoolDataSource.md)
+      + [javax.sql.DataSource](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/10-javax-sql-DataSource.md)
+      + [javax.sql.PooledConnection](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/11-javax-sql-PooledConnection.md)
+      + [javax.naming.Context](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/12-javax-naming-Context.md)
+      + [javax.naming.spi.InitialContextFactory](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/13-javax-naming-spi-InitialContextFactory.md)
+      + [CopyManager](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/14-CopyManager.md)
+  + Development Based on ODBC
+    + [Overview](/developer-guide/dev/3-development-based-on-odbc/1-development-based-on-odbc-overview.md)
+    + [ODBC Packages, Dependent Libraries, and Header Files](/developer-guide/dev/3-development-based-on-odbc/2-odbc-packages-dependent-libraries-and-header-files.md)
+    + [Configuring a Data Source in the Linux OS](/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md)
+    + [Development Process](/developer-guide/dev/3-development-based-on-odbc/4-development-process.md)
+    + [Example: Common Functions and Batch Binding](/developer-guide/dev/3-development-based-on-odbc/5-example-common-functions-and-batch-binding.md)
+    + [Typical Application Scenarios and Configurations](/developer-guide/dev/3-development-based-on-odbc/5.1-typical-application-scenarios-and-configurations.md)
+    + ODBC API Reference
+      + [Overview](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-0-odbc-overview.md)
+      + [SQLAllocEnv](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-1-SQLAllocEnv.md)
+      + [SQLAllocConnect](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-2-SQLAllocConnect.md)
+      + [SQLAllocHandle](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-3-SQLAllocHandle.md)
+      + [SQLAllocStmt](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-4-SQLAllocStmt.md)
+      + [SQLBindCol](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-5-SQLBindCol.md)
+      + [SQLBindParameter](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-6-SQLBindParameter.md)
+      + [SQLColAttribute](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-7-SQLColAttribute.md)
+      + [SQLConnect](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-8-SQLConnect.md)
+      + [SQLDisconnect](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-9-SQLDisconnect.md)
+      + [SQLExecDirect](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-10-SQLExecDirect.md)
+      + [SQLExecute](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-11-SQLExecute.md)
+      + [SQLFetch](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-12-SQLFetch.md)
+      + [SQLFreeStmt](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-13-SQLFreeStmt.md)
+      + [SQLFreeConnect](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-14-SQLFreeConnect.md)
+      + [SQLFreeHandle](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-15-SQLFreeHandle.md)
+      + [SQLFreeEnv](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-16-SQLFreeEnv.md)
+      + [SQLPrepare](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-17-SQLPrepare.md)
+      + [SQLGetData](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-18-SQLGetData.md)
+      + [SQLGetDiagRec](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-19-SQLGetDiagRec.md)
+      + [SQLSetConnectAttr](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-20-SQLSetConnectAttr.md)
+      + [SQLSetEnvAttr](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-21-SQLSetEnvAttr.md)
+      + [SQLSetStmtAttr](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-22-SQLSetStmtAttr.md)
+      + [Examples](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-23-Examples.md)
+  + Development Based on libpq
+    + [Development Based on libpq](/developer-guide/dev/4-development-based-on-libpq/1-development-based-on-libpq.md)
+    + libpq API Reference
+      + Database Connection Control Functions
+        + [Description](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/1-database-connection-control-functions-overview.md)
+        + [PQconnectdbParams](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/2-PQconnectdbParams.md)
+        + [PQconnectdb](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/3-PQconnectdb.md)
+        + [PQconninfoParse](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/4-PQconninfoParse.md)
+        + [PQconnectStart](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/5-PQconnectStart.md)
+        + [PQerrorMessage](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/6-PQerrorMessage.md)
+        + [PQsetdbLogin](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/7-PQsetdbLogin.md)
+        + [PQfinish](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/8-PQfinish.md)
+        + [PQreset](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/9-PQreset.md)
+        + [PQstatus](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/10-PQstatus.md)
+      + Database Statement Execution Functions
+        + [PQclear](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/1-PQclear.md)
+        + [PQexec](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/2-PQexec.md)
+        + [PQexecParams](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/3-PQexecParams.md)
+        + [PQexecParamsBatch](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/4-PQexecParamsBatch.md)
+        + [PQexecPrepared](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/5-PQexecPrepared.md)
+        + [PQexecPreparedBatch](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/6-PQexecPreparedBatch.md)
+        + [PQfname](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/7-PQfname.md)
+        + [PQgetvalue](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/8-PQgetvalue.md)
+        + [PQnfields](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/9-PQnfields.md)
+        + [PQntuples](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/10-PQntuples.md)
+        + [PQprepare](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/11-PQprepare.md)
+        + [PQresultStatus](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/12-PQresultStatus.md)
+      + Functions for Asynchronous Command Processing
+        + [Description](/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/1-functions-for-asynchronous-command-processing-overview.md)
+        + [PQsendQuery](/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/2-PQsendQuery.md)
+        + [PQsendQueryParams](/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/3-PQsendQueryParams.md)
+        + [PQsendPrepare](/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/4-PQsendPrepare.md)
+        + [PQsendQueryPrepared](/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/5-PQsendQueryPrepared.md)
+        + [PQflush](/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/6-PQflush.md)
+      + Functions for Canceling Queries in Progress
+        + [PQgetCancel](/developer-guide/dev/4-development-based-on-libpq/2-libpq/4-functions-for-canceling-queries-in-progress/1-PQgetCancel.md)
+        + [PQfreeCancel](/developer-guide/dev/4-development-based-on-libpq/2-libpq/4-functions-for-canceling-queries-in-progress/2-PQfreeCancel.md)
+        + [PQcancel](/developer-guide/dev/4-development-based-on-libpq/2-libpq/4-functions-for-canceling-queries-in-progress/3-PQcancel.md)
+      + [Example](/developer-guide/dev/4-development-based-on-libpq/2-libpq/5-libpq-example.md)
+      + [Connection Characters](/developer-guide/dev/4-development-based-on-libpq/2-libpq/6-connection-characters.md)
+  + Psycopg-Based Development
+    + [Psycopg-Based Development](/developer-guide/dev/4.1-psycopg-based-development/1-psycopg-based-development.md)
+    + [Psycopg Package](/developer-guide/dev/4.1-psycopg-based-development/2-psycopg-package.md)
+    + [Development Process](/developer-guide/dev/4.1-psycopg-based-development/3.1-development-process.md)
+    + [Loading a Driver](/developer-guide/dev/4.1-psycopg-based-development/4-loading-a-driver.md)
+    + [Connecting to a Database](/developer-guide/dev/4.1-psycopg-based-development/5.1-connecting-to-a-database.md)
+    + [Executing SQL Statements](/developer-guide/dev/4.1-psycopg-based-development/6-executing-sql-statements.md)
+    + [Processing the Result Set](/developer-guide/dev/4.1-psycopg-based-development/7-processing-the-result-set.md)
+    + [Closing the Connection](/developer-guide/dev/4.1-psycopg-based-development/8-closing-the-connection.md)
+    + [Connecting to the Database (Using SSL)](/developer-guide/dev/4.1-psycopg-based-development/9-connecting-to-the-database-using-ssl.md)
+    + [Examples: Common Operations](/developer-guide/dev/4.1-psycopg-based-development/10.1-example-common-operations.md)
+    + Psycopg API Reference
+      + [psycopg2.connect()](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/1-psycopg2-connect.md)
+      + [connection.cursor()](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/2-connection-cursor.md)
+      + [cursor.execute(query,vars_list)](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/3-cursor-execute-query-vars-list.md)
+      + [curosr.executemany(query,vars_list)](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/4-curosr-executemany-query-vars-list.md)
+      + [connection.commit()](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/5-connection-commit.md)
+      + [connection.rollback()](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/6-connection-rollback.md)
+      + [cursor.fetchone()](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/7-cursor-fetchone.md)
+      + [cursor.fetchall()](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/8-cursor-fetchall.md)
+      + [cursor.close()](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/9-cursor-close.md)
+      + [connection.close()](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/10-connection-close.md)
+  + [Commissioning](/developer-guide/dev/5-commissioning.md)
+  + [Appendices](/developer-guide/dev/6-appendix.md)
++ [Stored Procedure](/developer-guide/1-1-stored-procedure.md)
++ [User Defined Functions](/developer-guide/user-defined-functions.md)
++ PL/pgSQL-SQL Procedural Language
+  + [Overview of PL/pgSQL Functions](/developer-guide/plpgsql/1-1-plpgsql-overview.md)
+  + [Data Types](/developer-guide/plpgsql/1-2-data-types.md)
+  + [Data Type Conversion](/developer-guide/plpgsql/1-3-data-type-conversion.md)
+  + [Arrays and Records](/developer-guide/plpgsql/1-4-arrays-and-records.md)
+  + [DECLARE Syntax](/developer-guide/plpgsql/1-5-declare-syntax.md)
+  + [Basic Statements](/developer-guide/plpgsql/1-6-basic-statements.md)
+  + [Dynamic Statements](/developer-guide/plpgsql/1-7-dynamic-statements.md)
+  + [Control Statements](/developer-guide/plpgsql/1-8-control-statements.md)
+  + [Transaction Management](/developer-guide/plpgsql/1-9-transaction-management.md)
+  + [Other Statements](/developer-guide/plpgsql/1-10-other-statements.md)
+  + [Cursors](/developer-guide/plpgsql/1-11-cursors.md)
+  + [PKG_SERVICE API](/developer-guide/plpgsql/1-14-pkg-service.md)
+  + [Retry Management](/developer-guide/plpgsql/1-12-retry-management.md)
+  + [Debugging](/developer-guide/plpgsql/1-13-debugging.md)
++ Scheduled Jobs
+  + [PKG_SERVICE API](/developer-guide/scheduled-jobs/pkg-service.md)
++ Autonomous Transaction
+  + [Introduction](/developer-guide/autonomous-transaction/1-introduction-to-autonomous-transaction.md)
+  + [Stored Procedure Supporting Autonomous Transaction](/developer-guide/autonomous-transaction/3-stored-procedure-supporting-autonomous-transaction.md)
+  + [Anonymous Block Supporting Autonomous Transaction](/developer-guide/autonomous-transaction/anonymous-block-supporting-autonomous-transaction.md)
+  + [Function Supporting Autonomous Transaction](/developer-guide/autonomous-transaction/2-function-supporting-autonomous-transaction.md)
+  + [Restrictions](/developer-guide/autonomous-transaction/4-restrictions.md)
++ Logical Replication
+  + Logical Decoding
+    + [Overview](/developer-guide/logical-replication/1-logical-decoding.md)
+    + [Logical Decoding by SQL Function Interfaces](/developer-guide/logical-replication/2-logical-decoding-by-sql-function-interfaces.md)
++ Foreign Data Wrapper
+  + [Introduction](/developer-guide/foreign-data-wrapper/fdw-introduction.md)
+  + [oracle_fdw](/developer-guide/foreign-data-wrapper/1-oracle_fdw.md)
+  + [mysql_fdw](/developer-guide/foreign-data-wrapper/2-mysql_fdw.md)
+  + [postgres_fdw](/developer-guide/foreign-data-wrapper/3-postgres_fdw.md)
+  + [file_fdw](/developer-guide/foreign-data-wrapper/file_fdw.md)
+  + [dblink](/developer-guide/foreign-data-wrapper/dblink.md)
++ Materialized View
+  + [Materialized View Overview](/developer-guide/materialized-view/1-materialized-view-overview.md)
+  + Full Materialized View
+    + [Overview](/developer-guide/materialized-view/2-full-materialized-view/1-full-materialized-view-overview.md)
+    + [Usage](/developer-guide/materialized-view/2-full-materialized-view/2-full-materialized-view-usage.md)
+    + [Support and Constraints](/developer-guide/materialized-view/2-full-materialized-view/3-full-materialized-view-support-and-constraints.md)
+  + Incremental Materialized View
+    + [Overview](/developer-guide/materialized-view/3-incremental-materialized-view/1-incremental-materialized-view-overview.md)
+    + [Usage](/developer-guide/materialized-view/3-incremental-materialized-view/2-incremental-materialized-view-usage.md)
+    + [Support and Constraints](/developer-guide/materialized-view/3-incremental-materialized-view/3-incremental-materialized-view-support-and-constraints.md)
++ AI Features
+  + [Overview](/developer-guide/AI-features/1-AI-features-overview.md)
+  + Predictor: AI Query Time Forecasting
+    + [Overview](/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-1-ai-query-time-forecasting-overview.md)
+    + [Environment Deployment](/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-2-environment-deployment.md)
+    + [Usage Guide](/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-3-usage-guide.md)
+    + [Best Practices](/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-4-best-practices.md)
+    + [FAQs](/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-5-faqs.md)
+  + X-Tuner: Parameter Optimization and Diagnosis
+    + [Overview](/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-1-x-tuner-overview.md)
+    + [Preparations](/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-2-preparations.md)
+    + [Examples](/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-3-examples.md)
+    + [Obtaining Help Information](/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-4-obtaining-help-information.md)
+    + [Command Reference](/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-5-command-reference.md)
+    + [Troubleshooting](/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-6-Troubleshooting.md)
+  + SQLdiag: Slow SQL Discovery
+    + [Overview](/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-1-overview.md)
+    + [Usage Guide](/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-2-usage-guide.md)
+    + [Obtaining Help Information](/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-3-obtaining-help-information.md)
+    + [Command Reference](/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-4-command-reference.md)
+    + [Troubleshooting](/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-5-troubleshooting.md)
+  + A-Detection: Status Monitoring
+    + [Overview](/developer-guide/AI-features/5-a-detection-status-monitoring/5-1-overview.md)
+    + [Preparations](/developer-guide/AI-features/5-a-detection-status-monitoring/5-2-preparations.md)
+    + [Adding Monitoring Parameters](/developer-guide/AI-features/5-a-detection-status-monitoring/5-3-adding-monitoring-parameters.md)
+    + [Obtaining Help Information](/developer-guide/AI-features/5-a-detection-status-monitoring/5-4-obtaining-help-information.md)
+    + [Examples](/developer-guide/AI-features/5-a-detection-status-monitoring/5-6-examples.md)
+    + [Command Reference](/developer-guide/AI-features/5-a-detection-status-monitoring/5-5-command-reference.md)
+    + [AI_SERVER](/developer-guide/AI-features/5-a-detection-status-monitoring/5-7-ai-server.md)
+    + [AI_MANAGER](/developer-guide/AI-features/5-a-detection-status-monitoring/5-8-ai-manager.md)
+  + Index-advisor: Index Recommendation
+    + [Single-query Index Recommendation](/developer-guide/AI-features/6-index-advisor-index-recommendation/6-1-single-query-index-recommendation.md)
+    + [Virtual Index](/developer-guide/AI-features/6-index-advisor-index-recommendation/6-2-virtual-index.md)
+    + [Workload-level Index Recommendation](/developer-guide/AI-features/6-index-advisor-index-recommendation/6-3-workload-level-index-recommendation.md)
+  + DeepSQL
+    + [Overview](/developer-guide/AI-features/7-deepsql/7-1-overview.md)
+    + [Environment Deployment](/developer-guide/AI-features/7-deepsql/7-2-environment-deployment.md)
+    + [Usage Guide](/developer-guide/AI-features/7-deepsql/7-3-usage-guide.md)
+    + [Best Practices](/developer-guide/AI-features/7-deepsql/7-4-best-practices.md)
+    + [Troubleshooting](/developer-guide/AI-features/7-deepsql/7-5-troubleshooting.md)
+  + AI-Native Database (DB4AI)
+    + [Overview](/developer-guide/AI-features/8-db4ai/8-1-overview.md)
+    + [DB4AI-Snapshots for Data Version Management](/developer-guide/AI-features/8-db4ai/8-2-db4ai-snapshots-for-data-version-management.md)
+    + [DB4AI-Query for Model Training and Prediction](/developer-guide/AI-features/8-db4ai/8-3-db4ai-query-for-model-training-and-prediction.md)
+    + [PL/Python Fenced Mode](/developer-guide/AI-features/8-db4ai/8-4-pl-python-fenced-mode.md)
++ Resource Load Management
+  + [Overview](/developer-guide/resource-load-management/resource-load-management-overview.md)
+  + Resource Management Preparation
+    + [Planning Resources](/developer-guide/resource-load-management/resource-management-preparation/planning-resources.md)
+    + [Enabling Resource Load Management](/developer-guide/resource-load-management/resource-management-preparation/enabling-resource-load-management.md)
+    + [Setting a Cgroup](/developer-guide/resource-load-management/resource-management-preparation/setting-a-cgroup.md)
+    + [Creating a Resource Pool](/developer-guide/resource-load-management/resource-management-preparation/creating-a-resource-pool.md)
diff --git a/product/en/docs-mogdb/v3.0/toc_error.md b/product/en/docs-mogdb/v3.0/toc_error.md
new file mode 100644
index 0000000000000000000000000000000000000000..320dec9edeacad872657066aa2cbf591e079c79b
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/toc_error.md
@@ -0,0 +1,89 @@
+<!-- markdownlint-disable MD007 -->
+<!-- markdownlint-disable MD041 -->
+# MogDB Documentation 3.0
+
+## Error Messages
+
++ [Description of SQL Error Codes](/reference-guide/error-code-reference/description-of-sql-error-codes.md)
++ [Third-Party Library Error Codes](/reference-guide/error-code-reference/third-party-library-error-codes.md)
++ [GAUSS-00001 - GAUSS-00100](/reference-guide/error-code-reference/1-GAUSS-00001-GAUSS-00100.md)
++ [GAUSS-00101 - GAUSS-00200](/reference-guide/error-code-reference/2-GAUSS-00101-GAUSS-00200.md)
++ [GAUSS 00201 - GAUSS 00300](/reference-guide/error-code-reference/3-GAUSS-00201-GAUSS-00300.md)
++ [GAUSS 00301 - GAUSS 00400](/reference-guide/error-code-reference/4-GAUSS-00301-GAUSS-00400.md)
++ [GAUSS 00401 - GAUSS 00500](/reference-guide/error-code-reference/5-GAUSS-00401-GAUSS-00500.md)
++ [GAUSS 00501 - GAUSS 00600](/reference-guide/error-code-reference/6-GAUSS-00501-GAUSS-00600.md)
++ [GAUSS 00601 - GAUSS 00700](/reference-guide/error-code-reference/7-GAUSS-00601-GAUSS-00700.md)
++ [GAUSS 00701 - GAUSS 00800](/reference-guide/error-code-reference/8-GAUSS-00701-GAUSS-00800.md)
++ [GAUSS 00801 - GAUSS 00900](/reference-guide/error-code-reference/9-GAUSS-00801-GAUSS-00900.md)
++ [GAUSS 00901 - GAUSS 01000](/reference-guide/error-code-reference/10-GAUSS-00901-GAUSS-01000.md)
++ [GAUSS 01001 - GAUSS 01100](/reference-guide/error-code-reference/11-GAUSS-01001-GAUSS-01100.md)
++ [GAUSS 01101 - GAUSS 01200](/reference-guide/error-code-reference/12-GAUSS-01101-GAUSS-01200.md)
++ [GAUSS 01201 - GAUSS 01300](/reference-guide/error-code-reference/13-GAUSS-01201-GAUSS-01300.md)
++ [GAUSS 01301 - GAUSS 01400](/reference-guide/error-code-reference/14-GAUSS-01301-GAUSS-01400.md)
++ [GAUSS 01401 - GAUSS 01500](/reference-guide/error-code-reference/15-GAUSS-01401-GAUSS-01500.md)
++ [GAUSS 01501 - GAUSS 01600](/reference-guide/error-code-reference/16-GAUSS-01501-GAUSS-01600.md)
++ [GAUSS 01601 - GAUSS 01700](/reference-guide/error-code-reference/17-GAUSS-01601-GAUSS-01700.md)
++ [GAUSS 01701 - GAUSS 01800](/reference-guide/error-code-reference/18-GAUSS-01701-GAUSS-01800.md)
++ [GAUSS 01801 - GAUSS 01900](/reference-guide/error-code-reference/19-GAUSS-01801-GAUSS-01900.md)
++ [GAUSS 01901 - GAUSS 02000](/reference-guide/error-code-reference/20-GAUSS-01901-GAUSS-02000.md)
++ [GAUSS 02001 - GAUSS 02100](/reference-guide/error-code-reference/21-GAUSS-02001-GAUSS-02100.md)
++ [GAUSS 02101 - GAUSS 02200](/reference-guide/error-code-reference/22-GAUSS-02101-GAUSS-02200.md)
++ [GAUSS 02201 - GAUSS 02300](/reference-guide/error-code-reference/23-GAUSS-02201-GAUSS-02300.md)
++ [GAUSS 02301 - GAUSS 02400](/reference-guide/error-code-reference/24-GAUSS-02301-GAUSS-02400.md)
++ [GAUSS 02401 - GAUSS 02500](/reference-guide/error-code-reference/25-GAUSS-02401-GAUSS-02500.md)
++ [GAUSS 02501 - GAUSS 02600](/reference-guide/error-code-reference/26-GAUSS-02501-GAUSS-02600.md)
++ [GAUSS 02601 - GAUSS 02700](/reference-guide/error-code-reference/27-GAUSS-02601-GAUSS-02700.md)
++ [GAUSS 02701 - GAUSS 02800](/reference-guide/error-code-reference/28-GAUSS-02701-GAUSS-02800.md)
++ [GAUSS 02801 - GAUSS 02900](/reference-guide/error-code-reference/29-GAUSS-02801-GAUSS-02900.md)
++ [GAUSS 02901 - GAUSS 03000](/reference-guide/error-code-reference/30-GAUSS-02901-GAUSS-03000.md)
++ [GAUSS 03001 - GAUSS 03100](/reference-guide/error-code-reference/31-GAUSS-03001-GAUSS-03100.md)
++ [GAUSS 03101 - GAUSS 03200](/reference-guide/error-code-reference/32-GAUSS-03101-GAUSS-03200.md)
++ [GAUSS 03201 - GAUSS 03300](/reference-guide/error-code-reference/33-GAUSS-03201-GAUSS-03300.md)
++ [GAUSS 03301 - GAUSS 03400](/reference-guide/error-code-reference/34-GAUSS-03301-GAUSS-03400.md)
++ [GAUSS 03401 - GAUSS 03500](/reference-guide/error-code-reference/35-GAUSS-03401-GAUSS-03500.md)
++ [GAUSS 03501 - GAUSS 03600](/reference-guide/error-code-reference/36-GAUSS-03501-GAUSS-03600.md)
++ [GAUSS 03601 - GAUSS 03700](/reference-guide/error-code-reference/37-GAUSS-03601-GAUSS-03700.md)
++ [GAUSS 03701 - GAUSS 03800](/reference-guide/error-code-reference/38-GAUSS-03701-GAUSS-03800.md)
++ [GAUSS 03801 - GAUSS 03900](/reference-guide/error-code-reference/39-GAUSS-03801-GAUSS-03900.md)
++ [GAUSS 03901 - GAUSS 04000](/reference-guide/error-code-reference/40-GAUSS-03901-GAUSS-04000.md)
++ [GAUSS 04001 - GAUSS 04100](/reference-guide/error-code-reference/41-GAUSS-04001-GAUSS-04100.md)
++ [GAUSS 04101 - GAUSS 04200](/reference-guide/error-code-reference/42-GAUSS-04101-GAUSS-04200.md)
++ [GAUSS 04201 - GAUSS 04300](/reference-guide/error-code-reference/43-GAUSS-04201-GAUSS-04300.md)
++ [GAUSS 04301 - GAUSS 04400](/reference-guide/error-code-reference/44-GAUSS-04301-GAUSS-04400.md)
++ [GAUSS 04401 - GAUSS 04500](/reference-guide/error-code-reference/45-GAUSS-04401-GAUSS-04500.md)
++ [GAUSS 04501 - GAUSS 04600](/reference-guide/error-code-reference/46-GAUSS-04501-GAUSS-04600.md)
++ [GAUSS 04601 - GAUSS 04700](/reference-guide/error-code-reference/47-GAUSS-04601-GAUSS-04700.md)
++ [GAUSS 04701 - GAUSS 04800](/reference-guide/error-code-reference/48-GAUSS-04701-GAUSS-04800.md)
++ [GAUSS 04801 - GAUSS 04900](/reference-guide/error-code-reference/49-GAUSS-04801-GAUSS-04900.md)
++ [GAUSS 04901 - GAUSS 05000](/reference-guide/error-code-reference/50-GAUSS-04901-GAUSS-05000.md)
++ [GAUSS 05001 - GAUSS 05100](/reference-guide/error-code-reference/51-GAUSS-05001-GAUSS-05100.md)
++ [GAUSS 05101 - GAUSS 05200](/reference-guide/error-code-reference/52-GAUSS-05101-GAUSS-05200.md)
++ [GAUSS 05201 - GAUSS 05300](/reference-guide/error-code-reference/53-GAUSS-05201-GAUSS-05300.md)
++ [GAUSS 05301 - GAUSS 05400](/reference-guide/error-code-reference/54-GAUSS-05301-GAUSS-05400.md)
++ [GAUSS 05401 - GAUSS 05500](/reference-guide/error-code-reference/55-GAUSS-05401-GAUSS-05500.md)
++ [GAUSS 05501 - GAUSS 05600](/reference-guide/error-code-reference/56-GAUSS-05501-GAUSS-05600.md)
++ [GAUSS 05601 - GAUSS 05700](/reference-guide/error-code-reference/57-GAUSS-05601-GAUSS-05700.md)
++ [GAUSS 05701 - GAUSS 05800](/reference-guide/error-code-reference/58-GAUSS-05701-GAUSS-05800.md)
++ [GAUSS 05801 - GAUSS 05900](/reference-guide/error-code-reference/59-GAUSS-05801-GAUSS-05900.md)
++ [GAUSS 05901 - GAUSS 06000](/reference-guide/error-code-reference/60-GAUSS-05901-GAUSS-06000.md)
++ [GAUSS 06001 - GAUSS 06100](/reference-guide/error-code-reference/61-GAUSS-06001-GAUSS-06100.md)
++ [GAUSS 06101 - GAUSS 06200](/reference-guide/error-code-reference/62-GAUSS-06101-GAUSS-06200.md)
++ [GAUSS 06201 - GAUSS 06300](/reference-guide/error-code-reference/63-GAUSS-06201-GAUSS-06300.md)
++ [GAUSS 06301 - GAUSS 06400](/reference-guide/error-code-reference/64-GAUSS-06301-GAUSS-06400.md)
++ [GAUSS 06401 - GAUSS 06500](/reference-guide/error-code-reference/65-GAUSS-06401-GAUSS-06500.md)
++ [GAUSS 06501 - GAUSS 06600](/reference-guide/error-code-reference/66-GAUSS-06501-GAUSS-06600.md)
++ [GAUSS 06601 - GAUSS 06700](/reference-guide/error-code-reference/67-GAUSS-06601-GAUSS-06700.md)
++ [GAUSS 06701 - GAUSS 06800](/reference-guide/error-code-reference/68-GAUSS-06701-GAUSS-06800.md)
++ [GAUSS 06801 - GAUSS 06900](/reference-guide/error-code-reference/69-GAUSS-06801-GAUSS-06900.md)
++ [GAUSS 06901 - GAUSS 07000](/reference-guide/error-code-reference/70-GAUSS-06901-GAUSS-07000.md)
++ [GAUSS 07001 - GAUSS 07100](/reference-guide/error-code-reference/71-GAUSS-07001-GAUSS-07100.md)
++ [GAUSS 07101 - GAUSS 07200](/reference-guide/error-code-reference/72-GAUSS-07101-GAUSS-07200.md)
++ [GAUSS 07201 - GAUSS 07300](/reference-guide/error-code-reference/73-GAUSS-07201-GAUSS-07300.md)
++ [GAUSS 07301 - GAUSS 07400](/reference-guide/error-code-reference/74-GAUSS-07301-GAUSS-07400.md)
++ [GAUSS 07401 - GAUSS 07480](/reference-guide/error-code-reference/75-GAUSS-07401-GAUSS-07480.md)
++ [GAUSS 50000 - GAUSS 50999](/reference-guide/error-code-reference/76-GAUSS-50000-GAUSS-50999.md)
++ [GAUSS 51000 - GAUSS 51999](/reference-guide/error-code-reference/77-GAUSS-51000-GAUSS-51999.md)
++ [GAUSS 52000 - GAUSS 52999](/reference-guide/error-code-reference/78-GAUSS-52000-GAUSS-52999.md)
++ [GAUSS 53000 - GAUSS 53699](/reference-guide/error-code-reference/79-GAUSS-53000-GAUSS-53699.md)
++ Error Log Reference
+  + [Kernel Error Message](/reference-guide/error-log-reference/kernel-error-message.md)
diff --git a/product/en/docs-mogdb/v3.0/toc_extension-referecne.md b/product/en/docs-mogdb/v3.0/toc_extension-referecne.md
new file mode 100644
index 0000000000000000000000000000000000000000..2a2454e64861e9bb022b7dfa0543ce14a08f888f
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/toc_extension-referecne.md
@@ -0,0 +1,14 @@
+<!-- markdownlint-disable MD007 -->
+<!-- markdownlint-disable MD041 -->
+
+# MogDB Documentation 3.0
+
+## Extension Reference
+
++ [dblink](/reference-guide/oracle-plugins/dblink-user-guide.md)
++ [orafce](/reference-guide/oracle-plugins/orafce-user-guide.md)
++ [pg_bulkload](/reference-guide/oracle-plugins/pg_bulkload-user-guide.md)
++ [pg_prewarm](/reference-guide/oracle-plugins/pg_prewarm-user-guide.md)
++ [pg_repack](/reference-guide/oracle-plugins/pg_repack-user-guide.md)
++ [pg_trgm](/reference-guide/oracle-plugins/pg_trgm-user-guide.md)
++ [wal2json](/reference-guide/oracle-plugins/wal2json-user-guide.md)
\ No newline at end of file
diff --git a/product/en/docs-mogdb/v3.0/toc_faqs.md b/product/en/docs-mogdb/v3.0/toc_faqs.md
new file mode 100644
index 0000000000000000000000000000000000000000..af384ed434513993bfa092451c6a0cddf561ca21
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/toc_faqs.md
@@ -0,0 +1,12 @@
+<!-- markdownlint-disable MD007 -->
+<!-- markdownlint-disable MD041 -->
+# MogDB Documentation 3.0
+
+## FAQs
+
++ [Product FAQs](/faqs/product-faqs.md)
++ [Application Development FAQs](/faqs/application-development-faqs.md)
++ [Deployment and Maintenance FAQs](/faqs/deployment-and-maintenance-faqs.md)
++ [Upgrade FAQs](/faqs/upgrade-faqs.md)
++ [High Availability FAQs](/faqs/high-availability-faqs.md)
++ [Migration FAQs](/faqs/migration-faqs.md)
diff --git a/product/en/docs-mogdb/v3.0/toc_glossary.md b/product/en/docs-mogdb/v3.0/toc_glossary.md
new file mode 100644
index 0000000000000000000000000000000000000000..c933ef47b611f66396e5ae24847895acd3dfced1
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/toc_glossary.md
@@ -0,0 +1,5 @@
+# MogDB Documentation 3.0
+
+## Glossary
+
++ [Glossary](/glossary.md)
diff --git a/product/en/docs-mogdb/v3.0/toc_install.md b/product/en/docs-mogdb/v3.0/toc_install.md
new file mode 100644
index 0000000000000000000000000000000000000000..2f796417a8cdf06c21c07523e00149d71e371bd7
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/toc_install.md
@@ -0,0 +1,21 @@
+<!-- markdownlint-disable MD007 -->
+<!-- markdownlint-disable MD041 -->
+# MogDB Documentation 3.0
+
+## Installation Guide
+
++ [Container Installation](/installation-guide/docker-installation/docker-installation.md)
++ Simplified Installation Process
+  + [Preparing for Installation](/installation-guide/simplified-installation-process/1-installation-preparation.md)
+  + [Installation on a Single Node](/installation-guide/simplified-installation-process/2-installation-on-a-single-node.md)
+  + [Installation on Primary/Standby Nodes](/installation-guide/simplified-installation-process/3-installation-on-primary-standby-nodes.md)
++ Standard Installation
+  + [Installation Overview](/installation-guide/standard-installation/1-installation-overview.md)
+  + Preparing for Installation
+    + [Environment Requirement](/installation-guide/standard-installation/2-environment-requirement.md)
+    + [Modifying OS Configuration](/installation-guide/standard-installation/3-modifying-os-configuration.md)
+  + [Installing MogDB](/installation-guide/standard-installation/4-installing-mogdb.md)
+  + [Verifying the Installation](/installation-guide/standard-installation/5-verifying-installation.md)
+  + [Recommended Parameter Settings](/installation-guide/standard-installation/7-recommended-parameter-settings.md)
+  + [Uninstalling MogDB](/installation-guide/standard-installation/6-uninstallation.md)
++ [Manual Installation](/installation-guide/manual-installation.md)
diff --git a/product/en/docs-mogdb/v3.0/toc_manage.md b/product/en/docs-mogdb/v3.0/toc_manage.md
new file mode 100644
index 0000000000000000000000000000000000000000..ad182a0b2f44eb1f7fc9330f89a19f7490248afb
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/toc_manage.md
@@ -0,0 +1,72 @@
+<!-- markdownlint-disable MD007 -->
+<!-- markdownlint-disable MD041 -->
+# MogDB Documentation 3.0
+
+## Administrator Guide
+
++ Routine Maintenance
+  + [Starting and Stopping MogDB](/administrator-guide/routine-maintenance/0-starting-and-stopping-mogdb.md)
+  + [Using the gsql Client for Connection](/administrator-guide/routine-maintenance/using-the-gsql-client-for-connection.md)
+  + [Routine Maintenance](/administrator-guide/routine-maintenance/1-routine-maintenance-check-items.md)
+  + [Checking OS Parameters](/administrator-guide/routine-maintenance/2-checking-os-parameters.md)
+  + [Checking MogDB Health Status](/administrator-guide/routine-maintenance/3-checking-mogdb-health-status.md)
+  + [Checking Database Performance](/administrator-guide/routine-maintenance/4-checking-database-performance.md)
+  + [Checking and Deleting Logs](/administrator-guide/routine-maintenance/5-checking-and-deleting-logs.md)
+  + [Checking Time Consistency](/administrator-guide/routine-maintenance/6-checking-time-consistency.md)
+  + [Checking The Number of Application Connections](/administrator-guide/routine-maintenance/7-checking-the-number-of-application-connections.md)
+  + [Routinely Maintaining Tables](/administrator-guide/routine-maintenance/8-routinely-maintaining-tables.md)
+  + [Routinely Recreating an Index](/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md)
+  + [Data Security Maintenance Suggestions](/administrator-guide/routine-maintenance/10-data-security-maintenance-suggestions.md)
+  + [Log Reference](/administrator-guide/routine-maintenance/11-log-reference.md)
++ [Primary and Standby Management](/administrator-guide/primary-and-standby-management.md)
++ MOT Engine
+  + Introducing MOT
+    + [MOT Introduction](/administrator-guide/mot-engine/1-introducing-mot/1-mot-introduction.md)
+    + [MOT Features and Benefits](/administrator-guide/mot-engine/1-introducing-mot/2-mot-features-and-benefits.md)
+    + [MOT Key Technologies](/administrator-guide/mot-engine/1-introducing-mot/3-mot-key-technologies.md)
+    + [MOT Usage Scenarios](/administrator-guide/mot-engine/1-introducing-mot/4-mot-usage-scenarios.md)
+    + [MOT Performance Benchmarks](/administrator-guide/mot-engine/1-introducing-mot/5-mot-performance-benchmarks.md)
+  + Using MOT
+    + [Using MOT Overview](/administrator-guide/mot-engine/2-using-mot/1-using-mot-overview.md)
+    + [MOT Preparation](/administrator-guide/mot-engine/2-using-mot/2-mot-preparation.md)
+    + [MOT Deployment](/administrator-guide/mot-engine/2-using-mot/3-mot-deployment.md)
+    + [MOT Usage](/administrator-guide/mot-engine/2-using-mot/4-mot-usage.md)
+    + [MOT Administration](/administrator-guide/mot-engine/2-using-mot/5-mot-administration.md)
+    + [MOT Sample TPC-C Benchmark](/administrator-guide/mot-engine/2-using-mot/6-mot-sample-tpcc-benchmark.md)
+  + Concepts of MOT
+    + [MOT Scale-up Architecture](/administrator-guide/mot-engine/3-concepts-of-mot/3-1.md)
+    + [MOT Concurrency Control Mechanism](/administrator-guide/mot-engine/3-concepts-of-mot/3-2.md)
+    + [Extended FDW and Other MogDB Features](/administrator-guide/mot-engine/3-concepts-of-mot/3-3.md)
+    + [NUMA Awareness Allocation and Affinity](/administrator-guide/mot-engine/3-concepts-of-mot/3-4.md)
+    + [MOT Indexes](/administrator-guide/mot-engine/3-concepts-of-mot/3-5.md)
+    + [MOT Durability Concepts](/administrator-guide/mot-engine/3-concepts-of-mot/3-6.md)
+    + [MOT Recovery Concepts](/administrator-guide/mot-engine/3-concepts-of-mot/3-7.md)
+    + [MOT Query Native Compilation (JIT)](/administrator-guide/mot-engine/3-concepts-of-mot/3-8.md)
+    + [Comparison - Disk vs. MOT](/administrator-guide/mot-engine/3-concepts-of-mot/3-9.md)
+  + Appendix
+    + [References](/administrator-guide/mot-engine/4-appendix/1-references.md)
+    + [Glossary](/administrator-guide/mot-engine/4-appendix/2-glossary.md)
++ [Column-store Tables Management](/administrator-guide/column-store-tables-management.md)
++ Backup and Restoration
+  + [Overview](/administrator-guide/br/1-1-br.md)
+  + [Physical Backup and Restoration](/administrator-guide/br/1-2-br.md)
+  + [Logical Backup and Restoration](/administrator-guide/br/1-3-br.md)
+  + [Flashback Restoration](/administrator-guide/br/1-4-br.md)
++ Importing and Exporting Data
+  + Importing Data
+    + [Import Modes](/administrator-guide/importing-and-exporting-data/importing-data/1-import-modes.md)
+    + [Running the INSERT Statement to Insert Data](/administrator-guide/importing-and-exporting-data/importing-data/2-running-the-INSERT-statement-to-insert-data.md)
+    + [Running the COPY FROM STDIN Statement to Import Data](/administrator-guide/importing-and-exporting-data/importing-data/3-running-the-COPY-FROM-STDIN-statement-to-import-data.md)
+    + [Using a gsql Meta-Command to Import Data](/administrator-guide/importing-and-exporting-data/importing-data/4-using-a-gsql-meta-command-to-import-data.md)
+    + [Using gs_restore to Import Data](/administrator-guide/importing-and-exporting-data/importing-data/5-using-gs_restore-to-import-data.md)
+    + [Updating Data in a Table](/administrator-guide/importing-and-exporting-data/importing-data/6-updating-data-in-a-table.md)
+    + [Deep Copy](/administrator-guide/importing-and-exporting-data/importing-data/7-deep-copy.md)
+    + [ANALYZE Table](/administrator-guide/importing-and-exporting-data/importing-data/8-ANALYZE-table.md)
+    + [Doing VACUUM to a Table](/administrator-guide/importing-and-exporting-data/importing-data/9-doing-VACUUM-to-a-table.md)
+    + [Managing Concurrent Write Operations](/administrator-guide/importing-and-exporting-data/importing-data/10-managing-concurrent-write-operations.md)
+  + Exporting Data
+    + [Using gs_dump and gs_dumpall to Export Data Overview](/administrator-guide/importing-and-exporting-data/exporting-data/1-using-gs_dump-and-gs_dumpall-to-export-data-overview.md)
+    + [Exporting a Single Database](/administrator-guide/importing-and-exporting-data/exporting-data/2-exporting-a-single-database.md)
+    + [Exporting All Databases](/administrator-guide/importing-and-exporting-data/exporting-data/3-exporting-all-databases.md)
+    + [Data Export By a User Without Required Permissions](/administrator-guide/importing-and-exporting-data/exporting-data/4-data-export-by-a-user-without-required-permissions.md)
++ [Upgrade Guide](/administrator-guide/upgrade-guide.md)
diff --git a/product/en/docs-mogdb/v3.0/toc_parameters-and-tools.md b/product/en/docs-mogdb/v3.0/toc_parameters-and-tools.md
new file mode 100644
index 0000000000000000000000000000000000000000..8237916d8038f5c72f4d12f0cbf756b0c0438d54
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/toc_parameters-and-tools.md
@@ -0,0 +1,377 @@
+<!-- markdownlint-disable MD007 -->
+<!-- markdownlint-disable MD041 -->
+
+# MogDB Documentation 3.0
+
+## Parameters and Tools
+
++ GUC Parameters
+  + [GUC Parameter Usage](./reference-guide/guc-parameters/1-guc-parameter-usage.md)
+  + [File Location](./reference-guide/guc-parameters/2-file-location.md)
+  + Connection and Authentication
+    + [Connection Settings](./reference-guide/guc-parameters/3-connection-and-authentication/1-connection-settings.md)
+    + [Security and Authentication (postgresql.conf)](./reference-guide/guc-parameters/3-connection-and-authentication/2-security-and-authentication.md)
+    + [Communication Library Parameters](./reference-guide/guc-parameters/3-connection-and-authentication/3-communication-library-parameters.md)
+  + Resource Consumption
+    + [Memory](./reference-guide/guc-parameters/4-resource-consumption/1-memory.md)
+    + [Disk Space](./reference-guide/guc-parameters/4-resource-consumption/2-disk-space.md)
+    + [Kernel Resource Usage](./reference-guide/guc-parameters/4-resource-consumption/3-kernel-resource-usage.md)
+    + [Cost-based Vacuum Delay](./reference-guide/guc-parameters/4-resource-consumption/4-cost-based-vacuum-delay.md)
+    + [Background Writer](./reference-guide/guc-parameters/4-resource-consumption/5-background-writer.md)
+    + [Asynchronous I/O Operations](./reference-guide/guc-parameters/4-resource-consumption/6-asynchronous-io-operations.md)
+  + [Parallel Import](./reference-guide/guc-parameters/5-parallel-import.md)
+  + Write Ahead Log
+    + [Settings](./reference-guide/guc-parameters/6-write-ahead-log/1-settings.md)
+    + [Checkpoints](./reference-guide/guc-parameters/6-write-ahead-log/2-checkpoints.md)
+    + [Log Replay](./reference-guide/guc-parameters/6-write-ahead-log/3-log-replay.md)
+    + [Archiving](./reference-guide/guc-parameters/6-write-ahead-log/4-archiving.md)
+  + HA Replication
+    + [Sending Server](./reference-guide/guc-parameters/7-ha-replication/1-sending-server.md)
+    + [Primary Server](./reference-guide/guc-parameters/7-ha-replication/2-primary-server.md)
+    + [Standby Server](./reference-guide/guc-parameters/7-ha-replication/3-standby-server.md)
+  + [Memory Table](./reference-guide/guc-parameters/8-mot.md)
+  + Query Planning
+    + [Introduction](./reference-guide/guc-parameters/9-query-planning/introduction-to-query-planning.md)
+    + [Optimizer Method Configuration](./reference-guide/guc-parameters/9-query-planning/1-optimizer-method-configuration.md)
+    + [Optimizer Cost Constants](./reference-guide/guc-parameters/9-query-planning/2-optimizer-cost-constants.md)
+    + [Genetic Query Optimizer](./reference-guide/guc-parameters/9-query-planning/3-genetic-query-optimizer.md)
+    + [Other Optimizer Options](./reference-guide/guc-parameters/9-query-planning/4-other-optimizer-options.md)
+  + Error Reporting and Logging
+    + [Logging Destination](./reference-guide/guc-parameters/10-error-reporting-and-logging/1-logging-destination.md)
+    + [Logging Time](./reference-guide/guc-parameters/10-error-reporting-and-logging/2-logging-time.md)
+    + [Logging Content](./reference-guide/guc-parameters/10-error-reporting-and-logging/3-logging-content.md)
+    + [Using CSV Log Output](./reference-guide/guc-parameters/10-error-reporting-and-logging/4-using-csv-log-output.md)
+  + [Alarm Detection](./reference-guide/guc-parameters/11-alarm-detection.md)
+  + Statistics During the Database Running
+    + [Query and Index Statistics Collector](./reference-guide/guc-parameters/12-statistics-during-the-database-running/1-query-and-index-statistics-collector.md)
+    + [Performance Statistics](./reference-guide/guc-parameters/12-statistics-during-the-database-running/2-performance-statistics.md)
+  + [Load Management](./reference-guide/guc-parameters/13-load-management.md)
+  + [Automatic Vacuuming](./reference-guide/guc-parameters/14-automatic-vacuuming.md)
+  + Default Settings of Client Connection
+    + [Statement Behavior](./reference-guide/guc-parameters/15-default-settings-of-client-connection/1-statement-behavior.md)
+    + [Zone and Formatting](./reference-guide/guc-parameters/15-default-settings-of-client-connection/2-zone-and-formatting.md)
+    + [Other Default Parameters](./reference-guide/guc-parameters/15-default-settings-of-client-connection/3-other-default-parameters.md)
+  + [Lock Management](./reference-guide/guc-parameters/16-lock-management.md)
+  + Version and Platform Compatibility
+    + [Compatibility with Earlier Versions](./reference-guide/guc-parameters/17-version-and-platform-compatibility/1-compatibility-with-earlier-versions.md)
+    + [Platform and Client Compatibility](./reference-guide/guc-parameters/17-version-and-platform-compatibility/2-platform-and-client-compatibility.md)
+  + [Faut Tolerance](./reference-guide/guc-parameters/18-fault-tolerance.md)
+  + [Connection Pool Parameters](./reference-guide/guc-parameters/19-connection-pool-parameters.md)
+  + [MogDB Transaction](./reference-guide/guc-parameters/20-MogDB-transaction.md)
+  + [Developer Options](./reference-guide/guc-parameters/21-developer-options.md)
+  + Auditing
+    + [Audit Switch](./reference-guide/guc-parameters/22-auditing/1-audit-switch.md)
+    + [User and Permission Audit](./reference-guide/guc-parameters/22-auditing/2-user-and-permission-audit.md)
+    + [Operation Auditing](./reference-guide/guc-parameters/22-auditing/3-operation-audit.md)
+  + [Upgrade Parameters](./reference-guide/guc-parameters/23-upgrade-parameters.md)
+  + [Miscellaneous Parameters](./reference-guide/guc-parameters/24-miscellaneous-parameters.md)
+  + [Wait Events](./reference-guide/guc-parameters/25-wait-events.md)
+  + [Query](./reference-guide/guc-parameters/26-query.md)
+  + [System Performance Snapshot](./reference-guide/guc-parameters/27-system-performance-snapshot.md)
+  + [Security Configuration](./reference-guide/guc-parameters/27.1-security-configuration.md)
+  + [Global Temporary Table](./reference-guide/guc-parameters/29-global-temporary-table.md)
+  + [HyperLogLog](./reference-guide/guc-parameters/29.1-HyperLogLog.md)
+  + [Scheduled Task](./reference-guide/guc-parameters/31-scheduled-task.md)
+  + [Thread Pool](./reference-guide/guc-parameters/32-thread-pool.md)
+  + [User-defined Functions](./reference-guide/guc-parameters/33-user-defined-functions.md)
+  + [Backup and Restoration](./reference-guide/guc-parameters/34-backup-and-restoration.md)
+  + [Undo](./reference-guide/guc-parameters/35-undo.md)
+  + [DCF Parameters Settings](./reference-guide/guc-parameters/36-DCF-parameters-settings.md)
+  + [Flashback](./reference-guide/guc-parameters/37-flashback.md)
+  + [Rollback Parameters](./reference-guide/guc-parameters/38-rollback-parameters.md)
+  + [Reserved Parameters](./reference-guide/guc-parameters/39-reserved-parameters.md)
+  + [AI Features](./reference-guide/guc-parameters/40-AI-features.md)
+  + [Appendix](./reference-guide/guc-parameters/30-appendix.md)
++ schema
+  + Information Schema
+    + [Overview](./reference-guide/schema/information-schema/1-information-schema-overview.md)
+    + [_PG_FOREIGN_DATA_WRAPPERS](./reference-guide/schema/information-schema/2-_PG_FOREIGN_DATA_WRAPPERS.md)
+    + [_PG_FOREIGN_SERVERS](./reference-guide/schema/information-schema/3-_PG_FOREIGN_SERVERS.md)
+    + [_PG_FOREIGN_TABLE_COLUMNS](./reference-guide/schema/information-schema/4-_PG_FOREIGN_TABLE_COLUMNS.md)
+    + [_PG_FOREIGN_TABLES](./reference-guide/schema/information-schema/5-_PG_FOREIGN_TABLES.md)
+    + [_PG_USER_MAPPINGS](./reference-guide/schema/information-schema/6-_PG_USER_MAPPINGS.md)
+    + [INFORMATION_SCHEMA_CATALOG_NAME](./reference-guide/schema/information-schema/7-INFORMATION_SCHEMA_CATALOG_NAME.md)
+  + DBE_PERF
+    + [Overview](./reference-guide/schema/DBE_PERF/DBE_PERF_overview.md)
+    + OS
+      + [OS_RUNTIME](./reference-guide/schema/DBE_PERF/os/OS_RUNTIME.md)
+      + [GLOBAL_OS_RUNTIME](./reference-guide/schema/DBE_PERF/os/GLOBAL_OS_RUNTIME.md)
+      + [OS_THREADS](./reference-guide/schema/DBE_PERF/os/OS_THREADS.md)
+      + [GLOBAL_OS_THREADS](./reference-guide/schema/DBE_PERF/os/GLOBAL_OS_THREADS.md)
+    + Instance
+      + [INSTANCE_TIME](./reference-guide/schema/DBE_PERF/instance/INSTANCE_TIME.md)
+      + [GLOBAL_INSTANCE_TIME](./reference-guide/schema/DBE_PERF/instance/GLOBAL_INSTANCE_TIME.md)
+    + Memory
+      + [MEMORY_NODE_DETAIL](./reference-guide/schema/DBE_PERF/memory/MEMORY_NODE_DETAIL.md)
+      + [GLOBAL_MEMORY_NODE_DETAIL](./reference-guide/schema/DBE_PERF/memory/GLOBAL_MEMORY_NODE_DETAIL.md)
+      + [GS_SHARED_MEMORY_DETAIL](./reference-guide/schema/DBE_PERF/memory/GS_SHARED_MEMORY_DETAIL.md)
+      + [GLOBAL_SHARED_MEMORY_DETAIL](./reference-guide/schema/DBE_PERF/memory/GLOBAL_SHARED_MEMORY_DETAIL.md)
+    + File
+      + [FILE_IOSTAT](./reference-guide/schema/DBE_PERF/file/FILE_IOSTAT.md)
+      + [SUMMARY_FILE_IOSTAT](./reference-guide/schema/DBE_PERF/file/SUMMARY_FILE_IOSTAT.md)
+      + [GLOBAL_FILE_IOSTAT](./reference-guide/schema/DBE_PERF/file/GLOBAL_FILE_IOSTAT.md)
+      + [FILE_REDO_IOSTAT](./reference-guide/schema/DBE_PERF/file/FILE_REDO_IOSTAT.md)
+      + [SUMMARY_FILE_REDO_IOSTAT](./reference-guide/schema/DBE_PERF/file/SUMMARY_FILE_REDO_IOSTAT.md)
+      + [GLOBAL_FILE_REDO_IOSTAT](./reference-guide/schema/DBE_PERF/file/GLOBAL_FILE_REDO_IOSTAT.md)
+      + [LOCAL_REL_IOSTAT](./reference-guide/schema/DBE_PERF/file/LOCAL_REL_IOSTAT.md)
+      + [GLOBAL_REL_IOSTAT](./reference-guide/schema/DBE_PERF/file/GLOBAL_REL_IOSTAT.md)
+      + [SUMMARY_REL_IOSTAT](./reference-guide/schema/DBE_PERF/file/SUMMARY_REL_IOSTAT.md)
+    + Object
+      + [STAT_USER_TABLES](./reference-guide/schema/DBE_PERF/object/STAT_USER_TABLES.md)
+      + [SUMMARY_STAT_USER_TABLES](./reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_USER_TABLES.md)
+      + [GLOBAL_STAT_USER_TABLES](./reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_USER_TABLES.md)
+      + [STAT_USER_INDEXES](./reference-guide/schema/DBE_PERF/object/STAT_USER_INDEXES.md)
+      + [SUMMARY_STAT_USER_INDEXES](./reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_USER_INDEXES.md)
+      + [GLOBAL_STAT_USER_INDEXES](./reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_USER_INDEXES.md)
+      + [STAT_SYS_TABLES](./reference-guide/schema/DBE_PERF/object/STAT_SYS_TABLES.md)
+      + [SUMMARY_STAT_SYS_TABLES](./reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_SYS_TABLES.md)
+      + [GLOBAL_STAT_SYS_TABLES](./reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_SYS_TABLES.md)
+      + [STAT_SYS_INDEXES](./reference-guide/schema/DBE_PERF/object/STAT_SYS_INDEXES.md)
+      + [SUMMARY_STAT_SYS_INDEXES](./reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_SYS_INDEXES.md)
+      + [GLOBAL_STAT_SYS_INDEXES](./reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_SYS_INDEXES.md)
+      + [STAT_ALL_TABLES](./reference-guide/schema/DBE_PERF/object/STAT_ALL_TABLES.md)
+      + [SUMMARY_STAT_ALL_TABLES](./reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_ALL_TABLES.md)
+      + [GLOBAL_STAT_ALL_TABLES](./reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_ALL_TABLES.md)
+      + [STAT_ALL_INDEXES](./reference-guide/schema/DBE_PERF/object/STAT_ALL_INDEXES.md)
+      + [SUMMARY_STAT_ALL_INDEXES](./reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_ALL_INDEXES.md)
+      + [GLOBAL_STAT_ALL_INDEXES](./reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_ALL_INDEXES.md)
+      + [STAT_DATABASE](./reference-guide/schema/DBE_PERF/object/STAT_DATABASE.md)
+      + [SUMMARY_STAT_DATABASE](./reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_DATABASE.md)
+      + [GLOBAL_STAT_DATABASE](./reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_DATABASE.md)
+      + [STAT_DATABASE_CONFLICTS](./reference-guide/schema/DBE_PERF/object/STAT_DATABASE_CONFLICTS.md)
+      + [SUMMARY_STAT_DATABASE_CONFLICTS](./reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_DATABASE_CONFLICTS.md)
+      + [GLOBAL_STAT_DATABASE_CONFLICTS](./reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_DATABASE_CONFLICTS.md)
+      + [STAT_XACT_ALL_TABLES](./reference-guide/schema/DBE_PERF/object/STAT_XACT_ALL_TABLES.md)
+      + [SUMMARY_STAT_XACT_ALL_TABLES](./reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_ALL_TABLES.md)
+      + [GLOBAL_STAT_XACT_ALL_TABLES](./reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_ALL_TABLES.md)
+      + [STAT_XACT_SYS_TABLES](./reference-guide/schema/DBE_PERF/object/STAT_XACT_SYS_TABLES.md)
+      + [SUMMARY_STAT_XACT_SYS_TABLES](./reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_SYS_TABLES.md)
+      + [GLOBAL_STAT_XACT_SYS_TABLES](./reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_SYS_TABLES.md)
+      + [STAT_XACT_USER_TABLES](./reference-guide/schema/DBE_PERF/object/STAT_XACT_USER_TABLES.md)
+      + [SUMMARY_STAT_XACT_USER_TABLES](./reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_USER_TABLES.md)
+      + [GLOBAL_STAT_XACT_USER_TABLES](./reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_USER_TABLES.md)
+      + [STAT_XACT_USER_FUNCTIONS](./reference-guide/schema/DBE_PERF/object/STAT_XACT_USER_FUNCTIONS.md)
+      + [SUMMARY_STAT_XACT_USER_FUNCTIONS](./reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_USER_FUNCTIONS.md)
+      + [GLOBAL_STAT_XACT_USER_FUNCTIONS](./reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_USER_FUNCTIONS.md)
+      + [STAT_BAD_BLOCK](./reference-guide/schema/DBE_PERF/object/STAT_BAD_BLOCK.md)
+      + [SUMMARY_STAT_BAD_BLOCK](./reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_BAD_BLOCK.md)
+      + [GLOBAL_STAT_BAD_BLOCK](./reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_BAD_BLOCK.md)
+      + [STAT_USER_FUNCTIONS](./reference-guide/schema/DBE_PERF/object/STAT_USER_FUNCTIONS.md)
+      + [SUMMARY_STAT_USER_FUNCTIONS](./reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_USER_FUNCTIONS.md)
+      + [GLOBAL_STAT_USER_FUNCTIONS](./reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_USER_FUNCTIONS.md)
+    + Workload
+      + [WORKLOAD_SQL_COUNT](./reference-guide/schema/DBE_PERF/workload/WORKLOAD_SQL_COUNT.md)
+      + [SUMMARY_WORKLOAD_SQL_COUNT](./reference-guide/schema/DBE_PERF/workload/SUMMARY_WORKLOAD_SQL_COUNT.md)
+      + [WORKLOAD_TRANSACTION](./reference-guide/schema/DBE_PERF/workload/WORKLOAD_TRANSACTION.md)
+      + [SUMMARY_WORKLOAD_TRANSACTION](./reference-guide/schema/DBE_PERF/workload/SUMMARY_WORKLOAD_TRANSACTION.md)
+      + [GLOBAL_WORKLOAD_TRANSACTION](./reference-guide/schema/DBE_PERF/workload/GLOBAL_WORKLOAD_TRANSACTION.md)
+      + [WORKLOAD_SQL_ELAPSE_TIME](./reference-guide/schema/DBE_PERF/workload/WORKLOAD_SQL_ELAPSE_TIME.md)
+      + [SUMMARY_WORKLOAD_SQL_ELAPSE_TIME](./reference-guide/schema/DBE_PERF/workload/SUMMARY_WORKLOAD_SQL_ELAPSE_TIME.md)
+      + [USER_TRANSACTION](./reference-guide/schema/DBE_PERF/workload/USER_TRANSACTION.md)
+      + [GLOBAL_USER_TRANSACTION](./reference-guide/schema/DBE_PERF/workload/GLOBAL_USER_TRANSACTION.md)
+    + Session/Thread
+      + [SESSION_STAT](./reference-guide/schema/DBE_PERF/session-thread/SESSION_STAT.md)
+      + [GLOBAL_SESSION_STAT](./reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_STAT.md)
+      + [SESSION_TIME](./reference-guide/schema/DBE_PERF/session-thread/SESSION_TIME.md)
+      + [GLOBAL_SESSION_TIME](./reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_TIME.md)
+      + [SESSION_MEMORY](./reference-guide/schema/DBE_PERF/session-thread/SESSION_MEMORY.md)
+      + [GLOBAL_SESSION_MEMORY](./reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_MEMORY.md)
+      + [SESSION_MEMORY_DETAIL](./reference-guide/schema/DBE_PERF/session-thread/SESSION_MEMORY_DETAIL.md)
+      + [GLOBAL_SESSION_MEMORY_DETAIL](./reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_MEMORY_DETAIL.md)
+      + [SESSION_STAT_ACTIVITY](./reference-guide/schema/DBE_PERF/session-thread/SESSION_STAT_ACTIVITY.md)
+      + [GLOBAL_SESSION_STAT_ACTIVITY](./reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_STAT_ACTIVITY.md)
+      + [THREAD_WAIT_STATUS](./reference-guide/schema/DBE_PERF/session-thread/THREAD_WAIT_STATUS.md)
+      + [GLOBAL_THREAD_WAIT_STATUS](./reference-guide/schema/DBE_PERF/session-thread/GLOBAL_THREAD_WAIT_STATUS.md)
+      + [LOCAL_THREADPOOL_STATUS](./reference-guide/schema/DBE_PERF/session-thread/LOCAL_THREADPOOL_STATUS.md)
+      + [GLOBAL_THREADPOOL_STATUS](./reference-guide/schema/DBE_PERF/session-thread/GLOBAL_THREADPOOL_STATUS.md)
+      + [SESSION_CPU_RUNTIME](./reference-guide/schema/DBE_PERF/session-thread/SESSION_CPU_RUNTIME.md)
+      + [SESSION_MEMORY_RUNTIME](./reference-guide/schema/DBE_PERF/session-thread/SESSION_MEMORY_RUNTIME.md)
+      + [STATEMENT_IOSTAT_COMPLEX_RUNTIME](./reference-guide/schema/DBE_PERF/session-thread/STATEMENT_IOSTAT_COMPLEX_RUNTIME.md)
+      + [LOCAL_ACTIVE_SESSION](./reference-guide/schema/DBE_PERF/session-thread/LOCAL_ACTIVE_SESSION.md)
+    + Transaction
+      + [TRANSACTIONS_PREPARED_XACTS](./reference-guide/schema/DBE_PERF/transaction/TRANSACTIONS_PREPARED_XACTS.md)
+      + [SUMMARY_TRANSACTIONS_PREPARED_XACTS](./reference-guide/schema/DBE_PERF/transaction/SUMMARY_TRANSACTIONS_PREPARED_XACTS.md)
+      + [GLOBAL_TRANSACTIONS_PREPARED_XACTS](./reference-guide/schema/DBE_PERF/transaction/GLOBAL_TRANSACTIONS_PREPARED_XACTS.md)
+      + [TRANSACTIONS_RUNNING_XACTS](./reference-guide/schema/DBE_PERF/transaction/TRANSACTIONS_RUNNING_XACTS.md)
+      + [SUMMARY_TRANSACTIONS_RUNNING_XACTS](./reference-guide/schema/DBE_PERF/transaction/SUMMARY_TRANSACTIONS_RUNNING_XACTS.md)
+      + [GLOBAL_TRANSACTIONS_RUNNING_XACTS](./reference-guide/schema/DBE_PERF/transaction/GLOBAL_TRANSACTIONS_RUNNING_XACTS.md)
+    + Query
+      + [STATEMENT](./reference-guide/schema/DBE_PERF/query/STATEMENT.md)
+      + [SUMMARY_STATEMENT](./reference-guide/schema/DBE_PERF/query/SUMMARY_STATEMENT.md)
+      + [STATEMENT_COUNT](./reference-guide/schema/DBE_PERF/query/STATEMENT_COUNT.md)
+      + [GLOBAL_STATEMENT_COUNT](./reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COUNT.md)
+      + [SUMMARY_STATEMENT_COUNT](./reference-guide/schema/DBE_PERF/query/SUMMARY_STATEMENT_COUNT.md)
+      + [GLOBAL_STATEMENT_COMPLEX_HISTORY](./reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COMPLEX_HISTORY.md)
+      + [GLOBAL_STATEMENT_COMPLEX_HISTORY_TABLE](./reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COMPLEX_HISTORY_TABLE.md)
+      + [GLOBAL_STATEMENT_COMPLEX_RUNTIME](./reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COMPLEX_RUNTIME.md)
+      + [STATEMENT_RESPONSETIME_PERCENTILE](./reference-guide/schema/DBE_PERF/query/STATEMENT_RESPONSETIME_PERCENTILE.md)
+      + [STATEMENT_USER_COMPLEX_HISTORY](./reference-guide/schema/DBE_PERF/query/STATEMENT_USER_COMPLEX_HISTORY.md)
+      + [STATEMENT_COMPLEX_RUNTIME](./reference-guide/schema/DBE_PERF/query/STATEMENT_COMPLEX_RUNTIME.md)
+      + [STATEMENT_COMPLEX_HISTORY_TABLE](./reference-guide/schema/DBE_PERF/query/STATEMENT_COMPLEX_HISTORY_TABLE.md)
+      + [STATEMENT_COMPLEX_HISTORY](./reference-guide/schema/DBE_PERF/query/STATEMENT_COMPLEX_HISTORY.md)
+      + [STATEMENT_WLMSTAT_COMPLEX_RUNTIME](./reference-guide/schema/DBE_PERF/query/STATEMENT_WLMSTAT_COMPLEX_RUNTIME.md)
+      + [STATEMENT_HISTORY](./reference-guide/schema/DBE_PERF/query/STATEMENT_HISTORY.md)
+    + Cache/IO
+      + [STATIO_USER_TABLES](./reference-guide/schema/DBE_PERF/cache-io/STATIO_USER_TABLES.md)
+      + [SUMMARY_STATIO_USER_TABLES](./reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_USER_TABLES.md)
+      + [GLOBAL_STATIO_USER_TABLES](./reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_USER_TABLES.md)
+      + [STATIO_USER_INDEXES](./reference-guide/schema/DBE_PERF/cache-io/STATIO_USER_INDEXES.md)
+      + [SUMMARY_STATIO_USER_INDEXES](./reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_USER_INDEXES.md)
+      + [GLOBAL_STATIO_USER_INDEXES](./reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_USER_INDEXES.md)
+      + [STATIO_USER_SEQUENCES](./reference-guide/schema/DBE_PERF/cache-io/STATIO_USER_SEQUENCES.md)
+      + [SUMMARY_STATIO_USER_SEQUENCES](./reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_USER_SEQUENCES.md)
+      + [GLOBAL_STATIO_USER_SEQUENCES](./reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_USER_SEQUENCES.md)
+      + [STATIO_SYS_TABLES](./reference-guide/schema/DBE_PERF/cache-io/STATIO_SYS_TABLES.md)
+      + [SUMMARY_STATIO_SYS_TABLES](./reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_SYS_TABLES.md)
+      + [GLOBAL_STATIO_SYS_TABLES](./reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_SYS_TABLES.md)
+      + [STATIO_SYS_INDEXES](./reference-guide/schema/DBE_PERF/cache-io/STATIO_SYS_INDEXES.md)
+      + [SUMMARY_STATIO_SYS_INDEXES](./reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_SYS_INDEXES.md)
+      + [GLOBAL_STATIO_SYS_INDEXES](./reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_SYS_INDEXES.md)
+      + [STATIO_SYS_SEQUENCES](./reference-guide/schema/DBE_PERF/cache-io/STATIO_SYS_SEQUENCES.md)
+      + [SUMMARY_STATIO_SYS_SEQUENCES](./reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_SYS_SEQUENCES.md)
+      + [GLOBAL_STATIO_SYS_SEQUENCES](./reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_SYS_SEQUENCES.md)
+      + [STATIO_ALL_TABLES](./reference-guide/schema/DBE_PERF/cache-io/STATIO_ALL_TABLES.md)
+      + [SUMMARY_STATIO_ALL_TABLES](./reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_ALL_TABLES.md)
+      + [GLOBAL_STATIO_ALL_TABLES](./reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_ALL_TABLES.md)
+      + [STATIO_ALL_INDEXES](./reference-guide/schema/DBE_PERF/cache-io/STATIO_ALL_INDEXES.md)
+      + [SUMMARY_STATIO_ALL_INDEXES](./reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_ALL_INDEXES.md)
+      + [GLOBAL_STATIO_ALL_INDEXES](./reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_ALL_INDEXES.md)
+      + [STATIO_ALL_SEQUENCES](./reference-guide/schema/DBE_PERF/cache-io/STATIO_ALL_SEQUENCES.md)
+      + [SUMMARY_STATIO_ALL_SEQUENCES](./reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_ALL_SEQUENCES.md)
+      + [GLOBAL_STATIO_ALL_SEQUENCES](./reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_ALL_SEQUENCES.md)
+      + [GLOBAL_STAT_DB_CU](./reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STAT_DB_CU.md)
+      + [GLOBAL_STAT_SESSION_CU](./reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STAT_SESSION_CU.md)
+    + Utility
+      + [REPLICATION_STAT](./reference-guide/schema/DBE_PERF/utility/REPLICATION_STAT.md)
+      + [GLOBAL_REPLICATION_STAT](./reference-guide/schema/DBE_PERF/utility/GLOBAL_REPLICATION_STAT.md)
+      + [REPLICATION_SLOTS](./reference-guide/schema/DBE_PERF/utility/REPLICATION_SLOTS.md)
+      + [GLOBAL_REPLICATION_SLOTS](./reference-guide/schema/DBE_PERF/utility/GLOBAL_REPLICATION_SLOTS.md)
+      + [BGWRITER_STAT](./reference-guide/schema/DBE_PERF/utility/BGWRITER_STAT.md)
+      + [GLOBAL_BGWRITER_STAT](./reference-guide/schema/DBE_PERF/utility/GLOBAL_BGWRITER_STAT.md)
+      + [GLOBAL_CKPT_STATUS](./reference-guide/schema/DBE_PERF/utility/GLOBAL_CKPT_STATUS.md)
+      + [GLOBAL_DOUBLE_WRITE_STATUS](./reference-guide/schema/DBE_PERF/utility/GLOBAL_DOUBLE_WRITE_STATUS.md)
+      + [GLOBAL_PAGEWRITER_STATUS](./reference-guide/schema/DBE_PERF/utility/GLOBAL_PAGEWRITER_STATUS.md)
+      + [GLOBAL_RECORD_RESET_TIME](./reference-guide/schema/DBE_PERF/utility/GLOBAL_RECORD_RESET_TIME.md)
+      + [GLOBAL_REDO_STATUS](./reference-guide/schema/DBE_PERF/utility/GLOBAL_REDO_STATUS.md)
+      + [GLOBAL_RECOVERY_STATUS](./reference-guide/schema/DBE_PERF/utility/GLOBAL_RECOVERY_STATUS.md)
+      + [CLASS_VITAL_INFO](./reference-guide/schema/DBE_PERF/utility/CLASS_VITAL_INFO.md)
+      + [USER_LOGIN](./reference-guide/schema/DBE_PERF/utility/USER_LOGIN.md)
+      + [SUMMARY_USER_LOGIN](./reference-guide/schema/DBE_PERF/utility/SUMMARY_USER_LOGIN.md)
+      + [GLOBAL_GET_BGWRITER_STATUS](./reference-guide/schema/DBE_PERF/utility/GLOBAL_GET_BGWRITER_STATUS.md)
+      + [GLOBAL_SINGLE_FLUSH_DW_STATUS](./reference-guide/schema/DBE_PERF/utility/GLOBAL_SINGLE_FLUSH_DW_STATUS.md)
+      + [GLOBAL_CANDIDATE_STATUS](./reference-guide/schema/DBE_PERF/utility/GLOBAL_CANDIDATE_STATUS.md)
+    + Lock
+      + [LOCKS](./reference-guide/schema/DBE_PERF/lock/LOCKS.md)
+      + [GLOBAL_LOCKS](./reference-guide/schema/DBE_PERF/lock/GLOBAL_LOCKS.md)
+    + Wait Events
+      + [WAIT_EVENTS](./reference-guide/schema/DBE_PERF/wait-events/WAIT_EVENTS.md)
+      + [GLOBAL_WAIT_EVENTS](./reference-guide/schema/DBE_PERF/wait-events/GLOBAL_WAIT_EVENTS.md)
+    + Configuration
+      + [CONFIG_SETTINGS](./reference-guide/schema/DBE_PERF/configuration/CONFIG_SETTINGS.md)
+      + [GLOBAL_CONFIG_SETTINGS](./reference-guide/schema/DBE_PERF/configuration/GLOBAL_CONFIG_SETTINGS.md)
+    + Operator
+      + [OPERATOR_HISTORY_TABLE](./reference-guide/schema/DBE_PERF/operator/OPERATOR_HISTORY_TABLE.md)
+      + [OPERATOR_HISTORY](./reference-guide/schema/DBE_PERF/operator/OPERATOR_HISTORY.md)
+      + [OPERATOR_RUNTIME](./reference-guide/schema/DBE_PERF/operator/OPERATOR_RUNTIME.md)
+      + [GLOBAL_OPERATOR_HISTORY](./reference-guide/schema/DBE_PERF/operator/GLOBAL_OPERATOR_HISTORY.md)
+      + [GLOBAL_OPERATOR_HISTORY_TABLE](./reference-guide/schema/DBE_PERF/operator/GLOBAL_OPERATOR_HISTORY_TABLE.md)
+      + [GLOBAL_OPERATOR_RUNTIME](./reference-guide/schema/DBE_PERF/operator/GLOBAL_OPERATOR_RUNTIME.md)
+    + Workload Manager
+      + [WLM_USER_RESOURCE_CONFIG](./reference-guide/schema/DBE_PERF/workload-manager/WLM_USER_RESOURCE_CONFIG.md)
+      + [WLM_USER_RESOURCE_RUNTIME](./reference-guide/schema/DBE_PERF/workload-manager/WLM_USER_RESOURCE_RUNTIME.md)
+    + Global Plancache
+      + [Overview](./reference-guide/schema/DBE_PERF/global-plancache/global-plancache-overview.md)
+      + [GLOBAL_PLANCACHE_STATUS](./reference-guide/schema/DBE_PERF/global-plancache/GLOBAL_PLANCACHE_STATUS.md)
+      + [GLOBAL_PLANCACHE_CLEAN](./reference-guide/schema/DBE_PERF/global-plancache/GLOBAL_PLANCACHE_CLEAN.md)
+    + RTO
+      + [global_rto_status](./reference-guide/schema/DBE_PERF/rto/global_rto_status.md)
+    + Appendix
+      + [Waiting status list](./reference-guide/schema/DBE_PERF/appendices/table-1.md)
+      + [List of wait events corresponding to lightweight locks](./reference-guide/schema/DBE_PERF/appendices/table-2.md)
+      + [List of wait events corresponding to I/Os](./reference-guide/schema/DBE_PERF/appendices/table-3.md)
+      + [List of wait events corresponding to transaction locks](./reference-guide/schema/DBE_PERF/appendices/table-4.md)
+      + [GS_WLM_SESSION_HISTORY columns](./reference-guide/schema/DBE_PERF/appendices/table-5.md)
+      + [GS_WLM_OPERATOR_INFO columns](./reference-guide/schema/DBE_PERF/appendices/table-6.md)
+  + DBE_PLDEBUGGER Schema
+    + [Overview](./reference-guide/schema/DBE_PLDEBUGGER-schema/overview-of-DBE_PLDEBUGGER-schema.md)
+    + [DBE_PLDEBUGGER.turn_on](./reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.turn_on.md)
+    + [DBE_PLDEBUGGER.turn_off](./reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.turn_off.md)
+    + [DBE_PLDEBUGGER.local_debug_server_info](./reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.local_debug_server_info.md)
+    + [DBE_PLDEBUGGER.attach](./reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.attach.md)
+    + [DBE_PLDEBUGGER.next](./reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.next.md)
+    + [DBE_PLDEBUGGER.continue](./reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.continue.md)
+    + [DBE_PLDEBUGGER.abort](./reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.abort.md)
+    + [DBE_PLDEBUGGER.print_var](./reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.print_var.md)
+    + [DBE_PLDEBUGGER.info_code](./reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.info_code.md)
+    + [DBE_PLDEBUGGER.step](./reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.step.md)
+    + [DBE_PLDEBUGGER.add_breakpoint](./reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.add_breakpoint.md)
+    + [DBE_PLDEBUGGER.delete_breakpoint](./reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.delete_breakpoint.md)
+    + [DBE_PLDEBUGGER.info_breakpoints](./reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.info_breakpoints.md)
+    + [DBE_PLDEBUGGER.backtrace](./reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.backtrace.md)
+    + [DBE_PLDEBUGGER.finish](./reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.finish.md)
+    + [DBE_PLDEBUGGER.set_var](./reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.set_var.md)
+  + DB4AI Schema
+    + [Overview](./reference-guide/schema/DB4AI-schema/overview-of-DB4AI-schema.md)
+    + [DB4AI.SNAPSHOT](./reference-guide/schema/DB4AI-schema/DB4AI.SNAPSHOT.md)
+    + [DB4AI.CREATE_SNAPSHOT](./reference-guide/schema/DB4AI-schema/DB4AI.CREATE_SNAPSHOT.md)
+    + [DB4AI.CREATE_SNAPSHOT_INTERNAL](./reference-guide/schema/DB4AI-schema/DB4AI.CREATE_SNAPSHOT_INTERNAL.md)
+    + [DB4AI.PREPARE_SNAPSHOT](./reference-guide/schema/DB4AI-schema/DB4AI.PREPARE_SNAPSHOT.md)
+    + [DB4AI.PREPARE_SNAPSHOT_INTERNAL](./reference-guide/schema/DB4AI-schema/DB4AI.PREPARE_SNAPSHOT_INTERNAL.md)
+    + [DB4AI.ARCHIVE_SNAPSHOT](./reference-guide/schema/DB4AI-schema/DB4AI.ARCHIVE_SNAPSHOT.md)
+    + [DB4AI.PUBLISH_SNAPSHOT](./reference-guide/schema/DB4AI-schema/DB4AI.PUBLISH_SNAPSHOT.md)
+    + [DB4AI.MANAGE_SNAPSHOT_INTERNAL](./reference-guide/schema/DB4AI-schema/DB4AI.MANAGE_SNAPSHOT_INTERNAL.md)
+    + [DB4AI.SAMPLE_SNAPSHOT](./reference-guide/schema/DB4AI-schema/DB4AI.SAMPLE_SNAPSHOT.md)
+    + [DB4AI.PURGE_SNAPSHOT](./reference-guide/schema/DB4AI-schema/DB4AI.PURGE_SNAPSHOT.md)
+    + [DB4AI.PURGE_SNAPSHOT_INTERNAL](./reference-guide/schema/DB4AI-schema/DB4AI.PURGE_SNAPSHOT_INTERNAL.md)
++ Tool Reference
+  + [Tool Overview](./reference-guide/tool-reference/tool-overview.md)
+  + [Client Tool](./reference-guide/tool-reference/client-tool.md)
+  + Server Tools
+    + [gs_cgroup](./reference-guide/tool-reference/server-tools/0-gs_cgroup.md)
+    + [gs_check](./reference-guide/tool-reference/server-tools/1-gs_check.md)
+    + [gs_checkos](./reference-guide/tool-reference/server-tools/2-gs_checkos.md)
+    + [gs_checkperf](./reference-guide/tool-reference/server-tools/3-gs_checkperf.md)
+    + [gs_collector](./reference-guide/tool-reference/server-tools/4-gs_collector.md)
+    + [gs_dump](./reference-guide/tool-reference/server-tools/5-gs_dump.md)
+    + [gs_dumpall](./reference-guide/tool-reference/server-tools/6-gs_dumpall.md)
+    + [gs_guc](./reference-guide/tool-reference/server-tools/7-gs_guc.md)
+    + [gs_encrypt](./reference-guide/tool-reference/server-tools/7.1-gs_encrypt.md)
+    + [gs_om](./reference-guide/tool-reference/server-tools/8-gs_om.md)
+    + [gs_plan_simulator](./reference-guide/tool-reference/server-tools/8.1-gs_plan_simulator.md)
+    + [gs_restore](./reference-guide/tool-reference/server-tools/9-gs_restore.md)
+    + [gs_ssh](./reference-guide/tool-reference/server-tools/10-gs_ssh.md)
+  + Tools Used in the Internal System
+    + [gaussdb](./reference-guide/tool-reference/tools-used-in-the-internal-system/1-gaussdb.md)
+    + [gs_backup](./reference-guide/tool-reference/tools-used-in-the-internal-system/2-gs_backup.md)
+    + [gs_basebackup](./reference-guide/tool-reference/tools-used-in-the-internal-system/3-gs_basebackup.md)
+    + [gs_ctl](./reference-guide/tool-reference/tools-used-in-the-internal-system/4-gs_ctl.md)
+    + [gs_initdb](./reference-guide/tool-reference/tools-used-in-the-internal-system/5-gs_initdb.md)
+    + [gs_install](./reference-guide/tool-reference/tools-used-in-the-internal-system/6-gs_install.md)
+    + [gs_install_plugin](/reference-guide/tool-reference/tools-used-in-the-internal-system/gs_install_plugin.md)
+    + [gs_install_plugin_local](/reference-guide/tool-reference/tools-used-in-the-internal-system/gs_install_plugin_local.md)
+    + [gs_postuninstall](./reference-guide/tool-reference/tools-used-in-the-internal-system/7-gs_postuninstall.md)
+    + [gs_preinstall](./reference-guide/tool-reference/tools-used-in-the-internal-system/8-gs_preinstall.md)
+    + [gs_sshexkey](./reference-guide/tool-reference/tools-used-in-the-internal-system/9-gs_sshexkey.md)
+    + [gs_tar](./reference-guide/tool-reference/tools-used-in-the-internal-system/10-gs_tar.md)
+    + [gs_uninstall](./reference-guide/tool-reference/tools-used-in-the-internal-system/11-gs_uninstall.md)
+    + [gs_upgradectl](./reference-guide/tool-reference/tools-used-in-the-internal-system/12-gs_upgradectl.md)
+    + [gs_expansion](./reference-guide/tool-reference/tools-used-in-the-internal-system/13-gs_expansion.md)
+    + [gs_dropnode](./reference-guide/tool-reference/tools-used-in-the-internal-system/14-gs_dropnode.md)
+    + [gs_probackup](./reference-guide/tool-reference/tools-used-in-the-internal-system/15-gs_probackup.md)
+    + [gstrace](./reference-guide/tool-reference/tools-used-in-the-internal-system/16-gstrace.md)
+    + [kdb5_util](./reference-guide/tool-reference/tools-used-in-the-internal-system/17-kdb5_util.md)
+    + [kadmin.local](./reference-guide/tool-reference/tools-used-in-the-internal-system/18-kadmin-local.md)
+    + [kinit](./reference-guide/tool-reference/tools-used-in-the-internal-system/19-kinit.md)
+    + [klist](./reference-guide/tool-reference/tools-used-in-the-internal-system/20-klist.md)
+    + [krb5kdc](./reference-guide/tool-reference/tools-used-in-the-internal-system/21-krb5kdc.md)
+    + [kdestroy](./reference-guide/tool-reference/tools-used-in-the-internal-system/22-kdestroy.md)
+    + [pg_config](./reference-guide/tool-reference/tools-used-in-the-internal-system/23-pg_config.md)
+    + [pg_controldata](./reference-guide/tool-reference/tools-used-in-the-internal-system/24-pg_controldata.md)
+    + [pg_recvlogical](./reference-guide/tool-reference/tools-used-in-the-internal-system/24.1-pg_recvlogical.md)
+    + [pg_resetxlog](./reference-guide/tool-reference/tools-used-in-the-internal-system/25-pg_resetxlog.md)
+    + [pg_archivecleanup](./reference-guide/tool-reference/tools-used-in-the-internal-system/26-pg_archivecleanup.md)
+    + [pssh](./reference-guide/tool-reference/tools-used-in-the-internal-system/27-pssh.md)
+    + [pscp](./reference-guide/tool-reference/tools-used-in-the-internal-system/28-pscp.md)
+    + [transfer.py](./reference-guide/tool-reference/tools-used-in-the-internal-system/29-transfer.py.md)
+  + [FAQ](./reference-guide/tool-reference/FAQ.md)
+  + [System Catalogs and Views Supported by gs_collector](./reference-guide/tool-reference/system-catalogs-and-views-supported-by-gs_collector.md)
diff --git a/product/en/docs-mogdb/v3.0/toc_performance.md b/product/en/docs-mogdb/v3.0/toc_performance.md
new file mode 100644
index 0000000000000000000000000000000000000000..d1159e592f69e74058dd2da829fcf4ee51f0cde6
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/toc_performance.md
@@ -0,0 +1,23 @@
+<!-- markdownlint-disable MD007 -->
+<!-- markdownlint-disable MD041 -->
+# MogDB Documentation 3.0
+
+## Performance Tuning
+
++ System Optimization
+  + [Optimizing OS Parameters](/performance-tuning/1-system/1-optimizing-os-parameters.md)
+  + [Optimizing Database Parameters](/performance-tuning/1-system/2-optimizing-database-parameters.md)
+  + [Configuring SMP](/performance-tuning/1-system/4-configuring-smp.md)
+  + [Configuring LLVM](/performance-tuning/1-system/3-configuring-llvm.md)
++ SQL Optimization
+  + [Query Execution Process](/performance-tuning/2-sql/1-query-execution-process.md)
+  + [Introduction to the SQL Execution Plan](/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md)
+  + [Tuning Process](/performance-tuning/2-sql/3-tuning-process.md)
+  + [Updating Statistics](/performance-tuning/2-sql/4-updating-statistics.md)
+  + [Reviewing and Modifying a Table Definition](/performance-tuning/2-sql/5-reviewing-and-modifying-a-table-definition.md)
+  + [Typical SQL Optimization Methods](/performance-tuning/2-sql/6-typical-sql-optimization-methods.md)
+  + [Experience in Rewriting SQL Statements](/performance-tuning/2-sql/7-experience-in-rewriting-sql-statements.md)
+  + [Resetting Key Parameters During SQL Tuning](/performance-tuning/2-sql/8-resetting-key-parameters-during-sql-tuning.md)
+  + [Hint-based Tuning](/performance-tuning/2-sql/9-hint-based-tuning.md)
++ [WDR Snapshot Schema](/performance-tuning/wdr-snapshot-schema.md)
++ [TPCC Performance Tuning Guide](/performance-tuning/TPCC-performance-tuning-guide.md)
diff --git a/product/en/docs-mogdb/v3.0/toc_quickstart.md b/product/en/docs-mogdb/v3.0/toc_quickstart.md
new file mode 100644
index 0000000000000000000000000000000000000000..1641c5ae184797aff0f58daca8daf6f448a6e074
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/toc_quickstart.md
@@ -0,0 +1,27 @@
+<!-- markdownlint-disable MD007 -->
+<!-- markdownlint-disable MD041 -->
+# MogDB Documentation 3.0
+
+## Quick Start
+
++ [MogDB Playground](/quick-start/mogdb-playground.md)
++ [Container-based MogDB Installation](/quick-start/container-based-installation.md)
++ [Installation on a Single Node](/quick-start/installation-on-a-single-node.md)
++ MogDB Access
+  + Use CLI to Access MogDB
+    + [gsql](/quick-start/mogdb-access/use-cli-to-access-mogdb/gsql.md)
+    + [pgcli](/quick-start/mogdb-access/use-cli-to-access-mogdb/pgcli.md)
+  + Use GUI to Access MogDB
+    + [Data Studio](/quick-start/mogdb-access/use-gui-tools-to-access-mogdb/datastudio.md)
+    + [DBeaver](/quick-start/mogdb-access/use-gui-tools-to-access-mogdb/dbeaver.md)
+  + Use Middleware to Access MogDB
+    + [Use WebLogic to Configure MogDB Data Sources](/quick-start/mogdb-access/use-middleware-to-access-mogdb/weblogic-configures-mogdb(postgresql)-data-source-reference.md)
+    + [Use WebSphere to Configure MogDB Data Sources](/quick-start/mogdb-access/use-middleware-to-access-mogdb/websphere-configures-mogdb(postgresql)-data-source-reference.md)
+  + Use Programming Language to Access MogDB
+    + [Java](/quick-start/mogdb-access/use-programming-language-to-access-mogdb/java.md)
+    + [C/C++](/quick-start/mogdb-access/use-programming-language-to-access-mogdb/c-cpp.md)
+    + [Python](/quick-start/mogdb-access/use-programming-language-to-access-mogdb/python.md)
+    + [Go](/quick-start/mogdb-access/use-programming-language-to-access-mogdb/go.md)
+    + [Rust](/quick-start/mogdb-access/use-programming-language-to-access-mogdb/rust.md)
+    + [NodeJS](/quick-start/mogdb-access/use-programming-language-to-access-mogdb/nodejs.md)
++ [Using Sample Dataset Mogila](/quick-start/mogila.md)
diff --git a/product/en/docs-mogdb/v3.0/toc_secure.md b/product/en/docs-mogdb/v3.0/toc_secure.md
new file mode 100644
index 0000000000000000000000000000000000000000..c4577a739863a0a58c0a4817fa91ccc6c771bbf9
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/toc_secure.md
@@ -0,0 +1,11 @@
+<!-- markdownlint-disable MD007 -->
+<!-- markdownlint-disable MD041 -->
+# MogDB Documentation 3.0
+
+## Security Guide
+
++ [Client Access Authentication](security-guide/security/1-client-access-authentication.md)
++ [Managing Users and Their Permissions](/security-guide/security/2-managing-users-and-their-permissions.md)
++ [Configuring Database Audit](/security-guide/security/3-configuring-database-audit.md)
++ [Setting Encrypted Equality Query](/security-guide/security/4-setting-encrypted-equality-query.md)
++ [Setting a Ledger Database](/security-guide/security/5-setting-a-ledger-database.md)
diff --git a/product/en/docs-mogdb/v3.0/toc_system-catalogs-and-functions.md b/product/en/docs-mogdb/v3.0/toc_system-catalogs-and-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..37e6b9532e6eea892beea446b66e3e8b1bd8266c
--- /dev/null
+++ b/product/en/docs-mogdb/v3.0/toc_system-catalogs-and-functions.md
@@ -0,0 +1,248 @@
+<!-- markdownlint-disable MD007 -->
+<!-- markdownlint-disable MD041 -->
+
+# MogDB Documentation 3.0
+
+## System Catalogs and Functions
+
++ System Catalogs and System Views
+  + [Overview of System Catalogs and System Views](./reference-guide/system-catalogs-and-system-views/overview-of-system-catalogs-and-system-views.md)
+  + System Catalogs
+    + [GS_AUDITING_POLICY](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY.md)
+    + [GS_AUDITING_POLICY_ACCESS](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY_ACCESS.md)
+    + [GS_AUDITING_POLICY_FILTERS](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY_FILTERS.md)
+    + [GS_AUDITING_POLICY_PRIVILEGES](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY_PRIVILEGES.md)
+    + [GS_CLIENT_GLOBAL_KEYS](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_CLIENT_GLOBAL_KEYS.md)
+    + [GS_CLIENT_GLOBAL_KEYS_ARGS](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_CLIENT_GLOBAL_KEYS_ARGS.md)
+    + [GS_COLUMN_KEYS](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_COLUMN_KEYS.md)
+    + [GS_COLUMN_KEYS_ARGS](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_COLUMN_KEYS_ARGS.md)
+    + [GS_ENCRYPTED_COLUMNS](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_ENCRYPTED_COLUMNS.md)
+    + [GS_ENCRYPTED_PROC](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_ENCRYPTED_PROC.md)
+    + [GS_GLOBAL_CHAIN](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_GLOBAL_CHAIN.md)
+    + [GS_MASKING_POLICY](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MASKING_POLICY.md)
+    + [GS_MASKING_POLICY_ACTIONS](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MASKING_POLICY_ACTIONS.md)
+    + [GS_MASKING_POLICY_FILTERS](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MASKING_POLICY_FILTERS.md)
+    + [GS_MATVIEW](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MATVIEW.md)
+    + [GS_MATVIEW_DEPENDENCY](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MATVIEW_DEPENDENCY.md)
+    + [GS_OPT_MODEL](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_OPT_MODEL.md)
+    + [GS_POLICY_LABEL](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_POLICY_LABEL.md)
+    + [GS_RECYCLEBIN](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_RECYCLEBIN.md)
+    + [GS_TXN_SNAPSHOT](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_TXN_SNAPSHOT.md)
+    + [GS_WLM_INSTANCE_HISTORY](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_INSTANCE_HISTORY.md)
+    + [GS_WLM_OPERATOR_INFO](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_OPERATOR_INFO.md)
+    + [GS_WLM_PLAN_ENCODING_TABLE](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_PLAN_ENCODING_TABLE.md)
+    + [GS_WLM_PLAN_OPERATOR_INFO](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_PLAN_OPERATOR_INFO.md)
+    + [GS_WLM_EC_OPERATOR_INFO](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_EC_OPERATOR_INFO.md)
+    + [PG_AGGREGATE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AGGREGATE.md)
+    + [PG_AM](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AM.md)
+    + [PG_AMOP](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AMOP.md)
+    + [PG_AMPROC](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AMPROC.md)
+    + [PG_APP_WORKLOADGROUP_MAPPING](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_APP_WORKLOADGROUP_MAPPING.md)
+    + [PG_ATTRDEF](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_ATTRDEF.md)
+    + [PG_ATTRIBUTE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_ATTRIBUTE.md)
+    + [PG_AUTHID](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AUTHID.md)
+    + [PG_AUTH_HISTORY](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AUTH_HISTORY.md)
+    + [PG_AUTH_MEMBERS](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AUTH_MEMBERS.md)
+    + [PG_CAST](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CAST.md)
+    + [PG_CLASS](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CLASS.md)
+    + [PG_COLLATION](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_COLLATION.md)
+    + [PG_CONSTRAINT](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CONSTRAINT.md)
+    + [PG_CONVERSION](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CONVERSION.md)
+    + [PG_DATABASE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DATABASE.md)
+    + [PG_DB_ROLE_SETTING](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DB_ROLE_SETTING.md)
+    + [PG_DEFAULT_ACL](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DEFAULT_ACL.md)
+    + [PG_DEPEND](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DEPEND.md)
+    + [PG_DESCRIPTION](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DESCRIPTION.md)
+    + [PG_DIRECTORY](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DIRECTORY.md)
+    + [PG_ENUM](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_ENUM.md)
+    + [PG_EXTENSION](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_EXTENSION.md)
+    + [PG_EXTENSION_DATA_SOURCE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_EXTENSION_DATA_SOURCE.md)
+    + [PG_FOREIGN_DATA_WRAPPER](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_FOREIGN_DATA_WRAPPER.md)
+    + [PG_FOREIGN_SERVER](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_FOREIGN_SERVER.md)
+    + [PG_FOREIGN_TABLE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_FOREIGN_TABLE.md)
+    + [PG_INDEX](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_INDEX.md)
+    + [PG_INHERITS](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_INHERITS.md)
+    + [PG_JOB](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_JOB.md)
+    + [PG_JOB_PROC](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_JOB_PROC.md)
+    + [PG_LANGUAGE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_LANGUAGE.md)
+    + [PG_LARGEOBJECT](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_LARGEOBJECT.md)
+    + [PG_LARGEOBJECT_METADATA](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_LARGEOBJECT_METADATA.md)
+    + [PG_NAMESPACE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_NAMESPACE.md)
+    + [PG_OBJECT](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OBJECT.md)
+    + [PG_OPCLASS](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OPCLASS.md)
+    + [PG_OPERATOR](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OPERATOR.md)
+    + [PG_OPFAMILY](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OPFAMILY.md)
+    + [PG_PARTITION](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_PARTITION.md)
+    + [PG_PLTEMPLATE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_PLTEMPLATE.md)
+    + [PG_PROC](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_PROC.md)
+    + [PG_RANGE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_RANGE.md)
+    + [PG_RESOURCE_POOL](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_RESOURCE_POOL.md)
+    + [PG_REWRITE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_REWRITE.md)
+    + [PG_RLSPOLICY](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_RLSPOLICY.md)
+    + [PG_SECLABEL](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SECLABEL.md)
+    + [PG_SHDEPEND](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SHDEPEND.md)
+    + [PG_SHDESCRIPTION](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SHDESCRIPTION.md)
+    + [PG_SHSECLABEL](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SHSECLABEL.md)
+    + [PG_STATISTIC](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_STATISTIC.md)
+    + [PG_STATISTIC_EXT](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_STATISTIC_EXT.md)
+    + [PG_SYNONYM](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SYNONYM.md)
+    + [PG_TABLESPACE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TABLESPACE.md)
+    + [PG_TRIGGER](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TRIGGER.md)
+    + [PG_TS_CONFIG](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_CONFIG.md)
+    + [PG_TS_CONFIG_MAP](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_CONFIG_MAP.md)
+    + [PG_TS_DICT](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_DICT.md)
+    + [PG_TS_PARSER](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_PARSER.md)
+    + [PG_TS_TEMPLATE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_TEMPLATE.md)
+    + [PG_TYPE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TYPE.md)
+    + [PG_USER_MAPPING](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_USER_MAPPING.md)
+    + [PG_USER_STATUS](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_USER_STATUS.md)
+    + [PG_WORKLOAD_GROUP](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_WORKLOAD_GROUP.md)
+    + [PLAN_TABLE_DATA](/reference-guide/system-catalogs-and-system-views/system-catalogs/PLAN_TABLE_DATA.md)
+    + [STATEMENT_HISTORY](/reference-guide/system-catalogs-and-system-views/system-catalogs/STATEMENT_HISTORY.md)
+  + System Views
+    + [GET_GLOBAL_PREPARED_XACTS](/reference-guide/system-catalogs-and-system-views/system-views/GET_GLOBAL_PREPARED_XACTS.md)
+    + [GS_AUDITING](/reference-guide/system-catalogs-and-system-views/system-views/GS_AUDITING.md)
+    + [GS_AUDITING_ACCESS](/reference-guide/system-catalogs-and-system-views/system-views/GS_AUDITING_ACCESS.md)
+    + [GS_AUDITING_PRIVILEGE](/reference-guide/system-catalogs-and-system-views/system-views/GS_AUDITING_PRIVILEGE.md)
+    + [GS_CLUSTER_RESOURCE_INFO](/reference-guide/system-catalogs-and-system-views/system-views/GS_CLUSTER_RESOURCE_INFO.md)
+    + [GS_INSTANCE_TIME](/reference-guide/system-catalogs-and-system-views/system-views/GS_INSTANCE_TIME.md)
+    + [GS_LABELS](/reference-guide/system-catalogs-and-system-views/system-views/GS_LABELS.md)
+    + [GS_MASKING](/reference-guide/system-catalogs-and-system-views/system-views/GS_MASKING.md)
+    + [GS_MATVIEWS](/reference-guide/system-catalogs-and-system-views/system-views/GS_MATVIEWS.md)
+    + [GS_SESSION_MEMORY](/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY.md)
+    + [GS_SESSION_CPU_STATISTICS](/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_CPU_STATISTICS.md)
+    + [GS_SESSION_MEMORY_CONTEXT](/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY_CONTEXT.md)
+    + [GS_SESSION_MEMORY_DETAIL](/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY_DETAIL.md)
+    + [GS_SESSION_MEMORY_STATISTICS](/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY_STATISTICS.md)
+    + [GS_SQL_COUNT](/reference-guide/system-catalogs-and-system-views/system-views/GS_SQL_COUNT.md)
+    + [GS_WLM_CGROUP_INFO](/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_CGROUP_INFO.md)
+    + [GS_WLM_PLAN_OPERATOR_HISTORY](/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_PLAN_OPERATOR_HISTORY.md)
+    + [GS_WLM_REBUILD_USER_RESOURCE_POOL](/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_REBUILD_USER_RESOURCE_POOL.md)
+    + [GS_WLM_RESOURCE_POOL](/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_RESOURCE_POOL.md)
+    + [GS_WLM_USER_INFO](/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_USER_INFO.md)
+    + [GS_STAT_SESSION_CU](/reference-guide/system-catalogs-and-system-views/system-views/GS_STAT_SESSION_CU.md)
+    + [GS_TOTAL_MEMORY_DETAIL](/reference-guide/system-catalogs-and-system-views/system-views/GS_TOTAL_MEMORY_DETAIL.md)
+    + [MPP_TABLES](/reference-guide/system-catalogs-and-system-views/system-views/MPP_TABLES.md)
+    + [PG_AVAILABLE_EXTENSION_VERSIONS](/reference-guide/system-catalogs-and-system-views/system-views/PG_AVAILABLE_EXTENSION_VERSIONS.md)
+    + [PG_AVAILABLE_EXTENSIONS](/reference-guide/system-catalogs-and-system-views/system-views/PG_AVAILABLE_EXTENSIONS.md)
+    + [PG_COMM_DELAY](/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_DELAY.md)
+    + [PG_COMM_RECV_STREAM](/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_RECV_STREAM.md)
+    + [PG_COMM_SEND_STREAM](/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_SEND_STREAM.md)
+    + [PG_COMM_STATUS](/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_STATUS.md)
+    + [PG_CONTROL_GROUP_CONFIG](/reference-guide/system-catalogs-and-system-views/system-views/PG_CONTROL_GROUP_CONFIG.md)
+    + [PG_CURSORS](/reference-guide/system-catalogs-and-system-views/system-views/PG_CURSORS.md)
+    + [PG_EXT_STATS](/reference-guide/system-catalogs-and-system-views/system-views/PG_EXT_STATS.md)
+    + [PG_GET_INVALID_BACKENDS](/reference-guide/system-catalogs-and-system-views/system-views/PG_GET_INVALID_BACKENDS.md)
+    + [PG_GET_SENDERS_CATCHUP_TIME](/reference-guide/system-catalogs-and-system-views/system-views/PG_GET_SENDERS_CATCHUP_TIME.md)
+    + [PG_GROUP](/reference-guide/system-catalogs-and-system-views/system-views/PG_GROUP.md)
+    + [PG_GTT_RELSTATS](/reference-guide/system-catalogs-and-system-views/system-views/PG_GTT_RELSTATS.md)
+    + [PG_GTT_STATS](/reference-guide/system-catalogs-and-system-views/system-views/PG_GTT_STATS.md)
+    + [PG_GTT_ATTACHED_PIDS](/reference-guide/system-catalogs-and-system-views/system-views/PG_GTT_ATTACHED_PIDS.md)
+    + [PG_INDEXES](/reference-guide/system-catalogs-and-system-views/system-views/PG_INDEXES.md)
+    + [PG_LOCKS](/reference-guide/system-catalogs-and-system-views/system-views/PG_LOCKS.md)
+    + [PG_NODE_ENV](/reference-guide/system-catalogs-and-system-views/system-views/PG_NODE_ENV.md)
+    + [PG_OS_THREADS](/reference-guide/system-catalogs-and-system-views/system-views/PG_OS_THREADS.md)
+    + [PG_PREPARED_STATEMENTS](/reference-guide/system-catalogs-and-system-views/system-views/PG_PREPARED_STATEMENTS.md)
+    + [PG_PREPARED_XACTS](/reference-guide/system-catalogs-and-system-views/system-views/PG_PREPARED_XACTS.md)
+    + [PG_REPLICATION_SLOTS](/reference-guide/system-catalogs-and-system-views/system-views/PG_REPLICATION_SLOTS.md)
+    + [PG_RLSPOLICIES](/reference-guide/system-catalogs-and-system-views/system-views/PG_RLSPOLICIES.md)
+    + [PG_ROLES](/reference-guide/system-catalogs-and-system-views/system-views/PG_ROLES.md)
+    + [PG_RULES](/reference-guide/system-catalogs-and-system-views/system-views/PG_RULES.md)
+    + [PG_SECLABELS](/reference-guide/system-catalogs-and-system-views/system-views/PG_SECLABELS.md)
+    + [PG_SETTINGS](/reference-guide/system-catalogs-and-system-views/system-views/PG_SETTINGS.md)
+    + [PG_SHADOW](/reference-guide/system-catalogs-and-system-views/system-views/PG_SHADOW.md)
+    + [PG_STATS](/reference-guide/system-catalogs-and-system-views/system-views/PG_STATS.md)
+    + [PG_STAT_ACTIVITY](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_ACTIVITY.md)
+    + [PG_STAT_ALL_INDEXES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_ALL_INDEXES.md)
+    + [PG_STAT_ALL_TABLES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_ALL_TABLES.md)
+    + [PG_STAT_BAD_BLOCK](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_BAD_BLOCK.md)
+    + [PG_STAT_BGWRITER](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_BGWRITER.md)
+    + [PG_STAT_DATABASE](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_DATABASE.md)
+    + [PG_STAT_DATABASE_CONFLICTS](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_DATABASE_CONFLICTS.md)
+    + [PG_STAT_USER_FUNCTIONS](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_USER_FUNCTIONS.md)
+    + [PG_STAT_USER_INDEXES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_USER_INDEXES.md)
+    + [PG_STAT_USER_TABLES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_USER_TABLES.md)
+    + [PG_STAT_REPLICATION](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_REPLICATION.md)
+    + [PG_STAT_SYS_INDEXES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_SYS_INDEXES.md)
+    + [PG_STAT_SYS_TABLES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_SYS_TABLES.md)
+    + [PG_STAT_XACT_ALL_TABLES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_ALL_TABLES.md)
+    + [PG_STAT_XACT_SYS_TABLES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_SYS_TABLES.md)
+    + [PG_STAT_XACT_USER_FUNCTIONS](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_USER_FUNCTIONS.md)
+    + [PG_STAT_XACT_USER_TABLES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_USER_TABLES.md)
+    + [PG_STATIO_ALL_INDEXES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_ALL_INDEXES.md)
+    + [PG_STATIO_ALL_SEQUENCES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_ALL_SEQUENCES.md)
+    + [PG_STATIO_ALL_TABLES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_ALL_TABLES.md)
+    + [PG_STATIO_SYS_INDEXES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_SYS_INDEXES.md)
+    + [PG_STATIO_SYS_SEQUENCES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_SYS_SEQUENCES.md)
+    + [PG_STATIO_SYS_TABLES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_SYS_TABLES.md)
+    + [PG_STATIO_USER_INDEXES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_USER_INDEXES.md)
+    + [PG_STATIO_USER_SEQUENCES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_USER_SEQUENCES.md)
+    + [PG_STATIO_USER_TABLES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_USER_TABLES.md)
+    + [PG_TABLES](/reference-guide/system-catalogs-and-system-views/system-views/PG_TABLES.md)
+    + [PG_TDE_INFO](/reference-guide/system-catalogs-and-system-views/system-views/PG_TDE_INFO.md)
+    + [PG_THREAD_WAIT_STATUS](/reference-guide/system-catalogs-and-system-views/system-views/PG_THREAD_WAIT_STATUS.md)
+    + [PG_TIMEZONE_ABBREVS](/reference-guide/system-catalogs-and-system-views/system-views/PG_TIMEZONE_ABBREVS.md)
+    + [PG_TIMEZONE_NAMES](/reference-guide/system-catalogs-and-system-views/system-views/PG_TIMEZONE_NAMES.md)
+    + [PG_TOTAL_MEMORY_DETAIL](/reference-guide/system-catalogs-and-system-views/system-views/PG_TOTAL_MEMORY_DETAIL.md)
+    + [PG_TOTAL_USER_RESOURCE_INFO](/reference-guide/system-catalogs-and-system-views/system-views/PG_TOTAL_USER_RESOURCE_INFO.md)
+    + [PG_TOTAL_USER_RESOURCE_INFO_OID](/reference-guide/system-catalogs-and-system-views/system-views/PG_TOTAL_USER_RESOURCE_INFO_OID.md)
+    + [PG_USER](/reference-guide/system-catalogs-and-system-views/system-views/PG_USER.md)
+    + [PG_USER_MAPPINGS](/reference-guide/system-catalogs-and-system-views/system-views/PG_USER_MAPPINGS.md)
+    + [PG_VARIABLE_INFO](/reference-guide/system-catalogs-and-system-views/system-views/PG_VARIABLE_INFO.md)
+    + [PG_VIEWS](/reference-guide/system-catalogs-and-system-views/system-views/PG_VIEWS.md)
+    + [PLAN_TABLE](/reference-guide/system-catalogs-and-system-views/system-views/PLAN_TABLE.md)
+    + [GS_FILE_STAT](/reference-guide/system-catalogs-and-system-views/system-views/GS_FILE_STAT.md)
+    + [GS_OS_RUN_INFO](/reference-guide/system-catalogs-and-system-views/system-views/GS_OS_RUN_INFO.md)
+    + [GS_REDO_STAT](/reference-guide/system-catalogs-and-system-views/system-views/GS_REDO_STAT.md)
+    + [GS_SESSION_STAT](/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_STAT.md)
+    + [GS_SESSION_TIME](/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_TIME.md)
+    + [GS_THREAD_MEMORY_CONTEXT](/reference-guide/system-catalogs-and-system-views/system-views/GS_THREAD_MEMORY_CONTEXT.md)
++ Functions and Operators
+  + [Logical Operators](./reference-guide/functions-and-operators/1-logical-operators.md)
+  + [Comparison Operators](./reference-guide/functions-and-operators/2-comparison-operators.md)
+  + [Character Processing Functions and Operators](./reference-guide/functions-and-operators/3-character-processing-functions-and-operators.md)
+  + [Binary String Functions and Operators](./reference-guide/functions-and-operators/4-binary-string-functions-and-operators.md)
+  + [Bit String Functions and Operators](./reference-guide/functions-and-operators/5-bit-string-functions-and-operators.md)
+  + [Mode Matching Operators](./reference-guide/functions-and-operators/6-mode-matching-operators.md)
+  + [Mathematical Functions and Operators](./reference-guide/functions-and-operators/7-mathematical-functions-and-operators.md)
+  + [Date and Time Processing Functions and Operators](./reference-guide/functions-and-operators/8-date-and-time-processing-functions-and-operators.md)
+  + [Type Conversion Functions](./reference-guide/functions-and-operators/9-type-conversion-functions.md)
+  + [Geometric Functions and Operators](./reference-guide/functions-and-operators/10-geometric-functions-and-operators.md)
+  + [Network Address Functions and Operators](./reference-guide/functions-and-operators/11-network-address-functions-and-operators.md)
+  + [Text Search Functions and Operators](./reference-guide/functions-and-operators/12-text-search-functions-and-operators.md)
+  + [JSON/JSONB Functions and Operators](./reference-guide/functions-and-operators/13-json-functions.md)
+  + [HLL Functions and Operators](./reference-guide/functions-and-operators/13.1-hll-functions-and-operators.md)
+  + [SEQUENCE Functions](./reference-guide/functions-and-operators/14-sequence-functions.md)
+  + [Array Functions and Operators](./reference-guide/functions-and-operators/15-array-functions-and-operators.md)
+  + [Range Functions and Operators](./reference-guide/functions-and-operators/16-range-functions-and-operators.md)
+  + [Aggregate Functions](./reference-guide/functions-and-operators/17-aggregate-functions.md)
+  + [Window Functions](./reference-guide/functions-and-operators/18-window-functions.md)
+  + [Security Functions](./reference-guide/functions-and-operators/19-security-functions.md)
+  + [Ledger Database Functions](./reference-guide/functions-and-operators/20.1-ledger-database-functions.md)
+  + [Encrypted Equality Functions](./reference-guide/functions-and-operators/20-encrypted-equality-functions.md)
+  + [Set Returning Functions](./reference-guide/functions-and-operators/21-set-returning-functions.md)
+  + [Conditional Expression Functions](./reference-guide/functions-and-operators/22-conditional-expressions-functions.md)
+  + [System Information Functions](./reference-guide/functions-and-operators/23-system-information-functions.md)
+  + System Administration Functions
+    + [Configuration Settings Functions](./reference-guide/functions-and-operators/24-system-management-functions/1-configuration-settings-functions.md)
+    + [Universal File Access Functions](./reference-guide/functions-and-operators/24-system-management-functions/2-universal-file-access-functions.md)
+    + [Server Signal Functions](./reference-guide/functions-and-operators/24-system-management-functions/3-server-signal-functions.md)
+    + [Backup and Restoration Control Functions](./reference-guide/functions-and-operators/24-system-management-functions/4-backup-and-restoration-control-functions.md)
+    + [Snapshot Synchronization Functions](./reference-guide/functions-and-operators/24-system-management-functions/5-snapshot-synchronization-functions.md)
+    + [Database Object Functions](./reference-guide/functions-and-operators/24-system-management-functions/6-database-object-functions.md)
+    + [Advisory Lock Functions](./reference-guide/functions-and-operators/24-system-management-functions/7-advisory-lock-functions.md)
+    + [Logical Replication Functions](./reference-guide/functions-and-operators/24-system-management-functions/8-logical-replication-functions.md)
+    + [Segment-Page Storage Functions](./reference-guide/functions-and-operators/24-system-management-functions/9.1-segment-page-storage-functions.md)
+    + [Other Functions](./reference-guide/functions-and-operators/24-system-management-functions/9-other-functions.md)
+    + [Undo System Functions](./reference-guide/functions-and-operators/24-system-management-functions/10-undo-system-functions.md)
+  + [Statistics Information Functions](./reference-guide/functions-and-operators/25-statistics-information-functions.md)
+  + [Trigger Functions](./reference-guide/functions-and-operators/26-trigger-functions.md)
+  + [Hash Function](./reference-guide/functions-and-operators/27.1-hash-function.md)
+  + [Prompt Message Function](./reference-guide/functions-and-operators/27.2-prompt-message-function.md)
+  + [Global Temporary Table Functions](./reference-guide/functions-and-operators/27-global-temporary-table-functions.md)
+  + [Fault Injection System Function](./reference-guide/functions-and-operators/28.1-fault-injection-system-function.md)
+  + [AI Feature Functions](./reference-guide/functions-and-operators/28-ai-feature-functions.md)
+  + [Dynamic Data Masking Functions](./reference-guide/functions-and-operators/29.1-dynamic-data-masking-functions.md)
+  + [Other System Functions](./reference-guide/functions-and-operators/29-other-system-functions.md)
+  + [Internal Functions](./reference-guide/functions-and-operators/30-internal-functions.md)
+  + [Obsolete Functions](./reference-guide/functions-and-operators/31-obsolete-functions.md)
diff --git a/product/zh/docs-mogdb/v2.1/faqs/application-development-faqs.md b/product/zh/docs-mogdb/v2.1/faqs/application-development-faqs.md
new file mode 100644
index 0000000000000000000000000000000000000000..0e55d1a854cc7000604d06245c2dc82a758e6ff0
--- /dev/null
+++ b/product/zh/docs-mogdb/v2.1/faqs/application-development-faqs.md
@@ -0,0 +1,8 @@
+---
+title: 应用开发FAQs
+summary: 应用开发FAQs
+author: Guo Huan
+date: 2021-09-26
+---
+
+正在编写中……
diff --git a/product/zh/docs-mogdb/v3.0/about-mogdb/MogDB-compared-to-openGauss.md b/product/zh/docs-mogdb/v3.0/about-mogdb/MogDB-compared-to-openGauss.md
new file mode 100644
index 0000000000000000000000000000000000000000..1b94412228120c9a0214d6138a410add40a33fd1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/about-mogdb/MogDB-compared-to-openGauss.md
@@ -0,0 +1,134 @@
+---
+title: MogDB与openGauss
+summary: MogDB与openGauss
+author: Guo Huan
+date: 2021-03-30
+---
+
+# MogDB与openGauss
+
+<br/>
+
+## MogDB与openGauss的关系
+
+MogDB是在openGauss开源内核的基础上封装和改善的对于企业应用更加友好的企业级数据库。在openGauss内核的基础上，MogDB增加了MogHA组件，用于进行主备架构下高可用的自动化管理，这对于企业级应用来说是至关重要的。同时也同步研发了MogDB Manager管理软件，其中包括备份恢复，监控，自动化安装等等针对企业级易用性需求的组件。
+
+MogDB是一款商业产品，按照既定的License价格体系销售，同时享有云和恩墨的专业服务支持。
+
+<br/>
+
+## 关于openGauss
+
+openGauss是一款开源关系型数据库管理系统，openGauss内核源自PostgreSQL，采用木兰宽松许可证v2发行。openGauss内核是开源的，任何人任何组织都可以自行下载源码进行编译安装使用，无需任何费用；openGauss社区也会定期发布编译好的二进制安装文件，目前的发布策略是每年发布一个稳定常支持版本（每年3月底）和一个新功能激进版本（每年9月底）。
+
+openGauss是一个单机数据库，具备关系型数据库的基本功能，以及企业特性的增强功能。
+
+更多详情请访问openGauss官方网站：<https://opengauss.org>
+
+<br/>
+
+### 基本功能
+
+- 标准SQL支持
+
+    支持标准的SQL92/SQL99/SQL2003/SQL2011规范，支持GBK和UTF-8字符集，支持SQL标准函数与分析函数，支持存储过程。
+
+- 数据库存储管理功能
+
+    支持表空间，可以把不同表规划到不同的存储位置。
+
+- 提供主备双机
+
+    事务支持ACID特性、单节点故障恢复、双机数据同步，双机故障切换等。
+
+- 应用程序接口
+
+    支持标准JDBC 4.0的特性、ODBC 3.5特性。
+
+- 管理工具
+
+    提供安装部署工具、实例启停工具、备份恢复工具。
+
+- 安全管理
+
+    支持SSL安全网络连接、用户权限管理、密码管理、安全审计等功能，保证数据库在管理层、应用层、系统层和网络层的安全性。
+
+<br/>
+
+### 企业级增强特性
+
+- 数据分区
+
+    数据分区是数据库产品普遍具备的功能。在openGauss中，数据分区是对数据按照用户指定的策略对数据做的水平分表，将表按照指定范围划分为多个数据互不重叠的部分（Partition）。
+
+- 向量化执行和行列混合引擎
+
+    在大宽表，数据量比较大、查询经常关注某些列的场景中，行存储引擎查询性能比较差。例如气象局的场景，单表有200~800个列，查询经常访问10个列，在类似这样的场景下，向量化执行技术和列存储引擎可以极大的提升性能和减少存储空间。
+
+- 高可靠事务处理
+
+    openGauss提供事务管理功能，保证事务的ACID特性。为了在主节点出现故障时尽可能地不中断服务，openGauss提供了主备双机高可靠机制。通过保护关键用户程序对外不间断提供服务，把因为硬件、软件和人为造成的故障对业务的影响程度降到最低，以保证业务的持续性。
+
+- 高并发&高性能
+
+    openGauss通过服务器端的线程池，可以支持1W并发连接。通过NUMA化内核数据结构，支持线程亲核性处理，可以支持百万级tpmC。通过页面的高效冷热淘汰，支持T级别大内存缓冲区管理。通过CSN快照，去除快照瓶颈，实现多版本访问，读写互不阻塞。通过增量检查点，避免全页写导致的性能波动，实现业务性能平稳运行。
+
+- SQL自诊断
+
+    通过执行查询对应的explain performance，获得对应执行计划，是一种十分有效的定位查询性能问题的方法。但是这种方法需要修改业务逻辑，同时输出的日志量大，问题定位的效率依赖于人员的经验。SQL自诊断为用户提供了另一种更为高效易用的性能问题定位方法。
+
+- 全密态数据库等值查询
+
+    密态数据库允许客户端对客户端应用程序内的敏感数据进行加密。在查询期间，整个业务数据流在数据处理过程中都是以密文形态存在。优势如下:
+
+  - 保护数据在云上全生命周期的隐私安全；
+  - 通过将密钥掌握在用户自己手上，实现公有云、消费者云以及开发用户的用户信任问题；
+  - 让云数据库借助全密态能力更好的遵守个人隐私保护方面的法律法规。
+
+- 内存表
+
+    内存表把数据全部缓存在内存中，所有数据访问实现免锁并发，实现数据处理的极致性能，满足实时性严苛要求场景。
+
+- 主备双机
+
+    主备双机支持同步和异步复制，应用可以根据业务场景选择合适的部署方式。同步复制保证数据的高可靠，一般需要一主两备部署，同时对性能有一定影响。异步复制一主一备部署即可，对性能影响小，但异常时可能存在数据丢失。openGauss支持页面损坏的自动修复，在主机页面发生损坏时，能够自动从备机修复损坏页面。openGauss支持备机并行日志恢复，尽量降低主机故障时业务不可用的时间。
+
+    同时，如果按照主备模式部署，并打开备机可读功能后，备机将能够提供读操作，但不支持写操作（如建表、插入数据、删除数据等），从而缓解主机上的压力。
+
+- 具备AI能力
+
+  - 参数自动调优
+  - 慢SQL发现
+  - 索引推荐
+  - 时序预测与异常检测
+  - 支持DB4AI功能
+  - SQL执行时间预测
+  - 数据库监控
+
+- 逻辑日志复制
+
+    在逻辑复制中把主库称为源端库，备库称为目标端数据库，源端数据库根据预先指定好的逻辑解析规则对WAL文件进行解析，把DML操作解析成一定的逻辑变化信息（标准SQL语句），源端数据库把标准SQL语句发给目标端数据库，目标端数据库收到后进行应用，从而实现数据同步。逻辑复制只有DML操作。逻辑复制可以实现跨版本复制，异构数据库复制，双写数据库复制，表级别复制。
+
+- 支持WDR自动性能分析报告
+
+    定时主动分析run日志和WDR报告（自动后台生成，可由关键指标阈值如CPU占用率、内存占用率、长SQL比例等触发），并生成html、pdf等格式的报告。能自动生成性能报告。WDR(Workload Diagnosis Report)基于两次不同时间点系统的性能快照数据， 生成这两个时间点之间的性能表现报表，用于诊断数据库内核的性能故障。
+
+- 增量备份/恢复（beta）
+
+    支持对数据库进行全量备份和增量备份，支持对备份数据进行管理，查看备份状态。支持增量备份的合并，过期备份的删除。数据库服务器动态跟踪页面更改，每当一个关系页被更新时，这个页就会被标记为需要备份。增量备份功能需要打开GUC参数 enable_cbm_tracking，以便允许服务器跟踪修改页。
+
+- 恢复到指定时间点（PITR）
+
+    时间点恢复(Point In Time Recovery)基本原理是通过基础热备 + WAL预写日志 + WAL归档日志进行备份恢复。重放WAL记录的时候可以在任意点停止重放，这样就有一个在任意时间的数据库一致的快照。即可以把数据库恢复到自开始备份以来的任意时刻的状态。在恢复时可以指定恢复的停止点位置为TID，时间和LSN。
+
+<br/>
+
+## MogDB的优势
+
+openGauss是单机系统，在这样的系统架构中，业务数据存储在单个物理节点上，数据访问任务被推送到服务节点执行，通过服务器的高并发，实现对数据处理的快速响应。同时通过日志复制可以把数据复制到备机，提供数据的高可靠和读扩展。
+
+openGauss为单一数据库内核，若要在正式的商业项目上使用，还需要构筑数据库监控、主备切换等完整工具链的能力。
+
+在产品层面，MogDB在openGauss原有功能的基础上增加了MogHA企业级高可用组件，以及功能丰富的图形化管理工具MogDB Manager，并在既定路线上持续不断对openGauss内核进行增强。MogDB可最大限度地保障多机房高可用部署能力，4路服务器上可以达到250万tpmC。MogDB Manager包含多种实用组件，如MTK数据库迁移、MIT性能监控、RWT性能压测、PTK自动化部署等，极大程度上完善了openGauss开源数据库的不足之处，丰富了各项企业级功能。
+
+在服务层面，云和恩墨拥有数十年的数据库运维经验，可提供完整的兜底服务，确保数据库更加稳定，应用改造更加平滑，风险更小，弥补openGauss开源数据库人力运维不足的劣势，同时降低维护成本。
diff --git a/product/zh/docs-mogdb/v3.0/about-mogdb/mogdb-release-notes.md b/product/zh/docs-mogdb/v3.0/about-mogdb/mogdb-release-notes.md
new file mode 100644
index 0000000000000000000000000000000000000000..48345360b3e4d241944c1083865a7c11bac73c54
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/about-mogdb/mogdb-release-notes.md
@@ -0,0 +1,347 @@
+---
+title: MogDB 2.1 发行说明
+summary: MogDB 2.1 发行说明
+author: Guo Huan
+date: 2021-12-06
+---
+
+# MogDB 2.1 发行说明
+
+## 1. 版本说明
+
+MogDB 2.1版本基于MogDB 2.0版本进一步增强，并合入了openGauss 2.1.0版本的新增特性。
+
+> 说明：MogDB 2.1是Preview版本，该版本生命周期为半年。
+
+## 2. 新增特性
+
+### 2.1 集成openGauss 2.1.0版本新增特性
+
+- 存储过程兼容性增强
+- SQL引擎能力增强
+- 支持Ustore存储引擎
+- 支持段页式存储
+- 基于Paxos分布式一致性协议的高可用
+- AI4DB和DB4AI竞争力持续构筑
+- 日志框架及错误码整改
+- JDBC客户端负载均衡及读写分离
+- 支持cmake脚本编译
+- 列存表支持主键唯一键约束
+- 支持jsonb数据类型
+- 支持unique sql自动淘汰
+- UCE故障感知
+- 支持GB18030字符集
+- 备机catch优化
+- 客户端工具gsql支持readline命令自动补齐
+- 动态数据脱敏
+- 支持国密算法
+- 防篡改账本数据库
+- 内置角色和权限管理机制
+- 透明加密
+- 全密态数据库增强
+- 支持dblink
+- 支持Ubuntu系统
+- 支持Hash索引
+- upsert支持子查询
+- min/max函数支持ip地址类型
+- 增加array_remove/array_replace/first/last函数
+- Data Studio客户端工具适配内核特性
+
+### 2.2 x86架构性能优化
+
+ 优化x86架构下的多核性能，TPC-C高并发下性能达到PostgreSQL 14的1.5-5倍，主要优化点有：
+
+- 支持NUMA绑核
+- 无锁WAL
+- Cache友好数据结构
+
+### 2.3 在线创建及重建索引
+
+支持在执行create index和reindex index时指定CONCURRENTLY选项，以不阻塞DML语句执行的方式创建和重建索引，提升索引的可维护性。支持普通表上的索引和分区表全局索引的在线创建和重建。
+
+相比于普通的创建和重建索引，在线创建和重建的方式可能需要更长的时间才能完成。
+
+列存表上的索引、分区表本地索引和临时表上的索引不支持在线方式创建索引及重建。
+
+**相关页面**
+
+- [CREATE INDEX](50-CREATE-INDEX#CONCURRENTLY)
+- [REINDEX](117-REINDEX#CONCURRENTLY)
+
+### 2.4 增强Oracle兼容能力
+
+#### 2.4.1 支持Orafce插件
+
+> 说明：需要用户下载plugin包 ，并手工安装使用。
+
+通过集成orafce插件，支持以下Oracle兼容语法：
+
+- SQL Queries
+  - DUAL table
+- SQL Functions
+  - Mathematical functions
+    - BITAND
+    - COSH
+    - SINH
+    - TANH
+  - String functions
+    - INSTR
+    - LENGTH
+    - LENGTHB
+    - LPAD
+    - LTRIM
+    - NLSSORT
+    - REGEXP_COUNT
+    - REGEXP_INSTR
+    - REGEXP_LIKE
+    - REGEXP_SUBSTR
+    - REGEXP_REPLACE
+    - RPAD
+    - RTRIM
+    - SUBSTR
+    - SUBSTRB
+  - Date/time functions
+    - ADD_MONTHS
+    - DBTIMEZONE
+    - LAST_DAY
+    - MONTHS_BETWEEN
+    - NEXT_DAY
+    - ROUND
+    - SESSIONTIMEZONE
+    - SYSDATE
+    - TRUNC
+  - Data type formatting functions
+    - TO_CHAR
+    - TO_DATE
+    - TO_MULTI_BYTE
+    - TO_NUMBER
+    - TO_SINGLE_BYTE
+  - Conditional expressions
+    - DECODE
+    - LNNVL
+    - NANVL
+    - NVL
+    - NVL2
+  - Aggregate functions
+    - LISTAGG
+    - MEDIAN
+  - Functions that return internal information
+    - DUMP
+- SQL Operators
+  - Datetime operator
+- Packages
+  - DBMS_ALERT
+  - DBMS_ASSERT
+  - DBMS_OUTPUT
+  - DBMS_PIPE
+  - DBMS_RANDOM
+  - DBMS_UTILITY
+  - UTL_FILE
+
+**相关页面**
+
+- [orafce](orafce-user-guide)
+
+#### 2.4.2 支持connect by语法
+
+提供兼容oracle的connect by语法，实现层级结构的数据查询控制，并展示等级、循环、起始层级等。
+
+提供oracle兼容的层级查询功能，可以按照指定的连接关系，起始条件等按照树状结构展示数据内容，数据层级，路径等。
+
+通过start with条件指定层级查询的根行，根据这些行进行递归查询来获取所有子行，以及子行的子行等。
+
+通过connect by条件指定层级间父行与子行关系，来确定每一行的满足条件的所有子行。
+
+如果存在连接，无论是连接语句，还是from或where子句中，先获取连接后的结果集，然后再进行层级查询。
+
+语句中如果存在where过滤条件，先执行层级查询后再将结果集进行过滤，而不是过滤掉不满足的行以及其所有子行。
+
+可以通过level伪列查看该行所在层级，sys_connect_by_path查看从根行到该行的路径，以及connect_by_root查看根行等辅助功能。
+
+**相关页面**
+
+- [CONNECT BY](139-CONNECT-BY)
+
+#### 2.4.3 可更新视图
+
+支持可更新视图，用户可以对视图进行Insert/Update/Delete操作，更新操作会直接作用到视图对应基表。
+
+不是所有视图都可更新，视图中的行与基表中的行必须要是一一对应关系，即视图的内容不能是基于聚合或窗口函数创建而来。
+
+对于多表连接的视图，如果某一个基表的主键（唯一键）可以作为视图的主键（唯一键），则该视图也支持更新，更新结果作用到主键来源的基表。
+
+**相关页面**
+
+- [支持updatable-views](overview-of-system-catalogs-and-system-views#支持updatable-views)
+
+#### 2.4.4 重建视图时变更列
+
+在视图重建时，支持减少列、更改列名操作，本命令仅对非物化视图有效。
+
+**相关页面**
+
+- [CREATE VIEW](70-CREATE-VIEW#replace)
+
+#### 2.4.5 支持systimestamp函数
+
+返回数据库所在服务器的当前系统日期和时间，以及时区信息。
+
+**相关页面**
+
+- [时间和日期处理函数和操作符](8-date-and-time-processing-functions-and-operators#systimestamp)
+
+#### 2.4.6 支持sys_guid函数
+
+系统根据当前时间和机器码，生成并返回一个16字节的全局唯一标识符。
+
+**相关页面**
+
+- [系统信息函数](23-system-information-functions#sys_guid)
+
+### 2.5 新增支持PostgreSQL插件
+
+> 说明：需要用户下载plugin包 ，并手工安装使用。
+
+- [pg_repack插件](pg_repack-user-guide)：通过触发器机制，提供在线重建表的功能，主要用于在线缩减表中的空闲空间大小。
+- [wal2json插件](wal2json-user-guide)：通过逻辑复制机制，以json形态提供持续的数据变更内容，主要用于异构复制等情况。
+- [pg_trgm插件](pg_trgm-user-guide)：实现trgm分词算法，实现更好的全文检索能力。
+- [pg_prewarm插件](pg_prewarm-user-guide)：将指定的数据表预先缓存到共享内存中，加快数据的访问速度。
+- [pg_bulkload插件](pg_bulkload-user-guide)：不经过共享内存直接加载数据到数据文件中，加快了数据库批量导入的速度。
+
+### 2.6 支持读扩展
+
+> 说明：配套ShardingSphere 5.1.0及后续版本，需要用户手工下载安装。
+
+MogDB通过集成ShardingSphere的Proxy来支持读扩展能力：
+
+- 读写事务自动路由到主库执行，只读事务自动路由到备库执行；在有更高读一致性要求场景下，也可以通过hint控制只读事务也路由到主库执行；
+
+- 支持自动识别并配置读写节点，无需配置主备角色，在配置列表中自动发现主备库；
+
+- 支持切换后自动识别主备角色，无需额外操作，自动识别新的主备角色并正确路由；
+
+- 支持备节点的自动负载均衡：当备库宕机恢复或者新备库加入时，在备库复制状态正常后，会自动加入到读负载均衡中；
+
+### 2.7 其他
+
+- nlssort函数支持GBK字符集生僻字按拼音排序
+
+  **相关页面**：[SELECT](125-SELECT#nlssort)
+
+- ALTER SEQUENCE支持修改increment
+
+  **相关页面**：[ALTER SEQUENCE](16-ALTER-SEQUENCE#increment)
+
+- 对于TIMESTAMP WITH TIME ZONE类型，可以在TO_CHAR使用TZH，TZM，TZD，TZR参数来输出时区信息
+
+  **相关页面**：[类型转换函数](9-type-conversion-functions#to_char)
+
+### 2.8 Preview特性
+
+> 说明：Preview特性需要通过以下方式手动开启。
+>
+> ```sql
+> alter system set enable_poc_feature = on;
+> -- 或
+> alter system set enable_poc_feature to on;
+> -- 或在MogDB数据目录下的postgresql.conf配置文件中加入enable_poc_feature = on
+> -- 重启后生效
+> ```
+
+#### 2.8.1 行存表压缩
+
+支持在创建行存表(astore)时指定是否为压缩表，对于开启压缩的行存表，系统自动对表数据进行压缩，以节省存储空间。当往压缩表写入数据时，系统自动根据每列数据的特征选择合适的压缩算法，用户也可以直接指定每一列使用的压缩算法。
+
+实际压缩率和数据内容强相关，典型场景下可达到50%的压缩率；开启压缩特性后有一定性能损耗，典型TPC-C模型下性能损耗在5%以内，实际性能影响取决于实际系统负载情况。
+
+对于非压缩表，也可通过Alter Table的方式修改为压缩表，对于后续新写入的数据将自动进行压缩。
+
+**相关页面**
+
+- [CREATE TABLE](60-CREATE-TABLE#COMPRESSION)
+- [ALTER TABLE](22-ALTER-TABLE#COMPRESS)
+
+#### 2.8.2 二级分区
+
+支持创建二级分区表，数据自动按照分区方式进行分区存储，以提升大数据量下的存储和查询效率，支持的二级分区组合有：
+
+- List-List
+- List-Range
+- List-Hash
+- Range-List
+- Range-Range
+- Range-Hash
+
+支持对单个Partition和SubPartition进行查询；
+
+支持对Partition Key，SubPartition Key或其组合条件进行分区裁剪，进一步优化分区查询效率；
+
+支持对分区表或一级分区进行truncate，vacuum 操作；
+
+Update操作时，支持数据跨分区移动（不支持Partition/SubPartition Key为List或Hash分区类型）；
+
+支持对二级分区的备份恢复。
+
+**相关页面**
+
+- [CREATE TABLE SUBPARTITION](62.1-CREATE-TABLE-SUBPARTITION)
+- [ALTER TABLE SUBPARTITION](23.1-ALTER-TABLE-SUBPARTITION)
+
+<br/>
+
+## 3. 修复缺陷
+
+### 3.1 集成openGauss 2.1.0版本修复缺陷
+
+- [I435UP](https://gitee.com/opengauss/openGauss-server/issues/I435UP) explain语句执行报错
+- [I44QS6](https://gitee.com/opengauss/openGauss-server/issues/I44QS6) 执行函数select get_local_active_session() limit 1 ;数据库挂掉
+- [I4566H](https://gitee.com/opengauss/openGauss-server/issues/I4566H) 分区表拆分分区update global index 后查询结果与master版本不一致
+- [I45822](https://gitee.com/opengauss/openGauss-server/issues/I45822) 全局临时表的GPC全局计划缓存信息查询存在问题
+- [I442TY](https://gitee.com/opengauss/openGauss-server/issues/I442TY) PITR指定时间戳恢复失败
+- [I45T7A](https://gitee.com/opengauss/openGauss-server/issues/I45T7A) 环境变量分离方式安装的数据库，远程备份异常
+- [I464G5](https://gitee.com/opengauss/openGauss-server/issues/I464G5) gs_ctl build备机重建指定非实例目录失败报错信息不一致
+- [I45TTB](https://gitee.com/opengauss/openGauss-server/issues/I45TTB) file_fdw目前不支持的文件类型创建外表成功，未进行相应报错
+- [I491CN](https://gitee.com/opengauss/openGauss-server/issues/I491CN) cidr类型的网络地址子网掩码为32时，在函数中调用max时报
+- [I496VN](https://gitee.com/opengauss/openGauss-server/issues/I496VN) 备机xlog大量堆积后，修正归档地址，归档失败
+- [I49HRV](https://gitee.com/opengauss/openGauss-server/issues/I49HRV) 开启备机归档，备机归档慢，switchover后新主机异常慢
+- [I492W4](https://gitee.com/opengauss/openGauss-server/issues/I492W4) om安装的数据库，进行mysql_fdw和oracle_fdw外表相关操作数据库core掉
+- [I498QT](https://gitee.com/opengauss/openGauss-server/issues/I498QT) 最大可用模式，同步备参数为ANY2情况下，主机持续压力的情况下，kill-9停止其中一个同步备，主机事务阻塞2s
+- [I49L15](https://gitee.com/opengauss/openGauss-server/issues/I49L15) 开启2备机归档，减容+扩容其中一个节点，另一个节点归档异常
+- [I43MTG](https://gitee.com/opengauss/openGauss-server/issues/I43MTG) 新增函数开发者指南无相关资料
+- [I42YW8](https://gitee.com/opengauss/openGauss-server/issues/I42YW8) upsert子查询相关资料未补充
+- [I45WDH](https://gitee.com/opengauss/openGauss-server/issues/I45WDH) file_fdw，不支持fixed格式，在开发者指南支持类型应该去掉相关说明
+- [I484J0](https://gitee.com/opengauss/openGauss-server/issues/I484J0) gs_initdb -T参数未增加校验，且按照指导手册设置后取值不正确
+- [I471CS](https://gitee.com/opengauss/openGauss-server/issues/I471CS) 数据库pgxc_node_name存在‘-’字符时，数据库异常退出，存在残留临时表未清理干净时，无法自动清理和vacuum
+- [I40QM1](https://gitee.com/opengauss/openGauss-server/issues/I40QM1) 执行gs_basebackup过程中备节点异常，gs_basebackup进程阻塞无法退出
+- [I3RTQK](https://gitee.com/opengauss/openGauss-server/issues/I3RTQK) 备节点使用gs_basebackup备份失败，提示could not fetch mot checkpoint info: , status:7
+
+### 3.2 MogDB 2.1.0版本修复缺陷
+
+- gs_probackup恢复数据库时提示which doesn't support recovery_target_lsn
+- Statement_history表无法清理
+- 模式级联删除操作引起数据库异常宕机
+- gsql中\d无法查询到同义词对应的表或视图的字段信息
+- lengthb函数不支持blob等大对象字段
+- 在开启sha256验证以后原先md5加密的用户仍然可以通过md5验证成功登陆
+- MogDB中嵌套存储过程内部的raise输出过于细节
+
+### 3.3 MogDB 2.1.1版本修复缺陷
+
+MogDB 2.1.1是MogDB 2.1.0的补丁版本，于2022年3月22日发布，在MogDB 2.1.0的基础上修复如下内容：
+
+- 修复pg_encoding_to_char()函数由于参数溢出导致的coredump的缺陷
+- 修复connect by语句作为查询子句时产生的coredump的缺陷
+- 修复在x86平台上connect by语句order by level查询数据顺序不一致的缺陷
+
+## 4. 兼容性
+
+本版本支持以下操作系统及CPU架构组合：
+
+| 操作系统              | CPU架构                                       |
+| --------------------- | --------------------------------------------- |
+| CentOS 7.x            | X86_64（Intel，AMD，海光，兆芯）              |
+| Redhat 7.x            | X86_64（Intel，AMD，海光，兆芯）              |
+| openEuler 20.03LTS    | ARM（鲲鹏）、X86_64（Intel，AMD，海光，兆芯） |
+| 银河麒麟V10           | ARM（鲲鹏）、X86_64（Intel，AMD，海光，兆芯） |
+| 统信UOS V20-D / V20-E | ARM（鲲鹏）、X86_64（Intel，AMD，海光，兆芯） |
+| 统信UOS V20-A         | X86_64（Intel，AMD，海光，兆芯）              |
diff --git a/product/zh/docs-mogdb/v3.0/about-mogdb/open-source-components/1-enhanced-opengauss-kernel.md b/product/zh/docs-mogdb/v3.0/about-mogdb/open-source-components/1-enhanced-opengauss-kernel.md
new file mode 100644
index 0000000000000000000000000000000000000000..ae892da7bba0acddd0eeceb013760c9130915779
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/about-mogdb/open-source-components/1-enhanced-opengauss-kernel.md
@@ -0,0 +1,12 @@
+---
+title: 增强的openGauss内核
+summary: 增强的openGauss内核
+author: Liuxu
+date: 2021-06-09
+---
+
+# 增强的openGauss内核
+
+<br/>
+
+MogDB是在openGauss开源内核的基础上封装和改善的对于企业应用更加友好的企业级数据库。在openGauss内核的基础上，MogDB增加了MogHA、时序（应对IoT场景）、分布式（实现每个数据节点为一个openGauss内核的分布式环境）、Oracle视图兼容（DBA_和V$视图）等多种插件，其中MogHA插件用于进行主备架构下高可用的自动化管理，对于企业级应用来说是至关重要的。同时也同步研发了MogDB Manager管理软件，其中包括备份恢复、性能监控，健康检查工具包、自动化部署、数据库迁移、数据同步、兼容性分析、性能压测和极限数据恢复多种针对企业级易用性需求的组件。
diff --git a/product/zh/docs-mogdb/v3.0/about-mogdb/open-source-components/2-docker-based-mogdb.md b/product/zh/docs-mogdb/v3.0/about-mogdb/open-source-components/2-docker-based-mogdb.md
new file mode 100644
index 0000000000000000000000000000000000000000..f5836061610347664c79a667c874b690ce4d9f9c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/about-mogdb/open-source-components/2-docker-based-mogdb.md
@@ -0,0 +1,37 @@
+---
+title: 容器版本的MogDB
+summary: 容器版本的MogDB
+author: Liuxu
+date: 2021-06-09
+---
+
+# 容器版本的MogDB
+
+<br/>
+
+## 特点
+
+- 随着每一个MogDB的版本变化，第一时间发布镜像的新版本。
+- 容器版本数据库镜像内置最佳实践的初始化参数配置。
+- 容器版本数据库同时支持x86平台和ARM平台。
+- MogDB 2.1容器版支持最新版的compat-tools和插件功能。
+
+**目前已经支持x86-64和ARM64两种架构，请根据您宿主机的机器架构获取对应的容器镜像。**
+
+从2.0版本开始（包括2.0版本）
+
+- x86-64架构的MogDB运行在[Ubuntu 18.04操作系统](https://ubuntu.com/)中
+- ARM64架构的MogDB运行在[Debian 10 操作系统](https://www.debian.org/)中
+
+在1.1.0版本之前（包括1.1.0版本）
+
+- x86-64架构的MogDB运行在[CentOS 7.6操作系统](https://www.centos.org/)中
+- ARM64架构的MogDB运行在[openEuler 20.03 LTS操作系统](https://openeuler.org/zh/)中
+
+<br/>
+
+## 如何使用本镜像
+
+您可以从下方获取容器版本的详细内容：
+
+[安装指南-容器化安装](docker-installation)
diff --git a/product/zh/docs-mogdb/v3.0/about-mogdb/open-source-components/5-wal2json-extention-for-mogdb&opengauss.md b/product/zh/docs-mogdb/v3.0/about-mogdb/open-source-components/5-wal2json-extention-for-mogdb&opengauss.md
new file mode 100644
index 0000000000000000000000000000000000000000..485a45c4f91457f8623292b4fc90fe5d7d7f548d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/about-mogdb/open-source-components/5-wal2json-extention-for-mogdb&opengauss.md
@@ -0,0 +1,125 @@
+---
+title: wal2json extention for MogDB&openGauss
+summary: wal2json extention for MogDB&openGauss
+author: Guo Huan
+date: 2021-06-02
+---
+
+# wal2json extention for MogDB&openGauss
+
+## 组件获取
+
+<https://gitee.com/enmotech/wal2json>
+
+<br/>
+
+## 逻辑解码（wal2json）
+
+基于MogDB和openGauss的wal2json插件，可以将逻辑日志文件输出为JSON格式供您查看。
+
+<br/>
+
+## 前提条件
+
+已设置实例参数wal_level = logical。
+
+<br/>
+
+## 背景信息
+
+wal2json是逻辑解码插件，使用该插件可以访问由INSERT和UPDATE生成的元组，解析WAL中的内容。
+
+wal2json插件会在每个事务中生成一个JSON对象。JSON对象中提供了所有新/旧元组，额外选项还可以包括事务时间戳、限定架构、数据类型、事务ID等属性。
+
+<br/>
+
+## 通过SQL获取JSON对象
+
+1. 登录MogDB数据库
+
+2. 执行如下命令建表及初始化插件。
+
+   ```sql
+   --开另一个session执行以下
+   pg_recvlogical -d mogdb --slot test_slot --create-slot -P wal2json
+   pg_recvlogical -d mogdb --slot test_slot --start -o pretty-print=1 -f -
+   --进行一些基本的DML操作
+   CREATE TABLE test_table (
+       id char(10) NOT NULL,
+       code        char(10),
+       PRIMARY KEY (id)
+   );
+   mogdb=# INSERT INTO test_table (id, code) VALUES('id1', 'code1');
+   INSERT 0 1
+   mogdb=# update test_table set code='code2' where id='id1';
+   UPDATE 1
+   mogdb=# delete from test_table where id='id1';
+   DELETE 1
+   ```
+
+   对应DML的输出：
+
+   **INSERT**
+
+   ```json
+   {
+     "change": [
+       {
+         "kind": "insert",
+         "schema": "mdmv2",
+         "table": "test_table",
+         "columnnames": ["id", "code"],
+         "columntypes": ["character(10)", "character(10)"],
+         "columnvalues": ["id1       ", "code1     "]
+       }
+     ]
+   }
+   ```
+
+   **UPDATE**
+
+   ```json
+   {
+     "change": [
+       {
+         "kind": "update",
+         "schema": "mdmv2",
+         "table": "test_table",
+         "columnnames": ["id", "code"],
+         "columntypes": ["character(10)", "character(10)"],
+         "columnvalues": ["id1       ", "code2     "],
+         "oldkeys": {
+           "keynames": ["id"],
+           "keytypes": ["character(10)"],
+           "keyvalues": ["id1       "]
+         }
+       }
+     ]
+   }
+   ```
+
+   **DELETE**
+
+   ```json
+   {
+     "change": [
+       {
+         "kind": "delete",
+         "schema": "mdmv2",
+         "table": "test_table",
+         "oldkeys": {
+           "keynames": ["id"],
+           "keytypes": ["character(10)"],
+           "keyvalues": ["id1       "]
+         }
+       }
+     ]
+   }
+   ```
+
+   也可以用REPLICA IDENTITY来决定对表UPDATE和DELETE操作时，logical日志输出信息的详细程度。
+
+   - DEFAULT：逻辑日志中包含表中主键列被UPDATE或DELETE的前值的信息。
+   - NOTHING：逻辑日志中不包含表中任何UPDATE或DELETE变更的信息。
+   - FULL：逻辑日志中包含表中被UPDATE或DELETE列的前值的整行信息。
+   - USING INDEX ：仅包含指定索引中所有列的前值信息。
diff --git a/product/zh/docs-mogdb/v3.0/about-mogdb/open-source-components/DBMS-RANDOM.md b/product/zh/docs-mogdb/v3.0/about-mogdb/open-source-components/DBMS-RANDOM.md
new file mode 100644
index 0000000000000000000000000000000000000000..e04639d1cc050c9e3a5148f7e4ef5564b1efaa4c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/about-mogdb/open-source-components/DBMS-RANDOM.md
@@ -0,0 +1,532 @@
+---
+title: DBMS_RANDOM随机函数包：在MogDB数据库中生成随机数（数字、字符串和日期）
+summary: DBMS_RANDOM随机函数包：在MogDB数据库中生成随机数（数字、字符串和日期）
+author: Liu Xu
+date: 2021-09-06
+---
+
+# DBMS_RANDOM随机函数包 ：在MogDB数据库中生成随机数（数字、字符串和日期）
+
+<br/>
+
+## compat-tools介绍
+
+compat-tools是一个兼容工具集合，旨在为从其他异构数据库，迁移到 MogDB之后的系统，创建必要的函数，以及系统视图的兼容。为后续的系统运维与应用改造提供便利。
+
+<br/>
+
+## 获取compat-tools
+
+若要安装 compat-tools，请从[https://gitee.com/enmotech/compat-tools](https://gitee.com/enmotech/compat-tools)下载中心下载该工具的最新版本。
+
+<br/>
+
+## compat-tools功能
+
+1. runMe.sql: 总调度脚本
+2. Oracle_Views.sql: 兼容Oracle数据库数据字典及视图
+3. Oracle_Functions.sql: 兼容Oracle数据库函数
+4. Oracle_Packages.sql: 兼容Oracle数据库管理包
+5. MySQL_Views.sql: 兼容MySQL数据库数据字典及视图 //TODO
+6. MySQL_Functions.sql: 兼容MySQL数据库函数 //TODO
+
+<br/>
+
+## compat-tools支持的数据库版本
+
+- MogDB 2.0
+- MogDB 1.1
+
+<br/>
+
+## 安装和使用compat-tools的方法
+
+1. 获取compat-tools: <https://gitee.com/enmotech/compat-tools>
+
+2. 将下载的文件存放到自定义的目录中（本文以**/opt/compat-tools-0902**为例）
+
+   ```bash
+   [root@mogdb-kernel-0005 compat-tools-0902]# pwd
+   /opt/compat-tools-0902
+   [root@mogdb-kernel-0005 compat-tools-0902]# ls -l
+   total 228
+   -rw-r--r-- 1 root root   9592 Sep  2 14:40 LICENSE
+   -rw-r--r-- 1 root root      0 Sep  2 14:40 MySQL_Functions.sql
+   -rw-r--r-- 1 root root      0 Sep  2 14:40 MySQL_Views.sql
+   -rw-r--r-- 1 root root  41652 Sep  2 14:40 Oracle_Functions.sql
+   -rw-r--r-- 1 root root  34852 Sep  2 14:40 Oracle_Packages.sql
+   -rw-r--r-- 1 root root 125799 Sep  2 14:40 Oracle_Views.sql
+   -rw-r--r-- 1 root root   4708 Sep  2 14:40 README.md
+   -rw-r--r-- 1 root root    420 Sep  2 14:40 runMe.sql
+   ```
+
+3. 切换到omm用户
+
+   ```
+   su - omm
+   ```
+
+4. 用omm用户执行以下脚本（26000是数据库所在的端口号）
+
+   ```bash
+   gsql -d mogdb -p 26000 -f /opt/compat-tools-0902/runMe.sql
+   ```
+
+<br/>
+
+## 开始测试DBMS_RANDOM随机函数包
+
+### 登录到mogdb数据库
+
+```sql
+[omm@mogdb-kernel-0005 ~]$ gsql -d mogdb -p 26000
+gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+Non-SSL connection (SSL connection is recommended when requiring high-security)
+Type "help" for help.
+
+mogdb=#
+```
+
+<br/>
+
+- [SEED](#seed)
+- [VALUE](#value)
+- [STRING](#string)
+- [NORMAL](#normal)
+- [RANDOM](#random)
+- [Generating Random Dates](#generating-random-dates)
+- [Generating Random Data](#generating-random-data)
+
+<br/>
+
+## SEED
+
+**SEED**可以用来指定伪随机数生成器的种子，增加其随机性。seed可支持二进制整数，也支持长度最大为2000的字符串。如果要始终生成相同的伪随机数集，请始终使用相同的随机数种子。
+
+```sql
+declare
+BEGIN
+  DBMS_OUTPUT.put_line('Run 1 : seed=0');
+  DBMS_RANDOM.seed (val => 0);
+  FOR i IN 1 ..5 LOOP
+    DBMS_OUTPUT.put_line('i=' || i || ' : value=' || DBMS_RANDOM.value(low => 1, high => 10));
+  END LOOP;
+
+  DBMS_OUTPUT.put_line('Run 2 : seed=0');
+  DBMS_RANDOM.seed (val => 0);
+  FOR i IN 1 ..5 LOOP
+    DBMS_OUTPUT.put_line('i=' || i || ' : value=' || DBMS_RANDOM.value(low => 1, high => 10));
+  END LOOP;
+
+END;
+/
+NOTICE:  Run 1 : seed=0
+CONTEXT:  SQL statement "CALL dbms_output.put_line('Run 1 : seed=0')"
+PL/pgSQL function inline_code_block line 3 at PERFORM
+NOTICE:  i=1 : value=2.53745232429355
+CONTEXT:  SQL statement "CALL dbms_output.put_line('i=' || i || ' : value=' || DBMS_RANDOM.value(low => 1, high => 10))"
+PL/pgSQL function inline_code_block line 6 at PERFORM
+NOTICE:  i=2 : value=7.749117821455
+CONTEXT:  SQL statement "CALL dbms_output.put_line('i=' || i || ' : value=' || DBMS_RANDOM.value(low => 1, high => 10))"
+PL/pgSQL function inline_code_block line 6 at PERFORM
+NOTICE:  i=3 : value=1.86734489817172
+CONTEXT:  SQL statement "CALL dbms_output.put_line('i=' || i || ' : value=' || DBMS_RANDOM.value(low => 1, high => 10))"
+PL/pgSQL function inline_code_block line 6 at PERFORM
+NOTICE:  i=4 : value=8.83418704243377
+CONTEXT:  SQL statement "CALL dbms_output.put_line('i=' || i || ' : value=' || DBMS_RANDOM.value(low => 1, high => 10))"
+PL/pgSQL function inline_code_block line 6 at PERFORM
+NOTICE:  i=5 : value=6.19573155790567
+CONTEXT:  SQL statement "CALL dbms_output.put_line('i=' || i || ' : value=' || DBMS_RANDOM.value(low => 1, high => 10))"
+PL/pgSQL function inline_code_block line 6 at PERFORM
+NOTICE:  Run 2 : seed=0
+CONTEXT:  SQL statement "CALL dbms_output.put_line('Run 2 : seed=0')"
+PL/pgSQL function inline_code_block line 9 at PERFORM
+NOTICE:  i=1 : value=2.53745232429355
+CONTEXT:  SQL statement "CALL dbms_output.put_line('i=' || i || ' : value=' || DBMS_RANDOM.value(low => 1, high => 10))"
+PL/pgSQL function inline_code_block line 12 at PERFORM
+NOTICE:  i=2 : value=7.749117821455
+CONTEXT:  SQL statement "CALL dbms_output.put_line('i=' || i || ' : value=' || DBMS_RANDOM.value(low => 1, high => 10))"
+PL/pgSQL function inline_code_block line 12 at PERFORM
+NOTICE:  i=3 : value=1.86734489817172
+CONTEXT:  SQL statement "CALL dbms_output.put_line('i=' || i || ' : value=' || DBMS_RANDOM.value(low => 1, high => 10))"
+PL/pgSQL function inline_code_block line 12 at PERFORM
+NOTICE:  i=4 : value=8.83418704243377
+CONTEXT:  SQL statement "CALL dbms_output.put_line('i=' || i || ' : value=' || DBMS_RANDOM.value(low => 1, high => 10))"
+PL/pgSQL function inline_code_block line 12 at PERFORM
+NOTICE:  i=5 : value=6.19573155790567
+CONTEXT:  SQL statement "CALL dbms_output.put_line('i=' || i || ' : value=' || DBMS_RANDOM.value(low => 1, high => 10))"
+PL/pgSQL function inline_code_block line 12 at PERFORM
+ANONYMOUS BLOCK EXECUTE
+mogdb=#
+```
+
+<br/>
+
+## VALUE
+
+**VALUE**函数用于生成一个指定范围的随机数。 若不指定范围，将生成一个大于等于0小于1的38位随机小数（小数点后38位）
+
+```sql
+DECLARE
+BEGIN
+  FOR cur_rec IN 1 ..5 LOOP
+    DBMS_OUTPUT.put_line('value= ' || DBMS_RANDOM.value());
+  END LOOP;
+END;
+/
+NOTICE:  value= .785799258388579
+CONTEXT:  SQL statement "CALL dbms_output.put_line('value= ' || DBMS_RANDOM.value())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  value= .692194153089076
+CONTEXT:  SQL statement "CALL dbms_output.put_line('value= ' || DBMS_RANDOM.value())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  value= .368766269646585
+CONTEXT:  SQL statement "CALL dbms_output.put_line('value= ' || DBMS_RANDOM.value())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  value= .87390407640487
+CONTEXT:  SQL statement "CALL dbms_output.put_line('value= ' || DBMS_RANDOM.value())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  value= .745095098391175
+CONTEXT:  SQL statement "CALL dbms_output.put_line('value= ' || DBMS_RANDOM.value())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+ANONYMOUS BLOCK EXECUTE
+```
+
+若指定了范围，则会生成一个大于等于最小值且小于最大值的随机数，同时小数点后的取值限制在最大值范围内。
+
+```sql
+declare
+BEGIN
+  FOR cur_rec IN 1 ..5 LOOP
+    DBMS_OUTPUT.put_line('value(1,100)= ' || DBMS_RANDOM.value(1,100));
+  END LOOP;
+END;
+/
+
+NOTICE:  value(1,100)= 45.158544998616
+CONTEXT:  SQL statement "CALL dbms_output.put_line('value(1,100)= ' || DBMS_RANDOM.value(1,100))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  value(1,100)= 36.0190920610912
+CONTEXT:  SQL statement "CALL dbms_output.put_line('value(1,100)= ' || DBMS_RANDOM.value(1,100))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  value(1,100)= 73.5194435422309
+CONTEXT:  SQL statement "CALL dbms_output.put_line('value(1,100)= ' || DBMS_RANDOM.value(1,100))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  value(1,100)= 26.7619780991226
+CONTEXT:  SQL statement "CALL dbms_output.put_line('value(1,100)= ' || DBMS_RANDOM.value(1,100))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  value(1,100)= 40.035083710216
+CONTEXT:  SQL statement "CALL dbms_output.put_line('value(1,100)= ' || DBMS_RANDOM.value(1,100))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+ANONYMOUS BLOCK EXECUTE
+mogdb=#
+```
+
+可按要求使用**TRUNC**或者**ROUND**改变随机数位数。例如，要生成1到10之间的随机整数，将小数点后的值舍去并给最大值加1。
+
+```sql
+mogdb=# select TRUNC(DBMS_RANDOM.value(1,11)) ;
+
+ trunc
+-------
+
+     6
+
+(1 row)
+
+mogdb=#
+```
+
+<br/>
+
+## STRING
+
+**STRING** 函数返回指定长度的随机字符串。`OPT` 参数定义了字符串的类型。 详细如下：
+
+- 'u', 'U' - 返回一个由大写字母组成的字符串
+- 'l', 'L' - 返回一个由小写字母组成的字符串
+- 'a', 'A' - 返回一个由大写字母和小写字母组成的字符串
+- 'x', 'X' - 返回一个由大写字母和数字组成的字符串
+- 'p', 'P' - 返回一个由任意的可打印字符组成的字符串
+
+`LEN`参数定义了返回字符串的长度。
+
+```sql
+declare
+BEGIN
+  FOR i IN 1 .. 5 LOOP
+    DBMS_OUTPUT.put_line('string(''x'',10)= ' || DBMS_RANDOM.string('x',10));
+  END LOOP;
+END;
+/
+
+NOTICE:  string('x',10)= i5S6XOZxrA
+CONTEXT:  SQL statement "CALL dbms_output.put_line('string(''x'',10)= ' || DBMS_RANDOM.string('x',10))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  string('x',10)= HGvRm75w19
+CONTEXT:  SQL statement "CALL dbms_output.put_line('string(''x'',10)= ' || DBMS_RANDOM.string('x',10))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  string('x',10)= N9WsQGJl6l
+CONTEXT:  SQL statement "CALL dbms_output.put_line('string(''x'',10)= ' || DBMS_RANDOM.string('x',10))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  string('x',10)= hDlPevVgRb
+CONTEXT:  SQL statement "CALL dbms_output.put_line('string(''x'',10)= ' || DBMS_RANDOM.string('x',10))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  string('x',10)= ZdSd8x8RKx
+CONTEXT:  SQL statement "CALL dbms_output.put_line('string(''x'',10)= ' || DBMS_RANDOM.string('x',10))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+ANONYMOUS BLOCK EXECUTE
+mogdb=#
+```
+
+**STRING**和**VALUE**函数结合可以生成各种长度的字符串。
+
+```sql
+declare
+BEGIN
+  FOR i IN 1 .. 5 LOOP
+    DBMS_OUTPUT.put_line('string(''L'',?)= ' || DBMS_RANDOM.string('L',TRUNC(DBMS_RANDOM.value(10,21))));
+  END LOOP;
+END;
+/
+
+NOTICE:  string('L',?)= kcyzowdxqbyzu
+CONTEXT:  SQL statement "CALL dbms_output.put_line('string(''L'',?)= ' || DBMS_RANDOM.string('L',TRUNC(DBMS_RANDOM.value(10,21))))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  string('L',?)= ohzpljyatsplqtbbus
+CONTEXT:  SQL statement "CALL dbms_output.put_line('string(''L'',?)= ' || DBMS_RANDOM.string('L',TRUNC(DBMS_RANDOM.value(10,21))))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  string('L',?)= hbrjsfeevoi
+CONTEXT:  SQL statement "CALL dbms_output.put_line('string(''L'',?)= ' || DBMS_RANDOM.string('L',TRUNC(DBMS_RANDOM.value(10,21))))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  string('L',?)= lfsapmytdamvwcw
+CONTEXT:  SQL statement "CALL dbms_output.put_line('string(''L'',?)= ' || DBMS_RANDOM.string('L',TRUNC(DBMS_RANDOM.value(10,21))))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  string('L',?)= pcvtxnwzomkqwpfzes
+CONTEXT:  SQL statement "CALL dbms_output.put_line('string(''L'',?)= ' || DBMS_RANDOM.string('L',TRUNC(DBMS_RANDOM.value(10,21))))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+ANONYMOUS BLOCK EXECUTE
+mogdb=#
+```
+
+<br/>
+
+## NORMAL
+
+NORMAL函数返回一组随机数。
+
+```sql
+declare
+BEGIN
+  FOR cur_rec IN 1 ..5 LOOP
+    DBMS_OUTPUT.put_line('normal= ' || DBMS_RANDOM.normal());
+  END LOOP;
+END;
+/
+
+NOTICE:  normal= .838851847718988
+CONTEXT:  SQL statement "CALL dbms_output.put_line('normal= ' || DBMS_RANDOM.normal())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  normal= -.523612260373397
+CONTEXT:  SQL statement "CALL dbms_output.put_line('normal= ' || DBMS_RANDOM.normal())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  normal= -.241931681458075
+CONTEXT:  SQL statement "CALL dbms_output.put_line('normal= ' || DBMS_RANDOM.normal())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  normal= -.120847761874286
+CONTEXT:  SQL statement "CALL dbms_output.put_line('normal= ' || DBMS_RANDOM.normal())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  normal= .360125112757284
+CONTEXT:  SQL statement "CALL dbms_output.put_line('normal= ' || DBMS_RANDOM.normal())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+ANONYMOUS BLOCK EXECUTE
+mogdb=#
+```
+
+<br/>
+
+## RANDOM
+
+```sql
+declare
+BEGIN
+  FOR i IN 1 .. 5 LOOP
+    DBMS_OUTPUT.put_line('random= ' || DBMS_RANDOM.random());
+  END LOOP;
+END;
+/
+NOTICE:  This function is deprecated with Release 11gR1, although currently supported, it should not be used.
+CONTEXT:  SQL statement "CALL dbms_output.put_line('random= ' || DBMS_RANDOM.random())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  random= -1023930867
+CONTEXT:  SQL statement "CALL dbms_output.put_line('random= ' || DBMS_RANDOM.random())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  This function is deprecated with Release 11gR1, although currently supported, it should not be used.
+CONTEXT:  SQL statement "CALL dbms_output.put_line('random= ' || DBMS_RANDOM.random())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  random= 1068572119
+CONTEXT:  SQL statement "CALL dbms_output.put_line('random= ' || DBMS_RANDOM.random())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  This function is deprecated with Release 11gR1, although currently supported, it should not be used.
+CONTEXT:  SQL statement "CALL dbms_output.put_line('random= ' || DBMS_RANDOM.random())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  random= 95361253
+CONTEXT:  SQL statement "CALL dbms_output.put_line('random= ' || DBMS_RANDOM.random())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  This function is deprecated with Release 11gR1, although currently supported, it should not be used.
+CONTEXT:  SQL statement "CALL dbms_output.put_line('random= ' || DBMS_RANDOM.random())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  random= -712638729
+CONTEXT:  SQL statement "CALL dbms_output.put_line('random= ' || DBMS_RANDOM.random())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  This function is deprecated with Release 11gR1, although currently supported, it should not be used.
+CONTEXT:  SQL statement "CALL dbms_output.put_line('random= ' || DBMS_RANDOM.random())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  random= -1251059926
+CONTEXT:  SQL statement "CALL dbms_output.put_line('random= ' || DBMS_RANDOM.random())"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+ANONYMOUS BLOCK EXECUTE
+mogdb=#
+```
+
+<br/>
+
+## Generating Random Dates
+
+目前没有生成随机日期的特定函数，但是可以为现有日期添加随机数来产生随机日期。下面的示例为生成下一年的随机日期。
+
+```sql
+declare
+BEGIN
+  FOR i IN 1 .. 5 LOOP
+    DBMS_OUTPUT.put_line('date= ' || TRUNC(SYSDATE + DBMS_RANDOM.value(0,366)));
+  END LOOP;
+END;
+/
+
+NOTICE:  date= 2021-10-06 00:00:00
+CONTEXT:  SQL statement "CALL dbms_output.put_line('date= ' || TRUNC(SYSDATE + DBMS_RANDOM.value(0,366)))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  date= 2022-05-09 00:00:00
+CONTEXT:  SQL statement "CALL dbms_output.put_line('date= ' || TRUNC(SYSDATE + DBMS_RANDOM.value(0,366)))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  date= 2022-04-07 00:00:00
+CONTEXT:  SQL statement "CALL dbms_output.put_line('date= ' || TRUNC(SYSDATE + DBMS_RANDOM.value(0,366)))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  date= 2021-11-29 00:00:00
+CONTEXT:  SQL statement "CALL dbms_output.put_line('date= ' || TRUNC(SYSDATE + DBMS_RANDOM.value(0,366)))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+NOTICE:  date= 2022-06-04 00:00:00
+CONTEXT:  SQL statement "CALL dbms_output.put_line('date= ' || TRUNC(SYSDATE + DBMS_RANDOM.value(0,366)))"
+PL/pgSQL function inline_code_block line 4 at PERFORM
+ANONYMOUS BLOCK EXECUTE
+mogdb=#
+```
+
+通过进行正确除法运算，可以给日期添加小时、秒或分钟。
+
+```sql
+DECLARE
+  l_hours_in_day NUMBER := 24;
+  l_mins_in_day  NUMBER := 24*60;
+  l_secs_in_day  NUMBER := 24*60*60;
+BEGIN
+  FOR i IN 1 .. 5 LOOP
+    DBMS_OUTPUT.put_line('hours= ' || (TRUNC(SYSDATE) + (TRUNC(DBMS_RANDOM.value(0,1000))/l_hours_in_day)));
+  END LOOP;
+  FOR i IN 1 .. 5 LOOP
+    DBMS_OUTPUT.put_line('mins = ' || (TRUNC(SYSDATE) + (TRUNC(DBMS_RANDOM.value(0,1000))/l_mins_in_day)));
+  END LOOP;
+  FOR i IN 1 .. 5 LOOP
+    DBMS_OUTPUT.put_line('secs = ' || (TRUNC(SYSDATE) + (TRUNC(DBMS_RANDOM.value(0,1000))/l_secs_in_day)));
+  END LOOP;
+END;
+/
+NOTICE:  hours= 2021-10-13 22:00:00
+CONTEXT:  SQL statement "CALL dbms_output.put_line('hours= ' || (TRUNC(SYSDATE)+ (TRUNC(DBMS_RANDOM.value(0,1000))/l_hours_in_day)))"
+PL/pgSQL function inline_code_block line 6 at PERFORM
+NOTICE:  hours= 2021-10-10 00:00:00
+CONTEXT:  SQL statement "CALL dbms_output.put_line('hours= ' || (TRUNC(SYSDATE)+ (TRUNC(DBMS_RANDOM.value(0,1000))/l_hours_in_day)))"
+PL/pgSQL function inline_code_block line 6 at PERFORM
+NOTICE:  hours= 2021-09-07 02:00:00
+CONTEXT:  SQL statement "CALL dbms_output.put_line('hours= ' || (TRUNC(SYSDATE)+ (TRUNC(DBMS_RANDOM.value(0,1000))/l_hours_in_day)))"
+PL/pgSQL function inline_code_block line 6 at PERFORM
+NOTICE:  hours= 2021-09-26 11:00:00
+CONTEXT:  SQL statement "CALL dbms_output.put_line('hours= ' || (TRUNC(SYSDATE)+ (TRUNC(DBMS_RANDOM.value(0,1000))/l_hours_in_day)))"
+PL/pgSQL function inline_code_block line 6 at PERFORM
+NOTICE:  hours= 2021-09-19 22:00:00
+CONTEXT:  SQL statement "CALL dbms_output.put_line('hours= ' || (TRUNC(SYSDATE)+ (TRUNC(DBMS_RANDOM.value(0,1000))/l_hours_in_day)))"
+PL/pgSQL function inline_code_block line 6 at PERFORM
+NOTICE:  mins = 2021-09-04 00:01:00
+CONTEXT:  SQL statement "CALL dbms_output.put_line('mins = ' || (TRUNC(SYSDATE)+ (TRUNC(DBMS_RANDOM.value(0,1000))/l_mins_in_day)))"
+PL/pgSQL function inline_code_block line 9 at PERFORM
+NOTICE:  mins = 2021-09-04 11:56:00
+CONTEXT:  SQL statement "CALL dbms_output.put_line('mins = ' || (TRUNC(SYSDATE)+ (TRUNC(DBMS_RANDOM.value(0,1000))/l_mins_in_day)))"
+PL/pgSQL function inline_code_block line 9 at PERFORM
+NOTICE:  mins = 2021-09-04 00:53:00
+CONTEXT:  SQL statement "CALL dbms_output.put_line('mins = ' || (TRUNC(SYSDATE)+ (TRUNC(DBMS_RANDOM.value(0,1000))/l_mins_in_day)))"
+PL/pgSQL function inline_code_block line 9 at PERFORM
+NOTICE:  mins = 2021-09-04 00:21:00
+CONTEXT:  SQL statement "CALL dbms_output.put_line('mins = ' || (TRUNC(SYSDATE)+ (TRUNC(DBMS_RANDOM.value(0,1000))/l_mins_in_day)))"
+PL/pgSQL function inline_code_block line 9 at PERFORM
+NOTICE:  mins = 2021-09-04 12:38:00
+CONTEXT:  SQL statement "CALL dbms_output.put_line('mins = ' || (TRUNC(SYSDATE)+ (TRUNC(DBMS_RANDOM.value(0,1000))/l_mins_in_day)))"
+PL/pgSQL function inline_code_block line 9 at PERFORM
+NOTICE:  secs = 2021-09-04 00:10:28
+CONTEXT:  SQL statement "CALL dbms_output.put_line('secs = ' || (TRUNC(SYSDATE)+ (TRUNC(DBMS_RANDOM.value(0,1000))/l_secs_in_day)))"
+PL/pgSQL function inline_code_block line 12 at PERFORM
+NOTICE:  secs = 2021-09-04 00:15:31
+CONTEXT:  SQL statement "CALL dbms_output.put_line('secs = ' || (TRUNC(SYSDATE)+ (TRUNC(DBMS_RANDOM.value(0,1000))/l_secs_in_day)))"
+PL/pgSQL function inline_code_block line 12 at PERFORM
+NOTICE:  secs = 2021-09-04 00:09:07
+CONTEXT:  SQL statement "CALL dbms_output.put_line('secs = ' || (TRUNC(SYSDATE)+ (TRUNC(DBMS_RANDOM.value(0,1000))/l_secs_in_day)))"
+PL/pgSQL function inline_code_block line 12 at PERFORM
+NOTICE:  secs = 2021-09-04 00:06:54
+CONTEXT:  SQL statement "CALL dbms_output.put_line('secs = ' || (TRUNC(SYSDATE)+ (TRUNC(DBMS_RANDOM.value(0,1000))/l_secs_in_day)))"
+PL/pgSQL function inline_code_block line 12 at PERFORM
+NOTICE:  secs = 2021-09-04 00:06:32
+CONTEXT:  SQL statement "CALL dbms_output.put_line('secs = ' || (TRUNC(SYSDATE)+ (TRUNC(DBMS_RANDOM.value(0,1000))/l_secs_in_day)))"
+PL/pgSQL function inline_code_block line 12 at PERFORM
+ANONYMOUS BLOCK EXECUTE
+mogdb=#
+```
+
+<br/>
+
+## Generating Random Data
+
+DBMS_RANDOM 包用于生成随机测试数据。通过将其与查询结合，可以快速生成大量数据。
+
+```sql
+mogdb=# CREATE TABLE random_data (
+  id           NUMBER,
+  small_number NUMBER(5),
+  big_number   NUMBER,
+  short_string VARCHAR2(50),
+  long_string  VARCHAR2(400),
+  created_date DATE,
+  CONSTRAINT random_data_pk PRIMARY KEY (id)
+);
+NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index "random_data_pk" for table "random_data"
+CREATE TABLE
+mogdb=#
+```
+
+```sql
+mogdb=# INSERT INTO random_data
+SELECT generate_series(1,29999),
+       TRUNC(DBMS_RANDOM.value(1,5)) AS small_number,
+       TRUNC(DBMS_RANDOM.value(100,10000)) AS big_number,
+       DBMS_RANDOM.string('L',TRUNC(DBMS_RANDOM.value(10,50))) AS short_string,
+       DBMS_RANDOM.string('L',TRUNC(DBMS_RANDOM.value(100,400))) AS long_string,
+       TRUNC(SYSDATE + DBMS_RANDOM.value(0,366)) AS created_date;
+INSERT 0 29999
+mogdb=#
+mogdb=#  select count(*) from random_data;
+ count
+-------
+ 29999
+(1 row)
+
+mogdb=#
+```
diff --git a/product/zh/docs-mogdb/v3.0/about-mogdb/open-source-components/compat-tools.md b/product/zh/docs-mogdb/v3.0/about-mogdb/open-source-components/compat-tools.md
new file mode 100644
index 0000000000000000000000000000000000000000..476083231ffc5bbde6ef7978b931fadd336d8f04
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/about-mogdb/open-source-components/compat-tools.md
@@ -0,0 +1,18 @@
+---
+title: compat-tools
+summary: compat-tools
+author: Zhang Cuiping
+date: 2021-07-14
+---
+
+# compat-tools
+
+本项目是一个兼容工具集合，旨在为从其他异构数据库，迁移到 MogDB 之后的系统，创建必要的函数，以及系统视图的兼容。为后续的系统运维与应用改造提供便利。
+
+脚本中带有版本控制，直接运行脚本时，会根据如下三种情况进行处理：
+
+1. 若待创建对象在目标数据库中不存在，则直接进行创建
+2. 若待创建对象版本高于目标数据库中的对象版本，则进行升级重建
+3. 若待创建对象版本不高于目标数据库中的对象版本，则跳过创建
+
+组件获取及使用方法详见[compat-tools仓库页面](https://gitee.com/enmotech/compat-tools)。
diff --git a/product/zh/docs-mogdb/v3.0/about-mogdb/open-source-components/mog_filedump.md b/product/zh/docs-mogdb/v3.0/about-mogdb/open-source-components/mog_filedump.md
new file mode 100644
index 0000000000000000000000000000000000000000..2dfa8faeb46a11484ea3b3c94bf1e62a39f629a5
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/about-mogdb/open-source-components/mog_filedump.md
@@ -0,0 +1,106 @@
+---
+title: mog_filedump使用说明
+summary: mog_filedump使用说明
+author: Guo Huan
+date: 2021-11-15
+---
+
+
+
+# mog_filedump使用说明
+
+## 简介
+
+mog_filedump是根据pg_filedump工具改进兼容性，移植到MogDB上的解析数据文件工具，用于将MogDB的heap/index/control文件转换成用户可读的格式内容。本工具能够根据需要，解析数据列中一部分字段，也能直接以二进制格式转储数据内容。该工具可以通过文件中块的数据，自动确定文件的类型。要格式化pg_control文件必须使用-c选项。
+
+<br/>
+
+## 原理说明
+
+实现步骤主要分三步：
+
+1. 读取数据文件中的数据块。
+
+2. 以对应数据类型的回调函数，解析对应类型的数据。
+
+3. 调用对应的数据类型函数输出，打印数据内容。
+
+<br/>
+
+## 恩墨的改进
+
+1. 对MogDB做了兼容性移植。
+
+2. 修复官方bug：数据类型char的解析bug。
+
+3. 修复官方bug：在多字段场景下，解析数据文件，数据类型name会产生数据长度不对齐bug。
+
+<br/>
+
+## 安装方法
+
+访问[MogDB官网下载页面](https://www.mogdb.io/downloads/mogdb)下载对应版本的工具包，将工具放在MogDB安装路径的bin目录下即可。如下图所示，toolkits-xxxxxx.tar.gz即为包含mog_filedump的工具包。
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/about-mogdb/open-source-components-1.png)
+
+<br/>
+
+## 使用方法
+
+```
+mog_filedump [-abcdfhikxy] [-R startblock [endblock]] [-D attrlist] [-S blocksize] [-s segsize] [-n segnumber] file
+```
+
+对heap和index文件有效的选项如下：
+
+| 选项  | 功能                                                         |
+| ---- | ------------------------------------------------------------ |
+| -a   | 显示绝对路径                                                 |
+| -b   | 输出一个范围的二进制block images                             |
+| -d   | 输出文件块内容                                               |
+| -D   | 表的数据类型。<br/>目前支持的数据类型有：bigint、bigserial、bool、charN、date、float、float4、float8、int、json、macaddr、name、oid、real、serial、smallint、smallserial、text、time、timestamp、timetz、uuid、varchar、varcharN、xid、xml、~。 <br/>'~'表示忽略后面所有的数据类型，比如元组有10列，`-D 前三列数据类型, ~`表示只解析该表元组前三列数据。 |
+| -f   | 输出并解析数据块的内容                                       |
+| -h   | 显示使用说明和帮助信息                                       |
+| -i   | 输出并解析item的详细信息（其中包含XMIN、XMAX、Block Id、linp Index、Attributes、Size、infomask） |
+| -k   | 核实数据块的校验和                                           |
+| -R   | 解析并输出指定LSN范围的数据文件内容，例如 -R startblock [endblock]。如果只有startblock没有endblock，则只输出单个数据块内容 |
+| -s   | 设置segment大小                                             |
+| -n   | 设置segment数量                                             |
+| -S   | 设置数据块大小                                               |
+| -x   | 把块items当作索引item格式解析并输出（默认自带）              |
+| -y   | 把块items当作堆item格式解析并输出（默认自带）                |
+
+对控制文件有效的选项如下：
+
+| 选项 | 功能                     |
+| ---- | ------------------------ |
+| -c   | 解析控制文件的列表目录   |
+| -f   | 输出并解析数据块的内容   |
+| -S   | 设置控制文件解析的块大小 |
+
+可以结合-i和-f参数，得到更有效的数据以帮助运维人员分析与参考。
+
+<br/>
+
+## 示例
+
+test表基本上覆盖了mog_filedump所包含的数据类型。
+
+此处是展示数据解析功能的用例，其它参数请根据实际具体需要添加使用。
+
+```sql
+-- 创建表test:
+create table test(serial serial, smallserial smallserial, bigserial bigserial, bigint bigint, bool bool, char char(3), date date, float float, float4 float4, float8 float8, int int, json json, macaddr macaddr, name name, oid oid, real real, smallint smallint, text text, time time, timestamp timestamp, timetz timetz, uuid uuid, varchar varchar(20), xid xid, xml xml);
+
+-- 插入数据：
+insert into test(bigint, bool, char, date, float, float4, float8, int, json, macaddr, name, oid, real, smallint, text, time, timestamp, timetz, uuid, varchar, xid, xml) values(123456789, true, 'abc', '2021-4-02 16:45:00', 3.1415926, 3.1415926, 3.14159269828412, 123456789, '{"a":1, "b":2, "c":3}'::json, '04-6C-59-99-AF-07', 'lvhui', 828243, 3.1415926, 12345, 'text', '2021-04-02 16:48:23', '2021-04-02 16:48:23', '2021-04-02 16:48:23', 'a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11', 'adsfghkjlzc', '9973::xid', '<title>Book0001</title>');
+
+-- 查询表test的数据文件所在目录。该处gs_initdb指定的数据目录为db_p。所以表test数据文件在db_p/base/15098/32904
+postgres=# select pg_relation_filepath('test');
+base/15098/32904 (1 row)
+
+-- 用mog_filedump工具解析数据文件内容：
+./mog_filedump -D serial,smallserial,bigserial,bigint,bool,charN,date,float,float4,float8,int,json,macaddr,name,oid,real,smallint,text,time,timestamp,timetz,uuid,varchar,xid,xml db_p/base/15098/32904
+```
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/reference-guide/mog_filedump.png)
diff --git a/product/zh/docs-mogdb/v3.0/about-mogdb/open-source-components/mog_xlogdump.md b/product/zh/docs-mogdb/v3.0/about-mogdb/open-source-components/mog_xlogdump.md
new file mode 100644
index 0000000000000000000000000000000000000000..803deb97805e54e76dadf0babec7b272fa0418af
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/about-mogdb/open-source-components/mog_xlogdump.md
@@ -0,0 +1,305 @@
+---
+title: mog_xlogdump使用说明
+summary: mog_xlogdump使用说明
+author: Guo Huan
+date: 2021-11-15
+---
+
+# mog_xlogdump使用说明
+
+## 简介
+
+mog_xlogdump是云和恩墨独立开发的wal日志离线解析工具。主要用于在主备集群场景中，数据库永久性宕机且无法恢复的情况下，反向解析无法启动的数据库，然后在集群中恢复wal日志尾部没有同步的数据。
+
+<br/>
+
+## 研发背景
+
+在MogDB主备高可用集群一主多备，使用异步逻辑复制场景中，当主库宕机其事务提交完时，该事务操作的数据已经被写入wal日志中。主库宕机后由于无法发送给备库，备库会产生不完整的数据段日志。因此在主库宕机后，备库与主库之间的数据存在数据丢失、逻辑没有对齐的情况。所以其后备库组成的主备集群和实际业务中数据存在数据丢失的风险。
+
+在主库恢复期间，后备库组成的集群会有业务数据写入，此时即时主库恢复，主库的wal日志末尾不完整的数据段的段号、起始和结束位置与备库中已经产生不一致现象，也会导致主库最后宕机时丢失的数据无法恢复到备库中。
+
+<br/>
+
+## 使用场景
+
+MogDB高可用集群中，当主库宕机时，在walbuffer写满一定比例时，或者checkpoint，或者commit时，触发walbuffer写入wal日志。由于数据库宕机，逻辑同步的WalSender线程停止发送日志，备库接收到不完整的数据段wal日志。此时则需要用falshback工具读取主库的wal日志中的数据块，并解码出对应数据操作的SQL语句，供DBA分析数据是否有价值，并恢复到备库中。
+
+<br/>
+
+## 原理说明
+
+该工具使用的两个机制，一个是wal日志的头部解析，另一个是逻辑复制机制。
+
+实现步骤主要分三步：
+
+1. 读取wal日志文件，解析头部。
+
+2. 依次读取数据，并反解码数据。
+
+3. 根据数据不同的数据类型，回调不同类型的函数输出。
+
+<br/>
+
+## 支持解析的表类型
+
+目前支持分区表和普通表。
+
+<br/>
+
+## 支持解析的数据类型
+
+bool、bytea、char、name、int8、int2、int、text、oid、tid、xid、cid、xid32、clob、float4、float8、money、inet、varchar、numeric、int4;
+
+> 注意：由于mog_xlogdump是离线wal解析工具，所以暂时不支持需要用toast数据的大数据类型（clob等），下个版本将会支持toast表文件离线解析功能。
+
+<br/>
+
+## 安装方法
+
+访问[MogDB官网下载页面](https://www.mogdb.io/downloads/mogdb)下载对应版本的工具包，将工具放在MogDB安装路径的bin目录下即可。如下图所示，toolkits-xxxxxx.tar.gz即为包含mog_xlogdump的工具包。
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/about-mogdb/open-source-components-1.png)
+
+<br/>
+
+## 使用说明
+
+mog_xlogdump是用于解析并显示MogDB-2.1版本的Wal日志的工具。旨在帮助DBA分析与Debugging数据库问题的辅助工具。
+
+mog_xlogdump解析工具暂时不支持列存表。（研究发现列存表会在cstore模式下生成两张对应的CUDesc和delta表，CUDesc是列存表的元数据，delta是列存表的临时表，是张行存表，这两张表（CUDesc，delta）都会写在wal日志中，虽然wal日志能解析出对应的delta表，但该表受表属性阈值deltarow_threshold控制 ，默认100，即小于100条数据才会写在delta表中，大于阈值就会直接写到cu文件里）
+
+> 注意：列存表要写delta表，需要postgres.conf中开启参数enable_delta_store = on。
+
+<br/>
+
+## 使用方式
+
+```
+mog_xlogdump [OPTION]... [STARTSEG [ENDSEG]]
+```
+
+<br/>
+
+## 选项说明
+
+- -b, --bkp-details 
+
+  输出文件块的详细信息。（默认显示block的id、rel、fork、blk、lastlsn，该参数会显示Block Image）
+
+- -B, --bytea_output
+
+  指定bytea类型解码输出的显示格式，有二进制和字符两种格式
+
+- -c --connectinfo
+
+  指定链接字符串URL，例如postgres://user:password@ip:port/dbname
+
+- -e, --end=RECPTR
+
+  指定解析wal日志的结束位置，LSN号
+
+- -f, --follow
+
+  表示当指定的wal日志解析到结尾时，继续往下一个文件解析
+
+- -n, --limit=N
+
+  指定输出数据记录的条数
+
+- -o, --oid=OID
+
+  指定反解码表的OID
+
+- -p, --path=PATH
+
+  指定wal日志存放目录
+
+- -R, --Rel=Relation
+
+  指定反解码表的数据类型
+
+- -r, --rmgr=RMGR
+
+  只显示资源管理器生成的记录内容
+
+- -s, --start=RECPTR
+
+  指定解析wal日志的开始位置，LSN号
+
+- -T, --CTimeZone_ENV
+
+  指定时域，默认的是UTC。
+
+- -t, --timeline=TLI
+
+  指定开始读取wal日志的timeline
+
+- -V, --version
+
+  显示版本号
+
+- -w, --write-FPW
+
+  显示全页写的信息，配合-b使用
+
+- -x, --xid=XID
+
+  输出指定事务id的记录
+
+- -z, --stats
+
+  输出插入记录的统计
+
+- -v, --verbose
+
+  显示细节信息
+
+- -?, --help
+
+  显示帮助信息并退出
+
+<br/>
+
+## 用例一
+
+### 使用场景
+
+当主库宕机且无法恢复，备库可以正常链接，此时主库末发的wal日志里面可能包含有上万张表数据的操作，而mog_xlogdump工具需要根据指定的-s、-e（起始和结束的lsn位置），把所有表的数据操作都解析出来。
+
+### 使用方法
+
+```
+mog_xlogdump -c '备库链接串' -s '起始lsn' -e '结束lsn 主库wal日志文件
+```
+
+### 解析设置
+
+注：主要是为了让wal日志中记录旧数据，即update操作修改前的数据元组，和delete操作删除的数据。
+
+1. 把数据库配置文件postgres.conf里的**wal_level**设置为**logical**级别。
+2. 对表进行修改: `alter table table_name replica identity full;`
+
+### 结果展示
+
+以json格式输出wal日志数据解析结果。tuple展示格式为 `’列名’:’数据’`
+
+```json
+{'table_name':'xxx','schema_name':'yyy','action':'insert','tuple':{'name':'xx','id':'ss'}}
+```
+
+### 示例
+
+![fe1b12d080accfb9e54f857e79baebc](https://cdn-mogdb.enmotech.com/docs-media/mogdb/reference-guide/mog_xlogdump-1.png)
+
+红框中是根据解析设置后才会解析出的旧数据，如果没有设置则解析不到update和delete的旧数据。
+
+其中-c后面的备机链接URL为`postgres://test:Test123456@172.16.0.44:5003/postgres`
+
+- postgres://为链接串标记头部
+
+- test为链接用户名
+
+- Test123456为链接用户的密码
+
+- 172.16.0.44为备机ip地址
+
+- 5003为备机链接端口
+
+- postgres为链接备机的数据库名
+
+- db_p/pg_xlog/000000010000000000000004为主机的wal日志文件
+
+ <br/>
+
+## 用例二
+
+### 使用场景
+
+当主库宕机且无法恢复，且备库可以正常链接，此时用户可能只关注库中的几张表（个别表），mog_xlogdump工具可以根据参数-o、-R来解析指定oid的表数据。比如-o指定表的oid，-R指定表的字段类型。
+
+### 使用方法
+
+创建表，写入数据并修改，用mog_xlogdump工具反解析Wal日志。
+
+```sql
+create table t2(id int, money money,inet inet,bool bool,numeric numeric ,text text);
+insert into t2 values(1, 24.241, '192.168.255.132', true, 3.1415926, 'ljfsodfo29892ifj');
+insert into t2 values(2, 928.8271, '10.255.132.101', false, 3.1415926, 'vzvzcxwf2424@');
+update t2 set id=111, money=982.371 where id =2;
+delete from t2 where id=1;
+
+postgres=# select * from t2;
+ id | money |   inet    | bool | numeric |    text    
+----+---------+-----------------+------+-----------+------------------
+ 1 | $24.24 | 192.168.255.132 | t  | 3.1415926 | ljfsodfo29892ifj
+ 2 | $928.83 | 10.255.132.101 | f  | 3.1415926 | vzvzcxwf2424@
+(2 rows)
+
+postgres=# update t2 set id=111, money=982.371 where id =2;
+Postgres=# delete from t2 where id=1;
+postgres=# select * from t2;
+ id |  money  |   inet   | bool | numeric |   text   
+-----+-------------+----------------+------+-----------+---------------
+ 111 | $982,371.00 | 10.255.132.101 | f  | 3.1415926 | vzvzcxwf2424@
+ 
+(1 rows)
+```
+
+### 解析设置
+
+与用例一相同，设置wal_level和alter table等两个设置。
+
+### 结果展示
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/reference-guide/mog_xlogdump-2.png)
+
+```json
+./mog_xlogdump -o 16394 -R int,money,inet,bool,numeric,text ./db_p/pg_xlog/000000010000000000000004 
+'insert','tuple':{'(null)':'1','(null)':'$24.24','(null)':'192.168.255.132','(null)':true,'(null)':'3.1415926','(null)':'ljfsodfo29892ifj'}}
+'insert','tuple':{'(null)':'2','(null)':'$928.83','(null)':'10.255.132.101','(null)':false,'(null)':'3.1415926','(null)':'vzvzcxwf2424@'}}
+'update','old_tuple':{'(null)':'2','(null)':'$928.83','(null)':'10.255.132.101','(null)':false,'(null)':'3.1415926','(null)':'vzvzcxwf2424@'},'new_tuple':{'(null)':'111','(null)':'$982,371.00','(null)':'10.255.132.101','(null)':false,'(null)':'3.1415926','(null)':'vzvzcxwf2424@'}}
+'delete','tuple':{'(null)':'1','(null)':'$24.24','(null)':'192.168.255.132','(null)':true,'(null)':'3.1415926','(null)':'ljfsodfo29892ifj'}}
+```
+
+> 注意：由于输出格式的更改，表名、模式名和列名是依据-c链接字符串去备机上查询获取，但由于原来的-o、-R指定表oid和字段类型的方式是完全离线式，所以无法获取表名、模式名、列名这些信息，所以再用-o、-R来离线解析，不显示表名、模式名，列名显示为null。
+
+```
+mog_xlogdump -o 表OID -R 表的数据类型 -s 解析起始的LSN -e 解析结束的LSN Wal日志文件
+```
+
+该工具也保留了pg_xlogdump原始的功能。
+
+<br/>
+
+## 用例三
+
+### 使用场景
+
+当用户想看wal日志头部数据内容时，或者统计wal日志一些相关信息，用mog_xlogdump原始功能。
+
+### 使用方法
+
+使用一（头部信息）：
+
+```
+./mog_xlogdump -n 10 wal日志文件
+```
+
+-n 10 表示只显示10条数据。
+
+使用二（统计信息）：
+
+```
+./mog_xlogdump -z wal日志文件   
+```
+
+### 结果展示
+
+结果一
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/reference-guide/mog_xlogdump-3.png)
+
+结果二
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/reference-guide/mog_xlogdump-4.png)
diff --git a/product/zh/docs-mogdb/v3.0/about-mogdb/open-source-components/mogdb-monitor.md b/product/zh/docs-mogdb/v3.0/about-mogdb/open-source-components/mogdb-monitor.md
new file mode 100644
index 0000000000000000000000000000000000000000..f701b542efbffa8468b622f81ca5615e37ca47e1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/about-mogdb/open-source-components/mogdb-monitor.md
@@ -0,0 +1,27 @@
+---
+title: mogdb-monitor
+summary: mogdb-monitor
+author: Guo Huan
+date: 2022-04-14
+---
+
+# mogdb-monitor
+
+mogdb-monitor是MogDB数据库集群监控部署工具，借助当前非常流行的开源监控体系prometheus框架，结合由恩墨数据库团队开发的opengauss_exporter，可以实现对MogDB数据库进行全方位的检测。
+
+核心监控组件opengauss_exporter具有以下特点：
+
+- 支持所有版本MogDB/openGauss数据库
+- 支持监控数据库集群
+- 支持集群内主备角色判断
+- 支持自动发现数据库
+- 支持自定义查询query
+- 支持在线加载配置文件
+- 支持配置线程并发数
+- 支持数据采集信息缓存
+
+在grafana展示方面，云和恩墨也提供了一套完整的dashboard，既有展示每个实例详细信息的实例级dashboard，也有展示所有实例汇总信息的展示大屏，结合alertmanager组件，可以第一时间将符合规则的报警触发到相关人员。
+
+<br/>
+
+组件获取及使用方法详见[mogdb-monitor仓库页面](https://gitee.com/enmotech/mogdb-monitor)。
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/about-mogdb/roadmap.md b/product/zh/docs-mogdb/v3.0/about-mogdb/roadmap.md
new file mode 100644
index 0000000000000000000000000000000000000000..3bd29076b06ce285136f23d43c8bece69aae5358
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/about-mogdb/roadmap.md
@@ -0,0 +1,81 @@
+---
+title: 功能迭代计划
+summary: 功能迭代计划
+author: Guo Huan
+date: 2021-04-14
+---
+
+# 功能迭代计划
+
+本文档主要介绍MogDB 2.0.1的功能迭代计划。
+
+<table>
+    <tr>
+        <th>产品组件修改</th>
+        <th>未合并的内容</th>
+    </tr>
+    <tr>
+        <td rowspan="4">MogHA</td>
+        <td>新增支持主库实例自动重启</td>
+    </tr>
+    <tr>
+        <td>新增支持数据库cpu使用限额</td>
+    </tr>
+    <tr>
+        <td>新增支持HA切换自定义操作</td>
+    </tr>
+    <tr>
+        <td>新增配套WEB界面，api等，方便小规模部署使用（EA阶段）</td>
+    </tr>
+    <tr>
+        <td rowspan="10">MogDB Server</td>
+        <td>支持主库设置为全局只读，可用于网络隔离情况下的防脑裂处理</td>
+    </tr>
+    <tr>
+        <td>支持pg trgm插件（全文索引插件）</td>
+    </tr>
+    <tr>
+        <td>支持自定义操作符，自定义操作符类</td>
+    </tr>
+    <tr>
+        <td>降低数据库指标采集的资源消耗</td>
+    </tr>
+    <tr>
+        <td>分区创建语法优化</td>
+    </tr>
+     <tr>
+        <td>优化对CJK（东亚字符集）的排序支持，针对大数据量排序有更好的表现</td>
+    </tr>
+     <tr>
+        <td>支持基于xid的闪回查询</td>
+    </tr>
+     <tr>
+        <td>二级分区（sub partition)</td>
+    </tr>
+     <tr>
+        <td>citus 插件支持， 横向扩展的分布式能力</td>
+    </tr>
+     <tr>
+        <td>在线重建索引（online reindex), 重建索引不锁表</td>
+    </tr>
+    <tr>
+        <td rowspan="2">MogDB Client</td>
+        <td>go客户端：新增支持go的sha256加密算法支持</td>
+    </tr>
+    <tr>
+        <td>python客户端：新增支持sha256加密算法，支持主库自动识别</td>
+    </tr>
+    <tr>
+        <td rowspan="4">MogDB plugin</td>
+        <td>wal2json 插件兼容支持 用于现在的逻辑日志导出以及异构复制</td>
+    </tr>
+    <tr>
+        <td>pg_dirtyread 插件支持 用于特殊情况下的数据恢复和回查</td>
+    </tr>
+    <tr>
+        <td>walminer 插件支持 用于在线的wal日志解析（不依赖逻辑日志）</td>
+    </tr>
+    <tr>
+        <td>db_link 插件支持，用于从MogDB连接PostgreSQL数据库</td>
+    </tr>
+</table>
diff --git a/product/zh/docs-mogdb/v3.0/about-mogdb/terms-of-use.md b/product/zh/docs-mogdb/v3.0/about-mogdb/terms-of-use.md
new file mode 100644
index 0000000000000000000000000000000000000000..b7aecf0487057a4ac3de13adf113bedb6679a465
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/about-mogdb/terms-of-use.md
@@ -0,0 +1,22 @@
+---
+title: 法律声明
+summary: 法律声明
+author: Guo Huan
+date: 2021-06-01
+---
+
+# 法律声明
+
+**版权所有 © 2009-2022 云和恩墨（北京）信息技术有限公司。**
+
+您对“本文档”的复制、使用、修改及分发受知识共享(Creative Commons)署名-相同方式共享4.0国际公共许可协议(以下简称“CC BY-SA 4.0”)的约束。为了方便用户理解，您可以通过访问<https://creativecommons.org/licenses/by-sa/4.0/> 了解CC BY-SA 4.0的概要（但不是替代）。CC BY-SA 4.0的完整协议内容您可以访问如下网址获取：[https://creativecommons.org/licenses/by-sa/4.0/legalcode](https://creativecommons.org/licenses/by-sa/4.0/legalcode)。
+
+“本文档”部分页面内容参考自[openGauss官方文档](https://opengauss.org/zh/docs/1.1.0/docs/Quickstart/%E4%BA%86%E8%A7%A3%E4%BA%A7%E5%93%81.html)。
+
+**商标声明**
+
+MogDB为云和恩墨（北京）信息技术有限公司的商标。本文档提及的其他所有商标或注册商标，由各自的所有人拥有。
+
+**免责声明**
+
+本文档仅作为使用指导，除非适用法强制规定或者双方有明确书面约定，云和恩墨（北京）信息技术有限公司对本文档中的所有陈述、信息和建议不做任何明示或默示的声明或保证，包括但不限于不侵权，时效性或满足特定目的的担保。
diff --git a/product/zh/docs-mogdb/v3.0/about-mogdb/test-report/ha/1-database-server-exception-testing.md b/product/zh/docs-mogdb/v3.0/about-mogdb/test-report/ha/1-database-server-exception-testing.md
new file mode 100644
index 0000000000000000000000000000000000000000..daedfabde3bb93c59b142bca9be7e4240f80fa16
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/about-mogdb/test-report/ha/1-database-server-exception-testing.md
@@ -0,0 +1,217 @@
+---
+title: MogDB数据库服务器异常测试
+summary: MogDB数据库服务器异常测试
+author: Liu Xu
+date: 2021-03-04
+---
+
+# MogDB数据库服务器异常测试
+
+## 测试目的
+
+测试MogDB在主节点异常宕机、备节点异常宕机、仲裁节点异常宕机、主+备节点异常宕机和仲裁+主节点异常宕机场景下的可用性、稳定性。
+
+<br/>
+
+## 测试环境
+
+| 类别     | 服务端配置            | 客户端配置    | 数量  |
+| -------- | --------------------- | ------------- | ----- |
+| CPU      | Kunpeng 920           | Kunpeng 920   | 128   |
+| 内存     | DDR4,2933MT/s         | DDR4,2933MT/s | 2048G |
+| 硬盘     | Nvme 3.5T             | Nvme 3T       | 4个   |
+| 文件系统 | Xfs                   | Xfs           | 4     |
+| OS       | openEuler 20.03 (LTS) | Kylin V10     |       |
+| 数据库   | MogDB1.1.0安装包      |               |       |
+| 测试工具 | pgbench               |               |       |
+
+<br/>
+
+## 主节点异常宕机
+
+测试方案:
+
+1. 重启主机
+
+2. 监控TPS变化
+
+3. 加入新备机
+
+4. 监控集群状态及TPS变化
+
+测试步骤:
+
+1. 重启主机
+
+    ```bash
+    reboot
+    ```
+
+2. 原先的主库做为备库新加入集群
+
+    ```bash
+    gs_ctl -b full build -D /gaussdata/openGauss/db1
+    ```
+
+3. 新备库追赶日志
+
+4. 追赶完成
+
+测试结果:
+
+- 主库关闭后，TPS从9000降至0，持续时间为50秒左右。vip到新主库（节点2）后，tps从0增至13000左右
+
+- 老主厍作为新备库加入集群同步埶据时，tps从13000降到0 同步完成后恢9000正常水平
+
+<br/>
+
+## 备节点异常宕机
+
+测试方案:
+
+1. 重启备机
+
+2. 监控TPS变化
+
+3. 备机加入集群
+
+4. 监控集群状态及TPS变化
+
+测试步骤:
+
+1. 重启备机
+
+    ```bash
+    reboot
+    ```
+
+2. 备机加入集群
+
+    ```bash
+    gs_ctl start -D /gaussdata/openGauss/db1 -M standby
+    ```
+
+3. 追赶数据
+
+    ```bash
+    Standby Catchup
+    ```
+
+4. 追赶完成
+
+测试结果:
+
+- 备库关闭后，tps从9000左右升至13000左右
+
+- 备库加入集群后追赶数据tps从 13000降至0，追完成后恢复9000正常水平
+
+<br/>
+
+## 仲裁节点异常宕机
+
+测试方案:
+
+1. 在nodc.conf里的ping_list参数加入一个vip
+
+2. 操作vip的上线与下线来模拟仲裁宕机
+
+测试步骤:
+
+1. 在服务器ip上添加vip
+
+    ```bash
+    ifconfig ens160:1 192.168.122.111 netmask 255.255.255.0
+    ```
+
+2. 在node.conf的ping_list参数加入vip，同步主备的配置文件并重启监控脚本
+
+3. 在监控脚本运行正常的情况下，下掉模拟仲裁的vip，观察现象
+
+    ```bash
+    ifconfig ens160:1 down
+    ```
+
+4. 手动上线模拟仲裁的vip，观察现象
+
+测试结果:
+
+- 主备的监脚本报告仲裁ip ping失败，没发生其它的操作和现象
+- tps未观察到现象
+
+<br/>
+
+## 主+备节点异常宕机
+
+测试方案:
+
+1. 同时reboot主备节点机器
+
+2. 开启主备node_run脚本
+
+3. 主备机器开启后手动启动主备库
+
+测试步骤:
+
+1. 同时reboot主备节点机器
+
+    ```bash
+    reboot
+    reboot
+    ```
+
+2. 开启主备node_run脚本
+
+3. 主备机器开启后手动启动主备库
+
+测试结果:
+
+tps在关库后降至0，启动集群后大约15秒后tps恢复至9000
+
+<br/>
+
+## 仲裁+主节点异常宕机
+
+测试方案:
+
+同时关闭主库机器和下线仲裁的ip
+
+测试步骤:
+
+1. 同时关闭主库机器和下线仲裁的ip
+
+2. 备库查询状态
+
+3. 启动主库以及主库监控脚本
+
+    ```bash
+    gs_ctl start -D /gaussdata/openGauss/db1 -M primary
+    ```
+
+4. 查询集群状态
+
+测试结果:
+
+- 关掉主库和仲裁后，tps从9000降到0
+- 主库回来后tps恢复到9000
+
+<br/>
+
+## 仲裁+备节点异常宕机
+
+测试方案:
+
+同时关闭备库机器和移除仲裁的ip
+
+测试步骤:
+
+1. 同时关闭备库机器和移除仲裁的ip
+
+2. 查询主库
+
+3. 没有其他现象
+
+4. 备库恢复正常之后，启动备库监控脚本后，主库脚本报错消失
+
+5. 启动备库
+
+6. 查询集群状态
diff --git a/product/zh/docs-mogdb/v3.0/about-mogdb/test-report/ha/2-network-exception-testing.md b/product/zh/docs-mogdb/v3.0/about-mogdb/test-report/ha/2-network-exception-testing.md
new file mode 100644
index 0000000000000000000000000000000000000000..d33baaa5fd4955a4de570126ae4a307c7ead693e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/about-mogdb/test-report/ha/2-network-exception-testing.md
@@ -0,0 +1,175 @@
+---
+title: MogDB网络异常测试
+summary: MogDB网络异常测试
+author: Liu Xu
+date: 2021-03-04
+---
+
+# MogDB网络异常测试
+
+## 测试范围
+
+1. 主节点服务网卡异常
+2. 主节点心跳网卡异常
+3. 节点服务+心跳网卡异常
+4. 从节点服务网卡异常
+5. 从节点心跳网卡异常
+6. 主机VIP异常（掉线）
+
+<br/>
+
+## 测试环境
+
+| 类别     |      服务端配置       |  客户端配置   | 数量  |
+| -------- | :-------------------: | :-----------: | :---: |
+| CPU      |      Kunpeng 920      |  Kunpeng 920  |  128  |
+| 内存     |     DDR4,2933MT/s     | DDR4,2933MT/s | 2048G |
+| 硬盘     |       Nvme 3.5T       |    Nvme 3T    |  4个  |
+| 文件系统 |          Xfs          |      Xfs      |   4   |
+| OS       | openEuler 20.03 (LTS) |   Kylin V10   |       |
+| 数据库   |   MogDB1.1.0安装包    |               |       |
+| 测试工具 |        pgbench        |               |       |
+
+<br/>
+
+## 主节点服务网卡异常
+
+测试方案:
+
+1. 先关闭网卡再开启
+2. 观察数据库状态
+
+测试步骤:
+
+1. 记录初始集群状态
+2. 先关闭网卡再开启
+3. 观察备库状态
+4. 备库节点无法连接主库
+5. 查询集群状态，主备未发生切换
+
+测试结果:
+
+1. 未发生切换
+2. 主库网络恢复正常后,备库从disconnect状态恢复normal状态
+3. TPS在主库服务网卡异常时从9000跌到0。在开启服务网卡后约15s TPS从0升至9000
+
+<br/>
+
+## 主节点心跳网卡异常
+
+测试方案:
+
+1. 先关闭网卡并开启
+2. 观察数据库状态
+
+测试步骤:
+
+1. 观察数据库状态
+
+2. 关闭网卡再开启
+3. 观察数据库状态
+4. 发现未发生切换
+5. 观察集群状态
+
+测试结果:
+
+1. 未发生切换
+
+2. 未观察到此过程中的TPS发生变化
+
+<br/>
+
+## 主节点服务+心跳网卡异常
+
+测试方案:
+
+1. 先关闭网卡再开启
+
+2. 观察数据库状态
+
+测试步骤:
+
+1. 观察初始数据库状态
+
+2. 先关闭网卡再开启
+
+3. 主库正常
+
+测试结果:
+
+1. 未发生切换
+
+2. 在服务网卡断开后，tps从9000降到0，服务恢复后TPS升到9000
+
+<br/>
+
+## 从节点服务网卡异常
+
+测试方案:
+
+1. 先关闭网卡再开启
+
+2. 观察数据库状态
+
+测试步骤:
+
+1. 记录初始集群状态
+
+2. 先闭网卡再开启
+
+3. 观察主库状态
+
+4. 备库服务网卡ip ping失败
+
+5. 主备未切换
+
+测试结果:
+
+1. 备库监控脚本报心跳错误,主备未发生切换
+
+2. 备机服务网卡异常后，主库TPS上升到13000，备机服务网卡恢复后,主库TPS恢复9000
+
+<br/>
+
+## 从节点心跳网卡异常
+
+测试方案:
+
+1. 先关闭网卡60s，再开启
+
+2. 观察数据库状态
+
+测试步骤:
+
+1. 观察数据库初始状态
+
+2. 先关闭网卡60s，再开启
+
+3. 脚本执行完毕后观察树据库状态
+   发现未发生切换，主库监控脚本报告备库服务网卡ip ping失败
+
+测试结果:
+
+1. 未发生切换
+
+<br/>
+
+## 主机VIP异常（掉线）
+
+测试方案:
+
+先关闭再开启网卡bond0:1
+
+测试步骤:
+
+1. 先关闭再开启网卡bond0:1
+
+2. 观察数据库状态
+
+3. 观察vip
+
+测试结果:
+
+1. 主库vip自动上线
+
+2. TPS在vip先下线再上线之后恢复了正常
diff --git a/product/zh/docs-mogdb/v3.0/about-mogdb/test-report/ha/3-routine-maintenance-testing.md b/product/zh/docs-mogdb/v3.0/about-mogdb/test-report/ha/3-routine-maintenance-testing.md
new file mode 100644
index 0000000000000000000000000000000000000000..9ec9a578be3a5f9c77746e8fab1b2fa8b5725572
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/about-mogdb/test-report/ha/3-routine-maintenance-testing.md
@@ -0,0 +1,158 @@
+---
+title: MogDB日常维护测试
+summary: MogDB日常维护测试
+author: Liu Xu
+date: 2021-03-04
+---
+
+# MogDB日常维护测试
+
+## 测试范围
+
+1. HA工具切换switchover
+
+2. gs_ctl切换 switchover
+
+3. HA工具切换failover
+
+4. gs_ctl切换 failover
+
+5. gs_ctl启动与HA配合相悖测试
+
+6. 双主脑裂测试
+
+<br/>
+
+## 测试环境
+
+| 类别     |      服务端配置       |  客户端配置   | 数量  |
+| -------- | :-------------------: | :-----------: | :---: |
+| CPU      |      Kunpeng 920      |  Kunpeng 920  |  128  |
+| 内存     |     DDR4,2933MT/s     | DDR4,2933MT/s | 2048G |
+| 硬盘     |       Nvme 3.5T       |    Nvme 3T    |  4个  |
+| 文件系统 |          Xfs          |      Xfs      |   4   |
+| OS       | openEuler 20.03 (LTS) |   Kylin V10   |       |
+| 数据库   |   MogDB1.1.0安装包    |               |       |
+| 测试工具 |        pgbench        |               |       |
+
+<br/>
+
+## HA工具切换switchover
+
+测试步骤:
+
+1. 查询数据库状态。
+
+2. 在备库上执行切换命令，之后查询数据库状态。
+
+    ```
+    /home/omm/venv/bin/python3 /home/omm/openGaussHA_standlone/switch.py -config /home/omm/openGaussHA_standlone/node.conf --switchover
+    ```
+
+3. 在新主库上查询vip。
+
+测试结果:
+
+主备角色切换正常。
+
+<br/>
+
+## gs_ctl切换 switchover
+
+测试步骤:
+
+1. 查询数据库状态。
+2. 使用命令进行切换，完成后查询状态。
+3. 查询vip。
+
+测试结果:
+
+主备角色切换正常。
+
+<br/>
+
+## HA工具切换failover
+
+测试步骤:
+
+1. 查看数据库当前状态。
+
+2. 执行ha的failover命令。
+
+3. 观察集群状态。
+
+4. 发现原备库成为新主库。
+
+测试结果:
+
+1. 原先的备库成为新主库并有了vip。
+
+2. 原先的主库被杀掉。
+
+3. TPS在failover之后约10秒从6000升到13000。
+
+<br/>
+
+## gs_ctl切换 failover
+
+测试步骤:
+
+1. 查看数据库当前状态。
+
+2. 执行gs_ctl的failover命令。
+
+3. 观察新主库状态。
+
+4. 观察原先的主库。
+
+5. 观察脚本变化。
+
+测试结果:
+
+1. 新主库等待10s被自动关闭,原先的主库不受影响，vip依然在原先的主库上。
+
+2. 在备库failover后约5、6秒，TPS从9000升到13000。除波动外无其他变化。
+
+<br/>
+
+## gs_ctl启动与HA配合相悖测试
+
+测试步骤:
+
+1. 记录集群状态。
+
+2. 同时stop主库和备库。
+
+3. gs_ctl 启动主库和备库，指定原来的备库为主库，主库为备库。
+
+4. 观察脚本及集群状态。
+
+测试结果:
+
+1. HA配置跟随实际情况调整。
+
+2. TPS在关闭主库和备库库后从9000降至0，HA在检测到集群配置改变并在10s内修复挂起了新主库的vip，之后后约5、6s，TPS从0升到13000。
+
+<br/>
+
+## 双主脑裂测试
+
+测试步骤:
+
+1. 查看当前集群状态。
+
+2. 用gs_ctl 命令重启备库为主库。
+
+测试结果:
+
+1. 超时10s后，非正常操作重新start的主库被监控脚本kill掉。
+
+2. 修复备库并加入集群。
+
+    ```
+    gs_ctl build -b full -D /gaussdata/openGauss/db1
+    ```
+
+3. 重启备库为主库后TPS从6000升到13000。
+
+4. 备库重新加入集群后TPS从13000降到9000的一主一备水平。
diff --git a/product/zh/docs-mogdb/v3.0/about-mogdb/test-report/ha/4-service-exception-testing.md b/product/zh/docs-mogdb/v3.0/about-mogdb/test-report/ha/4-service-exception-testing.md
new file mode 100644
index 0000000000000000000000000000000000000000..660b77d7d6e0227f5984e492d06658ac9043f94f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/about-mogdb/test-report/ha/4-service-exception-testing.md
@@ -0,0 +1,96 @@
+---
+title: MogDB服务异常测试
+summary: MogDB服务异常测试
+author: Liu Xu
+date: 2021-03-04
+---
+
+# MogDB服务异常测试
+
+## 测试范围
+
+1. 从节点数据库进程异常
+
+2. 从库监控脚本异常
+
+3. 主库文件系统异常 （影响HA进程）
+
+<br/>
+
+## 测试环境
+
+| 类别     |      服务端配置       |  客户端配置   | 数量  |
+| -------- | :-------------------: | :-----------: | :---: |
+| CPU      |      Kunpeng 920      |  Kunpeng 920  |  128  |
+| 内存     |     DDR4,2933MT/s     | DDR4,2933MT/s | 2048G |
+| 硬盘     |       Nvme 3.5T       |    Nvme 3T    |  4个  |
+| 文件系统 |          Xfs          |      Xfs      |   4   |
+| OS       | openEuler 20.03 (LTS) |   Kylin V10   |       |
+| 数据库   |   MogDB1.1.0安装包    |               |       |
+| 测试工具 |        pgbench        |               |       |
+
+<br/>
+
+## 从节点数据库进程异常
+
+测试步骤:
+
+kill掉数据库进程。
+
+测试结果:
+
+1. 观察集群状态。
+
+2. 备库脚本显示心跳失败。
+
+3. 未发生切换。
+
+4. 在备库执行命令。
+
+    ```
+    gs_ctl start -D /gaussdata/openGauss/db1 -M standby
+    ```
+
+5. 集群恢复正常，自始至终未发生切换操作。
+
+6. 在kill掉备库进程时，主库TPS从9000升到13000。
+
+7. 未观察到主备切换操作。
+
+<br/>
+
+## 从库监控脚本异常
+
+测试步骤:
+
+kill掉主库监控脚本。
+
+测试结果:
+
+1. 观察集群状态。
+
+2. 未观察到切换操作。
+
+3. 主库监控脚本报告从库的脚本异常。
+
+4. 恢复从库监控脚本。
+
+5. TPS维持在9000。
+
+<br/>
+
+## 主库文件系统异常 （影响HA进程）
+
+测试步骤:
+
+修改ha所调用的主库数据库脚本权限，如gs_ctl。
+
+测试结果:
+
+1. 修改了gs_ctl的rwx权限后，主库监控脚本报告心跳失败。
+
+2. 检测不到实例状态。
+
+3. 查询当前集群状态。
+
+4. 等待约两分钟，未见发生切换。
diff --git a/product/zh/docs-mogdb/v3.0/about-mogdb/test-report/ha/MogDB-ha-test-report.md b/product/zh/docs-mogdb/v3.0/about-mogdb/test-report/ha/MogDB-ha-test-report.md
new file mode 100644
index 0000000000000000000000000000000000000000..44f64234eff68fe8167b31b2881ccf4d37bacfc9
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/about-mogdb/test-report/ha/MogDB-ha-test-report.md
@@ -0,0 +1,36 @@
+---
+title: 高可用测试
+summary: 高可用测试
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# 高可用测试
+
+## 测试目的
+
+数据库的高可用测试是为了最大程度地为用户提供服务，避免服务器宕机等故障带来的服务中断。数据库的高可用性不仅仅体现在数据库能否持续提供服务，而且也体现在能否保证数据的一致性。
+
+## 测试环境
+
+| 类别     |      服务端配置       |  客户端配置   | 数量  |
+| -------- | :-------------------: | :-----------: | :---: |
+| CPU      |      Kunpeng 920      |  Kunpeng 920  |  128  |
+| 内存     |     DDR4,2933MT/s     | DDR4,2933MT/s | 2048G |
+| 硬盘     |       Nvme 3.5T       |    Nvme 3T    |  4个  |
+| 文件系统 |          Xfs          |      Xfs      |   4   |
+| OS       | openEuler 20.03 (LTS) |   Kylin V10   |       |
+| 数据库   |     MogDB 安装包      |               |       |
+| 测试工具 |        pgbench        |               |       |
+
+## 高可用、可扩展性测试
+
+| 序号 | 测试项               | 描述                                                         |
+| ---- | -------------------- | ------------------------------------------------------------ |
+| 1    | 读写分离集群实现     | 支持按照读写进行路由，并实现读、写的任务分发                 |
+| 2    | 扩容/缩容            | 在负载场景下，添加/减少物理设备时，能够保持前端应用不间断    |
+| 3    | 共享存储集群         | 支持2节点共享存储集群，支持故障自动切换，支持并发事务的负载均衡 |
+| 4    | 服务异常测试         | 支持在从节点数据库进程异常 、从库监控脚本异常和主库文件系统异常场景下最大程度的保证应用的可用性 |
+| 5    | 日常维护测试         | 支持gs_ctl(数据库服务控制工具)和MogHA(高可用组件)进行Switchover和Failover的切换操作 |
+| 6    | 数据库服务器异常测试 | 能够提供在主节点异常宕机、备节点异常宕机、仲裁节点异常宕机、主节点和备节点异常宕机和仲裁+主节点异常宕机的场景下应用的可用性和稳定性 |
+| 7    | 网络异常测试         | 能够提供在主节点服务网卡异常、主节点心跳网卡异常、主节点服务+心跳网卡异常、从节点服务网卡异常、主机VIP异常的场景下最大程度的保证应用的可用性 |
diff --git a/product/zh/docs-mogdb/v3.0/about-mogdb/test-report/performance/1-performance-test-overview.md b/product/zh/docs-mogdb/v3.0/about-mogdb/test-report/performance/1-performance-test-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..b5dd717d6e69271377d1f6b06e198035a449defd
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/about-mogdb/test-report/performance/1-performance-test-overview.md
@@ -0,0 +1,110 @@
+---
+title: 性能测试简述
+summary: 性能测试简述
+author: Liu Xu
+date: 2021-03-04
+---
+
+# 性能测试简述
+
+<br/>
+
+## 测试相关指标
+
+### 数据量
+
+每个仓库约70MB数据量，为了让数据量更加符合实际使用场景，初始化创建1000个仓库，添加相关索引后，数据库大小在100G左右。
+
+<br/>
+
+### 并发数
+
+模拟真实的用户行为，同时在线请求操作的客户端数量。
+
+<br/>
+
+### 系统平均负载
+
+系统负载指系统CPU繁忙程度的度量，即有多少进程在等待被CPU调度，反应整个系统的压力，而系统平均负载被定义为在特定时间间隔内运行队列中的平均进程树，这个一段时间一般取1分钟、5分钟、10分钟。
+
+<br/>
+
+### CPU使用率
+
+CPU使用率其实是指运行的程序占用的CPU资源，表示你的机器在某个时间点的运行程序的情况。使用率越高，说明你的机器在这个时间上运行了很多程序，反之较少。使用率的高低与CPU强弱有直接关系，通过CPU的使用率来判断CPU是否达到瓶颈。
+
+<br/>
+
+### IOPS
+
+IOPS（Input/OutputOperatIOns Per Second）是一个用于计算机存储设备（如硬盘（HDD）、固态硬盘（SSD）或存储区域网络（SAN））性能测试的量测方式，可以视为是每秒的读写次数，是衡量磁盘性能的主要指标之一。IOPS是指单位时间内系统能处理的I/O请求数量，一般以每秒处理的I/O请求数量为单位，I/O请求通常为读或写数据操作请求。
+
+<br/>
+
+### IO延时
+
+IO响应时间也被称为IO延时(IOLatency)，IO响应时间就是从操作系统内核发出的一个读或者写的IO命令到操作系统内核接收到IO回应的时间，注意不要和单个IO时间混淆了，单个IO时间仅仅指的是IO操作在磁盘内部处理的时间，而IO响应时间还要包括IO操作在IO等待队列中所花费的等待时间。
+
+<br/>
+
+### tpmC
+
+TPC-C使用三种性能和价格度量，其中性能由TPC-C吞吐率衡量，单位是tpmC。tpm是transactions per minute的简称；C指TPC中的C基准程序。它的定义是每分钟内系统处理的新订单个数。
+
+<br/>
+
+## 准备测试程序
+
+### 测试工具介绍
+
+BenchmarkSQL是一款经典的开源数据库测试工具，内嵌了TPC-C测试脚本，可以对PostgreSQL、MySQL、Oracle以及SQL Server等数据库直接进行测试。它通过JDBC测试OLTP（联机事务处理, Online TransactIOn Processing）的TPC-C。
+
+<br/>
+
+### 测试规范说明
+
+TPC-C 是一个对 OLTP（联机交易处理）系统进行测试的规范，使用一个商品销售模型对 OLTP 系统进行测试，其中包含五类事务, 其事务内容及特点如下:
+
+- **NewOrder - 新订单的生成**
+
+    事务内容: 对于任意一个客户端,从固定的仓库随机选取 5-15  件商品,创建新订单.其中 1%的订单要由假想的用户操作失败而回滚。
+
+    主要特点: 中量级、读写频繁、要求响应快。
+
+- **Payment - 订单付款**
+
+    事务内容: 对于任意一个客户端,从固定的仓库随机选取一个辖区及其内用户,采用随机的金额支付一笔订单,并作相应历史纪录。
+
+    主要特点: 轻量级、读写频繁、要求响应快。
+
+- **OrderStatus - 最近订单查询**
+
+    事务内容: 对于任意一个客户端,从固定的仓库随机选取一个辖区及其内用户，读取其最后一条订单，显示订单内每件商品的状态。
+
+    主要特点: 中量级、只读频率低、要求响应快。
+
+- **Delivery - 配送**
+
+    事务内容: 对于任意一个客户端,随机选取一个发货包，更新被处理订单的用户余额，并把该订单从新订单中删除。
+
+    主要特点: 1-10 个批量，读写频率低、较宽松的响应时间。
+
+- **StockLevel - 库存缺货状态分析**
+
+    事物内容: 对于任意一个客户端，从固定的仓库和辖区随机选取最后 20 条订单，查看订单中所有的货物的库存，计算并显示所有库存低于随机生成域  值的商品数量。
+
+    主要特点: 重量级，只读频率低,较宽松的响应时间。
+
+<br/>
+
+### 测试规则描述
+
+在测试开始前，TPC-C Benchmark 规定了数据库的初始状态，也就是数据库中数据生成的规则，其中 ITEM 表中固定包含 10 万种商品，仓库的数量可进行调整，本次测试初始化WAREHOUSE 表中有 1000 条记录，那么:
+
+- STOCK 表中应有 1000 * 10 万条记录（每个仓库对应 10 万种商品的库存数据）
+- DISTRICT 表中应有1000 * 10 条记录（每个仓库为 10 个地区提供服务）
+- CUSTOMER 表中应有 1000 \* 10 \* 3000 条记录（每个地区有 3000 个客户）
+- HISTORY 表中应有 1000 \* 10 \* 3000 条记录（每个客户一条交易历史）
+- ORDER 表中应有 1000 \* 10 \* 3000 条记录（每个地区 3000 个订单），并且最后生成的 900 个订单被添加到 NEW-ORDER 表中，每个订单随机生成 5 ~ 15 条 ORDER-LINE 记录。
+
+> TPC-C 使用 tpmC 值（Transactions per Minute）来衡量系统最大有效吞吐量 (MQTh, Max Qualified Throughput)，其中 Transactions 以 NewOrder Transaction 为准，即最终衡量单位为每分钟处理的新订单数。
diff --git a/product/zh/docs-mogdb/v3.0/about-mogdb/test-report/performance/2-mogdb-on-kunpeng-performance-test-report.md b/product/zh/docs-mogdb/v3.0/about-mogdb/test-report/performance/2-mogdb-on-kunpeng-performance-test-report.md
new file mode 100644
index 0000000000000000000000000000000000000000..9c510ca7689aa5f6696d95e0251fbe202ae49cbc
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/about-mogdb/test-report/performance/2-mogdb-on-kunpeng-performance-test-report.md
@@ -0,0 +1,334 @@
+---
+title: MogDB on鲲鹏性能测试
+summary: MogDB on鲲鹏性能测试
+author: Liu Xu
+date: 2021-03-04
+---
+
+# MogDB on鲲鹏性能测试
+
+## 测试目的
+
+本文主要讲述了对MogDB 2.0.0 版本on鲲鹏进行的单节点和一主多备（同步备、异步备）的测试。
+
+<br/>
+
+## 测试环境
+
+### 环境配置
+
+| 类别     | 服务端配置            | 客户端配置    | 数量  |
+| -------- | --------------------- | ------------- | ----- |
+| CPU      | Kunpeng 920           | Kunpeng 920   | 128   |
+| 内存     | DDR4,2933MT/s         | DDR4,2933MT/s | 2048G |
+| 硬盘     | Nvme 3.5T             | Nvme 3T       | 4个   |
+| 文件系统 | Xfs                   | Xfs           | 4     |
+| OS       | openEuler 20.03 (LTS) | Kylin V10     |       |
+| 数据库   | MogDB 1.1.0安装包     |               |       |
+
+<br/>
+
+### 测试工具
+
+| 工具名称        | 用途                 |
+| ------------- | ---------------------------------|
+| Benchmarksql5.0 | BenchmarkSQL是对OLTP数据库主流测试标准TPC-C的开源JAVA实现,用于对数据库事务处理能力的评估测试。 |
+
+<br/>
+
+## 测试步骤
+
+### MogDB数据库端操作
+
+1. 获取数据库安装包
+
+2. 安装数据库
+
+3. 创建tpcc测试用户和数据库
+
+    ```bash
+    create user [username] identified by 'passwd';
+    grant [origin user] to [username];
+    create database [dbname];
+    ```
+
+4. 停止数据库修改数据库配置文件postgresql.conf数据库，在末尾添加配置参数（单节点测试追加参数如下）
+
+    ```bash
+    max_connections = 4096
+    allow_concurrent_tuple_update = true
+    audit_enabled = off
+    checkpoint_segments = 1024
+    cstore_buffers =16MB
+    enable_alarm = off
+    enable_codegen = false
+    enable_data_replicate = off
+    full_page_writes  = off
+    max_files_per_process = 100000
+    max_prepared_transactions = 2048
+    shared_buffers = 350GB
+    use_workload_manager = off
+    wal_buffers = 1GB
+    work_mem = 1MB
+    log_min_messages  = FATAL
+    transaction_isolation = 'read committed'
+    default_transaction_isolation = 'read committed'
+    synchronous_commit = on
+    fsync  = on
+    maintenance_work_mem = 2GB
+    vacuum_cost_limit = 2000
+    autovacuum = on
+    autovacuum_mode = vacuum
+    autovacuum_max_workers = 5
+    autovacuum_naptime = 20s
+    autovacuum_vacuum_cost_delay =10
+    xloginsert_locks = 48
+    update_lockwait_timeout =20min
+    enable_mergejoin = off
+    enable_nestloop = off
+    enable_hashjoin = off
+    enable_bitmapscan = on
+    enable_material = off
+    wal_log_hints = off
+    log_duration = off
+    checkpoint_timeout = 15min
+    enable_save_datachanged_timestamp =FALSE
+    enable_thread_pool = on
+    thread_pool_attr =  '812,4,(cpubind:0-27,32-59,64-91,96-123)'
+    enable_double_write = on
+    enable_incremental_checkpoint = on
+    enable_opfusion = on
+    advance_xlog_file_num = 10
+    numa_distribute_mode = 'all'
+    track_activities = off
+    enable_instr_track_wait = off
+    enable_instr_rt_percentile = off
+    track_counts =on
+    track_sql_count = off
+    enable_instr_cpu_timer = off
+    plog_merge_age = 0
+    session_timeout = 0
+    enable_instance_metric_persistent = off
+    enable_logical_io_statistics = off
+    enable_user_metric_persistent =off
+    enable_xlog_prune = off
+    enable_resource_track = off
+    instr_unique_sql_count = 0
+    enable_beta_opfusion = on
+    enable_beta_nestloop_fusion = on
+    autovacuum_vacuum_scale_factor = 0.02
+    autovacuum_analyze_scale_factor = 0.1
+    client_encoding = UTF8
+    lc_messages = en_US.UTF-8
+    lc_monetary = en_US.UTF-8
+    lc_numeric = en_US.UTF-8
+    lc_time = en_US.UTF-8
+    modify_initial_password = off
+    ssl = off
+    enable_memory_limit = off
+    data_replicate_buffer_size = 16384
+    max_wal_senders = 8
+    log_line_prefix = '%m %u %d %h %p %S'
+    vacuum_cost_limit = 10000
+    max_process_memory = 12582912
+    recovery_max_workers = 1
+    recovery_parallelism = 1
+    explain_perf_mode = normal
+    remote_read_mode = non_authentication
+    enable_page_lsn_check = off
+    pagewriter_sleep = 100
+    ```
+
+<br/>
+
+### benchmarksql端操作
+
+1. 修改配置文件
+
+    进入benchmarksql安装目录下，找到run目录下的配置文件[config file]
+
+    ```text
+    db=postgres
+
+    driver=org.postgresql.Driver
+
+    conn=jdbc:postgresql://[ip:port]/tpcc?prepareThreshold=1&batchMode=on&fetchsize=10
+
+    user=[user]
+
+    password=[passwd]
+
+    warehouses=1000
+
+    loadWorkers=80
+
+    terminals=812
+
+    //To run specified transactions per terminal- runMins must equal zero
+
+    runTxnsPerTerminal=0
+
+    //To run for specified minutes- runTxnsPerTerminal must equal zero
+
+    runMins=30
+
+    //Number of total transactions per minute
+
+    limitTxnsPerMin=0
+
+    //Set to true to run in 4.x compatible mode. Set to false to use the
+
+    //entire configured database evenly.
+
+    terminalWarehouseFixed=false  #true
+
+    //The following five values must add up to 100
+
+    //The default percentages of 45, 43, 4, 4 & 4 match the TPC-C spec
+
+    newOrderWeight=45
+
+    paymentWeight=43
+
+    orderStatusWeight=4
+
+    deliveryWeight=4
+
+    stockLevelWeight=4
+
+    // Directory name to create for collecting detailed result data.
+
+    // Comment this out to suppress.
+
+    //resultDirectory=my_result_%tY-%tm-%td_%tH%tM%tS
+
+    //osCollectorScript=./misc/os_collector_linux.py
+
+    //osCollectorInterval=1
+
+    //osCollectorSSHAddr=tpcc@127.0.0.1
+
+    //osCollectorDevices=net_eth0 blk_sda blk_sdg blk_sdh blk_sdi blk_sdj
+    ```
+
+2. 运行runDataBuild.sh生成数据
+
+    ```
+    ./runDatabaseBuild.sh [config file]
+    ```
+
+3. 运行runBenchmark.sh测试数据库
+
+    ```
+    ./runBenchmark.sh [config file]
+    ```
+
+<br/>
+
+### 操作系统配置
+
+1. 修改操作系统内核PAGESIZE（仅EulerOS需执行此步骤）
+
+    **安装kernel-4.19.36-1.aarch64.rpm**
+
+    ```
+    # rpm -Uvh --force --nodeps kernel-4.19.36-1.aarch64.rpm
+
+    # *: 此文件是基于linux 4.19.36的内核包，获取路径如下:
+
+    # 10.44.133.121 (root/Huawei12#$)
+
+    /data14/xy_packages/kernel-4.19.36-1.aarch64.rpm
+    ```
+
+    **修改操作系统内核配置文件中root的启动项**
+
+    ```
+    # vim /boot/efi/EFI/euleros/grubenv  //修改前备份grubenv文件
+
+    # GRUB Environment Block
+
+    saved_entry=EulerOS (4.19.36) 2.0 (SP8)   -- 此处修改为4.19.36
+    ```
+
+<br/>
+
+### 文件系统
+
+1. 修改xfs文件系统blocksize为8K
+
+    \# 下面命令查看当前挂载的nvme盘
+
+    ```bash
+    # df -h | grep nvme
+    /dev/nvme0n1         3.7T  2.6T  1.2T  69% /data1
+    /dev/nvme1n1         3.7T  1.9T  1.8T  51% /data2
+    /dev/nvme2n1         3.7T  2.2T  1.6T  59% /data3
+    /dev/nvme3n1         3.7T  1.4T  2.3T  39% /data4
+
+    # xfs_info命令可以查看nvme盘的信息
+
+    xfs_info /data1
+    ```
+
+2. 针对需要修改的磁盘，备份所需的数据
+
+3. 重新格式化磁盘
+
+    ```bash
+    # 以/dev/nvme0n1盘，加载点为/data1为例，相关参考命令如下
+
+    umount /data1
+
+    mkfs.xfs -b size=8192 /dev/nvme0n1 -f
+
+    mount /dev/nvme0n1 /data1
+    ```
+
+<br/>
+
+## 测试项及结论
+
+### 测试结果汇总
+
+| 测试项   | 数据量 | 并发数 | CPU平均使用率 | IOPS   | IO延时   | WAL数量 | tpmC       | 测试时长 |
+| ------ | ------ | ------ | --------- | ------ | -------- | ------- | ---------- | -------- |
+| 单节点   | 100G   | 500    | 77.49%        | 17.96K | 819.05us | 13260   | 1567226.12 | 10分钟   |
+| 一主一备 | 100G   | 500    | 57.64%        | 5.31K  | 842.78us | 13272   | 1130307.87 | 10分钟   |
+| 一主两备 | 100G   | 500    | 60.77%        | 5.3K   | 821.66us | 14324   | 1201560.28 | 10分钟   |
+
+<br/>
+
+### 单节点
+
+- tpmC
+
+    ![单节点tpmC](https://cdn-mogdb.enmotech.com/docs-media/mogdb/about-mogdb/mogdb-on-kunpeng-1.png)
+
+- 系统数据
+
+    ![单节点系统数据](https://cdn-mogdb.enmotech.com/docs-media/mogdb/about-mogdb/mogdb-on-kunpeng-2.png)
+
+<br/>
+
+### 一主一备
+
+- tpmC
+
+    ![一主一备tpmC](https://cdn-mogdb.enmotech.com/docs-media/mogdb/about-mogdb/mogdb-on-kunpeng-3.png)
+
+- 系统数据
+
+    ![一主一备系统数据](https://cdn-mogdb.enmotech.com/docs-media/mogdb/about-mogdb/mogdb-on-kunpeng-4.png)
+
+<br/>
+
+### 一主两备
+
+- tpmC
+
+    ![一主两备tpmC](https://cdn-mogdb.enmotech.com/docs-media/mogdb/about-mogdb/mogdb-on-kunpeng-5.png)
+
+- 系统数据
+
+    ![一主两备系统数据](https://cdn-mogdb.enmotech.com/docs-media/mogdb/about-mogdb/mogdb-on-kunpeng-6.png)
diff --git a/product/zh/docs-mogdb/v3.0/about-mogdb/test-report/performance/3-mogdb-on-x86-performance-test-report.md b/product/zh/docs-mogdb/v3.0/about-mogdb/test-report/performance/3-mogdb-on-x86-performance-test-report.md
new file mode 100644
index 0000000000000000000000000000000000000000..03e5b38dbebb8009c1615231e182996c9af05754
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/about-mogdb/test-report/performance/3-mogdb-on-x86-performance-test-report.md
@@ -0,0 +1,672 @@
+---
+title: MogDB on x86性能测试
+summary: MogDB on x86性能测试
+author: Liu Xu
+date: 2021-03-04
+---
+
+# MogDB on x86性能测试
+
+## 测试目的
+
+本文主要讲述了对MogDB 2.0.0 版本on x86进行的单节点和一主多备（同步备、异步备）的测试。
+
+<br/>
+
+## 测试环境
+
+### 环境配置
+
+| 服务器类型       | Fit Server                               | NFS5280M5                                |
+| -------------- | ---------------------------------------- | ---------------------------------------- |
+| CPU            | 144cIntel® Xeon(R) Gold 6240 CPU@2.60GHz | 64cIntel® Xeon(R) Gold 5218 CPU @2.30GHz |
+| 内存            | 768G                                     | 128G                                     |
+| 硬盘            | SAS SSD                                  | SAS SSD                                  |
+| 网卡            | 10GE                                     | 10GE                                     |
+
+<br/>
+
+### 测试工具
+
+| 工具名称        | 用途                                                    |
+| --------------- | ----------------------------------------------------- |
+| Benchmarksql5.0 | BenchmarkSQL是对OLTP数据库主流测试标准TPC-C的开源JAVA实现，用于对数据库事务处理能力的评估测试。 |
+
+<br/>
+
+## 测试步骤
+
+### MogDB数据库端操作
+
+1. 获取数据库安装包
+
+2. 安装数据库
+
+3. 创建tpcc测试用户和数据库
+
+    ```sql
+    create user [username] identified by ‘passwd’;
+    grant [origin user] to [username];
+    create database [dbname];
+    ```
+
+4. 停止数据库修改数据库配置文件postgresql.conf数据库，在末尾添加配置参数（单节点测试追加参数如下）
+
+    ```bash
+    max_connections = 4096
+
+    allow_concurrent_tuple_update = true
+
+    audit_enabled = off
+
+    checkpoint_segments = 1024
+
+    cstore_buffers =16MB
+
+    enable_alarm = off
+
+    enable_codegen = false
+
+    enable_data_replicate = off
+
+    full_page_writes  = off
+
+    max_files_per_process = 100000
+
+    max_prepared_transactions = 2048
+
+    shared_buffers = 350GB
+
+    use_workload_manager = off
+
+    wal_buffers = 1GB
+
+    work_mem = 1MB
+
+    log_min_messages  = FATAL
+
+    transaction_isolation = 'read committed'
+
+    default_transaction_isolation = 'read committed'
+
+    synchronous_commit = on
+
+    fsync  = on
+
+    maintenance_work_mem = 2GB
+
+    vacuum_cost_limit = 2000
+
+    autovacuum = on
+
+    autovacuum_mode = vacuum
+
+    autovacuum_max_workers = 5
+
+    autovacuum_naptime = 20s
+
+    autovacuum_vacuum_cost_delay =10
+
+    xloginsert_locks = 48
+
+    update_lockwait_timeout =20min
+
+    enable_mergejoin = off
+
+    enable_nestloop = off
+
+    enable_hashjoin = off
+
+    enable_bitmapscan = on
+
+    enable_material = off
+
+    wal_log_hints = off
+
+    log_duration = off
+
+    checkpoint_timeout = 15min
+
+    enable_save_datachanged_timestamp =FALSE
+
+    enable_thread_pool = on
+
+    thread_pool_attr =  '812,4,(cpubind:0-27,32-59,64-91,96-123)'
+
+    enable_double_write = on
+
+    enable_incremental_checkpoint = on
+
+    enable_opfusion = on
+
+    advance_xlog_file_num = 10
+
+    numa_distribute_mode = 'all'
+
+    track_activities = off
+
+    enable_instr_track_wait = off
+
+    enable_instr_rt_percentile = off
+
+    track_counts =on
+
+    track_sql_count = off
+
+    enable_instr_cpu_timer = off
+
+    plog_merge_age = 0
+
+    session_timeout = 0
+
+    enable_instance_metric_persistent = off
+
+    enable_logical_io_statistics = off
+
+    enable_user_metric_persistent =off
+
+    enable_xlog_prune = off
+
+    enable_resource_track = off
+
+    instr_unique_sql_count = 0
+
+    enable_beta_opfusion = on
+
+    enable_beta_nestloop_fusion = on
+
+    autovacuum_vacuum_scale_factor = 0.02
+
+    autovacuum_analyze_scale_factor = 0.1
+
+    client_encoding = UTF8
+
+    lc_messages = en_US.UTF-8
+
+    lc_monetary = en_US.UTF-8
+
+    lc_numeric = en_US.UTF-8
+
+    lc_time = en_US.UTF-8
+
+    modify_initial_password = off
+
+    ssl = off
+
+    enable_memory_limit = off
+
+    data_replicate_buffer_size = 16384
+
+    max_wal_senders = 8
+
+    log_line_prefix = '%m %u %d %h %p %S'
+
+    vacuum_cost_limit = 10000
+
+    max_process_memory = 12582912
+
+    recovery_max_workers = 1
+
+    recovery_parallelism = 1
+
+    explain_perf_mode = normal
+
+    remote_read_mode = non_authentication
+
+    enable_page_lsn_check = off
+
+    pagewriter_sleep = 100对方的
+    ```
+
+<br/>
+
+### benchmarksql端操作
+
+1. 修改配置文件
+
+    进入benchmarksql安装目录下，找到run目录下的配置文件[config file]
+
+    ```bash
+    db=postgres
+
+    driver=org.postgresql.Driver
+
+    conn=jdbc:postgresql://[ip:port]/tpcc?prepareThreshold=1&batchMode=on&fetchsize=10
+
+    user=[user]
+
+    password=[passwd]
+
+    warehouses=1000
+
+    loadWorkers=80
+
+    terminals=812
+
+    //To run specified transactions per terminal- runMins must equal zero
+
+    runTxnsPerTerminal=0
+
+    //To run for specified minutes- runTxnsPerTerminal must equal zero
+
+    runMins=30
+
+    //Number of total transactions per minute
+
+    limitTxnsPerMin=0
+
+    //Set to true to run in 4.x compatible mode. Set to false to use the
+
+    //entire configured database evenly.
+
+    terminalWarehouseFixed=false  #true
+
+    //The following five values must add up to 100
+
+    //The default percentages of 45, 43, 4, 4 & 4 match the TPC-C spec
+
+    newOrderWeight=45
+
+    paymentWeight=43
+
+    orderStatusWeight=4
+
+    deliveryWeight=4
+
+    stockLevelWeight=4
+
+    // Directory name to create for collecting detailed result data.
+
+    // Comment this out to suppress.
+
+    //resultDirectory=my_result_%tY-%tm-%td_%tH%tM%tS
+
+    //osCollectorScript=./misc/os_collector_linux.py
+
+    //osCollectorInterval=1
+
+    //osCollectorSSHAddr=tpcc@127.0.0.1
+
+    //osCollectorDevices=net_eth0 blk_sda blk_sdg blk_sdh blk_sdi blk_sdj
+    ```
+
+2. 运行runDataBuild.sh生成数据
+
+    ```
+    ./runDatabaseBuild.sh [config file]
+    ```
+
+3. 运行runBenchmark.sh测试数据库
+
+    ```
+    ./runBenchmark.sh [config file]
+    ```
+
+<br/>
+
+### 操作系统参数
+
+```bash
+vm.dirty_background_ratIO=5
+
+vm.dirty_ratIO=10
+
+kernel.sysrq=0
+
+net.ipv4.ip_forward=0
+
+net.ipv4.conf.all.send_redirects=0
+
+net.ipv4.conf.default.send_redirects=0
+
+net.ipv4.conf.all.accept_source_route=0
+
+net.ipv4.conf.default.accept_source_route=0
+
+net.ipv4.conf.all.accept_redirects=0
+
+net.ipv4.conf.default.accept_redirects=0
+
+net.ipv4.conf.all.secure_redirects=0
+
+net.ipv4.conf.default.secure_redirects=0
+
+net.ipv4.icmp_echo_ignore_broadcasts=1
+
+net.ipv4.icmp_ignore_bogus_error_responses=1
+
+net.ipv4.conf.all.rp_filter=1
+
+net.ipv4.conf.default.rp_filter=1
+
+net.ipv4.tcp_syncookies=1
+
+kernel.dmesg_restrict=1
+
+net.ipv6.conf.all.accept_redirects=0
+
+net.ipv6.conf.default.accept_redirects=0
+
+net.core.rmem_max = 21299200
+
+net.core.rmem_default = 21299200
+
+net.core.somaxconn = 65535
+
+net.ipv4.tcp_tw_reuse = 1
+
+net.sctp.sctp_mem = 94500000 915000000 927000000
+
+net.ipv4.tcp_max_tw_buckets = 10000
+
+net.ipv4.tcp_rmem = 8192 250000 16777216
+
+kernel.sem = 250 6400000 1000 25600
+
+net.core.wmem_default = 21299200
+
+kernel.shmall = 1152921504606846720
+
+net.core.wmem_max = 21299200
+
+net.sctp.sctp_rmem = 8192 250000 16777216
+
+net.core.netdev_max_backlog = 65535
+
+kernel.shmmax = 18446744073709551615
+
+net.sctp.sctp_wmem = 8192 250000 16777216
+
+net.ipv4.tcp_keepalive_intvl = 30
+
+net.ipv4.tcp_keepalive_time = 30
+
+net.ipv4.tcp_wmem = 8192 250000 16777216
+
+net.ipv4.tcp_max_syn_backlog = 65535
+
+vm.oom_panic_on_oom=0
+
+kernel.nmi_watchdog=0
+
+kernel.nmi_watchdog=0
+
+kernel.nmi_watchdog=0
+
+kernel.nmi_watchdog=0
+
+kernel.nmi_watchdog=0
+
+net.ipv4.tcp_timestamps = 1
+
+net.ipv4.tcp_tso_win_divisor = 30
+
+net.sctp.path_max_retrans = 10
+
+net.sctp.max_init_retransmits = 10
+
+net.ipv4.tcp_retries1 = 5
+
+net.ipv4.tcp_syn_retries = 5
+
+net.ipv4.tcp_synack_retries = 5
+
+kernel.core_uses_pid=1
+
+kernel.core_pattern=/home/core/core-%e-%u-%s-%t-%p
+
+kernel.nmi_watchdog=0
+
+kernel.nmi_watchdog=0
+
+kernel.nmi_watchdog=0
+
+kernel.nmi_watchdog=0
+
+kernel.core_pattern=/home/core/core-%e-%u-%s-%t-%h
+
+net.core.netdev_max_backlog = 65535
+
+net.core.rmem_default = 21299200
+
+net.core.rmem_max = 21299200
+
+net.core.somaxconn = 65535
+
+net.core.wmem_default = 21299200
+
+net.core.wmem_max = 21299200
+
+net.ipv4.conf.all.accept_redirects = 0
+
+net.ipv4.conf.all.rp_filter = 1
+
+net.ipv4.conf.all.secure_redirects = 0
+
+net.ipv4.conf.all.send_redirects = 0
+
+net.ipv4.conf.default.accept_redirects = 0
+
+net.ipv4.conf.default.accept_source_route = 0
+
+net.ipv4.conf.default.rp_filter = 1
+
+net.ipv4.conf.default.secure_redirects = 0
+
+net.ipv4.conf.default.send_redirects = 0
+
+net.ipv4.conf.enp135s0.accept_redirects = 0
+
+net.ipv4.conf.enp135s0.accept_source_route = 0
+
+net.ipv4.conf.enp135s0.forwarding = 1
+
+net.ipv4.conf.enp135s0.rp_filter = 1
+
+net.ipv4.conf.enp135s0.secure_redirects = 0
+
+net.ipv4.conf.enp135s0.send_redirects = 0
+
+net.ipv4.tcp_keepalive_intvl = 30
+
+net.ipv4.tcp_keepalive_time = 30
+
+net.ipv4.tcp_max_syn_backlog = 65535
+
+net.ipv4.tcp_max_tw_buckets = 10000
+
+net.ipv4.tcp_mem = 362715 483620 725430
+
+#net.ipv4.tcp_mem = 94500000 915000000 927000000
+
+net.ipv4.tcp_retries1 = 5
+
+net.ipv4.tcp_rmem = 8192     250000  16777216
+
+net.ipv4.tcp_syn_retries = 5
+
+net.ipv4.tcp_tso_win_divisor = 30
+
+net.ipv4.tcp_tw_reuse = 1
+
+net.ipv4.tcp_wmem = 8192     250000  16777216
+
+net.ipv4.udp_mem = 725430    967240  1450860
+
+#net.ipv4.tcp_max_orphans = 3276800
+
+#net.ipv4.tcp_fin_timeout = 60
+
+#net.ipv4.ip_local_port_range = 26000 65535
+
+net.ipv4.tcp_retries2 = 80
+
+#net.ipv4.ip_local_reserved_ports = 20050-30007
+
+vm.min_free_kbytes = 40140150
+```
+
+<br/>
+
+### 数据库参数
+
+| 参数项                            | MogDB                            |
+| --------------------------------- | -------------------------------- |
+| listen_addresses                  | 具体ip                           |
+| port                              | 26000                            |
+| max_connectIOns                   | 4096                             |
+| wal_level                         | hot_standby                      |
+| archive_mode                      | on                               |
+| archive_command                   | /bin/ture                        |
+| max_wal_senders                   | 16                               |
+| wal_keep_segments                 | 16                               |
+| max_replicatIOn_slots             | 8                                |
+| hot_standby                       | on                               |
+| logging_collector                 | on                               |
+| log_directory                     | 安装工具指定                     |
+| log_filename                      | PostgreSQL-%Y-%m-%d_%H%M%S.log   |
+| log_min_duratIOn_statement        | 1800000                          |
+| log_line_prefix                   | %m%c%d%p%a%x%n%e                 |
+| log_timezone                      | PRC                              |
+| datestyle                         | iso,mdy                          |
+| timezone                          | PRC                              |
+| default_text_search_config        | pg_catalog.english               |
+| applicatIOn_name                  | dn_6001                          |
+| max_prepared_transactIOns         | 2048                             |
+| shared_buffers                    | 350GB                            |
+| wal_buffers                       | 1GB                              |
+| work_mem                          | 64MB                             |
+| log_min_messages                  | FATAL                            |
+| synchronous_commit                | on                               |
+| fsync                             | on                               |
+| maintenance_work_mem              | 2GB                              |
+| autovacuum                        | on                               |
+| autovacuum_max_workers            | 5                                |
+| autovacuum_naptime                | 20s                              |
+| autovacuum_vacuum_cost_delay      | 10                               |
+| enable_mergejoin                  | off                              |
+| enable_nestloop                   | off                              |
+| enable_hashjoin                   | off                              |
+| enable_bitmapscan                 | on                               |
+| enable_material                   | off                              |
+| wal_log_hints                     | off                              |
+| log_duratIOn                      | off                              |
+| checkpoint_timeout                | 15min                            |
+| track_activities                  | off                              |
+| track_counts                      | on                               |
+| autovacuum_vacuum_scale_factor    | 0.02                             |
+| autovacuum_analyze_scale_factor   | 0.1                              |
+| ssl                               | off                              |
+| local_bind_address                | 具体IP                           |
+| max_inner_tool_connectIOns        | 10                               |
+| password_encryptIOn_type          | 0                                |
+| comm_tcp_mode                     | on                               |
+| comm_quota_size                   | 1024kB                           |
+| max_process_memory                | 700GB                            |
+| bulk_write_ring_size              | 2GB                              |
+| checkpoint_segments               | 1024                             |
+| incremental_checkpoint_timeout    | 60s                              |
+| archive_dest                      | /log/archive                     |
+| enable_slot_log                   | off                              |
+| data_replicate_buffer_size        | 128MB                            |
+| walsender_max_send_size           | 8MB                              |
+| enable_kill_query                 | off                              |
+| connectIOn_alARM_rate             | 0.9                              |
+| alARM_report_interval             | 10                               |
+| alARM_component                   | /opt/huawei/snas/bin/snas_cm_cmd |
+| lockwait_timeout                  | 1200s                            |
+| pgxc_node_name                    | xxx                              |
+| audit_directory                   | 安装工具指定                     |
+| explain_perf_mode                 | pretty                           |
+| job_queue_processes               | 10                               |
+| default_storage_nodegroup         | installatIOn                     |
+| expected_computing_nodegroup      | query                            |
+| replicatIOn_type                  | 1                                |
+| recovery_max_workers              | 4                                |
+| available_zone                    | AZ1                              |
+| allow_concurrent_tuple_update     | TRUE                             |
+| audit_enabled                     | off                              |
+| cstore_buffers                    | 16MB                             |
+| enable_alARM                      | off                              |
+| enable_codegen                    | FALSE                            |
+| enable_data_replicate             | off                              |
+| max_file_per_process              | 10000                            |
+| use_workload_manager              | off                              |
+| xloginsert_locks                  | 48                               |
+| update_lockwait_timeout           | 20min                            |
+| enable_save_datachanged_timestamp | FALSE                            |
+| enable_thread_pool                | off                              |
+| enable_double_write               | on                               |
+| enable_incremental_checkpoint     | on                               |
+| advance_xlog_file_num             | 10                               |
+| enable_instr_track_wait           | off                              |
+| enable_instr_rt_percentile        | off                              |
+| track_sql_count                   | off                              |
+| enable_instr_cpu_timer            | off                              |
+| plog_merge_age                    | 0                                |
+| sessIOn_timeout                   | 0                                |
+| enable_instance_metric_persistent | off                              |
+| enable_logical_IO_statistics      | off                              |
+| enable_user_metric_persistent     | off                              |
+| enable_xlog_prune                 | off                              |
+| enable_resource_track             | off                              |
+| instr_unique_sql_count            | 0                                |
+| enable_beta_opfusIOn              | on                               |
+| enable_bete_netsloop_fusIOn       | on                               |
+| remote_read_mode                  | non_authenticatIOn               |
+| enable_page_lsn_check             | off                              |
+| pagewriter_sleep                  | 2s                               |
+| enable_opfusIOn                   | on                               |
+| max_redo_log_size                 | 100GB                            |
+| pagewrite_thread_num              | 1                                |
+| bgwrite_thread_num                | 1                                |
+| dirty_page_percent_max            | 1                                |
+| candidate_buf_percent_target      | 01                               |
+
+<br/>
+
+## 测试项及结论
+
+### 测试结果汇总
+
+| 测试项   | 数据量 | 并发数 | CPU平均使用率 | IOPS  | IO延时  | WAL数量 | tpmC     | 测试时长 |
+| -------- | ------ | ------ | ---------- | ----- | ------- | ------- | -------- | -------- |
+| 单节点   | 100G   | 500    | 29.39%        | 6.50K | 1.94.ms | 3974    | 520896.3 | 10分钟   |
+| 一主一备 | 100G   | 500    | 30.4%         | 5.31K | 453.2us | 3944    | 519993.5 | 10分钟   |
+| 一主两备 | 100G   | 500    | 26.35%        | 7.66K | 531.9us | 3535    | 480842.2 | 10分钟   |
+
+<br/>
+
+### 单节点
+
+- tpmC
+
+    ![单节点tpmC](https://cdn-mogdb.enmotech.com/docs-media/mogdb/about-mogdb/mogdb-on-x86-1.png)
+
+- 系统数据
+
+    ![单节点系统数据](https://cdn-mogdb.enmotech.com/docs-media/mogdb/about-mogdb/mogdb-on-x86-2.png)
+
+<br/>
+
+### 一主一备
+
+- tpmC
+
+    ![一主一备tpmC](https://cdn-mogdb.enmotech.com/docs-media/mogdb/about-mogdb/mogdb-on-x86-3.png)
+
+- 系统数据
+
+    ![一主一备系统数据](https://cdn-mogdb.enmotech.com/docs-media/mogdb/about-mogdb/mogdb-on-x86-4.png)
+
+<br/>
+
+### 一主两备
+
+- tpmC
+
+    ![一主两备tpmC](https://cdn-mogdb.enmotech.com/docs-media/mogdb/about-mogdb/mogdb-on-x86-5.png)
+
+- 系统数据
+
+    ![一主两备系统数据](https://cdn-mogdb.enmotech.com/docs-media/mogdb/about-mogdb/mogdb-on-x86-6.png)
diff --git a/product/zh/docs-mogdb/v3.0/about-mogdb/usage-limitations.md b/product/zh/docs-mogdb/v3.0/about-mogdb/usage-limitations.md
new file mode 100644
index 0000000000000000000000000000000000000000..00a1f9e8091725d87b6601d3227769c2acb8c6bb
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/about-mogdb/usage-limitations.md
@@ -0,0 +1,27 @@
+---
+title: 使用限制
+summary: 使用限制
+author: Guo Huan
+date: 2021-06-01
+---
+
+# 使用限制
+
+MogDB 具有如下使用限制：
+
+| 指标项                 | 最大值                                    |
+| ---------------------- | ----------------------------------------- |
+| 数据库容量             | 受限于操作系统与硬件                      |
+| 单表大小               | 32TB                                      |
+| 单行数据大小           | 1GB                                       |
+| 每条记录单个字段的大小 | 1GB                                       |
+| 单表记录数             | 281474976710656（2^48）                   |
+| 单表列数               | 250~1600（随字段类型不同会有变化）        |
+| 单表中的索引个数       | 无限制                                    |
+| 复合索引包含列数       | 32                                        |
+| 单表约束个数           | 无限制                                    |
+| 并发连接数             | 10000                                     |
+| 分区表的分区个数       | 32768（范围分区）/64（哈希分区/列表分区） |
+| 分区表的单个分区大小   | 32TB                                      |
+| 分区表的单个分区记录数 | 2^55                                      |
+| SQL文本最大长度        | 1048576字节（1MB）                        |
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/br/1-1-br.md b/product/zh/docs-mogdb/v3.0/administrator-guide/br/1-1-br.md
new file mode 100644
index 0000000000000000000000000000000000000000..4a9853f1e1100717b522303ebff28a0468c8d297
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/br/1-1-br.md
@@ -0,0 +1,95 @@
+---
+title: 概述
+summary: 概述
+author: Liu Xu
+date: 2021-03-04
+---
+
+# 概述
+
+数据备份是保护数据安全的重要手段之一，为了更好的保护数据安全，MogDB数据库支持三种备份恢复类型、多种备份恢复方案，备份和恢复过程中提供数据的可靠性保障机制。
+
+备份与恢复类型可分为逻辑备份与恢复、物理备份与恢复、闪回恢复。
+
+- 逻辑备份与恢复
+
+  通过逻辑导出对数据进行备份，逻辑备份只能基于备份时刻进行数据转储，所以恢复时也只能恢复到备份时保存的数据。对于故障点和备份点之间的数据，逻辑备份无能为力，逻辑备份适合备份那些很少变化的数据，当这些数据因误操作被损坏时，可以通过逻辑备份进行快速恢复。如果通过逻辑备份进行全库恢复，通常需要重建数据库，导入备份数据来完成，对于可用性要求很高的数据库，这种恢复时间太长，通常不被采用。由于逻辑备份具有平台无关性，所以更为常见的是，逻辑备份被作为一个数据迁移及移动的主要手段。
+
+- 物理备份与恢复
+
+  通过物理文件拷贝的方式对数据库进行备份，以磁盘块为基本单位将数据从主机复制到备机。通过备份的数据文件及归档日志等文件，数据库可以进行完全恢复。物理备份速度快，一般被用作对数据进行备份和恢复，用于全量备份的场景。通过合理规划，可以低成本进行备份与恢复。
+
+- 闪回恢复：利用回收站的闪回恢复删除的表。数据库的回收站功能类似于windows系统的回收站，将删除的表信息保存到回收站中。利用MVCC机制闪回恢复到指定时间点或者CSN点。
+
+以下为MogDB支持的三类数据备份恢复方案，备份方案也决定了当异常发生时该如何恢复。
+
+**表 1** 三种备份恢复类型对比
+
+<table>
+    <tr>
+        <th>备份类型</th>
+        <th>应用场景</th>
+        <th>支持的介质</th>
+        <th>工具名称</th>
+        <th>恢复时间</th>
+        <th>优缺点</th>
+    </tr>
+    <td rowspan="2">逻辑备份与恢复</td>
+    <td rowspan="2">适合于数据量小的场景。<br/>可以备份单表和多表，单database和所有database。备份后的数据需要使用gsql或者gs_restore工具恢复。数据量大时，恢复需要较长时间。</td>
+    <td rowspan="6">磁盘<br/>SSD</td>
+    <td>gs_dump</td>
+    <td>纯文本格式数据恢复时间长。归档格式数据恢复时间中等。</td>
+    <td>导出数据库相关信息的工具，用户可以自定义导出一个数据库或其中的对象（模式、表、视图等）。支持导出的数据库可以是默认数据库postgres，也可以是自定义数据库。导出的格式可选择纯文本格式或者归档格式。纯文本格式的数据只能通过gsql进行恢复，恢复时间较长。归档格式的数据只能通过gs_restore进行恢复，恢复时间较纯文本格式短。</td>
+    <tr>
+        <td>gs_dumpall</td>
+        <td>数据恢复时间长</td>
+        <td>导出所有数据库相关信息工具，它可以导出MogDB数据库的所有数据，包括默认数据库postgres的数据、自定义数据库的数据、以及MogDB所有数据库公共的全局对象。只能导出纯文本格式的数据，导出的数据只能通过gsql进行恢复，恢复时间较长。</td>
+    </tr>
+    <tr>
+        <td rowspan="3">物理备份与恢复</td>
+        <td rowspan="3">适用于数据量大的场景，主要用于全量数据备份恢复，也可对整个数据库中的WAL归档日志和运行日志进行备份。</td>
+        <td>gs_backup</td>
+        <td>数据量小数据恢复时间快</td>
+        <td>导出数据库相关信息的OM工具，可以导出数据库参数文件和二进制文件。帮助MogDB备份、恢复重要数据、显示帮助信息和版本号信息。在进行备份时，可以选择备份内容的类型，在进行还原时，需要保证各节点备份目录中存在备份文件。在集群恢复时，通过静态配置文件中的集群信息进行恢复。只恢复参数文件恢复时间较短。</td>
+    </tr>
+    <tr>
+        <td>gs_basebackup</td>
+        <td>恢复时可以直接拷贝替换原有的文件， 或者直接在备份的库上启动数据库，恢复时间快。</td>
+        <td>对服务器数据库文件的二进制进行全量拷贝，只能对数据库某一个时间点的时间作备份。结合PITR恢复，可恢复全量备份时间点后的某一时间点。</td>
+    </tr>
+    <tr>
+        <td>gs_probackup</td>
+        <td>恢复时可以直接恢复到某个备份点，在备份的库上启动数据库，恢复时间快。</td>
+        <td>gs_probackup是一个用于管理MogDB数据库备份和恢复的工具。它对MogDB实例进行定期备份。可用于备份单机数据库或者集群主节点数据库，为物理备份。 可备份外部目录的内容，如脚本文件、配置文件、日志文件、dump文件等。 支持增量备份、定期备份和远程备份。增量备份时间相对于全量备份时间比较短，只需要备份修改的文件。当前默认备份是数据目录，如果表空间不在数据目录，需要手动指定备份的表空间目录进行备份。当前只支持在主机上执行备份。</td>
+    </tr>
+    <tr>
+        <td>闪回恢复</td>
+        <td>适用于：<br/>1）误删除表的场景；<br/>2）需要将表中的数据恢复到指定时间点或者CSN。</td>
+        <td>无</td>
+        <td>可以将表的状态恢复到指定时间点或者是表结构删除前的状态，恢复时间快。</td>
+        <td>闪回技术能够有选择性的高效撤销一个已提交事务的影响，从人为错误中恢复。在采用闪回技术之前，只能通过备份恢复、PITR等手段找回已提交的数据库修改，恢复时长需要数分钟甚至数小时。采用闪回技术后，恢复已提交的数据库修改前的数据，只需要秒级，而且恢复时间和数据库大小无关。<br/>闪回支持两种恢复模式：<br/>- 基于MVCC多版本的数据恢复：适用于误删除、误更新、误插入数据的查询和恢复，用户通过配置旧版本保留时间，并执行相应的查询或恢复命令，查询或恢复到指定的时间点或CSN点。<br/>- 基于类似windows系统回收站的恢复：适用于误DROP、误TRUNCATE的表的恢复。用户通过配置回收站开关，并执行相应的恢复命令，可以将误DROP、误TRUNCATE的表找回。</td>
+    </tr>
+</table>
+
+当需要进行备份恢复操作时，主要从以下四个方面考虑数据备份方案。
+
+- 备份对业务的影响在可接受范围。
+
+- 数据库恢复效率。
+
+    为尽量减小数据库故障的影响，要使恢复时间减到最少，从而使恢复的效率达到最高。
+
+- 数据可恢复程度。
+
+    当数据库失效后，要尽量减少数据损失。
+
+- 数据库恢复成本。
+
+    在现网选择备份策略时参考的因素比较多，如备份对象、数据大小、网络配置等，表2列出了可用的备份策略和每个备份策略的适用场景。
+
+    **表 2** 备份策略典型场景
+
+    |  **备份策略**  |          **关键性能因素**          |         **典型数据量**         | **性能规**                |
+    | :------------: | :-------------------------: | :----------------------------: | :--------------------------------- |
+    | 数据库实例备份 |     - 数据大小<br/>- 网络配置      | 数据: PB级<br/>对象: 约100万个 | 备份: 每个主机80 Mbit/s（NBU/EISOO+磁盘）约90%磁盘I/O速率（SSD/HDD）                |
+    |     表备份     | - 表所在模式<br/>- 网络配置（NBU） |         数据: 10 TB级          | 备份: 基于查询性能速度+I/O速度<br/>说明:<br/>多表备份时，备份耗时计算方式: <br/>`总时间 = 表数量 x 起步时间 + 数据总量 /  数据备份速度`<br/>其中: <br/>- 磁盘起步间为5s左右，NBU起步时间比DISK长（取决于NBU部署方案）。<br/>- 数据备份速度为单节点50MB/s左右（基于1GB大小的表，物理机备份到本地磁盘得出此速率）。<br/>表越小，备份性能更低。 |
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/br/1-2-br.md b/product/zh/docs-mogdb/v3.0/administrator-guide/br/1-2-br.md
new file mode 100644
index 0000000000000000000000000000000000000000..88992a67dca5901743bffee0a7203c1cb6ab063b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/br/1-2-br.md
@@ -0,0 +1,941 @@
+---
+title: 物理备份恢复
+summary: 物理备份恢复
+author: Liu Xu
+date: 2021-03-04
+---
+
+# 物理备份恢复
+
+<br/>
+
+## gs_basebackup
+
+### 背景信息
+
+MogDB部署成功后，在数据库运行的过程中，会遇到各种问题及异常状态。MogDB提供了gs_basebackup工具做基础的物理备份。gs_basebackup的实现目标是对服务器数据库文件的二进制进行拷贝，其实现原理使用了复制协议。远程执行gs_basebackup时，需要使用系统管理员账户。gs_basebackup当前支持热备份模式和压缩格式备份。
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+
+- gs_basebackup仅支持主机和备机的全量备份，不支持增量。
+- gs_basebackup当前支持热备份模式和压缩格式备份模式。
+- gs_basebackup在备份包含绝对路径的表空间时，如果在同一台机器上进行备份，可以通过tablespace-mapping重定向表空间路径，或使用归档模式进行备份。
+- 若打开增量检测点功能且打开双写，gs_basebackup也会备份双写文件。
+- 若pg_xlog目录为软链接，备份时将不会建立软链接，会直接将数据备份到目的路径的pg_xlog目录下。
+- 备份过程中收回用户备份权限，可能导致备份失败，或者备份数据不可用。
+- 如果因为网络临时故障等原因导致Server端无应答，gs_basebackup将在最长等待120秒后退出。
+
+<br/>
+
+### 前提条件
+
+- 可以正常连接MogDB数据库。
+- 备份过程中用户权限没有被回收。
+- pg_hba.conf中需要配置允许复制链接，且该连接必须由一个系统管理员建立。
+- 如果xlog传输模式为stream模式，需要配置max_wal_senders的数量，至少有一个可用。
+- 如果xlog传输模式为fetch模式，有必要把wal_keep_segments参数设置得足够高，这样在备份末尾之前日志不会被移除。
+- 在进行还原时，需要保证各节点备份目录中存在备份文件，若备份文件丢失，则需要从其他节点进行拷贝。
+
+<br/>
+
+### 语法
+
+- 显示帮助信息
+
+    ```bash
+    gs_basebackup -? | --help
+    ```
+
+- 显示版本号信息
+
+    ```bash
+    gs_basebackup -V | --version
+    ```
+
+<br/>
+
+### 参数说明
+
+gs_basebackup参数可以分为如下几类:
+
+- -D directory
+
+  备份文件输出的目录，必选项。
+
+- 常用参数:
+
+  - -c，--checkpoint=fast|spread
+
+    设置检查点模式为fast或者spread（默认）。
+
+  - -l，--label=LABEL
+
+    为备份设置标签。
+
+  - -P，--progress
+
+    启用进展报告。
+
+  - -v， --verbose
+
+    启用冗长模式。
+
+  - -V， --version
+
+      打印版本后退出。
+
+  - -?，--help
+
+    显示gs_basebackup命令行参数。
+
+  - -T，--tablespace-mapping=olddir=newdir
+
+    在备份期间将目录olddir中的表空间重定位到newdir中。为使之有效，olddir必须正好匹配表空间所在的路径（但如果备份中没有包含olddir中的表空间也不是错误）。olddir和newdir必须是绝对路径。如果一个路径凑巧包含了一个=符号，可用反斜线对它转义。对于多个表空间可以多次使用这个选项。
+
+  - -F，--format=plain|tar
+
+    设置输出格式为plain（默认）或者tar。没有设置该参数的情况下，默认-–format=plain。plain格式把输出写成平面文件，使用和当前数据目录和表空间相同的布局。当集簇没有额外表空间时，整个数据库将被放在目标目录中。如果集簇包含额外的表空间，主数据目录将被放置在目标目录中，但是所有其他表空间将被放在它们位于服务器上的相同的绝对路径中。tar模式将输出写成目标目录中的tar文件。主数据目录将被写入到一个名为base.tar的文件中，并且其他表空间将被以其OID命名。生成的tar包，需要用gs_tar命令解压。
+
+  - -X， --xlog-method=fetch|stream
+
+    设置xlog传输方式。没有设置该参数的情况下，默认–-xlog-method=stream。在备份中包括所需的预写式日志文件（WAL文件）。这包括所有在备份期间产生的预写式日志。fetch方式在备份末尾收集预写式日志文件。因此，有必要把wal_keep_segments参数设置得足够高，这样在备份末尾之前日志不会被移除。如果在要传输日志时它已经被轮转，备份将失败并且是不可用的。stream方式在备份被创建时流传送预写式日志。这将开启一个到服务器的第二连接并且在运行备份时并行开始流传输预写式日志。因此，它将使用最多两个由max_wal_senders参数配置的连接。只要客户端能保持接收预写式日志，使用这种模式不需要在主控机上保存额外的预写式日志。
+
+  - -x， --xlog
+
+    使用这个选项等效于和方法fetch一起使用-X。
+
+  - -Z, --compress=level
+
+    启用对tar文件输出的gzip压缩，并且制定压缩级别（0到9，0是不压缩，9是最佳压缩）。只有使用tar格式时压缩才可用，并且会在所有tar文件名后面自动加上后缀.gz。
+
+  - -z
+
+    启用对 tar 文件输出的 gzip 压缩，使用默认的压缩级别。只有使用 tar 格式时压缩才可用，并且会在所有tar文件名后面自动加上后缀.gz。
+
+  - -t，--rw-timeout
+
+    设置备份期间checkpoint的时间限制，默认限制时间为120s。当数据库全量checkpoint耗时较长时，可以适当增大rw-timeout限制时间。
+
+- 连接参数
+
+  - -h, --host=HOSTNAME
+
+    指定正在运行服务器的主机名或者Unix域套接字的路径。
+
+  - -p, --port=PORT
+
+    指定数据库服务器的端口号。
+
+    可以通过port参数修改默认端口号。
+
+  - -U，--username=USERNAME
+
+    指定连接数据库的用户。
+
+  - -s, --status-interval=INTERVAL
+
+    发送到服务器的状态包的时间（以秒为单位）。
+
+  - -w, --no-password
+
+    不出现输入密码提示。
+
+  - -W, --password
+
+    当使用-U参数连接本地数据库或者连接远端数据库时，可通过指定该选项出现输入密码提示。
+
+<br/>
+
+### 示例
+
+```bash
+gs_basebackup -D /home/test/trunk/install/data/backup -h 127.0.0.1 -p 21233
+INFO:  The starting position of the xlog copy of the full build is: 0/1B800000. The slot minimum LSN is: 0/1B800000.
+```
+
+<br/>
+
+### 从备份文件恢复数据
+
+当数据库发生故障时需要从备份文件进行恢复。因为gs_basebackup是对数据库按二进制进行备份，因此恢复时可以直接拷贝替换原有的文件，或者直接在备份的库上启动数据库。
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+
+- 若当前数据库实例正在运行，直接从备份文件启动数据库可能会存在端口冲突，这时需要修改配置文件的port参数，或者在启动数据库时指定一下端口。
+- 若当前备份文件为主备数据库，可能需要修改一下主备之间的复制连接。即配置文件postgresql.conf中的replconninfo1，replconninfo2等。
+- 若配置文件postgresql.conf的参数data_directory打开且有配置，当使用备份目录启动数据库时候，data_directory和备份目录不同会导致启动失败。可以修改data_directory的值为新的数据目录，或者注释掉该参数。
+
+若要在原库的地方恢复数据库，参考步骤如下:
+
+1. 停止数据库服务器，具体操作请参见[启停MogDB](0-starting-and-stopping-mogdb)。
+2. 将原数据库和所有表空间复制到另外一个位置，以备后面需要。
+3. 清理原库中的所有或部分文件。
+4. 使用数据库系统用户权限从备份中还原需要的数据库文件。
+5. 若数据库中存在链接文件，需要修改使其链接到正确的文件。
+6. 重启数据库服务器，并检查数据库内容，确保数据库已经恢复到所需的状态。
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+
+- 暂不支持备份文件增量恢复。
+- 恢复后需要检查数据库中的链接文件是否链接到正确的文件。
+
+## PITR恢复
+
+### 背景信息
+
+当数据库崩溃或希望回退到数据库之前的某一状态时，MogDB的即时恢复功能（Point-In-Time Recovery，简称PITR）可以支持恢复到备份归档数据之后的任意时间点。
+
+ **说明:**
+
+- PITR仅支持恢复到物理备份数据之后的某一时间点。
+- 仅主节点可以进行PITR恢复，备机需要进行全量build达成与主机数据同步。
+
+<br/>
+
+### 前提条件
+
+- 基于经过物理备份的全量数据文件。
+- 基于已归档的WAL日志文件。
+
+<br/>
+
+### PITR恢复流程
+
+1. 将物理备份的文件替换目标数据库目录。
+2. 删除数据库目录下pg_xlog/中的所有文件。
+3. 将归档的WAL日志文件复制到pg_xlog文件中（此步骤可以省略，通过配置recovery.conf恢复命令文件中的restore_command项替代）。
+4. 在数据库目录下创建恢复命令文件recovery.conf，指定数据库恢复的程度。
+5. 启动数据库。
+6. 连接数据库，查看是否恢复到希望预期的状态。
+7. 若已经恢复到预期状态，通过pg_xlog_replay_resume()指令使主节点对外提供服务。
+
+<br/>
+
+### recovery.conf文件配置
+
+**归档恢复配置**
+
+- restore_command = string
+
+    这个SHELL命令是获取WAL文件系列中已归档的WAL文件。字符串中的任何一个%f是用归档检索中的文件名替换，并且%p是用服务器上的复制目的地的路径名替换。任意一个%r是用包含最新可用重启点的文件名替换。
+
+    示例:
+
+    ```bash
+    restore_command = 'cp /mnt/server/archivedir/%f %p'
+    ```
+
+- archive_cleanup_command = string
+
+    这个选项参数声明一个shell命令。在每次重启时会执行这个shell命令。archive_cleanup_command为清理备库不需要的归档WAL文件提供一个机制。任何一个%r由包含最新可用重启点的文件名代替。这是最早的文件，因此必须保留以允许恢复能够重新启动，因此所有早于%r的文件可以安全的移除。
+
+    示例:
+
+    ```bash
+    archive_cleanup_command = 'pg_archivecleanup /mnt/server/archivedir %r'
+    ```
+
+    需要注意的是，如果多个备服务器从相同的归档路径恢复时，需要确保在任何一个备服务器在需要之前，不能删除WAL文件。
+
+- recovery_end_command = string
+
+    这个参数是可选的，用于声明一个只在恢复完成时执行的SHELL命令。recovery_end_command是为以后的复制或恢复提供一个清理机制。
+
+**恢复目标设置**
+
+- recovery_target_name = string
+
+    此参数声明命名还原到一个使用pg_create_restore_point()创建的还原点。
+
+    示例:
+
+    ```bash
+    recovery_target_name = 'restore_point_1'
+    ```
+
+- recovery_target_time = timestamp
+
+    此参数声明命名还原到一个指定时间戳。
+
+    示例:
+
+    ```bash
+    recovery_target_time = '2020-01-01 12:00:00'
+    ```
+
+- recovery_target_xid = string
+
+    这个参数声明还原到一个事务ID。
+
+    示例:
+
+    ```bash
+    recovery_target_xid = '3000'
+    ```
+
+- recovery_target_lsn = string
+
+    这个参数声明还原到日志的指定LSN点。
+
+    示例:
+
+    ```bash
+    recovery_target_lsn = '0/0FFFFFF'
+    ```
+
+- recovery_target_inclusive = boolean
+
+    声明是否在指定恢复目标（true）之后停止，或在（false）之前停止。改声明仅支持恢复目标为recovery_target_time，recovery_target_xid和recovery_target_lsn的配置。
+
+    示例:
+
+    ```bash
+    recovery_target_inclusive = true
+    ```
+
+说明:
+
+- recovery_target_name，recovery_target_time，recovery_target_xid，recovery_target_lsn这四个配置项仅同时支持一项。
+- 如果不配置任何恢复目标，或配置目标不存在，则默认恢复到最新的WAL日志点。
+
+<br/>
+
+## gs_probackup
+
+### 背景信息
+
+gs_probackup是一个用于管理MogDB数据库备份和恢复的工具。它对MogDB实例进行定期备份，以便在数据库出现故障时能够恢复服务器。
+
+- 可用于备份单机数据库，也可对主机或者主节点数据库备机进行备份，为物理备份。
+- 可备份外部目录的内容，如脚本文件、配置文件、日志文件、dump文件等。
+- 支持增量备份、定期备份和远程备份。
+- 可设置备份的留存策略。
+
+### 前提条件
+
+- 可以正常连接MogDB数据库。
+- 若要使用PTRACK增量备份，需在postgresql.conf中手动添加参数“enable_cbm_tracking = on”。
+- 为了防止xlog在传输结束前被清理，请适当调高postgresql.conf文件中wal_keep_segments的值。
+
+### 限制说明
+
+- 备份必须由运行数据库服务器的用户执行。
+- 备份和恢复的数据库服务器的主版本号必须相同。
+- 如果要通过ssh在远程模式下备份数据库，需要在本地和远程主机安装相同主版本的数据库，并通过ssh-copy-id remote_user@remote_host命令设置本地主机备份用户和远程主机数据库用户的无密码ssh连接。
+- 远程模式下只能执行add-instance、backup、restore子命令。
+- 使用restore子命令前，应先停止mogdb进程。
+- 当存在用户自定义表空间时，备份的时候要加上--external-dirs参数，否则，该表空间不会被备份。
+- 当备份的规模比较大时，为了防止备份过程中timeout发生，请适当调整postgresql.conf文件的参数session_timeout、wal_sender_timeout。并且在备份的命令行参数中适当调整参数--rw-timeout的值。
+- 恢复时，使用-T选项把备份中的外部目录重定向到新目录时，请同时指定参数--external-mapping。
+- 增量备份恢复后，之前创建的逻辑复制槽不可用，需删除重建。
+- 当使用远程备份时，请确保远程机器和备份机器的时钟同步，以防止使用--recovery-target-time恢复的场合,启动MogDB时有可能会失败。
+- 当远程备份有效时(remote-proto=ssh)，请确保-h和--remote-host指定的是同一台机器。当远程备份无效时，如果指定了-h选项，请确保-h指定的是本机地址或本机主机名。
+- 当前暂不支持备份逻辑复制槽。
+
+### 命令说明
+
+- 打印gs_probackup版本。
+
+  ```bash
+  gs_probackup -V|--version
+  gs_probackup version
+  ```
+
+- 显示gs_probackup命令的摘要信息。如果指定了gs_probackup的子命令，则显示可用于此子命令的参数的详细信息。
+
+  ```bash
+  gs_probackup -?|--help
+  gs_probackup help [command]
+  ```
+
+- 初始化备份路径backup-path中的备份目录，该目录将存储已备份的内容。如果备份路径backup-path已存在，则backup-path必须为空目录。
+
+  ```bash
+  gs_probackup init -B backup-path [--help]
+  ```
+
+- 在备份路径backup-path内初始化一个新的备份实例，并生成pg_probackup.conf配置文件，该文件保存了指定数据目录pgdata-path的gs_probackup设置。
+
+  ```bash
+  gs_probackup add-instance -B backup-path -D pgdata-path --instance=instance_name
+  [-E external-directories-paths]
+  [remote_options]
+  [--help]
+  ```
+
+- 在备份路径backup-path内删除指定实例相关的备份内容。
+
+  ```bash
+  gs_probackup del-instance -B backup-path --instance=instance_name
+  [--help]
+  ```
+
+- 将指定的连接、压缩、日志等相关设置添加到pg_probackup.conf配置文件中，或修改已设置的值。不推荐手动编辑pg_probackup.conf配置文件。
+
+  ```bash
+  gs_probackup set-config -B backup-path --instance=instance_name
+  [-D pgdata-path] [-E external-directories-paths] [--archive-timeout=timeout]
+  [--retention-redundancy=retention-redundancy] [--retention-window=retention-window] [--wal-depth=wal-depth]
+  [--compress-algorithm=compress-algorithm] [--compress-level=compress-level]
+  [-d dbname] [-h hostname] [-p port] [-U username]
+  [logging_options] [remote_options]
+  [--help]
+  ```
+
+- 将备份相关设置添加到backup.control配置文件中，或修改已设置的值。
+
+  ```bash
+  gs_probackup set-backup -B backup-path --instance=instance_name -i backup-id
+  [--note=text] [pinning_options]
+  [--help]
+  ```
+
+- 显示位于备份目录中的pg_probackup.conf配置文件的内容。可以通过指定--format=json选项，以json格式显示。默认情况下，显示为纯文本格式。
+
+  ```bash
+  gs_probackup show-config -B backup-path --instance=instance_name
+  [--format=plain|json]
+  [--help]
+  ```
+
+- 显示备份目录的内容。如果指定了instance_name和backup_id，则显示该备份的详细信息。可以通过指定--format=json选项，以json格式显示。默认情况下，备份目录的内容显示为纯文本格式。
+
+  ```bash
+  gs_probackup show -B backup-path
+  [--instance=instance_name [-i backup-id]] [--archive] [--format=plain|json]
+  [--help]
+  ```
+
+- 创建指定实例的备份。
+
+  ```bash
+  gs_probackup backup -B backup-path --instance=instance_name -b backup-mode
+  [-D pgdata-path] [-C] [-S slot-name] [--temp-slot] [--backup-pg-log] [-j threads_num] [--progress]
+  [--no-validate] [--skip-block-validation] [-E external-directories-paths] [--no-sync] [--note=text]
+  [--archive-timeout=timeout] [-t rwtimeout]
+  [logging_options] [retention_options] [compression_options]
+  [connection_options] [remote_options] [pinning_options]
+  [--help]
+  ```
+
+- 从备份目录_backup-path_中的备份副本恢复指定实例。如果指定了恢复目标选项，gs_probackup将查找最近的备份并将其还原到指定的恢复目标。否则，使用最近一次备份。
+
+  ```bash
+  gs_probackup restore -B backup-path --instance=instance_name
+  [-D pgdata-path] [-i backup_id] [-j threads_num] [--progress] [--force] [--no-sync] [--no-validate] [--skip-block-validation]
+  [--external-mapping=OLDDIR=NEWDIR] [-T OLDDIR=NEWDIR] [--skip-external-dirs] [-I incremental_mode]
+  [recovery_options] [remote_options] [logging_options]
+  [--help]
+  ```
+
+- 将指定的增量备份与其父完全备份之间的所有增量备份合并到父完全备份。父完全备份将接收所有合并的数据，而已合并的增量备份将作为冗余被删除。
+
+  ```bash
+  gs_probackup merge -B backup-path --instance=instance_name -i backup_id
+  [-j threads_num] [--progress] [logging_options]
+  [--help]
+  ```
+
+- 删除指定备份，或删除不满足当前保留策略的备份。
+
+  ```bash
+  gs_probackup delete -B backup-path --instance=instance_name
+  [-i backup-id | --delete-expired | --merge-expired | --status=backup_status]
+  [--delete-wal] [-j threads_num] [--progress]
+  [--retention-redundancy=retention-redundancy] [--retention-window=retention-window]
+  [--wal-depth=wal-depth] [--dry-run]
+  [logging_options]
+  [--help]
+  ```
+
+- 验证恢复数据库所需的所有文件是否存在且未损坏。如果未指定instance_name，gs_probackup将验证备份目录中的所有可用备份。如果指定instance_name而不指定任何附加选项，gs_probackup将验证此备份实例的所有可用备份。如果指定了instance_name并且指定backup-id或恢复目标相关选项，gs_probackup将检查是否可以使用这些选项恢复数据库。
+
+  ```bash
+  gs_probackup validate -B backup-path
+  [--instance=instance_name] [-i backup-id]
+  [-j threads_num] [--progress] [--skip-block-validation]
+  [--recovery-target-time=time | --recovery-target-xid=xid | --recovery-target-lsn=lsn | --recovery-target-name=target-name]
+  [--recovery-target-inclusive=boolean]
+  [logging_options]
+  [--help]
+  ```
+
+### 参数说明
+
+**通用参数**
+
+- command
+
+  gs_probackup除version和help以外的子命令：init、add-instance、del-instance、set-config、set-backup、show-config、show、backup、restore、merge、delete、validate。
+
+- -?, --help
+
+  显示gs_probackup命令行参数的帮助信息，然后退出。
+
+  子命令中只能使用-help，不能使用-?。
+
+- -V, --version
+
+  打印gs_probackup版本，然后退出。
+
+- -B backup-path, --backup-path=backup-path
+
+  备份的路径。
+
+  系统环境变量：$BACKUP_PATH
+
+- -D pgdata-path, --pgdata=pgdata-path
+
+  数据目录的路径。
+
+  系统环境变量：$PGDATA
+
+- --instance=instance_name
+
+  实例名。
+
+- -i backup-id, --backup-id=backup-id
+
+  备份的唯一标识。
+
+- --format=format
+
+  指定显示备份信息的格式，支持plain和json格式。
+
+  默认值：plain
+
+- --status=backup_status
+
+  删除指定状态的所有备份，包含以下状态：
+
+  - OK ：备份已完成且有效。
+  - DONE：备份已完成但未经过验证。
+  - RUNNING：备份正在进行中。
+  - MERGING：备份正在合并中。
+  - DELETING：备份正在删除中。
+  - CORRUPT：部分备份文件已损坏。
+  - ERROR：由于意外错误，备份失败。
+  - ORPHAN：由于其父备份之一已损坏或丢失，备份无效。
+  - -j threads_num, --threads=threads_num
+
+  设置备份、还原、合并进程的并行线程数。
+
+- --archive
+
+  显示WAL归档信息。
+
+- --progress
+
+  显示进度。
+
+- --note=text
+
+  给备份添加note。
+
+**备份相关参数**
+
+- -b backup-mode, --backup-mode=backup-mode
+
+  指定备份模式，支持FULL和PTRACK。
+
+  FULL：创建全量备份，全量备份包含所有数据文件。
+
+  PTRACK：创建PTRACK增量备份。
+
+- -C, --smooth-checkpoint
+
+  将检查点在一段时间内展开。默认情况下，gs_probackup会尝试尽快完成检查点。
+
+- -S slot-name, --slot=slot-name
+
+  指定WAL流处理的复制slot。
+
+- --temp-slot
+
+  在备份的实例中为WAL流处理创建一个临时物理复制slot，它确保在备份过程中，所有所需的WAL段仍然是可用的。
+
+  默认的slot名为pg_probackup_slot，可通过选项--slot/-S更改。
+
+- --backup-pg-log
+
+  将日志目录包含到备份中。此目录通常包含日志消息。默认情况下包含日志目录，但不包含日志文件。如果修改了默认的日志路径，需要备份日志文件时可使用-E参数进行备份，使用方法见下文。
+
+- -E external-directories-paths, --external-dirs=external-directories-paths
+
+  将指定的目录包含到备份中。此选项对于备份位于数据目录外部的脚本、sql转储和配置文件很有用。如果要备份多个外部目录，请在Unix上用冒号分隔它们的路径。
+
+  例如：-E /tmp/dir1:/tmp/dir2
+
+- --skip-block-validation
+
+  关闭块级校验，加快备份速度。
+
+- --no-validate
+
+  在完成备份后跳过自动验证。
+
+- --no-sync
+
+  不将备份文件同步到磁盘。
+
+- --archive-timeout=timeout
+
+  以秒为单位设置流式处理的超时时间。
+
+  默认值：300
+
+- -t rwtimeout
+
+  以秒为单位的连接的超时时间。
+
+  默认值：120
+
+**恢复相关参数**
+
+- -I, --incremental-mode=none|checksum|lsn
+
+  若PGDATA中可用的有效页没有修改，则重新使用它们。
+
+  默认值：none
+
+- --external-mapping=OLDDIR=NEWDIR
+
+  在恢复时，将包含在备份中的外部目录从_OLDDIR_重新定位到_NEWDIR_目录。_OLDDIR_和_NEWDIR_都必须是绝对路径。如果路径中包含“=”，则使用反斜杠转义。此选项可为多个目录多次指定。
+
+- -T OLDDIR=NEWDIR, --tablespace-mapping=OLDDIR=NEWDIR
+
+  在恢复时，将表空间从_OLDDIR_重新定位到_NEWDIR_目录。_OLDDIR_和_NEWDIR_必须都是绝对路径。如果路径中包含“=”，则使用反斜杠转义。多个表空间可以多次指定此选项。此选项必须和--external-mapping一起使用。
+
+- --skip-external-dirs
+
+  跳过备份中包含的使用--external-dirs选项指定的外部目录。这些目录的内容将不会被恢复。
+
+- --skip-block-validation
+
+  跳过块级校验，以加快验证速度。在恢复之前的自动验证期间，将仅做文件级别的校验。
+
+- --no-validate
+
+  跳过备份验证。
+
+- --force
+
+  允许忽略备份的无效状态。如果出于某种原因需要从损坏的或无效的备份中恢复数据，可以使用此标志。请谨慎使用。
+
+**恢复目标相关参数(recovery_options)**
+
+> **说明：**
+>
+> 当前不支持配置连续的WAL归档的PITR，因而使用这些参数会有一定限制，具体如下描述。 如果需要使用持续归档的WAL日志进行PITR恢复，请按照下面描述的步骤：
+>
+> 1. 将物理备份的文件替换目标数据库目录。
+> 2. 删除数据库目录下pg_xlog/中的所有文件。
+> 3. 将归档的WAL日志文件复制到pg_xlog文件中（此步骤可以省略，通过配置recovery.conf恢复命令文件中的restore_command项替代）。
+> 4. 在数据库目录下创建恢复命令文件recovery.conf，指定数据库恢复的程度。
+> 5. 启动数据库。
+> 6. 连接数据库，查看是否恢复到希望预期的状态。若已经恢复到预期状态，通过pg_xlog_replay_resume()指令使主节点对外提供服务。
+
+- --recovery-target-lsn=lsn
+
+  指定要恢复到的lsn，当前只能指定备份的stop lsn。
+
+- --recovery-target-name=target-name
+
+  指定要将数据恢复到的已命名的保存点，保存点可以通过查看备份中recovery-name字段得到。
+
+- --recovery-target-time=time
+
+  指定要恢复到的时间，当前只能指定备份中的recovery-time。
+
+- --recovery-target-xid=xid
+
+  指定要恢复到的事务ID，当前只能指定备份中的recovery-xid。
+
+- --recovery-target-inclusive=boolean
+
+  当该参数指定为true时，恢复目标将包括指定的内容。
+
+  当该参数指定为false时，恢复目标将不包括指定的内容。
+
+  该参数必须和--recovery-target-name、--recovery-target-time、--recovery-target-lsn或--recovery-target-xid一起使用。
+
+**留存相关参数(retention_options)**
+
+> **说明：**
+>
+> 可以和backup和delete命令一起使用这些参数。
+
+- --retention-redundancy=retention-redundancy
+
+  指定在数据目录中留存的完整备份数。必须为正整数。0表示禁用此设置。
+
+  默认值：0
+
+- --retention-window=retention-window
+
+  指定留存的天数。必须为正整数。0表示禁用此设置。
+
+  默认值：0
+
+- --wal-depth=wal-depth
+
+  每个时间轴上必须留存的执行PITR能力的最新有效备份数。必须为正整数。0表示禁用此设置。
+
+  默认值：0
+
+- --delete-wal
+
+  从任何现有的备份中删除不需要的WAL文件。
+
+- --delete-expired
+
+  删除不符合pg_probackup.conf配置文件中定义的留存策略的备份。
+
+- --merge-expired
+
+  将满足留存策略要求的最旧的增量备份与其已过期的父备份合并。
+
+- --dry-run
+
+  显示所有可用备份的当前状态，不删除或合并过期备份。
+
+**固定备份相关参数(pinning_options)**
+
+> **说明：**
+>
+> 如果要将某些备份从已建立的留存策略中排除，可以和backup和set-backup命令一起使用这些参数。
+
+- --ttl=interval
+
+  指定从恢复时间开始计算，备份要固定的时间量。必须为正整数。0表示取消备份固定。
+
+  支持的单位：ms, s, min, h, d（默认为s）。
+
+  例如：--ttl=30d。
+
+- --expire-time=time
+
+  指定备份固定失效的时间戳。必须是ISO-8601标准的时间戳。
+
+  例如：--expire-time='2020-01-01 00:00:00+03'
+
+**日志相关参数(logging_options)**
+
+日志级别：verbose、log、info、warning、error和off。
+
+- --log-level-console=log-level-console
+
+  设置要发送到控制台的日志级别。每个级别都包含其后的所有级别。级别越高，发送的消息越少。指定off级别表示禁用控制台日志记录。
+
+  默认值：info
+
+- --log-level-file=log-level-file
+
+  设置要发送到日志文件的日志级别。每个级别都包含其后的所有级别。级别越高，发送的消息越少。指定off级别表示禁用日志文件记录。
+
+  默认值：off
+
+- --log-filename=log-filename
+
+  指定要创建的日志文件的文件名。文件名可以使用strftime模式，因此可以使用%-escapes指定随时间变化的文件名。
+
+  例如，如果指定了“pg_probackup-%u.log”模式，则pg_probackup为每周的每一天生成单独的日志文件，其中%u替换为相应的十进制数字，即pg_probackup-1.log表示星期一；pg_probackup-2.log表示星期二，以此类推。
+
+  如果指定了--log-level-file参数启用日志文件记录，则该参数有效。
+
+  默认值："pg_probackup.log"
+
+- --error-log-filename=error-log-filename
+
+  指定仅用于error日志的日志文件名。指定方式与--log-filename参数相同。
+
+  此参数用于故障排除和监视。
+
+- --log-directory=log-directory
+
+  指定创建日志文件的目录。必须是绝对路径。此目录会在写入第一条日志时创建。
+
+  默认值：$BACKUP_PATH/log
+
+- --log-rotation-size=log-rotation-size
+
+  指定单个日志文件的最大大小。如果达到此值，则启动gs_probackup命令后，日志文件将循环，但help和version命令除外。0表示禁用基于文件大小的循环。
+
+  支持的单位：KB、MB、GB、TB（默认为KB）。
+
+  默认值：0
+
+- --log-rotation-age=log-rotation-age
+
+  单个日志文件的最大生命周期。如果达到此值，则启动gs_probackup命令后，日志文件将循环，但help和version命令除外。$BACKUP_PATH/log/log_rotation目录下保存最后一次创建日志文件的时间。0表示禁用基于时间的循环。
+
+  支持的单位：ms, s, min, h, d（默认为min）。
+
+  默认值：0
+
+**连接相关参数(connection_options)**
+
+> **说明：**
+>
+> 可以和backup命令一起使用这些参数。
+
+- -d dbname, --pgdatabase=dbname
+
+  指定要连接的数据库名称。该连接仅用于管理备份进程，因此您可以连接到任何现有的数据库。如果命令行、PGDATABASE环境变量或pg_probackup.conf配置文件中没有指定此参数，则gs_probackup会尝试从PGUSER环境变量中获取该值。如果未设置PGUSER变量，则从当前用户名获取。
+
+  系统环境变量：$PGDATABASE
+
+- -h hostname, --pghost=hostname
+
+  指定运行服务器的系统的主机名。如果该值以斜杠开头，则被用作到Unix域套接字的路径。
+
+  系统环境变量：$PGHOST
+
+  默认值：local socket
+
+- -p port, --pgport=port
+
+  指定服务器正在侦听连接的TCP端口或本地Unix域套接字文件扩展名。
+
+  系统环境变量：$PGPORT
+
+  默认值：5432
+
+- -U username, --pguser=username
+
+  指定所连接主机的用户名。
+
+  系统环境变量：$PGUSER
+
+- -w, --no-password
+
+  不出现输入密码提示。如果主机要求密码认证并且密码没有通过其它形式给出，则连接尝试将会失败。 该选项在批量工作和不存在用户输入密码的脚本中很有帮助。
+
+- -W password, --password=password
+
+  指定用户连接的密码。如果主机的认证策略是trust，则不会对系统管理员进行密码验证，即无需输入-W选项；如果没有-W选项，并且不是系统管理员，则会提示用户输入密码。
+
+**压缩相关参数(compression_options)**
+
+> **说明：**
+>
+> 可以和backup命令一起使用这些参数。
+
+- --compress-algorithm=compress-algorithm
+
+  指定用于压缩数据文件的算法。
+
+  取值包括zlib、pglz和none。如果设置为zlib或pglz，此选项将启用压缩。默认情况下，压缩功能处于关闭状态。
+
+  默认值：none
+
+- --compress-level=compress-level
+
+  指定压缩级别。取值范围: 0~9
+
+  - 0表示无压缩。
+  - 1表示压缩比最小，处理速度最快。
+  - 9表示压缩比最大，处理速度最慢。
+  - 可与--compress-algorithm选项一起使用。
+
+  默认值：1
+
+- --compress
+
+  以--compress-algorithm=zlib和--compress-level=1进行压缩。
+
+**远程模式相关参数(remote_options)**
+
+> **说明：**
+>
+> 通过SSH远程运行gs_probackup操作的相关参数。可以和add-instance、set-config、backup、restore命令一起使用这些参数。
+
+- --remote-proto=protocol
+
+  指定用于远程操作的协议。目前只支持SSH协议。取值包括：
+
+  ssh：通过SSH启用远程备份模式。这是默认值。
+
+  none：显式禁用远程模式。
+
+  如果指定了--remote-host参数，可以省略此参数。
+
+- --remote-host=destination
+
+  指定要连接的远程主机的IP地址或主机名。
+
+- --remote-port=port
+
+  指定要连接的远程主机的端口号。
+
+  默认值：22
+
+- --remote-user=username
+
+  指定SSH连接的远程主机用户。如果省略此参数，则使用当前发起SSH连接的用户。
+
+  默认值：当前用户
+
+- --remote-path=path
+
+  指定gs_probackup在远程系统的安装目录。
+
+  默认值：当前路径
+
+- --remote-libpath=libpath
+
+   指定gs_probackup在远程系统安装的lib库目录。
+
+- --ssh-options=ssh_options
+
+  指定SSH命令行参数的字符串。
+
+  例如：--ssh-options='-c cipher_spec -F configfile'
+
+>**说明：**
+>
+>* 如果因为网络临时故障等原因导致server端无应答，gs_probackup将在等待archive-timeout（默认300秒）后退出。
+>
+>* 如果备机lsn与主机有差别时，数据库会不停地刷以下log信息，此时应重新build备机。
+>
+>  ```
+>  LOG: walsender thread shut down
+>  LOG: walsender thread started
+>  LOG: received wal replication command: IDENTIFY_VERSION
+>  LOG: received wal replication command: IDENTIFY_MODE
+>  LOG: received wal replication command: IDENTIFY_SYSTEM
+>  LOG: received wal replication command: IDENTIFY_CONSISTENCE 0/D0002D8
+>  LOG: remote request lsn/crc: [xxxxx] local max lsn/crc: [xxxxx]
+>  ```
+
+### 备份流程
+
+1. 初始化备份目录。在指定的目录下创建backups/和wal/子目录，分别用于存放备份文件和WAL文件。
+
+   ```bash
+   gs_probackup init -B backup_dir
+   ```
+
+2. 添加一个新的备份实例。gs_probackup可以在同一个备份目录下存放多个数据库实例的备份。
+
+   ```bash
+   gs_probackup add-instance -B backup_dir -D data_dir --instance instance_name
+   ```
+
+3. 创建指定实例的备份。在进行增量备份之前，必须至少创建一次全量备份。
+
+   ```bash
+   gs_probackup backup -B backup_dir --instance instance_name -b backup_mode
+   ```
+
+4. 从指定实例的备份中恢复数据。
+
+   ```bash
+   gs_probackup restore -B backup_dir --instance instance_name -D pgdata-path -i backup_id
+   ```
+
+### 故障处理
+
+| 问题描述                                                     | 原因和解决方案                                               |
+| :----------------------------------------------------------- | :----------------------------------------------------------- |
+| ERROR: query failed: ERROR: canceling statement due to conflict with recovery（错误：查询失败：由于与恢复操作冲突，正在取消语句命令） | 原因：在备机上执行的操作正在访问存储行，主机上更改或者删除了对应的行，并将xlog在备机上重放，迫使备机上操作取消。<br />解决方案：<br />1. 适当增加如下配置参数的值：max_standby_archive_delaymax_standby_streaming_delay<br />2. 增加如下配置：hot_standby_feedback = on |
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/br/1-3-br.md b/product/zh/docs-mogdb/v3.0/administrator-guide/br/1-3-br.md
new file mode 100644
index 0000000000000000000000000000000000000000..bd6d79b55d0cb4e40e3b8079016be1f5f1491a0c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/br/1-3-br.md
@@ -0,0 +1,1464 @@
+---
+title: 逻辑备份恢复
+summary: 逻辑备份恢复
+author: Liu Xu
+date: 2021-03-04
+---
+
+# 逻辑备份恢复
+
+<br/>
+
+## gs_dump
+
+### 背景信息
+
+gs_dump是MogDB用于导出数据库相关信息的工具，用户可以自定义导出一个数据库或其中的对象（模式、表、视图等），回收站对象除外。支持导出的数据库可以是默认数据库mogdb，也可以是自定义数据库。
+
+gs_dump工具由操作系统用户omm执行。
+
+gs_dump工具在进行数据导出时，其他用户可以访问MogDB数据库（读或写）。
+
+gs_dump工具支持导出完整一致的数据。例如，T1时刻启动gs_dump导出A数据库，那么导出数据结果将会是T1时刻A数据库的数据状态，T1时刻之后对A数据库的修改不会被导出。
+
+gs_dump时生成列不会被转储。
+
+gs_dump支持导出兼容v1版本数据库的文本格式文件。
+
+gs_dump支持将数据库信息导出至纯文本格式的SQL脚本文件或其他归档文件中。
+
+- 纯文本格式的SQL脚本文件: 包含将数据库恢复为其保存时的状态所需的SQL语句。通过[gsql](client-tool#gsql)运行该SQL脚本文件，可以恢复数据库。即使在其他主机和其他数据库产品上，只要对SQL脚本文件稍作修改，也可以用来重建数据库。
+- 归档格式文件: 包含将数据库恢复为其保存时的状态所需的数据，可以是tar格式、目录归档格式或自定义归档格式，详见表1。该导出结果必须与[gs_restore](9-gs_restore)配合使用来恢复数据库，gs_restore工具在导入时，系统允许用户选择需要导入的内容，甚至可以在导入之前对等待导入的内容进行排序。
+
+<br/>
+
+### 主要功能
+
+gs_dump可以创建四种不同的导出文件格式，通过“-F”或者“--format=”选项指定，具体如表1所示。
+
+**表 1** 导出文件格式
+
+<table>
+    <tr>
+        <th>格式名称</th>
+        <th>-F的参数值</th>
+        <th>说明</th>
+        <th>建议</th>
+        <th>对应导入工具</th>
+    </tr>
+    <tr>
+        <td>纯文本格式</td>
+        <td>p</td>
+        <td>纯文本脚本文件包含SQL语句和命令。命令可以由gsql命令行终端程序执行，用于重新创建数据库对象并加载表数据。</td>
+        <td>小型数据库，一般推荐纯文本格式。</td>
+        <td>使用gsql工具恢复数据库对象前，可根据需要使用文本编辑器编辑纯文本导出文件。</td>
+    </tr>
+    <tr>
+        <td>自定义归档格式</td>
+        <td>c</td>
+        <td>一种二进制文件。支持从导出文件中恢复所有或所选数据库对象。</td>
+        <td>中型或大型数据库，推荐自定义归档格式。</td>
+        <td rowspan="3">使用gs_restore可以选择要从自定义归档导出文件中导入相应的数据库对象。</td>
+    </tr>
+    <tr>
+        <td>目录归档格式</td>
+        <td>d</td>
+        <td>该格式会创建一个目录，该目录包含两类文件，一类是目录文件，另一类是每个表和blob对象对应的数据文件。</td>
+        <td>-</td>
+    </tr>
+    <tr>
+        <td>tar归档格式</td>
+        <td>t</td>
+        <td>tar归档文件支持从导出文件中恢复所有或所选数据库对象。tar归档格式不支持压缩且对于单独表大小应小于8GB。</td>
+        <td>-</td>
+    </tr>
+</table>
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+
+可以使用gs_dump程序将文件压缩为目录归档或自定义归档导出文件，减少导出文件的大小。生成目录归档或自定义归档导出文件时，默认进行中等级别的压缩。gs_dump程序无法压缩已归档导出文件。
+
+<br/>
+
+### 注意事项
+
+- 禁止修改导出的文件和内容，否则可能无法恢复成功。
+
+- 为了保证数据一致性和完整性，gs_dump会对需要转储的表设置共享锁。如果表在别的事务中设置了共享锁，gs_dump会等待锁释放后锁定表。如果无法在指定时间内锁定某个表，转储会失败。用户可以通过指定--lock-wait-timeout选项，自定义等待锁超时时间。
+
+- 不支持加密导出存储过程和函数。
+
+<br/>
+
+### 语法
+
+```bash
+gs_dump [OPTION]... [DBNAME]
+```
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+
+"DBNAME"前面不需要加短或长选项。"DBNAME"指定要连接的数据库。例如：不需要-d，直接指定"DBNAME"。
+
+```bash
+gs_dump -p port_number  mogdb -f dump1.sql
+```
+
+或者
+
+```
+export PGDATABASE=mogdb
+```
+
+```bash
+gs_dump -p port_number -f dump1.sql
+```
+
+环境变量:  PGDATABASE
+
+<br/>
+
+### 参数说明
+
+#### 通用参数
+
+- -f, --file=FILENAME
+
+    将输出发送至指定文件或目录。如果省略该参数，则使用标准输出。如果输出格式为（-F c/-F d/-F t）时，必须指定-f参数。如果-f的参数值含有目录，要求当前用户对该目录具有读写权限，并且不能指定已有目录。
+
+- -F, --format=c|d|t|p
+
+  选择输出格式。格式如下:
+
+  - p|plain: 输出一个文本SQL脚本文件（默认）。
+
+  - c|custom: 输出一个自定义格式的归档，并且以目录形式输出，作为gs_restore输入信息。该格式是最灵活的输出格式，因为能手动选择，而且能在恢复过程中将归档项重新排序。该格式默认状态下会被压缩。
+
+  - d|directory: 该格式会创建一个目录，该目录包含两类文件，一类是目录文件，另一类是每个表和blob对象对应的数据文件。
+
+  - t|tar: 输出一个tar格式的归档形式，作为gs_restore输入信息。tar格式与目录格式兼容；tar格式归档形式在提取过程中会生成一个有效的目录格式归档形式。但是，tar格式不支持压缩且对于单独表有8GB的大小限制。此外，表数据项的相应排序在恢复过程中不能更改。
+
+    输出一个tar格式的归档形式，也可以作为gsql输入信息。
+
+- -v, --verbose
+
+    指定verbose模式。该选项将导致gs_dump向转储文件输出详细的对象注解和启动/停止次数，向标准错误流输出处理信息。
+
+- -V, --version
+
+    打印gs_dump版本，然后退出。
+
+- -Z, --compress=0-9
+
+    指定使用的压缩比级别。
+
+    取值范围: 0~9
+
+  - 0表示无压缩。
+  - 1表示压缩比最小，处理速度最快。
+  - 9表示压缩比最大，处理速度最慢。
+
+    针对自定义归档格式，该选项指定单个表数据片段的压缩，默认方式是以中等级别进行压缩。tar归档格式和纯文本格式目前不支持压缩。
+
+- --lock-wait-timeout=TIMEOUT
+
+    请勿在转储刚开始时一直等待以获取共享表锁。如果无法在指定时间内锁定某个表，就选择失败。可以以任何符合SET statement_timeout的格式指定超时时间。
+
+- -?, --help
+
+    显示gs_dump命令行参数帮助，然后退出。
+
+#### 转储参数
+
+- -a, --data-only
+
+    只输出数据，不输出模式（数据定义）。转储表数据、大对象和序列值。
+
+- -b, --blobs
+
+    该参数为扩展预留接口，不建议使用。
+
+- -c, --clean
+
+    在将创建数据库对象的指令输出到备份文件之前，先将清理（删除）数据库对象的指令输出到备份文件中。（如果目标数据库中没有任何对象，gs_restore工具可能会输出一些提示性的错误信息）
+
+  该选项只对文本格式有意义。针对归档格式，可以调用gs_restore时指定选项。
+
+- -C, --create
+
+    备份文件以创建数据库和连接到创建的数据库的命令开始。（如果命令脚本是这种方式执行，可以先指定任意数据库用于执行创建数据库的命令，数据不会恢复到指定的数据库中，而是恢复到创建的数据库中。）
+
+    该选项只对文本格式有意义。针对归档格式，可以在调用gs_restore时指定选项。
+
+- -E, --encoding=ENCODING
+
+    以指定的字符集编码创建转储。默认情况下，以数据库编码创建转储。（得到相同结果的另一个办法是将环境变量"PGCLIENTENCODING"设置为所需的转储编码。）
+
+- -n, --schema=SCHEMA
+
+    只转储与模式名称匹配的模式，此选项包括模式本身和所有它包含的对象。如果该选项没有指定，所有在目标数据库中的非系统模式将会被转储。写入多个-n选项来选择多个模式。
+    此外，根据gsql的\\d命令所使用的相同规则，模式参数可被理解成一个pattern，所以多个模式也可以通过在该pattern中写入通配符来选择。使用通配符时，注意给pattern打引号，防止shell扩展通配符。
+
+    ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+
+  - 当-n已指定时，gs_dump不会转储已选模式所附着的任何其他数据库对象。因此，无法保证某个指定模式的转储结果能够自行成功地储存到一个空数据库中。
+  - 当-n指定时，非模式对象不会被转储。
+
+    转储支持多个模式的转储。多次输入-n schemaname转储多个模式。
+
+    例如:
+
+    ```bash
+    gs_dump -h host_name -p port_number mogdb -f backup/bkp_shl2.sql -n sch1 -n sch2
+    ```
+
+  在上面这个例子中，sch1和sch2会被转储。
+
+- -N, --exclude-schema=SCHEMA
+
+    不转储任何与模式pattern匹配的模式。pattern将参照针对-n的相同规则来理解。可以通过输入多次-N，不转储与任何pattern匹配的模式。
+
+    当同时输入-n和-N时，会转储与至少一个-n选项匹配、与-N选项不匹配的模式。如果有-N没有-n，则不转储常规转储中与-N匹配的模式。
+
+    转储过程支持排除多个模式。
+
+    在转储过程中，输入-N exclude schema name排除多个模式。
+
+    例如:
+
+    ```bash
+    gs_dump -h host_name -p port_number mogdb -f backup/bkp_shl2.sql -N sch1 -N sch2
+    ```
+
+    在上面这个例子中，sch1和sch2在转储过程中会被排除。
+
+- -o, --oids
+
+    转储每个表的对象标识符（OIDs），作为表的一部分数据。该选项用于应用以某种方式参照了OID列的情况。如果不是以上这种情况，请勿使用该选项。
+
+- -O, --no-owner
+
+    不输出设置对象的归属这样的命令，以匹配原始数据库。默认情况下，gs_dump会发出ALTER OWNER或SET SESSION AUTHORIZATION语句设置所创建的数据库对象的归属。如果脚本正在运行，该语句不会执行成功，除非是由系统管理员触发（或是拥有脚本中所有对象的同一个用户）。通过指定-O，编写一个任何用户都能存储的脚   本，且该脚本会授予该用户拥有所有对象的权限。
+
+    该选项只对文本格式有意义。针对归档格式，可以在调用gs_restore时指定选项。
+
+- -s, --schema-only <a id="--schema-only"> </a>
+
+    只转储对象定义（模式），而非数据。
+
+- -S, --sysadmin=NAME
+
+    该参数为扩展预留接口，不建议使用。
+
+- -t, --table=TABLE
+
+    指定转储的表（或视图、或序列、或外表）对象列表，可以使用多个-t选项来选择多个表，也可以使用通配符指定多个表对象。
+
+    当使用通配符指定多个表对象时，注意给pattern打引号，防止shell扩展通配符。
+
+    当使用-t时，-n和-N没有任何效应，这是因为由-t选择的表的转储不受那些选项的影响。
+
+    ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+
+  - -t参数选项个数必须小于等于100。
+  - 如果-t参数选项个数大于100，建议使用参数-include-table-file来替换。
+  - 当-t已指定时，gs_dump不会转储已选表所附着的任何其他数据库对象。因此，无法保证某个指定表的转储结果能够自行成功地储存到一个空数据库中。
+  - -t tablename只转储在默认搜索路径中可见的表。-t '*.tablename'转储数据库下所有模式下的tablename表。-t schema.table转储特定模式中的表。
+  - -t tablename不会导出表上的触发器信息。
+
+    例如:
+
+    ```bash
+    gs_dump -h host_name -p port_number mogdb -f backup/bkp_shl2.sql -t schema1.table1 -t schema2.table2
+    ```
+
+    在上面这个例子中，schema1.table1和schema2.table2会被转储。
+
+- --include-table-file=FILENAME
+
+    指定需要dump的表文件。
+
+- -T, --exclude-table=TABLE
+
+    不转储的表（或视图、或序列、或外表）对象列表，可以使用多个-T选项来选择多个表，也可以使用通配符指定多个表对象。
+
+    当同时输入-t和-T时，会转储在-t列表中，而不在-T列表中的表对象。
+
+    例如:
+
+    ```bash
+    gs_dump -h host_name -p port_number mogdb -f backup/bkp_shl2.sql -T table1 -T table2
+    ```
+
+  在上面这个例子中，table1和table2在转储过程中会被排除。
+
+- --exclude-table-file=FILENAME
+
+    指定不需要dump的表文件。
+
+    ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+
+    ```
+    同--include-table-file，其内容格式如下：
+    schema1.table1
+    schema2.table2
+    ......
+    ```
+
+- -x, --no-privileges|-no-acl
+
+    防止转储访问权限（授权/撤销命令）。
+
+- -q, --target
+
+  指定导出兼容其他版本数据库的文本文件，目前支持v1和v5参数。v1参数用于导出v5数据库的数据为兼容v1的文本文件。v5参数用于导出v5数据库的数据为v5格式的文本文件，减少了导入v5时的可能的报错情况。
+
+  在使用v1参数时，建议和--exclude-guc="enable_cluster_resize"，--exclude-function，--exclude-with等选项共用，否则导入到v1时可能报错。
+
+- --exclude-guc
+
+  导出的文本文件中，不包括相关guc参数的set命令，目前只支持enable_cluster_resize。
+
+- --exclude-function
+
+  不导出函数和存储过程。
+
+- --exclude-with
+
+  导出的表定义，末尾不添加WITH(orientation=row，compression=on)这样的描述。
+
+- --binary-upgrade
+
+    该参数为扩展预留接口，不建议使用。
+
+- --binary-upgrade-usermap="USER1=USER2"
+
+    该参数为扩展预留接口，不建议使用。
+
+- --column-inserts|-attribute-inserts
+
+    以INSERT命令带列名（INSERT INTO表（列、…）值…）方式导出数据。这会导致恢复缓慢。但是由于该选项会针对每行生成一个独立分开的命令，所以在重新加载某行时出现的错误只会导致那行丢失，而非整个表内容。
+
+- --disable-dollar-quoting
+
+    该选项将禁止在函数体前使用美元符号$，并强制使用SQL标准字符串语法对其进行引用。
+
+- --disable-triggers
+
+    该参数为扩展预留接口，不建议使用。
+
+- --exclude-table-data=TABLE
+
+    指定不转储任何匹配表pattern的表这方面的数据。依照针对-t的相同规则理解该pattern。
+
+    可多次输入-exclude-table-data来排除匹配任何pattern的表。当用户需要特定表的定义但不需要其中的数据时，这个选项很有帮助。
+
+    排除数据库中所有表的数据，参见[--schema-only](#--schema-only)。
+
+- --inserts
+
+    发出INSERT命令（而非COPY命令）转储数据。这会导致恢复缓慢。
+
+    但是由于该选项会针对每行生成一个独立分开的命令，所以在重新加载某行时出现的错误只会导致那行丢失，而非整个表内容。注意:如果重排列顺序，可能会导致整个恢复失败。列顺序改变时，-column-inserts选项不受影响，虽然会更慢。
+
+- --no-publications
+
+  不转储发布。
+
+- -no-security-labels
+
+    该参数为扩展预留接口，不建议使用。
+
+- --no-subscriptions
+
+  不转储订阅。
+
+- --no-tablespaces
+
+    不输出选择表空间的命令。使用该选项，无论默认表空间是哪个，在恢复过程中所有对象都会被创建。
+
+    该选项只对文本格式有意义。针对归档格式，可以在调用gs_restore时指定选项。
+
+- --no-unlogged-table-data
+
+    该参数为扩展预留接口，不建议使用。
+
+- --non-lock-table
+
+    该参数为扩展预留接口，不建议使用。
+
+- --include-alter-table
+
+    转储表删除列。该选项会记录列的删除。
+
+- --quote-all-identifiers
+
+    强制对所有标识符加引号。为了向后续版本迁移，且其中可能涉及引入额外关键词，在转储相应数据库时该选项会有帮助。
+
+- --section=SECTION
+
+    指定已转储的名称区段（pre-data、data和post-data）。
+
+- --serializable-deferrable
+
+    转储过程中使用可串行化事务，以确保所使用的快照与之后的数据库状态一致；要实现该操作需要在无异常状况的事务流中等待某个点，因为这样才能保证转储成功，避免引起其他事务出现serialization_failure要重新再做。
+
+    但是该选项对于灾难恢复没有益处。对于在原始数据库进行升级的时候，加载一个数据库的拷贝作为报告或其他只读加载共享的转储是有帮助的。没有这个选项，转储会反映一个与任何事务最终提交的序列化执行不一致的状态。
+
+    如果当gs_dump启动时，读写事务仍处于非活动状态，即便使用该选项也不会对其产生影响。如果读写事务处于活动状态，转储的开始时间可能会延迟一段不确定的时间。
+
+- --use-set-session-authorization
+
+    输出符合SQL标准的SET SESSION AUTHORIZATION命令而不是ALTER OWNER命令来确定对象所有权。这样令转储更加符合标准，但是如果转储文件中的对象的历史有些问题，那么可能不能正确恢复。并且，使用SET SESSION AUTHORIZATION的转储需要数据库系统管理员的权限才能转储成功，而ALTER OWNER需要的权限则低得多。
+
+- --with-encryption=AES128
+
+    指定转储数据需用AES128进行加密。
+
+- --with-key=KEY
+
+    AES128密钥规则如下：
+
+  - 钥长度为8\~16个字符。
+  - 至少包含大写字母（A-Z）、小写字母（a-z）、数字（0-9）、非字母数字字符（限定为\~!@\#$%^&\*\(\)-\_=+\\|\[\{\}\];:,<.\>/?）四类字符中的三类字符。
+
+> **说明：**
+>
+> - 使用gs_dump工具进行加密导出时，仅支持plain格式导出。通过-F plain导出的数据，需要通过gsql工具进行导入，且如果以加密方式导入，在通过gsql导入时，需要指定-with-key参数。
+> - 不支持加密导出存储过程和函数。
+
+- --with-salt=RANDVALUES
+
+  gs_dumpall使用此参数传递随机值。
+
+- --include-extensions
+
+  在转储中包含扩展。
+
+- --include-depend-objs
+
+  备份结果包含依赖于指定对象的对象信息。该参数需要同-t/-include-table-file参数关联使用才会生效。
+
+- --exclude-self
+
+  备份结果不包含指定对象自身的信息。该参数需要同-t/-include-table-file参数关联使用才会生效。
+
+- --pipeline
+
+  使用管道传输密码，禁止在终端使用。
+
+- --dont-overwrite-file
+
+  文本、tar以及自定义格式情况下会重写现有文件。这对目录格式不适用。
+
+  例如:
+
+  设想这样一种情景，即当前目录下backup.sql已存在。如果在输入命令中输入-f backup.sql选项时，当前目录恰好也生成backup.sql，文件就会被重写。
+
+  如果备份文件已存在，且输入-dont-overwrite-file选项，则会报告附带‘转储文件已经存在’信息的错误。
+
+  ```bash
+  gs_dump -p port_number mogdb -f backup.sql -F plain --dont-overwrite-file
+  ```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+> 
+> - -s/--schema-only和-a/--data-only不能同时使用。
+> - -c/--clean和-a/--data-only不能同时使用。
+> - --inserts/--column-inserts和-o/--oids不能同时使用，因为INSERT命令不能设置OIDS。
+> - --role和--rolepassword必须一起使用。
+> - --binary-upgrade-usermap和--binary-upgrade必须一起使用。
+> - --include-depend-objs/--exclude-self需要同-t/--include-table-file参数关联使用才会生效。
+> - --exclude-self必须同--include-depend-objs一起使用。
+
+#### 连接参数
+
+- -h, --host=HOSTNAME
+
+    指定主机名称。如果数值以斜杠开头，则被用作到Unix域套接字的路径。缺省从PGHOST环境变量中获取（如果已设置），否则，尝试一个Unix域套接字连接。
+
+    该参数只针对MogDB外，对MogDB内本机只能用127.0.0.1。
+
+    例如: 主机名
+
+    环境变量: PGHOST
+
+- -p, --port=PORT
+
+    指定主机端口。在开启线程池情况下，建议使用 pooler port，即主机端口+1。
+
+    环境变量: PGPORT
+
+- -U, --username=NAME
+
+    指定所连接主机的用户名。
+
+    不指定连接主机的用户名时，用户默认系统管理员。
+
+    环境变量: PGUSER
+
+- -w, --no-password
+
+    不出现输入密码提示。如果主机要求密码认证并且密码没有通过其它形式给出，则连接尝试将会失败。 该选项在批量工作和不存在用户输入密码的脚本中很有帮助。
+
+- -W, --password=PASSWORD
+
+    指定用户连接的密码。如果主机的认证策略是trust，则不会对系统管理员进行密码验证，即无需输入-W选项；如果没有-W选项，并且不是系统管理员，"Dump Restore工具"会提示用户输入密码。
+
+- --role=ROLENAME
+
+    指定创建转储使用的角色名。选择该选项，会使gs_dump连接数据库后，发起一个SET ROLE角色名命令。当所授权用户（由-U指定）没有gs_dump要求的权限时，该选项会起到作用，即切换到具备相应权限的角色。某些安装操作规定不允许直接以超系统管理员身份登录，而使用该选项能够在不违反该规定的情况下完成转储。
+
+- --rolepassword=ROLEPASSWORD
+
+    指定角色名的密码。
+
+### 说明
+
+如果MogDB有任何本地数据要添加到template1数据库，请谨慎将gs_dump的输出恢复到一个真正的空数据库中，否则可能会因为被添加对象的定义被复制，出现错误。要创建一个无本地添加的空数据库，需从template0而非template1复制，例如:
+
+```
+CREATE DATABASE foo WITH TEMPLATE template0;
+```
+
+tar归档形式的文件大小不得超过8GB（tar文件格式的固有限制）。tar文档整体大小和任何其他输出格式没有限制，操作系统可能对此有要求。
+
+由gs_dump生成的转储文件不包含优化程序用来做执行计划决定的统计数据。因此，最好从某转储文件恢复之后运行ANALYZE以确保最佳效果。转储文件不包含任何ALTER DATABASE…SET命令，这些设置由gs_dumpall转储，还有数据库用户和其他完成安装设置。
+
+<br/>
+
+### 示例
+
+使用gs_dump转储数据库为SQL文本文件或其它格式的操作，如下所示。
+
+示例中"Bigdata@123"表示数据库用户密码；"backup/MPPDB_backup.sql"表示导出的文件，其中backup表示相对于当前目录的相对目录；"37300"表示数据库服务器端口；"mogdb"表示要访问的数据库名。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+> 
+> 导出操作时，请确保该目录存在并且当前的操作系统用户对其具有读写权限。
+
+示例1: 执行gs_dump，导出mogdb数据库全量信息，导出的MPPDB_backup.sql文件格式为纯文本格式。
+
+```bash
+gs_dump -U omm -W Bigdata@123 -f backup/MPPDB_backup.sql -p 37300 mogdb -F p
+gs_dump[port='37300'][mogdb][2018-06-27 09:49:17]: The total objects number is 356.
+gs_dump[port='37300'][mogdb][2018-06-27 09:49:17]: [100.00%] 356 objects have been dumped.
+gs_dump[port='37300'][mogdb][2018-06-27 09:49:17]: dump database mogdb successfully
+gs_dump[port='37300'][mogdb][2018-06-27 09:49:17]: total time: 1274  ms
+```
+
+使用gsql程序从纯文本导出文件中导入数据。
+
+示例2: 执行gs_dump，导出mogdb数据库全量信息，导出的MPPDB_backup.tar文件格式为tar格式。
+
+```bash
+gs_dump -U omm -W Bigdata@123 -f backup/MPPDB_backup.tar -p 37300 mogdb -F t
+gs_dump[port='37300'][mogdb][2018-06-27 10:02:24]: The total objects number is 1369.
+gs_dump[port='37300'][mogdb][2018-06-27 10:02:53]: [100.00%] 1369 objects have been dumped.
+gs_dump[port='37300'][mogdb][2018-06-27 10:02:53]: dump database mogdb successfully
+gs_dump[port='37300'][mogdb][2018-06-27 10:02:53]: total time: 50086  ms
+```
+
+示例3: 执行gs_dump，导出mogdb数据库全量信息，导出的MPPDB_backup.dmp文件格式为自定义归档格式。
+
+```bash
+gs_dump -U omm -W Bigdata@123 -f backup/MPPDB_backup.dmp -p 37300 mogdb -F c
+gs_dump[port='37300'][mogdb][2018-06-27 10:05:40]: The total objects number is 1369.
+gs_dump[port='37300'][mogdb][2018-06-27 10:06:03]: [100.00%] 1369 objects have been dumped.
+gs_dump[port='37300'][mogdb][2018-06-27 10:06:03]: dump database mogdb successfully
+gs_dump[port='37300'][mogdb][2018-06-27 10:06:03]: total time: 36620  ms
+```
+
+示例4: 执行gs_dump，导出mogdb数据库全量信息，导出的MPPDB_backup文件格式为目录格式。
+
+```bash
+gs_dump -U omm -W Bigdata@123 -f backup/MPPDB_backup -p 37300  mogdb -F d
+gs_dump[port='37300'][mogdb][2018-06-27 10:16:04]: The total objects number is 1369.
+gs_dump[port='37300'][mogdb][2018-06-27 10:16:23]: [100.00%] 1369 objects have been dumped.
+gs_dump[port='37300'][mogdb][2018-06-27 10:16:23]: dump database mogdb successfully
+gs_dump[port='37300'][mogdb][2018-06-27 10:16:23]: total time: 33977  ms
+```
+
+示例5: 执行gs_dump，导出mogdb数据库信息，但不导出/home/MPPDB_temp.sql中指定的表信息。导出的MPPDB_backup.sql文件格式为纯文本格式。
+
+```bash
+gs_dump -U omm -W Bigdata@123 -p 37300 mogdb --exclude-table-file=/home/MPPDB_temp.sql -f backup/MPPDB_backup.sql
+gs_dump[port='37300'][mogdb][2018-06-27 10:37:01]: The total objects number is 1367.
+gs_dump[port='37300'][mogdb][2018-06-27 10:37:22]: [100.00%] 1367 objects have been dumped.
+gs_dump[port='37300'][mogdb][2018-06-27 10:37:22]: dump database mogdb successfully
+gs_dump[port='37300'][mogdb][2018-06-27 10:37:22]: total time: 37017  ms
+```
+
+示例6: 执行gs_dump，仅导出依赖于指定表testtable的视图信息。然后创建新的testtable表，再恢复依赖其上的视图。
+
+- 备份仅依赖于testtable的视图。
+
+    ```bash
+    gs_dump -s -p 37300 mogdb -t PUBLIC.testtable --include-depend-objs --exclude-self -f backup/  MPPDB_backup.sql -F p
+    gs_dump[port='37300'][mogdb][2018-06-15 14:12:54]: The total objects number is 331.
+    gs_dump[port='37300'][mogdb][2018-06-15 14:12:54]: [100.00%] 331 objects have been dumped.
+    gs_dump[port='37300'][mogdb][2018-06-15 14:12:54]: dump database mogdb successfully
+    gs_dump[port='37300'][mogdb][2018-06-15 14:12:54]: total time: 327  ms
+    ```
+
+- 修改testtable名称。
+
+    ```
+    gsql -p 37300 mogdb -r -c "ALTER TABLE PUBLIC.testtable RENAME TO testtable_bak;"
+    ```
+
+- 创建新的testtable表。
+
+    ```
+    CREATE TABLE PUBLIC.testtable(a int, b int, c int);
+    ```
+
+- 还原依赖于testtable的视图。
+
+    ```
+    gsql -p 37300 mogdb -r -f backup/MPPDB_backup.sql
+    ```
+
+<br/>
+
+## gs_dumpall
+
+### 背景信息
+
+gs_dumpall是MogDB用于导出所有数据库相关信息工具，它可以导出MogDB数据库的所有数据，包括默认数据库mogdb的数据、自定义数据库的数据以及MogDB所有数据库公共的全局对象。
+
+gs_dumpall工具由操作系统用户omm执行。
+
+gs_dumpall工具在进行数据导出时，其他用户可以访问MogDB数据库（读或写）。
+
+gs_dumpall工具支持导出完整一致的数据。例如，T1时刻启动gs_dumpall导出MogDB数据库，那么导出数据结果将会是T1时刻该MogDB数据库的数据状态，T1时刻之后对MogDB的修改不会被导出。
+
+gs_dumpall生成列不会被转储。
+
+gs_dumpall在导出MogDB所有数据库时分为两部分:
+
+- gs_dumpall自身对所有数据库公共的全局对象进行导出，包括有关数据库用户和组，表空间以及属性（例如，适用于数据库整体的访问权限）信息。
+- gs_dumpall通过调用gs_dump来完成MogDB中各数据库的SQL脚本文件导出，该脚本文件包含将数据库恢复为其保存时的状态所需要的全部SQL语句。
+
+以上两部分导出的结果为纯文本格式的SQL脚本文件，使用gsql运行该脚本文件可以恢复MogDB数据库。
+
+<br/>
+
+### 注意事项
+
+- 禁止修改导出的文件和内容，否则可能无法恢复成功。
+- 为了保证数据一致性和完整性，gs_dumpall会对需要转储的表设置共享锁。如果某张表在别的事务中设置了共享锁，gs_dumpall会等待此表的锁释放后锁定此表。如果无法在指定时间内锁定某张表，转储会失败。用户可以通过指定-lock-wait-timeout选项，自定义等待锁超时时间。
+- 由于gs_dumpall读取所有数据库中的表，因此必须以MogDB管理员身份进行连接，才能导出完整文件。在使用gsql执行脚本文件导入时，同样需要管理员权限，以便添加用户和组以及创建数据库。
+
+<br/>
+
+### 语法
+
+```bash
+gs_dumpall [OPTION]...
+```
+
+<br/>
+
+### 参数说明
+
+#### 通用参数
+
+- -f, --filename=FILENAME
+
+    将输出发送至指定文件。如果这里省略，则使用标准输出。
+
+- -v, --verbose
+
+    指定verbose模式。该选项将导致gs_dumpall向转储文件输出详细的对象注解和启动/停止次数，向标准错误流输出处理信息。
+
+- -V, --version
+
+    打印gs_dumpall版本，然后退出。
+
+- --lock-wait-timeout=TIMEOUT
+
+    请勿在转储刚开始时一直等待以获取共享表锁。如果无法在指定时间内锁定某个表，就选择失败。可以以任何符合SET statement_timeout的格式指定超时时间。
+
+- -?, --help
+
+    显示gs_dumpall命令行参数帮助，然后退出。
+
+#### 转储参数
+
+- -a, --data-only
+
+    只转储数据，不转储模式（数据定义）。
+
+- -c, --clean
+
+    在重新创建数据库之前，执行SQL语句清理（删除）这些数据库。针对角色和表空间的转储命令已添加。
+
+- -g, --globals-only
+
+    只转储全局对象（角色和表空间），无数据库。
+
+- -o, --oids
+
+    转储每个表的对象标识符（OIDs），作为表的一部分数据。该选项用于应用以某种方式参照了OID列的情况。如果不是以上这种情况，请勿使用该选项。
+
+- -O, --no-owner
+
+    不输出设置对象的归属这样的命令，以匹配原始数据库。默认情况下，gs_dumpall会发出ALTER OWNER或SET SESSION AUTHORIZATION语句设置所创建的模式元素的所属。如果脚本正在运行，该语句不会执行成功，除非是由系统管理员触发（或是拥有脚本中所有对象的同一个用户）。通过指定-O，编写一个任何用户都能存储的脚本，且该脚本会授予该用户拥有所有对象的权限。
+
+- -r, --roles-only
+
+    只转储角色，不转储数据库或表空间。
+
+- -s, --schema-only
+
+    只转储对象定义（模式），而非数据。
+
+- -S, --sysadmin=NAME
+
+    在转储过程中使用的系统管理员名称。
+
+- -t, --tablespaces-only
+
+    只转储表空间，不转储数据库或角色。
+
+- -x, --no-privileges
+
+    防止转储访问权限（授权/撤销命令）。
+
+- --column-inserts|--attribute-inserts
+
+    以INSERT命令带列名（INSERT INTO表（列、…）值…）方式导出数据。这会导致恢复缓慢。但是由于该选项会针对每行生成一个独立分开的命令，所以在重新加载某行时出现的错误只会导致那行丢失，而非整个表内容。
+
+- --disable-dollar-quoting
+
+    该选项将禁止在函数体前使用美元符号$，并强制使用SQL标准字符串语法对其进行引用。
+
+- --disable-triggers
+
+    该参数为扩展预留接口，不建议使用。
+
+- --inserts
+
+    发出INSERT命令（而非COPY命令）转储数据。这会导致恢复缓慢。注意:如果重排列顺序，可能会导致恢复整个失败。-column-inserts选项更加安全，虽然可能更慢些。
+
+- --no-security-labels
+
+    该参数为扩展预留接口，不建议使用。
+
+- --no-tablespaces
+
+    请勿输出创建表空间的命令，也请勿针对对象选择表空间。使用该选项，无论默认表空间是哪个，在恢复过程中所有对象都会被创建。
+
+- --no-publications
+
+    不转储发布。
+
+- --no-security-labels
+
+    该参数为扩展预留接口，不建议使用。
+
+- --no-subscriptions
+
+    不转储订阅。
+
+- --include-alter-table
+
+    导出表中已删除的列信息。
+
+- --quote-all-identifiers
+
+    强制对所有标识符加引号。为了向后续版本迁移，且其中可能涉及引入额外关键词，在转储相应数据库时该选项会有帮助。
+
+- --dont-overwrite-file
+
+    不重写当前文件。
+
+- --use-set-session-authorization
+
+    输出符合SQL标准的SET SESSION AUTHORIZATION命令而不是ALTER OWNER命令来确定对象所有权。这样令转储更加符合标准，但是如果转储文件中的对象的历史有些问题，那么可能不能正确恢复。并且，使用SET SESSION AUTHORIZATION的转储需要数据库系统管理员的权限才能转储成功，而ALTER OWNER需要的权限则低得多。
+
+- --with-encryption=AES128
+
+    指定转储数据需用AES128进行加密。
+
+- --with-key=KEY
+
+  AES128密钥规则如下：
+
+  - 密钥长度为8\~16个字符。
+  - 至少包含大写字母（A-Z），小写字母（a-z），数字（0-9），非字母数字字符（限定为\~!@\#$%^&\*\(\)-\_=+\\|\[\{\}\];:,<.\>/?）四类字符中的三类字符。
+
+- --include-extensions
+
+    如果include-extensions参数被设置，将备份所有的CREATE EXTENSION语句。
+
+- --include-templatedb
+
+    转储过程中包含模板库。
+
+- --binary-upgrade
+
+    该参数为扩展预留接口，不建议使用。
+
+- --binary-upgrade-usermap="USER1=USER2"
+
+    该参数为扩展预留接口，不建议使用。
+
+- --non-lock-table
+
+    该参数仅供OM工具使用。
+
+- --tablespaces-postfix
+
+    该参数为扩展预留接口，不建议使用。
+
+- --parallel-jobs
+
+    指定备份进程并发数，取值范围为1~1000。
+
+- --pipeline
+
+    使用管道传输密码，禁止在终端使用。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+> 
+> - -g/--globals-only和-r/--roles-only不能同时使用。
+> - -g/--globals-only和-t/--tablespaces-only不能同时使用。
+> - -r/--roles-only和-t/--tablespaces-only不能同时使用。
+> - -s/--schema-only和-a/--data-only不能同时使用。
+> - -r/--roles-only和-a/--data-only不能同时使用。
+> - -t/--tablespaces-only和-a/--data-only不能同时使用。
+> - -g/--globals-only和-a/--data-only不能同时使用。
+> - --tablespaces-postfix和--binary-upgrade必须一起使用。
+> - --binary-upgrade-usermap和--binary-upgrade必须一起使用。
+> - --parallel-jobs和-f/--file必须一起使用。
+
+#### 连接参数
+
+- -h, --host
+
+    指定主机的名称。如果取值是以斜线开头，它将用作Unix域套接字的目录。默认值取自PGHOST环境变量；如果没有设置，将启动某个Unix域套接字建立连接。
+
+    该参数只针对MogDB外，对MogDB内本机只能用127.0.0.1。
+
+    环境变量: PGHOST
+
+- -l, --database
+
+    指定所连接的转储全局对象的数据库名称，并去寻找还有其他哪些数据库需要被转储。如果没有指定，会使用mogdb数据库，如果mogdb数据库不存在，会使用template1。
+
+- -p, --port
+
+    指定服务器所侦听的TCP端口或本地Unix域套接字后缀，以确保连接。默认值设置为PGPORT环境变量。
+
+    在开启线程池情况下，建议使用 pooler port，即侦听端口+1。
+
+    环境变量: PGPORT
+
+- -U, --username
+
+    所连接的用户名。
+
+    环境变量: PGUSER
+
+- -w, --no-password
+
+    不出现输入密码提示。如果服务器要求密码认证并且密码没有通过其它形式给出，则连接尝试将会失败。 该选项在批量工作和不存在用户输入密码的脚本中很有帮助。
+
+- -W, --password
+
+    指定用户连接的密码。如果主机的认证策略是trust，则不会对系统管理员进行密码验证，即无需输入-W选项；如果没有-W选项，并且不是系统管理员，"Dump Restore工具"会提示用户输入密码。
+
+- --role
+
+    指定创建转储使用的角色名。选择该选项，会使gs_dumpall连接数据库后，发起一个SET ROLE角色名命令。当所授权用户（由-U指定）没有gs_dumpall要求的权限时，该选项会起到作用，即切换到具备相应权限的角色。某些安装操作规定不允许直接以系统管理员身份登录，而使用该选项能够在不违反该规定的情况下完成转储。
+
+- --rolepassword
+
+    指定具体角色用户的角色密码。
+
+<br/>
+
+### 说明
+
+由于gs_dumpall内部调用gs_dump，所以一些诊断信息参见[gs_dump](#gs_dump)。
+
+一旦恢复，最好在每个数据库上运行ANALYZE，优化程序提供有用的统计数据。
+
+gs_dumpall恢复前需要所有必要的表空间目录才能退出；否则，对于处在非默认位置的数据库，数据库创建会失败。
+
+<br/>
+
+### 示例
+
+使用gs_dumpall一次导出MogDB的所有数据库。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+> 
+> gs_dumpall仅支持纯文本格式导出。所以只能使用gsql恢复gs_dumpall导出的转储内容。
+
+```bash
+gs_dumpall -f backup/bkp2.sql -p 37300
+gs_dump[port='37300'][dbname='mogdb'][2018-06-27 09:55:09]: The total objects number is 2371.
+gs_dump[port='37300'][dbname='mogdb'][2018-06-27 09:55:35]: [100.00%] 2371 objects have been dumped.
+gs_dump[port='37300'][dbname='mogdb'][2018-06-27 09:55:46]: dump database dbname='mogdb' successfully
+gs_dump[port='37300'][dbname='mogdb'][2018-06-27 09:55:46]: total time: 55567  ms
+gs_dumpall[port='37300'][2018-06-27 09:55:46]: dumpall operation successful
+gs_dumpall[port='37300'][2018-06-27 09:55:46]: total time: 56088  ms
+```
+
+<br/>
+
+## gs_restore
+
+### 背景信息
+
+gs_restore是MogDB提供的针对gs_dump导出数据的导入工具。通过此工具可由gs_dump生成的导出文件进行导入。
+
+gs_restore工具由操作系统用户omm执行。
+
+主要功能包含:
+
+- 导入到数据库
+
+    如果连接参数中指定了数据库，则数据将被导入到指定的数据库中。其中，并行导入必须指定连接的密码。导入时生成列会自动更新，并像普通列一样保存。
+
+- 导入到脚本文件
+
+    如果未指定导入数据库，则创建包含重建数据库所必须的SQL语句脚本并写入到文件或者标准输出。等效于直接使用gs_dump导出为纯文本格式。
+
+<br/>
+
+### 命令格式
+
+```bash
+gs_restore [OPTION]... FILE
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+> 
+> - FILE没有短选项或长选项。用来指定归档文件所处的位置。
+> - 作为前提条件，需输入dbname或-l选项。不允许用户同时输入dbname和-l选项。
+> - gs_restore默认是以追加的方式进行数据导入。为避免多次导入造成数据异常，在进行导入时，建议使用“-c”参数，在重新创建数据库对象前，清理（删除）已存在于将要还原的数据库中的数据库对象。
+> - 日志打印无开关，若需隐藏日志，请将日志重定向到日志文件。若恢复表数据时，数据量很大，会分批恢复，因此会多次出现"表数据已完成导入"的日志。
+
+<br/>
+
+### 参数说明
+
+#### 通用参数
+
+- -d, --dbname=NAME
+
+    连接数据库dbname并直接导入到该数据库中。
+
+- -f, --file=FILENAME
+
+    指定生成脚本的输出文件，或使用-l时列表的输出文件。
+
+    默认是标准输出。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+  > 
+  > -f不能同-d一起使用。
+
+- -F, --format=c|d|t
+
+    指定归档格式。由于gs_restore会自动决定格式，因此不需要指定格式。
+
+    取值范围:
+
+  - c/custom: 该归档形式为[gs_dump](#gs_dump)的自定义格式。
+  - d/directory: 该归档形式是一个目录归档形式。
+  - t/tar: 该归档形式是一个tar归档形式。
+
+- -l, -list
+
+    列出归档形式内容。这一操作的输出可用作-L选项的输入。注意如果像-n或-t的过滤选项与-l使用，过滤选项将会限制列举的项目（即归档形式内容）。
+
+- -v, --verbose
+
+    指定verbose模式。
+
+- -V, --version
+
+    打印gs_restore版本，然后退出。
+
+- -?, --help
+
+    显示gs_restore命令行参数帮助，然后退出。
+
+#### 导入参数
+
+- -a, --data-only
+
+    只导入数据，不导入模式（数据定义）。gs_restore的导入是以追加方式进行的。
+
+- -c, --clean
+
+  在重新创建数据库对象前，清理（删除）已存在于将要还原的数据库中的数据库对象。
+
+- -C, --create
+
+    导入数据库之前会先使用CREATE DATABASE创建数据库。（指定该选项后，-d指定的数据库仅用以执行CREATE DATABASE命令，所有数据依然会导入到创建的数据库中。）
+
+- -e, --exit-on-error
+
+    当发送SQL语句到数据库时如果出现错误，请退出。默认状态下会继续，且在导入后会显示一系列错误信息。
+
+- -I, --index=NAME
+
+    只导入已列举的index的定义。允许导入多个index。如果多次输入-I index导入多个index。
+
+    例如:
+
+    ```
+    gs_restore -h host_name -p port_number -d mogdb -I Index1 -I Index2 backup/MPPDB_backup.tar
+    ```
+
+    在上面这个例子中，Index1和Index2会被导入。
+
+- -j, --jobs=NUM
+
+    运行gs_restore最耗时的部分（如加载数据、创建index或创建约束）使用并发任务。该选项能大幅缩短导入时间，即将一个大型数据库导入到某一多处理器的服务器上。
+
+    每个任务可能是一个进程或一个线程，这由操作系统决定；每个任务与服务器进行单独连接。
+
+    该选项的最优值取决于服务器的硬件设置、客户端以及网络。还包括这些因素，如CPU核数量、硬盘设置。建议是从增加服务器上的CPU核数量入手，更大的值（服务器上CPU核数量）在很多情况下也能导致数据文件更快的被导入。当然，过高的值会由于超负荷反而导致性能降低。
+
+    该选项只支持自定义归档格式。输入文件必须是常规文件（不能是像pipe的文件）。如果是通过脚本文件，而非直接连接数据库服务器，该选项可忽略。而且，多任务不能与-single-transaction选项一起使用。
+
+- -L, --use-list=FILENAME
+
+    只导入列举在list-file中的那些归档形式元素，导入顺序以它们在文件中的顺序为准。注意如果像-n或-t的过滤选项与-L使用，它们将会进一步限制导入的项目。
+
+    一般情况下，list-file是通过编辑前面提到的某个-l参数的输出创建的。文件行的位置可更改或直接删除，也可使用分号（;）在行的开始注出。
+
+- -n, --schema=NAME
+
+    只导入已列举的模式中的对象。
+
+    该选项可与-t选项一起用以导入某个指定的表。
+
+    多次输入-n _schemaname_可以导入多个模式。
+
+    例如:
+
+    ```
+    gs_restore -h host_name -p port_number -d mogdb -n sch1 -n sch2 backup/MPPDB_backup.tar
+    ```
+
+    在上面这个例子中，sch1和sch2会被导入。
+
+- -O, --no-owner
+
+    不输出设置对象的归属这样的命令，以匹配原始数据库。默认情况下，gs_restore会发出ALTER OWNER或SET SESSION AUTHORIZATION语句设置所创建的模式元素的所属。除非是由系统管理员（或是拥有脚本中所有对象的同一个用户）进行数据库首次连接的操作，否则语句会失败。使用-O选项，任何用户名都可用于首次连接，且该用户拥有所有已创建的对象。
+
+- -P, --function=NAME(args)
+
+    只导入已列举的函数。请按照函数所在转储文件中的目录，准确拼写函数名称和参数。
+
+    当-P单独使用时，表示导入文件中所有'function-name(args)'函数；当-P同-n一起使用时，表示导入指定模式下的'function-name(args)'函数；多次输入-P，而仅指定一次-n，表示所有导入的函数默认都是位于-n模式下的。
+
+    可以多次输入-n schema-name -P 'function-name(args)'同时导入多个指定模式下的函数。
+
+    例如:
+
+    ```
+    gs_restore -h host_name -p port_number -d mogdb -n test1 -P 'Func1(integer)' -n test2 -P 'Func2(integer)' backup/MPPDB_backup.tar
+    ```
+
+    在上面这个例子中，test1模式下的函数Func1(i integer)和test2模式下的函数Func2(j integer)会被一起导入。
+
+- -s, --schema-only
+
+    只导入模式（数据定义），不导入数据（表内容）。当前的序列值也不会导入。
+
+- -S, --sysadmin=NAME
+
+    该参数为扩展预留接口，不建议使用。
+
+- -t, --table=NAME
+
+    只导入已列举的表定义、数据或定义和数据。该选项与-n选项同时使用时，用来指定某个模式下的表对象。-n参数不输入时，默认为PUBLIC模式。多次输入-n -t 可以导入指定模式下的多个表。
+
+    例如:
+
+    导入PUBLIC模式下的table1
+
+    ```
+    gs_restore -h host_name -p port_number -d mogdb -t table1 backup/MPPDB_backup.tar
+    ```
+
+    导入test1模式下的test1和test2模式下test2
+
+    ```
+    gs_restore -h host_name -p port_number -d mogdb -n test1 -t test1 -n test2 -t test2 backup/MPPDB_backup.tar
+    ```
+
+    导入PUBLIC模式下的table1和test1 模式下test1
+
+    ```
+    gs_restore -h host_name -p port_number -d mogdb -n PUBLIC -t table1 -n test1 -t table1 backup/MPPDB_backup.tar
+    ```
+
+> **说明：**
+> 
+> -t不支持schema_name.table_name的输入格式。
+
+- -T, --trigger=NAME
+
+    该参数为扩展预留接口。
+
+- -x, --no-privileges/-no-acl
+
+    防止导入访问权限（GRANT/REVOKE命令）。
+
+- -1, --single-transaction
+
+    执行导入作为一个单独事务（即把命令包围在BEGIN/COMMIT中）。
+
+    该选项确保要么所有命令成功完成，要么没有改变应用。该选项意为--exit-on-error。
+
+- --disable-triggers
+
+    该参数为扩展预留接口，不建议使用。
+
+- --no-data-for-failed-tables
+
+    默认状态下，即使创建表的命令失败（如表已经存在），表数据仍会被导入。使用该选项，像这种表的数据会被跳过。如果目标数据库已包含想要的表内容，这种行为会有帮助。
+
+    该选项只有在直接导入到某数据库中时有效，不针对生成SQL脚本文件输出。
+
+- --no-publications
+
+    不导入发布。
+
+- --no-security-labels
+
+    该参数为扩展预留接口，不建议使用。
+
+- --no-subscriptions
+
+    不导入订阅。
+
+- --no-tablespaces
+
+    不输出选择表空间的命令。使用该选项，无论默认表空间是哪个，在导入过程中所有对象都会被创建。
+
+- --section=SECTION
+
+    导入已列举的区段（如pre-data、data或post-data）。
+
+- --use-set-session-authorization
+
+    该选项用来进行文本格式的备份。
+
+    输出SET SESSION AUTHORIZATION命令，而非ALTER OWNER命令，用以决定对象归属。该选项使转储更加兼容标准，但通过参考转储中对象的记录，导入过程可能会有问题。使用SET SESSION AUTHORIZATION的转储要求必须是系统管理员，同时在导入前还需参考“SET SESSION AUTHORIZATION”，手工对导出文件的密码进行修改验证，只有这样才能进行正确的导入操作，相比之下，ALTER OWNER对权限要求较低。
+
+- --pipeline
+
+    使用管道传输密码，禁止在终端使用。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> 
+> - 如果安装过程中有任何本地数据要添加到template1数据库，请谨慎将gs_restore的输出载入到一个真正的空数据库中；否则可能会因为被添加对象的定义被复制，而出现错误。要创建一个无本地添加的空数据库，需从template0而非template1复制，例如:
+> 
+>    ```
+>    CREATE DATABASE foo WITH TEMPLATE template0;
+>    ```
+> 
+> - gs_restore不能选择性地导入大对象；例如只能导入那些指定表的对象。如果某个归档形式包含大对象，那所有大对象都会被导入或一个都不会被导入，如果它们通过-L、-t或其他选项被排除。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+> 
+> 1. -d/--dbname 和 -f/--file 不能同时使用。
+> 2. -s/--schema-only 和 -a/--data-only不能同时使用。
+> 3. -c/--clean 和 -a/--data-only不能同时使用。
+> 4. 使用--single-transaction时，-j/--jobs必须为单任务。
+> 5. --role和--rolepassword必须一起使用。
+
+#### 连接参数
+
+- -h, --host=HOSTNAME
+
+    指定的主机名称。如果取值是以斜线开头，他将用作Unix域套接字的目录。默认值取自PGHOST环境变量；如果没有设置，将启动某个Unix域套接字建立连接。
+
+    该参数只针对MogDB外，对MogDB内本机只能用127.0.0.1。
+
+- -p, --port=PORT
+
+    指定服务器所侦听的TCP端口或本地Unix域套接字后缀，以确保连接。默认值设置为PGPORT环境变量。
+
+    在开启线程池情况下，建议使用pooler port，即侦听端口+1。
+
+- -U, --username=NAME
+
+    所连接的用户名。
+
+- -w, --no-password
+
+    不出现输入密码提示。如果服务器要求密码认证并且密码没有通过其它形式给出，则连接尝试将会失败。该选项在批量工作和不存在用户输入密码的脚本中很有帮助。
+
+- -W, --password=PASSWORD
+
+    指定用户连接的密码。如果主机的认证策略是trust，则不会对系统管理员进行密码验证，即无需输入-W参数；如果没有-W参数，并且不是系统管理员，"gs_restore"会提示用户输入密码。
+
+- --role=ROLENAME
+
+    指定导入操作使用的角色名。选择该参数，会使gs_restore连接数据库后，发起一个SET ROLE角色名命令。当所授权用户（由-U指定）没有gs_restore要求的权限时，该参数会起到作用，即切换到具备相应权限的角色。某些安装操作规定不允许直接以初始用户身份登录，而使用该参数能够在不违反该规定的情况下完成导入。
+
+- --rolepassword=ROLEPASSWORD
+
+    指定具体角色用户的角色密码。
+
+<br/>
+
+### 示例
+
+特例: 执行gsql程序，使用如下选项导入由gs_dump/gs_dumpall生成导出文件夹（纯文本格式）的MPPDB_backup.sql文件到mogdb数据库。
+
+```bash
+gsql -d mogdb -p 15400 -W Bigdata@123 -f /home/omm/test/MPPDB_backup.sql
+SET
+SET
+SET
+SET
+SET
+ALTER TABLE
+ALTER TABLE
+ALTER TABLE
+ALTER TABLE
+ALTER TABLE
+CREATE INDEX
+CREATE INDEX
+CREATE INDEX
+SET
+CREATE INDEX
+REVOKE
+REVOKE
+GRANT
+GRANT
+total time: 30476  ms
+```
+
+gs_restore用来导入由gs_dump生成的导出文件。
+
+示例1: 执行gs_restore，将导出的MPPDB_backup.dmp文件（自定义归档格式）导入到mogdb数据库。
+
+```bash
+gs_restore -W Bigdata@123 backup/MPPDB_backup.dmp -p 15400 -d mogdb
+gs_restore: restore operation successful
+gs_restore: total time: 13053  ms
+```
+
+示例2: 执行gs_restore，将导出的MPPDB_backup.tar文件（tar格式）导入到mogdb数据库。
+
+```bash
+gs_restore backup/MPPDB_backup.tar -p 15400 -d mogdb
+gs_restore[2017-07-21 19:16:26]: restore operation successful
+gs_restore[2017-07-21 19:16:26]: total time: 21203  ms
+```
+
+示例3: 执行gs_restore，将导出的MPPDB_backup文件（目录格式）导入到mogdb数据库。
+
+```bash
+gs_restore backup/MPPDB_backup -p 15400 -d mogdb
+gs_restore[2017-07-21 19:16:26]: restore operation successful
+gs_restore[2017-07-21 19:16:26]: total time: 21003  ms
+```
+
+示例4: 执行gs_restore，使用自定义归档格式的MPPDB_backup.dmp文件来进行如下导入操作。 导入PUBLIC模式下所有对象的定义和数据。在导入时会先删除已经存在的对象，如果原对象存在跨模式的依赖则需手工强制干预。
+
+```bash
+gs_restore backup/MPPDB_backup.dmp -p 15400 -d mogdb -e -c -n PUBLIC
+gs_restore: [archiver (db)] Error while PROCESSING TOC:
+gs_restore: [archiver (db)] Error from TOC entry 313; 1259 337399 TABLE table1 gaussdba
+gs_restore: [archiver (db)] could not execute query: ERROR:  cannot drop table table1 because other objects depend on it
+DETAIL:  view t1.v1 depends on table table1
+HINT:  Use DROP ... CASCADE to drop the dependent objects too.
+    Command was: DROP TABLE public.table1;
+```
+
+手工删除依赖，导入完成后再重新创建。
+
+```bash
+gs_restore backup/MPPDB_backup.dmp -p 15400 -d mogdb -e -c -n PUBLIC
+gs_restore[2017-07-21 19:16:26]: restore operation successful
+gs_restore[2017-07-21 19:16:26]: total time: 2203  ms
+```
+
+示例5: 执行gs_restore，使用自定义归档格式的MPPDB_backup.dmp文件来进行如下导入操作。只导入PUBLIC模式下表table1的定义。
+
+```bash
+gs_restore backup/MPPDB_backup.dmp -p 15400 -d mogdb -e -c -s -n PUBLIC -t table1
+gs_restore[2017-07-21 19:16:26]: restore operation successful
+gs_restore[2017-07-21 19:16:26]: total time: 21000  ms
+```
+
+示例6: 执行gs_restore，使用自定义归档格式的MPPDB_backup.dmp文件来进行如下导入操作。只导入PUBLIC模式下表table1的数据。
+
+```bash
+gs_restore backup/MPPDB_backup.dmp -p 15400 -d mogdb -e -a -n PUBLIC -t table1
+gs_restore[2017-07-21 19:16:26]: restore operation successful
+gs_restore[2017-07-21 19:16:26]: total time: 20203  ms
+```
+
+<br/>
+
+## gs_backup
+
+### 背景信息
+
+MogDB部署成功后，在数据库运行的过程中，会遇到各种问题及异常状态。MogDB提供了gs_backup工具帮助MogDB备份、恢复重要数据、显示帮助信息和版本号信息。
+
+<br/>
+
+### 前提条件
+
+- 可以正常连接MogDB数据库。
+- 在进行还原时，需要保证各节点备份目录中存在备份文件。
+- 需以操作系统用户omm执行gs_backup命令。
+
+<br/>
+
+### 语法
+
+- 备份数据库主机
+
+    ```
+    gs_backup -t backup --backup-dir=BACKUPDIR [-h HOSTNAME] [--parameter] [--binary] [--all] [-l LOGFILE]
+    ```
+
+- 恢复数据库主机
+
+    ```
+    gs_backup -t restore --backup-dir=BACKUPDIR [-h HOSTNAME] [--parameter] [--binary] [--all] [-l LOGFILE] [--force]
+    ```
+
+- 显示帮助信息
+
+    ```
+    gs_backup -? | --help
+    ```
+
+- 显示版本号信息
+
+    ```
+    gs_backup -V | --version
+    ```
+
+<br/>
+
+### 参数说明
+
+gs_backup参数可以分为如下几类:
+
+- 备份数据库主机参数:
+
+  - -h
+
+    指定存储备份文件的主机名称。
+
+    取值范围: 主机名称。如果不指定主机名称，则备份当前集群。
+
+  - --backup-dir=BACKUPDIR
+
+    备份文件保存路径。
+
+  - --parameter
+
+    备份参数文件，不指定-parameter、-binary、-all参数时默认只备份参数文件。
+
+  - --binary
+
+    备份app目录下的二进制文件。
+
+  - --all
+
+    备份app目录下的二进制文件、pg_hba.conf和postgsql.conf文件。
+
+  - -l
+
+    指定日志文件及存放路径。
+
+    默认值: $GAUSSLOG/om/gs_backup-YYYY-MM-DD_hhmmss.log
+
+- 恢复数据库主机参数:
+
+  - -h
+
+    指定需要恢复主机的名称。
+
+    取值范围：主机名称。如果不指定主机，则恢复对应的备份节点。
+
+  - --backup-dir=BACKUPDIR
+
+    恢复文件提取路径。
+
+  - --parameter
+
+    恢复参数文件，不指定--parameter、--binary、--all参数时默认只恢复参数文件。
+
+  - --binary
+
+    恢复二进制文件。
+
+  - --all
+
+    恢复二进制和参数文件。
+
+  - -l
+
+    指定日志文件及存放路径。
+
+    默认值: $GAUSSLOG/om/gs_backup-YYYY-MM-DD_hhmmss.log
+
+  - --force
+
+    节点的静态文件丢失后强行restore，仅限--all或者--binary一起使用时才生效。
+
+- 其他参数:
+
+  - -?, --help
+
+    显示帮助信息。
+
+  - -V, --version
+
+    显示版本号信息。
+
+  - -t
+
+    指定操作类型。
+
+    取值范围：backup或者restore。
+
+<br/>
+
+### 示例
+
+- 使用gs_backup脚本备份数据库主机。
+
+    ```bash
+    gs_backup -t backup --backup-dir=/opt/software/mogdb/backup_dir -h plat1 --parameter
+    Backing up MogDB.
+    Parsing configuration files.
+    Successfully parsed the configuration file.
+    Performing remote backup.
+    Remote backup succeeded.
+    Successfully backed up mogdb
+    ```
+
+- 使用gs_backup脚本恢复数据库主机。
+
+    ```bash
+    gs_backup -t restore --backup-dir=/opt/software/mogdb/backup_dir -h plat1 --parameter
+    Restoring MogDB.
+    Parsing the configuration file.
+    Successfully parsed configuration files.
+    Performing remote restoration.
+    Remote restoration succeeded.
+    Successfully restored openGauss.
+    ```
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/br/1-4-br.md b/product/zh/docs-mogdb/v3.0/administrator-guide/br/1-4-br.md
new file mode 100644
index 0000000000000000000000000000000000000000..5bd9f6f3a0373f6611941bc94329a3b0ccd5c0b9
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/br/1-4-br.md
@@ -0,0 +1,215 @@
+---
+title: 闪回恢复
+summary: 闪回恢复
+author: Guo Huan
+date: 2021-10-12
+---
+
+# 闪回恢复
+
+闪回恢复功能是数据库恢复技术的一环，可以有选择性的撤销一个已提交事务的影响，将数据从人为不正确的操作中进行恢复。在采用闪回技术之前，只能通过备份恢复、PITR等手段找回已提交的数据库修改，恢复时长需要数分钟甚至数小时。采用闪回技术后，恢复已提交的数据库修改前的数据，只需要秒级，而且恢复时间和数据库大小无关。
+
+> **说明：**
+> ASTORE引擎暂不支持闪回DROP/TRUNCATE。
+
+**闪回支持两种恢复模式：**
+
+- 基于MVCC多版本的数据恢复（仅支持Ustore）：适用于误删除、误更新、误插入数据的查询和恢复，用户通过配置旧版本保留时间，并执行相应的查询或恢复命令，查询或恢复到指定的时间点或CSN点。
+- 基于数据库回收站的恢复（仅支持Astore）：适用于误DROP、误TRUNCATE的表的恢复。用户通过配置回收站开关，并执行相应的恢复命令，可以将误DROP、误TRUNCATE的表找回。
+
+**相关参数：**
+
+- undo_zone_count=16384
+
+  内存中可分配的undo zone数量，0代表禁用undo和Ustore表，建议取值为max_connections*4
+
+- enable_default_ustore_table=on
+
+  开启默认支持Ustore存储引擎
+
+- version_retention_age=10000
+
+  旧版本保留的事务数，超过该事务数的旧版本将被回收清理
+
+- enable_recyclebin=on
+
+  打开回收站
+
+- recyclebin_retention_time=15min
+
+  设置回收站对象保留时间，超过该时间的回收站对象将被自动清理
+
+<br/>
+
+## 闪回查询
+
+### 背景信息
+
+闪回查询可以查询过去某个时间点表的某个snapshot数据，这一特性可用于查看和逻辑重建意外删除或更改的受损数据。闪回查询基于MVCC多版本机制，通过检索查询旧版本，获取指定老版本数据。
+
+### 前提条件
+
+- undo_retention_time参数用于设置undo旧版本的保留时间。
+
+### 语法
+
+```ebnf+diagram
+FlashBack ::= {[ ONLY ] table_name [ * ] [ partition_clause ] [ [ AS ] alias [ ( column_alias [, ...] ) ] ]
+[ TABLESAMPLE sampling_method ( argument [, ...] ) [ REPEATABLE ( seed ) ] ]
+[TIMECAPSULE { TIMESTAMP | CSN } expression ]
+|( select ) [ AS ] alias [ ( column_alias [, ...] ) ]
+|with_query_name [ [ AS ] alias [ ( column_alias [, ...] ) ] ]
+|function_name ( [ argument [, ...] ] ) [ AS ] alias [ ( column_alias [, ...] | column_definition [, ...] ) ]
+|function_name ( [ argument [, ...] ] ) AS ( column_definition [, ...] )
+|from_item [ NATURAL ] join_type from_item [ ON join_condition | USING ( join_column [, ...] ) ]}
+```
+
+语法树中“TIMECAPSULE {TIMESTAMP | CSN} expression”为闪回功能新增表达方式，其中TIMECAPSULE表示使用闪回功能，TIMESTAMP以及CSN表示闪回功能使用具体时间点信息或使用CSN（commit sequence number）信息。
+
+### 参数说明
+
+- TIMESTAMP
+  - 指要查询某个表在TIMESTAMP这个时间点上的数据，TIMESTAMP指一个具体的历史时间。
+- CSN
+  - 指要查询整个数据库逻辑提交序下某个CSN点的数据，CSN指一个具体逻辑提交时间点，数据库中的CSN为写一致性点，每个CSN代表整个数据库的一个一致性点，查询某个CSN下的数据代表SQL查询数据库在该一致性点的相关数据。
+
+### 使用示例
+
+- 示例1：
+
+  ```sql
+  SELECT * FROM t1 TIMECAPSULE TIMESTAMP to_timestamp ('2020-02-11 10:13:22.724718', 'YYYY-MM-DD HH24:MI:SS.FF');
+  ```
+
+- 示例2：
+
+  ```sql
+  SELECT * FROM t1 TIMECAPSULE CSN 9617;
+  ```
+
+- 示例3：
+
+  ```sql
+  SELECT * FROM t1 AS t TIMECAPSULE TIMESTAMP to_timestamp ('2020-02-11 10:13:22.724718', 'YYYY-MM-DD HH24:MI:SS.FF');
+  ```
+
+- 示例4：
+
+  ```sql
+  SELECT * FROM t1 AS t TIMECAPSULE CSN 9617;
+  ```
+
+## 闪回表
+
+### 背景信息
+
+闪回表可以将表恢复至特定时间点，当逻辑损坏仅限于一个或一组表，而不是整个数据库时，此特性可以快速恢复表的数据。闪回表基于MVCC多版本机制，通过删除指定时间点和该时间点之后的增量数据，并找回指定时间点和当前时间点删除的数据，实现表级数据还原。
+
+### 前提条件
+
+- undo_retention_time参数用于设置undo旧版本的保留时间。
+
+### 语法
+
+```ebnf+diagram
+FlashBack ::= TIMECAPSULE TABLE table_name TO { TIMESTAMP | CSN } expression
+```
+
+### 使用示例
+
+```sql
+TIMECAPSULE TABLE t1 TO TIMESTAMP to_timestamp ('2020-02-11 10:13:22.724718', 'YYYY-MM-DD HH24:MI:SS.FF');
+TIMECAPSULE TABLE t1 TO CSN 9617;
+```
+
+## 闪回DROP/TRUNCATE
+
+### 背景信息
+
+- 闪回DROP：可以恢复意外删除的表，从回收站（recycle bin）中恢复被删除的表及其附属结构如索引、表约束等。闪回drop是基于回收站机制，通过还原回收站中记录的表的物理文件，实现已drop表的恢复。
+
+- 闪回TRUNCATE：可以恢复误操作或意外被进行truncate的表，从回收站中恢复被truncate的表及索引的物理数据。闪回truncate基于回收站机制，通过还原回收站中记录的表的物理文件，实现已truncate表的恢复。
+
+### 前提条件
+
+- 开启enable_recyclebin参数，启用回收站。
+- recyclebin_retention_time参数用于设置回收站对象保留时间，超过该时间的回收站对象将被自动清理。
+
+### 相关语法
+
+- 删除表
+
+  ```ebnf+diagram
+  DropTable ::= DROP TABLE table_name [PURGE]
+  ```
+
+- 清理回收站对象
+
+  ```ebnf+diagram
+  PurgeRecyclebin ::= PURGE { TABLE { table_name }
+  | INDEX { index_name }
+  | RECYCLEBIN
+  }
+  ```
+
+- 闪回被删除的表
+
+  ```ebnf+diagram
+  TimecapsuleTable ::= TIMECAPSULE TABLE { table_name } TO BEFORE DROP [RENAME TO new_tablename]
+  ```
+
+- 截断表
+
+  ```ebnf+diagram
+  TruncateTable ::= TRUNCATE TABLE { table_name } [ PURGE ]
+  ```
+
+- 闪回截断的表
+
+  ```ebnf+diagram
+  TimecapsuleTable ::= TIMECAPSULE TABLE { table_name } TO BEFORE TRUNCATE
+  ```
+
+### 参数说明
+
+- DROP/TRUNCATE TABLE table_name PURGE
+  - 默认将表数据放入回收站中，PURGE直接清理。
+- PURGE RECYCLEBIN
+  - 表示清理回收站对象。
+- **TO BEFORE DROP**
+
+使用这个子句检索回收站中已删除的表及其子对象。
+
+可以指定原始用户指定的表的名称，或对象删除时数据库分配的系统生成名称。
+
+- 回收站中系统生成的对象名称是唯一的。因此，如果指定系统生成名称，那么数据库检索指定的对象。使用“select * from pg_recyclebin;”语句查看回收站中的内容。
+- 如果指定了用户指定的名称，且如果回收站中包含多个该名称的对象，然后数据库检索回收站中最近移动的对象。如果想要检索更早版本的表，你可以这样做：
+  - 指定你想要检索的表的系统生成名称。
+  - 执行TIMECAPSULE TABLE … TO BEFORE DROP语句，直到你要检索的表。
+  - 恢复DROP表时，只恢复基表名，其他子对象名均保持回收站对象名。用户可根据需要，执行DDL命令手工调整子对象名。
+  - 回收站对象不支持DML、DCL、DDL等写操作，不支持DQL查询操作（后续支持）。
+  - 闪回点和当前点之间，执行过修改表结构或影响物理结构的语句，闪回失败。涉及namespace、表名改变等操作的DDL执行闪回报错： ERROR: recycle object %s desired does not exis；增加/删除/切割/合成等分区改变等操作的DDL执行闪回报错： ERROR: relation %s does not exis；其他情况报错：“ERROR：The table definition of %s has been changed. ”。
+- **RENAME TO**
+
+为从回收站中检索的表指定一个新名称。
+
+- **TO BEFORE TRUNCATE**
+
+闪回到TRUNCATE之前。
+
+### 语法示例
+
+```sql
+DROP TABLE t1 PURGE;
+
+PURGE TABLE t1;
+PURGE TABLE "BIN$04LhcpndanfgMAAAAAANPw==$0";
+PURGE INDEX i1;
+PURGE INDEX "BIN$04LhcpndanfgMAAAAAANPw==$0";
+PURGE RECYCLEBIN;
+
+TIMECAPSULE TABLE t1 TO BEFORE DROP;
+TIMECAPSULE TABLE t1 TO BEFORE DROP RENAME TO new_t1;
+TIMECAPSULE TABLE "BIN$04LhcpndanfgMAAAAAANPw==$0" TO BEFORE DROP;
+TIMECAPSULE TABLE "BIN$04LhcpndanfgMAAAAAANPw==$0" TO BEFORE DROP RENAME TO new_t1;
+```
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/column-store-tables-management.md b/product/zh/docs-mogdb/v3.0/administrator-guide/column-store-tables-management.md
new file mode 100644
index 0000000000000000000000000000000000000000..54c4652f8412de0f9f47aa4496c89bb66e2c13a1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/column-store-tables-management.md
@@ -0,0 +1,401 @@
+---
+title: 列存表管理
+summary: 列存表管理
+author: Guo Huan
+date: 2021-04-06
+---
+
+# 列存表管理
+
+<br/>
+
+## 什么是列存储
+
+行存储是指将表按行存储到硬盘分区上，列存储是指将表按列存储到硬盘分区上。默认情况下，创建的表为行存储。行存储和列存储的差异请参见图1。
+
+**图 1** 行存储和列存储的差异
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/column-store-tables-management.png)
+
+上图中，左上为行存表，右上为行存表在硬盘上的存储方式。左下为列存表，右下为列存表在硬盘上的存储方式。从上图可以很清楚地看到，行式存储下一张表的数据都是放在一起的，但列式存储下都被分开保存了。
+
+<br/>
+
+## 行存表和列存表的优缺点及适用场景
+
+行、列存储有如下优缺点:
+
+| **存储模型** | **优点**   | **缺点**   |
+| :----------- | :--------------------| :-----------------------|
+| 行存         | 数据被保存在一起。INSERT/UPDATE容易。                                      | 选择(Selection)时即使只涉及某几列，所有数据也都会被读取。 |
+| 列存         | 查询时只有涉及到的列会被读取。投影(Projection)很高效。任何列都能作为索引。 | 选择完成时，被选择的列要重新组装。INSERT/UPDATE比较麻烦。 |
+
+一般情况下，如果表的字段比较多（大宽表），查询中涉及到的列不多的情况下，适合列存储。如果表的字段个数比较少，查询大部分字段，那么选择行存储比较好。
+
+| 存储类型 | 适用场景                                                                                        |
+| :------- | :----------------- |
+| 行存     | 点查询(返回记录少，基于索引的简单查询)。增、删、改操作较多的场景。                              |
+| 列存     | 统计分析类查询 (关联、分组操作较多的场景)。即席查询（查询条件不确定，行存表扫描难以使用索引）。 |
+
+MogDB支持行列混合存储。行、列存储模型各有优劣，建议根据实际情况选择。通常MogDB用于TP场景的数据库，默认使用行存储，仅对执行复杂查询且数据量大的AP场景时，才使用列存储。
+
+<br/>
+
+## 行存表和列存表的选择
+
+- 更新频繁程度
+
+    数据如果频繁更新，选择行存表。
+
+- 插入频繁程度
+
+    频繁的少量插入，选择行存表。
+
+- 表的列数
+
+    表的列数很多，选择列存表。
+
+- 查询的列数
+
+    如果每次查询时，只涉及了表的少数（<50%总列数）几个列，选择列存表。
+
+- 压缩率
+
+    列存表比行存表压缩率高。但高压缩率会消耗更多的CPU资源。
+
+<br/>
+
+## 列存表的限制
+
+- 列存表不支持数组。
+- 列存表的数量建议不超过1000个。
+- 列存表的表级约束只支持PARTIAL CLUSTER KEY，不支持主外键等表级约束。
+- 列存表的字段约束只支持NULL、NOT NULL和DEFAULT常量值。
+- 列存表不支持alter命令修改字段约束。
+- 列存表支持delta表，受参数enable_delta_store 控制是否开启，受参数deltarow_threshold控制进入delta表的阀值。
+
+<br/>
+
+## 列存相关参数
+
+- cstore_buffers
+
+    列存所使用的共享缓冲区的大小，默认值: 32768KB。
+
+- partition_mem_batch
+
+    指定缓存个数，为了优化对列存分区表的批量插入，在批量插入过程中会对数据进行缓存后再批量写盘。默认值: 256 。
+
+- partition_max_cache_size
+
+    指定数据缓存区大小，为了优化对列存分区表的批量插入，在批量插入过程中会对数据进行缓存后再批量写盘。默认值: 2GB。
+
+- enable_delta_store
+
+    为了增强列存单条数据导入的性能和解决磁盘冗余问题，是否需要开启列存delta表功能，与参数DELTAROW_THRESHOLD 配合使用。默认值: off。
+
+<br/>
+
+## 建表语法
+
+MogDB创建普通表默认是未压缩的行存表。
+
+```bash
+mogdb=# \dt
+No relations found.
+mogdb=# create table test_t(id serial primary key ,col1 varchar(8),col2 decimal(6,2),create_time timestamptz not null default now());
+NOTICE:  CREATE TABLE will create implicit sequence "test_t_id_seq" for serial column "test_t.id"
+NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index "test_t_pkey" for table "test_t"
+CREATE TABLE
+mogdb=# \dt+
+                                     List of relations
+ Schema |  Name  | Type  | Owner |  Size   |             Storage              | Description
+--------+--------+-------+-------+---------+----------------------------------+-------------
+ public | test_t | table | omm   | 0 bytes | {orientation=row,compression=no} |
+(1 row)
+
+mogdb=#
+```
+
+创建列存表，需要指定**orientation=column**，默认压缩级别是low。
+
+```sql
+mogdb=# create table column_t(id serial,col1 varchar(8),col2 decimal(6,2),create_time timestamptz not null default now()) with (orientation=column );
+NOTICE:  CREATE TABLE will create implicit sequence "column_t_id_seq" for serial column "column_t.id"
+CREATE TABLE
+mogdb=# \dt+
+                                        List of relations
+ Schema |   Name   | Type  | Owner |  Size   |               Storage                | Description
+--------+----------+-------+-------+---------+--------------------------------------+-------------
+ public | column_t | table | omm   | 16 kB   | {orientation=column,compression=low} |
+ public | test_t   | table | omm   | 0 bytes | {orientation=row,compression=no}     |
+(2 rows)
+
+mogdb=#
+mogdb=# \d+ column_t
+                                                        Table "public.column_t"
+   Column    |           Type           |                       Modifiers                       | Storage  | Stats target | Description
+-------------+--------------------------+-------------------------------------------------------+----------+--------------+-------------
+ id          | integer                  | not null default nextval('column_t_id_seq'::regclass) | plain    |              |
+ col1        | character varying(8)     |                                                       | extended |              |
+ col2        | numeric(6,2)             |                                                       | main     |              |
+ create_time | timestamp with time zone | not null default now()                                | plain    |              |
+Has OIDs: no
+Options: orientation=column, compression=low
+```
+
+列存表添加局部聚簇存储列。
+
+```sql
+mogdb=# \d+ column_t
+                                                        Table "public.column_t"
+   Column    |           Type           |                       Modifiers                       | Storage  | Stats target | Description
+-------------+--------------------------+-------------------------------------------------------+----------+--------------+-------------
+ id          | integer                  | not null default nextval('column_t_id_seq'::regclass) | plain    |              |
+ col1        | character varying(8)     |                                                       | extended |              |
+ col2        | numeric(6,2)             |                                                       | main     |              |
+ create_time | timestamp with time zone | not null default now()                                | plain    |              |
+Has OIDs: no
+Options: orientation=column, compression=low
+
+mogdb=# alter table column_t add PARTIAL CLUSTER KEY(id);
+ALTER TABLE
+mogdb=# \d+ column_t
+                                                        Table "public.column_t"
+   Column    |           Type           |                       Modifiers                       | Storage  | Stats target | Description
+-------------+--------------------------+-------------------------------------------------------+----------+--------------+-------------
+ id          | integer                  | not null default nextval('column_t_id_seq'::regclass) | plain    |              |
+ col1        | character varying(8)     |                                                       | extended |              |
+ col2        | numeric(6,2)             |                                                       | main     |              |
+ create_time | timestamp with time zone | not null default now()                                | plain    |              |
+Partial Cluster :
+    "column_t_cluster" PARTIAL CLUSTER KEY (id)
+Has OIDs: no
+Options: orientation=column, compression=low
+
+mogdb=#
+```
+
+直接创建带局部聚簇存储的列存表。
+
+```sql
+mogdb=# create table column_c(id serial,col1 varchar(8),col2 decimal(6,2),create_time timestamptz not null default now(),PARTIAL CLUSTER KEY(id)) with (orientation=column );
+NOTICE:  CREATE TABLE will create implicit sequence "column_c_id_seq" for serial column "column_c.id"
+CREATE TABLE
+mogdb=# \d+ column_c
+                                                        Table "public.column_c"
+   Column    |           Type           |                       Modifiers                       | Storage  | Stats target | Description
+-------------+--------------------------+-------------------------------------------------------+----------+--------------+-------------
+ id          | integer                  | not null default nextval('column_c_id_seq'::regclass) | plain    |              |
+ col1        | character varying(8)     |                                                       | extended |              |
+ col2        | numeric(6,2)             |                                                       | main     |              |
+ create_time | timestamp with time zone | not null default now()                                | plain    |              |
+Partial Cluster :
+    "column_c_cluster" PARTIAL CLUSTER KEY (id)
+Has OIDs: no
+Options: orientation=column, compression=low
+
+mogdb=#
+```
+
+有关列存表支持的数据类型，请参见参考指南&gt;支持的数据类型下的[列存表支持的数据类型](16-data-types-supported-by-column-store-tables).
+
+<br/>
+
+## 列存与行存对比
+
+**磁盘使用空间**
+
+- 列存表默认大小16K，low压缩级别。
+
+- 行存表默认大小0bytes，非压缩级别。
+
+- 分别向两个表中插入100万条数据，占用磁盘大小对比。
+
+    ```sql
+    mogdb=# \dt+
+                                          List of relations
+    Schema |   Name    | Type  | Owner |  Size   |                 Storage                 | Description
+    --------+-----------+-------+-------+---------+-----------------------------------------+-------------
+    public | column_t  | table | omm   | 16 kB   | {orientation=column,compression=low}    |
+    public | column_th | table | omm   | 16 kB   | {orientation=column,compression=high}   |
+    public | column_tm | table | omm   | 16 kB   | {orientation=column,compression=middle} |
+    public | row_tc    | table | omm   | 0 bytes | {orientation=row,compression=yes}       |
+    public | test_t    | table | omm   | 0 bytes | {orientation=row,compression=no}        |
+    (5 rows)
+    mogdb=# insert into column_t select generate_series(1,1000000),left(md5(random()::text),8),random()::numeric(6,2);
+    INSERT 0 1000000
+    Time: 11328.880 ms
+    mogdb=# insert into column_th select generate_series(1,1000000),left(md5(random()::text),8),random()::numeric(6,2);
+    INSERT 0 1000000
+    Time: 10188.634 ms
+    mogdb=# insert into column_tm select generate_series(1,1000000),left(md5(random()::text),8),random()::numeric(6,2);
+    INSERT 0 1000000
+    Time: 9802.739 ms
+    mogdb=# insert into test_t select generate_series(1,1000000),left(md5(random()::text),8),random()::numeric(6,2);
+    INSERT 0 1000000
+    Time: 17404.945 ms
+    mogdb=# insert into row_tc select generate_series(1,1000000),left(md5(random()::text),8),random()::numeric(6,2);
+    INSERT 0 1000000
+    Time: 12394.866 ms
+    mogdb=# \dt+
+                                           List of relations
+    Schema |   Name    | Type  | Owner |   Size   |                 Storage                 | Description
+    --------+-----------+-------+-------+----------+-----------------------------------------+-------------
+    public | column_t  | table | omm   | 12 MB    | {orientation=column,compression=low}    |
+    public | column_th | table | omm   | 8304 kB  | {orientation=column,compression=high}   |
+    public | column_tm | table | omm   | 10168 kB | {orientation=column,compression=middle} |
+    public | row_tc    | table | omm   | 58 MB    | {orientation=row,compression=yes}       |
+    public | test_t    | table | omm   | 58 MB    | {orientation=row,compression=no}        |
+    (5 rows)
+    mogdb=#
+    ```
+
+- 列存表开启的压缩级别越高，占用磁盘空间越少。
+
+- 行存表开启压缩后，磁盘空间大小占比减少不明显。
+
+- 列存表占用磁盘空间比行存表占用磁盘空间少近6倍。
+
+**DML对比**
+
+查找单列:
+
+```sql
+---
+---按范围查找，列存比行存快近20倍
+---
+mogdb=# select col1 from test_t where id>=100010 and id<100020;
+   col1
+----------
+ 4257a3f3
+ 3d397284
+ 64343438
+ 6eb7bdb7
+ d1c9073d
+ 6aeb037c
+ 1d424974
+ 223235ab
+ 329de235
+ 2f02adc1
+(10 rows)
+
+Time: 77.341 ms
+mogdb=# select col1 from column_t where id>=100010 and id<100020;
+   col1
+----------
+ d4837c30
+ 87a46f7a
+ 2f42a9c9
+ 4481c793
+ 68800204
+ 613b9205
+ 9d8f4a0a
+ 5cc4ff9e
+ f948cd10
+ f2775cee
+(10 rows)
+
+Time: 3.884 ms
+
+---
+---随机查找，列存比行存快近35倍
+---
+
+mogdb=# select col1 from test_t limit 10;
+   col1
+----------
+ c2780d93
+ 294be14d
+ 4e53b761
+ 2c10f8a2
+ ae776743
+ 7d683c66
+ b3b40054
+ 7e56edf9
+ a7b7336e
+ ea3d47d9
+(10 rows)
+
+Time: 249.887 ms
+mogdb=# select col1 from column_t limit 10;
+   col1
+----------
+ a745d77b
+ 4b6df494
+ 76fed9c1
+ 70c9664d
+ 3384de8a
+ 4158f3bf
+ 5d1c3b9f
+ 341876bb
+ f396f4ed
+ abfd78bb
+(10 rows)
+
+Time: 7.738 ms
+```
+
+查找全部数据:
+
+```sql
+---
+---行存比列存查询快30%
+---
+mogdb=# select * from test_t limit 10;
+ id |   col1   | col2 |          create_time
+----+----------+------+-------------------------------
+  1 | c2780d93 |  .37 | 2020-10-26 14:27:33.304108+08
+  2 | 294be14d |  .57 | 2020-10-26 14:27:33.304108+08
+  3 | 4e53b761 |  .98 | 2020-10-26 14:27:33.304108+08
+  4 | 2c10f8a2 |  .27 | 2020-10-26 14:27:33.304108+08
+  5 | ae776743 |  .97 | 2020-10-26 14:27:33.304108+08
+  6 | 7d683c66 |  .58 | 2020-10-26 14:27:33.304108+08
+  7 | b3b40054 |  .44 | 2020-10-26 14:27:33.304108+08
+  8 | 7e56edf9 |  .43 | 2020-10-26 14:27:33.304108+08
+  9 | a7b7336e |  .31 | 2020-10-26 14:27:33.304108+08
+ 10 | ea3d47d9 |  .42 | 2020-10-26 14:27:33.304108+08
+(10 rows)
+
+Time: 6.822 ms
+
+mogdb=# select * from column_t limit 10;
+ id |   col1   | col2 |          create_time
+----+----------+------+-------------------------------
+  1 | a745d77b |  .33 | 2020-10-26 14:28:20.633253+08
+  2 | 4b6df494 |  .42 | 2020-10-26 14:28:20.633253+08
+  3 | 76fed9c1 |  .73 | 2020-10-26 14:28:20.633253+08
+  4 | 70c9664d |  .74 | 2020-10-26 14:28:20.633253+08
+  5 | 3384de8a |  .48 | 2020-10-26 14:28:20.633253+08
+  6 | 4158f3bf |  .59 | 2020-10-26 14:28:20.633253+08
+  7 | 5d1c3b9f |  .63 | 2020-10-26 14:28:20.633253+08
+  8 | 341876bb |  .97 | 2020-10-26 14:28:20.633253+08
+  9 | f396f4ed |  .73 | 2020-10-26 14:28:20.633253+08
+ 10 | abfd78bb |  .30 | 2020-10-26 14:28:20.633253+08
+(10 rows)
+
+Time: 9.982 ms
+```
+
+更新数据:
+
+```sql
+---
+---直接更新一个字段，列存比行存快近7倍
+---
+mogdb=# update test_t set col1=col1;
+UPDATE 1000000
+Time: 19779.978 ms
+mogdb=# update column_t set col1=col1;
+UPDATE 1000000
+Time: 2702.339 ms
+```
+
+<br/>
+
+## 总结
+
+1. 列存表比行存表在磁盘空间占用上节省近6倍。
+2. 查询指定字段，列存表比行存表快约20-35倍。
+3. select * 的方式，列存表比行存表慢30%。
+4. 默认压缩方式批量导入数据，列存表比行存表快40%。
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/exporting-data/1-using-gs_dump-and-gs_dumpall-to-export-data-overview.md b/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/exporting-data/1-using-gs_dump-and-gs_dumpall-to-export-data-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..fc3a7de573515e01c12a8951f34379f82a2f223a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/exporting-data/1-using-gs_dump-and-gs_dumpall-to-export-data-overview.md
@@ -0,0 +1,91 @@
+---
+title: 使用gs_dump和gs_dumpall命令导出数据概述
+summary: 使用gs_dump和gs_dumpall命令导出数据概述
+author: Guo Huan
+date: 2021-03-04
+---
+
+# 使用gs_dump和gs_dumpall命令导出数据概述
+
+MogDB提供的gs_dump和gs_dumpall工具，能够帮助用户导出需要的数据库对象或其相关信息。通过导入工具将导出的数据信息导入至需要的数据库，可以完成数据库信息的迁移。gs_dump支持导出单个数据库或其内的对象，而gs_dumpall支持导出MogDB中所有数据库或各库的公共全局对象。详细的使用场景见[表1](#适用场景)。
+
+**表 1** 适用场景<a id="适用场景"> </a>
+
+<table>
+    <tr>
+        <th>适用场景</th>
+        <th>支持的导出粒度</th>
+        <th>支持的导出格式</th>
+        <th>配套的导入方法</th>
+    </tr>
+    <tr>
+        <td rowspan="3">导出单个数据库</td>
+        <td>数据库级导出。<br/>
+            - 导出全量信息。<br/>使用导出的全量信息可以创建一个与当前库相同的数据库，且库中数据也与当前库相同。<br/>
+            - 仅导出库中所有对象的定义，包含库定义、函数定义、模式定义、表定义、索引定义和存储过程定义等。<br/>
+            使用导出的对象定义，可以快速创建一个相同的数据库，但是库中并无原数据库的数据。<br/>
+            - 仅导出数据。</td>
+        <td rowspan="3">
+            - 纯文本格式<br/>
+            - 自定义归档格式<br/>
+            - 目录归档格式<br/>
+            - tar归档格式
+        </td>
+        <td rowspan="3">
+            - 纯文本格式数据文件导入请参见使用gsql元命令导入数据。<br/>
+            - 自定义归档格式、目录归档格式和tar归档格式数据文件导入请参见使用gs_restore命令导入数据。</td>
+    </tr>
+    <tr>
+        <td>模式级导出。<br/>
+            - 导出模式的全量信息。<br/>
+            - 仅导出模式中数据。<br/>
+            - 仅导出对象的定义，包含表定义、存储过程定义和索引定义等。
+        </td>
+    </tr>
+    <tr>
+        <td>表级导出。<br/>
+            - 导出表的全量信息。<br/>
+            - 仅导出表中数据。<br/>
+            - 仅导出表的定义。
+        </td>
+    </tr>
+    <tr>
+        <td rowspan="2">导出所有数据库</td>
+        <td>数据库级导出。<br/>
+            - 导出全量信息。<br/>使用导出的全量信息可以创建与当前主机相同的一个主机环境，拥有相同数据库和公共全局对象，且库中数据也与当前各库相同。<br/>
+            - 仅导出各数据库中的对象定义，包含表空间、库定义、函数定义、模式定义、表定义、索引定义和存储过程定义等。<br/>
+            使用导出的对象定义，可以快速创建与当前主机相同的一个主机环境，拥有相同的数据库和表空间，但是库中并无原数据库的数据。<br/>
+            - 仅导出数据。</td>
+        <td rowspan="2">纯文本格式</td>
+        <td rowspan="2">数据文件导入请参见使用gsql元命令导入数据。</td>
+    </tr>
+    <tr>
+        <td>各库公共全局对象导出。<br/>
+- 仅导出表空间信息。<br/>
+- 仅导出角色信息。<br/>
+- 导出角色与表空间。</td>
+    </tr>
+</table>
+
+gs_dump和gs_dumpall通过-U指定执行导出的用户帐户。如果当前使用的帐户不具备导出所要求的权限时，会无法导出数据。此时，可在导出命令中设置-role参数来指定具备权限的角色。在执行命令后，gs_dump和gs_dumpall会使用-role参数指定的角色，完成导出动作。可使用该功能的场景请参见[表1](#适用场景)，详细操作请参见[无权限角色导出数据](4-data-export-by-a-user-without-required-permissions)。
+
+gs_dump和gs_dumpall通过对导出的数据文件加密，导入时对加密的数据文件进行解密，可以防止数据信息泄露，为数据库的安全提供保证。注意，使用gs_dump加密的纯文本格式文件，如果导出的数据库中包含存储过程，不支持使用gsql命令恢复文件，请使用另外三种模式导出数据库，并使用gs_restore恢复。
+
+gs_dump和gs_dumpall工具在进行数据导出时，其他用户可以访问数据库（读或写）。
+
+gs_dump和gs_dumpall工具支持导出完整一致的数据。例如，T1时刻启动gs_dump导出A数据库，或者启动gs_dumpall导出MogDB数据库，那么导出数据结果将会是T1时刻A数据库或者该MogDB数据库的数据状态，T1时刻之后对A数据库或MogDB数据库的修改不会被导出。
+
+**注意事项**
+
+- 禁止修改导出的文件和内容，否则可能无法恢复成功。
+
+- 如果数据库中包含的对象数量（数据表、视图、索引）在50万以上，为了提高性能且避免出现内存问题，建议通过gs_guc工具设置数据库节点的如下参数（如果参数值大于如下建议值，则无需设置）。
+
+    ```bash
+    gs_guc set -N all -I all -c 'max_prepared_transactions = 1000'
+    gs_guc set -N all -I all -c 'max_locks_per_transaction = 512'
+    ```
+
+- 为了保证数据一致性和完整性，导出工具会对需要转储的表设置共享锁。如果表在别的事务中设置了共享锁，gs_dump和gs_dumpall会等待锁释放后锁定表。如果无法在指定时间内锁定某个表，转储会失败。用户可以通过指定-lock-wait-timeout选项，自定义等待锁超时时间。
+
+- 由于gs_dumpall读取所有数据库中的表，因此必须以MogDB管理员身份进行连接，才能导出完整文件。在使用gsql执行脚本文件导入时，同样需要管理员权限，以便添加用户和组，以及创建数据库。
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/exporting-data/2-exporting-a-single-database.md b/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/exporting-data/2-exporting-a-single-database.md
new file mode 100644
index 0000000000000000000000000000000000000000..0ee53b4a21e255ecd97f4200acd7763172b3d8bd
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/exporting-data/2-exporting-a-single-database.md
@@ -0,0 +1,305 @@
+---
+title: 导出单个数据库
+summary: 导出单个数据库
+author: Guo Huan
+date: 2021-03-04
+---
+
+# 导出单个数据库
+
+<br/>
+
+## 导出数据库
+
+MogDB支持使用gs_dump工具导出某个数据库级的内容，包含数据库的数据和所有对象定义。可根据需要自定义导出如下信息:
+
+- 导出数据库全量信息，包含数据和所有对象定义。
+
+    使用导出的全量信息可以创建一个与当前库相同的数据库，且库中数据也与当前库相同。
+
+- 仅导出所有对象定义，包括: 库定义、函数定义、模式定义、表定义、索引定义和存储过程定义等。
+
+    使用导出的对象定义，可以快速创建一个相同的数据库，但是库中并无原数据库的数据。
+
+- 仅导出数据，不包含所有对象定义。
+
+<br/>
+
+### 操作步骤
+
+1. 以操作系统用户omm登录数据库主节点。
+
+2. 使用gs_dump导出userdatabase数据库。
+
+    ```bash
+    gs_dump -U jack -f /home/omm/backup/userdatabase_backup.tar -p 8000 postgres -F t
+    ```
+
+    **表 1** 常用参数说明
+
+    | 参数   | 参数说明        | 举例      |
+    | :------- | :------------------------------------ | :----------------------|
+    | -U     | 连接数据库的用户名。<br/>- 说明:<br/>不指定连接数据库的用户名时，默认以安装时创建的初始系统管理员连接。                   | -U jack    |
+    | -W     | 指定用户连接的密码。<br/>- 如果主机的认证策略是trust，则不会对数据库管理员进行密码验证，即无需输入-W选项；<br/>- 如果没有-W选项，并且不是数据库管理员，会提示用户输入密码。 | -W abcd@123                   |
+    | -f     | 将导出文件发送至指定目录文件夹。如果这里省略，则使用标准输出。           | -f /home/omm/backup/**postgres**_backup.tar |
+    | -p     | 指定服务器所监听的TCP端口或本地Unix域套接字后缀，以确保连接。            | -p 8000          |
+    | dbname | 需要导出的数据库名称        | postgres         |
+    | -F     | 选择导出文件格式。-F参数值如下: <br/>- p: 纯文本格式<br/>- c: 自定义归档<br/>- d: 目录归档格式<br/>- t: tar归档格式       | -F t    |
+
+    其他参数说明请参见《参考指南》中“工具参考 > 服务端工具 > [gs_dump](5-gs_dump)”章节。
+
+<br/>
+
+### 示例
+
+示例一: 执行gs_dump，导出postgres数据库全量信息，导出文件格式为sql文本格式。
+
+```bash
+gs_dump -f /home/omm/backup/postgres_backup.sql -p 8000 postgres -F p
+Password:
+gs_dump[port='8000'][postgres][2017-07-21 15:36:13]: dump database postgres successfully
+gs_dump[port='8000'][postgres][2017-07-21 15:36:13]: total time: 3793  ms
+```
+
+示例二: 执行gs_dump，仅导出postgres数据库中的数据，不包含数据库对象定义，导出文件格式为自定义归档格式。
+
+```bash
+gs_dump -f /home/omm/backup/postgres_data_backup.dmp -p 8000 postgres -a -F c
+Password:
+gs_dump[port='8000'][postgres][2017-07-21 15:36:13]: dump database postgres successfully
+gs_dump[port='8000'][postgres][2017-07-21 15:36:13]: total time: 3793  ms
+```
+
+示例三: 执行gs_dump，仅导出postgres数据库所有对象的定义，导出文件格式为sql文本格式。
+
+```bash
+gs_dump  -f /home/omm/backup/postgres_def_backup.sql -p 8000 postgres -s -F p
+Password:
+gs_dump[port='8000'][postgres][2017-07-20 15:04:14]: dump database postgres successfully
+gs_dump[port='8000'][postgres][2017-07-20 15:04:14]: total time: 472 ms
+```
+
+示例四: 执行gs_dump，仅导出postgres数据库的所有对象的定义，导出文件格式为文本格式，并对导出文件进行加密。
+
+```bash
+gs_dump -f /home/omm/backup/postgres_def_backup.sql -p 8000 postgres --with-encryption AES128 --with-key 1234567812345678 -s -F p
+Password:
+gs_dump[port='8000'][postgres][2018-11-14 11:25:18]: dump database postgres successfully
+gs_dump[port='8000'][postgres][2018-11-14 11:25:18]: total time: 1161  ms
+```
+
+<br/>
+
+## 导出模式
+
+MogDB目前支持使用gs_dump工具导出模式级的内容，包含模式的数据和定义。用户可通过灵活的自定义方式导出模式内容，不仅支持选定一个模式或多个模式的导出，还支持排除一个模式或者多个模式的导出。可根据需要自定义导出如下信息:
+
+- 导出模式全量信息，包含数据和对象定义。
+- 仅导出数据，即模式包含表中的数据，不包含对象定义。
+- 仅导出模式对象定义，包括: 表定义、存储过程定义和索引定义等。
+
+<br/>
+
+### 操作步骤
+
+1. 以操作系统用户omm登录数据库主节点。
+
+2. 使用gs_dump同时导出hr和public模式。
+
+    ```bash
+    gs_dump -W Bigdata@123 -U jack -f /home/omm/backup/MPPDB_schema_backup -p 8000 human_resource -n hr -n public -F d
+    ```
+
+    **表 1** 常用参数说明
+
+    | 参数   | 参数说明        | 举例      |
+    | :------- | :------------------------------ | :----------------------|
+    | -U     | 连接数据库的用户名。        | -U jack         |
+    | -W     | 指定用户连接的密码。<br/>- 如果主机的认证策略是trust，则不会对数据库管理员进行密码验证，即无需输入-W选项。<br/>- 如果没有-W选项，并且不是数据库管理员，会提示用户输入密码。 | -W Bigdata@123  |
+    | -f     | 将导出文件发送至指定目录文件夹。如果这里省略，则使用标准输出。    | -f /home/omm/backup/MPPDB*_*schema_backup         |
+    | -p     | 指定服务器所监听的TCP端口或本地Unix域套接字后缀，以确保连接。     | -p 8000         |
+    | dbname | 需要导出的数据库名称        | human_resource  |
+    | -n     | 只导出与模式名称匹配的模式，此选项包括模式本身和所有它包含的对象。<br/>- 单个模式: -n **schemaname**<br/>- 多个模式: 多次输入-n **schemaname**        | - 单个模式: -n hr<br/>- 多个模式: -n hr -n public |
+    | -F     | 选择导出文件格式。-F参数值如下: <br/>- p: 纯文本格式<br/>- c: 自定义归档<br/>- d: 目录归档格式<br/>- t: tar归档格式       | -F d            |
+
+    其他参数说明请参见《参考指南》中“工具参考 > 服务端工具 > [gs_dump](5-gs_dump)”章节。
+
+<br/>
+
+### 示例
+
+示例一: 执行gs_dump，导出hr模式全量信息，导出文件格式为文本格式。
+
+```bash
+gs_dump -W Bigdata@123 -f /home/omm/backup/MPPDB_schema_backup.sql -p 8000 human_resource -n hr -F p
+gs_dump[port='8000'][human_resource][2017-07-21 16:05:55]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2017-07-21 16:05:55]: total time: 2425  ms
+```
+
+示例二: 执行gs_dump，仅导出hr模式的数据，导出文件格式为tar归档格式。
+
+```bash
+gs_dump -W Bigdata@123 -f /home/omm/backup/MPPDB_schema_data_backup.tar -p 8000 human_resource -n hr -a -F t
+gs_dump[port='8000'][human_resource][2018-11-14 15:07:16]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2018-11-14 15:07:16]: total time: 1865  ms
+```
+
+示例三: 执行gs_dump，仅导出hr模式的定义，导出文件格式为目录归档格式。
+
+```bash
+gs_dump -W Bigdata@123 -f /home/omm/backup/MPPDB_schema_def_backup -p 8000 human_resource -n hr -s -F d
+gs_dump[port='8000'][human_resource][2018-11-14 15:11:34]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2018-11-14 15:11:34]: total time: 1652  ms
+```
+
+示例四: 执行gs_dump，导出human_resource数据库时，排除hr模式，导出文件格式为自定义归档格式。
+
+```bash
+gs_dump -W Bigdata@123 -f /home/omm/backup/MPPDB_schema_backup.dmp -p 8000 human_resource -N hr -F c
+gs_dump[port='8000'][human_resource][2017-07-21 16:06:31]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2017-07-21 16:06:31]: total time: 2522  ms
+```
+
+示例五: 执行gs_dump，同时导出hr和public模式，且仅导出模式定义，导出文件格式为tar归档格式。
+
+```bash
+gs_dump -W Bigdata@123 -f /home/omm/backup/MPPDB_schema_backup1.tar -p 8000 human_resource -n hr -n public -s -F t
+gs_dump[port='8000'][human_resource][2017-07-21 16:07:16]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2017-07-21 16:07:16]: total time: 2132  ms
+```
+
+示例六: 执行gs_dump，导出human_resource数据库时，排除hr和public模式，导出文件格式为自定义归档格式。
+
+```bash
+gs_dump -W Bigdata@123 -f /home/omm/backup/MPPDB_schema_backup2.dmp -p 8000 human_resource -N hr -N public -F c
+gs_dump[port='8000'][human_resource][2017-07-21 16:07:55]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2017-07-21 16:07:55]: total time: 2296  ms
+```
+
+示例七: 执行gs_dump，导出public模式下所有表（视图、序列和外表）和hr模式中staffs表，包含数据和表定义，导出文件格式为自定义归档格式。
+
+```bash
+gs_dump -W Bigdata@123 -f /home/omm/backup/MPPDB_backup3.dmp -p 8000 human_resource -t public.* -t hr.staffs -F c
+gs_dump[port='8000'][human_resource][2018-12-13 09:40:24]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2018-12-13 09:40:24]: total time: 896  ms
+```
+
+<br/>
+
+## 导出表
+
+MogDB支持使用gs_dump工具导出表级的内容，包含表定义和表数据。视图、序列和外表属于特殊的表。用户可通过灵活的自定义方式导出表内容，不仅支持选定一个表或多个表的导出，还支持排除一个表或者多个表的导出。可根据需要自定义导出如下信息:
+
+- 导出表全量信息，包含表数据和表定义。
+- 仅导出数据，不包含表定义。
+- 仅导出表定义。
+
+<br/>
+
+### 操作步骤
+
+1. 以操作系统用户omm登录数据库主节点。
+
+2. 使用gs_dump同时导出指定表hr.staffs和hr.employments。
+
+    ```bash
+    gs_dump -W Bigdata@123 -U jack -f /home/omm/backup/MPPDB_table_backup -p 8000 human_resource -t hr.staffs -t hr.employments -F d
+    ```
+
+    **表 1** 常用参数说明
+
+    | 参数   | 参数说明                                                     | 举例                                                         |
+    | :----- | :----------------------------------------------------------- | :----------------------------------------------------------- |
+    | -U     | 连接数据库的用户名。                                         | -U jack                                                      |
+    | -W     | 指定用户连接的密码。<br/>- 如果主机的认证策略是trust，则不会对数据库管理员进行密码验证，即无需输入-W选项。<br/>- 如果没有-W选项，并且不是数据库管理员，会提示用户输入密码。 | -W Bigdata@123                                               |
+    | -f     | 将导出文件发送至指定目录文件夹。如果这里省略，则使用标准输出。 | -f /home/omm/backup/   MPPDB_table_backup                    |
+    | -p     | 指定服务器所监听的TCP端口或本地Unix域套接字后缀，以确保连接。 | -p 8000                                                      |
+    | dbname | 需要导出的数据库名称。                                       | human_resource                                               |
+    | -t     | 指定导出的表（或视图、序列、外表），可以使用多个-t选项来选择多个表，也可以使用通配符指定多个表对象。当使用通配符指定多个表对象时，注意给pattern打引号，防止shell扩展通配符。<br/>- 单个表: -t **schema.table**<br/>- 多个表: 多次输入-t **schema.table** | - 单个表: -t   hr.staffs<br/>- 多个表: -t hr.staffs -t hr.employments |
+    | -F     | 选择导出文件格式。-F参数值如下: <br/>- p: 纯文本格式<br/>- c: 自定义归档<br/>- d: 目录归档格式<br/>- t: tar归档格式 | -F d                                                         |
+
+    其他参数说明请参见《参考指南》中“工具参考 > 服务端工具 > [gs_dump](5-gs_dump)”章节。
+
+<br/>
+
+### 示例
+
+示例一: 执行gs_dump，导出表hr.staffs的定义和数据，导出文件格式为文本格式。
+
+```bash
+gs_dump -W Bigdata@123 -f /home/omm/backup/MPPDB_table_backup.sql -p 8000 human_resource -t hr.staffs -F p
+gs_dump[port='8000'][human_resource][2017-07-21 17:05:10]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2017-07-21 17:05:10]: total time: 3116  ms
+```
+
+示例二: 执行gs_dump，只导出表hr.staffs的数据，导出文件格式为tar归档格式。
+
+```bash
+gs_dump -W Bigdata@123 -f /home/omm/backup/MPPDB_table_data_backup.tar -p 8000 human_resource -t hr.staffs -a -F t
+gs_dump[port='8000'][human_resource][2017-07-21 17:04:26]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2017-07-21 17:04:26]: total time: 2570  ms
+```
+
+示例三: 执行gs_dump，导出表hr.staffs的定义，导出文件格式为目录归档格式。
+
+```bash
+gs_dump -W Bigdata@123 -f /home/omm/backup/MPPDB_table_def_backup -p 8000 human_resource -t hr.staffs -s -F d
+gs_dump[port='8000'][human_resource][2017-07-21 17:03:09]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2017-07-21 17:03:09]: total time: 2297  ms
+```
+
+示例四: 执行gs_dump，不导出表hr.staffs，导出文件格式为自定义归档格式。
+
+```bash
+gs_dump -W Bigdata@123 -f /home/omm/backup/MPPDB_table_backup4.dmp -p 8000 human_resource -T hr.staffs -F c
+gs_dump[port='8000'][human_resource][2017-07-21 17:14:11]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2017-07-21 17:14:11]: total time: 2450  ms
+```
+
+示例五: 执行gs_dump，同时导出两个表hr.staffs和hr.employments，导出文件格式为文本格式。
+
+```bash
+gs_dump -W Bigdata@123 -f /home/omm/backup/MPPDB_table_backup1.sql -p 8000 human_resource -t hr.staffs -t hr.employments -F p
+gs_dump[port='8000'][human_resource][2017-07-21 17:19:42]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2017-07-21 17:19:42]: total time: 2414  ms
+```
+
+示例六: 执行gs_dump，导出时，排除两个表hr.staffs和hr.employments，导出文件格式为文本格式。
+
+```bash
+gs_dump -W Bigdata@123 -f /home/omm/backup/MPPDB_table_backup2.sql -p 8000 human_resource -T hr.staffs -T hr.employments -F p
+gs_dump[port='8000'][human_resource][2017-07-21 17:21:02]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2017-07-21 17:21:02]: total time: 3165  ms
+```
+
+示例七: 执行gs_dump，导出表hr.staffs的定义和数据，只导出表hr.employments的定义，导出文件格式为tar归档格式。
+
+```bash
+gs_dump -W Bigdata@123 -f /home/omm/backup/MPPDB_table_backup3.tar -p 8000 human_resource -t hr.staffs -t hr.employments --exclude-table-data hr.employments -F t
+gs_dump[port='8000'][human_resource][2018-11-14 11:32:02]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2018-11-14 11:32:02]: total time: 1645  ms
+```
+
+示例八: 执行gs_dump，导出表hr.staffs的定义和数据，并对导出文件进行加密，导出文件格式为文本格式。
+
+```bash
+gs_dump -W Bigdata@123 -f /home/omm/backup/MPPDB_table_backup4.sql -p 8000 human_resource -t hr.staffs --with-encryption AES128 --with-key abcdefg_?1234567 -F p
+gs_dump[port='8000'][human_resource][2018-11-14 11:35:30]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2018-11-14 11:35:30]: total time: 6708  ms
+```
+
+示例九: 执行gs_dump，导出public模式下所有表（包括视图、序列和外表）和hr模式中staffs表，包含数据和表定义，导出文件格式为自定义归档格式。
+
+```bash
+gs_dump -W Bigdata@123 -f /home/omm/backup/MPPDB_table_backup5.dmp -p 8000 human_resource -t public.* -t hr.staffs -F c
+gs_dump[port='8000'][human_resource][2018-12-13 09:40:24]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2018-12-13 09:40:24]: total time: 896  ms
+```
+
+示例十:  执行gs_dump，仅导出依赖于t1模式下的test1表对象的视图信息，导出文件格式为目录归档格式。
+
+```bash
+gs_dump -W Bigdata@123 -U jack -f /home/omm/backup/MPPDB_view_backup6 -p 8000 human_resource -t t1.test1 --include-depend-objs --exclude-self -F d
+gs_dump[port='8000'][jack][2018-11-14 17:21:18]: dump database human_resource successfully
+gs_dump[port='8000'][jack][2018-11-14 17:21:23]: total time: 4239  ms
+```
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/exporting-data/3-exporting-all-databases.md b/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/exporting-data/3-exporting-all-databases.md
new file mode 100644
index 0000000000000000000000000000000000000000..5559608e6c7f45f18ea9ea02c614d19eb43adeb5
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/exporting-data/3-exporting-all-databases.md
@@ -0,0 +1,133 @@
+---
+title: 导出所有数据库
+summary: 导出所有数据库
+author: Guo Huan
+date: 2021-03-04
+---
+
+# 导出所有数据库
+
+<br/>
+
+## 导出所有数据库
+
+MogDB支持使用gs_dumpall工具导出所有数据库的全量信息，包含MogDB中每个数据库信息和公共的全局对象信息。可根据需要自定义导出如下信息:
+
+- 导出所有数据库全量信息，包含MogDB中每个数据库信息和公共的全局对象信息（包含角色和表空间信息）。
+
+    使用导出的全量信息可以创建与当前主机相同的一个主机环境，拥有相同数据库和公共全局对象，且库中数据也与当前各库相同。
+
+- 仅导出数据，即导出每个数据库中的数据，且不包含所有对象定义和公共的全局对象信息。
+
+- 仅导出所有对象定义，包括: 表空间、库定义、函数定义、模式定义、表定义、索引定义和存储过程定义等。
+
+    使用导出的对象定义，可以快速创建与当前主机相同的一个主机环境，拥有相同的数据库和表空间，但是库中并无原数据库的数据。
+
+<br/>
+
+### 操作步骤
+
+1. 以操作系统用户omm登录数据库主节点。
+
+2. 使用gs_dumpall一次导出所有数据库信息。
+
+    ```bash
+    gs_dumpall -W Bigdata@123 -U omm -f /home/omm/backup/MPPDB_backup.sql -p 8000
+    ```
+
+    **表 1** 常用参数说明
+
+    | 参数   | 参数说明        | 举例      |
+    | :------- | :----------------------------------------------------------------- | :----------------------|
+    | -U   | 连接数据库的用户名，需要是MogDB管理员用户。                                                                                                                                 | -U omm                               |
+    | -W   | 指定用户连接的密码。<br/>- 如果主机的认证策略是trust，则不会对数据库管理员进行密码验证，即无需输入-W选项；<br/>- 如果没有-W选项，并且不是数据库管理员，会提示用户输入密码。 | -W Bigdata@123                       |
+    | -f   | 将导出文件发送至指定目录文件夹。如果这里省略，则使用标准输出。                                                                                                              | -f /home/omm/backup/MPPDB_backup.sql |
+    | -p   | 指定服务器所监听的TCP端口或本地Unix域套接字后缀，以确保连接。                                                                                                               | -p 8000                              |
+
+    其他参数说明请参见《参考指南》中“工具参考 > 服务端工具 > [gs_dumpall](6-gs_dumpall)”章节。
+
+<br/>
+
+### 示例
+
+示例一: 执行gs_dumpall，导出所有数据库全量信息（omm用户为管理员用户），导出文件为文本格式。执行命令后，会有很长的打印信息，最终出现total time即代表执行成功。示例中将不体现中间的打印信息。
+
+```bash
+gs_dumpall -W Bigdata@123 -U omm -f /home/omm/backup/MPPDB_backup.sql -p 8000
+gs_dumpall[port='8000'][2017-07-21 15:57:31]: dumpall operation successful
+gs_dumpall[port='8000'][2017-07-21 15:57:31]: total time: 9627  ms
+```
+
+示例二: 执行gs_dumpall，仅导出所有数据库定义（omm用户为管理员用户），导出文件为文本格式。执行命令后，会有很长的打印信息，最终出现total time即代表执行成功。示例中将不体现中间的打印信息。
+
+```bash
+gs_dumpall -W Bigdata@123 -U omm -f /home/omm/backup/MPPDB_backup.sql -p 8000 -s
+gs_dumpall[port='8000'][2018-11-14 11:28:14]: dumpall operation successful
+gs_dumpall[port='8000'][2018-11-14 11:28:14]: total time: 4147  ms
+```
+
+示例三: 执行gs_dumpall，仅导出所有数据库中数据，并对导出文件进行加密，导出文件为文本格式。执行命令后，会有很长的打印信息，最终出现total time即代表执行成功。示例中将不体现中间的打印信息。
+
+```bash
+gs_dumpall -f /home/omm/backup/MPPDB_backup.sql -p 8000 -a --with-encryption AES128 --with-key 1234567812345678
+gs_dumpall[port='8000'][2018-11-14 11:32:26]: dumpall operation successful
+gs_dumpall[port='8000'][2018-11-14 11:23:26]: total time: 4147  ms
+```
+
+<br/>
+
+## 导出全局对象
+
+MogDB支持使用gs_dumpall工具导出所有数据库公共的全局对象，包含数据库用户和组，表空间及属性（例如: 适用于数据库整体的访问权限）信息。
+
+<br/>
+
+### 操作步骤
+
+1. 以操作系统用户omm登录数据库主节点。
+
+2. 使用gs_dumpall导出表空间对象信息。
+
+    ```bash
+    gs_dumpall -W Bigdata@123 -U omm -f /home/omm/backup/MPPDB_tablespace.sql -p 8000 -t
+    ```
+
+    **表 1** 常用参数说明
+
+    | 参数   | 参数说明        | 举例      |
+    | :------- | :----------------------------------------------------------------- | :----------------------|
+    | -U   | 连接数据库的用户名，需要是MogDB管理员用户。                                                                                                                                 | -U omm                                       |
+    | -W   | 指定用户连接的密码。<br/>- 如果主机的认证策略是trust，则不会对数据库管理员进行密码验证，即无需输入-W选项；<br/>- 如果没有-W选项，并且不是数据库管理员，会提示用户输入密码。 | -W Bigdata@123                               |
+    | -f   | 将导出文件发送至指定目录文件夹。如果这里省略，则使用标准输出。                                                                                                              | -f /home/omm/backup/**MPPDB_tablespace**.sql |
+    | -p   | 指定服务器所监听的TCP端口或本地Unix域套接字后缀，以确保连接。                                                                                                               | -p 8000                                      |
+    | -t   | 或者-tablespaces-only，只转储表空间，不转储数据库或角色。                                                                                                                   | -                                            |
+
+    其他参数说明请参见《参考指南》中“工具参考 > 服务端工具 > [gs_dumpall](6-gs_dumpall)”章节。
+
+<br/>
+
+### 示例
+
+示例一: 执行gs_dumpall，导出所有数据库的公共全局表空间信息和用户信息（omm用户为管理员用户），导出文件为文本格式。
+
+```bash
+gs_dumpall -W Bigdata@123 -U omm -f /home/omm/backup/MPPDB_globals.sql -p 8000 -g
+gs_dumpall[port='8000'][2018-11-14 19:06:24]: dumpall operation successful
+gs_dumpall[port='8000'][2018-11-14 19:06:24]: total time: 1150  ms
+```
+
+示例二:  执行gs_dumpall，导出所有数据库的公共全局表空间信息（omm用户为管理员用户），并对导出文件进行加密，导出文件为文本格式。
+
+```bash
+gs_dumpall -W Bigdata@123 -U omm -f /home/omm/backup/MPPDB_tablespace.sql -p 8000 -t --with-encryption AES128 --with-key 1212121212121212
+gs_dumpall[port='8000'][2018-11-14 19:00:58]: dumpall operation successful
+gs_dumpall[port='8000'][2018-11-14 19:00:58]: total time: 186  ms
+```
+
+示例三: 执行gs_dumpall，导出所有数据库的公共全局用户信息（omm用户为管理员用户），导出文件为文本格式。
+
+```bash
+gs_dumpall -W Bigdata@123 -U omm -f /home/omm/backup/MPPDB_user.sql -p 8000 -r
+gs_dumpall[port='8000'][2018-11-14 19:03:18]: dumpall operation successful
+gs_dumpall[port='8000'][2018-11-14 19:03:18]: total time: 162  ms
+```
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/exporting-data/4-data-export-by-a-user-without-required-permissions.md b/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/exporting-data/4-data-export-by-a-user-without-required-permissions.md
new file mode 100644
index 0000000000000000000000000000000000000000..b458480389d7cdf6b3371cbe7c34bee3f3b5fe8f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/exporting-data/4-data-export-by-a-user-without-required-permissions.md
@@ -0,0 +1,86 @@
+---
+title: 无权限角色导出数据
+summary: 无权限角色导出数据
+author: Guo Huan
+date: 2021-03-04
+---
+
+# 无权限角色导出数据
+
+gs_dump和gs_dumpall通过-U指定执行导出的用户帐户。如果当前使用的帐户不具备导出所要求的权限时，会无法导出数据。此时，需要将有权限的用户赋权给无权限用户，然后可在导出命令中设置-role参数来指定具备权限的角色。在执行命令后，gs_dump和gs_dumpall会使用-role参数指定的角色，完成导出动作。
+
+<br/>
+
+## 操作步骤
+
+1. 以操作系统用户omm登录数据库主节点。
+
+2. 使用gs_dump导出human_resource数据库数据。
+
+   用户jack不具备导出数据库human_resource的权限，而角色role1具备该权限，要实现导出数据库human_resource，需要将role1赋权给jack，然后可以在导出命令中设置-role角色为role1，使用role1的权限，完成导出目的。导出文件格式为tar归档格式。
+
+    ```bash
+   gs_dump -U jack -f /home/omm/backup/MPPDB_backup.tar -p 8000 human_resource --role role1 --rolepassword  abc@1234 -F t
+    Password:
+    ```
+
+    **表 1** 常用参数说明
+
+   | 参数   | 参数说明        | 举例      |
+   | :------- | :----------------------------------------------------------------- | :----------------------|
+   | -U            | 连接数据库的用户名。                                                                                                                                                                     | -U jack                              |
+   | -W            | 指定用户连接的密码。<br/>- 如果主机的认证策略是trust，则不会对数据库管理员进行密码验证，即无需输入-W选项。<br/>- 如果没有-W选项，并且不是数据库管理员，会提示用户输入密码。              | -W Bigdata@123                       |
+   | -f            | 将导出文件发送至指定目录文件夹。如果这里省略，则使用标准输出。                                                                                                                           | -f /home/omm/backup/MPPDB_backup.tar |
+   | -p            | 指定服务器所监听的TCP端口或本地Unix域套接字后缀，以确保连接。                                                                                                                            | -p 8000                              |
+   | dbname        | 需要导出的数据库名称                                                                                                                                                                     | human_resource                       |
+   | -role         | 指定导出使用的角色名。选择该选项，会使导出工具连接数据库后，发起一个SET ROLE角色名命令。当所授权用户（由-U指定）没有导出工具要求的权限时，该选项会起到作用，即切换到具备相应权限的角色。 | -r role1                             |
+   | -rolepassword | 指定具体角色用户的角色密码。                                                                                                                                                             | -rolepassword abc@1234               |
+   | -F            | 选择导出文件格式。-F参数值如下: <br/>- p: 纯文本格式<br/>- c: 自定义归档<br/>- d: 目录归档格式<br/>- t: tar归档格式                                                                      | -F t                                 |
+
+    其他参数说明请参见《参考指南》中“工具参考 > 服务端工具 > [gs_dump](5-gs_dump)”章节或“[gs_dumpall](6-gs_dumpall)”章节。
+
+<br/>
+
+## 示例
+
+示例一: 执行gs_dump导出数据，用户jack不具备导出数据库human_resource的权限，而角色role1具备该权限，要实现导出数据库human_resource，可以在导出命令中设置-role角色为role1，使用role1的权限，完成导出目的。导出文件格式为tar归档格式。
+
+```bash
+$ human_resource=# CREATE USER jack IDENTIFIED BY "1234@abc";
+CREATE ROLE
+human_resource=# GRANT role1 TO jack;
+GRANT ROLE
+
+$ gs_dump -U jack -f /home/omm/backup/MPPDB_backup11.tar -p 8000 human_resource --role role1 --rolepassword abc@1234 -F t
+Password:
+gs_dump[port='8000'][human_resource][2017-07-21 16:21:10]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2017-07-21 16:21:10]: total time: 4239  ms
+```
+
+示例二: 执行gs_dump导出数据，用户jack不具备导出模式public的权限，而角色role1具备该权限，要实现导出模式public，可以在导出命令中设置-role角色为role1，使用role1的权限，完成导出目的。导出文件格式为tar归档格式。
+
+```bash
+$ human_resource=# CREATE USER jack IDENTIFIED BY "1234@abc";
+CREATE ROLE
+human_resource=# GRANT role1 TO jack;
+GRANT ROLE
+
+$ gs_dump -U jack -f /home/omm/backup/MPPDB_backup12.tar -p 8000 human_resource -n public --role role1 --rolepassword abc@1234 -F t
+Password:
+gs_dump[port='8000'][human_resource][2017-07-21 16:21:10]: dump database human_resource successfully
+gs_dump[port='8000'][human_resource][2017-07-21 16:21:10]: total time: 3278  ms
+```
+
+示例三: 执行gs_dumpall导出数据，用户jack不具备导出所有数据库的权限，而角色role1（管理员）具备该权限，要实现导出所有数据库，可以在导出命令中设置-role角色为role1，使用role1的权限，完成导出目的。导出文件格式为文本归档格式。
+
+```bash
+$ human_resource=# CREATE USER jack IDENTIFIED BY "1234@abc";
+CREATE ROLE
+human_resource=# GRANT role1 TO jack;
+GRANT ROLE
+
+$ gs_dumpall -U jack -f /home/omm/backup/MPPDB_backup.sql -p 8000 --role role1 --rolepassword abc@1234
+Password:
+gs_dumpall[port='8000'][human_resource][2018-11-14 17:26:18]: dumpall operation successful
+gs_dumpall[port='8000'][human_resource][2018-11-14 17:26:18]: total time: 6437  ms
+```
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/1-import-modes.md b/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/1-import-modes.md
new file mode 100644
index 0000000000000000000000000000000000000000..27ac8cd5719d28ffc8c60c3290f220cab600a46d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/1-import-modes.md
@@ -0,0 +1,18 @@
+---
+title: 导入方式
+summary: 导入方式
+author: Guo Huan
+date: 2021-03-04
+---
+
+# 导入方式
+
+MogDB数据库提供了灵活的数据入库方式: INSERT、COPY以及gsql元命令\\copy。各方式具有不同的特点，具体请参见[表1](#导入方式特点说明)。
+
+**表 1** 导入方式特点说明<a id="导入方式特点说明"> </a>
+
+| 方式                   | 特点         |
+| :--------------------- | :----------------------------------------- |
+| INSERT                 | 通过INSERT语句插入一行或多行数据，及从指定表插入数据。     |
+| COPY                   | 通过COPY FROM STDIN语句直接向MogDB数据库写入数据。<br/>通过JDBC驱动的CopyManager接口从其他数据库向MogDB数据库写入数据时，具有业务数据无需落地成文件的优势。        |
+| gsql工具的元命令\\copy | 与直接使用SQL语句COPY不同，该命令读取/写入的文件只能是gsql客户端所在机器上的本地文件。<br/>说明:<br/>\\COPY只适合小批量、格式良好的数据导入，不会对非法字符做预处理，也无容错能力，无法适用于含有异常数据的场景。导入数据应优先选择COPY。 |
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/10-managing-concurrent-write-operations.md b/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/10-managing-concurrent-write-operations.md
new file mode 100644
index 0000000000000000000000000000000000000000..83f117845ddb99b3ced0edc3766c51f4acebd65f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/10-managing-concurrent-write-operations.md
@@ -0,0 +1,195 @@
+---
+title: 管理并发写入操作
+summary: 管理并发写入操作
+author: Guo Huan
+date: 2021-03-04
+---
+
+# 管理并发写入操作
+
+<br/>
+
+## 事务隔离说明
+
+MogDB基于MVCC（多版本并发控制）并结合两阶段锁的方式进行事务管理，其特点是读写之间不阻塞。SELECT是纯读操作，UPDATE和DELETE是读写操作。
+
+- 读写操作和纯读操作之间并不会发生冲突，读写操作之间也不会发生冲突。每个并发事务在事务开始时创建事务快照，并发事务之间不能检测到对方的更改。
+
+  - 读已提交隔离级别中，如果事务T1提交后，事务T2就可以看到事务T1更改的结果。
+
+  - 可重复读级别中，如果事务T1提交事务前事务T2开始执行，则事务T1提交后，事务T2依旧看不到事务T1更改的结果，保证了一个事务开始后，查询的结果前后一致，不受其他事务的影响。
+
+- 读写操作，支持的是行级锁，不同的事务可以并发更新同一个表，只有更新同一行时才需等待，后发生的事务会等待先发生的事务提交后，再执行更新操作。
+
+  - READ COMMITTED: 读已提交隔离级别，事务只能读到已提交的数据而不会读到未提交的数据，这是缺省值。
+  - REPEATABLE READ:  事务只能读到事务开始之前已提交的数据，不能读到未提交的数据以及事务执行期间其它并发事务提交的修改。
+
+<br/>
+
+## 写入和读写操作
+
+关于写入和读写操作的命令:
+
+- INSERT，可向表中插入一行或多行数据。
+- UPDATE，可修改表中现有数据。
+- DELETE，可删除表中现有数据。
+- COPY，导入数据。
+
+INSERT和COPY是纯写入的操作。并发写入操作，需要等待，对同一个表的操作，当事务T1的INSERT或COPY未解除锁定时，事务T2的INSERT或COPY需等待，事务T1解除锁定时，事务T2正常继续。
+
+UPDATE和DELETE是读写操作（先查询出要操作的行）。UPDATE和DELETE执行前需要先查询数据，由于并发事务彼此不可见，所以UPDATE和DELETE操作是读取事务发生前提交的数据的快照。写入操作，是行级锁，当事务T1和事务T2并发更新同一行时，后发生的事务T2会等待，根据设置的等待时长，若超时事务T1未提交则事务T2执行失败；当事务T1和事务T2并发更新的行不同时，事务T1和事务2都会执行成功。
+
+<br/>
+
+## 并发写入事务的潜在死锁情况
+
+只要事务涉及多个表的或者同一个表相同行的更新时，同时运行的事务就可能在同时尝试写入时变为死锁状态。事务会在提交或回滚时一次性解除其所有锁定，而不会逐一放弃锁定。 例如，假设事务T1和T2在大致相同的时间开始:
+
+- 如果T1开始对表A进行写入且T2开始对表B进行写入，则两个事务均可继续而不会发生冲突；但是，如果T1完成了对表A的写入操作并需要开始对表B进行写入，此时操作的行数正好与T2一致，它将无法继续，因为T2仍保持对表B对应行的锁定，此时T2开始更新表A中与T1相同的行数，此时也将无法继续，产生死锁，在锁等待超时内，前面事务提交释放锁，后面的事务可以继续执行更新，等待时间超时后，事务抛错，有一个事务退出。
+- 如果T1，T2都对表A进行写入，此时T1更新1-5行的数据，T2更新6-10行的数据，两个事务不会发生冲突，但是，如果T1完成后开始对表A的6-10行数据进行更新，T2完成后开始更新1-5行的数据，此时两个事务无法继续，在锁等待超时内，前面事务提交释放锁，后面的事务可以继续执行更新，等待时间超时后，事务抛错，有一个事务退出。
+
+## 并发写入示例
+
+本章节以表test为例，分别介绍相同表的INSERT和DELETE并发，相同表的并发INSERT，相同表的并发UPDATE，以及数据导入和查询的并发的执行详情。
+
+```sql
+CREATE TABLE test(id int, name char(50), address varchar(255));
+```
+
+<br/>
+
+### 相同表的INSERT和DELETE并发
+
+事务T1:
+
+```sql
+START TRANSACTION;
+INSERT INTO test VALUES(1,'test1','test123');
+COMMIT;
+```
+
+事务T2:
+
+```sql
+START TRANSACTION;
+DELETE test WHERE NAME='test1';
+COMMIT;
+```
+
+场景1:
+
+开启事务T1，不提交的同时开启事务T2，事务T1执行INSERT完成后，执行事务T2的DELETE，此时显示DELETE 0，由于事务T1未提交，事务2看不到事务插入的数据；
+
+场景2:
+
+- READ COMMITTED级别
+
+    开启事务T1，不提交的同时开启事务T2，事务T1执行INSERT完成后，提交事务T1，事务T2再执行DELETE语句时，此时显示DELETE 1，事务T1提交完成后，事务T2可以看到此条数据，可以删除成功。
+
+- REPEATABLE READ级别
+
+    开启事务T1，不提交的同时开启事务T2，事务T1执行INSERT完成后，提交事务T1，事务T2再执行DELETE语句时，此时显示DELETE 0，事务T1提交完成后，事务T2依旧看不到事务T1的数据，一个事务中前后查询到的数据是一致的。
+
+<br/>
+
+### 相同表的并发INSERT
+
+事务T1:
+
+```sql
+START TRANSACTION;
+INSERT INTO test VALUES(2,'test2','test123');
+COMMIT;
+```
+
+事务T2:
+
+```sql
+START TRANSACTION;
+INSERT INTO test VALUES(3,'test3','test123');
+COMMIT;
+```
+
+场景1:
+
+开启事务T1，不提交的同时开启事务T2，事务T1执行INSERT完成后，执行事务T2的INSERT语句，可以执行成功，读已提交和可重复读隔离级别下，此时在事务T1中执行SELECT语句，看不到事务T2中插入的数据，事务T2中执行查询语句看不到事务T1中插入的数据。
+
+场景2:
+
+- READ COMMITTED级别
+
+    开启事务T1，不提交的同时开启事务T2，事务T1执行INSERT完成后直接提交，事务T2中执行INSERT语句后执行查询语句，可以看到事务T1中插入的数据。
+
+- REPEATABLE READ级别
+
+    开启事务T1，不提交的同时开启事务T2，事务T1执行INSERT完成后直接提交，事务T2中执行INSERT语句后执行查询语句，看不到事务T1中插入的数据。
+
+<br/>
+
+### 相同表的并发UPDATE
+
+事务T1:
+
+```sql
+START TRANSACTION;
+UPDATE test SET address='test1234' WHERE name='test1';
+COMMIT;
+```
+
+事务T2:
+
+```sql
+START TRANSACTION;
+UPDATE test SET address='test1234' WHERE name='test2';
+COMMIT;
+```
+
+事务T3:
+
+```sql
+START TRANSACTION;
+UPDATE test SET address='test1234' WHERE name='test1';
+COMMIT;
+```
+
+场景1:
+
+开启事务T1，不提交的同时开启事务T2，事务T1开始执行UPDATE，事务T2开始执行UPDATE，事务T1和事务T2都执行成功。更新不同行时，更新操作拿的是行级锁，不会发生冲突，两个事务都可以执行成功。
+
+场景2:
+
+开启事务T1，不提交的同时开启事务T3，事务T1开始执行UPDATE，事务T3开始执行UPDATE，事务T1执行成功，事务T3等待超时后会出错。更新相同行时，事务T1未提交时，未释放锁，导致事务T3执行不成功。
+
+<br/>
+
+### 数据导入和查询的并发
+
+事务T1:
+
+```sql
+START TRANSACTION;
+COPY test FROM '...';
+COMMIT;
+```
+
+事务T2:
+
+```sql
+START TRANSACTION;
+SELECT * FROM test;
+COMMIT;
+```
+
+场景1:
+
+开启事务T1，不提交的同时开启事务T2，事务T1开始执行COPY，事务T2开始执行SELECT，事务T1和事务T2都执行成功。事务T2中查询看不到事务T1新COPY进来的数据。
+
+场景2:
+
+- READ COMMITTED级别
+
+    开启事务T1，不提交的同时开启事务T2，事务T1开始执行COPY，然后提交，事务T2查询，可以看到事务T1中COPY的数据。
+
+- REPEATABLE READ级别
+
+    开启事务T1，不提交的同时开启事务T2，事务T1开始执行COPY，然后提交，事务T2 查询，看不到事务T1中COPY的数据。
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/2-running-the-INSERT-statement-to-insert-data.md b/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/2-running-the-INSERT-statement-to-insert-data.md
new file mode 100644
index 0000000000000000000000000000000000000000..e5f9bd28fde774badadad5887bfcb7ed5fb3464d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/2-running-the-INSERT-statement-to-insert-data.md
@@ -0,0 +1,20 @@
+---
+title: 通过INSERT语句直接写入数据
+summary: 通过INSERT语句直接写入数据
+author: Guo Huan
+date: 2021-03-04
+---
+
+# 通过INSERT语句直接写入数据
+
+用户可以通过以下方式执行INSERT语句直接向MogDB数据库写入数据:
+
+- 使用MogDB数据库提供的客户端工具向MogDB数据库写入数据。
+
+    请参见向表中插入数据。
+
+- 通过JDBC/ODBC驱动连接数据库执行INSERT语句向MogDB数据库写入数据。
+
+    详细内容请参见连接数据库。
+
+MogDB数据库支持完整的数据库事务级别的增删改操作。INSERT是最简单的一种数据写入方式，这种方式适合数据写入量不大，并发度不高的场景。
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/3-running-the-COPY-FROM-STDIN-statement-to-import-data.md b/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/3-running-the-COPY-FROM-STDIN-statement-to-import-data.md
new file mode 100644
index 0000000000000000000000000000000000000000..f3c2560d546ba072e6f0504a056deac4eef96d93
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/3-running-the-COPY-FROM-STDIN-statement-to-import-data.md
@@ -0,0 +1,318 @@
+---
+title: COPY FROM STDIN导入数据
+summary: COPY FROM STDIN导入数据
+author: Guo Huan
+date: 2021-03-04
+---
+
+# 使用COPY FROM STDIN导入数据
+
+<br/>
+
+## 关于COPY FROM STDIN导入数据
+
+用户可以使用以下方式通过COPY FROM STDIN语句直接向MogDB写入数据。
+
+- 通过键盘输入向MogDB数据库写入数据。详细请参见[COPY](41-COPY)。
+- 通过JDBC驱动的CopyManager接口从文件或者数据库向MogDB写入数据。此方法支持COPY语法中copy option的所有参数。
+
+<br/>
+
+## CopyManager类简介
+
+CopyManager是MogDB JDBC驱动中提供的一个API接口类，用于批量向MogDB数据库中导入数据。
+
+<br/>
+
+### CopyManager的继承关系
+
+CopyManager类位于org.postgresql.copy Package中，继承自java.lang.Object类，该类的声明如下:
+
+```java
+public class CopyManager
+extends Object
+```
+
+<br/>
+
+### 构造方法
+
+```java
+public CopyManager(BaseConnection connection)
+throws SQLException
+```
+
+<br/>
+
+### 常用方法
+
+**表 1** CopyManager常用方法
+
+| 返回值  | 方法                      | 描述    | throws                   |
+| :------ | :-------------------------- | :------------------------------- | :----------------------- |
+| CopyIn  | copyIn(String sql)        | -        | SQLException             |
+| long    | copyIn(String sql, InputStream from)                 | 使用COPY FROM STDIN从InputStream中快速向数据库中的表导入数据。 | SQLException,IOException |
+| long    | copyIn(String sql, InputStream from, int bufferSize) | 使用COPY FROM STDIN从InputStream中快速向数据库中的表导入数据。 | SQLException,IOException |
+| long    | copyIn(String sql, Reader from)                      | 使用COPY FROM STDIN从Reader中快速向数据库中的表导入数据。      | SQLException,IOException |
+| long    | copyIn(String sql, Reader from, int bufferSize)      | 使用COPY FROM STDIN从Reader中快速向数据库中的表导入数据。      | SQLException,IOException |
+| CopyOut | copyOut(String sql)       | -        | SQLException             |
+| long    | copyOut(String sql, OutputStream to)                 | 将一个COPY TO STDOUT的结果集从数据库发送到OutputStream类中。   | SQLException,IOException |
+| long    | copyOut(String sql, Writer to)                       | 将一个COPY TO STDOUT的结果集从数据库发送到Writer类中。         | SQLException,IOException |
+
+<br/>
+
+## 处理错误表
+
+### 操作场景
+
+当数据导入发生错误时，请根据本文指引信息进行处理。
+
+### 查询错误信息
+
+数据导入过程中发生的错误，一般分为数据格式错误和非数据格式错误。
+
+- 数据格式错误
+
+  在创建外表时，通过设置参数“LOG INTO error_table_name”，将数据导入过程中出现的数据格式错误信息写入指定的错误信息表error_table_name中。您可以通过以下SQL，查询详细错误信息。
+
+  ```sql
+  mogdb=# SELECT * FROM error_table_name;
+  ```
+
+  错误信息表结构如表1所示。
+
+  **表 1** 错误信息表
+
+  | 列名称    | 类型                     | 描述                                         |
+  | :-------- | :----------------------- | :------------------------------------------- |
+  | nodeid    | integer                  | 报错节点编号。                               |
+  | begintime | timestamp with time zone | 出现数据格式错误的时间。                     |
+  | filename  | character varying        | 出现数据格式错误的数据源文件名。             |
+  | rownum    | bigint                   | 在数据源文件中，出现数据格式错误的行号。     |
+  | rawrecord | text                     | 在数据源文件中，出现数据格式错误的原始记录。 |
+  | detail    | text                     | 详细错误信息。                               |
+
+- 非数据格式错误
+
+  对于非数据格式错误，一旦发生将导致整个数据导入失败。您可以根据执行数据导入过程中，界面提示的错误信息，帮助定位问题，处理错误表。
+
+### 处理数据导入错误
+
+根据获取的错误信息，请对照下表，处理数据导入错误。
+
+**表 2** 处理数据导入错误
+
+| 错误信息                                                     | 原因                                                         | 解决办法                                                     |
+| :----------------------------------------------------------- | :----------------------------------------------------------- | :----------------------------------------------------------- |
+| missing data for column “r_reason_desc”                      | 1. 数据源文件中的列数比外表定义的列数少。<br/>2. 对于TEXT格式的数据源文件，由于转义字符（\）导致delimiter（分隔符）错位或者quote（引号字符）错位造成的错误。<br/>**示例：**目标表存在3列字段，导入的数据如下所示。由于存在转义字符“\”，分隔符“\|”被转义为第二个字段的字段值，导致第三个字段值缺失。<br/>`BE|Belgium|1` | 1. 由于列数少导致的报错，选择下列办法解决：<br/>- 在数据源文件中，增加列“r_reason_desc”的字段值。<br/>- 在创建外表时，将参数“fill_missing_fields”设置为“on”。即当导入过程中，若数据源文件中一行数据的最后一个字段缺失，则把最后一个字段的值设置为NULL，不报错。<br/>2. 对由于转义字符导致的错误，需检查报错的行中是否含有转义字符（\）。若存在，建议在创建外表时，将参数“noescaping”（是否不对'\\'和后面的字符进行转义）设置为true。 |
+| extra data after last expected column                        | 数据源文件中的列数比外表定义的列数多。                       | - 在数据源文件中，删除多余的字段值。<br/>- 在创建外表时，将参数“ignore_extra_data”设置为“on”。即在导入过程中，若数据源文件比外表定义的列数多，则忽略行尾多出来的列。 |
+| invalid input syntax for type numeric: “a”                   | 数据类型错误。                                               | 在数据源文件中，修改输入字段的数据类型。根据此错误信息，请将输入的数据类型修改为numeric。 |
+| null value in column “staff_id” violates not-null constraint | 非空约束。                                                   | 在数据源文件中，增加非空字段信息。根据此错误信息，请增加“staff_id”列的值。 |
+| duplicate key value violates unique constraint “reg_id_pk”   | 唯一约束。                                                   | - 删除数据源文件中重复的行。<br/>- 通过设置关键字“DISTINCT”，从SELECT结果集中删除重复的行，保证导入的每一行都是唯一的。<br/>`mogdb=# INSERT INTO reasons SELECT DISTINCT * FROM foreign_tpcds_reasons;` |
+| value too long for type character varying(16)                | 字段值长度超过限制。                                         | 在数据源文件中，修改字段值长度。根据此错误信息，字段值长度限制为VARCHAR2(16)。 |
+
+<br/>
+
+## 示例1: 通过本地文件导入导出数据
+
+在使用JAVA语言基于MogDB进行二次开发时，可以使用CopyManager接口，通过流方式，将数据库中的数据导出到本地文件或者将本地文件导入数据库中，文件格式支持CSV、TEXT等格式。
+
+样例程序如下，执行时需要加载MogDB的JDBC驱动。
+
+```java
+import java.sql.Connection;
+import java.sql.DriverManager;
+import java.io.IOException;
+import java.io.FileInputStream;
+import java.io.FileOutputStream;
+import java.sql.SQLException;
+import org.postgresql.copy.CopyManager;
+import org.postgresql.core.BaseConnection;
+
+public class Copy{
+
+     public static void main(String[] args)
+     {
+      String urls = new String("jdbc:postgresql://localhost:8000/postgres"); //数据库URL
+      String username = new String("username");            //用户名
+      String password = new String("passwd");             //密码
+      String tablename = new String("migration_table"); //定义表信息
+      String tablename1 = new String("migration_table_1"); //定义表信息
+      String driver = "org.postgresql.Driver";
+      Connection conn = null;
+
+      try {
+          Class.forName(driver);
+          conn = DriverManager.getConnection(urls, username, password);
+      } catch (ClassNotFoundException e) {
+           e.printStackTrace(System.out);
+      } catch (SQLException e) {
+           e.printStackTrace(System.out);
+      }
+
+      // 将表migration_table中数据导出到本地文件d:/data.txt
+      try {
+          copyToFile(conn, "d:/data.txt", "(SELECT * FROM migration_table)");
+      } catch (SQLException e) {
+          // TODO Auto-generated catch block
+          e.printStackTrace();
+      } catch (IOException e) {
+          // TODO Auto-generated catch block
+          e.printStackTrace();
+      }
+      //将d:/data.txt中的数据导入到migration_table_1中。
+      try {
+          copyFromFile(conn, "d:/data.txt", tablename1);
+      } catch (SQLException e) {
+          // TODO Auto-generated catch block
+          e.printStackTrace();
+      } catch (IOException e) {
+          // TODO Auto-generated catch block
+          e.printStackTrace();
+      }
+
+      // 将表migration_table_1中的数据导出到本地文件d:/data1.txt
+      try {
+          copyToFile(conn, "d:/data1.txt", tablename1);
+      } catch (SQLException e) {
+          // TODO Auto-generated catch block
+          e.printStackTrace();
+      } catch (IOException e) {
+          // TODO Auto-generated catch block
+          e.printStackTrace();
+      }
+  }
+
+  public static void copyFromFile(Connection connection, String filePath, String tableName)
+         throws SQLException, IOException {
+
+     FileInputStream fileInputStream = null;
+
+     try {
+         CopyManager copyManager = new CopyManager((BaseConnection)connection);
+         fileInputStream = new FileInputStream(filePath);
+         copyManager.copyIn("COPY " + tableName + " FROM STDIN with (" + "DELIMITER"+"'"+ delimiter +  "'" + "ENCODING " + "'" + encoding + "')", fileInputStream);
+     } finally {
+         if (fileInputStream != null) {
+             try {
+                 fileInputStream.close();
+             } catch (IOException e) {
+                 e.printStackTrace();
+             }
+         }
+     }
+ }
+     public static void copyToFile(Connection connection, String filePath, String tableOrQuery)
+          throws SQLException, IOException {
+
+      FileOutputStream fileOutputStream = null;
+
+      try {
+          CopyManager copyManager = new CopyManager((BaseConnection)connection);
+          fileOutputStream = new FileOutputStream(filePath);
+          copyManager.copyOut("COPY " + tableOrQuery + " TO STDOUT", fileOutputStream);
+      } finally {
+          if (fileOutputStream != null) {
+              try {
+                  fileOutputStream.close();
+              } catch (IOException e) {
+                  e.printStackTrace();
+              }
+          }
+      }
+  }
+}
+```
+
+<br/>
+
+## 示例2: 从MY向MogDB数据库进行数据迁移
+
+下面示例演示如何通过CopyManager从MY向MogDB数据库进行数据迁移的过程。
+
+```java
+import java.io.StringReader;
+import java.sql.Connection;
+import java.sql.DriverManager;
+import java.sql.ResultSet;
+import java.sql.SQLException;
+import java.sql.Statement;
+
+import org.postgresql.copy.CopyManager;
+import org.postgresql.core.BaseConnection;
+
+public class Migration{
+
+    public static void main(String[] args) {
+        String url = new String("jdbc:postgresql://localhost:8000/postgres"); //数据库URL
+        String user = new String("username");            //MogDB数据库用户名
+        String pass = new String("passwd");             //MogDB数据库密码
+        String tablename = new String("migration_table_1"); //定义表信息
+        String delimiter = new String("|");              //定义分隔符
+        String encoding = new String("UTF8");            //定义字符集
+        String driver = "org.postgresql.Driver";
+        StringBuffer buffer = new StringBuffer();       //定义存放格式化数据的缓存
+
+        try {
+            //获取源数据库查询结果集
+            ResultSet rs = getDataSet();
+
+            //遍历结果集，逐行获取记录
+            //将每条记录中各字段值，按指定分隔符分割，由换行符结束，拼成一个字符串
+            //把拼成的字符串，添加到缓存buffer
+            while (rs.next()) {
+                buffer.append(rs.getString(1) + delimiter
+                        + rs.getString(2) + delimiter
+                        + rs.getString(3) + delimiter
+                        + rs.getString(4)
+                        + "\n");
+            }
+            rs.close();
+
+            try {
+                //建立目标数据库连接
+                Class.forName(driver);
+                Connection conn = DriverManager.getConnection(url, user, pass);
+                BaseConnection baseConn = (BaseConnection) conn;
+                baseConn.setAutoCommit(false);
+
+                //初始化表信息
+                String sql = "Copy " + tablename + " from STDIN with (DELIMITER " + "'" + delimiter + "'" +","+ " ENCODING " + "'" + encoding + "'");
+
+                //提交缓存buffer中的数据
+                CopyManager cp = new CopyManager(baseConn);
+                StringReader reader = new StringReader(buffer.toString());
+                cp.copyIn(sql, reader);
+                baseConn.commit();
+                reader.close();
+                baseConn.close();
+            } catch (ClassNotFoundException e) {
+                e.printStackTrace(System.out);
+            } catch (SQLException e) {
+                e.printStackTrace(System.out);
+            }
+
+        } catch (Exception e) {
+            e.printStackTrace();
+        }
+    }
+
+    //********************************
+    // 从源数据库返回查询结果集
+    //*********************************
+    private static ResultSet getDataSet() {
+        ResultSet rs = null;
+        try {
+            Class.forName("com.MY.jdbc.Driver").newInstance();
+            Connection conn = DriverManager.getConnection("jdbc:MY://10.119.179.227:3306/jack?useSSL=false&allowPublicKeyRetrieval=true", "jack", "Gauss@123");
+            Statement stmt = conn.createStatement();
+            rs = stmt.executeQuery("select * from migration_table");
+        } catch (SQLException e) {
+            e.printStackTrace();
+        } catch (Exception e) {
+            e.printStackTrace();
+        }
+        return rs;
+    }
+}
+```
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/4-using-a-gsql-meta-command-to-import-data.md b/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/4-using-a-gsql-meta-command-to-import-data.md
new file mode 100644
index 0000000000000000000000000000000000000000..6319837c8c7379f9a18677fc375382c8b83449ac
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/4-using-a-gsql-meta-command-to-import-data.md
@@ -0,0 +1,211 @@
+---
+title: 使用gsql元命令导入数据
+summary: 使用gsql元命令导入数据
+author: Guo Huan
+date: 2021-03-04
+---
+
+# 使用gsql元命令导入数据
+
+gsql工具提供了元命令\\copy进行数据导入。
+
+<br/>
+
+**\\copy命令**
+
+## 语法
+
+```
+\copy { table [ ( column_list ) ] |
+
+( query ) } { from | to } { filename |
+
+stdin | stdout | pstdin | pstdout }
+
+[ with ] [ binary ] [ delimiter
+
+[ as ] 'character' ] [ null [ as ] 'string' ]
+
+[ csv [ header ] [ quote [ as ]
+
+'character' ] [ escape [ as ] 'character' ]
+
+[ force quote column_list | * ] [ force
+
+not null column_list ] ]
+```
+
+在任何gsql客户端登录数据库成功后，可以使用该命令进行数据的导入/导出。但是与SQL的COPY命令不同，该命令读取/写入的文件是本地文件，而非数据库服务器端文件；所以，要操作的文件的可访问性、权限等，都是受限于本地用户的权限。
+
+> **说明：**
+>
+> \\COPY只适合小批量、格式良好的数据导入，不会对非法字符做预处理，也无容错能力，无法适用于含有异常数据的场景。导入数据应优先选择GDS或COPY。
+
+**参数说明**
+
+- table
+
+    表的名称（可以有模式修饰）。
+
+    取值范围: 已存在的表名。
+
+- column_list
+
+    可选的待拷贝字段列表。
+
+    取值范围: 任意字段。如果没有声明字段列表，将使用所有字段。
+
+- query
+
+    其结果将被拷贝。
+
+    取值范围: 一个必须用圆括弧包围的SELECT或VALUES命令。
+
+- filename
+
+    文件的绝对路径。执行copy命令的用户必须有此路径的写权限。
+
+- stdin
+
+    声明输入是来自标准输入。
+
+- stdout
+
+    声明输出打印到标准输出。
+
+- pstdin
+
+    声明输入是来自gsql的标准输入。
+
+- pstout
+
+- 声明输出打印到gsql的标准输出。
+
+- binary
+
+    使用二进制格式存储和读取，而不是以文本的方式。在二进制模式下，不能声明DELIMITER，NULL，CSV选项。指定binary类型后，不能再通过option或copy_option指定CSV、FIXED、TEXT等类型。
+
+- delimiter [ as ] 'character'
+
+    指定数据文件行数据的字段分隔符。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+    >
+    > - 分隔符不能是\\r和\\n。
+    > - 分隔符不能和null参数相同，CSV格式数据的分隔符不能和quote参数相同。
+    > - TEXT格式数据的分隔符不能包含:  \\.abcdefghijklmnopqrstuvwxyz0123456789。
+    > - 数据文件中单行数据长度需<1GB，如果分隔符较长且数据列较多的情况下，会影响导出有效数据的长度。
+    > - 分隔符推荐使用多字符和不可见字符。多字符例如'$^&'；不可见字符例如0x07，0x08，0x1b等。
+
+    取值范围: 支持多字符分隔符，但分隔符不能超过10个字节。
+
+    默认值:
+
+  - TEXT格式的默认分隔符是水平制表符（tab）。
+  - CSV格式的默认分隔符为","。
+  - FIXED格式没有分隔符。
+
+- null [ as ] 'string'
+
+    用来指定数据文件中空值的表示。
+
+    取值范围:
+
+  - null值不能是\\r和\\n，最大为100个字符。
+  - null值不能和分隔符、quote参数相同。
+
+    默认值:
+
+  - CSV格式下默认值是一个没有引号的空字符串。
+  - 在TEXT格式下默认值是\\N。
+
+- header
+
+    指定导出数据文件是否包含标题行，标题行一般用来描述表中每个字段的信息。header只能用于CSV，FIXED格式的文件中。
+
+    在导入数据时，如果header选项为on，则数据文本第一行会被识别为标题行，会忽略此行。如果header为off，而数据文件中第一行会被识别为数据。
+
+    在导出数据时，如果header选项为on，则需要指定fileheader。fileheader是指定导出数据包含标题行的定义文件。如果header为off，则导出数据文件不包含标题行。
+
+    取值范围: true/on，false/off。
+
+    默认值: false
+
+- quote [ as ] 'character'
+
+    CSV格式文件下的引号字符。
+
+    默认值: 双引号。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+    >
+    > - quote参数不能和分隔符、null参数相同。
+    > - quote参数只能是单字节的字符。
+    > - 推荐不可见字符作为quote，例如0x07，0x08，0x1b等。
+
+- escape [ as ] 'character'
+
+    CSV格式下，用来指定逃逸字符，逃逸字符只能指定为单字节字符。
+
+    默认值: 双引号。当与quote值相同时，会被替换为'\\0'。
+
+- force quote column_list | *
+
+    在CSV COPY TO模式下，强制在每个声明的字段周围对所有非NULL值都使用引号包围。NULL输出不会被引号包围。
+
+    取值范围: 已存在的字段。
+
+- force not null column_list
+
+    在CSV COPY FROM模式下，指定的字段输入不能为空。
+
+    取值范围: 已存在的字段。
+
+<br/>
+
+**任务示例**
+
+1. 创建目标表a。
+
+    ```sql
+    mogdb=# CREATE TABLE a(a int);
+    ```
+
+2. 导入数据。
+
+    从stdin拷贝数据到目标表a。
+
+    ```sql
+    mogdb=# \copy a from stdin;
+    ```
+
+    出现>>符号提示时，输入数据，输入\\.时结束。
+
+    ```sql
+    Enter data to be copied followed by a newline.
+    End with a backslash and a period on a line by itself.
+    >> 1
+    >> 2
+    >> \.
+    ```
+
+    查询导入目标表a的数据。
+
+    ```sql
+    mogdb=# SELECT * FROM a;
+     a
+    ---
+     1
+     2
+    (2 rows)
+    ```
+
+3. 从本地文件拷贝数据到目标表a。假设存在本地文件/home/omm/2.csv。
+
+   - 分隔符为“,”。
+
+   - 在导入过程中，若数据源文件比外表定义的列数多，则忽略行尾多出来的列。
+
+    ```sql
+    mogdb=# \copy a FROM '/home/omm/2.csv' WITH (delimiter',',IGNORE_EXTRA_DATA 'on');
+    ```
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/5-using-gs_restore-to-import-data.md b/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/5-using-gs_restore-to-import-data.md
new file mode 100644
index 0000000000000000000000000000000000000000..ee68bc06ee74c6e487baabb4c8a1c4c028f9d6ec
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/5-using-gs_restore-to-import-data.md
@@ -0,0 +1,272 @@
+---
+title: 使用gs_restore命令导入数据
+summary: 使用gs_restore命令导入数据
+author: Guo Huan
+date: 2021-03-04
+---
+
+# 使用gs_restore命令导入数据
+
+<br/>
+
+## 操作场景
+
+gs_restore是MogDB数据库提供的与gs_dump配套的导入工具。通过该工具，可将gs_dump导出的文件导入至数据库。gs_restore支持导入的文件格式包含自定义归档格式、目录归档格式和tar归档格式。
+
+gs_restore具备如下两种功能。
+
+- 导入至数据库
+
+  如果指定了数据库，则数据将被导入到指定的数据库中。其中，并行导入必须指定连接数据库的密码。导入时生成列会自动更新，并像普通列一样保存。
+
+- 导入至脚本文件
+
+  如果未指定导入数据库，则创建包含重建数据库所需的SQL语句脚本，并将其写入至文件或者标准输出。该脚本文件等效于gs_dump导出的纯文本格式文件。
+
+gs_restore工具在导入时，允许用户选择需要导入的内容，并支持在数据导入前对等待导入的内容进行排序。
+
+<br/>
+
+## 操作步骤
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+> gs_restore默认是以追加的方式进行数据导入。为避免多次导入造成数据异常，在进行导入时，建议选择使用"-c" 和"-e"参数。"-c"表示在重新创建数据库对象前，清理（删除）已存在于将要还原的数据库中的数据库对象；"-e"表示当发送SQL语句到数据库时如果出现错误请退出，默认状态下会继续，且在导入后会显示一系列错误信息。
+
+1. 以操作系统用户omm登录数据库主节点。
+
+2. 使用gs_restore命令，从mogdb整个数据库内容的导出文件中，将数据库的所有对象的定义导入到backupdb。
+
+    ```bash
+    gs_restore -U jack /home/omm/backup/MPPDB_backup.tar -p 8000 -d backupdb -s -e -c
+    Password:
+    ```
+
+    **表 1** 常用参数说明
+
+    | 参数 | 参数说明| 举例           |
+    | :----- | :--------------------| :------------- |
+    | -U   | 连接数据库的用户名。        | -U jack        |
+    | -W   | 指定用户连接的密码。<br/>- 如果主机的认证策略是trust，则不会对数据库管理员进行密码验证，即无需输入-W选项；<br/>- 如果没有-W选项，并且不是数据库管理员，会提示用户输入密码。 | -W abcd@123 |
+    | -d   | 连接数据库dbname，并直接将数据导入到该数据库中。       | -d backupdb    |
+    | -p   | 指定服务器所监听的TCP端口或本地Unix域套接字后缀，以确保连接。                | -p 8000        |
+    | -e   | 当发送SQL语句到数据库时如果出现错误，则退出。默认状态下会忽略错误任务并继续执行导入，且在导入后会显示一系列错误信息。 | -              |
+    | -c   | 在重新创建数据库对象前，清理（删除）已存在于将要导入的数据库中的数据库对象。  | -              |
+    | -s   | 只导入模式定义，不导入数据。当前的序列值也不会被导入。 | -              |
+
+    其他参数说明请参见《参考指南》中“工具参考 > 服务端工具 > [gs_restore](9-gs_restore)”章节。
+
+<br/>
+
+## 示例
+
+示例一：执行gs_restore，导入指定MPPDB_backup.dmp文件（自定义归档格式）中mogdb数据库的数据和对象定义。
+
+```bash
+gs_restore backup/MPPDB_backup.dmp -p 8000 -d backupdb
+gs_restore[2017-07-21 19:16:26]: restore operation successful
+gs_restore: total time: 13053  ms
+```
+
+示例二：执行gs_restore，导入指定MPPDB_backup.tar文件（tar归档格式）中mogdb数据库的数据和对象定义。
+
+```bash
+gs_restore backup/MPPDB_backup.tar -p 8000 -d backupdb
+gs_restore[2017-07-21 19:21:32]: restore operation successful
+gs_restore[2017-07-21 19:21:32]: total time: 21203  ms
+```
+
+示例三：执行gs_restore，导入指定MPPDB_backup目录文件（目录归档格式）中mogdb数据库的数据和对象定义。
+
+```bash
+gs_restore backup/MPPDB_backup -p 8000 -d backupdb
+gs_restore[2017-07-21 19:26:46]: restore operation successful
+gs_restore[2017-07-21 19:26:46]: total time: 21003  ms
+```
+
+示例四：执行gs_restore，将mogdb数据库的所有对象的定义导入至backupdb数据库。导入前，数据库存在完整的定义和数据，导入后，backupdb数据库只存在所有对象定义，表没有数据。
+
+```bash
+gs_restore /home/omm/backup/MPPDB_backup.tar -p 8000 -d backupdb -s -e -c
+gs_restore[2017-07-21 19:46:27]: restore operation successful
+gs_restore[2017-07-21 19:46:27]: total time: 32993  ms
+```
+
+示例五：执行gs_restore，导入MPPDB_backup.dmp文件中PUBLIC模式的所有定义和数据。在导入时会先删除已经存在的对象，如果原对象存在跨模式的依赖则需手工强制干预。
+
+```bash
+gs_restore backup/MPPDB_backup.dmp -p 8000 -d backupdb -e -c -n PUBLIC
+gs_restore: [archiver (db)] Error while PROCESSING TOC:
+gs_restore: [archiver (db)] Error from TOC entry 313; 1259 337399 TABLE table1 gaussdba
+gs_restore: [archiver (db)] could not execute query: ERROR:  cannot drop table table1 because other objects depend on it
+DETAIL:  view t1.v1 depends on table table1
+HINT:  Use DROP ... CASCADE to drop the dependent objects too.
+Command was: DROP TABLE public.table1;
+```
+
+手工删除依赖，导入完成后再重新创建。
+
+```bash
+gs_restore backup/MPPDB_backup.dmp -p 8000 -d backupdb -e -c -n PUBLIC
+gs_restore[2017-07-21 19:52:26]: restore operation successful
+gs_restore[2017-07-21 19:52:26]: total time: 2203  ms
+```
+
+示例六：执行gs_restore，导入MPPDB_backup.dmp文件中hr模式下表hr.staffs的定义。在导入之前，hr.staffs表不存在，需要确保存在hr的schema。
+
+```bash
+gs_restore backup/MPPDB_backup.dmp -p 8000 -d backupdb -e -c -s -n hr -t staffs
+gs_restore[2017-07-21 19:56:29]: restore operation successful
+gs_restore[2017-07-21 19:56:29]: total time: 21000  ms
+```
+
+示例七: 执行gs_restore，导入MPPDB_backup.dmp文件中hr模式下表hr.staffs的数据。在导入之前，hr.staffs表不存在数据，需要确保存在hr的schema。
+
+```bash
+gs_restore backup/MPPDB_backup.dmp -p 8000 -d backupdb -e -a -n hr -t staffs
+gs_restore[2017-07-21 20:12:32]: restore operation successful
+gs_restore[2017-07-21 20:12:32]: total time: 20203  ms
+```
+
+示例八：执行gs_restore，导入指定表hr.staffs的定义。在导入之前，hr.staffs表的数据是存在的。
+
+```sql
+human_resource=# select * from hr.staffs;
+ staff_id | first_name  |  last_name  |  email   |    phone_number    |      hire_date      | employment_id |  salary  | commission_pct | manager_id | section_id
+----------+-------------+-------------+----------+--------------------+---------------------+---------------+----------+----------------+------------+------------
+      200 | Jennifer    | Whalen      | JWHALEN  | 515.123.4444       | 1987-09-17 00:00:00 | AD_ASST       |  4400.00 |                |        101 |         10
+      201 | Michael     | Hartstein   | MHARTSTE | 515.123.5555       | 1996-02-17 00:00:00 | MK_MAN        | 13000.00 |                |        100 |         20
+
+$ gsql -d human_resource -p 8000
+
+gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr
+Non-SSL connection (SSL connection is recommended when requiring high-security)
+Type "help" for help.
+
+human_resource=# drop table hr.staffs CASCADE;
+NOTICE:  drop cascades to view hr.staff_details_view
+DROP TABLE
+
+$ gs_restore /home/omm/backup/MPPDB_backup.tar -p 8000 -d human_resource -n hr -t staffs -s -e
+Password:
+restore operation successful
+total time: 904  ms
+
+human_resource=# select * from hr.staffs;
+ staff_id | first_name | last_name | email | phone_number | hire_date | employment_id | salary | commission_pct | manager_id | section_id
+----------+------------+-----------+-------+--------------+-----------+---------------+--------+----------------+------------+------------
+(0 rows)
+```
+
+示例九：执行gs_restore，导入staffs和areas两个指定表的定义和数据。在导入之前，staffs和areas表不存在。
+
+```sql
+human_resource=# \d
+                                 List of relations
+ Schema |        Name        | Type  |  Owner   |             Storage
+--------+--------------------+-------+----------+----------------------------------
+ hr     | employment_history | table | omm | {orientation=row,compression=no}
+ hr     | employments        | table | omm | {orientation=row,compression=no}
+ hr     | places             | table | omm | {orientation=row,compression=no}
+ hr     | sections           | table | omm | {orientation=row,compression=no}
+ hr     | states             | table | omm | {orientation=row,compression=no}
+(5 rows)
+
+$ gs_restore /home/mogdb/backup/MPPDB_backup.tar -p 8000 -d human_resource -n hr -t staffs -n hr -t areas
+Password:
+restore operation successful
+total time: 724  ms
+
+human_resource=# \d
+                                 List of relations
+ Schema |        Name        | Type  |  Owner   |             Storage
+--------+--------------------+-------+----------+----------------------------------
+ hr     | areas              | table | omm | {orientation=row,compression=no}
+ hr     | employment_history | table | omm | {orientation=row,compression=no}
+ hr     | employments        | table | omm | {orientation=row,compression=no}
+ hr     | places             | table | omm | {orientation=row,compression=no}
+ hr     | sections           | table | omm | {orientation=row,compression=no}
+ hr     | staffs             | table | omm | {orientation=row,compression=no}
+ hr     | states             | table | omm | {orientation=row,compression=no}
+(7 rows)
+
+human_resource=# select * from hr.areas;
+ area_id |       area_name
+---------+------------------------
+       4 | Middle East and Africa
+       1 | Europe
+       2 | Americas
+       3 | Asia
+(4 rows)
+```
+
+示例十：执行gs_restore，导入hr的模式，包含模式下的所有对象定义和数据。
+
+```bash
+gs_restore /home/omm/backup/MPPDB_backup1.dmp -p 8000 -d backupdb -n hr -e
+Password:
+restore operation successful
+total time: 702  ms
+```
+
+示例十一：执行gs_restore，同时导入hr和hr1两个模式，仅导入模式下的所有对象定义。
+
+```bash
+gs_restore /home/omm/backup/MPPDB_backup2.dmp -p 8000 -d backupdb -n hr -n hr1 -s
+Password:
+restore operation successful
+total time: 665  ms
+```
+
+示例十二：执行gs_restore，将human_resource数据库导出文件导入至backupdb数据库中。
+
+```sql
+mogdb=# create database backupdb;
+CREATE DATABASE
+
+$ gs_restore /home/omm/backup/MPPDB_backup.tar -p 8000 -d backupdb
+
+restore operation successful
+total time: 23472  ms
+
+$ gsql -d backupdb -p 8000 -r
+
+gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr
+Non-SSL connection (SSL connection is recommended when requiring high-security)
+Type "help" for help.
+
+backupdb=# select * from hr.areas;
+ area_id |       area_name
+---------+------------------------
+       4 | Middle East and Africa
+       1 | Europe
+       2 | Americas
+       3 | Asia
+(4 rows)
+```
+
+示例十三：用户user1不具备将导出文件中数据导入至数据库backupdb的权限，而角色role1具备该权限，要实现将文件数据导入数据库backupdb，可以在导出命令中设置-role角色为role1，使用role1的权限，完成导出目的。
+
+```sql
+human_resource=# CREATE USER user1 IDENTIFIED BY "1234@abc";
+CREATE ROLE role1 with SYSADMIN IDENTIFIED BY "abc@1234";
+
+$ gs_restore -U user1 /home/omm/backup/MPPDB_backup.tar -p 8000 -d backupdb --role role1 --rolepassword abc@1234
+Password:
+restore operation successful
+total time: 554  ms
+
+$ gsql -d backupdb -p 8000 -r
+
+gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr
+Non-SSL connection (SSL connection is recommended when requiring high-security)
+Type "help" for help.
+
+backupdb=# select * from hr.areas;
+ area_id |       area_name
+---------+------------------------
+       4 | Middle East and Africa
+       1 | Europe
+       2 | Americas
+       3 | Asia
+(4 rows)
+```
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/6-updating-data-in-a-table.md b/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/6-updating-data-in-a-table.md
new file mode 100644
index 0000000000000000000000000000000000000000..82cea08f09f6af2c474c84ee3f9c226689eefeb9
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/6-updating-data-in-a-table.md
@@ -0,0 +1,176 @@
+---
+title: 更新表中数据
+summary: 更新表中数据
+author: Guo Huan
+date: 2021-03-04
+---
+
+# 更新表中数据
+
+<br/>
+
+## 使用DML命令更新表
+
+MogDB支持标准的数据库操作语言（DML）命令，对表进行更新。
+
+<br/>
+
+### 操作步骤
+
+假设存在表customer_t，表结构如下:
+
+```sql
+CREATE TABLE customer_t
+( c_customer_sk             integer,
+  c_customer_id             char(5),
+  c_first_name              char(6),
+  c_last_name               char(8)
+) ;
+```
+
+可以使用如下DML命令对表进行数据更新。
+
+- 使用INSERT向表中插入数据。
+
+  - 向表customer_t中插入一行。
+
+    ```sql
+    INSERT INTO customer_t (c_customer_sk, c_customer_id, c_first_name,c_last_name) VALUES (3769, 5, 'Grace','White');
+    ```
+
+  - 向表customer_t中插入多行数据。
+
+    ```sql
+    INSERT INTO customer_t (c_customer_sk, c_customer_id, c_first_name,c_last_name) VALUES
+    (6885, 1, 'Joes', 'Hunter'),
+    (4321, 2, 'Lily','Carter'),
+    (9527, 3, 'James', 'Cook'),
+    (9500, 4, 'Lucy', 'Baker');
+    ```
+
+    更多关于INSERT的使用方法，请参见向表中插入数据。
+
+- 使用UPDATE更新表中数据。修改字段c_customer_id值为0。
+
+    ```sql
+    UPDATE customer_t SET c_customer_id = 0;
+    ```
+
+    更多关于UPDATE的使用方法，请参见UPDATE。
+
+- 使用DELETE删除表中的行。
+
+    可以使用WHERE子句指定需要删除的行，若不指定即删除表中所有的行，只保留数据结构。
+
+    ```sql
+    DELETE FROM customer_t WHERE c_last_name = 'Baker';
+    ```
+
+    更多关于DELETE的使用方法，请参见DELETE。
+
+- 使用TRUNCATE命令快速从表中删除所有的行。
+
+    ```sql
+    TRUNCATE TABLE customer_t;
+    ```
+
+    更多关于TRUNCATE的使用方法，请参见TRUNCATE。
+
+    删除表时，DELETE语句每次删除一行数据而TRUNCATE语句是通过释放表存储的数据页来删除数据，使用TRUNCATE语句比使用DELETE语句更加快速。
+
+    使用DELETE语句删除表时，仅删除数据，不释放存储空间。使用TRUNCATE语句删除表时，删除数据且释放存储空间。
+
+<br/>
+
+## 使用合并方式更新和插入数据
+
+在用户需要将一个表中所有的数据或大量的数据添加至现有表的场景下，MogDB提供了MERGE INTO语句通过两个表合并的方式高效地将新数据添加到现有表。
+
+MERGE INTO语句将目标表和源表中数据针对关联条件进行匹配，若关联条件匹配时对目标表进行UPDATE，关联条件不匹配时对目标表执行INSERT。此方法可以很方便地用来将两个表合并执行UPDATE和INSERT，避免多次执行。
+
+<br/>
+
+### 前提条件
+
+进行MERGE INTO操作的用户需要同时拥有目标表的UPDATE和INSERT权限，以及源表的SELECT权限。
+
+<br/>
+
+### 操作步骤
+
+1. 创建源表products，并插入数据。
+
+    ```sql
+    mogdb=# CREATE TABLE products
+    ( product_id INTEGER,
+      product_name VARCHAR2(60),
+      category VARCHAR2(60)
+    );
+
+    mogdb=# INSERT INTO products VALUES
+    (1502, 'olympus camera', 'electrncs'),
+    (1601, 'lamaze', 'toys'),
+    (1666, 'harry potter', 'toys'),
+    (1700, 'wait interface', 'books');
+    ```
+
+2. 创建目标表newproducts，并插入数据。
+
+    ```sql
+    mogdb=# CREATE TABLE newproducts
+    ( product_id INTEGER,
+      product_name VARCHAR2(60),
+      category VARCHAR2(60)
+    );
+
+    mogdb=# INSERT INTO newproducts VALUES
+    (1501, 'vivitar 35mm', 'electrncs'),
+    (1502, 'olympus ', 'electrncs'),
+    (1600, 'play gym', 'toys'),
+    (1601, 'lamaze', 'toys'),
+    (1666, 'harry potter', 'dvd');
+    ```
+
+3. 使用MERGE INTO 语句将源表products的数据合并至目标表newproducts。
+
+    ```sql
+    MERGE INTO newproducts np
+    USING products p
+    ON (np.product_id = p.product_id )
+    WHEN MATCHED THEN
+      UPDATE SET np.product_name = p.product_name, np.category = p.category
+    WHEN NOT MATCHED THEN
+      INSERT VALUES (p.product_id, p.product_name, p.category) ;
+    ```
+
+    上述语句中使用的参数说明，请见[表1](#MERGE INTO语句参数说明)。更多信息，请参见MERGE INTO。
+
+    **表 1** MERGE INTO语句参数说明<a id="MERGE INTO语句参数说明"> </a>
+
+    | 参数                 | 说明| 举例 |
+    | :--------------- | :------------- | :--------------|
+    | INTO 子句            | 指定需要更新或插入数据的目标表。<br/>目标表支持指定别名。 | **取值:**newproducts np<br/>**说明:**名为newproducts，别名为np的目标表。          |
+    | USING子句            | 指定源表。源表支持指定别名。                       | **取值:**products p<br/>**说明:**名为products，别名为p的源表。                   |
+    | ON子句               | 指定目标表和源表的关联条件。<br/>关联条件中的字段不支持更新。  | **取值:**np.product_id = p.product_id<br/>**说明:**指定的关联条件为，目标表newproducts的product_id字段和源表products的product_id字段相等。                      |
+    | WHEN MATCHED子句     | 当源表和目标表中数据针对关联条件可以匹配上时，选择WHEN MATCHED子句进行UPDATE操作。<br/>- 仅支持指定一个WHEN MATCHED子句。<br/>- WHEN MATCHED子句可缺省，缺省时，对于满足ON子句条件的行，不进行任何操作。<br/>- 若目标表中存在分布列，则该列不支持更新。                | **取值:**WHEN MATCHED THEN UPDATE SET np.product_name = p.product_name, np.category = p.category<br/>**说明:**当满足ON子句条件时，将目标表newproducts的product_name、category字段的值替换为源表products相对应字段的值。 |
+    | WHEN NOT MATCHED子句 | 当源表和目标表中数据针对关联条件无法匹配时，选择WHEN NOT MATCHED子句进行INSERT操作。<br/>- 仅支持指定一个WHEN NOT MATCHED子句。<br/>- WHEN NOT MATCHED子句可缺省。<br/>- 不支持INSERT子句中包含多个VALUES。<br/>- WHEN MATCHED和WHEN NOT MATCHED子  句顺序可以交换，可以缺省其中一个，但不能同时缺省。 | **取值:**WHEN NOT MATCHED THENINSERT VALUES (p.product_id, p.product_name, p.category)<br/>**说明:**将源表products中，不满足ON子句条件的行插入目标表newproducts。 |
+
+4. 查询合并后的目标表newproducts。
+
+    ```sql
+    SELECT * FROM newproducts;
+    ```
+
+   返回信息如下:
+
+    ```sql
+     product_id |  product_name  | category
+    ------------+----------------+-----------
+          1501 | vivitar 35mm   | electrncs
+          1502 | olympus camera | electrncs
+          1666 | harry potter   | toys
+          1600 | play gym       | toys
+          1601 | lamaze         | toys
+          1700 | wait interface | books
+    (6 rows)
+    ```
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/7-deep-copy.md b/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/7-deep-copy.md
new file mode 100644
index 0000000000000000000000000000000000000000..4eee90773d175998a02339186e94fe327cda56b8
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/7-deep-copy.md
@@ -0,0 +1,122 @@
+---
+title: 深层复制
+summary: 深层复制
+author: Guo Huan
+date: 2021-03-04
+---
+
+# 深层复制
+
+数据导入后，如果需要修改表的分区键、或者将行存表改列存、添加PCK（Partial Cluster Key）约束等场景下，可以使用深层复制的方式对表进行调整。深层复制是指重新创建表，然后使用批量插入填充表的过程。
+
+Mog提供了三种深层复制的方式供用户选择。
+
+<br/>
+
+## 使用CREATE TABLE执行深层复制
+
+该方法使用CREATE TABLE语句创建原始表的副本，将原始表的数据填充至副本并重命名副本，完成原始表的复制。
+
+在创建新表时，可以指定表以及列属性，比如主键。
+
+**操作步骤**
+
+执行如下步骤对表customer_t进行深层复制。
+
+1. 使用CREATE TABLE语句创建表customer_t的副本customer_t_copy。
+
+    ```sql
+    CREATE TABLE customer_t_copy
+    ( c_customer_sk             integer,
+      c_customer_id             char(5),
+      c_first_name              char(6),
+      c_last_name               char(8)
+    ) ;
+    ```
+
+2. 使用INSERT INTO…SELECT语句向副本填充原始表中的数据。
+
+    ```sql
+    INSERT INTO customer_t_copy (SELECT * FROM customer_t);
+    ```
+
+3. 删除原始表。
+
+    ```sql
+    DROP TABLE customer_t;
+    ```
+
+4. 使用ALTER TABLE语句将副本重命名为原始表名称。
+
+    ```sql
+    ALTER TABLE customer_t_copy RENAME TO customer_t;
+    ```
+
+<br/>
+
+## 使用CREATE TABLE LIKE执行深层复制
+
+该方法使用CREATE TABLE LIKE语句创建原始表的副本，将原始表的数据填充至副本并重命名副本，完成原始表的复制。该方法不继承父表的主键属性，您可以使用ALTER TABLE语句来添加它们。
+
+**操作步骤**
+
+1. 使用CREATE TABLE LIKE语句创建表customer_t的副本customer_t_copy。
+
+    ```sql
+    CREATE TABLE customer_t_copy (LIKE customer_t);
+    ```
+
+2. 使用INSERT INTO…SELECT语句向副本填充原始表中的数据。
+
+    ```sql
+    INSERT INTO customer_t_copy (SELECT * FROM customer_t);
+    ```
+
+3. 删除原始表。
+
+    ```sql
+    DROP TABLE customer_t;
+    ```
+
+4. 使用ALTER TABLE语句将副本重命名为原始表名称。
+
+    ```sql
+    ALTER TABLE customer_t_copy RENAME TO customer_t;
+    ```
+
+<br/>
+
+## 通过创建临时表并截断原始表来执行深层复制
+
+该方法使用CREATE TABLE AS语句创建原始表的临时表，然后截断原始表并从临时表填充它完成原始表的深层复制。
+
+在新建表需要保留父表的主键属性，或如果父表具有依赖项的情况下，建议使用此方法。
+
+**操作步骤**
+
+1. 使用CREATE TABLE AS语句创建表customer_t的临时表副本customer_t_temp。
+
+    ```sql
+    CREATE TEMP TABLE customer_t_temp AS SELECT * FROM customer_t;
+    ```
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+    > 与使用永久表相比，使用临时表可以提高性能，但存在丢失数据的风险。临时表只在当前会话可见，本会话结束后将自动删除。如果数据丢失是不可接受的，请使用永久表。
+
+2. 截断当前表customer_t。
+
+    ```sql
+    TRUNCATE customer_t;
+    ```
+
+3. 使用INSERT INTO…SELECT语句从副本中向原始表中填充数据。
+
+    ```sql
+    INSERT INTO customer_t (SELECT * FROM customer_t_temp);
+    ```
+
+4. 删除临时表副本customer_t_temp。
+
+    ```sql
+    DROP TABLE customer_t_temp;
+    ```
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/8-ANALYZE-table.md b/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/8-ANALYZE-table.md
new file mode 100644
index 0000000000000000000000000000000000000000..93aad56134dede0198103d19145a1fc88879ffc9
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/8-ANALYZE-table.md
@@ -0,0 +1,50 @@
+---
+title: 分析表
+summary: 分析表
+author: Guo Huan
+date: 2021-03-04
+---
+
+# 分析表
+
+执行计划生成器需要使用表的统计信息，以生成最有效的查询执行计划，提高查询性能。因此数据导入完成后，建议执行ANALYZE语句生成最新的表统计信息。统计结果存储在系统表PG_STATISTIC中。
+
+<br/>
+
+## 分析表
+
+ANALYZE支持的表类型有行/列存表。ANALYZE同时也支持对本地表的指定列进行信息统计。下面以表的ANALYZE为例，更多关于ANALYZE的信息，请参见[ANALYZE | ANALYSE](32-ANALYZE-ANALYSE)。
+
+更新表统计信息。
+
+以表product_info为例，ANALYZE命令如下:
+
+```sql
+ANALYZE product_info;
+```
+
+```sql
+ANALYZE
+```
+
+<br/>
+
+## 表自动分析
+
+MogDB提供了GUC参数autovacuum用于控制数据库自动清理功能的启动。
+
+autovacuum设置为on时，系统定时启动autovacuum线程来进行表自动分析，如果表中数据量发生较大变化达到阈值时，会触发表自动分析，即autoanalyze。
+
+- 对于空表而言，当表中插入数据的行数大于50时，会触发表自动进行ANALYZE。
+- 对于表中已有数据的情况，阈值设定为50+10%*reltuples，其中reltuples是表的总行数。
+
+autovacuum自动清理功能的生效还依赖于下面两个GUC参数:
+
+- track_counts 参数需要设置为on，表示开启收集收据库统计数据功能。
+- autovacuum_max_workers参数需要大于0，该参数表示能同时运行的自动清理线程的最大数量。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+>
+> - autoanalyze只支持默认采样方式，不支持百分比采样方式。
+> - 多列统计信息仅支持百分比采样，因此autoanalyze不收集多列统计信息。
+> - autoanalyze支持行存表和列存表，不支持外表、临时表、unlogged表和toast表。
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/9-doing-VACUUM-to-a-table.md b/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/9-doing-VACUUM-to-a-table.md
new file mode 100644
index 0000000000000000000000000000000000000000..7eba671698f9ca38bb54e8e24e796841af013909
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/importing-and-exporting-data/importing-data/9-doing-VACUUM-to-a-table.md
@@ -0,0 +1,22 @@
+---
+title: 对表执行VACUUM
+summary: 对表执行VACUUM
+author: Guo Huan
+date: 2021-03-04
+---
+
+# 对表执行VACUUM
+
+如果导入过程中，进行了大量的更新或删除行时，应运行VACUUM FULL命令，然后运行ANALYZE命令。大量的更新和删除操作，会产生大量的磁盘页面碎片，从而逐渐降低查询的效率。VACUUM FULL可以将磁盘页面碎片恢复并交还操作系统。
+
+对表执行VACUUM FULL。
+
+以表product_info为例，VACUUM FULL命令如下:
+
+```sql
+VACUUM FULL product_info
+```
+
+```sql
+VACUUM
+```
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/1-introducing-mot/1-mot-introduction.md b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/1-introducing-mot/1-mot-introduction.md
new file mode 100644
index 0000000000000000000000000000000000000000..82a383ff782c917c5d185de9202ad5788bfe71d6
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/1-introducing-mot/1-mot-introduction.md
@@ -0,0 +1,29 @@
+---
+title: MOT简介
+summary: MOT简介
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# MOT简介
+
+MogDB引入了MOT存储引擎，它是一种事务性行存储，针对多核和大内存服务器进行了优化。MOT是MogDB数据库最先进的生产级特性（Beta版本），它为事务性工作负载提供更高的性能。MOT完全支持ACID特性，并包括严格的持久性和高可用性支持。企业可以在关键任务、性能敏感的在线事务处理（OLTP）中使用MOT，以实现高性能、高吞吐、可预测低延迟以及多核服务器的高利用率。MOT尤其适合在多路和多核处理器的现代服务器上运行，例如基于Arm/鲲鹏处理器的华为TaiShan服务器，以及基于x86的戴尔或类似服务器。
+
+**图 1** MogDB内存优化存储引擎<a id="neicun"></a>
+
+![mogdb内存优化存储引擎](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-introduction-1.png)
+
+如[图1](#neicun)所示，MogDB数据库内存优化存储引擎组件（绿色部分）负责管理MOT和事务。
+
+MOT与基于磁盘的普通表并排创建。MOT的有效设计实现了几乎完全的SQL覆盖，并且支持完整的数据库功能集，如存储过程和自定义函数（限制参见[MOT SQL覆盖和限制](4-mot-usage#mot-sql覆盖和限制)）。
+
+通过完全存储在内存中的数据和索引、非统一内存访问感知（NUMA-aware）设计、消除锁和锁存争用的算法以及查询原生编译，MOT可提供更快的数据访问和更高效的事务执行。
+
+MOT有效的几乎无锁的设计和高度调优的实现，使其在多核服务器上实现了卓越的近线性吞吐量扩展，这可能是业界最好的。
+
+MOT完全支持ACID特性：
+
+- 原子性（Atomicity）：原子事务是一系列不可分割的数据库操作。在事务完成（分别提交或中止）之后，这些操作要么全部发生，要么全部不发生。
+- 一致性（Consistency）：事务结束后，数据库处于一致状态，保留数据完整性。
+- 隔离性（Isolation）：事务之间不能相互干扰。MOT支持不同的重复读和读提交隔离级别。在下一个版本中，MOT还将支持可序列化隔离。更多信息，请参见[MOT隔离级别](3-2#mot隔离级别)。
+- 持久性（Durability）：即使发生崩溃和失败，成功完成（提交）的事务效果持久保存。MOT完全集成了MogDB的基于WAL的日志记录。同时支持同步和异步日志记录选项。MOT还支持同步+面向NUMA优化的组提交。更多信息，请参见[MOT持久性概念](3-6)。
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/1-introducing-mot/2-mot-features-and-benefits.md b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/1-introducing-mot/2-mot-features-and-benefits.md
new file mode 100644
index 0000000000000000000000000000000000000000..f46cfdd2fa4bd716ac0f08ecbf120f56eaffb5af
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/1-introducing-mot/2-mot-features-and-benefits.md
@@ -0,0 +1,22 @@
+---
+title: MOT特性及价值
+summary: MOT特性及价值
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# MOT特性及价值
+
+MOT在高性能（查询和事务延迟）、高可扩展性（吞吐量和并发量）以及高资源利用率（某些程度上节约成本）方面拥有显著优势。
+
+- 低延迟（Low Latency）：提供快速的查询和事务响应时间。
+- 高吞吐量（High Throughput）：支持峰值和持续高用户并发。
+- 高资源利用率（High Resource Utilization）：充分利用硬件。
+
+使用了MOT的应用程序可以达到普通表2.5到4倍的吞吐量。例如，在基于Arm/鲲鹏的华为TaiShan服务器和基于英特尔至强的戴尔x86服务器上，执行TPC-C基准测试（交互事务和同步日志），MOT提供的吞吐率增益在2路服务器上达到2.5倍，4路服务器上达到3.7倍，在4路256核Arm服务器上达到480万tpmC。
+
+在TPC-C基准测试中可观察到，MOT提供更低的延迟，将事务处理速度提升了3至5.5倍。
+
+此外，高负载和高争用的场景是所有领先的行业数据库都会遇到的公认问题，而MOT能够在这种情况下极高地利用服务器资源。使用MOT后，4路服务器的资源利用率达到99%，远远领先其他行业数据库。
+
+这种能力在现代的多核服务器上尤为明显和重要。
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/1-introducing-mot/3-mot-key-technologies.md b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/1-introducing-mot/3-mot-key-technologies.md
new file mode 100644
index 0000000000000000000000000000000000000000..48201108a58d36ed838747f0fe4fc9c0bebad01a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/1-introducing-mot/3-mot-key-technologies.md
@@ -0,0 +1,24 @@
+---
+title: MOT关键技术
+summary: MOT关键技术
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# MOT关键技术
+
+MOT的关键技术如下：
+
+- 内存优化数据结构：以实现高并发吞吐量和可预测的低延迟为目标，所有数据和索引都在内存中，不使用中间页缓冲区，并使用持续时间最短的锁。数据结构和所有算法都是专门为内存设计而优化的。
+- 免锁事务管理：MOT在保证严格一致性和数据完整性的前提下，采用乐观的策略实现高并发和高吞吐。在事务过程中，MOT不会对正在更新的数据行的任何版本加锁，从而大大降低了一些大内存系统中的争用。事务中的乐观并发控制（Optimistic Concurrency Control，OCC）语句是在没有锁的情况下实现的，所有的数据修改都是在内存中专门用于私有事务的部分（也称为私有事务内存）中进行的。这就意味着在事务过程中，相关数据在私有事务内存中更新，从而实现了无锁读写；而且只有在提交阶段才会短时间加锁。更多详细信息，请参见[MOT并发控制机制](3-2)。
+- 免锁索引：由于内存表的数据和索引完全存储在内存中，因此拥有一个高效的索引数据结构和算法非常重要。MOT索引机制基于最先进的Masstree，这是一种用于多核系统的快速和可扩展的键值（Key Value，KV）存储索引，以B+树的Trie实现。通过这种方式，高并发工作负载在多核服务器上可以获得卓越的性能。同时MOT应用了各种先进的技术以优化性能，如优化锁方法、高速缓存感知和内存预取。
+- NUMA-aware的内存管理：MOT内存访问的设计支持非统一内存访问（NUMA）感知。NUMA-aware算法增强了内存中数据布局的性能，使线程访问物理上连接到线程运行的核心的内存。这是由内存控制器处理的，不需要通过使用互连（如英特尔QPI）进行额外的跳转。MOT的智能内存控制模块，为各种内存对象预先分配了内存池，提高了性能，减少了锁，保证了稳定性。事务的内存对象的分配始终是NUMA本地的。本地处理的对象会返回到池中。同时在事务中尽量减少系统内存分配（OS malloc）的使用，避免不必要的锁。
+- 高效持久性：日志和检查点是实现磁盘持久化的关键能力，也是ACID的关键要求之一（D代表持久性）。目前所有的磁盘（包括SSD和NVMe）都明显慢于内存，因此持久化是基于内存数据库引擎的瓶颈。作为一个基于内存的存储引擎，MOT的持久化设计必须实现各种各样的算法优化，以确保持久化的同时还能达到设计时的速度和吞吐量目标。这些优化包括：
+  - 并行日志，所有MogDB磁盘表都支持。
+  - 每个事务的日志缓冲和无锁事务准备。
+  - 增量更新记录，即只记录变化。
+  - 除了同步和异步之外，创新的NUMA感知组提交日志记录。
+  - 最先进的数据库检查点（CALC）使内存和计算开销降到最低。
+- 高SQL覆盖率和功能集：MOT通过扩展的PostgreSQL外部数据封装（FDW）以及索引，几乎支持完整的SQL范围，包括存储过程、用户定义函数和系统函数调用。有关不支持的功能的列表，请参阅[MOT SQL覆盖和限制](4-mot-usage#mot-sql覆盖和限制)。
+- 使用PREPARE语句的查询原生编译：通过使用PREPARE客户端命令，可以以交互方式执行查询和事务语句。这些命令已被预编译成原生执行格式，也称为Code-Gen或即时（Just-in-Time，JIT）编译。这样可以实现平均30%的性能提升。在可能的情况下，应用编译和轻量级执行；否则，使用标准执行路径处理适用的查询。Cache Plan模块已针对OLTP进行了优化，在整个会话中甚至使用不同的绑定设置以及在不同的会话中重用编译结果。
+- MOT和MogDB数据库的无缝集成：MOT是一个高性能的面向内存优化的存储引擎，已集成在MogDB包中。MOT的主内存引擎和基于磁盘的存储引擎并存，以支持多种应用场景，同时在内部重用数据库辅助服务，如WAL重做日志、复制、检查点和恢复高可用性等。用户可以从基于磁盘的表和MOT的统一部署、配置和访问中受益。根据特定需求，灵活且低成本地选择使用哪种存储引擎。例如，把会导致瓶颈的高度性能敏感数据放入内存中。
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/1-introducing-mot/4-mot-usage-scenarios.md b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/1-introducing-mot/4-mot-usage-scenarios.md
new file mode 100644
index 0000000000000000000000000000000000000000..2e890b323526cb4d1c36926b7787d47737fcc925
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/1-introducing-mot/4-mot-usage-scenarios.md
@@ -0,0 +1,22 @@
+---
+title: MOT应用场景
+summary: MOT应用场景
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# MOT应用场景
+
+MOT可以根据负载的特点，显著加快应用程序的整体性能。MOT通过提高数据访问和事务执行的效率，并通过消除并发执行事务之间的锁和锁存争用，最大程度地减少重定向，从而提高了事务处理的性能。
+
+MOT的极速不仅因为它在内存中，还因为它围绕并发内存使用管理进行了优化。数据存储、访问和处理算法从头开始设计，以利用内存和高并发计算的最新先进技术。
+
+MogDB允许应用程序随意组合MOT和基于标准磁盘的表。对于启用已证明是瓶颈的最活跃、高争用和对性能敏感的应用程序表，以及需要可预测的低延迟访问和高吞吐量的表来说，MOT特别有用。
+
+MOT可用于各种应用，例如：
+
+- 高吞吐事务处理：这是使用MOT的主要场景，因为它支持海量事务，同时要求单个事务的延迟较低。这类应用的例子有实时决策系统、支付系统、金融工具交易、体育博彩、移动游戏、广告投放等。
+- 性能瓶颈加速：存在高争用现象的表可以通过使用MOT受益，即使该表是磁盘表。由于延迟更低、竞争和锁更少以及服务器吞吐量能力增加，此类表（除了相关表和在查询和事务中一起引用的表之外）的转换使得性能显著提升。
+- 消除中间层缓存：云计算和移动应用往往会有周期性或峰值的高工作负载。此外，许多应用都有80%以上负载是读负载，并伴有频繁的重复查询。为了满足峰值负载单独要求，以及降低响应延迟提供最佳的用户体验，应用程序通常会部署中间缓存层。这样的附加层增加了开发的复杂性和时间，也增加了运营成本。 MOT提供了一个很好的替代方案，通过一致的高性能数据存储来简化应用架构，缩短开发周期，降低CAPEX和OPEX成本。
+- 大规模流数据提取：MOT可以满足云端（针对移动、M2M和物联网）、事务处理（Transactional Processing，TP）、分析处理（Analytical Processing，AP）和机器学习（Machine Learning，ML）的大规模流数据的提取要求。MOT尤其擅长持续快速地同时提取来自许多不同来源的大量数据。这些数据可以在以后进行处理、转换，并在速度较慢的基于磁盘的表中进行移动。另外，MOT还可以查询到一致的、最新的数据，从而得出实时结果。在有许多实时数据流的物联网和云计算应用中，通常会有专门的数据摄取和处理。例如，一个Apache Kafka集群可以用来提取10万个事件/秒的数据，延迟为10ms。一个周期性的批处理任务会将收集到的数据收集起来，并将转换格式，放入关系型数据库中进行进一步分析。MOT可以通过将数据流直接存储在MOT关系表中，为分析和决策做好准备，从而支持这样的场景（同时消除单独的数据处理层）。这样可以更快地收集和处理数据，MOT避免了代价高昂的分层和缓慢的批处理，提高了一致性，增加了分析数据的实时性，同时降低了总拥有成本（Total Cost of Ownership，TCO）。
+- 降低TCO：提高资源利用率和消除中间层可以节省30%到90%的TCO。
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/1-introducing-mot/5-mot-performance-benchmarks.md b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/1-introducing-mot/5-mot-performance-benchmarks.md
new file mode 100644
index 0000000000000000000000000000000000000000..1f61899182b4ff4cc02493d7be2756970533662e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/1-introducing-mot/5-mot-performance-benchmarks.md
@@ -0,0 +1,204 @@
+---
+title: MOT性能基准
+summary: MOT性能基准
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# MOT性能基准
+
+我们的性能测试是基于业界和学术界通用的TPC-C基准。
+
+测试使用了BenchmarkSQL（请参见[MOT样例TPC-C基准](6-mot-sample-tpcc-benchmark)），并且使用交互式SQL命令而不是存储过程来生成工作负载。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 使用存储过程方法可能会产生更高的性能结果，因为它需要大大减少网络往返和数据库封装SQL处理周期。
+
+评估MogDB MOT性能和磁盘性能的所有测试都使用了同步日志记录和在MOT中优化的group-commit=on版本。
+
+最后我们进行了额外测试，评估MOT快速采集大量数据的能力，并将其作为中间层数据采集解决方案的替代方案。
+
+2020年6月完成全部测试。
+
+下面是各种类型的MOT性能基准。
+
+<br/>
+
+## MOT硬件
+
+本次测试使用的服务器满足10GbE组网和以下配置：
+
+- 基于Arm64/鲲鹏920的2路服务器，型号为TaiShan 2280 v2（128核），800GB RAM，1TB NVMe盘。服务器详细规格参见[此页面](https://e.huawei.com/cn/products/servers/taishan-server/taishan-2480-v2)。操作系统为openEuler。
+- 基于Arm64/鲲鹏960的4路服务器，型号为TaiShan 2480 v2（256核），512GB RAM，1TB NVMe盘。服务器详细规格参见[此页面](https://e.huawei.com/cn/products/servers/taishan-server/taishan-2480-v2)。操作系统为openEuler。
+- 戴尔x86服务器，2路英特尔至强金牌6154 CPU @ 3Ghz，18核（超线程开启时共72核），1TB RAM，1TB SSD。操作系统为CentOS 7.6。
+- x86超微服务器，8路英特尔（R）至强（R） CPU E7-8890 v4 @ 2.20GHz，24核（超线程开启共384核），1TB RAM，1.2 TB SSD（希捷1200 SSD 200GB，SAS 12Gb/s）。操作系统为Ubuntu 16.04.2 LTS。
+- 华为x86服务器，4路英特尔（R）至强（R） CPU E7-8890 v4 @ 2.2Ghz（超线程开启共96核），512GB RAM，SSD 2TB。操作系统为CentOS 7.6。
+
+<br/>
+
+## MOT测试总结
+
+MOT比磁盘表性能提升2.5至4.1倍，在Arm/鲲鹏256核服务器上达到480万tpmC。测试结果清楚表明MOT在扩展和利用所有硬件资源方面的卓越能力。随着CPU槽位和服务器核数增加，性能会随之跃升。
+
+MOT在Arm/鲲鹏架构下最高可达3万tpmC/核，在x86架构下最高可达4万tpmC/核。
+
+由于持久性机制更高效，MOT中的复制开销在Arm/鲲鹏主备高可用场景下为7%，在x86服务器中为2%。而磁盘表的开销在Arm/鲲鹏中为20%，在x86中为15%。
+
+最终，MOT延迟降低2.5倍，TPC-C事务响应速度提升2至7倍。
+
+<br/>
+
+## MOT高吞吐量
+
+MOT高吞吐量测试结果如下。
+
+<br/>
+
+### Arm/鲲鹏2路128核
+
+- **性能**
+
+  下图是华为Arm/鲲鹏2路128核服务器TPC-C基准测试的结果。
+
+  一共进行了四类测试：
+
+  - MOT和MogDB基于磁盘的表各进行了2次测试。
+  - 其中两项测试是在单节点（无高可用性）上执行，这意味着没有向备节点执行复制。其余两个测试在主备节点（有高可用性）上执行，即写入主节点的数据被复制到备节点。
+
+  MOT用橙色表示，基于磁盘的表用蓝色表示。
+
+  **图 1** Arm/鲲鹏2路128核性能基准
+
+  ![Arm-鲲鹏2路128核性能基准](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-performance-benchmarks-1.png)
+
+  结果表明：
+
+  - 正如预期的那样，在所有情况下，MOT的性能明显高于基于磁盘的表。
+  - 单节点：MOT性能为380万tpmC，而基于磁盘的表为150万tpmC。
+  - 主备节点：MOT性能为350万tpmC，而基于磁盘的表为120万tpmC。
+  - 相比单节点（无高可用性，无复制），在有复制需求的生产级（高可用性）服务器（主备节点）上，使用MOT的好处更显著。
+  - 同在主备高可用场景下，MOT复制开销：Arm/鲲鹏为7%，x86为2%；而基于磁盘的表复制开销：Arm/鲲鹏为20%；x86为15%。
+
+- **单CPU核性能**
+
+  下图是华为Arm/鲲鹏服务器2路128核的单核TPC-C基准性能/吞吐量测试结果。同样地，一共进行了四类测试：
+
+  **图 2** Arm/鲲鹏2路128核的单核性能标杆
+
+  ![Arm-鲲鹏2路128核的单核性能标杆](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-performance-benchmarks-2.png)
+
+  结果表明，正如预期的那样，在所有情况下，MOT的单核性能明显高于基于磁盘的表。相比单节点（无高可用性，无复制），在有复制需求的生产级（高可用性）服务器（主备节点）上，使用MOT的好处更显著。
+
+<br/>
+
+### Arm/鲲鹏4路256核
+
+下面通过单连接数的tpmC来展示MOT出色的并发控制性能。
+
+**图 3** Arm/鲲鹏4路256核性能基准
+
+![Arm-鲲鹏4路256核性能基准](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-performance-benchmarks-3.png)
+
+结果表明，随着核数增多，性能也显著提高，在768核时性能达到480万tpmC的峰值。
+
+<br/>
+
+### x86服务器
+
+- **8路384核**
+
+下面通过比较基于磁盘的表和MOT之间单连接数的tpmC，来展示MOT出色的并发控制性能。本次测试以8路384核x86服务器为例。橙色表示MOT的结果。
+
+**图 4** 8路384核x86服务器性能基准
+
+![8路384核x86服务器性能基准](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-performance-benchmarks-4.png)
+
+结果表明，在386核服务器上，MOT的性能明显优于基于磁盘的表，并且单核性能非常高，达到300万tpmC/核。
+
+- **4路96核**
+
+在4路96核服务器上，MOT实现了390万tpmC。下图展示了高效MOT的单核性能达到4万tpmC/核。
+
+**图 5** 4路96核服务器性能基准
+
+![4路96核服务器性能基准](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-performance-benchmarks-5.png)
+
+<br/>
+
+## MOT低延迟
+
+以下是在Arm/鲲鹏两路服务器（128核）上进行测试的结果。单位为毫秒（ms）。
+
+**图 1** 低延迟（90th%）性能基准
+
+![低延迟（90th-）性能基准](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-performance-benchmarks-6.png)
+
+MOT的平均事务速度为2.5倍，MOT延迟为10.5ms，而基于磁盘的表延迟为23至25ms。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 计算平均数时，已考虑TPC-C的5个事务分布占比。有关更多信息，请参阅[MOT样例TPC-C基准](6-mot-sample-tpcc-benchmark)中关于TPC-C事务的说明。
+
+**图 2** 低延迟（90th%，事务平均）性能基准
+
+![低延迟（90th-事务平均）性能基准](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-performance-benchmarks-7.png)
+
+<br/>
+
+## MOT恢复时间目标（RTO）和冷启动时间
+
+### 高可用RTO
+
+MOT完全集成到MogDB中，包括支持主备部署的高可用场景。WAL重做日志的复制机制将把复制更改到数据库备节点并使用备节点进行重放。
+
+如果故障转移事件发生，无论是由于计划外的主节点故障还是由于计划内的维护事件，备节点都会迅速活跃。恢复和重放WAL重做日志以及启用连接所需的时间也称为恢复时间目标（RTO）。
+
+**MogDB（包括MOT）的RTO小于10秒。**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 灾难发生后必须恢复业务流程，避免导致连续性中断相关的不可接受的后果，而RTO表示的就是这段流程的持续时间和业务级别。换句话说，RTO就是在回答这个问题：在通知业务流程中断后，需要多长时间才能恢复？
+
+另外，从[MOT高吞吐量](#mot高吞吐量)的MOT中可以看出，在Arm/鲲鹏架构下，主从高可用场景复制开销仅为7%，在x86架构下仅为2%，而基于磁盘的表复制开销为2%。Arm/鲲鹏机型为20%，x86机型为15%。
+
+<br/>
+
+### 冷启动恢复时间
+
+冷启动恢复时间是指系统从停止模式到能够完全运行所需的时间。在内存数据库中，这包括将所有数据和索引加载到内存中的时间，因此它取决于数据大小、硬件带宽和软件算法能否高效地处理这些数据。
+
+MOT测试使用40 GB/s的ARM磁盘测试，可以在100 GB/s的时间内加载数据库。MOT的索引非持久化，因此它们是在冷启动时创建的。实际加载的数据加索引大小约多50%。因此，可以转换为MOT冷启动时间的数据和索引容量为40秒内150GB，或225 GB/分钟（3.75 GB/秒）。
+
+冷启动过程和从磁盘加载数据到MOT所需时间如下图所示。
+
+**图 1** 冷启动时间性能基准
+
+![冷启动时间性能基准](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-performance-benchmarks-8.png)
+
+- 数据库大小：加载整个数据库（每数据库GB）的总时间由蓝色线条和左侧的Y轴“时间（秒）”表示。
+- 吞吐量：数据库每秒GB吞吐量由橙色线和右侧的Y轴“吞吐量GB/秒”表示。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 测试过程中表现的性能与SSD硬件的带宽非常接近。因此，可以在不同的平台上实现更高（或更低）的性能。
+
+<br/>
+
+## MOT资源利用率
+
+在4路96核512GB RAM的x86服务器上测试的资源利用率如下所示。MOT能够高效持续消耗几乎所有可用的CPU资源。例如，192核390万tpmC的CPU利用率几乎达到100%。
+
+- tmpC：每分钟完成的TPC-C事务数以橙色条柱和左侧的Y轴“tpmC”表示。
+- CPU利用率（%）：CPU利用率由蓝色线条和右侧的Y轴“CPU%”表示。
+
+**图 1** 资源利用率性能基准
+
+![资源利用率性能基准](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-performance-benchmarks-9.png)
+
+<br/>
+
+## MOT数据采集速度
+
+该测试模拟海量物联网、云端或移动端接入的实时数据流，快速持续地把海量数据注入到数据库。
+
+- 本次测试涉及大量数据采集，具体如下：
+  - 1000万行数据由500个线程发送，2000轮，每个insert命令有10条记录（行），每条记录占200字节。
+  - 客户端和数据库位于不同的机器上。 数据库服务器为2路72核x86服务器。
+- 性能结果
+  - 吞吐量：10000个记录/核，或2MB/核。
+  - 延迟：2.8ms每10条记录批量插入（包括客户端-服务器组网）。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **注意：** 预计MOT将针对这一场景进行多项额外的甚至重大的性能改进。更多关于大规模数据流和数据采集的信息，请参阅[MOT应用场景](4-mot-usage-scenarios)。
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/1-using-mot-overview.md b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/1-using-mot-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..3d56907db1651b422d5c9aa2c9aa15f54999b2be
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/1-using-mot-overview.md
@@ -0,0 +1,18 @@
+---
+title: MOT使用概述
+summary: MOT使用概述
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# MOT使用概述
+
+MOT作为MogDB的一部分自动部署。有关如何计算和规划所需的内存和存储资源以维持工作负载的说明，请参阅[MOT准备](2-mot-preparation)。参考[MOT部署](3-mot-deployment)了解MOT中所有的配置，以及服务器优化的非必须选项。
+
+使用MOT的方法非常简单。MOT命令的语法与基于磁盘的表的语法相同，并支持大多数标准，如PostgreSQL SQL、DDL和DML命令和功能，如存储过程。只有MOT中的创建和删除表语句与MogDB中基于磁盘的表的语句不同。您可以参考[MOT使用](4-mot-usage)了解这两个简单命令的说明，如何将基于磁盘的表转换为MOT，如何使用查询原生编译和PREPARE语句获得更高的性能，以及了解外部工具支持和MOT引擎的限制。
+
+[MOT管理](5-mot-administration)介绍了如何进行数据库维护，以及监控和分析日志和错误报告。最后，[MOT样例TPC-C基准](6-mot-sample-tpcc-benchmark)介绍了如何执行标准TPC-C基准测试。
+
+- 阅读以下内容了解如何使用MOT：
+
+  ![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/using-mot-overview-1.png)
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/2-mot-preparation.md b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/2-mot-preparation.md
new file mode 100644
index 0000000000000000000000000000000000000000..984a76a6dff4fa451f09eb7a54212b73db5731bc
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/2-mot-preparation.md
@@ -0,0 +1,226 @@
+---
+title: MOT准备
+summary: MOT准备
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# MOT准备
+
+下文介绍了使用MOT的前提条件以及内存和存储规划。
+
+<br/>
+
+## 前提条件
+
+以下是使用MogDB MOT的软硬件前提条件。
+
+<br/>
+
+### 硬件支持
+
+MOT支持最新硬件和现有硬件平台，支持x86架构和华为鲲鹏Arm架构。
+
+MOT与MogDB数据库支持的硬件完全对齐。
+
+<br/>
+
+### CPU
+
+MOT在多核服务器（扩容）上提供卓越的性能。在这些环境中，MOT的性能明显优于友商，并提供近线性扩展和极高的资源利用率。
+
+用户也可以开始在低端、中端和高端服务器上实现MOT的性能优势，无论CPU槽位是1或2个，还是4个，甚至是8个也没问题。在16路甚至32路的高端服务器上，性能和资源利用率也非常高（建议与云和恩墨技术支持联系）。
+
+<br/>
+
+### 内存
+
+MOT支持标准RAM/DRAM用于其数据和事务管理。所有MOT数据和索引都驻留在内存中，因此内存容量必须能够支撑数据容量，并且还有进一步增长的空间。内存需求和规划请参见[MOT内存和存储规划](#mot内存和存储规划)。
+
+<br/>
+
+### 存储IO
+
+MOT是一个持久的数据库，使用永久性存储设备（磁盘/SSD/NVMe驱动器）进行事务日志操作和存储定期检查点。
+
+推荐采用低延迟的存储设备，如配置RAID-1的SSD、NVMe或者任何企业级存储系统。当使用适当的硬件时，数据库事务处理和竞争将成为瓶颈，而非IO。
+
+详细的内存要求和规划请参见[MOT内存和存储规划](#mot内存和存储规划)。
+
+操作系统支持
+
+MOT与MogDB支持的操作系统完全对齐。
+
+MOT支持裸机和虚拟化环境，可以在裸机或虚拟机上运行以下操作系统：
+
+- x86：CentOS 7.6和EulerOS 2.0
+- Arm：openEuler和EulerOS
+
+<br/>
+
+### 操作系统优化
+
+MOT不需要任何特殊修改或安装新软件。但是，一些优化可以提高性能。有关实现最大性能的优化说明，请参阅[MOT服务器优化：x86](3-mot-deployment#mot服务器优化x86)和[MOT服务器优化：基于Arm的华为TaiShan2P/4P服务器](3-mot-deployment#mot服务器优化基于arm的华为taishan2p4p服务器)。
+
+<br/>
+
+## MOT内存和存储规划
+
+本节描述了为满足特定应用程序需求，在评估、估计和规划内存和存储容量数量时，需要注意的事项和准则，以及影响所需内存数量的各种数据，例如计划表的数据和索引大小、维持事务管理的内存以及数据增长的速度。
+
+<br/>
+
+### MOT内存规划
+
+MOT是一种内存数据库存储引擎（IMDB），其中所有表和索引完全驻留在内存中。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 内存存储是易失的，需要电力来维护所存储的信息。磁盘存储是持久的，写入磁盘是非易失性存储。MOT使用两种存储，既把所有数据保存在内存中，也把事务性更改同步（通过WAL日志记录）到磁盘上以保持严格一致性（使用同步日志记录模式）。
+
+服务器上必须有足够的物理内存以维持内存表的状态，并满足工作负载和数据的增长。所有这些都是在传统的基于磁盘的引擎、表和会话所需的内存之外的要求。因此，提前规划好足够的内存来容纳这些内容是非常有必要的。
+
+开始可以使用任何数量的内存并执行基本任务和评估测试。但当准备好生产时，应解决以下问题：
+
+- **内存配置**
+
+  MogDB数据库和标准Postgres类似，其内存上限是由max_process_memory设置的，该上限在postgres.conf文件中定义。MOT及其所有组件和线程，都驻留在MogDB进程中。因此，分配给MOT的内存也是在整个MogDB数据库进程的max_process_memory定义的上限内分配。
+
+  MOT为自己保留的内存是max_process_memory的一部分。可以通过百分比或通过小于max_process_memory的绝对值定义。这个部分在mot.conf配置文件中由_mot__memory配置项定义。
+
+  max_process_memory中可以除了被MOT使用的部分之外，必须为Postgres（MogDB）封装留下至少2GB的可用空间。为了确保这一点，MOT在数据库启动过程中会进行如下校验：
+
+  ```
+  (max_mot_global_memory + max_mot_local_memory) + 2GB < max_process_memory
+  ```
+
+  如果违反此限制，则调整MOT内存内部限制，最大可能地满足上述限制范围。该调整在启动时进行，并据此计算MOT最大内存值。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** MOT最大内存值是配置或调整值（max_mot_global_memory + max_mot_local_memory）的逻辑计算值。
+
+  此时，会向服务器日志发出警告，如下所示：
+
+  以下是报告问题的警告消息示例：
+
+  ```
+  [WARNING] <Configuration> MOT engine maximum memory definitions (global: 9830 MB, local: 1843 MB, session large store: 0 MB, total: 11673 MB) breach GaussDB maximum process memory restriction (12288 MB) and/or total system memory (64243 MB). MOT values shall be adjusted accordingly to preserve required gap (2048 MB).
+  ```
+
+  以下警告消息示例提示MOT正在自动调整内存限制：
+
+  ```
+  [WARNING] <Configuration> Adjusting MOT memory limits: global = 8623 MB, local = 1617 MB, session large store = 0 MB, total = 10240 MB
+  ```
+
+  新内存限制仅在此处显示。
+
+  此外，当总内存使用量接近所选内存限制时，MOT不再允许插入额外数据。不再允许额外数据插入的阈值即是MOT最大内存百分比（如上所述，这是一个计算值）。MOT最大内存百分比默认值为90，即90%。尝试添加超过此阈值的额外数据时，会向用户返回错误，并且也会注册到数据库日志文件中。
+
+- **最小值和最大值**
+
+  为了确保内存安全，MOT根据最小的全局和本地设置预先分配内存。数据库管理员应指定MOT和会话维持工作负载所需的最小内存量。这样可以确保即使另一个消耗内存的应用程序与数据库在同一台服务器上运行，并且与数据库竞争内存资源，也能够将这个最小的内存分配给MOT。最大值用于限制内存增长。
+
+- **全局和本地**
+
+    MOT使用的内存由两部分组成：
+
+  - 全局内存：全局内存是一个长期内存池，包含MOT的数据和索引。它平均分布在NUMA节点，由所有CPU核共享。
+
+  - 本地内存：本地内存是用于短期对象的内存池。它的主要使用者是处理事务的会话。这些会话将数据更改存储在专门用于相关特定事务的内存部分（称为事务专用内存）。在提交阶段，数据更改将被移动到全局内存中。内存对象分配以NUMA-local方式执行，以实现尽可能低的延迟。
+
+    被释放的对象被放回相关的内存池中。在事务期间尽量少使用操作系统内存分配（malloc）函数，避免不必要的锁和锁存。
+
+    这两个内存的分配由专用的min/max_mot_global_memory和min/max_mot_local_memory设置控制。如果MOT全局内存使用量太接近最大值，则MOT会保护自身，不接受新数据。超出此限制的内存分配尝试将被拒绝，并向用户报告错误。
+
+- **最低内存要求**
+
+  在开始执行对MOT性能的最小评估前，请确保：
+
+  除了磁盘表缓冲区和额外的内存，max_process_memory（在postgres.conf中定义）还有足够的容量用于MOT和会话（由mix/max_mot_global_memory和mix/max_mot_local_memory配置）。对于简单的测试，可以使用mot.conf的默认设置。
+
+- **生产过程中实际内存需求**
+
+  在典型的OLTP工作负载中，平均读写比例为80:20，每个表的MOT内存使用率比基于磁盘的表高60%（包括数据和索引）。这是因为使用了更优化的数据结构和算法，使得访问速度更快，并具有CPU缓存感知和内存预取功能。
+
+  特定应用程序的实际内存需求取决于数据量、预期工作负载，特别是数据增长。
+
+- **最大全局内存规划：数据和索引大小**
+
+  要规划最大全局内存，需满足：
+
+  1. 确定特定磁盘表（包括其数据和所有索引）的大小。如下统计查询可以确定customer表的数据大小和customer_pkey索引大小：
+
+     - 数据大小：选择pg_relation_size（'customer'）；
+     - 索引：选择pg_relation_size（'customer_pkey'）；
+
+  2. 额外增加60%的内存，相对于基于磁盘的数据和索引的当前大小，这是MOT中的常见要求。
+
+  3. 额外增加数据预期增长百分比。例如：
+
+     5%月增长率 = 80%年增长率（1.05^12）。因此，为了维持年增长，需分配比表当前使用的还多80%的内存。
+
+     至此，max_mot_global_memory值的估计和规划就完成了。实际设置可以用绝对值或Postgres max_process_memory的百分比来定义。具体的值通常在部署期间进行微调。
+
+- **最大本地内存规划：并发会话支持**
+
+  本地内存需求主要是并发会话数量的函数。平均会话的典型OLTP工作负载最大占用8MB。此值乘以会话的数量，再加一点额外的值。
+
+  可以通过这种方式进行内存计算，然后进行微调：
+
+  ```bash
+  SESSION_COUNT * SESSION_SIZE (8 MB) + SOME_EXTRA (100MB should be enough)
+  ```
+
+  默认指定Postgres最大进程内存（默认为12GB）的15%。相当于1.8GB可满足230个会话，即max_mot_local内存需求。实际设置可以用绝对值或Postgres max_process_memory的百分比来定义。具体的值通常在部署期间进行微调。
+
+- **异常大事务**
+
+  某些事务非常大，因为它们将更改应用于大量行。这可能导致单个会话的本地内存增加到允许的最大限制，即1GB。例如：
+
+  ```sql
+  delete from SOME_VERY_LARGE_TABLE;
+  ```
+
+  在配置max_mot_local_memory设置和应用程序开发时，请考虑此场景。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 有关配置的更多信息，请参阅[内存（MOT）](3-mot-deployment#内存mot)部分。
+
+<br/>
+
+### 存储IO
+
+MOT是一个内存优化的持久化数据库存储引擎。需要磁盘驱动器来存储WAL重做日志和定期检查点。
+
+推荐采用低延迟的存储设备，如配置RAID-1的SSD、NVMe或者任何企业级存储系统。当使用适当的硬件时，数据库事务处理和竞争将成为瓶颈，而非IO。
+
+由于持久性存储比RAM内存慢得多，因此IO操作（日志和检查点）可能成为内存中数据库和内存优化数据库的瓶颈。但是，MOT具有针对现代硬件（如SSD、NVMe）进行优化的高效持久性设计和实现。此外，MOT最小化和优化了写入点（例如，使用并行日志记录、每个事务的单日志记录和NUMA-aware事务组写入），并且最小化了写入磁盘的数据（例如，只把更改记录的增量或更新列记录到日志，并且只记录提交阶段的事务）。
+
+<br/>
+
+### 容量需求
+
+所需容量取决于检查点和记录的要求，如下所述：
+
+- **检查点**
+
+  检查点将所有数据的快照保存到磁盘。
+
+  需要给检查点分配两倍数据大小的容量。不需要为检查点索引分配空间。
+
+  检查点 = 2 x MOT数据大小（仅表示行，索引非持久）。
+
+  检查点之所以需要两倍大小，是因为快照会保存数据的全部大小到磁盘上，此外还应该为正在进行的检查点分配同样数量的空间。当检查点进程结束时，以前的检查点文件将被删除。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 在下一个MogDB版本中，MOT将有一个增量检查点特性，这将大大降低存储容量需求。
+
+- **日志记录**
+
+  MOT日志记录与基于磁盘的表的其它记录写入同一个数据库事务日志。
+
+  日志的大小取决于事务吞吐量、数据更改的大小和检查点之间的时间（每次检查点，重做日志被截断并重新开始扩展）。
+
+  与基于磁盘的表相比，MOT使用较少的日志带宽和较低的IO争用。这由多种机制实现。
+
+  例如，MOT不会在事务完成之前记录每个操作。它只在提交阶段记录，并且只记录更新的增量记录（不像基于磁盘的表那样的完整记录）。
+
+  为了确保日志IO设备不会成为瓶颈，日志文件必须放在具有低延迟的驱动器上。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 有关配置的更多信息，请参阅[存储（MOT）](3-mot-deployment#存储mot)。
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/3-mot-deployment.md b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/3-mot-deployment.md
new file mode 100644
index 0000000000000000000000000000000000000000..07e972bf37cfaf8943db686e4d0228c83a1126fe
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/3-mot-deployment.md
@@ -0,0 +1,706 @@
+---
+title: MOT部署
+summary: MOT部署
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# MOT部署
+
+以下各小节介绍了各种必需和可选的设置，以达到最佳部署效果。
+
+<br/>
+
+## MOT服务器优化：x86
+
+通常情况下，数据库由以下组件绑定：
+
+- CPU：更快的CPU可以加速任何CPU绑定的数据库。
+- 磁盘：高速SSD/NVME可加速任何I/O绑定数据库。
+- 网络：更快的网络可以加速任何SQL*Net绑定数据库。
+
+除以上内容外，以下通用服务器设置默认使用，可能会明显影响数据库的性能。
+
+MOT性能调优是确保快速的应用程序功能和数据检索的关键步骤。MOT支持最新的硬件，因此调整每个系统以达到最大吞吐量是极为重要的。
+
+以下是用于优化在英特尔x86服务器上运行MOT时的建议配置。这些设置是高吞吐量工作负载的最佳选择。
+
+<br/>
+
+### BIOS
+
+- Hyper Threading设置为ON。
+
+  强烈建议打开超线程（HT=ON）。
+
+  建议在MOT上运行OLTP工作负载时打开超线程。当使用超线程时，某些OLTP工作负载显示高达40%的性能增益。
+
+<br/>
+
+### 操作系统环境设置
+
+- NUMA
+
+  禁用NUMA平衡，如下所示。MOT以极其高效的NUMA-aware方式进行内存管理，远远超过操作系统使用的默认方法。
+
+  ```
+  echo 0 > /proc/sys/kernel/numa_balancing
+  ```
+
+- 服务
+
+  禁用如下服务：
+
+  ```
+  service irqbalance stop           # MANADATORY
+  service sysmonitor stop           # OPTIONAL, performance
+  service rsyslog stop       # OPTIONAL, performance
+  ```
+
+- 调优服务
+
+  以下为必填项。
+
+  服务器必须运行throughput-performance配置文件。
+
+  ```
+  [...]$ tuned-adm profile throughput-performance
+  ```
+
+  throughput-performance配置文件是广泛适用的调优，它为各种常见服务器工作负载提供卓越的性能。
+
+  其他不太适合MogDB和MOT服务器的配置可能会影响MOT的整体性能，包括：平衡配置、桌面配置、延迟性能配置、网络延迟配置、网络吞吐量配置和节能配置。
+
+- 系统命令
+
+    推荐使用下列操作系统设置以获得最佳性能。
+
+  - 在/etc/sysctl.conf文件中添加如下配置，然后执行sysctl -p命令：
+
+    ```
+    net.ipv4.ip_local_port_range = 9000 65535
+    kernel.sysrq = 1
+    kernel.panic_on_oops = 1
+    kernel.panic = 5
+    kernel.hung_task_timeout_secs = 3600
+    kernel.hung_task_panic = 1
+    vm.oom_dump_tasks = 1
+    kernel.softlockup_panic = 1
+    fs.file-max = 640000
+    kernel.msgmnb = 7000000
+    kernel.sched_min_granularity_ns = 10000000
+    kernel.sched_wakeup_granularity_ns = 15000000
+    kernel.numa_balancing=0
+    vm.max_map_count = 1048576
+    net.ipv4.tcp_max_tw_buckets = 10000
+    net.ipv4.tcp_tw_reuse = 1
+    net.ipv4.tcp_tw_recycle = 1
+    net.ipv4.tcp_keepalive_time = 30
+    net.ipv4.tcp_keepalive_probes = 9
+    net.ipv4.tcp_keepalive_intvl = 30
+    net.ipv4.tcp_retries2 = 80
+    kernel.sem = 250 6400000 1000 25600
+    net.core.wmem_max = 21299200
+    net.core.rmem_max = 21299200
+    net.core.wmem_default = 21299200
+    net.core.rmem_default = 21299200
+    #net.sctp.sctp_mem = 94500000 915000000 927000000
+    #net.sctp.sctp_rmem = 8192 250000 16777216
+    #net.sctp.sctp_wmem = 8192 250000 16777216
+    net.ipv4.tcp_rmem = 8192 250000 16777216
+    net.ipv4.tcp_wmem = 8192 250000 16777216
+    net.core.somaxconn = 65535
+    vm.min_free_kbytes = 26351629
+    net.core.netdev_max_backlog = 65535
+    net.ipv4.tcp_max_syn_backlog = 65535
+    #net.sctp.addip_enable = 0
+    net.ipv4.tcp_syncookies = 1
+    vm.overcommit_memory = 0
+    net.ipv4.tcp_retries1 = 5
+    net.ipv4.tcp_syn_retries = 5
+    ```
+
+  - 按如下方式修改/etc/security/limits.conf对应部分：
+
+    ```
+    <user> soft nofile 100000
+    <user> hard nofile 100000
+    ```
+
+    软限制和硬限制设置可指定一个进程同时打开的文件数量。软限制可由各自运行这些限制的进程进行更改，直至达到硬限制值。
+
+- 磁盘/SSD
+
+  下面以数据库同步提交模式为例，介绍如何保证磁盘读写性能适合数据库同步提交模式。
+
+  按如下方式运行磁盘/SSD性能测试：
+
+  ```
+  [...]$ sync; dd if=/dev/zero of=testfile bs=1M count=1024; sync
+  1024+0 records in
+  1024+0 records out
+  1073741824 bytes (1.1 GB) copied, 1.36034 s, 789 MB/s
+  ```
+
+  当磁盘带宽明显低于789MB/s时，可能会造成MogDB性能瓶颈，尤其是造成MOT性能瓶颈。
+
+<br/>
+
+### 网络
+
+需要使用10Gbps以上网络。
+
+运行iperf命令进行验证：
+
+```
+Server side: iperf -s
+Client side: iperf -c <IP>
+```
+
+rc.local：网卡调优
+
+以下可选设置对性能有显著影响：
+
+1. 将 <https://gist.github.com/SaveTheRbtz/8875474> 下的set_irq_privacy.sh文件拷贝到/var/scripts/目录下。
+
+2. 进入/etc/rc.d/rc.local，执行chmod命令，确保在boot时执行以下脚本：
+
+   ```
+   'chmod +x /etc/rc.d/rc.local'
+   var/scripts/set_irq_affinity.sh -x all <DEVNAME>
+   ethtool -K <DEVNAME> gro off
+   ethtool -C <DEVNAME> adaptive-rx on adaptive-tx on
+   Replace <DEVNAME> with the network card, i.e. ens5f1
+   ```
+
+<br/>
+
+## MOT服务器优化：基于Arm的华为TaiShan2P/4P服务器
+
+以下是基于Arm/鲲鹏架构的华为TaiShan 2280 v2服务器（2路256核）和TaiShan 2480 v2服务器（4路256核）上运行MOT时的建议配置。
+
+除非另有说明，以下设置适用于客户端和服务器的机器。
+
+<br/>
+
+### BIOS
+
+修改BIOS相关设置：
+
+1. 选择**BIOS**> **Advanced** > **MISC Config**。设置**Support Smmu**为**Disabled**。
+
+2. 选择**BIOS**> **Advanced** > **MISC Config**。设置**CPU Prefetching Configuration**为**Disabled**。
+
+   ![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-deployment-1.png)
+
+3. 选择**BIOS**> **Advanced** > **Memory Config**。设置**Die Interleaving**为**Disabled**。
+
+   ![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-deployment-2.png)
+
+4. 选择**BIOS**> **Advanced** > **Performance Config**。设置**Power Policy**为**Performance**。
+
+   ![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-deployment-3.png)
+
+<br/>
+
+### 操作系统：内核和启动
+
+- 以下操作系统内核和启动参数通常由sysadmin配置。
+
+  配置内核参数，如下所示。
+
+  ```bash
+  net.ipv4.ip_local_port_range = 9000 65535
+  kernel.sysrq = 1
+  kernel.panic_on_oops = 1
+  kernel.panic = 5
+  kernel.hung_task_timeout_secs = 3600
+  kernel.hung_task_panic = 1
+  vm.oom_dump_tasks = 1
+  kernel.softlockup_panic = 1
+  fs.file-max = 640000
+  kernel.msgmnb = 7000000
+  kernel.sched_min_granularity_ns = 10000000
+  kernel.sched_wakeup_granularity_ns = 15000000
+  kernel.numa_balancing=0
+  vm.max_map_count = 1048576
+  net.ipv4.tcp_max_tw_buckets = 10000
+  net.ipv4.tcp_tw_reuse = 1
+  net.ipv4.tcp_tw_recycle = 1
+  net.ipv4.tcp_keepalive_time = 30
+  net.ipv4.tcp_keepalive_probes = 9
+  net.ipv4.tcp_keepalive_intvl = 30
+  net.ipv4.tcp_retries2 = 80
+  kernel.sem = 32000 1024000000      500     32000
+  kernel.shmall = 52805669
+  kernel.shmmax = 18446744073692774399
+  sys.fs.file-max = 6536438
+  net.core.wmem_max = 21299200
+  net.core.rmem_max = 21299200
+  net.core.wmem_default = 21299200
+  net.core.rmem_default = 21299200
+  net.ipv4.tcp_rmem = 8192 250000 16777216
+  net.ipv4.tcp_wmem = 8192 250000 16777216
+  net.core.somaxconn = 65535
+  vm.min_free_kbytes = 5270325
+  net.core.netdev_max_backlog = 65535
+  net.ipv4.tcp_max_syn_backlog = 65535
+  net.ipv4.tcp_syncookies = 1
+  vm.overcommit_memory = 0
+  net.ipv4.tcp_retries1 = 5
+  net.ipv4.tcp_syn_retries = 5
+  ##NEW
+  kernel.sched_autogroup_enabled=0
+  kernel.sched_min_granularity_ns=2000000
+  kernel.sched_latency_ns=10000000
+  kernel.sched_wakeup_granularity_ns=5000000
+  kernel.sched_migration_cost_ns=500000
+  vm.dirty_background_bytes=33554432
+  kernel.shmmax=21474836480
+  net.ipv4.tcp_timestamps = 0
+  net.ipv6.conf.all.disable_ipv6=1
+  net.ipv6.conf.default.disable_ipv6=1
+  net.ipv4.tcp_keepalive_time=600
+  net.ipv4.tcp_keepalive_probes=3
+  kernel.core_uses_pid=1
+  ```
+
+- 调优服务
+
+  以下为必填项。
+
+  服务器必须运行throughput-performance配置文件：
+
+  ```bash
+  [...]$ tuned-adm profile throughput-performance
+  ```
+
+  throughput-performance配置文件是广泛适用的调优，它为各种常见服务器工作负载提供卓越的性能。
+
+  其他不太适合MogDB和MOT服务器的配置可能会影响MOT的整体性能，包括：平衡配置、桌面配置、延迟性能配置、网络延迟配置、网络吞吐量配置和节能配置。
+
+- 启动调优
+
+  在内核启动参数中添加iommu.passthrough=1。
+
+  在pass-through模式下运行时，适配器需要DMA转换到内存，从而提高性能。
+
+<br/>
+
+## MOT配置
+
+预置MOT用于创建工作MOT。为了获得最佳效果，建议根据应用程序的特定要求和偏好自定义MOT配置（在mot.conf文件中定义）。
+
+该文件在服务器启动时只读。如果在系统运行中编辑此文件，则必须重新加载服务器才能使修改内容生效。
+
+mot.conf文件与postgres.conf配置文件在同一文件夹下。
+
+阅读[总体原则](#总体原则)，根据需要查看和配置mot.conf文件。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 以上描述了mot.conf文件中的各个设置。除上述内容外，要了解特定MOT功能（如恢复），可参考本用户手册的相关章节。例如，[MOT恢复](5-mot-administration#mot恢复)说明了mot.conf文件的恢复，包含影响MOT恢复的设置。此外，有关恢复的完整说明，请参阅“MOT管理”章节的[MOT恢复](5-mot-administration#mot恢复)。下文各相关章节中还提供了参考链接。
+
+以下介绍了mot.conf文件中的各个部分，其包含的设置以及默认值。
+
+<br/>
+
+### 总体原则
+
+以下是编辑mot.conf文件的总体原则。
+
+- 每个设置项都带有默认值，如下所示：
+
+  ```
+  # name = value
+  ```
+
+- 可以接受空格或留空。
+
+- 在各行添加#号可进行注释。
+
+- 每个设置项的默认值将作为注释显示在整个文件中。
+
+- 如果参数没有注释并且置入了新值，则定义新设置。
+
+- 对mot.conf文件的更改仅在数据库服务器启动或重装时生效。
+
+内存单元的表示如下：
+
+- KB：千字节
+- MB：兆字节
+- GB：吉字节
+- TB：太字节
+
+某些内存单位为postgresql.conf中的max_process_memory的百分比值。例如，20%。
+
+时间单位表示如下：
+
+- us：微秒
+- ms：毫秒
+- s：秒
+- min：分钟
+- h：小时
+- d：天
+
+<br/>
+
+### 重做日志（MOT）
+
+- **enable_redo_log = true**
+
+  指定是否使用重做日志以获得持久性。有关重做日志的详细信息，请参阅[MOT日志记录：WAL重做日志](5-mot-administration#mot日志记录wal重做日志)。
+
+- **enable_group_commit = false**
+
+  是否使用组提交。
+
+  该选项仅在MogDB配置为使用同步提交时相关，即仅当postgresql.conf中的synchronization_commit设置为除off以外的任何值时相关。
+
+  有关WAL重做日志的详细信息，请参阅[MOT日志记录：WAL重做日志](5-mot-administration#mot日志记录wal重做日志)。
+
+- **group_commit_size = 16**
+
+- **group_commit_timeout = 10 ms**
+
+  只有当MOT引擎配置为同步组提交日志记录时，此选项才相关。即postgresql.conf中的synchronization_commit配置为true，mot.conf配置文件中的enable_group_commit配置为true。
+
+  当一组事务记录在WAL重做日志中时，需确定以下设置项取值：
+
+  group_commit_size：一组已提交的事务数。例如，16表示当同一组中的16个事务已由它们的客户端应用程序提交时，则针对16个事务中的每个事务，在磁盘的WAL重做日志中写入一个条目。
+
+  group_commit_timeout：超时时间，单位为毫秒。例如，10表示在10毫秒之后，为同一组由客户端应用程序在最近10毫秒内提交的每个事务，在磁盘的WAL重做日志中写入一个条目。
+
+  提交组在到达配置的事务数后或者在超时后关闭。组关闭后，组中的所有事务等待一个组落盘完成执行，然后通知客户端每个事务都已经结束。
+
+  有关同步组提交日志记录的详细信息，请参阅[MOT日志类型](5-mot-administration#mot日志类型)。
+
+<br/>
+
+### 检查点（MOT）
+
+- **enable_checkpoint = true**
+
+  是否使用周期检查点。
+
+- **checkpoint_dir =**
+
+  指定检查点数据存放目录。默认位置在每个数据节点的data文件夹中。
+
+- **checkpoint_segsize = 16 MB**
+
+  指定检查点时使用的段大小。分段执行检查点。当一个段已满时，它将被序列化到磁盘，并为后续的检查点数据打开一个新的段。
+
+- **checkpoint_workers = 3**
+
+  指定在检查点期间要使用的工作线程数。
+
+  检查点由多个MOT引擎工作线程并行执行。工作线程的数量可能会大大影响整个检查点操作的整体性能，以及其它正在运行的事务的操作。为了实现较短的检查点持续时间，应使用更多线程，直至达到最佳数量（根据硬件和工作负载的不同而不同）。但请注意，如果这个数目太大，可能会对其他正在运行的事务的执行时间产生负面影响。尽可能低这个数字，以最小化对其他运行事务的运行时的影响。当此数目过高时，检查点持续时间会较长。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 有关配置的更多信息，请参阅[MOT检查点](5-mot-administration#mot检查点)。
+
+<br/>
+
+### 恢复（MOT）
+
+- **checkpoint_recovery_workers = 3**
+
+  指定在检查点数据恢复期间要使用的工作线程数。每个MOT引擎工作线程在自己的核上运行，通过将不同的表读入内存，可以并行处理不同的表。缺省值为3，可将此参数设置为可处理的核数。恢复后，将停止并杀死这些线程。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 有关配置的详细信息，请参阅[MOT恢复](5-mot-administration#mot恢复)。
+
+<br/>
+
+### 统计（MOT）
+
+- **enable_stats = false**
+
+  设置周期性统计打印信息。
+
+- **print_stats_period = 10 minute**
+
+  设置汇总统计报表打印的时间范围。
+
+- **print_full_stats_period = 1 hours**
+
+  设置全量统计报表打印的时间范围。
+
+  以下设置为周期性统计报表中的各个部分。如果没有配置，则抑制统计报表。
+
+- **enable_log_recovery_stats = false**
+
+  日志恢复统计信息包含各种重做日志的恢复指标。
+
+- **enable_db_session_stats = false**
+
+  数据库会话统计信息包含事务事件，如提交、回滚等。
+
+- **enable_network_stats = false**
+
+  网络统计信息包括连接/断连事件。
+
+- **enable_log_stats = false**
+
+  日志统计信息包含重做日志详情。
+
+- **enable_memory_stats = false**
+
+  内存统计信息包含内存层详情。
+
+- **enable_process_stats = false**
+
+  进程统计信息包含当前进程的内存和CPU消耗总量。
+
+- **enable_system_stats = false**
+
+  系统统计信息包含整个系统的内存和CPU消耗总量。
+
+- **enable_jit_stats = false**
+
+  JIT统计信息包含有关JIT查询编译和执行的信息。
+
+<br/>
+
+### 错误日志（MOT）
+
+- **log_level = INFO**
+
+  设置MOT引擎下发的消息在数据库服务器的错误日志中记录的日志级别。有效值为PANIC、ERROR、WARN、INFO、TRACE、DEBUG、DIAG1、DIAG2。
+
+- **Log/COMPONENT/LOGGER=LOG_LEVEL**
+
+  使用以下语法设置特定的日志记录器。
+
+  例如，要为系统组件中的ThreadIdPool日志记录器配置TRACE日志级别，请使用以下语法：
+
+  ```
+  Log/System/ThreadIdPool=TRACE
+  ```
+
+  要为某个组件下的所有记录器配置日志级别，请使用以下语法：
+
+  ```
+  Log/COMPONENT=LOG_LEVEL
+  ```
+
+  例如：
+
+  ```
+  Log/System=DEBUG
+  ```
+
+<br/>
+
+### 内存（MOT）
+
+- **enable_numa = true**
+
+  指定是否使用可识别NUMA的内存。 禁用时，所有亲和性配置也将被禁用。 MOT引擎假定所有可用的NUMA节点都有内存。 如果计算机具有某些特殊配置，其中某些NUMA节点没有内存，则MOT引擎初始化将因此失败，因此数据库服务器启动将失败。 在此类计算机中，建议将此配置值设置为false，以防止启动失败并让MOT引擎在不使用可识别NUMA的内存分配的情况下正常运行。
+
+- **affinity_mode = fill-physical-first**
+
+    设置用户会话和内部MOT任务的线程亲和模式。
+
+    使用线程池时，用户会话将忽略此值，因为它们的亲和性由线程池控制。但内部MOT任务仍然使用。
+
+    有效值为fill-socket-first、equal-per-socket、fill-physical-first、none。
+
+  - Fill-socket-first将线程连接到同一个槽位的核上，直到槽位已满，然后移动到下一个槽位。
+  - Equal-per-socket使线程均匀分布在所有槽位中。
+  - Fill-physical-first将线程连接到同一个槽位中的物理核，直到用尽所有物理核，然后移动到下一个槽位。当所有物理核用尽时，该过程再次从超线程核开始。
+  - None禁用任何亲和配置，并让系统调度程序确定每个线程调度在哪个核上运行。
+
+- **lazy_load_chunk_directory = true**
+
+  设置块目录模式，用于内存块查找。
+
+  Lazy模式将块目录设置为按需加载部分目录，从而减少初始内存占用（大约从1GB减少到1MB）。然而，这可能会导致轻微的性能损失和极端情况下的内存损坏。相反，使用non-lazy块目录会额外分配1GB的初始内存，产生略高的性能，并确保在内存损坏期间避免块目录错误。
+
+- **reserve_memory_mode = virtual**
+
+  设置内存预留模式（取值为physical或virtual）。
+
+  每当从内核分配内存时，都会参考此配置值来确定所分配的内存是常驻（physical）还是非常驻（virtual）。这主要与预分配有关，但也可能影响运行时分配。对于physical保留模式，通过强制内存区域所跨越的所有页出现页错误，使整个分配的内存区域常驻。配置virtual内存预留可加速内存分配（特别是在预分配期间），但可能在初始访问期间出现页错误（因此导致轻微的性能影响），并在物理内存不可用时出现更多服务器错误。相反，物理内存分配速度较慢，但后续访问速度更快且有保障。
+
+- **store_memory_policy = compact**
+
+  设置内存存储策略（取值为compact或expanding）。
+
+  当定义了compact策略时，未使用的内存会释放回内核，直到达到内存下限（请参见下面的min_mot_memory）。在expanding策略中，未使用的内存存储在MOT引擎中，以便后续再使用。compact存储策略可以减少MOT引擎的内存占用，但偶尔会导致性能轻微下降。此外，在内存损坏时，它还可能导致内存不可用。相反，expanding模式会占用更多的内存，但是会更快地分配内存，并且能够更好地保证在解分配后能够重新分配内存。
+
+- **chunk_alloc_policy = auto**
+
+    设置全局内存的块分配策略。
+
+    MOT内存以2MB的块为单位组织。源NUMA节点和每个块的内存布局会影响表数据在NUMA节点间的分布，因此对数据访问时间有很大影响。在特定NUMA节点上分配块时，会参考分配策略。
+
+    可用值包括auto、local、page-interleaved、chunk-interleaved、native。
+
+  - Auto策略根据当前硬件情况选择块分配策略。
+  - Local策略在各自的NUMA节点上分配每个数据块。
+  - Page-interleaved策略从所有NUMA节点分配由交插内存4千字节页组成的数据块。
+  - Chunk-interleaved策略以轮循调度方式从所有NUMA节点分配数据块。
+  - Native策略通过调用原生系统内存分配器来分配块。
+
+- **chunk_prealloc_worker_count = 8**
+
+  设置每个NUMA节点参与内存预分配的工作线程数。
+
+- **max_mot_global_memory = 80%**
+
+  设置MOT引擎全局内存的最大限制。
+
+  指定百分比值与postgresql.conf中max_process_memory定义的总量有关。
+
+  MOT引擎内存分为全局（长期）内存，主要用于存储用户数据，以及本地（短期）内存，主要用于用户会话，以满足本地需求。
+
+  任何试图分配超出此限制的内存的尝试将被拒绝，并向用户报告错误。请确保max_mot_global_memory与max_mot_local_memory之和不超过postgresql.conf中配置的max_process_memory。
+
+- **min_mot_global_memory = 0 MB**
+
+  设置MOT引擎全局内存的最小限制。
+
+  指定百分比值与postgresql.conf中max_process_memory定义的总量有关。
+
+  此值用于启动期间的内存预分配，以及确保MOT引擎在正常运行期间有最小的内存可用量。当使用compact存储策略时（参阅上文store_memory_policy），该值指定了下限，超过下限的内存不会释放回内核，而是保留在MOT引擎中以便后续重用。
+
+- **max_mot_local_memory = 15%**
+
+  设置MOT引擎本地内存的最大限制。
+
+  指定百分比值与postgresql.conf中max_process_memory定义的总量有关。
+
+  MOT引擎内存分为全局（长期）内存，主要用于存储用户数据，以及本地（短期）内存，主要用于用户会话，以满足本地需求。
+
+  任何试图分配超出此限制的内存的尝试将被拒绝，并向用户报告错误。请确保max_mot_global_memory与max_mot_local_memory之和不超过postgresql.conf中配置的max_process_memory。
+
+- **min_mot_local_memory = 0 MB**
+
+  设置MOT引擎本地内存的最小限制。
+
+  指定百分比值与postgresql.conf中max_process_memory定义的总量有关。
+
+  此值用于在启动期间预分配内存，以及确保MOT引擎在正常运行期间有最小的可用内存。当使用compact存储策略时（参阅上文store_memory_policy），该值指定了下限，超过下限的内存不会释放回内核，而是保留在MOT引擎中以便后续重用。
+
+- **max_mot_session_memory = 0 MB**
+
+  设置MOT引擎中单个会话的最大内存限制。
+
+  指定百分比值与postgresql.conf中max_process_memory定义的总量有关。
+
+  通常，MOT引擎中的会话可以根据需要分配尽可能多的本地内存，只要没有超出本地内存限制即可。为了避免单个会话占用过多的内存，从而拒绝其他会话的内存，通过该配置项限制小会话的本地内存分配（最大1022KB）。
+
+  请确保该配置项不影响大会话的本地内存分配。
+
+  0表示不会限制每个小会话的本地分配，除非是由max_mot_local_memory配置的本地内存分配限制引起的。
+
+- **min_mot_session_memory = 0 MB**
+
+  设置MOT引擎中单个会话的最小内存预留。
+
+  指定百分比值与postgresql.conf中max_process_memory定义的总量有关。
+
+  此值用于在会话创建期间预分配内存，以及确保会话有最小的可用内存量来执行其正常操作。
+
+- **high_red_mark_percent = 90**
+
+  设置内存分配的高红标记。
+
+  这是按照由max_mot_memory设置的MOT引擎的最大值百分比计算的。默认值为90，即90%。当MOT占用内存总量达到此值时，只允许进行破坏性操作。其它操作都向用户报告错误。
+
+- **session_large_buffer_store_size = 0 MB**
+
+  设置会话的大缓冲区存储。
+
+  当用户会话执行需要大量内存的查询时（例如，使用许多行），大缓冲区存储用于增加此类内存可用的确定级别，并更快地为这个内存请求提供服务。对于超过1022KB的会话，任何内存分配都是大内存分配。如果未使用或耗尽了大缓冲区存储，则这些分配将被视为直接从内核提供的巨大分配。
+
+- **session_large_buffer_store_max_object_size = 0 MB**
+
+  设置会话的大分配缓冲区存储中的最大对象大小。
+
+  大缓冲区存储内部被划分为不同大小的对象。此值用于对源自大缓冲区存储的对象设置上限，以及确定缓冲区存储内部划分为不同大小的对象。
+
+  此大小不能超过session_large_buffer_store_size的1/8。如果超过，则将其调整到最大可能。
+
+- **session_max_huge_object_size = 1 GB**
+
+  设置会话单个大内存分配的最大尺寸。
+
+  巨大分配直接从内核中提供，因此不能保证成功。
+
+  此值也适用于全局（非会话相关）内存分配。
+
+<br/>
+
+### 垃圾收集（MOT）
+
+- **enable_gc = true**
+
+  是否使用垃圾收集器（Garbage Collector，GC）。
+
+- **reclaim_threshold = 512 KB**
+
+  设置垃圾收集器的内存阈值。
+
+  每个会话管理自己的待回收对象列表，并在事务提交时执行自己的垃圾回收。此值决定了等待回收的对象的总内存阈值，超过该阈值，会话将触发垃圾回收。
+
+  一般来说，这里是在权衡未回收对象与垃圾收集频率。设置低值会使未回收的内存保持在较少的水平，但会导致频繁的垃圾回收，从而影响性能。设置高值可以减少触发垃圾回收的频率，但会导致未回收的内存过多。此设置取决于整体工作负载。
+
+- **reclaim_batch_size = 8000**
+
+  设置垃圾回收的批次大小。
+
+  垃圾收集器从对象中批量回收内存，以便限制在一次垃圾收集传递中回收的对象数量。此目的是最小化单个垃圾收集传递的操作时间。
+
+- **high_reclaim_threshold = 8 MB**
+
+  设置垃圾回收的高内存阈值。
+
+  由于垃圾收集是批量工作的，因此会话可能有许多可以回收的对象，但这些对象不能回收。在这种情况下，为了防止垃圾收集列表变得过于膨胀，尽管已经达到批处理大小限制，此值继续单独回收对象，直到待回收对象小于该阈值，或者没有更多符合回收条件的对象。
+
+<br/>
+
+### JIT（MOT）
+
+- **enable_mot_codegen = true**
+
+  指定是否对计划查询使用JIT查询编译和执行。
+
+  JIT查询执行为在计划阶段准备好的查询准备了JIT编译的代码。每当调用准备好的查询时，都会执行生成的JIT编译函数。JIT编译通常以LLVM的形式进行。在原生不支持LLVM的平台上，MOT提供了基于软件的回退（Tiny Virtual Machine，TVM）。
+
+- **force_mot_pseudo_codegen = false**
+
+  当前平台支持LLVM时，是否使用TVM（伪LLVM）。
+
+  在原生不支持LLVM的平台上，MOT自动默认为TVM。
+
+  在原生支持LLVM的平台上，默认使用LLVM。该配置项允许在支持LLVM的平台上使用TVM进行JIT编译和执行。
+
+- **enable_mot_codegen_print = false**
+
+  指定是否为JIT编译的查询打印发出的LLVM/TVM IR代码。
+
+- **mot_codegen_limit = 100**
+
+  限制每个用户会话允许的JIT查询数。
+
+<br/>
+
+### 存储（MOT）
+
+**allow_index_on_nullable_column = true**
+
+指定是否允许在可空列上定义索引。
+
+<br/>
+
+### 默认MOT.conf文件
+
+最小设置和配置指定将Postgresql.conf文件指向MOT.conf文件的位置：
+
+```
+Postgresql.conf
+mot_config_file = '/tmp/gauss/ MOT.conf'
+```
+
+确保max_process_memory设置的值足够包含MOT的全局（数据和索引）和本地（会话）内存。
+
+MOT.conf的默认内容满足开始使用的需求。设置内容后续可以优化。
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/4-mot-usage.md b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/4-mot-usage.md
new file mode 100644
index 0000000000000000000000000000000000000000..2a1e83eeca3f2346799c8e356257e79be1ebafcf
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/4-mot-usage.md
@@ -0,0 +1,544 @@
+---
+title: MOT使用
+summary: MOT使用
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# MOT使用
+
+使用MOT非常简单，以下几个小节将会进行描述。
+
+MogDB允许应用程序使用MOT和基于标准磁盘的表。MOT适用于最活跃、高竞争和对吞吐量敏感的应用程序表，也可用于所有应用程序的表。
+
+以下命令介绍如何创建MOT，以及如何将现有的基于磁盘的表转换为MOT，以加速应用程序的数据库相关性能。MOT尤其有利于已证明是瓶颈的表。
+
+以下是与使用MOT相关的任务的简单概述：
+
+- 授予用户权限
+- 创建/删除MOT
+- 为MOT创建索引
+- 将磁盘表转换为MOT
+- 查询原生编译
+- 重试中止事务
+- MOT外部支持工具
+- MOT SQL覆盖和限制
+
+<br/>
+
+## 授予用户权限
+
+以授予数据库用户对MOT存储引擎的访问权限为例。每个数据库用户仅执行一次，通常在初始配置阶段完成。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** MOT通过外部数据封装器（Foreign Data Wrapper，FDW）机制与MogDB数据库集成，所以需要授权用户权限。
+
+要使特定用户能够创建和访问MOT（DDL、DML、SELECT），以下语句只执行一次：
+
+```sql
+GRANT USAGE ON FOREIGN SERVER mot_server TO <user>;
+```
+
+所有关键字不区分大小写。
+
+<br/>
+
+## 创建/删除MOT
+
+创建MOT非常简单。只有MOT中的创建和删除表语句与MogDB中基于磁盘的表的语句不同。SELECT、DML和DDL的所有其他命令的语法对于MOT表和MogDB基于磁盘的表是一样的。
+
+- 创建MOT：
+
+  ```sql
+  create FOREIGN table test(x int) [server mot_server];
+  ```
+
+- 以上语句中：
+
+  - 始终使用FOREIGN关键字引用MOT。
+  - 在创建MOT表时，[server mot_server]部分是可选的，因为MOT是一个集成的引擎，而不是一个独立的服务器。
+  - 上文以创建一个名为test的内存表（表中有一个名为x的整数列）为例。在下一节（创建索引）中将提供一个更现实的例子。
+  - 如果postgresql.conf中开启了增量检查点，则无法创建MOT。因此请在创建MOT前将enable_incremental_checkpoint设置为off。
+
+- 删除名为test的MOT：
+
+  ```sql
+  drop FOREIGN table test;
+  ```
+
+有关MOT的功能限制（如数据类型），请参见[MOT SQL覆盖和限制](#mot-sql覆盖和限制)。
+
+<br/>
+
+## 为MOT创建索引
+
+支持标准的PostgreSQL创建和删除索引语句。
+
+例如：
+
+```sql
+create index  text_index1 on test(x) ;
+```
+
+创建一个用于TPC-C的ORDER表，并创建索引：
+
+```sql
+create FOREIGN table bmsql_oorder (
+  o_w_id       integer      not null,
+  o_d_id       integer      not null,
+  o_id         integer      not null,
+  o_c_id       integer not null,
+  o_carrier_id integer,
+  o_ol_cnt     integer,
+  o_all_local  integer,
+  o_entry_d    timestamp,
+  primarykey (o_w_id, o_d_id, o_id)
+);
+create index  bmsql_oorder_index1 on bmsql_oorder(o_w_id, o_d_id, o_c_id, o_id) ;
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 在MOT名字之前不需要指定FOREIGN关键字，因为它仅用于创建和删除表的命令。
+
+有关MOT索引限制，请参见[MOT SQL覆盖和限制](#mot-sql覆盖和限制)的索引部分内容。
+
+<br/>
+
+## 将磁盘表转换为MOT
+
+磁盘表直接转换为MOT尚不能实现，这意味着尚不存在将基于磁盘的表转换为MOT的ALTER TABLE语句。
+
+下面介绍如何手动将基于磁盘的表转换为MOT，如何使用gs_dump工具导出数据，以及如何使用gs_restore工具导入数据。
+
+<br/>
+
+### 前置条件检查
+
+检查待转换为MOT的磁盘表的模式是否包含所有需要的列。
+
+检查架构是否包含任何不支持的列数据类型，具体参见[不支持的数据类型](#不支持的数据类型)章节。
+
+如果不支持特定列，则建议首先创建一个更新了模式的备磁盘表。此模式与原始表相同，只是所有不支持的类型都已转换为支持的类型。
+
+使用以下脚本导出该备磁盘表，然后导入到MOT中。
+
+<br/>
+
+### 转换
+
+要将基于磁盘的表转换为MOT，请执行以下步骤：
+
+1. 暂停应用程序活动。
+2. 使用gs_dump工具将表数据转储到磁盘的物理文件中。请确保使用data only。
+3. 重命名原始基于磁盘的表。
+4. 创建同名同模式的MOT。请确保使用创建FOREIGN关键字指定该表为MOT。
+5. 使用gs_restore将磁盘文件的数据加载/恢复到数据库表中。
+6. 浏览或手动验证所有原始数据是否正确导入到新的MOT中。下面将举例说明。
+7. 恢复应用程序活动。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 由于表名称保持不变，应用程序查询和相关数据库存储过程将能够无缝访问新的MOT，而无需更改代码。请注意，MOT目前不支持跨引擎多表查询（如使用Join、Union和子查询）和跨引擎多表事务。因此，如果在多表查询、存储过程或事务中访问原始表，则必须将所有相关的磁盘表转换为MOT，或者更改应用程序或数据库中的相关代码。
+
+<br/>
+
+### 转换示例
+
+假设要将数据库benchmarksql中一个基于磁盘的表customer迁移到MOT中。
+
+将customer表迁移到MOT，操作步骤如下：
+
+1. 检查源表列类型。验证MOT支持所有类型，详情请参阅[不支持的数据类型](#不支持的数据类型)章节。
+
+   ```sql
+   benchmarksql-# \d+ customer
+                          Table "public.customer"
+    Column |  Type   | Modifiers | Storage | Stats target | Description
+   --------+---------+-----------+---------+--------------+-------------
+    x      | integer |           | plain   |              |
+    y      | integer |           | plain   |              |
+   Has OIDs: no
+   Options: orientation=row, compression=no
+   ```
+
+2. 请检查源表数据。
+
+   ```sql
+   benchmarksql=# select * from customer;
+    x | y
+   ---+---
+    1 | 2
+    3 | 4
+   (2 rows)
+   ```
+
+3. 只能使用gs_dump转储表数据。
+
+   ```sql
+   $ gs_dump -Fc benchmarksql -a --table customer -f customer.dump
+   gs_dump[port='15500'][benchmarksql][2020-06-04 16:45:38]: dump database benchmarksql successfully
+   gs_dump[port='15500'][benchmarksql][2020-06-04 16:45:38]: total time: 332  ms
+   ```
+
+4. 重命名源表。
+
+   ```sql
+   benchmarksql=# alter table customer rename to customer_bk;
+   ALTER TABLE
+   ```
+
+5. 创建与源表完全相同的MOT。
+
+   ```sql
+   benchmarksql=# create foreign table customer (x int, y int);
+   CREATE FOREIGN TABLE
+   benchmarksql=# select * from customer;
+    x | y
+   ---+---
+   (0 rows)
+   ```
+
+6. 将源转储数据导入到新MOT中。
+
+   ```sql
+   $ gs_restore -C -d benchmarksql customer.dump
+   restore operation successful
+   total time: 24  ms
+   Check that the data was imported successfully.
+   benchmarksql=# select * from customer;
+    x | y
+   ---+---
+    1 | 2
+    3 | 4
+   (2 rows)
+
+   benchmarksql=# \d
+                                   List of relations
+    Schema |    Name     |     Type      | Owner  |             Storage
+   --------+-------------+---------------+--------+----------------------------------
+    public | customer    | foreign table | aharon |
+    public | customer_bk | table         | aharon | {orientation=row,compression=no}
+   (2 rows)
+   ```
+
+<br/>
+
+## 查询原生编译
+
+MOT的另一个特性是，在预编译的完整查询需要执行之前，能够以原生格式（使用PREPARE语句）准备并解析这些查询。
+
+这种原生格式方便后续更有效地执行（使用EXECUTE命令）。这种执行类型速度要快得多，因为原生格式在执行期间绕过多个数据库处理层，从而获得更好的性能。
+
+这种分工避免了重复的解析分析操作。查询和事务语句可以交互执行。此功能有时称为即时（Just-In-Time，JIT）查询编译。
+
+<br/>
+
+### 查询编译：PREPARE语句
+
+若要使用MOT的原生查询编译，请在执行查询之前调用PREPARE客户端语句。MOT将预编译查询和（或）从缓存预加载先前预编译的代码。
+
+下面是SQL中PREPARE语法的示例：
+
+```sql
+PREPARE name [ ( data_type [, ...] ) ] AS statement
+```
+
+PREPARE在数据库服务器中创建一个预处理语句，该语句是一个可用于优化性能的服务器端对象。
+
+<br/>
+
+### 运行命令
+
+发出EXECUTE命令时，将解析、分析、重写和执行预处理语句。这种分工避免了重复的解析分析操作，同时使执行计划依赖于特定的设置值。
+
+下面是在Java应用程序中调用PREPARE和EXECUTE语句的示例。
+
+```sql
+conn = DriverManager.getConnection(connectionUrl, connectionUser, connectionPassword);
+
+// Example 1: PREPARE without bind settings
+String query = "SELECT * FROM getusers";
+PreparedStatement prepStmt1 = conn.prepareStatement(query);
+ResultSet rs1 = pstatement.executeQuery())
+while (rs1.next()) {…}
+
+// Example 2: PREPARE with bind settings
+String sqlStmt = "SELECT * FROM employees where first_name=? and last_name like ?";
+PreparedStatement prepStmt2 = conn.prepareStatement(sqlStmt);
+prepStmt2.setString(1, "Mark"); // first name “Mark”
+prepStmt2.setString(2, "%n%"); // last name contains a letter “n”
+ResultSet rs2 = prepStmt2.executeQuery())
+while (rs2.next()) {…}
+```
+
+MOT编译支持的特性和不支持的特性见下文。
+
+<br/>
+
+### 轻量执行支持的查询
+
+以下查询类型适合轻量执行：
+
+- 简单点查询
+  - SELECT (including SELECT for UPDATE)
+  - UPDATE
+  - DELETE
+- INSERT查询
+- 引用主键的完整前缀的范围UPDATE查询
+- 引用主键的完整前缀的范围SELECT查询
+- JOIN查询，其中一部分或两部分重叠为点查询
+- 引用每个连接表中主键的完整前缀的JOIN查询
+
+<br/>
+
+### 轻量执行不支持的查询
+
+任何特殊的查询属性都不适用于轻量执行。特别是如果以下条件中的任何一项适用，则该查询不适合轻量执行。有关更多信息，请参阅[原生编译和轻量执行不支持的查询](#原生编译和轻量执行不支持的查询)。
+
+需要强调一点，如果查询语句不适用原生编译和轻量执行，不向客户端报告错误，查询仍以正常和规范的方式执行。
+
+有关MOT原生编译功能的详细信息，请参阅[查询原生编译](#查询原生编译)的有关内容。
+
+<br/>
+
+## 重试中止事务
+
+在乐观并发控制（OCC）中，在COMMIT阶段前的事务期间（使用任何隔离级别）不会对记录进行锁定。这是一个能显著提高性能的强大优势。它的缺点是，如果另一个会话尝试更新相同的记录，则更新可能会失败。所以必须中止整个事务。这些所谓的更新冲突是由MOT在提交时通过版本检查机制检测到的。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 使用悲观并发控制的引擎，如标准Postgres和MogDB基于磁盘的表，当使用SERIALIZABLE或REPEATABLE-READ隔离级别时，也会发生类似的异常中止。
+
+这种更新冲突在常见的OLTP场景中非常少见，在使用MOT时尤其少见。但是，由于仍有可能发生这种情况，开发人员应该考虑使用事务重试代码来解决此问题。
+
+下面以多个会话同时尝试更新同一个表为例，说明如何重试表命令。有关更多详细信息，请参阅[OCC与2PL的区别举例](3-2#occ与2pl的区别举例)部分。下面以TPC-C支付事务为例。
+
+```sql
+int commitAborts = 0;
+
+while (commitAborts < RETRY_LIMIT) {
+
+    try {
+        stmt =db.stmtPaymentUpdateDistrict;
+        stmt.setDouble(1, 100);
+        stmt.setInt(2, 1);
+        stmt.setInt(3, 1);
+        stmt.executeUpdate();
+
+        db.commit();
+
+        break;
+    }
+    catch (SQLException se) {
+        if(se != null && se.getMessage().contains("could not serialize access due to concurrent update")) {
+            log.error("commmit abort = " + se.getMessage());
+            commitAborts++;
+            continue;
+        }else {
+            db.rollback();
+        }
+
+        break;
+    }
+}
+```
+
+<br/>
+
+## MOT外部支持工具
+
+为了支持MOT，修改了以下外部MogDB工具。请确保使用的工具是最新版本。下面将介绍与MOT相关的用法。有关这些工具及其使用方法的完整说明，请参阅《参考指南》中的“工具参考”章节。
+
+<br/>
+
+### gs_ctl（全量和增量）
+
+此工具用于从主服务器创建备服务器，以及当服务器的时间线偏离后，将服务器与其副本进行同步。
+
+在操作结束时，工具将获取最新的MOT检查点，同时考虑checkpoint_dir配置值。
+
+检查点从源服务器的checkpoint_dir读取到目标服务器的checkpoint_dir。
+
+目前MOT不支持增量检查点。因此，gs_ctl增量构建对于MOT来说不是以增量方式工作，而是以全量方式工作。Postgres磁盘表仍然可以增量构建。
+
+<br/>
+
+### gs_basebackup
+
+gs_basebackup用于准备运行中服务器的基础备份，不影响其他数据库客户端。
+
+MOT检查点也会在操作结束时获取。但是，检查点的位置是从源服务器中的checkpoint_dir获取的，并传输到源数据目录中，以便正确备份。
+
+<br/>
+
+### gs_dump
+
+gs_dump用于将数据库模式和数据导出到文件中。支持MOT。
+
+<br/>
+
+### gs_restore
+
+gs_restore用于从文件中导入数据库模式和数据。支持MOT。
+
+<br/>
+
+## MOT SQL覆盖和限制
+
+MOT设计几乎能够覆盖SQL和未来特性集。例如，大多数支持标准的Postgres SQL，也支持常见的数据库特性，如存储过程、自定义函数等。
+
+下面介绍各种SQL覆盖和限制。
+
+<br/>
+
+### 不支持的特性
+
+MOT不支持以下特性：
+
+- 跨引擎操作：不支持跨引擎（磁盘+MOT）的查询、视图或事务。计划于2021年实现该特性。
+- MVCC、隔离：不支持没有快照/可序列化隔离。计划于2021年实现该特性。
+- 原生编译（JIT）：SQL覆盖有限。此外，不支持存储过程的JIT编译。
+- 本地内存限制为1GB。一个事务只能更改小于1GB的数据。
+- 容量（数据+索引）受限于可用内存。未来将提供Anti-caching和数据分层功能。
+- 不支持全文检索索引。
+- 不支持逻辑复制特性。
+
+此外，下面详细列出了MOT、MOT索引、查询和DML语法的各种通用限制，以及查询原生编译的特点和限制。
+
+<br/>
+
+### MOT限制
+
+MOT功能限制：
+
+- 按范围分区
+- AES加密
+- 流操作
+- 自定义类型
+- 子事务
+- DML触发器
+- DDL触发器
+- “C”或“POSIX”以外的排序规则
+
+<br/>
+
+### 不支持的DDL操作
+
+- 修改表结构
+- 创建including表
+- 创建as select表
+- 按范围分区
+- 创建无日志记录子句（no-logging clause）的表
+- 创建可延迟约束主键（DEFERRABLE）
+- 重新索引
+- 表空间
+- 使用子命令创建架构
+
+<br/>
+
+### 不支持的数据类型
+
+- UUID
+- User-Defined Type (UDF)
+- Array data type
+- NVARCHAR2(n)
+- NVARCHAR(n)
+- Clob
+- Name
+- Blob
+- Raw
+- Path
+- Circle
+- Reltime
+- Bit varying(10)
+- Tsvector
+- Tsquery
+- JSON
+- HSTORE
+- Box
+- Text
+- Line
+- Point
+- LSEG
+- POLYGON
+- INET
+- CIDR
+- MACADDR
+- Smalldatetime
+- BYTEA
+- Bit
+- Varbit
+- OID
+- Money
+- 无限制的varchar/character varying
+- HSTORE
+- XML
+
+<br/>
+
+### 不支持的索引DDL和索引
+
+- 在小数和数值类型上创建索引
+
+- 在可空列上创建索引
+
+- 单表创建索引总数>9
+
+- 在键大小>256的表上创建索引
+
+  键大小包括以字节为单位的列大小+列附加大小，这是维护索引所需的开销。下表列出了不同列类型的列附加大小。
+
+  此外，如果索引不是唯一的，额外需要8字节。
+
+  下面是伪代码计算键大小：
+
+  ```sql
+  keySize =0;
+
+  for each (column in index){
+        keySize += (columnSize + columnAddSize);
+  }
+  if (index is non_unique) {
+        keySize += 8;
+  }
+  ```
+
+  | 列类型   | 列大小 | 列附加大小 |
+  | :------- | :----- | :--------- |
+  | varchar  | N      | 4          |
+  | tinyint  | 1      | 1          |
+  | smallint | 2      | 1          |
+  | int      | 4      | 1          |
+  | longint  | 8      | 1          |
+  | float    | 4      | 2          |
+  | double   | 8      | 3          |
+
+上表中未指定的类型，列附加大小为零（例如时间戳）。
+
+<br/>
+
+### 不支持的DML
+
+- Merge into
+- Select into
+- Lock table
+- Copy from table
+
+<br/>
+
+### 原生编译和轻量执行不支持的查询
+
+- 查询涉及两个以上的表
+- 查询有以下任何一个情况：
+  - 非原生类型的聚合
+  - 窗口功能
+  - 子查询子链接
+  - Distinct-ON修饰语（distinct子句来自DISTINCT ON）
+  - 递归（已指定WITH RECURSIVE）
+  - 修改CTE（WITH中有INSERT/UPDATE/DELETE）
+
+以下子句不支持轻量执行：
+
+- Returning list
+- Group By clause
+- Grouping sets
+- Having clause
+- Windows clause
+- Distinct clause
+- Sort clause that does not conform to native index order
+- Set operations
+- Constraint dependencies
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/5-mot-administration.md b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/5-mot-administration.md
new file mode 100644
index 0000000000000000000000000000000000000000..a9733c9757824c8e51a17e1b36799723daca4290
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/5-mot-administration.md
@@ -0,0 +1,456 @@
+---
+title: MOT管理
+summary: MOT管理
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# MOT管理
+
+下面介绍MOT管理。
+
+<br/>
+
+## MOT持久性
+
+持久性是指长期的数据保护（也称为磁盘持久化）。持久性意味着存储的数据不会遭受任何形式的退化或损坏，因此数据不会丢失或损坏。持久性可确保在有计划停机（例如维护）或计划外崩溃（例如电源故障）后数据和MOT引擎恢复到一致状态。
+
+内存存储是易失的，需要电力来维护所存储的信息。另一方面，磁盘存储是非易失性的，这意味着它不需要电源来维护存储的信息，因此不用担心停电。MOT同时使用这两种类型的存储。内存中存储了所有数据，同时将事务性更改持久化到磁盘，并保持频繁的定期[MOT检查点](#mot检查点)，以确保在关机时恢复数据。
+
+用户必须保证有足够的磁盘空间用于日志记录和检查点操作。检查点使用单独的驱动器，通过减少磁盘I/O负载来提高性能。
+
+参考[MOT关键技术](3-mot-key-technologies)了解如何在MOT引擎中实现持久化。
+
+若要设置持久性：
+
+为保证严格一致性，请在postgres.conf配置文件中将参数sync_commit配置为On。
+
+MOT的WAL重做日志和检查点开启持久性，下面将详细介绍。
+
+<br/>
+
+### MOT日志记录：WAL重做日志
+
+为保证持久性，MOT全面集成MogDB的WAL机制，通过MogDB的XLOG接口持久化WAL记录。这意味着，每次MOT记录的添加、更新和删除都记录在WAL中。确保了可以从这个非易失性日志重新生成和恢复最新的数据状态。例如，如果向表中添加了3行，删除了2行，更新了1行，那么日志中将记录6个条目。
+
+MOT日志记录和MogDB磁盘表的其他记录写入同一个WAL中。
+
+MOT只记录事务提交阶段的操作。
+
+MOT只记录更新的增量记录，以便最小化写入磁盘的数据量。
+
+在恢复期间，从最后一个已知或特定检查点加载数据；然后使用WAL重做日志完成从该点开始发生的数据更改。
+
+WAL重做日志将保留所有表行修改，直到执行检查点（如上所述）。然后可以截断日志，以减少恢复时间和节省磁盘空间。
+
+注意：为确保日志IO设备不会成为瓶颈，日志文件必须放在具有低延迟的驱动器上。
+
+<br/>
+
+### MOT日志类型
+
+支持两个同步事务日志选项和一个异步事务日志选项（标准MogDB磁盘引擎也支持这些选项）。MOT还支持同步的组提交日志记录与NUMA-aware优化，如下所述。
+
+根据您的配置，实现以下类型的日志记录：
+
+- **同步重做日志记录**
+
+  同步重做日志记录选项是最简单、最严格的重做日志记录器。当客户端应用程序提交事务时，事务重做条目记录在WAL重做日志中，如下所示：
+
+  1. 当事务正在进行时，它存储在MOT内存中。
+
+  2. 事务完成后，客户端应用程序发送Commit命令，该事务被锁定，然后写入磁盘上的WAL重做日志。当事务日志条目写入日志时，客户端应用程序仍在等待响应。
+
+  3. 一旦事务的整个缓冲区被写入日志，就更改内存中的数据，然后提交事务。事务提交后，通知客户端应用程序事务完成。
+
+     **总结**
+
+     同步重做日志记录选项是最安全、最严格的，因为它确保了客户端应用程序和每个事务提交时的WAL重做日志条目的完全同步，从而确保了总的持久性和一致性，并且绝对不会丢失数据。此日志记录选项可防止客户端应用程序在事务尚未持久化到磁盘时将事务标记为成功的情况。
+
+     同步重做日志记录选项的缺点是，它是三个选项中最慢的日志机制。因为客户端应用程序必须等待所有数据都写入磁盘，并且磁盘写入过于频繁导致数据库变慢。
+
+- **组同步重做日志记录**
+
+  组同步重做日志记录选项与同步重做日志记录选项非常相似，它确保完全持久性，绝对不会丢失数据，并保证客户端应用程序和WAL重做日志条目的完全同步。不同的是，组同步重做日志记录选项将事务重做条目组同时写入磁盘上的WAL重做日志，而不是在提交时写入每个事务。使用组同步重做日志记录可以减少磁盘I/O数量，从而提高性能，特别是在运行繁重的工作负载时。
+
+  MOT引擎通过根据运行事务的核的NUMA槽位自动对事务进行分组，使用NUMA感知优化来执行同步的组提交记录。
+
+  有关NUMA-aware内存访问的更多信息，请参阅[NUMA-aware分配和亲和性](3-4)。
+
+  当一个事务提交时，一组条目记录在WAL重做日志中，如下所示：
+
+  1. 当事务正在进行时，它存储在内存中。MOT引擎根据运行事务的核的NUMA槽位对桶中的事务进行分组。在同一槽位上运行的所有事务都被分组在一起，并且多个组将根据事务运行的核并行填充。
+
+     这样，将事务写入WAL更为有效，因为来自同一个槽位的所有缓冲区都一起写入磁盘。
+
+     注意：每个线程在属于单槽位的单核/CPU上运行，每个线程只写在各自运行的核的槽位上。
+
+  2. 在事务完成并且客户端应用程序发送Commit命令之后，事务重做日志条目将与同组的其他事务一起序列化。
+
+  3. 当特定一组事务满足配置条件后，如[重做日志（MOT）](3-mot-deployment#重做日志mot)小节中描述的已提交的事务数或超时时间，该组中的事务将被写入磁盘的WAL中。当这些日志条目被写入日志时，发出提交请求的客户端应用程序正在等待响应。
+
+  4. 一旦NUMA-aware组中的所有事务缓冲区都写入日志，该组中的所有事务都将对内存存储执行必要的更改，并且通知客户端这些事务已完成。
+
+     **总结**
+
+     组同步重做日志记录选项是一个极其安全和严格的日志记录选项，因为它确保了客户端应用程序和WAL重做日志条目的完全同步，从而确保了总的持久性和一致性，而且绝对不会丢失数据。此日志记录选项可防止客户端应用程序在事务尚未持久化到磁盘时将事务标记为成功的情况。
+
+     该选项的磁盘写入次数比同步重做日志记录选项少，这可能意味着它更快。缺点是事务被锁定的时间更长。在同一NUMA内存中的所有事务都写入磁盘的WAL重做日志之前，它们一直处于锁定状态。
+
+     是否使用此选项取决于事务工作负载的类型。例如，此选项有利于事务较多的系统。而对于事务少的系统而言，磁盘写入量也很少，因此不建议使用。
+
+- **异步重做日志记录**
+
+  异步重做日志记录选项是最快的日志记录方法，但是它不能确保数据不会丢失，某些仍位于缓冲区中且尚未写入磁盘的数据在电源故障或数据库崩溃时可能会丢失。当客户端应用程序提交事务时，事务重做条目将记录在内部缓冲区中，并按预先配置的时间间隔写入磁盘。客户端应用程序不会等待数据写入磁盘。它将继续进行下一个事务。这就是异步重做日志记录最快的原因。
+
+  当客户端应用程序提交事务时，事务重做条目记录在WAL重做日志中，如下所示：
+
+  1. 当事务正在进行时，它存储在MOT内存中。
+
+  2. 在事务完成并且客户端应用程序发送Commit命令后，事务重做条目将被写入内部缓冲区，但尚未写入磁盘。然后更改MOT数据内存，并通知客户端应用程序事务已提交。
+
+  3. 后台运行的重做日志线程按预先配置的时间间隔收集所有缓存的重做日志条目，并将它们写入磁盘。
+
+     **总结**
+
+     异步重做日志记录选项是最快的日志记录选项，因为它不需要客户端应用程序等待数据写入磁盘。此外，它将许多事务重做条目分组并把它们写入一起，从而减少降低MOT引擎速度的磁盘I/O数量。
+
+     异步重做日志记录选项的缺点是它不能确保在崩溃或失败时数据不会丢失。已提交但尚未写入磁盘的数据在提交时是不持久的，因此在出现故障时无法恢复。异步重做日志记录选项对于愿意牺牲数据恢复（一致性）而不是性能的应用程序来说最为适用。
+
+<br/>
+
+### 配置日志
+
+标准MogDB磁盘引擎支持两个同步事务日志选项和一个异步事务日志选项。
+
+配置日志记录
+
+1. 在postgres.conf配置文件中的sync_commit (On = Synchronous)参数中指定是否执行同步或异步事务日志记录。
+2. 在重做日志章节中的mot.conf配置文件里，将enable_redo_log参数设置为True。
+
+如果已选择事务日志记录的同步模式（如上文所述，synchronous_commit = On），则在mot.conf配置文件中的enable_group_commit参数中指定Group Synchronous Redo Logging选项或Synchronous Redo Logging选项。如果选择Group Synchronous Redo Logging，必须在mot.conf文件中定义以下阈值，决定何时将一组事务记录在WAL中。
+
+- group_commit_size：一组已提交的事务数。例如，16表示当同一组中的16个事务已由它们的客户端应用程序提交时，则针对16个事务中的每个事务，在磁盘的WAL重做日志中写入一个条目。
+- group_commit_timeout：超时时间，单位为毫秒。例如，10表示在10毫秒之后，为同一组由客户端应用程序在最近10毫秒内提交的每个事务，在磁盘的WAL重做日志中写入一个条目。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 有关配置的详细信息，请参阅[重做日志（MOT）](3-mot-deployment#重做日志mot)。
+
+<br/>
+
+### MOT检查点
+
+检查点是一个时间点。在这个时间点，表行的所有数据都保存在持久存储上的文件中，以便创建完整持久的数据库镜像。这是一个数据在某个时间点的快照。
+
+检查点减少了为确保持久性而必须重放的WAL重做日志条目的数量，以此缩短数据库的恢复时间。检查点还减少了保存所有日志条目所需的存储空间。
+
+如果没有检查点，那么为了恢复数据库，所有WAL重做条目必须从开始时间进行重放，可能需要几天或几周的时间，这取决于数据库中的记录数量。检查点记录数据库的当前状态，并允许丢弃旧的重做条目。
+
+检查点在恢复方案（特别是冷启动）中是必不可少的。首先，从最后一个已知或特定检查点加载数据；然后使用WAL完成此后发生的数据更改。
+
+例如，如果同一表行被修改100次，则日志中将记录100个条目。当使用检查点后，即使表行被修改了100次，检查点也可以一次性记录。在记录检查点之后，可以基于该检查点执行恢复，并且只需要播放自该检查点之后发生的WAL重做日志条目。
+
+<br/>
+
+## MOT恢复
+
+MOT恢复的主要目标是在有计划停机（例如维护）或计划外崩溃（例如电源故障后）后，将数据和MOT引擎恢复到一致状态。
+
+MOT恢复是随着MogDB数据库其余部分的恢复而自动执行的，并且完全集成到MogDB恢复过程（也称为冷启动）。
+
+MOT恢复包括两个阶段：
+
+检查点恢复：必须通过将数据加载到内存行并创建索引，从磁盘上的最新检查点文件恢复数据。
+
+WAL重做日志恢复：从检查点恢复中使用检查点后，必须通过重放之后添加到日志中的记录，从WAL重做日志中恢复最近的数据（在检查点中未捕获）。
+
+MogDB管理和触发WAL重做日志恢复。
+
+- 配置恢复。
+- 虽然WAL恢复以串行方式执行，但可以将检查点恢复配置为以多线程方式运行（即由多个工作线程并行运行）。
+- 在mot.conf文件中配置Checkpoint_recovery_workers参数，见[恢复（MOT）](3-mot-deployment#恢复mot)中的描述。
+
+<br/>
+
+## MOT复制和高可用
+
+由于MOT集成到MogDB中，并且使用或支持其复制和高可用，因此，MOT原厂功能即支持同步复制和异步复制。
+
+MogDB gs_ctl工具用于可用性控制和数据库操作。这包括gs_ctl切换、gs_ctl故障切换、gs_ctl构建等等。
+
+有关更多信息，请参见MogDB参考指南。
+
+- 配置复制和高可用性。
+- 请参考MogDB相关文档。
+
+<br/>
+
+## MOT内存管理
+
+规划和微调请参见[MOT内存和存储规划](2-mot-preparation#mot内存和存储规划)和[MOT配置](3-mot-deployment#mot配置)。
+
+<br/>
+
+## MOT VACUUM清理
+
+使用VACUUM进行垃圾收集，并有选择地分析数据库，如下所示。
+
+- 【Postgres】
+
+  在Postgres中，VACUUM用于回收死元组占用的存储空间。在正常的Postgres操作中，删除的元组或因更新而作废的元组不会从表中物理删除。只能由VACUUM清理。因此，需要定期执行VACUUM，特别是在频繁更新的表上。
+
+- 【MOT扩展】
+
+  MOT不需要周期性的VACUUM操作，因为新元组会重用失效元组和空元组。只有当MOT的大小急剧减少，并且不计划恢复到原来大小时，才需要VACUUM操作。
+
+  例如，应用程序定期（如每周一次）大量删除表数据的同时插入新数据，这需要几天时间，并且不一定是相同数量的行。在这种情况下，可以使用VACUUM。
+
+  对MOT的VACUUM操作总是被转换为带有排他表锁的VACUUM FULL。
+
+- 支持的语法和限制
+
+    按规范激活VACUUM操作。
+
+    ```sql
+    VACUUM [FULL | ANALYZE] [ table ];
+    ```
+
+    只支持FULL和ANALYZE VACUUM两种类型。VACUUM操作只能对整个MOT进行。
+
+    不支持以下Postgres VACUUM选项：
+
+  - FREEZE
+  - VERBOSE
+  - Column specification
+  - LAZY模式（部分表扫描）
+
+    此外，不支持以下功能：
+
+  - AUTOVACUUM
+
+<br/>
+
+## MOT统计
+
+统计信息主要用于性能分析或调试。在生产环境中，通常不打开它们（默认是关闭的）。统计信息主要由数据库开发人员使用，数据库用户较少使用。
+
+对性能有一定影响，特别是对服务器。对用户的影响可以忽略不计。
+
+统计信息保存在数据库服务器日志中。该日志位于data文件夹中，命名为postgresql-DATE-TIME.log。
+
+有关详细的配置选项，请参阅[统计（MOT）](3-mot-deployment#统计mot)。
+
+<br/>
+
+## MOT监控
+
+监控的所有语法支持基于Postgres的FDW表，包括下面的表或索引大小。此外，还存在用于监控MOT内存消耗的特殊函数，包括MOT全局内存、MOT本地内存和单个客户端会话。
+
+<br/>
+
+### 表和索引大小
+
+可以通过查询pg_relation_size来监控表和索引的大小。
+
+例如：
+
+**数据大小**
+
+```sql
+select pg_relation_size('customer');
+```
+
+**索引**
+
+```sql
+select pg_relation_size('customer_pkey');
+```
+
+<br/>
+
+### MOT全局内存详情
+
+检查MOT全局内存大小，主要是数据和索引。
+
+```sql
+select * from mot_global_memory_detail();
+```
+
+结果如下。
+
+```sql
+numa_node  | reserved_size        | used_size
+----------------+----------------+-------------
+-1            | 194716368896      | 25908215808
+0             | 446693376         | 446693376
+1             | 452984832         | 452984832
+2             | 452984832         | 452984832
+3             | 452984832         | 452984832
+4             | 452984832         | 452984832
+5             | 364904448         | 364904448
+6             | 301989888         | 301989888
+7             | 301989888         | 301989888
+```
+
+其中，
+
+- -1为总内存。
+- 0-7为NUMA内存节点。
+
+<br/>
+
+### MOT本地内存详情
+
+检查MOT本地内存大小，包括会话内存。
+
+```sql
+select * from mot_local_memory_detail();
+```
+
+结果如下。
+
+```sql
+numa_node  | reserved_size      | used_size
+----------------+----------------+-------------
+-1            | 144703488       | 144703488
+0             | 25165824        | 25165824
+1             | 25165824        | 25165824
+2             | 18874368        | 18874368
+3             | 18874368        | 18874368
+4             | 18874368        | 18874368
+5             | 12582912        | 12582912
+6             | 12582912        | 12582912
+7             | 12582912        | 12582912
+```
+
+其中，
+
+- -1为总内存。
+- 0-7为NUMA内存节点。
+
+<br/>
+
+### 会话内存
+
+会话管理的内存从MOT本地内存中获取。
+
+所有活动会话（连接）的内存使用量可以通过以下查询。
+
+```sql
+select * from mot_session_memory_detail();
+```
+
+结果如下。
+
+```sql
+sessid                   | total_size | free_size | used_size
+----------------------------------------+-----------+----------+----------
+1591175063.139755603855104 | 6291456    | 1800704   | 4490752
+```
+
+其中，
+
+- total_size：分配给会话的内存。
+- free_size：未使用的内存。
+- used_size：使用中的内存。
+
+DBA可以通过以下查询确定当前会话使用的本地内存状态。
+
+```sql
+select * from mot_session_memory_detail()
+ where sessid = pg_current_sessionid();
+```
+
+结果如下。
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-administration-1.png)
+
+<br/>
+
+## MOT错误消息
+
+错误可能由多种场景引起。所有错误都记录在数据库服务器日志文件中。此外，与用户相关的错误作为对查询、事务或存储过程执行或数据库管理操作的响应的一部分返回给用户。
+
+- 服务器日志中报告的错误包括函数、实体、上下文、错误消息、错误描述和严重性。
+- 向用户报告的错误被翻译成标准PostgreSQL错误码，可能由MOT特定的消息和描述组成。
+
+错误提示、错误描述和错误码见下文。该错误码实际上是内部代码，不记录也不返回给用户。
+
+<br/>
+
+### 写入日志文件的错误
+
+所有错误都记录在数据库服务器日志文件中。以下列出了写入数据库服务器日志文件但未返回给用户的错误。该日志位于data文件夹中，命名为postgresql-DATE-TIME.log。
+
+**表 1** 只写入日志文件的错误
+
+| 日志消息                            | 内部错误代码                     |
+| :---------------------------------- | :------------------------------- |
+| Error code denoting success         | MOT_NO_ERROR 0                   |
+| Out of memory                       | MOT_ERROR_OOM 1                  |
+| Invalid configuration               | MOT_ERROR_INVALID_CFG 2          |
+| Invalid argument passed to function | MOT_ERROR_INVALID_ARG 3          |
+| System call failed                  | MOT_ERROR_SYSTEM_FAILURE 4       |
+| Resource limit reached              | MOT_ERROR_RESOURCE_LIMIT 5       |
+| Internal logic error                | MOT_ERROR_INTERNAL 6             |
+| Resource unavailable                | MOT_ERROR_RESOURCE_UNAVAILABLE 7 |
+| Unique violation                    | MOT_ERROR_UNIQUE_VIOLATION 8     |
+| Invalid memory allocation size      | MOT_ERROR_INVALID_MEMORY_SIZE 9  |
+| Index out of range                  | MOT_ERROR_INDEX_OUT_OF_RANGE 10  |
+| Error code unknown                  | MOT_ERROR_INVALID_STATE 11       |
+
+<br/>
+
+### 返回给用户的错误
+
+下面列出了写入数据库服务器日志文件并返回给用户的错误。
+
+MOT使用返回码（Return Code，RC）返回Postgres标准错误代码至封装。某些RC会导致向正在与数据库交互的用户生成错误消息。
+
+MOT从内部返回Postgres代码（见下文）到数据库包，数据库封装根据标准的Postgres行为对其做出反应。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 提示信息中的%s、%u、%lu指代相应的错误信息（如查询、表名或其他信息）。 - %s：字符串 - %u：数字 - %lu：数字
+
+**表 2** 返回给用户并记录到日志文件的错误
+
+| 返回给用户的短/长描述                  | Postgres代码                     | 内部错误码                       |
+| :---------------------------------- | :------------------------------ | :------------------------------ |
+| Success.Denotes success                                      | ERRCODE*SUCCESSFUL*COMPLETION                               | RC_OK = 0                           |
+| FailureUnknown error has occurred.                           | ERRCODE_FDW_ERROR                                           | RC_ERROR = 1                        |
+| Unknown error has occurred.Denotes aborted operation.        | ERRCODE_FDW_ERROR                                           | RC_ABORT                            |
+| Column definition of %s is not supported.Column type %s is not supported yet. | ERRCODE_INVALID_COLUMN_DEFINITION                           | RC_UNSUPPORTED_COL_TYPE             |
+| Column definition of %s is not supported.Column type Array of %s is not supported yet. | ERRCODE_INVALID_COLUMN_DEFINITION                           | RC_UNSUPPORTED_COL_TYPE_ARR         |
+| Column size %d exceeds max tuple size %u.Column definition of %s is not supported. | ERRCODE_FEATURE_NOT_SUPPORTED                               | RC_EXCEEDS_MAX_ROW_SIZE             |
+| Column name %s exceeds max name size %u.Column definition of %s is not supported. | ERRCODE_INVALID_COLUMN_DEFINITION                           | RC_COL_NAME_EXCEEDS_MAX_SIZE        |
+| Column size %d exceeds max size %u.Column definition of %s is not supported. | ERRCODE_INVALID_COLUMN_DEFINITION                           | RC_COL_SIZE_INVLALID                |
+| Cannot create table.Cannot add column %s; as the number of declared columns exceeds the maximum declared columns. | ERRCODE_FEATURE*NOT*SUPPORTED                               | RC_TABLE_EXCEEDS*MAX*DECLARED_COLS  |
+| Cannot create index.Total column size is greater than maximum index size %u. | ERRCODE_FDW_KEY*SIZE*EXCEEDS_MAX_ALLOWED                    | RC_INDEX_EXCEEDS_MAX_SIZE           |
+| Cannot create index.Total number of indexes for table %s is greater than the maximum number of indexes allowed %u. | ERRCODE_FDW_TOO*MANY*INDEXES                                | RC_TABLE_EXCEEDS_MAX_INDEXES        |
+| Cannot execute statement.Maximum number of DDLs per transaction reached the maximum %u. | ERRCODE_FDW_TOO*MANY*DDL_CHANGES*IN*TRANSACTION*NOT*ALLOWED | RC_TXN_EXCEEDS_MAX_DDLS             |
+| Unique constraint violationDuplicate key value violates unique constraint \“%s\“”.Key %s already exists. | ERRCODE*UNIQUE*VIOLATION                                    | RC_UNIQUE_VIOLATION                 |
+| Table \“%s\” does not exist.                                 | ERRCODE_UNDEFINED_TABLE                                     | RC_TABLE_NOT_FOUND                  |
+| Index \“%s\” does not exist.                                 | ERRCODE_UNDEFINED_TABLE                                     | RC_INDEX_NOT_FOUND                  |
+| Unknown error has occurred.                                  | ERRCODE_FDW_ERROR                                           | RC_LOCAL_ROW_FOUND                  |
+| Unknown error has occurred.                                  | ERRCODE_FDW_ERROR                                           | RC_LOCAL_ROW_NOT_FOUND              |
+| Unknown error has occurred.                                  | ERRCODE_FDW_ERROR                                           | RC_LOCAL_ROW_DELETED                |
+| Unknown error has occurred.                                  | ERRCODE_FDW_ERROR                                           | RC_INSERT_ON_EXIST                  |
+| Unknown error has occurred.                                  | ERRCODE_FDW_ERROR                                           | RC_INDEX_RETRY_INSERT               |
+| Unknown error has occurred.                                  | ERRCODE_FDW_ERROR                                           | RC_INDEX_DELETE                     |
+| Unknown error has occurred.                                  | ERRCODE_FDW_ERROR                                           | RC_LOCAL_ROW_NOT_VISIBLE            |
+| Memory is temporarily unavailable.                           | ERRCODE_OUT_OF_LOGICAL_MEMORY                               | RC_MEMORY_ALLOCATION_ERROR          |
+| Unknown error has occurred.                                  | ERRCODE_FDW_ERROR                                           | RC_ILLEGAL_ROW_STATE                |
+| Null constraint violated.NULL value cannot be inserted into non-null column %s at table %s. | ERRCODE_FDW_ERROR                                           | RC_NULL_VIOLATION                   |
+| Critical error.Critical error: %s.                           | ERRCODE_FDW_ERROR                                           | RC_PANIC                            |
+| A checkpoint is in progress - cannot truncate table.         | ERRCODE_FDW_OPERATION_NOT_SUPPORTED                         | RC_NA                               |
+| Unknown error has occurred.                                  | ERRCODE_FDW_ERROR                                           | RC_MAX_VALUE                        |
+| &lt;recovery message&gt;                                     |                                                             | ERRCODE_CONFIG_FILE_ERROR           |
+| &lt;recovery message&gt;                                     |                                                             | ERRCODE_INVALID*TABLE*DEFINITION    |
+| Memory engine - Failed to perform commit prepared.           |                                                             | ERRCODE_INVALID*TRANSACTION*STATE   |
+| Invalid option &lt;option name&gt;                           |                                                             | ERRCODE_FDW_INVALID*OPTION*NAME     |
+| Invalid memory allocation request size.                      |                                                             | ERRCODE_INVALID*PARAMETER*VALUE     |
+| Memory is temporarily unavailable.                           |                                                             | ERRCODE_OUT_OF*LOGICAL*MEMORY       |
+| Could not serialize access due to concurrent update.         |                                                             | ERRCODE_T_R*SERIALIZATION*FAILURE   |
+| Alter table operation is not supported for memory table.Cannot create MOT tables while incremental checkpoint is enabled.Re-index is not supported for memory tables. |                                                             | ERRCODE_FDW_OPERATION*NOT*SUPPORTED |
+| Allocation of table metadata failed.                         |                                                             | ERRCODE_OUT_OF_MEMORY               |
+| Database with OID %u does not exist.                         |                                                             | ERRCODE_UNDEFINED_DATABASE          |
+| Value exceeds maximum precision: %d.                         |                                                             | ERRCODE_NUMERIC_VALUE*OUT*OF_RANGE  |
+| You have reached a maximum logical capacity %lu of allowed %lu. |                                                             | ERRCODE_OUT_OF*LOGICAL*MEMORY       |
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/6-mot-sample-tpcc-benchmark.md b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/6-mot-sample-tpcc-benchmark.md
new file mode 100644
index 0000000000000000000000000000000000000000..e9b1daa0d48142b149cd7b904900567bfd8b2115
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/2-using-mot/6-mot-sample-tpcc-benchmark.md
@@ -0,0 +1,116 @@
+---
+title: MOT样例TPC-C基准
+summary: MOT样例TPC-C基准
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# MOT样例TPC-C基准
+
+## TPC-C简介
+
+TPC-C基准是衡量联机事务处理（OLTP）系统性能的行业标准基准。它基于一个复杂的数据库和许多不同的事务类型。这些事务类型在此基准上执行。TPC-C基准测试既不依赖硬件，也不依赖软件，因此可以在每个测试平台上运行。基准模型的官方概述，见[tpc.org网站](http://www.tpc.org/default5.asp)。
+
+该数据库由9个不同结构的表组成，因此也包括9种类型的数据。每个表的数据大小和数量不同。在数据库上混合执行五种不同类型和复杂性的并发事务。这些大部分是在线事务或者部分排队等待延迟批处理。由于这些表竞争有限的系统资源，许多系统组件都有压力，数据更改以各种方式执行。
+
+**表 1** TPC-C数据库结构
+
+| 表       | 条目数               |
+| :------- | :------------------- |
+| 仓库     | n                    |
+| 供货商品 | 100,000              |
+| 库存     | n x 100,000          |
+| 地区     | n x 10               |
+| 客户     | 3000/区，30,000/仓库 |
+| 订单     | 客户数量（初始值）   |
+| 新增订单 | 30%订单（初始值）    |
+| 定单分录 | ~10/单               |
+| 历史记录 | 客户数量（初始值）   |
+
+事务组合代表从订单输入到订单交付的完整业务处理。具体来说，所提供的组合旨在产生相等数量的新订单事务和支付事务，并且为每十个新订单事务产生一个交付事务、一个订单状态事务和一个库存水平事务。
+
+**表 2** TPC-C事务比例
+
+| 事务级别≥4% | 占所有事务份额 |
+| :---------- | :------------- |
+| TPC-C新订单 | ≤ 45%          |
+| 支付        | ≥ 43%          |
+| 订单状态    | ≥ 4%           |
+| 交付        | ≥4%（批次）    |
+| 库存水平    | ≥ 4%           |
+
+有两种方法来执行事务：作为存储过程（允许更高的吞吐量）和以标准交互式SQL模式执行。
+
+**性能指标：tpm-C**
+
+tpm-C指标是每分钟执行的新订单事务数。考虑到事务中所需的组合以及广泛的复杂性和类型，此指标最接近地模拟一个全面的业务活动，而不仅仅是一个或两个事务或计算机操作。因此，tpm-C指标被认为是业务吞吐量的指标。
+
+tpm-C指标单位表示为每分钟事务数-C，而C表示TPC-C特定基准。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 官方TPC-C基准规范可访问[此页面](http://www.tpc.org/tpc_documents_current_versions/pdf/tpc-c_v5.11.0.pdf)。本规范中的一些规则在行业中难以实现，因为对行业现状来说这些规则太严格了。例如：扩容规则（a） tpm-C/Warehouse必须大于9且小于12.86（要达到较高的tpm-C率，需要很高的仓库费率。这就意味着需要非常大的数据库和内存容量）以及规则（b）10倍终端*仓库（意味着大量的模拟客户端）。
+
+## 系统级优化
+
+请按照[MOT部署](3-mot-deployment)中的说明进行操作。下面介绍MogDB数据库在华为TaiShan服务器和Euler 2.8操作系统上部署时系统级的关键优化点，以达到极致性能。
+
+## BenchmarkSQL：开源TPC-C工具
+
+可以使用BenchmarkSQL测试TPCC，如下所示：
+
+- 下载benchmarksql：[https://osdn.net/frs/g_redir.php?m=kent&f=benchmarksql%2Fbenchmarksql-5.0.zip](https://osdn.net/frs/g_redir.php?m=kent&f=benchmarksql/benchmarksql-5.0.zip)
+- benchmarksql工具中的模式创建脚本需要调整为MOT语法，避免使用不支持的DDL。下载调整后的脚本：<https://opengauss.obs.cn-south-1.myhuaweicloud.com/1.1.0/MOT-TPCC-Benchmark.tar.gz>。该tar文件的内容包括sql.common.mogdb.mot文件夹和jTPCCTData.java文件，以及一个示例配置文件postgresql.conf和TPCC属性文件props.mot供参考。
+- 将sql.common.mogdb.mot文件夹放在run文件夹下与sql.common同级的文件夹，用下载的Java文件替换src/client/jTPCCTData.java文件。
+- 编辑run文件夹下的runDatabaseBuild.sh文件，将extraHistID从AFTER_LOAD列表中删除，以避免不支持的ALTER表DDL。
+- 将lib/postgres文件夹下的JDBC驱动替换为MogDB JDBC。驱动下载链接：<https://opengauss.org/en/download.html>。
+
+在下载的Java文件（与原始文件相比）中所做的唯一更改是注释错误日志打印，以进行序列化和重复键错误。这些错误在MOT中是正常的，因为MOT使用的是乐观并发控制（OCC）机制。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 基准测试使用标准交互式SQL模式执行，没有存储过程。
+
+## 运行基准
+
+任何人都可以启动服务器，运行benchmarksql脚本。
+
+运行基准测试：
+
+1. 进入benchmarksql运行文件夹，将sql.common重命名为sql.common.orig。
+2. 创建sql.common到sql.common.mogdb.mot的链接，用于测试MOT。
+3. 启动数据库服务器。
+4. 配置客户端props.pg文件。
+5. 运行基准测试。
+
+## 结果报告
+
+- CLI结果
+
+  BenchmarkSQL结果应如下所示：
+
+  ![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-sample-tpcc-benchmark-1.jpg)
+
+  随着时间的推移，基准测量并平均已提交的事务。上面的例子是两分钟的基准测试。
+
+  得分为271万tmp-C（每分钟新增订单数），占总承诺事务数的45%，即tpmTOTAL。
+
+- 详细结果报告
+
+  详细结果报告示例：
+
+**图 1** 详细结果报告
+
+![详细结果报告](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-sample-tpcc-benchmark-2.png)
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-sample-tpcc-benchmark-3.png)
+
+BenchmarkSQL收集详细的性能统计数据和操作系统性能数据（如果配置了的话）。
+
+这些信息可以显示查询的延迟，从而暴露与存储/网络/CPU相关的瓶颈。
+
+华为TaiShan 2480 MOT TPC-C测试结果
+
+2020年5月1日TPC-C基准测试，TaiShan 2480服务器（Arm/鲲鹏4路服务器）安装MogDB数据库，吞吐量达到479万tpmC。
+
+下图展示了近乎线性的可扩展性：
+
+**图 2** 华为TaiShan 2480 MOT TPC-C测试结果
+
+![华为TaiShan-2480-MOT-TPC-C测试结果](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-sample-tpcc-benchmark-4.png)
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-1.md b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-1.md
new file mode 100644
index 0000000000000000000000000000000000000000..a3b7c461a1ed99ab9c6f04b3019d19490b787e87
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-1.md
@@ -0,0 +1,95 @@
+---
+title: MOT纵向扩容架构
+summary: MOT纵向扩容架构
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# MOT纵向扩容架构
+
+纵向扩容即为同一台机器添加额外的核以增加算力。纵向扩容是传统上为单对控制器和多核的机器增加算力的常见形式。纵向扩容架构受限于控制器的可扩展性。
+
+<br/>
+
+## 技术要求
+
+MOT旨在实现以下目标：
+
+- **线性扩容**：MOT提供事务性存储引擎，利用单个NUMA架构服务器的所有核，以提供近线性的扩容性能。这意味着MOT的目标是在机器的核数和性能提升倍数之间实现直接的、近线性的关系。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** MOT的近线性扩容效果明显优于所有现有方案，并且尽可能接近于获得最佳效果，因现有方案皆受限于硬件（如电线）的物理限制和局限性。
+
+- **无最大核数限制**：MOT对最大核数不做任何限制。这意味着MOT可从单核扩展到高达1000秒的多核，并且新增的核退化速度最小，即便是在跨NUMA槽位边界的情况下。
+- **极高的事务性吞吐量**：MOT提供了一个事务性存储引擎，与市场上任何其他OLTP供应商相比，它能够实现极高的事务性吞吐量。
+- **极低的事务性时延**：与市场上任何其他OLTP供应商相比，MOT提供事务性存储引擎，可以达到极低的事务时延。
+- **无缝集成和利用MogDB产品**：MOT事务引擎与MogDB产品标准无缝集成。通过这种方式，MOT最大限度地重用了位于其事务性存储引擎顶部的MogDB层功能。
+
+<br/>
+
+## 设计原则
+
+为了实现上述要求（特别是在多核的环境中），我们存储引擎的体系结构实施了以下技术和策略：
+
+- 数据和索引只存在于内存中。
+- 数据和索引不用物理分区来布局（因为对于某些类型的应用程序，这些分区的性能可能会降低）。
+- 事务并发控制基于乐观并发控制（OCC），没有集中的争用点。有关OCC的详细信息，请参见[MOT并发控制机制](3-2)。
+- 使用平行重做日志（最后单位为核）来有效避免中央锁定点。
+- 使用免锁索引。有关免锁索引的详细信息，请参见[MOT索引](3-5)。
+- 使用NUMA感知内存分配，避免跨槽位访问，特别是会话生命周期对象。有关NUMA感知的更多信息，请参见[NUMA-aware分配和亲和性](3-4)。
+- 使用带有预缓存对象池的自定义MOT内存管理分配器，避免昂贵的运行时间分配和额外的争用点。这种专用的MOT内存分配器按需预先访问操作系统中较大的内存块，然后按需将内存分配给MOT，使内存分配更加高效。
+
+<br/>
+
+## 使用外部数据封装（FDW）进行集成
+
+MOT遵循并利用了MogDB的标准扩展机制 - 外部数据封装（FDW），如下图所示。
+
+在PostgreSQL外部数据封装特性的支持下，作为其他数据源的代理的MOT数据库可以创建外表，如MySQL、Oracle、PostgreSQL等。当对外表执行查询时，FDW将查询外部数据源并返回结果，就像查询内表一样。
+
+MogDB依赖PostgreSQL外部数据封装和索引支持，因此SQL完全覆盖，包括存储过程、用户定义函数、系统函数调用。
+
+**图 1** MOT架构
+
+![MOT架构](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-scale-up-architecture-1.png)
+
+上图中绿色表示MOT引擎，蓝色表示现有的MogDB（基于Postgres）组件。由此可见，FDW在MOT引擎和MogDB组件之间进行中介。
+
+**与MOT相关的FDW定制**
+
+通过FDW集成MOT可以重用最上层的MogDB功能，从而显著缩短MOT的上市时间，同时不影响SQL的覆盖范围。
+
+但是，MogDB中原有的FDW机制并不是为存储引擎扩展而设计的，因此缺少以下基本功能：
+
+- 查询规划阶段待计算的外表的索引感知
+- 完整的DDL接口
+- 完整的事务生命周期接口
+- 检查点接口
+- 重做日志接口
+- 恢复接口
+- 真空接口
+
+为了支持所有缺失的功能，SQL层和FDW接口层已扩展，从而为插入MOT事务存储引擎提供必要的基础设施。
+
+<br/>
+
+## 结果：线性扩容
+
+以下是上述MOT设计原则和实现的结果：
+
+MOT在符合ACID工作负载的事务吞吐量方面优于所有现有的工业级OLTP数据库。
+
+MogDB和MOT在以下多核系统上进行了测试，性能可扩展性良好。在x86架构Intel和ARM/鲲鹏架构的多核服务器上进行了测试。详细的性能评估请参见[MOT性能基准](5-mot-performance-benchmarks)。
+
+以2020年6月的TPC-C基准测试了一台泰山2480服务器上的MogDB MOT数据库（4路ARM/鲲鹏服务器，吞吐量：480万tpmC）。下图显示了MOT数据库的近线性性质，即MOT数据库通过增加核数显著提高性能。
+
+**图 2** ARM上的TPC-C（256核）
+
+![ARM上的TPC-C（256核）](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-performance-benchmarks-3.png)
+
+下面是另一个测试示例，一台基于x86的服务器上也显示了CPU使用率。
+
+**图 3** tpmC 对比CPU使用率
+
+![tpmC-对比CPU使用率](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-performance-benchmarks-9.png)
+
+图表显示，MOT性能提高与核数增加有显著的相关性。随着核数的增加，MOT对CPU的消耗也越来越大。其他行业解决方案不能提高MOT性能，有时性能甚至略有下降，影响客户的CAPEX和OPEX支出以及运营效率。这是数据库行业的公认问题。
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-2.md b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-2.md
new file mode 100644
index 0000000000000000000000000000000000000000..347235365b034ee1b21655ecc40751c552e97f70
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-2.md
@@ -0,0 +1,191 @@
+---
+title: MOT并发控制机制
+summary: MOT并发控制机制
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# MOT并发控制机制
+
+通过大量研究，我们找到了最佳的并发控制机制，结论为：基于SILO的OCC算法是MOT中最符合ACID特性的OCC算法。SILO为满足MOT的挑战性需求提供了最好的基础。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** MOT完全符合原子性、一致性、隔离性、持久性（ACID）特性，如[MOT简介](1-mot-introduction)所述。
+
+下面介绍MOT的并发控制机制。
+
+<br/>
+
+## MOT本地内存和全局内存
+
+SILO管理本地内存和全局内存，如图1所示。
+
+- 全局内存是所有核共享的长期内存，主要用于存储所有的表数据和索引。
+- 本地内存是短期内存，主要由会话使用，用于处理事务及将数据更改存储到事务内存中，直到提交阶段。
+
+当事务需要更改时，SILO将该事务的所有数据从全局内存复制到本地内存。使用OCC方法，全局内存中放置的是最小的锁，因此争用时间极短。事务更改完成后，该数据从本地内存回推到全局内存中。
+
+本地内存与SILO增强并发控制的基本交互式事务流如下所示：
+
+**图 1** 私有（本地）内存（每个事务）和全局内存（所有核的所有事务）
+
+![私有（本地）内存（每个事务）和全局内存（所有核的所有事务）](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-concurrency-control-mechanism-1.png)
+
+具体请参见[对比：磁盘与MOT](3-9)。
+
+<br/>
+
+## MOT SILO增强特性
+
+SILO凭借其基本算法流程，优于我们在研究实验中测试的许多其他符合ACID的OCC算法。然而，为了使SILO成为产品级机制，我们必须用许多在最初设计中缺失的基本功能来增强它，例如：
+
+- 新增对交互式事务的支持，其中事务的SQL运行在客户端实现，而不是作为服务器端的单个步骤运行。
+- 新增乐观插入
+- 新增对非唯一索引的支持
+- 新增对事务中写后读校验（RAW）的支持，使用户能够在提交之前查看更改
+- 新增对无锁协同垃圾回收的支持
+- 新增对无锁检查点的支持
+- 新增对快速恢复的支持
+- 新增对分布式部署两阶段提交的支持
+
+在不破坏原始SILO的可扩展特性的前提下添加这些增强是非常具有挑战性的。
+
+<br/>
+
+## MOT隔离级别
+
+即使MOT完全兼容ACID，MogDB 2.1并非支持所有的隔离级别。下表介绍了各隔离级别，以及MOT支持和不支持的内容。
+
+**表 1** 隔离级别
+
+| 隔离级别         | 说明                                                         |
+| :--------------- | :----------------------------------------------------------- |
+| READ UNCOMMITTED | **MOT不支持**                                                |
+| READ COMMITTED   | **MOT支持**<br/>READ COMMITTED（读已提交）隔离级别保证任何正在读取的数据在上一次读取时都已提交。它只是限制读者看到任何中间数据、未提交数据，或脏读。数据被读取后可以自由更改，因此，读已提交隔离级别并不保证事务再次读取时能找到相同的数据。 |
+| SNAPSHOT         | **MOT不支持**<br/>SNAPSHOT（快照）隔离级别提供与SERIALIZABLE（可序列化）相同的保证，同时支持并发事务修改数据。相反，它迫使每个读者看到自己的世界版本（自己的快照）。不阻止并发更新使得编程非常容易，且可扩展性很强。然而，在许多实现中，这种隔离级别需要更高的服务器资源。 |
+| REPEATABLE READ  | **MOT支持**<br/>REPEATABLE READ（可重复读）是一个更高的隔离级别，除了READ COMMITTED隔离级别的保证之外，它还保证任何读取的数据都不能更改。如果一个事务再次读取相同的数据，它将找出该数据，不做更改，并且保证它可读取。乐观模型使得并发事务能更新该事务读取的行。在提交时，该事务将验证REPEATABLE READ隔离级别是否被违反。若违反，则回滚该事务，必须重试。 |
+| SERIALIZABLE     | **MOT不支持**<br/>SERIALIZABLE（可序列化）隔离提供了更强的保证。除了REPEATABLE READ隔离级别保证的所有内容外，它还保证后续读取不会看到新数据。它之所以被命名为SERIALIZABLE，是因为隔离非常严格，几乎有点像事务串行运行，而不是并行运行。 |
+
+下表显示了不同隔离级别启用的并发副作用。
+
+**表 2** 隔离级别启用的并发副作用
+
+| 隔离级别         | 说明 | 不可重复读 | 幻影 |
+| :--------------- | :--- | :--------- | :--- |
+| READ UNCOMMITTED | 是   | 是         | 是   |
+| READ COMMITTED   | 否   | 是         | 是   |
+| REPEATABLE READ  | 否   | 否         | 是   |
+| SNAPSHOT         | 否   | 否         | 否   |
+| SERIALIZABLE     | 否   | 否         | 否   |
+
+在不久后将发布的版本中，MogDB MOT还将支持SNAPSHOT和SERIALIZABLE隔离级别。
+
+<br/>
+
+## MOT乐观并发控制
+
+并发控制模块（简称CC模块）提供了主内存引擎的所有事务性需求。CC模块的主要目标是为主内存引擎提供各种隔离级别的支持。
+
+<br/>
+
+### 乐观OCC与悲观2PL
+
+悲观2PL（2阶段锁定）和乐观并发控制（OCC）的功能差异在于对事务完整性分别采用悲观和乐观方法。
+
+基于磁盘的表使用悲观方法，这是最常用的数据库方法。MOT引擎使用的是乐观方法。
+
+悲观方法和乐观方法的主要功能区别在于，如果冲突发生，
+
+- 悲观的方法会导致客户端等待；
+- 而乐观方法会导致其中一个事务失败，使得客户端必须重试失败的事务。
+
+**乐观并发控制方法（MOT使用）**
+
+乐观并发控制（OCC）方法在冲突发生时检测冲突，并在提交时执行验证检查。
+
+乐观方法开销较小，而且通常效率更高，原因之一是事务冲突在大多数应用程序中并不常见。
+
+当强制执行REPEATABLE READ隔离级别时，乐观方法与悲观方法之间的函数差异更大，而当强制执行SERIALIZABLE隔离级别时，函数差异最大。
+
+**悲观方法（MOT未使用）**
+
+悲观并发控制（2PL，或称2阶段锁定）方法使用锁阻止在潜在冲突的发生。执行语句时应用锁，提交事务时释放锁。基于磁盘的行存储使用这种方法，并且添加了多版本并发控制（Multi-version Concurrency Control，MVCC）。
+
+在2PL算法中，当一个事务正在写入行时，其他事务不能访问该行；当一个行正在读取时，其他事务不能覆盖该行。在访问时锁定每个行，以进行读写；在提交时释放锁。这些算法需要一个处理和避免死锁的方案。死锁可以通过计算等待图中的周期来检测。死锁可以通过使用TSO保持时序或使用某种回退方案来避免。
+
+**遇时锁定（ETL）**
+
+另一种方法是遇时锁定（ETL），它以乐观的方式处理读取，但写入操作锁定它们访问的数据。因此，来自不同ETL事务的写入操作相互感知，并可以决定中止。实验证明，ETL通过两种方式提高OCC的性能：
+
+- 首先，ETL会在早期检测冲突，并通常能增加事务吞吐量。这是因为事务不会执行无用的操作。（通常）在提交时发现的冲突无法在不中止至少一个事务的情况下解决。
+- 其次，ETL写后读校验（RAW）运行高效，无需昂贵或复杂的机制。
+
+**结论：**
+
+OCC是大多数工作负载最快的选项。这一点我们在初步研究阶段已经发现。
+
+其中一个原因是，当每个核执行多个线程时，锁很可能被交换线程持有，特别是在交互模式下。另一个原因是悲观算法涉及死锁检测（产生开销），并通常使用读写锁（比标准自旋锁效率低）。
+
+我们选择Silo是因为它比其他现有选项（如TicToc）简单，同时对大多数工作负载保持相同的性能。ETL有时比OCC更快，但它引入了假中止，可能会使用户混淆，而OCC则只在提交时中止。
+
+<br/>
+
+### OCC与2PL的区别举例
+
+下面是会话同时更新同一个表时，两种用户体验的区别：悲观（针对基于磁盘的表）和乐观（针对MOT表）。
+
+本例中，使用如下表测试命令：
+
+```
+table “TEST” - create table test (x int, y int, z int, primary key(x));
+```
+
+本示例描述同一测试的两个方面：用户体验（本示例中的操作）和重试要求。
+
+**悲观方法示例 - 用于基于磁盘的表**
+
+下面是一个悲观方法例子（非MOT）。任何隔离级别都可能适用。
+
+以下两个会话执行尝试更新单个表的事务。
+
+WAIT LOCK操作发生，客户端体验是：会话2卡住，直到会话1完成COMMIT，会话2才能进行。
+
+但是，使用这种方法时，两个会话都成功，并且不会发生异常中止（除非应用了SERIALIZABLE或REPEATABLE-READ隔离级别），这会导致整个事务需要重试。
+
+**表 3** 悲观方法代码示例
+
+|      | 会话1                            | 会话2                                                        |
+| :--- | :------------------------------- | :----------------------------------------------------------- |
+| t0   | Begin                            | Begin                                                        |
+| t1   | update test set y=200 where x=1; |                                                              |
+| t2   | y=200                            | Update test set y=300 where x=1; - Wait on lock              |
+| t4   | Commit                           |                                                              |
+|      |                                  | Unlock                                                       |
+|      |                                  | Commit(in READ-COMMITTED this will succeed, in SERIALIZABLE it will fail) |
+|      |                                  | y = 300                                                      |
+
+**乐观方法示例 - 用于MOT**
+
+下面是一个乐观方法的例子。
+
+它描述了创建一个MOT表，然后有两个并发会话同时更新同一个MOT表的情况。
+
+```
+create foreign table test (x int, y int, z int, primary key(x));
+```
+
+- OCC的优点是，在COMMIT之前没有锁。
+- OCC的缺点是，如果另一个会话更新了相同的记录，则更新可能会失败。如果更新失败（在所有支持的隔离级别中），则必须重试整个会话#2事务。
+- 更新冲突由内核在提交时通过版本检查机制检测。
+- 会话2将不会等待其更新操作，并且由于在提交阶段检测到冲突而中止。
+
+**表 4** 乐观方法代码示例--用于MOT
+
+|      | 会话1                            | 会话2                            |
+| :--- | :------------------------------- | :------------------------------- |
+| t0   | Begin                            | Begin                            |
+| t1   | update test set y=200 where x=1; |                                  |
+| t2   | y=200                            | Update test set y=300 where x=1; |
+| t4   | Commit                           | y = 300                          |
+|      |                                  | Commit                           |
+|      |                                  | ABORT                            |
+|      |                                  | y = 200                          |
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-3.md b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-3.md
new file mode 100644
index 0000000000000000000000000000000000000000..e0e477a62939272560abfcb390e91036b5789124
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-3.md
@@ -0,0 +1,71 @@
+---
+title: 扩展FDW与其他MogDB特性
+summary: 扩展FDW与其他MogDB特性
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# 扩展FDW与其他MogDB特性
+
+MogDB基于PostgreSQL，而PostgreSQL没有内置存储引擎适配器，如MySQL的handlerton。为了使MOT存储引擎能够集成到MogDB中，我们利用并扩展了现有的FDW机制。随着FDW引入PostgreSQL 9.1，现在可以将这些外表和数据源呈现为统一、本地可访问的关系来访问外部管理的数据库。
+
+和PostgreSQL不同的是，MOT存储引擎是嵌入在MogDB内部的，表由MogDB管理。MogDB规划器和执行器控制表的访问。MOT从MogDB获取日志和检查点服务，并参与MogDB恢复过程和其他过程。
+
+我们把正在使用或正在访问MOT存储引擎的所有组件称为封装。
+
+下图显示了MOT存储引擎如何嵌入到MogDB中及其对数据库功能的双向访问。
+
+**图 1** MogDB内置MOT存储引擎-外部数据库的FDW访问
+
+![MOT架构](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-scale-up-architecture-1.png)
+
+我们通过扩展和修改FdwRoutine结构来扩展FDW的能力，以便引入在MOT引入之前不需要的特性和调用。例如，新增了对以下功能的支持：添加索引、删除索引/表、截断、真空和表/索引内存统计。重点放在了FdwRoutine结构与MogDB日志、复制和检查点机制的集成，以便通过故障为跨表事务提供一致性。在这种情况下，MOT本身有时会通过FDW层发起对MogDB功能的调用。
+
+<br/>
+
+## 创建表和索引
+
+为了支持MOT表的创建，重用了标准的FDW语法。
+
+例如，创建FOREIGN表。
+
+MOT DW机制将指令传递给MOT存储引擎，用于实际建表。同样，我们支持创建索引（create index …）。此功能以前在FDW中不可用，因为表由外部管理，不需要此功能。
+
+为了在MOT FDW中支持两者，ValidateTableDef函数实际上创建了指定的表。它还处理该关系的索引创建，DROP TABLE和DROP INDEX，以及先前在FDW中不支持的VACUUM和ALTER TABLE。
+
+<br/>
+
+## 索引规划与执行的使用方法
+
+查询分为两个阶段：规划和执行。在规划阶段（可能在多次执行中才出现一次），选择扫描的最佳索引。该选择基于匹配查询的WHERE子句、JOIN子句和ORDER BY条件。在执行期间，查询迭代相关的表行，并执行各种任务，如每次迭代的更新或删除。插入是一种特殊情况-表将行添加到所有索引中，且不需要扫描。
+
+- **规划器**：在标准FDW中，将查询传递给外部数据源执行。这意味着索引过滤和实际规划（例如索引的选择）不在数据库中本地执行，而是在外部数据源中执行。在内部，FDW向数据库规划器返回总体计划。MOT表的处理方式与磁盘表类似。这意味着相关的MOT索引得到过滤和匹配，最小化遍历行集的索引被选择并添加到计划中。
+- **执行器**：查询执行器使用所选的MOT索引来迭代表的相关行。每个行都由MogDB封装检查，根据查询条件调用update或delete处理相应的行。
+
+<br/>
+
+## 持久性、复制性和高可用性
+
+存储引擎负责存储、读取、更新和删除底层内存和存储系统中的数据。存储引擎不处理日志、检查点和恢复，特别是因为某些事务包含多个不同存储引擎的表。因此，为了数据持久化和复制，MogDB封装使用如下高可用性设施：
+
+- **持久性**：MOT引擎通过WAL记录使数据持久化，WAL记录使用MogDB的XLOG接口。这为MogDB提供了使用相同API进行复制的好处。具体请参见[MOT持久性概念](3-6)。
+- **检查点设定**：通过向MogDB Checkpointer注册回调来启用MOT检查点每当执行通用数据库检查点时，MOT检查点也被调用。MOT保留了检查点的日志序列号（LSN），以便与MogDB恢复对齐。MOT Checkpointing算法是高度优化的异步算法，不会停止并发事务。具体请参见[MOT检查点概念](3-6#mot检查点概念)。
+- **恢复**：启动时，MogDB首先调用MOT回调，通过加载到内存行并创建索引来恢复MOT检查点，然后根据检查点的LSN重放记录来执行WAL恢复。MOT检查点使用多线程并行恢复，每个线程读取不同的数据段。这使MOT检查点在多核硬件上的恢复速度相当快，尽管可能比仅重放WAL记录的基于磁盘的表慢一些。具体请参见[MOT恢复概念](3-7)。
+
+<br/>
+
+## VACUUM和DROP
+
+为了最大化MOT功能，我们增加了对VACUUM、DROP TABLE和DROP INDEX的支持。这三个操作都使用排他表锁执行，这意味着不允许在表上并发事务。系统VACUUM调用一个新的FDW函数执行MOT真空，而ValidateTableDef()函数中增加了DROP。
+
+<br/>
+
+## 删除内存池
+
+每个索引和表都跟踪它使用的所有内存池。DROP INDEX命令用于删除元数据。内存池作为单个连续块被删除。MOT VACUUM只对已使用的内存进行压缩，因为内存回收由基于epoch的垃圾收集器（GC）在后台持续进行。为了执行压缩，我们将索引或表切换到新的内存池，遍历所有实时数据，删除每行并使用新池插入数据，最后删除池，就像执行DROP那样。
+
+<br/>
+
+## 查询本机编译（JIT）
+
+MOT引擎的FDW适配器还包含一个轻量级执行路径，该路径使用LLVM编译器执行JIT编译查询。
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-4.md b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-4.md
new file mode 100644
index 0000000000000000000000000000000000000000..3c6a0fd939cdd5620b48376774a5a7c88e8dbe09
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-4.md
@@ -0,0 +1,22 @@
+---
+title: NUMA-aware分配和亲和性
+summary: NUMA-aware分配和亲和性
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# NUMA-aware分配和亲和性
+
+非统一内存访问（NUMA）是一种计算机内存设计，用于多重处理，其中内存访问时间取决于内存相对于处理器的位置。处理器可以利用NUMA的优势，优先访问本地内存（速度更快），而不是访问非本地内存（这意味着它不会访问另一个处理器的本地内存或处理器之间共享的内存）。
+
+MOT内存访问设计时采用了NUMA感知。即MOT意识到内存不是统一的，而是通过访问最快和最本地的内存来获得最佳性能。
+
+NUMA的优点仅限于某些类型的工作负载，特别是数据通常与某些任务或用户强相关的服务器上的工作负载。
+
+在NUMA平台上运行的内储存数据库系统面临一些问题，例如访问远程主内存时，时延增加和带宽降低。为了应对这些NUMA相关问题，NUMA感知必须被看作是数据库系统基本架构的主要设计原则。
+
+为了便于快速操作和高效利用NUMA节点，MOT为每个表的行分配一个指定的内存池，同时为索引的节点分配一个指定的内存池。每个内存池由多个2MB的块组成。指定API从本地NUMA节点、来自所有节点的页面或通过轮询分配这些块，每个块在下一个节点上分配。默认情况下，共享数据池以轮询方式分配，以保持访问均衡，同时避免在不同NUMA节点之间拆分行。但是，线程专用内存是从一个本地节点分配的，必须验证线程始终运行在同一个NUMA节点中。
+
+**总结**
+
+MOT有一个智能内存控制模块，它预先为各种类型的内存对象分配了内存池。这种智能内存控制可以提高性能，减少锁并保证稳定性。事务的内存对象分配始终是NUMA-local，从而保证了CPU内存访问的最佳性能，降低时延和争用。被释放的对象返回到内存池中。在事务期间最小化使用操作系统的malloc函数可以避免不必要的锁。
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-5.md b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-5.md
new file mode 100644
index 0000000000000000000000000000000000000000..49eafd3ede80698f565e5de48c93345bc981510d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-5.md
@@ -0,0 +1,43 @@
+---
+title: MOT索引
+summary: MOT索引
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# MOT索引
+
+MOT索引基于最先进的Masstree的免锁索引，用于多核系统的快速和可扩展的键值（KV）存储，通过B+树的Trie实现。在多核服务器和高并发工作负载上，性能优异。它使用各种先进的技术，如乐观锁方法、缓存感知和内存预取。
+
+在比较了各种最先进的解决方案之后，我们选择了Masstree作为索引，因为它显示了点查询、迭代和修改的最佳总体性能。Masstree是Trie和B+树的组合，用以谨慎利用缓存、预取、乐观导航和细粒度锁定。它针对高争用进行了优化，并对其前代产品增加了许多优化，如OLFIT。然而，Masstree索引的缺点是它的内存消耗更高。虽然行数据占用相同的内存大小，但每个索引（主索引或辅助索引）的每行内存平均高了16字节-基于磁盘的表使用基于锁的B树，大小为29字节，而MOT的Masstree大小为45字节。
+
+我们的实证研究表明，成熟的免锁Masstree实现与我们对Silo的强大改进相结合，恰能为我们解决这一方面的问题。
+
+另一个挑战是对具有多个索引的表使用乐观插入。
+
+Masstree索引是用于数据和索引管理的MOT内存布局的核心。我们的团队增强并显著改进了Masstree，同时提交了一些关键贡献给Masstree开源。这些改进包括：
+
+- 每个索引都有专用内存池：高效分配和快速索引下移
+- Masstree全球GC：快速按需内存回收
+- 具有插入键访问的大众树迭代器实现
+- ARM架构支持
+
+我们为Masstree开放源码实现贡献了我们的Masstree索引改进，可以在[https://github.com/kohler/masstree-beta](https://github.com/kohler/masstree-beta)找到。
+
+MOT的主要创新是增强了原有的Masstree数据结构和算法，它不支持非唯一索引（作为二级索引）。设计细节请参见[非唯一索引](#非唯一索引)。
+
+MOT支持主索引、辅助索引和无键索引（受[不支持的索引DDL和索引](4-mot-usage#不支持的索引ddl和索引)中提到的限制）。
+
+<br/>
+
+## 非唯一索引
+
+一个非唯一索引可以包含多个具有相同键的行。非唯一索引仅用于通过维护频繁使用的数据值的排序来提高查询性能。例如，数据库可能使用非唯一索引对来自同一家庭的所有人员进行分组。但是，Masstree数据结构实现不允许将多个对象映射到同一个键。我们用于创建非唯一索引的解决方案（如下图所示）是为映射行的键添加一个打破对称的后缀。这个添加的后缀是指向行本身的指针，该行具有8个字节的常量大小，并且值对该行是唯一的。当插入到非唯一索引时，哨兵的插入总是成功的，这使执行事务分配的行能够被使用。这种方法还使MOT能够为非唯一索引提供一个快速、可靠、基于顺序的迭代器。
+
+**图 1** 非唯一索引
+
+![非唯一索引](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-indexes-1.png)
+
+上图描述了一个MOT的T表的结构，它有三个行和两个索引。矩形表示数据行，索引指向指向行的哨兵（椭圆形）。哨兵用键插入唯一索引，用键+后缀插入非唯一索引。哨兵可以方便维护操作，无需接触索引数据结构就可替换行。此外，在哨兵中嵌入了各种标志和参考计数，以便于乐观插入。
+
+查找非唯一辅助索引时，会使用所需的键（如姓氏）。全串联键只用于插入和删除操作。插入和删除操作总是将行作为参数获取，从而可以创建整个键，并在执行删除或插入索引的特定行时使用它。
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-6.md b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-6.md
new file mode 100644
index 0000000000000000000000000000000000000000..21161c18e11bebff26c9b443cfb3341171b13e19
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-6.md
@@ -0,0 +1,208 @@
+---
+title: MOT持久性概念
+summary: MOT持久性概念
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# MOT持久性概念
+
+持久性是指长期的数据保护（也称为磁盘持久性）。持久性意味着存储的数据不会遭受任何形式的退化或破坏，因此数据不会丢失或损坏。持久性可确保在有计划停机（例如维护）或计划外崩溃（例如电源故障）后数据和MOT引擎恢复到一致状态。
+
+内存存储是易失的，需要电源来维护所存储的信息。另一方面，磁盘存储是非易失性的，这意味着它不需要电源来维护存储的信息，因此它不用担心停电。MOT使用这两种类型的存储，它拥有内存中的所有数据，同时将事务性更改持久化到磁盘，并保持频繁的定期**MOT检查点**，以确保在关机时恢复数据。
+
+用户必须保证有足够的磁盘空间用于日志记录和检查点操作。检查点使用单独的驱动器，通过减少磁盘I/O负载来提高性能。
+
+有关如何在MOT引擎中实现持久性的概述，请参见[MOT关键技术](3-mot-key-technologies)。
+
+MOT的WAL重做日志和检查点启用了持久性，如下所述。
+
+- [MOT日志记录：WAL重做日志概念](#mot日志记录wal重做日志概念)
+- [MOT检查点概念](#mot检查点概念)
+
+<br/>
+
+## MOT日志记录：WAL重做日志概念
+
+### 概述
+
+预写日志记录（WAL）是确保数据持久性的标准方法。WAL的主要概念是，数据文件（表和索引所在的位置）的更改只有在记录这些更改之后才会写入，即只有在描述这些更改的日志记录被刷新到永久存储之后才会写入。
+
+MOT全面集成MogDB的封装日志记录设施。除持久性外，这种方法的另一个好处是能够将WAL用于复制目的。
+
+支持三种日志记录方式：两种标准同步和一种异步方式。标准MogDB磁盘引擎也支持这三种日志记录方式。此外，在MOT中，组提交（Group-Commit）选项还提供了特殊的NUMA感知优化。Group-Commit在维护ACID属性的同时提供最高性能。
+
+为保证持久性，MOT全面集成MogDB的WAL机制，通过MogDB的XLOG接口持久化WAL记录。这意味着，每次MOT记录的添加、更新和删除都记录在WAL中。这确保了可以从这个非易失性日志中重新生成和恢复最新的数据状态。例如，如果向表中添加了3个新行，删除了2个，更新了1个，那么日志中将记录6个条目。
+
+- MOT日志记录和MogDB磁盘表的其他记录写入同一个WAL中。
+- MOT只记录事务提交阶段的操作。
+- MOT只记录更新的增量记录，以便最小化写入磁盘的数据量。
+- 在恢复期间，从最后一个已知或特定检查点加载数据；然后使用WAL重做日志完成从该点开始发生的数据更改。
+- WAL重做日志将保留所有表行修改，直到执行一个检查点为止（如上所述）。然后可以截断日志，以减少恢复时间和节省磁盘空间。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 为了确保日志IO设备不会成为瓶颈，日志文件必须放在具有低时延的驱动器上。
+
+<br/>
+
+### 日志类型
+
+支持两个同步事务日志选项和一个异步事务日志选项（标准MogDB磁盘引擎也支持这些选项）。MOT还支持同步的组提交日志记录与NUMA感知优化，如下所述。
+
+根据您的配置，实现以下类型的日志记录：
+
+- **同步重做日志记录**
+
+  同步重做日志记录选项是最简单、最严格的重做日志记录器。当客户端应用程序提交事务时，事务重做条目记录在WAL重做日志中，如下所示：
+
+  1. 当事务正在进行时，它存储在MOT内存中。
+  2. 事务完成后，客户端应用程序发送提交命令，该事务被锁定，然后写入磁盘上的WAL重做日志。这意味着，当事务日志条目写入日志时，客户端应用程序仍在等待响应。
+  3. 一旦事务的整个缓冲区被写入日志，就更改内存中的数据，然后提交事务。事务提交后，客户端应用程序收到事务完成通知。
+
+  **技术说明**
+
+  当事务结束时，同步重做日志处理程序（SynchronousRedoLogHandler）序列化事务缓冲区，并写入XLOG iLogger实现。
+
+  **图 1** 同步日志记录
+
+  ![同步日志记录](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-durability-concepts-1.png)
+
+  **总结**
+
+  **同步重做日志记录**选项是最安全、最严格的，因为它确保了客户端应用程序和每个事务提交时的WAL重做日志条目的完全同步，从而确保了总的持久性和一致性，并且绝对不会丢失数据。此日志记录选项可防止客户端应用程序在事务尚未持久化到磁盘时将事务标记为成功的情况。
+
+  同步重做日志记录选项的缺点是，它是三个选项中最慢的日志机制。这是因为客户端应用程序必须等到所有数据都写入磁盘，并且磁盘频繁写入（这通常使数据库变慢）。
+
+- **组同步重做日志记录**
+
+  **组同步重做日志记录**选项与**同步重做日志记录**选项非常相似，因为它还确保完全持久性，绝对不会丢失数据，并保证客户端应用程序和WAL重做日志条目的完全同步。不同的是，**组同步重做日志记录**选项将事务重做条目组同时写入磁盘上的WAL重做日志，而不是在提交时写入每个事务。使用组同步重做日志记录可以减少磁盘I/O数量，从而提高性能，特别是在运行繁重的工作负载时。
+
+  MOT引擎通过根据运行事务的核的NUMA槽位自动对事务进行分组，使用非统一内存访问（NUMA）感知优化来执行同步的组提交记录。
+
+  有关NUMA感知内存访问的更多信息，请参见[NUMA-aware分配和亲和性](3-4)。
+
+  当一个事务提交时，一组条目记录在WAL重做日志中，如下所示：
+
+  1. 当事务正在进行时，它存储在内存中。MOT引擎根据运行事务的核的NUMA槽位对桶中的事务进行分组。这意味着在同一槽位上运行的所有事务都被分在一组，并且多个组将根据事务运行的核心并行填充。
+
+     这样，将事务写入WAL更为有效，因为来自同一个槽位的所有缓冲区都一起写入磁盘。
+
+     > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** - 每个线程在属于单个槽位的单核/CPU上运行，每个线程只写运行于其上的核的槽位。
+
+  2. 在事务完成并且客户端应用程序发送Commit命令之后，事务重做日志条目将与属于同一组的其他事务一起序列化。
+
+  3. 当特定一组事务满足配置条件后，如《重做日志（MOT）》小节中描述的已提交的事务数或超时时间，该组中的事务将被写入磁盘的WAL中。这意味着，当这些日志条目被写入日志时，发出提交请求的客户端应用程序正在等待响应。
+
+  4. 一旦NUMA-aware组中的所有事务缓冲区都写入日志，该组中的所有事务都将对内存存储执行必要的更改，并且通知客户端这些事务已完成。
+
+  **技术说明**
+
+  4种颜色分别代表4个NUMA节点。因此，每个NUMA节点都有自己的内存日志，允许多个连接的组提交。
+
+  **图 2** 组提交-具有NUMA感知
+
+  ![组提交-具有NUMA感知](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-durability-concepts-2.png)
+
+  **总结**
+
+  组同步重做日志记录选项是一个极其安全和严格的日志记录选项，因为它保证了客户端应用程序和WAL重做日志条目的完全同步，从而确保总的持久性和一致性，并且绝不会丢失数据。此日志记录选项可防止客户端应用程序在事务尚未持久化到磁盘时将事务标记为成功的情况。
+
+  一方面，该选项的磁盘写入次数比同步重做日志记录选项少，这可能意味着它更快。缺点是事务被锁定的时间更长，这意味着它们被锁定，直到同一NUMA内存中的所有事务都写入磁盘上的WAL重做日志为止。
+
+  使用此选项的好处取决于事务工作负载的类型。例如，此选项有利于事务多的系统（而对于事务少的系统而言，则较少使用，因为磁盘写入量也很少）。
+
+- **异步重做日志记录**
+
+  **异步重做日志记录**选项是最快的日志记录方法，但是，它不能确保数据不会丢失。也就是说，某些仍位于缓冲区且尚未写入磁盘的数据在电源故障或数据库崩溃时可能会丢失。当客户端应用程序提交事务时，事务重做条目将记录在内部缓冲区中，并按预先配置的时间间隔写入磁盘。客户端应用程序不会等待数据写入磁盘，而是继续到下一个事务。因此异步重做日志记录的速度最快。
+
+  当客户端应用程序提交事务时，事务重做条目记录在WAL重做日志中，如下所示：
+
+  1. 当事务正在进行时，它存储在MOT内存中。
+  2. 在事务完成并且客户端应用程序发送Commit命令后，事务重做条目将被写入内部缓冲区，但尚未写入磁盘。然后更改MOT数据内存，并通知客户端应用程序事务已提交。
+  3. 后台运行的重做日志线程按预先配置的时间间隔收集所有缓存的重做日志条目，并将它们写入磁盘。
+
+  **技术说明**
+
+  在事务提交时，事务缓冲区被移到集中缓冲区（指针分配，而不是数据副本），并为事务分配一个新的事务缓冲区。一旦事务缓冲区移动到集中缓冲区，且事务线程不被阻塞，事务就会被释放。实际写入日志使用Postgres WALWRITER线程。当WALWRITER计时器到期时，它首先调用异步重做日志处理程序（通过注册的回调）来写缓冲区，然后继续其逻辑，并将数据刷新到XLOG中。
+
+  **图 3** 异步日志记录
+
+  ![异步日志记录](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-durability-concepts-3.png)
+
+  **总结**
+
+  异步重做日志记录选项是最快的日志记录选项，因为它不需要客户端应用程序等待数据写入磁盘。此外，它将许多事务重做条目分组并把它们写入一起，从而减少降低MOT引擎速度的磁盘I/O数量。
+
+  异步重做日志记录选项的缺点是它不能确保在崩溃或失败时数据不会丢失。已提交但尚未写入磁盘的数据在提交时是不持久的，因此在出现故障时无法恢复。异步重做日志记录选项对于愿意牺牲数据恢复（一致性）而不是性能的应用程序来说最为相关。
+
+  日志记录设计细节
+
+  下面将详细介绍内储存引擎模块中与持久化相关的各个组件的设计细节。
+
+  **图 4** 三种日志记录选项
+
+  ![三种日志记录选项](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-durability-concepts-4.png)
+
+重做日志组件由使用内储存引擎的后端线程和WAL编写器使用，以便持久化其数据。检查点通过Checkpoint管理器执行，由Postgres的Checkpointer触发。
+
+- **日志记录设计概述**
+
+  预写日志记录（WAL）是确保数据持久性的标准方法。WAL的核心概念是，数据文件（表和索引所在的位置）的更改只有在记录了这些更改之后才会写入，这意味着在描述这些更改的日志记录被刷新到永久存储之后。
+
+  在内储存引擎中，我们使用现有的MogDB日志设施，并没有从头开始开发低级别的日志API，以减少开发时间并使其可用于复制目的。
+
+- **单事务日志记录**
+
+  在内储存引擎中，事务日志记录存储在事务缓冲区中，事务缓冲区是事务对象（TXN）的一部分。在调用addToLog()时记录事务缓冲区-如果缓冲区超过阈值，则将其刷新并重新使用。当事务提交并通过验证阶段或由于某种原因中止时，相应的消息也会保存在日志中，以便能够在恢复期间确定事务的状态。
+
+**图 5** 单事务日志记录
+
+![单事务日志记录](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/mot-durability-concepts-5.png)
+
+并行日志记录由MOT和磁盘引擎执行。但是，MOT引擎通过每个事务的日志缓冲区、无锁准备和单个日志记录增强了这种设计。
+
+- **异常处理**
+
+  持久化模块通过Postgres错误报告基础设施（ereport）处理异常。系统日志中会记录每个错误情况的错误信息。此外，使用Postgres内置的错误报告基础设施将错误报告到封装。
+
+  该模块上报有如下异常：
+
+**表 1** 异常处理
+
+| 异常条件                 | 异常码                         | 场景描述                               | 最终结果       |
+| :----------------------- | :----------------------------- | :------------------------------------- | :------------- |
+| WAL写入失败              | ERRCODE_FDW_ERROR              | 在任何情况下，WAL写入失败              | 事务终止       |
+| 文件IO错误：写入、打开等 | ERRCODE_IO_ERROR               | 检查点：在任何文件访问错误时调用       | 严重：进程存在 |
+| 内存不足                 | ERRCODE_INSUFFICIENT_RESOURCES | 检查点：本地内存分配失败               | 严重：进程存在 |
+| 逻辑、DB错误             | ERRCODE*INTERNAL*错误          | 检查点：算法失败或无法检索表数据或索引 | 严重：进程存在 |
+
+<br/>
+
+## MOT检查点概念
+
+在MogDB中，检查点是事务序列中一个点的快照，在该点上，可以保证堆和索引数据文件已经同步了检查点之前写入的所有信息。
+
+在执行检查点时，所有脏数据页都会刷新到磁盘，并将一个特殊的检查点记录写入日志文件。
+
+数据直接存储在内存中。MOT没有像MogDB那样存储数据，因此不存在脏页的概念。
+
+为此，我们研究并实现了CALC算法，该算法在耶鲁大学发布的Low-Overhead Asynchronous Checkpointing in Main-Memory Database Systems, SIGMOND 2016中得到了描述。
+
+主内存数据库系统中的低开销异步检查点。
+
+<br/>
+
+### CALC检查点算法：内存和计算开销低
+
+检查点算法具有以下优点：
+
+- 降低内存使用量-每条记录在任何时候最多存储两个副本。在记录处于活动且稳定版本相同或没有记录任何检查点时，仅存储记录的一个物理副本，可以最大限度地减少内存使用。
+- **低开销**：CALC的开销比其他异步检查点算法小。
+- **使用虚拟一致性点**：CALC不需要静默数据库以实现物理一致性点。
+
+<br/>
+
+### 检查点激活
+
+MOT检查点被集成到MogDB的封装的检查点机制中。检查点流程可以通过执行**CHECKPOINT**；命令手动触发，也可以根据封装的检查点触发设置（时间/大小）自动触发。
+
+检查点配置在mot.conf文件中执行，请参见[检查点（MOT）](3-mot-deployment#检查点mot)部分。
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-7.md b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-7.md
new file mode 100644
index 0000000000000000000000000000000000000000..ab9b9e564af46deb277cda257e6cb90a9b6b8f13
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-7.md
@@ -0,0 +1,24 @@
+---
+title: MOT恢复概念
+summary: MOT恢复概念
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# MOT恢复概念
+
+MOT恢复模块提供了恢复MOT表数据所需的所有功能。恢复模块的主要目标是在计划（例如维护）关闭或计划外（例如电源故障）崩溃后，将数据和MOT引擎恢复到一致的状态。
+
+MogDB数据库恢复（有时也称为冷启动）包括MOT表，并且随着数据库其余部分的恢复而自动执行。MOT恢复模块无缝、全面地集成到MogDB恢复过程中。
+
+MOT恢复有两个主要阶段：检查点恢复和WAL恢复（重做日志）。
+
+MOT检查点恢复在封装的恢复发生之前执行。仅在冷启动事件（PG进程的启动）中执行此操作。它首先恢复元数据，然后插入当前有效检查点的所有行，这由checkpoint_recovery_workers并行完成，每个行都在不同的表中工作。索引在插入过程中创建。
+
+在检查点时，表被分成多个16MB的块，以便多个恢复工作进程可以并行地恢复表。这样做是为了加快检查点恢复速度，它被实现为一个多线程过程，其中每个线程负责恢复不同的段。不同段之间没有依赖关系，因此线程之间没有争用，在更新表或插入新行时也不需要使用锁。
+
+WAL记录作为封装的WAL恢复的一部分进行恢复。MogDB封装会迭代XLOG，根据xlog记录类型执行必要的操作。如果是记录类型为MOT的条目，封装将它转发给MOT 恢复管理器进行处理。如果XLOG条目太旧（即XLOG条目的LSN比检查点的LSN旧），MOT恢复将忽略该条目。
+
+在主备部署中，备用服务器始终处于Recovery状态，以便自动WAL恢复过程。
+
+MOT恢复参数在mot.conf文件中配置，参见[MOT恢复](5-mot-administration#mot恢复)。
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-8.md b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-8.md
new file mode 100644
index 0000000000000000000000000000000000000000..0e7e8a28abee1914e1b477db719283d8411a8f00
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-8.md
@@ -0,0 +1,79 @@
+---
+title: MOT查询原生编译（JIT）
+summary: MOT查询原生编译（JIT）
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# MOT查询原生编译（JIT）
+
+MOT使您可以在执行之前以原生格式（使用PREPARE语句）准备并分析预编译的完整查询。
+
+这种本机格式以后可以更有效地执行（使用EXECUTE命令）。这种类型的执行效率要高得多，因为在执行期间，本机格式绕过了多个数据库处理层。这种分工避免了重复的解析分析操作。Lite Executor模块负责执行预准备查询，其执行路径比封装执行的常规通用计划要快得多。这是通过LLVM使用实时（JIT）编译来实现的。此外，以伪LLVM的形式提供具有潜在相似性能的类似解决方案。
+
+下面是SQL中的PREPARE语法示例：
+
+```
+PREPARE name [ ( data_type [, ...] ) ] AS statement
+```
+
+下面是一个如何在Java应用程序中调用PREPARE和EXECUTE语句的示例：
+
+```java
+conn = DriverManager.getConnection(connectionUrl, connectionUser, connectionPassword);
+
+// Example 1: PREPARE without bind settings
+String query = "SELECT * FROM getusers";
+PreparedStatement prepStmt1 = conn.prepareStatement(query);
+ResultSet rs1 = pstatement.executeQuery())
+while (rs1.next()) {…}
+
+// Example 2: PREPARE with bind settings
+String sqlStmt = "SELECT * FROM employees where first_name=? and last_name like ?";
+PreparedStatement prepStmt2 = conn.prepareStatement(sqlStmt);
+prepStmt2.setString(1, "Mark"); // first name “Mark”
+prepStmt2.setString(2, "%n%"); // last name contains a letter “n”
+ResultSet rs2 = prepStmt2.executeQuery())
+while (rs2.next()) {…}
+```
+
+<br/>
+
+## Prepare
+
+**Prepare**创建一个预处理语句。预处理语句是服务器端对象，可用于优化性能。执行PREPARE语句时，将解析、分析和重写指定的语句。
+
+如果查询语句中提到的表是MOT表，则MOT编译负责对象准备，并基于LLVM将查询编译成IR字节码进行特殊优化。
+
+每当需要新的查询编译时，都会分析查询，并使用实用程序GsCodeGen对象和标准LLVM JIT API （IRBuilder）为查询生成合适的IR字节代码。完成字节代码生成后，代码将被JIT编译到单独的LLVM模块中。编译的代码生成一个C函数指针，以后可以调用该指针直接执行。请注意，这个C函数可以被许多线程并发调用，只要每个线程提供不同的执行上下文（详细信息如下）。每个这样的执行上下文称为“JIT上下文”。
+
+为了进一步提高性能，MOT JIT对其LLVM代码结果应用缓存策略，使它们能够被在不同会话中的相同查询重用。
+
+<br/>
+
+## 执行
+
+当发出EXECUTE命令时，会计划并执行预准备语句（上文所述）。这种分工避免了重复的解析分析工作，同时使执行计划依赖于提供的特定设置值。
+
+当生成的执行查询命令到达数据库时，它使用相应的IR字节代码，在MOT引擎中直接执行该代码，并且执行效率更高。这称为“轻量级执行”。
+
+此外，为了可用性，Lite Executor维护了一个预先分配的JIT源池。每个会话预分配自己的会话本地JIT上下文对象池（用于重复执行预编译查询）。
+
+有关更多详细信息，请参阅“支持Lite执行的查询”和“不支持Lite执行的查询”部分。
+
+<br/>
+
+## JIT编译对比-MogDB盘表与MOT表
+
+目前，MogDB包含针对其基于磁盘的表的JIT/CodeGen查询优化的两种主要形式：
+
+- 加速表达式计算，例如在WHERE子句、目标列表、聚合和投影中。
+- 内联小函数调用。
+
+这些优化是局部的（从某种意义上说，它们不优化整个解释的运算符树或完全替换它），并且主要针对CPU绑定的复杂查询，通常在OLAP用例中可见。查询的执行是在使用解释运算符树的拉模型（Volcano样式处理）中执行的。激活后，每次执行查询时都会执行编译。目前，尚未提供生成的LLVM代码的缓存及其跨会话和查询的重用。
+
+相反，MOT JIT优化为符合MOT JIT优化条件的整个查询提供了LLVM代码。结果代码用于直接执行MOT表，而解释的运算符模型则完全放弃。结果实际上是为整个特定查询执行生成的手写LLVM代码。
+
+另一个显着的概念差异是MOT LLVM代码只在查询的PREPARE阶段为准备查询生成，而不是在查询执行时生成。由于OLTP查询的运行时间相当短，因此这对于OLTP场景尤其重要，这无法在每次查询执行期间生成代码和执行较长的查询编译时间。
+
+最后，在PostgreSQL中，激活PREPARE意味着于同一个会话中具有不同参数的执行之间重用生成的计划。同样，MOT JIT对其LLVM代码结果应用了缓存策略，并扩展了缓存策略，以便在不同会话之间重用。因此，单个查询可以只编译一次，其LLVM代码可以在多个会话中重用，这同样有利于OLTP场景。
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-9.md b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-9.md
new file mode 100644
index 0000000000000000000000000000000000000000..4d0079e24741f438ddc54a2703a42145f767cac2
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/3-concepts-of-mot/3-9.md
@@ -0,0 +1,33 @@
+---
+title: 对比：磁盘与MOT
+summary: 对比：磁盘与MOT
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# 对比：磁盘与MOT
+
+下表简要对比了基于MogDB磁盘的存储引擎和MOT存储引擎的各种特性。
+
+对比：基于磁盘与MOT
+
+| 特性                   | MogDB 磁盘存储  | MogDB MOT引擎           |
+| :--------------------- | :-------------- | :---------------------- |
+| 英特尔x86+鲲鹏ARM      | 是              | 是                      |
+| SQL和功能集覆盖率      | 100%            | 98%                     |
+| 纵向扩容（多核，NUMA） | 低效            | 高效                    |
+| 吞吐量                 | 高              | 极高                    |
+| 时延                   | 低              | 极低                    |
+| 分布式                 | 是              | 是                      |
+| 隔离级别               | RC+SIRR序列化   | RCRRRC+SI（V2版本）     |
+| 并发控制策略           | 悲观            | 乐观                    |
+| 数据容量（数据+索引）  | 不受限制        | 受限于DRAM              |
+| 本地编译               | 否              | 是                      |
+| 复制、恢复             | 是              | 是                      |
+| 复制选项               | 2（同步，异步） | 3（同步、异步、组提交） |
+
+**其中，**
+
+- RR=可重复读取
+- RC=读已提交
+- SI=快照隔离
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/4-appendix/1-references.md b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/4-appendix/1-references.md
new file mode 100644
index 0000000000000000000000000000000000000000..0c6dcc039031c0250e191805dc1b2621b716e4fe
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/4-appendix/1-references.md
@@ -0,0 +1,40 @@
+---
+title: 参考文献
+summary: 参考文献
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# 参考文献
+
+[1] Y. Mao, E. Kohler, and R. T. Morris. Cache craftiness for fast multicore key-value storage. In Proc. 7th ACM European Conference on Computer Systems (EuroSys), Apr. 2012.
+
+[2] K. Ren, T. Diamond, D. J. Abadi, and A. Thomson. Low-overhead asynchronous checkpointing in main-memory database systems. In Proceedings of the 2016 ACM SIGMOD International Conference on Management of Data, 2016.
+
+[3] <https://e.huawei.com/en/products/servers/taishan-server/taishan-2280-v2>
+
+[4] <https://e.huawei.com/en/products/servers/taishan-server/taishan-2480-v2>
+
+[5] Tu, S., Zheng, W., Kohler, E., Liskov, B., and Madden, S. Speedy transactions in multicore in-memory databases. In Proceedings of the Twenty-Fourth ACM Symposium on Operating Systems Principles (New York, NY, USA, 2013), SOSP ’13, ACM, pp. 18-32.
+
+[6] H. Avni at al. Industrial-Strength OLTP Using Main Memory and Many-cores, VLDB 2020.
+
+[7] Bernstein, P. A., and Goodman, N. Concurrency control in distributed database systems. ACM Comput. Surv. 13, 2 (1981), 185-221.
+
+[8] Felber, P., Fetzer, C., and Riegel, T. Dynamic performance tuning of word-based software transactional memory. In Proceedings of the 13th ACM SIGPLAN Symposium on Principles and Practice of Parallel Programming, PPOPP 2008, Salt Lake City, UT, USA, February 20-23, 2008 (2008),
+
+pp. 237-246.
+
+[9] Appuswamy, R., Anadiotis, A., Porobic, D., Iman, M., and Ailamaki, A. Analyzing the impact of system architecture on the scalability of OLTP engines for high-contention workloads. PVLDB 11, 2 (2017),
+
+121-134.
+
+[10] R. Sherkat, C. Florendo, M. Andrei, R. Blanco, A. Dragusanu, A. Pathak, P. Khadilkar, N. Kulkarni, C. Lemke, S. Seifert, S. Iyer, S. Gottapu, R. Schulze, C. Gottipati, N. Basak, Y. Wang, V. Kandiyanallur, S. Pendap, D. Gala, R. Almeida, and P. Ghosh. Native store extension for SAP HANA. PVLDB, 12(12):
+
+2047-2058, 2019.
+
+[11] X. Yu, A. Pavlo, D. Sanchez, and S. Devadas. Tictoc: Time traveling optimistic concurrency control. In Proceedings of the 2016 International Conference on Management of Data, SIGMOD Conference 2016, San Francisco, CA, USA, June 26 - July 01, 2016, pages 1629-1642, 2016.
+
+[12] V. Leis, A. Kemper, and T. Neumann. The adaptive radix tree: Artful indexing for main-memory databases. In C. S. Jensen, C. M. Jermaine, and X. Zhou, editors, 29th IEEE International Conference on Data Engineering, ICDE 2013, Brisbane, Australia, April 8-12, 2013, pages 38-49. IEEE Computer Society, 2013.
+
+[13] S. K. Cha, S. Hwang, K. Kim, and K. Kwon. Cache-conscious concurrency control of main-memory indexes on shared-memory multiprocessor systems. In P. M. G. Apers, P. Atzeni, S. Ceri, S. Paraboschi, K. Ramamohanarao, and R. T. Snodgrass, editors, VLDB 2001, Proceedings of 27th International Conference on Very Large Data Bases, September 11-14, 2001, Roma, Italy, pages 181-190. Morga Kaufmann, 2001.
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/4-appendix/2-glossary.md b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/4-appendix/2-glossary.md
new file mode 100644
index 0000000000000000000000000000000000000000..ff47d4ffa2343ea3d49ce65e70591b5082124865
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/mot-engine/4-appendix/2-glossary.md
@@ -0,0 +1,59 @@
+---
+title: 术语表
+summary: 术语表
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# 术语表
+
+| 缩略语 | 定义描述                                                     |
+| :----- | :----------------------------------------------------------- |
+| 2PL    | 2阶段锁（2-Phase Locking）                                   |
+| ACID   | 原子性（Atomicity），一致性（Consistency），隔离性（Isolation），持久性（Durability） |
+| AP     | 分析处理（Analytical Processing）                            |
+| Arm    | 高级RISC机器（Advanced RISC Machine），x86的替代硬件架构。   |
+| CC     | 并发控制（Concurrency Control）                              |
+| CPU    | 中央处理器（Central Processing Unit）                        |
+| DB     | 数据库（Database）                                           |
+| DBA    | 数据库管理员（Database Administrator）                       |
+| DBMS   | 数据库管理系统（DataBase Management System）                 |
+| DDL    | 数据定义语言（Data Definition Language）数据库模式管理语言   |
+| DML    | 数据修改语言（Data Modification Language）                   |
+| ETL    | 提取、转换、加载或遇时锁定（Extract, Transform, Load or Encounter Time Locking） |
+| FDW    | 外部数据封装（Foreign Data Wrapper）                         |
+| GC     | 垃圾收集器（Garbage Collector）                              |
+| HA     | 高可用性（High Availability）                                |
+| HTAP   | 事务分析混合处理（Hybrid Transactional-Analytical Processing） |
+| IoT    | 物联网（Internet of Things）                                 |
+| IM     | 内储存（In-Memory）                                          |
+| IMDB   | 内储存数据库（In-Memory Database）                           |
+| IR     | 源代码的中间表示（Intermediate Representation），用于编译和优化 |
+| JIT    | 准时（Just In Time）                                         |
+| JSON   | JavaScript对象表示法（JavaScript Object Notation）           |
+| KV     | 键值（Key Value）                                            |
+| LLVM   | 低级虚拟机（Low-Level Virtual Machine），指编译代码或IR查询  |
+| M2M    | 机对机（Machine-to-Machine）                                 |
+| ML     | 机器学习（Machine Learning）                                 |
+| MM     | 主内存（Main Memory）                                        |
+| MO     | 内存优化（Memory Optimized）                                 |
+| MOT    | 内存优化表存储引擎（SE），读作/em/ /oh/ /tee/                |
+| MVCC   | 多版本并发控制（Multi-Version Concurrency Control）          |
+| NUMA   | 非一致性内存访问（Non-Uniform Memory Access）                |
+| OCC    | 乐观并发控制（Optimistic Concurrency Control）               |
+| OLTP   | 在线事务处理（On-Line Transaction Processing），多用户在线交易类业务 |
+| PG     | PostgreSQL                                                   |
+| RAW    | 写后读校验（Reads-After-Writes）                             |
+| RC     | 返回码（Return Code）                                        |
+| RTO    | 目标恢复时间（Recovery Time Objective）                      |
+| SE     | 存储引擎（Storage Engine）                                   |
+| SQL    | 结构化查询语言（Structured Query Language）                  |
+| TCO    | 总体拥有成本（Total Cost of Ownership）                      |
+| TP     | 事务处理（Transactional Processing）                         |
+| TPC-C  | 一种联机事务处理基准                                         |
+| Tpm-C  | 每分钟事务数-C. TPC-C基准的性能指标，用于统计新订单事务。    |
+| TVM    | 微小虚拟机（Tiny Virtual Machine）                           |
+| TSO    | 分时选项（Time Sharing Option）                              |
+| UDT    | 自定义类型                                                   |
+| WAL    | 预写日志（Write Ahead Log）                                  |
+| XLOG   | 事务日志的PostgreSQL实现（WAL，如上文所述）                  |
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/primary-and-standby-management.md b/product/zh/docs-mogdb/v3.0/administrator-guide/primary-and-standby-management.md
new file mode 100644
index 0000000000000000000000000000000000000000..788f92a61cc8f52c4cd5d3c58e3bb85f842f9bea
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/primary-and-standby-management.md
@@ -0,0 +1,134 @@
+---
+title: 主备管理
+summary: 主备管理
+author: Guo Huan
+date: 2021-03-11
+---
+
+# 主备管理
+
+## 操作场景
+
+MogDB在运行过程中，数据库管理员可能需要手工对数据库节点做主备切换。例如发现数据库节点主备failover后需要恢复原有的主备角色，或怀疑硬件故障需要手动进行主备切换。级联备机不能直接转换为主机，只能先通过switchover或者failover成为备机，然后再切换为主机。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+>
+> - 主备切换为维护操作，确保MogDB状态正常，所有业务结束后，再进行切换操作。
+> - 在开启极致RTO时，不支持级联备机。级联备机因为极致RTO开启情况下，备机不支持连接无法同步数据。
+
+<br/>
+
+## 操作步骤
+
+1. 以操作系统用户omm登录数据库任意节点，执行如下命令，查看主备情况。
+
+    ```bash
+    gs_om -t status --detail
+    ```
+
+2. 以操作系统用户omm登录准备切换为主节点的备节点，执行如下命令。
+
+    ```bash
+    gs_ctl switchover -D /home/omm/cluster/dn1/
+    ```
+
+    /home/omm/cluster/dn1/为备数据库节点的数据目录。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:** 对于同一数据库，上一次主备切换未完成，不能执行下一次切换。对于业务正在操作时，发起switchover，可能主机的线程无法停止导致switchover显示超时，实际后台仍然在运行，等主机线程停止后，switchover即可完成。比如在主机删除一个大的分区表时，可能无法响应switchover发起的信号。
+
+3. switchover成功后，执行如下命令记录当前主备机器信息。
+
+    ```bash
+    gs_om -t refreshconf
+    ```
+
+<br/>
+
+## 示例
+
+将数据库节点备实例切换为主实例。
+
+1. 查询数据库状态。
+
+   ```bash
+   gs_om -t status --detail
+   [   Cluster State   ]
+
+   cluster_state   : Normal
+   redistributing  : No
+   current_az      : AZ_ALL
+
+   [  Datanode State   ]
+
+       node             node_ip         port      instance                            state
+   --------------------------------------------------------------------------------------------------
+   1  pekpopgsci00235  10.244.62.204    5432      6001 /home/omm/cluster/dn1/   P Primary Normal
+   2  pekpopgsci00238  10.244.61.81     5432      6002 /home/omm/cluster/dn1/   S Standby Normal
+   ```
+
+2. 登录备节点，进行主备切换。另外，switchover级联备机后，级联备机切换为备机，原备机将为级联备。
+
+   ```bash
+   gs_ctl switchover -D /home/omm/cluster/dn1/
+   [2020-06-17 14:28:01.730][24438][][gs_ctl]: gs_ctl switchover ,datadir is -D "/home/omm/cluster/dn1"
+   [2020-06-17 14:28:01.730][24438][][gs_ctl]: switchover term (1)
+   [2020-06-17 14:28:01.768][24438][][gs_ctl]: waiting for server to switchover............
+   [2020-06-17 14:28:11.175][24438][][gs_ctl]: done
+   [2020-06-17 14:28:11.175][24438][][gs_ctl]: switchover completed (/home/omm/cluster/dn1)
+   ```
+
+3. 保存数据库主备机器信息。
+
+   ```bash
+   gs_om -t refreshconf
+   Generating dynamic configuration file for all nodes.
+   Successfully generated dynamic configuration file.
+   ```
+
+<br/>
+
+## 错误排查
+
+如果switchover过程中出现失败，请根据日志文件中的日志信息排查错误，参见[日志参考](11-log-reference)。
+
+<br/>
+
+## 异常处理
+
+异常判断标准如下:
+
+- 业务压力下，主备实例切换时间长，这种情况不需要处理。
+
+- 其他备机正在build的情况下，主机需要发送日志到备机后，才能降备，导致主备切换时间长。这种情况不需要处理，但应尽量避免build过程中进行主备切换。
+
+- 切换过程中，因网络故障、磁盘满等原因造成主备实例连接断开，出现双主现象时，此时请参考如下步骤修复。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-warning.gif) **警告:** 出现双主状态后，请按如下步骤恢复成正常的主备状态。否则可能会造成数据丢失。
+
+1. 执行以下命令查询数据库当前的实例状态。
+
+    ```bash
+    gs_om -t status --detail
+    ```
+
+    若查询结果显示两个实例的状态都为Primary，这种状态为异常状态。
+
+2. 确定降为备机的节点，在节点上执行如下命令关闭服务。
+
+    ```bash
+    gs_ctl stop -D /home/omm/cluster/dn1/
+    ```
+
+3. 执行以下命令，以standby模式启动备节点。
+
+    ```bash
+    gs_ctl start -D /home/omm/cluster/dn1/ -M standby
+    ```
+
+4. 保存数据库主备机器信息。
+
+    ```bash
+    gs_om -t refreshconf
+    ```
+
+5. 查看数据库状态，确认实例状态恢复。
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/0-starting-and-stopping-mogdb.md b/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/0-starting-and-stopping-mogdb.md
new file mode 100644
index 0000000000000000000000000000000000000000..41ad61ff86d2d21d07952a93df59ecc00fc0935e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/0-starting-and-stopping-mogdb.md
@@ -0,0 +1,66 @@
+---
+title: 启停MogDB
+summary: 启停MogDB
+author: Guo Huan
+date: 2021-06-24
+---
+
+# 启停MogDB
+
+## 启动MogDB
+
+1. 以操作系统用户omm登录数据库主节点。
+
+2. 使用以下命令启动MogDB。
+
+   ```bash
+   gs_om -t start
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 双机启动必须以双机模式启动，若中间过程以单机模式启动，则必须修复才能恢复双机关系，用gs_ctl build进行修复，gs_ctl的使用方法参见“参考指南 > 工具参考 > 系统内部使用的工具 > [gs_ctl](4-gs_ctl)”章节。
+
+## 停止MogDB
+
+1. 以操作系统用户omm登录数据库主节点。
+
+2. 使用以下命令停止MogDB。
+
+   ```bash
+   gs_om -t stop
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+   > 启停节点及AZ的操作请参见“参考指南 > 工具参考 > 服务端工具 > [gs_om](8-gs_om)”章节。
+
+## 示例
+
+启动MogDB：
+
+```bash
+gs_om -t start
+Starting cluster.
+=========================================
+=========================================
+Successfully started.
+```
+
+停止MogDB：
+
+```bash
+gs_om -t stop
+Stopping cluster.
+=========================================
+Successfully stopped cluster.
+=========================================
+End stop cluster.
+```
+
+## 错误排查
+
+如果启动MogDB或者停止MogDB服务失败，请根据日志文件中的日志信息排查错误，参见[日志参考](11-log-reference)。
+
+如果是超时导致启动失败，可以执行如下命令，设置启动超时时间，默认超时时间为300s。
+
+```bash
+gs_om -t start --time-out=300
+```
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/1-routine-maintenance-check-items.md b/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/1-routine-maintenance-check-items.md
new file mode 100644
index 0000000000000000000000000000000000000000..a676de71e3fd028572618b16fa03ff009ce8947c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/1-routine-maintenance-check-items.md
@@ -0,0 +1,178 @@
+---
+title: 日常运维
+summary: 日常运维
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# 日维护检查项
+
+## 检查MogDB状态
+
+通过MogDB提供的工具查询数据库和实例状态，确认数据库和实例都处于正常的运行状态，可以对外提供数据服务。
+
+- 检查实例状态
+
+    ```bash
+    gs_check -U omm -i CheckClusterState
+    ```
+
+- 检查参数
+
+    ```sql
+    mogdb=# SHOW parameter_name;
+    ```
+
+  上述命令中，parameter_name需替换成具体的参数名称。
+
+- 修改参数
+
+    ```bash
+    gs_guc reload  -D /mogdb/data/dbnode -c "paraname=value"
+    ```
+
+<br/>
+
+## 检查锁信息
+
+锁机制是数据库保证数据一致性的重要手段，检查相关信息可以检查数据库的事务和运行状况。
+
+- 查询数据库中的锁信息
+
+    ```sql
+    mogdb=# SELECT * FROM pg_locks;
+    ```
+
+- 查询等待锁的线程状态信息
+
+    ```sql
+    mogdb=# SELECT * FROM pg_thread_wait_status WHERE wait_status = 'acquire lock';
+    ```
+
+- 结束系统进程
+
+    查找正在运行的系统进程，然后使用kill命令结束此进程。
+
+    ```bash
+    ps ux
+    kill -9 pid
+    ```
+
+<br/>
+
+## 统计事件数据
+
+SQL语句长时间运行会占用大量系统资源，用户可以通过查看事件发生的时间，占用内存大小来了解现在数据库运行状态。
+
+- 查询事件的时间
+
+    查询事件的线程启动时间、事务启动时间、SQL启动时间以及状态变更时间。
+
+    ```sql
+    mogdb=# SELECT backend_start,xact_start,query_start,state_change FROM pg_stat_activity;
+    ```
+
+- 查询当前服务器的会话计数信息
+
+    ```sql
+    mogdb=# SELECT count(*) FROM pg_stat_activity;
+    ```
+
+- 查询系统级统计信息
+
+    查询当前使用内存最多的会话信息。
+
+    ```sql
+    mogdb=# SELECT * FROM pv_session_memory_detail() ORDER BY usedsize desc limit 10;
+    ```
+
+<br/>
+
+## 对象检查
+
+表、索引、分区、约束等是数据库的核心存储对象，其核心信息和对象维护是DBA重要的日常工作。
+
+- 查看表的详细信息
+
+    ```sql
+    mogdb=# \d+ table_name
+    ```
+
+- 查询表统计信息
+
+    ```sql
+    mogdb=# SELECT * FROM pg_statistic;
+    ```
+
+- 查看索引的详细信息
+
+    ```sql
+    mogdb=# \d+ index_name
+    ```
+
+- 查询分区表信息
+
+    ```sql
+    mogdb=# SELECT * FROM pg_partition;
+    ```
+
+- 收集统计信息
+
+    使用ANALYZE语句收集数据库相关的统计信息。
+
+    使用VACUUM语句可以回收空间并更新统计信息。
+
+- 查询约束信息
+
+    ```sql
+    mogdb=# SELECT * FROM pg_constraint;
+    ```
+
+<br/>
+
+## SQL报告检查
+
+使用EXPLAIN语句查看执行计划。
+
+<br/>
+
+### 备份
+
+数据备份重于一切，日常应检查备份执行情况，并检查备份有效性，确保备份能够保障数据安全，备份安全加密也应兼顾。
+
+- 指定用户导出数据库
+
+    ```bash
+    gs_dump dbname -p port -f out.sql -U user_name -W password
+    ```
+
+- 导出schema
+
+    ```bash
+    gs_dump dbname -p port -n schema_name -f out.sql
+    ```
+
+- 导出table:
+
+    ```bash
+    gs_dump dbname -p port -t table_name -f out.sql
+    ```
+
+<br/>
+
+### 基本信息检查
+
+基本信息包括版本、组件、补丁集等信息，定期检查数据库信息并登记在案是数据库生命周期管理的重要内容之一。
+
+- 版本信息
+
+    ```sql
+    mogdb=# SELECT version();
+    ```
+
+- 容量检查
+
+    ```sql
+    mogdb=# SELECT pg_table_size('table_name');
+    mogdb=# SELECT pg_database_size('database_name');
+    ```
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/10-data-security-maintenance-suggestions.md b/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/10-data-security-maintenance-suggestions.md
new file mode 100644
index 0000000000000000000000000000000000000000..dd1db26992a82c72aba02d4c80de38c2a90a1b38
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/10-data-security-maintenance-suggestions.md
@@ -0,0 +1,29 @@
+---
+title: 日常运维
+summary: 日常运维
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# 数据安全维护建议
+
+为保证MogDB数据库中的数据安全，避免丢失数据，非法访问数据等事故发生，请仔细阅读以下内容。
+
+**避免数据被丢失**
+
+建议用户规划周期性的物理备份，且对备份文件进行可靠的保存。在系统发生严重错误的情况下，可以利用备份文件，将系统恢复到备份前的状态。
+
+**避免数据被非法访问**
+
+- 建议对数据库用户进行权限分级管理。数据库管理员根据业务需要，建立用户并赋予权限，保证各用户对数据库的合理访问。
+- 对于MogDB的服务端和客户端（或基于客户端库开发的应用程序），最好也部署在可信任的内网中。如果服务端和客户端一定要部署在非信任的网络中，需要在服务启动前，打开SSL加密，保证数据在非信任网络上的传输安全。需要注意的是，打开SSL加密会降低数据库的性能。
+
+**避免系统日志泄露个人数据**
+
+- 将调试日志发给他人进行分析前，请删除个人数据。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:** 因为日志级别（log_min_messages）设置为DEBUGx（x为DEBUG级别，取值范围为1~5）时，调试日志中记录的信息可能包含用户的个人数据。
+
+- 将系统日志发给其他人进行分析前，请删除个人数据。因为在默认配置下，当SQL语句执行错误时，日志中会记录出错的SQL语句，而这些SQL语句中可能包含用户个人数据。
+
+- 将log_min_error_statement参数的值设置为PANIC，可以避免将出错的SQL语句记录在系统日志中。若禁用该功能，当出现故障时，很难定位故障原因。
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/11-log-reference.md b/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/11-log-reference.md
new file mode 100644
index 0000000000000000000000000000000000000000..c69810ae35150ea1e8d9d8172d2d6d3d04cddb37
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/11-log-reference.md
@@ -0,0 +1,153 @@
+---
+title: 日志参考
+summary: 日志参考
+author: Guo Huan
+date: 2021-06-24
+---
+
+# 日志参考
+
+## 日志类型简介
+
+在数据库运行过程中，会出现大量日志，既有保证数据库安全可靠的WAL日志（预写式日志，也称为Xlog），也有用于数据库日常维护的运行和操作日志等。在数据库发生故障时，可以参考这些日志进行问题定位和数据库恢复的操作。
+
+**日志类型**
+
+日志类型的详细说明请参见下表。
+
+**表 1** 日志类型
+
+| 类型       | 说明                                                         |
+| :--------- | :----------------------------------------------------------- |
+| 系统日志   | 数据库系统进程运行时产生的日志，记录系统进程的异常信息。     |
+| 操作日志   | 通过客户端工具（例如gs_guc）操作数据库时产生的日志。         |
+| Trace日志  | 打开数据库的调试开关后，会记录大量的Trace日志。这些日志可以用来分析数据库的异常信息。 |
+| 黑匣子日志 | 数据库系统崩溃的时候，通过故障现场堆、栈信息可以分析出故障发生时的进程上下文，方便故障定位。黑匣子具有在系统崩溃时，dump出进程和线程的堆、栈、寄存器信息的功能。 |
+| 审计日志   | 开启数据库审计功能后，将数据库用户的某些操作记录在日志中，这些日志称为审计日志。 |
+| WAL日志    | 又称为REDO日志，在数据库异常损坏时，可以利用WAL日志进行恢复。由于WAL日志的重要性，所以需要经常备份这些日志。 |
+| 性能日志   | 数据库系统在运行时检测物理资源的运行状态的日志，在对外部资源进行访问时的性能检测，包括磁盘、Hadoop MogDB等外部资源的访问检测信息。 |
+
+## 系统日志
+
+MogDB运行时数据库节点以及MogDB安装部署时产生的日志统称为系统日志。如果MogDB在运行时发生故障，可以通过这些系统日志及时定位故障发生的原因，根据日志内容制定恢复MogDB的方法。
+
+**日志文件存储路径**
+
+数据库节点的运行日志放在“/var/log/mogdb/用户名/pg_log”中各自对应的目录下。
+
+OM MogDB安装卸载时产生的日志放在“/var/log/mogdb/用户名/om”目录下。
+
+**日志文件命名格式**
+
+- 数据库节点运行日志的命名规则：
+
+  postgresql-创建时间.log
+
+  默认情况下，每日0点或者日志文件大于16MB或者数据库实例（数据库节点）重新启动后，会生成新的日志文件。
+
+- CM的运行日志的命名规则：
+
+  - cm_agent的日志：cm_agent-创建时间.log、cm_agent-创建时间-current.log、system_call-创建时间.log、system_call-创建时间-current.log。
+  - cm_server的日志：cm_server-创建时间.log、cm_server-创建时间-current.log；key_event-创建时间.log、key_event-创建时间-current.log。
+  - om_monitor的日志：om_monitor-创建时间.log、om_monitor-创建时间-current.log。
+
+  其中，不带current标识符的文件是历史日志文件，带current标识符的文件是当前日志文件。最初调用进程时，进程会先创建一个带current标识符的日志文件，当该日志文件的大小超过16MB时，会将当前日志文件重命名为历史日志文件，并以当前时间生成新的当前日志文件。
+
+**日志内容说明**
+
+- 数据库节点每一行日志内容的默认格式：
+
+  日期+时间+时区+用户名称+数据库名称+会话ID+日志级别+日志内容
+
+- cm_agent、cm_server、om_monitor每一行日志内容的默认格式：
+
+  时间+时区+会话ID+日志内容
+  SYSTEM_CALL系统调用日志记录了CM_AGENT在运行过程中调用工具命令的情况。
+  key_event每一行日志内容的默认格式: 时间+线程号+线程名: 关键事件类型+仲裁对象实例ID+仲裁细节。
+
+## 操作日志
+
+操作日志是指数据库管理员使用工具操作数据库时以及工具被MogDB调用时产生的日志。如果MogDB发生故障，可以通过这些日志信息跟踪用户对数据库进行了哪些操作，重现故障场景。
+
+**日志文件存储路径**
+
+默认在`$GAUSSLOG/bin`目录下, 如果环境变量`$GAUSSLOG`不存在或者变量值为空，则工具日志信息不会记录到对应的工具日志文件中，日志信息只会打印到屏幕上。
+
+其中`$GAUSSLOG`默认为`/var/log/mogdb/_用户名_`。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+> 如果使用om脚本部署时，则日志路径为`/var/log/mogdb/_用户名_`。
+
+**日志文件命名格式**
+
+日志文件命名格式为：
+
+- 工具名-日志创建时间.log
+- 工具名-日志创建时间-current.log
+
+其中，“工具名-日志创建时间.log”是历史日志文件，“工具名-日志创建时间-current.log”是当前日志文件。
+
+如果日志大小超过16MB，在下一次调用该工具时，会重命名当前日志文件为历史日志文件，并以当前时间生成新的当前日志文件。
+
+例如将“gs_guc-2015-01-16_183728-current.log”重命名为“gs_guc-2015-01-16_183728.log”，然后重新生成“gs_guc-2015-01-17_142216-current.log”。
+
+**维护建议**
+
+建议定时对过期的日志文件进行转储，以避免大量日志占用太多的磁盘空间和避免重要日志丢失。
+
+## 审计日志
+
+审计功能开启时会不断产生大量的审计日志，占用磁盘空间。用户可以根据磁盘空间的大小设置审计日志维护策略。
+
+关于如何设置审计日志维护策略请参见《数据库安全管理》中设置数据库审计 > 维护审计日志”章节。
+
+## WAL日志
+
+预写式日志WAL（Write Ahead Log，也称为Xlog）是实现事务日志的标准方法，对数据文件（表和索引的载体）持久化修改之前必须先持久化相应的日志。如果要修改数据文件，必须是在这些修改操作已经记录到日志文件之后才能进行修改，即在描述这些变化的日志记录刷新到永久存储器之后。在系统崩溃时，可以使用WAL日志对MogDB进行恢复操作。
+
+**日志文件存储路径**
+
+以一个数据库节点为例，默认在`/mogdb/data/data_dn/pg_xlog`目录下。
+
+其中`/mogdb/data/data_dn`代表MogDB节点的数据目录。
+
+**日志文件命名格式**
+
+日志文件以段文件的形式存储的，每个段为16MB，并分割成若干页，每页8KB。对WAL日志的命名说明如下：一个段文件的名称由24个十六进制组成，分为三个部分，每个部分由8个十六进制字符组成。第一部分表示时间线，第二部分表示日志文件标号，第三部分表示日志文件的段标号。时间线由1开始，日志文件标号和日志文件的段标号由0开始。
+
+例如，系统中的第一个事务日志文件是000000010000000000000000。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+> 这些数字一般情况下是顺序增长使用的（要把所有可用数字都用光也需要非常长的时间），但也存在循环使用的情况。
+
+**日志内容说明**
+
+WAL日志的内容取决于记录事务的类型，在系统崩溃时可以利用WAL日志进行恢复。
+
+默认配置下，MogDB每次启动时会先读取WAL日志进行恢复。
+
+**维护建议**
+
+WAL日志对数据库异常恢复有重要的作用，建议定期对WAL日志进行备份。
+
+## 性能日志
+
+性能日志主要关注外部资源的访问性能问题。性能日志指的是数据库系统在运行时检测物理资源的运行状态的日志，在对外部资源进行访问时的性能检测，包括磁盘、Hadoop MogDB等外部资源的访问检测信息。在出现性能问题时，可以借助性能日志及时的定位问题发生的原因，能极大地提升问题解决效率。
+
+**日志文件存储路径**
+
+数据库节点的性能日志目录在“$GAUSSLOG/gs_profile”中各自对应的目录下。
+
+**日志文件命名格式**
+
+数据库节点的性能日志的命名规则：
+
+postgresql-创建时间.prf
+
+默认情况下，每日0点或者日志文件大于20MB或者数据库实例（数据库节点）重新启动后，会生成新的日志文件。
+
+**日志内容说明**
+
+数据库节点每一行日志内容的默认格式：
+
+主机名称+日期+时间+实例名称+线程号+日志内容。
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/2-checking-os-parameters.md b/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/2-checking-os-parameters.md
new file mode 100644
index 0000000000000000000000000000000000000000..c9efaf111968b7e000d34650de1d64faa1b9a05e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/2-checking-os-parameters.md
@@ -0,0 +1,180 @@
+---
+title: 日常运维
+summary: 日常运维
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# 检查操作系统参数
+
+## 检查办法
+
+通过MogDB提供的gs_checkos工具可以完成操作系统状态检查。
+
+**前提条件**
+
+- 当前的硬件和网络环境正常。
+- 各主机间root互信状态正常。
+- 只能使用root用户执行gs_checkos命令。
+
+**操作步骤**
+
+1. 以root用户身份登录任意一台服务器。
+
+2. 执行如下命令对MogDB节点服务器的OS参数进行检查。
+
+    ```
+    gs_checkos -i A
+    ```
+
+    检查节点服务器的OS参数的目的是保证MogDB正常通过预安装，并且在安装成功后可以安全高效的运行。详细的检查项目请参见《参考指南》中“工具参考 > 服务端工具 > [gs_checkos](2-gs_checkos)”章节。
+
+**示例**
+
+执行gs_checkos前需要先使用gs_preinstall工具执行前置脚本，准备环境。以参数“A”为例。
+
+```
+gs_checkos -i A
+Checking items:
+    A1. [ OS version status ]                                   : Normal
+    A2. [ Kernel version status ]                               : Normal
+    A3. [ Unicode status ]                                      : Normal
+    A4. [ Time zone status ]                                    : Normal
+    A5. [ Swap memory status ]                                  : Normal
+    A6. [ System control parameters status ]                    : Normal
+    A7. [ File system configuration status ]                    : Normal
+    A8. [ Disk configuration status ]                           : Normal
+    A9. [ Pre-read block size status ]                          : Normal
+    A10.[ IO scheduler status ]                                 : Normal
+    A11.[ Network card configuration status ]                   : Normal
+    A12.[ Time consistency status ]                             : Warning
+    A13.[ Firewall service status ]                             : Normal
+    A14.[ THP service status ]                                  : Normal
+Total numbers:14. Abnormal numbers:0. Warning number:1.
+```
+
+以参数“B”为例。
+
+```
+gs_checkos -i B
+Setting items:
+    B1. [ Set system control parameters ]                       : Normal
+    B2. [ Set file system configuration value ]                 : Normal
+    B3. [ Set pre-read block size value ]                       : Normal
+    B4. [ Set IO scheduler value ]                              : Normal
+    B5. [ Set network card configuration value ]                : Normal
+    B6. [ Set THP service ]                                     : Normal
+    B7. [ Set RemoveIPC value ]                                 : Normal
+    B8. [ Set Session Process ]                                 : Normal
+Total numbers:6. Abnormal numbers:0. Warning number:0.
+```
+
+<br/>
+
+## 异常处理
+
+使用gs_checkos检查MogDB状态，可以使用如下命令查看详细的错误信息。
+
+```
+gs_checkos -i A --detail
+```
+
+其中，Abnormal为必须处理项，影响MogDB安装。Warning可以不处理，不会影响MogDB安装。
+
+- 如果操作系统版本（A1）检查项检查结果为Abnormal，需要将不属于混编范围的操作系统版本替换为混编范围内的操作系统版本。
+
+- 如果内核版本（A2）检查项检查结果为Warning，则表示MogDB内平台的内核版本不一致。
+
+- 如果Unicode状态（A3）检查项检查结果为Abnormal，需要将各主机的字符集设置为相同的字符集，可以在/etc/profile文件中添加“export LANG=XXX”（XXX为Unicode编码）。
+
+    ```
+    vim /etc/profile
+    ```
+
+- 如果时区状态（A4）检查项检查结果为Abnormal，需要将各主机的时区设置为相同时区，可以将/usr/share/zoneinfo/目录下的时区文件拷贝为/etc/localtime文件。
+
+    ```
+    cp /usr/share/zoneinfo/$地区/$时区 /etc/localtime
+    ```
+
+- 如果交换内存状态（A5）检查项检查结果为Abnormal，可能是因为swap空间大于mem空间，可减小Swap解决或者增大Mem空间解决。
+
+- 如果系统控制参数（A6）检查项检查结果为Abnormal，可以使用以下两种方法进行设置。
+
+  - 可以使用如下命令进行设置。
+
+    ```
+    gs_checkos -i B1
+    ```
+
+  - 根据错误提示信息，在/etc/sysctl.conf文件中进行设置。然后执行sysctl -p使其生效。
+
+    ```
+    vim /etc/sysctl.conf
+    ```
+
+- 如果文件系统配置状态（A7）检查项检查结果为Abnormal，可以使用如下命令进行设置。
+
+    ```
+    gs_checkos -i B2
+    ```
+
+- 如果磁盘配置状态（A8）检查项检查结果为Abnormal，需修改磁盘挂载格式为: "rw,noatime,inode64,allocsize=16m"。
+
+    使用linux的man mount命令挂载XFS选项:
+
+    ```
+    rw,noatime,inode64,allocsize=16m
+    ```
+
+    也可以在/etc/fstab文件中设定XFS选项。如下示例:
+
+    ```
+    /dev/data /data xfs rw,noatime,inode64,allocsize=16m 0 0
+    ```
+
+- 如果预读块大小（A9）检查项检查结果为Abnormal，可以使用如下命令进行设置。
+
+    ```
+    gs_checkos -i B3
+    ```
+
+- 如果IO调度状态（A10）检查项检查结果为Abnormal，可以使用如下命令进行设置。
+
+    ```
+    gs_checkos -i B4
+    ```
+
+- 如果网卡配置状态（A11）检查项检查结果为Warning，可以使用如下命令进行设置。
+
+    ```
+    gs_checkos -i B5
+    ```
+
+- 如果时间一致性（A12）检查项检查结果为Abnormal，需检查是否安装ntp服务，以及ntp服务是否启动；并与ntp时钟源同步。
+
+- 如果防火墙状态（A13）检查项检查结果为Abnormal，需关闭防火墙服务。使用如下命令进行设置。
+
+  - SuSE:
+
+    ```
+    SuSEfirewall2 stop
+    ```
+
+  - RedHat7:
+
+    ```
+    systemctl disable firewalld
+    ```
+
+  - RedHat6:
+
+    ```
+    service iptables stop
+    ```
+
+- 如果THP服务（A14）检查项检查结果为Abnormal，可以使用如下命令进行设置。
+
+    ```
+    gs_checkos -i B6
+    ```
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/3-checking-mogdb-health-status.md b/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/3-checking-mogdb-health-status.md
new file mode 100644
index 0000000000000000000000000000000000000000..e0c89b4d056a962aeba275a958a8fc113a86e07c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/3-checking-mogdb-health-status.md
@@ -0,0 +1,648 @@
+---
+title: 日常运维
+summary: 日常运维
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# 检查MogDB健康状态
+
+## 检查办法
+
+通过MogDB提供的gs_check工具可以开展MogDB健康状态检查。
+
+**注意事项**
+
+- 扩容新节点检查只能在root用户下执行，其他场景都必须在omm用户下执行。
+- 必须指定-i或-e参数，-i会检查指定的单项，-e会检查对应场景配置中的多项。
+- 如果-i参数中不包含root类检查项或-e场景配置列表中没有root类检查项，则不需要交互输入root权限的用户及其密码。
+- 可使用-skip-root-items跳过检查项中包含的root类检查，以免需要输入root权限用户及密码。
+- 检查扩容新节点与现有节点之间的一致性，在现有节点执行gs_check命令指定-hosts参数进行检查，其中hosts文件中需要写入新节点ip。
+
+**操作步骤**
+
+方式1:
+
+1. 以操作系统用户omm登录数据库主节点。
+
+2. 执行如下命令对MogDB数据库状态进行检查。
+
+    ```bash
+    gs_check -i CheckClusterState
+    ```
+
+    其中，-i指定检查项，注意区分大小写。格式: -i CheckClusterState、-i CheckCPU或-i CheckClusterState，CheckCPU。
+
+    取值范围为所有支持的检查项名称，详细列表请参见“参考指南 > 工具参考 > 服务端工具 > [gs_check](1-gs_check)”中的“表 1 MogDB状态检查表”，用户可以根据需求自己编写新检查项。
+
+方式2:
+
+1. 以操作系统用户omm登录数据库主节点。
+
+2. 执行如下命令对MogDB数据库进行健康检查。
+
+    ```bash
+    gs_check -e inspect
+    ```
+
+    其中，-e指定场景名，注意区分大小写。格式: -e inspect或-e upgrade。
+
+    取值范围为所有支持的巡检场景名称，默认列表包括: inspect（例行巡检）、upgrade（升级前巡检）、install（安装）、binary_upgrade（就地升级前巡检）、health（健康检查巡检）、slow_node（节点）、longtime（耗时长巡检），用户可以根据需求自己编写场景。
+
+MogDB巡检的主要作用是在MogDB运行过程中，检查整个MogDB状态是否正常，或者重大操作前（升级、扩容），确保MogDB满足操作所需的环境条件和状态条件。详细的巡检项目和场景请参见《MogDB 工具参考》中"服务端工具 > [gs_checkos](2-gs_checkos) > MogDB状态检查表"。
+
+**示例**
+
+执行单项检查结果:
+
+```bash
+perfadm@lfgp000700749:/opt/huawei/perfadm/tool/script> gs_check -i CheckCPU
+Parsing the check items config file successfully
+Distribute the context file to remote hosts successfully
+Start to health check for the cluster. Total Items:1 Nodes:3
+
+Checking...               [=========================] 1/1
+Start to analysis the check result
+CheckCPU....................................OK
+The item run on 3 nodes.  success: 3
+
+Analysis the check result successfully
+Success. All check items run completed. Total:1  Success:1  Failed:0
+For more information please refer to /opt/mogdb/tools/script/gspylib/inspection/output/CheckReport_201902193704661604.tar.gz
+```
+
+本地执行结果:
+
+```bash
+perfadm@lfgp000700749:/opt/huawei/perfadm/tool/script> gs_check -i CheckCPU -L
+
+2017-12-29 17:09:29 [NAM] CheckCPU
+2017-12-29 17:09:29 [STD] 检查主机CPU占用率，如果idle 大于30%并且iowait 小于 30%.则检查项通过，否则检查项不通过
+2017-12-29 17:09:29 [RST] OK
+
+2017-12-29 17:09:29 [RAW]
+Linux 4.4.21-69-default (lfgp000700749)  12/29/17  _x86_64_
+
+17:09:24        CPU     %user     %nice   %system   %iowait    %steal     %idle
+17:09:25        all      0.25      0.00      0.25      0.00      0.00     99.50
+17:09:26        all      0.25      0.00      0.13      0.00      0.00     99.62
+17:09:27        all      0.25      0.00      0.25      0.13      0.00     99.37
+17:09:28        all      0.38      0.00      0.25      0.00      0.13     99.25
+17:09:29        all      1.00      0.00      0.88      0.00      0.00     98.12
+Average:        all      0.43      0.00      0.35      0.03      0.03     99.17
+```
+
+执行场景检查结果:
+
+```bash
+[perfadm@SIA1000131072 Check]$ gs_check -e inspect
+Parsing the check items config file successfully
+The below items require root privileges to execute:[CheckBlockdev CheckIOrequestqueue CheckIOConfigure CheckCheckMultiQueue CheckFirewall CheckSshdService CheckSshdConfig CheckCrondService CheckBootItems CheckFilehandle CheckNICModel CheckDropCache]
+Please enter root privileges user[root]:root
+Please enter password for user[root]:
+Please enter password for user[root] on the node[10.244.57.240]:
+Check root password connection successfully
+Distribute the context file to remote hosts successfully
+Start to health check for the cluster. Total Items:57 Nodes:2
+
+Checking...               [                         ] 21/57
+Checking...               [=========================] 57/57
+Start to analysis the check result
+CheckClusterState...........................OK
+The item run on 2 nodes.  success: 2
+
+CheckDBParams...............................OK
+The item run on 1 nodes.  success: 1
+
+CheckDebugSwitch............................OK
+The item run on 2 nodes.  success: 2
+
+CheckDirPermissions.........................OK
+The item run on 2 nodes.  success: 2
+
+CheckReadonlyMode...........................OK
+The item run on 1 nodes.  success: 1
+
+CheckEnvProfile.............................OK
+The item run on 2 nodes.  success: 2  (consistent)
+The success on all nodes value:
+GAUSSHOME        /usr1/mogdb/app
+LD_LIBRARY_PATH  /usr1/mogdb/app/lib
+PATH             /usr1/mogdb/app/bin
+
+
+CheckBlockdev...............................OK
+The item run on 2 nodes.  success: 2
+
+CheckCurConnCount...........................OK
+The item run on 1 nodes.  success: 1
+
+CheckCursorNum..............................OK
+The item run on 1 nodes.  success: 1
+
+CheckPgxcgroup..............................OK
+The item run on 1 nodes.  success: 1
+
+CheckDiskFormat.............................OK
+The item run on 2 nodes.  success: 2
+
+CheckSpaceUsage.............................OK
+The item run on 2 nodes.  success: 2
+
+CheckInodeUsage.............................OK
+The item run on 2 nodes.  success: 2
+
+CheckSwapMemory.............................OK
+The item run on 2 nodes.  success: 2
+
+CheckLogicalBlock...........................OK
+The item run on 2 nodes.  success: 2
+
+CheckIOrequestqueue.....................WARNING
+The item run on 2 nodes.  warning: 2
+The warning[host240,host157] value:
+On device (vdb) 'IO Request' RealValue '256' ExpectedValue '32768'
+On device (vda) 'IO Request' RealValue '256' ExpectedValue '32768'
+
+CheckMaxAsyIOrequests.......................OK
+The item run on 2 nodes.  success: 2
+
+CheckIOConfigure............................OK
+The item run on 2 nodes.  success: 2
+
+CheckMTU....................................OK
+The item run on 2 nodes.  success: 2  (consistent)
+The success on all nodes value:
+1500
+
+CheckPing...................................OK
+The item run on 2 nodes.  success: 2
+
+CheckRXTX...................................NG
+The item run on 2 nodes.  ng: 2
+The ng[host240,host157] value:
+NetWork[eth0]
+RX: 256
+TX: 256
+
+
+CheckNetWorkDrop............................OK
+The item run on 2 nodes.  success: 2
+
+CheckMultiQueue.............................OK
+The item run on 2 nodes.  success: 2
+
+CheckEncoding...............................OK
+The item run on 2 nodes.  success: 2  (consistent)
+The success on all nodes value:
+LANG=en_US.UTF-8
+
+CheckFirewall...............................OK
+The item run on 2 nodes.  success: 2
+
+CheckKernelVer..............................OK
+The item run on 2 nodes.  success: 2  (consistent)
+The success on all nodes value:
+3.10.0-957.el7.x86_64
+
+CheckMaxHandle..............................OK
+The item run on 2 nodes.  success: 2
+
+CheckNTPD...................................OK
+host240: NTPD service is running, 2020-06-02 17:00:28
+host157: NTPD service is running, 2020-06-02 17:00:06
+
+
+CheckOSVer..................................OK
+host240: The current OS is centos 7.6 64bit.
+host157: The current OS is centos 7.6 64bit.
+
+
+CheckSysParams..........................WARNING
+The item run on 2 nodes.  warning: 2
+The warning[host240,host157] value:
+Warning reason: variable 'net.ipv4.tcp_retries1' RealValue '3' ExpectedValue '5'.
+Warning reason: variable 'net.ipv4.tcp_syn_retries' RealValue '6' ExpectedValue '5'.
+
+CheckTHP....................................OK
+The item run on 2 nodes.  success: 2
+
+CheckTimeZone...............................OK
+The item run on 2 nodes.  success: 2  (consistent)
+The success on all nodes value:
++0800
+
+CheckCPU....................................OK
+The item run on 2 nodes.  success: 2
+
+CheckSshdService............................OK
+The item run on 2 nodes.  success: 2
+
+Warning reason: UseDNS parameter is not set; expected: no
+
+CheckCrondService...........................OK
+The item run on 2 nodes.  success: 2
+
+CheckStack..................................OK
+The item run on 2 nodes.  success: 2  (consistent)
+The success on all nodes value:
+8192
+
+CheckSysPortRange...........................OK
+The item run on 2 nodes.  success: 2
+
+CheckMemInfo................................OK
+The item run on 2 nodes.  success: 2  (consistent)
+The success on all nodes value:
+totalMem: 31.260929107666016G
+
+CheckHyperThread............................OK
+The item run on 2 nodes.  success: 2
+
+CheckTableSpace.............................OK
+The item run on 1 nodes.  success: 1
+
+CheckSysadminUser...........................OK
+The item run on 1 nodes.  success: 1
+
+
+CheckGUCConsistent..........................OK
+All DN instance guc value is consistent.
+
+CheckMaxProcMemory..........................OK
+The item run on 1 nodes.  success: 1
+
+CheckBootItems..............................OK
+The item run on 2 nodes.  success: 2
+
+CheckHashIndex..............................OK
+The item run on 1 nodes.  success: 1
+
+CheckPgxcRedistb............................OK
+The item run on 1 nodes.  success: 1
+
+CheckNodeGroupName..........................OK
+The item run on 1 nodes.  success: 1
+
+CheckTDDate.................................OK
+The item run on 1 nodes.  success: 1
+
+CheckDilateSysTab...........................OK
+The item run on 1 nodes.  success: 1
+
+CheckKeyProAdj..............................OK
+The item run on 2 nodes.  success: 2
+
+CheckProStartTime.......................WARNING
+host157:
+STARTED COMMAND
+Tue Jun  2 16:57:18 2020 /usr1/dmuser/dmserver/metricdb1/server/bin/mogdb --single_node -D /usr1/dmuser/dmb1/data -p 22204
+Mon Jun  1 16:15:15 2020 /usr1/mogdb/app/bin/mogdb -D /usr1/mogdb/data/dn1 -M standby
+
+
+CheckFilehandle.............................OK
+The item run on 2 nodes.  success: 2
+
+CheckRouting................................OK
+The item run on 2 nodes.  success: 2
+
+CheckNICModel...............................OK
+The item run on 2 nodes.  success: 2  (consistent)
+The success on all nodes value:
+version: 1.0.1
+model: Red Hat, Inc. Virtio network device
+
+
+CheckDropCache..........................WARNING
+The item run on 2 nodes.  warning: 2
+The warning[host240,host157] value:
+No DropCache process is running
+
+CheckMpprcFile..............................NG
+The item run on 2 nodes.  ng: 2
+The ng[host240,host157] value:
+There is no mpprc file
+
+Analysis the check result successfully
+Failed. All check items run completed. Total:57   Success:50   Warning:5   NG:2
+For more information please refer to /usr1/mogdb/tool/script/gspylib/inspection/output/CheckReport_inspect611.tar.gz
+```
+
+<br/>
+
+## 异常处理
+
+如果发现检查结果异常，可以根据以下内容进行修复。
+
+**表 1** 检查MogDB运行状态
+
+<table>
+    <tr>
+        <td>检查项    </td>
+        <td>  异常状态  </td>
+        <td> 处理方法   </td>
+     </tr>
+    <tr>
+        <td rowspan="2"> CheckClusterState（检查MogDB状态）   </td>
+        <td>  MogDB未启动或MogDB实例未启动  </td>
+        <td>  使用以下命令启动MogDB及实例。<br />gs_om -t start  </td>
+     </tr>
+    <tr>
+        <td>  MogDB状态异常或MogDB实例异常  </td>
+        <td>  检查各主机、实例状态，根据状态信息进行排查。<br />gs_check -i CheckClusterState </td>
+     </tr>
+    <tr>
+        <td>  CheckDBParams（检查数据库参数）  </td>
+        <td>  数据库参数错误  </td>
+        <td>   通过gs_guc工具修改数据库参数为指定值。 </td>
+     </tr>
+    <tr>
+        <td>  CheckDebugSwitch（检查调试日志）  </td>
+        <td>  日志级别不正确  </td>
+        <td>  使用gs_guc工具将log_min_messages改为指定内容。  </td>
+     </tr>
+    <tr>
+        <td>  CheckDirPermissions（检查目录权限）  </td>
+        <td>  路径权限错误  </td>
+        <td>   修改对应目录权限为指定数值（750/700）。<br />chmod 750 DIR </td>
+     </tr>
+    <tr>
+        <td>  CheckReadonlyMode（检查只读模式）  </td>
+        <td>  只读模式被打开  </td>
+        <td> 确认数据库节点所在磁盘使用率未超阈值（默认60%）且未在执行其他运维操作。<br />gs_check -i CheckDataDiskUsage ps ux<br />使用gs_guc工具关闭MogDB只读模式。<br />gs_guc reload -N all -I all -c 'default_transaction_read_only = off'     </td>
+     </tr>
+    <tr>
+        <td> CheckEnvProfile（检查环境变量）   </td>
+        <td>  环境变量不一致  </td>
+        <td> 重新执行前置更新环境变量信息。   </td>
+     </tr>
+    <tr>
+        <td>  CheckBlockdev（检查磁盘预读块）  </td>
+        <td>  磁盘预读块大小不为16384  </td>
+        <td> 使用gs_checkos设置预读块大小为16384KB，并写入自启动文件。<br />gs_checkos -i B3  </td>
+     </tr>
+    <tr>
+        <td> CheckCursorNum（检查游标数）   </td>
+        <td>   检查游标数失败 </td>
+        <td>  检查数据库能否正常连接，MogDB状态是否正常。  </td>
+     </tr>
+    <tr>
+        <td>  CheckPgxcgroup（检查重分布状态） </td>
+        <td>  有未完成重分布的pgxc_group表  </td>
+        <td>  继续完成扩容或缩容的数据重分布操作。<br />gs_expand、gs_shrink </td>
+     </tr>
+    <tr>
+        <td> CheckDiskFormat（检查磁盘配置）   </td>
+        <td>  各节点磁盘配置不一致  </td>
+        <td>  将各节点的磁盘规格改为相同。  </td>
+     </tr>
+    <tr>
+        <td> CheckSpaceUsage（检查磁盘空间使用率）   </td>
+        <td>  磁盘可用空间不足  </td>
+        <td> 清理或扩展对应目录所在的磁盘。   </td>
+     </tr>
+    <tr>
+        <td>   CheckInodeUsage（检查磁盘索引使用率） </td>
+        <td>  磁盘可用索引不足  </td>
+        <td>  清理或扩展对应目录所在的磁盘。  </td>
+     </tr>
+    <tr>
+        <td>  CheckSwapMemory（检查交换内存）  </td>
+        <td>  交换内存大于物理内存  </td>
+        <td>  将交换内存调小或关闭。  </td>
+     </tr>
+    <tr>
+        <td>  CheckLogicalBlock（检查磁盘逻辑块）  </td>
+        <td>  磁盘逻辑块大小不为512  </td>
+        <td>  使用gs_checkos修改磁盘逻辑块大小为512KB，并写入开机自启动文件。<br />gs_checkos -i B4  </td>
+     </tr>
+    <tr>
+        <td>  CheckIOrequestqueue（检查IO请求）  </td>
+        <td>  IO请求值不为32768  </td>
+        <td>  使用gs_checkos设置IO请求值为32768，并写入开机自启动文件。<br />gs_checkos -i B4  </td>
+     </tr>
+    <tr>
+        <td>  CheckCurConnCount（检查当前连接数）  </td>
+        <td>  当前连接数超过最大连接数的90%  </td>
+        <td>  断开未使用的数据库主节点连接。  </td>
+     </tr>
+    <tr>
+        <td>  CheckMaxAsyIOrequests（检查最大异步请求）  </td>
+        <td>  最大异步请求值小于104857600或当前节点数据库实例数乘以1048576  </td>
+        <td>  使用gs_checkos设置最大异步请求值为104857600和当前节点数据库实例数乘以1048576中的最大值。<br />gs_checkos -i B4  </td>
+     </tr>
+    <tr>
+        <td> CheckMTU（检查MTU值）   </td>
+        <td>  MTU值不一致  </td>
+        <td> 设置各节点的MTU一致为1500或8192。<br />ifconfig eth* MTU 1500  </td>
+     </tr>
+      <tr>
+        <td>  CheckIOConfigure（检查IO配置）  </td>
+        <td>  IO配置不是deadline  </td>
+        <td>   使用gs_checkos设置IO配置为deadline，并写入开机自启动文件。<br />gs_checkos -i B4 </td>
+     </tr>
+      <tr>
+        <td>   CheckRXTX（检查RXTX值） </td>
+        <td>  网卡RX/TX值不是4096  </td>
+        <td>  使用checkos设置MogDB使用的物理网卡RX/TX值为4096。<br />gs_checkos -i B5  </td>
+     </tr>
+      <tr>
+        <td>   CheckPing（检查网络通畅） </td>
+        <td>    存在MogDB IP无法ping通</td>
+        <td>  检查异常ip间网络设置和状态、防火墙状态。  </td>
+     </tr>
+      <tr>
+        <td> CheckNetWorkDrop（检查网络丢包率）   </td>
+        <td> 网络通信丢包率高于1%   </td>
+        <td>  检查对应IP间网络负载、状态。  </td>
+     </tr>
+      <tr>
+        <td> CheckMultiQueue（检查网卡多队列）   </td>
+        <td>   未开启网卡多队列并未将网卡中断绑定到不同CPU核心 </td>
+        <td>  开启网卡多队列并将网卡队列中断绑定到不同的CPU核心。  </td>
+     </tr>
+      <tr>
+        <td>  CheckEncoding（检查编码格式）  </td>
+        <td>  各节点编码格式不一致  </td>
+        <td>  在/etc/profile中写入一致的编码信息。<br />echo "export LANG=XXX" >> /etc/profile  </td>
+     </tr>
+      <tr>
+        <td>  CheckActQryCount（检查归档模式）  </td>
+        <td>  启用归档模式，归档目录不在主数据库节点目录下  </td>
+        <td>    关闭归档模式或者将归档目录设置在主数据库节点目录下。</td>
+     </tr>
+      <tr>
+        <td>  CheckFirewall（检查防火墙）  </td>
+        <td>  防火墙未关闭  </td>
+        <td>  关闭防火墙服务。<br />systemctl disable firewalld.service   </td>
+     </tr>
+      <tr>
+        <td>  CheckKernelVer（检查内核版本）  </td>
+        <td> 节点间的内核版本不一致  </td>
+        <td>    </td>
+     </tr>
+      <tr>
+        <td>  CheckMaxHandle（检查最大文件句柄数）  </td>
+        <td>  最大文件句柄数小于1000000  </td>
+        <td>  设置91-nofile.conf/90-nofile.conf最大文件句柄数软硬限制为1000000。<br />gs_checkos -i B2  </td>
+     </tr>
+      <tr>
+        <td>  CheckNTPD（检查时间同步服务）  </td>
+        <td>  NTPD服务未开启或时间误差超过一分钟  </td>
+        <td>   开启NTPD服务并设置时钟一致。 </td>
+     </tr>
+      <tr>
+        <td>   CheckSysParams（检查操作系统参数） </td>
+        <td>  操作系统参数设置不满足要求  </td>
+        <td>  使用gs_checkos进行参数设置或手动设置。<br />gs_checkos -i B1 vim /etc/sysctl.conf  </td>
+     </tr>
+      <tr>
+        <td>   CheckTHP（检查THP服务） </td>
+        <td>  THP服务未开启  </td>
+        <td>   使用gs_checkos设置THP服务。<br />gs_checkos -i B6</td>
+     </tr>
+      <tr>
+        <td>  CheckTimeZone（检查时区）  </td>
+        <td> 时区不一致   </td>
+        <td>  设置各节点为同一时区。<br />`cp /usr/share/zoneinfo/$地区/$时区 /etc/localtime`  </td>
+     </tr>
+      <tr>
+        <td>   CheckCPU（检查CPU） </td>
+        <td>   CPU占用过高或IO等待过高 </td>
+        <td>   进行CPU配置升级或磁盘性能升级。</td>
+     </tr>
+      <tr>
+        <td>  CheckSshdService（检查SSHD服务）  </td>
+        <td> 未开启SSHD服务   </td>
+        <td>  启动SSHD服务并写入开机自启动文件。<br />service sshd start echo "server sshd start" >> initFile  </td>
+     </tr>
+      <tr>
+        <td> CheckSshdConfig（检查SSHD配置）   </td>
+        <td>  SSHD服务配置错误  </td>
+        <td> 设置SSHD服务，<br />PasswordAuthentication=no; MaxStartups=1000; UseDNS=yes; ClientAliveInterval=10800/ClientAliveInterval=0<br />并重启服务: <br />server sshd start   </td>
+     </tr>
+      <tr>
+        <td>  CheckCrondService（检查Crond服务）  </td>
+        <td> Crond服务未启动   </td>
+        <td>  安装Crond服务并启用。</td>
+     </tr>
+      <tr>
+        <td>   CheckStack（检查堆栈大小） </td>
+        <td>   堆栈大小小于3072 </td>
+        <td>   使用gs_checkos设置为3072并重启堆栈值过小进程。<br /> gs_checkos -i B2 </td>
+     </tr>
+      <tr>
+        <td>   CheckSysPortRange（检查系统端口设置） </td>
+        <td>  系统ip端口不在预期范围内或MogDB端口在系统ip端口内  </td>
+        <td>  设置系统ip端口范围参数到26000-65535之中；设置MogDB端口在系统ip端口范围外。<br />vim /etc/sysctl.conf  </td>
+     </tr>
+      <tr>
+        <td>  CheckMemInfo（检查内存信息）  </td>
+        <td>  各节点内存大小不一致  </td>
+        <td>  使用相同规格的物理内存。</td>
+     </tr>
+      <tr>
+        <td>  CheckHyperThread（检查超线程）  </td>
+        <td>  未开启CPU超线程  </td>
+        <td>  开启CPU超线程。</td>
+     </tr>
+      <tr>
+        <td> CheckTableSpace（检查表空间）   </td>
+        <td>  表空间路径和MogDB路径存在嵌套或表空间路径相互存在嵌套  </td>
+        <td>  将表空间数据迁移到路径合法的表空间中。</td>
+     </tr>
+</table>
+
+## 状态查询
+
+**背景信息**
+
+MogDB支持查看整个MogDB的状态，通过查询结果确认MogDB或者单个主机的运行状态是否正常。
+
+**前提条件**
+
+MogDB已经启动。
+
+**操作步骤**
+
+1. 以操作系统用户omm登录数据库主节点。
+
+2. 使用如下命令查询MogDB状态：
+
+   ```bash
+   gs_om -t status --detail
+   ```
+
+   MogDB状态显示结果的参数说明请参见表1。
+
+   若要查询某主机上的实例状态，请在命令中增加“-h”项。示例如下：
+
+   ```bash
+   gs_om -t status -h plat2
+   ```
+
+   其中，plat2为待查询主机的名称。
+
+**参数说明**
+
+**表 1** 节点角色说明
+
+| 字段          | 字段含义                               | 字段值                                                       |
+| :------------ | :------------------------------------- | :----------------------------------------------------------- |
+| cluster_state | MogDB状态。显示整个MogDB是否运行正常。 | - Normal：表示MogDB可用，且数据有冗余备份。所有进程都在运行，主备关系正常。<br/>- Unavailable：表示MogDB不可用。<br/>- Degraded：表示MogDB可用，但存在故障的数据库节点、数据库主节点实例。 |
+| node          | 主机名称                               | 表示该实例所在的主机名称。多AZ时会显示AZ编号。               |
+| node_ip       | 主机IP                                 | 表示该实例所在的主机IP。                                     |
+| instance      | 实例ID                                 | 表示该实例的ID。                                             |
+| state         | 实例角色                               | - Normal：表示单主机实例。<br/>- Primary：表示实例为主实例。<br/>- Standby：表示实例为备实例。<br/>- Cascade Standby：表示实例为级联备实例。<br/>- Pending：表示该实例在仲裁阶段。<br/>- Unknown：表示实例状态未知。<br/>- Down：表示实例处于宕机状态。<br/>- Abnormal：表示节点处于异常状态。<br/>- Manually stopped：表示节点已经被手动停止。 |
+
+每个角色也存在不同的状态，例如启动，连接等，其各个状态说明如下：
+
+**表 2** 节点状态说明
+
+| 状态           | 字段含义                                                     |
+| :------------- | :----------------------------------------------------------- |
+| Normal         | 表示节点启动正常                                             |
+| Need repair    | 当前节点需要修复                                             |
+| Starting       | 节点正在启动中                                               |
+| Wait promoting | 节点正等待升级中，例如备机向主机发送升级请求后，正在等待主机回应时的状态 |
+| Promoting      | 备节点正在升级为主节点的状态                                 |
+| Demoting       | 节点正在降级中，如主机正在降为备机中                         |
+| Building       | 备机启动失败，需要重建                                       |
+| Catchup        | 备节点正在追赶主节点                                         |
+| Coredump       | 节点程序崩溃                                                 |
+| Unknown        | 节点状态未知                                                 |
+
+当节点出现Need repair状态时，可能需要对该节点进行重建使其恢复正常，通常情况下，节点重建原因说明如下：
+
+**表3** 节点重建原因说明
+
+| 状态                  | 字段含义                                              |
+| :-------------------- | :---------------------------------------------------- |
+| Normal                | 表示节点启动正常                                      |
+| WAL segment removed   | 主机日志WAL日志不存在，备机日志比主机日志新           |
+| Disconnect            | 备机不能连接主机                                      |
+| Version not matched   | 主备二进制版本不一致                                  |
+| Mode not matched      | 主备角色不匹配，例如两个备机互联                      |
+| System id not matched | 主备数据库系统id不一致，主备双机要求System ID必须一致 |
+| Timeline not matched  | 日志时间线不一致                                      |
+| Unknown               | 其他原因                                              |
+
+**示例**
+
+查看MogDB详细状态信息，含实例状态信息。
+
+```bash
+gs_om -t status --detail
+[   Cluster State   ]
+
+cluster_state   : Normal
+redistributing  : No
+current_az      : AZ_ALL
+
+[  Datanode State   ]
+
+    node             node_ip         port      instance                                   state
+-----------------------------------------------------------------------------------------------------
+1  pekpopgsci00235  10.244.62.204    5432      6001 /opt/mogdb/cluster/data/dn1   P Primary Normal
+2  pekpopgsci00238  10.244.61.81     5432      6002 /opt/mogdb/cluster/data/dn1   S Standby Normal
+```
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/4-checking-database-performance.md b/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/4-checking-database-performance.md
new file mode 100644
index 0000000000000000000000000000000000000000..dce87b26452ddff7617a23a97d4157eb2257827d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/4-checking-database-performance.md
@@ -0,0 +1,85 @@
+---
+title: 日常运维
+summary: 日常运维
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# 检查数据库性能
+
+## 检查办法
+
+通过MogDB提供的性能统计工具gs_checkperf可以对硬件性能进行检查。
+
+**前提条件**
+
+- MogDB运行状态正常。
+- 运行在数据库之上的业务运行正常。
+
+**操作步骤**
+
+1. 以操作系统用户omm登录数据库主节点。
+
+2. 执行如下命令对MogDB数据库进行性能检查。
+
+    ```bash
+    gs_checkperf
+    ```
+
+具体的性能统计项目请参见“参考指南 > 工具参考 > 服务端工具 > [gs_checkperf](3-gs_checkperf)”中的“表1 性能检查项”。
+
+**示例**
+
+以简要格式在屏幕上显示性能统计结果。
+
+```bash
+gs_checkperf -i pmk -U omm
+Cluster statistics information:
+    Host CPU busy time ratio                     :    1.43       %
+    MPPDB CPU time % in busy time                :    1.88       %
+    Shared Buffer Hit ratio                      :    99.96      %
+    In-memory sort ratio                         :    100.00     %
+    Physical Reads                               :    4
+    Physical Writes                              :    25
+    DB size                                      :    70         MB
+    Total Physical writes                        :    25
+    Active SQL count                             :    2
+    Session count                                :    3
+```
+
+<br/>
+
+## 异常处理
+
+使用gs_checkperf工具检查MogDB性能状态后，如果发现检查结果发现异常，可以根据以下内容进行修复。
+
+**表 1** 检查MogDB级别性能状态
+
+| 异常状态          | 处理方法           |
+| ----------------- | -------------------------------------------------- |
+| 主机CPU占有率高   | 1、更换和增加高性能的CPU。<br />2、使用top命令查看系统哪些进程的CPU占有率高，然后使用kill命令关闭没有使用的进程。<br />*top*                                                              |
+| MogDB CPU占有率高 | 1、更换和增加高性能的CPU。<br />2、使用top命令查看数据库哪些进程的CPU占有率高，然后使用kill命令关闭没有使用的进程。<br />*top*<br />3、使用gs_expand工具扩容，增加新的主机均衡CPU占有率。 |
+| 共享内存命中率低  | 1、扩大内存。<br />2、使用如下命令查看操作系统配置文件/etc/sysctl.conf，调大共享内存kernel.shmmax值。<br />*vim /etc/sysctl.conf*                                                         |
+| 内存中排序比率低  | 扩大内存。                                                                                                                                                                                |
+| I/O、磁盘使用率高 | 1、更换高性能的磁盘。<br />2、调整数据布局，尽量将I/O请求较合理的分配到所有物理磁盘中。<br />3、全库进行VACUUM FULL操作。<br />*vacuum full;*<br />4、进行磁盘整理。<br />5、降低并发数。 |
+| 事务统计          | 查询pg_stat_activity系统表，将不必要的连接断开。（登录数据库后查询: postgres=# \d+ pg_stat_activity;）                                                                                    |
+
+**表 2** 检查节点级别性能状态
+
+| 异常状态           | 处理方法                                                                                                                               |
+| ------------------ | --------------------------------------- |
+| CPU占有率高        | 1、更换和增加高性能的CPU。<br />2、使用top命令查看系统哪些进程的CPU占有率高，然后使用kill命令关闭没有使用的进程。<br />*top*           |
+| 内存使用率过高情况 | 扩大或清理内存。                                                                                                                       |
+| I/O使用率过高情况  | 1、更换高性能的磁盘。<br />2、进行磁盘清理。<br />3、尽可能用内存的读写代替直接磁盘I/O，使频繁访问的文件或数据放入内存中进行操作处理。 |
+
+**表 3** 会话/进程级别性能状态
+
+| 异常状态                     | 处理方法        |
+| ---------------------------- | --------------------------------- |
+| CPU、内存、I/O使用率过高情况 | 查看哪个进程占用CPU/内存高或I/O使用率高，若是无用的进程，则kill掉，否则排查具体原因。例如SQL执行占用内存大，查看是否SQL语句需要优化。 |
+
+**表 4** SSD性能状态
+
+| 异常状态        | 处理方法                                    |
+| --------------- | -------------------------------------------- |
+| SSD读写性能故障 | 使用以下命令查看SSD是否有故障，排查具体故障原因。<br />*gs_checkperf -i SSD -U omm* |
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/5-checking-and-deleting-logs.md b/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/5-checking-and-deleting-logs.md
new file mode 100644
index 0000000000000000000000000000000000000000..d1ebaf92bae1a1b88e8f5bca5081f8d895ff6776
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/5-checking-and-deleting-logs.md
@@ -0,0 +1,164 @@
+---
+title: 日常运维
+summary: 日常运维
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# 检查和清理日志
+
+日志是检查系统运行及故障定位的关键手段。建议按月度例行查看操作系统日志及数据库的运行日志。同时，随着时间的推移，日志的增加会占用较多的磁盘空间。建议按月度清理数据库的运行日志。
+
+<br/>
+
+## 检查操作系统日志
+
+建议按月检查操作系统日志，排除操作系统运行异常隐患。
+
+执行如下命令查看操作系统日志文件。
+
+```
+vim /var/log/messages
+```
+
+关注其中近一个月出现的kernel、error、fatal等字样，根据系统报警信息进行处理。
+
+<br/>
+
+## 检查MogDB运行日志
+
+数据库运行时，某些操作在执行过程中可能会出现错误，数据库依然能够运行。但是此时数据库中的数据可能已经发生不一致的情况。建议按月检查MogDB运行日志，及时发现隐患。
+
+**前提条件**
+
+- 收集日志的主机网络通畅且未宕机，数据库安装用户互信正常。
+- 日志收集工具依赖操作系统工具如gstack，如果未安装该工具，则提示错误后，跳过该收集项。
+
+**操作步骤**
+
+1. 以操作系统用户omm登录数据库主节点。
+
+2. 执行如下命令收集数据库日志。
+
+    ```bash
+    gs_collector --begin-time="20160616 01:01" --end-time="20160616 23:59"
+    ```
+
+    20160616 01:01为日志的开始时间，20160616 23:59为日志的结束时间。
+
+3. 根据2的界面输出提示，进入相应的日志收集目录，解压收集的日志，并检查数据库日志。
+
+    以下以日志收集路径"/opt/mogdb/tmp/gaussdba_mppdb/collector_20160726_105158.tar.gz"为例进行操作。
+
+    ```
+    tar -xvzf /opt/mogdb/tmp/gaussdba_mppdb/collector_20160726_105158.tar.gz
+    cd /opt/mogdb/tmp/gaussdba_mppdb/collector_20160726_105158
+    ```
+
+**示例**
+
+- 以-begin-time与-end-time为参数执行gs_collector命令。
+
+    ```bash
+    gs_collector --begin-time="20160616 01:01" --end-time="20160616 23:59"
+    ```
+
+    当显示类似如下信息表示日志已经归档。
+
+    ```
+    Successfully collected  files
+    All results are stored in /tmp/gaussdba_mppdb/collector_20160616_175615.tar.gz.
+    ```
+
+- 以-begin-time，-end-time与-h为参数执行gs_collector命令。
+
+    ```bash
+    gs_collector --begin-time="20160616 01:01" --end-time="20160616 23:59" -h plat2
+    ```
+
+    当显示类似如下信息表示日志已经归档。
+
+    ```
+    Successfully collected  files
+    All results are stored in /tmp/gaussdba_mppdb/collector_20160616_190225.tar.gz.
+    ```
+
+- 以-begin-time，-end-time与-f为参数执行gs_collector命令。
+
+    ```bash
+    gs_collector --begin-time="20160616 01:01" --end-time="20160616 23:59" -f /opt/software/mogdb/output
+    ```
+
+    当显示类似如下信息表示日志已经归档。
+
+    ```
+    Successfully collected  files
+    All results are stored in /opt/software/mogdb/output/collector_20160616_190511.tar.gz.
+    ```
+
+- 以-begin-time，-end-time与-keyword为参数执行gs_collector命令。
+
+    ```bash
+    gs_collector --begin-time="20160616 01:01" --end-time="20160616 23:59" --keyword="os"
+    ```
+
+    当显示类似如下信息表示日志已经归档。
+
+    ```
+    Successfully collected files.
+    All results are stored in /tmp/gaussdba_mppdb/collector_20160616_190836.tar.gz.
+    ```
+
+- 以-begin-time，-end-time与-o为参数执行gs_collector命令。
+
+    ```bash
+    gs_collector --begin-time="20160616 01:01" --end-time="20160616 23:59" -o /opt/software/mogdb/output
+    ```
+
+    当显示类似如下信息表示日志已经归档。
+
+    ```
+    Successfully collected files.
+    All results are stored in /opt/software/mogdb/output/collector_20160726_113711.tar.gz.
+    ```
+
+- 以-begin-time，-end-time与-l为参数（文件名必须以.log为后缀）执行gs_collector命令。
+
+    ```bash
+    gs_collector --begin-time="20160616 01:01" --end-time="20160616 23:59" -l /opt/software/mogdb/logfile.log
+    ```
+
+    当显示类似如下信息表示日志已经归档。
+
+    ```
+    Successfully collected files.
+    All results are stored in /opt/software/mogdb/output/collector_20160726_113711.tar.gz.
+  ```
+
+<br/>
+
+## 清理运行日志
+
+数据库运行过程中会产生大量运行日志，占用大量的磁盘空间，建议清理过期日志文件，只保留一个月的日志。
+
+**操作步骤**
+
+1. 以操作系统用户omm登录数据库主节点。
+
+2. 清理日志。
+
+    a. 将超过1个月的日志备份到其他磁盘。
+
+    b. 进入日志存放目录。
+
+    ```
+    cd $GAUSSLOG
+    ```
+
+    c. 进入相应的子目录，使用如下方式删除1个月之前产生的日志。
+
+    ```
+    rm 日志名称
+    ```
+
+    日志文件的命名格式为"mogdb-年-月-日_HHMMSS"。
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/6-checking-time-consistency.md b/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/6-checking-time-consistency.md
new file mode 100644
index 0000000000000000000000000000000000000000..5af18cfa5b93352e3f06a2e669b64a20ec06dcda
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/6-checking-time-consistency.md
@@ -0,0 +1,52 @@
+---
+title: 日常运维
+summary: 日常运维
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# 检查时间一致性
+
+数据库事务一致性通过逻辑时钟保证，与操作系统时间无关，但是系统时间不一致会导致诸多潜在问题，主要是后台运维和监控功能异常，因此在月度检查时建议检查各个节点的时间一致性。
+
+**操作步骤**
+
+1. 以操作系统用户omm登录数据库主节点。
+
+2. 创建记录MogDB各节点的配置文件（_mpphosts文件目录_用户可随意指定，建议放在/tmp下）。
+
+    ```
+    vim /tmp/mpphosts
+    ```
+
+    增加各节点的主机名称。
+
+    ```
+    plat1
+    plat2
+    plat3
+    ```
+
+3. 保存配置文件。
+
+    ```
+    :wq!
+    ```
+
+4. 执行如下命令，输出各节点上的时间到"/tmp/sys_ctl-os1.log"文件中。
+
+    ```
+    for ihost in `cat /tmp/mpphosts`; do ssh -n -q $ihost "hostname;date"; done > /tmp/  sys_ctl-os1.log
+    ```
+
+5. 根据输出确认各个节点的时间一致性，节点之间时间差异不能超过30秒。
+
+    ```
+    cat /tmp/sys_ctl-os1.log
+    plat1
+    Thu Feb  9 16:46:38 CST 2017
+    plat2
+    Thu Feb  9 16:46:49 CST 2017
+    plat3
+    Thu Feb  9 16:46:14 CST 2017
+    ```
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/7-checking-the-number-of-application-connections.md b/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/7-checking-the-number-of-application-connections.md
new file mode 100644
index 0000000000000000000000000000000000000000..68b6fd9d692054f398f3938dec7537027e91e56f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/7-checking-the-number-of-application-connections.md
@@ -0,0 +1,133 @@
+---
+title: 日常运维
+summary: 日常运维
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# 检查应用连接数
+
+如果应用程序与数据库的连接数超过最大值，则新的连接无法建立。建议每天检查连接数，及时释放空闲的连接或者增加最大连接数。
+
+**操作步骤**
+
+1. 以操作系统用户omm登录数据库主节点。
+
+2. 使用如下命令连接数据库。
+
+    ```bash
+    gsql -d mogdb -p 8000
+    ```
+
+    mogdb为需要连接的数据库名称，8000为数据库主节点的端口号。
+
+    连接成功后，系统显示类似如下信息:
+
+    ```bash
+    gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+    Non-SSL connection (SSL connection is recommended when requiring high-security)
+    Type "help" for help.
+
+    mogdb=#
+    ```
+
+3. 执行如下SQL语句查看连接数。
+
+    ```sql
+    mogdb=# SELECT count(*) FROM (SELECT pg_stat_get_backend_idset() AS backendid) AS s;
+    ```
+
+    显示类似如下的信息，其中2表示当前有两个应用连接到数据库。
+
+    ```sql
+    count
+    -------
+         2
+    (1 row)
+    ```
+
+4. 查看现有最大连接数。
+
+    ```sql
+    mogdb=# SHOW max_connections;
+    ```
+
+    显示信息如下，其中200为现在的最大连接数。
+
+    ```sql
+     max_connections
+    -----------------
+     200
+    (1 row)
+    ```
+
+<br/>
+
+## 异常处理
+
+如果显示的连接数接近数据库的最大连接数max_connections，则需要考虑清理现有连接数或者增加新的连接数。
+
+1. 执行如下SQL语句，查看state字段等于idle，且state_change字段长时间没有更新过的连接信息。
+
+    ```sql
+    mogdb=# SELECT * FROM pg_stat_activity where state='idle' order by state_change;
+    ```
+
+    显示类似如下的信息:
+
+    ```sql
+     datid | datname  |       pid       | usesysid | usename  | application_name |  client_addr
+     | client_hostname | client_port |         backend_start         | xact_start |          quer
+    y_start          |         state_change          | waiting | enqueue | state | resource_pool
+    |                    query
+    -------+----------+-----------------+----------+----------+------------------+---------------
+    -+-----------------+-------------+-------------------------------+------------+--------------
+    -----------------+-------------------------------+---------+---------+-------+---------------
+    +----------------------------------------------
+     13626 | mogdb | 140390162233104 |       10 | gaussdba |                  |
+     |                 |          -1 | 2016-07-15 14:08:59.474118+08 |            | 2016-07-15 14
+    :09:04.496769+08 | 2016-07-15 14:09:04.496975+08 | f       |         | idle  | default_pool
+    | select count(group_name) from pgxc_group;
+     13626 | mogdb | 140390132872976 |       10 | gaussdba | cn_5002          | 10.180.123.163
+     |                 |       48614 | 2016-07-15 14:11:16.014871+08 |            | 2016-07-15 14
+    :21:17.346045+08 | 2016-07-15 14:21:17.346095+08 | f       |         | idle  | default_pool
+    | SET SESSION AUTHORIZATION DEFAULT;RESET ALL;
+    (2 rows)
+    ```
+
+2. 释放空闲的连接数。
+
+    查看每个连接，并与此连接的使用者确认是否可以断开连接，或执行如下SQL语句释放连接。其中，pid为上一步查询中空闲连接所对应的pid字段值。
+
+    ```sql
+    mogdb=# SELECT pg_terminate_backend(140390132872976);
+    ```
+
+    显示类似如下的信息:
+
+    ```sql
+    mogdb=# SELECT pg_terminate_backend(140390132872976);
+     pg_terminate_backend
+    ----------------------
+     t
+    (1 row)
+    ```
+
+    如果没有可释放的连接，请执行下一步。
+
+3. 增加最大连接数。
+
+    ```bash
+    gs_guc set -D /mogdb/data/dbnode -c "max_connections= 800"
+    ```
+
+    其中800为新修改的连接数。
+
+4. 重启数据库服务使新的设置生效。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+    > 重启MogDB操作会导致用户执行操作中断，请在操作之前规划好合适的执行窗口。
+
+    ```bash
+    gs_om -t stop && gs_om -t start
+    ```
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/8-routinely-maintaining-tables.md b/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/8-routinely-maintaining-tables.md
new file mode 100644
index 0000000000000000000000000000000000000000..79fbb0368fad381b46179becb9dbec24f9081a7e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/8-routinely-maintaining-tables.md
@@ -0,0 +1,111 @@
+---
+title: 日常运维
+summary: 日常运维
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# 例行维护表
+
+为了保证数据库的有效运行，数据库必须在插入/删除操作后，基于客户场景，定期做VACUUM FULL和ANALYZE，更新统计信息，以便获得更优的性能。
+
+**相关概念**
+
+使用VACUUM、VACUUM FULL和ANALYZE命令定期对每个表进行维护，主要有以下原因:
+
+- VACUUM FULL可回收已更新或已删除的数据所占据的磁盘空间，同时将小数据文件合并。
+- VACUUM对每个表维护了一个可视化映射来跟踪包含对别的活动事务可见的数组的页。一个普通的索引扫描首先通过可视化映射来获取对应的数组，来检查是否对当前事务可见。若无法获取，再通过堆数组抓取的方式来检查。因此更新表的可视化映射，可加速唯一索引扫描。
+- VACUUM可避免执行的事务数超过数据库阈值时，事务ID重叠造成的原有数据丢失。
+- ANALYZE可收集与数据库中表内容相关的统计信息。统计结果存储在系统表PG_STATISTIC中。查询优化器会使用这些统计数据，生成最有效的执行计划。
+
+**操作步骤**
+
+1. 使用VACUUM或VACUUM FULL命令，进行磁盘空间回收。
+
+   - **VACUUM**:
+
+     对表执行VACUUM操作
+
+     ```sql
+     postgres=# VACUUM customer;
+     ```
+
+     ```sql
+     VACUUM
+     ```
+
+     可以与数据库操作命令并行运行。（执行期间，可正常使用的语句: SELECT、INSERT、UPDATE和DELETE。不可正常使用的语句: ALTER TABLE）。
+
+     对表分区执行VACUUM操作
+
+     ```sql
+     postgres=# VACUUM customer_par PARTITION ( P1 );
+     ```
+
+     ```sql
+     VACUUM
+     ```
+
+   - **VACUUM FULL**:
+
+      ```sql
+      postgres=# VACUUM FULL customer;
+      ```
+
+      ```sql
+      VACUUM
+      ```
+
+      需要向正在执行的表增加排他锁，且需要停止其他所有数据库操作。
+
+2. 使用ANALYZE语句更新统计信息。
+
+    ```sql
+    postgres=# ANALYZE customer;
+    ```
+
+    ```sql
+    ANALYZE
+    ```
+
+    使用ANALYZE VERBOSE语句更新统计信息，并输出表的相关信息。
+
+    ```sql
+    postgres=# ANALYZE VERBOSE customer;
+    ```
+
+    ```sql
+    ANALYZE
+    ```
+
+    也可以同时执行VACUUM ANALYZE命令进行查询优化。
+
+    ```sql
+    postgres=# VACUUM ANALYZE customer;
+    ```
+
+    ```sql
+    VACUUM
+    ```
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:** VACUUM和ANALYZE会导致I/O流量的大幅增加，这可能会影响其他活动会话的性能。因此，建议通过"vacuum_cost_delay"参数设置《开发者指南》中"GUC参数说明 > 资源消耗 > 基于开销的清理延迟"。
+
+3. 删除表。
+
+    ```sql
+    postgres=# DROP TABLE customer;
+    postgres=# DROP TABLE customer_par;
+    postgres=# DROP TABLE part;
+    ```
+
+    当结果显示为如下信息，则表示删除成功。
+
+    ```sql
+    DROP TABLE
+    ```
+
+**维护建议**
+
+- 定期对部分大表做VACUUM FULL，在性能下降后为全库做VACUUM FULL，目前暂定每月做一次VACUUM FULL。
+- 定期对系统表做VACUUM FULL，主要是PG_ATTRIBUTE。
+- 启用系统自动清理线程（AUTOVACUUM）自动执行VACUUM和ANALYZE，回收被标识为删除状态的记录空间，并更新表的统计数据。
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md b/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md
new file mode 100644
index 0000000000000000000000000000000000000000..35da4c0f81d9d4bd2367a7255ffdaf70c7202776
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md
@@ -0,0 +1,72 @@
+---
+title: 日常运维
+summary: 日常运维
+author: Zhang Cuiping
+date: 2021-03-04
+---
+
+# 例行重建索引
+
+## 背景信息
+
+数据库经过多次删除操作后，索引页面上的索引键将被删除，造成索引膨胀。例行重建索引，可有效的提高查询效率。
+
+数据库支持的索引类型为B-tree索引，例行重建索引可有效的提高查询效率。
+
+- 如果数据发生大量删除后，索引页面上的索引键将被删除，导致索引页面数量的减少，造成索引膨胀。重建索引可回收浪费的空间。
+- 新建的索引中逻辑结构相邻的页面，通常在物理结构中也是相邻的，所以一个新建的索引比更新了多次的索引访问速度要快。
+
+<br/>
+
+## 重建索引
+
+重建索引有以下两种方式:
+
+- 先运行DROP INDEX语句删除索引，再运行CREATE INDEX语句创建索引。
+
+  在删除索引过程中，会在父表上增加一个短暂的排他锁，阻止相关读写操作。在创建索引过程中，会锁住写操作但是不会锁住读操作，此时读操作只能使用顺序扫描。
+
+- 使用REINDEX语句重建索引。
+
+  - 使用REINDEX TABLE语句重建索引，会在重建过程中增加排他锁，阻止相关读写操作。
+  - 使用REINDEX INTERNAL TABLE语句重建desc表（包括列存表的cudesc表）的索引，会在重建过程中增加排他锁，阻止相关读写操作。
+
+<br/>
+
+## 操作步骤
+
+假定在导入表"areaS"上的"area_id"字段上存在普通索引"areaS_idx"。重建索引有以下两种方式:
+
+- 先删除索引（DROP INDEX），再创建索引（CREATE INDEX）
+
+  1. 删除索引。
+
+     ```sql
+     mogdb=# DROP INDEX areaS_idx;
+     DROP INDEX
+     ```
+
+  2. 创建索引。
+
+     ```sql
+     mogdb=# CREATE INDEX areaS_idx ON areaS (area_id);
+     CREATE INDEX
+     ```
+
+- 使用REINDEX重建索引。
+
+  - 使用REINDEX TABLE语句重建索引。
+
+      ```sql
+      mogdb=# REINDEX TABLE areaS;
+      REINDEX
+      ```
+
+  - 使用REINDEX INTERNAL TABLE重建desc表（包括列存表的cudesc表）的索引。
+
+      ```sql
+      mogdb=# REINDEX INTERNAL TABLE areaS;
+      REINDEX
+      ```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:** 在重建索引前，用户可以通过临时增大maintenance_work_mem和psort_work_mem的取值来加快索引的重建。
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/slow-sql-diagnosis.md b/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/slow-sql-diagnosis.md
new file mode 100644
index 0000000000000000000000000000000000000000..0c81719ecca5282c23e8a6d295bd0cee810ba7a2
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/slow-sql-diagnosis.md
@@ -0,0 +1,29 @@
+---
+title: 慢SQL诊断
+summary: 慢SQL诊断
+author: Guo Huan
+date: 2022-04-13
+---
+
+# 慢SQL诊断
+
+## 背景信息
+
+在SQL语句执行性能不符合预期时，可以查看SQL语句执行信息，便于事后分析SQL语句执行时的行为，从而诊断SQL语句执行出现的相关问题。
+
+## 前提条件
+
+- 数据库实例运行正常。
+
+- 查询SQL语句信息，需要正确设置GUC参数track_stmt_stat_level。
+
+- 只能用系统管理员和监控管理员权限进行操作。
+
+  ```
+  执行命令查看数据库实例中SQL语句执行信息
+  gsql> select * from dbe_perf.get_global_full_sql_by_timestamp(start_timestamp, end_timestamp); 
+  执行命令查看数据库实例中慢SQL语句执行信息
+  gsql> select * from dbe_perf.get_global_slow_sql_by_timestamp(start_timestamp, end_timestamp);
+  查看当前节点SQL语句执行信息
+  gsql> select * from statement_history;
+  ```
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/using-the-gsql-client-for-connection.md b/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/using-the-gsql-client-for-connection.md
new file mode 100644
index 0000000000000000000000000000000000000000..d64a7beaf6cdfce8107d451db8f7c871b2bcfc14
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/routine-maintenance/using-the-gsql-client-for-connection.md
@@ -0,0 +1,212 @@
+---
+title: gsql客户端连接
+summary: gsql客户端连接
+author: Guo Huan
+date: 2021-12-2
+---
+
+# gsql客户端连接
+
+## 确认连接信息
+
+客户端工具通过数据库主节点连接数据库。因此连接前，需获取数据库主节点所在服务器的IP地址及数据库主节点的端口号信息。
+
+1. 以操作系统用户omm登录数据库主节点。
+
+2. 使用"gs_om -t status --detail"命令查询MogDB各实例情况。
+
+   ```bash
+   gs_om -t status --detail
+
+   [  Datanode State   ]
+
+   node                 node_ip         instance                state
+   ---------------------------------------------------------------------------------
+   1  mogdb-kernel-0005 172.16.0.176    6001 /mogdb/data/db1 P Primary Normal
+   ```
+
+   如上部署了数据库主节点实例的服务器IP地址为172.16.0.176。数据库主节点数据路径为"/mogdb/data/db1"。
+
+3. 确认数据库主节点的端口号。
+
+   在步骤2查到的数据库主节点数据路径下的postgresql.conf文件中查看端口号信息。示例如下:
+
+   ```bash
+   cat /mogdb/data/db1/postgresql.conf | grep port
+
+   port = 26000    # (change requires restart)
+   #comm_sctp_port = 1024   # Assigned by installation (change requires restart)
+   #comm_control_port = 10001  # Assigned by installation (change requires restart)
+         # supported by the operating system:
+         # e.g. 'localhost=10.145.130.2 localport=12211 remotehost=10.145.130.3 remoteport=12212, localhost=10.145.133.2 localport=12213 remotehost=10.145.133.3 remoteport=12214'
+         # e.g. 'localhost=10.145.130.2 localport=12311 remotehost=10.145.130.4 remoteport=12312, localhost=10.145.133.2 localport=12313 remotehost=10.145.133.4 remoteport=12314'
+         #   %r = remote host and port
+   alarm_report_interval = 10
+   support_extended_features=true
+   ```
+
+   第一行中的26000为数据库主节点的端口号。
+
+<br/>
+
+## 安装gsql客户端
+
+在客户端机器上，上传客户端工具包并配置gsql的执行环境变量。
+
+1. 以任意用户登录客户端机器。
+
+2. 创建"/opt/mogdb/tools"目录。
+
+   ```bash
+   mkdir /opt/mogdb/tools
+   ```
+
+3. 获取软件安装包中的"MogDB-x.x.x-openEuler-64bit-tools.tar.gz"上传到"/opt/mogdb/tools"路径下。
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+   >
+   > - 软件包相对位置为安装时所放位置，根据实际情况填写。
+   > - 不同的操作系统，工具包文件名称会有差异。请根据实际的操作系统类型选择对应的工具包。
+
+4. 解压文件。
+
+   ```bash
+   cd /opt/mogdb/tools
+   tar -zxvf MogDB-x.x.x-openEuler-64bit-tools.tar.gz
+   ```
+
+5. 设置环境变量。
+
+   打开"~/.bashrc"文件。
+
+   ```bash
+   vi ~/.bashrc
+   ```
+
+   在其中输入如下内容后，使用":wq!"命令保存并退出。
+
+   ```bash
+   export PATH=/opt/mogdb/tools/bin:$PATH
+   export LD_LIBRARY_PATH=/opt/mogdb/tools/lib:$LD_LIBRARY_PATH
+   ```
+
+6. 使环境变量配置生效。
+
+   ```bash
+   source ~/.bashrc
+   ```
+
+<br/>
+
+## 使用gsql连接数据库
+
+<br/>
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 缺省情况下，客户端连接数据库后处于空闲状态时会根据参数session_timeout的默认值自动断开连接。如果要关闭超时设置，设置参数session_timeout为0即可。
+
+<br/>
+
+### 本地连接数据库
+
+1. 以操作系统用户omm登录数据库服务器。
+
+2. 连接数据库。
+
+   数据库安装完成后，默认生成名称为postgres的数据库。第一次连接数据库时可以连接到此数据库。
+
+   执行如下命令连接数据库。
+
+   ```bash
+   gsql -d postgres -p 26000
+   ```
+
+   其中postgres为需要连接的数据库名称，26000为数据库主节点的端口号。请根据实际情况替换。
+
+   连接成功后，系统显示类似如下信息:
+
+   ```sql
+   gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+   Non-SSL connection (SSL connection is recommended when requiring high-security)
+   Type "help" for help.
+
+   postgres=#
+   ```
+
+   omm用户是管理员用户，因此系统显示"postgres=#"。若使用普通用户身份登录和连接数据库，系统显示"postgres=>"。
+
+   "Non-SSL connection"表示未使用SSL方式连接数据库。如果需要高安全性时，请使用SSL连接。
+
+3. 退出数据库。
+
+   ```sql
+   postgres=# \q
+   ```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 使用omm用户在本地连接数据库，无需输入密码，这是由于在pg_hba.conf文件中默认设置了本机允许trust方式连接。
+> - 更多关于客户端认证方式的信息，请参见[客户端接入认证](1-client-access-authentication)章节。
+
+<br/>
+
+## 远程连接数据库
+
+<br/>
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 由于安全性限制，数据库初始用户omm无法进行远程连接。
+
+<br/>
+
+### 通过gs_guc配置白名单（更新pg_hba.conf文件）
+
+1. 以操作系统用户omm登录数据库主节点。
+
+2. 配置客户端认证方式，允许客户端以"jack"用户连接到本机，远程连接禁止使用"omm"用户（即数据库初始化用户）。
+
+   例如，下面示例中配置允许IP地址为172.16.0.245的客户端访问本机。
+
+   ```bash
+   gs_guc set -N all -I all -h "host all jack 172.16.0.245/24 sha256"
+   ```
+
+   **注意：**
+
+   - 使用"jack"用户前，需先本地连接数据库，并在数据库中使用如下语句建立"jack"用户:
+
+     ```sql
+     postgres=# CREATE USER jack PASSWORD 'Test@123';
+     ```
+
+   - -N all表示MogDB的所有主机。
+
+   - -I all表示主机的所有实例。
+
+   - -h表示指定需要在"pg_hba.conf"增加的语句。
+
+   - all表示允许客户端连接到任意的数据库。
+
+   - jack表示连接数据库的用户。
+
+   - 172.16.0.245/24表示只允许IP地址为172.16.0.245的主机连接。此处的IP地址不能为MogDB内的IP，在使用过程中，请根据用户的网络进行配置修改。24表示子网掩码为1的位数，即255.255.255.0。
+
+   - sha256表示连接时jack用户的密码使用sha256算法加密。
+
+   这条命令在数据库主节点实例对应的"pg_hba.conf"文件中添加了一条规则，用于对连接数据库主节点的客户端进行鉴定。
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+   >
+   > + 更多关于客户端认证方式的信息，请参见[客户端接入认证](1-client-access-authentication)章节。
+
+3. 连接数据库。
+
+   数据库安装完成后，默认生成名称为postgres的数据库。第一次连接数据库时可以连接到此数据库。
+
+   ```bash
+   gsql -d postgres -h 172.16.0.176 -U jack -p 26000 -W Test@123
+   ```
+
+   postgres为需要连接的数据库名称，172.16.0.176为数据库主节点所在的服务器IP地址，jack为连接数据库的用户，26000为数据库主节点的端口号，Test@123为连接数据库用户jack的密码。
diff --git a/product/zh/docs-mogdb/v3.0/administrator-guide/upgrade-guide.md b/product/zh/docs-mogdb/v3.0/administrator-guide/upgrade-guide.md
new file mode 100644
index 0000000000000000000000000000000000000000..ca203f23ab7c916a049932d7ad7834c21987f285
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/administrator-guide/upgrade-guide.md
@@ -0,0 +1,347 @@
+---
+title: 升级指南
+summary: 升级指南
+author: Zhang Cuiping
+date: 2021-09-27
+---
+
+# 升级指南
+
+## 概述
+
+本文档详细的描述了版本升级、回滚流程、以及具体的操作指导，同时提供了常见的问题解答及故障处理方法。
+
+## 读者对象
+
+本文档主要适用于升级的操作人员。操作人员必须具备以下经验和技能:
+
+- 熟悉当前网络的组网和相关网元的版本信息。
+- 有该设备维护经验，熟悉设备的操作维护方式。
+
+## 升级方案
+
+本节为指导用户选择升级方式。
+
+用户根据MogDB提供的新特性和数据库现状，确定是否对现有系统进行升级。
+
+当前支持的升级模式为就地升级和灰度升级。升级方式的策略又分为大版本升级和小版本升级。
+
+用户挑选升级方式后，系统会自动判断并选择合适的升级策略。
+
+* 就地升级: 升级期间需停止业务进行，一次性升级所有节点。
+
+* 灰度升级: 灰度升级支持全业务操作，也是一次性升级所有节点（目前仅支持从1.1.0版本到2.0及以上版本进行灰度升级）。
+
+## 升级前的版本要求（升级路径）
+
+MogDB升级版本要求如[表1](#biaoyi)所示。
+
+**表 1**  升级前的版本要求（升级路径）<a id="biaoyi"> </a>
+
+| 版本                      | 升级说明                            |
+| ------------------------- | ----------------------------------- |
+| MogDB 1.1.0版本之后的版本 | 可以升级到MogDB 1.1.0之后的任意版本 |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:** 升级前版本，可以通过执行如下工具查看。
+>
+> ```bash
+> gsql -V | --version
+> ```
+
+## 升级影响和升级约束
+
+升级过程需要注意以下事项。
+
+- 升级操作不能和扩容、缩容同时执行。
+- 不支持虚拟IP。
+- 升级过程中，不允许对wal_level，max_connections，max_prepared_transactions，max_locks_per_transaction这四个GUC参数的值进行修改。如果修改，会导致回滚后实例启动异常。
+- 建议在数据库系统空闲情况下进行升级，尽量避开业务繁忙的时间段（可按照经验判断，如节假日等）。
+- 升级前尽可能保证数据库正常。可以通过gs_om -t status查询，查询结果的cluster_state为Normal代表数据库正常。
+- 升级前保证数据库互信正常，可以在任意节点上，通过ssh hostname命令，连接另外一个节点进行验证。如果各机器间互连不用输入密码，说明互信正常（通常数据库状态正常时，互信一般都是正常的）。
+- 升级前后，数据库的部署方式（配置文件）不能发生变化。升级前会对部署方式进行校验，如果改变，会报错。
+- 升级前要保证操作系统处于健康状态，通过gs_checkos工具可以完成操作系统状态检查。
+- 就地升级需要停止业务，灰度升级支持全业务操作。
+- 数据库运行正常且主DN的数据完全同步到备DN。
+- 升级过程中不允许打开kerberos开关。
+- 请不要修改安装包中解压出来的version.cfg文件。
+- 如果升级过程中出现异常导致升级失败，需用户手动回滚，并且必须回滚成功后才能进行下一次升级。
+- 如果升级回滚成功后，再次升级成功，未提交阶段设置的GUC参数将失效。
+- 执行升级的过程中请不要手动设置GUC参数。
+- 灰度升级中，升级的时候都会产生不超过10s的业务中断
+- 升级过程中，必须保持内核版本与om版本一致才可执行om操作。这里的一致是指，内核代码和om代码都来自同一个软件包。如果执行了升级包的前置脚本却没有升级，或者升级回滚后没有执行基线包的前置脚本，就会造成内核代码和om代码的不一致。
+- 升级过程中如果系统表新增了字段，升级后通过**\d**命令将查看不到这些新增的字段。此时通过**select**命令可以查到这些新增的字段。
+- 升级需要guc参数enable_stream_replication=on，该参数为off时不允许升级。
+- 灰度升级中，业务并发要小于200并发读加200并发写的情况。
+- 若在MogDB 2.0之前的版本中使用了MOT表，则不支持升级到MogDB 2.0版本。
+
+## 升级流程
+
+本章介绍升级到该版本的主要升级过程。
+
+**图 1**  升级流程图
+
+![12](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/upgrade-guide-1.png)
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif)**说明:** 本文档中描述的时间仅供参考，实际操作时间以现场情况为准。
+
+**表 2**  升级流程执行效率估计
+
+<table> <tr> <td>  步骤</td> <td>  建议起始时间</td> <td> 耗时（天/小时/分钟） </td> <td> 业务中断时长 </td> <td>  备注 </td> </tr> <tr> <td>升级前准备与检查  </td> <td>  升级操作前一天</td> <td>  约2～3小时。 </td> <td> 对业务无影响。 </td> <td> 升级前检查和备份数据、校验软件包等操作。 </td> </tr> <tr> <td> 升级操作 </td> <td> 业务空闲期 </td> <td>  耗时主要集中在数据库的启动和停止以及每个database的系统表修改处。升级操作耗时一般不会超过30分钟。</td> <td>与操作时长一致，一般不会超过30分钟。 </td> <td>  依据指导书开始升级。</td> </tr> <tr> <td> 升级验证 </td> <td> 业务空闲期</td> <td> 约30分钟。  </td> <td> 与操作时长一致，约30分钟。 </td> <td> - </td> </tr> <tr> <td> 提交升级 </td> <td> 业务空闲期 </td> <td>  提交升级耗时一般不超过10分钟。</td> <td> 与操作时长一致，一般不超过10分钟。 </td> <td> - </td> </tr> <tr> <td>升级版本回滚  </td> <td> 业务空闲期 </td> <td> 版本回滚耗时一般不会超过30分钟。 </td> <td> 与操作时长一致，一般不会超过30分钟。 </td> <td> - </td> </tr> </table>
+
+## 升级前准备与检查
+
+### 升级前准备与检查清单
+
+**表 3**  升级前准备清单
+
+<table> <tr> <td>  序号</td> <td>  升级准备项目项目</td> <td> 准备内容 </td> <td> 建议起始时间 </td> <td>   耗时（天/小时/分钟） </td> </tr> <tr> <td>1  </td> <td>   收集节点信息</td> <td>  收集到数据库涉及节点的名称、IP地址，root、omm用户密码等环境信息。 </td> <td>升级前一天 </td> <td> 1小时 </td> </tr> <tr> <td> 2 </td> <td>  设置root用户远程登录 </td> <td>  设置配置文件，允许root用户远程登录。</td> <td>升级前一天 </td> <td>  2小时</td> </tr> <tr> <td>3 </td> <td> 备份数据</td> <td> 参考《管理指南》中的“备份与恢复”章节进行。  </td> <td> 升级前一天 </td> <td>备份数据量和方案不同，耗时也不同 </td> </tr> <tr> <td>4 </td> <td> 获取并校验升级包 </td> <td>  获取升级软件包，进行完整性校验。</td> <td>   升级前一天 </td> <td>0.5小时 </td> </tr> <tr> <td>5 </td> <td> 健康检查 </td> <td> 使用gs_checkos工具完成操作系统状态检查。 </td> <td> 升级前一天 </td> <td>  0.5小时 </td> </tr> <tr> <td>6 </td> <td>  检查数据库节点磁盘使用率</td> <td>  使用df命令查看磁盘使用率。</td> <td>   升级前一天 </td> <td> 0.5小时</td> </tr> <tr> <td>7 </td> <td> 检查数据库状态 </td> <td> 使用gs_om工具完成数据库状态检查。 </td> <td> 升级前一天 </td> <td> 0.5小时 </td> </tr> </table>
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif)**说明:** “耗时”依不同环境（包括现场数据量、服务器性能等原因)会存在一定差异。
+
+### 收集节点信息
+
+联系数据库系统管理员，获取数据库涉及节点的节点名称、节点IP地址。节点的root、omm用户密码等环境信息。
+
+**表 4**  节点信息<a id="biaosi"> </a>
+
+<table>
+<tr>
+<td>  序号</td>
+<td>  节点名称</td>
+<td> 节点IP </td>
+<td>
+root用户密码</td>
+<td>  omm用户密码</td>
+<td> 备注 </td>
+</tr>
+<tr>
+<td>1  </td>
+<td>
+-</td>
+<td>
+- </td>
+<td>  -</td>
+<td>  -</td>
+<td> - </td>
+</tr>
+</table>
+
+### 备份数据
+
+升级一旦失败，有可能会影响到业务的正常开展。提前备份数据，就可以在风险发生后，尽快的恢复业务。
+
+请参考《管理指南》中的“备份与恢复”章节，完成数据的备份。
+
+### 获取升级包
+
+访问[此页面](https://www.mogdb.io/downloads/mogdb)获取想要升级的升级包。
+
+### 健康检查
+
+通过gs_checkos工具可以完成操作系统状态检查。
+
+**前提条件**
+
+- 当前的硬件和网络环境正常。
+- 各主机间root互信状态正常。
+- 只能使用root用户执行gs_checkos命令。
+
+**操作步骤**
+
+1. 以root用户身份登录服务器。
+
+2. 执行如下命令对服务器的OS参数进行检查。
+
+    ```
+    # gs_checkos -i A
+    ```
+
+    检查服务器的OS参数的目的是为了保证数据库正常通过预安装，并且在安装成功后可以安全高效的运行。
+
+#### 检查数据库节点磁盘使用率
+
+建议数据库节点磁盘使用率低于80%时再执行升级操作。
+
+#### 检查数据库状态
+
+本节介绍数据库状态查询的具体操作。
+
+**验证步骤**
+
+1. 以数据库用户（如omm）登录节点，source环境变量。
+
+    ```
+    # su - omm
+    $ source /home/omm/.bashrc
+    ```
+
+2. 执行如下命令查看数据库状态。
+
+    ```bash
+    gs_om -t status
+    ```
+
+3. 保证数据库状态正常。
+
+## 升级操作
+
+介绍就地升级和灰度升级的详细操作。
+
+**操作步骤**
+
+1. 以root身份登录节点。
+
+2. 创建新包目录。
+
+    ```
+    # mkdir -p /opt/software/mogdb_upgrade
+    ```
+
+3. 将需要更新的新包上传至目录"/opt/software/mogdb_upgrade"并解压。
+
+4. 进入安装包解压出的script目录下:
+
+    ```
+    # cd /opt/software/mogdb_upgrade/script
+    ```
+
+5. 在就地升级或灰度升级前执行前置脚本gs_preinstall。<a id="qianzhijiaoben"> </a>
+
+    ```
+    # ./gs_preinstall -U omm -G dbgrp  -X /opt/software/mogdb/clusterconfig.xml
+    ```
+
+6. 切换至omm用户。
+
+    ```
+    # su - omm
+    ```
+
+7. 数据库状态正常时，使用如下命令进行就地升级或者灰度升级。
+
+    示例一: 使用gs_upgradectl脚本执行就地升级。
+
+    ```bash
+    gs_upgradectl -t auto-upgrade -X /opt/software/mogdb/clusterconfig.xml
+    ```
+
+    示例二: 使用gs_upgradectl脚本执行灰度升级。
+
+    ```bash
+    gs_upgradectl -t auto-upgrade -X /opt/software/mogdb/clusterconfig.xml --grey
+    ```
+
+## 升级验证
+
+本章介绍升级完成后的验证操作。给出验证的用例和详细操作步骤。
+
+### 验证项目的检查表
+
+**表 5**  验证项目的检查表
+
+<table> <tr> <td>  序号</td> <td>     验证项目</td> <td>    检查标准</td> <td>     检查结果</td> </tr> <tr> <td>1  </td> <td>     版本查询</td> <td>   查询升级后版本是否正确 </td> <td>  -</td> </tr> <tr> <td>2 </td> <td>     健康检查</td> <td>    使用gs_checkos工具完成操作系统状态检查。</td> <td>  -</td> </tr> <tr> <td>3  </td> <td>     数据库状态</td> <td>    使用gs_om工具完成数据库状态检查。</td> <td>  -</td> </tr> </table>
+
+### 升级版本查询
+
+本节介绍版本查询的具体操作。
+
+**验证步骤**
+
+1. 以数据库用户（如omm）登录节点，source环境变量。
+
+    ```
+    # su - omm
+    $ source /home/omm/.bashrc
+    ```
+
+2. 执行如下命令查看所有节点的版本信息。
+
+    ```bash
+    gs_ssh -c "gsql -V"
+    ```
+
+### 检查升级数据库状态
+
+本节介绍数据库状态查询的具体操作。
+
+**验证步骤**
+
+1. 以数据库用户（如omm）登录节点。
+
+    ```
+    # su - omm
+    ```
+
+2. 执行如下命令查看数据库状态。
+
+    ```bash
+    gs_om -t status
+    ```
+
+    查询结果的cluster_state为Normal代表数据库正常。
+
+## 提交升级
+
+升级完成后，如果验证也没问题。接下来就可以提交升级。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:** 一旦提交操作完成，则不能再执行回滚操作。
+
+**操作步骤**
+
+1. 以数据库用户（如omm）登录节点。
+
+    ```
+    # su - omm
+    ```
+
+2. 执行如下命令完成升级提交。
+
+    ```bash
+    gs_upgradectl -t commit-upgrade  -X /opt/software/mogdb/clusterconfig.xml
+    ```
+
+## 升级版本回滚
+
+本章介绍版本回滚方法。
+
+**操作步骤**
+
+1. 以数据库用户（如omm）登录节点。
+
+    ```
+    # su - omm
+    ```
+
+2. 执行如下命令完成版本回滚（回滚内核代码）。回滚完成，如果需要保持内核和om代码的版本一致，可以执行一下旧包的前置命令（参见[执行前置脚本gs_preinstall](#qianzhijiaoben))。
+
+    ```bash
+    gs_upgradectl -t auto-rollback  -X /opt/software/mogdb/clusterconfig.xml
+    ```
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:** 如果数据库异常，需要强制回滚，可以使用如下命令。
+    >
+    > ```bash
+    >    gs_upgradectl -t auto-rollback -X /opt/software/mogdb/clusterconfig.xml   --force
+    > ```
+
+3. 查看回滚之后的版本号。
+
+    ```bash
+    gs_om -V | --version
+    ```
+
+    如果升级失败，请按照如下方式进行处理:
+
+    a. 排查是否有环境问题。
+
+    如磁盘满、网络故障等，或者升级包、升级版本号是否正确。排除问题后，可以尝试重入升级。
+
+    b. 如果没有发现环境问题，或者重入升级失败，需要收集相关日志，找技术支持工程师定位。
+
+    收集日志命令:
+
+    ```bash
+    gs_collector -begin-time='20200724 00:00'  -end-time='20200725 00:00'
+    ```
+
+    如果条件允许，建议保留环境。
diff --git a/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/1-core-dump-occurs-due-to-full-disk-space.md b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/1-core-dump-occurs-due-to-full-disk-space.md
new file mode 100644
index 0000000000000000000000000000000000000000..758fefdffeb1ff68fc00efb7722e0282afb65484
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/1-core-dump-occurs-due-to-full-disk-space.md
@@ -0,0 +1,22 @@
+---
+title: 磁盘满故障引起的core问题
+summary: 磁盘满故障引起的core问题
+author: Guo Huan
+date: 2021-05-24
+---
+
+# 磁盘满故障引起的core问题
+
+## 问题现象
+
+TPCC运行时，注入磁盘满故障，数据库进程mogdb core掉，如下图所示。
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/core-dump-occurs-due-to-full-disk-space.png)
+
+## 原因分析
+
+数据库本身机制，在磁盘满时，xlog日志无法进行写入，通过panic日志退出程序。
+
+## 处理办法
+
+外部监控磁盘使用状况，定时进行清理磁盘。
diff --git a/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/2-core-dump-occurs-due-to-incorrect-settings-of-guc-parameter-log-directory.md b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/2-core-dump-occurs-due-to-incorrect-settings-of-guc-parameter-log-directory.md
new file mode 100644
index 0000000000000000000000000000000000000000..151d277c8d5a69cb9a19ff6d1e41e1974cbe0710
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/2-core-dump-occurs-due-to-incorrect-settings-of-guc-parameter-log-directory.md
@@ -0,0 +1,20 @@
+---
+title: GUC参数log_directory设置不正确引起的core问题
+summary: GUC参数log_directory设置不正确引起的core问题
+author: Guo Huan
+date: 2021-05-24
+---
+
+# GUC参数log_directory设置不正确引起的core问题
+
+## 问题现象
+
+数据库进程拉起后出现coredump，日志无内容。
+
+## 原因分析
+
+GUC参数log_directory设置的路径不可读取或无访问权限，数据库在启动过程中进行校验失败，通过panic日志退出程序。
+
+## 处理办法
+
+GUC参数log_directory设置为合法路径，具体请参考[log_directory](1-logging-destination#log_directory)。
diff --git a/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/3-core-dump-occurs-when-removeipc-is-enabled.md b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/3-core-dump-occurs-when-removeipc-is-enabled.md
new file mode 100644
index 0000000000000000000000000000000000000000..daf6fbf4dbb0fcb8b691ba1b1e832a7057c33412
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/3-core-dump-occurs-when-removeipc-is-enabled.md
@@ -0,0 +1,24 @@
+---
+title: 开启RemoveIPC引起的core问题
+summary: 开启RemoveIPC引起的core问题
+author: Guo Huan
+date: 2021-05-24
+---
+
+# 开启RemoveIPC引起的core问题
+
+## 问题现象
+
+操作系统配置中RemoveIPC参数设置为yes，数据库运行过程中出现宕机，并显示如下日志消息。
+
+```shell
+FATAL: semctl(1463124609, 3, SETVAL, 0) failed: Invalid argument
+```
+
+## 原因分析
+
+当RemoveIPC参数设置为yes时，操作系统会在对应用户退出时删除IPC资源（共享内存和信号量），从而使得MogDB服务器使用的IPC资源被清理，引发数据库宕机。
+
+## 处理分析
+
+设置RemoveIPC参数为no。设置方法请参考《安装指南》中“[修改操作系统配置](3-modifying-os-configuration)”章节。
diff --git a/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/4-core-dump-occurs-after-installation-on-x86.md b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/4-core-dump-occurs-after-installation-on-x86.md
new file mode 100644
index 0000000000000000000000000000000000000000..e717f74e9955a329676d9f8a748101bf6aef9065
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/4-core-dump-occurs-after-installation-on-x86.md
@@ -0,0 +1,26 @@
+---
+title: x86下安装完成后发生coredump
+summary: x86下安装完成后发生coredump
+author: Guo Huan
+date: 2021-12-09
+---
+
+# x86下安装完成后发生coredump
+
+## 问题现象
+
+x86架构下安装MogDB完成后发生coredump，出现如下报错
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/core-dump-occurs-after-installation-on-x86-1.png)
+
+## 原因分析
+
+x86架构不包括rdtscp指令，常见于在本地windows系统上，虚拟化安装Linux服务器，但虚拟化版本太低，部署MogDB启动失败。
+
+## 处理办法
+
+使用`lscpu | grep rdtscp`查看是否支持rdtscp指令集
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/administrator-guide/core-dump-occurs-after-installation-on-x86-2.png)
+
+可以通过主机的管理侧设置开启支持该指令集。云主机CPU模式，设置为host-passthrough，重新reboot。
diff --git a/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/10-disk-space-usage-reaches-the-threshold.md b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/10-disk-space-usage-reaches-the-threshold.md
new file mode 100644
index 0000000000000000000000000000000000000000..2bb6ec7a65ebd3fac6136fa94db341aa176882c5
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/10-disk-space-usage-reaches-the-threshold.md
@@ -0,0 +1,58 @@
+---
+title: 磁盘空间达到阈值，数据库只读
+summary: 磁盘空间达到阈值，数据库只读
+author: Guo Huan
+date: 2021-05-24
+---
+
+# 磁盘空间达到阈值，数据库只读
+
+## 问题现象
+
+执行非只读SQL时报错如下。
+
+```
+ERROR: cannot execute %s in a read-only transaction.
+```
+
+或者运行中部分非只读SQL（insert、update、create table as、create index、alter table 及copy from等）时报错。
+
+```
+canceling statement due to default_transaction_read_only is on.
+```
+
+## 原因分析
+
+磁盘空间达到阈值后，设置数据库只读，只允许只读语句执行。
+
+## 处理办法
+
+1. 使用maintenance模式连接数据库，以下两种方法均可。
+
+   - 方式一
+
+     ```bash
+     gsql -d mogdb -p 8000 -r -m
+     ```
+
+   - 方式二
+
+     ```bash
+     gsql -d mogdb -p 8000 -r
+     ```
+
+     连接成功后，执行如下命令：
+
+     ```bash
+     set xc_maintenance_mode=on;
+     ```
+
+2. 使用DROP/TRUNCATE语句删除当前不再使用的用户表，直至磁盘空间使用率小于设定的阈值。
+
+   删除用户表只能暂时缓解磁盘空间不足的问题，建议尽早通过扩容解决磁盘空间不足的问题。
+
+3. 使用系统用户omm设置数据库只读模式关闭。
+
+   ```bash
+   gs_guc reload -D /mogdb/data/dbnode -c "default_transaction_read_only=off"
+   ```
diff --git a/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/11-slow-response-to-a-query-statement.md b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/11-slow-response-to-a-query-statement.md
new file mode 100644
index 0000000000000000000000000000000000000000..82a5a4b389abeef7cfd03ee87df638ef45f05eaa
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/11-slow-response-to-a-query-statement.md
@@ -0,0 +1,48 @@
+---
+title: 分析查询语句长时间运行的问题
+summary: 分析查询语句长时间运行的问题
+author: Guo Huan
+date: 2021-05-24
+---
+
+# 分析查询语句长时间运行的问题
+
+## 问题现象
+
+系统中部分查询语句运行时间过长。
+
+## 原因分析
+
+- 查询语句较为复杂，需要长时间运行。
+- 查询语句阻塞。
+
+## 处理办法
+
+1. 以操作系统用户omm登录主机。
+
+2. 使用如下命令连接数据库。
+
+   ```bash
+   gsql -d mogdb -p 8000
+   ```
+
+   postgres为需要连接的数据库名称，8000为端口号。
+
+3. 查看系统中长时间运行的查询语句。
+
+   ```sql
+   SELECT timestampdiff(minutes, query_start, current_timestamp) AS runtime, datname, usename, query FROM pg_stat_activity WHERE state != 'idle' ORDER BY 1 desc;
+   ```
+
+   查询会返回按执行时间长短从大到小排列的查询语句列表。第一条结果就是当前系统中执行时间长的查询语句。
+
+   如果当前系统较为繁忙，可以使用[TIMESTAMPDIFF](8-date-and-time-processing-functions-and-operators)函数通过限制current_timestamp和query_start大于某一阈值查看执行时间超过此阈值的查询语句。timestampdiff的第一个参数为时间差单位。例如，执行超过2分钟的查询语句可以通过如下语句查询。
+
+   ```sql
+   SELECT query FROM pg_stat_activity WHERE timestampdiff(minutes, query_start, current_timestamp) > 2;
+   ```
+
+4. 分析长时间运行的查询语句状态。
+
+   - 如果查询语句处于正常状态，则等待其执行完毕。
+   - 如果查询语句阻塞，请参见[分析查询语句是否被阻塞处理](14-analyzing-whether-a-query-statement-is-blocked)。
diff --git a/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/12-analyzing-the-status-of-a-query-statement.md b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/12-analyzing-the-status-of-a-query-statement.md
new file mode 100644
index 0000000000000000000000000000000000000000..8e6b993e604577ec5f5a54028803150359302631
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/12-analyzing-the-status-of-a-query-statement.md
@@ -0,0 +1,57 @@
+---
+title: 分析查询语句运行状态
+summary: 分析查询语句运行状态
+author: Guo Huan
+date: 2021-05-24
+---
+
+# 分析查询语句运行状态
+
+## 问题现象
+
+系统中部分查询语句运行时间过长，需要分析查询语句的运行状态。
+
+## 处理办法
+
+1. 以操作系统用户omm登录主机。
+
+2. 使用如下命令连接数据库。
+
+   ```bash
+   gsql -d mogdb -p 8000
+   ```
+
+   postgres为需要连接的数据库名称，8000为端口号。
+
+3. 设置参数track_activities为on。
+
+   ```sql
+   SET track_activities = on;
+   ```
+
+   当此参数为on时，数据库系统才会收集当前活动查询的运行信息。
+
+4. 查看正在运行的查询语句。以查看视图pg_stat_activity为例。
+
+   ```sql
+   SELECT datname, usename, state, query FROM pg_stat_activity;
+   datname  | usename | state  | query
+   ----------+---------+--------+-------
+   mogdb     | omm     | idle   |
+   mogdb     | omm     | active |
+   (2 rows)
+   ```
+
+   如果state字段显示为idle，则表明此连接处于空闲，等待用户输入命令。 如果仅需要查看非空闲的查询语句，则使用如下命令查看。
+
+   ```sql
+   SELECT datname, usename, state, query FROM pg_stat_activity WHERE state != 'idle';
+   ```
+
+5. 分析查询语句为活跃状态还是阻塞状态。通过如下命令查看当前处于阻塞状态的查询语句。
+
+   ```sql
+   SELECT datname, usename, state, query FROM pg_stat_activity WHERE waiting = true;
+   ```
+
+   查询结果中包含了当前被阻塞的查询语句，该查询语句所请求的锁资源可能被其他会 话持有，正在等待持有会话释放锁资源。
diff --git a/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/13-forcibly-terminating-a-session.md b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/13-forcibly-terminating-a-session.md
new file mode 100644
index 0000000000000000000000000000000000000000..eb9bb7fa4da15089bd1a5f603b1b108a039446a6
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/13-forcibly-terminating-a-session.md
@@ -0,0 +1,62 @@
+---
+title: 强制结束指定的问题会话
+summary: 强制结束指定的问题会话
+author: Guo Huan
+date: 2021-05-24
+---
+
+# 强制结束指定的问题会话
+
+## 问题现象
+
+有些情况下，为了使系统继续提供服务，管理员需要强制结束有问题的会话。
+
+## 处理办法
+
+1. 以操作系统用户omm登录主机。
+
+2. 使用如下命令连接数据库。
+
+   ```bash
+   gsql -d mogdb -p 8000
+   ```
+
+   mogdb为需要连接的数据库名称，8000为端口号。
+
+3. 从当前活动会话视图查找问题会话的线程ID。
+
+   ```sql
+   SELECT datid, pid, state, query FROM pg_stat_activity;
+   ```
+
+   显示类似如下信息，其中pid的值即为该会话的线程ID。
+
+   ```bash
+   datid |       pid       | state  | query
+   -------+-----------------+--------+------
+   13205 | 139834762094352 | active |
+   13205 | 139834759993104 | idle   |
+   (2 rows)
+   ```
+
+4. 根据线程ID结束会话。
+
+   ```
+   SELECT pg_terminate_backend(139834762094352);
+   ```
+
+   显示类似如下信息，表示结束会话成功。
+
+   ```bash
+   pg_terminate_backend
+   ---------------------
+   t
+   (1 row)
+   ```
+
+   显示类似如下信息，表示用户正在尝试结束当前会话，此时仅会重连会话，而不是结束会话。
+
+   ```bash
+   FATAL:  terminating connection due to administrator command
+   FATAL:  terminating connection due to administrator command The connection to the server was lost. Attempting reset: Succeeded.
+   ```
diff --git a/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/14-analyzing-whether-a-query-statement-is-blocked.md b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/14-analyzing-whether-a-query-statement-is-blocked.md
new file mode 100644
index 0000000000000000000000000000000000000000..676dcdf2f1f395e6d12de732b1decac57bb17f94
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/14-analyzing-whether-a-query-statement-is-blocked.md
@@ -0,0 +1,56 @@
+---
+title: 分析查询语句是否被阻塞
+summary: 分析查询语句是否被阻塞
+author: Guo Huan
+date: 2021-05-24
+---
+
+# 分析查询语句是否被阻塞
+
+## 问题现象
+
+数据库系统运行时，在某些业务场景下，查询语句会被阻塞，导致语句运行时间过长。
+
+## 原因分析
+
+查询语句需要通过加锁来保护其要访问的数据对象。当要进行加锁时发现要访问的数据对象已经被其他会话加锁，则查询语句会被阻塞，等待其他会话完成操作并释放锁资源。这些需要加锁访问的数据对象主要包括表、元组等。
+
+## 处理办法
+
+1. 以操作系统用户omm登录主机。
+
+2. 使用如下命令连接数据库。
+
+   ```bash
+   gsql -d mogdb -p 8000
+   ```
+
+   mogdb为需要连接的数据库名称，8000为端口号。
+
+3. 从当前活动会话视图查找问题会话的线程ID。
+
+   ```sql
+   SELECT w.query AS waiting_query, w.pid AS w_pid, w.usename AS w_user, l.query AS locking_query, l.pid AS l_pid, l.usename AS l_user, t.schemaname || '.' || t.relname AS tablename FROM pg_stat_activity w JOIN pg_locks l1 ON w.pid = l1.pid AND NOT l1.granted JOIN pg_locks l2 ON l1.relation = l2.relation AND l2.granted JOIN pg_stat_activity l ON l2.pid = l.pid JOIN pg_stat_user_tables t ON l1.relation = t.relid WHERE w.waiting = true;
+   ```
+
+4. 根据线程ID结束会话。
+
+   ```sql
+   SELECT pg_terminate_backend(139834762094352);
+   ```
+
+   显示类似如下信息，表示结束会话成功。
+
+   ```bash
+   pg_terminate_backend
+   ---------------------
+   t
+   (1 row)
+   ```
+
+   显示类似如下信息，表示用户正在尝试结束当前会话，此时仅会重连会话，而不是结束会话。
+
+   ```bash
+   FATAL:  terminating connection due to administrator command
+   FATAL:  terminating connection due to administrator command The connection to the server was lost. Attempting reset: Succeeded.
+   ```
diff --git a/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/15-low-query-efficiency.md b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/15-low-query-efficiency.md
new file mode 100644
index 0000000000000000000000000000000000000000..63fcf3627c05907845704e2fbc11ba2916a3925d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/15-low-query-efficiency.md
@@ -0,0 +1,32 @@
+---
+title: 分析查询效率异常降低的问题
+summary: 分析查询效率异常降低的问题
+author: Guo Huan
+date: 2021-05-24
+---
+
+# 分析查询效率异常降低的问题
+
+## 问题现象
+
+通常在几十毫秒内完成的查询，有时会突然需要几秒的时间完成；而通常需要几秒完成的查询，有时需要半小时才能完成。
+
+## 处理办法
+
+通过下列的操作步骤，分析查询效率异常降低的原因。
+
+1. 使用analyze命令分析数据库。
+
+   使用analyze命令会更新所有表中数据大小以及属性等相关统计信息，建议在作业压力较小时执行。如果此命令执行后性能恢复或者有所提升，则表明autovacuum未能很好的完成它的工作，有待进一步分析。
+
+2. 检查查询语句是否返回了多余的数据信息。
+
+   例如，如果查询语句先查询一个表中所有的记录，而只用到结果中的前10条记录。对于包含50条记录的表，查询速度较快；但是，当表中包含的记录数达到50000条，查询效率将会有所下降。 如果业务应用中存在只需要部分数据信息，但是查询语句却是返回所有信息的情况，建议修改查询语句，增加LIMIT子句来限制返回的记录数。这样使数据库优化器有了一定的优化空间，一定程度上会提升查询效率。
+
+3. 检查查询语句单独运行时是否仍然较慢。
+
+   尝试在数据库没有其他查询或查询较少的时候运行查询语句，并观察运行效率。如果效率较高，则说明可能是由于之前运行数据库系统的主机负载过大导致查询低效。此外，还可能是由于执行计划比较低效，但是由于主机硬件较快使得查询效率较高。
+
+4. 检查重复相同查询语句的执行效率。
+
+   查询效率低的一个重要原因是查询所需信息没有缓存在内存中，这可能是由于内存资源紧张，导致缓存信息被其他查询处理覆盖。重复执行相同的查询语句，如果后续执行的查询语句效率提升，则可能是由于上述原因导致。
diff --git a/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/16-lock-wait-timeout-is-displayed.md b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/16-lock-wait-timeout-is-displayed.md
new file mode 100644
index 0000000000000000000000000000000000000000..8ba85522b1a01fef842e3eb58b4d49728992667d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/16-lock-wait-timeout-is-displayed.md
@@ -0,0 +1,25 @@
+---
+title: 执行 SQL 语句时，提示 Lock wait timeout
+summary: 执行 SQL 语句时，提示 Lock wait timeout
+author: Guo Huan
+date: 2021-05-24
+---
+
+# 执行 SQL 语句时，提示 Lock wait timeout
+
+## 问题现象
+
+执行SQL语句时，提示”Lock wait timeout”。
+
+```
+ERROR:  Lock wait timeout: thread 140533638080272 waiting for ShareLock on relation 16409 of database 13218 after 1200000.122 ms ERROR:  Lock wait timeout: thread 140533638080272 waiting for AccessExclusiveLock on relation 16409 of database 13218 after 1200000.193 ms
+```
+
+## 原因分析
+
+数据库中存在锁等待超时现象。
+
+## 处理办法
+
+- 数据库在识别此类错误后，会自动进行重跑，重跑次数可以使用max_query_retry_times控制。
+- 需要分析锁超时的原因，查看系统表pg_locks，pg_stat_activity可以找出超时的SQL语句。
diff --git a/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/17-table-size-does-not-change.md b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/17-table-size-does-not-change.md
new file mode 100644
index 0000000000000000000000000000000000000000..7a7c328eb4b2c251e79dc4d435dde3da038ff5af
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/17-table-size-does-not-change.md
@@ -0,0 +1,39 @@
+---
+title: VACUUM FULL一张表后，表文件大小无变化
+summary: VACUUM FULL一张表后，表文件大小无变化
+author: Guo Huan
+date: 2021-05-24
+---
+
+# VACUUM FULL一张表后，表文件大小无变化
+
+## 问题现象
+
+使用VACUUM FULL命令对一张表进行清理，清理完成后表大小和清理前一样大。
+
+## 原因分析
+
+假定该表的名称为table_name，对于该现象可能有以下两种原因：
+
+- table_name表本身没有delete过数据，使用VACUUM FULL table_name后无需清理delete的数据。因此表大小清理前后一样大。
+- 在执行VACUUM FULL table_name时有并发的事务存在，可能会导致VACUUM FULL跳过清理最近删除的数据，导致清理不完全。
+
+## 处理办法
+
+对于第二种可能原因，有如下两种处理方法：
+
+- 如果在VACUUM FULL时有并发的事务存在，此时需要等待所有事务结束，再次执行VACUUM FULL命令对该表进行清理。
+
+- 如果使用上面的方法清理后，表文件大小仍然无变化，确认无业务操作后，使用以下SQL查询活跃事务列表状态：
+
+  ```sql
+  select txid_current();
+  ```
+
+  使用该SQL可以查询当前的事务XID。再使用以下命令查看活跃事务列表：
+
+  ```sql
+  select txid_current_snapshot();
+  ```
+
+  如果发现活跃事务列表中有XID比当前的事务XID小时，停止数据库再启动数据库，再次使用VACUUM FULL命令对该表进行清理。
diff --git a/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/18-an-error-is-reported-when-the-table-partition-is-modified.md b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/18-an-error-is-reported-when-the-table-partition-is-modified.md
new file mode 100644
index 0000000000000000000000000000000000000000..c158f33e2859ede4556ce4e017595f707a842957
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/18-an-error-is-reported-when-the-table-partition-is-modified.md
@@ -0,0 +1,46 @@
+---
+title: 执行修改表分区操作时报错
+summary: 执行修改表分区操作时报错
+author: Guo Huan
+date: 2021-05-24
+---
+
+# 执行修改表分区操作时报错
+
+## 问题现象
+
+执行ALTER TABLE PARTITION时，报错如下。
+
+```
+ERROR:start value of partition "XX" NOT EQUAL up-boundary of last partition.
+```
+
+## 原因分析
+
+在同一条ALTER TABLE PARTITION语句中，既存在DROP PARTITION又存在ADD PARTITION时，无论它们在语句中的顺序是什么，MogDB总会先执行DROP PARTITION再执行ADD PARTITION。执行完DROP PARTITION删除末尾分区后，再执行ADD PARTITION操作会出现分区间隙，导致报错。
+
+## 处理办法
+
+为防止出现分区间隙，需要将ADD PARTITION的START值前移。 示例如下。
+
+```sql
+--创建分区表partitiontest。
+mogdb=#  CREATE TABLE partitiontest
+(
+c_int integer,
+c_time TIMESTAMP WITHOUT TIME ZONE
+)
+PARTITION BY range (c_int)
+(
+partition p1 start(100)end(108),
+partition p2 start(108)end(120)
+);
+--使用如下两种语句会发生报错：
+mogdb=#  ALTER TABLE partitiontest ADD PARTITION p3 start(120)end(130), DROP PARTITION p2;
+ERROR:  start value of partition "p3" NOT EQUAL up-boundary of last partition.
+mogdb=#  ALTER TABLE partitiontest DROP PARTITION p2,ADD PARTITION p3 start(120)end(130);
+ERROR:  start value of partition "p3" NOT EQUAL up-boundary of last partition.
+--可以修改语句为：
+mogdb=#  ALTER TABLE partitiontest ADD PARTITION p3 start(108)end(130), DROP PARTITION p2;
+mogdb=#  ALTER TABLE partitiontest DROP PARTITION p2,ADD PARTITION p3 start(108)end(130);
+```
diff --git a/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/19-different-data-is-displayed.md b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/19-different-data-is-displayed.md
new file mode 100644
index 0000000000000000000000000000000000000000..06103877cdee74903eba33bca50e491da03e8b5d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/19-different-data-is-displayed.md
@@ -0,0 +1,32 @@
+---
+title: 不同用户查询同表显示数据不同
+summary: 不同用户查询同表显示数据不同
+author: Guo Huan
+date: 2021-05-24
+---
+
+# 不同用户查询同表显示数据不同
+
+## 问题现象
+
+2个用户登录相同数据库human_resource，同样执行如下查询语句，查询同一张表areas时，查询结果却不一致。
+
+```sql
+select count(*) from areas;
+```
+
+## 原因分析
+
+1. 检查同名表是否是同一张表。在关系型数据库中，确定一张表通常需要3个因素：database，schema，table。从问题现象描述看，database，table已经确定， 分别是human_resource、areas。
+2. 检查同名表的schema是否一致。使用omm，user01分别登录发现，search_path依次是public和”$user”。omm作为数据库管理员，默认不会创建omm同名的schema，即不指定schema的情况下所有表都会建在public下。而对于普通用户如user01，则会在创建用户时，默认创建同名的schema，即不指定schema时表都会创建在user01的schema下。
+3. 如果最终判断是同一张表，存在不同用户访问数据不同情况，则需要进一步判断当前该表中对象针对不同的用户是否存在不同的访问策略。
+
+## 处理办法
+
+- 对于不同schema下同名表的查询，在查询表时加上schema引用。格式如下。
+
+  ```bash
+  schema.table
+  ```
+
+- 对于不同访问策略造成对同一表查询结果不同时，可以通过查询pg_rlspolicy系统表来确认具体的访问准则。
diff --git a/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/2-when-the-tpcc-is-running.md b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/2-when-the-tpcc-is-running.md
new file mode 100644
index 0000000000000000000000000000000000000000..fe49110d6eaa27265330b70782757ed91f460863
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/2-when-the-tpcc-is-running.md
@@ -0,0 +1,20 @@
+---
+title: TPCC运行时，注入磁盘满故障，TPCC卡住的问题
+summary: TPCC运行时，注入磁盘满故障，TPCC卡住的问题
+author: Guo Huan
+date: 2021-05-24
+---
+
+# TPCC运行时，注入磁盘满故障，TPCC卡住的问题
+
+## 问题现象
+
+TPCC运行时，注入磁盘满故障，TPCC卡住，故障消除后，TPCC自动续跑。
+
+## 原因分析
+
+数据库本身机制，在性能日志（gs_profile）所在磁盘满时，导致无法写入而陷入无限等待，表现为TPCC卡住。磁盘满故障消除后，性能日志能正常写入，TPCC恢复正常。
+
+## 处理分析
+
+外部监控磁盘使用状况，定时进行清理磁盘。
diff --git a/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/20-when-a-user-specifies-only-an-index-name.md b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/20-when-a-user-specifies-only-an-index-name.md
new file mode 100644
index 0000000000000000000000000000000000000000..d73f9b9fcaa195481bf1d5477cadb49b2a59c7d1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/20-when-a-user-specifies-only-an-index-name.md
@@ -0,0 +1,47 @@
+---
+title: 修改索引时只调用索引名提示索引不存在
+summary: 修改索引时只调用索引名提示索引不存在
+author: Guo Huan
+date: 2021-05-24
+---
+
+# 修改索引时只调用索引名提示索引不存在
+
+## 问题现象
+
+修改索引时只调用索引名提示索引不存在。举例如下。
+
+```sql
+--创建分区表索引HR_staffS_p1_index1，不指定索引分区的名称。
+CREATE INDEX HR_staffS_p1_index1 ON HR.staffS_p1 (staff_ID) LOCAL;
+--创建分区索引HR_staffS_p1_index2，并指定索引分区的名称。
+CREATE INDEX HR_staffS_p1_index2 ON HR.staffS_p1 (staff_ID) LOCAL
+(
+PARTITION staff_ID1_index,
+PARTITION staff_ID2_index TABLESPACE example3,
+PARTITION staff_ID3_index TABLESPACE example4
+) TABLESPACE example;
+--修改索引分区staff_ID2_index的表空间为example1，提示索引不存在。
+ALTER INDEX HR_staffS_p1_index2 MOVE PARTITION staff_ID2_index TABLESPACE example1;
+```
+
+## 原因分析
+
+推测是当前模式是public模式，而不是hr模式，导致检索不到该索引。
+
+```sql
+--执行如下命令验证推测，发现调用成功。
+ALTER INDEX hr.HR_staffS_p1_index2 MOVE PARTITION staff_ID2_index TABLESPACE example1;
+--修改当前会话的schema为hr。
+ALTER SESSION SET CURRENT_SCHEMA TO hr;
+--执行如下命令修改索引，即可执行成功。
+ALTER INDEX HR_staffS_p1_index2 MOVE PARTITION staff_ID2_index TABLESPACE example1;
+```
+
+## 处理办法
+
+在操作表、索引、视图时加上schema引用，格式如下。
+
+```
+schema.table
+```
diff --git a/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/21-reindexing-fails.md b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/21-reindexing-fails.md
new file mode 100644
index 0000000000000000000000000000000000000000..f7f671deb8a6f46d0f40b007191ffe61cbb5f977
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/21-reindexing-fails.md
@@ -0,0 +1,29 @@
+---
+title: 重建索引失败
+summary: 重建索引失败
+author: Guo Huan
+date: 2021-05-24
+---
+
+# 重建索引失败
+
+## 问题现象
+
+当Desc表的索引出现损坏时，无法进行一系列操作，可能的报错信息如下。
+
+```
+index \"%s\" contains corrupted page at block
+ %u" ,RelationGetRelationName(rel),BufferGetBlockNumber(buf), please reindex it.
+```
+
+## 原因分析
+
+在实际操作中，索引会由于软件问题或者硬件问题引起崩溃。例如，当索引分裂完而磁盘空间不足、出现页面损坏等问题时，会导致索引损坏。
+
+## 处理办法
+
+如果此表是以pg_cudesc_xxxxx_index进行命名则为列存表，则说明desc表的索引表损坏。通过desc表的索引表表名，找到对应主表的oid和表，执行如下语句重建表的索引。
+
+```
+REINDEX INTERNAL TABLE name;
+```
diff --git a/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/22-an-error-occurs-during-integer-conversion.md b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/22-an-error-occurs-during-integer-conversion.md
new file mode 100644
index 0000000000000000000000000000000000000000..fb9c6c7ea96b5bc70d54ff39169e878b89bd24e2
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/22-an-error-occurs-during-integer-conversion.md
@@ -0,0 +1,24 @@
+---
+title: 业务运行时整数转换错
+summary: 业务运行时整数转换错
+author: Guo Huan
+date: 2021-05-24
+---
+
+# 业务运行时整数转换错
+
+## 问题现象
+
+在转换整数时报错如下。
+
+```
+Invalid input syntax for integer: "13."
+```
+
+## 原因分析
+
+部分数据类型不能转换成目标数据类型。
+
+## 处理办法
+
+逐步缩小SQL范围确定不能转换的数据类型。
diff --git a/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/23-too-many-clients-already.md b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/23-too-many-clients-already.md
new file mode 100644
index 0000000000000000000000000000000000000000..7ea79796d797aa1474e1833560c00484ee54c9a1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/23-too-many-clients-already.md
@@ -0,0 +1,50 @@
+---
+title: 高并发报错”too many clients already”或无法创建线程
+summary: 高并发报错”too many clients already”或无法创建线程Concurrency Scenarios
+author: Guo Huan
+date: 2021-05-24
+---
+
+# 高并发报错”too many clients already”或无法创建线程
+
+## 问题现象
+
+高并发执行SQL，报错”sorry, too many clients already”；或报无法创建线程、无法fork进程等错误。
+
+## 原因分析
+
+该类报错是由于操作系统线程资源不足引起，查看操作系统ulimit -u，如果过小（例如小于32768），则基本可以判断是操作系统限制引起的。
+
+## 处理办法
+
+通过“ulimit -u”命令查看操作系统max user processes的值。
+
+```
+[root@MogDB36 mnt]# ulimit -u
+unlimited
+```
+
+按如下简易公式计算需要设置的最小值。
+
+```
+value=max(32768，实例数目*8192)
+```
+
+其中实例数目指本节点所有实例总数。
+
+设置最小值方法为，修改/etc/security/limits.conf，追加如下两行：
+
+```
+* hard nproc [value]
+* soft nproc [value]
+```
+
+对于不同操作系统修改方式略有不同，centos6以上版本可以修改/etc/security/ limits.d/90-nofile.conf文件，方法同上。
+
+另外，也可以直接通过如下命令设置，但OS重启会失效，可以添加到全局环境变量/etc/profile文件中使其生效。
+
+```
+ulimit -u [values]
+```
+
+在大并发模式下，建议开启线程池，使数据库内部的线程资源受控。
diff --git a/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/24-b-tree-index-faults.md b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/24-b-tree-index-faults.md
new file mode 100644
index 0000000000000000000000000000000000000000..d76be37d8148ab42f1b8e971d7e07007ee67e0a3
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/24-b-tree-index-faults.md
@@ -0,0 +1,68 @@
+---
+title: btree 索引故障情况下应对策略
+summary: btree 索引故障情况下应对策略
+author: Guo Huan
+date: 2021-05-24
+---
+
+# btree 索引故障情况下应对策略
+
+## 问题现象
+
+偶发索引丢失错误，报错如下。
+
+```
+ERROR: index 'xxxx_index' contains unexpected zero page
+或
+ERROR: index 'pg_xxxx_index' contains unexpected zero page
+或
+ERROR: compressed data is corrupt
+```
+
+## 原因分析
+
+该类错误是因为索引发生故障导致的，可能引发故障的原因如下：
+
+- 由于软件bug或者硬件原因导致的索引不再可用。
+- 索引包含许多空的页面或者几乎为空的页面。
+- 并发执行DDL过程中，发生了网络闪断故障
+- 创建并发索引时失败，遗留了一个失效的索引，这样的索引无法被使用。
+- 执行DDL或者DML操作时，网络出现故障。
+
+## 处理办法
+
+执行REINDEX命令进行索引重建。
+
+1. 以操作系统用户omm登录主机。
+
+2. 使用如下命令连接数据库。
+
+   ```bash
+   gsql -d mogdb -p 8000 -r
+   ```
+
+3. 重建索引。
+
+   - 如果进行DDL或DML操作时，因软硬件故障导致索引问题，请执行如下命令重建表索引。
+
+     ```
+     REINDEX TABLE tablename;
+     ```
+
+   - 如果错误中提示是xxxx_index，其中xxxx代表用户表名。请执行如下命令之一重建表的索引。
+
+     ```
+     REINDEX INDEX indexname;
+     ```
+
+     或者
+
+     ```
+     REINDEX TABLE tablename;
+     ```
+
+   - 如果错误中提示pg_xxxx_index，说明是系统表索引存在问题。请执行如下命令重建表索引。
+
+     ```
+     REINDEX SYSTEM databasename;
+     ```
diff --git a/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/3-standby-node-in-the-need-repair-state.md b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/3-standby-node-in-the-need-repair-state.md
new file mode 100644
index 0000000000000000000000000000000000000000..a4b1581bb9020724cb3fb173d5f78f34fca22e96
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/3-standby-node-in-the-need-repair-state.md
@@ -0,0 +1,20 @@
+---
+title: 备机处于need repair(WAL)状态问题
+summary: 备机处于need repair(WAL)状态问题
+author: Guo Huan
+date: 2021-05-24
+---
+
+# 备机处于need repair(WAL)状态问题
+
+## 问题现象
+
+MogDB备机出现Standby Need repair(WAL)故障。
+
+## 原因分析
+
+因网络故障、磁盘满等原因造成主备实例连接断开，主备日志不同步，导致数据库在启动时异常。
+
+## 处理分析
+
+通过gs_ctl build -D 命令对故障节点进行重建，具体的操作方法请参见MogDB工具参考中的[build参数](4-gs_ctl#build)。
diff --git a/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/4-insufficient-memory.md b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/4-insufficient-memory.md
new file mode 100644
index 0000000000000000000000000000000000000000..9aa3a97309997444a603cf97d071f34cbce70e4f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/4-insufficient-memory.md
@@ -0,0 +1,20 @@
+---
+title: 内存不足问题
+summary: 内存不足问题
+author: Guo Huan
+date: 2021-05-24
+---
+
+# 内存不足问题
+
+## 问题现象
+
+客户端或日志里出现错误: memory usage reach the max_dynamic_memory。
+
+## 原因分析
+
+出现内存不足可能因GUC参数max_process_memory值设置较小相关，该参数限制一个MogDB实例可用最大内存。
+
+## 处理分析
+
+通过工具gs_guc适当调整max_process_memory参数值。注意需重启实例生效。
diff --git a/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/5-service-startup-failure.md b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/5-service-startup-failure.md
new file mode 100644
index 0000000000000000000000000000000000000000..22902da010d6dfc702bb53e5d48b7a81785a9b8a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/5-service-startup-failure.md
@@ -0,0 +1,88 @@
+---
+title: 服务启动失败
+summary: 服务启动失败
+author: Guo Huan
+date: 2021-05-24
+---
+
+# 服务启动失败
+
+## 问题现象
+
+服务启动失败。
+
+## 原因分析
+
+- 配置参数不合理，数据库因系统资源不足，或者配置参数不满足内部约束，启动失败。
+- 由于部分数据节点状态不正常，导致数据库启动失败。
+- 目录权限不够。例如对/tmp目录、数据库数据目录的权限不足。
+- 配置的端口已经被占用。
+- 开启了系统防火墙导致数据库启动失败。
+- 组成数据库的各台机器之间需要正确建立互信关系，在互信关系出现异常的情况下，数据库将无法启动。
+
+## 处理办法
+
+- 确认是否由于参数配置不合理导致系统资源不足或不满足内部约束启动失败。
+
+  - 登录启动失败的节点，检查运行日志确认是否因资源不足启动失败或配置参数不满足内部约束。例如出现Out of memory的错误，或如下错误提示均为资源不足启动失败或配置参数不满足内部约束。
+
+    ```bash
+    FATAL: hot standby is not possible because max_connections = 10 is a lower setting than on the master server (its value was 100)
+    ```
+
+  - 检查GUC参数配置的合理性。例如，shared_buffers、effective_cache_size、 bulk_write_ring_size等消耗资源过大的参数；或max_connections等增加后不容易减少的参数。 GUC参数的查看及设置方法，详情请参见配置运行参数。
+
+- 确认是否由于实例状态不正常，导致数据库启动失败。 通过gs_om -t status -detail工具，查询当前数据库各主备机实例的状态。
+
+  - 如果某一节点上的所有实例都异常，请进行主机替换。
+
+  - 如果发现某一实例状态为Unknown、Pending和Down的状态，则以数据库用户登录到状态不正常的实例所在节点，查看该实例的日志检查状态异常的原 因。例如：
+
+    ```bash
+    2014-11-27 14:10:07.022 CST 140720185366288 FATAL:  database "mogdb" does not exist 2014-11-27 14:10:07.022 CST 140720185366288 DETAIL:  The database subdirectory "base/ 13252" is missing.
+    ```
+
+    如果日志中出现上面这种报错信息，则说明该数据节点的数据目录文件遭到破坏，该实例无法执行正常查询，需要进行替换实例操作。
+
+- 目录权限不够处理办法。例如，对/tmp目录、数据库数据目录的权限不足。
+
+  - 根据错误提示，确认权限不足的目录名称。
+  - 使用chmod命令修改目录权限使其满足要求。对于/tmp目录，数据库用户需要具有读写权限。对于数据库数据目录，请参考权限无问题的同类目录进行设置。
+
+- 确认是否由于配置的端口已经被占用，导致数据库启动失败。
+
+  - 登录启动失败的节点，查看实例进程是否存在。
+
+  - 如果实例进程不存在，则可以通过查看该实例的日志来检查启动异常的原因。例如：
+
+     ```bash
+    2014-10-17 19:38:23.637 CST 139875904172320 LOG:  could not bind IPv4 socket at the 0 time: Address already in use 2014-10-17 19:38:23.637 CST 139875904172320 HINT:  Is another postmaster already running on port 40005? If not, wait a few seconds and retry.
+    ```
+
+    如果日志中出现上面这种报错信息，则说明该数据节点的TCP端口已经被占用，该实例无法正常启动。
+
+    ```bash
+    2015-06-10 10:01:50 CST 140329975478400 [SCTP MODE] WARNING: (sctp bind)         bind(socket=9, [addr:0.0.0.0,port:1024]):Address already in use  --  attempt 10/10 2015-06-10 10:01:50 CST 140329975478400 [SCTP MODE] ERROR: (sctp bind)   Maximum bind() attempts. Die now...
+    ```
+
+    如果日志中出现上面这种报错信息，则说明该数据节点的SCTP端口已经被占用，该实例无法正常启动。
+
+- 通过sysctl -a查看net.ipv4.ip_local_port_range，如果该实例配置的端口在系统随机占用端口号的范围内，则可以修改系统随机占用端口号的范围，确保xml文件中所有实例端口号均不在这个范围内。检查某个端口是否被占用的命令如下。
+
+  ```shell
+  netstat -anop | grep 端口号
+  ```
+
+  示例如下。
+
+  ```
+  [root@MogDB36 ~]# netstat -anop | grep 15970
+  tcp        0      0 127.0.0.1:15970         0.0.0.0:*               LISTEN      3920251/mogdb      off (0.00/0/0)
+  tcp6       0      0 ::1:15970               :::*                    LISTEN      3920251/mogdb      off (0.00/0/0)
+  unix  2      [ ACC ]     STREAM     LISTENING     197399441 3920251/mogdb      /tmp/.s.PGSQL.15970
+  unix  3      [ ]         STREAM     CONNECTED     197461142 3920251/mogdb      /tmp/.s.PGSQL.15970
+  ```
+
+- 确认是否是由于开启了系统防火墙导致数据库启动失败。
+
+- 确认是否由于互信关系出现异常，导致数据库无法启动。 重新配置实例中各台机器的互信关系解决此问题。
diff --git a/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/6-error-no-space-left-on-device-is-displayed.md b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/6-error-no-space-left-on-device-is-displayed.md
new file mode 100644
index 0000000000000000000000000000000000000000..bb30c4dd6bc9844bc6a0afaae3197d4f634d05c6
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/6-error-no-space-left-on-device-is-displayed.md
@@ -0,0 +1,64 @@
+---
+title: 出现“Error:No space left on device”提示
+summary: 出现“Error:No space left on device”提示
+author: Guo Huan
+date: 2021-05-24
+---
+
+# 出现“Error:No space left on device”提示
+
+## 问题现象
+
+在数据库使用过程中，出现如下错误提示。
+
+```
+Error:No space left on device
+```
+
+## 原因分析
+
+磁盘空间不足造成此提示信息。
+
+## 处理办法
+
+- 使用如下命令查看磁盘占用情况。显示信息如下，其中Avail列表示各磁盘可用的空间，Use%列表示已使用的磁盘空间百分比。
+
+  ```
+  [root@openeuler123 mnt]# df -h
+  Filesystem                  Size  Used Avail Use% Mounted on
+  devtmpfs                    255G     0  255G   0% /dev
+  tmpfs                       255G   35M  255G   1% /dev/shm
+  tmpfs                       255G   57M  255G   1% /run
+  tmpfs                       255G     0  255G   0% /sys/fs/cgroup
+  /dev/mapper/openeuler-root  196G  8.8G  178G   5% /
+  tmpfs                       255G  1.0M  255G   1% /tmp
+  /dev/sda2                   9.8G  144M  9.2G   2% /boot
+  /dev/sda1                    10G  5.8M   10G   1% /boot/efi
+  ```
+
+  由于业务数据的增长情况不同，对剩余磁盘空间的要求不同。建议如下：
+
+  - 持续观察磁盘空间增长情况，确保剩 余空间满足一年以上的增长要求。
+  - 数据目录所在磁盘已使用空间&gt;60% 则进行空间清理或者扩容。
+
+- 使用如下命令查看数据目录大小。
+
+  ```bash
+   du --max-depth=1 -h /mnt/
+  ```
+
+  显示如下信息，其中第一列表示目录或文件的大小，第二列是“/mnt/”目录下的所有子目录或者文件。
+
+  ```
+  [root@MogDB36 mnt]# du --max-depth=1 -h /mnt
+  83G /mnt/data3
+  71G /mnt/data2
+  365G    /mnt/data1
+  518G    /mnt
+  ```
+
+- 清理磁盘空间。 建议定期将审计日志备份到其他存储设备，推荐的日志保留时长为一个月。pg_log存放数据库各进程的运行日志，运行日志可以帮助数据库管理员定位数据库的问题。如果每日查看错误日志并及时处理错误，则可以删除这些日志。
+
+- 清理无用的数据。 通过先备份使用频率较低或者一定时间以前的数据至更低成本的存储介质中，然后清理这些已备份的数据来获取更多的磁盘空间。
+
+- 如果以上方法无法清理出足够的空间，请对磁盘空间进行扩容。
diff --git a/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/7-after-you-run-the-du-command.md b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/7-after-you-run-the-du-command.md
new file mode 100644
index 0000000000000000000000000000000000000000..7a4ccf7efca7b5ea17539741ac2decb6eca32d94
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/7-after-you-run-the-du-command.md
@@ -0,0 +1,32 @@
+---
+title: 在XFS文件系统中，使用du命令查询数据文件大小大于文件实际大小
+summary: 在XFS文件系统中，使用du命令查询数据文件大小大于文件实际大小
+author: Guo Huan
+date: 2021-05-24
+---
+
+# 在XFS文件系统中，使用du命令查询数据文件大小大于文件实际大小
+
+## 问题现象
+
+在数据库使用过程中，通过如下du命令查询数据文件大小，查询结果大于文件实际的大小。
+
+```bash
+ du -sh file
+```
+
+## 原因分析
+
+XFS文件系统有预分配机制，预分配的大小由参数allocsize确定。du命令显示的文件大小包括该预分配的磁盘空间。
+
+## 处理办法
+
+- 将XFS文件系统挂载选项allocsize设置为默认值（64KB）减缓该问题。
+
+- 使用du命令时，增加-apparent-size选项，查看实际文件的大小。
+
+  ```bash
+  du -sh file --apparent-size
+  ```
+
+- XFS文件系统有回收预分配空间的机制，文件系统可以通过回收文件预分配的空间，使du命令显示为实际文件的大小。
diff --git a/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/8-file-is-damaged-in-the-xfs-file-system.md b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/8-file-is-damaged-in-the-xfs-file-system.md
new file mode 100644
index 0000000000000000000000000000000000000000..412aba3162613f7aa951f84235922364d84aca37
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/8-file-is-damaged-in-the-xfs-file-system.md
@@ -0,0 +1,22 @@
+---
+title: 在XFS文件系统中，出现文件损坏
+summary: 在XFS文件系统中，出现文件损坏
+author: Guo Huan
+date: 2021-05-24
+---
+
+# 在XFS文件系统中，出现文件损坏
+
+## 问题现象
+
+在数据库使用过程中，有极小的概率出现XFS文件系统的报错 (Input/Output error , structure needs cleaning)。
+
+## 原因分析
+
+此为XFS文件系统问题。
+
+## 处理办法
+
+首先尝试umount/mount对应文件系统，重试看是否可以规避此问题。
+
+如果问题重现，则需要参考文件系统相应的文档请系统管理员对文件系统进行修复，例如xfs_repair。文件系统成功修复后，请使用gs_ctl build命令来修复文件受损的数据节点。
diff --git a/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/9-primary-node-is-hung-in-demoting.md b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/9-primary-node-is-hung-in-demoting.md
new file mode 100644
index 0000000000000000000000000000000000000000..b02d1697609a8fcf545392c8a5f65a845d7aae3d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-cases/9-primary-node-is-hung-in-demoting.md
@@ -0,0 +1,24 @@
+---
+title: switchover操作时，主机降备卡住
+summary: switchover操作时，主机降备卡住
+author: Guo Huan
+date: 2021-05-24
+---
+
+# switchover操作时，主机降备卡住
+
+## 问题现象
+
+一主多备模式下，系统资源不足时，发生switchover，出现主机降备时卡住。
+
+## 原因分析
+
+当系统资源不足时，无法创建第三方管理线程，导致其管理的子线程无法退出，出现主机降备时卡住。
+
+## 处理办法
+
+需要执行以下命令终止主机进程，使备机正常升主。确定为上述场景时执行以下操作，不是上述场景时请勿按照本方法执行。
+
+```bash
+ kill -9 PID
+```
diff --git a/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-methods.md b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-methods.md
new file mode 100644
index 0000000000000000000000000000000000000000..a92136774baadf1cf71f050d4a3c6301816a9d5d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/common-faults-and-identification/common-fault-locating-methods.md
@@ -0,0 +1,283 @@
+---
+title: 常见故障定位手段
+summary: 常见故障定位手段
+author: Guo Huan
+date: 2021-05-24
+---
+
+# 常见故障定位手段
+
+## 操作系统故障定位手段
+
+查询状态时，显示一个节点上所有实例都不正常时，可能是操作系统发生了故障。
+
+可以通过如下方法确定操作系统是否存在问题：
+
+- 通过SSH或者其它远程登录工具登录该节点。如果连接失败，请尝试通过ping发包检查网络状态。
+
+  - 如果ping操作没有回复，则表明这台机器可能存在网络连接故障、处于宕机状态或者正处于重启状态。
+
+    如果操作系统内核发生panic引起系统崩溃，系统重新启动时间较慢，需经过较长时间(大约20分钟)才能重启。建议每5分钟尝试连接一次，20分钟后不能连接成功，则表明这台机器已宕机或网络连接有问题，需要管理员到现场进行检查处理。
+
+  - 如果网络可以ping通，但在SSH登入时卡住或登入后不能执行任何命令，通常是由系资源不足（如CPU或IO资源过载）引起的机器不响应外部连接。建议重试几次。如果5分钟内仍不能成功，需要管理员到现场进行检查处理。
+
+- 可以远程登录节点，但在执行操作时，响应缓慢，需要检查系统运行情况后，进行进一步处理。例如，收集系统信息、确定系统版本、硬件、参数设置及登录用户情况。下面列出一些常用命令供参考。
+
+  - `who`命令查看当前在线用户。
+
+    ```bash
+    [root@MogDB36 ~]# who
+    root     pts/0        2020-11-07 16:32 (10.70.223.238)
+    wyc      pts/1        2020-11-10 09:54 (10.70.223.222)
+    root     pts/2        2020-10-10 14:20 (10.70.223.238)
+    root     pts/4        2020-10-09 10:14 (10.70.223.233)
+    root     pts/5        2020-10-09 10:14 (10.70.223.233)
+    root     pts/7        2020-10-31 17:03 (10.70.223.222)
+    root     pts/9        2020-10-20 10:03 (10.70.220.85)
+    ```
+
+  - `cat /etc/openEuler-release`和`uname -a`命 令检查系统的版本和内核信息。
+
+    ```bash
+    [root@MogDB36 ~]# cat /etc/openEuler-release
+    openEuler release 20.03 (LTS)
+    [root@MogDB36 ~]# uname -a
+    Linux MogDB36 4.19.90-2003.4.0.0036.oe1.aarch64 #1 SMP Mon Mar 23 19:06:43 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux
+    [root@MogDB36 ~]#
+    ```
+
+  - `sysctl -a`命令（需要root用户执行）和`cat /etc/sysctl.conf`命令获得系统参数信息。
+
+  - `cat /proc/cpuinfo`和`cat /proc/meminfo`获得CPU和内存信息。
+
+    ```bash
+    [root@MogDB36 ~]# cat /proc/cpuinfo
+    processor   : 0
+    BogoMIPS    : 200.00
+    Features    : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm jscvt fcma dcpop asimddp asimdfhm
+    CPU implementer : 0x48
+    CPU architecture: 8
+    CPU variant : 0x1
+    CPU part    : 0xd01
+    CPU revision    : 0
+    [root@MogDB36 ~]# cat /proc/meminfo
+    MemTotal:       534622272 kB
+    MemFree:        253322816 kB
+    MemAvailable:   369537344 kB
+    Buffers:         2429504 kB
+    Cached:         253063168 kB
+    SwapCached:            0 kB
+    Active:         88570624 kB
+    Inactive:       171801920 kB
+    Active(anon):    4914880 kB
+    Inactive(anon): 67011456 kB
+    Active(file):   83655744 kB
+    Inactive(file): 104790464 kB
+    ```
+
+  - `top -H”命令查看CPU的使用情况，确定是否因为某个进程导致CPU使用率过高。如果存在这种情况，通过gdb或gstack打印该程序堆栈，观察是否该程序处于死循环逻辑。
+
+  - `iostat -x 1 3”命令查看IO的使用情况，确定是否当前磁盘的IO处于饱和状态。查看当前运行的执行作业情况，决定是否对占用较多IO的执行作业进行处理。
+
+  - `vmstat 1 3`命令查看当前系统中内存的消耗情况，结合`top`命令获得消耗内存较多的进程，处于超出预期的状态。
+
+  - 以root用户查看操作系统日志信息(/var/log/messages)或dmseg信息，检查操作系统是否发生过异常错误。
+
+  - 操作系统的watchdog是为了保证OS系统正常运行，或者从死循环，死锁等状态退出的一种机制，如果watchdog超时(一般默认值为60s)，系统将会复位。
+
+## 网络故障定位手段
+
+在数据库正常工作的情况下，网络层对上层用户是透明的，但数据库在长期运行时，可能会由于各种原因导致出现网络异常或错误。常见的因网络故障引发的异常有：
+
+- 数据库启动失败，报网络错误。
+- 状态异常，如：节点上所有的实例都是UnKnown或者所有主机都切换为备机。
+- 网络连接建立失败。
+- 对数据库执行SQL操作时，报网络异常中断的错误。
+- 连接数据库或执行查询时发生进程停止响应。数据库出现了网络故障后，主要通过使用Linux系统提供的网络相关命令工具 (ping、ifconfig、netstat、lsof等)，进程堆栈查看工具(gdb、gstack)，结合数据库的 日志信息，进行分析定位。本节通过举例介绍常见的网络问题，并进行基本的分析定位。
+
+常见故障问题如下：
+
+- 启动失败，报网络错误
+
+  **问题现象1**：日志中存在如下错误信息。可能是端口被其他进程侦听。
+
+  ```bash
+  LOG: could not bind socket at the 10 time, is another postmaster already running on port 54000?
+  ```
+
+  **处理办法**：执行如下命令查看侦听该端口的进程。端口号请根据实际端口号替换。
+
+  ```bash
+  [root@MogDB36 ~]# netstat -anop | grep 15970
+  tcp        0      0 127.0.0.1:15970         0.0.0.0:*               LISTEN      3920251/mogdb      off (0.00/0/0)
+  tcp6       0      0 ::1:15970               :::*                    LISTEN      3920251/mogdb      off (0.00/0/0)
+  unix  2      [ ACC ]     STREAM     LISTENING     197399441 3920251/mogdb      /tmp/.s.PGSQL.15970
+  unix  3      [ ]         STREAM     CONNECTED     197461142 3920251/mogdb      /tmp/.s.PGSQL.15970
+
+  ```
+
+  根据查询结果，强行停止正在占用端口的进程或者更改数据库侦听端口。
+
+  **问题现象2**：使用gs_om -t status -detail 查询状态，如果显示主备间连接未建立。
+
+  **处理办法**：在openEuler操作系统下，使用systemctl status firewalld.service命令，查看节点上是否 开启了防火墙。如果开启，使用systemctl stop firewalld.service关闭防火墙。
+
+  ```bash
+  [root@MogDB36 mnt]# systemctl status firewalld.service
+  ●firewalld.service - firewalld - dynamic firewall daemon
+     Loaded: loaded (/usr/lib/systemd/system/firewalld.service; disabled; vendor preset: enabled)
+     Active: inactive (dead)
+       Docs: man:firewalld(1)
+  ```
+
+  操作系统不同，命令可能不同，使用对应操作系统命令查看修改。
+
+- 数据库状态异常
+
+  **问题现象**：某一节点上出现如下问题：
+
+  - 所有实例都是UnKnown。
+  - 所有主实例都切换成了备实例。
+  - 查询中出现大量Connection reset by peer，Connection timed out等报错信息。
+
+  **处理办法**
+
+  - 如果ssh不能连接故障机器，在其他机器上使用Ping命令向该机器发数据包。如果可以Ping通，说明可能是该机器上的资源（内存、CPU、磁盘）耗尽导致不能建立连接。
+
+  - 如果ssh可以连接该机器，尝试执行查询，并每隔1s执行/sbin/ifconfig eth?（?代表数字，表示第几个网卡）命令，查看如下信息中的dropped及errors值的变化情况， 如果增长迅速，可能是网卡或网卡驱动故障。
+
+    ```bash
+    [root@MogDB36 ~]# ifconfig enp125s0f0
+    enp125s0f0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
+            inet 10.90.56.36  netmask 255.255.255.0  broadcast 10.90.56.255
+            inet6 fe80::7be7:8038:f3dc:f916  prefixlen 64  scopeid 0x20<link>
+            ether 44:67:47:7d:e6:84  txqueuelen 1000  (Ethernet)
+            RX packets 129344246  bytes 228050833914 (212.3 GiB)
+            RX errors 0  dropped 647228  overruns 0  frame 0
+            TX packets 96689431  bytes 97279775245 (90.5 GiB)
+            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
+    ```
+
+  - 检查如下参数设置是否正确。
+
+    ```bash
+    net.ipv4.tcp_retries1 = 3
+    net.ipv4.tcp_retries2 = 15
+    ```
+
+- 网络连接建立失败
+
+  **问题现象1**： 节点连接其他节点失败，日志中报出“ Connection refused ”错误。
+
+  **处理办法**：
+
+  - 查看端口是否配置错误，导致连接时使用的端口并非对方侦听的端口。查看报错节点配置文件postgresql.conf记录端口号与对方侦听的端口就号是否一致。
+  - 查看对方端口侦听是否正常（可以使用`netstat -anp”命令）。
+  - 查看对方进程是否存在。
+
+  **问题现象2**：对数据库执行SQL操作时，获取连接描述符失败，报错如下。
+
+    ```sql
+    WARNING:  29483313: incomplete message from client:4905,9
+    WARNING:  29483313: failed to receive connDefs at the time:1.
+    ERROR:  29483313: failed to get pooled connections
+    ```
+
+  在日志中，找到上面的错误，并向上查看一段日志内容，可以看到详细的错误信息，常见的错误如下所示，主要是由于主备信息不正确导致。
+
+    ```sql
+    FATAL:  dn_6001_6002: can not accept connection in pending mode.
+    FATAL:  dn_6001_6002: the database system is starting up
+    FATAL:  dn_6009_6010: can not accept connection in standby mode.
+    ```
+
+  **处理办法：**
+
+  - 使用gs_om -t status -detail查询状态，确认是否发生过主备切换。重置实例状态。
+  - 此外，需要查看连接失败的节点是否发生了core或者重启。通过om日志可以查看到是否发生了重启。
+
+- 对数据库执行 SQL 操作时，报网络异常中断的错误
+
+  **问题现象1**：查询执行失败，报错信息如下。
+
+    ```sql
+    ERROR:  dn_6065_6066: Failed to read response from Datanodes. Detail: Connection reset by peer. Local: dn_6065_6066 Remote: dn_6023_6024
+    ERROR: Failed to read response from Datanodes Detail: Remote close socket unexpectedly
+    ERROR: dn_6155_6156: dn_6151_6152: Failed to read vector response from Datanodes
+    ```
+
+  连接建立失败，报错信息如下。
+
+    ```sql
+    ERROR:  Distribute Query unable to connect 10.145.120.79:14600 [Detail:stream connect connect() fail: Connection timed out
+    ERROR: Distribute Query unable to connect 10.144.192.214:12600 [Detail:receive accept response fail: Connection timed out
+    ```
+
+  **处理办法**：
+
+  1. 使用gs_check检查网络配置是否符合标准。详细参考《参考指南》中“工具参考 &gt; 服务端工具 &gt; [gs_check](1-gs_check)”章节中对network的检查。
+  2. 查看是否有进程发生core或重启，以及主备切换。
+  3. 如果不存在上述问题，可以联系网络技术人员做具体分析。
+
+## 磁盘故障定位手段
+
+常见的磁盘故障是磁盘空间不足、磁盘出现坏块、磁盘未挂载等。 部分磁盘故障会导致文件系统损坏，例如磁盘未挂载，数据库管理自动定期执行磁盘检测时会识别故障并将实例停止，查看数据库状态时对应实例状态异常；部分磁盘故障不会导致文件系统损坏，例如磁盘空间不足，数据库管理无法检测到，服务进程访问到故障磁盘会异常退出，例如数据库无法启动、checksum校验不对、页面读写失败、页面校验错误等。
+
+- 对于会导致文件系统损坏的故障，查看状态会显示对应实例状态持续为Unknown，定位方法如下：
+
+  - 查看日志，日志中会有类似 “data path disc writable test failed”异常，说明文件系统已损坏。
+
+  - 文件系统损坏可能是磁盘未挂载，通过ls -l可以看到该磁盘对应的目录权限异常，如下：
+
+  - 也可能是磁盘出现坏块，然后操作系统将文件系统保护起来，拒绝读写，可以使 用磁盘坏块检查工具如badblocks检查磁盘是否有坏块，如下
+
+    ```bash
+    [root@openeuler123 mnt]# badblocks /dev/sdb1 -s -v
+    Checking blocks 0 to 2147482623
+    Checking for bad blocks (read-only test): done
+    Pass completed, 0 bad blocks found. (0/0/0 errors)
+    ```
+
+- 对于不会导致文件系统损坏的故障，服务进程访问到故障磁盘会异常退出，定位方法如下。
+
+  查看日志。日志中会有文件读写错误，例如“No space left on device”、“ invalid page header n block 122838 of relation base/16385/152715”。 文件读写错误可能是磁盘空间不足，通过df -h可以看到磁盘空间已达100%，如下。
+
+  ```
+  [root@openeuler123 mnt]# df -h
+  Filesystem                  Size  Used Avail Use% Mounted on
+  devtmpfs                    255G     0  255G   0% /dev
+  tmpfs                       255G   35M  255G   1% /dev/shm
+  tmpfs                       255G   57M  255G   1% /run
+  tmpfs                       255G     0  255G   0% /sys/fs/cgroup
+  /dev/mapper/openeuler-root  196G  8.8G  178G   5% /
+  tmpfs                       255G  1.0M  255G   1% /tmp
+  /dev/sda2                   9.8G  144M  9.2G   2% /boot
+  /dev/sda1                    10G  5.8M   10G   1% /boot/efi
+  /dev/mapper/openeuler-home  1.5T   69G  1.4T   5% /home
+  tmpfs                        51G     0   51G   0% /run/user/0
+  tmpfs                        51G     0   51G   0% /run/user/1004
+  /dev/sdb1                   2.0T  169G  1.9T   9% /data
+  ```
+
+## 数据库故障定位手段
+
+- 日志。数据库日志记录了数据库服务端启动、运行或停止时出现的问题，当数据库在启动、运行或停止的过程中出现问题时，数据库用户可以通过运行日志快速分析问题的产生原因，并根据不同的原因采取相应的处理方法，尽可能地解决问题。
+
+- 视图。数据库提供了许多视图，用于展示数据库的内部状态，在定位故障时，经常使用的视图如下：
+
+  - pg_stat_activity，用于查询当前实例上各个session的状态。
+  - pg_thread_wait_status，用于查询该实例上各个线程的等待事件。
+  - pg_locks，用于查询当前实例上的锁状态。
+
+- CORE文件。数据库相关进程在运行过程中可能会因为各种意外情况导致数据库崩溃 （Coredump），而崩溃时产生的core文件对于迅速定位程序崩溃的原因及位置非常重要。如果进程运行时出现Coredump现象，建议立即收集core文件便于分析、定位故障。
+
+  - 对性能有一定的影响，尤其是进程频繁异常时对性能的影响更大。
+
+  - core文件会占用磁盘空间。因此，当检查到core文件产生后，应及时解决以避免对操作系统带来更严重的影响。操作系统自带core dump机制。开启后，系统中所有出现Coredump问题时都会生成core文件，对操作系统带来性能和磁盘占用的影响
+
+  - 设置core文件生成路径。修改/proc/sys/kernel/core_pattern内容。
+
+    ```bash
+    [root@openeuler123 mnt]# cat /proc/sys/kernel/core_pattern
+    /data/jenkins/workspace/MogDBInstall/dbinstall/cluster/corefile/core-%e-%p-%t
+    ```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/1-1-stored-procedure.md b/product/zh/docs-mogdb/v3.0/developer-guide/1-1-stored-procedure.md
new file mode 100644
index 0000000000000000000000000000000000000000..ddda5e0d1e6dd44e4587a68c6022a9605978d828
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/1-1-stored-procedure.md
@@ -0,0 +1,16 @@
+---
+title: 存储过程
+summary: 存储过程
+author: Guo Huan
+date: 2021-03-04
+---
+
+# 存储过程
+
+商业规则和业务逻辑可以通过程序存储在MogDB中，这个程序就是存储过程。
+
+存储过程是SQL和PL/pgSQL的组合。存储过程使执行商业规则的代码可以从应用程序中移动到数据库。从而，代码存储一次能够被多个程序使用。
+
+存储过程的创建及调用办法请参考[CREATE PROCEDURE](53-CREATE-PROCEDURE)。
+
+[用户自定义函数](user-defined-functions)一节所提到的PL/pgSQL语言创建的函数与存储过程的应用方法相通。具体介绍请参看[PL/pgSQL-SQL过程语言](1-1-plpgsql-overview)章节，除非特别声明，否则其中内容通用于存储过程和用户自定义函数。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/1-AI-features-overview.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/1-AI-features-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..1456527e99996f3bf70639c5be5ad57c13543188
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/1-AI-features-overview.md
@@ -0,0 +1,13 @@
+---
+title: 概述
+summary: 概述
+author: Guo Huan
+date: 2021-05-19
+---
+
+# 概述
+
+人工智能技术最早可以追溯到上世纪50年代，甚至比数据库系统的发展历史还要悠久。但是，由于各种各样客观因素的制约，在很长的一段时间内，人工智能技术并没有得到大规模的应用，甚至还经历了几次明显的低谷期。到了近些年，随着信息技术的进一步发展，从前限制人工智能发展的因素已经逐渐减弱，所谓的ABC（AI、Big data、Cloud Computing）技术也随之而诞生。AI与数据库结合是近些年的行业研究热点，我们的数据库团队较早地参与了该领域的探索，并取得了阶段性的成果。AI特性子模块相对数据库其他组件更为独立，名为dbmind，大致可分为AI4DB与DB4AI两个部分。
+
+- AI4DB就是指用人工智能技术优化数据库的性能，从而获得更好的执行表现；也可以通过人工智能的手段实现自治、免人工运维等。主要包括自调优、自诊断、自安全、自运维和自愈等子领域；
+- DB4AI就是指打通数据库到人工智能应用的端到端流程，统一人工智能技术栈，达到开箱即用、高性能、节约成本等目的。例如通过SQL-like语句使用推荐系统、图像检索、时序预测等功能，充分发挥高斯数据库高并行、列存储等优势。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-1-ai-query-time-forecasting-overview.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-1-ai-query-time-forecasting-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..a87a0e60aa54f25f423bbbd0eeb289de1c775248
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-1-ai-query-time-forecasting-overview.md
@@ -0,0 +1,12 @@
+---
+title: 概述
+summary: 概述
+author: Guo Huan
+date: 2021-05-19
+---
+
+# 概述
+
+Predictor是基于机器学习且具有在线学习能力的查询时间预测工具。通过不断学习数据库内收集的历史执行信息，实现计划的执行时间预测功能。
+
+本特性需要拉起python进程AIEngine，用于模型的训练和推理。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-2-environment-deployment.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-2-environment-deployment.md
new file mode 100644
index 0000000000000000000000000000000000000000..1ef4248e7330b9a4866e85dda479d17b1c24a56c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-2-environment-deployment.md
@@ -0,0 +1,213 @@
+---
+title: 环境部署
+summary: 环境部署
+author: Guo Huan
+date: 2021-05-19
+---
+
+# 环境部署
+
+<br/>
+
+## 前提条件
+
+需要保证MogDB处于正常状态，用户通过身份验证成功登录MogDB；用户执行的SQL语法正确无报错，且不会导致数据库异常等；历史性能数据窗口内MogDB并发量稳定，表结构、表数量不变，数据量无突变，涉及查询性能的guc参数不变；进行预测时，需要保证模型已训练并收敛；AiEngine运行环境稳定。
+
+<br/>
+
+## 请求样例
+
+AiEngine进程与内核进程使用https发送请求进行通信，请求样例如下：
+
+```bash
+curl -X POST -d '{"modelName":"modelname"}' -H 'Content-Type: application/json' 'https://IP-address:port/request-API'
+```
+
+**表 1** ： AI-Engine对外接口
+
+| Request-API    | 功能                   |
+| :------------- | :--------------------- |
+| /check         | 检查模型是否被正常拉起 |
+| /configure     | 设置模型参数           |
+| /train         | 模型训练               |
+| /track_process | 查看模型训练日志       |
+| /setup         | 加载历史模型           |
+| /predict       | 模型预测               |
+
+<br/>
+
+## 证书生成
+
+使用此功能前需使用openssl工具生成通信双方认证所需的证书，保证通信安全。
+
+1. 搭建证书生成环境，证书文件保存路径为$GAUSSHOME/CA。
+
+   -拷贝证书生成脚本及相关文件
+
+   ```bash
+   cp path_to_predictor/install/ssl.sh $GAUSSHOME/
+   cp path_to_predictor/install/ca_ext.txt $GAUSSHOME/
+   ```
+
+   -copy 配置文件openssl.cnf到$GAUSSHOME路径下
+
+   ```bash
+    cp $GAUSSHOME/share/om/openssl.cnf  $GAUSSHOME/
+   ```
+
+   -修改openssl.conf配置参数
+
+   ```bash
+   dir  = $GAUSSHOME/CA/demoCA
+   default_md      = sha256
+   ```
+
+   -至此证书生成环境准备完成
+
+2. 生成证书及密钥。
+
+   ```bash
+   cd $GAUSSHOME
+   sh ssl.sh
+   ```
+
+   -根据提示设置密码，假如为Test@123：
+
+   -密码要求至少3种不同类型字符，长度至少为8位
+
+   ```bash
+   Please enter your password:
+   ```
+
+   -根据提示输入选项：
+
+   ```bash
+   Certificate Details:
+           Serial Number: 1 (0x1)
+           Validity
+               Not Before: May 15 08:32:44 2020 GMT
+               Not After : May 15 08:32:44 2021 GMT
+           Subject:
+               countryName               = CN
+               stateOrProvinceName       = SZ
+               organizationName          = HW
+               organizationalUnitName    = GS
+               commonName                = CA
+           X509v3 extensions:
+               X509v3 Basic Constraints:
+                   CA:TRUE
+   Certificate is to be certified until May 15 08:32:44 2021 GMT (365 days)
+   Sign the certificate? [y/n]:y
+   1 out of 1 certificate requests certified, commit? [y/n]y
+   ```
+
+   -输入拉起AIEngine的IP地址，如IP为127.0.0.1：
+
+   ```bash
+   Please enter your aiEngine IP: 127.0.0.1
+   ```
+
+   -根据提示输入选项：
+
+   ```bash
+   Certificate Details:
+           Serial Number: 2 (0x2)
+           Validity
+               Not Before: May 15 08:38:07 2020 GMT
+               Not After : May 13 08:38:07 2030 GMT
+           Subject:
+               countryName               = CN
+               stateOrProvinceName       = SZ
+               organizationName          = HW
+               organizationalUnitName    = GS
+               commonName                = 127.0.0.1
+           X509v3 extensions:
+               X509v3 Basic Constraints:
+                   CA:FALSE
+   Certificate is to be certified until May 13 08:38:07 2030 GMT (3650 days)
+   Sign the certificate? [y/n]:y
+   1 out of 1 certificate requests certified, commit? [y/n]y
+   ```
+
+   -输入启动MogDB IP地址，如IP为127.0.0.1：
+
+   ```bash
+   Please enter your mogdb IP: 127.0.0.1
+   ```
+
+   -根据提示输入选项：
+
+   ```bash
+   Certificate Details:
+           Serial Number: 3 (0x3)
+           Validity
+               Not Before: May 15 08:41:46 2020 GMT
+               Not After : May 13 08:41:46 2030 GMT
+           Subject:
+               countryName               = CN
+               stateOrProvinceName       = SZ
+               organizationName          = HW
+               organizationalUnitName    = GS
+               commonName                = 127.0.0.1
+           X509v3 extensions:
+               X509v3 Basic Constraints:
+                   CA:FALSE
+   Certificate is to be certified until May 13 08:41:46 2030 GMT (3650 days)
+   Sign the certificate? [y/n]:y
+   1 out of 1 certificate requests certified, commit? [y/n]y
+   ```
+
+   -至此，相关证书及密钥已生成，（$GAUSSHOME/CA）内容如下：
+
+   ![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/environment-deployment-1.png)
+
+<br/>
+
+## 环境准备
+
+1. 将工具代码文件夹拷贝至目标环境
+
+   -假设安装路径为$INSTALL_FOLDER
+
+   -假设目标环境路径为/home/ai_user :
+
+   ```bash
+   scp -r $INSTALL_FOLDER/bin/dbmind/predictor  ai_user@127.0.0.1:path_to_Predictor
+   ```
+
+2. 拷贝CA证书文件夹至aiEngine环境中某路径下：
+
+   ```bash
+   cp -r $GAUSSHOME/CA  ai_user@127.0.0.1:path_to_CA
+   ```
+
+3. 安装predictor/install/requirements(-gpu).txt工具：
+
+   ```bash
+   有GPU：pip install -r requirements-gpu.txt
+   无GPU：pip install -r requirements.txt
+   ```
+
+<br/>
+
+## 拉起AiEngine
+
+1. 切换至aiEngine环境（即拷贝predictor的目标环境 ai_user）：
+
+   设置predictor/python/settings.py 中的相关参数：
+
+   ```bash
+   DEFAULT_FLASK_SERVER_HOST = '127.0.0.1' （aiEngine运行IP地址）
+   DEFAULT_FLASK_SERVER_PORT = '5000' （aiEngine运行端口号）
+   PATH_SSL = "path_to_CA" (CA文件夹路径)
+   ```
+
+2. 运行aiEngine启动脚本：
+
+   ```bash
+   python path_to_Predictor/python/run.py
+   ```
+
+   此时，aiEngine即在相应端口保持拉起状态，等待内核侧时间预测功能的请求指令。
+
+   至此，aiEngine工具部署完成。从内核中发起执行时间预测功能指令步骤，请参考《[使用指导](2-3-usage-guide)》。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-3-usage-guide.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-3-usage-guide.md
new file mode 100644
index 0000000000000000000000000000000000000000..d753bdbad6c16c3333a2cd41320272341629892c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-3-usage-guide.md
@@ -0,0 +1,222 @@
+---
+title: 使用指导
+summary: 使用指导
+author: Guo Huan
+date: 2021-05-19
+---
+
+# 使用指导
+
+<br/>
+
+## 数据收集
+
+1. 打开数据收集。
+
+   a. 设置ActiveSQL operator信息相关参数:
+
+      ```bash
+      enable_resource_track=on
+      resource_track_level=operator
+      enable_resource_record=on
+      resource_track_cost=10（默认值为100000）
+      ```
+
+      > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+      >
+      > - resource_track_cost需设置为小于需要收集的查询总代价，满足条件的信息才能被收集。
+      > - Cgroups功能正常加载。
+
+   b. 信息收集：
+
+      执行业务查询语句。
+
+      查看实时收集数据：
+
+      ```sql
+      select * from gs_wlm_plan_operator_history;
+      ```
+
+      预期：满足resource_track_duration和resource_track_cost的作业被全量收集。
+
+2. 关闭数据收集。
+
+   a. 设置ActiveSQL operator信息相关参数：
+
+      ```bash
+      enable_resource_track=off 或
+      resource_track_level=none 或
+      resource_track_level=query
+      ```
+
+   b. 执行业务查询语句。
+
+      等待三分钟之后查看当前节点上的数据：
+
+      ```sql
+      select * from gs_wlm_plan_operator_info;
+      ```
+
+      预期：所查表和视图无新增数据。
+
+3. 数据持久化保存。
+
+   a. 设置ActiveSQL operator信息相关参数：
+
+      ```bash
+      enable_resource_track=on
+      resource_track_level=operator
+      enable_resource_record=on
+      resource_track_duration=0（默认值为60s）
+      resource_track_cost=10（默认值为100000）
+      ```
+
+      > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+      >
+      > - resource_track_cost需设置为小于需要收集的查询总代价，满足条件的信息才能被收集。
+      > - Cgroups功能正常加载。
+
+   b. 执行业务查询语句。
+
+      等待三分钟之后查看当前节点上的数据：
+
+      ```sql
+      select * from gs_wlm_plan_operator_info;
+      ```
+
+      预期：满足resource_track_duration和resource_track_cost的作业被全量收集。
+
+<br/>
+
+## 模型管理（系统管理员用户）
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 模型管理操作需要在数据库正常的状态下进行。
+
+1. 新增模型：
+
+   INSERT INTO gs_opt_model values('……')；
+
+   示例：
+
+   ```sql
+   INSERT INTO gs_opt_model values('rlstm', 'model_name', 'datname', '127.0.0.1', 5000, 2000, 1, -1, 64, 512, 0 , false, false, '{S, T}', '{0,0}', '{0,0}', 'Text');
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+   >
+   > - 具体模型参数设置请参考[GS_OPT_MODEL](GS_OPT_MODEL)。
+   > - 目前“template_name”列只支持“rlstm”。
+   > - “datname”列请和用于模型使用和训练的数据库保持一致，否则无法使用。
+   > - “model_name”一列需要满足unique约束。
+   > - 其他参数设置见[最佳实践](2-4-best-practices)。
+
+2. 修改模型参数：
+
+   ```sql
+   UPDATE gs_opt_model SET <attribute> = <value> WHERE model_name = <target_model_name>;
+   ```
+
+3. 删除模型：
+
+   ```sql
+   DELETE FROM gs_opt_model WHERE model_name = <target_model_name>;
+   ```
+
+4. 查询现有模型及其状态：
+
+   ```sql
+   SELECT * FROM gs_opt_model;
+   ```
+
+<br/>
+
+## 模型训练（系统管理员用户）
+
+1. 配置/添加模型训练参数：参考模型管理（系统管理员用户）进行模型添加、模型参数修改，来指定训练参数。
+
+   例：
+
+   模型添加：
+
+   ```sql
+   INSERT INTO gs_opt_model values('rlstm', 'default', 'mogdb', '127.0.0.1', 5000, 2000, 1, -1, 64, 512, 0 , false, false, '{S, T}', '{0,0}', '{0,0}', 'Text');
+   ```
+
+   训练参数更新：
+
+   ```sql
+   UPDATE gs_opt_model SET <attribute> = <value> WHERE model_name = <target_model_name>;
+   ```
+
+2. 前提条件为数据库状态正常且历史数据正常收集：
+
+   删除原有encoding数据：
+
+   ```sql
+   DELETE FROM gs_wlm_plan_encoding_table;
+   ```
+
+   进行数据编码，需要指定数据库名：
+
+   ```sql
+   SELECT gather_encoding_info('mogdb');
+   ```
+
+   开始训练：
+
+   ```sql
+   SELECT model_train_opt('rlstm', 'default');
+   ```
+
+3. 查看模型训练状态：
+
+   ```sql
+   SELECT * FROM track_model_train_opt('rlstm', 'default');
+   ```
+
+   返回Tensorboard所用URL：
+
+   ![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/usage-guide-1.png)
+
+   打开URL查看模型训练状态：
+
+   ![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/usage-guide-2.png)
+
+<br/>
+
+## 模型预测
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 模型预测功能需在数据库状态正常、指定模型已被训练且收敛的条件下进行。
+> - 目前，模型训练参数的标签设置中需要包含“S”标签，explain中才可显示“p-time”预测值。 例：INSERT INTO gs_opt_model values('rlstm', 'default', 'mogdb', '127.0.0.1', 5000, 1000, 1, -1, 50, 500, 0 , false, false, '{**S**, T}', '{0,0}', '{0,0}', 'Text');
+
+调用explain接口：
+
+```sql
+explain (analyze on, predictor <model_name>)
+SELECT ...
+```
+
+预期结果：
+
+```bash
+例：Row Adapter  (cost=110481.35..110481.35 rows=100 p-time=99..182 width=100) (actual time=375.158..375.160 rows=2 loops=1)
+其中，“p-time”列为标签预测值。
+```
+
+<br/>
+
+## 其他功能
+
+1. 检查AiEngine是否可连接:
+
+   ```sql
+   mogdb=# select check_engine_status('aiEngine-ip-address',running-port);
+   ```
+
+2. 查看模型对应日志在AiEngine侧的保存路径：
+
+   ```sql
+   mogdb=# select track_model_train_opt('template_name', 'model_name');
+   ```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-4-best-practices.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-4-best-practices.md
new file mode 100644
index 0000000000000000000000000000000000000000..c78455c3fe64f65ee91be1e408b58a7e24f0c2bb
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-4-best-practices.md
@@ -0,0 +1,32 @@
+---
+title: 最佳实践
+summary: 最佳实践
+author: Guo Huan
+date: 2021-05-19
+---
+
+# 最佳实践
+
+相关参数解释参考表[GS_OPT_MODEL](GS_OPT_MODEL)。
+
+**表 1**
+
+| 模型参数      | 参数建议                                                     |
+| :------------ | :----------------------------------------------------------- |
+| template_name | ‘rlstm’                                                      |
+| model_name    | 自定义，如‘open_ai’，需满足unique约束。                      |
+| datname       | 所服务database名称，如‘mogdb’。                              |
+| ip            | aiEngine-ip地址，如‘127.0.0.1’。                             |
+| port          | aiEngine监听端口，如‘5000’。                                 |
+| max_epoch     | 迭代次数，推荐较大数值，保证收敛效果，如‘2000’。             |
+| learning_rate | (0, 1]浮点数，推荐较大的学习率，助于加快收敛速度。           |
+| dim_red       | 特征值降维系数：<br/>‘-1’：不采用PCA降维，全量特征；<br/>‘（0，1] ’区间浮点数：越小，训练维度越小，收敛速度越快，但影响训练准确率。 |
+| hidden_units  | 特征值维度较高时，建议适度增大此参数，提高模型复杂度，如 ‘64，128……’ |
+| batch_size    | 根据编码数据量，较大数据量推荐适度增大此参数，加快模型收敛，如‘256，512……’ |
+| 其他参数      | 参考表[GS_OPT_MODEL](GS_OPT_MODEL)                           |
+
+推荐参数配置：
+
+```sql
+INSERT INTO gs_opt_model values('rlstm', 'open_ai', 'mogdb', '127.0.0.1', 5000, 2000，1, -1, 64, 512, 0 , false, false, '{S, T}', '{0,0}', '{0,0}', 'Text');
+```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-5-faqs.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-5-faqs.md
new file mode 100644
index 0000000000000000000000000000000000000000..4b3818c603cbc95c5b82526bcfef9830d2405fab
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-5-faqs.md
@@ -0,0 +1,35 @@
+---
+title: 常见问题处理
+summary: 常见问题处理
+author: Guo Huan
+date: 2021-05-19
+---
+
+# 常见问题处理
+
+## AI Engine配置问题
+
+- **AiEngine启动失败**：请检查ip地址，端口是否可用；CA证书路径是否存在。
+- **发起请求AiEngine无响应**：请检查通信双方CA证书是否一致。
+- **训练，测试场景失败**：请检查模型文件保存路径是否存在；训练预测文件是否在正确下载。
+- **更换AiEngine-IP地址**：按照[证书生成](2-2-environment-deployment#证书生成)步骤重新生成证书，在生成证书及密钥步骤中替换成相应的IP地址即可。
+
+## 数据库内部报错问题
+
+问题：AiEngine链接失败。
+
+```
+ERROR:  AI engine connection failed.
+CONTEXT:  referenced column: model_train_opt
+```
+
+处理方法：检查AIEngine是否正常拉起或重启AIEngine；检查通信双方CA证书是否一致；检查模型配置信息中的ip和端口是否匹配。
+
+问题：模型不存在。
+
+```
+ERROR:  OPT_Model not found for model name XXX
+CONTEXT:  referenced column: track_model_train_opt
+```
+
+处理方法：检查[GS_OPT_MODEL](GS_OPT_MODEL)表中是否存在执行语句中“model_name”对应的模型；使用预测功能报错时，检查模型是否已被训练。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-1-x-tuner-overview.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-1-x-tuner-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..c7945cc087e1ec172b4befef16c404b52c48d220
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-1-x-tuner-overview.md
@@ -0,0 +1,10 @@
+---
+title: 概述
+summary: 概述
+author: Guo Huan
+date: 2021-05-19
+---
+
+# 概述
+
+X-Tuner 是一款数据库集成的参数调优工具，通过结合深度强化学习和全局搜索算法等AI技术，实现在无需人工干预的情况下，获取最佳数据库参数配置。本功能不强制与数据库环境部署到一起，支持独立部署，脱离数据库安装环境独立运行。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-2-preparations.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-2-preparations.md
new file mode 100644
index 0000000000000000000000000000000000000000..e9193e85fc0c099931d3f2c7135b9d957eafac39
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-2-preparations.md
@@ -0,0 +1,229 @@
+---
+title: 使用准备
+summary: 使用准备
+author: Guo Huan
+date: 2021-05-19
+---
+
+# 使用准备
+
+<br/>
+
+## 前提条件与使用事项
+
+- 数据库状态正常、客户端能够正常连接、且要求数据库内导入数据，以便调优程序可以执行benchmark测试调优效果。
+- 使用本工具需要指定登录到数据库的用户身份，要求该登录到数据库上的用户具有足够的权限，以便可以获得充足的数据库状态信息。
+- 使用登录到数据库宿主机上的Linux用户，需要将$**GAUSSHOME/bin**添加到PATH环境变量中，即能够直接运行gsql、gs_guc、gs_ctl等数据库运维工具。
+- Python版本建议为Python3.6+，且运行环境中已经安装相应依赖，并能够正常启动调优程序。您可以独立安装一个python3.6+的环境，无需设置到全局环境变量中。不建议使用root用户权限安装本工具，如果以root身份安装本完毕工具，使用其他用户身份运行本工具时，需要确保配置文件有读取权限。
+- 本工具支持以三种模式运行，其中tune和train模式要求用户配置好benchmark运行环境，并导入数据，本工具将会通过迭代运行benchmark来判断修改后的参数是否有性能提升。
+- recommend模式建议在数据库正在执行workload的过程中执行，以便获得更准确的实时workload信息。
+- 本工具默认带有TPC-C、TPC-H、TPC-DS以及sysbench的benchmark运行脚本样例，如果用户使用上述benchmark对数据库系统进行压力测试，则可以对上述配置文件进行适度修改或配置。如果需要适配用户自己的业务场景，需要您参照benchmark目录中的template.py文件编写驱动您自定义benchmark的脚本文件。
+
+<br/>
+
+## 原理简介
+
+调优程序是一个独立于数据库内核之外的工具，需要提供数据库及其所在实例的用户名和登录密码信息，以便控制数据库执行benchmark进行性能测试；在启动调优程序前，要求用户测试环境交互正常，能够正常跑通benchmark测试脚本、能够正常连接数据库。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 如果需要调优的参数中，包含重启数据库后才能使修改生效的参数，那么在调优过程中数据库将会重启多次。如果用户的数据库正在执行作业，请慎用train与tune模式。
+
+调优程序X-Tuner包含三种运行模式，分别是:
+
+- recommend：通过用户指定的用户名等信息登录到数据库环境中，获取当前正在运行的workload特征信息，根据上述特征信息生成参数推荐报告。报告当前数据库中不合理的参数配置和潜在风险等；输出根据当前正在运行的workload行为和特征；输出推荐的参数配置。**该模式是秒级的，不涉及数据库的重启操作，其他模式可能需要反复重启数据库**。
+- train：通过用户提供的benchmark信息，不断地进行参数修改和benchmark的执行。通过反复的迭代过程，训练强化学习模型，以便用户在后面通过tune模式加载该模型进行调优。
+- tune：使用优化算法进行数据库参数的调优，当前支持两大类算法，一种是深度强化学习，另一种是全局搜索算法（全局优化算法）。深度强化学习模式要求先运行train模式，生成训练后的调优模型，而使用全局搜索算法则不需要提前进行训练，可以直接进行搜索调优。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 如果在tune模式下，使用深度强化学习算法，要求必须有一个训练好的模型，且要求**训练该模型时的参数与进行调优时的参数列表（包括max与min）必须一致**。
+
+**图 1** X-Tuner 结构图<br/>
+
+![X-Tuner-结构图](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/preparations-1.png)
+
+X-Tuner 的整体架构如图1 X-Tuner 结构图所示，系统可以分为：
+
+- DB侧：通过DB_Agent 模块对数据库实例进行抽象，通过该模块可以获取数据库内部的状态信息、当前数据库参数、以及设置数据库参数等。DB侧包括登录数据库环境使用的SSH连接。
+- 算法侧：用于调优的算法包，包括全局搜索算法（如贝叶斯优化、粒子群算法等）和深度强化学习（如DDPG）；
+- X-Tuner 主体逻辑模块：通过Enviroment模块进行封装，每一个step 就是一次调优过程。整个调优过程通过多个step进行迭代；
+- benchmark：由用户指定的benchmark性能测试脚本，用于运行benchmark作业，通过跑分结果反映数据库系统性能优劣。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 应确保benchmark脚本跑分结果越大表示性能越好。 例如TPC-H这种衡量SQL语句整体执行时长的benchmark，可以通过取总体执行时间的相反数作为benchmark的输出分数。
+
+<br/>
+
+## X-Tuner的运行和安装方法
+
+可以通过两种方式运行X-Tuner，一种是直接通过源码运行，另一种则是通过Python的setuptools将X-Tuner安装到系统上，而后直接通过 gs_xtuner 命令调用。下面分别介绍两种运行X-Tuner的方法。
+
+**方法一：直接通过源代码运行**
+
+1. 切换到xtuner的源代码目录下。对于openGauss社区代码来说，该路径在openGauss-server/src/gausskernel/dbmind/tools/xtuner。对于已经安装的数据库系统，则该源代码路径为 **$GAUSSHOME**/bin/dbmind/xtuner。
+
+2. 在当前目录下可以看到 requirements.txt 等文件，通过pip包管理工具根据该 requirements.txt 文件安装依赖：
+
+   ```bash
+   pip install -r requirements.txt
+   ```
+
+3. 安装成功后需要添加环境变量PYTHONPATH，然后可执行main.py。以获取帮助信息为例，则可以执行：
+
+   ```bash
+   cd tuner # 切换到 main.py 入口文件所在的目录
+   export PYTHONPATH='..'  # 将上一级目录添加到寻找包的路径中
+   python main.py --help  # 可以直接通过该命令执行获取帮助的动作，其他功能使用方法类似
+   ```
+
+**方法二：将X-Tuner 安装到系统中**
+
+1. 可以通过 setup.py 文件将X-Tuner安装到系统中，然后通过命令gs_xtuner运行。首先需要切换到xtuner的根目录，目录位置见上文。
+
+2. 执行下述命令，Python 会通过自身的setuptools 将本工具安装到Python环境中：
+
+   ```bash
+   python setup.py install
+   ```
+
+   如果Python的bin目录被添加到PATH环境变量中，则gs_xtuner命令也可以在任何地方被直接调用。
+
+3. 仍然以获取帮助信息为例，执行下述命令：
+
+   ```bash
+   gs_xtuner --help
+   ```
+
+<br/>
+
+## X-Tuner 的配置文件说明
+
+X-Tuner 在运行前需要加载配置文件，该配置文件默认路径是**$INSTALL_DIR/tuner/xtuner.conf**，可以通过**gs_xtuner --help**命令查看默认加载的配置文件绝对路径：
+
+```bash
+...
+ -x TUNER_CONFIG_FILE, --tuner-config-file TUNER_CONFIG_FILE
+                        This is the path of the core configuration file of the
+                        X-Tuner. You can specify the path of the new
+                        configuration file. The default path is /path/to/xtuner/xtuner.conf.
+                        You can modify the configuration file to control the
+                        tuning process.
+...
+```
+
+修改配置文件的配置项可以指引X-Tuner 执行不同的动作，用户可以根据自己的不同需求来修改配置文件的内容，配置文件的配置项说明详见[命令参考](3-5-command-reference)页面中的表2。如果需要修改配置文件的加载路径，则可以通过选项 **-x** 命令行选项来指定。
+
+<br/>
+
+## Benchmark的选择与配置
+
+Benchmark的驱动脚本存放路径为 X-Tuner 的benchmark子目录。X-Tuner自带常用的benchmark驱动脚本，例如基于时间周期的探测脚本（**默认**）、TPC-C、TPC-H等。X-Tuner通过调用benchmark/__init__.py文件中 **get_benchmark_instance()** 命令来加载不同的benchmark驱动脚本，获取benchmark驱动实例。其中，benchmark驱动脚本的格式说明如下：
+
+- 驱动脚本文件名：表示benchmark的名字，该名字用于表示驱动脚本的唯一性，可通过在 X-Tuner 的配置文件中的配置项**benchmark_script**来指定选择加载哪个benchmark驱动脚本。
+- 驱动脚本内容三要素：path变量、cmd变量以及run函数。
+
+下面分别介绍驱动脚本的内容三要素：
+
+1. path 变量：表示benchmark脚本的存放地址，可以直接在驱动脚本中修改，也可以通过配置文件的 benchmark_path 配置项来指定。
+
+2. cmd 变量：表示执行benchmark 脚本需要运行的命令，可以直接在驱动脚本中修改，也可以通过配置文件的 benchmark_cmd 配置项来指定。cmd中的文本允许使用占位符，用于获取某些运行cmd命令时的必要信息，使用示例参见TPC-H驱动脚本示例。这些占位符包括：
+
+   - {host}：数据库宿主机的IP地址
+   - {port}：数据库实例的侦听端口号
+   - {user}：登录数据库系统上的用户名
+   - {password}：与登录数据库系统上的用户相匹配的密码
+   - {db}：正在进行调优的数据库名
+
+3. run 函数：该函数的函数签名为：
+
+   ```java
+   def run(remote_server, local_host) -> float:
+   ```
+
+   其中，返回数据类型为float，表示benchmark执行后的评估分数值，要求该值越大表示性能越好，例如使用TPC-C跑分结果tpmC即可作为返回值，TPC-H的全部SQL语句执行总时间的相反数（取相反数后可保证返回值越大则性能越好）也可作为返回值。
+
+   remote_server 变量是X-Tuner 程序传递给脚本使用的远端主机（数据库宿主机）的shell命令接口，local_host 变量是X-Tuner 程序传递给脚本使用的本地主机（运行X-Tuner脚本的主机）的shell命令接口。上述shell命令接口提供的方法包括：
+
+   ```
+   exec_command_sync(command, timeout)
+   功能：该方法用于在主机上执行shell命令。
+   参数列表：
+   command 必选，数据类型可以是str, 以及元素为str类型的list或tuple;
+   timeout 可选，表示命令执行的超时时长，单位是秒。
+   返回值：
+   返回二元组 (stdout, stderr)，stdout表示标准输出流结果，stderr表示标准错误流结果，数据类型均为str.
+   ```
+
+   ```
+   exit_status
+   功能：该属性表示最近一条shell命令执行后的退出状态码(exit status code)。
+   说明：一般情况，退出状态码为0表示执行正常，非0表示存在错误。
+   ```
+
+Benchmark驱动脚本示例说明
+
+1. TPC-C 驱动脚本
+
+   ```bash
+   from tuner.exceptions import ExecutionError
+
+   # WARN: You need to download the benchmark-sql test tool to the system,
+   # replace the PostgreSQL JDBC driver with the openGauss driver,
+   # and configure the benchmark-sql configuration file.
+   # The program starts the test by running the following command:
+   path = '/path/to/benchmarksql/run'  # TPC-C测试脚本benchmark-sql 的存放路径
+   cmd = "./runBenchmark.sh props.gs"  # 自定义一个名为 props.gs 的benchmark-sql测试配置文件
+
+
+   def run(remote_server, local_host):
+       # 切换到 TPC-C 脚本目录下，清除历史错误日志，然后运行测试命令。
+       # 此处最好等待几秒钟，因为benchmark-sql 测试脚本生成最终测试报告是通过一个shell脚本实现的，整个过程会有延迟，
+       # 为了保证能够获取到最终的tpmC数值报告，我们这里选择等待3秒钟。
+       stdout, stderr = remote_server.exec_command_sync(['cd %s' % path, 'rm -rf benchmarksql-error.log', cmd, 'sleep 3'])
+       # 如果标准错误流中有数据，则报异常退出。
+       if len(stderr) > 0:
+           raise ExecutionError(stderr)
+
+       # 寻找最终tpmC结果
+       tpmC = None
+       split_string = stdout.split()  # 对标准输出流结果进行分词。
+       for i, st in enumerate(split_string):
+           # 在5.0版本的benchmark-sql中，tpmC最终测试结果数值在 ‘(NewOrders)’关键字的后两位，正常情况下，找到该字段后直接返回即可。
+           if "(NewOrders)" in st:
+               tpmC = split_string[i + 2]
+               break
+       stdout, stderr = remote_server.exec_command_sync(
+           "cat %s/benchmarksql-error.log" % path)
+       nb_err = stdout.count("ERROR:")  # 判断整个benchmark运行过程中，是否有报错，记录报错的错误数
+       return float(tpmC) - 10 * nb_err  # 这里将报错的错误数作为一个惩罚项，惩罚系数为10，越高的惩罚系数表示越看中报错的数量.
+
+   ```
+
+2. TPC-H 驱动脚本
+
+   ```bash
+   import time
+
+   from tuner.exceptions import ExecutionError
+
+   # WARN: You need to import data into the database and SQL statements in the following path will be executed.
+   # The program automatically collects the total execution duration of these SQL statements.
+   path = '/path/to/tpch/queries'  # 存放TPC-H测试用的SQL脚本目录
+   cmd = "gsql -U {user} -W {password} -d {db} -p {port} -f {file}"  # 需要运行TPC-H测试脚本的命令，一般使用'gsql -f 脚本文件' 来运行
+
+
+   def run(remote_server, local_host):
+       # 遍历当前目录下所有的测试用例文件名
+       find_file_cmd = "find . -type f -name '*.sql'"
+       stdout, stderr = remote_server.exec_command_sync(['cd %s' % path, find_file_cmd])
+       if len(stderr) > 0:
+           raise ExecutionError(stderr)
+       files = stdout.strip().split('\n')
+       time_start = time.time()
+       for file in files:
+           # 使用 file 变量替换 {file}，然后执行该命令行。
+           perform_cmd = cmd.format(file=file)
+           stdout, stderr = remote_server.exec_command_sync(['cd %s' % path, perform_cmd])
+           if len(stderr) &t;> 0:
+               print(stderr)
+       # 代价为全部测试用例的执行总时长
+       cost = time.time() - time_start
+       # 取相反数，适配run 函数的定义：返回结果越大表示性能越好。
+       return - cost
+   ```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-3-examples.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-3-examples.md
new file mode 100644
index 0000000000000000000000000000000000000000..7d81dc93f6bd5e6960b41942ec7889258bdee5ce
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-3-examples.md
@@ -0,0 +1,157 @@
+---
+title: 使用示例
+summary: 使用示例
+author: Guo Huan
+date: 2021-05-19
+---
+
+# 使用示例
+
+X-Tuner 支持三种模式，分别是获取参数诊断报告的recommend模式、训练强化学习模型的train模式、以及使用算法进行调优的tune模式。上述三种模式可以通过命令行参数来区别，通过配置文件来指定具体的细节。
+
+<br/>
+
+## 配置数据库连接信息
+
+三种模式连接数据库的配置项是相同的，有两种方式：一种是直接通过命令行输入详细的连接信息，另一种是通过JSON格式的配置文件输入，下面分别对两种指定数据库连接信息的方法进行说明。
+
+1. 通过命令行指定：
+
+   分别传递 -db-name -db-user -port -host -host-user 参数，可选 -host-ssh-port 参数，例如：
+
+   ```bash
+   gs_xtuner recommend --db-name mogdb --db-user omm --port 5678 --host 192.168.1.100 --host-user omm
+   ```
+
+2. 通过JSON格式的连接信息配置文件指定：
+
+   JSON配置文件的示例如下，并假设文件名为 connection.json：
+
+   ```json
+   {
+     "db_name": "mogdb",     # 数据库名
+     "db_user": "dba",       # 登录到数据库上的用户名
+     "host": "127.0.0.1",    # 数据库宿主机的IP地址
+     "host_user": "dba",     # 登录到数据库宿主机的用户名
+     "port": 5432,           # 数据库的侦听端口号
+     "ssh_port": 22          # 数据库宿主机的SSH侦听端口号
+   }
+   ```
+
+   则可通过 -f connection.json 传递。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 为了防止密码泄露，配置文件和命令行参数中默认都不包含密码信息，用户在输入上述连接信息后，程序会采用交互式的方式要求用户输数据库密码以及操作系统登录用户的密码。
+
+<br/>
+
+## recommend 模式使用示例
+
+对recommend 模式生效的配置项为 scenario，若为auto，则自动检测workload类型。
+
+执行下述命令，获取诊断结果：
+
+```bash
+gs_xtuner recommend -f connection.json
+```
+
+则可以生成诊断报告如下：
+
+**图 1** recommend 模式生成的报告示意图
+
+![recommend-模式生成的报告示意图](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/examples-1.png)
+
+在上述报告中，推荐了该环境上的数据库参数配置，并进行了风险提示。报告同时生成了当前workload的特征信息，其中有几个特征是比较有参考意义的：
+
+- temp_file_size：产生的临时文件数量，如果该结果大于0，则表明系统使用了临时文件。使用过多的临时文件会导致性能不佳，如果可能的话，需要提高work_mem参数的配置。
+- cache_hit_rate：shared_buffer 的缓存命中率，表明当前workload使用缓存的效率。
+- read_write_ratio：数据库作业的读写比例。
+- search_modify_ratio：数据库作业的查询与修改数据的比例。
+- ap_index：表明当前workload的AP指数，取值范围是0到10，该数值越大，表明越偏向于数据分析与检索。
+- workload_type：根据数据库统计信息，推测当前负载类型，分为AP、TP以及HTAP三种类型。
+- checkpoint_avg_sync_time：数据库在checkpoint 时，平均每次同步刷新数据到磁盘的时长，单位是毫秒。
+- load_average：平均**每个CPU核心**在1分钟、5分钟以及15分钟内的负载。一般地，该数值在1左右表明当前硬件比较匹配workload、在3左右表明运行当前作业压力比较大，大于5则表示当前硬件环境运行该workload压力过大（此时一般建议减少负载或升级硬件）。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** recommend 模式会读取数据库中的pg_stat_database以及 pg_stat_bgwriter等系统表中的信息，需要登录到数据库上的用户具有足够的权限（建议为**管理员权限**，可通过alter user username sysadmin；授予username相应的权限)。 由于某些系统表会一直记录统计信息，这可能会对负载特征识别造成干扰，因此建议最好先清空某些系统表的统计信息，运行一段时间的workload后再使用recommend模式进行诊断，以便获得更准确的结果。使用如下命令清除统计信息：
+>
+> `select pg_stat_reset_shared('bgwriter');`
+>
+> `select pg_stat_reset();`
+
+<br/>
+
+## train 模式使用示例
+
+该模式是用来训练深度强化学习模型的，与该模式有关的配置项为：
+
+- rl_algorithm：用于训练强化学习模型的算法，当前支持设置为ddpg。
+
+- rl_model_path：训练后生成的强化学习模型保存路径。
+
+- rl_steps：训练过程的最大迭代步数。
+
+- max_episode_steps：每个回合的最大步数。
+
+- scenario：明确指定的workload类型，如果为auto则为自动判断。在不同模式下，推荐的调优参数列表也不一样。
+
+- tuning_list：**用户指定需要调哪些参数，如果不指定，则根据workload类型自动推荐应该调的参数列表。**如需指定，则tuning_list 表示调优列表文件的路径。一个调优列表配置文件的文件内容示例如下：
+
+  ```json
+  {
+    "work_mem": {
+      "default": 65536,
+      "min": 65536,
+      "max": 655360,
+      "type": "int",
+      "restart": false
+    },
+    "shared_buffers": {
+      "default": 32000,
+      "min": 16000,
+      "max": 64000,
+      "type": "int",
+      "restart": true
+    },
+    "random_page_cost": {
+      "default": 4.0,
+      "min": 1.0,
+      "max": 4.0,
+      "type": "float",
+      "restart": false
+    },
+    "enable_nestloop": {
+      "default": true,
+      "type": "bool",
+      "restart": false
+    }
+  }
+  ```
+
+待上述配置项配置完成后，可以通过下述命令启动训练：
+
+```bash
+gs_xtuner train -f connection.json
+```
+
+训练完成后，会在配置项rl_model_path指定的目录中生成模型文件。
+
+<br/>
+
+## tune 模式使用示例
+
+tune模式支持多种算法，包括基于强化学习（Reinforcement Learning, RL）的DDPG算法、基于全局搜索算法（Global OPtimization algorithm, GOP）算法的贝叶斯优化算法（Bayesian Optimization）以及粒子群算法（Particle Swarm Optimization, PSO）。
+
+与tune模式相关的配置项为：
+
+- tune_strategy: 指定选择哪种算法进行调优，支持rl（使用强化学习模型进行调优）、gop （使用全局搜索算法）以及 auto（自动选择）。若该参数设置为rl，则rl相关的配置项生效。除前文提到过的train模式下生效的配置项外，test_episode配置项也生效，该配置项表明调优过程的最大回合数，该参数直接影响了调优过程的执行时间（一般地，数值越大越耗时）。
+- gop_algorithm: 选择何种全局搜索算法，支持bayes以及pso。
+- max_iterations: 最大迭代轮次，数值越高搜索时间越长，效果往往越好。
+- particle_nums: 在PSO算法上生效，表示粒子数。
+- scenario 与 tuning_list 见上文 train 模式中的描述。
+
+待上述配置项配置完成后，可以通过下述命令启动调优：
+
+```bash
+gs_xtuner tune -f connection.json
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **注意：** 在使用tune和train 模式前，用户需要先导入benchmark所需数据并检查benchmark能否正常跑通。调优过程结束后，调优程序会自动恢复调优前的数据库参数配置。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-4-obtaining-help-information.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-4-obtaining-help-information.md
new file mode 100644
index 0000000000000000000000000000000000000000..f22f423cf72a6cd192fca0aee9cb505fdd6a99bb
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-4-obtaining-help-information.md
@@ -0,0 +1,58 @@
+---
+title: 获取帮助
+summary: 获取帮助
+author: Guo Huan
+date: 2021-05-19
+---
+
+# 获取帮助
+
+启动调优程序之前，可以通过如下命令获取帮助信息：
+
+```bash
+gs_xtuner --help
+```
+
+输出帮助信息结果如下：
+
+```bash
+usage: gs_xtuner [-h] [--db-name DB_NAME] [--db-user DB_USER] [--port PORT]
+                 [--host HOST] [--host-user HOST_USER]
+                 [--host-ssh-port HOST_SSH_PORT] [-f DB_CONFIG_FILE]
+                 [-x TUNER_CONFIG_FILE] [-v]
+                 {train,tune,recommend}
+
+X-Tuner: a self-tuning tool integrated by MogDB.
+
+positional arguments:
+  {train,tune,recommend}
+                        Train a reinforcement learning model or tune database
+                        by model. And also can recommend best_knobs according
+                        to your workload.
+
+optional arguments:
+  -h, --help            show this help message and exit
+  -f DB_CONFIG_FILE, --db-config-file DB_CONFIG_FILE
+                        You can pass a path of configuration file otherwise
+                        you should enter database information by command
+                        arguments manually. Please see the template file
+                        share/server.json.template.
+  -x TUNER_CONFIG_FILE, --tuner-config-file TUNER_CONFIG_FILE
+                        This is the path of the core configuration file of the
+                        X-Tuner. You can specify the path of the new
+                        configuration file. The default path is xtuner.conf.
+                        You can modify the configuration file to control the
+                        tuning process.
+  -v, --version         show program's version number and exit
+
+Database Connection Information:
+  --db-name DB_NAME     The name of database where your workload running on.
+  --db-user DB_USER     Use this user to login your database. Note that the
+                        user must have sufficient permissions.
+  --port PORT           Use this port to connect with the database.
+  --host HOST           The IP address of your database installation host.
+  --host-user HOST_USER
+                        The login user of your database installation host.
+  --host-ssh-port HOST_SSH_PORT
+                        The SSH port of your database installation host.
+```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-5-command-reference.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-5-command-reference.md
new file mode 100644
index 0000000000000000000000000000000000000000..d6a992580a3681607e92f432fb67046b09fc030f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-5-command-reference.md
@@ -0,0 +1,50 @@
+---
+title: 命令参考
+summary: 命令参考
+author: Guo Huan
+date: 2021-05-19
+---
+
+# 命令参考
+
+**表 1** 命令行参数
+
+| 参数                   | 参数说明                                                     | 取值范围               |
+| :--------------------- | :----------------------------------------------------------- | :--------------------- |
+| mode                   | 指定调优程序运行的模式                                       | train，tune，recommend |
+| -tuner-config-file, -x | X-Tuner的核心参数配置文件路径，默认路径为安装目录下的xtuner.conf | \-                     |
+| -db-config-file, -f    | 调优程序的用于登录到数据库宿主机上的连接信息配置文件路径，若通过该文件配置数据库连接信息，则下述数据库连接信息可省略 | \-                     |
+| -db-name               | 指定需要调优的数据库名                                       | \-                     |
+| -db-user               | 指定以何用户身份登陆到调优的数据库上                         | \-                     |
+| -port                  | 数据库的侦听端口                                             | \-                     |
+| -host                  | 数据库实例的宿主机IP                                         | \-                     |
+| -host-user             | 指定以何用户身份登陆到数据库实例的宿主机上，要求改用户名的环境变量中可以找到gsql、gs_ctl等数据库运维工具。 | \-                     |
+| -host-ssh-port         | 数据库实例所在宿主机的SSH端口号，可选，默认为22              | \-                     |
+| -help, -h              | 返回帮助信息                                                 | \-                     |
+| -version, -v           | 返回当前工具版本号                                           | \-                     |
+
+**表 2** 配置文件中的参数详解
+
+| 参数名                | 参数说明                                                     | 取值范围                      |
+| :-------------------- | :----------------- | :------------------- |
+| logfile               | 生成的日志存放路径                                           | \-                            |
+| output_tuning_result  | 可选，调优结果的保存路径                                     | \-                            |
+| verbose               | 是否打印详情                                                 | on, off                       |
+| recorder_file         | 调优中间信息的记录日志存放路径                               | \-                            |
+| tune_strategy         | 调优模式下采取哪种策略                                       | rl, gop, auto                 |
+| drop_cache            | 是否在每一个迭代轮次中进行drop cache，drop cache可以使benchmark跑分结果更加稳定。若启动该参数，则需要将登录的系统用户加入到 /etc/sudoers 列表中，同时为其增加 **NOPASSWD** 权限（由于该权限可能过高，建议临时启用该权限，调优结束后关闭）。 | on, off                       |
+| used_mem_penalty_term | 数据库使用总内存的惩罚系数，用于防止通过无限量占用内存而换取的性能表现。该数值越大，惩罚力度越大。 | 建议0 ~ 1                     |
+| rl_algorithm          | 选择何种RL算法                                               | ddpg                          |
+| rl_model_path         | RL模型保存或读取路径，包括保存目录名与文件名前缀。在train 模式下该路径用于保存模型，在tune模式下则用于读取模型文件 | \-                            |
+| rl_steps              | 深度强化学习算法迭代的步数                                   | \-                            |
+| max_episode_steps     | 每个回合的最大迭代步数                                       | \-                            |
+| test_episode          | 使用RL算法进行调优模式的回合数                               | \-                            |
+| gop_algorithm         | 采取何种全局搜索算法                                         | bayes, pso, auto              |
+| max_iterations        | 全局搜索算法的最大迭代轮次（并非确定数值，可能会根据实际情况多跑若干轮） | \-                            |
+| particle_nums         | PSO算法下的粒子数量                                          | \-                            |
+| benchmark_script      | 使用何种benchmark驱动脚本，该选项指定加载benchmark路径下同名文件，默认支持TPC-C、TPC-H等典型benchmark | tpcc, tpch, tpcds, sysbench … |
+| benchmark_path        | benchmark 脚本的存储路径，若没有配置该选项，则使用benchmark驱动脚本中的配置 | \-                            |
+| benchmark_cmd         | 启动benchmark 脚本的命令，若没有配置该选项，则使用benchmark驱动脚本中的配置 | \-                            |
+| benchmark_period      | 仅对 period benchmark有效，表明整个benchmark的测试周期是多少，单位是秒 | -                             |
+| scenario              | 用户指定的当前workload所属的类型                             | tp, ap, htap                  |
+| tuning_list           | 准备调优的参数列表文件，可参考 share/knobs.json.template 文件 | \-                            |
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-6-Troubleshooting.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-6-Troubleshooting.md
new file mode 100644
index 0000000000000000000000000000000000000000..dba0a629a283a28a41a135e74a7cb6071924ecef
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-6-Troubleshooting.md
@@ -0,0 +1,14 @@
+---
+title: 常见问题处理
+summary: 常见问题处理
+author: Guo Huan
+date: 2021-05-19
+---
+
+# 常见问题处理
+
+- 数据库实例连接失败：请检查数据库实例的情况，是否数据库实例出现了问题或安全权限配置（pg_hba.conf文件中的配置项）不正确。
+- 重启失败：请检查数据库实例健康情况，确保数据库实例工作正常；
+- 依赖安装失败：建议先升级pip包管理工具，通过命令 python -m pip install -upgrade pip 实现
+- 跑TPC-C作业时发现性能越来越慢：TPC-C等高并发场景下的压力测试，往往伴随着大量的数据修改。由于每一次测试并非是幂等的（TPC-C数据库数据量的增加、没有进行vacuum full清理掉失效元组、数据库没有触发checkpoint、没有进行drop cache等），因此一般建议TPC-C等伴随着较多数据写入的benchmark应该每隔一段时间（视具体并发量、执行时长的不同而异）重新导入一次数据，比较简单的方法是备份$PGDATA目录。
+- TPC-C 跑作业时，TPC-C驱动脚本报异常 “TypeError: float() argument must be a string or a number, not 'NoneType'”（不能将None转换为float类型）：这是因为没有获取到TPC-C的压测返回结果，造成该问题的原因比较多，请首先手动检测是否能够跑通TPC-C并能够获取返回结果。若无上述问题，则建议将 TPC-C 驱动脚本中的命令列表中的 “sleep” 命令延迟时间设得更大一些。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-1-overview.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-1-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..eb13999f6c434e629b70a7c910e0ef3467a8df2f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-1-overview.md
@@ -0,0 +1,18 @@
+---
+title: 概述
+summary: 概述
+author: Guo Huan
+date: 2021-05-19
+---
+
+# 概述
+
+SQLdiag是MogDB中SQL语句执行时长预测工具。现有的预测技术主要基于执行计划的预测方法，但这些预测方案仅适用于OLAP场景且可以获取执行计划的任务，对于OLTP或者HTAP这样的快速、简单查询是没有太多使用价值的。与上述方案不同，SQLdiag着眼于数据库的历史SQL语句，通过对历史SQL语句的执行表现进行总结归纳，将之再用于推断新的未知业务上。由于短时间内数据库SQL语句执行时长不会有太大的差距，SQLdiag可以从历史数据中检测出与已执行SQL语句相似的语句结果集，并基于SQL向量化技术和模板化方法预测SQL语句执行时长。本工具有如下优点：
+
+1. 不需要SQL语句的执行计划，对数据库性能不会有任何的影响。
+2. 使用场景广泛，目前业内的很多算法局限性比较高，比如只适用于OLTP或者OLAP，而SQLdiag使用场景广泛。
+3. 该框架鲁棒性强，容易理解，只需要简单的操作，就可以训练出自己的预测模型。
+
+SQLdiag是一个SQL语句执行时间预测工具，通过模板化方法，实现在不获取SQL语句执行计划的前提下，依据语句逻辑相似度与历史执行记录，预测SQL语句的执行时间。
+
+本工具的典型应用场景是对一批即将上线的SQL语句进行透视，提前识别风险。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-2-usage-guide.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-2-usage-guide.md
new file mode 100644
index 0000000000000000000000000000000000000000..aedee8afc965c7795efafab7010275c9452fab11
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-2-usage-guide.md
@@ -0,0 +1,107 @@
+---
+title: 使用指导
+summary: 使用指导
+author: Guo Huan
+date: 2021-10-21
+---
+
+# 使用指导
+
+## 前提条件
+
+- 需要保证用户提供训练数据。
+- 如果用户通过提供的工具收集训练数据，则需要启用WDR功能，涉及到的参数为track_stmt_stat_level和log_min_duration_statement，具体情况见下面小节。
+- 为保证预测准确率，用户提供的历史语句日志应尽可能全面并具有代表性。
+- 按照要求配置python 3.6+环境及其依赖。
+
+## 环境配置
+
+本功能运行环境要求Python 3.6版本及以上，需要的第三方依赖包记录在requirements.txt文件中，可以通过pip install命令安装依赖，如：
+
+```bash
+pip install requirements.txt
+```
+
+## SQL流水采集方法
+
+本工具需要用户提前准备数据，训练数据格式如下，每个样本通过换行符分隔：
+
+```
+SQL,EXECUTION_TIME
+```
+
+预测数据格式如下：
+
+```
+SQL
+```
+
+其中SQL表示**SQL语句的文本**，EXECUTION_TIME表示**SQL语句的执行时间**，样例数据见sample_data中的train.csv和predict.csv。
+
+用户可以按照要求格式自己收集训练数据，工具也提供了脚本自动采集（load_sql_from_rd），该脚本基于WDR报告获取SQL信息，涉及到的参数有log_min_duration_statement和track_stmt_stat_level：
+
+- 其中log_min_duration_statement表示慢SQL阈值，如果为0则全量收集，时间单位为毫秒；
+- track_stmt_stat_level表示信息捕获的级别，建议设置为track_stmt_stat_level='L0,L0'
+
+参数开启后，可能占用一定的系统资源，但一般不大。持续的高并发场景可能产生5%以内的损耗，数据库并发较低的场景，性能损耗可忽略。
+
+```bash
+使用脚本获取训练集方式：
+load_sql_from_wdr.py [-h] --port PORT --start_time START_TIME
+                            --finish_time FINISH_TIME [--save_path SAVE_PATH]
+例如：
+    python load_sql_from_wdr.py --start_time "2021-04-25 00:00:00" --finish_time "2021-04-26 14:00:00" --port 5432  --save_path ./data.csv
+```
+
+## 操作步骤
+
+1. 提供历史日志以供模型训练
+
+2. 进行训练与预测操作：
+
+   ```bash
+   基于模板法的训练与预测：
+       python main.py [train, predict] -f FILE --model template --model-path template_model_path
+   基于DNN的训练与预测：
+       python main.py [train, predict] -f FILE --model dnn --model-path dnn_model_path
+   ```
+
+## 使用方法示例
+
+在本工具的根目录中，执行下列语句可以实现对应功能。
+
+使用提供的测试数据进行模板化训练：
+
+```bash
+python main.py train -f ./sample_data/train.csv --model template --model-path ./template
+```
+
+使用提供的测试数据进行模板化预测：
+
+```bash
+python main.py predict -f ./sample_data/predict.csv --model template --model-path ./template --predicted-file ./result/t_result
+```
+
+使用提供的测试数据进行模板化模型更新：
+
+```bash
+python main.py finetune -f ./sample_data/train.csv --model template --model-path ./template
+```
+
+使用提供的测试数据进行DNN训练：
+
+```bash
+python main.py train -f ./sample_data/train.csv --model dnn --model-path ./dnn_model
+```
+
+使用提供的测试数据进行DNN预测：
+
+```bash
+python main.py predict -f ./sample_data/predict.csv --model dnn --model-path ./dnn_model --predicted-file
+```
+
+使用提供的测试数据进行DNN模型更新：
+
+```bash
+python main.py finetune -f ./sample_data/train.csv --model dnn --model-path ./dnn_model
+```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-3-obtaining-help-information.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-3-obtaining-help-information.md
new file mode 100644
index 0000000000000000000000000000000000000000..0b8ebae44ec1feaf2057352754d12bba87fda427
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-3-obtaining-help-information.md
@@ -0,0 +1,49 @@
+---
+title: 获取帮助
+summary: 获取帮助
+author: Guo Huan
+date: 2021-05-19
+---
+
+# 获取帮助
+
+使用SQLdiag工具前，您可以通过以下指令获取帮助。
+
+```
+python main.py --help
+```
+
+显示如下帮助信息：
+
+```
+usage: main.py [-h] [-f CSV_FILE] [--predicted-file PREDICTED_FILE]
+               [--model {template,dnn}] --model-path MODEL_PATH
+               [--config-file CONFIG_FILE]
+               {train,predict,finetune}
+
+SQLdiag integrated by openGauss.
+
+positional arguments:
+  {train,predict,finetune}
+                        The training mode is to perform feature extraction and
+                        model training based on historical SQL statements. The
+                        prediction mode is to predict the execution time of a
+                        new SQL statement through the trained model.
+
+optional arguments:
+  -h, --help            show this help message and exit
+  -f CSV_FILE, --csv-file CSV_FILE
+                        The data set for training or prediction. The file
+                        format is CSV. If it is two columns, the format is
+                        (SQL statement, duration time). If it is three
+                        columns, the format is (timestamp of SQL statement
+                        execution time, SQL statement, duration time).
+  --predicted-file PREDICTED_FILE
+                        The file path to save the predicted result.
+  --model {template,dnn}
+                        Choose the model model to use.
+  --model-path MODEL_PATH
+                        The storage path of the model file, used to read or
+                        save the model file.
+  --config-file CONFIG_FILE
+```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-4-command-reference.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-4-command-reference.md
new file mode 100644
index 0000000000000000000000000000000000000000..75a86c223f4c3653c68a596edfe63cde8f685899
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-4-command-reference.md
@@ -0,0 +1,17 @@
+---
+title: 命令参考
+summary: 命令参考
+author: Guo Huan
+date: 2021-05-19
+---
+
+# 命令参考
+
+**表 1** 命令行参数说明
+
+| 参数            | 参数说明           | 取值范围      |
+| :-------------- | :----------------- | :------------ |
+| -f              | 训练或预测文件位置 |               |
+| -predicted-file | 预测结果存储位置   |               |
+| -model          | 模型选择           | template，dnn |
+| -model-path     | 训练模型存储位置   |               |
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-5-troubleshooting.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-5-troubleshooting.md
new file mode 100644
index 0000000000000000000000000000000000000000..bbbaf007d5a0889d80787cc8965daf05e70d2811
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-5-troubleshooting.md
@@ -0,0 +1,11 @@
+---
+title: 常见问题处理
+summary: 常见问题处理
+author: Guo Huan
+date: 2021-05-19
+---
+
+# 常见问题处理
+
+- 训练场景失败：请检查历史日志文件路径是否正确，且文件格式符合上文规定。
+- 预测场景失败：请检查模型路径是否正确。确保待预测负载文件格式正确。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-1-overview.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-1-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..bae52cc9b87c214de206dcbf93dbd8598df0c987
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-1-overview.md
@@ -0,0 +1,14 @@
+---
+title: 概述
+summary: 概述
+author: Guo Huan
+date: 2021-05-19
+---
+
+# 概述
+
+anomaly_detection是MogDB集成的、可以用于数据库指标采集、预测指标趋势变化、慢SQL根因分析以及异常监控与诊断的AI工具，是DBMind套间中的一个组件。支持采集的信息分为三块，分别是os_exporter、database_exporter、wdr，os_exporter主要包括IO_Read、IO_Write、IO_Wait、CPU_Usage、Memory_Usage、数据库数据目录磁盘空间占用Disk_space；database_exporter主要包括QPS、部分关键GUC参数（work_mem、shared_buffers、max_connections）、数据库临时文件、外部进程情况、外部连接数；wdr包括慢SQL文本、SQL开始执行时间、SQL结束执行时间相关信息。在异常监控方面，anomaly_detection可以同时对IO_Read、IO_Write、IO_Wait、CPU_Usage、Memory_Usage和Disk_Space多个指标的未来变化趋势进行预测，当发现某个指标在未来某段时间或者某个时刻会超出人工设置的阈值，该工具会通过日志进行报警。在慢SQL根因分析方面，工具会定期从WDR报告中拉取慢SQL信息，并对慢SQL的根因进行诊断，最后将诊断结果存放到日志文件中，同时该工具还支持用户交互式慢SQL诊断，即对用户输入的慢SQL进行根因分析，并将结果反馈给用户。
+
+anomaly_detection由agent和detector两大模块组成。agent和MogDB数据库环境部署在同一个服务器上，该模块主要有两个作用。一个是定时采集数据库指标数据，并将采集到的数据存放到缓冲队列中；另一个作用是将缓冲队列中数据定时发送到detector的collector子模块中。
+
+detector模块由collector模块和monitor模块组成，collector模块和agent模块通过http或https进行通信，接受agent模块push的数据并存储到本地。monitor模块基于本地数据对指标的未来变化趋势进行预测和异常报警，另外结合系统和WDR报告等各种相关联信息，分析慢SQL的根因。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-2-preparations.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-2-preparations.md
new file mode 100644
index 0000000000000000000000000000000000000000..425a08bc3d35863d80a5be6866c27262c1675adf
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-2-preparations.md
@@ -0,0 +1,173 @@
+---
+title: 使用准备
+summary: 使用准备
+author: Guo Huan
+date: 2021-05-19
+---
+
+# 使用准备
+
+## 前提条件与使用事项
+
+- 数据库状态正常。
+- 工具运行过程中，如果系统时间被篡改，可能会造成慢SQL数据采集失效。
+- 工具不支持在备节点上采集。
+- 使用登录到数据库宿主机上的Linux用户，需要将$**GAUSSHOME/bin**添加到PATH环境变量中，即能够直接运行gsql、gs_guc、gs_ctl等数据库运维工具。
+- Python版本建议为Python3.6及以上，且运行环境中已经安装相应依赖，并能够正常启动调优程序。
+- 本工具由Agent和Detector组成，Agent和Detector之间通过'http'或者'https'方式传递数据，因此需要保证Agent服务器和Detector服务器之间能够正常通信。
+- Detector模块运行collector和monitor服务， 需要分别启动。
+- 如果使用'https'方式进行通信，需要准备CA证书以及Agent和Detector的证书和密钥，并分别放入项目根目录certificate下的ca、agent、collector中，同时将密钥加密密码放入certificate的pwf中，并将其权限设置为600，防止其他用户进行读写操作。用户也可以使用share中的脚本生成证书和密钥。
+- 建议用户配置自己的python环境，以免影响其他功能使用（例如使用miniconda）。
+- 慢SQL的根因分析功能需要WDR报告，用户需要开启track_stmt_stat_level='OFF,L1', log_min_duration_statement=3000（慢SQL阈值，用户可按需设定），单位ms。
+- 如果将detecor和数据库部署在同一服务器上，则collector服务端口不能和数据库本地端口相同，否则将无法启动进程。
+
+## 原理简介
+
+图1 anomaly_detection结构图
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/5-2-preparations-1.png)
+
+anomaly_detection是一个独立于数据库内核之外的工具，其结构如图1所示，anomaly_detection主要由agent和detector模块组成；
+
+- agent：数据代理模块，由Source、Channel以及Sink组成。部署在数据库环境上，用于采集数据库中的指标，并通过http或者https方式将其传送给远端检测器模块。
+- detector：检测器模块，负责收集Agent推送的数据并存储，同时该模块基于时序预测和异常检测等算法对数据库指标进行监控和异常检测，同时提供慢SQL根因服务功能。
+
+## anomaly_detection的运行和安装方法
+
+1. 切换到anomaly_detection目录下。对于openGauss社区代码来说，该路径在openGauss-server/src/gausskernel/dbmind/tools/anomaly_detection。对于已经安装的数据库系统，则该源代码路径为 **$GAUSSHOME**/bin/dbmind/anomaly_detection。
+
+2. 在当前目录下可以看到 requirements.txt 等文件，通过pip包管理工具根据该 requirements.txt 文件安装依赖：
+
+   ```bash
+   pip install -r requirements.txt
+   ```
+
+3. 安装成功后可执行main.py。以获取帮助信息为例，则可以执行：
+
+   ```bash
+   python main.py --help  # 可以直接通过该命令执行获取帮助的动作，其他功能使用方法类似
+   ```
+
+## 证书生成
+
+当使用https方式进行通信时，需要用户提供证书，anomaly_detection也提供了证书生成工具。
+
+1. 生成CA根证书，在anomaly_detection的share目录下，执行以下命令：
+
+   ```bash
+   sh gen_ca_certificate.sh
+   ```
+
+该脚本会在anomaly_detection根目录下创建certificate目录，其中包括ca、server、agent三个子目录，ca中存放根证书ca.crt和密钥文件ca.key。
+
+1. 生成server端证书和密钥文件，在anomaly_detection的share目录下，执行以下命令：
+
+   ```bash
+   sh gen_certificate.sh
+
+   # please input the basename of ssl certificate: ../certificate/server
+
+   # please input the filename of ssl certificate: server
+
+   # please input the local host: 127.0.0.1
+
+   # please input the password of ca and ssl separated by space:
+   ```
+
+该脚本需要用户分别输入生成证书与密钥文件存放目录、证书与密钥文件名称、detector端服务器IP地址、ca证书密码和当前证书密码(用空格分开)。脚本最后会在certificate的server下生成server.crt和server.key。
+
+1. 生成agent端证书密钥和文件，在anomaly_detection的share目录下，执行以下命令：
+
+   ```bash
+   sh gen_certificate.sh
+
+   # please input the basename of ssl certificate: ../certificate/agent
+
+   # please input the filename of ssl certificate: agent
+
+   # please input the local host: 127.0.0.1
+
+   # please input the password of ca and ssl separated by space:
+   ```
+
+该脚本需要用户分别输入生成证书与密钥文件存放目录、证书与密钥文件名称、agent端服务器IP地址、ca证书密码和当前证书密码(用空格分开)。脚本最后会在certificate的agent下生成agent.crt和agent.key。
+
+## anomaly_detection的配置文件说明
+
+anomaly_detection 在运行前需要加载 **a-detection.conf** 和 `metric_task.conf` 两个配置文件，可以通过 **python main.py -help** 命令查看配置文件路径：
+
+**a-detection.conf**：该配置文件包含agent、server、database、security、forecast、log六个section，参数解释如下：
+
+```bash
+[database]
+storage_duration = 12H  # 数据存储时间长度，默认12小时
+database_dir = ./data  # 数据存储目录
+
+[security]
+tls = False
+ca = ./certificate/ca/ca.crt
+server_cert = ./certificate/server/server.crt
+server_key = ./certificate/server/server.key
+agent_cert = ./certificate/agent/agent.crt
+agent_key = ./certificate/agent/agent.key
+
+[server]
+host = 0.0.0.0  # 服务端IP地址
+listen_host = 0.0.0.0
+listen_port = 8080
+white_host = 0.0.0.0  # IP白名单
+white_port = 8000  # 端口号白名单
+
+[agent]
+source_timer_interval = 10S  # agent端数据采集频率
+sink_timer_interval = 10S  # agent端数据发送频率
+channel_capacity = 1000  # 缓冲队列最大长度
+db_host = 0.0.0.0  # agent节点IP地址
+db_port = 8080  # agent节点端口号
+db_type = single  # agent节点类型, single: 单机，cn： CN节点、dn： DN节点
+
+[forecast]
+forecast_alg = auto_arima  # 时序预测算法，auto_arima、fbprophet(需要用户自行安装)
+[log]
+log_dir = ./log  # 日志文件位置
+```
+
+metric_task.conf: 该配置文件包括detector method, os_expoeterhe trend_parameter三个sections，参数结束如下：
+
+```bash
+[detector_method]
+trend = os_exporter # 用于时序预测的表名
+slow_sql = wdr # 用户慢SQL诊断的表名
+
+[os_exporter]
+cpu_usage_minimum = 1 # cpu_usage的下限值
+cpu_usage_maximum = 10 # cpu_usage的上限值
+memory_usage_minimum = 1 # memory_usage的下限值
+memory_usage_maximum = 10 # memory_usage的上限值
+io_read_minimum = 1
+io_read_maximum = 10
+io_write_minimum = 1
+io_write_maximum = 10
+io_wait_minimum = 1
+io_wait_maximum = 10
+disk_space_minimum = 1
+disk_space_maximum = 10
+
+[common_parameter]
+data_period = 1000S # 是用于时序预测的历史数据长度，支持整数加时间单位（如：100S、2M、10D）。
+interval = 20S # 监控间隔
+freq = 3S # 趋势预测频率
+period = 2 # 趋势预测长度
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 支持的时间单位：
+>   - 'S'：second，秒。
+>   - 'M'：minute，分。
+>   - 'H'：hour，小时。
+>   - 'D'：day，天。
+>   - 'W'：week，周。
+> - minimum和maximum至少提供一个，不能都不提供。
+> - freq和period共同决定时序预测结果，例子：freq=2S，period=5, 则会预测未来2S、4S、6S、8S、10S的值。
+> - 建议参数配置的时候，保证训练数据长度大于预测长度，否则预测效果会受影响。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-3-adding-monitoring-parameters.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-3-adding-monitoring-parameters.md
new file mode 100644
index 0000000000000000000000000000000000000000..97b6416cbbd630f7105eaf1f69e2756f89f8d076
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-3-adding-monitoring-parameters.md
@@ -0,0 +1,42 @@
+---
+title: 添加监控参数
+summary: 添加监控参数
+author: Guo Huan
+date: 2021-05-19
+---
+
+# 添加监控参数
+
+<br/>
+
+工具只针对os_exporter中的指标进行趋势预测与阈值异常检测，支持用户添加新的监控参数，步骤如下：
+
+1. 在task/os_exporter.py的OS_exporter中编写获取指标的功能函数，并将该函数加入到output的result列表中，例如：
+
+   ```
+   @staticmethod
+   def new_metric():
+       return metric_value
+
+   def output(self):
+       result = [self.cpu_usage(), self.io_wait(), self.io_read(),
+                 self.io_write(), self.memory_usage(), self.disk_space(), self.new_metric()]
+       return result
+
+   ```
+
+2. 在table.json的os_exporter中，将new_metric字段加入到“create table”中，并在“insert”中加上字段类型信息，例如：
+
+   ```
+   "os_exporter": {
+     "create_table": "create table  os_exporter(timestamp bigint, cpu_usage text, io_wait text, io_read text, io_write text, memory_usage text, disk_space text, new_metric text);",
+     "insert": "insert into os_exporter values(%d, \"%s\", \"%s\", \"%s\", \"%s\", \"%s\", \"%s\", \"%s\");",
+   ```
+
+3. 在task/metric_task.conf中添加指标的上限值或者下限值，例如：
+
+   ```
+   [os_exporter]
+   new_metric_minimum = 0
+   new_metric_maximum = 10
+   ```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-4-obtaining-help-information.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-4-obtaining-help-information.md
new file mode 100644
index 0000000000000000000000000000000000000000..832cd5d396dbc1dd370bb4161103309136b17853
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-4-obtaining-help-information.md
@@ -0,0 +1,78 @@
+---
+title: 获取帮助
+summary: 获取帮助
+author: Guo Huan
+date: 2021-05-19
+---
+
+# 获取帮助
+
+启动调优程序之前，可以通过如下命令获取帮助信息：
+
+```python
+源码方式：python main.py --help
+```
+
+输出帮助信息结果如下：
+
+```python
+usage:
+    python main.py start [--role {{agent,collector,monitor}}] # start local service.
+    python main.py stop [--role {{agent,collector,monitor}}] # stop local service.
+    python main.py start [--user USER] [--host HOST] [--project-path PROJECT_PATH] [--role {{agent,collector,monitor}}]
+    # start the remote service.
+    python main.py stop [--user USER] [--host HOST] [--project-path PROJECT_PATH] [--role {{agent,collector,
+    monitor}}] # stop the remote service.
+    python main.py deploy [--user USER] [--host HOST] [--project-path PROJECT_PATH] # deploy project in remote host.
+    python main.py diagnosis [--query] [--start_time] [--finish_time] # rca for slow SQL.
+    python main.py show_metrics # display all monitored metrics(can only be executed on 'detector' machine).
+    python main.py forecast [--metric-name METRIC_NAME] [--period] [--freq]
+     [--forecast-method {{auto_arima, fbprophet}}] [--save-path SAVE_PATH] # forecast future trend of
+     metric(can only be executed on 'detector' machine).
+
+Anomaly-detection: a time series forecast and anomaly detection tool.
+
+positional arguments:
+  {start,stop,deploy,show_metrics,forecast,diagnosis}
+
+optional arguments:
+  -h, --help            show this help message and exit
+  --user USER           User of remote server.
+  --host HOST           IP of remote server.
+  --project-path PROJECT_PATH
+                        Project location in remote server.
+  --role {agent,collector,monitor}
+                        Run as 'agent', 'collector', 'monitor'. Notes: ensure
+                        the normal operation of the openGauss in agent.
+  --metric-name METRIC_NAME
+                        Metric name to be predicted, you must provide an specified metric name.
+.
+  --query QUERY         target sql for RCA.
+                        Currently, the join operator is not supported, and the accuracy of the result
+                        is not guaranteed for SQL syntax containing "not null and".
+  --start_time START_TIME
+                        start time of query
+  --finish_time FINISH_TIME
+                        finish time of query
+  --period PERIOD       Forecast periods of metric, it should be integernotes:
+                        the specific value should be determined to the
+                        trainnig data.if this parameter is not provided, the
+                        default value '100S' will be used.
+  --freq FREQ           forecast gap, time unit: S: Second, M: Minute, H:
+                        Hour, D: Day, W: Week.
+  --forecast-method FORECAST_METHOD
+                        Forecast method, default method is 'auto_arima',if
+                        want to use 'fbprophet', you should install fbprophet
+                        first.
+  --save-path SAVE_PATH
+                        Save the results to this path using csv format, if
+                        this parameter is not provided,, the result wil not be
+                        saved.
+  -v, --version         show program's version number and exit
+
+epilog:
+     the 'a-detection.conf' and 'metric_task.conf' will be read when the program is running,
+     the location of them is:
+     a-detection.conf: /openGauss-server/src/gausskernel/dbmind/tools/anomaly_detection/a-detection.conf.
+     metric_config: /openGauss-server/src/gausskernel/dbmind/tools/anomaly_detection/task/metric_task.conf.
+```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-5-command-reference.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-5-command-reference.md
new file mode 100644
index 0000000000000000000000000000000000000000..892e72b9ec0f661788add25aaabf1f4f316714e8
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-5-command-reference.md
@@ -0,0 +1,26 @@
+---
+title: 命令参考
+summary: 命令参考
+author: Guo Huan
+date: 2021-05-19
+---
+
+# 命令参考
+
+**表 1** 命令行参数
+
+| 参数              | 参数说明                            | 取值范围                                                     |
+| :---------------- | :---------------------------------- | :----------------------------------------------------------- |
+| mode              | 指定运行模式                        | start, stop, forecast, show_metrics, deploy, diagnosis       |
+| -user             | 远程服务器用户                      | -                                                            |
+| -host             | 远程服务器IP                        | -                                                            |
+| -project-path     | 远程服务器anomaly_detection项目路径 | -                                                            |
+| -role             | 启动角色选择                        | agent，collector，monitor                                    |
+| -metric-name      | 指标名称                            | -                                                            |
+| -query            | 根因分析RCA目标query                |                                                              |
+| -start_time       | query执行的开始时间                 |                                                              |
+| -finish_time      | query执行的结束时间                 |                                                              |
+| -forecast-periods | 未来预测周期                        | 整数+时间单位，如'100S'，'3H'<br/>时间单位包括（S(second),M(minute),H(hour),D(day),W(week)） |
+| -forecast-method  | 预测方法                            | auto_arima， fbprophet                                       |
+| -save-path        | 预测结果存放地址                    | -                                                            |
+| -version, -v      | 返回当前工具版本号                  | -                                                            |
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-6-examples.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-6-examples.md
new file mode 100644
index 0000000000000000000000000000000000000000..ebabc411f5a83bbcd31c60c5a4fca637ca9b7417
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-6-examples.md
@@ -0,0 +1,102 @@
+---
+title: 使用示例
+summary: 使用示例
+author: Guo Huan
+date: 2021-05-19
+---
+
+# 使用示例
+
+为了方便用户理解部署过程，假设当前数据库节点信息如下：
+
+```
+IP: 10.90.110.130
+PORT: 8000
+type: single
+```
+
+detector服务器信息：
+
+```
+IP: 10.90.110.131
+listen_host = 0.0.0.0
+listen_port = 8080
+```
+
+部署的启动流程如下：
+
+## 配置文件修改
+
+首先需要更改配置文件 a-detection.conf，主要涉及其中的两个session：
+
+```
+[database]
+storage_duration = 12H  # 数据存储时间长度，默认12小时
+database_dir = ./data  # 数据存储目录
+
+[security]
+tls = False
+ca = ./certificate/ca/ca.crt
+server_cert = ./certificate/server/server.crt
+server_key = ./certificate/server/server.key
+agent_cert = ./certificate/agent/agent.crt
+agent_key = ./certificate/agent/agent.key
+
+[server]
+host = 10.90.110.131
+listen_host = 0.0.0.0
+listen_port = 8080
+white_host =  10.90.110.130
+white_port = 8000
+[agent]
+source_timer_interval = 10S
+sink_timer_interval = 10S
+channel_capacity = 1000
+db_host =  10.90.110.130
+db_port = 8080
+db_type = single
+
+[forecast]
+forecast_alg = auto_arima
+
+[log]
+log_dir = ./log
+```
+
+## 服务启动与停止
+
+启动本地agent服务：
+
+```
+python main.py start --role agent
+```
+
+停止本地agent服务：
+
+```
+python main.py stop --role agent
+```
+
+启动本地collector服务：
+
+```
+python main.py start --role collector
+```
+
+停止本地collector服务：
+
+```
+python main.py stop --role collector
+```
+
+启动本地monitor服务：
+
+```
+python main.py start --role monitor
+```
+
+停止本地monitor服务：
+
+```
+python main.py stop --role monitor
+```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-7-ai-server.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-7-ai-server.md
new file mode 100644
index 0000000000000000000000000000000000000000..ef08fcd1be9858a06f1174f46617491b2791d858
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-7-ai-server.md
@@ -0,0 +1,72 @@
+---
+title: AI_SERVER
+summary: AI_SERVER
+author: Guo Huan
+date: 2021-10-21
+---
+
+# AI_SERVER
+
+ai_server为anomaly_detection特性的分离特性，在原anomaly_detection数据采集功能的基础上增加了采集类型、采集项、数据存储模式，仅用于数据采集，后续将整合到anomaly_detection中，该特性主要包含server组件和agent组件，agent须部署到数据库节点，用于数据采集，server部署在独立节点进行数据收集存储。
+
+数据存储方式包括：sqlite、mongodb、influxdb。
+
+采集项如表1：
+
+**表 1** 采集项说明
+
+<table>
+    <tr>
+        <th>采集类型</th>
+        <th>采集项</th>
+        <th>描述</th>
+    </tr>
+    <tr>
+        <td rowspan=5>database</td>
+        <td>work_mem</td>
+        <td>数据库内存相关GUC参数，对涉及到排序任务的sql，检测分配的空间是否足够。</td>
+    </tr>
+    <tr>
+        <td>shared_buffers</td>
+        <td>数据库内存相关GUC参数，不合适的shared_buffer会导致数据库性能变差。</td>
+    </tr>
+    <tr>
+        <td>max_connections</td>
+        <td>数据库最大连接数。</td>
+    </tr>
+    <tr>
+        <td>current connections</td>
+        <td>数据库当前连接数。</td>
+    </tr>
+    <tr>
+        <td>qps</td>
+        <td>数据库性能指标。</td>
+    </tr>
+    <tr>
+        <td rowspan=6>os</td>
+        <td>cpu usage</td>
+        <td>cpu使用率。</td>
+    </tr>
+    <tr>
+        <td>memory usage</td>
+        <td>内存使用率。</td>
+    </tr>
+    <tr>
+        <td>io wait</td>
+        <td>系统因为io导致的进程wait。</td>
+    </tr>
+    <tr>
+        <td>io write</td>
+        <td>数据磁盘写吞吐量。</td>
+    </tr>
+    <tr>
+        <td>io read</td>
+        <td>数据磁盘读吞吐量。</td>
+    </tr>
+    <tr>
+        <td>disk used</td>
+        <td>磁盘已使用的大小。</td>
+    </tr>
+</table>
+
+部署方式请参见[AI_MANAGER](5-8-ai-manager)章节。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-8-ai-manager.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-8-ai-manager.md
new file mode 100644
index 0000000000000000000000000000000000000000..82dfd54b79b2d369a941bdec668c203a41e23f39
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/5-a-detection-status-monitoring/5-8-ai-manager.md
@@ -0,0 +1,82 @@
+---
+title: AI_MANAGER
+summary: AI_MANAGER
+author: Guo Huan
+date: 2021-10-22
+---
+
+# AI_MANAGER
+
+ai_manager是AI特性部署工具，旨在为ai特性提供自动化、高效便捷的部署及卸载方式，可通过指定模块名称、操作类型及参数文件进行相应ai特性的自动化部署和卸载，实现了版本管理、操作日志记录及日志管理、安装信息记录等功能，支持特性级横向扩展，该工具目前仅支持ai_server的安装及卸载。
+
+## 使用准备
+
+- 项目部署路径为/dbs/AI-tools，需保证该路径存在并有读写执行权限，安装/卸载操作中会清理该路径下的内容，不要将其它文件保存在该路径下。
+- 需要安装python3环境及特性所需python库,依赖库请参考包内的requirements.txt文件。
+- 如开启https，需准备相应的根证书，秘钥文件及密码。
+- agent节点已启动MogDB数据库。
+- 安装agent节点须使用集群用户操作。
+- 如果agent节点集群用户的~/.bashrc文件中没有正确的PGHOST配置，需要将PGHOST配置到/dbs/AI-tools/ai_env文件中。
+
+## 示例
+
+安装命令示例：
+
+```bash
+python3 ai_manager --module anomaly_detection --action install --param-file opengauss.json
+```
+
+卸载命令示例：
+
+```bash
+python3 ai_manager --module anomaly_detection--action uninstall --param-file opengauss.json
+```
+
+参数文件示例：
+
+```json
+{
+  "scene": "mogdb",                                       # 场景，mogdb安装server及agent,huaweiyun仅安装server
+  "module": "anomaly_detection",                              # 模块（特性）名称，目前仅支持anomaly_detection
+  "action": "install",                                        # 操作类型，支持install及uninstall
+  "ca_info": {
+    "ca_cert_path": "/home/Ruby/CA_AI/ca.crt",                # 根证书路径
+    "ca_key_path": "/home/Ruby/CA_AI/ca.crt.key",             # 根证书秘钥路径
+    "ca_password": "GHJAyusa241~"                             # 根证书密码
+  },
+  "agent_nodes": [
+    {
+      "node_ip": "10.000.00.000",                             # agent节点IP
+      "username": "Ruby",                                     # agent节点用户
+      "password": "password"                                  # agent节点密码
+    }
+  ],
+  "config_info": {
+    "server": {
+      "host": "10.000.00.000",                                # server部署节点IP（执行节点）
+      "listen_host": "0.0.0.0",                               # server 监听IP
+      "listen_port": "20060",                                 # server 监听端口
+      "pull_kafka": "False"                                   # 是否拉取kafka数据，暂不支持拉取。
+    },
+    "database": {
+      "name": "sqlite",                                       # 数据存储方式，支持sqlite、mongodb、influxdb
+      "host": "127.0.0.1",                                    # 数据库ip
+      "port": "2937",                                         # 数据库端口
+      "user": "Ruby",                                         # 数据库用户
+      "size": "175000000",                                    # mongodb 最大存储容量
+      "max_rows": "1000000"                                   # mongodb 最大存储条数
+    },
+    "agent": {
+      "cluster_name": "my_cluster",                           # 采集数据库的名称
+      "collection_type": "os",                                # 采集类型，支持os、database、all
+      "collection_item": [["dn", "10.000.00.000", "33700"]],  # agent节点采集数据类型（dn/cn），采集节点IP，端口
+      "channel_capacity": "1000",                             # 队列容量
+      "source_timer_interval": "5S",                          # 采集间隔
+      "sink_timer_interval": "5S"                             # 发送间隔
+    },
+    "security": {
+      "tls": "True"                                           # 是否开启https
+    }
+  }
+}
+```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/6-index-advisor-index-recommendation/6-1-single-query-index-recommendation.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/6-index-advisor-index-recommendation/6-1-single-query-index-recommendation.md
new file mode 100644
index 0000000000000000000000000000000000000000..b24139d0ea67517c70e4c90900695910c6ecc188
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/6-index-advisor-index-recommendation/6-1-single-query-index-recommendation.md
@@ -0,0 +1,61 @@
+---
+title: 单query索引推荐
+summary: 单query索引推荐
+author: Guo Huan
+date: 2021-05-19
+---
+
+# 单query索引推荐
+
+单query索引推荐功能支持用户在数据库中直接进行操作，本功能基于查询语句的语义信息和数据库的统计信息，对用户输入的单条查询语句生成推荐的索引。本功能涉及的函数接口如下。
+
+**表 1** 单query索引推荐功能的接口
+
+| 函数名          | 参数          | 功能                           |
+| :-------------- | :------------ | :----------------------------- |
+| gs_index_advise | SQL语句字符串 | 针对单条查询语句生成推荐索引。 |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 本功能仅支持单条SELECT类型的语句，不支持其他类型的SQL语句。
+> - 本功能暂不支持分区表、列存表、段页式表、普通视图、物化视图、全局临时表以及密态数据库。
+
+<br/>
+
+## 使用方法
+
+使用上述函数，获取针对该query生成的推荐索引，推荐结果由索引的表名和列名组成。
+
+例如：
+
+```sql
+mogdb=> select "table", "column" from gs_index_advise('SELECT c_discount from bmsql_customer where c_w_id = 10');
+     table      |  column
+----------------+----------
+ bmsql_customer | (c_w_id)
+(1 row)
+```
+
+上述结果表明：应当在 bmsql_customer 的 c_w_id 列上创建索引，例如可以通过下述SQL语句创建索引：
+
+```sql
+CREATE INDEX idx on bmsql_customer(c_w_id);
+```
+
+某些SQL语句，也可能被推荐创建联合索引，例如：
+
+```sql
+mogdb=# select "table", "column" from gs_index_advise('select name, age, sex from t1 where age >= 18 and age < 35 and sex = ''f'';');
+ table | column
+-------+------------
+ t1    | (age, sex)
+(1 row)
+```
+
+则上述语句表明应该在表 t1 上创建一个联合索引 (age, sex)， 则可以通过下述命令创建：
+
+```sql
+CREATE INDEX idx1 on t1(age, sex);
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 系统函数 gs_index_advise() 的参数是文本型，如果参数中存在如单引号（'） 等特殊字符，可以使用单引号（'） 进行转义，可参考上述示例。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/6-index-advisor-index-recommendation/6-2-virtual-index.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/6-index-advisor-index-recommendation/6-2-virtual-index.md
new file mode 100644
index 0000000000000000000000000000000000000000..5c212af60434e04114e4c3ba729d11bdc2262559
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/6-index-advisor-index-recommendation/6-2-virtual-index.md
@@ -0,0 +1,125 @@
+---
+title: 虚拟索引
+summary: 虚拟索引
+author: Guo Huan
+date: 2021-05-19
+---
+
+# 虚拟索引
+
+虚拟索引功能支持用户在数据库中直接进行操作，本功能将模拟真实索引的建立，避免真实索引创建所需的时间和空间开销，用户基于虚拟索引，可通过优化器评估该索引对指定查询语句的代价影响。
+
+本功能涉及的系统函数接口如下表所示：
+
+**表 1** 虚拟索引功能的接口
+
+| 函数名               | 参数                 | 功能                             |
+| :------------------- | :------------------- | :------------------------------- |
+| hypopg_create_index  | 创建索引语句的字符串 | 创建虚拟索引。                   |
+| hypopg_display_index | 无                   | 显示所有创建的虚拟索引信息。     |
+| hypopg_drop_index    | 索引的oid            | 删除指定的虚拟索引。             |
+| hypopg_reset_index   | 无                   | 清除所有虚拟索引。               |
+| hypopg_estimate_size | 索引的oid            | 估计指定索引创建所需的空间大小。 |
+
+本功能涉及的GUC参数如下：
+
+**表 2** 虚拟索引功能的GUC参数
+
+| 参数名            | 功能                 | 默认值 |
+| :---------------- | :------------------- | :----- |
+| enable_hypo_index | 是否开启虚拟索引功能 | off    |
+
+<br/>
+
+## 使用步骤
+
+1. 使用函数hypopg_create_index创建虚拟索引。例如：
+
+   ```sql
+   mogdb=> select * from hypopg_create_index('create index on bmsql_customer(c_w_id)');
+    indexrelid |              indexname
+   ------------+-------------------------------------
+        329726 | <329726>btree_bmsql_customer_c_w_id
+   (1 row)
+   ```
+
+2. 开启GUC参数enable_hypo_index，该参数控制数据库的优化器进行EXPLAIN时是否考虑创建的虚拟索引。通过对特定的查询语句执行explain，用户可根据优化器给出的执行计划评估该索引是否能够提升该查询语句的执行效率。例如：
+
+   ```sql
+   mogdb=> set enable_hypo_index = on;
+   SET
+   ```
+
+   开启GUC参数前，执行EXPLAIN + 查询语句：
+
+   ```sql
+   mogdb=> explain SELECT c_discount from bmsql_customer where c_w_id = 10;
+                                 QUERY PLAN
+   ----------------------------------------------------------------------
+    Seq Scan on bmsql_customer  (cost=0.00..52963.06 rows=31224 width=4)
+      Filter: (c_w_id = 10)
+   (2 rows)
+   ```
+
+   开启GUC参数后，执行EXPLAIN + 查询语句：
+
+   ```sql
+   mogdb=> explain SELECT c_discount from bmsql_customer where c_w_id = 10;
+                                                       QUERY PLAN
+   ------------------------------------------------------------------------------------------------------------------
+    [Bypass]
+    Index Scan using <329726>btree_bmsql_customer_c_w_id on bmsql_customer  (cost=0.00..39678.69 rows=31224 width=4)
+      Index Cond: (c_w_id = 10)
+   (3 rows)
+   ```
+
+   通过对比两个执行计划可以观察到，该索引预计会降低指定查询语句的执行代价，用户可考虑创建对应的真实索引。
+
+3. （可选）使用函数hypopg_display_index展示所有创建过的虚拟索引。例如：
+
+   ```sql
+   mogdb=> select * from hypopg_display_index();
+                    indexname                  | indexrelid |     table      |      column
+   --------------------------------------------+------------+----------------+------------------
+    <329726>btree_bmsql_customer_c_w_id        |     329726 | bmsql_customer | (c_w_id)
+    <329729>btree_bmsql_customer_c_d_id_c_w_id |     329729 | bmsql_customer | (c_d_id, c_w_id)
+   (2 rows)
+   ```
+
+4. （可选）使用函数hypopg_estimate_size估计虚拟索引创建所需的空间大小（单位：字节）。例如：
+
+   ```sql
+   mogdb=> select * from hypopg_estimate_size(329730);
+    hypopg_estimate_size
+   ----------------------
+                15687680
+   (1 row)
+   ```
+
+5. 删除虚拟索引。
+
+   使用函数hypopg_drop_index删除指定oid的虚拟索引。例如：
+
+   ```sql
+   mogdb=> select * from hypopg_drop_index(329726);
+    hypopg_drop_index
+   -------------------
+    t
+   (1 row)
+   ```
+
+   使用函数hypopg_reset_index一次性清除所有创建的虚拟索引。例如：
+
+   ```sql
+   mogdb=> select * from hypopg_reset_index();
+    hypopg_reset_index
+   --------------------
+
+   (1 row)
+   ```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 执行EXPLAIN ANALYZE不会涉及虚拟索引功能。
+> - 创建的虚拟索引是数据库实例级别的，各个会话（session）之间可共享设置，关闭会话后虚拟索引仍可存在，但是重启数据库后将被清空。
+> - 本功能暂不支持视图、物化视图、列存表。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/6-index-advisor-index-recommendation/6-3-workload-level-index-recommendation.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/6-index-advisor-index-recommendation/6-3-workload-level-index-recommendation.md
new file mode 100644
index 0000000000000000000000000000000000000000..b3c1a085fb5f9c97e5d48b1249232b01fa10716d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/6-index-advisor-index-recommendation/6-3-workload-level-index-recommendation.md
@@ -0,0 +1,112 @@
+---
+title: Workload-level Index Recommendation
+summary: Workload-level Index Recommendation
+author: Guo Huan
+date: 2021-05-19
+---
+
+# workload级别索引推荐
+
+对于workload级别的索引推荐，用户可通过运行数据库外的脚本使用此功能，本功能将包含有多条DML语句的workload作为输入，最终生成一批可对整体workload的执行表现进行优化的索引。同时，本功能提供从日志中抽取业务数据SQL流水的功能。
+
+<br/>
+
+## 前提条件
+
+- 数据库状态正常、客户端能够正常连接。
+
+- 当前执行用户下安装有gsql工具，该工具路径已被加入到PATH环境变量中。
+
+- 具备Python3.6+的环境。
+
+- 若使用本功能提供的业务数据抽取功能，需提前将要收集的节点的GUC参数按如下设置：
+
+  - log_min_duration_statement = 0
+
+  - log_statement= 'all'
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+    > 业务数据抽取完毕建议将上述GUC参数复原，否则容易导致日志文件膨胀。
+
+<br/>
+
+## 业务数据抽取脚本使用步骤
+
+1. 按前提条件中要求设置相关GUC参数。
+
+2. 运行python脚本extract_log.py，命令如下：
+
+   ```
+   python extract_log.py [l LOG_DIRECTORY] [f OUTPUT_FILE] [-d DATABASE] [-U USERNAME][--start_time] [--sql_amount] [--statement] [--json]
+   ```
+
+   其中的输入参数依次为：
+
+   - LOG_DIRECTORY：pg_log的存放目录。
+   - OUTPUT_PATH：输出SQL流水文件文件的保存路径，即抽取出的业务数据存放的文件路径。
+   - DATABASE：（可选）数据库名称，不指定默认所有数据库。
+   - USERNAME：（可选）用户名称，不指定默认所有用户。
+   - start_time：（可选）日志收集的开始时间， 不指定默认所有文件。
+   - sql_amount：（可选）收集SQL数量的最大值， 不指定默认收集所有SQL。
+   - statement：（可选）表示收集pg_log日志中statement标识开头的SQL，不指定默认不收集。
+   - json：指定收集日志的文件存储格式为SQL归一化后的json，不指定默认格式每条SQL占一行。
+
+   使用示例：
+
+   ```
+   python extract_log.py $GAUSSLOG/pg_log/dn_6001 sql_log.txt -d postgres -U omm --start_time '2021-07-06 00:00:00' --statement
+   ```
+
+3. 将步骤1中设置的GUC参数还原为设置前的值。
+
+<br/>
+
+## 索引推荐脚本使用步骤
+
+1. 准备好包含有多条DML语句的文件作为输入的workload，文件中每条语句占据一行。用户可从数据库的离线日志中获得历史的业务语句。
+
+2. 运行python脚本index_advisor_workload.py，命令如下：
+
+   ```python
+   python index_advisor_workload.py [p PORT] [d DATABASE] [f FILE] [--h HOST] [-U USERNAME] [-W PASSWORD][--schema SCHEMA][--max_index_num MAX_INDEX_NUM][--max_index_storage MAX_INDEX_STORAGE] [--multi_iter_mode] [--multi_node]  [--json] [--driver] [--show_detail]
+   ```
+
+   其中的输入参数依次为：
+
+   - PORT：连接数据库的端口号。
+   - DATABASE：连接数据库的名字。
+   - FILE：包含workload语句的文件路径。
+   - HOST：（可选）连接数据库的主机号。
+   - USERNAME：（可选）连接数据库的用户名。
+   - PASSWORD：（可选）连接数据库用户的密码。
+   - SCHEMA：模式名称。
+   - MAX_INDEX_NUM：（可选）最大的索引推荐数目。
+   - MAX_INDEX_STORAGE：（可选）最大的索引集合空间大小。
+   - multi_node：（可选）指定当前是否为分布式数据库实例。
+   - multi_iter_mode：（可选）算法模式，可通过是否设置该参数来切换算法。
+   - json：（可选）指定workload语句的文件路径格式为SQL归一化后的json，默认格式每条SQL占一行。
+   - driver：（可选）指定是否使用python驱动器连接数据库，默认gsql连接。
+   - show_detail：（可选）是否显示当前推荐索引集合的详细优化信息。
+
+   例如：
+
+   ```python
+    python index_advisor_workload.py 6001 postgres tpcc_log.txt --max_index_num 10 --multi_iter_mode
+   ```
+
+   推荐结果为一批索引，以多个创建索引语句的格式显示在屏幕上，结果示例。
+
+   ```sql
+   create index ind0 on public.bmsql_stock(s_i_id,s_w_id);
+   create index ind1 on public.bmsql_customer(c_w_id,c_id,c_d_id);
+   create index ind2 on public.bmsql_order_line(ol_w_id,ol_o_id,ol_d_id);
+   create index ind3 on public.bmsql_item(i_id);
+   create index ind4 on public.bmsql_oorder(o_w_id,o_id,o_d_id);
+   create index ind5 on public.bmsql_new_order(no_w_id,no_d_id,no_o_id);
+   create index ind6 on public.bmsql_customer(c_w_id,c_d_id,c_last,c_first);
+   create index ind7 on public.bmsql_new_order(no_w_id);
+   create index ind8 on public.bmsql_oorder(o_w_id,o_c_id,o_d_id);
+   create index ind9 on public.bmsql_district(d_w_id);
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** multi_node参数需严格按照当前数据库架构进行指定，否则推荐结果不全，甚至导致无推荐结果。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/7-deepsql/7-1-overview.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/7-deepsql/7-1-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..438893d620997fe6f918063984f3696dd7feba38
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/7-deepsql/7-1-overview.md
@@ -0,0 +1,108 @@
+---
+title: 概述
+summary: 概述
+author: Guo Huan
+date: 2021-05-19
+---
+
+# 概述
+
+数据库DeepSQL特性实现DB4AI功能，即在数据库内实现AI算法，以更好的支撑大数据的快速分析和计算。这里提供了一整套基于SQL的机器学习、数据挖掘以及统计学的算法，用户可以直接使用SQL进行机器学习工作。Deep SQL能够抽象出端到端从数据到模型的研发过程，配合底层的引擎及自动优化，具备基础SQL知识的技术人员即可完成大部分的机器学习模型训练及预测任务。整个分析和处理都运行在数据库引擎中，用户可以直接分析和处理数据库内的数据，不需要在数据库和其它平台之间进行数据传递，避免在多个环境之间进行不必要地数据移动。
+
+DeepSQL是对MogDB DB4AI能力的增强，让对MADLib比较熟悉的数据分析师或开发者可以轻松迁移到MogDB上进行工作。DeepSQL将常用的机器学习算法封装为SQL语句，支持60多个常用算法。其中包括回归算法（例如线性回归，逻辑回归，随机森林等）、分类算法（比如KNN等）、聚类算法（比如K-means）等。除了基础的机器学习算法之外，还包括图相关的算法，比如最短路径，图形直径等等算法；此外还支持数据处理（比如PCA），稀疏向量，统计学常用算法（比如协方差，Pearson系数计算等），训练集测试集分割方法，交叉验证方法等。
+
+**表 1** 支持的机器学习算法 - 回归类算法
+
+| 算法中文名称    | 算法英文名称                        | 应用场景                                                     |
+| :-------------- | :---------------------------------- | :----------------------------------------------------------- |
+| 逻辑回归        | Logistic Regression                 | 例如寻找某疾病的危险因素，金融商业机构需要对企业进行评估等。<br/>预测：根据模型预测不同的自变量情况下某病或某情况的发生概率。<br/>判别：实际上跟预测类似，也是根据模型判断某人属于某病或属于某种情况的概率有多大，即判断某人有多大可能是属于某病。 |
+| Cox比例风险回归 | Cox Proportional Hazards Regression | 该模型以生存结局和生存时间为因变量，可同时分析众多因素对生存期的影响，能分析带有截尾生存时间的资料，且不要求估计资料的生存分布类型。由于上述优良性质，该模型自问世以来，在医学类研究中得到广泛的应用，是迄今生存分析中应用最多的多因素分析方法。 |
+| 弹性网络回归    | Elastic Net Regularization          | 弹性回归是岭回归和套索回归的混合技术，它同时使用 L2 和 L1 正则化。当有多个相关的特征时，套索回归很可能随机选择其中一个，而弹性回归很可能都会选择。 |
+| 广义线性模型    | Generalized Linear Models           | 在一些实际问题中，变量间的关系并不都是线性的，这种情况就应该用曲线去进行拟合。 |
+| 边际效应        | Marginal Effects                    | 提供边际效应的计算。                                         |
+| 多类回归        | Multinomial Regression              | 如果目标类别数超过两个，这时就需要使用多类回归，如疗效可能是“无效”，“显效”，“痊愈”三类。 |
+| 序数回归        | Ordinal Regression                  | 在统计学中，序数回归是一种用于预测序数变量的回归分析，即其值存在于任意范围内的变量，不同值之间的度量距离也不同。它可以被认为是介于回归和分类之间的一类问题。例如，病情的分级（1、2、3、4级），症状的感觉分级（不痛、微痛、较痛和剧痛），对药物剂量反应的分级（无效、微效、中效和高效）等等。不同级别之间的差异不一定相等，如不痛与微痛的差值不一定等于较痛与剧痛的差值。 |
+| 聚类方差        | Clustered Variance                  | Clustered Variance模块调整聚类的标准误差。例如，将一个数据集合复制100次，不应该增加参数估计的精度，但是在符合独立同分布假设（Independent Identically Distributed，IID）下执行这个过程实际上会提高精度。 |
+| 稳健方差        | Robust Variance                     | Robust Variance模块中的函数用于计算线性回归、逻辑回归、多类逻辑回归和Cox比例风险回归的稳健方差（Huber-White估计）。它们可用于计算具有潜在噪声异常值的数据集中数据的差异。 |
+| 支持向量机      | Support Vector Machines(SVM)        | 用于文本和超文本的分类、图像分类，比起传统的查询优化方案，支持向量机能够获取明显更高的搜索准确度。这同样也适用于图像分割系统。 |
+| 线性回归        | Linear Regression                   | 应用广泛，例如经济学、金融学等。                             |
+
+**表 2** 支持的机器学习算法 - 其他监督学习
+
+| 算法名称（中文） | 算法名称（英文）               | 应用场景                                                     |
+| :--------------- | :----------------------------- | :----------------------------------------------------------- |
+| 决策树           | Decision Tree                  | 最为广泛的归纳推理算法之一，处理类别型或连续型变量的分类预测问题，可以用图形和if-then的规则表示模型，可读性较高。 |
+| 随机森林         | Random Forest                  | 随机森林是一类专门为决策树分类器设计的组合方法。它组合多棵决策树作出的预测。 |
+| 条件随机场       | Conditional Random Field (CRF) | 条件随机场（CRF）是一种判别的，无向概率的图形模型。线性链CRF是一种特殊类型的CRF，它假定当前状态仅取决于先前的状态。在分词、词性标注和命名实体识别等序列标注任务中取得了很好的效果。 |
+| 朴素贝叶斯       | Naive Bayes                    | 通过计算概率来进行分类，可以用来处理多分类问题，比如：垃圾邮件过滤器。 |
+| 神经网络         | Neural Networks                | 拥有广泛的应用场景，譬如语音识别、图像识别、机器翻译等等。在模式识别的领域中算是标准监督学习算法，并在计算神经学中，持续成为被研究的课题。MLP已被证明是一种通用的函数近似方法，可以被用来拟合复杂的函数或解决分类问题。 |
+| k临近算法        | k-Nearest Neighbors            | K近邻分类方法通过计算每个训练样例到待分类样品的距离，取和待分类样品距离最近的K个训练样例，K个样品中哪个类别的训练样例占多数，则待分类元组就属于哪个类别。<br/>可用于：文字识别，面部识别，基因模式识别，客户流失预测、欺诈侦测。 |
+
+**表 3** 支持的机器学习算法 - 数据处理类算法
+
+| 算法名称（中文） | 算法名称（英文）               | 应用场景                                                     |
+| :--------------- | :----------------------------- | :----------------------------------------------------------- |
+| 数组操作         | Array Operations               | 数组、向量操作运算，包括基础的加减乘除、幂运算、开方、cos、sin、绝对值、方差等。 |
+| 主成成分分析     | Dimensionality Reduction (PCA) | 降维，计算主成分。                                           |
+| 变量编码         | Encoding Categorical Variables | 当前支持one-hot和dummy编码技术。<br/>当需要用一组特定的预测变量与其它预测变量组作比较时，通常使用哑编码（dummy coding），与之比较的变量组称为参照组。One-hot编码与哑编码类似，两者的区别是前者为每种分类值建立数字类型的0/1指示列。在每行数据中（对应一个数据点），只有一个分类编码列的值可以为1。 |
+| 矩阵操作         | Matrix Operations              | 运用矩阵分解，将大型矩阵分解成简单矩阵的乘积形式，则可大大降低计算的难度以及计算量。矩阵加减乘除、最值、均值、求秩、求逆、矩阵分解(QR，LU，Cholesky)，特征提取。 |
+| 规范化和距离函数 | Norms and Distance Functions   | 求范数，余弦相似度，向量间距离。                             |
+| 稀疏向量         | Sparse Vectors                 | 实现稀疏向量类型，如果向量中重复值较多，可以用来压缩储存节省空间。 |
+| 透视图           | Pivot                          | 透视表或枢轴表，通常用来实现OLAP或报表系统中一类常见的行列转置需求。pivot函数能够对一个表中存储的数据执行基本行转列操作，并将汇总后的结果输出到另一个表中。使行列转置操作变得更为简单与灵活。 |
+| 模式匹配         | Path                           | 是在一系列行上执行常规模式匹配，并提取有关模式匹配的有用信息。有用的信息可以是简单的匹配计数或更多涉及的内容，如聚合或窗口函数。 |
+| 会话             | Sessionize                     | 会话化功能对包括事件序列的数据集执行面向时间的会话重建。定义的不活动时段表示一个会话的结束和下一个会话的开始。<br/>可以用于：网络分析，网络安全，制造，财务和运营分析。 |
+| 共轭梯度法       | Conjugate gradient             | 求解系数矩阵为对称正定矩阵的线性方程组的数值解的方法。       |
+| 词干提取         | Stemming                       | 词干提取简单说就是找出单词中的词干部分，场景比如：搜索引擎建立网页主题概念。在英文网站优化作用明显，对其他语言有借鉴意义。 |
+| 训练集测试集分割 | Train-Test Split               | 分割数据集，把一份数据集划分成训练集和测试集，train的部分用于训练，test部分用于验证。 |
+| 交叉验证         | Cross Validation               | 交叉验证。                                                   |
+| 预测指标         | Prediction Metrics             | 用于评估模型预测的质量，包括均方误差，AUC值、混淆矩阵、修正R方等用于评价模型的函数。 |
+| 小批量预处理     | Mini-Batch Preprocessor        | 把数据打包成小份进行训练，优点是它可以比随机梯度下降（默认MADlib优化器）表现更好，会更快更平滑的收敛。 |
+
+**表 4** 支持的机器学习算法 - 图类
+
+| 算法名称（中文）   | 算法名称（英文）                      | 应用场景                                                     |
+| :----------------- | :------------------------------------ | :----------------------------------------------------------- |
+| 所有对间最短路径   | All Pairs Shortest Path (APSP)        | 所有对最短路径（APSP）算法找到所有顶点对之间的最短路径的长度（总和权重），使得路径边缘的权重之和最小化。 |
+| 广度优先算法       | Breadth-First Search                  | 广度优先算法遍历路径。                                       |
+| 超链接诱导主题搜索 | Hyperlink-Induced Topic Search (HITS) | HITS算法输出每个节点的authority评分和hub评分，其中authority评分给出页面内容的分数，hub评估出连接到其他页面的分数。 |
+| 平均路径长度       | Average Path Length                   | 此函数计算每对顶点之间的最短路径的平均值。平均路径长度基于“可到达的目标顶点”，因此它忽略了未连接的顶点之间的无限长度路径。 |
+| 中心性             | Closeness Centrality                  | 接近度度量是和的倒数，平均值的倒数，以及到所有可到达目标顶点（不包括源顶点）的最短距离的倒数之和。 |
+| 图表直径           | Graph Diameter                        | 直径被定义为图中所有最短路径中最长的。                       |
+| 入度出度           | In-Out Degree                         | 计算图中每个点的入度出度，入度指指向此点的边的数量，出度指此点指向其他点的边的数量。 |
+| 网页排名           | PageRank                              | 给定图形，PageRank算法输出概率分布，该概率分布表示随机遍历图形的人将到达任何特定顶点的可能性。 |
+| 单源最短路径       | Single Source Shortest Path (SSSP)    | 给定图形和源顶点，单源最短路径（SSSP）算法找到从源顶点到图中的每个其他顶点的路径，使得路径边缘的权重之和最小化（每条边权值非负）。 |
+| 弱连通分量         | Weakly Connected Component            | 给定有向图，弱连通分量（WCC）是原始图的子图，其中所有顶点通过某个路径彼此连接，忽略边的方向。在无向图的情况下，弱连通分量也是强连通分量。该模块还包括许多在WCC输出上运行的辅助函数。 |
+
+**表 5** 支持的机器学习算法 - 时间序列
+
+| 算法名称（中文）           | 算法名称（英文）                                      | 应用场景                                                     |
+| :------------------------- | :---------------------------------------------------- | :----------------------------------------------------------- |
+| 差分整合移动平均自回归模型 | Autoregressive Integrated Moving Average model(ARIMA) | 时间序列预测，用于理解和预测一系列数据的未来值。<br/>比如：国际航空旅客数据，预测旅客人数。 |
+
+**表 6** 支持的机器学习算法 - 采样
+
+| 算法名称（中文） | 算法名称（英文）    | 应用场景                                                     |
+| :--------------- | :------------------ | :----------------------------------------------------------- |
+| 采样函数         | sample              | 抽样。                                                       |
+| 分层抽样         | Stratified Sampling | 分层随机抽样，又称类型随机抽样，它是先将总体各单位按一定标准分成各种类型（或层）；然后根据各类型单位数与总体单位数的比例，确定从各类型中抽取样本单位的数量；最后，按照随机原则从各类型中抽取样本。 |
+| 对称抽样         | Balanced Sampling   | 一些分类算法仅在每个类中的样本数大致相同时才最佳地执行。高度偏斜的数据集在许多领域中是常见的（例如，欺诈检测），因此重新采样以抵消这种不平衡可以产生更好的决策边界。 |
+
+**表 7** 支持的机器学习算法 - 统计学
+
+| 算法名称（中文） | 算法名称（英文）                 | 应用场景                                                     |
+| :--------------- | :------------------------------- | :----------------------------------------------------------- |
+| 汇总统计函数     | Summary                          | 生成任何数据表的摘要统计信息。                               |
+| 协方差和相关系数 | Correlation and Covariance       | 描述性统计，求Pearson系数，相关系数，另一个输出协方差。了解数据从统计学上反映的量的特征，以便我们更好地认识这些将要被挖掘的数据。 |
+| 统计频率算法     | CountMin (Cormode-Muthukrishnan) | 统计一个实时的数据流中元素出现的频率，并且准备随时回答某个元素出现的频率，不需要的精确的计数。 |
+| 基数估计算法     | FM (Flajolet-Martin)             | 获取指定列中的不同值的数量。 找出这个数字集合中不重复的数字的个数。 |
+| 最频繁值         | MFV (Most Frequent Values)       | 计算频繁值的场景。                                           |
+| 假设检验         | Hypothesis Tests                 | 包含F-test，chi2-test等。                                    |
+| 概率函数         | Probability Functions            | 概率函数模块为各种概率分布提供累积分布，密度、质量和分位数函数。 |
+
+**表 8** 支持的机器学习算法 - 其他算法
+
+| 算法名称（中文） | 算法名称（英文）                  | 应用场景                                                     |
+| :--------------- | :-------------------------------- | :----------------------------------------------------------- |
+| k-聚类算法       | K-means                           | 聚类场景。                                                   |
+| 隐含狄利克雷分布 | Latent Dirichlet Allocation (LDA) | LDA 在主题模型中占有非常重要的地位，常用来文本分类。         |
+| 关联规则算法     | Apriori Algorithm                 | 关联规则算法，关联规则挖掘的目标是发现数据项集之间的关联关系。比如经典的“啤酒和尿布”。 |
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/7-deepsql/7-2-environment-deployment.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/7-deepsql/7-2-environment-deployment.md
new file mode 100644
index 0000000000000000000000000000000000000000..2898d749d3b137178157b054035432140ca89f41
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/7-deepsql/7-2-environment-deployment.md
@@ -0,0 +1,119 @@
+---
+title: 环境部署
+summary: 环境部署
+author: Guo Huan
+date: 2021-05-19
+---
+
+# 环境部署
+
+DeepSQL环境包括编译数据库和安装算法库两个部分。
+
+<br/>
+
+## 前提条件
+
+- 环境中安装python2.7.12以上版本Python。
+- 数据库需要开启对PL/Python存储过程的支持。
+- 安装算法库需要拥有管理员权限的用户。
+
+<br/>
+
+## 操作步骤
+
+1. 检查部署Python环境。
+
+   安装前，请查看系统安装的python版本，当前DeepSQL需要python2.7.12以上版本的环境。
+
+   - 如果当前系统python2版本高于2.7.12，可以直接安装python-devel包。
+   - 如果版本过低，或者无法安装python-devel包，可以下载最新python2源码，手动配置编译python2，并配置环境变量。
+
+   算法库中，部分算法调用了python包，如numpy，pandas等。用户可以安装以下python库：
+
+   ```bash
+   pip install numpy
+   pip install pandas
+   pip install scipy
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+   >
+   > - 如果自行编译python，需要在**configure**脚本执行时加入**-enable-shared**参数；
+   > - 如果系统中的python2使用的是UCS4编码，自行编译python2时，还需要加入**-enable-unicode=ucs4**参数。 可以在系统中自带的python2下执行：“import sys；print sys.maxunicode”并查看结果，如果结果是65535，说明系统默认的是ucs2；如果结果是1114111，说明用的ucs4编码。
+   > - 如果系统中内置的python2使用的ucs4，说明系统中的gdb，gstack等也会依赖ucs4。因此自行编译的python2在configure时，需要添加-enable-unicode=ucs4，否则后续使用gdb，gstack时，会遇到报错。
+
+2. 编译部署数据库。
+
+   数据库需要开启对PL/Python存储过程的支持。默认编译数据库，不包含此模块。因此需要编译数据库时，在configure阶段，加入--with-python参数；
+
+   其他编译保持步骤不变；
+
+   编译完成后，需要重新gs_initdb；
+
+   默认PL/Python存储过程模块不被加载，请执行“CREATE EXTENSION plpythonu”来加载模块。
+
+3. 算法库编译和安装。
+
+   算法库使用开源的MADlib机器学习框架。源码包和相应patch可以从第三方库的代码仓库里获取。安装命令如下：
+
+   ```bash
+   tar -zxf apache-madlib-1.17.0-src.tar.gz
+   cp madlib.patch apache-madlib-1.17.0-src
+   cd apache-madlib-1.17.0-src/
+   patch -p1 < madlib.patch
+   ```
+
+   编译命令如下：
+
+   ```bash
+   ./configure -DCMAKE_INSTALL_PREFIX={YOUR_MADLIB_INSTALL_FOLDER}
+   -DPOSTGRESQL_EXECUTABLE=$GAUSSHOME/bin/
+   -DPOSTGRESQL_9_2_EXECUTABLE=$GAUSSHOME/bin/
+   -DPOSTGRESQL_9_2_CLIENT_INCLUDE_DIR=$GAUSSHOME/bin/
+   -DPOSTGRESQL_9_2_SERVER_INCLUDE_DIR=$GAUSSHOME/bin/
+   # 以上均为configure命令。
+   make
+   make install
+   ```
+
+   其中， {YOUR_MADLIB_INSTALL_FOLDER}需要改为用户的实际安装路径。
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 编译MADlib时，会联网下载依赖软件。无法联网时，需要手动下载依赖包“PyXB-1.2.6.tar.gz”，“eigen-branches-3.2.tar.gz”和“boost_1_61_0.tar.gz”放在本地。使用的configure命令如下：
+   >
+   > ```bash
+   > ./configure -DCMAKE_INSTALL_PREFIX={YOUR_MADLIB_INSTALL_FOLDER}                  # your install folder
+   > -DPYXB_TAR_SOURCE={YOUR_DEPENDENCY_FOLDER}/PyXB-1.2.6.tar.gz                     # change to your local folder
+   > -DEIGEN_TAR_SOURCE={YOUR_DEPENDENCY_FOLDER}/eigen-branches-3.2.tar.gz      # change to your local folder
+   > -DBOOST_TAR_SOURCE={YOUR_DEPENDENCY_FOLDER}/boost_1_61_0.tar.gz              # change to your local folder
+   > -DPOSTGRESQL_EXECUTABLE=$GAUSSHOME/bin/
+   > -DPOSTGRESQL_9_2_EXECUTABLE=$GAUSSHOME/bin/
+   > -DPOSTGRESQL_9_2_CLIENT_INCLUDE_DIR=$GAUSSHOME/bin/
+   > -DPOSTGRESQL_9_2_SERVER_INCLUDE_DIR=$GAUSSHOME/bin/
+   > ```
+
+4. 将算法库安装到数据库中。
+
+   a. 进入{YOUR_MADLIB_INSTALL_FOLDER}路径。
+
+   b. 进入bin文件夹。
+
+   c. 执行如下命令。
+
+      ```bash
+      ./madpack -s <SCHEMA_NAME> -p mogdb -c <USER_NAME>@127.0.0.1:<PORT>/<DATABASE_NAME> install
+      ```
+
+      命令中参数说明如下：
+
+      - -s：schema的名称。
+      - -p：数据库平台，使用mogdb即可。
+      - -c：连接数据库的参数。包括用户名、‘@’、IP地址、端口号和目标数据库名称。
+
+      install为安装的命令，除此之外，还有reinstall（重新安装），uninstall（卸载）等命令可用。
+
+      > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+      >
+      > - 目标数据库必须存在。
+      > - IP请使用127.0.0.1，不要使用localhost。
+      > - 涉及到大量PL/Python存储过程的安装、卸载等操作，需要数据库管理员权限用户来进行，普通用户没有权限创建和修改PL/Python存储过程，只能调用。
+      > - 数据库兼容性，推荐兼容性为B。不同的数据库兼容性下，对空值，NULL等处理有较大差异。建议使用B兼容性。例如，`CREATE DATABASE dbcompatibility='B'`。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/7-deepsql/7-3-usage-guide.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/7-deepsql/7-3-usage-guide.md
new file mode 100644
index 0000000000000000000000000000000000000000..5233799af9f668d861466363160efcaf751e2487
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/7-deepsql/7-3-usage-guide.md
@@ -0,0 +1,246 @@
+---
+title: Usage Guide
+summary: Usage Guide
+author: Guo Huan
+date: 2021-05-19
+---
+
+# 使用指导
+
+<br/>
+
+## PL/Python存储过程
+
+当前PL/Python存储过程优先支持python2；默认版本也是python2。
+
+PL/Python中的函数通过标准的CREATE FUNCTION声明：
+
+```sql
+CREATE FUNCTION funcname (argument-list)
+RETURNS return-type
+AS $$
+# PL/Python function body
+$$ LANGUAGE plpythonu;
+```
+
+函数体是一个简单的Python脚本，当函数被调用的时候，它的参数作为列表args的元素传递；命名参数也会被当做普通的变量传递到Python脚本中。命名参数的使用通常更易读。 结果将使用return或yield（结果集语句的情况） 照常从Python代码中返回。如果没有提供返回值，Python返回缺省的None。 PL/Python将Python中的None认为SQL空值。
+
+例如，返回两个整数中较大者的函数定义如下。
+
+```sql
+CREATE FUNCTION pymax(a integer, b integer) RETURNS integer AS $$
+if a > b:
+    return a
+return b
+$$ LANGUAGE plpythonu;
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **注意：**
+>
+> - PL/Python函数中，后缀为plpythonu。'u’说明是untrusted类型的存储过程。
+> - Trusted：这个语言不能访问越权的数据。例如，数据库服务器的文件、数据库内部（包括直接访问共享内存）。
+> - Untrusted：这个语言没有任何限制，允许访问任何数据（包括文件，网络，共享LIB库等，危害性较大），但是功能更加强大。
+> - PL/Python属于untrusted类型的存储过程语言，当前仅允许管理员权限的用户创建和修改，普通用户仅支持使用。
+> - 定义PL/Python存储过程时，注意不要定义执行诸如import os；os.system(“rm -rf /") 等危险语句。管理员权限的用户需要小心创建此类PL/Python存储过程。
+
+<br/>
+
+## 数据库Null, None和空串处理
+
+如果向函数传递了一个SQL null值，参数值在Python中将会显示为None。在数据库中，不同的兼容性下，空串的行为会被当做NULL处理。
+
+同一个函数，在不同的兼容性下表现不同。
+
+```sql
+CREATE FUNCTION quote(t text, how text) RETURNS text AS $$
+if how == "literal":
+    return plpy.quote_literal(t)
+elif how == "nullable":
+    return plpy.quote_nullable(t)
+elif how == "ident":
+    return plpy.quote_ident(t)
+else:
+    raise plpy.Error("unrecognized quote type %s" % how)
+$$ LANGUAGE plpythonu;
+```
+
+**示例1：**
+
+```sql
+SELECT quote(t, 'literal') FROM (VALUES ('abc'),('a''bc'),('''abc'''),(''),(''''),('xyzv')) AS v(t);
+```
+
+数据库不同兼容性下的结果为：
+
+- 兼容性为A时，返回结果如下：
+
+  ```sql
+  ERROR:  TypeError: argument 1 must be string, not None
+  CONTEXT:  Traceback (most recent call last):
+  PL/Python function "quote", line 3, in <module>
+  return plpy.quote_literal(t)
+  referenced column: quote
+  ```
+
+- 兼容性为B时，返回结果如下：
+
+  ```sql
+  quote
+  -----------
+  'abc'
+  'a''bc'
+  '''abc'''
+  ''
+  ''''
+  'xyzv'
+  (6 rows)
+  ```
+
+**示例2：**
+
+```sql
+SELECT quote(t, 'nullable') FROM (VALUES ('abc'),('a''bc'),('''abc'''),(''),(''''),(NULL)) AS v(t);
+```
+
+数据库不同兼容性下的结果为：
+
+- 兼容性为A时，返回结果如下：
+
+  ```sql
+  quote
+  -----------
+  'abc'
+  'a''bc'
+  '''abc'''
+  NULL
+  ''''
+  NULL
+  (6 rows)
+  ```
+
+- 兼容性为B时，返回结果如下：
+
+  ```sql
+  quote
+  -----------
+  'abc'
+  'a''bc'
+  '''abc'''
+  ''
+  ''''
+  NULL
+  (6 rows)
+  ```
+
+可以看到，在兼容性“A”中，空串被当为NULL了。
+
+<br/>
+
+## 触发器
+
+当前PL/Python存储过程中，不支持触发器功能。
+
+<br/>
+
+## 匿名代码块
+
+PL/Python也支持DO声明的匿名代码块：
+
+```sql
+DO $$
+# PL/Python code
+$$ LANGUAGE plpythonu;
+```
+
+一个匿名代码块不接受参数，并且丢弃它可能返回的值。
+
+<br/>
+
+## 共享数据
+
+每个函数都在Python解释器里获得自己的执行环境。
+
+全局字典SD在函数调用之间用于存储数据。这些变量是私有静态数据。每一个函数都有自己的SD数据空间，函数A的全局数据和函数参数是函数B不可用的。
+
+全局字典GD是公共数据，在一个gsql会话中，所有python函数都可访问和改变，使用时需要小心。
+
+当gsql断开或退出，共享数据就被释放。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **注意：**
+>
+> - 运行DeepSQL或者PL/Python存储过程时，需要关闭线程池相关参数。否则PL/Python存储过程中的Sharing Data（“GD”、“SD”)等功能会失效。
+> - 在数据库中，当线程池功能关闭，每一个连入的gsql，数据库内会起一个新的线程去处理。在gsql中，如果调用到PL/Python存储过程，会在本线程中完成python解析器模块的初始化，其中包括初始化“GD”，“SD”等共享空间。
+> - 在线程池功能开启的状态下，一个gsql执行时，由当前空闲线程执行，每次执行可能分配到不同的线程上。导致共享数据紊乱。
+
+<br/>
+
+## 数据库访问
+
+PL/Python语言模块自动import一个叫plpy的Python模块。
+
+plpy模块提供几个函数执行数据库命令：比如plpy.execute，plpy.prepare等。
+
+plpy模块也提供了函数plpy.debug(**msg**)、 plpy.log(**msg**)、plpy.info(**msg**)、 plpy.notice(**msg**)、plpy.warning(**msg**)、 plpy.error(**msg**)和plpy.fatal(**msg**)。 plpy.error和 plpy.fatal实际上抛出了一个Python异常，会导致当前事务或者子事务退出。
+
+另一个实用函数集是plpy.quote_literal(string)、 plpy.quote_nullable(string)和 plpy.quote_ident(string)。
+
+<br/>
+
+## 关于审计
+
+PL/Python存储过程支持审计功能。具体设置可以参考[审计](1-audit-switch)。
+
+<br/>
+
+## 关于并发执行
+
+当前PL/Python存储过程对并发执行不友好，建议串行执行。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 由于MogDB是多线程架构，C-python中，由于GIL锁（Global Interpreter Lock)的限制，多线程在Python中只能交替执行，无法做到真正的并发。
+
+<br/>
+
+## 库内算法
+
+具体库内算法介绍和使用，可参考MADlib官方网站（[MADlib文档](http://madlib.apache.org/docs/latest/index.html)）。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+>
+> - 当前仅支持机器学习算法，不支持深度学习（deep learning)模块。
+> - 当前数据库不支持xml，所以pmml模块和相关功能不支持。
+> - 数据库不支持jsonb模块，json格式的模型导出功能也不支持。
+
+<br/>
+
+## 其他算法支持
+
+除了MADlib提供的算法外，MogDB又额外提供了以下三个算法。
+
+**表 1** 额外增加的模块列表
+
+| 算法名称（中文）   | 算法名称（英文） |
+| :----------------- | :--------------- |
+| 梯度提升树         | gbdt             |
+| 梯度提升           | xgboost          |
+| 时间序列预测的算法 | facebook_prophet |
+
+使用时，需要安装依赖的python库：
+
+- 如果使用prophet算法：
+
+  ```bash
+  pip install pystan
+  pip install holidays==0.9.8
+  pip install fbprophet==0.3.post2
+  ```
+
+- 如果使用xgboost算法：
+
+  ```bash
+  pip install xgboost
+  pip install scikit-learn
+  ```
+
+- gbdt不需要额外安装其他库。
+
+详细操作请参考[最佳实践](7-4-best-practices)。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/7-deepsql/7-4-best-practices.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/7-deepsql/7-4-best-practices.md
new file mode 100644
index 0000000000000000000000000000000000000000..502bad8910db6d1705a61a76c5ba6ae6eb3d4398
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/7-deepsql/7-4-best-practices.md
@@ -0,0 +1,902 @@
+---
+title: Best Practices
+summary: Best Practices
+author: Guo Huan
+date: 2021-05-19
+---
+
+# 最佳实践
+
+本章节介绍部分算法的使用，主要包含分类、回归、聚类、gbdt算法、xgboost算法和prohpet算法。
+
+首先需要创建一个数据库，并安装算法。
+
+```sql
+create database test1 dbcompatibility='B';
+./madpack -s madlib -p mogdb -c opg@127.0.0.1:7651/test1 install
+```
+
+<br/>
+
+## 分类算法
+
+以svm分类房价为例子：
+
+1. 数据集准备。
+
+   ```sql
+   DROP TABLE IF EXISTS houses;
+   CREATE TABLE houses (id INT, tax INT, bedroom INT, bath FLOAT, price INT,  size INT, lot INT);
+   INSERT INTO houses VALUES
+   (1 ,  590 ,       2 ,    1 ,  50000 ,  770 , 22100),
+   (2 , 1050 ,       3 ,    2 ,  85000 , 1410 , 12000),
+   (3 ,   20 ,       3 ,    1 ,  22500 , 1060 ,  3500),
+   (4 ,  870 ,       2 ,    2 ,  90000 , 1300 , 17500),
+   (5 , 1320 ,       3 ,    2 , 133000 , 1500 , 30000),
+   (6 , 1350 ,       2 ,    1 ,  90500 ,  820 , 25700),
+   (7 , 2790 ,       3 ,  2.5 , 260000 , 2130 , 25000),
+   (8 ,  680 ,       2 ,    1 , 142500 , 1170 , 22000),
+   (9 , 1840 ,       3 ,    2 , 160000 , 1500 , 19000),
+   (10 , 3680 ,       4 ,    2 , 240000 , 2790 , 20000),
+   (11 , 1660 ,       3 ,    1 ,  87000 , 1030 , 17500),
+   (12 , 1620 ,       3 ,    2 , 118600 , 1250 , 20000),
+   (13 , 3100 ,       3 ,    2 , 140000 , 1760 , 38000),
+   (14 , 2070 ,       2 ,    3 , 148000 , 1550 , 14000),
+   (15 ,  650 ,       3 ,  1.5 ,  65000 , 1450 , 12000);
+   ```
+
+2. 模型训练。
+
+   训练前配置相应schema和兼容性参数：
+
+   ```sql
+   SET search_path="$user",public,madlib;
+   SET behavior_compat_options = 'bind_procedure_searchpath';
+   ```
+
+   使用默认的参数进行训练，分类的条件为‘price &lt; 100000’，SQL语句如下：
+
+   ```sql
+   DROP TABLE IF EXISTS houses_svm, houses_svm_summary;
+   SELECT madlib.svm_classification('public.houses','public.houses_svm','price < 100000','ARRAY[1, tax, bath, size]');
+   ```
+
+3. 查看模型。
+
+   ```sql
+   \x on
+   SELECT * FROM houses_svm;
+   \x off
+   ```
+
+   结果如下：
+
+   ```sql
+   -[ RECORD 1 ]------+-----------------------------------------------------------------
+   coef               | {.113989576847,-.00226133300602,-.0676303607996,.00179440841072}
+   loss               | .614496714256667
+   norm_of_gradient   | 108.171180769224
+   num_iterations     | 100
+   num_rows_processed | 15
+   num_rows_skipped   | 0
+   dep_var_mapping    | {f,t}
+   ```
+
+4. 进行预测。
+
+   ```sql
+   DROP TABLE IF EXISTS houses_pred;
+   SELECT madlib.svm_predict('public.houses_svm','public.houses','id','public.houses_pred');
+   ```
+
+   - 查看预测结果
+
+     ```sql
+     SELECT *, price < 100000 AS actual FROM houses JOIN houses_pred USING (id) ORDER BY id;
+     ```
+
+     结果如下：
+
+     ```sql
+      id | tax  | bedroom | bath | price  | size |  lot  | prediction | decision_function | actual
+     ----+------+---------+------+--------+------+-------+------------+-------------------+--------
+      1 |  590 |       2 |    1 |  50000 |  770 | 22100 | t          |      .09386721875 | t
+      2 | 1050 |       3 |    2 |  85000 | 1410 | 12000 | t          |     .134445058042 | t
+      3 |   20 |       3 |    1 |  22500 | 1060 |  3500 | t          |   1.9032054712902 | t
+      4 |  870 |       2 |    2 |  90000 | 1300 | 17500 | t          |    .3441000739464 | t
+      5 | 1320 |       3 |    2 | 133000 | 1500 | 30000 | f          |   -.3146180966186 | f
+      6 | 1350 |       2 |    1 |  90500 |  820 | 25700 | f          |  -1.5350254452892 | t
+      7 | 2790 |       3 |  2.5 | 260000 | 2130 | 25000 | f          |  -2.5421154971142 | f
+      8 |  680 |       2 |    1 | 142500 | 1170 | 22000 | t          |    .6081106124962 | f
+      9 | 1840 |       3 |    2 | 160000 | 1500 | 19000 | f          |   -1.490511259749 | f
+     10 | 3680 |       4 |    2 | 240000 | 2790 | 20000 | f          |   -3.336577140997 | f
+     11 | 1660 |       3 |    1 |  87000 | 1030 | 17500 | f          |  -1.8592129109042 | t
+     12 | 1620 |       3 |    2 | 118600 | 1250 | 20000 | f          |  -1.4416201011046 | f
+     13 | 3100 |       3 |    2 | 140000 | 1760 | 38000 | f          |   -3.873244660547 | f
+     14 | 2070 |       2 |    3 | 148000 | 1550 | 14000 | f          |  -1.9885277913972 | f
+     15 |  650 |       3 |  1.5 |  65000 | 1450 | 12000 | t          |   1.1445697772786 | t
+     (15 rows)
+     ```
+
+   - 查看误分率
+
+     ```sql
+     SELECT COUNT(*) FROM houses_pred JOIN houses USING (id) WHERE houses_pred.prediction != (houses.price < 100000);
+     ```
+
+     结果如下：
+
+     ```sql
+     count
+     -------
+          3
+     (1 row)
+     ```
+
+5. 使用svm其他核进行训练。
+
+   ```sql
+   DROP TABLE IF EXISTS houses_svm_gaussian, houses_svm_gaussian_summary, houses_svm_gaussian_random;
+   SELECT madlib.svm_classification( 'public.houses','public.houses_svm_gaussian','price < 100000','ARRAY[1, tax, bath, size]','gaussian','n_components=10', '', 'init_stepsize=1, max_iter=200' );
+   ```
+
+   进行预测，并查看训练结果。
+
+   ```sql
+   DROP TABLE IF EXISTS houses_pred_gaussian;
+   SELECT madlib.svm_predict('public.houses_svm_gaussian','public.houses','id', 'public.houses_pred_gaussian');
+   SELECT COUNT(*) FROM houses_pred_gaussian JOIN houses USING (id) WHERE houses_pred_gaussian.prediction != (houses.price < 100000);
+   ```
+
+   结果如下。
+
+   ```sql
+    count
+   -------+
+   0
+   (1 row)
+   ```
+
+6. 其他参数
+
+   除了指定不同的核方法外，还可以指定迭代次数，初始参数，比如init_stepsize, max_iter, class_weight等。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+>
+> ```sql
+> SET search_path="$user",public,madlib;
+> SET behavior_compat_options = 'bind_procedure_searchpath';
+> ```
+>
+> 执行算法前，需要设置search_path中schema，另外需要bind_procedure_searchpath，否则出现表找不到的情况。因为机器学习所有的方法安装在一个schema中，用户的表安装在用户的schema中，在这个例子中，算法安装在madlib中，用户表放置在public中。如果不设置，可能会出现执行算法时，找不到表的情况。执行算法时，建议把输入表的schema也加进去。
+
+<br/>
+
+## 回归算法
+
+我们以线性回归预测波士顿房价为例：
+
+1. 数据集准备。
+
+   同svm的数据集。
+
+2. 训练模型。
+
+   ```sql
+   SET search_path="$user",public,madlib;
+   SET behavior_compat_options = 'bind_procedure_searchpath';
+
+   DROP TABLE IF EXISTS houses_linregr, houses_linregr_summary;
+   SELECT madlib.linregr_train( 'public.houses', 'public.houses_linregr',  'price', 'ARRAY[1, tax, bath, size]');
+   ```
+
+3. 查看模型内容。
+
+   ```sql
+   \x ON
+   SELECT * FROM houses_linregr;
+   \x OFF
+   ```
+
+   返回结果如下。
+
+   ```sql
+   -[ RECORD 1 ]------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+   coef                     | {-12849.4168959872,28.9613922651775,10181.6290712649,50.516894915353}
+   r2                       | .768577580597462
+   std_err                  | {33453.0344331377,15.8992104963991,19437.7710925915,32.9280231740856}
+   t_stats                  | {-.384103179688204,1.82156166004197,.523806408809163,1.53416118083608}
+   p_values                 | {.708223134615411,.0958005827189556,.610804093526516,.153235085548177}
+   condition_no             | 9002.50457069858
+   num_rows_processed       | 15
+   num_missing_rows_skipped | 0
+   variance_covariance      | {{1119105512.7847,217782.067878005,-283344228.394538,-616679.693190829},{217782.067878005,252.784894408806,-46373.1796964038,-369.864520095145},{-283344228.394538,-46373.1796964038,377826945.047986,-209088.217319699},{-616679.693190829,-369.864520095145,-209088.217319699,1084.25471015312}}
+   ```
+
+4. 预测，并对比结果。
+
+   ```sql
+   SELECT houses.*,
+       madlib.linregr_predict( m.coef, ARRAY[1,tax,bath,size]) as predict,
+       price - madlib.linregr_predict( m.coef, ARRAY[1,tax,bath,size]) as residual
+   FROM public.houses, public.houses_linregr AS m
+   ORDER BY id;
+   ```
+
+   返回结果如下。
+
+   ```sql
+    id | tax  | bedroom | bath | price  | size |  lot  |     predict      |     residual
+   ----+------+---------+------+--------+------+-------+------------------+-------------------
+    1 |  590 |       2 |    1 |  50000 |  770 | 22100 | 53317.4426965543 | -3317.44269655428
+    2 | 1050 |       3 |    2 |  85000 | 1410 | 12000 | 109152.124955627 | -24152.1249556268
+    3 |   20 |       3 |    1 |  22500 | 1060 |  3500 | 51459.3486308555 | -28959.3486308555
+    4 |  870 |       2 |    2 |  90000 | 1300 | 17500 |  98382.215907206 | -8382.21590720599
+    5 | 1320 |       3 |    2 | 133000 | 1500 | 30000 | 121518.221409606 |  11481.7785903935
+    6 | 1350 |       2 |    1 |  90500 |  820 | 25700 | 77853.9455638568 |  12646.0544361432
+    7 | 2790 |       3 |  2.5 | 260000 | 2130 | 25000 | 201007.926371722 |  58992.0736282778
+    8 |  680 |       2 |    1 | 142500 | 1170 | 22000 | 76130.7259665615 |  66369.2740334385
+    9 | 1840 |       3 |    2 | 160000 | 1500 | 19000 | 136578.145387499 |  23421.8546125013
+   10 | 3680 |       4 |    2 | 240000 | 2790 | 20000 | 255033.901596231 | -15033.9015962306
+   11 | 1660 |       3 |    1 |  87000 | 1030 | 17500 | 97440.5250982859 | -10440.5250982859
+   12 | 1620 |       3 |    2 | 118600 | 1250 | 20000 | 117577.415360321 |  1022.58463967856
+   13 | 3100 |       3 |    2 | 140000 | 1760 | 38000 | 186203.892319614 | -46203.8923196141
+   14 | 2070 |       2 |    3 | 148000 | 1550 | 14000 | 155946.739425522 | -7946.73942552213
+   15 |  650 |       3 |  1.5 |  65000 | 1450 | 12000 | 94497.4293105374 | -29497.4293105374
+   (15 rows)
+   ```
+
+<br/>
+
+## 聚类算法
+
+以kmeans为例：
+
+1. 准备数据。
+
+   ```sql
+   DROP TABLE IF EXISTS km_sample;
+   CREATE TABLE km_sample(pid int, points double precision[]);
+   INSERT INTO km_sample VALUES
+   (1,  '{14.23, 1.71, 2.43, 15.6, 127, 2.8, 3.0600, 0.2800, 2.29, 5.64, 1.04, 3.92, 1065}'),
+   (2,  '{13.2, 1.78, 2.14, 11.2, 1, 2.65, 2.76, 0.26, 1.28, 4.38, 1.05, 3.49, 1050}'),
+   (3,  '{13.16, 2.36,  2.67, 18.6, 101, 2.8,  3.24, 0.3, 2.81, 5.6799, 1.03, 3.17, 1185}'),
+   (4,  '{14.37, 1.95, 2.5, 16.8, 113, 3.85, 3.49, 0.24, 2.18, 7.8, 0.86, 3.45, 1480}'),
+   (5,  '{13.24, 2.59, 2.87, 21, 118, 2.8, 2.69, 0.39, 1.82, 4.32, 1.04, 2.93, 735}'),
+   (6,  '{14.2, 1.76, 2.45, 15.2, 112, 3.27, 3.39, 0.34, 1.97, 6.75, 1.05, 2.85, 1450}'),
+   (7,  '{14.39, 1.87, 2.45, 14.6, 96, 2.5, 2.52, 0.3, 1.98, 5.25, 1.02, 3.58, 1290}'),
+   (8,  '{14.06, 2.15, 2.61, 17.6, 121, 2.6, 2.51, 0.31, 1.25, 5.05, 1.06, 3.58, 1295}'),
+   (9,  '{14.83, 1.64, 2.17, 14, 97, 2.8, 2.98, 0.29, 1.98, 5.2, 1.08, 2.85, 1045}'),
+   (10, '{13.86, 1.35, 2.27, 16, 98, 2.98, 3.15, 0.22, 1.8500, 7.2199, 1.01, 3.55, 1045}');
+   ```
+
+2. 运行kmeans算法。
+
+   使用kmeans++进行计算，距离函数使用欧几里得距离。
+
+   ```sql
+   SET search_path="$user",public,madlib;
+   SET behavior_compat_options = 'bind_procedure_searchpath';
+
+   DROP TABLE IF EXISTS km_result;
+   CREATE TABLE km_result AS SELECT * FROM madlib.kmeanspp( 'public.km_sample',   -- Table of source data
+                                                            'points',      -- Column containing point co-ordinates
+                                                            2,             -- Number of centroids to calculate
+                                                            'madlib.squared_dist_norm2',   -- Distance function
+                                                            'madlib.avg',  -- Aggregate function
+                                                            20,            -- Number of iterations
+                                                            0.001          -- Fraction of centroids reassigned to keep iterating
+   );
+   ```
+
+   kmeans执行完后，不会自动创建表保存内容，所以需要用户自行创建table。
+
+   ```sql
+   \x on
+    select * from km_result;
+   \x off
+   ```
+
+   返回结果如下。
+
+   ```sql
+   -[ RECORD 1 ]----+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+   centroids        | {{14.0333333333333,1.84111111111111,2.41,15.5111111111111,96.2222222222222,2.91666666666667,3.01111111111111,.282222222222222,1.95444444444444,5.88553333333333,1.02222222222222,3.38222222222222,1211.66666666667},{13.24,2.59,2.87,21,118,2.8,2.69,.39,1.82,4.32,1.04,2.93,735}}
+   cluster_variance | {257041.999707571,0}
+   objective_fn     | 257041.999707571
+   frac_reassigned  | 0
+   num_iterations   | 2
+   ```
+
+3. 应用聚类结果。
+
+   执行以下函数，计算每个节点的临近节点和相应距离。
+
+   ```sql
+   DROP TABLE IF EXISTS km_points_silh;
+   SELECT * FROM madlib.simple_silhouette_points('public.km_sample',          -- Input points table
+                                                 'public.km_points_silh',      -- Output table
+                                                 'pid',                 -- Point ID column in input table
+                                                 'points',              -- Points column in input table
+                                                 'public.km_result',           -- Centroids table
+                                                 'centroids',           -- Column in centroids table containing centroids
+                                                 'madlib.squared_dist_norm2'   -- Distance function
+   );
+   SELECT * FROM km_points_silh ORDER BY pid;
+   ```
+
+   返回结果如下。
+
+   ```sql
+    pid | centroid_id | neighbor_centroid_id |       silh
+   -----+-------------+----------------------+------------------
+     1 |           0 |                    1 | .793983543638996
+     2 |           0 |                    1 | .688301735667703
+     3 |           0 |                    1 | .996324103148159
+     4 |           0 |                    1 | .869765755931474
+     5 |           1 |                    0 |                1
+     6 |           0 |                    1 | .888416176253661
+     7 |           0 |                    1 | .980107240092519
+     8 |           0 |                    1 | .975880363039906
+     9 |           0 |                    1 | .712384473959954
+    10 |           0 |                    1 | .712198411442872
+   (10 rows)
+   ```
+
+<br/>
+
+## gbdt算法
+
+gdbt的基学习器虽然是回归树，但算法本身支持分类和回归两种操作。以下将展示两种任务的具体实现。这里值得注意的一点是，本方法不支持标签列含有空值（NULL）的情况。
+
+**分类任务**：
+
+1. 准备数据。
+
+   ```sql
+   DROPTABLEIFEXISTS dt_golf CASCADE;
+   DROPTABLEIFEXISTS train_output,train_output_summary;
+   CREATETABLE dt_golf (
+       id integerNOTNULL,
+   "OUTLOOK"text,
+       temperature double precision,
+       humidity double precision,
+   "Cont_features"double precision[],
+       cat_features text[],
+       windy boolean,
+       class integer
+   ) ;
+   INSERTINTO dt_golf (id,"OUTLOOK",temperature,humidity,"Cont_features",cat_features, windy,class) VALUES
+   (1, 'sunny', 85, 85,ARRAY[85, 85], ARRAY['a', 'b'], false, 0),
+   (2, 'sunny', 80, 90, ARRAY[80, 90], ARRAY['a', 'b'], true, 0),
+   (3, 'overcast', 83, 78, ARRAY[83, 78], ARRAY['a', 'b'], false, 1),
+   (4, 'rain', 70, NULL, ARRAY[70, 96], ARRAY['a', 'b'], false, 1),
+   (5, 'rain', 68, 80, ARRAY[68, 80], ARRAY['a', 'b'], false, 1),
+   (6, 'rain', NULL, 70, ARRAY[65, 70], ARRAY['a', 'b'], true, 0),
+   (7, 'overcast', 64, 65, ARRAY[64, 65], ARRAY['c', 'b'], NULL , 1),
+   (8, 'sunny', 72, 95, ARRAY[72, 95], ARRAY['a', 'b'], false, 0),
+   (9, 'sunny', 69, 70, ARRAY[69, 70], ARRAY['a', 'b'], false, 1),
+   (10, 'rain', 75, 80, ARRAY[75, 80], ARRAY['a', 'b'], false, 1),
+   (11, 'sunny', 75, 70, ARRAY[75, 70], ARRAY['a', 'd'], true, 1),
+   (12, 'overcast', 72, 90, ARRAY[72, 90], ARRAY['c', 'b'], NULL, 1),
+   (13, 'overcast', 81, 75, ARRAY[81, 75], ARRAY['a', 'b'], false, 1),
+   (15, NULL, 81, 75, ARRAY[81, 75], ARRAY['a', 'b'], false, 1),
+   (16, 'overcast', NULL, 75, ARRAY[81, 75], ARRAY['a', 'd'], false,1),
+   (14, 'rain', 71, 80, ARRAY[71, 80], ARRAY['c', 'b'], true, 0);
+   ```
+
+2. 训练模型。
+
+   ```sql
+   select madlib.gbdt_train('dt_golf',         -- source table
+                     'train_output',    -- output model table
+                     'id'  ,            -- id column
+                     'class',           -- response
+                     '"OUTLOOK", temperature',          -- features
+                     NULL,        -- exclude columns
+                     1,       --weight
+                     10,                -- num of trees
+                     NULL,                 -- num of random features
+                     10,       -- max depth
+                     1,        -- min split
+                     1,        -- min bucket
+                     8,        -- number of bins per continuous variable
+                     'max_surrogates=0',
+                     TRUE
+   );
+   ```
+
+   模型训练结束会生成两个表，其中一张表train_output中保存着gdbt中的回归树模型，内容包括对每一个基学习器的参数记录。
+
+   ```sql
+          Column       |     Type      | Modifiers | Storage  | Stats target | Description
+   --------------------+---------------+-----------+----------+--------------+-------------
+   iteration          | integer       |           | plain    |              |
+   tree               | madlib.bytea8 |           | external |              |
+   cat_levels_in_text | text[]        |           | extended |              |
+   cat_n_levels       | integer[]     |           | extended |              |
+   tree_depth         | integer       |           | plain    |              |
+   ```
+
+   ```sql
+    iteration |  cat_levels_in_text   | cat_n_levels | tree_depth
+   -----------+-----------------------+--------------+------------
+           0 | {sunny,rain,overcast} | {3}          |          4
+           1 | {sunny,rain,overcast} | {3}          |          5
+           2 | {sunny,rain,overcast} | {3}          |          6
+           3 | {sunny,rain,overcast} | {3}          |          4
+           4 | {sunny,rain,overcast} | {3}          |          5
+           5 | {sunny,rain,overcast} | {3}          |          5
+           6 | {sunny,rain,overcast} | {3}          |          5
+           7 | {sunny,rain,overcast} | {3}          |          5
+           8 | {sunny,rain,overcast} | {3}          |          4
+           9 | {sunny,rain,overcast} | {3}          |          3
+   (10 rows)
+   ```
+
+   另一张表train_output_summary，内容是对gdbt训练的整体描述：
+
+   ```sql
+   select * from train_output_summary;
+    method | cat_features | con_features | source_table | model_table  | null_proxy | learning_rate | is_classification | predict_dt_prob | num_trees
+   --------+--------------+--------------+--------------+--------------+------------+---------------+-------------------+-----------------+-----------
+    GBDT   | "OUTLOOK"    | temperature  | dt_golf      | train_output |            |           .01 | t                 | response        |        10
+   (1 row)
+   ```
+
+3. 预测。
+
+   ```sql
+   select madlib.gbdt_predict('dt_golf2','train_output','test_output','id');
+   ```
+
+   查看预测结果
+
+   ```sql
+   select test_output.id, test_prediction,class from test_output join dt_golf using (id);
+   id | test_prediction | class
+   ----+-----------------+-------
+     1 |             1.0 |     0
+     2 |             1.0 |     0
+     3 |             1.0 |     1
+     4 |             1.0 |     1
+     5 |             1.0 |     1
+     6 |             1.0 |     0
+     7 |             1.0 |     1
+     8 |             0.0 |     0
+     9 |             1.0 |     1
+    10 |             1.0 |     1
+    11 |             1.0 |     1
+    12 |             1.0 |     1
+    13 |             1.0 |     1
+    15 |             0.0 |     1
+    16 |             1.0 |     1
+    14 |             0.0 |     0
+   (16 rows)
+   ```
+
+<br/>
+
+## 回归任务
+
+1. 准备数据。
+
+   ```sql
+   DROP TABLE IF EXISTS crime;
+   CREATE TABLE crime (
+       id SERIAL NOT NULL,
+       CrimeRat DOUBLE PRECISION,
+       MaleTeen INTEGER,
+       South SMALLINT,
+       Educ DOUBLE PRECISION,
+       Police60 INTEGER,
+       Police59 INTEGER,
+       Labor INTEGER,
+       Males INTEGER,
+       Pop   INTEGER,
+       NonWhite INTEGER,
+       Unemp1  INTEGER,
+       Unemp2  INTEGER,
+       Median  INTEGER,
+       BelowMed INTEGER
+   );
+
+   INSERT INTO crime(
+       CrimeRat, MaleTeen, South, Educ, Police60, Police59, Labor, Males, Pop,
+       NonWhite, Unemp1, Unemp2, Median, BelowMed
+   ) VALUES
+   (79.1, 151, 1, 9.1, 58, 56, 510, 950, 33, 301, 108, 41, 394, 261),
+   (163.5, 143, 0, 11.3, 103, 95, 583, 1012, 13, 102, 96, 36, 557, 194),
+   (57.8, 142, 1, 8.9, 45, 44, 533, 969, 18, 219, 94, 33, 318, 250),
+   (196.9, 136, 0, 12.1, 149, 141, 577, 994, 157, 80, 102, 39, 673, 167),
+   (123.4, 141, 0, 12.1, 109, 101, 591, 985, 18, 30, 91, 20, 578, 174),
+   (68.2, 121, 0, 11.0, 118, 115, 547, 964, 25, 44, 84, 29, 689, 126),
+   (96.3, 127, 1, 11.1, 82, 79, 519, 982, 4, 139, 97, 38, 620, 168),
+   (155.5, 131, 1, 10.9, 115, 109, 542, 969, 50, 179, 79, 35, 472, 206),
+   (85.6, 157, 1, 9.0, 65, 62, 553, 955, 39, 286, 81, 28, 421, 239),
+   (70.5, 140, 0, 11.8, 71, 68, 632, 1029, 7, 15, 100, 24, 526, 174),
+   (167.4, 124, 0, 10.5, 121, 116, 580, 966, 101, 106, 77, 35, 657, 170),
+   (84.9, 134, 0, 10.8, 75, 71, 595, 972, 47, 59, 83, 31, 580, 172),
+   (51.1, 128, 0, 11.3, 67, 60, 624, 972, 28, 10, 77, 25, 507, 206),
+   (66.4, 135, 0, 11.7, 62, 61, 595, 986, 22, 46, 77, 27, 529, 190),
+   (79.8, 152, 1, 8.7, 57, 53, 530, 986, 30, 72, 92, 43, 405, 264),
+   (94.6, 142, 1, 8.8, 81, 77, 497, 956, 33, 321, 116, 47, 427, 247),
+   (53.9, 143, 0, 11.0, 66, 63, 537, 977, 10, 6, 114, 35, 487, 166),
+   (92.9, 135, 1, 10.4, 123, 115, 537, 978, 31, 170, 89, 34, 631, 165),
+   (75.0, 130, 0, 11.6, 128, 128, 536, 934, 51, 24, 78, 34, 627, 135),
+   (122.5, 125, 0, 10.8, 113, 105, 567, 985, 78, 94, 130, 58, 626, 166),
+   (74.2, 126, 0, 10.8, 74, 67, 602, 984, 34, 12, 102, 33, 557, 195),
+   (43.9, 157, 1, 8.9, 47, 44, 512, 962, 22, 423, 97, 34, 288, 276),
+   (121.6, 132, 0, 9.6, 87, 83, 564, 953, 43, 92, 83, 32, 513, 227),
+   (96.8, 131, 0, 11.6, 78, 73, 574, 1038, 7, 36, 142, 42, 540, 176),
+   (52.3, 130, 0, 11.6, 63, 57, 641, 984, 14, 26, 70, 21, 486, 196),
+   (199.3, 131, 0, 12.1, 160, 143, 631, 1071, 3, 77, 102, 41, 674, 152),
+   (34.2, 135, 0, 10.9, 69, 71, 540, 965, 6, 4, 80, 22, 564, 139),
+   (121.6, 152, 0, 11.2, 82, 76, 571, 1018, 10, 79, 103, 28, 537, 215),
+   (104.3, 119, 0, 10.7, 166, 157, 521, 938, 168, 89, 92, 36, 637, 154),
+   (69.6, 166, 1, 8.9, 58, 54, 521, 973, 46, 254, 72, 26, 396, 237),
+   (37.3, 140, 0, 9.3, 55, 54, 535, 1045, 6, 20, 135, 40, 453, 200),
+   (75.4, 125, 0, 10.9, 90, 81, 586, 964, 97, 82, 105, 43, 617, 163),
+   (107.2, 147, 1, 10.4, 63, 64, 560, 972, 23, 95, 76, 24, 462, 233),
+   (92.3, 126, 0, 11.8, 97, 97, 542, 990, 18, 21, 102, 35, 589, 166),
+   (65.3, 123, 0, 10.2, 97, 87, 526, 948, 113, 76, 124, 50, 572, 158),
+   (127.2, 150, 0, 10.0, 109, 98, 531, 964, 9, 24, 87, 38, 559, 153),
+   (83.1, 177, 1, 8.7, 58, 56, 638, 974, 24, 349, 76, 28, 382, 254),
+   (56.6, 133, 0, 10.4, 51, 47, 599, 1024, 7, 40, 99, 27, 425, 225),
+   (82.6, 149, 1, 8.8, 61, 54, 515, 953, 36, 165, 86, 35, 395, 251),
+   (115.1, 145, 1, 10.4, 82, 74, 560, 981, 96, 126, 88, 31, 488, 228),
+   (88.0, 148, 0, 12.2, 72, 66, 601, 998, 9, 19, 84, 20, 590, 144),
+   (54.2, 141, 0, 10.9, 56, 54, 523, 968, 4, 2, 107, 37, 489, 170),
+   (82.3, 162, 1, 9.9, 75, 70, 522, 996, 40, 208, 73, 27, 496, 224),
+   (103.0, 136, 0, 12.1, 95, 96, 574, 1012, 29, 36, 111, 37, 622, 162),
+   (45.5, 139, 1, 8.8, 46, 41, 480, 968, 19, 49, 135, 53, 457, 249),
+   (50.8, 126, 0, 10.4, 106, 97, 599, 989, 40, 24, 78, 25, 593, 171),
+   (84.9, 130, 0, 12.1, 90, 91, 623, 1049, 3, 22, 113, 40, 588, 160);
+   ```
+
+2. 训练模型。
+
+   ```sql
+   select madlib.gbdt_train('crime',         -- source table
+                     'train_output',    -- output model table
+                     'id'  ,            -- id column
+                     'CrimeRat',           -- response
+                    '*',          -- features
+                     NULL,        -- exclude columns
+                     1,       --weight
+                     20,                -- num of trees
+                     4,                 -- num of random features
+                     10,       -- max depth
+                     1,        -- min split
+                     1,        -- min bucket
+                     8,        -- number of bins per continuous variable
+                     'max_surrogates=0',
+                     FALSE
+   );
+   ```
+
+   当is_classification设为FALSE时，模型为回归任务。默认状态下gbdt提供回归计算支持。方法生成两个表，其中一张表记录每棵树的集体信息和模型的二进制，一张表记录方法的参数信息。
+
+3. 预测。
+
+   ```sql
+   select madlib.gbdt_predict('crime','train_output','test_output','id');
+   ```
+
+   查看预测结果：
+
+   ```sql
+   select test_output.id, test_prediction,CrimeRat  from test_output join crime using (id);
+
+    id |  test_prediction   | crimerat
+   ----+--------------------+----------
+     1 |               79.1 |     79.1
+     2 |              163.5 |    163.5
+     3 |               57.8 |     57.8
+     4 |              196.9 |    196.9
+     5 |              123.4 |    123.4
+     6 |               68.2 |     68.2
+     7 |   96.2999999992251 |     96.3
+     8 | 155.49842087765936 |    155.5
+     9 |              84.35 |     85.6
+    10 |  70.50157912234037 |     70.5
+    11 |  167.4000000007749 |    167.4
+    12 |               84.9 |     84.9
+    13 |               51.1 |     51.1
+    14 |               66.4 |     66.4
+    15 |               79.8 |     79.8
+    16 |               94.6 |     94.6
+    17 |               53.9 |     53.9
+    18 |               92.9 |     92.9
+    19 |               75.0 |       75
+    20 |              122.5 |    122.5
+    21 |               74.2 |     74.2
+    22 |               43.9 |     43.9
+    23 |              121.6 |    121.6
+    24 |               96.8 |     96.8
+    25 |               52.3 |     52.3
+    26 |              199.3 |    199.3
+    27 |               34.2 |     34.2
+    28 |              121.6 |    121.6
+    29 |              104.3 |    104.3
+    30 |               69.6 |     69.6
+    31 |               37.3 |     37.3
+    32 |               75.4 |     75.4
+    33 |              107.2 |    107.2
+    34 |               92.3 |     92.3
+    35 |   65.2999999992251 |     65.3
+    36 | 127.19842087765963 |    127.2
+    37 |  84.35000000002215 |     83.1
+    38 |  56.60155638297881 |     56.6
+    39 |  82.45000000075257 |     82.6
+    40 | 115.10002273936168 |    115.1
+    41 |               88.0 |       88
+    42 |  54.19997726063828 |     54.2
+    43 |  82.44999999999999 |     82.3
+    44 | 103.00002273936173 |      103
+    45 | 45.500000000000156 |     45.5
+    46 |               50.8 |     50.8
+    47 |               84.9 |     84.9
+   (47 rows)
+   ```
+
+<br/>
+
+## xgboost算法
+
+新增的xgboost支持分类和回归两种操作。下面以分类iris花为例，展示xgboost算法。
+
+xgboost支持grid search方式，可以同时训练多组参数。
+
+1. 准备数据。
+
+   ```sql
+   DROP TABLE IF EXISTS iris;
+   create table iris (id serial, a float, d float, c float, b float, label int);
+
+   INSERT into iris (a, b, c, d, label) values
+   (5.1, 3.5, 1.4, 0.2, 0),(4.9, 3.0, 1.4, 0.2, 0),(4.7, 3.2, 1.3, 0.2, 0),(4.6, 3.1, 1.5, 0.2, 0),
+   (5.0, 3.6, 1.4, 0.2, 0),(5.4, 3.9, 1.7, 0.4, 0),(4.6, 3.4, 1.4, 0.3, 0),(5.0, 3.4, 1.5, 0.2, 0),
+   (4.4, 2.9, 1.4, 0.2, 0),(4.9, 3.1, 1.5, 0.1, 0),(5.4, 3.7, 1.5, 0.2, 0),(4.8, 3.4, 1.6, 0.2, 0),
+   (4.8, 3.0, 1.4, 0.1, 0),(4.3, 3.0, 1.1, 0.1, 0),(5.8, 4.0, 1.2, 0.2, 0),(5.7, 4.4, 1.5, 0.4, 0),
+   (5.4, 3.9, 1.3, 0.4, 0),(5.1, 3.5, 1.4, 0.3, 0),(5.7, 3.8, 1.7, 0.3, 0),(5.1, 3.8, 1.5, 0.3, 0),
+   (5.4, 3.4, 1.7, 0.2, 0),(5.1, 3.7, 1.5, 0.4, 0),(4.6, 3.6, 1.0, 0.2, 0),(5.1, 3.3, 1.7, 0.5, 0),
+   (4.8, 3.4, 1.9, 0.2, 0),(5.0, 3.0, 1.6, 0.2, 0),(5.0, 3.4, 1.6, 0.4, 0),(5.2, 3.5, 1.5, 0.2, 0),
+   (5.2, 3.4, 1.4, 0.2, 0),(4.7, 3.2, 1.6, 0.2, 0),(4.8, 3.1, 1.6, 0.2, 0),(5.4, 3.4, 1.5, 0.4, 0),
+   (5.2, 4.1, 1.5, 0.1, 0),(5.5, 4.2, 1.4, 0.2, 0),(4.9, 3.1, 1.5, 0.2, 0),(5.0, 3.2, 1.2, 0.2, 0),
+   (5.5, 3.5, 1.3, 0.2, 0),(4.9, 3.6, 1.4, 0.1, 0),(4.4, 3.0, 1.3, 0.2, 0),(5.1, 3.4, 1.5, 0.2, 0),
+   (5.0, 3.5, 1.3, 0.3, 0),(4.5, 2.3, 1.3, 0.3, 0),(4.4, 3.2, 1.3, 0.2, 0),(5.0, 3.5, 1.6, 0.6, 0),
+   (5.1, 3.8, 1.9, 0.4, 0),(4.8, 3.0, 1.4, 0.3, 0),(5.1, 3.8, 1.6, 0.2, 0),(4.6, 3.2, 1.4, 0.2, 0),
+   (5.3, 3.7, 1.5, 0.2, 0),(5.0, 3.3, 1.4, 0.2, 0),(7.0, 3.2, 4.7, 1.4, 1),(6.4, 3.2, 4.5, 1.5, 1),
+   (6.9, 3.1, 4.9, 1.5, 1),(5.5, 2.3, 4.0, 1.3, 1),(6.5, 2.8, 4.6, 1.5, 1),(5.7, 2.8, 4.5, 1.3, 1),
+   (6.3, 3.3, 4.7, 1.6, 1),(4.9, 2.4, 3.3, 1.0, 1),(6.6, 2.9, 4.6, 1.3, 1),(5.2, 2.7, 3.9, 1.4, 1),
+   (5.0, 2.0, 3.5, 1.0, 1),(5.9, 3.0, 4.2, 1.5, 1),(6.0, 2.2, 4.0, 1.0, 1),(6.1, 2.9, 4.7, 1.4, 1),
+   (5.6, 2.9, 3.6, 1.3, 1),(6.7, 3.1, 4.4, 1.4, 1),(5.6, 3.0, 4.5, 1.5, 1),(5.8, 2.7, 4.1, 1.0, 1),
+   (6.2, 2.2, 4.5, 1.5, 1),(5.6, 2.5, 3.9, 1.1, 1),(5.9, 3.2, 4.8, 1.8, 1),(6.1, 2.8, 4.0, 1.3, 1),
+   (6.3, 2.5, 4.9, 1.5, 1),(6.1, 2.8, 4.7, 1.2, 1),(6.4, 2.9, 4.3, 1.3, 1),(6.6, 3.0, 4.4, 1.4, 1),
+   (6.8, 2.8, 4.8, 1.4, 1),(6.7, 3.0, 5.0, 1.7, 1),(6.0, 2.9, 4.5, 1.5, 1),(5.7, 2.6, 3.5, 1.0, 1),
+   (5.5, 2.4, 3.8, 1.1, 1),(5.5, 2.4, 3.7, 1.0, 1),(5.8, 2.7, 3.9, 1.2, 1),(6.0, 2.7, 5.1, 1.6, 1),
+   (5.4, 3.0, 4.5, 1.5, 1),(6.0, 3.4, 4.5, 1.6, 1),(6.7, 3.1, 4.7, 1.5, 1),(6.3, 2.3, 4.4, 1.3, 1),
+   (5.6, 3.0, 4.1, 1.3, 1),(5.5, 2.5, 4.0, 1.3, 1),(5.5, 2.6, 4.4, 1.2, 1),(6.1, 3.0, 4.6, 1.4, 1),
+   (5.8, 2.6, 4.0, 1.2, 1),(5.0, 2.3, 3.3, 1.0, 1),(5.6, 2.7, 4.2, 1.3, 1),(5.7, 3.0, 4.2, 1.2, 1),
+   (5.7, 2.9, 4.2, 1.3, 1),(6.2, 2.9, 4.3, 1.3, 1),(5.1, 2.5, 3.0, 1.1, 1),(5.7, 2.8, 4.1, 1.3, 1),
+   (6.3, 3.3, 6.0, 2.5, 2),(5.8, 2.7, 5.1, 1.9, 2),(7.1, 3.0, 5.9, 2.1, 2),(6.3, 2.9, 5.6, 1.8, 2),
+   (6.5, 3.0, 5.8, 2.2, 2),(7.6, 3.0, 6.6, 2.1, 2),(4.9, 2.5, 4.5, 1.7, 2),(7.3, 2.9, 6.3, 1.8, 2),
+   (6.7, 2.5, 5.8, 1.8, 2),(7.2, 3.6, 6.1, 2.5, 2),(6.5, 3.2, 5.1, 2.0, 2),(6.4, 2.7, 5.3, 1.9, 2),
+   (6.8, 3.0, 5.5, 2.1, 2),(5.7, 2.5, 5.0, 2.0, 2),(5.8, 2.8, 5.1, 2.4, 2),(6.4, 3.2, 5.3, 2.3, 2),
+   (6.5, 3.0, 5.5, 1.8, 2),(7.7, 3.8, 6.7, 2.2, 2),(7.7, 2.6, 6.9, 2.3, 2),(6.0, 2.2, 5.0, 1.5, 2),
+   (6.9, 3.2, 5.7, 2.3, 2),(5.6, 2.8, 4.9, 2.0, 2),(7.7, 2.8, 6.7, 2.0, 2),(6.3, 2.7, 4.9, 1.8, 2),
+   (6.7, 3.3, 5.7, 2.1, 2),(7.2, 3.2, 6.0, 1.8, 2),(6.2, 2.8, 4.8, 1.8, 2),(6.1, 3.0, 4.9, 1.8, 2),
+   (6.4, 2.8, 5.6, 2.1, 2),(7.2, 3.0, 5.8, 1.6, 2),(7.4, 2.8, 6.1, 1.9, 2),(7.9, 3.8, 6.4, 2.0, 2),
+   (6.4, 2.8, 5.6, 2.2, 2),(6.3, 2.8, 5.1, 1.5, 2),(6.1, 2.6, 5.6, 1.4, 2),(7.7, 3.0, 6.1, 2.3, 2),
+   (6.3, 3.4, 5.6, 2.4, 2),(6.4, 3.1, 5.5, 1.8, 2),(6.0, 3.0, 4.8, 1.8, 2),(6.9, 3.1, 5.4, 2.1, 2),
+   (6.7, 3.1, 5.6, 2.4, 2),(6.9, 3.1, 5.1, 2.3, 2),(5.8, 2.7, 5.1, 1.9, 2),(6.8, 3.2, 5.9, 2.3, 2),
+   (6.7, 3.3, 5.7, 2.5, 2),(6.7, 3.0, 5.2, 2.3, 2),(6.3, 2.5, 5.0, 1.9, 2),(6.5, 3.0, 5.2, 2.0, 2),
+   (6.2, 3.4, 5.4, 2.3, 2),(5.9, 3.0, 5.1, 1.8, 2);
+   ```
+
+2. 执行分类训练操作。
+
+   ```sql
+   SET search_path="$user",public,madlib;
+   SET behavior_compat_options = 'bind_procedure_searchpath';
+   select madlib.xgboost_sk_Classifier('public.iris', 'public.iris_model_xgbc', 'id', 'label', 'a,b,c,d', NULL,
+   $${'booster': ['gbtree'], 'eta':   (0.1, 0.9), 'max_depth': (5,1), 'objective': ('multi:softmax',)}$$,   -- 训练参数组合，如果有多个参数，请用元组或者列表的方式传入
+   TRUE);                                  -- 是否评估模型，多分类评价为精确度和kappa值；二分类评价指标为precision, recall, fscore和support；回归评价指标为mae, mse, R2squared和rmse
+   ```
+
+   xgboost支持多组参数并行训练，比如用例中eta值为0.1和0.9，最大深度为5或者1。
+
+   ```sql
+   select id, train_timestamp, source_table, y_type, metrics, features, params from iris_model_xgbc;
+   ```
+
+   查看模型结果如下。
+
+   ```sql
+    id |        train_timestamp        | source_table | y_type  |          metrics           | features  |                                     params
+   ----+-------------------------------+--------------+---------+----------------------------+-----------+---------------------------------------------------------------------------------
+    1 | 2020-12-14 20:15:05.904184+08 | public.iris  | integer | {'acc': 1.0, 'kappa': 1.0} | {a,b,c,d} | ('objective = multi:softmax', 'eta = 0.1', 'max_depth = 5', 'booster = gbtree')
+    2 | 2020-12-14 20:15:05.904184+08 | public.iris  | integer | {'acc': 1.0, 'kappa': 1.0} | {a,b,c,d} | ('objective = multi:softmax', 'eta = 0.1', 'max_depth = 1', 'booster = gbtree')
+    3 | 2020-12-14 20:15:05.904184+08 | public.iris  | integer | {'acc': 1.0, 'kappa': 1.0} | {a,b,c,d} | ('objective = multi:softmax', 'eta = 0.9', 'max_depth = 5', 'booster = gbtree')
+    4 | 2020-12-14 20:15:05.904184+08 | public.iris  | integer | {'acc': 1.0, 'kappa': 1.0} | {a,b,c,d} | ('objective = multi:softmax', 'eta = 0.9', 'max_depth = 1', 'booster = gbtree')
+   (4 rows)
+   ```
+
+   结果表中，记录着训练时间，特征，结果类型，所用参数等。
+
+   在本示例函数输入中，eta选择为2种，max_depth选择为2种，总共4种参数组合。所以在结果中，有4行结果；在metrics列中，记录4种参数组合的训练后的评价结果。用户可以输入多种参数组合，训练后，用户可以选择合适的模型留下。
+
+3. 预测结果。
+
+   ```sql
+   select madlib.xgboost_sk_predict('public.iris', 'public.iris_model_xgbc', 'public.iris_xgbc_out', 'id');
+   select t1.id, prediction, label from iris as t1, iris_xgbc_out as t2 where t1.id = t2.id and prediction <> label;
+   ```
+
+   查看结果，预测和训练结果的对比，当前不匹配的行数为0，证明分类准确性较高。
+
+   ```sql
+    id | prediction | label
+   ----+------------+-------
+   (0 rows)
+   ```
+
+<br/>
+
+## prophet算法
+
+新增facebook的prophet时序预测算法。下面以时序数据为例，展示prophet算法使用。
+
+1. 准备数据。
+
+   ```sql
+   DROP TABLE IF EXISTS ts_data;
+   CREATE TABLE ts_data(date date, value float);
+
+   INSERT into ts_data (date, value) values
+   ('2016-11-29 21:20:00', 5.6),('2016-11-29 21:30:00', 5.2),('2016-11-29 21:40:00', 5.3),('2016-11-29 21:50:00', 5.3),
+   ('2016-11-29 22:00:00', 5.1),('2016-11-29 22:10:00', 5.8),('2016-11-29 22:20:00', 5.6),('2016-11-29 22:30:00', 5.4),
+   ('2016-11-29 22:40:00', 5.4),('2016-11-29 22:50:00', 5.1),('2016-11-29 23:00:00', 5.2),('2016-11-29 23:10:00', 5.9),
+   ('2016-11-29 23:20:00', 5.9),('2016-11-29 23:30:00', 5.1),('2016-11-29 23:40:00', 5.8),('2016-11-29 23:50:00', 6.0),
+   ('2016-11-30 00:00:00', 5.9),('2016-11-30 00:10:00', 5.3),('2016-11-30 00:20:00', 5.4),('2016-11-30 00:30:00', 5.1),
+   ('2016-11-30 00:40:00', 5.6),('2016-11-30 00:50:00', 5.7),('2016-11-30 01:00:00', 5.8),('2016-11-30 01:10:00', 5.4),
+   ('2016-11-30 01:20:00', 5.8),('2016-11-30 01:30:00', 5.1),('2016-11-30 01:40:00', 5.6),('2016-11-30 01:50:00', 5.6),
+   ('2016-11-30 02:00:00', 5.6),('2016-11-30 02:10:00', 5.9),('2016-11-30 02:20:00', 5.7),('2016-11-30 02:30:00', 5.4),
+   ('2016-11-30 02:40:00', 5.6),('2016-11-30 02:50:00', 5.4),('2016-11-30 03:00:00', 5.1),('2016-11-30 03:10:00', 5.0),
+   ('2016-11-30 03:20:00', 5.9),('2016-11-30 03:30:00', 5.8),('2016-11-30 03:40:00', 5.4),('2016-11-30 03:50:00', 5.7),
+   ('2016-11-30 04:00:00', 5.6),('2016-11-30 04:10:00', 5.9),('2016-11-30 04:20:00', 5.1),('2016-11-30 04:30:00', 5.8),
+   ('2016-11-30 04:40:00', 5.5),('2016-11-30 04:50:00', 5.1),('2016-11-30 05:00:00', 5.8),('2016-11-30 05:10:00', 5.5),
+   ('2016-11-30 05:20:00', 5.7),('2016-11-30 05:30:00', 5.2),('2016-11-30 05:40:00', 5.7),('2016-11-30 05:50:00', 6.0),
+   ('2016-11-30 06:00:00', 5.8),('2016-11-30 06:10:00', 5.6),('2016-11-30 06:20:00', 5.2),('2016-11-30 06:30:00', 5.8),
+   ('2016-11-30 06:40:00', 5.3),('2016-11-30 06:50:00', 5.4),('2016-11-30 07:00:00', 5.8),('2016-11-30 07:10:00', 5.2),
+   ('2016-11-30 07:20:00', 5.3),('2016-11-30 07:30:00', 5.3),('2016-11-30 07:40:00', 5.8),('2016-11-30 07:50:00', 5.9),
+   ('2016-11-30 08:00:00', 5.6),('2016-11-30 08:10:00', 5.2),('2016-11-30 08:20:00', 5.4),('2016-11-30 08:30:00', 5.6),
+   ('2016-11-30 08:40:00', 6.0),('2016-11-30 08:50:00', 5.4),('2016-11-30 09:00:00', 6.0),('2016-11-30 09:10:00', 5.1),
+   ('2016-11-30 09:20:00', 5.1),('2016-11-30 09:30:00', 5.5),('2016-11-30 09:40:00', 5.6),('2016-11-30 09:50:00', 5.0),
+   ('2016-11-30 10:00:00', 5.1),('2016-11-30 10:10:00', 5.7),('2016-11-30 10:20:00', 5.4),('2016-11-30 10:30:00', 5.4),
+   ('2016-11-30 10:40:00', 5.7),('2016-11-30 10:50:00', 5.2),('2016-11-30 11:00:00', 5.4),('2016-11-30 11:10:00', 5.3),
+   ('2016-11-30 11:20:00', 5.6),('2016-11-30 11:30:00', 5.0),('2016-11-30 11:40:00', 5.2),('2016-11-30 11:50:00', 5.2),
+   ('2016-11-30 12:00:00', 5.5),('2016-11-30 12:10:00', 5.1),('2016-11-30 12:20:00', 5.7),('2016-11-30 12:30:00', 5.4),
+   ('2016-11-30 12:40:00', 5.2),('2016-11-30 12:50:00', 5.5),('2016-11-30 13:00:00', 5.0),('2016-11-30 13:10:00', 5.5),
+   ('2016-11-30 13:20:00', 5.6),('2016-11-30 13:30:00', 5.3),('2016-11-30 13:40:00', 5.5),('2016-11-30 13:50:00', 5.9),
+   ('2016-11-30 14:00:00', 10.9),('2016-11-30 14:10:00', 10.6),('2016-11-30 14:20:00', 10.3),('2016-11-30 14:30:00', 11.0),
+   ('2016-11-30 14:40:00', 10.0),('2016-11-30 14:50:00', 10.1),('2016-11-30 15:00:00', 10.2),('2016-11-30 15:10:00', 10.2),
+   ('2016-11-30 15:20:00', 10.3),('2016-11-30 15:30:00', 10.1),('2016-11-30 15:40:00', 10.9),('2016-11-30 15:50:00', 10.1),
+   ('2016-11-30 16:00:00', 11.0),('2016-11-30 16:10:00', 10.2),('2016-11-30 16:20:00', 10.7),('2016-11-30 16:30:00', 10.2),
+   ('2016-11-30 16:40:00', 10.2),('2016-11-30 16:50:00', 10.2),('2016-11-30 17:00:00', 10.8),('2016-11-30 17:10:00', 10.6),
+   ('2016-11-30 17:20:00', 10.5),('2016-11-30 17:30:00', 10.7),('2016-11-30 17:40:00', 10.9),('2016-11-30 17:50:00', 10.9),
+   ('2016-11-30 18:00:00', 10.1),('2016-11-30 18:10:00', 10.3),('2016-11-30 18:20:00', 10.1),('2016-11-30 18:30:00', 10.6),
+   ('2016-11-30 18:40:00', 10.3),('2016-11-30 18:50:00', 10.8),('2016-11-30 19:00:00', 10.9),('2016-11-30 19:10:00', 10.8),
+   ('2016-11-30 19:20:00', 10.6),('2016-11-30 19:30:00', 11.0),('2016-11-30 19:40:00', 10.3),('2016-11-30 19:50:00', 10.9),
+   ('2016-11-30 20:00:00', 10.6),('2016-11-30 20:10:00', 10.6),('2016-11-30 20:20:00', 10.5),('2016-11-30 20:30:00', 10.4),
+   ('2016-11-30 20:40:00', 10.9),('2016-11-30 20:50:00', 10.9),('2016-11-30 21:00:00', 10.7),('2016-11-30 21:10:00', 10.6),
+   ('2016-11-30 21:20:00', 10.5),('2016-11-30 21:30:00', 10.8),('2016-11-30 21:40:00', 10.4),('2016-11-30 21:50:00', 10.0),
+   ('2016-11-30 22:00:00', 10.6),('2016-11-30 22:10:00', 10.6),('2016-11-30 22:20:00', 10.6),('2016-11-30 22:30:00', 10.1),
+   ('2016-11-30 22:40:00', 10.4),('2016-11-30 22:50:00', 10.8),('2016-11-30 23:00:00', 10.4),('2016-11-30 23:10:00', 10.6),
+   ('2016-11-30 23:20:00', 10.1),('2016-11-30 23:30:00', 10.2),('2016-11-30 23:40:00', 10.6),('2016-11-30 23:50:00', 10.8),
+   ('2016-12-01 00:00:00', 10.6),('2016-12-01 00:10:00', 10.2),('2016-12-01 00:20:00', 10.9),('2016-12-01 00:30:00', 10.3),
+   ('2016-12-01 00:40:00', 10.3),('2016-12-01 00:50:00', 10.1),('2016-12-01 01:00:00', 10.7),('2016-12-01 01:10:00', 10.5),
+   ('2016-12-01 01:20:00', 10.4),('2016-12-01 01:30:00', 10.7),('2016-12-01 01:40:00', 10.5),('2016-12-01 01:50:00', 10.7),
+   ('2016-12-01 02:00:00', 10.8),('2016-12-01 02:10:00', 10.9),('2016-12-01 02:20:00', 10.9),('2016-12-01 02:30:00', 10.1),
+   ('2016-12-01 02:40:00', 10.4),('2016-12-01 02:50:00', 10.7),('2016-12-01 03:00:00', 10.7),('2016-12-01 03:10:00', 10.5),
+   ('2016-12-01 03:20:00', 10.2),('2016-12-01 03:30:00', 10.2),('2016-12-01 03:40:00', 10.8),('2016-12-01 03:50:00', 10.2),
+   ('2016-12-01 04:00:00', 10.9),('2016-12-01 04:10:00', 10.4),('2016-12-01 04:20:00', 10.6),('2016-12-01 04:30:00', 11.0),
+   ('2016-12-01 04:40:00', 10.4),('2016-12-01 04:50:00', 10.3),('2016-12-01 05:00:00', 10.7),('2016-12-01 05:10:00', 10.6),
+   ('2016-12-01 05:20:00', 10.9),('2016-12-01 05:30:00', 11.0),('2016-12-01 05:40:00', 10.9),('2016-12-01 05:50:00', 10.0),
+   ('2016-12-01 06:00:00', 10.8),('2016-12-01 06:10:00', 10.0),('2016-12-01 06:20:00', 10.1),('2016-12-01 06:30:00', 10.5),
+   ('2016-12-01 06:40:00', 15.5),('2016-12-01 06:50:00', 15.7),('2016-12-01 07:00:00', 15.1),('2016-12-01 07:10:00', 15.6),
+   ('2016-12-01 07:20:00', 15.5),('2016-12-01 07:30:00', 15.4),('2016-12-01 07:40:00', 15.7),('2016-12-01 07:50:00', 15.6),
+   ('2016-12-01 08:00:00', 15.3),('2016-12-01 08:10:00', 15.6),('2016-12-01 08:20:00', 15.1),('2016-12-01 08:30:00', 15.6),
+   ('2016-12-01 08:40:00', 15.9),('2016-12-01 08:50:00', 16.0),('2016-12-01 09:00:00', 15.4),('2016-12-01 09:10:00', 15.0),
+   ('2016-12-01 09:20:00', 15.0),('2016-12-01 09:30:00', 15.4),('2016-12-01 09:40:00', 15.9),('2016-12-01 09:50:00', 15.6),
+   ('2016-12-01 10:00:00', 15.7),('2016-12-01 10:10:00', 15.4),('2016-12-01 10:20:00', 15.2),('2016-12-01 10:30:00', 15.2),
+   ('2016-12-01 10:40:00', 15.8),('2016-12-01 10:50:00', 15.4),('2016-12-01 11:00:00', 16.0),('2016-12-01 11:10:00', 15.9),
+   ('2016-12-01 11:20:00', 15.1),('2016-12-01 11:30:00', 15.0),('2016-12-01 11:40:00', 15.0),('2016-12-01 11:50:00', 15.4),
+   ('2016-12-01 12:00:00', 15.5),('2016-12-01 12:10:00', 15.3),('2016-12-01 12:20:00', 16.0),('2016-12-01 12:30:00', 15.1),
+   ('2016-12-01 12:40:00', 15.5),('2016-12-01 12:50:00', 16.0),('2016-12-01 13:00:00', 15.7),('2016-12-01 13:10:00', 15.9),
+   ('2016-12-01 13:20:00', 15.4),('2016-12-01 13:30:00', 15.3),('2016-12-01 13:40:00', 15.9),('2016-12-01 13:50:00', 15.8),
+   ('2016-12-01 14:00:00', 15.4),('2016-12-01 14:10:00', 15.9),('2016-12-01 14:20:00', 15.3),('2016-12-01 14:30:00', 16.0),
+   ('2016-12-01 14:40:00', 15.5),('2016-12-01 14:50:00', 15.0),('2016-12-01 15:00:00', 15.1),('2016-12-01 15:10:00', 16.0),
+   ('2016-12-01 15:20:00', 15.8),('2016-12-01 15:30:00', 15.9),('2016-12-01 15:40:00', 15.4),('2016-12-01 15:50:00', 15.1),
+   ('2016-12-01 16:00:00', 15.8),('2016-12-01 16:10:00', 15.2),('2016-12-01 16:20:00', 15.4),('2016-12-01 16:30:00', 15.8),
+   ('2016-12-01 16:40:00', 15.8),('2016-12-01 16:50:00', 15.1),('2016-12-01 17:00:00', 15.3),('2016-12-01 17:10:00', 15.6),
+   ('2016-12-01 17:20:00', 15.3),('2016-12-01 17:30:00', 15.8),('2016-12-01 17:40:00', 15.0),('2016-12-01 17:50:00', 15.3),
+   ('2016-12-01 18:00:00', 15.5),('2016-12-01 18:10:00', 15.4),('2016-12-01 18:20:00', 15.3),('2016-12-01 18:30:00', 15.8),
+   ('2016-12-01 18:40:00', 15.2),('2016-12-01 18:50:00', 15.9),('2016-12-01 19:00:00', 15.4),('2016-12-01 19:10:00', 15.3),
+   ('2016-12-01 19:20:00', 15.1),('2016-12-01 19:30:00', 15.3),('2016-12-01 19:40:00', 15.9),('2016-12-01 19:50:00', 15.3),
+   ('2016-12-01 20:00:00', 15.3),('2016-12-01 20:10:00', 15.2),('2016-12-01 20:20:00', 15.0),('2016-12-01 20:30:00', 15.3),
+   ('2016-12-01 20:40:00', 15.1),('2016-12-01 20:50:00', 15.1),('2016-12-01 21:00:00', 15.6),('2016-12-01 21:10:00', 15.8),
+   ('2016-12-01 21:20:00', 15.4),('2016-12-01 21:30:00', 15.2),('2016-12-01 21:40:00', 16.0),('2016-12-01 21:50:00', 15.5),
+   ('2016-12-01 22:00:00', 15.4),('2016-12-01 22:10:00', 15.7),('2016-12-01 22:20:00', 15.3),('2016-12-01 22:30:00', 15.9),
+   ('2016-12-01 22:40:00', 15.9),('2016-12-01 22:50:00', 15.2),('2016-12-01 23:00:00', 15.8),('2016-12-01 23:10:00', 15.9),
+   ('2016-12-01 23:20:00', 20.9),('2016-12-01 23:30:00', 20.4),('2016-12-01 23:40:00', 20.3),('2016-12-01 23:50:00', 20.1),
+   ('2016-12-02 00:00:00', 20.7),('2016-12-02 00:10:00', 20.7),('2016-12-02 00:20:00', 20.5),('2016-12-02 00:30:00', 20.4),
+   ('2016-12-02 00:40:00', 20.4),('2016-12-02 00:50:00', 20.1),('2016-12-02 01:00:00', 20.2),('2016-12-02 01:10:00', 20.9),
+   ('2016-12-02 01:20:00', 20.6),('2016-12-02 01:30:00', 20.0),('2016-12-02 01:40:00', 20.4),('2016-12-02 01:50:00', 20.2),
+   ('2016-12-02 02:00:00', 20.6),('2016-12-02 02:10:00', 20.4),('2016-12-02 02:20:00', 20.5),('2016-12-02 02:30:00', 20.4),
+   ('2016-12-02 02:40:00', 20.5),('2016-12-02 02:50:00', 20.7),('2016-12-02 03:00:00', 20.2),('2016-12-02 03:10:00', 20.2),
+   ('2016-12-02 03:20:00', 20.1),('2016-12-02 03:30:00', 20.5),('2016-12-02 03:40:00', 20.5),('2016-12-02 03:50:00', 20.0),
+   ('2016-12-02 04:00:00', 20.7),('2016-12-02 04:10:00', 20.8),('2016-12-02 04:20:00', 20.6),('2016-12-02 04:30:00', 20.4),
+   ('2016-12-02 04:40:00', 20.5),('2016-12-02 04:50:00', 20.8),('2016-12-02 05:00:00', 20.1),('2016-12-02 05:10:00', 20.9),
+   ('2016-12-02 05:20:00', 20.5),('2016-12-02 05:30:00', 20.4),('2016-12-02 05:40:00', 20.2),('2016-12-02 05:50:00', 20.4),
+   ('2016-12-02 06:00:00', 20.8),('2016-12-02 06:10:00', 20.7),('2016-12-02 06:20:00', 20.9),('2016-12-02 06:30:00', 20.1),
+   ('2016-12-02 06:40:00', 20.3),('2016-12-02 06:50:00', 20.2),('2016-12-02 07:00:00', 20.4),('2016-12-02 07:10:00', 20.7),
+   ('2016-12-02 07:20:00', 20.4),('2016-12-02 07:30:00', 20.8),('2016-12-02 07:40:00', 20.8),('2016-12-02 07:50:00', 20.1),
+   ('2016-12-02 08:00:00', 20.3),('2016-12-02 08:10:00', 20.7),('2016-12-02 08:20:00', 20.9),('2016-12-02 08:30:00', 21.0),
+   ('2016-12-02 08:40:00', 20.2),('2016-12-02 08:50:00', 20.5),('2016-12-02 09:00:00', 20.2),('2016-12-02 09:10:00', 20.8),
+   ('2016-12-02 09:20:00', 20.9),('2016-12-02 09:30:00', 20.5),('2016-12-02 09:40:00', 20.9),('2016-12-02 09:50:00', 20.7),
+   ('2016-12-02 10:00:00', 20.3),('2016-12-02 10:10:00', 21.0),('2016-12-02 10:20:00', 20.5),('2016-12-02 10:30:00', 20.3),
+   ('2016-12-02 10:40:00', 20.2),('2016-12-02 10:50:00', 20.3),('2016-12-02 11:00:00', 20.4),('2016-12-02 11:10:00', 20.4),
+   ('2016-12-02 11:20:00', 21.0),('2016-12-02 11:30:00', 20.3),('2016-12-02 11:40:00', 20.3),('2016-12-02 11:50:00', 20.9),
+   ('2016-12-02 12:00:00', 20.8),('2016-12-02 12:10:00', 20.9),('2016-12-02 12:20:00', 20.7),('2016-12-02 12:30:00', 20.7);
+   ```
+
+2. 执行训练操作：
+
+   ```sql
+   SET search_path="$user",public,madlib;
+   SET behavior_compat_options = 'bind_procedure_searchpath';
+   select madlib.prophet_fit('public.ts_data', 'public.prophet_model',
+   $${'ds': 'date', 'y': 'value'}$$, -- 列名映射， prophet要求时间列名必须为'ds'， 时序值列名'y'
+   $${'growth': 'linear', 'changepoints': ['2016-11-30 05:40:00']}$$ -- 训练参数组合，如果有多个参数，请用元组方式传入
+   );
+   ```
+
+   查询模型表：
+
+   ```sql
+    select id, y_type, params from public.prophet_model;
+
+   id |      y_type      |                            params
+   ----+------------------+---------------------------------------------------------------
+    1 | double precision | {'changepoints': ['2016-11-30 05:40:00'], 'growth': 'linear'}
+   ```
+
+   在模型表中，记录着训练时间，结果类型，所用参数等。
+
+3. 执行预测操作
+
+   ```sql
+   select madlib.prophet_predict('public.prophet_model','public.prophet_output', 10, '10T');
+   ```
+
+   查看预测结果：
+
+   ```sql
+   select ds, yhat, yhat_lower, yhat_upper from public.prophet_output;
+
+        ds     |     yhat      |  yhat_lower   |  yhat_upper
+   ------------+---------------+---------------+---------------
+    2016-12-02 | 20.6943848045 | 17.7671496048 | 23.4160694837
+    2016-12-02 | 20.7408355633 | 17.9264413164 | 23.6426403933
+    2016-12-02 | 20.7872863221 | 17.9298207895 | 23.4548814727
+    2016-12-02 |  20.833737081 |  18.234443228 | 23.5317342873
+    2016-12-02 | 20.8801878398 | 18.2471709649 | 23.8345735574
+    2016-12-02 | 20.9266385986 | 18.1780101465 |  23.696087927
+    2016-12-02 | 20.9730893575 | 18.4292088648 | 23.7209823631
+    2016-12-02 | 21.0195401163 | 18.2623494126 | 23.7341427068
+    2016-12-02 | 21.0659908751 | 18.1173966769 | 23.7919478206
+    2016-12-02 |  21.112441634 | 18.5018042056 | 23.9508963879
+   (10 rows)
+   ```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/7-deepsql/7-5-troubleshooting.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/7-deepsql/7-5-troubleshooting.md
new file mode 100644
index 0000000000000000000000000000000000000000..a5bd8017dd6a2dda86f555d34ea8e1c26f46eaad
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/7-deepsql/7-5-troubleshooting.md
@@ -0,0 +1,46 @@
+---
+title: 常见问题处理
+summary: 常见问题处理
+author: Guo Huan
+date: 2021-05-19
+---
+
+# 常见问题处理
+
+- **问题描述**：编译数据库时，提示python模块，“can not be used when making a shared object；recompile with -fPIC”或者 “libpython22.7.a: could not read symbols: Bad value”。
+
+  **处理方式**：
+
+  1. 请检查python版本和环境变量。
+  2. 查看是否安装python-devel，或者编译python时，是否启用了-enable-shared。<br/>
+
+- **问题描述**：执行gdb或者gstack命令，报错 “gdb: symbol lookup error: gdb: undefined symbol: PyUnicodeUCS4_FromEncodedObject”。
+
+  **处理方式**：这个问题一般发生在自行编译python2的环境上，Python2在编译安装时可以通过参数 -enable-unicode=ucs2 或 -enable-unicode=ucs4分别指定使用2个字节或者4个字节表示一个unicode字符，python2缺省使用-enable-unicode=ucs2。Python3默认使用4个字节表示一个unicode字符。
+
+  可以在系统中自带的python2下执行：“import sys; print sys.maxunicode”并查看结果，如果结果是65535，说明系统默认的是ucs2；如果结果是1114111，说明用的ucs4编码。
+
+  自行编译python2时，如果系统中内置的python2使用的ucs4，系统中的gdb也会依赖ucs4。因此自行编译的python2在configure时，需要添加-enable-unicode=ucs4。<br/>
+
+- **问题描述**：在kmeans等算法里，报错“Data table does not exist”。
+
+  **处理方式**：算法所在的schema和输入表不在一个schema下，可以设置SET behavior_compat_options = 'bind_procedure_searchpath';解决这个问题。<br/>
+
+- **问题描述**：python启动报错，或者import报错。
+
+  **处理方式：**
+
+  1. 检查环境变量比如PYTHONHOME，PYTHONPATH。
+  2. 安装必备依赖包。<br/>
+
+- **问题描述**：Regression等算法报错“ERROR: spiexceptions.UndefinedFunction: operator does not exist: json -&gt;&gt; unknown.”。
+
+  **处理方式**：数据库不支持json导出功能，不支持此功能。<br/>
+
+- **问题描述**：MADlib中进行编译时，如果使用make -sj，会遇到boost相关的报错。例如，“fatal error: boost/mpl/if.hpp: No such file or directory”。
+
+  **处理方式**：非问题，MADlib编译时，会先解压这几个安装包。如果是并行编译，会出现一边编译，一边解压的情况。如果编译用到这个文件，另一边还没有解压完成，会出现这类报错。再次执行make -sj即可解决。<br/>
+
+- **问题描述**：执行./madpack 安装时，遇到报错：“ERROR : Failed to connect to database”。
+
+  **处理方式**：需要排查数据库是否启动，目标库是否存在，数据库端口是否被占用，安装用户是否具有管理员权限。另外执行madpack安装时，IP请使用127.0.0.1，不要使用localhost，否则也会出现连接失败的情况。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/8-db4ai/8-1-overview.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/8-db4ai/8-1-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..e4eccd05571c42acec8e0eb1c145279f7ac2e1fc
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/8-db4ai/8-1-overview.md
@@ -0,0 +1,10 @@
+---
+title: 概述
+summary: 概述
+author: Guo Huan
+date: 2021-05-19
+---
+
+# 概述
+
+DB4AI是指利用数据库的能力驱动AI任务，实现数据存储、技术栈的同构。通过在数据库内集成AI算法，令MogDB具备数据库原生AI计算引擎、模型管理、AI算子、AI原生执行计划的能力，为用户提供普惠AI技术。不同于传统的AI建模流程，DB4AI“一站式”建模可以解决数据在各平台的反复流转问题，同时简化开发流程，并可通过数据库规划出最优执行路径，让开发者更专注于具体业务和模型的调优上，具备同类产品不具备的易用性与性能优势。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/8-db4ai/8-2-db4ai-snapshots-for-data-version-management.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/8-db4ai/8-2-db4ai-snapshots-for-data-version-management.md
new file mode 100644
index 0000000000000000000000000000000000000000..fc623932193f837ade1bd0af0ebdbdd324764a9e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/8-db4ai/8-2-db4ai-snapshots-for-data-version-management.md
@@ -0,0 +1,265 @@
+---
+title: DB4AI-Snapshots：数据版本管理
+summary: DB4AI-Snapshots数据版本管理
+author: Guo Huan
+date: 2021-10-20
+---
+
+# DB4AI-Snapshots：数据版本管理
+
+DB4AI-Snapshots是DB4AI模块用于管理数据集版本的功能。通过DB4AI-Snapshots组件，开发者可以简单、快速地进行特征筛选、类型转换等数据预处理操作，同时还可以像git一样对训练数据集进行版本控制。数据表快照创建成功后可以像视图一样进行使用，但是一经发布后，数据表快照便固化为不可变的静态数据，如需修改该数据表快照的内容，需要创建一个版本号不同的新数据表快照。
+
+## DB4AI-Snapshots的生命周期
+
+DB4AI-Snapshots的状态包括published、archived以及purged。其中，published可以用于标记该DB4AI-Snapshots已经发布，可以进行使用。archived表示当前DB4AI-Snapshots处于“存档期”，一般不进行新模型的训练，而是利用旧数据对新的模型进行验证。purged则是该DB4AI-Snapshots已经被删除的状态，在数据库系统中无法再检索到。
+
+需要注意的是快照管理功能是为了给用户提供统一的训练数据，不同团队成员可以使用给定的训练数据来重新训练机器学习模型，方便用户间协同。为此**私有用户**和**三权分立**状态（enableSeparationOfDuty=ON）等涉及不支持用户数据转写等情况将不支持Snapshot特性。
+
+用户可以通过“CREATE SNAPSHOT”语句创建数据表快照，创建好的快照默认即为published状态。可以采用两种模式创建数据表快照，即为MSS以及CSS模式，它们可以通过GUC参数db4ai_snapshot_mode进行配置。对于MSS模式，它是采用物化算法进行实现的，存储了原始数据集的数据实体；CSS则是基于相对计算算法实现的，存储的是数据的增量信息。数据表快照的元信息存储在DB4AI的系统目录中。可以通过db4ai.snapshot系统表查看到。
+
+可以通过“ARCHIVE SNAPSHOT”语句将某一个数据表快照标记为archived状态，可以通过“PUBLISH SNAPSHOT”语句将其再度标记为published状态。标记数据表快照的状态，是为了帮助数据科学家进行团队合作使用的。
+
+当一个数据表快照已经丧失存在价值时，可以通过“PURGE SNAPSHOT”语句删除它，以便永久删除其数据并恢复存储空间。
+
+## DB4AI-Snapshots使用指导
+
+1. 创建表以及插入表数据。
+
+   数据库内存在已有的数据表，可根据该已有的数据表创建对应的数据表快照。为了后续演示，在此处新建一个名为t1的数据表，并向其中插入测试数据。
+
+   ```sql
+   create table t1 (id int, name varchar);
+   insert into t1 values (1, 'zhangsan');
+   insert into t1 values (2, 'lisi');
+   insert into t1 values (3, 'wangwu');
+   insert into t1 values (4, 'lisa');
+   insert into t1 values (5, 'jack');
+   ```
+
+   通过SQL语句，查询搭配数据表内容。
+
+   ```sql
+   SELECT * FROM t1;
+   id |   name
+   ----+----------
+     1 | zhangsan
+     2 | lisi
+     3 | wangwu
+     4 | lisa
+     5 | jack
+   (5 rows)
+   ```
+
+2. 使用DB4AI-Snapshots。
+
+   - 创建DB4AI-Snapshots
+
+     - 示例1：CREATE SNAPSHOT…AS
+
+       示例如下，其中，默认版本分隔符为 “@”, 默认子版本分割符为 “.”，该分割符可以分别通过GUC参数db4ai_snapshot_version_delimiter以及db4ai_snapshot_version_separator进行设置。
+
+       ```sql
+       create snapshot s1@1.0 comment is 'first version' as select * from t1;
+       schema |  name
+       --------+--------
+        public | s1@1.0
+       (1 row)
+       ```
+
+       上述结果提示已经创建了数据表s1的快照，版本号为1.0。创建好后的数据表快照可以像使用一般视图一样进行查询，但不支持通过“INSERT INTO”语句进行更新。例如下面几种语句都可以查询到数据表快照s1的对应版本1.0的内容：
+
+       ```sql
+       SELECT * FROM s1@1.0;
+       SELECT * FROM public.s1@1.0;
+       SELECT * FROM public . s1 @ 1.0;
+       id |   name
+       ----+----------
+         1 | zhangsan
+         2 | lisi
+         3 | wangwu
+         4 | lisa
+         5 | jack
+       (5 rows)
+       ```
+
+       可以通过下列SQL语句修改数据表t1的内容：
+
+       ```sql
+       UPDATE t1 SET name = 'tom' where id = 4;
+       insert into t1 values (6, 'john');
+       insert into t1 values (7, 'tim');
+       ```
+
+       再检索数据表t1的内容时，发现虽然数据表t1的内容已经发生变化，但是数据表快照s1@1.0版本的查询结果并未发生变化。由于数据表t1的数据已经发生了改变，如果将当前数据表的内容作为版本2.0，则可创建快照**s1@2.0**,创建的SQL语句如下：
+
+       ```sql
+       create snapshot s1@2.0 as select * from t1;
+       ```
+
+       通过上述例子，我们可以发现，数据表快照可以固化数据表的内容，避免中途对数据的改动造成机器学习模型训练时的不稳定，同时可以避免多用户同时访问、修改同一个表时造成的锁冲突。
+
+     - 示例2：CREATE SNAPSHOT…FROM
+
+       SQL语句可以对一个已经创建好的数据表快照进行继承，利用在此基础上进行的数据修改产生一个新的数据表快照。例如：
+
+       ```sql
+       create snapshot s1@3.0 from @1.0 comment is 'inherits from @1.0' using (INSERT VALUES(6, 'john'), (7, 'tim'); DELETE WHERE id = 1);
+       schema |  name
+       --------+--------
+        public | s1@3.0
+       (1 row)
+       ```
+
+       其中，“@”为数据表快照的版本分隔符，from子句后加上已存在的数据表快照，用法为“@”+版本号，USING关键字后加入可选的几个操作关键字（INSERT …/UPDATE …/DELETE …/ALTER …），其中 “INSERT INTO”以及“DELETE FROM”语句中的“INTO”、“FROM”等与数据表快照名字相关联的子句可以省略，具体可以参考[AI特性函数](28-ai-feature-functions)。
+
+       示例中，基于前述s1@1.0快照，插入2条数据，删除1条新的数据，新生成的快照s1@3.0，检索该s1@3.0：
+
+       ```sql
+       SELECT * FROM s1@3.0;
+       id |   name
+       ----+----------
+         1 | zhangsan
+         2 | lisi
+         3 | wangwu
+         4 | lisa
+         5 | jack
+         6 | john
+         7 | tim
+       (7 rows)
+       ```
+
+   - 删除数据表快照SNAPSHOT
+
+     ```sql
+     purge snapshot s1@3.0;
+     schema |  name
+     --------+--------
+      public | s1@3.0
+     (1 row)
+     ```
+
+     此时，已经无法再从s1@3.0 中检索到数据了，同时该数据表快照在db4ai.snapshot视图中的记录也会被清除。删除该版本的数据表快照不会影响其他版本的数据表快照。
+
+   - 从数据表快照中采样
+
+     示例：从snapshot s1中抽取数据，使用0.5抽样率。
+
+     ```sql
+     sample snapshot s1@2.0 stratify by name as nick at ratio .5;
+     schema |    name
+     --------+------------
+      public | s1nick@2.0
+     (1 row)
+     ```
+
+     可以利用该功能创建训练集与测试集，例如：
+
+     ```sql
+     SAMPLE SNAPSHOT s1@2.0  STRATIFY BY name AS _test AT RATIO .2, AS _train AT RATIO .8 COMMENT IS 'training';
+     schema |      name
+     --------+----------------
+      public | s1_test@2.0
+      public | s1_train@2.0
+     (2 rows)
+     ```
+
+   - 发布数据表快照
+
+     采用下述SQL语句将数据表快照s1@2.0标记为published状态：
+
+     ```sql
+     publish snapshot s1@2.0;
+     schema |  name
+     --------+--------
+      public | s1@2.0
+     (1 row)
+     ```
+
+   - 存档数据表快照
+
+     采用下述语句可以将数据表快照标记为archived状态：
+
+     ```sql
+     archive snapshot s1@2.0;
+     schema |  name
+     --------+--------
+      public | s1@2.0
+     (1 row)
+     ```
+
+     可以通过db4ai-snapshots提供的视图查看当前数据表快照的状态以及其他信息：
+
+     ```sql
+     select * from db4ai.snapshot;
+     id | parent_id | matrix_id | root_id | schema |    name    | owner  |                 commands                 | comment | published | archived |          created           | row_count
+     ----+-----------+-----------+---------+--------+------------+--------+------------------------------------------+---------+-----------+----------+----------------------------+-----------
+       1 |           |           |       1 | public | s1@2.0     | omm | {"select *","from t1 where id > 3",NULL} |         | t         | f        | 2021-04-17 09:24:11.139868 |         2
+       2 |         1 |           |       1 | public | s1nick@2.0 | omm | {"SAMPLE nick .5 {name}"}                |         | f         | f        | 2021-04-17 10:02:31.73923  |         0
+     ```
+
+3. 异常场景
+
+   - 数据表或db4ai-snapshots不存在时。
+
+     ```sql
+     purge snapshot s1nick@2.0;
+     publish snapshot s1nick@2.0;
+     ---------
+     ERROR:  snapshot public."s1nick@2.0" does not exist
+     CONTEXT:  PL/pgSQL function db4ai.publish_snapshot(name,name) line 11 at assignment
+
+     archive snapshot s1nick@2.0;
+     ----------
+     ERROR:  snapshot public."s1nick@2.0" does not exist
+     CONTEXT:  PL/pgSQL function db4ai.archive_snapshot(name,name) line 11 at assignment
+     ```
+
+   - 删除snapshot时，有依赖该快照的其他snapshot，需先确保删除对本快照所依赖的其他快照。
+
+     ```sql
+     purge snapshot s1@1.0;
+     ERROR:  cannot purge root snapshot 'public."s1@1.0"' having dependent db4ai-snapshots
+     HINT:  purge all dependent db4ai-snapshots first
+     CONTEXT:  referenced column: purge_snapshot_internal
+     SQL statement "SELECT db4ai.purge_snapshot_internal(i_schema, i_name)"
+     PL/pgSQL function db4ai.purge_snapshot(name,name) line 62 at PERFORM
+     ```
+
+4. 相关GUC参数
+
+   - db4ai_snapshot_mode：
+
+     Snapshot有2种模式：MSS（物化模式，存储数据实体）和CSS（计算模式，存储增量信息）。Snapshot可在MSS和CSS之间切换快照模式，默认是MSS模式。
+
+   - db4ai_snapshot_version_delimiter：
+
+     该参数为数据表快照版本分隔符。“@”为数据表快照的默认版本分隔符。
+
+   - db4ai_snapshot_version_separator：
+
+     该参数为数据表快照子版本分隔符。“.”为数据表快照的默认版本分隔符。
+
+5. DB4AI Schema下的数据表快照详情db4ai.snapshot。
+
+   ```sql
+   mogdb=# \d db4ai.snapshot
+                          Table "db4ai.snapshot"
+     Column   |            Type             |         Modifiers
+   -----------+-----------------------------+---------------------------
+    id        | bigint                      |
+    parent_id | bigint                      |
+    matrix_id | bigint                      |
+    root_id   | bigint                      |
+    schema    | name                        | not null
+    name      | name                        | not null
+    owner     | name                        | not null
+    commands  | text[]                      | not null
+    comment   | text                        |
+    published | boolean                     | not null default false
+    archived  | boolean                     | not null default false
+    created   | timestamp without time zone | default pg_systimestamp()
+    row_count | bigint                      | not null
+   Indexes:
+       "snapshot_pkey" PRIMARY KEY, btree (schema, name) TABLESPACE pg_default
+       "snapshot_id_key" UNIQUE CONSTRAINT, btree (id) TABLESPACE pg_default
+   ```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/8-db4ai/8-3-db4ai-query-for-model-training-and-prediction.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/8-db4ai/8-3-db4ai-query-for-model-training-and-prediction.md
new file mode 100644
index 0000000000000000000000000000000000000000..38eab31f690ffa5b9aa1600e96d8bf0bba4176ec
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/8-db4ai/8-3-db4ai-query-for-model-training-and-prediction.md
@@ -0,0 +1,420 @@
+---
+title: DB4AI-Query：模型训练和推断
+summary: DB4AI-Query：模型训练和推断
+author: Guo Huan
+date: 2021-10-20
+---
+
+# DB4AI-Query：模型训练和推断
+
+MogDB当前版本支持了原生DB4AI能力，通过引入原生AI算子，简化操作流程，充分利用数据库优化器、执行器的优化与执行能力，获得高性能的数据库内模型训练能力。更简化的模型训练与预测流程、更高的性能表现，让开发者在更短时间内能更专注于模型的调优与数据分析上，而避免了碎片化的技术栈与冗余的代码实现。
+
+## 关键字解析
+
+**表 1** DB4AI语法及关键字
+
+<table>
+    <tr>
+        <th></th>
+        <th>名称</th>
+        <th>描述</th>
+    </tr>
+    <tr>
+        <td rowspan=2>语句</td>
+        <td>CREATE MODEL</td>
+        <td>创建模型并进行训练，同时保存模型。</td>
+    </tr>
+<tr>
+    <td>PREDICT BY</td>
+    <td>利用已有模型进行推断。</td>
+</tr>
+<tr>
+    <td rowspan=3>关键字</td>
+    <td>TARGET</td>
+    <td>训练/推断任务的目标列名。</td>
+</tr>
+<tr>
+    <td>FEATURES</td>
+    <td>训练/推断任务的数据特征列名。</td>
+</tr>
+<tr>
+    <td>MODEL</td>
+    <td>训练任务的模型名称。</td>
+</tr>
+    </table>
+
+## 使用指导
+
+1. 本版本支持的算法概述。
+
+   当前版本的DB4AI支持基于SGD算子的逻辑回归（目前支持二分类任务）、线性回归和支持向量机算法（分类任务），以及基于K-Means算子的Kmeans聚类算法。
+
+2. 模型训练语法说明。
+
+   - CREATE MODEL
+
+     使用“CREATE MODEL”语句可以进行模型的创建和训练。模型训练SQL语句，现有一个数据集为kmeans_2d，该表的数据内容如下：
+
+     ```sql
+     mogdb=# select * from kmeans_2d;
+      id |              position
+     ----+-------------------------------------
+       1 | {74.5268815685995,88.2141939294524}
+       2 | {70.9565760521218,98.8114827475511}
+       3 | {76.2756086327136,23.8387574302033}
+       4 | {17.8495847294107,81.8449544720352}
+       5 | {81.2175785354339,57.1677675866522}
+       6 | {53.97752255667,49.3158342130482}
+       7 | {93.2475341879763,86.934042100329}
+       8 | {72.7659293473698,19.7020415100269}
+       9 | {16.5800288529135,75.7475957670249}
+      10 | {81.8520747194998,40.3476078575477}
+      11 | {76.796671198681,86.3827232690528}
+      12 | {59.9231450678781,90.9907738864422}
+      13 | {70.161884885747,19.7427458665334}
+      14 | {11.1269539105706,70.9988166182302}
+      15 | {80.5005071521737,65.2822235273197}
+      16 | {54.7030725912191,52.151339428965}
+      17 | {103.059707058128,80.8419883321039}
+      18 | {85.3574452036992,14.9910179991275}
+      19 | {28.6501615960151,76.6922890325077}
+      20 | {69.7285806713626,49.5416352967732}
+     (20 rows)
+     ```
+
+     该表的字段position的数据类型为double precision[]。
+
+   - 以Kmeans为例，训练一个模型。从kmeans_2d训练集中指定position为特征列，使用kmeans算法，创建并保存模型point_kmeans。
+
+     ```sql
+     mogdb=# CREATE MODEL point_kmeans USING kmeans FEATURES position FROM kmeans_2d WITH num_centroids=3;
+     NOTICE:  Hyperparameter max_iterations takes value DEFAULT (10)
+     NOTICE:  Hyperparameter num_centroids takes value 3
+     NOTICE:  Hyperparameter tolerance takes value DEFAULT (0.000010)
+     NOTICE:  Hyperparameter batch_size takes value DEFAULT (10)
+     NOTICE:  Hyperparameter num_features takes value DEFAULT (2)
+     NOTICE:  Hyperparameter distance_function takes value DEFAULT (L2_Squared)
+     NOTICE:  Hyperparameter seeding_function takes value DEFAULT (Random++)
+     NOTICE:  Hyperparameter verbose takes value DEFAULT (0)
+     NOTICE:  Hyperparameter seed takes value DEFAULT (0)
+     MODEL CREATED. PROCESSED 1
+     ```
+
+     上述命令中：
+
+     - “CREATE MODEL”语句用于模型的训练和保存。
+
+     - USING关键字指定算法名称。
+
+     - FEATURES用于指定训练模模型的特征，需根据训练数据表的列名添加。
+
+     - TARGET指定模型的训练目标，它可以是训练所需数据表的列名，也可以是一个表达式，例如：price > 10000。
+
+     - WITH用于指定训练模型时的超参数。当超参未被用户进行设置的时候，框架会使用默认数值。
+
+       针对不同的算子，框架支持不同的超参组合：
+
+       **表 2** 算子支持的超参
+
+       | 算子                                                         | 超参                                                         |
+       | :----------------------------------------------------------- | :----------------------------------------------------------- |
+       | GD(logistic_regression、linear_regression、svm_classification) | optimizer(char\*); verbose(bool); max_iterations(int); max_seconds(double); batch_size(int); learning_rate(double); decay(double); tolerance(double) <br/>其中，SVM限定超参lambda(double) |
+       | Kmeans                                                       | max_iterations(int); num_centroids(int); tolerance(double); batch_size(int); num_features(int); distance_function(char); seeding_function(char*); verbose(int);seed(int) |
+
+       当前各个超参数设置的默认值和取值范围如下：
+
+       **表 3** 超参的默认值以及取值范围
+
+       <table>
+           <tr>
+               <th>算子</th>
+               <th>超参（默认值）</th>
+               <th>取值范围</th>
+               <th>超参描述</th>
+           </tr>
+           <tr>
+               <td rowspan=10>GD (logistic_regression、linear_regression、svm_classification)</td>
+               <td>optimizer = gd（梯度下降法）</td>
+               <td>gd/ngd（自然梯度下降）</td>
+               <td>优化器</td>
+           </tr>
+           <tr>
+               <td>verbose = false</td>
+               <td>T/F</td>
+               <td>日志显示</td>
+           </tr>
+           <tr>
+               <td>max_iterations = 100</td>
+               <td>(0, INT_MAX_VALUE]</td>
+               <td>最大迭代次数</td>
+           </tr>
+           <tr>
+               <td>max_seconds = 0（不对运行时长设限制）</td>
+               <td>[0,INT_MAX_VALUE]</td>
+               <td>运行时长</td>
+           </tr>
+           <tr>
+               <td>batch_size = 1000</td>
+               <td>(0, MAX_MEMORY_LIMIT]</td>
+               <td>一次训练所选取的样本数</td>
+           </tr>
+           <tr>
+               <td>learning_rate = 0.8</td>
+               <td>(0, DOUBLE_MAX_VALUE]</td>
+               <td>学习率</td>
+           </tr>
+           <tr>
+               <td>decay = 0.95</td>
+               <td>(0, DOUBLE_MAX_VALUE]</td>
+               <td>权值衰减率</td>
+           </tr>
+           <tr>
+               <td>tolerance = 0.0005</td>
+               <td>(0, DOUBLE_MAX_VALUE]</td>
+               <td>公差</td>
+           </tr>
+           <tr>
+               <td>seed = 0（对seed取随机值）</td>
+               <td>[0, INT_MAX_VALUE]</td>
+               <td>种子</td>
+           </tr>
+           <tr>
+               <td>just for SVM：lambda = 0.01</td>
+               <td>(0, DOUBLE_MAX_VALUE)</td>
+               <td>正则化参数</td>
+           </tr>
+           <tr>
+               <td rowspan=9>Kmeans</td>
+               <td>max_iterations = 10</td>
+               <td>[1, INT_MAX_VALUE]</td>
+               <td>最大迭代次数</td>
+           </tr>
+           <tr>
+               <td>num_centroids = 10</td>
+               <td>[1, MAX_MEMORY_LIMIT]</td>
+               <td>簇的数目</td>
+           </tr>
+           <tr>
+               <td>tolerance = 0.00001</td>
+               <td>(0,1)</td>
+               <td>中心点误差</td>
+           </tr>
+           <tr>
+               <td>batch_size = 10</td>
+               <td>[1, MAX_MEMORY_LIMIT]</td>
+               <td>一次训练所选取的样本数</td>
+           </tr>
+           <tr>
+               <td>num_features = 2</td>
+               <td>[1, GS_MAX_COLS]</td>
+               <td>输入样本特征数</td>
+           </tr>
+           <tr>
+               <td>distance_function = "L2_Squared"</td>
+               <td>L1, L2, L2_Squared, or Linf</td>
+               <td>正则化方法</td>
+           </tr>
+           <tr>
+               <td>seeding_function = "Random++"</td>
+               <td>"Random++" or "KMeans||"</td>
+               <td>初始化种子点方法</td>
+           </tr>
+           <tr>
+               <td>verbose = 0U</td>
+               <td>{ 0, 1, 2 }</td>
+               <td>冗长模式</td>
+           </tr>
+           <tr>
+               <td>seed = 0U</td>
+               <td>[0, INT_MAX_VALUE]</td>
+               <td>种子</td>
+           </tr>
+           <tr>
+               <td colspan=4>MAX_MEMORY_LIMIT = 最大内存加载的元组数量</td>
+           </tr>
+           <tr>
+               <td colspan=4>GS_MAX_COLS = 数据库单表最大属性数量</td>
+           </tr>
+       </table>
+
+   - 模型保存成功，则返回创建成功信息：
+
+     ```sql
+     MODEL CREATED. PROCESSED x
+     ```
+
+3. 查看模型信息。
+
+   当训练完成后模型会被存储到系统表gs_model_warehouse中。系统表gs_model_warehouse可以查看到关于模型本身和训练过程的相关信息。
+
+   用户可以通过查看系统表的方式查看模型，例如查看模型名为”point_kmeans”的SQL语句如下：
+
+   ```sql
+   mogdb=# select * from gs_model_warehouse where modelname='point_kmeans';
+   -[ RECORD 1 ]---------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+   modelname             | point_kmeans
+   modelowner            | 10
+   createtime            | 2021-04-30 17:30:39.59044
+   processedtuples       | 20
+   discardedtuples       | 0
+   pre_process_time      | 6.2001e-05
+   exec_time             | .000185272
+   iterations            | 5
+   outputtype            | 23
+   modeltype             | kmeans
+   query                 | CREATE MODEL point_kmeans USING kmeans FEATURES position FROM kmeans_2d WITH num_centroids=3;
+   modeldata             |
+   weight                |
+   hyperparametersnames  | {max_iterations,num_centroids,tolerance,batch_size,num_features,distance_function,seeding_function,verbose,seed}
+   hyperparametersvalues | {10,3,1e-05,10,2,L2_Squared,Random++,0,0}
+   hyperparametersoids   | {23,23,701,23,23,1043,1043,23,23}
+   coefnames             | {original_num_centroids,actual_num_centroids,dimension,distance_function_id,seed,coordinates}
+   coefvalues            | {3,3,2,2,572368998,"(77.282589,23.724434)(74.421616,73.239455)(18.551682,76.320914)"}
+   coefoids              |
+   trainingscoresname    |
+   trainingscoresvalue   |
+   modeldescribe         | {"id:1,objective_function:542.851169,avg_distance_to_centroid:108.570234,min_distance_to_centroid:1.027078,max_distance_to_centroid:297.210108,std_dev_distance_to_centroid:105.053257,cluster_size:5","id:2,objective_function:5825.982139,avg_distance_to_centroid:529.634740,min_distance_to_centroid:100.270449,max_distance_to_centroid:990.300588,std_dev_distance_to_centroid:285.915094,cluster_size:11","id:3,objective_function:220.792591,avg_distance_to_centroid:55.198148,min_distance_to_centroid:4.216111,max_distance_to_centroid:102.117204,std_dev_distance_to_centroid:39.319118,cluster_size:4"}
+   ```
+
+4. 利用已存在的模型做推断任务。
+
+   使用“SELECT”和“PREDICT BY”关键字利用已有模型完成推断任务。
+
+   查询语法：SELECT…PREDICT BY…(FEATURES…)…FROM…;
+
+   ```sql
+   mogdb=# SELECT id, PREDICT BY point_kmeans (FEATURES position) as pos FROM (select * from kmeans_2d limit 10);
+    id | pos
+   ----+-----
+     1 |   2
+     2 |   2
+     3 |   1
+     4 |   3
+     5 |   2
+     6 |   2
+     7 |   2
+     8 |   1
+     9 |   3
+    10 |   1
+   (10 rows)
+   ```
+
+   针对相同的推断任务，同一个模型的结果是稳定的。且基于相同的超参数和训练集训练的模型也具有稳定性，同时AI模型训练存在随机成分（每个batch的数据分布、随机梯度下降），所以不同的模型间的计算表现、结果允许存在小的差别。
+
+5. 查看执行计划。
+
+   使用explain语句可对“CREATE MODEL”和“PREDICT BY”的模型训练或预测过程中的执行计划进行分析。Explain关键字后可直接拼接CREATE MODEL/ PREDICT BY语句（子句），也可接可选的参数，支持的参数如下：
+
+   **表 4** EXPLAIN支持的参数
+
+   | 参数名    | 描述                                           |
+   | :-------- | :--------------------------------------------- |
+   | ANALYZE   | 布尔型变量，追加运行时间、循环次数等描述信息   |
+   | VERBOSE   | 布尔型变量，控制训练的运行信息是否输出到客户端 |
+   | COSTS     | 布尔型变量                                     |
+   | CPU       | 布尔型变量                                     |
+   | DETAIL    | 布尔型变量，不可用。                           |
+   | NODES     | 布尔型变量，不可用                             |
+   | NUM_NODES | 布尔型变量，不可用                             |
+   | BUFFERS   | 布尔型变量                                     |
+   | TIMING    | 布尔型变量                                     |
+   | PLAN      | 布尔型变量                                     |
+   | FORMAT    | 可选格式类型：TEXT / XML / JSON / YAML         |
+
+   示例：
+
+   ```sql
+   mogdb=# Explain CREATE MODEL patient_logisitic_regression USING logistic_regression FEATURES second_attack, treatment TARGET trait_anxiety > 50 FROM patients WITH batch_size=10, learning_rate = 0.05;
+   NOTICE:  Hyperparameter batch_size takes value 10
+   NOTICE:  Hyperparameter decay takes value DEFAULT (0.950000)
+   NOTICE:  Hyperparameter learning_rate takes value 0.050000
+   NOTICE:  Hyperparameter max_iterations takes value DEFAULT (100)
+   NOTICE:  Hyperparameter max_seconds takes value DEFAULT (0)
+   NOTICE:  Hyperparameter optimizer takes value DEFAULT (gd)
+   NOTICE:  Hyperparameter tolerance takes value DEFAULT (0.000500)
+   NOTICE:  Hyperparameter seed takes value DEFAULT (0)
+   NOTICE:  Hyperparameter verbose takes value DEFAULT (FALSE)
+   NOTICE:  GD shuffle cache size 212369
+                               QUERY PLAN
+   -------------------------------------------------------------------
+    Gradient Descent  (cost=0.00..0.00 rows=0 width=0)
+      ->  Seq Scan on patients  (cost=0.00..32.20 rows=1776 width=12)
+   (2 rows)
+   ```
+
+6. 异常场景。
+
+   - 训练阶段。
+
+     - 场景一：当超参数的设置超出取值范围，模型训练失败，返回ERROR，并提示错误，例如：
+
+       ```sql
+       mogdb=# CREATE MODEL patient_linear_regression USING linear_regression FEATURES second_attack,treatment TARGET trait_anxiety  FROM patients WITH optimizer='aa';
+       NOTICE:  Hyperparameter batch_size takes value DEFAULT (1000)
+       NOTICE:  Hyperparameter decay takes value DEFAULT (0.950000)
+       NOTICE:  Hyperparameter learning_rate takes value DEFAULT (0.800000)
+       NOTICE:  Hyperparameter max_iterations takes value DEFAULT (100)
+       NOTICE:  Hyperparameter max_seconds takes value DEFAULT (0)
+       NOTICE:  Hyperparameter optimizer takes value aa
+       ERROR:  Invalid hyperparameter value for optimizer. Valid values are: gd, ngd. (default is gd)
+       ```
+
+     - 场景二：当模型名称已存在，模型保存失败，返回ERROR，并提示错误原因：
+
+       ```sql
+       mogdb=# CREATE MODEL patient_linear_regression USING linear_regression FEATURES second_attack,treatment TARGET trait_anxiety  FROM patients;
+       NOTICE:  Hyperparameter batch_size takes value DEFAULT (1000)
+       NOTICE:  Hyperparameter decay takes value DEFAULT (0.950000)
+       NOTICE:  Hyperparameter learning_rate takes value DEFAULT (0.800000)
+       NOTICE:  Hyperparameter max_iterations takes value DEFAULT (100)
+       NOTICE:  Hyperparameter max_seconds takes value DEFAULT (0)
+       NOTICE:  Hyperparameter optimizer takes value DEFAULT (gd)
+       NOTICE:  Hyperparameter tolerance takes value DEFAULT (0.000500)
+       NOTICE:  Hyperparameter seed takes value DEFAULT (0)
+       NOTICE:  Hyperparameter verbose takes value DEFAULT (FALSE)
+       NOTICE:  GD shuffle cache size 5502
+       ERROR:  The model name "patient_linear_regression" already exists in gs_model_warehouse.
+       ```
+
+     - 场景三：FEATURE或者TARGETS列是*，返回ERROR，并提示错误原因：
+
+       ```sql
+       mogdb=# CREATE MODEL patient_linear_regression USING linear_regression FEATURES *  TARGET trait_anxiety  FROM
+       patients;
+       ERROR:  FEATURES clause cannot be *
+       -----------------------------------------------------------------------------------------------------------------------、
+       mogdb=# CREATE MODEL patient_linear_regression USING linear_regression FEATURES second_attack,treatment TARGET *  FROM patients;
+       ERROR:  TARGET clause cannot be *
+       ```
+
+     - 场景四：对于无监督学习方法使用TARGET关键字，或者在监督学习方法中不适用TARGET关键字，均会返回ERROR，并提示错误原因：
+
+       ```sql
+       mogdb=# CREATE MODEL patient_linear_regression USING linear_regression FEATURES second_attack,treatment FROM patients;
+       ERROR:  Supervised ML algorithms require TARGET clause
+       -----------------------------------------------------------------------------------------------------------------------------
+       CREATE MODEL patient_linear_regression USING linear_regression TARGET trait_anxiety  FROM patients;   ERROR:  Supervised ML algorithms require FEATURES clause
+       ```
+
+     - 场景五：当GUC参数statement_timeout设置了时长，训练超时执行的语句将被终止：执行CREATE MODEL语句。训练集的大小、训练轮数(iteration)、提前终止条件(tolerance、max_seconds)、并行线程数(nthread)等参数都会影响训练时长。当时长超过数据库限制，语句被终止模型训练失败。
+
+   - 推断阶段。
+
+     - 场景六：当模型名在系统表中查找不到，数据库会报ERROR：
+
+       ```sql
+       mogdb=# select id, PREDICT BY patient_logistic_regression (FEATURES second_attack,treatment) FROM patients;
+       ERROR:  There is no model called "patient_logistic_regression".
+       ```
+
+     - 场景七：当做推断任务FEATURES的数据维度和数据类型与训练集存在不一致，将报ERROR，并提示错误原因，例如：
+
+       ```sql
+       mogdb=# select id, PREDICT BY patient_linear_regression (FEATURES second_attack) FROM patients;
+       ERROR:  Invalid number of features for prediction, provided 1, expected 2
+       CONTEXT:  referenced column: patient_linear_regression_pred
+       -------------------------------------------------------------------------------------------------------------------------------------
+       mogdb=# select id, PREDICT BY patient_linear_regression (FEATURES 1,second_attack,treatment) FROM patients;
+       ERROR:  Invalid number of features for prediction, provided 3, expected 2
+       CONTEXT:  referenced column: patient_linear_regression_pre
+       ```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/8-db4ai/8-4-pl-python-fenced-mode.md b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/8-db4ai/8-4-pl-python-fenced-mode.md
new file mode 100644
index 0000000000000000000000000000000000000000..58cfa3d18747c0b3c3ebf5a82d0dfbb093bbc9c1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/AI-features/8-db4ai/8-4-pl-python-fenced-mode.md
@@ -0,0 +1,135 @@
+---
+title: plpython-fenced模式
+summary: plpython-fenced模式
+author: Guo Huan
+date: 2021-10-20
+---
+
+# plpython-fenced模式
+
+在fenced模式中添加plpython非安全语言。在数据库编译时需要将python集成进数据库中，在configure截断加入-with-python选项。同时也可指定安装plpython的python路径，添加选项-with-includes='/python-dir=path'。
+
+在启动数据库之前配置GUC参数unix_socket_directory，指定unix_socket进程间通讯的文件地址。用户需要提前在user-set-dir-path路径下创建文件夹，并将该文件夹权限修改为可读可写可执行。
+
+```bash
+unix_socket_directory = '/user-set-dir-path'
+```
+
+配置完成，启动数据库。
+
+将plpython加入数据库编译，并设置好GUC参数unix_socket_directory后，在启动数据库的过程中，自动创建fenced-Master进程。在数据库不进行python编译的情况下，fenced模式需要手动拉起master进程，在GUC参数设置完成后，输入创建master进程命令。
+
+启动fenced-Master进程，命令为：
+
+```bash
+gaussdb --fenced -k /user-set-dir-path -D /user-set-dir-path &
+```
+
+完成fence模式配置，针对plpython-fenced UDF数据库将在fenced-worker进程中执行UDF计算。
+
+## 使用指导
+
+- 创建extension
+
+  - 当编译的plpython为Python2时：
+
+    ```sql
+    mogdb=# create extension plpythonu;
+    CREATE EXTENSION
+    ```
+
+  - 当编译的plpython为Python3时：
+
+    ```sql
+    mogdb=# create extension plpython3u;
+    CREATE EXTENSION
+    ```
+
+  下面示例是以Python2为例。
+
+- 创建plpython-fenced UDF
+
+  ```sql
+  mogdb=# create or replace function pymax(a int, b int)
+  mogdb-# returns INT
+  mogdb-# language plpythonu fenced
+  mogdb-# as $$
+  mogdb$# import numpy
+  mogdb$# if a > b:
+  mogdb$#     return a;
+  mogdb$# else:
+  mogdb$#     return b;
+  mogdb$# $$;
+  CREATE FUNCTION
+  ```
+
+- 查看UDF信息
+
+  ```sql
+  mogdb=# select * from pg_proc where proname='pymax';
+  -[ RECORD 1 ]----+--------------
+  proname          | pymax
+  pronamespace     | 2200
+  proowner         | 10
+  prolang          | 16388
+  procost          | 100
+  prorows          | 0
+  provariadic      | 0
+  protransform     | -
+  proisagg         | f
+  proiswindow      | f
+  prosecdef        | f
+  proleakproof     | f
+  proisstrict      | f
+  proretset        | f
+  provolatile      | v
+  pronargs         | 2
+  pronargdefaults  | 0
+  prorettype       | 23
+  proargtypes      | 23 23
+  proallargtypes   |
+  proargmodes      |
+  proargnames      | {a,b}
+  proargdefaults   |
+  prosrc           |
+                   | import numpy
+                   | if a > b:
+                   |     return a;
+                   | else:
+                   |     return b;
+                   |
+  probin           |
+  proconfig        |
+  proacl           |
+  prodefaultargpos |
+  fencedmode       | t
+  proshippable     | f
+  propackage       | f
+  prokind          | f
+  proargsrc        |
+  ```
+
+- 运行UDF
+
+  - 创建一个数据表：
+
+    ```sql
+    mogdb=# create table temp (a int ,b int) ;
+    CREATE TABLE
+    mogdb=# insert into temp values (1,2),(2,3),(3,4),(4,5),(5,6);
+    INSERT 0 5
+    ```
+
+  - 运行UDF：
+
+    ```sql
+    mogdb=# select pymax(a,b) from temp;
+    pymax
+    -------
+        2
+        3
+        4
+        5
+        6
+    (5 rows)
+    ```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/autonomous-transaction/1-introduction-to-autonomous-transaction.md b/product/zh/docs-mogdb/v3.0/developer-guide/autonomous-transaction/1-introduction-to-autonomous-transaction.md
new file mode 100644
index 0000000000000000000000000000000000000000..7c4574e8ffca51be2513b44e856d23e0c9256b86
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/autonomous-transaction/1-introduction-to-autonomous-transaction.md
@@ -0,0 +1,12 @@
+---
+title: 介绍
+summary: 介绍
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# 介绍
+
+自治事务（Autonomous Transaction），在主事务执行过程中新启的独立的事务。自治事务的提交和回滚不会影响主事务已提交的数据，同时自治事务也不受主事务影响。
+
+自治事务在存储过程、函数和匿名块中定义，用PRAGMA AUTONOMOUS_TRANSACTION关键字来声明。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/autonomous-transaction/2-function-supporting-autonomous-transaction.md b/product/zh/docs-mogdb/v3.0/developer-guide/autonomous-transaction/2-function-supporting-autonomous-transaction.md
new file mode 100644
index 0000000000000000000000000000000000000000..862fc7a3742c91e26172a63a3c2d4c2640b8fe6d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/autonomous-transaction/2-function-supporting-autonomous-transaction.md
@@ -0,0 +1,75 @@
+---
+title: 函数支持自治事务
+summary: 函数支持自治事务
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# 函数支持自治事务
+
+自治事务可以在函数中定义，标识符为PRAGMA AUTONOMOUS_TRANSACTION，执行的函数块中使用包含start transaction和commit/rollback的sql，其余语法与CREATE FUNCTION创建函数语法类似，一个简单的用例如下：
+
+```sql
+--创建表。
+CREATE TABLE test1 (a int, b text);
+--创建包含自治事务的函数。
+CREATE OR REPLACE FUNCTION autonomous_easy_2(i int) RETURNS integer
+LANGUAGE plpgsql
+AS $$
+DECLARE
+    PRAGMA AUTONOMOUS_TRANSACTION;
+BEGIN
+    START TRANSACTION;
+    INSERT INTO test1 VALUES (2, 'a');
+    IF i % 2 = 0 THEN
+        COMMIT;
+    ELSE
+        ROLLBACK;
+    END IF;
+  RETURN i % 2 = 0;
+END;
+$$;
+--执行命令。
+select autonomous_easy_2(1);
+--执行结果。
+ autonomous_easy_2
+-------------------
+                 0
+(1 row)
+--执行命令，查询表数据。
+select * from test1;
+--执行结果。
+ a | b
+---+---
+(0 rows)
+--执行命令。
+select autonomous_easy_2(2);
+--执行结果。
+ autonomous_easy_2
+-------------------
+                 1
+(1 row)
+--执行命令，查询表数据。
+select * from test1;
+--执行结果
+ a | b
+---+---
+ 2 | a
+(1 row)
+--清空表数据。
+truncate table test1;
+--在回滚的事务块中执行包含自治事务的函数。
+begin;
+insert into test1 values(1,'b');
+select autonomous_easy_2(2);
+rollback;
+--检查表数据。
+select * from test1;
+--执行结果如下。
+ a | b
+---+---
+ 2 | a
+(1 row)
+```
+
+上述例子，最后在回滚的事务块中执行包含自治事务的函数，直接说明了自治事务的特性，即主事务的回滚，不会影响自治事务已经提交的内容。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/autonomous-transaction/3-stored-procedure-supporting-autonomous-transaction.md b/product/zh/docs-mogdb/v3.0/developer-guide/autonomous-transaction/3-stored-procedure-supporting-autonomous-transaction.md
new file mode 100644
index 0000000000000000000000000000000000000000..82c0878c721f0bf1dc6a0de58517cf413899986a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/autonomous-transaction/3-stored-procedure-supporting-autonomous-transaction.md
@@ -0,0 +1,45 @@
+---
+title: 存储过程支持自治事务
+summary: 存储过程支持自治事务
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# 存储过程支持自治事务
+
+自治事务可以在存储过程中定义，标识符为PRAGMA AUTONOMOUS_TRANSACTION，其余语法与创建存储过程语法相同，示例如下。
+
+```sql
+--建表
+create table t2(a int, b int);
+insert into t2 values(1,2);
+select * from t2;
+
+--创建包含自治事务的存储过程
+CREATE OR REPLACE PROCEDURE autonomous_4(a int, b int)  AS
+DECLARE
+    num3 int := a;
+    num4 int := b;
+    PRAGMA AUTONOMOUS_TRANSACTION;
+BEGIN
+    insert into t2 values(num3, num4);
+    dbe_output.print_line('just use call.');
+END;
+/
+--创建调用自治事务存储过程的普通存储过程
+CREATE OR REPLACE PROCEDURE autonomous_5(a int, b int)  AS
+DECLARE
+BEGIN
+    dbe_output.print_line('just no use call.');
+    insert into t2 values(666, 666);
+    autonomous_4(a,b);
+    rollback;
+END;
+/
+--调用普通存储过程
+select autonomous_5(11,22);
+--查看表结果
+select * from t2 order by a;
+```
+
+上述例子，最后在回滚的事务块中执行包含自治事务的存储过程，直接说明了自治事务的特性，即主事务的回滚，不会影响自治事务已经提交的内容。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/autonomous-transaction/4-restrictions.md b/product/zh/docs-mogdb/v3.0/developer-guide/autonomous-transaction/4-restrictions.md
new file mode 100644
index 0000000000000000000000000000000000000000..a9412bc96fd83e9eab98f6a9bde196cdad48509b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/autonomous-transaction/4-restrictions.md
@@ -0,0 +1,131 @@
+---
+title: 规格约束
+summary: 规格约束
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# 规格约束
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **注意：** 自治事务执行时，将会在后台启动自治事务session，我们可以通过max_concurrent_autonomous_transactions设置自治事务执行的最大并行数量，该参数取值范围为0~1024，默认值为10。当max_concurrent_autonomous_transactions参数设置为0时，自治事务将无法执行。
+
+- 触发器函数不支持自治事务。
+
+  ```sql
+  CREATE TABLE test_trigger_des_tbl(id1 INT, id2 INT, id3 INT);
+
+  CREATE OR REPLACE FUNCTION tri_insert_func() RETURNS TRIGGER AS
+  $$
+  DECLARE
+      PRAGMA AUTONOMOUS_TRANSACTION;
+  BEGIN
+  INSERT INTO test_trigger_des_tbl VALUES(NEW.id1, NEW.id2, NEW.id3);
+  RETURN NEW;
+  END
+  $$ LANGUAGE PLPGSQL;
+  ```
+
+- 自治事务不支持非顶层匿名块调用（仅支持顶层自治事务,包括存储过程、函数、匿名块）。
+
+  ```sql
+  create table t1(a int ,b text);
+
+  DECLARE
+      --PRAGMA AUTONOMOUS_TRANSACTION;
+  BEGIN
+      DECLARE
+          PRAGMA AUTONOMOUS_TRANSACTION;
+      BEGIN
+          dbe_output.print_line('just use call.');
+          insert into t1 values(1,'can you rollback!');
+      END;
+      insert into t1 values(2,'I will rollback!');
+      rollback;
+  END;
+  /
+
+  select * from t1;
+
+  ```
+
+- 自治事务不支持ref_cursor参数传递。
+
+  ```sql
+  create table sections(section_ID int);
+  insert into sections values(1);
+  insert into sections values(1);
+  insert into sections values(1);
+  insert into sections values(1);
+
+  CREATE OR REPLACE function proc_sys_ref()
+  return SYS_REFCURSOR
+  IS
+  declare
+          PRAGMA AUTONOMOUS_TRANSACTION;
+          C1 SYS_REFCURSOR;
+  BEGIN
+      OPEN C1 FOR SELECT section_ID FROM sections ORDER BY section_ID;
+      return C1;
+  END;
+  /
+
+  CREATE OR REPLACE PROCEDURE proc_sys_call() AS
+  DECLARE
+       C1 SYS_REFCURSOR;
+       TEMP NUMBER(4);
+  BEGIN
+       c1 = proc_sys_ref();
+       if c1%isopen then
+               raise notice '%','ok';
+      end if;
+
+       LOOP
+               FETCH C1 INTO TEMP;
+               raise notice '%',C1%ROWCOUNT;
+               EXIT WHEN C1%NOTFOUND;
+       END LOOP;
+  END;
+  /
+
+  select proc_sys_call();
+
+  CREATE OR REPLACE function proc_sys_ref(OUT C2 SYS_REFCURSOR, OUT a int)
+  return SYS_REFCURSOR
+  IS
+  declare
+          PRAGMA AUTONOMOUS_TRANSACTION;
+          C1 SYS_REFCURSOR;
+  BEGIN
+      OPEN C1 FOR SELECT section_ID FROM sections ORDER BY section_ID;
+      return C1;
+  END;
+  /
+
+  CREATE OR REPLACE PROCEDURE proc_sys_call() AS
+  DECLARE
+       C1 SYS_REFCURSOR;
+       TEMP NUMBER(4);
+       a int;
+  BEGIN
+       OPEN C1 FOR SELECT section_ID FROM sections ORDER BY section_ID;
+       c1 = proc_sys_ref(C1,a);
+       if c1%isopen then
+               raise notice '%','ok';
+      end if;
+
+       LOOP
+               FETCH C1 INTO TEMP;
+               raise notice '%',C1%ROWCOUNT;
+               EXIT WHEN C1%NOTFOUND;
+       END LOOP;
+  END;
+  /
+
+  select proc_sys_call();
+  ```
+
+- 自治事务函数不支持返回非out形式的record类型。
+
+- 不支持修改自治事务的隔离级别。
+
+- 不支持自治事务返回集合类型（setof）。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/autonomous-transaction/anonymous-block-supporting-autonomous-transaction.md b/product/zh/docs-mogdb/v3.0/developer-guide/autonomous-transaction/anonymous-block-supporting-autonomous-transaction.md
new file mode 100644
index 0000000000000000000000000000000000000000..fe19bd7820684e67d9b64f91b1c590e7fefd1917
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/autonomous-transaction/anonymous-block-supporting-autonomous-transaction.md
@@ -0,0 +1,29 @@
+---
+title: 匿名块支持自治事务
+summary: 匿名块支持自治事务
+author: Guo Huan
+date: 2021-10-15
+---
+
+# 匿名块支持自治事务
+
+自治事务可以在匿名块中定义，标识符为PRAGMA AUTONOMOUS_TRANSACTION，其余语法与创建匿名块语法相同，示例如下。
+
+```sql
+create table t1(a int ,b text);
+
+START TRANSACTION;
+DECLARE
+    PRAGMA AUTONOMOUS_TRANSACTION;
+BEGIN
+    dbe_output.print_line('just use call.');
+    insert into t1 values(1,'you are so cute,will commit!');
+END;
+/
+insert into t1 values(1,'you will rollback!');
+rollback;
+
+select * from t1;
+```
+
+上述例子，最后在回滚的事务块前执行包含自治事务的匿名块，也能直接说明了自治事务的特性，即主事务的回滚，不会影响自治事务已经提交的内容。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/1-development-specifications.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/1-development-specifications.md
new file mode 100644
index 0000000000000000000000000000000000000000..ac9277d286667c4d2ca8d57f5a36049ac87fd772
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/1-development-specifications.md
@@ -0,0 +1,779 @@
+---
+title: 开发规范
+summary: 开发规范
+author: Guo Huan
+date: 2021-04-27
+---
+
+# 开发规范
+
+如果用户在APP的开发中，使用了连接池机制，那么需要遵循如下规范:
+
+- 如果在连接中设置了GUC参数，那么在将连接归还连接池之前，必须使用"SET SESSION AUTHORIZATION DEFAULT;RESET ALL;"将连接的状态清空。
+- 如果使用了临时表，那么在将连接归还连接池之前，必须将临时表删除。
+
+否则，连接池里面的连接就是有状态的，会对用户后续使用连接池进行操作的正确性带来影响。
+
+## 概述
+
+### 简介
+
+尽管ISO针对SQL已经发布SQL-92、SQL:1999、SQL:2006等标准，但由于不同数据库自身的特性，使得同样功能在各自产品的实现上不尽相同，这也使得相关的语法规则各有千秋。因此，在制定具体开发规范的时候，需要针对不同数据库来编写相应的规范。
+
+本规范强调实用性、可操作性，根据开发人员在编码过程中常见的问题和易犯的错误,对代码编写的各方面均进行了详细明确的规范和约束。主要包括下列内容：
+
+- 命名规范
+
+- 设计规范
+
+- 语法规范
+
+- 优化相关
+
+- PG兼容性
+
+- 常用函数
+
+除此之外,对规范的每条细则均给出具体的范例。
+
+### 适用范围
+
+本规范适用于MogDB/openGauss 1.0.0及以上版本。
+
+## 命名规范
+
+### 对象命名统一规范
+
+数据库对象，如database, schema, table, column, view, index, constraint,sequence, function, trigger等命名统一标准如下：
+
+- 建议使用小写字母、数字、下划线的组合
+
+- 命名尽量采用富有意义英文词汇
+
+- 建议不使用双引号即"包围，除非必须包含大写字母或空格等特殊字符
+
+- 长度不能超过63个字符
+
+- 不建议以PG、GS开头（避免与系统DB object混淆），不建议以数字开头
+
+- 禁止使用保留字，保留关键字参考官方文档。
+
+- table能包含的column数目,根据字段类型的不同，数目在 250 到 1600 之间
+
+### 临时及备份对象命名
+
+- 临时或备份的数据库对象名，如table,建议添加日期, 如dba.trade_record_2020_12_08 (其中dba 为DBA专用schema，trade_record为表名，2020_12_08为备份日期)。
+
+### 表空间命名
+
+- 数据库的用户表空间用ts_<表空间名>来表现，其中，表空间名分为：
+  1. 数据空间：对于用户的缺省表空间，用default来表现。对于其他的表空间，根据寄存在表空间上的表的类别来表现。如放代码的表，用code来表现。放客户资料的表，用customer来表现。尽量用一个表空间来寄存该类的表。如果某表特殊大，可考虑单独使用一个表空间。
+  2. 索引空间：在相应的数据表空间的名字前加idx_。如对用户缺省表空间的索引空间，用ts_idx_default来表现。对代码表的索引表空间，用ts_idx_code来表现。
+
+- 表空间名禁止以"PG_"开头。
+
+### 索引命名
+
+- Index对象命名规则为: 表名_列名_idx,如student_name_idx,该索引命名方式为MogDB/openGauss数据库在创建索引时没有明确指定索引名称时的默认命名方式。
+
+  因此建议创建索引时，不显式给出index name,使用DBMS默认值。
+
+```sql
+create unique index on departments(department_id);
+
+CREATE INDEX
+
+ \di
+
++----------+-------------------------------+--------+---------+
+
+| Schema  | Name              | Type  | Owner  |
+
+|----------+-------------------------------+--------+---------|
+
+| mogdb   | departments_department_id_idx | index  | mogdb  |
+
++----------+-------------------------------+--------+---------+
+
+SELECT 1
+```
+
+### 变量命名
+
+- 命名应该使用英文单词,避免使用拼音,特别不应该使用拼音简写。命名不允许使用中文或者特殊字符。
+
+- 如果不涉及复杂运算,一律用number定义计数等简单应用。
+
+### 分区表命名
+
+- 分区表的表名遵循普通表的正常命名规则。
+
+- 按时间范围分区（每月一个分区）,分区名字为PART_YYYYMM。
+
+  举例： PART_201901、PART_201902
+
+### 函数命名
+
+- 名称应与其实际功能保持一致。导致发生某动作应以动词为前缀命令。
+
+示例：以下命名符合规范：
+
+```
+func_addgroups(增加多个群组)
+func_addgroup(增加一个群组)
+```
+
+## 设计规范
+
+### database设计
+
+- 数据库优先使用兼容PG类型的方式来创建。
+
+- 数据库编码只能用utf8。
+
+### tablespace设计
+
+- 一般较大的表或索引单独分配一个tablespace。
+
+- 高频率insert的对象分成一组，存在对应的tablespace中。
+
+- 增、删、改的对象分成一组，存在对应的tablespace中。
+
+- 表和索引分别存于不同的tablespace。
+
+- 原则上每个schema对应一个表空间和一个相应索引表空间；每个schema下的大表对应一个单独的表空间和索引表空间。
+
+### table设计
+
+- 设计表结构时，应该规划好，避免经常添加字段，或者修改字段类型或长度。
+
+- 必须为表添加注释信息，表名与注释信息相匹配。
+
+- 禁止使用unlogged关键字新建表，默认创建非压缩行表。
+
+- 每个表在创建时候,必须指定所在的表空间,不要采用默认表空间以防止表建立在系统表空间上导致性能问题。对于事务比较繁忙的数据表,必须存放在专用表空间中。
+
+- 作为表间连接关系的字段，数据类型必须保持严格一致，避免索引无法正常使用。
+
+- 禁止使用VARCHAR或其他字符类型来存储日期值，如果使用，则不能在此字段上做运算，需要在数据规范中严格定义。
+
+- 字段必须添加能够清楚表示其含义的注释，状态类字段的注释中必须明确列出各状态值的说明。
+
+- 对于频繁更新的表，建议建表时指定表的fillfactor=85，每页预留15%的空间给HOT更新使用。
+
+- 表结构中字段定义的数据类型与应用程序中的定义保持一致，表之间字段校对规则一致，避免报错或无法使用索引的情况发生。
+
+  说明：比如A表user_id字段数据类型定义为varchar，但是SQL语句查询为 where user_id=1234；
+
+### partition table设计
+
+- MogDB/openGauss数据库支持的分区表为范围分区表。
+
+- 分区表的个数不建议超过1000个。
+
+- 主键或唯一索引必须要包含分区键。
+
+- 对于数据量比较大的表,根据表数据的属性进行分区,以得到较好的性能。
+
+- 普通表若要转成分区表，需要新建分区表，然后把普通表中的数据导入到新建的分区表中。因此在初始设计表时，请根据业务提前规划是否使用分区表。
+
+- 建议有定期历史数据删除需求的业务，表按时间分区，删除时不要使用DELETE操作，而是DROP或者TRUNCATE对应的表。
+
+- 在分区表中不建议使用全局索引，因为做分区维护操作时可能会导致全局索引失效，造成难以维护。
+
+#### 分区表的使用
+
+按照以下方式对范围分区表进行操作。
+
+- 创建表空间
+
+```sql
+mogdb=# CREATE TABLESPACE example1 RELATIVE LOCATION 'tablespace1/tablespace_1';
+mogdb=# CREATE TABLESPACE example2 RELATIVE LOCATION 'tablespace2/tablespace_2';
+mogdb=# CREATE TABLESPACE example3 RELATIVE LOCATION 'tablespace3/tablespace_3';
+mogdb=# CREATE TABLESPACE example4 RELATIVE LOCATION 'tablespace4/tablespace_4';
+```
+
+当结果显示为如下信息，则表示创建成功。
+
+```sql
+CREATE TABLESPACE
+```
+
+- 创建分区表
+
+```sql
+mogdb=# CREATE TABLE mogdb_usr.customer_address
+(
+  ca_address_sk    integer          NOT NULL  ,
+  ca_address_id    character(16)       NOT NULL  ,
+  ca_street_number   character(10)            ,
+  ca_street_name    character varying(60)        ,
+  ca_street_type    character(15)            ,
+  ca_suite_number   character(10)            ,
+  ca_city       character varying(60)        ,
+  ca_county      character varying(30)        ,
+  ca_state       character(2)             ,
+  ca_zip        character(10)            ,
+  ca_country      character varying(20)        ,
+  ca_gmt_offset    numeric(5,2)             ,
+  ca_location_type   character(20)
+)
+TABLESPACE example1
+
+PARTITION BY RANGE (ca_address_sk)
+(
+    PARTITION P1 VALUES LESS THAN(5000),
+    PARTITION P2 VALUES LESS THAN(10000),
+    PARTITION P3 VALUES LESS THAN(15000),
+    PARTITION P4 VALUES LESS THAN(20000),
+    PARTITION P5 VALUES LESS THAN(25000),
+    PARTITION P6 VALUES LESS THAN(30000),
+    PARTITION P7 VALUES LESS THAN(40000),
+    PARTITION P8 VALUES LESS THAN(MAXVALUE) TABLESPACE example2
+)
+ENABLE ROW MOVEMENT;
+```
+
+当结果显示为如下信息，则表示创建成功。
+
+```sql
+CREATE TABLE
+```
+
+   ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) 创建列存分区表的数量建议不超过1000个。
+
+- 插入数据
+
+将表mogdb_usr.customer_address的数据插入到表mogdb_usr.customer_address_bak中。例如在数据库中创建了一个表mogdb_usr.customer_address的备份表mogdb_usr.customer_address_bak，现在需要将表mogdb_usr.customer_address中的数据插入到表mogdb_usr.customer_address_bak中，则可以执行如下命令。
+
+```sql
+mogdb=# CREATE TABLE mogdb_usr.customer_address_bak
+(
+  ca_address_sk    integer          NOT NULL  ,
+  ca_address_id    character(16)       NOT NULL  ,
+  ca_street_number   character(10)            ,
+  ca_street_name    character varying(60)        ,
+  ca_street_type    character(15)            ,
+  ca_suite_number   character(10)            ,
+  ca_city       character varying(60)        ,
+  ca_county      character varying(30)        ,
+  ca_state       character(2)             ,
+  ca_zip        character(10)            ,
+  ca_country      character varying(20)        ,
+  ca_gmt_offset    numeric(5,2)             ,
+  ca_location_type   character(20)
+)
+TABLESPACE example1
+PARTITION BY RANGE (ca_address_sk)
+(
+    PARTITION P1 VALUES LESS THAN(5000),
+    PARTITION P2 VALUES LESS THAN(10000),
+    PARTITION P3 VALUES LESS THAN(15000),
+    PARTITION P4 VALUES LESS THAN(20000),
+    PARTITION P5 VALUES LESS THAN(25000),
+    PARTITION P6 VALUES LESS THAN(30000),
+    PARTITION P7 VALUES LESS THAN(40000),
+    PARTITION P8 VALUES LESS THAN(MAXVALUE) TABLESPACE example2
+)
+ENABLE ROW MOVEMENT;
+CREATE TABLE
+mogdb=# INSERT INTO mogdb_usr.customer_address_bak SELECT * FROM mogdb_usr.customer_address;
+INSERT 0 0
+```
+
+- 修改分区表行迁移属性
+
+```sql
+mogdb=# ALTER TABLE mogdb_usr.customer_address_bak DISABLE ROW MOVEMENT;
+ALTER TABLE
+```
+
+- 删除分区
+
+删除分区P8。
+
+```sql
+mogdb=# ALTER TABLE mogdb_usr.customer_address_bak DROP PARTITION P8;
+ALTER TABLE
+```
+
+- 增加分区
+
+增加分区P8，范围为 40000<= P8<=MAXVALUE。
+
+```sql
+mogdb=# ALTER TABLE mogdb_usr.customer_address_bak ADD PARTITION P8 VALUES LESS THAN (MAXVALUE);
+ALTER TABLE
+```
+
+- 重命名分区
+
+重命名分区P8为P_9。
+
+```sql
+mogdb=# ALTER TABLE mogdb_usr.customer_address_bak RENAME PARTITION P8 TO P_9;
+ALTER TABLE
+```
+
+重命名分区P_9为P8。
+
+```sql
+mogdb=# ALTER TABLE mogdb_usr.customer_address_bak RENAME PARTITION FOR (40000) TO P8;
+ALTER TABLE
+```
+
+- 修改分区的表空间
+
+修改分区P6的表空间为example3。
+
+```sql
+mogdb=#  ALTER TABLE mogdb_usr.customer_address_bak MOVE PARTITION P6 TABLESPACE example3;
+ALTER TABLE
+```
+
+修改分区P4的表空间为example4。
+
+```sql
+mogdb=#  ALTER TABLE mogdb_usr.customer_address_bak MOVE PARTITION P4 TABLESPACE example4;
+ALTER TABLE
+```
+
+- 查询分区
+
+查询分区P6。
+
+```sql
+mogdb=# SELECT * FROM mogdb_usr.customer_address_bak PARTITION (P6);
+mogdb=# SELECT * FROM mogdb_usr.customer_address_bak PARTITION FOR (35888);
+```
+
+- 删除分区表和表空间
+
+```sql
+mogdb=# DROP TABLE mogdb_usr.customer_address_bak;
+DROP TABLE
+mogdb=# DROP TABLESPACE example1;
+mogdb=# DROP TABLESPACE example2;
+mogdb=# DROP TABLESPACE example3;
+mogdb=# DROP TABLESPACE example4;
+DROP TABLESPACE
+```
+
+### column设计
+
+- 建议可以采用数值类型的场合，则避免采用字符类型。
+
+- 建议可以采用varchar(N) 就避免采用char(N), 可以采用varchar(N) 就避免采用text,varchar。
+
+- 只允许用char(N)、varchar(N)及text字符类型。
+
+- MogDB/openGauss新建数据库默认兼容oracle,not null 约束不允许传入空字符串，空字符串默认会转换为null，兼容PG模式的数据库不会有这个问题。
+
+- 建议使用timestamp with time zone(timestamptz),而不用timestamp without time zone。
+
+- 建议使用NUMERIC(precision, scale)来存储货币金额和其它要求精确计算的数值, 而不建议使用real, double precision。
+
+### 序列设计
+
+- 禁止手动添加与表相关的序列。
+
+- 建表时指定列的serial或bigserial类型的方式来创建序列。
+
+- 序列应与代码中变量定义类型及范围一致，防止无法插入数据。
+
+### constraint设计
+
+#### 主键约束
+
+- 每个table必须包含主键。
+
+- 建议不要用有业务含义的名称作为主键,比如身份证或者国家名称,尽管其是unique的。
+
+- 建议主键的一步到位的写法:id serial primary key 或id bigserial primary key。
+
+- 建议内容系统中size较大的table主键的等效写法如下,便于后续维护。
+
+```sql
+create table test(id serial not null );
+create unique index CONCURRENTLY ON test (id);
+```
+
+#### 唯一约束
+
+除主键外，需存在唯一性约束的，可通过创建以“uk_”为前缀的唯一索引实现。
+
+#### 外键约束
+
+- 存在外键关系的表上尽量创建外键约束。
+
+- 使用外键时，一定要设置fk的action，例如cascade，set null，set default。
+
+#### 非空列
+
+- 所有非空列须在建表之初明确标识“NOT NULL”,上线之后，不再变更。同时需注意 NULL 与空字符‘’的查询结果差别：null 值会转换为 NULL, 而空值无字符显示。
+
+#### 检查约束
+
+- 对于字段有检查性约束,一般要求指定check规则。例如：性别、状态等字段。
+
+### index设计
+
+- MogDB/openGauss 提供的index类型: 行存表支持的索引类型：btree（行存表缺省值）、gin、gist。列存表支持的索引类型：Psort（列存表缺省值）、btree、gin。
+- 建议create 或 drop index 时,加 CONCURRENTLY参数,这是个好习惯，达到与写入数据并发的效果，列存表、分区表和临时表不支持CONCURRENTLY方式创建索引。
+- 建议对于频繁update, delete的包含于index 定义中的column的table, 用create index CONCURRENTLY , drop index CONCURRENTLY的方式进行维护其对应index。
+- 建议用unique index 代替unique constraints便于后续维护。
+- 建议对where 中带多个字段and条件的高频 query，参考数据分布情况，建多个字段的联合index。
+- 每个表的index数量不能超过5个。
+- 复合索引的建立需要进行仔细分析：
+  - 正确选择复合索引中的第一个字段,一般是选择性较好的且在where子句中常用的字段上；
+  - 复合索引的几个字段是否经常同时以AND方式出现在Where子句中？单字段查询是否极少甚至没有？如果是,则可以建立复合索引；否则考虑单字段索引；
+  - 如果复合索引中包含的字段经常单独出现在Where子句中,则分解为多个单字段索引；
+  - 如果既有单字段索引，又有以这个字段为首列的复合索引,一般可考虑删除单字段索引；
+  - 复合索引第一个字段一般不使用时间字段，因为时间字段多用于范围扫描，而前面的字段使用范围扫描后，后续字段无法用于索引过滤。
+  - 复合索引字段个数不能超过4个。
+
+- 频繁DML（写次数明显超过读次数）的表,不要建立太多的索引。
+
+- 无用的索引以及重复索引应删除，避免对执行计划及数据库性能造成负面影响。
+
+### view设计
+
+- 尽量使用简单视图，尽可能少使用复杂视图。
+
+  简单视图定义：数据来自单个表,且无分组（DISTINCT/GROUP BY）、无函数。
+
+  复杂视图定义：数据来自多个表,或有分组,有函数，表的个数不能超过3个。
+
+- 尽量不要使用嵌套视图，如果必须使用，不能超过2层嵌套。
+
+### function设计
+
+- 函数必须检索数据库表记录或数据库其他对象,甚至修改（执行Insert、Delete、Update、Drop、Create等操作）数据库信息。
+
+- 如果某项功能不需要和数据库打交道,则不得通过数据库函数的方式实现。
+
+- 在函数中避免采用DML或DDL语句。
+
+## 语法规范
+
+### 关于NULL
+
+- 说明：NULL 的判断：IS NULL ，IS NOT NULL。
+
+- 说明：注意boolean 类型取值 true，false，NULL。
+
+- 说明：小心NOT IN 集合中带有NULL元素。
+
+```sql
+mydb=# SELECT * FROM (VALUES(1),(2)) v(a) ;  a
+
+\---
+
+ 1
+
+ 2
+
+(2 rows)
+
+mydb=# select 1 NOT IN (1,NULL);
+
+?column?
+
+\---------
+
+f
+
+(1 row)
+
+mydb=# select 2 NOT IN (1,NULL);
+
+?column?
+
+\---------
+
+(1 row)
+
+mydb=# SELECT * FROM (VALUES(1),(2)) v(a) WHERE a NOT IN (1, NULL);  a
+
+\---
+
+(0 rows)
+```
+
+- 建议：使用count(1) 或count(*) 来统计行数，而不建议使用count(col) 来统计行数，因为NULL值不会计入。
+
+- 规则：count(多列列名)时，多列列名必须使用括号，例如count( (col1,col2,col3) )。
+
+- 注意：多列的count，即使所有列都为NULL，该行也被计数，所以效果与count(*) 一致。
+
+- 注意：count(distinct col) 计算某列的非NULL不重复数量，NULL不被计数
+
+ count(distinct (col1,col2,...) ) 计算多列的唯一值时，NULL会被计数，同时NULL与NULL会被认为是相同的。
+
+- 注意：NULL 的count与sum
+
+```sql
+select count(1), count(a), sum(a)  from (SELECT * FROM (VALUES (NULL), (2) ) v(a)) as foo where a is NULL;
+
+count | count | sum
+
+-------+-------+-----
+
+   1 |   0 |
+
+(1 row)
+```
+
+- 判断两个值是否相同（将NULL视为相同的值）
+
+```sql
+select null is distinct from null;
+
+?column?
+
+\---------
+
+f
+
+(1 row)
+
+select null is distinct from 1;
+
+?column?
+
+\---------
+
+t
+
+(1 row)
+
+select null is not distinct from null;
+
+?column?
+
+\---------
+
+t
+
+(1 row)
+
+select null is not distinct from 1;
+
+?column?
+
+\---------
+
+f
+
+(1 row)
+```
+
+### 关于索引失效
+
+- 在书写SQL语句时经常会在查询中使用函数及表达式，建议尽量不要在条件列上使用函数及表达式。在条件列上使用函数或者表达式的时候会导致使用不上该条件列上的索引，从而影响SQL的查询效率。尽量把函数或者表达式用在条件值上，避免使用在条件列上。示例：
+
+  `select name from tab where id+100>1000;`
+
+  可以改写为如下形式：
+
+  `select name from tab where id>1000-100;`
+
+- 查询语句中尽量不要使用左模糊查询。示例：
+
+  `select id from tab where name like '%ly';`
+
+- 查询中尽量不要使用负向查询，如not in/like，示例：
+
+  `select id from tab where name not in ('ly','ty');`
+
+### 确保使用到所有变量和参数
+
+- 声明变量也会产生一定的系统开销,并会显得代码不够严谨,在编译时未使用的变量会有告警,需修改以确保没有任何告警。
+
+## Query操作
+
+### DDL操作
+
+- DB object 尤其是COLUMN 加COMMENT，便于后续新人了解业务及维护
+
+- 发给DBA 发布的DDL，附带常用SQL: SELECT, INSERT ,DELETE, UPDATE，便于DBA给出create index CONCURRENTLY等其他优化建议
+
+- 向大size的table中add column时，将 alter table t add column col datatype not null default xxx；分解为如下，避免填充default值导致的过长时间锁表
+
+```sql
+alter table t add column col datatype ；
+
+alter table t alter column col set default xxx；
+
+update table t  set column= DEFAULT where id in ( select id from t where column is null limit
+
+1000 ) ; \watch 3
+
+alter table t alter column col set not null；
+```
+
+### DML操作
+
+- update 时做 <> 判断,比如update table_a set column_b = c where column_b <> c，禁止出现where 1=1
+
+- 单条DML语句操作数据量不超过10万
+
+- 建议清空表时,使用truncate,不建议使用delete
+
+### DQL操作
+
+- 非必须时禁止使用select *，只取所需字段，以减少包括不限于网络带宽消耗，避免表结构变更对程序的影响（比如某些prepare query）
+
+- 对报表类的或生成基础数据的查询，使用物化视图(MATERIALIZED VIEW)定期固化数据快照，避免对多表（尤其多写频繁的表）重复跑相同的查询
+
+- 复杂的统计查询可以尝试窗口函数 Window Functions
+
+- 避免关联字段数据类型不一致，禁止使用隐式类型转换
+
+- 不同字段的or语句使用union代替
+
+### 数据导入
+
+- 建议大批量的数据入库时，使用copy，不建议使用insert，以提高写入速度
+
+- 导入数据前需要先删除相关索引，导入完成后重建，提高数据导入速度
+
+### 事务操作
+
+- 事务中的sql逻辑尽可能的简单，让每个事务的粒度尽可能小，尽量lock少的资源，避免lock 、deadlock的产生，事务执行完及时提交
+
+- 执行CRAETE、DROP、ALTER等DDL操作, 尤其多条，不要显式的开transaction, 因为加lock的mode非常高,极易产生deadlock
+
+- state 为 idle in transaction 的连接，如果出现在Master, 会无谓的lock住相应的资源, 可导致后续产生lock,甚至deadlock; 出现在Slave,可导致卡住主从同步
+
+### 其他
+
+- 建议运行在SSD上的实例, random_page_cost (默认值为4) 设置为1.0~2.0之间, 使查询规划器更倾向于使用索引扫描
+
+- 建议在需要使用explain analyze 查看实际真正执行计划与时间时，如果是写入 query，强烈建议先开启事务， 然后回滚。
+
+- 对于频繁更新，膨胀率较高的表，应找窗口期执行表重组，降低高水位
+
+## PostgreSQL兼容性
+
+### 建库规范
+
+MogDB/openGauss创建数据库使用PG兼容模式如下：
+
+create database dbnam DBCOMPATIBILITY='PG' encoding=’utf8’;
+
+### 数据类型
+
+#### 数值类型
+
+在开发使用中，MogDB/openGauss只允许使用smallint、integer、bigint、numeric[(p[,s])]、serial、bigserial 这几种类型。
+
+| 类型             | PostgreSQL | openGauss | 存储尺寸     | 备注                                                    |
+| ---------------- | ---------- | --------- | ------------ | ------------------------------------------------------- |
+| tinyint          | /          | 支持      | 1字节        | 0 ～ 255                                                |
+| smallint         | 支持       | 支持      | 2字节        | -32,768 ~ +32,767                                       |
+| integer          | 支持       | 支持      | 4字节        | -2,147,483,648 ~ +2,147,483,647                         |
+| binary_integer   | /          | 支持      | /            | integer别名                                             |
+| bigint           | 支持       | 支持      | 8字节        | -9,223,372,036,854,775,808 ~ +9,223,372,036,854,775,807 |
+| decimal[(p[,s])] | 支持       | 支持      | 可变字节     | 最高小数点前131072位，以及小数点后16383位               |
+| numeric[(p[,s])] | 支持       | 支持      | 可变字节     | 最高小数点前131072位，以及小数点后16383位               |
+| number[(p[,s])]  | /          | 支持      | /            | numeric别名                                             |
+| real             | 支持       | 支持      | 4字节        | 6位十进制数字精度                                       |
+| float4           | /          | 支持      | 4字节        | 6位十进制数字精度                                       |
+| double precision | 支持       | 支持      | 8字节        | 15位十进制数字精度                                      |
+| binary_double    | /          | 支持      | 8字节        | double precision别名                                    |
+| float8           | /          | 支持      | 8字节        | 15位十进制数字精度                                      |
+| float[(p )]      | /          | 支持      | 4字节或8字节 |                                                         |
+| dec[(p,[s])]     | /          | 支持      | /            | 最高小数点前131072位，以及小数点后16383位               |
+| integer[(p,[s])] | /          | 支持      | /            | 最高小数点前131072位，以及小数点后16383位               |
+| smallserial      | 支持       | 支持      | 2字节        | 1 ~ 32,767                                              |
+| serial           | 支持       | 支持      | 4字节        | 1 ~ 2,147,483,647                                       |
+| bigserial        | 支持       | 支持      | 8字节        | 1 ~ 9,223,372,036,854,775,807                           |
+| tinyint          | /          | 支持      | 1字节        | 0 ～ 255                                                |
+
+#### 字符类型
+
+在开发使用中，MogDB/openGauss只允许使用char(n)、varchar(n)、text字符类型。
+
+| 类型         | PostgreSQL | openGauss | 存储尺寸                      | 备注                                                         |
+| ------------ | ---------- | --------- | ----------------------------- | ------------------------------------------------------------ |
+| char(n)      | 支持       | 支持      | pg中最大为1GB，og中最大为10MB | pg中n指字符数量，og中n指字节数量，兼容pg模式配置下n代表字符数量 |
+| nchar(n)     | /          | 支持      | 最大为10MB                    | n指字节数量，兼容pg模式配置下n代表字符数量                   |
+| varchar(n)   | 支持       | 支持      | pg中最大为1GB，og中最大为10MB | pg中n指字符数量，og中n指字节数量，兼容pg模式配置下n代表字符数量 |
+| varchar2(n)  | /          | 支持      | 最大为10MB                    | varchar(n)别名                                               |
+| nvarchar2(n) | /          | 支持      | 最大为10MB                    | n指字符数量                                                  |
+| text         | 支持       | 支持      | 1GB - 1                       |                                                              |
+| clob         | /          | 支持      | 1GB - 1                       | text别名                                                     |
+
+#### 时间类型
+
+在开发使用中，MogDB/openGauss只允许使用timestamp[(p )][with time zone]、date日期类型。
+
+| 类型                                | PostgreSQL | openGauss | 存储尺寸 | 备注                                                    |
+| ----------------------------------- | ---------- | --------- | -------- | ------------------------------------------------------- |
+| timestamp[(p )][without time zone] | 支持       | 支持      | 8字节    | 4713 BC - 294276 AD                                     |
+| timestamp[(p )][with time zone]    | 支持       | 支持      | 8字节    | 4713 BC - 294276 AD                                     |
+| date                                | 支持       | 支持      | 4字节    | 4713 BC - 5874897 AD (og实际存储空间大小为8字节)        |
+| time[(p )][without time zone]      | 支持       | 支持      | 8字节    | 00:00:00 - 24:00:00                                     |
+| time[(p )][with time zone]         | 支持       | 支持      | 12字节   | 00:00:00+1459 - 24:00:00-1459                           |
+| interval[fields][(p )]             | 支持       | 支持      | 16字节   | -178000000年 - 178000000年                              |
+| smalldatetime                       | /          | 支持      | 8字节    | 日期和时间，不带时区,精确到分钟，秒位大于等于30秒进一位 |
+| interval day(1) to second(p )       | /          | 支持      | 16字节   |                                                         |
+| reltime                             | /          | 支持      | 4字节    |                                                         |
+
+#### json类型
+
+MogDB/openGauss只允许使用json 类型。
+
+| 类型  | PostgreSQL | openGauss | 存储尺寸 | 备注 |
+| ----- | ---------- | --------- | -------- | ---- |
+| json  | 支持       | 支持      | /        |      |
+| jsonb | 支持       | /         | /        |      |
+
+### 关键字
+
+PostgreSQL与openGauss数据库中关键字差异化说明，保留是指数据库保留关键字，不允许自定义使用；非保留或空是指可以自定义使用，MogDB/openGauss保留字详情，请参考附件。
+
+| 关键字        | MogDB/openGauss          | PostgreSQL               |
+| ------------- | ------------------------ | ------------------------ |
+| AUTHID        | 保留                     | #N/A                     |
+| BUCKETS       | 保留                     | #N/A                     |
+| COMPACT       | 保留                     | #N/A                     |
+| DATE          | 非保留(不能是函数或类型) |                          |
+| DELTAMERGE    | 保留                     | #N/A                     |
+| EXCLUDED      | 保留                     | #N/A                     |
+| FENCED        | 保留                     | #N/A                     |
+| GROUPING      |                          | 非保留(不能是函数或类型) |
+| HDFSDIRECTORY | 保留                     | #N/A                     |
+| IS            | 保留                     | 保留(可以是函数或类型)   |
+| ISNULL        | 非保留                   | 保留(可以是函数或类型)   |
+| LATERAL       |                          | 保留                     |
+| LESS          | 保留                     | #N/A                     |
+| MAXVALUE      | 保留                     | 非保留                   |
+| MINUS         | 保留                     | #N/A                     |
+| MODIFY        | 保留                     | #N/A                     |
+| NLSSORT       | 保留                     | #N/A                     |
+| NUMBER        | 非保留(不能是函数或类型) |                          |
+| PERFORMANCE   | 保留                     | #N/A                     |
+| PROCEDURE     | 保留                     | 非保留                   |
+| REJECT        | 保留                     | #N/A                     |
+| ROWNUM        | 保留                     | #N/A                     |
+| SYSDATE       | 保留                     | #N/A                     |
+| VERIFY        | 保留                     | #N/A                     |
+
+### 隐式转换对应表
+
+| input_type  | target_type                                                | MogDB/openGauss |
+| ----------- | ---------------------------------------------------------- | --------------- |
+| bool        | int2、int4、int8                                           | 支持            |
+| int2        | bool、text、varchar、interval                              | 支持            |
+| int4        | bool、int2、text、varchar、interval                        | 支持            |
+| int8        | bool、text、varchar                                        | 支持            |
+| text        | int8、int4、int2、float4、float8、date、timestamp、nemeric | 支持            |
+| float4      | int8、int4、int2、text、varchar                            | 支持            |
+| float8      | int8、int4、int2、text、float4、varchar、interval、numeric | 支持            |
+| date        | text、varchar                                              | 支持            |
+| timestamp   | text、varchar                                              | 支持            |
+| timestamptz | text                                                       | 支持            |
+| numeric     | int8、int4、int2、text、varchar、interval                  | 支持            |
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/1-development-based-on-jdbc-overview.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/1-development-based-on-jdbc-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..1bab561f9c095b56adb9ef6e0f944222a8f179e9
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/1-development-based-on-jdbc-overview.md
@@ -0,0 +1,10 @@
+---
+title: 概述
+summary: 概述
+author: Guo Huan
+date: 2021-04-26
+---
+
+# 概述
+
+JDBC（Java Database Connectivity，Java数据库连接）是一种用于执行SQL语句的Java API，可以为多种关系数据库提供统一访问接口，应用程序可基于它操作数据。 MogDB库提供了对JDBC 4.0特性的支持，需要使用JDK1.8版本编译程序代码，不支持JDBC桥接ODBC方式。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/10-example-common-operations.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/10-example-common-operations.md
new file mode 100644
index 0000000000000000000000000000000000000000..7977be04b725e9ede4096db519cebe16c47b776c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/10-example-common-operations.md
@@ -0,0 +1,228 @@
+---
+title: 示例：常用操作
+summary: 示例：常用操作
+author: Guo Huan
+date: 2021-04-26
+---
+
+# 示例：常用操作
+
+<br/>
+
+## 示例1
+
+此示例将演示如何基于MogDB提供的JDBC接口开发应用程序。
+
+```java
+//DBtest.java
+//演示基于JDBC开发的主要步骤，会涉及创建数据库、创建表、插入数据等。
+
+import java.sql.Connection;
+import java.sql.DriverManager;
+import java.sql.PreparedStatement;
+import java.sql.SQLException;
+import java.sql.Statement;
+import java.sql.CallableStatement;
+
+public class DBTest {
+
+  //创建数据库连接。
+  public static Connection GetConnection(String username, String passwd) {
+    String driver = "org.postgresql.Driver";
+    String sourceURL = "jdbc:postgresql://localhost:8000/postgres";
+    Connection conn = null;
+    try {
+      //加载数据库驱动。
+      Class.forName(driver).newInstance();
+    } catch (Exception e) {
+      e.printStackTrace();
+      return null;
+    }
+
+    try {
+      //创建数据库连接。
+      conn = DriverManager.getConnection(sourceURL, username, passwd);
+      System.out.println("Connection succeed!");
+    } catch (Exception e) {
+      e.printStackTrace();
+      return null;
+    }
+
+    return conn;
+  };
+
+  //执行普通SQL语句，创建customer_t1表。
+  public static void CreateTable(Connection conn) {
+    Statement stmt = null;
+    try {
+      stmt = conn.createStatement();
+
+      //执行普通SQL语句。
+      int rc = stmt
+          .executeUpdate("CREATE TABLE customer_t1(c_customer_sk INTEGER, c_customer_name VARCHAR(32));");
+
+      stmt.close();
+    } catch (SQLException e) {
+      if (stmt != null) {
+        try {
+          stmt.close();
+        } catch (SQLException e1) {
+          e1.printStackTrace();
+        }
+      }
+      e.printStackTrace();
+    }
+  }
+
+  //执行预处理语句，批量插入数据。
+  public static void BatchInsertData(Connection conn) {
+    PreparedStatement pst = null;
+
+    try {
+      //生成预处理语句。
+      pst = conn.prepareStatement("INSERT INTO customer_t1 VALUES (?,?)");
+      for (int i = 0; i < 3; i++) {
+        //添加参数。
+        pst.setInt(1, i);
+        pst.setString(2, "data " + i);
+        pst.addBatch();
+      }
+      //执行批处理。
+      pst.executeBatch();
+      pst.close();
+    } catch (SQLException e) {
+      if (pst != null) {
+        try {
+          pst.close();
+        } catch (SQLException e1) {
+        e1.printStackTrace();
+        }
+      }
+      e.printStackTrace();
+    }
+  }
+
+  //执行预编译语句，更新数据。
+  public static void ExecPreparedSQL(Connection conn) {
+    PreparedStatement pstmt = null;
+    try {
+      pstmt = conn
+          .prepareStatement("UPDATE customer_t1 SET c_customer_name = ? WHERE c_customer_sk = 1");
+      pstmt.setString(1, "new Data");
+      int rowcount = pstmt.executeUpdate();
+      pstmt.close();
+    } catch (SQLException e) {
+      if (pstmt != null) {
+        try {
+          pstmt.close();
+        } catch (SQLException e1) {
+          e1.printStackTrace();
+        }
+      }
+      e.printStackTrace();
+    }
+  }
+
+
+//执行存储过程。
+  public static void ExecCallableSQL(Connection conn) {
+    CallableStatement cstmt = null;
+    try {
+
+      cstmt=conn.prepareCall("{? = CALL TESTPROC(?,?,?)}");
+      cstmt.setInt(2, 50);
+      cstmt.setInt(1, 20);
+      cstmt.setInt(3, 90);
+      cstmt.registerOutParameter(4, Types.INTEGER);  //注册out类型的参数，类型为整型。
+      cstmt.execute();
+      int out = cstmt.getInt(4);  //获取out参数
+      System.out.println("The CallableStatment TESTPROC returns:"+out);
+      cstmt.close();
+    } catch (SQLException e) {
+      if (cstmt != null) {
+        try {
+          cstmt.close();
+        } catch (SQLException e1) {
+          e1.printStackTrace();
+        }
+      }
+      e.printStackTrace();
+    }
+  }
+
+
+  /**
+   * 主程序，逐步调用各静态方法。
+   * @param args
+  */
+  public static void main(String[] args) {
+    //创建数据库连接。
+    Connection conn = GetConnection("tester", "Password1234");
+
+    //创建表。
+    CreateTable(conn);
+
+    //批插数据。
+    BatchInsertData(conn);
+
+    //执行预编译语句，更新数据。
+    ExecPreparedSQL(conn);
+
+    //执行存储过程。
+    ExecCallableSQL(conn);
+
+    //关闭数据库连接。
+    try {
+      conn.close();
+    } catch (SQLException e) {
+      e.printStackTrace();
+    }
+
+  }
+
+}
+```
+
+<br/>
+
+## 示例2 客户端内存占用过多解决
+
+此示例主要使用setFetchSize来调整客户端内存使用，它的原理是通过数据库游标来分批获取服务器端数据，但它会加大网络交互，可能会损失部分性能。
+
+由于游标事务内有效，故需要先关闭自动提交，最后需要执行手动提交。
+
+```java
+// 关闭掉自动提交
+conn.setAutoCommit(false);
+Statement st = conn.createStatement();
+
+// 打开游标，每次获取50行数据
+st.setFetchSize(50);
+ResultSet rs = st.executeQuery("SELECT * FROM mytable");
+conn.commit();
+while (rs.next())
+{
+    System.out.print("a row was returned.");
+}
+rs.close();
+
+// 关闭服务器游标。
+st.setFetchSize(0);
+rs = st.executeQuery("SELECT * FROM mytable");
+conn.commit();
+while (rs.next())
+{
+    System.out.print("many rows were returned.");
+}
+rs.close();
+
+// Close the statement.
+st.close();
+conn.close();
+```
+
+执行完毕后可使用如下命令恢复自动提交:
+
+```java
+conn.setAutoCommit(true);
+```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/11-example-retrying-sql-queries-for-applications.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/11-example-retrying-sql-queries-for-applications.md
new file mode 100644
index 0000000000000000000000000000000000000000..ca8f68fb16dfcba6c9f57474cc4cc1b240802880
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/11-example-retrying-sql-queries-for-applications.md
@@ -0,0 +1,205 @@
+---
+title: 示例：重新执行应用SQL
+summary: 示例：重新执行应用SQL
+author: Guo Huan
+date: 2021-04-26
+---
+
+# 示例：重新执行应用SQL
+
+当主数据库节点故障且10s未恢复时，MogDB会将对应的备数据库节点升主，使MogDB正常运行。备升主期间正在运行的作业会失败；备升主后启动的作业不会再受影响。如果要做到数据库节点主备切换过程中，上层业务不感知，可参考此示例构建业务层SQL重试机制。
+
+```java
+import java.sql.Connection;
+import java.sql.DriverManager;
+import java.sql.PreparedStatement;
+import java.sql.ResultSet;
+import java.sql.SQLException;
+import java.sql.Statement;
+
+class ExitHandler extends Thread {
+    private Statement cancel_stmt = null;
+
+    public ExitHandler(Statement stmt) {
+        super("Exit Handler");
+        this.cancel_stmt = stmt;
+    }
+    public void run() {
+        System.out.println("exit handle");
+        try {
+            this.cancel_stmt.cancel();
+        } catch (SQLException e) {
+            System.out.println("cancel query failed.");
+            e.printStackTrace();
+        }
+    }
+}
+
+public class SQLRetry {
+   //创建数据库连接。
+   public static Connection GetConnection(String username, String passwd) {
+     String driver = "org.postgresql.Driver";
+     String sourceURL = "jdbc:postgresql://10.131.72.136:8000/postgres";
+     Connection conn = null;
+     try {
+       //加载数据库驱动。
+       Class.forName(driver).newInstance();
+     } catch (Exception e) {
+       e.printStackTrace();
+       return null;
+     }
+
+     try {
+       //创建数据库连接。
+       conn = DriverManager.getConnection(sourceURL, username, passwd);
+       System.out.println("Connection succeed!");
+     } catch (Exception e) {
+       e.printStackTrace();
+       return null;
+     }
+
+     return conn;
+}
+
+   //执行普通SQL语句，创建jdbc_test1表。
+   public static void CreateTable(Connection conn) {
+     Statement stmt = null;
+     try {
+       stmt = conn.createStatement();
+
+
+       Runtime.getRuntime().addShutdownHook(new ExitHandler(stmt));
+
+       //执行普通SQL语句。
+       int rc2 = stmt
+          .executeUpdate("DROP TABLE if exists jdbc_test1;");
+
+       int rc1 = stmt
+          .executeUpdate("CREATE TABLE jdbc_test1(col1 INTEGER, col2 VARCHAR(10));");
+
+       stmt.close();
+     } catch (SQLException e) {
+       if (stmt != null) {
+         try {
+           stmt.close();
+         } catch (SQLException e1) {
+           e1.printStackTrace();
+         }
+       }
+       e.printStackTrace();
+     }
+   }
+
+   //执行预处理语句，批量插入数据。
+   public static void BatchInsertData(Connection conn) {
+     PreparedStatement pst = null;
+
+     try {
+       //生成预处理语句。
+       pst = conn.prepareStatement("INSERT INTO jdbc_test1 VALUES (?,?)");
+       for (int i = 0; i < 100; i++) {
+        //添加参数。
+         pst.setInt(1, i);
+         pst.setString(2, "data " + i);
+         pst.addBatch();
+       }
+       //执行批处理。
+       pst.executeBatch();
+       pst.close();
+     } catch (SQLException e) {
+       if (pst != null) {
+         try {
+           pst.close();
+         } catch (SQLException e1) {
+         e1.printStackTrace();
+         }
+       }
+       e.printStackTrace();
+     }
+   }
+
+   //执行预编译语句，更新数据。
+   private static boolean QueryRedo(Connection conn){
+     PreparedStatement pstmt = null;
+     boolean retValue = false;
+     try {
+       pstmt = conn
+           .prepareStatement("SELECT col1 FROM jdbc_test1 WHERE col2 = ?");
+
+           pstmt.setString(1, "data 10");
+           ResultSet rs = pstmt.executeQuery();
+
+           while (rs.next()) {
+               System.out.println("col1 = " + rs.getString("col1"));
+           }
+           rs.close();
+
+       pstmt.close();
+        retValue = true;
+      } catch (SQLException e) {
+       System.out.println("catch...... retValue " + retValue);
+       if (pstmt != null) {
+         try {
+          pstmt.close();
+        } catch (SQLException e1) {
+          e1.printStackTrace();
+         }
+       }
+       e.printStackTrace();
+     }
+
+      System.out.println("finesh......");
+     return retValue;
+   }
+
+   //查询语句，执行失败重试，重试次数可配置。
+   public static void ExecPreparedSQL(Connection conn) throws InterruptedException {
+         int maxRetryTime = 50;
+         int time = 0;
+         String result = null;
+         do {
+             time++;
+             try {
+  System.out.println("time:" + time);
+  boolean ret = QueryRedo(conn);
+  if(ret == false){
+   System.out.println("retry, time:" + time);
+   Thread.sleep(10000);
+   QueryRedo(conn);
+  }
+             } catch (Exception e) {
+                 e.printStackTrace();
+             }
+         } while (null == result && time < maxRetryTime);
+
+   }
+
+   /**
+    * 主程序，逐步调用各静态方法。
+    * @param args
+    * @throws InterruptedException
+    */
+   public static void main(String[] args) throws InterruptedException {
+     //创建数据库连接。
+     Connection conn = GetConnection("testuser", "test@123");
+
+     //创建表。
+     CreateTable(conn);
+
+     //批插数据。
+     BatchInsertData(conn);
+
+     //执行预编译语句，更新数据。
+     ExecPreparedSQL(conn);
+
+     //关闭数据库连接。
+     try {
+       conn.close();
+     } catch (SQLException e) {
+       e.printStackTrace();
+     }
+
+   }
+
+ }
+```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/12-example-importing-and-exporting-data-through-local-files.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/12-example-importing-and-exporting-data-through-local-files.md
new file mode 100644
index 0000000000000000000000000000000000000000..607d1c30fc37d55508e114d001970cd442031e8f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/12-example-importing-and-exporting-data-through-local-files.md
@@ -0,0 +1,119 @@
+---
+title: 示例：通过本地文件导入导出数据
+summary: 示例：通过本地文件导入导出数据
+author: Guo Huan
+date: 2021-04-26
+---
+
+# 示例：通过本地文件导入导出数据
+
+在使用JAVA语言基于MogDB进行二次开发时，可以使用CopyManager接口，通过流方式，将数据库中的数据导出到本地文件或者将本地文件导入数据库中，文件格式支持CSV、TEXT等格式。
+
+样例程序如下，执行时需要加载MogDB jdbc驱动。
+
+```java
+import java.sql.Connection;
+import java.sql.DriverManager;
+import java.io.IOException;
+import java.io.FileInputStream;
+import java.io.FileOutputStream;
+import java.sql.SQLException;
+import org.postgresql.copy.CopyManager;
+import org.postgresql.core.BaseConnection;
+
+public class Copy{
+
+     public static void main(String[] args)
+     {
+      String urls = new String("jdbc:postgresql://10.180.155.74:8000/postgres"); //数据库URL
+      String username = new String("jack");            //用户名
+      String password = new String("Gauss@123");             //密码
+      String tablename = new String("migration_table"); //定义表信息
+      String tablename1 = new String("migration_table_1"); //定义表信息
+      String driver = "org.postgresql.Driver";
+      Connection conn = null;
+
+      try {
+            Class.forName(driver);
+            conn = DriverManager.getConnection(urls, username, password);
+          } catch (ClassNotFoundException e) {
+               e.printStackTrace(System.out);
+          } catch (SQLException e) {
+               e.printStackTrace(System.out);
+          }
+
+      // 将SELECT * FROM migration_table查询结果导出到本地文件d:/data.txt
+      try {
+     copyToFile(conn, "d:/data.txt", "(SELECT * FROM migration_table)");
+   } catch (SQLException e) {
+  k
+  e.printStackTrace();
+   } catch (IOException e) {
+
+  e.printStackTrace();
+   }
+      //将d:/data.txt中的数据导入到migration_table_1中。
+      try {
+      copyFromFile(conn, "d:/data.txt", tablename1);
+   } catch (SQLException e) {
+         e.printStackTrace();
+ } catch (IOException e) {
+
+  e.printStackTrace();
+ }
+
+      // 将migration_table_1中的数据导出到本地文件d:/data1.txt
+      try {
+      copyToFile(conn, "d:/data1.txt", tablename1);
+   } catch (SQLException e) {
+
+  e.printStackTrace();
+   } catch (IOException e) {
+
+
+  e.printStackTrace();
+ }
+     }
+  // 使用copyIn把数据从文件中导入数据库，
+  public static void copyFromFile(Connection connection, String filePath, String tableName)
+         throws SQLException, IOException {
+
+     FileInputStream fileInputStream = null;
+
+     try {
+         CopyManager copyManager = new CopyManager((BaseConnection)connection);
+         fileInputStream = new FileInputStream(filePath);
+         copyManager.copyIn("COPY " + tableName + " FROM STDIN", fileInputStream);
+     } finally {
+         if (fileInputStream != null) {
+             try {
+                 fileInputStream.close();
+             } catch (IOException e) {
+                 e.printStackTrace();
+             }
+         }
+     }
+ }
+
+  // 使用copyOut把数据从数据库中导出到文件中
+  public static void copyToFile(Connection connection, String filePath, String tableOrQuery)
+          throws SQLException, IOException {
+
+      FileOutputStream fileOutputStream = null;
+
+      try {
+          CopyManager copyManager = new CopyManager((BaseConnection)connection);
+          fileOutputStream = new FileOutputStream(filePath);
+          copyManager.copyOut("COPY " + tableOrQuery + " TO STDOUT", fileOutputStream);
+      } finally {
+          if (fileOutputStream != null) {
+              try {
+                  fileOutputStream.close();
+              } catch (IOException e) {
+                  e.printStackTrace();
+              }
+          }
+      }
+  }
+}
+```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/13-example-2-migrating-data-from-a-my-database-to-mogdb.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/13-example-2-migrating-data-from-a-my-database-to-mogdb.md
new file mode 100644
index 0000000000000000000000000000000000000000..59d6a8e332235ddc847ff6ddd6d5b72146d6792a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/13-example-2-migrating-data-from-a-my-database-to-mogdb.md
@@ -0,0 +1,97 @@
+---
+title: 示例：从MY向MogDB进行数据迁移
+summary: 示例：从MY向MogDB进行数据迁移
+author: Guo Huan
+date: 2021-04-26
+---
+
+# 示例：从MY向MogDB进行数据迁移
+
+下面示例演示如何通过CopyManager从MY向MogDB进行数据迁移的过程。
+
+```java
+import java.io.StringReader;
+import java.sql.Connection;
+import java.sql.DriverManager;
+import java.sql.ResultSet;
+import java.sql.SQLException;
+import java.sql.Statement;
+
+import org.postgresql.copy.CopyManager;
+import org.postgresql.core.BaseConnection;
+
+public class Migration{
+
+    public static void main(String[] args) {
+        String url = new String("jdbc:postgresql://10.180.155.74:8000/postgres"); //数据库URL
+        String user = new String("jack");            //MogDB用户名
+        String pass = new String("Gauss@123");             //MogDB密码
+        String tablename = new String("migration_table"); //定义表信息
+        String delimiter = new String("|");              //定义分隔符
+        String encoding = new String("UTF8");            //定义字符集
+        String driver = "org.postgresql.Driver";
+        StringBuffer buffer = new StringBuffer();       //定义存放格式化数据的缓存
+
+        try {
+            //获取源数据库查询结果集
+            ResultSet rs = getDataSet();
+
+            //遍历结果集，逐行获取记录
+            //将每条记录中各字段值，按指定分隔符分割，由换行符结束，拼成一个字符串
+            //把拼成的字符串，添加到缓存buffer
+            while (rs.next()) {
+                buffer.append(rs.getString(1) + delimiter
+                        + rs.getString(2) + delimiter
+                        + rs.getString(3) + delimiter
+                        + rs.getString(4)
+                        + "\n");
+            }
+            rs.close();
+
+            try {
+                //建立目标数据库连接
+                Class.forName(driver);
+                Connection conn = DriverManager.getConnection(url, user, pass);
+                BaseConnection baseConn = (BaseConnection) conn;
+                baseConn.setAutoCommit(false);
+
+                //初始化表信息
+                String sql = "Copy " + tablename + " from STDIN DELIMITER " + "'" + delimiter + "'" + " ENCODING " + "'" + encoding + "'";
+
+                //提交缓存buffer中的数据
+                CopyManager cp = new CopyManager(baseConn);
+                StringReader reader = new StringReader(buffer.toString());
+                cp.copyIn(sql, reader);
+                baseConn.commit();
+                reader.close();
+                baseConn.close();
+            } catch (ClassNotFoundException e) {
+                e.printStackTrace(System.out);
+            } catch (SQLException e) {
+                e.printStackTrace(System.out);
+            }
+
+        } catch (Exception e) {
+            e.printStackTrace();
+        }
+    }
+
+    //********************************
+    // 从源数据库返回查询结果集
+    //*********************************
+    private static ResultSet getDataSet() {
+        ResultSet rs = null;
+        try {
+            Class.forName("com.MY.jdbc.Driver").newInstance();
+            Connection conn = DriverManager.getConnection("jdbc:MY://10.119.179.227:3306/jack?useSSL=false&allowPublicKeyRetrieval=true", "jack", "Gauss@123");
+            Statement stmt = conn.createStatement();
+            rs = stmt.executeQuery("select * from migration_table");
+        } catch (SQLException e) {
+            e.printStackTrace();
+        } catch (Exception e) {
+            e.printStackTrace();
+        }
+        return rs;
+    }
+}
+```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/14-example-logic-replication-code.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/14-example-logic-replication-code.md
new file mode 100644
index 0000000000000000000000000000000000000000..96c6772524e5ffae0956a3d627766fff4c7cf982
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/14-example-logic-replication-code.md
@@ -0,0 +1,111 @@
+---
+title: 示例：逻辑复制代码示例
+summary: 示例：逻辑复制代码示例
+author: Guo Huan
+date: 2021-04-26
+---
+
+# 示例：逻辑复制代码示例
+
+下面示例演示如何通过JDBC接口使用逻辑复制功能的过程。
+
+```java
+//逻辑复制功能示例: 文件名，LogicalReplicationDemo.java
+//前提条件: 添加JDBC用户机器IP到数据库白名单里，在pg_hba.conf添加以下内容即可:
+//假设JDBC用户IP为10.10.10.10
+//host    all             all             10.10.10.10/32        sha256
+//host    replication     all             10.10.10.10/32        sha256
+
+import org.postgresql.PGProperty;
+import org.postgresql.jdbc.PgConnection;
+import org.postgresql.replication.LogSequenceNumber;
+import org.postgresql.replication.PGReplicationStream;
+
+import java.nio.ByteBuffer;
+import java.sql.DriverManager;
+import java.util.Properties;
+import java.util.concurrent.TimeUnit;
+
+public class LogicalReplicationDemo {
+    public static void main(String[] args) {
+        String driver = "org.postgresql.Driver";
+    //此处配置数据库IP以及端口，
+        String sourceURL = "jdbc:postgresql://$ip:$port/postgres";
+        PgConnection conn = null;
+    //默认逻辑复制槽的名称是: replication_slot
+    //测试模式: 创建逻辑复制槽
+        int TEST_MODE_CREATE_SLOT = 1;
+    //测试模式: 开启逻辑复制（前提条件是逻辑复制槽已经存在）
+        int TEST_MODE_START_REPL = 2;
+    //测试模式: 删除逻辑复制槽
+        int TEST_MODE_DROP_SLOT = 3;
+        //开启不同的测试模式
+        int testMode = TEST_MODE_START_REPL;
+
+        try {
+            Class.forName(driver);
+        } catch (Exception e) {
+            e.printStackTrace();
+            return;
+        }
+
+        try {
+            Properties properties = new Properties();
+            PGProperty.USER.set(properties, "user");
+            PGProperty.PASSWORD.set(properties, "passwd");
+        //对于逻辑复制，以下三个属性是必须配置项
+            PGProperty.ASSUME_MIN_SERVER_VERSION.set(properties, "9.4");
+            PGProperty.REPLICATION.set(properties, "database");
+            PGProperty.PREFER_QUERY_MODE.set(properties, "simple");
+            conn = (PgConnection) DriverManager.getConnection(sourceURL, properties);
+            System.out.println("connection success!");
+
+            if(testMode == TEST_MODE_CREATE_SLOT){
+                conn.getReplicationAPI()
+                        .createReplicationSlot()
+                        .logical()
+                        .withSlotName("replication_slot")
+                        .withOutputPlugin("test_decoding")
+                        .make();
+            }else if(testMode == TEST_MODE_START_REPL) {
+                //开启此模式前需要创建复制槽
+                LogSequenceNumber waitLSN = LogSequenceNumber.valueOf("6F/E3C53568");
+                PGReplicationStream stream = conn
+                        .getReplicationAPI()
+                        .replicationStream()
+                        .logical()
+                        .withSlotName("replication_slot")
+                        .withSlotOption("include-xids", false)
+                        .withSlotOption("skip-empty-xacts", true)
+                        .withStartPosition(waitLSN)
+                        .start();
+                while (true) {
+                    ByteBuffer byteBuffer = stream.readPending();
+
+                    if (byteBuffer == null) {
+                        TimeUnit.MILLISECONDS.sleep(10L);
+                        continue;
+                    }
+
+                    int offset = byteBuffer.arrayOffset();
+                    byte[] source = byteBuffer.array();
+                    int length = source.length - offset;
+                    System.out.println(new String(source, offset, length));
+
+                    //如果需要flush lsn，根据业务实际情况调用以下接口
+                    //LogSequenceNumber lastRecv = stream.getLastReceiveLSN();
+                    //stream.setFlushedLSN(lastRecv);
+                    //stream.forceUpdateStatus();
+
+                }
+            }else if(testMode == TEST_MODE_DROP_SLOT){
+                conn.getReplicationAPI()
+                        .dropReplicationSlot("replication_slot");
+            }
+        } catch (Exception e) {
+            e.printStackTrace();
+            return;
+        }
+    }
+}
+```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/14.1-example-parameters-for-connecting-to-the-database-in-different-scenarios.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/14.1-example-parameters-for-connecting-to-the-database-in-different-scenarios.md
new file mode 100644
index 0000000000000000000000000000000000000000..689df80e0831e586016fedb980f41c8a66928603
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/14.1-example-parameters-for-connecting-to-the-database-in-different-scenarios.md
@@ -0,0 +1,60 @@
+---
+title: 不同场景下连接数据库参数配置
+summary: 不同场景下连接数据库参数配置
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# 示例：不同场景下连接数据库参数配置
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 以下示例场景中node代表“host:port”，host为数据库服务器名称或IP地址，port为数据库服务器端口。
+
+## 容灾场景
+
+某客户有两套数据库数据库实例，其中A数据库实例为生产数据库实例，B数据库实例为容灾数据库实例。当客户执行容灾切换时，A数据库实例将降为容灾数据库实例，B数据库实例将升为生产数据库实例。此时为了避免修改配置文件导致的应用重启或重新发版。客户可在初始配置文件时，即将A、B数据库实例写入连接串中。此时在主数据库实例不可连接时，驱动将尝试对容灾数据库实例建连。例如A数据库实例为{node1,node2,node3}。B数据库实例为{node4,node5,node6}。
+
+则url可参考如下进行配置：
+
+```java
+jdbc:postgresql://node1,node2,node3,node4,node5,node6/database?priorityServers=3
+```
+
+## 负载均衡场景
+
+某客户存在一套集中式数据库实例，包含1主2备三个节点{node1，node2，node3}，其中node1为主节点，node2、node3为备节点。
+
+客户希望同一应用程序上建立的连接，较为均匀的分布在三个节点上，则url可参考如下配置：
+
+```java
+jdbc:postgresql://node1,node2,node3/database?loadBalanceHosts=true
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **注意：** 使用loadBalanceHosts时，若连接建立在备DN上，将无法执行写操作。如果业务需要执行读写操作，请勿配置该参数。
+
+## 日志诊断场景
+
+某客户在使用中出现数据导入慢或出现一些难以分析的异常报错，可通过开启trace日志进行诊断，url可参考如下进行配置。
+
+```
+jdbc:postgresql://node1/database?loggerLevel=trace&loggerFile=jdbc.log
+```
+
+## 高性能场景
+
+某客户对于相同sql可能多次执行，仅是传参不同，为了提升执行效率，可开启prepareThreshold参数，避免重复生成执行计划，url可参考如下配置。
+
+```java
+jdbc:postgresql://node1/database?prepareThreshold=5
+```
+
+某客户一次查询1000万数据，为避免同时返回造成内存溢出，可使用defaultRowFetchSize，url可参考如下配置。
+
+```java
+jdbc:postgresql://node1/database?defaultRowFetchSize=50000
+```
+
+某客户需要批量插入1000万数据，为提升效率，可使用batchMode，url可参考如下配置。
+
+```java
+jdbc:postgresql://node1/database?batchMode=true
+```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/1-java-sql-Connection.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/1-java-sql-Connection.md
new file mode 100644
index 0000000000000000000000000000000000000000..0c36598e4120bf55e7fc9136e1f2a33e5873db2c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/1-java-sql-Connection.md
@@ -0,0 +1,67 @@
+---
+title: java.sql.Connection
+summary: java.sql.Connection
+author: Guo Huan
+date: 2021-05-17
+---
+
+# java.sql.Connection
+
+java.sql.Connection是数据库连接接口。
+
+**表 1**  对java.sql.Connection接口的支持情况
+
+| 方法名                                                       | 返回值类型                       | 支持JDBC 4 |
+| :----------------------------------------------------------- | :------------------------------- | :--------- |
+| abort(Executor executor)                                     | void                             | Yes        |
+| clearWarnings()                                              | void                             | Yes        |
+| close()                                                      | void                             | Yes        |
+| commit()                                                     | void                             | Yes        |
+| createArrayOf(String typeName, Object[] elements)            | Array                            | Yes        |
+| createBlob()                                                 | Blob                             | Yes        |
+| createClob()                                                 | Clob                             | Yes        |
+| createSQLXML()                                               | SQLXML                           | Yes        |
+| createStatement()                                            | Statement                        | Yes        |
+| createStatement(int resultSetType, int resultSetConcurrency) | Statement                        | Yes        |
+| createStatement(int resultSetType, int resultSetConcurrency, int resultSetHoldability) | Statement                        | Yes        |
+| getAutoCommit()                                              | Boolean                          | Yes        |
+| getCatalog()                                                 | String                           | Yes        |
+| getClientInfo()                                              | Properties                       | Yes        |
+| getClientInfo(String name)                                   | String                           | Yes        |
+| getHoldability()                                             | int                              | Yes        |
+| getMetaData()                                                | DatabaseMetaData                 | Yes        |
+| getNetworkTimeout()                                          | int                              | Yes        |
+| getSchema()                                                  | String                           | Yes        |
+| getTransactionIsolation()                                    | int                              | Yes        |
+| getTypeMap()                                                 | Map&lt;String,Class&lt;?&gt;&gt; | Yes        |
+| getWarnings()                                                | SQLWarning                       | Yes        |
+| isClosed()                                                   | Boolean                          | Yes        |
+| isReadOnly()                                                 | Boolean                          | Yes        |
+| isValid(int timeout)                                         | boolean                          | Yes        |
+| nativeSQL(String sql)                                        | String                           | Yes        |
+| prepareCall(String sql)                                      | CallableStatement                | Yes        |
+| prepareCall(String sql, int resultSetType, int resultSetConcurrency) | CallableStatement                | Yes        |
+| prepareCall(String sql, int resultSetType, int resultSetConcurrency, int resultSetHoldability) | CallableStatement                | Yes        |
+| prepareStatement(String sql)                                 | PreparedStatement                | Yes        |
+| prepareStatement(String sql, int autoGeneratedKeys)          | PreparedStatement                | Yes        |
+| prepareStatement(String sql, int[] columnIndexes)            | PreparedStatement                | Yes        |
+| prepareStatement(String sql, int resultSetType, int resultSetConcurrency) | PreparedStatement                | Yes        |
+| prepareStatement(String sql, int resultSetType, int resultSetConcurrency, int resultSetHoldability) | PreparedStatement                | Yes        |
+| prepareStatement(String sql, String[] columnNames)           | PreparedStatement                | Yes        |
+| releaseSavepoint(Savepoint savepoint)                        | void                             | Yes        |
+| rollback()                                                   | void                             | Yes        |
+| rollback(Savepoint savepoint)                                | void                             | Yes        |
+| setAutoCommit(boolean autoCommit)                            | void                             | Yes        |
+| setClientInfo(Properties properties)                         | void                             | Yes        |
+| setClientInfo(String name,String value)                      | void                             | Yes        |
+| setHoldability(int holdability)                              | void                             | Yes        |
+| setNetworkTimeout(Executor executor, int milliseconds)       | void                             | Yes        |
+| setReadOnly(boolean readOnly)                                | void                             | Yes        |
+| setSavepoint()                                               | Savepoint                        | Yes        |
+| setSavepoint(String name)                                    | Savepoint                        | Yes        |
+| setSchema(String schema)                                     | void                             | Yes        |
+| setTransactionIsolation(int level)                           | void                             | Yes        |
+| setTypeMap(Map&lt;String,Class&lt;?&gt;&gt; map)             | void                             | Yes        |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+> 接口内部默认使用自动提交模式，若通过setAutoCommit(false)关闭自动提交，将会导致后面执行的语句都受到显式事务包裹，数据库中不支持事务中执行的语句不能在此模式下执行。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/10-javax-sql-DataSource.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/10-javax-sql-DataSource.md
new file mode 100644
index 0000000000000000000000000000000000000000..f4da542db8a95b9e016965cea8b30981f7a6f28d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/10-javax-sql-DataSource.md
@@ -0,0 +1,21 @@
+---
+title: javax.sql.DataSource
+summary: javax.sql.DataSource
+author: Guo Huan
+date: 2021-05-17
+---
+
+# javax.sql.DataSource
+
+javax.sql.DataSource是数据源接口。
+
+**表 1** 对javax.sql.DataSource接口的支持情况
+
+| 方法名                                         | 返回值类型  | 支持JDBC 4 |
+| :--------------------------------------------- | :---------- | :--------- |
+| getConneciton()                                | Connection  | Yes        |
+| getConnection(String username,String password) | Connection  | Yes        |
+| getLoginTimeout()                              | int         | Yes        |
+| getLogWriter()                                 | PrintWriter | Yes        |
+| setLoginTimeout(int seconds)                   | void        | Yes        |
+| setLogWriter(PrintWriter out)                  | void        | Yes        |
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/11-javax-sql-PooledConnection.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/11-javax-sql-PooledConnection.md
new file mode 100644
index 0000000000000000000000000000000000000000..24e813580c7818d26aea5d658880f15df62d29c5
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/11-javax-sql-PooledConnection.md
@@ -0,0 +1,19 @@
+---
+title: javax.sql.PooledConnection
+summary: javax.sql.PooledConnection
+author: Guo Huan
+date: 2021-05-17
+---
+
+# javax.sql.PooledConnection
+
+javax.sql.PooledConnection是由连接池创建的连接接口。
+
+**表 1** 对javax.sql.PooledConnection的支持情况
+
+| 方法名                                                       | 返回值类型 | 支持JDBC 4 |
+| :----------------------------------------------------------- | :--------- | :--------- |
+| addConnectionEventListener (ConnectionEventListener listener) | void       | Yes        |
+| close()                                                      | void       | Yes        |
+| getConnection()                                              | Connection | Yes        |
+| removeConnectionEventListener (ConnectionEventListener listener) | void       | Yes        |
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/12-javax-naming-Context.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/12-javax-naming-Context.md
new file mode 100644
index 0000000000000000000000000000000000000000..1e5b534ef3b2d121bbccb327ca8160a585aadcff
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/12-javax-naming-Context.md
@@ -0,0 +1,25 @@
+---
+title: javax.naming.Context
+summary: javax.naming.Context
+author: Guo Huan
+date: 2021-05-17
+---
+
+# javax.naming.Context
+
+javax.naming.Context是连接配置的上下文接口。
+
+**表 1** 对javax.naming.Context的支持情况
+
+| 方法名                                 | 返回值类型 | 支持JDBC 4 |
+| :------------------------------------- | :--------- | :--------- |
+| bind(Name name, Object obj)            | void       | Yes        |
+| bind(String name, Object obj)          | void       | Yes        |
+| lookup(Name name)                      | Object     | Yes        |
+| lookup(String name)                    | Object     | Yes        |
+| rebind(Name name, Object obj)          | void       | Yes        |
+| rebind(String name, Object obj)        | void       | Yes        |
+| rename(Name oldName, Name newName)     | void       | Yes        |
+| rename(String oldName, String newName) | void       | Yes        |
+| unbind(Name name)                      | void       | Yes        |
+| unbind(String name)                    | void       | Yes        |
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/13-javax-naming-spi-InitialContextFactory.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/13-javax-naming-spi-InitialContextFactory.md
new file mode 100644
index 0000000000000000000000000000000000000000..8db2b4c881c683922a17cbe5994cb1ac6823317e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/13-javax-naming-spi-InitialContextFactory.md
@@ -0,0 +1,16 @@
+---
+title: javax.naming.spi.InitialContextFactory
+summary: javax.naming.spi.InitialContextFactory
+author: Guo Huan
+date: 2021-05-17
+---
+
+# javax.naming.spi.InitialContextFactory
+
+javax.naming.spi.InitialContextFactory是初始连接上下文工厂接口。
+
+**表 1** 对javax.naming.spi.InitialContextFactory的支持情况
+
+| 方法名                                              | 返回值类型 | 支持JDBC 4 |
+| :-------------------------------------------------- | :--------- | :--------- |
+| getInitialContext(Hashtable&lt;?,?&gt; environment) | Context    | Yes        |
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/14-CopyManager.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/14-CopyManager.md
new file mode 100644
index 0000000000000000000000000000000000000000..37f3a68fae608149e8e695e1594f3ee8cd6b8493
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/14-CopyManager.md
@@ -0,0 +1,47 @@
+---
+title: CopyManager
+summary: CopyManager
+author: Guo Huan
+date: 2021-05-17
+---
+
+# CopyManager
+
+CopyManager是MogDB JDBC驱动中提供的一个API接口类，用于批量向MogDB中导入数据。
+
+<br/>
+
+## CopyManager的继承关系
+
+CopyManager类位于org.postgresql.copy Package中，继承自java.lang.Object类，该类的声明如下：
+
+```java
+public class CopyManager
+extends Object
+```
+
+<br/>
+
+## 构造方法
+
+```java
+public CopyManager(BaseConnection connection)
+throws SQLException
+```
+
+<br/>
+
+## 常用方法
+
+**表 1** CopyManager常用方法
+
+| 返回值                    | 方法                       | 描述                         | throws                   |
+| :----------------------- | :---------------- | :-------------- | :------------- |
+| CopyIn  | copyIn(String sql)                                   | -                                                            | SQLException             |
+| long    | copyIn(String sql, InputStream from)                 | 使用COPY FROM STDIN从InputStream中快速向数据库中的表加载数据。 | SQLException,IOException |
+| long    | copyIn(String sql, InputStream from, int bufferSize) | 使用COPY FROM STDIN从InputStream中快速向数据库中的表加载数据。 | SQLException,IOException |
+| long    | copyIn(String sql, Reader from)                      | 使用COPY FROM STDIN从Reader中快速向数据库中的表加载数据。    | SQLException,IOException |
+| long    | copyIn(String sql, Reader from, int bufferSize)      | 使用COPY FROM STDIN从Reader中快速向数据库中的表加载数据。    | SQLException,IOException |
+| CopyOut | copyOut(String sql)                                  | -                                                            | SQLException             |
+| long    | copyOut(String sql, OutputStream to)                 | 将一个COPY TO STDOUT的结果集从数据库发送到OutputStream类中。 | SQLException,IOException |
+| long    | copyOut(String sql, Writer to)                       | 将一个COPY TO STDOUT的结果集从数据库发送到Writer类中。       | SQLException,IOException |
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/2-java-sql-CallableStatement.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/2-java-sql-CallableStatement.md
new file mode 100644
index 0000000000000000000000000000000000000000..dbb92d0e69006522b40ebf1d00c9eae4249aa040
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/2-java-sql-CallableStatement.md
@@ -0,0 +1,46 @@
+---
+title: java.sql.CallableStatement
+summary: java.sql.CallableStatement
+author: Guo Huan
+date: 2021-05-17
+---
+
+# java.sql.CallableStatement
+
+java.sql.CallableStatement是存储过程执行接口。
+
+**表 1** 对java.sql.CallableStatement的支持情况
+
+| 方法名                                             | 返回值类型 | 支持JDBC 4 |
+| :------------------------------------------------- | :--------- | :--------- |
+| getArray(int parameterIndex)                       | Array      | Yes        |
+| getBigDecimal(int parameterIndex)                  | BigDecimal | Yes        |
+| getBlob(int parameterIndex)                        | Blob       | Yes        |
+| getBoolean(int parameterIndex)                     | boolean    | Yes        |
+| getByte(int parameterIndex)                        | byte       | Yes        |
+| getBytes(int parameterIndex)                       | byte[]     | Yes        |
+| getClob(int parameterIndex)                        | Clob       | Yes        |
+| getDate(int parameterIndex)                        | Date       | Yes        |
+| getDate(int parameterIndex, Calendar cal)          | Date       | Yes        |
+| getDouble(int parameterIndex)                      | double     | Yes        |
+| getFloat(int parameterIndex)                       | float      | Yes        |
+| getInt(int parameterIndex)                         | int        | Yes        |
+| getLong(int parameterIndex)                        | long       | Yes        |
+| getObject(int parameterIndex)                      | Object     | Yes        |
+| getObject(int parameterIndex, Class&lt;T&gt; type) | Object     | Yes        |
+| getShort(int parameterIndex)                       | short      | Yes        |
+| getSQLXML(int parameterIndex)                      | SQLXML     | Yes        |
+| getString(int parameterIndex)                      | String     | Yes        |
+| getNString(int parameterIndex)                     | String     | Yes        |
+| getTime(int parameterIndex)                        | Time       | Yes        |
+| getTime(int parameterIndex, Calendar cal)          | Time       | Yes        |
+| getTimestamp(int parameterIndex)                   | Timestamp  | Yes        |
+| getTimestamp(int parameterIndex, Calendar cal)     | Timestamp  | Yes        |
+| registerOutParameter(int parameterIndex, int type) | void       | Yes        |
+| wasNull()                                          | Boolean    | Yes        |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 不允许含有OUT参数的语句执行批量操作。
+> - 以下方法是从java.sql.Statement继承而来：close，execute，executeQuery，executeUpdate，getConnection，getResultSet，getUpdateCount，isClosed，setMaxRows , setFetchSize。
+> - 以下方法是从java.sql.PreparedStatement继承而来：addBatch，clearParameters，execute，executeQuery，executeUpdate，getMetaData，setBigDecimal，setBoolean，setByte，setBytes，setDate，setDouble，setFloat，setInt，setLong，setNull，setObject，setString，setTime，setTimestamp 。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/3-java-sql-DatabaseMetaData.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/3-java-sql-DatabaseMetaData.md
new file mode 100644
index 0000000000000000000000000000000000000000..c223704c8e5128c4dad6afac2310dcff59370a20
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/3-java-sql-DatabaseMetaData.md
@@ -0,0 +1,189 @@
+---
+title: java.sql.DatabaseMetaData
+summary: java.sql.DatabaseMetaData
+author: Guo Huan
+date: 2021-05-17
+---
+
+# java.sql.DatabaseMetaData
+
+java.sql.DatabaseMetaData是数据库对象定义接口。
+
+**表 1** 对java.sql.DatabaseMetaData的支持情况
+
+| 方法名                                                       | 返回值类型   | 支持JDBC 4 |
+| :----------------------------------------------------------- | :----------- | :--------- |
+| allProceduresAreCallable()                                   | boolean      | Yes        |
+| allTablesAreSelectable()                                     | boolean      | Yes        |
+| autoCommitFailureClosesAllResultSets()                       | boolean      | Yes        |
+| dataDefinitionCausesTransactionCommit()                      | boolean      | Yes        |
+| dataDefinitionIgnoredInTransactions()                        | boolean      | Yes        |
+| deletesAreDetected(int type)                                 | boolean      | Yes        |
+| doesMaxRowSizeIncludeBlobs()                                 | boolean      | Yes        |
+| generatedKeyAlwaysReturned()                                 | boolean      | Yes        |
+| getBestRowIdentifier(String catalog, String schema, String table, int scope, boolean nullable) | ResultSet    | Yes        |
+| getCatalogs()                                                | ResultSet    | Yes        |
+| getCatalogSeparator()                                        | String       | Yes        |
+| getCatalogTerm()                                             | String       | Yes        |
+| getClientInfoProperties()                                    | ResultSet    | Yes        |
+| getColumnPrivileges(String catalog, String schema, String table, String columnNamePattern) | ResultSet    | Yes        |
+| getConnection()                                              | Connection   | Yes        |
+| getCrossReference(String parentCatalog, String parentSchema, String parentTable, String foreignCatalog, String foreignSchema, String foreignTable) | ResultSet    | Yes        |
+| getDefaultTransactionIsolation()                             | int          | Yes        |
+| getExportedKeys(String catalog, String schema, String table) | ResultSet    | Yes        |
+| getExtraNameCharacters()                                     | String       | Yes        |
+| getFunctionColumns(String catalog, String schemaPattern, String functionNamePattern, String columnNamePattern) | ResultSet    | Yes        |
+| getFunctions(String catalog, String schemaPattern, String functionNamePattern) | ResultSet    | Yes        |
+| getIdentifierQuoteString()                                   | String       | Yes        |
+| getImportedKeys(String catalog, String schema, String table) | ResultSet    | Yes        |
+| getIndexInfo(String catalog, String schema, String table, boolean unique, boolean approximate) | ResultSet    | Yes        |
+| getMaxBinaryLiteralLength()                                  | int          | Yes        |
+| getMaxCatalogNameLength()                                    | int          | Yes        |
+| getMaxCharLiteralLength()                                    | int          | Yes        |
+| getMaxColumnNameLength()                                     | int          | Yes        |
+| getMaxColumnsInGroupBy()                                     | int          | Yes        |
+| getMaxColumnsInIndex()                                       | int          | Yes        |
+| getMaxColumnsInOrderBy()                                     | int          | Yes        |
+| getMaxColumnsInSelect()                                      | int          | Yes        |
+| getMaxColumnsInTable()                                       | int          | Yes        |
+| getMaxConnections()                                          | int          | Yes        |
+| getMaxCursorNameLength()                                     | int          | Yes        |
+| getMaxIndexLength()                                          | int          | Yes        |
+| getMaxLogicalLobSize()                                       | default long | Yes        |
+| getMaxProcedureNameLength()                                  | int          | Yes        |
+| getMaxRowSize()                                              | int          | Yes        |
+| getMaxSchemaNameLength()                                     | int          | Yes        |
+| getMaxStatementLength()                                      | int          | Yes        |
+| getMaxStatements()                                           | int          | Yes        |
+| getMaxTableNameLength()                                      | int          | Yes        |
+| getMaxTablesInSelect()                                       | int          | Yes        |
+| getMaxUserNameLength()                                       | int          | Yes        |
+| getNumericFunctions()                                        | String       | Yes        |
+| getPrimaryKeys(String catalog, String schema, String table)  | ResultSet    | Yes        |
+| getProcedureColumns(String catalog, String schemaPattern, String procedureNamePattern, String columnNamePattern) | ResultSet    | Yes        |
+| getProcedures(String catalog, String schemaPattern, String procedureNamePattern) | ResultSet    | Yes        |
+| getProcedureTerm()                                           | String       | Yes        |
+| getSchemas()                                                 | ResultSet    | Yes        |
+| getSchemas(String catalog, String schemaPattern)             | ResultSet    | Yes        |
+| getSchemaTerm()                                              | String       | Yes        |
+| getSearchStringEscape()                                      | String       | Yes        |
+| getSQLKeywords()                                             | String       | Yes        |
+| getSQLStateType()                                            | int          | Yes        |
+| getStringFunctions()                                         | String       | Yes        |
+| getSystemFunctions()                                         | String       | Yes        |
+| getTablePrivileges(String catalog, String schemaPattern, String tableNamePattern) | ResultSet    | Yes        |
+| getTimeDateFunctions()                                       | String       | Yes        |
+| getTypeInfo()                                                | ResultSet    | Yes        |
+| getUDTs(String catalog, String schemaPattern, String typeNamePattern, int[] types) | ResultSet    | Yes        |
+| getURL()                                                     | String       | Yes        |
+| getVersionColumns(String catalog, String schema, String table) | ResultSet    | Yes        |
+| insertsAreDetected(int type)                                 | boolean      | Yes        |
+| locatorsUpdateCopy()                                         | boolean      | Yes        |
+| othersDeletesAreVisible(int type)                            | boolean      | Yes        |
+| othersInsertsAreVisible(int type)                            | boolean      | Yes        |
+| othersUpdatesAreVisible(int type)                            | boolean      | Yes        |
+| ownDeletesAreVisible(int type)                               | boolean      | Yes        |
+| ownInsertsAreVisible(int type)                               | boolean      | Yes        |
+| ownUpdatesAreVisible(int type)                               | boolean      | Yes        |
+| storesLowerCaseIdentifiers()                                 | boolean      | Yes        |
+| storesMixedCaseIdentifiers()                                 | boolean      | Yes        |
+| storesUpperCaseIdentifiers()                                 | boolean      | Yes        |
+| supportsBatchUpdates()                                       | boolean      | Yes        |
+| supportsCatalogsInDataManipulation()                         | boolean      | Yes        |
+| supportsCatalogsInIndexDefinitions()                         | boolean      | Yes        |
+| supportsCatalogsInPrivilegeDefinitions()                     | boolean      | Yes        |
+| supportsCatalogsInProcedureCalls()                           | boolean      | Yes        |
+| supportsCatalogsInTableDefinitions()                         | boolean      | Yes        |
+| supportsCorrelatedSubqueries()                               | boolean      | Yes        |
+| supportsDataDefinitionAndDataManipulationTransactions()      | boolean      | Yes        |
+| supportsDataManipulationTransactionsOnly()                   | boolean      | Yes        |
+| supportsGetGeneratedKeys()                                   | boolean      | Yes        |
+| supportsMixedCaseIdentifiers()                               | boolean      | Yes        |
+| supportsMultipleOpenResults()                                | boolean      | Yes        |
+| supportsNamedParameters()                                    | boolean      | Yes        |
+| supportsOpenCursorsAcrossCommit()                            | boolean      | Yes        |
+| supportsOpenCursorsAcrossRollback()                          | boolean      | Yes        |
+| supportsOpenStatementsAcrossCommit()                         | boolean      | Yes        |
+| supportsOpenStatementsAcrossRollback()                       | boolean      | Yes        |
+| supportsPositionedDelete()                                   | boolean      | Yes        |
+| supportsPositionedUpdate()                                   | boolean      | Yes        |
+| supportsRefCursors()                                         | boolean      | Yes        |
+| supportsResultSetConcurrency(int type, int concurrency)      | boolean      | Yes        |
+| supportsResultSetType(int type)                              | boolean      | Yes        |
+| supportsSchemasInIndexDefinitions()                          | boolean      | Yes        |
+| supportsSchemasInPrivilegeDefinitions()                      | boolean      | Yes        |
+| supportsSchemasInProcedureCalls()                            | boolean      | Yes        |
+| supportsSchemasInTableDefinitions()                          | boolean      | Yes        |
+| supportsSelectForUpdate()                                    | boolean      | Yes        |
+| supportsStatementPooling()                                   | boolean      | Yes        |
+| supportsStoredFunctionsUsingCallSyntax()                     | boolean      | Yes        |
+| supportsStoredProcedures()                                   | boolean      | Yes        |
+| supportsSubqueriesInComparisons()                            | boolean      | Yes        |
+| supportsSubqueriesInExists()                                 | boolean      | Yes        |
+| supportsSubqueriesInIns()                                    | boolean      | Yes        |
+| supportsSubqueriesInQuantifieds()                            | boolean      | Yes        |
+| supportsTransactionIsolationLevel(int level)                 | boolean      | Yes        |
+| supportsTransactions()                                       | boolean      | Yes        |
+| supportsUnion()                                              | boolean      | Yes        |
+| supportsUnionAll()                                           | boolean      | Yes        |
+| updatesAreDetected(int type)                                 | boolean      | Yes        |
+| getTables(String catalog, String schemaPattern, String tableNamePattern, String[] types) | ResultSet    | Yes        |
+| getColumns(String catalog, String schemaPattern, String tableNamePattern, String columnNamePattern) | ResultSet    | Yes        |
+| getTableTypes()                                              | ResultSet    | Yes        |
+| getUserName()                                                | String       | Yes        |
+| isReadOnly()                                                 | boolean      | Yes        |
+| nullsAreSortedHigh()                                         | boolean      | Yes        |
+| nullsAreSortedLow()                                          | boolean      | Yes        |
+| nullsAreSortedAtStart()                                      | boolean      | Yes        |
+| nullsAreSortedAtEnd()                                        | boolean      | Yes        |
+| getDatabaseProductName()                                     | String       | Yes        |
+| getDatabaseProductVersion()                                  | String       | Yes        |
+| getDriverName()                                              | String       | Yes        |
+| getDriverVersion()                                           | String       | Yes        |
+| getDriverMajorVersion()                                      | int          | Yes        |
+| getDriverMinorVersion()                                      | int          | Yes        |
+| usesLocalFiles()                                             | boolean      | Yes        |
+| usesLocalFilePerTable()                                      | boolean      | Yes        |
+| supportsMixedCaseIdentifiers()                               | boolean      | Yes        |
+| storesUpperCaseIdentifiers()                                 | boolean      | Yes        |
+| storesLowerCaseIdentifiers()                                 | boolean      | Yes        |
+| supportsMixedCaseQuotedIdentifiers()                         | boolean      | Yes        |
+| storesUpperCaseQuotedIdentifiers()                           | boolean      | Yes        |
+| storesLowerCaseQuotedIdentifiers()                           | boolean      | Yes        |
+| storesMixedCaseQuotedIdentifiers()                           | boolean      | Yes        |
+| supportsAlterTableWithAddColumn()                            | boolean      | Yes        |
+| supportsAlterTableWithDropColumn()                           | boolean      | Yes        |
+| supportsColumnAliasing()                                     | boolean      | Yes        |
+| nullPlusNonNullIsNull()                                      | boolean      | Yes        |
+| supportsConvert()                                            | boolean      | Yes        |
+| supportsConvert(int fromType, int toType)                    | boolean      | Yes        |
+| supportsTableCorrelationNames()                              | boolean      | Yes        |
+| supportsDifferentTableCorrelationNames()                     | boolean      | Yes        |
+| supportsExpressionsInOrderBy()                               | boolean      | Yes        |
+| supportsOrderByUnrelated()                                   | boolean      | Yes        |
+| supportsGroupBy()                                            | boolean      | Yes        |
+| supportsGroupByUnrelated()                                   | boolean      | Yes        |
+| supportsGroupByBeyondSelect()                                | boolean      | Yes        |
+| supportsLikeEscapeClause()                                   | boolean      | Yes        |
+| supportsMultipleResultSets()                                 | boolean      | Yes        |
+| supportsMultipleTransactions()                               | boolean      | Yes        |
+| supportsNonNullableColumns()                                 | boolean      | Yes        |
+| supportsMinimumSQLGrammar()                                  | boolean      | Yes        |
+| supportsCoreSQLGrammar()                                     | boolean      | Yes        |
+| supportsExtendedSQLGrammar()                                 | boolean      | Yes        |
+| supportsANSI92EntryLevelSQL()                                | boolean      | Yes        |
+| supportsANSI92IntermediateSQL()                              | boolean      | Yes        |
+| supportsANSI92FullSQL()                                      | boolean      | Yes        |
+| supportsIntegrityEnhancementFacility()                       | boolean      | Yes        |
+| supportsOuterJoins()                                         | boolean      | Yes        |
+| supportsFullOuterJoins()                                     | boolean      | Yes        |
+| supportsLimitedOuterJoins()                                  | boolean      | Yes        |
+| isCatalogAtStart()                                           | boolean      | Yes        |
+| supportsSchemasInDataManipulation()                          | boolean      | Yes        |
+| supportsSavepoints()                                         | boolean      | Yes        |
+| supportsResultSetHoldability(int holdability)                | boolean      | Yes        |
+| getResultSetHoldability()                                    | int          | Yes        |
+| getDatabaseMajorVersion()                                    | int          | Yes        |
+| getDatabaseMinorVersion()                                    | int          | Yes        |
+| getJDBCMajorVersion()                                        | int          | Yes        |
+| getJDBCMinorVersion()                                        | int          | Yes        |
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/4-java-sql-Driver.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/4-java-sql-Driver.md
new file mode 100644
index 0000000000000000000000000000000000000000..1c6f1b7b0942b77ce91471ec4ee0e7e8f16554f1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/4-java-sql-Driver.md
@@ -0,0 +1,22 @@
+---
+title: java.sql.Driver
+summary: java.sql.Driver
+author: Guo Huan
+date: 2021-05-17
+---
+
+# java.sql.Driver
+
+java.sql.Driver是数据库驱动接口。
+
+**表 1** 对java.sql.Driver的支持情况
+
+| 方法名                                       | 返回值类型           | 支持JDBC 4 |
+| :------------------------------------------- | :------------------- | :--------- |
+| acceptsURL(String url)                       | Boolean              | Yes        |
+| connect(String url, Properties info)         | Connection           | Yes        |
+| jdbcCompliant()                              | Boolean              | Yes        |
+| getMajorVersion()                            | int                  | Yes        |
+| getMinorVersion()                            | int                  | Yes        |
+| getParentLogger()                            | Logger               | Yes        |
+| getPropertyInfo(String url, Properties info) | DriverPropertyInfo[] | Yes        |
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/5-java-sql-PreparedStatement.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/5-java-sql-PreparedStatement.md
new file mode 100644
index 0000000000000000000000000000000000000000..19a170d4cdfc639022c72f90fc64c4d33a9e4edf
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/5-java-sql-PreparedStatement.md
@@ -0,0 +1,70 @@
+---
+title: java.sql.PreparedStatement
+summary: java.sql.PreparedStatement
+author: Guo Huan
+date: 2021-05-17
+---
+
+# java.sql.PreparedStatement
+
+java.sql.PreparedStatement是预处理语句接口。
+
+**表 1** 对java.sql.PreparedStatement的支持情况
+
+| 方法名                                                       | 返回值类型        | 支持JDBC 4 |
+| :----------------------------------------------------------- | :---------------- | :--------- |
+| clearParameters()                                            | void              | Yes        |
+| execute()                                                    | Boolean           | Yes        |
+| executeQuery()                                               | ResultSet         | Yes        |
+| excuteUpdate()                                               | int               | Yes        |
+| executeLargeUpdate()                                         | long              | No         |
+| getMetaData()                                                | ResultSetMetaData | Yes        |
+| getParameterMetaData()                                       | ParameterMetaData | Yes        |
+| setArray(int parameterIndex, Array x)                        | void              | Yes        |
+| setAsciiStream(int parameterIndex, InputStream x, int length) | void              | Yes        |
+| setBinaryStream(int parameterIndex, InputStream x)           | void              | Yes        |
+| setBinaryStream(int parameterIndex, InputStream x, int length) | void              | Yes        |
+| setBinaryStream(int parameterIndex, InputStream x, long length) | void              | Yes        |
+| setBlob(int parameterIndex, InputStream inputStream)         | void              | Yes        |
+| setBlob(int parameterIndex, InputStream inputStream, long length) | void              | Yes        |
+| setBlob(int parameterIndex, Blob x)                          | void              | Yes        |
+| setCharacterStream(int parameterIndex, Reader reader)        | void              | Yes        |
+| setCharacterStream(int parameterIndex, Reader reader, int length) | void              | Yes        |
+| setClob(int parameterIndex, Reader reader)                   | void              | Yes        |
+| setClob(int parameterIndex, Reader reader, long length)      | void              | Yes        |
+| setClob(int parameterIndex, Clob x)                          | void              | Yes        |
+| setDate(int parameterIndex, Date x, Calendar cal)            | void              | Yes        |
+| setNull(int parameterIndex, int sqlType)                     | void              | Yes        |
+| setNull(int parameterIndex, int sqlType, String typeName)    | void              | Yes        |
+| setObject(int parameterIndex, Object x)                      | void              | Yes        |
+| setObject(int parameterIndex, Object x, int targetSqlType)   | void              | Yes        |
+| setObject(int parameterIndex, Object x, int targetSqlType, int scaleOrLength) | void              | Yes        |
+| setSQLXML(int parameterIndex, SQLXML xmlObject)              | void              | Yes        |
+| setTime(int parameterIndex, Time x)                          | void              | Yes        |
+| setTime(int parameterIndex, Time x, Calendar cal)            | void              | Yes        |
+| setTimestamp(int parameterIndex, Timestamp x)                | void              | Yes        |
+| setTimestamp(int parameterIndex, Timestamp x, Calendar cal)  | void              | Yes        |
+| setUnicodeStream(int parameterIndex, InputStream x, int length) | void              | Yes        |
+| setURL(int parameterIndex, URL x)                            | void              | Yes        |
+| setBoolean(int parameterIndex, boolean x)                    | void              | Yes        |
+| setBigDecimal(int parameterIndex, BigDecimal x)              | void              | Yes        |
+| setByte(int parameterIndex, byte x)                          | void              | Yes        |
+| setBytes(int parameterIndex, byte[] x)                       | void              | Yes        |
+| setDate(int parameterIndex, Date x)                          | void              | Yes        |
+| setDouble(int parameterIndex, double x)                      | void              | Yes        |
+| setFloat(int parameterIndex, float x)                        | void              | Yes        |
+| setInt(int parameterIndex, int x)                            | void              | Yes        |
+| setLong(int parameterIndex, long x)                          | void              | Yes        |
+| setShort(int parameterIndex, short x)                        | void              | Yes        |
+| setString(int parameterIndex, String x)                      | void              | Yes        |
+| setNString(int parameterIndex, String x)                     | void              | Yes        |
+| addBatch()                                                   | void              | Yes        |
+| executeBatch()                                               | int[]             | Yes        |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - addBatch()、execute()必须在clearBatch()之后才能执行。
+> - 调用executeBatch()方法并不会清除batch。用户必须显式使用clearBatch()清除 。
+> - 在添加了一个batch的绑定变量后，用户若想重用这些值(再次添加一个batch)，无需再次使用set*()方法 。
+> - 以下方法是从java.sql.Statement继承而来：close，execute，executeQuery，executeUpdate，getConnection，getResultSet，getUpdateCount，isClosed，setMaxRows, setFetchSize。
+> - executeLargeUpdate()方法必须在JDBC4.2及以上使用。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/6-java-sql-ResultSet.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/6-java-sql-ResultSet.md
new file mode 100644
index 0000000000000000000000000000000000000000..1daf58a35b3a0238a97f76faa8067ed3e949f38a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/6-java-sql-ResultSet.md
@@ -0,0 +1,154 @@
+---
+title: java.sql.ResultSet
+summary: java.sql.ResultSet
+author: Guo Huan
+date: 2021-05-17
+---
+
+# java.sql.ResultSet
+
+java.sql.ResultSet是执行结果集接口。
+
+**表 1** 对java.sql.ResultSet的支持情况
+
+| 方法名                                                       | 返回值类型        | 支持JDBC 4 |
+| :----------------------------------------------------------- | :---------------- | :--------- |
+| absolute(int row)                                            | Boolean           | Yes        |
+| afterLast()                                                  | void              | Yes        |
+| beforeFirst()                                                | void              | Yes        |
+| cancelRowUpdates()                                           | void              | Yes        |
+| clearWarnings()                                              | void              | Yes        |
+| close()                                                      | void              | Yes        |
+| deleteRow()                                                  | void              | Yes        |
+| findColumn(String columnLabel)                               | int               | Yes        |
+| first()                                                      | Boolean           | Yes        |
+| getArray(int columnIndex)                                    | Array             | Yes        |
+| getArray(String columnLabel)                                 | Array             | Yes        |
+| getAsciiStream(int columnIndex)                              | InputStream       | Yes        |
+| getAsciiStream(String columnLabel)                           | InputStream       | Yes        |
+| getBigDecimal(int columnIndex)                               | BigDecimal        | Yes        |
+| getBigDecimal(String columnLabel)                            | BigDecimal        | Yes        |
+| getBinaryStream(int columnIndex)                             | InputStream       | Yes        |
+| getBinaryStream(String columnLabel)                          | InputStream       | Yes        |
+| getBlob(int columnIndex)                                     | Blob              | Yes        |
+| getBlob(String columnLabel)                                  | Blob              | Yes        |
+| getBoolean(int columnIndex)                                  | Boolean           | Yes        |
+| getBoolean(String columnLabel)                               | Boolean           | Yes        |
+| getByte(int columnIndex)                                     | byte              | Yes        |
+| getBytes(int columnIndex)                                    | byte[]            | Yes        |
+| getByte(String columnLabel)                                  | byte              | Yes        |
+| getBytes(String columnLabel)                                 | byte[]            | Yes        |
+| getCharacterStream(int columnIndex)                          | Reader            | Yes        |
+| getCharacterStream(String columnLabel)                       | Reader            | Yes        |
+| getClob(int columnIndex)                                     | Clob              | Yes        |
+| getClob(String columnLabel)                                  | Clob              | Yes        |
+| getConcurrency()                                             | int               | Yes        |
+| getCursorName()                                              | String            | Yes        |
+| getDate(int columnIndex)                                     | Date              | Yes        |
+| getDate(int columnIndex, Calendar cal)                       | Date              | Yes        |
+| getDate(String columnLabel)                                  | Date              | Yes        |
+| getDate(String columnLabel, Calendar cal)                    | Date              | Yes        |
+| getDouble(int columnIndex)                                   | double            | Yes        |
+| getDouble(String columnLabel)                                | double            | Yes        |
+| getFetchDirection()                                          | int               | Yes        |
+| getFetchSize()                                               | int               | Yes        |
+| getFloat(int columnIndex)                                    | float             | Yes        |
+| getFloat(String columnLabel)                                 | float             | Yes        |
+| getInt(int columnIndex)                                      | int               | Yes        |
+| getInt(String columnLabel)                                   | int               | Yes        |
+| getLong(int columnIndex)                                     | long              | Yes        |
+| getLong(String columnLabel)                                  | long              | Yes        |
+| getMetaData()                                                | ResultSetMetaData | Yes        |
+| getObject(int columnIndex)                                   | Object            | Yes        |
+| getObject(int columnIndex, Class&lt;T&gt; type)              | &lt;T&gt; T       | Yes        |
+| getObject(int columnIndex, Map&lt;String,Class&lt;?&gt;&gt; map) | Object            | Yes        |
+| getObject(String columnLabel)                                | Object            | Yes        |
+| getObject(String columnLabel, Class&lt;T&gt; type)           | &lt;T&gt; T       | Yes        |
+| getObject(String columnLabel, Map&lt;String,Class&lt;?&gt;&gt; map) | Object            | Yes        |
+| getRow()                                                     | int               | Yes        |
+| getShort(int columnIndex)                                    | short             | Yes        |
+| getShort(String columnLabel)                                 | short             | Yes        |
+| getSQLXML(int columnIndex)                                   | SQLXML            | Yes        |
+| getSQLXML(String columnLabel)                                | SQLXML            | Yes        |
+| getStatement()                                               | Statement         | Yes        |
+| getString(int columnIndex)                                   | String            | Yes        |
+| getString(String columnLabel)                                | String            | Yes        |
+| getNString(int columnIndex)                                  | String            | Yes        |
+| getNString(String columnLabel)                               | String            | Yes        |
+| getTime(int columnIndex)                                     | Time              | Yes        |
+| getTime(int columnIndex, Calendar cal)                       | Time              | Yes        |
+| getTime(String columnLabel)                                  | Time              | Yes        |
+| getTime(String columnLabel, Calendar cal)                    | Time              | Yes        |
+| getTimestamp(int columnIndex)                                | Timestamp         | Yes        |
+| getTimestamp(int columnIndex, Calendar cal)                  | Timestamp         | Yes        |
+| getTimestamp(String columnLabel)                             | Timestamp         | Yes        |
+| getTimestamp(String columnLabel, Calendar cal)               | Timestamp         | Yes        |
+| getType()                                                    | int               | Yes        |
+| getWarnings()                                                | SQLWarning        | Yes        |
+| insertRow()                                                  | void              | Yes        |
+| isAfterLast()                                                | Boolean           | Yes        |
+| isBeforeFirst()                                              | Boolean           | Yes        |
+| isClosed()                                                   | Boolean           | Yes        |
+| isFirst()                                                    | Boolean           | Yes        |
+| isLast()                                                     | Boolean           | Yes        |
+| last()                                                       | Boolean           | Yes        |
+| moveToCurrentRow()                                           | void              | Yes        |
+| moveToInsertRow()                                            | void              | Yes        |
+| next()                                                       | Boolean           | Yes        |
+| previous()                                                   | Boolean           | Yes        |
+| refreshRow()                                                 | void              | Yes        |
+| relative(int rows)                                           | Boolean           | Yes        |
+| rowDeleted()                                                 | Boolean           | Yes        |
+| rowInserted()                                                | Boolean           | Yes        |
+| rowUpdated()                                                 | Boolean           | Yes        |
+| setFetchDirection(int direction)                             | void              | Yes        |
+| setFetchSize(int rows)                                       | void              | Yes        |
+| updateArray(int columnIndex, Array x)                        | void              | Yes        |
+| updateArray(String columnLabel, Array x)                     | void              | Yes        |
+| updateAsciiStream(int columnIndex, InputStream x, int length) | void              | Yes        |
+| updateAsciiStream(String columnLabel, InputStream x, int length) | void              | Yes        |
+| updateBigDecimal(int columnIndex, BigDecimal x)              | void              | Yes        |
+| updateBigDecimal(String columnLabel, BigDecimal x)           | void              | Yes        |
+| updateBinaryStream(int columnIndex, InputStream x, int length) | void              | Yes        |
+| updateBinaryStream(String columnLabel, InputStream x, int length) | void              | Yes        |
+| updateBoolean(int columnIndex, boolean x)                    | void              | Yes        |
+| updateBoolean(String columnLabel, boolean x)                 | void              | Yes        |
+| updateByte(int columnIndex, byte x)                          | void              | Yes        |
+| updateByte(String columnLabel, byte x)                       | void              | Yes        |
+| updateBytes(int columnIndex, byte[] x)                       | void              | Yes        |
+| updateBytes(String columnLabel, byte[] x)                    | void              | Yes        |
+| updateCharacterStream(int columnIndex, Reader x, int length) | void              | Yes        |
+| updateCharacterStream(String columnLabel, Reader reader, int length) | void              | Yes        |
+| updateDate(int columnIndex, Date x)                          | void              | Yes        |
+| updateDate(String columnLabel, Date x)                       | void              | Yes        |
+| updateDouble(int columnIndex, double x)                      | void              | Yes        |
+| updateDouble(String columnLabel, double x)                   | void              | Yes        |
+| updateFloat(int columnIndex, float x)                        | void              | Yes        |
+| updateFloat(String columnLabel, float x)                     | void              | Yes        |
+| updateInt(int columnIndex, int x)                            | void              | Yes        |
+| updateInt(String columnLabel, int x)                         | void              | Yes        |
+| updateLong(int columnIndex, long x)                          | void              | Yes        |
+| updateLong(String columnLabel, long x)                       | void              | Yes        |
+| updateNull(int columnIndex)                                  | void              | Yes        |
+| updateNull(String columnLabel)                               | void              | Yes        |
+| updateObject(int columnIndex, Object x)                      | void              | Yes        |
+| updateObject(int columnIndex, Object x, int scaleOrLength)   | void              | Yes        |
+| updateObject(String columnLabel, Object x)                   | void              | Yes        |
+| updateObject(String columnLabel, Object x, int scaleOrLength) | void              | Yes        |
+| updateRow()                                                  | void              | Yes        |
+| updateShort(int columnIndex, short x)                        | void              | Yes        |
+| updateShort(String columnLabel, short x)                     | void              | Yes        |
+| updateSQLXML(int columnIndex, SQLXML xmlObject)              | void              | Yes        |
+| updateSQLXML(String columnLabel, SQLXML xmlObject)           | void              | Yes        |
+| updateString(int columnIndex, String x)                      | void              | Yes        |
+| updateString(String columnLabel, String x)                   | void              | Yes        |
+| updateTime(int columnIndex, Time x)                          | void              | Yes        |
+| updateTime(String columnLabel, Time x)                       | void              | Yes        |
+| updateTimestamp(int columnIndex, Timestamp x)                | void              | Yes        |
+| updateTimestamp(String columnLabel, Timestamp x)             | void              | Yes        |
+| wasNull()                                                    | Boolean           | Yes        |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 一个Statement不能有多个处于"open"状态的ResultSet。
+> - 用于遍历结果集(ResultSet)的游标(Cursor)在被提交后不能保持“open”的状态。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/7-java-sql-ResultSetMetaData.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/7-java-sql-ResultSetMetaData.md
new file mode 100644
index 0000000000000000000000000000000000000000..897b8d227243ca77c4b281a6ce9a4ba749203f53
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/7-java-sql-ResultSetMetaData.md
@@ -0,0 +1,36 @@
+---
+title: java.sql.ResultSetMetaData
+summary: java.sql.ResultSetMetaData
+author: Guo Huan
+date: 2021-05-17
+---
+
+# java.sql.ResultSetMetaData
+
+java.sql.ResultSetMetaData是对ResultSet对象相关信息的具体描述。
+
+**表 1**  对java.sql.ResultSetMetaData的支持情况
+
+| 方法名                           | 返回值类型 | 支持JDBC 4 |
+| :------------------------------- | :--------- | :--------- |
+| getCatalogName(int column)       | String     | Yes        |
+| getColumnClassName(int column)   | String     | Yes        |
+| getColumnCount()                 | int        | Yes        |
+| getColumnDisplaySize(int column) | int        | Yes        |
+| getColumnLabel(int column)       | String     | Yes        |
+| getColumnName(int column)        | String     | Yes        |
+| getColumnType(int column)        | int        | Yes        |
+| getColumnTypeName(int column)    | String     | Yes        |
+| getPrecision(int column)         | int        | Yes        |
+| getScale(int column)             | int        | Yes        |
+| getSchemaName(int column)        | String     | Yes        |
+| getTableName(int column)         | String     | Yes        |
+| isAutoIncrement(int column)      | boolean    | Yes        |
+| isCaseSensitive(int column)      | boolean    | Yes        |
+| isCurrency(int column)           | boolean    | Yes        |
+| isDefinitelyWritable(int column) | boolean    | Yes        |
+| isNullable(int column)           | int        | Yes        |
+| isReadOnly(int column)           | boolean    | Yes        |
+| isSearchable(int column)         | boolean    | Yes        |
+| isSigned(int column)             | boolean    | Yes        |
+| isWritable(int column)           | boolean    | Yes        |
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/8-java-sql-Statement.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/8-java-sql-Statement.md
new file mode 100644
index 0000000000000000000000000000000000000000..1b50c6149dd54522bdacb83a878f217f859d0850
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/8-java-sql-Statement.md
@@ -0,0 +1,69 @@
+---
+title: java.sql.Statement
+summary: java.sql.Statement
+author: Guo Huan
+date: 2021-05-17
+---
+
+# java.sql.Statement
+
+java.sql.Statement是SQL语句接口。
+
+**表 1** 对java.sql.Statement的支持情况
+
+| 方法名                                                | 返回值类型 | 支持JDBC 4 |
+| :---------------------------------------------------- | :--------- | :--------- |
+| addBatch(String sql)                                  | void       | Yes        |
+| clearBatch()                                          | void       | Yes        |
+| clearWarnings()                                       | void       | Yes        |
+| close()                                               | void       | Yes        |
+| closeOnCompletion()                                   | void       | Yes        |
+| execute(String sql)                                   | Boolean    | Yes        |
+| execute(String sql, int autoGeneratedKeys)            | Boolean    | Yes        |
+| execute(String sql, int[] columnIndexes)              | Boolean    | Yes        |
+| execute(String sql, String[] columnNames)             | Boolean    | Yes        |
+| executeBatch()                                        | Boolean    | Yes        |
+| executeQuery(String sql)                              | ResultSet  | Yes        |
+| executeUpdate(String sql)                             | int        | Yes        |
+| executeUpdate(String sql, int autoGeneratedKeys)      | int        | Yes        |
+| executeUpdate(String sql, int[] columnIndexes)        | int        | Yes        |
+| executeUpdate(String sql, String[] columnNames)       | int        | Yes        |
+| getConnection()                                       | Connection | Yes        |
+| getFetchDirection()                                   | int        | Yes        |
+| getFetchSize()                                        | int        | Yes        |
+| getGeneratedKeys()                                    | ResultSet  | Yes        |
+| getMaxFieldSize()                                     | int        | Yes        |
+| getMaxRows()                                          | int        | Yes        |
+| getMoreResults()                                      | boolean    | Yes        |
+| getMoreResults(int current)                           | boolean    | Yes        |
+| getResultSet()                                        | ResultSet  | Yes        |
+| getResultSetConcurrency()                             | int        | Yes        |
+| getResultSetHoldability()                             | int        | Yes        |
+| getResultSetType()                                    | int        | Yes        |
+| getQueryTimeout()                                     | int        | Yes        |
+| getUpdateCount()                                      | int        | Yes        |
+| getWarnings()                                         | SQLWarning | Yes        |
+| isClosed()                                            | Boolean    | Yes        |
+| isCloseOnCompletion()                                 | Boolean    | Yes        |
+| isPoolable()                                          | Boolean    | Yes        |
+| setCursorName(String name)                            | void       | Yes        |
+| setEscapeProcessing(boolean enable)                   | void       | Yes        |
+| setFetchDirection(int direction)                      | void       | Yes        |
+| setMaxFieldSize(int max)                              | void       | Yes        |
+| setMaxRows(int max)                                   | void       | Yes        |
+| setPoolable(boolean poolable)                         | void       | Yes        |
+| setQueryTimeout(int seconds)                          | void       | Yes        |
+| setFetchSize(int rows)                                | void       | Yes        |
+| cancel()                                              | void       | Yes        |
+| executeLargeUpdate(String sql)                        | long       | No         |
+| getLargeUpdateCount()                                 | long       | No         |
+| executeLargeBatch()                                   | long       | No         |
+| executeLargeUpdate(String sql, int autoGeneratedKeys) | long       | No         |
+| executeLargeUpdate(String sql, int[] columnIndexes)   | long       | No         |
+| executeLargeUpdate(String sql, String[] columnNames)  | long       | No         |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 通过setFetchSize可以减少结果集在客户端的内存占用情况。它的原理是通过将结果集打包成游标，然后分段处理，所以会加大数据库与客户端的通信量，会有性能损耗。
+> - 由于数据库游标是事务内有效，所以，在设置setFetchSize的同时，需要将连接设置为非自动提交模式，setAutoCommit(false)。同时在业务数据需要持久化到数据库中时，在连接上执行提交操作。
+> - LargeUpdate相关方法必须在JDBC4.2及以上使用。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/9-javax-sql-ConnectionPoolDataSource.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/9-javax-sql-ConnectionPoolDataSource.md
new file mode 100644
index 0000000000000000000000000000000000000000..731c5b7deefd267c05c21e53156471d3d0698a9f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/9-javax-sql-ConnectionPoolDataSource.md
@@ -0,0 +1,17 @@
+---
+title: javax.sql.ConnectionPoolDataSource
+summary: javax.sql.ConnectionPoolDataSource
+author: Guo Huan
+date: 2021-05-17
+---
+
+# javax.sql.ConnectionPoolDataSource
+
+javax.sql.ConnectionPoolDataSource是数据源连接池接口。
+
+**表 1** 对javax.sql.ConnectionPoolDataSource的支持情况
+
+| 方法名                                           | 返回值类型       | 支持JDBC 4 |
+| :----------------------------------------------- | :--------------- | :--------- |
+| getPooledConnection()                            | PooledConnection | Yes        |
+| getPooledConnection(String user,String password) | PooledConnection | Yes        |
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/2-jdbc-package-driver-class-and-environment-class.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/2-jdbc-package-driver-class-and-environment-class.md
new file mode 100644
index 0000000000000000000000000000000000000000..9d8e526442e523d16ebf6c937d8532e42585365f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/2-jdbc-package-driver-class-and-environment-class.md
@@ -0,0 +1,51 @@
+---
+title: JDBC包、驱动类和环境类
+summary: JDBC包、驱动类和环境类
+author: Guo Huan
+date: 2021-04-26
+---
+
+# JDBC包、驱动类和环境类
+
+<br/>
+
+## JDBC包
+
+在linux服务器端源代码目录下执行build.sh，获得驱动jar包postgresql.jar，包位置在源代码目录下。从发布包中获取, 包名为[openGauss-x.x.x-JDBC.tar.gz](https://opengauss.org/zh/download.html)。
+
+驱动包与PostgreSQL保持兼容，其中类名、类结构与PostgreSQL驱动完全一致，曾经运行于PostgreSQL的应用程序可以直接移植到当前系统使用。
+
+<br/>
+
+## 驱动类
+
+在创建数据库连接之前，需要加载数据库驱动类"org.postgresql.Driver"。
+
+> **说明:**
+> 由于MogDB在JDBC的使用上与PG的使用方法保持兼容，所以同时在同一进程内使用两个JDBC驱动的时候，可能会类名冲突。
+
+<br/>
+
+## 环境类
+
+客户端需配置JDK1.8，配置方法如下:
+
+1. DOS窗口输入"java -version"，查看JDK版本，确认为JDK1.8版本。如果未安装JDK，请从官方网站下载安装包并安装。
+
+2. 根据如下步骤配置系统环境变量。
+
+    a. 右键单击"我的电脑"，选择"属性"。
+
+    b. 在"系统"页面左侧导航栏单击"高级系统设置"。
+
+    c. 在"系统属性"页面，"高级"页签上单击"环境变量"。
+
+    d. 在"环境变量"页面上，"系统变量"区域单击"新建"或"编辑"配置系统变量。变量说明请参见表1。
+
+**表 1** 变量说明
+
+| 变量名    | 操作        | 变量值  |
+| :-------- | :--------------- | :-------------------- |
+| JAVA_HOME | - 若存在，则单击"编辑"。<br />- 若不存在，则单击"新建"。 | JAVA的安装目录。<br />例如: C:\\Program Files\\Java\\jdk1.8.0_131                                                                                                                    |
+| Path      | 编辑                                                     | - 若配置了JAVA_HOME，则在变量值的最前面加上:  %JAVA_HOME%\\bin;<br />- 若未配置JAVA_HOME，则在变量值的最前面加上 JAVA安装的全路径: <br />C:\\Program Files\\Java\\jdk1.8.0_131\\bin; |
+| CLASSPATH | 新建                                                     | ".;%JAVA_HOME%\\lib;%JAVA_HOME%\\lib\\tools.jar;"                                                                                                                                    |
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/3-development-process.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/3-development-process.md
new file mode 100644
index 0000000000000000000000000000000000000000..377854610c4a5c7bc2696df5a40c00160784dc22
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/3-development-process.md
@@ -0,0 +1,12 @@
+---
+title: 开发流程
+summary: 开发流程
+author: Guo Huan
+date: 2021-04-26
+---
+
+# 开发流程
+
+**图 1** 采用JDBC开发应用程序的流程
+
+![采用JDBC开发应用程序的流程](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/development-process-1.png)
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/4-loading-the-driver.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/4-loading-the-driver.md
new file mode 100644
index 0000000000000000000000000000000000000000..25ba850ce986523112a1a8b46a4f7cc4824662da
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/4-loading-the-driver.md
@@ -0,0 +1,19 @@
+---
+title: 加载驱动
+summary: 加载驱动
+author: Guo Huan
+date: 2021-04-26
+---
+
+# 加载驱动
+
+在创建数据库连接之前，需要先加载数据库驱动程序。
+
+加载驱动有两种方法:
+
+- 在代码中创建连接之前任意位置隐含装载: Class.forName("org.postgresql.Driver");
+
+- 在JVM启动时参数传递: java -Djdbc.drivers=org.postgresql.Driver jdbctest
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+    > 上述jdbctest为测试用例程序的名称。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/5-connecting-to-a-database.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/5-connecting-to-a-database.md
new file mode 100644
index 0000000000000000000000000000000000000000..9fcab44982601403f299d9cd569f632c5017a43c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/5-connecting-to-a-database.md
@@ -0,0 +1,111 @@
+---
+title: 连接数据库
+summary: 连接数据库
+author: Guo Huan
+date: 2021-04-26
+---
+
+# 连接数据库
+
+在创建数据库连接之后，才能使用它来执行SQL语句操作数据。
+
+<br/>
+
+## 函数原型
+
+JDBC提供了三个方法，用于创建数据库连接。
+
+- DriverManager.getConnection(String url);
+- DriverManager.getConnection(String url, Properties info);
+- DriverManager.getConnection(String url, String user, String password);
+
+<br/>
+
+## 参数
+
+**表 1** 数据库连接参数
+
+| 参数     | 描述        |
+| :------- | :-------------- |
+| url      | postgresql.jar数据库连接描述符。格式如下: <br />- jdbc:postgresql:database<br />- jdbc:postgresql://host/database<br />- jdbc:postgresql://host:port/database<br />- jdbc:postgresql://host:port/database?param1=value1&param2=value2<br />- jdbc:postgresql://host1:port1,host2:port2/database?param1=value1&param2=value2<br />说明:<br />- database为要连接的数据库名称。<br />- host为数据库服务器名称或IP地址。<br />连接MogDB的机器与MogDB不在同一网段时，host指定的IP地址应为Manager界面上所设的coo.cooListenIp2（应用访问IP）的取值。<br />由于安全原因，数据库主节点禁止MogDB内部其他节点无认证接入。如果要在MogDB内部访问数据库主节点，请将JDBC程序部署在数据库主节点所在机器，host使用"127.0.0.1"。否则可能会出现"FATAL: Forbid remote connection with trust method!"错误。<br />建议业务系统单独部署在MogDB外部，否则可能会影响数据库运行性能。<br />缺省情况下，连接服务器为localhost。<br />- port为数据库服务器端口。<br />缺省情况下，会尝试连接到5431端口的database。<br />- param为参数名称，即数据库连接属性。<br />参数可以配置在URL中，以"?"开始配置，以"="给参数赋值，以"&"作为不同参数的间隔。也可以采用info对象的属性方式进行配置，详细示例会在本节给出。<br />- value为参数值，即数据库连接属性值。|
+| info     | 数据库连接属性。常用的属性如下: <br />- PGDBNAME: String类型。表示数据库名称。（URL中无需配置该参数，自动从URL中解析）<br />- PGHOST: String类型。主机IP地址。详细示例见下。<br />- PGPORT: Integer类型。主机端口号。详细示例见下。<br />- user: String类型。表示创建连接的数据库用户。<br />- password: String类型。表示数据库用户的密码。<br />- loggerLevel: String类型。目前支持3种级别: OFF、DEBUG、TRACE。设置为OFF关闭日志，设置为DEBUG和TRACE记录的日志信息详细程度不同。<br />- loggerFile: String类型。Logger输出的文件名。需要显示指定日志文件名，若未指定目录则生成在客户端运行程序目录。<br />- allowEncodingChanges: Boolean类型。设置该参数值为"true"进行字符集类型更改，配合characterEncoding=CHARSET设置字符集，二者使用"&"分隔。<br />- currentSchema: String类型。在search-path中指定要设置的schema。<br />- hostRecheckSeconds: Integer类型。JDBC尝试连接主机后会保存主机状态: 连接成功或连接失败。在hostRecheckSeconds时间内保持可信，超过则状态失效。缺省值是10秒。<br />- ssl: Boolean类型。以SSL方式连接。ssl=true可支持NonValidatingFactory通道和使用证书的方式: <br />1、NonValidatingFactory通道需要配置用户名和密码，同时将SSL设置为true。<br />2、配置客户端证书、密钥、根证书，将SSL设置为true。<br />- sslmode: String类型。SSL认证方式。取值范围为: require、verify-ca、verify-full。<br />    - require只尝试SSL连接，如果存在CA文件，则应设置成verify-ca的方式验证。<br />    - verify-ca只尝试SSL连接，并且验证服务器是否具有由可信任的证书机构签发的证书。<br />    - verify-full只尝试SSL连接，并且验证服务器是否具有由可信任的证书机构签发的证书，以及验证服务器主机名是否与证书中的一致。<br />- sslcert: String类型。提供证书文件的完整路径。客户端和服务端证书的类型为End Entity。<br />- sslkey: String类型。提供密钥文件的完整路径。使用时将客户端证书转换为DER格式: <br />*openssl pkcs8 -topk8 -outform DER -in client.key -out client.key.pk8 -nocrypt*<br />- sslrootcert: String类型。SSL根证书的文件名。根证书的类型为CA。<br />- sslpassword: String类型。提供给ConsoleCallbackHandler使用。<br />- sslpasswordcallback: String类型。SSL密码提供者的类名。缺省值: org.postgresql.ssl.jdbc4.LibPQFactory.ConsoleCallbackHandler。<br />- sslfactory: String类型。提供的值是SSLSocketFactory在建立SSL连接时用的类名。<br />- sslfactoryarg: String类型。此值是上面提供的sslfactory类的构造函数的可选参数（不推荐使用）。<br />- sslhostnameverifier: String类型。主机名验证程序的类名。接口实现javax.net.ssl.HostnameVerifier，默认使用org.postgresql.ssl.PGjdbcHostnameVerifier。<br />- loginTimeout: Integer类型。指建立数据库连接的等待时间。超时时间单位为秒。<br />- connectTimeout: Integer类型。用于连接服务器操作的超时值。如果连接到服务器花费的时间超过此值，则连接断开。超时时间单位为秒，值为0时表示已禁用，timeout不发生。<br />- socketTimeout: Integer类型。用于socket读取操作的超时值。如果从服务器读取所花费的时间超过此值，则连接关闭。超时时间单位为秒，值为0时表示已禁用，timeout不发生。<br />- cancelSignalTimeout: Integer类型。发送取消消息本身可能会阻塞，此属性控制用于取消命令的"connect超时"和"socket超时"。超时时间单位为秒，默认值为10秒。<br />- tcpKeepAlive: Boolean类型。启用或禁用TCP保活探测功能。默认为false。<br />- logUnclosedConnections: Boolean类型。客户端可能由于未调用Connection对象的close()方法而泄漏Connection对象。最终这些对象将被垃圾回收，并且调用finalize()方法。如果调用者自己忽略了此操作，该方法将关闭Connection。<br />- assumeMinServerVersion: String类型。客户端会发送请求进行float精度设置。该参数设置要连接的服务器版本，如assumeMinServerVersion=9.0，可以在建立时减少相关包的发送。<br />- ApplicationName: String类型。设置正在使用连接的JDBC驱动的名称。通过在数据库主节点上查询pg_stat_activity表可以看到正在连接的客户端信息，JDBC驱动名称显示在application_name列。缺省值为PostgreSQL JDBC Driver。<br />- connectionExtraInfo: Boolean类型。表示驱动是否上报当前驱动的部署路径、进程属主用户到数据库。取值范围: true或false，默认值为false。设置connectionExtraInfo为true，JDBC驱动会将当前驱动的部署路径、进程属主用户上报到数据库中，记录在connection_info参数里；同时可以在PG_STAT_ACTIVITY中查询到。<br />- autosave: String类型。共有3种: "always", "never", "conservative"。如果查询失败，指定驱动程序应该执行的操作。在autosave=always模式下，JDBC驱动程序在每次查询之前设置一个保存点，并在失败时回滚到该保存点。在autosave=never模式（默认）下，无保存点。在autosave=conservative模式下，每次查询都会设置保存点，但是只会在"statement XXX无效"等情况下回滚并重试。<br />- protocolVersion: Integer类型。连接协议版本号，目前仅支持3。注意:设置该参数时将采用md5加密方式，需要同步修改数据库的加密方式: gs_guc set -N all -I all -c "password_encryption_type=1" ，重启MogDB生效后需要创建用md5方式加密口令的用户。同时修改pg_hba.conf，将客户端连接方式修改为md5。用新建用户进行登录（不推荐）。<br />- prepareThreshold: Integer类型。控制parse语句何时发送。默认值是5。第一次parse一个SQL比较慢，后面再parse就会比较快，因为有缓存了。如果一个会话连续多次执行同一个SQL，在达到prepareThreshold次数以上时，JDBC将不再对这个SQL发送parse命令。<br />- preparedStatementCacheQueries: Integer类型。确定每个连接中缓存的查询数，默认情况下是256。若在prepareStatement()调用中使用超过256个不同的查询，则最近最少使用的查询缓存将被丢弃。0表示禁用缓存。<br />- preparedStatementCacheSizeMiB: Integer类型。确定每个连接可缓存的最大值（以兆字节为单位），默认情况下是5。若缓存了超过5MB的查询，则最近最少使用的查询缓存将被丢弃。0表示禁用缓存。<br />- databaseMetadataCacheFields: Integer类型。默认值是65536。指定每个连接可缓存的最大值。"0"表示禁用缓存。<br />- databaseMetadataCacheFieldsMiB: Integer类型。默认值是5。每个连接可缓存的最大值，单位是MB。"0"表示禁用缓存。<br />- stringtype: String类型，可选字段为: false, "unspecified", "varchar"。设置通过setString()方法使用的PreparedStatement参数的类型，如果stringtype设置为VARCHAR（默认值），则这些参数将作为varchar参数发送给服务器。若stringtype设置为unspecified，则参数将作为untyped值发送到服务器，服务器将尝试推断适当的类型。<br />- batchMode: Boolean类型。用于确定是否使用batch模式连接。<br />- fetchsize: Integer类型。用于设置数据库连接所创建statement的默认fetchsize。<br />- reWriteBatchedInserts: Boolean类型。批量导入时，该参数设置为on，可将N条插入语句合并为一条: insert into TABLE_NAME values(values1, …, valuesN), …, (values1, …, valuesN);使用该参数时，需设置batchMode=off。<br />- unknownLength: Integer类型，默认为Integer.MAX_VALUE。某些postgresql类型（例如TEXT）没有明确定义的长度，当通过ResultSetMetaData.getColumnDisplaySize和ResultSetMetaData.getPrecision等函数返回关于这些类型的数据时，此参数指定未知长度类型的长度。<br />- defaultRowFetchSize: Integer类型。确定一次fetch在ResultSet中读取的行数。限制每次访问数据库时读取的行数可以避免不必要的内存消耗，从而避免OutOfMemoryException。缺省值是0，这意味着ResultSet中将一次获取所有行。没有负数。<br />- binaryTransfer: Boolean类型。使用二进制格式发送和接收数据，默认值为"false"。<br />- binaryTransferEnable: String类型。启用二进制传输的类型列表，以逗号分隔。OID编号和名称二选一，例如binaryTransferEnable=Integer4_ARRAY,Integer8_ARRAY。比如: OID名称为BLOB，编号为88，可以如下配置: <br />binaryTransferEnable=BLOB 或 binaryTransferEnable=88<br />- binaryTransferDisEnable: String类型。禁用二进制传输的类型列表，以逗号分隔。OID编号和名称二选一。覆盖binaryTransferEnable的设置。<br />- blobMode: String类型。用于设置setBinaryStream方法为不同类型的数据赋值，设置为on时表示为blob类型数据赋值，设置为off时表示为bytea类型数据赋值，默认为on。<br />- socketFactory: String类型。用于创建与服务器socket连接的类的名称。该类必须实现了接口"javax.net.SocketFactory"，并定义无参或单String参数的构造函数。<br />- socketFactoryArg: String类型。此值是上面提供的socketFactory类的构造函数的可选参数，不推荐使用。<br />- receiveBufferSize: Integer类型。该值用于设置连接流上的SO_RCVBUF。<br />- sendBufferSize: Integer类型。该值用于设置连接流上的SO_SNDBUF。<br />- preferQueryMode: String类型。共有4种: "extended", "extendedForPrepared", "extendedCacheEverything", "simple"。用于指定执行查询的模式，simple模式会excute，不parse和bind；extended模式会bind和excute；extendedForPrepared模式为prepared statement扩展使用；extendedCacheEverything模式会缓存每个statement。<br />- targetServerType: String类型。共有4种: "any"、"master"、"slave"、"preferSlave"。 |
+| user     | 数据库用户。          |
+| password | 数据库用户的密码。    |
+
+<br/>
+
+## 示例
+
+```java
+//以下代码将获取数据库连接操作封装为一个接口，可通过给定用户名和密码来连接数据库。
+public static Connection getConnect(String username, String passwd)
+    {
+        //驱动类。
+        String driver = "org.postgresql.Driver";
+        //数据库连接描述符。
+        String sourceURL = "jdbc:postgresql://10.10.0.13:8000/postgres";
+        Connection conn = null;
+
+        try
+        {
+            //加载驱动。
+            Class.forName(driver);
+        }
+        catch( Exception e )
+        {
+            e.printStackTrace();
+            return null;
+        }
+
+        try
+        {
+             //创建连接。
+            conn = DriverManager.getConnection(sourceURL, username, passwd);
+            System.out.println("Connection succeed!");
+        }
+        catch(Exception e)
+        {
+            e.printStackTrace();
+            return null;
+        }
+
+        return conn;
+    };
+// 以下代码将使用Properties对象作为参数建立连接
+public static Connection getConnectUseProp(String username, String passwd)
+    {
+        //驱动类。
+        String driver = "org.postgresql.Driver";
+        //数据库连接描述符。
+        String sourceURL = "jdbc:postgresql://10.10.0.13:8000/postgres?";
+        Connection conn = null;
+        Properties info = new Properties();
+
+        try
+        {
+            //加载驱动。
+            Class.forName(driver);
+        }
+        catch( Exception e )
+        {
+            e.printStackTrace();
+            return null;
+        }
+
+        try
+        {
+             info.setProperty("user", username);
+             info.setProperty("password", passwd);
+             //创建连接。
+             conn = DriverManager.getConnection(sourceURL, info);
+             System.out.println("Connection succeed!");
+        }
+        catch(Exception e)
+        {
+            e.printStackTrace();
+            return null;
+        }
+
+        return conn;
+    };
+```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/6-connecting-to-a-database-using-ssl.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/6-connecting-to-a-database-using-ssl.md
new file mode 100644
index 0000000000000000000000000000000000000000..c3f733fe73c0afdfc9b34f2603785c4cb499b917
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/6-connecting-to-a-database-using-ssl.md
@@ -0,0 +1,149 @@
+---
+title: 连接数据库（以SSL方式）
+summary: 连接数据库（以SSL方式）
+author: Guo Huan
+date: 2021-04-26
+---
+
+# 连接数据库（以SSL方式）
+
+用户通过JDBC连接MogDB服务器时，可以通过开启SSL加密客户端和服务器之间的通讯，为敏感数据在Internet上的传输提供了一种安全保障手段。本小节主要介绍应用程序通过JDBC如何采用SSL的方式连接MogDB。在使用本小节所描述的方法前，默认用户已经获取了服务端和客户端所需要的证书和私钥文件，关于证书等文件的获取请参考Openssl相关文档和命令 。
+
+<br/>
+
+## 服务端配置
+
+当开启SSL模式后，必须提供根证书、服务器证书和私钥。
+
+配置步骤（假设用户的证书文件放在数据目录/mogdb/data/datanode下，且采用默认文件名）:
+
+1. 以操作系统用户omm登录数据库主节点。
+
+2. 生成并配置证书
+
+    生成SSL证书，具体请参见"证书生成"。将生成出的文件server.crt，server.key，cacert.pem拷贝到服务端数据目录下。
+
+    使用如下命令可以查询数据库节点的数据目录，instance列为数据目录。
+
+    ```bash
+    gs_om -t status --detail
+    ```
+
+    在Unix系统上，server.crt、server.key的权限设置必须禁止任何外部或组的访问，请执行如下命令实现这一点。
+
+    ```bash
+    chmod 0600 server.key
+    ```
+
+3. 开启SSL认证模式。
+
+    ```bash
+    gs_guc set -D /mogdb/data/datanode -c "ssl=on"
+    ```
+
+4. 配置客户端接入认证参数，IP为所要连接的主机IP。
+
+    ```bash
+    gs_guc reload -D /mogdb/data/datanode -h "hostssl all             all             127.0.0.1/32           cert"
+    gs_guc reload -D /mogdb/data/datanode -h "hostssl all             all             IP/32           cert"
+    ```
+
+    表示允许127.0.0.1/32网段的客户端以ssl认证方式连接到MogDB服务器。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+    > 如果服务端pg_hba.conf文件中METHOD配置为cert，则只有客户端使用证书（client.crt）中所设置的用户名（common name）才能够成功连接数据库。如果设置为md5或sha256则对连接数据库的用户没有限制。
+
+5. 配置SSL认证相关的数字证书参数。
+
+    各命令后所附为设置成功的回显。
+
+    ```bash
+    gs_guc set -D /mogdb/data/datanode -c "ssl_cert_file='server.crt'"
+    gs_guc set: ssl_cert_file='server.crt'
+    ```
+
+    ```bash
+    gs_guc set -D /mogdb/data/datanode -c "ssl_key_file='server.key'"
+    gs_guc set: ssl_key_file='server.key'
+    ```
+
+    ```bash
+    gs_guc set -D /mogdb/data/datanode -c "ssl_ca_file='cacert.pem'"
+    gs_guc set: ssl_ca_file='cacert.pem'
+    ```
+
+6. 重启数据库。
+
+    ```bash
+    gs_om -t stop && gs_om -t start
+    ```
+
+7. 生成并上传证书文件
+
+<br/>
+
+## 客户端配置
+
+配置步骤如下:
+
+上传证书文件，将在服务端配置章节生成出的文件client.key.pk8，client.crt，cacert.pem放置在客户端。
+
+<br/>
+
+## 示例
+
+```java
+import java.sql.Connection;
+import java.util.Properties;
+import java.sql.DriverManager;
+import java.sql.Statement;
+import java.sql.ResultSet;
+
+public class SSL{
+    public static void main(String[] args) {
+        Properties urlProps = new Properties();
+        String urls = "jdbc:postgresql://10.29.37.136:8000/postgres";
+
+        /**
+         * ==================  示例1  使用NonValidatingFactory通道，pg_hba.conf文件中MTETHOD不为cert
+         */
+/*
+        urlProps.setProperty("sslfactory","org.postgresql.ssl.NonValidatingFactory");
+        urlProps.setProperty("user", "world");
+        //此处的test@123为创建用户CRETAE USER world WITH PASSWORD 'test123@'时指定的密码
+        urlProps.setProperty("password", "test@123");
+        urlProps.setProperty("ssl", "true");
+*/
+        /**
+         * ==================  示例2 - 5  使用证书，pg_hba.conf文件中MTETHOD为cert
+         */
+        urlProps.setProperty("sslcert", "client.crt");
+        // DER格式的客户端秘钥
+        urlProps.setProperty("sslkey", "client.key.pk8");
+        urlProps.setProperty("sslrootcert", "cacert.pem");
+        urlProps.setProperty("user", "world");
+        /* ==================  示例2  设置ssl为true，使用证书认证 */
+        urlProps.setProperty("ssl", "true");
+        /* ==================  示例3  设置sslmode为require，使用证书 */
+//        urlProps.setProperty("sslmode", "require");
+        /* ==================  示例4  设置sslmode为verify-ca，使用证书 */
+//        urlProps.setProperty("sslmode", "verify-ca");
+        /* ==================  示例5  设置sslmode为verify-full，使用证书（Linux下验证） */
+//        urls = "jdbc:postgresql://world:8000/postgres";
+//        urlProps.setProperty("sslmode", "verify-full");
+
+        try {
+            Class.forName("org.postgresql.Driver").newInstance();
+        } catch (Exception e) {
+            e.printStackTrace();
+        }
+        try {
+            Connection conn;
+            conn = DriverManager.getConnection(urls,urlProps);
+            conn.close();
+        } catch (Exception e) {
+            e.printStackTrace();
+        }
+    }
+}
+```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/7-running-sql-statements.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/7-running-sql-statements.md
new file mode 100644
index 0000000000000000000000000000000000000000..a4ee1896eb6c977ee8f14c99d1140f2083d75de9
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/7-running-sql-statements.md
@@ -0,0 +1,177 @@
+---
+title: 执行SQL语句
+summary: 执行SQL语句
+author: Guo Huan
+date: 2021-06-07
+---
+
+# 执行SQL语句
+
+<br/>
+
+## 执行普通SQL语句
+
+应用程序通过执行SQL语句来操作数据库的数据（不用传递参数的语句），需要按以下步骤执行:
+
+1. 调用Connection的createStatement方法创建语句对象。
+
+    ```java
+    Connection conn = DriverManager.getConnection("url","user","password");
+    Statement stmt = conn.createStatement();
+    ```
+
+2. 调用Statement的executeUpdate方法执行SQL语句。
+
+    ```java
+    int rc = stmt.executeUpdate("CREATE TABLE customer_t1(c_customer_sk INTEGER, c_customer_name VARCHAR(32));");
+    ```
+
+    > **说明:**
+    > 数据库中收到的一次执行请求（不在事务块中），如果含有多条语句，将会被打包成一个事务，事务块中不支持vacuum操作。如果其中有一个语句失败，那么整个请求都将会被回滚。
+
+3. 关闭语句对象。
+
+    ```java
+    stmt.close();
+    ```
+
+<br/>
+
+## 执行预编译SQL语句
+
+预编译语句是只编译和优化一次，然后可以通过设置不同的参数值多次使用。由于已经预先编译好，后续使用会减少执行时间。因此，如果多次执行一条语句，请选择使用预编译语句。可以按以下步骤执行:
+
+1. 调用Connection的prepareStatement方法创建预编译语句对象。
+
+    ```java
+    PreparedStatement pstmt = con.prepareStatement("UPDATE customer_t1 SET c_customer_name = ? WHERE c_customer_sk = 1");
+    ```
+
+2. 调用PreparedStatement的setShort设置参数。
+
+    ```java
+    pstmt.setShort(1, (short)2);
+    ```
+
+3. 调用PreparedStatement的executeUpdate方法执行预编译SQL语句。
+
+    ```java
+    int rowcount = pstmt.executeUpdate();
+    ```
+
+4. 调用PreparedStatement的close方法关闭预编译语句对象。
+
+    ```java
+    pstmt.close();
+    ```
+
+<br/>
+
+## 调用存储过程
+
+MogDB支持通过JDBC直接调用事先创建的存储过程，步骤如下:
+
+1. 调用Connection的prepareCall方法创建调用语句对象。
+
+    ```java
+    Connection myConn = DriverManager.getConnection("url","user","password");
+    CallableStatement cstmt = myConn.prepareCall("{? = CALL TESTPROC(?,?,?)}");
+    ```
+
+2. 调用CallableStatement的setInt方法设置参数。
+
+    ```java
+    cstmt.setInt(2, 50);
+    cstmt.setInt(1, 20);
+    cstmt.setInt(3, 90);
+    ```
+
+3. 调用CallableStatement的registerOutParameter方法注册输出参数。
+
+    ```java
+    cstmt.registerOutParameter(4, Types.INTEGER);  //注册out类型的参数，类型为整型。
+    ```
+
+4. 调用CallableStatement的execute执行方法调用。
+
+    ```java
+    cstmt.execute();
+    ```
+
+5. 调用CallableStatement的getInt方法获取输出参数。
+
+    ```java
+    int out = cstmt.getInt(4);  //获取out参数
+    ```
+
+    示例:
+
+    ```sql
+    //在数据库中已创建了如下存储过程，它带有out参数。
+    create or replace procedure testproc
+    (
+        psv_in1 in integer,
+        psv_in2 in integer,
+        psv_inout in out integer
+    )
+    as
+    begin
+        psv_inout := psv_in1 + psv_in2 + psv_inout;
+    end;
+    /
+    ```
+
+6. 调用CallableStatement的close方法关闭调用语句。
+
+    ```java
+    cstmt.close();
+    ```
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+    >
+    > - 很多的数据库类如Connection、Statement和ResultSet都有close()方法，在使用完对象后应把它们关闭。要注意的是，Connection的关闭将间接关闭所有与它关联的   Statement，Statement的关闭间接关闭了ResultSet。
+    >
+    > - 一些JDBC驱动程序还提供命名参数的方法来设置参数。命名参数的方法允许根据名称而不是顺序来设置参数，若参数有默认值，则可以不用指定参数值就可以使用此参数的默认值。即使存储过程中参数的顺序发生了变更，也不必修改应用程序。目前MogDB数据库的JDBC驱动程序不支持此方法。
+    >
+    > - MogDB数据库不支持带有输出参数的函数，也不支持存储过程和函数参数默认值。
+    >
+    >   ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+    >
+    > - 当游标作为存储过程的返回值时，如果使用JDBC调用该存储过程，返回的游标将不可用。
+    >
+    > - 存储过程不能和普通SQL在同一条语句中执行。
+
+<br/>
+
+## 执行批处理
+
+用一条预处理语句处理多条相似的数据，数据库只创建一次执行计划，节省了语句的编译和优化时间。可以按如下步骤执行:
+
+1. 调用Connection的prepareStatement方法创建预编译语句对象。
+
+    ```java
+    Connection conn = DriverManager.getConnection("url","user","password");
+    PreparedStatement pstmt = conn.prepareStatement("INSERT INTO customer_t1 VALUES (?)");
+    ```
+
+2. 针对每条数据都要调用setShort设置参数，以及调用addBatch确认该条设置完毕。
+
+    ```java
+    pstmt.setShort(1, (short)2);
+    pstmt.addBatch();
+    ```
+
+3. 调用PreparedStatement的executeBatch方法执行批处理。
+
+    ```java
+    int[] rowcount = pstmt.executeBatch();
+    ```
+
+4. 调用PreparedStatement的close方法关闭预编译语句对象。
+
+    ```java
+    pstmt.close();
+    ```
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+    > 在实际的批处理过程中，通常不终止批处理程序的执行，否则会降低数据库的性能。因此在批处理程序时，应该关闭自动提交功能，每几行提交一次。关闭自动提交功能的语句为:  conn.setAutoCommit(false);
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/8-processing-data-in-a-result-set.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/8-processing-data-in-a-result-set.md
new file mode 100644
index 0000000000000000000000000000000000000000..9e33d223708fbc5aefd4eb551c00b5a1a6b08e77
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/8-processing-data-in-a-result-set.md
@@ -0,0 +1,84 @@
+---
+title: 处理结果集
+summary: 处理结果集
+author: Guo Huan
+date: 2021-04-26
+---
+
+# 处理结果集
+
+<br/>
+
+## 设置结果集类型
+
+不同类型的结果集有各自的应用场景，应用程序需要根据实际情况选择相应的结果集类型。在执行SQL语句过程中，都需要先创建相应的语句对象，而部分创建语句对象的方法提供了设置结果集类型的功能。具体的参数设置如[表1](#结果集类型)所示。涉及的Connection的方法如下:
+
+```
+//创建一个Statement对象，该对象将生成具有给定类型和并发性的ResultSet对象。
+createStatement(int resultSetType, int resultSetConcurrency);
+
+//创建一个PreparedStatement对象，该对象将生成具有给定类型和并发性的ResultSet对象。
+prepareStatement(String sql, int resultSetType, int resultSetConcurrency);
+
+//创建一个CallableStatement对象，该对象将生成具有给定类型和并发性的ResultSet对象。
+prepareCall(String sql, int resultSetType, int resultSetConcurrency);
+```
+
+**<a id="结果集类型">表 1</a>** 结果集类型
+
+| 参数                 | 描述    |
+| :------------------- | :-------------------------|
+| resultSetType        | 表示结果集的类型，具体有三种类型: <br />- ResultSet.TYPE_FORWARD_ONLY: ResultSet只能向前移动。是缺省值。<br />- ResultSet.TYPE_SCROLL_SENSITIVE: 在修改后重新滚动到修改所在行，可以看到修改后的结果。<br />- ResultSet.TYPE_SCROLL_INSENSITIVE: 对可修改例程所做的编辑不进行显示。<br />说明:<br />结果集从数据库中读取了数据之后，即使类型是ResultSet.TYPE_SCROLL_SENSITIVE，也不会看到由其他事务在这之后引起的改变。调用ResultSet的refreshRow()方法，可进入数据库并从其中取得当前游标所指记录的最新数据。 |
+| resultSetConcurrency | 表示结果集的并发，具体有两种类型: <br />- ResultSet.CONCUR_READ_ONLY: 如果不从结果集中的数据建立一个新的更新语句，不能对结果集中的数据进行更新。<br />- ResultSet.CONCUR_UPDATEABLE: 可改变的结果集。对于可滚动的结果集，可对结果集进行适当的改变。                                                                                                                                                                                                                                                         |
+
+<br/>
+
+## 在结果集中定位
+
+ResultSet对象具有指向其当前数据行的光标。最初，光标被置于第一行之前。next方法将光标移动到下一行；因为该方法在ResultSet对象没有下一行时返回false，所以可以在while循环中使用它来迭代结果集。但对于可滚动的结果集，JDBC驱动程序提供更多的定位方法，使ResultSet指向特定的行。定位方法如[表2](#结果集中定位方法)所示。
+
+**<a id="结果集中定位方法">表 2 </a>**在结果集中定位的方法
+
+| 方法          | 描述                                                                                             |
+| :------------ | :----------------------------------------------------------------------------------------------- |
+| next()        | 把ResultSet向下移动一行。                                                                        |
+| previous()    | 把ResultSet向上移动一行。                                                                        |
+| beforeFirst() | 把ResultSet定位到第一行之前。                                                                    |
+| afterLast()   | 把ResultSet定位到最后一行之后。                                                                  |
+| first()       | 把ResultSet定位到第一行。                                                                        |
+| last()        | 把ResultSet定位到最后一行。                                                                      |
+| absolute(int) | 把ResultSet移动到参数指定的行数。                                                                |
+| relative(int) | 通过设置为1向前（设置为1，相当于next()）或者向后（设置为-1，相当于previous()）移动参数指定的行。 |
+
+<br/>
+
+## 获取结果集中光标的位置
+
+对于可滚动的结果集，可能会调用定位方法来改变光标的位置。JDBC驱动程序提供了获取结果集中光标所处位置的方法。获取光标位置的方法如[表3](#获取结果集光标位置)所示。
+
+**<a id="获取结果集光标位置">表 3 </a>** 获取结果集光标的位置
+
+| 方法            | 描述                 |
+| :-------------- | :------------------- |
+| isFirst()       | 是否在一行。         |
+| isLast()        | 是否在最后一行。     |
+| isBeforeFirst() | 是否在第一行之前。   |
+| isAfterLast()   | 是否在最后一行之后。 |
+| getRow()        | 获取当前在第几行。   |
+
+<br/>
+
+## 获取结果集中的数据
+
+ResultSet对象提供了丰富的方法，以获取结果集中的数据。获取数据常用的方法如[表4](#对象的常用方法)所示，其他方法请参考JDK官方文档。
+
+**<a id="对象的常用方法">表 4 </a>**ResultSet对象的常用方法
+
+| 方法                                 | 描述                     |
+| :----------------------------------- | :----------------------- |
+| int getInt(int columnIndex)          | 按列标获取int型数据。    |
+| int getInt(String columnLabel)       | 按列名获取int型数据。    |
+| String getString(int columnIndex)    | 按列标获取String型数据。 |
+| String getString(String columnLabel) | 按列名获取String型数据。 |
+| Date getDate(int columnIndex)        | 按列标获取Date型数据     |
+| Date getDate(String columnLabel)     | 按列名获取Date型数据。   |
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/8.1-log-management.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/8.1-log-management.md
new file mode 100644
index 0000000000000000000000000000000000000000..10d2e1a124c773f6119be4cc4f2d3188560ffad2
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/8.1-log-management.md
@@ -0,0 +1,145 @@
+---
+title: 日志管理
+summary: 日志管理
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# 日志管理
+
+MogDB JDBC驱动程序支持使用日志记录来帮助解决在应用程序中使用MogDB JDBC驱动程序时的问题。MogDB JDBC支持如下三种日志管理方式：
+
+1. 使用连接属性指定临时日志文件。
+2. 对接应用程序使用的SLF4J日志框架。
+3. 对接应用程序使用的JdkLogger日志框架。
+
+SLF4J和JdkLogger是业界Java应用程序日志管理的主流框架，描述应用程序如何使用这些框架超出了本文范围，用户请参考对应的官方文档
+
+- SLF4J: <http://www.slf4j.org/manual.html>
+- JdkLogger <https://docs.oracle.com/javase/8/docs/technotes/guides/logging/overview.html>
+
+方式一：使用连接属性。
+
+url上配置loggerLevel和loggerFile。
+
+此种方式，配置简单，适用于调试驱动，但不支持日志级别、文件大小、文件数量管控，若日志不及时手动处理，会占满磁盘，因此，除调试驱动，不建议用此方式管理日志。
+
+示例：
+
+```
+public static Connection GetConnection(String username, String passwd){
+
+    String sourceURL = "jdbc:postgresql://10.10.0.13:8000/postgres?loggerLevel=DEBUG&loggerFile=gsjdbc.log";
+    Connection conn = null;
+
+    try{
+        //创建连接
+        conn = DriverManager.getConnection(sourceURL,username,passwd);
+        System.out.println("Connection succeed!");
+    }catch (Exception e){
+        e.printStackTrace();
+        return null;
+    }
+    return conn;
+}
+```
+
+方式二：对接应用程序的SLF4J日志框架。
+
+在建立连接时，url配置logger=Slf4JLogger。
+
+可采用Log4j或Log4j2来实现SLF4J。当采用Log4j实现SLF4J，需要添加如下jar包：log4j-\*.jar、slf4j-api-\*.jar、slf4j-log4\*-\*.jar，（\*区分版本），和配置文件：log4j.properties。若采用Log4j2实现SLF4J，需要添加如下jar包：log4j-api-\*.jar、log4j-core-\*.jar、log4j-slf4j18-impl-\*.jar、slf4j-api-*-alpha1.jar（\*区分版本），和配置文件：log4j2.xml。
+
+此方式支持日志管控。SLF4J可通过文件中的相关配置实现强大的日志管控功能，建议使用此方式进行日志管理。注意：此方式依赖slf4j的通用API接口，如org.slf4j.LoggerFactory.getLogger(String name)、org.slf4j.Logger.debug(String var1)、org.slf4j.Logger.info(String var1)、org.slf4j.Logger.warn(String warn)、org.slf4j.Logger.warn(String warn)等，若以上接口发生变更，日志将无法打印。
+
+示例：
+
+```
+public static Connection GetConnection(String username, String passwd){
+
+    String sourceURL = "jdbc:postgresql://10.10.0.13:8000/postgres?logger=Slf4JLogger";
+    Connection conn = null;
+
+    try{
+        //创建连接
+        conn = DriverManager.getConnection(sourceURL,username,passwd);
+        System.out.println("Connection succeed!");
+    }catch (Exception e){
+        e.printStackTrace();
+        return null;
+    }
+    return conn;
+}
+```
+
+log4j.properties示例：
+
+```
+log4j.logger.org.postgresql=ALL, log_gsjdbc
+
+# 默认文件输出配置
+log4j.appender.log_gsjdbc=org.apache.log4j.RollingFileAppender
+log4j.appender.log_gsjdbc.Append=true
+log4j.appender.log_gsjdbc.File=gsjdbc.log
+log4j.appender.log_gsjdbc.Threshold=TRACE
+log4j.appender.log_gsjdbc.MaxFileSize=10MB
+log4j.appender.log_gsjdbc.MaxBackupIndex=5
+log4j.appender.log_gsjdbc.layout=org.apache.log4j.PatternLayout
+log4j.appender.log_gsjdbc.layout.ConversionPattern=%d %p %t %c - %m%n
+log4j.appender.log_gsjdbc.File.Encoding = UTF-8
+```
+
+log4j2.xml示例：
+
+```
+<?xml version="1.0" encoding="UTF-8"?>
+<configuration status="OFF">
+    <appenders>
+        <Console name="Console" target="SYSTEM_OUT">
+            <PatternLayout pattern="%d %p %t %c - %m%n"/>
+        </Console>
+        <File name="FileTest" fileName="test.log">
+            <PatternLayout pattern="%d %p %t %c - %m%n"/>
+        </File>
+        <!--JDBC Driver日志文件输出配置，支持日志回卷，设定日志大小超过10MB时，创建新的文件，新文件的命名格式为：年-月-日-文件编号-->
+        <RollingFile name="RollingFileJdbc" fileName="gsjdbc.log" filePattern="%d{yyyy-MM-dd}-%i.log">
+            <PatternLayout pattern="%d %p %t %c - %m%n"/>
+            <Policies>
+                <SizeBasedTriggeringPolicy size="10 MB"/>
+            </Policies>
+        </RollingFile>
+    </appenders>
+    <loggers>
+        <root level="all">
+            <appender-ref ref="Console"/>
+            <appender-ref ref="FileTest"/>
+        </root>
+        <!--指定JDBC Driver日志，级别为：all，可查看所有日志，输出到gsjdbc.log文件中-->
+        <logger name="org.postgresql" level="all" additivity="false">
+            <appender-ref ref="RollingFileJdbc"/>
+        </logger>
+    </loggers>
+</configuration>
+```
+
+方式三：对接应用程序使用的JdkLogger日志框架。
+
+默认的Java日志记录框架将其配置存储在名为logging.properties的文件中。Java会在Java安装目录的文件夹中安装全局配置文件。logging.properties文件也可以创建并与单个项目一起存储。
+
+logging.properties配置示例：
+
+```
+# 指定处理程序为文件。
+handlers= java.util.logging.FileHandler
+
+# 指定默认全局日志级别
+.level= ALL
+
+# 指定日志输出管控标准
+java.util.logging.FileHandler.level=ALL
+java.util.logging.FileHandler.pattern = gsjdbc.log
+java.util.logging.FileHandler.limit = 500000
+java.util.logging.FileHandler.count = 30
+java.util.logging.FileHandler.formatter = java.util.logging.SimpleFormatter
+java.util.logging.FileHandler.append=false
+```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/9-closing-a-connection.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/9-closing-a-connection.md
new file mode 100644
index 0000000000000000000000000000000000000000..588c5b611668b49179e729046ad059a6d0636798
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/2-development-based-on-jdbc/9-closing-a-connection.md
@@ -0,0 +1,12 @@
+---
+title: 关闭连接
+summary: 关闭连接
+author: Guo Huan
+date: 2021-06-07
+---
+
+# 关闭连接
+
+在使用数据库连接完成相应的数据操作后，需要关闭数据库连接。
+
+关闭数据库连接可以直接调用其close方法即可。如：**Connection conn = DriverManager.getConnection(“url”,“user”,“password”) ; conn.close()**；
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/1-development-based-on-odbc-overview.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/1-development-based-on-odbc-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..84f145910426cd321d948d661e1ba6c22daf4ed0
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/1-development-based-on-odbc-overview.md
@@ -0,0 +1,34 @@
+---
+title: 概述
+summary: 概述
+author: Guo Huan
+date: 2021-04-26
+---
+
+# 概述
+
+ODBC（Open Database Connectivity，开放数据库互连）是由Microsoft公司基于X/OPEN CLI提出的用于访问数据库的应用程序编程接口。应用程序通过ODBC提供的API与数据库进行交互，增强了应用程序的可移植性、扩展性和可维护性。
+
+ODBC的系统结构参见[图1](#ODBC)。
+
+**图 1**ODBC系统机构<a id="ODBC"> </a>
+
+![ODBC系统机构](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/development-based-on-odbc-overview-1.png)
+
+MogDB目前在以下环境中提供对ODBC3.5的支持。
+
+**表 1** ODBC支持平台
+
+| 操作系统                                           | 平台     |
+| :------------------------------------------------- | :------- |
+| CentOS 6.4/6.5/6.6/6.7/6.8/6.9/7.0/7.1/7.2/7.3/7.4 | x86_64位 |
+| CentOS 7.6                                         | ARM64位  |
+| EulerOS 2.0 SP2/SP3                                | x86_64位 |
+| EulerOS 2.0 SP8                                    | ARM64位  |
+
+UNIX/Linux系统下的驱动程序管理器主要有unixODBC和iODBC，在这选择驱动管理器unixODBC-2.3.0作为连接数据库的组件。
+
+Windows系统自带ODBC驱动程序管理器，在控制面板->管理工具中可以找到数据源（ODBC）选项。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+> 当前数据库ODBC驱动基于开源版本，对于tinyint、smalldatetime、nvarchar2类型，在获取数据类型的时候，可能会出现不兼容。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/2-odbc-packages-dependent-libraries-and-header-files.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/2-odbc-packages-dependent-libraries-and-header-files.md
new file mode 100644
index 0000000000000000000000000000000000000000..809fc5840b83bdcae7435d1ab05c8f07c1f7d475
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/2-odbc-packages-dependent-libraries-and-header-files.md
@@ -0,0 +1,14 @@
+---
+title: ODBC包及依赖的库和头文件
+summary: ODBC包及依赖的库和头文件
+author: Guo Huan
+date: 2021-04-26
+---
+
+# ODBC包及依赖的库和头文件
+
+<br/>
+
+## Linux下的ODBC包
+
+从发布包中获取，包名为[openGauss-x.x.x-ODBC.tar.gz](https://opengauss.org/zh/download.html)。Linux环境下，开发应用程序要用到unixODBC提供的头文件（sql.h、sqlext.h等）和库libodbc.so。这些头文件和库可从unixODBC-2.3.0的安装包中获得。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md
new file mode 100644
index 0000000000000000000000000000000000000000..e0b60066799a2a9f642b979b855bf1f3c6af39ef
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md
@@ -0,0 +1,326 @@
+---
+title: Linux下配置数据源
+summary: Linux下配置数据源
+author: Guo Huan
+date: 2021-06-16
+---
+
+# Linux下配置数据源
+
+将MogDB提供的ODBC DRIVER（psqlodbcw.so）配置到数据源中便可使用。配置数据源需要配置"odbc.ini"和"odbcinst.ini"两个文件（在编译安装unixODBC过程中生成且默认放在"/usr/local/etc"目录下），并在服务器端进行配置。
+
+<br/>
+
+## 操作步骤
+
+1. 获取unixODBC源码包。获取参考地址: <https://sourceforge.net/projects/unixodbc/files/unixODBC/2.3.7/unixODBC-2.3.7pre.tar.gz/download> 下载后请先按照社区提供的完整性校验算法进行完整性校验。
+
+2. 安装unixODBC。如果机器上已经安装了其他版本的unixODBC，可以直接覆盖安装。
+
+    目前不支持unixODBC-2.2.1版本。以unixODBC-2.3.0版本为例，在客户端执行如下命令安装unixODBC。默认安装到"/usr/local"目录下，生成数据源文件到 "/usr/local/etc"目录下，库文件生成在"/usr/local/lib"目录。
+
+    ```bash
+    tar zxvf unixODBC-2.3.0.tar.gz
+    cd unixODBC-2.3.0
+    #修改configure文件（如果不存在，那么请修改configure.ac），找到LIB_VERSION
+    #将它的值修改为"1:0:0"，这样将编译出*.so.1的动态库，与psqlodbcw.so的依赖关系相同。
+    vim configure
+
+    ./configure --enable-gui=no #如果要在鲲鹏服务器上编译，请追加一个configure参数:  --build=aarch64-unknown-linux-gnu
+    make
+    #安装可能需要root权限
+    make install
+    ```
+
+3. 替换客户端openGauss驱动程序。
+
+    a. 将openGauss-1.1.0-ODBC.tar.gz解压到"/usr/local/lib"目录下。解压会得  到"psqlodbcw.la"和"psqlodbcw.so"两个文件。
+
+    b. 将openGauss-1.1.0-ODBC.tar.gz解压后lib目录中的库拷贝到"/usr/local/lib"目录下。
+
+4. 配置数据源。
+
+    a. 配置ODBC驱动文件。
+
+    在`/xxx/odbc/etc/odbcinst.ini`文件中追加以下内容。
+
+    ```bash
+    [GaussMPP]
+    Driver64=/xxx/odbc/lib/psqlodbcw.so
+    setup=/xxx/odbc/lib/psqlodbcw.so
+    ```
+
+    odbcinst.ini文件中的配置参数说明如[表1](#odbcinst.ini)所示。
+
+    **表 1** odbcinst.ini文件配置参数<a id="odbcinst.ini"></a>
+
+    | **参数**     | **描述**                                     | **示例**                            |
+    | :----------- | :------------------------------------------- | :---------------------------------- |
+    | [DriverName] | 驱动器名称，对应数据源DSN中的驱动名。        | [DRIVER_N]                          |
+    | Driver64     | 驱动动态库的路径。                           | Driver64=/xxx/odbc/lib/psqlodbcw.so |
+    | setup        | 驱动安装路径，与Driver64中动态库的路径一致。 | setup=/xxx/odbc/lib/psqlodbcw.so    |
+
+    b. 配置数据源文件。
+
+    在`/usr/local/etc/odbc.ini`文件中追加以下内容。
+
+    ```bash
+    [MPPODBC]
+    Driver=GaussMPP
+    Servername=10.10.0.13（数据库Server IP）
+    Database=postgres  （数据库名）
+    Username=omm  （数据库用户名）
+    Password=  （数据库用户密码）
+    Port=8000 （数据库侦听端口）
+    Sslmode=allow
+    ```
+
+    odbc.ini文件配置参数说明如[表2](#odbc.ini)所示。
+
+    **表 2** odbc.ini文件配置参数<a id="odbc.ini"></a>
+
+    | **参数**             | **描述**    | **示例**                        |
+    | :------------------- | :------------------ |--------------------|
+    | [DSN]                | 数据源的名称。                                | [MPPODBC]|
+    | Driver               | 驱动名，对应odbcinst.ini中的DriverName。      | Driver=DRIVER_N|
+    | Servername           | 服务器的IP地址。                              | Servername=10.145.130.26|
+    | Database             | 要连接的数据库的名称。                        | Database=postgres               |
+    | Username             | 数据库用户名称。                              | Username=omm  |
+    | Password             | 数据库用户密码。                              | Password=<br />说明:<br />ODBC驱动本身已经对内存密码进行过清理，以保证用户密码在连接后不会再在内存中保留。<br />但是如果配置了此参数，由于UnixODBC对数据源文件等进行缓存，可能导致密码长期保留在内存中。<br />推荐在应用程序连接时，将密码传递给相应API，而非写在数据源配置文件中。同时连接成功后，应当及时清理保存密码的内存段。 |
+    | Port                 | 服务器的端口号。                              | Port=8000     |
+    | Sslmode              | 开启SSL模式                                   | Sslmode=allow |
+    | Debug | 设置为1时，将会打印psqlodbc驱动的mylog，日志生成目录为/tmp/。设置为0时则不会生成。 | Debug=1 |
+    | UseServerSidePrepare | 是否开启数据库端扩展查询协议。<br />可选值0或1，默认为1，表示打开扩展查询协议。                                   | UseServerSidePrepare=1          |
+    | UseBatchProtocol     | 是否开启批量查询协议（打开可提高DML性能）；可选值0或者1，默认为1。<br />当此值为0时，不使用批量查询协议（主要用于与早期数据库版本通信兼容）。<br />当此值为1，并且数据库support_batch_bind参数存在且为on时，将打开批量查询协议。 | UseBatchProtocol=1              |
+    | ForExtensionConnector | 这个开关控制着savepoint是否发送，savepoint相关问题可以注意这个开关。 | ForExtensionConnector=1 |
+    | UnamedPrepStmtThreshold | 每次调用SQLFreeHandle释放Stmt时，ODBC都会向server端发送一个Deallocate plan_name语句，业务中存在大量这类语句。为了减少这类语句的发送，我们将 stmt->plan_name置空，从而使得数据库识别这个为unamed stmt。增加这个参数对unamed stmt的阈值进行控制。 | UnamedPrepStmtThreshold=100 |
+    | ConnectionExtraInfo  | GUC参数connection_info（参见connection_info）中显示驱动部署路径和进程属主用户的开关。                             | ConnectionExtraInfo=1<br />说明:<br />默认值为0。当设置为1时，ODBC驱动会将当前驱动的部署路径、进程属主用户上报到数据库中，记录在connection_info参数（参见connection_info）里；同时可以在PG_STAT_ACTIVITY中查询到。 |
+    | BoolAsChar | 设置为Yes是，Bools值将会映射为SQL_CHAR。如不设置将会映射为SQL_BIT。 | BoolsAsChar = Yes |
+    | RowVersioning | 当尝试更新一行数据时，设置为Yes会允许应用检测数据有没有被其他用户进行修改。 | RowVersioning=Yes |
+    | ShowSystemTables | 驱动将会默认系统表格为普通SQL表格。 | ShowSystemTables=Yes |
+
+    其中关于Sslmode的选项的允许值，具体信息见下表:
+
+    **表 3** Sslmode的可选项及其描述<a id="sslmode"> </a>
+
+    | sslmode     | 是否会启用SSL加密 | 描述   |
+    | :---------- | :---------------- | :------------------------------ |
+    | disable     | 否           | 不使用SSL安全连接。|
+    | allow  | 可能    | 如果数据库服务器要求使用，则可以使用SSL安全加密连接，但不验证数据库服务器的真实性。|
+    | prefer | 可能    | 如果数据库支持，那么建议使用SSL安全加密连接，但不验证数据库服务器的真实性。   |
+    | require| 是 | 必须使用SSL安全连接，但是只做了数据加密，而并不验证数据库服务器的真实性。|
+    | verify-ca   | 是 | 必须使用SSL安全连接，并且验证数据库是否具有可信证书机构签发的证书。 |
+    | verify-full | 是 | 必须使用SSL安全连接，在verify-ca的验证范围之外，同时验证数据库所在主机的主机名是否与证书内容一致。MogDB不支持此模式。 |
+
+5. （可选）生成SSL证书。此步骤和[6](#6)在服务端与客户端通过ssl方式连接的情况下需要执行。非ssl方式连接情况下可以跳过。
+
+6. （可选）替换SSL证书，具体请参见"证书替换"。<a id="6"> </a>
+
+7. SSL模式：
+
+    ```
+    退回根目录，创建.postgresql目录，并将root.crt，client.crt，client.key，client.key.cipher，client.key.rand，client.req，server.crt，server.key，server.key.cipher，server.key.rand，server.req放在此路径下。
+    将root.crt以及server开头的证书相关文件全部拷贝进数据库install/data目录下（与postgresql.conf文件在同一路径）。
+    修改postgresql.conf文件：
+        ssl = on
+        ssl_cert_file = 'server.crt'
+        ssl_key_file = 'server.key'
+        ssl_ca_file = 'root.crt'
+    修改完参数后需重启数据库。
+    修改配置文件odbc.ini中的sslmode参数（require或verify-ca）。
+    ```
+
+8. 配置数据库服务器。<a id="8"></a>
+
+    a. 以操作系统用户omm登录数据库主节点。
+
+    b. 执行如下命令增加对外提供服务的网卡IP或者主机名（英文逗号分隔），其中NodeName为当前节点名称:
+
+    ```bash
+    gs_guc reload -N NodeName -I all -c "listen_addresses='localhost,192.168.0.100,10.11.12.13'"
+    ```
+
+    在DR（Direct Routing，LVS的直接路由DR模式）模式中需要将虚拟IP地址（10.11.12.13）加入到服务器的侦听地址列表中。
+
+    listen_addresses也可以配置为"\*"或"0.0.0.0"，此配置下将侦听所有网卡，但存在安全风险，不推荐用户使用，推荐用户按照需要配置IP或者主机名，打开侦听。
+
+    c. 执行如下命令在数据库主节点配置文件中增加一条认证规则。（这里假设客户端IP地址为10.11.12.13，即远程连接的机器的IP地址）
+
+    ```bash
+    gs_guc reload -N all -I all -h "host all jack 10.11.12.13/32 sha256"
+    ```
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+    >
+    > - -N all表示MogDB中的所有主机。
+    > - -I all表示主机中的所有实例。
+    > - -h表示指定需要在"pg_hba.conf"增加的语句。
+    > - all表示允许客户端连接到任意的数据库。
+    > - jack表示连接数据库的用户。
+    > - 10.11.12.13/32表示只允许IP地址为10.11.12.13的主机连接。在使用过程中，请根据用户的网络进行配置修改。32表示子网掩码为1的位数，即255.255.255.255
+    > - sha256表示连接时jack用户的密码使用sha256算法加密。
+
+    如果将ODBC客户端配置在和要连接的数据库主节点在同一台机器上，则可使用local trust认证方式，如下:
+
+    ```bash
+    local all all trust
+    ```
+
+    如果将ODBC客户端配置在和要连接的数据库主节点在不同机器上，则需要使用sha256认证方式，如下:
+
+    ```bash
+    host all all xxx.xxx.xxx.xxx/32 sha256
+    ```
+
+    d. 重启MogDB。
+
+    ```bash
+    gs_om -t stop
+    gs_om -t start
+    ```
+
+9. 在客户端配置环境变量。
+
+   ```
+   vim ~/.bashrc
+   ```
+
+   在配置文件中追加以下内容。
+
+   ```
+   export LD_LIBRARY_PATH=/usr/local/lib/:$LD_LIBRARY_PATH
+   export ODBCSYSINI=/usr/local/etc
+   export ODBCINI=/usr/local/etc/odbc.ini
+   ```
+
+10. 执行如下命令使设置生效。
+
+    ```
+    source ~/.bashrc
+    ```
+
+    <br/>
+
+## 测试数据源配置
+
+执行./isql -v MPPODBC（数据源名称）命令。
+
+- 如果显示如下信息，表明配置正确，连接成功。
+
+    ```bash
+    +---------------------------------------+
+    | Connected!                            |
+    |                                       |
+    | sql-statement                         |
+    | help [tablename]                      |
+    | quit                                  |
+    |                                       |
+    +---------------------------------------+
+    SQL>
+    ```
+
+- 若显示ERROR信息，则表明配置错误。请检查上述配置是否正确。
+
+<br/>
+
+## 常见问题处理
+
+- [UnixODBC]Can't open lib 'xxx/xxx/psqlodbcw.so' : file not found.
+
+    此问题的可能原因:
+
+  - odbcinst.ini文件中配置的路径不正确
+
+    确认的方法: 'ls'一下错误信息中的路径，以确保该psqlodbcw.so文件存在，同时具有执行权限。
+
+  - psqlodbcw.so的依赖库不存在，或者不在系统环境变量中
+
+    确认的办法: ldd一下错误信息中的路径，如果是缺少libodbc.so.1等UnixODBC的库，那么按照"操作步骤"中的方法重新配置UnixODBC，并确保它的安装路径下的lib目录添加到了LD_LIBRARY_PATH中；如果是缺少其他库，请将ODBC驱动包中的lib目录添加到LD_LIBRARY_PATH中。
+
+- [UnixODBC]connect to server failed: no such file or directory
+
+    此问题可能的原因:
+
+  - 配置了错误的/不可达的数据库地址，或者端口
+
+    请检查数据源配置中的Servername及Port配置项。
+
+  - 服务器侦听不正确
+
+    如果确认Servername及Port配置正确，请根据"操作步骤"中数据库服务器的相关配置，确保数据库侦听了合适的网卡及端口。
+
+  - 防火墙及网闸设备
+
+    请确认防火墙设置，将数据库的通信端口添加到可信端口中。
+
+    如果有网闸设备，请确认一下相关的设置。
+
+- [unixODBC]The password-stored method is not supported.
+
+    此问题可能原因:
+
+    数据源中未配置sslmode配置项。
+
+    解决办法:
+
+    请配置该选项至allow或以上选项。此配置的更多信息，见[表3](#sslmode)。
+
+- Server common name "xxxx" does not match host name "xxxxx"
+
+    此问题的原因:
+
+    使用了SSL加密的"verify-full"选项，驱动程序会验证证书中的主机名与实际部署数据库的主机名是否一致。
+
+    解决办法:
+
+    碰到此问题可以使用"verify-ca"选项，不再校验主机名；或者重新生成一套与数据库所在主机名相同的CA证书。
+
+- Driver's SQLAllocHandle on SQL_HANDLE_DBC failed
+
+    此问题的可能原因:
+
+    可执行文件（比如UnixODBC的isql，以下都以isql为例）与数据库驱动（psqlodbcw.so）依赖于不同的odbc的库版本: libodbc.so.1或者libodbc.so.2。此问题可以通过如下方式确认:
+
+    ```bash
+    ldd `which isql` | grep odbc
+    ldd psqlodbcw.so | grep odbc
+    ```
+
+    这时，如果输出的libodbc.so最后的后缀数字不同或者指向不同的磁盘物理文件，那么基本就可以断定是此问题。isql与psqlodbcw.so都会要求加载libodbc.so，这时如果它们加载的是不同的物理文件，便会导致两套完全同名的函数列表，同时出现在同一个可见域里（UnixODBC的libodbc.so.\*的函数导出列表完全一致），产生冲突，无法加载数据库驱动。
+
+    解决办法:
+
+    确定一个要使用的UnixODBC，然后卸载另外一个（比如卸载库版本号为.so.2的UnixODBC），然后将剩下的.so.1的库，新建一个同名但是后缀为.so.2的软链接，便可解决此问题。
+
+- FATAL: Forbid remote connection with trust method!
+
+    由于安全原因，数据库主节点禁止MogDB内部其他节点无认证接入。
+
+    如果要在MogDB内部访问数据库主节点，请将ODBC程序部署在数据库主节点所在机器，服务器地址使用"127.0.0.1"。建议业务系统单独部署在MogDB外部，否则可能会影响数据库运行性能。
+
+- [unixODBC]Invalid attribute value
+
+    有可能是unixODBC的版本并非推荐版本，建议通过"odbcinst -version"命令排查环境中的unixODBC版本。
+
+- authentication method 10 not supported.
+
+    使用开源客户端碰到此问题，可能原因:
+
+    数据库中存储的口令校验只存储了SHA256格式哈希，而开源客户端只识别MD5校验，双方校验方法不匹配报错。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+    >
+    > - 数据库并不存储用户口令，只存储用户口令的哈希码。
+    > - 数据库当用户更新用户口令或者新建用户时，会同时存储两种格式的哈希码，这时将兼容开源的认证协议。
+    > - 但是当老版本升级到新版本时，由于哈希的不可逆性，所以数据库无法还原用户口令，进而生成新格式的哈希，所以仍然只保留了SHA256格式的哈希，导致仍然无法使用MD5做口令认证。
+    > - MD5加密算法安全性低，存在安全风险，建议使用更安全的加密算法。
+
+    要解决该问题，可以更新用户口令（参见[ALTER USER](29-ALTER-USER)）；或者新建一个用户（参见CREATE USER），赋于同等权限，使用新用户连接数据库。
+
+- unsupported frontend protocol 3.51: server supports 1.0 to 3.0
+
+    目标数据库版本过低，或者目标数据库为开源数据库。请使用对应版本的数据库驱动连接目标数据库。
+
+- FATAL: GSS authentication method is not allowed because XXXX user password is not disabled.
+
+    目标数据库主节点的pg_hba.conf里配置了当前客户端IP使用"gss"方式来做认证，该认证算法不支持用作客户端的身份认证，请修改到"sha256"后再试。配置方法见[8](#8)。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/4-development-process.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/4-development-process.md
new file mode 100644
index 0000000000000000000000000000000000000000..dbea0e1781f7de49192c603939b7f86c04be07cb
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/4-development-process.md
@@ -0,0 +1,40 @@
+---
+title: 开发流程
+summary: 开发流程
+author: Guo Huan
+date: 2021-04-26
+---
+
+# 开发流程
+
+**图 1** ODBC开发应用程序的流程
+
+![ODBC开发应用程序的流程](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/development-process-3.png)
+
+<br/>
+
+## 开发流程中涉及的API
+
+**表 1** 相关API说明
+
+| **功能**                      | **API**                                                                                                                                                |
+| :---------------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 申请句柄资源                  | SQLAllocHandle: 申请句柄资源，可替代如下函数: <br />- SQLAllocEnv: 申请环境句柄<br />- SQLAllocConnect: 申请连接句柄<br />- SQLAllocStmt: 申请语句句柄 |
+| 设置环境属性                  | SQLSetEnvAttr                                                                                                                                          |
+| 设置连接属性                  | SQLSetConnectAttr                                                                                                                                      |
+| 设置语句属性                  | SQLSetStmtAttr                                                                                                                                         |
+| 连接数据源                    | SQLConnect                                                                                                                                             |
+| 绑定缓冲区到结果集的列中      | SQLBindCol                                                                                                                                             |
+| 绑定SQL语句的参数标志和缓冲区 | SQLBindParameter                                                                                                                                       |
+| 查看最近一次操作错误信息      | SQLGetDiagRec                                                                                                                                          |
+| 为执行SQL语句做准备           | SQLPrepare                                                                                                                                             |
+| 执行一条准备好的SQL语句       | SQLExecute                                                                                                                                             |
+| 直接执行SQL语句               | SQLExecDirect                                                                                                                                          |
+| 结果集中取行集                | SQLFetch                                                                                                                                               |
+| 返回结果集中某一列的数据      | SQLGetData                                                                                                                                             |
+| 获取结果集中列的描述信息      | SQLColAttribute                                                                                                                                        |
+| 断开与数据源的连接            | SQLDisconnect                                                                                                                                          |
+| 释放句柄资源                  | SQLFreeHandle: 释放句柄资源，可替代如下函数: <br />- SQLFreeEnv: 释放环境句柄<br />- SQLFreeConnect: 释放连接句柄<br />- SQLFreeStmt: 释放语句句柄     |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+> 数据库中收到的一次执行请求（不在事务块中），如果含有多条语句，将会被打包成一个事务，同时如果其中有一个语句失败，那么整个请求都将会被回滚。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/5-example-common-functions-and-batch-binding.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/5-example-common-functions-and-batch-binding.md
new file mode 100644
index 0000000000000000000000000000000000000000..43acf678a6142481fb20fdfea90f204d899a4c46
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/5-example-common-functions-and-batch-binding.md
@@ -0,0 +1,440 @@
+---
+title: 常用功能和批量绑定
+summary: 常用功能和批量绑定
+author: Guo Huan
+date: 2021-04-26
+---
+
+# 示例：常用功能和批量绑定
+
+## 常用功能示例代码
+
+```
+// 此示例演示如何通过ODBC方式获取openGauss中的数据。
+// DBtest.c (compile with: libodbc.so)   
+#include <stdlib.h> 
+#include <stdio.h> 
+#include <sqlext.h>
+#ifdef WIN32
+#include <windows.h>
+#endif 
+SQLHENV       V_OD_Env;        // Handle ODBC environment 
+SQLHSTMT      V_OD_hstmt;      // Handle statement 
+SQLHDBC       V_OD_hdbc;       // Handle connection     
+char          typename[100];
+SQLINTEGER    value = 100;
+SQLINTEGER    V_OD_erg,V_OD_buffer,V_OD_err,V_OD_id;
+int main(int argc,char *argv[]) 
+{         
+      // 1. 申请环境句柄       
+      V_OD_erg = SQLAllocHandle(SQL_HANDLE_ENV,SQL_NULL_HANDLE,&V_OD_Env);     
+      if ((V_OD_erg != SQL_SUCCESS) && (V_OD_erg != SQL_SUCCESS_WITH_INFO))        
+      {           
+           printf("Error AllocHandle\n");           
+           exit(0);        
+      } 
+      // 2. 设置环境属性（版本信息）         
+      SQLSetEnvAttr(V_OD_Env, SQL_ATTR_ODBC_VERSION, (void*)SQL_OV_ODBC3, 0);      
+      // 3. 申请连接句柄        
+      V_OD_erg = SQLAllocHandle(SQL_HANDLE_DBC, V_OD_Env, &V_OD_hdbc);     
+      if ((V_OD_erg != SQL_SUCCESS) && (V_OD_erg != SQL_SUCCESS_WITH_INFO))      
+      {                     
+           SQLFreeHandle(SQL_HANDLE_ENV, V_OD_Env);          
+           exit(0);       
+      }
+      // 4. 设置连接属性
+      SQLSetConnectAttr(V_OD_hdbc, SQL_ATTR_AUTOCOMMIT, SQL_AUTOCOMMIT_ON, 0);          
+      // 5. 连接数据源，这里的“userName”与“password”分别表示连接数据库的用户名和用户密码，请根据实际情况修改。
+      // 如果odbc.ini文件中已经配置了用户名密码，那么这里可以留空（""）；但是不建议这么做，因为一旦odbc.ini权限管理不善，将导致数据库用户密码泄露。    
+      V_OD_erg = SQLConnect(V_OD_hdbc, (SQLCHAR*) "gaussdb", SQL_NTS,  
+                           (SQLCHAR*) "userName", SQL_NTS,  (SQLCHAR*) "password", SQL_NTS);        
+      if ((V_OD_erg != SQL_SUCCESS) && (V_OD_erg != SQL_SUCCESS_WITH_INFO))      
+      {           
+          printf("Error SQLConnect %d\n",V_OD_erg);            
+          SQLFreeHandle(SQL_HANDLE_ENV, V_OD_Env);       
+          exit(0);        
+      }     
+      printf("Connected !\n"); 
+      // 6. 设置语句属性
+      SQLSetStmtAttr(V_OD_hstmt,SQL_ATTR_QUERY_TIMEOUT,(SQLPOINTER *)3,0);
+      // 7. 申请语句句柄
+      SQLAllocHandle(SQL_HANDLE_STMT, V_OD_hdbc, &V_OD_hstmt);       
+      // 8. 直接执行SQL语句。
+      SQLExecDirect(V_OD_hstmt,"drop table IF EXISTS customer_t1",SQL_NTS);
+      SQLExecDirect(V_OD_hstmt,"CREATE TABLE customer_t1(c_customer_sk INTEGER, c_customer_name VARCHAR(32));",SQL_NTS);
+      SQLExecDirect(V_OD_hstmt,"insert into customer_t1 values(25,li)",SQL_NTS);
+      // 9. 准备执行
+      SQLPrepare(V_OD_hstmt,"insert into customer_t1 values(?)",SQL_NTS); 
+      // 10. 绑定参数
+      SQLBindParameter(V_OD_hstmt,1,SQL_PARAM_INPUT,SQL_C_SLONG,SQL_INTEGER,0,0,
+                       &value,0,NULL);
+      // 11. 执行准备好的语句
+      SQLExecute(V_OD_hstmt);
+      SQLExecDirect(V_OD_hstmt,"select id from testtable",SQL_NTS);
+      // 12. 获取结果集某一列的属性
+      SQLColAttribute(V_OD_hstmt,1,SQL_DESC_TYPE,typename,100,NULL,NULL);                 
+      printf("SQLColAtrribute %s\n",typename);
+      // 13. 绑定结果集
+      SQLBindCol(V_OD_hstmt,1,SQL_C_SLONG, (SQLPOINTER)&V_OD_buffer,150,
+                (SQLLEN *)&V_OD_err);
+      // 14. 通过SQLFetch取结果集中数据
+      V_OD_erg=SQLFetch(V_OD_hstmt);
+      // 15. 通过SQLGetData获取并返回数据。
+      while(V_OD_erg != SQL_NO_DATA)
+      {
+          SQLGetData(V_OD_hstmt,1,SQL_C_SLONG,(SQLPOINTER)&V_OD_id,0,NULL);
+          printf("SQLGetData ----ID = %d\n",V_OD_id);
+          V_OD_erg=SQLFetch(V_OD_hstmt);
+      };
+      printf("Done !\n");
+      // 16. 断开数据源连接并释放句柄资源
+      SQLFreeHandle(SQL_HANDLE_STMT,V_OD_hstmt);    
+      SQLDisconnect(V_OD_hdbc);         
+      SQLFreeHandle(SQL_HANDLE_DBC,V_OD_hdbc);       
+      SQLFreeHandle(SQL_HANDLE_ENV, V_OD_Env);  
+      return(0);
+ }
+```
+
+## 批量绑定示例代码
+
+```
+/**********************************************************************
+* 请在数据源中打开UseBatchProtocol，同时指定数据库中参数support_batch_bind
+* 为on
+* CHECK_ERROR的作用是检查并打印错误信息。
+* 此示例将与用户交互式获取DSN、模拟的数据量，忽略的数据量，并将最终数据入库到test_odbc_batch_insert中
+***********************************************************************/
+#include <stdio.h>
+#include <stdlib.h>
+#include <sql.h>
+#include <sqlext.h>
+#include <string.h>
+
+void Exec(SQLHDBC hdbc, SQLCHAR* sql)
+{
+    SQLRETURN retcode;                  // Return status
+    SQLHSTMT hstmt = SQL_NULL_HSTMT;    // Statement handle
+    SQLCHAR     loginfo[2048];
+
+    // Allocate Statement Handle
+    retcode = SQLAllocHandle(SQL_HANDLE_STMT, hdbc, &hstmt);
+    
+    if (!SQL_SUCCEEDED(retcode)) {
+        printf("SQLAllocHandle(SQL_HANDLE_STMT) failed");
+        return;
+    }
+
+    // Prepare Statement
+    retcode = SQLPrepare(hstmt, (SQLCHAR*) sql, SQL_NTS);
+    sprintf((char*)loginfo, "SQLPrepare log: %s", (char*)sql);
+    
+    if (!SQL_SUCCEEDED(retcode)) {
+        printf("SQLPrepare(hstmt, (SQLCHAR*) sql, SQL_NTS) failed");
+        return;
+    }
+
+    // Execute Statement
+    retcode = SQLExecute(hstmt);
+    sprintf((char*)loginfo, "SQLExecute stmt log: %s", (char*)sql);
+    
+    if (!SQL_SUCCEEDED(retcode)) {
+        printf("SQLExecute(hstmt) failed");
+        return;
+    }
+    // Free Handle
+    retcode = SQLFreeHandle(SQL_HANDLE_STMT, hstmt);
+    sprintf((char*)loginfo, "SQLFreeHandle stmt log: %s", (char*)sql);
+    
+    if (!SQL_SUCCEEDED(retcode)) {
+        printf("SQLFreeHandle(SQL_HANDLE_STMT, hstmt) failed");
+        return;
+    }
+}
+
+int main () 
+{
+    SQLHENV  henv  = SQL_NULL_HENV;
+    SQLHDBC  hdbc  = SQL_NULL_HDBC; 
+    int      batchCount = 1000; // 批量绑定的数据量
+    SQLLEN   rowsCount = 0;
+    int      ignoreCount = 0; // 批量绑定的数据中，不要入库的数据量
+
+    SQLRETURN   retcode;
+    SQLCHAR     dsn[1024] = {'\0'};
+    SQLCHAR     loginfo[2048];
+
+    do 
+    {
+        if (ignoreCount > batchCount)
+        {
+            printf("ignoreCount(%d) should be less than batchCount(%d)\n", ignoreCount, batchCount);
+        }
+    }while(ignoreCount > batchCount);
+
+    retcode = SQLAllocHandle(SQL_HANDLE_ENV, SQL_NULL_HANDLE, &henv);
+    
+    if (!SQL_SUCCEEDED(retcode)) {
+        printf("SQLAllocHandle failed");
+        goto exit;
+    }
+
+    // Set ODBC Verion
+    retcode = SQLSetEnvAttr(henv, SQL_ATTR_ODBC_VERSION,
+                                        (SQLPOINTER*)SQL_OV_ODBC3, 0);
+    
+    if (!SQL_SUCCEEDED(retcode)) {
+        printf("SQLSetEnvAttr failed");
+        goto exit;
+    }
+
+    // Allocate Connection
+    retcode = SQLAllocHandle(SQL_HANDLE_DBC, henv, &hdbc);
+    
+    if (!SQL_SUCCEEDED(retcode)) {
+        printf("SQLAllocHandle failed");
+        goto exit;
+    }
+
+
+    // Set Login Timeout
+    retcode = SQLSetConnectAttr(hdbc, SQL_LOGIN_TIMEOUT, (SQLPOINTER)5, 0);
+    
+    if (!SQL_SUCCEEDED(retcode)) {
+        printf("SQLSetConnectAttr failed");
+        goto exit;
+    }
+
+
+    // Set Auto Commit
+    retcode = SQLSetConnectAttr(hdbc, SQL_ATTR_AUTOCOMMIT,
+                                        (SQLPOINTER)(1), 0);
+    
+    if (!SQL_SUCCEEDED(retcode)) {
+        printf("SQLSetConnectAttr failed");
+        goto exit;
+    }
+
+
+    // Connect to DSN
+    // gaussdb替换成用户所使用的数据源名称
+    sprintf(loginfo, "SQLConnect(DSN:%s)", dsn);
+    retcode = SQLConnect(hdbc, (SQLCHAR*) "gaussdb", SQL_NTS,
+                               (SQLCHAR*) NULL, 0, NULL, 0);
+    
+    if (!SQL_SUCCEEDED(retcode)) {
+        printf("SQLConnect failed");
+        goto exit;
+    }
+
+    // init table info.
+    Exec(hdbc, "drop table if exists test_odbc_batch_insert");
+    Exec(hdbc, "create table test_odbc_batch_insert(id int primary key, col varchar2(50))");
+
+    // 下面的代码根据用户输入的数据量，构造出将要入库的数据:
+    {
+        SQLRETURN retcode; 
+        SQLHSTMT hstmtinesrt = SQL_NULL_HSTMT;
+        int          i;
+        SQLCHAR      *sql = NULL;
+        SQLINTEGER   *ids  = NULL;
+        SQLCHAR      *cols = NULL;
+        SQLLEN       *bufLenIds = NULL;
+        SQLLEN       *bufLenCols = NULL;
+        SQLUSMALLINT *operptr = NULL;
+        SQLUSMALLINT *statusptr = NULL;
+        SQLULEN      process = 0;
+
+        // 这里是按列构造，每个字段的内存连续存放在一起。
+        ids = (SQLINTEGER*)malloc(sizeof(ids[0]) * batchCount);
+        cols = (SQLCHAR*)malloc(sizeof(cols[0]) * batchCount * 50);
+        // 这里是每个字段中，每一行数据的内存长度。
+        bufLenIds = (SQLLEN*)malloc(sizeof(bufLenIds[0]) * batchCount);
+        bufLenCols = (SQLLEN*)malloc(sizeof(bufLenCols[0]) * batchCount);
+        // 该行是否需要被处理，SQL_PARAM_IGNORE 或 SQL_PARAM_PROCEED
+        operptr = (SQLUSMALLINT*)malloc(sizeof(operptr[0]) * batchCount);
+        memset(operptr, 0, sizeof(operptr[0]) * batchCount);
+        // 该行的处理结果。
+        // 注：由于数据库中处理方式是同一语句隶属同一事务中，所以如果出错，那么待处理数据都将是出错的，并不会部分入库。
+        statusptr = (SQLUSMALLINT*)malloc(sizeof(statusptr[0]) * batchCount);
+        memset(statusptr, 88, sizeof(statusptr[0]) * batchCount);
+
+        if (NULL == ids || NULL == cols || NULL == bufLenCols || NULL == bufLenIds)
+        {
+            fprintf(stderr, "FAILED:\tmalloc data memory failed\n");
+            goto exit;
+        }
+
+        for (int i = 0; i < batchCount; i++)
+        {
+            ids[i] = i;
+            sprintf(cols + 50 * i, "column test value %d", i);
+            bufLenIds[i] = sizeof(ids[i]);
+            bufLenCols[i] = strlen(cols + 50 * i);
+            operptr[i] = (i < ignoreCount) ? SQL_PARAM_IGNORE : SQL_PARAM_PROCEED;
+        }
+
+        // Allocate Statement Handle
+        retcode = SQLAllocHandle(SQL_HANDLE_STMT, hdbc, &hstmtinesrt);
+        
+        if (!SQL_SUCCEEDED(retcode)) {
+            printf("SQLAllocHandle failed");
+            goto exit;
+        }
+
+        // Prepare Statement
+        sql = (SQLCHAR*)"insert into test_odbc_batch_insert values(?, ?)";
+        retcode = SQLPrepare(hstmtinesrt, (SQLCHAR*) sql, SQL_NTS);
+        sprintf((char*)loginfo, "SQLPrepare log: %s", (char*)sql);
+        
+        if (!SQL_SUCCEEDED(retcode)) {
+            printf("SQLPrepare failed");
+            goto exit;
+        }
+
+        retcode = SQLSetStmtAttr(hstmtinesrt, SQL_ATTR_PARAMSET_SIZE, (SQLPOINTER)batchCount, sizeof(batchCount));
+        
+        if (!SQL_SUCCEEDED(retcode)) {
+            printf("SQLSetStmtAttr failed");
+            goto exit;
+        }
+
+        retcode = SQLBindParameter(hstmtinesrt, 1, SQL_PARAM_INPUT, SQL_C_SLONG, SQL_INTEGER, sizeof(ids[0]), 0,&(ids[0]), 0, bufLenIds);
+        
+        if (!SQL_SUCCEEDED(retcode)) {
+            printf("SQLBindParameter failed");
+            goto exit;
+        }
+
+        retcode = SQLBindParameter(hstmtinesrt, 2, SQL_PARAM_INPUT, SQL_C_CHAR, SQL_CHAR, 50, 50, cols, 50, bufLenCols);
+        
+        if (!SQL_SUCCEEDED(retcode)) {
+            printf("SQLBindParameter failed");
+            goto exit;
+        }
+
+        retcode = SQLSetStmtAttr(hstmtinesrt, SQL_ATTR_PARAMS_PROCESSED_PTR, (SQLPOINTER)&process, sizeof(process));
+        
+        if (!SQL_SUCCEEDED(retcode)) {
+            printf("SQLSetStmtAttr failed");
+            goto exit;
+        }
+
+        retcode = SQLSetStmtAttr(hstmtinesrt, SQL_ATTR_PARAM_STATUS_PTR, (SQLPOINTER)statusptr, sizeof(statusptr[0]) * batchCount);
+        
+        if (!SQL_SUCCEEDED(retcode)) {
+            printf("SQLSetStmtAttr failed");
+            goto exit;
+        }
+
+        retcode = SQLSetStmtAttr(hstmtinesrt, SQL_ATTR_PARAM_OPERATION_PTR, (SQLPOINTER)operptr, sizeof(operptr[0]) * batchCount);
+        
+        if (!SQL_SUCCEEDED(retcode)) {
+            printf("SQLSetStmtAttr failed");
+            goto exit;
+        }
+
+        retcode = SQLExecute(hstmtinesrt);
+        sprintf((char*)loginfo, "SQLExecute stmt log: %s", (char*)sql);
+        
+        if (!SQL_SUCCEEDED(retcode)) {
+            printf("SQLExecute(hstmtinesrt) failed");
+            goto exit;
+
+        retcode = SQLRowCount(hstmtinesrt, &rowsCount);
+        
+        if (!SQL_SUCCEEDED(retcode)) {
+            printf("SQLRowCount failed");
+            goto exit;
+        }
+
+        if (rowsCount != (batchCount - ignoreCount))
+        {
+            sprintf(loginfo, "(batchCount - ignoreCount)(%d) != rowsCount(%d)", (batchCount - ignoreCount), rowsCount);
+            
+            if (!SQL_SUCCEEDED(retcode)) {
+                printf("SQLExecute failed");
+                goto exit;
+            }
+        }
+        else
+        {
+            sprintf(loginfo, "(batchCount - ignoreCount)(%d) == rowsCount(%d)", (batchCount - ignoreCount), rowsCount);
+            
+            if (!SQL_SUCCEEDED(retcode)) {
+                printf("SQLExecute failed");
+                goto exit;
+            }
+        }
+
+        // check row number returned
+        if (rowsCount != process)
+        {
+            sprintf(loginfo, "process(%d) != rowsCount(%d)", process, rowsCount);
+            
+            if (!SQL_SUCCEEDED(retcode)) {
+                printf("SQLExecute failed");
+                goto exit;
+            }
+        }
+        else
+        {
+            sprintf(loginfo, "process(%d) == rowsCount(%d)", process, rowsCount);
+            
+            if (!SQL_SUCCEEDED(retcode)) {
+                printf("SQLExecute failed");
+                goto exit;
+            }
+        }
+
+        for (int i = 0; i < batchCount; i++)
+        {
+            if (i < ignoreCount)
+            {
+                if (statusptr[i] != SQL_PARAM_UNUSED)
+                {
+                    sprintf(loginfo, "statusptr[%d](%d) != SQL_PARAM_UNUSED", i, statusptr[i]);
+                    
+                    if (!SQL_SUCCEEDED(retcode)) {
+                        printf("SQLExecute failed");
+                        goto exit;
+                    }
+                }
+            }
+            else if (statusptr[i] != SQL_PARAM_SUCCESS)
+            {
+                sprintf(loginfo, "statusptr[%d](%d) != SQL_PARAM_SUCCESS", i, statusptr[i]);
+                
+                if (!SQL_SUCCEEDED(retcode)) {
+                    printf("SQLExecute failed");
+                    goto exit;
+                }
+            }
+        }
+
+        retcode = SQLFreeHandle(SQL_HANDLE_STMT, hstmtinesrt);
+        sprintf((char*)loginfo, "SQLFreeHandle hstmtinesrt");
+        
+        if (!SQL_SUCCEEDED(retcode)) {
+            printf("SQLFreeHandle failed");
+            goto exit;
+        }
+    }
+
+
+exit:
+    (void) printf ("\nComplete.\n");
+
+    // Connection
+    if (hdbc != SQL_NULL_HDBC) {
+        SQLDisconnect(hdbc);
+        SQLFreeHandle(SQL_HANDLE_DBC, hdbc);
+    }
+
+    // Environment
+    if (henv != SQL_NULL_HENV)
+        SQLFreeHandle(SQL_HANDLE_ENV, henv);
+
+    return 0;
+}
+```
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/5.1-typical-application-scenarios-and-configurations.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/5.1-typical-application-scenarios-and-configurations.md
new file mode 100644
index 0000000000000000000000000000000000000000..07c3729b3f0667402b1dde5dfd87f4c6dfbcd651
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/5.1-typical-application-scenarios-and-configurations.md
@@ -0,0 +1,496 @@
+---
+title: 典型应用场景配置
+summary: 典型应用场景配置
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# 典型应用场景配置
+
+## 日志诊断场景
+
+ODBC日志分为unixODBC驱动管理器日志和psqlODBC驱动端日志。前者可以用于追溯应用程序API的执行是否成功，后者是底层实现过程中的一些DFX日志，用来帮助定位问题。
+
+unixODBC日志需要在odbcinst.ini文件中配置：
+
+```bash
+[ODBC]
+Trace=Yes
+TraceFile=/path/to/odbctrace.log
+
+[GaussMPP]
+Driver64=/usr/local/lib/psqlodbcw.so
+setup=/usr/local/lib/psqlodbcw.so
+```
+
+psqlODBC日志只需要在odbc.ini加上：
+
+```bash
+[gaussdb]
+Driver=GaussMPP
+Servername=10.10.0.13（数据库Server IP）
+...
+Debug=1（打开驱动端debug日志）
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** unixODBC日志将会生成在TraceFile配置的路径下，psqlODBC会在系统/tmp/下生成mylog_xxx.log。
+
+## 高性能场景
+
+进行大量数据插入时，建议如下：
+
+- 需要设置批量绑定：odbc.ini配置文件中设置UseBatchProtocol=1、数据库设置support_batch_bind=on。
+- ODBC程序绑定类型要和数据库中类型一致。
+- 客户端字符集和数据库字符集一致。
+- 事务改成手动提交。
+
+odbc.ini配置文件：
+
+```bash
+[gaussdb]
+Driver=GaussMPP
+Servername=10.10.0.13（数据库Server IP）
+...
+UseBatchProtocol=1 （默认打开）
+ConnSettings=set client_encoding=UTF8 （设置客户端字符编码，保证和server端一致）
+```
+
+绑定类型用例：
+
+```c
+#include <stdio.h>
+#include <stdlib.h>
+#include <sql.h>
+#include <sqlext.h>
+#include <string.h>
+#include <sys/time.h>
+
+#define MESSAGE_BUFFER_LEN  128
+SQLHANDLE   h_env = NULL;
+SQLHANDLE   h_conn = NULL;
+SQLHANDLE   h_stmt = NULL;
+void print_error()
+{
+    SQLCHAR     Sqlstate[SQL_SQLSTATE_SIZE+1];
+    SQLINTEGER  NativeError;
+    SQLCHAR     MessageText[MESSAGE_BUFFER_LEN];
+    SQLSMALLINT TextLength;
+    SQLRETURN   ret = SQL_ERROR;
+
+    ret = SQLGetDiagRec(SQL_HANDLE_STMT, h_stmt, 1, Sqlstate, &NativeError, MessageText, MESSAGE_BUFFER_LEN, &TextLength);
+    if ( SQL_SUCCESS == ret)
+    {
+        printf("\n STMT ERROR-%05d %s", NativeError, MessageText);
+        return;
+    }
+
+    ret = SQLGetDiagRec(SQL_HANDLE_DBC, h_conn, 1, Sqlstate, &NativeError, MessageText, MESSAGE_BUFFER_LEN, &TextLength);
+    if ( SQL_SUCCESS == ret)
+    {
+        printf("\n CONN ERROR-%05d %s", NativeError, MessageText);
+        return;
+    }
+
+    ret = SQLGetDiagRec(SQL_HANDLE_ENV, h_env, 1, Sqlstate, &NativeError, MessageText, MESSAGE_BUFFER_LEN, &TextLength);
+    if ( SQL_SUCCESS == ret)
+    {
+        printf("\n ENV ERROR-%05d %s", NativeError, MessageText);
+        return;
+    }
+
+    return;
+}
+
+/* 期盼函数返回SQL_SUCCESS */
+#define RETURN_IF_NOT_SUCCESS(func) \
+{\
+    SQLRETURN ret_value = (func);\
+    if (SQL_SUCCESS != ret_value)\
+    {\
+        print_error();\
+        printf("\n failed line = %u: expect SQL_SUCCESS, but ret = %d", __LINE__, ret_value);\
+        return SQL_ERROR; \
+    }\
+}
+
+/* 期盼函数返回SQL_SUCCESS */
+#define RETURN_IF_NOT_SUCCESS_I(i, func) \
+{\
+    SQLRETURN ret_value = (func);\
+    if (SQL_SUCCESS != ret_value)\
+    {\
+        print_error();\
+        printf("\n failed line = %u (i=%d): : expect SQL_SUCCESS, but ret = %d", __LINE__, (i), ret_value);\
+        return SQL_ERROR; \
+    }\
+}
+
+/* 期盼函数返回SQL_SUCCESS_WITH_INFO */
+#define RETURN_IF_NOT_SUCCESS_INFO(func) \
+{\
+    SQLRETURN ret_value = (func);\
+    if (SQL_SUCCESS_WITH_INFO != ret_value)\
+    {\
+        print_error();\
+        printf("\n failed line = %u: expect SQL_SUCCESS_WITH_INFO, but ret = %d", __LINE__, ret_value);\
+        return SQL_ERROR; \
+    }\
+}
+
+/* 期盼数值相等 */
+#define RETURN_IF_NOT(expect, value) \
+if ((expect) != (value))\
+{\
+    printf("\n failed line = %u: expect = %u, but value = %u", __LINE__, (expect), (value)); \
+    return SQL_ERROR;\
+}
+
+/* 期盼字符串相同 */
+#define RETURN_IF_NOT_STRCMP_I(i, expect, value) \
+if (( NULL == (expect) ) || (NULL == (value)))\
+{\
+    printf("\n failed line = %u (i=%u): input NULL pointer !", __LINE__, (i)); \
+    return SQL_ERROR; \
+}\
+else if (0 != strcmp((expect), (value)))\
+{\
+    printf("\n failed line = %u (i=%u): expect = %s, but value = %s", __LINE__, (i), (expect), (value)); \
+    return SQL_ERROR;\
+}
+
+
+// prepare + execute SQL语句
+int execute_cmd(SQLCHAR *sql)
+{
+    if ( NULL == sql )
+    {
+        return SQL_ERROR;
+    }
+
+    if ( SQL_SUCCESS != SQLPrepare(h_stmt, sql, SQL_NTS))
+    {
+        return SQL_ERROR;
+    }
+
+    if ( SQL_SUCCESS != SQLExecute(h_stmt))
+    {
+        return SQL_ERROR;
+    }
+
+    return SQL_SUCCESS;
+}
+// execute + commit 句柄
+int commit_exec()
+{
+    if ( SQL_SUCCESS != SQLExecute(h_stmt))
+    {
+        return SQL_ERROR;
+    }
+
+    // 手动提交
+    if ( SQL_SUCCESS != SQLEndTran(SQL_HANDLE_DBC, h_conn, SQL_COMMIT))
+    {
+        return SQL_ERROR;
+    }
+
+    return SQL_SUCCESS;
+}
+
+int begin_unit_test()
+{
+    SQLINTEGER    ret;
+
+    /* 申请环境句柄 */
+    ret = SQLAllocHandle(SQL_HANDLE_ENV, SQL_NULL_HANDLE, &h_env);
+    if ((SQL_SUCCESS != ret) && (SQL_SUCCESS_WITH_INFO != ret))
+    {
+        printf("\n begin_unit_test::SQLAllocHandle SQL_HANDLE_ENV failed ! ret = %d", ret);
+        return SQL_ERROR;
+    }
+
+    /* 进行连接前必须要先设置版本号 */
+    if (SQL_SUCCESS != SQLSetEnvAttr(h_env, SQL_ATTR_ODBC_VERSION, (SQLPOINTER)SQL_OV_ODBC3, 0))
+    {
+        print_error();
+        printf("\n begin_unit_test::SQLSetEnvAttr SQL_ATTR_ODBC_VERSION failed ! ret = %d", ret);
+        SQLFreeHandle(SQL_HANDLE_ENV, h_env);
+        return SQL_ERROR;
+    }
+
+    /* 申请连接句柄 */
+    ret = SQLAllocHandle(SQL_HANDLE_DBC, h_env, &h_conn);
+    if (SQL_SUCCESS != ret)
+    {
+        print_error();
+        printf("\n begin_unit_test::SQLAllocHandle SQL_HANDLE_DBC failed ! ret = %d", ret);
+        SQLFreeHandle(SQL_HANDLE_ENV, h_env);
+        return SQL_ERROR;
+    }
+
+    /* 建立连接 */
+    ret = SQLConnect(h_conn, (SQLCHAR*) "gaussdb", SQL_NTS,
+                               (SQLCHAR*) NULL, 0, NULL, 0);
+    if (SQL_SUCCESS != ret)
+    {
+        print_error();
+        printf("\n begin_unit_test::SQLConnect  failed ! ret = %d", ret);
+        SQLFreeHandle(SQL_HANDLE_DBC, h_conn);
+        SQLFreeHandle(SQL_HANDLE_ENV, h_env);
+        return SQL_ERROR;
+    }
+
+    /* 申请语句句柄 */
+    ret = SQLAllocHandle(SQL_HANDLE_STMT, h_conn, &h_stmt);
+    if (SQL_SUCCESS != ret)
+    {
+        print_error();
+        printf("\n begin_unit_test::SQLAllocHandle SQL_HANDLE_STMT failed ! ret = %d", ret);
+        SQLFreeHandle(SQL_HANDLE_DBC, h_conn);
+        SQLFreeHandle(SQL_HANDLE_ENV, h_env);
+        return SQL_ERROR;
+    }
+
+    return SQL_SUCCESS;
+}
+
+void end_unit_test()
+{
+    /* 释放语句句柄 */
+    if (NULL != h_stmt)
+    {
+        SQLFreeHandle(SQL_HANDLE_STMT, h_stmt);
+    }
+
+    /* 释放连接句柄 */
+    if (NULL != h_conn)
+    {
+        SQLDisconnect(h_conn);
+        SQLFreeHandle(SQL_HANDLE_DBC, h_conn);
+    }
+
+    /* 释放环境句柄 */
+    if (NULL != h_env)
+    {
+        SQLFreeHandle(SQL_HANDLE_ENV, h_env);
+    }
+
+    return;
+}
+
+int main()
+{
+    // begin test
+    if (begin_unit_test() != SQL_SUCCESS)
+    {
+        printf("\n begin_test_unit failed.");
+        return SQL_ERROR;
+    }
+    // 句柄配置同前面用例
+    int         i = 0;
+    SQLCHAR*    sql_drop   = "drop table if exists test_bindnumber_001";
+    SQLCHAR*    sql_create = "create table test_bindnumber_001("
+                             "f4 number, f5 number(10, 2)"
+                             ")";
+    SQLCHAR*    sql_insert = "insert into test_bindnumber_001 values(?, ?)";
+    SQLCHAR*    sql_select = "select * from test_bindnumber_001";
+    SQLLEN      RowCount;
+    SQL_NUMERIC_STRUCT st_number;
+    SQLCHAR     getValue[2][MESSAGE_BUFFER_LEN];
+
+    /* step 1. 建表 */
+    RETURN_IF_NOT_SUCCESS(execute_cmd(sql_drop));
+    RETURN_IF_NOT_SUCCESS(execute_cmd(sql_create));
+
+    /* step 2.1 通过SQL_NUMERIC_STRUCT结构绑定参数 */
+    RETURN_IF_NOT_SUCCESS(SQLPrepare(h_stmt, sql_insert, SQL_NTS));
+
+    //第一行: 1234.5678
+    memset(st_number.val, 0, SQL_MAX_NUMERIC_LEN);
+    st_number.precision = 8;
+    st_number.scale = 4;
+    st_number.sign = 1;
+    st_number.val[0] = 0x4E;
+    st_number.val[1] = 0x61;
+    st_number.val[2] = 0xBC;
+
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 1, SQL_PARAM_INPUT, SQL_C_NUMERIC, SQL_NUMERIC, sizeof(SQL_NUMERIC_STRUCT), 4, &st_number, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 2, SQL_PARAM_INPUT, SQL_C_NUMERIC, SQL_NUMERIC, sizeof(SQL_NUMERIC_STRUCT), 4, &st_number, 0, NULL));
+
+    // 关闭自动提交
+    SQLSetConnectAttr(h_conn, SQL_ATTR_AUTOCOMMIT, (SQLPOINTER)SQL_AUTOCOMMIT_OFF, 0);
+
+    RETURN_IF_NOT_SUCCESS(commit_exec());
+    RETURN_IF_NOT_SUCCESS(SQLRowCount(h_stmt, &RowCount));
+    RETURN_IF_NOT(1, RowCount);
+
+    //第二行: 12345678
+    memset(st_number.val, 0, SQL_MAX_NUMERIC_LEN);
+    st_number.precision = 8;
+    st_number.scale = 0;
+    st_number.sign = 1;
+    st_number.val[0] = 0x4E;
+    st_number.val[1] = 0x61;
+    st_number.val[2] = 0xBC;
+
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 1, SQL_PARAM_INPUT, SQL_C_NUMERIC, SQL_NUMERIC, sizeof(SQL_NUMERIC_STRUCT), 0, &st_number, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 2, SQL_PARAM_INPUT, SQL_C_NUMERIC, SQL_NUMERIC, sizeof(SQL_NUMERIC_STRUCT), 0, &st_number, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(commit_exec());
+    RETURN_IF_NOT_SUCCESS(SQLRowCount(h_stmt, &RowCount));
+    RETURN_IF_NOT(1, RowCount);
+
+    //第三行: 12345678
+    memset(st_number.val, 0, SQL_MAX_NUMERIC_LEN);
+    st_number.precision = 0;
+    st_number.scale = 4;
+    st_number.sign = 1;
+    st_number.val[0] = 0x4E;
+    st_number.val[1] = 0x61;
+    st_number.val[2] = 0xBC;
+
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 1, SQL_PARAM_INPUT, SQL_C_NUMERIC, SQL_NUMERIC, sizeof(SQL_NUMERIC_STRUCT), 4, &st_number, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 2, SQL_PARAM_INPUT, SQL_C_NUMERIC, SQL_NUMERIC, sizeof(SQL_NUMERIC_STRUCT), 4, &st_number, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(commit_exec());
+    RETURN_IF_NOT_SUCCESS(SQLRowCount(h_stmt, &RowCount));
+    RETURN_IF_NOT(1, RowCount);
+
+
+    /* step 2.2 第四行通过SQL_C_CHAR字符串绑定参数 */
+    RETURN_IF_NOT_SUCCESS(SQLPrepare(h_stmt, sql_insert, SQL_NTS));
+    SQLCHAR*    szNumber = "1234.5678";
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 1, SQL_PARAM_INPUT, SQL_C_CHAR, SQL_NUMERIC, strlen(szNumber), 0, szNumber, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 2, SQL_PARAM_INPUT, SQL_C_CHAR, SQL_NUMERIC, strlen(szNumber), 0, szNumber, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(commit_exec());
+    RETURN_IF_NOT_SUCCESS(SQLRowCount(h_stmt, &RowCount));
+    RETURN_IF_NOT(1, RowCount);
+
+    /* step 2.3 第五行通过SQL_C_FLOAT绑定参数 */
+    RETURN_IF_NOT_SUCCESS(SQLPrepare(h_stmt, sql_insert, SQL_NTS));
+    SQLREAL    fNumber = 1234.5678;
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 1, SQL_PARAM_INPUT, SQL_C_FLOAT, SQL_NUMERIC, sizeof(fNumber), 4, &fNumber, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 2, SQL_PARAM_INPUT, SQL_C_FLOAT, SQL_NUMERIC, sizeof(fNumber), 4, &fNumber, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(commit_exec());
+    RETURN_IF_NOT_SUCCESS(SQLRowCount(h_stmt, &RowCount));
+    RETURN_IF_NOT(1, RowCount);
+
+    /* step 2.4 第六行通过SQL_C_DOUBLE绑定参数 */
+    RETURN_IF_NOT_SUCCESS(SQLPrepare(h_stmt, sql_insert, SQL_NTS));
+    SQLDOUBLE   dNumber = 1234.5678;
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 1, SQL_PARAM_INPUT, SQL_C_DOUBLE, SQL_NUMERIC, sizeof(dNumber), 4, &dNumber, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 2, SQL_PARAM_INPUT, SQL_C_DOUBLE, SQL_NUMERIC, sizeof(dNumber), 4, &dNumber, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(commit_exec());
+    RETURN_IF_NOT_SUCCESS(SQLRowCount(h_stmt, &RowCount));
+    RETURN_IF_NOT(1, RowCount);
+
+    SQLBIGINT   bNumber1 = 0xFFFFFFFFFFFFFFFF;
+    SQLBIGINT   bNumber2 = 12345;
+
+    /* step 2.5 第七行通过SQL_C_SBIGINT绑定参数 */
+    RETURN_IF_NOT_SUCCESS(SQLPrepare(h_stmt, sql_insert, SQL_NTS));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 1, SQL_PARAM_INPUT, SQL_C_SBIGINT, SQL_NUMERIC, sizeof(bNumber1), 4, &bNumber1, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 2, SQL_PARAM_INPUT, SQL_C_SBIGINT, SQL_NUMERIC, sizeof(bNumber2), 4, &bNumber2, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(commit_exec());
+    RETURN_IF_NOT_SUCCESS(SQLRowCount(h_stmt, &RowCount));
+    RETURN_IF_NOT(1, RowCount);
+
+    /* step 2.6 第八行通过SQL_C_UBIGINT绑定参数 */
+    RETURN_IF_NOT_SUCCESS(SQLPrepare(h_stmt, sql_insert, SQL_NTS));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 1, SQL_PARAM_INPUT, SQL_C_UBIGINT, SQL_NUMERIC, sizeof(bNumber1), 4, &bNumber1, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 2, SQL_PARAM_INPUT, SQL_C_UBIGINT, SQL_NUMERIC, sizeof(bNumber2), 4, &bNumber2, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(commit_exec());
+    RETURN_IF_NOT_SUCCESS(SQLRowCount(h_stmt, &RowCount));
+    RETURN_IF_NOT(1, RowCount);
+
+    SQLLEN  lNumber1 = 0xFFFFFFFFFFFFFFFF;
+    SQLLEN  lNumber2 = 12345;
+
+    /* step 2.7 第九行通过SQL_C_LONG绑定参数 */
+    RETURN_IF_NOT_SUCCESS(SQLPrepare(h_stmt, sql_insert, SQL_NTS));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 1, SQL_PARAM_INPUT, SQL_C_LONG, SQL_NUMERIC, sizeof(lNumber1), 0, &lNumber1, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 2, SQL_PARAM_INPUT, SQL_C_LONG, SQL_NUMERIC, sizeof(lNumber2), 0, &lNumber2, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(commit_exec());
+    RETURN_IF_NOT_SUCCESS(SQLRowCount(h_stmt, &RowCount));
+    RETURN_IF_NOT(1, RowCount);
+
+    /* step 2.8 第十行通过SQL_C_ULONG绑定参数 */
+    RETURN_IF_NOT_SUCCESS(SQLPrepare(h_stmt, sql_insert, SQL_NTS));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 1, SQL_PARAM_INPUT, SQL_C_ULONG, SQL_NUMERIC, sizeof(lNumber1), 0, &lNumber1, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 2, SQL_PARAM_INPUT, SQL_C_ULONG, SQL_NUMERIC, sizeof(lNumber2), 0, &lNumber2, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(commit_exec());
+    RETURN_IF_NOT_SUCCESS(SQLRowCount(h_stmt, &RowCount));
+    RETURN_IF_NOT(1, RowCount);
+
+    SQLSMALLINT sNumber = 0xFFFF;
+
+    /* step 2.9 第十一行通过SQL_C_SHORT绑定参数 */
+    RETURN_IF_NOT_SUCCESS(SQLPrepare(h_stmt, sql_insert, SQL_NTS));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 1, SQL_PARAM_INPUT, SQL_C_SHORT, SQL_NUMERIC, sizeof(sNumber), 0, &sNumber, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 2, SQL_PARAM_INPUT, SQL_C_SHORT, SQL_NUMERIC, sizeof(sNumber), 0, &sNumber, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(commit_exec());
+    RETURN_IF_NOT_SUCCESS(SQLRowCount(h_stmt, &RowCount));
+    RETURN_IF_NOT(1, RowCount);
+
+    /* step 2.10 第十二行通过SQL_C_USHORT绑定参数 */
+    RETURN_IF_NOT_SUCCESS(SQLPrepare(h_stmt, sql_insert, SQL_NTS));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 1, SQL_PARAM_INPUT, SQL_C_USHORT, SQL_NUMERIC, sizeof(sNumber), 0, &sNumber, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 2, SQL_PARAM_INPUT, SQL_C_USHORT, SQL_NUMERIC, sizeof(sNumber), 0, &sNumber, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(commit_exec());
+    RETURN_IF_NOT_SUCCESS(SQLRowCount(h_stmt, &RowCount));
+    RETURN_IF_NOT(1, RowCount);
+
+    SQLCHAR cNumber = 0xFF;
+
+    /* step 2.11 第十三行通过SQL_C_TINYINT绑定参数 */
+    RETURN_IF_NOT_SUCCESS(SQLPrepare(h_stmt, sql_insert, SQL_NTS));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 1, SQL_PARAM_INPUT, SQL_C_TINYINT, SQL_NUMERIC, sizeof(cNumber), 0, &cNumber, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 2, SQL_PARAM_INPUT, SQL_C_TINYINT, SQL_NUMERIC, sizeof(cNumber), 0, &cNumber, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(commit_exec());
+    RETURN_IF_NOT_SUCCESS(SQLRowCount(h_stmt, &RowCount));
+    RETURN_IF_NOT(1, RowCount);
+
+    /* step 2.12 第十四行通过SQL_C_UTINYINT绑定参数 */
+    RETURN_IF_NOT_SUCCESS(SQLPrepare(h_stmt, sql_insert, SQL_NTS));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 1, SQL_PARAM_INPUT, SQL_C_UTINYINT, SQL_NUMERIC, sizeof(cNumber), 0, &cNumber, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(SQLBindParameter(h_stmt, 2, SQL_PARAM_INPUT, SQL_C_UTINYINT, SQL_NUMERIC, sizeof(cNumber), 0, &cNumber, 0, NULL));
+    RETURN_IF_NOT_SUCCESS(commit_exec());
+    RETURN_IF_NOT_SUCCESS(SQLRowCount(h_stmt, &RowCount));
+    RETURN_IF_NOT(1, RowCount);
+
+    /* 用字符串类型统一进行期盼 */
+    SQLCHAR*    expectValue[14][2] = {{"1234.5678",             "1234.57"},
+                                      {"12345678",              "12345678"},
+                                      {"0",                     "0"},
+                                      {"1234.5678",             "1234.57"},
+                                      {"1234.5677",             "1234.57"},
+                                      {"1234.5678",             "1234.57"},
+                                      {"-1",                    "12345"},
+                                      {"18446744073709551615",  "12345"},
+                                      {"-1",                    "12345"},
+                                      {"4294967295",            "12345"},
+                                      {"-1",                    "-1"},
+                                      {"65535",                 "65535"},
+                                      {"-1",                    "-1"},
+                                      {"255",                   "255"},
+                                      };
+
+    RETURN_IF_NOT_SUCCESS(execute_cmd(sql_select));
+    while ( SQL_NO_DATA != SQLFetch(h_stmt))
+    {
+        RETURN_IF_NOT_SUCCESS_I(i, SQLGetData(h_stmt, 1, SQL_C_CHAR, &getValue[0], MESSAGE_BUFFER_LEN, NULL));
+        RETURN_IF_NOT_SUCCESS_I(i, SQLGetData(h_stmt, 2, SQL_C_CHAR, &getValue[1], MESSAGE_BUFFER_LEN, NULL));
+
+        //RETURN_IF_NOT_STRCMP_I(i, expectValue[i][0], getValue[0]);
+        //RETURN_IF_NOT_STRCMP_I(i, expectValue[i][1], getValue[1]);
+        i++;
+    }
+
+    RETURN_IF_NOT_SUCCESS(SQLRowCount(h_stmt, &RowCount));
+    RETURN_IF_NOT(i, RowCount);
+    SQLCloseCursor(h_stmt);
+    /* step final. 删除表还原环境 */
+    RETURN_IF_NOT_SUCCESS(execute_cmd(sql_drop));
+
+    end_unit_test();
+}
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 上述用例中定义了number列，调用SQLBindParameter接口时，绑定SQL_NUMERIC会比SQL_LONG性能高一些。因为如果是char，在数据库服务端插入数据时需要进行数据类型转换，从而引发性能瓶颈。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-0-odbc-overview.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-0-odbc-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..fece78228a6c6579adb8170aee29f78d0f0b845f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-0-odbc-overview.md
@@ -0,0 +1,10 @@
+---
+title: 说明
+summary: 说明
+author: Guo Huan
+date: 2021-05-17
+---
+
+# 说明
+
+ODBC接口是一套提供给用户的API函数，本节将对部分常用接口做具体描述，若涉及其他接口可参考[msdn](https://msdn.microsoft.com/en-us/library/windows/desktop/ms714177(v=vs.85).aspx)中“ODBC Programmer's Reference”项的相关内容。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-1-SQLAllocEnv.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-1-SQLAllocEnv.md
new file mode 100644
index 0000000000000000000000000000000000000000..9cae84431a73edc8688f5715636c20c8bf77e5a9
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-1-SQLAllocEnv.md
@@ -0,0 +1,10 @@
+---
+title: SQLAllocEnv
+summary: SQLAllocEnv
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLAllocEnv
+
+在ODBC 3.x版本中，ODBC 2.x的函数SQLAllocEnv已被SQLAllocHandle代替。有关详细信息请参阅SQLAllocHandle。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-10-SQLExecDirect.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-10-SQLExecDirect.md
new file mode 100644
index 0000000000000000000000000000000000000000..f0524978168fc485585da2d7771759985f55af97
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-10-SQLExecDirect.md
@@ -0,0 +1,48 @@
+---
+title: SQLExecDirect
+summary: SQLExecDirect
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLExecDirect
+
+## 功能描述
+
+使用参数的当前值，执行一条准备好的语句。对于一次只执行一条SQL语句，SQLExecDirect是最快的执行方式。
+
+## 原型
+
+```
+SQLRETURN SQLExecDirect(SQLHSTMT         StatementHandle,
+                        SQLCHAR         *StatementText,
+                        SQLINTEGER       TextLength);
+```
+
+## 参数
+
+**表 1** SQLExecDirect参数
+
+| **关键字**      | **参数说明**                              |
+| :-------------- | :---------------------------------------- |
+| StatementHandle | 语句句柄，通过SQLAllocHandle获得。        |
+| StatementText   | 要执行的SQL语句。不支持一次执行多条语句。 |
+| TextLength      | StatementText的长度。                     |
+
+## 返回值
+
+- SQL_SUCCESS：表示调用正确。
+- SQL_SUCCESS_WITH_INFO：表示会有一些警告信息。
+- SQL_NEED_DATA：在执行SQL语句前没有提供足够的参数。
+- SQL_ERROR：表示比较严重的错误，如：内存分配失败、建立连接失败等。
+- SQL_INVALID_HANDLE：表示调用无效句柄。其他API的返回值同理。
+- SQL_STILL_EXECUTING：表示语句正在执行。
+- SQL_NO_DATA：表示SQL语句不返回结果集。
+
+## 注意事项
+
+当调用SQLExecDirect函数返回SQL_ERROR或SQL_SUCCESS_WITH_INFO时，通过调用SQLGetDiagRec函数，并将HandleType和Handle参数设置为SQL_HANDLE_STMT和StatementHandle，可得到一个相关的SQLSTATE值，通过SQLSTATE值可以查出调用此函数的具体信息。
+
+## 示例
+
+参见：ODBC - 示例
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-11-SQLExecute.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-11-SQLExecute.md
new file mode 100644
index 0000000000000000000000000000000000000000..577517d23ac423fad9643b87c959a610d744a095
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-11-SQLExecute.md
@@ -0,0 +1,44 @@
+---
+title: SQLExecute
+summary: SQLExecute
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLExecute
+
+## 功能描述
+
+如果语句中存在参数标记的话，SQLExecute函数使用参数标记参数的当前值，执行一条准备好的SQL语句。
+
+## 原型
+
+```
+SQLRETURN SQLExecute(SQLHSTMT    StatementHandle);
+```
+
+## 参数
+
+**表 1** SQLExecute参数
+
+| **关键字**      | **参数说明**           |
+| :-------------- | :--------------------- |
+| StatementHandle | 要执行语句的语句句柄。 |
+
+## 返回值
+
+- SQL_SUCCESS：表示调用正确。
+- SQL_SUCCESS_WITH_INFO：表示会有一些警告信息。
+- SQL_NEED_DATA：表示在执行SQL语句前没有提供足够的参数。
+- SQL_ERROR：表示比较严重的错误，如：内存分配失败、建立连接失败等。
+- SQL_NO_DATA：表示SQL语句不返回结果集。
+- SQL_INVALID_HANDLE：表示调用无效句柄。其他API的返回值同理。
+- SQL_STILL_EXECUTING：表示语句正在执行。
+
+## 注意事项
+
+当SQLExecute函数返回SQL_ERROR或SQL_SUCCESS_WITH_INFO时，可通过调用SQLGetDiagRec函数，并将HandleType和Handle参数设置为SQL_HANDLE_STMT和StatementHandle，可得到一个相关的SQLSTATE值，通过SQLSTATE值可以查出调用此函数的具体信息。
+
+## 示例
+
+参见：ODBC - 示例
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-12-SQLFetch.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-12-SQLFetch.md
new file mode 100644
index 0000000000000000000000000000000000000000..7660632bf512c5e22d56887a32b1099575b14d4b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-12-SQLFetch.md
@@ -0,0 +1,43 @@
+---
+title: SQLFetch
+summary: SQLFetch
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLFetch
+
+## 功能描述
+
+从结果集中取下一个行集的数据，并返回所有被绑定列的数据。
+
+## 原型
+
+```
+SQLRETURN SQLFetch(SQLHSTMT    StatementHandle);
+```
+
+## 参数
+
+**表 1** SQLFetch参数
+
+| **关键字**      | **参数说明**                       |
+| :-------------- | :--------------------------------- |
+| StatementHandle | 语句句柄，通过SQLAllocHandle获得。 |
+
+## 返回值
+
+- SQL_SUCCESS：表示调用正确。
+- SQL_SUCCESS_WITH_INFO：表示会有一些警告信息。
+- SQL_ERROR：表示比较严重的错误，如：内存分配失败、建立连接失败等。
+- SQL_NO_DATA：表示SQL语句不返回结果集。
+- SQL_INVALID_HANDLE：表示调用无效句柄。其他API的返回值同理。
+- SQL_STILL_EXECUTING：表示语句正在执行。
+
+## 注意事项
+
+当调用SQLFetch函数返回SQL_ERROR或SQL_SUCCESS_WITH_INFO时，通过调用SQLGetDiagRec函数，并将HandleType和Handle参数设置为SQL_HANDLE_STMT和StatementHandle，可得到一个相关的SQLSTATE值，通过SQLSTATE值可以查出调用此函数的具体信息。
+
+## 示例
+
+参见：ODBC - 示例
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-13-SQLFreeStmt.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-13-SQLFreeStmt.md
new file mode 100644
index 0000000000000000000000000000000000000000..a20fe21a06a9e0de5ef1a520d6e95cea0c13d26e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-13-SQLFreeStmt.md
@@ -0,0 +1,10 @@
+---
+title: SQLFreeStmt
+summary: SQLFreeStmt
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLFreeStmt
+
+在ODBC 3.x版本中，ODBC 2.x的函数SQLFreeStmt已被SQLFreeHandle代替。有关详细信息请参阅SQLFreeHandle。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-14-SQLFreeConnect.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-14-SQLFreeConnect.md
new file mode 100644
index 0000000000000000000000000000000000000000..ffd51fa4cb5553ef8c9ae4cd846e5e29360955aa
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-14-SQLFreeConnect.md
@@ -0,0 +1,10 @@
+---
+title: SQLFreeConnect
+summary: SQLFreeConnect
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLFreeConnect
+
+在ODBC 3.x版本中，ODBC 2.x的函数SQLFreeConnect已被SQLFreeHandle代替。有关详细信息请参阅SQLFreeHandle。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-15-SQLFreeHandle.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-15-SQLFreeHandle.md
new file mode 100644
index 0000000000000000000000000000000000000000..fca4c449a665f1d9a44d92b6b31d0f9f1118158b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-15-SQLFreeHandle.md
@@ -0,0 +1,43 @@
+---
+title: SQLFreeHandle
+summary: SQLFreeHandle
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLFreeHandle
+
+## 功能描述
+
+释放与指定环境、连接、语句或描述符相关联的资源，它替代了ODBC 2.x函数SQLFreeEnv、SQLFreeConnect及SQLFreeStmt。
+
+## 原型
+
+```
+SQLRETURN SQLFreeHandle(SQLSMALLINT   HandleType,
+                        SQLHANDLE     Handle);
+```
+
+## 参数
+
+**表 1** SQLFreeHandle参数
+
+| **关键字** | **参数说明**                                                 |
+| :--------- | :----------------------------------------------------------- |
+| HandleType | SQLFreeHandle要释放的句柄类型。必须为下列值之一：<br/>- SQL_HANDLE_ENV<br/>- SQL_HANDLE_DBC<br/>- SQL_HANDLE_STMT<br/>- SQL_HANDLE_DESC<br/>如果HandleType不是这些值之一，SQLFreeHandle返回SQL_INVALID_HANDLE。 |
+| Handle     | 要释放的句柄。                                               |
+
+## 返回值
+
+- SQL_SUCCESS：表示调用正确。
+- SQL_SUCCESS_WITH_INFO：表示会有一些警告信息。
+- SQL_ERROR：表示比较严重的错误，如：内存分配失败、建立连接失败等。
+- SQL_INVALID_HANDLE：表示调用无效句柄。其他API的返回值同理。
+
+## 注意事项
+
+如果SQLFreeHandle返回SQL_ERROR，句柄仍然有效。
+
+## 示例
+
+参见：ODBC - 示例
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-16-SQLFreeEnv.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-16-SQLFreeEnv.md
new file mode 100644
index 0000000000000000000000000000000000000000..6a245776fa1ca9305c3726bea219730bbadc2166
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-16-SQLFreeEnv.md
@@ -0,0 +1,10 @@
+---
+title: SQLFreeEnv
+summary: SQLFreeEnv
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLFreeEnv
+
+在ODBC 3.x版本中，ODBC 2.x的函数SQLFreeEnv已被SQLFreeHandle代替。有关详细信息请参阅SQLFreeHandle。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-17-SQLPrepare.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-17-SQLPrepare.md
new file mode 100644
index 0000000000000000000000000000000000000000..03ee6a6171744e2abf674048325fc395b295491e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-17-SQLPrepare.md
@@ -0,0 +1,46 @@
+---
+title: SQLPrepare
+summary: SQLPrepare
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLPrepare
+
+## 功能描述
+
+准备一个将要进行的SQL语句。
+
+## 原型
+
+```
+SQLRETURN SQLPrepare(SQLHSTMT      StatementHandle,
+                     SQLCHAR       *StatementText,
+                     SQLINTEGER    TextLength);
+```
+
+## 参数
+
+**表 1** SQLPrepare参数
+
+| **关键字**      | **参数说明**          |
+| :-------------- | :-------------------- |
+| StatementHandle | 语句句柄。            |
+| StatementText   | SQL文本串。           |
+| TextLength      | StatementText的长度。 |
+
+## 返回值
+
+- SQL_SUCCESS：表示调用正确。
+- SQL_SUCCESS_WITH_INFO：表示会有一些警告信息。
+- SQL_ERROR：表示比较严重的错误，如：内存分配失败、建立连接失败等。
+- SQL_INVALID_HANDLE：表示调用无效句柄。其他API的返回值同理。
+- SQL_STILL_EXECUTING：表示语句正在执行。
+
+## 注意事项
+
+当SQLPrepare返回的值为SQL_ERROR或SQL_SUCCESS_WITH_INFO时，通过调用SQLGetDiagRec函数，并将HandleType和Handle参数分别设置为SQL_HANDLE_STMT和StatementHandle，可得到一个相关的SQLSTATE值，通过SQLSTATE值可以查出调用此函数的具体信息。
+
+## 示例
+
+参见：ODBC - 示例
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-18-SQLGetData.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-18-SQLGetData.md
new file mode 100644
index 0000000000000000000000000000000000000000..b167531ec8d2c15e9b6f2cefaf8d2271ad839383
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-18-SQLGetData.md
@@ -0,0 +1,53 @@
+---
+title: SQLGetData
+summary: SQLGetData
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLGetData
+
+## 功能描述
+
+SQLGetData返回结果集中某一列的数据。可以多次调用它来部分地检索不定长度的数据。
+
+## 原型
+
+```
+SQLRETURN SQLGetData(SQLHSTMT        StatementHandle,
+                     SQLUSMALLINT    Col_or_Param_Num,
+                     SQLSMALLINT     TargetType,
+                     SQLPOINTER      TargetValuePtr,
+                     SQLLEN          BufferLength,
+                     SQLLEN          *StrLen_or_IndPtr);
+```
+
+## 参数
+
+**表 1** SQLGetData参数
+
+| **关键字**       | **参数说明**                                                 |
+| :--------------- | :----------------------------------------------------------- |
+| StatementHandle  | 语句句柄，通过SQLAllocHandle获得。                           |
+| Col_or_Param_Num | 要返回数据的列号。结果集的列按增序从1开始编号。书签列的列号为0。 |
+| TargetType       | TargetValuePtr缓冲中的C数据类型的类型标识符。若TargetType为SQL_ARD_TYPE，驱动使用ARD中SQL_DESC_CONCISE_TYPE字段的类型标识符。若为SQL_C_DEFAULT，驱动根据源的SQL数据类型选择缺省的数据类型。 |
+| TargetValuePtr   | **输出参数**：指向返回数据所在缓冲区的指针。                 |
+| BufferLength     | TargetValuePtr所指向缓冲区的长度。                           |
+| StrLen_or_IndPtr | **输出参数**：指向缓冲区的指针，在此缓冲区中返回长度或标识符的值。 |
+
+## 返回值
+
+- SQL_SUCCESS：表示调用正确。
+- SQL_SUCCESS_WITH_INFO：表示会有一些警告信息。
+- SQL_ERROR：表示比较严重的错误，如：内存分配失败、建立连接失败等。
+- SQL_NO_DATA：表示SQL语句不返回结果集。
+- SQL_INVALID_HANDLE：表示调用无效句柄。其他API的返回值同理。
+- SQL_STILL_EXECUTING：表示语句正在执行。
+
+## 注意事项
+
+当调用SQLGetData函数返回SQL_ERROR或SQL_SUCCESS_WITH_INFO时，通过调用SQLGetDiagRec函数，并将HandleType和Handle参数分别设置为SQL_HANDLE_STMT和StatementHandle，可得到一个相关的SQLSTATE值，通过SQLSTATE值可以查出调用此函数的具体信息。
+
+## 示例
+
+参见：ODBC - 示例
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-19-SQLGetDiagRec.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-19-SQLGetDiagRec.md
new file mode 100644
index 0000000000000000000000000000000000000000..f086ec4d7f05b20e5e51e8c62b778f665e9f43ad
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-19-SQLGetDiagRec.md
@@ -0,0 +1,74 @@
+---
+title: SQLGetDiagRec
+summary: SQLGetDiagRec
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLGetDiagRec
+
+## 功能描述
+
+返回诊断记录的多个字段的当前值，其中诊断记录包含错误、警告及状态信息。
+
+## 原型
+
+```
+SQLRETURN  SQLGetDiagRec(SQLSMALLINT    HandleType
+                         SQLHANDLE      Handle,
+                         SQLSMALLINT    RecNumber,
+                         SQLCHAR        *SQLState,
+                         SQLINTEGER     *NativeErrorPtr,
+                         SQLCHAR        *MessageText,
+                         SQLSMALLINT    BufferLength
+                         SQLSMALLINT    *TextLengthPtr);
+```
+
+## 参数
+
+**表 1** SQLGetDiagRec参数
+
+| **关键字**     | **参数说明**                                                 |
+| :------------- | :----------------------------------------------------------- |
+| HandleType     | 句柄类型标识符，它说明诊断所要求的句柄类型。必须为下列值之一：<br/>- SQL_HANDLE_ENV<br/>- SQL_HANDLE_DBC<br/>- SQL_HANDLE_STMT<br/>- SQL_HANDLE_DESC |
+| Handle         | 诊断数据结构的句柄，其类型由HandleType来指出。如果HandleType是SQL_HANDLE_ENV，Handle可以是共享的或非共享的环境句柄。 |
+| RecNumber      | 指出应用从查找信息的状态记录。状态记录从1开始编号。          |
+| SQLState       | **输出参数**：指向缓冲区的指针，该缓冲区存储着有关RecNumber的五字符的SQLSTATE码。 |
+| NativeErrorPtr | **输出参数**：指向缓冲区的指针，该缓冲区存储着本地的错误码。 |
+| MessageText    | 指向缓冲区的指针，该缓冲区存储着诊断信息文本串。             |
+| BufferLength   | MessageText的长度。                                          |
+| TextLengthPtr  | **输出参数**：指向缓冲区的指针，返回MessageText中的字节总数。如果返回字节数大于BufferLength，则MessageText中的诊断信息文本被截断成BufferLength减去NULL结尾字符的长度。 |
+
+## 返回值
+
+- SQL_SUCCESS：表示调用正确。
+- SQL_SUCCESS_WITH_INFO：表示会有一些警告信息。
+- SQL_ERROR：表示比较严重的错误，如：内存分配失败、建立连接失败等。
+- SQL_INVALID_HANDLE：表示调用无效句柄。其他API的返回值同理。
+
+## 注意事项
+
+SQLGetDiagRec不发布自己的诊断记录。它用下列返回值来报告它自己的执行结果：
+
+- SQL_SUCCESS：函数成功返回诊断信息。
+- SQL_SUCCESS_WITH_INFO：MessageText太小以致不能容纳所请求的诊断信息。没有诊断记录生成。
+- SQL_INVALID_HANDLE：由HandType和Handle所指出的句柄是不合法句柄。
+- SQL_ERROR：RecNumber小于等于0或BufferLength小于0。
+
+如果调用ODBC函数返回SQL_ERROR或SQL_SUCCESS_WITH_INFO，可调用SQLGetDiagRec返回诊断信息值SQLSTATE，SQLSTATE值的如下表。
+
+**表 2** SQLSTATE值
+
+| SQLSATATE | 错误                 | 描述                                                         |
+| :-------- | :------------------- | :----------------------------------------------------------- |
+| HY000     | 一般错误             | 未定义特定的SQLSTATE所产生的一个错误。                       |
+| HY001     | 内存分配错误         | 驱动程序不能分配所需要的内存来支持函数的执行或完成。         |
+| HY008     | 取消操作             | 调用SQLCancel取消执行语句后，依然在StatementHandle上调用函数。 |
+| HY010     | 函数系列错误         | 在为执行中的所有数据参数或列发送数据前就调用了执行函数。     |
+| HY013     | 内存管理错误         | 不能处理函数调用，可能由当前内存条件差引起。                 |
+| HYT01     | 连接超时             | 数据源响应请求之前，连接超时。                               |
+| IM001     | 驱动程序不支持此函数 | 调用了StatementHandle相关的驱动程序不支持的函数。            |
+
+## 示例
+
+参见：ODBC - 示例
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-2-SQLAllocConnect.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-2-SQLAllocConnect.md
new file mode 100644
index 0000000000000000000000000000000000000000..c95fef8c096c1872185da494010de9b86af1680a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-2-SQLAllocConnect.md
@@ -0,0 +1,10 @@
+---
+title: SQLAllocConnect
+summary: SQLAllocConnect
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLAllocConnect
+
+在ODBC 3.x版本中，ODBC 2.x的函数SQLAllocConnect已被SQLAllocHandle代替。有关详细信息请参阅SQLAllocHandle。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-20-SQLSetConnectAttr.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-20-SQLSetConnectAttr.md
new file mode 100644
index 0000000000000000000000000000000000000000..184ca27355dfdc8e53d27fbef5c78a56e2d8c2da
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-20-SQLSetConnectAttr.md
@@ -0,0 +1,47 @@
+---
+title: SQLSetConnectAttr
+summary: SQLSetConnectAttr
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLSetConnectAttr
+
+## 功能描述
+
+设置控制连接各方面的属性。
+
+## 原型
+
+```
+SQLRETURN SQLSetConnectAttr(SQLHDBC       ConnectionHandle
+                            SQLINTEGER    Attribute,
+                            SQLPOINTER    ValuePtr,
+                            SQLINTEGER    StringLength);
+```
+
+## 参数
+
+**表 1** SQLSetConnectAttr参数
+
+| **关键字**       | **参数说明**                                                 |
+| :--------------- | :----------------------------------------------------------- |
+| ConnectionHandle | 连接句柄。                                                   |
+| Attribute        | 设置属性。                                                   |
+| ValuePtr         | 指向对应Attribute的值。依赖于Attribute的值，ValuePtr是32位无符号整型值或指向以空结束的字符串。注意，如果ValuePtr参数是驱动程序指定值。ValuePtr可能是有符号的整数。 |
+| StringLength     | 如果ValuePtr指向字符串或二进制缓冲区，这个参数是*ValuePtr长度，如果ValuePtr指向整型，忽略StringLength。 |
+
+## 返回值
+
+- SQL_SUCCESS：表示调用正确。
+- SQL_SUCCESS_WITH_INFO：表示会有一些警告信息。
+- SQL_ERROR：表示比较严重的错误，如：内存分配失败、建立连接失败等。
+- SQL_INVALID_HANDLE：表示调用无效句柄。其他API的返回值同理。
+
+## 注意事项
+
+当SQLSetConnectAttr的返回值为SQL_ERROR或SQL_SUCCESS_WITH_INFO时，通过借助SQL_HANDLE_DBC的HandleType和ConnectionHandle的Handle，调用SQLGetDiagRec可得到相关的SQLSTATE值，通过SQLSTATE值可以查出调用此函数的具体信息。
+
+## 示例
+
+参见：ODBC - 示例
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-21-SQLSetEnvAttr.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-21-SQLSetEnvAttr.md
new file mode 100644
index 0000000000000000000000000000000000000000..669f3ea40b0c99b49af1067ce965b492f20db864
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-21-SQLSetEnvAttr.md
@@ -0,0 +1,47 @@
+---
+title: SQLSetEnvAttr
+summary: SQLSetEnvAttr
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLSetEnvAttr
+
+## 功能描述
+
+设置控制环境各方面的属性。
+
+## 原型
+
+```
+SQLRETURN SQLSetEnvAttr(SQLHENV       EnvironmentHandle
+                        SQLINTEGER    Attribute,
+                        SQLPOINTER    ValuePtr,
+                        SQLINTEGER    StringLength);
+```
+
+## 参数
+
+**表 1** SQLSetEnvAttr参数
+
+| **关键字**        | **参数说明**                                                 |
+| :---------------- | :----------------------------------------------------------- |
+| EnvironmentHandle | 环境句柄。                                                   |
+| Attribute         | 需设置的环境属性，可为如下值：<br/>- SQL_ATTR_ODBC_VERSION：指定ODBC版本。<br/>- SQL_CONNECTION_POOLING：连接池属性。<br/>- SQL_OUTPUT_NTS：指明驱动器返回字符串的形式。 |
+| ValuePtr          | 指向对应Attribute的值。依赖于Attribute的值，ValuePtr可能是32位整型值，或为以空结束的字符串。 |
+| StringLength      | 如果ValuePtr指向字符串或二进制缓冲区，这个参数是*ValuePtr长度，如果ValuePtr指向整型，忽略StringLength。 |
+
+## 返回值
+
+- SQL_SUCCESS：表示调用正确。
+- SQL_SUCCESS_WITH_INFO：表示会有一些警告信息。
+- SQL_ERROR：表示比较严重的错误，如：内存分配失败、建立连接失败等。
+- SQL_INVALID_HANDLE：表示调用无效句柄。其他API的返回值同理。
+
+## 注意事项
+
+当SQLSetEnvAttr的返回值为SQL_ERROR或SQL_SUCCESS_WITH_INFO时，通过借助SQL_HANDLE_ENV的HandleType和EnvironmentHandle的Handle，调用SQLGetDiagRec可得到相关的SQLSTATE值，通过SQLSTATE值可以查出调用此函数的具体信息。
+
+## 示例
+
+参见：ODBC - 示例
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-22-SQLSetStmtAttr.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-22-SQLSetStmtAttr.md
new file mode 100644
index 0000000000000000000000000000000000000000..0a9bfeb2dbf841470105ea16fdf84027b57d30b6
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-22-SQLSetStmtAttr.md
@@ -0,0 +1,47 @@
+---
+title: SQLSetStmtAttr
+summary: SQLSetStmtAttr
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLSetStmtAttr
+
+## 功能描述
+
+设置相关语句的属性。
+
+## 原型
+
+```
+SQLRETURN SQLSetStmtAttr(SQLHSTMT      StatementHandle
+                         SQLINTEGER    Attribute,
+                         SQLPOINTER    ValuePtr,
+                         SQLINTEGER    StringLength);
+```
+
+## 参数
+
+**表 1** SQLSetStmtAttr参数
+
+| **关键字**      | **参数说明**                                                 |
+| :-------------- | :----------------------------------------------------------- |
+| StatementHandle | 语句句柄。                                                   |
+| Attribute       | 需设置的属性。                                               |
+| ValuePtr        | 指向对应Attribute的值。依赖于Attribute的值，ValuePtr可能是32位无符号整型值，或指向以空结束的字符串，二进制缓冲区，或者驱动定义值。注意，如果ValuePtr参数是驱动程序指定值。ValuePtr可能是有符号的整数。 |
+| StringLength    | 如果ValuePtr指向字符串或二进制缓冲区，这个参数是*ValuePtr长度，如果ValuePtr指向整型，忽略StringLength。 |
+
+## 返回值
+
+- SQL_SUCCESS：表示调用正确。
+- SQL_SUCCESS_WITH_INFO：表示会有一些警告信息。
+- SQL_ERROR：表示比较严重的错误，如：内存分配失败、建立连接失败等。
+- SQL_INVALID_HANDLE：表示调用无效句柄。其他API的返回值同理。
+
+## 注意事项
+
+当SQLSetStmtAttr的返回值为SQL_ERROR或SQL_SUCCESS_WITH_INFO时，通过借助SQL_HANDLE_STMT的HandleType和StatementHandle的Handle，调用SQLGetDiagRec可得到相关的SQLSTATE值，通过SQLSTATE值可以查出调用此函数的具体信息。
+
+## 示例
+
+参见：ODBC - 示例
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-23-Examples.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-23-Examples.md
new file mode 100644
index 0000000000000000000000000000000000000000..5c39c9324de8f17bbab63d895b2576f7b7d5f9e0
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-23-Examples.md
@@ -0,0 +1,347 @@
+---
+title: 示例
+summary: 示例
+author: Guo Huan
+date: 2021-05-17
+---
+
+# 示例
+
+## 常用功能示例代码
+
+```c
+// 此示例演示如何通过ODBC方式获取MogDB中的数据。
+// DBtest.c (compile with: libodbc.so)
+#include <stdlib.h>
+#include <stdio.h>
+#include <sqlext.h>
+#ifdef WIN32
+#include <windows.h>
+#endif
+SQLHENV       V_OD_Env;        // Handle ODBC environment
+SQLHSTMT      V_OD_hstmt;      // Handle statement
+SQLHDBC       V_OD_hdbc;       // Handle connection
+char          typename[100];
+SQLINTEGER    value = 100;
+SQLINTEGER    V_OD_erg,V_OD_buffer,V_OD_err,V_OD_id;
+int main(int argc,char *argv[])
+{
+      // 1. 申请环境句柄
+      V_OD_erg = SQLAllocHandle(SQL_HANDLE_ENV,SQL_NULL_HANDLE,&V_OD_Env);
+      if ((V_OD_erg != SQL_SUCCESS) && (V_OD_erg != SQL_SUCCESS_WITH_INFO))
+      {
+           printf("Error AllocHandle\n");
+           exit(0);
+      }
+      // 2. 设置环境属性（版本信息）
+      SQLSetEnvAttr(V_OD_Env, SQL_ATTR_ODBC_VERSION, (void*)SQL_OV_ODBC3, 0);
+      // 3. 申请连接句柄
+      V_OD_erg = SQLAllocHandle(SQL_HANDLE_DBC, V_OD_Env, &V_OD_hdbc);
+      if ((V_OD_erg != SQL_SUCCESS) && (V_OD_erg != SQL_SUCCESS_WITH_INFO))
+      {
+           SQLFreeHandle(SQL_HANDLE_ENV, V_OD_Env);
+           exit(0);
+      }
+      // 4. 设置连接属性
+      SQLSetConnectAttr(V_OD_hdbc, SQL_ATTR_AUTOCOMMIT, SQL_AUTOCOMMIT_ON, 0);
+      // 5. 连接数据源，这里的“userName”与“password”分别表示连接数据库的用户名和用户密码，请根据实际情况修改。
+      // 如果odbc.ini文件中已经配置了用户名密码，那么这里可以留空（""）；但是不建议这么做，因为一旦odbc.ini权限管理不善，将导致数据库用户密码泄露。
+      V_OD_erg = SQLConnect(V_OD_hdbc, (SQLCHAR*) "mogdb", SQL_NTS,
+                           (SQLCHAR*) "userName", SQL_NTS,  (SQLCHAR*) "password", SQL_NTS);
+      if ((V_OD_erg != SQL_SUCCESS) && (V_OD_erg != SQL_SUCCESS_WITH_INFO))
+      {
+          printf("Error SQLConnect %d\n",V_OD_erg);
+          SQLFreeHandle(SQL_HANDLE_ENV, V_OD_Env);
+          exit(0);
+      }
+      printf("Connected !\n");
+      // 6. 设置语句属性
+      SQLSetStmtAttr(V_OD_hstmt,SQL_ATTR_QUERY_TIMEOUT,(SQLPOINTER *)3,0);
+      // 7. 申请语句句柄
+      SQLAllocHandle(SQL_HANDLE_STMT, V_OD_hdbc, &V_OD_hstmt);
+      // 8. 直接执行SQL语句。
+      SQLExecDirect(V_OD_hstmt,"drop table IF EXISTS customer_t1",SQL_NTS);
+      SQLExecDirect(V_OD_hstmt,"CREATE TABLE customer_t1(c_customer_sk INTEGER, c_customer_name VARCHAR(32));",SQL_NTS);
+      SQLExecDirect(V_OD_hstmt,"insert into customer_t1 values(25,li)",SQL_NTS);
+      // 9. 准备执行
+      SQLPrepare(V_OD_hstmt,"insert into customer_t1 values(?)",SQL_NTS);
+      // 10. 绑定参数
+      SQLBindParameter(V_OD_hstmt,1,SQL_PARAM_INPUT,SQL_C_SLONG,SQL_INTEGER,0,0,
+                       &value,0,NULL);
+      // 11. 执行准备好的语句
+      SQLExecute(V_OD_hstmt);
+      SQLExecDirect(V_OD_hstmt,"select id from testtable",SQL_NTS);
+      // 12. 获取结果集某一列的属性
+      SQLColAttribute(V_OD_hstmt,1,SQL_DESC_TYPE,typename,100,NULL,NULL);
+      printf("SQLColAtrribute %s\n",typename);
+      // 13. 绑定结果集
+      SQLBindCol(V_OD_hstmt,1,SQL_C_SLONG, (SQLPOINTER)&V_OD_buffer,150,
+                (SQLLEN *)&V_OD_err);
+      // 14. 通过SQLFetch取结果集中数据
+      V_OD_erg=SQLFetch(V_OD_hstmt);
+      // 15. 通过SQLGetData获取并返回数据。
+      while(V_OD_erg != SQL_NO_DATA)
+      {
+          SQLGetData(V_OD_hstmt,1,SQL_C_SLONG,(SQLPOINTER)&V_OD_id,0,NULL);
+          printf("SQLGetData ----ID = %d\n",V_OD_id);
+          V_OD_erg=SQLFetch(V_OD_hstmt);
+      };
+      printf("Done !\n");
+      // 16. 断开数据源连接并释放句柄资源
+      SQLFreeHandle(SQL_HANDLE_STMT,V_OD_hstmt);
+      SQLDisconnect(V_OD_hdbc);
+      SQLFreeHandle(SQL_HANDLE_DBC,V_OD_hdbc);
+      SQLFreeHandle(SQL_HANDLE_ENV, V_OD_Env);
+      return(0);
+ }
+```
+
+<br/>
+
+## 批量绑定示例代码
+
+```c
+/**********************************************************************
+* 请在数据源中打开UseBatchProtocol，同时指定数据库中参数support_batch_bind
+* 为on
+* CHECK_ERROR的作用是检查并打印错误信息。
+* 此示例将与用户交互式获取DSN、模拟的数据量，忽略的数据量，并将最终数据入库到test_odbc_batch_insert中
+***********************************************************************/
+#include <stdio.h>
+#include <stdlib.h>
+#include <sql.h>
+#include <sqlext.h>
+#include <string.h>
+
+#include "util.c"
+
+void Exec(SQLHDBC hdbc, SQLCHAR* sql)
+{
+    SQLRETURN retcode;                  // Return status
+    SQLHSTMT hstmt = SQL_NULL_HSTMT;    // Statement handle
+    SQLCHAR     loginfo[2048];
+
+    // Allocate Statement Handle
+    retcode = SQLAllocHandle(SQL_HANDLE_STMT, hdbc, &hstmt);
+    CHECK_ERROR(retcode, "SQLAllocHandle(SQL_HANDLE_STMT)",
+                hstmt, SQL_HANDLE_STMT);
+
+    // Prepare Statement
+    retcode = SQLPrepare(hstmt, (SQLCHAR*) sql, SQL_NTS);
+    sprintf((char*)loginfo, "SQLPrepare log: %s", (char*)sql);
+    CHECK_ERROR(retcode, loginfo, hstmt, SQL_HANDLE_STMT);
+
+    // Execute Statement
+    retcode = SQLExecute(hstmt);
+    sprintf((char*)loginfo, "SQLExecute stmt log: %s", (char*)sql);
+    CHECK_ERROR(retcode, loginfo, hstmt, SQL_HANDLE_STMT);
+
+    // Free Handle
+    retcode = SQLFreeHandle(SQL_HANDLE_STMT, hstmt);
+    sprintf((char*)loginfo, "SQLFreeHandle stmt log: %s", (char*)sql);
+    CHECK_ERROR(retcode, loginfo, hstmt, SQL_HANDLE_STMT);
+}
+
+int main ()
+{
+    SQLHENV  henv  = SQL_NULL_HENV;
+    SQLHDBC  hdbc  = SQL_NULL_HDBC;
+    int      batchCount = 1000;
+    SQLLEN   rowsCount = 0;
+    int      ignoreCount = 0;
+
+    SQLRETURN   retcode;
+    SQLCHAR     dsn[1024] = {'\0'};
+    SQLCHAR     loginfo[2048];
+
+    // 交互获取数据源名称
+    getStr("Please input your DSN", (char*)dsn, sizeof(dsn), 'N');
+    // 交互获取批量绑定的数据量
+    getInt("batchCount", &batchCount, 'N', 1);
+    do
+    {
+        // 交互获取批量绑定的数据中，不要入库的数据量
+        getInt("ignoreCount", &ignoreCount, 'N', 1);
+        if (ignoreCount > batchCount)
+        {
+            printf("ignoreCount(%d) should be less than batchCount(%d)\n", ignoreCount, batchCount);
+        }
+    }while(ignoreCount > batchCount);
+
+    retcode = SQLAllocHandle(SQL_HANDLE_ENV, SQL_NULL_HANDLE, &henv);
+    CHECK_ERROR(retcode, "SQLAllocHandle(SQL_HANDLE_ENV)",
+                henv, SQL_HANDLE_ENV);
+
+    // Set ODBC Verion
+    retcode = SQLSetEnvAttr(henv, SQL_ATTR_ODBC_VERSION,
+                                        (SQLPOINTER*)SQL_OV_ODBC3, 0);
+    CHECK_ERROR(retcode, "SQLSetEnvAttr(SQL_ATTR_ODBC_VERSION)",
+                henv, SQL_HANDLE_ENV);
+
+    // Allocate Connection
+    retcode = SQLAllocHandle(SQL_HANDLE_DBC, henv, &hdbc);
+    CHECK_ERROR(retcode, "SQLAllocHandle(SQL_HANDLE_DBC)",
+                henv, SQL_HANDLE_DBC);
+
+    // Set Login Timeout
+    retcode = SQLSetConnectAttr(hdbc, SQL_LOGIN_TIMEOUT, (SQLPOINTER)5, 0);
+    CHECK_ERROR(retcode, "SQLSetConnectAttr(SQL_LOGIN_TIMEOUT)",
+                hdbc, SQL_HANDLE_DBC);
+
+    // Set Auto Commit
+    retcode = SQLSetConnectAttr(hdbc, SQL_ATTR_AUTOCOMMIT,
+                                        (SQLPOINTER)(1), 0);
+    CHECK_ERROR(retcode, "SQLSetConnectAttr(SQL_ATTR_AUTOCOMMIT)",
+                hdbc, SQL_HANDLE_DBC);
+
+    // Connect to DSN
+    sprintf(loginfo, "SQLConnect(DSN:%s)", dsn);
+    retcode = SQLConnect(hdbc, (SQLCHAR*) dsn, SQL_NTS,
+                               (SQLCHAR*) NULL, 0, NULL, 0);
+    CHECK_ERROR(retcode, loginfo, hdbc, SQL_HANDLE_DBC);
+
+    // init table info.
+    Exec(hdbc, "drop table if exists test_odbc_batch_insert");
+    Exec(hdbc, "create table test_odbc_batch_insert(id int primary key, col varchar2(50))");
+
+    // 下面的代码根据用户输入的数据量，构造出将要入库的数据:
+    {
+        SQLRETURN retcode;
+        SQLHSTMT hstmtinesrt = SQL_NULL_HSTMT;
+        int          i;
+        SQLCHAR      *sql = NULL;
+        SQLINTEGER   *ids  = NULL;
+        SQLCHAR      *cols = NULL;
+        SQLLEN       *bufLenIds = NULL;
+        SQLLEN       *bufLenCols = NULL;
+        SQLUSMALLINT *operptr = NULL;
+        SQLUSMALLINT *statusptr = NULL;
+        SQLULEN      process = 0;
+
+        // 这里是按列构造，每个字段的内存连续存放在一起。
+        ids = (SQLINTEGER*)malloc(sizeof(ids[0]) * batchCount);
+        cols = (SQLCHAR*)malloc(sizeof(cols[0]) * batchCount * 50);
+        // 这里是每个字段中，每一行数据的内存长度。
+        bufLenIds = (SQLLEN*)malloc(sizeof(bufLenIds[0]) * batchCount);
+        bufLenCols = (SQLLEN*)malloc(sizeof(bufLenCols[0]) * batchCount);
+        // 该行是否需要被处理，SQL_PARAM_IGNORE 或 SQL_PARAM_PROCEED
+        operptr = (SQLUSMALLINT*)malloc(sizeof(operptr[0]) * batchCount);
+        memset(operptr, 0, sizeof(operptr[0]) * batchCount);
+        // 该行的处理结果。
+        // 注：由于数据库中处理方式是同一语句隶属同一事务中，所以如果出错，那么待处理数据都将是出错的，并不会部分入库。
+        statusptr = (SQLUSMALLINT*)malloc(sizeof(statusptr[0]) * batchCount);
+        memset(statusptr, 88, sizeof(statusptr[0]) * batchCount);
+
+        if (NULL == ids || NULL == cols || NULL == bufLenCols || NULL == bufLenIds)
+        {
+            fprintf(stderr, "FAILED:\tmalloc data memory failed\n");
+            goto exit;
+        }
+
+        for (int i = 0; i < batchCount; i++)
+        {
+            ids[i] = i;
+            sprintf(cols + 50 * i, "column test value %d", i);
+            bufLenIds[i] = sizeof(ids[i]);
+            bufLenCols[i] = strlen(cols + 50 * i);
+            operptr[i] = (i < ignoreCount) ? SQL_PARAM_IGNORE : SQL_PARAM_PROCEED;
+        }
+
+        // Allocate Statement Handle
+        retcode = SQLAllocHandle(SQL_HANDLE_STMT, hdbc, &hstmtinesrt);
+        CHECK_ERROR(retcode, "SQLAllocHandle(SQL_HANDLE_STMT)",
+                    hstmtinesrt, SQL_HANDLE_STMT);
+
+        // Prepare Statement
+        sql = (SQLCHAR*)"insert into test_odbc_batch_insert values(?, ?)";
+        retcode = SQLPrepare(hstmtinesrt, (SQLCHAR*) sql, SQL_NTS);
+        sprintf((char*)loginfo, "SQLPrepare log: %s", (char*)sql);
+        CHECK_ERROR(retcode, loginfo, hstmtinesrt, SQL_HANDLE_STMT);
+
+        retcode = SQLSetStmtAttr(hstmtinesrt, SQL_ATTR_PARAMSET_SIZE, (SQLPOINTER)batchCount, sizeof(batchCount));
+        CHECK_ERROR(retcode, "SQLSetStmtAttr", hstmtinesrt, SQL_HANDLE_STMT);
+
+        retcode = SQLBindParameter(hstmtinesrt, 1, SQL_PARAM_INPUT, SQL_C_SLONG, SQL_INTEGER, sizeof(ids[0]), 0,&(ids[0]), 0, bufLenIds);
+        CHECK_ERROR(retcode, "SQLBindParameter for id", hstmtinesrt, SQL_HANDLE_STMT);
+
+        retcode = SQLBindParameter(hstmtinesrt, 2, SQL_PARAM_INPUT, SQL_C_CHAR, SQL_CHAR, 50, 50, cols, 50, bufLenCols);
+        CHECK_ERROR(retcode, "SQLBindParameter for cols", hstmtinesrt, SQL_HANDLE_STMT);
+
+        retcode = SQLSetStmtAttr(hstmtinesrt, SQL_ATTR_PARAMS_PROCESSED_PTR, (SQLPOINTER)&process, sizeof(process));
+        CHECK_ERROR(retcode, "SQLSetStmtAttr for SQL_ATTR_PARAMS_PROCESSED_PTR", hstmtinesrt, SQL_HANDLE_STMT);
+
+        retcode = SQLSetStmtAttr(hstmtinesrt, SQL_ATTR_PARAM_STATUS_PTR, (SQLPOINTER)statusptr, sizeof(statusptr[0]) * batchCount);
+        CHECK_ERROR(retcode, "SQLSetStmtAttr for SQL_ATTR_PARAM_STATUS_PTR", hstmtinesrt, SQL_HANDLE_STMT);
+
+        retcode = SQLSetStmtAttr(hstmtinesrt, SQL_ATTR_PARAM_OPERATION_PTR, (SQLPOINTER)operptr, sizeof(operptr[0]) * batchCount);
+        CHECK_ERROR(retcode, "SQLSetStmtAttr for SQL_ATTR_PARAM_OPERATION_PTR", hstmtinesrt, SQL_HANDLE_STMT);
+
+        retcode = SQLExecute(hstmtinesrt);
+        sprintf((char*)loginfo, "SQLExecute stmt log: %s", (char*)sql);
+        CHECK_ERROR(retcode, loginfo, hstmtinesrt, SQL_HANDLE_STMT);
+
+        retcode = SQLRowCount(hstmtinesrt, &rowsCount);
+        CHECK_ERROR(retcode, "SQLRowCount execution", hstmtinesrt, SQL_HANDLE_STMT);
+
+        if (rowsCount != (batchCount - ignoreCount))
+        {
+            sprintf(loginfo, "(batchCount - ignoreCount)(%d) != rowsCount(%d)", (batchCount - ignoreCount), rowsCount);
+            CHECK_ERROR(SQL_ERROR, loginfo, NULL, SQL_HANDLE_STMT);
+        }
+        else
+        {
+            sprintf(loginfo, "(batchCount - ignoreCount)(%d) == rowsCount(%d)", (batchCount - ignoreCount), rowsCount);
+            CHECK_ERROR(SQL_SUCCESS, loginfo, NULL, SQL_HANDLE_STMT);
+        }
+
+        // check row number returned
+        if (rowsCount != process)
+        {
+            sprintf(loginfo, "process(%d) != rowsCount(%d)", process, rowsCount);
+            CHECK_ERROR(SQL_ERROR, loginfo, NULL, SQL_HANDLE_STMT);
+        }
+        else
+        {
+            sprintf(loginfo, "process(%d) == rowsCount(%d)", process, rowsCount);
+            CHECK_ERROR(SQL_SUCCESS, loginfo, NULL, SQL_HANDLE_STMT);
+        }
+
+        for (int i = 0; i < batchCount; i++)
+        {
+            if (i < ignoreCount)
+            {
+                if (statusptr[i] != SQL_PARAM_UNUSED)
+                {
+                    sprintf(loginfo, "statusptr[%d](%d) != SQL_PARAM_UNUSED", i, statusptr[i]);
+                    CHECK_ERROR(SQL_ERROR, loginfo, NULL, SQL_HANDLE_STMT);
+                }
+            }
+            else if (statusptr[i] != SQL_PARAM_SUCCESS)
+            {
+                sprintf(loginfo, "statusptr[%d](%d) != SQL_PARAM_SUCCESS", i, statusptr[i]);
+                CHECK_ERROR(SQL_ERROR, loginfo, NULL, SQL_HANDLE_STMT);
+            }
+        }
+
+        retcode = SQLFreeHandle(SQL_HANDLE_STMT, hstmtinesrt);
+        sprintf((char*)loginfo, "SQLFreeHandle hstmtinesrt");
+        CHECK_ERROR(retcode, loginfo, hstmtinesrt, SQL_HANDLE_STMT);
+    }
+
+
+exit:
+    printf ("\nComplete.\n");
+
+    // Connection
+    if (hdbc != SQL_NULL_HDBC) {
+        SQLDisconnect(hdbc);
+        SQLFreeHandle(SQL_HANDLE_DBC, hdbc);
+    }
+
+    // Environment
+    if (henv != SQL_NULL_HENV)
+        SQLFreeHandle(SQL_HANDLE_ENV, henv);
+
+    return 0;
+}
+```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-3-SQLAllocHandle.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-3-SQLAllocHandle.md
new file mode 100644
index 0000000000000000000000000000000000000000..c7383dac35cc5063b7e116f644ff01f76a8e179f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-3-SQLAllocHandle.md
@@ -0,0 +1,45 @@
+---
+title: SQLAllocHandle
+summary: SQLAllocHandle
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLAllocHandle
+
+## 功能描述
+
+分配环境、连接、语句或描述符的句柄，它替代了ODBC 2.x函数SQLAllocEnv、SQLAllocConnect及SQLAllocStmt。
+
+## 原型
+
+```c
+SQLRETURN SQLAllocHandle(SQLSMALLINT   HandleType,
+                         SQLHANDLE     InputHandle,
+                         SQLHANDLE     *OutputHandlePtr);
+```
+
+## 参数
+
+**表 1**  SQLAllocHandle参数
+
+| **关键字**      | **参数说明**                                                 |
+| :-------------- | :----------------------------------------------------------- |
+| HandleType      | 由SQLAllocHandle分配的句柄类型。必须为下列值之一：<br/>- SQL_HANDLE_ENV（环境句柄）<br/>- SQL_HANDLE_DBC（连接句柄）<br/>- SQL_HANDLE_STMT（语句句柄）<br/>- SQL_HANDLE_DESC（描述句柄）<br/>申请句柄顺序为，先申请环境句柄，再申请连接句柄，最后申请语句句柄，后申请的句柄都要依赖它前面申请的句柄。 |
+| InputHandle     | 将要分配的新句柄的类型。<br/>- 如果HandleType为SQL_HANDLE_ENV，则这个值为SQL_NULL_HANDLE。<br/>- 如果HandleType为SQL_HANDLE_DBC，则这一定是一个环境句柄。<br/>- 如果HandleType为SQL_HANDLE_STMT或SQL_HANDLE_DESC，则它一定是一个连接句柄。 |
+| OutputHandlePtr | **输出参数**：一个缓冲区的指针，此缓冲区以新分配的数据结构存放返回的句柄。 |
+
+## 返回值
+
+- SQL_SUCCESS：表示调用正确。
+- SQL_SUCCESS_WITH_INFO：表示会有一些警告信息。
+- SQL_ERROR：表示比较严重的错误，如：内存分配失败、建立连接失败等。
+- SQL_INVALID_HANDLE：表示调用无效句柄。其他API的返回值同理。
+
+## 注意事项
+
+当分配的句柄并非环境句柄时，如果SQLAllocHandle返回的值为SQL_ERROR，则它会将OutputHandlePtr的值设置为SQL_NULL_HDBC、SQL_NULL_HSTMT或SQL_NULL_HDESC。之后，通过调用带有适当参数的SQLGetDiagRec，其中HandleType和Handle被设置为IntputHandle的值，可得到相关的SQLSTATE值，通过SQLSTATE值可以查出调用此函数的具体信息。
+
+## 示例
+
+参见：ODBC - 示例
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-4-SQLAllocStmt.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-4-SQLAllocStmt.md
new file mode 100644
index 0000000000000000000000000000000000000000..d1569ed0b5d14b830f3adc270cc71e60a68d58f6
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-4-SQLAllocStmt.md
@@ -0,0 +1,10 @@
+---
+title: SQLAllocStmt
+summary: SQLAllocStmt
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLAllocStmt
+
+在ODBC 3.x版本中，ODBC 2.x的函数SQLAllocStmt已被SQLAllocHandle代替。有关详细信息请参阅SQLAllocHandle。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-5-SQLBindCol.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-5-SQLBindCol.md
new file mode 100644
index 0000000000000000000000000000000000000000..aea568d9ca80945ce3549ff0db3bbaf0069312b1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-5-SQLBindCol.md
@@ -0,0 +1,51 @@
+---
+title: SQLBindCol
+summary: SQLBindCol
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLBindCol
+
+## 功能描述
+
+将应用程序数据缓冲区绑定到结果集的列中。
+
+## 原型
+
+```c
+SQLRETURN SQLBindCol(SQLHSTMT       StatementHandle,
+                     SQLUSMALLINT   ColumnNumber,
+                     SQLSMALLINT    TargetType,
+                     SQLPOINTER     TargetValuePtr,
+                     SQLLEN     BufferLength,
+                     SQLLEN     *StrLen_or_IndPtr);
+```
+
+## 参数
+
+**表 1**  SQLBindCol参数
+
+| **关键字**       | **参数说明**                                                 |
+| :--------------- | :----------------------------------------------------------- |
+| StatementHandle  | 语句句柄。                                                   |
+| ColumnNumber     | 要绑定结果集的列号。起始列号为0，以递增的顺序计算列号，第0列是书签列。若未设置书签页，则起始列号为1。 |
+| TargetType       | 缓冲区中C数据类型的标识符。                                  |
+| TargetValuePtr   | **输出参数**：指向与列绑定的数据缓冲区的指针。SQLFetch函数返回这个缓冲区中的数据。如果此参数为一个空指针，则StrLen_or_IndPtr是一个有效值。 |
+| BufferLength     | TargetValuePtr指向缓冲区的长度，以字节为单位。               |
+| StrLen_or_IndPtr | **输出参数**：缓冲区的长度或指示器指针。若为空值，则未使用任何长度或指示器值。 |
+
+## 返回值
+
+- SQL_SUCCESS：表示调用正确。
+- SQL_SUCCESS_WITH_INFO：表示会有一些警告信息。
+- SQL_ERROR：表示比较严重的错误，如：内存分配失败、建立连接失败等。
+- SQL_INVALID_HANDLE：表示调用无效句柄。其他API的返回值同理。
+
+## 注意事项
+
+当SQLBindCol返回SQL_ERROR或SQL_SUCCESS_WITH_INFO时，通过调用SQLGetDiagRec函数，并将HandleType和Handle参数设置为SQL_HANDLE_STMT和StatementHandle，可得到一个相关的SQLSTATE值，通过SQLSTATE值可以查出调用此函数的具体信息。
+
+## 示例
+
+参见：ODBC -  示例
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-6-SQLBindParameter.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-6-SQLBindParameter.md
new file mode 100644
index 0000000000000000000000000000000000000000..4ef9b9668740cbc5fb278c7109e6ef10ed66f458
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-6-SQLBindParameter.md
@@ -0,0 +1,59 @@
+---
+title: SQLBindParameter
+summary: SQLBindParameter
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLBindParameter
+
+## 功能描述
+
+将一条SQL语句中的一个参数标志和一个缓冲区绑定起来。
+
+## 原型
+
+```c
+SQLRETURN SQLBindParameter(SQLHSTMT       StatementHandle,
+                           SQLUSMALLINT   ParameterNumber,
+                           SQLSMALLINT    InputOutputType,
+                           SQLSMALLINT    ValuetType,
+                           SQLSMALLINT    ParameterType,
+                           SQLULEN    ColumnSize,
+                           SQLSMALLINT    DecimalDigits,
+                           SQLPOINTER     ParameterValuePtr,
+                           SQLLEN     BufferLength,
+                           SQLLEN     *StrLen_or_IndPtr);
+```
+
+## 参数
+
+**表 1**  SQLBindParameter
+
+| **关键词**        | **参数说明**                                                 |
+| :---------------- | :----------------------------------------------------------- |
+| StatementHandle   | 语句句柄。                                                   |
+| ParameterNumber   | 参数序号，起始为1，依次递增。                                |
+| InputOutputType   | 输入输出参数类型。                                           |
+| ValueType         | 参数的C数据类型。                                            |
+| ParameterType     | 参数的SQL数据类型。                                          |
+| ColumnSize        | 列的大小或相应参数标记的表达式。                             |
+| DecimalDigits     | 列的十进制数字或相应参数标记的表达式。                       |
+| ParameterValuePtr | 指向存储参数数据缓冲区的指针。                               |
+| BufferLength      | ParameterValuePtr指向缓冲区的长度，以字节为单位。            |
+| StrLen_or_IndPtr  | 缓冲区的长度或指示器指针。若为空值，则未使用任何长度或指示器值。 |
+
+## 返回值
+
+- SQL_SUCCESS：表示调用正确。
+- SQL_SUCCESS_WITH_INFO：表示会有一些警告信息。
+- SQL_ERROR：表示比较严重的错误，如：内存分配失败、建立连接失败等。
+- SQL_INVALID_HANDLE：表示调用无效句柄。其他API的返回值同理。
+
+## 注意事项
+
+当SQLBindParameter返回SQL_ERROR或SQL_SUCCESS_WITH_INFO时，通过调用SQLGetDiagRec函数，并将HandleType和Handle参数设置为SQL_HANDLE_STMT和StatementHandle，可得到一个相关的SQLSTATE值，通过SQLSTATE值可以查出调用此函数的具体信息。
+
+## 示例
+
+参见：ODBC - 示例
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-7-SQLColAttribute.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-7-SQLColAttribute.md
new file mode 100644
index 0000000000000000000000000000000000000000..a63134806f54e4873517dfbc76a14fad4e8780bb
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-7-SQLColAttribute.md
@@ -0,0 +1,53 @@
+---
+title: SQLColAttribute
+summary: SQLColAttribute
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLColAttribute
+
+## 功能描述
+
+返回结果集中一列的描述符信息。
+
+## 原型
+
+```c
+SQLRETURN SQLColAttibute(SQLHSTMT        StatementHandle,
+                         SQLUSMALLINT    ColumnNumber,
+                         SQLUSMALLINT    FieldIdentifier,
+                         SQLPOINTER      CharacterAtrriburePtr,
+                         SQLSMALLINT     BufferLength,
+                         SQLSMALLINT     *StringLengthPtr,
+                         SQLLEN       *NumericAttributePtr);
+```
+
+## 参数
+
+**表 1** SQLColAttribute参数
+
+| **关键字**            | **参数说明**                                                 |
+| :-------------------- | :----------------------------------------------------------- |
+| StatementHandle       | 语句句柄。                                                   |
+| ColumnNumber          | 要检索字段的列号，起始为1，依次递增。                        |
+| FieldIdentifier       | IRD中ColumnNumber行的字段。                                  |
+| CharacterAttributePtr | **输出参数**：一个缓冲区指针，返回FieldIdentifier字段值。    |
+| BufferLength          | - 如果FieldIdentifier是一个ODBC定义的字段，而且CharacterAttributePtr指向一个字符串或二进制缓冲区，则此参数为该缓冲区的长度。<br/>- 如果FieldIdentifier是一个ODBC定义的字段，而且CharacterAttributePtr指向一个整数，则会忽略该字段。 |
+| StringLengthPtr       | **输出参数**：缓冲区指针，存放*CharacterAttributePtr中字符类型数据的字节总数，对于非字符类型，忽略BufferLength的值。 |
+| NumericAttributePtr   | **输出参数**：指向一个整型缓冲区的指针，返回IRD中ColumnNumber行FieldIdentifier字段的值。 |
+
+## 返回值
+
+- SQL_SUCCESS：表示调用正确。
+- SQL_SUCCESS_WITH_INFO：表示会有一些警告信息。
+- SQL_ERROR：表示比较严重的错误，如：内存分配失败、建立连接失败等。
+- SQL_INVALID_HANDLE：表示调用无效句柄。其他API的返回值同理。
+
+## 注意事项
+
+当SQLColAttribute返回SQL_ERROR或SQL_SUCCESS_WITH_INFO时，通过调用SQLGetDiagRec函数，并将HandleType和Handle参数设置为SQL_HANDLE_STMT和StatementHandle，可得到一个相关的SQLSTATE值，通过SQLSTATE值可以查出调用此函数的具体信息。
+
+## 示例
+
+参见：ODBC - 示例
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-8-SQLConnect.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-8-SQLConnect.md
new file mode 100644
index 0000000000000000000000000000000000000000..d30141146f9e1b17c52200667cafe9106fa1342a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-8-SQLConnect.md
@@ -0,0 +1,54 @@
+---
+title: SQLConnect
+summary: SQLConnect
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLConnect
+
+## 功能描述
+
+在驱动程序和数据源之间建立连接。连接上数据源之后，可以通过连接句柄访问到所有有关连接数据源的信息，包括程序运行状态、事务处理状态和错误信息。
+
+## 原型
+
+```
+SQLRETURN  SQLConnect(SQLHDBC        ConnectionHandle,
+                      SQLCHAR        *ServerName,
+                      SQLSMALLINT    NameLength1,
+                      SQLCHAR        *UserName,
+                      SQLSMALLINT    NameLength2,
+                      SQLCHAR        *Authentication,
+                      SQLSMALLINT    NameLength3);
+```
+
+## 参数
+
+**表 1** SQLConnect参数
+
+| **关键字**       | **参数说明**                       |
+| :--------------- | :--------------------------------- |
+| ConnectionHandle | 连接句柄，通过SQLAllocHandle获得。 |
+| ServerName       | 要连接数据源的名称。               |
+| NameLength1      | ServerName的长度。                 |
+| UserName         | 数据源中数据库用户名。             |
+| NameLength2      | UserName的长度。                   |
+| Authentication   | 数据源中数据库用户密码。           |
+| NameLength3      | Authentication的长度。             |
+
+## 返回值
+
+- SQL_SUCCESS：表示调用正确。
+- SQL_SUCCESS_WITH_INFO：表示会有一些警告信息。
+- SQL_ERROR：表示比较严重的错误，如：内存分配失败、建立连接失败等。
+- SQL_INVALID_HANDLE：表示调用无效句柄。其他API的返回值同理。
+- SQL_STILL_EXECUTING：表示语句正在执行。
+
+## 注意事项
+
+当调用SQLConnect函数返回SQL_ERROR或SQL_SUCCESS_WITH_INFO时，通过调用SQLGetDiagRec函数，并将HandleType和Handle参数设置为SQL_HANDLE_DBC和ConnectionHandle，可得到一个相关的SQLSTATE值，通过SQLSTATE值可以查出调用此函数的具体信息。
+
+## 示例
+
+参见：ODBC - 示例
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-9-SQLDisconnect.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-9-SQLDisconnect.md
new file mode 100644
index 0000000000000000000000000000000000000000..56df88142e1791887cade8ab7b30bf9321d476d8
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-9-SQLDisconnect.md
@@ -0,0 +1,41 @@
+---
+title: SQLDisconnect
+summary: SQLDisconnect
+author: Guo Huan
+date: 2021-05-17
+---
+
+# SQLDisconnect
+
+## 功能描述
+
+关闭一个与特定连接句柄相关的连接。
+
+## 原型
+
+```
+SQLRETURN SQLDisconnect(SQLHDBC    ConnectionHandle);
+```
+
+## 参数
+
+**表 1** SQLDisconnect参数
+
+| **关键字**       | **参数说明**                       |
+| :--------------- | :--------------------------------- |
+| ConnectionHandle | 连接句柄，通过SQLAllocHandle获得。 |
+
+## 返回值
+
+- SQL_SUCCESS：表示调用正确。
+- SQL_SUCCESS_WITH_INFO：表示会有一些警告信息。
+- SQL_ERROR：表示比较严重的错误，如：内存分配失败、建立连接失败等。
+- SQL_INVALID_HANDLE：表示调用无效句柄。其他API的返回值同理。
+
+## 注意事项
+
+当调用SQLDisconnect函数返回SQL_ERROR或SQL_SUCCESS_WITH_INFO时，通过调用SQLGetDiagRec函数，并将HandleType和Handle参数设置为SQL_HANDLE_DBC和ConnectionHandle，可得到一个相关的SQLSTATE值，通过SQLSTATE值可以查出调用此函数的具体信息。
+
+## 示例
+
+参见：ODBC -> 示例
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/1-development-based-on-libpq.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/1-development-based-on-libpq.md
new file mode 100644
index 0000000000000000000000000000000000000000..d25d46ddd75a01a7ab089bf9b58cd530c453a834
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/1-development-based-on-libpq.md
@@ -0,0 +1,10 @@
+---
+title: 基于libpq开发
+summary: 基于libpq开发
+author: Guo Huan
+date: 2021-04-27
+---
+
+# 基于libpq开发
+
+MogDB未对此接口在应用程序开发场景下的使用做验证。因此对使用此接口做应用程序开发存在的风险未知，故不推荐用户使用此套接口做应用程序开发。推荐用户使用ODBC或JDBC接口来替代。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/1-database-connection-control-functions-overview.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/1-database-connection-control-functions-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..5de97fc9bf4a33402f2791094853c8e47854c506
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/1-database-connection-control-functions-overview.md
@@ -0,0 +1,10 @@
+---
+title: 说明
+summary: 说明
+author: Guo Huan
+date: 2021-05-17
+---
+
+# 说明
+
+数据库连接控制函数控制与MogDB服务器链接的事情。一个应用程序一次可以与多个服务器建立链接，如一个客户端链接多个数据库的场景。每个链接都是用一个从函数PQconnectdb、PQconnectdbParams或PQsetdbLogin获得的PGconn对象表示。注意，这些函数总是返回一个非空的对象指针，除非内存分配失败，会返回一个空的指针。链接建立的接口保存在PGconn对象中，可以调用PQstatus函数来检查一下返回值看看连接是否成功。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/10-PQstatus.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/10-PQstatus.md
new file mode 100644
index 0000000000000000000000000000000000000000..25d748f8edfe89a17312a047fdbe0e5ebe54dc6c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/10-PQstatus.md
@@ -0,0 +1,64 @@
+---
+title: PQstatus
+summary: PQstatus
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQstatus
+
+## 功能描述
+
+返回链接的状态。
+
+## 原型
+
+```
+ConnStatusType PQstatus(const PGconn *conn);
+```
+
+## 参数
+
+**表 1** PQstatus参数
+
+| **关键字** | **参数说明**             |
+| :--------- | :----------------------- |
+| conn       | 指向包含链接的对象指针。 |
+
+## 返回值
+
+ConnStatusType：链接状态的枚举，包括：
+
+```
+CONNECTION_STARTED
+等待进行连接。
+
+CONNECTION_MADE
+连接成功；等待发送。
+
+CONNECTION_AWAITING_RESPONSE
+等待来自服务器的响应。
+
+CONNECTION_AUTH_OK
+已收到认证；等待后端启动结束。
+
+CONNECTION_SSL_STARTUP
+协商SSL加密。
+
+CONNECTION_SETENV
+协商环境驱动的参数设置。
+
+CONNECTION_OK
+链接正常。
+
+CONNECTION_BAD
+链接故障。
+```
+
+## 注意事项
+
+状态可以是多个值之一。但是，在异步连接过程之外只能看到其中两个：CONNECTION_OK和CONNECTION_BAD。与数据库的良好连接状态为CONNECTION_OK。状态表示连接尝试失败CONNECTION_BAD。通常，“正常”状态将一直保持到PQfinish，但通信失败可能会导致状态CONNECTION_BAD过早变为。在这种情况下，应用程序可以尝试通过调用进行恢复PQreset。
+
+## 示例
+
+请参见示例章节。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/2-PQconnectdbParams.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/2-PQconnectdbParams.md
new file mode 100644
index 0000000000000000000000000000000000000000..9dd60513d63c1c2a211db04b9d033e0abb2257c9
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/2-PQconnectdbParams.md
@@ -0,0 +1,42 @@
+---
+title: PQconnectdbParams
+summary: PQconnectdbParams
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQconnectdbParams
+
+## 功能描述
+
+与数据库服务器建立一个新的连接。
+
+## 原型
+
+```
+PGconn *PQconnectdbParams(const char * const *keywords,
+                          const char * const *values,
+                          int expand_dbname);
+```
+
+## 参数
+
+**表 1** PQconnectdbParams参数
+
+| **关键字**    | **参数说明**                                                 |
+| :------------ | :----------------------------------------------------------- |
+| keywords      | 定义为一个字符串的数组，每个都成为一个关键字。               |
+| values        | 给每个关键字一个值。                                         |
+| expand_dbname | 当expand_dbname是非零的时，允许将dbname的关键字值看做一个连接字符串。只有第一个出现的dbname是这样展开的，任何随后的dbname值作为纯数据库名处理。 |
+
+## 返回值
+
+PGconn *：指向包含链接的对象指针，内存在函数内部申请。
+
+## 注意事项
+
+这个函数用从两个NULL结束的数组中来的参数打开一个新的数据库连接。与PQsetdbLogin不同的是，可以不必更换函数签名（名字）就可以扩展参数集，所以建议应用程序中使用这个函数（或者它的类似的非阻塞变种PQconnectStartParams和PQconnectPoll）。
+
+## 示例
+
+请参见示例章节。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/3-PQconnectdb.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/3-PQconnectdb.md
new file mode 100644
index 0000000000000000000000000000000000000000..794a62209c8fc3be595238b5c71da5a388366f42
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/3-PQconnectdb.md
@@ -0,0 +1,39 @@
+---
+title: PQconnectdb
+summary: PQconnectdb
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQconnectdb
+
+## 功能描述
+
+与数据库服务器建立一个新的连接。
+
+## 原型
+
+```
+PGconn *PQconnectdb(const char *conninfo);
+```
+
+## 参数
+
+**表 1** PQconnectdb参数
+
+| **关键字** | **参数说明**                               |
+| :--------- | :----------------------------------------- |
+| conninfo   | 链接字符串，字符串中的字段见链接字符章节。 |
+
+## 返回值
+
+PGconn *：指向包含链接的对象指针，内存在函数内部申请。
+
+## 注意事项
+
+- 这个函数用从一个字符串conninfo来的参数与数据库打开一个新的链接。
+- 传入的参数可以为空，表明使用所有缺省的参数，或者可以包含一个或更多个用空白间隔的参数设置，或者它可以包含一个URL。
+
+## 示例
+
+请参见示例章节。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/4-PQconninfoParse.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/4-PQconninfoParse.md
new file mode 100644
index 0000000000000000000000000000000000000000..bcdd8a497ed93bdef29dbb4c2d657b122f0f8983
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/4-PQconninfoParse.md
@@ -0,0 +1,31 @@
+---
+title: PQconninfoParse
+summary: PQconninfoParse
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQconninfoParse
+
+## 功能描述
+
+根据连接，返回已解析的连接选项。
+
+## 原型
+
+```
+PQconninfoOption* PQconninfoParse(const char* conninfo, char** errmsg);
+```
+
+## 参数
+
+**表 1**
+
+| **关键字** | **参数说明**                                                 |
+| :--------- | :----------------------------------------------------------- |
+| conninfo   | 被传递的字符串。可以为空，这样将会使用默认参数。也可以包含由空格分隔的一个或多个参数设置，还可以包含一个URI。 |
+| errmsg     | 错误信息。                                                   |
+
+## 返回值
+
+PQconninfoOption类型指针。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/5-PQconnectStart.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/5-PQconnectStart.md
new file mode 100644
index 0000000000000000000000000000000000000000..c8d0f3e1442d77719d75c0f387148b82de7c15ac
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/5-PQconnectStart.md
@@ -0,0 +1,30 @@
+---
+title: PQconnectStart
+summary: PQconnectStart
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQconnectStart
+
+## 功能描述
+
+与数据库服务器建立一次非阻塞的连接。
+
+## 原型
+
+```
+PGconn* PQconnectStart(const char* conninfo);
+```
+
+## 参数
+
+**表 1**
+
+| **关键字** | **参数说明**                                                 |
+| :--------- | :----------------------------------------------------------- |
+| conninfo   | 连接信息字符串。可以为空，这样将会使用默认参数。也可以包含由空格分隔的一个或多个参数设置，还可以包含一个URI。 |
+
+## 返回值
+
+PGconn类型指针。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/6-PQerrorMessage.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/6-PQerrorMessage.md
new file mode 100644
index 0000000000000000000000000000000000000000..9e83cf7d3f44f079179a5f9d4097f2e0c730248a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/6-PQerrorMessage.md
@@ -0,0 +1,34 @@
+---
+title: PQerrorMessage
+summary: PQerrorMessage
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQerrorMessage
+
+## 功能描述
+
+返回连接上的错误信息。
+
+## 原型
+
+```
+char* PQerrorMessage(const PGconn* conn);
+```
+
+## 参数
+
+**表 1**
+
+| **关键字** | **参数说明** |
+| :--------- | :----------- |
+| conn       | 连接句柄。   |
+
+## 返回值
+
+char类型指针。
+
+## 示例
+
+参见：示例
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/7-PQsetdbLogin.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/7-PQsetdbLogin.md
new file mode 100644
index 0000000000000000000000000000000000000000..aa749776ca67f8991248cd2ee82e5ded01f137f8
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/7-PQsetdbLogin.md
@@ -0,0 +1,51 @@
+---
+title: PQsetdbLogin
+summary: PQsetdbLogin
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQsetdbLogin
+
+## 功能描述
+
+与数据库服务器建立一个新的链接。
+
+## 原型
+
+```
+PGconn *PQsetdbLogin(const char *pghost,
+                     const char *pgport,
+                     const char *pgoptions,
+                     const char *pgtty,
+                     const char *dbName,
+                     const char *login,
+                     const char *pwd);
+```
+
+## 参数
+
+**表 1** PQsetdbLogin参数
+
+| **关键字** | **参数说明**                                                 |
+| :--------- | :----------------------------------------------------------- |
+| pghost     | 要链接的主机名，详见链接字符章节描述的host字段。             |
+| pgport     | 主机服务器的端口号，详见链接字符描述的port字段。             |
+| pgoptions  | 添加命令行选项以在运行时发送到服务器，详见链接字符描述的options字段。 |
+| pgtty      | 忽略（以前，这个选项声明服务器日志的输出方向）               |
+| dbName     | 要链接的数据库名，详见链接字符描述的dbname字段。             |
+| login      | 要链接的用户名，详见链接字符章节描述的user字段。             |
+| pwd        | 如果服务器要求口令认证，所用的口令，详见链接字符描述的password字段。 |
+
+## 返回值
+
+PGconn *：指向包含链接的对象指针，内存在函数内部申请。
+
+## 注意事项
+
+- 该函数为PQconnectdb前身，参数个数固定，未定义参数被调用时使用缺省值，若需要给固定参数设置缺省值，则可赋值NULL或者空字符串。
+- 若dbName中包含“=”或链接URL的有效前缀，则该dbName被看做一个conninfo字符串并传递至PQconnectdb中，其余参数与PQconnectdbParams保持一致。
+
+## 示例
+
+请参见示例章节。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/8-PQfinish.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/8-PQfinish.md
new file mode 100644
index 0000000000000000000000000000000000000000..19afa66d8b59fea7c7a5690412c3edf31d5bc59d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/8-PQfinish.md
@@ -0,0 +1,34 @@
+---
+title: PQfinish
+summary: PQfinish
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQfinish
+
+## 功能描述
+
+关闭与服务器的连接，同时释放被PGconn对象使用的存储器。
+
+## 原型
+
+```
+void PQfinish(PGconn *conn);
+```
+
+## 参数
+
+**表 1** PQfinish参数
+
+| **关键字** | **参数说明**             |
+| :--------- | :----------------------- |
+| conn       | 指向包含链接的对象指针。 |
+
+## 注意事项
+
+若PQstatus判断服务器链接尝试失败，应用程序调用PQfinish释放被PGconn对象使用的存储器，PQfinish调用后PGconn指针不可再次使用。
+
+## 示例
+
+请参见示例章节。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/9-PQreset.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/9-PQreset.md
new file mode 100644
index 0000000000000000000000000000000000000000..899ede04113bb452c6dd44970b16f90628c53c91
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/9-PQreset.md
@@ -0,0 +1,34 @@
+---
+title: PQreset
+summary: PQreset
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQreset
+
+## 功能描述
+
+重置与服务器的通讯端口。
+
+## 原型
+
+```
+void PQreset(PGconn *conn);
+```
+
+## 参数
+
+**表 1** PQreset参数
+
+| **关键字** | **参数说明**             |
+| :--------- | :----------------------- |
+| conn       | 指向包含链接的对象指针。 |
+
+## 注意事项
+
+此函数将关闭与服务器的连接并且试图与同一个服务器重建新的连接，并使用所有前面使用过的参数。该函数在链接异常后进行故障恢复时很有用。
+
+## 示例
+
+请参见示例章节。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/1-PQclear.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/1-PQclear.md
new file mode 100644
index 0000000000000000000000000000000000000000..899cfea8c43c7703c748d1d147ad3dfe0083d90c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/1-PQclear.md
@@ -0,0 +1,34 @@
+---
+title: PQclear
+summary: PQclear
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQclear
+
+## 功能描述
+
+释放与PGresult相关联的存储空间，任何不再需要的查询结果都应该用PQclear释放掉。
+
+## 原型
+
+```
+void PQclear(PGresult *res);
+```
+
+## 参数
+
+**表 1** PQclear参数
+
+| **关键字** | **参数说明**             |
+| :--------- | :----------------------- |
+| res        | 包含查询结果的对象指针。 |
+
+## 注意事项
+
+PGresult不会自动释放，当提交新的查询时它并不消失，甚至断开连接后也不会。要删除它，必须调用PQclear，否则则会有内存泄漏。
+
+## 示例
+
+请参见示例章节。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/10-PQntuples.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/10-PQntuples.md
new file mode 100644
index 0000000000000000000000000000000000000000..4cd9138677f97ce50af00ebeda5923cc3e437ee6
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/10-PQntuples.md
@@ -0,0 +1,34 @@
+---
+title: PQntuples
+summary: PQntuples
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQntuples
+
+## 功能描述
+
+返回查询结果中的行（元组）数。因为它返回一个整数结果，在 32 位操作系统上大型的结果集可能使返回值溢出。
+
+## 原型
+
+```
+int PQntuples(const PGresult *res);
+```
+
+## 参数
+
+**表 1** PQntuples参数
+
+| **关键字** | **参数说明**   |
+| :--------- | :------------- |
+| res        | 操作结果句柄。 |
+
+## 返回值
+
+int类型数字
+
+## 示例
+
+参见：示例
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/11-PQprepare.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/11-PQprepare.md
new file mode 100644
index 0000000000000000000000000000000000000000..7dbb5a0a6188fa64c7b8a86169cf2449ae4605dd
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/11-PQprepare.md
@@ -0,0 +1,50 @@
+---
+title: PQprepare
+summary: PQprepare
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQprepare
+
+## 功能描述
+
+用给定的参数提交请求，创建一个预备语句，然后等待结束。
+
+## 原型
+
+```
+PGresult *PQprepare(PGconn *conn,
+                    const char *stmtName,
+                    const char *query,
+                    int nParams,
+                    const Oid *paramTypes);
+```
+
+## 参数
+
+**表 1** PQprepare参数
+
+| **关键字** | **参数说明**             |
+| :--------- | :----------------------- |
+| conn       | 指向包含链接的对象指针。 |
+| stmtName   | 需要执行的*stmt*名称。   |
+| query      | 需要执行的查询字符串。   |
+| nParams    | 参数个数。               |
+| paramTypes | 声明参数类型的数组。     |
+
+## 返回值
+
+PGresult：包含查询结果的对象指针。
+
+## 注意事项
+
+- PQprepare创建一个为PQexecPrepared执行用的预备语句，本特性支持命令的重复执行，不需要每次都进行解析和规划。PQprepare仅在协议3.0及以后的连接中支持，使用协议2.0时，PQprepare将失败。
+- 该函数从查询字符串创建一个名为stmtName的预备语句，该查询字符串必须包含一个SQL命令。stmtName可以是”“来创建一个未命名的语句，在这种情况下，任何预先存在的未命名的语句都将被自动替换；否则，如果在当前会话中已经定义了语句名称，则这是一个错误。如果使用了任何参数，那么在查询中将它们称为$1,$2等。nParams是在paramTypes[]数组中预先指定类型的参数的数量。（当nParams为0时，数组指针可以为NULL） paramTypes[]通过OID指定要分配给参数符号的数据类型。如果paramTypes为NULL ，或者数组中的任何特定元素为零，服务器将按照对非类型化字面字符串的相同方式为参数符号分配数据类型。另外，查询可以使用数字高于nParams的参数符号；还将推断这些符号的数据类型。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+> 通过执行SQLPREPARE语句，还可以创建与PQexecPrepared一起使用的预备语句。此外，虽然没有用于删除预备语句的libpq函数，但是SQL DEALLOCATE语句可用于此目的。
+
+## 示例
+
+请参见示例章节。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/12-PQresultStatus.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/12-PQresultStatus.md
new file mode 100644
index 0000000000000000000000000000000000000000..8e78886ec575cd37147d65e7f3d0ab0ebc1916e8
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/12-PQresultStatus.md
@@ -0,0 +1,72 @@
+---
+title: PQresultStatus
+summary: PQresultStatus
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQresultStatus
+
+## 功能描述
+
+返回命令的结果状态。
+
+## 原型
+
+```
+ExecStatusType PQresultStatus(const PGresult *res);
+```
+
+## 参数
+
+**表 1** PQresultStatus参数
+
+| **关键字** | **参数说明**             |
+| :--------- | :----------------------- |
+| res        | 包含查询结果的对象指针。 |
+
+## 返回值
+
+PQresultStatus：命令执行结果的枚举，包括：
+
+```
+PQresultStatus可以返回下面数值之一：
+PGRES_EMPTY_QUERY
+发送给服务器的字串是空的。
+
+PGRES_COMMAND_OK
+成功完成一个不返回数据的命令。
+
+PGRES_TUPLES_OK
+成功执行一个返回数据的查询（比如SELECT或者SHOW）。
+
+PGRES_COPY_OUT
+（从服务器）Copy Out （拷贝出）数据传输开始。
+
+PGRES_COPY_IN
+Copy In（拷贝入）（到服务器）数据传输开始。
+
+PGRES_BAD_RESPONSE
+服务器的响应无法理解。
+
+PGRES_NONFATAL_ERROR
+发生了一个非致命错误（通知或者警告）。
+
+PGRES_FATAL_ERROR
+发生了一个致命错误。
+
+PGRES_COPY_BOTH
+拷贝入/出（到和从服务器）数据传输开始。这个特性当前只用于流复制， 所以这个状态不会在普通应用中发生。
+
+PGRES_SINGLE_TUPLE
+PGresult包含一个来自当前命令的结果元组。 这个状态只在查询选择了单行模式时发生
+```
+
+## 注意事项
+
+- 请注意，恰好检索到零行的SELECT命令仍然显示PGRES_TUPLES_OK。PGRES_COMMAND_OK用于永远不能返回行的命令（插入或更新，不带返回子句等）。PGRES_EMPTY_QUERY响应可能表明客户端软件存在bug。
+- 状态为PGRES_NONFATAL_ERROR的结果永远不会由PQexec或其他查询执行函数直接返回，此类结果将传递给通知处理程序。
+
+## 示例
+
+请参见示例章节。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/2-PQexec.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/2-PQexec.md
new file mode 100644
index 0000000000000000000000000000000000000000..40b9d44f8eb1e0017c78628316801f59060f03cc
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/2-PQexec.md
@@ -0,0 +1,42 @@
+---
+title: PQexec
+summary: PQexec
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQexec
+
+## 功能描述
+
+向服务器提交一条命令并等待结果。
+
+## 原型
+
+```
+PGresult *PQexec(PGconn *conn, const char *command);
+```
+
+## 参数
+
+**表 1** PQexec参数
+
+| **关键字** | **参数说明**             |
+| :--------- | :----------------------- |
+| conn       | 指向包含链接的对象指针。 |
+| command    | 需要执行的查询字符串。   |
+
+## 返回值
+
+PGresult：包含查询结果的对象指针。
+
+## 注意事项
+
+应该调用PQresultStatus函数来检查任何错误的返回值（包括空指针的值，在这种情况下它将返回PGRES_FATAL_ERROR）。使用PQerrorMessage获取有关错误的更多信息。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+> 命令字符串可以包括多个SQL命令（用分号分隔）。在一个PQexec调用中发送的多个查询是在一个事务里处理的，除非在查询字符串里有明确的BEGIN/COMMIT命令把整个字符串分隔成多个事务。请注意，返回的PGresult结构只描述字符串里执行的最后一条命令的结果，如果有一个命令失败，那么字符串处理的过程就会停止，并且返回的PGresult会描述错误条件。
+
+## 示例
+
+请参见示例章节。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/3-PQexecParams.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/3-PQexecParams.md
new file mode 100644
index 0000000000000000000000000000000000000000..f88c7a59661dc5072e27141aed0400ed74a719f6
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/3-PQexecParams.md
@@ -0,0 +1,44 @@
+---
+title: PQexecParams
+summary: PQexecParams
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQexecParams
+
+## 功能描述
+
+执行一个绑定参数的命令。
+
+## 原型
+
+```
+PGresult* PQexecParams(PGconn* conn,
+                       const char* command,
+                       int nParams,
+                       const Oid* paramTypes,
+                       const char* const* paramValues,
+                       const int* paramLengths,
+                       const int* paramFormats,
+                       int resultFormat);
+```
+
+## 参数
+
+**表 1** PQexecParams参数
+
+| **关键字**   | **参数说明**                   |
+| :----------- | :----------------------------- |
+| conn         | 连接句柄。                     |
+| command      | SQL文本串。                    |
+| nParams      | 绑定参数的个数                 |
+| paramTypes   | 绑定参数类型。                 |
+| paramValues  | 绑定参数的值。                 |
+| paramLengths | 参数长度。                     |
+| paramFormats | 参数格式（文本或二进制）。     |
+| resultFormat | 返回结果格式（文本或二进制）。 |
+
+## 返回值
+
+PGresult类型指针。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/4-PQexecParamsBatch.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/4-PQexecParamsBatch.md
new file mode 100644
index 0000000000000000000000000000000000000000..f86d6a2ac6e3fa6ca219838955e8720ae31ca902
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/4-PQexecParamsBatch.md
@@ -0,0 +1,46 @@
+---
+title: PQexecParamsBatch
+summary: PQexecParamsBatch
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQexecParamsBatch
+
+## 功能描述
+
+执行一个批量绑定参数的命令。
+
+## 原型
+
+```
+PGresult* PQexecParamsBatch(PGconn* conn,
+                            const char* command,
+                            int nParams,
+                            int nBatch,
+                            const Oid* paramTypes,
+                            const char* const* paramValues,
+                            const int* paramLengths,
+                            const int* paramFormats,
+                            int resultFormat);
+```
+
+## 参数
+
+**表 1** PQexecParamsBatch参数
+
+| **关键字**   | **参数说明**                   |
+| :----------- | :----------------------------- |
+| conn         | 连接句柄。                     |
+| command      | SQL文本串。                    |
+| nParams      | 绑定参数的个数。               |
+| nBatch       | 批量操作数。                   |
+| paramTypes   | 绑定参数类型。                 |
+| paramValues  | 绑定参数的值。                 |
+| paramLengths | 参数长度。                     |
+| paramFormats | 参数格式（文本或二进制）。     |
+| resultFormat | 返回结果格式（文本或二进制）。 |
+
+## 返回值
+
+PGresult类型指针。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/5-PQexecPrepared.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/5-PQexecPrepared.md
new file mode 100644
index 0000000000000000000000000000000000000000..e524fe03520fab2c5c5ac1500867815df1ceaf4d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/5-PQexecPrepared.md
@@ -0,0 +1,42 @@
+---
+title: PQexecPrepared
+summary: PQexecPrepared
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQexecPrepared
+
+## 功能描述
+
+发送一个请求来用给定参数执行一个预备语句，并且等待结果。
+
+## 原型
+
+```
+PGresult* PQexecPrepared(PGconn* conn,
+                         const char* stmtName,
+                         int nParams,
+                         const char* const* paramValues,
+                         const int* paramLengths,
+                         const int* paramFormats,
+                         int resultFormat);
+```
+
+## 参数
+
+**表 1** PQexecPrepared参数
+
+| **关键字**   | **参数说明**                                                 |
+| :----------- | :----------------------------------------------------------- |
+| conn         | 连接句柄。                                                   |
+| stmtName     | **stmt**名称，可以用”“或者NULL来引用未命名语句，否则它必须是一个现有预备语句的名字。 |
+| nParams      | 参数个数。                                                   |
+| paramValues  | 参数的实际值。                                               |
+| paramLengths | 参数的实际数据长度。                                         |
+| paramFormats | 参数的格式（文本或二进制）。                                 |
+| resultFormat | 结果的格式（文本或二进制）。                                 |
+
+## 返回值
+
+PGresult类型指针。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/6-PQexecPreparedBatch.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/6-PQexecPreparedBatch.md
new file mode 100644
index 0000000000000000000000000000000000000000..83bb4e73c0b2b6f0a100823756cc9448e4a72ee3
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/6-PQexecPreparedBatch.md
@@ -0,0 +1,44 @@
+---
+title: PQexecPreparedBatch
+summary: PQexecPreparedBatch
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQexecPreparedBatch
+
+## 功能描述
+
+发送一个请求来用给定的批量参数执行一个预备语句，并且等待结果。
+
+## 原型
+
+```
+PGresult* PQexecPreparedBatch(PGconn* conn,
+                              const char* stmtName,
+                              int nParams,
+                              int nBatchCount,
+                              const char* const* paramValues,
+                              const int* paramLengths,
+                              const int* paramFormats,
+                              int resultFormat);
+```
+
+## 参数
+
+**表 1** PQexecPreparedBatch参数
+
+| **关键字**   | **参数说明**                                                 |
+| :----------- | :----------------------------------------------------------- |
+| conn         | 连接句柄。                                                   |
+| stmtName     | **stmt**名称，可以用”“或者NULL来引用未命名语句，否则它必须是一个现有预备语句的名字。 |
+| nParams      | 参数个数。                                                   |
+| nBatchCount  | 批量数。                                                     |
+| paramValues  | 参数的实际值。                                               |
+| paramLengths | 参数的实际数据长度。                                         |
+| paramFormats | 参数的格式（文本或二进制）。                                 |
+| resultFormat | 结果的格式（文本或二进制）。                                 |
+
+## 返回值
+
+PGresult类型指针。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/7-PQfname.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/7-PQfname.md
new file mode 100644
index 0000000000000000000000000000000000000000..3f9556794b441943f1afa6963b3e34bd5c0de132
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/7-PQfname.md
@@ -0,0 +1,36 @@
+---
+title: PQfname
+summary: PQfname
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQfname
+
+## 功能描述
+
+返回与给定列号相关联的列名。列号从 0 开始。调用者不应该直接释放该结果。它将在相关的PGresult句柄被传递给PQclear之后被释放。
+
+## 原型
+
+```
+char *PQfname(const PGresult *res,
+              int column_number);
+```
+
+## 参数
+
+**表 1** PQfname参数
+
+| **关键字**    | **参数说明**   |
+| :------------ | :------------- |
+| res           | 操作结果句柄。 |
+| column_number | 列数。         |
+
+## 返回值
+
+char类型指针。
+
+## 示例
+
+参见：示例
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/8-PQgetvalue.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/8-PQgetvalue.md
new file mode 100644
index 0000000000000000000000000000000000000000..5227b0886f9f24a4e45a14920488565cf6d7b602
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/8-PQgetvalue.md
@@ -0,0 +1,42 @@
+---
+title: PQgetvalue
+summary: PQgetvalue
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQgetvalue
+
+## 功能描述
+
+返回一个PGresult的一行的单一域值。行和列号从 0 开始。调用者不应该直接释放该结果。它将在相关的PGresult句柄被传递给PQclear之后被释放。
+
+## 原型
+
+```
+char *PQgetvalue(const PGresult *res,
+                 int row_number,
+                 int column_number);
+```
+
+## 参数
+
+**表 1** PQgetvalue参数
+
+| **关键字**    | **参数说明**   |
+| :------------ | :------------- |
+| res           | 操作结果句柄。 |
+| row_number    | 行数。         |
+| column_number | 列数。         |
+
+## 返回值
+
+对于文本格式的数据，PQgetvalue返回的值是该域值的一种空值结束的字符串表示。
+
+对于二进制格式的数据，该值是由该数据类型的typsend和typreceive函数决定的二进制表示。
+
+如果该域值为空，则返回一个空串。
+
+## 示例
+
+参见：示例
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/9-PQnfields.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/9-PQnfields.md
new file mode 100644
index 0000000000000000000000000000000000000000..618fb7d9c68ecada8590cd5771f26a687ad8704f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/9-PQnfields.md
@@ -0,0 +1,34 @@
+---
+title: PQnfields
+summary: PQnfields
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQnfields
+
+## 功能描述
+
+返回查询结果中每一行的列（域）数。
+
+## 原型
+
+```
+int PQnfields(const PGresult *res);
+```
+
+## 参数
+
+**表 1** PQnfields参数
+
+| **关键字** | **参数说明**   |
+| :--------- | :------------- |
+| res        | 操作结果句柄。 |
+
+## 返回值
+
+int类型数字。
+
+## 示例
+
+参见：示例
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/1-functions-for-asynchronous-command-processing-overview.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/1-functions-for-asynchronous-command-processing-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..f782a8b1d76ce30ce9df1af541827f180eb03ddb
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/1-functions-for-asynchronous-command-processing-overview.md
@@ -0,0 +1,17 @@
+---
+title: 说明
+summary: 说明
+author: Guo Huan
+date: 2021-05-17
+---
+
+# 说明
+
+PQexec函数对普通的同步应用里提交命令已经足够使用。但是它却有几个缺陷，而这些缺陷可能对某些用户很重要：
+
+- PQexec等待命令结束，而应用可能还有其它的工作要做（比如维护用户界面等），此时PQexec可不想阻塞在这里等待响应。
+- 因为客户端应用在等待结果的时候是处于挂起状态的，所以应用很难判断它是否该尝试结束正在进行的命令。
+- PQexec只能返回一个PGresult结构。如果提交的命令字符串包含多个SQL命令，除了最后一个PGresult以外都会被PQexec丢弃。
+- PQexec总是收集命令的整个结果，将其缓存在一个PGresult中。虽然这为应用简化了错误处理逻辑，但是对于包含多行的结果是不切实际的。
+
+不想受到这些限制的应用可以改用下面的函数，这些函数也是构造PQexec的函数：PQsendQuery和PQgetResult。PQsendQueryParams，PQsendPrepare，PQsendQueryPrepared也可以和PQgetResult一起使用。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/2-PQsendQuery.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/2-PQsendQuery.md
new file mode 100644
index 0000000000000000000000000000000000000000..b8c3257dbc4de51c3f06ed2a7fb4de4a852afbf2
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/2-PQsendQuery.md
@@ -0,0 +1,39 @@
+---
+title: PQsendQuery
+summary: PQsendQuery
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQsendQuery
+
+## 功能描述
+
+向服务器提交一个命令而不等待结果。如果查询成功发送则返回1，否则返回0。
+
+## 原型
+
+```c
+int PQsendQuery(PGconn *conn, const char *command);
+```
+
+## 参数
+
+**表 1** PQsendQuery参数
+
+| **关键字** | **参数说明**             |
+| :--------- | :----------------------- |
+| conn       | 指向包含链接的对象指针。 |
+| command    | 需要执行的查询字符串.    |
+
+## 返回值
+
+int：执行结果为1表示成功，0表示失败，失败原因存到conn-&gt;errorMessage中。
+
+## 注意事项
+
+在成功调用PQsendQuery后，调用PQgetResult一次或者多次获取结果。PQgetResult返回空指针表示命令已执行完成，否则不能再次调用PQsendQuery（在同一连接上）。
+
+## 示例
+
+请参见示例章节。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/3-PQsendQueryParams.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/3-PQsendQueryParams.md
new file mode 100644
index 0000000000000000000000000000000000000000..9c5d4587360ce79c1feaed26f34c214a6038abf0
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/3-PQsendQueryParams.md
@@ -0,0 +1,52 @@
+---
+title: PQsendQueryParams
+summary: PQsendQueryParams
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQsendQueryParams
+
+## 功能描述
+
+给服务器提交一个命令和分隔的参数，而不等待结果。
+
+## 原型
+
+```c
+int PQsendQueryParams(PGconn *conn,
+                      const char *command,
+                      int nParams,
+                      const Oid *paramTypes,
+                      const char * const *paramValues,
+                      const int *paramLengths,
+                      const int *paramFormats,
+                      int resultFormat);
+```
+
+## 参数
+
+**表 1** PQsendQueryParams参数
+
+| **关键字**   | **参数说明**             |
+| :----------- | :----------------------- |
+| conn         | 指向包含链接的对象指针。 |
+| command      | 需要执行的查询字符串。   |
+| nParams      | 参数个数。               |
+| paramTypes   | 参数类型。               |
+| paramValues  | 参数值。                 |
+| paramLengths | 参数长度。               |
+| paramFormats | 参数格式。               |
+| resultFormat | 结果的格式。             |
+
+## 返回值
+
+int：执行结果为1表示成功，0表示失败，失败原因存到conn-&gt;errorMessage中。
+
+## 注意事项
+
+该函数等效于PQsendQuery，只是查询参数可以和查询字符串分开声明。函数的参数处理和PQexecParams一样，和PQexecParams类似，它不能在2.0版本的协议连接上工作，并且它只允许在查询字符串里出现一条命令。
+
+## 示例
+
+请参见示例章节。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/4-PQsendPrepare.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/4-PQsendPrepare.md
new file mode 100644
index 0000000000000000000000000000000000000000..cfd6aea6276e072346d5e76842d3b52ba8dae121
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/4-PQsendPrepare.md
@@ -0,0 +1,46 @@
+---
+title: PQsendPrepare
+summary: PQsendPrepare
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQsendPrepare
+
+## 功能描述
+
+发送一个请求，创建一个给定参数的预备语句，而不等待结束。
+
+## 原型
+
+```c
+int PQsendPrepare(PGconn *conn,
+                  const char *stmtName,
+                  const char *query,
+                  int nParams,
+                  const Oid *paramTypes);
+```
+
+## 参数
+
+**表 1** PQsendPrepare参数
+
+| **关键字** | **参数说明**             |
+| :--------- | :----------------------- |
+| conn       | 指向包含链接的对象指针。 |
+| stmtName   | 需要执行的*stmt*名称。   |
+| query      | 需要执行的查询字符串。   |
+| nParams    | 参数个数。               |
+| paramTypes | 声明参数类型的数组。     |
+
+## 返回值
+
+int：执行结果为1表示成功，0表示失败，失败原因存到conn-&gt;errorMessage中。
+
+## 注意事项
+
+该函数为PQprepare的异步版本：如果能够分派请求，则返回1，否则返回0。调用成功后，调用PQgetResult判断服务端是否成功创建了preparedStatement。函数的参数与PQprepare一样处理。与PQprepare一样，它也不能在2.0协议的连接上工作。
+
+## 示例
+
+请参见示例章节。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/5-PQsendQueryPrepared.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/5-PQsendQueryPrepared.md
new file mode 100644
index 0000000000000000000000000000000000000000..43f6f09e1326108a64b7e7f8e43f170d9014ac9d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/5-PQsendQueryPrepared.md
@@ -0,0 +1,50 @@
+---
+title: PQsendQueryPrepared
+summary: PQsendQueryPrepared
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQsendQueryPrepared
+
+## 功能描述
+
+发送一个请求执行带有给出参数的预备语句，不等待结果。
+
+## 原型
+
+```c
+int PQsendQueryPrepared(PGconn *conn,
+                        const char *stmtName,
+                        int nParams,
+                        const char * const *paramValues,
+                        const int *paramLengths,
+                        const int *paramFormats,
+                        int resultFormat);
+```
+
+## 参数
+
+**表 1** PQsendQueryPrepared参数
+
+| **关键字**   | **参数说明**                 |
+| :----------- | :--------------------------- |
+| conn         | 指向包含链接信息的对象指针。 |
+| stmtName     | 需要执行的stmt名称。         |
+| nParams      | 参数个数。                   |
+| paramValues  | 参数值。                     |
+| paramLengths | 参数长度。                   |
+| paramFormats | 参数格式。                   |
+| resultFormat | 结果的格式。                 |
+
+## 返回值
+
+int：执行结果为1表示成功，0表示失败，失败原因存到conn-&gt;error_message中。
+
+## 注意事项
+
+该函数类似于PQsendQueryParams，但是要执行的命令是通过命名一个预先准备的语句来指定的，而不是提供一个查询字符串。该函数的参数与PQexecPrepared一样处理。和PQexecPrepared一样，它也不能在2.0协议的连接上工作。
+
+## 示例
+
+请参见示例章节。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/6-PQflush.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/6-PQflush.md
new file mode 100644
index 0000000000000000000000000000000000000000..6af91b8d6716e0c2e1c3dfe4938a1c00be4c72db
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/6-PQflush.md
@@ -0,0 +1,38 @@
+---
+title: PQflush
+summary: PQflush
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQflush
+
+## 功能描述
+
+尝试将任何排队的输出数据刷新到服务器。
+
+## 原型
+
+```c
+int PQflush(PGconn *conn);
+```
+
+## 参数
+
+**表 1** PQflush参数
+
+| **关键字** | **参数说明**               |
+| :--------- | :------------------------- |
+| conn       | 指向包含链接信息的对象指针 |
+
+## 返回值
+
+int：如果成功（或者如果发送队列为空），则返回0；如果由于某种原因失败，则返回-1；如果发送队列中的所有数据都发送失败，则返回1。（此情况只有在连接为非阻塞时才能发生），失败原因存到conn-&gt;error_message中。
+
+## 注意事项
+
+在非阻塞连接上发送任何命令或数据之后，调用PQflush。如果返回1，则等待套接字变为读或写就绪。如果为写就绪状态，则再次调用PQflush。如果已经读到，调用PQconsumeInput，然后再次调用PQflush。重复，直到PQflush返回0。(必须检查读就绪，并用PQconsumeInput排出输入，因为服务器可以阻止试图向我们发送数据，例如。通知信息，直到我们读完它才会读我们的数据。)一旦PQflush返回0，就等待套接字准备好，然后按照上面描述读取响应。
+
+## 示例
+
+请参见示例章节。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/4-functions-for-canceling-queries-in-progress/1-PQgetCancel.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/4-functions-for-canceling-queries-in-progress/1-PQgetCancel.md
new file mode 100644
index 0000000000000000000000000000000000000000..245cff30927aff34878d924b0131c19702d0e2a4
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/4-functions-for-canceling-queries-in-progress/1-PQgetCancel.md
@@ -0,0 +1,38 @@
+---
+title: PQgetCancel
+summary: PQgetCancel
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQgetCancel
+
+## 功能描述
+
+创建一个数据结构，其中包含取消通过特定数据库连接发出的命令所需的信息。
+
+## 原型
+
+```c
+PGcancel *PQgetCancel(PGconn *conn);
+```
+
+## 参数
+
+**表 1** PQgetCancel参数
+
+| **关键字** | **参数说明**                 |
+| :--------- | :--------------------------- |
+| conn       | 指向包含链接信息的对象指针。 |
+
+## 返回值
+
+PGcancel：指向包含cancel信息对象的指针。
+
+## 注意事项
+
+PQgetCancel创建一个给定PGconn连接对象的PGcancel对象。如果给定的conn是NULL或无效连接，它将返回NULL。PGcancel对象是一个不透明的结构，应用程序不能直接访问它；它只能传递给PQcancel或PQfreeCancel。
+
+## 示例
+
+请参见示例章节。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/4-functions-for-canceling-queries-in-progress/2-PQfreeCancel.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/4-functions-for-canceling-queries-in-progress/2-PQfreeCancel.md
new file mode 100644
index 0000000000000000000000000000000000000000..8627766c98e3d7cea6888074a3a8441672960c0b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/4-functions-for-canceling-queries-in-progress/2-PQfreeCancel.md
@@ -0,0 +1,34 @@
+---
+title: PQfreeCancel
+summary: PQfreeCancel
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQfreeCancel
+
+## 功能描述
+
+释放PQgetCancel创建的数据结构。
+
+## 原型
+
+```c
+void PQfreeCancel(PGcancel *cancel);
+```
+
+## 参数
+
+**表 1** PQfreeCancel参数
+
+| **关键字** | **参数说明**                   |
+| :--------- | :----------------------------- |
+| cancel     | 指向包含cancel信息的对象指针。 |
+
+## 注意事项
+
+PQfreeCancel释放一个由前面的PQgetCancel创建的数据对象。
+
+## 示例
+
+请参见示例章节。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/4-functions-for-canceling-queries-in-progress/3-PQcancel.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/4-functions-for-canceling-queries-in-progress/3-PQcancel.md
new file mode 100644
index 0000000000000000000000000000000000000000..c7e198ff918be86d049ef3430d8206c065359234
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/4-functions-for-canceling-queries-in-progress/3-PQcancel.md
@@ -0,0 +1,41 @@
+---
+title: PQcancel
+summary: PQcancel
+author: Guo Huan
+date: 2021-05-17
+---
+
+# PQcancel
+
+## 功能描述
+
+要求服务器放弃处理当前命令。
+
+## 原型
+
+```c
+int PQcancel(PGcancel *cancel, char *errbuf, int errbufsize);
+```
+
+## 参数
+
+**表 1** PQcancel参数
+
+| **关键字** | **参数说明**                   |
+| :--------- | :----------------------------- |
+| cancel     | 指向包含cancel信息的对象指针。 |
+| errbuf     | 出错保存错误信息的buffer。     |
+| errbufsize | 保存错误信息的buffer大小。     |
+
+## 返回值
+
+int：执行结果为1表示成功，0表示失败，失败原因存到errbuf中。
+
+## 注意事项
+
+- 成功发送并不保证请求将产生任何效果。如果取消有效，当前命令将提前终止并返回错误结果。如果取消失败（例如，因为服务器已经处理完命令），无返回结果。
+- 如果errbuf是信号处理程序中的局部变量，则可以安全地从信号处理程序中调用PQcancel。就PQcancel而言，PGcancel对象是只读的，因此它也可以从一个线程中调用，这个线程与操作PGconn对象线程是分离的。
+
+## 示例
+
+请参见示例章节。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/5-libpq-example.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/5-libpq-example.md
new file mode 100644
index 0000000000000000000000000000000000000000..6c877de27c88f32c8cb9e8215af7be0010627968
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/5-libpq-example.md
@@ -0,0 +1,282 @@
+---
+title: 示例
+summary: 示例
+author: Guo Huan
+date: 2021-05-17
+---
+
+# 示例
+
+## 常用功能示例代码
+
+示例1：
+
+```c
+/*
+ * testlibpq.c
+ */
+#include <stdio.h>
+#include <stdlib.h>
+#include <libpq-fe.h>
+
+static void
+exit_nicely(PGconn *conn)
+{
+    PQfinish(conn);
+    exit(1);
+}
+
+int
+main(int argc, char **argv)
+{
+    const char *conninfo;
+    PGconn     *conn;
+    PGresult   *res;
+    int         nFields;
+    int         i,j;
+
+    /*
+     * 用户在命令行上提供了conninfo字符串的值时使用该值
+     * 否则环境变量或者所有其它连接参数
+     * 都使用缺省值。
+     */
+    if (argc > 1)
+        conninfo = argv[1];
+    else
+        conninfo = "dbname=postgres port=42121 host='10.44.133.171' application_name=test connect_timeout=5 sslmode=allow user='test' password='test_1234'";
+
+    /* 连接数据库 */
+    conn = PQconnectdb(conninfo);
+
+    /* 检查后端连接成功建立 */
+    if (PQstatus(conn) != CONNECTION_OK)
+    {
+        fprintf(stderr, "Connection to database failed: %s",
+                PQerrorMessage(conn));
+        exit_nicely(conn);
+    }
+
+    /*
+     * 测试实例涉及游标的使用时候必须使用事务块
+     *把全部放在一个  "select * from pg_database"
+     * PQexec() 里，过于简单，不推荐使用
+     */
+
+    /* 开始一个事务块 */
+    res = PQexec(conn, "BEGIN");
+    if (PQresultStatus(res) != PGRES_COMMAND_OK)
+    {
+        fprintf(stderr, "BEGIN command failed: %s", PQerrorMessage(conn));
+        PQclear(res);
+        exit_nicely(conn);
+    }
+
+    /*
+     * 在结果不需要的时候PQclear PGresult，以避免内存泄漏
+     */
+    PQclear(res);
+
+    /*
+     * 从系统表 pg_database（数据库的系统目录）里抓取数据
+     */
+    res = PQexec(conn, "DECLARE myportal CURSOR FOR select * from pg_database");
+    if (PQresultStatus(res) != PGRES_COMMAND_OK)
+    {
+        fprintf(stderr, "DECLARE CURSOR failed: %s", PQerrorMessage(conn));
+        PQclear(res);
+        exit_nicely(conn);
+    }
+    PQclear(res);
+
+    res = PQexec(conn, "FETCH ALL in myportal");
+    if (PQresultStatus(res) != PGRES_TUPLES_OK)
+    {
+        fprintf(stderr, "FETCH ALL failed: %s", PQerrorMessage(conn));
+        PQclear(res);
+        exit_nicely(conn);
+    }
+
+    /* 打印属性名称 */
+    nFields = PQnfields(res);
+    for (i = 0; i < nFields; i++)
+        printf("%-15s", PQfname(res, i));
+    printf("\n\n");
+
+    /* 打印行 */
+    for (i = 0; i < PQntuples(res); i++)
+    {
+        for (j = 0; j < nFields; j++)
+            printf("%-15s", PQgetvalue(res, i, j));
+        printf("\n");
+    }
+
+    PQclear(res);
+
+    /* 关闭入口 ... 不用检查错误 ... */
+    res = PQexec(conn, "CLOSE myportal");
+    PQclear(res);
+
+    /* 结束事务 */
+    res = PQexec(conn, "END");
+    PQclear(res);
+
+    /* 关闭数据库连接并清理 */
+    PQfinish(conn);
+
+    return 0;
+}
+```
+
+<br/>
+
+示例2：
+
+```c
+/*
+ * testlibpq2.c
+ *      测试外联参数和二进制I/O。
+ *
+ * 在运行这个例子之前，用下面的命令填充一个数据库
+ *
+ *
+ * CREATE TABLE test1 (i int4, t text);
+ *
+  * INSERT INTO test1 values (2, 'ho there');
+ *
+ * 期望的输出如下
+ *
+ *
+ * tuple 0: got
+ *  i = (4 bytes) 2
+ *  t = (8 bytes) 'ho there'
+ *
+ */
+#include <stdio.h>
+#include <stdlib.h>
+#include <string.h>
+#include <sys/types.h>
+#include <libpq-fe.h>
+
+/* for ntohl/htonl */
+#include <netinet/in.h>
+#include <arpa/inet.h>
+
+static void
+exit_nicely(PGconn *conn)
+{
+    PQfinish(conn);
+    exit(1);
+}
+
+/*
+ * 这个函数打印查询结果，这些结果是二进制格式，从上面的
+ * 注释里面创建的表中抓取出来的
+ */
+static void
+show_binary_results(PGresult *res)
+{
+    int         i;
+    int         i_fnum,
+                t_fnum;
+
+    /* 使用 PQfnumber 来避免对结果中的字段顺序进行假设 */
+    i_fnum = PQfnumber(res, "i");
+    t_fnum = PQfnumber(res, "t");
+
+    for (i = 0; i < PQntuples(res); i++)
+    {
+        char       *iptr;
+        char       *tptr;
+        int         ival;
+
+        /* 获取字段值（忽略可能为空的可能） */
+        iptr = PQgetvalue(res, i, i_fnum);
+        tptr = PQgetvalue(res, i, t_fnum);
+
+        /*
+         * INT4 的二进制表现形式是网络字节序
+         * 建议转换成本地字节序
+         */
+        ival = ntohl(*((uint32_t *) iptr));
+
+        /*
+         * TEXT 的二进制表现形式是文本，因此libpq能够给它附加一个字节零
+         * 把它看做 C 字符串
+         *
+         */
+
+        printf("tuple %d: got\n", i);
+        printf(" i = (%d bytes) %d\n",
+               PQgetlength(res, i, i_fnum), ival);
+        printf(" t = (%d bytes) '%s'\n",
+               PQgetlength(res, i, t_fnum), tptr);
+        printf("\n\n");
+    }
+}
+
+int
+main(int argc, char **argv)
+{
+    const char *conninfo;
+    PGconn     *conn;
+    PGresult   *res;
+    const char *paramValues[1];
+    int         paramLengths[1];
+    int         paramFormats[1];
+    uint32_t    binaryIntVal;
+
+    /*
+     * 如果用户在命令行上提供了参数，
+     * 那么使用该值为conninfo 字符串；否则
+     * 使用环境变量或者缺省值。
+     */
+    if (argc > 1)
+        conninfo = argv[1];
+    else
+        conninfo = "dbname=postgres port=42121 host='10.44.133.171' application_name=test connect_timeout=5 sslmode=allow user='test' password='test_1234'";
+
+    /* 和数据库建立连接 */
+    conn = PQconnectdb(conninfo);
+
+    /* 检查与服务器的连接是否成功建立 */
+    if (PQstatus(conn) != CONNECTION_OK)
+    {
+        fprintf(stderr, "Connection to database failed: %s",
+                PQerrorMessage(conn));
+        exit_nicely(conn);
+    }
+
+    /* 把整数值 "2" 转换成网络字节序 */
+    binaryIntVal = htonl((uint32_t) 2);
+
+    /* 为 PQexecParams 设置参数数组 */
+    paramValues[0] = (char *) &binaryIntVal;
+    paramLengths[0] = sizeof(binaryIntVal);
+    paramFormats[0] = 1;        /* 二进制 */
+
+    res = PQexecParams(conn,
+                       "SELECT * FROM test1 WHERE i = $1::int4",
+                       1,       /* 一个参数 */
+                       NULL,    /* 让后端推导参数类型 */
+                       paramValues,
+                       paramLengths,
+                       paramFormats,
+                       1);      /* 要求二进制结果 */
+
+    if (PQresultStatus(res) != PGRES_TUPLES_OK)
+    {
+        fprintf(stderr, "SELECT failed: %s", PQerrorMessage(conn));
+        PQclear(res);
+        exit_nicely(conn);
+    }
+
+    show_binary_results(res);
+
+    PQclear(res);
+
+    /* 关闭与数据库的连接并清理 */
+    PQfinish(conn);
+
+    return 0;
+}
+```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/6-connection-characters.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/6-connection-characters.md
new file mode 100644
index 0000000000000000000000000000000000000000..3bb6d0fcfc6e4bfe849fea4e75f50d3ebb1e8d7f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4-development-based-on-libpq/2-libpq/6-connection-characters.md
@@ -0,0 +1,27 @@
+---
+title: 链接字符
+summary: 链接字符
+author: Guo Huan
+date: 2021-05-17
+---
+
+# 链接字符
+
+**表 1** 链接字符串
+
+| 字符串              | 描述                                                         |
+| :------------------ | :----------------------------------------------------------- |
+| host                | 要链接的主机名。如果主机名以斜杠开头，则它声明使用Unix域套接字通讯而不是TCP/IP通讯；该值就是套接字文件所存储的目录。如果没有声明host，那么默认是与位于/tmp目录（或者安装MogDB的时候声明的套接字目录）里面的Unix-域套接字链接。在没有Unix域套接字的机器上，默认与localhost链接。 |
+| hostaddr            | 与之链接的主机的IP地址，是标准的IPv4地址格式，比如，172.28.40.9。如果机器支持IPv6，那么也可以使用IPv6的地址。如果声明了一个非空的字符串，那么使用TCP/IP通讯机制。<br/>使用hostaddr取代host可以让应用避免一次主机名查找，这一点对于那些有时间约束的应用来说可能是非常重要的。不过，GSSAPI或SSPI认证方法要求主机名（host）。因此，应用下面的规则：<br/>1. 如果声明了不带hostaddr的host那么就强制进行主机名查找。<br/>2. 如果声明中没有host，hostaddr的值给出服务器网络地址；如果认证方法要求主机名，那么链接尝试将失败。<br/>3. 如果同时声明了host和hostaddr，那么hostaddr的值作为服务器网络地址。host的值将被忽略，除非认证方法需要它，在这种情况下它将被用作主机名。<br/>须知：<br/>- 要注意如果host不是网络地址hostaddr处的服务器名，那么认证很有可能失败。<br/>- 如果主机名（host）和主机地址都没有，那么libpq将使用一个本地的Unix域套接字进行链接；或者是在没有Unix域套接字的机器上，它将尝试与localhost链接。 |
+| port                | 主机服务器的端口号，或者在Unix域套接字链接时的套接字扩展文件名。 |
+| user                | 要链接的用户名，缺省是与运行该应用的用户操作系统名同名的用户。 |
+| dbname              | 数据库名，缺省和用户名相同。                                 |
+| password            | 如果服务器要求口令认证，所用的口令。                         |
+| connect_timeout     | 链接的最大等待时间，以秒计（用十进制整数字符串书写），0或者不声明表示无穷。不建议把链接超时的值设置得小于2秒。 |
+| client_encoding     | 为这个链接设置client_encoding配置参数。除了对应的服务器选项接受的值，你可以使用auto从客户端中的当前环境中确定正确的编码（Unix系统上是LC_CTYPE环境变量）。 |
+| options             | 添加命令行选项以在运行时发送到服务器。                       |
+| application_name    | 为application_name配置参数指定一个值，表明当前用户身份。     |
+| keepalives          | 控制客户端侧的TCP保持激活是否使用。缺省值是1，意思为打开，但是如果不想要保持激活，你可以更改为0，意思为关闭。通过Unix域套接字做的链接忽略这个参数。 |
+| keepalives_idle     | 在TCP应该发送一个保持激活的信息给服务器之后，控制不活动的秒数。0值表示使用系统缺省。通过Unix域套接字做的链接或者如果禁用了保持激活则忽略这个参数。 |
+| keepalives_interval | 在TCP保持激活信息没有被应该传播的服务器承认之后，控制秒数。0值表示使用系统缺省。通过Unix域套接字做的链接或者如果禁用了保持激活则忽略这个参数。 |
+| keepalives_count    | 添加命令行选项以在运行时发送到服务器。例如，设置为-c comm_debug_mode=off，设置guc参数comm_debug_mode参数的会话值为off。 |
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/1-psycopg-based-development.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/1-psycopg-based-development.md
new file mode 100644
index 0000000000000000000000000000000000000000..a5ca06e12a64a78e0da4cbf46449b08e45735180
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/1-psycopg-based-development.md
@@ -0,0 +1,19 @@
+---
+title: 基于Psycopg开发
+summary: 基于Psycopg开发
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# 基于Psycopg开发
+
+Psycopg是一种用于执行SQL语句的PythonAPI，可以为PostgreSQL、GaussDB数据库提供统一访问接口，应用程序可基于它进行数据操作。Psycopg2是对libpq的封装，主要使用C语言实现，既高效又安全。它具有客户端游标和服务器端游标、异步通信和通知、支持“COPY TO/COPY FROM”功能。支持多种类型Python开箱即用，适配PostgreSQL数据类型；通过灵活的对象适配系统，可以扩展和定制适配。Psycopg2兼容Unicode和Python 3。
+
+MogDB数据库提供了对Psycopg2特性的支持，并且支持psycopg2通过SSL模式链接。
+
+**表 1** Psycopg支持平台
+
+| 操作系统    | 平台     |
+| :---------- | :------- |
+| EulerOS 2.5 | x86_64位 |
+| EulerOS 2.8 | ARM64位  |
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/10.1-example-common-operations.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/10.1-example-common-operations.md
new file mode 100644
index 0000000000000000000000000000000000000000..b7f2d0897f2a2cd1aaf9698f0ca3b922345d4090
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/10.1-example-common-operations.md
@@ -0,0 +1,61 @@
+---
+title: 常用操作
+summary: 常用操作
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# 示例：常用操作
+
+```bash
+import psycopg2
+
+#创建连接对象
+conn=psycopg2.connect(database="postgres",user="user",password="password",host="localhost",port=port)
+cur=conn.cursor() #创建指针对象
+
+#创建连接对象（SSl连接）
+conn = psycopg2.connect(dbname="postgres", user="user", password="password", host="localhost", port=port,
+         sslmode="verify-ca", sslcert="client.crt",sslkey="client.key",sslrootcert="cacert.pem")
+注意： 如果sslcert, sslkey,sslrootcert没有填写，默认取当前用户.postgresql目录下对应的client.crt，
+         client.key， root.crt
+
+# 创建表
+cur.execute("CREATE TABLE student(id integer,name varchar,sex varchar);")
+
+#插入数据
+cur.execute("INSERT INTO student(id,name,sex) VALUES(%s,%s,%s)",(1,'Aspirin','M'))
+cur.execute("INSERT INTO student(id,name,sex) VALUES(%s,%s,%s)",(2,'Taxol','F'))
+cur.execute("INSERT INTO student(id,name,sex) VALUES(%s,%s,%s)",(3,'Dixheral','M'))
+
+# 获取结果
+cur.execute('SELECT * FROM student')
+results=cur.fetchall()
+print (results)
+
+# 关闭连接
+conn.commit()
+cur.close()
+conn.close()
+
+psycopg2常用链接方式
+1. conn = psycopg2.connect(dbname="postgres", user="user", password="password", host="localhost", port=port)
+2. conn = psycopg2.connect("dbname=postgres user=user password=password  host=localhost port=port")
+3. 使用日志
+import logging
+import psycopg2
+from psycopg2.extras import LoggingConnection
+
+logging.basicConfig(level=logging.DEBUG) # 日志级别
+logger = logging.getLogger(__name__)
+
+db_settings = {
+    "user": "user",
+    "password": "password",
+    "host": "localhost",
+    "database": "postgres",
+    "port": port
+}
+conn = psycopg2.connect(connection_factory=LoggingConnection, **db_settings)
+conn.initialize(logger)
+```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/1-psycopg2-connect.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/1-psycopg2-connect.md
new file mode 100644
index 0000000000000000000000000000000000000000..6250db45a41862993009daedebb2e301b9c8ac3f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/1-psycopg2-connect.md
@@ -0,0 +1,42 @@
+---
+title: psycopg2.connect()
+summary: psycopg2.connect()
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# psycopg2.connect()
+
+## 功能描述
+
+此方法创建新的数据库会话并返回新的connection对象。
+
+## 原型
+
+```
+conn=psycopg2.connect(dbname="test",user="postgres",password="secret",host="127.0.0.1",port="5432")
+```
+
+## 参数
+
+**表 1** psycopg2.connect参数
+
+| **关键字**  | **参数说明**                          |
+| :---------- | :------------------------------------ |
+| dbname      | 数据库名称                            |
+| user        | 用户名                                |
+| password    | 密码                                  |
+| host        | 数据库IP地址，默认为UNIX socket类型。 |
+| port        | 连接端口号，默认为5432。              |
+| sslmode     | ssl模式，ssl连接时用。                |
+| sslcert     | 客户端证书路径，ssl连接时用。         |
+| sslkey      | 客户端密钥路径，ssl连接时用。         |
+| sslrootcert | 根证书路径，ssl连接时用。             |
+
+## 返回值
+
+connection对象（连接MogDB数据库实例的对象）。
+
+## 示例
+
+请参见[示例：常用操作](10.1-example-common-operations)。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/10-connection-close.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/10-connection-close.md
new file mode 100644
index 0000000000000000000000000000000000000000..66dde59f37a466564cc724cdeddff0b7a0eda2b3
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/10-connection-close.md
@@ -0,0 +1,32 @@
+---
+title: connection.close()
+summary: connection.close()
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# connection.close()
+
+## 功能描述
+
+此方法关闭数据库连接。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **注意：** 此方法关闭数据库连接，并不自动调用commit()。如果只是关闭数据库连接而不调用commit()方法，那么所有更改将会丢失。
+
+## 原型
+
+```
+connection.close()
+```
+
+## 参数
+
+无
+
+## 返回值
+
+无
+
+## 示例
+
+请参见[示例：常用操作](10.1-example-common-operations)。
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/2-connection-cursor.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/2-connection-cursor.md
new file mode 100644
index 0000000000000000000000000000000000000000..4af41606a4c3c8961dee913027cb0ba8c50d18e2
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/2-connection-cursor.md
@@ -0,0 +1,37 @@
+---
+title: connection.cursor()
+summary: connection.cursor()
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# connection.cursor()
+
+## 功能描述
+
+此方法用于返回新的cursor对象。
+
+## 原型
+
+```
+cursor(name=None, cursor_factory=None, scrollable=None, withhold=False)
+```
+
+## 参数
+
+**表 1** connection.cursor参数
+
+| **关键字**     | **参数说明**                       |
+| :------------- | :--------------------------------- |
+| name           | cursor名称，默认为None。           |
+| cursor_factory | 用于创造非标准cursor，默认为None。 |
+| scrollable     | 设置SCROLL选项，默认为None。       |
+| withhold       | 设置HOLD选项，默认为False。        |
+
+## 返回值
+
+cursor对象（用于整个数据库使用Python编程的cursor）。
+
+## 示例
+
+请参见[示例：常用操作](10.1-example-common-operations)。
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/3-cursor-execute-query-vars-list.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/3-cursor-execute-query-vars-list.md
new file mode 100644
index 0000000000000000000000000000000000000000..fc05de6fc57b99ab4111cf9489228199517363dd
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/3-cursor-execute-query-vars-list.md
@@ -0,0 +1,35 @@
+---
+title: cursor.execute(query,vars_list)
+summary: cursor.execute(query,vars_list)
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# cursor.execute(query,vars_list)
+
+## 功能描述
+
+此方法执行被参数化的SQL语句（即占位符，而不是SQL文字）。psycopg2模块支持用％s标志的占位符。
+
+## 原型
+
+```
+curosr.execute(query,vars_list)
+```
+
+## 参数
+
+**表 1** curosr.execute参数
+
+| **关键字** | **参数说明**                    |
+| :--------- | :------------------------------ |
+| query      | 待执行的sql语句。               |
+| vars_list  | 变量列表，匹配query中%s占位符。 |
+
+## 返回值
+
+无
+
+## 示例
+
+请参见[示例：常用操作](10.1-example-common-operations)。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/4-curosr-executemany-query-vars-list.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/4-curosr-executemany-query-vars-list.md
new file mode 100644
index 0000000000000000000000000000000000000000..c2a8b2557876aca4fe212c8052dd4b9ecfb204c2
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/4-curosr-executemany-query-vars-list.md
@@ -0,0 +1,35 @@
+---
+title: curosr.executemany(query,vars_list)
+summary: curosr.executemany(query,vars_list)
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# curosr.executemany(query,vars_list)
+
+## 功能描述
+
+此方法执行SQL命令所有参数序列或序列中的SQL映射。
+
+## 原型
+
+```
+curosr.executemany(query,vars_list)
+```
+
+## 参数
+
+**表 1** curosr.executemany参数
+
+| **关键字** | **参数说明**                    |
+| :--------- | :------------------------------ |
+| query      | 待执行的SQL语句。               |
+| vars_list  | 变量列表，匹配query中%s占位符。 |
+
+## 返回值
+
+无
+
+## 示例
+
+请参见[示例：常用操作](10.1-example-common-operations)。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/5-connection-commit.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/5-connection-commit.md
new file mode 100644
index 0000000000000000000000000000000000000000..3f5df3e5f177c9dbd1edf99bf6e407870c027f09
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/5-connection-commit.md
@@ -0,0 +1,32 @@
+---
+title: connection.commit()
+summary: connection.commit()
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# connection.commit()
+
+## 功能描述
+
+此方法将当前挂起的事务提交到数据库。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **注意：** 默认情况下，Psycopg在执行第一个命令之前打开一个事务：如果不调用commit()，任何数据操作的效果都将丢失。
+
+## 原型
+
+```
+connection.commit()
+```
+
+## 参数
+
+无
+
+## 返回值
+
+无
+
+## 示例
+
+请参见[示例：常用操作](10.1-example-common-operations)。
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/6-connection-rollback.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/6-connection-rollback.md
new file mode 100644
index 0000000000000000000000000000000000000000..b843725a8fad3c84942e1ae14ab7090a2774fa3f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/6-connection-rollback.md
@@ -0,0 +1,32 @@
+---
+title: connection.rollback()
+summary: connection.rollback()
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# connection.rollback()
+
+## 功能描述
+
+此方法回滚当前挂起事务。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **注意：** 执行关闭连接“close()”而不先提交更改“commit()”将导致执行隐式回滚。
+
+## 原型
+
+```
+connection.rollback()
+```
+
+## 参数
+
+无
+
+## 返回值
+
+无
+
+## 示例
+
+请参见[示例：常用操作](10.1-example-common-operations)。
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/7-cursor-fetchone.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/7-cursor-fetchone.md
new file mode 100644
index 0000000000000000000000000000000000000000..38a4b57e71292c0a17044ac692d75db7f6b7fc17
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/7-cursor-fetchone.md
@@ -0,0 +1,30 @@
+---
+title: cursor.fetchone()
+summary: cursor.fetchone()
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# cursor.fetchone()
+
+## 功能描述
+
+此方法提取查询结果集的下一行，并返回一个元组。
+
+## 原型
+
+```
+cursor.fetchone()
+```
+
+## 参数
+
+无
+
+## 返回值
+
+单个元组，为结果集的第一条结果，当没有更多数据可用时，返回为“None”。
+
+## 示例
+
+请参见[示例：常用操作](10.1-example-common-operations)。
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/8-cursor-fetchall.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/8-cursor-fetchall.md
new file mode 100644
index 0000000000000000000000000000000000000000..f7483b1efa98c456bf20a659f9285fee9046a9ac
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/8-cursor-fetchall.md
@@ -0,0 +1,30 @@
+---
+title: cursor.fetchall()
+summary: cursor.fetchall()
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# cursor.fetchall()
+
+## 功能描述
+
+此方法获取查询结果的所有（剩余）行，并将它们作为元组列表返回。
+
+## 原型
+
+```
+cursor.fetchall()
+```
+
+## 参数
+
+无
+
+## 返回值
+
+元组列表，为结果集的所有结果。空行时则返回空列表。
+
+## 示例
+
+请参见[示例：常用操作](10.1-example-common-operations)。
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/9-cursor-close.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/9-cursor-close.md
new file mode 100644
index 0000000000000000000000000000000000000000..ba67eb854847fe3f71136d287c026a3b1962c74b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/9-cursor-close.md
@@ -0,0 +1,30 @@
+---
+title: cursor.close()
+summary: cursor.close()
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# cursor.close()
+
+## 功能描述
+
+此方法关闭当前连接的游标。
+
+## 原型
+
+```
+cursor.close()
+```
+
+## 参数
+
+无
+
+## 返回值
+
+无
+
+## 示例
+
+请参见[示例：常用操作](10.1-example-common-operations)。
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/2-psycopg-package.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/2-psycopg-package.md
new file mode 100644
index 0000000000000000000000000000000000000000..bb52ebf568553df5baef1fe2846f6c9361057b8c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/2-psycopg-package.md
@@ -0,0 +1,15 @@
+---
+title: Psycopg包
+summary: Psycopg包
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# Psycopg包
+
+从发布包中获取，包名为GaussDB-Kernel-VxxxRxxxCxx-操作系统版本号-64bit-Python.tar.gz。
+
+解压后有两个文件夹：
+
+- psycopg2：psycopg2库文件。
+- lib：lib库文件。
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/3.1-development-process.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/3.1-development-process.md
new file mode 100644
index 0000000000000000000000000000000000000000..149bfb6baef6926a0943d40793eb3ee83cf5ca2a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/3.1-development-process.md
@@ -0,0 +1,12 @@
+---
+title: 开发流程
+summary: 开发流程
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# 开发流程
+
+**图 1** psycopg2开发应用程序的流程
+
+![ODBC开发应用程序的流程](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/development-process-1.png)
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/4-loading-a-driver.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/4-loading-a-driver.md
new file mode 100644
index 0000000000000000000000000000000000000000..d2c79b5aee635382fbf82d4c874b115b536422e6
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/4-loading-a-driver.md
@@ -0,0 +1,21 @@
+---
+title: 加载驱动
+summary: 加载驱动
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# 加载驱动
+
+- 在使用驱动之前，需要做如下操作：
+
+  1. 先解压版本对应驱动包，使用root用户将psycopg2拷贝到python安装目录下的site-packages文件夹下。
+  2. 修改psycopg2目录权限为755。
+  3. 将psycopg2目录添加到环境变量$PYTHONPATH，并使之生效。
+  4. 对于非数据库用户，需要将解压后的lib目录，配置在LD_LIBRARY_PATH中。
+
+- 在创建数据库连接之前，需要先加载如下数据库驱动程序：
+
+  ```
+  import  psycopg2
+  ```
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/5.1-connecting-to-a-database.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/5.1-connecting-to-a-database.md
new file mode 100644
index 0000000000000000000000000000000000000000..43e237a33a7e7e643fd11b74b63f3087cb5013d8
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/5.1-connecting-to-a-database.md
@@ -0,0 +1,11 @@
+---
+title: 连接数据库
+summary: 连接数据库
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# 连接数据库
+
+1. 使用psycopg2.connect函数获得connection对象。
+2. 使用connection对象创建cursor对象。
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/6-executing-sql-statements.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/6-executing-sql-statements.md
new file mode 100644
index 0000000000000000000000000000000000000000..c53b2464c59f17b16d5b05fc410c374d42a30f2e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/6-executing-sql-statements.md
@@ -0,0 +1,11 @@
+---
+title: 执行SQL语句
+summary: 执行SQL语句
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# 执行SQL语句
+
+1. 构造操作语句，使用%s作为占位符，执行时psycopg2会用参数值智能替换掉占位符。可以添加RETURNING子句，来得到自动生成的字段值。
+2. 使用cursor.execute方法来操作一行，使用cursor.executemany方法来操作多行。
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/7-processing-the-result-set.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/7-processing-the-result-set.md
new file mode 100644
index 0000000000000000000000000000000000000000..4e06c48e2957467f5692927992a0f99b19960988
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/7-processing-the-result-set.md
@@ -0,0 +1,11 @@
+---
+title: 处理结果集
+summary: 处理结果集
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# 处理结果集
+
+1. cursor.fetchone()：这种方法提取查询结果集的下一行，返回一个序列，没有数据可用时则返回空。
+2. cursor.fetchall()：这个例程获取所有查询结果（剩余）行，返回一个列表。空行时则返回空列表。
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/8-closing-the-connection.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/8-closing-the-connection.md
new file mode 100644
index 0000000000000000000000000000000000000000..ca2ca8df23433881837ccbb39ed5cb3bde9e1962
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/8-closing-the-connection.md
@@ -0,0 +1,12 @@
+---
+title: 关闭连接
+summary: 关闭连接
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# 关闭连接
+
+在使用数据库连接完成相应的数据操作后，需要关闭数据库连接。关闭数据库连接可以直接调用其close方法，如connection.close()。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **注意：** 此方法关闭数据库连接，并不自动调用commit()。如果只是关闭数据库连接而不调用commit()方法，那么所有更改将会丢失。
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/9-connecting-to-the-database-using-ssl.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/9-connecting-to-the-database-using-ssl.md
new file mode 100644
index 0000000000000000000000000000000000000000..9c9859ec47092f2ef8f1afc95267d7311c2baf02
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/4.1-psycopg-based-development/9-connecting-to-the-database-using-ssl.md
@@ -0,0 +1,37 @@
+---
+title: 连接数据库
+summary: 连接数据库
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# 连接数据库（SSL方式）
+
+用户通过psycopy2连接MogDB服务器时，可以通过开启SSL加密客户端和服务器之间的通讯。在使用SSL时，默认用户已经获取了服务端和客户端所需要的证书和私钥文件，关于证书等文件的获取请参考Openssl相关文档和命令。
+
+1. 使用*.ini文件（python的configparser包可以解析这种类型的配置文件）保存数据库连接的配置信息。
+
+2. 在连接选项中添加SSL连接相关参数：sslmode，sslcert，sslkey，sslrootcert。
+
+   - sslmode：可选项见[表1](#table1.1)。
+
+   - sslcert：客户端证书路径。
+
+   - sslkey：客户端密钥路径。
+
+   - sslrootcert：根证书路径。
+
+3. 使用psycopg2.connect函数获得connection对象。
+
+4. 使用connection对象创建cursor对象。
+
+**表 1** sslmode的可选项及其描述 <a id=table1.1> </a>
+
+| sslmode     | 是否会启用SSL加密 | 描述                                                         |
+| :---------- | :---------------- | :----------------------------------------------------------- |
+| disable     | 否                | 不适用SSL安全连接。                                          |
+| allow       | 可能              | 如果数据库服务器要求使用，则可以使用SSL安全加密连接，但不验证数据库服务器的真实性。 |
+| prefer      | 可能              | 如果数据库支持，那么首选使用SSL连接，但不验证数据库服务器的真实性。 |
+| require     | 是                | 必须使用SSL安全连接，但是只做了数据加密，而并不验证数据库服务器的真实性。 |
+| verify-ca   | 是                | 必须使用SSL安全连接。                                        |
+| verify-full | 是                | 必须使用SSL安全连接，目前MogDB 暂不支持。           |
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/5-commissioning.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/5-commissioning.md
new file mode 100644
index 0000000000000000000000000000000000000000..6c6c3555f1c3036b820ff2b814f5f51ceced21d1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/5-commissioning.md
@@ -0,0 +1,40 @@
+---
+title: 调试
+summary: 调试
+author: Guo Huan
+date: 2021-04-27
+---
+
+# 调试
+
+用户可以根据自己的需要，通过修改实例数据目录下的postgresql.conf文件中特定的配置参数来控制日志的输出，从而更好的了解数据库的运行状态。
+
+可调整的配置参数请参见[表1](#配置参数)。
+
+**<a id="配置参数">表 1 </a>**配置参数
+
+| 参数名称                           | <span style="white-space:nowrap;">描述</span> | 取值范围                                                     | 备注                                                         |
+| :--------------------------------- | :------------------------- | :---------------------------- | :---------------------------|
+| client_min_messages                | 配置发送到客户端信息的级别。                                 | - DEBUG5<br />- DEBUG4<br />- DEBUG3<br />- DEBUG2<br />- DEBUG1<br />- LOG<br />- NOTICE<br />WARNING<br />- ERROR<br />- FATAL<br />- PANIC<br />默认值: NOTICE 。 | 设置级别后，发送到客户端的信息包含所设级别及以下所有低级别会发送的信息。级别越低，发送的信息越少。 |
+| log_min_messages                   | 配置写到服务器日志里信息的级别。                             | - DEBUG5<br />- DEBUG4<br />- DEBUG3<br />- DEBUG2<br />- DEBUG1<br />- INFO<br />- NOTICE<br />- WARNING<br />- ERROR<br />- LOG<br />- FATAL<br />- PANIC<br />默认值: WARNING。 | 指定某一级别后，写到日志的信息包含所有更高级别会输出的信息。级别越高，服务器日志的信息越少。 |
+| log_min_error_statement            | 配置写到服务器日志中错误SQL语句的级别。                      | - DEBUG5<br />- DEBUG4<br />- DEBUG3<br />- DEBUG2<br />- DEBUG1<br />- INFO<br />- NOTICE<br />- WARNING<br />- ERROR<br />- FATAL<br />- PANIC<br />缺省值: ERROR。 | 所有导致一个特定级别（或者更高级别）错误的SQL语句都将记录在服务器日志中。只有系统管理员可以修改该参数。 |
+| log_min_duration_statement         | 配置语句执行持续的最短时间。如果某个语句的持续时间大于或者等于设置的毫秒数，则会在日志中记录该语句及其持续时间。打开这个选项可以方便地跟踪需要优化的查询。 | INT类型。<br />默认值: 30min。<br />单位: 毫秒。             | 设置为-1表示关闭这个功能。只有系统管理员可以修改该参数。     |
+| log_connections/log_disconnections | 配置是否在每次会话连接或结束时向服务器日志里打印一条信息。   | - on: 每次会话连接或结束时向日志里打印一条信息。<br />- off: 每次会话连接或结束时不向日志里打印信息。<br />默认值: off。 | -                                                            |
+| log_duration                       | 配置是否记录每个已完成语句的持续时间。                       | - on: 记录每个已完成语句的持续时间。<br />- off: 不记录已完成语句的持续时间。默认值: on 。 | 只有系统管理员可以修改该参数。                               |
+| log_statement                      | 配置日志中记录哪些SQL语句。                                  | - none: 不记录任何SQL语句。<br />- ddl: 记录数据定义语句。<br />- mod: 记录数据定义语句和数据操作语句。<br />- all : 记录所有语句。<br />默认值:  none。 | 只有系统管理员可以修改该参数。                               |
+| log_hostname                       | 配置是否记录主机名。                                         | - on: 记录主机名。<br />- off: 不记录主机名。<br />默认值: off。 | 缺省时，连接日志只记录所连接主机的IP地址。打开这个选项会同时记录主机名。该参数同时影响 "查看审计结果"、GS_WLM_SESSION_HISTORY、PG_STAT_ACTIVITY和log_line_prefix参数。 |
+
+上表有关参数级别的说明请参见[表2](#日志级别参数说明)。
+
+**<a id="日志级别参数说明">表 2</a>** 日志级别参数说明
+
+| 级别       | 说明                                                                   |
+| :--------- | :--------------------------------------------------------------------- |
+| DEBUG[1-5] | 提供开发人员使用的信息。5级为最高级别，依次类推，1级为最低级别。       |
+| INFO       | 提供用户隐含要求的信息。如在VACUUM VERBOSE过程中的信息。               |
+| NOTICE     | 提供可能对用户有用的信息。如长标识符的截断，作为主键一部分创建的索引。 |
+| WARNING    | 提供给用户的警告。如在事务块范围之外的COMMIT。                         |
+| ERROR      | 报告导致当前命令退出的错误。                                           |
+| LOG        | 报告一些管理员感兴趣的信息。如检查点活跃性。                           |
+| FATAL      | 报告导致当前会话终止的原因。                                           |
+| PANIC      | 报告导致所有会话退出的原因。                                           |
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/dev/6-appendix.md b/product/zh/docs-mogdb/v3.0/developer-guide/dev/6-appendix.md
new file mode 100644
index 0000000000000000000000000000000000000000..e3ed879a500f22ca7d126955ecc9244754466917
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/dev/6-appendix.md
@@ -0,0 +1,107 @@
+---
+title: 附录
+summary: 附录
+author: Guo Huan
+date: 2021-04-27
+---
+
+# 附录
+
+## <a id="PG_STAT_ACTIVITY">**表 1**</a> PG_STAT_ACTIVITY字段
+
+| 名称             | 类型                     | 描述 |
+| :--------------- | :----------------------- | :---------------------------------------------|
+| datid            | oid                      | 用户会话在后台连接到的数据库OID。              |
+| datname          | name                     | 用户会话在后台连接到的数据库名称。             |
+| pid              | bigint                   | 后台线程ID。                                   |
+| sessionid        | bigint                   | 会话ID。                                       |
+| usesysid         | oid                      | 登录该后台的用户OID。                          |
+| usename          | name                     | 登录该后台的用户名。                           |
+| application_name | text                     | 连接到该后台的应用名。                         |
+| client_addr      | inet                     | 连接到该后台的客户端的IP地址。 如果此字段是null，它表明通过服务器机器上UNIX套接字连接客户端或者这是内部进程，如autovacuum。|
+| client_hostname  | text                     | 客户端的主机名，这个字段是通过client_addr的反向DNS查找得到。这个字段只有在启动log_hostname且使用IP连接时才非空。                   |
+| client_port      | integer                  | 客户端用于与后台通讯的TCP端口号，如果使用Unix套接字，则为-1。              |
+| backend_start    | timestamp with time zone | 该过程开始的时间，即当客户端连接服务器时。     |
+| xact_start       | timestamp with time zone | 启动当前事务的时间，如果没有事务是活跃的，则为null。如果当前查询是首个事务，则这列等同于query_start列。                            |
+| query_start      | timestamp with time zone | 开始当前活跃查询的时间， 如果state的值不是active，则这个值是上一个查询的开始时间。                                                 |
+| state_change     | timestamp with time zone | 上次状态改变的时间。                           |
+| waiting          | Boolean                  | 如果后台当前正等待锁则为true。                 |
+| enqueue          | text                     | 该字段不支持。                                 |
+| state            | text                     | 该后台当前总体状态。可能值是: <br />- active: 后台正在执行一个查询。<br />- idle: 后台正在等待一个新的客户端命令。<br />- idle in transaction: 后台在事务中，但事务中没有语句在执行。<br />- idle in transaction (aborted): 后台在事务中，但事务中有语句执行失败。<br />- fastpath function call: 后台正在执行一个fast-path函数。<br />- disabled: 如果后台禁用track_activities，则报告这个状态。<br />说明:<br />普通用户只能查看到自己帐户所对应的会话状态。即其他帐户的state信息为空。例如以judy用户连接数据库后，在pg_stat_activity中查看到的普通用户joe及初始用户omm的state信息为空: <br /> *SELECT datname, usename, usesysid, state,pid FROM pg_stat_activity;* <br /> datname | usename | usesysid | state | pid ----+---+----+---+------ postgres | omm | 10 |  | 139968752121616 postgres | omm | 10 |  | 139968903116560 db_tpcc | judy | 16398 | active | 139968391403280 postgres | omm | 10 |  | 139968643069712 postgres | omm | 10 |  | 139968680818448 postgres | joe | 16390 |  | 139968563377936 (6 rows)` |
+| resource_pool    | name                     | 用户使用的资源池。                             |
+| query_id         | bigint                   | 查询语句的ID。                                 |
+| query            | text                     | 该后台的最新查询。如果state状态是active（活跃的），此字段显示当前正在执行的查询。所有其他情况表示上一个查询。                      |
+| connection_info  | text                     | json格式字符串，记录当前连接数据库的驱动类型、驱动版本号、当前驱动的部署路径、进程属主用户等信息（参见connection_info）。          |
+
+## <a id="GS_WLM">**表 2** </a>GS_WLM_SESSION_HISTORY的字段
+
+| 名称                | 类型                     | 描述|
+| ------------------- | ------------------- | ---------------- |
+| datid               | oid                      | 连接后端的数据库OID。 |
+| dbname              | text                     | 连接后端的数据库名称。                                |
+| schemaname          | text                     | 模式的名称。                                          |
+| nodename            | text                     | 语句执行的数据库节点名称。                            |
+| username            | text                     | 连接到后端的用户名。                                  |
+| application_name    | text                     | 连接到后端的应用名。                                  |
+| client_addr         | inet                     | 连接到后端的客户端的IP地址。 如果此字段是null，它表明通过服务器机器上UNIX套接字连接客户端或者这是内部进程，如autovacuum。 |
+| client_hostname     | text                     | 客户端的主机名，这个字段是通过client_addr的反向DNS查找得到。这个字段只有在启动log_hostname且使用IP连接时才非空。                                  |
+| client_port         | integer                  | 客户端用于与后端通讯的TCP端口号，如果使用Unix套接字，则为-1。          |
+| query_band          | text                     | 用于标示作业类型，可通过GUC参数query_band进行设置，默认为空字符串。    |
+| block_time          | bigint                   | 语句执行前的阻塞时间，包含语句解析和优化时间，单位ms。|
+| start_time          | timestamp with time zone | 语句执行的开始时间。                                  |
+| finish_time         | timestamp with time zone | 语句执行的结束时间。                                  |
+| duration            | bigint                   | 语句实际执行的时间，单位ms。                          |
+| estimate_total_time | bigint                   | 语句预估执行时间，单位ms。                            |
+| status              | text                     | 语句执行结束状态: 正常为finished，异常为aborted。     |
+| abort_info          | text                     | 语句执行结束状态为aborted时显示异常信息。             |
+| resource_pool       | text                     | 用户使用的资源池。                                    |
+| control_group       | text                     | 该字段不支持                                          |
+| estimate_memory     | integer                  | 语句估算内存大小。                                    |
+| min_peak_memory     | integer                  | 语句在数据库节点上的最小内存峰值，单位MB。            |
+| max_peak_memory     | integer                  | 语句在数据库节点上的最大内存峰值，单位MB。            |
+| average_peak_memory | integer                  | 语句执行过程中的内存使用平均值，单位MB。              |
+| memory_skew_percent | integer                  | 语句数据库节点间的内存使用倾斜率。                    |
+| spill_info          | text                     | 语句在数据库节点上的下盘信息: <br />- None: 数据库节点均未下盘。<br />- All: 数据库节点均下盘。<br />- [a:b]: 数量为b个数据库节点中有a个数据库节点下盘。|
+| min_spill_size      | integer                  | 若发生下盘，数据库节点上下盘的最小数据量，单位MB，默认为0。            |
+| max_spill_size      | integer                  | 若发生下盘，数据库节点上下盘的最大数据量，单位MB，默认为0。            |
+| average_spill_size  | integer                  | 若发生下盘，数据库节点上下盘的平均数据量，单位MB，默认为0。            |
+| spill_skew_percent  | integer                  | 若发生下盘，数据库节点间下盘倾斜率。                  |
+| min_dn_time         | bigint                   | 语句在数据库节点上的最小执行时间，单位ms。            |
+| max_dn_time         | bigint                   | 语句在数据库节点上的最大执行时间，单位ms。            |
+| average_dn_time     | bigint                   | 语句在数据库节点上的平均执行时间，单位ms。            |
+| dntime_skew_percent | integer                  | 语句在数据库节点间的执行时间倾斜率。                  |
+| min_cpu_time        | bigint                   | 语句在数据库节点上的最小CPU时间，单位ms。             |
+| max_cpu_time        | bigint                   | 语句在数据库节点上的最大CPU时间，单位ms。             |
+| total_cpu_time      | bigint                   | 语句在数据库节点上的CPU总时间，单位ms。               |
+| cpu_skew_percent    | integer                  | 语句在数据库节点间的CPU时间倾斜率。                   |
+| min_peak_iops       | integer                  | 语句在数据库节点上的每秒最小IO峰值（列存单位是次/s，行存单位是万次/s）。                  |
+| max_peak_iops       | integer                  | 语句在数据库节点上的每秒最大IO峰值（列存单位是次/s，行存单位是万次/s）。                  |
+| average_peak_iops   | integer                  | 语句在数据库节点上的每秒平均IO峰值（列存单位是次/s，行存单位是万次/s）。                  |
+| iops_skew_percent   | integer                  | 语句在数据库节点间的IO倾斜率。                        |
+| warning             | text                     | 主要显示如下几类告警信息: <br />- Spill file size large than 256MB<br />- Broadcast size large than 100MB<br />- Early spill<br />- Spill times is greater than 3<br />- Spill on memory adaptive<br />- Hash table conflict |
+| queryid             | bigint                   | 语句执行使用的内部query id。                          |
+| query               | text                     | 执行的语句。                                          |
+| query_plan          | text                     | 语句的执行计划。                                      |
+| node_group          | text                     | 该字段不支持。                                        |
+| cpu_top1_node_name  | text                     | 当前数据库节点名称。                                  |
+| cpu_top2_node_name  | text                     | 该字段不支持。                                        |
+| cpu_top3_node_name  | text                     | 该字段不支持。                                        |
+| cpu_top4_node_name  | text                     | 该字段不支持。                                        |
+| cpu_top5_node_name  | text                     | 该字段不支持。                                        |
+| mem_top1_node_name  | text                     | 当前数据库节点名称。                                  |
+| mem_top2_node_name  | text                     | 该字段不支持。                                        |
+| mem_top3_node_name  | text                     | 该字段不支持。                                        |
+| mem_top4_node_name  | text                     | 该字段不支持。                                        |
+| mem_top5_node_name  | text                     | 该字段不支持。                                        |
+| cpu_top1_value      | bigint                   | 当前数据库节点cpu使用率。                             |
+| cpu_top2_value      | bigint                   | 该字段不支持。                                        |
+| cpu_top3_value      | bigint                   | 该字段不支持。                                        |
+| cpu_top4_value      | bigint                   | 该字段不支持。                                        |
+| cpu_top5_value      | bigint                   | 该字段不支持。                                        |
+| mem_top1_value      | bigint                   | 当前数据库节点内存使用量。                            |
+| mem_top2_value      | bigint                   | 该字段不支持。                                        |
+| mem_top3_value      | bigint                   | 该字段不支持。                                        |
+| mem_top4_value      | bigint                   | 该字段不支持。                                        |
+| mem_top5_value      | bigint                   | 该字段不支持。                                        |
+| top_mem_dn          | text                     | 当前数据库节点内存使用量信息。                        |
+| top_cpu_dn          | text                     | 当前数据库节点cpu使用量信息。                         |
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-design/constraint-design.md b/product/zh/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-design/constraint-design.md
new file mode 100644
index 0000000000000000000000000000000000000000..9874315902a33c8d61b1e793d33251574d1f24f0
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-design/constraint-design.md
@@ -0,0 +1,37 @@
+---
+title: 约束设计
+summary: 约束设计
+author: Guo Huan
+date: 2021-10-14
+---
+
+# 约束设计
+
+## DEFAULT和NULL约束
+
+- 【建议】如果能够从业务层面补全字段值，那么，就不建议使用DEFAULT约束，避免数据加载时产生不符合预期的结果。
+- 【建议】给明确不存在NULL值的字段加上NOT NULL约束，优化器会在特定场景下对其进行自动优化。
+- 【建议】给可以显式命名的约束显式命名。除了NOT NULL和DEFAULT约束外，其他约束都可以显式命名。
+
+## 局部聚簇
+
+Partial Cluster Key（局部聚簇，简称PCK）是列存表的一种局部聚簇技术，在MogDB中，使用PCK可以通过min/max稀疏索引实现事实表快速过滤扫描。PCK的选取遵循以下原则：
+
+- 【关注】一张表上只能建立一个PCK，一个PCK可以包含多列，但是一般不建议超过2列。
+- 【建议】在查询中的简单表达式过滤条件上创建PCK。这种过滤条件一般形如col op const，其中col为列名，op为操作符 =、>、>=、<=、<，const为常量值。
+- 【建议】在满足上面条件的前提下，选择distinct值比较多的列上建PCK。
+
+## 唯一约束
+
+- 【关注】行存表、列存表均支持唯一约束。
+- 【建议】从命名上明确标识唯一约束，例如，命名为“UNI+构成字段”。
+
+## 主键约束
+
+- 【关注】行存表、列存表均支持主键约束。
+- 【建议】从命名上明确标识主键约束，例如，将主键约束命名为 “PK+字段名”。
+
+## 检查约束
+
+- 【关注】行存表支持检查约束，而列存表不支持。
+- 【建议】从命名上明确标识检查约束，例如，将检查约束命名为 “CK+字段名”。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-design/database-and-schema-design.md b/product/zh/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-design/database-and-schema-design.md
new file mode 100644
index 0000000000000000000000000000000000000000..1493db0a50fe9867df716daa3fa92235faca5e54
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-design/database-and-schema-design.md
@@ -0,0 +1,27 @@
+---
+title: Database和Schema设计
+summary: Database和Schema设计
+author: Guo Huan
+date: 2021-10-14
+---
+
+# Database和Schema设计
+
+MogDB中可以使用Database和Schema实现业务的隔离，区别在于Database的隔离更加彻底，各个Database之间共享资源极少，可实现连接隔离、权限隔离等，Database之间无法直接互访。Schema隔离的方式共用资源较多，可以通过grant与revoke语法便捷地控制不同用户对各Schema及其下属对象的权限。
+
+- 从便捷性和资源共享效率上考虑，推荐使用Schema进行业务隔离。
+- 建议系统管理员创建Schema和Database，再赋予相关用户对应的权限。
+
+## Database设计建议
+
+- 【规则】在实际业务中，根据需要创建新的Database，不建议直接使用数据库实例默认的postgres数据库。
+- 【建议】一个数据库实例内，用户自定义的Database数量建议不超过3个。
+- 【建议】为了适应全球化的需求，使数据库编码能够存储与表示绝大多数的字符，建议创建Database的时候使用UTF-8编码。
+- 【关注】创建Database时，需要重点关注字符集编码（ENCODING）和兼容性（DBCOMPATIBILITY）两个配置项。MogDB支持A、B和PG三种兼容模式，分别表示兼容Oracle语法、MySQL语法和PostgreSQL语法，不同兼容模式下的语法行为存在一定差异，默认为A兼容模式。
+- 【关注】Database的owner默认拥有该Database下所有对象的所有权限，包括删除权限。删除权限影响较大，请谨慎使用。
+
+## Schema设计建议
+
+- 【关注】如果该用户不具有sysadmin权限或者不是该Schema的owner，要访问Schema下的对象，需要同时给用户赋予Schema的usage权限和对象的相应权限。
+- 【关注】如果要在Schema下创建对象，需要授予操作用户该Schema的create权限。
+- 【关注】Schema的owner默认拥有该Schema下对象的所有权限，包括删除权限。删除权限影响较大，请谨慎使用。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-design/field-design.md b/product/zh/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-design/field-design.md
new file mode 100644
index 0000000000000000000000000000000000000000..55b455b1be95378baf6522dfaf2c4657020995d1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-design/field-design.md
@@ -0,0 +1,40 @@
+---
+title: 字段设计
+summary: 字段设计
+author: Guo Huan
+date: 2021-10-14
+---
+
+# 字段设计
+
+## 选择数据类型
+
+在字段设计时，基于查询效率的考虑，一般遵循以下原则：
+
+- 【建议】尽量使用高效数据类型。
+
+  选择数值类型时，在满足业务精度的情况下，选择数据类型的优先级从高到低依次为整数、浮点数、NUMERIC。
+
+- 【建议】当多个表存在逻辑关系时，表示同一含义的字段应该使用相同的数据类型。
+
+- 【建议】对于字符串数据，建议使用变长字符串数据类型，并指定最大长度。请务必确保指定的最大长度大于需要存储的最大字符数，避免超出最大长度时出现字符截断现象。除非明确知道数据类型为固定长度字符串，否则，不建议使用CHAR(n)、BPCHAR(n)、NCHAR(n)、CHARACTER(n)。
+
+  关于字符串类型的详细说明，请参见下文。
+
+## 常用字符串类型介绍
+
+在进行字段设计时，需要根据数据特征选择相应的数据类型。字符串类型在使用时比较容易混淆，下表列出了MogDB中常见的字符串类型：
+
+**表 1** 常用字符串类型
+
+| **名称**             | **描述**                                                     | **最大存储空间** |
+| :------------------- | :----------------------------------------------------------- | :--------------- |
+| CHAR(n)              | 定长字符串，n描述了存储的字节长度，如果输入的字符串字节格式小于n，那么后面会自动用空字符补齐至n个字节。 | 10MB             |
+| CHARACTER(n)         | 定长字符串，n描述了存储的字节长度，如果输入的字符串字节格式小于n，那么后面会自动用空字符补齐至n个字节。 | 10MB             |
+| NCHAR(n)             | 定长字符串，n描述了存储的字节长度，如果输入的字符串字节格式小于n，那么后面会自动用空字符补齐至n个字节。 | 10MB             |
+| BPCHAR(n)            | 定长字符串，n描述了存储的字节长度，如果输入的字符串字节格式小于n，那么后面会自动用空字符补齐至n个字节。 | 10MB             |
+| VARCHAR(n)           | 变长字符串，n描述了可以存储的最大字节长度。                  | 10MB             |
+| CHARACTER VARYING(n) | 变长字符串，n描述了可以存储的最大字节长度；此数据类型和VARCHAR(n)是同一数据类型的不同表达形式。 | 10MB             |
+| VARCHAR2(n)          | 变长字符串，n描述了可以存储的最大字节长度，此数据类型是为兼容Oracle类型新增的，行为和VARCHAR(n)一致。 | 10MB             |
+| NVARCHAR2(n)         | 变长字符串，n描述了可以存储的最大字节长度。                  | 10MB             |
+| TEXT                 | 不限长度（不超过1GB-8203字节）变长字符串。                   | 1GB-8203字节     |
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-design/table-design.md b/product/zh/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-design/table-design.md
new file mode 100644
index 0000000000000000000000000000000000000000..9dcd2ba1d85b57ada8a6accf44560e293a2672c7
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-design/table-design.md
@@ -0,0 +1,81 @@
+---
+title: 表设计
+summary: 表设计
+author: Guo Huan
+date: 2021-10-14
+---
+
+# 表设计
+
+MogDB是分布式架构。数据分布在各个DN上。总体上讲，良好的表设计需要遵循以下原则：
+
+- 【关注】将表数据均匀分布在各个DN上。数据均匀分布，可以防止数据在部分DN上集中分布，从而导致因存储倾斜造成数据库实例有效容量下降。通过选择合适的分布列，可以避免数据倾斜。
+- 【关注】将表的扫描压力均匀分散在各个DN上。避免扫描压力集中在部分DN上，而导致性能瓶颈。例如，在事实表上使用等值过滤条件时，将会导致扫描压力不均匀。
+- 【关注】减少需要扫描的数据量。通过分区表的剪枝机制可以大幅减少数据的扫描量。
+- 【关注】尽量减少随机I/O。通过聚簇/局部聚簇可以实现热数据的连续存储，将随机I/O转换为连续I/O，从而减少扫描的I/O代价。
+- 【关注】尽量避免数据shuffle。shuffle，是指在物理上，数据从一个节点，传输到另一个节点。shuffle占用了大量宝贵的网络资源，减小不必要的数据shuffle，可以减少网络压力，使数据的处理本地化，提高数据库实例的性能和可支持的并发度。通过对关联条件和分组条件的仔细设计，能够尽可能地减少不必要的数据shuffle。
+
+## 选择存储方案
+
+【建议】表的存储类型是表定义设计的第一步，客户业务类型是决定表的存储类型的主要因素，表存储类型的选择依据请参考表1。
+
+**表 1** 表的存储类型及场景
+
+| 存储类型 | 适用场景                                                     |
+| :------- | :----------------------------------------------------------- |
+| 行存     | - 点查询（返回记录少，基于索引的简单查询）。<br />- 增、删、改操作较多的场景。 |
+| 列存     | - 统计分析类查询（关联、分组操作较多的场景）。<br />- 即席查询（查询条件不确定，行存表扫描难以使用索引）。 |
+
+## 选择分布方案
+
+【建议】表的分布方式的选择一般遵循以下原则：
+
+**表 2** 表的分布方式及使用场景
+
+| 分布方式    | 描述                                             | 适用场景                       |
+| :---------- | :----------------------------------------------- | :----------------------------- |
+| Hash        | 表数据通过Hash方式散列到数据库实例中的所有DN上。 | 数据量较大的事实表。           |
+| Replication | 数据库实例中每一个DN都有一份全量表数据。         | 维度表、数据量较小的事实表。   |
+| Range       | 表数据对指定列按照范围进行映射，分布到对应DN。   | 用户需要自定义分布规则的场景。 |
+| List        | 表数据对指定列按照具体值进行映射，分布到对应DN。 | 用户需要自定义分布规则的场景。 |
+
+## 选择分区方案
+
+当表中的数据量很大时，应当对表进行分区，一般需要遵循以下原则：
+
+- 【建议】使用具有明显区间性的字段进行分区，比如日期、区域等字段上建立分区。
+- 【建议】分区名称应当体现分区的数据特征。例如，关键字+区间特征。
+- 【建议】将分区上边界的分区值定义为MAXVALUE，以防止可能出现的数据溢出。
+
+典型的分区表定义如下：
+
+```sql
+CREATE TABLE staffS_p1
+(
+  staff_ID       NUMBER(6) not null,
+  FIRST_NAME     VARCHAR2(20),
+  LAST_NAME      VARCHAR2(25),
+  EMAIL          VARCHAR2(25),
+  PHONE_NUMBER   VARCHAR2(20),
+  HIRE_DATE      DATE,
+  employment_ID  VARCHAR2(10),
+  SALARY         NUMBER(8,2),
+  COMMISSION_PCT NUMBER(4,2),
+  MANAGER_ID     NUMBER(6),
+  section_ID     NUMBER(4)
+)
+PARTITION BY RANGE (HIRE_DATE)
+(
+   PARTITION HIRE_19950501 VALUES LESS THAN ('1995-05-01 00:00:00'),
+   PARTITION HIRE_19950502 VALUES LESS THAN ('1995-05-02 00:00:00'),
+   PARTITION HIRE_maxvalue VALUES LESS THAN (MAXVALUE)
+);
+```
+
+## 选择分布键
+
+Hash表的分布键选取至关重要，如果分布键选择不当，可能会导致数据倾斜，从而导致查询时，I/O负载集中在部分DN上，影响整体查询性能。因此，在确定Hash表的分布策略之后，需要对表数据进行倾斜性检查，以确保数据的均匀分布。分布键的选择一般需要遵循以下原则：
+
+- 【建议】选作分布键的字段取值应该比较离散，以便数据能在各个DN上均匀分布。当单个字段无法满足离散条件时，可以考虑使用多个字段一起作为分布键。一般情况下，可以考虑选择表的主键作为分布键。例如，在人员信息表中选择证件号码作为分布键。
+- 【建议】在满足第一条原则的情况下，尽量不要选取在查询中存在常量过滤条件的字段作为分布键。例如，在表dwcjk相关的查询中，字段zqdh存在常量过滤条件“zqdh='000001'”，那么就应当尽量不选择zqdh字段做为分布键。
+- 【建议】在满足前两条原则的情况，尽量选择查询中的关联条件为分布键。当关联条件作为分布键时，join任务的相关数据都分布在DN本地，将极大减少DN之间的数据流动代价。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-design/view-and-joined-table-design.md b/product/zh/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-design/view-and-joined-table-design.md
new file mode 100644
index 0000000000000000000000000000000000000000..b6d071ac74dd31eea255c823382d16813f23d741
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-design/view-and-joined-table-design.md
@@ -0,0 +1,19 @@
+---
+title: 视图和关联表设计
+summary: 视图和关联表设计
+author: Guo Huan
+date: 2021-10-14
+---
+
+# 视图和关联表设计
+
+## 视图设计
+
+- 【建议】除非视图之间存在强依赖关系，否则不建议视图嵌套。
+- 【建议】视图定义中尽量避免排序操作。
+
+## 关联表设计
+
+- 【建议】表之间的关联字段应该尽量少。
+- 【建议】关联字段的数据类型应该保持一致。
+- 【建议】关联字段在命名上，应该可以明显体现出关联关系。例如，采用同样名称来命名。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-naming-conventions.md b/product/zh/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-naming-conventions.md
new file mode 100644
index 0000000000000000000000000000000000000000..797973d296669c9b3563a7c199108cddb1b95e20
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/database-object-naming-conventions.md
@@ -0,0 +1,31 @@
+---
+title: 数据库对象命名
+summary: 数据库对象命名
+author: Guo Huan
+date: 2021-10-14
+---
+
+# 数据库对象命名
+
+数据库对象命名需要满足约束：非时序表长度不超过63个字符，时序表长度不超过53个字符，以字母或下划线开头，中间字符可以是字母、数字、下划线、$、#。
+
+- 【建议】避免使用保留或者非保留关键字命名数据库对象。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 可以使用select * from pg_get_keywords()查询MogDB的关键字，或者在[关键字](2-keywords)章节中查看。
+
+- 【建议】避免使用双引号括起来的字符串来定义数据库对象名称，除非需要限制数据库对象名称的大小写。数据库对象名称大小写敏感会使定位问题难度增加。
+
+- 【建议】数据库对象命名风格务必保持统一。
+
+  - 增量开发的业务系统或进行业务迁移的系统，建议遵守历史的命名风格。
+  - 建议使用多个单词组成，以下划线分割。
+  - 数据库对象名称建议能够望文知意，尽量避免使用自定义缩写（可以使用通用的术语缩写进行命名）。例如，在命名中可以使用具有实际业务含义的英文词汇或汉语拼音，但规则应该在数据库实例范围内保持一致。
+  - 变量名的关键是要具有描述性，即变量名称要有一定的意义，变量名要有前缀标明该变量的类型。
+
+- 【建议】表对象的命名应该可以表征该表的重要特征。例如，在表对象命名时区分该表是普通表、临时表还是非日志表：
+
+  - 普通表名按照数据集的业务含义命名。
+  - 临时表以“tmp_+后缀”命名。
+  - 非日志表以“ul_+后缀”命名。
+  - 外表以“f_+后缀”命名。
+  - 不创建以redis_为前缀的数据库对象。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/overview-of-development-and-design-proposal.md b/product/zh/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/overview-of-development-and-design-proposal.md
new file mode 100644
index 0000000000000000000000000000000000000000..782d0075bac40d8026d31ae415a8ea42649a40a3
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/overview-of-development-and-design-proposal.md
@@ -0,0 +1,15 @@
+---
+title: 开发设计建议概述
+summary: 开发设计建议概述
+author: Guo Huan
+date: 2021-10-14
+---
+
+# 开发设计建议概述
+
+本开发设计建议约定数据库建模和数据库应用程序开发过程中，应当遵守的设计规范。依据这些规范进行建模，能够更好的契合MogDB的分布式处理架构，输出更高效的业务SQL代码。
+
+本开发设计建议中所陈述的“建议”和“关注”含义如下：
+
+- **建议**：用户应当遵守的设计规则。遵守这些规则，能够保证业务的高效运行；违反这些规则，将导致业务性能的大幅下降或某些业务逻辑错误。
+- **关注**：在业务开发过程中客户需要注意的细则。用于标识容易导致客户理解错误的知识点（实际上遵守SQL标准的SQL行为），或者程序中潜在的客户不易感知的默认行为。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/sql-compilation.md b/product/zh/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/sql-compilation.md
new file mode 100644
index 0000000000000000000000000000000000000000..046ede24aafd1b615b45be13ae5f9207ef86a370
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/sql-compilation.md
@@ -0,0 +1,143 @@
+---
+title: SQL编写
+summary: SQL编写
+author: Guo Huan
+date: 2021-10-14
+---
+
+# SQL编写
+
+## DDL
+
+- 【建议】在MogDB中，建议DDL（建表、comments等）操作统一执行，在批处理作业中尽量避免DDL操作。避免大量并发事务对性能的影响。
+- 【建议】在非日志表（unlogged table）使用完后，立即执行数据清理（truncate）操作。因为在异常场景下，MogDB不保证非日志表（unlogged table）数据的安全性。
+- 【建议】临时表和非日志表的存储方式建议和基表相同。当基表为行存（列存）表时，临时表和非日志表也推荐创建为行存（列存）表，可以避免行列混合关联带来的高计算代价。
+- 【建议】索引字段的总长度不超过50字节。否则，索引大小会膨胀比较严重，带来较大的存储开销，同时索引性能也会下降。
+- 【建议】不要使用DROP…CASCADE方式删除对象，除非已经明确对象间的依赖关系，以免误删。
+
+## 数据加载和卸载
+
+- 【建议】在insert语句中显式给出插入的字段列表。例如：
+
+  ```sql
+  INSERT INTO task(name,id,comment) VALUES ('task1','100','第100个任务');
+  ```
+
+- 【建议】在批量数据入库之后，或者数据增量达到一定阈值后，建议对表进行analyze操作，防止统计信息不准确而导致的执行计划劣化。
+
+- 【建议】如果要清理表中的所有数据，建议使用truncate table方式，不要使用delete table方式。delete table方式删除性能差，且不会释放那些已经删除了的数据占用的磁盘空间。
+
+## 类型转换
+
+- 【建议】在需要数据类型转换（不同数据类型进行比较或转换）时，使用强制类型转换，以防隐式类型转换结果与预期不符。
+- 【建议】在查询中，对常量要显式指定数据类型，不要试图依赖任何隐式的数据类型转换。
+- 【关注】若sql_compatibility参数设置为A，在导入数据时，空字符串会自动转化为NULL。如果需要保留空字符串需要sql_compatibility参数设置为C。
+
+## 查询操作
+
+- 【建议】除ETL程序外，应该尽量避免向客户端返回大量结果集的操作。如果结果集过大，应考虑业务设计是否合理。
+
+- 【建议】使用事务方式执行DDL和DML操作。例如，truncate table、update table、delete table、drop table等操作，一旦执行提交就无法恢复。对于这类操作，建议使用事务进行封装，必要时可以进行回滚。
+
+- 【建议】在查询编写时，建议明确列出查询涉及的所有字段，不建议使用“SELECT *”这种写法。一方面基于性能考虑，尽量减少查询输出列；另一方面避免增删字段对前端业务兼容性的影响。
+
+- 【建议】在访问表对象时带上schema前缀，可以避免因schema切换导致访问到非预期的表。
+
+- 【建议】超过3张表或视图进行关联（特别是full join）时，执行代价难以估算。建议使用WITH TABLE AS语句创建中间临时表的方式增加SQL语句的可读性。
+
+- 【建议】尽量避免使用笛卡尔积和Full join。这些操作会造成结果集的急剧膨胀，同时其执行性能也很低。
+
+- 【关注】NULL值的比较只能使用IS NULL或者IS NOT NULL的方式判断，其他任何形式的逻辑判断都返回NULL。例如：NULL<>NULL、NULL=NULL和NULL<>1返回结果都是NULL，而不是期望的布尔值。
+
+- 【关注】需要统计表中所有记录数时，不要使用count(col)来替代count(*)。count(*)会统计NULL值（真实行数），而count(col)不会统计。
+
+- 【关注】在执行count(col)时，将“值为NULL”的记录行计数为0。在执行sum(col)时，当所有记录都为NULL时，最终将返回NULL；当不全为NULL时，“值为NULL”的记录行将被计数为0。
+
+- 【关注】count(多个字段)时，多个字段名必须用圆括号括起来。例如，count( (col1,col2,col3) )。注意：通过多字段统计行数时，即使所选字段都为NULL，该行也被计数，效果与count(*)一致。
+
+- 【关注】count(distinct col)用来计算该列不重复的非NULL的数量，NULL将不被计数。
+
+- 【关注】count(distinct (col1,col2,…))用来统计多列的唯一值数量，当所有统计字段都为NULL时，也会被计数，同时这些记录被认为是相同的。
+
+- 【建议】使用连接操作符“||”替换concat函数进行字符串连接。因为concat函数生成的执行计划不能下推，导致查询性能严重劣化。
+
+- 【建议】使用下面时间相关的宏替换now函数来获取当前时间。因为now函数生成的执行计划无法下推，导致查询性能严重劣化。
+
+  **表 1** 时间相关的宏
+
+  | **宏名称**           | **描述**                                                     | **示例**                                                     |
+  | :------------------- | :----------------------------------------------------------- | :----------------------------------------------------------- |
+  | CURRENT_DATE         | 获取当前日期，不包含时分秒。                                 | `mogdb=# select CURRENT_DATE; date ----- 2018-02-02 (1 row)` |
+  | CURRENT_TIME         | 获取当前时间，不包含年月日。                                 | `mogdb=# select CURRENT_TIME; timetz -------- 00:39:34.633938+08 (1 row)` |
+  | CURRENT_TIMESTAMP(n) | 获取当前日期和时间，包含年月日时分秒。<br />说明：<br />n表示存储的毫秒位数。 | `mogdb=# select CURRENT_TIMESTAMP(6); timestamptz ----------- 2018-02-02 00:39:55.231689+08 (1 row)` |
+
+- 【建议】尽量避免标量子查询语句的出现。标量子查询是出现在select语句输出列表中的子查询，在下面例子中，下划线部分即为一个标量子查询语句：
+
+  ```sql
+  SELECT id, (SELECT COUNT(*) FROM films f WHERE f.did = s.id) FROM staffs_p1 s;
+  ```
+
+  标量子查询往往会导致查询性能急剧劣化，在应用开发过程中，应当根据业务逻辑，对标量子查询进行等价转换，将其写为表关联。
+
+- 【建议】在where子句中，应当对过滤条件进行排序，把选择读较小（筛选出的记录数较少）的条件排在前面。
+
+- 【建议】where子句中的过滤条件，尽量符合单边规则。即把字段名放在比较条件的一边，优化器在某些场景下会自动进行剪枝优化。形如col op expression，其中col为表的一个列，op为‘=’、‘>’的等比较操作符，expression为不含列名的表达式。例如，
+
+  ```sql
+  SELECT id, from_image_id, from_person_id, from_video_id FROM face_data WHERE current_timestamp(6) - time < '1 days'::interval;
+  ```
+
+  改写为：
+
+  ```sql
+  SELECT id, from_image_id, from_person_id, from_video_id FROM face_data where time >  current_timestamp(6) - '1 days'::interval;
+  ```
+
+- 【建议】尽量避免不必要的排序操作。排序需要耗费大量的内存及CPU，如果业务逻辑许可，可以组合使用order by和limit，减小资源开销。MogDB默认按照ASC & NULL LAST进行排序。
+
+- 【建议】使用ORDER BY子句进行排序时，显式指定排序方式（ASC/DESC），NULL的排序方式（NULL FIRST/NULL LAST）。
+
+- 【建议】不要单独依赖limit子句返回特定顺序的结果集。如果部分特定结果集，可以将ORDER BY子句与Limit子句组合使用，必要时也可以使用offset跳过特定结果。
+
+- 【建议】在保障业务逻辑准确的情况下，建议尽量使用UNION ALL来代替UNION。
+
+- 【建议】如果过滤条件只有OR表达式，可以将OR表达式转化为UNION ALL以提升性能。使用OR的SQL语句经常无法优化，导致执行速度慢。例如，将下面语句
+
+  ```sql
+  SELECT * FROM scdc.pub_menu
+  WHERE (cdp= 300 AND inline=301) OR (cdp= 301 AND inline=302) OR (cdp= 302 ANDinline=301);
+  ```
+
+  转换为：
+
+  ```sql
+  SELECT * FROM scdc.pub_menu
+  WHERE (cdp= 300 AND inline=301)
+  union all
+  SELECT * FROM scdc.pub_menu
+  WHERE (cdp= 301 AND inline=302)
+  union all
+  SELECT * FROM tablename
+  WHERE (cdp= 302 AND inline=301)
+  ```
+
+- 【建议】当in(val1, val2, val3…)表达式中字段较多时，建议使用in (values (va11), (val2),(val3)…)语句进行替换。优化器会自动把in约束转换为非关联子查询，从而提升查询性能。
+
+- 【建议】在关联字段不存在NULL值的情况下，使用(not) exist代替(not) in。例如，在下面查询语句中，当T1.C1列不存在NULL值时，可以先为T1.C1字段添加NOT NULL约束，再进行如下改写。
+
+  ```sql
+  SELECT * FROM T1 WHERE T1.C1 NOT IN (SELECT T2.C2 FROM T2);
+  ```
+
+  可以改写为：
+
+  ```sql
+  SELECT * FROM T1 WHERE NOT EXISTS (SELECT  * FROM T1,T2 WHERE T1.C1=T2.C2);
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  >
+  > - 如果不能保证T1.C1列的值为NOT NULL的情况下，就不能进行上述改写。
+  > - 如果T1.C1为子查询的输出，要根据业务逻辑确认其输出是否为NOT NULL。
+
+- 【建议】通过游标进行翻页查询，而不是使用LIMIT OFFSET语法，避免多次执行带来的资源开销。游标必须在事务中使用，执行完后务必关闭游标并提交事务。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/tool-interconnection/jdbc-configuration.md b/product/zh/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/tool-interconnection/jdbc-configuration.md
new file mode 100644
index 0000000000000000000000000000000000000000..7ef8ae23013dc880f50f3b89180de08d14a0509f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/development-and-design-proposal/tool-interconnection/jdbc-configuration.md
@@ -0,0 +1,63 @@
+---
+title: JDBC配置
+summary: JDBC配置
+author: Guo Huan
+date: 2021-10-14
+---
+
+# JDBC配置
+
+目前，MogDB相关的第三方工具都是通过JDBC进行连接的，此部分将介绍工具配置时的注意事项。
+
+## 连接参数
+
+- 【关注】第三方工具通过JDBC连接MogDB时，JDBC向MogDB发起连接请求，会默认添加以下配置参数，详见JDBC代码ConnectionFactoryImpl类的实现。
+
+  ```
+  params = {
+  { "user", user },
+  { "database", database },
+  { "client_encoding", "UTF8" },
+  { "DateStyle", "ISO" },
+  { "extra_float_digits", "2" },
+  { "TimeZone",  createPostgresTimeZone() },
+  };
+  ```
+
+  这些参数可能会导致JDBC客户端的行为与gsql客户端的行为不一致，例如，Date数据显示方式、浮点数精度表示、timezone显示。
+
+  如果实际期望和这些配置不符，建议在java连接设置代码中显式设定这些参数。
+
+- 【建议】通过JDBC连接数据库时，应该保证下面三个时区设置一致：
+
+  - JDBC客户端所在主机的时区。
+
+  - MogDB数据库实例所在主机的时区。
+
+  - MogDB数据库实例配置过程中时区。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+    > 时区设置相关的操作，请参考《安装指南》中“[设置时区和时间](3-modifying-os-configuration#设置时区和时间)“部分内容。
+
+## fetchsize
+
+【关注】在应用程序中，如果需要使用fetchsize，必须关闭autocommit。开启autocommit，会令fetchsize配置失效。
+
+## autocommit
+
+【建议】在JDBC向MogDB申请连接的代码中，建议显式打开autocommit开关。如果基于性能或者其它方面考虑，需要关闭autocommit时，需要应用程序自己来保证事务的提交。例如，在指定的业务SQL执行完之后做显式提交，特别是客户端退出之前务必保证所有的事务已经提交。
+
+## 释放连接
+
+【建议】推荐使用连接池限制应用程序的连接数。每执行一条SQL就连接一次数据库，是一种不好SQL的编写习惯。
+
+【建议】在应用程序完成作业任务之后，应当及时断开和MogDB的连接，释放资源。建议在任务中设置session超时时间参数。
+
+【建议】使用JDBC连接池，在将连接释放给连接池前，需要执行以下操作，重置会话环境。否则，可能会因为历史会话信息导致的对象冲突。
+
+- 如果在连接中设置了GUC参数，那么在将连接归还连接池之前，必须使用“SET SESSION AUTHORIZATION DEFAULT;RESET ALL;”将连接的状态清空。
+- 如果使用了临时表，那么在将连接归还连接池之前，必须将临时表删除。
+
+## CopyManager
+
+【建议】在不使用ETL工具，数据入库实时性要求又比较高的情况下，建议在开发应用程序时，使用MogDB JDBC驱动的copyManger接口进行微批导入。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/1-oracle_fdw.md b/product/zh/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/1-oracle_fdw.md
new file mode 100644
index 0000000000000000000000000000000000000000..63a54e9f865db57c0ac761ccc875e22722f0bfc3
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/1-oracle_fdw.md
@@ -0,0 +1,49 @@
+---
+title: oracle_fdw
+summary: oracle_fdw
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# oracle_fdw
+
+oracle_fdw（foreign data wrapper for oracle）用于Oracle的外部数据包装器，是一款开源插件。MogDB基于开源的[oracle_fdw Release 2.2.0 版本](https://github.com/laurenz/oracle_fdw/archive/ORACLE_FDW_2_2_0.tar.gz)进行开发适配。
+
+编译和使用oracle_fdw需要环境上包含Oracle的开发包，所以MogDB默认不编译oracle_fdw，下面依次介绍如何编译和使用oracle_fdw。
+
+## 编译oracle_fdw
+
+编译oracle_fdw需要安装Oracle的开发库和头文件。
+
+选择合适的运行环境和版本，下载**Basic Package**和**SDK Package**并安装。另外**SQLPlus Package**是Oracle的客户端工具，也可以根据需要安装，用于连接Oracle Server进行测试。
+
+安装好开发包后，就可以开始编译oracle_fdw了。编译时需要在执行**configure**时，加入 **-enable-oracle-fdw** 选项。后续按照正常的MogDB编译方式编译即可。
+
+编译完成后，编译产物为 **oracle_fdw.so**，位于安装目录的 **lib/postgresql/**下。oracle_fdw相关的sql文件和control文件，位于安装目录的 **share/postgresql/extension/**下。
+
+如果编译安装时，没有加入 `-enable-oracle-fdw` 选项，可以在MogDB安装完成后，再次编译oracle_fdw，然后手动将编译产物 `oracle_fdw.so` 放到对应的安装目录 **lib/postgresql/** ，将 `oracle_fdw-1.0-1.1.sql`，`oracle_fdw-1.1.sql`，`oracle_fdw.control`放到对应的安装目录 **share/postgresql/extension/**即可。
+
+## 使用oracle_fdw
+
+- 使用oracle_fdw需要连接Oracle，Oracle server请自行安装。
+- 加载oracle_fdw扩展：**CREATE EXTENSION oracle_fdw;**
+- 创建服务器对象：**CREATE SERVER**
+- 创建用户映射：**CREATE USER MAPPING**
+- 创建外表：**CREATE FOREIGN TABLE** 外表的表结构需要与Oracle数据库中的表结构保持一致。注意Oracle server侧的表的第一个字段必须具有唯一性约束（如PRIMARY KEY、UNIQUE等）。
+- 对外表做正常的操作，如 **INSERT** 、 **UPDATE** 、 **DELETE** 、 **SELECT** 、 **EXPLAIN** 、 **ANALYZE** 、 **COPY** 等。
+- 删除外表：**DROP FOREIGN TABLE**
+- 删除用户映射：**DROP USER MAPPING**
+- 删除服务器对象：**DROP SERVER**
+- 删除扩展：**DROP EXTENSION oracle_fdw；**
+
+## 常见问题
+
+- 在MogDB上建立外表时，不会在Oracle数据库中同步建表，需要自行在Oracle数据库中建表。
+- 执行**CREATE USER MAPPING**时使用的Oracle用户需要有远程连接Oracle数据库及对表相关操作的权限。使用外表前，可以在MogDB server所在的机器上，使用Oracle的客户端，使用对应的用户名密码确认能否成功连接Oracle并进行操作。
+- 执行**CREATE EXTENSION oracle_fdw;**时，出现 **libclntsh.so: cannot open shared object file: No such file or directory**。原因是Oracle的开发库libclntsh.so不在系统的相关路径中，可以先找到libclntsh.so的具体路径，然后将该so文件所在的文件夹加到 **/etc/ld.so.conf** 中。比如libclntsh.so的路径为 **/usr/lib/oracle/11.2/client64/lib/libclntsh.so.11.1** ，那么就将该文件的路径 **/usr/lib/oracle/11.2/client64/lib/** 加到 **/etc/ld.so.conf** 文件末尾。然后执行 **ldconfig**使修改生效即可。注意此操作需要**root**权限。
+
+## 注意事项
+
+- 两个Oracle外表间的**SELECT JOIN**不支持下推到Oracle server执行，会被分成两条SQL语句传递到Oracle执行，然后在MogDB处汇总处理结果。
+- 不支持**IMPORT FOREIGN SCHEMA**语法。
+- 不支持对外表进行**CREATE TRIGGER**操作。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/2-mysql_fdw.md b/product/zh/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/2-mysql_fdw.md
new file mode 100644
index 0000000000000000000000000000000000000000..66d51c84df18c296aa1e0699be88a3ef398ab55b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/2-mysql_fdw.md
@@ -0,0 +1,49 @@
+---
+title: mysql_fdw
+summary: mysql_fdw
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# mysql_fdw
+
+mysql_fdw是一款开源插件。MogDB基于开源的[mysql_fdw Release 2.5.3 版本](https://github.com/EnterpriseDB/mysql_fdw/archive/REL-2_5_3.tar.gz)进行开发适配。
+
+编译和使用mysql_fdw需要环境上包含MariaDB的开发包，所以MogDB默认不编译mysql_fdw，下面依次介绍如何编译和使用mysql_fdw。
+
+## 编译mysql_fdw
+
+编译mysql_fdw需要安装MariaDB的开发库和头文件，推荐使用MariaDB的[官方源](http://downloads.mariadb.org/mariadb/repositories)进行安装。
+
+配置好源后，使用**yum install MariaDB-devel MariaDB-shared**安装相关开发库。另外**MariaDB-client**是MariaDB的客户端工具，也可以根据需要安装，用于连接MariaDB进行测试。
+
+安装好开发包后，就可以开始编译mysql_fdw了。编译时需要在执行**configure**时，加入`-enable-mysql-fdw`选项。后续按照正常的MogDB编译方式编译即可。
+
+编译完成后，编译产物为**mysql_fdw.so** ，位于安装目录的**lib/postgresql/** 下。mysql_fdw相关的sql文件和control文件，位于安装目录的 **share/postgresql/extension/**下。
+
+如果编译安装时，没有加入**-enable-mysql-fdw**选项，可以在MogDB安装完成后，再次编译mysql_fdw，然后手动将编译产物`mysql_fdw.so`放到对应的安装目录 **lib/postgresql/**，将 **mysql_fdw-1.0-1.1.sql，mysql_fdw-1.1.sql，mysql_fdw-1.0.sql，mysql_fdw.control** 放到对应的安装目录 **share/postgresql/extension/** 即可。
+
+## 使用mysql_fdw
+
+- 使用mysql_fdw需要连接MariaDB或者MySQL Server，MariaDB或MySQL Server请自行安装。
+- 加载mysql_fdw扩展：**CREATE EXTENSION mysql_fdw;**
+- 创建服务器对象：**CREATE SERVER**
+- 创建用户映射：**CREATE USER MAPPING**
+- 创建外表：**CREATE FOREIGN TABLE** 外表的表结构需要与MySQL/MariaDB侧的表结构保持一致。注意MySQL/MariaDB侧的表的第一个字段必须具有唯一性约束（如PRIMARY KEY、UNIQUE等）。
+- 对外表做正常的操作，如 **INSERT** 、 **UPDATE** 、 **DELETE** 、 **SELECT** 、 **EXPLAIN** 、 **ANALYZE** 、 **COPY** 等。
+- 删除外表：**DROP FOREIGN TABLE**
+- 删除用户映射：**DROP USER MAPPING**
+- 删除服务器对象：**DROP SERVER**
+- 删除扩展：**DROP EXTENSION mysql_fdw;**
+
+## 常见问题
+
+- 在MogDB上建立外表时，不会同步在MariaDB/MySQL Server上建表，需要自己利用MariaDB/MySQL Server的客户端连接MariaDB/MySQL Server建表。
+- 创建USER MAPPING时使用的MariaDB/MySQL Server用户需要有远程连接MariaDB/MySQL Server及对表相关操作的权限。使用外表前，可以在MogDB server所在的机器上，使用MariaDB/MySQL Server的客户端，使用对应的用户名密码确认能否成功连接MariaDB/MySQL Server并进行操作。
+- 对外表执行DML操作时，出现**Can't initialize character set SQL_ASCII (path: compiled_in)** 错误。由于MariaDB不支持**SQL_ASCII**编码格式，目前只能通过修改MogDB database的编码格式解决该问题。修改database编码格式的方式为**update pg_database set encoding = pg_char_to_encoding('UTF-8') where datname = 'postgres';** datname根据实际情况填写。注意修改完编码格式后，需要重新开启一个gsql会话，才能使mysql_fdw使用更新后的参数。也可以通过在执行 **gs\_initdb** 时，使用 **-locale=LOCALE** ，指定默认的编码格式为 **非SQL_ASCII** 编码。
+
+## 注意事项
+
+- 两个mysql外表间的**SELECT JOIN**不支持下推到MariaDB/MySQL Server执行，会被分成两条SQL语句传递到MariaDB/MySQL Server执行，然后在MogDB处汇总处理结果。
+- 不支持**IMPORT FOREIGN SCHEMA**语法。
+- 不支持对外表进行**CREATE TRIGGER**操作。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/3-postgres_fdw.md b/product/zh/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/3-postgres_fdw.md
new file mode 100644
index 0000000000000000000000000000000000000000..0283e578a09b615934d3d592e187634673367127
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/3-postgres_fdw.md
@@ -0,0 +1,37 @@
+---
+title: postgres_fdw
+summary: postgres_fdw
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# postgres_fdw
+
+postgres_fdw是一款开源插件，其代码随PostgreSQL源码一同发布。MogDB基于开源的 PostgreSQL 9.4.26 版本中的postgres_fdw源码<https://ftp.postgresql.org/pub/source/v9.4.26/postgresql-9.4.26.tar.gz>进行开发适配。
+
+postgres_fdw插件默认参与编译，使用安装包安装好MogDB后，可直接使用postgres_fdw，无须其他操作。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 当前postgres_fdw仅支持MogDB连接MogDB，不支持MogDB连接PostgreSQL。
+
+## 使用postgres_fdw
+
+- 加载postgres_fdw扩展：**CREATE EXTENSION postgres_fdw;**
+- 创建服务器对象：**CREATE SERVER**
+- 创建用户映射：**CREATE USER MAPPING**
+- 创建外表：**CREATE FOREIGN TABLE** 外表的表结构需要与远端MogDB侧的表结构保持一致。
+- 对外表做正常的操作，如 **INSERT** 、 **UPDATE** 、 **DELETE** 、 **SELECT** 、 **EXPLAIN** 、 **ANALYZE** 、 **COPY** 等。
+- 删除外表：**DROP FOREIGN TABLE**
+- 删除用户映射：**DROP USER MAPPING**
+- 删除服务器对象：**DROP SERVER**
+- 删除扩展：**DROP EXTENSION postgres_fdw;**
+
+## 常见问题
+
+- 在MogDB上建立外表时，不会同步在远端的MogDB上建表，需要自己利用客户端连接远端MogDB建表。
+- 执行**CREATE USER MAPPING**时使用的MogDB用户需要有远程连接MogDB及对表相关操作的权限。使用外表前，可以在本地机器上，使用gsql的客户端，使用对应的用户名密码确认能否成功连接远端MogDB并进行操作。
+
+## 注意事项
+
+- 两个postgres_fdw外表间的**SELECT JOIN**不支持下推到远端MogDB执行，会被分成两条SQL语句传递到远端MogDB执行，然后在本地汇总处理结果。
+- 不支持**IMPORT FOREIGN SCHEMA**语法。
+- 不支持对外表进行**CREATE TRIGGER**操作。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/dblink.md b/product/zh/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/dblink.md
new file mode 100644
index 0000000000000000000000000000000000000000..ea5da8e414ca8ed5acc12da493d1a4e1ec491ebe
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/dblink.md
@@ -0,0 +1,79 @@
+---
+title: dblink
+summary: dblink
+author: Guo Huan
+date: 2021-10-19
+---
+
+# dblink
+
+dblink是一个可以在一个MogDB数据库会话中连接到其它MogDB数据库的工具，同libpq支持的连接参数一致，可参考[链接字符](6-connection-characters)。MogDB默认不编译dblink，下面依次介绍如何编译和使用dblink。
+
+## 编译dblink
+
+当前dblink的源码放在[contrib/dblink](https://gitee.com/opengauss/openGauss-server/tree/master/contrib/dblink)目录中。在编译安装完MogDB数据库之后，如果用户需要使用dblink，只需要进入上述目录执行如下即可完成dblink的编译安装。
+
+```bash
+make
+make install
+```
+
+## 常用的dblink函数
+
+- 加载dblink扩展
+
+  ```sql
+  CREATE EXTENSION dblink;
+  ```
+
+- 打开一个到远程数据库的持久连接
+
+  ```sql
+  SELECT dblink_connect(text connstr);
+  ```
+
+- 关闭一个到远程数据库的持久连接
+
+  ```sql
+  SELECT dblink_disconnect();
+  ```
+
+- 在远程数据库执行查询
+
+  ```sql
+  SELECT * FROM dblink(text connstr, text sql);
+  ```
+
+- 在远程数据库执行命令
+
+  ```sql
+  SELECT dblink_exec(text connstr, text sql);
+  ```
+
+- 返回所有打开的命名dblink连接的名称
+
+  ```sql
+  SELECT dblink_get_connections();
+  ```
+
+- 发送一个异步查询到远程数据库
+
+  ```sql
+  SELECT dblink_send_query(text connname, text sql);
+  ```
+
+- 检查连接是否正在忙于一个异步查询
+
+  ```sql
+  SELECT dblink_is_busy(text connname);
+  ```
+
+- 删除扩展
+
+  ```sql
+  DROP EXTENSION dblink;
+  ```
+
+## 注意事项
+
+目前dblink仅支持MogDB数据库访问另一个MogDB数据库，不支持MogDB数据库访问PostgreSQL数据库。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/fdw-introduction.md b/product/zh/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/fdw-introduction.md
new file mode 100644
index 0000000000000000000000000000000000000000..4e8838c757968c55a75b17fcc76ba6929d2b6801
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/fdw-introduction.md
@@ -0,0 +1,10 @@
+---
+title: 介绍
+summary: 介绍
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 介绍
+
+MogDB的fdw实现的功能是各个MogDB数据库及远程数据库之间的跨库操作。目前支持的远程服务器类型包括Oracle、MySQL（MariaDB）、PostgreSQL/openGauss/MogDB（postgres_fdw）、file_fdw 、dblink。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/file_fdw.md b/product/zh/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/file_fdw.md
new file mode 100644
index 0000000000000000000000000000000000000000..b69bf0f26c9f74a52f4a02713f9b119996dcc377
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/foreign-data-wrapper/file_fdw.md
@@ -0,0 +1,77 @@
+---
+title: file_fdw
+summary: file_fdw
+author: Guo Huan
+date: 2021-10-19
+---
+
+# file_fdw
+
+file_fdw模块提供了外部数据封装器file_fdw，可以用来在服务器的文件系统中访问数据文件。数据文件必须是COPY FROM可读的格式；具体可参照[COPY](41-COPY)语句的介绍。 访问这样的数据文件当前只是可读的。当前不支持对该数据文件的写入操作。
+
+当前MogDB会默认编译file_fdw，在initdb的时候会在pg_catalog schema中创建该插件。
+
+使用file_fdw创建的外部表可以有下列选项：
+
+- **filename**
+
+  指定要读取的文件，必需的参数，且必须是一个绝对路径名。
+
+- **format**
+
+    远端server的文件格式，支持text/csv/binary三种格式，和COPY语句的FORMAT选项相同。
+
+- **header**
+
+    指定的文件是否有标题行，与COPY语句的HEADER选项相同。
+
+- **delimiter**
+
+    指定文件的分隔符，与COPY的DELIMITER选项相同。
+
+- **quote**
+
+    指定文件的引用字符，与COPY的QUOTE选项相同。
+
+- **escape**
+
+    指定文件的转义字符，与COPY的ESCAPE选项相同。
+
+- **null**
+
+    指定文件的null字符串，与COPY的NULL选项相同。
+
+- **encoding**
+
+    指定文件的编码，与COPY的ENCODING选项相同。
+
+- **force_not_null**
+
+    这是一个布尔选项。如果为真，则声明字段的值不应该匹配空字符串（也就是， 文件级别null选项）。与COPY的FORCE_NOT_NULL选项里的字段相同。
+
+<br/>
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif)**注意：**
+>
+> - file_fdw不支持COPY的OIDS和 FORCE_QUOTE选项。
+>
+> - 注意这些选项只能为外部表或它的字段声明，不是在file_fdw外部数据封装器的选项里，也不是在使用该封装器的服务器或用户映射的选项里。
+>
+> - 修改表级别的选项需要系统管理员权限，因为安全原因：只有系统管理员用户能够决定读哪个文件。
+>
+> - 对于一个使用file_fdw的外部表，EXPLAIN显示要读取的文件名。除非指定了COSTS OFF，否则也显示文件大小（字节计）。
+
+## 使用file_fdw
+
+- 使用file_fdw需要指定要读取的文件，请先准备好该文件，并让数据库有读取权限。
+- 创建服务器对象：**CREATE SERVER**
+- 创建用户映射：**CREATE USER MAPPING**
+- 创建外表：**CREATE FOREIGN TABLE** 外表的表结构需要与指定的文件的数据保持一致。
+- 对外表做查询操作，写操作不被允许。
+- 删除外表：**DROP FOREIGN TABLE**
+- 删除用户映射：**DROP USER MAPPING**
+- 删除服务器对象：**DROP SERVER**
+
+## 注意事项
+
+- 不支持**DROP EXTENSION file_fdw**操作。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/logical-replication/1-logical-decoding.md b/product/zh/docs-mogdb/v3.0/developer-guide/logical-replication/1-logical-decoding.md
new file mode 100644
index 0000000000000000000000000000000000000000..85e8a1c484308fd4301b84303503e4700d862a98
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/logical-replication/1-logical-decoding.md
@@ -0,0 +1,53 @@
+---
+title: 逻辑解码概述
+summary: 逻辑解码概述
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# 逻辑解码概述
+
+## 功能描述
+
+MogDB对数据复制能力的支持情况为：
+
+支持通过数据迁移工具定期向异构数据库（如Oracle等）进行数据同步，不具备实时数据复制能力。不足以支撑与异构数据库间并网运行实时数据同步的诉求。
+
+MogDB提供了逻辑解码功能，通过反解xlog的方式生成逻辑日志。目标数据库解析逻辑日志以实时进行数据复制。具体如图1所示。逻辑复制降低了对目标数据库的形态限制，支持异构数据库、同构异形数据库对数据的同步，支持目标库进行数据同步期间的数据可读写，数据同步时延低。
+
+**图1** 逻辑复制
+
+![image-20210512102853986](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/logical-decoding-1.png)
+
+逻辑复制由两部分组成：逻辑解码和数据复制。逻辑解码会输出以事务为单位组织的逻辑日志。业务或数据库中间件将会对逻辑日志进行解析并最终实现数据复制。MogDB当前只提供逻辑解码功能，因此本章节只涉及逻辑解码的说明。
+
+逻辑解码为逻辑复制提供事务解码的基础能力，MogDB使用SQL函数接口进行逻辑解码。此方法调用方便，不需使用工具，对接外部工具接口也比较清晰，不需要额外适配。
+
+由于逻辑日志是以事务为单位的，在事务提交后才能输出，且逻辑解码是由用户驱动的；因此为了防止事务开始时的xlog被系统回收，或所需的事务信息被VACUUM回收，MogDB新增了逻辑复制槽，用于阻塞xlog的回收。
+
+一个逻辑复制槽表示一个更改流，这些更改可以在其它数据库中以它们在原数据库上产生的顺序被重播。逻辑复制槽，由每个逻辑日志的获取者维护一个。
+
+## 注意事项
+
+- 不支持DDL语句解码，在执行特定的DDL语句（例如普通表truncate或分区表exchange）时，可能造成解码数据丢失。
+- 不支持列存、数据页复制的解码。
+- 不支持级联备机进行逻辑解码。
+- 当执行DDL语句（如alter table）后，该DDL语句前尚未解码的物理日志可能会丢失。
+- 单条元组大小不超过1GB，考虑解码结果可能大于插入数据，因此建议单条元组大小不超过500MB。
+- MogDB支持解码的数据类型为：INTEGER、BIGINT、SMALLINT、TINYINT、SERIAL、SMALLSERIAL、BIGSERIAL、FLOAT、DOUBLE PRECISION、DATE、TIME[WITHOUT TIME ZONE]、TIMESTAMP[WITHOUT TIME ZONE]、CHAR(n)、VARCHAR(n)、TEXT。
+- 目前默认不支持ssl连接，如果需要ssl连接需要设置guc参数ssl=on。
+- 逻辑复制槽名称必须小于64个字符，且只包含小写字母、数字或者下划线中的一种或几种。
+- 当前逻辑复制不支持MOT特性。
+- 当逻辑复制槽所在数据库被删除后，这些复制槽变为不可用状态，需要用户手动删除。
+- 仅支持utf-8字符集。
+- 对多库的解码需要分别在库内创建流复制槽并开始解码，每个库的解码都需要单独扫一遍日志。
+- 不支持强起，强起后需要重新全量导出数据。
+- 备机解码时，switchover和failover时可能出现解码数据变多，需用户手动过滤。Qurem协议下，switchover和failover选择升主的备机，需要与当前主机日志同步。
+- 不允许主备，多个备机同时使用同一个复制槽解码，否则会产生数据不一致。
+- 只支持主机创建删除复制槽。
+- 数据库故障重启或逻辑复制进程重启后，解码数据存在重复，用户需自己过滤。
+- 计算机内核故障后，解码存在乱码，需手动或自动过滤。
+- 当前备机逻辑解码，不支持开启极致RTO。
+- 请确保在创建逻辑复制槽过程中长事务未启动，启动长事务会阻塞逻辑复制槽的创建。
+- 不支持interval partition表复制。
+- 在事务中执行DDL语句后，该DDL语句与之后的语句不会被解码。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/logical-replication/2-logical-decoding-by-sql-function-interfaces.md b/product/zh/docs-mogdb/v3.0/developer-guide/logical-replication/2-logical-decoding-by-sql-function-interfaces.md
new file mode 100644
index 0000000000000000000000000000000000000000..fc7fac0c5daaa0ff154ede30beea260b03d2edd9
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/logical-replication/2-logical-decoding-by-sql-function-interfaces.md
@@ -0,0 +1,83 @@
+---
+title: 使用SQL函数接口进行逻辑解码
+summary: 使用SQL函数接口进行逻辑解码
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# 使用SQL函数接口进行逻辑解码
+
+MogDB可以通过调用SQL函数，进行创建、删除、推进逻辑复制槽，获取解码后的事务日志。
+
+## 前提条件
+
+- 逻辑日志目前从主机节点中抽取，默认关闭SSL连接，如果进行逻辑复制，需要先上配置GUC参数ssl=on。
+
+   > **说明：** 为避免安全风险，请保证启用SSL连接。
+
+- 设置GUC参数wal_level=logical。
+
+- 设置GUC参数max_replication_slots>每个节点所需的（物理流复制槽数+逻辑复制槽数）。
+
+  物理流复制槽提供了一种自动化的方法来确保主节点在所有备节点或从备节点收到xlog之前，xlog不会被移除。也就是说物理流复制槽用于支撑主备节点HA。数据库所需要的物理流复制槽数为：备节点加从备的和与主节点之间的比例。例如，假设数据库的高可用方案为1主、1备、1从备，则所需物理流复制槽数为2。
+
+  关于逻辑复制槽数，请按如下规则考虑。
+
+  - 一个逻辑复制槽只能解码一个Database的修改，如果需要解码多个Database，则需要创建多个逻辑复制槽。
+  - 如果需要多路逻辑复制同步给多个目标数据库，在源端数据库需要创建多个逻辑复制槽，每个逻辑复制槽对应一条逻辑复制链路。
+
+- 仅限数据库管理员和拥有REPLICATION权限的用户进行操作。
+
+## 操作步骤
+
+1. 以数据库安装用户登录MogDB数据库主节点。
+
+2. 使用如下命令通过连接默认数据库mogdb。
+
+   ```bash
+   gsql -d mogdb -p 16000 -r
+   ```
+
+   其中，16000为数据库端口号，用户可根据实际情况替换。
+
+3. 创建名称为slot1的逻辑复制槽。
+
+   ```sql
+   mogdb=# SELECT * FROM pg_create_logical_replication_slot('slot1', 'mppdb_decoding');
+   slotname | xlog_position
+   ----------+---------------
+   slot1    | 0/601C150
+   (1 row)
+   ```
+
+4. 在数据库中创建表t，并向表t中插入数据。
+
+   ```sql
+   mogdb=# CREATE TABLE t(a int PRIMARY KEY, b int);
+   mogdb=# INSERT INTO t VALUES(3,3);
+   ```
+
+5. 读取复制槽slot1解码结果，解码条数为4096。
+
+   ```sql
+   mogdb=# SELECT * FROM pg_logical_slot_peek_changes('slot1', NULL, 4096);
+   location  |  xid  | data
+   -----------+-------+-------------------------------------------------------------------------------------------------------------------------------------------------
+   -------------------------------------------
+    0/601C188 | 1010023 | BEGIN 1010023
+    0/601ED60 | 1010023 | COMMIT 1010023 CSN 1010022
+    0/601ED60 | 1010024 | BEGIN 1010024
+    0/601ED60 | 1010024 | {"table_name":"public.t","op_type":"INSERT","columns_name":["a","b"],"columns_type":["integer","integer"],"columns_val":["3","3"],"old_keys_name":[],"old_keys_type":[],"old_keys_val":[]}
+    0/601EED8 | 1010024 | COMMIT 1010024 CSN 1010023
+   (5 rows)
+   ```
+
+6. 删除逻辑复制槽slot1。
+
+   ```sql
+   mogdb=#  SELECT * FROM pg_drop_replication_slot('slot1');
+    pg_drop_replication_slot
+   --------------------------
+
+   (1 row)
+   ```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/materialized-view/1-materialized-view-overview.md b/product/zh/docs-mogdb/v3.0/developer-guide/materialized-view/1-materialized-view-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..6bfbaef7d7f2b747af7b3635187cda3279a20d73
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/materialized-view/1-materialized-view-overview.md
@@ -0,0 +1,10 @@
+---
+title: 物化视图概述
+summary: 物化视图概述
+author: Liuxu
+date: 2021-05-21
+---
+
+# 物化视图概述
+
+物化视图是一种特殊的物理表，物化视图是相对普通视图而言的。普通视图是虚拟表，应用的局限性较大，任何对视图的查询实际上都是转换为对SQL语句的查询，性能并没有实际上提高。物化视图实际上就是存储SQL执行语句的结果，起到缓存的效果。
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/materialized-view/2-full-materialized-view/1-full-materialized-view-overview.md b/product/zh/docs-mogdb/v3.0/developer-guide/materialized-view/2-full-materialized-view/1-full-materialized-view-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..7d2a959031483d0e7057425d8df86b8e6958fec8
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/materialized-view/2-full-materialized-view/1-full-materialized-view-overview.md
@@ -0,0 +1,10 @@
+---
+title: 概述
+summary: 概述
+author: Liuxu
+date: 2021-05-21
+---
+
+# 概述
+
+全量物化视图仅支持对已创建的物化视图进行全量更新，而不支持进行增量更新。创建全量物化视图语法和CREATE TABLE AS语法类似。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/materialized-view/2-full-materialized-view/2-full-materialized-view-usage.md b/product/zh/docs-mogdb/v3.0/developer-guide/materialized-view/2-full-materialized-view/2-full-materialized-view-usage.md
new file mode 100644
index 0000000000000000000000000000000000000000..65dd1a39d1b39e99d460c7bdfcaddde5064d90bf
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/materialized-view/2-full-materialized-view/2-full-materialized-view-usage.md
@@ -0,0 +1,69 @@
+---
+title: 使用
+summary: 使用
+author: Liuxu
+date: 2021-05-21
+---
+
+# 使用
+
+## 语法格式
+
+- 创建全量物化视图
+
+  ```sql
+  CREATE MATERIALIZED VIEW [ view_name ] AS { query_block }; 
+  ```
+
+- 全量刷新物化视图
+
+  ```sql
+  REFRESH MATERIALIZED VIEW [ view_name ];
+  ```
+
+- 删除物化视图
+
+  ```sql
+  DROP MATERIALIZED VIEW [ view_name ];
+  ```
+
+- 查询物化视图
+
+  ```sql
+  SELECT * FROM [ view_name ];
+  ```
+
+## 示例
+
+```sql
+--准备数据。
+mogdb=# CREATE TABLE t1(c1 int, c2 int);
+mogdb=# INSERT INTO t1 VALUES(1, 1);
+mogdb=# INSERT INTO t1 VALUES(2, 2);
+
+--创建全量物化视图。
+mogdb=# CREATE MATERIALIZED VIEW mv AS select count(*) from t1;
+
+--查询物化视图结果。
+mogdb=# SELECT * FROM mv;
+ count 
+-------
+     2
+(1 row)
+
+--向物化视图中基表插入数据。
+mogdb=# INSERT INTO t1 VALUES(3, 3);
+
+--对全量物化视图做全量刷新。
+mogdb=# REFRESH MATERIALIZED VIEW mv;
+
+--查询物化视图结果。
+mogdb=# SELECT * FROM mv;
+ count 
+-------
+     3
+(1 row)
+
+--删除物化视图。
+mogdb=# DROP MATERIALIZED VIEW mv;
+```
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/materialized-view/2-full-materialized-view/3-full-materialized-view-support-and-constraints.md b/product/zh/docs-mogdb/v3.0/developer-guide/materialized-view/2-full-materialized-view/3-full-materialized-view-support-and-constraints.md
new file mode 100644
index 0000000000000000000000000000000000000000..3b2431a20b39a91e81e74e5b2330040bd810706e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/materialized-view/2-full-materialized-view/3-full-materialized-view-support-and-constraints.md
@@ -0,0 +1,18 @@
+---
+title: 支持和约束
+summary: 支持和约束
+author: Liuxu
+date: 2021-05-21
+---
+
+# 支持和约束
+
+## 支持场景
+
+- 通常全量物化视图所支持的查询范围与CREATE TABLE AS语句一致。
+- 全量物化视图上支持创建索引。
+- 支持analyze、explain。
+
+## 不支持场景
+
+物化视图不支持增删改操作，只支持查询语句。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/materialized-view/3-incremental-materialized-view/1-incremental-materialized-view-overview.md b/product/zh/docs-mogdb/v3.0/developer-guide/materialized-view/3-incremental-materialized-view/1-incremental-materialized-view-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..aad0be145496f28bc5fddd982ad16bd82944ed74
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/materialized-view/3-incremental-materialized-view/1-incremental-materialized-view-overview.md
@@ -0,0 +1,10 @@
+---
+title: 概述
+summary: 概述
+author: Liuxu
+date: 2021-05-21
+---
+
+# 概述
+
+增量物化视图可以对物化视图增量刷新，需要用户手动执行语句完成对物化视图在一段时间内的增量数据刷新。与全量创建物化视图的不同在于目前增量物化视图所支持场景较小。目前物化视图创建语句仅支持基表扫描语句或者UNION ALL语句。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/materialized-view/3-incremental-materialized-view/2-incremental-materialized-view-usage.md b/product/zh/docs-mogdb/v3.0/developer-guide/materialized-view/3-incremental-materialized-view/2-incremental-materialized-view-usage.md
new file mode 100644
index 0000000000000000000000000000000000000000..f322b99c7033fd7e2a9c5f91eb024d7b3ab26bf7
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/materialized-view/3-incremental-materialized-view/2-incremental-materialized-view-usage.md
@@ -0,0 +1,92 @@
+---
+title: 使用
+summary: 使用
+author: Liuxu
+date: 2021-05-21
+---
+
+# 使用
+
+## 语法格式
+
+- 创建增量物化视图
+
+  ```sql
+  CREATE INCREMENTAL MATERIALIZED VIEW [ view_name ] AS { query_block }; 
+  ```
+
+- 全量刷新物化视图
+
+  ```sql
+  REFRESH MATERIALIZED VIEW [ view_name ];
+  ```
+
+- 增量刷新物化视图
+
+  ```sql
+  REFRESH INCREMENTAL MATERIALIZED VIEW [ view_name ];
+  ```
+
+- 删除物化视图
+
+  ```sql
+  DROP MATERIALIZED VIEW [ view_name ];
+  ```
+
+- 查询物化视图
+
+  ```sql
+  SELECT * FROM [ view_name ];
+  ```
+
+## 示例
+
+```sql
+--准备数据。
+CREATE TABLE t1(c1 int, c2 int);
+INSERT INTO t1 VALUES(1, 1);
+INSERT INTO t1 VALUES(2, 2);
+
+--创建增量物化视图。
+mogdb=# CREATE INCREMENTAL MATERIALIZED VIEW mv AS SELECT * FROM t1;
+CREATE MATERIALIZED VIEW
+
+--插入数据。
+mogdb=# INSERT INTO t1 VALUES(3, 3);
+INSERT 0 1
+
+--增量刷新物化视图。
+mogdb=# REFRESH INCREMENTAL MATERIALIZED VIEW mv;
+REFRESH MATERIALIZED VIEW
+
+--查询物化视图结果。
+mogdb=# SELECT * FROM mv;
+ c1 | c2 
+----+----
+  1 |  1
+  2 |  2
+  3 |  3
+(3 rows)
+
+--插入数据。
+mogdb=# INSERT INTO t1 VALUES(4, 4);
+INSERT 0 1
+
+--全量刷新物化视图。
+mogdb=# REFRESH MATERIALIZED VIEW mv;
+REFRESH MATERIALIZED VIEW
+
+--查询物化视图结果。
+mogdb=# select * from mv;
+ c1 | c2 
+----+----
+  1 |  1
+  2 |  2
+  3 |  3
+  4 |  4
+(4 rows)
+
+--删除物化视图。
+mogdb=# DROP MATERIALIZED VIEW mv;
+DROP MATERIALIZED VIEW
+```
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/materialized-view/3-incremental-materialized-view/3-incremental-materialized-view-support-and-constraints.md b/product/zh/docs-mogdb/v3.0/developer-guide/materialized-view/3-incremental-materialized-view/3-incremental-materialized-view-support-and-constraints.md
new file mode 100644
index 0000000000000000000000000000000000000000..61d94febf580969c37c244a68493a19d905dd747
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/materialized-view/3-incremental-materialized-view/3-incremental-materialized-view-support-and-constraints.md
@@ -0,0 +1,29 @@
+---
+title: 支持和约束
+summary: 支持和约束
+author: Liuxu
+date: 2021-05-21
+---
+
+# 支持和约束
+
+## 支持场景
+
+- 单表查询语句。
+- 多个单表查询的UNION ALL。
+- 物化视图上支持创建索引。
+- 物化视图支持Analyze操作。
+
+## 不支持场景
+
+- 物化视图中不支持多表Join连接计划以及subquery计划。
+- 除少部分ALTER操作外，不支持对物化视图中基表执行绝大多数DDL操作。
+- 物化视图不支持增删改操作，只支持查询语句。
+- 不支持用临时表/hashbucket/unlog/分区表创建物化视图。
+- 不支持物化视图嵌套创建（即物化视图上创建物化视图）。
+- 仅支持行存表，不支持列存表。
+- 不支持UNLOGGED类型的物化视图，不支持WITH语法。
+
+## 约束
+
+物化视图定义如果为UNION ALL，则其中每个子查询需使用不同的基表。
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-1-plpgsql-overview.md b/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-1-plpgsql-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..927544166bd5f8acecc7952ddb26f15f49c32929
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-1-plpgsql-overview.md
@@ -0,0 +1,24 @@
+---
+title: PL/pgSQL语言函数介绍
+summary: PL/pgSQL语言函数介绍
+author: Guo Huan
+date: 2021-11-10
+---
+
+# PL/pgSQL语言函数介绍
+
+PL/pgSQL是一种可载入的过程语言。
+
+用PL/pgSQL创建的函数可以被用在任何可以使用内建函数的地方。例如，可以创建复杂条件的计算函数并且后面用它们来定义操作符或把它们用于索引表达式。
+
+SQL被大多数数据库用作查询语言。它是可移植的并且容易学习。但是每一个SQL语句必须由数据库服务器单独执行。
+
+这意味着客户端应用必须发送每一个查询到数据库服务器、等待它被处理、接收并处理结果、做一些计算，然后发送更多查询给服务器。如果客户端和数据库服务器不在同一台机器上，则会引起进程间通信并且将带来网络负担。
+
+通过PL/pgSQL，可以将一整块计算和一系列查询分组在数据库服务器内部，这样就有了一种过程语言的能力并且使SQL更易用，同时能节省客户端/服务器通信开销。
+
+- 客户端和服务器之间的额外往返通信被消除。
+- 客户端不需要的中间结果不必被整理或者在服务器和客户端之间传送。
+- 多轮的查询解析可以被避免。
+
+PL/pgSQL可以使用SQL中所有的数据类型、操作符和函数。一些常见函数，例如gs_extend_library。
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-10-other-statements.md b/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-10-other-statements.md
new file mode 100644
index 0000000000000000000000000000000000000000..41134ca26c5649ec70197bab739ee302e6ef2d0d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-10-other-statements.md
@@ -0,0 +1,20 @@
+---
+title: 其他语句
+summary: 其他语句
+author: Guo Huan
+date: 2021-03-04
+---
+
+# 其他语句
+
+## 锁操作
+
+MogDB提供了多种锁模式用于控制对表中数据的并发访问。这些模式可以用在MVCC（多版本并发控制）无法给出期望行为的场合。同样，大多数MogDB命令自动施加恰当的锁，以保证被引用的表在命令的执行过程中不会以一种不兼容的方式被删除或者修改。比如，在存在其他并发操作的时候，ALTER TABLE是不能在同一个表上执行的。
+
+## 游标操作
+
+MogDB中游标（cursor）是系统为用户开设的一个数据缓冲区，存放着SQL语句的执行结果。每个游标区都有一个名称。用户可以用SQL语句逐一从游标中获取记录，并赋给主变量，交由主语言进一步处理。
+
+游标的操作主要有游标的定义、打开、获取和关闭。
+
+完整的游标操作示例可参考[显式游标](1-11-cursors#显式游标)。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-11-cursors.md b/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-11-cursors.md
new file mode 100644
index 0000000000000000000000000000000000000000..119557d560e71b2263b74fe5721206985d1fbb21
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-11-cursors.md
@@ -0,0 +1,179 @@
+---
+title: 游标
+summary: 游标
+author: Guo Huan
+date: 2021-03-04
+---
+
+# 游标
+
+## 游标概述
+
+为了处理SQL语句，存储过程进程分配一段内存区域来保存上下文联系。游标是指向上下文区域的句柄或指针。借助游标，存储过程可以控制上下文区域的变化。
+
+> **须知：**
+> 当游标作为存储过程的返回值时，如果使用JDBC调用该存储过程，返回的游标将不可用。
+
+游标的使用分为显式游标和隐式游标。对于不同的SQL语句，游标的使用情况不同，详细信息请参见[表1](#游标使用情况)。
+
+**表 1** 游标使用情况<a id="游标使用情况"> </a>
+
+| SQL语句              | 游标           |
+| :------------------- | :------------- |
+| 非查询语句           | 隐式的         |
+| 结果是单行的查询语句 | 隐式的或显式的 |
+| 结果是多行的查询语句 | 显式的         |
+
+## 显式游标
+
+显式游标主要用于对查询语句的处理，尤其是在查询结果为多条记录的情况下。
+
+**处理步骤**
+
+显式游标处理需六个PL/SQL步骤：
+
+1. **定义静态游标**：就是定义一个游标名，以及与其相对应的SELECT语句。
+
+    定义静态游标的语法图，请参见[图1](#static_cursor_define)。
+
+    **图 1** static_cursor_define::=<a id="static_cursor_define"> </a>
+
+    ![static_cursor_define](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/cursors-1.jpg)
+
+    参数说明：
+
+    - cursor_name：定义的游标名。
+
+    - parameter：游标参数，只能为输入参数，其格式为：
+
+        ```sql
+        parameter_name datatype
+        ```
+
+    - select_statement：查询语句。
+
+    >  **说明：**
+    > 根据执行计划的不同，系统会自动判断该游标是否可以用于以倒序的方式检索数据行。
+
+    **定义动态游标：**指ref游标，可以通过一组静态的SQL语句动态的打开游标。首先定义ref游标类型，然后定义该游标类型的游标变量，在打开游标时通过OPEN FOR动态绑定SELECT语句。
+
+    定义动态游标的语法图，请参见[图2](#cursor_typename)和[图3](#dynamic_cursor_define)。
+
+    **图 2** cursor_typename::=<a id="cursor_typename"> </a>
+
+    ![cursor_typename](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/cursors-2.png)
+
+    **图 3** dynamic_cursor_define::=<a id="dynamic_cursor_define"> </a>
+
+    ![dynamic_cursor_define](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/cursors-3.png)
+
+2. **打开静态游标：**就是执行游标所对应的SELECT语句，将其查询结果放入工作区，并且指针指向工作区的首部，标识游标结果集合。如果游标查询语句中带有FOR UPDATE选项，OPEN语句还将锁定数据库表中游标结果集合对应的数据行。
+
+    打开静态游标的语法图，请参见[图4](#open_static_cursor)。
+
+    **图 4** open_static_cursor::=<a id="open_static_cursor"> </a>
+
+    ![open_static_cursor](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/cursors-4.png)
+
+    **打开动态游标：**可以通过OPEN FOR语句打开动态游标，动态绑定SQL语句。
+
+    打开动态游标的语法图，请参见[图5](#open_dynamic_cursor)。
+
+    **图 5** open_dynamic_cursor::=<a id="open_dynamic_cursor"> </a>
+
+    ![open_dynamic_cursor](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/cursors-5.png)
+
+    PL/SQL程序不能用OPEN语句重复打开一个游标。
+
+3. 提取游标数据：检索结果集合中的数据行，放入指定的输出变量中。
+
+    提取游标数据的语法图，请参见[图6](#fetch_cursor)。
+
+    **图 6** fetch_cursor::=<a id="fetch_cursor"> </a>
+
+    ![fetch_cursor](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/cursors-6.png)
+
+4. 对该记录进行处理。
+
+5. 继续处理，直到活动集合中没有记录。
+
+6. 关闭游标：当提取和处理完游标结果集合数据后，应及时关闭游标，以释放该游标所占用的系统资源，并使该游标的工作区变成无效，不能再使用FETCH语句获取其中数据。关闭后的游标可以使用OPEN语句重新打开。
+
+    关闭游标的语法图，请参见[图7](#close_cursor)。
+
+    **图 7** close_cursor::=<a id="close_cursor"> </a>
+
+    ![close_cursor](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/cursors-7.jpg)
+
+**属性**
+
+游标的属性用于控制程序流程或者了解程序的状态。当运行DML语句时，PL/SQL打开一个内建游标并处理结果，游标是维护查询结果的内存中的一个区域，游标在运行DML语句时打开，完成后关闭。显式游标的属性为：
+
+- %FOUND布尔型属性：当最近一次读记录时成功返回，则值为TRUE。
+- %NOTFOUND布尔型属性：与%FOUND相反。
+- %ISOPEN布尔型属性：当游标已打开时返回TRUE。
+- %ROWCOUNT数值型属性：返回已从游标中读取的记录数。
+
+## 隐式游标
+
+对于非查询语句，如修改、删除操作，则由系统自动地为这些操作设置游标并创建其工作区，这些由系统隐含创建的游标称为隐式游标，隐式游标的名称为SQL，这是由系统定义的。
+
+**简介**
+
+对于隐式游标的操作，如定义、打开、取值及关闭操作，都由系统自动地完成，无需用户进行处理。用户只能通过隐式游标的相关属性，来完成相应的操作。在隐式游标的工作区中，所存放的数据是最新处理的一条SQL语句所包含的数据，与用户自定义的显式游标无关。
+
+**格式调用为**： SQL%
+
+> **说明：**
+> INSERT、UPDATE、DELETE、SELECT语句中不必明确定义游标。
+
+**属性**
+
+隐式游标属性为：
+
+- SQL%FOUND布尔型属性：当最近一次读记录时成功返回，则值为TRUE。
+- SQL%NOTFOUND布尔型属性：与%FOUND相反。
+- SQL%ROWCOUNT数值型属性：返回已从游标中读取得记录数。
+- SQL%ISOPEN布尔型属性：取值总是FALSE。SQL语句执行完毕立即关闭隐式游标。
+
+**示例**
+
+```sql
+--删除员工表hr.staffs表中某部门的所有员工，如果该部门中已没有员工，则在部门表hr.sections中删除该部门。
+
+CREATE OR REPLACE PROCEDURE proc_cursor3()
+AS
+    DECLARE
+    V_DEPTNO NUMBER(4) := 100;
+    BEGIN
+        DELETE FROM hr.staffs WHERE section_ID = V_DEPTNO;
+        --根据游标状态做进一步处理
+        IF SQL%NOTFOUND THEN
+        DELETE FROM hr.sections WHERE section_ID = V_DEPTNO;
+        END IF;
+    END;
+/
+
+CALL proc_cursor3();
+
+--删除存储过程和临时表
+DROP PROCEDURE proc_cursor3;
+```
+
+## 游标循环
+
+游标在WHILE语句、LOOP语句中的使用称为游标循环，一般这种循环都需要使用OPEN、FETCH和CLOSE语句。下面要介绍的一种循环不需要这些操作，可以简化游标循环的操作，这种循环方式适用于静态游标的循环，不用执行静态游标的四个步骤。
+
+**语法**
+
+FOR AS循环的语法请参见[图8](#FOR_AS_loop)。
+
+**图 8** FOR_AS_loop::=<a id="FOR_AS_loop"> </a>
+
+![FOR_AS_loop](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/cursors-8.png)
+
+**注意事项**
+
+- 不能在该循环语句中对查询的表进行更新操作。
+- 变量loop_name会自动定义且只在此循环中有效，类型和select_statement的查询结果类型一致。loop_name的取值就是select_statement的查询结果。
+- 游标的属性中%FOUND、%NOTFOUND、%ROWCOUNT在MogDB数据库中都是访问同一个内部变量，事务和匿名块不支持多个游标同时访问。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-12-retry-management.md b/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-12-retry-management.md
new file mode 100644
index 0000000000000000000000000000000000000000..af65631fc3979aab0e35f7863f255143a25dc39b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-12-retry-management.md
@@ -0,0 +1,28 @@
+---
+title: Retry管理
+summary: Retry管理
+author: Guo Huan
+date: 2021-03-04
+---
+
+# Retry管理
+
+Retry是数据库在SQL或存储过程（包含匿名块）执行失败时，在数据库内部进行重新执行的过程，以提高执行成功率和用户体验。数据库内部通过检查
+
+发生错误时的错误码及Retry相关配置，决定是否进行重试。
+
+- 失败时回滚之前执行的语句，并重新执行存储过程进行Retry。
+
+    示例：
+
+    ```sql
+    mogdb=# CREATE OR REPLACE PROCEDURE retry_basic ( IN  x INT)
+    AS
+    BEGIN
+          INSERT INTO t1 (a) VALUES (x);
+          INSERT INTO t1 (a) VALUES (x+1);
+    END;
+    /
+
+    mogdb=# CALL retry_basic(1);
+    ```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-13-debugging.md b/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-13-debugging.md
new file mode 100644
index 0000000000000000000000000000000000000000..8fe9e9f35ef4e83139c806c7d7fa18192d0d925d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-13-debugging.md
@@ -0,0 +1,136 @@
+---
+title: 调试
+summary: 调试
+author: Guo Huan
+date: 2021-03-04
+---
+
+# 调试
+
+## **语法**
+
+RAISE有以下五种语法格式：
+
+**图 1** raise_format::=
+
+![raise_format](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/debugging-1.png)
+
+**图 2** raise_condition::=
+
+![raise_condition](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/debugging-2.png)
+
+**图 3** raise_sqlstate::=
+
+![raise_sqlstate](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/debugging-3.png)
+
+**图 4** raise_option::=
+
+![raise_option](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/debugging-4.png)
+
+**图 5** raise::=<a id="raise::="> </a>
+
+![raise](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/debugging-5.png)
+
+**参数说明：**
+
+- level选项用于指定错误级别，有DEBUG，LOG，INFO，NOTICE，WARNING以及EXCEPTION（默认值）。EXCEPTION抛出一个正常终止当前事务的异常，其他的仅产生不同异常级别的信息。特殊级别的错误信息是否报告到客户端、写到服务器日志由log_min_messages和client_min_messages这两个配置参数控制。
+
+- format：格式字符串，指定要报告的错误消息文本。格式字符串后可跟表达式，用于向消息文本中插入。在格式字符串中，%由format后面跟着的参数的值替换，%%用于打印出%。例如：
+
+    ```
+    --v_job_id 将替换字符串中的 %:
+    RAISE NOTICE 'Calling cs_create_job(%)',v_job_id;
+    ```
+
+- option = expression：向错误报告中添加另外的信息。关键字option可以是MESSAGE、DETAIL、HINT以及ERRCODE，并且每一个expression可以是任意的字符串。
+
+  - MESSAGE，指定错误消息文本，这个选项不能用于在USING前包含一个格式字符串的RAISE语句中。
+  - DETAIL，说明错误的详细信息。
+  - HINT，用于打印出提示信息。
+  - ERRCODE，向报告中指定错误码（SQLSTATE）。可以使用条件名称或者直接用五位字符的SQLSTATE错误码。
+
+- condition_name：错误码对应的条件名。
+
+- sqlstate：错误码。
+
+如果在RAISE EXCEPTION命令中既没有指定条件名也没有指定SQLSTATE，默认用RAISE EXCEPTION (P0001)。如果没有指定消息文本，默认用条件名或者SQLSTATE作为消息文本。
+
+> **须知：**
+> 当由SQLSTATE指定了错误码，则不局限于已定义的错误码，可以选择任意包含五个数字或者大写的ASCII字母的错误码，而不是00000。建议避免使用以三个0结尾的错误码，因为这种错误码是类别码，会被整个种类捕获。
+>
+> **说明：**
+> [图5](#raise::=)所示的语法不接任何参数。这种形式仅用于一个BEGIN块中的EXCEPTION语句，它使得错误重新被处理。
+
+## **示例**
+
+终止事务时，给出错误和提示信息：
+
+```sql
+CREATE OR REPLACE PROCEDURE proc_raise1(user_id in integer)
+AS
+BEGIN
+RAISE EXCEPTION 'Noexistence ID --> %',user_id USING HINT = 'Please check your user ID';
+END;
+/
+
+call proc_raise1(300011);
+
+--执行结果
+ERROR:  Noexistence ID --> 300011
+HINT:  Please check your user ID
+```
+
+两种设置SQLSTATE的方式：
+
+```sql
+CREATE OR REPLACE PROCEDURE proc_raise2(user_id in integer)
+AS
+BEGIN
+RAISE 'Duplicate user ID: %',user_id USING ERRCODE = 'unique_violation';
+END;
+/
+
+\set VERBOSITY verbose
+call proc_raise2(300011);
+
+--执行结果
+ERROR:  Duplicate user ID: 300011
+SQLSTATE: 23505
+LOCATION:  exec_stmt_raise, pl_exec.cpp:3482
+```
+
+如果主要的参数是条件名或者是SQLSTATE，可以使用：
+
+RAISE division_by_zero;
+
+RAISE SQLSTATE '22012';
+
+例如：
+
+```sql
+CREATE OR REPLACE PROCEDURE division(div in integer, dividend in integer)
+AS
+DECLARE
+res int;
+    BEGIN
+    IF dividend=0 THEN
+        RAISE division_by_zero;
+        RETURN;
+    ELSE
+        res := div/dividend;
+        RAISE INFO 'division result: %', res;
+        RETURN;
+    END IF;
+    END;
+/
+call division(3,0);
+
+--执行结果
+ERROR:  division_by_zero
+```
+
+或者另一种方式：
+
+```sql
+RAISE unique_violation USING MESSAGE = 'Duplicate user ID: ' || user_id;
+```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-2-data-types.md b/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-2-data-types.md
new file mode 100644
index 0000000000000000000000000000000000000000..37ba28099f66b15a1ac3fbcdaf05bf2e12409586
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-2-data-types.md
@@ -0,0 +1,10 @@
+---
+title: 数据类型
+summary: 数据类型
+author: Guo Huan
+date: 2021-03-04
+---
+
+# 数据类型
+
+数据类型是一组值的集合以及定义在这个值集上的一组操作。MogDB数据库是由表的集合组成的，而各表中的列定义了该表，每一列都属于一种数据类型，MogDB根据数据类型有相应函数对其内容进行操作，例如MogDB可对数值型数据进行加、减、乘、除操作。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-3-data-type-conversion.md b/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-3-data-type-conversion.md
new file mode 100644
index 0000000000000000000000000000000000000000..9d5e85bdd2ce07871a12bc1fd8c8dd10e87e934a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-3-data-type-conversion.md
@@ -0,0 +1,42 @@
+---
+title: 数据类型转换
+summary: 数据类型转换
+author: Guo Huan
+date: 2021-03-04
+---
+
+# 数据类型转换
+
+数据库中允许有些数据类型进行隐式类型转换（赋值、函数调用的参数等），有些数据类型间不允许进行隐式数据类型转换，可尝试使用MogDB提供的类型转换函数，例如CAST进行数据类型强转。
+
+MogDB数据库常见的隐式类型转换，请参见[表1](#隐式类型转换表)。
+
+> **须知:**
+> MogDB支持的DATE的效限范围是: 公元前4713年到公元294276年。
+
+**表 1** 隐式类型转换表<a id="隐式类型转换表"> </a>
+
+| 原始数据类型 | 目标数据类型 | 备注                         |
+| :----------- | :----------- | :--------------------------- |
+| CHAR         | VARCHAR2     | -                            |
+| CHAR         | NUMBER       | 原数据必须由数字组成。       |
+| CHAR         | DATE         | 原数据不能超出合法日期范围。 |
+| CHAR         | RAW          | -                            |
+| CHAR         | CLOB         | -                            |
+| VARCHAR2     | CHAR         | -                            |
+| VARCHAR2     | NUMBER       | 原数据必须由数字组成。       |
+| VARCHAR2     | DATE         | 原数据不能超出合法日期范围。 |
+| VARCHAR2     | CLOB         | -                            |
+| NUMBER       | CHAR         | -                            |
+| NUMBER       | VARCHAR2     | -                            |
+| DATE         | CHAR         | -                            |
+| DATE         | VARCHAR2     | -                            |
+| RAW          | CHAR         | -                            |
+| RAW          | VARCHAR2     | -                            |
+| CLOB         | CHAR         | -                            |
+| CLOB         | VARCHAR2     | -                            |
+| CLOB         | NUMBER       | 原数据必须由数字组成。       |
+| INT4         | CHAR         | -                            |
+| INT4         | BOOLEAN      | -                            |
+| INT4         | CHAR         | -                            |
+| BOOLEAN      | INT4         | -                            |
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-4-arrays-and-records.md b/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-4-arrays-and-records.md
new file mode 100644
index 0000000000000000000000000000000000000000..7e7508461855f70c234511fd7b27d9467e28e2d1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-4-arrays-and-records.md
@@ -0,0 +1,157 @@
+---
+title: 数组和record
+summary: 数组和record
+author: Guo Huan
+date: 2021-03-04
+---
+
+# 数组和record
+
+## 数组
+
+**数组类型的使用**
+
+在使用数组之前，需要自定义一个数组类型。
+
+在存储过程中紧跟AS关键字后面定义数组类型。定义方法如下。
+
+```
+TYPE array_type IS VARRAY(size) OF data_type;
+```
+
+其中:
+
+- array_type: 要定义的数组类型名。
+- VARRAY: 表示要定义的数组类型。
+- size: 取值为正整数，表示可以容纳的成员的最大数量。
+- data_type: 要创建的数组中成员的类型。
+
+> **说明:**
+>
+> - 在MogDB中，数组会自动增长，访问越界会返回一个NULL，不会报错。
+> - 在存储过程中定义的数组类型，其作用域仅在该存储过程中。
+> - 建议选择上述定义方法的一种来自定义数组类型，当同时使用两种方法定义同名的数组类型时，MogDB会优先选择存储过程中定义的数组类型来声明数组变量。
+> - data_type也可以为存储过程中定义的record类型（匿名块不支持），但不可以为存储过程中定义的数组或集合类型。
+
+MogDB支持使用圆括号来访问数组元素，且还支持一些特有的函数，如extend、count、first、last来访问数组的内容。
+
+> **说明:**
+> 存储过程中如果有DML语句（SELECT、UPDATE、INSERT、DELETE），DML语句推荐使用中括号来访问数组元素，使用小括号默认识别为数组访问，若数组不存在，则识别为函数表达式。
+
+## record
+
+**record**类型的变量
+
+创建一个record变量的方式:
+
+定义一个record类型 ，然后使用该类型来声明一个变量。
+
+**语法**
+
+record类型的语法参见[图1](#record类型的语法)。
+
+**图 1** record类型的语法<a id="record类型的语法"> </a>
+
+![record类型的语法](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/arrays-and-records-1.png)
+
+对以上语法格式的解释如下:
+
+- record_type: 声明的类型名称。
+- field: record类型中的成员名称。
+- datatype: record类型中成员的类型。
+- expression: 设置默认值的表达式。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+>
+> 在MogDB中:
+>
+> - record类型变量的赋值支持：
+>   - 在函数或存储过程的声明阶段，声明一个record类型，并且可以在该类型中定义成员变量。
+>   - 一个record变量到另一个record变量的赋值。
+>   - SELECT INTO和FETCH向一个record类型的变量中赋值。
+>   - 将一个NULL值赋值给一个record变量。
+> - 不支持INSERT和UPDATE语句使用record变量进行插入数据和更新数据。
+> - 如果成员有复合类型，在声明阶段不支持指定默认值，该行为同声明阶段的变量一样。
+> - date_type也可以为存储过程中定义的record类型、数组类型和集合类型（匿名块不支持）。
+
+**示例**
+
+```sql
+下面示例中用到的表定义如下:
+mogdb=# \d emp_rec
+                Table "public.emp_rec"
+  Column  |              Type              | Modifiers
+----------+--------------------------------+-----------
+ empno    | numeric(4,0)                   | not null
+ ename    | character varying(10)          |
+ job      | character varying(9)           |
+ mgr      | numeric(4,0)                   |
+ hiredate | timestamp(0) without time zone |
+ sal      | numeric(7,2)                   |
+ comm     | numeric(7,2)                   |
+ deptno   | numeric(2,0)                   |
+
+--演示在函数中对数组进行操作。
+mogdb=# CREATE OR REPLACE FUNCTION regress_record(p_w VARCHAR2)
+RETURNS
+VARCHAR2  AS $$
+DECLARE
+
+   --声明一个record类型.
+   type rec_type is record (name  varchar2(100), epno int);
+   employer rec_type;
+
+   --使用%type声明record类型
+   type rec_type1 is record (name  emp_rec.ename%type, epno int not null :=10);
+   employer1 rec_type1;
+
+   --声明带有默认值的record类型
+   type rec_type2 is record (
+         name varchar2 not null := 'SCOTT',
+         epno int not null :=10);
+    employer2 rec_type2;
+    CURSOR C1 IS  select ename,empno from emp_rec order by 1 limit 1;
+
+BEGIN
+      --对一个record类型的变量的成员赋值。
+     employer.name := 'WARD';
+     employer.epno = 18;
+     raise info 'employer name: % , epno:%', employer.name, employer.epno;
+
+     --将一个record类型的变量赋值给另一个变量。
+     employer1 := employer;
+     raise info 'employer1 name: % , epno: %',employer1.name, employer1.epno;
+
+      --将一个record类型变量赋值为NULL。
+     employer1 := NULL;
+     raise info 'employer1 name: % , epno: %',employer1.name, employer1.epno;
+
+      --获取record变量的默认值。
+     raise info 'employer2 name: % ,epno: %', employer2.name, employer2.epno;
+
+      --在for循环中使用record变量
+      for employer in select ename,empno from emp_rec order by 1  limit 1
+          loop
+               raise info 'employer name: % , epno: %', employer.name, employer.epno;
+          end loop;
+
+      --在select into 中使用record变量。
+      select ename,empno  into employer2 from emp_rec order by 1 limit 1;
+      raise info 'employer name: % , epno: %', employer2.name, employer2.epno;
+
+      --在cursor中使用record变量。
+      OPEN C1;
+      FETCH C1 INTO employer2;
+      raise info 'employer name: % , epno: %', employer2.name, employer2.epno;
+      CLOSE C1;
+      RETURN employer.name;
+END;
+$$
+LANGUAGE plpgsql;
+
+--调用该函数。
+mogdb=# CALL regress_record('abc');
+
+--删除函数。
+mogdb=# DROP FUNCTION regress_record;
+```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-5-declare-syntax.md b/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-5-declare-syntax.md
new file mode 100644
index 0000000000000000000000000000000000000000..77a4bfcea2d3801c86976521d17191913983991a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-5-declare-syntax.md
@@ -0,0 +1,82 @@
+---
+title: 声明语法
+summary: 声明语法
+author: Guo Huan
+date: 2021-03-04
+---
+
+# 声明语法
+
+## 基本结构
+
+**结构**
+
+PL/SQL块中可以包含子块，子块可以位于PL/SQL中任何部分。PL/SQL块的结构如下:
+
+- 声明部分：声明PL/SQL用到的变量、类型、游标、局部的存储过程和函数。
+
+  ```sql
+  DECLARE
+  ```
+
+  >  **说明:**
+  > 不涉及变量声明时声明部分可以没有。
+  >
+  > - 对匿名块来说，没有变量声明部分时，可以省去DECLARE关键字。
+  > - 对存储过程来说，没有DECLARE， AS相当于DECLARE。即便没有变量声明的部分，关键字AS也必须保留。
+
+- 执行部分：过程及SQL语句，程序的主要部分。必选。
+
+  ```sql
+  BEGIN
+  ```
+
+- 执行异常部分：错误处理。可选。
+
+  ```sql
+  EXCEPTION
+  ```
+
+- 结束
+
+  ```sql
+  END;
+  /
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+  > 禁止在PL/SQL块中使用连续的Tab，连续的Tab可能会造成在使用gsql工具带“-r”参数执行PL/SQL块时出现异常。
+
+**分类**
+
+PL/SQL块可以分为以下几类：
+
+- 匿名块：动态构造，只能执行一次。语法请参考[图1](#anonymous_block::=)。
+- 子程序：存储在数据库中的存储过程、函数、操作符和高级包等。当在数据库上建立好后，可以在其他程序中调用它们。
+
+## 匿名块
+
+匿名块（Anonymous Block）一般用于不频繁执行的脚本或不重复进行的活动。它们在一个会话中执行，并不被存储。
+
+**语法**
+
+匿名块的语法参见[图1](#anonymous_block::=)。
+
+**图 1** anonymous_block::=<a id="anonymous_block::="> </a>
+
+![anonymous_block](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/declare-syntax-1.png)
+
+对以上语法图的解释如下：
+
+- 匿名块程序实施部分，以BEGIN语句开始，以END语句停顿，以一个分号结束。输入“/”按回车执行它。
+
+  >  **须知：**
+  > 最后的结束符”/“必须独占一行，不能直接跟在END后面。
+
+- 声明部分包括变量定义、类型、游标定义等。
+
+- 最简单的匿名块不执行任何命令。但一定要在任意实施块里至少有一个语句，甚至是一个NULL语句。
+
+## 子程序
+
+存储在数据库中的存储过程、函数、操作符和高级包等。当在数据库上建立好后，可以在其他程序中调用它们。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-6-basic-statements.md b/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-6-basic-statements.md
new file mode 100644
index 0000000000000000000000000000000000000000..abf3c088d3c13542f92daa2edeab70d8dd6c9d8c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-6-basic-statements.md
@@ -0,0 +1,189 @@
+---
+title: 基本语句
+summary: 基本语句
+author: Guo Huan
+date: 2021-03-04
+---
+
+# 基本语句
+
+在编写PL/SQL过程中，会定义一些变量，给变量赋值，调用其他存储过程等。介绍PL/SQL中的基本语句，包括定义变量、赋值语句、调用语句以及返回语句。
+
+> **说明：**
+> 尽量不要在存储过程中调用包含密码的SQL语句，因为存储在数据库中的存储过程文本可能被其他有权限的用户看到导致密码信息被泄漏。如果存储过程中包含其他敏感信息也需要配置存储过程的访问权限，保证敏感信息不会泄漏。
+
+## 定义变量
+
+介绍PL/SQL中变量的声明，以及该变量在代码中的作用域。
+
+**变量声明**
+
+变量声明语法请参见[图1](#declare_variable::=)。
+
+**图 1** declare_variable::=<a id="declare_variable::="> </a>
+
+![declare_variable](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/basic-statements-1.png)
+
+对以上语法格式的解释如下：
+
+- variable_name：变量名。
+- type：变量类型。
+- value：该变量的初始值（如果不给定初始值，则初始为NULL）。value也可以是表达式。
+
+**示例**
+
+```sql
+mogdb=# DECLARE
+    emp_id  INTEGER := 7788;  --定义变量并赋值
+BEGIN
+    emp_id := 5*7784;  --变量赋值
+END;
+/
+```
+
+变量类型除了支持基本类型，还可以是使用%TYPE和%ROWTYPE去声明一些与其他表字段或表结构本身相关的变量。
+
+**%TYPE属性**
+
+%TYPE主要用于声明某个与其他变量类型（例如，表中某列的类型）相同的变量。假如我们想定义一个my_name变量，它的变量类型与employee的firstname类型相同，我们可以通过如下定义：
+
+```
+my_name employee.firstname%TYPE
+```
+
+这样定义可以带来两个好处，首先，我们不用预先知道employee表的firstname类型具体是什么。其次，即使之后firstname类型有了变化，我们也不需要再次修改my_name的类型。
+
+```
+TYPE employee_record is record (id INTEGER, firstname VARCHAR2(20));
+my_employee employee_record;
+my_id my_employee.id%TYPE;
+my_id_copy my_id%TYPE;
+```
+
+**%ROWTYPE属性**
+
+%ROWTYPE属性主要用于对一组数据的类型声明，用于存储表中的一行数据或从游标匹配的结果。假如，我们需要一组数据，该组数据的字段名称与字段类型都与employee表相同。我们可以通过如下定义：
+
+```
+my_employee employee%ROWTYPE
+```
+
+同样可以使用在cursor上面，该组数据的字段名称与字段类型都与employee表相同。%TYPE也可以引用cursor中某一列的类型，我们可以通过如下定义：
+
+```
+cursor cur is select * from employee;
+my_employee cur%ROWTYPE
+my_name cur.firstname%TYPE
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+>
+> - %TYPE不支持引用复合类型或RECORD类型变量的类型、RECORD类型的某列类型。
+> - %ROWTYPE不支持引用复合类型或RECORD类型变量的类型。
+
+**变量作用域**
+
+变量的作用域表示变量在代码块中的可访问性和可用性。只有在它的作用域内，变量才有效。
+
+- 变量必须在declare部分声明，即必须建立BEGIN-END块。块结构也强制变量必须先声明后使用，即变量在过程内有不同作用域、不同的生存期。
+- 同一变量可以在不同的作用域内定义多次，内层的定义会覆盖外层的定义。
+- 在外部块定义的变量，可以在嵌套块中使用。但外部块不能访问嵌套块中的变量。
+
+## 赋值语句
+
+**语法**
+
+给变量赋值的语法请参见[图2](#assignment_value::=)。
+
+**图 2** assignment_value::=<a id="assignment_value::="> </a>
+
+![assignment_value](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/basic-statements-2.png)
+
+对以上语法格式的解释如下：
+
+- variable_name：变量名。
+- value：可以是值或表达式。值value的类型需要和变量variable_name的类型兼容才能正确赋值。
+
+**示例**
+
+```sql
+mogdb=# DECLARE
+    emp_id  INTEGER := 7788;--赋值
+BEGIN
+    emp_id := 5;--赋值
+    emp_id := 5*7784;
+END;
+/
+```
+
+**嵌套赋值**
+
+给变量嵌套赋值的语法请参见[图3](#nested_assignment_value)。
+
+**图 3** nested_assignment_value::=<a id="nested_assignment_value"> </a>
+
+![nested_assignment_value](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/basic-statements-3.png)
+
+对以上语法格式的解释如下：
+
+- variable_name：变量名。
+- col_name：列名。
+- subscript：下标，针对数组变量使用，可以是值或表达式，类型必须为int。
+- value：可以是值或表达式。值value的类型需要和变量variable_name的类型兼容才能正确赋值。
+
+**示例**
+
+```sql
+mogdb=# CREATE TYPE o1 as (a int, b int);
+mogdb=# DECLARE
+    TYPE r1 is VARRAY(10) of o1;
+    emp_id  r1;
+BEGIN
+    emp_id(1).a := 5;--赋值
+    emp_id(1).b := 5*7784;
+END;
+/
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+>
+> - INTO 方式赋值仅支持对第一层列赋值，且不支持二维及以上数组；
+> - 引用嵌套的列值时，若存在数组下标，目前仅支持在前三层列中只存在一个小括号情况，建议使用方括号[ ]引用下标；
+
+## 调用语句
+
+**语法**
+
+调用一个语句的语法请参见[图4](#call_clause::=)。
+
+**图 4** call_clause::=<a id="call_clause::="> </a>
+
+![call_clause](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/basic-statements-4.png)
+
+对以上语法格式的解释如下：
+
+- procedure_name：存储过程名。
+- parameter：存储过程的参数，可以没有或者有多个参数。
+
+**示例**<a id="示例"> </a>
+
+```sql
+--创建存储过程proc_staffs
+mogdb=# CREATE OR REPLACE PROCEDURE proc_staffs
+(
+section     NUMBER(6),
+salary_sum out NUMBER(8,2),
+staffs_count out INTEGER
+)
+IS
+BEGIN
+SELECT sum(salary), count(*) INTO salary_sum, staffs_count FROM hr.staffs where section_id = section;
+END;
+/
+
+--调用存储过程proc_return.
+mogdb=# CALL proc_staffs(2,8,6);
+
+--清除存储过程
+mogdb=# DROP PROCEDURE proc_staffs;
+```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-7-dynamic-statements.md b/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-7-dynamic-statements.md
new file mode 100644
index 0000000000000000000000000000000000000000..af12c44f3cdfc6f70a54814229aa1869e4115ee4
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-7-dynamic-statements.md
@@ -0,0 +1,166 @@
+---
+title: 动态语句
+summary: 动态语句
+author: Guo Huan
+date: 2021-03-04
+---
+
+# 动态语句
+
+## 执行动态查询语句
+
+介绍执行动态查询语句。MogDB提供两种方式：使用EXECUTE IMMEDIATE、OPEN FOR实现动态查询。前者通过动态执行SELECT语句，后者结合了游标的使用。当需要将查询的结果保存在一个数据集用于提取时，可使用OPEN FOR实现动态查询。
+
+**EXECUTE IMMEDIATE**
+
+语法图请参见[图1](#图1)。
+
+**图 1** EXECUTE IMMEDIATE dynamic_select_clause::=<a id="图1"> </a>
+
+![EXECUTE-IMMEDIATE-dynamic_select_clause](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/dynamic-statements-1.png)
+
+using_clause子句的语法图参见[图2](#图2)。
+
+**图 2** using_clause::=<a id="图2"> </a>
+
+![using_clause](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/dynamic-statements-2.png)
+
+对以上语法格式的解释如下:
+
+- define_variable：用于指定存放单行查询结果的变量。
+
+- USING IN bind_argument：用于指定存放传递给动态SQL值的变量，即在dynamic_select_string中存在占位符时使用。
+
+- USING OUT bind_argument：用于指定存放动态SQL返回值的变量。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+    >
+    > - 查询语句中，into和out不能同时存在；
+    > - 占位符命名以“:”开始，后面可跟数字、字符或字符串，与USING子句的bind_argument一一对应；
+    > - bind_argument只能是值、变量或表达式，不能是表名、列名、数据类型等数据库对象，即不支持使用bind_argument为动态SQL语句传递模式对象。如果存储过程需要通过声明参数传递数据库对象来构造动态SQL语句（常见于执行DDL语句时），建议采用连接运算符“||”拼接dynamic_select_clause；
+    > - 动态PL/SQL块允许出现重复的占位符，即相同占位符只能与USING子句的一个bind_argument按位置对应。
+
+**OPEN FOR**
+
+动态查询语句还可以使用OPEN FOR打开动态游标来执行。
+
+语法参见[图3](#图3)。
+
+**图 3** open_for::=<a id="图3"> </a>
+
+![open_for](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/dynamic-statements-3.png)
+
+参数说明:
+
+- cursor_name：要打开的游标名。
+- dynamic_string：动态查询语句。
+- USING value：在dynamic_string中存在占位符时使用。
+
+游标的使用请参考[游标](1-11-cursors)。
+
+## 执行动态非查询语句
+
+**语法**
+
+语法请参见[图4](#noselect::=)。
+
+**图 4** noselect::=<a id="noselect::="> </a>
+
+![noselect](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/dynamic-statements-4.png)
+
+using_clause子句的语法参见[图5](#using_clause::=)。
+
+**图 5** using_clause::=<a id="using_clause::="> </a>
+
+![using_clause-0](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/dynamic-statements-5.png)
+
+对以上语法格式的解释如下：
+
+USING IN bind_argument用于指定存放传递给动态SQL值的变量，在dynamic_noselect_string中存在占位符时使用，即动态SQL语句执行时，bind_argument将替换相对应的占位符。要注意的是，bind_argument只能是值、变量或表达式，不能是表名、列名、数据类型等数据库对象。如果存储过程需要通过声明参数传递数据库对象来构造动态SQL语句（常见于执行DDL语句时），建议采用连接运算符“||”拼接dynamic_select_clause。另外，动态语句允许出现重复的占位符，相同占位符只能与唯一一个bind_argument按位置一一对应。
+
+**示例**
+
+```sql
+--创建表
+mogdb=# CREATE TABLE sections_t1
+(
+   section       NUMBER(4) ,
+   section_name  VARCHAR2(30),
+   manager_id    NUMBER(6),
+   place_id      NUMBER(4)
+);
+
+--声明变量
+mogdb=# DECLARE
+   section       NUMBER(4) := 280;
+   section_name  VARCHAR2(30) := 'Info support';
+   manager_id    NUMBER(6) := 103;
+   place_id      NUMBER(4) := 1400;
+   new_colname   VARCHAR2(10) := 'sec_name';
+BEGIN
+--执行查询
+    EXECUTE IMMEDIATE 'insert into sections_t1 values(:1, :2, :3, :4)'
+       USING section, section_name, manager_id,place_id;
+--执行查询（重复占位符）
+    EXECUTE IMMEDIATE 'insert into sections_t1 values(:1, :2, :3, :1)'
+       USING section, section_name, manager_id;
+--执行ALTER语句（建议采用"||"拼接数据库对象构造DDL语句）
+    EXECUTE IMMEDIATE 'alter table sections_t1 rename section_name to ' || new_colname;
+END;
+/
+
+--查询数据
+mogdb=# SELECT * FROM sections_t1;
+
+--删除表
+mogdb=# DROP TABLE sections_t1;
+```
+
+## 动态调用存储过程
+
+动态调用存储过程必须使用匿名的语句块将存储过程或语句块包在里面，使用EXECUTE IMMEDIATE…USING语句后面带IN、OUT来输入、输出参数。
+
+**语法**
+
+语法请参见[图6](#call_procedure::=)。
+
+**图 6** call_procedure::=<a id="call_procedure::="> </a>
+
+![call_procedure](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/dynamic-statements-6.png)
+
+using_clause子句的语法参见[图7](#using_clause)。
+
+**图 7** using_clause::=<a id="using_clause"> </a>
+
+![using_clause-1](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/dynamic-statements-7.png)
+
+对以上语法格式的解释如下：
+
+- CALL procedure_name：调用存储过程。
+- [:placeholder1，:placeholder2，…]：存储过程参数占位符列表。占位符个数与参数个数相同。
+- USING [IN|OUT|IN OUT] bind_argument：用于指定存放传递给存储过程参数值的变量。bind_argument前的修饰符与对应参数的修饰符一致。
+
+## 动态调用匿名块
+
+动态调用匿名块是指在动态语句中执行匿名块，使用EXECUTE IMMEDIATE…USING语句后面带IN、OUT来输入、输出参数。
+
+**语法**
+
+语法请参见[图8](#call_anonymous_block::=)。
+
+**图 8** call_anonymous_block::=<a id="call_anonymous_block::="> </a>
+
+![call_anonymous_block](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/dynamic-statements-8.png)
+
+using_clause子句的语法参见[图9](#using_clause::)。
+
+**图 9** using_clause::=<a id="using_clause::"> </a>
+
+![using_clause-2](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/dynamic-statements-9.png)
+
+对以上语法格式的解释如下：
+
+- 匿名块程序实施部分，以BEGIN语句开始，以END语句停顿，以一个分号结束。
+- USING [IN|OUT|IN OUT] bind_argument，用于指定存放传递给存储过程参数值的变量。bind_argument前的修饰符与对应参数的修饰符一致。
+- 匿名块中间的输入输出参数使用占位符来指明，要求占位符个数与参数个数相同，并且占位符所对应参数的顺序和USING中参数的顺序一致。
+- 目前MogDB在动态语句调用匿名块时，EXCEPTION语句中暂不支持使用占位符进行输入输出参数的传递。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-8-control-statements.md b/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-8-control-statements.md
new file mode 100644
index 0000000000000000000000000000000000000000..c3848946449017223c5e2a3873ac2371dad64566
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-8-control-statements.md
@@ -0,0 +1,647 @@
+---
+title: 控制语句
+summary: 控制语句
+author: Guo Huan
+date: 2021-03-04
+---
+
+# 控制语句
+
+## 返回语句
+
+MogDB提供两种方式返回数据：RETURN或RETURN NEXT及RETURN QUERY。其中，RETURN NEXT和RETURN QUERY只适用于函数，不适用存储过程。
+
+### RETURN
+
+**语法**
+
+返回语句的语法请参见[图1](#return_clause)。
+
+**图 1** return_clause::=<a id="return_clause"> </a>
+
+![return_clause](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/control-statements-1.jpg)
+
+对以上语法的解释如下：
+
+用于将控制从存储过程或函数返回给调用者。
+
+**示例**
+
+请参见调用语句的[示例](1-6-basic-statements#调用语句)。
+
+### RETURN NEXT及RETURN QUERY
+
+**语法**
+
+创建函数时需要指定返回值SETOF datatype。
+
+return_next_clause::=
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/control-statements-2.png)
+
+return_query_clause::=
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/control-statements-3.png)
+
+对以上语法的解释如下：
+
+当需要函数返回一个集合时，使用RETURN NEXT或者RETURN QUERY向结果集追加结果，然后继续执行函数的下一条语句。随着后续的RETURN NEXT或RETURN QUERY命令的执行，结果集中会有多个结果。函数执行完成后会一起返回所有结果。
+
+RETURN NEXT可用于标量和复合数据类型。
+
+RETURN QUERY有一种变体RETURN QUERY EXECUTE，后面还可以增加动态查询，通过USING向查询插入参数。
+
+**示例**
+
+```sql
+mogdb=# CREATE TABLE t1(a int);
+mogdb=# INSERT INTO t1 VALUES(1),(10);
+
+--RETURN NEXT
+mogdb=# CREATE OR REPLACE FUNCTION fun_for_return_next() RETURNS SETOF t1 AS $$
+DECLARE
+   r t1%ROWTYPE;
+BEGIN
+   FOR r IN select * from t1
+   LOOP
+      RETURN NEXT r;
+   END LOOP;
+   RETURN;
+END;
+$$ LANGUAGE PLPGSQL;
+mogdb=# call fun_for_return_next();
+ a
+---
+ 1
+ 10
+(2 rows)
+
+-- RETURN QUERY
+mogdb=# CREATE OR REPLACE FUNCTION fun_for_return_query() RETURNS SETOF t1 AS $$
+DECLARE
+   r t1%ROWTYPE;
+BEGIN
+   RETURN QUERY select * from t1;
+END;
+$$
+language plpgsql;
+mogdb=# call fun_for_return_query();
+ a
+---
+ 1
+ 10
+(2 rows)
+```
+
+## 条件语句
+
+条件语句的主要作用判断参数或者语句是否满足已给定的条件，根据判定结果执行相应的操作。
+
+MogDB有五种形式的IF：
+
+- IF_THEN
+
+    **图 2** IF_THEN::=
+
+    ![IF_THEN](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/control-statements-4.jpg)
+
+    IF_THEN语句是IF的最简单形式。如果条件为真，statements将被执行。否则，将忽略它们的结果使该IF_THEN语句执行结束。
+
+    **示例**
+
+    ```sql
+    mogdb=# IF v_user_id <> 0 THEN
+        UPDATE users SET email = v_email WHERE user_id = v_user_id;
+    END IF;
+    ```
+
+- IF_THEN_ELSE
+
+    **图 3** IF_THEN_ELSE::=
+
+    ![IF_THEN_ELSE](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/control-statements-5.jpg)
+
+    IF_THEN_ELSE语句增加了ELSE的分支，可以声明在条件为假的时候执行的语句。
+
+    **示例**
+
+    ```sql
+    mogdb=# IF parentid IS NULL OR parentid = ''
+    THEN
+        RETURN;
+    ELSE
+        hp_true_filename(parentid);--表示调用存储过程
+    END IF;
+    ```
+
+- IF_THEN_ELSE IF
+
+  I F语句可以嵌套，嵌套方式如下：
+
+    ```bash
+   mogdb=# IF sex = 'm' THEN
+        pretty_sex := 'man';
+    ELSE
+        IF sex = 'f' THEN
+            pretty_sex := 'woman';
+        END IF;
+    END IF;
+    ```
+
+    这种形式实际上就是在一个IF语句的ELSE部分嵌套了另一个IF语句。因此需要一个END IF语句给每个嵌套的IF，另外还需要一个END IF语句结束父IF-ELSE。如果有多个选项，可使用下面的形式。
+
+- IF_THEN_ELSIF_ELSE
+
+    **图 4** IF_THEN_ELSIF_ELSE::=
+
+    ![IF_THEN_ELSIF_ELSE](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/control-statements-6.png)
+
+    **示例**
+
+    ```bash
+    IF number_tmp = 0 THEN
+        result := 'zero';
+    ELSIF number_tmp > 0 THEN
+        result := 'positive';
+    ELSIF number_tmp < 0 THEN
+        result := 'negative';
+    ELSE
+        result := 'NULL';
+    END IF;
+    ```
+
+- IF_THEN_ELSEIF_ELSE
+
+    ELSEIF是ELSIF的别名。
+
+    综合示例
+
+    ```sql
+    CREATE OR REPLACE PROCEDURE proc_control_structure(i in integer)
+    AS
+        BEGIN
+            IF i > 0 THEN
+                raise info 'i:% is greater than 0. ',i;
+            ELSIF i < 0 THEN
+                raise info 'i:% is smaller than 0. ',i;
+            ELSE
+                raise info 'i:% is equal to 0. ',i;
+            END IF;
+            RETURN;
+        END;
+    /
+
+    CALL proc_control_structure(3);
+
+    --删除存储过程
+    DROP PROCEDURE proc_control_structure;
+    ```
+
+## 循环语句
+
+**简单LOOP语句**
+
+**语法图**
+
+**图 5** loop::=
+
+![loop](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/control-statements-7.png)
+
+**示例**
+
+```sql
+CREATE OR REPLACE PROCEDURE proc_loop(i in integer, count out integer)
+AS
+    BEGIN
+        count:=0;
+        LOOP
+        IF count > i THEN
+            raise info 'count is %. ', count;
+            EXIT;
+        ELSE
+            count:=count+1;
+        END IF;
+        END LOOP;
+    END;
+/
+
+CALL proc_loop(10,5);
+```
+
+> **须知：**
+> 该循环必须要结合EXIT使用，否则将陷入死循环。
+
+**WHILE_LOOP语句**
+
+**语法图**
+
+**图 6** while_loop::=
+
+![while_loop](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/control-statements-8.png)
+
+只要条件表达式为真，WHILE语句就会不停的在一系列语句上进行循环，在每次进入循环体的时候进行条件判断。
+
+**示例**
+
+```sql
+CREATE TABLE integertable(c1 integer) ;
+CREATE OR REPLACE PROCEDURE proc_while_loop(maxval in integer)
+AS
+    DECLARE
+    i int :=1;
+    BEGIN
+        WHILE i < maxval LOOP
+            INSERT INTO integertable VALUES(i);
+            i:=i+1;
+        END LOOP;
+    END;
+/
+
+--调用函数
+CALL proc_while_loop(10);
+
+--删除存储过程和表
+DROP PROCEDURE proc_while_loop;
+DROP TABLE integertable;
+```
+
+**FOR_LOOP（integer变量）语句**
+
+**语法图**
+
+**图 7** for_loop::=
+
+![for_loop](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/control-statements-9.png)
+
+> **说明:**
+>
+> - 变量name会自动定义为integer类型并且只在此循环里存在。变量name介于lower_bound和upper_bound之间。
+> - 当使用REVERSE关键字时，lower_bound必须大于等于upper_bound，否则循环体不会被执行。
+
+**FOR_LOOP查询语句**
+
+**语法图**
+
+**图 8** for_loop_query::=
+
+![for_loop_query](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/control-statements-10.png)
+
+> **说明:**
+> 变量target会自动定义，类型和query的查询结果的类型一致，并且只在此循环中有效。target的取值就是query的查询结果。
+
+**FORALL批量查询语句**
+
+**语法图**
+
+**图 9** forall::=
+
+![forall](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/control-statements-11.png)
+
+> **说明:**
+> 变量index会自动定义为integer类型并且只在此循环里存在。index的取值介于low_bound和upper_bound之间。
+
+**示例**
+
+```sql
+CREATE TABLE hdfs_t1 (
+  title NUMBER(6),
+  did VARCHAR2(20),
+  data_peroid VARCHAR2(25),
+  kind VARCHAR2(25),
+  interval VARCHAR2(20),
+  time DATE,
+  isModified VARCHAR2(10)
+);
+
+INSERT INTO hdfs_t1 VALUES( 8, 'Donald', 'OConnell', 'DOCONNEL', '650.507.9833', to_date('21-06-1999', 'dd-mm-yyyy'), 'SH_CLERK' );
+
+CREATE OR REPLACE PROCEDURE proc_forall()
+AS
+BEGIN
+    FORALL i IN 100..120
+        update hdfs_t1 set title = title + 100*i;
+END;
+/
+
+--调用函数
+CALL proc_forall();
+
+--查询存储过程调用结果
+SELECT * FROM hdfs_t1 WHERE title BETWEEN 100 AND 120;
+
+--删除存储过程和表
+DROP PROCEDURE proc_forall;
+DROP TABLE hdfs_t1;
+```
+
+## 分支语句
+
+**语法**
+
+分支语句的语法请参见[图10](#case_when)。
+
+**图 10** case_when::=<a id="case_when"> </a>
+
+![case_when](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/control-statements-12.png)
+
+when_clause子句的语法图参见[图11](#when_clause)。
+
+**图 11** when_clause::=<a id="when_clause"> </a>
+
+![when_clause](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/control-statements-13.png)
+
+参数说明:
+
+- case_expression：变量或表达式。
+- when_expression：常量或者条件表达式。
+- statement：执行语句。
+
+**示例**
+
+```sql
+CREATE OR REPLACE PROCEDURE proc_case_branch(pi_result in integer, pi_return out integer)
+AS
+    BEGIN
+        CASE pi_result
+            WHEN 1 THEN
+                pi_return := 111;
+            WHEN 2 THEN
+                pi_return := 222;
+            WHEN 3 THEN
+                pi_return := 333;
+            WHEN 6 THEN
+                pi_return := 444;
+            WHEN 7 THEN
+                pi_return := 555;
+            WHEN 8 THEN
+                pi_return := 666;
+            WHEN 9 THEN
+                pi_return := 777;
+            WHEN 10 THEN
+                pi_return := 888;
+            ELSE
+                pi_return := 999;
+        END CASE;
+        raise info 'pi_return : %',pi_return ;
+END;
+/
+
+CALL proc_case_branch(3,0);
+
+--删除存储过程
+DROP PROCEDURE proc_case_branch;
+```
+
+## 空语句
+
+在PL/SQL程序中，可以用NULL语句来说明“不用做任何事情”，相当于一个占位符，可以使某些语句变得有意义，提高程序的可读性。
+
+**语法**
+
+空语句的用法如下：
+
+```sql
+DECLARE
+    …
+BEGIN
+    …
+    IF v_num IS NULL THEN
+        NULL; -- 不需要处理任何数据。
+    END IF;
+END;
+/
+```
+
+## 错误捕获语句
+
+缺省时，当PL/SQL函数执行过程中发生错误时退出函数执行，并且周围的事务也会回滚。可以用一个带有EXCEPTION子句的BEGIN块捕获错误并且从中恢复。其语法是正常的BEGIN块语法的一个扩展：
+
+```sql
+[<<label>>]
+[DECLARE
+    declarations]
+BEGIN
+    statements
+EXCEPTION
+    WHEN condition [OR condition ...] THEN
+        handler_statements
+    [WHEN condition [OR condition ...] THEN
+        handler_statements
+    ...]
+END;
+```
+
+如果没有发生错误，这种形式的块儿只是简单地执行所有语句，然后转到END之后的下一个语句。但是如果在执行的语句内部发生了一个错误，则这个语句将会回滚，然后转到EXCEPTION列表。寻找匹配错误的第一个条件。若找到匹配，则执行对应的handler_statements，然后转到END之后的下一个语句。如果没有找到匹配，则会向事务的外层报告错误，和没有EXCEPTION子句一样。错误码可以捕获同一类的其他错误码。
+
+也就是说该错误可以被一个包围块用EXCEPTION捕获，如果没有包围块，则进行退出函数处理。
+
+condition的名称可以是SQL标准错误码编号说明的任意值。特殊的条件名OTHERS匹配除了QUERY_CANCELED之外的所有错误类型。
+
+如果在选中的handler_statements里发生了新错误，则不能被这个EXCEPTION子句捕获，而是向事务的外层报告错误。一个外层的EXCEPTION子句可以捕获它。
+
+如果一个错误被EXCEPTION捕获，PL/SQL函数的局部变量保持错误发生时的原值，但是所有该块中想写入数据库中的状态都回滚。
+
+示例：
+
+```sql
+CREATE TABLE mytab(id INT,firstname VARCHAR(20),lastname VARCHAR(20)) ;
+
+INSERT INTO mytab(firstname, lastname) VALUES('Tom', 'Jones');
+
+CREATE FUNCTION fun_exp() RETURNS INT
+AS $$
+DECLARE
+    x INT :=0;
+    y INT;
+BEGIN
+    UPDATE mytab SET firstname = 'Joe' WHERE lastname = 'Jones';
+    x := x + 1;
+    y := x / 0;
+EXCEPTION
+    WHEN division_by_zero THEN
+        RAISE NOTICE 'caught division_by_zero';
+        RETURN x;
+END;$$
+LANGUAGE plpgsql;
+
+call fun_exp();
+NOTICE:  caught division_by_zero
+ fun_exp
+---------
+       1
+(1 row)
+
+select * from mytab;
+ id | firstname | lastname
+----+-----------+----------
+    | Tom       | Jones
+(1 row)
+
+DROP FUNCTION fun_exp();
+DROP TABLE mytab;
+```
+
+当控制到达给y赋值的地方时，会有一个division_by_zero错误失败。这个错误将被EXCEPTION子句捕获。而在RETURN语句里返回的数值将是x的增量值。
+
+> **说明：**
+> 进入和退出一个包含EXCEPTION子句的块要比不包含的块开销大的多。因此，不必要的时候不要使用EXCEPTION。
+> 在下列场景中，无法捕获处理异常，整个存储过程回滚：节点故障、网络故障引起的存储过程参与节点线程退出以及COPY FROM操作中源数据与目标表的表结构不一致造成的异常。
+
+示例：UPDATE/INSERT异常
+
+这个例子根据使用异常处理器执行恰当的UPDATE或INSERT 。
+
+```sql
+CREATE TABLE db (a INT, b TEXT);
+
+CREATE FUNCTION merge_db(key INT, data TEXT) RETURNS VOID AS
+$$
+BEGIN
+    LOOP
+
+--第一次尝试更新key
+        UPDATE db SET b = data WHERE a = key;
+        IF found THEN
+            RETURN;
+        END IF;
+--不存在，所以尝试插入key，如果其他人同时插入相同的key，我们可能得到唯一key失败。
+        BEGIN
+            INSERT INTO db(a,b) VALUES (key, data);
+            RETURN;
+        EXCEPTION WHEN unique_violation THEN
+        --什么也不做，并且循环尝试再次更新。
+        END;
+     END LOOP;
+END;
+$$
+LANGUAGE plpgsql;
+
+SELECT merge_db(1, 'david');
+SELECT merge_db(1, 'dennis');
+
+--删除FUNCTION和TABLE
+DROP FUNCTION merge_db;
+DROP TABLE db;
+```
+
+## GOTO语句
+
+GOTO语句可以实现从GOTO位置到目标语句的无条件跳转。GOTO语句会改变原本的执行逻辑，因此应该慎重使用，或者也可以使用EXCEPTION处理特殊场景。当执行GOTO语句时，目标Label必须是唯一的。
+
+**语法**
+
+label declaration ::=
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/control-statements-14.png)
+
+goto statement ::=
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/developer-guide/control-statements-15.png)
+
+**示例**
+
+```sql
+mogdb=# CREATE OR REPLACE PROCEDURE GOTO_test()
+AS
+DECLARE
+    v1  int;
+BEGIN
+    v1  := 0;
+        LOOP
+        EXIT WHEN v1 > 100;
+                v1 := v1 + 2;
+                if v1 > 25 THEN
+                        GOTO pos1;
+                END IF;
+        END LOOP;
+<<pos1>>
+v1 := v1 + 10;
+raise info 'v1 is %. ', v1;
+END;
+/
+
+call GOTO_test();
+```
+
+**限制场景**
+
+GOTO使用有以下限制场景
+
+- 不支持有多个相同的GOTO labels目标场景，无论是否在同一个block中。
+
+    ```sql
+    BEGIN
+      GOTO pos1;
+      <<pos1>>
+      SELECT * FROM ...
+      <<pos1>>
+      UPDATE t1 SET ...
+    END;
+    ```
+
+- 不支持GOTO跳转到IF语句，CASE语句，LOOP语句中。
+
+    ```sql
+    BEGIN
+       GOTO pos1;
+       IF valid THEN
+         <<pos1>>
+         SELECT * FROM ...
+       END IF;
+     END;
+    ```
+
+- 不支持GOTO语句从一个IF子句跳转到另一个IF子句，或从一个CASE语句的WHEN子句跳转到另一个WHEN子句。
+
+    ```sql
+    BEGIN
+       IF valid THEN
+         GOTO pos1;
+         SELECT * FROM ...
+       ELSE
+         <<pos1>>
+         UPDATE t1 SET ...
+       END IF;
+     END;
+    ```
+
+- 不支持从外部块跳转到内部的BEGIN-END块。
+
+    ```sql
+    BEGIN
+       GOTO pos1;
+       BEGIN
+         <<pos1>>
+         UPDATE t1 SET ...
+       END;
+     END;
+    ```
+
+- 不支持从异常处理部分跳转到当前的BEGIN-END块。但可以跳转到上层BEGIN-END块。
+
+    ```sql
+    BEGIN
+       <<pos1>>
+       UPDATE t1 SET ...
+       EXCEPTION
+         WHEN condition THEN
+            GOTO pos1;
+     END;
+    ```
+
+- 如果从GOTO到一个不包含执行语句的位置，需要添加NULL语句。
+
+    ```sql
+    DECLARE
+       done  BOOLEAN;
+    BEGIN
+       FOR i IN 1..50 LOOP
+          IF done THEN
+             GOTO end_loop;
+          END IF;
+          <<end_loop>>  -- not allowed unless an executable statement follows
+          NULL; -- add NULL statement to avoid error
+       END LOOP;  -- raises an error without the previous NULL
+    END;
+    /
+    ```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-9-transaction-management.md b/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-9-transaction-management.md
new file mode 100644
index 0000000000000000000000000000000000000000..6523976e19bba7b7741f79f3e5a7b49c17c36b18
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/plpgsql/1-9-transaction-management.md
@@ -0,0 +1,420 @@
+---
+title: 事务管理
+summary: 事务管理
+author: Guo Huan
+date: 2021-03-04
+---
+
+# 事务管理
+
+存储过程本身就处于一个事务中，开始调用最外围存储过程时会自动开启一个事务，在调用结束时自动提交或者发生异常时回滚。除了系统自动的事务控制外，也可以使用COMMIT/ROLLBACK来控制存储过程中的事务。在存储过程中调用COMMIT/ROLLBACK命令，将提交/回滚当前事务并自动开启一个新的事务，后续的所有操作都会在此新事务中运行。
+
+保存点SAVEPOINT是事务中的一个特殊记号，它允许将那些在它建立后执行的命令全部回滚，把事务的状态恢复到保存点所在的时刻。存储过程中允许使用保存点来进行事务管理，当前支持保存点的创建、回滚和释放操作。存储过程中使用回滚保存点只是回退当前事务的修改，而不会改变存储过程的执行流程，也不会回退存储过程中的局部变量值等。
+
+## 语法格式
+
+```sql
+定义保存点
+    SAVEPOINT savepoint_name;
+回滚保存点
+    ROLLBACK TO [SAVEPOINT] savepoint_name;
+释放保存点
+    RELEASE [SAVEPOINT] savepoint_name;
+```
+
+## **使用场景**
+
+支持调用的上下文环境：
+
+- 支持在PLSQL的存储过程内使用COMMIT/ROLLBACK/SAVEPOINT。
+- 支持含有EXCEPTION的存储过程使用COMMIT/ROLLBACK/SAVEPOINT。
+- 支持在存储过程的EXCEPTION语句内使用COMMIT/ROLLBACK/SAVEPOINT。
+- 支持在事务块里调用含有COMMIT/ROLLBACK/SAVEPOINT的存储过程，即通过/BEGIN/START/END等开启控制的外部事务。
+- 支持在子事务中调用含有SAVEPOINT的存储过程，即存储过程中使用外部定义的SAVEPOINT，回退事务状态到存储过程外定义的SAVEPOINT位置。
+- 支持存储过程外部对存储过程内定义的SAVEPOINT可见，即存储过程外可以将事务修改回滚到存储过程中定义SAVEPOINT的位置。
+- 支持多数PLSQL的上下文和语句内调用COMMIT/ROLLBACK/SAVEPOINT，包括常用的IF/FOR/CURSOR LOOP/WHILE。
+
+## **使用限制**
+
+不支持调用的上下文环境：
+
+- 不支持除PLSQL的其他存储过程中调用COMMIT/ROLLBACK/SAVEPOINT，例如PLJAVA、PLPYTHON等。
+- 不支持函数中调用COMMIT/ROLLBACK/SAVEPOINT，包括函数调用含有COMMIT/ROLLBACK/SAVEPOINT的存储过程。
+- 不支持事务块中调用了SAVEPOINT后，调用含有COMMIT/ROLLBACK的存储过程。
+- 不支持TRIGGER中调用含有COMMIT/ROLLBACK/SAVEPOINT语句的存储过程。
+- 不支持EXECUTE语句中调用COMMIT/ROLLBACK/SAVEPOINT语句。
+- 不支持在CURSOR语句中打开一个含有COMMIT/ROLLBACK/SAVEPOINT的存储过程。
+- 不支持带有IMMUTABLE以及SHIPPABLE的存储过程调用COMMIT/ROLLBACK/SAVEPOINT，或调用带有COMMIT/ROLLBACK/SAVEPOINT语句的存储过程。
+- 不支持SQL中调用含有COMMIT/ROLLBACK/SAVEPOINT语句的存储过程，除了SELECT PROC以及CALL PROC。
+- 存储过程头带有GUC参数设置的不允许调用COMMIT/ROLLBACK/SAVEPOINT语句。
+- 不支持CURSOR/EXECUTE语句，以及各类表达式内调用COMMIT/ROLLBACK/SAVEPOINT。
+- 不支持存储过程返回值与表达式计算中调用含有COMMIT/ROLLBACK/SAVEPOINT的存储过程。
+- 自治事务和存储过程事务是两个独立的事务，不能互相使用对方事务中定义的保存点。
+
+不支持提交回滚的内容：
+
+- 不支持存储过程内声明变量以及传入变量的提交/回滚。
+- 不支持存储过程内必须重启生效的GUC参数的提交/回滚。
+
+**示例**
+
+- 示例1：支持在PLSQL的存储过程内使用COMMIT/ROLLBACK。
+
+    ```sql
+    CREATE TABLE EXAMPLE1(COL1 INT);
+
+    CREATE OR REPLACE PROCEDURE TRANSACTION_EXAMPLE()
+    AS
+    BEGIN
+        FOR i IN 0..20 LOOP
+            INSERT INTO EXAMPLE1(COL1) VALUES (i);
+            IF i % 2 = 0 THEN
+                COMMIT;
+            ELSE
+                ROLLBACK;
+            END IF;
+        END LOOP;
+    END;
+    /
+    ```
+
+- 示例2：
+
+    支持含有EXCEPTION的存储过程使用COMMIT/ROLLBACK。
+
+    支持在存储过程的EXCEPTION语句内使用COMMIT/ROLLBACK。
+
+    支持DDL在COMMIT/ROLLBACK后的提交/回滚。
+
+    ```sql
+    CREATE OR REPLACE PROCEDURE TEST_COMMIT_INSERT_EXCEPTION_ROLLBACK()
+    AS
+    BEGIN
+        DROP TABLE IF EXISTS TEST_COMMIT;
+        CREATE TABLE TEST_COMMIT(A INT, B INT);
+        INSERT INTO TEST_COMMIT SELECT 1, 1;
+        COMMIT;
+            CREATE TABLE TEST_ROLLBACK(A INT, B INT);
+        RAISE EXCEPTION 'RAISE EXCEPTION AFTER COMMIT';
+    EXCEPTION
+        WHEN OTHERS THEN
+        INSERT INTO TEST_COMMIT SELECT 2, 2;
+        ROLLBACK;
+    END;
+    /
+
+    ```
+
+- 示例3：支持在事务块里调用含有COMMIT/ROLLBACK的存储过程，即通过/BEGIN/START/END等开启控制的外部事务。
+
+    ```sql
+    BEGIN;
+        CALL TEST_COMMIT_INSERT_EXCEPTION_ROLLBACK();
+    END;
+    ```
+
+- 示例4：支持多数PLSQL的上下文和语句内调用COMMIT/ROLLBACK，包括常用的IF/FOR/CURSOR LOOP/WHILE。
+
+    ```sql
+    CREATE OR REPLACE PROCEDURE TEST_COMMIT2()
+    IS
+    BEGIN
+        DROP TABLE IF EXISTS TEST_COMMIT;
+        CREATE TABLE TEST_COMMIT(A INT);
+        FOR I IN REVERSE 3..0 LOOP
+        INSERT INTO TEST_COMMIT SELECT I;
+        COMMIT;
+        END LOOP;
+        FOR I IN REVERSE 2..4 LOOP
+        UPDATE TEST_COMMIT SET A=I;
+        COMMIT;
+        END LOOP;
+    EXCEPTION
+    WHEN OTHERS THEN
+        INSERT INTO TEST_COMMIT SELECT 4;
+        COMMIT;
+    END;
+    /
+    ```
+
+- 示例5：支持存储过程内GUC参数的回滚提交。
+
+    ```sql
+    SHOW explain_perf_mode;
+    SHOW enable_force_vector_engine;
+
+    CREATE OR REPLACE PROCEDURE GUC_ROLLBACK()
+    AS
+    BEGIN
+        SET enable_force_vector_engine = on;
+        COMMIT;
+        SET explain_perf_mode TO pretty;
+        ROLLBACK;
+    END;
+    /
+
+    call GUC_ROLLBACK();
+    SHOW explain_perf_mode;
+    SHOW enable_force_vector_engine;
+    SET enable_force_vector_engine = off;
+    ```
+
+- 示例6：函数（Function）中不允许调用commit/rollback语句，同时不允许函数调用含有commit/rollback的存储过程。
+
+    ```sql
+    CREATE OR REPLACE FUNCTION FUNCTION_EXAMPLE1() RETURN INT
+    AS
+    EXP INT;
+    BEGIN
+        FOR i IN 0..20 LOOP
+            INSERT INTO EXAMPLE1(col1) VALUES (i);
+            IF i % 2 = 0 THEN
+                COMMIT;
+            ELSE
+                ROLLBACK;
+            END IF;
+        END LOOP;
+        SELECT COUNT(*) FROM EXAMPLE1 INTO EXP;
+        RETURN EXP;
+    END;
+    /
+    ```
+
+- 示例7：函数（Fucntion）中不允许调用带有commit/rollback语句的存储过程。
+
+    ```sql
+    CREATE OR REPLACE FUNCTION FUNCTION_EXAMPLE2() RETURN INT
+    AS
+    EXP INT;
+    BEGIN
+        --transaction_example为存储过程，带有commit/rollback语句
+        CALL transaction_example();
+        SELECT COUNT(*) FROM EXAMPLE1 INTO EXP;
+        RETURN EXP;
+    END;
+    /
+    ```
+
+- 示例8：不允许Trigger的存储过程包含commit/rollback语句，或调用带有commit/rollback语句的存储过程。
+
+    ```sql
+    CREATE OR REPLACE FUNCTION FUNCTION_TRI_EXAMPLE2() RETURN TRIGGER
+    AS
+    EXP INT;
+    BEGIN
+        FOR i IN 0..20 LOOP
+            INSERT INTO EXAMPLE1(col1) VALUES (i);
+            IF i % 2 = 0 THEN
+                COMMIT;
+            ELSE
+                ROLLBACK;
+            END IF;
+        END LOOP;
+        SELECT COUNT(*) FROM EXAMPLE1 INTO EXP;
+    END;
+    /
+
+    CREATE TRIGGER TRIGGER_EXAMPLE AFTER DELETE ON EXAMPLE1
+    FOR EACH ROW EXECUTE PROCEDURE FUNCTION_TRI_EXAMPLE2();
+
+    DELETE FROM EXAMPLE1;
+    ```
+
+- 示例9：不支持带有IMMUABLE以及SHIPPABLE的存储过程调用commit/rollback，或调用带有commit/rollback语句的存储过程。
+
+    ```sql
+    CREATE OR REPLACE PROCEDURE TRANSACTION_EXAMPLE1()
+    IMMUTABLE
+    AS
+    BEGIN
+        FOR i IN 0..20 LOOP
+            INSERT INTO EXAMPLE1 (col1) VALUES (i);
+            IF i % 2 = 0 THEN
+                COMMIT;
+            ELSE
+                ROLLBACK;
+            END IF;
+        END LOOP;
+    END;
+    /
+    ```
+
+- 示例10：不支持存储过程中任何变量的提交，包括存储过程内声明的变量或者传入的参数。
+
+    ```sql
+    CREATE OR REPLACE PROCEDURE TRANSACTION_EXAMPLE2(EXP_OUT OUT INT)
+    AS
+    EXP INT;
+    BEGIN
+        EXP_OUT := 0;
+        COMMIT;
+        DBE_OUTPUT.PRINT_LINE('EXP IS:'||EXP);
+        EXP_OUT := 1;
+        ROLLBACK;
+        DBE_OUTPUT.PRINT_LINE('EXP IS:'||EXP);
+    END;
+    /
+    ```
+
+- 示例11：不支持出现在SQL中的调用（除了Select Procedure）。
+
+    ```sql
+    CREATE OR REPLACE PROCEDURE TRANSACTION_EXAMPLE3()
+    AS
+    BEGIN
+        FOR i IN 0..20 LOOP
+            INSERT INTO EXAMPLE1 (col1) VALUES (i);
+            IF i % 2 = 0 THEN
+                EXECUTE IMMEDIATE 'COMMIT';
+            ELSE
+                EXECUTE IMMEDIATE 'ROLLBACK';
+            END IF;
+        END LOOP;
+    END;
+    /
+    ```
+
+- 示例12：存储过程头带有GUC参数设置的不允许调用commit/rollback语句。
+
+    ```sql
+    CREATE OR REPLACE PROCEDURE TRANSACTION_EXAMPLE4()
+    SET ARRAY_NULLS TO "ON"
+    AS
+    BEGIN
+        FOR i IN 0..20 LOOP
+            INSERT INTO EXAMPLE1 (col1) VALUES (i);
+            IF i % 2 = 0 THEN
+                COMMIT;
+            ELSE
+                ROLLBACK;
+            END IF;
+        END LOOP;
+    END;
+    /
+    ```
+
+- 示例13：游标open的对象不允许为带有commit/rollback语句的存储过程。
+
+    ```sql
+    CREATE OR REPLACE PROCEDURE TRANSACTION_EXAMPLE5(INTIN IN INT, INTOUT OUT INT)
+    AS
+    BEGIN
+    INTOUT := INTIN + 1;
+    COMMIT;
+    END;
+    /
+
+    CREATE OR REPLACE PROCEDURE TRANSACTION_EXAMPLE6()
+    AS
+    CURSOR CURSOR1(EXPIN INT)
+    IS SELECT TRANSACTION_EXAMPLE5(EXPIN);
+    INTEXP INT;
+    BEGIN
+        FOR i IN 0..20 LOOP
+            OPEN CURSOR1(i);
+            FETCH CURSOR1 INTO INTEXP;
+            INSERT INTO EXAMPLE1(COL1) VALUES (INTEXP);
+            IF i % 2 = 0 THEN
+                COMMIT;
+            ELSE
+                ROLLBACK;
+            END IF;
+            CLOSE CURSOR1;
+        END LOOP;
+    END;
+    /
+    ```
+
+- 示例14：不支持CURSOR/EXECUTE语句，以及各类表达式内调用COMMIT/ROLLBACK。
+
+    ```sql
+    CREATE OR REPLACE PROCEDURE exec_func1()
+    AS
+    BEGIN
+        CREATE TABLE TEST_exec(A INT);
+    COMMIT;
+    END;
+    /
+    CREATE OR REPLACE PROCEDURE exec_func2()
+    AS
+    BEGIN
+    EXECUTE exec_func1();
+    COMMIT;
+    END;
+    /
+    ```
+
+- 示例15：不支持存储过程返回值与表达式计算。
+
+    ```sql
+    CREATE OR REPLACE PROCEDURE exec_func3(RET_NUM OUT INT)
+    AS
+    BEGIN
+        RET_NUM := 1+1;
+    COMMIT;
+    END;
+    /
+    CREATE OR REPLACE PROCEDURE exec_func4(ADD_NUM IN INT)
+    AS
+    SUM_NUM INT;
+    BEGIN
+    SUM_NUM := ADD_NUM + exec_func3();
+    COMMIT;
+    END;
+    /
+    ```
+
+- 示例16：存储过程使用保存点回退事务部分修改。
+
+    ```sql
+    CREATE OR REPLACE PROCEDURE STP_SAVEPOINT_EXAMPLE1()
+    AS
+    BEGIN
+        INSERT INTO EXAMPLE1 VALUES(1);
+        SAVEPOINT s1;
+        INSERT INTO EXAMPLE1 VALUES(2);
+        ROLLBACK TO s1;  -- 回退插入记录2
+        INSERT INTO EXAMPLE1 VALUES(3);
+    END;
+    /
+    ```
+
+- 示例17：存储过程中使用保存点回退到存储过程外部定义的保存点。
+
+    ```sql
+    CREATE OR REPLACE PROCEDURE STP_SAVEPOINT_EXAMPLE2()
+    AS
+    BEGIN
+        INSERT INTO EXAMPLE1 VALUES(2);
+        ROLLBACK TO s1;  -- 回退插入记录2
+        INSERT INTO EXAMPLE1 VALUES(3);
+    END;
+    /
+
+    BEGIN;
+    INSERT INTO EXAMPLE1 VALUES(1);
+    SAVEPOINT s1;
+    CALL STP_SAVEPOINT_EXAMPLE2();
+    SELECT * FROM EXAMPLE1;
+    COMMIT;
+    ```
+
+- 示例18：存储过程外部回退到存储过程中定义的保存点。
+
+    ```sql
+    CREATE OR REPLACE PROCEDURE STP_SAVEPOINT_EXAMPLE3()
+    AS
+    BEGIN
+        INSERT INTO EXAMPLE1 VALUES(1);
+        SAVEPOINT s1;
+        INSERT INTO EXAMPLE1 VALUES(2);
+    END;
+    /
+
+    BEGIN;
+    INSERT INTO EXAMPLE1 VALUES(3);
+    CALL STP_SAVEPOINT_EXAMPLE3();
+    ROLLBACK TO SAVEPOINT s1; --回退存储过程中插入记录2
+    SELECT * FROM EXAMPLE1;
+    COMMIT;
+    ```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/resource-load-management/resource-load-management-overview.md b/product/zh/docs-mogdb/v3.0/developer-guide/resource-load-management/resource-load-management-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..b733ee346f9f74751c800fbc0abfc8c953ddb82f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/resource-load-management/resource-load-management-overview.md
@@ -0,0 +1,26 @@
+---
+title: 资源负载管理概述
+summary: 资源负载管理概述
+author: Guo Huan
+date: 2021-10-22
+---
+
+# 资源负载管理概述
+
+## 功能描述
+
+MogDB提供了资源负载管理手段，来均衡任务对系统资源的利用。
+
+## 相关概念
+
+**资源管理**
+
+MogDB对于系统资源的管理范围包含CPU资源、内存资源、IO资源和存储资源。通过对系统的资源进行合理的分配，避免发生资源的不合理占用导致系统运行效率下降或者引发系统运行问题。
+
+**控制组**
+
+控制组（Cgroups）是control groups的缩写，是Linux内核提供的一种可以限制、记录、隔离进程组所使用的物理资源（如：CPU、内存、IO等）的机制。如果一个进程加入了某一个控制组，该控制组对Linux的系统资源都有严格的限制，进程在使用这些资源时，不能超过其最大限制。更多Cgroups的原理介绍，请查看相关操作系统的产品手册。
+
+**资源池**
+
+资源池（Resource Pool）是MogDB提供的一种配置机制，用于对主机资源（内存、IO）进行划分并提供SQL的并发控制能力。资源池通过绑定Cgroups对资源进行管理。用户通过绑定资源池可以实现对其下作业的资源负载管理。
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/resource-load-management/resource-management-preparation/creating-a-resource-pool.md b/product/zh/docs-mogdb/v3.0/developer-guide/resource-load-management/resource-management-preparation/creating-a-resource-pool.md
new file mode 100644
index 0000000000000000000000000000000000000000..8ac3dc5dde0568f79dcc1a0cf873f35ccbac5670
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/resource-load-management/resource-management-preparation/creating-a-resource-pool.md
@@ -0,0 +1,152 @@
+---
+title: 创建资源池
+summary: 创建资源池
+author: Guo Huan
+date: 2021-10-22
+---
+
+# 创建资源池
+
+## 背景信息
+
+MogDB支持通过创建资源池对主机资源进行划分。开启资源负载管理之后，仅使用默认资源池并不能满足业务对资源负载管理的诉求，必须根据需要创建新的资源池，对系统资源进行重分配，来满足实际业务对系统资源精细管理的需要。普通资源池的特点见表1。
+
+**表 1** 普通资源池的特点
+
+| 资源池分类             | 特点                                                         |
+| :--------------------- | :----------------------------------------------------------- |
+| 普通资源池（普通场景） | 关联Workload控制组。 且必须没有组资源池关联该控制组对应的子class。即如果创建业务资源池关联控制组‘class1:wd’，那么必须没有组资源池关联‘class1’。mem_percent默认为0%，没有mem_percent相加小于100%的限制。 |
+
+在开启了资源负载管理功能之后，系统会自动创建default_pool，当一个会话或者用户没有指定关联的资源池时，都会被默认关联到default_pool。default_pool默认绑定DefaultClass:Medium控制组，并且不限制所关联的业务的并发数。default_pool的详细属性如表2所示。
+
+**表 2** default_pool属性
+
+| 属性              | 属性值              | 说明                                                         |
+| :---------------- | :------------------ | :----------------------------------------------------------- |
+| respool_name      | default_pool        | 资源池名称。                                                 |
+| mem_percent       | 100                 | 最大占用内存百分比。                                         |
+| cpu_affinity      | -1                  | CPU亲和性，保留参数。                                        |
+| control_group     | DefaultClass:Medium | 资源池关联的控制组。                                         |
+| active_statements | -1                  | 资源池允许的最大并发数。-1为不限制并发数量。                 |
+| max_dop           | 1                   | 开启SMP后，算子执行的并发度，保留参数。                      |
+| memory_limit      | 8GB                 | 内存使用上限，保留参数。                                     |
+| parentid          | 0                   | 父资源池OID。                                                |
+| io_limits         | 0                   | 每秒触发IO的次数上限。行存单位是万次/s，列存是次/s。0表示不控制。 |
+| io_priority       | None                | IO利用率高达90%时，重消耗IO作业进行IO资源管控时关联的优先级等级。None表示不控制。 |
+| nodegroup         | installation        | 资源池所在的逻辑集群的名称。                                 |
+| is_foreign        | f                   | 资源池不用于逻辑集群之外的用户。                             |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** MogDB不允许对default_pool参数进行修改。
+
+## 前提条件
+
+已熟悉[CREATE RESOURCE POOL](53.2-CREATE-RESOURCE-POOL)、[ALTER RESOURCE POOL](11.3-ALTER-RESOURCE-POOL)和[DROP RESOURCE POOL](86.2-DROP-RESOURCE-POOL)语法的使用。
+
+## 操作过程
+
+**创建资源池**
+
+1. [使用gsql连接数据库](using-the-gsql-client-for-connection)。
+
+2. 创建组资源池关联到指定的子Class控制组。例如下面：名称为“resource_pool_a”的组资源池关联到了“class_a”控制组。
+
+   ```sql
+   mogdb=# CREATE RESOURCE POOL resource_pool_a WITH (control_group='class_a');
+   mogdb=# CREATE RESOURCE POOL resource_pool_b WITH (control_group='class_b');
+   CREATE RESOURCE POOL
+   ```
+
+3. 创建业务资源池关联到指定的Workload控制组。例如下面：名称为“resource_pool_a1”的业务资源池关联到了“workload_a1”控制组。
+
+   ```sql
+   mogdb=# CREATE RESOURCE POOL resource_pool_a1 WITH (control_group='class_a:workload_a1');
+   mogdb=# CREATE RESOURCE POOL resource_pool_a2 WITH (control_group='class_a:workload_a2');
+   mogdb=# CREATE RESOURCE POOL resource_pool_b1 WITH (control_group='class_b:workload_b1');
+   mogdb=# CREATE RESOURCE POOL resource_pool_b2 WITH (control_group='class_b:workload_b2');
+   CREATE RESOURCE POOL
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **NOTE:**
+   >
+   > - 如果在创建资源池的时候不指定所关联的控制组，则该资源池会被关联到默认控制组（DefaultClass控制组下的“Medium” Timeshare控制组）。
+   > - control_group取值区分大小写，指定时要使用单引号。
+   > - 若数据库用户指定Timeshare控制组代表的字符串，即“Rush”、“High”、“Medium”或“Low”其中一种，如control_group的字符串为“High”，代表资源池指定到DefaultClass控制组下的“High” Timeshare控制组。
+   > - control_group可以指定用户创建Workload控制组，即'class1:wd'，也可以带有控制组的级别，例如：'class1:wd:2'，这个级别范围一定要在1-10的范围内，但这个级别将不做任何区分作用。在旧版本中，允许创建同名Workload控制组，以级别进行区分。但新版本升级后，不允许创建同名控制组，用户如在旧版本中已创建同名Workload控制组，使用过程中其级别将不进行区分，由此可能造成的控制组不明确使用的问题，需要用户自行把旧的同名控制组删除以明确控制组使用。
+
+**管理资源池**
+
+修改资源池的属性。例如下面：修改资源池“resource_pool_a2”关联的控制组为“class_a:workload_a1”（假设class_a:workload_a1未被其他资源池关联）。
+
+```sql
+mogdb=# ALTER RESOURCE POOL resource_pool_a2 WITH (control_group="class_a:workload_a1");
+ALTER RESOURCE POOL
+```
+
+**删除资源池**
+
+删除资源池。例如下面删除资源池“resource_pool_a2”
+
+```sql
+mogdb=# DROP RESOURCE POOL resource_pool_a2;
+DROP RESOURCE POOL
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 如果某个角色已关联到该资源池，无法删除。
+> - 多租户场景下，如果删除组资源池，其业务资源池都将被删除。只有不关联用户时，资源池才能被删除。
+
+## 查看资源池的信息
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+>
+> - 不允许使用INSERT、UPDATE、DELETE、TRUNCATE操作资源负载管理的系统表pg_resource_pool。
+> - 不允许修改资源池的memory_limit和cpu_affinity属性。
+
+- 查看当前集群中所有的资源池信息。
+
+  ```sql
+  mogdb=# SELECT * FROM PG_RESOURCE_POOL;
+  ```
+
+  ```sql
+  respool_name     | mem_percent | cpu_affinity |    control_group    | active_statements | max_dop | memory_limit | parentid | io_limits | io_priority |  nodegroup   | is_foreign  | max_worker
+  ------------------+-------------+--------------+---------------------+-------------------+---------+--------------+----------+-----------+--------------+--------------+------------
+  default_pool     |         100 |           -1 | DefaultClass:Medium |                -1 |       1 | 8GB          |        0 |         0 | None        | installation | f  |
+  resource_pool_a  |          20 |           -1 | class_a             |                10 |       1 | 8GB          |        0 |         0 | None        | installation | f  |
+  resource_pool_b  |          20 |           -1 | class_b             |                10 |       1 | 8GB          |        0 |         0 | None        | installation | f  |
+  resource_pool_a1 |          20 |           -1 | class_a:workload_a1 |                10 |       1 | 8GB          |    16970 |         0 | None        | installation | f  |
+  resource_pool_a2 |          20 |           -1 | class_a:workload_a2 |                10 |       1 | 8GB          |    16970 |         0 | None        | installation | f  |
+  resource_pool_b1 |          20 |           -1 | class_b:workload_b1 |                10 |       1 | 8GB          |    16971 |         0 | None        | installation | f  |
+  resource_pool_b2 |          20 |           -1 | class_b:workload_b2 |                10 |       1 | 8GB          |    16971 |         0 | None        | installation | f  |
+  (7 rows)
+  ```
+
+- 查看某个资源池关联的控制组信息，具体内容可以参考[统计信息函数](25-statistics-information-functions)章节的gs_control_group_info(pool text)函数。
+
+  如下命令中“resource_pool_a1”为资源池名称。
+
+  ```sql
+  mogdb=# SELECT * FROM gs_control_group_info('resource_pool_a1');
+  ```
+
+  ```sql
+          name         |  class  |  workload   | type  | gid | shares | limits | rate | cpucores
+  ---------------------+---------+-------------+-------+-----+--------+--------+------+----------
+  class_a:workload_a1 | class_a | workload_a1 | DEFWD |  87 |     30 |      0 |    0 | 0-3
+  (1 row)
+  ```
+
+  **表 3** gs_control_group_info属性
+
+  | 属性     | 属性值              | 说明                                         |
+  | :------- | :------------------ | :------------------------------------------- |
+  | name     | class_a:workload_a1 | class和workload名称                          |
+  | class    | class_a             | Class控制组名称                              |
+  | workload | workload_a1         | Workload控制组名称                           |
+  | type     | DEFWD               | 控制组类型（Top、CLASS、BAKWD、DEFWD、TSWD） |
+  | gid      | 87                  | 控制组id                                     |
+  | shares   | 30                  | 占父节点CPU资源的百分比                      |
+  | limits   | 0                   | 占父节点CPU核数的百分比                      |
+  | rate     | 0                   | Timeshare中的分配比例                        |
+  | cpucores | 0-3                 | CPU核心数                                    |
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/resource-load-management/resource-management-preparation/enabling-resource-load-management.md b/product/zh/docs-mogdb/v3.0/developer-guide/resource-load-management/resource-management-preparation/enabling-resource-load-management.md
new file mode 100644
index 0000000000000000000000000000000000000000..ed97d4b19d9d8784cb219347729118fd5d0bbce0
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/resource-load-management/resource-management-preparation/enabling-resource-load-management.md
@@ -0,0 +1,74 @@
+---
+title: 启动资源负载管理功能
+summary: 启动资源负载管理功能
+author: Guo Huan
+date: 2021-10-22
+---
+
+# 启动资源负载管理功能
+
+## 背景信息
+
+使用资源负载管理功能前，需要参考本节完成参数配置。
+
+## 前提条件
+
+- 在MogDB中，如果需要对系统资源进行管理，用户需要拥有DBA权限。通过执行如下语法查询哪些用户拥有该权限：
+
+  ```sql
+  mogdb=# SELECT rolname FROM pg_roles WHERE rolsystemadmin = 't';
+   rolname
+  ---------
+   omm
+   Jack
+  (2 rows)
+  ```
+
+- 如果想要将一个用户纳入资源负载管理的范围，则此用户必须具有login权限。通过执行如下语法查询哪些用户拥有该权限：
+
+  ```sql
+  mogdb=# SELECT rolname FROM pg_roles WHERE rolcanlogin = 't';
+   rolname
+  ---------
+   omm
+  (1 row)
+  ```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+> 如果一个用户的login权限被取消，那么他的resource pool将会自动修改为default_pool。default_pool的详细介绍请参见[创建资源池](creating-a-resource-pool)中的表2。
+
+## 操作步骤
+
+DBA权限用户可以通过如下步骤启动基于资源池的资源负载管理。此处以omm用户为例进行描述。
+
+1. 以操作系统用户omm登录MogDB主节点。
+
+2. 开启Control Group功能。
+
+   ```bash
+   gs_guc reload -Z coordinator -Z datanode -N all -I all -c "enable_control_group=on"
+   ```
+
+3. 开启基于资源池的资源负载管理功能。
+
+   ```bash
+   gs_guc set -Z coordinator -Z datanode -N all -I all -c "use_workload_manager=on"
+   ```
+
+4. 开启对数据库的常驻后备线程的控制。
+
+   ```bash
+   gs_guc set -Z coordinator -Z datanode -N all -I all -c "enable_backend_control=on"
+   ```
+
+5. 开启对数据库的常驻后备线程中的autoVacuumWorker线程的控制。
+
+   ```bash
+   gs_guc set -Z coordinator -Z datanode -N all -I all -c "enable_vacuum_control=on"
+   ```
+
+6. 重启数据库使参数设置生效。
+
+   ```bash
+   gs_om -t stop && gs_om -t start
+   ```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/resource-load-management/resource-management-preparation/planning-resources.md b/product/zh/docs-mogdb/v3.0/developer-guide/resource-load-management/resource-management-preparation/planning-resources.md
new file mode 100644
index 0000000000000000000000000000000000000000..64e17468699478928b76ada9be10fded55d17944
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/resource-load-management/resource-management-preparation/planning-resources.md
@@ -0,0 +1,80 @@
+---
+title: 资源规划
+summary: 资源规划
+author: Guo Huan
+date: 2021-10-22
+---
+
+# 资源规划
+
+完成资源负载管理功能配置前，需要先根据业务模型完成租户资源的规划。业务运行一段时间后，可以根据资源的使用情况再进行配置调整。
+
+本章节我们假设某大型企业内的两个部门共用同一套集群，MogDB通过将同一个部门需要使用的系统资源集合划分为系统的一个租户，以此来实现不同部门间的资源隔离，其资源规划如表1所示。
+
+**表 1** 租户资源规划
+
+<table>
+    <tr>
+        <th>租户名称</th>
+        <th>参数名称</th>
+        <th>取值样例</th>
+    </tr>
+    <tr>
+        <td rowspan="6">租户A</td>
+        <td>子Class控制组</td>
+        <td>class_a</td>
+    </tr>
+    <tr>
+        <td>Workload控制组</td>
+        <td>- workload_a1<br/>- workload_a2</td>
+    </tr>
+    <tr>
+        <td>组资源池</td>
+        <td>resource_pool_a</td>
+    </tr>
+    <tr>
+        <td>业务资源池</td>
+        <td>- resource_pool_a1<br/>- resource_pool_a2</td>
+    </tr>
+    <tr>
+        <td>组用户</td>
+        <td>tenant_a</td>
+    </tr>
+    <tr>
+        <td>业务用户</td>
+        <td>- tenant_a1<br/>- tenant_a2</td>
+    </tr>
+</table>
+
+<table>
+    <tr>
+        <th>租户名称</th>
+        <th>参数名称</th>
+        <th>取值样例</th>
+    </tr>
+    <tr>
+        <td rowspan="6">租户B</td>
+        <td>子Class控制组</td>
+        <td>class_b</td>
+    </tr>
+    <tr>
+        <td>Workload控制组</td>
+        <td>- workload_b1<br/>- workload_b2</td>
+    </tr>
+    <tr>
+        <td>组资源池</td>
+        <td>resource_pool_b</td>
+    </tr>
+    <tr>
+        <td>业务资源池</td>
+        <td>- resource_pool_b1<br/>- resource_pool_b2</td>
+    </tr>
+    <tr>
+        <td>组用户</td>
+        <td>tenant_b</td>
+    </tr>
+    <tr>
+        <td>业务用户</td>
+        <td>- tenant_b1<br/>- tenant_b2</td>
+    </tr>
+</table>
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/resource-load-management/resource-management-preparation/setting-a-cgroup.md b/product/zh/docs-mogdb/v3.0/developer-guide/resource-load-management/resource-management-preparation/setting-a-cgroup.md
new file mode 100644
index 0000000000000000000000000000000000000000..89f42daedd53b9b3f352e52041ab60d6c702a0d6
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/resource-load-management/resource-management-preparation/setting-a-cgroup.md
@@ -0,0 +1,280 @@
+---
+title: 设置控制组
+summary: 设置控制组
+author: Guo Huan
+date: 2021-10-22
+---
+
+# 设置控制组
+
+## 背景信息
+
+MogDB资源负载管理的核心是资源池，而配置资源池首先要在环境中实现控制组Cgroups的设置。更多Cgroups的原理介绍，请查看相关操作系统的产品手册。MogDB的控制组请参考[查看控制组的信息](#查看控制组的信息)。
+
+Class控制组为数据库业务运行所在的顶层控制组，集群部署时会自动生成默认子Class控制组“DefaultClass”。DefaultClass的Medium控制组会含有系统触发的作业在运行，该控制组不允许进行资源修改，且运行在该控制组上的作业不受资源管理的控制，所以推荐创建新的子Class及其Workload控制组来设置资源比例。
+
+## 前提条件
+
+已熟悉《参考指南》中“工具参考 > 服务端工具 > [gs_cgroup](0-gs_cgroup)”章节和“服务端工具 > [gs_ssh](10-gs_ssh)”章节的使用。
+
+## 操作步骤
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 在MogDB中，需要在每个集群节点上执行控制组的创建、更新、删除操作，才能实现对整个集群资源的控制，所以下述步骤中都使用《工具参考》中“服务端工具 > gs_ssh”命令执行。
+> - 控制组的命名要求如下：
+>   - 无论是子Class控制组还是Workload控制组，都不允许在名称中包含字符”:”。
+>   - 不可以创建同名的控制组。
+
+**创建子Class控制组和Workload控制组**
+
+1. 以操作系统用户omm登录MogDB主节点。
+
+2. 创建名称为“class_a”和“class_b”的子Class控制组，CPU资源配额分别为Class的40%和20%。
+
+   ```bash
+   gs_ssh -c "gs_cgroup -c -S class_a -s 40"
+   ```
+
+   ```bash
+   gs_ssh -c "gs_cgroup -c -S class_b -s 20"
+   ```
+
+3. 创建子Class控制组“class_a”下名称为“workload_a1”和“workload_a2”的Workload控制组，CPU资源配额分别为“class_a”控制组的20%和60%。
+
+   ```bash
+   gs_ssh -c "gs_cgroup -c -S class_a -G workload_a1 -g 20 "
+   ```
+
+   ```bash
+   gs_ssh -c "gs_cgroup -c -S class_a -G workload_a2 -g 60 "
+   ```
+
+4. 创建子Class控制组“class_b”下名称为“workload_b1”和“workload_b2”的Workload控制组，CPU资源配额分别为“class_b”控制组的50%和40%。
+
+   ```bash
+   gs_ssh -c "gs_cgroup -c -S class_b -G workload_b1 -g 50 "
+   ```
+
+   ```bash
+   gs_ssh -c "gs_cgroup -c -S class_b -G workload_b2 -g 40 "
+   ```
+
+**更新控制组的资源配额**
+
+1. 更新“class_a”控制组的CPU资源配额为30%。
+
+   ```bash
+   gs_ssh -c "gs_cgroup -u -S class_a -s 30"
+   ```
+
+2. 更新“class_a”下的“workload_a1”的CPU资源配额为“class_a”的30%。
+
+   ```bash
+   gs_ssh -c "gs_cgroup -u -S class_a -G workload_a1 -g 30"
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 调整后的Workload控制组“workload_a1”占有的CPU资源不应大于其对应的子Class控制组“class_a”。并且，此名称不能是Timeshare Cgroup的默认名称，如“Low”、“Medium”、“High”或“Rush”。
+
+**删除控制组**
+
+1. 删除控制组“class_a”。
+
+   ```bash
+   gs_ssh -c "gs_cgroup -d  -S class_a"
+   ```
+
+   以上操作可以删除控制组“class_a”。
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** root用户或者具有root访问权限的用户指定“-d” 和“-U username”删除普通用户“username”可访问的默认Cgroups。普通用户指定“-d”和“-S classname”可以删除已有的Class Cgroups。
+
+## 查看控制组的信息
+
+1. 查看配置文件中控制组信息。
+
+   ```bash
+   gs_cgroup -p
+   ```
+
+   控制组配置信息
+
+   ```bash
+   gs_cgroup -p
+
+   Top Group information is listed:
+   GID:   0 Type: Top    Percent(%): 1000( 50) Name: Root                  Cores: 0-47
+   GID:   1 Type: Top    Percent(%):  833( 83) Name: Gaussdb:omm           Cores: 0-20
+   GID:   2 Type: Top    Percent(%):  333( 40) Name: Backend               Cores: 0-20
+   GID:   3 Type: Top    Percent(%):  499( 60) Name: Class                 Cores: 0-20
+
+   Backend Group information is listed:
+   GID:   4 Type: BAKWD  Name: DefaultBackend   TopGID:   2 Percent(%): 266(80) Cores: 0-20
+   GID:   5 Type: BAKWD  Name: Vacuum           TopGID:   2 Percent(%):  66(20) Cores: 0-20
+
+   Class Group information is listed:
+   GID:  20 Type: CLASS  Name: DefaultClass     TopGID:   3 Percent(%): 166(20) MaxLevel: 1 RemPCT: 100 Cores: 0-20
+   GID:  21 Type: CLASS  Name: class1           TopGID:   3 Percent(%): 332(40) MaxLevel: 2 RemPCT:  70 Cores: 0-20
+
+   Workload Group information is listed:
+   GID:  86 Type: DEFWD  Name: grp1:2           ClsGID:  21 Percent(%):  99(30) WDLevel:  2 Quota(%): 30 Cores: 0-5
+
+   Timeshare Group information is listed:
+   GID: 724 Type: TSWD   Name: Low              Rate: 1
+   GID: 725 Type: TSWD   Name: Medium           Rate: 2
+   GID: 726 Type: TSWD   Name: High             Rate: 4
+   GID: 727 Type: TSWD   Name: Rush             Rate: 8
+
+   Group Exception information is listed:
+   GID:  20 Type: EXCEPTION Class: DefaultClass
+   PENALTY: QualificationTime=1800 CPUSkewPercent=30
+
+   GID:  21 Type: EXCEPTION Class: class1
+   PENALTY: AllCpuTime=100 QualificationTime=2400 CPUSkewPercent=90
+
+   GID:  86 Type: EXCEPTION Group: class1:grp1:2
+   ABORT: BlockTime=1200 ElapsedTime=2400
+   ```
+
+   上述示例查看到的控制组配置信息如表1所示。
+
+   **表 1** 控制组配置信息
+
+   <table>
+       <tr>
+           <th>GID</th>
+           <th>类型</th>
+           <th>名称</th>
+           <th>Percent（%）信息</th>
+           <th>特定信息</th>
+       </tr>
+       <tr>
+           <td>0</td>
+           <td rowspan=4>Top控制组</td>
+           <td>Root</td>
+           <td>1000代表总的系统资源为1000份。<br/>括号中的50代表IO资源的50%。<br/>MogDB不通过控制组对IO资源做控制，因此下面其他控制组信息中仅涉及CPU配额情况。</td>
+           <td>-</td>
+       </tr>
+       <tr>
+           <td>1</td>
+           <td>Gaussdb:omm</td>
+           <td>系统中只运行一套数据库程序，Gaussdb:omm控制组默认配额为833，数据库程序和非数据库程序的比值为（833:167=5:1）。</td>
+           <td>-</td>
+       </tr>
+       <tr>
+           <td>2</td>
+           <td>Backend</td>
+           <td rowspan=2>Backend和Class括号中的40和60，代表Backend占用Gaussdb:dbuser控制组40%的资源，Class占用Gaussdb:dbuser控制组60%的资源。</td>
+           <td>-</td>
+       </tr>
+       <tr>
+           <td>3</td>
+           <td>Class</td>
+           <td>-</td>
+       </tr>
+       <tr>
+           <td>4</td>
+           <td rowspan=2>Backend控制组</td>
+           <td>DefaultBackend</td>
+           <td rowspan=2>括号中的80和20代表DefaultBackend和Vacuum占用Backend控制组80%和20%的资源。</td>
+           <td rowspan=2>TopGID：代表Top类型控制组中Backend组的GID，即2。</td>
+       </tr>
+       <tr>
+           <td>5</td>
+           <td>Vacuum</td>
+       </tr>
+       <tr>
+           <td>20</td>
+           <td rowspan=2>Class控制组</td>
+           <td>DefaultClass</td>
+           <td rowspan=2>DefaultClass和class1的20和40代表占Class控制组20%和40%的资源。因为当前只有两个Class组，所有它们按照20:40的比例分配Class控制组499的系统配额，则分别为166和332。</td>
+           <td rowspan=2>- TopGID：代表DefaultClass和class1所属的上层控制（Top控制组中的Class组）的GID，即3。<br/>-
+   MaxLevel：Class组当前含有的Workload组的最大层次，DefaultClass没有Workload Cgroup，其数值为1。<br/>-
+   RemPCT:代表Class组分配Workload组后剩余的资源百分比。如class1中剩余的百分比为70。</td>
+       </tr>
+       <tr>
+           <td>21</td>
+           <td>class1</td>
+       </tr>
+       <tr>
+           <td>86</td>
+           <td>Workload控制组</td>
+           <td>grp1:2<br/>（该名称由Workload Cgroup Name和其在class中的层级组成，它是class1的第一个Workload组，层级为2，每个Class组最多10层Workload Cgroup。）</td>
+           <td>根据设置，其占class1的百分比为30，则为332*30%=99。</td>
+           <td>- ClsGID：代表Workload控制组所属的上层控制组（class1控制组）的GID。<br/>- WDLevel：代表当前Workload Cgroup在对应的Class组所在的层次。</td>
+       </tr>
+       <tr>
+           <td>724</td>
+           <td rowspan=4>Timeshare控制组</td>
+           <td>Low</td>
+           <td>-</td>
+           <td rowspan=4>Rate：代表Timeshare中的分配比例，Low最少为1，Rush最高为8。这四个Timeshare组的资源配比为Rush:High:Medium:Low=8:4:2:1</td>
+       </tr>
+       <tr>
+           <td>725</td>
+           <td>Medium</td>
+           <td>-</td>
+       </tr>
+       <tr>
+           <td>726</td>
+           <td>High</td>
+           <td>-</td>
+       </tr>
+       <tr>
+           <td>727</td>
+           <td>Rush</td>
+           <td>-</td>
+       </tr>
+   </table>
+
+2. 查看操作系统中树形结构的控制组信息。
+
+   执行如下命令可以查询控制组树形结构信息。
+
+   ```bash
+   gs_cgroup -P
+   ```
+
+   返回信息如下，其中shares代表操作系统中CPU资源的动态资源配额“cpu.shares”的数值，cpus代表操作系统中CPUSET资源的动态资源限额“cpuset.cpus”的数值，指的是该控制组能够使用的核数范围。
+
+   ```
+   Mount Information:
+   cpu:/dev/cgroup/cpu
+   blkio:/dev/cgroup/blkio
+   cpuset:/dev/cgroup/cpuset
+   cpuacct:/dev/cgroup/cpuacct
+
+   Group Tree Information:
+   - Gaussdb:wangrui (shares: 5120, cpus: 0-20, weight: 1000)
+           - Backend (shares: 4096, cpus: 0-20, weight: 400)
+                   - Vacuum (shares: 2048, cpus: 0-20, weight: 200)
+                   - DefaultBackend (shares: 8192, cpus: 0-20, weight: 800)
+           - Class (shares: 6144, cpus: 0-20, weight: 600)
+                   - class1 (shares: 4096, cpus: 0-20, weight: 400)
+                           - RemainWD:1 (shares: 1000, cpus: 0-20, weight: 100)
+                                   - RemainWD:2 (shares: 7000, cpus: 0-20, weight: 700)
+                                           - Timeshare (shares: 1024, cpus: 0-20, weight: 500)
+                                                   - Rush (shares: 8192, cpus: 0-20, weight: 800)
+                                                   - High (shares: 4096, cpus: 0-20, weight: 400)
+                                                   - Medium (shares: 2048, cpus: 0-20, weight: 200)
+                                                   - Low (shares: 1024, cpus: 0-20, weight: 100)
+                                   - grp1:2 (shares: 3000, cpus: 0-5, weight: 300)
+                           - TopWD:1 (shares: 9000, cpus: 0-20, weight: 900)
+                   - DefaultClass (shares: 2048, cpus: 0-20, weight: 200)
+                           - RemainWD:1 (shares: 1000, cpus: 0-20, weight: 100)
+                                   - Timeshare (shares: 1024, cpus: 0-20, weight: 500)
+                                           - Rush (shares: 8192, cpus: 0-20, weight: 800)
+                                           - High (shares: 4096, cpus: 0-20, weight: 400)
+                                           - Medium (shares: 2048, cpus: 0-20, weight: 200)
+                                           - Low (shares: 1024, cpus: 0-20, weight: 100)
+                           - TopWD:1 (shares: 9000, cpus: 0-20, weight: 900)
+   ```
+
+3. 通过系统视图获取控制组配置信息。
+
+   1. [使用gsql连接数据库](using-the-gsql-client-for-connection)。
+
+   2. 获取系统中所有控制组的配置信息。
+
+      ```sql
+      mogdb=# SELECT * FROM gs_all_control_group_info;
+      ```
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/scheduled-jobs/pkg-service.md b/product/zh/docs-mogdb/v3.0/developer-guide/scheduled-jobs/pkg-service.md
new file mode 100644
index 0000000000000000000000000000000000000000..1e9d32c16fba801e6029d7db903eeb5ca1937e79
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/scheduled-jobs/pkg-service.md
@@ -0,0 +1,366 @@
+---
+title: PKG_SERVICE接口
+summary: PKG_SERVICE接口
+author: Guo Huan
+date: 2022-03-18
+---
+
+# PKG_SERVICE接口
+
+MogDB 2.1版本提供了以下PKG_SERVICE接口来实现定时任务管理。
+
+<br/>
+
+表1 接口描述
+
+| 接口名称               | 描述                                                       |
+| ---------------------- | ---------------------------------------------------------- |
+| PKG_SERVICE.JOB_CANCEL | 通过任务ID来删除定时任务。                                 |
+| PKG_SERVICE.JOB_FINISH | 禁用或者启用定时任务。                                     |
+| PKG_SERVICE.JOB_SUBMIT | 提交一个定时任务。作业号由系统自动生成或由用户指定。       |
+| PKG_SERVICE.JOB_UPDATE | 修改定时任务的属性，包括任务内容、下次执行时间、执行间隔。 |
+
+<br/>
+
+## 接口定义和使用示例
+
+- PKG_SERVICE.JOB_CANCEL
+
+  存储过程CANCEL删除指定的定时任务。
+
+  PKG_SERVICE.JOB_CANCEL函数原型为：
+
+  ```
+  PKG_SERVICE.JOB_CANCEL( job IN INTEGER);
+  ```
+
+  表2 PKG_SERVICE.JOB_CANCEL接口参数说明
+
+  | 参数 | 类型    | 入参/出参 | 是否可以为空 | 描述           |
+  | ---- | ------- | --------- | ------------ | -------------- |
+  | id   | integer | IN        | 否           | 指定的作业号。 |
+
+  示例：
+
+  ```sql
+  CALL PKG_SERVICE.JOB_CANCEL(101);
+  ```
+
+- PKG_SERVICE.JOB_FINISH
+
+  存储过程FINISH禁用或者启用定时任务。
+
+  PKG_SERVICE.JOB_FINISH函数原型为：
+
+  ```
+  PKG_SERVICE.JOB_FINISH(
+  id IN INTEGER,
+  broken IN BOOLEAN, 
+  next_time IN TIMESTAMP DEFAULT sysdate);
+  ```
+
+  表3 PKG_SERVICE.JOB_FINISH接口参数说明
+  
+  | 参数      | 类型      | 入参/出参 | 是否可以为空 | 描述                                                         |
+  | --------- | --------- | --------- | ------------ | ------------------------------------------------------------ |
+  | id        | integer   | IN        | 否           | 指定的作业号。                                               |
+  | broken    | Boolean   | IN        | 否           | 状态标志位，true代表禁用，false代表启用。根据true或false值更新当前job；如果为空值，则不改变原有job的状态。 |
+  | next_time | timestamp | IN        | 是           | 下次运行时间，默认为当前系统时间。如果参数broken状态为true，则更新该参数为'4000-1-1'；如果参数broken状态为false，且如果参数next_time不为空值，则更新指定job的next_time值，如果next_time为空值，则不更新next_time值。该参数可以省略，为默认值。 |
+
+- PKG_SERVICE.JOB_SUBMIT
+
+  存储过程JOB_SUBMIT提交一个系统提供的定时任务。
+
+  PKG_SERVICE.JOB_SUBMIT函数原型为：
+
+  ```
+  PKG_SERVICE.JOB_SUBMIT(
+  id IN BIGINT DEFAULT, 
+  content IN TEXT, 
+  next_date IN TIMESTAMP DEFAULT sysdate, 
+  interval_time IN TEXT DEFAULT 'null', 
+  job OUT INTEGER);
+  ```
+  
+  > 说明：当创建一个定时任务（JOB）时，系统默认将当前数据库和用户名与当前创建的定时任务绑定起来。该接口函数可以通过call或select调用，如果通过select调用，可以不填写出参。如果在存储过程中，则需要通过perform调用该接口函数。如果提交的sql语句任务使用到非public的schema，应该指定表或者函数的schema，或者在sql语句前添加`set current_schema = xxx;`语句。
+  
+  表4 PKG_SERVICE.JOB_SUBMIT接口参数说明
+  
+  | 参数          | 类型      | 入参/出参 | 是否可以为空 | 描述                                                         |
+  | ------------- | --------- | --------- | ------------ | ------------------------------------------------------------ |
+  | id            | bigint    | IN        | 否           | 作业号。如果传入id为NULL，则内部会生成作业ID。               |
+  | context       | text      | IN        | 否           | 要执行的SQL语句。支持一个或多个‘DML’，‘匿名块’，‘调用存储过程的语句’或3种混合的场景。 |
+  | next_time     | timestamp | IN        | 否           | 下次作业运行时间。默认值为当前系统时间（sysdate）。如果是过去时间，在提交作业时表示立即执行。 |
+  | interval_time | text      | IN        | 是           | 用来计算下次作业运行时间的时间表达式，可以是interval表达式，也可以是sysdate加上一个numeric值（例如：sysdate+1.0/24）。如果为空值或字符串"null"表示只执行一次，执行后JOB状态STATUS变成'd' 不再执行。 |
+  | job           | integer   | OUT       | 否           | 作业号。范围为1～32767。当使用select调用pkg_service.job_submit时，该参数可以省略。 |
+  
+  示例：
+  
+  ```sql
+  SELECT PKG_SERVICE.JOB_SUBMIT(NULL, 'call pro_xxx();', to_date('20180101','yyyymmdd'),'sysdate+1');
+  
+  SELECT PKG_SERVICE.JOB_SUBMIT(NULL, 'call pro_xxx();', to_date('20180101','yyyymmdd'),'sysdate+1.0/24');
+  
+  CALL PKG_SERVICE.JOB_SUBMIT(NULL, 'INSERT INTO T_JOB  VALUES(1);  call pro_1(); call pro_2();', add_months(to_date('201701','yyyymm'),1), 'date_trunc(''day'',SYSDATE) + 1 +(8*60+30.0)/(24*60)' ,:jobid);
+  
+  SELECT PKG_SERVICE.JOB_SUBMIT (101, 'insert_msg_statistic1;', sysdate, 'sysdate+3.0/24');
+  ```
+
+- PKG_SERVICE.JOB_UPDATE
+
+  存储过程UPDATE修改定时任务的属性，包括任务内容、下次执行时间、执行间隔。
+
+  PKG_SERVICE.JOB_UPDATE函数原型为：
+
+  ```
+  PKG_SERVICE.JOB_UPDATE(
+  id IN BIGINT, 
+  next_time IN TIMESTAMP, 
+  interval_time IN TEXT, 
+  content IN TEXT);
+  ```
+
+  表5 PKG_SERVICE.JOB_UPDATE接口参数说明
+
+  | 参数          | 类型      | 入参/出参 | 是否可以为空 | 描述                                                         |
+  | ------------- | --------- | --------- | ------------ | ------------------------------------------------------------ |
+  | id            | integer   | IN        | 否           | 指定的作业号。                                               |
+  | next_time     | timestamp | IN        | 是           | 下次运行时间。如果该参数为空值，则不更新指定job的next_time值，否则更新指定job的next_time值。 |
+  | interval_time | text      | IN        | 是           | 用来计算下次作业运行时间的时间表达式。如果该参数为空值，则不更新指定job的interval_time值；如果该参数不为空值，会校验interval_time是否为有效的时间类型或interval类型，则更新指定job的interval_time值。如果为字符串"null"表示只执行一次，执行后JOB状态STATUS变成'd' 不再执行。 |
+  | content       | text      | IN        | 是           | 执行的存储过程名或者sql语句块。如果该参数为空值，则不更新指定job的content值，否则更新指定job的content值。 |
+
+  示例：
+
+  ```sql
+  CALL PKG_SERVICE.JOB_UPDATE(101, 'call userproc();', sysdate, 'sysdate + 1.0/1440');
+  
+  CALL PKG_SERVICE.JOB_UPDATE(101, 'insert into tbl_a values(sysdate);', sysdate, 'sysdate + 1.0/1440');
+  ```
+
+<br/>
+
+## 定时任务（job）使用示例
+
+本示例介绍如何通过上述接口实现定时任务（job）管理。
+
+- 创建测试表
+
+  ```
+  mogdb=# create table t_job (value TIMESTAMP);
+  CREATE TABLE
+  
+  mogdb=# insert into t_job values(sysdate);
+  INSERT 0 1
+  
+  mogdb=# select * from t_job;
+  +---------------------+
+  | value               |
+  |---------------------|
+  | 2021-10-09 04:36:20 |
+  +---------------------+
+  SELECT 1
+  ```
+
+- 创建任务，每一分钟插入一条记录
+
+  ```
+  mogdb=# select pkg_service.job_submit(null, 'insert into t_job values(sysdate);',sysdate,'sysdate + 1/1440');
+  +--------------+
+  | job_submit   |
+  |--------------|
+  | 15566        |
+  +--------------+
+  SELECT 1
+  ```
+
+- 检查JOB运行结果
+
+  ```
+  mogdb=# select * from t_job;
+  +---------------------+
+  | value               |
+  |---------------------|
+  | 2021-10-09 04:36:20 |
+  | 2021-10-09 04:40:54 |
+  | 2021-10-09 04:41:54 |
+  | 2021-10-09 04:42:54 |
+  +---------------------+
+  SELECT 4
+  ```
+
+- 从系统视图中检查JOB运行情况
+
+  ```
+  mogdb=# select job_id,dbname,start_date,next_run_date,interval,failure_count from pg_job;
+  +----------+----------+----------------------------+---------------------+------------------+-----------------+
+  | job_id   | dbname   | start_date                 | next_run_date       | interval         | failure_count   |
+  |----------+----------+----------------------------+---------------------+------------------+-----------------|
+  | 15566    | postgres | 2021-10-09 04:40:54.072363 | 2021-10-09 04:56:54 | sysdate + 1/1440 | 0               |
+  +----------+----------+----------------------------+---------------------+------------------+-----------------+
+  SELECT 1
+  Time: 0.089s
+  mogdb=# select * from pg_catalog.pg_job_proc pjp where job_id=15566;
+  +----------+------------------------------------+
+  | job_id   | what                               |
+  |----------+------------------------------------|
+  | 15566    | insert into t_job values(sysdate); |
+  +----------+------------------------------------+
+  SELECT 1
+  Time: 0.089s
+  ```
+
+- 修改为2分钟执行一次
+
+  ```
+  mogdb=# select pkg_service.job_update(15566,null,'sysdate + 2/1440',null);
+  +--------------+
+  | job_update   |
+  |--------------|
+  |              |
+  +--------------+
+  SELECT 1
+  ```
+
+- 检查修改情况和运行结果
+
+  ```
+  mogdb=# select job_id,interval from pg_job where job_id=15566;
+  +----------+------------------+
+  | job_id   | interval         |
+  |----------+------------------|
+  | 15566    | sysdate + 2/1440 |
+  +----------+------------------+
+  SELECT 1
+  mogdb=# select * from t_job;
+  +---------------------+
+  | value               |
+  |---------------------|
+  | 2021-10-09 04:36:20 |
+  | 2021-10-09 04:40:54 |
+  | 2021-10-09 04:41:54 |
+  | 2021-10-09 04:42:54 |
+  | 2021-10-09 04:43:54 |
+  | 2021-10-09 04:44:54 |
+  | 2021-10-09 04:45:54 |
+  | 2021-10-09 04:46:54 |
+  | 2021-10-09 04:47:54 |
+  | 2021-10-09 04:48:54 |
+  | 2021-10-09 04:49:54 |
+  | 2021-10-09 04:50:54 |
+  | 2021-10-09 04:51:54 |
+  | 2021-10-09 04:52:54 |
+  | 2021-10-09 04:53:54 |
+  | 2021-10-09 04:54:54 |
+  | 2021-10-09 04:55:54 |
+  | 2021-10-09 04:56:54 |
+  | 2021-10-09 04:57:54 |
+  | 2021-10-09 04:58:54 |
+  | 2021-10-09 04:59:54 |
+  | 2021-10-09 05:00:55 |
+  | 2021-10-09 05:01:56 | <---
+  | 2021-10-09 05:03:57 | <--- 开始间隔2分钟
+  +---------------------+
+  SELECT 24
+  Time: 0.088s
+  mogdb=# select job_id,interval,next_run_date from pg_job where job_id=15566;
+  +----------+------------------+---------------------+
+  | job_id   | interval         | next_run_date       |
+  |----------+------------------+---------------------|
+  | 15566    | sysdate + 2/1440 | 2021-10-09 05:05:57 |
+  +----------+------------------+---------------------+
+  SELECT 1
+  Time: 0.078s>
+  ```
+
+- 禁用和启用任务
+
+  禁用和启用都是同样的函数pkg_service.job_finish，传入不同的参数表示是禁用还是启用。
+
+  ```
+  mogdb=# select pkg_service.job_finish(15566,true,null);
+  +--------------+
+  | job_finish   |
+  |--------------|
+  |              |
+  +--------------+
+  SELECT 1
+  Time: 0.089s
+  mogdb=# select job_id,next_run_date,job_status from pg_job where job_id=15566;
+  +----------+---------------------+--------------+
+  | job_id   | next_run_date       | job_status   |
+  |----------+---------------------+--------------|
+  | 15566    | 4000-01-01 00:00:00 | d            |
+  +----------+---------------------+--------------+
+  SELECT 1
+  Time: 0.075s
+  mogdb=# select pkg_service.job_finish(15566,false,null);
+  +--------------+
+  | job_finish   |
+  |--------------|
+  |              |
+  +--------------+
+  SELECT 1
+  Time: 0.091s
+  mogdb=# select job_id,next_run_date,job_status from pg_job where job_id=15566;
+  +----------+---------------------+--------------+
+  | job_id   | next_run_date       | job_status   |
+  |----------+---------------------+--------------|
+  | 15566    | 4000-01-01 00:00:00 | s            |
+  +----------+---------------------+--------------+
+  SELECT 1
+  Time: 0.080s
+  ```
+
+  可以看到如果重新启用任务的时候，没有指定下次运行时间，那么下次运行时间会始终保持在4000年，意味着仍然不会启动，所以如果禁用任务之后再重新启动，需要手动显式指定下次运行时间。
+
+  ```
+  mogdb=# select pkg_service.job_finish(15566,false,sysdate);
+  +--------------+
+  | job_finish   |
+  |--------------|
+  |              |
+  +--------------+
+  SELECT 1
+  Time: 0.088s
+  mogdb=# select job_id,next_run_date,job_status from pg_job where job_id=15566;
+  +----------+---------------------+--------------+
+  | job_id   | next_run_date       | job_status   |
+  |----------+---------------------+--------------|
+  | 15566    | 2021-10-09 05:16:22 | s            |
+  +----------+---------------------+--------------+
+  SELECT 1
+  Time: 0.086s
+  ```
+
+- 删除任务
+
+  ```
+  mogdb=# select pkg_service.job_cancel(15566);
+  +--------------+
+  | job_cancel   |
+  |--------------|
+  |              |
+  +--------------+
+  SELECT 1
+  Time: 0.082s
+  mogdb=# select job_id,next_run_date,job_status from pg_job where job_id=15566;
+  +----------+-----------------+--------------+
+  | job_id   | next_run_date   | job_status   |
+  |----------+-----------------+--------------|
+  +----------+-----------------+--------------+
+  SELECT 0
+  Time: 0.086s
+  mogdb=# select * from pg_catalog.pg_job_proc pjp where job_id=15566;
+  +----------+--------+
+  | job_id   | what   |
+  |----------+--------|
+  +----------+--------+
+  SELECT 0
+  Time: 0.087s
+  ```
+
+<br/>
+
+## 相关页面
+
+[PG_JOB](PG_JOB)、[定时任务](31-scheduled-task)
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/developer-guide/user-defined-functions.md b/product/zh/docs-mogdb/v3.0/developer-guide/user-defined-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..319dc7522f701394139ece8ef8eae85faefd4647
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/developer-guide/user-defined-functions.md
@@ -0,0 +1,16 @@
+---
+title: 用户自定义函数
+summary: 用户自定义函数
+author: Guo Huan
+date: 2021-03-04
+---
+
+# 用户自定义函数
+
+在MogDB数据库中，为了实现特定的功能，用户可以自定义函数，就像其它大多数语言一样，除了系统的库函数，程序员还会编写很多自定义的函数。
+
+MogDB用户自定义函数是存储在数据库服务器上并可以使用SQL界面调用的一组SQL和过程语句（声明、分配、循环、控制流程等）的组合，在表现形式上，用户自定义函数和存储过程是非常相似的，只是存储过程无返回值，而函数有返回值。
+
+用户自定义函数的创建及调用办法请参考[CREATE FUNCTION](48-CREATE-FUNCTION)。
+
+[存储过程](1-1-stored-procedure)一节所提到的存储过程编写方法与本章节用户自定义函数的编写方法相通。具体介绍请参看[PL/pgSQL-SQL过程语言](1-1-plpgsql-overview)章节，除非特别声明，否则其中内容通用于存储过程和用户自定义函数。
diff --git a/product/zh/docs-mogdb/v3.0/faqs/application-development-faqs.md b/product/zh/docs-mogdb/v3.0/faqs/application-development-faqs.md
new file mode 100644
index 0000000000000000000000000000000000000000..0e55d1a854cc7000604d06245c2dc82a758e6ff0
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/faqs/application-development-faqs.md
@@ -0,0 +1,8 @@
+---
+title: 应用开发FAQs
+summary: 应用开发FAQs
+author: Guo Huan
+date: 2021-09-26
+---
+
+正在编写中……
diff --git a/product/zh/docs-mogdb/v3.0/faqs/deployment-and-maintenance-faqs.md b/product/zh/docs-mogdb/v3.0/faqs/deployment-and-maintenance-faqs.md
new file mode 100644
index 0000000000000000000000000000000000000000..c5b699c3e4cdc949cc2d6ecffeb30679fdb9a34d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/faqs/deployment-and-maintenance-faqs.md
@@ -0,0 +1,332 @@
+---
+title: 部署运维FAQs
+summary: 部署运维FAQs
+author: Guo Huan
+date: 2021-09-26
+---
+
+# 部署运维FAQs
+
+<br/>
+
+## 初始化环境FAQs
+
+**Q1: `clusterconfig.xml`示例配置文件需要修改哪些参数？**
+
+需要修改机器名和IP地址。
+
+```xml
+<?xml version="1.0" encoding="UTF-8"?>
+<ROOT>
+    <!-- MogDB整体信息 -->
+    <CLUSTER>
+        <PARAM name="clusterName" value="dbCluster" />
+        <PARAM name="nodeNames" value="mogdb-kernel-0002" />
+        <PARAM name="backIp1s" value="172.16.0.245"/>
+        <PARAM name="gaussdbAppPath" value="/opt/mogdb/app" />
+        <PARAM name="gaussdbLogPath" value="/opt/mogdb/mogdb_log/omm" />
+        <PARAM name="gaussdbToolPath" value="/opt/mogdb/tool" />
+        <PARAM name="corePath" value="/opt/mogdb/corefile"/>
+        <PARAM name="clusterType" value="single-inst"/>
+    </CLUSTER>
+
+<!-- 每台服务器上的节点部署信息 -->
+    <DEVICELIST>
+        <!-- mogdb-kernel-0002上的节点部署信息 -->
+        <DEVICE sn="1000001">
+            <PARAM name="name" value="mogdb-kernel-0002"/>
+            <PARAM name="azName" value="AZ1"/>
+            <PARAM name="azPriority" value="1"/>
+            <!-- 如果服务器只有一个网卡可用，将backIP1和sshIP1配置成同一个IP -->
+            <PARAM name="backIp1" value="172.16.0.245"/>
+            <PARAM name="sshIp1" value="172.16.0.245"/>
+
+            <!--dbnode-->
+            <PARAM name="dataNum" value="1"/>
+            <PARAM name="dataPortBase" value="26000"/>
+            <PARAM name="dataNode1" value="/mogdb/data/db1"/>
+        </DEVICE>
+    </DEVICELIST>
+</ROOT>
+```
+
+<br/>
+
+## 初始化脚本FAQs
+
+**Q2: 当提示配置文件参数值与系统环境变量值不相符怎么办？**
+
+```bash
+Failed to check the preinstall repeat condition.gaussdbToolPath [/opt/enmo/wisery] is not same with environment [/opt/mogdb/tool]
+```
+
+将`clusterconfig.xml`文件里`gaussdbToolPath`的值改为`/opt/mogdb/tool`。
+
+> 说明：
+>
+> - 出现此类问题，主要是因为系统之前安装过MogDB，环境可能未清理干净，所以会产生配置文件参数值与系统环境变量值不相符的情况，将导致执行失败。将`clusterconfig.xml`配置文件中报错参数的值改为和环境变量文件参数值相同即可。
+> - 在`omm`用户下执行`vi ~/.bashrc`可查看环境变量。
+
+**Q3: 当提示无权限执行该命令，怎么办？**
+
+```bash
+Fixing server package owner.
+[GAUSS-51400] : Failed to execute the command: su - omm -c 'cd '/opt/software/mogdb/''. Error:
+-bash: line 0: cd: /opt/software/mogdb/: Permission denied
+```
+
+执行`chmod 755 -R /opt/software`为该目录赋予权限后，再重新执行脚本初始化命令。
+
+**Q4: 当符号链接创建失败怎么办？**
+
+```bash
+In:failed to create symbolic link 'usr/bin/python3': File exists
+```
+
+将`usr/bin/`目录下的`python3`删掉，重新执行`In`命令。
+
+**Q5: 当提示主机名不在集群中时怎么办？**
+
+```bash
+GAUSS-51619: "The host name [host-172-16-0-195] is not in the cluster."
+```
+
+这是因为机器实际的名称是`host-172-16-0-195`，而不是`mogdb-kernel-0006`，所以需要将`clusterconfig.xml`里的节点名称改为`host-172-16-0-195`。
+
+**Q6: 当出现如下报错时，怎么办？**
+
+```bash
+[GAUSS-50202]:The /opt/mogdb must be empty. Or user [omm] has write permission to directory /opt/mogdb. Because it will create symbolic link [/opt/mogdb/app] to install path [/opt/mogdb/app_e0e9f58d] in gs_install process with this user.
+```
+
+在`omm`用户下，执行`vi ~/.bashrc`，将环境变量清空，重新执行初始化脚本即可成功。
+
+**Q7: 当出现如下有关依赖包的报错时，怎么办？**
+
+```
+/opt/software/mogdb/bin/mogdb: error while loading shared libraries: libnsl.so.1: cannot open shared object file: No such file or directory
+no data was returned by command ""/opt/software/mogdb/bin/mogdb" -V"
+The program "mogdb" is needed by gs_initdb but was not found in the
+same directory as "/opt/software/mogdb/bin/gs_initdb".
+Check your installation.
+```
+
+重新安装依赖包libnsl*即可。
+
+<br/>
+
+## 安装FAQs
+
+**Q8: 当提示集群已安装怎么办？**
+
+```bash
+[GAUSS-51400] : Failed to execute the command: source /home/omm/.bashrc;python3 '/opt/mogdb/tool/script/local/CheckInstall.py' -U omm:dbgrp -R /opt/mogdb/app -l /opt/mogdb/mogdb_log/omm/omm/om/gs_local.log -X /opt/software/mogdb/clusterconfig.xml.Error:
+Checking old installation.
+[GAUSS-51806] : The cluster has been installed.
+```
+
+执行`vi ~/.bashrc`查看环境变量，将`GAUSS_ENV=2`改为`GAUSS_ENV=1`，重新执行安装命令即可。
+
+**Q9: 当执行安装命令报如下错误怎么办？**
+
+```bash
+[GAUSS-51400] : Failed to execute the command: source /home/omm/.bashrc;python3 '/opt/mogdb/tool/script/local/CheckInstall.py' -U omm:dbgrp -R /opt/mogdb/app -l /opt/mogdb/mogdb_log/omm/omm/om/gs_local.log -X /opt/software/mogdb/clusterconfig.xml.Error:
+Checking old installation.
+Successfully checked old installation.
+Checking SHA256.
+Successfully checked SHA256.
+Checking kernel parameters.
+Successfully checked kernel parameters.
+Checking directory.
+[GAUSS-50202] : The /opt/mogdb/app_b75b585a must be empty.
+```
+
+在`root`用户下，进入`/opt/mogdb/app_b75b585a`目录，执行`rm -rf *`将目录下所有文件删除，重新执行安装命令即可。
+
+**Q10: 当错误提示socket被占用怎么办？**
+
+```bash
+[GAUSS-50200] : The socket file already exists. Port:26000.
+```
+
+将`clusterconfig.xml`文件里的`dataPortBase`值改为一个可用的端口即可。
+
+**Q11: 测试MogDB安装需要开放哪些端口？**
+
+需要开放端口26000、26001、26003、26004和26005。
+
+<br/>
+
+## 部署后FAQs
+
+**gs_om -t start启动数据库失败："在标准安装后，通过hostnamectl set修改主机名"**
+
+**适用于：**
+
+* MogDB 1.1.0
+
+* MogDB 2.0.0
+
+* MogDB 2.0.1
+
+* MogDB 2.1.0
+
+* MogDB 2.1.1
+
+* MogDB 单机数据库
+
+本文档中的信息适用于x86平台。
+
+**症状**：
+
+在标准安装结束后（单机），通过`hostnamectl set`修改主机名，执行`gs_om -t start`命令数据库启动失败。
+
+例如：
+
+1. 在`root`用户下通过`hostnamectl set`将主机名`mogdb-kernel-0005`修改为`www.mogdb.com`。
+
+   ```bash
+   [root@mogdb-kernel-0005 ~]# hostnamectl
+      Static hostname: mogdb-kernel-0005
+            Icon name: computer-vm
+              Chassis: vm
+           Machine ID: de03a5f3bf5a4b7e9df939c9dc5b428d
+              Boot ID: 828bfbe948ed4de7aff2a059103a0eaa
+       Virtualization: kvm
+     Operating System: CentOS Linux 7 (Core)
+          CPE OS Name: cpe:/o:centos:centos:7
+               Kernel: Linux 3.10.0-1160.15.2.el7.x86_64
+         Architecture: x86-64
+   [root@mogdb-kernel-0005 ~]# id
+   uid=0(root) gid=0(root) groups=0(root)
+   [root@mogdb-kernel-0005 ~]# hostname
+   mogdb-kernel-0005
+   [root@mogdb-kernel-0005 ~]# hostnamectl set-hostname www.mogdb.com
+   ```
+
+2. 在任意用户下执行如下命令查看是否主机名修改成功。
+
+   ```bash
+   [root@mogdb-kernel-0005 ~]# hostname
+   www.mogdb.com
+   ```
+
+3. 在`omm`用户下执行如下命令停止数据库。
+
+   ```bash
+   [root@mogdb-kernel-0005 ~]# su - omm
+   Last login: Tue Jul 27 11:18:16 CST 2021 on pts/1
+   [omm@www ~]$ gs_ctl stop -D /mogdb/data/db1
+   [2021-07-27 11:19:20.283][32166][][gs_ctl]: gs_ctl stopped ,datadir is /mogdb/data/db1
+   waiting for server to shut down.... done
+   server stopped
+   ```
+
+4. 在`omm`用户下执行如下命令启动数据库。
+
+   ```bash
+   [omm@www ~]$ gs_om -t start
+
+   Starting cluster.
+   =========================================
+
+   =========================================
+   [GAUSS-53600]: Can not start the database, the cmd is source /home/omm/.bashrc; python3 '/opt/enmo/wisequery/script/local/StartInstance.py' -U omm -R /opt/mogdb/app -t 300 --security-mode=off,  Error:
+   [GAUSS-51400] : Failed to execute the command: source /home/omm/.bashrc; python3 '/opt/enmo/wisequery/script/local/StartInstance.py' -U omm -R /opt/mogdb/app -t 300 --security-mode=off. Error:
+   [FAILURE] mogdb-kernel-0005
+   ```
+
+**目的：**
+
+在标准安装结束后（单机），通过`modip.py`脚本修改主机名，执行`gs_om -t start`命令，数据库启动成功。
+
+**故障解决步骤：**
+
+1. 以`omm`用户创建`modip.py`脚本文件。
+
+   ```python
+   [omm@www ~]$ cd
+   [omm@www ~]$ pwd
+   /home/omm
+   [omm@www ~]$ vi modip.py
+
+   # -*- coding:utf-8 -*-
+
+   import sys
+   ##sys.path.append(r'$GPHOME/script/')
+   sys.path.append(r'/opt/enmo/wisequery/script/')
+   from gspylib.common.DbClusterInfo import dbClusterInfo
+
+   oldIP = '172.16.0.176'
+   newIP = '172.16.0.176'
+   oldnodename = 'mogdb-kernel-0005'
+   newnodename = 'www.mogdb.com'
+   ##Output file directory
+   tmpDir = r'/home/omm'
+   dbuser = 'omm'
+
+   c1=dbClusterInfo()
+   c1.initFromStaticConfig(dbuser)
+
+   for node in c1.dbNodes:
+       if node.backIps[0] == oldIP:
+           node.backIps[0] = newIP
+       if len(node.virtualIp):
+           if node.virtualIp[0] == oldIP:
+               node.virtualIp[0] = newIP
+       if node.name == oldnodename:
+           node.name = newnodename
+       if node.sshIps[0] == oldIP:
+           node.sshIps[0] = newIP
+       for dn in node.datanodes:
+           if dn.listenIps[0] == oldIP:
+               dn.listenIps[0] = newIP
+           if dn.haIps[0] == oldIP:
+               dn.haIps[0] = newIP
+           for peerdn in dn.peerInstanceInfos:
+               if len(peerdn.peerHAIPs):
+                   if peerdn.peerHAIPs[0] == oldIP:
+                       peerdn.peerHAIPs[0] = newIP
+   for node in c1.dbNodes:
+       staticConfigPath_dn = "%s/cluster_static_config_%s" % (tmpDir, node.name)
+       c1.saveToStaticConfig(staticConfigPath_dn, node.id)
+       print(staticConfigPath_dn)
+   ```
+
+   > **说明：**需根据实际情况，修改主机IP地址和主机名。例如，在本示例中，主机IP地址为`172.16.0.176`，旧主机名为`mogdb-kernel-0005`，新主机名为`www.mogdb.com`。
+
+2. 执行如下命令生成集群静态配置文件。
+
+   ```bash
+   [omm@www ~]$ python3 modip.py
+   ```
+
+   回显如下即执行成功。
+
+   ```bash
+   /home/omm/cluster_static_config_www.mogdb.com
+   ```
+
+3. 执行如下命令替换源文件。
+
+   ```bash
+   [omm@www ~]$ mv /opt/mogdb/app/bin/cluster_static_config /opt/mogdb/app/bin/cluster_static_config_mogdb.com
+
+   [omm@www ~]$ cp /home/omm/cluster_static_config_www.mogdb.com /opt/mogdb/app/bin/cluster_static_config
+   ```
+
+4. 执行如下命令启动数据库。
+
+   ```bash
+   [omm@www ~]$ gs_om -t start
+
+   Starting cluster.
+   =========================================
+
+   [SUCCESS] www.mogdb.com
+
+   2021-07-26 16:20:42.938 60fe7056.1 [unknown] 139667408496384 [unknown] 0 dn_6001 01000  0 [BACKEND] WARNING: could not create any HA TCP/IP sockets
+   =========================================
+
+   Successfully started.
+   ```
diff --git a/product/zh/docs-mogdb/v3.0/faqs/high-availability-faqs.md b/product/zh/docs-mogdb/v3.0/faqs/high-availability-faqs.md
new file mode 100644
index 0000000000000000000000000000000000000000..1e61356769f9f6aa7b54a0a07df5dacc88d9f1f5
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/faqs/high-availability-faqs.md
@@ -0,0 +1,28 @@
+---
+title: 高可用FAQs
+summary: 高可用FAQs
+author: Guo Huan
+date: 2021-09-26
+---
+
+# 高可用FAQs
+
+**Q1：MogHA组件做了什么事情？**
+
+独立的HA套件MogHA，主动应对服务器宕机、实例宕机等多种情况，使数据库的故障持续时间从分钟级降到秒级。
+
+**Q2：MogDB HA的架构是怎样的？**
+
+当前支持一台主机和最少一台备机，备机最多8台（与openGauss最新发版保持同步）。
+
+多节点版基于openGauss做了改良处理，由一主多备组成，最高支持8个备库。多节点版的RPO为0，RTO小于10s，即当主节点实例故障时，从节点可以在10s之内转换为主节点并提供服务，同时能够保证数据不丢失。
+
+**Q3：MogDB常见部署架构是怎样的？**
+
+MogDB支持三种节点主库、备库、级联库，其中备库和级联库加起来最多支持8个，即1主4备4级联或1主8备，某客户生产架构为1主5备1级联，如下图。
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/faqs/high-availability-faqs-1.png)
+
+**Q4：MogDB的RPO/RTO怎样？高可用性可以达到99.999%吗？**
+
+RPO=0，RTO<10s，SLA=99.999%。
diff --git a/product/zh/docs-mogdb/v3.0/faqs/migration-faqs.md b/product/zh/docs-mogdb/v3.0/faqs/migration-faqs.md
new file mode 100644
index 0000000000000000000000000000000000000000..ac2253a0e99cc5cbb4843d0c5b22cfcee17a9d95
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/faqs/migration-faqs.md
@@ -0,0 +1,21 @@
+---
+title: 迁移FAQs
+summary: 迁移FAQs
+author: Guo Huan
+date: 2021-09-26
+---
+
+# 迁移FAQs
+
+**Q1：目前支持哪些数据库迁移到MogDB？**
+
+通过云和恩墨自研的MTK异构数据库迁移工具，您可以将以下数据库的数据结构、全量数据高速导入到MogDB。
+
+* Oracle
+* MySQL
+* DB2 
+* openGauss
+* PostgreSQL（存储过程不支持）
+* SQL Server（分区表不支持）
+
+更多信息请访问[MTK官方文档](http://docs.mogdb.io:8000/zh/mtk/v2.0/overview)。
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/faqs/product-faqs.md b/product/zh/docs-mogdb/v3.0/faqs/product-faqs.md
new file mode 100644
index 0000000000000000000000000000000000000000..d6fc4e3a504f299ee812aa99285a3a1ec19dd449
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/faqs/product-faqs.md
@@ -0,0 +1,153 @@
+---
+title: 产品FAQs
+summary: 产品FAQs
+author: Guo Huan
+date: 2021-09-26
+---
+
+# 产品FAQs
+
+**Q1：“极致RTO”、“并行恢复”与“备机可读”的关系是什么？**
+
+极致RTO、并行恢复、备机可读配置分别如下：
+
+- 极致RTO配置：recovery_parse_workers 并行恢复时解析XLOG线程的个数 recovery_parallelism 并行恢复线程的实际个数 recovery_parse_workers大于1时是极致RTO恢复，同时需要配置recovery_parallelism大于1，才会实现并行恢复。
+- 并行恢复配置：recovery_max_workers 并行恢复的最大线程个数 recovery_parallelism 并行恢复线程的实际个数 recovery_max_workers大于1时是并行恢复，同时需要配置recovery_parallelism大于1，才会实现并行恢复。
+- 备机可读配置：hot_standby 备机热备，在恢复时支持读操作。 hot_standby为true时是备机可读。
+
+并行恢复是文件级别的并行REDO，极致RTO是数据块级别的并行恢复。并行恢复和备机可读是兼容的，极致RTO和备机可读是不兼容的。 配置上面参数时，代码中有检查（CheckExtremeRtoGUCConflicts），如果同时配置了recovery_parse_workers大于1和hot_standby会报错。
+
+**Q2：极致RTO场景下，备机不能读，那该如何选择主备切换的候选主节点？**
+
+备机只有极致RTO情况下不能读，在串行恢复、并行恢复情况下，备机都是可读的。如果使用极致RTO，即在极致RTO情况下，当前只能配置为同步方式，然后随机选择一个当做主机即可（配置为同步方式后所有节点数据是一样的）。
+
+**Q3：模板数据库的作用是什么？模板数据库中包含哪些表？**
+
+模板数据库提供了一个快速创建数据库的手段，创建数据库时指定**TEMPLATE**参数，即可通过复制模板数据库创建数据库。
+
+模板数据库中没有用户表，可通过系统表PG_DATABASE查看模板数据库属性。
+
+**Q4：MogDB支持物理复制时，备机是按照Page并行回放日志吗？**
+
+MogDB有两种并行恢复模式，一种是以文件为粒度，一种是以页面为粒度。
+
+**Q5：MogDB是不是分布式数据库？**
+
+不是。MogDB目前仅仅是单机主备模式，不具备分布式数据库特征。
+
+但是如果对于分库分表，请求路由等非Native分布式需求，MogDB前端可以架设pgpool-II或者Shardingsphere等分布式中间件，来提供相应的功能。
+
+**Q6：MogDB的适用场景有哪些？**
+
+和pgsql受众类似。MogDB数据库可应用于电商、金融、O2O、电信CRM/计费等大并发、大数据量、
+
+ 以联机事务处理为主的交易型应用场景和工业监控、远程控制、智慧城市能力延展、智能家居、车联网等物联网应用场景。
+
+不仅具备关系型数据库的基本功能，更针对企业级应用场景和特性打造高可用、监控等增强功能
+
+**Q7：MogDB可以部署在x86服务器上吗？硬件推荐配置是怎样的？**
+
+MogDB可以安装在x86服务器上（AMD64芯片架构）。具体信息请参考[硬件环境要求](1-installation-preparation#yingjianhuanjing)。
+
+**Q8：MogDB可以部署在鲲鹏服务器上吗？硬件推荐配置是怎样的？**
+
+MogDB可以部署在鲲鹏服务器上（ARM芯片架构），硬件推荐配置同x86一样。
+
+实际上，MogDB在鲲鹏服务器上的性能更优于x86服务器，因此我们推荐客户选择国产芯片服务器。
+
+**Q9：MogDB是免费的吗？MogDB的收费模式是怎样的？**
+
+MogDB不是免费的（openGauss是免费的）。MogDB目前面向企业用户，不向个人开放，具体定价规则请咨询销售体系。
+
+**Q10：MogDB创建数据库时的兼容数据库设置具体指什么？对兼容不同数据库的数据类型都做了哪些处理？**
+
+MogDB创建数据库时可以指定DBCOMPATIBILITY参数以兼容不同数据库，但是这里的兼容只是非常有限的数据存储结构的兼容，并不会支持比如SQL语法等等的兼容。
+
+目前有三种设定，分别是Oracle、MySQL和PostgreSQL。默认兼容Oracle。
+
+- 在Oracle兼容性下，数据库将空字符串作为NULL处理，数据类型DATE会被替换为TIMESTAMP(0) WITHOUT TIME ZONE。
+- 在MySQL兼容性下，将字符串转换成整数类型时，如果输入不合法，会将输入转换为0，而其它兼容性则会报错。
+- 在PG兼容性下，CHAR和VARCHAR以字符为计数单位，其它兼容性以字节为计数单位。
+  例如，对于UTF-8字符集，CHAR(3)在PG兼容性下能存放3个中文字符，而在其它兼容性下只能存放1个中文字符。
+
+如需创建兼容PG数据库，语法格式：CREATE DATABASE dbname DBCOMPATIBILITY='PG';
+
+参数说明：
+
+DBCOMPATIBILITY [ = ] compatibilty_type
+
+指定兼容的数据库的类型。取值范围: A、B、C、PG。分别表示兼容Oracle、MySQL、Teradata和PostgreSQL。但是C目前已经放弃支持。因此常用的取值是A、B、PG。
+
+**Q11：MogDB在传统PostgreSQL的基础上做了什么重要改进？MogDB优势是什么？**
+
+在技术实现层面
+
+- 最大可用模式most_available_sync（同步备机故障时，主机事务不因同步备机故障而被阻塞）
+- xid不可耗尽
+- 流复制环境自动创建物理复制槽
+- 增量检查点
+- 双写double write等等
+
+在生态层面
+
+- 基于openGauss魔改，依托于openGauss的强大研发团队。
+- 完全自主可控。
+- 有完整的生态工具。（PTK，MTK，RWT，MIT，SCA，BRM）–部分工具还在研发中。
+- 社区活跃，资料丰富。
+
+**Q12：对于 Intel 处理器，MogDB的性能情况如何呢？**
+
+| **测试项**       | **数据量** | **并发数** | **CPU平均使用率** | **IOPS** | **IO延时** | **WAL数量** | **tpmC** | **测试时长** |
+| ---------------- | ---------- | ---------- | ----------------- | -------- | ---------- | ----------- | -------- | ------------ |
+| 单节点           | 100G       | 500        | 29.39%            | 6.50K    | 1.94.ms    | 3974        | 520896.3 | 10分钟       |
+| 一主一同步一异步 | 100G       | 500        | 30.4%             | 5.31K    | 453.2us    | 3944        | 519993.5 | 10分钟       |
+| 一主两同步       | 100G       | 500        | 26.35%            | 7.66K    | 531.9us    | 3535        | 480842.2 | 10分钟       |
+
+**Q13：MogDB支持部署在哪些操作系统上？会有兼容性问题吗？**
+
+MogDB支持部署在以下操作系统：
+
+- ARM：
+  - openEuler 20.3LTS（推荐采用此操作系统）
+  - 麒麟V10
+- X86：
+  - openEuler 20.3LTS
+  - CentOS 7.6
+  - Asianux 7.6
+
+不同的操作系统和CPU架构会有兼容性问题。
+
+**Q14：MogDB和Oracle在MVCC的实现上有什么区别？**
+
+Oracle：基于SCN，块级别，循环undo segment实现，支持闪回功能，存在大事务回滚、快照过旧ORA-01555问题。
+MogDB：基于事务编号txid，行级别，无需undo，大事务可瞬间回滚，存在数据块（block page）空间及性能消耗问题
+
+**Q15：MogDB的增量检查点优势在哪里？**
+
+增量检查点会小批量的分阶段的滚筒式的去进行脏页刷盘，同时更新lsn信息，回收不需要的xlog日志,避免了全量刷脏页对磁盘造成冲击，影响性能
+
+**Q16：MogDB如何屏蔽或优化原生PostgreSQL中遇到的XID用尽问题？**
+
+MogDB将transactionid由int32改为了int64，64位的xid永远不可能耗尽，虽然xid改为了64位，但是过期的xid依旧需要freeze清理，只是永远不用担心会发生xid回卷宕机的风险。
+
+**Q17：MogDB用户权限和Oracle有什么不同？**
+
+Oracle schema和user是一个概念，MogDB则不是。MogDB中，用户创建的所有对象都被创建在指定的schema（或namespace）中。其他用户可能拥有、也可能不拥有访问这些对象的权限，甚至都不可以在对应的schema中创建对象。用户（或角色）是全局对象，不是定义在数据库中，而是定义在实例的级别。schema是用户在指定的数据库中创建的，其中包含数据库对象。
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/faqs/product-faqs-1.png)
+
+**Q18：MogDB中double write与MySQL二次commit有什么区别？**
+
+实现原理与MySQL机制相同，其目的是为了保证数据的强一致性，防止因为坏块导致数据丢失，从而导致数据无法恢复。
+
+**Q19：MogDB主备和Oracle Data Guard有什么异同点？**
+
+备库都可以做为查询库分担主库压力
+
+**Q20：物理备份可以使用并行吗？物理备份可以远程执行吗？远程执行物理备份的时候数据文件是通过什么方式传输到执行备份的机器上？**
+
+gs_probackup支持并行备份。可以远程执行，可以通过archive文件或者stream协议传输到目标机器。
+
+**Q21：在物理备份的时候，设置xlog-method=stream或者fetch有什么不同？**
+
+设置xlog传输方式。没有设置该参数的情况下，默认–xlog-method=stream。在备份中包括所需的预写式日志文件（WAL文件）。这包括所有在备份期间产生的预写式日志。fetch方式在备份末尾收集预写式日志文件。因此，有必要把wal_keep_segments参数设置得足够高，这样在备份末尾之前日志不会被移除。如果在要传输日志时它已经被轮转，备份将失败并且是不可用的。stream方式在备份被创建时流传送预写式日志。这将开启一个到服务器的第二连接并且在运行备份时并行开始流传输预写式日志。因此，它将使用最多两个由max_wal_senders参数配置的连接。只要客户端能保持接收预写式日志，使用这种模式不需要在主控机上保存额外的预写式日志。
diff --git a/product/zh/docs-mogdb/v3.0/faqs/upgrade-faqs.md b/product/zh/docs-mogdb/v3.0/faqs/upgrade-faqs.md
new file mode 100644
index 0000000000000000000000000000000000000000..d4d6bab1cdea555a36858868f7eaf513d14ed2cc
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/faqs/upgrade-faqs.md
@@ -0,0 +1,8 @@
+---
+title: 升级FAQs
+summary: 升级FAQs
+author: Guo Huan
+date: 2021-09-26
+---
+
+正在编写中……
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/glossary.md b/product/zh/docs-mogdb/v3.0/glossary.md
new file mode 100644
index 0000000000000000000000000000000000000000..402e28fb63fba7487ca92b0cc7fc5015245ff7d4
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/glossary.md
@@ -0,0 +1,158 @@
+---
+title: 术语表
+summary: 术语表
+author: Guo Huan
+date: 2021-03-04
+---
+
+# 术语表
+
+**表 1** 术语表
+
+| **术语**            | **解释**                                                     |
+| :------------------ | :----------------------------------------------------------- |
+| **A - E**           |                                                              |
+| ACID                | 在可靠数据库管理系统（DBMS）中，事务（transaction）所应该具有的四个特性：原子性（Atomicity）、一致性（Consistency）、隔离性（Isolation）和持久性（Durability）。 |
+| AZ                  | Available Zone，通常指一个机房。                             |
+| bgwriter            | 数据库启动时创建的一个后台写线程，此线程用于将数据库中脏页面写入到持久性设备（例如磁盘）中。 |
+| bit                 | 比特。计算机处理的最小的信息单位。比特用来表示二进制数字1或0，或者一种逻辑条件真或假。一个单独的比特位所传达的信息很少有意义的。8个bit构成一个byte（字节），可用于表示如一个英文字母，十进制数字，或其它字符等多种类型的信息。 |
+| Bloom Filter        | 布隆过滤器。由Howard Bloom在1970年提出的二进制向量数据结构，它具有很好的空间和时间效率，被用来检测一个元素是不是集合中的一个成员，这种检测只会对在集合内的数据进行错判，而不会对不是集合内的数据进行错判，这样每个检测请求返回有“在集合内（可能错误）”和“不在集合内（绝对不在集合内）”两种情况，可见Bloom Filter是牺牲了正确率换取时间和空间。 |
+| CEK                 | Column Encryption Key，列加密密钥。                          |
+| CIDR                | Classless Inter-Domain Routing，无类域间路由IP编址方案。CIDR摒弃传统的基于类（A类：8，B类：16，C类：24）的地址分配方式，允许使用任意长度的地址前缀，有效提高地址空间的利用率。CIDR表示方法：IP地址/网络ID的位数。比如192.168.23.35/21，其中“21”表示前面地址中的前21位代表网络部分，其余位代表主机部分。 |
+| CLI                 | Command-line Interface，命令行界面。应用程序和用户交互的一种方式，完全基于文本输入和输出。命令通过键盘或类似装置输入，由程序编译并执行。结果是以文本或图形的方式呈现在终端界面。 |
+| CMK                 | 全密态场景：Client Master Key，客户端加密主密钥。透明数据加密场景：Cluster Master Key，集群主密钥。 |
+| CU                  | Compression Unit，压缩单元。列存表的最小存储单位。           |
+| core文件            | 当程序出现内存越界、断言失败或者访问非法内存时，操作系统会中止进程，并将当前内存状态导出到core文件中，以便进一步分析。core文件包含内存转储，支持全二进制和指定端口格式。core文件名称由字符串core以及操作系统进程ID组成。core文件不依赖于任何平台。 |
+| Core Dump           | 通常在程序异常终止时，核心转储（Core Dump）、内存转储或系统转储用于记录特定时间计算机程序工作内存的状态。实际上，其它关键程序的状态经常在同一时间进行转储，例如处理器寄存器，包括程序指标和栈指针、内存管理信息、其它处理器和操作系统标记及信息。Core Dump经常用于辅助诊断和纠错计算机程序问题。 |
+| DBA                 | Database Administrator，数据库管理员。指导或执行所有和维护数据库环境相关的操作。 |
+| DBLINK              | DBLINK是定义一个数据库到另一个数据库路径的对象，通过它可以查询远程数据库对象。 |
+| DBMS                | Database Management System，数据库管理系统。数据库管理系统是为了访问数据库中的信息而使用的一个管理系统软件。它包含一组程序使用户可以进入、管理、查询数据库中数据。基于真实数据的位置，可以分为内存数据库管理系统和磁盘数据库管理系统。 |
+| DCL                 | Data Control Language，数据控制语言。                        |
+| DDL                 | Data Definition Language，数据定义语言。                     |
+| DEK                 | Data Encryption Key，数据加密密钥。                          |
+| DML                 | Data Manipulation Language，数据操纵语言。                   |
+| 备份                | 备份件或者备份过程。指复制并归档计算机数据，当发生数据丢失事件时，可以用该复制并归档的数据来恢复原始数据。 |
+| 备份和恢复          | 保护数据库防止由于媒介失效或人为错误造成的数据丢失过程中涉及的一组概念、过程及策略。 |
+| 备机                | openGauss双机方案中的一个节点，用于作为主机的备份，在主机异常时，备机会切换到主机状态，以确保能正常提供数据服务。 |
+| 崩溃                | 崩溃（或系统崩溃）指计算机或程序（例如软件应用程序或操作系统）异常终止的事件。出现错误后，通常会自动退出。有时出现恶意程序冻结或挂起直到崩溃上报服务记录崩溃的详细信息。对于操作系统内核关键部分的程序，整个计算机可能瘫痪（可能造成致命的系统错误）。 |
+| 编码                | 编码是指用代码来表示各组数据资料，使其成为可利用计算机进行处理和分析的信息。用预先规定的方法将文字、数字或其它对象编成数码，或将信息、数据转换成规定的电脉冲信号。 |
+| 编码技术            | 呈现计算机软硬件识别的特定字符集数据的技术。                 |
+| 表                  | 表是由行与列组合成的。每一列被当作是一个字段。每个字段中的值代表一种类型的数据。例如，一个表可能有3个字段：姓名、城市和国家。这个表就会有3列：一列代表姓名，一列代表城市，一列代表国家。表中的每一行包含3个字段的内容，姓名字段包含姓名，城市字段包含城市，国家字段包含国家。 |
+| 表空间              | 包含表、索引、大对象、长数据等数据的逻辑存储结构。表空间在物理数据和逻辑数据间提供了抽象的一层，为所有的数据库对象分配存储空间。表空间创建好后，创建数据库对象时可以指定该对象所属的表空间。 |
+| 并发控制            | 在多用户环境下同时执行多个事务并保证数据完整性的一个DBMS服务。并发控制是openGauss提供的一种多线程管理机制，用来保证多线程环境下在数据库中执行的操作是安全的和一致的。 |
+| 查询                | 向数据库发出的信息请求，包含更新、修改、查询或删除信息的请求。 |
+| 查询操作符          | Query Operator，也称为查询迭代算子（Iterator）或查询节点（Query Tree Node）。一个查询的执行可以分解为一个或多个查询操作符，是构成一个查询执行的最基本单位。常见的查询操作符包括表扫描（Scan）、表关联（Join）、表聚集（Aggregation）等。 |
+| 持久性              | 数据库事务的ACID特性之一。在事务完成以后，该事务对数据库所作的更改便持久的保存在数据库之中，并不会被回滚。 |
+| 存储过程            | 存储过程（StoredProcedure）是在大型数据库系统中，一组为了完成特定功能的SQL语句集，经编译后存储在数据库中，用户通过指定存储过程的名称并设置参数（如果该存储过程带有参数）来执行它。 |
+| 操作系统            | 操作系统OS（operating system）由引导程序加载到计算机中，对计算机中其它程序进行管理。其它程序叫做应用或应用程序。 |
+| 大对象              | 大对象（Blob）在数据库中指使用二进制方式存储的数据。它通常可以用于存储视频、音频和图像等多媒体数据。 |
+| 段                  | 数据库中，一段指包含一个或多个区域的数据库中的一部分。区域是数据库的最小范围，由单元调用块组成。一个或多个段组成一个表空间。 |
+| **F - J**           |                                                              |
+| Failover            | 指当某个节点出现故障时，自动切换到备节点上的过程。反之，从备节点上切换回来的过程称为Failback。 |
+| FDW                 | Foreign Data Wrapper，外部数据封装器。是openGauss提供的一个SQL接口，用于访问远程数据存储中的大数据对象，使DBA可以整合来自不相关数据源的数据，将它们存入数据库中的一个公共模型。 |
+| Freeze              | 在事务ID耗尽时由AutoVacuum Worker进程自动执行的操作。openGauss会把事务ID记在行头，在一个事务取得一行时，通过比较行头的事务ID和事务本身的ID判断这行是否可见，而事务ID是一个无符号整数，如果事务ID耗尽，事务ID会跨过整数的界限重新计算，此时原先可见的行就会变成不可见的行，为了避免这个问题，Freeze操作会将行头的事务标记为一个特殊的事务ID，标记了这个特殊的事务ID的行将对所有事务可见，以此避免事务ID耗尽产生的问题。 |
+| GDB                 | GNU工程调试器，可以监控其它程序运行时的内部情况，或者其它程序要崩溃时发生了什么。GDB支持如下四种主要操作（使PDK功能更加强大），辅助查找缺陷。启动程序，指定可能影响行为的任何因素。特定条件下，停止程序。程序停止时，检查发生了什么。修改程序内容，尝试纠正一个缺陷并继续下一个。 |
+| GIN索引             | Generalized Inverted Index，通用倒排索引。作用为处理索引项为组合值的情况，查询时需要通过索引搜索出出现在组合值中的特定元素值。 |
+| GNU                 | GNU计划，又称革奴计划，是由RichardStallman在1983年9月27日公开发起的。它的目标是创建一套完全自由的操作系统。GNU是“GNU's NotUnix”的递归缩写。Stallman宣布GNU应当发音为Guh-NOO以避免与new这个单词混淆（注：Gnu在英文中原意为非洲牛羚，发音与new相同）。Unix是一种广泛使用的商业操作系统的名称。技术上讲，GNU类似Unix。但是GNU却给了用户自由。 |
+| gsql                | openGauss交互终端。通过gsql能够以交互的方式输入查询，下发查询到openGauss，然后查看查询结果。或者，也可以从文件中输入。此外，gsql还提供许多元命令和各种类似shell命令，协助脚本编写及自动化各种任务。 |
+| GUC                 | Grand Unified Configuration，数据库运行参数。配置这些参数可以影响数据库系统的行为。 |
+| HA                  | 高可用性（HighAvailability），通过尽量缩短因日常维护操作（计划）和突发的系统崩溃（非计划）所导致的停机时间，以提高系统和应用的可用性。 |
+| HBA                 | host-based authentication，主机认证。主机鉴权允许主机鉴权部分或全部系统用户。适用于系统所有用户或者使用Match指令的子集。该类型鉴权对于管理计算以及其它完全同质设备非常有用。总之，服务器上的三个文件以及客户端上的一个文件必须修改，为主机鉴权做准备。 |
+| IV                  | Initialization Vector，初始向量。初始向量是许多加密模式中用于随机化加密的一块数据，因此可以由相同的明文、相同的密钥产生不同的密文。 |
+| 服务器              | 为客户端提供服务的软硬件的组合。单独使用时，指运行服务器操作系统的计算机，也可以指提供服务的软件或者专用硬件。 |
+| 隔离性              | 数据库事务的ACID特性之一。它是指一个事务内部的操作及使用的数据对其它并发事务是隔离的，并发执行的各个事务之间不能互相干扰。 |
+| 关系型数据库        | 创建在关系模型基础上的数据库。关系型数据库借助于集合代数等数学概念和方法来处理数据库中的数据。 |
+| 归档线程            | 数据库打开归档功能时启动的一个线程，此线程用于将数据库日志归档到指定的路径。 |
+| 故障接管            | 功能对等的系统部件对于故障部件的自动替换过程。系统部件包含处理器、服务器、网络、数据库等。 |
+| 环境变量            | 定义进程操作环境某一方面的变量。例如，环境变量可以为主目录，命令搜索路径，使用终端或当前时区。 |
+| 检查点              | 将数据库内存中某一时刻的数据存到磁盘的机制。openGauss定期将已提交的事务数据和未提交的事务数据存到磁盘，这些数据用来和Redo日志一起在数据库重启和崩溃时恢复数据库。 |
+| 加密                | 用于传输数据的功能。通过该功能，可以隐藏信息内容，防止非法使用。 |
+| 节点                | 将构成openGauss数据库环境的各台服务器（物理机或虚拟机）称为数据库节点，简称节点。 |
+| 纠错                | 系统自动识别软件和数据流上的错误并自动修正错误的能力，提升系统的稳定性和可靠性。 |
+| 进程                | 在单个计算机上执行程序的实例。一个进程由一个或多个线程组成。其它进程不能接入某个进程已占用的线程。 |
+| 基于时间点恢复      | PITR（Point-In-TIme Recovery），基于时间点恢复是openGauss备份恢复的一个特性，是指在备份数据和WAL日志正常的情况下，数据可以恢复到指定时间点。 |
+| 记录                | 在关系型数据库中，每一条记录对应表中的每一行数据。           |
+| **K - O**           |                                                              |
+| KMC                 | Key Management Component，密钥管理组件。                     |
+| KMS                 | Key Management Service，密钥管理服务。                       |
+| KSF                 | Key Store File，密钥存储文件。                               |
+| 逻辑复制            | 数据库主备或两个数据库间的数据同步方式。区别于通过物理日志回放方式的物理复制，逻辑复制在两个数据库间传输逻辑日志或通过逻辑日志对应的SQL语句实现数据同步。 |
+| 逻辑日志            | 数据库修改的日志记录，可直接对应为SQL语句，一般为行级记录。区别于物理日志，物理日志是记录物理页面修改的日志。 |
+| 逻辑解码            | 逻辑解码是一种通过对xlog日志的反解实现将数据库表的所有持久更改抽取到一种清晰、易于理解的格式的处理过程。 |
+| 逻辑复制槽          | 在逻辑复制的环境下，逻辑复制槽用以防止Xlog被系统或Vaccum回收。openGauss中用于记录逻辑解码位置的对象，提供创建、删除、读取、推进等多个SQL接口函数。 |
+| MVCC                | Multi-Version Concurrency Control，多版本并发控制。数据库并发控制协议的一种，它的基本算法是一个元组可以有多个版本，不同的查询可以工作在不同的版本上。一个基本的好处是读和写可以不冲突。 |
+| NameNode            | NameNode是Hadoop系统中的一个中心服务器，负责管理文件系统的名称空间(namespace)以及客户端对文件的访问。 |
+| OM                  | Operations Management，运维管理模块。提供数据库日常运维、配置管理的管理接口、工具。 |
+| 客户端              | 连接或请求其它计算机或程序服务的计算机或程序。               |
+| 空闲空间管理        | 管理表内空闲空间的机制，通过记录每个表内空闲空间信息，并建立易于查找的数据结构，可以加速对空闲空间进行的操作（例如INSERT）。 |
+| 垃圾元组            | 是指使用DELETE和UPDATE语句删除的元组，openGauss在删除元组时只是打个删除标记，由Vacuum线程清理这种垃圾元组。 |
+| 列                  | 字段的等效概念。在数据库中，表由一列或多列组成。             |
+| 逻辑节点            | 一个物理节点上可以安装多个逻辑节点。一个逻辑节点是一个数据库实例。 |
+| 模式                | 数据库对象集，包括逻辑结构，例如表、视图、序、存储过程、同义名、索引及数据库链接。 |
+| 模式文件            | 用于决定数据库结构的SQL文件。                                |
+| **P - T**           |                                                              |
+| Page                | openGauss数据库关系对象结构中行存的最小内存单元。一个Page大小默认为8KB。 |
+| Paxos               | 分布式一致性协议。                                           |
+| PostgreSQL          | PostgreSQL是一个开源的关系数据库管理系统（DBMS），由全球志愿者团队开发。PostgreSQL不受任何公司或个体所控制，源代码免费使用。 |
+| postmaster          | 数据库服务启动时启动的一个线程。用于侦听来自数据库其它节点或客户端的连接请求。主机上侦听到备机连接请求，并接受后，就会创建一个WAL Sender线程，用于处理与备机的交互。 |
+| RHEL                | Red Hat Enterprise Linux，红帽企业Linux。                    |
+| REDO日志            | 记录对数据库进行操作的日志，这些日志包含重新执行这些操作所需要的信息。当数据库故障时，可以利用REDO日志将数据库恢复到故障前的状态。 |
+| RK                  | Root Key，加密根密钥。                                       |
+| SCTP                | Stream Control Transmission Protocol，流控制传输协议。是IETF于2000年新定义的一个传输层协议。是提供基于不可靠传输业务的协议之上的可靠的数据报传输协议。SCTP的设计用于通过IP网传输SCN窄带信令消息。 |
+| Savepoint           | 保存点。是一种在关系数据库管理系统中实现子事务（也称为嵌套事务）的方法。在一个长事务中，可以把操作过程分成几部分，前面部分执行成功后，可以建一个保存点，若后面的执行失败，则回滚到这个保存点即可，无需回滚整个事务。保存点对于在数据库应用程序中实现复杂错误恢复很有用。如果在多语句事务中发生错误，则应用程序可能能够从错误中恢复（通过回滚到保存点）而无需中止整个事务。 |
+| Session             | 数据库系统在接收到应用程序的连接请求时，为该连接创建的一个任务。它被Session Manager管理，完成一些初始化任务，执行用户的所有操作。 |
+| SMP                 | Symmetric Multi-Processing，对称多处理技术，是指在一台计算机上汇集了一组处理器（多CPU），各CPU之间共享内存子系统以及总线结构。操作系统必须支持多任务和多线程处理，以使得SMP系统发挥高效的性能。数据库领域的SMP并行技术，一般指利用多线程技术实现查询的并行执行，以充分利用CPU资源，从而提升查询性能。 |
+| SQL                 | Structure Query Language，结构化查询语言。数据库的标准查询语言。它可以分为数据定义语言（DDL）、数据操纵语言（DML）和数据控制语言（DCL）。 |
+| SSL                 | Secure Socket Layer，安全套接层。SSL是Netscape公司率先采用的网络安全协议。它是在传输通信协议（TCP/IP）上实现的一种安全协议，采用公开密钥技术。SSL广泛支持各种类型的网络，同时提供三种基本的安全服务，它们都使用公开密钥技术。SSL支持服务通过网络进行通信而不损害安全性。它在客户端和服务器之间创建一个安全连接。然后通过该连接安全地发送任意数据量。 |
+| 收敛比              | 交换机下行带宽与上行带宽的比值。收敛比越高，流量收敛程度越大，丢包越严重。 |
+| Table Access Method | 表访问方法层，对执行引擎和存储引擎进行解耦，实现存储引擎的可插拔能力。 |
+| TCP                 | Transmission Control Protocol，传输控制协议。用于将数据信息分解成信息包，使之经过IP协议发送；并对利用IP协议接收来的信息包进行校验并将其重新装配成完整的信息。TCP是面向连接的可靠协议，能够确保信息的无误发送。 |
+| TDE                 | Transparent Data Encryption，透明数据加密。                  |
+| trace               | 一种特殊的日志记录方法，用来记录程序执行的信息。程序员使用该信息进行纠错。另外，根据trace日志中信息的类型和内容，有经验的系统管理员或技术支持人员以及软件监控工具诊断软件常见问题。 |
+| 强一致性            | 任何查询不会瞬时的看到一个事务的中间状态。                   |
+| 全备份              | 备份整个数据库。                                             |
+| 全量同步            | openGauss双机方案中的一种数据同步机制，是指把主机中的所有数据同步给备机。 |
+| 日志文件            | 计算机记录自身活动的记录。                                   |
+| 事务                | 数据库管理系统执行过程中的一个逻辑单位，由一个有限的数据库操作序列构成，事务必须满足ACID原则。 |
+| 数据                | 事实或指令的一种表达形式，适用于人为或自动的通信、解释或处理。数据包含常量、变量、阵列和字符串。 |
+| 数据分区            | 数据分区是指在一个数据库实例内部，将表按照指定范围划分为多个数据互不重叠的部分（Partition）。具体的分区方式可以有：范围分区（Range），它根据元组中指定字段的取值所处的范围映射到目标存储位置。 |
+| 数据库              | 数据库是存储在一起的相关数据的集合，这些数据可以被访问，管理以及更新。同一视图中，数据库可以根据存储内容类型分为以下几类：数目类、全文本类、数字类及图像类。 |
+| 数据库实例          | 一个数据库实例是一个openGauss进程以及它控制的数据库文件。openGauss在一个物理节点上安装多个数据库实例。一个数据库实例也被称为一个逻辑节点。 |
+| 数据库双机          | openGauss提供的高可靠性双机方案。在此方案中，每个openGauss逻辑节点标识为主机或备机。在同一时间内，只有一个openGauss被标识为主机。双机初次建立时，主机会对每个备机数据做全量同步，然后做增量同步。双机建立之后的运行过程中，主机能接受数据读和写的操作请求，备机只做日志同步。 |
+| 数据库文件          | 保存用户数据和数据库系统内部数据的二进制文件。               |
+| 数据字典            | 数据字典是一系列只读的表，用来提供数据库的信息。这些信息包括：数据库设计信息、存储过程信息、用户权限、用户统计数据、数据库进程信息、数据库增长统计数据和数据库性能统计数据。 |
+| 死锁                | 为使用同一资源而产生的无法解决的争用状态。                   |
+| 索引                | 数据库索引，是数据库管理系统中一个排序的数据结构，以协助快速查询、更新数据库表中数据。 |
+| 统计信息            | 数据库使用统计信息估算查询代价，以查找代价最小的执行计划，统计信息一般是数据库自动收集的，包括表级信息（元组数、页面数等）和列级信息（列的值域分布直方图）。 |
+| 停用词              | 在信息检索中，为节省存储空间和提高搜索效率，在处理自然语言数据（或文本）之前或之后会自动过滤掉某些字或词，这些字或词即被称为Stop Words（停用词）。 |
+| **U - Z**           |                                                              |
+| Ustore              | In-place Update存储引擎别称，很好的解决了Append update存储引擎空间膨胀和元组较大的问题，高效回滚段的设计是In-place update存储引擎的基础。 |
+| Undo Record         | 撤销记录，用于undo记录的插入、查询以及组织，北向对接ustore，南向对接buffer pool。 |
+| Undo Space          | 管理Undo记录的物理资源，包括增删undo文件等。                 |
+| Undo Zone           | 与业务线程绑定，管理每个业务线程的Undo逻辑资源。             |
+| TransactionSlot     | 按照事务粒度记录Undo Record，用于事务回滚及Undo记录回收。    |
+| TIMECAPSULE         | 闪回的关键字，使用闪回技术后，恢复已提交的数据库修改前的数据，只需要秒级，而且恢复时间和数据库大小无关。 |
+| RECYCLE BIN         | 回收站，开启回收站开关后，DROP TABLE可以将表及其子对象放入回收站中。 |
+| PURGE               | 对回收站对象进行清理。                                       |
+| Vacuum              | 数据库定期启动的清理垃圾元组的线程，根据配置参数可以同时启动多个。 |
+| verbose             | verbose选项指定显示在屏幕上的处理信息。                      |
+| WAL                 | Write-Ahead Logging，预写日志系统。实现事务日志的标准方法，是指对数据文件（表和索引的载体）持久化修改之前必须先持久化相应的日志。 |
+| WAL Receiver        | 数据库复制时备机创建的一个线程的名称。此线程用于从主机接收数据、命令，并反馈确认信息至主机。一个备机只有一个WAL Receiver线程。 |
+| WAL Sender          | 数据库复制过程中，主机接受到备机的连接请求后创建的一个线程的名称。此线程用于发送命令、数据到备机，并从备机接收信息。一个主机可能会有多个WAL Sender线程，每一个WAL Sender线程对应一个备机的一个连接请求。 |
+| WAL Writer          | 数据库启动时创建的一个写Redo日志的线程，用于将内存中的日志写入到持久性设备（如：磁盘）。 |
+| Xlog                | 表示事务日志，一个逻辑节点中只有一个，不允许创建多个Xlog文件。 |
+| xDR                 | 详单。用户面和信令面详单的统称，包括CDR和UFDR、TDR和SDR。    |
+| 物理节点            | 一个物理机器称为一个物理节点。                               |
+| 系统表              | 存储数据库元信息的表，元信息包括数据库中的用户表、索引、列、函数和数据类型等。 |
+| 下推                | openGauss可以利用多DN并行执行查询计划，即将数据库主节点中的查询计划下发到各DN中并行执行。这种行为称为下推。与将数据抽取到数据库主节点上执行查询的方式相比，下推可以大幅提升查询性能。 |
+| 压缩                | 数据压缩，信源编码，或比特率降低涉及使用相比原来较少比特的编码信息。压缩可以是有损或无损。无损压缩通过识别和消除统计冗余降低比特位。无损压缩中没有信息丢失。有损压缩识别并删除次要信息，减少了比特位。减少数据文件大小的方法被普遍称为数据压缩，尽管其正式名称为源编码（数据源的编码，然后将其存储或传输）。 |
+| 一致性              | 数据库事务的ACID特性之一。在事务开始之前和事务结束以后，数据库的完整性约束没有被破坏。 |
+| 元数据              | 用来定义数据的数据。主要是描述数据自身信息，包含源、大小、格式或其它数据特征。数据库字段中，元数据用于理解以及诠释数据仓库的内容。 |
+| 原子性              | 数据库事务的ACID特性之一。整个事务中的所有操作，要么全部完成，要么全部不完成，不可能停滞在中间某个环节。事务在执行过程中发生错误，会被回滚到事务开始前的状态，就像这个事务从来没有执行过一样。 |
+| 脏页面              | 已经被修改且未写入持久性设备的页面。                         |
+| 增量备份            | 基于上次有效备份之后对文件修改的备份。                       |
+| 增量同步            | openGauss双机方案中的一种数据同步机制，是指把主机中数据增量同步给备机，即只同步主备间有差异的数据。 |
+| 主机                | openGauss数据库双机系统中接受数据读写操作的节点，和所有备机一起协同工作。在同一时间内，双机系统中只有一个节点被标识为主机。 |
+| 主题词              | 在标引和检索中用以表达文献主题的规范化的词或词组。           |
+| 转储文件            | 转储文件是一种特定类型的trace文件。转储文件为响应事件过程中一次性输出的诊断数据，trace文件指诊断数据的连续输出。 |
+| 最小恢复点          | 最小恢复点是openGauss提供的数据一致性保障手段之一。最小恢复点特性可以在openGauss启动时检查出WAL日志和持久化到磁盘的数据的不一致性，并提示用户进行处理。 |
diff --git a/product/zh/docs-mogdb/v3.0/installation-guide/docker-installation/docker-installation.md b/product/zh/docs-mogdb/v3.0/installation-guide/docker-installation/docker-installation.md
new file mode 100644
index 0000000000000000000000000000000000000000..b1ea9e5de7d7d544994c921af6f6ac0eeb3649fe
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/installation-guide/docker-installation/docker-installation.md
@@ -0,0 +1,452 @@
+---
+title: 容器化安装
+summary: 容器化安装
+author: Guo Huan
+date: 2021-06-01
+---
+
+# 容器化安装
+
+本文档主要介绍MogDB容器版安装过程。MogDB容器版本不支持 MogHA工具、OM工具，目前最多支持一主八备。MogDB 2.1容器版支持最新版的compat-tools和插件功能。
+
+由于考虑尽可能缩减容器镜像的大小，以方便快速下载和部署，从2.0版本开始，容器化MogDB在容器里运行的操作系统在x86和ARM架构下分别运行在Ubuntu和Debian之上。
+
+x86-64架构的MogDB容器运行在Ubuntu 18.04操作系统中。
+
+ARM64架构的MogDB容器运行在Debian 10 操作系统中。
+
+<br/>
+
+## Docker部署
+
+### 单实例安装
+
+#### 准备工作
+
+容器化MogDB的安装与宿主机的操作系统无关，能够运行容器引擎的所有操作系统均可支持，比如Linux，Windows，macOS。
+在安装容器版MogDB之前，您需要先安装容器运行时环境，比如Docker。
+
+Docker是一个开源的应用容器引擎，基于Go语言并遵从Apache2.0协议开源。Docker可以让开发者打包他们的应用以及依赖包到一个轻量级、可移植的容器中，然后发布到任何流行的Linux机器上，也可以实现虚拟化。
+
+Docker Desktop下载地址：<https://www.docker.com/products/docker-desktop>
+
+<br/>
+
+#### 安装步骤
+
+1. 启动Docker服务。
+
+2. 输入以下命令获取最新版MogDB镜像文件：
+
+   ```bash
+   docker pull swr.cn-north-4.myhuaweicloud.com/mogdb/mogdb:2.1.1
+   ```
+   
+   > 说明：MogDB镜像支持运行在x86和ARM架构中，会根据发起命令的服务器架构自动下载相应的镜像，无需手工指定。
+
+3. 输入以下命令为 MogDB 创建运行目录，下文以“mogdb”为例：
+
+   ```bash
+   mkdir /mogdb
+   ```
+
+4. 继续输入以下命令创建一个新的容器，将容器命名为“mogdb”，以启动 MogDB 实例：
+
+   ```bash
+   docker run --name mogdb --privileged=true -d -e GS_PASSWORD=Secretpassword@123  -v /mogdb:/var/lib/mogdb  -p 15432:5432  swr.cn-north-4.myhuaweicloud.com/mogdb/mogdb:2.1.1
+   ```
+
+   对于Windows系统而言：
+
+   - 如果Docker使用Hyper-V做引擎，请依次执行以下命令，在Hyper-V中创建卷的逻辑对象mogdata，然后创建容器：
+
+     ```bash
+     docker volume create mogdata
+
+     docker run --name mogdb --privileged=true -d -e GS_PASSWORD=Secretpassword@123 -v mogdata:/var/lib/mogdb -p 15453:5432  swr.cn-north-4.myhuaweicloud.com/mogdb/mogdb:2.1.1
+     ```
+
+   - 如果Docker启用WSL 2做引擎，请执行以下命令创建容器：
+
+     ```bash
+     docker run --name mogdb --privileged=true -d -e GS_PASSWORD=Secretpassword@123 -v C:\mogdb:/var/lib/mogdb -p 15432:5432  swr.cn-north-4.myhuaweicloud.com/mogdb/mogdb:2.1.1
+     ```
+
+   > 注意：
+   >
+   > - MogDB的默认监听启动在容器内的5432端口上，如果想要从容器外部访问数据库，则需要在`docker run`的时候指定`-p`参数。比如以上命令将允许使用15432端口访问容器数据库。
+   > - 容器一旦被删除，容器内的所有数据和配置也均会丢失，而从镜像重新运行一个容器的话，则所有数据又都是呈现在初始化状态，因此对于数据库容器来说，为了防止因为容器的消亡或者损坏导致的数据丢失，需要进行持久化存储数据的操作。通过在`docker run`的时候指定`-v`参数来实现。比如以上命令将会指定将MogDB的所有数据文件存储在宿主机的`/mogdb`下。如果使用podman，会有目标路径检查，需要预先创建宿主机目标路径（步骤4）。
+
+5. 进入容器终端：
+
+   ```bash
+   docker exec -it mogdb bash
+   ```
+
+   至此，MogDB 容器版单实例安装完成。
+
+<br/>
+
+#### 使用MogDB
+
+安装完成并进入容器后，通过`su - omm`切换为omm用户，即可通过gsql进行数据库访问以正常体验MogDB各项功能：
+
+```
+root@384ac97543bd:/# su - omm
+omm@384ac97543bd:~$ gsql -d postgres
+gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+Non-SSL connection (SSL connection is recommended when requiring high-security)
+Type "help" for help.
+
+MogDB=#
+```
+
+<br/>
+
+#### 环境变量
+
+为了更灵活地使用MogDB镜像，可以设置额外的参数。未来我们会扩充更多的可控制参数，当前版本支持以下变量的设定。
+
+**GS_PASSWORD**
+
+使用MogDB镜像的时候，必须设置该参数。该参数值不能为空或者不定义。该参数设置了MogDB数据库的超级用户omm以及测试用户mogdb的密码。MogDB安装时默认会创建omm超级用户，该用户名暂时无法修改。测试用户mogdb是在entrypoint.sh中自定义创建的用户。
+
+MogDB镜像配置了本地信任机制，因此在容器内连接数据库无需密码，但是如果要从容器外部（其它主机或者其它容器）连接则必须要输入密码。
+
+MogDB的密码有复杂度要求，密码长度8个字符以上，必须同时包含大写字母、小写字母、数字、以及特殊符号（特殊符号仅包含( \# ? ! @ $ % ^ & * \- )，并且 ! $ & 需要用转义符"\\"进行转义。
+
+**GS_NODENAME**
+
+指定数据库节点名称，默认为mogdb。
+
+**GS_USERNAME**
+
+指定数据库连接用户名，默认为mogdb。
+
+**GS_PORT**
+
+指定数据库端口，默认为5432。
+
+<br/>
+
+### 主备安装
+
+#### 准备工作
+
+如需进行MogDB容器版主备搭建，请先完成上文“单实例安装”中的步骤。
+
+#### 操作步骤
+
+1. 切换到root用户：
+
+   ```bash
+   su - root
+   ```
+
+2. 创建自定义网络，创建容器便于使用的固定IP：
+
+   ```bash
+   docker network create --subnet=172.18.0.0/16 myNetwork
+   ```
+
+3. 创建主库容器：
+
+   ```bash
+   docker run --name mogdb_master \
+   --network myNetwork --ip 172.18.0.10 --privileged=true \
+   --hostname mogdb_master --detach \
+   --env GS_PORT=6432 \
+   --env OG_SUBNET=172.18.0.0/16 \
+   --env GS_PASSWORD=Enmo@1234 \
+   --env NODE_NAME=mogdb_master \
+   --env REPL_CONN_INFO="replconninfo1 = 'localhost=172.18.0.10 localport=6439  localservice=6432 remotehost=172.18.0.11 remoteport=6439 remoteservice=6432 '\n" \
+   swr.cn-north-4.myhuaweicloud.com/mogdb/mogdb:2.1.1 -M primary
+   ```
+
+4. 创建备库容器：
+
+   ```bash
+    docker run --name mogdb_slave_one \
+    --network myNetwork --ip 172.18.0.11 --privileged=true \
+    --hostname mogdb_slave_one --detach \
+    --env GS_PORT=6432 \
+    --env OG_SUBNET=172.18.0.0/16 \
+    --env GS_PASSWORD=Enmotech@1234 \
+    --env NODE_NAME=mogdb_slave_one \
+    --env REPL_CONN_INFO="replconninfo1 = 'localhost=172.18.0.11 localport=6439  localservice=6432 remotehost=172.18.0.10 remoteport=6439 remoteservice=6432 '\n" \
+    enmotech/mogdb:2.1.1 -M standby
+   ```
+
+5. 查询主库角色状态：
+
+   ```
+   [root@localhost ~]# docker exec -it mogdb_master bash 
+   [root@mogdb_master /] # su - omm
+   [omm@mogdb_master ~] $ gs_ctl query -D /var/lib/mogdb/data/
+   [2021-04-07 13:28:15.492][323][][gs_ctl] : gs_ctl query ,datadir is /var/lib/mogdb/data
+    HA state:
+         local_role                   : Primary
+         static_connections           : 1
+         db_state                     : Normal
+         detail_information           : Normal
+         
+    Senders info:
+         sender_pid                   : 286
+         local_role                   : Primary
+         peer_role                    : Standby
+         peer_state                   : Normal
+         state                        : Streaming
+         sender_sent_location         : 0/40007D0
+         sender_write_location        : 0/40007D0
+         sender_flush_location        : 0/40007D0
+         sender_replay_location       : 0/40007D0
+         receiver_received_location   : 0/40007D0
+         receiver_write_location      : 0/40007D0
+         receiver_flush_location      : 0/40007D0
+         receiver_replay_location     : 0/40007D0
+         sync_percent                 : 100%
+         sync_state                   : Sync
+         sync_priority                : 1
+         sync_most_available          : On
+         channel                      : 172.18.0.10:6439-->172.18.0.11: 45640
+   
+    Receiver info: 
+   No information
+   ```
+
+6. 查询备库角色状态：
+
+   ```
+   [root@localhost ~]# docker exec -it mogdb_slave_one bash
+   [root@mogdb_slave_one /] # su - omm
+   Last login: Wed Apr 7 13:32:23 UTC 2021 on pts/0
+   [omm@mogdb_slave_one ~] $ gs_ctl query -D /var/lib/mogdb/data/
+   [2021-04-07 14:46:15.492][393][][gs_ctl] : gs_ctl query ,datadir is /var/lib/mogdb/data
+    HA state:
+         local_role                   : Standby
+         static_connections           : 1
+         db_state                     : Normal
+         detail_information           : Normal
+         
+    Senders info:
+   No information
+    Receiver info: 
+         receiver_pid                 : 312
+         local_role                   : Standby
+         peer_role                    : Primary
+         peer_state                   : Normal
+         state                        : Normal
+         sender_sent_location         : 0/4005D50
+         sender_write_location        : 0/4005D50
+         sender_flush_location        : 0/4005D50
+         sender_replay_location       : 0/4005D50
+         receiver_received_location   : 0/4005D50
+         receiver_write_location      : 0/4005D50
+         receiver_flush_location      : 0/4005D50
+         receiver_replay_location     : 0/4005D50
+         sync_percent                 : 100%
+         channel                      : 172.18.0.11:45640<--172.18.0.10:6439
+   ```
+   
+   > 说明：从上面主库Senders信息和备库Receiver可以看到主备状态正常。
+
+#### 读写测试
+
+主库写测试：
+
+```sql
+[omm@mogdb_master ~] $ gsql -p6432
+gsql ((MogDB 2.1.1 build 56189e20) compiled at 2022-03-21 18:47:53 commit 0 last mr  )
+Non-SSL connection (SSL connection is recommended when requiring high-security)
+Type "help" for help.
+
+omm=# create table test(ID int);
+CREATE TABLE
+omm=# insert into test values(1);
+INSERT 0 1
+```
+
+备库读测试：
+
+```sql
+[omm@mogdb_slave_one ~] $ gsql -p6432
+gsql ((MogDB 2.1.1 build 56189e20) compiled at 2022-03-21 18:47:53 commit 0 last mr  )
+Non-SSL connection (SSL connection is recommended when requiring high-security)
+Type "help" for help.
+
+omm=# select * from test;
+ id 
+----
+  1
+(1 row)
+
+omm=# delete from test;
+ERROR: cannot execute DELETE in a read-only transaction
+```
+
+> 说明：命令结果显示主库可写，备库可读但不可写。
+
+#### 切换测试
+
+将mogdb_slave_one切换为主库，mogdb_master切换为备库。
+
+mogdb_slave_one执行switchover：
+
+```
+[omm@mogdb_slave_one ~] $ gs_ctl switchover -D /var/lib/mogdb/data/
+[2021-04-07 15:31:45.246][428][][gs_ctl]: gs_ctl switchover ,datadir is /var/lib/mogdb/data
+[2021-04-07 15:31:45.247][428][][gs_ctl]: switchover term(1)
+[2021-04-07 15:31:45.251][428][][gs_ctl]: waiting for server to switchover......
+[2021-04-07 15:31:45.325][428][][gs_ctl]: done
+[2021-04-07 15:31:45.325][428][][gs_ctl]: switchover completed (/var/lib/mogdb/data)
+```
+
+mogdb_slave_one查询状态：
+
+```
+[omm@mogdb_slave_one ~] $ gs_ctl query -D /var/lib/mogdb/data/
+[2021-04-07 15:42:45.246][459][][gs_ctl]: gs_ctl query ,datadir is /var/lib/mogdb/data
+ HA state:
+      local_role                   : Primary
+      static_connections           : 1
+      db_state                     : Normal
+      detail_information           : Normal
+      
+ Senders info:
+      sender_pid                   : 442
+      local_role                   : Primary
+      peer_role                    : Standby
+      peer_state                   : Normal
+      state                        : Streaming
+      sender_sent_location         : 0/40102B8
+      sender_write_location        : 0/40102B8
+      sender_flush_location        : 0/40102B8
+      sender_replay_location       : 0/40102B8
+      receiver_received_location   : 0/40102B8
+      receiver_write_location      : 0/40102B8
+      receiver_flush_location      : 0/40102B8
+      receiver_replay_location     : 0/40102B8
+      sync_percent                 : 100%
+      sync_state                   : Sync
+      sync_priority                : 1
+      sync_most_available          : On
+      channel                      : 172.18.0.11:6439-->172.18.0.10: 49696
+
+ Receiver info: 
+No information
+```
+
+mogdb_master查询状态：
+
+```
+[omm@mogdb_master ~] $ gs_ctl query -D /var/lib/mogdb/data/
+[2021-04-07 15:46:35.246][619][][gs_ctl]: gs_ctl query ,datadir is /var/lib/mogdb/data
+ HA state:
+      local_role                   : Standby
+      static_connections           : 1
+      db_state                     : Normal
+      detail_information           : Normal
+      
+ Senders info:
+No information
+ Receiver info: 
+      receiver_pid                 : 590
+      local_role                   : Standby
+      peer_role                    : Primary
+      peer_state                   : Normal
+      state                        : Normal
+      sender_sent_location         : 0/4010718
+      sender_write_location        : 0/4010718
+      sender_flush_location        : 0/4010718
+      sender_replay_location       : 0/4010718
+      receiver_received_location   : 0/4010718
+      receiver_write_location      : 0/4010718
+      receiver_flush_location      : 0/4010718
+      receiver_replay_location     : 0/4010718
+      sync_percent                 : 100%
+      channel                      : 172.18.0.10:49696<--172.18.0.11:6439
+```
+
+可以看到mogdb_master变为备库，mogdb_slave_one变为主库，切换成功。
+
+#### 数据读写验证
+
+切换后的主库mogdb_slave_one做写入验证：
+
+```sql
+[omm@mogdb_slave_one ~] $ gsql -p6432
+gsql ((MogDB 2.1.1 build 56189e20) compiled at 2022-03-21 18:47:53 commit 0 last mr  )
+Non-SSL connection (SSL connection is recommended when requiring high-security)
+Type "help" for help.
+
+omm=# select * from test;
+ id 
+----
+  1
+(1 row)
+
+omm=# insert into test values(2);
+INSERT 0 1
+```
+
+切换后的备库mogdb_master做读取验证：
+
+```sql
+[omm@mogdb_master ~] $ gsql -p6432
+gsql ((MogDB 2.1.1 build 56189e20) compiled at 2022-03-21 18:47:53 commit 0 last mr  )
+Non-SSL connection (SSL connection is recommended when requiring high-security)
+Type "help" for help.
+
+omm=# select * from test;
+ id 
+----
+  1
+  2
+(2 row)
+
+omm=# delete from test;
+ERROR: cannot execute DELETE in a read-only transaction
+```
+
+可以看到，原备库切换为主库后可写，原主库切换为备库后可读但不可写。
+
+<br/>
+
+## Kubernetes部署
+
+MogDB 2.1版本以后支持Kubernetes部署。
+
+- x86
+  
+  ```
+  $ kubectl apply -f https://gitee.com/enmotech/enmotech-docker-mogdb/raw/master/2.1.1/k8s_amd.yaml
+  pod/mogdb created
+  ```
+
+- arm
+
+  ```
+  $ kubectl apply -f https://gitee.com/enmotech/enmotech-docker-mogdb/raw/master/2.1.1/k8s_arm.yaml
+  pod/mogdb created
+  ```
+
+- k8s连接pod
+
+  进入容器内通过gsql命令登录MogDB。
+
+  ```
+  $ kubectl exec -it mogdb -- bash
+  root@mogdb:/# su - omm
+  omm@mogdb:~$ gsql -d postgres
+  gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+  Non-SSL connection (SSL connection is recommended when requiring high-security)
+  Type "help" for help.
+  
+  MogDB=#
+  ```
+
+<br/>
+
+## 后续步骤
+
+MogDB容器版不支持MogHA工具、OM工具，仅用于测试使用，目前最多支持一主八备。MogDB企业版包含MogHA组件。容器版与企业版基础功能完全一致，在生产环境中建议使用MogDB企业版。
diff --git a/product/zh/docs-mogdb/v3.0/installation-guide/manual-installation.md b/product/zh/docs-mogdb/v3.0/installation-guide/manual-installation.md
new file mode 100644
index 0000000000000000000000000000000000000000..29883c9a9130fadfc896012dd67e95f4171731f1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/installation-guide/manual-installation.md
@@ -0,0 +1,374 @@
+---
+title: MogDB/openGauss 手动部署(非OM工具)单机，主备，主备级联架构
+summary: MogDB/openGauss 手动部署(非OM工具)单机，主备，主备级联架构
+author: Zhang Cuiping
+date: 2021-10-14
+---
+
+# MogDB/openGauss 手动部署(非OM工具)单机，主备，主备级联架构
+
+## 前期准备
+
+1. 关闭防火墙，selinux
+
+   ```bash
+   systemctl disable firewalld.service
+   systemctl stop firewalld.service
+   setenforce=0
+   sed -i '/^SELINUX=/c'SELINUX=disabled /etc/selinux/config
+   ```
+
+2. 安装依赖包
+
+   ```bash
+   yum install libaio-devel -y
+   ```
+
+3. 创建相关目录，用户，组
+
+   ```bash
+   groupadd dbgrp -g 2000
+   useradd omm -g 2000 -u 2000
+   echo "Enmo@123" | passwd --stdin omm
+   mkdir -p /opt/mogdb/software
+   chown -R omm:dbgrp /opt/software/mogdb
+   ```
+
+4. 上传并解压二进制文件
+
+   ```bash
+   [root@mogdb-kernel-0001 software]# pwd
+   /opt/mogdb/software
+   [root@mogdb-kernel-0001 software]# ls -lrt
+   total 90236
+   -r-------- 1 root root 92401412 Jun 13 06:14 MogDB-2.1.1-openEuler-64bit.tar.bz2
+   chown omm:dbgrp MogDB-2.1.1-openEuler-64bit.tar.bz2
+   su - omm
+   cd /opt/mogdb/software/
+   tar -xf MogDB-2.1.1-openEuler-64bit.tar.bz2
+   ```
+
+## 初始化数据库（单机）
+
+1. 配置环境变量
+
+   ```bash
+   echo "export GAUSSHOME=/opt/mogdb/software"  >> /home/omm/.bashrc && \
+   echo "export PATH=\$GAUSSHOME/bin:\$PATH " >> /home/omm/.bashrc && \
+   echo "export LD_LIBRARY_PATH=\$GAUSSHOME/lib:\$LD_LIBRARY_PATH" >> /home/omm/.bashrc
+   source /home/omm/.bashrc
+   ```
+
+2. init数据库
+
+   ```bash
+   bin/gs_initdb --pgdata=/opt/mogdb/data --nodename=primary --pwpasswd=Enmo@123 --encoding=UTF-8 --locale=en_US.UTF-8
+   ```
+
+3. 修改初始化参数
+
+   ```bash
+   echo "port=26000" >> /opt/mogdb/data/postgresql.conf
+   echo "listen_addresses = '0.0.0.0'" >> /opt/mogdb/data/postgresql.conf
+   echo "password_encryption_type = 0" >> /opt/mogdb/data/postgresql.conf
+   echo "log_directory = 'pg_log'" >> /opt/mogdb/data/postgresql.conf
+   echo "remote_read_mode=non_authentication" >> /opt/mogdb/data/postgresql.conf
+   echo "host all all 0.0.0.0/0 md5" >> /opt/mogdb/data/pg_hba.conf
+   ```
+
+4. 启动数据库
+
+   ```bash
+   gs_ctl start -D /opt/mogdb/data
+   ```
+
+**至此单机安装完成**
+
+## 主备安装
+
+1. 主库操作
+
+    - 配置连接通道
+
+    ```bash
+    echo "replconninfo1='localhost=172.16.0.106 localport=26001 localheartbeatport=26005 localservice=26004 remotehost=172.16.0.245 remoteport=26001 remoteheartbeatport=26005 remoteservice=26004'
+    " >> /opt/mogdb/data/postgresql.conf
+    ```
+
+    **localhost为主库IP,remotehost为备库IP**
+
+    - 将主库以primary方式启动
+
+    ```bash
+    gs_ctl restart -D /opt/mogdb/data/ -M primary
+    ```
+
+2. 备库操作
+
+- 前期准备工作如上（一）
+
+- 配置环境变量
+
+  ```bash
+  echo "export GAUSSHOME=/opt/mogdb/software"  >> /home/omm/.bashrc && \
+  echo "export PATH=\$GAUSSHOME/bin:\$PATH " >> /home/omm/.bashrc && \
+  echo "export LD_LIBRARY_PATH=\$GAUSSHOME/lib:\$LD_LIBRARY_PATH" >> /home/omm/.bashrc
+  source /home/omm/.bashrc
+  - 将主库的配置文件传到备库
+  scp /opt/mogdb/data/pg_hba.conf /opt/mogdb/data/postgresql.conf 172.16.0.245:/opt/mogdb/data/
+  ```
+
+- 配置连接通道,将localhost和remotehost对调.
+
+  ```bash
+  sed -i “/^replconninfo1/creplconninfo1=‘localhost=172.16.0.245 localport=26001 localheartbeatport=26005 localservice=26004 remotehost=172.16.0.106 remoteport=26001 remoteheartbeatport=26005 remoteservice=26004’” /opt/mogdb/data/postgresql.conf
+  ```
+
+  **localhost为备库IP,remotehost为主库IP**
+
+- 构建主备关系
+
+  ```bash
+  gs_ctl build -D /opt/mogdb/data/ -b full -M standby
+  ```
+
+- 查询主备状态
+
+  - 主库
+
+    ```bash
+    gs_ctl query -D /opt/mogdb/data/
+    [2021-06-13 07:51:41.119][159054][][gs_ctl]: gs_ctl query ,datadir is /opt/mogdb/data
+    HA state:
+            local_role                     : Primary
+            static_connections             : 1
+            db_state                       : Normal
+            detail_information             : Normal
+
+    Senders info:
+            sender_pid                     : 159041
+            local_role                     : Primary
+            peer_role                      : Standby
+            peer_state                     : Normal
+            state                          : Streaming
+            sender_sent_location           : 0/14000258
+            sender_write_location          : 0/14000258
+            sender_flush_location          : 0/14000258
+            sender_replay_location         : 0/14000258
+            receiver_received_location     : 0/14000258
+            receiver_write_location        : 0/14000258
+            receiver_flush_location        : 0/14000258
+            receiver_replay_location       : 0/14000258
+            sync_percent                   : 100%
+            sync_state                     : Sync
+            sync_priority                  : 1
+            sync_most_available            : Off
+            channel                        : 172.16.0.106:26001-->172.16.0.245:60856
+
+    Receiver info:
+    No information
+    ```
+
+  - 备库
+
+    ```bash
+    gs_ctl query -D /opt/mogdb/data/
+    [2021-06-13 07:51:32.743][123204][][gs_ctl]: gs_ctl query ,datadir is /opt/mogdb/data
+    HA state:
+            local_role                     : Standby
+            static_connections             : 1
+            db_state                       : Normal
+            detail_information             : Normal
+
+    Senders info:
+    No information
+    Receiver info:
+            receiver_pid                   : 123194
+            local_role                     : Standby
+            peer_role                      : Primary
+            peer_state                     : Normal
+            state                          : Normal
+            sender_sent_location           : 0/14000140
+            sender_write_location          : 0/14000140
+            sender_flush_location          : 0/14000140
+            sender_replay_location         : 0/14000140
+            receiver_received_location     : 0/14000140
+            receiver_write_location        : 0/14000140
+            receiver_flush_location        : 0/14000140
+            receiver_replay_location       : 0/14000140
+            sync_percent                   : 100%
+            channel                        : 172.16.0.245:60856<--172.16.0.106:26001
+    ```
+
+**至此主备已安装完成**
+
+## 主备级联安装
+
+1. 主备安装如上(一，二，三)
+
+2. 添加复制通道
+
+    - 主库操作
+
+    ```bash
+    gsql -d postgres -p26000 -c “alter system set replconninfo2 to ‘localhost=172.16.0.106 localport=26001 localheartbeatport=26005 localservice=26004 remotehost=172.16.0.127 remoteport=26001 remoteheartbeatport=26005 remoteservice=26004 iscascade=true’;”
+    ```
+
+    - 备库操作
+
+    ```bash
+    gsql -d postgres -p26000 -c “alter system set replconninfo2 to ‘localhost=172.16.0.245 localport=26001 localheartbeatport=26005 localservice=26004 remotehost=172.16.0.127 remoteport=26001 remoteheartbeatport=26005 remoteservice=26004 iscascade=true’;”
+    ```
+
+3. 级联库操作
+
+- 前期准备工作如上（一）
+
+- 配置环境变量
+
+  ```bash
+  echo "export GAUSSHOME=/opt/mogdb/software"  >> /home/omm/.bashrc && \
+  echo "export PATH=\$GAUSSHOME/bin:\$PATH " >> /home/omm/.bashrc && \
+  echo "export LD_LIBRARY_PATH=\$GAUSSHOME/lib:\$LD_LIBRARY_PATH" >> /home/omm/.bashrc
+  source /home/omm/.bashrc
+  ```
+
+- 将备库的配置文件传到备库
+
+  ```bash
+  scp /opt/mogdb/data/pg_hba.conf /opt/mogdb/data/postgresql.conf 172.16.0.245:/opt/mogdb/data/
+  ```
+
+- 配置连接通道
+
+  ```bash
+  sed -i "/^replconninfo1/creplconninfo1='localhost=172.16.0.127 localport=26001 localheartbeatport=26005 localservice=26004 remotehost=172.16.0.106 remoteport=26001 remoteheartbeatport=26005 remoteservice=26004'" /opt/mogdb/data/postgresql.conf
+  sed -i "/replconninfo2/creplconninfo2='localhost=172.16.0.127 localport=26001 localheartbeatport=26005 localservice=26004 remotehost=172.16.0.245 remoteport=26001 remoteheartbeatport=26005 remoteservice=26004'" /opt/mogdb/data/postgresql.conf
+  ```
+
+  **localhost为级联IP，remotehost为主库IP和备库IP。**
+
+- 构建主备关系
+
+  ```bash
+  gs_ctl build -D /opt/mogdb/data/ -b full -M cascade_standby
+  ```
+
+4 查看主备级联状态
+
+- 主库
+
+  ```bash
+  gs_ctl query -D /opt/mogdb/data
+  [2021-06-13 08:37:03.281][207069][][gs_ctl]: gs_ctl query ,datadir is /opt/mogdb/data
+   HA state:
+          local_role                     : Primary
+          static_connections             : 2
+          db_state                       : Normal
+          detail_information             : Normal
+
+   Senders info:
+          sender_pid                     : 206143
+          local_role                     : Primary
+          peer_role                      : Standby
+          peer_state                     : Normal
+          state                          : Streaming
+          sender_sent_location           : 0/1A000140
+          sender_write_location          : 0/1A000140
+          sender_flush_location          : 0/1A000140
+          sender_replay_location         : 0/1A000140
+          receiver_received_location     : 0/1A000140
+          receiver_write_location        : 0/1A000140
+          receiver_flush_location        : 0/1A000140
+          receiver_replay_location       : 0/1A000140
+          sync_percent                   : 100%
+          sync_state                     : Sync
+          sync_priority                  : 1
+          sync_most_available            : Off
+          channel                        : 172.16.0.106:26001-->172.16.0.245:34586
+
+   Receiver info:
+  No information
+  ```
+
+- 备库
+
+  ```bash
+  gs_ctl query -D /opt/mogdb/data
+  [2021-06-13 08:37:09.128][147065][][gs_ctl]: gs_ctl query ,datadir is /opt/mogdb/data
+   HA state:
+          local_role                     : Standby
+          static_connections             : 2
+          db_state                       : Normal
+          detail_information             : Normal
+
+   Senders info:
+          sender_pid                     : 147043
+          local_role                     : Standby
+          peer_role                      : Cascade Standby
+          peer_state                     : Normal
+          state                          : Streaming
+          sender_sent_location           : 0/1A000140
+          sender_write_location          : 0/1A000140
+          sender_flush_location          : 0/1A000140
+          sender_replay_location         : 0/1A000140
+          receiver_received_location     : 0/1A000140
+          receiver_write_location        : 0/1A000140
+          receiver_flush_location        : 0/1A000140
+          receiver_replay_location       : 0/1A000140
+          sync_percent                   : 100%
+          sync_state                     : Async
+          sync_priority                  : 0
+          sync_most_available            : Off
+          channel                        : 172.16.0.245:26001-->172.16.0.127:49110
+
+   Receiver info:
+          receiver_pid                   : 146771
+          local_role                     : Standby
+          peer_role                      : Primary
+          peer_state                     : Normal
+          state                          : Normal
+          sender_sent_location           : 0/1A000140
+          sender_write_location          : 0/1A000140
+          sender_flush_location          : 0/1A000140
+          sender_replay_location         : 0/1A000140
+          receiver_received_location     : 0/1A000140
+          receiver_write_location        : 0/1A000140
+          receiver_flush_location        : 0/1A000140
+          receiver_replay_location       : 0/1A000140
+          sync_percent                   : 100%
+          channel                        : 172.16.0.245:34586<--172.16.0.106:26001
+  ```
+
+- 级联库
+
+  ```bash
+  gs_ctl query -D /opt/mogdb/data
+  [2021-06-13 08:36:56.223][273241][][gs_ctl]: gs_ctl query ,datadir is /opt/mogdb/data
+   HA state:
+          local_role                     : Cascade Standby
+          static_connections             : 2
+          db_state                       : Normal
+          detail_information             : Normal
+
+   Senders info:
+  No information
+   Receiver info:
+          receiver_pid                   : 273237
+          local_role                     : Cascade Standby
+          peer_role                      : Standby
+          peer_state                     : Normal
+          state                          : Normal
+          sender_sent_location           : 0/1A000140
+          sender_write_location          : 0/1A000140
+          sender_flush_location          : 0/1A000140
+          sender_replay_location         : 0/1A000140
+          receiver_received_location     : 0/1A000140
+          receiver_write_location        : 0/1A000140
+          receiver_flush_location        : 0/1A000140
+          receiver_replay_location       : 0/1A000140
+          sync_percent                   : 100%
+          channel                        : 172.16.0.127:49110<--172.16.0.245:26001
+  ```
+
+**至此主备级联安装完成**
diff --git a/product/zh/docs-mogdb/v3.0/installation-guide/simplified-installation-process/1-installation-preparation.md b/product/zh/docs-mogdb/v3.0/installation-guide/simplified-installation-process/1-installation-preparation.md
new file mode 100644
index 0000000000000000000000000000000000000000..a9673a0ca6150adb27a341845ac5185a7ff19270
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/installation-guide/simplified-installation-process/1-installation-preparation.md
@@ -0,0 +1,297 @@
+---
+title: 安装准备
+summary: 安装准备
+author: Zhang Cuiping
+date: 2021-06-11
+---
+
+# 安装准备
+
+本章详细介绍MogDB极简安装的环境准备和配置，极简安装包括单节点安装和一主一备节点安装，请在安装之前仔细阅读本章的内容。如果已完成本章节的配置，请忽略。
+
+## 获取安装包
+
+云和恩墨MogDB网站下载页面提供了安装包的获取方式。
+
+安装包下载链接：<https://www.mogdb.io/downloads/mogdb>
+
+**操作步骤**
+
+本节以openEuler系统为例描述如何获取安装包。
+
+1. 上传下载好的标准安装包，并解压以获得极简安装包。
+
+   ```bash
+   tar -xvf MogDB-x.x.x-openEuler-arm_64.tar
+   ```
+
+   > 说明：
+   >
+   > + 网站上提供标准安装包MogDB-x.x.x-openEuler-arm_64.tar，解压标准安装包后得到的MogDB-x.x.x-openEuler-64bit.tar.bz2即为极简安装包。
+   >
+   > + 在允许访问外网的环境中可通过wget命令直接下载标准安装包：
+   >
+   >   ```bash
+   >   wget -c https://cdn-mogdb.enmotech.com/mogdb-media/2.1.1/MogDB-2.1.1-openEuler-arm_64.tar
+   >   ```
+   >
+   >   然后执行tar命令解压即可。
+
+2. 检查安装包。
+
+   解压安装包，检查安装目录及文件是否齐全。在安装包所在目录执行以下命令：
+
+   ```bash
+   tar -jxf MogDB-x.x.x-openEuler-64bit.tar.bz2
+   ls -1b
+   ```
+
+   执行ls命令，显示类似如下信息：
+
+   ```bash
+   total 90296
+   drwx------ 3 root root     4096 Mar 31 21:18 bin
+   drwx------ 3 root root     4096 Mar 31 21:18 etc
+   drwx------ 3 root root     4096 Mar 31 21:18 include
+   drwx------ 4 root root     4096 Mar 31 21:18 jre
+   drwx------ 5 root root     4096 Mar 31 21:18 lib
+   -rw------- 1 root root 92427499 Apr  1 09:43 MogDB-x.x.x-openEuler-64bit.tar.bz2
+   drwx------ 5 root root     4096 Mar 31 21:18 share
+   drwx------ 2 root root     4096 Mar 31 21:18 simpleInstall
+   -rw------- 1 root root       32 Mar 31 21:18 version.cfg
+   ```
+
+<br/>
+
+## 软硬件环境要求
+
+介绍MogDB的软硬件环境要求。建议部署MogDB的各服务器具有等价的软硬件配置。
+
+### 硬件环境要求
+
+表1 硬件环境要求列出了MogDB服务器应具备的最低硬件要求。在实际产品中，硬件配置的规划需考虑数据规模及所期望的数据库响应速度。请根据实际情况进行规划。
+
+**表 1** 硬件环境要求 <a id="yingjianhuanjing"> </a>
+
+| 项目     | 配置描述                                                     |
+| :------- | :----------------------------------------------------------- |
+| 内存     | 功能调试建议32GB以上。<br />性能测试和商业部署时，单实例部署建议128GB以上。<br />复杂的查询对内存的需求量比较高，在高并发场景下，可能出现内存不足。此时建议使用大内存的机器，或使用负载管理限制系统的并发。 |
+| CPU      | 功能调试最小1×8 核 2.0GHz。<br />性能测试和商业部署时，建议1×16核 2.0GHz。<br />CPU超线程和非超线程两种模式都支持。<br />说明：<br />个人开发者最低配置2核4G，推荐配置4核8G。<br />目前，MogDB支持鲲鹏920处理器，海光3000、5000、7000系列处理器，兆芯KH30000、KH20000、ZX-C+系列处理器和基于X86_64通用PC服务器的CPU。 |
+| 硬盘     | 用于安装MogDB的硬盘需最少满足如下要求：<br />- 至少1GB用于安装MogDB的应用程序。<br />- 每个主机需大约300MB用于元数据存储。<br />- 预留70%以上的磁盘剩余空间用于数据存储。<br />建议系统盘配置为Raid1，数据盘配置为Raid5，且规划4组Raid5数据盘用于安装MogDB。有关Raid的配置方法在本手册中不做介绍。请参考硬件厂家的手册或互联网上的方法进行配置，其中Disk Cache Policy一项需要设置为Disabled，否则机器异常掉电后有数据丢失的风险。<br />MogDB支持使用SSD盘作为数据库的主存储设备，支持SAS接口和NVME协议的SSD盘，以RAID的方式部署使用。 |
+| 网络要求 | 300兆以上以太网。<br />建议网卡设置为双网卡冗余bond。有关网卡冗余bond的配置方法在本手册中不做介绍。请参考硬件厂商的手册或互联网上的方法进行配置。 |
+
+### 软件环境要求
+
+**表 2** 软件环境要求
+
+| 软件类型      | 配置描述                                                     |
+| :------------ | :----------------------------------------------------------- |
+| rdtscp指令集（x86）  | 执行`lscpu \| grep rdtscp`命令查看是否支持rdtscp指令集。                        |
+| bmi2指令集（CentOS）  | 执行`lscpu \| grep bmi2`命令查看是否支持bmi2指令集。                        |
+| 工具          | bzip2                                                        |
+
+### 操作系统要求
+
+本版本支持以下操作系统及CPU架构组合：
+
+**表 3** 操作系统要求
+
+| 操作系统            | x86                    | ARM    |
+| ------------------- | ---------------------- | ------ |
+| CentOS 7.x          | Intel，AMD，海光，兆芯 | 适配中 |
+| Redhat 7.x          | Intel，AMD，海光，兆芯 | 适配中 |
+| openEuler 20.03     | Intel，AMD，海光，兆芯 | 鲲鹏   |
+| 银河麒麟V10         | Intel，AMD，海光，兆芯 | 鲲鹏   |
+| 统信UOS V20-D/V20-E | Intel，AMD，海光，兆芯 | 鲲鹏   |
+| 统信UOS V20-A       | Intel，AMD，海光，兆芯 | 适配中 |
+
+### 软件依赖要求
+
+MogDB的软件依赖要求如表4 软件依赖要求所示。
+
+建议使用上述操作系统安装光盘或者源中，下列依赖软件的默认安装包，若不存在下列软件，可参看软件对应的建议版本。
+
+**表 4** 软件依赖要求
+
+| 所需软件                      | 建议版本                  |
+| :---------------------------- | :------------------------ |
+| libaio-devel                  | 建议版本：0.3.109-13      |
+| flex                          | 要求版本：2.5.31 以上     |
+| bison                         | 建议版本：2.7-4           |
+| ncurses-devel                 | 建议版本：5.9-13.20130511 |
+| glibc-devel                   | 建议版本：2.17-111        |
+| patch                         | 建议版本：2.7.1-10        |
+| redhat-lsb-core               | 建议版本：4.1             |
+| readline-devel                | 建议版本：7.0-13          |
+| libnsl（openeuler+x86环境中） | 建议版本 ：2.28-36        |
+| openSSH                       | 建议版本 ：8.4p1          |
+
+<br/>
+
+## 配置操作系统
+
+### 关闭操作系统防火墙
+
+为了在防火墙开启的状态下，确保MogDB的正常使用。用户需要将同MogDB相关的服务、协议、IP以及端口添加到MogDB主机的防火墙白名单中。
+
+以openEuler操作系统为例，假设MogDB信息如表 5所示。
+
+**表 5** MogDB信息
+
+| 主机名称 | 内部IP       | 外部IP       |
+| :------- | :----------- | :----------- |
+| plat1    | 192.168.0.11 | 10.10.0.11   |
+| 管理网络 | -            | 10.10.64.236 |
+
+目前仅支持在防火墙关闭的状态下进行安装。
+
+1. 修改SELinux运行模式，临时关闭防火墙。
+
+   ```bash
+    setenforce 0
+   ```
+
+2. 修改/etc/selinux/config文件中的“SELINUX“值为“disabled“。
+
+   a. 使用VIM打开config文件。
+
+    ```bash
+    vim /etc/selinux/config
+    ```
+
+   b. 修改“SELINUX“的值“disabled“，执行**:wq**保存并退出修改。
+
+   ```bash
+   SELINUX=disabled
+   ```
+
+3. （可选）重新启动操作系统。
+
+   ```bash
+   reboot
+   ```
+
+   以下步骤为永久性关闭防火墙。
+
+4. 检查防火墙是否关闭。
+
+   ```bash
+   systemctl status firewalld
+   ```
+
+   若防火墙状态显示为active (running)，则表示防火墙未关闭，请执行[5](#5)；
+
+   若防火墙状态显示为inactive (dead)，则无需再关闭防火墙。
+
+5. 关闭防火墙。 <a id="5"></a>
+
+   ```bash
+   systemctl disable firewalld.service
+   systemctl stop firewalld.service
+   ```
+
+6. 在其他主机上重复步骤1到步骤5。
+
+### 设置字符集参数
+
+将各数据库节点的字符集设置为相同的字符集，可以在/etc/profile文件中添加“export LANG=XXX”（XXX为Unicode编码）。
+
+```bash
+vim /etc/profile
+```
+
+### 设置时区和时间
+
+在各数据库节点上，确保时区和时间一致。
+
+1. 执行如下命令检查各数据库节点时间和时区是否一致。如果各数据库节点时间和时区不一致区，请执行[步骤2](#2)~[步骤3](#3)。
+
+   ```bash
+   date
+   ```
+
+2. 使用如下命令将各数据库节点/usr/share/zoneinfo/目录下的时区文件拷贝为/etc/localtime文件。 <a id="2"></a>
+
+   ```bash
+   cp /usr/share/zoneinfo/$地区/$时区 /etc/localtime
+   ```
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+    > `$地区/$时区`为需要设置时区的信息，例如：Asia/Shanghai。
+
+3. 使用**date -s**命令将各数据库节点的时间设置为统一时间，举例如下。<a id="3"></a>
+
+   ```bash
+   date -s "Sat Sep 27 16:00:07 CST 2020"
+   ```
+
+### (可选）关闭swap交换内存
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+> 关闭swap交换内存是为了保障数据库的访问性能，避免把数据库的缓冲区内存淘汰到磁盘上。 如果服务器内存比较小，内存过载时，可打开swap交换内存保障正常运行。
+
+在各数据库节点上，使用swapoff -a命令将交换内存关闭。
+
+```bash
+swapoff -a
+```
+
+### 关闭RemoveIPC
+
+在各数据库节点上，关闭RemoveIPC。CentOS操作系统默认为关闭，可以跳过该步骤。
+
+1. 修改/etc/systemd/logind.conf文件中的“RemoveIPC“值为“no“。 <a id="buzhou1"></a>
+
+   a. 使用VIM打开logind.conf文件。
+
+   ```bash
+   vim  /etc/systemd/logind.conf
+   ```
+
+   b. 修改“RemoveIPC“的值“no“。
+
+   ```bash
+   RemoveIPC=no
+   ```
+
+2. 修改/usr/lib/systemd/system/systemd-logind.service文件中的“RemoveIPC“值为“no“。
+
+   a. 使用VIM打开systemd-logind.service文件。
+
+   ```bash
+   vim /usr/lib/systemd/system/systemd-logind.service
+   ```
+
+   b. 修改“RemoveIPC“的值“no“。
+
+   ```bash
+   RemoveIPC=no
+   ```
+
+3. 重新加载配置参数。
+
+   ```bash
+   systemctl daemon-reload
+   systemctl restart systemd-logind
+   ```
+
+4. 检查修改是否生效。
+
+   ```bash
+   loginctl show-session | grep RemoveIPC
+   systemctl show systemd-logind | grep RemoveIPC
+   ```
+
+5. 分别打开limits.conf和sysctl.conf配置文件，增加如下对应内容。<a id="buzhou5"></a>
+
+   ```bash
+   vim /etc/security/limits.conf
+   #limits.conf配置文件增加如下内容：
+   omm            soft    nofile          1000000
+   omm            hard    nofile          1000000
+   vim /etc/sysctl.conf
+   #sysctl.conf配置文件增加如下内容：
+   kernel.sem = 250 32000 100 999
+   ```
+
+6. 在其他主机上重复[步骤1](#buzhou1)到[步骤5](#buzhou5)。
diff --git a/product/zh/docs-mogdb/v3.0/installation-guide/simplified-installation-process/2-installation-on-a-single-node.md b/product/zh/docs-mogdb/v3.0/installation-guide/simplified-installation-process/2-installation-on-a-single-node.md
new file mode 100644
index 0000000000000000000000000000000000000000..08acecda1e58e0c41927daad9a4e8b3a712be41d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/installation-guide/simplified-installation-process/2-installation-on-a-single-node.md
@@ -0,0 +1,96 @@
+---
+title: 单节点安装
+summary: 单节点安装
+author: Zhang Cuiping
+date: 2021-06-11
+---
+
+# 单节点安装
+
+本节以openEuler系统为例描述如何安装单节点。
+
+1. 创建相关目录、用户、组，并授权。
+
+   ```
+   groupadd dbgrp -g 2000
+   useradd omm -g 2000 -u 2000
+   mkdir -p /opt/software/mogdb
+   chown -R omm:dbgrp /opt/software/mogdb
+   ```
+
+2. 解压极简版安装包到安装目录。
+
+   ```
+   su - omm
+   cd /opt/software/mogdb/
+   tar -jxf MogDB-x.x.x-openEuler-64bit.tar.bz2 -C /opt/software/mogdb/
+   ```
+
+3. 进入解压后目录下的simpleInstall。
+
+   ```
+   cd /opt/software/mogdb/simpleInstall
+   ```
+
+4. 执行install.sh脚本安装MogDB。
+
+   ```
+   sh install.sh  -w xxxx
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+   >
+   > - -w：初始化数据库密码（gs_initdb指定）,安全需要必须设置。密码应包括大小写、字符、数字。
+   > - -p：指定的MogDB端口号, 如不指定，默认为5432。
+   > - -h|-help 打印使用说明。
+   > - 安装后，数据库的名称为sgnode。
+   > - 安装后，数据库目录安装路径/opt/software/mogdb/data/single_node，其中/opt/software/mogdb为解压包路径，data/single_node为新创建的数据库节点目录。
+
+5. 安装执行完成后，使用ps和gs_ctl查看进程是否正常。
+
+   ```
+   ps ux | grep mogdb
+   gs_ctl query -D /opt/software/mogdb/data/single_node
+   ```
+
+   执行ps命令，显示类似如下信息：
+
+   ```
+   omm      24209 11.9  1.0 1852000 355816 pts/0  Sl   01:54   0:33 /opt/software/mogdb/bin/mogdb -D /opt/software/mogdb/single_node
+   omm      20377  0.0  0.0 119880  1216 pts/0    S+   15:37   0:00 grep --color=auto mogdb
+   ```
+
+   执行gs_ctl命令，显示类似如下信息：
+
+   ```
+   gs_ctl query ,datadir is /opt/software/mogdb/data/single_node
+   HA state:
+       local_role                     : Normal
+       static_connections             : 0
+       db_state                       : Normal
+       detail_information             : Normal
+   
+   Senders info:
+       No information
+   
+    Receiver info:
+   No information
+   ```
+
+6. 使用数据库
+
+   ```
+   -- 配置PATH
+   echo "PATH=/opt/software/mogdb/bin:\$PATH" >> /home/omm/.bash_profile
+   source ~/.bash_profile
+   -bash: ulimit: open files: cannot modify limit: Operation not permitted
+   （默认设置fd可用大小超过系统设置，可以忽略该设置）
+
+   -- 登录数据库
+   gsql -d postgres -p 5432 -r
+   gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+   Non-SSL connection (SSL connection is recommended when requiring high-security)
+   Type "help" for help.
+
+   MogDB=#
+   ```
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/installation-guide/simplified-installation-process/3-installation-on-primary-standby-nodes.md b/product/zh/docs-mogdb/v3.0/installation-guide/simplified-installation-process/3-installation-on-primary-standby-nodes.md
new file mode 100644
index 0000000000000000000000000000000000000000..8e1cfd59b1184ed82f9d0d04f4b627959660587b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/installation-guide/simplified-installation-process/3-installation-on-primary-standby-nodes.md
@@ -0,0 +1,115 @@
+---
+title: 一主一备节点安装
+summary: 一主一备节点安装
+author: Zhang Cuiping
+date: 2021-06-11
+---
+
+# 一主一备节点安装
+
+本节以openEuler系统为例描述如何安装一主一备节点。
+
+1. 创建相关目录、用户、组，并授权。
+
+   ```
+   groupadd dbgrp -g 2000
+   useradd omm -g 2000 -u 2000
+   mkdir -p /opt/software/mogdb
+   chown -R omm:dbgrp /opt/software/mogdb
+   ```
+
+2. 解压MogDB压缩包到安装目录。
+
+   ```
+   su - omm
+   cd /opt/software/mogdb/
+   tar -jxf MogDB-x.x.x-openEuler-64bit.tar.bz2 -C /opt/software/mogdb/
+   ```
+
+3. 进入解压后目录下的simpleInstall。
+
+   ```
+   cd /opt/software/mogdb/simpleInstall
+   ```
+
+4. 执行install.sh脚本安装MogDB。
+
+   ```
+   sh install.sh  -w xxxx  --multinode
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+   >
+   > - -w：初始化数据库密码（gs_initdb指定），安全需要必须设置。 密码应包括大小写、字符、数字。
+   > - -p：指定的MogDB主节点端口号，默认5432。备节点端口号会使用主端口号+200，默认5632。
+   > - -multinode: 用来区分是单节点还是一主一备安装。
+   > - -h|-help 打印使用说明。
+   > - 安装后，数据库的主节点名称为nodename1，备节点名称为nodename2。
+   > - 安装后，数据库主节点目录安装路径/opt/software/mogdb/data/master，备节点目录安装路径为/opt/software/mogdb/data/slave，其中/opt/software/mogdb为解压包路径，data/master(slave)为新创建的数据库节点目录。
+
+5. 安装执行完成后，使用ps和gs_ctl查看进程是否正常。
+
+   ```
+   ps ux | grep mogdb
+   gs_ctl query -D /opt/software/mogdb/data/master
+   ```
+
+   执行ps命令，显示类似如下信息：
+
+   ```
+   omm  4879 11.8 1.1 2082452 373832 pts/0  Sl   14:26   8:29 /opt/software/mogdb/bin/mogdb -D /opt/software/mogdb/data/master -M primary
+   omm  5083  1.1  0.9 1819988 327200 pts/0  Sl   14:26   0:49 /opt/software/mogdb/bin/mogdb -D /opt/software/mogdb/data/slave -M standby
+   omm      20377  0.0  0.0 119880  1216 pts/0    S+   15:37   0:00 grep --color=auto mogdb
+   ```
+   
+   执行gs_ctl命令，显示类似如下信息：
+
+   ```
+   gs_ctl query ,datadir is /opt/software/mogdb/data/master
+   HA state:
+       local_role                     : Primary
+       static_connections             : 1
+       db_state                       : Normal
+       detail_information             : Normal
+   
+   Senders info:
+       sender_pid                     : 5165
+       local_role                     : Primary
+       peer_role                      : Standby
+       peer_state                     : Normal
+       state                          : Streaming
+       sender_sent_location           : 0/4005148
+       sender_write_location          : 0/4005148
+       sender_flush_location          : 0/4005148
+       sender_replay_location         : 0/4005148
+       receiver_received_location     : 0/4005148
+       receiver_write_location        : 0/4005148
+       receiver_flush_location        : 0/4005148
+       receiver_replay_location       : 0/4005148
+       sync_percent                   : 100%
+       sync_state                     : Sync
+       sync_priority                  : 1
+       sync_most_available            : Off
+       channel                        : 10.244.44.52:27001-->10.244.44.52:35912
+   
+    Receiver info:
+   No information
+   ```
+
+6. 使用数据库
+
+   ```
+   -- 配置PATH
+   echo "PATH=/opt/software/mogdb/bin:\$PATH" >> /home/omm/.bash_profile
+   source ~/.bash_profile
+   -bash: ulimit: open files: cannot modify limit: Operation not permitted
+   （默认设置fd可用大小超过系统设置，可以忽略该设置）
+
+   -- 登录数据库
+   gsql -d postgres -p 5432 -r
+   gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+   Non-SSL connection (SSL connection is recommended when requiring high-security)
+   Type "help" for help.
+
+   MogDB=#
+   ```
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/installation-guide/standard-installation/1-installation-overview.md b/product/zh/docs-mogdb/v3.0/installation-guide/standard-installation/1-installation-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..3146d3e8928f849df89c8e5fefe7028d6c98040b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/installation-guide/standard-installation/1-installation-overview.md
@@ -0,0 +1,10 @@
+---
+title: 安装概述
+summary: 安装概述
+author: Zhang Cuiping
+date: 2021-04-02
+---
+
+# 安装概述
+
+MogDB支持单机部署和单机HA部署两种部署方式。单机部署时，可在一个主机部署多个数据库实例，但为了数据安全，不建议用户这样部署。单机HA部署支持一台主机和最少一台备机，最多可配置8台备机。
diff --git a/product/zh/docs-mogdb/v3.0/installation-guide/standard-installation/2-environment-requirement.md b/product/zh/docs-mogdb/v3.0/installation-guide/standard-installation/2-environment-requirement.md
new file mode 100644
index 0000000000000000000000000000000000000000..45a6583f927548c3c6df2dd4b6ca9ac765c82ace
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/installation-guide/standard-installation/2-environment-requirement.md
@@ -0,0 +1,58 @@
+---
+title: 环境要求
+summary: 环境要求
+author: Zhang Cuiping
+date: 2021-04-2
+---
+
+# 环境要求
+
+## 硬件环境要求
+
+下表列出了MogDB服务器应具备的最低硬件要求。在实际产品中，硬件配置的规划需考虑数据规模及所期望的数据库响应速度。请根据实际情况进行规划。
+
+| 项目     | 配置描述                                                     |
+| -------- | ------------------------------------------------------------ |
+| 最小内存 | 功能调试32GB以上。 <br />性能测试和商业部署时，单实例部署建议128GB以上。  <br />复杂的查询对内存的需求量比较高，在高并发场景下，可能出现内存不足。此时建议使用大内存的机器，或使用负载管理限制系统的并发。 |
+| CPU      | 功能调试最小1×8 核 2.0GHz。  <br />性能测试和商业部署时，单实例部署建议1×16核 2.0GHz。  <br />CPU超线程和非超线程两种模式都支持。但是，MogDB各节点的设置需保持一致。 |
+| 硬盘     | 用于安装MogDB的硬盘需最少满足如下要求： <br />- 至少1GB用于安装MogDB的应用程序包。  <br />- 每个主机需大约300MB用于元数据存储。  <br />- 预留70%以上的磁盘剩余空间用于数据存储。  <br />建议系统盘配置为Raid1，数据盘配置为Raid5，且规划4组Raid5数据盘用于安装MogDB。有关Raid的配置方法在本手册中不做介绍。请参考硬件厂家的手册或互联网上的方法进行配置，其中Disk Cache Policy一项需要设置为Disabled，否则机器异常掉电后有数据丢失的风险。 <br />MogDB支持使用SSD盘作为数据库的主存储设备，支持SAS接口和NVME协议的SSD盘，以RAID的方式部署使用。 |
+| 网络要求 | 300兆以上以太网。  <br />建议网卡设置为双网卡冗余bond。有关网卡冗余bond的配置方法在本手册中不做介绍。请参考硬件厂商的手册或互联网上的方法进行配置。<br />MogDB网络如果配置bond，请保证bond模式一致，不一致的bond配置可能导致MogDB工作异常。 |
+
+## 软件环境要求
+
+| 软件类型      | 配置描述                                                     |
+| ------------- | ------------------------------------------------------------ |
+| rdtscp指令集（x86）  | 执行`lscpu \| grep rdtscp`命令查看是否支持rdtscp指令集。                       |
+| bmi2指令集（CentOS）  | 执行`lscpu \| grep bmi2`命令查看是否支持bmi2指令集。                       |
+| 工具          | Huawei JDK 1.8.0、psmisc、bzip2                              |
+| Python        | - openEuler：支持Python 3.7.X  <br />- CentOS：支持Python 3.6.X<br />- 麒麟：支持Python 3.7.X<br />  说明：<br />  python需要通过-enable-shared方式编译。 |
+
+## 操作系统要求
+
+| 操作系统            | x86                    | ARM    |
+| ------------------- | ---------------------- | ------ |
+| CentOS 7.x          | Intel，AMD，海光，兆芯 | 适配中 |
+| Redhat 7.x          | Intel，AMD，海光，兆芯 | 适配中 |
+| openEuler 20.03     | Intel，AMD，海光，兆芯 | 鲲鹏   |
+| 银河麒麟V10         | Intel，AMD，海光，兆芯 | 鲲鹏   |
+| 统信UOS V20-D/V20-E | Intel，AMD，海光，兆芯 | 鲲鹏   |
+| 统信UOS V20-A       | Intel，AMD，海光，兆芯 | 适配中 |
+
+## 软件依赖要求
+
+建议使用上述操作系统安装光盘或者源中，下列依赖软件的默认安装包，若不存在下列软件，可查看软件对应的建议版本。
+
+| 所需软件                      | 建议版本                  |
+| :---------------------------- | :------------------------ |
+| libaio-devel                  | 建议版本：0.3.109-13      |
+| flex                          | 要求版本：2.5.31 以上     |
+| bison                         | 建议版本：2.7-4           |
+| ncurses-devel                 | 建议版本：5.9-13.20130511 |
+| glibc-devel                   | 建议版本：2.17-111        |
+| patch                         | 建议版本：2.7.1-10        |
+| redhat-lsb-core               | 建议版本：4.1             |
+| readline-devel                | 建议版本：7.0-13          |
+| libnsl（openEuler+x86环境中） | 建议版本：2.28-36         |
+| openSSH                       | 建议版本 ：8.4p1          |
+
+注：实际测试4G内存也能安装（需要修改配置文件内存参数），4G以上内存不需要修改。
diff --git a/product/zh/docs-mogdb/v3.0/installation-guide/standard-installation/3-modifying-os-configuration.md b/product/zh/docs-mogdb/v3.0/installation-guide/standard-installation/3-modifying-os-configuration.md
new file mode 100644
index 0000000000000000000000000000000000000000..9749e9439ef63e77feabb98c71cf8dace1c54dda
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/installation-guide/standard-installation/3-modifying-os-configuration.md
@@ -0,0 +1,244 @@
+---
+title: 修改操作系统配置
+summary: 修改操作系统配置
+author: Zhang Cuiping
+date: 2021-04-2
+---
+
+# 修改操作系统配置
+
+## 关闭操作系统防火墙
+
+为了在防火墙开启的状态下，确保MogDB的正常使用。用户需要将同MogDB相关的服务、协议、IP以及端口添加到MogDB各主机的防火墙白名单中。
+
+以openEuler操作系统为例，假设MogDB信息如[表1 MogDB信息](#mogdb)所示。
+
+**表 1** MogDB信息 <a id="mogdb"></a>
+
+| 主机名称 | 内部IP       | 外部IP       |
+| :------- | :----------- | :----------- |
+| plat1    | 192.168.0.11 | 10.10.0.11   |
+| plat2    | 192.168.0.12 | 10.10.0.12   |
+| plat3    | 192.168.0.13 | 10.10.0.13   |
+| plat4    | 192.168.0.14 | 10.10.0.14   |
+| 管理网络 | -            | 10.10.64.236 |
+
+**操作步骤**
+
+目前仅支持在防火墙关闭的状态下进行安装。
+
+1. 修改/etc/selinux/config文件中的“SELINUX”值为“disabled”。<a id="1"> </a>
+
+   a. 使用VIM打开config文件。
+
+   ```
+   vim /etc/selinux/config
+   ```
+
+   b. 修改“SELINUX”的值“disabled”，执行:wq保存并退出修改。
+
+   ```
+   SELINUX=disabled
+   ```
+
+2. 重新启动操作系统。
+
+   ```
+   reboot
+   ```
+
+3. 检查防火墙是否关闭。
+
+   ```
+   systemctl status firewalld
+   ```
+
+   若防火墙状态显示为active (running)，则表示防火墙未关闭，请执行步骤[4](#4)；
+
+   若防火墙状态显示为inactive (dead)，则无需再关闭防火墙。
+
+4. 关闭防火墙并禁止开机重启。<a id="4"> </a>
+
+   ```
+   systemctl disable firewalld.service
+   systemctl stop firewalld.service
+   ```
+
+5. 在其他主机上重复步骤[1](#1)到步骤[4](#4)。
+
+## 设置字符集参数
+
+将各数据库节点的字符集设置为相同的字符集，可以在/etc/profile文件中添加“export LANG=XXX”（XXX为Unicode编码）。
+
+```
+vim /etc/profile
+```
+
+## 设置时区和时间
+
+将各数据库节点的时区设置为相同时区，可以将/usr/share/zoneinfo/目录下的时区文件拷贝为/etc/localtime文件。
+
+```
+cp /usr/share/zoneinfo/$地区/$时区 /etc/localtime
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+> `$地区/$时区`为需要设置时区的信息，例如：Asia/Shanghai。
+
+使用date -s命令将各主机的时间设置为统一时间，举例如下。
+
+```
+date -s "Sat Sep 27 16:00:07 CST 2020"
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+> 可以通过date命令查询主机时区。
+
+## （可选）关闭swap交换内存
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+> 关闭swap交换内存是为了保障数据库的访问性能，避免把数据库的缓冲区内存淘汰到磁盘上。 如果服务器内存比较小，内存过载时，可打开swap交换内存保障正常运行。
+
+在各数据库节点上，使用swapoff -a命令将交换内存关闭。
+
+```
+swapoff -a
+```
+
+## 设置网卡MTU值
+
+将各数据库节点的网卡MTU值设置为相同大小。对于x86，MTU值推荐1500；对于ARM，MTU值推荐8192。
+
+```
+ifconfig 网卡编号 mtu 值
+```
+
+## 关闭RemoveIPC
+
+在各数据库节点上，关闭RemoveIPC。CentOS操作系统无该参数，可以跳过该步骤。
+
+**操作步骤**
+
+1. 修改/etc/systemd/logind.conf文件中的“RemoveIPC”值为“no”。<a id="01"> </a>
+
+   a. 使用VIM打开logind.conf文件。
+
+   ```
+   vim  /etc/systemd/logind.conf
+   ```
+
+   b. 修改“RemoveIPC”值为“no”。
+
+   ```
+   RemoveIPC=no
+   ```
+
+2. 修改/usr/lib/systemd/system/systemd-logind.service文件中的“RemoveIPC”值为“no”。
+
+   a. 使用VIM打开systemd-logind.service文件。
+
+   ```
+   vim /usr/lib/systemd/system/systemd-logind.service
+   ```
+
+   b. 修改“RemoveIPC”值为“no”。
+
+   ```
+   RemoveIPC=no
+   ```
+
+3. 重新加载配置参数。
+
+   ```
+   systemctl daemon-reload
+   systemctl restart systemd-logind
+   ```
+
+4. 检查修改是否生效。<a id="04"> </a>
+
+   ```
+   loginctl show-session | grep RemoveIPC
+   systemctl show systemd-logind | grep RemoveIPC
+   ```
+
+5. 在其他主机上重复步骤[1](#01)到步骤[4](#04)。
+
+## 设置root用户远程登录
+
+在MogDB安装时需要root帐户远程登录访问权限，本章介绍如何设置使用root用户远程登录。
+
+1. 修改PermitRootLogin配置，允许用户远程登录。
+
+   a. 打开sshd_config文件。
+
+   ```
+   vim /etc/ssh/sshd_config
+   ```
+
+   b. 修改权限配置，可以使用以下两种方式实现：
+
+   - 注释掉“PermitRootLogin no”。
+
+     ```
+     #PermitRootLogin no
+     ```
+
+   - 将“PermitRootLogin”改为“yes”。
+
+     ```
+     PermitRootLogin yes
+     ```
+
+   c. 执行**:wq**保存并退出编辑页面。
+
+2. 修改Banner配置，去掉连接到系统时，系统提示的欢迎信息。欢迎信息会干扰安装时远程操作的返回结果，影响安装正常执行。
+
+   a. 编辑sshd_config文件。
+
+   ```
+   vim /etc/ssh/sshd_config
+   ```
+
+   b. 修改Banner配置，注释掉“Banner”所在的行。
+
+   ```
+   #Banner XXXX
+   ```
+
+   c. 执行**:wq**保存并退出编辑页面。
+
+3. 使用如下命令使设置生效。
+
+   ```
+   systemctl restart sshd.service
+   ```
+
+4. 以root用户身份重新登录。
+
+   ```
+   ssh xxx.xxx.xxx.xxx
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+   >
+   > xxx.xxx.xxx.xxx为安装MogDB环境的IP地址。
+
+## 动态关闭使用透明大页
+
+```bash
+echo never > /sys/kernel/mm/transparent_hugepage/enabled
+```
+
+例如 openEuler：
+
+```bash
+/root~ # cat /etc/system-release
+openEuler release 20.03 (LTS)
+/etc/default~ # echo never > /sys/kernel/mm/transparent_hugepage/enabled
+/etc/default~ # cat /sys/kernel/mm/transparent_hugepage/enabled
+always madvise [never]
+```
+
+成功关闭后，显示为 [never]
+
+关闭透明大页可以减少宿主机操作系统的开销，以便获得更稳定的性能。
diff --git a/product/zh/docs-mogdb/v3.0/installation-guide/standard-installation/4-installing-mogdb.md b/product/zh/docs-mogdb/v3.0/installation-guide/standard-installation/4-installing-mogdb.md
new file mode 100644
index 0000000000000000000000000000000000000000..04ef1deb5656d17b22d471bb3c613faa9589c6cd
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/installation-guide/standard-installation/4-installing-mogdb.md
@@ -0,0 +1,491 @@
+---
+title: 安装MogDB
+summary: 安装MogDB
+author: Zhang Cuiping
+date: 2021-04-2
+---
+
+# 安装MogDB
+
+## 创建XML配置文件
+
+安装MogDB前需要创建XML文件。XML文件包含部署MogDB的服务器信息、安装路径、IP地址以及端口号等。用于告知MogDB如何部署。用户需根据不同场配置对应的XML文件。
+
+<br/>
+
+**参数说明**
+
+<table>
+    <tr>
+      <td><b>参数</b></td>
+      <td><b>说明</b></td>
+    </tr>
+    <tr>
+      <td>clusterName</td>
+      <td>MogDB名称。</td>
+    </tr>
+    <tr>
+      <td>nodeNames</td>
+      <td>MogDB中主机名称。</td>
+    </tr>
+    <tr>
+      <td>backIp1s</td>
+      <td>
+        主机在后端存储网络中的IP地址（内网IP）。所有MogDB主机使用后端存储网络通讯。
+      </td>
+    </tr>
+    <tr>
+      <td>gaussdbAppPath</td>
+      <td>
+        MogDB程序安装目录。此目录应满足如下要求：<br />- 磁盘空间&gt;1GB<br />-
+        与数据库所需其它路径相互独立，没有包含关系。
+      </td>
+    </tr>
+    <tr>
+      <td>gaussdbLogPath</td>
+      <td>
+        MogDB运行日志和操作日志存储目录。此目录应满足如下要求：<br />-
+        磁盘空间建议根据主机上的数据库节点数规划。数据库节点预留1GB空间的基础上，再适当预留冗余空间。<br />-
+        与MogDB所需其它路径相互独立，没有包含关系。<br />
+        此路径可选。不指定的情况下，MogDB安装时会默认指定“$GAUSSLOG/安装用户名”作为日志目录。
+      </td>
+    </tr>
+    <tr>
+      <td>tmpdbPath</td>
+      <td>
+        数据库临时文件存放目录。<br />
+        若不配置tmpdbPath，默认存放在/opt/mogdb/tools/perfadm_db目录下。
+      </td>
+    </tr>
+    <tr>
+      <td>gaussdbToolPath</td>
+      <td>
+        MogDB系统工具目录，主要用于存放互信工具等。此目录应满足如下要求：<br />-
+        磁盘空间&gt;100MB <br />-
+        固定目录，与数据库所需其它目录相互独立，没有包含关系。<br />
+        此目录可选。不指定的情况下，MogDB安装时会默认指定“/opt/mogdb/tools”作为数据库系统工具目录。
+      </td>
+    </tr>
+    <tr>
+      <td>corePath</td>
+      <td>MogDB core文件的指定目录。</td>
+    </tr>
+    <tr>
+      <td>clusterType</td>
+      <td>
+        MogDB类型，MogDB拓扑类型；可选字段。<br />
+        “single-inst”表示单机一主多备部署形态。
+      </td>
+    </tr>
+</table>
+
+### 示例
+
+#### 单节点配置文件
+
+```xml
+<?xml version="1.0" encoding="UTF-8"?>
+<ROOT>
+    <!-- MogDB整体信息 -->
+    <CLUSTER>
+        <PARAM name="clusterName" value="dbCluster" />
+        <PARAM name="nodeNames" value="node1" />
+        <PARAM name="backIp1s" value="192.168.0.11"/>
+        <PARAM name="gaussdbAppPath" value="/opt/mogdb/app" />
+        <PARAM name="gaussdbLogPath" value="/var/log/mogdb" />
+        <PARAM name="gaussdbToolPath" value="/opt/mogdb/tools" />
+        <PARAM name="corePath" value="/opt/mogdb/corefile"/>
+        <PARAM name="clusterType" value="single-inst"/>
+    </CLUSTER>
+
+    <!-- 每台服务器上的节点部署信息 -->
+    <DEVICELIST>
+        <!-- node1上的节点部署信息 -->
+        <DEVICE sn="1000001">
+            <PARAM name="name" value="node1"/>
+            <PARAM name="azName" value="AZ1"/>
+            <PARAM name="azPriority" value="1"/>
+            <!-- 如果服务器只有一个网卡可用，将backIP1和sshIP1配置成同一个IP -->
+            <PARAM name="backIp1" value="192.168.0.11"/>
+            <PARAM name="sshIp1" value="192.168.0.11"/>
+
+            <!--dbnode-->
+            <PARAM name="dataNum" value="1"/>
+            <PARAM name="dataPortBase" value="26000"/>
+            <PARAM name="dataNode1" value="/mogdb/data/db1"/>
+        </DEVICE>
+    </DEVICELIST>
+</ROOT>
+```
+
+> 说明：替换主机名和IP，其他参数默认即可。
+
+#### 一主一备配置文件
+
+```xml
+<?xml version="1.0" encoding="UTF-8"?>
+<ROOT>
+    <!-- MogDB整体信息 -->
+    <CLUSTER>
+        <PARAM name="clusterName" value="dbCluster" />
+        <PARAM name="nodeNames" value="node1,node2" />
+        <PARAM name="backIp1s" value="192.168.0.11,192.168.0.12"/>
+        <PARAM name="gaussdbAppPath" value="/opt/mogdb/app" />
+        <PARAM name="gaussdbLogPath" value="/var/log/mogdb" />
+        <PARAM name="gaussdbToolPath" value="/opt/mogdb/tools" />
+        <PARAM name="corePath" value="/opt/mogdb/corefile"/>
+        <PARAM name="clusterType" value="single-inst"/>
+    </CLUSTER>
+    <!-- 每台服务器上的节点部署信息 -->
+    <DEVICELIST>
+        <!-- node1上的节点部署信息 -->
+        <DEVICE sn="1000001">
+            <PARAM name="name" value="node1"/>
+            <PARAM name="azName" value="AZ1"/>
+            <PARAM name="azPriority" value="1"/>
+            <!-- 如果服务器只有一个网卡可用，将backIP1和sshIP1配置成同一个IP -->
+            <PARAM name="backIp1" value="192.168.0.11"/>
+            <PARAM name="sshIp1" value="192.168.0.11"/>
+
+            <!--dbnode-->
+            <PARAM name="dataNum" value="1"/>
+            <PARAM name="dataPortBase" value="26000"/>
+            <PARAM name="dataNode1" value="/mogdb/data/db1,node2,/mogdb/data/db1"/>
+        </DEVICE>
+
+        <!-- node2上的节点部署信息，其中“name”的值配置为主机名称 -->
+        <DEVICE sn="1000002">
+            <PARAM name="name" value="node2"/>
+            <PARAM name="azName" value="AZ1"/>
+            <PARAM name="azPriority" value="1"/>
+            <!-- 如果服务器只有一个网卡可用，将backIP1和sshIP1配置成同一个IP -->
+            <PARAM name="backIp1" value="192.168.0.12"/>
+            <PARAM name="sshIp1" value="192.168.0.12"/>
+        </DEVICE>
+    </DEVICELIST>
+</ROOT>
+```
+
+> 说明：替换主机名和IP，其他参数默认即可。
+
+#### 一主二备配置文件
+
+```xml
+<?xml version="1.0" encoding="UTF-8"?>
+<ROOT>
+    <!-- MogDB整体信息 -->
+    <CLUSTER>
+        <PARAM name="clusterName" value="dbCluster" />
+        <PARAM name="nodeNames" value="node1,node2,node3" />
+        <PARAM name="backIp1s" value="192.168.0.11,192.168.0.12, 192.168.0.13"/>
+        <PARAM name="gaussdbAppPath" value="/opt/mogdb/app" />
+        <PARAM name="gaussdbLogPath" value="/var/log/mogdb" />
+        <PARAM name="gaussdbToolPath" value="/opt/mogdb/tools" />
+        <PARAM name="corePath" value="/opt/mogdb/corefile"/>
+        <PARAM name="clusterType" value="single-inst"/>
+    </CLUSTER>
+    <!-- 每台服务器上的节点部署信息 -->
+    <DEVICELIST>
+        <!-- node1上的节点部署信息 -->
+        <DEVICE sn="1000001">
+            <PARAM name="name" value="node1"/>
+            <PARAM name="azName" value="AZ1"/>
+            <PARAM name="azPriority" value="1"/>
+            <!-- 如果服务器只有一个网卡可用，将backIP1和sshIP1配置成同一个IP -->
+            <PARAM name="backIp1" value="192.168.0.11"/>
+            <PARAM name="sshIp1" value="192.168.0.11"/>
+
+            <!--dbnode-->
+            <PARAM name="dataNum" value="1"/>
+            <PARAM name="dataPortBase" value="26000"/>
+            <PARAM name="dataNode1" value="/mogdb/data/db1,node2,/mogdb/data/db1, node3,/mogdb/data/db1"/>
+        </DEVICE>
+
+        <!-- node2上的节点部署信息，其中“name”的值配置为主机名称 -->
+        <DEVICE sn="1000002">
+            <PARAM name="name" value="node2"/>
+            <PARAM name="azName" value="AZ1"/>
+            <PARAM name="azPriority" value="1"/>
+            <!-- 如果服务器只有一个网卡可用，将backIP1和sshIP1配置成同一个IP -->
+            <PARAM name="backIp1" value="192.168.0.12"/>
+            <PARAM name="sshIp1" value="192.168.0.12"/>
+        </DEVICE>
+        <!--node3上的节点部署信息，其中“name”的值配置为主机名称 -->
+        <DEVICE sn="1000003">
+            <PARAM name="name" value="node3"/>
+            <PARAM name="azName" value="AZ1"/>
+            <PARAM name="azPriority" value="1"/>
+            <!-- 如果服务器只有一个网卡可用，将backIP1和sshIP1配置成同一个IP -->
+            <PARAM name="backIp1" value="192.168.0.13"/>
+            <PARAM name="sshIp1" value="192.168.0.13"/>
+ </DEVICE>
+    </DEVICELIST>
+</ROOT>
+```
+
+> 说明：替换主机名和IP，其他参数默认即可。/mogdb/data/db1为数据存储路径，可根据需要替换。
+
+<br/>
+
+## 下载安装包
+
+安装前可访问[MogDB下载页面](https://www.mogdb.io/downloads/mogdb)下载适用于您当前操作系统和CPU的安装包。以CentOS系统为例，各安装包及功能介绍见下表。
+
+| **安装包**                            | **功能**                                                     |
+| ------------------------------------- | ------------------------------------------------------------ |
+| MogDB-x.x.x-CentOS-x86_64.tar     | 包含所有安装包所有文件                                       |
+| MogDB-x.x.x-CentOS-64bit.tar.bz2      | （主备）MogDB主备（Datanode）。负责存储业务数据、执行数据查询任务以及向客户端返回执行结果。MogDB实例包含主、备两种类型，支持一主多备。建议将主、备MogDB实例分散部署在不同的物理节点中。 |
+| MogDB-x.x.x-CentOS-64bit.sha256       | MogDB-x.x.x-CentOS-64bit.tar.bz2的sha256的hash值             |
+| MogDB-x.x.x-CentOS-64bit-Libpq.tar.gz | C程序访问MogDB数据库的驱动                                     |
+| MogDB-x.x.x-CentOS-64bit-om.tar.gz    | 运维管理模块（Operation  Manager）。提供数据库日常运维、配置管理的管理接口、工具。 |
+| MogDB-x.x.x-CentOS-64bit-om.sha256    | MogDB-x.x.x-CentOS-64bit-om.tar.gz的sha256的hash值           |
+| MogDB-x.x.x-CentOS-64bit-tools.tar.gz | 客户端驱动（Client  Driver）。负责接收来自应用的访问请求，并向应用返回执行结果。客户端驱动负责与MogDB实例通信，发送应用的SQL命令，接收MogDB实例的执行结果 |
+| upgrade_sql.tar.gz                    | 升级所需要的SQL                                              |
+| upgrade_sql.sha256                    | upgrade_sql.tar.gz的sha256的hash值                           |
+
+<br/>
+
+## 环境初始化
+
+下文以CentOS 7.6系统为例介绍安装过程。
+
+**操作步骤**
+
+1. 以root用户执行以下命令安装所需的基础环境包，以避免后续安装过程中因系统采用最小化安装或者安装包不全导致的报错。
+
+   ```
+   yum install -y libaio-devel gcc gcc-c++ zlib-devel
+   ```
+
+2. 以root用户登录待安装MogDB的任意主机，并按规划创建存放安装包的目录，下文以`/opt/software/mogdb`为例。
+
+   ```
+   mkdir -p /opt/software/mogdb
+   chmod 755 -R /opt/software
+   ```
+
+3. 进入`/opt/software/mogdb`，将安装包及配置文件`clusterconfig.xml`上传至此目录。若未创建配置文件，可通过`vi clusterconfig.xml`新建并编辑配置文件。
+
+   ```
+   cd /opt/software/mogdb
+   ```
+
+   > 说明：
+   > 在允许访问外网的环境中，可通过`wget`命令直接下载适用于当前操作系统和CPU的安装包：
+   >
+   > ```
+   > wget -c https://cdn-mogdb.enmotech.com/mogdb-media/2.1.1/MogDB-2.1.1-CentOS-x86_64.tar
+   > ```
+
+4. 在安装包所在的目录下，依次解压安装包。
+
+   ```
+   tar -xvf  MogDB-x.x.x-CentOS-x86_64.tar
+   tar -xvf  MogDB-x.x.x-CentOS-64bit-om.tar.gz
+   ```
+
+5. 进入到工具脚本存放目录下。
+
+   ```
+   cd /opt/software/mogdb/script
+   ```
+
+6. 为确保openssl版本正确，执行预安装前请加载安装包中lib库。执行命令如下，其中`{packagePath}`为用户安装包放置的路径，本示例中为`/opt/software/mogdb`。
+
+   ```
+   export LD_LIBRARY_PATH={packagePath}/script/gspylib/clib:$LD_LIBRARY_PATH
+   ```
+
+7. 为确保成功安装，请执行如下命令检查主机名称是否一致。预安装过程中，会对hostname进行检查。
+
+   ```
+   hostname
+   vi /etc/hostname
+   ```
+
+8. 若您使用的为openEuler系统，需打开`performance.sh`文件注释`#sysctl -w vm.min_free_kbytes=112640 &> /dev/null`
+
+   ```
+   vi /etc/profile.d/performance.sh
+   ```
+
+   完成后跳过第9步即可。
+
+9. CentOS系统需要安装python3，请依次执行以下命令。
+
+   注意：CentOS系统中进行标准安装，请务必安装Python 3.6.x版本，目前不支持Python更高版本。
+
+   ```
+   wget https://www.python.org/ftp/python/3.6.5/Python-3.6.5.tgz
+   mkdir -p /usr/local/python3
+   tar -zxvf Python-3.6.5.tgz
+   cd Python-3.6.5
+   ./configure --prefix=/usr/local/python3 --enable-shared CFLAGS=-fPIC && make && make install
+   ln -s /usr/local/python3/bin/python3 /usr/bin/python3
+   ln -s /usr/local/python3/bin/pip3 /usr/bin/pip3
+   ```
+
+   > 说明：
+   >
+   > - 如遇`zipimport.ZipImportError: can't decompress data; zlib not available`报错，请执行`yum -y install zlib*`安装解压缩类库，之后重新安装。
+   >
+   > - 如遇`find:'/run/user/1000/gvfs':权限不够`的报错，可忽略。
+   >
+
+<br/>
+
+## 初始化脚本
+
+执行以下命令以初始化脚本：
+
+```
+/opt/software/mogdb/script/gs_preinstall -U omm -G dbgrp -X /opt/software/mogdb/clusterconfig.xml
+```
+
+回显如下：
+
+```
+Parsing the configuration file.
+Successfully parsed the configuration file.
+Installing the tools on the local node.
+Successfully installed the tools on the local node.
+Distributing package.
+Begin to distribute package to tool path.
+Successfully distribute package to tool path.
+Begin to distribute package to package path.
+Successfully distribute package to package path.
+Successfully distributed package.
+Installing the tools in the cluster.
+Successfully installed the tools in the cluster.
+Checking hostname mapping.
+Successfully checked hostname mapping.
+Checking OS version.
+Successfully checked OS version.
+Creating cluster's path.
+Successfully created cluster's path.
+Setting SCTP service.
+Successfully set SCTP service.
+Set and check OS parameter.
+Setting OS parameters.
+Successfully set OS parameters.
+Set and check OS parameter completed.
+Preparing CRON service.
+Successfully prepared CRON service.
+Preparing SSH service.
+Successfully prepared SSH service.
+Setting user environmental variables.
+Successfully set user environmental variables.
+Configuring alarms on the cluster nodes.
+Successfully configured alarms on the cluster nodes.
+Setting the dynamic link library.
+Successfully set the dynamic link library.
+Setting Cgroup.
+Successfully set Cgroup.
+Set ARM Optimization.
+Successfully set ARM Optimization.
+Setting finish flag.
+Successfully set finish flag.
+Preinstallation succeeded.
+```
+
+> 说明：
+>
+> - 运行过程中会创建omm用户，输入yes，然后输入相关密码，需保证复杂度要求，密码应包括大小写、字符、数字，例如Enmo@123。
+>
+> - 如遇以下错误，则表示Python版本过高。
+>
+>   ```
+>   [root@localhost mogdb]# /opt/software/mogdb/script/gs_preinstall -U omm -G dbgrp -X /mogdb/etc/mogdb_clusterconfig.xml
+>   Failed to execute cmd: rm -rf '/opt/software/mogdb/script/gspylib/os/./../../../lib/psutil/_psutil_linux.so' && cp -r '/opt/software/mogdb/script/gspylib/os/./../../../lib/psutil/_psutil_linux.so_3.9' '/opt/software/mogdb/script/gspylib/os/./../../../lib/psutil/_psutil_linux.so' && rm -rf '/opt/software/mogdb/script/gspylib/os/./../../../lib/psutil/_psutil_posix.so' && cp -r '/opt/software/mogdb/script/gspylib/os/./../../../lib /psutil/_psutil_posix.so_3.9' '/opt/software/mogdb/script/gspylib/os/./../../../lib/psutil/_psutil_posix.so' . Error:
+>   cp: cannot stat '/opt/software/mogdb/script/gspylib/os/./../../../lib/psutil/_psutil_linux.so_3.9': No such file or directory
+>   ```
+
+<br/>
+
+## 执行安装
+
+修改安装目录下lib及script文件夹的用户以及用户组：
+
+```
+chown -R omm:dbgrp /opt/software/mogdb/lib
+chown -R omm:dbgrp /opt/software/mogdb/script
+```
+
+依次执行以下命令安装MogDB：
+
+```
+su - omm
+/opt/software/mogdb/script/gs_install -X /opt/software/mogdb/clusterconfig.xml --gsinit-parameter="--locale=en_US.UTF-8" --gsinit-parameter="--encoding=UTF-8"
+```
+
+回显如下：
+
+```
+Parsing the configuration file.
+Check preinstall on every node.
+Successfully checked preinstall on every node.
+Creating the backup directory.
+Successfully created the backup directory.
+begin deploy..
+Installing the cluster.
+begin prepare Install Cluster..
+Checking the installation environment on all nodes.
+begin install Cluster..
+Installing applications on all nodes.
+Successfully installed APP.
+begin init Instance..
+encrypt ciper and rand files for database.
+Please enter password for database:
+Please repeat for database:
+begin to create CA cert files
+The sslcert will be generated in /opt/mogdb/cluster/app/share/sslcert/om
+Cluster installation is completed.
+Configuring.
+Deleting instances from all nodes.
+Successfully deleted instances from all nodes.
+Checking node configuration on all nodes.
+Initializing instances on all nodes.
+Updating instance configuration on all nodes.
+Check consistence of memCheck and coresCheck on DN nodes.
+Successful check consistence of memCheck and coresCheck on all nodes.
+Configuring pg_hba on all nodes.
+Configuration is completed.
+Successfully started cluster.
+Successfully installed application.
+```
+
+> 说明：在执行过程中，用户需根据提示输入数据库的密码，密码具有一定的复杂度，为保证用户正常使用该数据库，请记住输入的数据库密码。
+
+<br/>
+
+## 连接数据库
+
+安装完成后，可使用omm用户通过“gsql -d postgres -p 26000 -r”命令连接MogDB数据库，其中“-p 26000”为数据库端口号，请根据实际情况替换。键入“\copyright”可查看版权信息。
+
+```sql
+[omm@ecs-saving-0006 ~]$ gsql -d postgres -p 26000 -r
+gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+Non-SSL connection (SSL connection is recommended when requiring high-security)
+Type "help" for help.
+
+MogDB=# \copyright
+MogDB Kernel Database Management System
+Copyright (c) Yunhe Enmo (Beijing) Information Technology Co., Ltd. Copyright © 2009-2022 , All rights reserved.
+```
+
+<br/>
+
+## 更改同步节点
+
+默认备库为异步，如果想配置同步需在主库做如下配置。
+
+```
+[omm@ecs-saving-0006 ~]$ sed -i "/synchronous_standby_names/csynchronous_standby_names = 'dn_6002'" /mogdb/data/db1/postgresql.conf
+[omm@ecs-saving-0006 ~]$ gs_om -t restart
+```
+
+dn_6002值比较特殊，其值为固定值，主库为dn_6001，备库1为dn_6002，备库2为dn_6003，依次顺延。
+
+'dn_6002,dn_6003'表示备库1，2为同步节点。
+
+请替换相应的数据存储路径。
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/installation-guide/standard-installation/5-verifying-installation.md b/product/zh/docs-mogdb/v3.0/installation-guide/standard-installation/5-verifying-installation.md
new file mode 100644
index 0000000000000000000000000000000000000000..549d0804c4a0c4cc6527303b58fe78441ee4cf92
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/installation-guide/standard-installation/5-verifying-installation.md
@@ -0,0 +1,32 @@
+---
+title: 安装验证
+summary: 安装验证
+author: Zhang Cuiping
+date: 2021-04-2
+---
+
+# 安装验证
+
+通过MogDB提供的gs_om工具可以完成数据库状态检查。
+
+**前提条件**
+
+MogDB数据库已安装。
+
+**操作步骤**
+
+1. 以omm用户身份登录服务器。
+
+2. 执行如下命令检查数据库状态是否正常，"cluster_state "显示"Normal"表示数据库可正常使用。
+
+    ```bash
+    gs_om -t status
+    ```
+
+3. 数据库安装完成后，默认生成名称为postgres的数据库。第一次连接数据库时可以连接到此数据库。
+
+    其中postgres为需要连接的数据库名称，26000为数据库主节点的端口号，即XML配置文件中的dataPortBase的值。请根据实际情况替换。
+
+    ```bash
+    gsql -d postgres -p 26000
+    ```
diff --git a/product/zh/docs-mogdb/v3.0/installation-guide/standard-installation/6-uninstallation.md b/product/zh/docs-mogdb/v3.0/installation-guide/standard-installation/6-uninstallation.md
new file mode 100644
index 0000000000000000000000000000000000000000..da2facee9d8894bf098caf0f43446b6d1ac48b35
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/installation-guide/standard-installation/6-uninstallation.md
@@ -0,0 +1,159 @@
+---
+title: 卸载MogDB
+summary: 卸载MogDB
+author: Zhang Cuiping
+date: 2021-04-2
+---
+
+# 卸载MogDB
+
+卸载MogDB的过程包含卸载MogDB以及清理MogDB服务器环境。
+
+## 执行卸载
+
+MogDB提供了卸载脚本帮助用户完整的卸载MogDB。
+
+**操作步骤**
+
+1. 以操作系统用户omm登录数据库主节点。
+
+2. 使用gs_uninstall卸载MogDB。
+
+    ```
+    gs_uninstall --delete-data
+    ```
+
+    或者在MogDB中每个节点执行本地卸载。
+
+    ```
+    gs_uninstall --delete-data -L
+    ```
+
+**示例**
+
+使用gs_uninstall脚本进行卸载MogDB。
+
+```bash
+gs_uninstall --delete-data
+Checking uninstallation.
+Successfully checked uninstallation.
+Stopping the cluster.
+Successfully stopped the cluster.
+Successfully deleted instances.
+Uninstalling application.
+Successfully uninstalled application.
+Uninstallation succeeded.
+```
+
+单机卸载场景使用gs_uninstall脚本进行卸载。
+
+```bash
+gs_uninstall --delete-data
+Checking uninstallation.
+Successfully checked uninstallation.
+Stopping the cluster.
+Successfully stopped the cluster.
+Successfully deleted instances.
+Uninstalling application.
+Successfully uninstalled application.
+Uninstallation succeeded.
+```
+
+**错误排查**
+
+如果卸载失败请根据"$GAUSSLOG/om/gs_uninstall-YYYY-MM-DD_HHMMSS.log"中的日志信息排查错误。
+
+## 一键式环境清理
+
+在MogDB卸载完成后，如果不需要在环境上重新部署MogDB，可以运行脚本gs_postuninstall对MogDB服务器上环境信息做清理。MogDB环境清理是对环境准备脚本gs_preinstall所做设置的清理。
+
+**前提条件**
+
+- MogDB卸载执行成功。
+- root用户互信可用。
+- 只能使用root用户执行gs_postuninstall命令。
+
+**操作步骤**
+
+1. 以root用户登录MogDB服务器。
+
+2. 查看root用户互信是否建立，如果root用户没有建立互信，需要手工建立root用户互信，操作参考**手工建立互信**。
+
+    查看互信是否建成功，可以互相ssh主机名。输入exit退出。
+
+    ```bash
+    plat1:~ # ssh plat2
+    Last login: Tue Jan  5 10:28:18 2016 from plat1
+    Huawei's internal systems must only be used for conducting Huawei's business or for purposes authorized by Huawei management.Use is subject to audit at any time by Huawei management.
+    plat2:~ # exit
+    logout
+    Connection to plat2 closed.
+    plat1:~ #
+    ```
+
+3. 进入script路径下。
+
+    ```bash
+    cd /opt/software/mogdb/script
+    ```
+
+4. 使用gs_postuninstall进行清理。若为环境变量分离的模式安装的数据库需要source环境变量分离文件ENVFILE。
+
+    ```bash
+    ./gs_postuninstall -U omm -X /opt/software/mogdb/clusterconfig.xml --delete-user --delete-group
+    ```
+
+    或者在MogDB中每个节点执行本地后置清理。
+
+    ```bash
+    ./gs_postuninstall -U omm -X /opt/software/mogdb/clusterconfig.xml --delete-user --delete-group -L
+    ```
+
+    omm为运行MogDB的操作系统用户名，/opt/software/mogdb/clusterconfig.xml为MogDB配置文件路径。
+
+    若为环境变量分离的模式安装的数据库需删除之前source的环境变量分离的env参数。
+
+    ```bash
+    unset MPPDB_ENV_SEPARATE_PATH
+    ```
+
+5. 删除MogDB数据库各节点root用户的互信，操作参考**手工建立互信**的删除root用户互信部分内容。
+
+**示例**
+
+清理主机的环境。
+
+```bash
+gs_postuninstall -U omm -X /opt/software/mogdb/clusterconfig.xml --delete-user
+Parsing the configuration file.
+Successfully parsed the configuration file.
+Check log file path.
+Successfully checked log file path.
+Checking unpreinstallation.
+Successfully checked unpreinstallation.
+Deleting Cgroup.
+Successfully deleted Cgroup.
+Deleting the instance's directory.
+Successfully deleted the instance's directory.
+Deleting the installation directory.
+Successfully deleted the installation directory.
+Deleting the temporary directory.
+Successfully deleted the temporary directory.
+Deleting remote OS user.
+Successfully deleted remote OS user.
+Deleting software packages and environmental variables of other nodes.
+Successfully deleted software packages and environmental variables of other nodes.
+Deleting logs of other nodes.
+Successfully deleted logs of other nodes.
+Deleting software packages and environmental variables of the local node.
+Successfully deleted software packages and environmental variables of the local nodes.
+Deleting local OS user.
+Successfully deleted local OS user.
+Deleting local node's logs.
+Successfully deleted local node's logs.
+Successfully cleaned environment.
+```
+
+ **错误排查**
+
+如果一键式环境清理失败请根据"\$GAUSSLOG/om/gs_postuninstall-YYYY-MM-DD_HHMMSS.log"中的日志信息排查错误。
diff --git a/product/zh/docs-mogdb/v3.0/installation-guide/standard-installation/7-recommended-parameter-settings.md b/product/zh/docs-mogdb/v3.0/installation-guide/standard-installation/7-recommended-parameter-settings.md
new file mode 100644
index 0000000000000000000000000000000000000000..b294c2cca347456a8c956e98af9684a98069492a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/installation-guide/standard-installation/7-recommended-parameter-settings.md
@@ -0,0 +1,159 @@
+---
+title: 推荐参数设置及新建测试库
+summary: 推荐参数设置及新建测试库
+author: Guo Huan
+date: 2021-06-24
+---
+
+# 推荐参数设置及新建测试库
+
+在安装完数据库之后，推荐执行以下shell脚本来进行初始化参数设置。
+
+> 注意：
+>
+> 执行脚本前，请确保脚本中提到的所有相关文件目录已存在。如没有，需要执行`mkdir -p <文件目录>`命令提前创建。
+>
+> 例如：执行`gs_guc set -I all -N all -c "archive_dest='/ogarchive'"`前，可先执行`ls -l`查看是否存在该目录，若不存在，需执行`mkdir -p ogarchive`创建此目录。
+
+```bash
+#!/bin/bash
+
+source ~/.bashrc
+
+memory=`free|awk '{print $2}' |sed -n 2p`
+if [[ $memory -lt 4*1024*1024 ]]
+then
+    max_process_memory=2GB
+    shared_buffers=128MB
+    max_connections=500
+    work_mem=4MB
+    maintenance_work_mem=256MB
+    echo "If the database fails to start, lower the parameters max_process_memory and shared_buffers"
+elif [[ $memory -gt 4*1024*1024 ]] && [[ $memory -lt 8*1024*1024 ]]
+then
+    max_process_memory=5GB
+    shared_buffers=1GB
+    max_connections=1000
+    work_mem=16MB
+    maintenance_work_mem=1GB
+else
+    max_process_memory=$((memory*6/10/1024/1024))GB
+    shared_buffers=$((memory*3/10/1024/1024))GB
+    max_connections=3000
+    work_mem=64MB
+    maintenance_work_mem=2GB
+fi
+
+##内存相关参数
+gs_guc set -I all -N all -c "max_process_memory=${max_process_memory}"
+gs_guc set -I all -N all -c "shared_buffers=${shared_buffers}"
+gs_guc set -I all -N all -c "work_mem=${work_mem}"
+gs_guc set -I all -N all -c "maintenance_work_mem=${maintenance_work_mem}"
+gs_guc set -I all -N all -c "cstore_buffers=16MB"
+gs_guc set -I all -N all -c "wal_buffers=1GB"
+gs_guc set -I all -N all -c "local_syscache_threshold=32MB"
+gs_guc set -I all -N all -c "standby_shared_buffers_fraction=1"
+
+##连接访问相关参数
+gs_guc set -I all -N all -c "max_connections=${max_connections}"
+gs_guc set -I all -N all -c "max_prepared_transactions=${max_connections}"
+gs_guc set -I all -N all -c "listen_addresses = '*'"
+gs_guc set -I all -N all -c "remote_read_mode=non_authentication"
+gs_guc set -I all -N all -c "password_encryption_type=1"
+gs_guc set -I all -N all -c "password_reuse_time=0"
+gs_guc set -I all -N all -c "password_lock_time=0"
+gs_guc set -I all -N all -c "password_effect_time=0"
+gs_guc set -I all -N all -c "session_timeout=0"
+
+##wal相关参数
+gs_guc set -I all -N all -c "wal_level=logical"
+gs_guc set -I all -N all -c "full_page_writes=off"
+gs_guc set -I all -N all -c "wal_log_hints=off"
+gs_guc set -I all -N all -c "xloginsert_locks=48"
+gs_guc set -I all -N all -c "advance_xlog_file_num=10"
+
+##复制相关参数
+gs_guc set -I all -N all -c "synchronous_commit=on"
+gs_guc set -I all -N all -c "wal_keep_segments=1024"
+gs_guc set -I all -N all -c "max_wal_senders=16"
+gs_guc set -I all -N all -c "recovery_max_workers=4"
+gs_guc set -I all -N all -c "most_available_sync=on"
+gs_guc set -I all -N all -c "max_size_for_xlog_prune=104857600"
+gs_guc set -I all -N all -c "catchup2normal_wait_time=0"
+gs_guc set -I all -N all -c "enable_slot_log=on"
+gs_guc set -I all -N all -c "max_replication_slots=32"
+gs_guc set -I all -N all -c "wal_receiver_timeout=60s"
+gs_guc set -I all -N all -c "sync_config_strategy=none_node"
+
+##日志相关参数
+gs_guc set -I all -N all -c "logging_collector=on"
+gs_guc set -I all -N all -c "log_duration=on"
+gs_guc set -I all -N all -c "log_line_prefix='%m %u %d %r %p %S'"
+gs_guc set -I all -N all -c "log_checkpoints=on"
+gs_guc set -I all -N all -c "plog_merge_age=0"
+
+##性能统计相关参数
+gs_guc set -I all -N all -c "vacuum_cost_limit=1000"
+gs_guc set -I all -N all -c "autovacuum_max_workers=10"
+gs_guc set -I all -N all -c "autovacuum_naptime=20s"
+gs_guc set -I all -N all -c "autovacuum_vacuum_cost_delay=10"
+gs_guc set -I all -N all -c "autovacuum_vacuum_scale_factor=0.05"
+gs_guc set -I all -N all -c "autovacuum_analyze_scale_factor=0.02"
+gs_guc set -I all -N all -c "autovacuum_vacuum_threshold=200"
+gs_guc set -I all -N all -c "autovacuum_analyze_threshold=200"
+gs_guc set -I all -N all -c "autovacuum_io_limits=104857600"
+gs_guc set -I all -N all -c "instr_unique_sql_count=20000"
+gs_guc set -I all -N all -c "enable_save_datachanged_timestamp=off"
+gs_guc set -I all -N all -c "track_sql_count=off"
+gs_guc set -I all -N all -c "enable_instr_rt_percentile=off"
+gs_guc set -I all -N all -c "enable_instance_metric_persistent=off"
+gs_guc set -I all -N all -c "enable_logical_io_statistics=off"
+gs_guc set -I all -N all -c "enable_user_metric_persistent=off"
+gs_guc set -I all -N all -c "enable_mergejoin=on"
+gs_guc set -I all -N all -c "enable_nestloop=on"
+gs_guc set -I all -N all -c "enable_pbe_optimization=off"
+gs_guc set -I all -N all -c "enable_resource_track=on"
+gs_guc set -I all -N all -c "enable_wdr_snapshot=on"
+gs_guc set -I all -N all -c "instr_unique_sql_count=5000"
+
+##客户端白名单
+gs_guc set -I all -N all -h "host     all      all  0.0.0.0/0    md5"
+
+##其他参数
+gs_guc set -I all -N all -c "checkpoint_segments=1024"
+gs_guc set -I all -N all -c "checkpoint_completion_target=0.8"
+gs_guc set -I all -N all -c "pagewriter_sleep=200"
+
+gs_guc set -I all -N all -c "enable_alarm=off"
+gs_guc set -I all -N all -c "enable_codegen=off"
+gs_guc set -I all -N all -c "audit_enabled=off"
+gs_guc set -I all -N all -c "enable_asp=off"
+
+gs_guc set -I all -N all -c "lc_messages='en_US.UTF-8'"
+gs_guc set -I all -N all -c "lc_monetary='en_US.UTF-8'"
+gs_guc set -I all -N all -c "lc_numeric='en_US.UTF-8'"
+gs_guc set -I all -N all -c "lc_time='en_US.UTF-8'"
+
+gs_guc set -I all -N all -c "update_lockwait_timeout=1min"
+gs_guc set -I all -N all -c "lockwait_timeout=1min"
+
+gs_guc set -I all -N all -c "max_files_per_process=100000"
+gs_guc set -I all -N all -c "behavior_compat_options='display_leading_zero'"
+gs_guc set -I all -N all -c "enable_thread_pool=off"
+```
+
+重启数据库，使参数生效
+
+```bash
+gs_om -t stop && gs_om -t start
+```
+
+在数据库init完成之后，如果需要进行测试，推荐新建数据库和新用户来进行测试。比如如果需要创建一个用于TPCC测试的数据库和用户，则执行以下命令。
+
+```sql
+CREATE DATABASE tpcc_db;
+\c tpcc_db
+CREATE USER tpcc_usr WITH PASSWORD "tpcc@1234";
+alter user tpcc_usr sysadmin;
+GRANT ALL ON schema public TO tpcc_usr;
+```
diff --git a/product/zh/docs-mogdb/v3.0/overview.md b/product/zh/docs-mogdb/v3.0/overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..e6d04b95138214c6cf1c61a9cfc6f29f8710c46e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/overview.md
@@ -0,0 +1,177 @@
+---
+title: MogDB - 安稳易用的openGauss商业版数据库
+summary: MogDB - 安稳易用的openGauss商业版数据库
+author: Liu Xu
+date: 2021-03-04
+---
+
+# MogDB - 安稳易用的openGauss商业版数据库
+
+<br/>
+
+MogDB是En**Mo**tech **o**pen**G**auss **D**ata**B**ase Enterprise Edition的缩写，是云和恩墨基于openGauss开源数据库进行定制、推出的企业发行版。它将围绕高可用、安全、自动化运维、数据库一体机和SQL审核优化等企业需求，解决企业用户落地。其核心价值是易用性、高性能、高可用等和全天候的企业支持。
+
+<br/>
+
+## MogDB特点
+
+### 面向应用开发的基本功能
+
+- **支持标准SQL**
+
+    MogDB数据库支持标准的SQL。SQL标准是一个国际性的标准，定期会进行刷新。
+
+- **支持标准开发接口**
+
+    提供业界标准的ODBC及JDBC接口，保证用户业务快速迁移至MogDB。
+
+    目前支持标准的ODBC 3.5及JDBC 4.0接口，其中ODBC支持SUSE、Win32、Win64平台，JDBC无平台差异。
+
+- **事务支持**
+
+    事务支持指的就是系统提供事务的能力，支持全局事务的ACID，保证事务的原子性、一致性、隔离性和持久性。
+
+- **支持函数及存储过程**
+
+    函数和存储过程是数据库中的一种重要对象，主要功能将用户特定功能的SQL语句集进行封装，并方便调用。
+
+- **PG接口兼容**
+
+    兼容PSQL客户端，兼容PostgreSQL标准接口。
+
+- **支持SQL hint**
+
+    支持SQL hint影响执行计划生成、提升SQL查询性能。
+
+- **Copy接口支持容错机制**
+
+    MogDB提供用户封装好的Copy错误表创建函数，并允许用户在使用Copy From指令时指定容错选项，使得Copy From语句在执行过程中部分解析、数据格式、字符集等相关的报错不会报错中断事务、而是被记录至错误表中，使得在Copy From的目标文件即使有少量数据错误也可以完成入库操作。用户随后可以在错误表中对相关的错误进行定位以及进一步排查。
+
+<br/>
+
+### 数据库安全
+
+- **访问控制**
+
+    管理用户对数据库的访问控制权限，涵盖数据库系统权限和对象权限。
+
+- **控制权和访问权分离**
+
+    针对系统管理员用户，实现表对象的控制权和访问权分离，提高普通用户数据安全性，限制管理员对象访问权限。
+
+- **数据库加密认证**
+
+    采用基于RFC5802机制的口令加密认证方法。
+
+- **数据库审计**
+
+    审计日志记录用户对数据库的启停、连接、DDL、DML、DCL等操作。审计日志机制主要增强数据库系统对非法操作的追溯及举证能力。
+
+- **全密态数据库等值查询**
+
+    数据以加密形态存储在数据库服务器中，数据库支持对密文数据的检索与计算，而与查询任务相关的词法解析、语法解析、执行计划生成、事务一致性保证、存储都继承原有数据库能力。
+
+- **网络通信安全特性**
+
+    支持通过SSL加密客户端和服务器之间的通信数据，保证客户的客户端与服务器通信安全。
+
+- **行级访问控制**
+
+    行级访问控制特性将数据库访问粒度控制到数据表行级别，使数据库达到行级访问控制的能力。不同用户执行相同的SQL查询操作，按照行访问控制策略，读取到的结果可能是不同的。
+
+- **资源标签**
+
+    资源标签（Resource Label）特性通过将数据库资源按照用户自定义的方式划分，实现资源分类管理的目的。
+
+- **动态数据脱敏**
+
+    为了在一定程度上限制非授权用户对隐私数据的窥探，可以利用动态数据脱敏（Dynamic Data Masking）特性保护用户隐私数据。在非授权用户访问配置了动态数据脱敏策略的数据时，数据库将返回脱敏后的数据而达到对隐私数据保护的目的。
+
+- **统一审计**
+
+    统一审计（Unified Auditing）利用策略和条件在数据库内部有选择地进行审计，管理员可以对数据库资源或资源标签统一地配置审计策略，从而达到简化管理、针对性地生成审计日志、减少审计日志冗余、提高管理效率的目的
+
+- **用户口令强度校验机制**
+
+    为了加固客户账户和数据的安全，禁止设置过低强度的口令，当初始化数据库、创建用户、修改用户时需要指定密码。密码必须满足强度校验，否则会提示用户重新输入密码
+
+- **数据加密存储**
+
+    提供对插入数据的加密存储。
+
+<br/>
+
+### 高性能
+
+- **CBO优化器**
+
+    MogDB优化器是典型的基于代价的优化 (Cost-Based Optimization，简称CBO)。在这种优化器模型下，数据库根据表的元组数、字段宽度、NULL记录比率、distinct值、MCV值、HB值等表的特征值，以及一定的代价计算模型，计算出每一个执行步骤的不同执行方式的输出元组数和执行代价(cost)，进而选出整体执行代价最小/首元组返回代价最小的执行方式进行执行。
+
+    CBO优化器能够在众多计划中依据代价选出最高效的执行计划，最大限度的满足客户业务要求。
+
+- **行列混合存储**
+
+    支持行存储和列存储两种存储模型，用户可以根据应用场景，建表的时候选择行存储还是列存储表。
+
+- **自适应压缩**
+
+    自适用压缩正是从数据类型和数据特征出发，采用相应的压缩算法，实现了良好的压缩比、快速的入库性能以及良好的查询性能。
+
+- **分区**
+
+    数据分区是将实例内部的数据集按照用户指定的策略作做一步拆分的水平分表，将表按照指定范围划分为多个数据互不重叠的部分。
+
+- **SQL by pass**
+
+    SQL-BY-PASS框架是在parse层对这类查询做简单的模式判别后，进入到特殊的执行路径里，跳过经典的执行器执行框架，包括算子的初始化与执行、表达式与投影等经典框架，直接重写一套简洁的执行路径，并且直接调用存储接口，这样可以大大加速简单查询的执行速度。
+
+- **鲲鹏NUMA架构优化**
+
+    减少跨界点数据访问，提升性能、基于LSE指令集的高效原子操作。
+
+<br/>
+
+### 高扩展
+
+**线程池高并发**
+
+对于外部连接最简单的处理模式是per-thread-per-connection模式，即来一个用户连接产生一个线程。这个模式好处是架构上处理简单，但是高并发下，由于线程太多，线程切换和数据库轻量级锁区域的冲突过大导致性能急剧下降，使得系统性能（吞吐量）严重下降，无法满足用户性能的SLA。
+
+<br/>
+
+### 高可用
+
+- **主备机**
+
+    为了保证故障的可恢复，需要将数据写多份，设置主备多个副本，通过日志进行数据同步，可以实现节点故障、停止后重启等情况下，MogDB能够保证故障之前的数据无丢失，满足ACID特性。
+
+- **逻辑备份**
+
+    MogDB提供逻辑备份能力，可以将用户表的数据以通用的text或者csv格式备份到本地磁盘文件，并在同构/异构数据库中恢复该用户表的数据。
+
+- **物理备份**
+
+    MogDB提供物理备份能力，可以将整个实例的数据以数据库内部格式备份到本地磁盘文件中，并在同构数据库中恢复整个实例的数据。
+
+- **恢复到指定时间点（PITR）**
+
+    时间点恢复(Point In Time Recovery)基本原理是通过基础热备 + WAL预写日志 + WAL归档日志进行备份恢复。重放WAL记录的时候可以在任意点停止重放，这样就有一个在任意时间的数据库一致的快照。即可以把数据库恢复到自开始备份以来的任意时刻的状态。MogDB在恢复时可以指定恢复的停止点位置为TID，时间和LSN。
+
+<br/>
+
+### 可维护性
+
+- **支持WDR诊断报告**
+
+    WDR(Workload Diagnosis Report)基于两次不同时间点系统的性能快照数据， 生成这两个时间点之间的性能表现报表，用于诊断数据库内核的性能故障。
+
+    WDR主要依赖两个组件:
+
+  - SNAPSHOT性能快照: 性能快照可以配置成按一定时间间隔从内核采集一定量的性能数据，持久化在用户表空间。任何一个SNAPSHOT可以作为一个性能基线，其他SNAPSHOT与之比较的结果，可以分析出与基线的性能表现。
+  - WDR Reporter: 报表生成工具基于两个SNAPSHOT，分析系统总体性能表现，并能计算出更多项具体的性能指标在这两个时间段之间的变化量，生成SUMMARY 和DETAIL两个不同级别的性能数据。
+
+<br/>
+
+### MogDB Manager
+
+MogDB Manager提供了一整套企业级数据库管理套件，包括: 安装部署、高可用监控及故障解决、性能监控、数据库迁移、备份恢复管理、异构数据库间数据同步、SQL兼容性分析、性能压测对比分析、极限数据恢复等管理组件，在多个运维维度帮助客户提高数据库管理效率。
diff --git a/product/zh/docs-mogdb/v3.0/performance-tuning/1-system/1-optimizing-os-parameters.md b/product/zh/docs-mogdb/v3.0/performance-tuning/1-system/1-optimizing-os-parameters.md
new file mode 100644
index 0000000000000000000000000000000000000000..97a805e6f5b35bdc6da916957e7c74db8c2d4b7a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/performance-tuning/1-system/1-optimizing-os-parameters.md
@@ -0,0 +1,125 @@
+---
+title: 操作系统参数调优
+summary: 操作系统参数调优
+author: Liu Xu
+date: 2021-03-04
+---
+
+# 操作系统参数调优
+
+在性能调优过程中，可以根据实际业务情况修改关键操作系统（OS）配置参数，以提升MogDB数据库的性能。
+
+<br/>
+
+## 前提条件
+
+需要用户使用gs_check检查操作系统参数结果是否和建议值保持一致，如果不一致，用户可根据实际业务情况去手动修改。
+
+<br/>
+
+## 内存相关参数设置
+
+配置"sysctl.conf"文件，修改内存相关参数vm.extfrag_threshold为1000（参考值），如果文件中没有内存相关参数，可以手动添加。
+
+```bash
+vim /etc/sysctl.conf
+```
+
+修改完成后，请执行如下命令，使参数生效。
+
+```bash
+sysctl -p
+```
+
+<br/>
+
+## 网络相关参数设置
+
+- 配置"sysctl.conf"文件，修改网络相关参数，如果文件中没有网络相关参数，可以手动添加。详细说明请参见[表1](#1)。
+
+    ```bash
+    vim /etc/sysctl.conf
+    ```
+
+    在修改完成后，请执行如下命令，使参数生效。
+
+    ```bash
+    sysctl -p
+    ```
+
+    <a id="1">**表 1** </a>网络相关参数
+
+    | 参数名                       | 参考值                       | 说明
+    | :--------------------------- | :--------------------------- | :------------------------------------|
+    | net.ipv4.tcp_timestamps      | 1                            | 表示开启TCP连接中TIME-WAIT sockets的快速回收，默认为0，表示关闭，1表示打开。                                                                                                                                                                            |
+    | net.ipv4.tcp_mem             | 94500000 915000000 927000000 | 第一个数字表示，当tcp使用的page少于 94500000 时，kernel不对其进行任何的干预。第二个数字表示，当tcp使用的page超过 915000000 时，kernel会进入"memory pressure"压力模式。第三个数字表示，当tcp使用的pages超过 927000000 时，就会报: Out of socket memory。 |
+    | net.ipv4.tcp_max_orphans     | 3276800                      | 最大孤儿套接字（orphan sockets）数。                                                                                                                        |
+    | net.ipv4.tcp_fin_timeout     | 60                           | 表示系統默认的TIMEOUT时间。                                     |
+    | net.ipv4.ip_local_port_range | 26000 65535                  | TCP和UDP能够使用的port段。                        |
+
+- 设置10GE网卡最大传输单元（MTU），使用ifconfig命令设置。10GE网卡推荐设置为8192，可提升网络带宽利用率。
+
+    示例:
+
+  ```bash
+    #ifconfig ethx mtu 8192
+  #ifconfig ethx
+    ethx   Link encap:Ethernet  HWaddr XX:XX:XX:XX:XX:XX
+    inet addr:xxx.xxx.xxx.xxx  Bcast:xxx.xxx.xxx.xxx  Mask:xxx.xxx.xxx.0
+    inet6 addr: fxxx::9xxx:bxxx:xxxa:1d18/64 Scope:Link
+    UP BROADCAST RUNNING MULTICAST  MTU:8192  Metric:1
+    RX packets:179849803 errors:0 dropped:0 overruns:0 frame:0
+    TX packets:40492292 errors:0 dropped:0 overruns:0 carrier:0
+    collisions:0 txqueuelen:1000
+    RX bytes:17952090386 (17120.4 Mb)  TX bytes:171359670290 (163421.3 Mb)
+    ```
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+    >
+  > - ethx为10GE数据库内部使用的业务网卡。
+    > - 第一条命令设置MTU，第二条命令验证是否设置成功，粗体部分为MTU的值。
+    > - 需使用root用户设置。
+
+- 设置10GE网卡接收（rx）、发送队列（tx）长度，使用ethtool工具设置。10GE网卡推荐设置为4096，可提升网络带宽利用率。
+
+    示例:
+
+    ```bash
+    # ethtool -G ethx rx 4096 tx 4096
+    # ethtool -g ethx
+    Ring parameters for ethx:
+    Pre-set maximums:
+    RX:             4096
+    RX Mini:        0
+    RX Jumbo:       0
+    TX:             4096
+    Current hardware settings:
+    RX:             4096
+    RX Mini:        0
+    RX Jumbo:       0
+    TX:             4096
+    ```
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+    >
+    > - ethx为10GE数据库内部使用的业务网卡。
+    > - 第一条命令设置网卡接收、发送队列长度，第二条命令验证是否设置成功，示例的输出表示设置成功。
+    > - 需使用root用户设置。
+
+<br/>
+
+## I/O相关参数设置
+
+设置hugepage属性。通过如下命令，关闭透明大页。。
+
+```bash
+echo never >
+/sys/kernel/mm/transparent_hugepage/enabled
+echo never > /sys/kernel/mm/transparent_hugepage/defrag
+```
+
+修改完成后，请执行如下命令，使参数生效。
+
+```bash
+reboot
+```
diff --git a/product/zh/docs-mogdb/v3.0/performance-tuning/1-system/2-optimizing-database-parameters.md b/product/zh/docs-mogdb/v3.0/performance-tuning/1-system/2-optimizing-database-parameters.md
new file mode 100644
index 0000000000000000000000000000000000000000..6462cc717eb602e18af26d3e750090a72ec1f45d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/performance-tuning/1-system/2-optimizing-database-parameters.md
@@ -0,0 +1,69 @@
+---
+title: 数据库系统参数调优
+summary: 数据库系统参数调优
+author: Liu Xu
+date: 2021-03-04
+---
+
+# 数据库系统参数调优
+
+为了保证数据库尽可能高性能地运行，建议依据硬件资源情况和业务实际进行数据库系统参数设置。
+
+<br/>
+
+## 数据库内存参数调优
+
+数据库的复杂查询语句性能非常强的依赖于数据库系统内存的配置参数。数据库系统内存的配置参数主要包括逻辑内存管理的控制参数和执行算子是否下盘的参数。
+
+<br/>
+
+### 逻辑内存管理参数
+
+逻辑内存管理参数为max_process_memory，主要功能是控制数据库节点上可用内存的最大峰值，该参数的数值设置公式参考max_process_memory。
+
+执行作业最终可用的内存为:
+
+max_process_memory - shared memory ( 包括shared_buffers ) - cstore_buffers
+
+所以影响执行作业可用内存参数的主要两个参数为shared_buffers及cstore_buffers。
+
+逻辑内存管理有专门的视图查询数据库节点中各大块内存区域已使用内存及峰值信息。可连接到单个数据库节点，通过"pg_total_memory_detail"查询该节点上内存区域信息；或者连接到数据库主节点，通过"pgxc_total_memory_detail"查询节点上内存区域信息。
+
+参数work_mem依据查询特点和并发来确定，一旦work_mem限定的物理内存不够，算子运算数据将写入临时表空间，带来5-10倍的性能下降，查询响应时间从秒级下降到分钟级。
+
+- 对于串行无并发的复杂查询场景，平均每个查询有5-10关联操作，建议work_mem=50%内存/10。
+- 对于串行无并发的简单查询场景，平均每个查询有2-5个关联操作，建议work_mem=50%内存/5。
+- 对于并发场景，建议work_mem=串行下的work_mem/物理并发数。
+
+<br/>
+
+### 执行算子是否下盘的参数
+
+参数work_mem可以判断执行作业可下盘算子是否已使用内存量触发下盘点。当前可下盘算子有六类（向量化及非向量化共10种）: Hash(VecHashJoin)，Agg(VecAgg)，Sort(VecSort)，Material(VecMaterial)，SetOp(VecSetOp)，WindowAgg(VecWindowAgg)。该参数设置通常是一个权衡，即要保证并发的吞吐量，又要保证单查询作业的性能，故需要根据实际执行情况（结合Explain Performance输出）进行调优。
+
+<br/>
+
+## 数据库并发队列参数调优
+
+数据库提供两种手段进行并发队列的控制，全局并发队列和局部并发队列。
+
+<br/>
+
+### 全局并发队列
+
+全局并发队列采用GUC参数max_active_statements控制数据库主节点上运行并发执行的作业数量。采用全局并发队列机制将控制所有普通用户的执行作业，不区分复杂度，即执行语句都将作为一个执行单元，当并发执行的作业数量达到此参数阈值时，将进入队列等待。对于管理员执行的作业，不走全局并发控制逻辑。
+
+设置该GUC参数数值时，需要考虑系统的承受能力，主要关注内存的使用情况及IO的使用情况，综合判断。若普通用户关联资源池，并且资源池中的优先级比例不同，全局并发队列在数据库内部将使用两维队列，即优先级高低排队和同一优先级进行排队。在唤醒时，将优先唤醒高优先级队列的作业。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+>
+> - 在事务类大并发业务场景下，参数max_active_statements建议设置为-1，即不限制全局并发数。
+> - 在分析类查询的场景下，参数max_active_statements的值设置为CPU的核数除以数据库节点个数，一般可以设置5~8个。
+
+<br/>
+
+### 局部并发队列
+
+采用资源池局部并发控制机制的目的是控制在数据库主节点上同一资源池内的并发作业数量。局部并发控制机制根据执行作业的cost，控制复杂查询的并发作业数量。
+
+参数parctl_min_cost数值用于判断执行作业是否是复杂作业。
diff --git a/product/zh/docs-mogdb/v3.0/performance-tuning/1-system/3-configuring-llvm.md b/product/zh/docs-mogdb/v3.0/performance-tuning/1-system/3-configuring-llvm.md
new file mode 100644
index 0000000000000000000000000000000000000000..f6c1639adf58ed102eda715fb223f08962752ad8
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/performance-tuning/1-system/3-configuring-llvm.md
@@ -0,0 +1,86 @@
+---
+title: 配置LLVM
+summary: 配置LLVM
+author: Liu Xu
+date: 2021-03-04
+---
+
+# 配置LLVM
+
+LLVM（Low Level Virtual Machine）动态编译技术可以为每个查询生成定制化的机器码用于替换原本的通用函数。通过减少实际查询时冗余的条件逻辑判断、虚函数调用并提高数据局域性，从而达到提升查询整体性能的目的。
+
+由于LLVM需要消耗额外的时间预生成IR中间态表示并编译成机器码，因此在小数据量场景或查询本身耗时较少时，可能引起性能的劣化。
+
+<br/>
+
+## LLVM适用场景与限制
+
+<br/>
+
+### 适用场景
+
+- 支持LLVM的表达式
+
+    查询语句中存在以下的表达式支持LLVM优化:
+
+    1. Case…when… 表达式
+    2. In表达式
+    3. Bool表达式 (And/Or/Not)
+    4. BooleanTest表达式 (IS_NOT_KNOWN/IS_UNKNOWN/IS_TRUE/IS_NOT_TRUE/IS_FALSE/IS_NOT_FALSE)
+    5. NullTest表达式 (IS_NOT_NULL/IS_NULL)
+    6. Operator表达式
+    7. Function表达式 (lpad，substring，btrim，rtrim，length)
+    8. Nullif表达式
+
+    表达式计算支持的数据类型包括bool，tinyint，smallint，int，bigint，float4，float8，numeric，date，time，timetz，timestamp，timestamptz，interval，bpchar，varchar，text，oid。
+
+    仅当表达式出现在向量化执行引擎中Scan节点的filter、Hash Join节点中的complicate hash condition、hash join filter、hash join target, Nested Loop节点中的filter、join filter, Merge Join节点的merge join filter, merge join target, Group节点中的filter表达式时，才会考虑是否使用LLVM动态编译优化。
+
+- 支持LLVM的算子:
+
+    1. Join：HashJoin
+    2. Agg：HashAgg
+    3. Sort
+
+    其中HashJoin算子仅支持Hash Inner Join，对应的hash cond仅支持int4、bigint、bpchar类型的比较；HashAgg算子仅支持针对bigint、numeric类型的sum及avg操作，且group by语句仅支持int4、bigint、bpchar，text，varchar，timestamp类型操作，同时支持count(*)聚集操作。Sort算子仅支持对int4，bigint，numeric，bpchar，text，varchar数据类型的比较操作。除此之外，无法使用LLVM动态编译优化，具体可通过explain performance工具进行显示。
+
+<br/>
+
+### 非适用场景
+
+- 不支持小数据量表使用LLVM动态编译优化。
+
+- 不支持生成非向量化执行路径的查询作业。
+
+<br/>
+
+## 其他因素对LLVM性能的影响
+
+LLVM优化效果不仅依赖于数据库内部具体的实现，还与当前所选择的硬件环境等有关。
+
+- 表达式调用C-函数个数
+
+    数据库内部针对表达式计算并未实现全codegen，即在整个表达式计算中部分表达式实现了codegen，部分直接调用原本的C代码。如果整个表达式计算中后者占据了主要部分，使用LLVM动态编译优化，可能会导致性能劣化。通过设置log_min_message的级别为DEBUG1可以查看到哪些表达式直接调用了C代码实现。
+
+- 内存资源
+
+    LLVM特性的一个重要思想是保障数据的局域特性，即数据应尽可能的存放在寄存器中。同时应减少数据加载，因此在使用LLVM优化时应设置足够大的work_mem，保证对应使用LLVM优化的执行代码整个过程在内存中实现，否则可能引起性能劣化。
+
+- 优化器代价估算
+
+    LLVM特性实现了简易的代价估算模型，即依据当前参与节点运算的表大小决定当前节点是否考虑使用LLVM动态编译优化。如果优化器低估了实际参与运算的行数，则原本可获得收益的未正常获得收益。反之亦然。
+
+<br/>
+
+## LLVM使用建议
+
+目前LLVM在数据库内核侧已默认打开，用户可结合上述的分析进行配置，总体建议如下:
+
+1. 设置合理的work_mem，在允许的条件下尽可能设置较大的work_mem，如果出现大量数据落盘，则建议关闭LLVM动态编译优化（通过设置enable_codegen=off实现）。
+
+2. 设置合理的codegen_cost_threshold（默认值为10000），确保小数据量场景下避免使用LLVM动态编译优化。当codegen_cost_threshold的值设定后，因使用LLVM动态编译优化引入性能劣化，则建议增加codegen_cost_threshold的取值。
+
+3. 对于表达式计算使用LLVM动态编译优化，如果存在大量的调用C-函数的场景，建议关闭LLVM动态编译优化。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+    > 在资源许可的情况下，数据量越大，可获得的性能提升效果越好。
diff --git a/product/zh/docs-mogdb/v3.0/performance-tuning/1-system/4-configuring-smp.md b/product/zh/docs-mogdb/v3.0/performance-tuning/1-system/4-configuring-smp.md
new file mode 100644
index 0000000000000000000000000000000000000000..04e7274388df9104848be019c4ab4610b4844db0
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/performance-tuning/1-system/4-configuring-smp.md
@@ -0,0 +1,111 @@
+---
+title: 配置SMP
+summary: 配置SMP
+author: Guo Huan
+date: 2021-07-26
+---
+
+# 配置SMP
+
+介绍SMP模块的使用限制与适用场景，并给出SMP配置指南。
+
+## SMP适用场景与限制
+
+### 背景信息
+
+SMP特性通过算子并行来提升性能，同时会占用更多的系统资源，包括CPU、内存、I/O等等。本质上SMP是一种以资源换取时间的方式，在合适的场景以及资源充足的情况下，能够起到较好的性能提升效果；但是如果在不合适的场景下，或者资源不足的情况下，反而可能引起性能的劣化。SMP特性适用于分析类查询场景，这类场景的特点是单个查询时间较长，业务并发度低。通过SMP并行技术能够降低查询时延，提高系统吞吐性能。然而在事务类大并发业务场景下，由于单个查询本身的时延很短，使用多线程并行技术反而会增加查询时延，降低系统吞吐性能。
+
+### 适用场景
+
+- 支持并行的算子：计划中存在以下算子支持并行。
+
+  - Scan：支持行存普通表和行存分区表顺序扫描 、列存普通表和列存分区表顺序扫描。
+  - Join：HashJoin、NestLoop
+  - Agg：HashAgg、SortAgg、PlainAgg、WindowAgg（只支持partition by，不支持order by）
+  - Stream：Local Redistribute、Local Broadcast
+  - 其他：Result、Subqueryscan、Unique、Material、Setop、Append、VectoRow、RowToVec
+
+- SMP特有算子：为了实现并行，新增了并行线程间的数据交换Stream算子供SMP特性使用。这些新增的算子可以看做Stream算子的子类。
+
+  - Local Gather：实现实例内部并行线程的数据汇总。
+  - Local Redistribute：在实例内部各线程之间，按照分布键进行数据重分布。
+  - Local Broadcast：将数据广播到实例内部的每个线程。
+  - Local RoundRobin：在实例内部各线程之间实现数据轮询分发。
+
+- 示例说明，以TPCH Q1的并行计划为例。
+
+  ![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/configuring-smp-1.png)
+
+  在这个计划中，实现了Scan以及HashAgg算子的并行，并新增了Local Gather数据交换算子。其中3号算子为Local Gather算子，上面标有的“dop: 1/4”表明该算子的发送端线程的并行度为4，而接受端线程的并行度为1，即下层的4号HashAggregate算子按照4并行度执行，而上层的1~2号算子按照串行执行，3号算子实现了实例内并行线程的数据汇总。
+
+  通过计划Stream算子上表明的dop信息即可看出各个算子的并行情况。
+
+### 非适用场景
+
+1. 索引扫描不支持并行执行。
+2. MergeJoin不支持并行执行。
+3. WindowAgg order by不支持并行执行。
+4. cursor不支持并行执行。
+5. 存储过程和函数内的查询不支持并行执行。
+6. 不支持子查询subplan和initplan的并行，以及包含子查询的算子的并行。
+7. 查询语句中带有median操作的查询不支持并行执行。
+8. 带全局临时表的查询不支持并行执行。
+9. 物化视图的更新不支持并行执行。
+
+## 资源对SMP性能的影响
+
+SMP架构是一种利用富余资源来换取时间的方案，计划并行之后必定会引起资源消耗的增加，包括CPU、内存、I/O等资源的消耗都会出现明显的增长，而且随着并行度的增大，资源消耗也随之增大。当上述资源成为瓶颈的情况下，SMP无法提升性能，反而可能导致集群整体性能的劣化。下面对各种资源对SMP性能的影响情况分别进行说明。
+
+- CPU资源
+
+  在一般客户场景中，系统CPU利用率不高的情况下，利用SMP并行架构能够更充分地利用系统CPU资源，提升系统性能。但当数据库服务器的CPU核数较少，CPU利用率已经比较高的情况下，如果打开SMP并行，不仅性能提升不明显，反而可能因为多线程间的资源竞争而导致性能劣化。
+
+- 内存资源
+
+  查询并行后会导致内存使用量的增长，但每个算子使用内存上限仍受到work_mem等参数的限制。假设work_mem为4GB，并行度为2，那么每个并行线程所分到的内存上限为2GB。在work_mem较小或者系统内存不充裕的情况下，使用SMP并行后，可能出现数据下盘，导致查询性能劣化的问题。
+
+- I/O资源
+
+  要实现并行扫描必定会增加I/O的资源消耗，因此只有在I/O资源充足的情况下，并行扫描才能够提高扫描性能。
+
+## 其他因素对SMP性能的影响
+
+除了资源因素外，还有一些因素也会对SMP并行性能造成影响。例如分区表中分区数据不均，以及系统并发度等因素。
+
+- 数据倾斜对SMP性能的影响
+
+  当数据中存在严重数据倾斜时，并行效果较差。例如某表join列上某个值的数据量远大于其他值，开启并行后，根据join列的值对该表数据做hash重分布，使得某个并行线程的数据量远多于其他线程，造成长尾问题，导致并行后效果差。
+
+- 系统并发度对SMP性能的影响
+
+  SMP特性会增加资源的使用，而在高并发场景下资源剩余较少。所以，如果在高并发场景下，开启SMP并行，会导致各查询之间严重的资源竞争问题。一旦出现了资源竞争的现象，无论是CPU、I/O、内存，都会导致整体性能的下降。因此在高并发场景下，开启SMP往往不能达到性能提升的效果，甚至可能引起性能劣化。
+
+## SMP 使用建议
+
+### 使用限制
+
+想要利用SMP提升查询性能需要满足以下条件：
+
+系统的CPU、内存、I/O和网络带宽等资源充足。SMP架构是一种利用富余资源来换取时间的方案，计划并行之后必定会引起资源消耗的增加，当上述资源成为瓶颈的情况下，SMP无法提升性能，反而可能导致性能的劣化。在出现资源瓶颈的情况下，建议关闭SMP。
+
+### 配置步骤
+
+1. 观察当前系统负载情况，如果系统资源充足（资源利用率小于50%），执行步骤2；否则退出。
+
+2. 设置query_dop=1（默认值），利用explain打出执行计划，观察计划是否符合[SMP适用场景与限制](#smp适用场景与限制)小节中的适用场景。如果符合，进入步骤3。
+
+3. 设置query_dop=value，不考虑资源情况和计划特征，强制选取dop为1或value。
+
+4. 在符合条件的查询语句执行前设置合适的query_dop值，在语句执行结束后关闭query_dop。举例如下。
+
+   ```
+   mogdb=# SET query_dop = 4;
+   mogdb=# SELECT COUNT(*) FROM t1 GROUP BY a;
+   ......
+   mogdb=# SET query_dop = 1;
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+   >
+   > - 资源许可的情况下，并行度越高，性能提升效果越好。
+   > - SMP并行度支持会话级设置，推荐客户在执行符合要求的查询前，打开smp，执行结束后，关闭smp。以免在业务峰值时，对业务造成冲击。
diff --git a/product/zh/docs-mogdb/v3.0/performance-tuning/2-sql/1-query-execution-process.md b/product/zh/docs-mogdb/v3.0/performance-tuning/2-sql/1-query-execution-process.md
new file mode 100644
index 0000000000000000000000000000000000000000..66d55577f7055d4bbe1a56cfd5255b0dace9f3e7
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/performance-tuning/2-sql/1-query-execution-process.md
@@ -0,0 +1,79 @@
+---
+title: Query执行流程
+summary: Query执行流程
+author: Liu Xu
+date: 2021-03-04
+---
+
+# Query执行流程
+
+<br/>
+
+## 简介
+
+SQL引擎从接受SQL语句到执行SQL语句需要经历的步骤如图1和说明1所示。其中，红色字体部分为DBA可以介入实施调优的环节。
+
+**图 1** SQL引擎执行查询类SQL语句的流程
+
+![SQL引擎执行查询类SQL语句的流程](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/query-execution-process-1.png)
+
+**说明 1** SQL引擎执行查询类SQL语句的步骤说明
+
+**1、语法&词法解析**
+
+按照约定的SQL语句规则，把输入的SQL语句从字符串转化为格式化结构（Stmt）。
+
+**2、语义解析**
+
+将"语法&词法解析"输出的格式化结构转化为数据库可以识别的对象。
+
+**3、查询重写**
+
+根据规则把"语义解析"的输出等价转化为执行上更为优化的结构。
+
+**4、查询优化**
+
+根据"查询重写"的输出和数据库内部的统计信息规划SQL语句具体的执行方式，也就是执行计划。统计信息和GUC参数对查询优化（执行计划）的影响，请参见调优手段之统计信息和调优手段之GUC参数。
+
+**5、查询执行**
+
+根据"查询优化"规划的执行路径执行SQL查询语句。底层存储方式的选择合理性，将影响查询执行效率。详见调优手段之底层存储。
+
+<br/>
+
+## 调优手段之统计信息
+
+MogDB优化器是典型的基于代价的优化（Cost-Based Optimization，简称CBO）。在这种优化器模型下，数据库根据表的元组数、字段宽度、NULL记录比率、distinct值、MCV值、HB值等表的特征值，以及一定的代价计算模型，计算出每一个执行步骤的不同执行方式的输出元组数和执行代价（cost），进而选出整体执行代价最小/首元组返回代价最小的执行方式进行执行。这些特征值就是统计信息。从上面的描述可以看出统计信息是查询优化的核心输入，准确的统计信息将帮助规划器选择最合适的查询规划，一般来说我们通过analyze语法收集整个表或者表的若干个字段的统计信息，周期性地运行ANALYZE，或者在对表的大部分内容做了更改之后马上运行它是个好习惯。
+
+<br/>
+
+## 调优手段之GUC参数
+
+查询优化的主要目的是为查询语句选择高效的执行方式。
+
+如下SQL语句:
+
+```sql
+select count(1)
+from customer inner join store_sales on (ss_customer_sk = c_customer_sk);
+```
+
+在执行customer inner join store_sales的时候，MogDB支持Nested Loop、Merge Join和Hash Join三种不同的Join方式。优化器会根据表customer和表store_sales的统计信息估算结果集的大小以及每种join方式的执行代价，然后对比选出执行代价最小的执行计划。
+
+正如前面所说，执行代价计算都是基于一定的模型和统计信息进行估算，当因为某些原因代价估算不能反映真实的cost的时候，我们就需要通过guc参数设置的方式让执行计划倾向更优规划。
+
+<br/>
+
+## 调优手段之底层存储
+
+MogDB的表支持行存表、列存表，底层存储方式的选择严格依赖于客户的具体业务场景。一般来说计算型业务查询场景（以关联、聚合操作为主）建议使用列存表；点查询、大批量UPDATE/DELETE业务场景适合行存表。
+
+对于每种存储方式还有对应的存储层优化手段，这部分会在后续的调优章节深入介绍。
+
+<br/>
+
+## 调优手段之SQL重写
+
+除了上述干预SQL引擎所生成执行计划的执行性能外，根据数据库的SQL执行机制以及大量的实践发现，有些场景下，在保证客户业务SQL逻辑的前提下，通过一定规则由DBA重写SQL语句，可以大幅度的提升SQL语句的性能。
+
+这种调优场景对DBA的要求比较高，需要对客户业务有足够的了解，同时也需要扎实的SQL语句基本功，后续会介绍几个常见的SQL改写场景。
diff --git a/product/zh/docs-mogdb/v3.0/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md b/product/zh/docs-mogdb/v3.0/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md
new file mode 100644
index 0000000000000000000000000000000000000000..5c5e291abe7bf7f83a90d65004259fcfd2fe3d0c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md
@@ -0,0 +1,142 @@
+---
+title: SQL执行计划介绍
+summary: SQL执行计划介绍
+author: Liu Xu
+date: 2021-03-04
+---
+
+# SQL执行计划介绍
+
+<br/>
+
+## SQL执行计划概述
+
+SQL执行计划是一个节点树，显示openGauss执行一条SQL语句时执行的详细步骤。每一个步骤为一个数据库运算符。
+
+使用EXPLAIN命令可以查看优化器为每个查询生成的具体执行计划。EXPLAIN给每个执行节点都输出一行，显示基本的节点类型和优化器为执行这个节点预计的开销值。如图1所示。
+
+**图 1** SQL执行计划示例
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/introduction-to-the-sql-execution-plan-1.png)
+
+- 最底层节点是表扫描节点，它扫描表并返回原始数据行。不同的表访问模式有不同的扫描节点类型: 顺序扫描、索引扫描等。最底层节点的扫描对象也可能是非表行数据（不是直接从表中读取的数据），如VALUES子句和返回行集的函数，它们有自己的扫描节点类型。
+- 如果查询需要连接、聚集、排序、或者对原始行做其它操作，那么就会在扫描节点之上添加其它节点。 并且这些操作通常都有多种方法，因此在这些位置也有可能出现不同的执行节点类型。
+- 第一行（最上层节点）是执行计划总执行开销的预计。这个数值就是优化器试图最小化的数值。
+
+<br/>
+
+### 执行计划显示信息
+
+除了设置不同的执行计划显示格式外，还可以通过不同的EXPLAIN用法，显示不同详细程度的执行计划信息。常见有如下几种:
+
+- EXPLAIN _statement_：只生成执行计划，不实际执行。其中statement代表SQL语句。
+- EXPLAIN ANALYZE _statement_：生成执行计划，进行执行，并显示执行的概要信息。显示中加入了实际的运行时间统计，包括在每个规划节点内部花掉的总时间（以毫秒计）和它实际返回的行数。
+- EXPLAIN PERFORMANCE _statement_：生成执行计划，进行执行，并显示执行期间的全部信息。
+
+为了测量运行时在执行计划中每个节点的开销，EXPLAIN ANALYZE或EXPLAIN PERFORMANCE会在当前查询执行上增加性能分析的开销。在一个查询上运行EXPLAIN ANALYZE或EXPLAIN PERFORMANCE有时会比普通查询明显的花费更多的时间。超支的数量依赖于查询的本质和使用的平台。
+
+因此，当定位SQL运行慢问题时，如果SQL长时间运行未结束，建议通过EXPLAIN命令查看执行计划，进行初步定位。如果SQL可以运行出来，则推荐使用EXPLAIN ANALYZE或EXPLAIN PERFORMANCE查看执行计划及其实际的运行信息，以便更精准地定位问题原因。
+
+EXPLAIN PERFORMANCE轻量化执行方式与EXPLAIN PERFORMANCE保持一致，在原来的基础上减少了性能分析的时间，执行时间与SQL执行时间的差异显著减少
+
+<br/>
+
+## 详解
+
+如SQL执行计划概述节中所说，EXPLAIN会显示执行计划，但并不会实际执行SQL语句。EXPLAIN ANALYZE和EXPLAIN PERFORMANCE两者都会实际执行SQL语句并返回执行信息。在这一节将详细解释执行计划及执行信息。
+
+<br/>
+
+### 执行计划
+
+以如下SQL语句为例:
+
+```sql
+SELECT * FROM t1, t2 WHERE t1.c1 = t2.c2;
+```
+
+执行EXPLAIN的输出为:
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/introduction-to-the-sql-execution-plan-2.png)
+
+**执行计划层级解读（纵向）:**
+
+1. 第一层: Seq Scan on t2
+
+    表扫描算子，用Seq Scan的方式扫描表t2。这一层的作用是把表t2的数据从buffer或者磁盘上读上来输送给上层节点参与计算。
+
+2. 第二层: Hash
+
+    Hash算子，作用是把下层计算输送上来的算子计算hash值，为后续hash join操作做数据准备。
+
+3. 第三层: Seq Scan on t1
+
+    表扫描算子，用Seq Scan的方式扫描表t1。这一层的作用是把表t1的数据从buffer或者磁盘上读上来输送给上层节点参与hash join计算。
+
+4. 第四层: Hash Join
+
+    join算子，主要作用是将t1表和t2表的数据通过hash join的方式连接，并输出结果数据。
+
+**执行计划中的关键字说明:**
+
+1. 表访问方式
+
+    - Seq Scan
+
+        全表顺序扫描。
+
+    - Index Scan
+
+        优化器决定使用两步的规划: 最底层的规划节点访问一个索引，找出匹配索引条件的行的位置，然后上层规划节点真实地从表中抓取出那些行。独立地抓取数据行比顺序地读取它们的开销高很多，但是因为并非所有表的页面都被访问了，这么做实际上仍然比一次顺序扫描开销要少。使用两层规划的原因是，上层规划节点在读取索引标识出来的行位置之前，会先将它们按照物理位置排序，这样可以最小化独立抓取的开销。
+
+        如果在WHERE里面使用的好几个字段上都有索引，那么优化器可能会使用索引的AND或OR的组合。但是这么做要求访问两个索引，因此与只使用一个索引，而把另外一个条件只当作过滤器相比，这个方法未必是更优。
+
+        索引扫描可以分为以下几类，他们之间的差异在于索引的排序机制。
+
+        - Bitmap Index Scan
+
+            使用位图索引抓取数据页。
+
+        - Index Scan using index_name
+
+            使用简单索引搜索，该方式表的数据行是以索引顺序抓取的，这样就令读取它们的开销更大，但是这里的行少得可怜，因此对行位置的额外排序并不值得。最常见的就是看到这种规划类型只抓取一行，以及那些要求ORDER BY条件匹配索引顺序的查询。因为那时候没有多余的排序步骤是必要的以满足ORDER BY。
+
+2. 表连接方式
+
+    - Nested Loop
+
+        嵌套循环，适用于被连接的数据子集较小的查询。在嵌套循环中，外表驱动内表，外表返回的每一行都要在内表中检索找到它匹配的行，因此整个查询返回的结果集不能太大（不能大于10000），要把返回子集较小的表作为外表，而且在内表的连接字段上建议要有索引。
+
+    - (Sonic) Hash Join
+
+        哈希连接，适用于数据量大的表的连接方式。优化器使用两个表中较小的表，利用连接键在内存中建立hash表，然后扫描较大的表并探测散列，找到与散列匹配的行。Sonic和非Sonic的Hash Join的区别在于所使用hash表结构不同，不影响执行的结果集。
+
+    - Merge Join
+
+        归并连接，通常情况下执行性能差于哈希连接。如果源数据已经被排序过，在执行融合连接时，并不需要再排序，此时融合连接的性能优于哈希连接。
+
+3. 运算符
+
+    - sort
+
+        对结果集进行排序。
+
+    - filter
+
+        EXPLAIN输出显示WHERE子句当作一个"filter"条件附属于顺序扫描计划节点。这意味着规划节点为它扫描的每一行检查该条件，并且只输出符合条件的行。预计的输出行数降低了，因为有WHERE子句。不过，扫描仍将必须访问所有 10000 行，因此开销没有降低；实际上它还增加了一些（确切的说，通过10000 * cpu_operator_cost）以反映检查WHERE条件的额外CPU时间。
+
+    - LIMIT
+
+        LIMIT限定了执行结果的输出记录数。如果增加了LIMIT，那么不是所有的行都会被检索到。
+
+<br/>
+
+### 执行信息
+
+```sql
+select sum(t2.c1) from t1,t2 where t1.c1=t2.c2 group by t1.c2;
+```
+
+执行EXPLAIN PERFORMANCE输出为:
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/introduction-to-the-sql-execution-plan-3.png)
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/performance-tuning/2-sql/3-tuning-process.md b/product/zh/docs-mogdb/v3.0/performance-tuning/2-sql/3-tuning-process.md
new file mode 100644
index 0000000000000000000000000000000000000000..e92a1a34b5f87fb69dba7b38d8ff7617d6f15306
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/performance-tuning/2-sql/3-tuning-process.md
@@ -0,0 +1,39 @@
+---
+title: 调优流程
+summary: 调优流程
+author: Liu Xu
+date: 2021-03-04
+---
+
+# 调优流程
+
+**对慢SQL语句进行分析，通常包括以下步骤:**
+
+<br/>
+
+## 收集SQL中涉及到的所有表的统计信息
+
+在数据库中，统计信息是规划器生成计划的源数据。没有收集统计信息或者统计信息陈旧往往会造成执行计划严重劣化，从而导致性能问题。从经验数据来看，10%左右性能问题是因为没有收集统计信息。
+
+<br/>
+
+## 通过查看执行计划来查找原因
+
+如果SQL长时间运行未结束，通过EXPLAIN命令查看执行计划，进行初步定位。如果SQL可以运行出来，则推荐使用EXPLAIN ANALYZE或EXPLAIN PERFORMANCE查看执行计划及实际运行情况，以便更精准地定位问题原因。
+
+<br/>
+
+## 针对EXPLAIN或EXPLAIN PERFORMANCE信息，定位SQL慢的具体原因以及改进措施
+
+可以从以下四个方面分析:
+
+- SQL自诊断
+- 子查询调优
+- 统计信息调优
+- 算子级调优
+
+<br/>
+
+### 通常情况下，有些SQL语句可以通过查询重写转换成等价的，或特定场景下等价的语句
+
+重写后的语句比原语句更简单，且可以简化某些执行步骤达到提升性能的目的。查询重写方法在各个数据库中基本是通用的。
diff --git a/product/zh/docs-mogdb/v3.0/performance-tuning/2-sql/4-updating-statistics.md b/product/zh/docs-mogdb/v3.0/performance-tuning/2-sql/4-updating-statistics.md
new file mode 100644
index 0000000000000000000000000000000000000000..561d3332d1f152a07de9449c1fc6be468bc4790e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/performance-tuning/2-sql/4-updating-statistics.md
@@ -0,0 +1,58 @@
+---
+title: 更新统计信息
+summary: 更新统计信息
+author: Liu Xu
+date: 2021-03-04
+---
+
+# 更新统计信息
+
+**在数据库中，统计信息是规划器生成计划的源数据。没有收集统计信息或者统计信息陈旧往往会造成执行计划严重劣化，从而导致性能问题**。
+
+<br/>
+
+## 背景信息
+
+ANALYZE语句可收集与数据库中表内容相关的统计信息，统计结果存储在系统表PG_STATISTIC中。查询优化器会使用这些统计数据，以生成最有效的执行计划。
+
+建议在执行了大批量插入/删除操作后，例行对表或全库执行ANALYZE语句更新统计信息。目前默认收集统计信息的采样比例是30000行（即: guc参数default_statistics_target默认设置为100），如果表的总行数超过一定行数（大于1600000），建议设置guc参数default_statistics_target为-2，即按2%收集样本估算统计信息。
+
+对于在批处理脚本或者存储过程中生成的中间表，也需要在完成数据生成之后显式的调用ANALYZE。
+
+对于表中多个列有相关性且查询中有同时基于这些列的条件或分组操作的情况，可尝试收集多列统计信息，以便查询优化器可以更准确地估算行数，并生成更有效的执行计划。
+
+<br/>
+
+## 操作步骤
+
+使用以下命令更新某个表或者整个database的统计信息。
+
+```sql
+--更新单个表的统计信息。
+ANALYZE tablename;
+--更新全库的统计信息。
+ANALYZE;
+```
+
+使用以下命令进行多列统计信息相关操作。
+
+```sql
+--收集tablename表的column_1、column_2列的多列统计信息。
+ANALYZE tablename ((column_1, column_2));
+
+--添加tablename表的column_1、column_2列的多列统计信息声明。
+ALTER TABLE tablename ADD STATISTICS ((column_1, column_2));
+
+--收集单列统计信息，并收集已声明的多列统计信息。
+ANALYZE tablename;
+
+--删除tablename表的column_1、column_2列的多列统计信息或其声明。
+ALTER TABLE tablename DELETE STATISTICS ((column_1, column_2));
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> 在使用ALTER TABLE tablename ADD STATISTICS语句添加了多列统计信息声明后，系统并不会立刻收集多列统计信息，而是在下次对该表或全库进行ANALYZE时，进行多列统计信息的收集。
+> 如果想直接收集多列统计信息，请使用ANALYZE命令进行收集。
+>
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+> 使用EXPLAIN查看各SQL的执行计划时，如果发现某个表SEQ SCAN的输出中rows=10，rows=10是系统给的默认值，有可能该表没有进行ANALYZE，需要对该表执行ANALYZE。
diff --git a/product/zh/docs-mogdb/v3.0/performance-tuning/2-sql/5-reviewing-and-modifying-a-table-definition.md b/product/zh/docs-mogdb/v3.0/performance-tuning/2-sql/5-reviewing-and-modifying-a-table-definition.md
new file mode 100644
index 0000000000000000000000000000000000000000..a2b8eeca6ddb2f113da80f30fbe1970d6ab5958a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/performance-tuning/2-sql/5-reviewing-and-modifying-a-table-definition.md
@@ -0,0 +1,73 @@
+---
+title: 审视和修改表定义
+summary: 审视和修改表定义
+author: Liu Xu
+date: 2021-03-04
+---
+
+# 审视和修改表定义
+
+<br/>
+
+## 审视和修改表定义概述
+
+好的表定义至少需要达到以下几个目标:
+
+1. **减少扫描数据数据量**。通过分区的剪枝机制可以实现该点。
+2. **尽量极少随机IO**。通过聚簇/局部聚簇可以实现该点。
+
+<br/>
+
+## 选择存储模型
+
+进行数据库设计时，表设计上的一些关键项将严重影响后续整库的查询性能。表设计对数据存储也有影响: 好的表设计能够减少I/O操作及最小化内存使用，进而提升查询性能。
+
+表的存储模型选择是表定义的第一步。客户业务属性是表的存储模型的决定性因素，依据下面表格选择适合当前业务的存储模型。
+
+| **存储模型** | **适用场景**                                                 |
+| :----------- | :----------------------------------------------------------- |
+| 行存         | 点查询（返回记录少，基于索引的简单查询）。增删改比较多的场景。 |
+| 列存         | 统计分析类查询（group , join多的场景）。                     |
+
+<br/>
+
+## 使用局部聚簇
+
+局部聚簇（Partial Cluster Key）是列存下的一种技术。这种技术可以通过min/max稀疏索引较快的实现基表扫描的filter过滤。Partial Cluster Key可以指定多列，但是一般不建议超过2列。Partial Cluster Key的选取原则:
+
+1. 受基表中的简单表达式约束。这种约束一般形如col op const，其中col为列名，op为操作符 =、>、>=、<=、<，const为常量值。
+2. 尽量采用选择度比较高（过滤掉更多数据）的简单表达式中的列。
+3. 尽量把选择度比较低的约束col放在Partial Cluster Key中的前面。
+4. 尽量把枚举类型的列放在Partial Cluster Key中的前面。
+
+<br/>
+
+## 使用分区表
+
+分区表是把逻辑上的一张表根据某种方案分成几张物理块进行存储。这张逻辑上的表称之为分区表，物理块称之为分区。分区表是一张逻辑表，不存储数据，数据实际是存储在分区上的。分区表和普通表相比具有以下优点:
+
+1. 改善查询性能: 对分区对象的查询可以仅搜索自己关心的分区，提高检索效率。
+2. 增强可用性: 如果分区表的某个分区出现故障，表在其他分区的数据仍然可用。
+3. 方便维护: 如果分区表的某个分区出现故障，需要修复数据，只修复该分区即可。
+
+**MogDB支持的分区表为范围分区表**。
+
+范围分区表: 将数据基于范围映射到每一个分区。这个范围是由创建分区表时指定的分区键决定的。分区键经常采用日期，例如将销售数据按照月份进行分区。
+
+<br/>
+
+## 选择数据类型
+
+高效数据类型，主要包括以下三方面:
+
+- **尽量使用执行效率比较高的数据类型**
+
+    一般来说整型数据运算（包括=、＞、＜、≧、≦、≠等常规的比较运算，以及group by）的效率比字符串、浮点数要高。比如某客户场景中对列存表进行点查询，filter条件在一个numeric列上，执行时间为10+s；修改numeric为int类型之后，执行时间缩短为1.8s左右。
+
+- **尽量使用短字段的数据类型**
+
+    长度较短的数据类型不仅可以减小数据文件的大小，提升IO性能；同时也可以减小相关计算时的内存消耗，提升计算性能。比如对于整型数据，如果可以用smallint就尽量不用int，如果可以用int就尽量不用bigint。
+
+- **使用一致的数据类型**
+
+    表关联列尽量使用相同的数据类型。如果表关联列数据类型不同，数据库必须动态地转化为相同的数据类型进行比较，这种转换会带来一定的性能开销。
diff --git a/product/zh/docs-mogdb/v3.0/performance-tuning/2-sql/6-typical-sql-optimization-methods.md b/product/zh/docs-mogdb/v3.0/performance-tuning/2-sql/6-typical-sql-optimization-methods.md
new file mode 100644
index 0000000000000000000000000000000000000000..305c206e82f7f2ffc9ca5013b21fbbf9b5fde6ef
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/performance-tuning/2-sql/6-typical-sql-optimization-methods.md
@@ -0,0 +1,722 @@
+---
+title: 典型SQL调优
+summary: 典型SQL调优
+author: Liu Xu
+date: 2021-03-04
+---
+
+# 典型SQL调优
+
+**SQL调优是一个不断分析与尝试的过程: 试跑Query，判断性能是否满足要求；如果不满足要求，则通过查看执行计划分析原因并进行针对性优化；然后重新试跑和优化，直到满足性能目标**。
+
+<br/>
+
+## SQL自诊断
+
+用户在执行查询或者执行INSERT/DELETE/UPDATE/CREATE TABLE AS语句时，可能会遇到性能问题。这种情况下，通过查询PG_CONTROL_GROUP_CONFIG，GS_SESSION_MEMORY_DETAIL视图的warning字段可以获得对应查询可能导致性能问题的告警信息，为性能调优提供参考。
+
+SQL自诊断的告警类型与resource_track_level的设置有关系。如果resource_track_level设置为query，则可以诊断多列/单列统计信息未收集和SQL不下推的告警。如果resource_track_level设置为operator，则可以诊断所有的告警场景。
+
+SQL自诊断的诊断范围与resource_track_cost的设置有关系。当SQL的代价大于resource_track_cost时，SQL才会被诊断。SQL的代价可以通过explain来确认。
+
+<br/>
+
+### 告警场景
+
+目前支持对多列/单列统计信息未收集导致性能问题的场景上报告警。
+
+如果存在单列或者多列统计信息未收集，则上报相关告警。调优方法可以参考更新统计信息和统计信息调优。
+
+告警信息示例:
+
+整表的统计信息未收集：
+
+```
+Statistic Not Collect:
+    schema_test.t1
+```
+
+单列统计信息未收集：
+
+```
+Statistic Not Collect:
+    schema_test.t2(c1,c2)
+```
+
+多列统计信息未收集：
+
+```
+Statistic Not Collect:
+    schema_test.t3((c1,c2))
+```
+
+单列和多列统计信息未收集：
+
+```
+Statistic Not Collect:
+    schema_test.t4(c1,c2)    schema_test.t4((c1,c2))
+```
+
+<br/>
+
+### 规格约束
+
+1. 告警字符串长度上限为2048。如果告警信息超过这个长度（例如存在大量未收集统计信息的超长表名，列名等信息）则不告警，只上报warning:
+
+    ```
+    WARNING, "Planner issue report is truncated, the rest of planner issues will be skipped"
+    ```
+
+2. 如果query存在limit节点（即查询语句中包含limit），则不会上报limit节点以下的Operator级别的告警。
+
+<br/>
+
+## 子查询调优
+
+**应用程序通过SQL语句来操作数据库时会使用大量的子查询，这种写法比直接对两个表做连接操作在结构上和思路上更清晰，尤其是在一些比较复杂的查询语句中，子查询有更完整、更独立的语义，会使SQL对业务逻辑的表达更清晰更容易理解，因此得到了广泛的应用**。
+
+MogDB根据子查询在SQL语句中的位置把子查询分成了子查询、子链接两种形式。
+
+- 子查询SubQuery: 对应于查询解析树中的范围表RangeTblEntry，更通俗一些指的是出现在FROM语句后面的独立的SELECT语句。
+
+- 子链接SubLink: 对应于查询解析树中的表达式，更通俗一些指的是出现在where/on子句、targetlist里面的语句。
+
+    综上，对于查询解析树而言，SubQuery的本质是范围表、而SubLink的本质是表达式。针对SubLink场景而言，由于SubLink可以出现在约束条件、表达式中，按照MogDB对sublink的实现，sublink可以分为以下几类:
+
+  - exist_sublink: 对应EXIST、NOT EXIST语句
+  
+  - any_sublink: 对应op ALL(select…)语句，其中OP可以是IN，&lt;，&gt;，=操作符
+  
+  - all_sublink: 对应op ALL(select…)语句，其中OP可以是IN，&lt;，&gt;，=操作符
+  
+  - rowcompare_sublink: 对应record op (select …)语句
+
+  - expr_sublink: 对应(SELECT with single targetlist item …)语句
+
+  - array_sublink: 对应ARRAY(select…)语句
+
+  - cte_sublink: 对应with query(…)语句
+
+    其中OLAP、HTAP场景中常用的sublink为exist_sublink、any_sublink，在MogDB的优化引擎中对其应用场景做了优化（子链接提升），由于SQL语句中子查询的使用的灵活性，会带来SQL子查询过于复杂造成性能问题。子查询从大类上来看，分为非相关子查询和相关子查询:
+
+  - **非相关子查询None-Correlated SubQuery**
+  
+    子查询的执行不依赖于外层父查询的任何属性值。这样子查询具有独立性，可独自求解，形成一个子查询计划先于外层的查询求解。
+  
+    例如:
+  
+    ```sql
+    select t1.c1,t1.c2
+    from t1
+    where t1.c1 in (
+        select c2
+        from t2
+        where t2.c2 IN (2,3,4)
+    );
+                                  QUERY PLAN
+    ----------------------------------------------------------------
+    Hash Join
+        Hash Cond: (t1.c1 = t2.c2)
+        ->  Seq Scan on t1
+            Filter: (c1 = ANY ('{2,3,4}'::integer[]))
+      ->  Hash
+            ->  HashAggregate
+              Group By Key: t2.c2
+                    ->  Seq Scan on t2
+                      Filter: (c2 = ANY ('{2,3,4}'::integer[]))
+        (9 rows)
+    ```
+    
+  - **相关子查询Correlated-SubQuery**
+  
+    子查询的执行依赖于外层父查询的一些属性值（如下列示例t2.c1 = t1.c1条件中的t1.c1）作为内层查询的一个AND-ed条件。这样的子查询不具备独立性，需要和外层查询按分组进行求解。
+  
+    例如:
+  
+    ```sql
+     select t1.c1,t1.c2
+        from t1
+        where t1.c1 in (
+            select c2
+            from t2
+            where t2.c1 = t1.c1 AND t2.c2 in (2,3,4)
+        );
+                                       QUERY PLAN
+        ------------------------------------------------------------------------
+         Seq Scan on t1
+           Filter: (SubPlan 1)
+           SubPlan 1
+             ->  Seq Scan on t2
+                   Filter: ((c1 = t1.c1) AND (c2 = ANY ('{2,3,4}'::integer[])))
+        (5 rows)  
+    ```
+
+MogDB对SubLink的优化
+
+针对SubLink的优化策略主要是让内层的子查询提升（pullup），能够和外表直接做关联查询，从而避免生成SubPlan+Broadcast內表的执行计划。判断子查询是否存在性能风险，可以通过explain查询语句查看Sublink的部分是否被转换成SubPlan的执行计划。
+
+例如:
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/typical-sql-optimization-methods-1.png)
+
+箭头右侧执行计划应替换成下面的执行计划:
+
+```sql
+QUERY PLAN
+--------------------------------
+Seq Scan on t1
+Filter: (SubPlan 1)
+SubPlan 1
+->  Seq Scan on t2
+Filter: (c1 = t1.c1)
+(5 rows)
+```
+
+- **目前MogDB支持的Sublink-Release场景**
+
+  - IN-Sublink无相关条件
+
+    - 不能包含上一层查询的表中的列（可以包含更高层查询表中的列）。
+
+    - 不能包含易变函数。
+
+        ![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/typical-sql-optimization-methods-2.png)
+
+        箭头右侧执行计划应替换成下面的执行计划:
+        
+        ```sql
+        QUERY PLAN
+        --------------------------------------
+        Hash Join
+        Hash Cond: (t1.c1 = t2.c2)
+        ->  Seq Scan on t1
+        ->  Hash
+        ->  HashAggregate
+        Group By Key: t2.c2
+        ->  Seq Scan on t2
+        Filter: (c1 = 1)
+        (8 rows)
+        ```
+
+  - Exist-Sublink包含相关条件
+    Where子句中必须包含上一层查询的表中的列，子查询的其它部分不能含有上层查询的表中的列。其它限制如下。
+
+    - 子查询必须有from子句。
+
+    - 子查询不能含有with子句。
+
+    - 子查询不能含有聚集函数。
+
+    - 子查询里不能包含集合操作、排序、limit、windowagg、having操作。
+
+    - 不能包含易变函数。
+
+    - 不能包含易变函数。
+
+        ![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/typical-sql-optimization-methods-3.png)
+
+        箭头右侧执行计划应替换成下面的执行计划:
+        
+        ```sql
+        QUERY PLAN
+        --------------------------------
+        Hash Join
+        Hash Cond: (t1.c1 = t2.c1)
+        -> Seq Scan on t1
+        -> Hash
+        -> HashAggregate
+        Group By Key: t2.c1
+        -> Seq Scan on t2
+        (7 rows)
+        ```
+
+  - 包含聚集函数的等值相关子查询的提升
+
+    子查询的where条件中必须含有来自上一层的列，而且此列必须和子查询本层涉及表中的列做相等判断，且这些条件必须用and连接。其它地方不能包含上层的列。其它限制条件如下。
+
+    - 子查询中where条件包含的表达式（列名）必须是表中的列。
+
+    - 子查询的Select关键字后，必须有且仅有一个输出列，此输出列必须是聚集函数（如max），并且聚集函数的参数（t2.c2）不能是来自外层表（t1）中的列。聚集函数不能是count。
+
+        例如，下列示例可以提升。
+
+        ```sql
+        select * from t1 where c1 >(
+               select max(t2.c1) from t2 where t2.c1=t1.c1
+        );
+        ```
+
+        下列示例不能提升，因为子查询没有聚集函数。
+
+        ```sql
+        select * from t1 where c1 >(
+               select  t2.c1 from t2 where t2.c1=t1.c1
+        );
+        ```
+
+        下列示例不能提升，因为子查询有两个输出列。
+
+        ```sql
+        select * from t1 where (c1,c2) >(
+               select  max(t2.c1),min(t2.c2) from t2 where t2.c1=t1.c1
+        );
+        ```
+
+    - 子查询必须是from子句。
+
+    - 子查询中不能有groupby、having、集合操作。
+
+    - 子查询只能是inner join。
+
+        例如: 下列示例不能提升。
+
+        ```sql
+        select * from t1 where c1 >(
+               select max(t2.c1) from t2 full join t3 on (t2.c2=t3.c2) where t2.c1=t1.c1
+        );
+        ```
+
+    - 子查询的targetlist中不能包含返回set的函数。
+
+    - 子查询的where条件中必须含有来自上一层的列，而且此列必须和子查询层涉及表中的列做相等判断，且这些条件必须用and连接。其它地方不能包含上层的上层中的列。例如: 下列示例中的最内层子链接可以提升。
+
+        ```sql
+        select * from t3 where t3.c1=(
+                select t1.c1
+                from t1 where c1 >(
+                        select max(t2.c1) from t2 where t2.c1=t1.c1
+        ));
+        ```
+
+        基于上面的示例，再加一个条件，则不能提升，因为最内侧子查询引用了上层中的列。示例如下:
+
+        ```sql
+        select * from t3 where t3.c1=(
+                select t1.c1
+                from t1 where c1 >(
+                       select max(t2.c1) from t2 where t2.c1=t1.c1 and t3.c1>t2.c2
+        ));
+        ```
+
+  - 提升OR子句中的SubLink
+
+    当WHERE过滤条件中有OR连接的EXIST相关SubLink，
+
+    例如:
+
+    ```sql
+    select a, c from t1
+    where t1.a = (select avg(a) from t3 where t1.b = t3.b) or
+    exists (select * from t4 where t1.c = t4.c);
+    ```
+
+    将OR-ed连接的EXIST相关子查询OR字句的提升过程:
+
+    1. 提取where条件中，or子句中的opExpr。为: t1.a = (select avg(a) from t3 where t1.b = t3.b)
+
+    2. 这个op操作中包含subquery，判断是否可以提升，如果可以提升，重写subquery为: select avg(a), t3.b from t3 group by t3.b，生成not null条件t3.b is not null，并将这个opexpr用这个not null条件替换。此时SQL变为:
+
+       ```sql
+       select a, c
+           from t1 left join (select avg(a) avg, t3.b from t3 group by t3.b)  as t3 on (t1.a = avg and t1.b = t3.b)
+           where t3.b is not null or exists (select * from t4 where t1.c = t4.c);
+       ```
+
+    3. 再次提取or子句中的exists sublink，exists (select * from t4 where t1.c = t4.c)，判断是否可以提升，如果可以提升，转换subquery为: select t4.c from t4 group by t4.c生成NotNull条件t4.c is not null提升查询，SQL变为:
+
+       ```sql
+        select a, c
+           from t1 left join (select avg(a) avg, t3.b from t3 group by t3.b)  as t3 on (t1.a = avg and t1.b = t3.b)
+           left join (select t4.c from t4 group by t4.c) where t3.b is not null or t4.c is not null;
+       ```
+
+- **目前MogDB不支持的Sublink-Release场景**
+
+    除了以上场景之外都不支持Sublink提升，因此关联子查询会被计划成SubPlan+Broadcast的执行计划，当inner表的数据量较大时则会产生性能风险。
+
+    如果相关子查询中跟外层的两张表做join，那么无法提升该子查询，需要通过将父SQL创建成with子句，然后再跟子查询中的表做相关子查询查询。
+
+    例如:
+
+    ```sql
+    select distinct t1.a, t2.a
+    from t1 left join t2 on t1.a=t2.a and not exists (select a,b from test1 where test1.a=t1.a and test1.b=t2.a);
+    ```
+
+    改写为
+
+    ```sql
+    with temp as
+    (
+            select * from (select t1.a as a, t2.a as b from t1 left join t2 on t1.a=t2.a)
+    )
+    select distinct a,b
+    from temp
+    where not exists (select a,b from test1 where temp.a=test1.a and temp.b=test1.b);
+    ```
+
+  - 出现在targetlist里的相关子查询无法提升(不含count)
+
+    例如：
+
+    ```sql
+    explain (costs off)
+    select (select c2 from t2 where t1.c1 = t2.c1) ssq, t1.c2
+    from t1
+    where t1.c2 > 10;
+    ```
+
+    执行计划为:
+
+    ```sql
+    explain (costs off)
+    select (select c2 from t2 where t1.c1 = t2.c1) ssq, t1.c2
+    from t1
+    where t1.c2 > 10;
+               QUERY PLAN
+    --------------------------------
+     Seq Scan on t1
+       Filter: (c2 > 10)
+       SubPlan 1
+         ->  Seq Scan on t2
+               Filter: (t1.c1 = c1)
+    (5 rows)
+    ```
+
+    由于相关子查询出现在targetlist（查询返回列表）里，对于t1.c1=t2.c1不匹配的场景仍然需要输出值，因此使用left-outerjoin关联T1&T2确保t1.c1=t2.c1在不匹配时，子SSQ能够返回不匹配的补空值。
+
+    > **![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) 说明:**
+    > SSQ和CSSQ的解释如下:
+    >
+    > - SSQ: ScalarSubQuery一般指返回1行1列scalar值的sublink，简称SSQ。
+    > - CSSQ: Correlated-ScalarSubQuery和SSQ相同不过是指包含相关条件的SSQ。
+
+    上述SQL语句可以改写为:
+
+    ```sql
+    with ssq as
+    (
+        select t2.c2 from t2
+    )
+    select ssq.c2, t1.c2
+    from t1 left join ssq on t1.c1 = ssq.c2
+    where t1.c2 > 10;
+    ```
+
+    改写后的执行计划为:
+
+    ```sql
+     QUERY PLAN
+    ---------------------------------
+    Hash Right Join
+      Hash Cond: (ssq.c2 = t1.c1)
+      CTE ssq
+        ->  Seq Scan on t2
+      ->  CTE Scan on ssq
+      ->  Hash
+            ->  Seq Scan on t1
+                  Filter: (c2 > 10)
+    (8 rows)
+    ```
+
+    可以看到出现在SSQ返回列表里的相关子查询SSQ，已经被提升成Right Join，从而避免当內表T2较大时出现SubPlan计划导致性能变差。
+
+  - 出现在targetlist里的相关子查询无法提升（带count）
+
+    例如:
+
+    ```sql
+    select (select count(*) from t2 where t2.c1=t1.c1) cnt, t1.c1, t3.c1
+    from t1,t3
+    where t1.c1=t3.c1 order by cnt, t1.c1;
+    ```
+
+    执行计划为
+
+    ```sql
+     QUERY PLAN
+    --------------------------------------------
+    Sort
+      Sort Key: ((SubPlan 1)), t1.c1
+      ->  Hash Join
+            Hash Cond: (t1.c1 = t3.c1)
+            ->  Seq Scan on t1
+            ->  Hash
+                  ->  Seq Scan on t3
+            SubPlan 1
+              ->  Aggregate
+                    ->  Seq Scan on t2
+                          Filter: (c1 = t1.c1)
+    (11 rows)
+    ```
+
+    由于相关子查询出现在targetlist（查询返回列表）里，对于t1.c1=t2.c1不匹配的场景仍然需要输出值，因此使用left-outerjoin关联T1&T2确保t1.c1=t2.c1在不匹配时子SSQ能够返回不匹配的补空值，但是这里带了count语句及时在t1.c1=t2.t1不匹配时需要输出0，因此可以使用一个case-when NULL then 0 else count(*)来代替。
+
+    上述SQL语句可以改写为:
+
+    ```sql
+    with ssq as
+    (
+        select count(*) cnt, c1 from t2 group by c1
+    )
+    select case when
+                ssq.cnt is null then 0
+                else ssq.cnt
+           end cnt, t1.c1, t3.c1
+    from t1 left join ssq on ssq.c1 = t1.c1,t3
+    where t1.c1 = t3.c1
+    order by ssq.cnt, t1.c1;
+    ```
+
+    改写后的执行计划为
+
+    ```sql
+                  QUERY PLAN
+    -------------------------------------------
+    Sort
+      Sort Key: ssq.cnt, t1.c1
+      CTE ssq
+        ->  HashAggregate
+              Group By Key: t2.c1
+              ->  Seq Scan on t2
+      ->  Hash Join
+            Hash Cond: (t1.c1 = t3.c1)
+            ->  Hash Left Join
+                  Hash Cond: (t1.c1 = ssq.c1)
+                  ->  Seq Scan on t1
+                  ->  Hash
+                        ->  CTE Scan on ssq
+          ->  Hash
+                  ->  Seq Scan on t3
+    (15 rows)
+    ```
+
+  - 相关条件为不等值场景
+
+    例如:
+    
+    ```sql
+    select t1.c1, t1.c2
+    from t1
+    where t1.c1 = (select agg() from t2.c2 > t1.c2);
+    ```
+  
+    对于非等值相关条件的SubLink目前无法提升，从语义上可以通过做2次join（一次CorrelationKey，一次rownum自关联）达到提升改写的目的。
+
+    改写方案有两种。
+
+    - 子查询改写方式
+  
+        ```sql
+        select t1.c1, t1.c2
+        from t1, (
+            select t1.rowid, agg() aggref
+            from t1,t2
+          where t1.c2 > t2.c2 group by t1.rowid
+        ) dt /* derived table */
+        where t1.rowid = dt.rowid AND t1.c1 = dt.aggref;
+        ```
+  
+    - CTE改写方式
+  
+        ```sql
+        WITH dt as
+        (
+            select t1.rowid, agg() aggref
+            from t1,t2
+            where t1.c2 > t2.c2 group by t1.rowid
+        )
+        select t1.c1, t1.c2
+        from t1, derived_table
+        where t1.rowid = derived_table.rowid AND
+        t1.c1 = derived_table.aggref;
+        ```
+  
+    > **须知:**
+    >
+    > - 对于AGG类型为count(\*)时需要进行CASE-WHEN对没有match的场景补0处理，非COUNT(\*)场景NULL处理。
+    > - CTE改写方式如果有sharescan支持性能上能够更优。
+
+<br/>
+
+### 更多优化示例
+
+**示例:**修改select语句，将子查询修改为和主表的join，或者修改为可以提升的subquery，但是在修改前后需要保证语义的正确性。
+
+```sql
+explain (costs off) select * from t1 where t1.c1 in (select t2.c1 from t2 where t1.c1 = t2.c2);
+           QUERY PLAN
+--------------------------------
+ Seq Scan on t1
+   Filter: (SubPlan 1)
+   SubPlan 1
+     ->  Seq Scan on t2
+           Filter: (t1.c1 = c2)
+(5 rows)
+```
+
+上面事例计划中存在一个subPlan，为了消除这个subPlan可以修改语句为:
+
+```sql
+explain (costs off) select * from t1 where exists (select t2.c1 from t2 where t1.c1 = t2.c2 and t1.c1 = t2.c1);
+                QUERY PLAN
+------------------------------------------
+ Hash Join
+   Hash Cond: (t1.c1 = t2.c2)
+   ->  Seq Scan on t1
+   ->  Hash
+         ->  HashAggregate
+               Group By Key: t2.c2, t2.c1
+               ->  Seq Scan on t2
+                     Filter: (c2 = c1)
+(8 rows)
+```
+
+从计划可以看出，subPlan消除了，计划变成了两个表的hash join，这样会大大提高执行效率。
+
+<br/>
+
+## 统计信息调优
+
+MogDB是基于代价估算生成的最优执行计划。优化器需要根据analyze收集的统计信息行数估算和代价估算，因此统计信息对优化器行数估算和代价估算起着至关重要的作用。通过analyze收集全局统计信息，主要包括: pg_class表中的relpages和reltuples；pg_statistic表中的stadistinct、stanullfrac、stanumbersN、stavaluesN、histogram_bounds等。
+
+<br/>
+
+### 实例分析1: 未收集统计信息导致查询性能差
+
+在很多场景下，由于查询中涉及到的表或列没有收集统计信息，会对查询性能有很大的影响。
+
+表结构如下所示:
+
+```sql
+CREATE TABLE LINEITEM
+(
+L_ORDERKEY         BIGINT        NOT NULL
+, L_PARTKEY        BIGINT        NOT NULL
+, L_SUPPKEY        BIGINT        NOT NULL
+, L_LINENUMBER     BIGINT        NOT NULL
+, L_QUANTITY       DECIMAL(15,2) NOT NULL
+, L_EXTENDEDPRICE  DECIMAL(15,2) NOT NULL
+, L_DISCOUNT       DECIMAL(15,2) NOT NULL
+, L_TAX            DECIMAL(15,2) NOT NULL
+, L_RETURNFLAG     CHAR(1)       NOT NULL
+, L_LINESTATUS     CHAR(1)       NOT NULL
+, L_SHIPDATE       DATE          NOT NULL
+, L_COMMITDATE     DATE          NOT NULL
+, L_RECEIPTDATE    DATE          NOT NULL
+, L_SHIPINSTRUCT   CHAR(25)      NOT NULL
+, L_SHIPMODE       CHAR(10)      NOT NULL
+, L_COMMENT        VARCHAR(44)   NOT NULL
+) with (orientation = column, COMPRESSION = MIDDLE);
+
+CREATE TABLE ORDERS
+(
+O_ORDERKEY        BIGINT        NOT NULL
+, O_CUSTKEY       BIGINT        NOT NULL
+, O_ORDERSTATUS   CHAR(1)       NOT NULL
+, O_TOTALPRICE    DECIMAL(15,2) NOT NULL
+, O_ORDERDATE     DATE NOT NULL
+, O_ORDERPRIORITY CHAR(15)      NOT NULL
+, O_CLERK         CHAR(15)      NOT NULL
+, O_SHIPPRIORITY  BIGINT        NOT NULL
+, O_COMMENT       VARCHAR(79)   NOT NULL
+)with (orientation = column, COMPRESSION = MIDDLE);
+```
+
+查询语句如下所示:
+
+```sql
+explain verbose select
+count(*) as numwait
+from
+lineitem l1,
+orders
+where
+o_orderkey = l1.l_orderkey
+and o_orderstatus = 'F'
+and l1.l_receiptdate > l1.l_commitdate
+and not exists (
+select
+*
+from
+lineitem l3
+where
+l3.l_orderkey = l1.l_orderkey
+and l3.l_suppkey <> l1.l_suppkey
+and l3.l_receiptdate > l3.l_commitdate
+)
+order by
+numwait desc;
+```
+
+当出现该问题时，可以通过如下方法确认查询中涉及到的表或列有没有做过analyze收集统计信息。
+
+1. 通过explain verbose执行query分析执行计划时会提示WARNING信息，如下所示:
+
+    ```bash
+    WARNING:Statistics in some tables or columns(public.lineitem.l_receiptdate, public.lineitem.l_commitdate, public.lineitem.l_orderkey, public.lineitem.l_suppkey, public.orders.o_orderstatus, public.orders.o_orderkey) are not collected.
+    HINT:Do analyze for them in order to generate optimized plan.
+    ```
+
+2. 可以通过在pg_log目录下的日志文件中查找以下信息来确认是当前执行的query是否由于没有收集统计信息导致查询性能变差。
+
+    ```bash
+    2017-06-14 17:28:30.336 CST 140644024579856 20971684 [BACKEND] LOG:Statistics in some tables or columns(public.lineitem.l_receiptdate, public.lineitem.l_commitdate, public.lineitem.l_orderkey, public.linei
+    tem.l_suppkey, public.orders.o_orderstatus, public.orders.o_orderkey) are not collected.
+    2017-06-14 17:28:30.336 CST 140644024579856 20971684 [BACKEND] HINT:Do analyze for them in order to generate optimized plan.
+    ```
+
+当通过以上方法查看到哪些表或列没有做analyze，可以通过对WARNING或日志中上报的表或列做analyze可以解决由于为收集统计信息导致查询变慢的问题。
+
+<br/>
+
+## 算子级调优
+
+一个查询语句要经过多个算子步骤才会输出最终的结果。由于个别算子耗时过长导致整体查询性能下降的情况比较常见。这些算子是整个查询的瓶颈算子。通用的优化手段是EXPLAIN ANALYZE/PERFORMANCE命令查看执行过程的瓶颈算子，然后进行针对性优化。
+
+如下面的执行过程信息中，Hashagg算子的执行时间占总时间的: (51016-13535)/ 56476 ≈66%，此处Hashagg算子就是这个查询的瓶颈算子，在进行性能优化时应当优先考虑此算子的优化。
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/typical-sql-optimization-methods-4.png)
+
+<br/>
+
+### 算子级调优示例
+
+**示例1：**基表扫描时，对于点查或者范围扫描等过滤大量数据的查询，如果使用SeqScan全表扫描会比较耗时，可以在条件列上建立索引选择IndexScan进行索引扫描提升扫描效率。
+
+```sql
+postgres=#  explain (analyze on, costs off) select * from store_sales where ss_sold_date_sk = 2450944;
+ id |             operation          |       A-time        | A-rows | Peak Memory  | A-width
+----+--------------------------------+---------------------+--------+--------------+---------
+  1 | ->  Streaming (type: GATHER)   | 3666.020            |   3360 | 195KB        |
+  2 |    ->  Seq Scan on store_sales | [3594.611,3594.611] |   3360 | [34KB, 34KB] |
+(2 rows)
+
+ Predicate Information (identified by plan id)
+-----------------------------------------------
+   2 --Seq Scan on store_sales
+         Filter: (ss_sold_date_sk = 2450944)
+         Rows Removed by Filter: 4968936
+postgres=#  create index idx on store_sales_row(ss_sold_date_sk);
+CREATE INDEX
+postgres=#  explain (analyze on, costs off) select * from store_sales_row where ss_sold_date_sk = 2450944;
+ id |                   operation                    |     A-time      | A-rows | Peak Memory  | A-width
+----+------------------------------------------------+-----------------+--------+--------------+----------
+  1 | ->  Streaming (type: GATHER)                   | 81.524          |   3360 | 195KB        |
+  2 |    ->  Index Scan using idx on store_sales_row | [13.352,13.352] |   3360 | [34KB, 34KB] |
+(2 rows)
+```
+
+上述例子中，全表扫描返回3360条数据，过滤掉大量数据，在ss_sold_date_sk列上建立索引后，使用IndexScan扫描效率显著提高，从3.6秒提升到13毫秒。
+
+**示例2：**如果从执行计划中看，两表join选择了NestLoop，而实际行数比较大时，NestLoop Join可能执行比较慢。如下的例子中NestLoop耗时181秒，如果设置参数enable_mergejoin=off关掉Merge Join，同时设置参数enable_nestloop=off关掉NestLoop，让优化器选择HashJoin，则Join耗时提升至200多毫秒。
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/typical-sql-optimization-methods-5.png)
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/typical-sql-optimization-methods-6.png)
+
+**示例3**：通常情况下Agg选择HashAgg性能较好，如果大结果集选择了Sort+GroupAgg，则需要设置enable_sort=off，HashAgg耗时明显优于Sort+GroupAgg。
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/typical-sql-optimization-methods-7.png)
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/typical-sql-optimization-methods-8.png)
diff --git a/product/zh/docs-mogdb/v3.0/performance-tuning/2-sql/7-experience-in-rewriting-sql-statements.md b/product/zh/docs-mogdb/v3.0/performance-tuning/2-sql/7-experience-in-rewriting-sql-statements.md
new file mode 100644
index 0000000000000000000000000000000000000000..92c00488c3027565ec0729c912219da0083c1101
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/performance-tuning/2-sql/7-experience-in-rewriting-sql-statements.md
@@ -0,0 +1,63 @@
+---
+title: SQL语句改写规则
+summary: SQL语句改写规则
+author: Liu Xu
+date: 2021-03-04
+---
+
+# SQL语句改写规则
+
+根据数据库的SQL执行机制以及大量的实践，总结发现: 通过一定的规则调整SQL语句，在保证结果正确的基础上，能够提高SQL执行效率。如果遵守这些规则，常常能够大幅度提升业务查询效率。
+
+- **使用union all代替union**
+
+    union在合并两个集合时会执行去重操作，而union all则直接将两个结果集合并、不执行去重。执行去重会消耗大量的时间，因此，在一些实际应用场景中，如果通过业务逻辑已确认两个集合不存在重叠，可用union all替代union以便提升性能。
+
+- **join列增加非空过滤条件**
+
+    若join列上的NULL值较多，则可以加上is not null过滤条件，以实现数据的提前过滤，提高join效率。
+
+- **not in转not exists**
+
+    not in语句需要使用nestloop anti join来实现，而not exists则可以通过hash anti join来实现。在join列不存在null值的情况下，not exists和not in等价。因此在确保没有null值时，可以通过将not in转换为not exists，通过生成hash join来提升查询效率。
+
+    如下所示，如果t2.d2字段中没有null值（t2.d2字段在表定义中not null）查询可以修改为
+
+    ```sql
+    SELECT * FROM t1 WHERE  NOT EXISTS (SELECT * FROM t2 WHERE t1.c1=t2.d2);
+    ```
+
+    产生的计划如下:
+
+    ```sql
+    QUERY PLAN
+    ------------------------------
+    Hash Anti Join
+    Hash Cond: (t1.c1 = t2.d2)
+    ->  Seq Scan on t1
+    ->  Hash
+    ->  Seq Scan on t2
+    (5 rows)
+    ```
+
+- **选择hashagg。**
+
+    查询中GROUP BY语句如果生成了groupagg+sort的plan性能会比较差，可以通过加大work_mem的方法生成hashagg的plan，因为不用排序而提高性能。
+
+- **尝试将函数替换为case语句。**
+
+    MogDB函数调用性能较低，如果出现过多的函数调用导致性能下降很多，可以根据情况把可下推函数的函数改成CASE表达式。
+
+- **避免对索引使用函数或表达式运算。**
+
+    对索引使用函数或表达式运算会停止使用索引转而执行全表扫描。
+
+- **尽量避免在where子句中使用!=或&lt;&gt;操作符、null值判断、or连接、参数隐式转换。**
+
+- **对复杂SQL语句进行拆分。**
+
+    对于过于复杂并且不易通过以上方法调整性能的SQL可以考虑拆分的方法，把SQL中某一部分拆分成独立的SQL并把执行结果存入临时表，拆分常见的场景包括但不限于:
+
+  - 作业中多个SQL有同样的子查询，并且子查询数据量较大。
+  - Plan cost计算不准，导致子查询hash bucket太小，比如实际数据1000W行，hash bucket只有1000。
+  - 函数（如substr,to_number）导致大数据量子查询选择度计算不准。
diff --git a/product/zh/docs-mogdb/v3.0/performance-tuning/2-sql/8-resetting-key-parameters-during-sql-tuning.md b/product/zh/docs-mogdb/v3.0/performance-tuning/2-sql/8-resetting-key-parameters-during-sql-tuning.md
new file mode 100644
index 0000000000000000000000000000000000000000..fe97def4f0e3cac4fad4cc8481dc760d2e4aa478
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/performance-tuning/2-sql/8-resetting-key-parameters-during-sql-tuning.md
@@ -0,0 +1,22 @@
+---
+title: SQL调优关键参数调整
+summary: SQL调优关键参数调整
+author: Liu Xu
+date: 2021-03-04
+---
+
+# SQL调优关键参数调整
+
+| 参数/参考值             | 描述       |
+| :---------------------- | :-------------------------------------------|
+| enable_nestloop=on      | 控制查询优化器对嵌套循环连接（Nest Loop Join）类型的使用。当设置为"on"后，优化器优先使用Nest Loop Join；当设置为"off"后，优化器在存在其他方法时将优先选择其他方法。<br />说明:<br />如果只需要在当前数据库连接（即当前Session）中临时更改该参数值，则只需要在SQL语句中执行如下命令: <br />*SET enable_nestloop to off;*<br />此参数默认设置为"on"，但实际调优中应根据情况选择是否关闭。一般情况下，在三种join方式（Nested Loop、Merge Join和Hash Join）里，Nested Loop性能较差，实际调优中可以选择关闭。 |
+| enable_bitmapscan=on    | 控制查询优化器对位图扫描规划类型的使用。设置为"on"，表示使用；设置为"off"，表示不使用。<br />说明：<br />如果只需要在当前数据库连接（即当前Session）中临时更改该参数值，则只需要在SQL语句中执行命令如下命令: <br />*SET enable_bitmapscan to off;*<br />bitmapscan扫描方式适用于"where a > 1 and b > 1"且a列和b列都有索引这种查询条件，但有时其性能不如indexscan。因此，现场调优如发现查询性能较差且计划中有bitmapscan算子，可以关闭bitmapscan，看性能是否有提升。                                 |
+| enable_hashagg=on       | 控制优化器对Hash聚集规划类型的使用。                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| enable_hashjoin=on      | 控制优化器对Hash连接规划类型的使用。                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| enable_mergejoin=on     | 控制优化器对融合连接规划类型的使用。                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| enable_indexscan=on     | 控制优化器对索引扫描规划类型的使用。                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| enable_indexonlyscan=on | 控制优化器对仅索引扫描规划类型的使用。                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| enable_seqscan=on       | 控制优化器对顺序扫描规划类型的使用。完全消除顺序扫描是不可能的，但是关闭这个变量会让优化器在存在其他方法的时候优先选择其他方法。                                                                                                                                                                                                                                                                                                                                                                   |
+| enable_sort=on          | 控制优化器使用的排序步骤。该设置不可能完全消除明确的排序，但是关闭这个变量可以让优化器在存在其他方法的时候优先选择其他方法。                                                                                                                                                                                                                                                                                                                                                                       |
+| rewrite_rule            | 控制优化器是否启用LAZY_AGG和MAGIC_SET重写规则。                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| sql_beta_feature        | 控制优化器是否启用。SEL_SEMI_POISSON/SEL_EXPR_INSTR/PARAM_PATH_GEN/RAND_COST_OPT/PARAM_PATH_OPT/PAGE_EST_OPT/CANONICAL_PATHKEY/PARTITION_OPFUSION测试功能。                                                                                                                                                                                                                                           |
diff --git a/product/zh/docs-mogdb/v3.0/performance-tuning/2-sql/9-hint-based-tuning.md b/product/zh/docs-mogdb/v3.0/performance-tuning/2-sql/9-hint-based-tuning.md
new file mode 100644
index 0000000000000000000000000000000000000000..4f34de755189fbd2c77da466069ef720e7d0d986
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/performance-tuning/2-sql/9-hint-based-tuning.md
@@ -0,0 +1,749 @@
+---
+title: 使用Plan Hint进行调优
+summary: 使用Plan Hint进行调优
+author: Liu Xu
+date: 2021-03-04
+---
+
+# 使用Plan Hint进行调优
+
+<br/>
+
+## Plan Hint调优概述
+
+Plan Hint为用户提供了直接影响执行计划生成的手段，用户可以通过指定join顺序，join、scan方法，指定结果行数，等多个手段来进行执行计划的调优，以提升查询的性能。
+
+<br/>
+
+### 功能描述
+
+Plan Hint仅支持在SELECT关键字后通过如下形式指定:
+
+```sql
+/*+ <plan hint>*/
+```
+
+可以同时指定多个hint，之间使用空格分隔。hint只能hint当前层的计划，对于子查询计划的hint，需要在子查询的select关键字后指定hint。
+
+例如:
+
+```sql
+select /*+ <plan_hint1> <plan_hint2> */ * from t1, (select /*+ <plan_hint3> */ from t2) where 1=1;
+```
+
+其中，为外层查询的hint，为内层子查询的hint。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> 如果在视图定义（CREATE VIEW）时指定hint，则在该视图每次被应用时会使用该hint。
+> 当使用random plan功能（参数plan_mode_seed不为0）时，查询指定的plan hint不会被使用。
+
+<br/>
+
+### 支持范围
+
+当前版本Plan Hint支持的范围如下，后续版本会进行增强。
+
+- 指定Join顺序的Hint - leading hint
+- 指定Join方式的Hint，仅支持除semi/anti join，unique plan之外的常用hint。
+- 指定结果集行数的Hint
+- 指定Scan方式的Hint，仅支持常用的tablescan，indexscan和indexonlyscan的hint。
+- 指定子链接块名的Hint
+
+<br/>
+
+### 注意事项
+
+不支持Agg、Sort、Setop和Subplan的hint。
+
+<br/>
+
+### 示例
+
+本章节使用同一个语句进行示例，便于Plan Hint支持的各方法作对比，示例语句及不带hint的原计划如下所示:
+
+```sql
+create table store
+(
+    s_store_sk                integer               not null,
+    s_store_id                char(16)              not null,
+    s_rec_start_date          date                          ,
+    s_rec_end_date            date                          ,
+    s_closed_date_sk          integer                       ,
+    s_store_name              varchar(50)                   ,
+    s_number_employees        integer                       ,
+    s_floor_space             integer                       ,
+    s_hours                   char(20)                      ,
+    s_manager                 varchar(40)                   ,
+    s_market_id               integer                       ,
+    s_geography_class         varchar(100)                  ,
+    s_market_desc             varchar(100)                  ,
+    s_market_manager          varchar(40)                   ,
+    s_division_id             integer                       ,
+    s_division_name           varchar(50)                   ,
+    s_company_id              integer                       ,
+    s_company_name            varchar(50)                   ,
+    s_street_number           varchar(10)                   ,
+    s_street_name             varchar(60)                   ,
+    s_street_type             char(15)                      ,
+    s_suite_number            char(10)                      ,
+    s_city                    varchar(60)                   ,
+    s_county                  varchar(30)                   ,
+    s_state                   char(2)                       ,
+    s_zip                     char(10)                      ,
+    s_country                 varchar(20)                   ,
+    s_gmt_offset              decimal(5,2)                  ,
+    s_tax_precentage          decimal(5,2)                  ,
+    primary key (s_store_sk)
+);
+create table store_sales
+(
+    ss_sold_date_sk           integer                       ,
+    ss_sold_time_sk           integer                       ,
+    ss_item_sk                integer               not null,
+    ss_customer_sk            integer                       ,
+    ss_cdemo_sk               integer                       ,
+    ss_hdemo_sk               integer                       ,
+    ss_addr_sk                integer                       ,
+    ss_store_sk               integer                       ,
+    ss_promo_sk               integer                       ,
+    ss_ticket_number          integer               not null,
+    ss_quantity               integer                       ,
+    ss_wholesale_cost         decimal(7,2)                  ,
+    ss_list_price             decimal(7,2)                  ,
+    ss_sales_price            decimal(7,2)                  ,
+    ss_ext_discount_amt       decimal(7,2)                  ,
+    ss_ext_sales_price        decimal(7,2)                  ,
+    ss_ext_wholesale_cost     decimal(7,2)                  ,
+    ss_ext_list_price         decimal(7,2)                  ,
+    ss_ext_tax                decimal(7,2)                  ,
+    ss_coupon_amt             decimal(7,2)                  ,
+    ss_net_paid               decimal(7,2)                  ,
+    ss_net_paid_inc_tax       decimal(7,2)                  ,
+    ss_net_profit             decimal(7,2)                  ,
+    primary key (ss_item_sk, ss_ticket_number)
+);
+create table store_returns
+(
+    sr_returned_date_sk       integer                       ,
+    sr_return_time_sk         integer                       ,
+    sr_item_sk                integer               not null,
+    sr_customer_sk            integer                       ,
+    sr_cdemo_sk               integer                       ,
+    sr_hdemo_sk               integer                       ,
+    sr_addr_sk                integer                       ,
+    sr_store_sk               integer                       ,
+    sr_reason_sk              integer                       ,
+    sr_ticket_number          integer               not null,
+    sr_return_quantity        integer                       ,
+    sr_return_amt             decimal(7,2)                  ,
+    sr_return_tax             decimal(7,2)                  ,
+    sr_return_amt_inc_tax     decimal(7,2)                  ,
+    sr_fee                    decimal(7,2)                  ,
+    sr_return_ship_cost       decimal(7,2)                  ,
+    sr_refunded_cash          decimal(7,2)                  ,
+    sr_reversed_charge        decimal(7,2)                  ,
+    sr_store_credit           decimal(7,2)                  ,
+    sr_net_loss               decimal(7,2)                  ,
+    primary key (sr_item_sk, sr_ticket_number)
+);
+create table customer
+(
+    c_customer_sk             integer               not null,
+    c_customer_id             char(16)              not null,
+    c_current_cdemo_sk        integer                       ,
+    c_current_hdemo_sk        integer                       ,
+    c_current_addr_sk         integer                       ,
+    c_first_shipto_date_sk    integer                       ,
+    c_first_sales_date_sk     integer                       ,
+    c_salutation              char(10)                      ,
+    c_first_name              char(20)                      ,
+    c_last_name               char(30)                      ,
+    c_preferred_cust_flag     char(1)                       ,
+    c_birth_day               integer                       ,
+    c_birth_month             integer                       ,
+    c_birth_year              integer                       ,
+    c_birth_country           varchar(20)                   ,
+    c_login                   char(13)                      ,
+    c_email_address           char(50)                      ,
+    c_last_review_date        char(10)                      ,
+    primary key (c_customer_sk)
+);
+create table promotion
+(
+    p_promo_sk                integer               not null,
+    p_promo_id                char(16)              not null,
+    p_start_date_sk           integer                       ,
+    p_end_date_sk             integer                       ,
+    p_item_sk                 integer                       ,
+    p_cost                    decimal(15,2)                 ,
+    p_response_target         integer                       ,
+    p_promo_name              char(50)                      ,
+    p_channel_dmail           char(1)                       ,
+    p_channel_email           char(1)                       ,
+    p_channel_catalog         char(1)                       ,
+    p_channel_tv              char(1)                       ,
+    p_channel_radio           char(1)                       ,
+    p_channel_press           char(1)                       ,
+    p_channel_event           char(1)                       ,
+    p_channel_demo            char(1)                       ,
+    p_channel_details         varchar(100)                  ,
+    p_purpose                 char(15)                      ,
+    p_discount_active         char(1)                       ,
+    primary key (p_promo_sk)
+);
+create table customer_address
+(
+    ca_address_sk             integer               not null,
+    ca_address_id             char(16)              not null,
+    ca_street_number          char(10)                      ,
+    ca_street_name            varchar(60)                   ,
+    ca_street_type            char(15)                      ,
+    ca_suite_number           char(10)                      ,
+    ca_city                   varchar(60)                   ,
+    ca_county                 varchar(30)                   ,
+    ca_state                  char(2)                       ,
+    ca_zip                    char(10)                      ,
+    ca_country                varchar(20)                   ,
+    ca_gmt_offset             decimal(5,2)                  ,
+    ca_location_type          char(20)                      ,
+    primary key (ca_address_sk)
+);
+create table item
+(
+    i_item_sk                 integer               not null,
+    i_item_id                 char(16)              not null,
+    i_rec_start_date          date                          ,
+    i_rec_end_date            date                          ,
+    i_item_desc               varchar(200)                  ,
+    i_current_price           decimal(7,2)                  ,
+    i_wholesale_cost          decimal(7,2)                  ,
+    i_brand_id                integer                       ,
+    i_brand                   char(50)                      ,
+    i_class_id                integer                       ,
+    i_class                   char(50)                      ,
+    i_category_id             integer                       ,
+    i_category                char(50)                      ,
+    i_manufact_id             integer                       ,
+    i_manufact                char(50)                      ,
+    i_size                    char(20)                      ,
+    i_formulation             char(20)                      ,
+    i_color                   char(20)                      ,
+    i_units                   char(10)                      ,
+    i_container               char(10)                      ,
+    i_manager_id              integer                       ,
+    i_product_name            char(50)                      ,
+    primary key (i_item_sk)
+);
+explain
+select i_product_name product_name
+,i_item_sk item_sk
+,s_store_name store_name
+,s_zip store_zip
+,ad2.ca_street_number c_street_number
+,ad2.ca_street_name c_street_name
+,ad2.ca_city c_city
+,ad2.ca_zip c_zip
+,count(*) cnt
+,sum(ss_wholesale_cost) s1
+,sum(ss_list_price) s2
+,sum(ss_coupon_amt) s3
+FROM   store_sales
+,store_returns
+,store
+,customer
+,promotion
+,customer_address ad2
+,item
+WHERE  ss_store_sk = s_store_sk AND
+ss_customer_sk = c_customer_sk AND
+ss_item_sk = i_item_sk and
+ss_item_sk = sr_item_sk and
+ss_ticket_number = sr_ticket_number and
+c_current_addr_sk = ad2.ca_address_sk and
+ss_promo_sk = p_promo_sk and
+i_color in ('maroon','burnished','dim','steel','navajo','chocolate') and
+i_current_price between 35 and 35 + 10 and
+i_current_price between 35 + 1 and 35 + 15
+group by i_product_name
+,i_item_sk
+,s_store_name
+,s_zip
+,ad2.ca_street_number
+,ad2.ca_street_name
+,ad2.ca_city
+,ad2.ca_zip
+;
+```
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/hint-based-tuning-1.png)
+
+<br/>
+
+## Join顺序的Hint
+
+<br/>
+
+### 功能描述
+
+指明join的顺序，包括内外表顺序。
+
+<br/>
+
+### 语法格式
+
+- 仅指定join顺序，不指定内外表顺序。
+
+    ```sql
+    leading(join_table_list)
+    ```
+
+- 同时指定join顺序和内外表顺序，内外表顺序仅在最外层生效。
+
+    ```sql
+    leading((join_table_list))
+    ```
+
+<br/>
+
+### 参数说明
+
+<a id="join"> </a> join_table_list为表示表join顺序的hint字符串，可以包含当前层的任意个表（别名），或对于子查询提升的场景，也可以包含子查询的hint别名，同时任意表可以使用括号指定优先级，表之间使用空格分隔。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> 表只能用单个字符串表示，不能带schema。
+> 表如果存在别名，需要优先使用别名来表示该表。
+
+join table list中指定的表需要满足以下要求，否则会报语义错误。
+
+- list中的表必须在当前层或提升的子查询中存在。
+- list中的表在当前层或提升的子查询中必须是唯一的。如果不唯一，需要使用不同的别名进行区分。
+- 同一个表只能在list里出现一次。
+- 如果表存在别名，则list中的表需要使用别名。
+
+例如:
+
+leading(t1 t2 t3 t4 t5)表示: t1，t2，t3，t4，t5先join，五表join顺序及内外表不限。
+
+leading((t1 t2 t3 t4 t5))表示: t1和t2先join，t2做内表；再和t3 join，t3做内表；再和t4 join，t4做内表；再和t5 join，t5做内表。
+
+leading(t1 (t2 t3 t4) t5)表示: t2，t3，t4先join，内外表不限；再和t1，t5 join，内外表不限。
+
+leading((t1 (t2 t3 t4) t5))表示: t2，t3，t4先join，内外表不限；在最外层，t1再和t2，t3，t4的join表join，t1为外表，再和t5 join，t5为内表。
+
+leading((t1 (t2 t3) t4 t5)) leading((t3 t2))表示: t2，t3先join，t2做内表；然后再和t1 join，t2，t3的join表做内表；然后再依次跟t4，t5做join，t4，t5做内表。
+
+<br/>
+
+### 示例
+
+对[示例](#示例)中原语句使用如下hint:
+
+```sql
+explain
+select /*+ leading((((((store_sales store) promotion) item) customer) ad2) store_returns) leading((store store_sales))*/ i_product_name product_name ...
+```
+
+该hint表示: 表之间的join关系是: store_sales和store先join，store_sales做内表，然后依次跟promotion, item, customer, ad2, store_returns做join。生成计划如下所示:
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/hint-based-tuning-2.png)
+
+<br/>
+
+## Join方式的Hint
+
+<br/>
+
+### 功能描述
+
+指明Join使用的方法，可以为Nested Loop，Hash Join和Merge Join。
+
+<br/>
+
+### 语法格式
+
+```
+[no] nestloop|hashjoin|mergejoin(table_list)
+```
+
+<br/>
+
+### 参数说明
+
+- **no**表示hint的join方式不使用。
+- <a id="table"> </a>table_list为表示hint表集合的字符串，该字符串中的表与join_table_list相同，只是中间不允许出现括号指定join的优先级。
+
+例如:
+
+no nestloop(t1 t2 t3)表示: 生成t1，t2，t3三表连接计划时，不使用nestloop。三表连接计划可能是t2 t3先join，再跟t1 join，或t1 t2先join，再跟t3 join。此hint只hint最后一次join的join方式，对于两表连接的方法不hint。如果需要，可以单独指定，例如: 任意表均不允许nestloop连接，且希望t2 t3先join，则增加hint: no nestloop(t2 t3)。
+
+<br/>
+
+### 示例
+
+对[示例](#示例)中原语句使用如下hint:
+
+```
+explain
+select /*+ nestloop(store_sales store_returns item) */ i_product_name product_name ...
+```
+
+该hint表示: 生成store_sales，store_returns和item三表的结果集时，最后的两表关联使用nestloop。生成计划如下所示:
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/hint-based-tuning-3.png)
+
+<br/>
+
+## 行数的Hint
+
+<br/>
+
+### 功能描述
+
+指明中间结果集的大小，支持绝对值和相对值的hint。
+
+<br/>
+
+### 语法格式
+
+```sql
+rows(table_list #|+|-|* const)
+```
+
+<br/>
+
+### 参数说明
+
+- **#**，**+**，**-**，*****，进行行数估算hint的四种操作符号。#表示直接使用后面的行数进行hint。+，-，*表示对原来估算的行数进行加、减、乘操作，运算后的行数最小值为1行。table_list为hint对应的单表或多表join结果集，与Join方式的Hint中table_list相同。
+- **const**可以是任意非负数，支持科学计数法。
+
+例如:
+
+rows(t1 #5)表示: 指定t1表的结果集为5行。
+
+rows(t1 t2 t3 *1000)表示: 指定t1, t2, t3 join完的结果集的行数乘以1000。
+
+<br/>
+
+### 建议
+
+- 推荐使用两个表的hint。对于两个表的采用\*操作符的hint，只要两个表出现在join的两端，都会触发hint。例如: 设置hint为rows(t1 t2 * 3)，对于(t1 t3 t4)和(t2 t5 t6)join时，由于t1和t2出现在join的两端，所以其join的结果集也会应用该hint规则乘以3。
+- rows hint支持在单表、多表、function table及subquery scan table的结果集上指定hint。
+
+<br/>
+
+### 示例
+
+对[示例](#示例)中原语句使用如下hint：
+
+```sql
+explain
+select /*+ rows(store_sales store_returns *50) */ i_product_name product_name ...
+```
+
+该hint表示: store_sales，store_returns关联的结果集估算行数在原估算行数基础上乘以50。生成计划如下所示:
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/hint-based-tuning-4.png)
+
+<br/>
+
+## Scan方式的Hint
+
+<br/>
+
+### 功能描述
+
+指明scan使用的方法，可以是tablescan、indexscan和indexonlyscan。
+
+<br/>
+
+### 语法格式
+
+```sql
+[no] tablescan|indexscan|indexonlyscan(table [index])
+```
+
+<br/>
+
+### 参数说明
+
+- **no**表示hint的scan方式不使用。
+- **table**表示hint指定的表，只能指定一个表，如果表存在别名应优先使用别名进行hint。
+- **index**表示使用indexscan或indexonlyscan的hint时，指定的索引名称，当前只能指定一个。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+> 对于indexscan或indexonlyscan，只有hint的索引属于hint的表时，才能使用该hint。
+> scan hint支持在行列存表、obs表、子查询表上指定。
+
+<br/>
+
+### 示例
+
+为了hint使用索引扫描，需要首先在表item的i_item_sk列上创建索引，名称为i。
+
+```sql
+create index i on item(i_item_sk);
+```
+
+对[示例](#示例)中原语句使用如下hint：
+
+```sql
+explain
+select /*+ indexscan(item i) */ i_product_name product_name ...
+```
+
+该hint表示: item表使用索引i进行扫描。生成计划如下所示:
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/hint-based-tuning-5.png)
+
+<br/>
+
+## 子链接块名的hint
+
+<br/>
+
+### 功能描述
+
+指明子链接块的名称。
+
+<br/>
+
+### 语法格式
+
+```sql
+blockname (table)
+```
+
+<br/>
+
+### 参数说明
+
+- **table**表示为该子链接块hint的别名的名称。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+>
+> - **blockname hint**仅在对应的子链接块提升时才会被上层查询使用。目前支持的子链接提升包括IN子链接提升、EXISTS子链接提升和包含Agg等值相关子链接提升。该hint通常会和前面章节提到的hint联合使用。
+> - 对于FROM关键字后的子查询，则需要使用子查询的别名进行hint，blockname hint不会被用到。
+> - 如果子链接中含有多个表，则提升后这些表可与外层表以任意优化顺序连接，hint也不会被用到。
+
+<br/>
+
+### 示例
+
+```sql
+explain select /*+nestloop(store_sales tt) */ * from store_sales where ss_item_sk in (select /*+blockname(tt)*/ i_item_sk from item group by 1);
+```
+
+该hint表示: 子链接的别名为tt，提升后与上层的store_sales表关联时使用nestloop。生成计划如下所示:
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/hint-based-tuning-6.png)
+
+<br/>
+
+## Hint的错误、冲突及告警
+
+Plan Hint的结果会体现在计划的变化上，可以通过explain来查看变化。
+
+Hint中的错误不会影响语句的执行，只是不能生效，该错误会根据语句类型以不同方式提示用户。对于explain语句，hint的错误会以warning形式显示在界面上，对于非explain语句，会以debug1级别日志显示在日志中，关键字为PLANHINT。
+
+hint的错误分为以下类型:
+
+- 语法错误
+
+    语法规则树归约失败，会报错，指出出错的位置。
+
+    例如: hint关键字错误，leading hint或join hint指定2个表以下，其它hint未指定表等。一旦发现语法错误，则立即终止hint的解析，所以此时只有错误前面的解析完的hint有效。
+
+    例如:
+
+    ```sql
+    leading((t1 t2)) nestloop(t1) rows(t1 t2 #10)
+    ```
+
+    nestloop(t1)存在语法错误，则终止解析，可用hint只有之前解析的leading((t1 t2))。
+
+- 语义错误
+
+  - 表不存在，存在多个，或在leading或join中出现多次，均会报语义错误。
+  - scanhint中的index不存在，会报语义错误。
+  - 另外，如果子查询提升后，同一层出现多个名称相同的表，且其中某个表需要被hint，hint会存在歧义，无法使用，需要为相同表增加别名规避。
+
+- hint重复或冲突
+
+    如果存在hint重复或冲突，只有第一个hint生效，其它hint均会失效，会给出提示。
+
+  - hint重复是指，hint的方法及表名均相同。例如: nestloop(t1 t2) nestloop(t1 t2)。
+
+  - hint冲突是指，table list一样的hint，存在不一样的hint，hint的冲突仅对于每一类hint方法检测冲突。
+
+    例如: nestloop (t1 t2) hashjoin (t1 t2)，则后面与前面冲突，此时hashjoin的hint失效。注意:nestloop(t1 t2)和no mergejoin(t1 t2)不冲突。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+    > leading hint中的多个表会进行拆解。例如: leading ((t1 t2 t3))会拆解成: leading((t1 t2)) leading(((t1 t2) t3))，此时如果存在leading((t2 t1))，则两者冲突，后面的会被丢弃。（例外: 指定内外表的hint若与不指定内外表的hint重复，则始终丢弃不指定内外表的hint。）
+
+- 子链接提升后hint失效
+
+    子链接提升后的hint失效，会给出提示。通常出现在子链接中存在多个表连接的场景。提升后，子链接中的多个表不再作为一个整体出现在join中。
+
+- 列类型不支持重分布
+
+  - 对于skew hint来说，目的是为了进行重分布时的调优，所以当hint列的类型不支持重分布时，hint将无效。
+
+- hint未被使用
+
+  - 非等值join使用hashjoin hint或mergejoin hint。
+  - 不包含索引的表使用indexscan hint或indexonlyscan hint。
+  - 通常只有在索引列上使用过滤条件才会生成相应的索引路径，全表扫描将不会使用索引，因此使用indexscan hint或indexonlyscan hint将不会使用。
+  - indexonlyscan只有输出列仅包含索引列才会使用，否则指定时hint不会被使用。
+  - 多个表存在等值连接时，仅尝试有等值连接条件的表的连接，此时没有关联条件的表之间的路径将不会生成，所以指定相应的leading，join，rows hint将不使用，例如: t1 t2 t3表join，t1和t2, t2和t3有等值连接条件，则t1和t3不会优先连接，leading(t1 t3)不会被使用。
+  - 生成stream计划时，如果表的分布列与join列相同，则不会生成redistribute的计划；如果不同，且另一表分布列与join列相同，只能生成redistribute的计划，不会生成broadcast的计划，指定相应的hint则不会被使用。
+  - 如果子链接未被提升，则blockname hint不会被使用。
+  - 对于skew hint，hint未被使用可能由于:
+    - 计划中不需要进行重分布。
+    - hint指定的列为包含分布键。
+    - hint指定倾斜信息有误或不完整，如对于join优化未指定值。
+    - 倾斜优化的GUC参数处于关闭状态。
+
+## 优化器GUC参数的Hint
+
+### 功能描述
+
+设置本次查询执行内生效的查询优化相关GUC参数。hint的推荐使用场景可以参考各guc参数的说明，此处不作赘述。
+
+### 语法格式
+
+```
+set(param value)
+```
+
+### 参数说明
+
+- **param**表示参数名。
+
+- **value**表示参数的取值。
+
+- 目前支持使用Hint设置生效的参数有
+
+  - 布尔类：
+
+    enable_bitmapscan, enable_hashagg, enable_hashjoin, enable_indexscan, enable_indexonlyscan, enable_material, enable_mergejoin, enable_nestloop, enable_index_nestloop, enable_seqscan, enable_sort, enable_tidscan
+
+  - 整形类：
+
+    query_dop
+
+  - 浮点类：
+
+    cost_weight_index, default_limit_rows, seq_page_cost, random_page_cost, cpu_tuple_cost, cpu_index_tuple_cost, cpu_operator_cost, effective_cache_size
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 设置不在白名单中的参数，参数取值不合法，或hint语法错误时，不会影响查询执行的正确性。使用explain(verbose on)执行可以看到hint解析错误的报错提示。
+> - GUC参数的hint只在最外层查询生效——子查询内的GUC参数hint不生效。
+> - 视图定义内的GUC参数hint不生效。
+> - CREATE TABLE … AS … 查询最外层的GUC参数hint可以生效。
+
+## Custom Plan和Generic Plan选择的Hint
+
+### 功能描述
+
+对于以PBE方式执行的查询语句和DML语句，优化器会基于规则、代价、参数等因素选择生成Custom Plan或Generic Plan执行。用户可以通过use_cplan/use_gplan的hint指定使用哪种计划执行方式。
+
+### 语法格式
+
+- 指定使用Custom Plan：
+
+  ```
+  use_cplan
+  ```
+
+- 指定使用Generic Plan：
+
+  ```
+  use_gplan
+  ```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 对于非PBE方式执行的SQL语句，设置本hint不会影响执行方式。
+> - 本Hint的优先级仅高于基于代价的选择和plan_cache_mode参数，即plan_cache_mode无法强制选择执行方式的语句本hint也无法生效。
+
+### 示例
+
+强制使用Custom Plan
+
+```sql
+set enable_fast_query_shipping = off;
+create table t (a int, b int, c int);
+prepare p as select /*+ use_cplan */ * from t where a = $1;
+explain execute p(1);
+```
+
+计划如下。可以看到过滤条件为入参的实际值，即此计划为Custom Plan。
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/hint-based-tuning-7.png)
+
+强制使用Generic Plan
+
+```sql
+deallocate p;
+prepare p as select /*+ use_gplan */ * from t where a = $1;
+explain execute p(1);
+```
+
+计划如下。可以看到过滤条件为待填充的入参，即此计划为Custom Plan。
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/hint-based-tuning-8.png)
+
+## 指定子查询不展开的Hint
+
+### 功能描述
+
+数据库在对查询进行逻辑优化时通常会将可以提升的子查询提升到上层来避免嵌套执行，但对于某些本身选择率较低且可以使用索引过滤访问页面的子查询，嵌套执行不会导致性能下降过多，而提升之后扩大了查询路径的搜索范围，可能导致性能变差。对于此类情况，可以使用no_expand Hint进行调试。大多数情况下不建议使用此hint。
+
+### 语法格式
+
+```
+no_expand
+```
+
+### 示例
+
+正常的查询执行
+
+```sql
+explain select * from t1 where t1.a in (select t2.a from t2);
+```
+
+计划
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/hint-based-tuning-9.png)
+
+加入no_expand
+
+```sql
+explain select * from t1 where t1.a in (select /*+ no_expand*/ t2.a from t2);
+```
+
+计划
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/hint-based-tuning-10.png)
+
+## 指定不使用全局计划缓存的Hint
+
+### 功能描述
+
+全局计划缓存打开时，可以通过no_gpc Hint来强制单个查询语句不在全局共享计划缓存，只保留会话生命周期的计划缓存。
+
+### 语法格式
+
+```
+no_gpc
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 本参数仅在enable_global_plancache=on时对PBE执行的语句生效。
+
+### 示例
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/hint-based-tuning-11.png)
+
+dbe_perf.global_plancache_status视图中无结果即没有计划被全局缓存。
diff --git a/product/zh/docs-mogdb/v3.0/performance-tuning/TPCC-performance-tuning-guide.md b/product/zh/docs-mogdb/v3.0/performance-tuning/TPCC-performance-tuning-guide.md
new file mode 100644
index 0000000000000000000000000000000000000000..af454271fca9be634df612620ee0b6724b0435c4
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/performance-tuning/TPCC-performance-tuning-guide.md
@@ -0,0 +1,780 @@
+---
+title: TPCC测试优化指南
+summary: TPCC测试优化指南
+author: Guo Huan
+date: 2021-08-03
+---
+
+# TPCC测试优化指南
+
+本章节主要介绍MogDB数据库TPCC测试方法，以及为达到最佳tpmC性能所依赖的关键系统级调优。
+
+<br/>
+
+## 硬件环境
+
+* 服务器
+  * 最佳TPCC结果是使用4路鲲鹏服务器（256C, 512G-1024G内存） + 一个2路鲲鹏服务器
+  * 常规可使用2个2路鲲鹏服务器，128C, 512G-1024G内存
+  * 2台X86也可以，但测试指南未使用NUMA优化
+
+* 硬盘
+  * 数据库端尽可能使用两块NVME闪存卡
+  * 其次使用3-4块SSD硬盘
+
+* 网卡
+  * 鲲鹏配套的Hi1822
+  * X86尽可能使用万兆网卡
+
+<br/>
+
+## 软件环境
+
+* 数据库：MogDB 2.1.1
+
+* TPCC客户端：使用tidb优化过的BenchmarkSQL 5.0（[https://github.com/pingcap/benchmarksql](https://github.com/pingcap/benchmarksql)）
+
+* 依赖包
+
+  | 所需软件 | 建议版本  |
+  | :------- | :-------- |
+  | numactl  | –         |
+  | jdk      | 1.8.0-242 |
+  | ant      | 1.10.5    |
+  | htop     | –         |
+
+<br/>
+
+## 测试步骤
+
+1. 安装MogDB。参考[安装MogDB](4-installing-mogdb)，单机部署即可。
+
+2. 初始化参数设置，并重启数据库，使参数生效。参考[推荐参数设置及新建测试库](7-recommended-parameter-settings)。
+
+3. 下载TPCC标准测试工具BenchmarkSQL5.0。
+
+   ```bash
+   [root@node151 ~]# git clone -b 5.0-mysql-support-opt-2.1 https://github.com/pingcap/benchmarksql.git
+   Cloning into 'tpcc-mysql'...
+   remote: Enumerating objects: 106, done.
+   remote: Total 106 (delta 0), reused 0 (delta 0), pack-reused 106
+   Receiving objects: 100% (106/106), 64.46 KiB | 225.00 KiB/s, done.
+   Resolving deltas: 100% (30/30), done.
+   ```
+
+4. 下载安装JDK和ant依赖包。
+
+   ```bash
+   [root@node151 ~]# rpm -ivh ant-1.10.5-6.oe1.noarch.rpm jdk-8u281-linux-aarch64.rpm --force --nodeps
+   warning: ant-1.10.5-6.oe1.noarch.rpm: Header V3 RSA/SHA1 Signature, key ID b25e7f66: NOKEY
+   warning: jdk-8u281-linux-aarch64.rpm: Header V3 RSA/SHA256 Signature, key ID ec551f03: NOKEY
+   Verifying...                          ################################# [100%]
+   Preparing...                          ################################# [100%]
+   Updating / installing...
+      1:jdk1.8-2000:1.8.0_281-fcs        ################################# [ 50%]
+   Unpacking JAR files...
+           tools.jar...
+           rt.jar...
+           jsse.jar...
+           charsets.jar...
+           localedata.jar...
+      2:ant-0:1.10.5-6.oe1               ################################# [100%]
+   ```
+
+5. 配置JAVA环境变量
+
+   ```bash
+   [root@node151 ~]# tail -3  /root/.bashrc
+   export JAVA_HOME=/usr/java/jdk1.8.0_281-aarch64
+   export PATH=$JAVA_HOME/bin:$PATH
+   export CLASSPATH=.:JAVA_HOME/lib:$BENCHMARKSQLPATH/run/ojdbc7.jar
+   ```
+
+6. 在BenchmarkSQL所在目录下输入ant命令进行编译，编译成功后会生成build和dist两个目录。
+
+   ```bash
+   [root@node151 benchmarksql-5.0-mysql-support-opt-2.1]# pwd
+   /tmp/benchmarksql-5.0-mysql-support-opt-2.1
+   [root@node151 benchmarksql-5.0-mysql-support-opt-2.1]# ant
+   Buildfile: /tmp/benchmarksql-5.0-mysql-support-opt-2.1/build.xml
+
+   init:
+       [mkdir] Created dir: /tmp/benchmarksql-5.0-mysql-support-opt-2.1/build
+
+   compile:
+       [javac] Compiling 12 source files to /tmp/benchmarksql-5.0-mysql-support-opt-2.1/build
+
+   dist:
+       [mkdir] Created dir: /tmp/benchmarksql-5.0-mysql-support-opt-2.1/dist
+         [jar] Building jar: /tmp/benchmarksql-5.0-mysql-support-opt-2.1/dist/BenchmarkSQL-5.0.jar
+
+   BUILD SUCCESSFUL
+   Total time: 1 second
+   ```
+
+7. 根据您的系统架构下载对应的JDBC驱动（[https://opengauss.org/zh/download.html](https://opengauss.org/zh/download.html)）至BenchmarkSQL目录的lib/postgresql文件夹，并解压，删除自带的JDBC驱动。
+
+   ```bash
+   [root@node151 postgres]# pwd
+   /tmp/benchmarksql-5.0-mysql-support-opt-2.1/lib/postgres/
+   [root@node151 postgres]# ls
+   openGauss-2.0.0-JDBC.tar.gz  postgresql-9.3-1102.jdbc41.jar
+   [root@node151 postgres]# rm -f postgresql-9.3-1102.jdbc41.jar
+   [root@node151 postgres]# tar -xf openGauss-2.0.0-JDBC.tar.gz
+   [root@node151 postgres]# ls
+   openGauss-2.0.0-JDBC.tar.gz  postgresql.jar
+   ```
+
+8. 数据库端准备，创建数据库tpcc_db及用户tpcc。
+
+   ```sql
+   [omm@node151 ~]$ gsql -d postgres -p 26000 -r
+   postgres=# create database tpcc_db;
+   CREATE DATABASE
+   postgres=# \q
+   [omm@node151 ~]$ gsql -d tpcc_db -p 26000 -r
+   tpcc_db=# CREATE USER tpcc WITH PASSWORD "tpcc@123";
+   CREATE ROLE
+   tpcc_db=# GRANT ALL ON schema public TO tpcc;
+   GRANT
+   tpcc_db=# ALTER User tpcc sysadmin;
+   ALTER ROLE
+   ```
+
+9. 客户端准备，进入BenchmarkSQL目录下的run文件夹，编辑benchmarksql配置文件，修改测试参数，包括数据库用户名、密码、IP、端口、数据库。
+
+    ```bash
+    [root@node151 db1]# cd /tmp/benchmarksql-5.0-mysql-support-opt-2.1/run
+    [root@node151 run]# vim props.mogdb
+    db=postgres
+    driver=org.postgresql.Driver
+    conn=jdbc:postgresql://172.16.0.176:26000/tpcc_db?prepareThreshold=1&batchMode=on&fetchsize=10&loggerLevel=off #修改连接字符串, 包含IP、端口号、数据库
+    user=tpcc #用户名
+    password=tpcc@123 #密码
+    warehouses=100  #仓位数
+    terminals=300 #并发数
+    runMins=5  #运行时间
+    runTxnsPerTerminal=0
+    loadWorkers=100
+    limitTxnsPerMin=0
+    terminalWarehouseFixed=false
+    newOrderWeight=45
+    paymentWeight=43
+    orderStatusWeight=4
+    deliveryWeight=4
+    stockLevelWeight=4
+    ```
+
+10. 初始化数据
+
+    ```
+    [root@node151 run]# sh runDatabaseBuild.sh props.mogdb
+
+    # ------------------------------------------------------------
+    # Loading SQL file ./sql.common/tableCreates.sql
+    # ------------------------------------------------------------
+    create table bmsql_config (
+    cfg_name    varchar(30) primary key,
+    cfg_value   varchar(50)
+    );
+    ```
+    
+    ```
+    ......
+    
+    # ------------------------------------------------------------
+    # Loading SQL file ./sql.postgres/buildFinish.sql
+    # ------------------------------------------------------------
+    -- ----
+    -- Extra commands to run after the tables are created, loaded,
+    -- indexes built and extra's created.
+    -- PostgreSQL version.
+    -- ----
+    vacuum analyze;
+    ```
+
+11. 修改runBenchmark.sh文件中funcs.sh所在的实际路径。
+
+    ```
+    [root@node151 run]# vim runBenchmark.sh
+    #!/usr/bin/env bash
+
+    if [ $# -ne 1 ] ; then
+        echo "usage: $(basename $0) PROPS_FILE" >&2
+        exit 2
+    fi
+
+    SEQ_FILE="./.jTPCC_run_seq.dat"
+    if [ ! -f "${SEQ_FILE}" ] ; then
+        echo "0" > "${SEQ_FILE}"
+    fi
+    SEQ=$(expr $(cat "${SEQ_FILE}") + 1) || exit 1
+    echo "${SEQ}" > "${SEQ_FILE}"
+
+    source /tmp/benchmarksql-5.0-mysql-support-opt-2.1/run/funcs.sh $1  #将此处路径修改为文件所在的实际路径
+
+    setCP || exit 1
+
+    myOPTS="-Dprop=$1 -DrunID=${SEQ}"
+
+    java -cp "$myCP" $myOPTS jTPCC
+    ```
+
+12. 开始测试，运行tpcc跑分，tpmC部分即为测试结果，结果同时保存在 runLog_mmdd-hh24miss.log 下。
+
+    ```
+    [root@node151 run]# sh runBenchmark.sh props.mogdb| tee runLog_`date +%m%d-%H%M%S`.log
+
+    ...
+
+    15:08:26,663 [Thread-16] INFO   jTPCC : Term-00, Measured tpmC (NewOrders) = 106140.46
+    15:08:26,663 [Thread-16] INFO   jTPCC : Term-00, Measured tpmTOTAL = 235800.39
+    15:08:26,664 [Thread-16] INFO   jTPCC : Term-00, Session Start     = 2021-08-04 15:03:26
+    15:08:26,664 [Thread-16] INFO   jTPCC : Term-00, Session End       = 2021-08-04 15:08:26
+    15:08:26,664 [Thread-16] INFO   jTPCC : Term-00, Transaction Count = 1179449
+    15:08:26,664 [Thread-16] INFO   jTPCC : executeTime[Payment]=29893614
+    15:08:26,664 [Thread-16] INFO   jTPCC : executeTime[Order-Status]=2564424
+    15:08:26,664 [Thread-16] INFO   jTPCC : executeTime[Delivery]=4438389
+    15:08:26,664 [Thread-16] INFO   jTPCC : executeTime[Stock-Level]=4259325
+    15:08:26,664 [Thread-16] INFO   jTPCC : executeTime[New-Order]=48509926
+    ```
+
+    调整props.mogdb，或者使用多个props文件，根据需要进行多次测试。
+
+13. 为了避免多次测试导致数据量太大，影响性能，可以把数据清空重新开始。
+
+    ```
+    [root@node151 run]# sh runDatabaseDestroy.sh props.mogdb
+    # ------------------------------------------------------------
+    # Loading SQL file ./sql.common/tableDrops.sql
+    # ------------------------------------------------------------
+    drop table bmsql_config;
+    drop table bmsql_new_order;
+    drop table bmsql_order_line;
+    drop table bmsql_oorder;
+    drop table bmsql_history;
+    drop table bmsql_customer;
+    drop table bmsql_stock;
+    drop table bmsql_item;
+    drop table bmsql_district;
+    drop table bmsql_warehouse;
+    drop sequence bmsql_hist_id_seq;
+    ```
+
+    在调试时，可以一次Build, 多次Run，但是如果是正式测试，建议每次都是 Build / Run / Destroy。
+
+<br/>
+
+## 调优
+
+### 1. 主机优化（鲲鹏专享）
+
+调整BIOS
+
+- BIOS>Advanced>MISC Config，配置Support Smmu为Disabled
+- BIOS>Advanced>MISC Config，配置CPU Prefetching Configuration为Disabled
+- BIOS>Advanced>Memory Config，配置Die Interleaving为Disable
+
+### 2. 操作系统优化（鲲鹏专享）
+
+- 修改操作系统内核PAGESIZE为64KB（一般默认值）
+
+- 关闭irqbalance
+
+  ```bash
+  systemctl stop irqbalance
+  ```
+
+- 调整numa_balance
+
+  ```bash
+  echo 0 > /proc/sys/kernel/numa_balancing
+  ```
+
+- 调整透明大页
+
+  ```bash
+  echo 'never' > /sys/kernel/mm/transparent_hugepage/enabled
+  echo 'never' > /sys/kernel/mm/transparent_hugepage/defrag
+  ```
+
+- 针对nvme磁盘io队列调度机制设置。
+
+  ```bash
+  echo none > /sys/block/nvme*n*/queue/scheduler
+  ```
+
+### 3. 文件系统配置
+
+- 格式为xfs，数据库大小为8K
+
+  ```bash
+  mkfs.xfs -b size=8192 /dev/nvme0n1 -f
+  ```
+
+### 4. 网络配置
+
+- 网卡多中断队列设置
+
+  下载 [IN500_solution_5.1.0.SPC401.zip](https://support.huawei.com/enterprise/zh/software/250968786-ESW2000173161) 安装hinicadm
+
+  ```
+  [root@node151 fc]# pwd
+  /root/IN500_solution_5/tools/linux_arm/fc
+  [root@node151 fc]# rpm -ivh hifcadm-2.4.1.0-1.aarch64.rpm
+  Verifying...                          ################################# [100%]
+  Preparing...                          ################################# [100%]
+          package hifcadm-2.4.1.0-1.aarch64 is already installed
+  [root@node151 fc]#
+  ```
+
+- 修改系统支持的最大中断队列数
+
+  ```
+  [root@node151 config]# pwd
+  /root/IN500_solution_5/tools/linux_arm/nic/config
+  [root@node151 config]# ./hinicconfig hinic0 -f std_sh_4x25ge_dpdk_cfg_template0.ini
+  [root@node151 config]# reboot
+  [root@node151 config]# ethtool -L enp3s0 combined 48
+  ```
+
+  不同平台，不同应用的优化值可能不同，当前128核的平台，服务器端调优值为12，客户端调优值为48。
+
+- 中断调优开启tso，lro，gro，gso特性。
+
+  ```bash
+  ethtool -K enp3s0 tso on
+  ethtool -K enp3s0 lro on
+  ethtool -K enp3s0 gro on
+  ethtool -K enp3s0 gso on
+  ```
+
+- 网卡固件确认与更新
+
+  ```
+  [root@node151 ~]# ethtool -i enp3s0
+  driver: hinic
+  version: 2.3.2.11
+  firmware-version: 2.4.1.0
+  expansion-rom-version:
+  bus-info: 0000:03:00.0
+  supports-statistics: yes
+  supports-test: yes
+  supports-eeprom-access: no
+  supports-register-dump: no
+  supports-priv-flags: no
+  ```
+
+  网卡固件版本应为2.4.1.0
+
+- 更新网卡固件。
+
+  ```
+  [root@node151 cfg_data_nic_prd_1h_4x25G]# pwd
+  /root/IN500_solution_5/firmware/update_bin/cfg_data_nic_prd_1h_4x25G
+  [root@node151 cfg_data_nic_prd_1h_4x25G]# hinicadm updatefw -i enp3s0 -f /root/IN500_solution_5/firmware/update_bin/cfg_data_nic_prd_1h_4x25G/Hi1822_nic_prd_1h_4x25G.bin
+  ```
+
+  重启服务器，再确认网卡固件版本成功更新为2.4.1.0。
+
+### 5. 数据库服务端及客户端绑核
+
+* 鲲鹏上numa绑定优化（128核）
+
+  * 数据库主机和客户端主机安装numa
+
+    ```bash
+    yum install numa* -y
+    ```
+
+    网卡驱动安装（包括数据库主机和客户端主机），参考上文**网络配置**部分。
+
+  * 数据库主机
+
+    ```bash
+    cp `find /opt -name "bind*.sh"|head -1 ` /root
+    sh /root/bind_net_irq.sh 12
+    ```
+
+    设置数据库参数：
+
+    ```bash
+    thread_pool_attr = '345,4,(cpubind:1-28,32-60,64-92,96-124)'
+    enable_thread_pool = on
+    ```
+
+    关闭数据库
+    启动数据库命令替换成：
+
+    ```bash
+    numactl -C 1-28,32-60,64-92,96-124 mogdb --single_node -D /opt/data/db2/ -p 26000 &
+    ```
+
+  * 客户端
+    拷贝/root/bind_net_irq.sh 到客户端
+
+    ```bash
+    sh /root/bind_net_irq.sh 48
+    ```
+
+    benchmark启动命令改成
+
+    ```bash
+    numactl -C 0-19,32-51,64-83,96-115 sh runBenchmark.sh props.mog
+    ```
+
+* 鲲鹏上numa绑定优化（256核）
+
+  * 数据库主机和客户端主机安装numa
+
+    ```bash
+    yum install numa* -y
+    ```
+
+    网卡驱动安装（包括数据库主机和客户端主机），参考上文**网络配置**部分。
+
+  * 数据库主机
+
+    ```bash
+    cp `find /opt -name "bind*.sh"|head -1 ` /root
+    sh /root/bind_net_irq.sh 24
+    ```
+
+    设置数据库参数：
+
+    ```bash
+    thread_pool_attr = '696,4,(cpubind:1-28,32-60,64-92,96-124,128-156,160-188,192-220,224-252)'
+    enable_thread_pool = on
+    ```
+
+    关闭数据库
+    启动数据库命令替换成：
+
+    ```bash
+    numactl -C 1-28,32-60,64-92,96-124,128-156,160-188,192-220,224-252 mogdb --single_node -D /opt/data/db2/ -p 26000 &
+    ```
+
+  * 客户端
+    拷贝/root/bind_net_irq.sh 到客户端
+
+    ```bash
+    sh /root/bind_net_irq.sh 48
+    ```
+
+    benchmark启动命令改成
+
+    ```bash
+    numactl -C 0-19,32-51,64-83,96-115 sh runBenchmark.sh props.mog
+    ```
+
+### 6. 数据库参数优化（通用）
+
+修改PGDATA下的postgresql.conf，并重启
+
+```bash
+max_connections = 4096
+allow_concurrent_tuple_update = true
+audit_enabled = off
+cstore_buffers =16MB
+enable_alarm = off
+enable_codegen = false
+enable_data_replicate = off
+full_page_writes = off
+max_files_per_process = 100000
+max_prepared_transactions = 2048
+shared_buffers = 350GB
+use_workload_manager = off
+wal_buffers = 1GB
+work_mem = 1MB
+transaction_isolation = 'read committed'
+default_transaction_isolation = 'read committed'
+synchronous_commit = on
+fsync = on
+maintenance_work_mem = 2GB
+vacuum_cost_limit = 2000
+autovacuum = on
+autovacuum_mode = vacuum
+autovacuum_vacuum_cost_delay =10
+xloginsert_locks = 48
+update_lockwait_timeout =20min
+enable_mergejoin = off
+enable_nestloop = off
+enable_hashjoin = off
+enable_bitmapscan = on
+enable_material = off
+wal_log_hints = off
+log_duration = off
+checkpoint_timeout = 15min
+autovacuum_vacuum_scale_factor = 0.1
+autovacuum_analyze_scale_factor = 0.02
+enable_save_datachanged_timestamp =FALSE
+log_timezone = 'PRC'
+timezone = 'PRC'
+lc_messages = 'C'
+lc_monetary = 'C'
+lc_numeric = 'C'
+lc_time = 'C'
+enable_double_write = on
+enable_incremental_checkpoint = on
+enable_opfusion = on
+numa_distribute_mode = 'all'
+track_activities = off
+enable_instr_track_wait = off
+enable_instr_rt_percentile = off
+track_counts =on
+track_sql_count = off
+enable_instr_cpu_timer = off
+plog_merge_age = 0
+session_timeout = 0
+enable_instance_metric_persistent = off
+enable_logical_io_statistics = off
+enable_user_metric_persistent =off
+enable_xlog_prune = off
+enable_resource_track = off
+instr_unique_sql_count = 0
+enable_beta_opfusion = on
+enable_thread_pool = on
+#0核用于walwriter线程绑核
+enable_partition_opfusion=off
+wal_writer_cpu=0
+xlog_idle_flushes_before_sleep = 500000000
+max_io_capacity = 2GB
+dirty_page_percent_max = 0.1
+candidate_buf_percent_target = 0.7
+bgwriter_delay = 500
+pagewriter_sleep = 30
+checkpoint_segments =10240
+advance_xlog_file_num = 100
+autovacuum_max_workers = 20
+autovacuum_naptime = 5s
+bgwriter_flush_after = 256kB
+data_replicate_buffer_size = 16MB
+enable_stmt_track = off
+remote_read_mode=non_authentication
+wal_level = archive
+hot_standby = off
+hot_standby_feedback = off
+client_min_messages = ERROR
+log_min_messages = FATAL
+enable_asp = off
+enable_bbox_dump = off
+enable_ffic_log = off
+enable_twophase_commit = off
+minimum_pool_size = 200
+wal_keep_segments = 1025
+incremental_checkpoint_timeout = 5min
+max_process_memory = 12GB
+vacuum_cost_limit = 10000
+xloginsert_locks = 8
+wal_writer_delay = 100
+wal_file_init_num = 30
+wal_level=minimal
+max_wal_senders=0
+fsync=off
+synchronous_commit = off
+enable_indexonlyscan=on
+thread_pool_attr = '345,4,(cpubind:1-28,32-60,64-92,96-124)'
+enable_page_lsn_check = off
+enable_double_write = off
+```
+
+### 7. benchmarksql调优
+
+- 连接串
+
+  ```bash
+  conn=jdbc:postgresql://10.10.10.40:26000/tpcc?prepareThreshold=1&batchMode=on&fetchsize=10&loggerLevel=off
+  ```
+
+- 修改文件内容将数据分散，调整FILLFACTOR，数据分区。
+
+  ```sql
+  [root@node151 ~]# ls benchmarksql-5.0-mysql-support-opt-2.1/run/sql.common/tableCreates.sql
+  benchmarksql-5.0-mysql-support-opt-2.1/run/sql.common/tableCreates.sql
+  [root@node151 sql.common]# cat tableCreates.sql
+  CREATE TABLESPACE example2 relative location 'tablespace2';
+  CREATE TABLESPACE example3 relative location 'tablespace3';
+
+  create table bmsql_config (
+    cfg_name    varchar(30),
+    cfg_value   varchar(50)
+  );
+
+  create table bmsql_warehouse (
+    w_id        integer   not null,
+    w_ytd       decimal(12,2),
+    w_tax       decimal(4,4),
+    w_name      varchar(10),
+    w_street_1  varchar(20),
+    w_street_2  varchar(20),
+    w_city      varchar(20),
+    w_state     char(2),
+    w_zip       char(9)
+  ) WITH (FILLFACTOR=80);
+
+  create table bmsql_district (
+    d_w_id       integer       not null,
+    d_id         integer       not null,
+    d_ytd        decimal(12,2),
+    d_tax        decimal(4,4),
+    d_next_o_id  integer,
+    d_name       varchar(10),
+    d_street_1   varchar(20),
+    d_street_2   varchar(20),
+    d_city       varchar(20),
+    d_state      char(2),
+    d_zip        char(9)
+   ) WITH (FILLFACTOR=80);
+
+  create table bmsql_customer (
+    c_w_id         integer        not null,
+    c_d_id         integer        not null,
+    c_id           integer        not null,
+    c_discount     decimal(4,4),
+    c_credit       char(2),
+    c_last         varchar(16),
+    c_first        varchar(16),
+    c_credit_lim   decimal(12,2),
+    c_balance      decimal(12,2),
+    c_ytd_payment  decimal(12,2),
+    c_payment_cnt  integer,
+    c_delivery_cnt integer,
+    c_street_1     varchar(20),
+    c_street_2     varchar(20),
+    c_city         varchar(20),
+    c_state        char(2),
+    c_zip          char(9),
+    c_phone        char(16),
+    c_since        timestamp,
+    c_middle       char(2),
+    c_data         varchar(500)
+  ) WITH (FILLFACTOR=80) tablespace example2;
+
+  create sequence bmsql_hist_id_seq;
+
+  create table bmsql_history (
+    hist_id  integer,
+    h_c_id   integer,
+    h_c_d_id integer,
+    h_c_w_id integer,
+    h_d_id   integer,
+    h_w_id   integer,
+    h_date   timestamp,
+    h_amount decimal(6,2),
+    h_data   varchar(24)
+  ) WITH (FILLFACTOR=80);
+
+  create table bmsql_new_order (
+    no_w_id  integer   not null,
+    no_d_id  integer   not null,
+    no_o_id  integer   not null
+  ) WITH (FILLFACTOR=80);
+
+  create table bmsql_oorder (
+    o_w_id       integer      not null,
+    o_d_id       integer      not null,
+    o_id         integer      not null,
+    o_c_id       integer,
+    o_carrier_id integer,
+    o_ol_cnt     integer,
+    o_all_local  integer,
+    o_entry_d    timestamp
+  ) WITH (FILLFACTOR=80);
+
+  create table bmsql_order_line (
+    ol_w_id         integer   not null,
+    ol_d_id         integer   not null,
+    ol_o_id         integer   not null,
+    ol_number       integer   not null,
+    ol_i_id         integer   not null,
+    ol_delivery_d   timestamp,
+    ol_amount       decimal(6,2),
+    ol_supply_w_id  integer,
+    ol_quantity     integer,
+    ol_dist_info    char(24)
+  ) WITH (FILLFACTOR=80);
+
+  create table bmsql_item (
+    i_id     integer      not null,
+    i_name   varchar(24),
+    i_price  decimal(5,2),
+    i_data   varchar(50),
+    i_im_id  integer
+  );
+
+  create table bmsql_stock (
+    s_w_id       integer       not null,
+    s_i_id       integer       not null,
+    s_quantity   integer,
+    s_ytd        integer,
+    s_order_cnt  integer,
+    s_remote_cnt integer,
+    s_data       varchar(50),
+    s_dist_01    char(24),
+    s_dist_02    char(24),
+    s_dist_03    char(24),
+    s_dist_04    char(24),
+    s_dist_05    char(24),
+    s_dist_06    char(24),
+    s_dist_07    char(24),
+    s_dist_08    char(24),
+    s_dist_09    char(24),
+    s_dist_10    char(24)
+  ) WITH (FILLFACTOR=80) tablespace example3;
+  ```
+
+### 8.数据库文件位置优化（通用）
+
+通过将默认主目录、xlog、example2、example3分开多个底层磁盘来避免I/O瓶颈。
+如果只有2个性能好的盘，优先移走xlog，如果有3个，优先xlog+ example2。
+分开的示例方法如下：
+
+```bash
+PGDATA=/opt/data/mogdb
+cd $PGDATA
+mv pg_xlog /tpccdir1
+ln -s /tpccdir1/pg_xlog .
+cd pg_location
+mv tablespace2 /tpccdir2
+ln -s /tpccdir2/tablespace2 .
+mv tablespace3 /tpccdir3
+ln -s /tpccdir3/tablespace3 .
+```
+
+### 9.观察系统资源工具
+
+- htop 观察CPU使用情况，arm平台需要从源码编译。
+
+  使用htop监控数据库服务端和tpcc客户端CPU利用情况，最佳性能测试情况下，各个业务CPU的占用率都非常高（> 90%）。如果有CPU占用率没有达标，可能是绑核方式不对或其他问题，需要定位找到根因进行调整。
+
+- iostat 查看系统IO使用情况。
+
+- sar 查看网络使用情况。
+
+- nmon 作为系统资源整体监控。
+
+**部分数据截图**
+
+- **数据库htop**
+
+  ![htop](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/TPCC-performance-tuning-guide-1.png)
+
+- **客户端htop**
+
+  ![客户端htop](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/TPCC-performance-tuning-guide-2.png)
+
+- iostat 查看系统IO使用情况
+
+  ![客户端htop](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/TPCC-performance-tuning-guide-3.png)
+
+- sar 查看网络使用情况
+
+  ![客户端htop](https://cdn-mogdb.enmotech.com/docs-media/mogdb/performance-tuning/TPCC-performance-tuning-guide-4.png)
+
+<br/>
+
+## 理想结果
+
+4路鲲鹏 256C， 1000仓500并发：250W TPMC<br/>
+2路鲲鹏服务器  100仓100并发：90W<br/>
+2路鲲鹏服务器  100仓300并发：140W
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/performance-tuning/wdr-snapshot-schema.md b/product/zh/docs-mogdb/v3.0/performance-tuning/wdr-snapshot-schema.md
new file mode 100644
index 0000000000000000000000000000000000000000..87e40cd13c3b8c33a4dbd169c82cc1e973f81448
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/performance-tuning/wdr-snapshot-schema.md
@@ -0,0 +1,181 @@
+---
+title: WDR解读指南
+summary: WDR解读指南
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# WDR解读指南
+
+WDR Snasphot在启动后（打开参数enable_wdr_snapshot），会在用户表空间"pg_default"，数据库"postgres"下新建schema "snapshot"，用于持久化WDR快照数据。默认初始化用户或monadmin用户可以访问Snapshot Schema。
+
+根据参数wdr_snapshot_retention_days来自动管理快照的生命周期。
+
+<br/>
+
+## WDR Snapshot 原信息表
+
+<br/>
+
+### SNAPSHOT.SNAPSHOT
+
+SNAPSHOT表记录当前系统中存储的WDR快照数据的索引信息、开始、结束时间。只能在系统库中查询到结果，在用户库中无法查询。
+
+**表 1** SNAPSHOT表属性
+
+| 名称        | 类型      | 描述                | 示例                          |
+| :---------- | :-------- | :------------------ | :---------------------------- |
+| snapshot_id | bigint    | WDR快照序号。       | 1                             |
+| start_ts    | timestamp | WDR快照的开始时间。 | 2019-12-28 17:11:27.423742+08 |
+| end_ts      | timestamp | WDR快照的结束时间。 | 2019-12-28 17:11:43.67726+08  |
+
+<br/>
+
+### SNAPSHOT.TABLES_SNAP_TIMESTAMP
+
+TABLES_SNAP_TIMESTAMP表记录所有存储的WDR snapshot中数据库、表对象、以及数据采集的开始和结束时间。
+
+**表 2** TABLES_SNAP_TIMESTAMP表属性
+
+| 名称        | 类型      | 描述                         | 示例                          |
+| :---------- | :-------- | :--------------------------- | :---------------------------- |
+| snapshot_id | bigint    | WDR快照序号。                | 1                             |
+| db_name     | text      | WDR snapshot对应的database。 | tpcc1000                      |
+| tablename   | text      | WDR snasphot对应的table。    | snap_xc_statio_all_indexes    |
+| start_ts    | timestamp | WDR快照的开始时间。          | 2019-12-28 17:11:27.425849+08 |
+| end_ts      | timestamp | WDR快照的结束时间。          | 2019-12-28 17:11:27.707398+08 |
+
+### SNAP_SEQ
+
+snap_seq是一个递增的sequence，其为WDR snapshot提供快照的ID。
+
+<br/>
+
+## WDR Snapshot 数据表
+
+WDR Snapshot数据表命名原则：snap_{源数据表}。
+
+WDR Snapshot数据表来源为"DBE_PERF Schema"下所有的视图。
+
+<br/>
+
+## WDR Snapshot生成性能报告
+
+基于WDR Snapshot数据表汇总、统计，生成性能报告。
+
+**前提条件**
+
+WDR Snasphot启动（即参数enable_wdr_snapshot）为on时， 且快照数量大于等于2时可以生成报告。
+
+**操作步骤**
+
+1. 执行以下命令连接postgres数据库。
+
+    ```
+    gsql -d postgres -p 端口号 -r
+    ```
+
+2. 执行如下命令查询已经生成的快照，以获取快照的snapshot_id。
+
+    ```sql
+    select * from snapshot.snapshot;
+    ```
+
+3. （可选）在CCN上执行如下命令手动创建快照。数据库中只有一个快照或者需要查询在当前时段数据库监控的监控数据，可以选择手动执行快照操作,该命令需要用户具有sysadmin权限。
+
+    ```sql
+    select create_wdr_snapshot();
+    ```
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 执行“cm_ctl query -Cdvi”，回显中“Central Coordinator State”下显示的信息即为CCN信息。
+
+4. 执行如下步骤生成性能报告。
+
+    a. 执行如下命令生成格式化性能报告文件。
+
+    ```sql
+    \a \t \o 服务器文件路径
+    ```
+
+    上述命令涉及参数说明如下:
+
+    - \\a: 切换非对齐模式。
+    - \\t: 切换输出的字段名的信息和行计数脚注。
+    - \\o: 把所有的查询结果发送至服务器文件里。
+    - 服务器文件路径：生成性能报告文件存放路径。用户需要拥有此路径的读写权限。
+
+    b. 执行如下命令将查询到的信息写入性能报告中。
+
+    ```sql
+    select generate_wdr_report(begin_snap_id bigint, end_snap_id bigint, report_type cstring, report_scope cstring, node_name cstring);
+    ```
+
+    命令中涉及的参数说明如下。
+
+    **表 3** generate_wdr_report函数参数说明
+
+    | 参数          | 说明             | 取值范围   |
+    | :------------ | :---------------|-----------|
+    | begin_snap_id | 查询时间段开始的snapshot的id（表snapshot.snaoshot中的snapshot_id）。                                                                                                          | -                                                                           |
+    | end_snap_id   | 查询时间段结束snapshot的id。默认end_snap_id大于begin_snap_id（表snapshot.snaoshot中的snapshot_id）。                                                                          | -                                                                           |
+    | report_type   | 指定生成report的类型。例如，summary/detail/all。                                                                                                                              | summary: 汇总数据。<br />detail: 明细数据。<br />all: 包含summary和detail。 |
+    | report_scope  | 指定生成report的范围，可以为cluster或者node。                                                                                                                                 | cluster: 数据库级别的信息。<br />node: 节点级别的信息。                     |
+    | node_name     | 在report_scope指定为node时，需要把该参数指定为对应节点的名称。(节点名称可以执行select * from pg_node_env;查询)。在report_scope为cluster时，该值可以指定为省略、空或者为NULL。 | node: MogDB中的节点名称。<br />cluster: 省略、空或者NULL。                  |
+
+    c.执行如下命令关闭输出选项及格式化输出命令。
+
+    ```
+    \o \a \t
+    ```
+
+5. 根据需要查看WDR报告内容。
+
+   **表 4** WDR报表主要内容
+
+   | 项目                                               | 描述                                                         |
+   | :------------------------------------------------- | :----------------------------------------------------------- |
+   | Database Stat（数据库范围）                        | 数据库维度性能统计信息：事务，读写，行活动，写冲突，死锁等。 |
+   | Load Profile（数据库范围）                         | 数据库维度的性能统计信息：CPU时间，DB时间，逻辑读/物理读，IO性能，登入登出，负载强度，负载性能表现等。 |
+   | Instance Efficiency Percentages（数据库/节点范围） | 数据库级或者节点Buffer Hit（缓冲命中率），Effective CPU（CPU使用率），WalWrite NoWait（获取Wal Buffer成功率），Soft Parse（软解析率），Non-parse CPU（CPU非解析时间比例）。 |
+   | Top 10 Events by Total Wait Time（节点范围）       | 最消耗时间的事件。                                           |
+   | Wait Classes by Total Wait Time（节点范围）        | 最消耗时间的等待事件分类。                                   |
+   | Host CPU（节点范围）                               | 主机CPU消耗。                                                |
+   | Memory Statistics（节点范围）                      | 内核内存使用分布。                                           |
+   | Object stats（节点范围）                           | 表，索引维度的性能统计信息。                                 |
+   | Database Configuration（节点范围）                 | 节点配置。                                                   |
+   | SQL Statistics（节点范围）                         | SQL语句各个维度性能统计：端到端时间，行活动，缓存命中，CPU消耗，时间消耗细分。 |
+   | SQL Detail（节点范围）                             | SQL语句文本详情。                                            |
+
+**示例**
+
+```sql
+--查询已经生成的快照。
+mogdb=# select * from snapshot.snapshot;
+ snapshot_id |           start_ts            |            end_ts
+-------------+-------------------------------+-------------------------------
+           1 | 2020-09-07 10:20:36.763244+08 | 2020-09-07 10:20:42.166511+08
+           2 | 2020-09-07 10:21:13.416352+08 | 2020-09-07 10:21:19.470911+08
+(2 rows)
+
+--生成格式化性能报告wdrTestNode.html。
+mogdb=# \a \t \o /home/om/wdrTestNode.html
+Output format is unaligned.
+Showing only tuples.
+
+--向性能报告wdrTestNode.html中写入数据。
+mogdb=# select generate_wdr_report(1, 2, 'all', 'node', 'dn');
+
+--关闭性能报告wdrTestNode.html。
+mogdb=# \o
+
+--生成格式化性能报告wdrTestCluster.html。
+mogdb=# \o /home/om/wdrTestCluster.html
+
+--向格式化性能报告wdrTestCluster.html中写入数据。
+mogdb=# select generate_wdr_report(1, 2, 'all', 'cluster');
+
+--关闭性能报告wdrTestCluster.html。
+mogdb=# \o \a \t
+Output format is aligned.
+Tuples only is off.
+```
diff --git a/product/zh/docs-mogdb/v3.0/poc/poc-jiangsumobile.assets/image-20210312105303222.png b/product/zh/docs-mogdb/v3.0/poc/poc-jiangsumobile.assets/image-20210312105303222.png
new file mode 100644
index 0000000000000000000000000000000000000000..616e33e610b0bca7f20fbef6bea75996c69b2d46
Binary files /dev/null and b/product/zh/docs-mogdb/v3.0/poc/poc-jiangsumobile.assets/image-20210312105303222.png differ
diff --git a/product/zh/docs-mogdb/v3.0/poc/poc-jiangsumobile.assets/image-20210312105352146.png b/product/zh/docs-mogdb/v3.0/poc/poc-jiangsumobile.assets/image-20210312105352146.png
new file mode 100644
index 0000000000000000000000000000000000000000..7d8d8d38fe5770b45b9a0b17ef3a9208d55d9133
Binary files /dev/null and b/product/zh/docs-mogdb/v3.0/poc/poc-jiangsumobile.assets/image-20210312105352146.png differ
diff --git a/product/zh/docs-mogdb/v3.0/poc/poc-jiangsumobile.md b/product/zh/docs-mogdb/v3.0/poc/poc-jiangsumobile.md
new file mode 100644
index 0000000000000000000000000000000000000000..e8930d403a51548730c386926acd139bc98f44a6
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/poc/poc-jiangsumobile.md
@@ -0,0 +1,1618 @@
+# 某省移动MogDB 1.1.0版本测试报告
+
+## POC前准备工作
+
+### 操作系统版本及下载地址
+
+| 介质名称                                                                                                                              | 介质大小 | 最后更新时间      |
+| ------------------------------------------------------------------------------------------------------------------------------------- | -------- | ----------------- |
+| [openEuler-20.03-LTS-aarch64-dvd.iso](https://repo.openeuler.org/openEuler-20.03-LTS/ISO/aarch64/openEuler-20.03-LTS-aarch64-dvd.iso) | 4.3 GiB  | 2020-Mar-26 14:46 |
+
+#### 用户名和组
+
+| 组名      | 组ID     | 用途          |
+| --------- | -------- | ------------- |
+| root      | 0        | administrator |
+| bomc      | 1302     | 网管          |
+| osmgr     | 1800     | OS管理        |
+| xtjgmons  | 5000     | 系统维护      |
+| ==dbgrp== | ==5002== | ==MogDB==     |
+
+| 用户名   | 用户ID   | 所属用户组 | Home目录      | Shell     | 用途              |
+| -------- | -------- | ---------- | ------------- | --------- | ----------------- |
+| root     | 0        | root       | /root         | /bin/bash | administrator     |
+| toptea   | 1302     | bomc       | /toptea       | /bin/bash | 网管              |
+| osmgr    | 1800     | osmgr      | /home/osmgr   | /bin/bash | OS管理            |
+| dutyview | 5000     | xtjgmons   | 5000          | 无        | 无                |
+| dutywath | 5001     | xtjgmons   | 5000          | 无        | 无                |
+| ==omm==  | ==5002== | ==dbgrp==  | ====/home/omm | 无        | ==MogDB==系统用户 |
+
+### 本地盘划分
+
+| lv卷名             | 文件系统   | 大小 | 属组  | 权限 | 系统格式 | 用途                                                     |
+| ------------------ | ---------- | ---- | ----- | ---- | -------- | -------------------------------------------------------- |
+| vg_og/lv_ogdata    | /ogdata    | 2T   | dbgrp | 755  | ext4     | datapath 存放数据文件                                    |
+| vg_og/lv_ogxlog    | /ogxlog    | 500G | dbgrp | 755  | ext4     | 存放redo日志                                             |
+| vg_og/lv_ogarchive | /ogarchive | 1T   | dbgrp | 755  | ext4     | 存放归档日志                                             |
+| rootvg             | /mogdb     | 200G | dbgrp | 755  | ext4     | 存放数据库二进制、日志、临时文件、socket文件、om维护命令 |
+| vg_og/lv_ogbackup  | /og_bak    | 6T   | dbgrp | 755  | ext4     | 存放数据备份                                             |
+
+## 服务器配置
+
+| 机房位置     | 机架位置  | 设备数量 | 设备型号     |
+| ------------ | --------- | -------- | ------------ |
+| 浦口高新机房 | C11(2台） | 2        | 华为100 T130 |
+
+| 型号        | CPU                | 内存 | 硬盘                                                      | 数量 |
+| ----------- | ------------------ | ---- | --------------------------------------------------------- | ---- |
+| 华为100 T30 | 鲲鹏920 (48core)*2 | 384G | OS盘:   2块600G SAS RAID1 <br />数据盘: 6块3.2T SSD RAID5 | 2台  |
+
+## IP地址
+
+| 设备 | 主机名   | 主机型号     | 机柜 | 管理地址      | 业务地址      |
+| ---- | -------- | ------------ | ---- | ------------- | ------------- |
+| 华为 | npromgs3 | 华为100 T130 | C11  | 190.168.80.79 | 10.32.225.150 |
+| 华为 | npromgs4 | 华为100 T130 | C11  | 190.168.80.80 | 10.32.225.151 |
+
+## 操作系统版本
+
+```
+openEuler 20.3LTS
+##
+```
+
+## 数据库信息
+
+### 数据库版本
+
+```
+gsql ((MogDB 1.1.0 build 5be05d82) compiled at 2021-01-06 17:23:14 commit 0 last mr  )
+```
+
+### 数据库主备信息
+
+| 主库 | IP: 10.32.225.150 | 读写 |
+| ---- | ----------------- | ---- |
+| 备库 | IP: 10.32.225.151 | 只读 |
+
+## 测试结果所在目录
+
+### IP: 10.32.225.150
+
+| 测试项         | 目录                               |
+| -------------- | ---------------------------------- |
+| 测试用例及日志 | /og_bak                            |
+| TPCC测试及日志 | /root/benchmarksql-5.0/run/tpcclog |
+
+## 功能测试
+
+### 兼容性
+
+| 测试项          | 测试结果 | 说明                                                                                                           |
+| --------------- | -------- | -------------------------------------------------------------------------------------------------------------- |
+| 数据类型        | 通过     | 对于数值类型 字符类型 二进制类型 日期类型 布尔类型 时间间隔类型 数组类型 json类型等常用数据类型支持情况。      |
+| 字符集          | 通过     | 支持utf-8(MySQL中应为utf8mb4)，gbk等常见字符格式类型                                                           |
+| 基本SQL语法     | 通过     | 增删改查操作                                                                                                   |
+| 复杂SQL         | 通过     | 多种连接查询，包括交叉连接、自然连接、jion…using、jion..on、自连接、内连接、外连接                             |
+| 常用函数        | 通过     | union、union all、intersect等集合操作符                                                                        |
+| 操作符          | 通过     | 逻辑操作符and or not                                                                                           |
+| SQL语法及兼容性 | 通过     | commit/rollback/grant等DCL操作                                                                                 |
+| 其他高级SQL兼容 | 通过     | on duplicate key update、WITH RECURSIVE（start with … connect、with as、lock table、create table if not exists |
+| 数据分区        | 通过     | 测试范围分区: 支持增加、拆分、合并、交换、删除分区                                                             |
+| 索引管理        | 通过     | 创建表并创建普通索引                                                                                           |
+| 约束            | 通过     | 创建表并创建约束                                                                                               |
+| 事务一致性      | 通过     | 原子性、一致性、隔离性、持久性特性                                                                             |
+| mvcc            | 通过     | 写之间不阻塞。SELECT是纯读操作，UPDATE和DELETE是读写操作。                                                     |
+| mot             | 通过     | 内存表                                                                                                         |
+
+### 优化器
+
+| 测试项       | 测试结果 | 说明                          |
+| ------------ | -------- | ----------------------------- |
+| 执行计划解析 | 通过     | 能够显式展现SQL语句的执行计划 |
+| hint         | 通过     | 能够支持加hint                |
+| 查询转换     | 通过     | 支持查询转换                  |
+
+### 高级功能
+
+| 测试项   | 测试结果 | 说明                                     |
+| -------- | -------- | ---------------------------------------- |
+| 存储过程 | 通过     | 测试存储过程的基本功能和过程中的控制语句 |
+| 函数     | 通过     | 测试存储函数的创建和删除操作             |
+| 视图     | 通过     | 支持视图建立、修改、删除                 |
+| 游标     | 通过     | 测试定义并使用引用游标                   |
+| 触发器   | 通过     | 测试insert/update/delete/instead of      |
+| 序列     | 通过     | 创建并使用序列、获取序列当前值和下一值   |
+
+## 安全性测试
+
+| 测试项       | 测试结果 | 说明                                                         |
+| ------------ | -------- | ------------------------------------------------------------ |
+| 用户权限管理 | 通过     | 权限管理                                                     |
+| 角色权限管理 | 通过     | 角色管理                                                     |
+| 身份鉴别     | 通过     | 配置密码复杂度检查，密码的不可重用天数，帐户登录失败尝试次数 |
+| 审计日志     | 通过     | 记录用户登录退出的审计日志                                   |
+
+## 高可用测试
+
+| 测试项       | 测试结果 | 说明                                                 |
+| ------------ | -------- | ---------------------------------------------------- |
+| 读写分离     | 通过     | 主库建测试表，备库去读取内容                         |
+| 保护模式配置 | 通过     | 通过参数控制保护模式，同步模式（同步，异步，半同步） |
+
+## 备份恢复测试
+
+| 测试项                 | 测试结果 | 说明                                                                             |
+| ---------------------- | -------- | -------------------------------------------------------------------------------- |
+| 物理备份全量备份和恢复 | 通过     | 主库建测试表，备库去读取内容                                                     |
+| 逻辑备份和恢复         | 通过     | 是否支持在线逻辑备份，验证备份后数据恢复正确性和效率，在线备份期间对性能的影响。 |
+
+## 运维管理测试
+
+| 测试项       | 测试结果 | 说明                                                                        |
+| ------------ | -------- | --------------------------------------------------------------------------- |
+| 报错信息     | 通过     | [errorcode](https://support.huaweicloud.com/errorcode-dws/dws_08_0001.html) |
+| 性能视图     | 通过     | 和数据库相关的性能视图                                                      |
+| 性能分析报告 | 通过     | WDR类似Oracle AWR                                                           |
+| 慢SQL视图    | 通过     |                                                                             |
+| 日志管理     | 通过     | 系统日志，操作日志，Trace日志，黑匣子日志，审计日志，WAL日志，性能日志。    |
+| 监控运维     | 通过     | 常用的运维和定位问题手段                                                    |
+
+## 性能测试
+
+### TPCC
+
+#### 测试工具BenchmarkSQL v5.0及参数
+
+| 序号 | 参数名称   | 值                                           |
+| ---- | ---------- | -------------------------------------------- |
+| 1    | db         | postgres                                     |
+| 2    | driver     | org.postgresql.Driver                        |
+| 3    | conn       | jdbc:postgresql://10.32.225.150:6432/tpcctst |
+| 4    | user       | tpccuser                                     |
+| 5    | warehouses | 10000                                        |
+
+> 说明:数据总容量大约100GB
+
+#### 测试用表的数据量
+
+| 序号 | 表名             | 数据总数             |
+| ---- | ---------------- | -------------------- |
+| 1    | bmsql_config     | 4                    |
+| 2    | bmsql_custome    | 30014788             |
+| 3    | bmsql_district   | 10000                |
+| 4    | bmsql_history    | 29996623             |
+| 5    | bmsql_item       | 100000               |
+| 6    | bmsql_new_order  | 9000105              |
+| 7    | bmsql_oorder     | 29995891             |
+| 8    | bmsql_order_line | 299981583（约1.9亿） |
+| 9    | bmsql_stock      | 100002396（约1亿）   |
+| 10   | bmsql_warehouse  | 1000                 |
+
+#### 测试结果
+
+| 并发 | 时长（分钟） | tpmC （NewOrders） |
+| ---- | ------------ | ------------------ |
+| 400  | 1            | 383010.44          |
+| 400  | 2            | 396593.65          |
+| 400  | 5            | 366825.72          |
+| 400  | 10           | 369191.96          |
+
+### TPCH
+
+#### 测试用表的数据量
+
+##### 工具导入3GB数据
+
+![image-20210312105303222](https://cdn-mogdb.enmotech.com/docs-media/111.png)
+
+##### 工具导入 TPC-H 30G 数据
+
+![image-20210312105352146](https://cdn-mogdb.enmotech.com/docs-media/115.png)
+
+#### 测试结果
+
+| 查询语句说明                                     | Query ID | 3GB数据      | 30GB数据      |
+| ------------------------------------------------ | -------- | ------------ | ------------- |
+| 价格统计报告查询                                 | Q1       | 86290.621 ms | 867229.922 ms |
+| 最小代价供货商查询                               | Q2       | 1588.686 ms  | 29948.139 ms  |
+| 运送优先级查询                                   | Q3       | 9930.242 ms  | 153179.243 ms |
+| 订单优先级查询                                   | Q4       | 2413.140 ms  | 29535.320 ms  |
+| 某地区供货商为公司带来的收入查询                 | Q5       | 12687.063 ms | 146917.921 ms |
+| 预测收入变化查询                                 | Q6       | 3381.666 ms  | 77716.338 ms  |
+| 货运盈利情况查询                                 | Q7       | 6423.072 ms  | 142928.852 ms |
+| 国家市场份额查询                                 | Q8       | 7985.378 ms  | 103726.748 ms |
+| 产品类型利润估量查询                             | Q9       | 28462.979 ms | 366562.292 ms |
+| 货运存在问题的查询                               | Q10      | 10098.798 ms | 149445.271 ms |
+| 库存价值查询                                     | Q11      | 1915.023 ms  | 23855.269 ms  |
+| 货运模式和订单优先级查询                         | Q12      | 11048.061 ms | 119823.533 ms |
+| 消费者订单数量查询                               | Q13      | 9149.003 ms  | 116618.514 ms |
+| 促销效果查询                                     | Q14      | 1024.503 ms  | 29369.667 ms  |
+| 查询获得某段时间内为总收入贡献最多的供货商的信息 | Q15      | 3011.973 ms  | 101147.519 ms |
+| 零件/供货商关系查询                              | Q16      | 2253.134 ms  | 28748.335 ms  |
+| 小订单收入查询                                   | Q17      | 35671.622 ms | 420488.742 ms |
+| 大订单顾客查询                                   | Q18      | 30810.445 ms | 461710.335 ms |
+| 折扣收入查询                                     | Q19      | 10483.329 ms | 107313.130 ms |
+| 供货商竞争力查询                                 | Q20      | 7903.905 ms  | 161276.226 ms |
+| 不能按时交货供货商查询                           | Q21      | 20424.039 ms | 264827.982 ms |
+| 全球销售机会查询                                 | Q22      | 3458.196 ms  | 50860.840 ms  |
+
+#### TPCH测试SQL
+
+##### Q1
+
+```
+select
+
+  l_returnflag,
+
+  l_linestatus,
+
+  sum(l_quantity) as sum_qty,
+
+  sum(l_extendedprice) as sum_base_price,
+
+  sum(l_extendedprice * (1 - l_discount)) as sum_disc_price,
+
+  sum(l_extendedprice * (1 - l_discount) * (1 + l_tax)) as sum_charge,
+
+  avg(l_quantity) as avg_qty,
+
+  avg(l_extendedprice) as avg_price,
+
+  avg(l_discount) as avg_disc,
+
+  count(*) as count_order
+
+from
+
+  lineitem
+
+where
+
+  l_shipdate <= date '1998-12-01' - interval '103' day
+
+group by
+
+  l_returnflag,
+
+  l_linestatus
+
+order by
+
+  l_returnflag,
+
+  l_linestatus
+
+LIMIT 1;
+```
+
+##### Q2
+
+```
+select
+
+  s_acctbal,
+
+  s_name,
+
+  n_name,
+
+  p_partkey,
+
+  p_mfgr,
+
+  s_address,
+
+  s_phone,
+
+  s_comment
+
+from
+
+  part,
+
+  supplier,
+
+  partsupp,
+
+  nation,
+
+  region,
+
+  (
+
+​    select
+
+​      ps_partkey,
+
+​      min(ps_supplycost) as min
+
+​    from
+
+​      partsupp,
+
+​      supplier,
+
+​      nation,
+
+​      region
+
+​    where
+
+​      s_suppkey = ps_suppkey
+
+​      and s_nationkey = n_nationkey
+
+​      and n_regionkey = r_regionkey
+
+​      and r_name = 'EUROPE'
+
+​    group by
+
+​      ps_partkey
+
+  ) temp
+
+where
+
+  p_partkey = partsupp.ps_partkey
+
+  and s_suppkey = ps_suppkey
+
+  and p_size = 47
+
+  and p_type like '%BRASS'
+
+  and s_nationkey = n_nationkey
+
+  and n_regionkey = r_regionkey
+
+  and r_name = 'EUROPE'
+
+  and ps_supplycost = temp.min
+
+  and p_partkey = temp.ps_partkey
+
+order by
+
+  s_acctbal desc,
+
+  n_name,
+
+  s_name,
+
+  p_partkey
+
+LIMIT 100;
+```
+
+#### Q3
+
+```
+select
+
+  l_orderkey,
+
+  sum(l_extendedprice * (1 - l_discount)) as revenue,
+
+  o_orderdate,
+
+  o_shippriority
+
+from
+
+  customer,
+
+  orders,
+
+  lineitem
+
+where
+
+  c_mktsegment = 'BUILDING'
+
+  and c_custkey = o_custkey
+
+  and l_orderkey = o_orderkey
+
+  and o_orderdate < date '1995-03-20'
+
+  and l_shipdate > date '1995-03-20'
+
+group by
+
+  l_orderkey,
+
+  o_orderdate,
+
+  o_shippriority
+
+order by
+
+  revenue desc,
+
+  o_orderdate
+
+LIMIT 10;
+```
+
+##### Q4
+
+```
+select
+
+  o_orderpriority,
+
+  count(*) as order_count
+
+from
+
+  orders
+
+where
+
+  o_orderdate >= date '1995-12-01'
+
+  and o_orderdate < date '1995-12-01' + interval '3' month
+
+  and exists
+
+  (
+
+​    select
+
+​      *
+
+​    from
+
+​      lineitem
+
+​    where
+
+​      l_orderkey = o_orderkey
+
+​      and l_commitdate < l_receiptdate
+
+​    limit 1
+
+  )
+
+group by
+
+  o_orderpriority
+
+order by
+
+  o_orderpriority
+
+LIMIT 1;
+```
+
+##### Q5
+
+```
+select
+
+  n_name,
+
+  sum(l_extendedprice * (1 - l_discount)) as revenue
+
+from
+
+  customer,
+
+  orders,
+
+  lineitem,
+
+  supplier,
+
+  nation,
+
+  region
+
+where
+
+  c_custkey = o_custkey
+
+  and l_orderkey = o_orderkey
+
+  and l_suppkey = s_suppkey
+
+  and c_nationkey = s_nationkey
+
+  and s_nationkey = n_nationkey
+
+  and n_regionkey = r_regionkey
+
+  and r_name = 'AMERICA'
+
+  and o_orderdate >= date '1997-01-01'
+
+  and o_orderdate < date '1997-01-01' + interval '1' year
+
+group by
+
+  n_name
+
+order by
+
+  revenue desc
+
+LIMIT 1;
+```
+
+##### Q6
+
+```
+select
+
+  sum(l_extendedprice * l_discount) as revenue
+
+from
+
+  lineitem
+
+where
+
+  l_shipdate >= date '1997-01-01'
+
+  and l_shipdate < date '1997-01-01' + interval '1' year
+
+  and l_discount between 0.07 - 0.01 and 0.07 + 0.01
+
+  and l_quantity < 24
+
+LIMIT 1;
+```
+
+##### Q7
+
+```
+select
+
+  supp_nation,
+
+  cust_nation,
+
+  l_year,
+
+  sum(volume) as revenue
+
+from
+
+(
+
+  select
+
+​    n1.n_name as supp_nation,
+
+​    n2.n_name as cust_nation,
+
+​    extract(year from l_shipdate) as l_year,
+
+​    l_extendedprice * (1 - l_discount) as volume
+
+  from
+
+​    supplier,
+
+​    lineitem,
+
+​    orders,
+
+​    customer,
+
+​    nation n1,
+
+​    nation n2
+
+  where
+
+​    s_suppkey = l_suppkey
+
+​    and o_orderkey = l_orderkey
+
+​    and c_custkey = o_custkey
+
+​    and s_nationkey = n1.n_nationkey
+
+​    and c_nationkey = n2.n_nationkey
+
+​    and
+
+​    (
+
+​      (n1.n_name = 'CHINA' and n2.n_name = 'INDONESIA')
+
+​      or (n1.n_name = 'INDONESIA' and n2.n_name = 'CHINA')
+
+​    )
+
+​    and l_shipdate between date '1995-01-01' and date '1996-12-31'
+
+) as shipping
+
+group by
+
+  supp_nation,
+
+  cust_nation,
+
+  l_year
+
+order by
+
+  supp_nation,
+
+  cust_nation,
+
+  l_year
+
+LIMIT 1;
+```
+
+##### Q8
+
+```
+select
+
+  o_year,
+
+  sum(case
+
+  when nation = 'INDONESIA' then volume
+
+  else 0
+
+  end) / sum(volume) as mkt_share
+
+from
+
+(
+
+  select
+
+​    extract(year from o_orderdate) as o_year,
+
+​    l_extendedprice * (1 - l_discount) as volume,
+
+​    n2.n_name as nation
+
+​    from
+
+​    part,
+
+​    supplier,
+
+​    lineitem,
+
+​    orders,
+
+​    customer,
+
+​    nation n1,
+
+​    nation n2,
+
+​    region
+
+  where
+
+​    p_partkey = l_partkey
+
+​    and s_suppkey = l_suppkey
+
+​    and l_orderkey = o_orderkey
+
+​    and o_custkey = c_custkey
+
+​    and c_nationkey = n1.n_nationkey
+
+​    and n1.n_regionkey = r_regionkey
+
+​    and r_name = 'ASIA'
+
+​    and s_nationkey = n2.n_nationkey
+
+​    and o_orderdate between date '1995-01-01' and date '1996-12-31'
+
+​    and p_type = 'PROMO POLISHED TIN'
+
+) as all_nations
+
+group by
+
+  o_year
+
+order by
+
+  o_year
+
+LIMIT 1;
+```
+
+##### Q9
+
+```
+select
+
+  nation,
+
+  o_year,
+
+  sum(amount) as sum_profit
+
+from
+
+(
+
+  select
+
+​    n_name as nation,
+
+​    extract(year from o_orderdate) as o_year,
+
+​    l_extendedprice * (1 - l_discount) - ps_supplycost * l_quantity as amount
+
+  from
+
+​    part,
+
+​    supplier,
+
+​    lineitem,
+
+​    partsupp,
+
+​    orders,
+
+​    nation
+
+  where
+
+​    s_suppkey = l_suppkey
+
+​    and ps_suppkey = l_suppkey
+
+​    and ps_partkey = l_partkey
+
+​    and p_partkey = l_partkey
+
+​    and o_orderkey = l_orderkey
+
+​    and s_nationkey = n_nationkey
+
+​    and p_name like '%thistle%'
+
+) as profit
+
+group by
+
+  nation,
+
+  o_year
+
+order by
+
+  nation,
+
+  o_year desc
+
+LIMIT 1;
+```
+
+##### Q10
+
+```
+select
+
+  c_custkey,
+
+  c_name,
+
+  sum(l_extendedprice * (1 - l_discount)) as revenue,
+
+  c_acctbal,
+
+  n_name,
+
+  c_address,
+
+  c_phone,
+
+  c_comment
+
+from
+
+  customer,
+
+  orders,
+
+  lineitem,
+
+  nation
+
+where
+
+  c_custkey = o_custkey
+
+  and l_orderkey = o_orderkey
+
+  and o_orderdate >= date '1994-06-01'
+
+  and o_orderdate < date '1994-06-01' + interval '3' month
+
+  and l_returnflag = 'R'
+
+  and c_nationkey = n_nationkey
+
+group by
+
+  c_custkey,
+
+  c_name,
+
+  c_acctbal,
+
+  c_phone,
+
+  n_name,
+
+  c_address,
+
+  c_comment
+
+order by
+
+  revenue desc
+
+LIMIT 20;
+```
+
+##### Q11
+
+```
+select
+
+  ps_partkey,
+
+  sum(ps_supplycost * ps_availqty) as value
+
+from
+
+  partsupp,
+
+  supplier,
+
+  nation
+
+where
+
+  ps_suppkey = s_suppkey
+
+  and s_nationkey = n_nationkey
+
+  and n_name = 'ALGERIA'
+
+group by
+
+  ps_partkey having
+
+  sum(ps_supplycost * ps_availqty) >
+
+  (
+
+​    select
+
+​      sum(ps_supplycost * ps_availqty) * 0.0001000000
+
+​    from
+
+​      partsupp,
+
+​      supplier,
+
+​      nation
+
+​    where
+
+​      ps_suppkey = s_suppkey
+
+​      and s_nationkey = n_nationkey
+
+​      and n_name = 'ALGERIA'
+
+  )
+
+order by
+
+  value desc
+
+LIMIT 1;
+```
+
+##### Q12
+
+```
+select
+
+  l_shipmode,
+
+  sum(case when o_orderpriority = '1-URGENT' or o_orderpriority = '2-HIGH' then 1 else 0 end) as high_line_count,
+
+  sum(case when o_orderpriority <> '1-URGENT' and o_orderpriority <> '2-HIGH' then 1 else 0 end) as low_line_count
+
+from
+
+  orders,
+
+  lineitem
+
+where
+
+  o_orderkey = l_orderkey
+
+  and l_shipmode in ('RAIL', 'SHIP')
+
+  and l_commitdate < l_receiptdate
+
+  and l_shipdate < l_commitdate
+
+  and l_receiptdate >= date '1994-01-01'
+
+  and l_receiptdate < date '1994-01-01' + interval '1' year
+
+group by
+
+  l_shipmode
+
+order by
+
+  l_shipmode
+
+LIMIT 1;
+```
+
+##### Q13
+
+```
+select
+
+  c_count,
+
+  count(*) as custdist
+
+from
+
+(
+
+  select
+
+​    c_custkey,
+
+​    count(o_orderkey)
+
+  from
+
+​    customer left outer join orders on
+
+​    c_custkey = o_custkey
+
+​    and o_comment not like '%express%packages%'
+
+  group by
+
+​    c_custkey
+
+) as c_orders (c_custkey, c_count)
+
+group by
+
+  c_count
+
+order by
+
+  custdist desc,
+
+  c_count desc
+
+LIMIT 1;
+```
+
+##### Q14
+
+```
+select
+
+  100.00 * sum(case when p_type like 'PROMO%' then l_extendedprice * (1 - l_discount) else 0 end) /sum(l_extendedprice * (1 - l_discount)) as promo_revenue
+
+from
+
+  lineitem,
+
+  part
+
+where
+
+  l_partkey = p_partkey
+
+  and l_shipdate >= date '1994-02-01'
+
+  and l_shipdate < date '1994-02-01' + interval '1' month
+
+LIMIT 1;
+```
+
+##### 用到的视图
+
+```
+create or replace view revenue0 (supplier_no, total_revenue) as
+
+select
+
+  l_suppkey,
+
+  sum(l_extendedprice * (1 - l_discount))
+
+from
+
+  lineitem
+
+where
+
+  l_shipdate >= date '1994-02-01'
+
+  and l_shipdate < date '1994-02-01' + interval '3' month
+
+group by
+
+  l_suppkey;
+```
+
+##### Q15
+
+```
+select
+
+  s_suppkey,
+
+  s_name,
+
+  s_address,
+
+  s_phone,
+
+  total_revenue
+
+from
+
+  supplier,
+
+  revenue0
+
+where
+
+  s_suppkey = supplier_no
+
+  and total_revenue =
+
+  (
+
+​    select
+
+​      max(total_revenue)
+
+​    from
+
+​      revenue0
+
+  )
+
+order by
+
+  s_suppkey
+
+LIMIT 1;
+```
+
+##### Q16
+
+```
+select
+
+  p_brand,
+
+  p_type,
+
+  p_size,
+
+  count(distinct ps_suppkey) as supplier_cnt
+
+from
+
+  partsupp,
+
+  part
+
+where
+
+   p_partkey = ps_partkey
+
+   and p_brand <> 'Brand#55'
+
+   and p_type not like 'MEDIUM PLATED%'
+
+   and p_size in (35, 17, 43, 49, 19, 41, 30, 47)
+
+   and ps_suppkey not in
+
+   (
+
+​     select
+
+​       s_suppkey
+
+​     from
+
+​       supplier
+
+​     where
+
+​       s_comment like '%Customer%Complaints%'
+
+  )
+
+group by
+
+  p_brand,
+
+  p_type,
+
+  p_size
+
+order by
+
+  supplier_cnt desc,
+
+  p_brand,
+
+  p_type,
+
+  p_size
+
+LIMIT 1;
+```
+
+##### Q17
+
+```
+select
+
+  sum(l_extendedprice) / 7.0 as avg_yearly
+
+from
+
+  lineitem,
+
+  part,
+
+  (SELECT l_partkey AS agg_partkey, 0.2 * avg(l_quantity) AS avg_quantity FROM lineitem GROUP BY l_partkey) part_agg
+
+where
+
+  p_partkey = l_partkey
+
+  and agg_partkey = l_partkey
+
+  and p_brand = 'Brand#53'
+
+  and p_container = 'JUMBO JAR'
+
+  and l_quantity < avg_quantity
+
+LIMIT 1;
+```
+
+#### Q18
+
+```
+select
+
+  c_name,
+
+  c_custkey,
+
+  o_orderkey,
+
+  o_orderdate,
+
+  o_totalprice,
+
+  sum(l_quantity)
+
+from
+
+  customer,
+
+  orders,
+
+  lineitem
+
+where
+
+  o_orderkey in
+
+  (
+
+​    select
+
+​      l_orderkey
+
+​    from
+
+​      lineitem
+
+​    group by
+
+​      l_orderkey having
+
+​      sum(l_quantity) > 313
+
+  )
+
+  and c_custkey = o_custkey
+
+  and o_orderkey = l_orderkey
+
+group by
+
+  c_name,
+
+  c_custkey,
+
+  o_orderkey,
+
+  o_orderdate,
+
+  o_totalprice
+
+order by
+
+  o_totalprice desc,
+
+  o_orderdate
+
+LIMIT 100;
+```
+
+##### Q19
+
+```
+select
+
+  sum(l_extendedprice* (1 - l_discount)) as revenue
+
+from
+
+  lineitem,
+
+  part
+
+where
+
+  (
+
+​     p_partkey = l_partkey
+
+​     and p_brand = 'Brand#42'
+
+​     and p_container in ('SM CASE', 'SM BOX', 'SM PACK', 'SM PKG')
+
+​     and l_quantity >= 6 and l_quantity <= 6 + 10
+
+​     and p_size between 1 and 5
+
+​     and l_shipmode in ('AIR', 'AIR REG')
+
+​     and l_shipinstruct = 'DELIVER IN PERSON'
+
+  )
+
+  or
+
+  (
+
+​     p_partkey = l_partkey
+
+​     and p_brand = 'Brand#55'
+
+​     and p_container in ('MED BAG', 'MED BOX', 'MED PKG', 'MED PACK')
+
+​     and l_quantity >= 20 and l_quantity <= 20 + 10
+
+​     and p_size between 1 and 10
+
+​     and l_shipmode in ('AIR', 'AIR REG')
+
+​     and l_shipinstruct = 'DELIVER IN PERSON'
+
+  )
+
+  or
+
+  (
+
+​     p_partkey = l_partkey
+
+​     and p_brand = 'Brand#24'
+
+​     and p_container in ('LG CASE', 'LG BOX', 'LG PACK', 'LG PKG')
+
+​     and l_quantity >= 23 and l_quantity <= 23 + 10
+
+​     and p_size between 1 and 15
+
+​     and l_shipmode in ('AIR', 'AIR REG')
+
+​     and l_shipinstruct = 'DELIVER IN PERSON'
+
+  )
+
+LIMIT 1;
+```
+
+##### Q20
+
+```
+select s_name,s_address
+
+from supplier,nation
+
+where
+
+  s_suppkey in
+
+  (select ps_suppkey
+
+​    from partsupp,
+
+​      (
+
+​        select
+
+​          l_partkey agg_partkey,
+
+​          l_suppkey agg_suppkey,
+
+​          0.5 * sum(l_quantity) AS agg_quantity
+
+​        from
+
+​          lineitem
+
+​        where
+
+​          l_shipdate >= date '1997-01-01'
+
+​          and l_shipdate < date '1997-01-01' + interval '1' year
+
+​        group by
+
+​          l_partkey,
+
+​          l_suppkey
+
+​      ) agg_lineitem
+
+​    where
+
+​      agg_partkey = ps_partkey
+
+​      and agg_suppkey = ps_suppkey
+
+​      and ps_partkey in
+
+​      (
+
+​        select
+
+​          p_partkey
+
+​        from
+
+​          part
+
+​        where
+
+​          p_name like 'frosted%'
+
+​      )
+
+​      and ps_availqty > agg_quantity
+
+  )
+
+  and s_nationkey = n_nationkey
+
+  and n_name = 'UNITED STATES'
+
+order by
+
+  s_name
+
+LIMIT 1;
+```
+
+##### Q21
+
+```
+select
+
+  s_name,
+
+  count(*) as numwait
+
+from
+
+  supplier,
+
+  lineitem l1,
+
+  orders,
+
+  nation
+
+where
+
+  s_suppkey = l1.l_suppkey
+
+  and o_orderkey = l1.l_orderkey
+
+  and o_orderstatus = 'F'
+
+  and l1.l_receiptdate > l1.l_commitdate
+
+  and exists
+
+  (
+
+​    select
+
+​      *
+
+​    from
+
+​      lineitem l2
+
+​    where
+
+​      l2.l_orderkey = l1.l_orderkey
+
+​      and l2.l_suppkey <> l1.l_suppkey
+
+  )
+
+  and not exists
+
+  (
+
+​    select
+
+​      *
+
+​    from
+
+​      lineitem l3
+
+​    where
+
+​      l3.l_orderkey = l1.l_orderkey
+
+​      and l3.l_suppkey <> l1.l_suppkey
+
+​      and l3.l_receiptdate > l3.l_commitdate
+
+  )
+
+  and s_nationkey = n_nationkey
+
+  and n_name = 'VIETNAM'
+
+group by
+
+  s_name
+
+order by
+
+  numwait desc,
+
+  s_name
+
+LIMIT 100;
+```
+
+##### Q22
+
+```
+select
+
+  cntrycode,
+
+  count(*) as numcust,
+
+  sum(c_acctbal) as totacctbal
+
+from
+
+(
+
+  select
+
+​    substring(c_phone from 1 for 2) as cntrycode,
+
+​    c_acctbal
+
+  from
+
+​    customer
+
+  where
+
+​    substring(c_phone from 1 for 2) in
+
+​    ('34', '18', '30', '24', '33', '22', '29')
+
+​    and c_acctbal >
+
+​    (
+
+​      select
+
+​        avg(c_acctbal)
+
+​      from
+
+​        customer
+
+​      where
+
+​        c_acctbal > 0.00
+
+​        and substring(c_phone from 1 for 2) in
+
+​        ('34', '18', '30', '24', '33', '22', '29')
+
+​    )
+
+​    and not exists
+
+​    (
+
+​      select
+
+​        *
+
+​      from
+
+​        orders
+
+​      where
+
+​        o_custkey = c_custkey
+
+​    )
+
+) as custsale
+
+group by
+
+  cntrycode
+
+order by
+
+  cntrycode
+
+LIMIT 1;
+```
diff --git a/product/zh/docs-mogdb/v3.0/quick-start/container-based-installation.md b/product/zh/docs-mogdb/v3.0/quick-start/container-based-installation.md
new file mode 100644
index 0000000000000000000000000000000000000000..9c5cd0ebb1b520ab87a1355bd4e7b47f35e8fa3c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/quick-start/container-based-installation.md
@@ -0,0 +1,204 @@
+---
+title: 容器化MogDB安装
+summary: 容器化MogDB安装
+author: Guo Huan
+date: 2021-03-30
+---
+
+# 容器化MogDB安装
+
+本文档主要介绍MogDB容器版安装过程。MogDB容器版本不支持 MogHA工具、OM工具，目前最多支持一主八备。MogDB 2.1容器版支持最新版的compat-tools和插件功能。<br/>由于考虑尽可能缩减容器镜像的大小，以方便快速下载和部署，从2.0版本开始，容器化MogDB在容器里运行的操作系统在x86和ARM架构下分别运行在Ubuntu和Debian之上。<br/>
+x86-64架构的MogDB容器运行在Ubuntu 18.04操作系统中。<br/>
+ARM64架构的MogDB容器运行在Debian 10 操作系统中。
+
+<br/>
+
+## Docker部署
+
+### 准备工作
+
+容器化MogDB的安装与宿主机的操作系统无关，能够运行容器引擎的所有操作系统均可支持，比如Linux，Windows，macOS。
+在安装容器版MogDB之前，您需要先安装容器运行时环境，比如Docker。
+
+Docker是一个开源的应用容器引擎，基于Go语言并遵从Apache2.0协议开源。Docker可以让开发者打包他们的应用以及依赖包到一个轻量级、可移植的容器中，然后发布到任何流行的Linux机器上，也可以实现虚拟化。
+
+Docker Desktop下载地址：<https://www.docker.com/products/docker-desktop>
+
+<br/>
+
+### 安装步骤
+
+1. 启动Docker服务。
+
+2. 输入以下命令获取最新版MogDB镜像文件：
+
+    ```bash
+    docker pull swr.cn-north-4.myhuaweicloud.com/mogdb/mogdb:2.1.1
+    ```
+    
+    > 说明：MogDB镜像支持运行在x86和ARM架构中，会根据发起命令的服务器架构自动下载相应的镜像，无需手工指定。
+
+3. 输入以下命令为MogDB创建运行目录，下文以“mogdb”为例：
+
+    ```bash
+    mkdir /mogdb
+    ```
+
+4. 继续输入以下命令创建一个新的容器，将容器命名为“mogdb”，以启动MogDB实例：
+
+    ```bash
+    docker run --name mogdb --privileged=true -d -e GS_PASSWORD=Secretpassword@123  -v /mogdb:/var/lib/mogdb  -p 15432:5432  swr.cn-north-4.myhuaweicloud.com/mogdb/mogdb:2.1.1
+    ```
+
+    对于Windows系统而言：
+
+    - 如果Docker使用Hyper-V做引擎，请依次执行以下命令，在Hyper-V中创建卷的逻辑对象mogdata，然后创建容器：
+
+      ```bash
+      docker volume create mogdata
+
+      docker run --name mogdb --privileged=true -d -e GS_PASSWORD=Secretpassword@123 -v mogdata:/var/lib/mogdb -p 15453:5432  swr.cn-north-4.myhuaweicloud.com/mogdb/mogdb:2.1.1
+      ```
+
+    - 如果Docker启用WSL 2做引擎，请执行以下命令创建容器：
+
+      ```bash
+      docker run --name mogdb --privileged=true -d -e GS_PASSWORD=Secretpassword@123 -v C:\mogdb:/var/lib/mogdb -p 15432:5432  swr.cn-north-4.myhuaweicloud.com/mogdb/mogdb:2.1.1
+      ```
+
+    > 注意：
+    >
+    > - MogDB的默认监听启动在容器内的5432端口上，如果想要从容器外部访问数据库，则需要在`docker run`的时候指定`-p`参数。比如以上命令将允许使用15432端口访问容器数据库。
+    >- 容器一旦被删除，容器内的所有数据和配置也均会丢失，而从镜像重新运行一个容器的话，则所有数据又都是呈现在初始化状态，因此对于数据库容器来说，为了防止因为容器的消亡或者损坏导致的数据丢失，需要进行持久化存储数据的操作。通过在`docker run`的时候指定`-v`参数来实现。比如以上命令将会指定将MogDB的所有数据文件存储在宿主机的`/mogdb`下。如果使用podman，会有目标路径检查，需要预先创建宿主机目标路径（步骤4）。
+
+5. 进入容器终端：
+
+    ```bash
+    docker exec -it mogdb bash
+    ```
+
+    至此，MogDB容器版安装完成。
+
+<br/>
+
+### 使用MogDB
+
+安装完成并进入容器后，通过`su - omm`切换为omm用户，即可通过gsql进行数据库访问以正常体验MogDB各项功能：
+
+```bash
+root@384ac97543bd:/# su - omm
+omm@384ac97543bd:~$ gsql -d postgres
+gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+Non-SSL connection (SSL connection is recommended when requiring high-security)
+Type "help" for help.
+
+postgres=#
+```
+
+<br/>
+
+### 环境变量
+
+为了更灵活地使用MogDB镜像，可以设置额外的参数。未来我们会扩充更多的可控制参数，当前版本支持以下变量的设定。
+
+**GS_PASSWORD**
+
+使用MogDB镜像的时候，必须设置该参数。该参数值不能为空或者不定义。该参数设置了MogDB数据库的超级用户omm以及测试用户mogdb的密码。MogDB安装时默认会创建omm超级用户，该用户名暂时无法修改。测试用户mogdb是在entrypoint.sh中自定义创建的用户。
+
+MogDB镜像配置了本地信任机制，因此在容器内连接数据库无需密码，但是如果要从容器外部（其它主机或者其它容器）连接则必须要输入密码。
+
+MogDB的密码有复杂度要求，密码长度8个字符以上，必须同时包含大写字母、小写字母、数字、以及特殊符号（特殊符号仅包含( \# ? ! @ $ % ^ & * \- )，并且 ! $ & 需要用转义符"\\"进行转义。
+
+**GS_NODENAME**
+
+指定数据库节点名称，默认为mogdb。
+
+**GS_USERNAME**
+
+指定数据库连接用户名，默认为mogdb。
+
+**GS_PORT**
+
+指定数据库端口，默认为5432。
+
+<br/>
+
+## Kubernetes部署
+
+MogDB 2.1版本以后支持Kubernetes部署。
+
+- x86
+  
+  ```
+  $ kubectl apply -f https://gitee.com/enmotech/enmotech-docker-mogdb/raw/master/2.1.1/k8s_amd.yaml
+  pod/mogdb created
+  ```
+
+- arm
+
+  ```
+  $ kubectl apply -f https://gitee.com/enmotech/enmotech-docker-mogdb/raw/master/2.1.1/k8s_arm.yaml
+  pod/mogdb created
+  ```
+
+- k8s连接pod
+
+  进入容器内通过gsql命令登录MogDB。
+
+  ```
+  $ kubectl exec -it mogdb -- bash
+  root@mogdb:/# su - omm
+  omm@mogdb:~$ gsql -d postgres
+  gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+  Non-SSL connection (SSL connection is recommended when requiring high-security)
+  Type "help" for help.
+  
+  MogDB=#
+  ```
+
+<br/>
+
+## Mogila样本数据集
+
+MogDB容器版内置了一个样本数据库mogila，该数据库是一个关于DVD出租店信息的数据库，包含有关电影（如标题、类别、女演员）、出租店（如地址、工作人员、客户）和出租的信息，其中一位顾客通过店员从一家商店租了一部影片。安装完MogDB容器版之后，您可以使用mogila数据库进行各种功能测试。
+
+安装完成并进入容器后，通过`su - omm`切换为omm用户，执行`gsql -d mogila`即可访问mogila数据库。
+
+```sql
+root@07456ed8f523:/# su - omm
+omm@07456ed8f523:~$ gsql -d mogila
+gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+Non-SSL connection (SSL connection is recommended when requiring high-security)
+Type "help" for help.
+
+MogDB=#\dt
+                             List of relations
+ Schema |     Name      | Type  | Owner |             Storage
+--------+---------------+-------+-------+----------------------------------
+ public | actor         | table | mogdb | {orientation=row,compression=no}
+ public | address       | table | mogdb | {orientation=row,compression=no}
+ public | category      | table | mogdb | {orientation=row,compression=no}
+ public | city          | table | mogdb | {orientation=row,compression=no}
+ public | country       | table | mogdb | {orientation=row,compression=no}
+ public | customer      | table | mogdb | {orientation=row,compression=no}
+ public | film          | table | mogdb | {orientation=row,compression=no}
+ public | film_actor    | table | mogdb | {orientation=row,compression=no}
+ public | film_category | table | mogdb | {orientation=row,compression=no}
+ public | inventory     | table | mogdb | {orientation=row,compression=no}
+ public | language      | table | mogdb | {orientation=row,compression=no}
+ public | payment       | table | mogdb | {orientation=row,compression=no}
+ public | rental        | table | mogdb | {orientation=row,compression=no}
+ public | staff         | table | mogdb | {orientation=row,compression=no}
+ public | store         | table | mogdb | {orientation=row,compression=no}
+(15 rows)
+
+MogDB=#
+```
+
+有关mogila样本数据集的详细介绍及查询示例，请参考[使用样本数据库集Mogila](mogila)。
+
+<br/>
+
+## 后续步骤
+
+MogDB容器版不支持MogHA工具、OM工具，当前仅用于测试使用，目前最多支持一主八备。MogDB企业版包含MogHA组件。容器版与企业版基础功能完全一致，在生产环境中建议使用MogDB企业版。
diff --git a/product/zh/docs-mogdb/v3.0/quick-start/installation-on-a-single-node.md b/product/zh/docs-mogdb/v3.0/quick-start/installation-on-a-single-node.md
new file mode 100644
index 0000000000000000000000000000000000000000..dabf90f68b29fe02a33fad8d62753c8f1797d571
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/quick-start/installation-on-a-single-node.md
@@ -0,0 +1,130 @@
+---
+title: 单实例安装
+summary: 单实例安装
+author: Zhang Cuiping
+date: 2021-04-2
+---
+
+# 单实例安装
+
+本文介绍MogDB极简版安装流程，极简版安装主要针对高校和个人测试环境，相对企业安装流程更简单快捷。该软件包中不含OM工具，采用脚本就可以实现一键式安装部署。
+
+<br/>
+
+## 准备软硬件安装环境
+
+**软件环境：** 访问[MogDB下载页面](https://www.mogdb.io/downloads/mogdb)下载对应平台的安装包。解压标准安装包后得到的`MogDB-x.x.x-openEuler-64bit.tar.bz2`即为极简安装包。
+
+**硬件环境：** 个人开发者最低配置2核4G，推荐配置4核8G。
+
+> 说明：
+>
+> 极简版为了适应小内存机器，在部署时将部分重要内存参数设置较低，如：“shared_buffers = 32MB”、“cstore_buffers = 512MB”。另外，极简版安装的数据库字符集将原先默认的SQL_ACSII字符集改为en_US.UTF-8，同时初始用户密码不做强制修改，即`modify_initial_password = false`。
+
+<br/>
+
+## 运行环境配置
+
+1. 关闭防火墙，selinux
+
+   ```
+   systemctl disable firewalld.service
+   systemctl stop firewalld.service
+   setenforce=0
+   sed -i '/^SELINUX=/c'SELINUX=disabled /etc/selinux/config
+   ```
+
+2. 安装依赖包
+
+   ```
+   yum install libaio-devel flex bison ncurses-devel glibc-devel patch redhat-lsb-core readline-devel -y
+   ```
+
+3. 设置时区
+
+   ```
+   rm -fr /etc/localtime
+   ln -s /usr/share/zoneinfo/Asia/Shanghai /etc/localtime
+   ll /etc/localtime
+   ```
+
+4. openEuler操作系统需要关闭RemoveIPC，CentOS操作系统默认为关闭，可以跳过该步骤。
+
+   ```
+   # 修改/etc/systemd/logind.conf文件中的“RemoveIPC”值为“no”。
+   vim  /etc/systemd/logind.conf
+   RemoveIPC=no
+   
+   # 修改/usr/lib/systemd/system/systemd-logind.service文件中的“RemoveIPC”值为“no”。
+   vim /usr/lib/systemd/system/systemd-logind.service
+   RemoveIPC=no
+   
+   # 重新加载配置参数。
+   systemctl daemon-reload
+   systemctl restart systemd-logind
+   
+   # 检查修改是否生效。
+   loginctl show-session | grep RemoveIPC
+   systemctl show systemd-logind | grep RemoveIPC
+   ```
+
+<br/>
+
+## 安装步骤
+
+1. 创建相关目录、用户、组，并授权。
+
+   ```
+   groupadd dbgrp -g 2000
+   useradd omm -g 2000 -u 2000
+   mkdir -p /opt/software/mogdb
+   chown -R omm:dbgrp /opt/software/mogdb
+   ```
+   
+2. 解压极简版安装包到安装目录。
+
+    ```
+    su - omm
+    cd /opt/software/mogdb/
+    tar -jxf MogDB-x.x.x-openEuler-64bit.tar.bz2 -C /opt/software/mogdb/
+    ```
+
+3. 进入解压后目录下的simpleInstall。
+
+    ```bash
+    cd /opt/software/mogdb/simpleInstall/
+    ```
+
+4. 执行install.sh脚本安装MogDB。
+
+    ```bash
+    sh install.sh  -w xxxx
+    ```
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+    >
+    > - -w: 初始化数据库密码（gs_initdb指定），安全需要必须设置。
+    > - -p: 指定的MogDB端口号，如不指定，默认为5432。
+    > - -h|-help 打印使用说明。
+    > - 安装后，数据库的名称为sgnode。
+    > - 安装后，数据库目录安装路径`/opt/software/mogdb/data/single_node`，其中`/opt/software/mogdb`为解压包路径，`data/single_node`为新创建的数据库节点目录。
+
+<br/>
+
+## 检查及使用数据库
+
+```
+## 配置PATH
+echo "PATH=/opt/software/mogdb/bin:\$PATH" >> /home/omm/.bash_profile
+source ~/.bash_profile
+-bash: ulimit: open files: cannot modify limit: Operation not permitted
+（默认设置fd可用大小超过系统设置，可以忽略该设置）
+
+## 登录数据库
+gsql -d postgres -p 5432 -r
+gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+Non-SSL connection (SSL connection is recommended when requiring high-security)
+Type "help" for help.
+
+MogDB=#
+```
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-cli-to-access-mogdb/gsql.md b/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-cli-to-access-mogdb/gsql.md
new file mode 100644
index 0000000000000000000000000000000000000000..15cc3397fbcd13678860a055a7c6708b0240de31
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-cli-to-access-mogdb/gsql.md
@@ -0,0 +1,216 @@
+---
+title: gsql
+summary: gsql
+author: Guo Huan
+date: 2021-12-1
+---
+
+# gsql
+
+gsql是MogDB提供的在命令行下运行的数据库连接工具。此工具除了具备操作数据库的基本功能，还提供了若干高级特性，便于用户使用。
+
+<br/>
+
+## 确认连接信息
+
+客户端工具通过数据库主节点连接数据库。因此连接前，需获取数据库主节点所在服务器的IP地址及数据库主节点的端口号信息。
+
+1. 以操作系统用户omm登录数据库主节点。
+
+2. 使用"gs_om -t status --detail"命令查询MogDB各实例情况。
+
+   ```bash
+   gs_om -t status --detail
+
+   [  Datanode State   ]
+
+   node                 node_ip         instance                state
+   ---------------------------------------------------------------------------------
+   1  mogdb-kernel-0005 172.16.0.176    6001 /mogdb/data/db1 P Primary Normal
+   ```
+
+   如上部署了数据库主节点实例的服务器IP地址为172.16.0.176。数据库主节点数据路径为"/mogdb/data/db1"。
+
+3. 确认数据库主节点的端口号。
+
+   在步骤2查到的数据库主节点数据路径下的postgresql.conf文件中查看端口号信息。示例如下:
+
+   ```bash
+   cat /mogdb/data/db1/postgresql.conf | grep port
+   
+   port = 26000    # (change requires restart)
+   #comm_sctp_port = 1024   # Assigned by installation (change requires restart)
+   #comm_control_port = 10001  # Assigned by installation (change requires restart)
+         # supported by the operating system:
+         # e.g. 'localhost=10.145.130.2 localport=12211 remotehost=10.145.130.3 remoteport=12212, localhost=10.145.133.2 localport=12213 remotehost=10.145.133.3 remoteport=12214'
+         # e.g. 'localhost=10.145.130.2 localport=12311 remotehost=10.145.130.4 remoteport=12312, localhost=10.145.133.2 localport=12313 remotehost=10.145.133.4 remoteport=12314'
+         #   %r = remote host and port
+   alarm_report_interval = 10
+   support_extended_features=true
+   ```
+
+   第一行中的26000为数据库主节点的端口号。
+
+<br/>
+
+## 安装gsql客户端
+
+在客户端机器上，上传客户端工具包并配置gsql的执行环境变量。
+
+1. 以任意用户登录客户端机器。
+
+2. 创建"/opt/mogdb/tools"目录。
+
+   ```bash
+   mkdir /opt/mogdb/tools
+   ```
+
+3. 获取软件安装包中的"MogDB-x.x.x-openEuler-64bit-tools.tar.gz"上传到"/opt/mogdb/tools"路径下。
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+   >
+   > - 软件包相对位置为安装时所放位置，根据实际情况填写。
+   > - 不同的操作系统，工具包文件名称会有差异。请根据实际的操作系统类型选择对应的工具包。
+
+4. 解压文件。
+
+   ```bash
+   cd /opt/mogdb/tools
+   tar -zxvf MogDB-x.x.x-openEuler-64bit-tools.tar.gz
+   ```
+
+5. 设置环境变量。
+
+   打开"~/.bashrc"文件。
+
+   ```bash
+   vi ~/.bashrc
+   ```
+
+   在其中输入如下内容后，使用":wq!"命令保存并退出。
+
+   ```bash
+   export PATH=/opt/mogdb/tools/bin:$PATH
+   export LD_LIBRARY_PATH=/opt/mogdb/tools/lib:$LD_LIBRARY_PATH
+   ```
+
+6. 使环境变量配置生效。
+
+   ```bash
+   source ~/.bashrc
+   ```
+
+<br/>
+
+## 使用gsql连接数据库
+
+<br/>
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 缺省情况下，客户端连接数据库后处于空闲状态时会根据参数session_timeout的默认值自动断开连接。如果要关闭超时设置，设置参数session_timeout为0即可。
+
+<br/>
+
+### 本地连接数据库
+
+1. 以操作系统用户omm登录数据库服务器。
+
+2. 连接数据库。
+
+   数据库安装完成后，默认生成名称为postgres的数据库。第一次连接数据库时可以连接到此数据库。
+
+   执行如下命令连接数据库。
+
+   ```bash
+   gsql -d postgres -p 26000
+   ```
+
+   其中postgres为需要连接的数据库名称，26000为数据库主节点的端口号。请根据实际情况替换。
+
+   连接成功后，系统显示类似如下信息:
+
+   ```sql
+   gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+   Non-SSL connection (SSL connection is recommended when requiring high-security)
+   Type "help" for help.
+
+   postgres=#
+   ```
+
+   omm用户是管理员用户，因此系统显示"postgres=#"。若使用普通用户身份登录和连接数据库，系统显示"postgres=>"。
+
+   "Non-SSL connection"表示未使用SSL方式连接数据库。如果需要高安全性时，请使用SSL连接。
+
+3. 退出数据库。
+
+   ```sql
+   postgres=# \q
+   ```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 使用omm用户在本地连接数据库，无需输入密码，这是由于在pg_hba.conf文件中默认设置了本机允许trust方式连接。
+> - 更多关于客户端认证方式的信息，请参见[客户端接入认证](1-client-access-authentication)章节。
+
+<br/>
+
+## 远程连接数据库
+
+<br/>
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 由于安全性限制，数据库初始用户omm无法进行远程连接。
+
+<br/>
+
+### 通过gs_guc配置白名单（更新pg_hba.conf文件）
+
+1. 以操作系统用户omm登录数据库主节点。
+
+2. 配置客户端认证方式，允许客户端以"jack"用户连接到本机，远程连接禁止使用"omm"用户（即数据库初始化用户）。
+
+   例如，下面示例中配置允许IP地址为172.16.0.245的客户端访问本机。
+
+   ```bash
+   gs_guc set -N all -I all -h "host all jack 172.16.0.245/24 sha256"
+   ```
+
+   **注意：**
+
+   - 使用"jack"用户前，需先本地连接数据库，并在数据库中使用如下语句建立"jack"用户:
+
+     ```sql
+     postgres=# CREATE USER jack PASSWORD 'Test@123';
+     ```
+
+   - -N all表示MogDB的所有主机。
+
+   - -I all表示主机的所有实例。
+
+   - -h表示指定需要在"pg_hba.conf"增加的语句。
+
+   - all表示允许客户端连接到任意的数据库。
+
+   - jack表示连接数据库的用户。
+
+   - 172.16.0.245/24表示只允许IP地址为172.16.0.245的主机连接。此处的IP地址不能为MogDB内的IP，在使用过程中，请根据用户的网络进行配置修改。24表示子网掩码为1的位数，即255.255.255.0。
+
+   - sha256表示连接时jack用户的密码使用sha256算法加密。
+
+   这条命令在数据库主节点实例对应的"pg_hba.conf"文件中添加了一条规则，用于对连接数据库主节点的客户端进行鉴定。
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+   >
+   > 更多关于客户端认证方式的信息，请参见[客户端接入认证](1-client-access-authentication)章节。
+
+3. 连接数据库。
+
+   数据库安装完成后，默认生成名称为postgres的数据库。第一次连接数据库时可以连接到此数据库。
+
+   ```bash
+   gsql -d postgres -h 172.16.0.176 -U jack -p 26000 -W Test@123
+   ```
+
+   postgres为需要连接的数据库名称，172.16.0.176为数据库主节点所在的服务器IP地址，jack为连接数据库的用户，26000为数据库主节点的端口号，Test@123为连接数据库用户jack的密码。
diff --git a/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-cli-to-access-mogdb/pgcli.md b/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-cli-to-access-mogdb/pgcli.md
new file mode 100644
index 0000000000000000000000000000000000000000..fe546424d19e6c9b3fca99b8a2e606ef35829103
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-cli-to-access-mogdb/pgcli.md
@@ -0,0 +1,85 @@
+---
+title: pgcli
+summary: pgcli
+author: Guo Huan
+date: 2022-02-16
+---
+
+# pgcli
+
+pgcli是一个具有自动补全以及高亮显示语法功能的Postgres命令行工具，同样适用于连接MogDB。
+
+pgcli Github页面：[https://github.com/dbcli/pgcli](https://github.com/dbcli/pgcli)
+
+<br/>
+
+## 安装pgcli
+
+```
+sudo pip3 install pgcli
+```
+
+适用于不同操作系统的详细安装步骤请参考pgcli官网页面：[http://pgcli.com](http://pgcli.com/)
+
+安装完成后可以使用help命令查看帮助信息。
+
+```
+[root@mogdb-kernel-0004 ~]# pgcli --help
+Usage: pgcli [OPTIONS] [DBNAME] [USERNAME]
+
+Options:
+  -h, --host TEXT            Host address of the postgres database.
+  -p, --port INTEGER         Port number at which the postgres instance is
+                             listening.
+  -U, --username TEXT        Username to connect to the postgres database.
+  -u, --user TEXT            Username to connect to the postgres database.
+  -W, --password             Force password prompt.
+  -w, --no-password          Never prompt for password.
+  --single-connection        Do not use a separate connection for completions.
+  -v, --version              Version of pgcli.
+  -d, --dbname TEXT          database name to connect to.
+  --pgclirc FILE             Location of pgclirc file.
+  -D, --dsn TEXT             Use DSN configured into the [alias_dsn] section
+                             of pgclirc file.
+  --list-dsn                 list of DSN configured into the [alias_dsn]
+                             section of pgclirc file.
+  --row-limit INTEGER        Set threshold for row limit prompt. Use 0 to
+                             disable prompt.
+  --less-chatty              Skip intro on startup and goodbye on exit.
+  --prompt TEXT              Prompt format (Default: "\u@\h:\d> ").
+  --prompt-dsn TEXT          Prompt format for connections using DSN aliases
+                             (Default: "\u@\h:\d> ").
+  -l, --list                 list available databases, then exit.
+  --auto-vertical-output     Automatically switch to vertical output mode if
+                             the result is wider than the terminal width.
+  --warn [all|moderate|off]  Warn before running a destructive query.
+  --help                     Show this message and exit.
+```
+
+<br/>
+
+## 连接MogDB示例
+
+通过`su - omm`命令切换到omm用户，然后执行`pgcli -d postgres -p 26000`即可连接MogDB数据库。
+
+```
+[root@mogdb-kernel-0004 ~]# su - omm
+Last login: Wed Feb 16 15:31:37 CST 2022 on pts/1
+[omm@mogdb-kernel-0004 ~]$ pgcli -d postgres -p 26000
+Server: PostgreSQL 9.2.4
+Version: 3.3.1
+Home: http://pgcli.com
+postgres> \l
++-----------+---------+----------+-------------+-------------+-------------------+
+| Name      | Owner   | Encoding | Collate     | Ctype       | Access privileges |
+|-----------+---------+----------+-------------+-------------+-------------------|
+| postgres  | omm     | UTF8     | en_US.UTF-8 | en_US.UTF-8 | <null>            |
+| template0 | omm     | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =c/omm            |
+|           |         |          |             |             | omm=CTc/omm       |
+| template1 | omm     | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =c/omm            |
+|           |         |          |             |             | omm=CTc/omm       |
++-----------+---------+----------+-------------+-------------+-------------------+
+SELECT 3
+Time: 0.020s
+postgres>
+```
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-gui-tools-to-access-mogdb/datastudio.md b/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-gui-tools-to-access-mogdb/datastudio.md
new file mode 100644
index 0000000000000000000000000000000000000000..aa4c979aa638835ae2fd69d69e7dbd7dd895c0d3
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-gui-tools-to-access-mogdb/datastudio.md
@@ -0,0 +1,112 @@
+---
+title: 使用Data Studio访问MogDB
+summary: 使用Data Studio访问MogDB
+author: Guo Huan
+date: 2022-03-15
+---
+
+# 使用Data Studio访问MogDB
+
+本文档介绍如何通过图形化工具Data Studio访问MogDB数据库。
+
+<br/>
+
+## 工具介绍
+
+Data Studio是一个集成开发环境（IDE），帮助数据库开发人员便捷地构建应用程序，以图形化界面形式提供数据库关键特性。数据库开发人员仅需掌握少量的编程知识，即可使用该工具进行数据库对象操作。
+Data Studio提供丰富多样的特性，例如：
+
+- 创建和管理数据库对象
+- 执行SQL语句/脚本
+- 编辑和执行PL/SQL语句
+- 图形化查看执行计划和开销
+- 导出表数据等
+
+创建和管理数据库对象，包括：
+
+- 数据库
+- 模式
+- 函数
+- 过程
+- 表
+- 序列
+- 索引
+- 视图
+- 表空间
+- 同义词
+
+Data Studio还提供SQL助手用于在SQL终端和PL/SQLViewer中执行各种查询/过程/函数。
+
+<br/>
+
+## 系统要求
+
+本节介绍使用Data Studio的最低系统要求。
+
+**硬件要求**
+
+表1 Data Studio硬件要求
+
+| **硬件要求** | **配置**                                                     |
+| ------------ | ------------------------------------------------------------ |
+| CPU          | x86 64位                                                     |
+| 可用内存     | 至少1GB内存                                                  |
+| 可用硬盘     | Data Studio安装目录需要至少1GB空间，用户HOME目录需要至少100MB空间 |
+| 网络         | 千兆以太网                                                   |
+
+**操作系统要求**
+
+运行在通用x86服务器上的Microsoft Windows系统，版本包括Windows 7 (64 位)、Windows 10 (64 位)、Windows 2012 (64 位)、Windows 2016 (64 位)。
+
+**软件要求**
+
+Java 1.8.0_181或更高版本。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> * 请参阅[https://java.com/en/download/help/path.xml](https://java.com/en/download/help/path.xml)以设置Java Home路径。
+> * 保证最佳体验的情况下，推荐的最小屏幕分辨率是1080 x 768。低于此分辨率，界面会异常。
+
+<br/>
+
+## 下载安装
+
+Data Studio的下载地址如下：<https://opengauss.org/zh/download.html>
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/datastudio-1.png)
+
+下载完成后解压安装包，双击**Data Studio.exe**即可运行软件。
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/use-gui-tools-to-access-mogdb-2.png)
+
+<br/>
+
+## 配置连接串
+
+首次打开软件会弹出“**新建/选择数据库连接**”窗口，如下图所示。
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/use-gui-tools-to-access-mogdb-3.png)
+
+您也可以点击“**文件 -> 新建连接**”打开此窗口。
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/use-gui-tools-to-access-mogdb-4.png)
+
+填写右侧“**通用**”标签页中的各项信息，点击“**确定**”，即可建立数据库连接。
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/use-gui-tools-to-access-mogdb-5.png)
+
+<br/>
+
+## 界面展示
+
+连接成功后的界面如下所示，右侧有语法和操作列表示例。
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/use-gui-tools-to-access-mogdb-6.png)
+
+<br/>
+
+## 后续步骤
+
+如需了解更多关于Data Studio的使用说明，请点击“**帮助 -> 用户手册**”，或访问以下页面在线浏览官方文档：[Data Studio用户手册](https://opengauss.obs.cn-south-1.myhuaweicloud.com/2.0.0/Data%20Studio%20%E7%94%A8%E6%88%B7%E6%89%8B%E5%86%8C.pdf)。
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/use-gui-tools-to-access-mogdb-7.png)
diff --git a/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-gui-tools-to-access-mogdb/dbeaver.md b/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-gui-tools-to-access-mogdb/dbeaver.md
new file mode 100644
index 0000000000000000000000000000000000000000..a3966b0daeb5093d1174d45b3341ca9c9fd0d535
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-gui-tools-to-access-mogdb/dbeaver.md
@@ -0,0 +1,64 @@
+---
+title: 使用DBeaver访问MogDB
+summary: 使用DBeaver访问MogDB
+author: Guo Huan
+date: 2022-03-15
+---
+
+# 使用DBeaver访问MogDB
+
+本文档介绍如何通过常用的图形化工具DBeaver访问MogDB数据库。
+
+<br/>
+
+## 工具介绍
+
+Dbeaver是一个跨平台的数据库开发者工具，包括SQL编程、数据库管理和分析。它支持任意适配JDBC驱动的数据库系统。同时该工具也支持一些非JDBC的数据源，如MongoDB、Cassandra、Redis、DynamoDB等。
+
+* 该工具提供了许多强大的特性，诸如元数据编辑器、SQL编辑器、富文本数据编辑器、ERD、数据导入/导出/迁移，SQL执行计划等；
+* 该工具基于eclipse平台开发；
+* 适配的数据库有MySQL/MariaDB、PostgreSQL、Greenplum、Oracle、DB2 LUW、Exasol、SQL Server、Sybase/SAP ASE、SQLite、Firebird、H2、HSQLDB、Derby、Teradata、Vertica、Netezza、Informix等。
+
+<br/>
+
+## 下载安装
+
+Dbeaver是一款开源软件，下载地址如下：[https://dbeaver.io/download/](https://dbeaver.io/download/)
+
+根据您的操作系统选择相应的安装包，下载完成后直接双击安装即可。
+
+<br/>
+
+## 配置连接串
+
+首次打开软件会弹出“**创建新连接**”窗口，如下图所示。
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/use-gui-tools-to-access-mogdb-8.png)
+
+您也可以点击“**数据库 -> 新建连接**”打开此窗口。
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/use-gui-tools-to-access-mogdb-9.png)
+
+选择“**Popular -> PostgreSQL**”类型，点击“**下一步**”，在弹出的页面中下载PostgreSQL驱动文件。
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/use-gui-tools-to-access-mogdb-10.png)
+
+下载完成后将弹出“**创建新连接**”窗口，在此窗口中填写数据库信息，然后点击“**完成**”即可建立数据库连接。
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/use-gui-tools-to-access-mogdb-11.png)
+
+<br/>
+
+## 界面展示
+
+连接成功后的界面如下所示。
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/use-gui-tools-to-access-mogdb-12.png)
+
+<br/>
+
+## 后续步骤
+
+如需了解更多关于DBeaver的使用说明，请点击“**帮助 -> 帮助内容**”，或点击以下页面在线浏览官方文档：[https://dbeaver.com/docs/wiki/](https://dbeaver.com/docs/wiki/)。
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/use-gui-tools-to-access-mogdb-13.png)
diff --git a/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-middleware-to-access-mogdb/weblogic-configures-mogdb(postgresql)-data-source-reference.md b/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-middleware-to-access-mogdb/weblogic-configures-mogdb(postgresql)-data-source-reference.md
new file mode 100644
index 0000000000000000000000000000000000000000..eea03a5a51abc2f89bb3d0ffbea3ad08221cdce1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-middleware-to-access-mogdb/weblogic-configures-mogdb(postgresql)-data-source-reference.md
@@ -0,0 +1,175 @@
+---
+title: WebLogic配置MogDB(PostgreSQL)数据源参考
+summary: WebLogic配置MogDB(PostgreSQL)数据源参考
+author: Guo Huan
+date: 2021-08-11
+---
+
+# WebLogic配置MogDB(PostgreSQL)数据源参考
+
+## 概述
+
+WebLogic配置MogDB数据源参考，同样适用WebLogic配置PostgreSQL数据源，详细内容见下文描述。
+
+<br/>
+
+## 配置前提
+
+### WebLogic JDK版本确认
+
+```bash
+$ /home/jdk1.7.0_80/bin/java -version
+java version "1.7.0_80"
+Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
+Java HotSpot(TM) 64-Bit Server VM (build 24.80-b11, mixed mode)
+```
+
+找到使用的JDK，并检查版本。
+
+JDBC驱动针对不同的JDK大版本有不同的jar包，明确JDK大版本才能保证下载对应的驱动。
+
+当前环境以1.7.0为测试环境。
+
+### 下载对应JDBC驱动包
+
+```
+当前版本42.2.23。
+
+这是驱动程序的当前版本。除非您有不寻常的需求（运行旧的应用程序或JVM），否则这就是您应该使用的驱动程序。它支持PostgreSQL 8.2或更高版本，并且需要Java 6或更高版本。它包含对SSL和javax.sql包的支持。
+
+如果您使用的是Java8或更高版本，那么应该使用JDBC4.2版本。
+如果您使用的是Java7，那么应该使用JDBC4.1版本。
+如果您使用的是Java6，那么应该使用JDBC4.0版本。
+```
+
+各JDK对应下载JDBC版本链接如下：
+
+| JDK版本 | JDBC驱动链接地址                                             |
+| ------- | ------------------------------------------------------------ |
+| 1.6     | <https://jdbc.postgresql.org/download/postgresql-42.2.23.jre6.jar> |
+| 1.7     | <https://jdbc.postgresql.org/download/postgresql-42.2.23.jre7.jar> |
+| 1.8     | <https://jdbc.postgresql.org/download/postgresql-42.2.23.jar>  |
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/weblogic-configures-mogdb(postgresql)-data-source-reference-1.png)
+
+使用 42.2.23 是最佳选择，支持PostgreSQL 8.2或更高版本，而且是当前最稳定版本。
+
+下载地址如下：[https://jdbc.postgresql.org/download.html](https://jdbc.postgresql.org/download.html)
+
+<br/>
+
+## 配置过程
+
+### 确认db相关信息
+
+| 数据库名 | 用户  | 密码   | 端口  | IP   |
+| -------- | ----- | ------ | ----- | ---- |
+| postgres | mogdb | 123456 | 25431 |      |
+
+### 确认端口联通
+
+在中间件主机telnet ip port ，确保能正常访问到db端口
+
+### Console配置数据源
+
+#### 添加驱动到CLASSPATH
+
+a. 备份启动文件
+
+```
+cd ${DOMAIN_HOME}/bin
+cp startWebLogic.sh startWebLogic.sh.bak
+```
+
+b. 上传驱动到WebLogic主机
+
+ 例如当前JDK版本为1.7，上传到指定路径
+
+/home/postgresql-42.2.23.jre7.jar
+
+c. 修改启动文件添加驱动包
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/weblogic-configures-mogdb(postgresql)-data-source-reference-2.png)
+
+CLASSPATH="${SAVE_CLASSPATH}"
+
+改为：
+
+CLASSPATH="${SAVE_CLASSPATH}:/home/postgresql-42.2.23.jre7.jar"
+
+d. 重启server生效
+
+#### 配置数据源
+
+a.   新建数据源
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/weblogic-configures-mogdb(postgresql)-data-source-reference-3.png)
+
+b.  填写JNDI及相关信息
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/weblogic-configures-mogdb(postgresql)-data-source-reference-4.png)
+
+c.   选择默认驱动
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/weblogic-configures-mogdb(postgresql)-data-source-reference-5.png)
+
+d.  选默认
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/weblogic-configures-mogdb(postgresql)-data-source-reference-6.png)
+
+e.   填写db信息
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/weblogic-configures-mogdb(postgresql)-data-source-reference-7.png)
+
+f.   测试连接
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/weblogic-configures-mogdb(postgresql)-data-source-reference-8.png)
+
+g.  确保测试成功
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/weblogic-configures-mogdb(postgresql)-data-source-reference-9.png)
+
+h.  根据需求选择server
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/weblogic-configures-mogdb(postgresql)-data-source-reference-10.png)
+
+i.   完成配置并激活更改生效
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/weblogic-configures-mogdb(postgresql)-data-source-reference-11.png)
+
+<br/>
+
+## 使用openGauss驱动连接MogDB
+
+openGauss JDBC驱动只提供JDK 1.8版本，JDK 1.8的应用使用openGauss驱动能够正常连接使用MogDB。
+
+如果是JDK 1.6、JDK 1.7的应用，那么只能使用PostgreSQL官方提供的JDBC驱动连接MogDB。
+
+openGauss驱动下载地址：
+
+[https://opengauss.org/zh/download.html](https://opengauss.org/zh/download.html)
+
+<br/>
+
+## 常见问题
+
+当驱动版本高于JDK版本时，启动server报错如下
+
+```
+<xxx 10, 2021 10:43:53 PM CST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'pg JDBC Data Source' due to error java.lang.UnsupportedClassVersionError: org/postgresql/Driver : Unsupported major.minor version 52.0.
+java.lang.UnsupportedClassVersionError: org/postgresql/Driver : Unsupported major.minor version 52.0
+        at java.lang.ClassLoader.defineClass1(Native Method)
+        at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
+        at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
+        at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
+        at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
+        Truncated. see log file for complete stacktrace
+Caused By: java.lang.UnsupportedClassVersionError: org/postgresql/Driver : Unsupported major.minor version 52.0
+        at java.lang.ClassLoader.defineClass1(Native Method)
+        at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
+        at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
+        at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
+        at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
+        Truncated. see log file for complete stacktrace
+>
+```
diff --git a/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-middleware-to-access-mogdb/websphere-configures-mogdb(postgresql)-data-source-reference.md b/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-middleware-to-access-mogdb/websphere-configures-mogdb(postgresql)-data-source-reference.md
new file mode 100644
index 0000000000000000000000000000000000000000..8943908e314650981d1b6a2c4c6bcda68293d57b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-middleware-to-access-mogdb/websphere-configures-mogdb(postgresql)-data-source-reference.md
@@ -0,0 +1,210 @@
+---
+title: WebSphere配置MogDB(PostgreSQL)数据源参考
+summary: WebSphere配置MogDB(PostgreSQL)数据源参考
+author: Guo Huan
+date: 2021-08-09
+---
+
+# WebSphere配置MogDB(PostgreSQL)数据源参考
+
+WebSphere配置MogDB数据源参考，同样适用WebSphere配置PostgreSQL数据源，详细内容见下文描述。
+
+<br/>
+
+## 配置前提
+
+### WebSphere JDK版本确认
+
+```bash
+C:\Windows\system32>D:\IBM1\WebSphere\AppServer\java\bin\java -version
+java version "1.6.0"
+Java(TM) SE Runtime Environment (build pwa6460_26sr8fp26ifix-20160708_01(SR8 FP26+IX90174))
+IBM J9 VM (build 2.6, JRE 1.6.0 Windows 8 amd64-64 Compressed References 20160406_298378 (JIT enabled, AOT enabled)
+J9VM - R26_Java626_SR8_20160406_0830_B298378
+JIT  - tr.r11_20160328_114192
+GC   - R26_Java626_SR8_20160406_0830_B298378_CMPRSS
+J9CL - 20160406_298378)
+JCL  - 20160507_01
+
+C:\Windows\system32>
+```
+
+找到使用的JDK，并检查版本。
+
+JDBC驱动针对不同的JDK大版本有不同的jar包，明确JDK大版本才能保证下载对应的驱动。
+
+### 下载对应JDBC驱动包
+
+```
+当前版本42.2.23。
+
+这是驱动程序的当前版本。除非您有不寻常的需求（运行旧的应用程序或JVM），否则这就是您应该使用的驱动程序。它支持PostgreSQL 8.2或更高版本，并且需要Java 6或更高版本。它包含对SSL和javax.sql包的支持。
+
+如果您使用的是Java8或更高版本，那么应该使用JDBC4.2版本。
+如果您使用的是Java7，那么应该使用JDBC4.1版本。
+如果您使用的是Java6，那么应该使用JDBC4.0版本。
+```
+
+各JDK对应下载JDBC版本链接如下：
+
+| JDK版本 | JDBC驱动链接地址                                             |
+| ------- | ------------------------------------------------------------ |
+| 1.6     | <https://jdbc.postgresql.org/download/postgresql-42.2.23.jre6.jar> |
+| 1.7     | <https://jdbc.postgresql.org/download/postgresql-42.2.23.jre7.jar> |
+| 1.8     | <https://jdbc.postgresql.org/download/postgresql-42.2.23.jar>  |
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/weblogic-configures-mogdb(postgresql)-data-source-reference-1.png)
+
+使用 42.2.23 是最佳选择，支持PostgreSQL 8.2或更高版本，而且是当前最稳定版本。
+
+下载地址如下：[https://jdbc.postgresql.org/download.html](https://jdbc.postgresql.org/download.html)
+
+<br/>
+
+## 配置过程
+
+### 确认db相关信息
+
+| 数据库名 | 用户     | 密码   | 端口 | IP   |
+| -------- | -------- | ------ | ---- | ---- |
+| postgres | postgres | 123456 | 5432 |      |
+
+### 确认端口联通
+
+telnet ip port 能正常访问到端口
+
+### Console配置
+
+#### JDBC提供程序
+
+a.   新建JDBC提供程序
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-1.png)
+
+b.  创建新的JDBC提供程序
+
+org.postgresql.ds.PGConnectionPoolDataSource
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-2.png)
+
+c.   指定驱动的路径
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-3.png)
+
+d.  下一步完成保存
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-4.png)
+
+#### 配置数据源
+
+a.   新建
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-5.png)
+
+b.  填写JNDI及相关信息
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-6.png)
+
+c.   选择现有的JDBC提供程序
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-7.png)
+
+d.  选默认
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-8.png)
+
+e.   下一步
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-9.png)
+
+f.   完成保存
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-10.png)
+
+#### 配置db认证
+
+a.   点击刚配置的pgtest数据源
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-11.png)
+
+b.  JAAS － J2C 认证数据
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-12.png)
+
+c.   新建
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-13.png)
+
+d.  指定用户密码，别名随意起名
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-14.png)
+
+e.   确定保存
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-15.png)
+
+f.   重新点击刚新建的数据源pgtest，配置“安全性设置”
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-16.png)
+
+g.  确定保存。
+
+#### 定制属性
+
+a.   点击刚配置的pgtest数据源
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-17.png)
+
+ b.  定制属性
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-18.png)
+
+c.   过滤
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-19.png)
+
+d.  过滤serverName
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-20.png)
+
+e.   点击serverName
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-21.png)
+
+f.   填写对应的db的IP地址
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-22.png)
+
+g.  确定保存
+
+h.  同理过滤输入portNumber/ databaseName
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-23.png)
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-24.png)
+
+#### 重启server测试连接
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-25.png)
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-26.png)
+
+<br/>
+
+## 使用openGauss驱动连接MogDB
+
+openGauss JDBC驱动只提供JDK 1.8版本，JDK 1.8的应用使用openGauss驱动能够正常连接使用MogDB。
+
+如果是JDK 1.6、JDK 1.7的应用，那么只能使用PostgreSQL官方提供的JDBC驱动连接MogDB。
+
+openGauss驱动下载地址：
+
+[https://opengauss.org/zh/download.html](https://opengauss.org/zh/download.html)
+
+<br/>
+
+## 常见问题
+
+驱动版本与JDK版本不匹配
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/websphere-configures-mogdb(postgresql)-data-source-reference-27.png)
diff --git a/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/c-cpp.md b/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/c-cpp.md
new file mode 100644
index 0000000000000000000000000000000000000000..2f2963daec699666928d664e7cc93b021a9ec650
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/c-cpp.md
@@ -0,0 +1,14 @@
+---
+title: 使用C/C++访问MogDB
+summary: 使用C/C++访问MogDB
+author: Guo Huan
+date: 2022-03-25
+---
+
+
+
+# 使用C/C++访问MogDB
+
+libpq是PostgreSQL的C应用程序接口，是一套允许客户程序向PostgreSQL服务进程发送查询并且获得查询结果的库函数。libpq同时也是其他几个PostgreSQL应用接口下面的引擎， 包括C++、Perl、Python、Tcl和ECPG。
+
+关于使用C/C++访问MogDB数据库的详细说明请参考《开发者指南》中[基于libpq开发](1-development-based-on-libpq)章节的内容。
diff --git a/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/go.md b/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/go.md
new file mode 100644
index 0000000000000000000000000000000000000000..4dcae755e62b403bcd285bb2c8aae4812b478c2b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/go.md
@@ -0,0 +1,16 @@
+---
+title: 使用Go访问MogDB
+summary: 使用Go访问MogDB
+author: Guo Huan
+date: 2022-03-31
+---
+
+
+
+# 使用Go访问MogDB
+
+openGauss基于[lib/pq](https://github.com/lib/pq)提供了用于Go数据库/sql包的Go openGauss驱动程序，该驱动程序同样适用于Go语言连接MogDB。
+
+您可以点击以下链接查看此驱动程序的源码及操作指导：
+
+[源码地址](https://gitee.com/opengauss/openGauss-connector-go-pq)、[操作指导](https://gitee.com/opengauss/openGauss-connector-go-pq/blob/master/README.cn.md)
diff --git a/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/java.md b/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/java.md
new file mode 100644
index 0000000000000000000000000000000000000000..88bb1260efaee4c561f36065b6a1161bfe8e9517
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/java.md
@@ -0,0 +1,14 @@
+---
+title: 使用Java访问MogDB
+summary: 使用Java访问MogDB
+author: Guo Huan
+date: 2022-03-25
+---
+
+
+
+# 使用Java访问MogDB
+
+JDBC（Java Database Connectivity，Java数据库连接）是一种用于执行SQL语句的Java API，可以为多种关系数据库提供统一访问接口，应用程序可基于它操作数据。MogDB数据库提供了对JDBC 4.0特性的支持。
+
+关于使用Java访问MogDB数据库的详细说明请参考《开发者指南》中[基于JDBC开发](1-development-based-on-jdbc-overview)章节的内容。
diff --git a/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/nodejs.md b/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/nodejs.md
new file mode 100644
index 0000000000000000000000000000000000000000..b4a25af71244185ec2fb4bad5fcc4db36f62fa56
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/nodejs.md
@@ -0,0 +1,16 @@
+---
+title: 使用NodeJS访问MogDB
+summary: 使用NodeJS访问MogDB
+author: Guo Huan
+date: 2022-03-31
+---
+
+
+
+# 使用NodeJS访问MogDB
+
+openGauss基于[node-postgres](https://github.com/brianc/node-postgres)提供了用于NodeJS的驱动程序，该驱动程序同样适用于NodeJS连接MogDB。
+
+您可以点击以下链接查看此驱动程序的源码及操作指导：
+
+[源码地址](https://gitee.com/opengauss/openGauss-connector-nodejs)、[操作指导](https://gitee.com/opengauss/openGauss-connector-nodejs/blob/master/README.md)
diff --git a/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/python.md b/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/python.md
new file mode 100644
index 0000000000000000000000000000000000000000..0f3f1158fb4c74a68b74df1d48dfaf0bc3887e31
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/python.md
@@ -0,0 +1,14 @@
+---
+title: 使用Python访问MogDB
+summary: 使用Python访问MogDB
+author: Guo Huan
+date: 2022-03-25
+---
+
+
+
+# 使用Python访问MogDB
+
+Psycopg是一种用于执行SQL语句的PythonAPI，可以为PostgreSQL、GaussDB数据库提供统一访问接口，应用程序可基于它进行数据操作。Psycopg2是对libpq的封装，主要使用C语言实现，既高效又安全。它具有客户端游标和服务器端游标、异步通信和通知、支持“COPY TO/COPY FROM”功能。支持多种类型Python开箱即用，适配PostgreSQL数据类型；通过灵活的对象适配系统，可以扩展和定制适配。Psycopg2兼容Unicode和Python 3。
+
+MogDB数据库提供了对Psycopg2特性的支持，并且支持psycopg2通过SSL模式链接。关于使用Python访问MogDB数据库的详细说明请参考《开发者指南》中[基于Psycopg开发](1-psycopg-based-development)章节的内容。
diff --git a/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/rust.md b/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/rust.md
new file mode 100644
index 0000000000000000000000000000000000000000..a7ca307d4db2adafb73f49c42d9b628793f4d4b3
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/quick-start/mogdb-access/use-programming-language-to-access-mogdb/rust.md
@@ -0,0 +1,16 @@
+---
+title: 使用Rust访问MogDB
+summary: 使用Rust访问MogDB
+author: Guo Huan
+date: 2022-03-31
+---
+
+
+
+# 使用Rust访问MogDB
+
+openGauss基于[rust-postgres](https://github.com/sfackler/rust-postgres)提供了用于Rust的驱动程序，该驱动程序同样适用于Rust语言连接MogDB。
+
+您可以点击以下链接查看此驱动程序的源码及操作指导：
+
+[源码地址](https://gitee.com/opengauss/openGauss-connector-rust)、[操作指导](https://gitee.com/opengauss/openGauss-connector-rust/blob/master/README.md)
diff --git a/product/zh/docs-mogdb/v3.0/quick-start/mogdb-playground.md b/product/zh/docs-mogdb/v3.0/quick-start/mogdb-playground.md
new file mode 100644
index 0000000000000000000000000000000000000000..1fe7f142188aad3e0717b519c9ef225dc1b23309
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/quick-start/mogdb-playground.md
@@ -0,0 +1,46 @@
+---
+title: MogDB实训环境
+summary: MogDB实训环境
+author: Guo Huan
+date: 2022-03-18
+---
+
+# MogDB实训环境
+
+MogDB实训环境是由[墨天轮](https://www.modb.pro/)提供的MogDB数据库线上学习与实训平台，同时提供Oracle/MySQL兼容包，以及Mogila样本数据集。您可以通过浏览器的命令行终端一键连接数据库，方便快速地体验MogDB的各项功能，无需自备环境进行安装。
+
+<br/>
+
+## 进入实训环境
+
+访问[MogDB在线实训环境](https://www.modb.pro/terminal)，进入后，左侧会显示相关操作文档，右侧会显示操作平台，此时还未连接上，需要点击【点击进入实训环境】，随后在弹出窗口中注册或登录墨天轮账号即可免费使用。
+
+![image.png](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/playground-1.png)
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/playground-6.png)
+
+## 开始学习
+
+连接成功后，开始正式运行，这时候就可以执行相关操作了。
+
+![image.png](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/playground-2.png)
+
+## 参考文档
+
+操作时，可以根据左侧的操作文档进行操作，同时左侧的操作文档可以进行折叠。
+
+![image.png](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/playground-3.png)
+
+## 关闭环境
+
+想要关闭数据库可以点击右下角的关闭按钮进行关闭，不过关闭后之前创建的数据库数据则被清空，再次连接则是一个新的环境，请谨慎操作。
+
+![image.png](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/playground-4.png)
+
+## 常见问题
+
+**如果中途退出页面怎么办？**
+
+用户如果直接关闭当前页面，事实上数据库资源还在运行中，只要在30分钟内再进入，之前创建的数据不会被删除（刷新当前页面也是一样的），并且中途退出当前页面，会有相关提示确定是否离开。
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/playground-5.png)
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/quick-start/mogila.md b/product/zh/docs-mogdb/v3.0/quick-start/mogila.md
new file mode 100644
index 0000000000000000000000000000000000000000..f8d379d9ba0db08221ea60f830d663ac9068af41
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/quick-start/mogila.md
@@ -0,0 +1,410 @@
+---
+title: 使用样本数据集Mogila
+summary: 使用样本数据集Mogila
+author: Guo Huan
+date: 2022-01-20
+---
+
+
+
+# 使用样本数据集Mogila
+
+MogDB提供了一个样本数据集Mogila，本数据集借鉴了适用于MySQL的[Sakila示例数据库](https://dev.mysql.com/doc/sakila/en/)。**Sakila**最初由MySQL AB文档团队的Mike Hillyer开发，其目的是提供一个可用于书籍、教程、文章、样本等示例的标准schema。
+
+Mogila数据集是一个关于DVD出租店信息的数据库，包含有关电影（如标题、类别、女演员）、出租店（如地址、工作人员、客户）和出租的信息。您可以使用Mogila数据库进行各种功能测试。
+
+Mogila适用于MogDB 2.1及更高版本。
+
+<br/>
+
+## 实体-关系模型图
+
+下图展示了Mogila数据库表和视图的概览。您可以查看不同表之间如何通过各个字段相互关联。例如，`film`表具有`title`和`description`列。它还通过列`language_id`和`original_language_id`与`language`表相关联。因此您可以联结这两个表来获取每部电影的语言，或者列出特定语言的所有电影。
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/quick-start/mogila-erm.png)
+
+<br/>
+
+## 在MogDB容器版中使用Mogila
+
+MogDB容器版本已经内置了Mogila样本数据库，无需额外安装。
+
+1. [安装MogDB容器版](https://docs.mogdb.io/zh/mogdb/v2.1/container-based-installation)。
+
+2. 使用样本数据库Mogila：
+
+   ```
+   docker exec -it mogdb bash
+   omm@eb7aef3f860f:~$ gsql -d mogila -p5432
+   gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+   Non-SSL connection (SSL connection is recommended when requiring high-security)
+   Type "help" for help.
+   
+   mogila=# \dt
+                             List of relations
+    Schema |     Name      | Type  | Owner |             Storage
+   --------+---------------+-------+-------+----------------------------------
+    public | actor         | table | mogdb | {orientation=row,compression=no}
+    public | address       | table | mogdb | {orientation=row,compression=no}
+    public | category      | table | mogdb | {orientation=row,compression=no}
+    public | city          | table | mogdb | {orientation=row,compression=no}
+    public | country       | table | mogdb | {orientation=row,compression=no}
+    public | customer      | table | mogdb | {orientation=row,compression=no}
+    public | film          | table | mogdb | {orientation=row,compression=no}
+    public | film_actor    | table | mogdb | {orientation=row,compression=no}
+    public | film_category | table | mogdb | {orientation=row,compression=no}
+    public | inventory     | table | mogdb | {orientation=row,compression=no}
+    public | language      | table | mogdb | {orientation=row,compression=no}
+    public | payment       | table | mogdb | {orientation=row,compression=no}
+    public | rental        | table | mogdb | {orientation=row,compression=no}
+    public | staff         | table | mogdb | {orientation=row,compression=no}
+    public | store         | table | mogdb | {orientation=row,compression=no}
+   (15 rows)
+   
+   mogila=#
+   ```
+
+<br/>
+
+## 在MogDB企业版中使用Mogila
+
+1. [安装MogDB企业版](https://docs.mogdb.io/zh/mogdb/v2.1/installation-on-a-single-node)。
+
+2. 创建样本数据库mogila及mogdb用户，然后登出：
+
+   ```
+   # 切换到omm用户
+   [root@test ~]# su - omm
+   # 登录postgres数据库，根据实际情况填写端口号
+   [omm@test ~]$ gsql -d postgres -p5432 -r
+   gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+   Non-SSL connection (SSL connection is recommended when requiring high-security)
+   Type "help" for help.
+   MogDB=#create database mogila DBCOMPATIBILITY='PG';
+   CREATE DATABASE
+   MogDB=#create user mogdb password 'Enmo@123';
+   CREATE ROLE
+   MogDB=#\q
+   [omm@test ~]$
+   ```
+
+3. [下载mogila](https://gitee.com/enmotech/mogila)，并上传至服务器中，进入mogila所在目录。
+
+4. 创建模式对象，然后手动插入数据：
+
+   - 4.1 创建所有模式对象（表等）：
+
+   ```
+   gsql -d mogila -p5432 -f mogila-schema.sql
+   ```
+
+   - 4.2 插入所有数据：
+
+   ```
+   gsql -d mogila -p5432 -f mogila-data.sql
+   ```
+
+   **或者通过1个脚本创建模式对象并插入数据，如果您已经完成步骤4.1和4.2，则无需执行步骤5。**
+
+5. 创建所有模式对象（表等）并插入所有数据：
+
+   ```
+   gsql -d mogila -p5432 -f mogila-insert-data.sql
+   ```
+
+6. 使用样本数据库Mogila：
+
+   ```
+   [omm@test ~]$ gsql -d mogila -p5432 -r
+   gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr  )
+   Non-SSL connection (SSL connection is recommended when requiring high-security)
+   Type "help" for help.
+   
+   mogila=# \dt
+                             List of relations
+    Schema |     Name      | Type  | Owner |             Storage
+   --------+---------------+-------+-------+----------------------------------
+    public | actor         | table | mogdb | {orientation=row,compression=no}
+    public | address       | table | mogdb | {orientation=row,compression=no}
+    public | category      | table | mogdb | {orientation=row,compression=no}
+    public | city          | table | mogdb | {orientation=row,compression=no}
+    public | country       | table | mogdb | {orientation=row,compression=no}
+    public | customer      | table | mogdb | {orientation=row,compression=no}
+    public | film          | table | mogdb | {orientation=row,compression=no}
+    public | film_actor    | table | mogdb | {orientation=row,compression=no}
+    public | film_category | table | mogdb | {orientation=row,compression=no}
+    public | inventory     | table | mogdb | {orientation=row,compression=no}
+    public | language      | table | mogdb | {orientation=row,compression=no}
+    public | payment       | table | mogdb | {orientation=row,compression=no}
+    public | rental        | table | mogdb | {orientation=row,compression=no}
+    public | staff         | table | mogdb | {orientation=row,compression=no}
+    public | store         | table | mogdb | {orientation=row,compression=no}
+   (15 rows)
+   
+   mogila=#
+   ```
+
+<br/>
+
+## 示例查询
+
+本节通过一些查询来展示如何使用样本数据库Mogila。所有查询结果仅展示前10项。
+
+- 按长度排序列出所有电影
+
+  ```sql
+  select
+      film_id,
+      title,
+      length
+  from
+      film
+  order by
+      length desc;
+  ```
+
+  ```sql
+  |film_id|title             |length|
+  |-------|------------------|------|
+  |426    |HOME PITY         |185   |
+  |690    |POND SEATTLE      |185   |
+  |609    |MUSCLE BRIGHT     |185   |
+  |991    |WORST BANGER      |185   |
+  |182    |CONTROL ANTHEM    |185   |
+  |141    |CHICAGO NORTH     |185   |
+  |349    |GANGS PRIDE       |185   |
+  |212    |DARN FORRESTER    |185   |
+  |817    |SOLDIERS EVOLUTION|185   |
+  |872    |SWEET BROTHERHOOD |185   |
+  ```
+
+- 列出每个电影类别中有多少部电影
+
+  ```sql
+  select
+      category.name,
+      count(category.name) category_count
+  from
+      category
+  left join film_category on
+      category.category_id = film_category.category_id
+  left join film on
+      film_category.film_id = film.film_id
+  group by
+      category.name
+  order by
+      category_count desc;
+  ```
+
+  ```sql
+  |name       |category_count|
+  |-----------|--------------|
+  |Sports     |74            |
+  |Foreign    |73            |
+  |Family     |69            |
+  |Documentary|68            |
+  |Animation  |66            |
+  |Action     |64            |
+  |New        |63            |
+  |Drama      |62            |
+  |Sci-Fi     |61            |
+  |Games      |61            |
+  ```
+
+- 显示按出演电影的数量排序的演员
+
+  ```sql
+  select
+      actor.first_name,
+      actor.last_name,
+      count(actor.first_name) featured_count
+  from
+      actor
+  left join film_actor on
+      actor.actor_id = film_actor.actor_id
+  group by
+      actor.first_name,
+      actor.last_name
+  order by
+      featured_count desc;
+  ```
+
+  ```sql
+  |first_name|last_name|featured_count|
+  |----------|---------|--------------|
+  |SUSAN     |DAVIS    |54            |
+  |GINA      |DEGENERES|42            |
+  |WALTER    |TORN     |41            |
+  |MARY      |KEITEL   |40            |
+  |MATTHEW   |CARREY   |39            |
+  |SANDRA    |KILMER   |37            |
+  |SCARLETT  |DAMON    |36            |
+  |VIVIEN    |BASINGER |35            |
+  |VAL       |BOLGER   |35            |
+  |GROUCHO   |DUNST    |35            |
+  ```
+
+- 获取所有活跃客户的列表，按其姓名排序
+
+  ```sql
+  select
+      first_name,
+      last_name
+  from
+      customer
+  where
+      active = 1
+  order by first_name asc;
+  ```
+
+  ```sql
+  |first_name|last_name|
+  |----------|---------|
+  |MARY      |SMITH    |
+  |PATRICIA  |JOHNSON  |
+  |LINDA     |WILLIAMS |
+  |BARBARA   |JONES    |
+  |ELIZABETH |BROWN    |
+  |JENNIFER  |DAVIS    |
+  |MARIA     |MILLER   |
+  |SUSAN     |WILSON   |
+  |MARGARET  |MOORE    |
+  |DOROTHY   |TAYLOR   |
+  ```
+
+- 查看租DVD数量最多的客户，以及租借次数
+
+  ```sql
+  select
+      customer.first_name,
+      customer.last_name,
+      count(customer.first_name) rentals_count
+  from
+      customer
+  left join rental on
+      customer.customer_id = rental.customer_id
+  group by
+      customer.first_name,
+      customer.last_name
+  order by rentals_count desc;
+  ```
+
+  ```sql
+  |first_name|last_name|rentals_count|
+  |----------|---------|-------------|
+  |ELEANOR   |HUNT     |46           |
+  |KARL      |SEAL     |45           |
+  |CLARA     |SHAW     |42           |
+  |MARCIA    |DEAN     |42           |
+  |TAMMY     |SANDERS  |41           |
+  |WESLEY    |BULL     |40           |
+  |SUE       |PETERS   |40           |
+  |MARION    |SNYDER   |39           |
+  |RHONDA    |KENNEDY  |39           |
+  |TIM       |CARY     |39           |
+  ```
+
+- 查看每个出租店的总收入
+
+  ```sql
+  select
+      store.store_id,
+      sum(payment.amount) as "total revenue"
+  from
+      store
+  left join inventory on
+      inventory.store_id = store.store_id
+  left join rental on
+      rental.inventory_id = inventory.inventory_id
+  left join payment on
+      payment.rental_id = rental.rental_id
+  where
+      payment.amount is not null
+  group by
+      store.store_id
+  order by
+      sum(payment.amount) desc;
+  ```
+
+  ```sql
+  |store_id|total revenue|
+  |--------|-------------|
+  |       2|     33726.77|
+  |       1|     33689.74|
+  ```
+
+- 按总收入列出前5个电影类型
+
+  ```sql
+  select
+      category.name,
+      film.title,
+      sum(payment.amount) as "gross revenue"
+  from
+      film
+  left join film_category on
+      film_category.film_id = film.film_id
+  left join category on
+      film_category.category_id = category.category_id
+  left join inventory on
+      inventory.film_id = film.film_id
+  left join rental on
+      rental.inventory_id = inventory.inventory_id
+  left join payment
+      on payment.rental_id = rental.rental_id
+  where
+      payment.amount is not null
+  group by
+      category.name,
+      film.title
+  order by
+      sum(payment.amount) desc
+  limit 5;
+  ```
+
+  ```sql
+  |   name     |       title       | gross revenue|
+  |------------|-------------------|--------------|
+  |Music       | TELEGRAPH VOYAGE  |        231.73|
+  |Documentary | WIFE TURN         |        223.69|
+  |Comedy      | ZORRO ARK         |        214.69|
+  |Sci-Fi      | GOODFELLAS SALUTE |        209.69|
+  |Sports      | SATURDAY LAMBS    |        204.72|
+  ```
+
+- `film.description` 的数据类型为 `text` ，支持全文搜索查询，搜索所有包含`documentary`和`robot`的描述
+
+  ```sql
+  select
+      film.title,
+      film.description
+  from
+      film
+  where
+      to_tsvector(film.description) @@ to_tsquery('documentary & robot');
+  ```
+
+  ```sql
+  |  title          |                                                    description                                                     |
+  |-----------------|--------------------------------------------------------------------------------------------------------------------|
+  |CASPER DRAGONFLY | A Intrepid Documentary of a Boat And a Crocodile who must Chase a Robot in The Sahara Desert                       |
+  |CHAINSAW UPTOWN  | A Beautiful Documentary of a Boy And a Robot who must Discover a Squirrel in Australia                             |
+  |CONTROL ANTHEM   | A Fateful Documentary of a Robot And a Student who must Battle a Cat in A Monastery                                |
+  |CROSSING DIVORCE | A Beautiful Documentary of a Dog And a Robot who must Redeem a Womanizer in Berlin                                 |
+  |KANE EXORCIST    | A Epic Documentary of a Composer And a Robot who must Overcome a Car in Berlin                                     |
+  |RUNNER MADIGAN   | A Thoughtful Documentary of a Crocodile And a Robot who must Outrace a Womanizer in The Outback                    |
+  |SOUTH WAIT       | A Amazing Documentary of a Car And a Robot who must Escape a Lumberjack in An Abandoned Amusement Park             |
+  |SWEDEN SHINING   | A Taut Documentary of a Car And a Robot who must Conquer a Boy in The Canadian Rockies                             |
+  |VIRGIN DAISY     | A Awe-Inspiring Documentary of a Robot And a Mad Scientist who must Reach a Database Administrator in A Shark Tank |
+  ```
+
+<br/>
+
+## 清理
+
+如需清理环境并删除样本数据库，请运行以下命令：
+
+```sql
+\c postgres;
+DROP DATABASE mogila;
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/1-GAUSS-00001-GAUSS-00100.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/1-GAUSS-00001-GAUSS-00100.md
new file mode 100644
index 0000000000000000000000000000000000000000..5a6e1702c8a5e3e5ba0849d36d2be471e0a948e1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/1-GAUSS-00001-GAUSS-00100.md
@@ -0,0 +1,828 @@
+---
+title: GAUSS-00001 - GAUSS-00100
+summary: GAUSS-00001 - GAUSS-00100
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-00001 - GAUSS-00100
+
+<br/>
+
+## GAUSS-00001 - GAUSS-00010
+
+<br/>
+
+### GAUSS-00001: "operator does not exist: %s"
+
+SQLSTATE: 42883
+
+错误原因: 所指定使用的操作符不存在。
+
+解决办法: 建议错误信息中包含操作符所涉及的类型，以便在系统表中查询是否存在相关的操作符。
+
+### GAUSS-00002: "could not identify an ordering operator for type %s"
+
+SQLSTATE: 42883
+
+错误原因: 对于需要进行sort/group操作时，需要进行排序，如果涉及类型的大于或小于操作符不存在，就会报这个错。
+
+解决办法: 此错误信息包含数据类型，使用之前可以在pg_operator系统表中查询，确保操作符存在。
+
+### GAUSS-00003: "could not identify an equality operator for type %s"
+
+SQLSTATE: 42883
+
+错误原因: 在进行group、unique类似操作时，如果涉及等于操作，但是涉及类型的操作符不存在，就会报这个错。
+
+解决办法: 此错误信息包含数据类型，使用之前可以在pg_operator系统表中查询，确保操作符存在。
+
+### GAUSS-00004: "operator requires run-time type coercion: %s"
+
+SQLSTATE: 42883
+
+错误原因: 使用order by using语句指定使用某个操作符，在运行中，会去校验所给类型和操作符之间是否兼容，不兼容即报错。
+
+解决办法: 确保使用时指定的操作符和类型之间是兼容的。
+
+### GAUSS-00005: "operator is not unique: %s"
+
+SQLSTATE: 42725
+
+错误原因: 对于一些类型，没有明确的操作符，在使用中要通过类型转换来寻找合适的操作符，当相关的类型转换涉及多个时就会报错。
+
+解决办法: 对于没有操作符的类型，可以使用类型转换指定其使用某个操作符。
+
+### GAUSS-00006: "operator is only a shell: %s"
+
+SQLSTATE: 42883
+
+错误原因: 未定义的函数。
+
+解决办法: 用户检查输入语句。
+
+### GAUSS-00007: "op ANY/ALL (array) requires array on right side"
+
+SQLSTATE: 42809
+
+错误原因: 对于ANY/ALL (array)操作符，右参数不是数组类型。
+
+解决办法: 对于ANY/ALL (array)操作符，右参数请使用数组类型。
+
+### GAUSS-00008: "op ANY/ALL (array) requires operator to yield Boolean"
+
+SQLSTATE: 42809
+
+错误原因: 对于ANY/ALL (array)操作符，返回值的类型不是布尔类型。
+
+解决办法: 对于ANY/ALL (array)操作符，返回值的类型请使用布尔类型。
+
+### GAUSS-00009: "op ANY/ALL (array) requires operator not to return a set"
+
+SQLSTATE: 42809
+
+错误原因: 对于ANY/ALL (array)操作符，返回值的类型使用了不支持的集合类型。
+
+解决办法: 对于ANY/ALL (array)操作符，返回值的类型请不要使用集合类型。
+
+### GAUSS-00010: "could not find array type for data type %s"
+
+SQLSTATE: 42704
+
+错误原因: 对于某个类型，找不到其对应的数组类型，则报错。
+
+解决办法: 如果要使用类型对应的数组类型，可查询pg_type系统表看其是否有对应的或这个兼容的数组类型。
+
+<br/>
+
+## GAUSS-00011 - GAUSS-00020
+
+<br/>
+
+### GAUSS-00011: "hash table corrupted"
+
+SQLSTATE: LL002
+
+错误原因: 哈希表损坏。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00012: "target lists can have at most %d entries"
+
+SQLSTATE: 54000
+
+错误原因: 目标列表中属性的个数超过了上限（1664）。
+
+解决办法: 请调小目标列表中属性的个数。
+
+### GAUSS-00013: "cache lookup failed for type %u"
+
+SQLSTATE: 22P06
+
+错误原因: 非法的操作符。
+
+解决办法: 检查SQL语句中的操作符是否合法。
+
+### GAUSS-00014: "cannot subscript type %s because it is not an array"
+
+SQLSTATE: 42804
+
+错误原因: 对非数组类型使用下标操作。
+
+解决办法: 非数组类型不能使用下标操作。
+
+### GAUSS-00015: "array subscript must have type integer"
+
+SQLSTATE: 42804
+
+错误原因: 数组下标使用错误。
+
+解决办法: 数组下标必须是整型。
+
+### GAUSS-00016: "array assignment requires type %s but expression is of type %s"
+
+SQLSTATE: 42804
+
+错误原因: 对数组类型的变量进行赋值时，类型之间没有类型转换。
+
+解决办法: 变量给变量赋值，变量之间要有类型转换函数，可查看pg_cast系统表获取相关信息。
+
+### GAUSS-00017: "unrecognized node type: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00018: "failed to find conversion function from %s to %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00020: "cache lookup failed for function %u"
+
+SQLSTATE: 22P06
+
+错误原因: 在系统表中未找到对应ID的函数。
+
+解决办法: 请检查是否有会话并发对该函数做了drop或create or replace的操作。
+
+<br/>
+
+## GAUSS-00021 - GAUSS-00030
+
+<br/>
+
+### GAUSS-00021: "unsupported pathtype %d in build_coercion_expression"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00022: "cannot cast type %s to %s"
+
+SQLSTATE: 42846
+
+错误原因: 两个类型之间不能相互转化。
+
+解决办法: 两个类型之间不存在类型转换函数，可查看pg_cast系统表获取相关信息。
+
+### GAUSS-00024: "argument of %s must not return a set"
+
+SQLSTATE: 42804
+
+错误原因: 不支持返回集合的操作。
+
+解决办法: 表达式计算不支持返回集合。
+
+### GAUSS-00025: "argument of %s must be type %s, not type %s"
+
+SQLSTATE: 42804
+
+错误原因: 源类型和目标类型不一致，且不能转换时，报此错。
+
+解决办法: 源类型和目标类型要兼容可转换。
+
+### GAUSS-00026: "%s types %s and %s cannot be matched"
+
+SQLSTATE: 42804
+
+错误原因: 两个类型的类别不一样。
+
+解决办法: 可查看pg_type中的typcategory字段确定每个类型属于的类别。
+
+### GAUSS-00027: "%s could not convert type %s to %s"
+
+SQLSTATE: 42846
+
+错误原因: 源类型和目标类型不一致，且不能转换时，报此错。
+
+解决办法: 源类型和目标类型要兼容可转换。
+
+### GAUSS-00028: "arguments declared 'anyelement' are not all alike"
+
+SQLSTATE: 42804
+
+错误原因: 对于伪类型作为函数参数，数组中各个元素的类型和定义的类型不一致。
+
+解决办法: 对于伪类型作为函数参数，数组中各个元素的类型和定义的类型要保持一致。
+
+### GAUSS-00029: "arguments declared 'anyarray' are not all alike"
+
+SQLSTATE: 42804
+
+错误原因: 对于伪类型作为函数参数，数组中各个元素的类型和定义的类型不一致。
+
+解决办法: 对于伪类型作为函数参数，数组中各个元素的类型和定义的类型要保持一致。
+
+### GAUSS-00030: "arguments declared 'anyrange' are not all alike"
+
+SQLSTATE: 42804
+
+错误原因: 对于伪类型作为函数参数，数组中各个元素的类型和定义的类型不一致。
+
+解决办法: 对于伪类型作为函数参数，数组中各个元素的类型和定义的类型要保持一致。
+
+<br/>
+
+## GAUSS-00031 - GAUSS-00040
+
+<br/>
+
+### GAUSS-00031: "argument declared 'anyarray' is not an array but type %s"
+
+SQLSTATE: 42804
+
+错误原因: 声明的参数和实际传入的参数类型不符。
+
+解决办法: 传入的参数要和声明的参数类型一致。
+
+### GAUSS-00032: "argument declared 'anyarray' is not consistent with argument declared 'anyelement'"
+
+SQLSTATE: 42804
+
+错误原因: 对于数组类型的ANY谓词，定义的数组类型与ANY数组中每个元素的类型不匹配。
+
+解决办法: 1.请分别查看定义的ANY数组的类型和ANY数组中元素的类型；2.分别确认查询语句中出现的ANY数组的类型和ANY数组中元素的类型是否正确。
+
+### GAUSS-00033: "argument declared 'anyrange' is not a range but type %s"
+
+SQLSTATE: 42804
+
+错误原因: 对于范围类型的ANY谓词，定义的范围类型与ANY数组中每个元素的类型不匹配。
+
+解决办法: 1.请分别查看定义的ANY范围的类型和ANY数组中元素的类型；2.分别确认查询语句中出现的ANY范围的类型和ANY数组中元素的类型是否正确。
+
+### GAUSS-00034: "argument declared 'anyrange' is not consistent with argument declared 'anyelement'"
+
+SQLSTATE: 42804
+
+错误原因: 实际的参数类型和声明的参数类型不一致。
+
+解决办法: 实际的参数类型和声明的参数类型要保持一致。
+
+### GAUSS-00035: "could not determine polymorphic type because input has type 'unknown'"
+
+SQLSTATE: 42804
+
+错误原因: 无法识别数组元素类型。
+
+解决办法: 请确认ANY谓词中数组元素的类型是否正确。
+
+### GAUSS-00036: "type matched to anynonarray is an array type: %s"
+
+SQLSTATE: 42804
+
+错误原因: 实际需要的不是array类型。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+### GAUSS-00037: "type matched to anyenum is not an enum type: %s"
+
+SQLSTATE: 42804
+
+错误原因: 实际需要的是enum类型。
+
+解决办法: 声明为anyenum类型的参数只接受enum类型。
+
+### GAUSS-00038: "could not find range type for data type %s"
+
+SQLSTATE: 42704
+
+错误原因: 数组声明为范围类型，但是实际传入的值不是范围类型。
+
+解决办法: 对数组赋值时，类型要和定义时的类型保持一致。
+
+### GAUSS-00039: "could not determine polymorphic type because context isn't polymorphic"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00040: "unrecognized castcontext: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-00041 - GAUSS-00050
+
+<br/>
+
+### GAUSS-00041: "unrecognized castmethod: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00042: "cache lookup failed for relation %u"
+
+SQLSTATE: XX000
+
+错误原因: ALTER TABLE SET TABLESPACE操作，关系不存在。
+
+解决办法: 无法找到关系表，建议更改本操作。
+
+### GAUSS-00043: "unsafe use of string constant with Unicode escapes"
+
+SQLSTATE: 0A000
+
+错误原因: standard_conforming_strings开关关闭情况下，字符串常量不能定义为统一编码的转义字符。
+
+解决办法: 1.请检查输入语句中的转义字符是否正确。2.通过gsql将standard_conforming_strings开关设置为on。
+
+### GAUSS-00044: "invalid Unicode escape"
+
+SQLSTATE: 22025
+
+错误原因: 输入的语句中存在非法的转义字符序列。
+
+解决办法: 请检查输入语句中转义字符序列的语法是否正确，是否存在如下字符序列: 例如: \\uXXXX或\\UXXXXXXXXX，其中""X""表示0..9或A..F或a..f。
+
+### GAUSS-00045: "unsafe use of \\' in a string literal"
+
+SQLSTATE: 22P06
+
+错误原因: 在字符串中使用了非法的转义字符'\\'。
+
+解决办法: 检查SQL语法中使用的转义字符'\\'是否正确，并修改SQL语法。
+
+### GAUSS-00046: "%s at end of input"
+
+SQLSTATE: 42601
+
+错误原因: 给定语句的结束符语法错误。
+
+解决办法: 检查并修改输入语句的语法。
+
+### GAUSS-00047: "%s at or near '%s'"
+
+SQLSTATE: 42601
+
+错误原因: 语法错误。
+
+解决办法: 保证执行的sql没有语法错误。
+
+### GAUSS-00048: "core_yylex_init() failed: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00049: "invalid hexadecimal digit"
+
+SQLSTATE: XX000
+
+错误原因: invalid input or unsupport format
+
+解决办法: 用户检查输入SQL。
+
+<br/>
+
+## GAUSS-00051 - GAUSS-00060
+
+<br/>
+
+### GAUSS-00052: "column '%s' of relation '%s' does not exist"
+
+SQLSTATE: 42703
+
+错误原因: 列名或者为空，或者拼写错误，或者不是关系表中定义的列名。
+
+解决办法: 请通过\\d tblname检查当前指定的列名是否为表中指定的列名，如果不正确，请修改为合法的列名。
+
+### GAUSS-00053: "type '%s' does not exist"
+
+SQLSTATE: 42704
+
+错误原因: 根据给定的类型名在系统表pg_type中无法找到匹配的类型。
+
+解决办法: 请检查语句中使用的类型名是否正确（可参考系统表pg_type中已定义的类型）。
+
+### GAUSS-00054: "type '%s' is only a shell"
+
+SQLSTATE: 42704
+
+错误原因: 给定的类型名在系统表pg_type中没有定义对应的操作执行函数。
+
+解决办法: 请确认语句中使用的类型名是否正确。如果正确，请通过create type语句自定义所使用类型名对应的操作函数。
+
+### GAUSS-00055: "type modifier cannot be specified for shell type '%s'"
+
+SQLSTATE: 42601
+
+错误原因: 自定义的类型包含了typmod。
+
+解决办法: 自定义的类型不能包含typmod。
+
+### GAUSS-00056: "type modifier is not allowed for type '%s'"
+
+SQLSTATE: 42601
+
+错误原因: 自定义的类型包含了typmod。
+
+解决办法: 自定义的类型不能包含typmod。
+
+### GAUSS-00057: "type modifiers must be simple constants or identifiers"
+
+SQLSTATE: 42601
+
+错误原因: 给定的类型修饰符错误。
+
+解决办法: 类型表示符必须定义为常量或标识符，请检查给定的类型修饰符语法是否正确，然后重新定义一个合法的类型修饰符。
+
+### GAUSS-00058: "collations are not supported by type %s"
+
+SQLSTATE: 42804
+
+错误原因: collation与类型不匹配，输入的问题。
+
+解决办法: 用户检查输入SQL。
+
+### GAUSS-00059: "typeTypeId() called with NULL type struct"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00060: "invalid type name '%s'"
+
+SQLSTATE: 42601
+
+错误原因: 给定的类型名无效。
+
+解决办法: 请检查语句中使用的类型名是否正确（可参考系统表pg_type中已定义的类型）。
+
+<br/>
+
+## GAUSS-00061 - GAUSS-00070
+
+<br/>
+
+### GAUSS-00061: "unrecognized A_Expr kind: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00062: "column %s.%s does not exist"
+
+SQLSTATE: 42703
+
+错误原因: 列名或者为空，或者拼写错误，或者不是关系表中定义的列名。
+
+解决办法: 请通过\\d tblname检查当前指定的列名是否为表中指定的列名，如果不正确，请修改为合法的列名。
+
+### GAUSS-00063: "column '%s' not found in data type %s"
+
+SQLSTATE: 42703
+
+错误原因: 给定列的类型定义错误。
+
+解决办法: 通过\\d tblname确认表中列的类型定义是否正确。
+
+### GAUSS-00064: "could not identify column '%s' in record data type"
+
+SQLSTATE: 42703
+
+错误原因: 列不存在，通过record数据类型不能识别列。
+
+解决办法: 检查列是否存在。
+
+### GAUSS-00065: "column notation .%s applied to type %s, which is not a composite type"
+
+SQLSTATE: 42809
+
+错误原因: 通过记号'.'来访问一个非复合类型的成员。
+
+解决办法: 确认类型是否为复合类型，如果为非复合类型，不能通过记号'.'方式访问。
+
+### GAUSS-00066: "row expansion via '*' is not supported here"
+
+SQLSTATE: 0A000
+
+错误原因: 当前上下文不支持通过*来进行列展开。
+
+解决办法: 当前上下文避免使用*进行列展开。
+
+### GAUSS-00067: "column reference '%s' is ambiguous"
+
+SQLSTATE: 42702
+
+错误原因: 列引用时多次引用了同一列。
+
+解决办法: 请排查和修改语法，避免多次引用同一列。
+
+### GAUSS-00068: "column '%s' does not exist"
+
+SQLSTATE: 42703
+
+错误原因: 列不存在。
+
+解决办法: 请检查表定义中是否存在要使用的列。
+
+### GAUSS-00069: "cross-database references are not implemented: %s"
+
+SQLSTATE: 0A000
+
+错误原因: 不支持跨数据库的引用对象。
+
+解决办法: 避免跨数据库的引用。在数据库Database2中不能通过Database1.schema.object方式访问数据库Database1中的对象，object包括: 表、索引、视图等。
+
+### GAUSS-00070: "improper qualified name (too many dotted names): %s"
+
+SQLSTATE: 42601
+
+错误原因: 点分隔符使用不当，个数过多，无法正确解析。
+
+解决办法: 请减少点分隔符个数后重试。
+
+<br/>
+
+## GAUSS-00071 - GAUSS-00080
+
+<br/>
+
+### GAUSS-00071: "there is no parameter $%d"
+
+SQLSTATE: 42P02
+
+错误原因: 参数序号超出了合法的参数序号范围。
+
+解决办法: 使用参数序号时，要注意其取值范围。
+
+### GAUSS-00072: "NULLIF requires = operator to yield Boolean"
+
+SQLSTATE: 42804
+
+错误原因: NULLIF中的参数比较时，所使用的函数返回值不是布尔类型。
+
+解决办法: NULLIF中的参数比较时，函数返回值请使用布尔类型。
+
+### GAUSS-00073: "arguments of row IN must all be row expressions"
+
+SQLSTATE: 42601
+
+错误原因: 对于IN表达式，参数不是数组类型，也不是行表达式。
+
+解决办法: 对于IN表达式，参数为数组类型或者行表达式。
+
+### GAUSS-00074: "unexpected non-SELECT command in SubLink"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00075: "subquery must return a column"
+
+SQLSTATE: 42601
+
+错误原因: 子查询没有返回列。
+
+解决办法: 子查询必须返回至少一列。
+
+### GAUSS-00076: "subquery must return only one column"
+
+SQLSTATE: 42601
+
+错误原因: 子查询作为子表达式时，不允许返回多列。
+
+解决办法: 子查询作为子表达式时，只能返回一列。
+
+### GAUSS-00077: "subquery has too many columns"
+
+SQLSTATE: 42601
+
+错误原因: 在行表达式中，子查询返回的列数大于实际需要的列数。
+
+解决办法: 请检查行表达式中子查询返回的列数，确保其等于实际需要的列数。
+
+### GAUSS-00078: "subquery has too few columns"
+
+SQLSTATE: 42601
+
+错误原因: 在行表达式中，子查询返回的列数小于实际需要的列数。
+
+解决办法: 请检查行表达式中子查询返回的列数，确保其等于实际需要的列数。
+
+### GAUSS-00079: "cannot determine type of empty array"
+
+SQLSTATE: 42P18
+
+错误原因: 对于一个空的数组不能确定其类型。
+
+解决办法: 对数据做强制类型转换。
+
+### GAUSS-00080: "could not find element type for data type %s"
+
+SQLSTATE: 42704
+
+错误原因: 数组中的某个元素不是合法的数据类型。
+
+解决办法: 存入到数组中的值的类型要和声明的类型一致。
+
+<br/>
+
+## GAUSS-00081 - GAUSS-00090
+
+<br/>
+
+### GAUSS-00081: "unnamed XML attribute value must be a column reference"
+
+SQLSTATE: 42601
+
+错误原因: 未命名的XML属性值必须是列的引用。
+
+解决办法: 用户检查输入SQL。
+
+### GAUSS-00082: "XML attribute name '%s' appears more than once"
+
+SQLSTATE: 42601
+
+错误原因: XMLELEMENT中出现了重复的列。
+
+解决办法: 用户检查输入SQL。
+
+### GAUSS-00083: "cannot cast XMLSERIALIZE result to %s"
+
+SQLSTATE: 42846
+
+错误原因: 将XMLSERIALIZE类型转换到其它类型时报错。
+
+解决办法: 使用时类型之间要保证可以相互转换。
+
+### GAUSS-00084: "unrecognized booltesttype: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00085: "WHERE CURRENT OF clause not yet supported"
+
+SQLSTATE: 54001
+
+错误原因: 使用了WHERE CURRENT OF语法。
+
+解决办法: WHERE CURRENT OF语法未支持，不建议使用。
+
+### GAUSS-00086: "unequal number of entries in row expressions"
+
+SQLSTATE: 42601
+
+错误原因: 行表达式中，使用等于操作符的左右的参数个数不相等。
+
+解决办法: 行表达式中，使用等于操作符的左右的参数个数要相等。
+
+### GAUSS-00087: "cannot compare rows of zero length"
+
+SQLSTATE: 0A000
+
+错误原因: 行比较的长度为0。
+
+解决办法: 使用行比较时，保证长度不为0。
+
+### GAUSS-00088: "row comparison operator must yield type Boolean, not type %s"
+
+SQLSTATE: 42804
+
+错误原因: 行表达式比较的返回值不是bool类型。
+
+解决办法: 行表达式比较的返回值要求是bool类型。
+
+### GAUSS-00089: "row comparison operator must not return a set"
+
+SQLSTATE: 42804
+
+错误原因: 行表达式比较的返回值是集合类型。
+
+解决办法: 行表达式比较的返回值要求不能是集合类型。
+
+### GAUSS-00090: "could not determine interpretation of row comparison operator %s"
+
+SQLSTATE: 0A000
+
+错误原因: 找不到行比较操作符。
+
+解决办法: 使用行比较时确定行比较操作符存在。
+
+<br/>
+
+## GAUSS-00091 - GAUSS-00100
+
+<br/>
+
+### GAUSS-00091: "IS DISTINCT FROM requires = operator to yield Boolean"
+
+SQLSTATE: 42804
+
+错误原因: IS DISTINCT FROM语句中，去重时使用的操作符返回值不是布尔类型。
+
+解决办法: IS DISTINCT FROM语句中，去重时的操作符返回值请使用布尔类型。
+
+### GAUSS-00092: "collation mismatch between implicit collations '%s' and '%s'"
+
+SQLSTATE: 42P21
+
+错误原因: 两个字符集不能进行隐式转换。
+
+解决办法: 字符集转换时要保证两者之间是兼容的。
+
+### GAUSS-00093: "collation mismatch between explicit collations '%s' and '%s'"
+
+SQLSTATE: 42P21
+
+错误原因: 两个字符集不能进行显示转换。
+
+解决办法: 字符集转换时要保证两者之间是兼容的。
+
+### GAUSS-00094: "table reference '%s' is ambiguous"
+
+SQLSTATE: 42P09
+
+错误原因: 引用表时由于重复的表名导致引用模糊。
+
+解决办法: 引用时请明确指定表名。
+
+### GAUSS-00095: "table reference %u is ambiguous"
+
+SQLSTATE: 42P09
+
+错误原因: 引用表时由于重复的表名导致引用模糊。
+
+解决办法: 引用时请明确指定表名。
+
+### GAUSS-00096: "table name '%s' specified more than once"
+
+SQLSTATE: 42712
+
+错误原因: from语句中同一个表名未使用别名时多次使用。
+
+解决办法: from语句中要多次使用同一个表，需要指定别名。
+
+### GAUSS-00097: "RTE not found (internal error)"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00098: "bad levelsup for CTE '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00099: "could not find CTE '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/10-GAUSS-00901-GAUSS-01000.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/10-GAUSS-00901-GAUSS-01000.md
new file mode 100644
index 0000000000000000000000000000000000000000..41bce8264dac19a653112c170e2e2d152de769c6
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/10-GAUSS-00901-GAUSS-01000.md
@@ -0,0 +1,756 @@
+---
+title: GAUSS-00901 - GAUSS-01000
+summary: GAUSS-00901 - GAUSS-01000
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-00901 - GAUSS-01000
+
+<br/>
+
+## GAUSS-00901 - GAUSS-00910
+
+<br/>
+
+GAUSS-00901: "tables in ALTER TABLE EXCHANGE PARTITION must have the same column/row storage"
+
+SQLSTATE: 0A000
+
+错误原因: ALTER TABLE EXCHANGE PARTITION语句执行的表必有相同的行/列存储。
+
+解决办法: 建议检查ALTER TABLE EXCHANGE PARTITION语句执行的表是否有相同的行列存储，否则不能执行。
+
+GAUSS-00902: "tables in ALTER TABLE EXCHANGE PARTITION must have the same type of compress"
+
+SQLSTATE: 0A000
+
+错误原因: ALTER TABLE EXCHANGE PARTITION语句执行的表必有相同的压缩类型。
+
+解决办法: 建议检查ALTER TABLE EXCHANGE PARTITION语句执行的表是否有相同的压缩类型，否则不能执行。
+
+GAUSS-00903: "tables in ALTER TABLE EXCHANGE PARTITION must have the same number of columns"
+
+SQLSTATE: 0A000
+
+错误原因: ALTER TABLE EXCHANGE PARTITION语句执行的表必有相同的列数。
+
+解决办法: 建议检查ALTER TABLE EXCHANGE PARTITION语句执行的表是否有相同的列数，否则不能执行。
+
+GAUSS-00904: "column name mismatch in ALTER TABLE EXCHANGE PARTITION"
+
+SQLSTATE: 0A000
+
+错误原因: ALTER TABLE EXCHANGE PARTITION语句执行的表列名不匹配。
+
+解决办法: 建议检查ALTER TABLE EXCHANGE PARTITION语句执行的表是否有相同的列名，否则不能执行。
+
+GAUSS-00905: "column type or size mismatch in ALTER TABLE EXCHANGE PARTITION"
+
+SQLSTATE: 0A000
+
+错误原因: ALTER TABLE EXCHANGE PARTITION语句执行的表列类型及大小不匹配。
+
+解决办法: 建议检查ALTER TABLE EXCHANGE PARTITION语句执行的表是否有相同的列类型和大小，否则不能执行。
+
+GAUSS-00906: "column not null constraint mismatch in ALTER TABLE EXCHANGE PARTITION"
+
+SQLSTATE: 0A000
+
+错误原因: ALTER TABLE EXCHANGE PARTITION语句执行的表列不能为空限制不匹配。
+
+解决办法: 建议检查ALTER TABLE EXCHANGE PARTITION语句执行的表列是否同时有不能为空限制，否则不能执行。
+
+GAUSS-00907: "column default constraint mismatch in ALTER TABLE EXCHANGE PARTITION"
+
+SQLSTATE: 0A000
+
+错误原因: ALTER TABLE EXCHANGE PARTITION语句执行的表列默认限制不匹配。
+
+解决办法: 建议检查ALTER TABLE EXCHANGE PARTITION语句执行的表列是否有相同的默认限制，否则不能执行。
+
+GAUSS-00908: "column collation mismatch in ALTER TABLE EXCHANGE PARTITION"
+
+SQLSTATE: 0A000
+
+错误原因: ALTER TABLE EXCHANGE PARTITION语句执行表的列排序不匹配。
+
+解决办法: 建议检查ALTER TABLE EXCHANGE PARTITION语句执行的表是否有相同的列排序，否则不能执行。
+
+GAUSS-00909: "column storage mismatch in ALTER TABLE EXCHANGE PARTITION"
+
+SQLSTATE: 0A000
+
+错误原因: ALTER TABLE EXCHANGE PARTITION语句执行的表列存储不匹配。
+
+解决办法: 建议检查ALTER TABLE EXCHANGE PARTITION语句执行的表是否有相同的列存储，否则不能执行。
+
+GAUSS-00910: "the type of column compress mismatch in ALTER TABLE EXCHANGE PARTITION"
+
+SQLSTATE: 0A000
+
+错误原因: ALTER TABLE EXCHANGE PARTITION语句执行的表列压缩类型不匹配。
+
+解决办法: 建议检查ALTER TABLE EXCHANGE PARTITION语句执行的表是否有相同的压缩类型，否则不能执行。
+
+<br/>
+
+## GAUSS-00911 - GAUSS-00920
+
+<br/>
+
+GAUSS-00911: "constraint mismatch in ALTER TABLE EXCHANGE PARTITION"
+
+SQLSTATE: 0A000
+
+错误原因: ALTER TABLE EXCHANGE PARTITION语句执行的表列限制不匹配。
+
+解决办法: 建议检查ALTER TABLE EXCHANGE PARTITION语句执行的表是否有相同的列限制，否则不能执行。
+
+GAUSS-00912: "distribute mismatch for tables in ALTER TABLE EXCHANGE PARTITION"
+
+SQLSTATE: 0A000
+
+错误原因: ALTER TABLE EXCHANGE PARTITION语句执行的表列分布不匹配。
+
+解决办法: 建议检查ALTER TABLE EXCHANGE PARTITION语句执行的表是否有相同的列分布，否则不能执行。
+
+GAUSS-00913: "tables in ALTER TABLE EXCHANGE PARTITION must have the same number of indexs"
+
+SQLSTATE: 0A000
+
+错误原因: ALTER TABLE EXCHANGE PARTITION语句执行的表索引数目不匹配。
+
+解决办法: 建议检查ALTER TABLE EXCHANGE PARTITION语句执行的表是否有相同的索引数目，否则不能执行。
+
+GAUSS-00914: "index mismatch for tables in ALTER TABLE EXCHANGE PARTITION"
+
+SQLSTATE: 0A000
+
+错误原因: ALTER TABLE EXCHANGE PARTITION语句执行的表索引不匹配。
+
+解决办法: 建议检查ALTER TABLE EXCHANGE PARTITION语句执行的表是否有相同的表索引，否则不能执行。
+
+GAUSS-00915: "some rows in table do not qualify for specified partition"
+
+SQLSTATE: 0A000
+
+错误原因: SPLIT PARTITION操作执行时，表中的一些行不符合指定的分区。
+
+解决办法: 请检查表中不符合指定分区的行，查明原因。
+
+GAUSS-00916: "the number of resulting partitions must be more than one"
+
+SQLSTATE: 42601
+
+错误原因: SPLIT PARTITION操作得到结果数目小于2个，表明分割分区失败。
+
+解决办法: 无分割点(split point)，分割分区失败，建议检查失败原因。
+
+GAUSS-00917: "the bound of the first resulting partition is too low"
+
+SQLSTATE: 42601
+
+错误原因: SPLIT PARTITION操作得到的第一结果分区边界过低，分割分区失败。
+
+解决办法: 分割分区操作失败，建议重新检查SPLIT PARTITION操作。
+
+GAUSS-00918: "the bound of resulting partition '%s' is too low"
+
+SQLSTATE: 42601
+
+错误原因: SPLIT PARTITION操作得到的结果分区边界过低，分割分区失败。
+
+解决办法: 分割分区操作失败，建议重新检查SPLIT PARTITION操作。
+
+GAUSS-00919: "the bound of the last resulting partition is not equal with specified partition bound"
+
+SQLSTATE: 42601
+
+错误原因: SPLIT PARTITION操作得到的最后一个结果分区边界与指定分区边界不等，分割分区失败。
+
+解决办法: 分割分区操作失败，建议重新检查SPLIT PARTITION操作。
+
+GAUSS-00920: "number of boundary items NOT EQUAL to number of partition keys"
+
+SQLSTATE: 42601
+
+错误原因: SPLIT PARTITION操作得到的边界项数目与分区键值数目不同，分割分区失败。
+
+解决办法: 分割分区操作失败，建议重新检查SPLIT PARTITION操作。
+
+<br/>
+
+## GAUSS-00921 - GAUSS-00930
+
+<br/>
+
+GAUSS-00921: "split point is too low"
+
+SQLSTATE: 0A000
+
+错误原因: SPLIT PARTITION操作得到的分割点应介于前分区与后分区之间，实际得到的分割点小于前分区。
+
+解决办法: 分割分区操作失败，建议重新检查SPLIT PARTITION操作。
+
+GAUSS-00922: "split point is too high"
+
+SQLSTATE: 0A000
+
+错误原因: SPLIT PARTITION操作得到的分割点应介于前分区与后分区之间，实际得到的分割点大于后分区。
+
+解决办法: 分割分区操作失败，建议重新检查SPLIT PARTITION操作。
+
+GAUSS-00923: "resulting partition '%s' name conflicts with that of an existing partition"
+
+SQLSTATE: 42710
+
+错误原因: SPLIT PARTITION操作得到的分区名称与已有分区名冲突，该分割分区操作不能执行。
+
+解决办法: 建议修改结果分区名称。
+
+GAUSS-00924: "number of boundary items NOT EQUAL to number of partition keys"
+
+SQLSTATE: 42601
+
+错误原因: SPLIT PARTITION操作得到的边界项数目与分区键值数目不同，分割分区失败。
+
+解决办法: 分割分区操作失败，建议重新检查SPLIT PARTITION操作。
+
+GAUSS-00925: "cache lookup failed for toast table: %u"
+
+SQLSTATE: XX000
+
+错误原因: 没有找到对应的toast表。
+
+解决办法: 系统表异常，请联系技术支持工程师提供技术支持。
+
+GAUSS-00926: "cache lookup failed for cuDesc table: %u"
+
+SQLSTATE: XX000
+
+错误原因: 没有找到对应的cuDesc表。
+
+解决办法: 系统表异常，请联系技术支持工程师提供技术支持。
+
+GAUSS-00927: "cache lookup failed for delta table: %u"
+
+SQLSTATE: XX000
+
+错误原因: 没有找到对应的delta表。
+
+解决办法: 系统表异常，请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-00931 - GAUSS-00940
+
+<br/>
+
+GAUSS-00935: "cache lookup failed for relation %u"
+
+SQLSTATE: 02000
+
+错误原因: ALTER TABLE SET TABLESPACE操作，关系不存在。
+
+解决办法: 无法找到关系表，建议更改本操作。
+
+GAUSS-00936: "SQL function cannot return shell type %s"
+
+SQLSTATE: 42P13
+
+错误原因: SQL函数不支持返回共享类型的变量。
+
+解决办法: 修改SQL函数，不使用共享类型变量作为返回值。
+
+GAUSS-00937: "SQL function cannot accept shell type %s"
+
+SQLSTATE: 42P13
+
+错误原因: SQL函数不支持共享类型的变量作为函数参数。
+
+解决办法: 修改SQL函数，不使用共享类型变量作为函数参数。
+
+GAUSS-00938: "type %s does not exist"
+
+SQLSTATE: 42704
+
+错误原因: 所提示的数据类型不存在。
+
+解决办法: 请检查函数或存储过程，确定参数的数据类型是否正确。
+
+GAUSS-00940: "VARIADIC parameter must be the last input parameter"
+
+SQLSTATE: 42P13
+
+错误原因: VARIADIC参数必须放在输入参数的最后位置。
+
+解决办法: 修改函数参数列表，将VARIADIC参数放在输入参数的最后位置。
+
+<br/>
+
+## GAUSS-00941 - GAUSS-00950
+
+<br/>
+
+GAUSS-00941: "VARIADIC parameter must be an array"
+
+SQLSTATE: 42P13
+
+错误原因: VARIADIC参数必须是数组类型。
+
+解决办法: 修改函数参数，使用数组类型变量作为VARIADIC参数。
+
+GAUSS-00942: "parameter name '%s' used more than once"
+
+SQLSTATE: 42P13
+
+错误原因: 在参数列表中多次使用了同一个参数名称。
+
+解决办法: 修改函数参数，使用不同的参数名称。
+
+GAUSS-00943: "only input parameters can have default values"
+
+SQLSTATE: 42P13
+
+错误原因: 只有输入参数才能有默认值。
+
+解决办法: 修改函数参数，只对输入参数定义默认值。
+
+GAUSS-00944: "cannot use table references in parameter default value"
+
+SQLSTATE: 42P10
+
+错误原因: 不能在参数的默认值中使用变量（如表、列、CurrentOf表达式等）。
+
+解决办法: 修改函数参数，不使用变量作为默认值。
+
+GAUSS-00945: "cannot use subquery in parameter default value"
+
+SQLSTATE: 0A000
+
+错误原因: 不能在参数的默认值中使用子查询。
+
+解决办法: 修改函数参数，不使用子查询作为默认值。
+
+GAUSS-00946: "cannot use aggregate function in parameter default value"
+
+SQLSTATE: 42803
+
+错误原因: 不能在参数的默认值中使用聚集函数。
+
+解决办法: 修改函数参数，不使用聚集函数作为默认值。
+
+GAUSS-00947: "cannot use window function in parameter default value"
+
+SQLSTATE: 42P20
+
+错误原因: 不能在参数的默认值中使用窗口函数。
+
+解决办法: 修改函数参数，不使用窗口函数作为默认值。
+
+GAUSS-00948: "invalid volatility '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 函数volatile类型非法。
+
+解决办法: 系统表异常，请联系技术支持工程师提供技术支持。
+
+GAUSS-00949: "no function body specified"
+
+SQLSTATE: 42P13
+
+错误原因: 没有定义函数体。
+
+解决办法: 请检查函数，确保定义了函数体。
+
+GAUSS-00950: "no language specified"
+
+SQLSTATE: 42P13
+
+错误原因: 没有定义函数的语言类型（如C/plpgsql/sql）。
+
+解决办法: 检查函数定义，确保定义了语言类型（如C/plpgsql/sql）。
+
+<br/>
+
+## GAUSS-00951 - GAUSS-00960
+
+<br/>
+
+GAUSS-00951: "COST must be positive"
+
+SQLSTATE: 22023
+
+错误原因: COST必须是正数。
+
+解决办法: 检查函数定义，确保COST定义为正数。
+
+GAUSS-00952: "ROWS must be positive"
+
+SQLSTATE: 22023
+
+错误原因: ROWS必须还正数。
+
+解决办法: 检查函数定义，确保ROWS定义为正数。
+
+GAUSS-00953: "only one AS item needed for language '%s'"
+
+SQLSTATE: 42P13
+
+错误原因: 只需要一个AS子句。
+
+解决办法: 检查函数定义，确保只有一个AS子句。
+
+GAUSS-00954: "language '%s' does not exist"
+
+SQLSTATE: 42704
+
+错误原因: 语言不存在。
+
+解决办法: 检查函数定义，确保函数的语言类型是数据库支持的(如language plpgsql/language sql等)。
+
+GAUSS-00955: "only system admin can define a leakproof function"
+
+SQLSTATE: 42501
+
+错误原因: 只有系统管理员来能定义leakproof函数。
+
+解决办法: 使用系统管理员帐户来创建leakproof函数。
+
+GAUSS-00957: "function result type cannot be a view."
+
+SQLSTATE: 42P13
+
+错误原因: 函数返回结果类型不能是视图。
+
+解决办法: 检查函数定义，不使用视图作为函数返回结果的类型。
+
+GAUSS-00958: "ROWS is not applicable when function does not return a set"
+
+SQLSTATE: 22023
+
+错误原因: 如果不是返回结果集的函数，不能指定ROWS。
+
+解决办法: 检查函数定义，对返回结果集的函数才指定ROWS。
+
+GAUSS-00959: "cache lookup failed for pg_aggregate tuple for function %u"
+
+SQLSTATE: XX000
+
+错误原因: 未在pg_aggregate中找到对应的聚集函数。
+
+解决办法: 系统表异常，请联系技术支持工程师提供技术支持。
+
+GAUSS-00960: "function %u doesn't return OPAQUE"
+
+SQLSTATE: XX000
+
+错误原因: 函数返回类型不是OPAQUE。
+
+解决办法: 请检查对应的函数的返回类型是否正确。
+
+<br/>
+
+## GAUSS-00961 - GAUSS-00970
+
+<br/>
+
+GAUSS-00962: "source data type %s is a pseudo-type"
+
+SQLSTATE: 42809
+
+错误原因: 源数据类型不能为pseudo类型。
+
+解决办法: 检查要创建的CAST，确保源数据类型不是pseudo类型。
+
+GAUSS-00963: "target data type %s is a pseudo-type"
+
+SQLSTATE: 42809
+
+错误原因: 目标数据类型不能为pseudo类型。
+
+解决办法: 检查要创建的CAST，确保目标数据类型不是pseudo类型。
+
+GAUSS-00964: "must be owner of type %s or type %s"
+
+SQLSTATE: 42501
+
+错误原因: 必须是源类型和目标类型的所有者。
+
+解决办法: 检查SQL语句，确保是源类型和目标类型的所有者。
+
+GAUSS-00965: "cast function must take one to three arguments"
+
+SQLSTATE: 42P17
+
+错误原因: CAST函数必须指定1到3个参数。
+
+解决办法: 检查CAST函数，确保有1到3个参数。
+
+GAUSS-00966: "argument of cast function must match or be binary-coercible from source data type"
+
+SQLSTATE: 42P17
+
+错误原因: CAST函数的参数必须和源数据类型匹配或二进制兼容。
+
+解决办法: 检查CAST函数，确保参数和源数据类型匹配或二进制兼容。
+
+GAUSS-00967: "second argument of cast function must be type integer"
+
+SQLSTATE: 42P17
+
+错误原因: CAST函数的第2个参数必须是整数类型。
+
+解决办法: 检查CAST函数，确保第2个参数是整数类型。
+
+GAUSS-00968: "third argument of cast function must be type Boolean"
+
+SQLSTATE: 42P17
+
+错误原因: CAST函数的第3个参数必须是布尔类型。
+
+解决办法: 检查CAST函数，确保第3个参数是布尔类型。
+
+GAUSS-00969: "return data type of cast function must match or be binary-coercible to target data type"
+
+SQLSTATE: 42P17
+
+错误原因: "return data type of cast function must match or be binary-coercible to target data typeCAST函数的返回数据类型必须和目标数据类型匹配或二进制兼容"。
+
+解决办法: "check the CAST function and make sure that return data type of cast function match or be binary-coercible to target data type检查CAST函数，确保返回数据类型和目标数据类型匹配或二进制兼容"。
+
+GAUSS-00970: "cast function must not be volatile"
+
+SQLSTATE: 42P17
+
+错误原因: "cast function must not be volatileCAST函数的属性不能是volatile的"。
+
+解决办法: "check the CAST function and make sure that cast function not be volatile检查CAST函数，确保它的属性不是volatile的"。
+
+<br/>
+
+## GAUSS-00971 - GAUSS-00980
+
+<br/>
+
+GAUSS-00971: "cast function must not be an aggregate function"
+
+SQLSTATE: 42P17
+
+错误原因: 函数不能是聚集函数。
+
+解决办法: 检查CAST函数，确保它不是聚集函数。
+
+GAUSS-00972: "cast function must not be a window function"
+
+SQLSTATE: 42P17
+
+错误原因: 函数不能是窗口函数。
+
+解决办法: 检查CAST函数，确保他不是窗口函数。
+
+GAUSS-00973: "cast function must not return a set"
+
+SQLSTATE: 42P17
+
+错误原因: 函数不能返回结果集。
+
+解决办法: 检查CAST函数，确保它不返回结果集"。
+
+GAUSS-00974: "must be system admin to create a cast WITHOUT FUNCTION"
+
+SQLSTATE: 42501
+
+错误原因: 必须是系统管理员才能指定CAST函数的WITHOUT FUNCTION属性。
+
+解决办法: 若要在创建CAST函数时指定WITHOUT FUNCTION属性，必须使用管理员帐户来执行创建语句。
+
+GAUSS-00975: "source and target data types are not physically compatible"
+
+SQLSTATE: 42P17
+
+错误原因: 源数据类型和目标数据类型不是物理兼容的（物理兼容是指: 这两种数据类型在pg_type系统表中的typlen，typbyval，typalign都相同）。
+
+解决办法: 创建一个CAST时，保证源数据类型和目标数据类型是物理兼容的（物理兼容是指: 这两种数据类型在pg_type系统表中的typlen，typbyval，typalign都相同）。
+
+GAUSS-00976: "composite data types are not binary-compatible"
+
+SQLSTATE: 42P17
+
+错误原因: 复合数据类型不是二进制兼容的，因此不能进行转换。
+
+解决办法: 创建CAST时，请勿使用复合数据类型作为源数据类型或目标数据类型。
+
+GAUSS-00977: "enum data types are not binary-compatible"
+
+SQLSTATE: 42P17
+
+错误原因: 枚举数据类型不是二进制兼容的，因此不能进行转换。
+
+解决办法: 创建CAST时，请勿使用枚举数据类型作为源数据类型或目标数据类型。
+
+GAUSS-00978: "array data types are not binary-compatible"
+
+SQLSTATE: 42P17
+
+错误原因: 数组类型不是二进制兼容的，因此不能进行转换。
+
+解决办法: 创建CAST时，请勿使用数组类型作为源数据类型或目标数据类型。
+
+GAUSS-00979: "domain data types must not be marked binary-compatible"
+
+SQLSTATE: 42P17
+
+错误原因: "domain data types must not be marked binary-compatibledomain数据类型不是二进制兼容的，因此不能进行转换。
+
+解决办法: 创建CAST时，请勿使用domain数据类型作为源数据类型或目标数据类型。
+
+GAUSS-00980: "source data type and target data type are the same"
+
+SQLSTATE: 42P17
+
+错误原因: 源数据类型和目标数据类型相同。
+
+解决办法: 创建CAST时，保证源数据类型和目标数据类型不同。
+
+<br/>
+
+## GAUSS-00981 - GAUSS-00990
+
+<br/>
+
+GAUSS-00981: "unrecognized CoercionContext: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-00982: "cast from type %s to type %s already exists"
+
+SQLSTATE: 42710
+
+错误原因: 从源数据类型到目标数据类型的CAST已经存在。
+
+解决办法: 从源数据类型到目标数据类型的CAST已经存在，无需再创建。
+
+GAUSS-00983: "cast from type %s to type %s does not exist"
+
+SQLSTATE: 42704
+
+错误原因: 从源数据类型到目标数据类型的CAST不存在。
+
+解决办法: 检查pg_cast系统表，看这个CAST是否存在，入不存在，可以进行创建，或重写sql语句来避免使用这个CAST。
+
+GAUSS-00984: "could not find tuple for cast %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-00985: "function '%s' already exists in schema '%s'"
+
+SQLSTATE: 42723
+
+错误原因: 目标模式中的这个函数已存在。
+
+解决办法: 检查目标模式，确定是否已创建了同名函数。
+
+GAUSS-00986: "failed to change schema dependency for function '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 更改函数的模式依赖未成功。
+
+解决办法: 系统表异常，请联系技术支持工程师提供技术支持。
+
+GAUSS-00987: "no inline code specified"
+
+SQLSTATE: 42601
+
+错误原因: 匿名块中没有指定内联语句（匿名块为内联执行，因此其中的语句都是内联语句）。
+
+解决办法: 检查匿名块语法，确保其中有内联语句（匿名块为内联执行，因此其中的语句都是内联语句）。
+
+GAUSS-00988: "language '%s' does not support inline code execution"
+
+SQLSTATE: 0A000
+
+错误原因: 此语言不支持内联执行。
+
+解决办法: 使用普通函数替代或使用其他语言。
+
+GAUSS-00989: "source encoding '%s' does not exist"
+
+SQLSTATE: 42704
+
+错误原因: 转换中的源编码不存在。
+
+解决办法: 检查源编码，确保其在系统中存在。
+
+GAUSS-00990: "destination encoding '%s' does not exist"
+
+SQLSTATE: 42704
+
+错误原因: 转换中的目标编码不存在。
+
+解决办法: 检查目标编码，确保其在系统中存在。
+
+<br/>
+
+## GAUSS-00991 - GAUSS-01000
+
+<br/>
+
+GAUSS-00991: "encoding conversion function %s must return type 'void'"
+
+SQLSTATE: 42P17
+
+错误原因: 编码转换函数只能返回void。
+
+解决办法: 检查编码转换函数，确保其返回void。
+
+GAUSS-00992: "cache lookup failed for conversion %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-00994: "extra data after last expected column"
+
+SQLSTATE: 22P04
+
+错误原因: 数据文件中的列的个数超过表中列的个数。
+
+解决办法: 检查数据文件列的个数与表定义是否一致。
+
+GAUSS-00995: "field position covers previous field"
+
+SQLSTATE: 22P04
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-00998: "%s"
+
+SQLSTATE: 42000
+
+错误原因: 语法错误。
+
+解决办法: 检查sql语句的语法是否正确。
+
+GAUSS-01000: "type '%s' already exists"
+
+SQLSTATE: 42710
+
+错误原因: 数据类型已存在。
+
+解决办法: 检查pg_type系统表，查看此类型是否已存在。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/11-GAUSS-01001-GAUSS-01100.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/11-GAUSS-01001-GAUSS-01100.md
new file mode 100644
index 0000000000000000000000000000000000000000..a431ddddf0e484e3a3c5fe4ad3db5790d4da0859
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/11-GAUSS-01001-GAUSS-01100.md
@@ -0,0 +1,812 @@
+---
+title: GAUSS-01001 - GAUSS-01100
+summary: GAUSS-01001 - GAUSS-01100
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-01001 - GAUSS-01100
+
+<br/>
+
+## GAUSS-01001 - GAUSS-01010
+
+<br/>
+
+GAUSS-01001: "invalid type category '%s': must be simple ASCII"
+
+SQLSTATE: 22023
+
+错误原因: 非法的类型类别: 类别名必须是简单ASCII字符（ASCII值33-126）。
+
+解决办法: 确保使用简单ASCII字符（ACII值22-126）作为类型的类别名。
+
+GAUSS-01002: "array element type cannot be %s"
+
+SQLSTATE: 42804
+
+错误原因: 数组的元素类型不能是伪类型。
+
+解决办法: 检查类型定义，请勿使用伪类型作为数组元素类型。
+
+GAUSS-01003: "alignment '%s' not recognized"
+
+SQLSTATE: 22023
+
+错误原因: 对齐参数不合法。
+
+解决办法: 检查数据类型定义中的对齐参数，确保其是合法的参数。
+
+GAUSS-01004: "storage '%s' not recognized"
+
+SQLSTATE: 22023
+
+错误原因: 存储参数不合法。
+
+解决办法: 检查数据类型定义中的存储参数，确保其是合法的。
+
+GAUSS-01005: "type input function must be specified"
+
+SQLSTATE: 42P17
+
+错误原因: 没有指定数据类型的input函数。
+
+解决办法: 检查数据类型定义语句，确保制定了input函数。
+
+GAUSS-01006: "type output function must be specified"
+
+SQLSTATE: 42P17
+
+错误原因: 没有指定数据类型的output函数。
+
+解决办法: 检查数据类型定义语句，确保制定了output函数。
+
+GAUSS-01007: "type modifier output function is useless without a type modifier input function"
+
+SQLSTATE: 42P17
+
+错误原因: 只指定类型的TYPMOD_OUT函数而不指定TYPMOD_IN函数是无效的。
+
+解决办法: 检查类型定义语句，确保在定义TYPMOD_OUT时同时定义了TYPMOD_IN函数。
+
+GAUSS-01008: "type input function %s must return type %s"
+
+SQLSTATE: 42P17
+
+错误原因: 类型的input函数没有返回指定的类型。
+
+解决办法: 检查类型定义语句，确保input函数返回指定的类型。
+
+GAUSS-01009: "type output function %s must return type 'cstring'"
+
+SQLSTATE: 42P17
+
+错误原因: 类型的output函数没有返回指定的类型。
+
+解决办法: 检查类型定义语句，确保output函数返回指定的类型。
+
+GAUSS-01010: "type receive function %s must return type %s"
+
+SQLSTATE: 42P17
+
+错误原因: 类型的receive函数没有返回指定的类型。
+
+解决办法: 检查类型定义语句，确保receive函数返回指定的类型。
+
+<br/>
+
+## GAUSS-01011 - GAUSS-01020
+
+<br/>
+
+GAUSS-01011: "type send function %s must return type 'bytea'"
+
+SQLSTATE: 42P17
+
+错误原因: 类型的send函数没有返回指定的类型。
+
+解决办法: 检查类型定义语句，确保send函数返回指定的类型。
+
+GAUSS-01012: "'%s' is not a valid base type for a domain"
+
+SQLSTATE: 42804
+
+错误原因: domain的基类型不合法。
+
+解决办法: 检查类型定义语句，确保domain的基类型是合法的（当前合法的是'b'，'d'，'e'，'r'）。
+
+GAUSS-01013: "multiple default expressions"
+
+SQLSTATE: 42601
+
+错误原因: 不能指定多个默认表达式。
+
+解决办法: 检查SQL语句，确保没有定义多个默认表达式。
+
+GAUSS-01014: "conflicting NULL/NOT NULL constraints"
+
+SQLSTATE: 42601
+
+错误原因: NULL/NOT NULL约束冲突。
+
+解决办法: 检查SQL语句，确保NULL/NOTNULL约束没有冲突。
+
+GAUSS-01015: "CHECK constraints for domains cannot be marked NO INHERIT"
+
+SQLSTATE: 42P17
+
+错误原因: domain的CHECK约束不能指定为NO INHERIT。
+
+解决办法: 检查SQL语句，确保domain的CHECK约束不指定NO INHERIT属性。
+
+GAUSS-01016: "unique constraints not possible for domains"
+
+SQLSTATE: 42000
+
+错误原因: "unique constraints are not allowed for domain defination.Domain定义中不允许有唯一性约束"。
+
+解决办法: 检查domain定义语句，确保其中没有唯一性约束。
+
+GAUSS-01017: "primary key constraints not possible for domains"
+
+SQLSTATE: 42601
+
+错误原因: Domain定义中不允许有主键约束。
+
+解决办法: 检查domain定义语句，确保其中没有主键约束。
+
+GAUSS-01018: "exclusion constraints not possible for domains"
+
+SQLSTATE: 42601
+
+错误原因: Domain定义中不允许有排他性约束。
+
+解决办法: 检查domain定义语句，确保其中没有排他性约束。
+
+GAUSS-01019: "foreign key constraints not possible for domains"
+
+SQLSTATE: 42601
+
+错误原因: Domain定义中不允许有外键约束。
+
+解决办法: 检查domain定义语句，确保其中没有外键约束。
+
+GAUSS-01020: "specifying constraint deferrability not supported for domains"
+
+SQLSTATE: 0A000
+
+错误原因: domain不支持指定约束的deferrability属性。
+
+解决办法: 检查domain定义语句，删除约束的deferrability属性。
+
+<br/>
+
+## GAUSS-01021 - GAUSS-01030
+
+<br/>
+
+GAUSS-01021: "unrecognized constraint subtype: %d"
+
+SQLSTATE: XX000
+
+错误原因: constraint的类型非法。
+
+解决办法: 请检查SQL语句中定义的约束类型是否正确。
+
+GAUSS-01022: "%s is not an enum"
+
+SQLSTATE: 42809
+
+错误原因: 此对象不是一个枚举。
+
+解决办法: 检查SQL语句，确保操作对象是一个枚举。
+
+GAUSS-01024: "type attribute 'subtype' is required"
+
+SQLSTATE: 42601
+
+错误原因: 没有指定类型的"subtype"属性。
+
+解决办法: 检查sql语句，添加subtype。
+
+GAUSS-01025: "range subtype cannot be %s"
+
+SQLSTATE: 42804
+
+错误原因: 不能是伪类型。
+
+解决办法: 检查sql语句，确保range subtype不是伪类型。
+
+GAUSS-01026: "range collation specified but subtype does not support collation"
+
+SQLSTATE: 42809
+
+错误原因: 指定了range collation但是subtype不支持collation。
+
+解决办法: 检查sql语句，如指定了collation,则subtype必须支持collation.。
+
+GAUSS-01027: "typmod_in function %s must return type 'integer'"
+
+SQLSTATE: 42P17
+
+错误原因: typmod_in函数必须返回integer类型。
+
+解决办法: 检查tymod_in函数，确保返回类型是integer类型。
+
+GAUSS-01028: "typmod_out function %s must return type 'cstring'"
+
+SQLSTATE: 42P17
+
+错误原因: typmod_out函数必须返回cstring类型。
+
+解决办法: 检查tymod_out函数，确保返回类型是cstring类型。
+
+GAUSS-01029: "type analyze function %s must return type 'Boolean'"
+
+SQLSTATE: 42P17
+
+错误原因: 类型的analyze函数必须返回Boolean类型。
+
+解决办法: 检查analyze函数，确保返回类型是Boolean类型的。
+
+GAUSS-01030: "operator class '%s' does not accept data type %s"
+
+SQLSTATE: 42804
+
+错误原因: operator class不支持此数据类型。
+
+解决办法: 检查sql语句，确保subtype类型和operator class相匹配。
+
+<br/>
+
+## GAUSS-01031 - GAUSS-01040
+
+<br/>
+
+GAUSS-01031: "data type %s has no default operator class for access method '%s'"
+
+SQLSTATE: 42704
+
+错误原因: 黑名单已禁用。
+
+解决办法: 禁止使用此语法。
+
+GAUSS-01032: "range canonical function %s must return range type"
+
+SQLSTATE: 42P17
+
+错误原因: 黑名单已禁用。
+
+解决办法: 禁止使用此语法。
+
+GAUSS-01033: "range canonical function %s must be immutable"
+
+SQLSTATE: 42P17
+
+错误原因: 黑名单已禁用。
+
+解决办法: 禁止使用此语法。
+
+GAUSS-01034: "range subtype diff function %s must return type double precision"
+
+SQLSTATE: 42P17
+
+错误原因: 黑名单已禁用。
+
+解决办法: 禁止使用此语法。
+
+GAUSS-01035: "range subtype diff function %s must be immutable"
+
+SQLSTATE: 42P17
+
+错误原因: 黑名单已禁用。
+
+解决办法: 禁止使用此语法。
+
+GAUSS-01036: "column '%s' of table '%s' contains null values"
+
+SQLSTATE: 23502
+
+错误原因: 黑名单已禁用。
+
+解决办法: 禁止使用此语法。
+
+GAUSS-01037: "constraint '%s' of domain '%s' does not exist"
+
+SQLSTATE: 42704
+
+错误原因: 黑名单已禁用。
+
+解决办法: 禁止使用此语法。
+
+GAUSS-01038: "constraint '%s' of domain '%s' is not a check constraint"
+
+SQLSTATE: 42809
+
+错误原因: 黑名单已禁用。
+
+解决办法: 禁止使用此语法。
+
+GAUSS-01039: "column '%s' of table '%s' contains values that violate the new constraint"
+
+SQLSTATE: 23514
+
+错误原因: 黑名单已禁用。
+
+解决办法: 禁止使用此语法。
+
+GAUSS-01040: "%s is not a domain"
+
+SQLSTATE: 42809
+
+错误原因: 黑名单已禁用。
+
+解决办法: 禁止使用此语法。
+
+<br/>
+
+## GAUSS-01041 - GAUSS-01050
+
+<br/>
+
+GAUSS-01041: "constraint '%s' for domain '%s' already exists"
+
+SQLSTATE: 42710
+
+错误原因: 黑名单已禁用。
+
+解决办法: 黑名单已禁用。
+
+GAUSS-01042: "cannot use table references in domain check constraint"
+
+SQLSTATE: 42P10
+
+错误原因: 黑名单已禁用。
+
+解决办法: 黑名单已禁用。
+
+GAUSS-01043: "cannot use subquery in check constraint"
+
+SQLSTATE: 0A000
+
+错误原因: 黑名单已禁用。
+
+解决办法: 黑名单已禁用。
+
+GAUSS-01044: "cannot use aggregate function in check constraint"
+
+SQLSTATE: 42803
+
+错误原因: 黑名单已禁用。
+
+解决办法: 黑名单已禁用。
+
+GAUSS-01045: "cannot use window function in check constraint"
+
+SQLSTATE: 42P20
+
+错误原因: 黑名单已禁用。
+
+解决办法: 黑名单已禁用。
+
+GAUSS-01046: "domain '%s' constraint '%s' has NULL conbin"
+
+SQLSTATE: XX000
+
+错误原因: 约束属性为空。
+
+解决办法: 系统表异常，请联系技术支持工程师提供技术支持。
+
+GAUSS-01047: "'%s' is not a domain"
+
+SQLSTATE: 42809
+
+错误原因: 此对象不是一个类型。
+
+解决办法: 检查SQL语句，确保要处理的对象是一个类型。
+
+GAUSS-01048: "%s is a table's row type"
+
+SQLSTATE: 42809
+
+错误原因: 此对象是一个表的行类型，不能使用ALTER TYPE语法。
+
+解决办法: 使用ALTER TABLE语法来替代。
+
+GAUSS-01049: "cannot alter array type %s"
+
+SQLSTATE: 42809
+
+错误原因: 不能修改数组类型。
+
+解决办法: 可以修改数组的元素类型，这样能自动修改这个数组的类型。
+
+GAUSS-01050: "type '%s' already exists in schema '%s'"
+
+SQLSTATE: 42710
+
+错误原因: 类型在指定模式中已经存在。
+
+解决办法: 检查此模式中的对象，看是否已存在此类型。
+
+<br/>
+
+## GAUSS-01051 - GAUSS-01060
+
+<br/>
+
+GAUSS-01051: "failed to change schema dependency for type %s"
+
+SQLSTATE: XX000
+
+错误原因: 更改类型的模式依赖未成功。
+
+解决办法: 系统表异常，请联系技术支持工程师提供技术支持。
+
+GAUSS-01052: "channel name cannot be empty"
+
+SQLSTATE: 22023
+
+错误原因: 管道名为空。
+
+解决办法: 检查sql语句，给定管道名。
+
+GAUSS-01053: "channel name too long"
+
+SQLSTATE: 22023
+
+错误原因: 管道名超出长度限制。
+
+解决办法: 检查sql语句，确保管道名长度符合要求。
+
+GAUSS-01054: "payload string too long"
+
+SQLSTATE: 22023
+
+错误原因: payload字符串超出长度限制。
+
+解决办法: 检查sql语句，确保payload字符串长度符合要求。
+
+GAUSS-01055: "cannot PREPARE a transaction that has executed LISTEN, UNLISTEN, or NOTIFY"
+
+SQLSTATE: 0A000
+
+错误原因: 不允许Prepare一个执行过LISTEN，UNLISTEN或NOTIFY操作的事务。
+
+解决办法: 检查sql语句，确保要prepare的事务没有执行过LISTEN，UNLISTEN或NOTIFY操作。
+
+GAUSS-01056: "too many notifications in the NOTIFY queue"
+
+SQLSTATE: 54000
+
+错误原因: 通知队列里的通知太多。
+
+解决办法: 重试失败的语句。
+
+GAUSS-01057: "unexpected rewrite result for CREATE TABLE AS SELECT"
+
+SQLSTATE: XX000
+
+错误原因: CREATE TABLE AS SELECT重写结果错误。
+
+解决办法: 重写结果应该只有一个语句，请尝试简化CREATE TABLE AS后的SELECT语句。
+
+GAUSS-01058: "no collation was derived for column '%s' with collatable type %s"
+
+SQLSTATE: 42P22
+
+错误原因: 属性列支持attcollation但是对应的attcollation无效，导致无法正常创建heap表格。
+
+解决办法: 检查创建表格时属性列关于collation定义的有效性。
+
+GAUSS-01059: "CREATE TABLE AS specifies too many column names"
+
+SQLSTATE: 42601
+
+错误原因: CREATE TABLE AS指定的列太多。
+
+解决办法: 检查sql语句，确保指定的列数相匹配。
+
+GAUSS-01060: "option '%s' not found"
+
+SQLSTATE: 42704
+
+错误原因: 选项未找到。
+
+解决办法: 检查sql语句，确保指定了相应选项。
+
+<br/>
+
+## GAUSS-01061 - GAUSS-01070
+
+<br/>
+
+GAUSS-01061: "option '%s' provided more than once"
+
+SQLSTATE: 42710
+
+错误原因: 选项出现了多次。
+
+解决办法: 检查sql语句，确保一个选项只出现一次。
+
+GAUSS-01062: "unrecognized action %d on option '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 对应选项的action设置非法。
+
+解决办法: 请检查相应的SQL语句选项参数是否正确。
+
+GAUSS-01063: "foreign-data wrapper '%s' does not exist"
+
+SQLSTATE: 42704
+
+错误原因: foreign-data wrapper不存在。
+
+解决办法: 检查是否已经创建了对应的foreign-data wrapper。
+
+GAUSS-01064: "foreign-data wrapper '%s' already exists"
+
+SQLSTATE: 42710
+
+错误原因: foreign-data wrapper已存在。
+
+解决办法: 对应的foreign-data wrapper已存在，无需创建。
+
+GAUSS-01065: "server '%s' does not exist"
+
+SQLSTATE: 42704
+
+错误原因: server不存在。
+
+解决办法: 检查是否已经创建了对应的server。
+
+GAUSS-01066: "server '%s' already exists"
+
+SQLSTATE: 42710
+
+错误原因: server已存在。
+
+解决办法: 对应的server已存在，无需创建。
+
+GAUSS-01067: "permission denied to change owner of foreign-data wrapper '%s'"
+
+SQLSTATE: 42501
+
+错误原因: 没有权限来修改foreign-data wrapper的所有者。
+
+解决办法: 使用系统管理员帐户来修改foreign-data wrapper的所有者。
+
+GAUSS-01068: "foreign-data wrapper with OID %u does not exist"
+
+SQLSTATE: 42704
+
+错误原因: foreign-data wrapper不存在。
+
+解决办法: 检查是否已经创建了对应的foreign-data wrapper。
+
+GAUSS-01069: "foreign server with OID %u does not exist"
+
+SQLSTATE: 42704
+
+错误原因:  foreign server不存在。
+
+解决办法: 检查是否已经创建了对应的foreign server。
+
+GAUSS-01070: "function %s must return type 'fdw_handler'"
+
+SQLSTATE: 42809
+
+错误原因: 函数必须返回"fdw_handler"类型。
+
+解决办法: 检查函数定义，确保函数返回"fdw_handler"类型。
+
+<br/>
+
+## GAUSS-01071 - GAUSS-01080
+
+<br/>
+
+GAUSS-01071: "permission denied to create foreign-data wrapper '%s'"
+
+SQLSTATE: 42501
+
+错误原因: 创建foreign-data wrapper时权限不足。
+
+解决办法: 使用系统管理员帐户来创建foreign-data wrapper。
+
+GAUSS-01072: "permission denied to alter foreign-data wrapper '%s'"
+
+SQLSTATE: 42501
+
+错误原因: 修改foreign-data wrapper时权限不足。
+
+解决办法: 使用系统管理员帐户来修改foreign-data wrapper。
+
+GAUSS-01073: "cache lookup failed for foreign-data wrapper %u"
+
+SQLSTATE: XX000
+
+错误原因: 无法找到对应的foreign data wrapper。
+
+解决办法: 请检查使用中的gds、hdfs外表以及roach、obs设置是否正确。
+
+GAUSS-01074: "cache lookup failed for foreign server %u"
+
+SQLSTATE: XX000
+
+错误原因: 无法找到对应的foreign data wrapper。
+
+解决办法: 请检查使用中的gds、hdfs外表以及roach、obs设置是否正确。
+
+GAUSS-01075: "user mapping '%s' already exists for server %s"
+
+SQLSTATE: 42710
+
+错误原因: server的user mapping已存在。
+
+解决办法: server的user mapping已存在，无需创建。
+
+GAUSS-01076: "user mapping '%s' does not exist for the server"
+
+SQLSTATE: 42704
+
+错误原因: server的user mapping不存在。
+
+解决办法: server的user mapping不存在，请确保使用前创建了user mapping。
+
+GAUSS-01077: "cache lookup failed for user mapping %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-01081 - GAUSS-01090
+
+<br/>
+
+GAUSS-01083: "get search path failed"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01084: "get namespace failed"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01086: "unacceptable schema name '%s'"
+
+SQLSTATE: 42939
+
+错误原因: 模式名非法。
+
+解决办法: pg_前缀的名称是系统保留的，不可使用。
+
+GAUSS-01087: "cache lookup failed for namespace %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01088: "schema '%s' does not exist"
+
+SQLSTATE: 3F000
+
+错误原因: 模式不存在。
+
+解决办法: 使用模式前确保其已存在。
+
+GAUSS-01089: "schema '%s' already exists"
+
+SQLSTATE: 42P06
+
+错误原因: 模式已存在。
+
+解决办法: 模式已存在，无需创建。
+
+GAUSS-01090: "cache lookup failed for schema %u"
+
+SQLSTATE: XX000
+
+错误原因: 模式查找失败。
+
+解决办法: 系统表异常，请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-01091 - GAUSS-01100
+
+<br/>
+
+GAUSS-01091: "cstore.%s is a internal table"
+
+SQLSTATE: XX000
+
+错误原因: cstore.开头的表是内部表，不允许VACUUM。
+
+解决办法: 不VACUUM内部表。
+
+GAUSS-01092: "pg_class entry for relid %u vanished during vacuuming"
+
+SQLSTATE: XX000
+
+错误原因: VACUUM结束后，查找对应表对象失败。
+
+解决办法: 系统表异常，请联系技术支持工程师提供技术支持。
+
+GAUSS-01093: "could not find tuple for database %u"
+
+SQLSTATE: XX000
+
+错误原因: 数据库对象查找失败。
+
+解决办法: 系统表异常，请联系技术支持工程师提供技术支持。
+
+GAUSS-01094: "pg_partition entry for partid %u vanished during vacuuming"
+
+SQLSTATE: XX000
+
+错误原因: VACUUM结束后，查找对应分区对象失败。
+
+解决办法: 系统表异常，请联系技术支持工程师提供技术支持。
+
+GAUSS-01095: "unexpected relkind!"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01096: "%s requires a parameter"
+
+SQLSTATE: 42601
+
+错误原因: 缺少参数。
+
+解决办法: 检查sql语句参数个数。
+
+GAUSS-01097: "%s requires a numeric value"
+
+SQLSTATE: 42601
+
+错误原因: 需要一个数字类型的参数，但语句中给的参数不是。
+
+解决办法: 检查SQL语句，给出正确的参数。
+
+GAUSS-01098: "%s requires a Boolean value"
+
+SQLSTATE: 42601
+
+错误原因: 需要一个布尔类型的参数，但语句中给的参数不是。
+
+解决办法: 检查SQL语句，给出正确的参数。
+
+GAUSS-01099: "argument of %s must be a name"
+
+SQLSTATE: 42601
+
+错误原因: 参数命名必须符合规范。
+
+解决办法: 检查参数，修改参数值。
+
+GAUSS-01100: "argument of %s must be a type name"
+
+SQLSTATE: 42601
+
+错误原因: 参数必须是一个类型名。
+
+解决办法: 检查参数，使用类型名作为参数值。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/12-GAUSS-01101-GAUSS-01200.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/12-GAUSS-01101-GAUSS-01200.md
new file mode 100644
index 0000000000000000000000000000000000000000..422088e71d518e566370ac2092c279a25b65160e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/12-GAUSS-01101-GAUSS-01200.md
@@ -0,0 +1,772 @@
+---
+title: GAUSS-01101 - GAUSS-01200
+summary: GAUSS-01101 - GAUSS-01200
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-01101 - GAUSS-01200
+
+<br/>
+
+## GAUSS-01101 - GAUSS-01110
+
+<br/>
+
+GAUSS-01101: "%s requires an integer value"
+
+SQLSTATE: 42601
+
+错误原因: 需要一个integer类型的参数，但语句中给的参数不是。
+
+解决办法: 检查SQL语句，给出正确的参数。
+
+GAUSS-01102: "invalid argument for %s: '%s'"
+
+SQLSTATE: 42601
+
+错误原因: 参数不合法。
+
+解决办法: 检查SQL语句，给出正确的参数。
+
+GAUSS-01103: "table is not partitioned"
+
+SQLSTATE: 0A000
+
+错误原因: 要cluster表分区，但该表不是分区表。
+
+解决办法: 检查表名，对普通表不能cluster分区。
+
+GAUSS-01104: "cannot cluster temporary tables of other sessions"
+
+SQLSTATE: 0A000
+
+错误原因: 不能cluster其他session创建的临时表。
+
+解决办法: 检查要cluster的表，不能CLUSTER其他session创建的临时表。
+
+GAUSS-01105: "there is no previously clustered index for table '%s'"
+
+SQLSTATE: 42704
+
+错误原因: 没有指定索引名称，该表之前也未做过cluster，因此无法确定以那个索引来做cluster。
+
+解决办法: 如果不指定cluster的索引名称，就必须保证该表之前做过cluster，系统使用上次cluster的索引。否则，需要指明要做cluster的索引名称。
+
+GAUSS-01106: "cannot cluster a shared catalog"
+
+SQLSTATE: 0A000
+
+错误原因: 不能对一个多数据库间共享的系统表做cluster操作。
+
+解决办法: 请勿对共享的系统表做cluster操作。
+
+GAUSS-01107: "cannot vacuum temporary tables of other sessions"
+
+SQLSTATE: 0A000
+
+错误原因: 不能VACUUM其他session创建的临时表。
+
+解决办法: 检查要VACUUM的表，不能VACUUM其他session创建的临时表。
+
+GAUSS-01108: "'%s' is not an index for table '%s'"
+
+SQLSTATE: 42809
+
+错误原因: 此索引不是这个表的索引，因此不能做cluster。
+
+解决办法: 检查SQL语句中索引和对应的表是否匹配。
+
+GAUSS-01109: "cannot cluster on index '%s' because access method does not support clustering"
+
+SQLSTATE: 0A000
+
+错误原因: 不能对此索引做cluster，此索引类型不支持cluster。
+
+解决办法: 请勿对此类型的索引做cluster，此索引类型不支持cluster。
+
+GAUSS-01110: "cannot cluster on partial index '%s'"
+
+SQLSTATE: 0A000
+
+错误原因: 不能对部分索引(partial index)做cluster。
+
+解决办法: 请勿对部分索引(partial index)做cluster。
+
+<br/>
+
+## GAUSS-01111 - GAUSS-01120
+
+<br/>
+
+GAUSS-01111: "cannot cluster on invalid index '%s'"
+
+SQLSTATE: 0A000
+
+错误原因: 指定的索引是CREATE INDEX CONCURRENTLY失败后遗留的无效索引，不能对无效索引做cluster。
+
+解决办法: 请勿对无效索引做cluster。
+
+GAUSS-01112: "cannot cluster on invalid index %u"
+
+SQLSTATE: XX000
+
+错误原因: 对应index非法，不能进行cluster操作。
+
+解决办法: 系统表异常，请联系技术支持工程师提供技术支持。
+
+GAUSS-01113: "CLUSTER does not support lossy index conditions"
+
+SQLSTATE: XX000
+
+错误原因: CLUSTER不支持lossy索引条件。
+
+解决办法: 请检查CLUTER表建立的索引，hash索引和gist索引不支持。
+
+GAUSS-01114: "unexpected HeapTupleSatisfiesVacuum result"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01115: "can not cluster partition %s using %s bacause of unusable local index"
+
+SQLSTATE: XX000
+
+错误原因: 聚簇的分区表不能使用本地索引，因为本地索引不可用。
+
+解决办法: 重建分区表。
+
+GAUSS-01117: "cannot swap mapped relation '%s' with non-mapped relation"
+
+SQLSTATE: XX000
+
+错误原因: 在扩容重分过程中，通过gs_switch_relfilenode函数交换两张表的物理文件时，由于表1的物理存储文件无效，不能交换当前表的物理文件。
+
+解决办法: 1、确认gs_switch_relfilenode函数第一个参数中表1的物理文件是否有效；2、删除表1，通过create table语法重新创建表，重建当前表的物理文件
+
+GAUSS-01118: "cannot change tablespace of mapped relation '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 在扩容重分过程中，通过gs_switch_relfilenode函数交换两张表的物理文件时，两张表的tablespace不一致，不能交换两张表的tablespace。
+
+解决办法: 删除当前表，通过create tablespace重新创建tablespace，通过语法create table语法重新创建表。
+
+GAUSS-01119: "cannot swap toast by links for mapped relation '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 在扩容重分过程中，通过gs_switch_relfilenode函数交换两张表的物理文件时，待交换两张表中其中有一张表的toast表为空，不能交换两张表的物理文件。
+
+解决办法: 删除当前表，通过create table语法重新创建表，重建当前表的物理文件。
+
+GAUSS-01120: "could not find relation mapping for relation '%s', OID %u"
+
+SQLSTATE: XX000
+
+错误原因: 在扩容充分过程中，通过gs_switch_relfilenode函数交换两张表的物理文件时，由于表1的物理存储文件无效，不能交换当前表的物理文件。
+
+解决办法: 1、确认gs_switch_relfilenode函数第一个参数中表1的物理文件是否有效；2、删除表1，通过create table语法重新创建表，重建当前表的物理文件。
+
+<br/>
+
+## GAUSS-01121 - GAUSS-01130
+
+<br/>
+
+GAUSS-01121: "cannot swap toast files by content when there's only one"
+
+SQLSTATE: XX000
+
+错误原因: 在扩容重分过程中，通过gs_switch_relfilenode函数交换两张表的物理文件时，待交换两张表中其中有一张表的toast表为空，不能交换两张表的物理文件。
+
+解决办法: 删除当前表，通过create table语法重新创建表，重建当前表的物理文件。
+
+GAUSS-01122: "cannot swap toast files by links for system catalogs"
+
+SQLSTATE: XX000
+
+错误原因: 在扩容重分过程中，通过gs_switch_relfilenode函数交换两张表的物理文件时，不允许交换系统表的toast物理文件。
+
+解决办法: 在扩容重分过程中，通过gs_switch_relfilenode函数不允许交换系统表的物理文件，非法的操作。请确认函数的参数中是否包含有系统表的表名。
+
+GAUSS-01123: "expected one dependency record for TOAST table, found %ld"
+
+SQLSTATE: XX000
+
+错误原因: 在扩容重分过程中，通过gs_switch_relfilenode函数交换两张表的物理文件时，由于toast表依赖的对象数大于1个，导致交换物理文件失败。
+
+解决办法: 确认toast表在pg_depend表中依赖的对象数大于1个，如果大于1个请先删除对象的依赖后再调用该函数交换物理文件。
+
+GAUSS-01124: "expected none dependency record for partiton's TOAST table, found %ld"
+
+SQLSTATE: XX000
+
+错误原因: 重建分区表对分区文件进行交换操作处理时，如果待交换的表包含有toast表需要做toast表的文件交换。其中toast表有依赖对象，导致交换分区文件失败。
+
+解决办法: 对需要重建的分区表通过create table partition重新创建分区表。
+
+GAUSS-01125: "expected one dependency record for CUDesc/Delta table, found %ld"
+
+SQLSTATE: XX000
+
+错误原因: 在扩容重分过程中，通过gs_switch_relfilenode函数交换两张列存表的物理文件时，由于列存表依赖的对象数大于1个，导致交换物理文件失败。
+
+解决办法: 确认列存表在pg_depend表中依赖的对象数大于1个，如果大于1个请先删除对象的依赖后再调用该函数交换物理文件。
+
+GAUSS-01127: "invalid statement name: must not be empty"
+
+SQLSTATE: 42P14
+
+错误原因: 非法的语句名: 语句名不能为空。
+
+解决办法: 给出明确的语句名。
+
+GAUSS-01128: "could not determine data type of parameter $%d"
+
+SQLSTATE: 42P18
+
+错误原因: 参数类型无法确定。
+
+解决办法: 修改参数值为系统可识别的类型，系统可识别类型见zh-cn_topic_0237121926.html。
+
+GAUSS-01129: "utility statements cannot be prepared"
+
+SQLSTATE: 42P14
+
+错误原因: DDL命令不能使用prepare。
+
+解决办法: DDL语句无需prepare，直接执行即可。
+
+GAUSS-01130: "EXECUTE does not support variable-result cached plans"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-01131 - GAUSS-01140
+
+<br/>
+
+GAUSS-01131: "prepared statement is not a SELECT"
+
+SQLSTATE: 42809
+
+错误原因: CREATE TABLE AS EXECUTE语句中的prepared语句只能是select查询。
+
+解决办法: 修改SQL语句，CREATE TABLE AS EXECUTE语句中的prepared语句改为select语句。
+
+GAUSS-01132: "wrong number of parameters for prepared statement '%s'"
+
+SQLSTATE: 42601
+
+错误原因: Prepared语句所需参数与实际获得的参数数目不匹配。
+
+解决办法: 请检查EXECUTE语法中的参数个数和PREPARE语法中创建预备语句参数个数是否一致，保证EXECUTE和PREPARE语法中参数个数的一致性，并重新调用PREPARE和EXECUTE语法执行。
+
+GAUSS-01136: "parameter $%d of type %s cannot be coerced to the expected type %s"
+
+SQLSTATE: 42804
+
+错误原因: Prepared语句中参数类型无法转化为期待的参数类型。
+
+解决办法: 增加相应的类型转化或保证Prepared中的参数类型。
+
+GAUSS-01137: "Passing parameters in PREPARE statement is not supported"
+
+SQLSTATE: 0A000
+
+错误原因: Prepared语句不支持远程传递参数。
+
+解决办法: 请勿在Prepared语句中执行分布式传输参数的操作。
+
+GAUSS-01138: "prepared statement '%s' already exists"
+
+SQLSTATE: 42P05
+
+错误原因: Prepared语句已经存在。
+
+解决办法: 查看pg_prepared_statements中关于已有prepared语句的记录，请勿重复创建prepared语句。
+
+GAUSS-01139: "prepared statement '%s' does not exist"
+
+SQLSTATE: 26000
+
+错误原因: 执行了不存在的Prepared语句。
+
+解决办法: 查看pg_prepared_statements中是否有自己执行的prepared语句。
+
+GAUSS-01140: "EXPLAIN EXECUTE does not support variable-result cached plans"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-01141 - GAUSS-01150
+
+<br/>
+
+GAUSS-01141: "datanode statement '%s' does not exist"
+
+SQLSTATE: 26000
+
+错误原因: EXECUTE DIRECT语法中没有包含指定执行的DN信息。
+
+解决办法: 请检查EXECUTE DIRECT语法是否正确，并指定执行的DN信息。
+
+GAUSS-01142: "must be system admin to create procedural language '%s'"
+
+SQLSTATE: 42501
+
+错误原因: 需要管理员用户才能创建存储过程语言。
+
+解决办法: 检查创建存储过程语言的用户是否是管理员用户。
+
+GAUSS-01143: "function %s must return type 'language_handler'"
+
+SQLSTATE: 42809
+
+错误原因: 存储过程语言返回值类型错误。
+
+解决办法: 请修改当前创建的存储过程语言为language_handler类型。
+
+GAUSS-01144: "unsupported language '%s'"
+
+SQLSTATE: 42704
+
+错误原因: 不支持的存储过程语言。
+
+解决办法: 查看pg_pltemplate检查所使用语言是否在列表汇中。
+
+GAUSS-01145: "must be system admin to create custom procedural language"
+
+SQLSTATE: 42501
+
+错误原因: 需要管理员用户才能创建存储过程语言。
+
+解决办法: 检查创建存储过程语言的用户是否是管理员用户。
+
+GAUSS-01146: "language '%s' already exists"
+
+SQLSTATE: 42710
+
+错误原因: 已存在的语言类型。
+
+解决办法: 查看pg_language检查是否创建了重复的语言类型。
+
+GAUSS-01147: "cache lookup failed for language %u"
+
+SQLSTATE: 22P06
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01148: "COPY BINARY is not supported to stdout or from stdin"
+
+SQLSTATE: 0A000
+
+错误原因: 不支持copy二进制数据类型到标准输入中的输出界面。
+
+解决办法: 请勿进行copy二进制数据类型到标准输入中的输出界面的操作。
+
+GAUSS-01149: "could not write to COPY file: %m"
+
+SQLSTATE: XX000
+
+错误原因: 无法copy数据到指定文件。
+
+解决办法: 检查指定文件是否有权限异常问题。
+
+GAUSS-01150: "connection lost during COPY to stdout"
+
+SQLSTATE: 08006
+
+错误原因: copy操作过程，连接丢失。
+
+解决办法: 检查客户端与服务器端连接线程是否正常。
+
+<br/>
+
+## GAUSS-01151 - GAUSS-01160
+
+<br/>
+
+GAUSS-01151: "COPY_FILE_SEGMENT does not implement in CopySendEndOfRow"
+
+SQLSTATE: XX000
+
+错误原因: Copy to指定的目标数据源不支持。
+
+解决办法: 请修改Copy to指定的目标数据源。
+
+GAUSS-01152: "COPY_GDS does not implement in CopySendEndOfRow"
+
+SQLSTATE: XX000
+
+错误原因: Copy to指定的目标数据源不支持。
+
+解决办法: 请修改Copy to指定的目标数据源。
+
+GAUSS-01153: "could not read from COPY file: %m"
+
+SQLSTATE: XX000
+
+错误原因: 无法读取指定copy文件中的数据。
+
+解决办法: 请检查指定文件是否被破坏或权限是否足够。
+
+GAUSS-01154: "unexpected EOF on client connection with an open transaction"
+
+SQLSTATE: 08006
+
+错误原因: 拷贝数据到标准输入时，发生连接故障。
+
+解决办法: 请检查客户端与服务器端连接线程是否正常。
+
+GAUSS-01155: "COPY from stdin failed: %s"
+
+SQLSTATE: 57014
+
+错误原因: 从标准输入中拷贝数据失败。
+
+解决办法: 请检查客户端与服务器端连接线程是否正常。
+
+GAUSS-01156: "unexpected message type 0x%02X during COPY from stdin"
+
+SQLSTATE: 08P01
+
+错误原因: 从标准输入中拷贝的数据类型有问题。
+
+解决办法: 请检查标准输入中的数据类型格式是否正确。
+
+GAUSS-01157: "COPY_BUFFER not allowed in this context"
+
+SQLSTATE: XX000
+
+错误原因: Copy to指定的目标数据源不支持。
+
+解决办法: 请修改Copy to指定的目标数据源。
+
+GAUSS-01158: "unimplemented CopyDest mode"
+
+SQLSTATE: XX000
+
+错误原因: Copy to指定的目标数据源不支持。
+
+解决办法: 请修改Copy to指定的目标数据源。
+
+GAUSS-01159: "must be system admin to COPY to or from a file"
+
+SQLSTATE: 42501
+
+错误原因: 必须是管理员用户才能进行对于文件的copy操作。
+
+解决办法: 检查执行文件copy操作的用户是否具有管理员权限。
+
+GAUSS-01160: "position of field '%s' can not be less then 0"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-01161 - GAUSS-01170
+
+<br/>
+
+GAUSS-01161: "length of field '%s' can not be less then 0"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01162: "max length of data row cannot greater than 1GB"
+
+SQLSTATE: 42601
+
+错误原因: 数据行不能大于1GB。
+
+解决办法: 检查行数据大小是否超过1GB。
+
+GAUSS-01163: "max length of data row cannot greater than 1GB"
+
+SQLSTATE: 42601
+
+错误原因: 数据行不能大于1GB。
+
+解决办法: 检查行数据大小是否超过1GB。
+
+GAUSS-01164: "pre-field '%s' can not be covered by field '%s'"
+
+SQLSTATE: 42601
+
+错误原因: 数据区域不能被覆盖。
+
+解决办法: 检查行数据大小是否超过指定值导致数据覆盖。
+
+GAUSS-01165: "default conversion function for encoding '%s' to '%s' does not exist"
+
+SQLSTATE: 42883
+
+错误原因: Copy操作指定的编码格式和数据库编码之间无默认转换函数。
+
+解决办法: 请修改Copy操作指定的编码格式。
+
+GAUSS-01166: "invalid user-define header file '%s'"
+
+SQLSTATE: XX000
+
+错误原因: Copy操作中遇到非法的用户自定义头文件。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01167: "no data in user-define header file '%s'"
+
+SQLSTATE: XX000
+
+错误原因: Copy操作中遇到非法的用户自定义头文件。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01168: "user-define header should not longger than 1MB"
+
+SQLSTATE: XX000
+
+错误原因: Copy操作中遇到非法的用户自定义头文件。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01169: "COPY format '%s' not recognized"
+
+SQLSTATE: 22023
+
+错误原因: copy的数据文件格式不支持。
+
+解决办法: 检查数据文件格式是否正确。
+
+GAUSS-01170: "null value string is too long"
+
+SQLSTATE: 22023
+
+错误原因: copy数据中使用了过长的空字符串。
+
+解决办法: copy数据中不能使用超过100个的空字符串。
+
+<br/>
+
+## GAUSS-01171 - GAUSS-01180
+
+<br/>
+
+GAUSS-01171: "argument to option '%s' must be a list of column names"
+
+SQLSTATE: 22023
+
+错误原因: 参数选项必须是列名之一。
+
+解决办法: 检查copy中参数名是否为表列名。
+
+GAUSS-01172: "argument to option '%s' must be a valid encoding name"
+
+SQLSTATE: 22023
+
+错误原因: 参数选项必须是可用的编码名。
+
+解决办法: 检查copy中参数是否为已知编码类型。
+
+GAUSS-01174: "invalid value of FIX"
+
+SQLSTATE: 22023
+
+错误原因: 不识别copy中fix选项的值。
+
+解决办法: 检查copy参数fix是否正确。
+
+GAUSS-01175: "option '%s' not recognized"
+
+SQLSTATE: 42601
+
+错误原因:  不识别copy中某个选项的值。
+
+解决办法: 检查copy中该不识别的参数是否正确。
+
+GAUSS-01176: "cannot specify DELIMITER in BINARY/FIXED mode"
+
+SQLSTATE: 42601
+
+错误原因: 不能在BINARY/FIXED模式下指定分隔符。
+
+解决办法: 请勿在BINARY/FIXED模式下指定分隔符。
+
+GAUSS-01177: "cannot specify NULL in BINARY/FIXED mode"
+
+SQLSTATE: 42601
+
+错误原因: 不能在BINARY/FIXED模式下指定空字符。
+
+解决办法: 请勿在BINARY/FIXED模式下指定空字符。
+
+GAUSS-01178: "FORMATTER only can be specified in FIXED mode"
+
+SQLSTATE: 42601
+
+错误原因: 只能在FIXED模式下指定FORMATTER参数。
+
+解决办法: 请在FIXED模式下指定FORMATTER参数。
+
+GAUSS-01179: "FORMATTER must be specified in FIXED mode"
+
+SQLSTATE: 42601
+
+错误原因: FIXED模式下必须指定FORMATTER参数。
+
+解决办法: FIXED模式下必须指定FORMATTER参数。
+
+GAUSS-01180: "FIX only can be specified in FIXED mode"
+
+SQLSTATE: 42601
+
+错误原因: FIX只能在FIXED模式下指定。
+
+解决办法: FIX只能在FIXED模式下指定。
+
+<br/>
+
+## GAUSS-01181 - GAUSS-01190
+
+<br/>
+
+GAUSS-01181: "COPY delimiter must be less than %d bytes"
+
+SQLSTATE: 0A000
+
+错误原因: Copy操作指定的分隔符长度超限。
+
+解决办法: 请修改Copy操作指定的分隔符，长度控制在10字节以内。
+
+GAUSS-01182: "COPY delimiter cannot be newline or carriage return"
+
+SQLSTATE: 22023
+
+错误原因: COPY操作的分隔符不允许使用换行或回车。
+
+解决办法: COPY操作分隔符只能是水平制表符或逗号，具体请参考zh-cn_topic_0237122096.html。
+
+GAUSS-01183: "COPY null representation cannot use newline or carriage return"
+
+SQLSTATE: 22023
+
+错误原因: COPY空字符不允许使用换行或回车。
+
+解决办法: COPY空字符时请勿使用换行或回车。
+
+GAUSS-01184: "delimiter '%s' cannot contain any characters in'%s'"
+
+SQLSTATE: 22023
+
+错误原因: 导入非CSV格式时，指定的分隔符中包含了不允许的字符（a-z0-9以及.\\）。
+
+解决办法: 重新指定分隔符，不允许出现a-z0-9以及.\\中的任何一个字符。
+
+GAUSS-01185: "COPY HEADER available only in CSV mode"
+
+SQLSTATE: 0A000
+
+错误原因: COPY操作中的头行检测只支持CSV模式。
+
+解决办法: 请在CSV模式下支持头行检测。
+
+GAUSS-01186: "COPY quote available only in CSV mode"
+
+SQLSTATE: 0A000
+
+错误原因: COPY操作中的引用字符只支持CSV模式。
+
+解决办法: 请在CSV模式下使用引用字符。
+
+GAUSS-01188: "delimiter cannot contain quote character"
+
+SQLSTATE: 22023
+
+错误原因: 导入CSV格式时指定的分隔符中出现了引号字符。
+
+解决办法: 需要重新指定CSV格式的分隔符或者引号字符。
+
+GAUSS-01189: "COPY escape available only in CSV mode"
+
+SQLSTATE: 0A000
+
+错误原因: COPY操作中逃逸字符只支持CSV模式。
+
+解决办法: 请在CSV模式中使用逃逸字符。
+
+<br/>
+
+## GAUSS-01191 - GAUSS-01200
+
+<br/>
+
+GAUSS-01191: "COPY force quote available only in CSV mode"
+
+SQLSTATE: 0A000
+
+错误原因: COPY操作中强制引用字符只支持CSV模式。
+
+解决办法: 请在CSV模式中使用强制引用字符。
+
+GAUSS-01194: "COPY force not null only available using COPY FROM"
+
+SQLSTATE: 0A000
+
+错误原因: COPY操作中强制非空字符只支持COPY FROM操作。
+
+解决办法: 请使用COPY FROM语句实现强制非空字符。
+
+GAUSS-01195: "COPY delimiter must not appear in the NULL specification"
+
+SQLSTATE: 0A000
+
+错误原因: COPY操作中分隔符不能出现在空值列表中。
+
+解决办法: 请勿使用空值列表中的值作为分隔符。
+
+GAUSS-01197: "CSV quote character must not appear in the NULL specification"
+
+SQLSTATE: 0A000
+
+错误原因: COPY操作中引用字符不能出现在空值列表中。
+
+解决办法: 请勿使用空值列表中的值作为分隔符。
+
+GAUSS-01198: "SHARED mode can not be used with CSV format"
+
+SQLSTATE: 0A000
+
+错误原因: 不能在CSV格式支持共享模式。
+
+解决办法: 请勿在CSV格式场景使用共享模式。
+
+GAUSS-01199: "HEADER FILE only available using COPY TO or WRITE ONLY foreign table"
+
+SQLSTATE: 0A000
+
+错误原因: 头文件只能在copy to和只有外表的场景中使用。
+
+解决办法: 请在copy to或外表场景使用头文件。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/13-GAUSS-01201-GAUSS-01300.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/13-GAUSS-01201-GAUSS-01300.md
new file mode 100644
index 0000000000000000000000000000000000000000..1e8c3500feaca6e7cc53b201dc8664e2f52f709e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/13-GAUSS-01201-GAUSS-01300.md
@@ -0,0 +1,814 @@
+---
+title: GAUSS-01201 - GAUSS-01300
+summary: GAUSS-01201 - GAUSS-01300
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-01201 - GAUSS-01300
+
+<br/>
+
+## GAUSS-01201 - GAUSS-01210
+
+<br/>
+
+GAUSS-01201: "can not specify EOL in BINARY mode"
+
+SQLSTATE: 0A000
+
+错误原因: 不能在BINARY模式下指定终止符。
+
+解决办法: 请勿在BINARY模式下使用终止符。
+
+GAUSS-01202: "FIX specification only available using COPY FROM or READ ONLY foreign table"
+
+SQLSTATE: 42000
+
+错误原因: 指定FIX参数只能在copy from和只读外表的场景中使用。
+
+解决办法: 请在copy from或外表场景使用指定FIX参数的操作。
+
+GAUSS-01203: "FILEHEADER specification only available using HEAD"
+
+SQLSTATE: 42601
+
+错误原因: 用户在导出的时候指定从哪个文件来读取HEAD信息，但是并没有指定是否真正需要HEAD信息。
+
+解决办法: 在导出语句中明确指定HEADER项，或者去掉读取的文件名信息。
+
+GAUSS-01204: "table '%s' does not have OIDs"
+
+SQLSTATE: 42703
+
+错误原因: 导入数据时指定了文本中存在OID项，但是用户表并不存在OID列。
+
+解决办法: 检查要导入的数据是否与用户表的定义在OID上是否一致，要么删除导入的OID项，要么对用户表增加OID列。
+
+GAUSS-01206: "unexpected rewrite result"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。导入SQL语句的重写结果非预期。
+
+解决办法: 运行时错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-01207: "COPY (SELECT INTO) is not supported"
+
+SQLSTATE: 0A000
+
+错误原因: 不支持COPY中SELECT INTO语法。
+
+解决办法: COPY中不建议使用SELECT INTO语法。
+
+GAUSS-01208: "FORCE QUOTE column '%s' not referenced by COPY"
+
+SQLSTATE: 42P10
+
+错误原因: 在CSV COPY TO模式下，在每个声明的字段周围对所有非NULL值没有使用引号包围。
+
+解决办法: 在CSV COPY TO模式下，强制在每个声明的字段周围对所有非NULL值都使用引号包围。NULL输出不会被引号包围。
+
+GAUSS-01209: "FORCE NOT NULL column '%s' not referenced by COPY"
+
+SQLSTATE: 42P10
+
+错误原因: 在CSV COPY FROM模式下，指定的字段输入为空。
+
+解决办法: 在CSV COPY FROM模式下，指定的字段输入不能为空。
+
+GAUSS-01210: "could not close file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 无法关闭指定文件。
+
+解决办法: 检查指定文件是否被破坏或权限问题。
+
+<br/>
+
+## GAUSS-01211 - GAUSS-01220
+
+<br/>
+
+GAUSS-01211: "cannot copy from view '%s'"
+
+SQLSTATE: 42809
+
+错误原因: 无法从视图中COPY数据。
+
+解决办法: 请勿从视图中COPY数据。
+
+GAUSS-01212: "cannot copy from foreign table '%s'"
+
+SQLSTATE: 42809
+
+错误原因: 无法从外表中COPY数据。
+
+解决办法: 请勿从外表中COPY数据。
+
+GAUSS-01213: "cannot copy from sequence '%s'"
+
+SQLSTATE: 42809
+
+错误原因: 无法从序列中COPY数据。
+
+解决办法: 请勿从序列中COPY数据。
+
+GAUSS-01214: "cannot copy from non-table relation '%s'"
+
+SQLSTATE: 42809
+
+错误原因: 无法从非表关系中COPY数据。
+
+解决办法: 请勿从非表关系中COPY数据。
+
+GAUSS-01215: "relative path not allowed for COPY to file"
+
+SQLSTATE: 42602
+
+错误原因: COPY目的文件不能用相对路径格式。
+
+解决办法: COPY目的文件使用绝对路径格式。
+
+GAUSS-01216: "could not open file '%s' for writing: %m"
+
+SQLSTATE: XX000
+
+错误原因: 无法打开指定文件。
+
+解决办法: 请检查指定文件是否被破坏或权限问题。
+
+GAUSS-01217: "'%s' is a directory"
+
+SQLSTATE: 42809
+
+错误原因: 期望为文件的参数是目录。
+
+解决办法: 请指定COPY的文件名而非目录名。
+
+GAUSS-01218: "could not chmod file '%s' : %m"
+
+SQLSTATE: XX000
+
+错误原因: 无法给文件变更权限。
+
+解决办法: 请检查文件目前的权限及所属用户是否正常。
+
+GAUSS-01219: "Invalid file format"
+
+SQLSTATE: XX000
+
+错误原因: 不支持的文件格式。
+
+解决办法: 请使用COPY支持的文本、二进制、CSV格式。
+
+GAUSS-01220: "null value in column '%s' violates not-null constraint"
+
+SQLSTATE: 23502
+
+错误原因: 向有非空约束的列插入空值。
+
+解决办法: 修改与非空约束冲突的空值为有效值。
+
+<br/>
+
+## GAUSS-01221 - GAUSS-01230
+
+<br/>
+
+GAUSS-01221: "Column Store unsupport CHECK constraint"
+
+SQLSTATE: XX000
+
+错误原因: 当前列存不支持CHECK约束。
+
+解决办法: 删除CHECK约束。
+
+GAUSS-01222: "cannot copy to view '%s'"
+
+SQLSTATE: 42809
+
+错误原因: 无法COPY数据到视图。
+
+解决办法: 请勿COPY数据到视图中。
+
+GAUSS-01223: "cannot copy to foreign table '%s'"
+
+SQLSTATE: 42809
+
+错误原因: 无法COPY数据到外表。
+
+解决办法: 请勿COPY数据到外表中。
+
+GAUSS-01224: "cannot copy to sequence '%s'"
+
+SQLSTATE: 42809
+
+错误原因: 无法COPY数据到序列。
+
+解决办法: 请勿COPY数据到序列中。
+
+GAUSS-01225: "cannot copy to non-table relation '%s'"
+
+SQLSTATE: 42809
+
+错误原因: 无法COPY数据非正规表。
+
+解决办法: 请勿COPY数据非正规表中。
+
+GAUSS-01226: "invalid COPY file header (COPY SEND)"
+
+SQLSTATE: 22P04
+
+错误原因: 无效COPY操作文件头。
+
+解决办法: COPY数据文件被破坏，请检查文件。
+
+GAUSS-01227: "Copy failed on a Datanode"
+
+SQLSTATE: 08000
+
+错误原因: 导入数据失败。
+
+解决办法: 需要查看数据节点上的日志来找出发生的错误类型，视具体问题采用不同的措施。
+
+GAUSS-01228: "Missing data when batch insert compressed data !"
+
+SQLSTATE: XX000
+
+错误原因: 向行存表导入压缩数据的过程中，出现了数据丢失的现象。
+
+解决办法: 使用alter table关闭行存表的压缩特性，重新导入数据。
+
+GAUSS-01229: "Non-shippable ROW triggers not supported with COPY"
+
+SQLSTATE: 0A000
+
+错误原因: COPY操作不支持行触发器。
+
+解决办法: 请勿在COPY中使用行触发器。
+
+GAUSS-01230: "could not open file '%s' for reading: %m"
+
+SQLSTATE: XX000
+
+错误原因: 打开文件失败。
+
+解决办法: 通过错误码，检查文件打开失败的原因并进行修正（不存在，无权限，磁盘空间满等）。
+
+<br/>
+
+## GAUSS-01231 - GAUSS-01240
+
+<br/>
+
+GAUSS-01231: "COPY file signature not recognized"
+
+SQLSTATE: 22P04
+
+错误原因: COPY数据文件签名无法识别。
+
+解决办法: COPY数据文件被破坏，请检查文件。
+
+GAUSS-01232: "invalid COPY file header (missing flags)"
+
+SQLSTATE: 22P04
+
+错误原因: COPY数据丢失文件头。
+
+解决办法: COPY数据文件被破坏，请检查文件。
+
+GAUSS-01233: "unrecognized critical flags in COPY file header"
+
+SQLSTATE: 22P04
+
+错误原因: COPY数据文件头无法识别。
+
+解决办法: COPY数据文件被破坏，请检查文件。
+
+GAUSS-01236: "missing data for OID column"
+
+SQLSTATE: 22P04
+
+错误原因: copy时OID为空值。
+
+解决办法: 检查数据文件首列是否有空值。
+
+GAUSS-01237: "null OID in COPY data"
+
+SQLSTATE: 22P04
+
+错误原因: copy操作时对应的OID为空。
+
+解决办法: 检查copy语句，确保需要导入数据的表的OID不为空。
+
+GAUSS-01238: "invalid OID in COPY data"
+
+SQLSTATE: 22P04
+
+错误原因: 数据所对应的OID是一个无效的OID。
+
+解决办法: 检查copy语句中属性列与实际数据是否相对应。
+
+GAUSS-01239: "missing data for column '%s'"
+
+SQLSTATE: 22P04
+
+错误原因: copy语句中希望导入的列数大于实际的数据列数，使得其中的某列没有数据。
+
+解决办法: 检查copy语句中的属性列与导入的数据量列数是否一致。
+
+GAUSS-01240: "received copy data after EOF marker"
+
+SQLSTATE: 22P04
+
+错误原因: 在EOF标记后仍然读取了数据，这是因为在旧协议中没有定义EOF标记。
+
+解决办法: 确保按照当前协议书写的数据不会超过预期想要的。
+
+<br/>
+
+## GAUSS-01241 - GAUSS-01250
+
+<br/>
+
+GAUSS-01241: "row field count is %d, expected %d"
+
+SQLSTATE: 22P04
+
+错误原因: 属性个数期望的与实际不一致。
+
+解决办法: "1、从DN端返回给CN端的属性个数出错，属于内部错误，请联系技术支持工程师提供技术支持。 2、目标表属性个数与要拷贝的源文件属性个数不一致。需要检查待copy文件的列数和表中指定的列数是否一致。"
+
+GAUSS-01242: "literal carriage return found in data"
+
+SQLSTATE: 22P04
+
+错误原因: copy的数据中包含回车符。
+
+解决办法: 确保数据中不包含回车符。
+
+GAUSS-01243: "literal newline found in data"
+
+SQLSTATE: 22P04
+
+错误原因: 在CSV文件中发现不可识别的数据格式。
+
+解决办法: 请检查文件格式及文件数据内容规范性。
+
+GAUSS-01244: "end-of-copy marker does not match previous newline style"
+
+SQLSTATE: 22P04
+
+错误原因: 文件中出现异常字符。
+
+解决办法: 请检查文件数据格式合法性，详细信息请参见zh-cn_topic_0237122096.html。
+
+GAUSS-01245: "end-of-copy marker corrupt"
+
+SQLSTATE: 22P04
+
+错误原因: 文件中出现异常字符。
+
+解决办法: 请检查文件数据格式合法性，详细信息请参见zh-cn_topic_0237122096.html。
+
+GAUSS-01246: "unterminated CSV quoted field"
+
+SQLSTATE: 22P04
+
+错误原因: 文件中出现异常字符。
+
+解决办法: 请检查文件数据格式合法性，详细信息请参见zh-cn_topic_0237122096.html。
+
+GAUSS-01247: "unexpected EOF in COPY data"
+
+SQLSTATE: 22P04
+
+错误原因: 读取COPY文件出现失败。
+
+解决办法: 请检查文件数据格式合法性，详细信息请参见zh-cn_topic_0237122096.html。
+
+GAUSS-01248: "invalid field size"
+
+SQLSTATE: 22P04
+
+错误原因: 读取COPY文件中数据大小错误。
+
+解决办法: 请检查文件数据格式合法性，详细信息请参见zh-cn_topic_0237122096.html。
+
+GAUSS-01249: "incorrect binary data format"
+
+SQLSTATE: 22P03
+
+错误原因: 错误的二进制文件格式。
+
+解决办法: 请检查文件数据格式合法性，详细信息请参见zh-cn_topic_0237122096.html。
+
+GAUSS-01250: "Failed to initialize Datanodes for COPY"
+
+SQLSTATE: 08000
+
+错误原因: 无法为COPY操作初始化数据节点之间的连接。
+
+解决办法: 需要依次检查: 1. 集群状态是否正常；2. 节点之间的连接是否正常；3. 当前节点之间的网络连接是否正常；4. 所有节点上的内存资源是充足的，未发生OOM问题；
+
+<br/>
+
+## GAUSS-01251 - GAUSS-01260
+
+<br/>
+
+GAUSS-01251: "could not read symbolic link '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 读取符号链接文件失败。
+
+解决办法: 请检查符号链接文件正确性。
+
+GAUSS-01252: "symbolic link '%s' target is too long"
+
+SQLSTATE: XX000
+
+错误原因: 符号链接文件过长。
+
+解决办法: 请检查符号链接文件正确性。
+
+GAUSS-01253: "Invalid URL '%s' in LOCATION"
+
+SQLSTATE: XX000
+
+错误原因: GDS服务中URL参数错误。
+
+解决办法: 请检查URL参数值及格式正确性。
+
+GAUSS-01254: "unrecognized URL '%s'"
+
+SQLSTATE: XX000
+
+错误原因: GDS服务中URL参数错误。
+
+解决办法: 请检查URL参数值及格式正确性。
+
+GAUSS-01255: "wrong URL format '%s'"
+
+SQLSTATE: XX000
+
+错误原因: GDS服务中URL参数错误。
+
+解决办法: 请检查URL参数值及格式正确性。
+
+GAUSS-01256: "unable to open file '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 无法打开操作文件。
+
+解决办法: 请检查文件格式及权限正确性。
+
+GAUSS-01257: "unable to fseek file '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 无法设置文件指针位置。
+
+解决办法: 请检查文件格式及权限正确性。
+
+GAUSS-01258: "no files found to import"
+
+SQLSTATE: XX000
+
+错误原因: 检测到导入的文件数目为0，在raise_errors_if_no_files开启的时候，进行报错处理。
+
+解决办法: 关闭raise_errors_if_no_files参数。
+
+GAUSS-01259: "%s"
+
+SQLSTATE: XX000
+
+错误原因: "this is a sql syntax errorsql语法错误"。
+
+解决办法: "check your sql syntax.检查sql语句的语法是否正确"。
+
+GAUSS-01260: "Incomplete Message from GDS ."
+
+SQLSTATE: XX000
+
+错误原因: 从GDS中收到了非预期的消息数据。
+
+解决办法: 首先需要检查当前网络运行状况（丢包率是否较高）；若网络运行良好，则属于内部错误，请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-01261 - GAUSS-01270
+
+<br/>
+
+GAUSS-01261: "unimplemented bulkload mode"
+
+SQLSTATE: XX000
+
+错误原因: 不支持的导入模式。
+
+解决办法: 在normal/shared/private中选择一个有效的导入模式。
+
+GAUSS-01262: "relative path not allowed for writable foreign table file"
+
+SQLSTATE: 42602
+
+错误原因: 在可写外表中使用了相对路径。
+
+解决办法: 请在可写外表中使用绝对路径。
+
+GAUSS-01264: "Found invalid error recored"
+
+SQLSTATE: XX000
+
+错误原因: 元组中数据记录错误。
+
+解决办法: 请结合报错Context，尝试定位文本中导致此报错的数据行，检查是否存在非法字符。若否，请联系技术支持工程师提供技术支持。
+
+GAUSS-01265: "could not cache error info:%m"
+
+SQLSTATE: XX000
+
+错误原因: 错误信息无法缓存。
+
+解决办法: 请结合报错Context，尝试定位文本中导致此报错的数据行，检查是否存在非法字符。若否，请联系技术支持工程师提供技术支持。
+
+GAUSS-01266: "could not fetch error record:%m"
+
+SQLSTATE: XX000
+
+错误原因: 错误信息获取失败。
+
+解决办法: 请结合报错Context，尝试定位文本中导致此报错的数据行，检查是否存在非法字符。若否，请联系技术支持工程师提供技术支持。
+
+GAUSS-01267: "incomplete error record"
+
+SQLSTATE: XX000
+
+错误原因: 不完整的错误信息记录。
+
+解决办法: 请结合报错Context，尝试定位文本中导致此报错的数据行，检查是否存在非法字符。若否，请联系技术支持工程师提供技术支持。
+
+GAUSS-01268: "access method '%s' does not exist"
+
+SQLSTATE: 42704
+
+错误原因: 系统缓存中获取元组失败。
+
+解决办法: 系统表信息错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-01269: "must specify at least one column"
+
+SQLSTATE: 42P17
+
+错误原因: 创建索引过程中没有指定列。
+
+解决办法: 创建索引必须至少指定一列。
+
+GAUSS-01270: "cannot use more than %d columns in an index"
+
+SQLSTATE: 54011
+
+错误原因: 一个索引中不能同时指定超过32列。
+
+解决办法: 请勿在一个索引中同时指定超过32列。
+
+<br/>
+
+## GAUSS-01271 - GAUSS-01280
+
+<br/>
+
+GAUSS-01271: "non-partitioned table does not support local partitioned indexes "
+
+SQLSTATE: 0A000
+
+错误原因: 非分区表不支持创建local模式下的分区索引。
+
+解决办法: 1、如果需要创建local模式下的分区索引，需要重新创建基表为分区表。
+
+2、如果不需要创建local模式下的分区索引，需要删除Create unique index…local;语法最后的local参数。
+
+GAUSS-01274: "cannot create index on foreign table '%s'"
+
+SQLSTATE: 42809
+
+错误原因: 不能在外表上创建索引。
+
+解决办法: 请勿在外表上创建索引。
+
+GAUSS-01275: "cannot create indexes on temporary tables of other sessions"
+
+SQLSTATE: 0A000
+
+错误原因: 不能在其他会话的临时表上创建索引。
+
+解决办法: 请勿在其他会话的临时表上创建索引。
+
+GAUSS-01276: "when creating partitioned index, get table partitions failed"
+
+SQLSTATE: XX000
+
+错误原因: 创建分区索引时，获取分区表失败。
+
+解决办法: 请检查分区表的分区定义是否正确，如果不正确，请重建分区表。
+
+GAUSS-01278: "number of partitions of LOCAL index must equal that of the underlying table"
+
+SQLSTATE: 42P17
+
+错误原因: 分区表中分区数目小于分区索引的数目。
+
+解决办法: 请重建分区表中分区数，必须等于分区索引的数目。
+
+GAUSS-01279: "unique index columns must contain the partition key"
+
+SQLSTATE: 42P17
+
+错误原因: 唯一索引列必须包含分区键。
+
+解决办法: 唯一索引列必须包含分区键。
+
+GAUSS-01280: "unique index columns must contain the partition key and collation must be default collation"
+
+SQLSTATE: 42P17
+
+错误原因: 唯一索引列必须包含分区键。
+
+解决办法: 唯一索引列必须包含分区键，排序方式必须使用默认方式。
+
+<br/>
+
+## GAUSS-01281 - GAUSS-01290
+
+<br/>
+
+GAUSS-01281: "access method '%s' does not support unique indexes"
+
+SQLSTATE: 0A000
+
+错误原因: 该索引方式不支持唯一索引。
+
+解决办法: 请勿使用报错提示的索引类建立唯一索引。
+
+GAUSS-01282: "access method '%s' does not support multicolumn indexes"
+
+SQLSTATE: 0A000
+
+错误原因: 该索引方式不支持组合索引。
+
+解决办法: 请勿使用报错提示的索引类建立唯一索引。
+
+GAUSS-01283: "access method '%s' does not support exclusion constraints"
+
+SQLSTATE: 0A000
+
+错误原因: 该索引方式不支持排他约束。
+
+解决办法: 请勿使用报错提示的索引类附加排他约束。
+
+GAUSS-01284: "Cannot create index whose evaluation cannot be enforced to remote nodes"
+
+SQLSTATE: 0A000
+
+错误原因: MogDB主键约束通过unique btree索引实现。主键约束没有包含分布列时，无法成功创建索引。
+
+解决办法: 请检查主键约束中是否包含分布列。
+
+GAUSS-01285: "unknown constraint type"
+
+SQLSTATE: XX000
+
+错误原因: 创建索引时定义的约束类型错误。
+
+解决办法: 创建索引的约束类型关键字只能为PRIMARY KEY、UNIQUE、EXCLUDE，请使用有效的约束关键字重新创建索引。
+
+GAUSS-01286: "fail to get index info when create index partition"
+
+SQLSTATE: 42P17
+
+错误原因: 创建分区索引时，获取索引信息失败。
+
+解决办法: 请重新创建分区索引，如仍然提示失败，请联系技术支持工程师提供技术支持。
+
+GAUSS-01287: "index partition with name '%s' already exists"
+
+SQLSTATE: 42704
+
+错误原因: 分区索引名已存在。
+
+解决办法: 修改分区索引名请勿重复。
+
+GAUSS-01288: "unsupport partitioned strategy"
+
+SQLSTATE: 42P17
+
+错误原因: 不支持的分区策略。
+
+解决办法: 目前仅支持对RANGE或INTERNAL分区表创建分区索引时，请重新修改分区表为RANGE或INTERNAL类型分区表，再创建分区索引。
+
+GAUSS-01289: "collation '%s' does not exist"
+
+SQLSTATE: 42P17
+
+错误原因: 索引的排序模式不存在。
+
+解决办法: 检查索引的排序模式是否正确。
+
+GAUSS-01290: "cannot use subquery in index predicate"
+
+SQLSTATE: 0A000
+
+错误原因: 表达式索引中不能使用子查询。
+
+解决办法: 请勿在表达式索引中使用子查询。
+
+<br/>
+
+## GAUSS-01291 - GAUSS-01300
+
+<br/>
+
+GAUSS-01291: "cannot use aggregate in index predicate"
+
+SQLSTATE: 42803
+
+错误原因: 表达式索引中不能使用聚集操作。
+
+解决办法: 请勿在表达式索引中使用聚集操作。
+
+GAUSS-01292: "functions in index predicate must be marked IMMUTABLE"
+
+SQLSTATE: 42P17
+
+错误原因: 表达式索引中不能使用易变函数。
+
+解决办法: 保证表达式索引中的函数为不变函数。
+
+GAUSS-01293: "cannot use subquery in index expression"
+
+SQLSTATE: 0A000
+
+错误原因: 表达式索引中不能使用子查询。
+
+解决办法: 请勿在表达式索引中使用子查询。
+
+GAUSS-01294: "cannot use aggregate function in index expression"
+
+SQLSTATE: 42803
+
+错误原因: 表达式索引中不能使用聚集操作。
+
+解决办法: 请勿在表达式索引中使用聚集操作。
+
+GAUSS-01295: "functions in index expression must be marked IMMUTABLE"
+
+SQLSTATE: 42P17
+
+错误原因: 表达式索引中的函数必须不能变化。
+
+解决办法: 保证表达式索引中的函数为不变函数。
+
+GAUSS-01296: "could not determine which collation to use for index expression"
+
+SQLSTATE: 42P22
+
+错误原因: 无法决定在表达式索引中使用哪种排序方式。
+
+解决办法: 需要在创建表达式索引时指定排序方式。
+
+GAUSS-01297: "operator %s is not commutative"
+
+SQLSTATE: 42809
+
+错误原因: 操作符不可交换。
+
+解决办法: 排他约束中必须使用可交换操作符。
+
+GAUSS-01298: "cache lookup failed for opfamily %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01299: "operator %s is not a member of operator family '%s'"
+
+SQLSTATE: 42809
+
+错误原因: 操作符不在期望的操作符家族之列。
+
+解决办法: 排除操作符必须和索引约束有关。
+
+GAUSS-01300: "access method '%s' does not support ASC/DESC options"
+
+SQLSTATE: 0A000
+
+错误原因: 索引处理方法不支持ASC/DESC选项。
+
+解决办法: 重建索引并设置索引列的访问方法（pg_am中amcanorder字段）为true支持索引列排序。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/14-GAUSS-01301-GAUSS-01400.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/14-GAUSS-01301-GAUSS-01400.md
new file mode 100644
index 0000000000000000000000000000000000000000..9b450b141033d35edd76042c79f4f1065b2cd665
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/14-GAUSS-01301-GAUSS-01400.md
@@ -0,0 +1,748 @@
+---
+title: GAUSS-01301 - GAUSS-01400
+summary: GAUSS-01301 - GAUSS-01400
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-01301 - GAUSS-01400
+
+<br/>
+
+## GAUSS-01301 - GAUSS-01310
+
+<br/>
+
+GAUSS-01301: "access method '%s' does not support NULLS FIRST/LAST options"
+
+SQLSTATE: 0A000
+
+错误原因: 索引处理方法不支持NULLS/FIRST/LAST选项。
+
+解决办法: 重建索引并设置索引列的访问方法（pg_am中amcanorder字段）为true支持索引列排序。
+
+GAUSS-01302: "operator class '%s' does not exist for access method '%s'"
+
+SQLSTATE: 42704
+
+错误原因: 索引处理方法不支持的操作符。
+
+解决办法: 请确定操作符是索引支持的类。
+
+GAUSS-01303: "there are multiple default operator classes for data type %s"
+
+SQLSTATE: 42710
+
+错误原因: 类型操作符的种类过多。
+
+解决办法: pg_opclass系统表中类型操作符定义错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-01304: "'%s' does not mean oid '%u'"
+
+SQLSTATE: XX000
+
+错误原因: 分区表OID获取错误。
+
+解决办法: 通过ALTER INDEX…REBUILD;语法重建索引。
+
+GAUSS-01305: "'%u' is not a child of '%u'"
+
+SQLSTATE: XX000
+
+错误原因: 非分区表的子分区。
+
+解决办法: 通过ALTER INDEX…REBUILD;语法重建索引。
+
+GAUSS-01308: "fail to get index info for index %u"
+
+SQLSTATE: XX000
+
+错误原因: 无法得到分区表索引的索引。
+
+解决办法: 在Cache中查找partition表的索引表（pg_index系统表的索引信息）失败，Cache存在异常，请联系技术支持工程师提供技术支持。
+
+GAUSS-01309: "unable to find attribute %d for relation %u."
+
+SQLSTATE: XX000
+
+错误原因: 无法找到表的属性信息。
+
+解决办法: 在Cache中查找partition索引表的属性列失败，Cache存在异常，请联系技术支持工程师提供技术支持。
+
+GAUSS-01310: "cache %d lookup failed for relation %u"
+
+SQLSTATE: XX000
+
+错误原因: 在pg_class表中查找索引表失败。
+
+解决办法: Cache中pg_class表对应的索引表产生异常，请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-01311 - GAUSS-01320
+
+<br/>
+
+GAUSS-01311: "collation attribute '%s' not recognized"
+
+SQLSTATE: 42601
+
+错误原因: create collation语法不支持。
+
+解决办法: create collation语法不支持。
+
+GAUSS-01314: "collation '%s' for encoding '%s' already exists in schema '%s'"
+
+SQLSTATE: 42710
+
+错误原因: 某类字符集的排序规则已存在。
+
+解决办法: 对一个字符集不创建重复的排序规则。
+
+GAUSS-01315: "collation '%s' already exists in schema '%s'"
+
+SQLSTATE: 42710
+
+错误原因: 排序规则在模式中已存在。
+
+解决办法: 不在同一模式中创建重复的排序规则。
+
+GAUSS-01316: "unlogged sequences are not supported"
+
+SQLSTATE: 0A000
+
+错误原因: 不支持创建不被记录的序列。
+
+解决办法: 请勿创建unlogged类型序列。
+
+GAUSS-01317: "GTM error, could not create sequence"
+
+SQLSTATE: 08006
+
+错误原因: GTM错误，无法创建序列。
+
+解决办法: 通过命令[gs_om -t status -detail]查看gtm状态，如果gtm状态异常，请参考《故障处理》手册定位解决GTM故障问题后再次进行创建序列操作。
+
+GAUSS-01318: "GTM error, could not alter sequence"
+
+SQLSTATE: 08006
+
+错误原因: GTM错误，无法修改序列。
+
+解决办法: 通过命令[gs_om -t status -detail]查看gtm状态，如果gtm状态异常，请参考《故障处理》手册定位解决GTM故障问题后再次进行创建序列操作。
+
+GAUSS-01319: "permission denied for sequence %s"
+
+SQLSTATE: 42501
+
+错误原因: 没有访问序列的权限。
+
+解决办法: 请检查当前用户是否有操作该序列的权限。
+
+GAUSS-01320: "nextval: reached maximum value of sequence '%s' (%s)"
+
+SQLSTATE: 55000
+
+错误原因: 达到序列最大值的限制。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-01321 - GAUSS-01330
+
+<br/>
+
+GAUSS-01321: "nextval: reached minimum value of sequence '%s' (%s)"
+
+SQLSTATE: 55000
+
+错误原因: 达到序列最小值的限制。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-01323: "lastval is not yet defined in this session"
+
+SQLSTATE: 55000
+
+错误原因: 序列的最后变量在当前会话中未定义。
+
+解决办法: 请检查当前会话是否已定义该序列的最后变量。
+
+GAUSS-01324: "setval: value %s is out of bounds for sequence '%s' (%s..%s)"
+
+SQLSTATE: 22003
+
+错误原因: 设置的序列值超出了序列范围。
+
+解决办法: 请检查设置值是否超出序列范围。
+
+GAUSS-01325: "GTM error, could not obtain sequence value"
+
+SQLSTATE: 08006
+
+错误原因: GTM错误，无法获得序列值。
+
+解决办法: 通过命令[gs_om -t status -detail]查看gtm状态，如果gtm状态异常，请参考《故障处理》手册定位解决GTM故障问题后再次进行创建序列操作。
+
+GAUSS-01326: "bad magic number in sequence '%s': %08X"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。打开序列表中的魔法数字与期望的魔法数字不一致。
+
+解决办法: 可能由于序列表存在异常导致，请联系技术支持工程师提供技术支持。
+
+GAUSS-01327: "INCREMENT must not be zero"
+
+SQLSTATE: 22023
+
+错误原因: 序列中增量值不能为0。
+
+解决办法: 序列中增量值不能为0。
+
+GAUSS-01328: "MINVALUE (%s) must be less than MAXVALUE (%s)"
+
+SQLSTATE: 22023
+
+错误原因: 序列最小值必须小于最大值。
+
+解决办法: 序列最小值必须小于最大值。
+
+GAUSS-01329: "START value (%s) cannot be less than MINVALUE (%s)"
+
+SQLSTATE: 22023
+
+错误原因: 序列最小值必须小于最大值。
+
+解决办法: 序列初始值不能设置为低于最小值。
+
+GAUSS-01330: "START value (%s) cannot be greater than MAXVALUE (%s)"
+
+SQLSTATE: 22023
+
+错误原因: 序列初始值不能超过最大值。
+
+解决办法: 序列初始值不能设置为超过最大值。
+
+<br/>
+
+## GAUSS-01331 - GAUSS-01340
+
+<br/>
+
+GAUSS-01331: "RESTART value (%s) cannot be less than MINVALUE (%s)"
+
+SQLSTATE: 22023
+
+错误原因: RESTART子句，RESTART的值小于了MINVALUE。
+
+解决办法: 修改RESTART子句，使得RESTART的值不小于MINVALUE。
+
+GAUSS-01332: "RESTART value (%s) cannot be greater than MAXVALUE (%s)"
+
+SQLSTATE: 22023
+
+错误原因: RESTART子句，RESTART的值大于了MAXVALUE。
+
+解决办法: 修改RESTART子句，使得RESTART的值不大于MAXVALUE。
+
+GAUSS-01334: "invalid OWNED BY option"
+
+SQLSTATE: 42601
+
+错误原因: OWNED BY子句中指定的不是NONE。
+
+解决办法: 修改为OWNED BY NONE。
+
+GAUSS-01335: "sequence must have same owner as table it is linked to"
+
+SQLSTATE: 55000
+
+错误原因: sequence与关联的表不是一个所有者。
+
+解决办法: OWNED BY子句只能指定与sequence相同OWNER的table。
+
+GAUSS-01336: "sequence must be in same schema as table it is linked to"
+
+SQLSTATE: 55000
+
+错误原因: sequence与关联的表不是一个schema。
+
+解决办法: OWNED BY子句只能指定与sequence相同schema的table。
+
+GAUSS-01337: "seq_redo: unknown op code %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01338: "seq_redo: failed to add item to page"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01340: "unrecognized attribute for text search parser: %d"
+
+SQLSTATE: XX000
+
+错误原因: 通过语法[CREATE TEXT SEARCH CONFIGURATION PARSER…]创建全文检索解析器时，获取系统表pg_ts_parser中指定列错误。
+
+解决办法: 系统表pg_ts_parser属性信息错误，系统产生异常或由人为修改系统表属性导致，请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-01341 - GAUSS-01350
+
+<br/>
+
+GAUSS-01341: "function %s should return type %s"
+
+SQLSTATE: 42P17
+
+错误原因: CREATE TEXT SEARCH PARSER，某个函数的返回值类型与期望的不符。
+
+解决办法: CREATE TEXT SEARCH PARSER，按照错误提示修改指定函数，新函数的返回值类型必须符合错误提示中的类型。
+
+GAUSS-01342: "must be system admin to create text search parsers"
+
+SQLSTATE: 42501
+
+错误原因: CREATE TEXT SEARCH PARSER，使用了非系统管理员帐户。
+
+解决办法: CREATE TEXT SEARCH PARSER，须得使用管理员帐户。
+
+GAUSS-01343: "text search parser parameter '%s' not recognized"
+
+SQLSTATE: 42601
+
+错误原因: CREATE TEXT SEARCH PARSER，定义了不识别的函数。
+
+解决办法: CREATE TEXT SEARCH PARSER，不要指定start/gettoken/end/headline/lextypes名称之外的函数。
+
+GAUSS-01345: "text search parser gettoken method is required"
+
+SQLSTATE: 42P17
+
+错误原因: CREATE TEXT SEARCH PARSER，没有定义gettoken方法。
+
+解决办法: CREATE TEXT SEARCH PARSER，需要定义gettoken函数。
+
+GAUSS-01347: "text search parser lextypes method is required"
+
+SQLSTATE: 42P17
+
+错误原因: CREATE TEXT SEARCH PARSER，没有定义lextypes方法。
+
+解决办法: CREATE TEXT SEARCH PARSER，需要定义start函数。
+
+GAUSS-01348: "cache lookup failed for text search parser %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01349: "must be system admin to rename text search parsers"
+
+SQLSTATE: 42501
+
+错误原因: ALTER TEXT SEARCH PARSER name RENAME TO new_name，使用了非系统管理员帐户。
+
+解决办法: ALTER TEXT SEARCH PARSER name RENAME TO new_name，须得是系统管理员。
+
+<br/>
+
+## GAUSS-01351 - GAUSS-01360
+
+<br/>
+
+GAUSS-01351: "cache lookup failed for text search template %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01352: "text search template '%s' does not accept options"
+
+SQLSTATE: 42601
+
+错误原因: CREATE TEXT SEARCH DICTIONARY/ALTER TEXT SEARCH DICTIONARY，没有指定INIT方法，但是指定了options。
+
+解决办法: CREATE TEXT SEARCH DICTIONARY/ALTER TEXT SEARCH DICTIONARY，要么在指定INIT时，才指定options选项，要么不要指定任何options。
+
+GAUSS-01353: "text search template is required"
+
+SQLSTATE: 42P17
+
+错误原因: CREATE TEXT SEARCH DICTIONARY，没有提供template。
+
+解决办法: CREATE TEXT SEARCH DICTIONARY，需要提供template。
+
+GAUSS-01354: "cache lookup failed for text search dictionary %u"
+
+SQLSTATE: XX000
+
+错误原因: 在系统表中未找到对应ID的全文检索词典。
+
+解决办法: 请检查是否有会话并发对该词典执行了drop操作。
+
+GAUSS-01355: "text search dictionary '%s' already exists"
+
+SQLSTATE: 42710
+
+错误原因: ALTER TEXT SEARCH DICTIONARY name RENAME TO new_name，提供的新名称与旧名称冲突。
+
+解决办法: ALTER TEXT SEARCH DICTIONARY name RENAME TO new_name，提供的新名称须不与旧名称冲突。
+
+GAUSS-01356: "unrecognized attribute for text search template: %d"
+
+SQLSTATE: XX000
+
+错误原因: 创建全文检索模板时，获取系统表pg_ts_template中指定列错误。
+
+解决办法: 系统表pg_ts_template属性信息错误，系统产生异常或由人为修改系统表属性导致，请联系技术支持工程师提供技术支持。
+
+GAUSS-01357: "must be system admin to create text search templates"
+
+SQLSTATE: 42501
+
+错误原因: CREATE TEXT SEARCH TEMPLATE时，使用了非管理员帐户。
+
+解决办法: CREATE TEXT SEARCH TEMPLATE，需要使用系统管理员帐户。
+
+GAUSS-01358: "text search template parameter '%s' not recognized"
+
+SQLSTATE: 42601
+
+错误原因: CREATE TEXT SEARCH TEMPLATE，提供了不识别的模板参数。
+
+解决办法: CREATE TEXT SEARCH TEMPLATE，不要提供init/lexize名称之外的模板参数。
+
+GAUSS-01359: "text search template lexize method is required"
+
+SQLSTATE: 42P17
+
+错误原因: CREATE TEXT SEARCH TEMPLATE，没有提供合法的lexize方法。
+
+解决办法: CREATE TEXT SEARCH TEMPLATE，需要提供合法的lexize方法。
+
+GAUSS-01360: "must be system admin to rename text search templates"
+
+SQLSTATE: 42501
+
+错误原因: ALTER TEXT SEARCH TEMPLATE name RENAME TO new_name，使用的帐户不是系统管理员帐户。
+
+解决办法: ALTER TEXT SEARCH TEMPLATE name RENAME TO new_name，须得是管理员。
+
+<br/>
+
+## GAUSS-01361 - GAUSS-01370
+
+<br/>
+
+GAUSS-01362: "cache lookup failed for text search configuration %u"
+
+SQLSTATE: XX000
+
+错误原因: 在系统表中未找到对应ID的全文检索配置。
+
+解决办法: 请检查是否有会话并发对该配置做了drop操作。
+
+GAUSS-01363: "text search configuration parameter '%s' not recognized"
+
+SQLSTATE: 42601
+
+错误原因: CREATE TEXT SEARCH CONFIGURATION，提供了不被识别的配置参数。
+
+解决办法: CREATE TEXT SEARCH CONFIGURATION，不要提供除了parser/copy之外的配置参数。
+
+GAUSS-01364: "cannot specify both PARSER and COPY options"
+
+SQLSTATE: 42601
+
+错误原因: CREATE TEXT SEARCH CONFIGURATION，同时指定了PARSER/COPY选项。
+
+解决办法: CREATE TEXT SEARCH CONFIGURATION，不要同时指定PARSER/COPY选项。
+
+GAUSS-01365: "text search parser is required"
+
+SQLSTATE: 42P17
+
+错误原因: CREATE TEXT SEARCH CONFIGURATION，从parser/copy中计算出的最终的parser非法。
+
+解决办法: CREATE TEXT SEARCH CONFIGURATION，从parser/copy中计算出的最终的parser必须是可用的。
+
+GAUSS-01366: "text search configuration '%s' already exists"
+
+SQLSTATE: 42710
+
+错误原因: ALTER TEXT SEARCH CONFIGURATION RENAME，新名称与旧名称冲突。
+
+解决办法: ALTER TEXT SEARCH CONFIGURATION RENAME，新名称须得不与旧名称冲突。
+
+GAUSS-01367: "text search configuration '%s' does not exist"
+
+SQLSTATE: 42704
+
+错误原因: ALTER TEXT SEARCH CONFIGURATION，指定名称的配置不存在。
+
+解决办法: ALTER TEXT SEARCH CONFIGURATION，须得指定名称存在的配置。
+
+GAUSS-01368: "method lextype isn't defined for text search parser %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统表pg_ts_parser中对应的prslextype定义错误。
+
+解决办法: 系统表pg_ts_parser属性信息错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-01369: "token type '%s' does not exist"
+
+SQLSTATE: 22023
+
+错误原因: ALTER TEXT SEARCH CONFIGURATION(ADD/ALTER/DROP MAPPING)，某个token_type不存在。
+
+解决办法: ALTER TEXT SEARCH CONFIGURATION(ADD/ALTER/DROP MAPPING)，必须指定存在的某个token_type。
+
+GAUSS-01370: "mapping for token type '%s' does not exist"
+
+SQLSTATE: 42704
+
+错误原因: ALTER TEXT SEARCH CONFIGURATION(DROP MAPPING)，某个标识的MAPPING不存在。
+
+解决办法: ALTER TEXT SEARCH CONFIGURATION(DROP MAPPING)，必须指定存在的某个mapping。
+
+<br/>
+
+## GAUSS-01371 - GAUSS-01380
+
+<br/>
+
+GAUSS-01371: "invalid parameter list format: '%s'"
+
+SQLSTATE: 42601
+
+错误原因: 反序列化字典选项时，参数list格式不正确，=后面缺少空格。
+
+解决办法: 参数list格式不正确，=后面紧跟一个空格。
+
+GAUSS-01372: "unrecognized deserialize_deflist state: %d"
+
+SQLSTATE: XX000
+
+错误原因: 无法识别全文检索目录反序列化过程状态机。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-01375: "Bad socket."
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。read socket不合法。
+
+解决办法: 请检查gds与数据节点的网络连接、网络环境、节点的系统端口是否正常。
+
+GAUSS-01376: "Unexpected EOF on GDS connection '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。与GDS端交互数据时，发生了错误。
+
+解决办法: 请检查gds与数据节点的网络连接、网络环境、节点的系统端口是否正常。请检查GDS的LOG，查看相关WARNING和ERROR日志，定位相关原因。
+
+GAUSS-01377: "Unexpected connection EOF from '%s':%m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。与GDS端交互数据时，发生了错误。
+
+解决办法: 请检查gds与数据节点的网络连接、网络环境、节点的系统端口是否正常。请检查GDS的LOG，查看相关WARNING和ERROR日志，定位相关原因。
+
+GAUSS-01378: "invalid URI '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 提供给GDS外表的URI非法。
+
+解决办法: 请检查并纠正GDS外表中location相关设置。
+
+GAUSS-01380: "'%s' is a table"
+
+SQLSTATE: 42809
+
+错误原因: 在表上定义了INSTEAD OF触发器。
+
+解决办法: 不要在表上定义INSTEAD OF trigger，只能定义BEFORE/AFTER。
+
+<br/>
+
+## GAUSS-01381 - GAUSS-01390
+
+<br/>
+
+GAUSS-01381: "'%s' is a view"
+
+SQLSTATE: 42809
+
+错误原因: 在视图上定义了row-level BEFORE or AFTER triggers/TRUNCATE触发器。
+
+解决办法: 在视图上只能定义INSTEAD OF触发器。
+
+GAUSS-01382: "'%s' is not a table or view"
+
+SQLSTATE: 42809
+
+错误原因: 在表上或者视图之外的对象上定义触发器。
+
+解决办法: 只能在表和视图上定义视图。
+
+GAUSS-01383: "TRUNCATE FOR EACH ROW triggers are not supported"
+
+SQLSTATE: 0A000
+
+错误原因: 定义了ROW-level TRUNCATE triggers。
+
+解决办法: 不要定义TRUNCATE FOR EACH ROW。
+
+GAUSS-01385: "INSTEAD OF triggers cannot have WHEN conditions"
+
+SQLSTATE: 0A000
+
+错误原因: INSTEAD OF triggers附加了WHEN子句。
+
+解决办法: INSTEAD OF triggers附加了WHEN子句。
+
+GAUSS-01386: "INSTEAD OF triggers cannot have column lists"
+
+SQLSTATE: 0A000
+
+错误原因: INSTEAD OF triggers定义在了表的列上。
+
+解决办法: INSTEAD OF triggers不能在表的列上定义。
+
+GAUSS-01387: "cannot use subquery in trigger WHEN condition"
+
+SQLSTATE: 0A000
+
+错误原因: trigger WHEN子句中使用了子查询。
+
+解决办法: trigger WHEN子句中不能使用子查询。
+
+GAUSS-01388: "cannot use aggregate function in trigger WHEN condition"
+
+SQLSTATE: 42803
+
+错误原因: trigger WHEN子句中使用了聚集函数。
+
+解决办法: trigger WHEN子句中不能使用聚集函数。
+
+GAUSS-01389: "cannot use window function in trigger WHEN condition"
+
+SQLSTATE: 42P20
+
+错误原因: trigger WHEN子句中使用了window函数。
+
+解决办法: trigger WHEN子句中不能使用window函数。
+
+GAUSS-01390: "statement trigger's WHEN condition cannot reference column values"
+
+SQLSTATE: 42P17
+
+错误原因: statement triggers的WHEN子句引用了列值。
+
+解决办法: statement triggers的WHEN子句不能引用列值。
+
+<br/>
+
+## GAUSS-01391 - GAUSS-01400
+
+<br/>
+
+GAUSS-01391: "INSERT trigger's WHEN condition cannot reference OLD values"
+
+SQLSTATE: 42P17
+
+错误原因: INSERT trigger的WHEN子句引用了OLD值。
+
+解决办法: INSERT trigger的WHEN子句不能引用OLD值。
+
+GAUSS-01392: "DELETE trigger's WHEN condition cannot reference NEW values"
+
+SQLSTATE: 42P17
+
+错误原因: DELETE trigger的WHEN子句引用了NEW值。
+
+解决办法: DELETE trigger的WHEN子句不能引用NEW值。
+
+GAUSS-01393: "BEFORE trigger's WHEN condition cannot reference NEW system columns"
+
+SQLSTATE: 0A000
+
+错误原因: BEFORE trigger的WHEN子句引用了NEW系统列值。
+
+解决办法: BEFORE trigger的WHEN子句不能引用NEW系统列值。
+
+GAUSS-01394: "trigger WHEN condition cannot contain references to other relations"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01395: "function %s must return type 'trigger'"
+
+SQLSTATE: 42P17
+
+错误原因: trigger function的返回值不是trigger类型。
+
+解决办法: trigger function的返回值必须是trigger类型。
+
+GAUSS-01396: "trigger '%s' for relation '%s' already exists"
+
+SQLSTATE: 42710
+
+错误原因: relation上已经定义了同名的trigger。
+
+解决办法: 修改create trigger的名称，不要与已有trigger重名。
+
+GAUSS-01397: "confused about RI update function"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01398: "confused about RI delete function"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01399: "could not find tuple for trigger %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01400: "trigger '%s' for table '%s' does not exist"
+
+SQLSTATE: 42704
+
+错误原因: 按照名称去查找trigger，结果发现找不到。
+
+解决办法: 指定存在的trigger名。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/15-GAUSS-01401-GAUSS-01500.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/15-GAUSS-01401-GAUSS-01500.md
new file mode 100644
index 0000000000000000000000000000000000000000..7f1dc1012b9046a32c3b3618b0d1c72d03159629
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/15-GAUSS-01401-GAUSS-01500.md
@@ -0,0 +1,820 @@
+---
+title: GAUSS-01401 - GAUSS-01500
+summary: GAUSS-01401 - GAUSS-01500
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-01401 - GAUSS-01500
+
+<br/>
+
+## GAUSS-01401 - GAUSS-01410
+
+<br/>
+
+GAUSS-01401: "permission denied: '%s' is a system trigger"
+
+SQLSTATE: 42501
+
+错误原因: 使用非系统管理员帐号ENABLE/DISABLE系统trigger。
+
+解决办法: 使用系统管理员帐号ENABLE/DISABLE系统trigger。
+
+GAUSS-01402: "tgargs is null in trigger for relation '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01403: "trigger function %u returned null value"
+
+SQLSTATE: 39P01
+
+错误原因: 系统内部错误。执行trigger函数，trigger函数返回了NULL值。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01404: "BEFORE STATEMENT trigger cannot return a value"
+
+SQLSTATE: 39P01
+
+错误原因: BEFORE STATEMENT trigger有返回值。
+
+解决办法: 检查BEFORE STATEMENT trigger的trigger函数，不能返回记录。
+
+GAUSS-01405: "could not serialize access due to concurrent update"
+
+SQLSTATE: 40001
+
+错误原因: 由于并发更新，无法满足事务的序列化。
+
+解决办法: 重试失败的事务。
+
+GAUSS-01406: "unrecognized heap_lock_tuple status: %u"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01407: "could not find trigger %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01408: "failed to fetch tuple1 for AFTER trigger"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01409: "failed to fetch tuple2 for AFTER trigger"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01410: "relation %u has no triggers"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-01411 - GAUSS-01420
+
+<br/>
+
+GAUSS-01411: "cross-database references are not implemented: '%s.%s.%s'"
+
+SQLSTATE: 0A000
+
+错误原因: SET CONSTRAINT语句，在当前数据库中设置别的数据库的CONSTRAINT。
+
+解决办法: SET CONSTRAINT语句，不要在当前数据库中设置别的数据库的CONSTRAINT。
+
+GAUSS-01412: "constraint '%s' is not deferrable"
+
+SQLSTATE: 42809
+
+错误原因: SET CONSTRAINT语句，constraint不是可延迟的。
+
+解决办法: SET CONSTRAINT语句，不能设置不可延迟的constraint为可延迟的。
+
+GAUSS-01413: "constraint '%s' does not exist"
+
+SQLSTATE: 42704
+
+错误原因: SET CONSTRAINT语句，constraint不存在。
+
+解决办法: SET CONSTRAINT语句，必须指定存在的constraint。
+
+GAUSS-01414: "no triggers found for constraint with OID %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01415: "AfterTriggerSaveEvent() called outside of transaction"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01416: "AfterTriggerSaveEvent() called outside of query"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01418: "XC: Could not find the required row position %d for AFTER ROW trigger"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01419: "XC: Could not find the required row position %d forAFTER ROW trigger"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-01421 - GAUSS-01430
+
+<br/>
+
+GAUSS-01421: "could not obtain lock on relation '%s'"
+
+SQLSTATE: 55P03
+
+错误原因: LOCK TABLE NOWAIT，在表上加不上锁。
+
+解决办法: 改成LOCK TABLE。
+
+GAUSS-01422: "cache lookup failed for access method %u"
+
+SQLSTATE: 22P06
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01423: "operator family '%s' does not exist for access method '%s'"
+
+SQLSTATE: 42704
+
+错误原因: ALTER OPERATOR FAMILY时，为指定access method服务的operator family不存在。
+
+解决办法: 查看已有的OPERATOR FAMILY，检查出错的ALTER OPERATOR FAMILY中指定的access method与OPERATOR FAMILY是否匹配。
+
+GAUSS-01424: "operator family '%s' for access method '%s' already exists"
+
+SQLSTATE: 42710
+
+错误原因: CREATE OPERATOR FAMILY时，创建的OPERATOR FAMILY已经存在了。
+
+解决办法: CREATE OPERATOR FAMILY时，名称须与已有OPERATOR FAMILY不重复。
+
+GAUSS-01425: "must be system admin to create an operator class"
+
+SQLSTATE: 42501
+
+错误原因: CREATE OPERATOR FAMILY时，使用帐户不是系统管理员。
+
+解决办法: CREATE OPERATOR FAMILY时，须得以系统管理员帐户。
+
+GAUSS-01426: "invalid operator number %d, must be between 1 and %d"
+
+SQLSTATE: 42P17
+
+错误原因: CREATE OPERATOR CLASS/ALTER OPERATOR FAMILY的OPERATOR子句中的strategy_number小于1或者大于index_method的最大strategy_number。
+
+解决办法: CREATE OPERATOR CLASS/ALTER OPERATOR FAMILY的OPERATOR子句中的strategy_number须得在1和index_method的最大strategy_number之间。
+
+GAUSS-01427: "invalid procedure number %d, must be between 1 and %d"
+
+SQLSTATE: 42P17
+
+错误原因: CREATE OPERATOR CLASS/ALTER OPERATOR FAMILY的FUNCTION子句中的support_number小于1或者大于index_method的最大support_number。
+
+解决办法: CREATE OPERATOR CLASS/ALTER OPERATOR FAMILY的FUNCTION子句中的support_number须得在1和index_method的最大support_number之间。
+
+GAUSS-01428: "storage type specified more than once"
+
+SQLSTATE: 42P17
+
+错误原因: CREATE OPERATOR CLASS包含了多个相同的STORAGE子句。
+
+解决办法: CREATE OPERATOR CLASS的多个STORAGE子句不可重复。
+
+GAUSS-01429: "unrecognized item type: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统不支持用户自定义操作符。
+
+解决办法: 系统不支持用户自定义操作符，导致通过语法create operator创建自定义操作符失败。
+
+GAUSS-01430: "storage type cannot be different from data type for access method '%s'"
+
+SQLSTATE: 42P17
+
+错误原因: CREATE OPERATOR CLASS的STORAGE子句指定的storage_type与column_type不同，但是指定的access_method不允许这样。
+
+解决办法: CREATE OPERATOR CLASS的STORAGE子句指定的index中实际存储的数据类型storage_type，须与access_method的列数据类型column_type相同。
+
+<br/>
+
+## GAUSS-01431 - GAUSS-01440
+
+<br/>
+
+GAUSS-01431: "operator class '%s' for access method '%s' already exists"
+
+SQLSTATE: 42710
+
+错误原因: CREATE OPERATOR CLASS，定义的operator class已经存在。
+
+解决办法: CREATE OPERATOR CLASS，定义的operator class须与已有的operator class不同名。
+
+GAUSS-01432: "could not make operator class '%s' be default for type %s"
+
+SQLSTATE: 42710
+
+错误原因: CREATE OPERATOR CLASS，使用关键字为数据类型创建默认的OPERATOR CLASS时，发现该数据类型已有默认的OPERATOR CLASS。
+
+解决办法: CREATE OPERATOR CLASS，使用关键字为数据类型创建默认的OPERATOR CLASS时，首先确认该数据类型没有默认的OPERATOR CLASS。
+
+GAUSS-01433: "must be system admin to create an operator family"
+
+SQLSTATE: 42501
+
+错误原因: CREATE OPERATOR FAMILY，使用的帐户不是系统管理员帐户。
+
+解决办法: CREATE OPERATOR FAMILY，须得以系统管理员帐户。
+
+GAUSS-01434: "must be system admin to alter an operator family"
+
+SQLSTATE: 42501
+
+错误原因: ALTER OPERATOR FAMILY … ADD/DROP，使用的帐户不是系统管理员帐户。
+
+解决办法: ALTER OPERATOR FAMILY … ADD/DROP，使用的帐户须得是系统管理员帐户。
+
+GAUSS-01435: "operator argument types must be specified in ALTER OPERATOR FAMILY"
+
+SQLSTATE: 42601
+
+错误原因: ALTER OPERATOR FAMILY … ADD OPERATOR，没有指定OPERATOR的参数类型。
+
+解决办法: ALTER OPERATOR FAMILY … ADD OPERATOR，须得指定OPERATOR的参数类型。
+
+GAUSS-01436: "STORAGE cannot be specified in ALTER OPERATOR FAMILY"
+
+SQLSTATE: 42601
+
+错误原因: ALTER OPERATOR FAMILY … ADD中指定了STORAGE子句。
+
+解决办法: ALTER OPERATOR FAMILY … ADD中不能指定STORAGE子句。
+
+GAUSS-01437: "one or two argument types must be specified"
+
+SQLSTATE: 42601
+
+错误原因: CREATE OPERATOR CLASS、ALTER OPERATOR FAMILY … ADD/DROP中指定的OPERATOR/FUNCTION参数超过了2个。
+
+解决办法: CREATE OPERATOR CLASS、ALTER OPERATOR FAMILY … ADD/DROP中指定的OPERATOR/FUNCTION参数只能是1个或者2个。
+
+GAUSS-01438: "index operators must be binary"
+
+SQLSTATE: 42P17
+
+错误原因: CREATE OPERATOR CLASS、ALTER OPERATOR FAMILY … ADD指定的OPERATOR不是二元操作符。
+
+解决办法: CREATE OPERATOR CLASS、ALTER OPERATOR FAMILY … ADD指定的OPERATOR须得是二元操作符。
+
+GAUSS-01439: "access method '%s' does not support ordering operators"
+
+SQLSTATE: 42P17
+
+错误原因: CREATE OPERATOR CLASS、ALTER OPERATOR FAMILY … ADD，指定了sort operator，但是access_method不支持排序。
+
+解决办法: CREATE OPERATOR CLASS、ALTER OPERATOR FAMILY … ADD，只有access_method支持排序操作符时，指定的OPERATOR才可以FOR ORDER，否则只能FOR SEARCH。
+
+GAUSS-01440: "index search operators must return Boolean"
+
+SQLSTATE: 42P17
+
+错误原因: CREATE OPERATOR CLASS、ALTER OPERATOR FAMILY … ADD OPERATOR…FOR SEARCH，但是该操作符的返回值不是BOOL类型。
+
+解决办法: CREATE OPERATOR CLASS、ALTER OPERATOR FAMILY … ADD OPERATOR…FOR SEARCH，则操作符的返回值必须是BOOL类型。
+
+<br/>
+
+## GAUSS-01441 - GAUSS-01450
+
+<br/>
+
+GAUSS-01441: "btree comparison procedures must have two arguments"
+
+SQLSTATE: 42P17
+
+错误原因: CREATE OPERATOR CLASS、ALTER OPERATOR FAMILY … ADD FUNCTION，access_method是btree且指定的函数是btree比较函数，但是参数个数不是2个。
+
+解决办法: CREATE OPERATOR CLASS、ALTER OPERATOR FAMILY … ADD FUNCTION，指定的函数是btree比较函数，则参数个数必须是2个。
+
+GAUSS-01442: "btree comparison procedures must return integer"
+
+SQLSTATE: 42P17
+
+错误原因: CREATE OPERATOR CLASS、ALTER OPERATOR FAMILY … ADD FUNCTION，access_method是btree且指定的函数是btree比较函数，但是返回值类型不是int。
+
+解决办法: CREATE OPERATOR CLASS、ALTER OPERATOR FAMILY … ADD FUNCTION，指定的函数是btree比较函数，则返回值类型必须是int。
+
+GAUSS-01443: "btree sort support procedures must accept type 'internal'"
+
+SQLSTATE: 42P17
+
+错误原因: CREATE OPERATOR CLASS、ALTER OPERATOR FAMILY … ADD FUNCTION，access_method是btree且指定的函数是btree sort support函数，但是参数类型不是internal。
+
+解决办法: CREATE OPERATOR CLASS、ALTER OPERATOR FAMILY … ADD FUNCTION，指定的函数是btree sort support函数，则参数类型必须是internal。
+
+GAUSS-01444: "btree sort support procedures must return void"
+
+SQLSTATE: 42P17
+
+错误原因: CREATE OPERATOR CLASS、ALTER OPERATOR FAMILY … ADD FUNCTION，access_method是btree且指定的函数是btree sort support函数，但是返回值类型不是void。
+
+解决办法: CREATE OPERATOR CLASS、ALTER OPERATOR FAMILY … ADD FUNCTION，指定的函数是btree sort support函数，则返回值类型必须是void。
+
+GAUSS-01446: "hash procedures must return integer"
+
+SQLSTATE: 42P17
+
+错误原因: CREATE OPERATOR CLASS、ALTER OPERATOR FAMILY … ADD FUNCTION，access_method是hash，但是返回值类型不是int。
+
+解决办法: CREATE OPERATOR CLASS、ALTER OPERATOR FAMILY … ADD FUNCTION，access_method是hash，则返回值类型必须是int。
+
+GAUSS-01447: "associated data types must be specified for index support procedure"
+
+SQLSTATE: 42P17
+
+错误原因: CREATE OPERATOR CLASS没有指定合法的FOR TYPE data_type，ALTER OPERATOR FAMILY … ADD OPERATOR没有指定左或右参数类型。
+
+解决办法: CREATE OPERATOR CLASS必须指定合法的FOR TYPE data_type，ALTER OPERATOR FAMILY … ADD OPERATOR须得指定左参数类型或者右参数类型。
+
+GAUSS-01448: "procedure number %d for (%s,%s) appears more than once"
+
+SQLSTATE: 42P17
+
+错误原因: CREATE OPERATOR CLASS、ALTER OPERATOR FAMILY … ADD/DROP procedure，相同的函数出现了多次。
+
+解决办法: CREATE OPERATOR CLASS、ALTER OPERATOR FAMILY … ADD/DROP procedure，确保一个SQL语句中不要出现重复函数。
+
+GAUSS-01449: "operator number %d for (%s,%s) appears more than once"
+
+SQLSTATE: 42P17
+
+错误原因: CREATE OPERATOR CLASS、ALTER OPERATOR FAMILY … ADD/DROP operator，相同的操作符出现了多次。
+
+解决办法: CREATE OPERATOR CLASS、ALTER OPERATOR FAMILY … ADD/DROP operator，确保一个SQL语句中不要出现重复的操作符。
+
+GAUSS-01450: "operator %d(%s,%s) already exists in operator family '%s'"
+
+SQLSTATE: 42710
+
+错误原因: CREATE OPERATOR CLASS、ALTER OPERATOR FAMILY … ADD/DROP operator，已经存在了相同的operator。
+
+解决办法: CREATE OPERATOR CLASS、ALTER OPERATOR FAMILY … ADD/DROP operator之前，确保添加的operator在指定的operator family中尚未存在。
+
+<br/>
+
+## GAUSS-01451 - GAUSS-01460
+
+<br/>
+
+GAUSS-01451: "function %d(%s,%s) already exists in operator family '%s'"
+
+SQLSTATE: 42710
+
+错误原因: CREATE OPERATOR CLASS、ALTER OPERATOR FAMILY … ADD/DROP function，已经存在了相同的function。
+
+解决办法: CREATE OPERATOR CLASS、ALTER OPERATOR FAMILY … ADD/DROP function之前，确保添加的function在指定的operator family中尚未存在。
+
+GAUSS-01452: "operator %d(%s,%s) does not exist in operator family '%s'"
+
+SQLSTATE: 42704
+
+错误原因: ALTER OPERATOR FAMILY … DROP operator，但是指定的operator不存在。
+
+解决办法: ALTER OPERATOR FAMILY … DROP operator，必须确保指定的operator在指定的operator family中存在。
+
+GAUSS-01453: "function %d(%s,%s) does not exist in operator family '%s'"
+
+SQLSTATE: 42704
+
+错误原因: ALTER OPERATOR FAMILY … DROP function，但是指定的function不存在。
+
+解决办法: ALTER OPERATOR FAMILY … DROP function，必须确保指定的function在指定的operator family中存在。
+
+GAUSS-01454: "could not find tuple for amop entry %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01455: "could not find tuple for amproc entry %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01456: "operator class '%s' for access method '%s' already exists in schema '%s'"
+
+SQLSTATE: 42710
+
+错误原因: ALTER OPERATOR CLASS name USING index_method RENAME TO new_name，但是新名称在schema中已经存在了。
+
+解决办法: ALTER OPERATOR CLASS name USING index_method RENAME TO new_name，首先确保新名称在schema中不存在。
+
+GAUSS-01457: "operator family '%s' for access method '%s' already exists in schema '%s'"
+
+SQLSTATE: 42710
+
+错误原因: ALTER OPERATOR FAMILY name USING index_method RENAME TO new_name，但是新名称在schema中已经存在了。
+
+解决办法: ALTER OPERATOR FAMILY name USING index_method RENAME TO new_name，首先确保新名称在schema中不存在。
+
+GAUSS-01458: "SETOF type not allowed for operator argument"
+
+SQLSTATE: 42P13
+
+错误原因: CREATE OPERATOR，左参数或右参数是SETOF类型（集合）。
+
+解决办法: CREATE OPERATOR，左参数和右参数都不能是SETOF类型（集合）。
+
+GAUSS-01459: "operator procedure must be specified"
+
+SQLSTATE: 42P13
+
+错误原因: CREATE OPERATOR，没有指定procedure。
+
+解决办法: CREATE OPERATOR，必须指定procedure。
+
+GAUSS-01460: "at least one of leftarg or rightarg must be specified"
+
+SQLSTATE: 42P13
+
+错误原因: CREATE OPERATOR，既没有指定LEFTARG，也没有指定RIGHTARG。
+
+解决办法: CREATE OPERATOR，LEFTARG和RIGHTARG，起码指定一个。
+
+<br/>
+
+## GAUSS-01461 - GAUSS-01470
+
+<br/>
+
+GAUSS-01461: "restriction estimator function %s must return type 'float8'"
+
+SQLSTATE: 42P17
+
+错误原因: CREATE OPERATOR，指定的RESTRICT函数返回值不是float8类型。
+
+解决办法: CREATE OPERATOR，指定的RESTRICT函数返回值必须是float8类型。
+
+GAUSS-01462: "join estimator function %s must return type 'float8'"
+
+SQLSTATE: 42P17
+
+错误原因: CREATE OPERATOR，指定的JOIN函数返回值不是float8类型。
+
+解决办法: CREATE OPERATOR，指定的JOIN函数返回值必须是float8类型。
+
+GAUSS-01464: "invalid cursor name: must not be empty"
+
+SQLSTATE: 34000
+
+错误原因: DECLARE/CLOSE/FETCH/MOVE CURSOR时，没有指定CURSOR的名称。
+
+解决办法: DECLARE/CLOSE/FETCH/MOVE CURSOR时，必须指定CURSOR的名称。
+
+GAUSS-01465: "cursor '%s' does not exist"
+
+SQLSTATE: 34000
+
+错误原因: FETCH/MOVE/CLOSE CURSOR/CURRENT OF/XML CURSOR操作时，指定CURSOR的名称不存在。
+
+解决办法: FETCH/MOVE/CLOSE CURSOR/CURRENT OF/XML CURSOR操作时，指定CURSOR的名称必须存在。
+
+GAUSS-01466: "portal '%s' cannot be run"
+
+SQLSTATE: 55000
+
+错误原因: This is an internal error.（portal内部状态不正确）
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01467: "could not reposition held cursor"
+
+SQLSTATE: 55000
+
+错误原因: This is an internal error.（portal内部状态不正确）。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01468: "unexpected end of tuple stream"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01469: "unrecognized rename stmt type: %d"
+
+SQLSTATE: XX000
+
+错误原因: ALTER..RENAME TO..语法中Alter对象类型错误。
+
+解决办法: 请参照《SQL指南》中ALTER..RENAME TO..语法对应Alter对象的类型。
+
+GAUSS-01470: "unrecognized AlterObjectSchemaStmt type: %d"
+
+SQLSTATE: XX000
+
+错误原因: ALTER..SET SCHEMA..语法中Alter对象类型错误。
+
+解决办法: 请参照《SQL指南》中ALTER..SET SCHEMA..语法对应Alter对象的类型。
+
+<br/>
+
+## GAUSS-01471 - GAUSS-01480
+
+<br/>
+
+GAUSS-01471: "cache lookup failed for object %u of catalog '%s'"
+
+SQLSTATE: XX000
+
+错误原因: ALTER..SET TABLESPACE..语法处理过程中从Cache获取Alter对象失败。
+
+解决办法: 由于系统Cache存在异常导致根据Alter对象OID从Cache获取对象tuple失败，请联系技术支持工程师提供技术支持。
+
+GAUSS-01472: "must be system admin to set schema of %s"
+
+SQLSTATE: 42501
+
+错误原因: 修改对象的namespace，但是使用的帐户不是系统管理员。
+
+解决办法: 修改对象的namespace，使用的帐户必须是系统管理员。
+
+GAUSS-01473: "%s already exists in schema '%s'"
+
+SQLSTATE: 42710
+
+错误原因: 修改对象的namespace，但是对象在新的schema内已经存在。
+
+解决办法: 修改对象的namespace，确保对象在新的schema内不存在。
+
+GAUSS-01474: "unrecognized AlterOwnerStmt type: %d"
+
+SQLSTATE: XX000
+
+错误原因: ALTER..OWNER TO..语法中Alter对象类型错误。
+
+解决办法: 请参照《SQL指南》中ALTER..OWNER TO..语法对应Alter对象的类型。
+
+GAUSS-01475: "Table %s does not support sampling operation for analyze."
+
+SQLSTATE: 42703
+
+错误原因: 对于gds外表不支持analyze采样操作。
+
+解决办法: gds外表不支持analyze。
+
+GAUSS-01476: "unsupported datatype"
+
+SQLSTATE: XX000
+
+错误原因: 对列存表进行analyze时，列存表中包含不支持的数据类型。
+
+解决办法: 请检查列存表定义是否正常，如果异常请重新创建列存表。如果仍然上报该错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-01477: "extension '%s' does not exist"
+
+SQLSTATE: 42704
+
+错误原因: CREATE EXTENSION或者ALTER EXTENSION时，发现了EXTENSION不存在的情况。
+
+解决办法: CREATE EXTENSION时，确保依赖的EXTENSION存在；ALTER EXTENSION时，只能ALTER已经存在的EXTENSION。
+
+GAUSS-01478: "invalid extension name: '%s'"
+
+SQLSTATE: 22023
+
+错误原因: CREATE EXTENSION时，EXTENSION名称非法。
+
+解决办法: CREATE EXTENSION时，EXTENSION名称不能出现以下4种情况之一: （1）无名；（2）包含-；（3）以-开头或结束；（4）包含文件夹间隔符如/或者\\。
+
+GAUSS-01479: "invalid extension version name: '%s'"
+
+SQLSTATE: 22023
+
+错误原因: CREATE EXTENSION时，VERSION名称非法，或ALTER EXTENSION时，new_version/default_version非法。
+
+解决办法: CREATE EXTENSION时或ALTER EXTENSION时，version/new_version/default_version不能出现以下情况: （1）无名；（2）包含-；（3）以-开头或结束；（4）包含文件夹间隔符如/或者\\。
+
+<br/>
+
+## GAUSS-01481 - GAUSS-01490
+
+<br/>
+
+GAUSS-01481: "parameter '%s' cannot be set in a secondary extension control file"
+
+SQLSTATE: 42601
+
+错误原因: CREATE EXTENSION时或ALTER EXTENSION时或执行EXTENSION相关的系统函数时，在secondary control file中指定了default_version或者directory参数。
+
+解决办法: CREATE EXTENSION时或ALTER EXTENSION时或执行EXTENSION相关的系统函数时，不能在secondary control file中指定default_version或者directory参数。
+
+GAUSS-01482: "parameter '%s' requires a Boolean value"
+
+SQLSTATE: 22023
+
+错误原因: "(1)CREATE EXTENSION时或ALTER EXTENSION时或执行EXTENSION相关的系统函数时，在控制文件中没有给参数relocatable/sysadmin指定一个BOOL值。
+
+解决办法: "(1)CREATE EXTENSION时或ALTER EXTENSION时或执行EXTENSION相关的系统函数时，在控制文件中，必须给参数relocatable/sysadmin指定一个BOOL值。
+
+GAUSS-01483: "'%s' is not a valid encoding name"
+
+SQLSTATE: 42704
+
+错误原因: CREATE EXTENSION时或ALTER EXTENSION时或执行EXTENSION相关的系统函数时，在控制文件中没有给参数encoding指定一个合法的encoding名称。
+
+解决办法: CREATE EXTENSION时或ALTER EXTENSION时或执行EXTENSION相关的系统函数时，在控制文件中必须给参数encoding指定一个合法的encoding名称。
+
+GAUSS-01484: "parameter '%s' must be a list of extension names"
+
+SQLSTATE: 22023
+
+错误原因: CREATE EXTENSION时或ALTER EXTENSION时或执行EXTENSION相关的系统函数时，在控制文件中没有给参数requires指定a list of extension names
+
+解决办法: CREATE EXTENSION时或ALTER EXTENSION时或执行EXTENSION相关的系统函数时，在控制文件中必须给参数requires指定a list of extension names
+
+GAUSS-01485: "unrecognized parameter '%s' in file '%s'"
+
+SQLSTATE: 42601
+
+错误原因: CREATE EXTENSION时或ALTER EXTENSION时或执行EXTENSION相关的系统函数时，在控制文件中指定了非法参数。
+
+解决办法: CREATE EXTENSION时或ALTER EXTENSION时或执行EXTENSION相关的系统函数时，在控制文件中仅可指定如下参数。directory/default_version/module_pathname/comment/schema/relocatable/sysadmin/encoding/requires。
+
+GAUSS-01486: "parameter 'schema' cannot be specified when 'relocatable' is true"
+
+SQLSTATE: 42601
+
+错误原因: CREATE EXTENSION时或ALTER EXTENSION时或执行EXTENSION相关的系统函数时，在控制文件中，当指定relocatable为true时，同时又指定了schema参数。
+
+解决办法: CREATE EXTENSION时或ALTER EXTENSION时或执行EXTENSION相关的系统函数时，在控制文件中，当指定relocatable为true时，不能再指定了schema参数。
+
+GAUSS-01487: "transaction control statements are not allowed within an extension script"
+
+SQLSTATE: 0A000
+
+错误原因: CREATE EXTENSION时或ALTER EXTENSION时，EXTENSION的SQL脚本文件中出现了控制事务的SQL语句。
+
+解决办法: CREATE EXTENSION时或ALTER EXTENSION时，EXTENSION的SQL脚本文件中不能使用控制事务的SQL语句。
+
+GAUSS-01488: "permission denied to create extension '%s'"
+
+SQLSTATE: 42501
+
+错误原因: CREATE EXTENSION时，EXTENSION的控制文件要求必须以系统管理员权限运行，但是实际帐户不是系统管理员。
+
+解决办法: CREATE EXTENSION时，EXTENSION的控制文件要求必须以系统管理员权限运行，则实际帐户也必须是系统管理员。
+
+GAUSS-01489: "permission denied to update extension '%s'"
+
+SQLSTATE: 42501
+
+错误原因: ALTER EXTENSION时，EXTENSION的控制文件要求必须以系统管理员权限运行，但是实际帐户不是系统管理员。
+
+解决办法: ALTER EXTENSION时，EXTENSION的控制文件要求必须以系统管理员权限运行，则实际帐户也必须是系统管理员。
+
+GAUSS-01490: "extension '%s' has no update path from version '%s' to version '%s'"
+
+SQLSTATE: 22023
+
+错误原因: CREATE EXTENSION/ALTER EXTENSION时，不存在从旧版本到新版本的更新路径。
+
+解决办法: CREATE EXTENSION/ALTER EXTENSION时，如果有版本FROM old_version、UPDATE TO new_version，确保新旧版本号对应的SQL文件名称和路径的正确性。
+
+<br/>
+
+## GAUSS-01491 - GAUSS-01500
+
+<br/>
+
+GAUSS-01492: "nested CREATE EXTENSION is not supported"
+
+SQLSTATE: 0A000
+
+错误原因: CREATE EXTENSION时，SQL中嵌套创建EXTENSION。
+
+解决办法: CREATE EXTENSION时，SQL中不允许嵌套创建EXTENSION。
+
+GAUSS-01493: "unrecognized option: %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01494: "version to install must be specified"
+
+SQLSTATE: 22023
+
+错误原因: CREATE/ALTER EXTENSION时，既没有指定new version，控制文件中也没有指定default version。
+
+解决办法: CREATE/ALTER EXTENSION时，要么指定new version，要么在控制文件中指定default version。
+
+GAUSS-01495: "FROM version must be different from installation target version '%s'"
+
+SQLSTATE: 22023
+
+错误原因: CREATE EXTENSION时，FROM版本号和VERSION版本号指定的版本号相同。
+
+解决办法: CREATE EXTENSION时，FROM版本号和VERSION版本号指定的版本号必须不同。
+
+GAUSS-01496: "extension '%s' must be installed in schema '%s'"
+
+SQLSTATE: 0A000
+
+错误原因: CREATE EXTENSION时，WITH SCHEMA指定的schema和控制文件中指定的schema不同。
+
+解决办法: CREATE EXTENSION时，WITH SCHEMA指定的schema必须与控制文件中指定的schema相同。
+
+GAUSS-01497: "there is no default creation target"
+
+SQLSTATE: XX000
+
+错误原因: CREATE EXTENSION语法中当不指定SCHEMA选项时，默认当前缺省的SCHEMA，但当前缺省的SCHEMA路径为空值。
+
+解决办法: 当前缺省的SCHEMA为空，当前系统存在异常或存在人为删除当前SCHEMA的目录导致，请联系技术支持工程师提供技术支持。
+
+GAUSS-01498: "required extension '%s' is not installed"
+
+SQLSTATE: 42704
+
+错误原因: CREATE EXTENSION/ALTER EXTENSION时，控制文件中指定的依赖的某个EXTENSION尚未安装。
+
+解决办法: CREATE EXTENSION/ALTER EXTENSION时，控制文件中指定的所有EXTENSION必须已经安装，已安装的EXTENSION可以通过\\dx查看。
+
+GAUSS-01499: "cannot drop extension '%s' because it is being modified"
+
+SQLSTATE: 55000
+
+错误原因: DROP EXTENSION时，EXTENSION正在被别的session修改。
+
+解决办法: DROP EXTENSION时，EXTENSION不能正在被别的session修改。
+
+GAUSS-01500: "pg_extension_config_dump() can only be called from an SQL script executed by CREATE EXTENSION"
+
+SQLSTATE: 0A000
+
+错误原因: pg_extension_config_dump没有在CREATE EXTENSION的SQL脚本文件中执行。
+
+解决办法: pg_extension_config_dump只能在CREATE EXTENSION的SQL脚本文件中执行。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/16-GAUSS-01501-GAUSS-01600.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/16-GAUSS-01501-GAUSS-01600.md
new file mode 100644
index 0000000000000000000000000000000000000000..76831e85be761605908ed8f84f00a0cdb37e7d43
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/16-GAUSS-01501-GAUSS-01600.md
@@ -0,0 +1,644 @@
+---
+title: GAUSS-01501 - GAUSS-01600
+summary: GAUSS-01501 - GAUSS-01600
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-01501 - GAUSS-01600
+
+<br/>
+
+## GAUSS-01501 - GAUSS-01510
+
+<br/>
+
+GAUSS-01501: "OID %u does not refer to a table"
+
+SQLSTATE: 42P01
+
+错误原因: pg_extension_config_dump()函数的参数1不是pg_class内定义的表。
+
+解决办法: pg_extension_config_dump()函数的参数1必须是pg_class内定义的表。
+
+GAUSS-01502: "table '%s' is not a member of the extension being created"
+
+SQLSTATE: 55000
+
+错误原因: pg_extension_config_dump()函数的参数1不是正在创建的EXTENSION的成员。
+
+解决办法: pg_extension_config_dump()函数的参数1必须是正在创建的EXTENSION的成员。
+
+GAUSS-01503: "extension with oid %u does not exist"
+
+SQLSTATE: XX000
+
+错误原因: 根据当前extension对象的OID从Cache中查找系统表pg_extension的tuple错误。
+
+解决办法: 由于系统Cache存在异常导致根据extension对象OID从Cache获取对象tuple失败，请联系技术支持工程师提供技术支持。
+
+GAUSS-01504: "extconfig is not a 1-D Oid array"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01505: "extconfig and extcondition arrays do not match"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01507: "extension name cannot be qualified"
+
+SQLSTATE: 42601
+
+错误原因: ALTER EXTENSION SET SCHEMA，指定EXTENSION名称时，extension的前面加了schema名称。
+
+解决办法: ALTER EXTENSION SET SCHEMA，指定EXTENSION名称时，extension的前面不可以加schema名称。
+
+GAUSS-01508: "cannot move extension '%s' into schema '%s' because the extension contains the schema"
+
+SQLSTATE: 55000
+
+错误原因: ALTER EXTENSION SET SCHEMA，新的schema是当前EXTENSION的成员。
+
+解决办法: ALTER EXTENSION SET SCHEMA，新的schema不可以是当前EXTENSION的成员。
+
+GAUSS-01509: "extension '%s' does not support SET SCHEMA"
+
+SQLSTATE: 0A000
+
+错误原因: ALTER EXTENSION SET SCHEMA，当前EXTENSION的relocatable参数为false。
+
+解决办法: 只对EXTENSION的relocatable参数为true的EXTENSION执行ALTER EXTENSION SET SCHEMA。
+
+<br/>
+
+## GAUSS-01511 - GAUSS-01520
+
+<br/>
+
+GAUSS-01511: "nested ALTER EXTENSION is not supported"
+
+SQLSTATE: 0A000
+
+错误原因: ALTER EXTENSION UPDATE，在一个事务内执行多次。
+
+解决办法: ALTER EXTENSION UPDATE，在一个事务内只允许执行一次。
+
+GAUSS-01513: "%s is already a member of extension '%s'"
+
+SQLSTATE: 55000
+
+错误原因: "(1)ALTER EXTENSION ADD，添加的对象已经是EXTENSION的成员了。(2)CREATE EXTENSION，EXTENSION的SQL脚本文件内创建的某个对象已经是别的EXTENSION的成员了。"
+
+解决办法: "(1)ALTER EXTENSION ADD，添加的对象必须尚未是EXTENSION的成员了。(2)CREATE EXTENSION，EXTENSION的SQL脚本文件内创建的所有对象都不能是别的EXTENSION的成员。"
+
+GAUSS-01514: "cannot add schema '%s' to extension '%s' because the schema contains the extension"
+
+SQLSTATE: 55000
+
+错误原因: ALTER EXTENSION ADD，ADD的schema就是EXTENSION所在的schema。
+
+解决办法: ALTER EXTENSION ADD，ADD的schema不能是EXTENSION所在的schema。
+
+GAUSS-01515: "%s is not a member of extension '%s'"
+
+SQLSTATE: 55000
+
+错误原因: ALTER EXTENSION DROP，删除的对象尚不是EXTENSION的成员。
+
+解决办法: ALTER EXTENSION DROP，删除的对象必须是EXTENSION的成员。
+
+GAUSS-01517: "cache lookup failed for extension %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01518: "no security label providers have been loaded"
+
+SQLSTATE: 22023
+
+错误原因: 执行SECURITY LABEL语句，没有加载SECURITY LABEL EXTENSION。
+
+解决办法: 执行SECURITY LABEL之前，加载相关SECURITY LABEL的EXTENSION。
+
+GAUSS-01519: "must specify provider when multiple security label providers have been loaded"
+
+SQLSTATE: 22023
+
+错误原因: 执行SECURITY LABEL语句，没有指定SECURITY LABEL。
+
+解决办法: 执行SECURITY LABEL语句，必须指定SECURITY LABEL。
+
+GAUSS-01520: "security label provider '%s' is not loaded"
+
+SQLSTATE: 22023
+
+错误原因: 执行SECURITY LABEL语句，指定的安全标记没有加载。
+
+解决办法: 执行SECURITY LABEL语句，仅指定加载的安全标记。
+
+<br/>
+
+## GAUSS-01521 - GAUSS-01530
+
+<br/>
+
+GAUSS-01521: "can't negate an empty subexpression"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01522: "unrecognized boolop: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01524: "could not find attribute %d in subquery targetlist"
+
+SQLSTATE: XX000
+
+错误原因: 子查询返回列为空。
+
+解决办法: 检查查询中子查询部分，是否存在空返回值问题。
+
+GAUSS-01525: "so where are the outer joins?"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01527: "reached base rel"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01528: "could not find join node %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01529: "subquery cannot be result relation"
+
+SQLSTATE: XX000
+
+错误原因: 子查询不能作为结果表。
+
+解决办法: 修改查询，使用非子查询作为输出表。
+
+GAUSS-01530: "unrecognized command_type: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-01531 - GAUSS-01540
+
+<br/>
+
+GAUSS-01531: "targetlist is not sorted correctly"
+
+SQLSTATE: XX000
+
+错误原因: 输出列顺序有误。
+
+解决办法: 调整输入列和insert/update列的顺序一致。
+
+GAUSS-01532: "unexpected outer reference in set operation subquery"
+
+SQLSTATE: XX000
+
+错误原因: setop中出现了交叉引用。
+
+解决办法: 检查查询中SETOP操作对应的输入列，是否存在与其他子查询的交叉引用。
+
+GAUSS-01533: "only UNION queries can be recursive"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01534: "could not implement recursive UNION"
+
+SQLSTATE: 0A000
+
+错误原因: 不能实现递归的UNION操作，所有列的类型都必须可哈希。
+
+解决办法: 调整相关列，所有列都得可哈希。
+
+GAUSS-01535: "could not implement %s"
+
+SQLSTATE: 0A000
+
+错误原因: 不能实现UNION，INTERSECT或者EXCEPT ，因为有的数据类型只支持哈希，另外一些类型只支持排序。
+
+解决办法: UNION，INTERSECT或者EXCEPT相关列都得可哈希且可排序
+
+GAUSS-01536: "could not find inherited attribute '%s' of relation '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01537: "attribute '%s' of relation '%s' does not match parent's type"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01538: "attribute '%s' of relation '%s' does not match parent's collation"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01539: "attribute %d of relation '%s' does not exist"
+
+SQLSTATE: XX000
+
+错误原因: 表中某一列不存在。
+
+解决办法: 检查查询中，是否访问了不存在的列。
+
+GAUSS-01540: "failed to join all relations together"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-01541 - GAUSS-01550
+
+<br/>
+
+GAUSS-01541: "minimum_count not set"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01542: "neither shared nor minimum number nor random edge found"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01543: "no edge found"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01547: "could not find plan for CTE '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01549: "failed to build any %d-way joins"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-01551 - GAUSS-01560
+
+<br/>
+
+GAUSS-01551: "a join rel requires both the left path and right path"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01552: "can not create remote path for ranges of type %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01553: "can not create remote path for relation of type %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01554: "No node list provided for remote query path"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01557: "operator %u is not a valid ordering operator"
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01558: "volatile EquivalenceClass has no sortref"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-01561 - GAUSS-01570
+
+<br/>
+
+GAUSS-01563: "wrong number of index expressions"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01564: "unsupported indexqual type: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01566: "could not find member %d(%u,%u) of opfamily %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01570: "no = operator for opfamily %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-01571 - GAUSS-01580
+
+<br/>
+
+GAUSS-01571: "no >= operator for opfamily %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01572: "no < operator for opfamily %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01576: "unexpected datatype in string_to_const: %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01577: "left and right pathkeys do not match in mergejoin"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01579: "Unrecognised command type %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01580: "Postgres-XC does not support this distribution type yet"
+
+SQLSTATE: 0A000
+
+错误原因: 尚未支持的重分布数据类型。
+
+解决办法: 目前不支持对float、double等数据类型进行重分布，建议修改该列数据类型。
+
+<br/>
+
+## GAUSS-01581 - GAUSS-01590
+
+<br/>
+
+GAUSS-01581: "predicate_classify returned a bogus value"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01582: "too late to create a new PlaceHolderInfo"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01583: "rel %d already exists"
+
+SQLSTATE: XX000
+
+错误原因: 表已经存在。
+
+解决办法: 修改表名。
+
+GAUSS-01584: "no relation entry for relid %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01585: "unexpected node type in reltargetlist: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01587: "cannot access temporary or unlogged relations during recovery"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。恢复期间无法访问临时表或者UNLOGGED表。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01588: "unsupported RTE kind %d in build_physical_tlist"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01589: "invalid restriction selectivity: %f"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01590: "invalid join selectivity: %f"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-01591 - GAUSS-01600
+
+<br/>
+
+GAUSS-01591: "WindowFunc contains out-of-range winref %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01592: "cannot commute non-binary-operator clause"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01593: "could not find commutator for operator %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01595: "unexpected RowCompare type: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01596: "unrecognized nulltesttype: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01598: "function's resolved result type changed during planning"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01599: "null prosrc for function %u"
+
+SQLSTATE: 42P13
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01600: "unexpected paramkind: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/17-GAUSS-01601-GAUSS-01700.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/17-GAUSS-01601-GAUSS-01700.md
new file mode 100644
index 0000000000000000000000000000000000000000..947e54c7cf5fee971d1df0c5846ba82895bc7378
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/17-GAUSS-01601-GAUSS-01700.md
@@ -0,0 +1,732 @@
+---
+title: GAUSS-01601 - GAUSS-01700
+summary: GAUSS-01601 - GAUSS-01700
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-01601 - GAUSS-01700
+
+<br/>
+
+## GAUSS-01601 - GAUSS-01610
+
+<br/>
+
+GAUSS-01601: "invalid paramid: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01602: "Upper-level Var found where not expected"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01603: "Upper-level Aggref found where not expected"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01604: "Aggref found where not expected"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01605: "Upper-level PlaceHolderVar found where not expected"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01606: "PlaceHolderVar found where not expected"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01607: "could not devise a query plan for the given query"
+
+SQLSTATE: XX000
+
+错误原因: 计划产生失败。
+
+解决办法: 请检查查询是否合理，例如join方式是否合理等。
+
+GAUSS-01608: "ORDER/GROUP BY expression not found in targetlist"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01610: "relation %s is not partitioned"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。检测索引是否有不可用的分区，heap或者index不是分区的，或者不是范围分区。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-01611 - GAUSS-01620
+
+<br/>
+
+GAUSS-01611: "no local indexes found for partition %s"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。表分区上没有定义索引分区。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01612: "bit map error when searching for unusable index partition"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。查找不可用的index partition时，发生bit位错误。
+
+解决办法: 报错，事务回滚。
+
+GAUSS-01613: "bit map error after searching for unusable index partition"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。查找不可用的index partition时，发生bit位错误。
+
+解决办法: 报错，事务回滚。
+
+GAUSS-01614: "relation of oid='%u' is not partitioned table"
+
+SQLSTATE: XX000
+
+错误原因: PARTITION FOR子句中指定的表是非分区表。
+
+解决办法: PARTITION FOR子句中的表必须为分区表。
+
+GAUSS-01616: "fail to find partition with oid %u for partitioned table %u"
+
+SQLSTATE: 42P01
+
+错误原因: 系统内部错误。分区表下指定的分区找不到。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01617: "partitionPruningForExpr: parameter can not be null"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。剪枝时，得到的参数为NULL。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01618: "get null for partition pruning"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。剪枝时，得到的内部剪枝结果为NULL。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01619: "For every node in same expression, pruning result's intervalOffset MUST be same"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。同一表达式内的节点，其剪枝结果的最小interval分区序号必须相同。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01620: "pruning result(PartitionIdentifier) is invalid"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。根据一组上边界和下边界组成的一个范围，剪枝出来的结果是不正常的。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-01621 - GAUSS-01630
+
+<br/>
+
+GAUSS-01621: "unsupported partition key column range mode"
+
+SQLSTATE: 42P17
+
+错误原因: 系统内部错误。判断剪枝结果中的分区是否需要排除时，根据分区序号构造出来的某个内部结构非法。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01623: "Unupport partition strategy '%c'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。不支持的分区策略。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01624: "Expected TargetEntry node, but got node with type %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01625: "can not generate shippable query for base relations of type other than plain tables"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01626: "can not handle multiple relations in a single baserel"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01627: "a join relation path should have both left and right paths"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01628: "unexpected unshippable quals in JOIN tree"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01629: "join with unshippable join clauses can not be shipped"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-01631 - GAUSS-01640
+
+<br/>
+
+GAUSS-01631: "Creating remote query plan for relations of type %d is not supported"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01632: "expected a VAR node but got node of type %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01633: "No distribution information found for remote query path"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01634: "creating remote query plan for relations of type %d is not supported"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01635: "Unexpected node type: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01637: "Duplicate node_ids not expected in source target list"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01638: "Duplicate ctids not expected in source target list"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01640: "cache lookup failed for attribute %s of relation %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-01641 - GAUSS-01650
+
+<br/>
+
+GAUSS-01641: "Source data plan's target list does not contain ctid colum"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01642: "Unexpected command type: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01645: "column store doesn't support backward scan"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01646: "Distributed key column can't be updated in current version"
+
+SQLSTATE: 42P10
+
+错误原因: 更新分布列。
+
+解决办法: 不要更新分布列。
+
+GAUSS-01647: "could not find array type for datatype %s"
+
+SQLSTATE: XX000
+
+错误原因: 该数据类型不能支持array sublink方式。
+
+解决办法: 修改子查询的类型。
+
+GAUSS-01648: "unexpected PARAM_SUBLINK ID: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01649: "unexpected outer reference in CTE query"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01650: "could not find plan for CteScan referencing plan ID %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-01651 - GAUSS-01660
+
+<br/>
+
+GAUSS-01651: "plan should not reference subplan's variable"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01652: "failed to construct the join relation"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01653: "could not find equality operator for ordering operator %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01654: "failed to re-find MinMaxAggInfo record"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01655: "could not implement GROUP BY"
+
+SQLSTATE: 0A000
+
+错误原因: SELECT的Window子句，某些类型只支持hash，另外一些类型只支持sort，因此无法支持GROUP BY。
+
+解决办法: 修改GROUP BY子句，使用可哈希且可排序的列。
+
+GAUSS-01656: "could not implement DISTINCT"
+
+SQLSTATE: 0A000
+
+错误原因: SELECT的Window子句，某些类型只支持hash，另外一些类型只支持sort，因此无法支持DISTINCT。
+
+解决办法: 修改distinct子句，使用可哈希且可排序的列。
+
+GAUSS-01657: "failed to locate grouping columns"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01658: "resjunk output columns are not implemented"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01659: "could not implement window PARTITION BY"
+
+SQLSTATE: 0A000
+
+错误原因:  SELECT的Window子句，Window partitioning column不是可排序的数据类型，导致不能实现window PARTITION BY。
+
+解决办法: 修改PARTITION BY子句，使用可排序的列。
+
+GAUSS-01660: "could not implement window ORDER BY"
+
+SQLSTATE: 0A000
+
+错误原因: SELECT的Window子句，Window ordering column不是可排序的数据类型，导致不能实现window ORDER BY。
+
+解决办法: 修改ORDER BY子句，使用可排序的列。
+
+<br/>
+
+## GAUSS-01661 - GAUSS-01670
+
+<br/>
+
+GAUSS-01661: "failed to deconstruct sort operators into partitioning/ordering operators"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01662: "failed to assign all NestLoopParams to plan nodes"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01663: "MergeAppend child's targetlist doesn't match MergeAppend"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01664: "failed to find unique expression in subplan tlist"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01665: "could not find compatible hash operator for operator %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01666: "could not find ordering operator for equality operator %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01667: "could not find param ID for CTE '%s'"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01668: "unsupported RTE kind %d in build_one_column_tlist"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01669: "outer pathkeys do not match mergeclauses"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01670: "inner pathkeys do not match mergeclauses"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-01671 - GAUSS-01680
+
+<br/>
+
+GAUSS-01671: "indexqual clause is not binary opclause"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01672: "inconsistent results from adjust_rowcompare_for_index"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01673: "indexorderby clause is not binary opclause"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01674: "unsupported indexorderby type: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01675: "index key does not match expected index column"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01676: "could not find pathkey item to sort"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01678: "Fail to create path for partitioned table by the lack of info"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。为分区表的scan算子设置信息时，输入参数不合法。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01679: "Only Scan operator have patition attribute"
+
+SQLSTATE: XX000
+
+错误原因: 为分区表的非scan算子设置信息。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-01681 - GAUSS-01690
+
+<br/>
+
+GAUSS-01682: "NestLoopParam was not reduced to a simple Var"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01683: "variable not found in subplan target lists"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01684: "variable not found in subplan target list"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01685: "variable not found in base remote scan target lists"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01687: "SELECT FOR UPDATE/SHARE cannot be applied to the nullable side of an outer join"
+
+SQLSTATE: 0A000
+
+错误原因:  SELECT FOR UPDATE/SHARE不能应用于外连接可能是空值的一侧。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01688: "JOIN qualification cannot refer to other relations"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-01691 - GAUSS-01700
+
+<br/>
+
+GAUSS-01692: "cannot insert into view '%s'"
+
+SQLSTATE: 55000
+
+错误原因: insert view。
+
+解决办法: 不能插入到视图。
+
+GAUSS-01693: "cannot update view '%s'"
+
+SQLSTATE: 55000
+
+错误原因: 不能更新视图。
+
+解决办法: 需要ON UPDATE DO INSTEAD 规则或者 INSTEAD OF UPDATE trigger。
+
+GAUSS-01694: "cannot delete from view '%s'"
+
+SQLSTATE: 55000
+
+错误原因: 不能从视图中删除。
+
+解决办法: 需要ON UPDATE DO INSTEAD 规则或者 INSTEAD OF UPDATE trigger。
+
+GAUSS-01697: "invalid fork name"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01698: "invalid relation file path %s."
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01699: "invalid relation file path %s: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01700: "invalid relpersistence: %c"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/18-GAUSS-01701-GAUSS-01800.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/18-GAUSS-01701-GAUSS-01800.md
new file mode 100644
index 0000000000000000000000000000000000000000..d9e365bf5f16b58e74a920c9f92de802d42cf4b1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/18-GAUSS-01701-GAUSS-01800.md
@@ -0,0 +1,750 @@
+---
+title: GAUSS-01701 - GAUSS-01800
+summary: GAUSS-01701 - GAUSS-01800
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-01701 - GAUSS-01800
+
+<br/>
+
+## GAUSS-01701 - GAUSS-01710
+
+<br/>
+
+GAUSS-01702: "permission denied to create '%s.%s'"
+
+SQLSTATE: 42501
+
+错误原因: 创建表的模式不是系统锁允许的或者数据库对象所属名称空间不是系统所支持的，导致无法正常创建heap表。
+
+解决办法: 检查创建时使用的mode或者对象名所属名称空间是否正确拼写。
+
+GAUSS-01703: "column name '%s' specified more than once"
+
+SQLSTATE: 42701
+
+错误原因: 表格中存在重复的属性名。
+
+解决办法: 检查在定义表格时是否重复使用某一属性名称。
+
+GAUSS-01704: "column '%s' has pseudo-type %s"
+
+SQLSTATE: 42P16
+
+错误原因: 表格中存在未知的属性类型，导致属性检测失败。
+
+解决办法: 检查当前属性类型是否是系统所支持的。
+
+GAUSS-01705: "composite type %s cannot be made a member of itself"
+
+SQLSTATE: 42P16
+
+错误原因: 复合数据类型与当前数据类型列表中重名，这是不被允许的。
+
+解决办法: 检查复合数据类型是否与已有数据类型重名。
+
+GAUSS-01706: "no collation was derived for column '%s' with collatable type %s"
+
+SQLSTATE: 42P16
+
+错误原因: 属性列支持attcollation但是对应的attcollation无效，导致无法正常创建heap表格。
+
+解决办法: 检查创建表格时属性列关于collation定义的有效性。
+
+GAUSS-01707: "Invalid distribution column specified"
+
+SQLSTATE: 42P16
+
+错误原因: 用于标记分布情况的属性名并不在表格属性列中，导致属性列个数小于等于0，因此错误。
+
+解决办法: 检查distributeby语句中属性名是否存在于表定义的属性列中。
+
+GAUSS-01708: "Column %s is not a hash distributable data type"
+
+SQLSTATE: 42809
+
+错误原因: 该数据类型不支持作为hash分布列。
+
+解决办法: 检查手册查看哪些数据类型能够作为hash分布列被使用并检查当前使用的属性列对应的数据类型。
+
+GAUSS-01709: "Column %s is not modulo distributable data type"
+
+SQLSTATE: 42809
+
+错误原因: 该数据类型不支持作为modulo分布列。
+
+解决办法: 检查手册查看哪些数据类型能够作为modulo分布列被使用并检查当前使用的属性列对应的数据类型。
+
+GAUSS-01710: "Invalid distribution type"
+
+SQLSTATE: 42P16
+
+错误原因: distribute后面所使用的分布方式不是系统所支持的。
+
+解决办法: 检查当前所使用的分布方式是否是系统所支持的。
+
+<br/>
+
+## GAUSS-01711 - GAUSS-01720
+
+<br/>
+
+GAUSS-01712: "PGXC node %s: not a Datanode"
+
+SQLSTATE: 42601
+
+错误原因: 该名称对应的节点并不是一个DN类型的节点。
+
+解决办法: 检查nodeid的正确性并检查系统当前状态。
+
+GAUSS-01713: "PGXC Group %s: group not defined"
+
+SQLSTATE: 42704
+
+错误原因: group_name对应的节点组不存在。
+
+解决办法: 检查调用的group_name是否正确，或数据库在创建时是否正确创建group。
+
+GAUSS-01714: "shared relations must be placed in pg_global tablespace"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01715: "could not find attrdef tuple for relation %u attnum %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01716: "could not find tuple for attrdef %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01717: "could not remove file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 未能成功删除对应的错误信息表，导致出错。
+
+解决办法: 检查错误表的用户权限。
+
+GAUSS-01718: "cache lookup failed for foreign table %u"
+
+SQLSTATE: XX000
+
+错误原因: 无法找到对应的foreign data wrapper。
+
+解决办法: 请检查使用中的gds、hdfs外表以及roach、obs设置是否正确。
+
+GAUSS-01719: "cache lookup failed for partitioned table %u in pg_partition"
+
+SQLSTATE: XX000
+
+错误原因: 找不到分区表中相关的元组。
+
+解决办法: 检查relid对应的是否为分区表并检查该表的元组状况。
+
+GAUSS-01720: "check constraint '%s' already exists"
+
+SQLSTATE: 42710
+
+错误原因: 准备添加的限制已经存在，不能重复添加。
+
+解决办法: 检查需要新增加的限制是否已经存在。
+
+<br/>
+
+## GAUSS-01721 - GAUSS-01730
+
+<br/>
+
+GAUSS-01721: "null conbin for rel %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01722: "constraint '%s' conflicts with non-inherited constraint on relation '%s'"
+
+SQLSTATE: 42P17
+
+错误原因: 新的限制与表格中的非继承类限制相互冲突。
+
+解决办法: 检查需要新增加的限制是否与当前已有的所有类型限制相一致。
+
+GAUSS-01723: "cannot use column references in default expression"
+
+SQLSTATE: 42P10
+
+错误原因: default表达式中含有表格属性变量。
+
+解决办法: 检查sql语句中的default表达式中是否含有属性变量名。
+
+GAUSS-01724: "default expression must not return a set"
+
+SQLSTATE: 42804
+
+错误原因: default表达式返回的是个集合，这是不被允许的。
+
+解决办法: 检查sql语句中的default表达式中其返回值是否可能为集合。
+
+GAUSS-01725: "cannot use subquery in default expression"
+
+SQLSTATE: 0A000
+
+错误原因: default表达式中含有子查询，这是不允许的。
+
+解决办法: 检查sql语句中的default表达式是否使用子查询语句。
+
+GAUSS-01727: "cannot use window function in default expression"
+
+SQLSTATE: 42P20
+
+错误原因: default表达式中含有窗口函数，这是不被允许的。
+
+解决办法: 检查sql语句中的default表达式是否使用窗口函数。
+
+GAUSS-01728: "column '%s' is of type %s but default expression is of type %s"
+
+SQLSTATE: 42804
+
+错误原因: 属性的类型与调用的对应default表达式的返回类型不一致。
+
+解决办法: 检查相应的表达式并进行重写。
+
+GAUSS-01729: "only table '%s' can be referenced in check constraint"
+
+SQLSTATE: 42P10
+
+错误原因: 当前检查的限制条件只针对某个表，而不可以跨表检查。
+
+解决办法: 检查限制条件所对应的表格名或检查解析后表达式所对应表是否与实际吻合。
+
+GAUSS-01730: "unsupported ON COMMIT and foreign key combination"
+
+SQLSTATE: 0A000
+
+错误原因: 当前表2的外键是表1的主键，即表2引用了表1，但是在COMMIT的设置上并不相同。
+
+解决办法: 检查两张表格在COMMIT设置上是否相同。
+
+<br/>
+
+## GAUSS-01731 - GAUSS-01740
+
+<br/>
+
+GAUSS-01731: "cannot truncate a table referenced in a foreign key constraint"
+
+SQLSTATE: 0A000
+
+错误原因: 不能truncate被另外一张表外键限制所引用的表格。
+
+解决办法: 检查当前需truncate表格是否被其他表格引用，如果如此，应同时删除。
+
+GAUSS-01732: "buildPartitionKey(): partKeys specified NONE IS found'"
+
+SQLSTATE: 22015
+
+错误原因: 没有找到与表格中属性相对应的partKeys。
+
+解决办法: 检查创建分区表时是否正确给出了partKeys。
+
+GAUSS-01733: "cache lookup failed for partition %u"
+
+SQLSTATE: XX000
+
+错误原因: 缓存中分区查找失败。
+
+解决办法: 建议更换为有效分区。
+
+GAUSS-01734: "missing definition for new partition"
+
+SQLSTATE: XX000
+
+错误原因: 所需增加的新的分区没有定义。
+
+解决办法: 确定在添加新的分区前该分区被正确定义。
+
+GAUSS-01735: "boundary not defined for new partition"
+
+SQLSTATE: XX000
+
+错误原因: 新增加的分区中没有定义边界。
+
+解决办法: 确保新增加的分区中正确定义了新分区的边界。
+
+GAUSS-01736: "too many partition keys, allowed is %d"
+
+SQLSTATE: XX000
+
+错误原因: 新增加的分区中定义的边界个数超过了所允许的增加的最大分区数。
+
+解决办法: 确保每次新增加的分区个数不超过所允许增加的分区个数。
+
+GAUSS-01737: "number of partition key columns MUST less or equal than 4"
+
+SQLSTATE: XX000
+
+错误原因: 分区的分区属性列个数必须小于或等于4。
+
+解决办法: 检查原有分区表中用于分区的属性列(partition key)个数是否在允许范围内。
+
+GAUSS-01738: "inserted partition key does not map to any table partition"
+
+SQLSTATE: P0002
+
+错误原因: 插入的元组的分区键值和任意一个已存在的分区键都匹配不上。
+
+解决办法: 建议检查插入的数据是否存在超出分区表分区范围。
+
+GAUSS-01739: "Inserted partition key does not map to any table partition"
+
+SQLSTATE: P0002
+
+错误原因: 新插入的分区键是无法进行识别的。
+
+解决办法: 检查插入的分区键是否与当前的分区相互匹配。
+
+<br/>
+
+## GAUSS-01741 - GAUSS-01750
+
+<br/>
+
+GAUSS-01742: "cannot have more than %d keys in a cluster key"
+
+SQLSTATE: 54011
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01743: "partial cluster key constraint does not support row/timeseries store"
+
+SQLSTATE: 42P16
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01744: "'%s' is not a valid operator name"
+
+SQLSTATE: 42602
+
+错误原因: 想要创建的操作名称是不合法的。
+
+解决办法: 检查创建的操作名称是否是合法的，包括名称的长度，名称中是否包含无效的字符，是否包含不允许的标记符等，具体可见validOperatorName函数。
+
+GAUSS-01745: "only binary operators can have commutators"
+
+SQLSTATE: 42P13
+
+错误原因: 针对存在左右变量的场景，只有binary类型的操作才可包含转向(commutators)运算。
+
+解决办法: 请检查需要创建的operator是否是binary operators。
+
+GAUSS-01746: "only binary operators can have join selectivity"
+
+SQLSTATE: 42P13
+
+错误原因: 针对存在左右变量的场景，只有binary类型的操作才可计算连接选择率(join selectivity)。
+
+解决办法: 请检查需要创建的operator是否是binary operators。
+
+GAUSS-01748: "only binary operators can hash"
+
+SQLSTATE: 42P13
+
+错误原因: 针对存在左右变量的场景，只有binary类型的操作才可用于mergejoin路径。
+
+解决办法: 请检查需要创建的operator是否是binary operators。
+
+GAUSS-01749: "only boolean operators can have negators"
+
+SQLSTATE: 42P13
+
+错误原因: 只有布尔类型的操作返回值才可支持否操作。
+
+解决办法: 请检查需要创建的operator是否是Boolean类型。
+
+GAUSS-01750: "only boolean operators can have restriction selectivity"
+
+SQLSTATE: 42P13
+
+错误原因: 只有布尔类型的操作返回值才可计算限制性条件的选择率。
+
+解决办法: 请检查需要创建的operator是否是Boolean类型。
+
+<br/>
+
+## GAUSS-01751 - GAUSS-01760
+
+<br/>
+
+GAUSS-01751: "only boolean operators can have join selectivity"
+
+SQLSTATE: 42P13
+
+错误原因: 只有布尔类型的操作返回值才可计算连接选择率。
+
+解决办法: 请检查需要创建的operator是否是Boolean类型。
+
+GAUSS-01753: "only boolean operators can hash"
+
+SQLSTATE: 42P13
+
+错误原因: 只有布尔类型的操作返回值才可用于生成hash路径。
+
+解决办法: 请检查需要创建的operator是否是Boolean类型。
+
+GAUSS-01754: "operator %s already exists"
+
+SQLSTATE: 42723
+
+错误原因: 当前想要创建的操作已经存在。
+
+解决办法: 请检查需要创建的operator是否已经存在。
+
+GAUSS-01755: "operator cannot be its own negator or sort operator"
+
+SQLSTATE: 42P13
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+G
+
+GAUSS-01758: "large object %u does not exist"
+
+SQLSTATE: 42704
+
+错误原因: 当前大对象名所对应的对象实际并不存在。
+
+解决办法: 检查是否创建过该名称的大对象或检查是否在执行中被清除。
+
+GAUSS-01759: "unrecognized objtype: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01760: "must specify relation and object name"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-01761 - GAUSS-01770
+
+<br/>
+
+GAUSS-01761: "column name must be qualified"
+
+SQLSTATE: 42601
+
+错误原因: 在对象中属性名称必须是已知被描述的。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01762: "must be owner of large object %u"
+
+SQLSTATE: 42501
+
+错误原因: 对该大对象数据的所有权关系错误。
+
+解决办法: 检查通过get_object_address处所获得的大对象数据Id并于此处的进行比对。
+
+GAUSS-01763: "must be system admin"
+
+SQLSTATE: 42501
+
+错误原因: 该对象被初始用户所拥有，但是该对象的持有者却并非被初始用户所拥有。
+
+解决办法: 检查在定义该对象时，是否正确继承相关用户权限。
+
+GAUSS-01764: "must have CREATEROLE privilege"
+
+SQLSTATE: 42501
+
+错误原因: 如果不是初始用户，那至少是拥有基本的创建对象权限。
+
+解决办法: 检查持有该对象数据的用户权限，并核对对象的有效性。
+
+GAUSS-01765: "unrecognized object type: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01766: "cache lookup failed for cache %d oid %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01767: "unrecognized class id: %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01768: "temporary tables cannot specify a schema name"
+
+SQLSTATE: 42P16
+
+错误原因: 当前的临时表并不在创建临时表所创建的临时表空间中，即临时表所属的是其他空间，因此错误。
+
+解决办法: 检查创建临时表时临时表空间是否被正确创建，并查看对应的临时表空间的OID。
+
+<br/>
+
+## GAUSS-01771 - GAUSS-01780
+
+<br/>
+
+GAUSS-01771: "cannot create relations in temporary schemas of other sessions"
+
+SQLSTATE: 42P16
+
+错误原因: 不可在其它sessions的临时表空间中创建表。
+
+解决办法: 创建表之前需确认当前的sessions。
+
+GAUSS-01772: "cannot create temporary relation in non-temporary schema"
+
+SQLSTATE: 42P16
+
+错误原因: 不可在非临时表空间中创建临时表。
+
+解决办法: 在创建临时表之前需先确认当时的空间名。
+
+GAUSS-01773: "only temporary relations may be created in temporary schemas"
+
+SQLSTATE: 42P16
+
+错误原因: 在临时模式(或表空间)中只可能创建临时表。
+
+解决办法: 在创建对象前应先确认空间名，并依据表空间的特性来创建相应的对象
+
+GAUSS-01774: "text search parser '%s' does not exist"
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01775: "text search dictionary '%s' does not exist"
+
+SQLSTATE: 42704
+
+错误原因: TS文件路径找不到或者不存在。
+
+解决办法: 检查数据库实际创建的文件目录并核实路径的正确性。
+
+GAUSS-01776: "text search template '%s' does not exist"
+
+SQLSTATE: 42704
+
+错误原因: 模板数据库不存在，因此其文件路径也是无效的。
+
+解决办法: 检查在创建数据库初始阶段是否正确创建了模板数据库，并检查模板数据库的文件路径是否正确。
+
+GAUSS-01777: "%s is already in schema '%s'"
+
+SQLSTATE: 42P07
+
+错误原因: 在当前表空间中已经存在该对象。
+
+解决办法: 查询系统表，检查此模式中是否已经有同名对象。
+
+GAUSS-01778: "cannot move objects into or out of temporary schemas"
+
+SQLSTATE: 0A000
+
+错误原因: 不可在临时表空间中进行移入或移出某个对象的操作。
+
+解决办法: 请确认需要移动的对象的来源和目的地是否是一个临时表空间，如果是，将不被允许。
+
+GAUSS-01780: "cannot move objects into CSTORE schema"
+
+SQLSTATE: 0A000
+
+错误原因: 列存暂不支持移入其他表空间的对象。
+
+解决办法: 请确认当前表空间类型，如果为列存表空间，将不支持移入相关数据对象。
+
+<br/>
+
+## GAUSS-01781 - GAUSS-01790
+
+<br/>
+
+GAUSS-01781: "cannot move objects into system schema"
+
+SQLSTATE: 0A000
+
+错误原因: 不可将对象移入系统表空间。
+
+解决办法: 请确认当前表空间类型，如果为系统表空间，将不支持移入相关数据对象。
+
+GAUSS-01782: "improper relation name (too many dotted names): %s"
+
+SQLSTATE: 42601
+
+错误原因: 导入的表名称不合法。
+
+解决办法: 数据库系统中的表名称最为复杂的情况是catalogname.schemaname.relname，如果超过此，将不在支持。
+
+GAUSS-01783: "unexpected node type in name list: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01784: "bogus PopOverrideSearchPath call"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01785: "collation '%s' for encoding '%s' does not exist"
+
+SQLSTATE: 42704
+
+错误原因: 对应于GetDatabaseEncodingName()所得到的编码方法并不支持NameListToString(name)所对应的字符集。
+
+解决办法: 查询手册确认当前系统所支持的字符集以及相应的编码方式。
+
+GAUSS-01786: "conversion '%s' does not exist"
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01787: "invalid list syntax"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01788: "permission denied to create temporary tables in database '%s'"
+
+SQLSTATE: 42501
+
+错误原因: 该用户没有在当前数据库创建临时表的权限。
+
+解决办法: 请确认用户当前的权限。
+
+GAUSS-01789: "cannot create temporary tables during recovery"
+
+SQLSTATE: 25006
+
+错误原因: 数据库当前属于从某个状态恢复的过程中，此时不支持创建临时表。
+
+解决办法: 若创建临时表不成功，可优先查看当前数据库状态。
+
+GAUSS-01790: "current user does not have privilege to role %s"
+
+SQLSTATE: 42501
+
+错误原因: 当前用户没有管理role的权限。
+
+解决办法: 可向管理员确认用户当前的权限。
+
+<br/>
+
+## GAUSS-01791 - GAUSS-01800
+
+<br/>
+
+GAUSS-01791: "collation '%s' for encoding '%s' already exists"
+
+SQLSTATE: 42710
+
+错误原因: 对应于pg_encoding_to_char(collencoding)这种编码方式的字符集已经存在，因此无法创建。
+
+解决办法: 确认当前编码方式所对应的字符集空间。
+
+GAUSS-01792: "collation '%s' already exists"
+
+SQLSTATE: 42710
+
+错误原因: 想要创建的字符集已经存在，不可重复创建。
+
+解决办法: 确认当前数据库中已经存在的字符集。
+
+GAUSS-01793: "could not find tuple for collation %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01794: "multiple pg_shdepend entries for object %u/%u/%d deptype %c"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01795: "cannot drop %s because it is required by the database system"
+
+SQLSTATE: 2BP01
+
+错误原因: 由于当前数据库系统的某些对象依赖于提示中的对象，因此无法丢弃当前对象。
+
+解决办法: 请确认当前对象与其他对象之间的依赖性，或者想删除该对象时可增加"cascade"选项。
+
+GAUSS-01797: "tablespace %u was concurrently dropped"
+
+SQLSTATE: 42704
+
+错误原因: 在记录表空间的依赖关系时，需要锁住该对象，但是拿到锁后，发现该表空间已不存在，报错。
+
+解决办法: 检查日志当中该表空间何时被丢弃并检查操作的逻辑合理性。
+
+GAUSS-01800: "unrecognized dependency type: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/19-GAUSS-01801-GAUSS-01900.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/19-GAUSS-01801-GAUSS-01900.md
new file mode 100644
index 0000000000000000000000000000000000000000..11f7aa6d28b63238eecd47d1c4cc5edf79a91d3d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/19-GAUSS-01801-GAUSS-01900.md
@@ -0,0 +1,740 @@
+---
+title: GAUSS-01801 - GAUSS-01900
+summary: GAUSS-01801 - GAUSS-01900
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-01801 - GAUSS-01900
+
+<br/>
+
+## GAUSS-01801 - GAUSS-01810
+
+<br/>
+
+GAUSS-01801: "cannot drop objects owned by %s because they are required by the database system"
+
+SQLSTATE: 2BP01
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01802: "unexpected dependency type"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01803: "cannot reassign ownership of objects owned by %s because they are required by the database system"
+
+SQLSTATE: 2BP01
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01804: "unexpected shared pin"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01805: "unexpected classid %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01806: "smgr_redo: unknown op code %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-01811 - GAUSS-01820
+
+<br/>
+
+GAUSS-01811: "could not access file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 需要将该动态库拷贝到其他物理节点，但是查询不到该文件，报错。
+
+解决办法: 检查该动态文件是否真实存在并核对其地址和相关链接信息。
+
+GAUSS-01815: "The name of dynamic library is too long"
+
+SQLSTATE: 42622
+
+错误原因: 使用的动态库名称过长。
+
+解决办法: 当前支持的最大长度是1000，请确保不要超过该长度。
+
+GAUSS-01816: "allParameterTypes is not a 1-D Oid array"
+
+SQLSTATE: XX000
+
+错误原因: 创建procedure时，出现异常: 传入参数有误。
+
+解决办法: 请检查传入参数allParameterTypes的有效性。
+
+GAUSS-01817: "parameterModes is not a 1-D char array"
+
+SQLSTATE: XX000
+
+错误原因: 创建procedure时，出现异常: 传入参数有误。
+
+解决办法: 请检查传入参数parameterModes的有效性。
+
+GAUSS-01818: "cannot determine result data type"
+
+SQLSTATE: 42P13
+
+错误原因: 由于没有输入项导致无法确认返回的数据类型。
+
+解决办法: 请确认输入的参数类型是正确的，这样才可确定返回结果类型。
+
+GAUSS-01819: "unsafe use of pseudo-type 'internal'"
+
+SQLSTATE: 42P13
+
+错误原因: 由于没有相关的internal输入项，使得internal的返回类型存在风险。
+
+解决办法: 需要确认存在相关的internal输入项。
+
+GAUSS-01820: "'%s' is already an attribute of type %s"
+
+SQLSTATE: 42701
+
+错误原因: 在创建函数时的复合类型与已有的属性类型相重名，因此报错。
+
+解决办法: 在创建函数时使用的任何名称都应与已有的属性名称不相同。
+
+<br/>
+
+## GAUSS-01821 - GAUSS-01830
+
+<br/>
+
+GAUSS-01821: "variadic parameter must be last"
+
+SQLSTATE: XX000
+
+错误原因: 创建procedure时，variadic参数出现异常。
+
+解决办法: 仅最后一个参数可以是variadic。
+
+GAUSS-01822: "variadic parameter is not an array"
+
+SQLSTATE: XX000
+
+错误原因: 创建procedure时，variadic参数出现异常（不是数组）。
+
+解决办法: 请检查variadic参数。
+
+GAUSS-01823: "invalid parameter mode '%c'"
+
+SQLSTATE: XX000
+
+错误原因: 创建procedure时，出现无效的PROARGMODE参数。
+
+解决办法: 请检查PROARGMODE参数。
+
+GAUSS-01824: "more than one function '%s' already exist, please drop function first"
+
+SQLSTATE: 42723
+
+错误原因: 在创建函数时发现已有一个名称相同的函数存在。
+
+解决办法: 在创建函数前，请确认当前模式中没有同名函数。
+
+GAUSS-01825: "function '%s' already exists with same argument types"
+
+SQLSTATE: 42723
+
+错误原因: 同名函数已经存在，且要创建的函数和原函数参数相同，因此不能重载。
+
+解决办法: 检查现在创建的函数是否为重新创建。
+
+GAUSS-01826: "cannot change return type of existing function"
+
+SQLSTATE: 42P13
+
+错误原因: 无法改变已经创建的函数的返回类型。
+
+解决办法: 检查新建函数的返回类型或者drop之前创建的函数。
+
+GAUSS-01827: "cannot change name of input parameter '%s'"
+
+SQLSTATE: 42P13
+
+错误原因: 创建函数时不可改变输入参数的类型。
+
+解决办法: 检查函数内部是否有改变函数参数的操作，并将当前的函数丢弃。
+
+GAUSS-01828: "function '%s' is an aggregate function"
+
+SQLSTATE: 42809
+
+错误原因: 内部错误，创建的函数为一个聚集函数，不可以改变其状态。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01829: "function '%s' is not an aggregate function"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01830: "function '%s' is a window function"
+
+SQLSTATE: 42809
+
+错误原因: 创建的函数为一个窗口函数，不可以改变其状态。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-01831 - GAUSS-01840
+
+<br/>
+
+GAUSS-01831: "function '%s' is not a window function"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01832: "null prosrc"
+
+SQLSTATE: XX005
+
+错误原因: 获取自定义函数时出错。
+
+解决办法: 请检查函数名是否正确。
+
+GAUSS-01833: "there is no built-in function named '%s'"
+
+SQLSTATE: 42883
+
+错误原因: 根据给定的函数名称找不到对应的build-in function。
+
+解决办法: 检查pg_proc表中是否存在对应的函数名称。
+
+GAUSS-01834: "null prosrc for C function %u"
+
+SQLSTATE: XX005
+
+错误原因: 获取自定义C函数时出错。
+
+解决办法: 请检查函数名是否正确。
+
+GAUSS-01835: "null probin for C function %u"
+
+SQLSTATE: XX005
+
+错误原因: 获取内置C函数时出错。
+
+解决办法: 请检查函数名是否正确。
+
+GAUSS-01836: "SQL functions cannot return type %s"
+
+SQLSTATE: 42P13
+
+错误原因: SQL函数当前不支持返回format_type_be(proc->prorettype)型的数据类型。
+
+解决办法: 检查sql语句的返回并进行确认。
+
+GAUSS-01837: "SQL functions cannot have arguments of type %s"
+
+SQLSTATE: 42P13
+
+错误原因: 函数当中不允许使用format_type_be(proc->proargtypes.values[i])类型的参数。
+
+解决办法: 检查sql函数中参数的类型。
+
+GAUSS-01838: "In XC, SQL functions cannot contain utility statements"
+
+SQLSTATE: 42601
+
+错误原因: sql函数中不可包含utility statements。
+
+解决办法: 检查sql函数中的内容。
+
+GAUSS-01840: "no conversion name supplied"
+
+SQLSTATE: XX000
+
+错误原因: 在创建conversion使，没有提供conversion name。
+
+解决办法: 请检查conversion name是否为空。
+
+<br/>
+
+## GAUSS-01841 - GAUSS-01850
+
+<br/>
+
+GAUSS-01841: "conversion '%s' already exists"
+
+SQLSTATE: 42710
+
+错误原因: 当前创建的名为conname的conversion已经创建，无法创建同名的conversion。
+
+解决办法: 检查需要创建的conversion是否存在与之相同名称的conversion。
+
+GAUSS-01842: "default conversion for %s to %s already exists"
+
+SQLSTATE: 42710
+
+错误原因: 当前创建的由conforencoding到contoencoding得conversion已经存在，无法创建具有相同功能的conversion。
+
+解决办法: 检查所需创建的conversion功能是否已经存在，无需创建具有相同功能的conversion。
+
+GAUSS-01843: "could not find tuple for conversion %u"
+
+SQLSTATE: XX000
+
+错误原因: 从pg_conversion中删除tuple时出错: 未找到该tuple。
+
+解决办法: 请检查tuple oid是否正确。
+
+GAUSS-01844: "pgxc class relid invalid."
+
+SQLSTATE: XX000
+
+错误原因: 在创建pgxc_class时，出现无效的relid。
+
+解决办法: 请检查传入参数relid的合法性。
+
+GAUSS-01845: "pgxc_group should have at least one default node group"
+
+SQLSTATE: XX000
+
+错误原因: pgxc_group不应该是NULL。
+
+解决办法: 请检查创建pgxc_class时，pgxc_group状态。
+
+GAUSS-01847: "could not obtain lock on partition '%s'"
+
+SQLSTATE: 55P03
+
+错误原因: 无法获取锁用于当前的分区。
+
+解决办法: 检查资源利用以及当前的分区状态。
+
+GAUSS-01848: "partition '%s' does not exist"
+
+SQLSTATE: 42P01
+
+错误原因: 名为partitionName的分区并不存在。
+
+解决办法: 检查对应于表格的分区名称，并进行核对。
+
+GAUSS-01849: "the object with oid %u is not a partitioned object"
+
+SQLSTATE: 42P17
+
+错误原因: 当前的对象并非具有分区特性。
+
+解决办法: 确认对应对象的属性，或检查是否按需求为其创建分区。
+
+GAUSS-01850: "object with oid %u is not a partition object"
+
+SQLSTATE: 42704
+
+错误原因: 当前的对象并非含分区对象。
+
+解决办法: 确认对应对象的属性，或检查是否按需求为其创建分区。
+
+<br/>
+
+## GAUSS-01851 - GAUSS-01860
+
+<br/>
+
+GAUSS-01851: "invalid input parameters when searching for local index under some index"
+
+SQLSTATE: 42704
+
+错误原因: 在检查索引OID有效性时，发现输入的参数是无效的。
+
+解决办法: 检查输入参数的有效性。
+
+GAUSS-01852: "%u is not a partitioned index"
+
+SQLSTATE: 42704
+
+错误原因: 参数OID对应的对象并非是一个分区索引。
+
+解决办法: 检查在执行流程中传入的参数的实际属性，可通过系统表来检查。
+
+GAUSS-01853: "%u not found in pg_class"
+
+SQLSTATE: 42704
+
+错误原因: 无法在pg_class系统表中找到参数OID对应的对象。
+
+解决办法: 确认想要查找的对象的OID并确认是否已经完成analyze操作并正确导入系统表。
+
+GAUSS-01854: "not found local index %u in pg_partition"
+
+SQLSTATE: 42704
+
+错误原因: 在pg_partition系统表中无法查找到对应的local index。
+
+解决办法: 检查local index参数的有效性并与实际创建时所创建的属性进行核对。
+
+GAUSS-01855: "none is the son local index of index %u"
+
+SQLSTATE: 42704
+
+错误原因: 在partitionedIndexid对应的索引中没有找到局部索引。
+
+解决办法: 检查所需查找的局部索引的正确性。
+
+GAUSS-01859: "cache lookup failed for index partition %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01860: "more than one item satisfied parttype is %c, parentOid is %u"
+
+SQLSTATE: 0A000
+
+错误原因: 在一个表中找到了两个同样类型的分区。
+
+解决办法: 在创建分区时应保障不存在相同的分区。
+
+<br/>
+
+## GAUSS-01861 - GAUSS-01870
+
+<br/>
+
+GAUSS-01861: "'%s' does not require a toast table"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01862: "shared tables cannot be toasted after gs_initdb"
+
+SQLSTATE: 55000
+
+错误原因: 当初始化数据库完成后，不允许对共享内存表做toast操作。
+
+解决办法: 请检查当前状态，若已完成初始化，则不允许toast共享内存表。
+
+GAUSS-01863: "cache lookup failed for relation or partition %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01864: "grant options can only be granted to roles"
+
+SQLSTATE: 0LP01
+
+错误原因: 只能对私有用户进行授权，无法对公有用户进行授权。
+
+解决办法: 检查用户的权限，并提交管理员受理。
+
+GAUSS-01865: "unrecognized object kind: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01866: "unrecognized GrantStmt.targtype: %d"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01867: "unrecognized GrantStmt.objtype: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01868: "column privileges are only valid for relations"
+
+SQLSTATE: 0LP01
+
+错误原因: 只有表对象才可拥有列存特性。
+
+解决办法: 检查当前对象的特性，或确认是否是对表对象赋予列存特性。
+
+GAUSS-01869: "AccessPriv node must specify privilege or columns"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01870: "default privileges cannot be set for columns"
+
+SQLSTATE: 0LP01
+
+错误原因: 属性列无默认访问权限。
+
+解决办法: 检查对象本身。
+
+<br/>
+
+## GAUSS-01871 - GAUSS-01880
+
+<br/>
+
+GAUSS-01871: "AccessPriv node must specify privilege"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01872: "could not find tuple for default ACL %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01873: "unexpected default ACL type: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01875: "column number out of range"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01876: "'%s' is an index"
+
+SQLSTATE: 42809
+
+错误原因: 无法对一个索引对象进行赋权限。
+
+解决办法: 检查需要赋予权限的list中的对象情况，确保对象需全为表对象。
+
+GAUSS-01877: "invalid privilege type USAGE for table"
+
+SQLSTATE: 0LP01
+
+错误原因: USAGE这种权限类型只支持sequences，不支持non-sequences场景。
+
+解决办法: 检查表的类型。
+
+GAUSS-01878: "invalid privilege type %s for column"
+
+SQLSTATE: 0LP01
+
+错误原因: 该权限类型不适用于列属性。
+
+解决办法: 检查上下文中关于权限类型的说明以及对象类型的说明。
+
+GAUSS-01879: "language '%s' is not trusted"
+
+SQLSTATE: 42809
+
+错误原因: 系统不信任的语言格式类型。
+
+解决办法: 确认当前系统信任的语言格式。
+
+<br/>
+
+## GAUSS-01881 - GAUSS-01890
+
+<br/>
+
+GAUSS-01881: "cache lookup failed for tablespace %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01882: "cannot set privileges of array types"
+
+SQLSTATE: 0LP01
+
+错误原因: 不能为集合类型设定权限。
+
+解决办法: 在设定权限前确认对象的类型。
+
+GAUSS-01883: "unrecognized privilege type '%s'"
+
+SQLSTATE: 42601
+
+错误原因: 不认识的权限类型。
+
+解决办法: 检查上下文看类型定义是否正确或被修改。
+
+GAUSS-01886: "permission denied for column '%s' of relation '%s'"
+
+SQLSTATE: 42501
+
+错误原因: 无法对表的属性列进行相关权限操作。
+
+解决办法: 检查权限操作定义本身。
+
+GAUSS-01887: "role with OID %u does not exist"
+
+SQLSTATE: 42704
+
+错误原因: 对应用户不存在。
+
+解决办法: 检查用户列表，确认用户是否存在。
+
+GAUSS-01888: "unrecognized objkind: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01889: "attribute %d of relation with OID %u does not exist"
+
+SQLSTATE: 42703
+
+错误原因: 表中不存在该属性的访问权限列表。
+
+解决办法: 检查表定义时候的权限列表情况。
+
+GAUSS-01890: "relation with OID %u does not exist"
+
+SQLSTATE: 42P01
+
+错误原因: 在出口程序中检查用户的访问权限时，发现对应表格不存在。
+
+解决办法: 检查pg_class系统表中OID所对应的表格是否存在。
+
+<br/>
+
+## GAUSS-01891 - GAUSS-01900
+
+<br/>
+
+GAUSS-01891: "database with OID %u does not exist"
+
+SQLSTATE: 3D000
+
+错误原因: 在检查用户的访问权限时，发现不存在对应的数据库。
+
+解决办法: 检查pg_database系统表中关于数据库的状态是否正常。
+
+GAUSS-01892: "function with OID %u does not exist"
+
+SQLSTATE: 42883
+
+错误原因: 在出口程序中检查用户的访问权限时，发现不存在对应的函数。
+
+解决办法: 检查pg_proc系统表中是否存在该函数定义。
+
+GAUSS-01893: "language with OID %u does not exist"
+
+SQLSTATE: 42704
+
+错误原因: 在出口程序中检查用户的访问权限时，发现不存在对应的语言格式。
+
+解决办法: 检查pg_language系统表中是否存在该language定义。
+
+GAUSS-01894: "schema with OID %u does not exist"
+
+SQLSTATE: 3F000
+
+错误原因: 在出口程序中检查用户的访问权限时，发现不存在对应的schema空间。
+
+解决办法: 检查pg_namespace系统表中是否存在该命名空间定义。
+
+GAUSS-01895: "tablespace with OID %u does not exist"
+
+SQLSTATE: 42704
+
+错误原因: 在出口程序中检查用户的访问权限时，发现不存在对应的表空间。
+
+解决办法: 检查pg_tablespace系统表中是否存在该表空间定义。
+
+GAUSS-01896: "foreign-data wrapper with OID %u does not exist"
+
+SQLSTATE: XX000
+
+错误原因: foreign-data wrapper不存在。
+
+解决办法: 检查是否已经创建了对应的foreign-data wrapper。
+
+GAUSS-01897: "foreign server with OID %u does not exist"
+
+SQLSTATE: XX000
+
+错误原因: foreign server不存在。
+
+解决办法: 检查是否已经创建了对应的foreign server。
+
+GAUSS-01898: "type with OID %u does not exist"
+
+SQLSTATE: XX000
+
+错误原因: 在出口程序中检查用户的访问权限时，发现不存在对应的数据类型。
+
+解决办法: 检查pg_type系统表中所有的type的类型定义。
+
+GAUSS-01899: "type with OID %u does not exist"
+
+SQLSTATE: 42704
+
+错误原因: 在出口程序中检查用户的访问权限时，发现不存在对应的数据类型。
+
+解决办法: 检查pg_type系统表中所有的type的类型定义。
+
+GAUSS-01900: "operator with OID %u does not exist"
+
+SQLSTATE: 42883
+
+错误原因: 在检查用户权限时，发现不存在对应的操作类型。
+
+解决办法: 检查pg_operator系统表中operator的定义。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/2-GAUSS-00101-GAUSS-00200.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/2-GAUSS-00101-GAUSS-00200.md
new file mode 100644
index 0000000000000000000000000000000000000000..9782bb64210ab888b159a645cbf690f7be96c88e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/2-GAUSS-00101-GAUSS-00200.md
@@ -0,0 +1,836 @@
+---
+title: GAUSS-00101 - GAUSS-00200
+summary: GAUSS-00101 - GAUSS-00200
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-00101 - GAUSS-00200
+
+<br/>
+
+## GAUSS-00101 - GAUSS-00110
+
+<br/>
+
+### GAUSS-00101: "table '%s' has %d columns available but %d columns specified"
+
+SQLSTATE: 42P10
+
+错误原因: 查询的表对象的列超过了表本身列的数量。
+
+解决办法: 指定的表对象的列不能超过表本身列的个数。
+
+### GAUSS-00102: "too many column aliases specified for function %s"
+
+SQLSTATE: 42P10
+
+错误原因: 函数的别名中列的个数超过一个。
+
+解决办法: 函数的别名中列的个数只能是一个。
+
+### GAUSS-00103: "relation '%s' is not partitioned table"
+
+SQLSTATE: 42P01
+
+错误原因: 表对象不是分区表。
+
+解决办法: 执行之前先通过系统表确定表对象是分区表。
+
+### GAUSS-00104: "partition '%s' of relation '%s' does not exist"
+
+SQLSTATE: 42P01
+
+错误原因: 对象的分区表不存在。
+
+解决办法: 使用分区时通过查询pg_partition表确认该分区是否存在。
+
+### GAUSS-00105: "The partition number is invalid or out-of-range"
+
+SQLSTATE: XX000
+
+错误原因: 插入分区的数值超过了分区的范围。
+
+解决办法: 对分区表插入数值，要保证数据能落到某一个分区里。
+
+### GAUSS-00106: "unsupported partition type"
+
+SQLSTATE: XX000
+
+错误原因: 不支持的分区类型。
+
+解决办法: 修改分区类型。目前行存表、列存表仅支持范围分区。
+
+### GAUSS-00107: "relation '%s.%s' does not exist"
+
+SQLSTATE: 42P01
+
+错误原因: 指定模式下的表对象不存在。
+
+解决办法: 在使用之前，请确保表对象是存在的。
+
+### GAUSS-00108: "relation '%s' does not exist"
+
+SQLSTATE: 42P01
+
+错误原因: 表对象不存在。
+
+解决办法: 在使用之前，请确保表对象是存在的。
+
+### GAUSS-00109: "a column definition list is only allowed for functions returning 'record'"
+
+SQLSTATE: 42601
+
+错误原因: 非返回record类型的函数不接受列定义列表（或表定义）。
+
+解决办法: 对于非返回record类型的函数不要使用表定义指定返回值。
+
+### GAUSS-00110: "a column definition list is required for functions returning 'record'"
+
+SQLSTATE: 42601
+
+错误原因: 返回record类型的函数需要列定义列表（或表定义）。
+
+解决办法: 对于返回record类型的函数要使用表定义指定返回值。
+
+<br/>
+
+## GAUSS-00111 - GAUSS-00120
+
+<br/>
+
+### GAUSS-00111: "column '%s' cannot be declared SETOF"
+
+SQLSTATE: 42P16
+
+错误原因: 函数的返回中声明某一列为SETOF。
+
+解决办法: 函数的返回中不能声明某一列为SETOF。
+
+### GAUSS-00112: "function '%s' in FROM has unsupported return type %s"
+
+SQLSTATE: 42804
+
+错误原因: 函数的返回值是不支持的类型。
+
+解决办法: 请切换为其它常用类型后，重新尝试操作。如问题依然存在，请联系技术支持工程师提供技术支持。
+
+### GAUSS-00113: "VALUES lists '%s' have %d columns available but %d columns specified"
+
+SQLSTATE: 42P10
+
+错误原因: VALUES中参数的个数和实际指定的列个数不一致。
+
+解决办法: 请检查VALUES中参数的个数和实际指定的列个数是否一致。
+
+### GAUSS-00114: "joins can have at most %d columns"
+
+SQLSTATE: 54000
+
+错误原因: join中列的个数超过了限制。
+
+解决办法: join中列的个数不能超过32767个。
+
+### GAUSS-00115: "WITH query '%s' does not have a RETURNING clause"
+
+SQLSTATE: 0A000
+
+错误原因: 非SELECT的with语句没有指定returning子句。
+
+解决办法: 非SELECT的with语句需要指定returning子句。
+
+### GAUSS-00116: "function in FROM has unsupported return type"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00117: "unrecognized RTE kind: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00118: "invalid attnum %d for rangetable entry %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00119: "cache lookup failed for attribute %d of relation %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00120: "subquery %s does not have attribute %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-00121 - GAUSS-00130
+
+<br/>
+
+### GAUSS-00121: "column %d of relation '%s' does not exist"
+
+SQLSTATE: 42703
+
+错误原因: 表中的列不存在。
+
+解决办法: 使用时要确定表中的列是否存在。
+
+### GAUSS-00122: "values list %s does not have attribute %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00123: "invalid varattno %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00124: "invalid attribute number %d"
+
+SQLSTATE: 42704
+
+错误原因: 非法的表属性编号。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00125: "invalid reference to FROM-clause entry for table '%s'"
+
+SQLSTATE: 42P01
+
+错误原因: FROM子句中对表的引用不合法。
+
+解决办法: FROM子句中引用表时请使用正确的语法。
+
+### GAUSS-00126: "missing FROM-clause entry for table '%s'"
+
+SQLSTATE: 42P01
+
+错误原因: with语句中缺少from子句。
+
+解决办法: with语句中必须包含from子句。
+
+### GAUSS-00127: "Password must be quoted"
+
+SQLSTATE: 42601
+
+错误原因: 密码未使用引号。
+
+解决办法: 指定密码时请使用引号引起来。
+
+### GAUSS-00128: "unrecognized role option '%s'"
+
+SQLSTATE: 42601
+
+错误原因: 使用了不识别的用户选项。
+
+解决办法: 使用研发支持文档中给出的用户选项。
+
+### GAUSS-00129: "'SET %s TO rolename' not yet supported"
+
+SQLSTATE: 42601
+
+错误原因: set name to rolename使用方式未支持。
+
+解决办法: 使用支持的方式:set name rolename。
+
+### GAUSS-00130: "'SET %s = rolename' not yet supported"
+
+SQLSTATE: 42601
+
+错误原因: set name = rolename使用方式未支持。
+
+解决办法: 使用支持的方式:set name rolename。
+
+<br/>
+
+## GAUSS-00131 - GAUSS-00140
+
+<br/>
+
+### GAUSS-00131: "current database cannot be changed"
+
+SQLSTATE: 0A000
+
+错误原因: 在当前数据库中对catalog进行设置。
+
+解决办法: 不允许设置系统表。
+
+### GAUSS-00132: "time zone interval must be HOUR or HOUR TO MINUTE"
+
+SQLSTATE: 42601
+
+错误原因: 时间间隔格式设置错误。
+
+解决办法: 间隔格式必须是HOUR or HOUR TO MINUTE。
+
+### GAUSS-00133: "interval precision specified twice"
+
+SQLSTATE: 42601
+
+错误原因: interval的精度被指定多次。
+
+解决办法: 只能指定一次。
+
+### GAUSS-00134: "MATCH PARTIAL not yet implemented"
+
+SQLSTATE: 0A000
+
+错误原因: 引用时使用了部分匹配。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+### GAUSS-00135: "unrecognized distribution option '%s'"
+
+SQLSTATE: 42601
+
+错误原因: 不可识别的分布列选项。
+
+解决办法: 请使用支持的分布选项。具体请参考zh-cn_topic_0237122117.html。
+
+### GAUSS-00136: "Invalid option %s"
+
+SQLSTATE: 42601
+
+错误原因: 选项不合法。
+
+解决办法: 请使用支持的选项。
+
+### GAUSS-00137: "constraint declared INITIALLY DEFERRED must be DEFERRABLE"
+
+SQLSTATE: 42601
+
+错误原因: 声明为INITIALLY DEFERRED的约束必须是DEFERRABLE的。
+
+解决办法: 声明为INITIALLY DEFERRED的约束必须是DEFERRABLE的。
+
+### GAUSS-00138: "conflicting constraint properties"
+
+SQLSTATE: 42601
+
+错误原因: 约束使用冲突。
+
+解决办法: 不能同时使用有冲突的约束。
+
+### GAUSS-00139: "CREATE ASSERTION is not yet implemented"
+
+SQLSTATE: 0A000
+
+错误原因: CREATE ASSERTION未支持。
+
+解决办法: 未支持的不要使用。
+
+### GAUSS-00140: "DROP ASSERTION is not yet implemented"
+
+SQLSTATE: 0A000
+
+错误原因: DROP ASSERTION未支持。
+
+解决办法: 未支持的不要使用。
+
+<br/>
+
+## GAUSS-00141 - GAUSS-00150
+
+<br/>
+
+### GAUSS-00141: "missing argument"
+
+SQLSTATE: 42601
+
+错误原因: 删除操作符时缺少参数。
+
+解决办法: 删除操作符时要使用和定义时一样的参数。
+
+### GAUSS-00142: "WITH CHECK OPTION is not implemented"
+
+SQLSTATE: 0A000
+
+错误原因: 此选项未实现。
+
+解决办法: 不要使用未支持的选项。
+
+### GAUSS-00144: "CREATE TABLE AS EXECUTE not yet supported"
+
+SQLSTATE: 0A000
+
+错误原因: 此语法未支持。
+
+解决办法: 请使用支持的语法，具体请参考zh-cn_topic_0237121923.html。
+
+### GAUSS-00145: "number of columns does not match number of values"
+
+SQLSTATE: 42601
+
+错误原因: 要修改的列的个数和实际给出的值的个数不匹配。
+
+解决办法: 要修改的列的个数和实际给出的值的个数要匹配。
+
+### GAUSS-00146: "Sort method %s is not supported!"
+
+SQLSTATE: XX000
+
+错误原因: 使用了不支持的排序方法。
+
+解决办法: 仅使用支持的选项，具体请参考zh-cn_topic_0237121923.html。
+
+### GAUSS-00148: "VALUES in FROM must have an alias"
+
+SQLSTATE: 42601
+
+错误原因: values语句出现在from子句中未使用别名。
+
+解决办法: values语句出现在from子句中必须使用别名。
+
+### GAUSS-00149: "precision for type float must be at least 1 bit"
+
+SQLSTATE: 22023
+
+错误原因: 指定float的精度时，精度小于1。
+
+解决办法: 指定float的精度时，精度最小是1。
+
+### GAUSS-00150: "precision for type float must be less than 54 bits"
+
+SQLSTATE: 22023
+
+错误原因: 指定float的精度时，精度大于54。
+
+解决办法: 指定float的精度时，精度最大是54。
+
+<br/>
+
+## GAUSS-00151 - GAUSS-00160
+
+<br/>
+
+### GAUSS-00151: "UNIQUE predicate is not yet implemented"
+
+SQLSTATE: 0A000
+
+错误原因: UNIQUE子句没有实现。
+
+解决办法: 请使用实现了的语法。
+
+### GAUSS-00152: "RANGE PRECEDING is only supported with UNBOUNDED"
+
+SQLSTATE: 0A000
+
+错误原因: RANGE PRECEDING使用时没有指定UNBOUNDED。
+
+解决办法: RANGE PRECEDING使用时必须指定UNBOUNDED。
+
+### GAUSS-00153: "RANGE FOLLOWING is only supported with UNBOUNDED"
+
+SQLSTATE: 0A000
+
+错误原因: RANGE FOLLOWING使用时没有指定UNBOUNDED。
+
+解决办法: RANGE FOLLOWING使用时必须指定UNBOUNDED。
+
+### GAUSS-00154: "frame start cannot be UNBOUNDED FOLLOWING"
+
+SQLSTATE: 42P20
+
+错误原因: frame start指定了UNBOUNDED FOLLOWING。
+
+解决办法: frame start不能是UNBOUNDED FOLLOWING。
+
+### GAUSS-00155: "frame starting from following row cannot end with current row"
+
+SQLSTATE: 42P20
+
+错误原因: frame从下一行开始从当前行结束。
+
+解决办法: frame从下一行开始不能从当前行结束。
+
+### GAUSS-00156: "frame end cannot be UNBOUNDED PRECEDING"
+
+SQLSTATE: 42P20
+
+错误原因: frame end指定了UNBOUNDED PRECEDING。
+
+解决办法: frame end不能是UNBOUNDED PRECEDING。
+
+### GAUSS-00157: "frame starting from current row cannot have preceding rows"
+
+SQLSTATE: 42P20
+
+错误原因: frame从当前行开始从之前的行结束。
+
+解决办法: frame从当前行开始不能从当前行之前的行结束。
+
+### GAUSS-00158: "frame starting from following row cannot have preceding rows"
+
+SQLSTATE: 42P20
+
+错误原因: frame从下一行开始从之前的行结束。
+
+解决办法: frame从下一行开始不能从当前行之前的行结束。
+
+### GAUSS-00159: "type modifier cannot have parameter name"
+
+SQLSTATE: 42601
+
+错误原因: 行数的参数模式包含参数。
+
+解决办法: 行数的参数模式不能包含参数。
+
+### GAUSS-00160: "wrong number of parameters on left side of OVERLAPS expression"
+
+SQLSTATE: 42601
+
+错误原因: overlaps函数的左参数个数大于2。
+
+解决办法: overlaps支持一个参数或者两个参数的表达式。
+
+<br/>
+
+## GAUSS-00161 - GAUSS-00170
+
+<br/>
+
+### GAUSS-00161: "wrong number of parameters on right side of OVERLAPS expression"
+
+SQLSTATE: 42601
+
+错误原因: overlaps函数的右参数个数大于2。
+
+解决办法: overlaps支持一个参数或者两个参数的表达式。
+
+### GAUSS-00162: "multiple ORDER BY clauses not allowed"
+
+SQLSTATE: 42601
+
+错误原因: INSERT INTO SELECT语法中使用了多个ORDER BY子句。
+
+解决办法: INSERT INTO SELECT语法中只能使用一个ORDER BY子句。
+
+### GAUSS-00163: "multiple OFFSET clauses not allowed"
+
+SQLSTATE: 42601
+
+错误原因: insert into select语法中使用多个offset子句。
+
+解决办法: insertintoselect语法中只能使用一个offset子句。
+
+### GAUSS-00164: "multiple LIMIT clauses not allowed"
+
+SQLSTATE: 42601
+
+错误原因: insert into select语法中使用多个limit子句
+
+解决办法: insertintoselect语法中只能使用一个limit子句。
+
+### GAUSS-00165: "multiple WITH clauses not allowed"
+
+SQLSTATE: 42601
+
+错误原因: INSERT INTO SELECT语法中使用多个WITH子句。
+
+解决办法: INSERT INTO SELECT语法中只能使用一个WITH子句。
+
+### GAUSS-00166: "OUT and INOUT arguments aren't allowed in TABLE functions"
+
+SQLSTATE: 42601
+
+错误原因: out/inout参数类型用在table function中。
+
+解决办法: out/inout参数类型不能用在table function中。
+
+### GAUSS-00167: "multiple COLLATE clauses not allowed"
+
+SQLSTATE: 42601
+
+错误原因: collate子句指定了多次。
+
+解决办法: collate子句只能指定一次。
+
+### GAUSS-00168: "unexpected node type %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00169: "%s constraints cannot be marked DEFERRABLE"
+
+SQLSTATE: 0A000
+
+错误原因: 使用了不能标记为DEFERRABLE的约束。
+
+解决办法: 修改SQL Statement。
+
+### GAUSS-00170: "%s constraints cannot be marked NOT VALID"
+
+SQLSTATE: 0A000
+
+错误原因: 使用了不能标记为NOT VALID的约束。
+
+解决办法: 修改SQL Statement。
+
+<br/>
+
+## GAUSS-00171 - GAUSS-00180
+
+<br/>
+
+### GAUSS-00171: "%s constraints cannot be marked NO INHERIT"
+
+SQLSTATE: 0A000
+
+错误原因: 使用了不能标记为NO INHERIT的约束。
+
+解决办法: 修改SQL Statement。
+
+### GAUSS-00172: "undefined or invalid action for statement ' alter system '"
+
+SQLSTATE: 42704
+
+错误原因: 使用alter system时的选项长度不为1。
+
+解决办法: 使用alter system时的选项长度为1。
+
+### GAUSS-00173: "unsupported action '%s' for statement ' alter system '"
+
+SQLSTATE: 42704
+
+错误原因: alter system中使用了没有支持的选项。
+
+解决办法: 使用语法支持的选项，具体请参考zh-cn_topic_0237122075.html。
+
+### GAUSS-00174: "undefined action '%s' for statement ' alter system '"
+
+SQLSTATE: 42704
+
+错误原因: alter system使用了没有支持的选项。
+
+解决办法: 使用语法支持的选项，具体请参考zh-cn_topic_0237122075.html。
+
+### GAUSS-00175: "missing or invalid session ID"
+
+SQLSTATE: 42704
+
+错误原因: ALTER SYSTEM中使用的Session ID不正确。
+
+解决办法: 使用正确的Session ID，查询dv_sessions视图查看。
+
+### GAUSS-00176: "parameter '%s' is assigned more than once"
+
+SQLSTATE: 42710
+
+错误原因: 重复使用相同参数名。
+
+解决办法: 一个函数的各个参数名称必须不同。
+
+### GAUSS-00177: "parameter '%s' is undefined"
+
+SQLSTATE: 42P02
+
+错误原因: 未定义参数。
+
+解决办法: 修改SQL Statement。
+
+### GAUSS-00178: "the parameter located '%d' have been assigned"
+
+SQLSTATE: 42710
+
+错误原因: 参数模式已被赋值。
+
+解决办法: 修改SQL Statement。
+
+### GAUSS-00179: "parameter mode %c doesn't exist"
+
+SQLSTATE: XX000
+
+错误原因: 使用了非法的参数模式。
+
+解决办法: 使用文档中描述的支持的参数模式。
+
+### GAUSS-00180: "output argument located '%d' doesnot assigned"
+
+SQLSTATE: XX000
+
+错误原因: 对于出参未赋值其类型。
+
+解决办法: 对参数都要赋值其对应的参数类型。
+
+<br/>
+
+## GAUSS-00181 - GAUSS-00190
+
+<br/>
+
+### GAUSS-00181: "function '%s' doesn't exist "
+
+SQLSTATE: 42883
+
+错误原因: 函数未定义。
+
+解决办法: 修改SQL Statement。
+
+### GAUSS-00182: "function '%s' isn't exclusive "
+
+SQLSTATE: 42723
+
+错误原因: 重复的函数定义。
+
+解决办法: 检查系统中重复的函数。
+
+### GAUSS-00183: "function '%s' with %d parameters doesn't exist "
+
+SQLSTATE: 42883
+
+错误原因: 函数未定义。
+
+解决办法: 修改SQL Statement。
+
+### GAUSS-00184: "invalid name: %s"
+
+SQLSTATE: 42601
+
+错误原因: 变量名不合法。
+
+解决办法: 变量名要符合命名规则，具体请参考zh-cn_topic_0237120321.html。
+
+### GAUSS-00185: "WITH query name '%s' specified more than once"
+
+SQLSTATE: 42712
+
+错误原因: with语句的名称被指定了多次。
+
+解决办法: with语句的名称只能指定一次。
+
+### GAUSS-00187: "unexpected utility statement in WITH"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00188: "WITH clause containing a data-modifying statement must be at the top level"
+
+SQLSTATE: 0A000
+
+错误原因: 非SELECT的with语句，应该放在整个查询的最前面。
+
+解决办法: 非SELECT的with语句，应该放在整个查询的最前面。
+
+### GAUSS-00189: "wrong number of output columns in WITH"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00190: "recursive query '%s' column %d has type %s in non-recursive term but type %s overall"
+
+SQLSTATE: 42804
+
+错误原因: 递归查询中的非递归查询的列类型和实际输出的列类型不一致。
+
+解决办法: 将非递归查询的输出类型转换成递归查询的输出类型。
+
+<br/>
+
+## GAUSS-00191 - GAUSS-00200
+
+<br/>
+
+### GAUSS-00191: "recursive query '%s' column %d has collation '%s' in non-recursive term but collation '%s' overall"
+
+SQLSTATE: 42P21
+
+错误原因: 递归查询中的列的字符集和非递归查询的列的字符集不一致。
+
+解决办法: 将非递归查询的输出字符集转换成递归查询的输出字符集。
+
+### GAUSS-00192: "WITH query '%s' has %d columns available but %d columns specified"
+
+SQLSTATE: 42P10
+
+错误原因: 递归查询中指定的参数个数和实际的查询需要的参数个数不一致。
+
+解决办法: 递归查询中指定的参数个数和实际的查询需要的参数个数要一致。
+
+### GAUSS-00193: "mutual recursion between WITH items is not implemented"
+
+SQLSTATE: 0A000
+
+错误原因: 各个查询之间相互递归没有实现。
+
+解决办法: 请勿使用没有实现的功能。
+
+### GAUSS-00194: "recursive query '%s' must not contain data-modifying statements"
+
+SQLSTATE: 42P19
+
+错误原因: 递归查询包含非查询语句。
+
+解决办法: 递归查询只能包含查询语句。
+
+### GAUSS-00196: "missing recursive reference"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00197: "ORDER BY in a recursive query is not implemented"
+
+SQLSTATE: 0A000
+
+错误原因: 递归查询中使用了order by。
+
+解决办法: 递归查询中使用order by没有实现。
+
+### GAUSS-00198: "OFFSET in a recursive query is not implemented"
+
+SQLSTATE: 0A000
+
+错误原因: 不支持的语法。
+
+解决办法: 修改SQL Statement。
+
+### GAUSS-00199: "LIMIT in a recursive query is not implemented"
+
+SQLSTATE: 0A000
+
+错误原因: 递归查询中使用了limit。
+
+解决办法: 递归查询中使用limit没有实现。
+
+### GAUSS-00200: "FOR UPDATE/SHARE in a recursive query is not implemented"
+
+SQLSTATE: 0A000
+
+错误原因: 递归查询中使用了FOR UPDATE/SHARE。
+
+解决办法: 递归查询中使用FOR UPDATE/SHARE没有实现。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/20-GAUSS-01901-GAUSS-02000.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/20-GAUSS-01901-GAUSS-02000.md
new file mode 100644
index 0000000000000000000000000000000000000000..87ae3761f58061dce6aecf5b33d798cfb9792f3f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/20-GAUSS-01901-GAUSS-02000.md
@@ -0,0 +1,614 @@
+---
+title: GAUSS-01901 - GAUSS-02000
+summary: GAUSS-01901 - GAUSS-02000
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-01901 - GAUSS-02000
+
+<br/>
+
+## GAUSS-01901 - GAUSS-01910
+
+<br/>
+
+GAUSS-01901: "language with OID %u does not exist"
+
+SQLSTATE: 42883
+
+错误原因: 在出口程序中检查用户的访问权限时，发现不存在对应的语言格式。
+
+解决办法: 检查pg_language系统表中是否存在该language定义。
+
+GAUSS-01904: "text search dictionary with OID %u does not exist"
+
+SQLSTATE: 42704
+
+错误原因: 在检查用户权限时，发现不存在对应的文件搜索路径。
+
+解决办法: 检查pg_ts_dict系统表中所有的文件搜索路径。
+
+GAUSS-01905: "text search configuration with OID %u does not exist"
+
+SQLSTATE: 42704
+
+错误原因: 在检查用户权限时，发现不存在对应的文件搜索构图。
+
+解决办法: 检查pg_ts_config系统表中所有的文件搜索构图。
+
+GAUSS-01906: "collation with OID %u does not exist"
+
+SQLSTATE: 42704
+
+错误原因: 在检查用户权限时，发现不存在对应的字符集。
+
+解决办法: 检查pg_collation系统表中所有的字符集。
+
+GAUSS-01907: "conversion with OID %u does not exist"
+
+SQLSTATE: 42704
+
+错误原因: 在检查用户权限时，发现不存在对应的conversion。
+
+解决办法: 检查pg_collation系统表中所有的conversion。
+
+GAUSS-01908: "extension with OID %u does not exist"
+
+SQLSTATE: 42704
+
+错误原因: 在检查用户权限时，发现不存在对应的extension。
+
+解决办法: 检查pg_extension系统表中所有的extension。
+
+GAUSS-01909: "relation '%s' has relchecks = 0"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-01911 - GAUSS-01920
+
+<br/>
+
+GAUSS-01911: "constraint '%s' for domain %s already exists"
+
+SQLSTATE: 42710
+
+错误原因: 在当前表对象中，重命名时想要使用的constraint名称已经存在。
+
+解决办法: 请确认当前域中的已经存在的constraint名称。
+
+GAUSS-01912: "table '%s' has multiple constraints named '%s'"
+
+SQLSTATE: 42710
+
+错误原因: 当前表中至少有两个相同名称的constraint。
+
+解决办法: 请确保对于同一张表，其constraint名称不相重合。
+
+GAUSS-01913: "constraint '%s' for table '%s' does not exist"
+
+SQLSTATE: 42704
+
+错误原因: 当前表中不存在该constraint。
+
+解决办法: 请确认当前表中存在该constraint，或核查该表上的constraint。
+
+GAUSS-01914: "domain '%s' has multiple constraints named '%s'"
+
+SQLSTATE: 42710
+
+错误原因: 当前域中至少有两个相同名称的constraint。
+
+解决办法: 请确保在同一域中，其constraint名称不相重合。
+
+GAUSS-01915: "constraint '%s' for domain '%s' does not exist"
+
+SQLSTATE: 42704
+
+错误原因: 当前域中不存在该constraint。
+
+解决办法: 请确认该域所持有的constraint。
+
+GAUSS-01916: "null conkey for constraint %u"
+
+SQLSTATE: XX005
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01917: "conkey is not a 1-D smallint array"
+
+SQLSTATE: 42804
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01918: "no aggregate name supplied"
+
+SQLSTATE: XX000
+
+错误原因: Aggregate未提供name。
+
+解决办法: 请提供Aggregate name。
+
+GAUSS-01919: "aggregate must have a transition function"
+
+SQLSTATE: XX000
+
+错误原因: Aggregate必须有一个transition function。
+
+解决办法: 请提供transition function。
+
+GAUSS-01920: "cannot determine transition data type"
+
+SQLSTATE: 42P13
+
+错误原因: 在创建聚集函数时对于复合类型无法确定其变换类型。
+
+解决办法: 对于复合类型应制定其转换类型。
+
+<br/>
+
+## GAUSS-01921 - GAUSS-01930
+
+<br/>
+
+GAUSS-01921: "return type of transition function %s is not %s"
+
+SQLSTATE: 42804
+
+错误原因: 依据transfn确定的返回类型与声明的返回类型不相匹配。
+
+解决办法: 对于复合类型必须确保其返回类型与声明的一致性。
+
+GAUSS-01922: "must not omit initial value when transition function is strict and transition type is not compatible with input type"
+
+SQLSTATE: 42P13
+
+错误原因: 当转换函数是严格的，且转换类型与输入类型不一致时，不可忽略初始值的类型。
+
+解决办法: 此时确保第一个值的类型必须与转换类型一致，或至少是二进制兼容的。
+
+GAUSS-01923: "return type of collection function %s is not %s"
+
+SQLSTATE: 42804
+
+错误原因: collection函数的返回类型与预期的aggTreanType不同。
+
+解决办法: 检查是否调用了正确的collection函数。
+
+GAUSS-01924: "cannot determine result data type"
+
+SQLSTATE: 42804
+
+错误原因: 由于没有输入项导致无法确认返回的数据类型。
+
+解决办法: 请确认输入的参数类型是正确的，这样才可确定返回结果类型。
+
+GAUSS-01925: "sort operator can only be specified for single-argument aggregates"
+
+SQLSTATE: 42P13
+
+错误原因: 排序算子只能出现在单参数的聚集函数中。
+
+解决办法: 请确认该聚集函数的参数个数，并确认是否需要调用排序算子。
+
+GAUSS-01926: "function %s returns a set"
+
+SQLSTATE: 42804
+
+错误原因:  聚集函数只能返回单个值不可返回一个集合。
+
+解决办法: 请确认聚集函数的返回情况。
+
+GAUSS-01927: "function %s requires run-time type coercion"
+
+SQLSTATE: 42804
+
+错误原因: 函数要求在执行过程中进行类型强转，但是在nodeAgg.c中并没有处理该场景。
+
+解决办法: 确保在执行过程中不存在类型转换。
+
+GAUSS-01928: "cannot drop %s because %s requires it"
+
+SQLSTATE: 2BP01
+
+错误原因: 由于其他对象依赖他，无法删除这个对象。
+
+解决办法: 解除这种依赖或者删除依赖对象。
+
+GAUSS-01929: "incorrect use of PIN dependency with %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01930: "unrecognized dependency type '%c' for %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-01931 - GAUSS-01940
+
+<br/>
+
+GAUSS-01931: "cannot drop %s because other objects depend on it"
+
+SQLSTATE: 2BP01
+
+错误原因: 由于其他对象依赖他，无法删除这个对象。
+
+解决办法: 解除这种依赖或者删除依赖对象。
+
+GAUSS-01932: "cannot drop desired object(s) because other objects depend on them"
+
+SQLSTATE: 2BP01
+
+错误原因: 由于其他对象依赖这些对象，无法删除这些对象。
+
+解决办法: 使用drop cascade来级联删除依赖对象。
+
+GAUSS-01933: "invalid varlevelsup %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01934: "invalid varno %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01935: "already-planned subqueries not supported"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01936: "invalid resultRelation %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01937: "invalid objectSubId 0 for object class %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01938: "could not find tuple for rule %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01939: "no namespace name supplied"
+
+SQLSTATE: XX000
+
+错误原因: 创建namespace时，未提供namespace的名称。
+
+解决办法: 请提供namespace的名称。
+
+GAUSS-01940: "primary keys cannot be expressions"
+
+SQLSTATE: 0A000
+
+错误原因: 主键不允许是表达式。
+
+解决办法: 请重新选择主键。
+
+<br/>
+
+## GAUSS-01941 - GAUSS-01950
+
+<br/>
+
+GAUSS-01942: "too few entries in colnames list"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01943: "must index at least one column"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01944: "user-defined indexes on system catalog tables are not supported"
+
+SQLSTATE: 0A000
+
+错误原因: 无法在系统表上创建用户定义索引。
+
+解决办法: 不要在系统表上创建索引。
+
+GAUSS-01945: "concurrent index creation on system catalog tables is not supported"
+
+SQLSTATE: 0A000
+
+错误原因: 并发在系统表上创建索引不支持。
+
+解决办法: 不要并发在系统表上创建索引。
+
+GAUSS-01946: "shared indexes cannot be created after gs_initdb"
+
+SQLSTATE: 55000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01947: "constraint must be PRIMARY, UNIQUE or EXCLUDE"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01948: "constraints cannot have index expressions"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01949: "DROP INDEX CONCURRENTLY must be first action in transaction"
+
+SQLSTATE: 0A000
+
+错误原因: 并发删除索引必须是事务块的第一条语句。
+
+解决办法: 调整事务块语句顺序，放置并发删除索引语句为第一句。
+
+GAUSS-01950: "invalid indnatts %d for index %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-01951 - GAUSS-01960
+
+<br/>
+
+GAUSS-01951: "could not find tuple for partition %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01952: "cannot reindex temporary tables of other sessions"
+
+SQLSTATE: 0A000
+
+错误原因: 不能重组其他session临时表上索引。
+
+解决办法: 不要重组其他session上的临时表上索引。
+
+GAUSS-01953: "cannot reindex while reindexing"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01954: "cache lookup failed for partitioned index %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统表缓存查找分区索引信息失败。
+
+解决办法: 检查分区索引是否存在。
+
+GAUSS-01955: "Memory alloc failed for indexInfo"
+
+SQLSTATE: XX000
+
+错误原因: 生成IndexInfo结构失败。
+
+解决办法: 检查有足够的内存。
+
+GAUSS-01956: "cache lookup failed for index %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统表缓存查找索引信息失败。
+
+解决办法: 检查索引名称是否正确。
+
+GAUSS-01957: "mergingBtreeIndexes, zero or less than 2 or greater than 4 source index relations"
+
+SQLSTATE: XX000
+
+错误原因:  实现索引合并时，输入了一个索引或者超过了最大值(300)个索引作为源索引。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01958: "mergingBtreeIndexes, only btree indexes can be merged"
+
+SQLSTATE: XX000
+
+错误原因: 只能合并B树索引。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01959: "target merging index '%s' already contains data"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-01961 - GAUSS-01970
+
+<br/>
+
+GAUSS-01961: "invalid enum label '%s'"
+
+SQLSTATE: 42602
+
+错误原因: 无效的枚举类型。
+
+解决办法: 请检查SQL语句中是否包含所提示的无效枚举类型。
+
+GAUSS-01962: "'%s' is not an existing enum label"
+
+SQLSTATE: 22023
+
+错误原因: 无效的枚举类型。
+
+解决办法: 请检查SQL语句中是否包含所提示的无效枚举类型。
+
+GAUSS-01963: "ALTER TYPE ADD BEFORE/AFTER is incompatible with binary upgrade"
+
+SQLSTATE: 22023
+
+错误原因: 修改枚举类型与二进制升级不兼容。
+
+解决办法: 请检查SQL语句中是否包含对于枚举类型的修改。
+
+GAUSS-01965: "alignment '%c' is invalid for passed-by-value type of size %d"
+
+SQLSTATE: 42P17
+
+错误原因: 对于PASS-BY-VALUE类型无效的长度。
+
+解决办法: 检查创建类型的定义。
+
+GAUSS-01966: "internal size %d is invalid for passed-by-value type"
+
+SQLSTATE: 42P17
+
+错误原因: 对于PASS-BY-VALUE类型无效的长度。
+
+解决办法: 检查创建类型的定义。
+
+GAUSS-01967: "alignment '%c' is invalid for variable-length type"
+
+SQLSTATE: 42P17
+
+错误原因: 变长类型不合法的alignment。
+
+解决办法: 检查创建类型的定义。
+
+GAUSS-01969: "cannot assign new OID to existing shell type"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-01970: "could not form array type name for type '%s'"
+
+SQLSTATE: 42710
+
+错误原因: 数组类型名称超长。
+
+解决办法: 请检查当前创建类型的定义语法中填写的数组类型长度是否超过最大值63。
+
+<br/>
+
+## GAUSS-01971 - GAUSS-01980
+
+<br/>
+
+GAUSS-01973: "could not stat file or directory '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 程序运行过程中需要访问的文件或目录不存在。
+
+解决办法: 手动创建该文件目录，或重新初始化数据目录。
+
+GAUSS-01977: "could not open file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 打开某个文件失败，可能原因是文件不存在，权限不对，或文件损坏。
+
+解决办法: 可根据错误信息分析具体原因，如果文件不存在，需要创建对应文件；权限不对则修改权限；文件损坏则修复文件系统或磁盘。
+
+<br/>
+
+## GAUSS-01981 - GAUSS-01990
+
+<br/>
+
+GAUSS-01983: "cannot continue WAL streaming, recovery has already ended"
+
+SQLSTATE: XX000
+
+错误原因: 主机上不用启动walreceiver，如果启动了报错退出。
+
+解决办法: 正常报错，不用处理。
+
+GAUSS-01984: "invalid standby handshake message type %d"
+
+SQLSTATE: 08P01
+
+错误原因: 主机收到备机无效的握手消息类型。
+
+解决办法: 检查主备节点网络环境，排查是否存在丢包现象。如果没有，请联系技术支持工程师提供技术支持。
+
+GAUSS-01986: "invalid standby message type '%c'"
+
+SQLSTATE: 08P01
+
+错误原因: 主机收到备机无效的消息类型。
+
+解决办法: 检查主备节点网络环境，排查是否存在丢包现象。如果没有，请联系技术支持工程师提供技术支持。
+
+GAUSS-01987: "number of requested standby connections exceeds max_wal_senders (currently %d)"
+
+SQLSTATE: 53300
+
+错误原因: 主机上备机连接数达到上限，可能原因是备机尝试连接主机了很多次，每次连接都失败了，也可能原因是主机上max_wal_senders设置过小，特别是在备机执行build命令的情况下，因为此时主机要启动两个发送线程来完成数据和日志的发送。
+
+解决办法: 查看之前的连接是否已关闭，如果没有则人工关掉。查看max_wal_senders设置是否偏小，如果偏小则手工调大。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/21-GAUSS-02001-GAUSS-02100.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/21-GAUSS-02001-GAUSS-02100.md
new file mode 100644
index 0000000000000000000000000000000000000000..458efcd3559cef51f346c2a67a2eacb320d2e8ad
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/21-GAUSS-02001-GAUSS-02100.md
@@ -0,0 +1,376 @@
+---
+title: GAUSS-02001 - GAUSS-02100
+summary: GAUSS-02001 - GAUSS-02100
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-02001 - GAUSS-02100
+
+<br/>
+
+## GAUSS-02011 - GAUSS-02020
+
+<br/>
+
+GAUSS-02015: "select() failed: %m"
+
+SQLSTATE: XX000
+
+错误原因: select返回失败。
+
+解决办法: 根据具体的错误码确定报错原因。返回错误码为标准错误码，请自行查阅系统帮助中相关错误码的解释。
+
+GAUSS-02016: "replconninfo1 or replconninfo2 not configured."
+
+SQLSTATE: XX000
+
+错误原因: postgresql.conf配置文件中存在replconninfo1或者replconninfo2配置为空。
+
+解决办法: 使用gs_guc工具修改对应报错实例的postgresql.conf中的配置项。
+
+GAUSS-02017: "terminating walreceiver process due to administrator command"
+
+SQLSTATE: 57P01
+
+错误原因: 备机walreceiver线程收到SIGTERM信号，线程退出前打印提示。
+
+解决办法: 检查日志中前面的相关处理，确定操作是否正常。
+
+GAUSS-02018: "walreceiver still running according to shared memory state"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02019: "terminating walreceiver process due to the death of walrcvwriter"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02021 - GAUSS-02030
+
+<br/>
+
+GAUSS-02022: "rm xlog comand is not from primary,peer_role=%d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02023: "return type must be a row type"
+
+SQLSTATE: XX000
+
+错误原因: 构建的元组描述符不是一个行结果信息。
+
+解决办法: 重新执行查询，如果仍然是报错，请联系技术支持工程师提供技术支持。
+
+GAUSS-02026: "requested WAL segment %s has already been removed"
+
+SQLSTATE: XX000
+
+错误原因: 备机/从备请求的日志在主机上已经被删除了。
+
+解决办法: "检查主机实例的pg_xlog目录，确定是否存在名称不连续的日志。需要去重建备机或重启从备，集群环境下，CM会自动重建备机。"
+
+GAUSS-02027: "could not open file '%s' (log file %u, segment %u): %m"
+
+SQLSTATE: XX000
+
+错误原因: 无法打开特定的日志段文件。
+
+解决办法: "检查实例的pg_xlog目录，确认当前打开的文件是否存在，权限是否正确。根据具体的日志错误码进行处理。"
+
+GAUSS-02030: "%u/%u/%u invalid bcm buffer %u"
+
+SQLSTATE: XX000
+
+错误原因: 无法读取到指定的BCM buffer。
+
+解决办法: "通过检查日志以及数据文件，确认是否存在异常删除的情况。重新启动实例。"
+
+<br/>
+
+## GAUSS-02031 - GAUSS-02040
+
+<br/>
+
+GAUSS-02032: "syntax error: unexpected character '%s'"
+
+SQLSTATE: 42601
+
+错误原因: 语法错误，不能识别的符号。
+
+解决办法: 根据报错的信息，请联系技术支持工程师提供技术支持。
+
+GAUSS-02039: "could not rename file '%s' to '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 无法重命名文件。
+
+解决办法: 检查具体的错误码，进行处理。
+
+GAUSS-02040: "could not unlink file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 无法删除文件。
+
+解决办法: 检查具体的错误码，进行处理。
+
+<br/>
+
+## GAUSS-02041 - GAUSS-02050
+
+<br/>
+
+GAUSS-02041: "could not fsync file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 无法sync文件。
+
+解决办法: 检查具体的错误码，进行处理。
+
+<br/>
+
+## GAUSS-02061 - GAUSS-02070
+
+<br/>
+
+GAUSS-02063: "cannot continue Data streaming, recovery has already ended"
+
+SQLSTATE: XX000
+
+错误原因: 当前实例已经退出恢复，不需要在继续启动数据复制。
+
+解决办法: "1. 当前属于正常报错。2. 检查备实例升主时机是否合适。"
+
+GAUSS-02064: "writing incorrect data page checksum at: rnode[%u,%u,%u], blocknum[%u], pageoffset[%u], size[%u], queueoffset[%u/%u]"
+
+SQLSTATE: XX000
+
+错误原因: 备机收到主机发送的数据页CRC校验不通过。
+
+解决办法: 检查网络环境，确定当前是否存在丢包现象。
+
+GAUSS-02065: "invalid tablespace link %s: %m"
+
+SQLSTATE: XX000
+
+错误原因: 备机pg_tblspc目录下存在无效的符号链接。
+
+解决办法: "根据检查错误，确认是否为恶意操作。如果为恶意操作，请恢复环境，或联系技术支持工程师对故障备机进行重建修复。"
+
+GAUSS-02069: "could not find type OID for relation %u"
+
+SQLSTATE: XX000
+
+错误原因: 查找对应的relation失败。
+
+解决办法: 系统表异常，请联系技术支持工程师提供技术支持。
+
+GAUSS-02070: "unrecognized list node type: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02071 - GAUSS-02080
+
+<br/>
+
+GAUSS-02077: "incomplete Bitmapset structure"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02078: "unrecognized token: '%.*s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02079: "unterminated Bitmapset structure"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02080: "unrecognized integer: '%.*s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02081 - GAUSS-02090
+
+<br/>
+
+GAUSS-02081: "unrecognized boolop '%.*s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02082: "NULL relname for RTE %u found"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02083: "NULL relnamespace for RTE %u found"
+
+SQLSTATE: XX000
+
+错误原因: 表所对应的表空间为空。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02086: "parseNodeString(): badly formatted node string '%s'…"
+
+SQLSTATE: XX000
+
+错误原因: 未匹配到正确的节点信息。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02087: "byval datum but length = %lu"
+
+SQLSTATE: XX000
+
+错误原因:  当前string所表示的数据超过了datum所表示的范围。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02088: "expected ']' to end datum, but got '%s'; length = %lu"
+
+SQLSTATE: XX000
+
+错误原因: 非期望的']'元素结束符，而是其他字符。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02090: "unterminated List structure"
+
+SQLSTATE: XX000
+
+错误原因: 遇到了非预期的空链表数据。
+
+解决办法: 内部错误， 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02091 - GAUSS-02100
+
+<br/>
+
+GAUSS-02091: "unrecognized OID: '%.*s'"
+
+SQLSTATE: XX000
+
+错误原因: 内部错误: 无法识别的OID号。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02092: "unexpected right parenthesis"
+
+SQLSTATE: XX000
+
+错误原因: 在读取节点信息时遇到了非预期的右括号
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02093: "cannot list_concat() a list to itself"
+
+SQLSTATE: XX000
+
+错误原因: 不可将一个list连接到它本身。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02094: "tuple offset out of range: %u"
+
+SQLSTATE: XX000
+
+错误原因: 数据偏移量超过了单个页面所能存放的最大元组个数。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02095: "negative bitmapset member not allowed"
+
+SQLSTATE: XX000
+
+错误原因: 位置信息不可以为负数。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02096: "bitmapset is empty"
+
+SQLSTATE: XX000
+
+错误原因: 当前的bitmapset不可为空。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02097: "bitmapset has multiple members"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误: bitmapset有重复的成员。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02098: "cannot get type for untransformed sublink"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误: 对于sublink表达式节点，如果sublink未转换，则无法正确获得表达式类型
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02099: "cannot get collation for untransformed sublink"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误: 对于sublink表达式节点，如果sublink未转换，则无法正确获得表达式的collation
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02100: "cannot set collation for untransformed sublink"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误: 无法未转换的sublink设置collation
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/22-GAUSS-02101-GAUSS-02200.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/22-GAUSS-02101-GAUSS-02200.md
new file mode 100644
index 0000000000000000000000000000000000000000..53097cfc8c874e3e1a2237b2a2d6480d39196f98
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/22-GAUSS-02101-GAUSS-02200.md
@@ -0,0 +1,580 @@
+---
+title: GAUSS-02101 - GAUSS-02200
+summary: GAUSS-02101 - GAUSS-02200
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-02101 - GAUSS-02200
+
+<br/>
+
+## GAUSS-02101 - GAUSS-02110
+
+<br/>
+
+GAUSS-02101: "Invalid RTE found."
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误: 无效的表信息。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02102: "could not determine which collation to use for regular expression"
+
+SQLSTATE: 42P22
+
+错误原因: 对于正则表达式，无法确定合适的排序规则。
+
+解决办法: 请检查正则表达式的定义。
+
+GAUSS-02103: "syntax error at line %d: unexpected character '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 语法错误。
+
+解决办法: 修改SQL Statement。
+
+GAUSS-02104: "%s at line %d"
+
+SQLSTATE: XX000
+
+错误原因: 语法错误。
+
+解决办法: 修改SQL Statement。
+
+GAUSS-02105: "incorrect number of columns in row (expected %d, got %d)"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02106: "relation not open"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02107: "too many columns"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02108: "unrecognized process type: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02109: "close of %s when %s was expected"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02110: "close of %s before any relation was opened"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02111 - GAUSS-02120
+
+<br/>
+
+GAUSS-02111: "no open relation to close"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02112: "unrecognized type '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02114: "type OID %u not found in TypInfo"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02115: "out of memory"
+
+SQLSTATE: XX000
+
+错误原因: 无法申请内存。
+
+解决办法: 请检查系统看是否有足够的内存。
+
+GAUSS-02116: "Incorrect redistribution operation"
+
+SQLSTATE: 42809
+
+错误原因: 无效的分布类型。
+
+解决办法: 只支持HASH，MODULO。
+
+GAUSS-02117: "a list of nodes should have at least one node"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02119: "Error: no such supported locator type: %c\\n"
+
+SQLSTATE: XX000
+
+错误原因: 不支持所指定的分布类型。
+
+解决办法: 只支持REPLICATED，HASH，RROBIN，MODULO分布方式。
+
+GAUSS-02120: "cache lookup failed for pgxc_group %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02121 - GAUSS-02130
+
+<br/>
+
+GAUSS-02124: "Bucket id(%d:%d) out of range."
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02125: "Node(%d) has no buckets on it."
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02128: "PGXC Group %s: group already defined"
+
+SQLSTATE: 42710
+
+错误原因: group已经被定义过。
+
+解决办法: 删除已定义的同名group，或修改新的group名称。
+
+GAUSS-02129: "PGXC node %s: only Datanodes can be group members"
+
+SQLSTATE: 42601
+
+错误原因: group的成员只能为DN类型。
+
+解决办法: 修改创建node group的SQL语句。
+
+<br/>
+
+## GAUSS-02131 - GAUSS-02140
+
+<br/>
+
+GAUSS-02135: "PGXC Group %s: group not defined"
+
+SQLSTATE: 42710
+
+错误原因: group_name对应的节点组不存在。
+
+解决办法: 检查调用的group_name是否正确，或数据库在创建时是否正确创建group。
+
+GAUSS-02136: "PGXC Group %s: group not defined"
+
+SQLSTATE: XX000
+
+错误原因: group_name对应的节点组不存在。
+
+解决办法: 检查调用的group_name是否正确，或数据库在创建时是否正确创建group。
+
+GAUSS-02137: "No options specified"
+
+SQLSTATE: 42601
+
+错误原因: 语法错误，执行create node语句中没有带with option。
+
+解决办法: 修改执行的语句（存疑，用户自行create node是否应作为不推荐行为）。
+
+GAUSS-02138: "port value is out of range"
+
+SQLSTATE: 22003
+
+错误原因: 指定的端口号port超出范围。
+
+解决办法: 修改SQL语句中的port。
+
+<br/>
+
+## GAUSS-02141 - GAUSS-02150
+
+<br/>
+
+GAUSS-02141: "port1 value is out of range"
+
+SQLSTATE: 22003
+
+错误原因: 指定的端口号port1超出范围。
+
+解决办法: 修改SQL语句中的port。
+
+GAUSS-02143: "control_port1 value is out of range"
+
+SQLSTATE: 22003
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02144: "type value is incorrect, specify 'coordinator or 'datanode'"
+
+SQLSTATE: 22023
+
+错误原因: 指定的类型有误，只能为coordinator或datanode类型。
+
+解决办法: 修改SQL语句。
+
+GAUSS-02145: "incorrect option: %s"
+
+SQLSTATE: 42601
+
+错误原因: 指定的选项不正确。
+
+解决办法: 修改SQL语句。
+
+GAUSS-02146: "PGXC node %s: cannot be a primary node, it has to be a Datanode"
+
+SQLSTATE: 42601
+
+错误原因: Create node或Alter node不能将Coordinator指定为主节点。
+
+解决办法: 禁止执行此操作。
+
+GAUSS-02147: "PGXC node %s: cannot be a preferred node, it has to be a Datanode"
+
+SQLSTATE: 42601
+
+错误原因: 不能将Coordinator指定为首选节点，必须是DN。
+
+解决办法: 禁止执行此操作。
+
+GAUSS-02148: "PGXC node %s: Node type not specified"
+
+SQLSTATE: 42601
+
+错误原因: 语法错误，执行create node语句的with option中没有type字段。
+
+解决办法: 修改执行的语句。
+
+GAUSS-02149: "Please choose different node name."
+
+SQLSTATE: 42P17
+
+错误原因: 执行create node指定的node name无法通过hash产生独特的node id。
+
+解决办法: 修改指定的node name。
+
+<br/>
+
+## GAUSS-02151 - GAUSS-02160
+
+<br/>
+
+GAUSS-02152: "Node name '%s' is too long"
+
+SQLSTATE: 42P17
+
+错误原因: 指定的node name过长。
+
+解决办法: 修改指定的node name。
+
+GAUSS-02153: "Failed to create coordinator, the maximum number of coordinators %d specified by 'max_coordinators' has been reached."
+
+SQLSTATE: 42601
+
+错误原因: 语法错误，创建的coordinator数量超过设置的max_coordinators数量。
+
+解决办法: 调大max_coordinators配置参数。
+
+GAUSS-02154: "Failed to create datanode, the maximum number of datanodes %d specified by 'max_datanodes' has been reached."
+
+SQLSTATE: 42601
+
+错误原因: 语法错误，创建的DN数量超过设置的max_datanodes数量。
+
+解决办法: 调大max_datanodes配置参数。
+
+GAUSS-02155: "PGXC node %s: two nodes cannot be primary"
+
+SQLSTATE: 42601
+
+错误原因: 语法错误，已经创建了一个primary node。
+
+解决办法: 根据需要将之前创建的primary node改为非primary节点。
+
+GAUSS-02157: "cache lookup failed for object %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02158: "PGXC node %s: cannot alter Coordinator to Datanode"
+
+SQLSTATE: 42601
+
+错误原因: 语法错误，无法将CN改为DN。
+
+解决办法: 禁止将CN修改为DN。
+
+GAUSS-02159: "PGXC node %s: cannot alter Datanode to Coordinator"
+
+SQLSTATE: 42601
+
+错误原因: 语法错误，无法将DN改为CN。
+
+解决办法: 禁止将DN修改为CN。
+
+<br/>
+
+## GAUSS-02161 - GAUSS-02170
+
+<br/>
+
+GAUSS-02161: "PGXC Node %s: cannot drop local node"
+
+SQLSTATE: 42601
+
+错误原因: 语法错误，无法drop当前节点。
+
+解决办法: 禁止删除本地节点信息。
+
+GAUSS-02167: "Can not connect to pool manager"
+
+SQLSTATE: 58030
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02171 - GAUSS-02180
+
+<br/>
+
+GAUSS-02177: "pool manager only supports UNIX socket"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02178: "unexpected EOF within message length word:%m"
+
+SQLSTATE: 08P01
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02179: "invalid message length"
+
+SQLSTATE: 08P01
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02180: "incomplete message from client:%m"
+
+SQLSTATE: 08P01
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02181 - GAUSS-02190
+
+<br/>
+
+GAUSS-02181: "pooler failed to send res: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02182: "could not receive data from client: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02183: "incomplete message from client"
+
+SQLSTATE: 08P01
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02184: "unexpected message code"
+
+SQLSTATE: 08P01
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02185: "pooler failed to send pids: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02186: "Unexpected response from the Datanodes for 'c' message, current request type %d"
+
+SQLSTATE: XX001
+
+错误原因:  系统内部错误: 对于'c'报文头的消息，遇到了非copyto请求
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02188: "Unexpected response from the Datanodes for 'T' message, current request type %d"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误: 对于'T'报文头的消息，遇到了非行描述信息序列。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02189: "Unexpected response from the Datanodes for 'S' message, current request type %d"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误: 对于'S'报文头的消息，遇到了非set命令请求。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02190: "Unexpected response from the Datanodes for 'G' message, current request type %d"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误: 对于'G'报文头的消息，遇到了非copy in命令请求。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02191 - GAUSS-02200
+
+<br/>
+
+GAUSS-02191: "Unexpected response from the Datanodes for 'H' message, current request type %d"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误: 对于'H'报文头的消息，遇到了非copy out命令请求。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02192: "Unexpected response from the Datanodes for 'd' message, current request type %d"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误: 对于'd'报文头的消息，遇到了非copy out 数据命令请求。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02193: "Unexpected response from the Datanodes for 'D' message, current request type %d"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误: 对于'D'报文头的消息，遇到了非接收数据命令请求。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02195: "Unexpected response from Datanode"
+
+SQLSTATE: XX000。
+
+错误原因: 系统内部错误: 来自于DN的非预期响应。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02196: "Failed to read response from Datanodes Detail: %s\\n"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误: 无法从DN正常获取响应。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02197: "Failed to fetch from Datanode"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02198: "Unexpected response from the Datanodes, result = %d, request type %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误: 从DN获得非预期的响应。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02200: "failed to send PREPARE TRANSACTION command to the node %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误: 无法向指定的节点下发'PREPARE TRANSACTION'命令
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/23-GAUSS-02201-GAUSS-02300.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/23-GAUSS-02201-GAUSS-02300.md
new file mode 100644
index 0000000000000000000000000000000000000000..07b014181650dfe12d98d0f8289e0c600ac90c2b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/23-GAUSS-02201-GAUSS-02300.md
@@ -0,0 +1,556 @@
+---
+title: GAUSS-02201 - GAUSS-02300
+summary: GAUSS-02201 - GAUSS-02300
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-02201 - GAUSS-02300
+
+<br/>
+
+## GAUSS-02201 - GAUSS-02210
+
+<br/>
+
+GAUSS-02202: "Failed to PREPARE the transaction on one or more nodes"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误: 无法在节点上准备所需的事务。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02209: "Error while running COPY"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误: 在收集信息时发现来自于DN的非预期响应。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02210: "could not obtain connection from pool"
+
+SQLSTATE: XX000
+
+错误原因: 无法从连接池中获得连接。
+
+解决办法: 建议设置更大的max_pool_size值。
+
+<br/>
+
+## GAUSS-02211 - GAUSS-02220
+
+<br/>
+
+GAUSS-02211: "cannot run transaction to remote nodes during recovery"
+
+SQLSTATE: XX000
+
+错误原因: 在集群恢复过程中无法执行在远端节点执行事务。
+
+解决办法: 建议等恢复结束后再提交事务操作。
+
+GAUSS-02212: "Failed to get next transaction ID"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误: 无法获得下一个事务ID。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02214: "Failed to send command to Datanodes"
+
+SQLSTATE: XX000
+
+错误原因: 无法下发命令到DN。
+
+解决办法: 请检查当前集群连接状态。
+
+GAUSS-02215: "Unexpected response from Datanode %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误: 来自于DN非预期响应。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02216: "Could not begin transaction on Datanodes %u."
+
+SQLSTATE: XX000
+
+错误原因:  无法在主节点上开始事务。
+
+解决办法: 请检查当前集群连接状态。
+
+GAUSS-02217: "Failed to read response from Datanodes when ending query"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误: 在结束查询时无法从DN读取响应信息。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02218: "Failed to close Datanode cursor"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误: 无法关闭DN上的游标。
+
+解决办法: 请检查当前集群连接状态。
+
+GAUSS-02219: "Number of user-supplied parameters do not match the number of remote parameters"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误: 用户提供的参数与下发的查询所需的参数个数不匹配。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02220: "cannot run EXECUTE DIRECT with utility inside a transaction block"
+
+SQLSTATE: 25001
+
+错误原因: 无法在事务内部执行EXECUTE DIRECT命令。
+
+解决办法: 请在事务外执行该EXECUTE DIRECT命令。
+
+<br/>
+
+## GAUSS-02221 - GAUSS-02230
+
+<br/>
+
+GAUSS-02221: "Could not begin transaction on Datanodes"
+
+SQLSTATE: XX000
+
+错误原因: 无法在主节点上开始事务。
+
+解决办法: 请检查当前集群连接状态。
+
+GAUSS-02223: "Could not begin transaction on coordinators"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02225: "Unexpected response from coordinator %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02228: "prepared transaction with identifier '%s' does not exist"
+
+SQLSTATE: XX000
+
+错误原因: 事务标识参数不存在。
+
+解决办法: 请检查输入参数，重新执行操作。
+
+GAUSS-02229: "NULL junk attribute"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02230: "Failed to read response from Datanode %u when ending query"
+
+SQLSTATE: XX000
+
+错误原因: 无法从DN收到结果。
+
+解决办法: 检查DN的状态，重启集群后，重新查询。
+
+<br/>
+
+## GAUSS-02231 - GAUSS-02240
+
+<br/>
+
+GAUSS-02232: "pgxc_pool_reload cannot run inside a transaction block"
+
+SQLSTATE: 25001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02234: "must define Database name or user name"
+
+SQLSTATE: 42000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02236: "The CREATE BARRIER PREPARE message is expected to arrive at a Coordinator from another Coordinator"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02237: "The CREATE BARRIER END message is expected to arrive at a Coordinator from another Coordinator"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02238: "The CREATE BARRIER EXECUTE message is expected to arrive from a Coordinator"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02239: "Failed to send CREATE BARRIER PREPARE request to the node"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02241 - GAUSS-02250
+
+<br/>
+
+GAUSS-02241: "CREATE BARRIER PREPARE command failed with error %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02242: "Failed to send CREATE BARRIER EXECUTE request to the node"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02244: "CREATE BARRIER command is not expected from another Coordinator"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02250: "cannot open %s query as cursor"
+
+SQLSTATE: 42P11
+
+错误原因: 无法作为游标打开该计划。
+
+解决办法: 请检查有表定义。
+
+<br/>
+
+## GAUSS-02251 - GAUSS-02260
+
+<br/>
+
+GAUSS-02252: "%s is not allowed in a non-volatile function"
+
+SQLSTATE: 0A000
+
+错误原因: 该语句无法在非易变函数内使用。
+
+解决办法: 请检查函数定义。
+
+GAUSS-02253: "invalid portal in SPI cursor operation"
+
+SQLSTATE: XX000
+
+错误原因: 执行中获取变量失败。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02258: "Failed to read response from Datanodes. Detail: %s\\n"
+
+SQLSTATE: XX000
+
+错误原因: 发送端连接断开，具体原因见Detail后的信息。
+
+解决办法: 查看对端DN是否出现故障，或排查网络是否出现异常。
+
+GAUSS-02260: "Unhandled datatype for modulo or hash distribution\\n"
+
+SQLSTATE: XX000
+
+错误原因: 无效的数据分布类型。
+
+解决办法: 请检查表的分布列定义。
+
+<br/>
+
+## GAUSS-02261 - GAUSS-02270
+
+<br/>
+
+GAUSS-02265: "BitmapOr doesn't support zero inputs"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误，BitmapOr算子的输入为空。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02266: "could not identify CTID variable"
+
+SQLSTATE: 42809
+
+错误原因:  获取到的变量不是ctid变量。
+
+解决办法: 查看执行计划，检查表达式返回的类型是否是ctid类型，若否，请联系技术支持工程师提供技术支持。
+
+GAUSS-02268: "invalid operation on partition, allowed are UPDATE/DELETE/SELECT"
+
+SQLSTATE: XX000
+
+错误原因: 对分区表的扫描操作，暂时只支持删查改。
+
+解决办法: 请检查当前针对分区表的操作是否正确。
+
+<br/>
+
+## GAUSS-02271 - GAUSS-02280
+
+<br/>
+
+GAUSS-02271: "could not determine actual type of argument declared %s"
+
+SQLSTATE: 42804
+
+错误原因: 无法确定参数的真实数据类型。
+
+解决办法: 请检查函数定义。
+
+GAUSS-02272: "%s is not allowed in a SQL function"
+
+SQLSTATE: 0A000
+
+错误原因: 事务语句不能出现在SQL函数里。
+
+解决办法: 请检查函数定义。
+
+GAUSS-02273: "could not determine actual result type for function declared to return type %s"
+
+SQLSTATE: 42804
+
+错误原因: 无法确定函数的真实返回类型。
+
+解决办法: 请检查函数定义。
+
+GAUSS-02274: "failed to fetch lazy-eval tuple"
+
+SQLSTATE: 22P08
+
+错误原因: 系统内部错误，从tuplestore中获取元组失败。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02275: "return type mismatch in function declared to return %s"
+
+SQLSTATE: 42P13
+
+错误原因: 返回的数据类型与函数定义的类型不匹配。
+
+解决办法: 请检查函数定义。
+
+GAUSS-02277: "mergejoin clause is not an OpExpr"
+
+SQLSTATE: XX000
+
+错误原因: 计划问题，mergejoin的条件不是一个算术表达式。
+
+解决办法: 生成的计划有问题，请联系技术支持工程师提供技术支持。
+
+GAUSS-02278: "unsupported mergejoin strategy %d"
+
+SQLSTATE: XX000
+
+错误原因: 计划问题，mergejoin使用的排序策略问题。
+
+解决办法: 内部问题，请联系技术支持工程师提供技术支持。
+
+GAUSS-02279: "cannot merge using non-equality operator %u"
+
+SQLSTATE: XX000
+
+错误原因: 计划问题，mergejoin使用的连接策略问题
+
+解决办法: 内部问题，请联系技术支持工程师提供技术支持。
+
+GAUSS-02280: "missing support function %d(%u,%u) in opfamily %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02281 - GAUSS-02290
+
+<br/>
+
+GAUSS-02281: "unrecognized mergejoin state: %d"
+
+SQLSTATE: XX000
+
+错误原因: 执行问题，mergejoin选择的执行策略错误导致。
+
+解决办法: 内部问题，请联系技术支持工程师提供技术支持。
+
+GAUSS-02282: "RIGHT JOIN is only supported with merge-joinable join conditions"
+
+SQLSTATE: 0A000
+
+错误原因:  计划问题，merge right join不支持。
+
+解决办法: 内部问题，请联系技术支持工程师提供技术支持。
+
+GAUSS-02283: "FULL JOIN is only supported with merge-joinable join conditions"
+
+SQLSTATE: 0A000
+
+错误原因: 对于mergejoin来说，full join无法处理非常数型的连接表达式(joinclauses)。
+
+解决办法: 检查sql语句在调用full join时joinclauses是否为常数型。
+
+GAUSS-02284: "non-MVCC snapshots are not supported in index-only scans"
+
+SQLSTATE: 0A000
+
+错误原因: index-only scan不支持非MVCC的snapshot。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02285: "EvalPlanQual recheck is not supported in index-only scans"
+
+SQLSTATE: 0A000
+
+错误原因: index-only scan不支持并发更新时的recheck。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02288: "could not find hash function for hash operator %u"
+
+SQLSTATE: 42883
+
+错误原因: 找不到对应的hash函数。
+
+解决办法: 检查数据类型是否支持hash。
+
+GAUSS-02289: "cursor '%s' is not a SELECT query"
+
+SQLSTATE: 24000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02290: "cursor '%s' is held from a previous transaction"
+
+SQLSTATE: 24000
+
+错误原因: 游标还被前一个事务持有。
+
+解决办法: 请检查游标的状态。
+
+<br/>
+
+## GAUSS-02291 - GAUSS-02300
+
+<br/>
+
+GAUSS-02291: "cursor '%s' has multiple FOR UPDATE/SHARE references to table '%s'"
+
+SQLSTATE: 24000
+
+错误原因: 游标重复作用在当前表上。
+
+解决办法: 检查sql语句是否存在嵌套作用或多次作用情况。
+
+GAUSS-02292: "cursor '%s' does not have a FOR UPDATE/SHARE reference to table '%s'"
+
+SQLSTATE: 24000
+
+错误原因: 对包含"current of"和"update"的sql语句没有找到定义对该表的update/share语法。
+
+解决办法: 对包含"current of"的sql语句，检查是否正确定义了对表的update/share操作或检查优化器部分是否正确处理。
+
+GAUSS-02294: "cursor '%s' is not a simply updatable scan of table '%s'"
+
+SQLSTATE: 24000
+
+错误原因: 对包含"current of"语法且不包含"update"的语法的查询语句没有找到对应的扫描节点。
+
+解决办法: 检查sql语句是否正确编写对表的操作或检查优化器是否正确处理。
+
+GAUSS-02295: "type of parameter %d (%s) does not match that when preparing the plan (%s)"
+
+SQLSTATE: 42804
+
+错误原因: 执行过程中返回的参数类型与执行计划中对表达式的参数类型的描述不一致。
+
+解决办法: "1、请检查sql语句中表达式参数的类型是否一致。2、请检查执行代码，确保参数属性的正确性。"
+
+GAUSS-02296: "no value found for parameter %d"
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02297: "LIMIT subplan failed to run backwards"
+
+SQLSTATE: XX005
+
+错误原因: LIMIT下层算子反向扫描时提前返回NULL。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02298: "impossible LIMIT state: %d"
+
+SQLSTATE: XX006
+
+错误原因: 不可能的LIMIT状态。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02299: "OFFSET must not be negative"
+
+SQLSTATE: 2201X
+
+错误原因: OFFSET count是无效的负值。
+
+解决办法: count值必须大于等于0。
+
+GAUSS-02300: "LIMIT must not be negative"
+
+SQLSTATE: 2201W
+
+错误原因: LIMIT count是无效的负值。
+
+解决办法: count值必须大于等于0。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/24-GAUSS-02301-GAUSS-02400.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/24-GAUSS-02301-GAUSS-02400.md
new file mode 100644
index 0000000000000000000000000000000000000000..df160b363b1a728bf5f6a8a8337e4573dc9c3c02
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/24-GAUSS-02301-GAUSS-02400.md
@@ -0,0 +1,759 @@
+---
+title: GAUSS-02301 - GAUSS-02400
+summary: GAUSS-02301 - GAUSS-02400
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-02301 - GAUSS-02400
+
+<br/>
+
+## GAUSS-02301 - GAUSS-02310
+
+<br/>
+
+GAUSS-02301: "frame starting offset must not be null"
+
+SQLSTATE: 22004
+
+错误原因: window frame子句指定的start offset为NULL。
+
+解决办法: 检查sql语句，保证frame子句的start offset非空。
+
+GAUSS-02302: "frame starting offset must not be negative"
+
+SQLSTATE: 22023
+
+错误原因: window frame子句指定的start offset为负数。
+
+解决办法: 检查sql语句，保证frame子句的start offset非负。
+
+GAUSS-02303: "frame ending offset must not be null"
+
+SQLSTATE: 22004
+
+错误原因: window frame子句指定的ending offset为NULL。
+
+解决办法: 检查sql语句，保证frame子句的ending offset非空。
+
+GAUSS-02304: "frame ending offset must not be negative"
+
+SQLSTATE: 22023
+
+错误原因: window frame子句指定的ending offset为负数。
+
+解决办法: 检查sql语句，保证frame子句的ending offset非负。
+
+GAUSS-02306: "WindowFunc with winref %u assigned to WindowAgg with winref %u"
+
+SQLSTATE: 42804
+
+错误原因: 计划问题，window func的序号和windowagg中的序号对不上。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02307: "aggregate %u needs to have compatible input type and transition type"
+
+SQLSTATE: 42P13
+
+错误原因: 入参类型或中间数据的类型和聚集函数不兼容。
+
+解决办法: 修改入参类型或中间数据的类型为兼容的类型。
+
+GAUSS-02308: "cannot fetch row before WindowObject's mark position"
+
+SQLSTATE: 22P08
+
+错误原因: 内部执行逻辑问题。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02309: "cannot move WindowObject's mark position backward"
+
+SQLSTATE: 0A000
+
+错误原因: 内部执行逻辑问题。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02310: "specified position is out of window: "
+
+SQLSTATE: XX000
+
+错误原因: 内部执行逻辑问题。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02311 - GAUSS-02320
+
+<br/>
+
+GAUSS-02312: "number of array dimensions (%d) exceeds the maximum allowed (%d)"
+
+SQLSTATE: 54000
+
+错误原因: 数组维度超过了最大限制。
+
+解决办法: 修改数组维度，小于报错信息中提示的最大限制。
+
+GAUSS-02313: "array subscript in assignment must not be null"
+
+SQLSTATE: 22004
+
+错误原因: 数组下标在赋值语句中不能为空。
+
+解决办法: 使用正常的数组下标。
+
+GAUSS-02315: "no aggregates in this expression context"
+
+SQLSTATE: 42P25
+
+错误原因: 表达式中不存在聚集函数。
+
+解决办法: 检查SQL中的AggRef表达式。
+
+GAUSS-02316: "no window functions in this expression context"
+
+SQLSTATE: 42P20
+
+错误原因: 表达式中不存在窗口函数。
+
+解决办法: 检查SQL中的WindowFunc表达式。
+
+GAUSS-02317: "attribute number %d exceeds number of columns %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02318: "attribute %d has wrong type"
+
+SQLSTATE: 42P24
+
+错误原因: 类型不匹配。
+
+解决办法: 根据报错Detail信息检查SQL语句。
+
+GAUSS-02319: "table row type and query-specified row type do not match"
+
+SQLSTATE: 42804
+
+错误原因: 表中行类型和查询定义的行类型不匹配。
+
+解决办法: 将表中行类型和查询定义的行类型修改为匹配的。
+
+<br/>
+
+## GAUSS-02321 - GAUSS-02330
+
+<br/>
+
+GAUSS-02322: "attribute '%s' does not exist"
+
+SQLSTATE: XX000
+
+错误原因: 属性列不存在。
+
+解决办法: 根据列名检查SQL语句。
+
+GAUSS-02323: "set-return function not supported in vector eninge"
+
+SQLSTATE: 0A000
+
+错误原因: 特性不支持。
+
+解决办法: 不建议使用。
+
+GAUSS-02324: "functions and operators can take at most one set argument"
+
+SQLSTATE: 0A000
+
+错误原因: 特性不支持，函数入参仅允许出现一个集合值。
+
+解决办法: 函数入参最多使用一个集合值。
+
+GAUSS-02325: "function returning setof record called in context that cannot accept type record"
+
+SQLSTATE: 0A000
+
+错误原因: 特性不支持，返回结果集的函数不能接受record类型。
+
+解决办法: 返回结果集的函数不要使用record类型。
+
+GAUSS-02326: "function return row and query-specified return row do not match"
+
+SQLSTATE: 42804
+
+错误原因: 函数返回的元组属性个数与期望的返回的元组属性个数不匹配。
+
+解决办法: 请检查函数定义中期望的返回列数和类型与实际返回的列数和类型是否匹配。
+
+GAUSS-02327: "table-function protocol for materialize mode was not followed"
+
+SQLSTATE: 39P02
+
+错误原因: 不支持返回结果集的函数用于物化模式。
+
+解决办法: 不使用返回结果集的函数用于物化模式。
+
+GAUSS-02328: "unrecognized table-function returnMode: %d"
+
+SQLSTATE: 39P02
+
+错误原因: 对于当前表格函数的返回模式无法识别。
+
+解决办法: 检查执行器部分代码对于该表的返回模式是否正确处理。
+
+GAUSS-02329: "function returning set of rows cannot return null value"
+
+SQLSTATE: 22004
+
+错误原因: 表函数返回的数据集中包含空值。
+
+解决办法: 在表达式处理阶段应存在对于空值的过滤操作，需要检查是否正确过滤。
+
+GAUSS-02330: "rows returned by function are not all of the same row type"
+
+SQLSTATE: 42804
+
+错误原因: 表函数前后返回的元组描述符不一致。
+
+解决办法: 检查数据的一致性。
+
+<br/>
+
+## GAUSS-02331 - GAUSS-02340
+
+<br/>
+
+GAUSS-02331: "IS DISTINCT FROM does not support set arguments"
+
+SQLSTATE: 42804
+
+错误原因: "is distinct from"型sql语句不支持多个参数。
+
+解决办法: 检查当前sql语句是否正确使用。
+
+GAUSS-02333: "cannot merge incompatible arrays"
+
+SQLSTATE: 42804
+
+错误原因: 两个矩阵的类型不一致。
+
+解决办法: 检查sql语句中进行操作的两个矩阵类型是否一致。
+
+GAUSS-02334: "multidimensional arrays must have array expressions with matching dimensions"
+
+SQLSTATE: 2202E
+
+错误原因: 多维的数组必须具有与维度相匹配的数组表达式。
+
+解决办法: 检查输入字符串。
+
+GAUSS-02335: "unrecognized RowCompareType: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02337: "NULLIF does not support set arguments"
+
+SQLSTATE: 42804
+
+错误原因: NULLIF操作不支持返回参数为集合的场景。
+
+解决办法: 检查sql语句中返回给NULLIF操作的参数是否可能为集合。
+
+GAUSS-02338: "domain %s does not allow null values"
+
+SQLSTATE: 23502
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02339: "value for domain %s violates check constraint '%s'"
+
+SQLSTATE: 23514
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02340: "unsupported reference to system column %d in FieldSelect"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02341 - GAUSS-02350
+
+<br/>
+
+GAUSS-02341: "CURRENT OF cannot be executed"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02342: "unrecognized paramkind: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02343: "Aggref found in non-Agg plan node"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02344: "WindowFunc found in non-WindowAgg plan node"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02345: "SubPlan found with no parent plan"
+
+SQLSTATE: 42P27
+
+错误原因: AlternativeSubPlan表达式无父节点PlanState为空。
+
+解决办法: 检查SQL语句和执行计划是否存在父节点为空的情况。
+
+GAUSS-02346: "AlternativeSubPlan found with no parent plan"
+
+SQLSTATE: 42P27
+
+错误原因: SubPlan表达式无父节点PlanState为空。
+
+解决办法: 检查SQL语句和执行计划是否存在父节点为空的情况。
+
+GAUSS-02347: "target type is not an array"
+
+SQLSTATE: 22023
+
+错误原因: 数组类型转换表达式的目标类型不是数组。
+
+解决办法: 数组类型转换表达式的目标类型和源类型都必须是数组类型。
+
+GAUSS-02348: "ROW() column has type %s instead of type %s"
+
+SQLSTATE: 42804
+
+错误原因: 行表达式类型不匹配。
+
+解决办法: 检查是否有ALTER COLUMN TYPE操作修改了类型。
+
+GAUSS-02349: "could not identify a comparison function for type %s"
+
+SQLSTATE: 42883
+
+错误原因: min/max表达式中类型的比较函数未定义。
+
+解决办法: 检查SQL语句中min/max表达式的用法是否有问题。
+
+GAUSS-02350: "CTE subplans should not be executed via ExecSubPlan"
+
+SQLSTATE: XX000
+
+错误原因: 生成的计划问题。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02351 - GAUSS-02360
+
+<br/>
+
+GAUSS-02351: "cannot set parent params from subquery"
+
+SQLSTATE: XX000
+
+错误原因: 生成的计划问题。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02352: "hashed subplan with direct correlation not supported"
+
+SQLSTATE: XX000
+
+错误原因: 生成的计划有问题，hashed subplan不支持相关子查询。
+
+解决办法: 优化器问题，请联系技术支持工程师提供技术支持。
+
+GAUSS-02353: "more than one row returned by a subquery used as an expression"
+
+SQLSTATE: 21000
+
+错误原因: 子查询返回了多余一行的数据。
+
+解决办法: 检查子查询语句的条件，保证只返回一条数据。
+
+GAUSS-02354: "unrecognized testexpr type: %d"
+
+SQLSTATE: XX000
+
+错误原因: 不识别的表达式类型。
+
+解决办法: 内部问题，请联系技术支持工程师提供技术支持。
+
+GAUSS-02355: "ANY/ALL subselect unsupported as initplan"
+
+SQLSTATE: XX000
+
+错误原因: any/all子查询不支持作为initplan。
+
+解决办法: 检查查询语句，非相关的子查询不要使用any/all子查询语句。
+
+GAUSS-02356: "CTE subplans should not be executed via ExecSetParamPlan"
+
+SQLSTATE: XX000
+
+错误原因: cte子查询不能作为非相关子查询的query。
+
+解决办法: 检查查询语句，非相关的子查询不要使用cte子查询语句。
+
+GAUSS-02357: "direct correlated subquery unsupported as initplan"
+
+SQLSTATE: XX000
+
+错误原因: 相关子查询不能作为initplan。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02358: "setParam list of initplan is empty"
+
+SQLSTATE: XX000
+
+错误原因: 相关子查询的参数列表是空的。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02359: "extParam set of initplan is empty"
+
+SQLSTATE: XX000
+
+错误原因: initplan的参数列表是空的。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02360: "Unrecognized parttype as '%c' for relation '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 检测到了错误的分区类型，不会走到，属于内部保护机制。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02361 - GAUSS-02370
+
+<br/>
+
+GAUSS-02361: "partition table delete conflict"
+
+SQLSTATE: 40000
+
+错误原因: 并发删除partition 表。
+
+解决办法: 不使用并发操作。
+
+GAUSS-02362: "unrecognized heap_delete status: %u"
+
+SQLSTATE: XX000
+
+错误原因: 删除元组的执行返回值不在预期之内，可能该元组不可见。
+
+解决办法: 尝试重新执行删除操作。
+
+GAUSS-02363: "failed to fetch deleted tuple for DELETE RETURNING"
+
+SQLSTATE: XX000
+
+错误原因: delete带有returning时获取删除的元组失败。
+
+解决办法: 内部问题，请联系技术支持工程师提供技术支持。
+
+GAUSS-02364: "cannot UPDATE during bootstrap"
+
+SQLSTATE: XX000
+
+错误原因: 初始化阶段不能有update操作。
+
+解决办法: 内部问题，请联系技术支持工程师提供技术支持。
+
+GAUSS-02365: "unrecognized heap_update status: %u"
+
+SQLSTATE: XX000
+
+错误原因: 更新元组的执行返回值不在预期之内，可能该元组不可见。
+
+解决办法: 尝试重新执行删除操作。
+
+GAUSS-02366: "fail to update partitioned table '%s'"
+
+SQLSTATE: XX000
+
+错误原因:
+
+1. 创建分区表时指定了DISABLE ROW MOVEMENT。
+2. 数据更新超出了分区范围。
+
+解决办法:
+
+1. 修改表为ENABLE ROW MOVEMENT。例如:
+
+   ```sql
+   ALTER TABLE table_name ENABLE ROW MOVEMENT
+   ```
+
+2. 更改分区范围。
+
+GAUSS-02367: "partition table update conflict"
+
+SQLSTATE: 40000
+
+错误原因:  不允许并发更新分区表。
+
+解决办法: 创建表时指定DISABLE ROW MOVEMENT。
+
+GAUSS-02368: "unrecognized heap_update status: %u"
+
+SQLSTATE: XX000
+
+错误原因: 更新元组的执行返回值不在预期之内，可能该元组不可见。
+
+解决办法: 尝试重新执行删除操作。
+
+GAUSS-02369: "unknown operation"
+
+SQLSTATE: XX000
+
+错误原因:  不识别的操作类型。
+
+解决办法: 内部问题，请联系技术支持工程师提供技术支持。
+
+GAUSS-02370: "ModifyTable should not be called during EvalPlanQual"
+
+SQLSTATE: XX000
+
+错误原因: 内部错误。
+
+解决办法: 内部问题，请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02371 - GAUSS-02380
+
+<br/>
+
+GAUSS-02372: "tableoid is null when update partitioned table"
+
+SQLSTATE: XX000
+
+错误原因: 获取到的junk 列是NULL。
+
+解决办法: 内部问题，请联系技术支持工程师提供技术支持。
+
+GAUSS-02374: "could not find junk ctid column"
+
+SQLSTATE: XX000
+
+错误原因: 找不到junk列。
+
+解决办法: 内部问题，请联系技术支持工程师提供技术支持。
+
+GAUSS-02375: "could not find junk tableoid column"
+
+SQLSTATE: XX000
+
+错误原因: 找不到junk列。
+
+解决办法: 内部问题，请联系技术支持工程师提供技术支持。
+
+GAUSS-02376: "could not find junk wholerow column"
+
+SQLSTATE: XX000
+
+错误原因: 找不到junk列。
+
+解决办法: 内部问题，请联系技术支持工程师提供技术支持。
+
+GAUSS-02377: "ExecReScanModifyTable is not implemented"
+
+SQLSTATE: XX000
+
+错误原因: modify table的rescan函数没有实现。
+
+解决办法: 计划问题，请联系技术支持工程师提供技术支持。
+
+GAUSS-02378: "expected valid OLD tuple for triggers"
+
+SQLSTATE: XX000
+
+错误原因: 触发器相关错误，内部错误。
+
+解决办法: 内部问题，请联系技术支持工程师提供技术支持。
+
+GAUSS-02380: "indexqual doesn't have key on left side"
+
+SQLSTATE: XX002
+
+错误原因: 索引表达式的左操作数不是已经建立了索引的变量。
+
+解决办法: 查看系统表检查相关列是否已经建立了索引。
+
+<br/>
+
+## GAUSS-02381 - GAUSS-02390
+
+<br/>
+
+GAUSS-02381: "bogus index qualification"
+
+SQLSTATE: XX002
+
+错误原因: 索引表达式的左操作数的属性号大于已建立索引的总属性个数。
+
+解决办法: 查看系统表和执行计划进行确认。
+
+GAUSS-02384: "NullTest indexqual has wrong key"
+
+SQLSTATE: XX002
+
+错误原因: 索引表达式的左操作数不是已经建立了索引的变量。
+
+解决办法: 查看系统表检查相关列是否已经建立了索引。
+
+GAUSS-02387: "unrecognized operation code: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02388: "whole-row update is not implemented"
+
+SQLSTATE: XX000
+
+错误原因: 整列的更新操作不支持。
+
+解决办法: 检查SQL语句。
+
+GAUSS-02390: "cannot change sequence '%s'"
+
+SQLSTATE: 42809
+
+错误原因: 错误的对象类型，INSERT/UPDATE/DELETE语句不能修改Sequence。
+
+解决办法: 修改SQL语句。
+
+<br/>
+
+## GAUSS-02391 - GAUSS-02400
+
+<br/>
+
+GAUSS-02391: "cannot change TOAST relation '%s'"
+
+SQLSTATE: 42809
+
+错误原因: 错误的对象类型，INSERT/UPDATE/DELETE语句不能修改TOAST表。
+
+解决办法: 修改SQL语句。
+
+GAUSS-02392: "cannot insert into foreign table '%s'"
+
+SQLSTATE: 0A000
+
+错误原因: 特性不支持，外表不支持INSERT操作。
+
+解决办法: 不要对外表进行INSERT操作。
+
+GAUSS-02393: "foreign table '%s' does not allow inserts"
+
+SQLSTATE: 55000
+
+错误原因: 特性不支持，外表不支持INSERT操作。
+
+解决办法: 不要对外表进行INSERT操作。
+
+GAUSS-02394: "cannot update foreign table '%s'"
+
+SQLSTATE: 0A000
+
+错误原因: 特性不支持，外表不支持UPDATE操作。
+
+解决办法: 不要对外表进行UPDATE操作。
+
+GAUSS-02395: "foreign table '%s' does not allow updates"
+
+SQLSTATE: 55000
+
+错误原因: 特性不支持，外表不支持UPDATE操作。
+
+解决办法: 不要对外表进行UPDATE操作。
+
+GAUSS-02396: "cannot delete from foreign table '%s'"
+
+SQLSTATE: 0A000
+
+错误原因: 特性不支持，外表不支持DELETE操作。
+
+解决办法: 不要对外表进行DELETE操作。
+
+GAUSS-02397: "foreign table '%s' does not allow deletes"
+
+SQLSTATE: 55000
+
+错误原因: 特性不支持，外表不支持DELETE操作。
+
+解决办法: 不要对外表进行DELETE操作。
+
+GAUSS-02398: "cannot change relation '%s'"
+
+SQLSTATE: 42809
+
+错误原因: 错误的对象类型，存在INSERT/UPDATE/DELETE语句不能修改的对象类型。
+
+解决办法: 修改SQL语句。
+
+GAUSS-02399: "cannot lock rows in sequence '%s'"
+
+SQLSTATE: 42809
+
+错误原因: 错误的对象类型，不能为Sequence加锁。
+
+解决办法: 修改SQL语句。
+
+GAUSS-02400: "cannot lock rows in TOAST relation '%s'"
+
+SQLSTATE: 42809
+
+错误原因: 错误的对象类型，不能为TOAST表加锁。
+
+解决办法: 修改SQL语句。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/25-GAUSS-02401-GAUSS-02500.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/25-GAUSS-02401-GAUSS-02500.md
new file mode 100644
index 0000000000000000000000000000000000000000..f082dbec5b4af422c4d2109dfa9c6f5eb2a173db
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/25-GAUSS-02401-GAUSS-02500.md
@@ -0,0 +1,708 @@
+---
+title: GAUSS-02401 - GAUSS-02500
+summary: GAUSS-02401 - GAUSS-02500
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-02401 - GAUSS-02500
+
+<br/>
+
+## GAUSS-02401 - GAUSS-02410
+
+<br/>
+
+GAUSS-02401: "cannot lock rows in view '%s'"
+
+SQLSTATE: 42809
+
+错误原因: 错误的对象类型，不能为视图加锁。
+
+解决办法: 修改SQL语句。
+
+GAUSS-02402: "cannot lock rows in foreign table '%s'"
+
+SQLSTATE: 42809
+
+错误原因: 错误的对象类型，不能为外表加锁。
+
+解决办法: 修改SQL语句。
+
+GAUSS-02403: "cannot lock rows in relation '%s'"
+
+SQLSTATE: 42809
+
+错误原因: 错误的对象类型，存在不能加锁的对象。
+
+解决办法: 修改SQL语句。
+
+GAUSS-02404: "new row for relation '%s' violates check constraint '%s'"
+
+SQLSTATE: 23514
+
+错误原因: 新的数据和check约束冲突。
+
+解决办法: 检查数据是否和check约束冲突。
+
+GAUSS-02405: "failed to find ExecRowMark for rangetable index %u"
+
+SQLSTATE: XX000
+
+错误原因: 通过index在Rangetable中未找到ExecRowMark。
+
+解决办法: 检查SQL语句和执行计划。
+
+GAUSS-02407: "t_xmin is uncommitted in tuple to be updated"
+
+SQLSTATE: XX000
+
+错误原因: 欲更新的元组xmin未提交。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02408: "abort transaction due to concurrent update"
+
+SQLSTATE: 40001
+
+错误原因: 事务不允许对同一个元组进行并发更新，所以事务回滚。
+
+解决办法: 重新执行失败回滚的更新事务。
+
+GAUSS-02409: "EvalPlanQual doesn't support locking rowmarks"
+
+SQLSTATE: XX000
+
+错误原因: 读已提交模式下，要检查更新的元组能不能被操作，对应的表不能加锁。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02410: "failed to fetch tuple for EvalPlanQual recheck"
+
+SQLSTATE: 22P08
+
+错误原因: recheck被更新的元组时，获取原则失败。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02411 - GAUSS-02420
+
+<br/>
+
+GAUSS-02411: "failed to fetch tuple for EvalPlanQual recheck"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02412: "found self tuple multiple times in index '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02416: "unrecognized hashjoin state: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02417: "could not rewind hash-join temporary file: %m"
+
+SQLSTATE: XX000
+
+错误原因: 下盘临时文件操作失败。
+
+解决办法: 根据提示的错误信息进行分析。
+
+GAUSS-02419: "could not read from hash-join temporary file: %m"
+
+SQLSTATE: XX000
+
+错误原因: 下盘临时文件操作失败。
+
+解决办法: 根据提示的错误信息进行分析。
+
+GAUSS-02420: "Result nodes do not support mark/restore"
+
+SQLSTATE: XX000
+
+错误原因: result算子不支持mark/restore操作。
+
+解决办法: 计划问题，请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02421 - GAUSS-02430
+
+<br/>
+
+GAUSS-02421: "Hash node does not support ExecProcNode call convention"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02422: "BitmapAnd doesn't support zero inputs"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。BitmapAnd算子的输入为空。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02424: "ExecLockRows:target relation cannot be NULL"
+
+SQLSTATE: 40001
+
+错误原因: BitmapAnd算子的输入为空。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02428: "aggregate function %u called as normal function"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02431 - GAUSS-02440
+
+<br/>
+
+GAUSS-02434: "latch already owned"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02435: "cannot wait on a latch owned by another process"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02436: "failed to create event for socket: error code %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02437: "failed to set up event for socket: error code %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02439: "WaitForMultipleObjects() failed: error code %lu"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02440: "failed to enumerate network events: error code %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02441 - GAUSS-02450
+
+<br/>
+
+GAUSS-02441: "unexpected return code from WaitForMultipleObjects(): %lu"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02442: "pipe() failed: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02443: "fcntl() failed on read-end of self-pipe: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02444: "fcntl() failed on write-end of self-pipe: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02445: "poll() failed: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统调用poll失败。
+
+解决办法: 数据库内部错误，请根据系统错误提示信息，请联系技术支持工程师提供技术支持。
+
+GAUSS-02446: "read() on self-pipe failed: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02447: "unexpected EOF on self-pipe"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02448: "sem_open('%s') failed: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02449: "sem_init failed: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02450: "too many semaphores created"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02451 - GAUSS-02460
+
+<br/>
+
+GAUSS-02451: "sem_trywait failed: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02452: "sem_wait failed: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02453: "sem_post failed: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02454: "could not get size for full pathname of datadir %s: error code %lu"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02455: "could not allocate memory for shared memory name"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02456: "could not generate full pathname for datadir %s: error code %lu"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02457: "could not create shared memory segment: error code %lu"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02458: "pre-existing shared memory block is still in use"
+
+SQLSTATE: XX000
+
+错误原因:  WIN32平台不涉及。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02461 - GAUSS-02470
+
+<br/>
+
+GAUSS-02461: "reattaching to shared memory returned unexpected address (got %p, expected %p)"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02462: "reattaching to shared memory returned non-PostgreSQL memory"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02463: "could not create signal listener pipe for PID %d: error code %lu"
+
+SQLSTATE: XX000
+
+错误原因:  WIN32平台不涉及。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02464: "could not create semaphores: %m"
+
+SQLSTATE: XX000
+
+错误原因: 创建的信号量超过系统限制。
+
+解决办法: 调整系统内核参数（/proc/sys/kernel/sem），增加允许创建的信号量，或调小数据库max_connections 。
+
+GAUSS-02465: "semop(id=%d) failed: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02466: "could not create shared memory segment: %m"
+
+SQLSTATE: XX000
+
+错误原因: 共享内存大小超过了系统限制。
+
+解决办法: 调整系统共享内存内核参数（SHMMAX，SHMMIN），或调小数据库shared_buffers。
+
+GAUSS-02467: "shmat(id=%d) failed: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02468: "could not stat data directory '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: data目录不存在或权限错误。
+
+解决办法: 检查data数据目录是否存在或权限是否正确。
+
+GAUSS-02470: "could not create semaphore: error code %d"
+
+SQLSTATE: XX000
+
+错误原因: WIN32平台不涉及。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02471 - GAUSS-02480
+
+<br/>
+
+GAUSS-02471: "could not lock semaphore: error code %d"
+
+SQLSTATE: XX000
+
+错误原因: WIN32平台不涉及。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02472: "could not unlock semaphore: error code %d"
+
+SQLSTATE: XX000
+
+错误原因: WIN32平台不涉及。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02473: "could not try-lock semaphore: error code %d"
+
+SQLSTATE: XX000
+
+错误原因: WIN32平台不涉及。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02474: "dynamic load not supported"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02475: "out of on_shmem_exit slots"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02476: "too late to call tuplestore_set_eflags"
+
+SQLSTATE: 23514
+
+错误原因: 系统内部错误: 调用tuplestore_set_eflags过晚。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02477: "too late to require new tuplestore eflags"
+
+SQLSTATE: 23514
+
+错误原因: 系统内部错误: 设置新的tuplestore 标记过晚。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02478: "tuplestore seek failed"
+
+SQLSTATE: 22P07
+
+错误原因: 系统内部错误: 寻找不到对应位置的tuple数据信息。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02479: "invalid tuplestore state"
+
+SQLSTATE: XX006
+
+错误原因: 系统内部错误: 当前tuplestor状态错误。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02481 - GAUSS-02490
+
+<br/>
+
+GAUSS-02481: "tuplestore seek to EOF failed"
+
+SQLSTATE: 22P07
+
+错误原因: 系统内部错误: 从文件中读取数据时未搜到结束符。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02482: "bogus tuple length in backward scan"
+
+SQLSTATE: 22P07
+
+错误原因: NA
+
+解决办法: NA
+
+GAUSS-02483: "tuplestore seek to start failed"
+
+SQLSTATE: 22P07
+
+错误原因: 系统内部错误: 读取数据时未搜到开始标记。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02484: "unexpected end of tape"
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误: 从逻辑Tape上读取数据过程中遇到非预期的结束。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02485: "unexpected end of data"
+
+SQLSTATE: 22P07
+
+错误原因: 系统内部错误: 从逻辑Tape上读取数据过程中遇到非预期的数据终止。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02487: "too late to call batchstore_set_eflags"
+
+SQLSTATE: XX006
+
+错误原因: 系统内部错误: 调用batchstore_set_eflags过晚。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02488: "too late to require new batchstore eflags"
+
+SQLSTATE: XX006
+
+错误原因: 系统内部错误: 设置新的batchstore 标记过晚。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02489: "batchstore seek failed"
+
+SQLSTATE: 22P07
+
+错误原因: 系统内部错误: 寻找不到对应位置的数据信息。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02490: "invalid batchstore state"
+
+SQLSTATE: XX006
+
+错误原因: 系统内部错误: 无效的batchstore状态。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02491 - GAUSS-02500
+
+<br/>
+
+GAUSS-02491: "batchstore seek to EOF failed"
+
+SQLSTATE: 22P07
+
+错误原因: 系统内部错误: 从文件中读取数据时未读到结束符
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02492: "batchstore seek to start failed"
+
+SQLSTATE: 22P07
+
+错误原因: 系统内部错误: 读取数据时未搜到开始标记。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02493: "could not write block %ld of temporary file: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部写临时文件出错。
+
+解决办法: 请检查磁盘是否有剩余空间，请联系技术支持工程师提供技术支持。
+
+GAUSS-02494: "could not read block %ld of temporary file: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误:无法从临时文件中读取block数据块。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02495: "invalid logtape state: should be dirty"
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误: 无效的logtape状态。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02496: "function %u returned NULL"
+
+SQLSTATE: XX005
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02497: "insufficient memory allowed for sort"
+
+SQLSTATE: 53000
+
+错误原因: 执行sort过程中内存不足。
+
+解决办法: work_mem过小，请调大work_mem参数取值。
+
+GAUSS-02498: "invalid tuplesort state"
+
+SQLSTATE: XX006
+
+错误原因: 系统内部错误: 无效的行存排序状态。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02499: "retrieved too many tuples in a bounded sort"
+
+SQLSTATE: 23001
+
+错误原因: 系统内部错误: 在排序过程中，遇到了非预期的结束符，导致在bounded排序时，所需的数据不足。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02500: "tuplesort_restorepos failed"
+
+SQLSTATE: 22P07
+
+错误原因: 系统内部错误: 在做mergejoin过程中无法重新计量当前位置。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/26-GAUSS-02501-GAUSS-02600.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/26-GAUSS-02501-GAUSS-02600.md
new file mode 100644
index 0000000000000000000000000000000000000000..125d93f705e4ea4f859cc9cd3698cdfa6ec94295
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/26-GAUSS-02501-GAUSS-02600.md
@@ -0,0 +1,772 @@
+---
+title: GAUSS-02501 - GAUSS-02600
+summary: GAUSS-02501 - GAUSS-02600
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-02501 - GAUSS-02600
+
+<br/>
+
+## GAUSS-02501 - GAUSS-02510
+
+<br/>
+
+GAUSS-02501: "could not create unique index '%s'"
+
+SQLSTATE: 23505
+
+错误原因: 系统内部错误: 无法创建唯一索引。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02502: "reversedirection_index_hash is not implemented"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误: 当前函数未实现。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02503: "copytup_datum() should not be called"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误: 未实现函数，无法调用。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02504: "Failed to fetch from data node cursor"
+
+SQLSTATE: 22P08
+
+错误原因: 系统内部错误: 无法从DN游标中获取数据。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02505: "Node id %d is incorrect"
+
+SQLSTATE: XX006
+
+错误原因: 系统内部错误: 获取到的节点ID号错误。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02506: "%s"
+
+SQLSTATE: XX000
+
+错误原因: 语法错误。
+
+解决办法: 检查sql语句的语法是否正确。
+
+GAUSS-02507: "Unexpected response from the data nodes"
+
+SQLSTATE: XX006
+
+错误原因: 系统内部错误: 非期望的来自于DN的响应信息。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02508: "invalid BatchSort state"
+
+SQLSTATE: XX006
+
+错误原因: 系统内部错误: 无效的列存排序状态。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02509: "invalid batchsort state"
+
+SQLSTATE: XX006
+
+错误原因: 系统内部错误: 无效的列存排序状态。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02510: "batchsort_restorepos failed"
+
+SQLSTATE: D0011
+
+错误原因: 系统内部错误: 列存排序过程中存取位置信息出错。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02511 - GAUSS-02520
+
+<br/>
+
+GAUSS-02511: "failed to initialize hash table '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02512: "cannot insert into frozen hashtable '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02513: "out of shared memory"
+
+SQLSTATE: 53200
+
+错误原因: 共享内存不足。
+
+解决办法: 1.可能需要将max_locks_per_transaction参数调大；2.可能当前节点上内存资源不足，需要通过释放相应的内存来解决；
+
+GAUSS-02514: "unrecognized hash action code: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02515: "cannot freeze shared hashtable '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02516: "cannot freeze hashtable '%s' because it has active scans"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02517: "hash table '%s' corrupted"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02518: "too many active hash_seq_search scans, cannot start one on '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02519: "no hash_seq_search scan for hash table '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02520: "could not change directory to '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02521 - GAUSS-02530
+
+<br/>
+
+GAUSS-02521: "could not get current working directory: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02522: "cannot set parameter '%s' within security-restricted operation"
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02524: "role '%s' is not permitted to login"
+
+SQLSTATE: 28000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02525: "too many connections for role '%s'"
+
+SQLSTATE: 53300
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02526: "permission denied to set session authorization"
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02527: "invalid role OID: %u"
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02528: "could not create lock file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02529: "could not open lock file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02530: "could not read lock file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02531 - GAUSS-02540
+
+<br/>
+
+GAUSS-02532: "lock file '%s' already exists"
+
+SQLSTATE: F0001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02533: "pre-existing shared memory block (key %lu, ID %lu) is still in use"
+
+SQLSTATE: F0001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02534: "could not remove old lock file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02535: "could not write lock file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02536: "'%s' is not a valid data directory"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02537: "database files are incompatible with server"
+
+SQLSTATE: 22023
+
+错误原因: 数据库文件和软件版本不匹配。
+
+解决办法: 请使用正确的软件版本重建数据库。
+
+GAUSS-02538: "could not set timer for authorization timeout"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02539: "could not disable timer for authorization timeout"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02540: "database '%s' has disappeared from pg_database"
+
+SQLSTATE: 3D000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02541 - GAUSS-02550
+
+<br/>
+
+GAUSS-02541: "database '%s' is not currently accepting connections"
+
+SQLSTATE: 55000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02542: "permission denied for database '%s'"
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02543: "too many connections for database '%s'"
+
+SQLSTATE: 53300
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02544: "database locale is incompatible with operating system"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02545: "bad backend ID: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02546: "new replication connections are not allowed during database shutdown"
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02547: "must be system admin to connect during database shutdown"
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02548: "must be system admin to connect in binary upgrade mode"
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02551 - GAUSS-02560
+
+<br/>
+
+GAUSS-02551: "database %u does not exist"
+
+SQLSTATE: 3D000
+
+错误原因: 数据库不存在。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02552: "Forbid remote connection with trust method!"
+
+SQLSTATE: 42601
+
+错误原因: 在可信方法下禁止远程连接。
+
+解决办法: 请检查连接的安全设置。
+
+GAUSS-02554: "not able to set up signal action handler"
+
+SQLSTATE: 53000
+
+错误原因: 无法为线程创建信号处理函数。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02555: "failed to create timer for thread"
+
+SQLSTATE: XX000
+
+错误原因:  无法为线程创建定时器。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02556: "could not find function '%s' in file '%s'"
+
+SQLSTATE: 42883
+
+错误原因: 无法找到函数定义。
+
+解决办法: 请检查语句中的函数定义是否合法。
+
+GAUSS-02557: "could not load library '%s': %s"
+
+SQLSTATE: XX000
+
+错误原因: 无法载入库。
+
+解决办法: 请根据错误原因提示检查库。
+
+GAUSS-02558: "incompatible library '%s': missing magic block"
+
+SQLSTATE: XX000
+
+错误原因: 不兼容的库，缺失魔数。
+
+解决办法: 请检查该库是否损坏。
+
+GAUSS-02559: "incompatible library '%s': version mismatch"
+
+SQLSTATE: XX000
+
+错误原因: 不兼容版本的库。
+
+解决办法: 请检查是否兼容该版本的库。
+
+GAUSS-02560: "incompatible library '%s': magic block mismatch"
+
+SQLSTATE: XX000
+
+错误原因: 不兼容的库，魔数不匹配。
+
+解决办法: 请检查是否兼容此库。
+
+<br/>
+
+## GAUSS-02561 - GAUSS-02570
+
+<br/>
+
+GAUSS-02563: "invalid macro name in dynamic library path: %s"
+
+SQLSTATE: 42602
+
+错误原因: 动态库地址中包含不合法的路径宏。
+
+解决办法: 请检查动态库地址中的路径宏是否合法。
+
+GAUSS-02564: "zero-length component in parameter 'dynamic_library_path'"
+
+SQLSTATE: 42602
+
+错误原因: 动态库地址长度为0，不合法。
+
+解决办法: 请检查动态库的地址。
+
+GAUSS-02565: "component in parameter 'dynamic_library_path' is not an absolute path"
+
+SQLSTATE: 42602
+
+错误原因: 动态库地址不是绝对路径。
+
+解决办法: 请检查动态库的地址。
+
+GAUSS-02566: "init_MultiFuncCall cannot be called more than once"
+
+SQLSTATE: 2F000
+
+错误原因: 函数init_MultiFuncCall不能被调用多次。
+
+解决办法: 请检查调用逻辑。
+
+GAUSS-02567: "could not determine actual result type for function '%s' declared to return type %s"
+
+SQLSTATE: 42804
+
+错误原因: 无法确定函数的返回类型。
+
+解决办法: 请检查函数的返回类型。
+
+GAUSS-02568: "proallargtypes is not a 1-D Oid array"
+
+SQLSTATE: XX000
+
+错误原因: 函数参数不合法。
+
+解决办法: 请检查传入参数。
+
+GAUSS-02569: "proargnames must have the same number of elements as the function has arguments"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误: 函数参数数目与proarnames不匹配。
+
+解决办法: 请检查输入参数。
+
+<br/>
+
+## GAUSS-02571 - GAUSS-02580
+
+<br/>
+
+GAUSS-02572: "number of aliases does not match number of columns"
+
+SQLSTATE: 42804
+
+错误原因: 别名的数量和列的数量无法匹配。
+
+解决办法: 通过\\d+ tablename确认列的数目后，请检查当前查询语句的别名的数量和列的数量是否匹配。
+
+GAUSS-02573: "no column alias was provided"
+
+SQLSTATE: 42804
+
+错误原因: 列的别名没有提供。
+
+解决办法: 请提供列的别名。
+
+GAUSS-02574: "could not determine row description for function returning record"
+
+SQLSTATE: 42804
+
+错误原因: 无法确定RECORD返回类型函数的RECORD类型定义。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02575: "internal function '%s' is not in internal lookup table"
+
+SQLSTATE: 42883
+
+错误原因: 无法在函数查找表内找到函数定义。
+
+解决办法: 检查SQL语句中的函数是否有效。
+
+GAUSS-02576: "unrecognized function API version: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02577: "language %u has old-style handler"
+
+SQLSTATE: 42P13
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02578: "null result from info function '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02579: "unrecognized API version %d reported by info function '%s'"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02580: "fmgr_oldstyle received NULL pointer"
+
+SQLSTATE: XX005
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02581 - GAUSS-02590
+
+<br/>
+
+GAUSS-02581: "function %u has too many arguments (%d, maximum is %d)"
+
+SQLSTATE: 54023
+
+错误原因: 函数输入参数过多。
+
+解决办法: 通过\\df检查函数定义的参数数目和当前查询语句输入的参数数目是否一致。函数最大参数数目为16。
+
+GAUSS-02583: "input function %u returned non-NULL"
+
+SQLSTATE: XX005
+
+错误原因: 列数据进行类型处理后返回了空字符串，与not null要求冲突。
+
+解决办法: 修正列数据不为空，满足not null约束。
+
+GAUSS-02584: "input function %u returned NULL"
+
+SQLSTATE: XX005
+
+错误原因: 列数据进行类型处理后返回了非空字符串，与null要求冲突。
+
+解决办法: 修正列数据为空，满足null约束。
+
+GAUSS-02585: "receive function %u returned non-NULL"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02586: "receive function %u returned NULL"
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02587: "could not reopen file '%s' as stderr: %m"
+
+SQLSTATE: XX000
+
+错误原因: 无法作为STDERR重定向文件打开。
+
+解决办法: 检查文件是否存在。
+
+GAUSS-02588: "could not reopen file '%s' as stdout: %m"
+
+SQLSTATE: XX000
+
+错误原因: 无法作为STDOUT重定向文件打开。
+
+解决办法: 检查文件是否存在。
+
+GAUSS-02590: "buffer %d is not owned by resource owner %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02591 - GAUSS-02600
+
+<br/>
+
+GAUSS-02591: "catcache reference %p is not owned by resource owner %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02592: "catcache list reference %p is not owned by resource owner %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02594: "partcache reference %s is not owned by resource owner %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02595: "fakerel reference %s is not owned by resource owner %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02596: "plancache reference %p is not owned by resource owner %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02597: "tupdesc reference %p is not owned by resource owner %s"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02598: "snapshot reference %p is not owned by resource owner %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02599: "temporery file %d is not owned by resource owner %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02600: "pthread mutex %p is not owned by resource owner %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/27-GAUSS-02601-GAUSS-02700.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/27-GAUSS-02601-GAUSS-02700.md
new file mode 100644
index 0000000000000000000000000000000000000000..6774c53a3ddda82d69927cd606306e7253bf2942
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/27-GAUSS-02601-GAUSS-02700.md
@@ -0,0 +1,764 @@
+---
+title: GAUSS-02601 - GAUSS-02700
+summary: GAUSS-02601 - GAUSS-02700
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-02601 - GAUSS-02700
+
+<br/>
+
+## GAUSS-02601 - GAUSS-02610
+
+<br/>
+
+GAUSS-02601: "invalid source encoding ID: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02602: "expected source encoding '%s', but got '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02603: "invalid destination encoding ID: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02604: "expected destination encoding '%s', but got '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02605: "encoding conversion length must not be negative"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02606: "invalid byte sequence for encoding '%s': %s"
+
+SQLSTATE: 22021
+
+错误原因: 无法识别的字符序列。
+
+解决办法: 请参考**PostgreSQL中文文档**中"字符集支持"小节检查数据中是否有无法识别的字符编码。
+
+GAUSS-02607: "character with byte sequence %s in encoding '%s' has no equivalent in encoding '%s'"
+
+SQLSTATE: 22P05
+
+错误原因: 无法找到对应的字符编码。
+
+解决办法: 请通过"select * from pg_conversion;"查看conname列，确认两种字符编码能否互相转换。
+
+GAUSS-02608: "encoding name too long"
+
+SQLSTATE: 42622
+
+错误原因: 超长的字符编码名称。
+
+解决办法: 请检查字符编码名称。
+
+GAUSS-02609: "invalid encoding number: %d"
+
+SQLSTATE: 22023
+
+错误原因: 无法识别的本地字符集。
+
+解决办法: 请检查是否支持本地字符集。
+
+GAUSS-02610: "conversion between %s and %s is not supported"
+
+SQLSTATE: 0A000
+
+错误原因: 这两种字符编码集无法互相转换。
+
+解决办法: 检查源目标字符集和目标字符集是否兼容。
+
+<br/>
+
+## GAUSS-02611 - GAUSS-02620
+
+<br/>
+
+GAUSS-02611: "out of memory"
+
+SQLSTATE: 54000
+
+错误原因: 无法申请内存。
+
+解决办法: 请检查系统看是否有足够的内存。
+
+GAUSS-02612: "invalid source encoding name '%s'"
+
+SQLSTATE: 22023
+
+错误原因: 无法识别的源字符编码集。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02613: "invalid destination encoding name '%s'"
+
+SQLSTATE: 22023
+
+错误原因: 无法识别的目标字符编码集。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02614: "invalid encoding name '%s'"
+
+SQLSTATE: 22023
+
+错误原因: 无法识别的字符编码集。
+
+解决办法: 修改SQL语句。
+
+GAUSS-02615: "invalid byte value for encoding '%s': 0x%02x"
+
+SQLSTATE: 22021
+
+错误原因: 无法识别的字符编码。
+
+解决办法: 检查数据中是否含有不可识别的字符。
+
+GAUSS-02616: "invalid database encoding: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02617: "unexpected encoding ID %d for WIN character sets"
+
+SQLSTATE: XX000
+
+错误原因: 对于Windows字符集无法识别的字符编码。
+
+解决办法: 检查数据中是否含有不可识别的字符。
+
+GAUSS-02618: "unexpected encoding ID %d for ISO 8859 character sets"
+
+SQLSTATE: XX000
+
+错误原因: 对于ISO 8859字符集无法识别的字符编码。
+
+解决办法: 检查数据中是否含有不可识别的字符。
+
+GAUSS-02619: "duplicate portal name"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02620: "cursor '%s' already exists"
+
+SQLSTATE: 42P03
+
+错误原因: 创建portal时已经有重名的portal。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02621 - GAUSS-02630
+
+<br/>
+
+GAUSS-02621: "portal already pinned"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02622: "portal not pinned"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02624: "cannot commit while a portal is pinned"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02625: "cannot PREPARE a transaction that has created a cursor WITH HOLD"
+
+SQLSTATE: 0A000
+
+错误原因: 无法对于创建WITH HOLD关键字游标的事务进行prepare操作。
+
+解决办法: 检查SQL脚本文件中是否含有WITH HOLD关键字的游标。
+
+GAUSS-02627: "invalid memory alloc request size %lu"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02628: "unrecognized context type"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02629: "could not find block containing chunk %p"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02630: "inserted partition key does not map to any table partition"
+
+SQLSTATE: 22003
+
+错误原因: 插入的元组的分区键值和任意一个已存在的分区键都匹配不上。
+
+解决办法: 建议检查插入的数据是否存在超出分区表分区范围。
+
+<br/>
+
+## GAUSS-02631 - GAUSS-02640
+
+<br/>
+
+GAUSS-02631: "NULL can not be compared with NULL"
+
+SQLSTATE: 42804
+
+错误原因: 两个分区键做比较时，不允许空指针和空指针做比较。
+
+解决办法: 建议检查插入的数据的分区列以及分区边界值是否存在空值。
+
+GAUSS-02632: "null maxvalue for tuple %u"
+
+SQLSTATE: XX000
+
+错误原因: 范围分区的maxvalue为空。
+
+解决办法: 检查分区表定义。
+
+GAUSS-02633: "partition key column's number is not a 1-D smallint array"
+
+SQLSTATE: XX000
+
+错误原因: 分区键对应的列编号不是一维的整型数组。
+
+解决办法: 检查分区表定义和查询语句。
+
+GAUSS-02635: "Fail to build partitionmap for partitioned table '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 创建分区映射失败，该分区表不存在。
+
+解决办法: 建议检查被操作的表是否分区表。
+
+GAUSS-02636: "Fail to build partitionmap for partitioned table '%u'"
+
+SQLSTATE: XX000
+
+错误原因: 创建分区映射失败，该分区表的分区方式和指定的分区方式不符。
+
+解决办法: 建议检查被操作的表是否分区表。
+
+GAUSS-02637: "rebuild partition map ERROR"
+
+SQLSTATE: XX000
+
+错误原因: 创建分区失败，新表分区方式和旧表分区方式不一致。
+
+解决办法: 建议检查重建的分区表和旧的分区表是否分区方式一致。
+
+GAUSS-02638: "invalid partition sequence: %d of relation '%s'"
+
+SQLSTATE: XX000
+
+错误原因: split分区时，无法获取到原分区的范围。
+
+解决办法: 检查分区表定义。
+
+GAUSS-02640: "CAN NOT get number of partition against NON-PARTITIONED relation"
+
+SQLSTATE: XX000
+
+错误原因: 禁止对非分区表执行获取分区数的操作。
+
+解决办法: 错误，事务回滚。
+
+<br/>
+
+## GAUSS-02641 - GAUSS-02650
+
+<br/>
+
+GAUSS-02642: "fail to get partition oid, because range partition index is overflow."
+
+SQLSTATE: XX000
+
+错误原因: 获取分区OID失败，分区下标越界。
+
+解决办法: 检查分区表定义和查询语句。
+
+GAUSS-02643: "unsupported partition strategy"
+
+SQLSTATE: XX000
+
+错误原因: 不支持指定的分区方式。
+
+解决办法: 建议检查当指定的分区方式是否在支持列表里。关于支持的分区方式请参考zh-cn_topic_0237122117.html。
+
+GAUSS-02644: "fail to get partition strategy"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02645: "failed when making EQUAL expression state for constCompare"
+
+SQLSTATE: XX000
+
+错误原因: 常量比较的表达式初始化失败。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02646: "failed when making GREATE-THAN expression state for constCompare"
+
+SQLSTATE: XX000
+
+错误原因: 常量比较的表达式初始化失败。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02647: "null value can not be compared with null value."
+
+SQLSTATE: XX000
+
+错误原因: 两个分区键做比较时，不允许空值和空值做比较。
+
+解决办法: 建议检查插入的数据的分区列以及分区边界值是否存在空值。
+
+GAUSS-02648: "unsupported partitioned strategy"
+
+SQLSTATE: 42P17
+
+错误原因: 无效的分区方式。
+
+解决办法: 建议检查当指定的分区方式是否在支持列表里。关于支持的分区方式请参考zh-cn_topic_0237122117.html。
+
+<br/>
+
+## GAUSS-02651 - GAUSS-02660
+
+<br/>
+
+GAUSS-02651: "cache lookup failed for table partition %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02652: "unrecognized rbtree node state: %d"
+
+SQLSTATE: RB001
+
+错误原因: 不能识别的红黑树节点。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02653: "unrecognized rbtree iteration order: %d"
+
+SQLSTATE: RB002
+
+错误原因: 不能识别的红黑树迭代顺序。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02654: "failed to initialize %s to %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02655: "failed to initialize %s to %g"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02656: "failed to initialize %s to '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02657: "could not find enum option %d for %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02658: "unrecognized configuration parameter '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 无法识别的配置参数。
+
+解决办法: 建议检查配置文件是否存在非法配置参数。
+
+GAUSS-02659: "unrecognized configuration parameter '%s'"
+
+SQLSTATE: 42704
+
+错误原因: 无法识别的配置参数。
+
+解决办法: 建议检查配置文件是否存在非法配置参数。
+
+<br/>
+
+## GAUSS-02661 - GAUSS-02670
+
+<br/>
+
+GAUSS-02661: "SET %s takes only one argument"
+
+SQLSTATE: 22023
+
+错误原因: 当前GUC变量不支持指定多个参数值。
+
+解决办法: 请检查SET命令确保每次只指定一个参数值。
+
+GAUSS-02663: "unexpected SET TRANSACTION element: %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02664: "unexpected SET SESSION element: %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02665: "SET LOCAL TRANSACTION SNAPSHOT is not implemented"
+
+SQLSTATE: 0A000
+
+错误原因: 不支持"SET LOCAL TRANSACTION SNAPSHOT"命令。
+
+解决办法: 建议不使用该特性。
+
+GAUSS-02666: "unexpected SET MULTI element: %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02667: "unexpected SET name: %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02668: "role name in the set command is empty."
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02669: "verify set session_authorization and passwd failed."
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02670: "verify set role and passwd failed."
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02671 - GAUSS-02680
+
+<br/>
+
+GAUSS-02671: "SET requires parameter name"
+
+SQLSTATE: 22004
+
+错误原因: SET命令没有指定变量名。
+
+解决办法: 请指定变量名后，重新执行SET。
+
+GAUSS-02672: "Postgres-XC: ERROR SET query"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02673: "cannot create PGC_POSTMASTER variables after startup"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02674: "attempt to redefine parameter '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 存在重复定义的用户变量。
+
+解决办法: 建议检查是否重复定义了相同的用户表变量。
+
+GAUSS-02675: "invalid format of exec config params file"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02676: "could not read from file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 读取配置文件失败。
+
+解决办法: 建议检查错误提示中指定的配置文件是否存在，或者是否有访问权限。
+
+GAUSS-02677: "failed to locate variable '%s' in exec config params file"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02678: "permission denied to set parameter '%s'"
+
+SQLSTATE: 42501
+
+错误原因: 当前用户没有权限修改该GUC变量。
+
+解决办法: 建议切换初始用户修改该GUC参数。
+
+GAUSS-02679: "Invalid username/password,set role denied."
+
+SQLSTATE: 42704
+
+错误原因: SET ROLE语句中设置的用户名/密码。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02680: "Invalid username/password,set session_authorization denied."
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02681 - GAUSS-02690
+
+<br/>
+
+GAUSS-02684: "md5-password encryption failed"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02686: "Invalid username/password,set role denied."
+
+SQLSTATE: XX000
+
+错误原因: SET ROLE语句中设置的用户名/密码。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02687: "Invalid username/password,set session_authorization denied."
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02688: "configuration file '%s' contains errors"
+
+SQLSTATE: F0000
+
+错误原因: 配置文件存在错误的配置项。
+
+解决办法: 建议检查配置文件是否存在非法配置参数。
+
+GAUSS-02689: "could not initialize cache %u (%d)"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02690: "invalid cache ID: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02691 - GAUSS-02700
+
+<br/>
+
+GAUSS-02691: "type %u not supported as catcache key"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02692: "wrong number of hash keys: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02693: "only sys attr supported in caches is OID"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02694: "operator %u is not a member of opfamily %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02695: "operator %u does not exist"
+
+SQLSTATE: XX000
+
+错误原因: 出现非法表达式。
+
+解决办法: 检查查询中的表达式是否合法，若不合法，需要修改查询。
+
+GAUSS-02696: "binary I/O not supported during bootstrap"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02697: "invalid syntax for type: '%s'"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02698: "cache lookup failed for node %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02699: "cache lookup failed for group %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02700: "cache lookup failed on distribution relation %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/28-GAUSS-02701-GAUSS-02800.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/28-GAUSS-02701-GAUSS-02800.md
new file mode 100644
index 0000000000000000000000000000000000000000..c08aabfb7c6f524485c56ea36577bd1f7333f732
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/28-GAUSS-02701-GAUSS-02800.md
@@ -0,0 +1,732 @@
+---
+title: GAUSS-02701 - GAUSS-02800
+summary: GAUSS-02701 - GAUSS-02800
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-02701 - GAUSS-02800
+
+<br/>
+
+## GAUSS-02701 - GAUSS-02710
+
+<br/>
+
+GAUSS-02701: "unrecognized distribution option found in source like table"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02703: "cache lookup failed for workload group %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02705: "type %s is only a shell"
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02706: "no input function available for type %s"
+
+SQLSTATE: 42883
+
+错误原因: 内部错误，此数据类型没有可用的输入函数。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02707: "no output function available for type %s"
+
+SQLSTATE: 42883
+
+错误原因: 内部错误，此数据类型没有可用的输出函数。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02708: "no binary input function available for type %s"
+
+SQLSTATE: 42883
+
+错误原因: 内部错误，此数据类型没有可用的输入函数。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02709: "no binary output function available for type %s"
+
+SQLSTATE: 42883
+
+错误原因: 内部错误，此数据类型没有可用的输出函数。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02710: "stavalues is null"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02711 - GAUSS-02720
+
+<br/>
+
+GAUSS-02711: "stanumbers is null"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02712: "stanumbers is not a 1-D float4 array"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02713: "text search parser %u has no prsstart method"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02714: "text search parser %u has no prstoken method"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02715: "text search parser %u has no prsend method"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02716: "text search dictionary %u has no template"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02717: "text search template %u has no lexize method"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02718: "text search configuration %u has no parser"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02719: "maptokentype value %d is out of range"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02721 - GAUSS-02730
+
+<br/>
+
+GAUSS-02721: "too many pg_ts_config_map entries for one token type"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02722: "text search configuration isn't set"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02723: "cannot read pg_class without having selected a database"
+
+SQLSTATE: 3D000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02724: "could not find relation mapping for partition '%s', OID %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02725: "partition %u deleted while still in use"
+
+SQLSTATE: XX000
+
+错误原因: 用户SQL语句调度问题。
+
+解决办法: 正在使用的partition不能删除。请修改调度语句。
+
+GAUSS-02726: "partition %u is still open"
+
+SQLSTATE: XX000
+
+错误原因: 用户SQL语句调度问题。
+
+解决办法: 正在使用的partition不能删除。请修改调度语句。
+
+GAUSS-02727: "could not find pg_partition tuple for index %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02728: "cannot change relation mapping within subtransaction"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02729: "attempt to apply a mapping to unmapped relation %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02730: "ran out of space in relation map"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02731 - GAUSS-02740
+
+<br/>
+
+GAUSS-02731: "could not find temporary mapping for relation %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02732: "cannot PREPARE a transaction that modified relation mapping"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02733: "could not open relation mapping file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 内部错误，找不到relation映射文件。
+
+解决办法: 建议检查数据目录是否被外部修改，或者联系请联系技术支持工程师提供技术支持。
+
+GAUSS-02735: "relation mapping file '%s' contains invalid data"
+
+SQLSTATE: XX000
+
+错误原因: 内部错误，relation映射文件数据不一致。
+
+解决办法: 建议检查数据目录是否被外部修改，或者联系请联系技术支持工程师提供技术支持。
+
+GAUSS-02736: "relation mapping file '%s' contains incorrect checksum"
+
+SQLSTATE: XX000
+
+错误原因: 内部错误，relation映射文件数据不一致。
+
+解决办法: 建议检查数据目录是否被外部修改，或者联系请联系技术支持工程师提供技术支持。
+
+GAUSS-02738: "could not write to relation mapping file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 内部错误，访问relation映射文件失败。
+
+解决办法: 建议检查数据目录是否被外部修改，或者联系请联系技术支持工程师提供技术支持。
+
+GAUSS-02740: "could not close relation mapping file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 内部错误，访问relation映射文件失败。
+
+解决办法: 建议检查数据目录是否被外部修改，或者联系请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02741 - GAUSS-02750
+
+<br/>
+
+GAUSS-02742: "relmap_redo: unknown op code %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02743: "cannot read pg_class without having selected a database"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02744: "invalid attribute number %d for %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+AUSS-02746: "relnatts disagrees with indnatts for index %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02747: "bogus pg_index tuple"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02748: "could not find tuple for opclass %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02749: "invalid amproc number %d for opclass %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02750: "could not find pg_class tuple for index %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02751 - GAUSS-02760
+
+<br/>
+
+GAUSS-02751: "relation %u deleted while still in use"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02752: "relation %u is still open"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02753: "shared_relation flag for '%s' does not match IsSharedRelation(%u)"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02754: "invalid relowner in pg_class entry for '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02755: "could not open critical system index %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02756: "unexpected constraint record found for rel %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02758: "null cluster key for rel %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02759: "unexpected exclusion constraint record found for rel %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02760: "null conexclop for rel %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02761 - GAUSS-02770
+
+<br/>
+
+AUSS-02762: "exclusion constraint record missing for rel %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02763: "could not find strategy for operator %u in family %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02764: "could not write init file"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02765: "could not remove cache file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 内部错误，访问缓存文件失败。
+
+解决办法: 建议检查数据目录是否被外部修改，或者请联系技术支持工程师提供技术支持。
+
+GAUSS-02766: "Fail to get index key for index with oid %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02767: "unrecognized SI message ID: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02768: "out of syscache_callback_list slots"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02769: "out of relcache_callback_list slots"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02770: "out of partcache_callback_list slots"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02771 - GAUSS-02780
+
+<br/>
+
+GAUSS-02771: "cannot save one-shot cached plan"
+
+SQLSTATE: XX000
+
+错误原因: change result type
+
+解决办法: 重新执行原始语句。
+
+GAUSS-02772: "cached plan must not change result type"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02773: "cannot apply ResourceOwner to non-saved cached plan"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02775: "cannot move a saved cached plan to another context"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02776: "cannot move a one-shot cached plan to another context"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02777: "cannot copy a one-shot cached plan"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02778: "invalid typrelid for composite type %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02779: "cache lookup failed for range type %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02780: "type %s is not composite"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02781 - GAUSS-02790
+
+<br/>
+
+GAUSS-02781: "record type has not been registered"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02782: "enum value %u not found in cache for enum %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02787: "could not import the requested snapshot"
+
+SQLSTATE: 55000
+
+错误原因: 因为事务已执行完毕，无法为指定事务导入快照信息。
+
+解决办法: 尝试重新执行事务可解决。
+
+GAUSS-02789: "could not create file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 内部错误，文件访问失败。
+
+解决办法: 建议检查数据目录是否被外部修改，或者请联系技术支持工程师提供技术支持。
+
+GAUSS-02790: "could not write to file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 内部错误，文件访问失败。
+
+解决办法: 建议检查数据目录是否被外部修改，或者请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02791 - GAUSS-02800
+
+<br/>
+
+GAUSS-02791: "invalid snapshot data in file '%s'"
+
+SQLSTATE: 22P02
+
+错误原因: 内部错误，文件访问失败。
+
+解决办法: 建议检查数据目录是否被外部修改，或者请联系技术支持工程师提供技术支持。
+
+GAUSS-02792: "SET TRANSACTION SNAPSHOT must be called before any query"
+
+SQLSTATE: 25001
+
+错误原因: SET TRANSACTION SNAPSHOT必须作为第一条语句执行。
+
+解决办法: 建议检查SQL脚本文件，是否"SET TRANSACTION SNAPSHOT"之前是否包含其他语句。
+
+GAUSS-02793: "a snapshot-importing transaction must have isolation level SERIALIZABLE or REPEATABLE READ"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02795: "could not stat file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 无法获得文件的状态信息。
+
+解决办法: 检查文件状态是否异常，例如文件不存在，文件读取权限不够等。
+
+GAUSS-02796: "could not read file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 必须使用数据库系统管理员读取文件。
+
+解决办法: 更换系统管理员用户进行操作。
+
+GAUSS-02797: "a serializable transaction cannot import a snapshot from a non-serializable transaction"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02798: "a non-read-only serializable transaction cannot import a snapshot from a read-only transaction"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02799: "cannot import a snapshot from a different database"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02800: "unrecognized weight: %d"
+
+SQLSTATE: XX000
+
+错误原因: 函数tsvector_setweight的第二个参数类型不能识别。
+
+解决办法: 第二个参数只支持A a B b C c D d八个字符。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/29-GAUSS-02801-GAUSS-02900.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/29-GAUSS-02801-GAUSS-02900.md
new file mode 100644
index 0000000000000000000000000000000000000000..92486572b345521fefd65ba86af6e0fb248966d5
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/29-GAUSS-02801-GAUSS-02900.md
@@ -0,0 +1,780 @@
+---
+title: GAUSS-02801 - GAUSS-02900
+summary: GAUSS-02801 - GAUSS-02900
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-02801 - GAUSS-02900
+
+<br/>
+
+## GAUSS-02801 - GAUSS-02810
+
+<br/>
+
+GAUSS-02801: "string is too long for tsvector (%d bytes, max %d bytes)"
+
+SQLSTATE: 54000
+
+错误原因: 字符串超出tsvector最大长度。
+
+解决办法: 建议检查输入数据是否过长。
+
+GAUSS-02802: "unrecognized operator: %d"
+
+SQLSTATE: XX000
+
+错误原因: 不能识别的tsvector操作符。
+
+解决办法: 请检查输入，只支持 ! | &三种操作符。
+
+GAUSS-02803: "SPI_prepare('%s') failed"
+
+SQLSTATE: XX000
+
+错误原因: SPI_prepare调用返回NULL值。
+
+解决办法: 内部错误，产生的原因很多，请联系技术支持工程师提供技术支持。
+
+GAUSS-02804: "SPI_cursor_open('%s') failed"
+
+SQLSTATE: XX000
+
+错误原因: SPI_cursor_open调用返回NULL值。
+
+解决办法: 内部错误，产生的原因很多，请联系技术支持工程师提供技术支持。
+
+GAUSS-02806: "tsvector_update_trigger: not fired by trigger manager"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02807: "tsvector_update_trigger: must be fired for row"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02808: "tsvector_update_trigger: must be fired BEFORE event"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02809: "tsvector_update_trigger: must be fired for INSERT or UPDATE"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02810: "tsvector_update_trigger: arguments must be tsvector_field, ts_config, text_field1, …）"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02811 - GAUSS-02820
+
+<br/>
+
+GAUSS-02811: "tsvector column '%s' does not exist"
+
+SQLSTATE: 42703
+
+错误原因: 选取列不存在。
+
+解决办法: 建议检选取列是否存在。
+
+GAUSS-02812: "column '%s' is not of tsvector type"
+
+SQLSTATE: 42804
+
+错误原因: 选取列非tsvector类型。
+
+解决办法: 建议检查选取列是否为tsvector类型。
+
+GAUSS-02813: "configuration column '%s' does not exist"
+
+SQLSTATE: 42703
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02814: "column '%s' is not of regconfig type"
+
+SQLSTATE: 42804
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02815: "configuration column '%s' must not be null"
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02816: "text search configuration name '%s' must be schema-qualified"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02817: "column '%s' is not of a character type"
+
+SQLSTATE: 42804
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02818: "tsvector_update_trigger: %d returned by SPI_modifytuple"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02819: "gtsvector_in not implemented"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02820: "invalid input syntax for type numeric: '%s'"
+
+SQLSTATE: 22P02
+
+错误原因: 非法的Numeric输入。
+
+解决办法: 请检查数据中是否包含非法的Numeric输入。关于Numeric的合法格式请参考zh-cn_topic_0237121926.html。
+
+<br/>
+
+## GAUSS-02821 - GAUSS-02830
+
+<br/>
+
+GAUSS-02821: "invalid length in external 'numeric' value"
+
+SQLSTATE: 22P03
+
+错误原因: 非法的Numeric输入。
+
+解决办法: 请检查数据中是否包含非法的Numeric输入。关于Numeric的合法格式请参考zh-cn_topic_0237121926.html。
+
+GAUSS-02822: "invalid sign in external 'numeric' value"
+
+SQLSTATE: 22P03
+
+错误原因: 非法的Numeric输入。
+
+解决办法: 请检查数据中是否包含非法的Numeric输入。关于Numeric的合法格式请参考zh-cn_topic_0237121926.html。
+
+GAUSS-02823: "invalid digit in external 'numeric' value"
+
+SQLSTATE: 22P03
+
+错误原因: 非法的Numeric输入。
+
+解决办法: 请检查数据中是否包含非法的Numeric输入。关于Numeric的合法格式请参考zh-cn_topic_0237121926.html。
+
+GAUSS-02824: "NUMERIC precision %d must be between 1 and %d"
+
+SQLSTATE: 22023
+
+错误原因: 非法的Numeric输入，精度超出范围。
+
+解决办法: 请根据提示修改输入满足范围要求。
+
+GAUSS-02825: "NUMERIC scale %d must be between 0 and precision %d"
+
+SQLSTATE: 22023
+
+错误原因: 非法的Numeric输入，位数超出范围。
+
+解决办法: 请根据提示修改输入满足范围要求。
+
+GAUSS-02826: "invalid NUMERIC type modifier"
+
+SQLSTATE: 22023
+
+错误原因: 非法的Numeric输入。
+
+解决办法: 请检查数据中是否包含非法的Numeric输入。关于Numeric的合法格式请参考zh-cn_topic_0237121926.html。
+
+GAUSS-02827: "count must be greater than zero"
+
+SQLSTATE: 2201G
+
+错误原因: width_bucket函数的count参数必须大于0。
+
+解决办法: 建议检查width_bucket函数的count参数是否小于或等于0。
+
+GAUSS-02828: "operand, lower bound, and upper bound cannot be NaN"
+
+SQLSTATE: 2201G
+
+错误原因: width_bucket函数的操作数，下限，上限不能为NaN。
+
+解决办法: 建议检查width_bucket函数的操作数，上限，下限是否为NaN。
+
+GAUSS-02829: "lower bound cannot equal upper bound"
+
+SQLSTATE: 2201G
+
+错误原因: width_bucket函数的下限不能等于上限。
+
+解决办法: 建议检查width_bucket函数的上下限。
+
+GAUSS-02830: "value overflows numeric format"
+
+SQLSTATE: 22003
+
+错误原因: Numeric的阶乘溢出。
+
+解决办法: 建议检查程序是否输入数据过大，否则建议应用层做处理。
+
+<br/>
+
+## GAUSS-02831 - GAUSS-02840
+
+<br/>
+
+GAUSS-02831: "zero raised to a negative power is undefined"
+
+SQLSTATE: 2201F
+
+错误原因: 不支持计算0的负数次方。
+
+解决办法: 建议检查输入中是否存在计算0的负数次方。
+
+GAUSS-02832: "a negative number raised to a non-integer power yields a complex result"
+
+SQLSTATE: 2201F
+
+错误原因: 系统内部错误。
+
+解决办法: 请检查语句或数据，或请联系技术支持工程师提供技术支持。
+
+GAUSS-02833: "cannot convert NaN to integer"
+
+SQLSTATE: 0A000
+
+错误原因: 不支持转换Numeric的NaN到整形。
+
+解决办法: 请检查是否存在NaN转换为整形的计算。
+
+GAUSS-02834: "integer out of range"
+
+SQLSTATE: 22003
+
+错误原因: 整形溢出。
+
+解决办法: 请检查语句是否存在整形溢出的可能，或者将整型转换成Numeric类型。
+
+GAUSS-02835: "cannot convert NaN to bigint"
+
+SQLSTATE: 0A000
+
+错误原因: 不支持转换Numeric的NaN到bigint类型。
+
+解决办法: 请检查是否存在NaN转换为bigint类型的计算。
+
+GAUSS-02836: "bigint out of range"
+
+SQLSTATE: 22003
+
+错误原因: bigint溢出。
+
+解决办法: 建议检查语句是否存在bigint溢出的可能，或者转换成Numeric类。
+
+GAUSS-02837: "cannot convert NaN to smallint"
+
+SQLSTATE: 0A000
+
+错误原因: 转换错误。
+
+解决办法: 查看原始数据。
+
+GAUSS-02838: "smallint out of range"
+
+SQLSTATE: 22003
+
+错误原因: 数据溢出。
+
+解决办法: 请检查语句或数据，或请联系技术支持工程师提供技术支持。
+
+GAUSS-02839: "cannot convert NaN to tinyint"
+
+SQLSTATE: 0A000
+
+错误原因: 转换错误。
+
+解决办法: 查看原始数据。
+
+GAUSS-02840: "tinyint out of range"
+
+SQLSTATE: 22003
+
+错误原因: 数据越界。
+
+解决办法: 查看原始数据大小。
+
+<br/>
+
+## GAUSS-02841 - GAUSS-02850
+
+<br/>
+
+GAUSS-02841: "expected 3-element numeric array"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02842: "expected 2-element numeric array"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02843: "expected 2-element int8 array"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02844: "numeric field overflow"
+
+SQLSTATE: 22003
+
+错误原因: 数据越界。
+
+解决办法: 查看原始数据大小。
+
+GAUSS-02845: "invalid input syntax for type double precision: '%s'"
+
+SQLSTATE: 22P02
+
+错误原因: 数据类型错误。
+
+解决办法: 请检查语句或数据，请联系技术支持工程师提供技术支持。
+
+GAUSS-02846: "division by zero"
+
+SQLSTATE: 22012
+
+错误原因: 除数为0。
+
+解决办法: 检查sql语句，对于除数可能为0的时候进行特殊处理。
+
+GAUSS-02847: "cannot take square root of a negative number"
+
+SQLSTATE: 2201F
+
+错误原因: 不允许对负数开根号。
+
+解决办法: 请检查语句或数据，请联系技术支持工程师提供技术支持。
+
+GAUSS-02849: "cannot take logarithm of zero"
+
+SQLSTATE: 2201E
+
+错误原因: 对数参数不能为0。
+
+解决办法: 请检查语句或数据，或请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02851 - GAUSS-02860
+
+<br/>
+
+GAUSS-02851: "invalid input syntax for integer: '%s'"
+
+SQLSTATE: 22P02
+
+错误原因: 源字符串错误。
+
+解决办法: 查看数据源。
+
+GAUSS-02853: "OID out of range"
+
+SQLSTATE: 22003
+
+错误原因: 数据越界。
+
+解决办法: 查看元数据。
+
+GAUSS-02854: "step size cannot equal zero"
+
+SQLSTATE: 22023
+
+错误原因: 语句错误。
+
+解决办法: 修改SQL。间隔不能是0。
+
+GAUSS-02855: "argument of ntile must be greater than zero"
+
+SQLSTATE: 22014
+
+错误原因: 系统内部错误: 获取的frame中参数表达式值应大于0。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02856: "argument of nth_value must be greater than zero"
+
+SQLSTATE: 22016
+
+错误原因: 系统内部错误: 对于某个frame，从1开始后其第n个值需大于零。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-02857: "type %u is not a range type"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02858: "range constructor flags argument must not be NULL"
+
+SQLSTATE: 22000
+
+错误原因: SQL语句错误。
+
+解决办法: 修改语句。
+
+GAUSS-02859: "range types do not match"
+
+SQLSTATE: 42804
+
+错误原因: SQL语句错误。
+
+解决办法: 修改语句。
+
+GAUSS-02860: "result of range difference would not be contiguous"
+
+SQLSTATE: 22000
+
+错误原因: SQL语句错误。
+
+解决办法: 修改语句，数据异常。
+
+<br/>
+
+## GAUSS-02861 - GAUSS-02870
+
+<br/>
+
+GAUSS-02861: "unexpected case in range_minus"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02862: "result of range union would not be contiguous"
+
+SQLSTATE: 22000
+
+错误原因: SQL语句错误。
+
+解决办法: 修改语句，数据异常。
+
+GAUSS-02863: "could not identify a hash function for type %s"
+
+SQLSTATE: 42883
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02864: "range lower bound must be less than or equal to range upper bound"
+
+SQLSTATE: 22000
+
+错误原因: SQL语句错误
+
+解决办法: 修改语句，数据异常。
+
+GAUSS-02865: "invalid range bound flags"
+
+SQLSTATE: 42601
+
+错误原因: 语法错误。
+
+解决办法: 修改SQL。
+
+GAUSS-02866: "malformed range literal: '%s'"
+
+SQLSTATE: 22P02
+
+错误原因: 语法错误。
+
+解决办法: 修改SQL。
+
+GAUSS-02867: "cannot store a toast pointer inside a range"
+
+SQLSTATE: 22000
+
+错误原因: 语法错误。
+
+解决办法: 修改SQL。
+
+GAUSS-02868: "invalid input syntax for type macaddr: '%s'"
+
+SQLSTATE: 22P02
+
+错误原因: 语法错误。
+
+解决办法: 修改SQL。
+
+GAUSS-02869: "invalid octet value in 'macaddr' value: '%s'"
+
+SQLSTATE: 22003
+
+错误原因: 语法错误。
+
+解决办法: 修改SQL。
+
+GAUSS-02870: "unrecognized QueryItem type: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02871 - GAUSS-02880
+
+<br/>
+
+GAUSS-02871: "syntax error in tsquery: '%s'"
+
+SQLSTATE: 42601
+
+错误原因: tsvector变量的语法错误。
+
+解决办法: 请检查传入tsvector类型的变量的语法。
+
+GAUSS-02872: "there is no escaped character: '%s'"
+
+SQLSTATE: 42601
+
+错误原因: tsvector变量的字符串中转义字符后没跟要转义的字符。
+
+解决办法: 保证使用转义字符后要跟要转义的字符。
+
+GAUSS-02873: "wrong position info in tsvector: '%s'"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02874: "unrecognized state in gettoken_tsvector: %d"
+
+SQLSTATE: XX000
+
+错误原因: 内部解析tsvector变量出现状态错误。
+
+解决办法: 请先检查字符串的语法问题，或者请联系技术支持工程师提供技术支持。
+
+GAUSS-02875: "identifier too long"
+
+SQLSTATE: 42622
+
+错误原因: 数据过长。
+
+解决办法: 请检查语句或数据，或请联系技术支持工程师提供技术支持。
+
+GAUSS-02879: "unexpected json parse state: %d"
+
+SQLSTATE: XX004
+
+错误原因: 语法错误。
+
+解决办法: 修改SQL。
+
+GAUSS-02880: "invalid input syntax for type json"
+
+SQLSTATE: 22P02
+
+错误原因: 语法错误。
+
+解决办法: 修改SQL。
+
+<br/>
+
+## GAUSS-02881 - GAUSS-02890
+
+<br/>
+
+GAUSS-02881: "invalid type modifier"
+
+SQLSTATE: 22023
+
+错误原因: 语法错误。
+
+解决办法: 修改SQL。
+
+GAUSS-02882: "length for type %s must be at least 1"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02883: "length for type %s cannot exceed %d"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02884: "bit string length %d does not match type bit(%d)"
+
+SQLSTATE: 22026
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02885: "'%c' is not a valid binary digit"
+
+SQLSTATE: 22P02
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02886: "'%c' is not a valid hexadecimal digit"
+
+SQLSTATE: 22P02
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02888: "bit string too long for type bit varying(%d)"
+
+SQLSTATE: 22001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02889: "negative substring length not allowed"
+
+SQLSTATE: 22011
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02891 - GAUSS-02900
+
+<br/>
+
+GAUSS-02893: "bit index %d out of valid range (0..%d)"
+
+SQLSTATE: 2202E
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02894: "new bit must be 0 or 1"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02895: "invalid input syntax for type %s: '%s'"
+
+SQLSTATE: 22P02
+
+错误原因: 非法的网络地址。
+
+解决办法: 建议检查输入的网络地址是否符合网络地址的格式。
+
+GAUSS-02896: "invalid cidr value: '%s'"
+
+SQLSTATE: 22P02
+
+错误原因: 非法的网络地址。
+
+解决办法: 建议检查输入的网络地址是否符合网络地址的格式。
+
+GAUSS-02897: "could not format inet value: %m"
+
+SQLSTATE: 22P03
+
+错误原因: 非法的网络地址。
+
+解决办法: 建议检查输入的网络地址是否符合网络地址的格式。
+
+GAUSS-02898: "invalid address family in external '%s' value"
+
+SQLSTATE: 22P03
+
+错误原因: 非法的网络地址族。
+
+解决办法: 建议检查输入的网络地址是否符合网络地址的格式。
+
+GAUSS-02899: "invalid bits in external '%s' value"
+
+SQLSTATE: 22P03
+
+错误原因: 非法的网络地址。
+
+解决办法: 建议检查输入的网络地址是否符合网络地址的格式。
+
+GAUSS-02900: "invalid length in external '%s' value"
+
+SQLSTATE: 22P03
+
+错误原因: 非法的网络地址。
+
+解决办法: 建议检查输入的网络地址是否符合网络地址的格式。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/3-GAUSS-00201-GAUSS-00300.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/3-GAUSS-00201-GAUSS-00300.md
new file mode 100644
index 0000000000000000000000000000000000000000..76151d2a926a2138e43c419007386d35f409660e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/3-GAUSS-00201-GAUSS-00300.md
@@ -0,0 +1,748 @@
+---
+title: GAUSS-00201 - GAUSS-00300
+summary: GAUSS-00201 - GAUSS-00300
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-00201 - GAUSS-00300
+
+<br/>
+
+## GAUSS-00201 - GAUSS-00210
+
+<br/>
+
+### GAUSS-00202: "unrecognized join type: %d"
+
+SQLSTATE: XX004
+
+错误原因: 不支持的语法。
+
+解决办法: 修改SQL Statement。
+
+### GAUSS-00203: "unrecognized set op: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00204: "bogus InhOption value: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00206: "subquery in FROM must have an alias"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00207: "unexpected non-SELECT command in subquery in FROM"
+
+SQLSTATE: XX000
+
+错误原因: 不支持的语法。
+
+解决办法: 修改SQL Statement。
+
+### GAUSS-00210: "cannot use aggregate function in function expression in FROM"
+
+SQLSTATE: 42803
+
+错误原因: FROM子句的函数表达式中使用了聚集函数。
+
+解决办法: FROM子句的函数表达式中不允许使用聚集函数。
+
+<br/>
+
+## GAUSS-00211 - GAUSS-00220
+
+<br/>
+
+### GAUSS-00211: "cannot use window function in function expression in FROM"
+
+SQLSTATE: 42P20
+
+错误原因: FROM子句的函数表达式中使用了窗口函数。
+
+解决办法: FROM子句的函数表达式中不能使用窗口函数。
+
+### GAUSS-00212: "column name '%s' appears more than once in USING clause"
+
+SQLSTATE: 42701
+
+错误原因: join时，使用using语法，同一个列名在using中出现多次。
+
+解决办法: join时，使用using语法，同一个列名在using中只能出现一次。
+
+### GAUSS-00214: "column '%s' specified in USING clause does not exist in left table"
+
+SQLSTATE: 42703
+
+错误原因: join时，使用using语法，在左表中找不到对应的列名。
+
+解决办法: join时，使用using语法，要保证使用的列名在左右表中。
+
+### GAUSS-00217: "column alias list for '%s' has too many entries"
+
+SQLSTATE: 42601
+
+错误原因: 对象别名中的列数超过了实际的列数。
+
+解决办法: 对象别名中的列数要和实际的列数保持一致。
+
+### GAUSS-00218: "argument of %s must not contain variables"
+
+SQLSTATE: 42P10
+
+错误原因: 类似Limit类的子句中使用了变量。
+
+解决办法: 类似Limit类的子句中不能使用变量。
+
+### GAUSS-00219: "argument of %s must not contain aggregate functions"
+
+SQLSTATE: 42803
+
+错误原因: 类似Limit类的子句中使用了聚集函数。
+
+解决办法: 类似Limit类的子句中不能使用聚集函数。
+
+### GAUSS-00220: "argument of %s must not contain window functions"
+
+SQLSTATE: 42P20
+
+错误原因: 类似Limit类的子句中使用了窗口函数。
+
+解决办法: 类似Limit类的子句中不能使用窗口函数。
+
+<br/>
+
+## GAUSS-00221 - GAUSS-00230
+
+<br/>
+
+### GAUSS-00221: "%s '%s' is ambiguous"
+
+SQLSTATE: 42702
+
+错误原因: GROUP BY/ORDER BY指定的列不明确。
+
+解决办法: 请检查确保GROUP BY/ORDER BY指定的列正确。
+
+### GAUSS-00222: "non-integer constant in %s"
+
+SQLSTATE: 42601
+
+错误原因: GROUP BY/ORDER BY指定的常量不是一个整形。
+
+解决办法: GROUP BY/ORDER BY指定的常量必须是整形。
+
+### GAUSS-00223: "%s position %d is not in select list"
+
+SQLSTATE: 42P10
+
+错误原因: GROUP BY/ORDER BY指定的常量位置不在目前列中。
+
+解决办法: GROUP BY/ORDER BY指定的常量位置要出现在目前列中。
+
+### GAUSS-00224: "window '%s' is already defined"
+
+SQLSTATE: 42P20
+
+错误原因: Window名已经被定义了。
+
+解决办法: 请使用未被定义的window名。
+
+### GAUSS-00225: "window '%s' does not exist"
+
+SQLSTATE: 42704
+
+错误原因: 指定的窗口对象不存在。
+
+解决办法: 窗口对象在使用之前要定义。
+
+### GAUSS-00226: "cannot override PARTITION BY clause of window '%s'"
+
+SQLSTATE: 42P20
+
+错误原因: 不能覆盖窗口函数中的PARTITION BY子句。
+
+解决办法: 请检查语法确认窗口函数中的PARTITION BY子句不被覆盖。
+
+### GAUSS-00227: "cannot override ORDER BY clause of window '%s'"
+
+SQLSTATE: 42P20
+
+错误原因: 不能覆盖窗口函数中的ORDER BY子句。
+
+解决办法: 请检查语法确认窗口函数中的PARTITION BY子句不被覆盖。
+
+### GAUSS-00228: "cannot override frame clause of window '%s'"
+
+SQLSTATE: 42P20
+
+错误原因: 不能覆盖窗口函数中的frame子句。
+
+解决办法: 不能覆盖窗口函数中的frame子句。
+
+### GAUSS-00229: "in an aggregate with DISTINCT, ORDER BY expressions must appear in argument list"
+
+SQLSTATE: 42P10
+
+错误原因:  聚集操作中使用DISTINCT，ORDER BY表达式的参数没有出现在目标列中。
+
+解决办法: 请检查确保聚集操作中使用DISTINCT，ORDER BY表达式时的参数在目标列中存在。
+
+### GAUSS-00230: "SELECT DISTINCT ON expressions must match initial ORDER BY expressions"
+
+SQLSTATE: 42P10
+
+错误原因: DISTINCT ON和ORDER BY同时使用时，ORDER BY后的表达式和DISTINCT ON的表达式不相同。
+
+解决办法: DISTINCT ON和ORDER BY同时使用时，ORDER BY后的表达式需要和DISTINCT ON的表达式相同。
+
+<br/>
+
+## GAUSS-00231 - GAUSS-00240
+
+<br/>
+
+### GAUSS-00231: "get_matching_location: no matching sortgroupref"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00232: "operator %s is not a valid ordering operator"
+
+SQLSTATE: 42809
+
+错误原因: 使用order by是指定的操作符不是合法的排序操作符。
+
+解决办法: 使用order by指定操作符时，只能使用 >或者<排序。
+
+### GAUSS-00233: "unrecognized sortby_dir: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00234: "unrecognized sortby_nulls: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00235: "window frame with value offset is not implemented"
+
+SQLSTATE: 0A000
+
+错误原因: 不支持的语法。
+
+解决办法: 修改SQL Statement。
+
+### GAUSS-00236: "aggregate function calls cannot be nested"
+
+SQLSTATE: 42803
+
+错误原因: 聚集函数嵌套调用。
+
+解决办法: "1.检查语句中是否存在聚集函数的嵌套调用；2.修改聚集函数的嵌套结构"。
+
+### GAUSS-00237: "aggregate function calls cannot contain window function calls"
+
+SQLSTATE: 42803
+
+错误原因: 不支持的语法。
+
+解决办法: 修改SQL Statement。
+
+### GAUSS-00238: "cache lookup failed for aggregate %u"
+
+SQLSTATE: 22P06
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00239: "window function calls cannot be nested"
+
+SQLSTATE: 42P20
+
+错误原因: 窗口函数嵌套调用。
+
+解决办法: 取消窗口函数嵌套调用。
+
+### GAUSS-00240: "aggregates not allowed in WHERE clause"
+
+SQLSTATE: 42803
+
+错误原因: WHERE子句中使用了聚集函数。
+
+解决办法: WHERE子句中不允许使用聚集函数。
+
+<br/>
+
+## GAUSS-00241 - GAUSS-00250
+
+<br/>
+
+### GAUSS-00241: "aggregates not allowed in JOIN conditions"
+
+SQLSTATE: 42803
+
+错误原因: JOIN condition中使用聚集函数。
+
+解决办法: JOIN condition中不允许使用聚集函数。
+
+### GAUSS-00242: "aggregates not allowed in GROUP BY clause"
+
+SQLSTATE: 42803
+
+错误原因: 聚集函数出现在group by子句中。
+
+解决办法: 聚集函数不允许出现在group by子句中。
+
+### GAUSS-00243: "aggregate functions not allowed in a recursive query's recursive term"
+
+SQLSTATE: 42P19
+
+错误原因: 递归查询中使用聚集函数。
+
+解决办法: 递归查询中不允许使用递归查询。
+
+### GAUSS-00244: "window functions not allowed in WHERE clause"
+
+SQLSTATE: 42P20
+
+错误原因: WHERE clause中出现窗口函数。
+
+解决办法: WHERE clause中不允许出现窗口函数。
+
+### GAUSS-00245: "window functions not allowed in JOIN conditions"
+
+SQLSTATE: 42P20
+
+错误原因: JOIN condition中使用窗口函数。
+
+解决办法: JOIN condition中不允许使用窗口函数。
+
+### GAUSS-00246: "window functions not allowed in HAVING clause"
+
+SQLSTATE: 42P20
+
+错误原因: 不支持的语法。
+
+解决办法: 修改SQL Statement。
+
+### GAUSS-00247: "window functions not allowed in GROUP BY clause"
+
+SQLSTATE: 42P20
+
+错误原因: group by子句中使用窗口函数。
+
+解决办法: group by子句中不允许使用窗口函数。
+
+### GAUSS-00248: "window functions not allowed in window definition"
+
+SQLSTATE: 42P20
+
+错误原因: 窗口函数出现在partition clause里或者order by clause里。
+
+解决办法: 窗口函数不允许出现在partition clause里或者order by clause里。
+
+### GAUSS-00249: "column '%s.%s' must appear in the GROUP BY clause or be used in an aggregate function"
+
+SQLSTATE: 42803
+
+错误原因: 使用group by时，targetlist里边的变量没有变量出现在group by的变量里，或者使用聚集函数。
+
+解决办法: 使用group by时，targetlist里边的变量必须出现在group by的变量里，或者使用聚集函数。
+
+### GAUSS-00250: "subquery uses ungrouped column '%s.%s' from outer query"
+
+SQLSTATE: 42803
+
+错误原因: 子查询中使用了外层未分组的列。
+
+解决办法: 请检查确保子查询中使用的是外层分组的列。
+
+<br/>
+
+## GAUSS-00251 - GAUSS-00260
+
+<br/>
+
+### GAUSS-00251: "yylex_init() failed: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00252: "Invalid RTE found"
+
+SQLSTATE: XX000
+
+错误原因: 引用没找到。
+
+解决办法: 修改SQL Statement。
+
+### GAUSS-00253: "cannot assign to system column '%s'"
+
+SQLSTATE: 0A000
+
+错误原因: 不能对系统列进行赋值。
+
+解决办法: 不要对系统列操作。
+
+### GAUSS-00254: "cannot set an array element to DEFAULT"
+
+SQLSTATE: 0A000
+
+错误原因: 设置了数组里类型元素的默认值。
+
+解决办法: 不要对数组类型的变量设置default。
+
+### GAUSS-00255: "cannot set a subfield to DEFAULT"
+
+SQLSTATE: 0A000
+
+错误原因: 设置了数组下标的默认值。
+
+解决办法: 数组下标不能设置默认值。
+
+### GAUSS-00256: "column '%s' is of type %s but expression is of type %s"
+
+SQLSTATE: 42804
+
+错误原因: 表达式两端的数据类型不一致。
+
+解决办法: 通过类型转换，使表达式两端的类型一致。
+
+### GAUSS-00257: "cannot assign to field '%s' of column '%s' because its type %s is not a composite type"
+
+SQLSTATE: 42804
+
+错误原因: 对非复合类型的变量指定field。
+
+解决办法: 不能对非复合类型的变量作此操作。
+
+### GAUSS-00258: "cannot assign to field '%s' of column '%s' because there is no such column in data type %s"
+
+SQLSTATE: 42703
+
+错误原因: 对非复合类型的变量指定field。
+
+解决办法: 不能对非复合类型的变量作此操作。
+
+### GAUSS-00259: "cannot assign to system column '%s'"
+
+SQLSTATE: 42703
+
+错误原因: 不能对系统列进行赋值。
+
+解决办法: 不要对系统列操作。
+
+### GAUSS-00260: "array assignment to '%s' requires type %s but expression is of type %s"
+
+SQLSTATE: 42804
+
+错误原因: 被赋值的对象和实际表达式的类型不匹配。
+
+解决办法: 修改SQL Statement。
+
+<br/>
+
+## GAUSS-00261 - GAUSS-00270
+
+<br/>
+
+### GAUSS-00261: "subfield '%s' is of type %s but expression is of type %s"
+
+SQLSTATE: 42804
+
+错误原因: 表达式两端的数据类型不一致。
+
+解决办法: 通过类型转换，使表达式两端的类型一致。
+
+### GAUSS-00262: "column '%s' specified more than once"
+
+SQLSTATE: 42701
+
+错误原因: 向表对象中插入数据时，同样的列指定了多次。
+
+解决办法: 插入数据时，相同的列只能指定一次。
+
+### GAUSS-00263: "SELECT * with no tables specified is not valid"
+
+SQLSTATE: 42601
+
+错误原因: 不支持的语法。
+
+解决办法: 修改SQL Statement。
+
+### GAUSS-00265: "Un-support feature"
+
+SQLSTATE: XX000
+
+错误原因: 不支持的特性。
+
+解决办法: 不建议使用。
+
+### GAUSS-00268: "VALUES lists must all be the same length"
+
+SQLSTATE: 42601
+
+错误原因: INSERT … VALUES语句中VALUES列表的数目与字段数目不匹配。
+
+解决办法: 1.请通过\\d tblname查看表的字段信息。2.检查INSERT … VALUES语句中VALUES的数目与表的字段数目是否匹配。3.修改INSERT … VALUES语句的语法。
+
+### GAUSS-00269: "VALUES must not contain table references"
+
+SQLSTATE: 0A000
+
+错误原因: INSERT… VALUES语句的SELECT子句中有关系表JOIN列表。
+
+解决办法: 检查INSERT … VALUES语句中的SELECT子句是否有非法的JOIN列表。重新根据INSERT语法结构修改INSERT语句。
+
+### GAUSS-00270: "VALUES must not contain OLD or NEW references"
+
+SQLSTATE: 0A000
+
+错误原因: 不支持的语法。
+
+解决办法: 修改SQL Statement。
+
+<br/>
+
+## GAUSS-00271 - GAUSS-00280
+
+<br/>
+
+### GAUSS-00271: "cannot use aggregate function in VALUES"
+
+SQLSTATE: 42803
+
+错误原因: INSERT语句中VALUES子句包含聚合函数。
+
+解决办法: INSERT语句中VALUES子句不能包含聚合函数，请检查INSERT语法是否正确，重新根据INSERT语法结构修改INSERT语句。
+
+### GAUSS-00272: "cannot use window function in VALUES"
+
+SQLSTATE: 42P20
+
+错误原因: 不支持的语法。
+
+解决办法: 修改SQL Statement。
+
+### GAUSS-00273: "INSERT has more expressions than target columns"
+
+SQLSTATE: 42601
+
+错误原因: INSERT语句中有效表达式或值的数目大于对应的目标列数目。
+
+解决办法: 请检查表达式或值的数目是否与对应的目标列数目匹配。
+
+### GAUSS-00274: "INSERT has more target columns than expressions"
+
+SQLSTATE: 42601
+
+错误原因: INSERT语句中目标列数目大于对应的有效表达式或值的数目。
+
+解决办法: 请检查目标列数目和表达式/值的数目是否匹配。如存在不匹配，请修改INSERT语句。
+
+### GAUSS-00275: "SELECT … INTO is not allowed here"
+
+SQLSTATE: 42601
+
+错误原因: 语法解析错误: SELECT语句中出现了INTO子句。
+
+解决办法: SELECT语句中不允许出现INTO子句，请检查并修改SELECT语句。
+
+### GAUSS-00276: "DEFAULT can only appear in a VALUES list within INSERT"
+
+SQLSTATE: 42601
+
+错误原因: 语法解析错误: SELECT语句中存在缺省的表达式或值。
+
+解决办法: 缺省表达式或值只能出现在INSERT语句中，请检查当前SELECT语句语法是否正确。
+
+### GAUSS-00277: "SELECT FOR UPDATE/SHARE cannot be applied to VALUES"
+
+SQLSTATE: 0A000
+
+错误原因: SELECT语句的表达式或值中包含有SELECT FOR UPDATE/SHARE子句。
+
+解决办法: SELECT语句的表达式或值中不允许包含有SELECT FOR UPDATE/SHARE子句，请检查并修改SELECT语句。
+
+### GAUSS-00278: "SELECT FOR UPDATE/SHARE is not allowed with UNION/INTERSECT/EXCEPT"
+
+SQLSTATE: 0A000
+
+错误原因: SELECT语句的集合子句（UNION/INTERSECT/EXCEPT）中包含有SELECT FOR UPDATE/SHARE子句。
+
+解决办法: SELECT语句的集合子句中不允许包含有SELECT FOR UPDATE/SHARE子句，请检查并修改SELECT语句。
+
+### GAUSS-00279: "invalid UNION/INTERSECT/EXCEPT ORDER BY clause"
+
+SQLSTATE: 0A000
+
+错误原因: 不支持的语法。
+
+解决办法: 修改SQL Statement。
+
+### GAUSS-00280: "INTO is only allowed on first SELECT of UNION/INTERSECT/EXCEPT"
+
+SQLSTATE: 42601
+
+错误原因: 语法解析错误: INTO子句在SELECT..UNION/INTERSECT/EXCEPT语句中的位置错误。
+
+解决办法: INTO只能出现在SELECT..UNION/INTERSECT/EXCEPT语句中，不能出现在SELECT..UNION/INTERSECT/EXCEPT..SELECT的第二个select子句中。
+
+<br/>
+
+## GAUSS-00281 - GAUSS-00290
+
+<br/>
+
+### GAUSS-00281: "UNION/INTERSECT/EXCEPT member statement cannot refer to other relations of same query level"
+
+SQLSTATE: 42P10
+
+错误原因: 不支持的语法。
+
+解决办法: 修改SQL Statement。
+
+### GAUSS-00282: "each %s query must have the same number of columns"
+
+SQLSTATE: 42601
+
+错误原因: 语法错误。
+
+解决办法: 修改SQL Statement。
+
+### GAUSS-00283: "cannot use aggregate function in UPDATE"
+
+SQLSTATE: 42803
+
+错误原因: UPDATE语法中，更新列的值不能为聚合函数。
+
+解决办法: 请检查UPDATE语法中待更新的列值是否有聚合函数。待更新的列值不能为聚合函数，若有，请修改更新语法。
+
+### GAUSS-00284: "cannot use window function in UPDATE"
+
+SQLSTATE: 42P20
+
+错误原因: 不支持的语法。
+
+解决办法: 修改SQL Statement。
+
+### GAUSS-00285: "UPDATE target count mismatch - internal error"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00286: "column '%s.%s' of relation '%s' does not exist"
+
+SQLSTATE: 42703
+
+错误原因: UPDATE语法中，待更新的列名在表中不存在。
+
+解决办法: 请检查UPDATE语法中待更新的列名是否正确。
+
+### GAUSS-00287: "cannot use aggregate function in RETURNING"
+
+SQLSTATE: 42803
+
+错误原因: INSERT/UPDATE/DELETE语法中的RETURNING子句非法的包含聚合函数。
+
+解决办法: INSERT/UPDATE/DELETE语法中的RETURNING子句中不能包含聚合函数，请检查语法是否正确。
+
+### GAUSS-00288: "cannot use window function in RETURNING"
+
+SQLSTATE: 42P20
+
+错误原因: 不支持的语法。
+
+解决办法: 修改SQL Statement。
+
+<br/>
+
+## GAUSS-00291 - GAUSS-00300
+
+<br/>
+
+### GAUSS-00291: "unexpected non-SELECT command in DECLARE CURSOR"
+
+SQLSTATE: XX000
+
+错误原因: 不支持的语法。
+
+解决办法: 修改SQL Statement。
+
+### GAUSS-00292: "DECLARE CURSOR must not contain data-modifying statements in WITH"
+
+SQLSTATE: 0A000
+
+错误原因: DECLARE CURSOR语法中的WITH子句含有INSERT/UPDATE/DELETE语句。
+
+解决办法: DECLARE CURSOR语法中的WITH子句不能包含INSERT/UPDATE/DELETE语句。
+
+### GAUSS-00293: "DECLARE CURSOR WITH HOLD … FOR UPDATE/SHARE is not supported"
+
+SQLSTATE: 0A000
+
+错误原因: 特性不支持: DECLARE CURSOR WITH HOLD … FOR SelectStmt子句中包含UPDATE/SHARE语句。
+
+解决办法: DECLARE CURSOR WITH HOLD … FOR SelectStmt不能包含UPDATE/SHARE子句，请检查并修改查询语句。
+
+### GAUSS-00294: "DECLARE SCROLL CURSOR … FOR UPDATE/SHARE is not supported"
+
+SQLSTATE: 0A000
+
+错误原因: 特性不支持: DECLARE SCROLL CURSOR … FOR SelectStmt子句中包含UPDATE/SHARE语句。
+
+解决办法: DECLARE SCROLL CURSOR … FOR SelectStmt can't include UPDATE/SHARE子句，请检查并修改查询语句。
+
+### GAUSS-00295: "DECLARE INSENSITIVE CURSOR … FOR UPDATE/SHARE is not supported"
+
+SQLSTATE: 0A000
+
+错误原因: 特性不支持: DECLARE INSENSITIVE CURSOR … FOR SelectStmt子句中包含UPDATE/SHARE语句。
+
+解决办法: DECLARE INSENSITIVE CURSOR … FOR SelectStmt can't include UPDATE/SHARE子句，请检查并修改查询语句。
+
+### GAUSS-00298: "PGXC Node %s: object not defined"
+
+SQLSTATE: 42704
+
+错误原因: 指定的node对象异常或者不存在。
+
+解决办法: 请检查指定的nodename是否存在或运行正常。如果异常，需要重新启动该node节点。
+
+### GAUSS-00300: "EXECUTE DIRECT cannot execute DML queries"
+
+SQLSTATE: 0A000
+
+错误原因: EXECUTE DIRECT ON ( nodename [, … ] ) query语法中在DN上执行了DML语句。
+
+解决办法: 在EXECUTE DIRECT ON ( nodename [, … ] ) query语法中不能执行DML语句，目前只支持SELECT语句。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/30-GAUSS-02901-GAUSS-03000.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/30-GAUSS-02901-GAUSS-03000.md
new file mode 100644
index 0000000000000000000000000000000000000000..1315f0b1f23a2fe0edfbb5f197d4cd6e9cfc1fb4
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/30-GAUSS-02901-GAUSS-03000.md
@@ -0,0 +1,780 @@
+---
+title: GAUSS-02901 - GAUSS-03000
+summary: GAUSS-02901 - GAUSS-03000
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-02901 - GAUSS-03000
+
+<br/>
+
+## GAUSS-02901 - GAUSS-02910
+
+<br/>
+
+GAUSS-02901: "invalid external 'cidr' value"
+
+SQLSTATE: 22P03
+
+错误原因: 非法的网络地址。
+
+解决办法: 建议检查输入的网络地址是否符合网络地址的格式。
+
+GAUSS-02902: "invalid inet bit length: %d"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02903: "invalid mask length: %d"
+
+SQLSTATE: 22023
+
+错误原因: 非法的网络地址。
+
+解决办法: 建议检查输入的网络地址是否符合网络地址的格式。
+
+GAUSS-02904: "could not format cidr value: %m"
+
+SQLSTATE: 22P03
+
+错误原因: 网络地址格式化CIDR格式失败。
+
+解决办法: 建议检查需要被格式化数据是否为有效网络地址。
+
+GAUSS-02905: "unsupported type: %u"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02906: "cannot AND inet values of different sizes"
+
+SQLSTATE: 22023
+
+错误原因: 不支持IPv4地址和IPv6同时作为AND的操作数。
+
+解决办法: 建议检查AND的左右操作数是否为相同IP地址族。
+
+GAUSS-02907: "cannot OR inet values of different sizes"
+
+SQLSTATE: 22023
+
+错误原因: 不支持IPv4地址和IPv6同时作为OR的操作数。
+
+解决办法: 建议检查OR的左右操作数是否为相同IP地址族。
+
+GAUSS-02908: "result is out of range"
+
+SQLSTATE: 22003
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02909: "cannot subtract inet values of different sizes"
+
+SQLSTATE: 22023
+
+错误原因: 不支持IPv4地址和IPv6同时作为SUBTRACT的操作数。
+
+解决办法: 建议检查SUBTRACT的操作数是否为相同IP地址族。
+
+GAUSS-02910: "arraycontsel called for unrecognized operator %u"
+
+SQLSTATE: XX000
+
+错误原因: 数组操作错误。
+
+解决办法: 请检查语句或数据，或请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02911 - GAUSS-02920
+
+<br/>
+
+GAUSS-02911: "suppress_redundant_updates_trigger: must be called as trigger"
+
+SQLSTATE: 39P01
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02912: "suppress_redundant_updates_trigger: must be called on update"
+
+SQLSTATE: 39P01
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02913: "suppress_redundant_updates_trigger: must be called before update"
+
+SQLSTATE: 39P01
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02914: "suppress_redundant_updates_trigger: must be called for each row"
+
+SQLSTATE: 39P01
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02915: "could not determine input data types"
+
+SQLSTATE: 22023
+
+错误原因: 数据类型错误。
+
+解决办法: 请检查语句或数据，或请联系技术支持工程师提供技术支持。
+
+GAUSS-02916: "neither input type is an array"
+
+SQLSTATE: 42804
+
+错误原因: 数组数据错误。
+
+解决办法: 请检查语句或数据，或请联系技术支持工程师提供技术支持。
+
+GAUSS-02917: "argument must be empty or one-dimensional array"
+
+SQLSTATE: 22000
+
+错误原因: 参数错误。
+
+解决办法: 请检查语句或数据，或请联系技术支持工程师提供技术支持。
+
+GAUSS-02918: "cannot concatenate incompatible arrays"
+
+SQLSTATE: 42804
+
+错误原因: 数组数据错误。
+
+解决办法: 请检查语句或数据，或请联系技术支持工程师提供技术支持。
+
+GAUSS-02919: "cannot concatenate incompatible arrays"
+
+SQLSTATE: 2202E
+
+错误原因: 数组数据错误。
+
+解决办法: 请检查语句或数据，或请联系技术支持工程师提供技术支持。
+
+GAUSS-02920: "invalid number of dimensions: %d"
+
+SQLSTATE: 22023
+
+错误原因: 数组的维度小于0。
+
+解决办法: 检查输入参数。
+
+<br/>
+
+## GAUSS-02921 - GAUSS-02930
+
+<br/>
+
+GAUSS-02921: "could not determine input data type"
+
+SQLSTATE: 22023
+
+错误原因: 数据类型错误。
+
+解决办法: 请检查语句或数据，或请联系技术支持工程师提供技术支持。
+
+GAUSS-02922: "array_agg_transfn called in non-aggregate context"
+
+SQLSTATE: XX000
+
+错误原因: 在非聚集操作中使用了array_agg。
+
+解决办法: 修改查询中array_agg的使用。
+
+GAUSS-02924: "no active snapshot set"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02925: "invalid snapshot data"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02926: "SPI_connect failed"
+
+SQLSTATE: SP001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02927: "SPI_finish failed"
+
+SQLSTATE: SP002
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02928: "insert or update on table '%s' violates foreign key constraint '%s'"
+
+SQLSTATE: 23503
+
+错误原因: 插入或者更新操作违反外键约束。
+
+解决办法: 建议检查外检约束是否满足当前插入或者更新操作。
+
+GAUSS-02929: "invalid confmatchtype"
+
+SQLSTATE: 42804
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02930: "unrecognized match type: %d"
+
+SQLSTATE: 42804
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02931 - GAUSS-02940
+
+<br/>
+
+GAUSS-02931: "SPI_prepare returned %d for %s"
+
+SQLSTATE: SP003
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02932: "SPI_execute_snapshot returned %d"
+
+SQLSTATE: SP005
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02933: "function '%s' must be fired for INSERT"
+
+SQLSTATE: 39P01
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02934: "function '%s' must be fired for UPDATE"
+
+SQLSTATE: 39P01
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02935: "function '%s' must be fired for DELETE"
+
+SQLSTATE: 39P01
+
+错误原因: 函数应该在delete操作时被触发，但实际没有。
+
+解决办法: 检查trigger触发逻辑是否异常。
+
+GAUSS-02936: "no pg_constraint entry for trigger '%s' on table '%s'"
+
+SQLSTATE: 42P17
+
+错误原因: 对于表上的触发器，没有对应的constraint。
+
+解决办法: 删除相关的完整性约束触发器，然后重新添加constraint。
+
+GAUSS-02937: "wrong pg_constraint entry for trigger '%s' on table '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02938: "null confkey for constraint %u"
+
+SQLSTATE: XX005
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02939: "confkey is not a 1-D smallint array"
+
+SQLSTATE: 42804
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02941 - GAUSS-02950
+
+<br/>
+
+GAUSS-02941: "conppeqop is not a 1-D Oid array"
+
+SQLSTATE: 42804
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02943: "conffeqop is not a 1-D Oid array"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02944: "referential integrity query on '%s' from constraint '%s' on '%s' gave unexpected result"
+
+SQLSTATE: XX000
+
+错误原因: 两表的主外键约束检查出错。
+
+解决办法: 检查主外键约束的表涉及的数据，查找数据错误。
+
+GAUSS-02945: "update or delete on table '%s' violates foreign key constraint '%s' on table '%s'"
+
+SQLSTATE: 23503
+
+错误原因: 更新或删除违反外键约束。
+
+解决办法: 检查更新或删除的外键值是否在主键中存在相同记录。
+
+GAUSS-02946: "no conversion function from %s to %s"
+
+SQLSTATE: 42883
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02948: "unrecognized bytea_output setting: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02949: "Node id out of range"
+
+SQLSTATE: XX001
+
+错误原因: Node ID超出范围。
+
+解决办法: 目前支持的最大DN数为4096，因此Node ID超出4096或小于0即为超出范围。请检查超出范围的Node ID并改正。
+
+GAUSS-02950: "Node id is too long"
+
+SQLSTATE: XX001
+
+错误原因: node id超出长度。
+
+解决办法: 目前支持的最大DN数为4096，因此node id的长度不小于5即为超出长度，请检查超出长度的node id并改正。
+
+<br/>
+
+## GAUSS-02951 - GAUSS-02960
+
+<br/>
+
+GAUSS-02951: "invalid backend encoding: encoding max length < 1"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02952: "could not determine which collation to use for string comparison"
+
+SQLSTATE: 42P22
+
+错误原因: 解析器不能解析隐式转换类型。
+
+解决办法: 检查当前字符串比较的collation是否可能有多个。
+
+GAUSS-02953: "could not convert string to UTF-16: error code %lu"
+
+SQLSTATE: XX000
+
+错误原因: 不能将字符串转为UTF-16格式。
+
+解决办法: 根据error code决定如何处理。
+
+GAUSS-02954: "could not compare Unicode strings: %m"
+
+SQLSTATE: XX000
+
+错误原因: 不能将字符串转为Unicode格式。
+
+解决办法: 检查出错的字符串并改正。
+
+GAUSS-02955: "index %d out of valid range, 0..%d"
+
+SQLSTATE: 2202E
+
+错误原因: 输入的索引值超出bytea字符串长度范围。
+
+解决办法: 请检查bytea字符串长度，确保索引值在其长度范围内。
+
+GAUSS-02956: "invalid name syntax"
+
+SQLSTATE: 42602
+
+错误原因: 无法将字符串分成以分隔符的字符串组。
+
+解决办法: 检查输入字符串。
+
+GAUSS-02957: "regular expression failed: %s"
+
+SQLSTATE: 2201B
+
+错误原因: 在字符串中查找特定字符串出错，可能因为字符串为空，或者查找模式不为预期等。
+
+解决办法: 请检查进行字符串查找操作的输入参数。
+
+GAUSS-02958: "field position must be greater than zero"
+
+SQLSTATE: 22023
+
+错误原因: 分隔字符串的位置小于1。
+
+解决办法: 分隔字符串的位置必须大于0，至少为1。
+
+GAUSS-02959: "string_agg_transfn called in non-aggregate context"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02960: "could not determine data type of concat() input"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02961 - GAUSS-02970
+
+<br/>
+
+GAUSS-02961: "unterminated conversion specifier"
+
+SQLSTATE: 22023
+
+错误原因: 格式化字符串没有结束符，不正确，故报此错误。
+
+解决办法: 检查该格式化字符串是否正确。
+
+GAUSS-02962: "argument number is out of range"
+
+SQLSTATE: 22003
+
+错误原因: 模式匹配的参数太多，超出整形范围。
+
+解决办法: 请重新定义模式匹配字符串，减少参数个数。
+
+GAUSS-02964: "too few arguments for format"
+
+SQLSTATE: 22023
+
+错误原因: 参数个数过少。
+
+解决办法: 检查格式化字符串中字符串个数是否与格式化变量个数匹配。
+
+GAUSS-02965: "unrecognized conversion specifier '%c'"
+
+SQLSTATE: 22023
+
+错误原因: text转为string的方式定义错误。
+
+解决办法: 检查text转为String的方式，只能为'%s','%I','%L'。
+
+GAUSS-02966: "null values cannot be formatted as an SQL identifier"
+
+SQLSTATE: 22004
+
+错误原因: 当text转为string的方式为'%I'时，输入数据不能为NULL。
+
+解决办法: 检查转换类别是否正确。
+
+GAUSS-02969: "invalid Datum pointer"
+
+SQLSTATE: 22000
+
+错误原因: 输入数据不能为空。
+
+解决办法: 请检查输入数据。
+
+GAUSS-02970: "invalid typLen: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-02971 - GAUSS-02980
+
+<br/>
+
+GAUSS-02971: "value out of range: overflow"
+
+SQLSTATE: 22003
+
+错误原因: 符点数超出了上限发生溢出。
+
+解决办法: 请检查输入数据是否超过上限。关于数据的取值范围请参考zh-cn_topic_0237121926.html。
+
+GAUSS-02972: "invalid input syntax for type real: '%s'"
+
+SQLSTATE: 22P02
+
+错误原因: 输入的需要转real类型的字符串格式不对。
+
+解决办法: 检查输入数据。
+
+GAUSS-02973: "'%s' is out of range for type real"
+
+SQLSTATE: 22003
+
+错误原因: 输入的字符串转real类型后溢出。
+
+解决办法: 检查输入数据。
+
+GAUSS-02974: "'%s' is out of range for type double precision"
+
+SQLSTATE: 22003
+
+错误原因: 输入的字符串转double类型后溢出。
+
+解决办法: 检查输入数据。
+
+GAUSS-02975: "input is out of range"
+
+SQLSTATE: 22003
+
+错误原因: 输入超出范围。
+
+解决办法: 请检查导致该错误的函数返回值是否超出了范围。关于数据的取值范围请参考zh-cn_topic_0237121926.html。
+
+GAUSS-02976: "setseed parameter %f out of range [-1,1]"
+
+SQLSTATE: XX000
+
+错误原因: setseed（）函数参数超过合法范围。
+
+解决办法: 修改setseed（）函数参数在-1到1之间。
+
+GAUSS-02978: "lower and upper bounds must be finite"
+
+SQLSTATE: 2201G
+
+错误原因: 下限和上限必须为有限值。
+
+解决办法: 请检查输入数据。
+
+GAUSS-02979: "reference to parent directory ('..') not allowed"
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02980: "absolute path not allowed"
+
+SQLSTATE: 42501
+
+错误原因: 只有数据目录和日志目录支持绝对路径，其它不支持。
+
+解决办法: 修改路径为相对路径。
+
+<br/>
+
+## GAUSS-02981 - GAUSS-02990
+
+<br/>
+
+GAUSS-02981: "path must be in or below the current directory"
+
+SQLSTATE: 42501
+
+错误原因: 路径必须在当前路径下。
+
+解决办法: 修改输入路径。
+
+GAUSS-02982: "could not stat file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 无法获得文件的状态信息。
+
+解决办法: 检查文件状态是否异常，例如文件不存在，文件读取权限不够等。
+
+GAUSS-02983: "requested length too large"
+
+SQLSTATE: 22023
+
+错误原因: 读取文件时，需要读取的长度超过了最大值。
+
+解决办法: 减少读取长度，减少到1G以下。
+
+GAUSS-02984: "could not seek in file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 不能根据offset定位文件。
+
+解决办法: 查看文件状态是否异常。
+
+GAUSS-02985: "could not read file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 必须使用数据库系统管理员读取文件。
+
+解决办法: 更换系统管理员用户进行操作。
+
+GAUSS-02987: "requested length cannot be negative"
+
+SQLSTATE: 22023
+
+错误原因: 必须使用数据库系统管理员用户获取文件信息。
+
+解决办法: 更换用户。
+
+GAUSS-02990: "requested length too large"
+
+SQLSTATE: 54000
+
+错误原因: 读取文件时，需要读取的长度超过了最大值。
+
+解决办法: 减少读取长度，减少到1G以下。
+
+<br/>
+
+## GAUSS-02991 - GAUSS-03000
+
+<br/>
+
+GAUSS-02991: "requested character too large"
+
+SQLSTATE: 54000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02992: "requested character too large for encoding: %d"
+
+SQLSTATE: 54000
+
+错误原因: 输入的字符串太长。
+
+解决办法: 仅支持unicode编码字符，请检查输入字符串。
+
+GAUSS-02993: "TIMESTAMP(%d)%s precision must not be negative"
+
+SQLSTATE: 22023
+
+错误原因: timestamp类型的精度不能小于0。
+
+解决办法: 检查timestamp类型的精度。
+
+GAUSS-02994: "timestamp out of range: '%s'"
+
+SQLSTATE: 22020
+
+错误原因: timestamp类型数值越界。
+
+解决办法: 检查timestamp类型的数值。
+
+GAUSS-02995: "date/time value '%s' is no longer supported"
+
+SQLSTATE: 0A000
+
+错误原因: 输入的待转换为timestamp类型的字符串值解析错误。
+
+解决办法: 请检查输入的字符串格式是否正确。待转换为timestamp的字符串格式需满足"日期/时间类型"格式要求。
+
+GAUSS-02996: "unexpected dtype %d while parsing timestamp '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-02997: "timestamp out of range"
+
+SQLSTATE: 22008
+
+错误原因: timestamp数据越界。
+
+解决办法: 检查timestamp类型的数值是否合法。
+
+GAUSS-02998: "timestamp cannot be NaN"
+
+SQLSTATE: 22008
+
+错误原因: timestamp类型数据不能为无限值。
+
+解决办法: 检查输入数据。
+
+GAUSS-02999: "smalldatetime out of range: '%s'"
+
+SQLSTATE: 22008
+
+错误原因: 数值越界。
+
+解决办法: 检查输入数据。
+
+GAUSS-03000: "unexpected dtype %d while parsing smalldatetime '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/31-GAUSS-03001-GAUSS-03100.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/31-GAUSS-03001-GAUSS-03100.md
new file mode 100644
index 0000000000000000000000000000000000000000..59252fadf25a608d0991963f4f0574e56c8297e3
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/31-GAUSS-03001-GAUSS-03100.md
@@ -0,0 +1,812 @@
+---
+title: GAUSS-03001 - GAUSS-03100
+summary: GAUSS-03001 - GAUSS-03100
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-03001 - GAUSS-03100
+
+<br/>
+
+## GAUSS-03001 - GAUSS-03010
+
+<br/>
+
+GAUSS-03001: "smalldatetime out of range"
+
+SQLSTATE: 22008
+
+错误原因: 数值越界。
+
+解决办法: 检查输入数据。
+
+GAUSS-03002: "smalldatetime cannot be NaN"
+
+SQLSTATE: 22008
+
+错误原因: smalldatetime类型数据不能为无限值。
+
+解决办法: 检查输入数据。
+
+GAUSS-03003: "timestamp(%d) precision must be between %d and %d"
+
+SQLSTATE: 22023
+
+错误原因: timestamp的精度只能界于0到6之间。
+
+解决办法: 检查输入的精度是否越界。
+
+GAUSS-03004: "unexpected dtype %d while parsing timestamptz '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03005: "interval out of range"
+
+SQLSTATE: 22008
+
+错误原因: interval类型数据越界。
+
+解决办法: 检查输入数据。
+
+GAUSS-03006: "unexpected dtype %d while parsing interval '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03007: "could not convert interval to tm"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03008: "invalid INTERVAL type modifier"
+
+SQLSTATE: 22023
+
+错误原因: 非法的interval类型精度值。
+
+解决办法: 检查类型精度值。
+
+GAUSS-03009: "INTERVAL(%d) precision must not be negative"
+
+SQLSTATE: 22023
+
+错误原因: interval类型的精度值不能为负。
+
+解决办法: 检查类型精度值。
+
+GAUSS-03010: "invalid INTERVAL typmod: 0x%x"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03011 - GAUSS-03020
+
+<br/>
+
+GAUSS-03013: "invalid argument for EncodeSpecialTimestamp"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03014: "cannot subtract infinite timestamps"
+
+SQLSTATE: 22008
+
+错误原因: 不能减去无限值的timestamp值。
+
+解决办法: 检查输入数据。
+
+GAUSS-03015: "expected 2-element interval array"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03016: "timestamp units '%s' not supported"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03017: "timestamp units '%s' not recognized"
+
+SQLSTATE: 22023
+
+错误原因: timestamp没有时间单位。
+
+解决办法: 检查输入参数。
+
+GAUSS-03018: "timestamp with time zone units '%s' not supported"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03019: "timestamp with time zone units '%s' not recognized"
+
+SQLSTATE: 22023
+
+错误原因: 带timezone的timestamp没有时间单位。
+
+解决办法: 检查输入参数。
+
+GAUSS-03020: "interval units '%s' not supported"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03021 - GAUSS-03030
+
+<br/>
+
+GAUSS-03021: "interval units '%s' not recognized"
+
+SQLSTATE: 22023
+
+错误原因: interval类型没有时间单位。
+
+解决办法: 检查输入参数。
+
+GAUSS-03022: "could not convert to time zone '%s'"
+
+SQLSTATE: 22023
+
+错误原因: 无法转换到指定的time zone。
+
+解决办法: 检查输入参数。关于数据的取值范围请参考zh-cn_topic_0237121926.html。
+
+GAUSS-03023: "time zone '%s' not recognized"
+
+SQLSTATE: 22023
+
+错误原因: 需要转换的timezone不能识别。
+
+解决办法: 检查输入参数。
+
+GAUSS-03024: "interval time zone '%s' must not specify month"
+
+SQLSTATE: 22023
+
+错误原因: interval time zone类型不能指定月份。
+
+解决办法: 检查输入参数。关于数据的取值范围请参考zh-cn_topic_0237121926.html。
+
+GAUSS-03027: "the format is not correct!"
+
+SQLSTATE: 0A000
+
+错误原因: 日期的格式不正确。
+
+解决办法: 请检查输入数据的格式是否正确。关于数据的取值范围请参考zh-cn_topic_0237121926.html。
+
+GAUSS-03028: "the year is invalid"
+
+SQLSTATE: 0A000
+
+错误原因: 年份值非法。
+
+解决办法: 请检查年份的位数是否为4。
+
+GAUSS-03029: "the month is invalid!"
+
+SQLSTATE: 0A000
+
+错误原因: 月份值非法。
+
+解决办法: 请检查月份的位数是否为2。
+
+GAUSS-03030: "the format is not correct"
+
+SQLSTATE: 0A000
+
+错误原因: 时间字符串中有多于两个的分隔符，不合法。
+
+解决办法: 请检查输入数据的合法性。关于数据的取值范围请参考zh-cn_topic_0237121926.html。
+
+<br/>
+
+## GAUSS-03031 - GAUSS-03040
+
+<br/>
+
+GAUSS-03031: "the time is not correct!"
+
+SQLSTATE: 0A000
+
+错误原因: 时间字符串长度越界。
+
+解决办法: 请检查输入数据的范围是否满足要求。
+
+GAUSS-03032: "the hour is invalid!"
+
+SQLSTATE: 0A000
+
+错误原因: 小时值非法。
+
+解决办法: 请检查小时的位数是否为2。
+
+GAUSS-03033: "the minute is invalid!"
+
+SQLSTATE: 0A000
+
+错误原因: 分钟值非法。
+
+解决办法: 请检查分钟的位数是否为2。
+
+GAUSS-03034: "the year = %d is illegal"
+
+SQLSTATE: 0A000
+
+错误原因: 年份值非法。
+
+解决办法: 请检查年份值是否在0-9999之间。
+
+GAUSS-03035: "the day = %d for february in leap year is illegal"
+
+SQLSTATE: 0A000
+
+错误原因: 闰年的二月份日期非法。
+
+解决办法: 检查日期值。
+
+GAUSS-03036: "the day = %d for big month is illegal"
+
+SQLSTATE: 0A000
+
+错误原因: 大月份的日期非法。
+
+解决办法: 检查日期值。
+
+GAUSS-03037: "the day = %d for small month is illegal"
+
+SQLSTATE: 0A000
+
+错误原因: 小月份的日期非法。
+
+解决办法: 检查日期值。
+
+GAUSS-03038: "the day = %d for February in commen year is illegal"
+
+SQLSTATE: 0A000
+
+错误原因: 平年的二月份日期非法。
+
+解决办法: 检查日期值。
+
+GAUSS-03039: "the month = %d is illegal"
+
+SQLSTATE: 0A000
+
+错误原因: 月份值非法。
+
+解决办法: 请检查月份值是否在1-12之间。
+
+GAUSS-03040: "the hour = %d is illegal"
+
+SQLSTATE: 0A000
+
+错误原因: 小时值非法。
+
+解决办法: 请检查小时值是否在0-24之间。
+
+<br/>
+
+## GAUSS-03041 - GAUSS-03050
+
+<br/>
+
+GAUSS-03041: "the minute = %d is illegal"
+
+SQLSTATE: 0A000
+
+错误原因: 分钟值非法。
+
+解决办法: 请检查分钟值是否在0-59之间。
+
+GAUSS-03042: "the second = %d is illegal"
+
+SQLSTATE: 0A000
+
+错误原因: 秒值非法。
+
+解决办法: 请检查秒值是否在0-59之间。
+
+GAUSS-03043: "encoding conversion from %s to ASCII not supported"
+
+SQLSTATE: 0A000
+
+错误原因: 不支持从当前编码格式转换为ascii。
+
+解决办法: 请检查输入字符的编码格式。
+
+GAUSS-03044: "too many points requested"
+
+SQLSTATE: 54000
+
+错误原因: 需要获取的点太多。
+
+解决办法: 检查输入参数。
+
+GAUSS-03045: "could not format 'path' value"
+
+SQLSTATE: 22023
+
+错误原因: 无法获取path信息。
+
+解决办法: 检查输入参数。
+
+GAUSS-03046: "invalid input syntax for type box: '%s'"
+
+SQLSTATE: 22P02
+
+错误原因: box类型数值非法。
+
+解决办法: 检查输入参数。
+
+GAUSS-03047: "invalid input syntax for type line: '%s'"
+
+SQLSTATE: 22P02
+
+错误原因: line类型数据非法。
+
+解决办法: 检查输入参数。
+
+GAUSS-03048: "type 'line' not yet implemented"
+
+SQLSTATE: 0A000
+
+错误原因: line类型不支持。
+
+解决办法: 检查此版本是否支持line类型。
+
+GAUSS-03049: "invalid input syntax for type path: '%s'"
+
+SQLSTATE: 22P02
+
+错误原因: path类型数据非法。
+
+解决办法: 检查输入参数。
+
+GAUSS-03050: "invalid number of points in external 'path' value"
+
+SQLSTATE: 22P03
+
+错误原因: path中的点数非法。
+
+解决办法: 检查输入参数。
+
+<br/>
+
+## GAUSS-03051 - GAUSS-03060
+
+<br/>
+
+GAUSS-03051: "invalid input syntax for type point: '%s'"
+
+SQLSTATE: 22P02
+
+错误原因: point类型的数据非法。
+
+解决办法: 检查输入参数。
+
+GAUSS-03052: "invalid input syntax for type lseg: '%s'"
+
+SQLSTATE: 22P02
+
+错误原因: lseg类型的数据非法。
+
+解决办法: 检查输入参数。
+
+GAUSS-03053: "function 'dist_lb' not implemented"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03054: "function 'close_lb' not implemented"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03056: "invalid input syntax for type polygon: '%s'"
+
+SQLSTATE: 22P02
+
+错误原因: 输入的polygon类型值无法解析。
+
+解决办法: 检查输入参数，应该以点对(a,b)格式使用","间隔的字符串输入。
+
+GAUSS-03057: "invalid number of points in external 'polygon' value"
+
+SQLSTATE: 22P03
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03058: "function 'poly_distance' not implemented"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03059: "function 'path_center' not implemented"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03060: "open path cannot be converted to polygon"
+
+SQLSTATE: 22023
+
+错误原因: 没有回路的path不能转换成多角形。
+
+解决办法: 检查输入路径是否有回路。
+
+<br/>
+
+## GAUSS-03061 - GAUSS-03070
+
+<br/>
+
+GAUSS-03061: "invalid input syntax for type circle: '%s'"
+
+SQLSTATE: 22P02
+
+错误原因: circle类型值非法。
+
+解决办法: 检查输入参数。
+
+GAUSS-03062: "could not format 'circle' value"
+
+SQLSTATE: 22023
+
+错误原因: 使用输入的circle类型值无法构造circle类型数据。
+
+解决办法: 无（不可能出现）。
+
+GAUSS-03063: "invalid radius in external 'circle' value"
+
+SQLSTATE: 22P03
+
+错误原因: 输入的circle的半径小于0。
+
+解决办法: 检查输入的circle值。
+
+GAUSS-03064: "cannot convert circle with radius zero to polygon"
+
+SQLSTATE: 0A000
+
+错误原因: 不能将半径为0的圆转换为多角形。
+
+解决办法: 检查输入的circle值。
+
+GAUSS-03065: "must request at least 2 points"
+
+SQLSTATE: 22023
+
+错误原因: 输出至少包含两个点。
+
+解决办法: 检查输入的需要点数。
+
+GAUSS-03066: "cannot convert empty polygon to circle"
+
+SQLSTATE: 22023
+
+错误原因: 不能将没有点集的多角形转换为circle型值。
+
+解决办法: 检查输入的多角形值。
+
+GAUSS-03067: "NULL pointer"
+
+SQLSTATE: XX005
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03068: "value '%s' is out of range for type integer"
+
+SQLSTATE: 22003
+
+错误原因: 参数值超过了integer类型的取值范围。
+
+解决办法: 请检查输入参数。关于数据的取值范围请参考zh-cn_topic_0237121926.html。
+
+GAUSS-03069: "value '%s' is out of range for type smallint"
+
+SQLSTATE: 22003
+
+错误原因: 参数值超过了smallint类型的取值范围。
+
+解决办法: 请检查输入参数。关于数据的取值范围请参考zh-cn_topic_0237121926.html。
+
+GAUSS-03070: "value '%s' is out of range for 8-bit integer"
+
+SQLSTATE: 22003
+
+错误原因: 参数值超过了8位int类型的取值范围。
+
+解决办法: 请检查输入参数。关于数据的取值范围请参考zh-cn_topic_0237121926.html。
+
+<br/>
+
+## GAUSS-03071 - GAUSS-03080
+
+<br/>
+
+GAUSS-03071: "unsupported result size: %d"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03072: "invalid regular expression: %s"
+
+SQLSTATE: 2201B
+
+错误原因: 输入的表达式非法。
+
+解决办法: 检查数据库encoding。
+
+GAUSS-03073: "invalid regexp option: '%c'"
+
+SQLSTATE: 22023
+
+错误原因: 非法的regexp转换类型。
+
+解决办法: 检查输入参数。
+
+GAUSS-03074: "invalid escape string"
+
+SQLSTATE: 22025
+
+错误原因: 非法的转义字符。
+
+解决办法: 检查输入参数。
+
+GAUSS-03075: "regexp_split does not support the global option"
+
+SQLSTATE: 22023
+
+错误原因: regexp_split目前不支持global选项。
+
+解决办法: 修改分隔选项。
+
+GAUSS-03076: "invalid match ending position"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03077: "invalid match starting position"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03078: "unexpected dtype %d while parsing abstime '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03079: "cannot convert abstime 'invalid' to timestamp"
+
+SQLSTATE: 0A000
+
+错误原因: 绝对时间非法，无法转换为timestamp类型。
+
+解决办法: 请检查输入参数。关于数据的取值范围请参考zh-cn_topic_0237121926.html。
+
+GAUSS-03080: "unexpected dtype %d while parsing reltime '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03081 - GAUSS-03090
+
+<br/>
+
+GAUSS-03081: "invalid status in external 'tinterval' value"
+
+SQLSTATE: 22P03
+
+错误原因: 输入的字符串中获得的interval错误状态与数据对应的状态不一致。
+
+解决办法: 检测输入字符串。
+
+GAUSS-03082: "cannot convert reltime 'invalid' to interval"
+
+SQLSTATE: 0A000
+
+错误原因: reltime类型值非法，不能转换为interval类型。
+
+解决办法: 检查输入参数。
+
+GAUSS-03083: "invalid input syntax for type tinterval: '%s'"
+
+SQLSTATE: 22007
+
+错误原因: 输入字符串转换为tinterval类型时语法错误。
+
+解决办法: 检查输入字符串。
+
+GAUSS-03084: "invalid input syntax for type boolean: '%s'"
+
+SQLSTATE: 22P02
+
+错误原因: 输入字符串转换为Boolean类型时语法错误。
+
+解决办法: 检查输入字符串。
+
+GAUSS-03085: "missing dimension value"
+
+SQLSTATE: 22P02
+
+错误原因: 没有指定数组的维度。
+
+解决办法: 检查输入字符串。
+
+GAUSS-03086: "missing ']' in array dimensions"
+
+SQLSTATE: 22P02
+
+错误原因: 指定数组的维度时缺少"]"。
+
+解决办法: 检查输入字符串。
+
+GAUSS-03087: "upper bound cannot be less than lower bound"
+
+SQLSTATE: 2202E
+
+错误原因: 数组上界不能小于下界。
+
+解决办法: 检查输入字符串。
+
+GAUSS-03088: "array value must start with '{' or dimension information"
+
+SQLSTATE: 22P02
+
+错误原因: 数组字符串必须以"{"开始或者维度信息。
+
+解决办法: 检查输入字符串。
+
+GAUSS-03089: "missing assignment operator"
+
+SQLSTATE: 22P02
+
+错误原因: 如果指定数组维度信息，必须给出"="操作符。
+
+解决办法: 检查输入字符串。
+
+GAUSS-03090: "array dimensions incompatible with array literal"
+
+SQLSTATE: 22P02
+
+错误原因: 数组的维度与数组的数据不相符。
+
+解决办法: 检查输入字符串。
+
+<br/>
+
+## GAUSS-03091 - GAUSS-03100
+
+<br/>
+
+GAUSS-03091: "malformed array literal: '%s'"
+
+SQLSTATE: 22P02
+
+错误原因: 数组输入数据格式错误。
+
+解决办法: 请确认输入字符串，是否可以转换成数组常量。
+
+GAUSS-03092: "multidimensional arrays must have array expressions with matching dimensions"
+
+SQLSTATE: 22P02
+
+错误原因: 多维的数组必须具有与维度相匹配的数组表达式。
+
+解决办法: 检查输入字符串。
+
+GAUSS-03093: "array size exceeds the maximum allowed (%d)"
+
+SQLSTATE: 54000
+
+错误原因: 数组长度超出了最大值。
+
+解决办法: 请检查输入字符串中包含的数组元素是否超过了错误信息中指定的数值。
+
+GAUSS-03095: "invalid number of dimensions: %d"
+
+SQLSTATE: 22P03
+
+错误原因: 数组的维度小于0。
+
+解决办法: 检查输入参数。
+
+GAUSS-03096: "invalid array flags"
+
+SQLSTATE: 22P03
+
+错误原因: 数组标志非法，只能为0或1。
+
+解决办法: 检查输入参数。
+
+GAUSS-03097: "wrong element type"
+
+SQLSTATE: 42804
+
+错误原因: 数组元素的类型不一致。
+
+解决办法: 检查输入参数。
+
+GAUSS-03098: "insufficient data left in message"
+
+SQLSTATE: 22P03
+
+错误原因: message中剩余的长度小于message首获取的长度值。
+
+解决办法: 检查当前字符串。
+
+GAUSS-03099: "improper binary format in array element %d"
+
+SQLSTATE: 22P03
+
+错误原因: 读完数组时，缓冲区还有数据。
+
+解决办法: 输入数据有误，检查之。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/32-GAUSS-03101-GAUSS-03200.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/32-GAUSS-03101-GAUSS-03200.md
new file mode 100644
index 0000000000000000000000000000000000000000..0bec48627e181bc498d994d92f89dee17d224074
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/32-GAUSS-03101-GAUSS-03200.md
@@ -0,0 +1,828 @@
+---
+title: GAUSS-03101 - GAUSS-03200
+summary: GAUSS-03101 - GAUSS-03200
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-03101 - GAUSS-03200
+
+<br/>
+
+## GAUSS-03101 - GAUSS-03110
+
+<br/>
+
+GAUSS-03101: "wrong number of array subscripts"
+
+SQLSTATE: 2202E
+
+错误原因: 使用定长元素的数组只能是一维，不支持多维元素替换。
+
+解决办法: 检查输入参数。
+
+GAUSS-03102: "array subscript out of range"
+
+SQLSTATE: 2202E
+
+错误原因: 一维的索引值超出数组容纳的元素值，非法。
+
+解决办法: 检查输入参数。
+
+GAUSS-03103: "cannot assign null value to an element of a fixed-length array"
+
+SQLSTATE: 22004
+
+错误原因: 不能将定长元素数组的元素值替换为NULL值。
+
+解决办法: 检查输入参数。
+
+GAUSS-03104: "updates on slices of fixed-length arrays not implemented"
+
+SQLSTATE: 0A000
+
+错误原因: 不支持在使用定长元素的数组上进行更新。
+
+解决办法: 检查输入参数。
+
+GAUSS-03105: "source array too small"
+
+SQLSTATE: 2202E
+
+错误原因: 源数组中没有要替换的索引号的元素。
+
+解决办法: 检查输入参数。
+
+GAUSS-03106: "invalid nargs: %d"
+
+SQLSTATE: XX000
+
+错误原因: array的参数非法。
+
+解决办法: 修改查询中array的参数。
+
+GAUSS-03107: "null input array"
+
+SQLSTATE: XX000
+
+错误原因: array没有参数。
+
+解决办法: 为array增加合法参数。
+
+GAUSS-03108: "null array element not allowed in this context"
+
+SQLSTATE: 22004
+
+错误原因: 如果当前数组元素标志不为NULL，则不允许数组元素的值为NULL。
+
+解决办法: 检查输入参数。
+
+GAUSS-03110: "invalid arguments to array_create_iterator"
+
+SQLSTATE: XX000
+
+错误原因: array_create_iterator函数的参数非法。
+
+解决办法: 为array_create_iterator修改合法参数。
+
+<br/>
+
+## GAUSS-03111 - GAUSS-03120
+
+<br/>
+
+GAUSS-03111: "dimension array or low bound array cannot be null"
+
+SQLSTATE: 22004
+
+错误原因: 数组维度和填充下标不能为NULL。
+
+解决办法: 检查输入参数。
+
+GAUSS-03112: "could not determine data type of input"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03113: "wrong range of array subscripts"
+
+SQLSTATE: 2202E
+
+错误原因: 数组的维度下界必须是1。
+
+解决办法: 检查输入参数。
+
+GAUSS-03114: "dimension values cannot be null"
+
+SQLSTATE: 22004
+
+错误原因: 数组的维度不能为空。
+
+解决办法: 检查输入参数。
+
+GAUSS-03115: "unrecognized encoding: '%s'"
+
+SQLSTATE: 22023
+
+错误原因: 根据当前的字符串无法找到对应的encoding。
+
+解决办法: 检查输入字符串。
+
+GAUSS-03116: "overflow - encode estimate too small"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03117: "overflow - decode estimate too small"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03118: "invalid hexadecimal digit: '%c'"
+
+SQLSTATE: 22023
+
+错误原因: 非法的十六进制字符。
+
+解决办法: 请检查输入参数。关于数据的取值范围请参考zh-cn_topic_0237121926.html。
+
+GAUSS-03119: "invalid hexadecimal data: odd number of digits"
+
+SQLSTATE: 22023
+
+错误原因: 转换后的十六进制数有奇数位，非法。
+
+解决办法: 检查输入参数。
+
+GAUSS-03120: "unexpected '='"
+
+SQLSTATE: 22023
+
+错误原因: 此处不应有"="。
+
+解决办法: 检查输入参数。
+
+<br/>
+
+## GAUSS-03121 - GAUSS-03130
+
+<br/>
+
+GAUSS-03121: "invalid symbol"
+
+SQLSTATE: 22023
+
+错误原因: 非法字符。
+
+解决办法: 检查输入参数。
+
+GAUSS-03122: "invalid end sequence"
+
+SQLSTATE: 22023
+
+错误原因: 字符串解析完毕后没有到尾部。
+
+解决办法: 检查输入参数。
+
+GAUSS-03123: "'char' out of range"
+
+SQLSTATE: 22003
+
+错误原因: int4转换为char时溢出。
+
+解决办法: 请检查输入参数。关于数据的取值范围请参考zh-cn_topic_0237121926.html。
+
+GAUSS-03124: "invalid input syntax for type oid: '%s'"
+
+SQLSTATE: 22P02
+
+错误原因: 输入字符串转换为OID类型时语法错误。
+
+解决办法: 检查输入参数。
+
+GAUSS-03125: "value '%s' is out of range for type oid"
+
+SQLSTATE: 22003
+
+错误原因: 值超出OID类型的值域。
+
+解决办法: 检查输入参数。
+
+GAUSS-03126: "oidvector has too many elements"
+
+SQLSTATE: 22023
+
+错误原因: OID类型数组有太多的元素值。
+
+解决办法: 最多支持666个值。
+
+GAUSS-03127: "invalid oidvector data"
+
+SQLSTATE: 22P03
+
+错误原因: OID类型数组里的元素不为OID类型，非法。
+
+解决办法: 检查输入参数。
+
+GAUSS-03129: "typmod array must be type cstring[]"
+
+SQLSTATE: 2202E
+
+错误原因: 当前函数中处理的数组类型必须为cstring型。
+
+解决办法: 检查数组元素类型。
+
+GAUSS-03130: "typmod array must be one-dimensional"
+
+SQLSTATE: 2202E
+
+错误原因: 当前函数处理的数组必须为一维。
+
+解决办法: 检查数组维度。
+
+<br/>
+
+## GAUSS-03131 - GAUSS-03140
+
+<br/>
+
+GAUSS-03131: "typmod array must not contain nulls"
+
+SQLSTATE: 22004
+
+错误原因: 当前函数处理的数组元素不能为空。
+
+解决办法: 检查数组元素是否为空。
+
+GAUSS-03132: "unrecognized key word: '%s'"
+
+SQLSTATE: 22P02
+
+错误原因: ACL的关键字只能是group或user。
+
+解决办法: 检查ACL的关键字是否正确。
+
+GAUSS-03133: "missing name"
+
+SQLSTATE: 22P02
+
+错误原因: 在关键字group或user之后缺少名称。
+
+解决办法: 检查ACL的语法。
+
+GAUSS-03134: "missing '=' sign"
+
+SQLSTATE: 22P02
+
+错误原因: 缺少group或user的权限赋值符。
+
+解决办法: 检查ACL的语法。
+
+GAUSS-03135: "invalid mode character: must be one of '%s'"
+
+SQLSTATE: 22P02
+
+错误原因: 权限模式非法，必须为"arwdDxtXUCTc"之一。
+
+解决办法: 检查ACL的语法。
+
+GAUSS-03136: "a name must follow the '/' sign"
+
+SQLSTATE: 22P02
+
+错误原因: 如果将权限返回sysadmin，需要在"/"后指定名称。
+
+解决办法: 检查ACL的语法。
+
+GAUSS-03137: "invalid size: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03138: "ACL array contains wrong data type"
+
+SQLSTATE: 22023
+
+错误原因: ACL数组中包含了非ACL元素。
+
+解决办法: 检查ACL数组是否合法。
+
+GAUSS-03139: "ACL arrays must be one-dimensional"
+
+SQLSTATE: 22023
+
+错误原因: ACL数组只能是一维。
+
+解决办法: 检查ACL数组是否合法。
+
+GAUSS-03140: "ACL arrays must not contain null values"
+
+SQLSTATE: 22004
+
+错误原因: ACL数组中不能包含NULL值。
+
+解决办法: 检查ACL数组是否合法。
+
+<br/>
+
+## GAUSS-03141 - GAUSS-03150
+
+<br/>
+
+GAUSS-03141: "extra garbage at the end of the ACL specification"
+
+SQLSTATE: 22P02
+
+错误原因: 需要转换为ACL数组的字符串解析完毕后还剩余多余字符。
+
+解决办法: 检查输入字符串。
+
+GAUSS-03142: "unrecognized objtype abbreviation: %c"
+
+SQLSTATE: XX000
+
+错误原因: acldefault函数输入参数错误。
+
+解决办法: 不要手动调用acldefault函数，或修改acldefault函数第一个入参。
+
+GAUSS-03143: "grant options cannot be granted back to your own grantor"
+
+SQLSTATE: 0LP01
+
+错误原因: 赋权出现回环，即赋权赋回给原始的赋权者。
+
+解决办法: 检查ACL规则。
+
+GAUSS-03144: "dependent privileges exist"
+
+SQLSTATE: 2BP01
+
+错误原因: 删除权限时，存在依赖权限。
+
+解决办法: 使用cascade关键字级联删除。
+
+GAUSS-03145: "null ACL"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03146: "aclinsert is no longer supported"
+
+SQLSTATE: 0A000
+
+错误原因: aclinsert函数不支持。
+
+解决办法: 不能手动调用不支持的aclinsert函数。
+
+GAUSS-03147: "aclremove is no longer supported"
+
+SQLSTATE: 0A000
+
+错误原因: aclremove函数不支持。
+
+解决办法: 不能手动调用不支持的aclremove函数。
+
+GAUSS-03148: "unrecognized privilege type: '%s'"
+
+SQLSTATE: 22023
+
+错误原因: makeaclitem函数参数不正确。
+
+解决办法: 不要手动调用makeaclitem函数，或者makeaclitem函数第三个参数。
+
+GAUSS-03149: "unrecognized aclright: %d"
+
+SQLSTATE: XX000
+
+错误原因: aclexplode函数参数不正确。
+
+解决办法: 不要手动调用aclexplode函数，或者修改aclexplode函数参数。
+
+GAUSS-03150: "function '%s' does not exist"
+
+SQLSTATE: 42883
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03151 - GAUSS-03160
+
+<br/>
+
+GAUSS-03151: "must be member of role '%s'"
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03152: "int2vector has too many elements"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03153: "invalid int2vector data"
+
+SQLSTATE: 22P03
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03156: "gin_tsquery_consistent requires eight arguments"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03157: "patternsel called for operator without a negator"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03158: "unrecognized consttype: %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03159: "join operator should take two arguments"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03161 - GAUSS-03170
+
+<br/>
+
+GAUSS-03161: "found unexpected null value in index '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03162: "could not find RelOptInfo for given relids"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03163: "case insensitive matching not supported on type bytea"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03164: "could not determine which collation to use for ILIKE"
+
+SQLSTATE: 42P22
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03165: "regular-expression matching not supported on type bytea"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03166: "unrecognized ptype: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03167: "missing support function %d for attribute %d of index '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 索引列不支持特定操作。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03168: "could not match index to operand"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03169: "unsupported GIN indexqual type: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03170: "invalid input value for enum %s: '%s'"
+
+SQLSTATE: 22P02
+
+错误原因: enum的输入非法。
+
+解决办法: 修改enum的输入。
+
+<br/>
+
+## GAUSS-03171 - GAUSS-03180
+
+<br/>
+
+GAUSS-03171: "invalid internal value for enum: %u"
+
+SQLSTATE: 22P03
+
+错误原因: enum参数非法。
+
+解决办法: 修改enum参数。
+
+GAUSS-03172: "invalid argument for enum_recv"
+
+SQLSTATE: XX000
+
+错误原因: enum_recv参数非法。
+
+解决办法: 修改enum_recv参数。
+
+GAUSS-03173: "could not determine actual enum type"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03174: "enum %s contains no values"
+
+SQLSTATE: 55000
+
+错误原因: enum中没有值。
+
+解决办法: 为enum中赋值。
+
+GAUSS-03175: "could not open tablespace directory '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 无法打开table space的路径。
+
+解决办法: 检查table space对应的路径是否损坏。
+
+GAUSS-03176: "Parameter value should not be negative."
+
+SQLSTATE: 22023
+
+错误原因: 参数不能为负。
+
+解决办法: 修改参数为正。
+
+GAUSS-03177: "tablespace with OID %u does not exist"
+
+SQLSTATE: XX000
+
+错误原因: 在出口程序中检查用户的访问权限时，发现不存在对应的表空间。
+
+解决办法: 检查pg_tablespace系统表中是否存在该表空间定义。
+
+GAUSS-03178: "database with OID %u does not exist"
+
+SQLSTATE: XX000
+
+错误原因: 在检查用户的访问权限时，发现不存在对应的数据库。
+
+解决办法: 检查pg_database系统表中关于数据库的状态是否正常。
+
+GAUSS-03179: "SPI connect failure - returned %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03180: "failed to execute query '%s' on node '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03181 - GAUSS-03190
+
+<br/>
+
+GAUSS-03181: "array of weight must be one-dimensional"
+
+SQLSTATE: 2202E
+
+错误原因: 函数ts_rank_wtt的第一个参数的数组不是一维数组。
+
+解决办法: 函数ts_rank_wtt的第一个参数必须是一维的。
+
+GAUSS-03182: "array of weight is too short"
+
+SQLSTATE: 2202E
+
+错误原因: 函数ts_rank_wtt的参数中，一维数组的元素个数小于4个。
+
+解决办法: 保证一维数组的元素个数大于等于4个。
+
+GAUSS-03183: "array of weight must not contain nulls"
+
+SQLSTATE: 22004
+
+错误原因: 函数ts_rank_wtt的第一个参数，数组元素中包含了空值。
+
+解决办法: 数组元素中不能包含空值。
+
+GAUSS-03184: "weight out of range"
+
+SQLSTATE: 22023
+
+错误原因: 函数ts_rank_wtt的第一个参数，数组元素中的数据大于1.0。
+
+解决办法: 数组的元组不能大于1。
+
+GAUSS-03185: "more than one function named '%s'"
+
+SQLSTATE: 42725
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03186: "more than one operator named %s"
+
+SQLSTATE: 42725
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03187: "missing argument"
+
+SQLSTATE: 42601
+
+错误原因: 删除操作符时缺少参数。
+
+解决办法: 删除操作符时要使用和定义时一样的参数。
+
+GAUSS-03188: "too many arguments"
+
+SQLSTATE: 54023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03189: "expected a left parenthesis"
+
+SQLSTATE: 22P02
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03190: "expected a right parenthesis"
+
+SQLSTATE: 22P02
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03191 - GAUSS-03200
+
+<br/>
+
+GAUSS-03191: "expected a type name"
+
+SQLSTATE: 22P02
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03192: "improper type name"
+
+SQLSTATE: 22P02
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03193: "input of anonymous composite types is not implemented"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03194: "malformed record literal: '%s'"
+
+SQLSTATE: 22P02
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03195: "wrong number of columns: %d, expected %d"
+
+SQLSTATE: 42804
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03196: "wrong data type: %u, expected %u"
+
+SQLSTATE: 42804
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03197: "improper binary format in record column %d"
+
+SQLSTATE: 22P03
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03198: "cannot compare dissimilar column types %s and %s at record column %d"
+
+SQLSTATE: 42804
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03199: "cannot compare record types with different numbers of columns"
+
+SQLSTATE: 42804
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03200: "invalid input syntax for type tid: '%s'"
+
+SQLSTATE: 22P02
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/33-GAUSS-03201-GAUSS-03300.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/33-GAUSS-03201-GAUSS-03300.md
new file mode 100644
index 0000000000000000000000000000000000000000..50647cace7f926386f1084389e28c045eae30f21
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/33-GAUSS-03201-GAUSS-03300.md
@@ -0,0 +1,820 @@
+---
+title: GAUSS-03201 - GAUSS-03300
+summary: GAUSS-03201 - GAUSS-03300
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-03201 - GAUSS-03300
+
+<br/>
+
+## GAUSS-03201 - GAUSS-03210
+
+<br/>
+
+GAUSS-03201: "ctid isn't of type TID"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03202: "currtid cannot handle views with no CTID"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03203: "the view has no rules"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03204: "only one select rule is allowed in views"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03205: "currtid cannot handle this view"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03206: "no operand in tsquery: '%s'"
+
+SQLSTATE: 42601
+
+错误原因: tsquery类型的字符串中，操作符后没有操作的变量。
+
+解决办法: 检查输入的字符串，保证每个操作符后都有操作的对象。
+
+GAUSS-03207: "value is too big in tsquery: '%s'"
+
+SQLSTATE: 54000
+
+错误原因: tsquery类型的字符串中，操作符后的字符串的长度超过了限制(1<<20) - 1。
+
+解决办法: 检查输入的字符串长度，不要超过上限。
+
+GAUSS-03208: "operand is too long in tsquery: '%s'"
+
+SQLSTATE: 54000
+
+错误原因: tsquery类型的字符串中，字符串的长度超过了限制(1<<11) - 1。
+
+解决办法: 检查输入的字符串长度，不要超过上限。
+
+GAUSS-03209: "word is too long in tsquery: '%s'"
+
+SQLSTATE: 54000
+
+错误原因: tsquery类型的字符串中，字符串的长度超过了限制(1<<11) - 1。
+
+解决办法: 检查输入的字符串长度，不要超过上限。
+
+GAUSS-03210: "tsquery stack too small"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03211 - GAUSS-03220
+
+<br/>
+
+GAUSS-03211: "malformed tsquery: operand not found"
+
+SQLSTATE: XX000
+
+错误原因: tsquery类型的字符串中未找到操作符。
+
+解决办法: 检查数据的输入，保证tsquery类型的变量包含操作符。
+
+GAUSS-03212: "malformed tsquery: extra nodes"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03213: "unrecognized operator type: %d"
+
+SQLSTATE: XX000
+
+错误原因: 输入了错误的操作符。
+
+解决办法: 检查输入的操作符，只识别！ | & 三种。
+
+GAUSS-03214: "unrecognized tsquery node type: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03215: "invalid size of tsquery"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03216: "invalid tsquery: invalid weight bitmap"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03218: "invalid tsquery: total operand length exceeded"
+
+SQLSTATE: XX000
+
+错误原因: tsquery类型的字符串超过了上限(1<<20) - 1。
+
+解决办法: 请检查字符串的长度，不要超过上限。
+
+GAUSS-03219: "invalid tsquery: unrecognized operator type %d"
+
+SQLSTATE: XX000
+
+错误原因: 输入了错误的操作符。
+
+解决办法: 检查输入的操作符，只识别！ | & 三种。
+
+<br/>
+
+## GAUSS-03221 - GAUSS-03230
+
+<br/>
+
+GAUSS-03221: "cannot accept a value of type any"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03222: "cannot display a value of type any"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03223: "cannot accept a value of type anyarray"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03224: "cannot accept a value of type anyenum"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03225: "cannot accept a value of type anyrange"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03226: "cannot accept a value of type trigger"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03227: "cannot display a value of type trigger"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03228: "cannot accept a value of type language_handler"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03229: "cannot display a value of type language_handler"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03230: "cannot accept a value of type fdw_handler"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03231 - GAUSS-03240
+
+<br/>
+
+GAUSS-03231: "cannot display a value of type fdw_handler"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03232: "cannot accept a value of type internal"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03233: "cannot display a value of type internal"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03234: "cannot accept a value of type opaque"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03235: "cannot display a value of type opaque"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03236: "cannot accept a value of type anyelement"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03237: "cannot display a value of type anyelement"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03238: "cannot accept a value of type anynonarray"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03239: "cannot display a value of type anynonarray"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03240: "cannot accept a value of a shell type"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03241 - GAUSS-03250
+
+<br/>
+
+GAUSS-03241: "cannot display a value of a shell type"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03242: "cannot accept a value of type pg_node_tree"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03243: "TIME(%d)%s precision must not be negative"
+
+SQLSTATE: 22023
+
+错误原因: 时间格式精度不能为负。
+
+解决办法: 修改时间格式精度为正。
+
+GAUSS-03244: "date/time value 'current' is no longer supported"
+
+SQLSTATE: 0A000
+
+错误原因: 不支持current值。
+
+解决办法: 不使用current值。
+
+GAUSS-03245: "date out of range: '%s'"
+
+SQLSTATE: 22008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03246: "date out of range"
+
+SQLSTATE: 22008
+
+错误原因: 日期超过限制。
+
+解决办法: 修改日期为合法值。
+
+GAUSS-03248: "cannot subtract infinite dates"
+
+SQLSTATE: 22008
+
+错误原因: 日期数据没有开始或者结束。
+
+解决办法: 修改日期数据为合法值。
+
+GAUSS-03249: "date out of range for timestamp"
+
+SQLSTATE: 22008
+
+错误原因: 日期超过时间戳范围。
+
+解决办法: 修改日期为合法值。
+
+GAUSS-03250: "cannot convert reserved abstime value to date"
+
+SQLSTATE: 0A000
+
+错误原因: 不能将绝对时间转换为对应时间格式。
+
+解决办法: 修改日期格式为合法值。
+
+<br/>
+
+## GAUSS-03251 - GAUSS-03260
+
+<br/>
+
+GAUSS-03251: "time out of range"
+
+SQLSTATE: 22008
+
+错误原因: 越界。
+
+解决办法: 查看原始数据。
+
+GAUSS-03252: "'time' units '%s' not recognized"
+
+SQLSTATE: 22023
+
+错误原因: SQL参数不对。
+
+解决办法: 修改SQL。
+
+GAUSS-03253: "time zone displacement out of range"
+
+SQLSTATE: 22009
+
+错误原因: 越界。
+
+解决办法: 查看原始数据。
+
+GAUSS-03254: "'time with time zone' units '%s' not recognized"
+
+SQLSTATE: 22023
+
+错误原因: SQL参数不对。
+
+解决办法: 修改SQL。
+
+GAUSS-03255: "'interval' time zone '%s' not valid"
+
+SQLSTATE: 22023
+
+错误原因: 非法数据。
+
+解决办法: 查看原始数据。
+
+GAUSS-03256: "compressed data is corrupt"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03257: "value too long for type character(%d)"
+
+SQLSTATE: 22001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03258: "value too long for type character varying(%d)"
+
+SQLSTATE: 22001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03259: "value too long for type nvarchar2(%d)"
+
+SQLSTATE: 22001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03260: "SPI_prepare failed for '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03261 - GAUSS-03270
+
+<br/>
+
+GAUSS-03261: "failed to get pg_rewrite tuple for rule %u"
+
+SQLSTATE: SP005
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03262: "failed to get pg_rewrite tuple for view %u"
+
+SQLSTATE: SP005
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03264: "tgargs is null for trigger %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03265: "unrecognized confmatchtype: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03266: "unrecognized confupdtype: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03267: "unrecognized confdeltype: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03268: "invalid constraint type '%c'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03269: "Deparse of this query at planning is not supported yet"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03270: "Deparse of this query at planning not supported yet"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03271 - GAUSS-03280
+
+<br/>
+
+GAUSS-03271: "rule '%s' has unsupported event type %d"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03272: "unrecognized query command type: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03273: "too many subquery RTEs in INSERT"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03274: "too many values RTEs in INSERT"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03275: "both subquery and values RTEs in INSERT"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03278: "Invalid distribution type"
+
+SQLSTATE: 42000
+
+错误原因: distribute后面所使用的分布方式不是系统所支持的。
+
+解决办法: 检查当前所使用的分布方式是否是系统所支持的。
+
+GAUSS-03279: "unexpected utility statement type"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03280: "bogus varlevelsup: %d offset %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03281 - GAUSS-03290
+
+<br/>
+
+GAUSS-03281: "bogus varattno for OUTER_VAR var: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03282: "bogus varattno for INNER_VAR var: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03283: "bogus varattno for INDEX_VAR var: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03284: "bogus varno: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03285: "bogus varattno for subquery var: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03286: "bogus varattno for remotequery var: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03287: "cannot decompile join alias var in plan tree"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03288: "failed to find plan for subquery %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03289: "failed to find plan for CTE %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03290: "bogus oprkind: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03291 - GAUSS-03300
+
+<br/>
+
+GAUSS-03291: "could not find window clause for winref %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03292: "unrecognized sublink type: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03293: "argument type %s of FieldStore is not a tuple type"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03294: "unrecognized oprkind: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03295: "date/time field value out of range: '%s'"
+
+SQLSTATE: 22008
+
+错误原因: date/time字段的值超出正常范围，如月份取值应在1-12之间等。
+
+解决办法: 请修正输入，确保date/time字段取值合法，符合日期和时间的正常格式。
+
+GAUSS-03296: "interval field value out of range: '%s'"
+
+SQLSTATE: 22015
+
+错误原因: interval字段的值超出范围。
+
+解决办法: 修正输入，确保interval字段取值合法。
+
+GAUSS-03297: "time zone displacement out of range: '%s'"
+
+SQLSTATE: 22009
+
+错误原因: time zone displacement字段的值超出范围。
+
+解决办法: 修正输入，确保time zone displacement字段取值合法。
+
+GAUSS-03298: "invalid input syntax for type %s: '%s'"
+
+SQLSTATE: 22007
+
+错误原因: 非法的网络地址。
+
+解决办法: 建议检查输入的网络地址是否符合网络地址的格式。
+
+GAUSS-03299: "only system admin can lock the cluster for backup"
+
+SQLSTATE: 42501
+
+错误原因: 没有权限锁定集群进行备份，只有系统管理员才有权限。
+
+解决办法: 使用系统管理员进行此项操作。
+
+GAUSS-03300: "internal error while locking the cluster for backup"
+
+SQLSTATE: 08000
+
+错误原因: 在锁定集群进行备份时发生了内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/34-GAUSS-03301-GAUSS-03400.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/34-GAUSS-03301-GAUSS-03400.md
new file mode 100644
index 0000000000000000000000000000000000000000..fed812e71c5c6beb39a2d3bb92971f71dbc862f4
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/34-GAUSS-03301-GAUSS-03400.md
@@ -0,0 +1,828 @@
+---
+title: GAUSS-03301 - GAUSS-03400
+summary: GAUSS-03301 - GAUSS-03400
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-03301 - GAUSS-03400
+
+<br/>
+
+## GAUSS-03301 - GAUSS-03310
+
+<br/>
+
+GAUSS-03301: "cannot lock cluster for backup in presence of %d uncommitted prepared transactions"
+
+SQLSTATE: 55P03
+
+错误原因: 存在未提交的prepared transaction时无法锁定集群进行备份。
+
+解决办法: 等待prepared transaction提交后，在锁定集群进行备份。
+
+GAUSS-03302: "cannot lock cluster for backup, lock is already held"
+
+SQLSTATE: 55P03
+
+错误原因: 未获取到锁，无法锁定集群进行备份。
+
+解决办法: 等待其它持锁作业完成后，再进行此项操作。
+
+GAUSS-03304: "word is too long (%ld bytes, max %ld bytes)"
+
+SQLSTATE: 54000
+
+错误原因: 单词太长，超过允许的最大值。
+
+解决办法: 使用不超过长度限制的单词。
+
+GAUSS-03305: "string is too long for tsvector (%ld bytes, max %ld bytes)"
+
+SQLSTATE: 54000
+
+错误原因: 字符串太长，超过允许的最大长度。
+
+解决办法: 使用不超过长度限制的字符串。
+
+GAUSS-03306: "positions array too long"
+
+SQLSTATE: XX000
+
+错误原因: 输入的字符串长度超过了tsvector类型允许的最大长度( (1<<20) - 1)。
+
+解决办法: 调整输入的字符串长度。
+
+GAUSS-03307: "invalid size of tsvector"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03308: "invalid tsvector: lexeme too long"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03309: "invalid tsvector: maximum total lexeme length exceeded"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03311 - GAUSS-03320
+
+<br/>
+
+GAUSS-03311: "position information is misordered"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03312: "unrecognized LC category: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03313: "could not convert string to UTF-8: error code %lu"
+
+SQLSTATE: 22021
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03314: "invalid LC_COLLATE setting"
+
+SQLSTATE: D0011
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03315: "invalid LC_CTYPE setting"
+
+SQLSTATE: D0011
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03316: "could not create locale '%s': %m"
+
+SQLSTATE: 22023
+
+错误原因: 无法创建locale，操作系统找不到指定的locale名称。
+
+解决办法: 请检查创建的locale是否是操作系统支持的locale。
+
+GAUSS-03317: "collations with different collate and ctype values are not supported on this platform"
+
+SQLSTATE: 0A000
+
+错误原因: 当前操作系统不支持含有不同collate和ctype值的collation。
+
+解决办法: collation允许指定各列数据的排序规则。创建collation时，如果设置LC_COLLATE和LC_CTYPE的值，则要求二者设置为相同的值。
+
+GAUSS-03318: "nondefault collations are not supported on this platform"
+
+SQLSTATE: 0A000
+
+错误原因: 非缺省的collation不支持。
+
+解决办法: 使用平台缺省的collation。
+
+GAUSS-03319: "wcstombs_l is not available"
+
+SQLSTATE: 22021
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03320: "mbstowcs_l is not available"
+
+SQLSTATE: 22021
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03321 - GAUSS-03330
+
+<br/>
+
+GAUSS-03321: "invalid multibyte character for locale"
+
+SQLSTATE: 22021
+
+错误原因: 待转换的字符是一个非法的多字节字符。该字符是符合服务器locale的，但是服务器设置的LC_CTYPE locale与数据库的字符编码不兼容。
+
+解决办法: 服务器设置的locale与数据库字符编码不兼容，请重新设置服务器的locale。
+
+GAUSS-03322: "unsupported XML feature"
+
+SQLSTATE: 0A000
+
+错误原因: 不支持XML特性。
+
+解决办法: 不使用XML特性相关功能。
+
+GAUSS-03323: "invalid XML comment"
+
+SQLSTATE: 2200S
+
+错误原因: 非法的XML注释。
+
+解决办法: XML注释的格式为<- … ->。
+
+GAUSS-03324: "not an XML document"
+
+SQLSTATE: 2200L
+
+错误原因: xmltotext函数中的输入的xml不是合法的XML文档。
+
+解决办法: 修改XML数据，使之变为合法的XML文档。
+
+GAUSS-03325: "invalid XML processing instruction"
+
+SQLSTATE: 42601
+
+错误原因: XML处理指令（PI）非法，其target name不应为"xml"（不分大小写）。
+
+解决办法: 修改XML文档中PI的target name。
+
+GAUSS-03326: "invalid XML processing instruction"
+
+SQLSTATE: 42601
+
+错误原因: XML处理指令（PI）非法，其target name不应为"xml"（不分大小写）。
+
+解决办法: 修改XML文档中PI的target name。
+
+GAUSS-03327: "xmlvalidate is not implemented"
+
+SQLSTATE: 0A000
+
+错误原因: XMLVALIDATE功能没有实现。
+
+解决办法: 不使用XMLVALIDATE函数。
+
+GAUSS-03328: "could not initialize XML library"
+
+SQLSTATE: XX000
+
+错误原因: 系统错误，初始化XML库失败。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03329: "could not set up XML error handler"
+
+SQLSTATE: 0A000
+
+错误原因: 系统错误，无法设置XML error handler。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03330: "xml_ereport called with invalid PgXmlErrorContext"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03331 - GAUSS-03340
+
+<br/>
+
+GAUSS-03331: "xml_errorHandler called with invalid PgXmlErrorContext"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03332: "invalid query"
+
+SQLSTATE: 22000
+
+错误原因: 非法的查询操作。
+
+解决办法: 修正查询语句。
+
+GAUSS-03333: "xpath expression result type %d is unsupported"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03334: "invalid array for XML namespace mapping"
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误，XML命名空间映射的数组不合法，必须是2维数组。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03335: "empty XPath expression"
+
+SQLSTATE: 22000
+
+错误原因: Xpath表达式为空。
+
+解决办法: 在调用XML函数时提供合法的Xpath表达式。
+
+GAUSS-03336: "neither namespace name nor URI may be null"
+
+SQLSTATE: 22004
+
+错误原因: XML命名空间或其对应的URL为空。
+
+解决办法: 修改XML的命名空间或URL，使其非空。
+
+GAUSS-03338: "LIKE pattern must not end with escape character"
+
+SQLSTATE: 22025
+
+错误原因: Like谓词中的pattern不应以转换字符结束。
+
+解决办法: 修正like后面的pattern，去掉尾部的转义字符。
+
+GAUSS-03339: "invalid format specification for an interval value"
+
+SQLSTATE: 22007
+
+错误原因: 在把date/time转换为char时，输入参数不能是interval类型。
+
+解决办法: 输入参数应使用正确的时间类型。
+
+GAUSS-03340: "'EEEE' must be the last pattern used"
+
+SQLSTATE: 42601
+
+错误原因: 数值格式错误，"EEEE"应出现在最后部分。
+
+解决办法: 修正数值格式，重新执行。
+
+<br/>
+
+## GAUSS-03341 - GAUSS-03350
+
+<br/>
+
+GAUSS-03341: "'9' must be ahead of 'PR'"
+
+SQLSTATE: 42601
+
+错误原因: 数值格式错误，"9"应出现在"PR"之前。
+
+解决办法: 修正数值格式，重新执行。
+
+GAUSS-03342: "'0' must be ahead of 'PR'"
+
+SQLSTATE: 42601
+
+错误原因: 数值格式错误， "0"应出现在"PR"之前。
+
+解决办法: 修正数值格式，重新执行。
+
+GAUSS-03343: "multiple decimal points"
+
+SQLSTATE: 42601
+
+错误原因: 数值格式错误，不应有多个小数点。
+
+解决办法: 修正数值格式，重新执行。
+
+GAUSS-03345: "cannot use 'S' twice"
+
+SQLSTATE: 42601
+
+错误原因: 数值格式错误，"S"不应出现两次。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03346: "cannot use 'S' and 'PL'/'MI'/'SG'/'PR' together"
+
+SQLSTATE: 42601
+
+错误原因: 数值格式错误， "S"不应与"PL"、"MI"、"SG"及"PR"同时出现。
+
+解决办法: 修正数值格式，重新执行。
+
+GAUSS-03347: "cannot use 'S' and 'MI' together"
+
+SQLSTATE: 42601
+
+错误原因: 数值格式错误，"S"不应与"MI"同时出现。
+
+解决办法: 修正数值格式，重新执行。
+
+GAUSS-03348: "cannot use 'S' and 'PL' together"
+
+SQLSTATE: 42601
+
+错误原因: 数值格式错误，"S"不应和"PL"同时出现。
+
+解决办法: 修正数值格式，重新执行。
+
+GAUSS-03349: "cannot use 'S' and 'SG' together"
+
+SQLSTATE: 42601
+
+错误原因: 数值格式错误，"S"不应与"SG"同时出现。
+
+解决办法: 修正数值格式，重新执行。
+
+GAUSS-03350: "cannot use 'PR' and 'S'/'PL'/'MI'/'SG' together"
+
+SQLSTATE: 42601
+
+错误原因: 数值格式错误，"PR"不应与"S"、"PL"、"MI"及"SG"同时出现。
+
+解决办法: 修正数值格式，重新执行。
+
+<br/>
+
+## GAUSS-03351 - GAUSS-03360
+
+<br/>
+
+GAUSS-03351: "cannot use 'EEEE' twice"
+
+SQLSTATE: 42601
+
+错误原因: 数值格式错误，"EEEE"不应出现两次。
+
+解决办法: 修正数值格式，重新执行。
+
+GAUSS-03352: "'EEEE' is incompatible with other formats"
+
+SQLSTATE: 42601
+
+错误原因: 数值格式错误，"EEEE"与其它格式不兼容。
+
+解决办法: 修正数值格式，重新执行。
+
+GAUSS-03353: "invalid data for match in format string"
+
+SQLSTATE: 22007
+
+错误原因: 数据转换为timestamp格式时，format参数值不正确，不符合timestamp格式。
+
+解决办法: 请修正转换格式format的字符串，使其能正确表示timestamp格式，重新执行。
+
+GAUSS-03354: "'%s' is not a number"
+
+SQLSTATE: 22P02
+
+错误原因: 数字串中不应有非数字字符。
+
+解决办法: 请修正数字字符串，重新执行。
+
+GAUSS-03355: "could not determine which collation to use for lower() function"
+
+SQLSTATE: 42P22
+
+错误原因: 在调用lower函数时无法确定使用的collation。
+
+解决办法: 应该使用COLLATE子句显式设定collation。
+
+GAUSS-03356: "could not determine which collation to use for upper() function"
+
+SQLSTATE: 42P22
+
+错误原因: 在调用upper函数时无法确定使用的collation。
+
+解决办法: 应该使用COLLATE子句显式设定collation。
+
+GAUSS-03357: "could not determine which collation to use for initcap() function"
+
+SQLSTATE: 42P22
+
+错误原因: 在调用initcap函数时无法确定使用的collation。
+
+解决办法: 应该使用COLLATE子句显式设定collation。
+
+GAUSS-03358: " RR/RRRR should be between 0 - 9999"
+
+SQLSTATE: 22008
+
+错误原因: 日期时间错误，年份应该在0-9999范围内。
+
+解决办法: 请修正年份数值在合理范围内。
+
+GAUSS-03359: "invalid combination of date conventions"
+
+SQLSTATE: 22007
+
+错误原因: 日期格式错误，不应在混合使用公历和ISO星期日期格式。
+
+解决办法: 修正日期格式，使用公历日期或者ISO星期日期。
+
+GAUSS-03360: "conflicting values for '%s' field in formatting string"
+
+SQLSTATE: 22007
+
+错误原因: 日期时间格式错误，同一字段被重复赋予不同的取值。
+
+解决办法: 不应设置冲突的值，取消第二次赋值。
+
+<br/>
+
+## GAUSS-03361 - GAUSS-03370
+
+<br/>
+
+GAUSS-03361: "source string too short for '%s' formatting field"
+
+SQLSTATE: 22007
+
+错误原因: 日期时间格式错误，源字符串长度小于需要读取的长度。
+
+解决办法: 如果源字符串不是定长的，尝试使用"FM"修饰符。
+
+GAUSS-03362: "invalid value '%s' for '%s'"
+
+SQLSTATE: 22007
+
+错误原因: 日期时间格式错误，需要长度的字符中有部分字符无法解析。
+
+解决办法: 请修正要转换为日期时间的字符格式，使其符合日期时间的字符格式要求，如果源字符串不是定长的，尝试使用"FM"修饰符。
+
+GAUSS-03363: "value for '%s' in source string is out of range"
+
+SQLSTATE: 22008
+
+错误原因: 日期时间格式错误，字符串的值超出正常范围。
+
+解决办法: 请根据提示调整字符取值，使其满足范围要求。
+
+GAUSS-03364: "character does not match format string"
+
+SQLSTATE: 22007
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03365: "input length of format 'US'/'us'/'FF'/'ff' must between 0 and 6"
+
+SQLSTATE: 22008
+
+错误原因: 日期时间的值超出范围，"US/us/FF/ff"格式的长度必须在0-6之间。
+
+解决办法: 修正格式长度，其值应在0-6之间。
+
+GAUSS-03366: "'TZ'/'tz' format patterns are not supported in to_date"
+
+SQLSTATE: 0A000
+
+错误原因: 不支持"TZ/tz"格式的日期。
+
+解决办法: 修正时间格式。
+
+GAUSS-03367: "invalid input string for 'Y,YYY'"
+
+SQLSTATE: 22007
+
+错误原因: 输入的字符串不满足日期时间格式要求。
+
+解决办法: 输入的字符串必须是"Y，YYY"格式。
+
+GAUSS-03368: "invalid data for match in date string"
+
+SQLSTATE: 22007
+
+错误原因: 日期时间格式错误，在日期字符串中用来匹配的数据不合法。
+
+解决办法: 使用合法的字符文本查询匹配。
+
+GAUSS-03369: "invalid data for '%s = %d' ,value must be %s"
+
+SQLSTATE: 22008
+
+错误原因: 日期时间格式错误，输入数据与制定值不一致。
+
+解决办法: 按指定值输入数据。
+
+GAUSS-03370: " seconds of minute conflicts with seconds in day"
+
+SQLSTATE: 22007
+
+错误原因: 日期时间格式错误，分钟和天中的秒数不一致。
+
+解决办法: 修正日期时间格式错误。
+
+<br/>
+
+## GAUSS-03371 - GAUSS-03380
+
+<br/>
+
+GAUSS-03371: " minutes of hour conflicts with seconds in day"
+
+SQLSTATE: 22007
+
+错误原因: 日期时间格式错误，小时中的分钟数和天中的秒数不一致。
+
+解决办法: 修正日期时间格式错误。
+
+GAUSS-03372: "hour conflicts with seconds in day"
+
+SQLSTATE: 22007
+
+错误原因: 日期时间格式错误，小时数和天中的秒数不一致。
+
+解决办法: 修正日期时间格式错误。
+
+GAUSS-03373: "hour '%d' is invalid for the 12-hour clock"
+
+SQLSTATE: 22007
+
+错误原因: 日期时间格式错误， 12小时制中的小时数不合法。
+
+解决办法: 12小时制中的小时数应在1-12之间。
+
+GAUSS-03374: "inconsistent use of year %04d and 'BC'"
+
+SQLSTATE: 22007
+
+错误原因: 日期时间格式错误，公元前的年份不合法，应为正值。
+
+解决办法: 修正年份数值在正数范围内。
+
+GAUSS-03375: "year conflicts with Julian date"
+
+SQLSTATE: 22007
+
+错误原因: 日期时间格式错误，年份与儒略日期冲突。
+
+解决办法: 修正日期时间格式错误。
+
+GAUSS-03376: "month conflicts with Julian date"
+
+SQLSTATE: 22007
+
+错误原因: 日期时间格式错误，月份与儒略日期冲突。
+
+解决办法: 修正日期时间格式错误。
+
+GAUSS-03377: "day conflicts with Julian date"
+
+SQLSTATE: 22007
+
+错误原因: 日期时间格式错误，日期与儒略日期冲突。
+
+解决办法: 修正日期时间格式错误。
+
+GAUSS-03378: "cannot calculate day of year without year information"
+
+SQLSTATE: 22007
+
+错误原因: 日期时间格式错误，缺少年份信息，无法计算一年当中的日期。
+
+解决办法: 修正日期时间格式错误。
+
+GAUSS-03379: "month conflicts with days of year"
+
+SQLSTATE: 22007
+
+错误原因: 日期时间格式错误，月份与年中的日期冲突。
+
+解决办法: 修正日期时间格式错误。
+
+GAUSS-03380: "days of month conflicts with days of year"
+
+SQLSTATE: 22007
+
+错误原因: 日期时间格式错误，月中的日期与年中的日期冲突。
+
+解决办法: 修正日期时间格式错误。
+
+<br/>
+
+## GAUSS-03381 - GAUSS-03390
+
+<br/>
+
+GAUSS-03381: "long_int_add inner error, addend or summand is null pointer"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。在长整形和整形相加时遇到空指针。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-03382: "long_int_add inner error, length of long_int not support."
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03383: "'EEEE' not supported for input"
+
+SQLSTATE: 0A000
+
+错误原因: 字符串转换为数值的输入不支持"EEEE"格式。
+
+解决办法: 不使用"EEEE"格式作为转换为数值的字符串。
+
+GAUSS-03384: "'RN' not supported for input"
+
+SQLSTATE: 0A000
+
+错误原因: 字符串转换为数值的输入不支持"RN"格式。
+
+解决办法: 不使用"RN"格式作为转换为数值的字符串。
+
+GAUSS-03385: "'%c' not supported"
+
+SQLSTATE: 0A000
+
+错误原因: 字符不是可以转换为数字的字符。
+
+解决办法: 字符转换为数值时，使用合法的字符。
+
+GAUSS-03386: "to_number only support 16 bytes hex to decimal conversion or plen less than 0."
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03387: "invalid number format model"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03388: "invalid number"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03389: "ts_rewrite query must return two tsquery columns"
+
+SQLSTATE: 22023
+
+错误原因: 系统错误: text search重写查询必须返回两个tsquery列。
+
+解决办法: 检查函数ts_rewrite调用时输入的查询语句，保证语句只能返回两列。
+
+GAUSS-03390: "array_typanalyze was invoked for non-array type %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03391 - GAUSS-03400
+
+<br/>
+
+GAUSS-03391: "insufficient pg_statistic slots for array stats"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03392: "must be system admin or have the same role to cancel queries running in other server processes"
+
+SQLSTATE: 42501
+
+错误原因: 用户没有权限取消查询。
+
+解决办法: 要取消运行在其它服务器进程中的查询，用户必须是相同管理员或相同角色。
+
+GAUSS-03394: "must be system admin or have the same role to terminate other backend"
+
+SQLSTATE: 42501
+
+错误原因: 用户没有权限终止其它后台进程。
+
+解决办法: 要终止运行在其它服务器进程中的查询，用户必须是相同管理员或相同角色。
+
+GAUSS-03395: "must be system admin to signal the postmaster"
+
+SQLSTATE: 42501
+
+错误原因: 重新装载数据库配置参数需要具有系统管理员权限。
+
+解决办法: 切换为系统管理员后，重新装载数据库配置参数。
+
+GAUSS-03396: "must be system admin to rotate log files"
+
+SQLSTATE: 42501
+
+错误原因: 只有系统管理员才能轮换日志文件。
+
+解决办法: 先获取系统管理员权限，再执行日志文件轮换。
+
+GAUSS-03397: "fail to drop the user"
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03398: "index '%s' already contains data"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03399: "failed to re-find scan position within index '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 偏移量大于内部最大偏移量。
+
+解决办法: 属于预防性错误机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03400: "hash does not support mark/restore"
+
+SQLSTATE: XX000
+
+错误原因: 哈希不支持记录或者恢复scan position。
+
+解决办法: 属于功能不支持，请检查使用方式。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/35-GAUSS-03401-GAUSS-03500.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/35-GAUSS-03401-GAUSS-03500.md
new file mode 100644
index 0000000000000000000000000000000000000000..832728371f2ee755dca1ee33fd55dbb520a824c8
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/35-GAUSS-03401-GAUSS-03500.md
@@ -0,0 +1,668 @@
+---
+title: GAUSS-03401 - GAUSS-03500
+summary: GAUSS-03401 - GAUSS-03500
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-03401 - GAUSS-03500
+
+<br/>
+
+## GAUSS-03401 - GAUSS-03410
+
+<br/>
+
+GAUSS-03402: "hash_redo: unimplemented"
+
+SQLSTATE: XX000
+
+错误原因: 哈希索引不支持的redo。
+
+解决办法: 属于功能不支持，请检查使用方式和场景。
+
+GAUSS-03404: "index row size %lu exceeds hash maximum %lu"
+
+SQLSTATE: 54000
+
+错误原因: 元组的大小超过一个页的大小。
+
+解决办法: 内部错误。检查是否使用了toast。
+
+GAUSS-03405: "failed to add index item to '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 向哈希索引页插入元组失败。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-03407: "hash AM does not use P_NEW"
+
+SQLSTATE: XX000
+
+错误原因: 哈希索引不支持外部扩页。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03408: "access to noncontiguous page in hash index '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 哈希索引扩的页必须连续，不支持非连续扩页。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03409: "unexpected hash relation size: %u, should be %u"
+
+SQLSTATE: XX000
+
+错误原因: 哈希索引扩页失败。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03410: "cannot initialize non-empty hash index '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 不能初始化非空哈希表。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03411 - GAUSS-03420
+
+<br/>
+
+GAUSS-03411: "scan in progress on supposedly new bucket"
+
+SQLSTATE: XX000
+
+错误原因: 在新的bucket上有scan操作。
+
+解决办法: 等scan操作结束后，再尝试执行本操作。
+
+GAUSS-03412: "could not get lock on supposedly new bucket"
+
+SQLSTATE: XX000
+
+错误原因: 新bucket上的锁被占用。
+
+解决办法: 尝试再次执行。
+
+GAUSS-03413: "invalid overflow block number %u"
+
+SQLSTATE: XX000
+
+错误原因: 超过hash表的内部最大页号。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03414: "firstfreebit found no free bit"
+
+SQLSTATE: XX000
+
+错误原因: 没有找到free bit。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03415: "invalid overflow bit number %u"
+
+SQLSTATE: XX000
+
+错误原因: 超过最大bitmap页数。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03416: "out of overflow pages in hash index '%s'"
+
+SQLSTATE: 54000
+
+错误原因: hash索引支持容量达到上限。
+
+解决办法: 请重建索引。
+
+GAUSS-03417: "missing support function %d(%u,%u) for index '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 不支持该哈希函数。
+
+解决办法: 使用其他的哈希函数。
+
+GAUSS-03418: "index '%s' contains unexpected zero page at block %u"
+
+SQLSTATE: XX002
+
+错误原因: 索引检测到空页。
+
+解决办法: 请重建索引。
+
+GAUSS-03419: "index '%s' contains corrupted page at block %u"
+
+SQLSTATE: XX002
+
+错误原因: 索引检测到坏页。
+
+解决办法: 请重建索引。
+
+GAUSS-03420: "index '%s' is not a hash index"
+
+SQLSTATE: XX002
+
+错误原因: 该索引不属于哈希索引。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03421 - GAUSS-03430
+
+<br/>
+
+GAUSS-03421: "index '%s' has wrong hash version"
+
+SQLSTATE: XX002
+
+错误原因: 版本信息错误。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03423: "lost saved point in index"
+
+SQLSTATE: XX000
+
+错误原因: 索引中的页面缺失。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03424: "could not find additional pending pages for same heap tuple"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03425: "index row size %lu exceeds maximum %lu for index '%s'"
+
+SQLSTATE: 54000
+
+错误原因: 元组的大小超过一个页的大小。
+
+解决办法: 内部错误，属于预防性报错。检查是否使用了toast机制。
+
+GAUSS-03426: "failed to add item to index page in '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 页面插入元组失败。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03427: "failed to add item to index root page"
+
+SQLSTATE: XX000
+
+错误原因: 向root页面插入元组失败。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03428: "Lost path"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03429: "ginmerge: unimplemented"
+
+SQLSTATE: XX000
+
+错误原因: 不支持gin索引merge。
+
+解决办法: 属于功能不支持，请检查使用方式和场景。
+
+GAUSS-03430: "unexpected searchMode: %d"
+
+SQLSTATE: XX000
+
+错误原因: searchMode错误。
+
+解决办法: 检查所设置的searchmode。
+
+<br/>
+
+## GAUSS-03431 - GAUSS-03440
+
+<br/>
+
+GAUSS-03431: "old GIN indexes do not support whole-index scans nor searches for nulls"
+
+SQLSTATE: 0A000
+
+错误原因: 低版本的gin索引不支持，whole-index scan或null的搜索。
+
+解决办法: 在新版本上重新创建gin索引。
+
+GAUSS-03432: "GIN does not support mark/restore"
+
+SQLSTATE: XX000
+
+错误原因: Gin索引不支持记录或者恢复scan position。
+
+解决办法: 属于功能不支持，请检查使用方式。
+
+GAUSS-03433: "failed to add item to index page in %u/%u/%u"
+
+SQLSTATE: XX000
+
+错误原因: 页面插入元组失败。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03434: "failed to add item to index page"
+
+SQLSTATE: XX000
+
+错误原因: 页面插入元组失败。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03438: "ginarrayextract requires three arguments"
+
+SQLSTATE: XX000
+
+错误原因: 该函数需要3个参数。
+
+解决办法: 检查函数ginarrayextract_2args的使用方法。
+
+GAUSS-03439: "ginqueryarrayextract: unknown strategy number: %d"
+
+SQLSTATE: XX000
+
+错误原因: 使用了错误的strategy。
+
+解决办法: 检查函数ginqueryarrayextract的使用方法，检查第三个参数。
+
+<br/>
+
+## GAUSS-03441 - GAUSS-03450
+
+<br/>
+
+GAUSS-03441: "column is not in index"
+
+SQLSTATE: XX000
+
+错误原因: 索引中没有该属性列。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03442: "system catalog scans with lossy index conditions are not implemented"
+
+SQLSTATE: XX000
+
+错误原因: 内部功能不支持。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03443: "cannot do ordered scan on index '%s', because it is being reindexed"
+
+SQLSTATE: XX000
+
+错误原因: reindex的过程中不支持order scan。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03444: "invalid %s regproc"
+
+SQLSTATE: XX000
+
+错误原因: 非法的regproc。
+
+解决办法: 内部错误，检查regproc。
+
+GAUSS-03445: "multixact_redo: unknown op code %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03451 - GAUSS-03460
+
+<br/>
+
+GAUSS-03453: "Xid is invalid."
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03454: "current transaction with handle: (%d:%u) have a valid xid: %lu already"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03456: "cannot commit a transaction that deleted files but has no xid"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03457: "cannot commit transaction %lu, it was already aborted"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03458: "maximum number of committed subtransactions (%d) exceeded"
+
+SQLSTATE: 54000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03459: "cannot abort transaction %lu, it was already committed"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03461 - GAUSS-03470
+
+<br/>
+
+GAUSS-03461: "cannot PREPARE a transaction that has exported snapshots"
+
+SQLSTATE: 0A000
+
+错误原因: 两阶段事务不能作用于快照。
+
+解决办法: 请关闭两阶段事务。
+
+GAUSS-03462: "CleanupTransaction: unexpected state %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03463: "StartTransactionCommand: unexpected state %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03464: "CommitTransactionCommand: unexpected state %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03465: "%s cannot run inside a transaction block"
+
+SQLSTATE: 25001
+
+错误原因: 事务内不能执行如下SQL(eg: CREATE TABLESPACE，COMMIT PREPARED)。
+
+解决办法: 请不要在事务内执行如下SQL(eg: CREATE TABLESPACE，COMMIT PREPARED)。
+
+GAUSS-03466: "%s cannot run inside a subtransaction"
+
+SQLSTATE: 25001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03467: "%s cannot be executed from a function or multi-command string"
+
+SQLSTATE: 25001
+
+错误原因: 函数不能执行如下SQL(eg: CREATE TABLESPACE，COMMIT PREPARED)。
+
+解决办法: 请不要针对函数执行如下SQL(eg: CREATE TABLESPACE，COMMIT PREPARED)。
+
+GAUSS-03468: "cannot prevent transaction chain"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03469: "%s can only be used in transaction blocks"
+
+SQLSTATE: 25005
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03470: "BeginTransactionBlock: unexpected state %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03471 - GAUSS-03480
+
+<br/>
+
+GAUSS-03471: "EndTransactionBlock: unexpected state %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03472: "UserAbortTransactionBlock: unexpected state %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03473: "DefineSavepoint: unexpected state %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03474: "no such savepoint"
+
+SQLSTATE: 3B001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03475: "ReleaseSavepoint: unexpected state %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03476: "RollbackToSavepoint: unexpected state %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03477: "BeginInternalSubTransaction: unexpected state %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03478: "ReleaseCurrentSubTransaction: unexpected state %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03479: "RollbackAndReleaseCurrentSubTransaction: unexpected state %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03480: "invalid transaction block state: %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03481 - GAUSS-03490
+
+<br/>
+
+GAUSS-03481: "cannot have more than 2^32-1 subtransactions in a transaction"
+
+SQLSTATE: 54000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03482: "PopTransaction with no parent"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03483: "xact_redo: unknown op code %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03485: "cannot assign TransactionIds during recovery"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03487: "Falling back to local Xid. Was = %lu, now is = %lu"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03491 - GAUSS-03500
+
+<br/>
+
+GAUSS-03492: "cannot assign OIDs during recovery"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03493: "Open file %s failed. %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03494: "Close file %s failed. %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03495: "seek file %s failed. %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03496: "clog_redo: unknown op code %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03498: "recovery is in progress"
+
+SQLSTATE: 55000
+
+错误原因: 系统处于前滚阶段，不能执行WAL控制函数。
+
+解决办法: 请等待系统启动完毕后，重新执行WAL控制函数。
+
+GAUSS-03500: "WAL level not sufficient for creating a restore point"
+
+SQLSTATE: 55000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/36-GAUSS-03501-GAUSS-03600.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/36-GAUSS-03501-GAUSS-03600.md
new file mode 100644
index 0000000000000000000000000000000000000000..55ff71cd93aa855ac18b42da1f1bffdccd59d982
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/36-GAUSS-03501-GAUSS-03600.md
@@ -0,0 +1,700 @@
+---
+title: GAUSS-03501 - GAUSS-03600
+summary: GAUSS-03501 - GAUSS-03600
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-03501 - GAUSS-03600
+
+<br/>
+
+## GAUSS-03501 - GAUSS-03510
+
+<br/>
+
+GAUSS-03501: "value too long for restore point (maximum %d characters)"
+
+SQLSTATE: 22023
+
+错误原因: 恢复点的名称长度超过了63个字节。
+
+解决办法: 请缩短恢复点的名称，重新创建。
+
+GAUSS-03502: "could not parse transaction log location '%s'"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03504: "recovery is not in progress"
+
+SQLSTATE: 55000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03505: "invalid input syntax for transaction log location: '%s'"
+
+SQLSTATE: 22P02
+
+错误原因: 输入参数错误。
+
+解决办法: 请检查函数参数，重新执行。
+
+GAUSS-03507: "could not access status of transaction %lu"
+
+SQLSTATE: XX000
+
+错误原因: 获取文件状态失败。
+
+解决办法: 请检查文件路径和权限是否正确。
+
+GAUSS-03508: "unrecognized SimpleLru error 错误原因:  %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03509: "cannot make new WAL entries during recovery"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03511 - GAUSS-03520
+
+<br/>
+
+GAUSS-03513: "xlog write request %X/%X is past end of log %X/%X"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03514: "xlog flush request %X/%X is not satisfied - flushed only to %X/%X"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03515: "not enough data in file '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03516: "InstallXLogFileSegment should not have failed"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03517: "invalid XLogFileRead source %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03518: "could not open transaction log directory '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 打开文件夹pg_xlog失败。
+
+解决办法: 请检查文件夹路径和权限是否正确。
+
+GAUSS-03519: "required WAL directory '%s' does not exist"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03520: "could not create missing directory '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03521 - GAUSS-03530
+
+<br/>
+
+GAUSS-03523: "syntax error in history file: %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03524: "invalid data in history file: %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03525: "invalid data in history file '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03527: "sizeof(ControlFileData) is larger than PG_CONTROL_SIZE; fix either one"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03529: "could not write to control file: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03530: "could not fsync control file: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03531 - GAUSS-03540
+
+<br/>
+
+GAUSS-03531: "could not close control file: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03532: "could not open control file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03533: "could not read from control file: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03534: "database files are incompatible with server"
+
+SQLSTATE: XX000
+
+错误原因: 数据库文件和软件版本不匹配。
+
+解决办法: 请使用正确的软件版本重建数据库。
+
+GAUSS-03535: "incorrect checksum in control file"
+
+SQLSTATE: XX000
+
+错误原因: pg_control文件内容异常。
+
+解决办法: 请使用备份数据恢复或者重建数据库。
+
+GAUSS-03536: "could not write bootstrap transaction log file: %m"
+
+SQLSTATE: XX000
+
+错误原因: 磁盘空间不足。
+
+解决办法: 请检查磁盘空间是否充足，重启数据库。
+
+GAUSS-03537: "could not fsync bootstrap transaction log file: %m"
+
+SQLSTATE: XX000
+
+错误原因: 文件权限不正确。
+
+解决办法: 请检查文件权限是否正确，重启数据库。
+
+GAUSS-03538: "could not close bootstrap transaction log file: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03539: "could not open recovery command file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03540: "recovery_target_timeline is not a valid number: '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03541 - GAUSS-03550
+
+<br/>
+
+GAUSS-03541: "recovery_target_xid is not a valid number: '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03542: "recovery_target_name is too long (maximum %d characters)"
+
+SQLSTATE: 22023
+
+错误原因: 配置恢复目标名称太长。
+
+解决办法: 请缩短配置恢复目标名称后，重新恢复数据库。
+
+GAUSS-03543: "unrecognized recovery parameter '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 配置恢复参数不支持。
+
+解决办法: 请正确配置恢复参数后，重新恢复数据库。
+
+GAUSS-03544: "recovery command file '%s' must specify restore_command when standby mode is not enabled"
+
+SQLSTATE: XX000
+
+错误原因: 配置恢复命令为空。
+
+解决办法: 请正确配置恢复命令后，重新恢复数据库。
+
+GAUSS-03545: "recovery target timeline %u does not exist"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03546: "hot standby is not possible because %s = %d is a lower setting than on the master server (its value was %d)"
+
+SQLSTATE: 22023
+
+错误原因: 备机的参数配置比主机小。
+
+解决办法: 请修改配置，重启数据库。
+
+GAUSS-03548: "control file contains invalid data"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03549: "requested timeline %u is not a child of database system timeline %u"
+
+SQLSTATE: XX000
+
+错误原因: 备份的WAL日志文件与数据库不匹配。
+
+解决办法: 请确保WAL日志文件与数据库一致后，重启恢复数据库。
+
+GAUSS-03550: "could not find redo location referenced by checkpoint record"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03551 - GAUSS-03560
+
+<br/>
+
+GAUSS-03551: "could not locate required checkpoint record"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03552: "could not locate a valid checkpoint record"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03553: "invalid next transaction ID"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03554: "invalid redo in checkpoint record"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03555: "invalid redo record in shutdown checkpoint"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03556: "backup_label contains data inconsistent with control file"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03558: "requested recovery stop point is before consistent recovery point"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03559: "WAL ends before end of online backup"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03560: "WAL ends before consistent recovery point"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03561 - GAUSS-03570
+
+<br/>
+
+GAUSS-03562: "concurrent transaction log activity while database system is shutting down"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03563: "online backup was canceled, recovery cannot continue"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03564: "unexpected timeline ID %u (after %u) in checkpoint record"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03565: "unexpected timeline ID %u (should be %u) in checkpoint record"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03566: "unrecognized wal_sync_method: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03571 - GAUSS-03580
+
+<br/>
+
+GAUSS-03571: "WAL level not sufficient for making an online backup"
+
+SQLSTATE: 55000
+
+错误原因: 配置WAL级别不足。
+
+解决办法: 配置WAL级别为archive或hot_standby，重启数据库后执行备份操作。
+
+GAUSS-03572: "backup label too long (max %d bytes)"
+
+SQLSTATE: 22023
+
+错误原因: 备份路径名称超过限制。
+
+解决办法: 修改配置路径名称，重新执行备份操作。
+
+GAUSS-03573: "a backup is already in progress"
+
+SQLSTATE: 55000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03574: "WAL generated with full_page_writes=off was replayed since last restartpoint"
+
+SQLSTATE: 55000
+
+错误原因: 配置项full_page_writes为off。
+
+解决办法: 配置full_page_writes为on，在主机做CHECKPOINT后，再次执行备份。
+
+GAUSS-03575: "could not write file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03576: "a backup is not in progress"
+
+SQLSTATE: 55000
+
+错误原因: 没有任何正在执行的备份供停止。
+
+解决办法: SELECT pg_start_backup和SELECT pg_stop_backup是成对出现的。必须先执行了开始备份，才能执行关闭备份。请确认相关备份是否已开启。
+
+GAUSS-03577: "invalid data in file '%s'"
+
+SQLSTATE: 55000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03578: "the standby was promoted during online backup"
+
+SQLSTATE: 55000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03579: "WAL generated with full_page_writes=off was replayed during online backup"
+
+SQLSTATE: 55000
+
+错误原因: 配置项full_page_writes为off。
+
+解决办法: 请配置full_page_writes为on，在主机做CHECKPOINT后，再次执行备份。
+
+GAUSS-03580: "invalid record offset at %X/%X."
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03581 - GAUSS-03590
+
+<br/>
+
+GAUSS-03581: "not enough shared memory for pg_lsnxlogflushchk share memory"
+
+SQLSTATE: 53200
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03582: "transaction identifier '%s' is too long"
+
+SQLSTATE: 22023
+
+错误原因: 事务标识参数太长。
+
+解决办法: 请检查输入参数后，重新执行PREPARE TRANSACTION操作。
+
+GAUSS-03583: "prepared transactions are disabled"
+
+SQLSTATE: 55000
+
+错误原因: 配置项max_prepared_transactions为0。
+
+解决办法: 请配置max_prepared_transactions为非0值。
+
+GAUSS-03584: "transaction identifier '%s' is already in use"
+
+SQLSTATE: 42710
+
+错误原因: 事务标识参数正在使用。
+
+解决办法: 请检查输入参数，重新执行PREPARE TRANSACTION操作。
+
+GAUSS-03585: "maximum number of prepared transactions reached"
+
+SQLSTATE: 53200
+
+错误原因: 配置项max_prepared_transactions值较小。
+
+解决办法: 请配置max_prepared_transactions为合理值或提交回滚一些事务。
+
+GAUSS-03586: "prepared transaction with identifier '%s' is busy"
+
+SQLSTATE: 55000
+
+错误原因: 事务标识参数正在使用。
+
+解决办法: 请重新执行操作。
+
+GAUSS-03587: "permission denied to finish prepared transaction"
+
+SQLSTATE: 42501
+
+错误原因: 权限不正确。
+
+解决办法: 请由事务发起者或管理员结束已准备好的事务。
+
+GAUSS-03588: "prepared transaction belongs to another database"
+
+SQLSTATE: 0A000
+
+错误原因: 连接的数据库不正确。
+
+解决办法: 请检查和确认数据库的正确性后，重新连接。
+
+GAUSS-03589: "prepared transaction with identifier '%s' does not exist"
+
+SQLSTATE: 42704
+
+错误原因: 事务标识参数不存在。
+
+解决办法: 请检查输入参数，重新执行操作。
+
+GAUSS-03590: "failed to find %p in GlobalTransaction array"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03591 - GAUSS-03600
+
+<br/>
+
+GAUSS-03591: "failed to find GlobalTransaction for xid %lu"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03594: "could not write two-phase state file: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03596: "could not close two-phase state file: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03598: "could not recreate two-phase state file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03599: "could not fsync two-phase state file: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/37-GAUSS-03601-GAUSS-03700.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/37-GAUSS-03601-GAUSS-03700.md
new file mode 100644
index 0000000000000000000000000000000000000000..0c7897c54c37318daba5361c6f3ca2cb737227a6
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/37-GAUSS-03601-GAUSS-03700.md
@@ -0,0 +1,748 @@
+---
+title: GAUSS-03601 - GAUSS-03700
+summary: GAUSS-03601 - GAUSS-03700
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-03601 - GAUSS-03700
+
+<br/>
+
+## GAUSS-03601 - GAUSS-03610
+
+<br/>
+
+GAUSS-03603: "number of index columns (%d) exceeds limit (%d)"
+
+SQLSTATE: 54011
+
+错误原因: 索引元组的数目超过了上限32个。
+
+解决办法: 减少需要建立行存索引的列数目。
+
+GAUSS-03604: "index row requires %lu bytes, maximum size is %lu"
+
+SQLSTATE: 54000
+
+错误原因: 单条索引元组的长度超过了一个页的大小，主要是由索引列数据过长引起的。
+
+解决办法: 不可对超长的列数据建立索引。
+
+GAUSS-03605: "column '%s' cannot be applied %s compress mode"
+
+SQLSTATE: 42P16
+
+错误原因: 列不支持所提示的压缩模式。
+
+解决办法: 请正确选择压缩列、模式。
+
+GAUSS-03606: "unsupported format code: %d"
+
+SQLSTATE: 22023
+
+错误原因: 不支持的类型。
+
+解决办法: 请检查列的类型，再次执行操作。
+
+GAUSS-03607: "invalid attnum: %d"
+
+SQLSTATE: XX000
+
+错误原因: 运行过程中出现了不存在的系统列。
+
+解决办法: 若是由用户发起的系统列查询，需要检测是否支持该系统列的查询；否则为内部运行错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-03608: "number of columns (%d) exceeds limit (%d)"
+
+SQLSTATE: 54011
+
+错误原因: 列的数量达到上限。
+
+解决办法: 请减少列的数量，再次执行操作。
+
+GAUSS-03609: "Tuple does not match the descriptor"
+
+SQLSTATE: XX001
+
+错误原因: 元组的列数目与实际数据的列数目不一致。
+
+解决办法: 运行时错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-03610: "cannot extract system attribute from virtual tuple"
+
+SQLSTATE: XX000
+
+错误原因: 内部错误: 无法从虚元组中抽取出系统列来。
+
+解决办法: 运行时错误，请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03611 - GAUSS-03620
+
+<br/>
+
+GAUSS-03611: "cannot extract system attribute from minimal tuple"
+
+SQLSTATE: XX000
+
+错误原因: 内部错误: 无法从虚元组中抽取出系统列来。
+
+解决办法: 运行时错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-03613: "user-defined relation parameter types limit exceeded"
+
+SQLSTATE: 54000
+
+错误原因: 关系参数类型定义达到上限。
+
+解决办法: 请重新定义关系参数类型。
+
+GAUSS-03614: "unsupported option type"
+
+SQLSTATE: XX000
+
+错误原因: 表定义的选项中出现了不支持的数据类型，支持的有效数据类型包括布尔类、整数、浮点数和字符串。
+
+解决办法: 修正创建表时可选项对应的数据类型为有效类型。
+
+GAUSS-03615: "RESET must not include values for parameters"
+
+SQLSTATE: 42601
+
+错误原因: RESET不支持指定参数值。
+
+解决办法: 请检查RESET命令，再次执行命令重置缺省值。
+
+GAUSS-03616: "unrecognized parameter namespace '%s'"
+
+SQLSTATE: 22023
+
+错误原因: 不可识别的参数命名空间。
+
+解决办法: 请检查参数命名空间是否存在，再次执行操作。
+
+GAUSS-03617: "unrecognized parameter '%s'"
+
+SQLSTATE: 22023
+
+错误原因: 不可识别的参数。
+
+解决办法: 请检查参数是否存在，再次执行操作。
+
+GAUSS-03618: "parameter '%s' specified more than once"
+
+SQLSTATE: 22023
+
+错误原因: 参数指定多于一次。
+
+解决办法: 请检查参数使用，再次执行操作。
+
+GAUSS-03619: "invalid value for boolean option '%s': %s"
+
+SQLSTATE: XX000
+
+错误原因: BOOL类型项数据不合法。
+
+解决办法: 请检查BOOL类型项数据的合法性，再次执行操作。
+
+GAUSS-03620: "invalid value for integer option '%s': %s"
+
+SQLSTATE: XX000
+
+错误原因: INT类型项数据不合法。
+
+解决办法: 请检查INT类型项数据的合法性，再次执行操作。
+
+<br/>
+
+## GAUSS-03621 - GAUSS-03630
+
+<br/>
+
+GAUSS-03621: "value %s out of bounds for option '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 数据值不在范围内。
+
+解决办法: 请检查数据取值范围，再次执行操作。
+
+GAUSS-03622: "invalid value for floating point option '%s': %s"
+
+SQLSTATE: XX000
+
+错误原因: FLOAT类型项数据不合法。
+
+解决办法: 请检查FLOAT类型项数据，再次执行操作。
+
+GAUSS-03623: "unsupported reloption type %d"
+
+SQLSTATE: XX000
+
+错误原因: 表定义的选项中出现了不支持的数据类型，支持的有效数据类型包括布尔类、整数、浮点数和字符串。
+
+解决办法: 修正创建表时可选项对应的数据类型为有效类型。
+
+GAUSS-03624: "unrecognized reloption type %c"
+
+SQLSTATE: XX000
+
+错误原因: 表定义的选项中出现了不支持的数据类型，支持的有效数据类型包括布尔类、整数、浮点数和字符串。
+
+解决办法: 修正创建表时可选项对应的数据类型为有效类型。
+
+GAUSS-03625: "reloption '%s' not found in parse table"
+
+SQLSTATE: XX000
+
+错误原因: 创建表时指定了不存在的表选项。
+
+解决办法: 询表支持的有效选项并修正。
+
+GAUSS-03626: "Invalid string for 'ORIENTATION' option"
+
+SQLSTATE: 22023
+
+错误原因: ORIENTATION项的参数不合法。
+
+解决办法: 请检查ORIENTATION项参数的合法性，再次执行操作。
+
+GAUSS-03627: "Invalid string for 'COMPRESSION' option"
+
+SQLSTATE: 22023
+
+错误原因: COMPRESSION项的参数不合法。
+
+解决办法: 请检查COMPRESSION项参数的合法性，再次执行操作。
+
+GAUSS-03628: "unrecognized StrategyNumber: %d"
+
+SQLSTATE: XX000
+
+错误原因: 使用的strategy错误。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03629: "missing oprcode for operator %u"
+
+SQLSTATE: XX000
+
+错误原因: 非法的oprcode。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03630: "btree index keys must be ordered by attribute"
+
+SQLSTATE: XX000
+
+错误原因: 索引的属性列小于1。
+
+解决办法: 检查B-tree索引是否创建正确。
+
+<br/>
+
+## GAUSS-03631 - GAUSS-03640
+
+<br/>
+
+GAUSS-03631: "multiple active vacuums for index '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 一个索引上同时有多个VACUUM操作。
+
+解决办法: 避免同时对一个b-tree索引做多个VACUUM操作。
+
+GAUSS-03632: "out of btvacinfo slots"
+
+SQLSTATE: XX000
+
+错误原因: VACUUM操作数量超过最大值。
+
+解决办法: 等其他VACUUM操作执行完成后再支持该操作。
+
+GAUSS-03633: "index '%s' is not a btree"
+
+SQLSTATE: XX002
+
+错误原因: 该节点不是B-tree索引的root。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03635: "no live root page found in index '%s'"
+
+SQLSTATE: XX000
+
+错误原因: B-tree索引没有root节点。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03636: "root page %u of index '%s' has level %u, expected %u"
+
+SQLSTATE: XX000
+
+错误原因: 索引的root页有错误的level信息。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03637: "failed to re-find parent key in index '%s' for deletion target page %u"
+
+SQLSTATE: XX000
+
+错误原因: 删除的过程中找不到父节点。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03638: "not enough stack items"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03639: "left link changed unexpectedly in block %u of index '%s'"
+
+SQLSTATE: XX000
+
+错误原因: left link的页编号被修改。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03640: "right sibling's left-link doesn't match: block %u links to %u instead of expected %u in index '%s'"
+
+SQLSTATE: XX000
+
+错误原因: B-tree索引结构错误，右兄弟的左连接不匹配。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03641 - GAUSS-03650
+
+<br/>
+
+GAUSS-03641: "failed to delete rightmost child %u of block %u in index '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 删除节点失败。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03642: "right sibling %u of block %u is not next child %u of block %u in index '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03643: "fell off the end of index '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03644: "missing support function %d(%u,%u) for attribute %d of index '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03646: "could not find left sibling of block %u in index '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03647: "btree level %u not found in index '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03648: "invalid scan direction: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03649: "duplicate key value violates unique constraint '%s'"
+
+SQLSTATE: 23505
+
+错误原因: 插入唯一索引主键冲突。
+
+解决办法: 请检查数据冲突或更改索引为非唯一索引，再次执行操作。
+
+GAUSS-03650: "failed to re-find tuple within index '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03651 - GAUSS-03660
+
+<br/>
+
+GAUSS-03651: "failed to add new item to block %u in index '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 插入记录到特定索引页失败。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03652: "failed to add hikey to the right sibling while splitting block %u of index '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03653: "failed to add hikey to the left sibling while splitting block %u of index '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03655: "failed to add new item to the right sibling while splitting block %u of index '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03656: "failed to add old item to the left sibling while splitting block %u of index '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03657: "failed to add old item to the right sibling while splitting block %u of index '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03658: "could not find a feasible split point for index '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03659: "failed to re-find parent key in index '%s' for split pages %u/%u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03660: "failed to add leftkey to new root page while splitting block %u of index '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03661 - GAUSS-03670
+
+<br/>
+
+GAUSS-03661: "failed to add rightkey to new root page while splitting block %u of index '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03662: "failed to add item to the index page"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03663: "index compare error, both are NULL"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03664: "_bt_restore_page: cannot add item to page"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03665: "btree_insert_redo: failed to add item"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03666: "failed to add new item to left page after split"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03667: "failed to add high key to left page after split"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03670: "btree_xlog_cleanup: left block unfound"
+
+SQLSTATE: XX000
+
+错误原因: left block查找不到。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03671 - GAUSS-03680
+
+<br/>
+
+GAUSS-03671: "btree_xlog_cleanup: right block unfound"
+
+SQLSTATE: XX000
+
+错误原因: right block查找不到。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03672: "btree_xlog_cleanup: _bt_pagedel failed"
+
+SQLSTATE: XX000
+
+错误原因: b tree页面删除失败。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03673: "unlogged GiST indexes are not supported"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03674: "concurrent GiST page split was incomplete"
+
+SQLSTATE: XX000
+
+错误原因: split不完整。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03675: "index '%s' contains an inner tuple marked as invalid"
+
+SQLSTATE: XX000
+
+错误原因:  内部索引包含无效元组。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03676: "failed to re-find parent of a page in index '%s', block %u"
+
+SQLSTATE: XX000
+
+错误原因: 查找父节点页失败。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03677: "numberOfAttributes %d > %d"
+
+SQLSTATE: XX000
+
+错误原因: 索引表的属性列超过最大值。
+
+解决办法: 减少创建索引的属性列数。
+
+GAUSS-03678: "invalid GiST tuple found on leaf page"
+
+SQLSTATE: XX000
+
+错误原因: GIST页错误。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03679: "GiST only supports forward scan direction"
+
+SQLSTATE: XX000
+
+错误原因: 只支持forward方向。
+
+解决办法: 内部错误。检查扫描方向，第二个参数。
+
+<br/>
+
+## GAUSS-03681 - GAUSS-03690
+
+<br/>
+
+GAUSS-03683: "invalid value for 'buffering' option"
+
+SQLSTATE: 22023
+
+错误原因: BufferingOption的选项非: on、off和auto。
+
+解决办法: 内部错误。检查BufferingOption选项。
+
+GAUSS-03685: "failed to re-find parent for block %u"
+
+SQLSTATE: XX000
+
+错误原因: 查找父节点页失败。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03687: "gistmerge: unimplemented"
+
+SQLSTATE: XX000
+
+错误原因: gist不支持的merge。
+
+解决办法: 属于功能不支持，请检查使用方式和场景。
+
+GAUSS-03688: "failed to add item to GiST index page, size %d bytes"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03690: "GiST does not support mark/restore"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03691 - GAUSS-03700
+
+<br/>
+
+GAUSS-03691: "inconsistent point values"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03692: "unknown strategy number: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03693: "unrecognized strategy number: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03694: "index '%s' is not an SP-GiST index"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03695: "desired SPGiST tuple size is too big"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03696: "SP-GiST inner tuple size %lu exceeds maximum %lu"
+
+SQLSTATE: 54000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03697: "SPGiST inner tuple header field is too small"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03698: "some but not all node labels are null in SPGiST inner tuple"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03699: "failed to add item of size %u to SPGiST index page"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/38-GAUSS-03701-GAUSS-03800.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/38-GAUSS-03701-GAUSS-03800.md
new file mode 100644
index 0000000000000000000000000000000000000000..f5582e908594d6da918828320bc583b4f12e1c0f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/38-GAUSS-03701-GAUSS-03800.md
@@ -0,0 +1,700 @@
+---
+title: GAUSS-03701 - GAUSS-03800
+summary: GAUSS-03701 - GAUSS-03800
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-03701 - GAUSS-03800
+
+<br/>
+
+## GAUSS-03701 - GAUSS-03710
+
+<br/>
+
+GAUSS-03701: "spg_redo: unknown op code %u"
+
+SQLSTATE: XX000
+
+错误原因: redo操作类型错误。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03702: "inconsistent tuple chain links in page %u of index '%s'"
+
+SQLSTATE: XX000
+
+错误原因: spgist内部tuple chain list出错。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03703: "unexpected SPGiST tuple state: %d"
+
+SQLSTATE: XX000
+
+系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03704: "inconsistent counts of deletable tuples"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03705: "redirection leads to root page of index '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03706: "allTheSame should not occur for k-d trees"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03707: "spgmerge: unimplemented"
+
+SQLSTATE: XX000
+
+错误原因: SPGIN索引不支持merge操作。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03708: "SPGiST does not support mark/restore"
+
+SQLSTATE: XX000
+
+系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03709: "inconsistent inner_consistent results for allTheSame inner tuple"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03710: "SP-GiST only supports forward scan direction"
+
+SQLSTATE: XX000
+
+系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03711 - GAUSS-03720
+
+<br/>
+
+GAUSS-03711: "getQuadrant: impossible case"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03712: "failed to find requested node %d in SPGiST inner tuple"
+
+SQLSTATE: XX000
+
+系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03715: "failed to divide leaf tuple groups across pages"
+
+SQLSTATE: XX000
+
+错误原因: 叶子节点跨页存储。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03716: "cannot enlarge root tuple any more"
+
+SQLSTATE: XX000
+
+错误原因: 不能扩大root tuple。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03718: "SPGiST inner-tuple split must not produce longer prefix"
+
+SQLSTATE: XX000
+
+系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03719: "SPGiST index page %u has wrong nulls flag"
+
+SQLSTATE: XX000
+
+系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03720: "cannot add a node to an allTheSame inner tuple"
+
+SQLSTATE: XX000
+
+错误原因: 不能将一个node添加到完全相同的内部元组上。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03721 - GAUSS-03730
+
+<br/>
+
+GAUSS-03721: "cannot add a node to an inner tuple without node labels"
+
+SQLSTATE: XX000
+
+错误原因: 给内部元组增加node时，node标签不能为空。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-03722: "unrecognized SPGiST choose result: %d"
+
+SQLSTATE: XX000
+
+系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03723: "row is too big: size %lu, maximum size %lu"
+
+SQLSTATE: 54000
+
+错误原因: 单个元组的长度超过了规格，也无法通过TOAST技术进行存储。
+
+解决办法: 可以将列数目较多的大表拆分为多个小表再进行数据存储，也可以将一些数据类型修改为字符串类型进行存储。64位xid系统改变了页面规格，如果旧表发生报错，也需要将列数目较多的大表拆分为多个小表再进行数据存储或者将一些数据类型修改为字符串类型进行存储。
+
+GAUSS-03724: "failed to add tuple"
+
+SQLSTATE: XX000
+
+错误原因: 内部错误: 插入元组执行失败。
+
+解决办法: 尝试重新执行可解决。
+
+GAUSS-03725: "wrong buffer passed to visibilitymap_clear"
+
+SQLSTATE: XX000
+
+错误原因: 内部错误: 可见性表操作前校验页和页号的有效性失败。
+
+解决办法: 尝试重新执行可解决。
+
+GAUSS-03728: "found toasted toast chunk for toast value %u in %s"
+
+SQLSTATE: XX014
+
+错误原因: 内部错误: TOAST数据存储内部异常。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03729: "unexpected chunk number %d (expected %d) for toast value %u in %s"
+
+SQLSTATE: XX014
+
+错误原因: 内部错误: TOAST数据存储的数目与期望不匹配。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03730: "unexpected chunk size %d (expected %d) in chunk %d of %d for toast value %u in %s"
+
+SQLSTATE: XX014
+
+错误原因: 内部错误: TOAST数据存储内部异常。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03731 - GAUSS-03740
+
+<br/>
+
+GAUSS-03731: "unexpected chunk size %d (expected %d) in final chunk %d for toast value %u in %s"
+
+SQLSTATE: XX014
+
+错误原因: 内部错误: TOAST数据存储内部异常。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03732: "unexpected chunk number %d (out of range %d..%d) for toast value %u in %s"
+
+SQLSTATE: XX014
+
+错误原因: 内部错误: TOAST数据存储内部异常。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03733: "missing chunk number %d for toast value %u in %s"
+
+SQLSTATE: XX014
+
+错误原因: 内部错误: TOAST数据存储内部异常。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03734: "unexpected chunk size %d (expected %d) in chunk %d of %d for toast value %u in %s when fetching slice"
+
+SQLSTATE: XX014
+
+错误原因: toast表chunk size与预期不符。
+
+解决办法: 检查toast表。
+
+GAUSS-03735: "unexpected chunk size %d (expected %d) in final chunk %d for toast value %u in %s when fetching slice"
+
+SQLSTATE: XX014
+
+错误原因:  toast表chunk size与预期不符。
+
+解决办法: 检查toast表。
+
+GAUSS-03736: "could not open relation with OID %u"
+
+SQLSTATE: XX000
+
+错误原因: Relation OID非法。
+
+解决办法: 查询pg_class检查表名与OID。
+
+GAUSS-03737: "block number %u is out of range for relation '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 块号超过表的最大块。
+
+解决办法: 检查表的文件长度。
+
+GAUSS-03738: "attempted to delete invisible tuple"
+
+SQLSTATE: XX000
+
+错误原因:  尝试删除不可见的tuple。
+
+解决办法: 检查操作的表是否有并发操作。
+
+GAUSS-03739: "tuple already updated by self"
+
+SQLSTATE: XX000
+
+错误原因: tuple被当前事务更新过。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03740: "tuple concurrently updated"
+
+SQLSTATE: XX000
+
+错误原因: tuple被并发更新或者删除。
+
+解决办法: 检查是否有并发操作同一张表。
+
+<br/>
+
+## GAUSS-03741 - GAUSS-03750
+
+<br/>
+
+GAUSS-03741: "attempted to update invisible tuple"
+
+SQLSTATE: XX000
+
+错误原因: 尝试更新的tuple不可见。
+
+解决办法: 检查操作的表是否有并发操作。
+
+GAUSS-03742: "attempted to lock invisible tuple"
+
+SQLSTATE: XX000
+
+错误原因: 尝试加锁的tuple不可见。
+
+解决办法: 检查操作的表是否有并发操作。
+
+GAUSS-03743: "could not obtain lock on row in relation '%s'"
+
+SQLSTATE: 55P03
+
+错误原因: 产生加锁失败。
+
+解决办法: 检查操作的表是否有并发操作。
+
+GAUSS-03744: "heap_inplace_update: invalid lp"
+
+SQLSTATE: XX000
+
+错误原因: 更新操作的tuple指针非法。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03745: "heap_inplace_update: wrong tuple length"
+
+SQLSTATE: XX000
+
+错误原因: 更新操作的tuple长度非法。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03746: "heap_delete_redo: invalid lp"
+
+SQLSTATE: XX000
+
+错误原因: redo delete时tuple指针非法。
+
+解决办法: 检查Xlog是否正确。
+
+GAUSS-03747: "heap_insert_redo: invalid max offset number"
+
+SQLSTATE: XX000
+
+错误原因: redo insert时页面偏移量非法。
+
+解决办法: 检查Xlog是否正确。
+
+GAUSS-03748: "heap_insert_redo: failed to add tuple"
+
+SQLSTATE: XX000
+
+错误原因: redo insert 添加tuple失败。
+
+解决办法: 检查Xlog是否正确。
+
+GAUSS-03749: "heap_multi_insert_redo: invalid max offset number"
+
+SQLSTATE: XX000
+
+错误原因: redo multi insert时页面偏移量非法。
+
+解决办法: 检查Xlog是否正确。
+
+GAUSS-03750: "heap_multi_insert_redo: failed to add tuple"
+
+SQLSTATE: XX000
+
+错误原因: redo multi insert 添加tuple失败。
+
+解决办法: 检查Xlog是否正确。
+
+<br/>
+
+## GAUSS-03751 - GAUSS-03760
+
+<br/>
+
+GAUSS-03751: "heap_update_redo: invalid lp"
+
+SQLSTATE: XX000
+
+错误原因: redo update tuple指针非法。
+
+解决办法: 检查Xlog是否正确。
+
+GAUSS-03752: "heap_update_redo: invalid max offset number"
+
+SQLSTATE: XX000
+
+错误原因: redo update tuple页面偏移量非法。
+
+解决办法: 检查Xlog是否正确。
+
+GAUSS-03753: "heap_update_redo: failed to add tuple"
+
+SQLSTATE: XX000
+
+错误原因: redo update添加tuple失败。
+
+解决办法: 检查Xlog是否正确。
+
+GAUSS-03754: "heap_lock_redo: invalid lp"
+
+SQLSTATE: XX000
+
+错误原因: redo lock tuple指针非法。
+
+解决办法: 检查Xlog是否正确。
+
+GAUSS-03755: "heap_inplace_redo: invalid lp"
+
+SQLSTATE: XX000
+
+错误原因: redo inplace tuple指针非法。
+
+解决办法: 检查Xlog是否正确。
+
+GAUSS-03756: "heap_inplace_redo: wrong tuple length"
+
+SQLSTATE: XX000
+
+错误原因: redo inplace tuple长度非法。
+
+解决办法: 检查Xlog是否正确。
+
+GAUSS-03759: "relation '%s' is not table or index"
+
+SQLSTATE: XX000
+
+错误原因: 操作的relation不是表或索引。
+
+解决办法: 检查SQL操作的对象是否是表或索引。
+
+<br/>
+
+## GAUSS-03761 - GAUSS-03770
+
+<br/>
+
+GAUSS-03761: "openning partition %u, but relation %s %u is neither table nor index"
+
+SQLSTATE: XX000
+
+错误原因: 操作的分区不是表或索引。
+
+解决办法: 检查SQL操作的对象是否是表或索引。
+
+GAUSS-03762: "closing partition %u, but relation %u is neither table nor index"
+
+SQLSTATE: 2200X
+
+错误原因: 关闭的分区不是表或索引。
+
+解决办法: 检查SQL操作的对象是否是表或索引。
+
+GAUSS-03763: "failed to add tuple to page"
+
+SQLSTATE: XX000
+
+错误原因: 页面添加tuple失败。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03764: "page %u of relation '%s' should be empty but is not"
+
+SQLSTATE: XX000
+
+错误原因: 页面应该为空 单实际不为空。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03765: "tuple is too big: size %lu"
+
+SQLSTATE: XX000
+
+错误原因: tuple长度大于页面剩余空间。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03767: "This query is not supported by optimizer in CStore"
+
+SQLSTATE: XX000
+
+错误原因: 列存查询在CN上执行。
+
+解决办法: 检查执行计划是否在CN上查询了列存表。
+
+<br/>
+
+## GAUSS-03771 - GAUSS-03780
+
+<br/>
+
+GAUSS-03771: "could not write cache file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 列存分区表插入，写入缓存文件错误。
+
+解决办法: 根据错误信息中写文件失败信息处理。
+
+GAUSS-03772: "could not read cache file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 列存分区表插入，读取缓存文件错误。
+
+解决办法: 根据错误信息中读文件失败信息处理。
+
+GAUSS-03774: "Column store don't support"
+
+SQLSTATE: XX000
+
+错误原因: 列存表不支持查询的系统列。
+
+解决办法: 去掉不支持的系统列。
+
+GAUSS-03775: "unsupported datatype branch"
+
+SQLSTATE: XX000
+
+错误原因: 列存表不支持查询的数据类型。
+
+解决办法: 检查数据类型。
+
+GAUSS-03777: "Non-deterministic UPDATE"
+
+SQLSTATE: 21000
+
+错误原因: 非一致性更新。
+
+解决办法: 检查更新条件，是否一行数据被多次更新。
+
+GAUSS-03778: "These rows have been deleted or updated"
+
+SQLSTATE: 21000
+
+错误原因: 数据被多次删除/更新。
+
+解决办法: 检查删除/更新条件，是否一行数据被多次删除/更新。
+
+<br/>
+
+## GAUSS-03781 - GAUSS-03790
+
+<br/>
+
+GAUSS-03781: "CStore: unrecognized heap_update status: %u"
+
+SQLSTATE: XX000
+
+错误原因: CUDesc表Tuple更新状态不能识别。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03785: "WITH query name '%s' appears in both a rule action and the query being rewritten"
+
+SQLSTATE: 0A000
+
+错误原因: WITH语句的名称在规则action和重写语句中同时出现。
+
+解决办法: 请检查规则action和重写语句，避免相同名称的WITH语句。
+
+GAUSS-03786: "cannot have RETURNING lists in multiple rules"
+
+SQLSTATE: 0A000
+
+错误原因: 多条规则含有RETURNING列表。
+
+解决办法: 修正规则的语法，消除不当的RETURNING列表。
+
+GAUSS-03787: "bogus resno %d in targetlist"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03788: "multiple assignments to same column '%s'"
+
+SQLSTATE: 42601
+
+错误原因: 语法错误，对同一列多次赋值 （除非所有赋值都是FieldStore或ArrayRef赋值操作）。
+
+解决办法: 修正UPDATE语句的语法，避免对同一列进行多次赋值。
+
+GAUSS-03789: "cannot happen"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03790: "expected just one rule action"
+
+SQLSTATE: XX000
+
+错误原因: 规则行为多于一个。
+
+解决办法: 此错误发生在外键约束上，请检查对应主外键约束。
+
+<br/>
+
+## GAUSS-03791 - GAUSS-03800
+
+<br/>
+
+GAUSS-03792: "cannot handle per-attribute ON SELECT rule"
+
+SQLSTATE: XX000
+
+错误原因: 规则行为必须是表级行为。
+
+解决办法: 此错误发生在外键约束上，请检查对应主外键约束。
+
+GAUSS-03793: "unrecognized commandType: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03794: "infinite recursion detected in rules for relation '%s'"
+
+SQLSTATE: 42P17
+
+错误原因: 在rules中出现无穷嵌套。
+
+解决办法: 检查rule用法。
+
+GAUSS-03795: "DO INSTEAD NOTHING rules are not supported for data-modifying statements in WITH"
+
+SQLSTATE: 0A000
+
+错误原因: data-modifying子句不支持DO INSTEAD NOTHING rules。
+
+解决办法: 检查rule用法。
+
+GAUSS-03796: "conditional DO INSTEAD rules are not supported for data-modifying statements in WITH"
+
+SQLSTATE: 0A000
+
+错误原因: data-modifying子句不支持conditional DO INSTEAD NO rules。
+
+解决办法: 检查rule用法。
+
+GAUSS-03797: "DO ALSO rules are not supported for data-modifying statements in WITH"
+
+SQLSTATE: 0A000
+
+错误原因: data-modifying子句不支持DO ALSO rules。
+
+解决办法: 检查rule用法。
+
+GAUSS-03799: "cannot perform INSERT RETURNING on relation '%s'"
+
+SQLSTATE: 0A000
+
+错误原因: INSTEAD rule中没有带returning，而原语句带returning，不能对表执行insert returning，出错。
+
+解决办法: 需要使用带有returning子句的无条件的ON INSERT DO INSTEAD rule。
+
+GAUSS-03800: "cannot perform UPDATE RETURNING on relation '%s'"
+
+SQLSTATE: 0A000
+
+错误原因: INSTEAD rule中没有带returning，而原语句带returning，不能对表执行update returning，出错。
+
+解决办法: 需要使用带有returning子句的无条件的ON UPDATE DO INSTEAD rule。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/39-GAUSS-03801-GAUSS-03900.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/39-GAUSS-03801-GAUSS-03900.md
new file mode 100644
index 0000000000000000000000000000000000000000..f658b1b79621fd767b602537a3a11fb0788163f3
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/39-GAUSS-03801-GAUSS-03900.md
@@ -0,0 +1,644 @@
+---
+title: GAUSS-03801 - GAUSS-03900
+summary: GAUSS-03801 - GAUSS-03900
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-03801 - GAUSS-03900
+
+<br/>
+
+## GAUSS-03801 - GAUSS-03810
+
+<br/>
+
+GAUSS-03801: "cannot perform DELETE RETURNING on relation '%s'"
+
+SQLSTATE: 0A000
+
+错误原因: INSTEAD rule中没有带returning，而原语句带returning，不能对表执行delete returning。
+
+解决办法: 需要使用带有returning子句的无条件的ON DELETE DO INSTEAD rule。
+
+GAUSS-03802: "WITH cannot be used in a query that is rewritten by rules into multiple queries"
+
+SQLSTATE: 0A000
+
+错误原因: 多query中使用了WITH。
+
+解决办法: 检查rule用法。
+
+GAUSS-03803: "Unexpected commandType or intoClause is not set properly"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03804: "cannot push down CurrentOfExpr"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03805: "expected to find SELECT subquery"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03806: "could not find rule placeholders"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03807: "conditional utility statements are not implemented"
+
+SQLSTATE: 0A000
+
+错误原因: 使用了conditional utility子句。
+
+解决办法: 未实现该功能，检查保证不传入该类型子句。
+
+GAUSS-03808: "replace_rte_variables inserted a SubLink, but has noplace to record it"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03809: "WHERE CURRENT OF on a view is not implemented"
+
+SQLSTATE: 0A000
+
+错误原因: 在视图上使用了WHERE CURRENT OF子句。
+
+解决办法: 未实现该功能，检查保证不传入该类型子句。
+
+GAUSS-03810: "unexpected varattno %d in expression to be mapped"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03811 - GAUSS-03820
+
+<br/>
+
+GAUSS-03811: "rule '%s' for relation '%s' already exists"
+
+SQLSTATE: 42710
+
+错误原因: 试图插入某表已经存在的rule。
+
+解决办法: 检查表的rule，若已经存在，则不再插入。
+
+GAUSS-03812: "rule actions on OLD are not implemented"
+
+SQLSTATE: 0A000
+
+错误原因: 对于OLD值的规则行为未实现。
+
+解决办法: 使用view或trigger进行规避。
+
+GAUSS-03813: "rule actions on NEW are not implemented"
+
+SQLSTATE: 0A000
+
+错误原因: 对于NEW值的规则行为未实现。
+
+解决办法: 使用trigger进行规避。
+
+GAUSS-03814: "INSTEAD NOTHING rules on SELECT are not implemented"
+
+SQLSTATE: 0A000
+
+错误原因: 试图使用INSTEAD NOTHING rule ON SELECT，不支持。
+
+解决办法: 检查rule用法。
+
+GAUSS-03815: "multiple actions for rules on SELECT are not implemented"
+
+SQLSTATE: 0A000
+
+错误原因: 规则行为多于一个。
+
+解决办法: 请检查规则行为是否多于一个，能否进行简化改写。
+
+GAUSS-03816: "rules on SELECT must have action INSTEAD SELECT"
+
+SQLSTATE: 0A000
+
+错误原因: 对应的规则行为必须是INSTEAD SELECT。
+
+解决办法: 请检查定义的规则行为是否正确。
+
+GAUSS-03817: "rules on SELECT must not contain data-modifying statements in WITH"
+
+SQLSTATE: 0A000
+
+错误原因: 对应的规则行为在WITH语句中不能包含数据改动的操作。
+
+解决办法: 请检查定义的规则行为是否正确。
+
+GAUSS-03818: "event qualifications are not implemented for rules on SELECT"
+
+SQLSTATE: 0A000
+
+错误原因: 规则行为的执行不能受条件约束。
+
+解决办法: 请检查定义的规则行为是否正确。
+
+GAUSS-03819: "'%s' is already a view"
+
+SQLSTATE: 55000
+
+错误原因: 对于view，仅能有一个ON SELECT规则行为。
+
+解决办法: 请检查定义的规则行为是否正确。
+
+GAUSS-03820: "view rule for '%s' must be named '%s'"
+
+SQLSTATE: 42P17
+
+错误原因: view规则行为必须定义为_RETURN。
+
+解决办法: 请检查定义的规则行为是否正确。
+
+<br/>
+
+## GAUSS-03821 - GAUSS-03830
+
+<br/>
+
+GAUSS-03821: "could not convert table '%s' to a view because it is a partitioned table"
+
+SQLSTATE: 55000
+
+错误原因: 试图把分区表转换成视图。
+
+解决办法: 若要把表变成视图要求表为非分区表。
+
+GAUSS-03822: "could not convert table '%s' to a view because it is not empty"
+
+SQLSTATE: 55000
+
+错误原因: 试图把非空表转换成视图。
+
+解决办法: 若要把表变成视图要求表数据为空。
+
+GAUSS-03823: "could not convert table '%s' to a view because it has triggers"
+
+SQLSTATE: 55000
+
+错误原因: 试图把有触发器的表转换成视图。
+
+解决办法: 若要把表变成视图要求表没有触发器。
+
+GAUSS-03824: "could not convert table '%s' to a view because it has indexes"
+
+SQLSTATE: 55000
+
+错误原因: 试图把有索引的表转换成视图。
+
+解决办法: 若要把表变成视图要求表没有索引。
+
+GAUSS-03825: "could not convert table '%s' to a view because it has child tables"
+
+SQLSTATE: 55000
+
+错误原因: 试图把有子表的表转换成视图。
+
+解决办法: 若要把表变成视图要求表没有子表。
+
+GAUSS-03826: "cannot have multiple RETURNING lists in a rule"
+
+SQLSTATE: 0A000
+
+错误原因: 在一个rule中写了多个returning lists。
+
+解决办法: 检查returning lists个数。
+
+GAUSS-03827: "RETURNING lists are not supported in conditional rules"
+
+SQLSTATE: 0A000
+
+错误原因: 在conditional rules里头使用了returning lists。
+
+解决办法: 不支持，考虑去掉returning lists。
+
+GAUSS-03828: "RETURNING lists are not supported in non-INSTEAD rules"
+
+SQLSTATE: 0A000
+
+错误原因: 在non-INSTEAD rules使用了returning lists。
+
+解决办法: 不支持，考虑去掉returning lists。
+
+GAUSS-03829: "SELECT rule's target list has too many entries"
+
+SQLSTATE: 42P17
+
+错误原因: 在SELECT rules目标列表有太多输入，输入的比要求的列数多。
+
+解决办法: 检查输入的列数，去掉多余的列。
+
+GAUSS-03830: "cannot convert relation containing dropped columns to view"
+
+SQLSTATE: 0A000
+
+错误原因: 试图转换带有删除列的表为视图。
+
+解决办法: 检查要转换成视图的表结构。
+
+<br/>
+
+## GAUSS-03831 - GAUSS-03840
+
+<br/>
+
+GAUSS-03831: "SELECT rule's target entry %d has different column name from '%s'"
+
+SQLSTATE: 42P17
+
+错误原因: SELECT rule中列名不同。
+
+解决办法: 检查SELECT rule目标输入中的列名。
+
+GAUSS-03832: "SELECT rule's target entry %d has different type from column '%s'"
+
+SQLSTATE: 42P17
+
+错误原因: SELECT rule中列类型不同。
+
+解决办法: 检查SELECT rule目标输入中的列类型。
+
+GAUSS-03833: "SELECT rule's target entry %d has different size from column '%s'"
+
+SQLSTATE: 42P17
+
+错误原因: SELECT rule中列大小不同。
+
+解决办法: 检查SELECT rule目标输入中的列大小。
+
+GAUSS-03834: "SELECT rule's target list has too few entries"
+
+SQLSTATE: 42P17
+
+错误原因: SELECT rule中输入列个数太少。
+
+解决办法: 检查SELECT rule中输入列的数目。
+
+GAUSS-03835: "rule '%s' for relation '%s' does not exist"
+
+SQLSTATE: 42704
+
+错误原因: 试图disable或enable rule，但是对应的表没有所要处理的rule。
+
+解决办法: 检查表的rule。
+
+GAUSS-03836: "rule '%s' does not exist"
+
+SQLSTATE: 42704
+
+错误原因: 试图获取对应表的某个rule，但是不存在。
+
+解决办法: 检查表的rule。
+
+GAUSS-03837: "there are multiple rules named '%s'"
+
+SQLSTATE: 42710
+
+错误原因: 试图获取对应表的某个rule，但是出现多个同名的rule。
+
+解决办法: 检查表的rule。
+
+GAUSS-03838: "Column store don't support this system column"
+
+SQLSTATE: XX000
+
+错误原因: 涉及列存不支持的系统列。
+
+解决办法: 检查涉及的系统列。
+
+<br/>
+
+## GAUSS-03841 - GAUSS-03850
+
+<br/>
+
+GAUSS-03841: "vector scan for VecMarkPos is not yet implemented "
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误: 未实现针对列存扫描节点的MarkPos功能。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-03842: "VecResult for VecMarkPos is not yet implemented "
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误: 未实现针对列存result节点的MarkPos功能。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-03844: "vector scan for VecRestrPos is not yet implemented "
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误: 未实现针对列存扫描节点的RestrPos功能。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-03845: "VecResult for VecRestrPos is not yet implemented "
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误: 未实现针对列存result节点的RestrPos功能。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-03848: "Not support pushing predicate with none-const external param"
+
+SQLSTATE: 0A000
+
+错误原因: 不支持下推非常数的外部参数。
+
+解决办法: 检查参数。
+
+GAUSS-03849: "could not find tuple for operator %u"
+
+SQLSTATE: XX000
+
+错误原因: 依据ID编号无法从系统表pg_operator中获取对应的信息
+
+解决办法: 请查询pg_operator系统表进行确认。
+
+<br/>
+
+## GAUSS-03851 - GAUSS-03860
+
+<br/>
+
+GAUSS-03851: "UnSupported vector aggregation function %u"
+
+SQLSTATE: XX000
+
+错误原因: 生成了错误的执行计划。
+
+解决办法: 保留计划，请联系技术支持工程师提供技术支持。
+
+GAUSS-03853: "unsupported aggregation type"
+
+SQLSTATE: XX000
+
+错误原因: 生成的计划有问题。
+
+解决办法: 保留计划，请联系技术支持工程师提供技术支持。
+
+GAUSS-03854: "VecRemoteQuery ReScan is not yet implemented"
+
+SQLSTATE: 0A000
+
+错误原因: 不支持VecRemoteQuery二次扫描。
+
+解决办法: 检查扫描语句。
+
+GAUSS-03857: "Unsupported window function %s in vector engine"
+
+SQLSTATE: XX000
+
+错误原因: 不支持的用法。
+
+解决办法: 修改SQL Statement。
+
+GAUSS-03860: "Un-support CHECK constraint"
+
+SQLSTATE: XX000
+
+错误原因: 列存暂不支持CHECK约束。
+
+解决办法: 检查语法，去掉check约束。
+
+<br/>
+
+## GAUSS-03861 - GAUSS-03870
+
+<br/>
+
+GAUSS-03862: "unsupport join type %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03864: "unrecognized running state: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03865: "ExecReScanVecModifyTable is not implemented"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03866: "could not write into hash-join temporary file: %m"
+
+SQLSTATE: XX000
+
+错误原因: 写hash-join临时文件出错。
+
+解决办法: 检查文件权限、用户权限等。
+
+GAUSS-03867: "could not write to hashAgg temporary file: %m"
+
+SQLSTATE: XX000
+
+错误原因: 写hashAgg临时文件出错。
+
+解决办法: 检查文件权限、用户权限等。
+
+GAUSS-03868: "could not read from hashAgg temporary file: %m"
+
+SQLSTATE: XX000
+
+错误原因: 读取hashAgg临时文件出错。
+
+解决办法: 检查文件权限、用户权限等。
+
+GAUSS-03869: "UnSupported vector function %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误: 当前函数未向量化。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-03870: "Unsupported array reference expression in vector engine"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误: 未实现Array reference表达式的向量化。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03871 - GAUSS-03880
+
+<br/>
+
+GAUSS-03873: "Unsupported field expression in vector engine"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误: 未实现FieldSelect表达式函数的向量化
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-03874: "Unsupported field store expression in vector engine"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误: 未实现Field Store表达式函数的向量化
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-03875: "Unsupported convert row type expression in vector engine"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误: 未实现ConvertRowType表达式函数的向量化。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-03876: "Unsupported array expression in vector engine"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误: 未实现数组表达式函数的向量化。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-03877: "Unsupported xml expression in vector engine"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误: 未实现XML表达式函数的向量化。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-03878: "Unsupported coerce to domain expression in vector engine"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误: 未实现CoerceToDomain表达式函数的向量化。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-03879: "Unsupported coerce to domain value expression in vector engine"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误: 未实现CoerceToDomainValue表达式函数的向量化。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-03880: "Unsupported current of expression in vector engine"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误: 未实现CurrentOf表达式函数的向量化。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03881 - GAUSS-03890
+
+<br/>
+
+GAUSS-03882: "Unsupported array coerce expression in vector engine"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误: 未实现ArrayCoerce表达式函数的向量化。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-03888: "redundant options"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03891 - GAUSS-03900
+
+<br/>
+
+GAUSS-03891: "Failed to initialize Cgroup. Please check if workload manager is enabled and Cgroups have been created!"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03893: "invalid control group: %s"
+
+SQLSTATE: XX000
+
+错误原因: 无效的控制组名称。
+
+解决办法: 检查控制组名称。
+
+GAUSS-03897: "Resource Pool '%s': object not defined"
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03899: "read workload_gpname failed."
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03900: "Workload Group '%s': object not defined"
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/4-GAUSS-00301-GAUSS-00400.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/4-GAUSS-00301-GAUSS-00400.md
new file mode 100644
index 0000000000000000000000000000000000000000..c435331163d83ebeb22ee86552a5fa0383ac3ab0
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/4-GAUSS-00301-GAUSS-00400.md
@@ -0,0 +1,804 @@
+---
+title: GAUSS-00301 - GAUSS-00400
+summary: GAUSS-00301 - GAUSS-00400
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-00301 - GAUSS-00400
+
+<br/>
+
+## GAUSS-00301 - GAUSS-00310
+
+<br/>
+
+### GAUSS-00301: "EXECUTE DIRECT cannot execute this utility query"
+
+SQLSTATE: 0A000
+
+错误原因: EXECUTE DIRECT ON ( nodename [, … ] ) query语法中在DN上执行了DDL语句。
+
+解决办法: 在EXECUTE DIRECT ON ( nodename [, … ] ) query语法中不能执行DDL语句，目前只支持SELECT语句。
+
+### GAUSS-00302: "EXECUTE DIRECT cannot execute locally this utility query"
+
+SQLSTATE: 0A000
+
+错误原因: 特性不支持: EXECUTE DIRECT ON ( nodename [, … ] ) query语法中在DN上执行了Set变量语句。
+
+解决办法: 在EXECUTE DIRECT ON ( nodename [, … ] ) query语法中不能执行Set变量语句，目前只支持SELECT语句。
+
+### GAUSS-00303: "SELECT FOR UPDATE/SHARE is not allowed with DISTINCT clause"
+
+SQLSTATE: 0A000
+
+错误原因: SELECT FOR UPDATE/SHARE不支持DISTINCT子句。
+
+解决办法: 修改语句。
+
+### GAUSS-00304: "SELECT FOR UPDATE/SHARE is not allowed with GROUP BY clause"
+
+SQLSTATE: 0A000
+
+错误原因: SELECT … FOR UPDATE/SHARE不支持GROUP BY子句。
+
+解决办法: 修改SELECT … FOR UPDATE/SHARE语句。
+
+### GAUSS-00305: "SELECT FOR UPDATE/SHARE is not allowed with HAVING clause"
+
+SQLSTATE: 0A000
+
+错误原因: SELECT … FOR UPDATE/SHARE不支持HAVING子句。
+
+解决办法: 修改SELECT … FOR UPDATE/SHARE语句。
+
+### GAUSS-00306: "SELECT FOR UPDATE/SHARE is not allowed with aggregate functions"
+
+SQLSTATE: 0A000
+
+错误原因: SELECT … FOR UPDATE/SHARE不支持聚合函数。
+
+解决办法: 修改SELECT … FOR UPDATE/SHARE语句。
+
+### GAUSS-00307: "SELECT FOR UPDATE/SHARE is not allowed with window functions"
+
+SQLSTATE: 0A000
+
+错误原因: SELECT … FOR UPDATE/SHARE不支持窗口函数。
+
+解决办法: 修改SELECT … FOR UPDATE/SHARE语句。
+
+### GAUSS-00308: "SELECT FOR UPDATE/SHARE is not allowed with set-returning functions in the target list"
+
+SQLSTATE: 0A000
+
+错误原因: SELECT … FOR UPDATE/SHARE语法的目标列中不支持定义了返回值的函数。
+
+解决办法: 修改SELECT … FOR UPDATE/SHARE语句。
+
+### GAUSS-00309: "SELECT FOR UPDATE/SHARE must specify unqualified relation names"
+
+SQLSTATE: 42601
+
+错误原因: SELECT … FOR UPDATE/SHARE…OF table_name语法中指定的表名存在数据库/模式的引用。
+
+解决办法: 修改SELECT … FOR UPDATE/SHARE…OF table_name语法中指定的表名不能包含database.table或schema.table等引用，只能是一个确定的表名。
+
+### GAUSS-00310: "SELECT FOR UPDATE/SHARE cannot be used with column table '%s'"
+
+SQLSTATE: 0A000
+
+错误原因: SELECT … FOR UPDATE/SHARE…OF table_name语法中指定的表为列存表。
+
+解决办法: SELECT … FOR UPDATE/SHARE…OF table_name语法中指定的表名不能使用列存表，请修改语法结构。
+
+<br/>
+
+## GAUSS-00311 - GAUSS-00320
+
+<br/>
+
+### GAUSS-00311: "SELECT FOR UPDATE/SHARE cannot be applied to a join"
+
+SQLSTATE: 0A000
+
+错误原因: SELECT … FOR UPDATE/SHARE…OF table_name语法中的范围表为JOIN类型的连接表。
+
+解决办法: SELECT … FOR UPDATE/SHARE…OF table_name语法中指定的表名不能为JOIN类型的连接表，请修改语法结构。
+
+### GAUSS-00312: "SELECT FOR UPDATE/SHARE cannot be applied to a function"
+
+SQLSTATE: 0A000
+
+错误原因: SELECT … FOR UPDATE/SHARE…OF table_name语法中的范围表为函数。
+
+解决办法: SELECT … FOR UPDATE/SHARE…OF table_name语法中指定的表名不能为函数，请修改语法结构。
+
+### GAUSS-00313: "SELECT FOR UPDATE/SHARE cannot be applied to a WITH query"
+
+SQLSTATE: 0A000
+
+错误原因: SELECT … FOR UPDATE/SHARE…OF table_name语法中的范围表为WITH子句标识的列表。
+
+解决办法: SELECT … FOR UPDATE/SHARE…OF table_name语法中指定的表名不能为WITH子句标识的列表，请修改语法结构。
+
+### GAUSS-00314: "unrecognized RTE type: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00315: "relation '%s' in FOR UPDATE/SHARE clause not found in FROM clause"
+
+SQLSTATE: 42P01
+
+错误原因: SELECT … FROM table1_name FOR UPDATE/SHARE…OF table_name语法中的table_name在FROM子句中不存在。
+
+解决办法: SELECT … FROM table1_name FOR UPDATE/SHARE…OF table_name语法中的table_name必须在FROM子句中存在。
+
+### GAUSS-00316: "unsupport 'like clause including partition' for partitioned table"
+
+SQLSTATE: 42P16
+
+错误原因: CREATE TABLE … LIKE source_table语法中LIKE子句表名指定为分区表的语法错误。
+
+解决办法: CREATE TABLE … LIKE source_table语法中LIKE子句源表名如果指定为分区表，需要使用partition by子句，请修改语法结构。
+
+### GAUSS-00317: "unsupport 'like clause including reloptions' together with 'with'"
+
+SQLSTATE: 42P16
+
+错误原因: CREATE TABLE … LIKE source_table语法中LIKE子句中包含有INCLUDING RELOPTIONS选项，与源表的WITH子句一起使用，存在语法冲突。
+
+解决办法: "CREATE TABLE … LIKE source_table语法中LIKE子句中包含有INCLUDING RELOPTIONS选项，该选项不能与源表的WITH子句一起使用。由于INCLUDING RELOPTIONS选项和源表中的即源表的WITH子句都表示源表的存储参数将拷贝至新表，因此只需要使用其中一个选项即可。"
+
+### GAUSS-00318: "array of serial is not implemented"
+
+SQLSTATE: 0A000
+
+错误原因: 特性不支持: CREATE TABLE或ALTER TABLE语法中的字段类型为序列数组产生错误。
+
+解决办法: CREATE TABLE或ALTER TABLE语法中的字段类型不能为序列数组。
+
+### GAUSS-00319: "conflicting NULL/NOT NULL declarations for column '%s' of table '%s'"
+
+SQLSTATE: 42601
+
+错误原因: CREATE TABLE或ALTER TABLE语法中定义的非空列名与约束子句中定义的列名为空产生矛盾。
+
+解决办法: CREATE TABLE或ALTER TABLE语法中约束子句中定义的列名为空，需要和字段名列表中定义的列名保持一致。
+
+### GAUSS-00320: "multiple default values specified for column '%s' of table '%s'"
+
+SQLSTATE: 42601
+
+错误原因: CREATE TABLE或ALTER TABLE语法的约束子句中定义的列名指定了多个值。
+
+解决办法: CREATE TABLE或ALTER TABLE语法的约束子句中定义的列名只能指定一个值。
+
+<br/>
+
+## GAUSS-00321 - GAUSS-00330
+
+<br/>
+
+### GAUSS-00321: "column exclusion constraints are not supported"
+
+SQLSTATE: XX000
+
+错误原因: 不支持的语法。
+
+解决办法: 修改SQL Statement。
+
+### GAUSS-00322: "unrecognized constraint type: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00323: "invalid context for constraint type %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00324: "'%s' is not a table, view, composite type, or foreign table"
+
+SQLSTATE: 42809
+
+错误原因: CREATE TABLE … LIKE source_table语法的LIKE子句中的source_table不是关系表、视图、复合类型或外表。
+
+解决办法: CREATE TABLE … LIKE source_table语法的LIKE子句中的source_table必须为关系表、视图、复合类型或外表中的一种。
+
+### GAUSS-00325: "could not specify 'INCLUDING PARTITION' for non-partitioned-table relation:'%s'"
+
+SQLSTATE: 42809
+
+错误原因: CREATE TABLE … LIKE source_table语法对分区表错误指定了INCLUDING PARTITION。
+
+解决办法: CREATE TABLE … LIKE source_table语法不能对分区表指定了INCLUDING PARTITION。
+
+### GAUSS-00326: "could not specify 2 or more 'INCLUDING PARTITION' clauses, only one is allowed"
+
+SQLSTATE: 42809
+
+错误原因: CREATE TABLE … （LIKE source_table INCLUDING PARTITION）语法中指定了多于1个LIKE…INCLUDING PARTITION子句。
+
+解决办法: CREATE TABLE … （LIKE source_table INCLUDING PARTITION）语法中只能指定1个LIKE…INCLUDING PARTITION子句。
+
+### GAUSS-00327: "could not specify 2 or more 'INCLUDING RELOPTIONS' clauses, only one is allowed"
+
+SQLSTATE: 42809
+
+错误原因: CREATE TABLE … LIKE source_table语法LIKE子句中指定了多于1个INCLUDINGRELOPTIONS。
+
+解决办法: CREATE TABLE … LIKE source_table语法LIKE子句中只能指定1个INCLUDINGRELOPTIONS。
+
+### GAUSS-00328: "could not specify 2 or more 'INCLUDING DISTRIBUTION' clauses, only one is allowed"
+
+SQLSTATE: 42809
+
+错误原因: CREATE TABLE … LIKE source_table语法LIKE子句中指定了多于1个INCLUDINGDISTRIBUTION。
+
+解决办法: CREATE TABLE … LIKE source_table语法LIKE子句中只能指定1个INCLUDINGDISTRIBUTION。
+
+### GAUSS-00329: "Postgres-XC does not support VIEW in LIKE clauses"
+
+SQLSTATE: 0A000
+
+错误原因: 特性不支持: CREATE TABLE … LIKE语法的LIKE子句中不支持视图。
+
+解决办法: 修改CREATE TABLE … LIKE语法的LIKE子句删除视图。
+
+### GAUSS-00330: "cannot convert whole-row table reference"
+
+SQLSTATE: 0A000
+
+错误原因: 不支持的语法。
+
+解决办法: 修改SQL Statement。
+
+<br/>
+
+## GAUSS-00331 - GAUSS-00340
+
+<br/>
+
+### GAUSS-00331: "cache lookup failed on source like relation %u for reloptions"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00332: "null partition key value for relation '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 不支持null partition key value 。
+
+解决办法: 检查partition key value。
+
+### GAUSS-00333: "partition key column's number of relation '%s' is not a 1-D smallint array"
+
+SQLSTATE: XX000
+
+错误原因: CREATE TABLE … LIKE语法的LIKE子句中指定INCLUDING PARTITION的分区键值列数错误或列类型错误。
+
+解决办法: CREATE TABLE … LIKE语法的LIKE子句中指定INCLUDING PARTITION的分区键值列数为1且列值类型为整形。
+
+### GAUSS-00334: "partition key column's number of %s not in the range of all its columns"
+
+SQLSTATE: XX000
+
+错误原因: CREATE TABLE … LIKE语法的LIKE子句中指定INCLUDING PARTITION的分区键值列数超过了当前表的列数范围。
+
+解决办法: CREATE TABLE … LIKE语法的LIKE子句中指定INCLUDING PARTITION的分区键值列数范围必须在1到表最大列数的范围内。
+
+### GAUSS-00335: "' including partition ' for list partitioned relation: '%s' not implemented yet"
+
+SQLSTATE: XX000
+
+错误原因: CREATE TABLE … LIKE语法的LIKE子句中指定INCLUDING PARTITION的分区类型错误。
+
+解决办法: CREATE TABLE … LIKE语法的LIKE子句中指定INCLUDING PARTITION的分区类型只能为定义为范围分区或哈希分区，列表分区暂不支持。
+
+### GAUSS-00336: "cache lookup failed for constraint %u"
+
+SQLSTATE: 22P06
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00337: "null conexclop for constraint %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00338: "cache lookup failed for operator %u"
+
+SQLSTATE: 22P06
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00339: "too few entries in indexprs list"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00340: "cache lookup failed for collation %u"
+
+SQLSTATE: 22P06
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-00341 - GAUSS-00350
+
+<br/>
+
+### GAUSS-00341: "cache lookup failed for opclass %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00342: "Partitioned table does not support EXCLUDE index"
+
+SQLSTATE: 0A000
+
+错误原因: 特性不支持: CREATE TABLE … CONSTRAINT语法中对于创建分区表不支持指定为排斥约束。
+
+解决办法: 修改CREATE TABLE … CONSTRAINT语法，对于创建分区表指定为其他约束。
+
+### GAUSS-00343: "Invalid PRIMARY KEY/UNIQUE constraint for partitioned table"
+
+SQLSTATE: 0A000
+
+错误原因: CREATE TABLE … CONSTRAINT语法中对于创建分区表创建为主键约束或唯一（UNIQUE）约束的字段名没有包含分区表的分区键字段名。
+
+解决办法: CREATE TABLE … CONSTRAINT语法中对于创建分区表创建为主键约束或唯一（UNIQUE）约束的字段名必须包含分区表的分区键字段名。
+
+### GAUSS-00344: "multiple primary keys for table '%s' are not allowed"
+
+SQLSTATE: 42P16
+
+错误原因: CREATE TABLE … LIKE source_table语法LIKE子句中指定了多个INCLUDING INDEXES的主键。
+
+解决办法: CREATE TABLE … LIKE source_table语法LIKE子句中只能指定了1个INCLUDING INDEXES的主键。
+
+### GAUSS-00345: "cannot use an existing index in CREATE TABLE"
+
+SQLSTATE: 0A000
+
+错误原因: 错误的使用CREATE TABLE语法给索引字段指定约束。
+
+解决办法: "ALTER TABLE … ADD table_constraint语法给数据表增加一个新约束"。
+
+### GAUSS-00346: "index '%s' does not exist"
+
+SQLSTATE: 42704
+
+错误原因: CREATE/ALTER TABLE语法中用于指定约束的属性名在关系表中不存在。
+
+解决办法: 请检查CREATE/ALTER TABLE语法中用于指定约束的属性名是否在关系表中存在。
+
+### GAUSS-00347: "index '%s' is already associated with a constraint"
+
+SQLSTATE: 55000
+
+错误原因: 不支持的用法。
+
+解决办法: 创建其它的索引。
+
+### GAUSS-00348: "index '%s' does not belong to table '%s'"
+
+SQLSTATE: 55000
+
+错误原因: CREATE/ALTER TABLE table_name语法中指定约束的属性名在table_name中不存在。
+
+解决办法: 请检查CREATE/ALTER TABLE table_name语法中指定约束的属性名是否在table_name中存在。
+
+### GAUSS-00349: "index '%s' is not valid"
+
+SQLSTATE: 55000
+
+错误原因: CREATE/ALTER TABLE语法中用于指定约束的属性名为无效值。
+
+解决办法: 请检查CREATE/ALTER TABLE语法中用于指定约束的属性名是否为关系表或模式中存在。
+
+### GAUSS-00350: "'%s' is not a unique index"
+
+SQLSTATE: 42809
+
+错误原因: CREATE TABLE … CONSTRAINT语法中对于创建分区表创建为主键约束或唯一（UNIQUE）约束的字段名不是唯一索引。
+
+解决办法: CREATE TABLE … CONSTRAINT语法中对于创建分区表创建为主键约束或唯一（UNIQUE）约束的字段名必须保证为唯一索引。
+
+<br/>
+
+## GAUSS-00351 - GAUSS-00360
+
+<br/>
+
+### GAUSS-00351: "index '%s' contains expressions"
+
+SQLSTATE: 42809
+
+错误原因: CREATE TABLE … CONSTRAINT语法中对于创建分区表创建为主键约束或唯一（UNIQUE）约束的约束属性错误的包含表达式。
+
+解决办法: CREATE TABLE … CONSTRAINT语法中对于创建分区表创建为主键约束或唯一（UNIQUE）约束的约束属性不允许包含表达式。
+
+### GAUSS-00352: "'%s' is a partial index"
+
+SQLSTATE: 42809
+
+错误原因: 不支持的用法。
+
+解决办法: 用合法的索引代替。
+
+### GAUSS-00353: "'%s' is a deferrable index"
+
+SQLSTATE: 42809
+
+错误原因: 不支持的用法。
+
+解决办法: 用合法的索引代替。
+
+### GAUSS-00354: "index '%s' is not a btree"
+
+SQLSTATE: 42809
+
+错误原因: btree函数中指定的索引不是B-tree索引。
+
+解决办法: 检查指定的索引类型，使用对应的索引函数。
+
+### GAUSS-00355: "index '%s' does not have default sorting behavior"
+
+SQLSTATE: 42809
+
+错误原因: 不支持的用法。
+
+解决办法: 用合法的索引代替。
+
+### GAUSS-00356: "inherited relation '%s' is not a table"
+
+SQLSTATE: 42809
+
+错误原因: CREATE TABLE … INHERITS parent_table语法中INHERITS子句声明的表为非法的数据表。
+
+解决办法: 请检查CREATE TABLE … INHERITS parent_table语法中INHERITS子句声明的表是否为一个已存在的表。
+
+### GAUSS-00357: "column '%s' named in key does not exist"
+
+SQLSTATE: 42703
+
+错误原因: CREATE TABLE语法中使用约束子句或INHERITS子句声明的表的字段名在表中不存在。
+
+解决办法: 请检查CREATE TABLE语法中使用约束子句或INHERITS子句声明的表的字段名是否在表中存在，如果不存在需要更换继承的字段名或重新创建表。
+
+### GAUSS-00358: "column '%s' appears twice in primary key constraint"
+
+SQLSTATE: 42701
+
+错误原因: CREATE TABLE … CONSTRAINT语法的PRIMARY KEY子句中指定的主键约束包含的约束属性中有2个相同的主键名。
+
+解决办法: 请检查CREATE TABLE … CONSTRAINT语法的PRIMARY KEY子句中指定的主键约束包含的约束属性中是否存在2个相同的主键名，并修改或删除其中一个主键名。
+
+### GAUSS-00359: "column '%s' appears twice in unique constraint"
+
+SQLSTATE: 42701
+
+错误原因: CREATE TABLE … CONSTRAINT语法的UNIQE子句中指定的主键约束包含的约束属性中有2个相同的主键名。
+
+解决办法: 请检查CREATE TABLE … CONSTRAINT语法的UNIQE子句中指定的主键约束包含的约束属性中是否存在2个相同的主键名，并修改或删除其中一个主键名。
+
+<br/>
+
+## GAUSS-00361 - GAUSS-00370
+
+<br/>
+
+### GAUSS-00361: "access method '%s' does not support column store"
+
+SQLSTATE: 0A000
+
+错误原因:  对列存表通过CREATE INDEX…USING method语法中指定的访问方法错误。
+
+解决办法: 对列存表创建索引时指定的访问方法只能为psort类型，请修改索引的访问方法。
+
+### GAUSS-00362: "index expression cannot return a set"
+
+SQLSTATE: 42804
+
+错误原因: CREATE INDEX语法中指定的一个或多个字段的索引表达式错误地返回了一个集合。
+
+解决办法: CREATE INDEX语法中指定的一个或多个字段的索引表达式不支持返回集合，请检查创建的索引表达式定义是否正确，并修改返回类型。
+
+### GAUSS-00363: "index expressions and predicates can refer only to the table being indexed"
+
+SQLSTATE: 42P10
+
+错误原因: "CREATE INDEX语法中指定创建一个基于该表的一个或多个字段的表达式索引归属于不同的表"。
+
+解决办法: "CREATE INDEX语法中指定创建一个基于该表的一个或多个字段的表达式索引只能归属于同一张表"。
+
+### GAUSS-00364: "unrecognized event type: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00365: "rule WHERE condition cannot contain references to other relations"
+
+SQLSTATE: 42P17
+
+错误原因: CREATE RULE语法中的WHERE条件表达式引用了NEW和OLD之外的表。
+
+解决办法: CREATE RULE语法中的WHERE条件表达式除了引用NEW和OLD之外不能引用其他任何表，请检查并修改语法。
+
+### GAUSS-00368: "Rule may not use NOTIFY, it is not yet supported"
+
+SQLSTATE: 42P17
+
+错误原因: 特性不支持: CREATE RULE语法中指定规则动作的命令错误的使用了NOTIFY。
+
+解决办法: CREATE RULE语法中指定规则动作的命令只能包含SELECT、INSERT、UPDATE或DELETE，当前版本暂时还不支持NOTIFY，请修改语法。
+
+### GAUSS-00369: "rules with WHERE conditions can only have SELECT, INSERT, UPDATE, or DELETE actions"
+
+SQLSTATE: 42P17
+
+错误原因: 特性不支持: CREATE RULE语法中指定规则动作的命令错误的使用了CREATE、DESTROY、COPY和VACUUM等功能型数据定义语句。
+
+解决办法: CREATE RULE语法中指定规则动作的命令目前只支持SELECT、INSERT、UPDATE或DELETE等动作。
+
+### GAUSS-00370: "conditional UNION/INTERSECT/EXCEPT statements are not implemented"
+
+SQLSTATE: 0A000
+
+错误原因: 对于用户建立的规则，生成的查询树中，对UNION/INTERSECT/EXCEPT进行了过滤操作，该执行模式目前不支持。
+
+解决办法: 尝试进行rule的改写，规避不支持的行为，或请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-00371 - GAUSS-00380
+
+<br/>
+
+### GAUSS-00371: "ON SELECT rule cannot use OLD"
+
+SQLSTATE: 42P17
+
+错误原因: CREATE RULE name AS ON SELECT语法中WHERE条件表达式中引用的表名不能为OLD表。
+
+解决办法: 请检查CREATE RULE name AS ON SELECT语法中WHERE条件表达式引用的表名是否包含OLD表，并修改为非OLD表。
+
+### GAUSS-00372: "ON SELECT rule cannot use NEW"
+
+SQLSTATE: 42P17
+
+错误原因: CREATE RULE name AS ON SELECT语法中WHERE条件表达式中引用的表名不能为NEW表。
+
+解决办法: 请检查CREATE RULE name AS ON SELECT语法中WHERE条件表达式引用的表名是否包含NEW表，并修改为非OLD表。
+
+### GAUSS-00373: "ON INSERT rule cannot use OLD"
+
+SQLSTATE: 42P17
+
+错误原因: CREATE RULE name AS ON INSERT语法中WHERE条件表达式中引用的表名不能为OLD表。
+
+解决办法: 请检查CREATE RULE name AS ON INSERT语法中WHERE条件表达式引用的表名是否包含OLD表，并修改为非OLD表。
+
+### GAUSS-00374: "ON DELETE rule cannot use NEW"
+
+SQLSTATE: 42P17
+
+错误原因: CREATE RULE name AS ON DELETE语法中WHERE条件表达式中引用的表名不能为NEW表。
+
+解决办法: 请检查CREATE RULE name AS ON DELETE语法中WHERE条件表达式引用的表名是否包含NEW表，并修改为非OLD表。
+
+### GAUSS-00377: "missing definition of adding partition"
+
+SQLSTATE: XX000
+
+错误原因: ALTER TABLE ADD PARTITION语法为指定的分区表添加一个分区时，分区中定义的分区列、索引、限制条件或父表存在无效值。
+
+解决办法: 请检查ALTER TABLE ADD PARTITION语法为指定的分区表添加的一个分区中定义的分区列、索引、限制条件或父表是否存在无效值，并修改为有效值。
+
+### GAUSS-00378: "misplaced DEFERRABLE clause"
+
+SQLSTATE: 42601
+
+错误原因: CREATE TABLE或ALTER TABLE语法中column_constraint子句指定的列的限制条件为可推迟类型错误。
+
+解决办法: CREATE TABLE或ALTER TABLE语法中column_constraint子句指定的列的限制类型只能为主键、UNIQUE、排他或外表时才能设置为可推迟类型。
+
+### GAUSS-00379: "multiple DEFERRABLE/NOT DEFERRABLE clauses not allowed"
+
+SQLSTATE: 42601
+
+错误原因: CREATE TABLE或ALTER TABLE语法中column_constraint子句列表中同时存在可推迟类型和不可推迟类型。
+
+解决办法: CREATE TABLE或ALTER TABLE语法中column_constraint子句列表中只能存在可推迟类型或非可推迟类型两者中的一种，请修改column_constraint子句列表。
+
+### GAUSS-00380: "misplaced NOT DEFERRABLE clause"
+
+SQLSTATE: 42601
+
+错误原因: CREATE TABLE或ALTER TABLE语法中column_constraint子句指定的列的限制条件为不可推迟类型错误。
+
+解决办法: CREATE TABLE或ALTER TABLE语法中column_constraint子句指定的列的限制类型只能为主键、UNIQUE、排他或外表时才能设置为不可推迟类型。
+
+<br/>
+
+## GAUSS-00381 - GAUSS-00390
+
+<br/>
+
+### GAUSS-00381: "misplaced INITIALLY DEFERRED clause"
+
+SQLSTATE: 42601
+
+错误原因: 语法错误。
+
+解决办法: 修改SQL Statement。
+
+### GAUSS-00382: "multiple INITIALLY IMMEDIATE/DEFERRED clauses not allowed"
+
+SQLSTATE: 42601
+
+错误原因: 语法错误。
+
+解决办法: 修改SQL Statement。
+
+### GAUSS-00383: "misplaced INITIALLY IMMEDIATE clause"
+
+SQLSTATE: 42601
+
+错误原因: 语法错误。
+
+解决办法: 修改SQL Statement。
+
+### GAUSS-00384: "CREATE specifies a schema (%s) different from the one being created (%s)"
+
+SQLSTATE: 42P15
+
+错误原因: "在CREATE SCHEMA schema_name schema_element…语法中，schema_element指示的CREATE TABLE、CREATE VIEW、CREATE INDEX、CREATE PARTITION或GRANT子句中的包含的模式名与schema_name不匹配"。
+
+解决办法: "在CREATE SCHEMA schema_name schema_element…语法中，需要确认并修改schema_element指示的CREATE TABLE、CREATE VIEW、CREATE INDEX、CREATE PARTITION或GRANT子句中的包含的模式名与schema_name一致。"
+
+### GAUSS-00385: "unsupport inherits clause for partitioned table"
+
+SQLSTATE: 42601
+
+错误原因: 语法错误。
+
+解决办法: 修改SQL Statement。
+
+### GAUSS-00386: "inherited relation '%s' is a foreign table"
+
+SQLSTATE: 42809
+
+错误原因: 不支持的用法。
+
+解决办法: 修改SQL Statement。
+
+### GAUSS-00387: "inherited relation '%s' is a partitioned table"
+
+SQLSTATE: XX000
+
+错误原因: "CREATE TABLE table_name (…) INHERITS ( parent_table [, … ] )语法中parent_table为分区表"。
+
+解决办法: "请检查CREATE TABLE table_name (…) INHERITS ( parent_table [, … ] )语法中parent_table是否为分区表，语法要求继承的parent_table不能为分区表"。
+
+### GAUSS-00389: "Typed table can't not be partitioned"
+
+SQLSTATE: 42601
+
+错误原因: CREATE … TABLE OF type_name …语法特性该版本暂不支持。
+
+解决办法: 请将CREATE … TABLE OF type_name …语法更换为其他方式。
+
+### GAUSS-00390: "unsupported feature with temporary/unlogged table for partitioned table"
+
+SQLSTATE:42601
+
+错误原因: CREATE TEMPORARY/UNLOGGED TABLE table_name …语法中分区表不支持TEMPORARY或UNLOGGED属性。
+
+解决办法: CREATE TEMPORARY/UNLOGGED TABLE table_name …语法中指定为TEMPORARY或UNLOGGED属性的表不支持分区表，请修改表名为非分区表。
+
+<br/>
+
+## GAUSS-00391 - GAUSS-00400
+
+<br/>
+
+### GAUSS-00392: "too many partition keys for partitioned table"
+
+SQLSTATE: 42P16
+
+错误原因: 创建表为范围分区表时，指定的分区列数目超过了规定的最大数目4。
+
+解决办法: 创建表为范围分区表时，请保证分区列最大数目不超过4个。
+
+### GAUSS-00393: "too many partitions for partitioned table"
+
+SQLSTATE: 42P16
+
+错误原因: "PARTITION BY RANGE(partition_key)(range_partition_definition_list)…语法创建范围分区表时，指定的分区值列表数目超过了规定的最大数目32767。"
+
+解决办法: 请确保指定的分区值列表最大数目不超过32767。
+
+### GAUSS-00394: "Range partitioned table with INTERVAL was forbidden"
+
+SQLSTATE: 42P16
+
+错误原因: PARTITION BY RANGE(partition_key) INTERVAL，即间隔分区在当前版本中暂不支持。
+
+解决办法: PARTITION BY RANGE(partition_key) INTERVAL子句特性在当前版本中暂不支持。
+
+### GAUSS-00395: "Range partitioned table with INTERVAL clause has more than one column"
+
+SQLSTATE: 42P16
+
+错误原因: 不支持的用法。
+
+解决办法: 修改SQL Statement。
+
+### GAUSS-00397: "duplicate partition name: '%s'"
+
+SQLSTATE: 42710
+
+错误原因: PARTITION BY RANGE(partition_key)(range_partition_definition_list)…语法创建范围分区表时，指定的分区值列表中存在重复的分区名。
+
+解决办法: 请检查指定的分区值列表中是否存在重复的分区名，并修改重复的分区名。
+
+### GAUSS-00398: "column '%s' appears twice in partial cluster key constraint"
+
+SQLSTATE: 42701
+
+错误原因: CREATE TABLE … CONSTRAINT PARTIAL CLUSTER KEY （columnList）语法中columnList列表中存在重复的列名。
+
+解决办法: 请检查并修改CREATE TABLE … CONSTRAINT PARTIAL CLUSTER KEY （columnList）语法中columnList列表中存在的重复列名。
+
+### GAUSS-00399: "column name '%s' conflicts with a system column name"
+
+SQLSTATE: 42701
+
+错误原因: CREATE TABLE语法中指定的列名与系统表列名保留列名重名。
+
+解决办法: CREATE TABLE语法中指定的列名不能与系统表列名保留列名重名，请根据提示修改列名。
+
+### GAUSS-00400: "access method 'psort' does not support WHERE clause"
+
+SQLSTATE: 0A000
+
+错误原因: 在CREATE INDEX或ALTER TABLE语法中INDEX子句中指定的访问方式如果为psort时，INDEX子句中不支持WHERE子句。
+
+解决办法: 在CREATE INDEX或ALTER TABLE语法中INDEX子句中指定的访问方式如果为psort时，请检查INDEX子句中是否存在WHERE子句，并修改语法。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/40-GAUSS-03901-GAUSS-04000.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/40-GAUSS-03901-GAUSS-04000.md
new file mode 100644
index 0000000000000000000000000000000000000000..f68e2abbd81e04739ec2109b4251d0661de3fcdd
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/40-GAUSS-03901-GAUSS-04000.md
@@ -0,0 +1,644 @@
+---
+title: GAUSS-03901 - GAUSS-04000
+summary: GAUSS-03901 - GAUSS-04000
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-03901 - GAUSS-04000
+
+<br/>
+
+## GAUSS-03901 - GAUSS-03910
+
+<br/>
+
+GAUSS-03903: "Resource Pool '%s': object already defined"
+
+SQLSTATE: 42710
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03906: "Can not alter default_pool"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03907: "cache lookup failed for pg_resource_pool %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03909: "Can not drop default_pool"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03910: "cannot drop resource pool '%s' because other objects depend on it"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03911 - GAUSS-03920
+
+<br/>
+
+GAUSS-03912: "Workload Group '%s': object already defined"
+
+SQLSTATE: 42710
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03915: "Can not alter default_group"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03916: "cache lookup failed for pg_workload_group %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03917: "must be system admin to remove workload groups "
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03918: "Can not drop default_group"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03919: "cannot drop workload group '%s' because other objects depend on it"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03920: "must be system admin to create application workload group mapping"
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03921 - GAUSS-03930
+
+<br/>
+
+GAUSS-03921: "Application Workload Group Mapping '%s': object can not create"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03922: "Application Workload Group Mapping '%s': object already defined"
+
+SQLSTATE: 42710
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03924: "must be system admin to change application workload group mapping"
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03925: "Application Workload Group Mapping '%s': object not defined"
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03926: "Can not alter default_application"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03927: "cache lookup failed for pg_app_workloadgroup_mapping %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03928: "must be system admin to remove application workload group mapping."
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03929: "Can not drop default_application"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03931 - GAUSS-03940
+
+<br/>
+
+GAUSS-03935: "user mapping not found for '%s'"
+
+SQLSTATE: 42704
+
+错误原因: 初始化Foreign data wrapper出现问题。
+
+解决办法: 请检查使用中的gds、hdfs外表以及roach、obs设置是否正确。若不正确，请联系技术支持工程师提供技术支持。
+
+GAUSS-03936: "foreign-data wrapper handler function %u did not return an FdwRoutine struct"
+
+SQLSTATE: XX000
+
+错误原因: 初始化Foreign data wrapper出现问题。
+
+解决办法: 请检查使用中的gds、hdfs外表以及roach、obs设置是否正确。若不正确，请联系技术支持工程师提供技术支持。
+
+GAUSS-03937: "foreign-data wrapper '%s' has no handler"
+
+SQLSTATE: 55000
+
+错误原因: 初始化Foreign data wrapper出现问题。
+
+解决办法: 请检查使用中的gds、hdfs外表以及roach、obs设置是否正确。若否，请联系技术支持工程师提供技术支持。
+
+GAUSS-03940: "unexpected delimiter"
+
+SQLSTATE: F0000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03941 - GAUSS-03950
+
+<br/>
+
+GAUSS-03941: "unexpected end of line or lexeme"
+
+SQLSTATE: F0000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03943: "unexpected end of line"
+
+SQLSTATE: F0000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03944: "thesaurus sample word '%s' isn't recognized by subdictionary (rule %d)"
+
+SQLSTATE: F0000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03945: "thesaurus sample word '%s' is a stop word (rule %d)"
+
+SQLSTATE: F0000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03946: "thesaurus substitute word '%s' is a stop word (rule %d)"
+
+SQLSTATE: F0000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03947: "thesaurus substitute word '%s' isn't recognized by subdictionary (rule %d)"
+
+SQLSTATE: F0000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03948: "thesaurus substitute phrase is empty (rule %d)"
+
+SQLSTATE: F0000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03949: "multiple DictFile parameters"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03950: "multiple Dictionary parameters"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03951 - GAUSS-03960
+
+<br/>
+
+GAUSS-03951: "unrecognized Thesaurus parameter: '%s'"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03952: "missing DictFile parameter"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03953: "missing Dictionary parameter"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03954: "forbidden call of thesaurus or nested call"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03955: "invalid text search configuration file name '%s'"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03957: "text search parser does not support headline creation"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03958: "word is too long to be indexed"
+
+SQLSTATE: 54000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03959: "unrecognized synonym parameter: '%s'"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03960: "missing Synonyms parameter"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03961 - GAUSS-03970
+
+<br/>
+
+GAUSS-03962: "multiple AffFile parameters"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03963: "multiple StopWords parameters"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03964: "unrecognized Ispell parameter: '%s'"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03965: "missing AffFile parameter"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03966: "internal error in RS_isRegis: state %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03967: "invalid regis pattern: '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03968: "internal error in RS_compile: state %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-03971 - GAUSS-03980
+
+<br/>
+
+GAUSS-03971: "syntax error"
+
+SQLSTATE: F0000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03972: "unrecognized state in parse_affentry: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03974: "could not open affix file '%s': %m"
+
+SQLSTATE: F0000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03977: "multiple Accept parameters"
+
+SQLSTATE: 22023
+
+错误原因: 输入了多个Accept参数。
+
+解决办法: 检查参数。
+
+GAUSS-03978: "unrecognized simple dictionary parameter: '%s'"
+
+SQLSTATE: 22023
+
+错误原因: 输入了错误的dictionary参数。
+
+解决办法: 检查参数。
+
+GAUSS-03979: "conversion from wchar_t to server encoding failed: %m"
+
+SQLSTATE: 22021
+
+错误原因: 将某个wchar_t字符转换成服务器的编码方式失败。
+
+解决办法: 检查待转换的字符。
+
+GAUSS-03980: "unrecognized headline parameter: '%s'"
+
+SQLSTATE: 22023
+
+错误原因: 对于HighlightAll命令输入了错误的参数。
+
+解决办法: 对于HighlightAll参数只能是1、on、true、t、y和yes。
+
+<br/>
+
+## GAUSS-03981 - GAUSS-03990
+
+<br/>
+
+GAUSS-03981: "MinWords should be less than MaxWords"
+
+SQLSTATE: 22023
+
+错误原因: 输入的min_words比max_words大。
+
+解决办法: 调整min_words和max_words。
+
+GAUSS-03982: "MinWords should be positive"
+
+SQLSTATE: 22023
+
+错误原因: 输入的min_words小于0。
+
+解决办法: 调整min_words为正数。
+
+GAUSS-03983: "ShortWord should be >= 0"
+
+SQLSTATE: 22023
+
+错误原因: 输入的ShortWord小于0。
+
+解决办法: 调整ShortWord大于等于0。
+
+GAUSS-03984: "MaxFragments should be >= 0"
+
+SQLSTATE: 22023
+
+错误原因: 输入的MaxFragments小于0。
+
+解决办法: 调整MaxFragments大于等于0。
+
+GAUSS-03985: "Invalid formatter options '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 数据格式不合法。
+
+解决办法: 请检查数据格式，再次执行操作。
+
+GAUSS-03986: "locations can not use different protocols"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03987: "invalid file header location '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03988: "Loading mode '%s' not recognized"
+
+SQLSTATE: XX000
+
+错误原因: 不可识别的模式。
+
+解决办法: 请使用normal，shared，private模式，再次执行操作。
+
+GAUSS-03989: "LOAD format '%s' not recognized"
+
+SQLSTATE: 22023
+
+错误原因: 不可识别的模式。
+
+解决办法: 请使用text，csv，fixed模式，再次执行操作。
+
+<br/>
+
+## GAUSS-03991 - GAUSS-04000
+
+<br/>
+
+GAUSS-03993: "location '%s' is invalid"
+
+SQLSTATE: 42000
+
+错误原因: 路径格式不正确。
+
+解决办法: 请检查确保路径正确后，再次执行操作。
+
+GAUSS-03994: "SHARED mode can not use location '%s'"
+
+SQLSTATE: 42601
+
+错误原因: SHARED模式不支持使用远程路径。
+
+解决办法: 请替换为本地路径后，再次执行操作。
+
+GAUSS-03995: "PRIVATE mode can not use location '%s'"
+
+SQLSTATE: 42601
+
+错误原因: PRIVATE模式不支持使用远程路径。
+
+解决办法: 请替换为本地路径后，再次执行操作。
+
+GAUSS-03996: "Normal mode can not use location '%s'"
+
+SQLSTATE: 42601
+
+错误原因: NORMAL模式不支持使用远程路径。
+
+解决办法: 请替换为本地路径后，再次执行操作。
+
+GAUSS-03997: "can not specify multiple local locations"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03998: "HEADER needs FILEHEADER specification in WRITE ONLY foreign table"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-03999: "can not scan a WRITE ONLY foreign table"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/41-GAUSS-04001-GAUSS-04100.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/41-GAUSS-04001-GAUSS-04100.md
new file mode 100644
index 0000000000000000000000000000000000000000..efd1fc4cc4867cdb94e4e3fe2dc84e422df0dd4b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/41-GAUSS-04001-GAUSS-04100.md
@@ -0,0 +1,724 @@
+---
+title: GAUSS-04001 - GAUSS-04100
+summary: GAUSS-04001 - GAUSS-04100
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-04001 - GAUSS-04100
+
+<br/>
+
+## GAUSS-04001 - GAUSS-04010
+
+<br/>
+
+GAUSS-04001: "invalid option '%s'"
+
+SQLSTATE: HV00D
+
+错误原因: 参数选项不合法。
+
+解决办法: 请检查输入参数，再次执行操作。
+
+GAUSS-04002: "SHARED mode can only be used with TEXT format"
+
+SQLSTATE: XX000
+
+错误原因: 用户尝试在使用shared模式的GDS外表时使用TEXT以外的格式。
+
+解决办法: 报错对应的GDS外表仅能够读取TEXT格式文件流，请在导入规格中做对应修改。
+
+GAUSS-04003: "can't find error record table '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内存不足，导致错误表加载失败。
+
+解决办法: 待操作系统回收部分内存后，再次执行操作。
+
+GAUSS-04005: "could not read from file: %m"
+
+SQLSTATE: XX000
+
+错误原因: 文件不存在或权限不正确。
+
+解决办法: 请检查文件是否存在或权限是否正确，再次执行操作。
+
+GAUSS-04006: "unable to open URL '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 文件不存在或权限不正确。
+
+解决办法: 请检查文件是否存在或权限是否正确，再次执行操作。
+
+GAUSS-04007: "fill_missing_fields can't be set while '%s' is NOT NULL"
+
+SQLSTATE: 42601
+
+错误原因: 非空列不能设置fill_missing_fields。
+
+解决办法: 请检查输入参数后，再次执行操作。
+
+GAUSS-04008: "unsupport BINARY format"
+
+SQLSTATE: XX000
+
+错误原因: 不支持二进制格式数据。
+
+解决办法: 请检查输入数据格式后，再次执行操作。
+
+GAUSS-04009: "only both text && csv formats are supported for foreign table"
+
+SQLSTATE: 0A000
+
+错误原因: 外表仅支持text和csv格式数据。
+
+解决办法: 检查外表数据格式，再次执行操作。
+
+GAUSS-04010: "%s doesn't exist, please create it first"
+
+SQLSTATE: XX000
+
+错误原因: 文件夹不存在或权限不正确。
+
+解决办法: 请检查文件夹是否存在或权限是否正确，再次执行操作。
+
+<br/>
+
+## GAUSS-04011 - GAUSS-04020
+
+<br/>
+
+GAUSS-04011: "%s exists and is a file, please remove it first and create directory"
+
+SQLSTATE: XX000
+
+错误原因: 文件夹不存在或权限不正确。
+
+解决办法: 请删除并创建文件夹或使用其他的路径，再次执行操作。
+
+GAUSS-04012: "location filepath is too long when importing data to foreign table"
+
+SQLSTATE: 22023
+
+错误原因: 外表的文件夹路径太长。
+
+解决办法: 请使用合适的路径，再次执行操作。
+
+GAUSS-04014: "no Snowball stemmer available for language '%s' and encoding '%s'"
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04015: "multiple Language parameters"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04016: "unrecognized Snowball parameter: '%s'"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04017: "missing Language parameter"
+
+SQLSTATE: 22023
+
+错误原因: Language参数缺失。
+
+解决办法: 请增加语言参数后，重新执行操作。
+
+GAUSS-04018: "could not translate host name '%s' to address: %s"
+
+SQLSTATE: XX000
+
+错误原因: 不能将主机名转换为IP地址。
+
+解决办法: 请检查hba.conf中配置的主机名称，IP地址是否正确。
+
+GAUSS-04019: "unsupported integer size %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04020: "no data left in message"
+
+SQLSTATE: 08P01
+
+错误原因: 消息中已经没有数据。
+
+解决办法: 数据库内部通信异常，请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04021 - GAUSS-04030
+
+<br/>
+
+GAUSS-04021: "insufficient data left in message"
+
+SQLSTATE: 08P01
+
+错误原因: message中剩余的长度小于message首获取的长度值。
+
+解决办法: 检查当前字符串。
+
+GAUSS-04022: "invalid string in message"
+
+SQLSTATE: 08P01
+
+错误原因: 消息无效。
+
+解决办法: 数据库内部通信异常，请联系技术支持工程师提供技术支持。
+
+GAUSS-04023: "invalid message format"
+
+SQLSTATE: 08P01
+
+错误原因: 消息格式无效。
+
+解决办法: 数据库内部通信异常，请联系技术支持工程师提供技术支持。
+
+GAUSS-04024: "Postgres-XC does not support large object yet"
+
+SQLSTATE: 0A000
+
+错误原因: 目前还不支持large object。
+
+解决办法: 不建议使用此特性。
+
+GAUSS-04025: "invalid large-object descriptor: %d"
+
+SQLSTATE: 42704
+
+错误原因: 无效的大对象描述符。
+
+解决办法: 不支持的特性。
+
+GAUSS-04026: "permission denied for large object %u"
+
+SQLSTATE: 42501
+
+错误原因: 目前还不支持超大对象。
+
+解决办法: 不支持的特性。
+
+GAUSS-04027: "large object descriptor %d was not opened for writing"
+
+SQLSTATE: 55000
+
+错误原因: 目前还不支持超大对象。
+
+解决办法: 不支持的特性。
+
+GAUSS-04028: "must be system admin to use server-side lo_import()"
+
+SQLSTATE: 42501
+
+错误原因: 必须为系统管理员权限才能使用服务器端的lo_import函数。
+
+解决办法: 不支持的特性。
+
+GAUSS-04029: "could not open server file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 打开服务器文件失败。
+
+解决办法: 不支持的特性。
+
+GAUSS-04030: "could not read server file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 读取服务器文件失败。
+
+解决办法: 不支持的特性。
+
+<br/>
+
+## GAUSS-04031 - GAUSS-04040
+
+<br/>
+
+GAUSS-04031: "must be system admin to use server-side lo_export()"
+
+SQLSTATE: 42501
+
+错误原因: 必须为系统管理员权限才能使用服务器端的lo_export函数。
+
+解决办法: 禁止使用不支持的函数。
+
+GAUSS-04032: "could not create server file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 创建服务器文件失败。
+
+解决办法: 禁止使用不支持的函数。
+
+GAUSS-04033: "could not chmod server file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 修改服务器文件权限失败。
+
+解决办法: 禁止使用不支持的函数。
+
+GAUSS-04034: "could not write server file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 写入服务器文件失败。
+
+解决办法: 禁止使用不支持的函数。
+
+GAUSS-04035: "connection requires a valid client certificate"
+
+SQLSTATE: 28000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04038: "pg_hba.conf rejects connection for host '%s', user '%s', database '%s', %s"
+
+SQLSTATE: 28000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04039: "pg_hba.conf rejects connection for host '%s', user '%s', database '%s'"
+
+SQLSTATE: 28000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04040: "no pg_hba.conf entry for host '%s', user '%s', database '%s', %s"
+
+SQLSTATE: 28000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04041 - GAUSS-04050
+
+<br/>
+
+GAUSS-04041: "no pg_hba.conf entry for host '%s', user '%s', database '%s'"
+
+SQLSTATE: 28000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04045: "Invalid username/password,login denied."
+
+SQLSTATE: 28000
+
+错误原因: 用户名或密码无效，登录失败。
+
+解决办法: 检查登录的用户名和密码是否有效。
+
+GAUSS-04047: "SSPI is not supported in protocol version 2"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04048: "out of memory"
+
+SQLSTATE: XX000
+
+错误原因: 无法申请内存。
+
+解决办法: 请检查系统看是否有足够的内存。
+
+GAUSS-04050: "malloc failed"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04051 - GAUSS-04060
+
+<br/>
+
+GAUSS-04051: "could not set the cipher list (no valid ciphers available)"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04052: "sslciphers can not be null"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04053: "unrecognized ssl ciphers name: '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04055: "could not load server certificate file '%s': %s"
+
+SQLSTATE: F0000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04057: "private key file '%s' has group or world access"
+
+SQLSTATE: F0000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04058: "could not load private key file '%s': %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04059: "check of private key '%s'failed: %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04061 - GAUSS-04070
+
+<br/>
+
+GAUSS-04061: "could not load the ca certificate file"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04062: "could not load root certificate file '%s': %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04063: "could not load SSL certificate revocation list file '%s': %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04068: "cipher file '%s' has group or world access"
+
+SQLSTATE: F0000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04069: "rand file '%s' has group or world access"
+
+SQLSTATE: F0000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04070: "spin.c does not support S_LOCK_FREE()"
+
+SQLSTATE: XX000
+
+错误原因: 不支持S_LOCK_FREE()。
+
+解决办法: 检查操作系统是否在支持的范围内。
+
+<br/>
+
+## GAUSS-04071 - GAUSS-04080
+
+<br/>
+
+GAUSS-04071: "not enough elements in RWConflictPool to record a read/write conflict"
+
+SQLSTATE: 53200
+
+错误原因: RWConflictPool 内存不足，不能记录更多的读写冲突。
+
+解决办法: 增加max_connections设置，或在新事务中重新执行。
+
+GAUSS-04072: "not enough elements in RWConflictPool to record a potential read/write conflict"
+
+SQLSTATE: 53200
+
+错误原因: RWConflictPool 内存不足，不能记录更多的读写冲突。
+
+解决办法: 增加max_connections设置，或在新事务中重新执行。
+
+GAUSS-04073: "not enough shared memory for elements of data structure '%s' (%lu bytes requested)"
+
+SQLSTATE: 53200
+
+错误原因: 没有足够共享内存初始化PredXactList。
+
+解决办法: 检查系统剩余内存是否足够。
+
+GAUSS-04074: "cannot use serializable mode in a hot standby"
+
+SQLSTATE: 0A000
+
+错误原因: hot standby不能设置为可串行化模式。
+
+解决办法: 检查default_transaction_isolation设置，设置为repeatable read。
+
+GAUSS-04075: "a snapshot-importing transaction must not be READ ONLY DEFERRABLE"
+
+SQLSTATE: 0A000
+
+错误原因: 不支持READ ONLY DEFERRABLE事务导入快照。
+
+解决办法: 请调整事务级别。
+
+GAUSS-04076: "could not serialize access due to read/write dependencies among transactions"
+
+SQLSTATE: 40001
+
+错误原因: 可串行化下读写冲突。
+
+解决办法: 尝试再次执行。
+
+GAUSS-04077: "unrecognized return value from HeapTupleSatisfiesVacuum: %u"
+
+SQLSTATE: XX000
+
+错误原因: HeapTupleSatisfiesVacuum返回值不识别。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04078: "deadlock seems to have disappeared"
+
+SQLSTATE: XX000
+
+错误原因: 死锁非正常消失。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04079: "inconsistent results during deadlock check"
+
+SQLSTATE: XX000
+
+错误原因: 死锁检测出现不一致结果。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04080: "deadlock detected"
+
+SQLSTATE: 40P01
+
+错误原因: 检测到死锁。
+
+解决办法: 请使用SELECT pg_cancel_backend结束掉死锁线程，再次执行操作。
+
+<br/>
+
+## GAUSS-04081 - GAUSS-04090
+
+<br/>
+
+GAUSS-04081: "proc header uninitialized"
+
+SQLSTATE: XX000
+
+错误原因: ProcGlobal 未初始化。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04082: "you already exist"
+
+SQLSTATE: XX000
+
+错误原因: 进程已退出。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04084: "could not set timer for process wakeup"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04085: "Lock wait timeout: thread %lu on node %s waiting for %s on %s after %ld.%03d ms"
+
+SQLSTATE: YY002
+
+错误原因: 分布式锁等待超时。
+
+解决办法: 检查并发执行情况。
+
+GAUSS-04086: "could not disable timer for process wakeup"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04087: "stuck spinlock (%p) detected at %s:%d"
+
+SQLSTATE: XX000
+
+错误原因: spinlock卡住时间过长。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04089: "unrecognized lock mode: %d"
+
+SQLSTATE: XX000
+
+错误原因: lock mode不识别。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04090: "cannot acquire lock mode %s on database objects while recovery is in progress"
+
+SQLSTATE: 55000
+
+错误原因: 恢复过程中申请的锁级别不正确。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04091 - GAUSS-04100
+
+<br/>
+
+GAUSS-04091: "proclock table corrupted"
+
+SQLSTATE: XX000
+
+错误原因: proclock 哈希表损坏。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04092: "LockAcquire failed"
+
+SQLSTATE: XX000
+
+错误原因: 常规锁申请失败。
+
+解决办法: 检查并发执行情况。
+
+GAUSS-04093: "lock table corrupted"
+
+SQLSTATE: XX000
+
+错误原因: lock 哈希表损坏。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04094: "lock %s on object %u/%u/%u is already held"
+
+SQLSTATE: XX000
+
+错误原因: 加锁的对象已经持有了这个锁。
+
+解决办法: 检查对象加锁情况。
+
+GAUSS-04095: "locallock table corrupted"
+
+SQLSTATE: XX000
+
+错误原因: locallock 哈希表损坏。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04096: "failed to re-find shared lock object"
+
+SQLSTATE: XX000
+
+错误原因: 重新查找shared lock失败。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04097: "failed to re-find shared proclock object"
+
+SQLSTATE: XX000
+
+错误原因: 重新查找shared proclock失败。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04098: "too many conflicting locks found"
+
+SQLSTATE: XX000
+
+错误原因: 常规锁冲突数>MaxBackends。
+
+解决办法: 降低业务并发。
+
+GAUSS-04099: "cannot PREPARE while holding both session-level and transaction-level locks on the same object"
+
+SQLSTATE: 0A000
+
+错误原因: 不能对同一对象同时持有session级和事务级锁。
+
+解决办法: 检查对象加锁情况。
+
+GAUSS-04100: "we seem to have dropped a bit somewhere"
+
+SQLSTATE: XX000
+
+错误原因: 持有锁和放锁mask不匹配。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/42-GAUSS-04101-GAUSS-04200.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/42-GAUSS-04101-GAUSS-04200.md
new file mode 100644
index 0000000000000000000000000000000000000000..bba371cdcbed4e400f08b8207729e36f0f34e10d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/42-GAUSS-04101-GAUSS-04200.md
@@ -0,0 +1,478 @@
+---
+title: GAUSS-04101 - GAUSS-04200
+summary: GAUSS-04101 - GAUSS-04200
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-04101 - GAUSS-04200
+
+<br/>
+
+## GAUSS-04101 - GAUSS-04110
+
+<br/>
+
+GAUSS-04102: "too many LWLocks taken"
+
+SQLSTATE: XX000
+
+错误原因: 持有了太多轻量级锁。
+
+解决办法: 降低业务并发。
+
+GAUSS-04103: "cannot wait without a PGPROC structure"
+
+SQLSTATE: XX000
+
+错误原因: MyProc为NULL。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04107: "invalid flags: %d"
+
+SQLSTATE: XX000
+
+错误原因: 打开大对象标志错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04108: "null field found in pg_largeobject"
+
+SQLSTATE: XX000
+
+错误原因: 大对象在pg_largeobject中记录错误。
+
+解决办法: 检查pg_largeobject。
+
+GAUSS-04109: "invalid seek offset: %d"
+
+SQLSTATE: XX000
+
+错误原因: 大对象访问偏移量错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04110: "invalid whence: %d"
+
+SQLSTATE: XX000
+
+错误原因: 大对象访问标志错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04111 - GAUSS-04120
+
+<br/>
+
+GAUSS-04111: "large object %u was not opened for writing"
+
+SQLSTATE: 55000
+
+错误原因: 大对象未打开。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04113: "no empty local buffer available"
+
+SQLSTATE: 53000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04118: "cannot access temporary tables of other sessions"
+
+SQLSTATE: 0A000
+
+错误原因:  不支持使用非当前会话的临时表。
+
+解决办法: 请使用本会话的临时表或普通表。
+
+GAUSS-04119: "unexpected data beyond EOF in block %u of relation %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04121 - GAUSS-04130
+
+<br/>
+
+GAUSS-04121: "buffer is pinned in InvalidateBuffer"
+
+SQLSTATE: XX010
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04122: "bad buffer ID: %d"
+
+SQLSTATE: XX010
+
+错误原因: bufid错误。
+
+解决办法: 内部错误，属于预防性报错机制。请联系技术支持工程师提供技术支持。
+
+GAUSS-04123: "unrecognized buffer lock mode: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04124: "incorrect local pin count: %d"
+
+SQLSTATE: XX010
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04125: "multiple backends attempting to wait for pincount 1"
+
+SQLSTATE: XX010
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04126: "no unpinned buffers available"
+
+SQLSTATE: XX010
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04127: "unrecognized buffer access strategy: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04128: "malloc fails, out of memory"
+
+SQLSTATE: XX000
+
+错误原因: 系统内存不足，导致对象空间分配失败。
+
+解决办法: 待操作系回收部分内存后，再次执行操作。
+
+GAUSS-04129: "Could not open file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 列存文件打开失败。
+
+解决办法: 请根据错误提示检查打开失败的文件，或者请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04131 - GAUSS-04140
+
+<br/>
+
+GAUSS-04131: "flush file '%s' failed: %m"
+
+SQLSTATE: XX000
+
+错误原因: 列存文件写入失败。
+
+解决办法: 请根据错误提示检查写入失败的文件，或者请联系技术支持工程师提供技术支持。
+
+GAUSS-04134: "memory is not enough during decompressing CU for integer type %d"
+
+SQLSTATE: XX000
+
+错误原因: 列存CU解压缩时内存不足。
+
+解决办法: 请调大数据库内存配置参数，或者请联系技术支持工程师提供技术支持。
+
+GAUSS-04135: "data corrupts during decompressing CU for integer type %d"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04138: "could not initialize CStore Column space desc hash table"
+
+SQLSTATE: XX000
+
+错误原因: 列式存储模式下初始化空闲空间哈希表失败。
+
+解决办法: 请重启数据库。
+
+GAUSS-04139: "No CUID is left for new CU in relation '%u'. Please execute the VACUUM FULL before do anything else"
+
+SQLSTATE: XX000
+
+错误原因: CUID耗尽。
+
+解决办法: 请在VACUUM执行成功后，再次执行操作。
+
+GAUSS-04140: "build global column space cache hash table failed"
+
+SQLSTATE: XX000
+
+错误原因: 列式存储模式下初始化空闲空间哈希表失败。
+
+解决办法: 重启数据库。
+
+<br/>
+
+## GAUSS-04141 - GAUSS-04150
+
+<br/>
+
+GAUSS-04141: "unsupported byval length: %d"
+
+SQLSTATE: XX000
+
+错误原因: 行存字典压缩，数据类型不支持。
+
+解决办法: 检查数据类型。
+
+GAUSS-04146: "corrupted item pointer: offset = %u, size = %u"
+
+SQLSTATE: XX001
+
+错误原因: 索引页的结构破坏。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04147: "incorrect index offsets supplied"
+
+SQLSTATE: XX000
+
+错误原因: 要求删除的索引元组在页内的位置是无效的。
+
+解决办法: 尝试再次执行解决。
+
+GAUSS-04148: "no free slots in PMChildFlags array"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04149: "canceling statement due to conflict with recovery"
+
+SQLSTATE: 40P01
+
+错误原因: 由于和回复冲突停止连接。
+
+解决办法: 过会儿重连数据库，重输入命令。
+
+<br/>
+
+## GAUSS-04151 - GAUSS-04160
+
+<br/>
+
+GAUSS-04152: "GTM error, could not obtain snapshot"
+
+SQLSTATE: 08006
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04156: "should be attached to shared memory already"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04157: "can not malloc memory for HeapmemIndexHeapmemIndex (%lu bytes requested)"
+
+SQLSTATE: 53200
+
+错误原因: 系统内存不足，导致共享缓存创建失败。
+
+解决办法: 待操作系回收部分内存后，再次执行操作。
+
+GAUSS-04158: "could not create HeapMemIndex entry for data structure '%s'"
+
+SQLSTATE: 53200
+
+错误原因: 系统内存不足，导致共享缓存元数据创建失败。
+
+解决办法: 待操作系回收部分内存后，再次执行操作。
+
+GAUSS-04159: "HeapMemIndex entry size is wrong for data structure '%s': expected %lu, actual %lu"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04160: "not enough heap memory for data structure '%s' (%lu bytes requested)"
+
+SQLSTATE: 53200
+
+错误原因: 系统内存不足，导致共享缓存元数据创建失败。
+
+解决办法: 待操作系回收部分内存后，再次执行操作。
+
+<br/>
+
+## GAUSS-04161 - GAUSS-04170
+
+<br/>
+
+GAUSS-04161: "not enough shared memory for data structure '%s' (%lu bytes requested)"
+
+SQLSTATE: 53200
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04162: "could not create ShmemIndex entry for data structure '%s'"
+
+SQLSTATE: 53200
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04163: "ShmemIndex entry size is wrong for data structure '%s': expected %lu, actual %lu"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04165: "could not initialize shared file id hash table"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04166: "insufficient file descriptors available to start server process"
+
+SQLSTATE: 53000
+
+错误原因: 文件句柄不足。
+
+解决办法: 请设置操作系统句柄恢复为合理值后，重启数据库。
+
+GAUSS-04167: "could not close file '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 无法关闭指定文件。
+
+解决办法: 检查指定文件是否被破坏或权限问题。
+
+GAUSS-04168: "file cache corrupted, file %s not opened with handle: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04171 - GAUSS-04180
+
+<br/>
+
+GAUSS-04171: "temporary file size exceeds temp_file_limit (%dkB)"
+
+SQLSTATE: 53400
+
+错误原因: 临时文件大小达到上限。
+
+解决办法: 请设置配置项temp_file_limit为合理值后，再次执行操作。
+
+GAUSS-04173: "Invalid socket fd '%d' for poll():%m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04174: "'%s:%d' connect failed"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04176: "AllocateDesc kind not recognized"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04178: "could not read directory '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04191 - GAUSS-04200
+
+<br/>
+
+GAUSS-04192: "could not open file '%s' (target block %u): %m"
+
+SQLSTATE: XX000
+
+错误原因: 文件打开失败，发生IO错误。
+
+解决办法: 检查是否文件句柄资源不足。
+
+GAUSS-04196: "invalid string enlargement request size: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04197: "bind message has %d result formats but query has %d columns"
+
+SQLSTATE: 08P01
+
+错误原因: 输出的结果列数和要求的列数不一致。
+
+解决办法: 检查query。
+
+GAUSS-04200: "unsupported portal strategy: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/43-GAUSS-04201-GAUSS-04300.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/43-GAUSS-04201-GAUSS-04300.md
new file mode 100644
index 0000000000000000000000000000000000000000..7f2dd9e96001c810a6f2a3c8982f2508f276a3e9
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/43-GAUSS-04201-GAUSS-04300.md
@@ -0,0 +1,692 @@
+---
+title: GAUSS-04201 - GAUSS-04300
+summary: GAUSS-04201 - GAUSS-04300
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-04201 - GAUSS-04300
+
+<br/>
+
+## GAUSS-04201 - GAUSS-04210
+
+<br/>
+
+GAUSS-04201: "unsupported portal strategy"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04202: "bogus direction"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04203: "invalid argument size %d in function call message"
+
+SQLSTATE: 08P01
+
+错误原因: 在函数调用时输入了无效的参数大小，argsize < -1。
+
+解决办法: 检查函数调用的参数个数。
+
+GAUSS-04204: "function %s has more than %d arguments"
+
+SQLSTATE: XX000
+
+错误原因: SQL参数不对。
+
+解决办法: 修改SQL。
+
+GAUSS-04205: "current transaction is aborted, commands ignored until end of transaction block"
+
+SQLSTATE: 25P02
+
+错误原因: 事务回滚时，接受了非commit和rollback的命令。
+
+解决办法: 执行sql语句时，要保证上一个事务已经提交或者回滚。
+
+GAUSS-04206: "function call message contains %d arguments but function requires %d"
+
+SQLSTATE: 08P01
+
+错误原因: 函数调用时输入的参数个数和定义的函数需要的个数不一致。
+
+解决办法: 检查函数调用的参数个数。
+
+GAUSS-04207: "function call message contains %d argument formats but %d arguments"
+
+SQLSTATE: 08P01
+
+错误原因: 函数调用时输入的格式参数个数与函数定义的不一致。
+
+解决办法: 检查函数调用的参数个数。
+
+GAUSS-04208: "incorrect binary data format in function argument %d"
+
+SQLSTATE: 22P03
+
+错误原因: 函数参数有不正确的二进制数据格式。
+
+解决办法: 检查函数调用的参数格式。
+
+GAUSS-04209: "invalid frontend message type %d"
+
+SQLSTATE: 08P01
+
+错误原因: 无效的信息类型。
+
+解决办法: 输入有效的message type类型。
+
+GAUSS-04210: "could not set timer for session timeout"
+
+SQLSTATE: 58000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04211 - GAUSS-04220
+
+<br/>
+
+GAUSS-04211: "could not disable timer for session timeout"
+
+SQLSTATE: 58000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04214: "bind message has %d parameter formats but %d parameters"
+
+SQLSTATE: 08P01
+
+错误原因: 使用接口时，绑定参数的个数和实际传入的参数个数不一致。
+
+解决办法: 传参时要保证参数个数和预期的个数一致。
+
+GAUSS-04215: "cannot insert multiple commands into a prepared statement"
+
+SQLSTATE: 42601
+
+错误原因: 在prepared statement中插入了多条命令。
+
+解决办法: 仅插入一条命令。
+
+GAUSS-04217: "bind message supplies %d parameters, but prepared statement '%s' requires %d"
+
+SQLSTATE: 08P01
+
+错误原因: bind message提供的参数个数不对。
+
+解决办法: 提供正确的参数。
+
+GAUSS-04218: "incorrect binary data format in bind parameter %d"
+
+SQLSTATE: 22P03
+
+错误原因: bind参数里有不正确的二进制数据。
+
+解决办法: 提供正确的参数。
+
+GAUSS-04219: "portal '%s' does not exist"
+
+SQLSTATE: 34000
+
+错误原因: portal不存在。
+
+解决办法: 检查对应的portal，传入正确的portal name。
+
+GAUSS-04220: "floating-point exception"
+
+SQLSTATE: 22P01
+
+错误原因: float异常，如过界，除以0等。
+
+解决办法: 输入有效的float值。
+
+<br/>
+
+## GAUSS-04221 - GAUSS-04230
+
+<br/>
+
+GAUSS-04221: "unrecognized conflict mode: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04222: "terminating autovacuum process due to administrator command"
+
+SQLSTATE: 57P01
+
+错误原因: autovacuum进程被管理员停止。
+
+解决办法: 请与管理员联系确认autovacuum是否被停止，并由管理员重新启动。
+
+GAUSS-04223: "terminating connection due to conflict with recovery"
+
+SQLSTATE: 40001
+
+错误原因: 数据库服务端正在进行数据恢复，当前请求与其冲突，无法连接。
+
+解决办法: 请稍后重连数据库，并重新执行命令。
+
+GAUSS-04224: "terminating connection due to conflict with recovery"
+
+SQLSTATE: 57P04
+
+错误原因: 数据库服务端正在进行数据恢复，当前请求与其冲突，无法连接。
+
+解决办法: 请稍后重连数据库，并重新执行命令。
+
+GAUSS-04225: "terminating connection due to administrator command"
+
+SQLSTATE: 57P01
+
+错误原因: 管理员停止了当前连接。
+
+解决办法: 请与管理员联系确认停止连接的原因。
+
+GAUSS-04226: "connection to client lost"
+
+SQLSTATE: 08006
+
+错误原因: 连接丢失。
+
+解决办法: 请检查网络连接是否正常。
+
+GAUSS-04229: "canceling autovacuum task"
+
+SQLSTATE: 57014
+
+错误原因: autovauum任务被取消。
+
+解决办法: 检查进程中断原因。
+
+GAUSS-04230: "canceling statement due to conflict with recovery"
+
+SQLSTATE: 40001
+
+错误原因: 由于和回复冲突停止连接。
+
+解决办法: 过会儿重连数据库，重输入命令。
+
+<br/>
+
+## GAUSS-04231 - GAUSS-04240
+
+<br/>
+
+GAUSS-04231: "canceling statement due to %s request"
+
+SQLSTATE: 57014
+
+错误原因: 用户或者CN取消了该操作。
+
+解决办法: 请检查用户或CN取消操作的原因是否正常。如果是正常的取消操作，可以不用处理。如果是异常取消，请分析和修复。
+
+GAUSS-04232: "stack depth limit exceeded"
+
+SQLSTATE: 54001
+
+错误原因: 栈的深度超限。超过了max_stack_depth_bytes（默认是100*1024）的值。
+
+解决办法: 请检查递归调用函数使用情况，有否出现递归深度太深情况。若有，考虑优化或者扩展max_stack_depth_bytes。
+
+GAUSS-04233: "local xids can be used only in single user mode"
+
+SQLSTATE: 42601
+
+错误原因: localxid只能在单用户模式下使用。
+
+解决办法: 需增加-single参数。
+
+GAUSS-04235: "invalid command-line argument for server process: %s"
+
+SQLSTATE: 42601
+
+错误原因: 链接库的时候对服务进程输入了无效的命令行参数。
+
+解决办法: 用-help确认参数的作用，输入正确的参数。
+
+GAUSS-04236: "%s: invalid command-line argument: %s"
+
+SQLSTATE: 42601
+
+错误原因: 链接库的时候输入了无效的命令行参数。
+
+解决办法: 用-help确认参数的作用，输入正确的参数。
+
+GAUSS-04238: "%s: no database nor user name specified"
+
+SQLSTATE: 22023
+
+错误原因: 链接库的时候没有指定数据库或用户名。
+
+解决办法: 带上数据库和用户名参数。
+
+GAUSS-04239: "invalid CLOSE message subtype %d"
+
+SQLSTATE: 08P01
+
+错误原因: 从前端或者标准输入中输入了无效的CLOSE命令。
+
+解决办法: 输入正确的CLOSE命令，CLOSE类型只能是S或者P。
+
+GAUSS-04240: "invalid DESCRIBE message subtype %d"
+
+SQLSTATE: 08P01
+
+错误原因: 从前端或者标准输入中输入了无效的DESCRIBE命令。
+
+解决办法: 输入正确的DESCRIBE命令，describe类型只能是S或者P。
+
+<br/>
+
+## GAUSS-04241 - GAUSS-04250
+
+<br/>
+
+GAUSS-04241: "Invalid command received"
+
+SQLSTATE: XX000
+
+错误原因: 从前端或者标准输入中输入了无效的命令，‘b’打头的，非bP、bX和bE。
+
+解决办法: 输入正确的命令。
+
+GAUSS-04242: "cannot execute %s in a read-only transaction"
+
+SQLSTATE: 25006
+
+错误原因: 在只读事务中执行了更新数据库类型操作。
+
+解决办法: 检查操作中更新类型操作，若要执行要求事务为非只读事务。
+
+GAUSS-04243: "cannot execute %s during recovery"
+
+SQLSTATE: 25006
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04244: "cannot execute %s within security-restricted operation"
+
+SQLSTATE: 42501
+
+错误原因: 在安全限制下不能执行某些操作。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04245: "Invalid transaciton_id to prepare."
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04247: "non-DECLARE CURSOR PlannedStmt passed to ProcessUtility"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04248: "CREATE not supported for TEMP and non-TEMP objects"
+
+SQLSTATE: 0A000
+
+错误原因: 不支持用一条语句同事创建临时和非临时对象。
+
+解决办法: 修改SQL语句，将临时对象和非临时对象分开成多条语句创建。
+
+GAUSS-04249: "Postgres-XC does not support FOREIGN DATA WRAPPER yet"
+
+SQLSTATE: 0A000
+
+错误原因: 特征不支持，不支持FOREIGN DATA WRAPPER。
+
+解决办法:  系统内部错误。请联系技术支持工程师提供技术支持。
+
+GAUSS-04250: "Postgres-XC does not support USER MAPPING yet"
+
+SQLSTATE: 0A000
+
+错误原因: 不支持CREATE USER MAPPING语句。
+
+解决办法: 不要执行CREATE USER MAPPING。
+
+<br/>
+
+## GAUSS-04251 - GAUSS-04260
+
+<br/>
+
+GAUSS-04251: "PGXC does not support concurrent INDEX yet"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04253: "unrecognized alter domain type: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04254: "PGXC does not support GRANT on multiple object types"
+
+SQLSTATE: 0A000
+
+错误原因: MogDB的GRANT语法不支持同时操作VIEW和TABLE。
+
+解决办法: 建议对VIEW和TABLE的GRANT操作分开执行。
+
+GAUSS-04255: "unrecognized define stmt type: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04257: "DROP not supported for TEMP and non-TEMP objects"
+
+SQLSTATE: 0A000
+
+错误原因: 在DROP语句一次性drop多个对象时，这些对象中不能既有临时对象，同时又有非临时对象。
+
+解决办法: 应该将临时对象和非临时对象分开DROP。
+
+GAUSS-04258: "%s is not yet supported."
+
+SQLSTATE: 0A000
+
+错误原因: 在黑名单开关（support_extended_features）为off时，黑名单上的特性不被支持。
+
+解决办法: 如果使用黑名单上的对象，应该打开黑名单开关，并不对黑名单上的对象做ALTER或DELETE操作。
+
+GAUSS-04260: "Failed to send snapshot to Datanode %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误: 向DN发送snapshot失败。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04261 - GAUSS-04270
+
+<br/>
+
+GAUSS-04261: "Failed to send queryid to Datanode %u"
+
+SQLSTATE: XX000
+
+错误原因: 通信错误。
+
+解决办法: 请检查网络状态，或确认是否出现节点故障。
+
+GAUSS-04265: "delete or update failed because lock conflict"
+
+SQLSTATE: XX000
+
+错误原因: 由于删除/更新条件复杂，导致同一CU中的两行在删除/更新执行的时机间隔较长，使Tuple删除/更新锁冲突。
+
+解决办法: 调整删除/更新条件，降低执行的复杂度。
+
+GAUSS-04266: "delete or update row conflict"
+
+SQLSTATE: XX000
+
+错误原因: 数据被多次删除/更新。
+
+解决办法: 检查删除/更新条件，是否一行数据被多次删除/更新。
+
+GAUSS-04267: "GiST page split into too many halves (%d, maximum %d)"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04270: "PER NODE REJECT LIMIT must be greater than 0"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04271 - GAUSS-04280
+
+<br/>
+
+GAUSS-04271: "Invalid name \\'%s\\' in REMOTE LOG"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04272: "PER NODE REJECT LIMIT only available on READ ONLY foreign table"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04273: "PER NODE REJECT LIMIT only available with LOG INTO or REMOTE LOG"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04275: "REMOTE LOG only available on in NORMAL mode"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04276: "FILL_MISSING_FIELDS only available on READ ONLY foreign table"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04277: "MODE only available on READ ONLY foreign table"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04279: "can not specify relative local locations"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04280: "could not fetch expected length:%m"
+
+SQLSTATE: XX000
+
+错误原因: 错误表尝试记录错误数据时发生错误。
+
+解决办法: 请结合报错Context，尝试定位文本中导致此报错的数据行，检查是否存在非法字符。若仍不能解决，请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04281 - GAUSS-04290
+
+<br/>
+
+GAUSS-04283: "pg_largeobject entry for OID %u, page %d has invalid data field size %d"
+
+SQLSTATE: XX001
+
+错误原因: 大对象的片断长度无效，数据损坏。
+
+解决办法: 请尝试使用已备份的数据进行恢复，或者请联系技术支持工程师提供技术支持。
+
+GAUSS-04284: "exceeded maxAllocatedDescs (%d) while trying to open file '%s:%d'"
+
+SQLSTATE: 53000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04285: "exceeded maxAllocatedDescs (%d) while trying to open file '%s'"
+
+SQLSTATE: 53000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04286: "exceeded maxAllocatedDescs (%d) while trying to open directory '%s'"
+
+SQLSTATE: 53000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04287: "must have at least one column"
+
+SQLSTATE: 0A000
+
+错误原因: CREATE TABLE语法没有指定表的列信息。
+
+解决办法: 请确认CREATE TABLE table_name({column_name data_type})语法中表名后面的列名信息为空，需要至少指定一列。
+
+GAUSS-04290: "length of field '%s' longer than limit of \\'%d\\'"
+
+SQLSTATE: 22P04
+
+错误原因: 使用Fixed格式的GDS外表进行导出时列数据长度大于外表表明长度。
+
+解决办法: 请根据报错信息修改外表定义。
+
+<br/>
+
+## GAUSS-04291 - GAUSS-04300
+
+<br/>
+
+GAUSS-04291: "tsquery is too large"
+
+SQLSTATE: 54000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04292: "bit string length exceeds the maximum allowed (%d)"
+
+SQLSTATE: 54000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04293: "language validation function %u called for language %u instead of %u"
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04294:"The name of memory context is too long(>=%dbytes)"
+
+SQLSTATE: 42602
+
+错误原因: 内存上下文的名称超出了限定值MEMORY_CONTEXT_NAME_LEN。
+
+解决办法: 由用户确认内存上下文的合法性。
+
+GAUSS-04295:"Fail to send signal to backend(tid:%lu). "
+
+SQLSTATE: XX000
+
+错误原因: 向backend thread发送内部信号失败。
+
+解决办法: backend可能已经退出，由用户确认该backend是否还存在。
+
+GAUSS-04296:"out of memory when preparing zlib encoder. "
+
+SQLSTATE: 53200
+
+错误原因: 系统内存不足导致压缩所需大块内存申请失败。
+
+解决办法: 释放系统中不必要的进程，再次执行导入。
+
+GAUSS-04297:"level %d is invalid when preparing zlib encoder. "
+
+SQLSTATE: XX000
+
+错误原因: zlib压缩级别设置错误。
+
+解决办法: 导入时使用low/middle压缩级别。
+
+GAUSS-04298: "version is incompatible when preparing zlib encoder."
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04299:"error %d occurs when preparing zlib encoder. "
+
+SQLSTATE: XX000
+
+错误原因: 系统资源不足导致。
+
+解决办法: 释放不必要的内存资源，再次执行导入。
+
+GAUSS-04300:"RLE decompress failed, expected bytes %d, real size %d "
+
+SQLSTATE: XX001
+
+错误原因: 数据损坏。
+
+解决办法: 需要使用已备份的数据进行恢复。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/44-GAUSS-04301-GAUSS-04400.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/44-GAUSS-04301-GAUSS-04400.md
new file mode 100644
index 0000000000000000000000000000000000000000..e33f28e09d60807c3520fa0c7495e26324a5730b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/44-GAUSS-04301-GAUSS-04400.md
@@ -0,0 +1,444 @@
+---
+title: GAUSS-04301 - GAUSS-04400
+summary: GAUSS-04301 - GAUSS-04400
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-04301 - GAUSS-04400
+
+<br/>
+
+## GAUSS-04301 - GAUSS-04310
+
+<br/>
+
+GAUSS-04308: "%s: could not locate bin path"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04311 - GAUSS-04320
+
+<br/>
+
+GAUSS-04325: "Parallel Function: Failed to send command to Datanode %u"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04321 - GAUSS-04330
+
+<br/>
+
+GAUSS-04321: "Failed to receive GTM commit transaction response after %s.
+
+SQLSTATE: XX000
+
+错误原因: 可能由于GTM断连，无法得到通知GTM提交事务的反馈信息。
+
+解决办法: 检查与GTM的连接正常与否。
+
+GAUSS-04325: "Parallel Function: Failed to send command to Datanode %u "
+
+SQLSTATE: XX000
+
+错误原因: 向DN发送sql/plan失败。
+
+解决办法: 内部错误，请联系技术支持工程师提供技术支持。
+
+GAUSS-04326: "Parallel Function: Failed to read response from Datanodes Detail: %s"
+
+SQLSTATE: XX000
+
+错误原因: 收不到对端DN的消息响应。
+
+解决办法: 检查是否有节点故障或者网络连接是否正常。
+
+GAUSS-04330: "pooler: Failed to send SIGTERM to postgres thread:%lu in PoolManagerAbortTransactions(), failed: %m"
+
+SQLSTATE: XX000
+
+错误原因: 向backend thread发送内部信号失败。
+
+解决办法: 用户可以再次重试。
+
+<br/>
+
+## GAUSS-04331 - GAUSS-04340
+
+<br/>
+
+GAUSS-04333: "pooler: invalid cn/dn node number, input cn: %d, dn: %d; current cn: %d, dn: %d"
+
+SQLSTATE: 08006
+
+错误原因: 非法的参数类型。
+
+解决办法: 这是为预防开发时程序内部逻辑错误而设置的报错，一旦出现，应由开发人员定位。
+
+GAUSS-04335: "pooler: Communication failure, failed to send session commands or invalid incoming data."
+
+SQLSTATE: 08000
+
+错误原因: 连接出现错误，和DN的通讯失败。
+
+解决办法: 重新执行query。
+
+GAUSS-04336: "pooler: Failed to duplicate fd, error: %s"
+
+SQLSTATE: XX000
+
+错误原因: 这是一个系统错误，可能是进程打开的句柄数受到限制。
+
+解决办法: 更改系统设置，增大进程能打开的句柄数。
+
+GAUSS-04339: "pooler: Failed to reset agent!"
+
+SQLSTATE: XX000
+
+错误原因: 内存上下文错误。
+
+解决办法: 重新执行query。
+
+<br/>
+
+## GAUSS-04341 - GAUSS-04350
+
+<br/>
+
+GAUSS-04342: "concurrent update under Stream mode is not yet supported"
+
+SQLSTATE: 0A000
+
+错误原因: Stream模式下不支持并发更新操作。
+
+解决办法: 关掉enable_stream_operator开关或者避免Stream模式下的并发更新操作。
+
+GAUSS-04344: "cannot read results"
+
+SQLSTATE: XX000
+
+错误原因: 不能读取数据，系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04345: "Operator with OID %u dose not exist."
+
+SQLSTATE: XX000
+
+错误原因: 此操作符不存在。
+
+解决办法: 使用正确的操作符如‘+’，‘-’等。
+
+GAUSS-04348: "%s is redistributing, please retry later."
+
+SQLSTATE: 0A000
+
+错误原因: 正在重分布的表不支持导入之外的其他DDL操作。
+
+解决办法: 等待正在重分布的表重分布完成后重试。
+
+GAUSS-04350: "duplicated URL '%s' in LOCATION"
+
+SQLSTATE: XX000
+
+错误原因: gds使用的URL重复。
+
+解决办法: 确认gds使用的URL与已存在使用的URL不重复。
+
+<br/>
+
+## GAUSS-04351 - GAUSS-04360
+
+<br/>
+
+GAUSS-04351: "IGNORE_EXTRA_DATA only available on READ ONLY foreign table"
+
+SQLSTATE: 42601
+
+错误原因: 创建可写外表时，在OPTIONS中使用了IGNORE_EXTRA_DATA。
+
+解决办法: 删除外表定义OPTIONS中的IGNORE_EXTRA_DATA。
+
+GAUSS-04352: "Permission denied to drop resource pools."
+
+SQLSTATE: 42501
+
+错误原因: 禁止普通用户进行删除resource pool对象的操作。
+
+解决办法: 只有系统用户可以对resource pool对象进行删除操作。普通用户无权删除。
+
+GAUSS-04353: "App Workload Group Mapping '%s': object not defined"
+
+SQLSTATE: 42704
+
+错误原因: 不允许移除一个不存在的app workload group mapping。
+
+解决办法: 只允许移除一个已存在的app workload group mapping。
+
+GAUSS-04355: "internal error, rename partitioned table failed"
+
+SQLSTATE: XX000
+
+错误原因: 重命名分区表失败。
+
+解决办法: 请确认ALTER TABLE [ IF EXISTS ] table_name RENAME TO new_table_name;语法中table_name和new_table_name是否正确。
+
+GAUSS-04356: "internal error, rename partition failed"
+
+SQLSTATE: XX000
+
+错误原因: 重命名表分区失败。
+
+解决办法: 请确认ALTER TABLE..RENAME PARTITION partition_name TO partition_new_name;语法中partition_name或partition_new_name是否为已存在分区。
+
+GAUSS-04358: "statistics percent valid value is between 0 and 100"
+
+SQLSTATE: 22023
+
+错误原因: 设置的百分比不在0-100之间。
+
+解决办法: 调整设置的百分比数据，保证在0-100之间。
+
+GAUSS-04360: "Partition cache lookup failed for index partition %u"
+
+SQLSTATE: XX000
+
+错误原因: cache数据瞬时刷新，分区索引查询失败。
+
+解决办法: 重新执行此操作。
+
+<br/>
+
+## GAUSS-04361 - GAUSS-04370
+
+<br/>
+
+GAUSS-04361: "explain_perf_mode requires FORMAT TEXT"
+
+SQLSTATE: 22023
+
+错误原因: 此参数设置为非normal模式时，使用了非text格式的format。
+
+解决办法: 设置explain_perf_mode为非normal格式时，需要format必须是text格式。
+
+GAUSS-04363: "unsupported type %d"
+
+SQLSTATE: XX000
+
+错误原因: 使用了未支持的类型，系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04365: "The expiration time could not be earlier than the starting time."
+
+SQLSTATE: XX000
+
+错误原因: 在设置帐户有效期时，帐号的有效开始时间比有效结束时间还要晚，这对于帐户来说是不可取的。
+
+解决办法: 检查设置帐户有效期时有效开始时间和有效结束时间的时间关系。
+
+GAUSS-04366: "The old password can not be NULL, please input your old password with 'replace' grammar."
+
+SQLSTATE: XX000
+
+错误原因: 在修改系统管理员用户密码或使用identified by语法修改用户密码时需要提供原始密码用于确认。如果没有提供原始密码则报错。
+
+解决办法: 修改系统管理员用户密码或使用identified by语法修改用户密码时，需要使用replace语法给出原始密码。
+
+GAUSS-04367: "The old password is invalid."
+
+SQLSTATE: XX000
+
+错误原因: 利用identified by … replace语法修改用户密码时给出的用户当前密码不正确。
+
+解决办法: 在使用identified by … replace语法修改用户的密码时需要提供正确的帐户当前密码。
+
+GAUSS-04368: "Permission denied to rename the initial account."
+
+SQLSTATE: 42501
+
+错误原因: 不允许用户尝试对数据库初始化用户进行重命名。
+
+解决办法: 检查需要重命名的对象，如果为数据库初始化用户，则不允许重命名。
+
+<br/>
+
+## GAUSS-04371 - GAUSS-04380
+
+<br/>
+
+GAUSS-04371: "Invalid value for tablespace maxsize: '%s'"
+
+SQLSTATE: 22023
+
+错误原因: 表空间限额设置格式或者数值不正确。
+
+解决办法: 依据对应的提示信息进行修正格式或者数值。
+
+GAUSS-04372: "tablespace cannot be created under data directory"
+
+SQLSTATE: 42P17
+
+错误原因: 用户在data目录下面创建tablespace会产生这个错误。
+
+解决办法: 不允许在data目录创建tablespace，发现创建的tablespace的绝对路径包含data目录则报错。
+
+GAUSS-04373: "unchangeable tablespace '%s'"
+
+SQLSTATE: 42939
+
+错误原因: 不允许修改系统表空间或者私有表空间。
+
+解决办法: 修正用户表空间名称为合法名称。
+
+GAUSS-04374: "Insufficient storage space for tablespace '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 配置给用户的表空间全部使用完毕。
+
+解决办法: 请联系管理员调整表空间配额。
+
+GAUSS-04375: "Communication failure, failed to send set commands to pool."
+
+SQLSTATE: 08000
+
+错误原因: 通信异常
+
+解决办法: 检查主机的网络状态，等待网络压力不大以后再执行该操作。
+
+GAUSS-04376: "explain_dna_file should be .csv file."
+
+SQLSTATE: XX000
+
+错误原因: 设置的文件名称不是.csv格式的。
+
+解决办法: 设置成.csv格式的文件名即可。
+
+GAUSS-04377: "explain_dna_file should be absolute path + .csv file."
+
+SQLSTATE: XX000
+
+错误原因: explain_dna_file参数没有设置成绝对路径+.csv格式的文件
+
+解决办法: explain_dna_file参数需要设置成绝对路径+.csv格式的文件。
+
+GAUSS-04378: "you are not allowed to do that operation immediately, please try again later"
+
+SQLSTATE: XX000
+
+错误原因: 不允许频率过快的使用该命令。
+
+解决办法: 保持一定的时间间隔来执行此命令。
+
+GAUSS-04379: "The account is not within the period of validity. "
+
+SQLSTATE: XX000
+
+错误原因: 当前帐户不在有效期范围内。
+
+解决办法: 需要由安全管理员重新设定用户的有效开始时间和有效结束时间。
+
+GAUSS-04380: "memory is temporarily unavailable"
+
+SQLSTATE: 53200
+
+错误原因: 申请内存时，无法满足需求，则报该错误。
+
+解决办法: ERROR级别，回滚正在执行的作业。
+
+<br/>
+
+## GAUSS-04381 - GAUSS-04390
+
+<br/>
+
+GAUSS-04381: "detected write past chunk end in %s %p"
+
+SQLSTATE: XX000
+
+错误原因: 在free内存时，验证填充的字符，若不正确，报错。
+
+解决办法: PANIC级别，用于Debug模式下的内存越界检查，终止进程，产生core。
+
+GAUSS-04383: "Bucketmap is NULL"
+
+SQLSTATE: XX000
+
+错误原因: Bucketmap为空。
+
+解决办法: 不要执行该操作。
+
+GAUSS-04385: "invalid name of memory context: NULL or " "
+
+SQLSTATE: XX000
+
+错误原因: 函数参数检查，NULL或者空字符串被认为是非法的内存上下文名称。
+
+解决办法: 由用户确保内存上下文名称的合法性。
+
+GAUSS-04386: "Failed to receive GTM commit transaction response for DN or other CN."
+
+SQLSTATE: XX000
+
+错误原因: 可能由于GTM断连，无法得到通知GTM提交事务的反馈信息。
+
+解决办法: 检查与GTM的连接正常与否。
+
+GAUSS-04387: "column '%s' needs too many memory"
+
+SQLSTATE: 0A000
+
+错误原因: 列存导入记录过大。
+
+解决办法: 当前列存不支持过大记录，使用行存进行导入。
+
+GAUSS-04390: "Failed to initialze NativeTarget for LLVM."
+
+SQLSTATE: XX000
+
+错误原因: 启动数据库时初始化LLVM本地对象失败。
+
+解决办法: 重新启动数据库。
+
+<br/>
+
+## GAUSS-04391 - GAUSS-04400
+
+<br/>
+
+GAUSS-04391: "Failed to initialze NativeTargetAsmPrinter for LLVM."
+
+SQLSTATE: XX000
+
+错误原因: 启动数据库时初始化LLVM本地对象ASM打印器失败。
+
+解决办法: 重新启动数据库。
+
+GAUSS-04392: "Failed to initialze NativeTargetAsmParser for LLVM."
+
+SQLSTATE: XX000
+
+错误原因: 启动数据库时初始化LLVM本地对象ASM解析器失败。
+
+解决办法: 重新启动数据库。
+
+GAUSS-04400: "Include identical distribution column '%s'"
+
+SQLSTATE: 42P16
+
+错误原因: 建表时指定了两个相同的分布列。
+
+解决办法: 修改建表语句。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/45-GAUSS-04401-GAUSS-04500.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/45-GAUSS-04401-GAUSS-04500.md
new file mode 100644
index 0000000000000000000000000000000000000000..18b4973fe2b5304c56904be109c93c1190ae4f00
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/45-GAUSS-04401-GAUSS-04500.md
@@ -0,0 +1,457 @@
+---
+title: GAUSS-04401 - GAUSS-04500
+summary: GAUSS-04401 - GAUSS-04500
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-04401 - GAUSS-04500
+
+<br/>
+
+## GAUSS-04401 - GAUSS-04410
+
+<br/>
+
+GAUSS-04401: "The local index %u on the partition %u not exist."
+
+SQLSTATE: 42704
+
+错误原因: 可能由于drop partition和drop index并发，在drop index的时候可能对应index已经不存在了。
+
+解决办法: 调整并发控制
+
+GAUSS-04403: "Can only access temp objects of the current session."
+
+SQLSTATE: 0A000
+
+错误原因: 访问了其他session的临时对象。
+
+解决办法: 只允许访问本session的临时对象，不支持访问其他session的临时对象。
+
+GAUSS-04404: "cache lookup failed for role %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04405: "temp relation is invalid because of cluster resizing"
+
+SQLSTATE: 0A000
+
+错误原因: 扩容/缩容后原有临时表失效。
+
+解决办法:
+
+1. 退出当前session，再重新连接并创建临时表
+2. 使用DROP SCHEMA %s, %s CASCADE来删除临时schema，再重建临时表。
+
+GAUSS-04407: "Not allowed to insert into relation pg_auth_history."
+
+SQLSTATE: XX000
+
+错误原因: pg_auth_history用于审计帐户密码的变更。只有当pg_authid中的帐户密码发生变化时才记录相应的变动。如果认为变更，将影响审计。
+
+解决办法: 禁止使用insert …into…语句人为向pg_auth_history中插入记录。
+
+GAUSS-04408: "do not support create non-temp table like temp table"
+
+SQLSTATE: 0A000
+
+错误原因: 创建普通表时使用了like临时表语法，不支持这样使用。
+
+解决办法: 不支持创建非临时表like临时表，如果要使用like临时表语法，请将要创建的表也指定为临时表。
+
+<br/>
+
+## GAUSS-04411 - GAUSS-04420
+
+<br/>
+
+GAUSS-04411: "Multi-column combined informational constraint is forbidden."
+
+SQLSTATE: 0A000
+
+错误原因: 不支持多列组合信息约束。
+
+解决办法: 在一个列上建立信息约束。
+
+GAUSS-04414: "The number of %s distribute key can not exceed 1"
+
+SQLSTATE: 42601
+
+错误原因: 非hash分布的表的分布列不能超过1。
+
+解决办法: 修改建表语句，指定一个列作为分布列。
+
+GAUSS-04415: "Compatibility args %s is invalid"
+
+SQLSTATE: 22023
+
+错误原因: 指定的兼容行参数不对。
+
+解决办法: 指定参数为'ORA'或者'TD'。
+
+GAUSS-04417: "Alias '%s' reference with window function included is not supported."
+
+SQLSTATE: 42703
+
+错误原因: 别名引用，被引用的表达式不能包含window function。
+
+解决办法: 修改sql语句，不支持该用法。
+
+GAUSS-04418: "Alias '%s' reference with volatile function included is not supported."
+
+SQLSTATE: 42703
+
+错误原因: 别名引用，被引用的表达式不能包含volatile function。
+
+解决办法: 修改sql语句，不支持该用法。
+
+GAUSS-04419: "Alias '%s' is ambiguous."
+
+SQLSTATE: 42703
+
+错误原因: 使用别名重复。
+
+解决办法: 更换别名，避免别名重复。
+
+<br/>
+
+## GAUSS-04421 - GAUSS-04430
+
+<br/>
+
+GAUSS-04422: "%u/%u/%u invalid bcm meta buffer %u"
+
+SQLSTATE: XX000
+
+错误原因: 无效的BCM文件的meta页面。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04424: "Vector aggregation does not support this distinct clause in aggregate function"
+
+SQLSTATE: XX000
+
+错误原因: aggregation向量化执行引擎初始化时，聚合函数不支持distinct子句。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04425: "Grant not supported for TEMP and non-TEMP objects together"
+
+SQLSTATE: 0A000
+
+错误原因: Grant操作不支持临时对象和非临时对象一起出现。
+
+解决办法: 将要执行的语句拆分成两句，将临时对象和非临时对象分开执行。
+
+GAUSS-04426: "Explicit prepare transaction is not supported."
+
+SQLSTATE: 0A000
+
+错误原因: 不支持显式prepare。由于用户输入了显式prepare语句。
+
+解决办法: 不输入显式prepare语句。
+
+GAUSS-04427: "Explicit commit prepared transaction is not supported."
+
+SQLSTATE: 0A000
+
+错误原因: 不支持显式commit prepared。由于用户输入了显式commit prepared语句。
+
+解决办法: 不输入显式commit prepared语句。
+
+GAUSS-04428: "Explicit rollback prepared transaction is not supported."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04429: "LOCK not supported for TEMP and non-TEMP objects together"
+
+SQLSTATE: 0A000
+
+错误原因: LOCK操作不支持临时对象和非临时对象一起出现。
+
+解决办法: 将要执行的语句拆分成两句，将临时对象和非临时对象分开执行。
+
+<br/>
+
+## GAUSS-04431 - GAUSS-04440
+
+<br/>
+
+GAUSS-04432: "invalid set size for BipartiteMatch"
+
+SQLSTATE: XX000
+
+错误原因: 输入参数错误，系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04433: "AIO Completer io_getevents() failed: error %d ."
+
+SQLSTATE: XX000
+
+错误原因: 操作系统函数io_getevents()执行失败。
+
+解决办法: 检测操作系统内核函数是否大于Linux 2.6.23，确认操作系统安装了libaio库。
+
+GAUSS-04434: "parent of GROUPING is not VecAgg node"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04435: "parent of GROUPINGID is not VecAgg node"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04436: "Unsupported alternative subPlan expression in vector engine"
+
+SQLSTATE: 0A000
+
+错误原因: alternative表达式没有实现向量化。
+
+解决办法: 修改SQL语句。
+
+GAUSS-04437: "Unsupported rowexpr expression in vector engine"
+
+SQLSTATE: 0A000
+
+错误原因: rowexpr表达式没有向量化。
+
+解决办法: 修改SQL语句。
+
+GAUSS-04438: "unsupported vector sub plan type %d"
+
+SQLSTATE: XX000
+
+错误原因: 用了向量化执行引擎不支持的Subplan类型，报错提示不支持。
+
+解决办法: 修改SQL语句。
+
+GAUSS-04439: "Unsupported state in vec sort agg"
+
+SQLSTATE: 20000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04440: "Failed to connect hdfs."
+
+SQLSTATE: XX000
+
+错误原因: 连接HDFS失败。
+
+解决办法: 请检查CN日志，根据这条报错可以搜索到具体报错原因。
+
+<br/>
+
+## GAUSS-04441 - GAUSS-04450
+
+<br/>
+
+GAUSS-04441: "Unsupport store format, only support ORC format for DFS table."
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。HDFS表检测数据格式，发现不是ORC格式。
+
+解决办法: 修改数据格式。
+
+GAUSS-04442: "'INSERT' is not supported by the type of relation."
+
+SQLSTATE: D0011
+
+错误原因: 该表不支持insert操作。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04443: "'DELETE' is not supported by the type of relation."
+
+SQLSTATE: D0011
+
+错误原因: 该表不支持delete操作。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04444: "'UPDATE' is not supported by the type of relation."
+
+SQLSTATE: D0011
+
+错误原因: 该表不支持update操作。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04449: "parent of GROUPING is not Agg node"
+
+SQLSTATE: 42P27
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04450: "parent of GROUPINGID is not Agg node"
+
+SQLSTATE: 42P27
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04461 - GAUSS-04470
+
+<br/>
+
+GAUSS-04468: "corrupt during reset shared hash table '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 重置共享hash表过程中内存崩溃。
+
+解决办法: 节点重启，无须额外处理。
+
+GAUSS-04469: "terminating SyncLocalXactsWithGTM process due to administrator command"
+
+SQLSTATE: 57P01
+
+错误原因: 主降备或者系统退出过程中SyncLocalXactsWithGTM被停止。
+
+解决办法: 无须额外处理。
+
+<br/>
+
+## GAUSS-04471 - GAUSS-04480
+
+<br/>
+
+GAUSS-04471: "fallocate(fd=%d, amount=%d, offset=%ld),write count(%d), errno(%d), maybe you use adio without XFS filesystem, if you really want do this,please turn off GUC parameter enable_fast_allocate"
+
+SQLSTATE: XX000
+
+错误原因: 快速分配数据文件块失败。
+
+解决办法: 确认文件系统是XFS，若不是请关闭enable_fast_allocate配置项。
+
+GAUSS-04472: "FileAsyncRead, file access failed %d"
+
+SQLSTATE: XX000
+
+错误原因: 在异步IO的模式下，服务器读取数据文件前，需要检测到文件状态异常。
+
+解决办法: 请确保数据文件状态正常，若数据文件异常，请从备机或备份数据中恢复。
+
+GAUSS-04474: "FileAsyncWrite, file access failed %d"
+
+SQLSTATE: XX000
+
+错误原因: 异步IO写数据文件前检测到文件状态异常。
+
+解决办法: 请确保数据文件状态正常，若数据文件异常，请从备机或备份数据中恢复。
+
+GAUSS-04476: "FileAccess() FAILED %d"
+
+SQLSTATE: XX000
+
+错误原因: 异步IO读写数据文件前检测到文件状态异常。
+
+解决办法: 请确保数据文件状态正常，若数据文件异常，请从备机或备份数据中恢复。
+
+GAUSS-04479: "fallocate(fd=%d, amount=%u, offset=%u),write count(%d), errno(%d), maybe you use adio without XFS filesystem, if you really want do this,please turn off GUC parameter enable_fast_allocate"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04481 - GAUSS-04490
+
+<br/>
+
+GAUSS-04481: "Require scratch buflist to reorder writes."
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04483: "CheckIOState, find an error in async write"
+
+SQLSTATE: XX000
+
+错误原因:  VACUUM FULL行存表产生写IO错误。
+
+解决办法: 检测磁盘是否发生故障是否需要更新磁盘后可尝试重新执行。
+
+GAUSS-04484: "InProgressBuf not null: id %d flags %u, buf: id %d flags %u"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04485: "posix_memalign fails, The alignment argument was not a power of two, or was not a multiple of sizeof(void *)"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。操作系统内存不足或者申请内存对齐参数不为2的幂次方或者指针参数异常。
+
+解决办法: 操作系统释放部分内存后，可尝试重新执行。
+
+<br/>
+
+## GAUSS-04491 - GAUSS-04500
+
+<br/>
+
+GAUSS-04492: "redundant options."
+
+SQLSTATE: XX000
+
+错误原因: 冗余的选项。
+
+解决办法: 检查DDL语句中的选项是否有重复。
+
+GAUSS-04494: "max_dop value can't be %ld."
+
+SQLSTATE: 22003
+
+错误原因: max_dop的值无效。
+
+解决办法: 设置max_dop的值必须大于等于1。
+
+GAUSS-04495: "invalid value '%s' for parameter '%s'"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04496: "memory_limit size value can't be %d."
+
+SQLSTATE: 22003
+
+错误原因: memory_limit的数值无效。
+
+解决办法: memory_limit的数值必须是正数。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/46-GAUSS-04501-GAUSS-04600.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/46-GAUSS-04501-GAUSS-04600.md
new file mode 100644
index 0000000000000000000000000000000000000000..16b6d92fb6a812a69e0342bc12637c0f9b20d833
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/46-GAUSS-04501-GAUSS-04600.md
@@ -0,0 +1,644 @@
+---
+title: GAUSS-04501 - GAUSS-04600
+summary: GAUSS-04501 - GAUSS-04600
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-04501 - GAUSS-04600
+
+<br/>
+
+## GAUSS-04501 - GAUSS-04510
+
+<br/>
+
+GAUSS-04503: "wrong buffer passed to BCM_clear, BlockNumber from buf is %u,mapBlock is %u"
+
+SQLSTATE: XX000
+
+错误原因: 错误的BCM buffer或者BCM buffer对应的块号和map块号不一致。
+
+解决办法: 系统内部错误。请联系技术支持工程师提供技术支持。
+
+GAUSS-04505: "Please use 'ALTER ROLE user_name IDENTIFIED BY 'password' REPLACE 'old password';' to modify the initial password of user %s before operation!"
+
+SQLSTATE: XX000
+
+错误原因: 未修改初始密码。
+
+解决办法: 使用显示命令修改初始密码。
+
+GAUSS-04506: "SECURITY LABEL is not yet supported."
+
+SQLSTATE: 0A000
+
+错误原因: 特性不支持。
+
+解决办法: 不建议使用。
+
+GAUSS-04507: "domain is not yet supported."
+
+SQLSTATE: 0A000
+
+错误原因: 特性不支持。
+
+解决办法: 不建议使用。
+
+GAUSS-04508: "user defined aggregate is not yet supported."
+
+SQLSTATE: 0A000
+
+错误原因: 特性不支持。
+
+解决办法: 不建议使用。
+
+GAUSS-04509: "user defined operator is not yet supported."
+
+SQLSTATE: 0A000
+
+错误原因: 特性不支持。
+
+解决办法: 不建议使用。
+
+<br/>
+
+## GAUSS-04511 - GAUSS-04520
+
+<br/>
+
+GAUSS-04511: "user-defined text search parser is not yet supported."
+
+SQLSTATE: 0A000
+
+错误原因: 特性不支持。
+
+解决办法: 不建议使用。
+
+GAUSS-04513: "user-defined text search template is not yet supported."
+
+SQLSTATE: 0A000
+
+错误原因: 特性不支持。
+
+解决办法: 不建议使用。
+
+GAUSS-04514: "user defined collation is not yet supported."
+
+SQLSTATE: 0A000
+
+错误原因: 特性不支持。
+
+解决办法: 不建议使用。
+
+GAUSS-04515: "RULE is not yet supported."
+
+SQLSTATE: 0A000
+
+错误原因: 特性不支持。
+
+解决办法: 不建议使用。
+
+GAUSS-04517: "NOFITY statement is not yet supported."
+
+SQLSTATE: 0A000
+
+错误原因: 特性不支持。
+
+解决办法: 不建议使用。
+
+GAUSS-04518: "LISTEN statement is not yet supported."
+
+SQLSTATE: 0A000
+
+错误原因: 特性不支持。
+
+解决办法: 不建议使用。
+
+GAUSS-04520: "LOAD statement is not yet supported."
+
+SQLSTATE: 无
+
+错误原因: 特性不支持。
+
+解决办法: 不建议使用。
+
+<br/>
+
+## GAUSS-04521 - GAUSS-04530
+
+<br/>
+
+GAUSS-04521: "DISCARD statement is not yet supported."
+
+SQLSTATE: 0A000
+
+错误原因: 特性不支持。
+
+解决办法: 不建议使用。
+
+GAUSS-04523: "new language is not yet supported."
+
+SQLSTATE: 0A000
+
+错误原因: 特性不支持。
+
+解决办法: 不建议使用。
+
+GAUSS-04524: "user defined conversion is not yet supported.""
+
+SQLSTATE: 0A000
+
+错误原因: 特性不支持。
+
+解决办法: 不建议使用。
+
+GAUSS-04528: "pg_pool_validate cannot run inside a transaction block"
+
+SQLSTATE: 25001
+
+错误原因: pg_pool_validate函数不能在事务块中执行。
+
+解决办法: 直接调用pg_pool_validate，而不是采用start transaction的方式。
+
+GAUSS-04529: "Failed to send query ID to %s while sending query ID with sync"
+
+SQLSTATE: XX000
+
+错误原因: 发送query ID失败。
+
+解决办法: 检查对端节点是否报错退出，或者当前是否有网络问题。
+
+GAUSS-04530: "Failed to read response from Datanodes while sending query ID with sync. Detail: %s"
+
+SQLSTATE: XX000
+
+错误原因: 发送query ID失败。
+
+解决办法: 检查对端节点是否报错退出，或者当前是否有网络问题。
+
+<br/>
+
+## GAUSS-04531 - GAUSS-04540
+
+<br/>
+
+GAUSS-04531: "Unexpected response from %s while sending query ID with sync"
+
+SQLSTATE: XX000
+
+错误原因: 发送query ID失败。
+
+解决办法: 系统内部错误。请联系技术支持工程师提供技术支持。
+
+GAUSS-04532: "Could not begin transaction on %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。在analyze处理过程中，向CN/DN发送查询pg_class表和pg_statistic表信息构造的query命令失败。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04533: "Failed to read response from CN %u when ending query"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。在analyze处理过程中，其他CN从源CN获取统计pg_class和pg_statistic系统表信息时，从消息缓冲区中收到EOF消息。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04534: "Unexpected response from CN %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。在analyze处理过程中，其他CN从源CN获取统计pg_class和pg_statistic系统表信息时，从消息缓冲区中收到不期望的响应消息。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04535: "Failed to read response from DN %u when ending query"
+
+SQLSTATE: XX000
+
+错误原因: 全局统计信息做analyze过程中，CN从DN1获取pg_class或pg_statistic统计信息时，未收到EOF消息。
+
+解决办法: 系统内部错误。请联系技术支持工程师提供技术支持。
+
+GAUSS-04536: "Unexpected response from DN %u"
+
+SQLSTATE: XX000
+
+错误原因: 全局统计信息做analyze过程中，CN从DN1获取pg_class或pg_statistic统计信息时，收到不期望的响应消息。
+
+解决办法: 系统内部错误。请联系技术支持工程师提供技术支持。
+
+GAUSS-04538: "The relation %s is invalid because of cluster resize, please quit current session and it will be automaticly dropped."
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04539: "Cache lookup failed for relation %u."
+
+SQLSTATE: XX000
+
+错误原因: 输入的表不存在。
+
+解决办法: 执行SQL语句输入正确的表名。
+
+GAUSS-04540: "Failed to create directory on HDFS."
+
+SQLSTATE: 42P17
+
+错误原因: 创建目录失败。
+
+解决办法: 请查看相关日志。
+
+<br/>
+
+## GAUSS-04541 - GAUSS-04550
+
+<br/>
+
+GAUSS-04542: "invalid starelkind for pg_statistic"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04543: "Failed to find the information of DFS table."
+
+SQLSTATE: 42P17
+
+错误原因: 增加delta表的分布信息时，没有找到HDFS的信息。
+
+解决办法: 尝试再次执行解决。
+
+GAUSS-04544: "could not obtain lock on partition(%d)"
+
+SQLSTATE: 55P03
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04545: "function roach_handler must return type 'fdw_handler'"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。roach导出需绑定fdw_handler。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04546: "could not open roach %s"
+
+SQLSTATE: XX000
+
+错误原因: roach导出不能正常打开。
+
+解决办法: 检查roach外表指定的location中包含的roach path是否可以正常访问。
+
+GAUSS-04547: "could not read from roach"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。用roach方式导出时不能正常拷贝数据。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04549: "can not specify multiple locations"
+
+SQLSTATE: 0A000
+
+错误原因: roach导出方式指定的location不能多于一个。
+
+解决办法: 指定roach外表的location只能限定一个。
+
+GAUSS-04550: "could not close roach %s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。roach导出结束后不能正常关闭。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04551 - GAUSS-04560
+
+<br/>
+
+GAUSS-04551: "could not write to roach"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。roach导出时报错。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04552: "COMPATIBLE_ILLEGAL_CHARS only available on READ ONLY foreign table"
+
+SQLSTATE: 42601
+
+错误原因: compatible_illegal_chars导入参数只能用于导入不能用于导出。
+
+解决办法: 对于导出操作去除compatible_illegal_chars参数。
+
+GAUSS-04553: "DATE_FORMAT only available on READ ONLY foreign table"
+
+SQLSTATE: 42601
+
+错误原因: date_format导入参数只能用于导入不能用于导出。
+
+解决办法: 对于导出操作去除date_format参数。
+
+GAUSS-04554: "TIME_FORMAT only available on READ ONLY foreign table"
+
+SQLSTATE: 42601
+
+错误原因: time_format导入参数只能用于导入不能用于导出。
+
+解决办法: 对于导出操作去除time_format参数。
+
+GAUSS-04555: "TIMESTAMP_FORMAT only available on READ ONLY foreign table"
+
+SQLSTATE: 42601
+
+错误原因: timestamp_format导入参数只能用于导入不能用于导出。
+
+解决办法: 对于导出操作去除timestamp_format参数。
+
+GAUSS-04556: "SMALLDATETIME_FORMAT only available on READ ONLY foreign table"
+
+SQLSTATE: 42601
+
+错误原因: smalldatetime_format导入参数只能用于导入不能用于导出。
+
+解决办法: 对于导出操作去除smalldatetime_format参数。
+
+GAUSS-04557: "could not find block %p"
+
+SQLSTATE: XX000
+
+错误原因: 已分配的内存在释放时未发现。
+
+解决办法: 避免double free而导致报错。
+
+GAUSS-04559: "Error happen when execute memcpy_s:%d in reallocating aliged memory"
+
+SQLSTATE: XX000
+
+错误原因: 内存拷贝函数调用失败。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04560: "unsupport to get memory size under aligned memory allocator"
+
+SQLSTATE: XX000
+
+错误原因: 在对齐内存上下文处理时，不支持GetChunkSpace函数。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04561 - GAUSS-04570
+
+<br/>
+
+GAUSS-04562: "unsupport to reallocate memory under stack memory allocator"
+
+SQLSTATE: XX000
+
+错误原因: 在栈式内存上下文处理时，不支持realloc函数。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04563: "unsupport to get memory size under stack memory allocator"
+
+SQLSTATE: XX000
+
+错误原因: 在栈式内存上下文处理时，不支持GetChunkSpace函数。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04564: "could not write to batchstore temporary file: %m"
+
+SQLSTATE: XX000
+
+错误原因: 写临时文件错误。
+
+解决办法: 请检查磁盘空间，磁盘状态是否正确。
+
+GAUSS-04565: "could not write to tuplestore temporary file: %m"
+
+SQLSTATE: XX000
+
+错误原因: 写临时文件错误。
+
+解决办法: 请检查磁盘空间，磁盘状态是否正确。
+
+GAUSS-04566: "unsupported to set memory_detail_tracking value under release version."
+
+SQLSTATE: XX000
+
+错误原因: release版本不支持。
+
+解决办法: 不建议使用。因为此特性在debug版本支持。
+
+GAUSS-04570: "specified timestamp format is null"
+
+SQLSTATE: 22007
+
+错误原因: 支持触发器以及触发器函数。
+
+解决办法: 支持触发器以及触发器函数。
+
+<br/>
+
+## GAUSS-04571 - GAUSS-04580
+
+<br/>
+
+GAUSS-04572: "specified date format is null"
+
+SQLSTATE: 22007
+
+错误原因: SQL参数不对。
+
+解决办法: 修改SQL。
+
+GAUSS-04573: "specified time format is null"
+
+SQLSTATE: 22007
+
+错误原因: 未开启逻辑内存管理功能。
+
+解决办法: 提示用户无法查询的原因。
+
+GAUSS-04574: "unsupported view for memory protection feature is disabled."
+
+SQLSTATE: XX000
+
+错误原因: 不支持特性。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04575: "It is unsupported to calculate size of database '%s' under the DFS tablespace '%s' on data node."
+
+SQLSTATE: 55006
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04576: "It is unsupported to calculate size of DFS tablespace '%s' on data node."
+
+SQLSTATE: 55006
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04578: "ExpectedEntries should be > 0 and < 10000000."
+
+SQLSTATE: XX000
+
+错误原因: 创建bloom filter时指定的元素预期个数超过了允许的范畴。
+
+解决办法: 请联系技术支持工程师提供技术支持。减少指定元素的个数。
+
+GAUSS-04580: "Add too many values to the bloom filter."
+
+SQLSTATE: XX000
+
+错误原因: bloom filter对象中填充的元素个数超过的最大能容纳的限制。
+
+解决办法: 请联系技术支持工程师提供技术支持。将填充对象个数减少在最大容纳个数之内。
+
+<br/>
+
+## GAUSS-04581 - GAUSS-04590
+
+<br/>
+
+GAUSS-04581: "BloomFilters are not compatible for merging."
+
+SQLSTATE: XX000
+
+错误原因: 对两个系数不同的bloom filter对象执行合并操作。
+
+解决办法: 请联系技术支持工程师提供技术支持。不允许两个不同系数的bloom filter对象执行合并操作。
+
+GAUSS-04582: "Failed to get enviroment parameter $GAUSSHOME or it is NULL, please set $GAUSSHOME as your installation directory!"
+
+SQLSTATE: 22004
+
+错误原因: 加载ir文件依赖于环境变量GAUSSHOME，如果未设置GAUSSHOME，则报错处理避免后续无效操作。
+
+解决办法: 检查是否设置环境变量GAUSSHOME，如果没有GAUSSHOME环境变量，需要进行设置。
+
+GAUSS-04584: "Codegen failed on the procedure of ExecVecQual!"
+
+SQLSTATE: XX000
+
+错误原因: 在生成总体IR函数时，若有一个表达式未正确处理，则使用codegen功能失败。
+
+解决办法: 请联系技术支持工程师提供技术支持。确认该查询是否符合代码生成要求并设置enable_codegen=off。
+
+GAUSS-04587: "Codegen failed on the first argument of FuncExpr!"
+
+SQLSTATE: XX000
+
+错误原因: 在处理函数参数时，未成功处理第一个参数，导致代码生成无法继续，报错处理。
+
+解决办法: 请联系技术支持工程师提供技术支持。检查当前函数是否为支持类型确认其参数合理性并设置enable_codegen=off。
+
+GAUSS-04588: "Codegen failed on the second argument of FuncExpr!"
+
+SQLSTATE: XX000
+
+错误原因: 在处理函数参数时，未成功处理第二个参数，导致代码生成无法继续，报错处理。
+
+解决办法: 请联系技术支持工程师提供技术支持。检查当前函数是否为支持类型确认其合理性并设置enable_codegen=off。
+
+GAUSS-04589: "Codegen failed on the third argument of FuncExpr!"
+
+SQLSTATE: XX000
+
+错误原因: 在处理函数参数时，未成功处理第三个参数，导致代码生成无法继续，报错处理。
+
+解决办法: 请联系技术支持工程师提供技术支持。检查当前函数是否为支持类型确认其合理性并设置enable_codegen=off。
+
+<br/>
+
+## GAUSS-04591 - GAUSS-04600
+
+<br/>
+
+GAUSS-04591: "Failed to create LLVM state object ExecutionEngine: %s"
+
+SQLSTATE: 42704
+
+错误原因: 在编译当前module时，需要将module挂靠在一个execution engine上。如果创建该execution engine失败，则报错处理，避免下一步无效操作。
+
+解决办法: 请重新尝试或设置enable_codegen=off完成该查询。
+
+GAUSS-04592: "Codegen failed on verifying IR function %s."
+
+SQLSTATE: 42883
+
+错误原因: 根据代码得到的IR函数是无效的或逻辑存在缺陷。
+
+解决办法: 设置enable_codegen=off来规避该问题。请联系技术支持工程师提供技术支持。
+
+GAUSS-04593: "Failed to create llvm function prototype."
+
+SQLSTATE: XX000
+
+错误原因: 声明LLVM函数原型失败，报错处理。
+
+解决办法: 请重试或设置enable_codegen=off。
+
+GAUSS-04595: "Unsupported LLVM debug type!"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04597: "Failed on getting IR function : LLVMIRtexteq!"
+
+SQLSTATE: XX000
+
+错误原因: 从当前LLVM module中未找到该LLVMIRtexteq函数，为避免后续无效调用，报错处理。
+
+解决办法: 避免对应IR文件的ll文件中包含该函数实现或设置enable_codegen=off来规避该问题。
+
+GAUSS-04598: "Failed on getting IR function : LLVMIRtextlt!"
+
+SQLSTATE: XX000
+
+错误原因: 从当前LLVM module中未找到该LLVMIRtextlt函数，为避免后续无效调用，报错处理。
+
+解决办法: 避免对应IR文件的ll文件中包含该函数实现或设置enable_codegen=off来规避该问题。
+
+GAUSS-04599: "Failed on getting IR function : LLVMIRtextgt!"
+
+SQLSTATE: XX000
+
+错误原因: 从当前LLVM module中未找到该LLVMIRtextgt函数，为避免后续无效调用，报错处理。
+
+解决办法: 避免对应IR文件的ll文件中包含该函数实现或设置enable_codegen=off来规避该问题。
+
+GAUSS-04600: "Failed on getting IR function : LLVMIRsubstring!"
+
+SQLSTATE: XX000
+
+错误原因: 从当前LLVM module中未找到该LLVMIRsubstring函数，未避免后续无效调用，报错处理。
+
+解决办法: 避免对应IR文件的ll文件中包含该函数实现或设置enable_codegen=off来规避该问题。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/47-GAUSS-04601-GAUSS-04700.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/47-GAUSS-04601-GAUSS-04700.md
new file mode 100644
index 0000000000000000000000000000000000000000..49faff058d868da7a415e692b1214e26395163a2
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/47-GAUSS-04601-GAUSS-04700.md
@@ -0,0 +1,614 @@
+---
+title: GAUSS-04601 - GAUSS-04700
+summary: GAUSS-04601 - GAUSS-04700
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-04601 - GAUSS-04700
+
+<br/>
+
+## GAUSS-04601 - GAUSS-04610
+
+<br/>
+
+GAUSS-04601: "Failed on getting IR function : LLVMIRrtrim1!"
+
+SQLSTATE: XX000
+
+错误原因: 对应IR文件的ll文件中包含该函数实现。
+
+解决办法: 避免对应IR文件的ll文件中包含该函数实现或设置enable_codegen=off来规避该问题。
+
+GAUSS-04602: "Failed on getting IR function : LLVMIRbtrim1!"
+
+SQLSTATE: XX000
+
+错误原因: 从当前LLVM module中未找到该LLVMIRbtrim1函数，为避免后续无效调用，报错处理。
+
+解决办法: 避免对应IR文件的ll文件中包含该函数实现或设置enable_codegen=off来规避该问题。
+
+GAUSS-04603: "Failed on getting IR function : LLVMIRbpchareq!"
+
+SQLSTATE: XX000
+
+错误原因: 从当前LLVM module中未找到LLVMIRbpchareq函数，为避免后续无效调用，报错处理。
+
+解决办法: 避免对应IR文件的ll文件中包含该函数实现或设置enable_codegen=off来规避该问题。
+
+GAUSS-04604: "Cannot get the llvm::Intrinsic::sadd_with_overflow function!"
+
+SQLSTATE: XX000
+
+错误原因: 此处需要调用LLVM库中的加法函数，如果声明该加法函数失败，则报错处理。
+
+解决办法: 检查LLVM库及LLVM存放位置是否正确或者请联系技术支持工程师提供技术支持。
+
+GAUSS-04605: "Cannot get the llvm::Intrinsic::ssub_with_overflow function!"
+
+SQLSTATE: XX000
+
+错误原因: 此处需要调用LLVM库中的减法函数，如果声明该减法函数失败，则报错处理。
+
+解决办法: 检查LLVM库及LLVM存放位置是否正确或者请联系技术支持工程师提供技术支持。
+
+GAUSS-04606: "Cannot get the llvm::Intrinsic::smul_with_overflow function!"
+
+SQLSTATE: XX000
+
+错误原因: 此处需要调用LLVM库中的乘法函数，如果声明该乘法函数失败，则报错处理。
+
+解决办法: 检查LLVM库及LLVM存放位置是否正确或者请联系技术支持工程师提供技术支持。
+
+GAUSS-04607: "Unsupport address, cfgpath, storepath options when the filesystem is not HDFS."
+
+SQLSTATE: XX000
+
+错误原因: 在创建tablespace时，只有filesystem选项是HDFS时，才支持address、cfgpath、storepath选项。
+
+解决办法: 请检查CREATE TABLESPACE..LOCATION address, cfgpath, storepath选项内容是否为HDFS的文件系统。
+
+GAUSS-04608: "Failed to get storepath from tablespace options."
+
+SQLSTATE: XX000
+
+错误原因: 无法从创建tablespace的选项中获取有效的storepath参数。
+
+解决办法: 请检查CREATE TABLESPACE..LOCATION语法中是否包含storepath选项。
+
+GAUSS-04609: "Failed to get cfgpath from tablespace options."
+
+SQLSTATE: XX000
+
+错误原因: 创建HDFS表空间时没有找到cfgpath参数。
+
+解决办法: 创建HDFS表空间时，需要指定cfgpath。
+
+GAUSS-04610: "Failed to create directory '%s' on HDFS."
+
+SQLSTATE: 42P17
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04611 - GAUSS-04620
+
+<br/>
+
+GAUSS-04611: "tablespace HDFS path '%s' is too long."
+
+SQLSTATE: 42P17
+
+错误原因: HDFS表空间的cfgpath的路径太长。
+
+解决办法: 设置路径不能超过1024。
+
+GAUSS-04612: "Directory '%s' already in use as a tablespace on HDFS."
+
+SQLSTATE: 55006
+
+错误原因: 报错的目录已经存在，所以创建表空间失败。
+
+解决办法: 创建表空间时重新选取一个storepath参数值。
+
+GAUSS-04613: "Failed to drop external directory, because the cfgpath option has not been found from pg_tablespace."
+
+SQLSTATE: XX000
+
+错误原因: 删除表空间时，在被删除的表空间的option中没有发现cfgpath参数。
+
+解决办法: pg_tablespace系统表中，已存在的表空间名称被异常修改，系统内部错误。请联系技术支持工程师提供技术支持。
+
+GAUSS-04619: "Resource Pool '%s': object not defined."
+
+SQLSTATE: 42704
+
+错误原因: 资源池未定义。
+
+解决办法: 检查资源池是否已经定义。
+
+<br/>
+
+## GAUSS-04621 - GAUSS-04630
+
+<br/>
+
+GAUSS-04622: "Password can't contain more than %d characters."
+
+SQLSTATE: 28P01
+
+错误原因: 帐户密码中不能包含多于%d数目的字符。
+
+解决办法: 修改密码格式，使字符个数不大于%d个。
+
+GAUSS-04623: "invalid GDS command: %d"
+
+SQLSTATE: XX000
+
+错误原因: 收到了非法的GDS交互。
+
+解决办法: 请检查GDS外表对应的导入文件中是否存在非法数据并对文件进行数据清洗后再次导入。
+
+GAUSS-04624: "Failed to deserialize command, which type is %d"
+
+SQLSTATE: XX000
+
+错误原因: 收到了非法的GDS交互。
+
+解决办法: 请检查GDS外表对应的导入文件中是否存在非法数据并对文件进行数据清洗后再次导入。
+
+GAUSS-04626: "Invalid schema oid: %u"
+
+SQLSTATE: 3F000
+
+错误原因: 没有找到用户输入的schema。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04627: "deltamerge: This relation doesn't support vacuum deltamerge operation"
+
+SQLSTATE: 42P01
+
+错误原因: 通过语法"vacuum deltamerge [table_name]"merge delta表时，该表不支持deltamerge操作。
+
+解决办法: 请确认语法vacuum deltamerge [table_name]中指定的table_name是否为delta表。
+
+GAUSS-04629: "gs_switch_relfilenode can be only used by redistribution tool."
+
+SQLSTATE: XX000
+
+错误原因: 元信息交换函数只在重分布工具使用，不建议用户使用。
+
+解决办法: 规格限制，请联系技术支持工程师提供技术支持。
+
+GAUSS-04630: "DFS tablespace can not be used as default tablespace."
+
+SQLSTATE: 22023
+
+错误原因: DFS表空间不允许被用作默认表空间。
+
+解决办法: 不要将DFS表空间用作默认表空间。
+
+<br/>
+
+## GAUSS-04631 - GAUSS-04640
+
+<br/>
+
+GAUSS-04631: "It is unsupported to rename database '%s' on DFS tablespace '%s'."
+
+SQLSTATE: 0A000
+
+错误原因: 如果数据库中的表使用了DFS类型的表空间，那么该数据库不支持重命名。
+
+解决办法: 如果需要对数据库进行重命名，请确认数据库中的表未使用DFS表空间。
+
+GAUSS-04634: "cannot alter text search configuration '%s' because other objects depend on it"
+
+SQLSTATE: 2BP01
+
+错误原因: 由于全文检索配置项与其他表或索引之间存在依赖关系，本配置信息不能更改。
+
+解决办法: 取消依赖关系后在执行本操作。
+
+GAUSS-04637: "It is not allowed to assign version option for non-dfs table."
+
+SQLSTATE: XX000
+
+错误原因: 创建行存表或者CU格式的列存表时指定了version参数直接报错。
+
+解决办法: 创建行存表或者CU格式的列存表时不要version参数。
+
+GAUSS-04638: "Unsupport '%s' option"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04639: "Invalid string for 'VERSION' option"
+
+SQLSTATE: XX000
+
+错误原因: 无效的version参数。
+
+解决办法: 参数只支持0.12。
+
+GAUSS-04640: "Num of partition keys in value-partitioned table should not be zeror"
+
+SQLSTATE: XX000
+
+错误原因: 创建valuesHDFS分区表时，没有指定分区列。
+
+解决办法: 创建valuesHDFS分区表时，指定不少于1，但是不超过4的列数。
+
+<br/>
+
+## GAUSS-04641 - GAUSS-04650
+
+<br/>
+
+GAUSS-04641: "Num of partition keys in value-partitioned table exceeds max allowed num:%d"
+
+SQLSTATE: XX000
+
+错误原因: 创建valuesHDFS分区表时，指定分区列超过四个。
+
+解决办法: 创建valuesHDFS分区表时，指定不少于1，但是不超过4的列数。
+
+GAUSS-04642: "Unsupport partition strategy '%s' feature for dfs table."
+
+SQLSTATE: XX000
+
+错误原因: 仅支持value HDFS分区表，其余分区不支持，直接报错。
+
+解决办法: 创建分区HDFS表时，指定为value分区。
+
+GAUSS-04644: "Value partitioned table can only be created on DFS tablespace."
+
+SQLSTATE: 0A000
+
+错误原因: 对于value分区，只支持在dfs表上创建。
+
+解决办法: 除了dfs表，其他类型表不要创建value分区。
+
+GAUSS-04645: "It is not supported to truncate foreign table '%s'."
+
+SQLSTATE: 42809
+
+错误原因: 对于外表，不支持truncate操作。
+
+解决办法: 对于外表，不要使用truncate操作。
+
+GAUSS-04646: "It is not supported to truncate non-table '%s'"
+
+SQLSTATE: 42809
+
+错误原因: 对于非正常表的数据库对象，不支持truncate操作。
+
+解决办法: 对于非正常表的数据库对象，不要使用truncate操作。
+
+GAUSS-04648: "Storage type '%s' is meaningless for column relation"
+
+SQLSTATE: 0A000
+
+错误原因: 行表的存储类型对于列存表是无意义的。
+
+解决办法: 对列存表不设置存储类型。
+
+GAUSS-04649: "column '%s' cannot be served as a value-partitioning column because of its datatype [%s]"
+
+SQLSTATE: 42804
+
+错误原因: value partition 对于部分类型不支持。
+
+解决办法: 请检查资料文档，确认value partition支持的数据类型范围。
+
+GAUSS-04650: "can not set tablespace for partitioned relation"
+
+SQLSTATE: XX000
+
+错误原因: 变更了分区表的表空间。
+
+解决办法: 对于分区表，不允许变更表空间。
+
+<br/>
+
+## GAUSS-04651 - GAUSS-04660
+
+<br/>
+
+GAUSS-04651: "It is not supported to rename schema '%s' which includes DFS table '%s'."
+
+SQLSTATE: 42939
+
+错误原因: 当前不支持通过ALTER SCHEMA schema_name RENAME TO new_schema_name语法更名包含有DFS表的SCHEMA。
+
+解决办法: 请检查ALTER SCHEMA schema_name RENAME TO new_schema_name语法中schema_name中是否包含DFS表，如果存在则不允许此操作。请删除DFS表后再次做更名操作即可。
+
+GAUSS-04652: "COPY_ROACH does not implement in CopySendEndOfRow"
+
+SQLSTATE: XX000
+
+错误原因: ROACH不能用于COPY TO导出。
+
+解决办法: ROACH不能用于COPY TO导出。
+
+GAUSS-04653: "the bulkload compatible illegal chars flag is already set before bulkload starts"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。之前导入指定非法字符兼容参数未清除。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04655: "cannot specify bulkload compatibility options in BINARY mode"
+
+SQLSTATE: 42601
+
+错误原因: 内部错误: 之前导入的CopyState对象未清除。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04656: "IGNORE_EXTRA_DATA specification only available using COPY FROM or READ ONLY foreign table"
+
+SQLSTATE: 42601
+
+错误原因: ignore_extra_data导入参数只能用于导入不能用于导出。
+
+解决办法: 对于导出操作去除ignore_extra_data参数。
+
+GAUSS-04657: "COMPATIBLE_ILLEGAL_CHARS specification only available using COPY FROM or READ ONLY foreign table"
+
+SQLSTATE: 42601
+
+错误原因: compatible_illegal_chars导入参数只能用于导入不能用于导出。
+
+解决办法: 对于导出操作去除compatible_illegal_chars参数。
+
+GAUSS-04658: "DATE_FORMAT specification only available using COPY FROM or READ ONLY foreign table"
+
+SQLSTATE: 42601
+
+错误原因: date_format导入参数只能用于导入不能用于导出。
+
+解决办法: 对于导出操作去除date_format参数。
+
+GAUSS-04659: "TIME_FORMAT specification only available using COPY FROM or READ ONLY foreign table"
+
+SQLSTATE: 42601
+
+错误原因: time_format导入参数只能用于导入不能用于导出。
+
+解决办法: 对于导出操作去除time_format参数。
+
+GAUSS-04660: "TIMESTAMP_FORMAT specification only available using COPY FROM or READ ONLY foreign table"
+
+SQLSTATE: 42601
+
+错误原因: timestamp_format导入参数只能用于导入不能用于导出。
+
+解决办法: 对于导出操作去除timestamp_format参数。
+
+<br/>
+
+## GAUSS-04661 - GAUSS-04670
+
+<br/>
+
+GAUSS-04662: "illegal chars conversion may confuse COPY null 0x%x"
+
+SQLSTATE: 42601
+
+错误原因: null导入参数设置为空格或者问号，同时又将compatible_illegal_chars设置为true，标识导入非法字符兼容。由于导入非法字符兼容会将非法字符转换为空格或者问号，所以会与null参数混淆引发潜在的导入错误。
+
+解决办法: 将null设置为非空格或问号的其他字符以避免与非法字符转换后产生混淆。
+
+GAUSS-04663: "illegal chars conversion may confuse COPY delimiter 0x%x"
+
+SQLSTATE: 42601
+
+错误原因: delimiter导入参数设置为空格或者问号，同时又将compatible_illegal_chars设置为true，标识导入非法字符兼容。由于导入非法字符兼容会将非法字符转换为空格或者问号，所以会与delimiter参数混淆引发潜在的导入错误。
+
+解决办法: 将delimiter设置为非空格或问号的其他字符以避免与非法字符转换后产生混淆。
+
+GAUSS-04664: "illegal chars conversion may confuse COPY quote 0x%x"
+
+SQLSTATE: XX000
+
+错误原因: quote导入参数设置为空格或者问号，同时又将compatible_illegal_chars设置为true，标识导入非法字符兼容。由于导入非法字符兼容会将非法字符转换为空格或者问号，所以会与quote参数混淆引发潜在的导入错误。
+
+解决办法: 将quote设置为非空格或问号的其他字符以避免与非法字符转换后产生混淆。
+
+GAUSS-04665: "illegal chars conversion may confuse COPY escape 0x%x"
+
+SQLSTATE: 42601
+
+错误原因: escape导入参数设置为空格或者问号，同时又将compatible_illegal_chars设置为true，标识导入非法字符兼容。由于导入非法字符兼容会将非法字符转换为空格或者问号，所以会与escape参数混淆引发潜在的导入错误。
+
+解决办法: 将escape设置为非空格或问号的其他字符以避免与非法字符转换后产生混淆。
+
+GAUSS-04666: "the bulkload state isn't accordant"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。全局变量缓存的CopyState与当前导入的CopyState不一致。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04667: "Failed to get import task for dn:%s"
+
+SQLSTATE: XX000
+
+错误原因: GDS导入数据对于某一个DN未分配导入任务。
+
+解决办法: 可尝试再次执行解决。
+
+GAUSS-04668: "Receive wrong messge %d from GDS."
+
+SQLSTATE: XX000
+
+错误原因: DN从GDS端获取错误消息。
+
+解决办法: 检查当前网络运行状况是否良好，可尝试再次执行解决。
+
+GAUSS-04669: "Receive incomplete message from GDS."
+
+SQLSTATE: XX000
+
+错误原因: DN从GDS端获取当前未支持消息。
+
+解决办法: 检查当前网络运行状况是否良好，可尝试再次执行解决。
+
+<br/>
+
+## GAUSS-04681 - GAUSS-04690
+
+<br/>
+
+GAUSS-04681: "CUBE is limited to 12 elements"
+
+SQLSTATE: 54011
+
+错误原因: CUBE参数个数小于等于12。
+
+解决办法: 修改SQL语句。
+
+GAUSS-04682: "type %s is not yet supported."
+
+SQLSTATE: 0A000
+
+错误原因: 特性不支持。
+
+解决办法: 修改SQL Statement。
+
+GAUSS-04683: "REFERENCES constraint is not yet supported."
+
+SQLSTATE: 0A000
+
+错误原因: 特性不支持。
+
+解决办法: 不建议使用。
+
+GAUSS-04684: "EXCLUDE constraint is not yet supported."
+
+SQLSTATE: 0A000
+
+错误原因: 特性不支持。
+
+解决办法: 不建议使用。
+
+GAUSS-04685: "FOREIGN KEY … REFERENCES constraint is not yet supported."
+
+SQLSTATE: 0A000
+
+错误原因: 特性不支持。
+
+解决办法: 不建议使用。
+
+GAUSS-04686: "CREATE TABLE … INHERITS is not yet supported."
+
+SQLSTATE: 0A000
+
+错误原因: 特性不支持。
+
+解决办法: 不建议使用。
+
+GAUSS-04687: "CREATE TABLE … WITH OIDS is not yet supported."
+
+SQLSTATE: 0A000
+
+错误原因: 特性不支持。
+
+解决办法: 不建议使用。
+
+GAUSS-04689: "CURSOR … WITH HOLD is not yet supported."
+
+SQLSTATE: 0A000
+
+错误原因: 特性不支持。
+
+解决办法: 不建议使用。
+
+GAUSS-04690: "SCROLL CURSOR is not yet supported."
+
+SQLSTATE: 0A000
+
+错误原因: 特性不支持。
+
+解决办法: 不建议使用。
+
+<br/>
+
+## GAUSS-04691 - GAUSS-04700
+
+<br/>
+
+GAUSS-04691: "INSENSITIVE CURSOR is not yet supported."
+
+SQLSTATE: 0A000
+
+错误原因: 特性不支持。
+
+解决办法: 不建议使用。
+
+GAUSS-04693: "For foreign table ROUNDROBIN distribution type is built-in support."
+
+SQLSTATE: 0A000
+
+错误原因: GDS外表内建支持ROUNDROBIN分布信息，不支持在创建外表时显式添加分布信息。
+
+解决办法: 在创建GDS外表时，去除指定的分布信息。
+
+GAUSS-04695: "Value-based partition table should have one column at least"
+
+SQLSTATE: 42601
+
+错误原因: 基于value的分区表至少有一列。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04696: "Value-Based partition table creation encounters unexpected data in unnecessary fields"
+
+SQLSTATE: XX000
+
+错误原因: 创建value分区表时遇到了异常数据。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04697: "too many grouping sets present (max 4096)"
+
+SQLSTATE: 54001
+
+错误原因: 分组个数不能超过4096。
+
+解决办法: 修改SQL语句。
+
+GAUSS-04698: "arguments to GROUPING must be grouping expressions of the associated query level"
+
+SQLSTATE: 42803
+
+错误原因: grouping参数没有再group by子句中找到。
+
+解决办法: 修改SQL语句。
+
+GAUSS-04699: "GROUPING must have fewer than 32 arguments"
+
+SQLSTATE: 54023
+
+错误原因: grouping的参数个数小于32。
+
+解决办法: 修改SQL语句。
+
+GAUSS-04700: "ngram parser only support UTF8/GBK encoding"
+
+SQLSTATE: XX000
+
+错误原因: ngram分词算法只支持UTF8/GBK两种数据库编码格式。
+
+解决办法: NGRAM是为支持中文全文检索引入的分词算法，使用本功能需要确保数据库编码为UTF8/GBK。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/48-GAUSS-04701-GAUSS-04800.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/48-GAUSS-04701-GAUSS-04800.md
new file mode 100644
index 0000000000000000000000000000000000000000..da457800ef716ba1ef629df987c40604689d336f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/48-GAUSS-04701-GAUSS-04800.md
@@ -0,0 +1,559 @@
+---
+title: GAUSS-04701 - GAUSS-04800
+summary: GAUSS-04701 - GAUSS-04800
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-04701 - GAUSS-04800
+
+<br/>
+
+## GAUSS-04701 - GAUSS-04710
+
+<br/>
+
+GAUSS-04706: "The parameter can not smaller than -1."
+
+SQLSTATE: XX000
+
+错误原因: 入参检查，prevbit必须>=-1。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04708: "Column count in table definition does not match with ORC file %s."
+
+SQLSTATE: 22000
+
+错误原因: 表的列定义和orc文件中的列不符合。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04709: "Error occurs while read row index of orc file, detail can be found in dn log of %s."
+
+SQLSTATE: 22000
+
+错误原因: DFS上的ORC格式文件索引数据出错。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04710: "Unsupported orc type : %u."
+
+SQLSTATE: 0A000
+
+错误原因: DFS表不支持该数据类型。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04711 - GAUSS-04720
+
+<br/>
+
+GAUSS-04714: "Unsupported data type : %u."
+
+SQLSTATE: 0A000
+
+错误原因: HDFS表不支持的数据类型。
+
+解决办法: 根据提示的信息变更定义类型为HDFS表支持类型。
+
+GAUSS-04715: "Invalid string for 'COMPRESSION' option."
+
+SQLSTATE: 22023
+
+错误原因: 无效的压缩模式。
+
+解决办法: 创建表时设置正确压缩模式，HDFS只支持zlib和snappy。
+
+<br/>
+
+## GAUSS-04721 - GAUSS-04730
+
+<br/>
+
+GAUSS-04721: "The start index is over the limit."
+
+SQLSTATE: 22000
+
+错误原因: 在HDFS表导入数据时，将上层的数据填充到底层数据流buffer过程中，导入的数据超过了buffer的最大限制。
+
+解决办法: 在对应DN日志中查看具体原因信息。
+
+GAUSS-04722: "DFS connector can not be NULL when loading data into dfs table."
+
+SQLSTATE: 42704
+
+错误原因: HDFS导入过程中，发现和dfs的链接是无效指针。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04726: "We only support pushing down opExpr and null test predicate."
+
+SQLSTATE: 0A000
+
+错误原因: HDFS表过滤谓词出现不支持的类型。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04727: "could not find operator by oid %u"
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。通过OID查找操作类型失败。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04728: "Not support pushing predicate with sublink param now!"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。不支持子查询的谓词下推。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04729: "Not support pushing predicate with non-const"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。不支持非常量的谓词下推。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04730: "We only support pushing down opExpr and null test predicates."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。仅仅支持表达式和null谓词下推。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04731 - GAUSS-04740
+
+<br/>
+
+GAUSS-04731: "Data type %u has not been supported for predicate push down."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。报错的数据类型不支持动态谓词下推。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04732: "The maximum accuracy of decimal/numeric data type supported is %d bits."
+
+SQLSTATE: 0A000
+
+错误原因: decimal/numeric支持的最大进度超过规定38位。
+
+解决办法: 建表时定义decimal/numeric类型的精度小于或者等于38。
+
+GAUSS-04737: "There is an illegal character \\'%c\\' in the option %s."
+
+SQLSTATE: 44000
+
+错误原因: 在filename或者foldername的option中存在非法字符。
+
+解决办法: 检查flilename或者foldername路径的规范性，重新创建HDFS外表。
+
+GAUSS-04738: "The option %s should not be end with \\'%c\\'."
+
+SQLSTATE: 44000
+
+错误原因: 检测filename的option以'/'结束直接报错。
+
+解决办法: filename的option不能以'/'结束。
+
+<br/>
+
+## GAUSS-04741 - GAUSS-04750
+
+<br/>
+
+GAUSS-04741: "The path '%s' must be an absolute path."
+
+SQLSTATE: 42P17
+
+错误原因: 检测filename或者foldername的路径不是绝对路径。
+
+解决办法: 创建HDFS表指定的foldername或者filename必须是一个绝对路径。
+
+GAUSS-04742: "The address option exists illegal character: \\'%c\\'"
+
+SQLSTATE: 44000
+
+错误原因: HDFS的Server的address option中存在非法字符空格。
+
+解决办法: 将非法字符空格去掉。
+
+GAUSS-04744: "The count of address '%s' must be not greater than %d."
+
+SQLSTATE: 44000
+
+错误原因: address的数量不能超过2个。
+
+解决办法: 创建DFS server时指定的address不能超过两个。
+
+GAUSS-04745: "Unsupport ipv6 foramt"
+
+SQLSTATE: 44000
+
+错误原因: DFS server的address不支持ipv6格式。
+
+解决办法: 创建DFS server的address改为ipv4格式。
+
+GAUSS-04746: "The incorrect address format"
+
+SQLSTATE: 44000
+
+错误原因: address的格式书写错误。
+
+解决办法: 查看正确描述address。
+
+GAUSS-04747: "Failed to create DfsInsert handler when updating table."
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04748: "build global dfs space cache hash table failed"
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。创建全局的HDFS连接缓存失败。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04749: "The number of files exceeds the limit %d."
+
+SQLSTATE: 22000
+
+错误原因: 文件数量达到设定的上限值。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04750: "could not initialize DFS space hash table"
+
+SQLSTATE: 42704
+
+错误原因: 不能创建用于缓存文件序号的hash table。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04751 - GAUSS-04760
+
+<br/>
+
+GAUSS-04752: "could not initialize partition pruning result cache."
+
+SQLSTATE: XX000
+
+错误原因: 分区表导入过程中用以分区搜索的cache创建失败。
+
+解决办法: 检查机器是否有足够的内存来创建分区收索cache。
+
+GAUSS-04753: "Unsupported data type on column:%s when forming partition signature"
+
+SQLSTATE: XX000
+
+错误原因: 分区表导入过程中发现分区键的数据类型不在支持的类型中。
+
+解决办法: 查看系统目录表是否有数据不一致情况，以创建的分区表分区列是否是不支持的分区类型。
+
+GAUSS-04756: "could not rewind DFS Partition Loading temporary file: %m"
+
+SQLSTATE: XX000
+
+错误原因: 在分区表导入过程中，下盘缓存文件未能成功移动文件游标。
+
+解决办法: 检查下盘临时文件是否已经损坏。
+
+GAUSS-04758: "Only ORC is supported for now."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。 手册HDFS表仅支持ORC格式。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04759: "DfsStore: unrecognized heap_update status: %u"
+
+SQLSTATE: XX000
+
+错误原因: desc表的删除和更新冲突。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04760: "type '%s' is not supported in DFS ORC format column store"
+
+SQLSTATE: 0A000
+
+错误原因: 此数据类型是HDFS表不支持的。
+
+解决办法: 创建HDFS表时使用其他数据类型。
+
+<br/>
+
+## GAUSS-04761 - GAUSS-04770
+
+<br/>
+
+GAUSS-04761: "Value '%s' of option 'compression' is invalid for row table"
+
+SQLSTATE: 0A000
+
+错误原因: 行存表压缩参数指定错误。
+
+解决办法: 修正压缩参数为yes或者no。
+
+GAUSS-04762: "Invalid string for 'filesystem' option."
+
+SQLSTATE: 22023
+
+错误原因: 创建表空间时，设置的filesystem的值错误，直接报错。
+
+解决办法: 创建表空间时，设置的filesystem为general或者为hdfs。
+
+GAUSS-04764: "No storepath is specified for a DFS server."
+
+SQLSTATE: XX000
+
+错误原因: 创建HDFS表空间时没有指定storepath。
+
+解决办法: 创建HDFS表空间时指定storepath。
+
+GAUSS-04765: "current text search configuration doesnot support options"
+
+SQLSTATE: 22023
+
+错误原因: 当前的configuration不支持options。
+
+解决办法: 按照文档修改SQL语句。
+
+GAUSS-04766: "CUListWrite: Cannot allocate memory"
+
+SQLSTATE: XX000
+
+错误原因: 系统可用内存不足，申请内存失败。
+
+解决办法: 操作系统释放部分内存后，可尝试重新执行。
+
+GAUSS-04767: "could not access status of transaction %lu, nextXid is %lu"
+
+SQLSTATE: XX000
+
+错误原因: 对未存在的事务状态进行访问，可能是所访问的事务在节点上还未存在。
+
+解决办法:
+
+- 如果是主动调用访问不存在的事务的状态，无须处理。
+- 如果是一个正常的事务，节点也参与，请联系技术支持工程师提供技术支持。
+
+GAUSS-04770: "write cu failed, colid(%d) cuid(%u), offset(%lu), size(%d) : %m"
+
+SQLSTATE: XX000
+
+错误原因: 异步IO写数据文件操作异常。
+
+解决办法: 从备机或者备份数据恢复集群数据文件。
+
+<br/>
+
+## GAUSS-04771 - GAUSS-04780
+
+<br/>
+
+GAUSS-04774: "Snapshot too old."
+
+SQLSTATE: XX000
+
+错误原因: 查询的快照是旧的快照。
+
+解决办法: 可尝试重新执行。
+
+GAUSS-04778: "Unable to get store format for Dfs relation %s"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04779: "The relation '%s' has no distribute type."
+
+SQLSTATE: 0A000
+
+错误原因: 所查询的表没有分布类型，比如在CN查询desc表。
+
+解决办法: 此类表只可以在DN查询。
+
+<br/>
+
+## GAUSS-04781 - GAUSS-04790
+
+<br/>
+
+GAUSS-04781: "Upper-level GROUPING found where not expected"
+
+SQLSTATE: XX000
+
+错误原因: 上层的grouping不能存在于subplan中。
+
+解决办法: 重新写语义相同的SQL语句。
+
+GAUSS-04782: "GROUPING found where not expected"
+
+SQLSTATE: XX000
+
+错误原因: where等字句中不能含有grouping。
+
+解决办法: 请修改SQL语句。
+
+GAUSS-04783: "ORDER/GROUP BY expression not found in list"
+
+SQLSTATE: XX000
+
+错误原因: 在ORDER/GROUP BY子句中无法查找到给定的ORDER/GROUP引用。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04784: "Relation with OID %u does not exist."
+
+SQLSTATE: XX000
+
+错误原因: 所查询的表不存在。
+
+解决办法: 系统内部错误。请联系技术支持工程师提供技术支持。
+
+GAUSS-04785: "get tablespace %u store path failed"
+
+SQLSTATE: 42P01
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+AUSS-04786: "Un-support feature: HDFS"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04787: "cache lookup failed for bucket %u"
+
+SQLSTATE: 29P01
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04788: "null bucket for tuple %u"
+
+SQLSTATE: 22004
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04789: "got null for pgxc_class option %u"
+
+SQLSTATE: 29P01
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04790: "should in restore mode"
+
+SQLSTATE: 42602
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04791 - GAUSS-04800
+
+<br/>
+
+GAUSS-04791: "invalid hashbucketId syntax"
+
+SQLSTATE: 42602
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04792: "Cannot drop all buckets"
+
+SQLSTATE: D0011
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04793: "Invalid bucket id %u, max bucket id is %d"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04794: "invalid relation file path %s for relpath_parse_rnode"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04795: "Failed to write data to the dfs file list, error code: %d"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04796: "grant to public operation is forbidden in security mode"
+
+SQLSTATE: 0LP01
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04797: "Forbid grant language c to user with grant option."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04798: "Forbid grant language c to public."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04800: "Only roles with sysadmin or createdb privileges can do GRANT/REVOKE."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/49-GAUSS-04801-GAUSS-04900.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/49-GAUSS-04801-GAUSS-04900.md
new file mode 100644
index 0000000000000000000000000000000000000000..15856da84f405461e942796de6be1b75e8bb0cf8
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/49-GAUSS-04801-GAUSS-04900.md
@@ -0,0 +1,844 @@
+---
+title: GAUSS-04801 - GAUSS-04900
+summary: GAUSS-04801 - GAUSS-04900
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-04801 - GAUSS-04900
+
+<br/>
+
+## GAUSS-04801 - GAUSS-04810
+
+<br/>
+
+GAUSS-04803: "cache lookup failed for data source %u"
+
+SQLSTATE: 29P01
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04804: "computing nodegroup is not a valid group."
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04805: "directory with OID %u does not exist"
+
+SQLSTATE: 42704
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04807: "data source with OID %u does not exist"
+
+SQLSTATE: 42704
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04808: "synonym with OID %u does not exist"
+
+SQLSTATE: 42704
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04809: "Invalid Oid of local index %u on the partition %u."
+
+SQLSTATE: 42704
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04810: "cache lookup failed for directory %u"
+
+SQLSTATE: 29P01
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04811 - GAUSS-04820
+
+<br/>
+
+GAUSS-04811: "could not find tuple for policy %u"
+
+SQLSTATE: 42704
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04812: "cache lookup failed for synonym %u"
+
+SQLSTATE: 29P01
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04813: "Create hash table directly on DN is not allowed."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04814: "Create hash table but there is no valid PGXCBucketMap."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04815: "Invalid BucketMap or wrong NodeId(%d)"
+
+SQLSTATE: 42P16
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04816: "distributeby no hash is invalid with hashbucket"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04817: "Temp tables are invalid because datanode %s restart. Quit your session to clean invalid temp tables."
+
+SQLSTATE: 42P18
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04818: "u_sess->parser_cxt.param_info should not be NULL"
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04819: "partition name is invalid"
+
+SQLSTATE: 23502
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04820: "null partition key value for relation '%s' in check partkey type."
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04821 - GAUSS-04830
+
+<br/>
+
+GAUSS-04821: "partition key column's number of relation '%s' is not a 1-D smallint array in check partkey type."
+
+SQLSTATE: XX001
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04822: "Object in DEFAULT constraints of column '%s' doesn't exists"
+
+SQLSTATE: 42P02
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04823: "Object in CHECK constraints doesn't exists"
+
+SQLSTATE: 42P02
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04824: "Using CREATE SYNONYM is forbidden in template database."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04825: "synonym '%s' already exists"
+
+SQLSTATE: 42710
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04826: "synonym '%s' does not exist"
+
+SQLSTATE: 42704
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04827: "permission denied to change owner of synonym '%s'"
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04828: "must be initial user"
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04829: "initialize the built-in function failed: %s"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04830: "user-defined indexes on value partition columns are not supported"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04831 - GAUSS-04840
+
+<br/>
+
+GAUSS-04831: "unexpected non-btree speculative unique index"
+
+SQLSTATE: 55000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04832: "resource pool %u was concurrently dropped"
+
+SQLSTATE: 42704
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04833: "multiple pg_shdepend entries: object %u/%u/%u/%d, deptype %c"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04834: "multiple pg_shdepend entries for object %u/%u/%u/%d deptype %c"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04835: "no pg_shdepend entry: object %u/%u/%u/%d, deptype %c"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04836: "Sync failed because there is data inside the delta table %d."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04837: "the current function does not support non-column-store table"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04838: "Function pg_sync_all_cstore_delta doest not support to run on DN."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04839: "enum label '%s' already exists"
+
+SQLSTATE: 42710
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04840: "pg_enum OID value not set when in binary upgrade mode"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04841 - GAUSS-04850
+
+<br/>
+
+GAUSS-04841: "cache lookup failed for existing[%d]!"
+
+SQLSTATE: 29P01
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04842: "can't find installation-group."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04843: "AlTER TABLE ADD/DELETE NODE can only be altered up-to installation group."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04844: "Temp namespace %s not found in pg_namespace. "
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04845: "bogus PopOverrideSearchPath call, stack level %d, xact level %d"
+
+SQLSTATE: XX006
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04846: "Failed to set temp namespace."
+
+SQLSTATE: YY005
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04847: "Can't get nodeoid for relation %d"
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04848: "Temp table's data is invalid because datanode %s restart. Quit your session to clean invalid temp tables."
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04849: "Submit or Isubmit job only can be operate on coordinator."
+
+SQLSTATE: 42704
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04850: "Can not find job id %d in system table pg_job."
+
+SQLSTATE: 42704
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04851 - GAUSS-04860
+
+<br/>
+
+GAUSS-04851: "Permission for current user to get this job. current_user: %s, job_user: %s, job_id: %ld"
+
+SQLSTATE: 42704
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04852: "Can not find jobid %d in system table pg_job_proc."
+
+SQLSTATE: 42704
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04853: "Invalid job status, job_id: %d."
+
+SQLSTATE: 20000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04854: "Invalid job_id: %ld"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04855: "Invalid job_status: \\'%c\\' "
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04856: "Unable to connect to execute internal query, job_id: %d."
+
+SQLSTATE: SP001
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04857: "Call SPI_execute execute job interval fail, job_id: %d."
+
+SQLSTATE: SP005
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04858: "Execute job interval for get next_date error, job_id: %d."
+
+SQLSTATE: SP000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04859: "Interval: %s must evaluate to a time in the future for job_id: %d."
+
+SQLSTATE: 29000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04860: "It is invalid job interval for the reason that it is a fixed timestamp, job_id: %d, interval: %s."
+
+SQLSTATE: 29000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04861 - GAUSS-04870
+
+<br/>
+
+GAUSS-04861: "Execute job failed, job_id: %d."
+
+SQLSTATE: OP001
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04862: "Invalid parameter interval: \\'%s\\'."
+
+SQLSTATE: 55000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04863: "Parameter what can not be null."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04864: "Parameter next date can not be null."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04865: "All 32768 jobids have alloc, and there is no free jobid"
+
+SQLSTATE: 55000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04866: "only system/monitor admin can submit multi-node jobs!"
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04867: "Parameter node_name can not be null."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04868: "Parameter node_name can only be 'ALL_NODE' for multi-node jobs."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04869: "Parameter Database can not be null."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04870: "Parameter Database can only be 'postgres'."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04871 - GAUSS-04880
+
+<br/>
+
+GAUSS-04871: "Parameter can not be null."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04872: "Invalid job_id: %d"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04873: "Remove jobid:%ld failed."
+
+SQLSTATE: 55000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04874: "can not find jobid in the job queue %d"
+
+SQLSTATE: 55000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04875: "Parameter id for job_update is unexpected."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04876: "Permission for current user to operate the job. current_user: %s, job_user: %s, job_id: %ld"
+
+SQLSTATE: D0011
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04877: "Can not operate this job due to running status, job_id: %ld. "
+
+SQLSTATE: 29000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04878: "File '%s' does not exist."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04879: "Library File '%s' does not have READ permission."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04880: "Library path can not include character %c."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04881 - GAUSS-04890
+
+<br/>
+
+GAUSS-04881: "Library file name can not include character '%c'."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04882: "Copy file '%s' failed: %m"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04883: "Send library to all node fail: %m, command %s"
+
+SQLSTATE: 58000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04884: "Send library to backup fail: %m, command %s"
+
+SQLSTATE: 58000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04885: "Library file '%s' does not exist."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04886: "abort transaction due to concurrent create function."
+
+SQLSTATE: 40001
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04887: "Invalid library path."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04888: "Do not allow package function overload not package function."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04889: "function '%s' is a builtin function,it can not be changed"
+
+SQLSTATE: 42P13
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04890: "can not get current user name."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04891 - GAUSS-04900
+
+<br/>
+
+GAUSS-04891: "package function does not support table parameter."
+
+SQLSTATE: 42P13
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04892: "package function does not support variadic parameter."
+
+SQLSTATE: 42P13
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04893: "Do not allow package function replace not package function."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04894: "Package function does not support function overload which has the same type argument."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04895: "File path can not include character '%c'"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04896: "couldn't get database name"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04897: "out of binary heap slots"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04898: "doubly linked list head address is NULL"
+
+SQLSTATE: 23502
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04899: "doubly linked list is corrupted."
+
+SQLSTATE: XX001
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04900: "singly linked list head address is NULL"
+
+SQLSTATE: 23502
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/5-GAUSS-00401-GAUSS-00500.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/5-GAUSS-00401-GAUSS-00500.md
new file mode 100644
index 0000000000000000000000000000000000000000..ad65b4d26c708a4394c75dec64e77e77d734973d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/5-GAUSS-00401-GAUSS-00500.md
@@ -0,0 +1,692 @@
+---
+title: GAUSS-00401 - GAUSS-00500
+summary: GAUSS-00401 - GAUSS-00500
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-00401 - GAUSS-00500
+
+<br/>
+
+## GAUSS-00401 - GAUSS-00410
+
+<br/>
+
+### GAUSS-00401: "access method 'psort' does not support index expressions"
+
+SQLSTATE: 0A000
+
+错误原因: 在CREATE INDEX或ALTER TABLE语法中INDEX子句中指定的访问方式如果为psort时，INDEX子句中不支持表达式。
+
+解决办法: 在CREATE INDEX或ALTER TABLE语法中INDEX子句中指定的访问方式如果为psort时，请检查INDEX子句中是否存在表达式，并修改语法。
+
+### GAUSS-00402: "Partition key value can not be null"
+
+SQLSTATE: 42601
+
+错误原因: 创建范围分区表时，通过PARTATION BY RANGE （partition_key）(range_partition_definition_list)指定的分区键值不能为空。
+
+解决办法: 请检查创建范围分区表时，通过PARTATION BY RANGE （partition_key）指定的分区键是否为空，并增加有效的分区键值。
+
+### GAUSS-00403: "partition key value must be const or const-evaluable expression"
+
+SQLSTATE: 42601
+
+错误原因: 创建范围分区表时，通过PARTATION BY RANGE （partition_key）(range_partition_definition_list)指定的分区键值不可度量。
+
+解决办法: 创建范围分区表时，通过PARTATION BY RANGE （partition_key）(range_partition_definition_list)指定的分区键值时，需要保证分区键值必须为可度量的常量或常量表达式。
+
+### GAUSS-00404: "argument name '%s' used more than once"
+
+SQLSTATE: 42601
+
+错误原因: 语法错误，参数名重名。
+
+解决办法: 修改重名的参数名。
+
+### GAUSS-00405: "positional argument cannot follow named argument"
+
+SQLSTATE: 42601
+
+错误原因: 语法错误，位置参数不能再命名参数之后。
+
+解决办法: 修改参数位置。
+
+### GAUSS-00406: "%s(*) specified, but %s is not an aggregate function"
+
+SQLSTATE: 42809
+
+错误原因: 指定了%s(*)，但是函数却不是聚集函数。
+
+解决办法: 选择一个有效的聚集函数。
+
+### GAUSS-00407: "DISTINCT specified, but %s is not an aggregate function"
+
+SQLSTATE: 42809
+
+错误原因: 指定了DISTINCT，但是函数却不是聚集函数。
+
+解决办法: 选择一个有效的聚集函数。
+
+### GAUSS-00408: "ORDER BY specified, but %s is not an aggregate function"
+
+SQLSTATE: 42809
+
+错误原因: 指定了ORDER BY，但是函数却不是聚集函数。
+
+解决办法: 选择一个有效的聚集函数。
+
+### GAUSS-00409: "OVER specified, but %s is not a window function nor an aggregate function"
+
+SQLSTATE: 42809
+
+错误原因: 指定了OVER，但是函数却不是窗口函数或者聚集函数。
+
+解决办法: 选择一个有效的窗口函数或聚集函数。
+
+### GAUSS-00410: "function %s is not unique"
+
+SQLSTATE: 42725
+
+错误原因: 函数不唯一。
+
+解决办法: 增加精确的类型转换来选择一个最佳的函数。
+
+<br/>
+
+## GAUSS-00411 - GAUSS-00420
+
+<br/>
+
+### GAUSS-00411: "function %s does not exist"
+
+SQLSTATE: 42883
+
+错误原因: 函数不存在。
+
+解决办法: 检查是否已定义需要用到的函数。
+
+### GAUSS-00412: "%s(*) must be used to call a parameterless aggregate function"
+
+SQLSTATE: 42809
+
+错误原因: 在创建函数或表达式为聚合函数时聚合函数的参数为空但不为"*"。
+
+解决办法: 在创建函数或表达式为聚合函数，需要确认如果聚合函数的参数为空，那么参数必须为星号"*"。
+
+### GAUSS-00413: "aggregates cannot return sets"
+
+SQLSTATE: 42P13
+
+错误原因: 创建函数或表达式为聚合函数时聚合函数不能返回了集合类型。
+
+解决办法: 创建函数或表达式为聚合函数时，聚合函数不能返回集合类型，请确认聚合函数的返回类型是否正确，并修改为非集合类型。
+
+### GAUSS-00414: "aggregates cannot use named arguments"
+
+SQLSTATE: 0A000
+
+错误原因: 调用函数或表达式为聚合函数时聚合函数参数错误使用了参数名称。
+
+解决办法: 调用函数或表达式为聚合函数时聚合函数参数不能指定为参数名称，必须要使用有效值。
+
+### GAUSS-00415: "window function call requires an OVER clause"
+
+SQLSTATE: 42809
+
+错误原因: 调用函数或表达式为窗口函数时，OVER子句未定义。
+
+解决办法: 调用函数或表达式为窗口函数时，该窗口函数必须使用OVER子句定义，请检查并修改语法。
+
+### GAUSS-00416: "DISTINCT is not implemented for window functions"
+
+SQLSTATE: 0A000
+
+错误原因: 调用函数或表达式为窗口函数时，该窗口函数存在DISTINCT子句。
+
+解决办法: 调用函数或表达式为窗口函数时，窗口函数中不能包含DISTINCT子句，请检查并修改语法。
+
+### GAUSS-00417: "aggregate ORDER BY is not implemented for window functions"
+
+SQLSTATE: 0A000
+
+错误原因: 调用函数或表达式为窗口函数时，该窗口函数存在ORDER BY子句。
+
+解决办法: 调用函数或表达式为窗口函数时，窗口函数中不能包含ORDER BY子句，请检查并修改语法。
+
+### GAUSS-00418: "window functions cannot return sets"
+
+SQLSTATE: 42P13
+
+错误原因: 创建函数或表达式为窗口函数时，该窗口函数不能返回集合类型。
+
+解决办法: 创建函数或表达式为窗口函数时，窗口函数不能返回集合类型，请确认窗口函数的返回类型是否正确，并修改为非集合类型。
+
+### GAUSS-00419: "window functions cannot use named arguments"
+
+SQLSTATE: 0A000
+
+错误原因: 窗口函数为函数或表达式时，参数不能使用参数名称，必须使用参数的值。
+
+解决办法: 调用函数或表达式为窗口函数时，窗口函数参数不能指定为参数名称，必须要使用有效值。
+
+### GAUSS-00420: "not enough default arguments"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-00421 - GAUSS-00430
+
+<br/>
+
+### GAUSS-00421: "function %s asks parameters"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00422: "aggregate %s(*) does not exist"
+
+SQLSTATE: 42883
+
+错误原因: 聚合函数的参数无效。
+
+解决办法: 请检查确认聚合函数的参数数目是否为0。
+
+### GAUSS-00423: "aggregate %s does not exist"
+
+SQLSTATE: 42883
+
+错误原因: 无效的聚合函数。
+
+解决办法: 请检查确认聚合函数是否在pg_proc表中存在。
+
+### GAUSS-00424: "function %s is not an aggregate"
+
+SQLSTATE: 42809
+
+错误原因: 创建的函数不是有效的聚合函数。
+
+解决办法: 请确认函数是否为聚合函数，使用"（*）"作为参数的必须为聚合函数。
+
+### GAUSS-00426: "inconsistent types deduced for parameter $%d"
+
+SQLSTATE: 42P08
+
+错误原因: 不支持的用法。
+
+解决办法: 修改SQL Statement。
+
+### GAUSS-00427: "could not determine data type of parameter $%d"
+
+SQLSTATE: 42P08
+
+错误原因: 参数类型无法确定。
+
+解决办法: 修改参数值为系统可识别的类型，系统可识别类型见zh-cn_topic_0237121926.html。
+
+### GAUSS-00428: "could not create syslogger data transfer thread: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00429: "could not create pipe for syslog: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00430: "could not redirect stdout: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-00431 - GAUSS-00440
+
+<br/>
+
+### GAUSS-00431: "could not redirect stderr: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00432: "checkpoint request failed"
+
+SQLSTATE: XX000
+
+错误原因: checkpoint内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00433: "ForwardFsyncRequest must not be called in checkpointer"
+
+SQLSTATE: XX000
+
+错误原因: checkpoint内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00434: "could not open archive status directory '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00435: "no free worker found"
+
+SQLSTATE: XX000
+
+错误原因: 目前没有可用的清理线程两阶段提交事务。
+
+解决办法: 将GUC参数autovacuum_max_workers调大。
+
+### GAUSS-00436: "cache lookup failed for database %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00437: "the options of -M is not recognized"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00438: "-%s requires a value"
+
+SQLSTATE: 42601
+
+错误原因: 使用命令时指定了某个参数，但没有指定该参数对应的值。
+
+解决办法: 使用命令时如果指定了某个需要有值的参数，则需要指定该参数对应的值。
+
+### GAUSS-00439: "-c %s requires a value"
+
+SQLSTATE: 42601
+
+错误原因: 使用命令时指定了某个参数，但没有指定该参数对应的值。
+
+解决办法: 使用命令时如果指定了某个需要有值的参数，则需要指定该参数对应的值。
+
+### GAUSS-00440: "invalid list syntax for 'listen_addresses'"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-00441 - GAUSS-00450
+
+<br/>
+
+### GAUSS-00442: "could not create any TCP/IP sockets"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00444: "no socket created for listening"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00445: "could not create I/O completion port for child queue"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00446: "could not load pg_hba.conf"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00447: "%s: could not locate my own executable path"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00448: "%s: could not locate matching postgres executable"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00449: "could not open directory '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 打开某个目录失败，可能原因是目录不存在，权限不对，或目录损坏。
+
+解决办法: 可根据错误信息分析具体原因，如果目录不存在，需要创建对应目录；权限不对则修改权限；目录损坏则修复文件系统或磁盘。
+
+### GAUSS-00450: "data directory '%s' does not exist"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-00451 - GAUSS-00460
+
+<br/>
+
+### GAUSS-00451: "could not read permissions of directory '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00452: "specified data directory '%s' is not a directory"
+
+SQLSTATE: 55000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00453: "data directory '%s' has wrong ownership"
+
+SQLSTATE: 55000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00454: "data directory '%s' has group or world access"
+
+SQLSTATE: 55000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00457: "hot standby is not possible because wal_level was not set to 'hot_standby'"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00458: "when starting as dual mode, we must ensure wal_level was not 'minimal' and max_wal_senders was set at least 1"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-00461 - GAUSS-00470
+
+<br/>
+
+### GAUSS-00466: "sorry, too many clients already"
+
+SQLSTATE: 53300
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-00471 - GAUSS-00480
+
+<br/>
+
+### GAUSS-00474: "fcntl F_GETFD failed!"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00475: "fcntl F_SETFD failed!"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00476: "could not set timer for startup packet timeout"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00477: "could not disable timer for startup packet timeout"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00478: "out of memory"
+
+SQLSTATE: 53200
+
+错误原因: 无法申请内存。
+
+解决办法: 请检查系统看是否有足够的内存。
+
+<br/>
+
+## GAUSS-00481 - GAUSS-00490
+
+<br/>
+
+### GAUSS-00481: "parameter error in ParseHaListenAddr()"
+
+SQLSTATE: XX000
+
+错误原因: ParseHaListenAddr函数参数错误。
+
+解决办法: 检查传入参数为何为空指针。
+
+### GAUSS-00482: "must be system admin to reset statistics counters"
+
+SQLSTATE: 42501
+
+错误原因: 系统管理员才能重置统计计数。
+
+解决办法: 切换数据库用户为系统管理员。
+
+### GAUSS-00483: "unrecognized reset target: '%s'"
+
+SQLSTATE: 22023
+
+错误原因: 重置目标参数错误。
+
+解决办法: 参数必须为bgwriter。
+
+### GAUSS-00484: "could not read statistics message: %m"
+
+SQLSTATE: XX000
+
+错误原因: pgStat读入统计消息出错。
+
+解决办法: 数据库内部线程通信出错，请联系技术支持工程师提供技术支持。
+
+### GAUSS-00485: "database hash table corrupted during cleanup - abort"
+
+SQLSTATE: XX000
+
+错误原因: 数据库在清理过程中哈希表损坏。
+
+解决办法: 数据库内部错误，请联系技术支持工程师提供技术支持。
+
+### GAUSS-00486: "could not create sysauditor data transfer thread: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00487: "could not create pipe for sysaudit: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00488: "could not write to audit file: %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00489: "set-valued function called in context that cannot accept a set"
+
+SQLSTATE: 0A000
+
+错误原因: 返回结果集的函数不能返回结果集。
+
+解决办法: 检查函数定义是否支持返回结果集。
+
+### GAUSS-00490: "materialize mode required, but it is not allowed in this context"
+
+SQLSTATE: 0A000
+
+错误原因: 返回tuplestore在当前上下文不支持。
+
+解决办法: 修改返回值类型。
+
+<br/>
+
+## GAUSS-00491 - GAUSS-00500
+
+<br/>
+
+### GAUSS-00491: "return type must be a row type"
+
+SQLSTATE: XX000
+
+错误原因: 构建的元组描述符不是一个行结果信息。
+
+解决办法: 重新执行查询，如果仍然是报错，请联系技术支持工程师提供技术支持。
+
+### GAUSS-00492: "attribute count of the return row type not matched"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00493: "permission denied to query audit"
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00494: "permission denied to delete audit"
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00495: "conflicting or redundant options"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00496: "option '%s' not recognized"
+
+SQLSTATE: XX000
+
+错误原因: 不识别copy中某个选项的值。
+
+解决办法: 检查copy中该不识别的参数是否正确。
+
+### GAUSS-00497: "%d is not a valid encoding code"
+
+SQLSTATE: 42704
+
+错误原因: 将字符串转换为ASCII编码格式时，未使用指定的编码标识符。
+
+解决办法: 将字符串转换为ASCII编码格式时，请确认使用指定的编码标识符编号必须小于42。
+
+### GAUSS-00498: "%s is not a valid encoding name"
+
+SQLSTATE: 42704
+
+错误原因: 将字符串转换为ASCII编码格式时，使用的字符编码名无效。
+
+解决办法: "将字符串转换为ASCII编码格式时，请确认使用指定的编码标识符名必须为以下列表中的有效名称。
+
+### GAUSS-00500: "permission denied to create database"
+
+SQLSTATE: 42501
+
+错误原因: 当前用户角色没有权限创建数据库。
+
+解决办法: 只有拥有CREATEDB权限的用户或系统管理员才可以创建新数据库，请确认用户权限是否正确。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/50-GAUSS-04901-GAUSS-05000.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/50-GAUSS-04901-GAUSS-05000.md
new file mode 100644
index 0000000000000000000000000000000000000000..2972b364f3762ed75c2d0524f0a469cbdd6d6212
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/50-GAUSS-04901-GAUSS-05000.md
@@ -0,0 +1,860 @@
+---
+title: GAUSS-04901 - GAUSS-05000
+summary: GAUSS-04901 - GAUSS-05000
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-04901 - GAUSS-05000
+
+<br/>
+
+## GAUSS-04901 - GAUSS-04910
+
+<br/>
+
+GAUSS-04901: "pg_hba.conf rejects replication connection for host '%s', user '%s', %s"
+
+SQLSTATE: 28000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04902: "pg_hba.conf rejects replication connection for host '%s', user '%s'"
+
+SQLSTATE: 28000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04903: "no pg_hba.conf entry for replication connection from host '%s', user '%s', %s"
+
+SQLSTATE: 28000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04904: "no pg_hba.conf entry for replication connection from host '%s', user '%s'"
+
+SQLSTATE: 28000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04905: "Forbid remote connection with initial user."
+
+SQLSTATE: 28000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04906: "Failed to Generate the random number,errcode:%d"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04907: "Failed to Generate the fake salt"
+
+SQLSTATE: 28000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04908: "Failed to Generate the random serverkey,errcode:%d"
+
+SQLSTATE: 28000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04909: "Failed to Generate the random storedkey,errcode:%d"
+
+SQLSTATE: 28000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04910: "GSS authentication method is not allowed because %s user password is not disabled."
+
+SQLSTATE: 28000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04911 - GAUSS-04920
+
+<br/>
+
+GAUSS-04911: "empty password returned by client"
+
+SQLSTATE: 28P01
+
+错误原因:  客户端返回的密码为空。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04912: "Could not get user information on this platform"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04913: "could not look up local user ID %ld: %s"
+
+SQLSTATE: D0011
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04914: "could not create SSL context : %s.)"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04915: "certificate file '%s' has group or world access"
+
+SQLSTATE: F0000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04916: "ca certificate file '%s' has group or world access"
+
+SQLSTATE: F0000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04917: "DH: generating parameters (3072 bits) failed"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04918: "Last read message sequence %u is not equal to the max written message sequence %u"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04919: "alert, failed in revert command buffer, invalid params data len %d pq buffer size %d"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04920: "expected message sequnce is %d, actual message sequence is %d"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04921 - GAUSS-04930
+
+<br/>
+
+GAUSS-04921: "expected message length is %d, actual message length is %d"
+
+SQLSTATE: 22026
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04922: "expected crc is %u, actual crc is %u"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04923: "varno is unvalid"
+
+SQLSTATE: 无n
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04924: "name for %s %u not found"
+
+SQLSTATE: 29P01
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04925: "namespace for %s %u not found"
+
+SQLSTATE: 29P01
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04926: "seqname of nextval() is not found"
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04927: "token should not return NULL."
+
+SQLSTATE: 22004
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04928: "incomplete array structure"
+
+SQLSTATE: 2202E
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04929: "unterminated array structure"
+
+SQLSTATE: 2202E
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04930: "NULL seqName for nextval()"
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04931 - GAUSS-04940
+
+<br/>
+
+GAUSS-04931: "NULL seqNamespace for nextval()"
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04932: "_readConstraint(): badly contype '%s'…"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04933: "expected '[' to start datum, but got '%s'; length = %lu"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04934: "WITHIN GROUP specified, but %s is not an aggregate function"
+
+SQLSTATE: 42809
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04935: "WITHIN GROUP is required for ordered-set aggregate %s"
+
+SQLSTATE: 42809
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04936: "OVER is not supported for ordered-set aggregate %s"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04937: "DISTINCT + WITHIN GROUP is not supported for ordered-set aggregate %s"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04938: "VARIADIC + WITHIN GROUP is not supported for ordered-set aggregate %s"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04939: "%s is not an ordered-set aggregate, so it cannot have WITHIN GROUP"
+
+SQLSTATE: 42809
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04940: "window function %s requires an OVER clause"
+
+SQLSTATE: 42809
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04941 - GAUSS-04950
+
+<br/>
+
+GAUSS-04941: "window function %s cannot have WITHIN GROUP"
+
+SQLSTATE: 42809
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04942: "window functions cannot allow multiple different order info"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04943: "Operator '(+)' can only be used in WhereClause of Select-Statement or Subquery."
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04944: "column reference '%s' is ambiguous."
+
+SQLSTATE: 42702
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04945: "name data must be quoted"
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04946: "REBUILD is not supported for multiple commands"
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04947: "IF EXISTS is not supported for REBUILD"
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04948: "Must use single quoted string for '%s' option."
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04949: "Row Level Security is not yet supported for INSERT and MERGE"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04950: "unrecognized row security option '%s'"
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04951 - GAUSS-04960
+
+<br/>
+
+GAUSS-04951: "WITH GRANT OPTION is not supported in security mode."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04952: "FENCED mode function is not yet supported in current version."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04953: "COMPACT can only be used with VACUUM FULL"
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04954: "COMPACT can not be used with FREEZE"
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04955: "COMPACT can not be used with PARTITION"
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04956: "COMPACT can not be used with ANALYZE"
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04957: "RETURNING clause is not yet supported whithin INSERT ON DUPLICATE KEY UPDATE statement."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04958: "WITH clause is not yet supported whithin INSERT ON DUPLICATE KEY UPDATE statement."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04959: "Subfield name or array subscript of column '%s' is not yet supported whithin INSERT ON DUPLICATE KEY UPDATE statement."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04960: "Update with subquery is not yet supported whithin INSERT ON DUPLICATE KEY UPDATE statement."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04961 - GAUSS-04970
+
+<br/>
+
+GAUSS-04961: "only allow column name within VALUES"
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04962: "missing WITHIN keyword."
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04963: "cannot use multiple ORDER BY clauses with WITHIN GROUP."
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04964: "cannot use DISTINCT with WITHIN GROUP."
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04965: "cannot use VARIADIC with WITHIN GROUP."
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04966: "cannot use multiple ORDER BY clauses with WITHIN GROUP"
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04967: "cannot use DISTINCT with WITHIN GROUP"
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04968: "cannot use VARIADIC with WITHIN GROUP"
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04969: "timestampdiff syntax is not supported."
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04970: "type modifier cannot have ORDER BY"
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04971 - GAUSS-04980
+
+<br/>
+
+GAUSS-04971: "No function matches the given arguments names. You might need to add explicit declare arguments names."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04972: "argname should not be null"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04974: "must be system admin or monitor admin to use EXECUTE DIRECT"
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04975: "Unsupported typeoid: %d for T_Integer value, please add single quota and try again."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04976: "pstate->p_target_relation is NULL unexpectedly"
+
+SQLSTATE: 22004
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04977: "tupleDesc should not be null"
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04978: "It is forbidden to use placeholder and dollar quoting together."
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04979: "type '%s' must be in installation group"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04980: "Date type is unsupported for hdfs table in TD-format database."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04981 - GAUSS-04990
+
+<br/>
+
+GAUSS-04981: "u_sess->parser_cxt.opr_cache_hash should not be null"
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04982: "OprCacheHash is unexpected null"
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04983: "relation '%s.%s' does not exist on%s %s"
+
+SQLSTATE: 42P01
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04984: "relation '%s' does not exist on%s %s"
+
+SQLSTATE: 42P01
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04985: "pstate can not be NULL"
+
+SQLSTATE: 22004
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04986: "permission denied to select from foreign table in security mode"
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04987: "relation '%s' does not have hash buckets"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04988: "Do not support create table with INERNAL DATA clause."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04989: "It's not supported to create serial column on temporary table"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04990: "It's not supported to alter table add serial column"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-04991 - GAUSS-05000
+
+<br/>
+
+GAUSS-04991: "CREATE TABLE LIKE with column sequence in different NodeGroup is not supported."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04992: "Table %s.%s does not exist in current datanode."
+
+SQLSTATE: 42P01
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04993: "timeseries store does not support add index "
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04994: "Unsupport cgin index in this version"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04995: "access method '%s' does not support row store"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04996: "access method '%s' does not support dfs store"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04997: "permission denied to alter foreign table in security mode"
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04998: "split partition '%s' does not exist."
+
+SQLSTATE: 42P01
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-04999: "access method 'cbtree' does not support WHERE clause"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05000: "access method 'cbtree' does not support index expressions"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/51-GAUSS-05001-GAUSS-05100.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/51-GAUSS-05001-GAUSS-05100.md
new file mode 100644
index 0000000000000000000000000000000000000000..49b280f024cd077298c41fe5b55cb0b07c03e7bf
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/51-GAUSS-05001-GAUSS-05100.md
@@ -0,0 +1,868 @@
+---
+title: GAUSS-05001 - GAUSS-05100
+summary: GAUSS-05001 - GAUSS-05100
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-05001 - GAUSS-05100
+
+<br/>
+
+## GAUSS-05001 - GAUSS-05010
+
+<br/>
+
+GAUSS-05001: "access method 'cgin' does not support WHERE clause"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05002: "access method 'cgin' does not support null text search parser"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05003: "It is not allowed to support 'NOT ENFORCED' informational constraint."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05004: "The foreign table only support 'NOT ENFORCED' informational constraint."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05005: "Only the primary key, unique, not null and null be supported."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05006: "CAN NOT get detail info from a NON-PARTITIONED relation."
+
+SQLSTATE: 42P17
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05007: "CAN NOT get detail info from a partitioned relation WITHOUT specified partition."
+
+SQLSTATE: 42P17
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05008: "CAN NOT get partition oid from a NON-PARTITIONED relation."
+
+SQLSTATE: 42P17
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05009: "start/end/every value must be an const-integer for partition '%s'"
+
+SQLSTATE: 42P16
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05010: "unexpected parameter for precheck start/end defstate."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05011 - GAUSS-05020
+
+<br/>
+
+GAUSS-05011: "partition parameter is not constant."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05012: "start value must be less than end value for partition '%s'."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05013: "ambiguous partition rule is raised by EVERY parameter in partition '%s'."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05014: "partition step is too small for partition '%s'."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05015: "partition step is too big for partition '%s'."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05016: "too many partitions after split partition '%s'."
+
+SQLSTATE: 42P16
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05017: "partition '%s' is invalid."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05018: "unsupported datatype served as a partition key in the start/end clause."
+
+SQLSTATE: 42804
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05019: "start value of partition '%s' is too low."
+
+SQLSTATE: 42P16
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05020: "partitioned table has too many partition keys."
+
+SQLSTATE: 42P16
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05021 - GAUSS-05030
+
+<br/>
+
+GAUSS-05021: "too many partition keys for partition '%s'."
+
+SQLSTATE: 42P16
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05022: "datatype of column '%s' is unsupported for partition key in start/end clause."
+
+SQLSTATE: 42804
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05023: "can not add more partitions as partition number is already at its maximum."
+
+SQLSTATE: 42804
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05024: "partition '%s' is not allowed behind MAXVALUE."
+
+SQLSTATE: 42P16
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05025: "start value of partition '%s' is too high."
+
+SQLSTATE: 42P16
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05026: "start value can not be MAXVALUE for partition '%s'."
+
+SQLSTATE: 42P16
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05027: "start value of partition '%s' NOT EQUAL up-boundary of last partition."
+
+SQLSTATE: 42P16
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05028: "end value of partition '%s' is too low."
+
+SQLSTATE: 42P16
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05029: "partition '%s' is an invalid definition clause."
+
+SQLSTATE: 42P16
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05030: "start value of partition '%s' MUST be less than up-boundary of the partition to be splitted."
+
+SQLSTATE: 42P16
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05031 - GAUSS-05040
+
+<br/>
+
+GAUSS-05031: "end value of partition '%s' NOT EQUAL up-boundary of the partition to be splitted."
+
+SQLSTATE: 42P16
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05032: "duplicate partition name: '%s'."
+
+SQLSTATE: 42710
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05033: "Not specify 'INCLUDING PARTITION' for partitioned-table relation:'%s'"
+
+SQLSTATE: 42809
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05034: "check failure with rt_fetch function"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05035: "permission denied to insert into foreign table in security mode"
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05036: "Invalid tablesample method %s"
+
+SQLSTATE: 42704
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05037: "tablesample method %s requires %d argument, not %d"
+
+SQLSTATE: 42809
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05038: "TABLESAMPLE clause can only be applied to tables."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05039: "TABLESAMPLE clause only support relation of oriented-row and oriented-column."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05040: "Cannot find expected NOT MATCHED WHEN clause with operator INSERT."
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05041 - GAUSS-05050
+
+<br/>
+
+GAUSS-05041: "Subquery should at least have a target list or values list."
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05042: "Default column should have default values."
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05043: "Expression whitin primary key or unique index are not supported yet."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05044: "Should not specify INSERT target columns in DEFAULT VALUES."
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05045: "pstate->p_target_relation should not be null"
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05046: "internal relation doesn't allow %s"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05047: "Target relation type is not supported for %s"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05048: "unknown action in MERGE WHEN clause"
+
+SQLSTATE: XX006
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05049: "unreachable WHEN clause specified after unconditional WHEN clause"
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05050: "Two WHEN MATCHED clauses are not supported for MERGE INTO"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05051 - GAUSS-05060
+
+<br/>
+
+GAUSS-05051: "Two WHEN NOT MATCHED clauses are not supported for MERGE INTO"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05052: "Invalid column reference in the UPDATE target values"
+
+SQLSTATE: 42703
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05053: "failed to transform InsertStmt for INSERT ON DUPLICATE KEY UPDATE statement."
+
+SQLSTATE: XX006
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05054: "Columns referenced in the primary or unique index cannot be updated: '%s'.'%s'"
+
+SQLSTATE: 42P10
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05055: "Columns referenced in the ON Clause cannot be updated: '%s'.'%s'"
+
+SQLSTATE: 42P10
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05056: "Replicate table only allows to INSERT static values from a VALUES clause in INSERT … ON DUPLICATE KEY UPDATE."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05057: "It is not allowed to use %s on the replicate table (%s) with column (%s) of unstable default value."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05058: "Subquery in WHERE clauses are not yet supported for %s"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05059: "Subquery in INSERT/UPDATE clauses are not yet supported for %s"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05060: "System Column reference are not yet supported for %s"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05061 - GAUSS-05070
+
+<br/>
+
+GAUSS-05061: "Subquery should at least have a target column."
+
+SQLSTATE: 42703
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05062: "Unexpected Node type '%s'"
+
+SQLSTATE: XX004
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05063: "Invalid column reference in the INSERT VALUES Clause"
+
+SQLSTATE: 42703
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05064: "aggregates not allowed in FROM clause"
+
+SQLSTATE: 42803
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05065: "unexpected args inside agg direct args"
+
+SQLSTATE: 42P25
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05066: "functions can have at most %d parameters"
+
+SQLSTATE: 54000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05067: "Operator '(+)' unknown node detected in %s()"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05068: "Relation can't outer join with each other."
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05069: "'%s' can't outer join with more than one relation."
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05070: "Operator '(+)' can't be specified on more than one relation in one join condition"
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05071 - GAUSS-05080
+
+<br/>
+
+GAUSS-05071: "'%s' can't outer join with more than one relation"
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05072: "Operator '(+)' and Join in FromClause can't be used together"
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05073: "Operator '(+)' is not allowed used with 'OR' together"
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05074: "Operator '(+)' transform failed."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05075: "'%s' is not allowed to outer join with itself."
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05076: "Operator '(+)' can not be used in outer join with SubQuery."
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05077: "Operator '(+)' can not be used in nesting expression."
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05078: "unrecognized A_Expr kind: %d used"
+
+SQLSTATE: XX004
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05079: "INSERT ON DUPLICATE KEY UPDATE is not supported on column orientated table."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05080: "INSERT ON DUPLICATE KEY UPDATE is not supported on foreign table."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05081 - GAUSS-05090
+
+<br/>
+
+GAUSS-05081: "INSERT ON DUPLICATE KEY UPDATE is not supported on VIEW."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05082: "INSERT ON DUPLICATE KEY UPDATE don't allow update on primary key or unique key."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05083: "rte is not in p_rtable list"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05084: "leftmostQuery should not be null"
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05085: "node name in node list is not coorrect"
+
+SQLSTATE: OP003
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05086: "unsupport node type: %d"
+
+SQLSTATE: XX006
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05087: "not support both coordinator and datanode in the execute list"
+
+SQLSTATE: OP003
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05088: "EXECUTE DIRECT cannot execute CREATE RULE"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05089: "EXECUTE DIRECT cannot execute SELECT query with normal table on coordinator"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05090: "subParseState should not be null"
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05091 - GAUSS-05100
+
+<br/>
+
+GAUSS-05091: "non-integer constant in group clause"
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05092: "%s position %ld is not in select list"
+
+SQLSTATE: 42P10
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05093: "Out of memory"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05094: "message len is too short."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05095: "you can only take append_mode = on, off, refresh, read_only, end_catchup"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05096: "Alter-Table set append mode should have 'rel_cn_oid' set together"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05097: "Alter-Table set rel_cn_oid should have 'append_mode' set together"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05098: "Proc redistribution only can be set during data redistribution time"
+
+SQLSTATE: D0011
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05099: "Proc redistribution only can be reset during data redistribution time"
+
+SQLSTATE: D0011
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05100: "Modulo value: %d out of range %d."
+
+SQLSTATE: 22003
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/52-GAUSS-05101-GAUSS-05200.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/52-GAUSS-05101-GAUSS-05200.md
new file mode 100644
index 0000000000000000000000000000000000000000..2d85c5fd3facd8ceff66a89e6ea9c3f5de59beda
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/52-GAUSS-05101-GAUSS-05200.md
@@ -0,0 +1,604 @@
+---
+title: GAUSS-05101 - GAUSS-05200
+summary: GAUSS-05101 - GAUSS-05200
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-05101 - GAUSS-05200
+
+<br/>
+
+## GAUSS-05101 - GAUSS-05110
+
+<br/>
+
+GAUSS-05101: "Could not alloc new memory."
+
+SQLSTATE: 58000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05102: "Can't get group member"
+
+SQLSTATE: 58000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05103: "null type_loc is invalid"
+
+SQLSTATE: 22004
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05104: "PGXC node %s: cannot be a central node, it has to be a Coordinator"
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05105: "the replication type should be multi-standby, now is %d"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05106: "DN matric cannot alloc memory."
+
+SQLSTATE: 53000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05107: "PGXC Node %s(host = %s, port = %d, sctp_port = %d, control_port = %d): object already defined"
+
+SQLSTATE: 42710
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05108: "Datanode %s: can not be central node."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05109: "PGXC node %s is central node already."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05110: "parameter requires a Boolean value"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05111 - GAUSS-05120
+
+<br/>
+
+GAUSS-05112: "Get buckets failed.reason:the buckets number(%d) is not correct(%d)."
+
+SQLSTATE: D0011
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05113: "group_members is null for tuple %u"
+
+SQLSTATE: 22004
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05116: "Can not find redistributed source group with in_redistribution 'y'."
+
+SQLSTATE: 42704
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05119: "NodeGroup name %s can not be preserved group name"
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05121 - GAUSS-05130
+
+<br/>
+
+GAUSS-05126: "group_name can not be NULL "
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05131 - GAUSS-05140
+
+<br/>
+
+GAUSS-05133: "The installation group has no members."
+
+SQLSTATE: 58000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05137: "No destgroup in resize process"
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05138: "NodeGroup name %s is invalid."
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05141 - GAUSS-05150
+
+<br/>
+
+GAUSS-05145: "cannot drop '%s' because other objects depend on it"
+
+SQLSTATE: 2BP01
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05150: "cannot drop '%s' because at least one role %u depend on it"
+
+SQLSTATE: 2BP01
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05151 - GAUSS-05160
+
+<br/>
+
+GAUSS-05152: "default_storage_nodegroup %s not defined."
+
+SQLSTATE: 42710
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05153: "Bucketmap is not found with given groupoid %u"
+
+SQLSTATE: 42704
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05155: "Connection to database failed: %s"
+
+SQLSTATE: 58000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05156: "execute statement: %s failed: %s"
+
+SQLSTATE: 58000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05157: "PQtuples num is invalid : %d"
+
+SQLSTATE: 58000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05158: "fail to get tables in database %s for query remain table"
+
+SQLSTATE: 58000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05160: "Invalid null pointer attribute for gs_get_nodegroup_tablecount()"
+
+SQLSTATE: 42P24
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05161 - GAUSS-05170
+
+<br/>
+
+AUSS-05161: "can not open pg_database"
+
+SQLSTATE: 58000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05162: "count is invalid, count:%d, tmpCount:%d"
+
+SQLSTATE: 58000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05163: "must be system admin or operator admin in operation mode to manage pooler"
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05164: "pg_pool_ping cannot run inside a transaction block"
+
+SQLSTATE: 25001
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05165: "invalid input/output buffer in node handle"
+
+SQLSTATE: 53200
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05166: "out of memory for node handles"
+
+SQLSTATE: 53200
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05167: "coordinator cannot identify itself"
+
+SQLSTATE: XX000
+
+错误原因: 内部错误，pgxc_node系统表被破坏或者用户自行修改过报错节点的pgxc_node_name参数。
+
+解决办法: "不建议用户修改pgxc_node_name参数，如因错误修改导致报错参考: 1. restore模式启动CN，查询pgxc_node系统表获取nodename，根据此信息恢复配置参数。2. 以OM部署的此实例的标准日志命名恢复配置参数。"
+
+GAUSS-05168: "message len is too short"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05169: "conn cursor overflow"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05170: "Invalid Datanode number"
+
+SQLSTATE: 53200
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05171 - GAUSS-05180
+
+<br/>
+
+GAUSS-05171: "Invalid coordinator number"
+
+SQLSTATE: 53200
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05172: "failed to get pooled connections"
+
+SQLSTATE: 53000
+
+错误原因: 从pooler manager线程获取连接失败。
+
+解决办法: 查看报错日志附近pooler manager的日志确定错误根因，并根据相应日志尝试修复。
+
+GAUSS-05173: "replication type is invalid in PGXCNodeGetNodeId (nodeoid = %u, node_type = %c"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05174: "Failed to connect to the compute pool. See log file for more details."
+
+SQLSTATE: 08006
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05175: "Write to replicated table returned different results from the Datanodes on current DN:%s and previous DN:%s."
+
+SQLSTATE: XX001
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05176: "Unexpected TUPDESC response from Datanode"
+
+SQLSTATE: 08000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05177: "Failed to send queryid to %s"
+
+SQLSTATE: 08000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05178: "Failed to send queryid to %s before PREPARE command"
+
+SQLSTATE: 08000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05179: "failed to send %s command to node %u"
+
+SQLSTATE: 08000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05180: "Failed to COMMIT the transaction on nodes: %s."
+
+SQLSTATE: 08000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05181 - GAUSS-05190
+
+<br/>
+
+GAUSS-05181: "Can not find location info for relation oid: %u"
+
+SQLSTATE: 22004
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05182: "foreignPrivateList is NULL"
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05183: "Could not send user pl to CN of the compute pool: %s."
+
+SQLSTATE: 08000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05184: "Could not begin transaction on Datanodes."
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05185: "Failed to read response from Datanodes"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05186: "FATAL state of connection to datanode %u"
+
+SQLSTATE: 08000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05187: "No coordinator nodes defined in cluster"
+
+SQLSTATE: 42704
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05188: "Failed to send snapshot to %s"
+
+SQLSTATE: 08000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05189: "Failed to send command to %s"
+
+SQLSTATE: 08000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05190: "Could not begin transaction on Coordinator nodes"
+
+SQLSTATE: 08000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05191 - GAUSS-05200
+
+<br/>
+
+GAUSS-05191: "Failed to send command to coordinators"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05192: "Unexpected response from coordinator"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05193: "TUPDESC message has not been received before DATAROW message from %s"
+
+SQLSTATE: 08000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05194: "Failed to close Datanode statement"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05195: "Unsupport DML two phase commit under gtm free mode."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05196: "from remote cluster: %s"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05197: "10655"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05198: "Could not begin transaction on Datanode."
+
+SQLSTATE: 08000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05199: "Fetch statistics from myself is unexpected. Maybe switchover happened."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05200: "cooperation analysis: please update to the same version"
+
+SQLSTATE: 08P01
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/53-GAUSS-05201-GAUSS-05300.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/53-GAUSS-05201-GAUSS-05300.md
new file mode 100644
index 0000000000000000000000000000000000000000..5b8c41d2571187f80fbe37b313a005bc7b48b5a7
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/53-GAUSS-05201-GAUSS-05300.md
@@ -0,0 +1,868 @@
+---
+title: GAUSS-05201- GAUSS-05300
+summary: GAUSS-05201- GAUSS-05300
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-05201- GAUSS-05300
+
+<br/>
+
+## GAUSS-05201- GAUSS-05210
+
+<br/>
+
+GAUSS-05201: "unrecognize LOCKMODE type."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05202: "invalid address for the compute pool: %s"
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05203: "invalid message format, please update to the same version"
+
+SQLSTATE: 08P01
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05204: "cooperation analysis: relation does not exist."
+
+SQLSTATE: 42704
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05205: "cooperation analysis: relation kind is not supported."
+
+SQLSTATE: 42809
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05206: "cooperation analysis: colomn information does not match."
+
+SQLSTATE: 42809
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05207: "cooperation analysis: unrecognized check result type: %d"
+
+SQLSTATE: 38000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05208: "cooperation analysis: invalid size of snapshot"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05209: "Failed to send queryid to %s before COMMIT command(1PC)"
+
+SQLSTATE: 08000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05210: "failed to notify node %u to commit"
+
+SQLSTATE: 08000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05211- GAUSS-05220
+
+<br/>
+
+GAUSS-05211: "failed to receice response from node %u after notify commit"
+
+SQLSTATE: 08000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05212: "failed to send commit csn to node %u"
+
+SQLSTATE: 08000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05213: "Failed to get valid node id from node definitions"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05214: "invalid node_list, coor_num:%d, datanode_num:%d"
+
+SQLSTATE: 22026
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05215: "Failed to send COMMIT/ROLLBACK on nodes: %s.Failed to COMMIT/ROLLBACK the transaction on nodes: %s."
+
+SQLSTATE: 08000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05216: "unsupported proc in single node mode."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05217: "pooler: Failed to create agent, number of agent reaches MaxAgentCount: %d"
+
+SQLSTATE: 53300
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05218: "agent cannot alloc memory."
+
+SQLSTATE: 53200
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05219: "pooler: connect failed, invaild argument."
+
+SQLSTATE: 08000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05220: "pooler: Failed to init agent, number of agent reaches MaxAgentCount: %d"
+
+SQLSTATE: 53300
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05221- GAUSS-05230
+
+<br/>
+
+GAUSS-05221: "pooler: could not find node of node[%d], oid[%u], needCreateArrayLen[%d], loopIndex[%d], i[%d], j[%d], isNull[%d]"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05222: "pooler: Failed to get_nodeInfo_from_matric: needCreateNodeArray is null."
+
+SQLSTATE: 01000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05223: "pooler: Failed to get_slave_datanode_oid: can't find slave nodes."
+
+SQLSTATE: 01000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05224: "invalid %s node number: %d, max_value is: %d."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05225: "pooler: The node(oid:%u) has no available slot, the number of slot in use reaches upper limit!"
+
+SQLSTATE: 53300
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05226: "pooler: Node(oid:%u) has been removed or altered"
+
+SQLSTATE: 01000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05227: "pooler: Communication failure, failed to send session commands or invalid incoming data, error count: %d."
+
+SQLSTATE: 08000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05228: "pooler: failed to create connections in parallel mode, due to failover, pending"
+
+SQLSTATE: 08006
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05229: "pooler: failed to create connections in parallel mode, Error Message: %s"
+
+SQLSTATE: 08006
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05230: "pooler: agent_release_connections: agent is null"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05231- GAUSS-05240
+
+<br/>
+
+GAUSS-05231: "malloc memory failed in dynamic loader."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05232: "latch already owned by %lu, my pid %lu"
+
+SQLSTATE: 58000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05233: "could not reattach to shared memory (key=%d): %m"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05234: "reattaching to shared memory returned unexpected address"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05235: "failed to release reserved memory region : error code %lu"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05236: "could not reattach to shared memory : error code %lu"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05237: "Init dictionary failed for invalid inputs"
+
+SQLSTATE: 58000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05238: "multiple FilePath parameters"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05239: "Text search for Danish is not supported!"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05240: "Text search for Dutch is not supported!"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05241- GAUSS-05250
+
+<br/>
+
+GAUSS-05241: "Text search for Finnish is not supported!"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05242: "Text search for French is not supported!"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05243: "Text search for German is not supported!"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05244: "Text search for Hungarian is not supported!"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05245: "Text search for Italian is not supported!"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05246: "Text search for Norwegian is not supported!"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05247: "Text search for Porter is not supported!"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05248: "Text search for Portuguese is not supported!"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05249: "Text search for Spanish is not supported!"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05250: "Text search for Swedish is not supported!"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05251- GAUSS-05260
+
+<br/>
+
+GAUSS-05251: "Text search for Romanian is not supported!"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05252: "Text search for Russian is not supported!"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05253: "Text search for Turkish is not supported!"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05254: "FilePath parameter should be with DictFile/AffFile/StopWords"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05255: "multiple Synonyms parameters"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05256: "multiple CaseSensitive parameters"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05257: "too many lexemes in thesaurus entry"
+
+SQLSTATE: F0000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05258: "Chinese is not supported by ASCII!"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05259: "pound parser only support UTF8/GBK/ASCII encoding"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05260: "Zhparser is not supported!"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05261- GAUSS-05270
+
+<br/>
+
+GAUSS-05261: "the parameter 'len' should not be negative."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05262: "the parameter 'len' is out of limit."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05263: "The name of internal dictionary file is too long"
+
+SQLSTATE: 42622
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05264: "FilePath must set an absolute path followed by 'file://'."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05265: "FilePath must set an absolute path followed by 'file:///'."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05266: "FilePath must set an obs path info followed by 'obs://'."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05267: "FilePath must start with 'file://' or 'obs://': %s"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05268: "The name of dictionary file is too long"
+
+SQLSTATE: 42622
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05269: "Dictionary file '%s' does not exist or cannot access the directory."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05270: "Dictionary File '%s' does not have READ permission."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05271- GAUSS-05280
+
+<br/>
+
+GAUSS-05271: "TEXT SEARCH is not yet supported."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05272: "Dictionary file name value '%s' contain no %c"
+
+SQLSTATE: 58000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05273: "Copy dictionary file '%s' failed: %m"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05274: "Send dictionary file to node fail: %m, command %s"
+
+SQLSTATE: 58000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05275: "Send dictionary file to backup fail: %m, command %s"
+
+SQLSTATE: 58000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05276: "Delete internal dictionary files failed for invalid inputs"
+
+SQLSTATE: 58000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05277: "unrecognized regis node type: %u"
+
+SQLSTATE: XX004
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05278: "affix flag '%s' is out of range"
+
+SQLSTATE: F0000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05279: "invalid affix flag '%s'"
+
+SQLSTATE: F0000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05280: "invalid character in affix flag '%s'"
+
+SQLSTATE: F0000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05281- GAUSS-05290
+
+<br/>
+
+GAUSS-05281: "unrecognized type of Conf->flagMode: %d"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05282: "invalid affix flag '%s' with 'long' flag value"
+
+SQLSTATE: F0000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05283: "unrecognized state in parse_ooaffentry: %d"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05284: "invalid affix alias '%s'"
+
+SQLSTATE: F0000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05285: "Ispell dictionary supports only 'default', 'long', and 'num' flag value"
+
+SQLSTATE: F0000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05286: "number of aliases exceeds specified number %d"
+
+SQLSTATE: F0000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05287: "affix file contains both old-style and new-style commands"
+
+SQLSTATE: F0000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05288: "invalid affix alias '%s', max affix value:%d"
+
+SQLSTATE: F0000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05289: "invalid len: %d"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05290: "localized string format value too long"
+
+SQLSTATE: 22008
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05291- GAUSS-05300
+
+<br/>
+
+GAUSS-05291: "The input NUMCacheEntry is invalid, which is Null."
+
+SQLSTATE: 22004
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05292: "input format of numeric shouldn't bigger than length of buffer."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05293: "invalid data."
+
+SQLSTATE: D0011
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05294: "invalid data for 'year = 0' ,value must be between -4712 and 9999, and not be 0"
+
+SQLSTATE: 22008
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05295: "value '%s' is out of range for type %s"
+
+SQLSTATE: 22003
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05296: "could not format inet value"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05297: "invalid input syntax for %s: '%s'"
+
+SQLSTATE: 22P02
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05298: "could not convert format string from UTF-8: error code %lu"
+
+SQLSTATE: 22021
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05299: "strftime(%s) failed: %m"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05300: "function '%s' does not exist xxxx"
+
+SQLSTATE: 42883
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/54-GAUSS-05301-GAUSS-05400.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/54-GAUSS-05301-GAUSS-05400.md
new file mode 100644
index 0000000000000000000000000000000000000000..9cbdc06219a9b6d08725599d9051e60654a3a7e9
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/54-GAUSS-05301-GAUSS-05400.md
@@ -0,0 +1,860 @@
+---
+title: GAUSS-05301 - GAUSS-05400
+summary: GAUSS-05301 - GAUSS-05400
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-05301 - GAUSS-05400
+
+<br/>
+
+## GAUSS-05301 - GAUSS-05310
+
+<br/>
+
+GAUSS-05301: "more than one function named '%s', %d functions are found"
+
+SQLSTATE: 42725
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05302: "SPI_connect failed: %s"
+
+SQLSTATE: SP001
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05303: "null value not allowed"
+
+SQLSTATE: 22004
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05304: "The length should not be nagative: %d."
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05305: "cache lookup failed for attribute %d of relation %u, in node [%s]"
+
+SQLSTATE: 29P01
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05306: "cache lookup failed for type oid %d"
+
+SQLSTATE: 29P01
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05307: "Multi-column statistic needs at least two columns."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05308: "Multi-column statistic supports at most %d columns."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05309: "Replicate foreign table is not supported by extended statistic."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05310: "System catalog is not supported by extended statistic."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05311 - GAUSS-05320
+
+<br/>
+
+GAUSS-05311: "MCV column numbers are not matched."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05312: "ordered_set_startup function context info is null"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05313: "ordered-set aggregate support function called for non-ordered-set aggregate"
+
+SQLSTATE: 29000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05314: "ordered-set aggregate support function does not support multiple aggregated columns"
+
+SQLSTATE: 42P25
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05315: "ordered-set aggregate called in non-aggregate context"
+
+SQLSTATE: 29000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05316: "wrong interpolate type"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05317: "percentile cannot be NULL"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05318: "percentile value %g is not between 0 and 1"
+
+SQLSTATE: 22003
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05319: "missing row in percentile_cont"
+
+SQLSTATE: P0002
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05320: "interval_mul result month: %lf, day: %lf overflow"
+
+SQLSTATE: 22015
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05321 - GAUSS-05330
+
+<br/>
+
+GAUSS-05321: "the input timestamp must not be null."
+
+SQLSTATE: 22004
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05322: "timestamp out of range, negative Julian days is not supported"
+
+SQLSTATE: 22008
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05323: "The result of timestampdiff out of range."
+
+SQLSTATE: 22008
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05324: "the format is not correct"
+
+SQLSTATE: 0A000
+
+错误原因: 输入数据为空或长度越界。
+
+解决办法: 检查输入数据。
+
+GAUSS-05325: "Invalid day format: \\'%s\\' of the week"
+
+SQLSTATE: 22008
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05326: "Week day out of range, the range is %d … %d"
+
+SQLSTATE: 22008
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05327: "timestamp out of range."
+
+SQLSTATE: 22008
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05328: "Parameters of complex_array_in are invalid."
+
+SQLSTATE: 00000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05329: "array size cannot be negative."
+
+SQLSTATE: 22003
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05330: "null pointer for nullbitmap."
+
+SQLSTATE: 22004
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05331 - GAUSS-05340
+
+<br/>
+
+GAUSS-05331: "input zero npts for path_encode is invalid"
+
+SQLSTATE: 22012
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05332: "file length cannot be divisibed by 8k: file %s, offset %ld, nbytes %ld"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05333: "cheksum failed in file '%s'(computed: %d, recorded: %d)"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05334: "must be initial account to read files"
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05335: "must be initial account to get file information"
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05336: "must be initial account to get directory listings"
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05337: "start value cannot be NaN"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05338: "stop value cannot be NaN"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05339: "step size cannot be NaN"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05340: "there should be at least one non-zero digit."
+
+SQLSTATE: 42P24
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05341 - GAUSS-05350
+
+<br/>
+
+GAUSS-05341: "cannot convert infinity to numeric"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05342: "caller passed the error typcache entry"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05343: "kill backend is prohibited during online expansion."
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05344: "must be system admin to cancel invalid queries running in all server processes"
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05345: "the user have no right to change cgroup for session [%lu]!"
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05346: "must be superuser account to recover node for wlm"
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05347: "must be superuser account to clean node for wlm"
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05348: "permission denied to get role name"
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05349: "Unexpected null value for the rel of vardata"
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05350: "the right operand should not be null in gincost_opexpr"
+
+SQLSTATE: OP002
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05351 - GAUSS-05360
+
+<br/>
+
+GAUSS-05351: "Unexpected null value for the plan"
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05352: "Unexpected null value for the path"
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05353: "Unexpected null value for the list record's head"
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05354: "the timeout_threshold(%d) could not less than 0"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05355: "the timeout_threshold(%d) could not larger than 2147483"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05356: "unsupported view in single node mode."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05357: "permission denied to get system environment"
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05358: "only system/monitor admin can query sql info view"
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05359: "The function 'pg_wlm_get_session_info' is not supported now!"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05360: "The function 'gs_wlm_get_user_session_info' is not supported now!"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05361 - GAUSS-05370
+
+<br/>
+
+GAUSS-05361: "Only system admin user can use this function"
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05362: "invalid thread id %ld for it is 0 or postmaster pid."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05363: "invalid size of cnt"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05364: "failed to get the parameter of resource pool %s!"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05365: "cgroup is not initialized or group name %s is invalid!"
+
+SQLSTATE: 42P26
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05366: "%s logical cluster doesn't exist!"
+
+SQLSTATE: 42704
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05367: "class group %s doesn't exist!"
+
+SQLSTATE: 42704
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05368: "workload group %s doesn't exist!"
+
+SQLSTATE: 42704
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05369: "invalid name of resource pool: NULL or ""
+
+SQLSTATE: 42602
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05370: "parent group '%s' doesn't have exception information!"
+
+SQLSTATE: 42704
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05371 - GAUSS-05380
+
+<br/>
+
+GAUSS-05371: "cgroup is not initialized!"
+
+SQLSTATE: 42704
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05372: "invalid name of logical cluster: NULL or ""
+
+SQLSTATE: 42602
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05373: "Fail to find central coordinator"
+
+SQLSTATE: 29P01
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05374: "Only superuser can call function pg_autovac_status."
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05375: "out of range."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05376: "must be system admin to view the global information"
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05377: "permission denied."
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05378: "must be system admin to reset bad block statistics counters"
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05379: "unknow func name"
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05380: "cannot accpect arrays with dimensions out of range"
+
+SQLSTATE: 2202E
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05381 - GAUSS-05390
+
+<br/>
+
+GAUSS-05381: "unsupported function or view in %s mode."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05382: "invalid null pointer input for text_to_cstring()"
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05383: "blob length: %d ,out of memory"
+
+SQLSTATE: 53200
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05384: "blob/bytea size:%d, only can recevie blob/bytea less than 500M "
+
+SQLSTATE: 53200
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05385: "unsupport type %s"
+
+SQLSTATE: XX004
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05386: "could not determine data type of concat() input to variadic"
+
+SQLSTATE: 42P38
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05387: "could not determine data type of format() input"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05388: "number is out of range"
+
+SQLSTATE: 22003
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05389: "format specifies argument 0, but arguments are numbered from 1"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05390: "width argument position must be ended by '$'"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05391 - GAUSS-05400
+
+<br/>
+
+GAUSS-05391: "ACL string cannot be NULL."
+
+SQLSTATE: 22P02
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05392: "ACL item cannot be NULL."
+
+SQLSTATE: 22P02
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05394: "hash num out of the int max, [%ld]"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05395: "input julian date is overflow"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05396: "the interval value is overflow, it can not perform as oracle interval-style"
+
+SQLSTATE: 22003
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05397: "could not stat bucket dir '%s': %m"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05398: "rel path is not a dir '%s': %m"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05399: "could not stat file under bucket dir '%s': %m"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05400: "expected 1 row, actual %u row"
+
+SQLSTATE: YY015
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/55-GAUSS-05401-GAUSS-05500.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/55-GAUSS-05401-GAUSS-05500.md
new file mode 100644
index 0000000000000000000000000000000000000000..d3fc2bb3ec83494cc35e937881021e39be879624
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/55-GAUSS-05401-GAUSS-05500.md
@@ -0,0 +1,860 @@
+---
+title: GAUSS-05401 - GAUSS-05500
+summary: GAUSS-05401 - GAUSS-05500
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-05401 - GAUSS-05500
+
+<br/>
+
+## GAUSS-05401 - GAUSS-05410
+
+<br/>
+
+GAUSS-05401: "must be system admin to call gs_get_max_dbsize_name."
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05402: "Please check if another schema is in redistribution in the same database."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05403: "system schema '%s' does not support transfer"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05404: "Only system admin can lock the cluster."
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05405: "temp table is not supported in online expansion"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05406: "Only system admin can use the function on coordinator"
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05407: "Can not run the function during initdb or upgrade"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05408: "Can not get temporary tables defination."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05409: "cache lookup failed for table %d."
+
+SQLSTATE: 29P01
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05410: "Not a ordinary table or foreign table."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05411 - GAUSS-05420
+
+<br/>
+
+GAUSS-05411: "Invalid attribute relation option."
+
+SQLSTATE: 02002
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05412: "recover failed could not write to relation mapping file '%s': %m"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05413: "recover failed could not fsync relation mapping file '%s': %m"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05414: "recover failed could not close relation mapping file '%s': %m"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05415: "relmap_redo: wrong size %d in relmap update record"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05416: "Invalid tablespace relation option."
+
+SQLSTATE: 02002
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05417: "unexpected duplicate for tablespace %u, relfilenode %u"
+
+SQLSTATE: LL002
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05418: "corrupted hashtable"
+
+SQLSTATE: LL002
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05419: "namespace %s was invalid after retry"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05420: "relation %s was invalid after retry"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05421 - GAUSS-05430
+
+<br/>
+
+GAUSS-05421: "Table object with oid %u does not exists (has been dropped)"
+
+SQLSTATE: 42P01
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05422: "cache lookup failed for cfg %u"
+
+SQLSTATE: 29P01
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05423: "cache lookup failed for enumlabelid %u"
+
+SQLSTATE: 29P01
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05424: "null group_members for tuple %u"
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05425: "unrecognized distribution key found in source like table"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05426: "Can't get nodeoid for relation %s"
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05427: "There is no installation group for system catalogs!"
+
+SQLSTATE: 55000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05428: "can not open pg_resource_pool"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05429: "Catalog attribute %d for relation '%s' has been updated concurrently"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05430: "Catalog is missing %d attribute(s) for relid %u"
+
+SQLSTATE: 02000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05431 - GAUSS-05440
+
+<br/>
+
+GAUSS-05431: "bucket key column's number is not a 1-D smallint array"
+
+SQLSTATE: 2202E
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05432: "could not find pg_class entry for %u"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05433: "Invalid Oid while setting new relfilenode for tag table."
+
+SQLSTATE: 42602
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05434: "pg_class entry for relid %u vanished during RelationGetIndexList"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05435: "could not open parent relation with OID %u"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05436: "unknown attrKind %u"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05437: "global plan can't be rebuild in share status stmt name %s :global session id :%lu session_id:%lu"
+
+SQLSTATE: 26000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05438: "could not open index with OID %u"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05439: "SearchCatCacheCheck:current transaction is aborted, commands ignored until end of transaction block"
+
+SQLSTATE: 25P02
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05440: "pg_attribute does not have syscache with id %d"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05441 - GAUSS-05450
+
+<br/>
+
+GAUSS-05441: "pg_localtime must not be null!"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05442: "parse error on statement %s."
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05443: "parse error on query %s."
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05444: "could not load library '%s', get error report failed"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05445: "function returned NULL"
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05446: "datum is NULL"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05447: "Division by zero when calculate element numbers!"
+
+SQLSTATE: 22012
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05448: "invalid path:%s"
+
+SQLSTATE: 58P03
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05449: "Current user id is invalid. Please try later."
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05450: "Abnormal process. UserOid has been reseted. Current userOid[%u], reset username is %s."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05451 - GAUSS-05460
+
+<br/>
+
+GAUSS-05451: "bogus lock file '%s',could not unlink it : %m"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05452: "bogus data in lock file '%s': '%s', please kill the instance process, than remove the damaged lock file"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05453: "Unable to get architecture to check ARM LSE!"
+
+SQLSTATE: 58P03
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05454: "Unable to open /proc/cpuinfo to check ARM LSE!"
+
+SQLSTATE: 58P03
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05455: "Normal user is not allowed to use HA channel!"
+
+SQLSTATE: 28000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05456: "Only applications can connect remotely."
+
+SQLSTATE: 28000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05457: "Forbid remote connection via internal maintenance tools."
+
+SQLSTATE: 28000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05458: "Inner maintenance tools only for the initial user."
+
+SQLSTATE: D0011
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05459: "Only allow initial user or operator admin to use operation tool gs_roach."
+
+SQLSTATE: D0011
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05460: "Already too many clients, active/non-active/reserved: %d/%d/%d."
+
+SQLSTATE: 53300
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05461 - GAUSS-05470
+
+<br/>
+
+GAUSS-05461: "pg_server_to_any returns null."
+
+SQLSTATE: 58000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05462: "Row Level Security is not supported."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05463: "'%s' is not a normal table"
+
+SQLSTATE: 42809
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05464: "do not support row level security policy on temp table '%s'"
+
+SQLSTATE: 42809
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05465: "do not support row level security policy on dfs table '%s'"
+
+SQLSTATE: 42809
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05466: "The text entered contains illegal characters!"
+
+SQLSTATE: 22P05
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05467: "failed to initialize %s to " INT64_FORMAT
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05468: "Incorrect backend environment variable $PGDATA"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05469: "must be initial account to examine '%s'"
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05470: "Current degree of parallelism can only be set within [-64,64]"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05471 - GAUSS-05480
+
+<br/>
+
+GAUSS-05472: "permission denied to set role '%s'"
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05473: "first stage encryption password failed"
+
+SQLSTATE: 28P01
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05474: "second stage encryption password failed"
+
+SQLSTATE: 28P01
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05475: "Invalid password stored"
+
+SQLSTATE: 28P01
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05476: "replication_type is not allowed set 1 in Current Version. Set to default (0)."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05477: "Length of file or line is too long."
+
+SQLSTATE: F0000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05478: "Failed to initilize the memory(%uM) of search server, maybe it exceed the half of maxChunksPerProcess(%dM)."
+
+SQLSTATE: 53200
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05479: "invalid operation on memory context"
+
+SQLSTATE: D0011
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05480: "We can not set memory context parent with different session number"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05481 - GAUSS-05490
+
+<br/>
+
+GAUSS-05481: "%s Memory Context could not find block containing block"
+
+SQLSTATE: OP002
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05482: "%s Memory Context could not find block"
+
+SQLSTATE: OP002
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05483: "portal is NULL"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05484: "Accessing null portal entry found in portal hash table."
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05485: "The block was freed before this time."
+
+SQLSTATE: OP002
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05486: "The memory use was overflow."
+
+SQLSTATE: OP002
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05487: "detected write past chunk end in %s"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05488: "Error on %s Memory Context happened when executing memcpy_s:%d"
+
+SQLSTATE: OP001
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05489: "failed to initialize rwlock in AllocSetContextCreate."
+
+SQLSTATE: D0014
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05490: "could not find block"
+
+SQLSTATE: OP001
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05491 - GAUSS-05500
+
+<br/>
+
+GAUSS-05491: "data cache block %d is not owned by resource owner %s"
+
+SQLSTATE: 01007
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05492: "meta cache block %d is not owned by resource owner %s"
+
+SQLSTATE: 01007
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05493: "fakepart reference %u is not owned by resource owner %s"
+
+SQLSTATE: 01007
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05494: "partition map reference is not owned by resource owner %s"
+
+SQLSTATE: 01007
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05495: "Failed to obtain address of the block!"
+
+SQLSTATE: 29P02
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05496: "could not write to row store temp file: %m"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05497: "could not read from row store temp file: %m"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05498: "row store : dn node id(%d) exceeds max bank num(%d)"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05499: "row store : cn node id(%d) exceeds max bank num(%d)"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05500: "failed to get cn/dn node id for OID %u"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/56-GAUSS-05501-GAUSS-05600.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/56-GAUSS-05501-GAUSS-05600.md
new file mode 100644
index 0000000000000000000000000000000000000000..7f1dd4602d4ff1e748863fc2ba6b8ea8186e7d6b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/56-GAUSS-05501-GAUSS-05600.md
@@ -0,0 +1,868 @@
+---
+title: GAUSS-05501 - GAUSS-05600
+summary: GAUSS-05501 - GAUSS-05600
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-05501 - GAUSS-05600
+
+<br/>
+
+## GAUSS-05501 - GAUSS-05510
+
+<br/>
+
+GAUSS-05501: "row store : cannot write cell into either memory or disk"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05502: "row store : expect data from row store, but no data read"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05503: "row store : expect to read node_id = %d but got %d"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05504: "could not seek store temp file: %m"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05505: "row store : expect to read from file but no file opened"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05506: "row store : cannot determine msg len when %s"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05507: "row store : msg and msglen mismatch when %s"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05508: "row store : LZ4_compress_default failed trying to compress the data"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05509: "row store : unexpected original len of msg when decompressing data"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05510: "row store : unexpected compressed len when decompressing data"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05511 - GAUSS-05520
+
+<br/>
+
+GAUSS-05511: "insufficient memory allowed for sort, allowed memory is %ld byte, available memory is %ld byte"
+
+SQLSTATE: 53000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05512: "ActiveTapes should be larger than zero."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05513: "invalid sortkey value: attrNum = %d, sortOperators oid = %d in position of %d."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05514: "Backward skip tupples is not support yet."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05515: "Skip n tuples must bigger than 0."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05516: "retrieved tuples over bounded size"
+
+SQLSTATE: 42P25
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05517: "Cannot found valid cid in UsedComboCids. UsedComboCids: %d, tuple cid: %u."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05518: "snapshot is not active"
+
+SQLSTATE: 29000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05519: "could not resolve cmin/cmax of catalog tuple"
+
+SQLSTATE: P0002
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05520: "could not resolve combocid to cmax"
+
+SQLSTATE: P0002
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05521 - GAUSS-05530
+
+<br/>
+
+GAUSS-05521: "Built-in functions should not be added into pg_proc"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05522: "(s|libcomm_cpu_rate init) Failed to malloc g_libcomm_used_rate."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05523: "(r|receivers init) Failed to malloc g_r_node_sock[%d]."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05524: "(r|receivers init) Failed to malloc g_receivers[%d]."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05525: "(s|sender init) Failed to malloc g_s_node_sock[%d]."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05526: "(s|sender init) Failed to malloc g_delay_info[%d]."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05527: "(s|sender init) Failed to malloc g_senders[%d]."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05528: "Failed to build mailbox[%d]."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05529: "communicator palloc CommReceiverPIDS mempry failed"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05530: "(r|cmailbox init) Failed to init cmailbox."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05531 - GAUSS-05540
+
+<br/>
+
+GAUSS-05531: "(s|pmailbox init) Failed to init pmailbox."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05532: "(s|pmailbox init) Failed to init g_usable_streamid."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05533: "(s|sender init) Failed to init sender[%d] for %s."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05534: "Failed to read response from Local Stream Node, Detail: Node %s, Plan Node ID %u, SMP ID %d"
+
+SQLSTATE: XX003
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05535: "(s|flow ctrl init) Failed to init poller list:%s."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05536: "(r|receiver init) Failed to init receiver listen socket:%s."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05537: "(r|receiver init) Failed to init receiver semaphore:%s."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05538: "(r|flow ctrl init) Failed to do listen:%s."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05539: "(r|flow ctrl init) Failed to init poller list:%s."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05540: "(s|flow ctrl) Failed to do epoll wait[%d] with errno[%d]:%s."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05541 - GAUSS-05550
+
+<br/>
+
+GAUSS-05541: "(r|flow ctrl) Failed to do epoll wait[%d] with errno[%d]:%s."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05542: "(r|recv loop) Failed to do epoll wait[%d] with errno[%d]:%s."
+
+SQLSTATE:无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05543: "(r|receiver init) Failed to init thd_receiver_id:%s."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05544: "(r|receiver init) Failed to init poller list:%s."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05545: "(r|receiver init) Failed to add libcomm listen socket[%d] and version[%d] to poller list."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05546: "(r|receiver init) Libcomm init receiver threads fail, wait(10s) timeout, please check the machine resource usage, and try again later."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05547: "Column %d receive unexpected C_TYPE %d"
+
+SQLSTATE: 42804
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05548: "unexpected null string in column %d"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05549: "query in function exec_on_extension returns too many columns"
+
+SQLSTATE: 54011
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05550: "SQL_ERROR: unexpected data while converting it into bool."
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05551 - GAUSS-05560
+
+<br/>
+
+GAUSS-05551: "libodbc.so.1 or libodbc.so.2 not found, which is needed to run the Extension Connector."
+
+SQLSTATE: 58P01
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05552: "Can NOT find function '%s()' in libodbc.so.1 or libodbc.so.2."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05553: "unsupport data type: [%s] found in record definition."
+
+SQLSTATE: 42804
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05554: "unsupport data type found, type oid: %d"
+
+SQLSTATE: 42804
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05555: "function returning record called in context that cannot accept type record"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05556: "key '%s' is given more than once!"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05557: "missing data source to be connected for first parameter."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05558: "data source '%s' does not exist"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05559: "missing statement to be executed for second parameter."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05560: "for ODBC driver, we need a DSN!"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05561 - GAUSS-05570
+
+<br/>
+
+GAUSS-05561: "Initialize ODBC Connector failed due to insufficient memory."
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05562: "Invalid string length"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05563: "SQL can not be null!"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05564: "Extension Connector is not supported in current version."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05565: "must be system admin to use this function"
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05566: "Un-support feature in MySQL compatibility"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05567: "Failed to found one dummy server."
+
+SQLSTATE: 22004
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05568: "Only one dummy server is allowed to exist in one database."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05569: "build global Dummy servder cache hash table failed"
+
+SQLSTATE: 42704
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05570: "could not initialize Dummny server hash table"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05571 - GAUSS-05580
+
+<br/>
+
+GAUSS-05571: "foreign table server is invalid."
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05572: "cannot find foreign server with given name %s ."
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05573: "totalrows is invalid"
+
+SQLSTATE: HV000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05574: "Failed to get obskey from options of DWS."
+
+SQLSTATE: HV000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05575: "No 'format' option provided."
+
+SQLSTATE: HV000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05576: "Invalid location value for the foreign table."
+
+SQLSTATE: HV000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05577: "Failed to get obskey from cipher file"
+
+SQLSTATE: 22004
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05578: "Incorrect backend environment variable $GAUSSHOME"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05579: "Failed to open file %s, errno = %d, reason = %s."
+
+SQLSTATE: HV000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05580: "The %s file is empty."
+
+SQLSTATE: HV000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05581 - GAUSS-05590
+
+<br/>
+
+GAUSS-05581: "Failed to read file %s."
+
+SQLSTATE: HV000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05582: "Failed to parse %s file: %s."
+
+SQLSTATE: HV000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05583: "Failed to parse %s file: unkonwn error."
+
+SQLSTATE: HV000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05584: "Must exist array format in the %s json file."
+
+SQLSTATE: HV000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05585: "No such region name: %s in %s file."
+
+SQLSTATE: HV000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05586: "Invalid percentile syntax"
+
+SQLSTATE: XX006
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05587: "Too many percentile values"
+
+SQLSTATE: XX006
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05588: "[UniqueSQL] check unique sql array slot index!"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05589: "[UniqueSQL] invalid 'r' message. node: %s"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05590: "[UniqueSQL] palloc failed for results!"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05591 - GAUSS-05600
+
+<br/>
+
+GAUSS-05591: "[UniqueSQL] during get stat from remote, failed to send/recv data!"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05592: "[UniqueSQL] palloc0 error when querying unique sql stat!"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05593: "only system/monitor admin can query unique sql view"
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05594: "[UniqueSQL] recv invalid sql ids count"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05595: "out of memory during allocating list element."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05596: "Cleanup global unique sql info only support on CN nodes."
+
+SQLSTATE: 01000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05597: "First parameter is wrong. USAGE: [GLOBAL/LOCAL],[ALL/BY_USERID/BY_CNID],[VALUE]"
+
+SQLSTATE: 01000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05598: "Second parameter is wrong. USAGE:[GLOBAL/LOCAL],[ALL/BY_USERID/BY_CNID],[VALUE]"
+
+SQLSTATE: 01000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05599: "only system/monitor admin can reset unique sql"
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05600: "[user] cannot alloc memory for user stat"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/57-GAUSS-05601-GAUSS-05700.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/57-GAUSS-05601-GAUSS-05700.md
new file mode 100644
index 0000000000000000000000000000000000000000..e0f4d3df072b651ee879d871c0e38b46d71bf4dd
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/57-GAUSS-05601-GAUSS-05700.md
@@ -0,0 +1,868 @@
+---
+title: GAUSS-05601 - GAUSS-05700
+summary: GAUSS-05601 - GAUSS-05700
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-05601 - GAUSS-05700
+
+<br/>
+
+## GAUSS-05601 - GAUSS-05610
+
+<br/>
+
+GAUSS-05601: "only system/monitor admin can get user statistics info"
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05602: "report params is null"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05603: "report type can not = %s"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05604: "report scope can not = %s"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05605: "dashTitle or tableTitle is null"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05606: "out of the Contents"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05607: "no available data for report"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05608: "dashboard title is not assigned"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05609: "table title is not assigned"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05610: "query is null"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05611 - GAUSS-05620
+
+<br/>
+
+GAUSS-05611: "list is null, can not free"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05612: "table is not null when overturn table"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05613: "no this type of report_scope"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05614: "calc trx diff count failed!"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05615: "set the snapshotid"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05616: "snapshot id is invalid"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05617: "Instance reset time is different"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05618: "invalid report type, should be %s or %s or %s"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05619: "invalid report scope, should be %s or %s"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05620: "invalid report node name."
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05621 - GAUSS-05630
+
+<br/>
+
+GAUSS-05621: "The 3rd argument 'report_type' and 4th argument 'report_scope' should not be null"
+
+SQLSTATE: 22004
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05622: "Superuser privilege is neended to generate report"
+
+SQLSTATE: OP001
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05623: "out of memory of current node."
+
+SQLSTATE: 53200
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05624: "could not establish connection"
+
+SQLSTATE: 08001
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05625: "Superuser privilege is need to operate wdr_xdb_query"
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05626: "wrong number of arguments"
+
+SQLSTATE: 54023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05627: "connection '%s' not available"
+
+SQLSTATE: 08003
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05628: "could not send query: %s"
+
+SQLSTATE: 02002
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05629: "failed to set single-row mode for dblink query"
+
+SQLSTATE: 02002
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05630: "remote query result rowtype does not match the specified FROM clause rowtype"
+
+SQLSTATE: 42804
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05631 - GAUSS-05640
+
+<br/>
+
+GAUSS-05631: "only system admin can kill snapshot thread"
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05632: "kill snapshot thread failed %s"
+
+SQLSTATE: OP001
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05633: "kill snapshot thread failed, exceeds MAX_RETRY_COUNT(%d)"
+
+SQLSTATE: OP001
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05634: "set lockwait_timeout failed: %s"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05635: "Superuser privilege is need to operate snapshot"
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05636: "WDR snapshot request can not be accepted, please retry later"
+
+SQLSTATE: OP001
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05637: "Cannot respond to WDR snapshot request"
+
+SQLSTATE: OP001
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05638: "query is NULL"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05639: "this query can not get datum values"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05640: "create sequence failed"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05641 - GAUSS-05650
+
+<br/>
+
+GAUSS-05641: "update snapshot end time stamp filled"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05642: "wdr_snapshot_interval is 0"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05643: "invalid query: %s"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05644: "clean table of snap_%s is failed"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05645: "WDR snapshot analyze table:%s not exist"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05646: "insert into tables_snap_timestamp start time stamp is failed"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05647: "insert into snap_%s is failed"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05648: "update tables_snap_timestamp end time stamp is failed"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05649: "clean snapshot id %lu is failed in snapshot table"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05650: "clean snapshot id %lu is failed in tables_snap_timestamp table"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05651 - GAUSS-05660
+
+<br/>
+
+GAUSS-05651: "query or the tablename is null when snapshot create stat table"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05652: "can not create snapshot stat table"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05653: "create WDR snapshot data table failed"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05654: "spilt str can not null"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05655: "insert into tables_snap_timestamp start time stamp failed"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05656: "create index failed"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05657: "analyze table, connection failed: %s"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05658: "snapshot thread SPI_connect failed: %s"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05659: "The length of str: %d is less than %d"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05660: "Array length %d or %d is less than %d"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05661 - GAUSS-05670
+
+<br/>
+
+GAUSS-05661: "[CapView] OOM in capture view"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05662: "[CapView] could not write to view perf file: %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05663: "[CapView] could not ftell json file :%m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05664: "[CapView] pls check database name and view name!"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05665: "[CapView] view name is too long!"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05666: "[CapView] view name can not contain '('!"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05667: "[CapView] only system admin can capure view"
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05668: "[CapView] in capture_view_to_json proc, view_name or is_all_db can not by null"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05669: "[CapView] in capture_view_to_json proc, is_all_db can only be 0 or 1"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05670: "[CapView] SPI_connect failed: %s"
+
+SQLSTATE: SP001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05671 - GAUSS-05680
+
+<br/>
+
+GAUSS-05671: "[CapView] json file can not by NULL"
+
+SQLSTATE: XX005
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05672: "[CapView] calc realpath failed"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05673: "[CapView] could not open log file '%s': %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05674: "[CapView] could not chmod view json file '%s': %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05675: "[CapView] calc localtime failed"
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05676: "[CapView] invalid query"
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05677: "The encryption key can not be empty!"
+
+SQLSTATE: 39000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05678: "The encryption key must be shorter than 16 bytes!"
+
+SQLSTATE: 39000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05679: "The decryption key can not be empty!"
+
+SQLSTATE: 39000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05680: "Decode the cipher text failed or the ciphertext is too short!"
+
+SQLSTATE: 39000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05681 - GAUSS-05690
+
+<br/>
+
+GAUSS-05681: "Encrypt OBS AK/SK failed."
+
+SQLSTATE: 39000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05682: "Encrypt OBS AK/SK internal error"
+
+SQLSTATE: 39000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05683: "Decrypt OBS AK/SK failed."
+
+SQLSTATE: 39000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05684: "Decrypt OBS AK/SK internal error."
+
+SQLSTATE: 39000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05685: "Failed to get OBS certificate file."
+
+SQLSTATE: 39000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05686: "No key file obsserver.key.cipher"
+
+SQLSTATE: 58P01
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05687: "aes128EncryptSpeedFailed!"
+
+SQLSTATE: 39000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05688: "Failed to get EC certificate file: get env GAUSSHOME failed."
+
+SQLSTATE: 39000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05689: "No key file datasource.key.cipher"
+
+SQLSTATE: 58P01
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05690: "Encrypt EC internal error: dest cipher length is too short."
+
+SQLSTATE: 39000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05691 - GAUSS-05700
+
+<br/>
+
+GAUSS-05691: "Decrypt EC internal error: dest plain length is too short."
+
+SQLSTATE: 39000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05692: "it's an encrypted cluster, but parameter not initialized!"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05693: "encrypt failed, return code is %u!"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05694: "encrypt failed after retry three times, error code is %u!"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05695: "decrypt failed, return code is %u!"
+
+SQLSTATE: 22026
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05696: "decrypt failed after retry three times, error code is %u!"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05697: "transparent_encrypt_kms_url and transparent_encrypt_kms_region should not be empty when transparent encryption enabled."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05698: "Failed to get ak/sk for transparent encryption."
+
+SQLSTATE: 39000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05699: "Failed to fork subprocess to get DEK for transparent encryption. Failure command is: [%s]"
+
+SQLSTATE: 39000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05700: "Failed to get DEK for transparent encryption. Failure command is [%s], error message is [%s]"
+
+SQLSTATE: 39000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/58-GAUSS-05701-GAUSS-05800.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/58-GAUSS-05701-GAUSS-05800.md
new file mode 100644
index 0000000000000000000000000000000000000000..718d22521541c6f2b5754f7d5b34fcda9bef4897
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/58-GAUSS-05701-GAUSS-05800.md
@@ -0,0 +1,868 @@
+---
+title: GAUSS-05701 - GAUSS-05800
+summary: GAUSS-05701 - GAUSS-05800
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-05701 - GAUSS-05800
+
+<br/>
+
+## GAUSS-05701 - GAUSS-05710
+
+<br/>
+
+GAUSS-05701: "Failed to get decode DEK for transparent encryption. Failure content is [%s]."
+
+SQLSTATE: 39000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05702: "Decode transparent_encrypted_string failed, please check it."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05703: "Decrypt transparent_encrypted_string failed, please check it!"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05704: "Out of memory while getting transparent encryption iv."
+
+SQLSTATE: 53200
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05705: "TDE is not supported."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05706: "The data type %u is not supported for bloom filter curently."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05707: "failed to init sigpool mutex: %m."
+
+SQLSTATE: 55P03
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05708: "failed to lock sigpool mutex: %m."
+
+SQLSTATE: 55P03
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05709: "failed to unlock sigpool mutex: %m."
+
+SQLSTATE: 55P03
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05710: "log2m = %d is out of range, it should be in range %d to %d"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05711 - GAUSS-05720
+
+<br/>
+
+GAUSS-05711: "regwidth = %d is out of range, it should be in range %d to %d"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05712: "expthresh = %ld is out of range, it should be in range %d to %d"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05713: "sparseon should be %d or %d"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05714: "no such parameters of input"
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05715: "hll_add_trans_normal outside transition context"
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05716: "hll_union_collect_compressed outside transition context"
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05717: "hll_union_trans_normal outside transition context"
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05718: "hll_union_trans_compressed context"
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05719: "Fail to build partitionmap for realtion'%s'."
+
+SQLSTATE: 42P23
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05720: "Can not run transaction to remote nodes during recovery."
+
+SQLSTATE: 25009
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05721 - GAUSS-05730
+
+<br/>
+
+GAUSS-05721: "could not find tuple with partition OID %u."
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05722: "Fail to build partitionmap for partitioned table '%s'."
+
+SQLSTATE: 42P23
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05723: "Fail to build partitionmap for partitioned table '%u'."
+
+SQLSTATE: 42P23
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05724: "Failed to set the default password for private key File: '%s'"
+
+SQLSTATE: OP002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05725: "too many writing times(>%d):%d, write %d, errno %d"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05726: "%d: write %d, errno %d, detail:%s"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05727: "unrecognized error:%d, write %d, errno %d"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05728: "failed to initialize SSL library, detail:%s"
+
+SQLSTATE: OP002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05729: "failed to create the SSL context, detail:%s"
+
+SQLSTATE: OP002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05730: "invlid cert file directory"
+
+SQLSTATE: OP002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05731 - GAUSS-05740
+
+<br/>
+
+GAUSS-05731: "failed to load the root CA Certificate %s(%s)"
+
+SQLSTATE: OP002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05732: "failed to certificate the %s(%s) file in SSL context"
+
+SQLSTATE: OP002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05733: "stat cipher file '%s' failed, detail: %s"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05734: "stat rand file '%s' failed, detail: %s"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05735: "cipher file '%s' has group or world access;permissions should be u=rw (0600) or less with Error: %s"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05736: "rand file '%s' has group or world access;permissions should be u=rw (0600) or less with Error: %s"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05737: "Failed to create the SSL."
+
+SQLSTATE: OP002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05738: "Failed to set the socket(%d) for SSL"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05739: "Failed to certificate file '%s' in SSL object"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05740: "Failed to check the private key File."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05741 - GAUSS-05750
+
+<br/>
+
+GAUSS-05741: "SSL connect failed, code %d"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05742: "gz_open failed: errno %d"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05743: "gz_read failed: offset %ld, errno %d, returned size %d"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05744: "vfd_file_open failed: vfd(-1), errno %d, file '%s' "
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05745: "vfd_file_open2 failed: vfd(-1), errno %d, file '%s' "
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05746: "vfd_file_read2 failed: errno %d, returned size %d"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05747: "vfd_file_write2 failed: errno %d, returned size %d"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05748: "unzOpen2_64 failed: file '%s'"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05749: "unzGetGlobalInfo64 failed: file '%s', err %d"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05750: "unzOpenCurrentFile failed: file '%s', err %d"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05751 - GAUSS-05760
+
+<br/>
+
+GAUSS-05751: "unzCloseCurrentFile failed: err %d"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05752: "unzReadCurrentFile failed: err %d"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05753: "unzGoToNextFile failed: err %d"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05754: "unzOpenCurrentFile failed: err %d"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05755: "invalid compute pool message subtype %d"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05756: "only coordinator could receive compute pool message type 'I'"
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05757: "only datanode could receive compute pool message type 'R'"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05758: "only coordinator could receive compute pool message type 'C'"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05759: "only coordinator could receive compute pool message type 'D'"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05760: "len is invalid[%d]"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05761 - GAUSS-05770
+
+<br/>
+
+GAUSS-05761: "Failed to get runtime info from the compute pool."
+
+SQLSTATE: 08006
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05762: "Failed to send request to ccn: %s for cp runtime info! 错误原因:  %s"
+
+SQLSTATE: 57P03
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05763: "No CCN in cluster!"
+
+SQLSTATE: XX005
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05764: "Failed to send request to ccn: %s for dn list! dnnum: %d, 错误原因:  %s"
+
+SQLSTATE: 57P03
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05765: "Failed to get dn list from CCN: %s, 错误原因:  %s"
+
+SQLSTATE: 57P03
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05766: "Failed to send request to CCN."
+
+SQLSTATE: 57P03
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05767: "invalid ccn index %d"
+
+SQLSTATE: 42P17
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05768: "invalid size [%lu]"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05769: "something wrong in CPmonitor thread, so reboot CPmonitor thread."
+
+SQLSTATE: 57P03
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05770: "Failed to get the values of $GAUSSHOME"
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05771 - GAUSS-05780
+
+<br/>
+
+GAUSS-05771: "Failed to open config file to connect compute pool. file path: %s"
+
+SQLSTATE: 58P03
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05772: "Failed to get the size of the config file to connect compute pool. file path: %s"
+
+SQLSTATE: 58P03
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05773: "Failed to get the data of the config file to connect compute pool. file path: %s"
+
+SQLSTATE: 58P03
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05774: "'cpip', 'cpport', 'username', 'password', 'version', 'dnnum', 'pl' are needed to connect to the compute pool."
+
+SQLSTATE: 42P17
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05775: "pl should be greater than 0, pl is %d current."
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05776: "no valid config info in cp_client.conf."
+
+SQLSTATE: 42P17
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05777: "get reload signal in %s"
+
+SQLSTATE: D0011
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05778: "the config of node is changed."
+
+SQLSTATE: F0000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05779: "init transaction error, data nodes or coordinators num init failed"
+
+SQLSTATE: D0014
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05780: "no the version of the compute pool is provided."
+
+SQLSTATE: XX005
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05781 - GAUSS-05790
+
+<br/>
+
+GAUSS-05781: "The key string of 'R' request could not be NULL"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05782: "estimate_memory will out of MAX_INT, orign[%d], addMemory[%d]"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05783: "%s space is out of %s's %s space limit"
+
+SQLSTATE: 57014
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05784: "the space used on DN has exceeded the sql use space limit (%d kB)."
+
+SQLSTATE: 57014
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05785: "Remote Sender: Failed to send command to datanode"
+
+SQLSTATE: 22003
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05786: "Normal user could not readjust other user space"
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05787: "cannot open database"
+
+SQLSTATE: 58000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05788: "user space is out of space limit"
+
+SQLSTATE: 57014
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05789: "The memory usage of %s is out of control. it will exit!"
+
+SQLSTATE: 0B000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05790: "role %u does not exist"
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05791 - GAUSS-05800
+
+<br/>
+
+GAUSS-05791: "resource pool %u does not exist in htab."
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05792: "resource pool with control_group %s has been existed in the two-layer resource pool list "
+
+SQLSTATE: 42710
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05793: "cannot create resource pool with class '%s', it has been existed in the normal resource pool list"
+
+SQLSTATE: 42710
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05794: "mem_percent of two-layer resource pools cannot be 0"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05795: "memory percent value is beyond the available range."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05796: "resource pool information of '%s' is missing."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05797: "cannot alter control_group between different groups or alter to a different layer. "
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05798: "resource pool with control group '%s' already exists"
+
+SQLSTATE: 42710
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05799: "cannot alter normal resource pool to the two-layer resource pool list."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05800: "mem_percent of two-layer resource pool cannot be altered to 0."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/59-GAUSS-05801-GAUSS-05900.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/59-GAUSS-05801-GAUSS-05900.md
new file mode 100644
index 0000000000000000000000000000000000000000..03ba427584812c7d939fa75d4fa51cc2a993339c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/59-GAUSS-05801-GAUSS-05900.md
@@ -0,0 +1,698 @@
+---
+title: GAUSS-05801 - GAUSS-05900
+summary: GAUSS-05801 - GAUSS-05900
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-05801 - GAUSS-05900
+
+<br/>
+
+## GAUSS-05801 - GAUSS-05810
+
+<br/>
+
+GAUSS-05801: "redundant options: 'mem_percent'"
+
+SQLSTATE: 22002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05802: "mem_percent has to be in the range of 0-100."
+
+SQLSTATE: 22003
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05803: "redundant options: 'active_statements'"
+
+SQLSTATE: 44000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05804: "active_statements value can't be %d."
+
+SQLSTATE: 22003
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05805: "Failed to initialize Cgroup. Please check Workload manager is enabled and Cgroups have been created!"
+
+SQLSTATE: 58000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05806: "redundant options: 'max_dop'"
+
+SQLSTATE: 22002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05807: "redundant options: 'memory_limit'"
+
+SQLSTATE: 22002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05808: "parent is not supported currently!"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05809: "redundant options: 'io_limits'"
+
+SQLSTATE: 22002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05810: "io_limits can't be %d."
+
+SQLSTATE: 22003
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05811 - GAUSS-05820
+
+<br/>
+
+GAUSS-05811: "redundant options: 'io_priority'"
+
+SQLSTATE: 22002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05812: "io_priority can only be named as 'High', 'Low', 'Medium' and 'None'."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05813: "redundant options: 'nodegroup'"
+
+SQLSTATE: 22002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05819: "redundant options: 'is_foreign'"
+
+SQLSTATE: 22002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05821 - GAUSS-05830
+
+<br/>
+
+GAUSS-05823: "Can't modify is_foreign option when altering resource pool."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05826: "Can't create parent resource pool used for foreign users."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05827: "cannot get resource pool information of %u"
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05828: "cache lookup failed for resource pool id %u, it is removed?"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05831 - GAUSS-05840
+
+<br/>
+
+GAUSS-05833: "The create resource pool statement buffer is too small(%d)."
+
+SQLSTATE: 42P26
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05834: "must be system admin or vcadmin to create resource pool"
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05835: "default session_respool 'invalid_pool' is not allowed to set by user"
+
+SQLSTATE: 42602
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05836: "The memory of resource pool htab cannot be out of %dMB. please drop the unnecessary resource pools"
+
+SQLSTATE: 42P26
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05837: "must be system admin or vcadmin to change resource pools"
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05838: "user %u does not exist"
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05839: "user set perm space failed because its used perm space is out of perm space limit."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05840: "user set temp space failed because its used temp space is out of temp space limit."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05841 - GAUSS-05850
+
+<br/>
+
+GAUSS-05841: "user set spill space failed because its used spill space is out of spill space limit."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05842: "user set group user failed because group user's used perm space will be out of perm space limit."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05843: "user set group user failed because group user's used temp space will be out of temp space limit."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05844: "user set group user failed because group user's used spill space will be out of spill space limit."
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05845: "group user's %s space cannot be less than its child user's %s space limit."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05846: "need two valid user."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05847: "cannot get resource pool information of user %u"
+
+SQLSTATE: 42P26
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05848: "user %u cannot be used as user group, for it uses non-parent resource pool %s"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05849: "please specify resource pool when create or alter user with user group %u"
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05850: "cannot get resource pool information of resource pool %u"
+
+SQLSTATE: 42P26
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05851 - GAUSS-05860
+
+<br/>
+
+GAUSS-05851: "resource pool %u cannot be used, for it is used by user %u"
+
+SQLSTATE: 55006
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05852: "please specify user group when create or alter user with child resource pool %u."
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05853: "non-child resource pool %u cannot be used for child user"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05854: "parent user's resource pool(control_group is '%s') and resource pool specified(control_group is '%s') don't match"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05855: "cannot use resource pool %u when alter user with 'user group default'"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05856: "user %u has child users, cannot alter it with any operation"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05857: "please specify 'user group default' when create or alter user with non-child resource pool %u."
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05858: "please specify resource pool when alter user with 'user group default'"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05859: "super user cannot use resource pool in the two-layer resource pool list."
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05860: "cannot find resource pool with user: %u"
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05861 - GAUSS-05870
+
+<br/>
+
+GAUSS-05862: "session_respool name '%s' does not exist"
+
+SQLSTATE: 42602
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05863: "parent resource pool '%s' cannot be used as sesion_respool"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05864: "resource pool '%s' is not in logical cluster '%s'."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05869: "Error: environment variable '%s' contain invaild symbol '%s'."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05870: "Cgroup is not mounted or enable_control_group is false"
+
+SQLSTATE: 0B000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05871 - GAUSS-05880
+
+<br/>
+
+GAUSS-05871: "must be superuser account to print cgroup config"
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05872: "move node failed, out of memory."
+
+SQLSTATE: 53200
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05873: "[DYWLM] Failed to send dynamic workload params to CCN!"
+
+SQLSTATE: 08006
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05874: "[DYWLM] Failed to receive queue info from CCN, error info: %s"
+
+SQLSTATE: 08006
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05875: "out of memory of current node, please check statement count"
+
+SQLSTATE: 53200
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05876: "failed to enqueue in central node"
+
+SQLSTATE: 58000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05877: "resource pool: %s does not exist"
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05878: "out of memory of central node"
+
+SQLSTATE: 53200
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05879: "group name %s does not exist on central node"
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05880: "the counts of waiting statements have reached the limitation."
+
+SQLSTATE: 54000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05881 - GAUSS-05890
+
+<br/>
+
+GAUSS-05881: "out of memory of current memory."
+
+SQLSTATE: 53200
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05882: "Central node is recovering now, please retry later."
+
+SQLSTATE: 08006
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05885: "client recover failed"
+
+SQLSTATE: 58000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05886: "records is NULL."
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05887: "out of memory of records."
+
+SQLSTATE: 53200
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05888: "dynamic workload record number is not correct!"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05889: "invalid retcode [%d]"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05890: "invalid paras."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05891 - GAUSS-05900
+
+<br/>
+
+GAUSS-05891: "option '%s' not recognized."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05892: "permission denied to create data source '%s'"
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05893: "data source '%s' already exists"
+
+SQLSTATE: 42710
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05894: "permission denied to change owner of data source '%s'"
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05895: "directory path contains illegal string: '%s'"
+
+SQLSTATE: 42602
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05896: "'%s' is not a directory, please check"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05897: "'%s' is a symlink, cannot be added as directory"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05898: "permission denied to create directory '%s'"
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05899: "directory '%s' is already used by an existing object"
+
+SQLSTATE: 42710
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05900: "permission denied to drop directory '%s'"
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/6-GAUSS-00501-GAUSS-00600.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/6-GAUSS-00501-GAUSS-00600.md
new file mode 100644
index 0000000000000000000000000000000000000000..0d18f57d37a7bf2ecbba71550810291dc1302fda
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/6-GAUSS-00501-GAUSS-00600.md
@@ -0,0 +1,724 @@
+---
+title: GAUSS-00501 - GAUSS-00600
+summary: GAUSS-00501 - GAUSS-00600
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-00501 - GAUSS-00600
+
+<br/>
+
+## GAUSS-00501 - GAUSS-00510
+
+<br/>
+
+### GAUSS-00501: "template database '%s' does not exist"
+
+SQLSTATE: 3D000
+
+错误原因: template1模板数据库不存在。
+
+解决办法: 数据库系统存在异常导致模板数据库template1丢失，请重启数据库或者通过手动创建模板数据库template1。
+
+### GAUSS-00502: "permission denied to copy database '%s'"
+
+SQLSTATE: 42501
+
+错误原因: 创建数据库语法中，如果原数据库不是模板数据库，当前用户角色没有权限创建数据库。
+
+解决办法: 创建数据库语法中，如果原数据库不是模板数据库，只有拥有CREATEDB权限的用户或系统管理员才可以创建新数据库，请确认用户权限是否正确。
+
+### GAUSS-00503: "invalid server encoding %d"
+
+SQLSTATE: 42809
+
+错误原因: 在创建数据库语法中，使用ENCODING encoding指定的编码格式无效。
+
+解决办法: "在创建数据库语法中，使用ENCODING encoding指定的编码格式必须出现在以下编码格式中: GBK、UTF8、Latin1
+
+### GAUSS-00504: "invalid locale name: '%s'"
+
+SQLSTATE: 42809
+
+错误原因: 在创建数据库时，指定的数据库字符集无效。
+
+解决办法: 在创建数据库语法中，指定新数据库使用的字符集必须与模板数据库的字符集匹配。请使用命令""show lc_collate;""检查模板数据库的字符集。
+
+### GAUSS-00505: "new encoding (%s) is incompatible with the encoding of the template database (%s)"
+
+SQLSTATE: 22023
+
+错误原因: 在创建数据库语法中，指定新数据库使用的字符编码与template0模板数据库的字符编码不匹配。
+
+解决办法: 在创建数据库语法中，指定新数据库使用的字符编码与template0模板数据库的字符编码必须一致。请使用命令"show server_encoding;"检查template0模板数据库的字符编码，并修改当前创建数据库指定的字符编码。
+
+### GAUSS-00506: "new collation (%s) is incompatible with the collation of the template database (%s)"
+
+SQLSTATE: 22023
+
+错误原因: 在创建数据库语法中，指定新数据库使用的字符集与template0模板数据库的字符集不匹配。
+
+解决办法: 在创建数据库语法中，指定新数据库使用的字符集与template0模板数据库的字符集必须一致，请使用命令"show lc_collate;"检查template0模板数据库的字符集，并修改当前创建数据库指定的字符集。
+
+### GAUSS-00507: "new LC_CTYPE (%s) is incompatible with the LC_CTYPE of the template database (%s)"
+
+SQLSTATE: 22023
+
+错误原因: 在创建数据库语法中，指定新数据库使用的字符分类与template0模板数据库的字符分类不匹配。
+
+解决办法: 在创建数据库语法中，指定新数据库使用的字符分类与template0模板数据库的字符分类必须一致，请使用命令"show lc_ctype;"检查template0模板数据库的字符分类，并修改当前创建数据库指定的字符分类。
+
+### GAUSS-00508: "pg_global cannot be used as default tablespace"
+
+SQLSTATE: 22023
+
+错误原因: 在创建数据库语法中，指定新数据库使用缺省的表空间tablespace为pg_global错误。
+
+解决办法: 在创建数据库语法中，指定新数据库使用缺省的表空间tablespace不能为pg_global，目前只支持缺省的表空间。
+
+### GAUSS-00509: "cannot assign new default tablespace '%s'"
+
+SQLSTATE: 0A000
+
+错误原因: 在创建数据库语法中，指定新数据库使用缺省的表空间tablespace为pg_global错误。
+
+解决办法: 在创建数据库语法中，指定新数据库使用除缺省的表空间和全局表空间以外的其他表空间tablespace时，请确认该表空间所在目录是否为有效的目录，如果为无效目录，请创建一个有效的目录。
+
+### GAUSS-00510: "database '%s' already exists"
+
+SQLSTATE: 42P04
+
+错误原因: 当前创建的数据库已存在。
+
+解决办法: 请使用命令"\\l"确认当前待创建的数据库是否已经存在，如果存在，请重新命名一个不存在的数据库。
+
+<br/>
+
+## GAUSS-00511 - GAUSS-00520
+
+<br/>
+
+### GAUSS-00511: "source database '%s' is being accessed by other users"
+
+SQLSTATE: 55006
+
+错误原因: 当前访问的数据库正在被其他用户访问会话。
+
+解决办法: 请检查当前访问的数据库是否正在被其他用户访问，这样会导致数据不一致的情况，需要关闭和退出其他用户访问，并重新尝试登录。
+
+### GAUSS-00512: "encoding '%s' does not match locale '%s'"
+
+SQLSTATE: 22023
+
+错误原因: 当前创建的数据库指定的字符编码与指定的字符分类得到的字符编码不匹配。
+
+解决办法: 请求确认当前创建的数据库指定的字符编码是否指定的字符分类得到的字符编码一致，如果不一致，请在重新创建数据时指定为一致。
+
+### GAUSS-00513: "database '%s' does not exist"
+
+SQLSTATE: 3D000
+
+错误原因: DROP DATABASE语法删除一个数据库时，该数据库不存在或者是一个无效的数据库。
+
+解决办法: DROP DATABASE语法删除一个数据库时，请确认当前删除的数据库是否为一个已经创建的有效的数据库。
+
+### GAUSS-00514: "cannot drop a template database"
+
+SQLSTATE: 42809
+
+错误原因: 试图删除模板数据库template0或template1，为非法操作。
+
+解决办法: 系统默认模板数据库template0或template1不能被删除，请重新指定需要删除的数据库。
+
+### GAUSS-00515: "cannot drop the currently open database"
+
+SQLSTATE: 55006
+
+错误原因: 当前待删除的数据库正在被其他用户打开，不能执行删除操作。
+
+解决办法: 请确认当前待删除的数据库是否正在被其他用户打开，并通知用户退出后再次尝试执行删除操作。
+
+### GAUSS-00516: "cannot drop the default database"
+
+SQLSTATE: 42809
+
+错误原因: 试图删除系统缺省的默认数据库postgres，为无效操作。
+
+解决办法: 系统缺省的默认数据库postgres不能被删除，请确认操作是否正确。
+
+### GAUSS-00517: "database '%s' is being accessed by other users"
+
+SQLSTATE: 55006
+
+错误原因: 当前待删除的数据库正在被其他用户访问。
+
+解决办法: 请检查当前待删除的数据库是否正在被其他用户访问，这样会导致数据不一致的情况，需要关闭和退出其他用户访问，并重新尝试删除该数据库。
+
+### GAUSS-00519: "permission denied to rename database"
+
+SQLSTATE: 42501
+
+错误原因: 当前用户没有权限修改数据库名称。
+
+解决办法: 请确认执行当前修改数据库名称操作的用户是否为数据库所有者权限的用户或管理员用户。
+
+### GAUSS-00520: "current database cannot be renamed"
+
+SQLSTATE: 0A000
+
+错误原因: 非法操作: 不能修改正在使用的数据库名称。
+
+解决办法: 请确认是否需要修改当前正在使用的数据库名称，该操作为非法操作，请勿修改正在使用的数据库名称。
+
+<br/>
+
+## GAUSS-00521 - GAUSS-00530
+
+<br/>
+
+### GAUSS-00521: "cannot change the tablespace of the currently open database"
+
+SQLSTATE: 55006
+
+错误原因: 通过ALTER DATABASE SET TABLESPACE语法修改数据库表空间时，该数据库正在被其他用户打开，不能执行当前操作。
+
+解决办法: 请确认当前待执行的修改数据库表空间操作中的数据库是否正在被其他用户打开，如果已被其他用户打开，请将数据库退出后再次尝试执行该操作。
+
+### GAUSS-00522: "some relations of database '%s' are already in tablespace '%s'"
+
+SQLSTATE: 55000
+
+错误原因: 通过ALTER DATABASE SET TABLESPACE语法修改数据库表空间时，该数据库的表空间目录下已经存在表、索引、视图等关系对象，不能执行当前操作。
+
+解决办法: 请确认当前待执行的修改数据库表空间操作中的数据库中是否已经存在表、索引、试图等关系对象，需要先删除已存在的对象后再次尝试执行该操作。
+
+### GAUSS-00523: "could not remove directory '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00524: "permission denied to change owner of database"
+
+SQLSTATE: 42501
+
+错误原因: 使用ALTER DATABASE name OWNER TO newowner语法修改数据库所有者时，当前用户没有权限执行该操作。
+
+解决办法: 使用ALTER DATABASE name OWNER TO newowner语法修改数据库所有者时，请确认当前用户是否为数据库所有者权限的用户或管理员用户，其他用户没有权限执行该操作。
+
+### GAUSS-00526: "could not create directory '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: "创建数据库的表空间时需要创建表空间对应的目录可能存在以下异常: 1.不是管理员用户，没有权限访问该目录；2.文件系统为只读；3.该目录已经存在；4.磁盘已满，没有足够的空间创建目录；5.硬件存在问题导致I/O错误；6.MogDB数据库系统内部错误。"
+
+解决办法: "创建数据库的表空间时需要创建表空间对应的目录存在异常，可以通过尝试如下方法排除问题: 1.确认是否为管理员用户或当前数据库创建权限；2.确认文件系统为只读，可以修改文件系统权限为可写和可执行；3.如果该目录已经存在，则不需要创建表空间；
+
+### GAUSS-00527: "could not stat directory '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 创建数据库的表空间时需要创建表空间对应的目录是一个无效的非法目录。
+
+解决办法: 确认创建数据库的表空间时需要创建表空间对应的目录名是否是一个有效的目录。
+
+### GAUSS-00528: "'%s' exists but is not a directory"
+
+SQLSTATE: 42809
+
+错误原因: 创建数据库的表空间时该表空间对应的目录无效。
+
+解决办法: 确认创建数据库的表空间时需要创建表空间对应的目录名是否是一个有效的目录。
+
+### GAUSS-00529: "Permission denied to create tablespace '%s'."
+
+SQLSTATE: 42501
+
+错误原因: 当前用户没有权限在数据库中创建一个新的表空间。
+
+解决办法: 只有系统管理员才能在数据库中创建一个新的表空间，请使用系统管理员权限执行创建表空间操作。
+
+### GAUSS-00530: "tablespace location cannot contain single quotes"
+
+SQLSTATE: 42602
+
+错误原因: 使用CREATE TABLESPACE tablespace_name …LOCATION语法指定表空间目录时，位置信息不能使用单引号标识。
+
+解决办法: 使用CREATE TABLESPACE tablespace_name …LOCATION语法指定表空间目录时，位置信息字符串必须用双引号标识。
+
+<br/>
+
+## GAUSS-00531 - GAUSS-00540
+
+<br/>
+
+### GAUSS-00531: "tablespace location must be an absolute path"
+
+SQLSTATE: 42P17
+
+错误原因: 使用CREATE TABLESPACE tablespace_name …LOCATION语法指定表空间目录时，位置信息指示的路径错误。
+
+解决办法: 使用CREATE TABLESPACE tablespace_name …LOCATION语法指定表空间目录时，位置信息字符串指定的目录必须是绝对路径。
+
+### GAUSS-00532: "tablespace location '%s' is too long"
+
+SQLSTATE: 42P17
+
+错误原因: 使用CREATE TABLESPACE tablespace_name …LOCATION语法指定表空间目录长度超过了最大长度1024。
+
+解决办法: 使用CREATE TABLESPACE tablespace_name …LOCATION语法指定表空间目录时，位置信息字符串指定的目录长度必须小于系统规定的最大长度1024。
+
+### GAUSS-00533: "unacceptable tablespace name '%s'"
+
+SQLSTATE: 42939
+
+错误原因: 使用CREATE TABLESPACE tablespace_name创建表空间时，使用了非法的表空间名称。
+
+解决办法: 使用CREATE TABLESPACE tablespace_name创建表空间时，表空间名称不能和数据库中的其他表空间重名，且名称不能以"pg"开头，这样的名称留给系统表空间使用。
+
+### GAUSS-00534: "tablespace '%s' already exists"
+
+SQLSTATE: 42710
+
+错误原因: 当前创建的表空间名称已经存在导致创建表空间失败。
+
+解决办法: 请使用命令"\\db"确认当前待创建的表空间是否已经存在，如果存在，请重新命名一个不存在的表空间名称。
+
+### GAUSS-00535: "tablespaces are not supported on this platform"
+
+SQLSTATE: 0A000
+
+错误原因: 不支持表空间。
+
+解决办法: 建议不要使用表空间。
+
+### GAUSS-00536: "Tablespace '%s' does not exist."
+
+SQLSTATE: 42704
+
+错误原因: 通过DROP TABLESPACE删除的表空间不存在。
+
+解决办法: 请通过"\\db"查询待删除的表空间名称是否存在，系统只支持删除存在的表空间。
+
+### GAUSS-00537: "tablespace '%s' is used by partitioned table '%s'"
+
+SQLSTATE: 0A000
+
+错误原因: 试图删除用于分区表的表空间为非法操作。
+
+解决办法: 请确认待删除的表空间是否被分区表使用，如果被分区表使用则系统不允许删除。
+
+### GAUSS-00538: "tablespace '%s' is not empty"
+
+SQLSTATE: 55000
+
+错误原因: 删除表空间时候表空间不为空。
+
+解决办法: 请确认删除表空间时，表空间为空才能正常删除。
+
+### GAUSS-00539: "directory '%s' does not exist"
+
+SQLSTATE: 58P01
+
+错误原因: 在创建表空间时表空间目录"$PGDATA/pg_tblspc/"不存在。
+
+解决办法: 在创建表空间时需要确认表空间目录"$PGDATA/pg_tblspc/"是否存在，如果不存在，需要重启数据库或单个节点。
+
+### GAUSS-00540: "could not set permissions on directory '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 在创建表空间时，设置表空间目录"$PGDATA/pg_tblspc/"可读可写可执行权限失败。
+
+解决办法: 创建数据库的表空间时设置表空间目录"$PGDATA/pg_tblspc/"目录权限存在异常，可以通过尝试如下方法排除问题: 1.确认是否为管理员用户或当前数据库创建权限；2.确认文件系统为只读，可以修改文件系统权限为可写和可执行；3.如果该目录已经存在，则不需要创建表空间。
+
+<br/>
+
+## GAUSS-00541 - GAUSS-00550
+
+<br/>
+
+### GAUSS-00541: "directory '%s' already in use as a tablespace"
+
+SQLSTATE: 55006
+
+错误原因: 为表空间所创建的目录已存在。
+
+解决办法: 将表空间定义在其他目录下。
+
+### GAUSS-00542: "could not remove symbolic link '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 移除符号连接文件失败。
+
+解决办法: 确认符号连接指向的有效的文件。
+
+### GAUSS-00543: "could not create symbolic link '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 创建符号连接文件失败。
+
+解决办法: 通过检查错误码，可以判断文件操作错误原因（无权限、磁盘满、文件已存在等），并进行相应处理。
+
+### GAUSS-00544: "tablespace '%s' does not exist"
+
+SQLSTATE: 42704
+
+错误原因: 表空间不存在。
+
+解决办法: 检查系统表pg_tablespace中相应表空间是否存在。
+
+### GAUSS-00546: "could not create tablespace directory '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 创建表空间失败。
+
+解决办法: 通过检查错误码，可以判断文件操作错误原因（无权限、磁盘满、文件已存在等），并进行相应处理。
+
+### GAUSS-00547: "could not access directory '%s': %m"
+
+SQLSTATE: XX000
+
+错误原因: 访问表空间目录失败。
+
+解决办法: 通过检查错误码，可以判断文件操作错误原因（无权限、磁盘满、文件已存在等），并进行相应处理。
+
+### GAUSS-00548: "tblspc_redo: unknown op code %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00549: "'%s' is an aggregate function"
+
+SQLSTATE: 42809
+
+错误原因: 1.使用DROP FUNCTION删除聚集函数失败；2.使用ALTER FUNCTION修改聚集函数失败；3.pg_get_functiondef获取聚集函数定义失败。
+
+解决办法: 1.可以使用DROP AGGREGATE删除聚集函数；2.可以使用ALTER AGGREGATE修改聚集函数；3.可以查看系统表pg_aggregate。
+
+### GAUSS-00550: "unexpected object type (%d)"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-00551 - GAUSS-00560
+
+<br/>
+
+### GAUSS-00551: "could not determine which collation to use for view column '%s'"
+
+SQLSTATE: 42P22
+
+错误原因: 对于视图的列无法决策使用哪种排序规则。
+
+解决办法: 使用COLLATE子句指定排序规则。
+
+### GAUSS-00552: "view must have at least one column"
+
+SQLSTATE: 42P16
+
+错误原因: 定义视图指定的列数少于1个。
+
+解决办法: 定义视图至少需要包含一列。
+
+### GAUSS-00553: "'%s' is not a view"
+
+SQLSTATE: 42809
+
+错误原因: 对象不是一个视图。
+
+解决办法: 检查要操作的对象是否是一个视图。
+
+### GAUSS-00554: "cannot drop columns from view"
+
+SQLSTATE: 42P16
+
+错误原因: 删除视图中的列失败。
+
+解决办法: 视图定义后不能删除其中的列。
+
+### GAUSS-00555: "cannot change name of view column '%s' to '%s'"
+
+SQLSTATE: 42P16
+
+错误原因: 修改视图中的列名失败。
+
+解决办法: 视图定义后不能其中的列名。
+
+### GAUSS-00556: "cannot change data type of view column '%s' from %s to %s"
+
+SQLSTATE: 42P16
+
+错误原因: CREATE OR REPLACE VIEW定义视图时，新视图和现有视图中列的数据类型不一致。
+
+解决办法: 保证新视图和现有视图中列的数据类型一致。
+
+### GAUSS-00557: "unexpected parse analysis result"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00559: "views must not contain data-modifying statements in WITH"
+
+SQLSTATE: 0A000
+
+错误原因: 定义视图语句中包含WITH子句。
+
+解决办法: 保证获取结果的query是单SELECT语句。
+
+### GAUSS-00560: "CREATE VIEW specifies more column names than columns"
+
+SQLSTATE: 42601
+
+错误原因: 定义视图指定的列比返回结果的列数多。
+
+解决办法: 保证指定列数不多于返回结果的列数。
+
+<br/>
+
+## GAUSS-00561 - GAUSS-00570
+
+<br/>
+
+### GAUSS-00561: "views cannot be unlogged because they do not have storage"
+
+SQLSTATE: 42601
+
+错误原因: 定义视图时指定为UNLOGGED。
+
+解决办法: 视图没有真正的存储，定义视图时不能指定为UNLOGGED。
+
+### GAUSS-00562: "unrecognized value for EXPLAIN option '%s': '%s'"
+
+SQLSTATE: 22023
+
+错误原因: EXPLAIN FORMAT的参数无法识别。
+
+解决办法: FORMAT参数只能是text、xml、json、yaml之一。
+
+### GAUSS-00563: "unrecognized EXPLAIN option '%s'"
+
+SQLSTATE: 42601
+
+错误原因: EXPLAIN的参数无法识别。
+
+解决办法: EXPLAIN支持的参数包括: analyze、verbose、costs、buffers、nodes、num_nodes、timing、CPU、detail、performance和format。
+
+### GAUSS-00564: "EXPLAIN option BUFFERS requires ANALYZE"
+
+SQLSTATE: 22023
+
+错误原因: EXPLAIN BUFFERS没有同时指定ANALYZE。
+
+解决办法: EXPLAIN BUFFERS需要同时指定ANALYZE。
+
+### GAUSS-00565: "EXPLAIN option CPU requires ANALYZE"
+
+SQLSTATE: 22023
+
+错误原因: EXPLAIN CPU没有同时指定ANALYZE。
+
+解决办法: EXPLAIN CPU需要同时指定ANALYZE。
+
+### GAUSS-00566: "EXPLAIN option DETAIL requires ANALYZE"
+
+SQLSTATE: 22023
+
+错误原因: EXPLAIN DETAIL没有同时指定ANALYZE。
+
+解决办法: EXPLAIN DETAIL需要同时指定ANALYZE。
+
+### GAUSS-00567: "EXPLAIN option TIMING requires ANALYZE"
+
+SQLSTATE: 22023
+
+错误原因: EXPLAIN TIMING没有同时指定ANALYZE。
+
+解决办法: EXPLAIN TIMING需要同时指定ANALYZE。
+
+### GAUSS-00568: "EXPLAIN %s requires ANALYZE"
+
+SQLSTATE: 22023
+
+错误原因: EXPLAIN CREATE TABLE AS SELECT或EXPLAIN SELECT INTO没有指定ANALYZE。
+
+解决办法: EXPLAIN CREATE TABLE AS SELECT或EXPLAIN SELECT INTO需要指定ANALYZE。
+
+### GAUSS-00569: "no tlist entry for key %d"
+
+SQLSTATE: XX000
+
+错误原因: 生成的计划问题。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00570: "cache lookup failed for index %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统表缓存查找索引信息失败。
+
+解决办法: 检查索引名称是否正确。
+
+<br/>
+
+## GAUSS-00571 - GAUSS-00580
+
+<br/>
+
+### GAUSS-00571: "unrecognized DISCARD target: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00572: "function '%s' was not called by trigger manager"
+
+SQLSTATE: 39P01
+
+错误原因: 函数没有被触发器管理器调用。
+
+解决办法: 保证函数作为AFTER ROW trigger被调用。
+
+### GAUSS-00573: "function '%s' must be fired AFTER ROW"
+
+SQLSTATE: 39P01
+
+错误原因: 函数在AFTER ROW触发器触发之前就被调用。
+
+解决办法: AFTER ROW触发器中的函数应该在触发器触发之后被调用。
+
+### GAUSS-00574: "function '%s' must be fired for INSERT or UPDATE"
+
+SQLSTATE: 39P01
+
+错误原因: 触发器没有被INSERT/UPDATE语句触发。
+
+解决办法: 触发器必须被INSERT/UPDATE语句触发。
+
+### GAUSS-00575: "Permission denied to create role with option UNENCRYPTED."
+
+SQLSTATE: XX000
+
+错误原因: CREATE ROLE指定参数UNENCRYPTED报错。
+
+解决办法: 密码必须加密，禁止使用密码的明文。
+
+### GAUSS-00579: "Permission denied to create role."
+
+SQLSTATE: 42501
+
+错误原因: 没有权限创建用户。
+
+解决办法: 检查用户权限，是否可以创建用户，权限说明参见zh-cn_topic_0237121098.html。
+
+### GAUSS-00580: "Separation of privileges is used,user can't be created because of too many privileges."
+
+SQLSTATE: 42501
+
+错误原因: 使用三权分立，为用户指定的权限太多。
+
+解决办法: 确认三权分立下为用户指定的权限没有超出范围。
+
+<br/>
+
+## GAUSS-00581 - GAUSS-00590
+
+<br/>
+
+### GAUSS-00581: "role name '%s' is reserved"
+
+SQLSTATE: 42939
+
+错误原因: 用户名是保留关键字。
+
+解决办法: 用户名不能是public或none。
+
+### GAUSS-00582: "role '%s' already exists"
+
+SQLSTATE: 42710
+
+错误原因: 创建的用户已存在。
+
+解决办法: 使用新的用户名。
+
+### GAUSS-00584: "The password does not satisfy the complexity requirement"
+
+SQLSTATE: XX000
+
+错误原因: 密码不符合复杂性要求。
+
+解决办法: "请参照密码规则进行修改: 1. 不能和用户名相同。2. 至少包含大写字母（A-Z），小写字母（a-z），数字（0-9），非字母数字字符（限定为~!@#$%^&*()-_=+\|[{}];:,<.>/?）四类字符中的三类字符"，且不少于8个字符。
+
+### GAUSS-00588: "The password could not be NULL."
+
+SQLSTATE: XX000
+
+错误原因: 密码为空。
+
+解决办法: 密码不允许为空。
+
+### GAUSS-00589: "unacceptable user name: fail to create same name schema for user '%s'"
+
+SQLSTATE: 42939
+
+错误原因: 用户名非法，创建同名的schema失败。
+
+解决办法: 用户名不能以'pg_'开头，'pg_'开头主要用作系统模式。
+
+### GAUSS-00590: "the relation pg_user_status is invalid"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-00591 - GAUSS-00600
+
+<br/>
+
+### GAUSS-00591: "role '%s' does not exist"
+
+SQLSTATE: 42704
+
+错误原因: 用户不存在。
+
+解决办法: 查看系统表pg_roles确认用户是否存在。
+
+### GAUSS-00593: "Permission denied to change privilege of the initial account."
+
+SQLSTATE: 42501
+
+错误原因: 修改初始用户权限失败。
+
+解决办法: 查看系统表确认当前用户是否有权限。
+
+### GAUSS-00594: "Permission denied to change password of the initial account."
+
+SQLSTATE: 42501
+
+错误原因: 修改初始用户密码失败。
+
+解决办法: 查看系统表确认当前用户是否有权限。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/60-GAUSS-05901-GAUSS-06000.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/60-GAUSS-05901-GAUSS-06000.md
new file mode 100644
index 0000000000000000000000000000000000000000..02c62fe14762f1dc586ece7616c65bf42d0814c8
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/60-GAUSS-05901-GAUSS-06000.md
@@ -0,0 +1,764 @@
+---
+title: GAUSS-05901 - GAUSS-06000
+summary: GAUSS-05901 - GAUSS-06000
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-05901 - GAUSS-06000
+
+<br/>
+
+## GAUSS-05901 - GAUSS-05910
+
+<br/>
+
+GAUSS-05901: "permission denied to change owner of directory"
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05902: "could not open extension control file: %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05903: "extension '%s' already exists in schema '%s'"
+
+SQLSTATE: 42710
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05904: "extcondition is not a 1-D Oid array"
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05905: "extension is null"
+
+SQLSTATE: XX005
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05906: "EXPLAIN PLAN does not support on datanode or single node."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05907: "EXPLAIN option 'PLAN' can not work with other options."
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05908: "EXPLAIN %s is not supported when declaring a cursor."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05909: "invalid value for parameter explain_perf_mode."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05910: "unrecognized value for EXPLAIN option 'format'."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05911 - GAUSS-05920
+
+<br/>
+
+GAUSS-05911: "u_sess->instr_cxt.global_instr is NULL"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05912: "statement_id is too long. Input statement_id length=%u, however max length=%d."
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05913: "Relation 'plan_table_data' does not exist"
+
+SQLSTATE: 42602
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05914: "Do not specify any information for CREATE POLICY '%s' ON '%s'"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05915: "Create row level security policy '%s' failed, because it will result in infinite recursion for DML queries"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05916: "row level policy '%s' for table '%s' already exists"
+
+SQLSTATE: 42710
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05917: "Num of row level policies for relation should less than or equal to %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05918: "Do not specify any information for ALTER POLICY '%s' ON '%s'"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05919: "row level security policy '%s' for relation '%s' does not exists"
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05920: "Alter row level security policy '%s' failed, because it will result in infinite recursion for DML queries"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05921 - GAUSS-05930
+
+<br/>
+
+GAUSS-05921: "row level policy '%s' for relation '%s' already exists"
+
+SQLSTATE: 42710
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05922: "unrecognized row level security policy command"
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05923: "too many roles specified in SQL statement."
+
+SQLSTATE: 54000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05924: "%s not implemented"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05925: "could not write to staging temporary file while exporting segment %s"
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05926: "could not write to local temporary buffile: %m"
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05927: "Write-Only table's output directory %s is not empty"
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05928: "could not rewind OBS exporting temporary file: %m"
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05929: "must be system admin to CREATE TEXT SEARCH DICTIONARY"
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05930: "CREATE TEXT SEARCH DICTIONARY in a temp namespace is not supported"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05931 - GAUSS-05940
+
+<br/>
+
+GAUSS-05931: "Not allowed to alter built-in text search dictionary"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05932: "Not allowed to drop built-in text search dictionary"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05933: "Not allowed Template parameter in alter text search dictionary"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05934: "env $GAUSSHOME not found, please set it first"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05935: "failed to bind fd(%d) to ssl"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05936: "m_fd + 1 cannot be greater than FD_SETSIZE"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05937: "The peer GDS has performed an orderly shutdown on current connection."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05938: "exception from GDS '%s':%m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05939: "Message size exceeds the maximum allowed (%d)"
+
+SQLSTATE: OP002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05940: "Invalid command to serialize."
+
+SQLSTATE: OP002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05941 - GAUSS-05950
+
+<br/>
+
+GAUSS-05941: "Unexpected length of data coming supposedly from GDS. Could be an forged attack package."
+
+SQLSTATE: DB001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05942: "Failed to _ReadError in CMD_TYPE_ERROR, could be a forged package."
+
+SQLSTATE: DB001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05943: "Failed to _ReadFileSwitch in CMD_TYPE_FILE_SWITCH, could be a forged package."
+
+SQLSTATE: DB001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05944: "Failed to _ReadResponse in CMD_TYPE_RESPONSE, could be a forged package."
+
+SQLSTATE: DB001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05945: "The corresponding GDS is of an older version. Please upgrade GDS to match the server version."
+
+SQLSTATE: DB001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05946: "Failed to _ReadResult in CMD_TYPE_QUERY_RESULT_V1, could be a forged package."
+
+SQLSTATE: DB001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05947: "Hash bkt dir '%s' not exists:%m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05948: "could not create directory '%s':%m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05949: "'%s' exists but is not a directory."
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05950: "permission denied to create tablespace in security mode"
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05951 - GAUSS-05960
+
+<br/>
+
+GAUSS-05951: "Create tablespace with absolute location can't be allowed"
+
+SQLSTATE: 42P17
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05952: "tablespace location can only be formed of 'a~z', 'A~Z', '0~9', '-', '_'"
+
+SQLSTATE: 42P17
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05953: "relative location can only be formed of 'a~z', 'A~Z', '0~9', '-', '_' and two level directory at most"
+
+SQLSTATE: 42P17
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05954: "The relative location can not be null"
+
+SQLSTATE: 42P17
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05955: "could not open pg_tblspc directory"
+
+SQLSTATE: 42P17
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05956: "could not get '%s' status"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05957: "'%s' is not symlink, please check and clean the remains in '%s'"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05958: "target of symbolic link '%s' doesn't exist"
+
+SQLSTATE: 42P17
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05959: "target of symbolic link '%s' isn't directory"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05960: "find conflict linkpath '%s' in pg_tblspc, location '%s'"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05961 - GAUSS-05970
+
+<br/>
+
+GAUSS-05961: "permission denied to alter tablespace in security mode"
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05962: "It is unsupported to reset 'filesystem' option."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05963: "It is unsupported to alter general tablespace to hdfs tablespace."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05964: "Tablespace '%u' does not exist."
+
+SQLSTATE: 58P01
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05965: "Can not get tablespace size with SnapshotNow after try 3 times."
+
+SQLSTATE: P0002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05970: "conflicting or redundant option: 'resource pool'"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05971 - GAUSS-05980
+
+<br/>
+
+GAUSS-05971: "conflicting or redundant option: 'user group default'"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05972: "conflictiong or redundant option: 'spill space'"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05975: "Can not create role with resource pool (%s) with foreign users option."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05976: "parent cannot be itself."
+
+SQLSTATE: 0P000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05977: "Role '%s': object not defined."
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05981 - GAUSS-05990
+
+<br/>
+
+GAUSS-05981: "Independent user is not supported."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05982: "Independent user cannot have sysadmin, auditadmin, vcadmin, createrole, monadmin and opradmin attributes."
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05983: "Failed to Generate the random number, errcode:%u"
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05984: "Can not alter role with resource pool (%s) with foreign users option."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05985: "resource pool of role '%s' does not exist."
+
+SQLSTATE: 42P26
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05989: "Can not alter Role '%s' to vcadmin."
+
+SQLSTATE: 0LP01
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-05991 - GAUSS-06000
+
+<br/>
+
+GAUSS-05991: "Only user himself can remove his own independent attribute."
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05992: "Only independent user himself can alter his own password."
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05993: "Only system admin can enable user's password."
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05994: "Only independent user himself can enable his own password."
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05995: "Only system admin can disable user's password."
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05996: "Only independent user himself can disable his own password."
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05997: "resource pool of role '%s' does not exsist."
+
+SQLSTATE: 42P26
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05998: "Only independent user himself can decide his own membership."
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-05999: "Role '%s' can not be granted across virtual clusters."
+
+SQLSTATE: 0LP01
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06000: "While get super user, invalid role OID: %u"
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/61-GAUSS-06001-GAUSS-06100.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/61-GAUSS-06001-GAUSS-06100.md
new file mode 100644
index 0000000000000000000000000000000000000000..ff1f961d2d0cf694fba764e849a3cf1383decbb7
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/61-GAUSS-06001-GAUSS-06100.md
@@ -0,0 +1,852 @@
+---
+title: GAUSS-06001 - GAUSS-06100
+summary: GAUSS-06001 - GAUSS-06100
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-06001 - GAUSS-06100
+
+<br/>
+
+## GAUSS-06001 - GAUSS-06010
+
+<br/>
+
+GAUSS-06001: "password encryption failed"
+
+SQLSTATE: 28P01
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06002: "cache lookup failed for role with oid %u"
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06003: "%s is not supported for using here, just support template0"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06005: "could not drop database while ddl delay function is enabled"
+
+SQLSTATE: 55006
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06006: "database '%s' is used by a logical decoding slot"
+
+SQLSTATE: 55006
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06007: "Database '%s' is being accessed by other users. You can stop all connections by command: 'clean connection to all force for database XXXX;' or wait for the sessions to end by querying view: 'pg_stat_activity'."
+
+SQLSTATE: 55006
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06008: "dbase_redo: unknown op code %hhu"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06009: "Not support alter cross-database private pbject, please switch to '%s' and run this command"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06010: "permission denied to create foreign table in security mode"
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06011 - GAUSS-06020
+
+<br/>
+
+GAUSS-06011: "Failed to create foreign table '%s'."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06012: "The schema 'dbe_perf' doesn't allow to drop"
+
+SQLSTATE: OP001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06013: "The schema 'snapshot' doesn't allow to drop"
+
+SQLSTATE: OP001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06014: "The schema '%s' doesn't allow to rename"
+
+SQLSTATE: OP001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06015: "It is not supported to rename schema '%s' which includes timeseries table '%s'."
+
+SQLSTATE: 42939
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06016: "column/timeseries store unsupport constraint '%s'"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06017: " period must smaller than ttl."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06018: "It is unsupported to create row/cstore non-temporary/non-unlogged table in hadoop enviroment."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06019: "It is unsupported to create unlogged table and temporary table on DFS tablespace."
+
+SQLSTATE: 42P16
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06020: "It is unsupported to create table with to group option on DFS tablespace."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06021 - GAUSS-06030
+
+<br/>
+
+GAUSS-06021: "It is unsupported to create foreign table with to group option."
+
+SQLSTATE: 42P16
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06022: "Only support hash/replication distribution for dfs table."
+
+SQLSTATE: 42P16
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06023: "Partition can not be created on DFS tablespace.Only table-level tablespace can be DFS.DFS table only support partition strategy '%s' feature."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06024: " unsupported persistency for timeseries table."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06025: "Only support hash distribution for timeseries table."
+
+SQLSTATE: 42P16
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06026: "kvtype of '%s' must be defined when using timeseries."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06027: "TIMESERIES must have one and only one time column."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06028: "type '%s' is not supported in timeseries store"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06029: "Cannot use orientation is timeseries when enable_tsdb is off."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06030: "Only support one partition Key."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06031 - GAUSS-06040
+
+<br/>
+
+GAUSS-06031: "type '%s' does not exist."
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06032: " Partition Key must be of type TIMESTAMP(TZ) when using ttl or period."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06033: " Partition Key must be of kv type TSTAG."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06034: "ON COMMIT only support PRESERVE ROWS or DELETE ROWS option"
+
+SQLSTATE: 42P16
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06035: "Unsupport the dfs table in this version."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06036: "Only support one partial cluster key for dfs/cstore table."
+
+SQLSTATE: 42P16
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06037: "hash bucket table not supported in current version!"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06038: "Local OID column not supported in column/timeseries store tables."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06039: "column constraint on postgres foreign tables are not supported"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06040: "relation type column on postgres foreign tables are not supported"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06041 - GAUSS-06050
+
+<br/>
+
+GAUSS-06041: "The table %s do not support hash bucket"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06042: "Invalid Oid while setting new relfilenode for ts aux table."
+
+SQLSTATE: 42602
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06043: "NOT-SUPPORT: Not support TRUNCATE multiple objects different nodegroup"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06044: "rel %s can not truncate during redis."
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06045: "column '%s' has a kvtype parameter conflict"
+
+SQLSTATE: 42804
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06046: "RENAME SEQUENCE is not yet supported."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06047: "cannot find timeseries aux table (or index). timeseries table oid: %u"
+
+SQLSTATE: OP001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06048: "This ALTER command is not support in timeseries store."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06049: "alter row table tablespace cannot run inside a transaction block"
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06050: "type '%s' is not supported in DFS table."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06051 - GAUSS-06060
+
+<br/>
+
+GAUSS-06051: "It's not supported to add column with default value for timeseries tables."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06052: "It's not supported to alter table add column default with nextval expression."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06053: "It is not supported on DFS table. The detailed reasons are the followings:"
+
+SQLSTATE: 42P16
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06054: "cannot drop TSTime column '%s' from timeseries table"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06055: "unrecognized table type: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06056: "cannot alter column type to '%s'"
+
+SQLSTATE: 42P16
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06057: "PSort %u should depend on only one index relation but not %ld."
+
+SQLSTATE: OP002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06059: "no perm space is available for the targeted owner"
+
+SQLSTATE: 53000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06060: "no perm space is available for the targeted user group"
+
+SQLSTATE: 53000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06061 - GAUSS-06070
+
+<br/>
+
+GAUSS-06061: "no temp space is available for the targeted owner"
+
+SQLSTATE: 53000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06062: "no temp space is available for the targeted user group"
+
+SQLSTATE: 53000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06063: "can not specify 'PARTITION FOR (value,,,)' for 'MOVE PARTITION CLAUSE'"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06064: "invalid partition node type in 'MOVE PARTITION CLAUSE'"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06065: "fail to remote read page, data corrupted in network"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06066: "invalid page in block %u of relation %s"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06067: "unknown type %u for ALTER TABLE ROW LEVEL SECURITY"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06068: "cache lookup failed for relation '%s'"
+
+SQLSTATE: 29P01
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06069: "unexpected identity type %u"
+
+SQLSTATE: XX006
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06070: "cannot use non-unique index '%s' as replica identity"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06071 - GAUSS-06080
+
+<br/>
+
+GAUSS-06071: "cannot use expression index '%s' as replica identity"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06072: "cannot use partial index '%s' as replica identity"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06073: "cannot use invalid index '%s' as replica identity"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06074: "internal column %d in unique index '%s'"
+
+SQLSTATE: 55000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06075: "index '%s' cannot be used as replica identity because column '%s' is nullable"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06076: "The obs foreign partition table cannot support on text, csv, carbondata format."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06077: "The obs foreign table has column type bytea, cannot support on orc format."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06078: "Invalid option '%s'"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06079: "There's dependent sequence, but ALTER SEQUENCE SET SCHEMA is not yet supported."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06080: "can't add partition bacause the relation %s has unusable local index"
+
+SQLSTATE: 42P17
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06081 - GAUSS-06090
+
+<br/>
+
+GAUSS-06081: "can't merge partition bacause partition %s has unusable local index"
+
+SQLSTATE: 42P17
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06082: "ALTER TABLE EXCHANGE requires both ordinary table and partitioned table to have the same hashbucket option(on or off)"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06083: "the kv storage type of column mismatch in ALTER TABLE EXCHANGE PARTITION"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06084: "cache lookup failed for relaton %u"
+
+SQLSTATE: 29P01
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06085: "can't split partition bacause relation %s has unusable local index"
+
+SQLSTATE: 42P17
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06086: "the partition oid(%u) of partition name (%s) is not found in partitioned table(%u)."
+
+SQLSTATE: P0002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06087: "Un-supported feature"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06088: "Cannot find a valid job_id."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06089: "cannot find timeseries aux table (or index). search name: %s"
+
+SQLSTATE: OP001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06090: "Unable to create partition policy when enable_tsdb is off."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06091 - GAUSS-06100
+
+<br/>
+
+GAUSS-06091: "%s does not have partition !"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06092: "cannot create partiton policy for aux table."
+
+SQLSTATE: OP001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06093: "Unable to alter partition policy when enable_tsdb is off."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06094: "The function's %s %u dismatch the type %u"
+
+SQLSTATE: 42804
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06095: "The index table does not support verify on cascade mode."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06096: "Non-table objects do not support verify."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06097: "The hdfs table does not support verify."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06098: "The temporary/unlog table does not support verify."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06099: "The important catalog table %s.%s corrupts, the node is %s, please fix it."
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06100: "pg_class entry for relid %u vanished during updating TotalRows"
+
+SQLSTATE: 2F000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/62-GAUSS-06101-GAUSS-06200.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/62-GAUSS-06101-GAUSS-06200.md
new file mode 100644
index 0000000000000000000000000000000000000000..72deedbbdcd18ea6b1013938840d98e12acfc540
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/62-GAUSS-06101-GAUSS-06200.md
@@ -0,0 +1,860 @@
+---
+title: GAUSS-06101 - GAUSS-06200
+summary: GAUSS-06101 - GAUSS-06200
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-06101 - GAUSS-06200
+
+<br/>
+
+## GAUSS-06101 - GAUSS-06110
+
+<br/>
+
+GAUSS-06101: "return type '%s' must be in installation group"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06102: "fencedmode function cannot accept shell type %s"
+
+SQLSTATE: 42P13
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06103: "parameterCount is invalid %d"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06104: "argument type '%s' must be in installation group"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06105: "fencedmode could not be fenced"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06106: "User defined window function only support INTERNAL language."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06107: "User defined window function only support INTERNAL window function"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06108: "JAVA UDF is not yet supported in current version."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06109: "Java UDF dose not support NOT FENCED functions."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06110: "the builtin function can not be removed,its function oid is '%u'"
+
+SQLSTATE: 42P13
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06111 - GAUSS-06120
+
+<br/>
+
+GAUSS-06111: "the builtin function can not be renamed,its function oid is '%u'"
+
+SQLSTATE: 42P13
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06112: "function '%s' is a builtin function,its owner can not be changed"
+
+SQLSTATE: 42P13
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06113: "ownerId change failed for function %u, because it is a builtin function."
+
+SQLSTATE: 42P13
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06114: "function '%s' is a builtin function,it can not be altered"
+
+SQLSTATE: 42P13
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06115: "Do not support package for ALTER FUNCTION."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06116: "set return type failed for function %u, because it is a builtin function."
+
+SQLSTATE: 42P13
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06117: "set argument type failed for function %u, because it is a builtin function."
+
+SQLSTATE: 42P13
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06118: "namespace change failed for function %u, because it is a builtin function."
+
+SQLSTATE: 42P13
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06119: "expected none dependency record for partition's CUDesc/Delta table, found %ld"
+
+SQLSTATE: OP002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06120: "Failed on finding partitioned tuple!"
+
+SQLSTATE: XX005
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06121 - GAUSS-06130
+
+<br/>
+
+GAUSS-06121: "invalid nodeId: %s(%d)"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06123: "could not open relation %s(%u) on node %s."
+
+SQLSTATE: 42P01
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06124: "Both table should have the same hashbucket option(on or off)"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06125: "analyze prefetch block list can not be NULL"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06126: "records n should not be zero"
+
+SQLSTATE: 22012
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06127: "Multi-columns statistic does not support hist/corr/mcelem/dechist"
+
+SQLSTATE: 42P10
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06128: "COPY_OBS does not implement in CopySendEndOfRow"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06129: "could not get data from COPY source"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06130: "copy from stdin failed because receive close conn message type 0x%02X"
+
+SQLSTATE: 08P01
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06131 - GAUSS-06140
+
+<br/>
+
+GAUSS-06131: "Cannot use OS-reserved file as COPY destination."
+
+SQLSTATE: 42602
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06132: "COPY to or from a file is prohibited for security concerns"
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06133: "could not open header file '%s': %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06134: "'%s' is not a valid EOL string, EOL string must not be empty"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06134: "'%s' is not a valid EOL string, EOL string must not be empty"
+
+SQLSTATE: 无
+
+错误原因: 自定义换行符不能为空。
+
+解决办法: 请检查指定的自定义换行符，确保自定义换行符不为空。
+
+GAUSS-06135: "'%s' is not a valid EOL string, EOL string must not exceed the maximum length (10 bytes)"
+
+SQLSTATE: 无
+
+错误原因: 自定义换行符超出最大长度（10字节）。
+
+解决办法: 请检查指定的自定义换行符的长度，确保自定义换行符的长度不超出最大长度。
+
+GAUSS-06136: "COPY delimiter cannot contain user-define EOL string"
+
+SQLSTATE: 无
+
+错误原因: 分隔符不能包含自定义换行符。
+
+解决办法: 请检查分隔符和换行符，确保分隔符不包含自定义换行符。
+
+GAUSS-06137: "COPY null representation cannot contain user-define EOL string"
+
+SQLSTATE: 无
+
+错误原因: NULL值不能包含自定义换行符。
+
+解决办法: 请检查NULL值，确保NULL值不包含自定义换行符。
+
+GAUSS-06138: "EOL string '%s' cannot contain any characters in'%s'"
+
+SQLSTATE: 无
+
+错误原因: 自定义换行符不能包含以下字符。
+
+解决办法: 请检查自定义换行符，确保不包含上述字符。
+
+GAUSS-06139: "EOL specification can not be used with non-text format using COPY FROM or READ ONLY foreign table"
+
+SQLSTATE: 无
+
+错误原因: 自定义换行符不能用于非TEXT格式的copy导入或只读外表。
+
+解决办法: 请检查copy导入或只读外表的设置的文件格式，确保为TEXT格式。
+
+GAUSS-06140: "EOL specification can not be used with non-text format using COPY TO or WRITE ONLY foreign table except 0x0D0A and 0x0A"
+
+SQLSTATE: 无
+
+错误原因: 自定义换行符不能用于非TEXT格式的copy导出或只写外表，但是允许自定义换行符0x0D0A和0x0A。
+
+解决办法: 请检查copy导出或只写外表的设置的文件格式，确保为TEXT格式。
+
+<br/>
+
+## GAUSS-06141 - GAUSS-06150
+
+<br/>
+
+GAUSS-06141: "out_filename_prefix is only allowed in write-only foreign tables"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06142: "out_fix_alignment is only allowed in write-only foreign tables"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06143: "COPY does not support subtransactions or exceptions."
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06144: "must be system admin to execute 'COPY from log errors data' "
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06145: "Unable to open %s.%s table for COPY FROM error logging."
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06146: "The column definition of %s.%s table is not as intended."
+
+SQLSTATE: OP001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06147: "Don't suppport COPY FROM table with INSERT triggers"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06148: "do not support system admin to COPY from %s"
+
+SQLSTATE: 42602
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06149: "bulkload illegal chars conversion is just allowed for char type attribute, the original character with byte sequence %s in encoding '%s' has no equivalent in encoding '%s'"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06150: "bulkload illegal chars conversion is just allowed for char type attribute, the original invalid byte sequence for encoding '%s': %s"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06151 - GAUSS-06160
+
+<br/>
+
+GAUSS-06151: "target of symbolic link '%s' doesn't exist."
+
+SQLSTATE: OP0A3
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06152: "GDS stream is null pointer, the dynamic cast failed"
+
+SQLSTATE: 29003
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06153: "GDS version does not match Gaussdb version."
+
+SQLSTATE: DB001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06154: "Abnormal data package received, package length is %d, input buffer length is %d"
+
+SQLSTATE: 无
+
+错误原因: 接受到异常的数据包，数据包的长度为xx，接收buffer的长度为xx。
+
+解决办法: 请检查数据文件，确保数据文件没有问题。
+
+GAUSS-06155: "Reject Limit , LOG ERRORS or LOG ERRORS DATA can only be used in COPY From Statements."
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06156: "Reject Limit must be used with LOG ERRORS or LOG ERRORS DATA."
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06157: "Error encountered while logging error into %s.%s."
+
+SQLSTATE: SP005
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06158: "the number of attributes is illegal"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06159: "index and table must be in the same schema"
+
+SQLSTATE: 55000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06160: "dfs value partition table does not support local partitioned indexes "
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06161 - GAUSS-06170
+
+<br/>
+
+GAUSS-06162: "It is not supported to create index on DFS tablespace."
+
+SQLSTATE: 42P17
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06163: "The operation of 'REINDEX INTERNAL TABLE %s PARTITION %s' failed. "
+
+SQLSTATE: 42P23
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06164: "The operation of 'REINDEX INTERNAL TABLE %s' on part '%u' failed. "
+
+SQLSTATE: 42P23
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06165: "The operation of 'REINDEX INTERNAL TABLE %s' failed. "
+
+SQLSTATE: XX002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06166: "The table '%s' doesn't support the operation of 'REINDEX INTERNAL TABLE'. There is no Desc table on it."
+
+SQLSTATE: 42P01
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06167: "Bypass process Failed"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06168: "uuids can not be NIL when generating uuid in restore mode."
+
+SQLSTATE: OP003
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06169: "Create table Like in multi-nodegroup is not supported"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06170: "Temporary sequences are not supported"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06171 - GAUSS-06180
+
+<br/>
+
+GAUSS-06171: "Invaild UUID for CREATE SEQUENCE %s."
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06172: "unrecognized sequence columns: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06173: "Sequence '%s' retry %d times to connect GTM on datanode %s"
+
+SQLSTATE: YY004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06174: "currval function is not supported"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06175: "lastval function is not supported"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06176: "'%s.%s' is not a sequence"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06177: "oldseqnamearg should not be null"
+
+SQLSTATE: XX005
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06178: "newseqnamearg should not be null"
+
+SQLSTATE: XX005
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06179: "Only support CREATE TRIGGER on regular row table."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06180: "Unsupport CREATE TRIGGER on table which is under cluster resizing."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06181 - GAUSS-06190
+
+<br/>
+
+GAUSS-06181: "invalid current user oid for trigger"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06182: "trigdesc should not be null"
+
+SQLSTATE: XX005
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06183: "invalid after-trigger event code: %u"
+
+SQLSTATE: 20000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06184: "unrecognized RI_FKey_trigger_type: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06185: "unrecognized node type when find the required outer rels for a bitmap tree: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06186: "unrecognized node type when find the required upper rels for a bitmap tree: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06187: "unrecognized node type when find indexpath quals: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06188: "wrong number of index expressions when match index to operand"
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06189: "unsupported indexqual type when expand indexqual conditions: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06190: "right operator can not be NULL"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06191 - GAUSS-06200
+
+<br/>
+
+GAUSS-06191: "unexpected strategy number %d when expand a single indexqual condition"
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06192: "when expand a single indexqual condition could not find commutator of member %d(%u,%u) of opfamily %u"
+
+SQLSTATE: D0011
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06193: "unexpected opfamily when generate indexqual condition by prefix quals: %u"
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06194: "unexpected const type when generate indexqual condition by prefix quals: %u"
+
+SQLSTATE: 20000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06195: "no < operator for opfamily %u when generate indexqual condition by prefix quals"
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06196: "unexpected operator when generate indexqual condition by network prefix quals: %u"
+
+SQLSTATE: 20000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06197: "no >= operator for opfamily %u when generate indexqual condition by network prefix quals"
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06198: "no > operator for opfamily %u when generate indexqual condition by network prefix quals"
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06199: "no <= operator for opfamily %u when generate indexqual condition by network prefix quals"
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06200: "unexpected rtekind: %d when set relation size"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/63-GAUSS-06201-GAUSS-06300.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/63-GAUSS-06201-GAUSS-06300.md
new file mode 100644
index 0000000000000000000000000000000000000000..6ca658ba82b81a0fa5554f956bdd9dce31d9e3e6
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/63-GAUSS-06201-GAUSS-06300.md
@@ -0,0 +1,924 @@
+---
+title: GAUSS-06201 - GAUSS-06300
+summary: GAUSS-06201 - GAUSS-06300
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-06201 - GAUSS-06300
+
+<br/>
+
+## GAUSS-06201 - GAUSS-06210
+
+<br/>
+
+GAUSS-06201: "failed on assertion in %s line %d : %s"
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06202: "unexpected rtekind when set relation path list: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06203: "All orientations are not covered."
+
+SQLSTATE: 20000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06204: "bad levelsup for CTE '%s' when set cte pathlist"
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06205: "could not find CTE '%s' when set cte pathlist"
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06206: "could not find plan for CTE '%s' when set cte pathlist"
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06207: "bad levelsup for CTE '%s' when set worktable pathlist"
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06208: "could not find plan for CTE '%s' when set worktable pathlist"
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06209: "unrecognized joinlist node type when build access paths by joinlist: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06210: "unrecognized node type when pushdown recurse through setOperations tree: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06211 - GAUSS-06220
+
+<br/>
+
+GAUSS-06211: "wrong number of tlist entries when compare a subquery targetlist datatypes"
+
+SQLSTATE: 20000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06212: "unrecognized node type when recurse push qual through setOperations tree: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06213: "unrecognized node type when create partiterator path: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06214: "Unsupported Using Index FOR TIMESERIES."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06215: "unrecognized node type of a bitmap index path when get pages: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06216: "unrecognized node type when extract cost and selectivity from a bitmap tree node: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06217: "left and right pathkeys do not match in mergejoin when initlize cost"
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06218: "cannot handle unplanned sub-select when costing quals"
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06219: "unrecognized join type when calculate joinrel size estimate: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06220: "unrecognized join type when match unsorted outer: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06221 - GAUSS-06230
+
+<br/>
+
+GAUSS-06221: "Null value error for building partitionwise join"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06222: "could not find opfamilies for equality operator %u when make pathkey from sortinfo"
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06223: "operator %u is not a valid ordering operator when make pathkey from sortinfo"
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06224: "volatile EquivalenceClass has no sortref when convert subquery pathkeys"
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06225: "too few pathkeys for mergeclauses when make inner pathkeys for merge"
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06226: "outer pathkeys do not match mergeclause when make inner pathkeys for merge"
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06227: "unrecognized join type when make a join rel: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06228: "Unsupported node type %s to check need stream setup for recursive union"
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06229: "encounters invalid varno"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06230: "invalid column number %d for table "
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06231 - GAUSS-06240
+
+<br/>
+
+GAUSS-06231: "There is no exist vararrno with 0"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06232: "tle can not be found from targetlist"
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06233: "No data node information for table: %s"
+
+SQLSTATE: XX006
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06234: "No data node found for u_sess->pgxc_cxt.gc_fdw_current_idx: %d, u_sess->pgxc_cxt.gc_fdw_max_idx: %d"
+
+SQLSTATE: XX006
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06235: "Unsupported Table Sample FOR TIMESERIES."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06236: "Unsupported Index Scan FOR TIMESERIES."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06237: "Unsupported Bitmap Heap Scan FOR TIMESERIES."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06238: "Unsupported Bitmap And FOR TIMESERIES."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06239: "Unsupported Bitmap OR FOR TIMESERIES."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06240: "Unsupported Bitmap Index Scan FOR TIMESERIES."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06134: "'%s' is not a valid EOL string, EOL string must not be empty"
+
+SQLSTATE: 无
+
+错误原因: 自定义换行符不能为空。
+
+解决办法: 请检查指定的自定义换行符，确保自定义换行符不为空。
+
+GAUSS-06135: "'%s' is not a valid EOL string, EOL string must not exceed the maximum length (10 bytes)"
+
+SQLSTATE: 无
+
+错误原因: 自定义换行符超出最大长度（10字节）。
+
+解决办法: 请检查指定的自定义换行符的长度，确保自定义换行符的长度不超出最大长度。
+
+GAUSS-06136: "COPY delimiter cannot contain user-define EOL string"
+
+SQLSTATE: 无
+
+错误原因: 分隔符不能包含自定义换行符。
+
+解决办法: 请检查分隔符和换行符，确保分隔符不包含自定义换行符。
+
+GAUSS-06137: "COPY null representation cannot contain user-define EOL string"
+
+SQLSTATE: 无
+
+错误原因: NULL值不能包含自定义换行符。
+
+解决办法: 请检查NULL值，确保NULL值不包含自定义换行符。
+
+GAUSS-06138: "EOL string '%s' cannot contain any characters in'%s'"
+
+SQLSTATE: 无
+
+错误原因: 自定义换行符不能包含以下字符。
+
+解决办法: 请检查自定义换行符，确保不包含上述字符。
+
+GAUSS-06139: "EOL specification can not be used with non-text format using COPY FROM or READ ONLY foreign table"
+
+SQLSTATE: 无
+
+错误原因: 自定义换行符不能用于非TEXT格式的copy导入或只读外表。
+
+解决办法: 请检查copy导入或只读外表的设置的文件格式，确保为TEXT格式。
+
+GAUSS-06140: "EOL specification can not be used with non-text format using COPY TO or WRITE ONLY foreign table except 0x0D0A and 0x0A"
+
+SQLSTATE: 无
+
+错误原因: 自定义换行符不能用于非TEXT格式的copy导出或只写外表，但是允许自定义换行符0x0D0A和0x0A。
+
+解决办法: 请检查copy导出或只写外表的设置的文件格式，确保为TEXT格式。
+
+<br/>
+
+## GAUSS-06241 - GAUSS-06250
+
+<br/>
+
+GAUSS-06241: "unrecognized node type: %d when modify worktable wtParam."
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06242: "recursive_union_plan can not be NULL"
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06243: "non-LATERAL parameter required by subquery"
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06244: "unexpected type of subquery parameter"
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06245: "Unsupported Direct Scan FOR TIMESERIES."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06246: "fail to find TargetEntry referenced by SortGroupClause"
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06247: "Unsupported FOR UPDATE/SHARE system table."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06248: "Unsupported FOR UPDATE/SHARE in non shippable plan."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06249: "Only Scan operator have BucketInfo attribute"
+
+SQLSTATE: XX006
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06250: "Unsupported FOR UPDATE/SHARE at non-top-level query in stream plan."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06251 - GAUSS-06260
+
+<br/>
+
+GAUSS-06251: "Unsupported FOR UPDATE/SHARE with limit in stream plan."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06252: "Unsupported FOR UPDATE/SHARE multiple table in stream plan."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06253: "can not find var with varno = %u and varattno = %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06254: "qry_tle should not be null"
+
+SQLSTATE: XX005
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06255: "Partition column can't be updated in current version"
+
+SQLSTATE: 42P10
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06256: "Build subPlan failed.. "
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06257: "convert to SubPlan failed. "
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06258: "Fail to process sublinks mutator."
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06259: "Fail to get sort group clause."
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06260: "failed to find relation %d in joinlist when remove relation from joinlist"
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06261 - GAUSS-06270
+
+<br/>
+
+GAUSS-06261: "unrecognized joinlist node type when remove relation from joinlist: %d"
+
+SQLSTATE: XX006
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06262: "cheapest_total_path should not exist para_info"
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06263: "unrecognized node type when add base_rels to query: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06264: "unrecognized node type when add vars to targetlist: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06265: "expected Var or PlaceHolderVar, others unsupported. "
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06266: "unrecognized join type in one level processing of deconstruct jointree: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06267: "unrecognized node type in one level of deconstruct jointree: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06268: "cannot cope with variable-free clause when distribute restrictinfo to rels"
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06269: "relid must not be less than zero."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06270: "too many range table entries when set plan reference."
+
+SQLSTATE: 54000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06271 - GAUSS-06280
+
+<br/>
+
+GAUSS-06271: "targetlist of stream node with plan_node_id %d should be equal to its child's targetlist"
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06272: "unrecognized node type in set plan refs: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06273: "Could not find the Aggref node when setting agg plan refernece."
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06274: "Could not find the Aggref node when setting agg plan reference."
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06275: "mark_stream_unsupport."
+
+SQLSTATE: 0A100
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06276: "Fail to generate subquery plan."
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06277: "unrecognized node type when process qual condition: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06278: "unrecognized node type when get base relation indexes: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06279: "OBS and HDFS foreign table can NOT be in the same plan."
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06280: "pl_size should not be zero"
+
+SQLSTATE: 22012
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06281 - GAUSS-06290
+
+<br/>
+
+GAUSS-06281: "Failed to get the runtime info from the compute pool."
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06282: "version is not compatible between local cluster and the compute pool"
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06283: "There is no optional index path for index column: %s.Please check for potential performance problem."
+
+SQLSTATE: 01000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06284: "MERGE INTO on replicated table does not yet support using distributed tables."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06285: "unrecognized bool test type: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06286: "RangeTblRef not found."
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06287: "Valid rel not found. "
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06288: "No Such Relation"
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06289: "subquery's setOperations tree should not be NULL in pull_up_simple_union_all"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06290: "jointree in subquery could not be NULL"
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06291 - GAUSS-06300
+
+<br/>
+
+GAUSS-06291: "Join range table do not have system column."
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06292: "Invalid join alias var"
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06293: "Invalid agg param which used in a join clause"
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06294: "Column should NOT be in JOIN clause."
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06295: "unsupported command type: %d."
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06296: "infinite recursion detected, please check the row level security policies for relation '%s'"
+
+SQLSTATE: 42P17
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06297: "could not convert table '%s' to a view because it has row level security enabled"
+
+SQLSTATE: 55000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06298: "could not convert table '%s' to a view because it has row level security policies"
+
+SQLSTATE: 55000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06299: "Fail to find base rel."
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06300: "predcate_classify returned a bogus value"
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/64-GAUSS-06301-GAUSS-06400.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/64-GAUSS-06301-GAUSS-06400.md
new file mode 100644
index 0000000000000000000000000000000000000000..dfe2b30c3f604f44a7b4f312dfe66fa101fa42ff
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/64-GAUSS-06301-GAUSS-06400.md
@@ -0,0 +1,860 @@
+---
+title: GAUSS-06301 - GAUSS-06400
+summary: GAUSS-06301 - GAUSS-06400
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-06301 - GAUSS-06400
+
+<br/>
+
+## GAUSS-06301 - GAUSS-06310
+
+<br/>
+
+GAUSS-06301: "invalid index oid to check for unusability"
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06302: "relation %s is not partitioned when check partition index"
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06303: "Could not find enough valid args for Boundary From OpExpr"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06304: "partSeq: %d out range of current relation partMap element num: %d."
+
+SQLSTATE: 2202E
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06305: "Duplicate range partition map oids: %u, please try again."
+
+SQLSTATE: 42710
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06306: "expected a RowCompareExpr for para clause"
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06307: "fail to eval const expressions."
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06308: "Fail to eval const expressoin."
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06309: "fail to eval const expressions. "
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06310: "Eval const expression mutator failed. "
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06311 - GAUSS-06320
+
+<br/>
+
+GAUSS-06311: "function '%s' doesn't exist"
+
+SQLSTATE: 42883
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06312: "function '%s' with %d parameters doesn't exist"
+
+SQLSTATE: 42883
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06313: "var on action's qual cannot find in target list"
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06314: "none_recursive_plan could not be NULL"
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06315: "outer_path and parent in outer_path could not be NULL"
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06316: "inner_path and parent in inner_path could not be NULL"
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06317: "Failed to get sort group clause. "
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06318: "buckets id %d of table '%s' is outsize range [%d,%d]"
+
+SQLSTATE: 22003
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06319: "%d of duplicate bucket id found"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06320: "No privilage assigned to user %u."
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06321 - GAUSS-06330
+
+<br/>
+
+GAUSS-06322: "Unexpected range table entry type."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06323: "exec_nodes could not be NULL"
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06324: "distribution could not be NULL"
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06325: "is_outer_replicated and is_inner_replicated could not all be false"
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06326: "[ng_get_single_dn_group_exec_node] unknown exec location."
+
+SQLSTATE: 2F000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06327: "Can not get valid skew value from hint."
+
+SQLSTATE: XX005
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06328: "Can not generate equal operation for non skew side."
+
+SQLSTATE: XX005
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06329: "Invalid skew stream type %d."
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06330: "Expected positive width estimation."
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06331 - GAUSS-06340
+
+<br/>
+
+GAUSS-06331: "child rel %u not found in append_rel_list"
+
+SQLSTATE: XX008
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06332: "source '%s' does not exist"
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06333: "global prepared statement '%s' does not exist in PrepareFetch GPC (%ld,%d,%d) dn session_id:%lu"
+
+SQLSTATE: 26000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06334: "store global plan source failed due to memory allocation failed"
+
+SQLSTATE: 26000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06335: "refuse to activate a job since illegal element in ExpiredJobList."
+
+SQLSTATE: 29000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06336: "no free slot when start job worker"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06337: "XuanYuanDB current do not support AIO"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06338: "could not request checkpoint because checkpointer not running"
+
+SQLSTATE: 44000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06339: "could not signal for checkpoint: %m"
+
+SQLSTATE: 44000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06340: "remote service port not available"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06341 - GAUSS-06350
+
+<br/>
+
+GAUSS-06341: "No data left in msg, left len:%u, desire len:%lu"
+
+SQLSTATE: 08P01
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06342: "No data left in msg, left len:%u"
+
+SQLSTATE: 08P01
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06343: "could not create Unix-domain socket: %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06344: "bind socket path %s failed:%m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06345: "listen socket failed: %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06346: "poll() failed in UDFMasterServerLoop, errno:%d, error reason:%s"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06347: "Socket send %d bytes: %m"
+
+SQLSTATE: 08006
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06348: "Invalid udf message len:%u"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06349: "create UDFWorkMemContext failed"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06350: "Otherwise, handlerType can only be UDF_RECV_RESULT"
+
+SQLSTATE: 29003
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06351 - GAUSS-06360
+
+<br/>
+
+GAUSS-06351: "Variable length %d cannot be negative"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06352: "Recv Unsupported argument type: %u"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06353: "Unsupport type: %u"
+
+SQLSTATE: 42804
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06354: "null prosrc for Java function %u"
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06355: "Run udf RPC connect failed: %m"
+
+SQLSTATE: 08006
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06356: "UDF Error:%s"
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06357: "internal_load_library %s failed: %m"
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06358: "load java_call_handler failed."
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06359: "UnixSocketDir is not valid, length is between 1 and %lu: %s/%s"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06360: "Invalid parameter."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06361 - GAUSS-06370
+
+<br/>
+
+GAUSS-06361: "execute cmd %s fail."
+
+SQLSTATE: XX005
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06362: "Can not read process num."
+
+SQLSTATE: XX005
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06363: "Contains invaid character: '%s'"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06364: "Invalid argument: should appoint an option of ls, addjar or rmjar."
+
+SQLSTATE: XX005
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06365: "Invalid argument: only support ls, addjar, rmjar options."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06366: "filepath should not be NULL"
+
+SQLSTATE: XX005
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06367: "Invalid argument: must set correct obs file path."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06368: "Invalid argument: must set accesskey."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06369: "Invalid argument: must set secretkey."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06370: "Invalid argument: must set region."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06371 - GAUSS-06380
+
+<br/>
+
+GAUSS-06371: "Invalid argument: must set a 'libraryname'."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06372: "Invalid argument: 'libraryname' should not contain '/' or starting with '.'."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06373: "Invalid argument: must set an absolute path followed by 'file:///'."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06374: "Invalid argument: the source file must be .jar file."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06375: "Invalid argument: must set bucket and filepath followed by 'obs://'."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06376: "must set correct source file path."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06377: "Invalid argument: the library already existed, please remove it first using rmjar."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06378: "%d %d: System error."
+
+SQLSTATE: 58000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06379: "%d: Failed to access system files."
+
+SQLSTATE: 2F000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06380: "%d: Invalid argument, must set correct region."
+
+SQLSTATE: 2F000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06381 - GAUSS-06390
+
+<br/>
+
+GAUSS-06381: "%d: Parameters error."
+
+SQLSTATE: 2F000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06382: "%d: Failed to connect to obs server."
+
+SQLSTATE: 08006
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06383: "%d: Failed to download from obs server."
+
+SQLSTATE: 2F000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06384: "%d: Obs server is busy. Try again later."
+
+SQLSTATE: 08006
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06385: "%d: Download failed."
+
+SQLSTATE: 2F000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06386: "execute command failed"
+
+SQLSTATE: 2F000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06387: "must be system admin to use the gs_extend_library function"
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06388: "Invaid argument: must at least set libraryname"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06389: "System Error."
+
+SQLSTATE: 58000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06390: "Invalid argument: must set correct bucket and obs file path."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06391 - GAUSS-06400
+
+<br/>
+
+GAUSS-06391: "the move_loc buffer should be invalid."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06392: "Integer overflow when update database-wid stats"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06393: "Failed to get database-wide stats."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06394: "timed_checkpoints overflow"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06395: "requested_checkpoints overflow"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06396: "checkpoint_write_time overflow"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06397: "checkpoint_sync_time overflow"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06398: "buf_written_checkpoints overflow"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06399: "buf_written_clean overflow"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06400: "maxwritten_clean overflow"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/65-GAUSS-06401-GAUSS-06500.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/65-GAUSS-06401-GAUSS-06500.md
new file mode 100644
index 0000000000000000000000000000000000000000..1f68d61c7132937d11a97584f5d6a82bd813f262
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/65-GAUSS-06401-GAUSS-06500.md
@@ -0,0 +1,788 @@
+---
+title: GAUSS-06401 - GAUSS-06500
+summary: GAUSS-06401 - GAUSS-06500
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-06401 - GAUSS-06500
+
+<br/>
+
+## GAUSS-06401 - GAUSS-06410
+
+<br/>
+
+GAUSS-06401: "buf_written_backend overflow"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06402: "buf_fsync_backend overflow"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06403: "buf_alloc overflow"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06404: "unrecognized bypass recovery conflict reason: %d"
+
+SQLSTATE: 20000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06405: "Invalid database num:%u"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06406: "Unable to connect to execute internal query."
+
+SQLSTATE: OP001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06407: "fail to execute query"
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06408: "toast table map hash table corrupted."
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06409: "AutoVacuum Data share mem is already init"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06410: "file_size is invalid:[%ld]"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06411 - GAUSS-06420
+
+<br/>
+
+GAUSS-06411: "process suicides because the victim of lwlock deadlock is an auxiliary thread"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06412: "syslogger could not open file %d: %m,exit"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06413: "terminate because pooler connect timeout(%ds) when process startup packet"
+
+SQLSTATE: 57014
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06414: "pg_strdup: cannot duplicate null pointer (internal error)"
+
+SQLSTATE: D0011
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06415: "out of memory"
+
+SQLSTATE: 58000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06416: "the options of -n is deprecated"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06417: "the options of -T is deprecated"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06418: "Single node mode: must start as single node (-single_node)"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06419: "could not create listen socket for '%s:%d'"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06420: "pooler_port must equal to gsql listen port plus one!"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06421 - GAUSS-06430
+
+<br/>
+
+GAUSS-06421: "could not create ha listen socket for '%s:%d'"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06422: "could not create Ha listen socket for ReplConnInfoArr[%d]'%s:%d'"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06423: "could not create Unix-domain socket for '%s:%d'"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06424: "Init libcomm for stream failed, maybe listen port already in use"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06425: "WAL streaming (max_wal_senders > 0) requires wal_level 'archive', 'hot_standby' or 'logical'"
+
+SQLSTATE: 58000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06426: "invalid value[%d] for parameter 'connect_timeout'"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06427: "no pg_hba.conf entry for host '%s'."
+
+SQLSTATE: 28000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06428: "when replconn port equals gsql port plus one, listen_addresses can not contain '*'"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06429: "set basic info of stream failed!"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06430: "could not set WorkingGrandVersionNum manually while not performing upgrade"
+
+SQLSTATE: D0011
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06431 - GAUSS-06440
+
+<br/>
+
+GAUSS-06431: "wrong environment variable '%s'"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06432: "unrecorgnized proc type %d"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06433: "create timer fail at thread : %lu"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06434: "unsupport thread role type %d"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06435: "must be superuser account to perform disable_conn()"
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06436: "Connection mode should be polling_connection or specify_connection or prohibit_connection"
+
+SQLSTATE: D0011
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06437: "could not add lock when DN is not redo all xlog, redo done flag is false"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06438: "could not add lock when DN is not redo all xlog."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06439: "Invalid null pointer attribute for disable_conn()"
+
+SQLSTATE: 42P24
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06440: "host is invalid"
+
+SQLSTATE: D0011
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06441 - GAUSS-06450
+
+<br/>
+
+GAUSS-06441: "Can't get local connection address."
+
+SQLSTATE: 42804
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06442: "get local host failed!"
+
+SQLSTATE: 42804
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06443: "get local port failed!"
+
+SQLSTATE: 42804
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06444: "cannot read disable connection file: '%s' "
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06445: "sql retrying routine off the track."
+
+SQLSTATE: 2F000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06446: "%s %s do stub test '%c'"
+
+SQLSTATE: XX015
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06447: "%s ecode stub test raise error %s"
+
+SQLSTATE: # thi
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06448: "invalid argument count %d in function call message"
+
+SQLSTATE: 08P01
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06449: "func_id not valid in %s line %d"
+
+SQLSTATE: 42883
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06450: "function call message supplies invalid numAFormats %d"
+
+SQLSTATE: 08P01
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06451 - GAUSS-06460
+
+<br/>
+
+GAUSS-06457: "Unable to create table on old installation group '%s' while in cluster resizing."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06458: "Current Node is not active"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06459: "commit xid %lu is not equal to the excute one %lu."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06460: "abort xid %lu is not equal to the former one %lu."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06461 - GAUSS-06470
+
+<br/>
+
+GAUSS-06461: "Current mode does not support FOREIGN table yet"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06462: "Current mode does not support FOREIGN server yet"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06463: "NOT-SUPPORT: Not support DROP multiple objects different nodegroup"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06464: "permission denied to drop foreign table in security mode"
+
+SQLSTATE: 42501
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06465: "foreign table '%s.%s' does not exist"
+
+SQLSTATE: 42P01
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06466: "NOT-SUPPORT: Not support DROP multiple functions in different nodegroup"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06467: "operation copy with file is forbidden in security mode."
+
+SQLSTATE: D0011
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06468: "NOT-SUPPORT: Not support Grant/Revoke privileges to objects in different nodegroup"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06469: "user defined range type is not yet supported."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06471 - GAUSS-06480
+
+<br/>
+
+GAUSS-06471: "This relation doesn't support analyze with column."
+
+SQLSTATE: 42P01
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06473: "Invalid value '%s' in WITH clause"
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06474: "Don't support node group in single_node mode."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06476: "%s can not run inside a transaction block"
+
+SQLSTATE: 25001
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06478: "unrecognized portal strategy: %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06479: "cursor can only scan forward"
+
+SQLSTATE: 55000
+
+错误原因: 显式的声明了NO SCROLL选项或当前执行计划不支持backward scan。
+
+解决办法: 若是显式的声明了NO SCROLL直接删除NO SCROLL选项即可。若是当前执行计划不支持，则需要调整执行计划。
+
+GAUSS-06480: "Cursor rewind are not supported."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06481 - GAUSS-06490
+
+<br/>
+
+GAUSS-06481: "Invaild parameter."
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06482: "Could not find \'}\' in the query string."
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06483: "unexpect list length %d of mem_list from info_query_string."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06484: "analyzeNode is null."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06485: "node n is null."
+
+SQLSTATE: XX001
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06486: "Invaild UUID Message for CREATE SEQUENCE."
+
+SQLSTATE: XX001
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06487: "Not enough UUID (%d/%d) in CREATE SEQUENCE."
+
+SQLSTATE: XX001
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06488: "Invaild UUID Message while CREATE SEQUENCE by serial."
+
+SQLSTATE: XX001
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06489: "Too long plan_string."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法: Please contact engineer to support."
+
+GAUSS-06490: "Received unexpected node type."
+
+SQLSTATE: XX006
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06491 - GAUSS-06500
+
+<br/>
+
+GAUSS-06491: "rel_loc_info is NULL."
+
+SQLSTATE: 58000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06492: "The current node should not receive z messages"
+
+SQLSTATE: 58030
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06493: "portal_name or stmt_name is null."
+
+SQLSTATE: XX001
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06494: "Too long portal_name and stmt_name."
+
+SQLSTATE: 08P01
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06495: "stmts is not NULL"
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06496: "terminating data redistribution process due to administrator command"
+
+SQLSTATE: 57P01
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06497: "terminating snapshot process due to administrator command"
+
+SQLSTATE: 57P01
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06498: "detach and reaper session from thread due to session connection lost"
+
+SQLSTATE: 57014
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06499: "terminate because authentication timeout(%ds)"
+
+SQLSTATE: 57014
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06500: "terminate because cancel interrupts"
+
+SQLSTATE: 57014
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/66-GAUSS-06501-GAUSS-06600.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/66-GAUSS-06501-GAUSS-06600.md
new file mode 100644
index 0000000000000000000000000000000000000000..8bbc6f194da11cdb8f65702fb737ffadae846bc5
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/66-GAUSS-06501-GAUSS-06600.md
@@ -0,0 +1,868 @@
+---
+title: GAUSS-06501 - GAUSS-06600
+summary: GAUSS-06501 - GAUSS-06600
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-06501 - GAUSS-06600
+
+<br/>
+
+## GAUSS-06501 - GAUSS-06510
+
+<br/>
+
+GAUSS-06501: "canceling statement due to %s.%s"
+
+SQLSTATE:无
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06502: "canceling statement due to %s"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法: Please contact engineer to support."
+
+GAUSS-06503: "canceling data redistribution task"
+
+SQLSTATE: 57014
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06504: "canceling statement due to failover, pending"
+
+SQLSTATE: 08000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06505: "canceling snapshot task"
+
+SQLSTATE: 57014
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06506: "Postgres-XC: must start as either a Coordinator (-coordinator) or Datanode (-datanode)"
+
+SQLSTATE: 42601
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06507: "Cannot execute DDL in a transaction block when need reconnect pooler"
+
+SQLSTATE: 25001
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06508: "invalid number of data nodes when initializing global node definition."
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06509: "invalid frontend message type '%c'."
+
+SQLSTATE: 08P01
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06510: "query_string is NULL."
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06511 - GAUSS-06520
+
+<br/>
+
+GAUSS-06511: "Too long query_string."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06512: "Invalid packet path, remoteConnType[%d], remote_host[%s], remote_port[%s]."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06513: "Acceptter in pooler stateless resue mode reset connection params %d > sql[%d]."
+
+SQLSTATE: 58000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06514: "Too long schema_name."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06515: "The overrideStack list has been reach the max length."
+
+SQLSTATE: 08P01
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06516: "Invalid message type %d for procedure overrideStack."
+
+SQLSTATE: 08P01
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06517: "invalid execute message"
+
+SQLSTATE: 08P01
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06518: "Too long close_target."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06519: "invalid describe message"
+
+SQLSTATE: 08P01
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06520: "gtm mode unconsistency, remote mode is %s, local mode is %s."
+
+SQLSTATE: 58000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06521 - GAUSS-06530
+
+<br/>
+
+GAUSS-06521: "Received an invalid commit csn: %lu."
+
+SQLSTATE:无
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06522: "Need to set support_batch_bind=true if executing batch"
+
+SQLSTATE: 58000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06523: "Portal run not complete for one in Batch bind-execute: name %s, query %s"
+
+SQLSTATE: 58000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06524: "Batch param of distribute key only support const"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06525: "Failed to get DataNode id for Batch bind-execute: name %s, query %s"
+
+SQLSTATE: 58000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06526: "unexpected batch_count %d get from inputmessage"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06527: "unexpected maxlen %d "
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06528: "Batch bind-execute message with invalid batch count: %d"
+
+SQLSTATE: 08P01
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06529: "Not support portal_name %s for Batch bind-execute."
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06530: "Batch bind-execute message with invalid parameter number: %d"
+
+SQLSTATE: 08P01
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06531 - GAUSS-06540
+
+<br/>
+
+GAUSS-06531: "conflict stmt name in Batch bind-execute message: bind %s, describe %s"
+
+SQLSTATE: 08P01
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06532: "conflict portal name in Batch bind-execute message: bind %s, describe %s"
+
+SQLSTATE: 08P01
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06533: "invalid DESCRIBE message subtype in Batch bind-execute message: %d"
+
+SQLSTATE: 08P01
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06534: "conflict portal name in Batch bind-execute message: bind %s, execute %s"
+
+SQLSTATE: 08P01
+
+错误原因: 系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06535: "Not support max_row in Batch bind-execute message: %d"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06536: "invalid value in Batch bind-execute message: %d"
+
+SQLSTATE: 08P01
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06537: "No thread pool worker left while waiting for session close. This is a very rare case when all thread pool workers happen to encounter FATAL problems before session close."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06538: "epoll receive %d events which exceed the limitation %d"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06539: "Exceed stream thread pool limitation %d in group %d"
+
+SQLSTATE: 58000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06540: "Fail to find a free slot for stream"
+
+SQLSTATE: 53000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06541 - GAUSS-06550
+
+<br/>
+
+GAUSS-06541: "Unexpected receive proc signal."
+
+SQLSTATE: 08000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06542: "receive more connection message %d than expect %d"
+
+SQLSTATE: 08P01
+
+错误原因: 系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06543: "undefined state %d for session attach"
+
+SQLSTATE: 42P24
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06544: "memory usage reach the max_dynamic_memory"
+
+SQLSTATE: YY006
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06545: "Invalid attribute for thread pool."
+
+SQLSTATE: OP0A3
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06546: "Unsupported LLVM report type!"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06547: "Cannot get the llvm::Intrinsic::smul_with_overflow function!"
+
+SQLSTATE: CG002
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06548: "Failed on getting IR function : LLVMIRbpcharne!"
+
+SQLSTATE: CG001
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06549: "Cannot get the llvm::Intrinsic::sasub_with_overflow function!"
+
+SQLSTATE: CG002
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06550: "Failed on getting IR function : LLVMIRtextlike!"
+
+SQLSTATE: CG001
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06551 - GAUSS-06560
+
+<br/>
+
+GAUSS-06551: "Failed on getting IR function : LLVMIRtextnlike!"
+
+SQLSTATE: CG001
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06552: "Unexpected NULL right operator!"
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06553: "Failed to get function Intrinsic::prefetch!"
+
+SQLSTATE: CG002
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06154: "Abnormal data package received, package length is %d, input buffer length is %d"
+
+SQLSTATE: 无
+
+错误原因: 接受到异常的数据包，数据包的长度为xx，接收buffer的长度为xx。
+
+解决办法: 请检查数据文件，确保数据文件没有问题。
+
+GAUSS-06555: "Failed to get the const node of the operation!"
+
+SQLSTATE: XX005
+
+错误原因: 系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06556: "Failed on getting IR function : LLVMIRbpchareq!"
+
+SQLSTATE: CG001
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06557: "unrecognized booltexttype: %d"
+
+SQLSTATE: XX004
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06558: "Failed on getting IR function : LLVMIRmemcmp!"
+
+SQLSTATE: CG001
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06559: "Codegen failed on the procedure of ExecVecTargetList!"
+
+SQLSTATE: CG000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06560: "Not supported expr node %d yet!"
+
+SQLSTATE: XX004
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06561 - GAUSS-06570
+
+<br/>
+
+GAUSS-06561: "Unexpected batch information from ExprContext."
+
+SQLSTATE: XX006
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06562: "Codegen keyMatch failed: unsupported data type!"
+
+SQLSTATE: 42804
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06563: "Failed to get inner hash key!"
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06564: "Failed to get outer hash key!"
+
+SQLSTATE: XX005
+
+错误原因: 系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06565: "Codegen keyMatch failed for %d-th clause of hash join!"
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06566: "Codegen fast keyMatch failed: unsupported data type!"
+
+SQLSTATE: 42804
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06567: "Codegen buildHashTable failed: unsupported data type!"
+
+SQLSTATE: 42804
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06568: "Codegen probeHashTable failed: unsupported data type!"
+
+SQLSTATE: 42804
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06569: "Unsupported operation %u in FastAgg."
+
+SQLSTATE: XX004
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06570: "Failed on generating HashBatchCodeGen!"
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06571 - GAUSS-06580
+
+<br/>
+
+GAUSS-06571: "Failed on generating MatchOneKey Function!"
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06572: "Unexpected NULL project information."
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06573: "Unsupported agg function %u!"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06574: "Type %u is not supported yet in hashBatch"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06575: "Type %u is not supported yet in match_key"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06576: "Unexpected operation %u!"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06577: "Cannot get the llvm::Intrinsic::sadd_with_overflow function!"
+
+SQLSTATE: CG002
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06578: "Invalid LLVM type %d"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06579: "unrecognized node type: %d when rescan"
+
+SQLSTATE: XX004
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06580: "unrecognized node type: %d when restore scan position"
+
+SQLSTATE: XX004
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06581 - GAUSS-06590
+
+<br/>
+
+GAUSS-06581: "cache lookup failed for relation %u when check backward scan for Index."
+
+SQLSTATE: 29P01
+
+错误原因: 系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06582: "cache lookup failed for access method %u when test backward scan for Index %s"
+
+SQLSTATE: 29P01
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06583: "cursor '%s' does not exist when executing Current Of Expr."
+
+SQLSTATE: 34000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06584: "cursor '%s' is not positioned on a row when the cursor uses for UPDATE/SHARE"
+
+SQLSTATE: 24000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06585: "cursor '%s' is not positioned on a row when the cursor doesn't use for UPDATE/SHARE"
+
+SQLSTATE: 24000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06586: "could not find hash function for hash operator %u for TupleHashTable, column number %d, total column number %d."
+
+SQLSTATE: 42883
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06587: "invalid node identifier for update/delete"
+
+SQLSTATE: 42704
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06588: "unrecognized result from subplan for BitmapAnd."
+
+SQLSTATE: XX004
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06589: "unrecognized result from subplan for BitmapHeapScan."
+
+SQLSTATE: XX004
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06590: "prefetch and main iterators are out of sync for BitmapHeapScan."
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06591 - GAUSS-06600
+
+<br/>
+
+GAUSS-06591: "can't initialize bitmap index scans using unusable index '%s'"
+
+SQLSTATE: XX002
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06592: "no local indexes found for partition %s BitmapIndexScan"
+
+SQLSTATE: 42809
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06593: "can't initialize bitmap index scans using unusable local index '%s' for partition"
+
+SQLSTATE: XX002
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06594: "unrecognized result from BitmapIndexScan subplan when execute BitmapOr"
+
+SQLSTATE: XX004
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06595: "unrecognized result from non-BitmapIndexScan subplan when execute BitmapOr"
+
+SQLSTATE: XX004
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06596: "ExtensibleNodeMethods '%s' was not registered"
+
+SQLSTATE: 42704
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06597: "unrecognized join type: %d for hashjoin"
+
+SQLSTATE: XX004
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06598: "could not write hashvalue %u to hash-join temporary file, written length %lu."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06599: "could not write tuple to hash-join temporary file: written length %lu, tuple length %u"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06600: "could not read from hash-join temporary file: read length %zu"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/67-GAUSS-06601-GAUSS-06700.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/67-GAUSS-06601-GAUSS-06700.md
new file mode 100644
index 0000000000000000000000000000000000000000..ce2188c581b3b8f67f88d05aea17ba33f678f520
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/67-GAUSS-06601-GAUSS-06700.md
@@ -0,0 +1,868 @@
+---
+title: GAUSS-06601 - GAUSS-06700
+summary: GAUSS-06601 - GAUSS-06700
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-06601 - GAUSS-06700
+
+<br/>
+
+## GAUSS-06601 - GAUSS-06610
+
+<br/>
+
+GAUSS-06601: "The hash-join temporary file is corrupted,hashvalue:%u, length:%u."
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06602: "could not read from hash-join temporary file(t_len:%u,nread:%lu): %m"
+
+SQLSTATE: 无
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06603: "can't initialize index-only scans using unusable index '%s'"
+
+SQLSTATE: XX002
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06604: "can't initialize index-only scans using unusable local index '%s'"
+
+SQLSTATE: XX002
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06605: "unrecognized join type: %d when initializing nestLoop"
+
+SQLSTATE: XX004
+
+错误原因:  系统内部错误。
+
+解决办法: Please contact engineer to support."
+
+GAUSS-06606: "TABLESAMPLE REPEATABLE parameter cannot be null"
+
+SQLSTATE: 29002
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06607: "sample percentage must be between 0 and 100"
+
+SQLSTATE: 29001
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06608: "invalid operation %d on partition for seqscan, allowed are UPDATE/DELETE/SELECT"
+
+SQLSTATE: D0011
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06609: "unrecognized set op: %d when seting the count of output."
+
+SQLSTATE: XX004
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06610: "MPP with-recursive, globalStreamNodeGroup is not found in Node:[%d]"
+
+SQLSTATE: XX000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06611 - GAUSS-06620
+
+<br/>
+
+GAUSS-06611: "stop scan the work table due to transaction aborted and vfd invalidated"
+
+SQLSTATE: 57P05
+
+错误原因:  系统内部错误。
+
+解决办法: Please contact engineer to support."
+
+GAUSS-06612: "MPP With-Recursive sync controller for RecursiveUnion[%d] is not found"
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06613: "[LIGHT PROXY] Failed to get pooled connections from %s[%u]"
+
+SQLSTATE: 08006
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06614: "[LIGHT PROXY] Failed to send parse to %s[%u]"
+
+SQLSTATE: 08000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06615: "[LIGHT PROXY] Failed to get new transaction id"
+
+SQLSTATE: 08000
+
+错误原因:  系统内部错误。
+
+解决办法: Please contact engineer to support."
+
+GAUSS-06616: "[LIGHT PROXY] Failed to send gxid %lu to %s[%u]"
+
+SQLSTATE: 08000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06617: "[LIGHT PROXY] Failed to send timestamp to %s[%u]"
+
+SQLSTATE: 08000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06618: "[LIGHT PROXY] Failed to send internal begin to %s[%u]"
+
+SQLSTATE: 08000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06619: "[LIGHT PROXY] Failed to send cid to %s[%u]"
+
+SQLSTATE: 08000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06620: "[LIGHT PROXY] Failed to send snapshot to %s[%u]"
+
+SQLSTATE: 08000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06621 - GAUSS-06630
+
+<br/>
+
+GAUSS-06621: "[LIGHT PROXY] Failed to send cgroup to %s[%u]"
+
+SQLSTATE: 08000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06622: "[LIGHT PROXY] Failed to send query id to %s[%u]"
+
+SQLSTATE: 08000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06623: "[LIGHT PROXY] Failed to send unique sql id to %s[%u]"
+
+SQLSTATE: 08000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06624: "INSERT ON DUPLICATE KEY UPDATE must have an transformed InsertStmt query."
+
+SQLSTATE: XX008
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06625: "invalid msgType %d for process message "
+
+SQLSTATE: 20000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06626: "[LIGHT PROXY] Failed to fetch from Datanode %u"
+
+SQLSTATE: 08006
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06627: "[LIGHT PROXY] Unexpected response from %s[%u]"
+
+SQLSTATE: 08000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06628: "[LIGHT PROXY] Failed to send global sess id to Datanode %u"
+
+SQLSTATE: 57P03
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06629: "[LIGHT PROXY] Failed to send sync to %s[%u]"
+
+SQLSTATE: 08000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06630: "CTE subplans should not be executed"
+
+SQLSTATE: 23514
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06631 - GAUSS-06640
+
+<br/>
+
+GAUSS-06631: "unrecognized testexpr type: %d in a hash subplan"
+
+SQLSTATE: XX004
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06632: "could not find compatible hash operator for operator %u for subplan"
+
+SQLSTATE: 42883
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06633: "could not find hash function for hash operator %u for subplan"
+
+SQLSTATE: 42883
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06634: "CTE subplans should not be executed when execute subplan"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06635: "could not identify CTID expression, %s"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06636: "cache lookup failed for aggregate function %u"
+
+SQLSTATE: 29P01
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06637: "unrecognized node type: %d when executing executor node."
+
+SQLSTATE: XX004
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06638: "unsupport bypass indexqual type: %d"
+
+SQLSTATE: XX004
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06639: "wrong input for router"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06640: "cannot find valid relation oid from router table_name"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06641 - GAUSS-06650
+
+<br/>
+
+GAUSS-06641: "invalid relation locator info from router table_name"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06642: "only support hash or modulo locator type, the relation locator type for router is %c"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06643: "input key number cannot match distribute keys on table %s"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06644: "invalid node id get from input key"
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06645: "cannot get result from tuplestore for WinwdowsAgg"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06646: "cache lookup failed for aggregate %u of WindowsAgg"
+
+SQLSTATE: 29P01
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06647: "cache lookup failed for function %u of WindowsAgg in pg_proc"
+
+SQLSTATE: 29P01
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06648: "cannot get result from tuplestore in WindowsAgg."
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06649: "unrecognized window seek type: %d on a specified row of partition."
+
+SQLSTATE: XX004
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06650: "window object is invalid"
+
+SQLSTATE: 22000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06651 - GAUSS-06660
+
+<br/>
+
+GAUSS-06651: "unrecognized window seek type: %d on a specified row of window frame"
+
+SQLSTATE: XX004
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06652: "Both cacheplan and planstmt are NULL"
+
+SQLSTATE: 26000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06653: "unrecognized bypass support process option: %d"
+
+SQLSTATE: 20000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06654: "r_formats can not be NULL when num of rformats is not 0"
+
+SQLSTATE: XX005
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06655: "unmatched parameter number"
+
+SQLSTATE: 26000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06656: "unexpected node type: %d when processing bypass expression."
+
+SQLSTATE: XX004
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06657: "unexpected arg length : %d when processing bypass expression."
+
+SQLSTATE: XX004
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06658: "unrecognized bypass support number of arguments function calls: %d"
+
+SQLSTATE: 20000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06659: "Invaild Oid when open hash bucket relation."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06660: "Invaild hash bucket oid from current tuple for update."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06661 - GAUSS-06670
+
+<br/>
+
+GAUSS-06661: "Invaild hash bucket oid from current tuple for delete."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06662: "Invaild hash bucket oid from current tuple for lock."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06663: "upper and lower index lists are not same length (%d, %d)"
+
+SQLSTATE: 2202E
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06664: "a NULL isNull pointer was passed when get attribute by number."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06665: "invalid null attribute name"
+
+SQLSTATE: 42602
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06666: "a NULL isNull pointer was passed when get attribute by name."
+
+SQLSTATE: 22023
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06667: "function doesn't exist "
+
+SQLSTATE: 42883
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06668: "The input function expression is NULL."
+
+SQLSTATE: 22004
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06669: "unrecognized XML operation %d"
+
+SQLSTATE: XX004
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06670: "unrecognized node type: %d when initializing expression."
+
+SQLSTATE: XX004
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06671 - GAUSS-06680
+
+<br/>
+
+GAUSS-06671: "set-valued function called in context when calculate targetlist that cannot accept a set"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06672: "failed to fetch conflicting tuple for DUPLICATE KEY UPDATE"
+
+SQLSTATE: 40001
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06673: "ON DUPLICATE KEY UPDATE command cannot affect row a second time"
+
+SQLSTATE: 40001
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06674: "unexpected self-updated tuple"
+
+SQLSTATE: 40001
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06675: "unexpected concurrent update tuple"
+
+SQLSTATE: 40001
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06676: "ON DUPLICATE KEY UPDATE is not supported on column orientated table"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06677: "ON DUPLICATE KEY UPDATE is not supported on DFS table"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06678: "delete conflict in delta table cstore.%s"
+
+SQLSTATE: 42P28
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06679: "unable to get a stable set of rows in the source tables"
+
+SQLSTATE: P0003
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06680: "update conflict in delta table cstore.%s"
+
+SQLSTATE: 42P28
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06681 - GAUSS-06690
+
+<br/>
+
+GAUSS-06681: "unknown operation %d when process BEFORE EACH STATEMENT triggers"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06682: "unknown operation %d when process AFTER EACH STATEMENT triggers"
+
+SQLSTATE: XX004
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06683: "junkfilter should not be NULL"
+
+SQLSTATE: 22004
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06684: "ctid is NULL when do operation %d, junk attribute number is %d"
+
+SQLSTATE: XX007
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06685: "bucketid is null when update table"
+
+SQLSTATE: XX007
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06686: "wholerow is NULL when do operation %d, junk attribute number is %d"
+
+SQLSTATE: XX007
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06687: "unknown operation %d when execute the required table modification."
+
+SQLSTATE: XX004
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06688: "Unsupport 'MERGE INTO' command during online expansion on '%s'"
+
+SQLSTATE: 0A000
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06689: "could not find junk tableoid column for partition table."
+
+SQLSTATE: 42P24
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06690: "could not find junk bucketid column for bucketed table."
+
+SQLSTATE: 42P24
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06691 - GAUSS-06700
+
+<br/>
+
+GAUSS-06691: "tableoid is NULL when try to lock current row."
+
+SQLSTATE: XX007
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06692: "bucketid is NULL when try to lock current row."
+
+SQLSTATE: XX007
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06693: "unrecognized heap_lock_tuple status: %u when lock a tuple"
+
+SQLSTATE: XX004
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06694: "ExecLockRows:target relation cannot be NULL for plan qual recheck."
+
+SQLSTATE: 40001
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06695: "unrecognized bypass support type: %d"
+
+SQLSTATE: XX004
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06696: "tableoid is null when merge partitioned table"
+
+SQLSTATE: XX007
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06697: "bucketid is null when merge table"
+
+SQLSTATE: XX007
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06698: "SPI stack corrupted when connect SPI, %s"
+
+SQLSTATE: XX001
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06699: "SPI stack corrupted when connect SPI, stack depth %d"
+
+SQLSTATE: XX001
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
+
+GAUSS-06700: "SPI stack corrupted when copy tuple, connected level: %d"
+
+SQLSTATE: XX001
+
+错误原因:  系统内部错误。
+
+解决办法:  请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/68-GAUSS-06701-GAUSS-06800.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/68-GAUSS-06701-GAUSS-06800.md
new file mode 100644
index 0000000000000000000000000000000000000000..50472a9323e09f692b6613e411bcfe9a9285d7ff
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/68-GAUSS-06701-GAUSS-06800.md
@@ -0,0 +1,868 @@
+---
+title: GAUSS-06701 - GAUSS-06800
+summary: GAUSS-06701 - GAUSS-06800
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-06701 - GAUSS-06800
+
+<br/>
+
+## GAUSS-06701 - GAUSS-06710
+
+<br/>
+
+GAUSS-06701: "SPI stack corrupted when return tuple, connected level: %d"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06702: "SPI stack corrupted when modify tuple, connected level: %d"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06703: "SPI stack corrupted when allocate, connected level: %d"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06704: "open cursor with args has invalid arguments, %s"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06705: "SPI stack is corrupted when open cursor with args, current level: %d, connected level: %d"
+
+SQLSTATE: 24000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06706: "SPI stack is corrupted when open cursor, current level: %d, connected level: %d"
+
+SQLSTATE: 24000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06707: "invalid portal in SPI cursor close operation"
+
+SQLSTATE: 24000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06708: "SPI stack level is corrupted when checking SPI id, current level: %d, connected level: %d"
+
+SQLSTATE: SP006
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06709: "SPI stack is corrupted when checking SPI id."
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06710: "SPI tupletable is not cleaned when initializing SPI."
+
+SQLSTATE: SP006
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06711 - GAUSS-06720
+
+<br/>
+
+GAUSS-06711: "tuple is NULL when store to SPI tupletable."
+
+SQLSTATE: SP006
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06712: "consistency check on SPI tuple count failed when execute plan, %s"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06713: "SPI stack is corrupted when perform cursor operation, current level: %d, connected level: %d"
+
+SQLSTATE: SP001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06714: "consistency check on SPI tuple count failed, %s"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06715: "SPI stack corrupted when begin SPI operation."
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06716: "SPI tupletable is NULL when shutdown SPI for analyze."
+
+SQLSTATE: SP000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06717: "Unable to connect to execute internal query, current level: %d, connected level: %d"
+
+SQLSTATE: SP001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06718: "Invalid parameter in function '%s'"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06719: "do not support update or delete on table %s, when do cluster resizing on it."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06720: "delete delta table %s is not found when do cluster resizing table '%s'"
+
+SQLSTATE: 42P01
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06721 - GAUSS-06730
+
+<br/>
+
+GAUSS-06721: "Unsupport '%s' command during online expansion"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06722: "Unsupport '%s' command during online expansion on '%s'"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06723: "Unsupport '%s' command with '%s' option during online expansion on '%s' because the object is in read only mode."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06724: "Unsupport '%s' command with '%s' option during online expansion on '%s'"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06725: "Unsupport 'VACUUM FULL' command during online expansion on '%s'"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06726: "Unsupport '%s' command during online expansion on '%s' because the object is in read only mode."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06727: "function with OID %u does not exist when checking function dnstable"
+
+SQLSTATE: 42883
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06728: "operation expression function with OID %u does not exist."
+
+SQLSTATE: 42883
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06729: "new table %s is not found when do cluster resizing table '%s'"
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06730: "Invalid parameter in function '%s' when getting the name of new table"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06731 - GAUSS-06740
+
+<br/>
+
+GAUSS-06731: "unrecognized markType: %d when initializing query plan."
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06732: "unrecognized CmdType: %d when perform operations on view."
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06733: "could not find tableoid junk %s column when build RowMark"
+
+SQLSTATE: XX007
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06734: "could not find bucketid junk %s column when build RowMark"
+
+SQLSTATE: XX007
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06735: "could not find ctid junk %s column when build RowMark"
+
+SQLSTATE: XX007
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06736: "could not find whole-row junk %s column when build RowMark"
+
+SQLSTATE: XX007
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06737: "failed to fetch tuple for EvalPlanQual recheck from partition relation."
+
+SQLSTATE: 29P02
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06738: "streaminfo space is not enough because STREAM NUMBER : %d + GATHER NUMBER : %d < streamInfoIdx : %d"
+
+SQLSTATE: XX006
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06739: "query dop is out of range: %u [0-%d]"
+
+SQLSTATE: 22017
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06740: "m_query_dop can not be zero"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06741 - GAUSS-06750
+
+<br/>
+
+GAUSS-06741: "Expecting messages of query: %lu, but received messages of query: %lu"
+
+SQLSTATE: YY002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06742: "slot is out of range"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06743: "can't initialize index scans using unusable index '%s'"
+
+SQLSTATE: XX002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06744: "indexqual for OpExpr doesn't have key on left side"
+
+SQLSTATE: XX002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06745: "bogus index qualification for OpExpr, attribute number is %d."
+
+SQLSTATE: XX002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06746: "indexqual for RowCompare expression doesn't have key on left side"
+
+SQLSTATE: XX002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06747: "bogus RowCompare index qualification, attribute number is %d"
+
+SQLSTATE: XX002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06748: "RowCompare index qualification contains wrong operator, strategy number is %d."
+
+SQLSTATE: XX002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06749: "n_sub_key can not be zero"
+
+SQLSTATE: XX002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06750: "indexqual for ScalarArray doesn't have key on left side"
+
+SQLSTATE: XX002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06751 - GAUSS-06760
+
+<br/>
+
+GAUSS-06751: "bogus index qualification for ScalarArray, attribute number is %d."
+
+SQLSTATE: XX002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06752: "can't initialize index scans using unusable local index '%s'"
+
+SQLSTATE: XX002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06753: "mergejoin clause is not an OpExpr %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06754: "cannot merge using non-equality operator %u, strategy is %d"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06755: "mj_InnerTupleSlot cannot be NULL"
+
+SQLSTATE: XX005
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06756: "RIGHT JOIN is only supported with merge-joinable join conditions."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06757: "FULL JOIN is only supported with merge-joinable join conditions."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06758: "unrecognized join type: %d for mergejoin."
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06759: "INSERT ON DUPLICATE KEY UPDATE does not support deferrable unique constraints/exclusion constraints."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06760: "could not create exclusion constraint '%s' when trying to build a new index"
+
+SQLSTATE: 23P01
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06761 - GAUSS-06770
+
+<br/>
+
+GAUSS-06761: "paramname should not be NULL"
+
+SQLSTATE: XX005
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06762: "cache lookup failed for function %u when initialize function cache."
+
+SQLSTATE: 29P01
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06763: "null prosrc for function %u when we need the function body text"
+
+SQLSTATE: 42P13
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06764: "function returns VOID, failed to get junk filter's slot"
+
+SQLSTATE: 29P02
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06765: "return type %s is not supported for SQL functions with ID %u."
+
+SQLSTATE: 42P13
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06766: "unrecognized node type: %d when initializing executor."
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06767: "unrecognized node type: %d when executing multi executor node."
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06768: "unrecognized node type: %d when ending executor."
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06769: "max iteration times %d hit when looping over right plan tree."
+
+SQLSTATE: 53400
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06770: "MPP with-recursive in node->shareContext is NULL in distributed mode "
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06771 - GAUSS-06780
+
+<br/>
+
+GAUSS-06771: "Unsupported hashing for recursive union"
+
+SQLSTATE: XX006
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06772: "SycUP stream node is not found"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06773: "Unsupported SyncController type typeid:%d typename%s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06774: "more than one sync-up stream node"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06775: "un-recognize steps for consumer side when synchronizing recusive-union."
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06776: "un-recognized steps for producer side when sychronizing recursive-union."
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06777: "MPP with-recursive. Controller is not found in ExecSyncStreamProducer with stream[%d] top:%s"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06778: "need_rescan should not be NULL"
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06779: "MPP With-Recursive sync controller for Stream[%d] is not found"
+
+SQLSTATE: XX005
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06780: "MPP with-recursive datanode:%s CTE(%d) none_recursive_finished is not set to finish"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06781 - GAUSS-06790
+
+<br/>
+
+GAUSS-06781: "MPP with-recursive datanode:%s CTE(%d) recursive_union_finish is not set to finish"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06782: "MPP with-recursive step information in SyncUpController is not correct %d"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06783: "Invalid start next recursvie iteration when kick-off the whole cluster."
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06784: "ORDER BY with column index is not supported"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06785: "can not cast from type %s to type %s "
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06786: "invalid operation on partition, allowed are UPDATE/DELETE/SELECT/MERGE"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06787: "Fail to find partition from sequence."
+
+SQLSTATE: XX005
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06788: "The left value of the expression should not be NULL"
+
+SQLSTATE: XX005
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06789: "Fail to get the right value of the expression"
+
+SQLSTATE: XX005
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06790: "unrecognized node type: %s"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06791 - GAUSS-06800
+
+<br/>
+
+GAUSS-06791: "hash bucket is not supported in column store."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06792: "Unexpected vector hash aggregation status"
+
+SQLSTATE: XX006
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06793: "Unexpected vector hashagg status"
+
+SQLSTATE: XX006
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06794: "TIMESERIES store dose not support this operation"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06795: "TIMESERIES store unsupport none partitioned table"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06796: "could not write to hashJoin temporary file: %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06797: "could not read hashkey from hash-join temporary file: %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06798: "unrecognize data type %u."
+
+SQLSTATE: 42P18
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06799: "Unsupported window function %u in vector engine"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06800: "UnSupported vector window aggregation function %u"
+
+SQLSTATE: 42P25
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/69-GAUSS-06801-GAUSS-06900.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/69-GAUSS-06801-GAUSS-06900.md
new file mode 100644
index 0000000000000000000000000000000000000000..d0a5a85f4c6ade55a7336e0aa81daf467807e3a7
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/69-GAUSS-06801-GAUSS-06900.md
@@ -0,0 +1,868 @@
+---
+title: GAUSS-06801 - GAUSS-06900
+summary: GAUSS-06801 - GAUSS-06900
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-06801 - GAUSS-06900
+
+<br/>
+
+## GAUSS-06801 - GAUSS-06810
+
+<br/>
+
+GAUSS-06801: "invalid datum int array size %d"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06802: "[SonicHash] Unsupport sonic data desc size %d without tuple desc"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06803: "[SonicHash] Unrecognize data type %u with tuple desc"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06804: "[VecSonicHashJoin: write numeric atom occurs error.]"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06805: "m_curFlag should not be NULL"
+
+SQLSTATE: 22004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06806: "[VecSonicHashJoin: load numeric atom occurs error.]"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06807: "Unrecognized vector sonic hashjoin run status."
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06808: "Unrecognize data type %u when choosing match functions from inner hash keys."
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06809: "Unrecognize data type %u when choosing match functions from outer hash keys."
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06810: "SonicHashJoin reportSorthashinfo: Unsupport report type %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06811 - GAUSS-06820
+
+<br/>
+
+GAUSS-06811: "[SonicHash] Unrecognize desc type %d with type oid %u"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06812: "[SonicHash] The number of rows is greater than SONIC_MAX_ROWS %u, which is not supported for hash table construction."
+
+SQLSTATE: P0003
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06813: "[SonicHash] Unrecognized datetype %u, attrlen %d when init hash functions."
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06814: "Unrecognized vector sonic hashagg run status."
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06815: "Unrecognized vector sonic hashagg data status."
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06816: "Unrecognized vector sonic hash aggregation status."
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06817: "[SonicHash] could not rewind sonic hash-join temporary file: %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06818: "[SonicHash] Int has unknown type size of %d"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06819: "[VecSonicHashJoin: reading numeric occurs error.]"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06820: "Unimplemented vector node %s"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06821 - GAUSS-06830
+
+<br/>
+
+GAUSS-06821: "unrecognized node type: %s in function ExecVecMarkPos"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06822: "unrecognized node type: %s in ExecRestrPos"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06823: "Type of parameter %d (%s) does not match that when preparing the plan (%s)"
+
+SQLSTATE: 42804
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06824: "No value found for parameter %d"
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06825: "Unrecognized RowCompareType: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06826: "Unrecognized nulltesttype: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06827: "nvalues: %d is invalid"
+
+SQLSTATE: 22015
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06828: "udfInfo->allocRows: %d is not enough"
+
+SQLSTATE: 22015
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06829: "UnSupported vector function %u"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06830: "unrecognized paramtype: %d"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06831 - GAUSS-06840
+
+<br/>
+
+GAUSS-06831: "Unaligned rows for batches need to be expression evaluation"
+
+SQLSTATE: 23514
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06832: "LZ4 decompress failed when deserializing message, return %d, compressed length %d, original length %d"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06833: "[%s] no such label found"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06834: "Unsupported policy filter values"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06835: "%s policy already exists, create failed"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06836: "Unsupported policy type"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06837: "%s no such policy found, alter failed"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06838: "%s policy does not exist, drop failed"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06839: "Cache lookup failed for relation %u"
+
+SQLSTATE: 29P01
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06840: "Do not support policy label on temp table '%s'"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06841 - GAUSS-06850
+
+<br/>
+
+GAUSS-06841: "[%s] no such schema found"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06842: "[%s.%s] no such relation found"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06843: "[%s.%s] no such view found"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06844: "[%s.%s.%s] no such relation column found"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06845: "[%s.%s] no such function found"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06846: "Column %s already in other label"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06847: "Column name without table"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06848: "%s label already defined"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06849: "Resource %s %s already exists in label %s"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06850: "No such resource %s %s found in label %s"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06851 - GAUSS-06860
+
+<br/>
+
+GAUSS-06851: "Could not find tuple for label %lld"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06852: "%s no such label found"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06853: "One or more labels bound to policies - cannot drop"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06854: "Masking policy can only operate on column object."
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06855: "Masking policy can only operate on column of ordinary table."
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06856: "current policy is conflict with exist policy: %s"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06857: "unsupported policy filter values"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06858: "policy %s not exists."
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06859: "app: [%s] is invalid"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06860: "ip range: [%s] is invalid, please identify"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06861 - GAUSS-06870
+
+<br/>
+
+GAUSS-06861: "role: [%s] is invalid"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06862: "filter: [%s] is invalid"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06863: "length of session ip buffer should more than 128"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06864: "invalid value for 64-bit integer option '%s': %s"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06865: "Value '%s' of option 'compression' is invalid for timeseries table"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06866: "Invalid interval string for 'ttl' option"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06867: "Invalid interval range for 'ttl' option"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06868: "Invalid interval string for 'period' option"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06869: "Invalid interval range for 'period' option"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06870: "invalid value for 'append_mode' option"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06871 - GAUSS-06880
+
+<br/>
+
+GAUSS-06871: "The split flag should exactly be one character and can not be NULL."
+
+SQLSTATE: 2200F
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06872: "%s is not supported by pound parser."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06873: "number of columns (%u) exceeds limit (%d)"
+
+SQLSTATE: 54011
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06874: "index is not correct"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06875: "data length is not correct"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06876: "unrecognized batch compress type"
+
+SQLSTATE: 42804
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06877: "the attribute column of user defined CompositeType does not support view type '%s' "
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06878: "unsupport connector type %d"
+
+SQLSTATE: HV00N
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06879: "Invalid file size is found on file: %s."
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06880: "Failed to parse the postscript from string"
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06881 - GAUSS-06890
+
+<br/>
+
+GAUSS-06881: "Failed to parse the filefooter from string"
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06882: "Error occurred while reading column %d: ORC and mpp types do not match, ORC type is %s and mpp type is %s."
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06883: "Error occurs while reading orc file %s, detail can be found in dn log of %s."
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06884: "The type of decimal(precision>38) doesn't support predicate pushdown."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06885: "Unsupported var type %u from data type %s(%u)."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06886: "Unsupported data type : %s."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06887: "Error occurs while reading parquet file %s, detail can be found in dn log of %s."
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06888: "Error occurred while reading column %d: PARQUET and mpp types do not match, PARQUET type is %s(%s) and mpp type is %s."
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06889: "Unsupported parquet type : %u."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06890: "Before encoding, the length of data as partition directory name must be less than dfs_partition_directory_length(%d)/3."
+
+SQLSTATE: 53400
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06891 - GAUSS-06900
+
+<br/>
+
+GAUSS-06891: "line is larger than 1GB."
+
+SQLSTATE: 22P04
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06892: "Indicates the restriction's level is undefined."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06893: "get min max statistics false."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06894: "Unsupported data type for min-max filter: %s(%u)."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06895: "Error occurred while reading column %d: carbondata and kernel types do not match, carbondata type is %s and kernel type is %s."
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06896: "Unsupported var type %s from data type %s."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06897: "Error occurred while reading column %d: carbondata and kernel types do not match, carbondata type is %s(%d,%d) and kernel type is %s."
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06898: "Unsupported data type : %s for predicate filter."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06899: "Unsupported carbondata type : %s."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06900: "Failed to alloc the space to fileFooter."
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/7-GAUSS-00601-GAUSS-00700.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/7-GAUSS-00601-GAUSS-00700.md
new file mode 100644
index 0000000000000000000000000000000000000000..0b6fca41ea2384a05cecf36627a2ecf25cf7102f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/7-GAUSS-00601-GAUSS-00700.md
@@ -0,0 +1,748 @@
+---
+title: GAUSS-00601 - GAUSS-00700
+summary: GAUSS-00601 - GAUSS-00700
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-00601 - GAUSS-00700
+
+<br/>
+
+## GAUSS-00601 - GAUSS-00610
+
+<br/>
+
+### GAUSS-00601: "Permission denied."
+
+SQLSTATE: 42501
+
+错误原因: CREATE/ALTER/DROP ROLE没有权限操作失败。
+
+解决办法: 确认当前用户是否有权限。
+
+### GAUSS-00602: "Separation of privileges is used,user can't be altered because of too many privileges."
+
+SQLSTATE: 42501
+
+错误原因: 使用三权分立，为用户指定的权限超出范围。
+
+解决办法: 确认三权分立下为用户指定的权限没有超出范围。
+
+### GAUSS-00603: "The account has been locked."
+
+SQLSTATE: 28000
+
+错误原因: 非法操作，帐号被锁定。
+
+解决办法: 联系系统管理员进行处理。通常系统管理员会确认该用户是否有非法操作。确认无非法操作后才会协助进行帐号解锁。
+
+### GAUSS-00606: "The role's password is null in pg_authid, REPLACE should not be specified."
+
+SQLSTATE: XX000
+
+错误原因: 修改密码失败，用户未指定密码，不能指定REPLACE。
+
+解决办法: 请指定密码。
+
+### GAUSS-00610: "Permission denied to drop role."
+
+SQLSTATE: 42501
+
+错误原因: DROP ROLE失败，没有权限。
+
+解决办法: 确认当前用户是否有权限。
+
+<br/>
+
+## GAUSS-00611 - GAUSS-00620
+
+<br/>
+
+### GAUSS-00611: "fail to drop the current schema"
+
+SQLSTATE: 55006
+
+错误原因: DROP ROLE失败，删除当前schema失败。
+
+解决办法: 不能删除当前用户。
+
+### GAUSS-00612: "current user cannot be dropped"
+
+SQLSTATE: 55006
+
+错误原因: DROP ROLE失败，当前用户不能被删除。
+
+解决办法: 不能删除当前用户。
+
+### GAUSS-00613: "session user cannot be dropped"
+
+SQLSTATE: 55006
+
+错误原因: DROP ROLE失败，连接当前会话的用户不能删除。
+
+解决办法: 不能删除当前会员用户。
+
+### GAUSS-00615: "role '%s' cannot be dropped because some objects depend on it"
+
+SQLSTATE: 2BP01
+
+错误原因: DROP ROLE失败，存在依赖当前用户的对象。
+
+解决办法: 消除依赖后重新尝试。
+
+### GAUSS-00616: "session user cannot be renamed"
+
+SQLSTATE: 0A000
+
+错误原因: 更名失败，当前会话用户不能更名。
+
+解决办法: 请使用其他有权限的用户重试。
+
+### GAUSS-00617: "current user cannot be renamed"
+
+SQLSTATE: 0A000
+
+错误原因: 更名失败，当前用户不能被更名。
+
+解决办法: 当前会话用户不能更名。
+
+### GAUSS-00620: "Permission denied to rename role."
+
+SQLSTATE: 42501
+
+错误原因: 没有权限对用户进行重命名。
+
+解决办法: 请确认当前用户是否有权限。
+
+<br/>
+
+## GAUSS-00621 - GAUSS-00630
+
+<br/>
+
+### GAUSS-00621: "column names cannot be included in GRANT/REVOKE ROLE"
+
+SQLSTATE: 0LP01
+
+错误原因: GRANT/REVOKE ROLE包含列名。
+
+解决办法: GRANT/REVOKE ROLE不能包含列名。
+
+### GAUSS-00622: "Permission denied to drop objects."
+
+SQLSTATE: 42501
+
+错误原因: 删除用户拥有的对象失败。
+
+解决办法: 确认当前用户是否有权限。
+
+### GAUSS-00623: "Permission denied to reassign objects."
+
+SQLSTATE: 42501
+
+错误原因: 重新为用户分配对象失败。
+
+解决办法: 确认当前用户是否有权限。
+
+### GAUSS-00625: "must have admin option on role '%s'"
+
+SQLSTATE: 42501
+
+错误原因: 系统管理员用户却不具有SYSADMIN属性。
+
+解决办法: 创建系统管理员用户时，请指定SYSADMIN属性。
+
+### GAUSS-00626: "must be system admin to set grantor"
+
+SQLSTATE: 42501
+
+错误原因: 设置权限授予者失败。
+
+解决办法: 请使用系统管理员权限设置权限授予者。
+
+### GAUSS-00627: "role '%s' is a member of role '%s'"
+
+SQLSTATE: 0LP01
+
+错误原因: 目标用户已经是某个用户的成员。
+
+解决办法: 检查目标用户是否已经是某个用户的成员。
+
+### GAUSS-00628: "schema '%s' doesnot exist"
+
+SQLSTATE: 3F000
+
+错误原因: schema不存在。
+
+解决办法: 检查schema是否存在。
+
+### GAUSS-00629: "cannot cancel current session's query"
+
+SQLSTATE: 42601
+
+错误原因: cancel当前session的查询失败。
+
+解决办法: 检查是否当前session对用户拥有的对象进行加锁。
+
+### GAUSS-00630: "md5-password encryption failed."
+
+SQLSTATE: XX000
+
+错误原因: MD5加密失败。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-00631 - GAUSS-00640
+
+<br/>
+
+### GAUSS-00631: "sha256-password encryption failed."
+
+SQLSTATE: XX000
+
+错误原因: SHA256加密失败。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00633: "Password must contain at least %d upper characters."
+
+SQLSTATE: 28P01
+
+错误原因: 密码应至少包含由GUC参数password_min_uppercase指定个数的大写字母。
+
+解决办法: 在密码中添加大写字母以满足参数要求。
+
+### GAUSS-00634: "Password must contain at least %d lower characters."
+
+SQLSTATE: 28P01
+
+错误原因: 密码应至少包含由GUC参数password_min_lowercase指定个数的小写字母。
+
+解决办法: 在密码中添加小写字母以满足参数要求。
+
+### GAUSS-00635: "Password must contain at least %d digital characters."
+
+SQLSTATE: 28P01
+
+错误原因: 密码应至少包含由GUC参数password_min_digital指定个数的数字。
+
+解决办法: 在密码中添加数字以满足参数要求。
+
+### GAUSS-00636: "Password must contain at least %d special characters."
+
+SQLSTATE: 28P01
+
+错误原因: 密码应至少包含由GUC参数password_min_special指定个数的特殊字符。
+
+解决办法: 在密码中添加特殊字符以满足参数要求。
+
+### GAUSS-00637: "Password must contain at least three kinds of characters."
+
+SQLSTATE: 28P01
+
+错误原因: 密码包含的字符类型少于3种。
+
+解决办法: "请参照密码规则进行修改: 1. 密码默认不少于8个字符。2. 不能和用户名相同。3. 至少包含大写字母（A-Z），小写字母（a-z），数字（0-9），非字母数字字符（限定为~!@#$%^&*()-_=+\|[{}];:,<.>/?）四类字符中的三类字符。"
+
+### GAUSS-00638: "The parameter roleID of CheckPasswordComplexity is NULL"
+
+SQLSTATE: XX000
+
+错误原因: 密码复杂性检查失败，roleID为空。
+
+解决办法: roleID不能为空。
+
+### GAUSS-00639: "The parameter newPasswd of CheckPasswordComplexity is NULL"
+
+SQLSTATE: XX000
+
+错误原因: 密码复杂性检查失败，新密码为空。
+
+解决办法: 新密码不能为空，请重新输入。
+
+### GAUSS-00640: "Password should not equal to the rolname."
+
+SQLSTATE: XX000
+
+错误原因: 新密码和用户名相同。
+
+解决办法: 不允许密码和用户名相同。请重新选择符合要求的密码。
+
+<br/>
+
+## GAUSS-00641 - GAUSS-00650
+
+<br/>
+
+### GAUSS-00641: "reverse_string failed, possibility out of memory"
+
+SQLSTATE: XX000
+
+错误原因: 密码字符串反转失败。
+
+解决办法: 内部错误，检查是否发生OOM。
+
+### GAUSS-00644: "New password should not equal to the reverse of old ones."
+
+SQLSTATE: XX000
+
+错误原因: 新密码和旧密码的反转相同。
+
+解决办法: 不能和旧密码的反转相同，换一个新的重试。
+
+### GAUSS-00645: "the parameter passwd of AddAuthHistory is null"
+
+SQLSTATE: XX000
+
+错误原因: 添加密码修改记录时密码为空。
+
+解决办法: 添加密码修改记录时密码不能为空。
+
+### GAUSS-00646: "sha256-password encryption failed"
+
+SQLSTATE: XX000
+
+错误原因: SHA256加密失败。
+
+解决办法: 内部错误。
+
+### GAUSS-00647: "The password cannot be reused."
+
+SQLSTATE: XX000
+
+错误原因:  密码不能被重用。
+
+解决办法: 检查新密码与旧密码是否相同，重用条件是否满足。
+
+### GAUSS-00648: "TryLockAccount(): roleid is not valid."
+
+SQLSTATE: XX000
+
+错误原因: roleid无效。
+
+解决办法: 检查roleid是否合法。
+
+### GAUSS-00649: "Permission denied."
+
+SQLSTATE: XX000
+
+错误原因: CREATE/ALTER/DROP ROLE没有权限操作失败。
+
+解决办法: 确认当前用户是否有权限。
+
+### GAUSS-00650: "TryLockAccount(): parameter extrafails is less than zero."
+
+SQLSTATE: XX000
+
+错误原因: 参数extrafails小于0。
+
+解决办法: 保证参数extrafails不小于0。
+
+<br/>
+
+## GAUSS-00651 - GAUSS-00660
+
+<br/>
+
+### GAUSS-00651: "The tuple of pg_user_status not found"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00652: "TryUnlockAccount(): roleid is not valid."
+
+SQLSTATE: XX000
+
+错误原因: roleid无效。
+
+解决办法: 检查roleid是否合法。
+
+### GAUSS-00653: "IsAccountLocked(): roleid is not valid."
+
+SQLSTATE: XX000
+
+错误原因: roleid无效。
+
+解决办法: 检查roleid是否合法。
+
+### GAUSS-00654: "getAccountLockedStyle: roleid is not valid."
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00655: "DropUserStatus(): roleid is not valid."
+
+SQLSTATE: XX000
+
+错误原因: roleid无效。
+
+解决办法: 检查roleid是否合法。
+
+### GAUSS-00656: "Invalid username/password,login denied."
+
+SQLSTATE: 42704
+
+错误原因: 用户名或密码无效，登录失败。
+
+解决办法: 检查登录的用户名和密码是否有效。
+
+### GAUSS-00657: "User's passwordtime in pg_auth_history is 0."
+
+SQLSTATE: 28P01
+
+错误原因: pg_auth_history中对应用户的passwordtime为空。
+
+解决办法: 此列理论上不会为空，若出现问题，请联系技术支持工程师提供技术支持。
+
+### GAUSS-00658: "aggregate stype must be specified"
+
+SQLSTATE: 42P13
+
+错误原因: 聚集函数定义时stype没有指定。
+
+解决办法: 聚集函数定义时必须指定stype。
+
+### GAUSS-00659: "aggregate sfunc must be specified"
+
+SQLSTATE: 42P13
+
+错误原因: 聚集函数定义时sfunc没有指定。
+
+解决办法: 聚集函数定义时必须指定sfunc。
+
+### GAUSS-00660: "aggregate input type must be specified"
+
+SQLSTATE: 42P13
+
+错误原因: 聚集函数定义时input type没有指定。
+
+解决办法: 聚集函数定义时必须指定input type。
+
+<br/>
+
+## GAUSS-00661 - GAUSS-00670
+
+<br/>
+
+### GAUSS-00661: "basetype is redundant with aggregate input type specification"
+
+SQLSTATE: 42P13
+
+错误原因: 聚集函数定义时参数发生冗余。
+
+解决办法: pg8.2之后使用新风格定的聚集函数，不用再指定basetype来表述输入类型。
+
+### GAUSS-00662: "aggregate transition data type cannot be %s"
+
+SQLSTATE: 42P13
+
+错误原因: 聚集函数转换的数据类型有误。
+
+解决办法: 转换类型不能为pseudo-type，对于初始用户转换类型可以为internal。
+
+### GAUSS-00663: "function %s already exists in schema '%s'"
+
+SQLSTATE: 42723
+
+错误原因: 模式下函数已存在。
+
+解决办法: 检查是否存在已定义的同名函数。
+
+### GAUSS-00664: "Unsupport feature"
+
+SQLSTATE: XX000
+
+错误原因: 不支持的特性。
+
+解决办法: 列存表不支持继承和CREATE TABLE OF TYPENAME，检查表定义语句。
+
+### GAUSS-00665: "column store unsupport constraint '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 定义列存表不支持的约束。
+
+解决办法: 列存表仅支持NULL、NOT NULL、DEFAULT、CLUSTER约束。
+
+### GAUSS-00666: "PARTIAL_CLUSTER_ROWS cannot be less than MAX_BATCHROW."
+
+SQLSTATE: 42P16
+
+错误原因: PARTIAL_CLUSTER_ROWS小于MAX_BATCHROW。
+
+解决办法: PARTIAL_CLUSTER_ROWS必须大于或等于MAX_BATCHROW。
+
+### GAUSS-00667: "ON COMMIT can only be used on temporary tables"
+
+SQLSTATE: 42P16
+
+错误原因: ON COMMIT参数用于非临时表。
+
+解决办法: ON COMMIT参数只能用于临时表。
+
+### GAUSS-00668: "constraints on foreign tables are not supported"
+
+SQLSTATE: 42809
+
+错误原因: 为外表定义约束。
+
+解决办法: 外表不支持约束。
+
+### GAUSS-00669: "cannot create temporary table within security-restricted operation"
+
+SQLSTATE: 42501
+
+错误原因:  安全限制的情形下创建临时表。
+
+解决办法: 安全限制的情形下禁止创建临时表。
+
+### GAUSS-00670: "only shared relations can be placed in pg_global tablespace"
+
+SQLSTATE: 22023
+
+错误原因: 用户定义的relation不能置于pg_global表空间下。
+
+解决办法: 只有共享的relation可以置于pg_global表空间下。
+
+<br/>
+
+## GAUSS-00671 - GAUSS-00680
+
+<br/>
+
+### GAUSS-00673: "default values on foreign tables are not supported"
+
+SQLSTATE: 42809
+
+错误原因: 定义外表时列指定默认值。
+
+解决办法: 外表不支持列指定默认值。
+
+### GAUSS-00674: "No Datanode defined in cluster"
+
+SQLSTATE: 42704
+
+错误原因: 数据节点未定义。
+
+解决办法: 为当前集群创建数据节点。
+
+### GAUSS-00675: "DROP INDEX CONCURRENTLY does not support dropping multiple objects"
+
+SQLSTATE: 0A000
+
+错误原因: DROP INDEX CONCURRENTLY语句删除多个对象，因为此语句不支持删除多个对象。
+
+解决办法: 禁止删除多个对象的操作。
+
+### GAUSS-00676: "DROP INDEX CONCURRENTLY does not support CASCADE"
+
+SQLSTATE: 0A000
+
+错误原因: DROP INDEX CONCURRENTLY语句指定CASCADE。
+
+解决办法: DROP INDEX CONCURRENTLY语句不支持指定CASCADE。
+
+### GAUSS-00677: "unrecognized drop object type: %d"
+
+SQLSTATE: XX000
+
+错误原因: 对象drop类型不支持。
+
+解决办法: 检查对象drop类型是否支持。
+
+### GAUSS-00678: "permission denied: '%s' is a system catalog"
+
+SQLSTATE: 42501
+
+错误原因: 该表为系统表，用户没有权限删除系统表。
+
+解决办法: 禁止删除系统表。
+
+### GAUSS-00679: "PGXC does not support RESTART IDENTITY yet"
+
+SQLSTATE: 0A000
+
+错误原因: TRUNCATE语句指定RESTART IDENTITY。
+
+解决办法: 暂时不支持TRUNCATE语句指定RESTART IDENTITY。
+
+<br/>
+
+## GAUSS-00681 - GAUSS-00690
+
+<br/>
+
+### GAUSS-00681: "'%s' is not a table"
+
+SQLSTATE: 42809
+
+错误原因: truncate的对象不是一个表。
+
+解决办法: truncate的对象需要是一个表。
+
+### GAUSS-00682: "cannot truncate temporary tables of other sessions"
+
+SQLSTATE: 0A000
+
+错误原因: truncate其他session的临时表。
+
+解决办法: 请勿truncate其他session的临时表。
+
+### GAUSS-00683: "tables can have at most %d columns"
+
+SQLSTATE: 54011
+
+错误原因: 表超过1600列。
+
+解决办法: 表最多拥有1600列。
+
+### GAUSS-00684: "cannot inherit from temporary relation '%s'"
+
+SQLSTATE: 42809
+
+错误原因: 继承临时表。
+
+解决办法: 临时表仅当前session可见，请勿继承临时表。
+
+### GAUSS-00685: "cannot inherit from temporary relation of another session"
+
+SQLSTATE: 42809
+
+错误原因: 继承临时表。
+
+解决办法: 临时表仅当前session可见，请勿继承临时表。
+
+### GAUSS-00686: "relation '%s' would be inherited from more than once"
+
+SQLSTATE: 42P07
+
+错误原因: 表被继承多次。
+
+解决办法: 检查建表语句，确保继承的表中没有重复表。
+
+### GAUSS-00687: "inherited column '%s' has a type conflict"
+
+SQLSTATE: 42804
+
+错误原因: 继承的列存在类型冲突。
+
+解决办法: 检查类型是否一致。
+
+### GAUSS-00688: "inherited column '%s' has a collation conflict"
+
+SQLSTATE: 42P21
+
+错误原因: 继承的列存在排序规则冲突。
+
+解决办法: 检查排序规则是否一致。
+
+### GAUSS-00689: "inherited column '%s' has a storage parameter conflict"
+
+SQLSTATE: 42804
+
+错误原因: 继承的列存在存储参数冲突。
+
+解决办法: 检查存储参数是否一致。
+
+### GAUSS-00690: "column '%s' has a type conflict"
+
+SQLSTATE: 42804
+
+错误原因: 列存在类型冲突。
+
+解决办法: 检查类型是否一致。
+
+<br/>
+
+## GAUSS-00691 - GAUSS-00700
+
+<br/>
+
+### GAUSS-00691: "column '%s' has a collation conflict"
+
+SQLSTATE: 42P21
+
+错误原因: 列存在排序规则冲突。
+
+解决办法: 检查排序规则是否一致。
+
+### GAUSS-00692: "column '%s' has a storage parameter conflict"
+
+SQLSTATE: 42804
+
+错误原因: 列存在存储参数冲突。
+
+解决办法: 检查存储参数是否一致。
+
+### GAUSS-00693: "column '%s' inherits conflicting default values"
+
+SQLSTATE: 42611
+
+错误原因: 列继承与默认值冲突。
+
+解决办法: 列继承不能和默认值冲突。
+
+### GAUSS-00694: "check constraint name '%s' appears multiple times but with different expressions"
+
+SQLSTATE: 42710
+
+错误原因: 不同表达式的check约束名出现多次。
+
+解决办法: 检查不同表达式的check约束名是否出现多次。
+
+### GAUSS-00695: "cannot rename column of typed table"
+
+SQLSTATE: 42809
+
+错误原因: 对type进行更名操作。
+
+解决办法: 不能修改type的列名。
+
+### GAUSS-00696: "'%s' is not a table, view, composite type, index, or foreign table"
+
+SQLSTATE: 42809
+
+错误原因: 更名的对象不是一个表。
+
+解决办法: 不能修改视图、类型、索引或外表的列名。
+
+### GAUSS-00697: "inherited column '%s' must be renamed in child tables too"
+
+SQLSTATE: 42P16
+
+错误原因: 继承的列在更名时没有在子表中进行修改。
+
+解决办法: 继承的列在更名时必须在子表中进行修改。
+
+### GAUSS-00698: "cannot rename system column '%s'"
+
+SQLSTATE: 0A000
+
+错误原因: 修改系统预留列的列名。
+
+解决办法: 不支持修改系统预留列的列名。
+
+### GAUSS-00699: "cannot rename inherited column '%s'"
+
+SQLSTATE: 42P16
+
+错误原因: 修改继承的列名。
+
+解决办法: 禁止修改继承的列名。
+
+### GAUSS-00700: "inherited constraint '%s' must be renamed in child tables too"
+
+SQLSTATE: 42P16
+
+错误原因: 继承的约束在更名时没有在子表中进行修改。
+
+解决办法: 继承的约束在更名时必须在子表中进行修改。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/70-GAUSS-06901-GAUSS-07000.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/70-GAUSS-06901-GAUSS-07000.md
new file mode 100644
index 0000000000000000000000000000000000000000..ecb100b45b12db99b2492afd67af093d51f5f236
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/70-GAUSS-06901-GAUSS-07000.md
@@ -0,0 +1,868 @@
+---
+title: GAUSS-06901 - GAUSS-07000
+summary: GAUSS-06901 - GAUSS-07000
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-06901 - GAUSS-07000
+
+<br/>
+
+## GAUSS-06901 - GAUSS-06910
+
+<br/>
+
+GAUSS-06901: "Failed to alloc the space to fileHeader."
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06902: "Failed to alloc the space to fileReader."
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06903: "Can't find .carbondata file."
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06904: "'type' option is not provided."
+
+SQLSTATE: 42P17
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06905: "No 'type' option provided."
+
+SQLSTATE: 42P17
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06906: "setMinMaxByHeapTuple"
+
+SQLSTATE: 20000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06907: "delete or update failed due to concurrent conflict"
+
+SQLSTATE: P0002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06908: "getting next tuple in an ordered catalog scan failed"
+
+SQLSTATE: P0002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06909: "read handler is not in pending_free_reader_list"
+
+SQLSTATE: D0009
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06910: "write handler is not in pending_free_writer_list"
+
+SQLSTATE: D0009
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06911 - GAUSS-06920
+
+<br/>
+
+GAUSS-06911: "Only ORC/PARQUET/CARBONDATA/CSV/TEXT is supported for now."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06912: "Failed to get currentFileName !"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06913: "setDescByFilePath cannot find filename"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06914: "Rigth operation in constraint expression cannot be NULL."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06915: "Invalid Oid for operator %u."
+
+SQLSTATE: 20000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06916: "Unsupported data type on typeoid:%u when converting string to datum."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06917: "Unsupported data type on typeoid:%u when converting datum to string."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06918: "The leftop is null"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06919: "The rightop is null"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06920: "The arg is null"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06921 - GAUSS-06930
+
+<br/>
+
+GAUSS-06921: "bloomFilter create failed"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06922: "empty partition expression"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06923: "Invalid partition expression:%s"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06924: "argument to option'%s' must be a valid encoding name"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06925: "Column %s is unsupported data type."
+
+SQLSTATE: HV004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06926: "No %s is specified for the foreign table."
+
+SQLSTATE: 44000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06927: "Unsupport any empy %s for the foreign table."
+
+SQLSTATE: 44000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06928: "The first character and the end character of each %s must be a '/' in string '%s'."
+
+SQLSTATE: 42P17
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06929: "No folder path is specified for the foreign table."
+
+SQLSTATE: 44000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06930: "No file path is specified for the foreign table."
+
+SQLSTATE: 44000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06931 - GAUSS-06940
+
+<br/>
+
+GAUSS-06931: "No hdfscfg path is specified for the server."
+
+SQLSTATE: 44000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06932: "Only a folder path is allowed for the foreign table."
+
+SQLSTATE: 44000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06933: "Only a hdfscfg path is allowed for the server."
+
+SQLSTATE: 44000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06934: "No address is specified for the server."
+
+SQLSTATE: 44000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06935: "The port value is out of range: \'%s\'"
+
+SQLSTATE: 44000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06936: "Please select other functions to parse deciaml data."
+
+SQLSTATE: HV004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06937: "The incorrect numeric format."
+
+SQLSTATE: HV004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06938: "index row size %zu exceeds maximum %zu for index '%s'"
+
+SQLSTATE: 54000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06939: "number of items mismatch in GIN entry tuple, %d in tuple header, %d decoded"
+
+SQLSTATE: XX002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06940: "Invalid arguments for function ginbuild"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06941 - GAUSS-06950
+
+<br/>
+
+GAUSS-06941: "Invalid arguments for function cginbuild"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06942: "access method 'cgin' does not support multi column index with operator ||"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06943: "access method 'cgin' does not support null column index"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06944: "Invalid arguments for function gininsert"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06945: "invalid item pointer."
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06946: "Invalid arguments for function ginarrayextract"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06947: "Invalid arguments for function ginqueryarrayextract"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06948: "right sibling of GIN page is of different type"
+
+SQLSTATE: XX002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06949: "right sibling of GIN page was deleted"
+
+SQLSTATE: XX002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06950: "invalid return code from GIN placeToPage method: %d"
+
+SQLSTATE: XX002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06951 - GAUSS-06960
+
+<br/>
+
+GAUSS-06951: "'%s' is not a GIN index"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06952: "cannot access temporary indexes of other sessions"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06953: "unexpected GIN leaf action: %hhu"
+
+SQLSTATE: 2200G
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06954: "GIN split record did not contain a full-page image of left page"
+
+SQLSTATE: XX002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06955: "GIN split record did not contain a full-page image of right page"
+
+SQLSTATE: XX002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06956: "GIN split record did not contain a full-page image of root page"
+
+SQLSTATE: XX002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06957: "replay of gin entry tree page vacuum did not restore the page"
+
+SQLSTATE: XX002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06958: "gin_redo: unknown op code %hhu"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06959: "unexpected order by operator: %d"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06960: "Invalid arguments for function ginrescan"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06961 - GAUSS-06970
+
+<br/>
+
+GAUSS-06961: "Invalid arguments for function ginendscan"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06962: "posting list is too long"
+
+SQLSTATE: 54000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06963: "could not split GIN page; all old items didn't fit"
+
+SQLSTATE: XX002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06964: "could not split GIN page; no new items fit"
+
+SQLSTATE: XX002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06965: "could not fit vacuumed posting list"
+
+SQLSTATE: XX002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06966: "Invalid arguments for function ginbulkdelete"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06967: "Invalid arguments for function ginvacuumcleanup"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06968: "missing GIN support function (%d or %d) for attribute %d of index '%s'"
+
+SQLSTATE: 42883
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06969: "invalid attribute num:%hu"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06970: "could not find parent of block %u in lookup table"
+
+SQLSTATE: XX002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06971 - GAUSS-06980
+
+<br/>
+
+GAUSS-06971: "failed to decompress keys in tuple"
+
+SQLSTATE: XX002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06972: "failed to form tuple from gist"
+
+SQLSTATE: XX002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06973: "could not seek temporary file: %ld"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06974: "could not read temporary file: %ld"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06975: "the leaf keys should have the high point equals to the low point"
+
+SQLSTATE: 42P24
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06976: "gist_redo: unknown op code %hhu"
+
+SQLSTATE: XX002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06977: "index '%s' already contains data."
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06978: "no order by operators allowed."
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06979: "hashmerge: unimplemented."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06980: "buckets id %d of table is outsize range [%d,%d]"
+
+SQLSTATE: 22003
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06981 - GAUSS-06990
+
+<br/>
+
+GAUSS-06981: "error format single item string %s"
+
+SQLSTATE: 42602
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06982: "empty merge_list string"
+
+SQLSTATE: 42602
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06983: "find merge_str in pgxc_class and is first set %d"
+
+SQLSTATE: 42602
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06984: "not find merge_str in pgxc_class and not first set %d"
+
+SQLSTATE: 42602
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06985: "could not truncate file '%s' to %u: %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06986: "could not seek to the end of file '%s': %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06987: "could not parse filename '%s'"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06988: "wrong VM buffer passed to visibilitymap_set"
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06989: "attempt to delete tuple containing indirect datums"
+
+SQLSTATE: 29P02
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06990: "shouldn't be called for indirect tuples"
+
+SQLSTATE: 29P02
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-06991 - GAUSS-07000
+
+<br/>
+
+GAUSS-06991: "attempted to kill a tuple inserted by another transaction: %lu, %lu"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06992: "Can't fit xid into page. relation '%s', now xid is %lu, base is %lu, min is %u, max is %u"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06993: "Can't fit xid into page, now xid is %lu, base is %lu, min is %u, max is %u"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06994: "heap_delete: invalid tid %hu, max tid %hu, rnode[%u,%u,%u], block %u"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06995: "attempted to delete self created tuple"
+
+SQLSTATE: 40001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06996: "pg_class entry for relid %u vanished during ExtractReplicaIdentity"
+
+SQLSTATE: 40001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06997: "heap_update: invalid tid %hu, max tid %hu, rnode[%u,%u,%u], block %u"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06998: "attempted to update self created tuple"
+
+SQLSTATE: 40001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-06999: "relation '%s' has one big row which is not supported under 64bits XID system. Current xid is %lu"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07000: "relation '%s' has no free space to upgrade. Current xid is %lu, please VACUUM FULL this relation!!!"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/71-GAUSS-07001-GAUSS-07100.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/71-GAUSS-07001-GAUSS-07100.md
new file mode 100644
index 0000000000000000000000000000000000000000..870a9e034293768e601c7c2b28b7a31bed84b358
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/71-GAUSS-07001-GAUSS-07100.md
@@ -0,0 +1,868 @@
+---
+title: GAUSS-07001 - GAUSS-07100
+summary: GAUSS-07001 - GAUSS-07100
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-07001 - GAUSS-07100
+
+<br/>
+
+## GAUSS-07001 - GAUSS-07010
+
+<br/>
+
+GAUSS-07001: "All built-in functions are hard coded, and they should not be updated."
+
+SQLSTATE: 55000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07002: "system column in index"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07003: "unexpected result when restoring backup block"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07004: "heap_multi_insert_redo: total tuple length mismatch"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07005: "heap_inplace_redo: no tuple data"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07006: "heap_redo: unknown op code %hhu"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07007: "heap2_redo: unknown op code %hhu"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07008: "heap3_redo: unknown op code %hhu"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07009: "partition %u is invalid"
+
+SQLSTATE: 29P04
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07010: "Invalid arguments for function btgettuple"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07011 - GAUSS-07020
+
+<br/>
+
+GAUSS-07011: "version mismatch in index '%s': file version %u, code version %d"
+
+SQLSTATE: XX002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07012: "failed to add old item to left page after split"
+
+SQLSTATE: XX002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07013: "btree_redo: unknown op code %hhu"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07014: "Failed to check input value: invalid token '%s'."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07015: "invalid client_crt_filepath length %lu"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07016: "Fail to list bucket object in node:%s with error code: %s, %s the bucket name: %s, prefix name: %s"
+
+SQLSTATE: 29000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07017: "Datanode '%s' fail to read OBS object bucket:'%s' key:'%s' with OBS error code:%s %s"
+
+SQLSTATE: 29000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07018: "Fail to flush data content to OBS in buffile offset ['%d'] to_write ['%d']"
+
+SQLSTATE: 29P03
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07019: "Datanode '%s' fail to seek buffer file be (0, 0) after reset actual length"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07020: "Datanode '%s' fail to write OBS object %s with OBS error code:%s %s"
+
+SQLSTATE: 29000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07021 - GAUSS-07030
+
+<br/>
+
+GAUSS-07021: "Node '%s' fail to initialize libobs with OBS error code:%s"
+
+SQLSTATE: 29000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07022: "unsupported operation in OBS handler layer"
+
+SQLSTATE: HV00B
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07023: "OBS URL's %s is not valid '%s'"
+
+SQLSTATE: HV00E
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07024: "Fail to connect OBS host %s in node:%s with error code: %s %s"
+
+SQLSTATE: 29000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07025: "failed to add item of size %d to SPGiST index page"
+
+SQLSTATE: XX002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07026: "reconstrValue is NULL but level = %d (not zero)."
+
+SQLSTATE: XX002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07027: "variable page should not be NULL"
+
+SQLSTATE: XX005
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07028: "sem_destroy failed: %m"
+
+SQLSTATE: DB001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07029: "[REDO_LOG_TRACE]ApplyReadyTxnShareLogRecords encounter fatal error:rmgrID:%u, info:%u, sharcount:%u"
+
+SQLSTATE: DB001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07030: "[REDO_LOG_TRACE]ApplyReadyTxnShareLogRecords encounter fatal error:rmgrID:%u, info:%u, sharcount:%u, refcount:%u"
+
+SQLSTATE: DB001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07031 - GAUSS-07040
+
+<br/>
+
+GAUSS-07031: "[REDO_LOG_TRACE]ApplyReadyTxnShareLogRecords encounter fatal error:rmgrID:%u, info:%u, designatedWorker:%u"
+
+SQLSTATE: DB001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07032: "[REDO_LOG_TRACE]ApplyReadyAllShareLogRecords encounter fatal error:rmgrID:%u, info:%u, sharcount:%u"
+
+SQLSTATE: DB001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07033: "[REDO_LOG_TRACE]ApplyReadyAllShareLogRecords encounter fatal error:rmgrID:%u, info:%u, sharcount:%u, refcount:%u"
+
+SQLSTATE: DB001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07034: "[REDO_LOG_TRACE]ApplyMultiPageAllWorkerRecord encounter fatal error:rmgrID:%u, info:%u"
+
+SQLSTATE: DB001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07035: "[REDO_LOG_TRACE]ApplyMultiPageShareWithTrxnRecord encounter fatal error:rmgrID:%u, info:%u, designatedWorker:%u"
+
+SQLSTATE: DB001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07036: "[REDO_LOG_TRACE]ApplyMultiPageShareWithTrxnRecord encounter fatal error:rmgrID:%u, info:%u"
+
+SQLSTATE: DB001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07037: "WaitWorkerReady failed, no worker is ready for work. totalWorkerCount :%u"
+
+SQLSTATE: DB001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07038: "CheckAlivePageWorkers: thread %lu is still alive"
+
+SQLSTATE: DB001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07039: "[REDO_LOG_TRACE]StartPageRedoWorkers we need at least one worker thread"
+
+SQLSTATE: DB001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07040: "[REDO_LOG_TRACE]DispatchRedoRecord encounter fatal error:rmgrID:%u, info:%u, indexid:%u"
+
+SQLSTATE: DB001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07041 - GAUSS-07050
+
+<br/>
+
+GAUSS-07041: "[REDO_LOG_TRACE]AddWorkerToSet:input work id error, id:%u, work num %u"
+
+SQLSTATE: DB001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07042: "Allocated record buffer failed!, cur item:%u, max item:%u"
+
+SQLSTATE: DB001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07043: "Allocated blocks data failed!, cur item:%u, max item:%u"
+
+SQLSTATE: DB001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07044: "Allocated main_data failed!, cur item:%u, max item:%u"
+
+SQLSTATE: DB001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07045: "NewReaderState Dispatch is null"
+
+SQLSTATE: DB001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07046: "Must be system admin or operator admin in operation mode to get cbm merged file."
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07047: "memory is temporarily unavailable while allocate block string"
+
+SQLSTATE: 53000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07048: "Negative timeout for force track cbm!"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07049: "Timeout happened during force track cbm!"
+
+SQLSTATE: YY004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07050: "start xlog location %X/%X should be smaller than end xlog location %X/%X"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07051 - GAUSS-07060
+
+<br/>
+
+GAUSS-07051: "end xlog location %X/%X should be smaller than already tracked xlog location %X/%X"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07052: "cannot mark transaction %lu committed without CSN %lu"
+
+SQLSTATE: 58030
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07053: "pg_csnlog contains invalid entry: xid %lu points to parent xid %lu"
+
+SQLSTATE: 58030
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07054: "csn log state change from %lu to %lu is not allowed!"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07055: "Snapshot too old when read CSN, this is a safe errorif there is breakdown in gtm of CN log"
+
+SQLSTATE: YY014
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07056: "Initialize the csn log failed."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07057: "the current transaction %lu is smaller than gtm recent global xmin, so no need to set csn log. pageno: %ld, startExtendCSNLogPage: %ld"
+
+SQLSTATE: YY014
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07058: "The lastExtenPage %ld is larger than newExtendPage %ld,and the newestXact is %lu, the recent global xmin %lu"
+
+SQLSTATE: YY014
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07059: "Length of CBM file home path exceeds MAXPGPATH!"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07060: "Length of absolute CBM file path would exceed MAXPGPATH!"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07061 - GAUSS-07070
+
+<br/>
+
+GAUSS-07061: "memory is temporarily unavailable while allocate page read buffer during validate CBM file"
+
+SQLSTATE: 53000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07062: "Failed to truncate CBM file '%s' to length %ld"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07063: "could not create new CBM file '%s': %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07064: "could not open CBM file '%s': %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07065: "failed to stat current cbm file %s :%m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07066: "The xlog LSN to be parsed %08X/%08X is smaller than already tracked xlog LSN %08X/%08X. This may be caused by xlog truncation (pg_rewind), xlog corruption or PITR (at present CBM does not support multiple timelines). Under these scenarios, inconsistent CBM files may be created. To be safe, we zap all existing CBM files and restart CBM tracking"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07067: "memory is temporarily unavailable while allocate xlog reader"
+
+SQLSTATE: 53000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07068: "could not read WAL record at %08X/%08X: %s"
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07069: "could not read WAL record at %08X/%08X"
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07070: "could not find or create CBM page entry: rel %u/%u/%u forknum %d blkno %u page type %d truncate blkno %u"
+
+SQLSTATE: 29P02
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07071 - GAUSS-07080
+
+<br/>
+
+GAUSS-07071: "memory is temporarily unavailable while allocate new CBM page"
+
+SQLSTATE: 53000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07072: "could not create dummy CBM page entry: rel %u/%u/%u forknum %d"
+
+SQLSTATE: 29P02
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07073: "memory is temporarily unavailable while allocate CBM page header array"
+
+SQLSTATE: 53000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07074: "CBM hash table corrupted"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07075: "fsync CBM file '%s' failed during flushing"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07076: "close CBM file '%s' failed during rotate"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07077: "found invalid CBM file name'%s' before rotate"
+
+SQLSTATE: 42602
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07078: "could not rename file '%s' to '%s' during rotate: %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07079: "could not open CBM file directory '%s': %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07080: "could not find valid CBM file between %08X/%08X and %08X/%08X, which may be caused by previous CBM switch-off, truncation, or corruption"
+
+SQLSTATE: 58P03
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07081 - GAUSS-07090
+
+<br/>
+
+GAUSS-07081: "could not find valid CBM file that contains the merging start point %08X/%08X"
+
+SQLSTATE: 58P03
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07082: "could not find valid CBM file that contains the merging end point %08X/%08X"
+
+SQLSTATE: 58P03
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07083: "there is a gap between CBM file %s and %s, which may be caused by previous CBM switch-off, truncation, or corruption"
+
+SQLSTATE: 29P02
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07084: "memory is temporarily unavailable while allocate page read buffer during merge CBM file array"
+
+SQLSTATE: 53000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07085: "could not open CBM file '%s' while merging: %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07086: "could not find merge start point %08X/%08X in CBM files "
+
+SQLSTATE: 29P02
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07087: "could not find merge end point %08X/%08X in CBM files, the last cbm page end at %08X/%08X"
+
+SQLSTATE: 29P02
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07088: "could not read the first page head of CBM file '%s' "
+
+SQLSTATE: 29P02
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07089: "the first page start LSN %08X/%08X of CBM file '%s' does not equal the file start LSN %08X/%08X"
+
+SQLSTATE: 29P02
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07090: "partial page read occurs at page offset %ld of CBM file '%s', stop reading"
+
+SQLSTATE: 58P03
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07091 - GAUSS-07100
+
+<br/>
+
+GAUSS-07091: "Corruption detected in CBM file '%s', page offset %ld"
+
+SQLSTATE: 58P03
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07092: "LSN track gap detected in CBM file '%s', page offset %ld: previous page batch end LSN is %08X/%08X, current page batch start LSN is %08X/%08X"
+
+SQLSTATE: 29P02
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07093: "Inconsistent start/end LSN in one page batch for CBM file '%s' at page offset %ld: previous page start-end LSN %08X/%08X-%08X/%08X, curent page start-end LSN %08X/%08X-%08X/%08X"
+
+SQLSTATE: 29P02
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07094: "the last read page end LSN %08X/%08X of CBM file '%s' does not equal the file end LSN %08X/%08X"
+
+SQLSTATE: 29P02
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07095: "could not find or create CBM page entry: rel %u/%u/%u forknum %d during merge into hash"
+
+SQLSTATE: 58P03
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07096: "invalid CBM page header: rel %u/%u/%u forknum %d first blkno %u page type %d truncate blkno %u"
+
+SQLSTATE: 29P02
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07097: "could not create merge dest CBM file '%s': %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07098: "memory is temporarily unavailable while allocate CBM array"
+
+SQLSTATE: 53000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07099: "memory is temporarily unavailable while allocate CBM array entry"
+
+SQLSTATE: 53000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07100: "CBM hash table corrupted: incorrect total hash entry number"
+
+SQLSTATE: 29P02
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/72-GAUSS-07101-GAUSS-07200.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/72-GAUSS-07101-GAUSS-07200.md
new file mode 100644
index 0000000000000000000000000000000000000000..e13ef131317cfd32e81c5a9356c56c6782589a06
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/72-GAUSS-07101-GAUSS-07200.md
@@ -0,0 +1,868 @@
+---
+title: GAUSS-07101 - GAUSS-07200
+summary: GAUSS-07101 - GAUSS-07200
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-07101 - GAUSS-07200
+
+<br/>
+
+## GAUSS-07101 - GAUSS-07110
+
+<br/>
+
+GAUSS-07101: "memory is temporarily unavailable while allocate CBM block array"
+
+SQLSTATE: 53000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07102: "could not force tracking cbm because cbm tracking function is not enabled!"
+
+SQLSTATE: 55000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07103: "the current valid prepared xid list or the next valid prepared list should not be NULL"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07104: "Invalid prepared list lenth: %d"
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07105: "could not read two-phase state from xlog at %X/%X, errormsg: %s"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07106: "expected two-phase state data is not present in xlog at %X/%X"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07107: "invalid twophase resource manager lock id"
+
+SQLSTATE: 29000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07108: "cannot commit prepared transaction %lu, it was already aborted"
+
+SQLSTATE: 25000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07109: "cannot abort prepared transaction %lu, it was already committed"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07110: "Can not connect to gtm when getting gxid, there is a connection error."
+
+SQLSTATE: 08000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07111 - GAUSS-07120
+
+<br/>
+
+GAUSS-07111: "GTM Mode: remote node sub xact can not get gxid directly from gtm"
+
+SQLSTATE: 25000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07112: "GTM Mode: remote node sub xact xid should be larger than parent xid."
+
+SQLSTATE: 25000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07113: "GTM-FREE-MODE: latestCompletedXid %lu larger than next alloc xid %lu."
+
+SQLSTATE: 25000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07114: "cannot have more than 2^32-2 commands in a transaction"
+
+SQLSTATE: 54000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07115: "Node %s: prepare gid is %s, and top xid is %lu, different transaction!"
+
+SQLSTATE: 25000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07116: "Failed to receive GTM commit transaction response after CN local PREPARE TRANSACTION '%s'."
+
+SQLSTATE: 08000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07117: "AbortCurrentTransaction: unexpected state %s"
+
+SQLSTATE: 25000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07118: "non-execute cn or dn: there is already a transaction in progress"
+
+SQLSTATE: 25001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07119: "AbortOutOfAnyTransaction reserving top xact abort: unexpected state %s"
+
+SQLSTATE: 25000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07120: "SUBXACT_TEST %s: Commit subtransaction %s before notice GTM failed."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07121 - GAUSS-07130
+
+<br/>
+
+GAUSS-07121: "xactWillRemoveRelFiles: unknown op code %u"
+
+SQLSTATE: DB001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07122: "the proc group is corrupted, the head is %u, the wakeidx is %u, localProc %p, proc %p, WALInsertLocks %p."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07123: "space reserved for WAL record does not match what was written"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07124: "could not find WAL buffer for %X/%X"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07125: "could not seek in log file %s to offset %u: %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07126: "could not write to log file %s at offset %u, length %lu: %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07127: "could not open file '%s' (log segment %s): %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07128: "lseek2:could not seek in log file %s to offset %u: %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07129: "could not open xlog file '%s' (log segment %s): %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07130: "could not close log file %s: %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07131 - GAUSS-07140
+
+<br/>
+
+GAUSS-07131: "could not parse xlog segment file '%s'"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07132: "recover failed could not open control file '%s': %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07133: "recover failed could not write to control file: %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07134: "recover failed could not fsync control file: %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07135: "recover failed could not close control file: %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07136: "nNumaNodes is zero."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07137: "XLOGShmemInit num_xloginsert_locks should be multiple of NUMA node number in the system."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07138: "XLOGShmemInit could not alloc memory on node %d"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07139: "cann't read a random number from file '/dev/urandom'."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07140: "could not open file '%s'"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07141 - GAUSS-07150
+
+<br/>
+
+GAUSS-07141: "lseek file error '%s' "
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07142: "could not write file '%s' "
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07143: "could not fsync file '%s' "
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07144: "could not close file '%s' "
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07145: "hot standby is not possible because wal_level was not set to 'hot_standby' or higher on the master server"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07146: "old version XLog must be shutdown checkpoint or online checkpoint."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07147: "redo can not support old version!!!!"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07148: "there are some received xlog have not been redo the tail of last redo lsn:%X/%X, received lsn:%X/%X"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07149: "curMinRecLSN little prev checkpoint lsn is %08X/%08X,now lsn is %08X/%08X"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07150: "current dirty page list head recLSN %08X/%08X smaller than redo lsn %08X/%08X"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07151 - GAUSS-07160
+
+<br/>
+
+GAUSS-07151: "unexpected XLogReadBufferForRedo result when restoring backup block"
+
+SQLSTATE: 20000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07152: "could not fsync log segment %s: %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07153: "could not fsync log file %s: %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07154: "could not fsync write-through log file %s: %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07155: "could not fdatasync log file %s: %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07156: "failed to stat %s file:%m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07157: "must be system admin or replication role or operator admin in operation mode to run a backup"
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07158: "file size is wrong, '%s': %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07159: "the file is not exist '%s': %m"
+
+SQLSTATE: 55000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07160: "failed to touch %s file during enable xlog delay: %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07161 - GAUSS-07170
+
+<br/>
+
+GAUSS-07161: "could not remove %s file: %m. This will lead to residual of stale xlog segments"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07162: "could not open rewind file: %s"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07163: "could not enable delay ddl when enable_cbm_tracking is off!"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07164: "could not remove %s file: %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07165: "failed to write %s file during enable delay ddl recycle"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07166: " could not disable delay ddl when enable_cbm_tracking is off!"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07167: "valid input lsn is not supported while doing forceful disable delay ddl"
+
+SQLSTATE: 20000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07168: "failed to write %s file during disable delay ddl recycle"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07169: "could not remove %s file after write failure: %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07170: "Failed to get cbm information during execute delayed DDL: %s"
+
+SQLSTATE: 20000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07171 - GAUSS-07180
+
+<br/>
+
+GAUSS-07171: "could not remove %s file before unlink col relation files: %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07172: "mpfl_pwrite_file failed, MPFL_FILE_SIZE %d, offset %ld, write_size %d"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07173: "mpfl_pwrite_file: Write file error"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07174: "mpfl_pwrite_file: Write file size mismatch: expected %d, written %d"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07175: "Could not remove max_flush_lsn file"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07176: "Could not create file '%s'"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07177: "Could not open file '%s'"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07178: "maximum number of WAL record block references exceeded"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07179: "too many registered buffers"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07180: "too much WAL data"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07181 - GAUSS-07190
+
+<br/>
+
+GAUSS-07181: "no block with id %d registered with WAL insertion"
+
+SQLSTATE: 55000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07182: "invalid xlog info mask %hhx"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07183: "invalid page header in block %u, spc oid %u db oid %u relfilenode %u"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07184: "xlog record length is %u, more than XLogRecordMaxSize %u"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07185: "Must be system admin or operator admin in operation mode to control xlog delay function."
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07186: "Must be system admin or operator admin in operation mode to switch transaction log files."
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07187: "Must be system admin or operator admin in operation mode to create a restore point."
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07188: "Must be system admin or operator admin in operation mode to control recovery."
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07189: "Must be system admin or operator admin in operation mode to control ddl delay function."
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07190: "could not parse xlog location '%s'"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07191 - GAUSS-07200
+
+<br/>
+
+GAUSS-07191: "Must be system admin or operator admin in operation mode to control resume_bkp_flag function."
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07192: "could not close log file %u, segment %lu: %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07193: "[REDO_LOG_TRACE]WAL contains references to invalid pages, count:%u"
+
+SQLSTATE: DB001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07194: "can not get xlog lsn from record page block %hhu lsn %lu"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07195: "lsn check error, lsn in record (%lu) ,lsn in current page %lu, page info:%u/%u/%u block %hhu forknum %d lsn %lu blknum:%u"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07196: "failed to locate backup block with ID %d"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07197: "block with WILL_INIT flag in WAL record must be zeroed by redo routine"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07198: "block to be initialized in redo routine must be marked with WILL_INIT flag in the WAL record"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07199: "failed to restore block image"
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07200: "could not seek in log segment %s to offset %u: %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/73-GAUSS-07201-GAUSS-07300.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/73-GAUSS-07201-GAUSS-07300.md
new file mode 100644
index 0000000000000000000000000000000000000000..ac79df509039fada72156841a6904968e121d8ba
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/73-GAUSS-07201-GAUSS-07300.md
@@ -0,0 +1,868 @@
+---
+title: GAUSS-07201 - GAUSS-07300
+summary: GAUSS-07201 - GAUSS-07300
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-07201 - GAUSS-07300
+
+<br/>
+
+## GAUSS-07201 - GAUSS-07210
+
+<br/>
+
+GAUSS-07201: "could not read from log segment %s, offset %u, length %d, readbytes %d: %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07202: "Incorrect xid status %d"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07203: "CLOG STATUS ERROR: xid %lu status %s"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07204: "CLOG PAGE STATUS ERROR: xid %lu status %s"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07205: "CLOG STATUS ERROR: xid: %lu input status %s, current status %s"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07206: "clog pageno should be >= 0"
+
+SQLSTATE: 42804
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07207: "slru zero page under %s"
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07208: "slru read page under %s"
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07209: "slru write page under %s"
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07210: "could not access status of transaction %lu , nextXid is %lu "
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07211 - GAUSS-07220
+
+<br/>
+
+GAUSS-07211: "Read file error"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07212: "Read file size mismatch: expected %d, read %d"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07213: "Write file error"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07214: "Write file size mismatch: expected %d, written %d"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07215: "Seek file error"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07216: "DW extend file failed, expected_file_size %ld, offset %ld, extend_size %ld"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07217: "DW verify checksum: page checksum flag is wrong"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07218: "DW check file size failed, expected_size %ld, actual_size %ld"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07219: "File header is broken"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07220: "Could not truncate dw file during startup!"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07221 - GAUSS-07230
+
+<br/>
+
+GAUSS-07221: "DW file close failed"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07222: "Could not remove the residual DW file"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07223: "DW file does not exist"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07224: "Double write not initialized"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07225: "Double write already closed"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07226: "Memory allocation failed."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07227: "invalid forkNum %d, should be less than %d"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07228: "invalid page in block %u of relation %s, remote read data corrupted"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07229: "buffer is dirty but not in dirty page queue in InvalidateBuffer"
+
+SQLSTATE: XX010
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07230: "[exception] private ref->refcount is %d in UnpinBuffer"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07231 - GAUSS-07240
+
+<br/>
+
+GAUSS-07231: "buffer is dirty but not in dirty page queue in TerminateBufferIO_common"
+
+SQLSTATE: XX010
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07232: "TerminateBufferIO_common, dirty page queue is full when trying to push buffer to the queue"
+
+SQLSTATE: XX010
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07233: "remote not available"
+
+SQLSTATE: 58030
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07234: "remote read failed from %s, %s"
+
+SQLSTATE: 58030
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07235: "local buffer hash table corrupted."
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07236: "block %u of %s is still referenced (local %d)"
+
+SQLSTATE: XX011
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07237: "fork number should not be less than zero"
+
+SQLSTATE: 2202E
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07238: "could not initialize local buffer hash table."
+
+SQLSTATE: D0014
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07239: "shared buffer hash table corrupted."
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07240: "Found invalid error recored: negative length that is not -1."
+
+SQLSTATE: OP002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07241 - GAUSS-07250
+
+<br/>
+
+GAUSS-07241: "Found invalid error recored: length is not the same as the attribute length."
+
+SQLSTATE: OP002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07242: "LOCATION is required for the foreign tables"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07243: "if the number of gds is greater than dn , query dop should not be greater than one."
+
+SQLSTATE: HV000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07244: "invalid timestamp string length"
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07245: "Unsupport distribute type."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07246: "It is not allowed to create partition on this foreign table."
+
+SQLSTATE: HV000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07247: "Invalid URL '%s' in trimed LOCATION"
+
+SQLSTATE: HV000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07248: "out_filename_prefix should not be empty"
+
+SQLSTATE: OP0A3
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07249: "out_filename_prefix is not supposed to contain '%c'"
+
+SQLSTATE: OP0A3
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07250: "out_filename_prefix is not supposed to be '%s'"
+
+SQLSTATE: OP0A3
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07251 - GAUSS-07260
+
+<br/>
+
+GAUSS-07251: "Only alphanumeric characters and \'_\' is allowed in out_filename_prefix option"
+
+SQLSTATE: OP0A3
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07252: "out_fix_alignment is only allowed with fixed format"
+
+SQLSTATE: OP0A3
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07253: "Only 'align_left' and 'align_right' is allowed in out_fix_alignment option"
+
+SQLSTATE: OP0A3
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07254: "Do not allow to set region option when the 'gsobs' prefix is specified for the location option."
+
+SQLSTATE: HV002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07255: "OBS foreign table does not support '%s' option"
+
+SQLSTATE: OP0A3
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07256: "OBS foreign table does not support remote_log option"
+
+SQLSTATE: OP0A3
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07257: "OBS foreign table have to specify '%s' option"
+
+SQLSTATE: OP0A3
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07258: "This OBS foreign table only supports CSV/TEXT format"
+
+SQLSTATE: OP0A3
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07259: "Invalid 'encrypt' option value '%s' for OBS foreign table"
+
+SQLSTATE: OP0A3
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07260: "Invalid 'chunksize' option value '%s', only numeric value can be set"
+
+SQLSTATE: OP0A3
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07261 - GAUSS-07270
+
+<br/>
+
+GAUSS-07261: "Invalid 'chunksize' option value '%s' for OBS Read-Only table, valid range [8, 512] in MB"
+
+SQLSTATE: OP0A3
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07262: "Option 'chunksize' is not allowed in OBS write-only table"
+
+SQLSTATE: OP0A3
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07263: "None OBS foreign table does not support '%s' option"
+
+SQLSTATE: OP0A3
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07264: "Shared mode and private mode are only available for the supper user and Operatoradmin"
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07265: "Invalid key string"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07266: "obs option chunksize is too large"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07267: "No free Cache Blocks! cstore_buffers maybe too small, scanned=%d, pinned=%d, unpinned=%d, invalid=%d, looped=%d, reserved=%d, freepinned = %d, start=%d, max=%d. RequestSize = %d, CurrentSize = %ld, BufferMaxSize = %ld."
+
+SQLSTATE: 53500
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07268: "complete IO, slot(%d), flag(%d)"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07269: " palloc size to big, size(%ld)."
+
+SQLSTATE: 53200
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07270: "Unsupported data type in column storage"
+
+SQLSTATE: 42804
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07271 - GAUSS-07280
+
+<br/>
+
+GAUSS-07271: "malloc fails, out of memory: size %lu"
+
+SQLSTATE: 53200
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07272: "unsupported data type length %d of column '%s' of relation '%s' "
+
+SQLSTATE: 42804
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07273: "Cannot load CUDesc and CU for a dropped column '%s' of table '%s'"
+
+SQLSTATE: D0011
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07274: "fail to remote read CU, data corrupted in network"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07275: "Cannot to fill unsupported system column %d for column store table"
+
+SQLSTATE: 42804
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07276: "Cannot save CUDesc for a dropped column '%s' of table '%s'"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07277: "Cannot fill VecBatch for a dropped column '%s' of table '%s'"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07278: "compression unit descriptor not found, table(%s), column(%s), relfilenode(%u/%u/%u), cuid(%u))."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07279: "CU Delete bitmap is missing."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07280: "Cannot get CUData for a dropped column '%s' of table '%s'"
+
+SQLSTATE: D0011
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07281 - GAUSS-07290
+
+<br/>
+
+GAUSS-07281: "Load CU failed in adio! table(%s), column(%s), relfilenode(%u/%u/%u), cuid(%u)"
+
+SQLSTATE: 58030
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07282: "invalid CU in cu_id %u of relation %s file %s offset %lu, prefetch %s"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07283: "invalid CU in cu_id %u of relation %s file %s offset %lu, sync load %s"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07284: "There is an IO error when remote read CU in cu_id %u of relation %s file %s offset %lu. slotId %d, column '%s' "
+
+SQLSTATE: 58030
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07285: "invalid CU in cu_id %u of relation %s file %s offset %lu, remote read %s"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07286: "compression unit descriptor(talbe '%s', column '%s', cuid %u) not found"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07287: "The delta table's definition is not the same with main relation, please use pg_sync_cstore_delta to adjust it."
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07288: "This query is not supported by optimizer in CStore."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07289: "The max insert memory is too small, it may occur endless loop. The used memory is %lu, the controlled memory limit is %dKB, the partition relation is %s, the flush partition id is %d."
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07290: "Invalid partition value cache record."
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07291 - GAUSS-07300
+
+<br/>
+
+GAUSS-07291: "Relation \'%s\' virtual cudesc tuple(cuid %u) not found"
+
+SQLSTATE: 02000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07292: "failed to remotely read CU, data corrupted in network"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07293: "invalid CU in cu_id %u of relation %s file %s offset %lu"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07294: "Invalid original partition name"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07295: "cannot merge partition bacause partition %s has unusable local index"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07296: "cache lookup failed for relation: %u"
+
+SQLSTATE: 29P01
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07297: "inititalSize is too large: initialSize(%u), m_bpNullRawSize(%u)"
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07298: "the CRC32C checksum are different between SSE42 (0x%x) and SB8 (0x%x)."
+
+SQLSTATE: 42804
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07299: "Find invalid compressed buffer or invalid CU while uncompressing."
+
+SQLSTATE: 53200
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07300: "CU size error, %u in CU descriptor but %u in CU header"
+
+SQLSTATE: 53200
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/74-GAUSS-07301-GAUSS-07400.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/74-GAUSS-07301-GAUSS-07400.md
new file mode 100644
index 0000000000000000000000000000000000000000..d08ff8b0b8c4e5cc2444406870fc09a015b833f2
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/74-GAUSS-07301-GAUSS-07400.md
@@ -0,0 +1,868 @@
+---
+title: GAUSS-07301 - GAUSS-07400
+summary: GAUSS-07301 - GAUSS-07400
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-07301 - GAUSS-07400
+
+<br/>
+
+## GAUSS-07301 - GAUSS-07310
+
+<br/>
+
+GAUSS-07301: "this->m_srcDataSize is too large: %u"
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07302: "No cache found when print data cache slot leak warning: slotId:%d"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07303: "validate user defined attribute failed!"
+
+SQLSTATE: 42P24
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07304: "CU partial write, file '%s', offset(%lu), total(%d), expected(%d), actual(%d): %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07305: "could not extend file '%s', offset(%lu), total(%d), expected(%d), actual(%d): %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07306: "read file '%s' failed, %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07307: "some data are read from '%s', offset(%lu), load size(%d), expected read(%d), actual read(%d)"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07308: "could not read file '%s', offset(%lu), load size(%d), expected read(%d), actual read(%d): %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07309: "write file '%s' failed in savecu!"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07310: "write file '%s' failed in OverwriteCU!"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07311 - GAUSS-07320
+
+<br/>
+
+GAUSS-07311: "read file '%s' failed in load!"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07312: "unexpected cu file read info: offset(%lu), size(%d), readFileId(%d), readOffset(%lu), expect_read_size(%d)."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07313: "read file '%s' failed, offset(%lu), size(%d), expect_read_size(%d), acture_read_size(%d), maybe you should upgrade cstore data files first"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07314: "could not read file '%s', offset(%lu), size(%d), expect_read_size(%d), acture_read_size(%d): %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07315: "read file '%s' failed in wsload!"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07316: "invalid size(%u) in CUStorage::LoadCU"
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07317: "CUStorage::LoadCU size = 0"
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07318: "Invalid tupleSortState, tupleSlot, or sorting strategy while getting tuple in cstore psort."
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07319: "memory alloc failed"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07320: "build global OBS connect cache hash table failed"
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07321 - GAUSS-07330
+
+<br/>
+
+GAUSS-07321: "could not initialize OBS connector hash table"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07322: "dfs forign server type error. type = %d"
+
+SQLSTATE: 42P17
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07323: "wait IO find an error when allocate meta block, slotID(%d), spcID(%u),dbID(%u), relID(%u), fileID(%d), stripeOrBlocketID(%u), columnID(%u)"
+
+SQLSTATE: P0002
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07324: "could not write to temporary file: the file size exceeds the max size: %ldBYTE"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07325: "could not write to temporary file: %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07326: "could not read from temporary file: %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07327: "could not munmap() while flushing data: %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07328: "unable to open process pid directory '%s'"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07329: "out of file descriptors: %m; release and retry"
+
+SQLSTATE: 53000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07330: "io_submit() async read failed %d, dispatch count(%d)"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07331 - GAUSS-07340
+
+<br/>
+
+GAUSS-07331: "io_submit() async write failed %d, dispatch count(%d)"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07332: "FileAsyncCUClose : invalid vfd(%d), SizeVfdCache(%lu)"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07333: "io_submit() async cu read failed %d, dispatch count(%d)"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07334: "io_submit() async cu write failed %d, dispatch count(%d)"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07335: "FileAccess() extend file failed %d"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07336: "exceeded MAX_ALLOCATED_DESCS while trying to open file '%s'"
+
+SQLSTATE: 54000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07337: "Allocate dir failed."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07338: "sorry, too many reserve thread already lastreserveBackend:%d, maxreserveBackends:%d"
+
+SQLSTATE: 53300
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07339: "sorry, session index isnot valid index:%d, maxreserveBackends:%d, maxBackends:%d"
+
+SQLSTATE: 53300
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07340: "sorry, session slot isnot valid:%d, maxreserveBackends:%d, maxBackends:%d"
+
+SQLSTATE: 53300
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07341 - GAUSS-07350
+
+<br/>
+
+GAUSS-07341: "standby_redo: unknown op code %hhu"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07342: "wait transaction %lu sync time exceed %d s."
+
+SQLSTATE: YY003
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07343: "Snapshot is invalid at %s, this is a safe error if there is breakdown in gtm log"
+
+SQLSTATE: YY014
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07344: "Out of memory at palloc memory for xids!"
+
+SQLSTATE: 53200
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07345: "GTM error, could not obtain valid gtm snapshot status."
+
+SQLSTATE: 08006
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07346: "Snapshot is invalid, snaphot type %s, snapshot csn: %lu."
+
+SQLSTATE: YY014
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07347: "Snapshot is invalid, this is a safe error, snapshot too old."
+
+SQLSTATE: YY014
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07348: "GTM error, could not obtain snapshot_status, please check GTM is running or failovering."
+
+SQLSTATE: 08006
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07349: "invalid offset num:%d"
+
+SQLSTATE: 42704
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07350: "Too many visited procs."
+
+SQLSTATE: 53300
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07351 - GAUSS-07360
+
+<br/>
+
+GAUSS-07351: "no more LWLocks available"
+
+SQLSTATE: 55P03
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07352: "force thread %lu to exit because of lwlock deadlock"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07353: "queueing for lock while waiting on another one"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07354: "lock %s is not held"
+
+SQLSTATE: 55P03
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07355: "InitNuma NUMA is not available"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07356: "InitProcGlobal NUMA memory allocation in node %d failed."
+
+SQLSTATE: 53200
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07357: "Too many clients already, active/non-active: %d/%d."
+
+SQLSTATE: 53300
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07358: "InitProcess numa_run_on_node_mask failed. errno:%d "
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07359: "failed to acquire mutex lock for deleMemContextMutex."
+
+SQLSTATE: 55P03
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07360: "failed to release mutex lock for deleMemContextMutex."
+
+SQLSTATE: 55P03
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07361 - GAUSS-07370
+
+<br/>
+
+GAUSS-07361: "all &g_instance.proc_aux_base are in use"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07362: "there remain unreleased locks when process exists."
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07363: "could not disable timer for reset txn xmin in Read Committed Mode."
+
+SQLSTATE: 58000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07364: "unrecognized lock method: %hu"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07365: "Failed to allocate memory for lockOwners."
+
+SQLSTATE: 53200
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07366: "newproc should not be null"
+
+SQLSTATE: XX005
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07367: "GetRunningTransactionLocks: index = %d els = %d"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07368: "proc should not be null"
+
+SQLSTATE: XX005
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07369: "snapshot xmin:%lu is not greater than global xmin:%lu"
+
+SQLSTATE: 55000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07370: "predicate locks hash table corrupted"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07371 - GAUSS-07380
+
+<br/>
+
+GAUSS-07371: "get parent relation lock's lock tag failed"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07372: "transfer predicate lock failed"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07373: "isolation level is not serializable"
+
+SQLSTATE: 25004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07374: "corrupted page pointers: lower = %hu, upper = %hu, special = %hu"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07375: "corrupted item pointer: %d"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07376: "corrupted item lengths: total %u, available space %d"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07377: "invalid index offnum: %hu"
+
+SQLSTATE: 2201X
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07378: "incorrect index offsets supplie"
+
+SQLSTATE: 2201X
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07379: "invalid size of data for block checksum"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07380: "Can't find the oldest unidentified connection."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07381 - GAUSS-07390
+
+<br/>
+
+GAUSS-07381: "logical decoding requires wal_level >= logical"
+
+SQLSTATE: 55000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07382: "logical decoding requires a database connection"
+
+SQLSTATE: 55000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07383: "cannot perform logical decoding without a acquired slot"
+
+SQLSTATE: 55000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07384: "cannot initialize logical decoding without a specified plugin"
+
+SQLSTATE: 55000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07385: "cannot use physical replication slot created for logical decoding"
+
+SQLSTATE: 55000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07386: "replication slot '%s' was not created in this database"
+
+SQLSTATE: 55000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07387: "cannot create logical replication slot in transaction that has performed writes"
+
+SQLSTATE: 25001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07388: "cannot use physical replication slot for logical decoding"
+
+SQLSTATE: 55000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07389: "Stopped to parse any valid XLog Record at %X/%X: %s."
+
+SQLSTATE: LL001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07390: "writes are only accepted in commit, begin and change callbacks"
+
+SQLSTATE: LL001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07391 - GAUSS-07400
+
+<br/>
+
+GAUSS-07391] : "OutputPluginPrepareWrite needs to be called before OutputPluginWrite"
+
+SQLSTATE: LL001
+
+错误原因: 调用OutputPluginWrite函数前应该先调用OutputPluginPrepareWrite函数。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07392: "output plugins have to declare the _PG_output_plugin_init symbol"
+
+SQLSTATE: LL001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07393: "output plugins have to register a change callback"
+
+SQLSTATE: LL001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07394: "output plugins have to register a commit callback"
+
+SQLSTATE: LL001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07395: "unexpected rmgr_id: %u"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07396: "unexpected RM_XLOG_ID record type: %u"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07397: "unexpected RM_XACT_ID record type: %u"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07398: "unexpected RM_STANDBY_ID record type: %u"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07399: "unexpected RM_HEAP2_ID record type: %u"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07400: "unexpected RM_HEAP3_ID record type: %u"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/75-GAUSS-07401-GAUSS-07480.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/75-GAUSS-07401-GAUSS-07480.md
new file mode 100644
index 0000000000000000000000000000000000000000..08e1b319d54b8b075303ac2b405c8f1463d26c20
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/75-GAUSS-07401-GAUSS-07480.md
@@ -0,0 +1,632 @@
+---
+title: GAUSS-07401 - GAUSS-07480
+summary: GAUSS-07401 - GAUSS-07480
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-07401 - GAUSS-07480
+
+<br/>
+
+## GAUSS-07401 - GAUSS-07410
+
+<br/>
+
+GAUSS-07401: "unexpected RM_HEAP_ID record type: %u"
+
+SQLSTATE: XX004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07402: "cannot free a copied snapshot"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07403: "cannot free an active snapshot"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07404: "cannot export a snapshot before reaching a consistent state"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07405: "cannot export a snapshot, not all transactions are monitored anymore"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07406: "cannot export a snapshot when MyPgXact->xmin already is valid"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07407: "cannot export a snapshot from within a transaction"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07408: "can only export one snapshot at a time"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07409: "clearing exported snapshot in wrong transaction state"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07410: "xl_heap_new_cid record without a valid CommandId"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07411 - GAUSS-07420
+
+<br/>
+
+GAUSS-07411: "waiting for ourselves"
+
+SQLSTATE: LL001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07412: "snapbuild state file '%s' has wrong magic %u instead of %d"
+
+SQLSTATE: LL001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07413: "snapbuild state file '%s' has unsupported version %u instead of %d"
+
+SQLSTATE: LL001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07414: "could not read file '%s', read %lu of %lu: %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07415: "could not read file '%s', size overflow"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07416: "snapbuild state file %s: checksum mismatch, is %u, should be %u"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07417: "too much output for sql interface"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07418: "must be superuser or replication role to use replication slots"
+
+SQLSTATE: 42501
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07419: "could not read from log segment %s, offset %u, length %lu: %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07420: "couldn't advance in recovery"
+
+SQLSTATE: 22P02
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07421 - GAUSS-07430
+
+<br/>
+
+GAUSS-07421: "invalid input syntax for type lsn: '%s' of start_lsn"
+
+SQLSTATE: 22P02
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07422: "array must be one-dimensional"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07423: "array must not contain nulls"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07424: "array must be TEXTOID"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07425: "array must have even number of elements"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07426: "could not remove directory '%s'"
+
+SQLSTATE: LL001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07427: "tuplecid value in changequeue"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07428: "output plugin used xid %lu"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07429: "can not found txn which xid = %lu"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07430: "only ever add one set of invalidations"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07431 - GAUSS-07440
+
+<br/>
+
+GAUSS-07431: "txn->subtxns is illegal point"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07432: "could not write to xid %lu's data file: %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07433: "could not read from reorderbuffer spill file: %m"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07434: "incomplete read from reorderbuffer spill file: read %d instead of %u"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07435: "illegality read length %lu"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07436: "could not read from reorderbuffer spill file: read %d instead of %u"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07437: "got sequence entry %u for toast chunk %u instead of seq 0"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07438: "got sequence entry %u for toast chunk %u instead of seq %d"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07439: "fail to get toast chunk"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07440: "unexpected type of toast chunk"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07441 - GAUSS-07450
+
+<br/>
+
+GAUSS-07441: "toast_rel should not be NULL!"
+
+SQLSTATE: LL001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07442: "could not read file '%s', read %d instead of %d"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07443: "could not parse fname %s"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07444: "yyscanner init failed: %m"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07445: "we should be a writer when enable_mix_replication is on"
+
+SQLSTATE: 42P08
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07446: "Insert BCM Info to be interrupted."
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07447: "The got BCM Array index is corrupt: index1 %u index2 %u array_index %u BCMElementArrayOffset1 %X/%X BCMElementArrayOffset2 %X/%X"
+
+SQLSTATE: XX001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07448: "Invalid relation while clearing BCM status: rnode[%u,%u,%u], blocknum[%u], pageoffset[%lu], size[%u], attid[%d]"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07449: "buffer should be valid, but now is %d"
+
+SQLSTATE: 22000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07450: "heap sync hash table not cleaned, num of entries:%ld"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07451 - GAUSS-07460
+
+<br/>
+
+GAUSS-07451: "enable_cbm_tracking must be turn on when enable_mix_replication is on!"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07452: "can't decode in pmState is not run or recovery in progress."
+
+SQLSTATE: LL001
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07453: "cannot use a logical replication slot for physical replication"
+
+SQLSTATE: 55000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07454: "Failed to init the xlog reader for the wal sender."
+
+SQLSTATE: 29000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07455: "walsender stop switchover process for catchup is alive, the process need to be restart"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07456: "terminating Walsender process due to replication timeout.now time(%s) timeout time(%s) last recv time(%s) heartbeat time(%s)"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07457: "syncrep_scanner_yylex_init() failed: %m"
+
+SQLSTATE: 42601
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07458: "invalid replication node index:%d"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07459: "Refuse WAL streaming, connection mode is %d, connertion IP is %s:%d"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07460: "terminating walreceiver due to timeout now time(%s) timeout time(%s) last recv time(%s) heartbeat time(%s)"
+
+SQLSTATE: YY004
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07461 - GAUSS-07470
+
+<br/>
+
+GAUSS-07461: "WAL streaming isn't employed to sync all the replication data log."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07462: "the corrupt data total len is %u bytes, the expected len is %lu bytes."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07463: "the unexpected data flag is %X, the expected data flag is 'd'."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07464: "the start xlog employed for the wal data is invalid."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07465: "the end xlog employed for the wal data is invalid."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07466: "the received wal data is unexpected %u bytes at least more than %lu bytes"
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07467: "the received xlog is unexpected %u bytes at least more than %lu bytes."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07468: "fail to push some wal data to the wal streaming writer queue: unexpected wal data flag %c."
+
+SQLSTATE: 22023
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07469: "Unexpected seek in the walreceiver buffer. xlogrecptr is (%X:%X) but local xlogptr is (%X:%X)."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07470: "corrupt wal data write len %u bytes, the expected write data_size %u"
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-07471 - GAUSS-07480
+
+<br/>
+
+GAUSS-07471: "The Row Store Heap Log SHOULD NOT BE synchronized in the WAL Streaming. Tracking the data header info: rnode[%u/%u/%u] blocknum[%u] pageoffset[%lu] size[%u] queueoffset[%u/%u]."
+
+SQLSTATE: 0A000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-07472: "Failed to write the wal data: the database path %s doesn't exist."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/76-GAUSS-50000-GAUSS-50999.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/76-GAUSS-50000-GAUSS-50999.md
new file mode 100644
index 0000000000000000000000000000000000000000..900ce99b2dd85dec6bbd1cbcf9740ecfd1071f58
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/76-GAUSS-50000-GAUSS-50999.md
@@ -0,0 +1,1100 @@
+---
+title: GAUSS-50000 - GAUSS-50999
+summary: GAUSS-50000 - GAUSS-50999
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-50000 - GAUSS-50999
+
+<br/>
+
+## GAUSS-50000 - GAUSS-50099
+
+<br/>
+
+GAUSS-50000: "Unrecognized parameter: %s."
+
+SQLSTATE: 无
+
+错误原因: 参数无法识别。
+
+解决办法: 检查报错信息中所涉及的参数，如果不是所执行脚本需要指定的参数就会报这个错。
+
+GAUSS-50001: "Incorrect parameter. Parameter '-%s' is required"
+
+SQLSTATE: 无
+
+错误原因: 缺少必须参数。
+
+解决办法: 检查报错信息中所涉及的参数，如果执行脚本必须要求指定该参数而用户未指定就会报这个错。
+
+GAUSS-50002: "Incorrect parameter. Parameter '-%s' is not required"
+
+SQLSTATE: 无
+
+错误原因: 多余的参数。
+
+解决办法: 检查报错信息中所涉及的参数，如果执行脚本不需要指定该参数而用户指定了就会报这个错。
+
+GAUSS-50003: "The parameter '-%s' type should be %s."
+
+SQLSTATE: 无
+
+错误原因: 参数类型错误。
+
+解决办法: 检查报错信息中所涉及的参数的类型，必须为指定的类型。
+
+GAUSS-50004: "The parameter '-%s' value is incorrect."
+
+SQLSTATE: 无
+
+错误原因: 参数值错误。
+
+解决办法: 检查报错信息中所涉及的参数的值，必须符合规范。
+
+GAUSS-50005: "The parameter '-%s' and '-%s' can not be used together."
+
+SQLSTATE: 无
+
+错误原因: 参数A和参数B不能同时被指定。
+
+解决办法: 检查报错信息中所涉及的两个参数以及要执行的场景，只允许指定其中一个。
+
+GAUSS-50006: "Too many command-line arguments (first is \\"%s\\")."
+
+SQLSTATE: 无
+
+错误原因: 指定参数的个数超过规定数量。
+
+解决办法: 检查报错信息中所涉及的参数个数是否满足要求。
+
+GAUSS-50007: "Failed to set %s parameter."
+
+SQLSTATE: 无
+
+错误原因: 设置GUC参数失败。
+
+解决办法: 检查gs_guc工具中参数设置是否满足工具要求。
+
+GAUSS-50008: "Failed to reload parameter."
+
+SQLSTATE: 无
+
+错误原因: 加载参数失败。
+
+解决办法: 检查加载参数的命令是否正确。
+
+GAUSS-50009: "Parameter format error."
+
+SQLSTATE: 无
+
+错误原因: 参数格式错误。
+
+解决办法: 检查命令中参数格式是否正确。
+
+GAUSS-50010: "Failed to check %s parameter."
+
+SQLSTATE: 无
+
+错误原因: 检查内核参数失败。
+
+解决办法: 检查内核参数shared_buffers或者max_connections值是否正确。
+
+GAUSS-50011: "The parameter[%s] value[%s] is invalid."
+
+SQLSTATE: 无
+
+错误原因: 参数有效值错误
+
+解决办法: 输入正确参数
+
+GAUSS-50012: "The parameter '%s' value can't be empty."
+
+SQLSTATE: 无
+
+错误原因: 该参数不能为空。
+
+解决办法: 检查该参数是否为空。
+
+GAUSS-50013: "The parameter '%s' have not been initialized."
+
+SQLSTATE: 无
+
+错误原因: 参数未初始化就被使用。
+
+解决办法: 检查代码逻辑，需要首先初始化指定参数。
+
+GAUSS-50014: "Parameters of '%s' can not be empty."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-50015: "The command line parser error: %s."
+
+SQLSTATE: 无
+
+错误原因: 命令行解析器执行错误。
+
+解决办法: 命令行解析器解析系统命令行失败，根据错误指示修正命令行输入参数。
+
+GAUSS-50016: "The re-entrant parameter '-%s' is not same with the previous command."
+
+SQLSTATE: 无
+
+错误原因: 操作重入后，命令参数改变，无法执行重入操作。
+
+解决办法: 重入时输入与上次失败操作相同的参数或执行手动回滚操作后再执行新的操作。
+
+GAUSS-50017: "Incorrect value '%s' specified by the parameter '-%s'."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-50018: "The·nodename·%s·upgrade·failed,·please·warm-standby·at·first·for·this·node."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-50100 - GAUSS-50199
+
+<br/>
+
+GAUSS-50100: "The %s is not readable for %s."
+
+SQLSTATE: 无
+
+错误原因: 文件对某用户而言没有读权限。
+
+解决办法: 检查用户是否正确或给用户赋予符合条件的读权限。
+
+GAUSS-50101: "The %s is not executable for %s."
+
+SQLSTATE: 无
+
+错误原因: 文件对某用户而言没有执行权限。
+
+解决办法: 检查用户是否正确或给用户赋予符合条件的执行权限。
+
+GAUSS-50102: "The %s is not writable for %s."
+
+SQLSTATE: 无
+
+错误原因: 文件对某用户而言没有写权限。
+
+解决办法: 检查用户是否正确或给用户赋予符合条件的写权限。
+
+GAUSS-50103: "The %s has unexpected rights."
+
+SQLSTATE: 无
+
+错误原因: 权限越界。
+
+解决办法: 给用户赋予符合条件的相应权限。
+
+GAUSS-50104: "Only a user with the root permission can run this script."
+
+SQLSTATE: 无
+
+错误原因: 只有root权限的用户才能执行该脚本。
+
+解决办法: 切换到有root权限的用户来执行该脚本。
+
+GAUSS-50105: "Cannot run this script as a user with the root permission."
+
+SQLSTATE: 无
+
+错误原因: 不能以root权限的用户来执行该脚本。
+
+解决办法: 切换到非root权限的其他用户来执行该脚本。
+
+GAUSS-50106: "Failed to change the owner of %s."
+
+SQLSTATE: 无
+
+错误原因: 更改文件/目录的属主失败。
+
+解决办法: 检查赋予文件/目录的用户/组是否正确。
+
+GAUSS-50107: "Failed to change the permission of %s."
+
+SQLSTATE: 无
+
+错误原因: 修改文件/目录的权限失败。
+
+解决办法: 检查修改文件/目录的用户是否为root用户或者赋予文件/目录的权限值是否正确。
+
+GAUSS-50108: "Failed to change the owner and permission of %s."
+
+SQLSTATE: 无
+
+错误原因: 修改文件/目录的属主和权限失败。
+
+解决办法: 检查文件/目录的属主是否存在，赋予文件/目录权限的用户或者权限值是否正确。
+
+GAUSS-50109: "Only a user with the root permission can check SSD information."
+
+SQLSTATE: 无
+
+错误原因: 仅root权限的用户才能检查SSD信息。
+
+解决办法: 检查当前用户是否具有root权限。
+
+GAUSS-50110: "Cannot execute this script on %s."
+
+SQLSTATE: 无
+
+错误原因: 不能在某个节点上执行该脚本。
+
+解决办法: 不能在执行温备或者节点替换操作的节点上执行gs_replace脚本。
+
+<br/>
+
+## GAUSS-50200 - GAUSS-50299
+
+<br/>
+
+GAUSS-50200: "The %s already exists."
+
+SQLSTATE: 无
+
+错误原因: 文件/目录已经存在。
+
+解决办法: 删除该文件/目录。
+
+GAUSS-50201: "The %s does not exist."
+
+SQLSTATE: 无
+
+错误原因: 文件/目录不存在。
+
+解决办法: 检查/目录文件不存在的原因，创建目录/文件或执行能够创建该文件/目录的脚本。
+
+GAUSS-50202: "The %s must be empty."
+
+SQLSTATE: 无
+
+错误原因: 目录不为空。
+
+解决办法: 检查目录，备份后使其为空。
+
+GAUSS-50203: "The %s cannot be empty."
+
+SQLSTATE: 无
+
+错误原因: 目录/文件不能为空。
+
+解决办法: 检查目录/文件为空的原因，然后创建目录/文件或执行能够创建该目录的脚本。
+
+GAUSS-50204: "Failed to read %s."
+
+SQLSTATE: 无
+
+错误原因: 读文件失败。
+
+解决办法: 检查并修改文件和用户的权限。
+
+GAUSS-50205: "Failed to write %s."
+
+SQLSTATE: 无
+
+错误原因: 写文件失败。
+
+解决办法: 检查并修改文件和用户的权限。
+
+GAUSS-50206: "Failed to create %s."
+
+SQLSTATE: 无
+
+错误原因: 创建文件失败。
+
+解决办法: 检查并修改用户在该文件路径目录下的权限。
+
+GAUSS-50207: "Failed to delete %s."
+
+SQLSTATE: 无
+
+错误原因: 删除文件失败。
+
+解决办法: 检查并修改用户在该文件路径目录下的权限。
+
+GAUSS-50208: "Failed to create the %s directory."
+
+SQLSTATE: 无
+
+错误原因: 创建文件夹失败。
+
+解决办法: 检查并修改用户在该目录下的权限。
+
+GAUSS-50209: "Failed to delete the %s directory."
+
+SQLSTATE: 无
+
+错误原因: 删除文件夹失败。
+
+解决办法: 检查并修改用户在该目录下的权限。
+
+GAUSS-50210: "The %s must be a file."
+
+SQLSTATE: 无
+
+错误原因: 不是文件类型。
+
+解决办法: 检查并修改类型，必须是文件类型。
+
+GAUSS-50211: "The %s must be a directory."
+
+SQLSTATE: 无
+
+错误原因: 不是目录类型。
+
+解决办法: 检查并修改类型，必须是目录类型。
+
+GAUSS-50212: "The suffix of the file '%s' should be '%s'."
+
+SQLSTATE: 无
+
+错误原因: 文件的后缀不是指定的类型。
+
+解决办法: 更改文件的后缀为指定的类型。
+
+GAUSS-50213: "The %s path must be an absolute path."
+
+SQLSTATE: 无
+
+错误原因: 路径不是绝对路径。
+
+解决办法: 更改路径值为绝对路径。
+
+GAUSS-50214: "Failed to copy %s."
+
+SQLSTATE: 无
+
+错误原因: 拷贝文件失败。
+
+解决办法: 检查待拷贝的文件是否存在，目的路径是否存在，网络是否正常。
+
+GAUSS-50215: "Failed to back up %s."
+
+SQLSTATE: 无
+
+错误原因: 备份文件/目录失败。
+
+解决办法: 检查待备份的文件/目录是否存在。
+
+GAUSS-50216: "Failed to remote copy %s."
+
+SQLSTATE: 无
+
+错误原因: 远程拷贝文件/目录失败。
+
+解决办法: 检查待拷贝的文件/目录是否存在，目的路径是否存在。
+
+GAUSS-50217: "Failed to decompress %s."
+
+SQLSTATE: 无
+
+错误原因: 解压包失败。
+
+解决办法: 检查待解压的压缩包是否存在，格式是否正确，有无损坏。
+
+GAUSS-50218: "Failed to rename %s."
+
+SQLSTATE: 无
+
+错误原因: 重命名文件失败。
+
+解决办法: 检查待命名的文件是否存在，重命名后的文件名和后缀是否正确。
+
+GAUSS-50219: "Failed to obtain %s."
+
+SQLSTATE: 无
+
+错误原因: 获取目录/文件/路径失败。
+
+解决办法: 检查目录/文件/路径是否存在。
+
+GAUSS-50220: "Failed to restore %s."
+
+SQLSTATE: 无
+
+错误原因: 恢复目录/文件/路径失败。
+
+解决办法: 检查目录/文件/路径是否存在。
+
+GAUSS-50221: "Failed to obtain file type."
+
+SQLSTATE: 无
+
+错误原因: 获取文件类型失败。
+
+解决办法: 1.检查命令是否正确；2.检查指定文件/路径是否存在。
+
+GAUSS-50222: "The content of file %s is not correct."
+
+SQLSTATE: 无
+
+错误原因: 文件内容不正确。
+
+解决办法: 检查文件内容是否正确。
+
+GAUSS-50223: "Failed to update %s files."
+
+SQLSTATE: 无
+
+错误原因: 更新(写)文件失败。
+
+解决办法: 检查需要更新(写)的文件是否存在，写入文件的内容是否正确。
+
+GAUSS-50224: "The file name is incorrect."
+
+SQLSTATE: 无
+
+错误原因: 文件名错误。
+
+解决办法: 检查文件是否有多个后缀名(即文件名中有多个".")。
+
+GAUSS-50225: "Failed to back up remotely."
+
+SQLSTATE: 无
+
+错误原因: 远程备份失败。
+
+解决办法: 检查待备份的文件/目录是否存在，远程目的路径是否存在。
+
+GAUSS-50226: "Failed to restore remotely."
+
+SQLSTATE: 无
+
+错误原因: 远程恢复失败。
+
+解决办法: 检查执行的restore命令是否正确。
+
+GAUSS-50227: "Failed to compress %s."
+
+SQLSTATE: 无
+
+错误原因: 压缩文件/目录失败。
+
+解决办法: 检查待压缩的文件/目录是否存在，目的路径是否存在。
+
+GAUSS-50228: "The %s does not exist or is empty."
+
+SQLSTATE: 无
+
+错误原因: 文件/目录不存在或者为空。
+
+解决办法: 检查文件/目录是否存在或者为空。
+
+GAUSS-50229: "Cannot specify the file [%s] to the cluster path %s."
+
+SQLSTATE: 无
+
+错误原因: 不能指定文件放到集群的某个路径下。
+
+解决办法: 更换将文件存放的指定路径。
+
+GAUSS-50230: "Failed to read/write %s."
+
+SQLSTATE: 无
+
+错误原因: 读/写文件失败。
+
+解决办法: 检查文件是存在，文件是否有读/写的权限。
+
+GAUSS-50231: "Failed to generate %s file."
+
+SQLSTATE: 无
+
+错误原因: 生成文件失败
+
+解决办法: 检查生成文件失败的原因，重新生成文件
+
+GAUSS-50232: "The instance directory [%s] cannot set in app directory [%s].Please check the xml."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-50233: "The directory name %s and %s cannot be same."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-50234: "Cannot execute the script in the relevant path of the database."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-50300 - GAUSS-50399
+
+<br/>
+
+GAUSS-50300: "User %s does not exist."
+
+SQLSTATE: 无
+
+错误原因: 用户不存在。
+
+解决办法: 检查用户不存在的原因，创建用户。
+
+GAUSS-50301: "The cluster user/group cannot be a root user/group."
+
+SQLSTATE: 无
+
+错误原因: 集群用户的用户/组不能是root用户/组。
+
+解决办法: 更改集群用户的用户/组。
+
+GAUSS-50302: "The cluster user cannot be a user with the root permission."
+
+SQLSTATE: 无
+
+错误原因: 集群用户不能拥有root权限。
+
+解决办法: 更改集群用户的权限或切换没有root权限的其他集群用户。
+
+GAUSS-50303: "Cannot install the program as a user with the root permission."
+
+SQLSTATE: 无
+
+错误原因: 不能用root权限的用户来安装该程序。
+
+解决办法: 更改该用户的权限或切换到没有root权限的其他用户。
+
+GAUSS-50304: "The new user [%s] is not the same as the old user [%s]."
+
+SQLSTATE: 无
+
+错误原因: 新旧用户不匹配。
+
+解决办法: 更改用户，使之与旧用户匹配。
+
+GAUSS-50305: "The user is not matched with the user group."
+
+SQLSTATE: 无
+
+错误原因: 用户和用户组不匹配。
+
+解决办法: 检查修改用户和用户组，使之相匹配。
+
+GAUSS-50306: "The password of %s is incorrect."
+
+SQLSTATE: 无
+
+错误原因: 密码错误。
+
+解决办法: 检查并修改为使用正确的密码。
+
+GAUSS-50307: "User password has expired."
+
+SQLSTATE: 无
+
+错误原因: 用户密码过期。
+
+解决办法: 请检查并修改密码。
+
+GAUSS-50308: "Failed to obtain user information."
+
+SQLSTATE:无
+
+错误原因: 获取用户信息失败。
+
+解决办法: 检查用户信息是否正确。
+
+GAUSS-50309: "Failed to obtain password change times of data base super user"
+
+SQLSTATE:无
+
+错误原因: 获得数据库初始用户修改密码次数失败。
+
+解决办法: 检查是否修改过初始用户的密码，如果没有，请修改密码。
+
+GAUSS-50310: "Failed to obtain password expiring days."
+
+SQLSTATE:无
+
+错误原因: 获取密码超时日期失败。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-50311: "Failed to change password for %s."
+
+SQLSTATE:无
+
+错误原因: 为用户更改密码失败。
+
+解决办法: 检查/temp/temp.[user]文件是否有读权限，文件内容是否正确。
+
+GAUSS-50312: "There are other users in the group %s on %s, skip to delete group."
+
+SQLSTATE:无
+
+错误原因: 删除组失败，因为该组中还有其他用户。
+
+解决办法: 先删除组中的其他用户，然后删除组。
+
+GAUSS-50313: "Failed to delete %s group."
+
+SQLSTATE:无
+
+错误原因: 删除组失败。
+
+解决办法: 1.检查要删除组是否存在；2.检查集群状态是否正常。
+
+GAUSS-50314: "Failed to delete %s user."
+
+SQLSTATE:无
+
+错误原因: 删除用户失败。
+
+解决办法: 检查待删除的用户是否存在。
+
+GAUSS-50315: "The user %s is not matched with the owner of %s."
+
+SQLSTATE:无
+
+错误原因: 用户与路径的属主不匹配。
+
+解决办法: 修改路径的属主。
+
+GAUSS-50316: "Group [%s] does not exist."
+
+SQLSTATE:无
+
+错误原因: 组不存在。
+
+解决办法: 重新执行前置脚本，修改-G参数。
+
+GAUSS-50317: "Failed to check user and password."
+
+SQLSTATE:无
+
+错误原因: 检查用户和密码失败。
+
+解决办法: 检查集群中各节点的用户和密码是否正确。
+
+GAUSS-50318: "Failed to add %s user."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-50319: "Failed to add %s group."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-50320: "Failed to set '%s' to '%s' in /etc/ssh/sshd_config."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-50321: "Failed to get configuration of '%s' from /etc/ssh/sshd_config."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-50400 - GAUSS-50499
+
+<br/>
+
+GAUSS-50400: "The remaining space of device [%s] cannot be less than %s."
+
+SQLSTATE: 无
+
+错误原因: 磁盘空间不能少于指定值。
+
+解决办法: 清理磁盘空间、扩大磁盘容量或更换磁盘。
+
+GAUSS-50401: "The usage of the device [%s] space cannot be greater than %s."
+
+SQLSTATE: 无
+
+错误原因: 磁盘的使用率不能大于指定值。
+
+解决办法: 清理磁盘空间、扩大磁盘容量或更换磁盘。
+
+GAUSS-50402: "The usage of INODE cannot be greater than %s."
+
+SQLSTATE: 无
+
+错误原因: INODE的使用率不能超过指定值。
+
+解决办法: 检查确保INODE的使用率不要超过指定值。
+
+GAUSS-50403: "The IO scheduling policy is incorrect."
+
+SQLSTATE: 无
+
+错误原因: IO调度策略异常。
+
+解决办法: 使用gs_checkos对其进行设置。具体的设置请参考gs_checkos工具的使用。
+
+GAUSS-50404: "The XFS mount type must be %s."
+
+SQLSTATE: 无
+
+错误原因: XFS挂载类型必须是指定类型。
+
+解决办法: 更改XFS的挂载类型为指定的类型。
+
+GAUSS-50405: "The pre-read block size must be 16384."
+
+SQLSTATE: 无
+
+错误原因: 预读块大小必须是16384。
+
+解决办法: 使用gs_checkos对其进行设置。具体的设置请参考gs_checkos工具的使用。
+
+GAUSS-50406: "Failed to obtain disk read and write rates."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-50407: "Failed to clean shared semaphore."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-50408: "Failed to obtain disk read-ahead memory block."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-50409: "The remaining space of dns cannot support shrink."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-50410: "Failed to check if remaining space of dns support shrink."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-50411: "The remaining space cannot be less than %s."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-50500 - GAUSS-50599
+
+<br/>
+
+GAUSS-50500: "The SWAP partition is smaller than the actual memory."
+
+SQLSTATE: 无
+
+错误原因: swap分区小于实际内存。
+
+解决办法: 调整设置swap分区的大小，修改其值使其大于实际内存。
+
+GAUSS-50501: "Shared_buffers must be less than shmmax. Please check it."
+
+SQLSTATE: 无
+
+错误原因: Shared_buffers值必须小于shmmax值。
+
+解决办法: 集群中所有节点在文件/etc/sysctl.conf中调整设置shmmax值的大小，使其大于shmall的值，然后执行/sbin/sysctl -p命令，让修改后的参数生效，重新执行命令。
+
+GAUSS-50502: "Failed to obtain %s information."
+
+SQLSTATE: 无
+
+错误原因: 获取swap分区或者内存信息失败。
+
+解决办法: 检查系统是否正常。
+
+<br/>
+
+## GAUSS-50600 - GAUSS-50699
+
+<br/>
+
+GAUSS-50600: "The IP address cannot be pinged, which is caused by network faults."
+
+SQLSTATE: 无
+
+错误原因: IP ping不通。
+
+解决办法: 检查并设置网络，使其相互能够ping通。
+
+GAUSS-50601: "The port [%s] is occupied."
+
+SQLSTATE: 无
+
+错误原因: 端口被占用。
+
+解决办法: 1.检查占用端口号的资源是否有用，若闲置则释放端口号；2.指定其它端口号。
+
+GAUSS-50602: "Failed to bind network adapters."
+
+SQLSTATE: 无
+
+错误原因: 网卡绑定错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-50603: "The IP address is invalid."
+
+SQLSTATE: 无
+
+错误原因: IP 无效。
+
+解决办法: 检查并修改为正确的IP。
+
+GAUSS-50604: "Failed to obtain network interface card of backIp(%s)."
+
+SQLSTATE: 无
+
+错误原因: 获取网卡失败。
+
+解决办法: 1.检查网络是否正常；2.检查网卡是否正常。
+
+GAUSS-50605: "Failed to obtain back IP subnet mask."
+
+SQLSTATE: 无
+
+错误原因: 获取子网掩码失败。
+
+解决办法: 检查网络是否正常。
+
+GAUSS-50606: "Back IP(s) do not have the same subnet mask."
+
+SQLSTATE: 无
+
+错误原因: BackIP不能有相同的子网掩码。
+
+解决办法: 给BackIP设置一个子网掩码。
+
+GAUSS-50607:"Failed to obtain configuring virtual IP line number position of network startup file."
+
+SQLSTATE: 无
+
+错误原因: 网卡启动文件中获取虚拟IP是失败
+
+解决办法: 用户手动检查网卡配置文件，查看是否被破坏
+
+GAUSS-50608:"Failed to writing virtual IP setting cmds into init file."
+
+SQLSTATE: 无
+
+错误原因: 在初始化文件中写虚拟IP设置命令失败
+
+解决办法: 用户手动检查网卡配置文件，查看是否被破坏
+
+GAUSS-50609:"Failed to check port: %s."
+
+SQLSTATE: 无
+
+错误原因: 检查端口失败
+
+解决办法: 检查端口是否启用，是否被占用
+
+GAUSS-50610:"Failed to get the range of random port."
+
+SQLSTATE: 无
+
+错误原因: 获取端口范围失败
+
+解决办法: 查看端口失败的原因，重新获取
+
+GAUSS-50611: "Failed to obtain network card bonding information."
+
+SQLSTATE: 无
+
+错误原因: 获取网卡绑定信息失败。
+
+解决办法: 检查文件/proc/net/bonding/[网卡编号]是否存在，文件中是否有"BONDING_OPTS"(redhat环境)或者"BONDING_MODULE_OPTS"(centOS环境)字符串。
+
+GAUSS-50612: "Failed to obtain network card %s value."
+
+SQLSTATE: 无
+
+错误原因: 获取网卡RTU/RX的值失败。
+
+解决办法: 检查网络是否正常，网卡是否正常。
+
+GAUSS-50613: "Failed to set network card %s value."
+
+SQLSTATE: 无
+
+错误原因: 设置网卡信息失败。
+
+解决办法: 检查网络是否正常，网卡是否正常。
+
+GAUSS-50614: "Failed to check network information."
+
+SQLSTATE: 无
+
+错误原因: 检查网卡信息失败
+
+解决办法: 查看ifconfig是否可用，可用状态下重新查询。
+
+GAUSS-50615:"IP %s and IP %s are not in the same network segment."
+
+SQLSTATE: 无
+
+错误原因: 两个IP的网段不一致
+
+解决办法: 将两个IP的网段配在相同网段，重新执行。
+
+GAUSS-50616:"Failed to get network interface."
+
+SQLSTATE: 无
+
+错误原因: 获取网络接口失败
+
+解决办法: 确保IP存在，ifconfig可用，网卡配置文件中有IP信息，重新执行。
+
+GAUSS-50617: "The node of XML configure file has the same virtual IP."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-50700 - GAUSS-50799
+
+<br/>
+
+GAUSS-50700: "The firewall should be disabled."
+
+SQLSTATE: 无
+
+错误原因: 防火墙没有关闭。
+
+解决办法: 关闭防火墙。
+
+GAUSS-50701: "The firewall should be opened."
+
+SQLSTATE: 无
+
+错误原因: 防火墙没有开启。
+
+解决办法: 开启防火墙。
+
+<br/>
+
+## GAUSS-50800 - GAUSS-50899
+
+<br/>
+
+GAUSS-50800: "Regular tasks are not started."
+
+SQLSTATE: 无
+
+错误原因: 定时任务未启动。
+
+解决办法: 启动定时任务。
+
+GAUSS-50801: "Failed to set up tasks."
+
+SQLSTATE: 无
+
+错误原因: 设置任务失败
+
+解决办法: 重新执行
+
+GAUSS-50802: "Failed to %s·service."
+
+SQLSTATE: 无
+
+错误原因: 重启定时任务服务失败。
+
+解决办法: 查看日志，查找出错误详细信息。
+
+GAUSS-50803: "Failed to check user cron."
+
+SQLSTATE: 无
+
+错误原因: 检查定时任务失败。
+
+解决办法: 检查集群状态是否正常，/bin/om_monitor/[cron]文件是否存在。
+
+<br/>
+
+## GAUSS-50900 - GAUSS-50999
+
+<br/>
+
+GAUSS-50900: "The NTPD service is not installed."
+
+SQLSTATE: 无
+
+错误原因: 时钟服务未安装。
+
+解决办法: 安装时钟服务。
+
+GAUSS-50901: "The NTPD service is not started."
+
+SQLSTATE: 无
+
+错误原因: 时钟服务未启动。
+
+解决办法: 启动时钟服务。
+
+GAUSS-50902: "The system time is different."
+
+SQLSTATE: 无
+
+错误原因: 系统时间不一致。
+
+解决办法: 更改系统时间使其保持一致。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/77-GAUSS-51000-GAUSS-51999.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/77-GAUSS-51000-GAUSS-51999.md
new file mode 100644
index 0000000000000000000000000000000000000000..5026e9f9da22964e4215dfb619bb19c2797df0d6
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/77-GAUSS-51000-GAUSS-51999.md
@@ -0,0 +1,1252 @@
+---
+title: GAUSS-51000 - GAUSS-51999
+summary: GAUSS-51000 - GAUSS-51999
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-51000 - GAUSS-51999
+
+<br/>
+
+## GAUSS-51000 - GAUSS-51099
+
+<br/>
+
+GAUSS-51000: "THP services must be shut down."
+
+SQLSTATE: 无
+
+错误原因: THP服务没有关闭。
+
+解决办法: 关闭THP服务。
+
+GAUSS-51001: "Failed to obtain THP service."
+
+SQLSTATE: 无
+
+错误原因: 获取THP服务信息失败。
+
+解决办法: 检查THP文件是否存在。
+
+GAUSS-51002: "Failed to close THP service."
+
+SQLSTATE: 无
+
+错误原因: 关闭THP服务失败。
+
+解决办法: 检查THP文件是否存在。
+
+<br/>
+
+## GAUSS-51100 - GAUSS-51199
+
+<br/>
+
+GAUSS-51100: "Failed to verify SSH trust on these nodes: %s."
+
+SQLSTATE: 无
+
+错误原因: 在各节点上核实SSH互信失败。
+
+解决办法: 检查确保各节点互信必须创建。
+
+GAUSS-51101: "SSH exception: %s"
+
+SQLSTATE: 无
+
+错误原因: 远程连接异常。
+
+解决办法: 检查确保网络连接必须正常；检查确保远程机器的IP及登录用户和密码必须正确。
+
+GAUSS-51102:"Failed to exchange SSH keys for user [%s] performing the %s operation."
+
+SQLSTATE: 无
+
+错误原因: 交换互信密钥失败。
+
+解决办法: 检查确保网络连接必须正常；检查确保机器地址配置必须正确。
+
+GAUSS-51103: "Failed to execute the PSSH command [%s]."
+
+SQLSTATE: 无
+
+错误原因: 执行PSSH命令失败。
+
+解决办法: 检查确保PSSH工具必须完整；检查确保执行命令必须正确。
+
+GAUSS-51104: "Failed to obtain SSH status."
+
+SQLSTATE: 无
+
+错误原因: 获取ssh状态和结果失败。
+
+解决办法: 检查确保网络连接必须正常；检查确保连接机器必须存在。
+
+GAUSS-51105: "Failed to parse SSH output: %s."
+
+SQLSTATE: 无
+
+错误原因: 解析ssh结果失败。
+
+解决办法: 检查确保SSH工具必须完整；检查确保解析命令必须正确。
+
+GAUSS-51106: "The SSH tool does not exist."
+
+SQLSTATE: 无
+
+错误原因: SSH工具不存在。
+
+解决办法: 检查确保SSH工具必须存在。
+
+GAUSS-51107: "Ssh Paramiko failed."
+
+SQLSTATE: 无
+
+错误原因: Paramiko互信失败。
+
+解决办法:
+
+1. 检查网络连接是否正常；
+2. 检查Paramiko包是否存在；
+3. 检查/etc/ssh/sshd_config文件以下选项:
+   - PasswordAuthentication=yes;
+   - MaxStartups=1000;
+   - UseDNS=no;
+   - ClientAliveInterval大于10800或者等于0；
+   - 当集群中机器较多时，MaxSessions是否配置过小。
+4. 修改配置后，请重启sshd服务。
+
+GAUSS-51108: "Ssh-keygen failed."
+
+SQLSTATE: 无
+
+错误原因: 执行Ssh-keygen命令失败。
+
+解决办法: 1.检查确保Ssh-keygen工具必须存在；2.检查网络是否正常。
+
+GAUSS-51109: "Failed to check authentication."
+
+SQLSTATE: 无
+
+错误原因: 身份验证失败
+
+解决办法: 查看日志，检查身份验证失败的原因，重新执行
+
+GAUSS-51110: "Failed to obtain RSA host key for local host."
+
+SQLSTATE: 无
+
+错误原因: 获取本地主机的RSA主机密钥失败
+
+解决办法: 检查获取失败的原因，重新执行
+
+GAUSS-51111: "Failed to append local ID to authorized_keys on remote node."
+
+SQLSTATE: 无
+
+错误原因: 将本地ID添加进远程节点的authorized_keys上失败
+
+解决办法: 检查添加失败的原因，重新添加
+
+GAUSS-51112: "Failed to exchange SSH keys for user[%s] using hostname."
+
+SQLSTATE: 无
+
+错误原因: 使用用户名交换SSH 密钥失败。
+
+解决办法: 检查网络是否正常。
+
+<br/>
+
+## GAUSS-51200 - GAUSS-51299
+
+<br/>
+
+GAUSS-51200: "The parameter [%s] in the XML file does not exist."
+
+SQLSTATE: 无
+
+错误原因: 找不到XML中的%s参数。
+
+解决办法: 检查XML里的配置参数。
+
+GAUSS-51201: "Node names must be configured."
+
+SQLSTATE: 无
+
+错误原因: 节点配置需要节点名称。
+
+解决办法: 节点配置指定节点名称。
+
+GAUSS-51202: "Failed to add the %s instance."
+
+SQLSTATE: 无
+
+错误原因: 追加实例失败。
+
+解决办法: 检查确保实例必须存在，配置必须正确。
+
+GAUSS-51203: "Failed to obtain the %s information from static configuration files."
+
+SQLSTATE: 无
+
+错误原因: 从静态配置文件中获取集群信息失败。
+
+解决办法: 1.检查静态配置文件是否存在；2.检查用户是否具有访问权限；3.检查系统是否正常。
+
+GAUSS-51204: " Invalid %s instance type: %d."
+
+SQLSTATE: 无
+
+错误原因: 无效的实例类型。
+
+解决办法: 检查并修改为有效的实例类型。
+
+GAUSS-51205: "Failed to refresh the %s instance ID."
+
+SQLSTATE: 无
+
+错误原因: 刷新实例编号失败。
+
+解决办法: 由于要根据当前集群的静态配置文件来刷新新集群CN的ID，所以需要检查静态配置文件是否存在或损坏，用户是否有权访问。
+
+GAUSS-51206: "The MPPRC file path must be an absolute path: %s."
+
+SQLSTATE: 无
+
+错误原因: MPPRC路径必须为绝对路径。
+
+解决办法: 修改MPPRC路径值为绝对路径值。
+
+GAUSS-51207: "Failed to obtain backIp from node [%s]."
+
+SQLSTATE: 无
+
+错误原因: 获取节点backIp失败。
+
+解决办法: 检查并正确配置该节点上的backIp。
+
+GAUSS-51208: "Invalid %s number [%d]."
+
+SQLSTATE: 无
+
+错误原因: 数量无效。
+
+解决办法: 确保数量有效。
+
+GAUSS-51209: "Failed to obtain %s configuration on the host [%s]."
+
+SQLSTATE: 无
+
+错误原因: 获取节点配置失败。
+
+解决办法: 在该节点上检查确保这项配置必须正确。
+
+GAUSS-51210: "The obtained number does not match the instance number."
+
+SQLSTATE: 无
+
+错误原因: 获取到的数量跟实例数量不匹配。
+
+解决办法: 检查并修改该数量使其与实例数量相匹配。
+
+GAUSS-51211: "Failed to save a static configuration file."
+
+SQLSTATE: 无
+
+错误原因: 保存静态配置文件失败。
+
+解决办法: 1.检查静态配置文件是否存在；2.检查用户是否具有访问权限；3.检查系统是否正常。
+
+GAUSS-51212: "There is no information about %s."
+
+SQLSTATE: 无
+
+错误原因: 没有%s信息。
+
+解决办法: 配置对应的%s信息。
+
+GAUSS-51213: "The port number of XML [%s] conflicted."
+
+SQLSTATE: 无
+
+错误原因: 端口号冲突。
+
+解决办法: 查看被占用端口的进程是否有用，如果没用kill掉，或者更换新的端口号。
+
+GAUSS-51214: "The number of capacity expansion DN nodes cannot be less than three or CN nodes cannot be less than one."
+
+SQLSTATE: 无
+
+错误原因: 扩容前的节点数不能少于3个。
+
+解决办法: 确保扩容前的节点数大于等于三个。
+
+GAUSS-51215 : "The capacity expansion node [%s] cannot contain GTM/CM/ETCD."
+
+SQLSTATE: 无
+
+错误原因: 扩容的节点上不能包含GTM/CM/ETCD。
+
+解决办法: 删除扩容节点上的GTM/CM/ETCD。
+
+GAUSS-51216: "The capacity expansion node [%s] must contain CN or DN."
+
+SQLSTATE: 无
+
+错误原因: 扩容的节点上不能没有CN或DN。
+
+解决办法: 在扩容节点上增加CN或DN。
+
+GAUSS-51217: "The cluster's static configuration does not match the new configuration file."
+
+SQLSTATE: 无
+
+错误原因: 集群配置不一致。
+
+解决办法: 修改新XML配置文件，使其与集群静态配置保持一致。
+
+GAUSS-51218:"Failed to obtain initialized configuration parameter: %s."
+
+SQLSTATE: 无
+
+错误原因: 获取初始化配置参数失败
+
+解决办法: 重新获取
+
+GAUSS-51219: "There is no CN in cluster."
+
+SQLSTATE: 无
+
+错误原因: 集群中没有安装CN。
+
+解决办法: 重新配置XML文件，然后执行前置和安装操作。
+
+GAUSS-51220: "The IP address %s is incorrect."
+
+SQLSTATE: 无
+
+错误原因: IP地址不正确。
+
+解决办法: 检查XML中配置的IP地址是否正确。
+
+GAUSS-51221: "Failed to configure hosts mapping information."
+
+SQLSTATE: 无
+
+错误原因: 配置主机映射失败。
+
+解决办法: 检查/etc/hosts文件是否存在；文件中配置的主机名和IP地址是否一一对应。
+
+GAUSS-51222: "Failed to check hostname mapping."
+
+SQLSTATE: 无
+
+错误原因: 检查主机映射失败。
+
+解决办法: 检查节点间互信是否正常。
+
+GAUSS-51223: "Failed to obtain network inet addr on the node(%s)."
+
+SQLSTATE: 无
+
+错误原因: 在节点获取inet地址失败
+
+解决办法: 用户在root下ifconfig手动确认，如果inet存在重新执行
+
+GAUSS-51224: "The ip(%s) has been used on other nodes."
+
+SQLSTATE: 无
+
+错误原因: IP已经在其它节点中使用。
+
+解决办法: 检查XML中各个节点的IP是否有冲突。
+
+GAUSS-51225: "Failed to set virtual IP."
+
+SQLSTATE: 无
+
+错误原因: 设置虚拟IP失败
+
+解决办法: 查看设置的虚拟IP是否已经使用
+
+GAUSS-51226: "Virtual IP(s) and Back IP(s) do not have the same network segment."
+
+SQLSTATE: 无
+
+错误原因: 虚拟IP和backIP不在相同的网段。
+
+解决办法: 在XML中配置虚拟IP和backIP在同一个网段。
+
+GAUSS-51227: "The number of %s on all nodes are different."
+
+SQLSTATE: 无
+
+错误原因: 所有节点上的backIP和sshIP数不相同。
+
+解决办法: XML中配置backIP和sshIP数目相同。
+
+GAUSS-51228: "The number %s does not match %s number."
+
+SQLSTATE: 无
+
+错误原因: 两个数字不匹配
+
+解决办法: 将两个数字设置为配置的数字
+
+GAUSS-51229: "The DN listenIp(%s) is not in the virtualIp or backIp on the node(%s)."
+
+SQLSTATE: 无
+
+错误原因: DN的listenIP没有在虚拟IP和backIp里。
+
+解决办法: 在XML中将listenIP修改为虚拟IP或backIp。
+
+GAUSS-51230: "The number of %s must %s."
+
+SQLSTATE: 无
+
+错误原因: CM Server/GTM/ETCD的数量不正确。
+
+解决办法: 在XML中配置CM Server/GTM/ETCD正确的数量。
+
+GAUSS-51231: "Old nodes is less than 2."
+
+SQLSTATE: 无
+
+错误原因: 旧节点数小于2。
+
+解决办法: 在XML中节点配置的数量必须大于等于3。
+
+GAUSS-51232: "XML configuration and static configuration are the same."
+
+SQLSTATE: 无
+
+错误原因: XML配置和静态配置文件相同。
+
+解决办法: 在要做扩容、缩容和manageCN等操作时，XML必须与之前安装集群的XML不同。
+
+GAUSS-51233: "The Port(%s) is invalid on the node(%s)."
+
+SQLSTATE: 无
+
+错误原因: 端口无效。
+
+解决办法: 检查XML中配置的端口号是否正确。
+
+GAUSS-51234 : "The configuration file [%s] contains parsing errors."
+
+SQLSTATE: 无
+
+错误原因: 解析XML文件不正确。
+
+解决办法: 检查配置文件是否有损坏，如果是则从另一节点拷贝一份配置文件即可；如果不是，则重新安装集群。
+
+GAUSS-51235: "Invalid directory [%s]."
+
+SQLSTATE: 无
+
+错误原因: 目录无效。
+
+解决办法: 检查目录是否正确。
+
+GAUSS-51236: "Failed to parsing xml."
+
+SQLSTATE: 无
+
+错误原因: 解析XML错误。
+
+解决办法: 查看XML是否成功打开。
+
+GAUSS-51239: "Failed to parse json. gs_collect configuration file (%s) is invalid , check key in json file"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-51240: "gs_collect configuration file is invalid, TypeName or content must in config file."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-51241: "The parameter %s(%s) formate is wrong, or value is less than 0."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-51242: "gs_collect configuration file is invalid: %s, the key: (%s) is invalid."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-51243: "content(%s) does not match the typename(%s) in gs_collect configuration file(%s)."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-51244: "(%s) doesn't yet support."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-51245: "There are duplicate key(%s)."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-51246: "%s info only support one time collect."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-51247: "These virtual IP(%s) are not accessible after configuring."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-51248: "gs_collector does not support '%s' view collection. please check key in json file."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-51300 - GAUSS-51399
+
+<br/>
+
+GAUSS-51300: "Failed to execute SQL: %s."
+
+SQLSTATE: 无
+
+错误原因:  执行SQL语句错误。
+
+解决办法:  1.确保SQL语句的正确性；2.检查数据库状态是否正常；3.检查是否有权限执行命令；4.检查数据库对象是否存在。
+
+GAUSS-51301 : "Execute SQL time out. Sql: %s."
+
+SQLSTATE: 无
+
+错误原因:  执行SQL超时。
+
+解决办法:  1.确保SQL语句的正确性；2.检查数据库状态是否正常；3.检查是否有权限执行命令；4.检查网络状态。
+
+GAUSS-51302: "The table '%s.%s' does not exist or is private table!"
+
+SQLSTATE: 无
+
+错误原因: 表不存在或者是私有表。
+
+解决办法: 1、请确保表在数据库中存在。2、如果表是私有表，请使用gs_dump进行备份。
+
+GAUSS-51303: "Query·'%s'·has·no·record!."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-51304: "Query '%s' result '%s' is incorrect!."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-51305: "The table '%s.%s' exists!"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-51400 - GAUSS-51499
+
+<br/>
+
+GAUSS-51400: "Failed to execute the command: %s."
+
+SQLSTATE: 无
+
+错误原因:  执行命令失败。
+
+解决办法:  1.检查命令是否正确；2.检查是否有权限执行命令。
+
+GAUSS-51401: "Failed to do %s.sh."
+
+SQLSTATE: 无
+
+错误原因:  执行shell脚本失败。
+
+解决办法:  1.检查命令是否正确；2.检查是否有权限执行命令；3.确保shell脚本存在。
+
+GAUSS_50402: "The usage of INODE cannot be greater than %s."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-51500 - GAUSS-51599
+
+<br/>
+
+GAUSS-51500: "Failed to call the interface %s. Exception: %s."
+
+SQLSTATE: 无
+
+错误原因:  调用接口失败。
+
+解决办法: 1.检查网络连接是否正常或地址路径是否正确；2.检查被调用接口是否开放。
+
+<br/>
+
+## GAUSS-51600 - GAUSS-51699
+
+<br/>
+
+GAUSS-51600: "Failed to obtain the cluster status."
+
+SQLSTATE: 无
+
+错误原因: 获取集群状态失败。
+
+解决办法: 1.检查集群是否搭建完成; 2.检查搭建好的集群是否启动正常。
+
+GAUSS-51601: "Failed to check %s status."
+
+SQLSTATE: 无
+
+错误原因: 检查集群/本地节点状态失败。
+
+解决办法: 检查集群/本地节点状态是否正常。
+
+GAUSS-51602: "The cluster status is Abnormal."
+
+SQLSTATE: 无
+
+错误原因: 集群状态不正常。
+
+解决办法: 检查是否因为工具脚本命令未执行完成导致集群状态没有恢复。
+
+GAUSS-51603: "Failed to obtain peer %s instance."
+
+SQLSTATE: 无
+
+错误原因: 获取对等的实例失败。
+
+解决办法: 1.如果获取GTM，则确保gtm.conf路径存在；2.检查配置是否正确。
+
+GAUSS-51604: "There is no HA status for %s."
+
+SQLSTATE: 无
+
+错误原因: 实例没有HA状态。
+
+解决办法: 确保集群状态以及网络连接正常。
+
+GAUSS-51605: "Failed to check whether the %s process exists."
+
+SQLSTATE: 无
+
+错误原因: 检查进程是否存在失败。
+
+解决办法: 1.确保权限可执行检查；2.确保检查进程的正确性。
+
+GAUSS-51606: "Failed to kill the %s process.
+
+SQLSTATE: 无
+
+错误原因: 杀进程失败。
+
+解决办法: 1.确保权限可执行此操作；2.检查执行命令是否正确。
+
+GAUSS-51607: "Failed to start %s."
+
+错误原因: 启动集群/节点/实例失败。
+
+解决办法: 1.检查网络连接是否正常；2.检查配置文件是否正确。
+
+GAUSS-51608: "Failed to lock cluster"
+
+SQLSTATE: 无
+
+错误原因: 锁集群失败。
+
+解决办法: 确保在该会话完成前没有进行关闭停止等操作。
+
+GAUSS-51609: "Failed to unlock cluster"
+
+SQLSTATE: 无
+
+错误原因: 解锁集群失败。
+
+解决办法: 确保在该会话完成前没有进行关闭停止等操作。
+
+GAUSS-51610: "Failed to stop %s."
+
+SQLSTATE: 无
+
+错误原因: 停止集群/节点/实例失败。
+
+解决办法: 1.确保命令操作执行正确；2.检查确保集群/节点/实例当前状态无异常。
+
+GAUSS-51611: "Failed to create %s instance."
+
+SQLSTATE: 无
+
+错误原因: 创建实例失败。
+
+解决办法: 检查XML中有CN的节点配置是否正确。
+
+GAUSS-51612: "The instance IDs [%s] are not found in %s."
+
+SQLSTATE: 无
+
+错误原因: 在节点信息里没有找到某个实例ID。
+
+解决办法: 在做增删CN时，检查XML中增删CN的节点配置是否正确。
+
+GAUSS-51613: "There is no instance in %s to be built."
+
+SQLSTATE: 无
+
+错误原因: 没有需要创建的实例。
+
+解决办法: 在做manageCN的时候，XML配置的不正确，XML中没有在新节点中配实例。
+
+GAUSS-51614: "Received signal[%d]."
+
+SQLSTATE: 无
+
+错误原因: 接收信号%d。
+
+解决办法: 重新接收。
+
+GAUSS-51615: "Failed to initialize instance."
+
+SQLSTATE: 无
+
+错误原因: 初始化实例失败。
+
+解决办法: 1.确保gs_initdb/gs_initcm工具存在；2.确保gs_initdb/gs_initcm命令正确；3.检查确保集群/节点/实例当前状态无异常。
+
+GAUSS-51616: "Failed to dump %s schema."
+
+SQLSTATE: 无
+
+错误原因: dump CN/DN schema失败。
+
+解决办法: 1.dumpall/dump工具存在；2.确保dumpall/dump命令操作正确；3.检查确保集群/节点/实例当前状态无异常。
+
+GAUSS-51617: "Failed to rebuild %s."
+
+SQLSTATE: 无
+
+错误原因: 重建失败
+
+解决办法: 重新执行命令
+
+GAUSS-51618: "Failed to get all hostname."
+
+SQLSTATE: 无
+
+错误原因: 获取所有主机名失败。
+
+解决办法: 确保ssh互信正常。
+
+GAUSS-51619: "The host·name [%s] is not in the cluster."
+
+SQLSTATE: 无
+
+错误原因: 当前节点不在集群内。
+
+解决办法: 检查xml中是否配置了该节点。
+
+GAUSS-51620: "Failed to obtain %s instance information."
+
+SQLSTATE: 无
+
+错误原因: 获取实例信息失败。
+
+解决办法: 1.确保XML配置正确；2.检查确保集群/节点/实例当前状态无异常。
+
+GAUSS-51621: "HA IP is empty."
+
+SQLSTATE: 无
+
+错误原因: HA IP为空。
+
+解决办法: 检查XML文件配置信息，如果XML中配置了HA IP，此时需确保其值配置正确；如果XML中没有配置HA IP，则其会默认使用backIP，此时需要确保正确配置XML文件中的backIP。
+
+GAUSS-51622: "There is no %s on %s node."
+
+SQLSTATE: 无
+
+错误原因: 节点上没有CN/DN实例。
+
+解决办法: 1.检查XML中该节点是否配置了CN/DN实例；2.检查确保集群/节点/实例当前状态无异常。
+
+GAUSS-51623: "Failed to obtain version."
+
+SQLSTATE: 无
+
+错误原因: 获取集群版本失败。
+
+解决办法: 1.确保version.cfg文件存在；2.检查version.cfg文件中数据格式是否正确；3.检查确保集群/节点/实例当前状态无异常。
+
+GAUSS-51624: "Failed to get CN connections."
+
+SQLSTATE: 无
+
+错误原因: 获取CN连接数失败。
+
+解决办法: 检查确保集群/节点/实例当前状态无异常。
+
+GAUSS-51625: "Cluster is running."
+
+SQLSTATE: 无
+
+错误原因: 集群正在运行。
+
+解决办法: 停止集群。
+
+GAUSS-51626: "Failed to rollback."
+
+SQLSTATE: 无
+
+错误原因: 回滚失败。
+
+解决办法: 1.确保命令操作执行正确；2.检查确保集群/节点/实例当前状态无异常；3.查看对应日志信息。
+
+GAUSS-51627: "Configuration failed."
+
+SQLSTATE: 无
+
+错误原因: 配置失败
+
+解决办法: 重新配置
+
+GAUSS-51628: "The version number of new cluster is [%s]. It should be float."
+
+SQLSTATE: 无
+
+错误原因: 新集群的版本号格式不正确。
+
+解决办法: 1.确保version.cfg文件存在；2.检查version.cfg文件中数据格式是否正确；3.检查确保集群/节点/实例当前状态无异常。
+
+GAUSS-51629: "The version number of new cluster is [%s]. It should be greater than or equal to the old version."
+
+SQLSTATE: 无
+
+错误原因: 新集群的版本号不正确，应该大于或等于旧版本号。
+
+解决办法: 1.确保version.cfg文件存在；2.检查新集群的version.cfg文件中数据是否小于现有集群的版本号；3.检查确保集群/节点/实例当前状态无异常。
+
+GAUSS-51630: "No node named %s."
+
+SQLSTATE: 无
+
+错误原因: 节点名不存在。
+
+解决办法: 1.检查XML中是否配置了该节点；2.检查确保集群/节点/实例当前状态无异常。
+
+GAUSS-51631: "Failed to delete the %s instance."
+
+SQLSTATE: 无
+
+错误原因: 删除CN实例失败。
+
+解决办法: 1.确保ssh互信正常；2.确保命令操作执行正确；3.检查确保集群/节点/实例当前状态无异常。
+
+GAUSS-51632: "Failed to do %s."
+
+SQLSTATE: 无
+
+错误原因: 执行python脚本失败。
+
+解决办法: 1.确保python脚本存在；2.确保命令操作执行正确；3.检查确保集群/节点/实例当前状态无异常。
+
+GAUSS-51633: "The·step·of·upgrade·number·%s·is·incorrect."
+
+SQLSTATE: 无
+
+错误原因: ID必须是数字。
+
+解决办法: 1.确保指定的实例存在；2.确保命令操作执行正确；3.检查确保集群/节点/实例当前状态无异常。
+
+GAUSS-51634: "Waiting node synchronizing timeout lead to failure."
+
+SQLSTATE: 无
+
+错误原因: 等待节点同步超时导致失败。
+
+解决办法: 1.确保命令操作执行正确；2.检查确保集群/节点/实例当前状态无异常。
+
+GAUSS-51635: "Failed to check SHA256."
+
+SQLSTATE: 无
+
+错误原因: 检查SHA256失败。
+
+解决办法: 1.确保SHA256文件存在；2.确保命令操作执行正确；3.检查确保集群/节点/实例当前状态无异常。
+
+GAUSS-51636: "Failed to obtain %s node information."
+
+SQLSTATE: 无
+
+错误原因: 获取节点信息失败。
+
+解决办法: 1.确保XML中配置了该节点；2.确保命令操作执行正确；3.检查确保集群/节点/实例当前状态无异常。
+
+GAUSS-51637: "The %s does not match with %s."
+
+SQLSTATE: 无
+
+错误原因: 集群信息不匹配。
+
+解决办法: 1.确保需要匹配的双方同时更新；2.确保命令操作执行正确；3.检查确保集群/节点/实例当前状态无异常。
+
+GAUSS-51638: "Failed to append instance on host [%s]."
+
+SQLSTATE: 无
+
+错误原因: 在某个节点上追加实例失败。
+
+解决办法: 1.检查XML配置是否正确，路径是否有冲突；2.检查确保集群/节点/实例当前状态无异常。
+
+GAUSS-51639: "Failed to obtain %s status of local node."
+
+SQLSTATE: 无
+
+错误原因: 获取本地节点状态失败。
+
+解决办法: 排除异常。
+
+GAUSS-51640: "Can't connect to cm_server, cluster is not running possibly."
+
+SQLSTATE: 无
+
+错误原因: 连接不上cm_server，集群可能不在运行。
+
+解决办法: 重启集群。
+
+GAUSS-51641: "Cluster redistributing status is not accord with expectation."
+
+SQLSTATE: 无
+
+错误原因: 重分布状态不满足条件。
+
+解决办法: 1.检查进群状态是否正常和健康；2.检查确保集群/节点/实例当前状态无异常。
+
+GAUSS-51642: "Failed to promote peer instances."
+
+SQLSTATE: 无
+
+错误原因: 拉起对等实例失败。
+
+解决办法: 1.确保指定的实例存在；2.确保命令操作执行正确；3.检查确保集群/节点/实例当前状态无异常。
+
+GAUSS_51643: "Cluster is in read-only mode."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS_51644: "Failed to set resource control for the cluster."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-51645: "Failed to restart %s."
+
+SQLSTATE: 无
+
+错误原因: 重启集群/逻辑集群失败。
+
+解决办法: 1.检查网络连接是否正常；2.检查配置文件是否正确。
+
+GAUSS-51646: "The other OM operation is currently being performed in the cluster node:"" '%s'."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-51647: "The operation step of OM components in current cluster nodes do not match"" with each other: %s."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-51648: "Waiting for redistribution process to end timeout."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-51649: "Capture exceptions '%s' : %s."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-51650: "Unclassified exceptions: %s."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-51651: "The node '%s' status is Abnormal."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-51652: "The package version on some nodes are inconsistent."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-51653: "The %s can not exist in %s."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-51654: "The standbyIp %s should different Kerberos server IP %s."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-51655: "The %s has already installed."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-51656: "Failed to make server.key.cipher and server.key.rand"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-51700 - GAUSS-51799
+
+<br/>
+
+GAUSS-51704: "Failed to set Cgroup."
+
+SQLSTATE: 无
+
+错误原因: 设置Cgroups失败
+
+解决办法: 重新设置
+
+GAUSS-51706: "Failed to check Cgroup."
+
+SQLSTATE: 无
+
+错误原因: 检查Cgroups失败。
+
+解决办法: 检查数据库状态是否正常。
+
+GAUSS-51707: "Failed to install Cgroup."
+
+SQLSTATE: 无
+
+错误原因: 安装Cgroups失败。
+
+解决办法: 检查数据库中是否已经成功挂载了Cgroups组件。
+
+GAUSS-51708: "Failed to uninstall Cgroup."
+
+SQLSTATE: 无
+
+错误原因: 卸载Cgroups失败
+
+解决办法: 重新执行卸载
+
+GAUSS-51709: "Failed to clean Cgroup configuration file."
+
+SQLSTATE: 无
+
+错误原因: 清除Cgroups配置文件失败
+
+解决办法: 重新执行清除命令
+
+<br/>
+
+## GAUSS-51800 - GAUSS-51899
+
+<br/>
+
+GAUSS-51800: "The environmental variable %s is empty.·or·variable·has·exceeded·maximum·length"
+
+SQLSTATE: 无
+
+错误原因: 环境变量为空。
+
+解决办法: 确保环境变量成功写入。
+
+GAUSS-51801: "The environment variable %s exists."
+
+SQLSTATE: 无
+
+错误原因: 环境变量已经存在。
+
+解决办法: 检查环境变量存在于.barshrc文件中的原因，是否因为在文件中已添加导致。
+
+GAUSS-51802: "Failed to obtain the environment variable %s."
+
+SQLSTATE: 无
+
+错误原因: 获取环境变量失败。
+
+解决办法: 1.确保环境变量配置完成；2.检查获取环境变量的路径是否正确。
+
+GAUSS-51803: "Failed to delete the environment variable %s."
+
+SQLSTATE: 无
+
+错误原因: 删除环境变量失败。
+
+解决办法: 1.确保删除命令正确性；2.确保拥有删除权限。
+
+GAUSS-51804: "Failed to set the environment variable %s."
+
+SQLSTATE: 无
+
+错误原因: 设置环境变量失败。
+
+解决办法: 1.检查权限是否正确；2.检查网络连接是否正常；3.检查设置环境变量命令是否准确。
+
+GAUSS-51805: "The environmental variable [%s]'s value is invalid."
+
+SQLSTATE: 无
+
+错误原因: 环境变量值无效。
+
+解决办法: 1.检查网络连接是否正常；2.检查设置环境变量命令是否准确；3.检查./bashrc文件中$GAUSS_ENV环境变量的值是否正确。
+
+GAUSS-51806: "The cluster has been installed."
+
+SQLSTATE: 无
+
+错误原因: 集群已经安装。
+
+解决办法: 检查.bashrc文件中$GAUSS_ENV环境变量的值是否为2。
+
+GAUSS-51807: "$GAUSSHOME of user is not equal to installation path."
+
+SQLSTATE: 无
+
+错误原因: GAUSSHOME路径和集群安装路径不一致。
+
+解决办法: 1.检查权限是否正确；2.检查网络连接是否正常；3.检查设置环境变量命令是否准确；4.检查./bashrc文件中$GAUSSHOME环境变量的值是否与XML中配置的路径相同。
+
+GAUSS-51808: "The env file contains errmsg: %s."
+
+SQLSTATE: 无
+
+错误原因: /etc/profile等环境变量文件包含错误流或输出流。
+
+解决办法: 根据提示检查对应文件，执行source，找到对应的输出信息，并删除对应shell。
+
+GAUSS-51809: "The variable [%s] context [%s] is invalid."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-51900 - GAUSS-51999
+
+<br/>
+
+GAUSS-51900: "The current OS is not supported."
+
+SQLSTATE: 无
+
+错误原因: 不支持当前的操作系统。
+
+解决办法: 检查切换与之匹配的操作系统进行操作。
+
+GAUSS-51901: "The OS versions are different among cluster nodes."
+
+SQLSTATE: 无
+
+错误原因: 集群节点间操作系统版本不一致。
+
+解决办法: 确保集群中每个节点的操作系统版本一致。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/78-GAUSS-52000-GAUSS-52999.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/78-GAUSS-52000-GAUSS-52999.md
new file mode 100644
index 0000000000000000000000000000000000000000..4ce029b85b916e46b29c3d62a7d6d693519cfea8
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/78-GAUSS-52000-GAUSS-52999.md
@@ -0,0 +1,914 @@
+---
+title: GAUSS-52000 - GAUSS-52999
+summary: GAUSS-52000 - GAUSS-52999
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-52000 - GAUSS-52999
+
+<br/>
+
+## GAUSS-52000 - GAUSS-52099
+
+<br/>
+
+GAUSS-52000: "Failed to obtain time zone information about the cluster node."
+
+SQLSTATE:无
+
+错误原因: 获取集群节点时区失败。
+
+解决办法: 检查时区获取命令"date -R"是否支持。
+
+GAUSS-52001: "Time zone information is different among cluster nodes."
+
+SQLSTATE:无
+
+错误原因: 集群节点时区不一致。
+
+解决办法: 使用date命令将各个节点的时区设为一致。
+
+<br/>
+
+## GAUSS-52100 - GAUSS-52199
+
+<br/>
+
+GAUSS-52100: "Failed to obtain cluster node character sets."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-52101: "Character sets are different among cluster nodes."
+
+SQLSTATE: 无
+
+错误原因: 集群节点字符集不一致。
+
+解决办法: 将各个节点需求的字符集格式手工强制写入/etc/profile文件中。
+
+GAUSS-52102: "The parameter [%s] value is not equal to the expected value."
+
+SQLSTATE: 无
+
+错误原因: 参数值不等于期望值。
+
+解决办法: 设置参数值等于期望值。
+
+GAUSS-52103: "Failed to forcibly make the character sets to take effect."
+
+SQLSTATE: 无
+
+错误原因: 强制字符集生效失败
+
+解决办法: 重新安装字符集
+
+<br/>
+
+## GAUSS-52200 - GAUSS-52299
+
+<br/>
+
+GAUSS-52200: "Unable to import module: %s."
+
+SQLSTATE: 无
+
+错误原因: 采用系统默认python执行工具，导致导入包错: 缺少python依赖的库。
+
+解决办法: 使用安装包中自带的python执行工具，即进入安装包解压的目录，使用"./工具名"方式来执行命令。
+
+以执行前置为例:
+
+进入到工具脚本存放目录下:
+
+```bash
+cd /opt/software/gaussdb/script
+```
+
+使用./gs_preinstall 执行前置:
+
+```shell
+./gs_preinstall -U omm -G dbgrp -X /opt/software/gaussdb/clusterconfig.xml --alarm-type=5 --root-passwd=Gauss_234
+```
+
+GAUSS-52201: "The current python version %s is not supported."
+
+SQLSTATE: 无
+
+错误原因: 操作系统默认的Python不是2.6.X或2.7.X。
+
+解决办法: 替换操作系统默认的Python编译器版本。
+
+<br/>
+
+## GAUSS-52300 - GAUSS-52399
+
+<br/>
+
+GAUSS-52300: "Failed to set OS parameters."
+
+SQLSTATE: 无
+
+错误原因: 设置操作系统参数失败。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-52301: "Failed to check OS parameters."
+
+SQLSTATE: 无
+
+错误原因: 检查操作系统参数失败。
+
+解决办法: 1.查看"uname -r 2>/dev/null"命令是否可用；2.查看"grep -Er '\\' /etc/keepalived/keepalived.conf "命令是否可执行；3.检查python是否安装以及是否有安装multiprocessing模块。
+
+<br/>
+
+## GAUSS-52400 - GAUSS-52499
+
+<br/>
+
+GAUSS-52400: "Installation environment does not meet the desired result."
+
+SQLSTATE: 无
+
+错误原因: 安装环境不能满足要求。
+
+解决办法: 使用gs_checkos检查操作系统是否满足安装要求。
+
+GAUSS-52401: "On systemwide basis, the maximum number of %s is not correct. the current %s value is:"
+
+SQLSTATE: 无
+
+错误原因: 系统范围内每个信号集中的信号量/信号集/信号量最大数目不正确。当前%s的值为: 。
+
+解决办法: 查看cat /proc/sys/kernel/sem获取信号数量，检查SEMMSL、SEMMNI或者SEMMNS是否满足要求。
+
+GAUSS-52402: "IP [%s] is not matched with hostname [%s]. "
+
+SQLSTATE: 无
+
+错误原因: IP与主机名不匹配。
+
+解决办法: 检查IP和主机名是否匹配，如果不匹配，则需要修改/etc/profile文件使其相匹配。
+
+GAUSS-52403: "Command \\"%s\\" does not exist or the user has no execute permission on %s."
+
+SQLSTATE: 无
+
+错误原因: 命令不存在或者用户没有执行权限。
+
+解决办法: 1.检查命令是否存在；2.确认用户权限是否满足要求。
+
+<br/>
+
+## GAUSS-52500 - GAUSS-52599
+
+<br/>
+
+GAUSS-52500: "Failed to delete regular tasks."
+
+SQLSTATE: 无
+
+错误原因: 删除规则任务失败。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-52501: "Run %s script before executing this script."
+
+SQLSTATE: 无
+
+错误原因: 在执行这个脚本之前先运行某个脚本。
+
+解决办法: 检查脚本的先后执行顺序。
+
+GAUSS-52502: "Another OM process is being executed. To avoid conflicts, this process ends in advance."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-52503: "Failed to execute checkRunStatus.py. Error: %s"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-52600 - GAUSS-52699
+
+<br/>
+
+GAUSS-52600: "Can not obtain any cluster ring."
+
+SQLSTATE: 无
+
+错误原因: 不能获取数据库中的任何环。
+
+解决办法: 检查XML中节点信息是否配置正确。
+
+GAUSS-52601: "Redistribution failed due to user request."
+
+SQLSTATE: 无
+
+错误原因: 由于用户请求，重分布失败。
+
+解决办法: 检查在扩容/缩容过程中，用户有没有执行非法操作。
+
+GAUSS-52604: " Parameter '-r'[%s] can not be more than the numbers of cluster ring[%s]."
+
+SQLSTATE: 无
+
+错误原因: 参数-r的值不能比数据库环的数量还要多。
+
+解决办法: 检查gs_shrink命令中'-r'参数的值是否超过数据库XML中配置的数据库环的个数。
+
+GAUSS-52605: "Can not contract local node(%s). "
+
+SQLSTATE: 无
+
+错误原因: 不能缩容本地节点。
+
+解决办法: 检查XML中配置的缩容节点是否包含执行缩容命令的所在节点。
+
+GAUSS-52606: " Contract too many nodes. It should left three nodes to format a cluster at least."
+
+SQLSTATE: 无
+
+错误原因: 缩容太多节点。缩容后的数据库至少保留3个节点。
+
+解决办法: 检查执行缩容命令的XML文件配置中缩容以后的数据库节点数量是否小于3个。
+
+GAUSS-52607: " [%s] does not at the end of instance list."
+
+SQLSTATE: 无
+
+错误原因: 节点不在实例列表的末尾。
+
+解决办法: 检查XML中配置的缩容节点是否为数据库节点中按顺序排序的末尾几个节点。
+
+GAUSS-52608: " [%s] contains %s instance."
+
+SQLSTATE: 无
+
+错误原因: 节点包含CM Server/ETCD实例。
+
+解决办法: 检查缩容的节点中是否包含CM Server/ETCD实例，如果是，则需要重新配置对应节点，使其不能包含CM Server/ETCD实例，然后重新执行命令。
+
+GAUSS-52609: " All contracted nodes do not contain DN instance."
+
+SQLSTATE: 无
+
+错误原因: 所有的缩容节点中不能包含DN实例。
+
+解决办法: 检查XML中配置的缩容节点是否包含DN实例。
+
+GAUSS-52612: " All dilatation nodes do not contain the DN instance."
+
+SQLSTATE: 无
+
+错误原因: 所有的扩容节点不能包含DN实例。
+
+解决办法: 检查XML中配置的扩容节点中是否配置了DN实例。
+
+GAUSS-52613: " Static configuration is not matched on some nodes. Please handle it first."
+
+SQLSTATE: 无
+
+错误原因: 节点上的静态配置文件与新的XML文件不匹配。
+
+解决办法: 检查xml文件配置是否正确，修改后重新执行前置脚本。
+
+GAUSS-52614: "Timeout. The current cluster status is %s."
+
+SQLSTATE: 无
+
+错误原因: 超时
+
+解决办法: 重试
+
+GAUSS-52615: "Cluster lock unlocked due to timeout. "
+
+SQLSTATE: 无
+
+错误原因: 由于超时数据库解锁失败。
+
+解决办法: 1.检查数据库状态是否正常；2.数据库可否进行写操作；3.查看相对应的日志，查看详细的错误信息。
+
+GAUSS-52616: "Can not find a similar instance for [%s %s]. "
+
+SQLSTATE: 无
+
+错误原因: 不能找到一个近似的实例[主机名 实例目录]。
+
+解决办法: 1.检查数据库状态是否正常；2.XML中节点信息是否配置正确。
+
+GAUSS-52617: "Invalid check type. "
+
+SQLSTATE: 无
+
+错误原因: 无效的检查类型。
+
+解决办法: 缩容模块检查节点组的检查类型错误，应该是precheck和postcheck，其他类型都是错误。
+
+GAUSS-52618: "Failed to delete etcd from node. "
+
+SQLSTATE: 无
+
+错误原因: 删除ETCD失败。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-52619: "Failed to uninstall application."
+
+SQLSTATE: 无
+
+错误原因: 卸载应用失败
+
+解决办法: 重新执行
+
+GAUSS-52620: " Not all nodes found. The following is what we found: %s."
+
+SQLSTATE: 无
+
+错误原因: 没有找到所有节点。以下是我们找到的节点: 。
+
+解决办法: 1.检查数据库状态是否正常；2.检查XML中配置的缩容节点名是否正确。
+
+GAUSS-52621: " No DNs specified in target create new group."
+
+SQLSTATE: 无
+
+错误原因: 在创建新节点组时没有DN。
+
+解决办法: 缩容模块创建新节点组时，没有DN，需要检查确认节点上DN配置是否正常。
+
+GAUSS-52622: " No new group name specified in target create new group."
+
+SQLSTATE: 无
+
+错误原因: 在创建新节点组时没有节点组名。
+
+解决办法: 缩容模块创建新节点组时，新节点组名为空，需要检查新节点组名是否正确，新节点组名取值范围: group_version2或group_version1。
+
+GAUSS-52625: "The local instance and peer instance does not both in contracted nodes. "
+
+SQLSTATE: 无
+
+错误原因: 本地实例和对端实例不在同一个缩容节点。
+
+解决办法: 请检查缩容节点是否自成一个环。
+
+GAUSS-52627: " The current cluster is locked."
+
+SQLSTATE: 无
+
+错误原因: 数据库处于锁状态。
+
+解决办法: 扩容模块检查老节点数据库已经被锁定，需要将当前数据库解锁后继续扩容。
+
+GAUSS-52628: "Static configuration has already been updated on all nodes, expansion has been completed possibly. "
+
+SQLSTATE: 无
+
+错误原因: 静态配置文件已经在各个节点更新，扩容可能已经完成。
+
+解决办法: 查看扩容以后的数据库状态是否正常，如果数据库中已经包含了扩容节点并且数据库状态正常，那么就不用再执行扩容命令了。
+
+GAUSS-52629: "Cluster ring(%s) can not obtain less than three nodes. "
+
+SQLSTATE: 无
+
+错误原因: 数据库环不能小于3个节点。
+
+解决办法: 检查缩容场景下使用的XML文件配置，执行的缩容节点数量是否小于3。
+
+GAUSS-52630: "Failed to set the read-only mode parameter for all DN instances. "
+
+SQLSTATE: 无
+
+错误原因: 设置所有DN实例只读模式参数失败。
+
+解决办法: 检查gs_guc工具是否存在，数据库状态是否正常，重试设置只读模式。
+
+GAUSS-52632: "Cluster breakdown or abnormal operation during expanding online, lock process for expansion is lost."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-52633: "Can not excute redistribution for shrink excuted failed."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-52634: "Redis table record count cannot be more than %d."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-52700 - GAUSS-52799
+
+<br/>
+
+GAUSS-52700: "Failed to update ETCD."
+
+SQLSTATE: 无
+
+错误原因: 更新ETCD失败。
+
+解决办法: 根据replace日志分析处理。
+
+GAUSS-52701: "All the CMAgents instances are abnormal. Cannot fix the cluster."
+
+SQLSTATE: 无
+
+错误原因: 所有的CM Agent实例损坏，不能修复集群。
+
+解决办法: 通过gs_replace工具进行温备。
+
+GAUSS-52702: "The cluster status is Normal. There is no instance to fix."
+
+SQLSTATE: 无
+
+错误原因: 集群状态正常，没有实例需要进行修复。
+
+解决办法: 不需要执行修复操作。
+
+GAUSS-52703: "The number of normal ETCD must be greater than half."
+
+SQLSTATE: 无
+
+错误原因: 集群中正常的ETCD个数必须大于一半。
+
+解决办法: 1.检查温备后集群状态是否正常；2.集群中正常的ETCD数量是否超过一半。
+
+GAUSS-52704: "Failed to check the %s condition."
+
+SQLSTATE: 无
+
+错误原因: 检查条件失败。
+
+解决办法: 检查对应的进程是否正常。
+
+GAUSS-52705: "Failed to obtain ETCD key."
+
+SQLSTATE: 无
+
+错误原因: 获取ETCD key失败。
+
+解决办法: 查看etcdctl日志分析处理。
+
+GAUSS-52706: "Failed to clean ETCD and touch flag file on %s."
+
+SQLSTATE: 无
+
+错误原因: 在节点上清理ETCD实例和创建标志文件失败。
+
+解决办法: 检查对应节点上是否有足够权限。
+
+GAUSS-52707: "Failed to install on %s."
+
+SQLSTATE: 无
+
+错误原因: 温备节点安装失败。
+
+解决办法: 根据replace日志进行分析处理。
+
+GAUSS-52708: "Failed to configure on %s."
+
+SQLSTATE: 无
+
+错误原因: 温备节点配置失败。
+
+解决办法: 根据replace日志进行分析处理。
+
+GAUSS-52709: "Failed to check the cluster configuration differences:"
+
+SQLSTATE: 无
+
+错误原因: 检查集群配置差异失败。
+
+解决办法: 在做温备或者修改IP时，对比xml文件和当前集群配置是否有差异，如果没有，则不能做温备或者修改IP，需要重新修改xml的配置信息。
+
+GAUSS-52710: "Replacement failed."
+
+SQLSTATE: 无
+
+错误原因: 替换实例失败。
+
+解决办法: 查看对应日志，查找详细失败信息。
+
+GAUSS-52711: "Failed to set CMAgent start mode."
+
+SQLSTATE: 无
+
+错误原因: 设置CM Agent启动模式失败。
+
+解决办法: 查看etcdctl日志分析处理。
+
+GAUSS-52712: "Failed to read step file with erro:[%s]."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-52713: "Failed to repair cm_server, errorinfo:[%s]."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-52714: "Failed to write step file, errorinfo:[%s]."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-52800 - GAUSS-52899
+
+<br/>
+
+GAUSS-52800: "Cluster is %s(%s) now."
+
+SQLSTATE: 无
+
+错误原因: 集群状态不正常(集群状态为Abnormal或者Degrade)。
+
+解决办法: 查看集群状态根据日志报错分析原因。
+
+GAUSS-52801: "Only allow to %s one CN. The %s is not matched."
+
+SQLSTATE: 无
+
+错误原因: 仅允许增加/删除一个CN，CN/DN/GTM/ETCD/CM Server数量不匹配 。
+
+解决办法: 检查xml中配置是否对其它实例进行了增删操作。
+
+GAUSS-52802: "Only allow to add one CN at the end."
+
+SQLSTATE: 无
+
+错误原因: 只允许在末尾增加一个CN 。
+
+解决办法: 请检查指定的XML配置，集群外增加CN只允许在集群中所有节点末尾增加一个CN。
+
+GAUSS-52803: "There is at least one Normal CN after delete CN."
+
+SQLSTATE: 无
+
+错误原因: 在删除CN后至少要保留一个正常的CN。
+
+解决办法: 检查执行删除CN操作的XML文件配置是否正确，保证在做删除CN以后，集群中还有一个正常的CN。
+
+GAUSS-52804: "Failed to add the Abnormal CN."
+
+SQLSTATE: 无
+
+错误原因: 增加不正常的CN失败。
+
+解决办法: 1.修改pgxc_node文件失败，请结合具体日志分析失败原因；2.重新执行一遍命令。
+
+GAUSS-52805: "Failed to find another instance as model for instance(%s)."
+
+SQLSTATE: 无
+
+错误原因: 没有找到其他可用的实例模板。
+
+解决办法: 查看具体日志分析失败原因。
+
+GAUSS-52806: "Invalid rollback step: %s."
+
+SQLSTATE: 无
+
+错误原因: 无效的回滚步骤。
+
+解决办法: 在GPHOST路径下，查看记录CN配置步骤的文件GaussManageCN.dat中的数据是否正确。
+
+GAUSS-52807: "There is no IP changed."
+
+SQLSTATE: 无
+
+错误原因: 没有需要修改的IP。
+
+解决办法: 检查IP是否已在集群中使用，如果在使用，则需要重新配置XML文件。
+
+GAUSS-52808: "Detected CN %s, but the action is %s."
+
+SQLSTATE: 无
+
+错误原因: 命令中的增删CN操作和xml配置不一致。
+
+解决办法: 修改命令中的增删CN动作(add或者delete)或者修改xml中增删CN的配置信息。
+
+GAUSS-52809: "Only allow to add or delete one CN."
+
+SQLSTATE: 无
+
+错误原因: 增删CN数量不为1。
+
+解决办法: 一次只允许增加或者删除一个CN。
+
+GAUSS-52810: "There is Abnormal coodinator(s) in cluster, please delete it firstly."
+
+SQLSTATE: 无
+
+错误原因: 集群中存在异常CN实例，导致想要删除的CN无法删除。
+
+解决办法: 先删除异常的CN，再进行其他CN的删除操作。
+
+<br/>
+
+## GAUSS-52900 - GAUSS-52999
+
+<br/>
+
+GAUSS-52900: " Failed to upgrade strategy: %s."
+
+SQLSTATE:无
+
+错误原因: 升级策略失败。
+
+解决办法: 检查版本信息文件version.cfg。
+
+GAUSS-52901: "New·cluster·commitid·cannot·be·same·with·old·cluster·commitid."
+
+SQLSTATE:无
+
+错误原因: 二进制升级的备份路径和大版本升级的备份路径不应该同时存在。
+
+解决办法: 确认上次升级失败的原因，排除后，整理备份文件。
+
+GAUSS-52902: "Can not support upgrade from %s to %s"
+
+SQLSTATE:无
+
+错误原因: 不支持从该版本的升级。
+
+解决办法: 请使用支持的版本进行升级，或使用中间版本过渡。
+
+GAUSS-52903: "The new cluster version number[%s] should be bigger than the old cluster[%s]."
+
+SQLSTATE:无
+
+错误原因: 不支持版本回退，即升级后的版本号必须大于升级前的版本号。
+
+解决办法: 请确认使用的版本信息。
+
+GAUSS-52904: "Please choose right upgrade strategy."
+
+SQLSTATE:无
+
+错误原因: 请选择正确的升级策略。
+
+解决办法: 调用策略选择接口，正确使用升级接口，或调用自动升级接口。
+
+GAUSS-52905: "Upgrade nodes number cannot be more than %d."
+
+SQLSTATE:无
+
+错误原因: 获取当前版本号失败。
+
+解决办法: 请查看相应的日志，查找详细的错误信息。
+
+GAUSS-52906: "Grey upgrade nodes number cannot be more than cluster nodes."
+
+SQLSTATE:无
+
+错误原因: 初始化升级失败。
+
+解决办法: 查看升级日志，排除错误原因，重试。
+
+GAUSS-52907: "Failed to cancel the cluster read-only mode"
+
+SQLSTATE:无
+
+错误原因: 取消集群只读模式失败。
+
+解决办法: 手动调用guc工具，命令为: gs_guc reload -Z coordinator -N all -I all -c "default_transaction_read_only=false"；gs_guc reload -Z datanode -N all -I all -c "default_transaction_read_only=false"，取消只读模式，重试。
+
+GAUSS-52908: "Failed to set cluster read-only mode."
+
+SQLSTATE:无
+
+错误原因: 设置只读模式失败。
+
+解决办法: 查看guc日志，排除错误后，重新执行命令。
+
+GAUSS-52909: "Specified upgrade nodes with same step can do upgrade task."
+
+SQLSTATE:无
+
+错误原因: 不合法的模式。
+
+解决办法: 请查找相对应的日志信息。
+
+GAUSS-52910: "These nodes %s have been successfully upgraded to new version, no need to upgrade again."
+
+SQLSTATE:无
+
+错误原因: 用户自定义检查失败。
+
+解决办法: 排查用户自定义检查脚本是否存在错误，或根据检查期望，排查升级失败原因。
+
+GAUSS-52911: "Last unsuccessfully upgrade nodes %s are not same with current upgrade nodes."
+
+SQLSTATE:无
+
+错误原因: 完全升级失败
+
+解决办法: 重新升级
+
+GAUSS-52912: "Some nodes were upgraded but were unsuccessfully, cannot use -continue."
+
+SQLSTATE:无
+
+错误原因: 在普通模式启动集群失败。
+
+解决办法: 手动排除原因，调用gs_om -t start命令手动启动集群。
+
+GAUSS-52913: "All nodes have been upgraded. No need to use -continue."
+
+SQLSTATE:无
+
+错误原因: 回滚失败
+
+解决办法: 重新执行
+
+GAUSS-52914: "The record commitid is not same with current commitid."
+
+SQLSTATE:无
+
+错误原因: 清除回滚脚本失败。
+
+解决办法: 排查集群状态，若升级成功，可手动清理残留文件。
+
+GAUSS-52915: "$GAUSSHOME is not a symbolic link."
+
+SQLSTATE:无
+
+错误原因: 不合法的升级步骤。
+
+解决办法: 在GPHOST路径下，请确认升级备份的步骤记录文件是否被修改。
+
+GAUSS-52916: "Current upgrade status is not pre commit."
+
+SQLSTATE:无
+
+错误原因: 集群节点不满足提交条件。
+
+解决办法: 确保所有节点升级成功后，再进行提交操作。
+
+GAUSS-52917: "Failed to drop old pmk schema."
+
+SQLSTATE:无
+
+错误原因: 二进制升级失败，回滚到原始集群
+
+解决办法: 查看升级日志，排除错误原因后，重试
+
+GAUSS-52918: "Failed to record node upgrade step in table %s.%s."
+
+SQLSTATE:无
+
+错误原因: 没有找到GTM
+
+解决办法: 调用gs_om -t status -detail命令查询集群状态，确认GTM状态，如果集群中GTM状态异常，则需要重新安装集群或者调用温备方法修复该集群。
+
+GAUSS-52919: "Upgrade has already been committed but not finished commit."
+
+SQLSTATE:无
+
+错误原因: 升级失败
+
+解决办法: 请查看升级日志，排除错误原因，根据实际情况重试。
+
+GAUSS-52920: "Can not use grey upgrade option -continue before upgrade grey nodes."
+
+SQLSTATE:无
+
+错误原因: 全面升级后还原GUC参数失败
+
+解决办法: 请查看升级日志和GUC日志，排除原因，重新升级。
+
+GAUSS-52921: "Failed to query disk usage with gs_check tool."
+
+SQLSTATE:无
+
+错误原因: 不合法的升级类型
+
+解决办法: 请使用自动升级接口
+
+GAUSS-52922: "Disk usage exceeds %s, please clean up before upgrading."
+
+SQLSTATE:无
+
+错误原因: 记录升级步骤失败
+
+解决办法: 请确认临时文件目录的权限或是否存在。
+
+GAUSS-52923: "Inplace upgrade commit failed.%s"
+
+SQLSTATE:无
+
+错误原因: 记录升级状态失败
+
+解决办法: 请确认临时文件目录的权限或是否存在。
+
+GAUSS-52924: "The %s parameter are only supported in independent deployment mode."
+
+SQLSTATE:无
+
+错误原因: 升级状态文件中信息错误
+
+解决办法: 请确认是否修改升级备份文件，并尝试根据升级步骤恢复记录文件。
+
+GAUSS-52925: "Input upgrade type [%s] is not same with record upgrade type [%s]."
+
+SQLSTATE:无
+
+错误原因: 使用不正确的升级接口
+
+解决办法: 请使用自动升级接口或者自动回滚接口
+
+GAUSS-52926: "The step of upgrade should be digit."
+
+SQLSTATE:无
+
+错误原因: 升级步骤必须是一个数字。
+
+解决办法: 请确认升级备份文件是否被修改，并尝试恢复。
+
+GAUSS-52929: "Failed to check application version. Output: %s."
+
+SQLSTATE:无
+
+错误原因: 检查集群版本失败。
+
+解决办法: 请检查升级日志，确认各节点版本信息。
+
+GAUSS-52932: "There is no CN in the remaining old nodes."
+
+SQLSTATE:无
+
+错误原因: 旧集群中没有可用的CN实例。
+
+解决办法: 请检查升级日志，确认各节点实例信息。
+
+GAUSS-52933: "There is not a majority of %s on the remaining old nodes."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-52934: "Binary upgrade failed."
+
+SQLSTATE:无
+
+错误原因: 升级失败。
+
+解决办法: 请检查升级日志，或联系对应开发进行定位。
+
+GAUSS-52935: "Current upgrade version is not same with unfinished upgrade version record."
+
+SQLSTATE:无
+
+错误原因: 上次升级操作未完成（没有提交或回滚），本次意图升级到另一个版本。
+
+解决办法: 先完成上次升级操作的提交或回滚，再进行另一个版本的升级。
+
+GAUSS-52936: "Upgrade is not finished, cannot do another task."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/79-GAUSS-53000-GAUSS-53699.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/79-GAUSS-53000-GAUSS-53699.md
new file mode 100644
index 0000000000000000000000000000000000000000..b1ea1fcf13d26e24eea238b24183a6cee63dda70
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/79-GAUSS-53000-GAUSS-53699.md
@@ -0,0 +1,954 @@
+---
+title: GAUSS-53000 - GAUSS-53699
+summary: GAUSS-53000 - GAUSS-53699
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-53000 - GAUSS-53699
+
+<br/>
+
+## GAUSS-53000 - GAUSS-53099
+
+<br/>
+
+GAUSS-53000: The database user [%s] is not match with the old user [%s].
+
+SQLSTATE:无
+
+错误原因: 数据库用户和旧用户不匹配。
+
+解决办法: 检查输入的用户是正确。
+
+GAUSS-53001: The result of query table is incorrect: %s.
+
+SQLSTATE:无
+
+错误原因: 查询表的返回结果错误。
+
+解决办法: 检查数据库是否正常。
+
+GAUSS-53002: Failed to obtain SSD device.
+
+SQLSTATE:无
+
+错误原因: 检查SSD设备失败。
+
+解决办法: 检查是否安装固态硬盘(SSD)。
+
+GAUSS-53003: The checked item does not meet the standards.
+
+SQLSTATE:无
+
+错误原因: 检查项不符合标准。
+
+解决办法: 检查固态硬盘状态是否正常。
+
+GAUSS-53004: Failed to collect statistics on all nodes.
+
+SQLSTATE:无
+
+错误原因: 收集所有节点统计信息失败。
+
+解决办法: 检查数据库是否能正常使用。
+
+GAUSS-53005: Unable to obtain SSD disk on current node.
+
+SQLSTATE:无
+
+错误原因: 获取SSD失败。
+
+解决办法: 检查固态硬盘是否安装。
+
+GAUSS-53006: No DN instance uses data directory %s on %s.
+
+SQLSTATE:无
+
+错误原因: 没有DN实例数据目录。
+
+解决办法: 检查DN目录是否存在。
+
+GAUSS-53007: Failed to switch %s.
+
+SQLSTATE:无
+
+错误原因: 主备实例切换失败。
+
+解决办法: 根据CM日志分析处理。
+
+GAUSS-53008: The current node do not install SSD. Can not check SSD performance.
+
+SQLSTATE:无
+
+错误原因: 当前节点未安装固态硬盘(SSD)。
+
+解决办法: 安装并使用固态硬盘(SSD)。
+
+GAUSS-53009: Failed to format cu of directory: %s.
+
+SQLSTATE:无
+
+错误原因: 格式化列存储文件失败。
+
+解决办法: 根据pg_format_cu日志分析处理。
+
+GAUSS-53010: The function name of %s is not exist in the %s.
+
+SQLSTATE:无
+
+错误原因: 脚本中没有此方法。
+
+解决办法: 检查命令是否正确。
+
+GAUSS-53011: Failed to check %s.
+
+SQLSTATE:无
+
+错误原因: 检查失败。
+
+解决办法: 根据check日志分析处理。
+
+GAUSS-53012: Failed to insert pmk data to database.
+
+SQLSTATE:无
+
+错误原因: 检查失败。
+
+解决办法: 根据gs_checkperf工具日志分析处理。
+
+GAUSS-53013: "Failed to force failover."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-53014: "Performance jobs not enabled."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-53100 - GAUSS-53199
+
+<br/>
+
+GAUSS-53100: "[%s] is not supported in single cluster."
+
+SQLSTATE:无
+
+错误原因: 检查失败。
+
+解决办法: 单机部署不支持用户指定的接口。
+
+GAUSS-53101: "This interface is not supported in %s cluster.""
+
+SQLSTATE:无
+
+错误原因: 检查失败。
+
+解决办法: 当前集群不支持用户指定的接口。
+
+GAUSS-53102: "[%s] is not supported in express cluster."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-53103: "The single primary multi standby cluster does not support the product"" version '%s'."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-53104: "[%s] is not supported in single instance cluster."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-53200 - GAUSS-53299
+
+<br/>
+
+GAUSS-53200: "The number of standbys for each DN instance must be the same. Please set it."
+
+SQLSTATE:42501
+
+错误原因: 用户权限不足，无法连接到静态库。
+
+解决办法: 修改用户权限后，再次执行操作。
+
+GAUSS-53201: "The number of DN standbys and the AZ settings are incorrect. Please set it."
+
+SQLSTATE:22023
+
+错误原因: 磁盘空间不足。
+
+解决办法: 释放磁盘空间后，再次执行操作。
+
+GAUSS-53202: "The AZ information is incorrect. Please set it."
+
+SQLSTATE:42P25
+
+错误原因: 计划中无AGG算子。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-53203: "The number of ETCD in %s. Please set it."
+
+SQLSTATE:42601
+
+错误原因: AGG语法错误。
+
+解决办法: 修改查询语句后，再次执行操作。
+
+GAUSS-53204: "[%s] is not supported in single primary multistandby cluster."
+
+SQLSTATE:42P24
+
+错误原因: 该属性列不存在。
+
+解决办法: 更换属性列后，再次执行操作。
+
+GAUSS-53205: "The priority of %s must be higher than %s. Please set it."
+
+SQLSTATE:42P24
+
+错误原因: 列属性值超过了列最大长度。
+
+解决办法: 修改列属性值后，再次执行操作。
+
+GAUSS-53206: "The value of %s must be greater than 0 and less than 11. Please set it."
+
+SQLSTATE:01000
+
+错误原因: 用户名不存在，无法从hashtable中找到sql count。
+
+解决办法: 修改用户名后，再次执行操作。
+
+[GAUSS-53207]: "cannot convert abstime 'invalid' to timestamp"
+
+SQLSTATE:0A000
+
+错误原因: 无法将低精度abstime转换为timestamp。
+
+解决办法: 修改为有效输入后，再次执行操作。
+
+[GAUSS-53208]: "cannot convert infinity to numeric"
+
+SQLSTATE:0A000
+
+错误原因: 无法将无限值转换为numeric类型。
+
+解决办法: 修改为有效输入后，再次执行操作。
+
+[GAUSS-53209]: "cannot convert reltime 'invalid' to interval"
+
+SQLSTATE:0A000
+
+错误原因: 无法将reltime转换为时间间隔。
+
+解决办法: 修改为有效输入后，再次执行操作。
+
+[GAUSS-53210]: "can't initialize bitmap index scans using unusable index '%s'"
+
+SQLSTATE:XX002
+
+错误原因: 索引无效，无法初始化bitmap索引扫描。
+
+解决办法: 修改为有效索引后，再次执行操作。
+
+[GAUSS-53211]: "can't initialize bitmap index scans using unusable local index '%s'"
+
+SQLSTATE:XX002
+
+错误原因: 本地索引无效，无法初始化bitmap索引扫描。
+
+解决办法: 修改为有效索引后，再次执行操作。
+
+[GAUSS-53212]: "can't initialize index scans using unusable index '%s'"
+
+SQLSTATE:XX002
+
+错误原因: 索引无效，无法初始化索引扫描。
+
+解决办法: 修改为有效索引后，再次执行操作。
+
+[GAUSS-53213]: "can't initialize index scans using unusable local index '%s'"
+
+SQLSTATE:XX002
+
+错误原因: 本地索引无效，无法初始化索引扫描。
+
+解决办法: 修改为有效索引后，再次执行操作。
+
+[GAUSS-53214]: "can't initialize index-only scans using unusable index '%s'"
+
+SQLSTATE:XX002
+
+错误原因: 索引无效，无法初始化全索引扫描。
+
+解决办法: 修改为有效索引后，再次执行操作。
+
+[GAUSS-53215]: "can't initialize index-only scans using unusable local index '%s'"
+
+SQLSTATE:XX002
+
+错误原因: 本地索引无效，无法初始化全索引扫描。
+
+解决办法: 修改为有效索引后，再次执行操作。
+
+[GAUSS-53216]: "cgroup is not initialized or group name %s is invalid!"
+
+SQLSTATE:42P26
+
+错误原因: cgroup无法初始化或groupname不合法。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+[GAUSS-53217]: "cgroup is not initialized!"
+
+SQLSTATE:42704
+
+错误原因: cgroup无法初始化。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+[GAUSS-53218]: "class group %s doesn't exist!"
+
+SQLSTATE:42704
+
+错误原因: cgroup不存在。
+
+解决办法: 创建cgroup后，再次执行操作。
+
+[GAUSS-53219]: "component in parameter 'dynamic_library_path' is not an absolute path"
+
+SQLSTATE:42602
+
+错误原因: dynamic_library_path中的路径不是绝对路径。
+
+解决办法: 修改dynamic_library_path中路径为绝对路径。
+
+[GAUSS-53220]: "conflicting key value violates exclusion constraint '%s'"
+
+SQLSTATE:23P01
+
+错误原因: 键值冲突，违反排除约束。
+
+解决办法: 修改键值后，再次执行操作。
+
+[GAUSS-53221]: "could not convert format string from UTF-8: error code %lu"
+
+SQLSTATE:22021
+
+错误原因: 无法将UTF-8字符格式化。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+[GAUSS-53222]: "could not create exclusion constraint '%s'"
+
+SQLSTATE:23P01
+
+错误原因: 无法创建排除约束。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+[GAUSS-53223]: "could not create locale '%s': %m"
+
+SQLSTATE:22023
+
+错误原因: 无法创建数据库字符集。
+
+解决办法: 修改使用已经存在的数据库字符集。
+
+[GAUSS-53224]: "could not create unique index '%s'"
+
+SQLSTATE:23505
+
+错误原因: 无法创建唯一索引列。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+[GAUSS-53225]: "internal function '%s' is not in internal lookup table"
+
+SQLSTATE:XX005
+
+错误原因: 无法在函数查找表内找到函数定义。
+
+解决办法: 检查SQL语句中的函数是否有效。
+
+[GAUSS-53226]: "invalid address family in external '%s' value"
+
+SQLSTATE:22P03
+
+错误原因: 非法的网络地址族。
+
+解决办法: 建议检查输入的网络地址是否符合网络地址的格式。
+
+[GAUSS-53227]: "invalid attribute name"
+
+SQLSTATE:42602
+
+错误原因: 非法属性名。
+
+解决办法: 检查输入字符串。
+
+[GAUSS-53228]: "invalid bits in external '%s' value"
+
+SQLSTATE:22P03
+
+错误原因: 非法的网络地址族。
+
+解决办法: 建议检查输入的网络地址是否符合网络地址的格式。
+
+[GAUSS-53229]: "invalid cidr value: '%s'"
+
+SQLSTATE:22P02
+
+错误原因: 非法的网络地址族。
+
+解决办法: 建议检查输入的网络地址是否符合网络地址的格式。
+
+[GAUSS-53230]: "invalid digit in external 'numeric' value"
+
+SQLSTATE:22P03
+
+错误原因: 非法的Numeric输入。
+
+解决办法: 请检查数据中是否包含非法的Numeric输入。关于Numeric的合法格式请参考zh-cn_topic_0274503547.html。
+
+[GAUSS-53231]: "invalid external 'cidr' value"
+
+SQLSTATE:22P03
+
+错误原因: 非法的网络地址。
+
+解决办法: 建议检查输入的网络地址是否符合网络地址的格式。
+
+[GAUSS-53232]: "invalid input syntax for %s: '%s'"
+
+SQLSTATE:22P02
+
+错误原因: 非法的网络地址。
+
+解决办法: 建议检查输入的网络地址是否符合网络地址的格式。
+
+[GAUSS-53233]: "invalid length in external '%s' value"
+
+SQLSTATE:22P03
+
+错误原因: 非法的网络地址。
+
+解决办法: 建议检查输入的网络地址是否符合网络地址的格式。
+
+[GAUSS-53234]: "invalid name of logical cluster: NULL or ""
+
+SQLSTATE:42602
+
+错误原因: 非法的逻辑集群名。
+
+解决办法: 建议检查输入的逻辑集群或其名称是否为空。
+
+[GAUSS-53235]: "invalid name of memory context: NULL or ""
+
+SQLSTATE:42602
+
+错误原因: 非法的内存上下文名。
+
+解决办法: 建议检查输入的内存上下文或其名称是否为空。
+
+[GAUSS-53236]: "invalid name of resource pool: NULL or ""
+
+SQLSTATE:42602
+
+错误原因: 非法的资源池名称。
+
+解决办法: 建议检查输入的资源池或其名称是否为空。
+
+[GAUSS-53237]: "invalid octet value in 'macaddr' value: '%s'"
+
+SQLSTATE:22003
+
+错误原因: 语法错误。
+
+解决办法: 修改SQL。
+
+[GAUSS-53238]: "invalid regexp option: '%c'"
+
+SQLSTATE:22023
+
+错误原因: 非法的regexp转换类型。
+
+解决办法: 检查输入参数。
+
+[GAUSS-53239]: "invalid sign in external 'numeric' value"
+
+SQLSTATE:22P03
+
+错误原因: 非法的Numeric输入。
+
+解决办法: 请检查数据中是否包含非法的Numeric输入。关于Numeric的合法格式请参考zh-cn_topic_0274503547.html。
+
+[GAUSS-53240]: "invalid status in external 'tinterval' value"
+
+SQLSTATE:22P03
+
+错误原因: 输入的字符串中获得的internal错误状态与数据对应的状态不一致。
+
+解决办法: 检查输入字符串。
+
+[GAUSS-53241]: "invalid time zone name: '%s'"
+
+SQLSTATE:22023
+
+错误原因: 非法的时区名。
+
+解决办法: 建议检查时区名是否合法。
+
+[GAUSS-53242]: "kill backend is prohibited during online expansion."
+
+SQLSTATE:42501
+
+错误原因: 禁止联机扩展时杀掉backend进程。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+[GAUSS-53243]: "malformed range literal: '%s'"
+
+SQLSTATE:22P02
+
+错误原因: 语法错误。
+
+解决办法: 检查SQL语句。
+
+[GAUSS-53244]: "malformed record literal: '%s'"
+
+SQLSTATE:22P02
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+[GAUSS-53245]: "more than one function named '%s'"
+
+SQLSTATE:42725
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+[GAUSS-53246]: "multidimensional arrays must have array "expressions with matching dimensions"
+
+SQLSTATE:2202E
+
+错误原因: 多维的数组必须具有与维度相匹配的数组表达式。
+
+解决办法: 检查输入字符串。
+
+[GAUSS-53247]: "must be system admin to cancel invalid queries running in all server processes"
+
+SQLSTATE:42501
+
+错误原因: 用户没有权限取消服务端进程的非法查询。
+
+解决办法: 切换为系统管理员，重新取消非法查询。
+
+[GAUSS-53248]: "must be system admin to reset bad block statistics counters"
+
+SQLSTATE:42501
+
+错误原因: 用户没有权限重置损坏的块统计信息。
+
+解决办法: 切换为系统管理员，重新重置损坏的块统计信息。
+
+[GAUSS-53249]: "must be system admin to view the global information"
+
+SQLSTATE:42501
+
+错误原因: 用户没有权限查看所有表的全局分布信息。
+
+解决办法: 切换为系统管理员，重新查看表的全局信息。
+
+[GAUSS-53250]: "unrecognized paramkind: %d"
+
+SQLSTATE:XX004
+
+错误原因: 未知参数类型。
+
+解决办法: 检查相关执行计划参数。
+
+[GAUSS-53251]: "unrecognized reset target: '%s'"
+
+SQLSTATE:22023
+
+错误原因: 未知重置目标信息。
+
+解决办法: 检查重置目标信息名称。
+
+[GAUSS-53252]: "unrecognized XML operation"
+
+SQLSTATE:XX004
+
+错误原因: 未知XML操作。
+
+解决办法: 检查XML内容信息。
+
+[GAUSS-53253]: "unsupported reference to system column %d in FieldSelect"
+
+SQLSTATE:42P10
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+[GAUSS-53254]: "update or delete on table '%s' violates foreign key constraint '%s' on table '%s'"
+
+SQLSTATE:23503
+
+错误原因: 更新或删除操作违反外键约束。
+
+解决办法: 检查相关语句及表外键信息。
+
+[GAUSS-53255]: "value '%s' is out of range for type %s"
+
+SQLSTATE:22003
+
+错误原因: 数据值超出数据类型有效范围。
+
+解决办法: 检查相关数据值及数据类型。
+
+[GAUSS-53256]: "value for domain %s violates check constraint '%s'"
+
+SQLSTATE:23514
+
+错误原因: 域值违反检查约束。
+
+解决办法: 检查相关域值。
+
+[GAUSS-53257]: "WindowFunc found in non-WindowAgg plan node"
+
+SQLSTATE:42P20
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+[GAUSS-53258]: "workload group %s doesn't exist!"
+
+SQLSTATE:42704
+
+错误原因: cgroup控制信息未定义。
+
+解决办法: 检查cgroup配置文件。
+
+[GAUSS-53259]: "wrong pg_constraint entry for trigger '%s' on table '%s'"
+
+SQLSTATE:23514
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+[GAUSS-53260]: "zero-length component in parameter 'dynamic_library_path'"
+
+SQLSTATE:42602
+
+错误原因: 动态库路径异常。
+
+解决办法: 检查动态库路径。
+
+<br/>
+
+## GAUSS-53300 - GAUSS-53399
+
+<br/>
+
+GAUSS-53300: "The current product version '%s' does not support the license " "register/unregister operation."
+
+SQLSTATE: 无
+
+错误原因: 当前产品版本不支持License注册和反注册操作。
+
+解决办法: 目前License注册和反注册操作只支持GaussDB200产品，在其它产品版本中不支持该操作。
+
+GAUSS-53301: "The license control files are not consistent on the cluster."
+
+SQLSTATE: 无
+
+错误原因: 集群中的License文件不一致。
+
+解决办法: 联系运维人员处理License不一致的问题。
+
+GAUSS-53302: "The current cluster does not apply the license control, please upgrade it" " first."
+
+SQLSTATE: 无
+
+错误原因: 当前数据库版本不支持License管理或集群所有节点License文件丢失。
+
+解决办法: 如果用户未从FusionInsight Manager中注册任何License，则代表用户必须升级数据库版本来支持License管理，否则需要联系运维人员处理License全部丢失的问题。
+
+GAUSS-53303: "The DWS cluster does not support the license register/unregister operation."
+
+SQLSTATE: 无
+
+错误原因: 云上DWS集群不支持License注册和反注册操作。
+
+解决办法: 目前License注册和反注册操作只支持GaussDB200产品，在其它产品版本中不支持该操作。
+
+GAUSS-53304: "Can not register the enabled features."
+
+SQLSTATE: 无
+
+错误原因: 不能注册已经启用的特性。
+
+解决办法: 更正命令行参数后重新执行注册操作。
+
+GAUSS-53304: "Can not un-register the disabled features."
+
+SQLSTATE: 无
+
+错误原因: 不能反注册已经禁用的特性。
+
+解决办法: 更正命令行参数后重新执行反注册操作。
+
+GAUSS-53306: "Can not register the unsupported features of the product version '%s'."
+
+SQLSTATE: 无
+
+错误原因: 不能注册指定产品版本不支持的特性。
+
+解决办法: 更正命令行参数后重新执行注册操作。
+
+GAUSS-53307: "No need to un-register the unsupported features of the product version '%s'."
+
+SQLSTATE: 无
+
+错误原因: 不需要反注册指定产品版本不支持的特性。
+
+解决办法: 更正命令行参数后重新执行反注册操作。
+
+<br/>
+
+## GAUSS-53400 - GAUSS-53499
+
+<br/>
+
+GAUSS-53400: "Roach ETCD term operate failed."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-53401: "Roach delete/clean operate failed, Failed to clean %s"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-53402: "Get %s cluster infomation/env failed, %s"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-53403: "Cluster balance check failed"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 首先定位是不是集群down，如果不是，请联系技术支持工程师提供技术支持。
+
+GAUSS-53404: "backup key %s does not exist"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-53500 - GAUSS-53599
+
+<br/>
+
+GAUSS-53500: "Relation %s does not exist."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-53501: "Connect to server failed, connection refused"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-53502: "Please check database status"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-53503: "There is no coordinator inst in this host"
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-53504: "There is no %s files: please check start-time and end-time."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-53505: "There is no log files: please check cluster info."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-53506: "Failed to mkdir."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-53507: "Failed to execute %s command."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-53508: "Core pattern is not core-e-p-t."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-53509: "There is no core files: please check core file name pattern is core-e-p-t."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-53510: "Please check db status or database name."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-53511: "There is no %s process."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-53512: "Gstack command not found."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-53513: "Schema '%s' is not in white list."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-53514: "Relation '%s' does not belong to '%s' schema."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-53515: "Database content '%s' is invalid, only support 'schema.relation'."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-53600 - GAUSS-53699
+
+<br/>
+
+GAUSS-53600: "CA password must contain at least eight characters."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-53601: "CA password cannot contain %s."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-53602: "CA password is too simple."
+
+SQLSTATE: 无
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/8-GAUSS-00701-GAUSS-00800.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/8-GAUSS-00701-GAUSS-00800.md
new file mode 100644
index 0000000000000000000000000000000000000000..e11c2148daa2ab2a287b05c61835b0d9cbeb17e7
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/8-GAUSS-00701-GAUSS-00800.md
@@ -0,0 +1,764 @@
+---
+title: GAUSS-00701 - GAUSS-00800
+summary: GAUSS-00701 - GAUSS-00800
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-00701 - GAUSS-00800
+
+<br/>
+
+## GAUSS-00701 - GAUSS-00710
+
+<br/>
+
+### GAUSS-00701: "cannot rename inherited constraint '%s'"
+
+SQLSTATE: 42P16
+
+错误原因: 修改继承的约束名。
+
+解决办法: 禁止修改继承的约束名。
+
+### GAUSS-00702: "relation '%s' already exists"
+
+SQLSTATE: 42P07
+
+错误原因: relation已存在。
+
+解决办法: 检查是否存在重名的relation。
+
+### GAUSS-00703: "GTM error, could not rename sequence"
+
+SQLSTATE: 08006
+
+错误原因: GTM出错，GTM中重名失败。
+
+解决办法: 请使用gs_om -t status -detail命令检查GTM是否状态正常。
+
+### GAUSS-00706: "partition '%s' of relation '%s' already exists"
+
+SQLSTATE: 42P07
+
+错误原因: 同名的表分区已存在。
+
+解决办法: 检查同名的分区是否已经存在。
+
+### GAUSS-00710: "cache lookup failed for partition %u of relation %u"
+
+SQLSTATE: 42704
+
+错误原因: 提示的partition查找失败。
+
+解决办法: 系统异常，请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-00711 - GAUSS-00720
+
+<br/>
+
+### GAUSS-00711: "cannot %s '%s' because it is being used by active queries in this session"
+
+SQLSTATE: 55006
+
+错误原因: 需要进行修改的对象正在被使用。
+
+解决办法: 可以等当前活跃的查询结束再进行重试。
+
+### GAUSS-00712: "cannot %s '%s' because it has pending trigger events"
+
+SQLSTATE: 55006
+
+错误原因: 修改表时发现有挂起的触发器事件。
+
+解决办法: 等待挂起的触发器事件处理完成后再进行重试。
+
+### GAUSS-00713: "Un-support feature"
+
+SQLSTATE: 0A000
+
+错误原因: 不支持的特性。
+
+解决办法: 不建议使用。
+
+### GAUSS-00714: "unrecognized alter table type: %d"
+
+SQLSTATE: XX000
+
+错误原因: 表更改类型不支持。
+
+解决办法: 检查表更改类型是否支持。
+
+### GAUSS-00715: "Incompatible operation with data redistribution"
+
+SQLSTATE: 54001
+
+错误原因: ALTER操作与数据重分布不兼容。
+
+解决办法: 使用与数据重分布兼容的ALTER操作。
+
+### GAUSS-00716: "cannot set with oids on partitioned table"
+
+SQLSTATE: 0A000
+
+错误原因: 修改分区表的oids。
+
+解决办法: 请勿修改分区表的oids。
+
+### GAUSS-00717: "cannot set without oids on partitioned table"
+
+SQLSTATE: 0A000
+
+错误原因: 修改分区表的oids。
+
+解决办法: 请勿修改分区表的oids。
+
+### GAUSS-00718: "cannot rewrite temporary tables of other sessions"
+
+SQLSTATE: 0A000
+
+错误原因: 重写其他session的临时表。
+
+解决办法: 请勿重写其他session的临时表。
+
+### GAUSS-00719: "cannot rewrite system relation '%s'"
+
+SQLSTATE: 0A000
+
+错误原因: 重写系统表。
+
+解决办法: 请勿重写系统表。
+
+<br/>
+
+## GAUSS-00721 - GAUSS-00730
+
+<br/>
+
+### GAUSS-00721: "column '%s' contains null values"
+
+SQLSTATE: 23502
+
+错误原因: 不允许为空的列中包含空值。
+
+解决办法: 检查是否存在非空约束的冲突。
+
+### GAUSS-00722: "check constraint '%s' is violated by some row"
+
+SQLSTATE: 23514
+
+错误原因: 一些行违反了check约束。
+
+解决办法: 检查是否存在check约束冲突。
+
+### GAUSS-00723: "cannot alter type '%s' because column '%s.%s' uses it"
+
+SQLSTATE: 0A000
+
+错误原因: 列类型不允许修改，因为有其它列依赖。
+
+解决办法: 确认是否存在列的依赖，如果是，需要删除对应对象后进行列类型修改。
+
+### GAUSS-00724: "cannot alter foreign table '%s' because column '%s.%s' uses its row type"
+
+SQLSTATE: 0A000
+
+错误原因: 修改外部表失败，有列正在使用它的行类型。
+
+解决办法: 确认是否存在列的依赖，如果是，需要删除对应对象后进行表修改。
+
+### GAUSS-00725: "cannot alter table '%s' because column '%s.%s' uses its row type"
+
+SQLSTATE: 0A000
+
+错误原因: 修改表失败，有列正在使用它的行类型。
+
+解决办法: 确认是否存在列的依赖，如果是，需要删除对应对象后进行表修改。
+
+### GAUSS-00726: "cannot alter type '%s' because it is the type of a typed table"
+
+SQLSTATE: 2BP01
+
+错误原因: 修改类型失败，它是一个type表的类型。
+
+解决办法: 使用ALTER … CASCADE同时修改type表。
+
+### GAUSS-00727: "type %s is not a composite type"
+
+SQLSTATE: 42809
+
+错误原因: CREATE TABLE OF/ALTER TABLE OF的类型不是复合类型。
+
+解决办法: 使用复合类型重试。
+
+### GAUSS-00728: "cannot add column to typed table"
+
+SQLSTATE: 42809
+
+错误原因: 为类型表增加列。
+
+解决办法: 不允许为类型表增加列。
+
+### GAUSS-00729: "type '%s' is not supported in column store"
+
+SQLSTATE: 0A000
+
+错误原因: 列式存储不支持此字段类型。
+
+解决办法: 请选择合适字段类型，再次执行操作。
+
+### GAUSS-00730: "default value cannot reference to a column"
+
+SQLSTATE: 42809
+
+错误原因: 默认值不能用于一个列。
+
+解决办法: 检查默认值是否包含在双引号里面。
+
+<br/>
+
+## GAUSS-00731 - GAUSS-00740
+
+<br/>
+
+### GAUSS-00731: "child table '%s' has different type for column '%s'"
+
+SQLSTATE: 42804
+
+错误原因: AddColumn操作时，向parent添加一列，检测到child table与添加列有相同的列名，但是类型不一样，本操作不能执行。
+
+解决办法: 建议修改添加列类型，使其与child table有相同的类型。
+
+### GAUSS-00732: "child table '%s' has different collation for column '%s'"
+
+SQLSTATE: 42P21
+
+错误原因: AddColumn操作时，向parent添加一列，检测到child table与添加列有相同的列名，但是排序方式(collation)不一样，本操作不能执行。
+
+解决办法: 建议修改添加列排序方式(collation)，使其与child table有相同的排序方式。
+
+### GAUSS-00733: "child table '%s' has a conflicting '%s' column"
+
+SQLSTATE: 42804
+
+错误原因: AddColumn操作时，向parent添加一列，检测到child table与添加列有相同的列名，child table与新添加列冲突，本操作不能执行。
+
+解决办法: 建议修改添加列，避免与child table发生冲突。
+
+### GAUSS-00735: "column must be added to child tables too"
+
+SQLSTATE: 42P16
+
+错误原因: AddColumn操作时，向parent table添加一列，新添列必须添加到child table中，否则不能执行。
+
+解决办法: 建议将向parent table新添列递归的添加到child table中。
+
+### GAUSS-00736: "column '%s' of relation '%s' already exists"
+
+SQLSTATE: 42701
+
+错误原因: 当向关系表添加列或更改列名时，发现该表中已经存在该列名。
+
+解决办法: 重新指定列名。
+
+### GAUSS-00737: "cannot alter system column '%s'"
+
+SQLSTATE: 0A000
+
+错误原因: ALTER TABLE ALTER COLUMN DROP操作时，系统表的列不能被修改。
+
+解决办法: 建议取消本操作，系统表的列不能被修改。
+
+### GAUSS-00738: "column '%s' is in a primary key"
+
+SQLSTATE: 42P16
+
+错误原因: ALTER TABLE ALTER COLUMN DROP操作时，表的主键不能被修改。
+
+解决办法: 建议取消本操作，表的主键不能被修改。
+
+### GAUSS-00739: "'%s' is not a table, index, or foreign table"
+
+SQLSTATE: 42809
+
+错误原因: ALTER TABLE ALTER COLUMN SET STATISTICS操作时，修改的目标不是表，索引或者外表，本操作不能执行。
+
+解决办法: 建议将修改设置为表、索引或外表，或取消本操作。
+
+### GAUSS-00740: "statistics target %d is too low"
+
+SQLSTATE: 22023
+
+错误原因: ALTER TABLE ALTER COLUMN SET STATISTICS操作时，统计目标值过小。
+
+解决办法: 建议将统计目标值限制在有效范围内。
+
+<br/>
+
+## GAUSS-00741 - GAUSS-00750
+
+<br/>
+
+### GAUSS-00741: "invalid storage type '%s'"
+
+SQLSTATE: 22023
+
+错误原因: ALTER TABLE ALTER COLUMN SET STORAGE操作时，目标为无效的数据存储类型。
+
+解决办法: 建议将操作目标更改为有效的存储类型。
+
+### GAUSS-00742: "column data type %s can only have storage PLAIN"
+
+SQLSTATE: 0A000
+
+错误原因: ALTER TABLE ALTER COLUMN SET STORAGE操作时，列存储类型只能设置为PLAIN类型。
+
+解决办法: 将建议将列数据存储类型设置PLAIN类型。
+
+### GAUSS-00743: "cannot drop column from typed table"
+
+SQLSTATE: 42809
+
+错误原因: ALTER TABLE DROP COLUMN操作时，类型表的列不能被删除。
+
+解决办法: 不支持删除类型表的列，建议取消本操作。
+
+### GAUSS-00745: "cannot drop system column '%s'"
+
+SQLSTATE: 0A000
+
+错误原因: ALTER TABLE DROP COLUMN操作时，系统表的列不能被删除。
+
+解决办法: 不支持删除系统表的列，建议取消本操作。
+
+### GAUSS-00747: "cache lookup failed for attribute '%s' of relation %u"
+
+SQLSTATE: XX000
+
+错误原因: 提示的列查找失败。
+
+解决办法: 系统异常，请联系技术支持工程师提供技术支持。
+
+### GAUSS-00748: "relation %u has non-inherited attribute '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 被继承表没有相应的继承列。
+
+解决办法: 系统异常，请联系技术支持工程师提供技术支持。
+
+### GAUSS-00749: "index '%s' is not unique"
+
+SQLSTATE: XX000
+
+错误原因: 添加unique约束涉及的index不带unique属性。
+
+解决办法: 系统异常，请联系技术支持工程师提供技术支持。
+
+### GAUSS-00750: "constraint '%s' for relation '%s' already exists"
+
+SQLSTATE: 42710
+
+错误原因: ALTER TABLE ADD CONSTRAINT操作时，新增约束已经存在，不能执行。
+
+解决办法: 新增约束已经存在，建议更改新增约束。
+
+<br/>
+
+## GAUSS-00751 - GAUSS-00760
+
+<br/>
+
+### GAUSS-00751: "cluster key for relation '%s' already exists"
+
+SQLSTATE: 42710
+
+错误原因: ALTER TABLE ADD CONSTRAINT操作时，关系表的cluster key已经存在，不能执行。
+
+解决办法: 新增约束已经存在，建议更改新增约束。
+
+### GAUSS-00753: "referenced relation '%s' is not a table"
+
+SQLSTATE: 42809
+
+错误原因: 为表添加外键限制时，外键约束的参考表必须是普通表。
+
+解决办法: 外键约束的参考表只能是普通表。
+
+### GAUSS-00754: "Invalid FOREIGN KEY constraints"
+
+SQLSTATE: 42809
+
+错误原因: 分区表可以创建外键约束，但是外键约束的参考表只能为普通表，不能为分区表。
+
+解决办法: 分区表可以创建外键约束，但是外键约束的参考表不能为分区表，建议修改外键约束的参照表。
+
+### GAUSS-00755: "constraints on permanent tables may reference only permanent tables"
+
+SQLSTATE: 42P16
+
+错误原因: 普通表的外键约束限制只能参照普通表。
+
+解决办法: 建议修改外键约束限制为普通表。
+
+### GAUSS-00756: "constraints on unlogged tables may reference only permanent or unlogged tables"
+
+SQLSTATE: 42P16
+
+错误原因: unlogged表的外键约束限制只能参照普通表或unlogged表。
+
+解决办法: unlogged表的约束限制只能参照普通表或unlogged表。
+
+### GAUSS-00757: "constraints on temporary tables may reference only temporary tables"
+
+SQLSTATE: 42P16
+
+错误原因: 临时表的外键约束限制只能参照表临时表。
+
+解决办法: 建议更改外键约束限制或者取消本操作。
+
+### GAUSS-00758: "constraints on temporary tables must involve temporary tables of this session"
+
+SQLSTATE: 42P16
+
+错误原因: 临时表的外键约束必需参照是本地临时表。
+
+解决办法: 建议更改外键约束限制或者取消本操作。
+
+### GAUSS-00759: "number of referencing and referenced columns for foreign key disagree"
+
+SQLSTATE: 42830
+
+错误原因: 为表添加外键约束时，被约束的字段数目需要和被引用的字段数目相同。
+
+解决办法: 建议更改外键约束操作，使被约束的字段数目与被引用的字段数目相同。
+
+### GAUSS-00760: "only b-tree indexes are supported for foreign keys"
+
+SQLSTATE: XX000
+
+错误原因: 外键对应主键的索引不是b-tree索引。
+
+解决办法: 检查主键唯一约束索引是否是b-tree索引。
+
+<br/>
+
+## GAUSS-00761 - GAUSS-00770
+
+<br/>
+
+### GAUSS-00761: "missing operator %d(%u,%u) in opfamily %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00762: "foreign key constraint '%s' cannot be implemented"
+
+SQLSTATE: 42804
+
+错误原因: 为表添加外键约束时，被约束的字段类型需要和被引用的字段类型相同。
+
+解决办法: 建议更改外键约束操作，使被约束的字段类型与被引用的字段类型相同。
+
+### GAUSS-00763: "Cannot create foreign key whose evaluation cannot be enforced to remote nodes"
+
+SQLSTATE: 0A000
+
+错误原因: 为表添加外键约束时，无法引用到远程节点。
+
+解决办法: 无法创建引用到远程节点的外键约束，建议取消本操作。
+
+### GAUSS-00764: "constraint '%s' of relation '%s' does not exist"
+
+SQLSTATE: 42704
+
+错误原因: ALTER TABLE VALIDATE CONSTRAINT操作时，该表的约束不存在。
+
+解决办法: 建议更改为已经存在的约束，或者取消本操作。
+
+### GAUSS-00765: "constraint '%s' of relation '%s' is not a foreign key or check constraint"
+
+SQLSTATE: 42809
+
+错误原因: ALTER TABLE VALIDATE CONSTRAINT操作时，该关系约束不是外键或CHECK CONSTRAINT。
+
+解决办法: 建议更改此操作，或取消本操作。
+
+### GAUSS-00766: "constraint must be validated on child tables too"
+
+SQLSTATE: 42P16
+
+错误原因: ALTER TABLE VALIDATE CONSTRAINT操作时，parent table添加的约束同样应添加到child table上。
+
+解决办法: 建议对parent table添加的约束同样添加到child table上。
+
+### GAUSS-00767: "column '%s' referenced in foreign key constraint does not exist"
+
+SQLSTATE: 42703
+
+错误原因: 关系表外键约束的参考列不存在。
+
+解决办法: 建议更改本外键约束。
+
+### GAUSS-00768: "cannot have more than %d keys in a foreign key"
+
+SQLSTATE: 54011
+
+错误原因: 外键的参照列数目超过32。
+
+解决办法: 建议限制外键参照列的数目。
+
+### GAUSS-00769: "cannot use a deferrable primary key for referenced table '%s'"
+
+SQLSTATE: 55000
+
+错误原因: GetPrimaryKey操作，deferrable primary key不能执行此操作。
+
+解决办法: 建议取消本操作。
+
+### GAUSS-00770: "there is no primary key for referenced table '%s'"
+
+SQLSTATE: 42704
+
+错误原因: GetPrimaryKey操作，被参考表没有主键。
+
+解决办法: 建议取消本操作。
+
+<br/>
+
+## GAUSS-00771 - GAUSS-00780
+
+<br/>
+
+### GAUSS-00771: "cannot use a deferrable unique constraint for referenced table '%s'"
+
+SQLSTATE: 55000
+
+错误原因: 外键不能依赖deferrable unique constraint。
+
+解决办法: 建议更改外键依赖。
+
+### GAUSS-00772: "there is no unique constraint matching given keys for referenced table '%s'"
+
+SQLSTATE: 42830
+
+错误原因: 外键依赖表的键不满足唯一性约束。
+
+解决办法: 建议更改外键依赖。
+
+### GAUSS-00773: "could not find cast from %u to %u"
+
+SQLSTATE: XX000
+
+错误原因: 找不到类型之间的转换方式。
+
+解决办法: 查找pg_cast系统表是否有对应的类型转换方式，如果没有请联系技术支持工程师提供技术支持。
+
+### GAUSS-00774: "null conbin for constraint %u"
+
+SQLSTATE: XX000
+
+错误原因: 约束属性为空。
+
+解决办法: 系统表异常，请联系技术支持工程师提供技术支持。
+
+### GAUSS-00775: "unrecognized FK action type: %d"
+
+SQLSTATE: XX000
+
+错误原因: 外键触发器类型不存在。
+
+解决办法: 检查对应的外键触发器类型。
+
+### GAUSS-00776: "cannot drop inherited constraint '%s' of relation '%s'"
+
+SQLSTATE: 42P16
+
+错误原因: ALTER TABLE DROP CONSTRAINT操作，不能删除继承的约束关系。
+
+解决办法: 不能删除继承的约束，建议更改本操作。
+
+### GAUSS-00777: "relation %u has non-inherited constraint '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 被继承表没有相应的继承约束。
+
+解决办法: 系统表异常，请联系技术支持工程师提供技术支持。
+
+### GAUSS-00778: "cannot alter column type of typed table"
+
+SQLSTATE: 42809
+
+错误原因: ALTER COLUMN TYPE操作，不能更改类型表的列类型。
+
+解决办法: 不能更改类型表的列类型，建议更改本操作。
+
+### GAUSS-00779: "cannot alter inherited column '%s'"
+
+SQLSTATE: 42P16
+
+错误原因: ALTER COLUMN TYPE操作，不能更改继承表的列的类型。
+
+解决办法: 不能更改类型表的列类型，建议更改本操作。
+
+### GAUSS-00780: "cache lookup failed for pgxc_class %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+<br/>
+
+## GAUSS-00781 - GAUSS-00790
+
+<br/>
+
+### GAUSS-00781: "cannot alter data type of distribute column"
+
+SQLSTATE: 0A000
+
+错误原因: ALTER COLUMN TYPE操作，不能修改表的分布列的类型。
+
+解决办法: 不能更改类型表的列类型，建议更改本操作。
+
+### GAUSS-00784: "cannot use subquery in transform expression"
+
+SQLSTATE: 0A000
+
+错误原因: ALTER COLUMN TYPE操作，转换表达式不能包含子查询。
+
+解决办法: 转换表达式不能包含子查询，建议更改本操作。
+
+### GAUSS-00785: "cannot use aggregate function in transform expression"
+
+SQLSTATE: 42803
+
+错误原因: ALTER COLUMN TYPE操作，转换表达式不能使用聚合函数。
+
+解决办法: 转换表达式不支持聚合函数，建议更改本操作。
+
+### GAUSS-00786: "cannot use window function in transform expression"
+
+SQLSTATE: 42P20
+
+错误原因: ALTER COLUMN TYPE操作，转换表达式不能使用window函数。
+
+解决办法: 转换表达式不支持window函数，建议更改本操作。
+
+### GAUSS-00788: "type of inherited column '%s' must be changed in child tables too"
+
+SQLSTATE: 42P16
+
+错误原因: ALTER COLUMN TYPE操作，当parent table列的类型改变时，child table列类型也要随之改变。
+
+解决办法: 建议语句中指明子表随父表的变化递归变化。
+
+### GAUSS-00789: "cannot alter data type of partitioning column '%s'"
+
+SQLSTATE: 0A000
+
+错误原因: ALTER COLUMN TYPE操作，不能更改分区表的列类型。
+
+解决办法: 分区表不支持更改列类型，建议更改本操作。
+
+### GAUSS-00790: "cannot alter type of column '%s' twice"
+
+SQLSTATE: 0A000
+
+错误原因: ALTER COLUMN TYPE操作，不能同时两次更改某一列类型。
+
+解决办法: 不支持同时两次更改列类型，建议更改本操作。
+
+<br/>
+
+## GAUSS-00791 - GAUSS-00800
+
+<br/>
+
+### GAUSS-00791: "default for column '%s' cannot be cast automatically to type %s"
+
+SQLSTATE: 42804
+
+错误原因: ALTER COLUMN TYPE操作，默认表达式不支持自动转换某类型。
+
+解决办法: 默认表达式不支持自动转换某类型，建议更改本操作。
+
+### GAUSS-00792: "cannot alter type of a pinned column"
+
+SQLSTATE: XX000
+
+错误原因: 该列被其它对象依赖，不允许更改类型。
+
+解决办法: 查找对象被依赖的原因，去除依赖后进行类型更改。
+
+### GAUSS-00793: "unexpected object depending on column: %s"
+
+SQLSTATE: XX000
+
+错误原因: 依赖类型对象不存在。
+
+解决办法: 系统表异常，请联系技术支持工程师提供技术支持。
+
+### GAUSS-00794: "cannot alter type of a column used by a view or rule"
+
+SQLSTATE: 0A000
+
+错误原因: ALTER COLUMN TYPE操作，不能通过视图或者规则更改列类型。
+
+解决办法: 视图和规则不支持更改列类型，建议更改本操作。
+
+### GAUSS-00795: "cannot alter type of a column used in a trigger definition"
+
+SQLSTATE: 0A000
+
+错误原因: ALTER COLUMN TYPE操作，触发器定义中不能更改列类型。
+
+解决办法: 触发器定义不能更改列类型，建议更改本操作。
+
+### GAUSS-00796: "unrecognized object class: %u"
+
+SQLSTATE: XX000
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+### GAUSS-00797: "found unexpected dependency type '%c'"
+
+SQLSTATE: XX000
+
+错误原因: 依赖类型异常。
+
+解决办法: 系统表异常，请联系技术支持工程师提供技术支持。
+
+### GAUSS-00798: "found unexpected dependency for column"
+
+SQLSTATE: XX000
+
+错误原因: 列依赖类型异常。
+
+解决办法: 系统表异常，请联系技术支持工程师提供技术支持。
+
+### GAUSS-00799: "foreign table '%s' does not exist"
+
+SQLSTATE: 42704
+
+错误原因: ALTER COLUMN OPTIONS操作，外表不存在。
+
+解决办法: 建议更改本操作。
+
+### GAUSS-00800: "unexpected statement type: %d"
+
+SQLSTATE: XX000
+
+错误原因: 表更改语句的子类型异常。
+
+解决办法: 请检查SQL语句是否支持。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/9-GAUSS-00801-GAUSS-00900.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/9-GAUSS-00801-GAUSS-00900.md
new file mode 100644
index 0000000000000000000000000000000000000000..41b32cd2f3472982cf62bc3a7ddfe31329850987
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/9-GAUSS-00801-GAUSS-00900.md
@@ -0,0 +1,700 @@
+---
+title: GAUSS-00801 - GAUSS-00900
+summary: GAUSS-00801 - GAUSS-00900
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# GAUSS-00801 - GAUSS-00900
+
+<br/>
+
+## GAUSS-00801 - GAUSS-00810
+
+<br/>
+
+GAUSS-00801: "null conpfeqop for constraint %u"
+
+SQLSTATE: XX005
+
+错误原因: 约束属性为空。
+
+解决办法: 系统表异常，请联系技术支持工程师提供技术支持。
+
+GAUSS-00802: "conpfeqop is not a 1-D Oid array"
+
+SQLSTATE: 42804
+
+错误原因: 约束数组不为一维数组。
+
+解决办法: 系统表异常，请联系技术支持工程师提供技术支持。
+
+GAUSS-00803: "cannot change owner of sequence '%s'"
+
+SQLSTATE: 0A000
+
+错误原因: ALTER TABLE OWNER操作，sequence的所属者不能更改其所属者。
+
+解决办法: sequence所属者自己不能更改其所属者，建议取消本操作。
+
+GAUSS-00804: "'%s' is a composite type"
+
+SQLSTATE: 42809
+
+错误原因: ALTER TABLE OWNER操作，复合类型所有者不能被更改。
+
+解决办法: 不能更改复合类型的所属者，建议取消本操作。
+
+GAUSS-00805: "'%s' is not a table, view, sequence, or foreign table"
+
+SQLSTATE: 42809
+
+错误原因: ALTER TABLE OWNER操作，被更改对象必须是表、视图、sequence或外表，否则不能执行。
+
+解决办法: 表、视图、sequence以及外表之外其他对象不能更改所有者，建议更改本操作。
+
+GAUSS-00806: "index '%s' for table '%s' does not exist"
+
+SQLSTATE: 42704
+
+错误原因: ALTER TABLE CLUSTER ON操作，表的索引不存在。
+
+解决办法: 表的索引不存在无法设置Cluster，建议更改本操作。
+
+GAUSS-00807: "cannot have multiple SET TABLESPACE subcommands"
+
+SQLSTATE: 42601
+
+错误原因: ALTER TABLE SET TABLESPACE操作，不能有多条SET TABLESPACE子命令。
+
+解决办法: 不支持多条SET TABLESPACE子命令，建议更改本操作。
+
+GAUSS-00808: "relkind of psort tuple shouldn't be '%c'."
+
+SQLSTATE: XX000
+
+错误原因: 设置psort参数涉及的表类型不对。
+
+解决办法: 检查表类型是否为列存表。
+
+GAUSS-00809: "psort tuple doesn't have the correct ORIENTATION value."
+
+SQLSTATE: XX000
+
+错误原因: 设置psort参数涉及的表类型不对。
+
+解决办法: 检查表类型是否为列存表。
+
+GAUSS-00810: "cache lookup failed for relation %u"
+
+SQLSTATE: XX000
+
+错误原因:  ALTER TABLE SET TABLESPACE操作，关系不存在。
+
+解决办法: 无法找到关系表，建议更改本操作。
+
+<br/>
+
+## GAUSS-00811 - GAUSS-00820
+
+<br/>
+
+GAUSS-00811: "'%s' is not a table, index, or TOAST table"
+
+SQLSTATE: 42809
+
+错误原因: Set, reset, or replace reloptions操作，对象必须是表、索引或TOAST表。
+
+解决办法: 表、索引及TOAST表外，不能进行此操作。
+
+GAUSS-00812: "can not set tablespace for partition of neither table nor index"
+
+SQLSTATE: 42601
+
+错误原因: 除表、索引外的其他对象都不能对分区表设置表空间。
+
+解决办法: 只有表、索引能对分区设置表空间，建议更改此操作。
+
+GAUSS-00816: "cache lookup failed for partition %u"
+
+SQLSTATE: XX000
+
+错误原因: 缓存中分区查找失败。
+
+解决办法: 建议更换为有效分区。
+
+GAUSS-00817: "cannot move system relation '%s'"
+
+SQLSTATE: 0A000
+
+错误原因: ALTER TABLE SET TABLESPACE操作，系统表不能被移动。
+
+解决办法: 无法移动系统表，建议取消本操作。
+
+GAUSS-00819: "cannot change inheritance of typed table"
+
+SQLSTATE: 42809
+
+错误原因: ALTER TABLE INHERIT操作，无法类型表增加父表。
+
+解决办法: 不支持类型表的继承关系，建议取消本操作。
+
+GAUSS-00820: "relation '%s' is a partitioned table"
+
+SQLSTATE: XX000
+
+错误原因: ALTER TABLE INHERIT操作，不能为分区表增加父表。
+
+解决办法: 无法为分区表增加继承，建议取消本操作。
+
+<br/>
+
+## GAUSS-00821 - GAUSS-00830
+
+<br/>
+
+GAUSS-00821: "cannot inherit to temporary relation of another session"
+
+SQLSTATE: 42809
+
+错误原因: ALTER TABLE INHERIT操作，不能继承到另一个会话的临时关系表。
+
+解决办法: 不支持继承到另一会话的临时关系表，建议取消本操作。
+
+GAUSS-00822: "circular inheritance not allowed"
+
+SQLSTATE: 42P07
+
+错误原因: ALTER TABLE INHERIT操作，不支持循环继承。
+
+解决办法: 不支持循环继承，建议取消本操作。
+
+GAUSS-00823: "table '%s' without OIDs cannot inherit from table '%s' with OIDs"
+
+SQLSTATE: 42809
+
+错误原因: ALTER TABLE INHERIT操作，没有OIDs的表不能继承。
+
+解决办法: 没有OIDs的表不能继承父表，建议更改修改本表具有OIDs。
+
+GAUSS-00824: "column '%s' in child table must be marked NOT NULL"
+
+SQLSTATE: 42804
+
+错误原因: ALTER TABLE INHERIT操作，parent table有not null限制，child table的列必需有not null限制。
+
+解决办法: 建议为child table增加not null列属性。
+
+GAUSS-00825: "child table is missing column '%s'"
+
+SQLSTATE: 42804
+
+错误原因: ALTER TABLE INHERIT操作，child table中有缺失的列，不能继承自parent table。
+
+解决办法: 建议添加child table中的缺失列，或取消本继承关系。
+
+GAUSS-00826: "child table '%s' has different definition for check constraint '%s'"
+
+SQLSTATE: 42804
+
+错误原因: ALTER TABLE INHERIT操作，child table与parent table有不同的约束定义，不能继承。
+
+解决办法: 建议将child table与parent table设置为相同的约束定义。
+
+GAUSS-00827: "constraint '%s' conflicts with non-inherited constraint on child table '%s'"
+
+SQLSTATE: 42P17
+
+错误原因: ALTER TABLE INHERIT操作，父表的约束与子表的非继承约束冲突，不能继承。
+
+解决办法: 建议更改子表或父表的约束限制。
+
+GAUSS-00828: "child table is missing constraint '%s'"
+
+SQLSTATE: 42804
+
+错误原因: ALTER TABLE INHERIT操作，子表缺少约束限制。
+
+解决办法: 建议更改此操作。
+
+GAUSS-00829: "relation '%s' is not a parent of relation '%s'"
+
+SQLSTATE: 42P01
+
+错误原因: ALTER TABLE NO INHERIT操作，当删除子表的父表约束时，检测出子表不存在该父表关系。
+
+解决办法: 不存在此子表父表关系，故不能直接删除。
+
+GAUSS-00830: "typed tables cannot inherit"
+
+SQLSTATE: 42809
+
+错误原因: ALTER TABLE OF操作，将一个表附加到复合类型时，类型表不能继承。
+
+解决办法: 检查ALTER TABLE操作，附加的继承表不能是复合类型。
+
+<br/>
+
+## GAUSS-00831 - GAUSS-00840
+
+<br/>
+
+GAUSS-00831: "table is missing column '%s'"
+
+SQLSTATE: 42804
+
+错误原因: 表的列不存在。
+
+解决办法: 系统表异常，请联系技术支持工程师提供技术支持。
+
+GAUSS-00832: "table has column '%s' where type requires '%s'"
+
+SQLSTATE: 42804
+
+错误原因: 表和类型的列名不统一。
+
+解决办法: 系统表异常，请联系技术支持工程师提供技术支持。
+
+GAUSS-00833: "table '%s' has different type for column '%s'"
+
+SQLSTATE: 42804
+
+错误原因: 表和类型的属性不统一。
+
+解决办法: 系统表异常，请联系技术支持工程师提供技术支持。
+
+GAUSS-00834: "table has extra column '%s'"
+
+SQLSTATE: 42804
+
+错误原因: 表存在多余列。
+
+解决办法: 系统表异常，请联系技术支持工程师提供技术支持。
+
+GAUSS-00835: "'%s' is not a typed table"
+
+SQLSTATE: 42809
+
+错误原因: DROP OF操作的表不是一个类型表。
+
+解决办法: 检查DROP OF操作涉及的表是否是类型表。
+
+GAUSS-00837: "Distribution mode cannot be altered"
+
+SQLSTATE: 0A000
+
+错误原因: ALTER TABLE语句中，分布模式不能被更改。
+
+解决办法: ALTER TABLE语句中不能更改分布模式，请修改并检查ALTER TABLE语句。
+
+GAUSS-00838: "Cannot alter table to distribution incompatible with existing constraints"
+
+SQLSTATE: 0A000
+
+错误原因: 检测表的REDISTRIBUTION时，发现与现存的CONSTRAINTS存在冲突，故不能REDISTRIBUTION。
+
+解决办法: 更改REDISTRIBUTION，避免与现存CONSTRAINTS冲突。
+
+GAUSS-00839: "Node list is empty: one node at least is mandatory"
+
+SQLSTATE: 42710
+
+错误原因: DELETE NODE LIST时，检测到NODE LIST为空，故不能进行删除操作。
+
+解决办法: DELETE NODE LIST不能作用于空的LIST，请检查并修改本操作语句。
+
+GAUSS-00840: "PGXC Node %s: object not in relation node list"
+
+SQLSTATE: 42710
+
+错误原因: DELETE NODE LIST时，检测到NODE不在该LIST中，故不能进行删除操作。
+
+解决办法: DELETE NODE LIST操作不能删除LIST中不存在的NODE节点，请检查并修改本操作。
+
+## GAUSS-00841 - GAUSS-00850
+
+GAUSS-00841: "PGXC Node %s: object already in relation node list"
+
+SQLSTATE: 42710
+
+错误原因: ADD NODE LIST时，检测到NODE节点已经存在LIST中，故不能进行添加操作。
+
+解决办法: ADD NODE LIST操作检测到NODE在LIST中已经存在，无需进行本操作。
+
+GAUSS-00842: "cannot move an owned sequence into another schema"
+
+SQLSTATE: 0A000
+
+错误原因: ALTER TABLE SET SCHEMA时，不能将所有者的sequence更改给其他模式（SCHEMA）。
+
+解决办法: 在ALTER TABLE SET SCHEMA操作时，不支持将所有者的sequence转给其他模式，建议修改此ALTER TABLE SET SCHEMA语句。
+
+GAUSS-00843: "relation '%s' already exists in schema '%s'"
+
+SQLSTATE: 42P07
+
+错误原因: ALTER RELATION NAMESPACE时，检测到该relation在本模式（SCHEMA）中已经存在。
+
+解决办法: ALTER RELATION NAMESPACE时，relation在本SCHEMA中已经存在，无需此操作。
+
+GAUSS-00844: "failed to change schema dependency for relation '%s'"
+
+SQLSTATE: XX000
+
+错误原因: 更改表的模式依赖未成功。
+
+解决办法: 系统表异常，请联系技术支持工程师提供技术支持。
+
+GAUSS-00845: "permission denied: system catalog '%s' can not be altered"
+
+SQLSTATE: 42501
+
+错误原因: 不允许对系统表进行RENAME、SET SCHEMA和ALTER TABLE操作。
+
+解决办法: 请不要对系统表进行修改。
+
+GAUSS-00846: "'%s' is not a sequence"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-00847: "'%s' is not a foreign table"
+
+SQLSTATE: 42809
+
+错误原因: 系统内部错误。
+
+解决办法: 请联系技术支持工程师提供技术支持。
+
+GAUSS-00848: "'%s' is not a composite type"
+
+SQLSTATE: 42809
+
+错误原因: 对象不是复合类型。
+
+解决办法: 检查操作的对象是否是复合类型。
+
+GAUSS-00849: "'%s' is not an index"
+
+SQLSTATE: 42809
+
+错误原因: 执行索引操作的对象非索引表。
+
+解决办法: 检查执行索引操作的对象，确保是正常的索引表。
+
+GAUSS-00850: "'%s' is a foreign table, which does not support column constraints."
+
+SQLSTATE: 42809
+
+错误原因: 操作对象是外表，不支持列约束。
+
+解决办法: 检查操作的表是否有误，不应该是外表。
+
+## GAUSS-00851 - GAUSS-00860
+
+GAUSS-00851: "cannot %s '%s' because it is in use"
+
+SQLSTATE: 55006
+
+错误原因: 执行SQL语句时，需要访问的数据分区正被访问，不能执行此命令。
+
+解决办法: 建议等待数据分区访问结束再执行此SQL语句。
+
+GAUSS-00852: "there is no column for a partitioned table!"
+
+SQLSTATE: 42601
+
+错误原因: 当从分区表中获取partition key sequence时，分区表列为空。
+
+解决办法: 建议更改访问非空分区表。
+
+GAUSS-00853: "there is no partition key!"
+
+SQLSTATE: 42601
+
+错误原因: 当从分区表中获取partition key sequence时，partition keys全为空。
+
+解决办法: 建议将partition keys更改为正确、存在的键值。
+
+GAUSS-00854: "duplicate partition key: %s"
+
+SQLSTATE: 42701
+
+错误原因: 当从分区表中获取partition key sequence时，partition key有重复。
+
+解决办法: 建议更改此分区表。
+
+GAUSS-00857: "column %s cannot serve as an interval partitioning column because of its datatype"
+
+SQLSTATE: 42804
+
+错误原因: 该列数据类型不能作为interval partition(间隔分区)的列。
+
+解决办法: 建议修改本数据类型，使其满足interval partition列要求。
+
+GAUSS-00858: "column %s cannot serve as a range partitioning column because of its datatype"
+
+SQLSTATE: 42804
+
+错误原因: 该列数据类型不能满足分区表列的数据范围要求。
+
+解决办法: 建议更改该列数据类型。
+
+GAUSS-00859: "partition bound list contains too few elements"
+
+SQLSTATE: 42601
+
+错误原因: 更改分区值为数组时，分区边界链表(partition bound list)包含元素个数小于目标元素个数。
+
+解决办法: 建议更改目标元素个数，使其与partition bound list元素个数相等。
+
+GAUSS-00860: "partition bound list contains too many elements"
+
+SQLSTATE: 42601
+
+错误原因: 更改分区值为数组时，分区边界链表(partition bound list)包含元素个数大于目标元素个数。
+
+解决办法: 建议更改目标元素个数，使其与partition bound list元素个数相等。
+
+## GAUSS-00861 - GAUSS-00870
+
+GAUSS-00865: "invalid range partiiton table definition"
+
+SQLSTATE: 42601
+
+错误原因: 调用ComparePartitionValue函数时，此处为无效的分区表定义。
+
+解决办法: 建议重新选择有效的分区表。
+
+GAUSS-00866: "there is no partition key"
+
+SQLSTATE: 42601
+
+错误原因: 调用ComparePartitionValue函数时，不存在分区值。
+
+解决办法: 建议重新选择有效的分区表。
+
+GAUSS-00868: "partition bound of partition '%s' is too low"
+
+SQLSTATE: 42601
+
+错误原因: 调用ComparePartitionValue函数时，分区表的分区边界过小。
+
+解决办法: 检查建表语句，保证分区的边界值递增。
+
+GAUSS-00869: "can not add partition against NON-PARTITIONED table"
+
+SQLSTATE: XX000
+
+错误原因: 不能为NON-PARTITIONED表增加分区。
+
+解决办法: 建议更改表类型，使其变为可增加分区，或者取消此操作。
+
+GAUSS-00870: "can not drop partition against NON-PARTITIONED table"
+
+SQLSTATE: XX000
+
+错误原因: NON-PARTITIONED表不支持删除分区操作。
+
+解决办法: 不能对NON-PARTITIONED表进行删除分区操作。
+
+## GAUSS-00871 - GAUSS-00880
+
+GAUSS-00871: "can not set unusable index partition against NON-PARTITIONED index"
+
+SQLSTATE: XX000
+
+错误原因: 不能对NON-PARTITIONED表设置不可用的索引分区。
+
+解决办法: 对PARTITION表设置索引分区。
+
+GAUSS-00872: "can not set all index unusable on one partition against NON-PARTITIONED table"
+
+SQLSTATE: XX000
+
+错误原因: 不能对NON-PARTITIONED表设置不可用的全索引分区。
+
+解决办法: 针对PARTITION表设置全索引分区。
+
+GAUSS-00873: "can not enable row movement against NON-PARTITIONED table"
+
+SQLSTATE: XX000
+
+错误原因: NON-PARTITIONED表不开启行移动。
+
+解决办法: 建议更改此操作或者更改NON-PARTITIONED表为PARTITION表。
+
+GAUSS-00874: "can not disable row movement against NON-PARTITIONED table"
+
+SQLSTATE: XX000
+
+错误原因: NON-PARTITIONED表不能取消行移动。
+
+解决办法: 建议更改此操作或者更改NON-PARTITIONED表为PARTITION表。
+
+GAUSS-00875: "can not truncate partition against NON-PARTITIONED table"
+
+SQLSTATE: XX000
+
+错误原因: NON-PARTITIONED表不支持截断分区。
+
+解决办法: 建议更改此操作或者更改NON-PARTITIONED表为PARTITION表。
+
+GAUSS-00876: "can not exchange partition against NON-PARTITIONED table"
+
+SQLSTATE: XX000
+
+错误原因: NON-PARTITIONED表不能更改分区。
+
+解决办法: 建议更改此操作或者更改NON-PARTITIONED表为PARTITION表。
+
+GAUSS-00877: "can not merge partition against NON-PARTITIONED table"
+
+SQLSTATE: XX000
+
+错误原因: NON-PARTITIONED表不能合并分区。
+
+解决办法: 建议更改此操作或者更改NON-PARTITIONED表为PARTITION表。
+
+GAUSS-00878: "can not split partition against NON-PARTITIONED table"
+
+SQLSTATE: XX000
+
+错误原因: NON-PARTITIONED表不能分割分区。
+
+解决办法: 建议更改此操作或者更改NON-PARTITIONED表为PARTITION表。
+
+GAUSS-00880: "the current relation have already reached max number of partitions"
+
+SQLSTATE: XX000
+
+错误原因: 当前关系表的分区数目已经达到最大，不能再增加。
+
+解决办法: 建议调整优化分区减少分区数量后，重新执行操作。
+
+## GAUSS-00881 - GAUSS-00890
+
+GAUSS-00882: "upper boundary of adding partition MUST overtop last existing partition"
+
+SQLSTATE: XX000
+
+错误原因: 关系表新增分区的上边界必须大于最后一个现有分区的上边界。
+
+解决办法: 请更改新增分区的上边界。
+
+GAUSS-00883: "could not acquire AccessExclusiveLock on dest table partition '%s', %s failed"
+
+SQLSTATE: XX000
+
+错误原因: 没有拿到分区的AccessExclusiveLock。
+
+解决办法: 可能由于并发冲突引起，稍后再试。
+
+GAUSS-00884: "Cannot drop the only partition of a partitioned table"
+
+SQLSTATE: XX000
+
+错误原因: 删除表分区操作时，无法删除关系表的最后一个分区。
+
+解决办法: 不能删除关系表的最后一个分区，建议取消本操作。
+
+GAUSS-00886: "no local index defined on partition %u"
+
+SQLSTATE: XX000
+
+错误原因: 该分区中不能查找到本地索引。
+
+解决办法: 建议重新检查本操作的分区和索引名称，不存在次索引可以取消本操作。
+
+GAUSS-00887: "can not set unusable index for relation %s , as it is not a index"
+
+SQLSTATE: XX000
+
+错误原因: 在检测索引有效性时，发现本索引无效，故不能为关系表设置此索引。
+
+解决办法: 建议检查该索引的有效性，若无效许修改此索引。
+
+GAUSS-00888: "could not find tuple for relation %u"
+
+SQLSTATE: XX000
+
+错误原因: 在执行ModifyRowMovement操作时，检测到无法获取关系表的元组，故不能进行此操作。
+
+解决办法: 建议检查关系表的元组属性，或取消此操作。
+
+GAUSS-00889: "cannot truncate a partition owned by partitioned table which is referenced in a foreign key constraint"
+
+SQLSTATE: XX000
+
+错误原因: 被外键(foreign key)引用限制的分区表不能截断其分区。
+
+解决办法: 建议取消该分区表的外键引用限制，或者取消此操作。
+
+GAUSS-00890: "can not merge index partition %s bacause it is unusable local index"
+
+SQLSTATE: XX000
+
+错误原因: 针对不可用的本地索引，不可合并索引分区。
+
+解决办法: 建议检查本地索引的可用性并修改，或者取消此操作。
+
+## GAUSS-00891 - GAUSS-00900
+
+GAUSS-00891: "source partitions must be at least two partitions"
+
+SQLSTATE: XX000
+
+错误原因: MergePartition操作时，检测到原始分区数目小于2，故不能进行MergePartition操作。
+
+解决办法: 建议检查表的原始分区数目，数目小于2个时，不能进行合并操作。
+
+GAUSS-00892: "merge partitions of relation '%s', source partitions must be no more than %d partitions"
+
+SQLSTATE: XX000
+
+错误原因: 合并的分区数大于支持的最大合并的分区数。
+
+解决办法: 减少合并的分区数。
+
+GAUSS-00893: "merge partitions cannot process inusable index relation \\"%s\\""
+
+SQLSTATE: XX000
+
+错误原因: MergePartition操作时，检测到包含不可用的本地索引，不能进行MergePartition操作。
+
+解决办法: 建议检查表的本地索引可用性，修改不可用索引，再进行MergePartition操作。
+
+GAUSS-00895: "source partitions must be continuous and in ascending order of boundary"
+
+SQLSTATE: XX000
+
+错误原因: MergePartition操作时，原始分区应满足连续性且边界升序，否则不能合并。
+
+解决办法: 建议检查原始分区是否满足连续性及边界递增条件，满足该条件才能进行合并操作。
+
+GAUSS-00896: "target partition's name '%s' already exists"
+
+SQLSTATE: 42710
+
+错误原因: MergePartition操作时，目标分区名已经存在，不能进行本操作。
+
+解决办法: 建议修改目标分区名，避免名称冲突。
+
+GAUSS-00898: "could not acquire AccessExclusiveLock on dest table partition '%s', MERGE PARTITIONS failed"
+
+SQLSTATE: XX000
+
+错误原因: 不能获取合并分区的排他锁。
+
+解决办法: 检查合并分区是否在进行其他操作。
+
+GAUSS-00899: "Specified partition does not exist"
+
+SQLSTATE: 42P01
+
+错误原因: ExchangePartition操作时，检测到指定分区不存在，不能进行此操作。
+
+解决办法: 建议检查分区名称，确定分区名称后再进行此操作。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/description-of-sql-error-codes.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/description-of-sql-error-codes.md
new file mode 100644
index 0000000000000000000000000000000000000000..d3a11e2daae03b43fc9c4bd43954acac1903e461
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/description-of-sql-error-codes.md
@@ -0,0 +1,396 @@
+---
+title: SQL标准错误码说明
+summary: SQL标准错误码说明
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# SQL标准错误码说明
+
+根据X/Open和SQL Access Group SQL CAE规范（1992）所进行的定义，SQLERROR返回SQLSTATE值。SQLSTATE值是包含五个字符的字符串，由2个字符的SQL错误类和3个字符的子类构成。五个字符包含数值或者大写字母， 代表各种错误或者警告条件的代码。成功的状态是由00000标识的。SQLSTATE代码大多数情况下都是定义在SQL标准里的。
+
+MogDB也遵循SQL标准返回错误码的SQLSTATE值，详细说明请参见[表1](#errorcode)。
+
+**表 1** MogDB错误码SQLSTATE值 <a id="errorcode"></a>
+
+| 错误码SQLSTATE值                                    | 错误码含义                                                   |
+| :-------------------------------------------------- | :----------------------------------------------------------- |
+| 类 00 - 成功完成                                    |                                                              |
+| 00000                                               | 成功完成（SUCCESSFUL_COMPLETION）                            |
+| 类 01 - 警告                                        |                                                              |
+| 01000                                               | 警告（WARNING）                                              |
+| 0100C                                               | 返回了动态结果集（DYNAMIC_RESULT_SETS_RETURNED）             |
+| 01008                                               | 警告，隐含补齐了零比特位（IMPLICIT_ZERO_BIT_PADDING）        |
+| 01003                                               | 在集合函数里消除了NULL（NULL_VALUE_ELIMINATED_IN_SET_FUNCTION） |
+| 01007                                               | 没有赋予权限（PRIVILEGE_NOT_GRANTED）                        |
+| 01006                                               | 没有撤销权限（PRIVILEGE_NOT_REVOKED）                        |
+| 01004                                               | 字符串数据在右端截断（STRING_DATA_RIGHT_TRUNCATION）         |
+| 01P01                                               | 废弃的特性（DEPRECATED_FEATURE）                             |
+| 类 02 - 没有数据（按照SQL标准的要求，这也是警告类） |                                                              |
+| 02000                                               | 没有数据（NO_DATA）                                          |
+| 02001                                               | 返回了无附加动态结果集（NO_ADDITIONAL_DYNAMIC_RESULT_SETS_RETURNED） |
+| 类 03 - SQL语句尚未结束                             |                                                              |
+| 03000                                               | SQL语句尚未结束（SQL_STATEMENT_NOT_YET_COMPLETE）            |
+| 类 08 - 连接异常                                    |                                                              |
+| 08000                                               | 连接异常（CONNECTION_EXCEPTION）                             |
+| 08003                                               | 连接不存在（CONNECTION_DOES_NOT_EXIST）                      |
+| 08006                                               | 连接失败（CONNECTION_FAILURE）                               |
+| 08001                                               | SQL客户端不能建立SQL连接（SQLCLIENT_UNABLE_TO_ESTABLISH_SQLCONNECTION） |
+| 08004                                               | SQL服务器拒绝建立SQL连接（SQLSERVER_REJECTED_ESTABLISHMENT_OF_SQLCONNECTION） |
+| 08007                                               | 未知的事务解析（TRANSACTION_RESOLUTION_UNKNOWN）             |
+| 08P01                                               | 违反协议（PROTOCOL_VIOLATION）                               |
+| 类09 - 触发动作异常                                 |                                                              |
+| 09000                                               | 触发动作异常（TRIGGERED_ACTION_EXCEPTION）                   |
+| 类 0A - 不支持特性                                  |                                                              |
+| 0A000                                               | 不支持此特性（FEATURE_NOT_SUPPORTED）                        |
+| 0A100                                               | 不支持流（STREAM_NOT_SUPPORTED）                             |
+| 类 0B - 非法事务初始化                              |                                                              |
+| 0B000                                               | 非法事务初始化（INVALID_TRANSACTION_INITIATION）             |
+| 类 0F - 定位器异常                                  |                                                              |
+| 0F000                                               | 定位器异常（LOCATOR_EXCEPTION）                              |
+| 0F001                                               | 非法的定位器声明（INVALID_LOCATOR_SPECIFICATION）            |
+| 类 0L - 非法赋权者                                  |                                                              |
+| 0L000                                               | 非法赋权者（INVALID_GRANTOR）                                |
+| 0LP01                                               | 非法赋权操作（INVALID_GRANT_OPERATION）                      |
+| 类 0P - 非法角色声明                                |                                                              |
+| 0P000                                               | 非法角色声明（INVALID_ROLE_SPECIFICATION）                   |
+| 类 0Z - 诊断异常                                    |                                                              |
+| 0Z000                                               | 诊断异常（DIAGNOSTICS_EXCEPTION）                            |
+| 0Z002                                               | 没有在活跃的处理程序下访问堆栈诊断信息（STACKED_DIAGNOSTICS_ACCESSED_WITHOUT_ACTIVE_HANDLER） |
+| 类 20 - 未找到CASE                                  |                                                              |
+| 20000                                               | 未找到CASE（CASE_NOT_FOUND）                                 |
+| 类 21 - 势违例                                      |                                                              |
+| 21000                                               | 势违例（CARDINALITY_VIOLATION）                              |
+| 类 22 - 数据异常                                    |                                                              |
+| 22000                                               | 数据异常（DATA_EXCEPTION）                                   |
+| 2202E                                               | 数组下标错误（ARRAY_SUBSCRIPT_ERROR）                        |
+| 22021                                               | 字符不被计算机命令系统识别（CHARACTER_NOT_IN_REPERTOIRE）    |
+| 22008                                               | 日期时间字段溢出（DATETIME_FIELD_OVERFLOW）                  |
+| 22012                                               | 被零除（DIVISION_BY_ZERO）                                   |
+| 22005                                               | 赋值中出错（ERROR_IN_ASSIGNMENT）                            |
+| 2200B                                               | 转义字符冲突（ESCAPE_CHARACTER_CONFLICT）                    |
+| 22022                                               | 指示器溢出（INDICATOR_OVERFLOW）                             |
+| 22015                                               | 内部字段溢出（INTERVAL_FIELD_OVERFLOW）                      |
+| 2201E                                               | 对数运算的非法参数（INVALID_ARGUMENT_FOR_LOGARITHM）         |
+| 22014                                               | NTILE函数的非法参数（INVALID_ARGUMENT_FOR_NTILE_FUNCTION）   |
+| 22016                                               | N值函数的非法参数（INVALID_ARGUMENT_FOR_NTH_VALUE_FUNCTION） |
+| 2201F                                               | 幂函数的非法参数（INVALID_ARGUMENT_FOR_POWER_FUNCTION）      |
+| 2201G                                               | 宽桶函数的非法参数（INVALID_ARGUMENT_FOR_WIDTH_BUCKET_FUNCTION） |
+| 22018                                               | 类型转换时非法的字符值（INVALID_CHARACTER_VALUE_FOR_CAST）   |
+| 22007                                               | 非法日期时间格式（INVALID_DATETIME_FORMAT）                  |
+| 22019                                               | 非法的转义字符（INVALID_ESCAPE_CHARACTER）                   |
+| 2200D                                               | 非法的转义字节（INVALID_ESCAPE_OCTET）                       |
+| 22025                                               | 非法转义序列（INVALID_ESCAPE_SEQUENCE）                      |
+| 22P06                                               | 非标准使用转义字符（NONSTANDARD_USE_OF_ESCAPE_CHARACTER）    |
+| 22010                                               | 非法指示器参数值（INVALID_INDICATOR_PARAMETER_VALUE）        |
+| 22023                                               | 非法参数值（INVALID_PARAMETER_VALUE）                        |
+| 2201B                                               | 非法正则表达式（INVALID_REGULAR_EXPRESSION）                 |
+| 2201W                                               | LIMIT子句中行号非法（INVALID_ROW_COUNT_IN_LIMIT_CLAUSE）     |
+| 2201X                                               | 结果集中行号非法（INVALID_ROW_COUNT_IN_RESULT_OFFSET_CLAUSE） |
+| 2202H                                               | 非法抽样参数（INVALID_TABLESAMPLE_ARGUMENT）                 |
+| 2202G                                               | 非法重复抽样（INVALID_TABLESAMPLE_REPEAT）                   |
+| 22009                                               | 非法时区显示值（INVALID_TIME_ZONE_DISPLACEMENT_VALUE）       |
+| 2200C                                               | 非法使用转义字符（INVALID_USE_OF_ESCAPE_CHARACTER）          |
+| 2200G                                               | 最相关类型不匹配（MOST_SPECIFIC_TYPE_MISMATCH）              |
+| 22004                                               | 不允许NULL值（NULL_VALUE_NOT_ALLOWED）                       |
+| 22002                                               | NULL值不能做指示器参数（NULL_VALUE_NO_INDICATOR_PARAMETER）  |
+| 22003                                               | 数值越界（NUMERIC_VALUE_OUT_OF_RANGE）                       |
+| 22017                                               | 并发数超限（DOP_VALUE_OUT_OF_RANGE）                         |
+| 22026                                               | 字符串数据长度不匹配（STRING_DATA_LENGTH_MISMATCH）          |
+| 22028                                               | 正则表达式不匹配（REGEXP_MISMATCH）                          |
+| 22001                                               | 字符串数据右截断（STRING_DATA_RIGHT_TRUNCATION）             |
+| 22011                                               | 抽取子字符串错误（SUBSTRING_ERROR）                          |
+| 22027                                               | 截断错误（TRIM_ERROR）                                       |
+| 22024                                               | 未结束的C字符串（UNTERMINATED_C_STRING）                     |
+| 2200F                                               | 零长度的字符串（ZERO_LENGTH_CHARACTER_STRING）               |
+| 22P01                                               | 浮点异常（FLOATING_POINT_EXCEPTION）                         |
+| 22P02                                               | 非法文本表现形式（INVALID_TEXT_REPRESENTATION）              |
+| 22P03                                               | 非法二进制表现形式（INVALID_BINARY_REPRESENTATION）          |
+| 22P04                                               | 错误的COPY格式（BAD_COPY_FILE_FORMAT）                       |
+| 22P05                                               | 不可翻译字符（UNTRANSLATABLE_CHARACTER）                     |
+| 22P06                                               | 内存查找失败（CACHE_LOOKUP_FAILED）                          |
+| 22P07                                               | 文件读取失败（FILE_READ_FAILED）                             |
+| 22P08                                               | 获取数据失败（FETCH_DATA_FAILED）                            |
+| 2200L                                               | 非XML文件（NOT_AN_XML_DOCUMENT）                             |
+| 2200M                                               | 非法的XML文件（INVALID_XML_DOCUMENT）                        |
+| 2200N                                               | 非法的XML内容（INVALID_XML_CONTENT）                         |
+| 2200O                                               | 非法的XML错误信息（INVALID_XML_ERROR_CONTEXT）               |
+| 2200S                                               | 非法的XML注释（INVALID_XML_COMMENT）                         |
+| 2200T                                               | 非法的XML处理命令（INVALID_XML_PROCESSING_INSTRUCTION）      |
+| 2200X                                               | 关闭RELATION错误（RELATION_CLOSE_ERROR）                     |
+| 类 23 - 违反完整性约束                              |                                                              |
+| 23000                                               | 违反完整性约束（INTEGRITY_CONSTRAINT_VIOLATION）             |
+| 23001                                               | 违反限制（RESTRICT_VIOLATION）                               |
+| 23502                                               | 违反非空约束（NOT_NULL_VIOLATION）                           |
+| 23503                                               | 违反外键约束（FOREIGN_KEY_VIOLATION）                        |
+| 23505                                               | 违反唯一约束（UNIQUE_VIOLATION）                             |
+| 23514                                               | 违反CHECK约束（CHECK_VIOLATION）                             |
+| 23P01                                               | 违反排他约束（EXCLUSION_VIOLATION）                          |
+| 类 24 - 非法游标状态                                |                                                              |
+| 24000                                               | 非法游标状态（INVALID_CURSOR_STATE）                         |
+| 类 25 - 非法事务状态                                |                                                              |
+| 25000                                               | 非法事务状态（INVALID_TRANSACTION_STATE）                    |
+| 25001                                               | 活跃的SQL状态（ACTIVE_SQL_TRANSACTION）                      |
+| 25002                                               | 分支事务已激活（BRANCH_TRANSACTION_ALREADY_ACTIVE）          |
+| 25008                                               | 持有的游标要求同样的隔离级别（HELD_CURSOR_REQUIRES_SAME_ISOLATION_LEVEL） |
+| 25003                                               | 分支事务访问方式不当（INAPPROPRIATE_ACCESS_MODE_FOR_BRANCH_TRANSACTION） |
+| 25004                                               | 分支事务隔离级别不当（INAPPROPRIATE_ISOLATION_LEVEL_FOR_BRANCH_TRANSACTION） |
+| 25005                                               | 分支事务没有活跃的SQL事务（NO_ACTIVE_SQL_TRANSACTION_FOR_BRANCH_TRANSACTION） |
+| 25006                                               | 只读的SQL事务（READ_ONLY_SQL_TRANSACTION）                   |
+| 25007                                               | 不支持模式和数据语句混合使用（SCHEMA_AND_DATA_STATEMENT_MIXING_NOT_SUPPORTED） |
+| 25009                                               | 恢复期间无法启用事务（RUN_TRANSACTION_DURING_RECOVERY）      |
+| 25010                                               | 事务ID不存在（GXID_DOES_NOT_EXIST）                          |
+| 25P01                                               | 没有活跃的SQL事务（NO_ACTIVE_SQL_TRANSACTION）               |
+| 25P02                                               | 在失败的SQL事务中（IN_FAILED_SQL_TRANSACTION）               |
+| 类 26 - 非法SQL语句名                               |                                                              |
+| 26000                                               | 非法SQL语句名（INVALID_SQL_STATEMENT_NAME）                  |
+| 类 27 - 触发的数据改变违规                          |                                                              |
+| 27000                                               | 触发的数据改变违规（TRIGGERED_DATA_CHANGE_VIOLATION）        |
+| 27001                                               | 触发的元素非法（TRIGGERED_INVALID_TUPLE）                    |
+| 类 28 - 非法授权声明                                |                                                              |
+| 28000                                               | 非法授权声明（INVALID_AUTHORIZATION_SPECIFICATION）          |
+| 28P01                                               | 非法密码（INVALID_PASSWORD）                                 |
+| 28P02                                               | 未修改初始密码（INITIAL_PASSWORD_NOT_MODIFIED）              |
+| 类29 - 无效或意外的状态                             |                                                              |
+| 29P06                                               | 缓存在CACHE中的PLAN无效（INVALID_CACHE_PLAN）                |
+| 类 2B - 依然存在依赖的优先级描述符                  |                                                              |
+| 2B000                                               | 依然存在依赖的优先级描述符（DEPENDENT_PRIVILEGE_DESCRIPTORS_STILL_EXIST） |
+| 2BP01                                               | 依赖性对象仍然存在（DEPENDENT_OBJECTS_STILL_EXIST）          |
+| 类 2D - 非法的事务终止                              |                                                              |
+| 2D000                                               | 非法的事务终止（INVALID_TRANSACTION_TERMINATION）            |
+| 类 2F - SQL过程异常                                 |                                                              |
+| 2F000                                               | SQL过程异常（SQL_ROUTINE_EXCEPTION）                         |
+| 2F005                                               | 执行的函数没有返回语句（FUNCTION_EXECUTED_NO_RETURN_STATEMENT） |
+| 2F002                                               | 不允许修改SQL数据（MODIFYING_SQL_DATA_NOT_PERMITTED）        |
+| 2F003                                               | 企图使用禁止的SQL语句（PROHIBITED_SQL_STATEMENT_ATTEMPTED）  |
+| 2F004                                               | 不允许读取SQL数据（READING_SQL_DATA_NOT_PERMITTED）          |
+| 类 34 - 非法游标名                                  |                                                              |
+| 34000                                               | 非法游标名（INVALID_CURSOR_NAME）                            |
+| 类 38 - 外部过程异常                                |                                                              |
+| 38000                                               | 外部过程异常（EXTERNAL_ROUTINE_EXCEPTION）                   |
+| 38001                                               | 不允许包含SQL（CONTAINING_SQL_NOT_PERMITTED）                |
+| 38002                                               | 不允许修改SQL数据（MODIFYING_SQL_DATA_NOT_PERMITTED）        |
+| 38003                                               | 企图使用禁止的SQL语句（PROHIBITED_SQL_STATEMENT_ATTEMPTED）  |
+| 38004                                               | 不允许读取SQL数据（READING_SQL_DATA_NOT_PERMITTED）          |
+| 类 39 - 外部过程调用异常                            |                                                              |
+| 39000                                               | 外部过程调用异常（EXTERNAL_ROUTINE_INVOCATION_EXCEPTION）    |
+| 39001                                               | 返回了非法的SQLSTATE（INVALID_SQLSTATE_RETURNED）            |
+| 39004                                               | 不允许空值（NULL_VALUE_NOT_ALLOWED）                         |
+| 39P01                                               | 违反触发协议（TRIGGER_PROTOCOL_VIOLATED）                    |
+| 39P02                                               | 违反SRF协议（SRF_PROTOCOL_VIOLATED）                         |
+| 类 3B - 保存点异常                                  |                                                              |
+| 3B000                                               | 保存点异常（SAVEPOINT_EXCEPTION）                            |
+| 3B001                                               | 无效的保存点声明（INVALID_SAVEPOINT_SPECIFICATION）          |
+| 类 3D - 非法数据库名                                |                                                              |
+| 3D000                                               | 非法数据库名（INVALID_CATALOG_NAME）                         |
+| 类 3F - 非法模式名                                  |                                                              |
+| 3F000                                               | 非法模式名（INVALID_SCHEMA_NAME）                            |
+| 3F001                                               | 未定义模式（UNDEFINED_SCHEMA）                               |
+| 类 40 - 事务回滚                                    |                                                              |
+| 40000                                               | 事务回滚（TRANSACTION_ROLLBACK）                             |
+| 40002                                               | 违反事务完整性约束（TRANSACTION_INTEGRITY_CONSTRAINT_VIOLATION） |
+| 40001                                               | 串行化失败（SERIALIZATION_FAILURE）                          |
+| 40003                                               | 未知语句是否结束（STATEMENT_COMPLETION_UNKNOWN）             |
+| 40P01                                               | 侦测到死锁（DEADLOCK_DETECTED）                              |
+| 类 42 - 语法错误或者违反访问规则                    |                                                              |
+| 42000                                               | 语法错误或者违反访问规则（SYNTAX_ERROR_OR_ACCESS_RULE_VIOLATION） |
+| 42601                                               | 语法错误（SYNTAX_ERROR）                                     |
+| 42501                                               | 权限不够（INSUFFICIENT_PRIVILEGE）                           |
+| 42846                                               | 无法进行类型转换（CANNOT_COERCE）                            |
+| 42803                                               | 分组错误（GROUPING_ERROR）                                   |
+| 42P20                                               | 窗口错误（WINDOWING_ERROR）                                  |
+| 42P19                                               | 无效递归（INVALID_RECURSION）                                |
+| 42830                                               | 非法的外键（INVALID_FOREIGN_KEY）                            |
+| 42602                                               | 非法名称（INVALID_NAME）                                     |
+| 42622                                               | 名称太长（NAME_TOO_LONG）                                    |
+| 42939                                               | 保留名称（RESERVED_NAME）                                    |
+| 42804                                               | 数据类型不匹配（DATATYPE_MISMATCH）                          |
+| 42P18                                               | 不确定的数据类型（INDETERMINATE_DATATYPE）                   |
+| 42P21                                               | 排序规则不匹配（COLLATION_MISMATCH）                         |
+| 42P22                                               | 不确定的排序规则（INDETERMINATE_COLLATION）                  |
+| 42P23                                               | 分区错误（PARTITION_ERROR）                                  |
+| 42P24                                               | 非法属性值（INVALID_ATTRIBUTE）                              |
+| 42P25                                               | 非法聚集函数（INVALID_AGG）                                  |
+| 42P26                                               | 资源池错误（RESOURCE_POOL_ERROR）                            |
+| 42P27                                               | 未找到父级计划（PLAN_PARENT_NOT_FOUND）                      |
+| 42P28                                               | 更新冲突（MODIFY_CONFLICTS）                                 |
+| 42P29                                               | 分布错误（DISTRIBUTION_ERROR）                               |
+| 42809                                               | 错误的对象类型（WRONG_OBJECT_TYPE）                          |
+| 42703                                               | 未定义的字段（UNDEFINED_COLUMN）                             |
+| 42883                                               | 未定义的函数（UNDEFINED_FUNCTION）                           |
+| 42P01                                               | 未定义的表（UNDEFINED_TABLE）                                |
+| 42P02                                               | 未定义的参数（UNDEFINED_PARAMETER）                          |
+| 42704                                               | 未定义对象（UNDEFINED_OBJECT）                               |
+| 42701                                               | 重复的字段（DUPLICATE_COLUMN）                               |
+| 42P03                                               | 重复的游标（DUPLICATE_CURSOR）                               |
+| 42P04                                               | 重复的数据库（DUPLICATE_DATABASE）                           |
+| 42723                                               | 重复的函数（DUPLICATE_FUNCTION）                             |
+| 42P05                                               | 重复的预编译语句（DUPLICATE_PREPARED_STATEMENT）             |
+| 42P06                                               | 重复的模式（DUPLICATE_SCHEMA）                               |
+| 42P07                                               | 重复的表（DUPLICATE_TABLE）                                  |
+| 42712                                               | 重复的别名（DUPLICATE_ALIAS）                                |
+| 42710                                               | 重复的对象（DUPLICATE_OBJECT）                               |
+| 42702                                               | 模糊的字段（AMBIGUOUS_COLUMN）                               |
+| 42725                                               | 模糊的函数（AMBIGUOUS_FUNCTION）                             |
+| 42P08                                               | 模糊的参数（AMBIGUOUS_PARAMETER）                            |
+| 42P09                                               | 模糊的别名（AMBIGUOUS_ALIAS）                                |
+| 42P10                                               | 非法字段引用（INVALID_COLUMN_REFERENCE）                     |
+| 42611                                               | 非法字段定义（INVALID_COLUMN_DEFINITION）                    |
+| 42P11                                               | 非法游标定义（INVALID_CURSOR_DEFINITION）                    |
+| 42P12                                               | 非法数据库定义（INVALID_DATABASE_DEFINITION）                |
+| 42P13                                               | 非法函数定义（INVALID_FUNCTION_DEFINITION）                  |
+| 42P14                                               | 非法预编译语句定义（INVALID_PREPARED_STATEMENT_DEFINITION）  |
+| 42P15                                               | 非法模式定义（INVALID_SCHEMA_DEFINITION）                    |
+| 42P16                                               | 非法表定义（INVALID_TABLE_DEFINITION）                       |
+| 42P17                                               | 非法对象定义（INVALID_OBJECT_DEFINITION）                    |
+| 类 44 - 违反WITH CHECK选项                          |                                                              |
+| 44000                                               | 违反WITH CHECK选项（WITH_CHECK_OPTION_VIOLATION）            |
+| 类 53 - 资源不足                                    |                                                              |
+| 53000                                               | 资源不足（INSUFFICIENT_RESOURCES）                           |
+| 53100                                               | 磁盘满（DISK_FULL）                                          |
+| 53200                                               | 内存耗尽（OUT_OF_MEMORY）                                    |
+| 53300                                               | 太多连接（TOO_MANY_CONNECTIONS）                             |
+| 53400                                               | 超过配置限制（CONFIGURATION_LIMIT_EXCEEDED）                 |
+| 类 54 - 超过程序限制                                |                                                              |
+| 54000                                               | 超过程序限制（PROGRAM_LIMIT_EXCEEDED）                       |
+| 54001                                               | 语句太复杂（STATEMENT_TOO_COMPLEX）                          |
+| 54011                                               | 字段太多（TOO_MANY_COLUMNS）                                 |
+| 54023                                               | 参数太多（TOO_MANY_ARGUMENTS）                               |
+| 类 55 - 对象不在预先要求的状态                      |                                                              |
+| 55000                                               | 对象不在预先要求的状态（OBJECT_NOT_IN_PREREQUISITE_STATE）   |
+| 55006                                               | 对象在使用中(OBJECT_IN_USE)                                  |
+| 55P02                                               | 无法修改运行时参数（CANT_CHANGE_RUNTIME_PARAM）              |
+| 55P03                                               | 锁不可获得（LOCK_NOT_AVAILABLE）                             |
+| 类 57 - 操作者干涉                                  |                                                              |
+| 57000                                               | 操作者干涉（OPERATOR_INTERVENTION）                          |
+| 57014                                               | 查询被取消（QUERY_CANCELED）                                 |
+| 57015                                               | 内部查询取消（QUERY_INTERNAL_CANCEL）                        |
+| 57P01                                               | 管理员关闭系统（ADMIN_SHUTDOWN）                             |
+| 57P02                                               | 崩溃宕机（CRASH_SHUTDOWN）                                   |
+| 57P03                                               | 现在无法连接（CANNOT_CONNECT_NOW）                           |
+| 57P04                                               | 丢弃数据库（DATABASE_DROPPED）                               |
+| 类 58 - 系统错误（GaussDB自己内部的错误）           |                                                              |
+| 58000                                               | 系统错误（SYSTEM_ERROR）                                     |
+| 58030                                               | IO错误（IO_ERROR）                                           |
+| 58P01                                               | 未定义的文件（UNDEFINED_FILE）                               |
+| 58P02                                               | 重复的文件（DUPLICATE_FILE）                                 |
+| 类 F0 - 配置文件错误                                |                                                              |
+| F0000                                               | 配置文件错误（CONFIG_FILE_ERROR）                            |
+| F0001                                               | 锁文件存在（LOCK_FILE_EXISTS）                               |
+| 类 HV - 外部数据错误（SQL/MED）                     |                                                              |
+| HV000                                               | 外部数据错误（FDW_ERROR）                                    |
+| HV005                                               | 未找到列名（FDW_COLUMN_NAME_NOT_FOUND）                      |
+| HV002                                               | 需要动态参数值（FDW_DYNAMIC_PARAMETER_VALUE_NEEDED）         |
+| HV010                                               | 函数序列错误（FDW_FUNCTION_SEQUENCE_ERROR）                  |
+| HV021                                               | 描述信息不一致（FDW_INCONSISTENT_DESCRIPTOR_INFORMATION）    |
+| HV024                                               | 非法属性值（FDW_INVALID_ATTRIBUTE_VALUE）                    |
+| HV007                                               | 非法列名称（FDW_INVALID_COLUMN_NAME）                        |
+| HV008                                               | 非法列数（FDW_INVALID_COLUMN_NUMBER）                        |
+| HV004                                               | 非法数据类型（FDW_INVALID_DATA_TYPE）                        |
+| HV006                                               | 非法数据类型描述符（FDW_INVALID_DATA_TYPE_DESCRIPTORS）      |
+| HV091                                               | 非法字段标识符（FDW_INVALID_DESCRIPTOR_FIELD_IDENTIFIER）    |
+| HV00B                                               | 非法处理（FDW_INVALID_HANDLE）                               |
+| HV00C                                               | 非法索引选项（FDW_INVALID_OPTION_INDEX）                     |
+| HV00D                                               | 非法选项名称（FDW_INVALID_OPTION_NAME）                      |
+| HV090                                               | 非法字符串长度或缓冲区长度（FDW_INVALID_STRING_LENGTH_OR_BUFFER_LENGTH） |
+| HV00A                                               | 非法字符长格式（FDW_INVALID_STRING_FORMAT）                  |
+| HV009                                               | 非法使用NULL指针（FDW_INVALID_USE_OF_NULL_POINTER）          |
+| HV014                                               | 太多句柄（FDW_TOO_MANY_HANDLES）                             |
+| HV001                                               | 内存耗尽（FDW_OUT_OF_MEMORY）                                |
+| HV00P                                               | 无模式（FDW_NO_SCHEMAS）                                     |
+| HV00J                                               | 未找到选项名称（FDW_OPTION_NAME_NOT_FOUND）                  |
+| HV00K                                               | 回复句柄（FDW_REPLY_HANDLE）                                 |
+| HV00Q                                               | 未找到模式（FDW_SCHEMA_NOT_FOUND）                           |
+| HV00R                                               | 未找到表（FDW_TABLE_NOT_FOUND）                              |
+| HV00S                                               | 不正确的服务器类型(FDW_INVALID_SERVER_TYPE)                  |
+| HV00L                                               | 无法建立执行（FDW_UNABLE_TO_CREATE_EXECUTION）               |
+| HV00M                                               | 不能创建回复（FDW_UNABLE_TO_CREATE_REPLY）                   |
+| HV00N                                               | 无法建立连接（FDW_UNABLE_TO_ESTABLISH_CONNECTION）           |
+| 类 P0 - PL/pgSQL错误                                |                                                              |
+| P0000                                               | PLPGSQL错误（PLPGSQL_ERROR）                                 |
+| P0001                                               | 抛出异常（RAISE_EXCEPTION）                                  |
+| P0002                                               | 未找到数据（NO_DATA_FOUND）                                  |
+| P0003                                               | 行太多（TOO_MANY_ROWS）                                      |
+| P0004                                               | FORALL需要DML操作（FORALL_NEED_DML）                         |
+| 类 XX - 内部错误                                    |                                                              |
+| XX000                                               | 内部错误（INTERNAL_ERROR）                                   |
+| XX001                                               | 数据损坏（DATA_CORRUPTED）                                   |
+| XX002                                               | 索引损坏（INDEX_CORRUPTED）                                  |
+| XX003                                               | 关闭远程流接口（STREAM_REMOTE_CLOSE_SOCKET）                 |
+| XX004                                               | 未知节点类型（UNRECOGNIZED_NODE_TYPE）                       |
+| XX005                                               | 异常空值（UNEXPECTED_NULL_VALUE）                            |
+| XX006                                               | 异常节点状态（UNEXPECTED_NODE_STATE）                        |
+| XX007                                               | JUNK列为空（NULL_JUNK_ATTRIBUTE）                            |
+| XX008                                               | 优化器状态不一致（OPTIMIZER_INCONSISTENT_STATE）             |
+| XX009                                               | 重复查询编号（STREAM_DUPLICATE_QUERY_ID）                    |
+| XX010                                               | 无效缓冲区（INVALID_BUFFER）                                 |
+| XX011                                               | 无效缓冲区引用（INVALID_BUFFER_REFERENCE）                   |
+| XX012                                               | 节点编号不匹配（NODE_ID_MISSMATCH）                          |
+| XX013                                               | 不能修改xid base（CANNOT_MODIFY_XIDBASE）                    |
+| XX014                                               | TOAST表数据损坏（UNEXPECTED_CHUNK_VALUE）                    |
+| 类 YY - SQL重试错误                                 |                                                              |
+| YY001                                               | 对端连接重置（CONNECTION_RESET_BY_PEER）                     |
+| YY002                                               | 对端流重置（STREAM_CONNECTION_RESET_BY_PEER）                |
+| YY003                                               | 锁等待超时（LOCK_WAIT_TIMEOUT）                              |
+| YY004                                               | 连接超时（CONNECTION_TIMED_OUT）                             |
+| YY005                                               | 查询设置错误（SET_QUERY_ERROR）                              |
+| YY006                                               | 超出逻辑内存（OUT_OF_LOGICAL_MEMORY）                        |
+| YY007                                               | 通信库内存分配（SCTP_MEMORY_ALLOC）                          |
+| YY008                                               | 无通信库缓存数据（SCTP_NO_DATA_IN_BUFFER）                   |
+| YY009                                               | 通信库释放内存关闭（SCTP_RELEASE_MEMORY_CLOSE）              |
+| YY010                                               | SCTP、TCP断开（SCTP_TCP_DISCONNECT）                         |
+| YY011                                               | 通信库断开（SCTP_DISCONNECT）                                |
+| YY012                                               | 通信库远程关闭（SCTP_REMOTE_CLOSE）                          |
+| YY013                                               | 等待未知通信库通信（SCTP_WAIT_POLL_UNKNOW）                  |
+| YY014                                               | 无效快照（SNAPSHOT_INVALID）                                 |
+| YY015                                               | 通讯接收信息错误（CONNECTION_RECEIVE_WRONG）                 |
+| 类SI - SPI接口错误                                  |                                                              |
+| SP000                                               | SPI接口错误（SPI_ERROR）                                     |
+| SP001                                               | SPI通讯失败（SPI_CONNECTION_FAILURE）                        |
+| SP002                                               | SPI完成失败（SPI_FINISH_FAILURE）                            |
+| SP003                                               | SPI准备失败（SPI_PREPARE_FAILURE）                           |
+| SP004                                               | SPI游标开启失败（SPI_CURSOR_OPEN_FAILURE）                   |
+| SP005                                               | SPI执行失败（SPI_EXECUTE_FAILURE）                           |
+| SP006                                               | SPI不当调用（SPI_IMPROPER_CALL_FUNCTION）                    |
+| 类RB - RBTree错误                                   |                                                              |
+| RB001                                               | RBTree无效节点状态（RBTREE_INVALID_NODE_STATE）              |
+| RB002                                               | RBTree无效迭代顺序（RBTREE_INVALID_ITERATOR_ORDER）          |
+| 类 PD - PL调试器错误                                |                                                              |
+| D0000                                               | PL调试器内部错误（PLDEBUGGER_INTERNAL_ERROR）                |
+| D0001                                               | 重复断点（DUPLICATE_BREAKPOINT）                             |
+| D0002                                               | 哈希函数没有被初始化（FUNCTION_HASH_IS_NOT_INITIALIZED）     |
+| D0003                                               | 断点不存在（BREAKPOINT_IS_NOT_PRESENT）                      |
+| D0004                                               | 已附加调试服务器（DEBUG_SERVER_ALREADY_IS_ATTACHED）         |
+| D0005                                               | 未附加调试服务器（DEBUG_SERVER_NOT_ATTACHED）                |
+| D0006                                               | 已同步调试服务器（DEBUG_SERVER_ALREADY_IN_SYNC）             |
+| D0007                                               | 未同步调试服务器（DEBUG_TARGET_SERVERS_NOT_IN_SYNC）         |
+| D0008                                               | 已同步目标服务（TARGET_SERVER_ALREADY_IN_SYNC）              |
+| D0009                                               | 变量不存在（NON_EXISTANT_VARIABLE）                          |
+| D0010                                               | 非法目标会话ID（INVALID_TARGET_SESSION_ID）                  |
+| D0011                                               | 非法操作（INVALID_OPERATION）                                |
+| D0012                                               | 达到最大调试会话数（MAXIMUM_NUMBER_OF_DEBUG_SESSIONS_REACHED） |
+| D0013                                               | 达到最大断点数（MAXIMUM_NUMBER_OF_BREAKPOINTS_REACHED）      |
+| 类LL - 逻辑解码错误码                               |                                                              |
+| LL001                                               | 逻辑解码错误（LOGICAL_DECODE_ERROR）                         |
+| LL002                                               | 哈希表搜索错误（RELFILENODEMAP）                             |
+
+**表 2** MogDB CM错误码SQLSTATE值
+
+| 类 c0 - 连接异常（Connection Exception）  |                                              |
+| :---------------------------------------- | :------------------------------------------- |
+| c0000                                     | 连接异常（connection_exception）             |
+| c0001                                     | 连接不存在（connection_does_not_exist）      |
+| c0002                                     | 连接失败（connection_failure）               |
+| 类 c1 - 环境异常（Environment Exception） |                                              |
+| c1000                                     | 内存不足（out_of_memory）                    |
+| 类 c2 - 文件异常（File Exception）        |                                              |
+| c2000                                     | 打开文件失败（open_file_failure）            |
+| c2001                                     | 文件读取失败（read_file_failure）            |
+| c2002                                     | 配置文件失败（config_file_failure）          |
+| 类 c3 - 参数异常（Parameter Exception）   |                                              |
+| c3000                                     | 参数失败（parameter_failure）                |
+| c3001                                     | 环境变量失败（environment_variable_failure） |
+| 类 c4 - Etcd异常（Etcd Exception）        |                                              |
+| c4000                                     | etcd打开失败（etcd_open_failure）            |
+| 类 c5 - 内部异常（Internal Exception）    |                                              |
+| c5000                                     | 内部错误（internal_error）                   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/third-party-library-error-codes.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/third-party-library-error-codes.md
new file mode 100644
index 0000000000000000000000000000000000000000..3cfc5163d72a33d084e48929c8cf960b985a839d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-code-reference/third-party-library-error-codes.md
@@ -0,0 +1,29 @@
+---
+title: 第三方库错误码说明
+summary: 第三方库错误码说明
+author: Zhang Cuiping
+date: 2021-03-11
+---
+
+# 第三方库错误码说明
+
+第三方错误码的值是包含五个字符的字符串，由3个字符的错误类型和2个字符的子类构成。五个字符包含数值或者大写字母，代表各种错误或者警告条件的代码。
+
+**表 1** liborc的错误码对照表
+
+| 错误级别  | 错误码 | 错误说明                                        |
+| :-------- | :----- | :---------------------------------------------- |
+| ORC_INFO  | ORC00  | 无效错误类型（INVALID_ERROR_CODE）              |
+| ORC_ERROR | ORC01  | 不支持或无法实现的错误类型（NOTIMPLEMENTEDYET） |
+| ORC_ERROR | ORC02  | 编译错误类型（PARSEERROR）                      |
+| ORC_ERROR | ORC03  | 逻辑错误类型（LOGICERROR）                      |
+| ORC_ERROR | ORC04  | 范围错误类型（RANGEERROR）                      |
+| ORC_ERROR | ORC05  | 写错误类型（WRITEERROR）                        |
+| ORC_FATAL | ORC06  | 中断错误类型（ASSERTERROR）                     |
+| ORC_ERROR | ORC07  | 内存错误类型（MEMORYERROR）                     |
+| ORC_ERROR | ORC08  | 其他未归类的错误类型（OTHERERROR）              |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+>
+> 1. 根据错误级别的不同，将ORC_ERROR及其以上级别的错误打印在psql端，将详细的堆栈信息打印在对应的CN/DN日志中，ORC_ERROR以下级别的错误打印仅打印在对应的CN/DN日志中。
+> 2. 户可根据错误码及对应的报错信息定位错误位置分析并解决问题。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/error-log-reference/kernel-error-message.md b/product/zh/docs-mogdb/v3.0/reference-guide/error-log-reference/kernel-error-message.md
new file mode 100644
index 0000000000000000000000000000000000000000..91cd0e4b06d42790b3bf098d694c8a63c84e0251
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/error-log-reference/kernel-error-message.md
@@ -0,0 +1,1328 @@
+---
+title: 内核错误信息
+summary: 内核错误信息
+author: Zhang Cuiping
+date: 2021-11-08
+---
+
+# 内核错误信息
+
+ERRMSG: “unsupported syntax: ENCRYPTED WITH in this operation”
+
+SQLSTATE: 42601
+
+CAUSE: “client encryption feature is not supported this operation.”
+
+ACTION: “Check client encryption feature whether supported this operation.”
+
+ERRMSG: “invalid grant operation”
+
+SQLSTATE: 0LP01
+
+CAUSE: “Grant options cannnot be granted to public.”
+
+ACTION: “Grant grant options to roles.”
+
+ERRMSG: “unrecognized object kind: %d”
+
+SQLSTATE: XX004
+
+CAUSE: “The object type is not supported for GRANT/REVOKE.”
+
+ACTION: “Check GRANT/REVOKE syntax to obtain the supported object types.”
+
+ERRMSG: “unrecognized GrantStmt.targtype: %d”
+
+SQLSTATE: XX004
+
+CAUSE: “The target type is not supported for GRANT/REVOKE.”
+
+ACTION: “Check GRANT/REVOKE syntax to obtain the supported target types.”
+
+ERRMSG: “invalid grant operation”
+
+SQLSTATE: 0LP01
+
+CAUSE: “Grant to public operation is forbidden in security mode.”
+
+ACTION: “Don't grant to public in security mode.”
+
+ERRMSG: “unrecognized object type”
+
+SQLSTATE: XX004
+
+CAUSE: “The object type is not supported for GRANT/REVOKE.”
+
+ACTION: “Check GRANT/REVOKE syntax to obtain the supported object types.”
+
+ERRMSG: “invalid grant/revoke operation”
+
+SQLSTATE: 0LP01
+
+CAUSE: “Column privileges are only valid for relations in GRANT/REVOKE.”
+
+ACTION: “Use the column privileges only for relations.”
+
+ERRMSG: “invalid AccessPriv node”
+
+SQLSTATE: 0LP01
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “unrecognized GrantStmt.objtype: %d”
+
+SQLSTATE: XX004
+
+CAUSE: “The object type is not supported for GRANT/REVOKE.”
+
+ACTION: “Check GRANT/REVOKE syntax to obtain the supported object types.”
+
+ERRMSG: “undefined client master key”
+
+SQLSTATE: 42705
+
+CAUSE: “The client master key does not exist.”
+
+ACTION: “Check whether the client master key exists.”
+
+ERRMSG: “undefined column encryption key”
+
+SQLSTATE: 42705
+
+CAUSE: “The column encryption key does not exist.”
+
+ACTION: “Check whether the column encryption key exists.”
+
+ERRMSG: “large object %u does not exist”
+
+SQLSTATE: 42704
+
+CAUSE: “The large object does not exist.”
+
+ACTION: “Check whether the large object exists.”
+
+ERRMSG: “redundant options”
+
+SQLSTATE: 42601
+
+CAUSE: “The syntax 'schemas' is redundant in ALTER DEFAULT PRIVILEGES statement.”
+
+ACTION: “Check ALTER DEFAULT PRIVILEGES syntax.”
+
+ERRMSG: “redundant options”
+
+SQLSTATE: 42601
+
+CAUSE: “The syntax 'roles' is redundant in ALTER DEFAULT PRIVILEGES statement.”
+
+ACTION: “Check ALTER DEFAULT PRIVILEGES syntax.”
+
+ERRMSG: “option '%s' not recognized”
+
+SQLSTATE: 42601
+
+CAUSE: “The option in ALTER DEFAULT PRIVILEGES statement is not supported.”
+
+ACTION: “Check ALTER DEFAULT PRIVILEGES syntax.”
+
+ERRMSG: “unrecognized GrantStmt.objtype: %d”
+
+SQLSTATE: XX004
+
+CAUSE: “The object type is not supported for ALTER DEFAULT PRIVILEGES.”
+
+ACTION: “Check ALTER DEFAULT PRIVILEGES syntax to obtain the supported object types.”
+
+ERRMSG: “invalid alter default privileges operation”
+
+SQLSTATE: 0LP01
+
+CAUSE: “Default privileges cannot be set for columns.”
+
+ACTION: “Check ALTER DEFAULT PRIVILEGES syntax.”
+
+ERRMSG: “unrecognized objtype: %d”
+
+SQLSTATE: XX004
+
+CAUSE: “The object type is not supported for default privileges.”
+
+ACTION: “Check ALTER DEFAULT PRIVILEGES syntax to obtain the supported object types.”
+
+ERRMSG: “could not find tuple for default ACL %u”
+
+SQLSTATE: 29P01
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “unexpected default ACL type: %d”
+
+SQLSTATE: 0LP01
+
+CAUSE: “The object type is not supported for default privilege.”
+
+ACTION: “Check ALTER DEFAULT PRIVILEGES syntax to obtain the supported object types.”
+
+ERRMSG: “invalid object id”
+
+SQLSTATE: 0LP01
+
+CAUSE: “The object type is not supported for GRANT/REVOKE.”
+
+ACTION: “Check GRANT/REVOKE syntax to obtain the supported object types.”
+
+ERRMSG: “undefined column”
+
+SQLSTATE: 42703
+
+CAUSE: “The column of the relation does not exist.”
+
+ACTION: “Check whether the column exists.”
+
+ERRMSG: “column number out of range”
+
+SQLSTATE: 0LP01
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “cache lookup failed for attribute %d of relation %u”
+
+SQLSTATE: 29P01
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “cache lookup failed for relation %u”
+
+SQLSTATE: 29P01
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “unsupported object type”
+
+SQLSTATE: 42809
+
+CAUSE: “Index type is not supported for GRANT/REVOKE.”
+
+ACTION: “Check GRANT/REVOKE syntax to obtain the supported object types.”
+
+ERRMSG: “unsupported object type”
+
+SQLSTATE: 42809
+
+CAUSE: “Composite type is not supported for GRANT/REVOKE.”
+
+ACTION: “Check GRANT/REVOKE syntax to obtain the supported object types.”
+
+ERRMSG: “wrong object type”
+
+SQLSTATE: 42809
+
+CAUSE: “GRANT/REVOKE SEQUENCE only support sequence objects.”
+
+ACTION: “Check GRANT/REVOKE syntax to obtain the supported object types.”
+
+ERRMSG: “invalid privilege type USAGE for table”
+
+SQLSTATE: 0LP01
+
+CAUSE: “GRANT/REVOKE TABLE do not support USAGE privilege.”
+
+ACTION: “Check GRANT/REVOKE syntax to obtain the supported privilege types for tables.”
+
+ERRMSG: “invalid privilege type %s for column”
+
+SQLSTATE: 0LP01
+
+CAUSE: “The privilege type is not supported for column object.”
+
+ACTION: “Check GRANT/REVOKE syntax to obtain the supported privilege types for column object.”
+
+ERRMSG: “cache lookup failed for database %u”
+
+SQLSTATE: 29P01
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “cache lookup failed for foreign-data wrapper %u”
+
+SQLSTATE: 29P01
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “cache lookup failed for foreign server %u”
+
+SQLSTATE: 29P01
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “cache lookup failed for function %u”
+
+SQLSTATE: 29P01
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “cache lookup failed for language %u”
+
+SQLSTATE: 29P01
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “Grant/revoke on untrusted languages if forbidden.”
+
+SQLSTATE: 0LP01
+
+CAUSE: “Grant/revoke on untrusted languages if forbidden.”
+
+ACTION: “Support grant/revoke on trusted C languages”
+
+ERRMSG: “Forbid grant language c to user with grant option.”
+
+SQLSTATE: 0A000
+
+CAUSE: “Forbid grant language c to user with grant option.”
+
+ACTION: “Only support grant language c to user.”
+
+ERRMSG: “Forbid grant language c to public.”
+
+SQLSTATE: 0A000
+
+CAUSE: “Forbid grant language c to public.”
+
+ACTION: “Grant language c to specified users.”
+
+ERRMSG: “cache lookup failed for large object %u”
+
+SQLSTATE: 29P01
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “cache lookup failed for namespace %u”
+
+SQLSTATE: 29P01
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “cache lookup failed for tablespace %u”
+
+SQLSTATE: 29P01
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “cache lookup failed for type %u”
+
+SQLSTATE: 29P01
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “cannot set privileges of array types”
+
+SQLSTATE: 0LP01
+
+CAUSE: “Cannot set privileges of array types.”
+
+ACTION: “Set the privileges of the element type instead.”
+
+ERRMSG: “wrong object type”
+
+SQLSTATE: 42809
+
+CAUSE: “GRANT/REVOKE DOMAIN only support domain objects.”
+
+ACTION: “Check GRANT/REVOKE syntax to obtain the supported object types.”
+
+ERRMSG: “cache lookup failed for data source %u”
+
+SQLSTATE: 29P01
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “cache lookup failed for client master key %u”
+
+SQLSTATE: 29P01
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “cache lookup failed for column encryption key %u”
+
+SQLSTATE: 29P01
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “cache lookup failed for directory %u”
+
+SQLSTATE: 29P01
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “unrecognized privilege type '%s'”
+
+SQLSTATE: 42601
+
+CAUSE: “The privilege type is not supported.”
+
+ACTION: “Check GRANT/REVOKE syntax to obtain the supported privilege types.”
+
+ERRMSG: “unrecognized privilege: %d”
+
+SQLSTATE: XX004
+
+CAUSE: “The privilege type is not supported.”
+
+ACTION: “Check GRANT/REVOKE syntax to obtain the supported privilege types.”
+
+ERRMSG: “unrecognized AclResult”
+
+SQLSTATE: XX004
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “permission denied for column '%s' of relation '%s'”
+
+SQLSTATE: 42501
+
+CAUSE: “Insufficient privileges for the column.”
+
+ACTION: “Select the system tables to get the acl of the column.”
+
+ERRMSG: “role with OID %u does not exist”
+
+SQLSTATE: 42704
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “unrecognized objkind: %d”
+
+SQLSTATE: XX004
+
+CAUSE: “The object type is not supported for privilege check.”
+
+ACTION: “Check GRANT/REVOKE syntax to obtain the supported object types.”
+
+ERRMSG: “attribute %d of relation with OID %u does not exist”
+
+SQLSTATE: 42703
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “the column has been dropped”
+
+SQLSTATE: 42703
+
+CAUSE: “The column does not exist.”
+
+ACTION: “Check whether the column exists.”
+
+ERRMSG: “relation with OID %u does not exist”
+
+SQLSTATE: 42P01
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “invalid group”
+
+SQLSTATE: 22000
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “database with OID %u does not exist”
+
+SQLSTATE: 3D000
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “directory with OID %u does not exist”
+
+SQLSTATE: 42704
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “function with OID %u does not exist”
+
+SQLSTATE: 42883
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “client master key with OID %u does not exist”
+
+SQLSTATE: 42705
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “language with OID %u does not exist”
+
+SQLSTATE: 42704
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “large object %u does not exist”
+
+SQLSTATE: 42704
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “schema with OID %u does not exist”
+
+SQLSTATE: 3F001
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “tablespace with OID %u does not exist”
+
+SQLSTATE: 42704
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “foreign-data wrapper with OID %u does not exist”
+
+SQLSTATE: 42704
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “foreign server with OID %u does not exist”
+
+SQLSTATE: 42704
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “data source with OID %u does not exist”
+
+SQLSTATE: 42704
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “type with OID %u does not exist”
+
+SQLSTATE: 42704
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “operator with OID %u does not exist”
+
+SQLSTATE: 42883
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “column encryption key with OID %u does not exist”
+
+SQLSTATE: 42705
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “operator class with OID %u does not exist”
+
+SQLSTATE: 42704
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “operator family with OID %u does not exist”
+
+SQLSTATE: 42704
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “text search dictionary with OID %u does not exist”
+
+SQLSTATE: 42704
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “text search configuration with OID %u does not exist”
+
+SQLSTATE: 42704
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “collation with OID %u does not exist”
+
+SQLSTATE: 42704
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “conversion with OID %u does not exist”
+
+SQLSTATE: 42704
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “extension with OID %u does not exist”
+
+SQLSTATE: 42704
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “synonym with OID %u does not exist”
+
+SQLSTATE: 42704
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “package can not create the same name with schema.”
+
+SQLSTATE: 22023
+
+CAUSE: “Package name conflict”
+
+ACTION: “Please rename package name”
+
+ERRMSG: “type is not exists %s.”
+
+SQLSTATE: 22023
+
+CAUSE: “System error.”
+
+ACTION: “Contact Huawei Engineer.”
+
+ERRMSG: “This input type is not supported for tdigest_in()“
+
+SQLSTATE: 0A000
+
+CAUSE: “input type is not supported”
+
+ACTION: “Check tdigest_in syntax to obtain the supported privilege types”
+
+ERRMSG: “Failed to apply for memory”
+
+SQLSTATE: 53200
+
+CAUSE: “palloc failed”
+
+ACTION: “Check memory”
+
+ERRMSG: “Failed to get tde info from relation '%s'.”
+
+SQLSTATE: XX005
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “SPI_connect failed: %s”
+
+SQLSTATE: SP001
+
+CAUSE: “System error.”
+
+ACTION: “Analyze the error message before the error”
+
+ERRMSG: “permission denied for terminate snapshot thread”
+
+SQLSTATE: 42501
+
+CAUSE: “The user does not have system admin privilege”
+
+ACTION: “Grant system admin to user”
+
+ERRMSG: “terminate snapshot thread failed”
+
+SQLSTATE: OP001
+
+CAUSE: “Execution failed due to: %s”
+
+ACTION: “check if snapshot thread exists”
+
+ERRMSG: “terminate snapshot thread failed”
+
+SQLSTATE: OP001
+
+CAUSE: “restart wdr snapshot thread timeoutor The thread did not respond to the kill signal”
+
+ACTION: “Check the wdr snapshot thread is restarted”
+
+ERRMSG: “set lockwait_timeout failed”
+
+SQLSTATE: XX000
+
+CAUSE: “System error.”
+
+ACTION: “Contact engineer to support.”
+
+ERRMSG: “permission denied for create WDR Snapshot”
+
+SQLSTATE: 42501
+
+CAUSE: “The user does not have system admin privilege”
+
+ACTION: “Grant system admin to user”
+
+ERRMSG: “WDR snapshot request can not be accepted, please retry later”
+
+SQLSTATE: OP001
+
+CAUSE: “wdr snapshot thread does not exist”
+
+ACTION: “Check if wdr snapshot thread exists”
+
+ERRMSG: “Cannot respond to WDR snapshot request”
+
+SQLSTATE: OP001
+
+CAUSE: “Execution failed due to: %s”
+
+ACTION: “Check if wdr snapshot thread exists”
+
+ERRMSG: “query(%s) can not get datum values”
+
+SQLSTATE: 22000
+
+CAUSE: “System error.”
+
+ACTION: “Check whether the query can be executed”
+
+ERRMSG: “create sequence failed”
+
+SQLSTATE: 22000
+
+CAUSE: “System error.”
+
+ACTION: “Check if sequence can be created”
+
+ERRMSG: “update snapshot end time stamp filled”
+
+SQLSTATE: 22000
+
+CAUSE: “System error.”
+
+ACTION: “Check whether the snapshot retry is successful”
+
+ERRMSG: “query can not get datum values”
+
+SQLSTATE: 22000
+
+CAUSE: “System error.”
+
+ACTION: “Check whether the query can be executed”
+
+ERRMSG: “SPI_connect failed: %s”
+
+SQLSTATE: XX000
+
+CAUSE: “System error.”
+
+ACTION: “Check whether the snapshot retry is successful”
+
+ERRMSG: “query(%s) execute failed”
+
+SQLSTATE: 22000
+
+CAUSE: “System error.”
+
+ACTION: “Check whether the snapshot retry is successful”
+
+ERRMSG: “clean table of snap_%s is failed”
+
+SQLSTATE: 22000
+
+CAUSE: “System error.”
+
+ACTION: “Check whether the snapshot retry is successful”
+
+ERRMSG: “analyze table failed”
+
+SQLSTATE: 22000
+
+CAUSE: “System error.”
+
+ACTION: “Check whether the snapshot retry is successful”
+
+ERRMSG: “insert into tables_snap_timestamp start time stamp is failed”
+
+SQLSTATE: 22000
+
+CAUSE: “System error.”
+
+ACTION: “Check whether the snapshot retry is successful”
+
+ERRMSG: “insert data failed”
+
+SQLSTATE: 22000
+
+CAUSE: “System error.”
+
+ACTION: “Check whether the snapshot retry is successful and check whether the query can be executed”
+
+ERRMSG: “update tables_snap_timestamp end time stamp is failed”
+
+SQLSTATE: 22000
+
+CAUSE: “System error.”
+
+ACTION: “Check whether the snapshot retry is successful”
+
+ERRMSG: “clean snapshot id %lu is failed in snapshot table”
+
+SQLSTATE: 22000
+
+CAUSE: “System error.”
+
+ACTION: “Check whether the snapshot retry is successful and check whether the query can be executed”
+
+ERRMSG: “clean snapshot failed”
+
+SQLSTATE: 22000
+
+CAUSE: “System error.”
+
+ACTION: “Check whether the snapshot retry is successful”
+
+ERRMSG: “can not create snapshot stat table”
+
+SQLSTATE: 22000
+
+CAUSE: “System error.”
+
+ACTION: “Check whether the query can be executed”
+
+ERRMSG: “create WDR snapshot data table failed”
+
+SQLSTATE: 22000
+
+CAUSE: “System error.”
+
+ACTION: “Check whether the query can be executed”
+
+ERRMSG: “insert into tables_snap_timestamp start time stamp failed”
+
+SQLSTATE: 22000
+
+CAUSE: “System error.”
+
+ACTION: “Check whether the query can be executed”
+
+ERRMSG: “insert into snap_%s is failed”
+
+SQLSTATE: 22000
+
+CAUSE: “System error.”
+
+ACTION: “Check whether the query can be executed”
+
+ERRMSG: “update tables_snap_timestamp end time stamp failed”
+
+SQLSTATE: 22000
+
+CAUSE: “System error.”
+
+ACTION: “Check whether the query can be executed”
+
+ERRMSG: “create index failed”
+
+SQLSTATE: 22000
+
+CAUSE: “System error.”
+
+ACTION: “Check whether the query can be executed”
+
+ERRMSG: “analyze table, connection failed: %s”
+
+SQLSTATE: XX000
+
+CAUSE: “System error.”
+
+ACTION: “Check whether the snapshot retry is successful”
+
+ERRMSG: “snapshot thread SPI_connect failed: %s”
+
+SQLSTATE: XX000
+
+CAUSE: “System error.”
+
+ACTION: “Check whether the snapshot retry is successful”
+
+ERRMSG: “Distributed key column can't be transformed”
+
+SQLSTATE: 42P10
+
+CAUSE: “There is a risk of violating uniqueness when transforming distribution columns.”
+
+ACTION: “Change transform column.”
+
+ERRMSG: “cannot convert %s to %s”
+
+SQLSTATE: 42804
+
+CAUSE: “There is no conversion path in pg_cast.”
+
+ACTION: “Rewrite or cast the expression.”
+
+ERRMSG: “create matview on TDE table failed”
+
+SQLSTATE: 0A000
+
+CAUSE: “create materialized views is not supported on TDE table”
+
+ACTION: “check CREATE syntax about create the materialized views”
+
+ERRMSG: “schema name can not same as package”
+
+SQLSTATE: 22023
+
+CAUSE: “schema name conflict”
+
+ACTION: “rename schema name”
+
+ERRMSG: “Unrecognized commandType when checking read-only attribute.”
+
+SQLSTATE: XX004
+
+CAUSE: “System error.”
+
+ACTION: “Contact Huawei Engineer.”
+
+ERRMSG: “Fail to generate subquery plan.”
+
+SQLSTATE: XX005
+
+CAUSE: “System error.”
+
+ACTION: “Contact Huawei Engineer.”
+
+ERRMSG: “Unrecognized node type when processing qual condition.”
+
+SQLSTATE: XX004
+
+CAUSE: “System error.”
+
+ACTION: “Contact Huawei Engineer.”
+
+ERRMSG: “Unrecognized node type when processing const parameters.”
+
+SQLSTATE: XX004
+
+CAUSE: “System error.”
+
+ACTION: “Contact Huawei Engineer.”
+
+ERRMSG: “SELECT FOR UPDATE/SHARE is not allowed with UNION/INTERSECT/EXCEPT”
+
+SQLSTATE: 0A000
+
+CAUSE: “SQL uses unsupported feature.”
+
+ACTION: “Modify SQL statement according to the manual.”
+
+ERRMSG: “GROUP BY cannot be implemented.”
+
+SQLSTATE: 0A000
+
+CAUSE: “GROUP BY uses unsupported datatypes.”
+
+ACTION: “Modify SQL statement according to the manual.”
+
+ERRMSG: “TSDB functions cannot be used if enable_tsdb is off.”
+
+SQLSTATE: D0011
+
+CAUSE: “Functions are not loaded.”
+
+ACTION: “Turn on enable_tsdb according to manual.”
+
+ERRMSG: “Unrecognized node type when extracting index.”
+
+SQLSTATE: XX004
+
+CAUSE: “System error.”
+
+ACTION: “Contact Huawei Engineer.”
+
+ERRMSG: “Ordering operator cannot be identified.”
+
+SQLSTATE: 42883
+
+CAUSE: “Grouping set columns must be able to sort their inputs.”
+
+ACTION: “Modify SQL statement according to the manual.”
+
+ERRMSG: “DISTINCT cannot be implemented.”
+
+SQLSTATE: 0A000
+
+CAUSE: “DISTINCT uses unsupported datatypes.”
+
+ACTION: “Modify SQL statement according to the manual.”
+
+ERRMSG: “Failed to locate grouping columns.”
+
+SQLSTATE: 55000
+
+CAUSE: “System error.”
+
+ACTION: “Contact Huawei Engineer.”
+
+ERRMSG: “Resjunk output columns are not implemented.”
+
+SQLSTATE: 20000
+
+CAUSE: “System error.”
+
+ACTION: “Contact Huawei Engineer.”
+
+ERRMSG: “PARTITION BY cannot be implemented.”
+
+SQLSTATE: 0A000
+
+CAUSE: “PARTITION BY uses unsupported datatypes.”
+
+ACTION: “Modify SQL statement according to the manual.”
+
+ERRMSG: “ORDER BY cannot be implemented.”
+
+SQLSTATE: 0A000
+
+CAUSE: “ORDER BY uses unsupported datatypes.”
+
+ACTION: “Modify SQL statement according to the manual.”
+
+ERRMSG: “Failed to deconstruct sort operators into partitioning/ordering operators.”
+
+SQLSTATE: D0011
+
+CAUSE: “System error.”
+
+ACTION: “Contact Huawei Engineer.”
+
+ERRMSG: “OBS and HDFS foreign table can NOT be in the same plan.”
+
+SQLSTATE: XX008
+
+CAUSE: “SQL uses unsupported feature.”
+
+ACTION: “Modify SQL statement according to the manual.”
+
+ERRMSG: “Pool size should not be zero”
+
+SQLSTATE: 22012
+
+CAUSE: “Compute pool configuration file contains error.”
+
+ACTION: “Please check the value of 'pl' in cp_client.conf.”
+
+ERRMSG: “Failed to get the runtime info from the compute pool.”
+
+SQLSTATE: 22004
+
+CAUSE: “System error.”
+
+ACTION: “Contact Huawei Engineer.”
+
+ERRMSG: “Version is not compatible between local cluster and the compute pool.”
+
+SQLSTATE: XX008
+
+CAUSE: “Compute pool is not installed appropriately.”
+
+ACTION: “Configure compute pool according to manual.”
+
+ERRMSG: “No optional index path is found.”
+
+SQLSTATE: 01000
+
+CAUSE: “System error.”
+
+ACTION: “Contact Huawei Engineer.”
+
+ERRMSG: “MERGE INTO on replicated table does not yet support using distributed tables.”
+
+SQLSTATE: 0A000
+
+CAUSE: “SQL uses unsupported feature.”
+
+ACTION: “Modify SQL statement according to the manual.”
+
+ERRMSG: “Fail to find ForeignScan node!”
+
+SQLSTATE: P0002
+
+CAUSE: “System error.”
+
+ACTION: “Contact Huawei Engineer.”
+
+ERRMSG: “sql advisor don't support none table, temp table, system table.”
+
+SQLSTATE: 42601
+
+CAUSE: “sql advisor don't support none table, temp table, system table.”
+
+ACTION: “check query component”
+
+ERRMSG: “Invalid autonomous transaction return datatypes”
+
+SQLSTATE: P0000
+
+CAUSE: “PL/SQL uses unsupported feature.”
+
+ACTION: “Contact Huawei Engineer.”
+
+ERRMSG: “new row for relation '%s' violates check constraint '%s'”
+
+SQLSTATE: 23514
+
+CAUSE: “some rows copy failed”
+
+ACTION: “check table defination”
+
+ERRMSG: “new row for relation '%s' violates check constraint '%s'”
+
+SQLSTATE: 23514
+
+CAUSE: “some rows copy failed”
+
+ACTION: “set client_min_messages = info for more details”
+
+ERRMSG: “get gauss home path is NULL”
+
+SQLSTATE: XX005
+
+CAUSE: “gauss home path not set”
+
+ACTION: “check if $GAUSSHOME is exist”
+
+ERRMSG: “unable to open kms_iam_info.json file”
+
+SQLSTATE: 58P03
+
+CAUSE: “file not exist or broken”
+
+ACTION: “check the kms_iam_info.json file”
+
+ERRMSG: “can not get password plaintext”
+
+SQLSTATE: XX005
+
+CAUSE: “file not exist or broken”
+
+ACTION: “check the password cipher rand file”
+
+ERRMSG: “IAM info json key is NULL”
+
+SQLSTATE: XX005
+
+CAUSE: “IAM info value error”
+
+ACTION: “check tde_config kms_iam_info.json file”
+
+ERRMSG: “get internal password is NULL”
+
+SQLSTATE: XX005
+
+CAUSE: “cipher rand file missing”
+
+ACTION: “check password cipher rand file”
+
+ERRMSG: “KMS info json key is NULL”
+
+SQLSTATE: XX005
+
+CAUSE: “KMS info value error”
+
+ACTION: “check tde_config kms_iam_info.json file”
+
+ERRMSG: “unable to get json file”
+
+SQLSTATE: 58P03
+
+CAUSE: “parse json file failed”
+
+ACTION: “check the kms_iam_info.json file format”
+
+ERRMSG: “get JSON tree is NULL”
+
+SQLSTATE: XX005
+
+CAUSE: “get KMS JSON tree failed”
+
+ACTION: “check input prarmeter or config.ini file”
+
+ERRMSG: “failed to get json tree”
+
+SQLSTATE: XX005
+
+CAUSE: “config.ini json tree error”
+
+ACTION: “check input prarmeter or config.ini file”
+
+ERRMSG: “failed to set the value of json tree”
+
+SQLSTATE: XX005
+
+CAUSE: “config.ini json tree error”
+
+ACTION: “check input prarmeter or config.ini file”
+
+ERRMSG: “http request failed”
+
+SQLSTATE: XX005
+
+CAUSE: “http request error”
+
+ACTION: “check KMS or IAM connect or config parameter”
+
+ERRMSG: “get iam token or iam agency token is NULL”
+
+SQLSTATE: XX005
+
+CAUSE: “connect IAM failed”
+
+ACTION: “check if your env can connect with IAM server”
+
+ERRMSG: “KMS dek json key is NULL”
+
+SQLSTATE: XX005
+
+CAUSE: “KMS return value error”
+
+ACTION: “check KMS config paramenter”
+
+ERRMSG: “get kms dek is NULL”
+
+SQLSTATE: XX005
+
+CAUSE: “connect KMS failed”
+
+ACTION: “check if your env can connect with KMS server”
+
+ERRMSG: “get http header is NULL”
+
+SQLSTATE: XX005
+
+CAUSE: “http request failed”
+
+ACTION: “check IAM config parameter”
+
+ERRMSG: “create KMS dek failed”
+
+SQLSTATE: XX005
+
+CAUSE: “KMS error”
+
+ACTION: “check KMS connect or config parameter”
+
+ERRMSG: “get KMS dek failed”
+
+SQLSTATE: XX005
+
+CAUSE: “KMS error”
+
+ACTION: “check KMS connect or config parameter”
+
+ERRMSG: “get KMS DEK is NULL”
+
+SQLSTATE: XX005
+
+CAUSE: “get KMS dek_plaintext failed”
+
+ACTION: “check KMS network or cipher is right”
+
+ERRMSG: “create matview with TDE failed”
+
+SQLSTATE: 0A000
+
+CAUSE: “TDE feature is not supported for Create materialized views”
+
+ACTION: “check CREATE syntax about create the materialized views”
+
+ERRMSG: “failed to add item to the index page”
+
+SQLSTATE: XX002
+
+CAUSE: “System error.”
+
+ACTION: “Check WARNINGS for the details.”
+
+ERRMSG: “index row size %lu exceeds maximum %lu for index '%s'”
+
+SQLSTATE: 54000
+
+CAUSE: “Values larger than 1⁄3 of a buffer page cannot be indexed.”
+
+ACTION: “Consider a function index of an MD5 hash of the value, or use full text indexing.”
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/1-logical-operators.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/1-logical-operators.md
new file mode 100644
index 0000000000000000000000000000000000000000..9aafdf6e57b1f9862a6e68551586a7df22b40c0f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/1-logical-operators.md
@@ -0,0 +1,26 @@
+---
+title: 逻辑操作符
+summary: 逻辑操作符
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 逻辑操作符
+
+常用的逻辑操作符有AND、OR和NOT，他们的运算结果有三个值，分别为TRUE、FALSE和NULL，其中NULL代表未知。他们运算优先级顺序为: NOT&gt;AND&gt;OR。
+
+运算规则请参见[表1](#运算规则表)，表中的a和b代表逻辑表达式。
+
+**表 1** 运算规则表<a id="运算规则表"> </a>
+
+| a     | b     | a **AND** b的结果 | a **OR** b的结果 | **NOT** a的结果 |
+| :---- | :---- | :---------------- | :--------------- | :-------------- |
+| TRUE  | TRUE  | TRUE              | TRUE             | FALSE           |
+| TRUE  | FALSE | FALSE             | TRUE             | FALSE           |
+| TRUE  | NULL  | NULL              | TRUE             | FALSE           |
+| FALSE | FALSE | FALSE             | FALSE            | TRUE            |
+| FALSE | NULL  | FALSE             | NULL             | TRUE            |
+| NULL  | NULL  | NULL              | NULL             | NULL            |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+> 操作符AND和OR具有交换性，即交换左右两个操作数，不影响其结果。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/10-geometric-functions-and-operators.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/10-geometric-functions-and-operators.md
new file mode 100644
index 0000000000000000000000000000000000000000..a3fc3e5ca4f159f0cd834e403ff6a7924e4e70f3
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/10-geometric-functions-and-operators.md
@@ -0,0 +1,948 @@
+---
+title: 几何函数和操作符
+summary: 几何函数和操作符
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 几何函数和操作符
+
+## 几何操作符
+
+- \+
+
+  描述：平移。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT box '((0,0),(1,1))' + point '(2.0,0)' AS RESULT;
+     result
+  -------------
+   (3,1),(2,0)
+  (1 row)
+  ```
+
+- \-
+
+  描述：平移。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT box '((0,0),(1,1))' - point '(2.0,0)' AS RESULT;
+      result
+  ---------------
+   (-1,1),(-2,0)
+  (1 row)
+  ```
+
+- \*
+
+  描述：伸展/旋转。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT box '((0,0),(1,1))' * point '(2.0,0)' AS RESULT;
+     result
+  -------------
+   (2,2),(0,0)
+  (1 row)
+  ```
+
+- /
+
+  描述：收缩/旋转。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT box '((0,0),(2,2))' / point '(2.0,0)' AS RESULT;
+     result
+  -------------
+   (1,1),(0,0)
+  (1 row)
+  ```
+
+- \#
+
+  描述：两个图形交面。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT box '((1,-1),(-1,1))' # box '((1,1),(-2,-2))' AS RESULT;
+   result
+  ---------------
+   (1,1),(-1,-1)
+  (1 row)
+  ```
+
+- \#
+
+  描述：图形的路径数目或多边形顶点数。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT # path'((1,0),(0,1),(-1,0))' AS RESULT;
+   result
+  --------
+        3
+  (1 row)
+  ```
+
+- @-@
+
+  描述：图形的长度或者周长。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT @-@ path '((0,0),(1,0))' AS RESULT;
+   result
+  --------
+        2
+  (1 row)
+  ```
+
+- @@
+
+  描述：图形的中心。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT @@ circle '((0,0),10)' AS RESULT;
+   result
+  --------
+   (0,0)
+  (1 row)
+  ```
+
+- &lt;-&gt;
+
+  描述：两个图形之间的距离。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT circle '((0,0),1)' <-> circle '((5,0),1)' AS RESULT;
+   result
+  --------
+        3
+  (1 row)
+  ```
+
+- &&
+
+  描述：两个图形是否重叠（有一个共同点就为真）。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT box '((0,0),(1,1))' && box '((0,0),(2,2))' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;&lt;
+
+  描述：图形是否全部在另一个图形的左边（没有相同的横坐标）。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT circle '((0,0),1)' << circle '((5,0),1)' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &gt;&gt;
+
+  描述：图形是否全部在另一个图形的右边（没有相同的横坐标）。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT circle '((5,0),1)' >> circle '((0,0),1)' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &&lt;
+
+  描述：图形的最右边是否不超过在另一个图形的最右边。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT box '((0,0),(1,1))' &< box '((0,0),(2,2))' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &&gt;
+
+  描述：图形的最左边是否不超过在另一个图形的最左边。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT box '((0,0),(3,3))' &> box '((0,0),(2,2))' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;&lt;|
+
+  描述：图形是否全部在另一个图形的下边（没有相同的纵坐标）。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT box '((0,0),(3,3))' <<| box '((3,4),(5,5))' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- |&gt;&gt;
+
+  描述：图形是否全部在另一个图形的上边（没有相同的纵坐标）。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT box '((3,4),(5,5))' |>> box '((0,0),(3,3))' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &&lt;|
+
+  描述：图形的最上边是否不超过另一个图形的最上边。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT box '((0,0),(1,1))' &<| box '((0,0),(2,2))' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- |&&gt;
+
+  描述：图形的最下边是否不超过另一个图形的最下边。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT box '((0,0),(3,3))' |&> box '((0,0),(2,2))' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;^
+
+  描述：图形是否低于另一个图形（允许两个图形有接触）。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT box '((0,0),(-3,-3))' <^ box '((0,0),(2,2))' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &gt;^
+
+  描述：图形是否高于另一个图形（允许两个图形有接触）。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT box '((0,0),(2,2))' >^ box '((0,0),(-3,-3))'  AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- ?#
+
+  描述：两个图形是否相交。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT lseg '((-1,0),(1,0))' ?# box '((-2,-2),(2,2))' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- ?-
+
+  描述：图形是否处于水平位置。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT ?- lseg '((-1,0),(1,0))' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- ?-
+
+  描述：图形是否水平对齐。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT point '(1,0)' ?- point '(0,0)' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- ?|
+
+  描述：图形是否处于竖直位置。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT ?| lseg '((-1,0),(1,0))' AS RESULT;
+   result
+  --------
+   f
+  (1 row)
+  ```
+
+- ?|
+
+  描述：图形是否竖直对齐。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT point '(0,1)' ?| point '(0,0)' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- ?-|
+
+  描述：两条线是否垂直。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT lseg '((0,0),(0,1))' ?-| lseg '((0,0),(1,0))' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- ?||
+
+  描述：两条线是否平行。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT lseg '((-1,0),(1,0))' ?|| lseg '((-1,2),(1,2))' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- @&gt;
+
+  描述：图形是否包含另一个图形。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT circle '((0,0),2)' @> point '(1,1)' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;@
+
+  描述：图形是否被包含于另一个图形。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT point '(1,1)' <@ circle '((0,0),2)' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- ~=
+
+  描述：两个图形是否相同。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT polygon '((0,0),(1,1))' ~= polygon '((1,1),(0,0))' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+## 几何函数
+
+- area(object)
+
+  描述：计算图形的面积。
+
+  返回类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT area(box '((0,0),(1,1))') AS RESULT;
+   result
+  --------
+        1
+  (1 row)
+  ```
+
+- center(object)
+
+  描述：计算图形的中心。
+
+  返回类型：point
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT center(box '((0,0),(1,2))') AS RESULT;
+   result
+  ---------
+   (0.5,1)
+  (1 row)
+  ```
+
+- diameter(circle)
+
+  描述：计算圆的直径。
+
+  返回类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT diameter(circle '((0,0),2.0)') AS RESULT;
+   result
+  --------
+        4
+  (1 row)
+  ```
+
+- height(box)
+
+  描述：矩形的竖直高度。
+
+  返回类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT height(box '((0,0),(1,1))') AS RESULT;
+   result
+  --------
+        1
+  (1 row)
+  ```
+
+- isclosed(path)
+
+  描述：图形是否为闭合路径。
+
+  返回类型：Boolean
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT isclosed(path '((0,0),(1,1),(2,0))') AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- isopen(path)
+
+  描述：图形是否为开放路径。
+
+  返回类型：Boolean
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT isopen(path '[(0,0),(1,1),(2,0)]') AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- length(object)
+
+  描述：计算图形的长度。
+
+  返回类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT length(path '((-1,0),(1,0))') AS RESULT;
+   result
+  --------
+        4
+  (1 row)
+  ```
+
+- npoints(path)
+
+  描述：计算路径的顶点数。
+
+  返回类型：int
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT npoints(path '[(0,0),(1,1),(2,0)]') AS RESULT;
+   result
+  --------
+        3
+  (1 row)
+  ```
+
+- npoints(polygon)
+
+  描述：计算多边形的顶点数。
+
+  返回类型：int
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT npoints(polygon '((1,1),(0,0))') AS RESULT;
+   result
+  --------
+        2
+  (1 row)
+  ```
+
+- pclose(path)
+
+  描述：把路径转换为闭合路径。
+
+  返回类型：path
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT pclose(path '[(0,0),(1,1),(2,0)]') AS RESULT;
+         result
+  ---------------------
+   ((0,0),(1,1),(2,0))
+  (1 row)
+  ```
+
+- popen(path)
+
+  描述：把路径转换为开放路径。
+
+  返回类型：path
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT popen(path '((0,0),(1,1),(2,0))') AS RESULT;
+         result
+  ---------------------
+   [(0,0),(1,1),(2,0)]
+  (1 row)
+  ```
+
+- radius(circle)
+
+  描述：计算圆的半径。
+
+  返回类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT radius(circle '((0,0),2.0)') AS RESULT;
+   result
+  --------
+        2
+  (1 row)
+  ```
+
+- width(box)
+
+  描述：计算矩形的水平尺寸。
+
+  返回类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT width(box '((0,0),(1,1))') AS RESULT;
+   result
+  --------
+        1
+  (1 row)
+  ```
+
+## 几何类型转换函数
+
+- box(circle)
+
+  描述：将圆转换成矩形
+
+  返回类型：box
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT box(circle '((0,0),2.0)') AS RESULT;
+                                    result
+  ---------------------------------------------------------------------------
+   (1.41421356237309,1.41421356237309),(-1.41421356237309,-1.41421356237309)
+  (1 row)
+  ```
+
+- box(point, point)
+
+  描述：将点转换成矩形
+
+  返回类型：box
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT box(point '(0,0)', point '(1,1)') AS RESULT;
+     result
+  -------------
+   (1,1),(0,0)
+  (1 row)
+  ```
+
+- box(polygon)
+
+  描述：将多边形转换成矩形
+
+  返回类型：box
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT box(polygon '((0,0),(1,1),(2,0))') AS RESULT;
+     result
+  -------------
+   (2,1),(0,0)
+  (1 row)
+  ```
+
+- circle(box)
+
+  描述：矩形转换成圆
+
+  返回类型：circle
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT circle(box '((0,0),(1,1))') AS RESULT;
+              result
+  -------------------------------
+   <(0.5,0.5),0.707106781186548>
+  (1 row)
+  ```
+
+- circle(point, double precision)
+
+  描述：将圆心和半径转换成圆
+
+  返回类型：circle
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT circle(point '(0,0)', 2.0) AS RESULT;
+    result
+  -----------
+   <(0,0),2>
+  (1 row)
+  ```
+
+- circle(polygon)
+
+  描述：将多边形转换成圆
+
+  返回类型：circle
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT circle(polygon '((0,0),(1,1),(2,0))') AS RESULT;
+                    result
+  -------------------------------------------
+   <(1,0.333333333333333),0.924950591148529>
+  (1 row)
+  ```
+
+- lseg(box)
+
+  描述：矩形对角线转化成线段
+
+  返回类型：lseg
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT lseg(box '((-1,0),(1,0))') AS RESULT;
+       result
+  ----------------
+   [(1,0),(-1,0)]
+  (1 row)
+  ```
+
+- lseg(point, point)
+
+  描述：点转换成线段
+
+  返回类型：lseg
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT lseg(point '(-1,0)', point '(1,0)') AS RESULT;
+       result
+  ----------------
+   [(-1,0),(1,0)]
+  (1 row)
+  ```
+
+- slope(point, point)
+
+    描述：计算两个点构成直线的斜率
+
+    返回类型： double
+
+    示例：
+
+    ```
+    mogdb=# SELECT slope(point '(1,1)', point '(0,0)') AS RESULT;
+     result
+    --------
+          1
+    (1 row)
+    ```
+
+- path(polygon)
+
+  描述：多边形转换成路径
+
+  返回类型：path
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT path(polygon '((0,0),(1,1),(2,0))') AS RESULT;
+         result
+  ---------------------
+   ((0,0),(1,1),(2,0))
+  (1 row)
+  ```
+
+- point(double precision, double precision)
+
+  描述：节点
+
+  返回类型：point
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT point(23.4, -44.5) AS RESULT;
+      result
+  --------------
+   (23.4,-44.5)
+  (1 row)
+  ```
+
+- point(box)
+
+  描述：矩形的中心
+
+  返回类型：point
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT point(box '((-1,0),(1,0))') AS RESULT;
+   result
+  --------
+   (0,0)
+  (1 row)
+  ```
+
+- point(circle)
+
+  描述：圆心
+
+  返回类型：point
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT point(circle '((0,0),2.0)') AS RESULT;
+   result
+  --------
+   (0,0)
+  (1 row)
+  ```
+
+- point(lseg)
+
+  描述：线段的中心
+
+  返回类型：point
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT point(lseg '((-1,0),(1,0))') AS RESULT;
+   result
+  --------
+   (0,0)
+  (1 row)
+  ```
+
+- point(polygon)
+
+  描述：多边形的中心
+
+  返回类型：point
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT point(polygon '((0,0),(1,1),(2,0))') AS RESULT;
+          result
+  -----------------------
+   (1,0.333333333333333)
+  (1 row)
+  ```
+
+- polygon(box)
+
+  描述：矩形转换成4点多边形
+
+  返回类型：polygon
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT polygon(box '((0,0),(1,1))') AS RESULT;
+            result
+  ---------------------------
+   ((0,0),(0,1),(1,1),(1,0))
+  (1 row)
+  ```
+
+- polygon(circle)
+
+  描述：圆转换成12点多边形
+
+  返回类型：polygon
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT polygon(circle '((0,0),2.0)') AS RESULT;
+                                                                                                                                                  result
+
+  -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+   ((-2,0),(-1.73205080756888,1),(-1,1.73205080756888),(-1.22464679914735e-16,2),(1,1.73205080756888),(1.73205080756888,1),(2,2.44929359829471e-16),(1.73205080756888,-0.999999999999999),(1,-1.73205080756888),(3.67394039744206e-16,-2),(-0.999999999999999,-1.73205080756888),(-1.73205080756888,-1))
+  (1 row)
+  ```
+
+- polygon(npts, circle)
+
+  描述：圆转换成npts点多边形
+
+  返回类型：polygon
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT polygon(12, circle '((0,0),2.0)') AS RESULT;
+                                                                                                                                                  result
+
+  -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+   ((-2,0),(-1.73205080756888,1),(-1,1.73205080756888),(-1.22464679914735e-16,2),(1,1.73205080756888),(1.73205080756888,1),(2,2.44929359829471e-16),(1.73205080756888,-0.999999999999999),(1,-1.73205080756888),(3.67394039744206e-16,-2),(-0.999999999999999,-1.73205080756888),(-1.73205080756888,-1))
+  (1 row)
+  ```
+
+- polygon(path)
+
+  描述：路径转换成多边形
+
+  返回类型：polygon
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT polygon(path '((0,0),(1,1),(2,0))') AS RESULT;
+         result
+  ---------------------
+   ((0,0),(1,1),(2,0))
+  (1 row)
+  ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/11-network-address-functions-and-operators.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/11-network-address-functions-and-operators.md
new file mode 100644
index 0000000000000000000000000000000000000000..09ae70f2087c00da52a826258de9e4d4c650fd14
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/11-network-address-functions-and-operators.md
@@ -0,0 +1,456 @@
+---
+title: 网络地址函数和操作符
+summary: 网络地址函数和操作符
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 网络地址函数和操作符
+
+## cidr和inet操作符
+
+操作符&lt;&lt;、&lt;&lt;=、&gt;&gt;、&gt;&gt;=对子网进行测试。它们只考虑两个地址的网络部分（忽略任何主机部分），然后判断其中一个网络是等于另外一个网络，还是另外一个网络的子网。
+
+- &lt;
+
+  描述：小于
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT inet '192.168.1.5' < inet '192.168.1.6' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;=
+
+  描述：小于或等于
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT inet '192.168.1.5' <= inet '192.168.1.5' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- =
+
+  描述：等于
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT inet '192.168.1.5' = inet '192.168.1.5' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &gt;=
+
+  描述：大于或等于
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT inet '192.168.1.5' >= inet '192.168.1.5' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &gt;
+
+  描述：大于
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT inet '192.168.1.5' > inet '192.168.1.4' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;&gt;
+
+  描述：不等于
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT inet '192.168.1.5' <> inet '192.168.1.4' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;&lt;
+
+  描述：包含于
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT inet '192.168.1.5' << inet '192.168.1/24' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;&lt;=
+
+  描述：包含于或等于
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT inet '192.168.1/24' <<= inet '192.168.1/24' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &gt;&gt;
+
+  描述：包含
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT inet '192.168.1/24' >> inet '192.168.1.5' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &gt;&gt;=
+
+  描述：包含或等于
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT inet '192.168.1/24' >>= inet '192.168.1/24' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- ~
+
+  描述：位非
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT ~ inet '192.168.1.6' AS RESULT;
+      result
+  ---------------
+   63.87.254.249
+  (1 row)
+  ```
+
+- &
+
+  描述：两个网络地址的每一位都进行“与”操作
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT inet '192.168.1.6' & inet '10.0.0.0' AS RESULT;
+   result
+  ---------
+   0.0.0.0
+  (1 row)
+  ```
+
+- |
+
+  描述：两个网络地址的每一位都进行“或”操作
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT inet '192.168.1.6' | inet '10.0.0.0' AS RESULT;
+     result
+  -------------
+   202.168.1.6
+  (1 row)
+  ```
+
+- \+
+
+  描述：加
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT inet '192.168.1.6' + 25 AS RESULT;
+      result
+  --------------
+   192.168.1.31
+  (1 row)
+  ```
+
+- \-
+
+  描述：减
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT inet '192.168.1.43' - 36 AS RESULT;
+     result
+  -------------
+   192.168.1.7
+  (1 row)
+  ```
+
+- \-
+
+  描述：减
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT inet '192.168.1.43' - inet '192.168.1.19' AS RESULT;
+   result
+  --------
+       24
+  (1 row)
+  ```
+
+## cidr和inet函数
+
+函数abbrev、host、text主要是为了提供可选的显示格式。
+
+- abbrev(inet)
+
+  描述：缩写显示格式文本。
+
+  返回类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT abbrev(inet '10.1.0.0/16') AS RESULT;
+     result
+  -------------
+   10.1.0.0/16
+  (1 row)
+  ```
+
+- abbrev(cidr)
+
+  描述：缩写显示格式文本。
+
+  返回类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT abbrev(cidr '10.1.0.0/16') AS RESULT;
+   result
+  ---------
+   10.1/16
+  (1 row)
+  ```
+
+- broadcast(inet)
+
+  描述：网络广播地址。
+
+  返回类型：inet
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT broadcast('192.168.1.5/24') AS RESULT;
+        result
+  ------------------
+   192.168.1.255/24
+  (1 row)
+  ```
+
+- family(inet)
+
+  描述：抽取地址族，4为IPv4，6为IPv6。
+
+  返回类型：int
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT family('127.0.0.1') AS RESULT;
+   result
+  --------
+        4
+  (1 row)
+  ```
+
+- host(inet)
+
+  描述：将主机地址类型抽出为文本。
+
+  返回类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT host('192.168.1.5/24') AS RESULT;
+     result
+  -------------
+   192.168.1.5
+  (1 row)
+  ```
+
+- hostmask(inet)
+
+  描述：为网络构造主机掩码。
+
+  返回类型：inet
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT hostmask('192.168.23.20/30') AS RESULT;
+   result
+  ---------
+   0.0.0.3
+  (1 row)
+  ```
+
+- masklen(inet)
+
+  描述：抽取子网掩码长度。
+
+  返回类型：int
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT masklen('192.168.1.5/24') AS RESULT;
+   result
+  --------
+       24
+  (1 row)
+  ```
+
+- netmask(inet)
+
+  描述：为网络构造子网掩码。
+
+  返回类型：inet
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT netmask('192.168.1.5/24') AS RESULT;
+      result
+  ---------------
+   255.255.255.0
+  (1 row)
+  ```
+
+- network(inet)
+
+  描述：抽取地址的网络部分。
+
+  返回类型：cidr
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT network('192.168.1.5/24') AS RESULT;
+       result
+  ----------------
+   192.168.1.0/24
+  (1 row)
+  ```
+
+- set_masklen(inet, int)
+
+  描述：为inet数值设置子网掩码长度。
+
+  返回类型：inet
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT set_masklen('192.168.1.5/24', 16) AS RESULT;
+       result
+  ----------------
+   192.168.1.5/16
+  (1 row)
+  ```
+
+- set_masklen(cidr, int)
+
+  描述：为cidr数值设置子网掩码长度。
+
+  返回类型：cidr
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT set_masklen('192.168.1.0/24'::cidr, 16) AS RESULT;
+       result
+  ----------------
+   192.168.0.0/16
+  (1 row)
+  ```
+
+- text(inet)
+
+  描述：把IP地址和掩码长度抽取为文本。
+
+  返回类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT text(inet '192.168.1.5') AS RESULT;
+       result
+  ----------------
+   192.168.1.5/32
+  (1 row)
+  ```
+
+任何cidr值都能以显式或者隐式的方式转换为inet值，因此上述能够操作inet值的函数也同样能够操作cidr值。inet值也可以转换为cidr值，此时inet子网掩码右侧的所有位都将转换为零，以创建一个有效的cidr值。另外，用户还可以使用常规的类型转换语法将一个文本字符串转换为inet或cidr值。例如：inet(expression)或colname::cidr。
+
+## macaddr函数
+
+函数trunc(macaddr)返回一个MAC地址，该地址的最后三个字节设置为零。
+
+- trunc(macaddr)
+
+  描述：把后三个字节置为零。
+
+  返回类型：macaddr
+
+  示例：
+
+```sql
+mogdb=# SELECT trunc(macaddr '12:34:56:78:90:ab') AS RESULT;
+      result
+-------------------
+ 12:34:56:00:00:00
+(1 row)
+```
+
+macaddr类型还支持标准关系操作符（&gt;、&lt;=等）用于词法排序，和按位运算符（~、&和|）非、与和或。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/12-text-search-functions-and-operators.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/12-text-search-functions-and-operators.md
new file mode 100644
index 0000000000000000000000000000000000000000..bca5bf48c945e1864e5062a7534d13d2b05d33b8
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/12-text-search-functions-and-operators.md
@@ -0,0 +1,535 @@
+---
+title: 文本检索函数和操作符
+summary: 文本检索函数和操作符
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 文本检索函数和操作符
+
+## 文本检索操作符
+
+- @@
+
+  描述: tsvector类型的词汇与tsquery类型的词汇是否匹配
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT to_tsvector('fat cats ate rats') @@ to_tsquery('cat & rat') AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- @@@
+
+  描述: @@的同义词
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT to_tsvector('fat cats ate rats') @@@ to_tsquery('cat & rat') AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- ||
+
+  描述: 连接两个tsvector类型的词汇
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT 'a:1 b:2'::tsvector || 'c:1 d:2 b:3'::tsvector AS RESULT;
+            result
+  ---------------------------
+   'a':1 'b':2,5 'c':3 'd':4
+  (1 row)
+  ```
+
+- &&
+
+  描述: 将两个tsquery类型的词汇进行"与"操作
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT 'fat | rat'::tsquery && 'cat'::tsquery AS RESULT;
+            result
+  ---------------------------
+   ( 'fat' | 'rat' ) & 'cat'
+  (1 row)
+  ```
+
+- ||
+
+  描述: 将两个tsquery类型的词汇进行"或"操作
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT 'fat | rat'::tsquery || 'cat'::tsquery AS RESULT;
+            result
+  ---------------------------
+   ( 'fat' | 'rat' ) | 'cat'
+  (1 row)
+  ```
+
+- !!
+
+  描述: tsquery类型词汇的非关系
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT !! 'cat'::tsquery AS RESULT;
+   result
+  --------
+   !'cat'
+  (1 row)
+  ```
+
+- @&gt;
+
+  描述: 一个tsquery类型的词汇是否包含另一个tsquery类型的词汇
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT 'cat'::tsquery @> 'cat & rat'::tsquery AS RESULT;
+   result
+  --------
+   f
+  (1 row)
+  ```
+
+- &lt;@
+
+  描述: 一个tsquery类型的词汇是否被包含另一个tsquery类型的词汇
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT 'cat'::tsquery <@ 'cat & rat'::tsquery AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+除了上述的操作符，还为tsvector类型和tsquery类型的数据定义了普通的B-tree比较操作符（=、&lt;等）。
+
+## 文本检索函数
+
+- get_current_ts_config()
+
+  描述: 获取文本检索的默认配置。
+
+  返回类型: regconfig
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT get_current_ts_config();
+   get_current_ts_config
+  -----------------------
+   english
+  (1 row)
+  ```
+
+- length(tsvector)
+
+  描述: tsvector类型词汇的单词数。
+
+  返回类型: integer
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT length('fat:2,4 cat:3 rat:5A'::tsvector);
+   length
+  --------
+        3
+  (1 row)
+  ```
+
+- numnode(tsquery)
+
+  描述: tsquery类型的单词加上操作符的数量。
+
+  返回类型: integer
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT numnode('(fat & rat) | cat'::tsquery);
+   numnode
+  ---------
+         5
+  (1 row)
+  ```
+
+- plainto_tsquery([ config regconfig , ] query text)
+
+  描述: 产生tsquery类型的词汇，并忽略标点。
+
+  返回类型: tsquery
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT plainto_tsquery('english', 'The Fat Rats');
+   plainto_tsquery
+  -----------------
+   'fat' & 'rat'
+  (1 row)
+  ```
+
+- querytree(query tsquery)
+
+  描述: 获取tsquery类型的词汇可加索引的部分。
+
+  返回类型: text
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT querytree('foo & ! bar'::tsquery);
+   querytree
+  -----------
+   'foo'
+  (1 row)
+  ```
+
+- setweight(tsvector, "char")
+
+  描述: 给tsvector类型的每个元素分配权值。
+
+  返回类型: tsvector
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT setweight('fat:2,4 cat:3 rat:5B'::tsvector, 'A');
+             setweight
+  -------------------------------
+   'cat':3A 'fat':2A,4A 'rat':5A
+  (1 row)
+  ```
+
+- strip(tsvector)
+
+  描述: 删除tsvector类型单词中的position和权值。
+
+  返回类型: tsvector
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT strip('fat:2,4 cat:3 rat:5A'::tsvector);
+         strip
+  -------------------
+   'cat' 'fat' 'rat'
+  (1 row)
+  ```
+
+- to_tsquery([ config regconfig , ] query text)
+
+  描述: 标准化单词，并转换为tsquery类型。
+
+  返回类型: tsquery
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT to_tsquery('english', 'The & Fat & Rats');
+    to_tsquery
+  ---------------
+   'fat' & 'rat'
+  (1 row)
+  ```
+
+- to_tsvector([ config regconfig , ] document text)
+
+  描述: 去除文件信息，并转换为tsvector类型。
+
+  返回类型: tsvector
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT to_tsvector('english', 'The Fat Rats');
+     to_tsvector
+  -----------------
+   'fat':2 'rat':3
+  (1 row)
+  ```
+
+- to_tsvector_for_batch([ config regconfig , ] document text)
+
+    描述：去除文件信息，并转换为tsvector类型。
+
+    返回类型：tsvector
+
+    示例：
+
+    ```sql
+    mogdb=# SELECT to_tsvector_for_batch('english', 'The Fat Rats');
+       to_tsvector
+    -----------------
+     'fat':2 'rat':3
+    (1 row)
+    ```
+
+- ts_headline([ config regconfig, ] document text, query tsquery [, options text ])
+
+  描述: 高亮显示查询的匹配项。
+
+  返回类型: text
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT ts_headline('x y z', 'z'::tsquery);
+   ts_headline
+  --------------
+   x y <b>z</b>
+  (1 row)
+  ```
+
+- ts_rank([ weights float4[], ] vector tsvector, query tsquery [, normalization integer ])
+
+  描述: 文档查询排名。
+
+  返回类型: float4
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT ts_rank('hello world'::tsvector, 'world'::tsquery);
+   ts_rank
+  ----------
+   .0607927
+  (1 row)
+  ```
+
+- ts_rank_cd([ weights float4[], ] vector tsvector, query tsquery [, normalization integer ])
+
+  描述: 排序文件查询使用覆盖密度。
+
+  返回类型: float4
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT ts_rank_cd('hello world'::tsvector, 'world'::tsquery);
+   ts_rank_cd
+  ------------
+            .1
+  (1 row)
+  ```
+
+- ts_rewrite(query tsquery, target tsquery, substitute tsquery)
+
+  描述: 替换目标tsquery类型的单词。
+
+  返回类型: tsquery
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT ts_rewrite('a & b'::tsquery, 'a'::tsquery, 'foo|bar'::tsquery);
+         ts_rewrite
+  -------------------------
+   'b' & ( 'foo' | 'bar' )
+  (1 row)
+  ```
+
+- ts_rewrite(query tsquery, select text)
+
+  描述: 使用SELECT命令的结果替代目标中tsquery类型的单词。
+
+  返回类型: tsquery
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT ts_rewrite('world'::tsquery, 'select ''world''::tsquery, ''hello''::tsquery');
+   ts_rewrite
+  ------------
+   'hello'
+  (1 row)
+  ```
+
+## 文本检索调试函数
+
+- ts_debug([ config regconfig, ] document text, OUT alias text, OUT description text, OUT token text, OUT dictionaries regdictionary[], OUT dictionary regdictionary, OUT lexemes text[])
+
+  描述: 测试一个配置。
+
+  返回类型: setof record
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT ts_debug('english', 'The Brightest supernovaes');
+                                       ts_debug
+  -----------------------------------------------------------------------------------
+   (asciiword,"Word, all ASCII",The,{english_stem},english_stem,{})
+   (blank,"Space symbols"," ",{},,)
+   (asciiword,"Word, all ASCII",Brightest,{english_stem},english_stem,{brightest})
+   (blank,"Space symbols"," ",{},,)
+   (asciiword,"Word, all ASCII",supernovaes,{english_stem},english_stem,{supernova})
+  (5 rows)
+  ```
+
+- ts_lexize(dict regdictionary, token text)
+
+  描述: 测试一个数据字典。
+
+  返回类型: text[]
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT ts_lexize('english_stem', 'stars');
+   ts_lexize
+  -----------
+   {star}
+  (1 row)
+  ```
+
+- ts_parse(parser_name text, document text, OUT tokid integer, OUT token text)
+
+  描述: 测试一个解析。
+
+  返回类型: setof record
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT ts_parse('default', 'foo - bar');
+   ts_parse
+  -----------
+   (1,foo)
+   (12," ")
+   (12,"- ")
+   (1,bar)
+  (4 rows)
+  ```
+
+- ts_parse(parser_oid oid, document text, OUT tokid integer, OUT token text)
+
+  描述: 测试一个解析。
+
+  返回类型: setof record
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT ts_parse(3722, 'foo - bar');
+   ts_parse
+  -----------
+   (1,foo)
+   (12," ")
+   (12,"- ")
+   (1,bar)
+  (4 rows)
+  ```
+
+- ts_token_type(parser_name text, OUT tokid integer, OUT alias text, OUT description text)
+
+  描述: 获取分析器定义的记号类型。
+
+  返回类型: setof record
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT ts_token_type('default');
+                          ts_token_type
+  --------------------------------------------------------------
+   (1,asciiword,"Word, all ASCII")
+   (2,word,"Word, all letters")
+   (3,numword,"Word, letters and digits")
+   (4,email,"Email address")
+   (5,url,URL)
+   (6,host,Host)
+   (7,sfloat,"Scientific notation")
+   (8,version,"Version number")
+   (9,hword_numpart,"Hyphenated word part, letters and digits")
+   (10,hword_part,"Hyphenated word part, all letters")
+   (11,hword_asciipart,"Hyphenated word part, all ASCII")
+   (12,blank,"Space symbols")
+   (13,tag,"XML tag")
+   (14,protocol,"Protocol head")
+   (15,numhword,"Hyphenated word, letters and digits")
+   (16,asciihword,"Hyphenated word, all ASCII")
+   (17,hword,"Hyphenated word, all letters")
+   (18,url_path,"URL path")
+   (19,file,"File or path name")
+   (20,float,"Decimal notation")
+   (21,int,"Signed integer")
+   (22,uint,"Unsigned integer")
+   (23,entity,"XML entity")
+  (23 rows)
+  ```
+
+- ts_token_type(parser_oid oid, OUT tokid integer, OUT alias text, OUT description text)
+
+  描述: 获取分析器定义的记号类型。
+
+  返回类型: setof record
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT ts_token_type(3722);
+                          ts_token_type
+  --------------------------------------------------------------
+   (1,asciiword,"Word, all ASCII")
+   (2,word,"Word, all letters")
+   (3,numword,"Word, letters and digits")
+   (4,email,"Email address")
+   (5,url,URL)
+   (6,host,Host)
+   (7,sfloat,"Scientific notation")
+   (8,version,"Version number")
+   (9,hword_numpart,"Hyphenated word part, letters and digits")
+   (10,hword_part,"Hyphenated word part, all letters")
+   (11,hword_asciipart,"Hyphenated word part, all ASCII")
+   (12,blank,"Space symbols")
+   (13,tag,"XML tag")
+   (14,protocol,"Protocol head")
+   (15,numhword,"Hyphenated word, letters and digits")
+   (16,asciihword,"Hyphenated word, all ASCII")
+   (17,hword,"Hyphenated word, all letters")
+   (18,url_path,"URL path")
+   (19,file,"File or path name")
+   (20,float,"Decimal notation")
+   (21,int,"Signed integer")
+   (22,uint,"Unsigned integer")
+   (23,entity,"XML entity")
+  (23 rows)
+  ```
+
+- ts_stat(sqlquery text, [ weights text, ] OUT word text, OUT ndoc integer, OUT nentry integer)
+
+  描述: 获取tsvector列的统计数据。
+
+  返回类型: setof record
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT ts_stat('select ''hello world''::tsvector');
+     ts_stat
+  -------------
+   (world,1,1)
+   (hello,1,1)
+  (2 rows)
+  ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/13-json-functions.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/13-json-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..c7b8c637fc92da8ba7a1cf92122045bd95d37621
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/13-json-functions.md
@@ -0,0 +1,746 @@
+---
+title: JSON/JSONB函数和操作符
+summary: JSON/JSONB函数和操作符
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# JSON/JSONB函数和操作符
+
+JSON/JSONB数据类型参考[JSON/JSONB类型](12-json-types)。
+
+**表 1** JSON/JSONB通用操作符
+
+| 操作符 | 左操作数类型       | 右操作数类型 | 返回类型 | 描述                                           | 例子                                             | 例子结果     |
+| :----- | :----------------- | :----------- | :------- | :--------------------------------------------- | :----------------------------------------------- | :----------- |
+| ->     | Array-json(b)      | int          | json(b)  | 获得array-json元素。下标不存在返回空。         | '[{“a”:“foo”},{“b”:“bar”},{“c”:“baz”}]'::json->2 | {“c”:“baz”}  |
+| ->     | object-json(b)     | text         | json(b)  | 通过键获得值。不存在则返回空。                 | '{“a”: {“b”:“foo”}}'::json->'a'                  | {“b”:“foo”}  |
+| ->>    | Array-json(b)      | int          | text     | 获得JSON数组元素。下标不存在返回空。           | '[1,2,3]'::json->>2                              | 3            |
+| ->>    | object-json(b)     | text         | text     | 通过键获得值。不存在则返回空。                 | '{“a”:1,“b”:2}'::json->>'b'                      | 2            |
+| #>     | container-json (b) | text[]       | json(b)  | 获取在指定路径的JSON对象，路径不存在则返回空。 | '{“a”: {“b”:{“c”: “foo”}}}'::json #>'{a,b}'      | {“c”: “foo”} |
+| #>>    | container-json (b) | text[]       | text     | 获取在指定路径的JSON对象，路径不存在则返回空。 | '{“a”:[1,2,3],“b”:[4,5,6]}'::json #>>'{a,2}'     | 3            |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **注意：**
+>
+> 对于 #> 和 #>> 操作符，当给出的路径无法查找到数据时，不会报错，会返回空。
+
+**表 2** **jsonb额外支持操作符**
+
+| 操作符 | 右操作数类型 | 描述                                             | 例子                                               |
+| :----- | :----------- | :----------------------------------------------- | :------------------------------------------------- |
+| @>     | jsonb        | 左边的JSON的顶层是否包含右边JSON的顶层所有项。   | '{"a":1, "b":2}'::jsonb @> '{"b":2}'::jsonb        |
+| <@     | jsonb        | 左边的JSON的所有项是否全部存在于右边JSON的顶层。 | '{"b":2}'::jsonb <@ '{"a":1, "b":2}'::jsonb        |
+| ?      | text         | 键/元素的字符串是否存在于JSON值的顶层。          | '{"a":1, "b":2}'::jsonb ? 'b'                      |
+| ?\|    | text[]       | 这些数组字符串中的任何一个是否做为顶层键存在。   | '{"a":1, "b":2, "c":3}'::jsonb ?\| array['b', 'c'] |
+| ?&     | text[]       | 是否所有这些数组字符串都作为顶层键存在。         | '["a", "b"]'::jsonb ?& array['a', 'b']             |
+| =      | jsonb        | 判断两个jsonb的大小关系，同函数jsonb_eq。        | /                                                  |
+| <>     | jsonb        | 判断两个jsonb的大小关系，同函数jsonb_ne。        | /                                                  |
+| <      | jsonb        | 判断两个jsonb的大小关系，同函数jsonb_lt。        | /                                                  |
+| >      | jsonb        | 判断两个jsonb的大小关系，同函数jsonb_gt。        | /                                                  |
+| <=     | jsonb        | 判断两个jsonb的大小关系，同函数jsonb_le。        | /                                                  |
+| >=     | jsonb        | 判断两个jsonb的大小关系，同函数jsonb_ge。        | /                                                  |
+
+## **JSON/JSONB**支持的函数
+
+- array_to_json(anyarray [, pretty_bool])
+
+  描述：返回JSON类型的数组。一个多维数组成为一个JSON数组的数组。如果pretty_bool为true，将在一维元素之间添加换行符。
+
+  返回类型：json
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT array_to_json('{{1,5},{99,100}}'::int[]);
+      array_to_json
+      ------------------
+      [[1,5],[99,100]]
+      (1 row)
+  ```
+
+- row_to_json(record [, pretty_bool])
+
+  描述：返回JSON类型的行。如果pretty_bool为true，将在第一级元素之间添加换行符。
+
+  返回类型：json
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT row_to_json(row(1,'foo'));
+           row_to_json
+      ---------------------
+       {"f1":1,"f2":"foo"}    (1 row)
+  ```
+
+- json_array_element(array-json, integer)、jsonb_array_element(array-jsonb, integer)
+
+  描述：同操作符`->`，返回数组中指定下标的元素。
+
+  返回类型：json、jsonb
+
+  示例：
+
+  ```sql
+  mogdb=# select json_array_element('[1,true,[1,[2,3]],null]',2);
+    json_array_element
+    --------------------
+    [1,[2,3]]
+    (1 row)
+  ```
+
+- json_array_element_text(array-json, integer)、jsonb_array_element_text(array-jsonb, integer)
+
+  描述：同操作符`->>`，返回数组中指定下标的元素。
+
+  返回类型：text、text
+
+  示例：
+
+  ```sql
+  mogdb=# select json_array_element_text('[1,true,[1,[2,3]],null]',2);
+  json_array_element_text
+  -----------------------
+    [1,[2,3]]
+    (1 row)
+  ```
+
+- json_object_field(object-json, text)、jsonb_object_field(object-jsonb, text)
+
+  描述：同操作符`->`，返回对象中指定键对应的值。
+
+  返回类型：json、json
+
+  示例：
+
+  ```sql
+  mogdb=# select json_object_field('{"a": {"b":"foo"}}','a');
+   json_object_field
+   -------------------
+   {"b":"foo"}
+   (1 row)
+  ```
+
+- json_object_field_text(object-json, text)、jsonb_object_field_text(object-jsonb, text)
+
+  描述：同操作符`->>`，返回对象中指定键对应的值。
+
+  返回类型：text、text
+
+  示例：
+
+  ```sql
+  mogdb=# select json_object_field_text('{"a": {"b":"foo"}}','a');
+   json_object_field_text
+   ----------------------
+   {"b":"foo"}
+   (1 row)
+  ```
+
+- json_extract_path(json, VARIADIC text[])、jsonb_extract_path((jsonb, VARIADIC text[])
+
+  描述：等价于操作符`#>`。根据$2所指的路径，查找json，并返回。
+
+  返回类型：json、jsonb
+
+  示例：
+
+  ```sql
+  mogdb=# select json_extract_path('{"f2":{"f3":1},"f4":{"f5":99,"f6":"stringy"}}', 'f4','f6');
+    json_extract_path
+   -------------------
+    "stringy"
+   (1 row)
+  ```
+
+- json_extract_path_op(json, text[])、jsonb_extract_path_op(jsonb, text[])
+
+  描述：同操作符`#>`。根据$2所指的路径，查找json，并返回。
+
+  返回类型：json、jsonb
+
+  示例：
+
+  ```sql
+  mogdb=# select json_extract_path_op('{"f2":{"f3":1},"f4":{"f5":99,"f6":"stringy"}}', 'f4','f6');
+    json_extract_path_op
+   ---------------------
+    "stringy"
+   (1 row)
+  ```
+
+- json_extract_path_text(json, VARIADIC text[])、jsonb_extract_path_text((jsonb, VARIADIC text[])
+
+  描述：等价于操作符`#>>`。根据$2所指的路径，查找json，并返回。
+
+  返回类型：text、text
+
+  示例：
+
+  ```sql
+  mogdb=# select json_extract_path_text('{"f2":{"f3":1},"f4":{"f5":99,"f6":"stringy"}}', 'f4','f6');
+    json_extract_path_text
+   -----------------------
+    "stringy"
+   (1 row)
+  ```
+
+- json_extract_path_text_op(json, text[])、jsonb_extract_path_text_op(jsonb, text[])
+
+  描述：同操作符`#>>`。根据$2所指的路径，查找json，并返回。
+
+  返回类型：text、text
+
+  示例：
+
+  ```sql
+  mogdb=# select json_extract_path_text_op('{"f2":{"f3":1},"f4":{"f5":99,"f6":"stringy"}}', 'f4','f6');
+    json_extract_path_text_op
+   --------------------------
+    "stringy"
+   (1 row)
+  ```
+
+- json_array_elements(array-json)、jsonb_array_elements(array-jsonb)
+
+  描述：拆分数组，每一个元素返回一行。
+
+  返回类型：json、jsonb
+
+  示例：
+
+  ```sql
+  mogdb=# select json_array_elements('[1,true,[1,[2,3]],null]');
+    json_array_elements
+   ---------------------
+    1
+    true
+    [1,[2,3]]
+    null
+   (4 rows)
+  ```
+
+- json_array_elements_text(array-json)、jsonb_array_elements_text(array-jsonb)
+
+  描述：拆分数组，每一个元素返回一行。
+
+  返回类型：text、text
+
+  示例：
+
+  ```sql
+  mogdb=# select * from  json_array_elements_text('[1,true,[1,[2,3]],null]');
+       value
+    -----------
+     1
+     true
+     [1,[2,3]]
+
+    (4 rows)
+  ```
+
+- json_array_length(array-json)、jsonb_array_length(array-jsonb)
+
+  描述：返回数组长度。
+
+  返回类型：integer
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT json_array_length('[1,2,3,{"f1":1,"f2":[5,6]},4,null]');
+    json_array_length
+   -------------------
+                    6
+   (1 row)
+  ```
+
+- json_each(object-json)、jsonb_each(object-jsonb)
+
+  描述：将对象的每个键值对拆分转换成一行两列。
+
+  返回类型：setof(key text, value json)、setof(key text, value jsonb)
+
+  示例：
+
+  ```sql
+  mogdb=# select * from  json_each('{"f1":[1,2,3],"f2":{"f3":1},"f4":null}');
+    key |  value
+   -----+----------
+    f1  | [1,2,3]
+    f2  | {"f3":1}
+    f4  | null
+   (3 rows)
+  ```
+
+- json_each_text(object-json)、jsonb_each_text(object-jsonb)
+
+  描述：将对象的每个键值对拆分转换成一行两列。
+
+  返回类型：setof(key text, value text)、setof(key text, value text)
+
+  示例：
+
+  ```sql
+  mogdb=# select * from  json_each_text('{"f1":[1,2,3],"f2":{"f3":1},"f4":null}');
+    key |  value
+   -----+----------
+    f1  | [1,2,3]
+    f2  | {"f3":1}
+    f4  |
+   (3 rows)
+  ```
+
+- json_object_keys(object-json)、jsonb_object_keys(object-jsonb)
+
+  描述：返回对象中顶层的所有键。
+
+  返回类型：SETOF text
+
+  示例：
+
+  ```sql
+  mogdb=# select json_object_keys('{"f1":"abc","f2":{"f3":"a", "f4":"b"}, "f1":"abcd"}');
+    json_object_keys
+   ------------------
+    f1
+    f2
+    f1
+   (3 rows)
+  ```
+
+- jsonb中会有去重操作
+
+  ```sql
+  mogdb=# select jsonb_object_keys('{"f1":"abc","f2":{"f3":"a", "f4":"b"}, "f1":"abcd"}');
+    jsonb_object_keys
+   -------------------
+    f1
+    f2
+   (2 rows)
+  ```
+
+- json_populate_record(anyelement, object-json [, bool])、jsonb_populate_record(anyelement, object-jsonb [, bool])
+
+  描述：\$1必须是一个复合类型的参数。将会把object-json里的每个对键值进行拆分，以键当做列名，与\$1中的列名进行匹配查找，并填充到\$1的格式中。
+
+  返回类型：anyelement、anyelement
+
+  示例：
+
+  ```sql
+  mogdb=# create type jpop as (a text, b int, c bool);
+   CREATE TYPE
+   postgres=# select * from json_populate_record(null::jpop,'{"a":"blurfl","x":43.2}');
+      a    | b | c
+   --------+---+---
+    blurfl |   |
+   (1 row)
+  ```
+
+  ```sql
+  mogdb=# select * from json_populate_record((1,1,null)::jpop,'{"a":"blurfl","x":43.2}');
+       a    | b | c
+    --------+---+---
+     blurfl | 1 |
+    (1 row)
+  ```
+
+- json_populate_record_set(anyelement, array-json [, bool])、jsonb_populate_record_set(anyelement, array-jsonb [, bool])
+
+  描述：参考上述函数json_populate_record、jsonb_populate_record，对\$2数组的每一个元素进行上述参数函数的操作，因此这也要求\$2数组的每个元素都是object-json类型的。
+
+  返回类型：setof anyelement、setof anyelement
+
+  示例：
+
+  ```sql
+  mogdb=# create type jpop as (a text, b int, c bool);
+   CREATE TYPE
+   postgres=# select * from json_populate_recordset(null::jpop, '[{"a":1,"b":2},{"a":3,"b":4}]');
+    a | b | c
+   ---+---+---
+    1 | 2 |
+    3 | 4 |
+   (2 rows)
+  ```
+
+- json_typeof(json)、jsonb_typeof(jsonb)
+
+  描述：检测json类型。
+
+  返回类型：text、text
+
+  示例：
+
+  ```sql
+  mogdb=# select value, json_typeof(value)
+   postgres-# from (values (json '123.4'), (json '"foo"'), (json 'true'), (json 'null'), (json '[1, 2, 3]'), (json '{"x":"foo", "y":123}'), (NULL::json))  as data(value);
+           value         | json_typeof
+   ----------------------+-------------
+    123.4                | number
+    "foo"                | string
+    true                 | boolean
+    null                 | null
+    [1, 2, 3]            | array
+    {"x":"foo", "y":123} | object
+                         |
+   (7 rows)
+  ```
+
+- json_build_array( [VARIADIC “any”] )
+
+  描述：从一个可变参数列表构造出一个JSON数组。
+
+  返回类型：array-json
+
+  示例：
+
+  ```sql
+  mogdb=# select json_build_array('a',1,'b',1.2,'c',true,'d',null,'e',json '{"x": 3, "y": [1,2,3]}','');
+                                json_build_array
+   ---------------------------------------------------------------------------
+    ["a", 1, "b", 1.2, "c", true, "d", null, "e", {"x": 3, "y": [1,2,3]}, ""]
+   (1 row)
+  ```
+
+- json_build_object( [VARIADIC “any”] )
+
+  描述：从一个可变参数列表构造出一个JSON对象，其入参必须为偶数个，两两一组组成键值对。注意键不可为null。
+
+  返回类型：object-json
+
+  示例：
+
+  ```sql
+  mogdb=# select json_build_object(1,2);
+    json_build_object
+   -------------------
+    {"1" : 2}
+   (1 row)
+  ```
+
+- json_to_record(object-json, bool)
+
+  描述：正如所有返回record 的函数一样，调用者必须用一个AS子句显式地定义记录的结构。会将object-json的键值对进行拆分重组，把键当做列名，去匹配填充as显示指定的记录的结构。
+
+  返回类型：record
+
+  示例：
+
+  ```sql
+  mogdb=# select * from json_to_record('{"a":1,"b":"foo","c":"bar"}',true) as x(a int, b text, d text);
+     a |  b  | d
+    ---+-----+---
+     1 | foo |
+    (1 row)
+  ```
+
+- json_to_recordset(array-json, bool)
+
+  描述：参考函数json_to_record，对数组内个每个元素，执行上述函数的操作，因此这要求数组内的每个元素都得是object-json。
+
+  返回类型：setof record
+
+  示例：
+
+  ```sql
+  mogdb=# select * from json_to_recordset(
+   openGauss(#   '[{"a":1,"b":"foo","d":false},{"a":2,"b":"bar","c":true}]',
+  openGauss(#   false
+  openGauss(# ) as x(a int, b text, c boolean);
+    a |  b  | c
+   ---+-----+---
+    1 | foo |
+    2 | bar | t
+   (2 rows)
+  ```
+
+- json_object(text[])、json_object(text[], text[])
+
+  描述：从一个文本数组构造一个object-json。这是个重载函数，当入参为一个文本数组的时候，其数组长度必须为偶数，成员被当做交替出现的键/值对。两个文本数组的时候，第一个数组认为是键，第二个认为是值，两个数组长度必须相等。键不可为null。
+
+  返回类型：object-json
+
+  示例：
+
+  ```sql
+  mogdb=# select json_object('{a,1,b,2,3,NULL,"d e f","a b c"}');
+                          json_object
+    -------------------------------------------------------
+     {"a" : "1", "b" : "2", "3" : null, "d e f" : "a b c"}
+    (1 row)
+  ```
+
+  ```sql
+  mogdb=# select json_object('{a,b,"a b c"}', '{a,1,1}');
+                 json_object
+   ---------------------------------------
+    {"a" : "a", "b" : "1", "a b c" : "1"}
+   (1 row)
+  ```
+
+- json_agg(any)
+
+  描述：将值聚集为json数组。
+
+  返回类型：array-json
+
+  示例：
+
+  ```sql
+  mogdb=# select * from classes;
+   name | score
+   -----+-------
+   A    |     2
+   A    |     3
+   D    |     5
+   D    |
+   (4 rows)
+  ```
+
+  ```sql
+  mogdb=# select name, json_agg(score) score from classes group by name order by name;
+   name |      score
+   -----+-----------------
+   A    | [2, 3]
+   D    | [5, null]
+        | [null]
+   (3 rows)
+  ```
+
+- json_object_agg(any, any)
+
+  描述：将值聚集为json对象。
+
+  返回类型：object-json
+
+  示例：
+
+  ```sql
+  mogdb=# select * from classes;
+   name | score
+   -----+-------
+   A    |     2
+   A    |     3
+   D    |     5
+   D    |
+   (4 rows)
+  ```
+
+  ```sql
+  mogdb=# select json_object_agg(name, score) from classes group by name order by name;
+        json_object_agg
+   -------------------------
+    { "A" : 2, "A" : 3 }
+    { "D" : 5, "D" : null }
+   (2 rows)
+  ```
+
+- jsonb_contained(jsonb, jsonb)
+
+  描述：同操作符 `<@`，判断$1中的所有元素是否在$2的顶层存在。
+
+  返回类型：bool
+
+  示例：
+
+  ```sql
+  mogdb=# select jsonb_contained('[1,2,3]', '[1,2,3,4]');
+    jsonb_contained
+   -----------------
+    t
+   (1 row)
+  ```
+
+- jsonb_contains(jsonb, jsonb)
+
+  描述：同操作符 `@>`，判断$1中的顶层所有元素是否包含在$2的所有元素。
+
+  返回类型：bool
+
+  示例：
+
+  ```sql
+  mogdb=# select jsonb_contains('[1,2,3,4]', '[1,2,3]');
+    jsonb_contains
+   ----------------
+    t
+   (1 row)
+  ```
+
+- jsonb_exists(jsonb, text)
+
+  描述：同操作符 `?`，字符串$2是否存在$1的顶层以key,elem,scalar的形式存在。
+
+  返回类型：bool
+
+  示例：
+
+  ```sql
+  mogdb=# select jsonb_exists('["1",2,3]', '1');
+    jsonb_exists
+   --------------
+    t
+   (1 row)
+  ```
+
+- jsonb_exists_all(jsonb, text[])
+
+  描述：同操作符 `?&`，字符串数组$2里面，是否所有的元素，都在$1的顶层以key,elem,scalar的形式存在。
+
+  返回类型：bool
+
+  示例：
+
+  ```sql
+  mogdb=# select jsonb_exists_all('["1","2",3]', '{1, 2}');
+    jsonb_exists_all
+   ------------------
+    t
+   (1 row)
+  ```
+
+- jsonb_exists_any(jsonb, text[])
+
+  描述：同操作符 `?|`，字符串数组$2里面，是否存在的元素，在$1的顶层以key,elem,scalar的形式存在。
+
+  返回类型：bool
+
+  示例：
+
+  ```sql
+  mogdb=# select jsonb_exists_any('["1","2",3]', '{1, 2, 4}');
+    jsonb_exists_any
+   ------------------
+    t
+   (1 row)
+  ```
+
+- jsonb_cmp(jsonb, jsonb)
+
+  描述：比较大小，正数代表大于，负数代表小于，0表示相等。
+
+  返回类型：integer
+
+  示例：
+
+  ```sql
+  mogdb=# select jsonb_cmp('["a", "b"]', '{"a":1, "b":2}');
+     jsonb_cmp
+    -----------
+            -1
+    (1 row)
+  ```
+
+- jsonb_eq(jsonb, jsonb)
+
+  描述：同操作符 `=`，比较两个值的大小。
+
+  返回类型：bool
+
+  示例：
+
+  ```sql
+  mogdb=# select jsonb_eq('["a", "b"]', '{"a":1, "b":2}');
+    jsonb_eq
+   ----------
+    f
+   (1 row)
+  ```
+
+- jsonb_ne(jsonb, jsonb)
+
+  描述：同操作符 `<>`，比较两个值的大小。
+
+  返回类型：bool
+
+  示例：
+
+  ```sql
+  mogdb=# select jsonb_ne('["a", "b"]', '{"a":1, "b":2}');
+    jsonb_ne
+   ----------
+    t
+   (1 row)
+  ```
+
+- jsonb_gt(jsonb, jsonb)
+
+  描述：同操作符 `>`，比较两个值的大小。
+
+  返回类型：bool
+
+  示例：
+
+  ```sql
+  mogdb=# select jsonb_gt('["a", "b"]', '{"a":1, "b":2}');
+    jsonb_gt
+   ----------
+    f
+   (1 row)
+  ```
+
+- jsonb_ge(jsonb, jsonb)
+
+  描述：同操作符 `>=`，比较两个值的大小。
+
+  返回类型：bool
+
+  示例：
+
+  ```sql
+  mogdb=# select jsonb_ge('["a", "b"]', '{"a":1, "b":2}');
+    jsonb_ge
+   ----------
+    f
+   (1 row)
+  ```
+
+- jsonb_lt(jsonb, jsonb)
+
+  描述：同操作符 `<`，比较两个值的大小。
+
+  返回类型：bool
+
+  示例：
+
+  ```sql
+  mogdb=# select jsonb_lt('["a", "b"]', '{"a":1, "b":2}');
+    jsonb_lt
+   ----------
+    t
+   (1 row)
+  ```
+
+- jsonb_le(jsonb, jsonb)
+
+  描述：同操作符 `<=`，比较两个值的大小。
+
+  返回类型：bool
+
+  示例：
+
+  ```sql
+  mogdb=# select jsonb_le('["a", "b"]', '{"a":1, "b":2}');
+    jsonb_le
+   ----------
+    t
+   (1 row)
+  ```
+
+- to_json(anyelement)
+
+  描述：把参数转换为`json`。
+
+  返回类型：json
+
+  示例：
+
+  ```sql
+  mogdb=# select to_json('{1,5}'::text[]);
+     to_json
+   -----------
+    ["1","5"]
+   (1 row)
+  ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/13.1-hll-functions-and-operators.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/13.1-hll-functions-and-operators.md
new file mode 100644
index 0000000000000000000000000000000000000000..04bdb9a0d1a1e6b7e5fb346d05d8087e5499b5a9
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/13.1-hll-functions-and-operators.md
@@ -0,0 +1,878 @@
+---
+title: HLL函数和操作符
+summary: HLL函数和操作符
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# HLL函数和操作符
+
+## 哈希函数
+
+- hll_hash_boolean(bool)
+
+  描述：对bool类型数据计算哈希值。
+
+  返回值类型：hll_hashval
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT hll_hash_boolean(FALSE);
+    hll_hash_boolean
+  ---------------------
+   -5451962507482445012
+  (1 row)
+  ```
+
+- hll_hash_boolean(bool, int32)
+
+  描述：设置hash seed（即改变哈希策略）并对bool类型数据计算哈希值。
+
+  返回值类型：hll_hashval
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT hll_hash_boolean(FALSE, 10);
+    hll_hash_boolean
+  --------------------
+   -1169037589280886076
+  (1 row)
+  ```
+
+- hll_hash_smallint(smallint)
+
+  描述：对smallint类型数据计算哈希值。
+
+  返回值类型：hll_hashval
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT hll_hash_smallint(100::smallint);
+    hll_hash_smallint
+  ---------------------
+   962727970174027904
+  (1 row)
+  ```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 数值大小相同的参数使用不同数据类型的哈希函数计算，最后结果会不一样，因为不同类型哈希函数会选取不同的哈希计算策略。
+
+- hll_hash_smallint(smallint, int32)
+
+  描述：设置hash seed（即改变哈希策略）同时对smallint类型数据计算哈希值。
+
+  返回值类型：hll_hashval
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT hll_hash_smallint(100::smallint, 10);
+    hll_hash_smallint
+  ---------------------
+   -9056177146160443041
+  (1 row)
+  ```
+
+- hll_hash_integer(integer)
+
+  描述：对integer类型数据计算哈希值。
+
+  返回值类型：hll_hashval
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT hll_hash_integer(0);
+     hll_hash_integer
+  ----------------------
+   5156626420896634997
+  (1 row)
+  ```
+
+- hll_hash_integer(integer, int32)
+
+  描述：对integer类型数据计算哈希值，并设置hashseed（即改变哈希策略）。
+
+  返回值类型：hll_hashval
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT hll_hash_integer(0, 10);
+    hll_hash_integer
+  --------------------
+   -5035020264353794276
+  (1 row)
+  ```
+
+- hll_hash_bigint(bigint)
+
+  描述：对bigint类型数据计算哈希值。
+
+  返回值类型：hll_hashval
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT hll_hash_bigint(100::bigint);
+     hll_hash_bigint
+  ---------------------
+   -2401963681423227794
+  (1 row)
+  ```
+
+- hll_hash_bigint(bigint, int32)
+
+  描述：对bigint类型数据计算哈希值，并设置hashseed（即改变哈希策略）。
+
+  返回值类型：hll_hashval
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT hll_hash_bigint(100::bigint, 10);
+     hll_hash_bigint
+  ---------------------
+   4631120266694327276
+  (1 row)
+  ```
+
+- hll_hash_bytea(bytea)
+
+  描述：对bytea类型数据计算哈希值。
+
+  返回值类型：hll_hashval
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT hll_hash_bytea(E'\\x');
+   hll_hash_bytea
+  ----------------
+   0
+  (1 row)
+  ```
+
+- hll_hash_bytea(bytea, int32)
+
+  描述：对bytea类型数据计算哈希值，并设置hashseed（即改变哈希策略）。
+
+  返回值类型：hll_hashval
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT hll_hash_bytea(E'\\x', 10);
+     hll_hash_bytea
+  ---------------------
+   6574525721897061910
+  (1 row)
+  ```
+
+- hll_hash_text(text)
+
+  描述：对text类型数据计算哈希值。
+
+  返回值类型：hll_hashval
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT hll_hash_text('AB');
+      hll_hash_text
+  ---------------------
+   5365230931951287672
+  (1 row)
+  ```
+
+- hll_hash_text(text, int32)
+
+  描述：对text类型数据计算哈希值，并设置hashseed（即改变哈希策略）。
+
+  返回值类型：hll_hashval
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT hll_hash_text('AB', 10);
+  hll_hash_text
+  ---------------------
+  7680762839921155903
+  (1 row)
+  ```
+
+- hll_hash_any(anytype)
+
+  描述：对任意类型数据计算哈希值。
+
+  返回值类型：hll_hashval
+
+  示例：
+
+  ```sql
+  mogdb=# select hll_hash_any(1);
+       hll_hash_any
+  ----------------------
+   -8604791237420463362
+  (1 row)
+
+  mogdb=# select hll_hash_any('08:00:2b:01:02:03'::macaddr);
+       hll_hash_any
+  ----------------------
+   -4883882473551067169
+  (1 row)
+  ```
+
+- hll_hash_any(anytype, int32)
+
+  描述：对任意类型数据计算哈希值，并设置hashseed（即改变哈希策略）。
+
+  返回值类型：hll_hashval
+
+  示例：
+
+  ```sql
+  mogdb=# select hll_hash_any(1, 10);
+       hll_hash_any
+  ----------------------
+   -1478847531811254870
+  (1 row)
+  ```
+
+- hll_hashval_eq(hll_hashval, hll_hashval)
+
+  描述：比较两个hll_hashval类型数据是否相等。
+
+  返回值类型：bool
+
+  示例：
+
+  ```sql
+  mogdb=# select hll_hashval_eq(hll_hash_integer(1), hll_hash_integer(1));
+   hll_hashval_eq
+  ----------------
+   t
+  (1 row)
+  ```
+
+- hll_hashval_ne(hll_hashval, hll_hashval)
+
+  描述：比较两个hll_hashval类型数据是否不相等。
+
+  返回值类型：bool
+
+  示例：
+
+  ```sql
+  mogdb=# select hll_hashval_ne(hll_hash_integer(1), hll_hash_integer(1));
+   hll_hashval_ne
+  ----------------
+   f
+  (1 row)
+  ```
+
+## 日志函数
+
+hll主要存在三种模式Explicit、Sparse、Full。当数据规模比较小的时候会使用Explicit模式，这种模式下distinct值的计算是没有误差的；随着distinct值越来越多，hll会先后转换为Sparse模式和Full模式，这两种模式在计算结果上没有任何区别，只影响hll函数的计算效率和hll对象的存储空间。下面的函数可以用于查看hll的一些参数。
+
+- hll_print(hll)
+
+  描述：打印hll的一些debug参数信息。
+
+  示例：
+
+  ```sql
+  mogdb=# select hll_print(hll_empty());
+                                     hll_print
+  -------------------------------------------------------------------------------
+   type=1(HLL_EMPTY), log2m=14, log2explicit=10, log2sparse=12, duplicatecheck=0
+  (1 row)
+  ```
+
+- hll_type(hll)
+
+  描述：查看当前hll的类型。返回值具体含义如下：返回值0，表示HLL_UNINIT，未初始化的hll对象；返回值1，表示HLL_EMPTY，hll空对象；返回值2，表示HLL_EXPLICIT，Explicit模式的hll对象；返回值3，表示HLL_SPARSE，Sparse模式的hll对象；返回值4，表示HLL_FULL，Full模式的hll对象；返回值5，表示HLL_UNDEFINED，不合法的hll对象。
+
+  示例：
+
+  ```sql
+  mogdb=# select hll_type(hll_empty());
+   hll_type
+  ----------
+          1
+  (1 row)
+  ```
+
+- hll_log2m(hll)
+
+  描述：查看当前hll数据结构中的log2m数值，log2m是分桶数的对数值，此值会影响最后hll计算distinct误差率，误差率计算公式为±1.04/√(2 ^ log2m)。当显式指定log2m的取值为10-16之间时，hll会设置分桶数为2log2m。当显示指定log2explicit为-1时，会采用内置默认值。
+
+  示例：
+
+  ```sql
+  mogdb=# select hll_log2m(hll_empty());
+   hll_log2m
+  -----------
+          14
+  (1 row)
+
+  mogdb=# select hll_log2m(hll_empty(10));
+   hll_log2m
+  -----------
+          10
+  (1 row)
+
+  mogdb=# select hll_log2m(hll_empty(-1));
+   hll_log2m
+  -----------
+          14
+  (1 row)
+  ```
+
+- hll_log2explicit(hll)
+
+  描述：查看当前hll数据结构中的log2explicit数值。hll通常会由Explicit模式到Sparse模式再到Full模式，这个过程称为promotion hierarchy策略。可以通过调整log2explicit值的大小改变策略，比如log2explicit为0的时候就会跳过Explicit模式而直接进入Sparse模式。当显式指定log2explicit的取值为1-12之间时，hll会在数据段长度超过2log2explicit时转为Sparse模式。当显示指定log2explicit为-1时，会采用内置默认值。
+
+  示例：
+
+  ```sql
+  mogdb=# select hll_log2explicit(hll_empty());
+   hll_log2explicit
+  ------------------
+                 10
+  (1 row)
+
+  mogdb=# select hll_log2explicit(hll_empty(12, 8));
+   hll_log2explicit
+  ------------------
+                  8
+  (1 row)
+
+  mogdb=# select hll_log2explicit(hll_empty(12, -1));
+   hll_log2explicit
+  ------------------
+                 10
+  (1 row)
+  ```
+
+- hll_log2sparse(hll)
+
+  描述：查看当前hll数据结构中的log2sparse数值。hll通常会由Explicit模式到Sparse模式再到Full模式，这个过程称为promotion hierarchy策略。可以通过调整log2sparse值的大小改变策略，比如log2sparse为0的时候就会跳过Sparse模式而直接进入Full模式。当显式指定Sparse的取值为1-14之间时，hll会在数据段长度超过2log2sparse时转为Full模式。当显示指定log2sparse为-1时，会采用内置默认值。
+
+  示例：
+
+  ```sql
+  mogdb=# select hll_log2sparse(hll_empty());
+   hll_log2sparse
+  ----------------
+               12
+  (1 row)
+
+  mogdb=# select hll_log2sparse(hll_empty(12, 8, 10));
+   hll_log2sparse
+  ----------------
+               10
+  (1 row)
+
+  mogdb=# select hll_log2sparse(hll_empty(12, 8, -1));
+   hll_log2sparse
+  ----------------
+               12
+  (1 row)
+  ```
+
+- hll_duplicatecheck(hll)
+
+  描述：是否启用duplicatecheck，0是关闭，1是开启。默认关闭，对于有较多重复值出现的情况，可以开启以提高效率。当显示指定duplicatecheck为-1时，会采用内置默认值。
+
+  示例：
+
+  ```sql
+  mogdb=# select hll_duplicatecheck(hll_empty());
+   hll_duplicatecheck
+  --------------------
+                    0
+  (1 row)
+
+  mogdb=# select hll_duplicatecheck(hll_empty(12, 8, 10, 1));
+   hll_duplicatecheck
+  --------------------
+                    1
+  (1 row)
+
+  mogdb=# select hll_duplicatecheck(hll_empty(12, 8, 10, -1));
+   hll_duplicatecheck
+  --------------------
+                    0
+  (1 row)
+  ```
+
+## 功能函数
+
+- hll_empty()
+
+  描述：创建一个空的hll。
+
+  返回值类型：hll
+
+  示例：
+
+  ```sql
+  mogdb=# select hll_empty();
+                           hll_empty
+  ------------------------------------------------------------
+   \x484c4c00000000002b05000000000000000000000000000000000000
+  (1 row)
+  ```
+
+- hll_empty(int32 log2m)
+
+  描述：创建空的hll并指定参数log2m，取值范围是10到16。若输入-1，则采用内置默认值。
+
+  返回值类型：hll
+
+  示例：
+
+  ```sql
+  mogdb=# select hll_empty(10);
+                           hll_empty
+  ------------------------------------------------------------
+   \x484c4c00000000002b04000000000000000000000000000000000000
+  (1 row)
+
+  mogdb=# select hll_empty(-1);
+                           hll_empty
+  ------------------------------------------------------------
+   \x484c4c00000000002b05000000000000000000000000000000000000
+  (1 row)
+  ```
+
+- hll_empty(int32 log2m, int32 log2explicit)
+
+  描述：创建空的hll并依次指定参数log2m、log2explicit。log2explicit取值范围是0到12，0表示直接跳过Explicit模式。该参数可以用来设置Explicit模式的阈值大小，在数据段长度达到2log2explicit后切换为Sparse模式或者Full模式。若输入-1，则log2explicit采用内置默认值。
+
+  返回值类型: hll
+
+  示例：
+
+  ```sql
+  mogdb=# select hll_empty(10, 4);
+                           hll_empty
+  ------------------------------------------------------------
+   \x484c4c00000000001304000000000000000000000000000000000000
+  (1 row)
+
+  mogdb=# select hll_empty(10, -1);
+                           hll_empty
+  ------------------------------------------------------------
+   \x484c4c00000000002b04000000000000000000000000000000000000
+  (1 row)
+  ```
+
+- hll_empty(int32 log2m, int32 log2explicit, int64 log2sparse)
+
+  描述：创建空的hll并依次指定参数log2m、log2explicit、log2sparse。log2sparse取值范围是0到14，0表示直接跳过Sparse模式。该参数可以用来设置Sparse模式的阈值大小，在数据段长度达到2log2sparse后切换为Full模式。若输入-1，则log2sparse采用内置默认值。
+
+  返回值类型：hll
+
+  示例：
+
+  ```sql
+  mogdb=# select hll_empty(10, 4, 8);
+                           hll_empty
+  ------------------------------------------------------------
+   \x484c4c00000000001204000000000000000000000000000000000000
+  (1 row)
+
+  mogdb=# select hll_empty(10, 4, -1);
+                           hll_empty
+  ------------------------------------------------------------
+   \x484c4c00000000001304000000000000000000000000000000000000
+  (1 row)
+  ```
+
+- hll_empty(int32 log2m, int32 log2explicit, int64 log2sparse, int32 duplicatecheck)
+
+  描述：创建空的hll并依次指定参数log2m、log2explicit、log2sparse、duplicatecheck。duplicatecheck取0或者1，表示是否开启该模式，默认情况下该模式会关闭。若输入-1，则duplicatecheck采用内置默认值。
+
+  返回值类型：hll
+
+  示例：
+
+  ```sql
+  mogdb=# select hll_empty(10, 4, 8, 0);
+                           hll_empty
+  ------------------------------------------------------------
+   \x484c4c00000000001204000000000000000000000000000000000000
+  (1 row)
+
+  mogdb=# select hll_empty(10, 4, 8, -1);
+                           hll_empty
+  ------------------------------------------------------------
+   \x484c4c00000000001204000000000000000000000000000000000000
+  (1 row)
+  ```
+
+- hll_add(hll, hll_hashval)
+
+  描述：把hll_hashval加入到hll中。
+
+  返回值类型：hll
+
+  示例：
+
+  ```sql
+  mogdb=# select hll_add(hll_empty(), hll_hash_integer(1));
+                                    hll_add
+  ----------------------------------------------------------------------------
+   \x484c4c08000002002b0900000000000000f03f3e2921ff133fbaed3e2921ff133fbaed00
+  (1 row)
+  ```
+
+- hll_add_rev(hll_hashval, hll)
+
+  描述：把hll_hashval加入到hll中，和hll_add功能一样，只是参数位置进行了交换。
+
+  返回值类型：hll
+
+  示例：
+
+  ```sql
+  mogdb=# select hll_add_rev(hll_hash_integer(1), hll_empty());
+                                  hll_add_rev
+  ----------------------------------------------------------------------------
+   \x484c4c08000002002b0900000000000000f03f3e2921ff133fbaed3e2921ff133fbaed00
+  (1 row)
+  ```
+
+- hll_eq(hll, hll)
+
+  描述：比较两个hll是否相等。
+
+  返回值类型：bool
+
+  示例：
+
+  ```sql
+  mogdb=# select hll_eq(hll_add(hll_empty(), hll_hash_integer(1)), hll_add(hll_empty(), hll_hash_integer(2)));
+   hll_eq
+  --------
+   f
+  (1 row)
+  ```
+
+- hll_ne(hll, hll)
+
+  描述：比较两个hll是否不相等。
+
+  返回值类型：bool
+
+  示例：
+
+  ```sql
+  mogdb=# select hll_ne(hll_add(hll_empty(), hll_hash_integer(1)), hll_add(hll_empty(), hll_hash_integer(2)));
+   hll_ne
+  --------
+   t
+  (1 row)
+  ```
+
+- hll_cardinality(hll)
+
+  描述：计算hll的distinct值。
+
+  返回值类型：int
+
+  示例：
+
+  ```sql
+  mogdb=# select hll_cardinality(hll_empty() || hll_hash_integer(1));
+   hll_cardinality
+  -----------------
+                 1
+  (1 row)
+  ```
+
+- hll_union(hll, hll)
+
+  描述：把两个hll数据结构union成一个。
+
+  返回值类型：hll
+
+  示例：
+
+  ```sql
+  mogdb=# select hll_union(hll_add(hll_empty(), hll_hash_integer(1)), hll_add(hll_empty(), hll_hash_integer(2)));
+                                           hll_union
+  --------------------------------------------------------------------------------------------
+   \x484c4c10002000002b090000000000000000400000000000000000b3ccc49320cca1ae3e2921ff133fbaed00
+  (1 row)
+  ```
+
+## 聚合函数
+
+- hll_add_agg(hll_hashval)
+
+  描述：把哈希后的数据按照分组放到hll中。
+
+  返回值类型：hll
+
+  示例：
+
+  ```sql
+  --准备数据
+  mogdb=# create table t_id(id int);
+  mogdb=# insert into t_id values(generate_series(1,500));
+  mogdb=# create table t_data(a int, c text);
+  mogdb=# insert into t_data select mod(id,2), id from t_id;
+
+  --创建表并指定列为hll
+  mogdb=# create table t_a_c_hll(a int, c hll);
+
+  --根据a列group by对数据分组，把各组数据加到hll中
+  mogdb=# insert into t_a_c_hll select a, hll_add_agg(hll_hash_text(c)) from t_data group by a;
+
+  --得到每组数据中hll的Distinct值
+  mogdb=# select a, #c as cardinality from t_a_c_hll order by a;
+   a |   cardinality
+  ---+------------------
+   0 | 247.862354346299
+   1 | 250.908710610377
+  (2 rows)
+  ```
+
+- hll_add_agg(hll_hashval, int32 log2m)
+
+  描述：把哈希后的数据按照分组放到hll中，并指定参数log2m，取值范围是10到16。若输入-1或者NULL，则采用内置默认值。
+
+  返回值类型：hll
+
+  示例：
+
+  ```sql
+  mogdb=# select hll_cardinality(hll_add_agg(hll_hash_text(c), 12)) from t_data;
+   hll_cardinality
+  ------------------
+   497.965240179228
+  (1 row)
+  ```
+
+- hll_add_agg(hll_hashval, int32 log2m, int32 log2explicit)
+
+  描述：把哈希后的数据按照分组放到hll中，依次指定参数log2m、log2explicit。log2explicit取值范围是0到12，0表示直接跳过Explicit模式。该参数可以用来设置Explicit模式的阈值大小，在数据段长度达到2log2explicit后切换为Sparse模式或者Full模式。若输入-1或者NULL，则log2explicit采用内置默认值。
+
+  返回值类型：hll
+
+  示例：
+
+  ```sql
+  mogdb=# select hll_cardinality(hll_add_agg(hll_hash_text(c), NULL, 1)) from t_data;
+   hll_cardinality
+  ------------------
+   498.496062953313
+  (1 row)
+  ```
+
+- hll_add_agg(hll_hashval, int32 log2m, int32 log2explicit, int64 log2sparse)
+
+  描述：把哈希后的数据按照分组放到hll中，依次指定参数log2m、log2explicit、log2sparse。log2sparse取值范围是0到14，0表示直接跳过Sparse模式。该参数可以用来设置Sparse模式的阈值大小，在数据段长度达到2log2sparse后切换为Full模式。若输入-1或者NULL，则log2sparse采用内置默认值。
+
+  返回值类型：hll
+
+  示例：
+
+  ```sql
+  mogdb=# select hll_cardinality(hll_add_agg(hll_hash_text(c), NULL, 6, 10)) from t_data;
+   hll_cardinality
+  ------------------
+   498.496062953313
+  (1 row)
+  ```
+
+- hll_add_agg(hll_hashval, int32 log2m, int32 log2explicit, int64 log2sparse, int32 duplicatecheck)
+
+  描述：把哈希后的数据按照分组放到hll中, 依次制定参数log2m、log2explicit、log2sparse、duplicatecheck，duplicatecheck取值范围是0或者1，表示是否开启该模式，默认情况下该模式会关闭。若输入-1或者NULL，则duplicatecheck采用内置默认值。
+
+  返回值类型：hll
+
+  示例：
+
+  ```sql
+  mogdb=# select hll_cardinality(hll_add_agg(hll_hash_text(c), NULL, 6, 10, -1)) from t_data;
+   hll_cardinality
+  ------------------
+   498.496062953313
+  (1 row)
+  ```
+
+- hll_union_agg(hll)
+
+  描述：将多个hll类型数据union成一个hll。
+
+  返回值类型：hll
+
+  示例：
+
+  ```sql
+  --将各组中的hll数据union成一个hll，并计算distinct值。
+  mogdb=# select #hll_union_agg(c) as cardinality from t_a_c_hll;
+     cardinality
+  ------------------
+   498.496062953313
+  (1 row)
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  >
+  > 注意：当两个或者多个hll数据结构做union的时候，必须要保证其中每一个hll里面的精度参数一样，否则将不可以进行union。同样的约束也适用于函数hll_union(hll,hll)。
+
+## 废弃函数
+
+由于版本升级，HLL（HyperLogLog）有一些旧的函数废弃，用户可以用类似的函数进行替代。
+
+- hll_schema_version(hll)
+
+  描述：查看当前hll中的schema version。旧版本schema version是常值1，用来进行hll字段的头部校验，重构后的hll在头部增加字段“HLL”进行校验，schema version不再使用。
+
+- hll_regwidth(hll)
+
+  描述：查看hll数据结构中桶的位数大小。旧版本桶的位数regwidth取值1~5，会存在较大的误差，也限制了基数估计上限。 重构后regwidth为固定值6，不再使用regwidth变量。
+
+- hll_expthresh(hll)
+
+  描述：得到当前hll中expthresh大小。采用hll_log2explicit(hll)替代类似功能。
+
+- hll_sparseon(hll)
+
+  描述：是否启用Sparse模式。采用hll_log2sparse(hll)替代类似功能，0表示关闭Sparse模式。
+
+## 内置函数
+
+HLL（HyperLogLog）有一系列内置函数用于内部对数据进行处理，一般情况下用户不需要熟知这些函数的使用。详情见表1。
+
+**表 1** 内置函数
+
+| 函数名称          | 功能描述                                                     |
+| :---------------- | :----------------------------------------------------------- |
+| hll_in            | 以string格式接收hll数据。                                    |
+| hll_out           | 以string格式发送hll数据。                                    |
+| hll_recv          | 以bytea格式接收hll数据。                                     |
+| hll_send          | 以bytea格式发送hll数据。                                     |
+| hll_trans_in      | 以string格式接收hll_trans_type数据。                         |
+| hll_trans_out     | 以string格式发送hll_trans_type数据。                         |
+| hll_trans_recv    | 以bytea形式接收hll_trans_type数据。                          |
+| hll_trans_send    | 以bytea形式发送hll_trans_type数据。                          |
+| hll_typmod_in     | 接收typmod类型数据。                                         |
+| hll_typmod_out    | 发送typmod类型数据。                                         |
+| hll_hashval_in    | 接收hll_hashval类型数据。                                    |
+| hll_hashval_out   | 发送hll_hashval类型数据。                                    |
+| hll_add_trans0    | 类似于hll_add所提供的功能，初始化时无指定入参，通常在聚合运算的第一阶段DN上使用。 |
+| hll_add_trans1    | 类似于hll_add所提供的功能，初始化时指定一个入参，通常在聚合运算的第一阶段DN上使用。 |
+| hll_add_trans2    | 类似于hll_add所提供的功能，初始化时指定两个入参，通常在聚合运算的第一阶段DN上使用。 |
+| hll_add_trans3    | 类似于hll_add所提供的功能，初始化时指定三个入参，通常在聚合运算的第一阶段DN上使用。 |
+| hll_add_trans4    | 类似于hll_add所提供的功能，初始化时指定四个入参，通常在聚合运算的第一阶段DN上使用。 |
+| hll_union_trans   | 类似hll_union所提供的功能，在聚合运算的第一阶段DN上使用。    |
+| hll_union_collect | 类似于hll_union所提供的功能，在聚合运算第二阶段DN上使用，汇总各个DN上的结果。 |
+| hll_pack          | 在聚合运算第三阶段DN上使用，把自定义hll_trans_type类型最后转换成hll类型。 |
+| hll               | 用于hll类型转换成hll类型，根据输入参数会设定指定参数。       |
+| hll_hashval       | 用于bigint类型转换成hll_hashval类型。                        |
+| hll_hashval_int4  | 用于int4类型转换成hll_hashval类型。                          |
+
+## 操作符
+
+- =
+
+  描述：比较hll或hll_hashval的值是否相等。
+
+  返回值类型：bool
+
+  示例：
+
+  ```sql
+  --hll
+  mogdb=# select (hll_empty() || hll_hash_integer(1)) = (hll_empty() || hll_hash_integer(1));
+  column
+  ----------
+   t
+  (1 row)
+
+  --hll_hashval
+  mogdb=# select hll_hash_integer(1) = hll_hash_integer(1);
+   ?column?
+  ----------
+   t
+  (1 row)
+  ```
+
+- <> or !=
+
+  描述：比较hll或hll_hashval是否不相等。
+
+  返回值类型：bool
+
+  示例：
+
+  ```sql
+  --hll
+  mogdb=# select (hll_empty() || hll_hash_integer(1)) <> (hll_empty() || hll_hash_integer(2));
+   ?column?
+  ----------
+   t
+  (1 row)
+
+  --hll_hashval
+  mogdb=# select hll_hash_integer(1) <> hll_hash_integer(2);
+   ?column?
+  ----------
+   t
+  (1 row)
+  ```
+
+- ||
+
+  描述：可代表hll_add、hll_union、hll_add_rev三个函数的功能。
+
+  返回值类型：hll
+
+  示例：
+
+  ```sql
+  --hll_add
+  mogdb=# select hll_empty() || hll_hash_integer(1);
+                                    ?column?
+  ----------------------------------------------------------------------------
+   \x484c4c08000002002b0900000000000000f03f3e2921ff133fbaed3e2921ff133fbaed00
+  (1 row)
+
+  --hll_add_rev
+  mogdb=# select hll_hash_integer(1) || hll_empty();
+                                    ?column?
+  ----------------------------------------------------------------------------
+   \x484c4c08000002002b0900000000000000f03f3e2921ff133fbaed3e2921ff133fbaed00
+  (1 row)
+
+  --hll_union
+  mogdb=# select (hll_empty() || hll_hash_integer(1)) || (hll_empty() || hll_hash_integer(2));
+                                            ?column?
+  --------------------------------------------------------------------------------------------
+   \x484c4c10002000002b090000000000000000400000000000000000b3ccc49320cca1ae3e2921ff133fbaed00
+  (1 row)
+  ```
+
+- \#
+
+  描述：计算出hll的Dintinct值, 同hll_cardinality函数。
+
+  返回值类型：int
+
+  示例：
+
+  ```sql
+  mogdb=# select #(hll_empty() || hll_hash_integer(1));
+   ?column?
+  ----------
+          1
+  (1 row)
+  ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/14-sequence-functions.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/14-sequence-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..7262605f1ae17fe3f500fba1fc9a99047326c3ee
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/14-sequence-functions.md
@@ -0,0 +1,127 @@
+---
+title: SEQUENCE函数
+summary: SEQUENCE函数
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# SEQUENCE函数
+
+序列函数为用户从序列对象中获取后续的序列值提供了简单的多用户安全的方法。
+
+- nextval(regclass)
+
+  描述：递增序列并返回新值。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  > 为了避免从同一个序列获取值的并发事务被阻塞， nextval操作不会回滚；也就是说，一旦一个值已经被抓取， 那么就认为它已经被用过了，并且不会再被返回。 即使该操作处于事务中，当事务之后中断，或者如果调用查询结束不使用该值，也是如此。这种情况将在指定值的顺序中留下未使用的“空洞”。 因此，MogDB序列对象不能用于获得“无间隙”序列。
+  >
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+  > nextval函数只能在主机上执行，备机不支持执行此函数。
+
+  返回类型：bigint
+
+  nextval函数有两种调用方式（其中第二种调用方式目前不支持Sequence命名中有特殊字符“.”的情况），如下：
+
+  示例1：
+
+  ```sql
+  mogdb=# select nextval('seqDemo');
+   nextval
+  ---------
+         2
+  (1 row)
+  ```
+
+  示例2：
+
+  ```sql
+  mogdb=# select seqDemo.nextval;
+   nextval
+  ---------
+         2
+  (1 row)
+  ```
+
+- currval(regclass)
+
+  返回当前会话里最近一次nextval返回的指定的sequence的数值。如果当前会话还没有调用过指定的sequence的nextval，那么调用currval将会报错。
+
+  返回类型：bigint
+
+  currval函数有两种调用方式（其中第二种调用方式目前不支持Sequence命名中有特殊字符“.”的情况），如下：
+
+  示例1：
+
+  ```sql
+  mogdb=# select currval('seq1');
+   currval
+  ---------
+         2
+  (1 row)
+  ```
+
+  示例2：
+
+  ```sql
+  mogdb=# select seq1.currval;
+   currval
+  ---------
+         2
+  (1 row)
+  ```
+
+- lastval()
+
+  描述：返回当前会话里最近一次nextval返回的数值。这个函数等效于currval，只是它不用序列名为参数，它抓取当前会话里面最近一次nextval使用的序列。如果当前会话还没有调用过nextval，那么调用lastval将会报错。
+
+  返回类型：bigint
+
+  示例：
+
+  ```sql
+  mogdb=# select lastval();
+   lastval
+  ---------
+         2
+  (1 row)
+  ```
+
+- setval(regclass, bigint)
+
+  描述：设置序列的当前数值。
+
+  返回类型：bigint
+
+  示例：
+
+  ```sql
+  mogdb=# select setval('seqDemo',1);
+   setval
+  --------
+        1
+  (1 row)
+  ```
+
+- setval(regclass, bigint, Boolean)
+
+  描述：设置序列的当前数值以及is_called标志。
+
+  返回类型：bigint
+
+  示例：
+
+  ```sql
+  mogdb=# select setval('seqDemo',1,true);
+   setval
+  --------
+        1
+  (1 row)
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  > Setval后当前会话会立刻生效，但如果其他会话有缓存的序列值，只能等到缓存值用尽才能感知Setval的作用。所以为了避免序列值冲突，setval要谨慎使用。
+  > 因为序列是非事务的，setval造成的改变不会由于事务的回滚而撤销。
+  >
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+  > nextval函数只能在主机上执行，备机不支持执行此函数。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/15-array-functions-and-operators.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/15-array-functions-and-operators.md
new file mode 100644
index 0000000000000000000000000000000000000000..41bcc21fe55783df770cbac3fa059151b986d5da
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/15-array-functions-and-operators.md
@@ -0,0 +1,566 @@
+---
+title: 数组函数和操作符
+summary: 数组函数和操作符
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 数组函数和操作符
+
+## 数组操作符
+
+- =
+
+  描述: 两个数组是否相等
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT ARRAY[1.1,2.1,3.1]::int[] = ARRAY[1,2,3] AS RESULT ;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;&gt;
+
+  描述: 两个数组是否不相等
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT ARRAY[1,2,3] <> ARRAY[1,2,4] AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;
+
+  描述: 一个数组是否小于另一个数组
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT ARRAY[1,2,3] < ARRAY[1,2,4] AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &gt;
+
+  描述: 一个数组是否大于另一个数组
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT ARRAY[1,4,3] > ARRAY[1,2,4] AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;=
+
+  描述: 一个数组是否小于或等于另一个数组
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT ARRAY[1,2,3] <= ARRAY[1,2,3] AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &gt;=
+
+  描述: 一个数组是否大于或等于另一个数组
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT ARRAY[1,4,3] >= ARRAY[1,4,3] AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- @&gt;
+
+  描述: 一个数组是否包含另一个数组
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT ARRAY[1,4,3] @> ARRAY[3,1] AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;@
+
+  描述: 一个数组是否被包含于另一个数组
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT ARRAY[2,7] <@ ARRAY[1,7,4,2,6] AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &&
+
+  描述: 一个数组是否和另一个数组重叠（有共同元素）
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT ARRAY[1,4,3] && ARRAY[2,1] AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- ||
+
+  描述: 数组与数组进行连接
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT ARRAY[1,2,3] || ARRAY[4,5,6] AS RESULT;
+      result
+  ---------------
+   {1,2,3,4,5,6}
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT ARRAY[1,2,3] || ARRAY[[4,5,6],[7,8,9]] AS RESULT;
+            result
+  ---------------------------
+   {{1,2,3},{4,5,6},{7,8,9}}
+  (1 row)
+  ```
+
+- ||
+
+  描述: 元素与数组进行连接
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT 3 || ARRAY[4,5,6] AS RESULT;
+    result
+  -----------
+   {3,4,5,6}
+  (1 row)
+  ```
+
+- ||
+
+  描述: 数组与元素进行连接
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT ARRAY[4,5,6] || 7 AS RESULT;
+    result
+  -----------
+   {4,5,6,7}
+  (1 row)
+  ```
+
+数组比较是使用默认的B-tree比较函数对所有元素逐一进行比较的。多维数组的元素按照行顺序进行访问。如果两个数组的内容相同但维数不等，决定排序顺序的首要因素是维数。
+
+## 数组函数
+
+- array_append(anyarray, anyelement)
+
+  描述: 向数组末尾添加元素，只支持一维数组。
+
+  返回类型: anyarray
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT array_append(ARRAY[1,2], 3) AS RESULT;
+   result
+  ---------
+   {1,2,3}
+  (1 row)
+  ```
+
+- array_prepend(anyelement, anyarray)
+
+  描述: 向数组开头添加元素，只支持一维数组。
+
+  返回类型: anyarray
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT array_prepend(1, ARRAY[2,3]) AS RESULT;
+   result
+  ---------
+   {1,2,3}
+  (1 row)
+  ```
+
+- array_cat(anyarray, anyarray)
+
+  描述: 连接两个数组，支持多维数组。
+
+  返回类型: anyarray
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT array_cat(ARRAY[1,2,3], ARRAY[4,5]) AS RESULT;
+     result
+  -------------
+   {1,2,3,4,5}
+  (1 row)
+
+  mogdb=# SELECT array_cat(ARRAY[[1,2],[4,5]], ARRAY[6,7]) AS RESULT;
+         result
+  ---------------------
+   {{1,2},{4,5},{6,7}}
+  (1 row)
+  ```
+
+- array_cat_distinct(anyarray, anyarray)
+
+    描述：连接两个数组，并去重，只支持一维数组。
+
+    返回类型：anyarray
+
+    示例：
+
+    ```sql
+    mogdb=# SELECT array_cat_distinct(ARRAY[1,2,3], ARRAY[3,4,5]) AS RESULT;
+       result
+    -------------
+     {1,2,3,4,5}
+    (1 row)
+    ```
+
+- array_intersect(anyarray, anyarray)
+
+    描述：两个数组取交集，只支持一维数组。
+
+    返回类型：anyarray
+
+    示例：
+
+    ```sql
+    mogdb=# SELECT array_intersect(ARRAY[1,2,3], ARRAY[3,4,5]) AS RESULT;
+       result
+    -------------
+     {3}
+    (1 row)
+    ```
+
+- array_intersect_distinct(anyarray, anyarray)
+
+    描述：两个数组取交集，并去重，只支持一维数组。
+
+    返回类型：anyarray
+
+    示例：
+
+    ```sql
+    mogdb=# SELECT array_intersect_distinct(ARRAY[1,2,2], ARRAY[2,2,4,5]) AS RESULT;
+       result
+    -------------
+     {2}
+    (1 row)
+    ```
+
+- array_except(anyarray, anyarray)
+
+    描述：两个数组取差，只支持一维数组。
+
+    返回类型：anyarray
+
+    示例：
+
+    ```sql
+    mogdb=# SELECT array_except(ARRAY[1,2,3], ARRAY[3,4,5]) AS RESULT;
+       result
+    -------------
+     {1,2}
+    (1 row)
+    ```
+
+- array_except_distinct(anyarray, anyarray)
+
+    描述：两个数组取差，并去重，只支持一维数组。
+
+    返回类型：anyarray
+
+    示例：
+
+    ```sql
+    mogdb=# SELECT array_except_distinct(ARRAY[1,2,2,3], ARRAY[3,4,5]) AS RESULT;
+       result
+    -------------
+     {1,2}
+    (1 row)
+    ```
+
+- array_ndims(anyarray)
+
+  描述: 返回数组的维数。
+
+  返回类型: int
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT array_ndims(ARRAY[[1,2,3], [4,5,6]]) AS RESULT;
+   result
+  --------
+        2
+  (1 row)
+  ```
+
+- array_dims(anyarray)
+
+  描述: 返回数组各个维度中的低位下标值和高位下标值。
+
+  返回类型: text
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT array_dims(ARRAY[[1,2,3], [4,5,6]]) AS RESULT;
+     result
+  ------------
+   [1:2][1:3]
+  (1 row)
+  ```
+
+- array_length(anyarray, int)
+
+  描述: 返回指定数组维度的长度。int为指定数组维度。
+
+  返回类型: int
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT array_length(array[1,2,3], 1) AS RESULT;
+   result
+  --------
+        3
+  (1 row)
+
+  mogdb=# SELECT array_length(array[[1,2,3],[4,5,6]], 2) AS RESULT;
+   result
+  --------
+        3
+  (1 row)
+  ```
+
+- array_lower(anyarray, int)
+
+  描述: 返回指定数组维数的下界。int为指定数组维度。
+
+  返回类型: int
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT array_lower('[0:2]={1,2,3}'::int[], 1) AS RESULT;
+   result
+  --------
+        0
+  (1 row)
+  ```
+
+- array_upper(anyarray, int)
+
+  描述: 返回指定数组维数的上界。int为指定数组维度。
+
+  返回类型: int
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT array_upper(ARRAY[1,8,3,7], 1) AS RESULT;
+   result
+  --------
+        4
+  (1 row)
+  ```
+
+- array_remove(anyarray, anyelement)
+
+    描述：移除数组中的所有指定元素。仅支持一维数组。
+
+    返回类型：anyarray
+
+    示例：
+
+    ```sql
+    mogdb=# SELECT array_remove(ARRAY[1,8,8,7], 8) AS RESULT;
+     result
+    --------
+     {1,7}
+    (1 row)
+    ```
+
+- array_to_string(anyarray, text [, text])
+
+  描述: 使用第一个text作为数组的新分隔符，使用第二个text替换数组值为null的值。
+
+  返回类型: text
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT array_to_string(ARRAY[1, 2, 3, NULL, 5], ',', '*') AS RESULT;
+    result
+  -----------
+   1,2,3,*,5
+  (1 row)
+  ```
+
+- array_delete(anyarray)
+
+    描述：清空数组中的元素并返回一个同类型的空数组。
+
+    返回类型：anyarray
+
+    示例：
+
+    ```sql
+    mogdb=# SELECT array_delete(ARRAY[1,8,3,7]) AS RESULT;
+     result
+    --------
+     {}
+    (1 row)
+    ```
+
+- array_extendnull(anyarray, int)
+
+    描述：往数组尾部添加指定个数的null空元素。
+
+    返回类型：anyarray
+
+    示例：
+
+    ```sql
+    mogdb=# SELECT array_extendnull(ARRAY[1,8,3,7],1) AS RESULT;
+        result
+    --------------
+    {1,8,3,7,null}
+    (1 row)
+    ```
+
+- array_exists(anyarray, int)
+
+    描述：检查第二个参数是否是数组的合法下标。
+
+    返回类型：boolean
+
+    示例：
+
+    ```sql
+    mogdb=# SELECT array_exists(ARRAY[1,8,3,7],1) AS RESULT;
+     result
+    --------
+     t
+    (1 row)
+    ```
+
+- array_next(anyarray, int)
+
+    描述：根据第二个入参返回数组中指定下标元素的下一个元素的下标。
+
+    返回类型：int
+
+    示例：
+
+    ```sql
+    mogdb=# SELECT array_next(ARRAY[1,8,3,7],1) AS RESULT;
+     result
+    --------
+          2
+    (1 row)
+    ```
+
+- array_prior(anyarray, int)
+
+    描述：根据第二个入参返回数组中指定下标元素的上一个元素的下标。
+
+    返回类型：int
+
+    示例：
+
+    ```sql
+    mogdb=# SELECT array_next(ARRAY[1,8,3,7],2) AS RESULT;
+     result
+    --------
+      1
+    (1 row)
+    ```
+
+- string_to_array(text, text [, text])
+
+  描述: 使用第二个text指定分隔符，使用第三个可选的text作为NULL值替换模板，如果分隔后的子串与第三个可选的text完全匹配，则将其替换为NULL。
+
+  返回类型: text[]
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT string_to_array('xx~^~yy~^~zz', '~^~', 'yy') AS RESULT;
+      result
+  --------------
+   {xx,NULL,zz}
+  (1 row)
+  mogdb=# SELECT string_to_array('xx~^~yy~^~zz', '~^~', 'y') AS RESULT;
+     result
+  ------------
+   {xx,yy,zz}
+  (1 row)
+  ```
+
+- unnest(anyarray)
+
+  描述: 扩大一个数组为一组行。
+
+  返回类型: setof anyelement
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT unnest(ARRAY[1,2]) AS RESULT;
+   result
+  --------
+        1
+        2
+  (2 rows)
+  ```
+
+在string_to_array中，如果分隔符参数是NULL，输入字符串中的每个字符将在结果数组中变成一个独立的元素。如果分隔符是一个空白字符串，则整个输入的字符串将变为一个元素的数组。否则输入字符串将在每个分隔字符串处分开。
+
+在string_to_array中，如果省略null字符串参数或为NULL，将字符串中没有输入内容的子串替换为NULL。
+
+在array_to_string中，如果省略null字符串参数或为NULL，运算中将跳过在数组中的任何null元素，并且不会在输出字符串中出现。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/16-range-functions-and-operators.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/16-range-functions-and-operators.md
new file mode 100644
index 0000000000000000000000000000000000000000..6e7887e8913401441d1bbd901138618f2e8f0558
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/16-range-functions-and-operators.md
@@ -0,0 +1,435 @@
+---
+title: 范围函数和操作符
+summary: 范围函数和操作符
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 范围函数和操作符
+
+## 范围操作符
+
+- =
+
+  描述: 等于
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT int4range(1,5) = '[1,4]'::int4range AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;&gt;
+
+  描述: 不等于
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT numrange(1.1,2.2) <> numrange(1.1,2.3) AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;
+
+  描述: 小于
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT int4range(1,10) < int4range(2,3) AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &gt;
+
+  描述: 大于
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT int4range(1,10) > int4range(1,5) AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;=
+
+  描述: 小于或等于
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT numrange(1.1,2.2) <= numrange(1.1,2.2) AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &gt;=
+
+  描述: 大于或等于
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT numrange(1.1,2.2) >= numrange(1.1,2.0) AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- @&gt;
+
+  描述: 包含范围
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT int4range(2,4) @> int4range(2,3) AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- @&gt;
+
+  描述: 包含元素
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT '[2011-01-01,2011-03-01)'::tsrange @> '2011-01-10'::timestamp AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;@
+
+  描述: 范围包含于
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT int4range(2,4) <@ int4range(1,7) AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;@
+
+  描述: 元素包含于
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT 42 <@ int4range(1,7) AS RESULT;
+   result
+  --------
+   f
+  (1 row)
+  ```
+
+- &&
+
+  描述: 重叠（有共同点）
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT int8range(3,7) && int8range(4,12) AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &lt;&lt;
+
+  描述: 范围值是否比另一个范围值的最小值还小（没有交集）
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT int8range(1,10) << int8range(100,110) AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &gt;&gt;
+
+  描述: 范围值是否比另一个范围值的最大值还大（没有交集）
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT int8range(50,60) >> int8range(20,30) AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &&lt;
+
+  描述: 范围值的最大值是否不超过另一个范围值的最大值。
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT int8range(1,20) &< int8range(18,20) AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- &&gt;
+
+  描述: 范围值的最小值是否不小于另一个范围值的最小值。
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT int8range(7,20) &> int8range(5,10) AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- -|-
+
+  描述: 相邻
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT numrange(1.1,2.2) -|- numrange(2.2,3.3) AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- \+
+
+  描述: 并集
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT numrange(5,15) + numrange(10,20) AS RESULT;
+   result
+  --------
+   [5,20)
+  (1 row)
+  ```
+
+- \*
+
+  描述: 交集
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT int8range(5,15) * int8range(10,20) AS RESULT;
+   result
+  ---------
+   [10,15)
+  (1 row)
+  ```
+
+- \-
+
+  描述: 差集
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT int8range(5,15) - int8range(10,20) AS RESULT;
+   result
+  --------
+   [5,10)
+  (1 row)
+  ```
+
+简单的比较操作符&lt;、&gt;、&lt;=和&gt;=先比较下界，只有下界相等时才比较上界。
+
+&lt;&lt;、&gt;&gt;和-|-操作符当包含空范围时也会返回false；也就是，不认为空范围在其他范围之前或之后。
+
+并集和差集操作符的执行结果无法包含两个不相交的子范围。
+
+## 范围函数
+
+- numrange(numeric, numeric, [text])
+
+    描述：表示一个范围。
+
+    返回类型：范围元素类型
+
+    示例：
+
+    ```sql
+    mogdb=# SELECT numrange(1.1,2.2) AS RESULT;
+     result
+    --------
+    [1.1,2.2)
+    (1 row)
+    mogdb=# SELECT numrange(1.1,2.2, '()') AS RESULT;
+     result
+    --------
+    (1.1,2.2)
+    (1 row)
+    ```
+
+- lower(anyrange)
+
+  描述: 范围的下界。
+
+  返回类型: 范围元素类型
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT lower(numrange(1.1,2.2)) AS RESULT;
+   result
+  --------
+      1.1
+  (1 row)
+  ```
+
+- upper(anyrange)
+
+  描述: 范围的上界。
+
+  返回类型: 范围元素类型
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT upper(numrange(1.1,2.2)) AS RESULT;
+   result
+  --------
+      2.2
+  (1 row)
+  ```
+
+- isempty(anyrange)
+
+  描述: 范围是否为空。
+
+  返回类型: Boolean
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT isempty(numrange(1.1,2.2)) AS RESULT;
+   result
+  --------
+   f
+  (1 row)
+  ```
+
+- lower_inc(anyrange)
+
+  描述: 是否包含下界。
+
+  返回类型: Boolean
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT lower_inc(numrange(1.1,2.2)) AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- upper_inc(anyrange)
+
+  描述: 是否包含上界。
+
+  返回类型: Boolean
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT upper_inc(numrange(1.1,2.2)) AS RESULT;
+   result
+  --------
+   f
+  (1 row)
+  ```
+
+- lower_inf(anyrange)
+
+  描述: 下界是否为无穷。
+
+  返回类型: Boolean
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT lower_inf('(,)'::daterange) AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- upper_inf(anyrange)
+
+  描述: 上界是否为无穷。
+
+  返回类型: Boolean
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT upper_inf('(,)'::daterange) AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+如果范围是空或者需要的界限是无穷的，lower和upper函数将返回null。lower_inc、upper_inc、lower_inf和upper_inf函数均对空范围返回false。
+
+- elem_contained_by_range(anyelement, anyrange)
+
+    描述：判断元素是否在范围内。
+
+    返回类型：Boolean
+
+    示例：
+
+    ```sql
+    mogdb=# SELECT elem_contained_by_range('2', numrange(1.1,2.2));
+     elem_contained_by_range
+    -------------------------
+     t
+    (1 row)
+    ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/17-aggregate-functions.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/17-aggregate-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..4e2fbe44f510e507336e9216d319b9e0ce262847
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/17-aggregate-functions.md
@@ -0,0 +1,823 @@
+---
+title: 聚集函数
+summary: 聚集函数
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 聚集函数
+
+- sum(expression)
+
+  描述：所有输入行的expression总和。
+
+  返回类型：
+
+  通常情况下输入数据类型和输出数据类型是相同的，但以下情况会发生类型转换：
+
+  - 对于SMALLINT或INT输入，输出类型为BIGINT。
+  - 对于BIGINT输入，输出类型为NUMBER 。
+  - 对于浮点数输入，输出类型为DOUBLE PRECISION。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT SUM(ss_ext_tax) FROM tpcds.STORE_SALES;
+    sum
+  --------------
+   213267594.69
+  (1 row)
+  ```
+
+- max(expression)
+
+  描述：所有输入行中expression的最大值。
+
+  参数类型：任意数组、数值、字符串、日期/时间类型、IPV4和IPV6地址（INET型和CIDR型）。
+
+  返回类型：与参数数据类型相同
+
+  示例：
+
+  ```
+  mogdb=# SELECT MAX(inv_quantity_on_hand) FROM tpcds.inventory;
+  ```
+
+- min(expression)
+
+  描述：所有输入行中expression的最小值。
+
+  参数类型：任意数组、数值、字符串、日期/时间类型、IPV4和IPV6地址（INET型和CIDR型）。
+
+  返回类型：与参数数据类型相同
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT MIN(inv_quantity_on_hand) FROM tpcds.inventory;
+   min
+  -----
+     0
+  (1 row)
+  ```
+
+- avg(expression)
+
+  描述：所有输入值的均值（算术平均）。
+
+  返回类型：
+
+  对于任何整数类型输入，结果都是NUMBER类型。
+
+  对于任何浮点输入，结果都是DOUBLE PRECISION类型。
+
+  否则和输入数据类型相同。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT AVG(inv_quantity_on_hand) FROM tpcds.inventory;
+           avg
+  ----------------------
+   500.0387129084044604
+  (1 row)
+  ```
+
+- count(expression)
+
+  描述：返回表中满足expression不为NULL的行数。
+
+  返回类型：BIGINT
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT COUNT(inv_quantity_on_hand) FROM tpcds.inventory;
+    count
+  ----------
+   11158087
+  (1 row)
+  ```
+
+- count(*)
+
+  描述：返回表中的记录行数。
+
+  返回类型：BIGINT
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT COUNT(*) FROM tpcds.inventory;
+    count
+  ----------
+   11745000
+  (1 row)
+  ```
+
+- median(expression) [over (query partition clause)]
+
+  描述：返回表达式的中位数，计算时NULL将会被median函数忽略。可以使用distinct关键字排除表达式中的重复记录。输入expression的数据类型可以是数值类型（包括integer， double，bigint等）， 也可以是interval类型。其他数据类型不支持求取中位数。
+
+  返回类型：double或interval类型
+
+  示例：
+
+  ```sql
+  select median(id) from (values(1), (2), (3), (4), (null)) test(id);
+   median
+  --------
+       2.5
+  (1 row)
+  ```
+
+- array_agg(expression)
+
+  描述：将所有输入值（包括空）连接成一个数组。
+
+  返回类型：参数类型的数组
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT ARRAY_AGG(sr_fee) FROM tpcds.store_returns WHERE sr_customer_sk = 2;
+     array_agg
+  ---------------
+   {22.18,63.21}
+  (1 row)
+  ```
+
+- string_agg(expression, delimiter)
+
+  描述：将输入值连接成为一个字符串，用分隔符分开。
+
+  返回类型：和参数数据类型相同。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT string_agg(sr_item_sk, ',') FROM tpcds.store_returns where sr_item_sk < 3;
+           string_agg
+  ---------------------------------------------------------------------------------
+  ------------------------------
+   1,2,1,2,2,1,1,2,2,1,2,1,2,1,1,1,2,1,1,1,1,1,2,1,1,1,1,1,2,2,1,1,1,1,1,1,1,1,1,2,
+  2,1,1,1,1,1,1,2,2,1,1,2,1,1,1
+  (1 row)
+  ```
+
+- listagg(expression [, delimiter]) WITHIN GROUP(ORDER BY order-list)
+
+  描述：将聚集列数据按WITHIN GROUP指定的排序方式排列，并用delimiter指定的分隔符拼接成一个字符串。
+
+  - expression：必选。指定聚集列名或基于列的有效表达式，不支持DISTINCT关键字和VARIADIC参数。
+  - delimiter：可选。指定分隔符，可以是字符串常数或基于分组列的确定性表达式，缺省时表示分隔符为空。
+  - order-list：必选。指定分组内的排序方式。
+
+  返回类型：text
+
+  示例：
+
+  聚集列是文本字符集类型。
+
+  ```sql
+  mogdb=# SELECT deptno, listagg(ename, ',') WITHIN GROUP(ORDER BY ename) AS employees FROM emp GROUP BY deptno;
+   deptno |              employees
+  --------+--------------------------------------
+       10 | CLARK,KING,MILLER
+       20 | ADAMS,FORD,JONES,SCOTT,SMITH
+       30 | ALLEN,BLAKE,JAMES,MARTIN,TURNER,WARD
+  (3 rows)
+  ```
+
+  聚集列是整型。
+
+  ```sql
+  mogdb=# SELECT deptno, listagg(mgrno, ',') WITHIN GROUP(ORDER BY mgrno NULLS FIRST) AS mgrnos FROM emp GROUP BY deptno;
+   deptno |            mgrnos
+  --------+-------------------------------
+       10 | 7782,7839
+       20 | 7566,7566,7788,7839,7902
+       30 | 7698,7698,7698,7698,7698,7839
+  (3 rows)
+  ```
+
+  聚集列是浮点类型。
+
+  ```sql
+  mogdb=# SELECT job, listagg(bonus, '($); ') WITHIN GROUP(ORDER BY bonus DESC) || '($)' AS bonus FROM emp GROUP BY job;
+      job     |                      bonus
+  ------------+-------------------------------------------------
+   CLERK      | 10234.21($); 2000.80($); 1100.00($); 1000.22($)
+   PRESIDENT  | 23011.88($)
+   ANALYST    | 2002.12($); 1001.01($)
+   MANAGER    | 10000.01($); 2399.50($); 999.10($)
+   SALESMAN   | 1000.01($); 899.00($); 99.99($); 9.00($)
+  (5 rows)
+  ```
+
+  聚集列是时间类型。
+
+  ```sql
+  mogdb=# SELECT deptno, listagg(hiredate, ', ') WITHIN GROUP(ORDER BY hiredate DESC) AS hiredates FROM emp GROUP BY deptno;
+   deptno |                                                          hiredates
+  --------+------------------------------------------------------------------------------------------------------------------------------
+       10 | 1982-01-23 00:00:00, 1981-11-17 00:00:00, 1981-06-09 00:00:00
+       20 | 2001-04-02 00:00:00, 1999-12-17 00:00:00, 1987-05-23 00:00:00, 1987-04-19 00:00:00, 1981-12-03 00:00:00
+       30 | 2015-02-20 00:00:00, 2010-02-22 00:00:00, 1997-09-28 00:00:00, 1981-12-03 00:00:00, 1981-09-08 00:00:00, 1981-05-01 00:00:00
+  (3 rows)
+  ```
+
+  聚集列是时间间隔类型。
+
+  ```sql
+  mogdb=# SELECT deptno, listagg(vacationTime, '; ') WITHIN GROUP(ORDER BY vacationTime DESC) AS vacationTime FROM emp GROUP BY deptno;
+   deptno |                                    vacationtime
+  --------+------------------------------------------------------------------------------------
+       10 | 1 year 30 days; 40 days; 10 days
+       20 | 70 days; 36 days; 9 days; 5 days
+       30 | 1 year 1 mon; 2 mons 10 days; 30 days; 12 days 12:00:00; 4 days 06:00:00; 24:00:00
+  (3 rows)
+  ```
+
+  分隔符缺省时，默认为空。
+
+  ```sql
+  mogdb=# SELECT deptno, listagg(job) WITHIN GROUP(ORDER BY job) AS jobs FROM emp GROUP BY deptno;
+   deptno |                     jobs
+  --------+----------------------------------------------
+       10 | CLERKMANAGERPRESIDENT
+       20 | ANALYSTANALYSTCLERKCLERKMANAGER
+       30 | CLERKMANAGERSALESMANSALESMANSALESMANSALESMAN
+  (3 rows)
+  ```
+
+  listagg作为窗口函数时，OVER子句不支持ORDER BY的窗口排序，listagg列为对应分组的有序聚集。
+
+  ```sql
+  mogdb=# SELECT deptno, mgrno, bonus, listagg(ename,'; ') WITHIN GROUP(ORDER BY hiredate) OVER(PARTITION BY deptno) AS employees FROM emp;
+   deptno | mgrno |  bonus   |                 employees
+  --------+-------+----------+-------------------------------------------
+       10 |  7839 | 10000.01 | CLARK; KING; MILLER
+       10 |       | 23011.88 | CLARK; KING; MILLER
+       10 |  7782 | 10234.21 | CLARK; KING; MILLER
+       20 |  7566 |  2002.12 | FORD; SCOTT; ADAMS; SMITH; JONES
+       20 |  7566 |  1001.01 | FORD; SCOTT; ADAMS; SMITH; JONES
+       20 |  7788 |  1100.00 | FORD; SCOTT; ADAMS; SMITH; JONES
+       20 |  7902 |  2000.80 | FORD; SCOTT; ADAMS; SMITH; JONES
+       20 |  7839 |   999.10 | FORD; SCOTT; ADAMS; SMITH; JONES
+       30 |  7839 |  2399.50 | BLAKE; TURNER; JAMES; MARTIN; WARD; ALLEN
+       30 |  7698 |     9.00 | BLAKE; TURNER; JAMES; MARTIN; WARD; ALLEN
+       30 |  7698 |  1000.22 | BLAKE; TURNER; JAMES; MARTIN; WARD; ALLEN
+       30 |  7698 |    99.99 | BLAKE; TURNER; JAMES; MARTIN; WARD; ALLEN
+       30 |  7698 |  1000.01 | BLAKE; TURNER; JAMES; MARTIN; WARD; ALLEN
+       30 |  7698 |   899.00 | BLAKE; TURNER; JAMES; MARTIN; WARD; ALLEN
+  (14 rows)
+  ```
+
+- covar_pop(Y, X)
+
+  描述：总体协方差。
+
+  返回类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT COVAR_POP(sr_fee, sr_net_loss) FROM tpcds.store_returns WHERE sr_customer_sk < 1000;
+      covar_pop
+  ------------------
+   829.749627587403
+  (1 row)
+  ```
+
+- covar_samp(Y, X)
+
+  描述：样本协方差。
+
+  返回类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT COVAR_SAMP(sr_fee, sr_net_loss) FROM tpcds.store_returns WHERE sr_customer_sk < 1000;
+      covar_samp
+  ------------------
+   830.052235037289
+  (1 row)
+  ```
+
+- stddev_pop(expression)
+
+  描述：总体标准差。
+
+  返回类型：对于浮点类型的输入返回double precision，其他输入返回numeric。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT STDDEV_POP(inv_quantity_on_hand) FROM tpcds.inventory WHERE inv_warehouse_sk = 1;
+      stddev_pop
+  ------------------
+   289.224294957556
+  (1 row)
+  ```
+
+- stddev_samp(expression)
+
+  描述：样本标准差。
+
+  返回类型：对于浮点类型的输入返回double precision，其他输入返回numeric。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT STDDEV_SAMP(inv_quantity_on_hand) FROM tpcds.inventory WHERE inv_warehouse_sk = 1;
+     stddev_samp
+  ------------------
+   289.224359757315
+  (1 row)
+  ```
+
+- var_pop(expression)
+
+  描述：总体方差（总体标准差的平方）
+
+  返回类型：对于浮点类型的输入返回double precision类型，其他输入返回numeric类型。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT VAR_POP(inv_quantity_on_hand) FROM tpcds.inventory WHERE inv_warehouse_sk = 1;
+        var_pop
+  --------------------
+   83650.692793695475
+  (1 row)
+  ```
+
+- var_samp(expression)
+
+  描述：样本方差（样本标准差的平方）
+
+  返回类型：对于浮点类型的输入返回double precision类型，其他输入返回numeric类型。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT VAR_SAMP(inv_quantity_on_hand) FROM tpcds.inventory WHERE inv_warehouse_sk = 1;
+        var_samp
+  --------------------
+   83650.730277028768
+  (1 row)
+  ```
+
+- bit_and(expression)
+
+  描述：所有非NULL输入值的按位与(AND)，如果全部输入值皆为NULL，那么结果也为NULL 。
+
+  返回类型：和参数数据类型相同。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT BIT_AND(inv_quantity_on_hand) FROM tpcds.inventory WHERE inv_warehouse_sk = 1;
+   bit_and
+  ---------
+         0
+  (1 row)
+  ```
+
+- bit_or(expression)
+
+  描述：所有非NULL输入值的按位或(OR)，如果全部输入值皆为NULL，那么结果也为NULL。
+
+  返回类型：和参数数据类型相同
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT BIT_OR(inv_quantity_on_hand) FROM tpcds.inventory WHERE inv_warehouse_sk = 1;
+   bit_or
+  --------
+     1023
+  (1 row)
+  ```
+
+- bool_and(expression)
+
+  描述：如果所有输入值都是真，则为真，否则为假。
+
+  返回类型：bool
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT bool_and(100 <2500);
+   bool_and
+  ----------
+   t
+  (1 row)
+  ```
+
+- bool_or(expression)
+
+  描述：如果所有输入值只要有一个为真，则为真，否则为假。
+
+  返回类型：bool
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT bool_or(100 <2500);
+   bool_or
+  ----------
+   t
+  (1 row)
+  ```
+
+- corr(Y, X)
+
+  描述：相关系数
+
+  返回类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT CORR(sr_fee, sr_net_loss) FROM tpcds.store_returns WHERE sr_customer_sk < 1000;
+         corr
+  -------------------
+   .0381383624904186
+  (1 row)
+  ```
+
+- every(expression)
+
+  描述：等效于bool_and。
+
+  返回类型：bool
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT every(100 <2500);
+   every
+  -------
+   t
+  (1 row)
+  ```
+
+- regr_avgx(Y, X)
+
+  描述：自变量的平均值 (sum(X)/N)
+
+  返回类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT REGR_AVGX(sr_fee, sr_net_loss) FROM tpcds.store_returns WHERE sr_customer_sk < 1000;
+      regr_avgx
+  ------------------
+   578.606576740795
+  (1 row)
+  ```
+
+- regr_avgy(Y, X)
+
+  描述：因变量的平均值 (sum(Y)/N)
+
+  返回类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT REGR_AVGY(sr_fee, sr_net_loss) FROM tpcds.store_returns WHERE sr_customer_sk < 1000;
+      regr_avgy
+  ------------------
+   50.0136711629602
+  (1 row)
+  ```
+
+- regr_count(Y, X)
+
+  描述：两个表达式都不为NULL的输入行数。
+
+  返回类型：bigint
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT REGR_COUNT(sr_fee, sr_net_loss) FROM tpcds.store_returns WHERE sr_customer_sk < 1000;
+   regr_count
+  ------------
+         2743
+  (1 row)
+  ```
+
+- regr_intercept(Y, X)
+
+  描述：根据所有输入的点(X, Y)按照最小二乘法拟合成一个线性方程，然后返回该直线的Y轴截距。
+
+  返回类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT REGR_INTERCEPT(sr_fee, sr_net_loss) FROM tpcds.store_returns WHERE sr_customer_sk < 1000;
+    regr_intercept
+  ------------------
+   49.2040847848607
+  (1 row)
+  ```
+
+- regr_r2(Y, X)
+
+  描述：相关系数的平方
+
+  返回类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT REGR_R2(sr_fee, sr_net_loss) FROM tpcds.store_returns WHERE sr_customer_sk < 1000;
+        regr_r2
+  --------------------
+   .00145453469345058
+  (1 row)
+  ```
+
+- regr_slope(Y, X)
+
+  描述：根据所有输入的点(X, Y)按照最小二乘法拟合成一个线性方程， 然后返回该直线的斜率。
+
+  返回类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT REGR_SLOPE(sr_fee, sr_net_loss) FROM tpcds.store_returns WHERE sr_customer_sk < 1000;
+       regr_slope
+  --------------------
+   .00139920009665259
+  (1 row)
+  ```
+
+- regr_sxx(Y, X)
+
+  描述：sum(X^2) - sum(X)^2/N （自变量的"平方和"）
+
+  返回类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT REGR_SXX(sr_fee, sr_net_loss) FROM tpcds.store_returns WHERE sr_customer_sk < 1000;
+       regr_sxx
+  ------------------
+   1626645991.46135
+  (1 row)
+  ```
+
+- regr_sxy(Y, X)
+
+  描述：sum(X*Y) - sum(X)* sum(Y)/N （自变量和因变量的"乘方积"）
+
+  返回类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT REGR_SXY(sr_fee, sr_net_loss) FROM tpcds.store_returns WHERE sr_customer_sk < 1000;
+       regr_sxy
+  ------------------
+   2276003.22847225
+  (1 row)
+  ```
+
+- regr_syy(Y, X)
+
+  描述：sum(Y^2) - sum(Y)^2/N（因变量的"平方和"）
+
+  返回类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT REGR_SYY(sr_fee, sr_net_loss) FROM tpcds.store_returns WHERE sr_customer_sk < 1000;
+      regr_syy
+  -----------------
+   2189417.6547314
+  (1 row)
+  ```
+
+- stddev(expression)
+
+  描述：stddev_samp的别名。
+
+  返回类型：对于浮点类型的输入返回double precision，其他输入返回numeric。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT STDDEV(inv_quantity_on_hand) FROM tpcds.inventory WHERE inv_warehouse_sk = 1;
+        stddev
+  ------------------
+   289.224359757315
+  (1 row)
+  ```
+
+- variance(expexpression,ression)
+
+  描述：var_samp的别名。
+
+  返回类型：对于浮点类型的输入返回double precision类型，其他输入返回numeric类型。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT VARIANCE(inv_quantity_on_hand) FROM tpcds.inventory WHERE inv_warehouse_sk = 1;
+        variance
+  --------------------
+   83650.730277028768
+  (1 row)
+  ```
+
+- delta
+
+    描述：返回当前行和前一行的差值。
+
+    参数：numeric
+
+    返回值类型：numeric
+
+- checksum(expression)
+
+  描述：返回所有输入值的CHECKSUM值。使用该函数可以用来验证MogDB数据库（不支持MogDB之外的其他数据库）的备份恢复或者数据迁移操作前后表中的数据是否相同。在备份恢复或者数据迁移操作前后都需要用户通过手工执行SQL命令的方式获取执行结果，通过对比获取的执行结果判断操作前后表中的数据是否相同。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+  >
+  > - 对于大表，CHECKSUM函数可能会需要很长时间。
+  > - 如果某两表的CHECKSUM值不同，则表明两表的内容是不同的。由于CHECKSUM函数中使用散列函数不能保证无冲突，因此两个不同内容的表可能会得到相同的CHECKSUM值，存在这种情况的可能性较小。对于列进行的CHECKSUM也存在相同的情况。
+  > - 对于时间类型timestamp, timestamptz和smalldatetime，计算CHECKSUM值时请确保时区设置一致。
+
+  - 若计算某列的CHECKSUM值，且该列类型可以默认转为TEXT类型，则expression为列名。
+  - 若计算某列的CHECKSUM值，且该列类型不能默认转为TEXT类型，则expression为列名::TEXT。
+  - 若计算所有列的CHECKSUM值，则expression为表名::TEXT。
+
+  可以默认转换为TEXT类型的类型包括：char, name, int8, int2, int1, int4, raw, pg_node_tree, float4, float8, bpchar, varchar, nvarchar2, date, timestamp, timestamptz, numeric, smalldatetime，其他类型需要强制转换为TEXT。
+
+  返回类型：numeric。
+
+  示例：
+
+  表中可以默认转为TEXT类型的某列的CHECKSUM值。
+
+  ```sql
+  mogdb=# SELECT CHECKSUM(inv_quantity_on_hand) FROM tpcds.inventory;
+       checksum
+  -------------------
+   24417258945265247
+  (1 row)
+  ```
+
+  表中不能默认转为TEXT类型的某列的CHECKSUM值。注意此时CHECKSUM参数是列名::TEXT。
+
+  ```sql
+  mogdb=# SELECT CHECKSUM(inv_quantity_on_hand::TEXT) FROM tpcds.inventory;
+       checksum
+  -------------------
+   24417258945265247
+  (1 row)
+  ```
+
+  表中所有列的CHECKSUM值。注意此时CHECKSUM参数是表名::TEXT，且表名前不加Schema。
+
+  ```sql
+  mogdb=# SELECT CHECKSUM(inventory::TEXT) FROM tpcds.inventory;
+       checksum
+  -------------------
+   25223696246875800
+  (1 row)
+  ```
+
+- first(anyelement)
+
+    描述：返回第一个非NULL输入。
+
+    返回类型：anyelement
+
+    ```
+    mogdb=# select * from tba;
+    name
+    -----
+    A
+    A
+    D
+    (4 rows)
+
+    mogdb=# select first(name) from tba;
+    first
+    -----
+    A
+    (1 rows)
+    ```
+
+- last(anyelement)
+
+    描述：返回最后一个非NULL输入。
+
+    返回类型：anyelement
+
+    ```
+    mogdb=# select * from tba;
+    name
+    -----
+    A
+    A
+    D
+    (4 rows)
+
+    mogdb=# select last(name) from tba;
+    last
+    -----
+    D
+    (1 rows)
+    ```
+
+- mode() within group (order by value anyelement)
+
+  描述：返回某列中出现频率最高的值，如果多个值频率相同，则返回最小的那个值。排序方式和该列类型的默认排序方式相同。其中value为输入参数，可以为任意类型。
+
+  返回类型：与输入参数类型相同。
+
+  示例：
+
+  ```sql
+  mogdb=# select mode() within group (order by value) from (values(1, 'a'), (2, 'b'), (2, 'c')) v(value, tag);
+   mode
+  ------
+      2
+  (1 row)
+  mogdb=# select mode() within group (order by tag) from (values(1, 'a'), (2, 'b'), (2, 'c')) v(value, tag);
+   mode
+  ------
+   a
+  (1 row)
+  ```
+
+- json_agg(any)
+
+    描述：将值聚集为json数组。
+
+    返回类型：array-json
+
+    示例：
+
+    ```
+    mogdb=# select * from classes;
+    name | score
+    -----+-------
+    A    |     2
+    A    |     3
+    D    |     5
+    D    |
+    (4 rows)
+    ```
+
+    ```
+    mogdb=# select name, json_agg(score) score from classes group by name order by name;
+    name |      score
+    -----+-----------------
+    A    | [2, 3]
+    D    | [5, null]
+    | [null]
+    (3 rows)
+    ```
+
+- json_object_agg(any, any)
+
+    描述：将值聚集为json对象。
+
+    返回类型：object-json
+
+    示例：
+
+    ```
+    mogdb=# select * from classes;
+    name | score
+    -----+-------
+    A    |     2
+    A    |     3
+    D    |     5
+    D    |
+    (4 rows)
+    ```
+
+    ```
+    mogdb=# select json_object_agg(name, score) from classes group by name order by name;
+    json_object_agg
+    -------------------------
+    { "A" : 2, "A" : 3 }
+    { "D" : 5, "D" : null }
+    (2 rows)
+    ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/18-window-functions.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/18-window-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..15f65f015583be9f62928c80a231ed6cfc43968b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/18-window-functions.md
@@ -0,0 +1,629 @@
+---
+title: 窗口函数
+summary: 窗口函数
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 窗口函数
+
+列存表目前只支持rank(expression)和row_number(expression)两个函数。
+
+窗口函数与OVER语句一起使用。OVER语句用于对数据进行分组，并对组内元素进行排序。窗口函数用于给组内的值生成序号。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+> 窗口函数中的order by后面必须跟字段名，若order by后面跟数字，该数字会被按照常量处理，因此对目标列没有起到排序的作用。
+
+- RANK()
+
+  描述：RANK函数为各组内值生成跳跃排序序号，其中，相同的值具有相同序号。
+
+  返回值类型：BIGINT
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT d_moy, d_fy_week_seq, rank() OVER(PARTITION BY d_moy ORDER BY d_fy_week_seq) FROM tpcds.date_dim WHERE d_moy < 4 AND d_fy_week_seq < 7 ORDER BY 1,2;
+     d_moy | d_fy_week_seq | rank
+  -------+---------------+------
+       1 |             1 |    1
+       1 |             1 |    1
+       1 |             1 |    1
+       1 |             1 |    1
+       1 |             1 |    1
+       1 |             1 |    1
+       1 |             1 |    1
+       1 |             2 |    8
+       1 |             2 |    8
+       1 |             2 |    8
+       1 |             2 |    8
+       1 |             2 |    8
+       1 |             2 |    8
+       1 |             2 |    8
+       1 |             3 |   15
+       1 |             3 |   15
+       1 |             3 |   15
+       1 |             3 |   15
+       1 |             3 |   15
+       1 |             3 |   15
+       1 |             3 |   15
+       1 |             4 |   22
+       1 |             4 |   22
+       1 |             4 |   22
+       1 |             4 |   22
+       1 |             4 |   22
+       1 |             4 |   22
+       1 |             4 |   22
+       1 |             5 |   29
+       1 |             5 |   29
+       2 |             5 |    1
+       2 |             5 |    1
+       2 |             5 |    1
+       2 |             5 |    1
+       2 |             5 |    1
+       2 |             6 |    6
+       2 |             6 |    6
+       2 |             6 |    6
+       2 |             6 |    6
+       2 |             6 |    6
+       2 |             6 |    6
+       2 |             6 |    6
+  (42 rows)
+  ```
+
+- ROW_NUMBER()
+
+  描述：ROW_NUMBER函数为各组内值生成连续排序序号，其中，相同的值其序号也不相同。
+
+  返回值类型：BIGINT
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT d_moy, d_fy_week_seq, Row_number() OVER(PARTITION BY d_moy ORDER BY d_fy_week_seq) FROM tpcds.date_dim  WHERE d_moy < 4 AND d_fy_week_seq < 7 ORDER BY 1,2;
+   d_moy | d_fy_week_seq | row_number
+  -------+---------------+------------
+       1 |             1 |          1
+       1 |             1 |          2
+       1 |             1 |          3
+       1 |             1 |          4
+       1 |             1 |          5
+       1 |             1 |          6
+       1 |             1 |          7
+       1 |             2 |          8
+       1 |             2 |          9
+       1 |             2 |         10
+       1 |             2 |         11
+       1 |             2 |         12
+       1 |             2 |         13
+       1 |             2 |         14
+       1 |             3 |         15
+       1 |             3 |         16
+       1 |             3 |         17
+       1 |             3 |         18
+       1 |             3 |         19
+       1 |             3 |         20
+       1 |             3 |         21
+       1 |             4 |         22
+       1 |             4 |         23
+       1 |             4 |         24
+       1 |             4 |         25
+       1 |             4 |         26
+       1 |             4 |         27
+       1 |             4 |         28
+       1 |             5 |         29
+       1 |             5 |         30
+       2 |             5 |          1
+       2 |             5 |          2
+       2 |             5 |          3
+       2 |             5 |          4
+       2 |             5 |          5
+       2 |             6 |          6
+       2 |             6 |          7
+       2 |             6 |          8
+       2 |             6 |          9
+       2 |             6 |         10
+       2 |             6 |         11
+       2 |             6 |         12
+  (42 rows)
+  ```
+
+- DENSE_RANK()
+
+  描述：DENSE_RANK函数为各组内值生成连续排序序号，其中，相同的值具有相同序号。
+
+  返回值类型：BIGINT
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT d_moy, d_fy_week_seq, dense_rank() OVER(PARTITION BY d_moy ORDER BY d_fy_week_seq) FROM tpcds.date_dim WHERE d_moy < 4 AND d_fy_week_seq < 7 ORDER BY 1,2;
+   d_moy | d_fy_week_seq | dense_rank
+  -------+---------------+------------
+       1 |             1 |          1
+       1 |             1 |          1
+       1 |             1 |          1
+       1 |             1 |          1
+       1 |             1 |          1
+       1 |             1 |          1
+       1 |             1 |          1
+       1 |             2 |          2
+       1 |             2 |          2
+       1 |             2 |          2
+       1 |             2 |          2
+       1 |             2 |          2
+       1 |             2 |          2
+       1 |             2 |          2
+       1 |             3 |          3
+       1 |             3 |          3
+       1 |             3 |          3
+       1 |             3 |          3
+       1 |             3 |          3
+       1 |             3 |          3
+       1 |             3 |          3
+       1 |             4 |          4
+       1 |             4 |          4
+       1 |             4 |          4
+       1 |             4 |          4
+       1 |             4 |          4
+       1 |             4 |          4
+       1 |             4 |          4
+       1 |             5 |          5
+       1 |             5 |          5
+       2 |             5 |          1
+       2 |             5 |          1
+       2 |             5 |          1
+       2 |             5 |          1
+       2 |             5 |          1
+       2 |             6 |          2
+       2 |             6 |          2
+       2 |             6 |          2
+       2 |             6 |          2
+       2 |             6 |          2
+       2 |             6 |          2
+       2 |             6 |          2
+  (42 rows)
+  ```
+
+- PERCENT_RANK()
+
+  描述：PERCENT_RANK函数为各组内对应值生成相对序号，即根据公式 (rank - 1) / (total rows - 1)计算所得的值。其中rank为该值依据RANK函数所生成的对应序号，totalrows为该分组内的总元素个数。
+
+  返回值类型：DOUBLE PRECISION
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT d_moy, d_fy_week_seq, percent_rank() OVER(PARTITION BY d_moy ORDER BY d_fy_week_seq) FROM tpcds.date_dim WHERE d_moy < 4 AND d_fy_week_seq < 7 ORDER BY 1,2;
+   d_moy | d_fy_week_seq |   percent_rank
+  -------+---------------+------------------
+       1 |             1 |                0
+       1 |             1 |                0
+       1 |             1 |                0
+       1 |             1 |                0
+       1 |             1 |                0
+       1 |             1 |                0
+       1 |             1 |                0
+       1 |             2 | .241379310344828
+       1 |             2 | .241379310344828
+       1 |             2 | .241379310344828
+       1 |             2 | .241379310344828
+       1 |             2 | .241379310344828
+       1 |             2 | .241379310344828
+       1 |             2 | .241379310344828
+       1 |             3 | .482758620689655
+       1 |             3 | .482758620689655
+       1 |             3 | .482758620689655
+       1 |             3 | .482758620689655
+       1 |             3 | .482758620689655
+       1 |             3 | .482758620689655
+       1 |             3 | .482758620689655
+       1 |             4 | .724137931034483
+       1 |             4 | .724137931034483
+       1 |             4 | .724137931034483
+       1 |             4 | .724137931034483
+       1 |             4 | .724137931034483
+       1 |             4 | .724137931034483
+       1 |             4 | .724137931034483
+       1 |             5 |  .96551724137931
+       1 |             5 |  .96551724137931
+       2 |             5 |                0
+       2 |             5 |                0
+       2 |             5 |                0
+       2 |             5 |                0
+       2 |             5 |                0
+       2 |             6 | .454545454545455
+       2 |             6 | .454545454545455
+       2 |             6 | .454545454545455
+       2 |             6 | .454545454545455
+       2 |             6 | .454545454545455
+       2 |             6 | .454545454545455
+       2 |             6 | .454545454545455
+  (42 rows)
+  ```
+
+- CUME_DIST()
+
+  描述：CUME_DIST函数为各组内对应值生成累积分布序号。即根据公式(小于等于当前值的数据行数)/(该分组总行数totalrows)计算所得的相对序号。
+
+  返回值类型：DOUBLE PRECISION
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT d_moy, d_fy_week_seq, cume_dist() OVER(PARTITION BY d_moy ORDER BY d_fy_week_seq) FROM tpcds.date_dim e_dim WHERE d_moy < 4 AND d_fy_week_seq < 7 ORDER BY 1,2;
+   d_moy | d_fy_week_seq |    cume_dist
+  -------+---------------+------------------
+       1 |             1 | .233333333333333
+       1 |             1 | .233333333333333
+       1 |             1 | .233333333333333
+       1 |             1 | .233333333333333
+       1 |             1 | .233333333333333
+       1 |             1 | .233333333333333
+       1 |             1 | .233333333333333
+       1 |             2 | .466666666666667
+       1 |             2 | .466666666666667
+       1 |             2 | .466666666666667
+       1 |             2 | .466666666666667
+       1 |             2 | .466666666666667
+       1 |             2 | .466666666666667
+       1 |             2 | .466666666666667
+       1 |             3 |               .7
+       1 |             3 |               .7
+       1 |             3 |               .7
+       1 |             3 |               .7
+       1 |             3 |               .7
+       1 |             3 |               .7
+       1 |             3 |               .7
+       1 |             4 | .933333333333333
+       1 |             4 | .933333333333333
+       1 |             4 | .933333333333333
+       1 |             4 | .933333333333333
+       1 |             4 | .933333333333333
+       1 |             4 | .933333333333333
+       1 |             4 | .933333333333333
+       1 |             5 |                1
+       1 |             5 |                1
+       2 |             5 | .416666666666667
+       2 |             5 | .416666666666667
+       2 |             5 | .416666666666667
+       2 |             5 | .416666666666667
+       2 |             5 | .416666666666667
+       2 |             6 |                1
+       2 |             6 |                1
+       2 |             6 |                1
+       2 |             6 |                1
+       2 |             6 |                1
+       2 |             6 |                1
+       2 |             6 |                1
+  (42 rows)
+  ```
+
+- NTILE(num_buckets integer)
+
+  描述：NTILE函数根据num_buckets integer将有序的数据集合平均分配到num_buckets所指定数量的桶中，并将桶号分配给每一行。分配时应尽量做到平均分配。
+
+  返回值类型：INTEGER
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT d_moy, d_fy_week_seq, ntile(3) OVER(PARTITION BY d_moy ORDER BY d_fy_week_seq) FROM tpcds.date_dim WHERE d_moy < 4 AND d_fy_week_seq < 7 ORDER BY 1,2;
+   d_moy | d_fy_week_seq | ntile
+  -------+---------------+-------
+       1 |             1 |     1
+       1 |             1 |     1
+       1 |             1 |     1
+       1 |             1 |     1
+       1 |             1 |     1
+       1 |             1 |     1
+       1 |             1 |     1
+       1 |             2 |     1
+       1 |             2 |     1
+       1 |             2 |     1
+       1 |             2 |     2
+       1 |             2 |     2
+       1 |             2 |     2
+       1 |             2 |     2
+       1 |             3 |     2
+       1 |             3 |     2
+       1 |             3 |     2
+       1 |             3 |     2
+       1 |             3 |     2
+       1 |             3 |     2
+       1 |             3 |     3
+       1 |             4 |     3
+       1 |             4 |     3
+       1 |             4 |     3
+       1 |             4 |     3
+       1 |             4 |     3
+       1 |             4 |     3
+       1 |             4 |     3
+       1 |             5 |     3
+       1 |             5 |     3
+       2 |             5 |     1
+       2 |             5 |     1
+       2 |             5 |     1
+       2 |             5 |     1
+       2 |             5 |     2
+       2 |             6 |     2
+       2 |             6 |     2
+       2 |             6 |     2
+       2 |             6 |     3
+       2 |             6 |     3
+       2 |             6 |     3
+       2 |             6 |     3
+  (42 rows)
+  ```
+
+- LAG(value any [, offset integer [, default any ]])
+
+  描述：LAG函数为各组内对应值生成滞后值。即当前值对应的行数往前偏移offset位后所得行的value值作为序号。若经过偏移后行数不存在，则对应结果取为default值。若无指定，在默认情况下，offset取为1，default值取为NULL。
+
+  返回值类型：与参数数据类型相同。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT d_moy, d_fy_week_seq, lag(d_moy,3,null) OVER(PARTITION BY d_moy ORDER BY d_fy_week_seq) FROM tpcds.date_dim WHERE d_moy < 4 AND d_fy_week_seq < 7 ORDER BY 1,2;
+   d_moy | d_fy_week_seq | lag
+  -------+---------------+-----
+       1 |             1 |
+       1 |             1 |
+       1 |             1 |
+       1 |             1 |   1
+       1 |             1 |   1
+       1 |             1 |   1
+       1 |             1 |   1
+       1 |             2 |   1
+       1 |             2 |   1
+       1 |             2 |   1
+       1 |             2 |   1
+       1 |             2 |   1
+       1 |             2 |   1
+       1 |             2 |   1
+       1 |             3 |   1
+       1 |             3 |   1
+       1 |             3 |   1
+       1 |             3 |   1
+       1 |             3 |   1
+       1 |             3 |   1
+       1 |             3 |   1
+       1 |             4 |   1
+       1 |             4 |   1
+       1 |             4 |   1
+       1 |             4 |   1
+       1 |             4 |   1
+       1 |             4 |   1
+       1 |             4 |   1
+       1 |             5 |   1
+       1 |             5 |   1
+       2 |             5 |
+       2 |             5 |
+       2 |             5 |
+       2 |             5 |   2
+       2 |             5 |   2
+       2 |             6 |   2
+       2 |             6 |   2
+       2 |             6 |   2
+       2 |             6 |   2
+       2 |             6 |   2
+       2 |             6 |   2
+       2 |             6 |   2
+  (42 rows)
+  ```
+
+- LEAD(value any [, offset integer [, default any ]])
+
+  描述：LEAD函数为各组内对应值生成提前值。即当前值对应的行数向后偏移offset位后所得行的value值作为序号。若经过向后偏移后行数超过当前组内的总行数，则对应结果取为default值。若无指定，在默认情况下，offset取为1，default值取为NULL。
+
+  返回值类型：与参数数据类型相同。
+
+  示例：
+
+  ```sql
+    mogdb=# SELECT d_moy, d_fy_week_seq, lead(d_fy_week_seq,2) OVER(PARTITION BY d_moy ORDER BY d_fy_week_seq) FROM  tpcds.date_dim WHERE d_moy < 4 AND d_fy_week_seq < 7 ORDER BY 1,2;
+    d_moy | d_fy_week_seq | lead
+    -------+---------------+------
+         1 |             1 |    1
+         1 |             1 |    1
+         1 |             1 |    1
+         1 |             1 |    1
+         1 |             1 |    1
+         1 |             1 |    2
+         1 |             1 |    2
+         1 |             2 |    2
+         1 |             2 |    2
+         1 |             2 |    2
+         1 |             2 |    2
+         1 |             2 |    2
+         1 |             2 |    3
+         1 |             2 |    3
+         1 |             3 |    3
+         1 |             3 |    3
+         1 |             3 |    3
+         1 |             3 |    3
+         1 |             3 |    3
+         1 |             3 |    4
+         1 |             3 |    4
+         1 |             4 |    4
+         1 |             4 |    4
+         1 |             4 |    4
+         1 |             4 |    4
+         1 |             4 |    4
+         1 |             4 |    5
+         1 |             4 |    5
+         1 |             5 |
+         1 |             5 |
+         2 |             5 |    5
+         2 |             5 |    5
+         2 |             5 |    5
+         2 |             5 |    6
+         2 |             5 |    6
+         2 |             6 |    6
+         2 |             6 |    6
+         2 |             6 |    6
+         2 |             6 |    6
+         2 |             6 |    6
+         2 |             6 |
+         2 |             6 |
+    (42 rows)
+  ```
+
+- FIRST_VALUE(value any)
+
+  描述：FIRST_VALUE函数取各组内的第一个值作为返回结果。
+
+  返回值类型：与参数数据类型相同。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT d_moy, d_fy_week_seq, first_value(d_fy_week_seq) OVER(PARTITION BY d_moy ORDER BY d_fy_week_seq) FROM tpcds.date_dim WHERE d_moy < 4 AND d_fy_week_seq < 7 ORDER BY 1,2;
+   d_moy | d_fy_week_seq | first_value
+  -------+---------------+-------------
+       1 |             1 |           1
+       1 |             1 |           1
+       1 |             1 |           1
+       1 |             1 |           1
+       1 |             1 |           1
+       1 |             1 |           1
+       1 |             1 |           1
+       1 |             2 |           1
+       1 |             2 |           1
+       1 |             2 |           1
+       1 |             2 |           1
+       1 |             2 |           1
+       1 |             2 |           1
+       1 |             2 |           1
+       1 |             3 |           1
+       1 |             3 |           1
+       1 |             3 |           1
+       1 |             3 |           1
+       1 |             3 |           1
+       1 |             3 |           1
+       1 |             3 |           1
+       1 |             4 |           1
+       1 |             4 |           1
+       1 |             4 |           1
+       1 |             4 |           1
+       1 |             4 |           1
+       1 |             4 |           1
+       1 |             4 |           1
+       1 |             5 |           1
+       1 |             5 |           1
+       2 |             5 |           5
+       2 |             5 |           5
+       2 |             5 |           5
+       2 |             5 |           5
+       2 |             5 |           5
+       2 |             6 |           5
+       2 |             6 |           5
+       2 |             6 |           5
+       2 |             6 |           5
+       2 |             6 |           5
+       2 |             6 |           5
+       2 |             6 |           5
+  (42 rows)
+  ```
+
+- LAST_VALUE(value any)
+
+  描述：LAST_VALUE函数取各组内的最后一个值作为返回结果。
+
+  返回值类型：与参数数据类型相同。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT d_moy, d_fy_week_seq, last_value(d_moy) OVER(PARTITION BY d_moy ORDER BY d_fy_week_seq) FROM tpcds.date_dim WHERE d_moy < 4 AND d_fy_week_seq < 6 ORDER BY 1,2;
+    d_moy | d_fy_week_seq | last_value
+  -------+---------------+------------
+       1 |             1 |          1
+       1 |             1 |          1
+       1 |             1 |          1
+       1 |             1 |          1
+       1 |             1 |          1
+       1 |             1 |          1
+       1 |             1 |          1
+       1 |             2 |          1
+       1 |             2 |          1
+       1 |             2 |          1
+       1 |             2 |          1
+       1 |             2 |          1
+       1 |             2 |          1
+       1 |             2 |          1
+       1 |             2 |          1
+       1 |             3 |          1
+       1 |             3 |          1
+       1 |             3 |          1
+       1 |             3 |          1
+       1 |             3 |          1
+       1 |             3 |          1
+       1 |             3 |          1
+       1 |             4 |          1
+       1 |             4 |          1
+       1 |             4 |          1
+       1 |             4 |          1
+       1 |             4 |          1
+       1 |             4 |          1
+       1 |             4 |          1
+       1 |             5 |          1
+       1 |             5 |          1
+       2 |             5 |          2
+       2 |             5 |          2
+       2 |             5 |          2
+       2 |             5 |          2
+       2 |             5 |          2
+  (35 rows)
+  ```
+
+- NTH_VALUE(value any, nth integer)
+
+  描述：NTH_VALUE函数返回该组内的第nth行作为结果。若该行不存在，则默认返回NULL。
+
+  返回值类型：与参数数据类型相同。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT d_moy, d_fy_week_seq, nth_value(d_fy_week_seq,6) OVER(PARTITION BY d_moy ORDER BY d_fy_week_seq) FROM tpcds.date_dim WHERE d_moy < 4 AND d_fy_week_seq < 6 ORDER BY 1,2;
+   d_moy | d_fy_week_seq | nth_value
+  -------+---------------+-----------
+       1 |             1 |         1
+       1 |             1 |         1
+       1 |             1 |         1
+       1 |             1 |         1
+       1 |             1 |         1
+       1 |             1 |         1
+       1 |             1 |         1
+       1 |             2 |         1
+       1 |             2 |         1
+       1 |             2 |         1
+       1 |             2 |         1
+       1 |             2 |         1
+       1 |             2 |         1
+       1 |             2 |         1
+       1 |             3 |         1
+       1 |             3 |         1
+       1 |             3 |         1
+       1 |             3 |         1
+       1 |             3 |         1
+       1 |             3 |         1
+       1 |             3 |         1
+       1 |             4 |         1
+       1 |             4 |         1
+       1 |             4 |         1
+       1 |             4 |         1
+       1 |             4 |         1
+       1 |             4 |         1
+       1 |             4 |         1
+       1 |             5 |         1
+       1 |             5 |         1
+       2 |             5 |
+       2 |             5 |
+       2 |             5 |
+       2 |             5 |
+       2 |             5 |
+  (35 rows)
+  ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/19-security-functions.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/19-security-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..5e9bb93b5bd9fa3c2723d770fe6ebda025ea784c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/19-security-functions.md
@@ -0,0 +1,273 @@
+---
+title: 安全函数
+summary: 安全函数
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 安全函数
+
+- gs_encrypt_aes128(encryptstr,keystr)
+
+描述：以keystr为密钥对encryptstr字符串进行加密，返回加密后的字符串。keystr的长度范围为8~16字节，至少包含3种字符（大写字母、小写字母、数字、特殊字符）。
+
+返回值类型：text
+
+返回值长度：至少为92字节，不超过4*[(Len+68)/3]字节，其中Len为加密前数据长度（单位为字节）。
+
+示例：
+
+```sql
+mogdb=# SELECT gs_encrypt_aes128('MPPDB','Asdf1234');
+
+                                gs_encrypt_aes128
+ -------------------------------------------------------------------------------------
+ gwditQLQG8NhFw4OuoKhhQJoXojhFlYkjeG0aYdSCtLCnIUgkNwvYI04KbuhmcGZp8jWizBdR1vU9CspjuzI0lbz12A=
+ (1 row)
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> 由于该函数的执行过程需要传入解密口令，为了安全起见，gsql工具不会将该函数记录入执行历史。即无法在gsql里通过上下翻页功能找到该函数的执行历史。
+
+- gs_encrypt(encryptstr,keystr,encrypttype)
+
+描述：根据encrypttype，以keystr为密钥对encryptstr字符串进行加密，返回加密后的字符串。keystr的长度范围为8~16字节，至少包含3种字符（大写字母、小写字母、数字、特殊字符），encrypttype可以是aes128或sm4。
+
+返回值类型：text
+
+示例：
+
+```sql
+mogdb=#  SELECT gs_encrypt('MPPDB','Asdf1234','sm4');
+          gs_encrypt
+  ------------------------------
+  ZBzOmaGA4Bb+coyucJ0B8AkIShqc
+ (1 row)
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> 由于该函数的执行过程需要传入解密口令，为了安全起见，gsql工具不会将该函数记录入执行历史。即无法在gsql里通过上下翻页功能找到该函数的执行历史。
+
+- gs_decrypt_aes128(decryptstr,keystr)
+
+描述：以keystr为密钥对decrypt字符串进行解密，返回解密后的字符串。解密使用的keystr必须保证与加密时使用的keystr一致才能正常解密。keystr不得为空。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> 此参数需要结合gs_encrypt_aes128加密函数共同使用。
+
+返回值类型：text
+
+示例：
+
+```sql
+mogdb=# SELECT gs_decrypt_aes128('gwditQLQG8NhFw4OuoKhhQJoXojhFlYkjeG0aYdSCtLCnIUgkNwvYI04KbuhmcGZp8jWizBdR1vU9CspjuzI0lbz12A=','1234');
+  gs_decrypt_aes128
+ -------------------
+  MPPDB
+ (1 row)
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> 由于该函数的执行过程需要传入解密口令，为了安全起见，gsql工具不会将该函数记录入执行历史；即无法在gsql里通过上下翻页功能找到该函数的执行历史。
+
+- gs_decrypt(decryptstr,keystr,decrypttype)
+
+描述：根据decrypttype，以keystr为密钥对decrypt字符串进行解密，返回解密后的字符串。解密使用的decrypttype及keystr必须保证与加密时使用的encrypttype及keystr一致才能正常解密。keystr不得为空。decrypttype可以是aes128或sm4。
+
+此函数需要结合gs_encrypt加密函数共同使用。
+
+返回值类型：text
+
+示例：
+
+```sql
+mogdb=# select gs_decrypt('ZBzOmaGA4Bb+coyucJ0B8AkIShqc','Asdf1234','sm4');
+  gs_decrypt
+ ------------
+  MPPDB
+ (1 row)
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> 由于该函数的执行过程需要传入解密口令，为了安全起见，gsql工具不会将该函数记录入执行历史；即无法在gsql里通过上下翻页功能找到该函数的执行历史。
+
+- gs_password_deadline
+
+  描述：显示当前帐户密码离过期还距离多少天。
+
+  返回值类型：interval
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT gs_password_deadline();
+    gs_password_deadline
+  -------------------------
+   83 days 17:44:32.196094
+  (1 row)
+  ```
+
+- gs_password_notifytime
+
+  描述：显示帐户密码到期前提醒的天数。
+
+  返回值类型：int32
+
+- login_audit_messages
+
+  描述：查看登录用户的登录信息。
+
+  返回值类型：元组
+
+  示例：
+
+  - 查看上一次登录认证通过的日期、时间和IP等信息。
+
+    ```sql
+    mogdb=> select * from login_audit_messages(true);
+    username | database |       logintime    |    mytype     | result | client_conninfo
+    ----------+----------+------------------------+---------------+--------+-----------------
+    omm      | openGauss | 2020-06-29 21:56:40+08 | login_success | ok     | gsql@[local]
+    (1 row)
+    ```
+
+  - 查看上一次登录认证失败的日期、时间和IP等信息。
+
+    ```sql
+    mogdb=>  select * from login_audit_messages(false) ORDER BY logintime desc limit 1;
+    username | database |       logintime    |    mytype    | result |  client_conninfo
+    ----------+----------+------------------------+--------------+--------+-------------------
+    omm      | openGauss | 2020-06-29 21:57:55+08 | login_failed | failed | [unknown]@[local]
+    (1 row)
+    ```
+
+  - 查看自从最后一次认证通过以来失败的尝试次数、日期和时间。
+
+    ```sql
+    mogdb=>  select * from login_audit_messages(false);
+    username | database |       logintime    |    mytype    | result |  client_conninfo
+    ----------+----------+------------------------+--------------+--------+-------------------
+    omm      | openGauss | 2020-06-29 21:57:55+08 | login_failed | failed | [unknown]@[local]
+    omm      | openGauss | 2020-06-29 21:57:53+08 | login_failed | failed | [unknown]@[local]
+    (2 rows)
+    ```
+
+- login_audit_messages_pid
+
+  描述：查看登录用户的登录信息。与login_audit_messages的区别在于结果基于当前backendid向前查找。所以不会因为同一用户的后续登录，而影响本次登录的查询结果。也就是查询不到该用户后续登录的信息。
+
+  返回值类型：元组
+
+  示例：
+
+  - 查看上一次登录认证通过的日期、时间和IP等信息。
+
+    ```sql
+    mogdb=> SELECT * FROM login_audit_messages_pid(true);
+    username | database |       logintime    |    mytype     | result | client_conninfo |    backendid
+    ----------+----------+------------------------+---------------+--------+-----------------+-----------------
+    omm      | openGauss | 2020-06-29 21:56:40+08 | login_success | ok     | gsql@[local]    | 139823109633792
+    (1 row)
+    ```
+
+  - 查看上一次登录认证失败的日期、时间和IP等信息。
+
+    ```sql
+    mogdb=> SELECT * FROM login_audit_messages_pid(false) ORDER BY logintime desc limit 1;
+    username | database |       logintime        |    mytype    | result |  client_conninfo  |    backendid
+    ----------+----------+------------------------+--------------+--------+-------------------+-----------------
+    omm      | openGauss | 2020-06-29 21:57:55+08 | login_failed | failed | [unknown]@[local] | 139823109633792
+    (1 row)
+    ```
+
+  - 查看自从最后一次认证通过以来失败的尝试次数、日期和时间。
+
+    ```sql
+    mogdb=> SELECT * FROM login_audit_messages_pid(false);
+    username | database |       logintime        |    mytype    | result |  client_conninfo  |    backendid
+    ----------+----------+------------------------+--------------+--------+-------------------+-----------------
+    omm      | openGauss | 2020-06-29 21:57:55+08 | login_failed | failed | [unknown]@[local] | 139823109633792
+    omm      | openGauss | 2020-06-29 21:57:53+08 | login_failed | failed | [unknown]@[local] | 139823109633792
+    (2 rows)
+    ```
+
+- inet_server_addr
+
+描述：显示服务器IP信息。
+
+返回值类型：inet
+
+示例：
+
+```sql
+mogdb=# SELECT inet_server_addr();
+  inet_server_addr
+ ------------------
+  10.10.0.13
+ (1 row)
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 上面是以客户端在10.10.0.50上，服务器端在10.10.0.13上为例。
+> - 如果是通过本地连接，使用此接口显示为空。
+
+- inet_client_addr
+
+描述：显示客户端IP信息。
+
+返回值类型：inet
+
+示例：
+
+```sql
+mogdb=# SELECT inet_client_addr();
+  inet_client_addr
+ ------------------
+  10.10.0.50
+ (1 row)
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 上面是以客户端在10.10.0.50上，服务器端在10.10.0.13上为例。
+> - 如果是通过本地连接，使用此接口显示为空。
+
+- pg_query_audit
+
+  描述：查看数据库主节点审计日志。
+
+  返回值类型：record
+
+  函数返回字段如下：
+
+  | 名称            | 类型                     | 描述             |
+  | :-------------- | :----------------------- | :--------------- |
+  | time            | timestamp with time zone | 操作时间         |
+  | type            | text                     | 操作类型         |
+  | result          | text                     | 操作结果         |
+  | userid          | oid                      | 用户id           |
+  | username        | text                     | 执行操作的用户名 |
+  | database        | text                     | 数据库名称       |
+  | client_conninfo | text                     | 客户端连接信息   |
+  | object_name     | text                     | 操作对象名称     |
+  | detail_info     | text                     | 执行操作详细信息 |
+  | node_name       | text                     | 节点名称         |
+  | thread_id       | text                     | 线程id           |
+  | local_port      | text                     | 本地端口         |
+  | remote_port     | text                     | 远端端口         |
+
+  函数使用方法及示例请参考[查看审计结果](3-configuring-database-audit#查看审计结果)。
+
+- pg_delete_audit
+
+  描述：删除指定时间段的审计日志。
+
+  返回值类型：void
+
+  函数使用方法及示例请参考[维护审计日志](3-configuring-database-audit#维护审计日志)。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/2-comparison-operators.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/2-comparison-operators.md
new file mode 100644
index 0000000000000000000000000000000000000000..83cb70a1658713b8ed84cf17f7cfe05dc54078e1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/2-comparison-operators.md
@@ -0,0 +1,27 @@
+---
+title: 比较操作符
+summary: 比较操作符
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 比较操作符
+
+大部分数据类型都可用比较操作符进行比较，并返回一个布尔类型的值。
+
+比较操作符均为双目操作符，被比较的两个数据类型必须是相同的数据类型或者是可以进行隐式转换的类型。
+
+MogDB提供的比较操作符请参见[表1](#比较操作符)。
+
+**表 1** 比较操作符<a id="比较操作符"> </a>
+
+| 操作符             | 描述       |
+| :----------------- | :--------- |
+| &lt;               | 小于       |
+| &gt;               | 大于       |
+| &lt;=              | 小于或等于 |
+| &gt;=              | 大于或等于 |
+| =                  | 等于       |
+| &lt;&gt; 或 !=或^= | 不等于     |
+
+比较操作符可以用于所有相关的数据类型。所有比较操作符都是双目操作符，返回布尔类型数值。不等号的计算优先级高于等号。当输入的数据不同且无法隐式转换时, 比较操作将会失败。例如像1&lt;2&lt;3这样的表达式是非法的，因为布尔值和3之间无法用小于号（&lt;）比较。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/20-encrypted-equality-functions.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/20-encrypted-equality-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..e1dbdcf53fc2cfcf8a97088f591f26f7aa18f66c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/20-encrypted-equality-functions.md
@@ -0,0 +1,187 @@
+---
+title: 密态等值的函数
+summary: 密态等值的函数
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 密态等值的函数
+
+- byteawithoutorderwithequalcolin(cstring)
+
+  描述: 将输入转码转化成内部byteawithoutorderwithequalcol形式。
+
+  参数类型: cstring
+
+  返回值类型: byteawithoutorderwithequalcol
+
+- byteawithoutorderwithequalcolout(byteawithoutorderwithequalcol)
+
+  描述: 将内部byteawithoutorderwithequalcol类型的数据转码转化为cstring类型。
+
+  参数类型: byteawithoutorderwithequalcol
+
+  返回值类型: cstring
+
+- byteawithoutorderwithequalcolsend(byteawithoutorderwithequalcol)
+
+  描述: 将byteawithoutorderwithequalcol类型的数据转码转化为bytea类型。
+
+  参数类型: byteawithoutorderwithequalcol
+
+  返回值类型: bytea
+
+- byteawithoutorderwithequalcolrecv(internal)
+
+  描述: 将byteawithoutorderwithequalcol类型的数据转码转化为byteawithoutorderwithequalcol类型。
+
+  参数类型: internal
+
+  返回值类型: byteawithoutorderwithequalcol
+
+- byteawithoutorderwithequalcoltypmodin(_cstring)
+
+  描述: 将byteawithoutorderwithequalcol类型的数据转码转化为byteawithoutorderwithequalcol类型。
+
+  参数类型: _cstring
+
+  返回值类型: int4
+
+- byteawithoutorderwithequalcoltypmodout(int4)
+
+  描述: 将int4类型的数据转码转化为cstring类型。
+
+  参数类型: int4
+
+  返回值类型: cstring
+
+- byteawithoutordercolin(cstring)
+
+  描述: 将输入转码转化成内部byteawithoutordercolin形式。
+
+  参数类型: cstring
+
+  返回值类型: byteawithoutordercol
+
+- byteawithoutordercolout(byteawithoutordercol)
+
+  描述: 将内部byteawithoutordercol类型的数据转码转化为cstring类型。
+
+  参数类型: byteawithoutordercol
+
+  返回值类型: cstring
+
+- byteawithoutordercolsend(byteawithoutordercol)
+
+  描述: 将byteawithoutordercol类型的数据转码转化为bytea类型。
+
+  参数类型: byteawithoutordercol
+
+  返回值类型: bytea
+
+- byteawithoutordercolrecv(internal)
+
+  描述: 将byteawithoutordercol类型的数据转码转化为byteawithoutordercol类型。
+
+  参数类型: internal
+
+  返回值类型: byteawithoutordercol
+
+- byteawithoutorderwithequalcolcmp(byteawithoutorderwithequalcol, byteawithoutorderwithequalcol)
+
+  描述: 比较两个byteawithoutorderwithequalcol类型的数据大小，若第一个参数小于第二个参数，返回-1，若等于，返回0，若大于，则返回1。
+
+  参数类型: byteawithoutorderwithequalcol, byteawithoutorderwithequalcol
+
+  返回值类型: int4
+
+- byteawithoutorderwithequalcolcmpbytear(byteawithoutorderwithequalcol, bytea)
+
+  描述: 比较byteawithoutorderwithequalcol和bytea数据大小，若第一个参数小于第二个参数，返回-1，若等于，返回0，若大于，则返回1。
+
+  参数类型: byteawithoutorderwithequalcol, bytea
+
+  返回值类型: int4
+
+- byteawithoutorderwithequalcolcmpbyteal(bytea, byteawithoutorderwithequalcol)
+
+  描述: 比较bytea和byteawithoutorderwithequalcol数据大小，若第一个参数小于第二个参数，返回-1，若等于，返回0，若大于，则返回1。
+
+  参数类型: byteawithoutorderwithequalcol, bytea
+
+  返回值类型: int4
+
+- byteawithoutorderwithequalcoleq(byteawithoutorderwithequalcol, byteawithoutorderwithequalcol)
+
+  描述: 比较两个byteawithoutorderwithequalcol类型的数据是否相同，相同则返回true，否则返回false。
+
+  参数类型: byteawithoutorderwithequalcol, bytea
+
+  返回值类型: bool
+
+- byteawithoutorderwithequalcoleqbyteal(bytea, byteawithoutorderwithequalcol)
+
+  描述: 比较bytea和byteawithoutorderwithequalcol数据是否相同，相同则返回true，否则返回false。
+
+  参数类型: bytea，byteawithoutorderwithequalcol
+
+  返回值类型: bool
+
+- byteawithoutorderwithequalcoleqbytear(byteawithoutorderwithequalcol, bytea)
+
+  描述: 比较byteawithoutorderwithequalcol和bytea数据是否相同，相同则返回true，否则返回false。
+
+  参数类型: byteawithoutorderwithequalcol, bytea
+
+  返回值类型: bool
+
+- byteawithoutorderwithequalcolne(byteawithoutorderwithequalcol, byteawithoutorderwithequalcol)
+
+  描述: 比较两个byteawithoutorderwithequalcol类型的数据是否不相同，不相同则返回true，否则返回false。
+
+  参数类型: byteawithoutorderwithequalcol, byteawithoutorderwithequalcol
+
+  返回值类型: bool
+
+- byteawithoutorderwithequalcolnebyteal(bytea, byteawithoutorderwithequalcol)
+
+  描述: 比较bytea和byteawithoutorderwithequalcol数据是否相同，相同则返回true，否则返回false。
+
+  参数类型: bytea，byteawithoutorderwithequalcol
+
+  返回值类型: bool
+
+- byteawithoutorderwithequalcolnebytear(byteawithoutorderwithequalcol, bytea)
+
+  描述: 比较byteawithoutorderwithequalcol和bytea数据是否不相同，相同则返回true，否则返回false。
+
+  参数类型: byteawithoutorderwithequalcol, bytea
+
+  返回值类型: bool
+
+- hll_hash_byteawithoutorderwithequalcol(byteawithoutorderwithequalcol)
+
+  描述: 返回byteawithoutorderwithequalcol的hll哈希值。
+
+  参数类型: byteawithoutorderwithequalcol
+
+  返回值类型: hll_hashval
+
+  由于byteawithoutorderwithequalcolin的实现会对cek进行查找，并且判断是否为正常加密后的数据类型。因此用户直接使用的时候会报错。
+
+    ```sql
+    mogdb=# SELECT * FROM byteawithoutorderwithequalcolsend('\x907219912381298461289346129'::byteawithoutorderwithequalcol);
+    ERROR:  cek with OID 596711794 not found
+    LINE 1: SELECT * FROM byteawithoutorderwithequalcolsend('\x907219912...
+                                                            ^
+    mogdb=# SELECT * FROM byteawithoutordercolout('\x90721901999999999999912381298461289346129');
+    ERROR:  cek with OID 2566986098 not found
+    LINE 1: SELECT * FROM byteawithoutordercolout('\x9072190199999999999...
+    SELECT * FROM byteawithoutorderwithequalcolrecv('\x90721901999999999999912381298461289346129'::byteawithoutorderwithequalcol);
+    ERROR:  cek with OID 2566986098 not found
+                                                ^
+    mogdb=# SELECT * FROM byteawithoutorderwithequalcolsend('\x90721901999999999999912381298461289346129'::byteawithoutorderwithequalcol);
+    ERROR:  cek with OID 2566986098 not found
+    LINE 1: SELECT * FROM byteawithoutorderwithequalcolsend('\x907219019...
+                                                            ^
+    ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/20.1-ledger-database-functions.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/20.1-ledger-database-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..c4742d9200b50751f90c9f64290d193dd99563b8
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/20.1-ledger-database-functions.md
@@ -0,0 +1,96 @@
+---
+title: 账本数据库的函数
+summary: 账本数据库的函数
+author: Guo Huan
+date: 2021-10-28
+---
+
+# 账本数据库的函数
+
+- get_dn_hist_relhash(text, text)
+
+  描述：返回指定防篡改用户表的表级数据hash值。该函数仅供分布式使用。
+
+  参数类型：text
+
+  返回值类型：hash16
+
+- ledger_hist_check(text, text)
+
+  描述：校验指定防篡改用户表的表级数据hash值与其对应历史表hash一致性。
+
+  参数类型：text
+
+  返回值类型：Boolean
+
+- ledger_hist_repair(text, text)
+
+  描述：修复指定防篡改用户表对应的历史表hash值，使之与用户表hash一致，返回hash差值。
+
+  参数类型：text
+
+  返回值类型：hash16
+
+- ledger_hist_archive(text, text)
+
+  描述：归档指定防篡改用户表对应的历史表至审计日志目录中hist_back文件夹下。
+
+  参数类型：text
+
+  返回值类型：Boolean
+
+- ledger_gchain_check(text, text)
+
+  描述：校验指定防篡改用户表对应的历史表hash与全局历史表对应的relhash一致性。
+
+  参数类型：text
+
+  返回值类型：Boolean
+
+- ledger_gchain_repair(text, text)
+
+  描述：修复验指定防篡改用户表在全局历史表中的relhash，使之与其历史表hash一致，返回hash差值。
+
+  参数类型：text
+
+  返回值类型：hash16
+
+- ledger_gchain_archive(void)
+
+  描述：归档全局历史表至审计日志目录中hist_back文件夹下。
+
+  参数类型：void
+
+  返回值类型：Boolean
+
+- hash16in(cstring)
+
+  描述：将输入16进制字符串转化成内部hash16形式。
+
+  参数类型：cstring
+
+  返回值类型：hash16
+
+- hash16out(hash16)
+
+  描述：将内部hash16类型的数据转码转化为16进制cstring类型。
+
+  参数类型：hash16
+
+  返回值类型：cstring
+
+- hash32in(cstring)
+
+  描述：将输入16进制字符串（32个字符）转化成内部类型hash32形式。
+
+  参数类型：cstring
+
+  返回值类型：hash32
+
+- hash32out(hash32)
+
+  描述：将内部hash32类型的数据转码转化为16进制cstring类型。
+
+  参数类型：cstring
+
+  返回值类型：hash32
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/21-set-returning-functions.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/21-set-returning-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..6baeb4004f9847080e62f778b8c87e1f6aa96d8a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/21-set-returning-functions.md
@@ -0,0 +1,131 @@
+---
+title: 返回集合的函数
+summary: 返回集合的函数
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 返回集合的函数
+
+## 序列号生成函数
+
+- generate_series(start, stop)
+
+  描述: 生成一个数值序列，从start到stop，步长为1。
+
+  参数类型: int、bigint、numeric
+
+  返回值类型: setof int、setof bigint、setof numeric（与参数类型相同）
+
+- generate_series(start, stop, step)
+
+  描述: 生成一个数值序列，从start到stop，步长为step。
+
+  参数类型: int、bigint、numeric
+
+  返回值类型: setof int、setof bigint、setof numeric（与参数类型相同）
+
+- generate_series(start, stop, step interval)
+
+  描述: 生成一个数值序列，从start到stop，步长为step。
+
+  参数类型: timestamp或timestamp with time zone
+
+  返回值类型: setof timestamp或setof timestamp with time zone（与参数类型相同）
+
+如果step是正数且start大于stop，则返回零行。相反，如果step是负数且start小于stop，则也返回零行。如果输入是NULL，同样产生零行。如果step为零则是一个错误。
+
+示例:
+
+```sql
+mogdb=# SELECT * FROM generate_series(2,4);
+ generate_series
+-----------------
+               2
+               3
+               4
+(3 rows)
+
+mogdb=# SELECT * FROM generate_series(5,1,-2);
+ generate_series
+-----------------
+               5
+               3
+               1
+(3 rows)
+
+mogdb=# SELECT * FROM generate_series(4,3);
+ generate_series
+-----------------
+(0 rows)
+
+--这个示例应用于date-plus-integer操作符。
+mogdb=# SELECT current_date + s.a AS dates FROM generate_series(0,14,7) AS s(a);
+   dates
+------------
+ 2017-06-02
+ 2017-06-09
+ 2017-06-16
+(3 rows)
+
+mogdb=# SELECT * FROM generate_series('2008-03-01 00:00'::timestamp, '2008-03-04 12:00', '10 hours');
+   generate_series
+---------------------
+ 2008-03-01 00:00:00
+ 2008-03-01 10:00:00
+ 2008-03-01 20:00:00
+ 2008-03-02 06:00:00
+ 2008-03-02 16:00:00
+ 2008-03-03 02:00:00
+ 2008-03-03 12:00:00
+ 2008-03-03 22:00:00
+ 2008-03-04 08:00:00
+(9 rows)
+```
+
+## 下标生成函数
+
+- generate_subscripts(array anyarray, dim int)
+
+  描述: 生成一系列包括给定数组的下标。
+
+  返回值类型: setof int
+
+- generate_subscripts(array anyarray, dim int, reverse boolean)
+
+  描述: 生成一系列包括给定数组的下标。当reverse为真时，该系列则以相反的顺序返回。
+
+  返回值类型: setof int
+
+generate_subscripts是一个为给定数组中的指定维度生成有效下标集的函数。如果数组中没有所请求的维度或者NULL数组，返回零行（但是会给数组元素为空的返回有效下标）。示例:
+
+```sql
+--基本用法。
+mogdb=# SELECT generate_subscripts('{NULL,1,NULL,2}'::int[], 1) AS s;
+ s
+---
+ 1
+ 2
+ 3
+ 4
+(4 rows)
+--unnest一个2D数组。
+mogdb=# CREATE OR REPLACE FUNCTION unnest2(anyarray)
+RETURNS SETOF anyelement AS $$
+SELECT $1[i][j]
+   FROM generate_subscripts($1,1) g1(i),
+        generate_subscripts($1,2) g2(j);
+$$ LANGUAGE sql IMMUTABLE;
+
+mogdb=# SELECT * FROM unnest2(ARRAY[[1,2],[3,4]]);
+ unnest2
+---------
+       1
+       2
+       3
+       4
+(4 rows)
+
+--删除函数。
+mogdb=# DROP FUNCTION unnest2;
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/22-conditional-expressions-functions.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/22-conditional-expressions-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..059a9df78b6c0ed85c280b846f3281ad71f5b6a0
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/22-conditional-expressions-functions.md
@@ -0,0 +1,175 @@
+---
+title: 条件表达式函数
+summary: 条件表达式函数
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 条件表达式函数
+
+- coalesce(expr1, expr2, …, exprn)
+
+  描述：
+
+  返回参数列表中第一个非NULL的参数值。
+
+  COALESCE(expr1, expr2) 等价于CASE WHEN expr1 IS NOT NULL THEN expr1 ELSE expr2 END。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT coalesce(NULL,'hello');
+   coalesce
+  ----------
+   hello
+  (1 row)
+  ```
+
+  备注：
+
+  - 如果表达式列表中的所有表达式都等于NULL，则本函数返回NULL。
+  - 它常用于在显示数据时用缺省值替换NULL。
+  - 和CASE表达式一样，COALESCE不会计算不需要用来判断结果的参数；即在第一个非空参数右边的参数不会被计算。
+
+- decode(base_expr, compare1, value1, Compare2,value2, … default)
+
+  描述：把base_expr与后面的每个compare(n) 进行比较，如果匹配返回相应的value(n)。如果没有发生匹配，则返回default。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT decode('A','A',1,'B',2,0);
+   case
+  ------
+   1
+  (1 row)
+  ```
+
+- nullif(expr1, expr2)
+
+  描述：当且仅当expr1和expr2相等时，NULLIF才返回NULL，否则它返回expr1。
+
+  nullif(expr1, expr2) 逻辑上等价于CASE WHEN expr1 = expr2 THEN NULL ELSE expr1 END。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT nullif('hello','world');
+   nullif
+  --------
+   hello
+  (1 row)
+  ```
+
+  备注：
+
+  如果两个参数的数据类型不同，则：
+
+  - 若两种数据类型之间存在隐式转换，则以其中优先级较高的数据类型为基准将另一个参数隐式转换成该类型，转换成功则进行计算，转换失败则返回错误。如：
+
+    ```sql
+    mogdb=# SELECT nullif('1234'::VARCHAR,123::INT4);
+    nullif
+    --------
+    1234
+    (1 row)
+    ```
+
+    ```sql
+    mogdb=# SELECT nullif('1234'::VARCHAR,'2012-12-24'::DATE);
+    ERROR:  invalid input syntax for type timestamp: "1234"
+    ```
+
+  - 若两种数据类型之间不存在隐式转换，则返回错误 。如：
+
+    ```sql
+    mogdb=# SELECT nullif(TRUE::BOOLEAN,'2012-12-24'::DATE);
+    ERROR:  operator does not exist: boolean = timestamp without time zone
+    LINE 1: SELECT nullif(TRUE::BOOLEAN,'2012-12-24'::DATE) FROM sys_dummy;
+    ^
+    HINT:  No operator matches the given name and argument type(s). You might need to add explicit type casts.
+    ```
+
+- nvl( expr1 , expr2 )
+
+  描述：
+
+  - 如果expr1为NULL则返回expr2。
+  - 如果expr1非NULL，则返回expr1。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT nvl('hello','world');
+    nvl
+  -------
+   hello
+  (1 row)
+  ```
+
+  备注：参数expr1和expr2可以为任意类型，当NVL的两个参数不属于同类型时，看第二个参数是否可以向第一个参数进行隐式转换。如果可以则返回第一个参数类型，否则返回错误。
+
+- greatest(expr1 [, …])
+
+  描述：获取并返回参数列表中值最大的表达式的值。
+
+  返回值类型：
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT greatest(1*2,2-3,4-1);
+   greatest
+  ----------
+          3
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT greatest('HARRY', 'HARRIOT', 'HAROLD');
+   greatest
+  ----------
+   HARRY
+  (1 row)
+  ```
+
+- least(expr1 [, …])
+
+  描述：获取并返回参数列表中值最小的表达式的值。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT least(1*2,2-3,4-1);
+   least
+  -------
+      -1
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT least('HARRY','HARRIOT','HAROLD');
+   least
+  --------
+   HAROLD
+  (1 row)
+  ```
+
+- EMPTY_BLOB()
+
+  描述：使用EMPTY_BLOB在INSERT或UPDATE语句中初始化一个BLOB变量，取值为NULL。
+
+  返回值类型：BLOB
+
+  示例：
+
+  ```sql
+  --新建表
+  mogdb=# CREATE TABLE blob_tb(b blob,id int);
+  --插入数据
+  mogdb=# INSERT INTO blob_tb VALUES (empty_blob(),1);
+  --删除表
+  mogdb=# DROP TABLE blob_tb;
+  ```
+
+  备注：使用DBE_LOB.GET_LENGTH求得的长度为0。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/23-system-information-functions.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/23-system-information-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..5b988a927c308452750bfa96a44e848d8628b9f6
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/23-system-information-functions.md
@@ -0,0 +1,1752 @@
+---
+title: 系统信息函数
+summary: 系统信息函数
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 系统信息函数
+
+## 会话信息函数
+
+- current_catalog
+
+  描述：当前数据库的名称（在标准SQL中称“catalog”）。
+
+  返回值类型：name
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT current_catalog;
+   current_database
+  ------------------
+   mogdb
+  (1 row)
+  ```
+
+- current_database()
+
+  描述：当前数据库的名称。
+
+  返回值类型：name
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT current_database();
+   current_database
+  ------------------
+   mogdb
+  (1 row)
+  ```
+
+- current_query()
+
+  描述：由客户端提交的当前执行语句（可能包含多个声明）。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT current_query();
+        current_query
+  -------------------------
+   SELECT current_query();
+  (1 row)
+  ```
+
+- current_schema[()]
+
+  描述：当前模式的名称。
+
+  返回值类型：name
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT current_schema();
+   current_schema
+  ----------------
+   public
+  (1 row)
+  ```
+
+  备注：current_schema返回在搜索路径中第一个顺位有效的模式名。（如果搜索路径为空则返回NULL，没有有效的模式名也返回NULL）。如果创建表或者其他命名对象时没有声明目标模式，则将使用这些对象的模式。
+
+- current_schemas(Boolean)
+
+  描述：搜索路径中的模式名称。
+
+  返回值类型：name[]
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT current_schemas(true);
+     current_schemas
+  ---------------------
+   {pg_catalog,public}
+  (1 row)
+  ```
+
+  备注：
+
+  current_schemas(Boolean)返回搜索路径中所有模式名称的数组。布尔选项决定像pg_catalog这样隐含包含的系统模式是否包含在返回的搜索路径中。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 搜索路径可以通过运行时设置更改。命令是：
+  >
+  > ```sql
+  > SET search_path TO schema [, schema, ...]
+  > ```
+
+- current_user
+
+  描述：当前执行环境下的用户名。
+
+  返回值类型：name
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT current_user;
+   current_user
+  --------------
+   omm
+  (1 row)
+  ```
+
+  备注：current_user是用于权限检查的用户标识。通常，他表示会话用户，但是可以通过[SET ROLE](129-SET-ROLE)改变他。在函数执行的过程中随着属性SECURITY DEFINER的改变，其值也会改变。
+
+- definer_current_user
+
+  描述：当前执行环境下的用户名。
+
+  返回值类型：name
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT definer_current_user();
+   definer_current_user
+  ----------------------
+   omm
+  (1 row)
+  ```
+
+- pg_current_sessionid()
+
+  描述：当前执行环境下的会话ID。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT pg_current_sessionid();
+      pg_current_sessionid
+  ----------------------------
+   1579228402.140190434944768
+  (1 row)
+  ```
+
+  备注：pg_current_sessionid()是用于获取当前执行环境下的会话ID。其组成结构为：时间戳.会话ID，当线程池模式开启（enable_thread_pool=on）时，会话ID为SessionID；而线程池模式关闭时，会话ID为ThreadID。
+
+- pg_current_sessid
+
+  描述：当前执行环境下的会话ID。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# select pg_current_sessid();
+  pg_current_sessid
+  -------------------
+  140308875015936
+  (1 row)
+  ```
+
+  备注：在线程池模式下获得当前会话的会话ID，非线程池模式下获得当前会话对应的后台线程ID。
+
+- pg_current_userid
+
+  描述：当前用户ID。
+
+  返回值类型：text
+
+  ```sql
+  mogdb=# SELECT pg_current_userid();
+  pg_current_userid
+  -------------------
+  10
+  (1 row)
+  ```
+
+- working_version_num()
+
+  描述：版本序号信息。返回一个系统兼容性有关的版本序号。
+
+  返回值类型：int
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT working_version_num();
+   working_version_num
+  ---------------------
+                 92231
+  (1 row)
+
+  ```
+
+- tablespace_oid_name()
+
+  描述: 根据表空间oid，查找表空间名称。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# select tablespace_oid_name(1663);
+   tablespace_oid_name
+  ---------------------
+   pg_default
+  (1 row)
+  ```
+
+- inet_client_addr()
+
+  描述：连接的远端地址。inet_client_addr返回当前客户端的IP地址。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 此函数只有在远程连接模式下有效。
+
+  返回值类型：inet
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT inet_client_addr();
+   inet_client_addr
+  ------------------
+   10.10.0.50
+  (1 row)
+  ```
+
+- inet_client_port()
+
+  描述：连接的远端端口。inet_client_port返回当前客户端的端口号。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 此函数只有在远程连接模式下有效。
+
+  返回值类型：int
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT inet_client_port();
+   inet_client_port
+  ------------------
+              33143
+  (1 row)
+  ```
+
+- inet_server_addr()
+
+  描述：连接的本地地址。inet_server_addr返回服务器接收当前连接用的IP地址。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 此函数只有在远程连接模式下有效。
+
+  返回值类型：inet
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT inet_server_addr();
+   inet_server_addr
+  ------------------
+   10.10.0.13
+  (1 row)
+  ```
+
+- inet_server_port()
+
+  描述：连接的本地端口。inet_server_port返回接收当前连接的端口号。如果是通过Unix-domain socket连接的，则所有这些函数都返回NULL。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 此函数只有在远程连接模式下有效。
+
+  返回值类型：int
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT inet_server_port();
+   inet_server_port
+  ------------------
+               8000
+  (1 row)
+  ```
+
+- pg_backend_pid()
+
+  描述：当前会话连接的服务进程的进程ID。
+
+  返回值类型：int
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT pg_backend_pid();
+   pg_backend_pid
+  -----------------
+   140229352617744
+  (1 row)
+  ```
+
+- pg_conf_load_time()
+
+  描述：配置加载时间。pg_conf_load_time返回最后加载服务器配置文件的时间戳。
+
+  返回值类型：timestamp with time zone
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT pg_conf_load_time();
+        pg_conf_load_time
+  ------------------------------
+   2017-09-01 16:05:23.89868+08
+  (1 row)
+  ```
+
+- pg_my_temp_schema()
+
+  描述：会话的临时模式的OID，不存在则为0。
+
+  返回值类型：oid
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT pg_my_temp_schema();
+   pg_my_temp_schema
+  -------------------
+                   0
+  (1 row)
+  ```
+
+  备注：pg_my_temp_schema返回当前会话中临时模式的OID，如果不存在（没有创建临时表）的话则返回0。如果给定的OID是其它会话中临时模式的OID，pg_is_other_temp_schema则返回true。
+
+- pg_is_other_temp_schema(oid)
+
+  描述：是否为另一个会话的临时模式。
+
+  返回值类型：Boolean
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT pg_is_other_temp_schema(25356);
+   pg_is_other_temp_schema
+  -------------------------
+   f
+  (1 row)
+  ```
+
+- pg_listening_channels()
+
+  描述：会话正在侦听的信道名称。
+
+  返回值类型：setof text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT pg_listening_channels();
+   pg_listening_channels
+  -----------------------
+  (0 rows)
+  ```
+
+  备注：pg_listening_channels返回当前会话正在侦听的一组信道名称。
+
+- pg_postmaster_start_time()
+
+  描述：服务器启动时间。pg_postmaster_start_time返回服务器启动时的timestamp with time zone。
+
+  返回值类型：timestamp with time zone
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT pg_postmaster_start_time();
+     pg_postmaster_start_time
+  ------------------------------
+   2017-08-30 16:02:54.99854+08
+  (1 row)
+  ```
+
+- pg_get_ruledef(rule_oid)
+
+  描述：获取规则的CREATE RULE命令。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# select * from pg_get_ruledef(24828);
+                                  pg_get_ruledef
+  -------------------------------------------------------------------
+   CREATE RULE t1_ins AS ON INSERT TO t1 DO INSTEAD INSERT INTO t2 (id) VALUES (new.id);
+  (1 row)
+  ```
+
+- sessionid2pid()
+
+  描述: 从sessionid中得到pid信息（例如，gs_session_stat中sessid列）。
+
+  返回值类型: int8
+
+  示例：
+
+  ```sql
+  mogdb=# select sessionid2pid(sessid::cstring) from gs_session_stat limit 2;
+    sessionid2pid
+  -----------------
+   139973107902208
+   139973107902208
+  (2 rows)
+  ```
+
+- pg_trigger_depth()
+
+  描述：触发器的嵌套层次。
+
+  返回值类型：int
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT pg_trigger_depth();
+   pg_trigger_depth
+  ------------------
+                  0
+  (1 row)
+  ```
+
+- session_user
+
+  描述：会话用户名。
+
+  返回值类型：name
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT session_user;
+   session_user
+  --------------
+   omm
+  (1 row)
+  ```
+
+  备注：session_user通常是连接当前数据库的初始用户，不过系统管理员可以用[SET SESSION AUTHORIZATION](130-SET-SESSION-AUTHORIZATION)修改这个设置。
+
+- user
+
+  描述：等价于current_user。
+
+  返回值类型：name
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT user;
+   current_user
+  --------------
+   omm
+  (1 row)
+  ```
+
+- getpgusername()
+
+  描述：获取数据库用户名。
+
+  返回值类型：name
+
+  示例：
+
+  ```sql
+  mogdb=# select getpgusername();
+   getpgusername
+  ---------------
+   GaussDB_userna
+  (1 row)
+  ```
+
+- getdatabaseencoding()
+
+  描述：获取数据库编码方式。
+
+  返回值类型：name
+
+  示例：
+
+  ```sql
+  mogdb=# select getdatabaseencoding();
+   getdatabaseencoding
+  ---------------------
+   SQL_ASCII
+  (1 row)
+  ```
+
+- version()
+
+  描述：版本信息。version返回一个描述服务器版本信息的字符串。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# select version();
+  version
+  -------------------------------------------------------------------------------------------------------------------------------------------------------------
+  (mogdb 2.1.1 build 24abfc73) compiled at 2021-04-16 19:39:59 commit 0 last mr 305 debug on x86_64-unknown-linux-gnu, compiled by g++ (GCC) 7.3.0, 64-bit
+  (1 row)
+  ```
+
+- opengauss_version()
+
+  描述：mogdb版本信息。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# select opengauss_version();
+   opengauss_version
+  -------------------
+   2.1.0
+  (1 row)
+  ```
+
+- gs_deployment()
+
+  描述：当前系统的部署形态信息。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# select gs_deployment();
+       gs_deployment
+  -----------------------
+   OpenSourceCentralized
+  (1 row)
+  ```
+
+- get_hostname()
+
+  描述：返回当前节点的hostname。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT get_hostname();
+   get_hostname
+  --------------
+   linux-user
+  (1 row)
+  ```
+
+- get_nodename()
+
+  描述：返回当前节点的名字。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT get_nodename();
+   get_nodename
+  --------------
+   datanode1
+  (1 row)
+  ```
+
+- get_schema_oid(cstring)
+
+  描述：返回查询schema的oid。
+
+  返回值类型：oid
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT get_schema_oid('public');
+   get_schema_oid
+  ----------------
+             2200
+  (1 row)
+  ```
+
+## 访问权限查询函数
+
+DDL类权限ALTER、DROP、COMMENT、INDEX、VACUUM属于所有者固有的权限，隐式拥有。
+
+- has_any_column_privilege(user, table, privilege)
+
+  描述：指定用户是否有访问表任何列的权限。
+
+  **表 1** 参数类型说明
+
+  | 参数名    | 合法入参类型 |
+  | :-------- | :----------- |
+  | user      | name, oid    |
+  | table     | text, oid    |
+  | privilege | text         |
+
+  返回类型：Boolean
+
+- has_any_column_privilege(table, privilege)
+
+  描述：当前用户是否有访问表任何列的权限，合法参数类型见表1。
+
+  返回类型：Boolean
+
+  备注：has_any_column_privilege检查用户是否以特定方式访问表的任何列。其参数可能与has_table_privilege类似，除了访问权限类型必须是SELECT、INSERT、UPDATE、COMMENT或REFERENCES的一些组合。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 拥有表的表级别权限则隐含的拥有该表每列的列级权限，因此如果与has_table_privilege参数相同，has_any_column_privilege总是返回true。但是如果授予至少一列的列级权限也返回成功。
+
+- has_column_privilege(user, table, column, privilege)
+
+  描述：指定用户是否有访问列的权限。
+
+  **表 2** 参数类型说明
+
+  | 参数名    | 合法入参类型   |
+  | :-------- | :------------- |
+  | user      | name, oid      |
+  | table     | text, oid      |
+  | column    | text, smallint |
+  | privilege | text           |
+
+  返回类型：Boolean
+
+- has_column_privilege(table, column, privilege)
+
+  描述：当前用户是否有访问列的权限，合法参数类型见表2。
+
+  返回类型：Boolean
+
+  备注：has_column_privilege检查用户是否以特定方式访问一列。其参数类似于has_table_privilege，可以通过列名或属性号添加列。想要的访问权限类型必须是SELECT、INSERT、UPDATE、COMMENT或REFERENCES的一些组合。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 拥有表的表级别权限则隐含的拥有该表每列的列级权限。
+
+- has_cek_privilege(user, cek, privilege)
+
+  描述：指定用户是否有访问列加密密钥CEK的权限。参数说明如下。
+
+  **表 3** 参数类型说明
+
+  | 参数名    | 合法入参类型 | 描述       | 取值范围                                                     |
+  | :-------- | :----------- | :--------- | :----------------------------------------------------------- |
+  | user      | name，oid    | 用户       | 用户名字或id。                                               |
+  | cek       | text，oid    | 列加密密钥 | 列加密密钥名称或id。                                         |
+  | privilege | text         | 权限       | USAGE：允许使用指定列加密密钥。DROP：允许删除指定列加密密钥。 |
+
+  返回类型：Boolean
+
+- has_cmk_privilege(user, cmk, privilege)
+
+  描述：指定用户是否有访问客户端加密主密钥CMK的权限。参数说明如下。
+
+  **表 4** 参数类型说明
+
+  | 参数名    | 合法入参类型 | 描述             | 取值范围                                                     |
+  | :-------- | :----------- | :--------------- | :----------------------------------------------------------- |
+  | user      | name，oid    | 用户             | 用户名字或id。                                               |
+  | cmk       | text，oid    | 客户端加密主密钥 | 客户端加密主密钥名称或id。                                   |
+  | privilege | text         | 权限             | USAGE：允许使用指定客户端加密主密钥。DROP：允许删除指定客户端加密主密钥。 |
+
+  返回类型：Boolean
+
+- has_database_privilege(user, database, privilege)
+
+  描述：指定用户是否有访问数据库的权限。参数说明如下。
+
+  **表 5** 参数类型说明
+
+  | 参数名    | 合法入参类型 |
+  | :-------- | :----------- |
+  | user      | name, oid    |
+  | database  | text, oid    |
+  | privilege | text         |
+
+  返回类型：Boolean
+
+- has_database_privilege(database, privilege)
+
+  描述：当前用户是否有访问数据库的权限，合法参数类型请参见表5。
+
+  返回类型：Boolean
+
+  备注：has_database_privilege检查用户是否能以在特定方式访问数据库。其参数类似has_table_privilege。访问权限类型必须是CREATE、CONNECT、TEMPORARY、ALTER、DROP、COMMENT或TEMP（等价于TEMPORARY）的一些组合。
+
+- has_directory_privilege(user, database, privilege)
+
+  描述：指定用户是否有访问directory的权限。
+
+  **表 6** 参数类型说明
+
+  | 参数名    | 合法入参类型 |
+  | :-------- | :----------- |
+  | user      | name, oid    |
+  | database  | text, oid    |
+  | privilege | text         |
+
+  返回类型：Boolean
+
+- has_directory_privilege(database, privilege)
+
+  描述：当前用户是否有访问directory的权限，合法参数类型请参见表6。
+
+  返回类型：Boolean
+
+- has_foreign_data_wrapper_privilege(user, fdw, privilege)
+
+  描述：指定用户是否有访问外部数据封装器的权限。
+
+  **表 7** 参数类型说明
+
+  | 参数名    | 合法入参类型 |
+  | :-------- | :----------- |
+  | user      | name, oid    |
+  | fdw       | text, oid    |
+  | privilege | text         |
+
+  返回类型：Boolean
+
+- has_foreign_data_wrapper_privilege(fdw, privilege)
+
+  描述：当前用户是否有访问外部数据封装器的权限。合法参数类型请参见表7。
+
+  返回类型：Boolean
+
+  备注：has_foreign_data_wrapper_privilege检查用户是否能以特定方式访问外部数据封装器。其参数类似has_table_privilege。访问权限类型必须是USAGE。
+
+- has_function_privilege(user, function, privilege)
+
+  描述：指定用户是否有访问函数的权限。
+
+  **表 8** 参数类型说明
+
+  | 参数名    | 合法入参类型 |
+  | :-------- | :----------- |
+  | user      | name, oid    |
+  | function  | text, oid    |
+  | privilege | text         |
+
+  返回类型：Boolean
+
+- has_function_privilege(function, privilege)
+
+  描述：当前用户是否有访问函数的权限。合法参数类型请参见表8。
+
+  返回类型：Boolean
+
+  备注：has_function_privilege检查一个用户是否能以指定方式访问一个函数。其参数类似has_table_privilege。使用文本字符而不是OID声明一个函数时，允许输入的类型和regprocedure数据类型一样（请参考[对象标识符类型](14-object-identifier-types)）。访问权限类型必须是EXECUTE、ALTER、DROP或COMMENT。
+
+- has_language_privilege(user, language, privilege)
+
+  描述：指定用户是否有访问语言的权限。
+
+  **表 9** 参数类型说明
+
+  | 参数名    | 合法入参类型 |
+  | :-------- | :----------- |
+  | user      | name, oid    |
+  | language  | text, oid    |
+  | privilege | text         |
+
+  返回类型：Boolean
+
+- has_language_privilege(language, privilege)
+
+  描述：当前用户是否有访问语言的权限。合法参数类型请参见表9。
+
+  返回类型：Boolean
+
+  备注：has_language_privilege检查用户是否能以特定方式访问一个过程语言。其参数类似has_table_privilege。访问权限类型必须是USAGE。
+
+- has_nodegroup_privilege(user, nodegroup, privilege)
+
+  描述：检查用户是否有数据库节点访问权限。
+
+  返回类型：Boolean
+
+  **表 10** 参数类型说明
+
+  | 参数名    | 合法入参类型 |
+  | :-------- | :----------- |
+  | user      | name, oid    |
+  | nodegroup | text, oid    |
+  | privilege | text         |
+
+- has_nodegroup_privilege(nodegroup, privilege)
+
+  描述：检查用户是否有数据库节点访问权限。参数与has_table_privilege类似。访问权限类型必须是USAGE、CREATE、COMPUTE、ALTER或CROP。
+
+  返回类型：Boolean
+
+- has_schema_privilege(user, schema, privilege)
+
+  描述：指定用户是否有访问模式的权限。
+
+  返回类型：Boolean
+
+- has_schema_privilege(schema, privilege)
+
+  描述：当前用户是否有访问模式的权限。
+
+  返回类型：Boolean
+
+  备注：has_schema_privilege检查用户是否能以特定方式访问一个模式。其参数类似has_table_privilege。访问权限类型必须是CREATE、USAGE、ALTER、DROP或COMMENT的一些组合。
+
+- has_server_privilege(user, server, privilege)
+
+  描述：指定用户是否有访问外部服务的权限。
+
+  返回类型：Boolean
+
+- has_server_privilege(server, privilege)
+
+  描述：当前用户是否有访问外部服务的权限。
+
+  返回类型：Boolean
+
+  备注：has_server_privilege检查用户是否能以指定方式访问一个外部服务器。其参数类似has_table_privilege。访问权限类型必须是USAGE、ALTER、DROP或COMMENT之一的值。
+
+- has_table_privilege(user, table, privilege)
+
+  描述：指定用户是否有访问表的权限。
+
+  返回类型：Boolean
+
+- has_table_privilege(table, privilege)
+
+  描述：当前用户是否有访问表的权限。
+
+  返回类型：Boolean
+
+  备注：has_table_privilege检查用户是否以特定方式访问表。用户可以通过名称或OID（pg_authid.oid）来指定，public表明PUBLIC伪角色，或如果缺省该参数，则使用current_user。该表可以通过名称或者OID声明。如果用名称声明，则在必要时可以用模式进行修饰。如果使用文本字符串来声明所希望的权限类型，这个文本字符串必须是SELECT、INSERT、UPDATE、DELETE、TRUNCATE、REFERENCES、TRIGGER、ALTER、DROP、COMMENT、INDEX或VACUUM之一的值。可以给权限类型添加WITH GRANT OPTION，用来测试权限是否拥有授权选项。也可以用逗号分隔列出的多个权限类型，如果拥有任何所列出的权限，则结果便为true。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT has_table_privilege('tpcds.web_site', 'select');
+   has_table_privilege
+  ---------------------
+   t
+  (1 row)
+
+  mogdb=# SELECT has_table_privilege('omm', 'tpcds.web_site', 'select,INSERT WITH GRANT OPTION ');
+   has_table_privilege
+  ---------------------
+   t
+  (1 row)
+  ```
+
+- has_tablespace_privilege(user, tablespace, privilege)
+
+  描述：指定用户是否有访问表空间的权限。
+
+  返回类型：Boolean
+
+- has_tablespace_privilege(tablespace, privilege)
+
+  描述：当前用户是否有访问表空间的权限。
+
+  返回类型：Boolean
+
+  备注：has_tablespace_privilege检查用户是否能以特定方式访问一个表空间。其参数类似has_table_privilege。访问权限类型必须是CREATE、ALTER、DROP或COMMENT之一的值。
+
+- pg_has_role(user, role, privilege)
+
+  描述：指定用户是否有角色的权限。
+
+  返回类型：Boolean
+
+- pg_has_role(role, privilege)
+
+  描述：当前用户是否有角色的权限。
+
+  返回类型：Boolean
+
+  备注：pg_has_role检查用户是否能以特定方式访问一个角色。其参数类似has_table_privilege，除了public不能用做用户名。访问权限类型必须是MEMBER或USAGE的一些组合。 MEMBER表示的是角色中的直接或间接成员关系（也就是SET ROLE的权限），而USAGE表示无需通过SET ROLE也直接拥有角色的使用权限。
+
+## 模式可见性查询函数
+
+每个函数执行检查数据库对象类型的可见性。对于函数和操作符，如果在前面的搜索路径中没有相同的对象名称和参数的数据类型，则此对象是可见的。对于操作符类，则要同时考虑名称和相关索引的访问方法。
+
+所有这些函数都需要使用OID来标识要需要检查的对象。如果用户想通过名称测试对象，则使用OID别名类型（regclass、regtype、regprocedure、regoperator、regconfig或regdictionary）将会很方便。
+
+比如，如果一个表所在的模式在搜索路径中，并且在前面的搜索路径中没有同名的表，则这个表是可见的。它等效于表可以不带明确模式修饰进行引用。比如，要列出所有可见表的名称：
+
+```sql
+mogdb=# SELECT relname FROM pg_class WHERE pg_table_is_visible(oid);
+```
+
+- pg_collation_is_visible(collation_oid)
+
+  描述：该排序是否在搜索路径中可见。
+
+  返回类型：Boolean
+
+- pg_conversion_is_visible(conversion_oid)
+
+  描述：该转换是否在搜索路径中可见。
+
+  返回类型：Boolean
+
+- pg_function_is_visible(function_oid)
+
+  描述：该函数是否在搜索路径中可见。
+
+  返回类型：Boolean
+
+- pg_opclass_is_visible(opclass_oid)
+
+  描述：该操作符类是否在搜索路径中可见。
+
+  返回类型：Boolean
+
+- pg_operator_is_visible(operator_oid)
+
+  描述：该操作符是否在搜索路径中可见。
+
+  返回类型：Boolean
+
+- pg_opfamily_is_visible(opclass_oid)
+
+  描述：该操作符族是否在搜索路径中可见。
+
+  返回类型：Boolean
+
+- pg_table_is_visible(table_oid)
+
+  描述：该表是否在搜索路径中可见。
+
+  返回类型：Boolean
+
+- pg_ts_config_is_visible(config_oid)
+
+  描述：该文本检索配置是否在搜索路径中可见。
+
+  返回类型：Boolean
+
+- pg_ts_dict_is_visible(dict_oid)
+
+  描述：该文本检索词典是否在搜索路径中可见。
+
+  返回类型：Boolean
+
+- pg_ts_parser_is_visible(parser_oid)
+
+  描述：该文本搜索解析是否在搜索路径中可见。
+
+  返回类型：Boolean
+
+- pg_ts_template_is_visible(template_oid)
+
+  描述：该文本检索模板是否在搜索路径中可见。
+
+  返回类型：Boolean
+
+- pg_type_is_visible(type_oid)
+
+  描述：该类型（或域）是否在搜索路径中可见。
+
+  返回类型：Boolean
+
+## 系统表信息函数
+
+- format_type(type_oid, typemod)
+
+  描述：获取数据类型的SQL名称。
+
+  返回类型：text
+
+  备注：format_type通过某个数据类型的类型OID以及可能的类型修饰词，返回其SQL名称。如果不知道具体的修饰词，则在类型修饰词的位置传入NULL。类型修饰词一般只对有长度限制的数据类型有意义。format_type所返回的SQL名称中包含数据类型的长度值，其大小是：实际存储长度len - sizeof(int32)，单位字节。原因是数据存储时需要32位的空间来存储用户对数据类型的自定义长度信息，即实际存储长度要比用户定义长度多4个字节。在下例中，format_type返回的SQL名称为“character varying(6)”，6表示varchar类型的长度值是6字节，因此该类型的实际存储长度为10字节。
+
+  ```sql
+  mogdb=# SELECT format_type((SELECT oid FROM pg_type WHERE typname='varchar'), 10);
+       format_type
+  ----------------------
+   character varying(6)
+  (1 row)
+  ```
+
+- getdistributekey(table_name)
+
+  描述：获取一个hash表的分布列。单机环境下不支持分布，该函数返回为空。
+
+- pg_check_authid(role_oid)
+
+  描述：检查是否存在给定oid的角色名。
+
+  返回类型：bool
+
+  示例：
+
+  ```sql
+  mogdb=# select pg_check_authid(1);
+  pg_check_authid
+  -----------------
+  f
+  (1 row)
+  ```
+
+- pg_describe_object(catalog_id, object_id, object_sub_id)
+
+  描述：获取数据库对象的描述。
+
+  返回类型：text
+
+  备注：pg_describe_object返回由目录OID，对象OID和一个（或许0个）子对象ID指定的数据库对象的描述。这有助于确认存储在pg_depend系统表中对象的身份。
+
+- pg_get_constraintdef(constraint_oid)
+
+  描述：获取约束的定义。
+
+  返回类型：text
+
+- pg_get_constraintdef(constraint_oid, pretty_bool)
+
+  描述：获取约束的定义。
+
+  返回类型：text
+
+  备注：pg_get_constraintdef和pg_get_indexdef分别从约束或索引上使用创建命令进行重构。
+
+- pg_get_expr(pg_node_tree, relation_oid)
+
+  描述：反编译表达式的内部形式，假设其中的任何Vars都引用第二个参数指定的关系。
+
+  返回类型：text
+
+- pg_get_expr(pg_node_tree, relation_oid, pretty_bool)
+
+  描述：反编译表达式的内部形式，假设其中的任何Vars都引用第二个参数指定的关系。
+
+  返回类型：text
+
+  备注：pg_get_expr反编译一个独立表达式的内部形式，比如一个字段的缺省值。在检查系统表的内容的时候很有用。如果表达式可能包含关键字，则指定他们引用相关的OID作为第二个参数；如果没有关键字，零就足够了。
+
+- pg_get_functiondef(func_oid)
+
+  描述：获取函数的定义。
+
+  返回类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# select * from pg_get_functiondef(598);
+   headerlines |                     definition
+  -------------+----------------------------------------------------
+             4 | CREATE OR REPLACE FUNCTION pg_catalog.abbrev(inet)+
+               |  RETURNS text                                     +
+               |  LANGUAGE internal                                +
+               |  IMMUTABLE STRICT NOT FENCED NOT SHIPPABLE        +
+               | AS $function$inet_abbrev$function$                +
+               |
+  (1 row)
+  ```
+
+- pg_get_function_arguments(func_oid)
+
+  描述：获取函数定义的参数列表（带默认值）。
+
+  返回类型：text
+
+  备注：pg_get_function_arguments返回一个函数的参数列表，需要在CREATE FUNCTION中使用这种格式。
+
+- pg_get_function_identity_arguments(func_oid)
+
+  描述：获取参数列表来确定一个函数（不带默认值）。
+
+  返回类型：text
+
+  备注：pg_get_function_identity_arguments返回需要的参数列表用来标识函数，这种形式需要在ALTER FUNCTION中使用，并且这种形式省略了默认值。
+
+- pg_get_function_result(func_oid)
+
+  描述：获取函数的RETURNS子句。
+
+  返回类型：text
+
+  备注：pg_get_function_result为函数返回适当的RETURNS子句。
+
+- pg_get_indexdef(index_oid)
+
+  描述：获取索引的CREATE INDEX命令。
+
+  返回类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# select * from pg_get_indexdef(16416);
+                               pg_get_indexdef
+  -------------------------------------------------------------------------
+   CREATE INDEX test3_b_idx ON test3 USING btree (b) TABLESPACE pg_default
+  (1 row)
+  ```
+
+- pg_get_indexdef(index_oid, dump_schema_only)
+
+  描述：获取索引的CREATE INDEX命令，仅用于dump场景。对于包含local索引的间隔分区表，当dump_schema_only为true时，返回的创建索引语句中不包含自动创建的分区的local索引信息；当dump_schema_only为false时，返回的创建索引语句中包含自动创建的分区的local索引信息。对于非间隔分区表或者不包含local索引的间隔分区分区表，dump_schema_only参数取值不影响函数返回结果。
+
+  返回类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# CREATE TABLE sales
+  mogdb-# (prod_id NUMBER(6),
+  mogdb(#  cust_id NUMBER,
+  mogdb(#  time_id DATE,
+  mogdb(#  channel_id CHAR(1),
+  mogdb(#  promo_id NUMBER(6),
+  mogdb(#  quantity_sold NUMBER(3),
+  mogdb(#  amount_sold NUMBER(10,2)
+  mogdb(# )
+  PARTITION BY RANGE( time_id) INTERVAL('1 day')
+  mogdb-# mogdb-# (
+  mogdb(#  partition p1 VALUES LESS THAN ('2019-02-01 00:00:00'),
+  mogdb(#  partition p2 VALUES LESS THAN ('2019-02-02 00:00:00')
+  mogdb(# );
+  CREATE TABLE
+  mogdb=# create index index_sales on sales(prod_id) local (PARTITION idx_p1 ,PARTITION idx_p2);
+  CREATE INDEX
+  mogdb=# -- 插入数据没有匹配的分区，新创建一个分区，并将数据插入该分区
+  mogdb=# INSERT INTO sales VALUES(1, 12, '2019-02-05 00:00:00', 'a', 1, 1, 1);
+  INSERT 0 1
+  mogdb=# select oid from pg_class where relname = 'index_sales';
+    oid
+  -------
+   24632
+  (1 row)
+  mogdb=# select * from pg_get_indexdef(24632, true);
+                                                       pg_get_indexdef
+  --------------------------------------------------------------------------------------------------------------------------
+   CREATE INDEX index_sales ON sales USING btree (prod_id) LOCAL(PARTITION idx_p1, PARTITION idx_p2)  TABLESPACE pg_default
+  (1 row)
+  mogdb=# select * from pg_get_indexdef(24632, false);
+                                                                      pg_get_indexdef
+
+  ------------------------------------------------------------------------------------------------------------------------------------
+  --------------------
+   CREATE INDEX index_sales ON sales USING btree (prod_id) LOCAL(PARTITION idx_p1, PARTITION idx_p2, PARTITION sys_p1_prod_id_idx)  TA
+  BLESPACE pg_default
+  (1 row
+  ```
+
+- pg_get_indexdef(index_oid, column_no, pretty_bool)
+
+  描述：获取索引的CREATE INDEX命令，或者如果column_no不为零，则只获取一个索引字段的定义。
+
+  示例：
+
+  ```sql
+  mogdb=# select * from pg_get_indexdef(16416, 0, false);
+                               pg_get_indexdef
+  -------------------------------------------------------------------------
+   CREATE INDEX test3_b_idx ON test3 USING btree (b) TABLESPACE pg_default
+  (1 row)
+  mogdb=# select * from pg_get_indexdef(16416, 1, false);
+   pg_get_indexdef
+  -----------------
+   b
+  (1 row)
+  ```
+
+  返回类型：text
+
+  备注：pg_get_functiondef为函数返回一个完整的CREATE OR REPLACE FUNCTION语句。
+
+- pg_get_keywords()
+
+  描述：获取SQL关键字和类别列表。
+
+  返回类型：setof record
+
+  备注：pg_get_keywords返回一组关于描述服务器识别SQL关键字的记录。word列包含关键字。catcode列包含一个分类代码：U表示通用的，C表示列名，T表示类型或函数名，或R表示保留。catdesc列包含了一个可能本地化描述分类的字符串。
+
+- pg_get_userbyid(role_oid)
+
+  描述：获取给定OID的角色名。
+
+  返回类型：name
+
+  备注：pg_get_userbyid通过角色的OID抽取对应的用户名。
+
+- pg_check_authid(role_id)
+
+  描述：通过role_id检查用户是否存在。
+
+  返回类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# select pg_check_authid(20);
+  pg_check_authid
+  -----------------
+  f
+  (1 row)
+  ```
+
+- pg_get_viewdef(view_name)
+
+  描述：为视图获取底层的SELECT命令。
+
+  返回类型：text
+
+- pg_get_viewdef(view_name, pretty_bool)
+
+  描述：为视图获取底层的SELECT命令，如果pretty_bool为true，行字段可以包含80列。
+
+  返回类型：text
+
+  备注：pg_get_viewdef重构出定义视图的SELECT查询。这些函数大多数都有两种形式，其中带有pretty_bool参数，且参数为true时，是”适合打印”的结果，这种格式更容易读。另一种是缺省的格式，更有可能被将来的不同版本用同样的方法解释。如果是用于转储，那么尽可能避免使用适合打印的格式。给pretty-print参数传递false生成的结果和没有这个参数的变种生成的结果是完全一样。
+
+- pg_get_viewdef(view_oid)
+
+  描述：为视图获取底层的SELECT命令。
+
+  返回类型：text
+
+- pg_get_viewdef(view_oid, pretty_bool)
+
+  描述：为视图获取底层的SELECT命令，如果pretty_bool为true，行字段可以包含80列。
+
+  返回类型：text
+
+- pg_get_viewdef(view_oid, wrap_column_int)
+
+  描述：为视图获取底层的SELECT命令；行字段被换到指定的列数，打印是隐含的。
+
+  返回类型：text
+
+- pg_get_tabledef(table_oid)
+
+  描述：根据table_oid获取表定义
+
+  示例：
+
+  ```sql
+  mogdb=# select * from pg_get_tabledef(16384);
+                      pg_get_tabledef
+  -------------------------------------------------------
+   SET search_path = public;                            +
+   CREATE  TABLE t1 (                                   +
+           c1 bigint DEFAULT nextval('serial'::regclass)+
+   )                                                    +
+   WITH (orientation=row, compression=no)               +
+   TO GROUP group1;
+  (1 row)
+  ```
+
+  返回类型：text
+
+- pg_get_tabledef(table_name)
+
+  描述：根据table_name获取表定义。
+
+  示例：
+
+  ```sql
+  mogdb=# select * from pg_get_tabledef('t1');
+                      pg_get_tabledef
+  -------------------------------------------------------
+   SET search_path = public;                            +
+   CREATE  TABLE t1 (                                   +
+           c1 bigint DEFAULT nextval('serial'::regclass)+
+   )                                                    +
+   WITH (orientation=row, compression=no)               +
+   TO GROUP group1;
+  (1 row)
+  ```
+
+  返回类型：text
+
+  备注：pg_get_tabledef重构出表定义的CREATE语句，包含了表定义本身、索引信息、comments信息。对于表对象依赖的group、schema、tablespace、server等信息，需要用户自己去创建，表定义里不会有这些对象的创建语句。
+
+- pg_options_to_table(reloptions)
+
+  描述：获取存储选项名称/值对的集合。
+
+  返回类型：setof record
+
+  备注：pg_options_to_table当通过pg_class.reloptions或pg_attribute.attoptions时返回存储选项名称/值对（option_name/option_value）的集合。
+
+- pg_tablespace_databases(tablespace_oid)
+
+  描述：获取在指定的表空间中有对象的数据库OID集合。
+
+  返回类型：setof oid
+
+  备注：pg_tablespace_databases允许检查表空间的状况，返回在该表空间中保存了对象的数据库OID集合。如果这个函数返回数据行，则该表空间就是非空的，因此不能删除。要显示该表空间中的特定对象，用户需要连接pg_tablespace_databases标识的数据库与查询pg_class系统表。
+
+- pg_tablespace_location(tablespace_oid)
+
+  描述：获取表空间所在的文件系统的路径。
+
+  返回类型：text
+
+- pg_typeof(any)
+
+  描述：获取任何值的数据类型。
+
+  返回类型：regtype
+
+  备注：pg_typeof返回传递给他的值的数据类型OID。这可能有助于故障排除或动态构造SQL查询。声明此函数返回regtype，这是一个OID别名类型（请参考[对象标识符类型](14-object-identifier-types)）；这意味着它是一个为了比较而显示类型名称的OID。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT pg_typeof(33);
+   pg_typeof
+  -----------
+   integer
+  (1 row)
+
+  mogdb=# SELECT typlen FROM pg_type WHERE oid = pg_typeof(33);
+   typlen
+  --------
+        4
+  (1 row)
+  ```
+
+- collation for (any)
+
+  描述：获取参数的排序。
+
+  返回类型：text
+
+  备注：表达式collation for返回传递给他的值的排序。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT collation for (description) FROM pg_description LIMIT 1;
+   pg_collation_for
+  ------------------
+   "default"
+  (1 row)
+  ```
+
+  值可能是引号括起来的并且模式限制的。如果没有为参数表达式排序，则返回一个null值。如果参数不是排序的类型，则抛出一个错误。
+
+- pg_extension_update_paths(name)
+
+  描述：返回指定扩展的版本更新路径。
+
+  返回类型：text(source text), text(path text), text(target text)
+
+- pg_get_serial_sequence(tablename, colname)
+
+  描述：获取对应表名和列名上的序列。
+
+  返回类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# select * from pg_get_serial_sequence('t1', 'c1');
+   pg_get_serial_sequence
+  ------------------------
+   public.serial
+  (1 row)
+  ```
+
+- pg_sequence_parameters(sequence_oid)
+
+  描述：获取指定sequence的参数，包含起始值，最小值和最大值，递增值等。
+
+  返回类型：bigint, bigint, bigint, bigint, Boolean
+
+  示例：
+
+  ```sql
+  mogdb=# select * from pg_sequence_parameters(16420);
+   start_value | minimum_value |    maximum_value    | increment | cycle_option
+  -------------+---------------+---------------------+-----------+--------------
+           101 |             1 | 9223372036854775807 |         1 | f
+  (1 row)
+  ```
+
+## 注释信息函数
+
+- col_description(table_oid, column_number)
+
+  描述：获取一个表字段的注释
+
+  返回类型：text
+
+  备注：col_description返回一个表中字段的注释，通过表OID和字段号来声明。
+
+- obj_description(object_oid, catalog_name)
+
+  描述：获取一个数据库对象的注释
+
+  返回类型：text
+
+  备注：带有两个参数的obj_description返回一个数据库对象的注释，该对象是通过其OID和其所属的系统表名称声明。比如，obj_description(123456,'pg_class')将返回OID为123456的表的注释。只带一个参数的obj_description只要求对象OID。
+
+  obj_description不能用于表字段，因为字段没有自己的OID。
+
+- obj_description(object_oid)
+
+  描述：获取一个数据库对象的注释
+
+  返回类型：text
+
+- shobj_description(object_oid, catalog_name)
+
+  描述：获取一个共享数据库对象的注释
+
+  返回类型：text
+
+  备注：shobj_description和obj_description差不多，不同之处仅在于前者用于共享对象。一些系统表是通用于MogDB中所有数据库的全局表，因此这些表的注释也是全局存储的。
+
+## 事务ID和快照
+
+内部事务ID类型（xid）是64位。这些函数使用的数据类型txid_snapshot，存储在特定时刻事务ID可见性的信息。其组件描述在表11。
+
+**表 11** 快照组件
+
+| 名称     | 描述                                                         |
+| :------- | :----------------------------------------------------------- |
+| xmin     | 最早的事务ID（txid）仍然活动。所有较早事务将是已经提交可见的，或者是直接回滚。 |
+| xmax     | 作为尚未分配的txid。所有大于或等于此txids的都是尚未开始的快照时间，因此不可见。 |
+| xip_list | 当前快照中活动的txids。这个列表只包含在xmin和xmax之间活动的txids；有可能活动的txids高于xmax。介于大于等于xmin、小于xmax，并且不在这个列表中的txid，在这个时间快照已经完成的，因此按照提交状态查看他是可见还是回滚。这个列表不包含子事务的txids。 |
+
+txid_snapshot的文本表示为：xmin:xmax:xip_list。
+
+示例：10:20:10,14,15意思为：xmin=10, xmax=20, xip_list=10, 14, 15。
+
+以下的函数在一个输出形式中提供服务器事务信息。这些函数的主要用途是为了确定在两个快照之间有哪个事务提交。
+
+- txid_current()
+
+  描述：获取当前事务ID。
+
+  返回类型：bigint
+
+- txid_current_snapshot()
+
+  描述：获取当前快照。
+
+  返回类型：txid_snapshot
+
+- txid_snapshot_xip(txid_snapshot)
+
+  描述：在快照中获取正在进行的事务ID。
+
+  返回类型：setof bigint
+
+- txid_snapshot_xmax(txid_snapshot)
+
+  描述：获取快照的xmax。
+
+  返回类型：bigint
+
+- txid_snapshot_xmin(txid_snapshot)
+
+  描述：获取快照的xmin。
+
+  返回类型：bigint
+
+- txid_visible_in_snapshot(bigint, txid_snapshot)
+
+  描述：在快照中事务ID是否可见（不使用子事务ID）。
+
+  返回类型：Boolean
+
+- get_local_prepared_xact()
+
+  描述：获取当前节点两阶段残留事务信息，包括事务id，两阶段gid名称，prepared的时间，owner的oid，database的oid及当前节点的node_name。
+
+  返回类型：xid, text, timestamptz, oid, oid，text
+
+- get_remote_prepared_xacts()
+
+  描述：获取所有远程节点两阶段残留事务信息，包括事务id，两阶段gid名称，prepared的时间，owner的名称，database的名称及node_name。
+
+  返回类型：xid, text, timestamptz, name, name，text
+
+- global_clean_prepared_xacts(text, text)
+
+  描述：并发清理两阶段残留事务，仅gs_clean工具可以调用清理，其他用户调用均返回false。
+
+  返回类型：Boolean
+
+- slice(hstore, text[])
+
+  描述： 提取hstore的子集。
+
+  返回值： hstore
+
+  示例：
+
+  ```sql
+  mogdb=# select slice('a=>1,b=>2,c=>3'::hstore, ARRAY['b','c','x']);
+         slice
+  --------------------
+   "b"=>"2", "c"=>"3"
+  (1 row)
+  ```
+
+- slice_array(hstore, text[])
+
+  描述：提取hstore的值的集合。
+
+  返回值：值数组
+
+  示例：
+
+  ```sql
+  mogdb=# select slice_array('a=>1,b=>2,c=>3'::hstore, ARRAY['b','c','x']);
+   slice_array
+  -------------
+   {2,3,NULL}
+  (1 row)
+  ```
+
+- skeys(hstore)
+
+  描述：返回hstore的所有键构成的集合。
+
+  返回值：键的集合。
+
+  示例：
+
+  ```sql
+  mogdb=# select skeys('a=>1,b=>2');
+   skeys
+  -------
+   a
+   b
+  (2 rows)
+  ```
+
+- pg_control_system()
+
+  描述：返回系统控制文件状态。
+
+  返回类型：SETOF record
+
+- pg_control_checkpoint()
+
+  描述：返回系统检查点状态。
+
+  返回类型：SETOF record
+
+- pv_builtin_functions
+
+  描述：查看所有内置系统函数信息。
+
+  参数：nan
+
+  返回值类型：proname name, pronamespace oid, proowner oid, prolang oid, procost real, prorows real, provariadic oid, protransform regproc, proisagg boolean, proiswindow boolean, prosecdef boolean, proleakproof boolean, proisstrict boolean, proretset boolean, provolatile “char”, pronargs smallint, pronargdefaults smallint, prorettype oid, proargtypes oidvector, proallargtypes integer[], proargmodes “char”[], proargnames text[], proargdefaults pg_node_tree, prosrc text, probin text, proconfig text[], proacl aclitem[], prodefaultargpos int2vector, fencedmode boolean, proshippable boolean, propackage boolean, oid oid
+
+- pv_thread_memory_detail
+
+  描述：返回各线程的内存信息。
+
+  参数：nan
+
+  返回值类型：threadid text, tid bigint, thrdtype text, contextname text, level smallint, parent text, totalsize bigint, freesize bigint, usedsize bigint
+
+- pg_relation_compression_ratio
+
+  描述：查询表压缩率，默认返回1.0。
+
+  参数：text
+
+  返回值类型：real
+
+- pg_relation_with_compression
+
+  描述：查询表是否压缩。
+
+  参数：text
+
+  返回值类型：boolean
+
+- pg_stat_file_recursive
+
+  描述：列出路径下所有文件。
+
+  参数：location text
+
+- pg_shared_memory_detail
+
+  描述：返回所有已产生的共享内存上下文的使用信息，各列描述请参考GS_SHARED_MEMORY_DETAIL。
+
+  参数：nan
+
+  返回值类型：contextname text, level smallint, parent text, totalsize bigint, freesize bigint, usedsize bigint
+
+- get_gtm_lite_status
+
+  描述：返回GTM上的backupXid和csn号，用来支持问题定位，GTM-FREE模式下不支持使用本系统函数，集中式不支持该函数。
+
+- gs_stat_get_wlm_plan_operator_info
+
+  描述：从内部哈希表中获取算子计划信息。
+
+  参数：oid
+
+  返回值类型：datname text, queryid int8, plan_node_id int4, startup_time int8, total_time int8, actual_rows int8, max_peak_memory int4, query_dop int4, parent_node_id int4, left_child_id int4, right_child_id int4, operation text, orientation text, strategy text, options text, condition text, projection text
+
+- pg_stat_get_partition_tuples_hot_updated
+
+  描述：返回给定分区id的分区热更新元组数的统计。
+
+  参数：oid
+
+  返回值类型：bigint
+
+- gs_session_memory_detail_tp
+
+  描述：返回会话的内存使用情况，参考gs_session_memory_detail。
+
+  参数：nan
+
+  返回值类型：sessid text, sesstype text, contextname text, level smallint, parent text, totalsize bigint, freesize bigint, usedsize bigint
+
+- gs_thread_memory_detail
+
+  描述：返回各线程的内存信息。
+
+  参数：nan
+
+  返回值类型：threadid text, tid bigint, thrdtype text, contextname text, level smallint, parent text, totalsize bigint, freesize bigint, usedsize bigint
+
+- pg_stat_get_wlm_realtime_operator_info
+
+  描述：从内部哈希表中获取实时执行计划算子信息。
+
+  参数：nan
+
+  返回值类型：queryid bigint, pid bigint, plan_node_id integer, plan_node_name text, start_time timestamp with time zone, duration bigint, status text, query_dop integer, estimated_rows bigint, tuple_processed bigint, min_peak_memory integer, max_peak_memory integer, average_peak_memory integer, memory_skew_percent integer, min_spill_size integer, max_spill_size integer, average_spill_size integer, spill_skew_percent integer, min_cpu_time bigint, max_cpu_time bigint, total_cpu_time bigint, cpu_skew_percent integer, warning text
+
+- pg_stat_get_wlm_realtime_ec_operator_info
+
+  描述：从内部哈希表中获取EC执行计划算子信息。
+
+  参数：nan
+
+  返回值类型：queryid bigint, plan_node_id integer, plan_node_name text, start_time timestamp with time zone, ec_operator integer, ec_status text, ec_execute_datanode text, ec_dsn text, ec_username text, ec_query text, ec_libodbc_type text, ec_fetch_count bigint
+
+- pg_stat_get_wlm_operator_info
+
+  描述：从内部哈希表中获取执行计划算子信息。
+
+  参数：nan
+
+  返回值类型：queryid bigint, pid bigint, plan_node_id integer, plan_node_name text, start_time timestamp with time zone, duration bigint, query_dop integer, estimated_rows bigint, tuple_processed bigint, min_peak_memory integer, max_peak_memory integer, average_peak_memory integer, memory_skew_percent integer, min_spill_size integer, max_spill_size integer, average_spill_size integer, spill_skew_percent integer, min_cpu_time bigint, max_cpu_time bigint, total_cpu_time bigint, cpu_skew_percent integer, warning text
+
+- pg_stat_get_wlm_node_resource_info
+
+  描述：获取当前节点资源信息。
+
+  参数：nan
+
+  返回值类型：min_mem_util integer, max_mem_util integer, min_cpu_util integer, max_cpu_util integer, min_io_util integer, max_io_util integer, used_mem_rate integer
+
+- pg_stat_get_session_wlmstat
+
+  描述：返回当前会话负载信息。
+
+  参数：pid integer
+
+  返回值类型：datid oid, threadid bigint, sessionid bigint, threadpid integer, usesysid oid, appname text, query text, priority bigint, block_time bigint, elapsed_time bigint, total_cpu_time bigint, skew_percent integer, statement_mem integer, active_points integer, dop_value integer, current_cgroup text, current_status text, enqueue_state text, attribute text, is_plana boolean, node_group text, srespool name
+
+- pg_stat_get_wlm_ec_operator_info
+
+  描述：从内部哈希表中获取EC执行计划算子信息。
+
+  参数：nan
+
+  返回值类型：queryid bigint, plan_node_id integer, plan_node_name text, start_time timestamp with time zone, duration bigint, tuple_processed bigint, min_peak_memory integer, max_peak_memory integer, average_peak_memory integer, ec_operator integer, ec_status text, ec_execute_datanode text, ec_dsn text, ec_username text, ec_query text, ec_libodbc_type text, ec_fetch_count bigint
+
+- pg_stat_get_wlm_instance_info
+
+  描述：返回当前实例负载信息。
+
+  参数：nan
+
+  返回值类型：instancename text, timestamp timestamp with time zone, used_cpu integer, free_memory integer, used_memory integer, io_await double precision, io_util double precision, disk_read double precision, disk_write double precision, process_read bigint, process_write bigint, logical_read bigint, logical_write bigint, read_counts bigint, write_counts bigint
+
+- pg_stat_get_wlm_instance_info_with_cleanup
+
+  描述：返回当前实例负载信息，并且保存到系统表中。
+
+  参数：nan
+
+  返回值类型：instancename text, timestamp timestamp with time zone, used_cpu integer, free_memory integer, used_memory integer, io_await double precision, io_util double precision, disk_read double precision, disk_write double precision, process_read bigint, process_write bigint, logical_read bigint, logical_write bigint, read_counts bigint, write_counts bigint
+
+- pg_stat_get_wlm_realtime_session_info
+
+  描述：返回实时会话负载信息。
+
+  参数：nan
+
+  返回值类型：nodename text, threadid bigint, block_time bigint, duration bigint, estimate_total_time bigint, estimate_left_time bigint, schemaname text, query_band text, spill_info text, control_group text, estimate_memory integer, min_peak_memory integer, max_peak_memory integer, average_peak_memory integer, memory_skew_percent integer, min_spill_size integer, max_spill_size integer, average_spill_size integer, spill_skew_percent integer, min_dn_time bigint, max_dn_time bigint, average_dn_time bigint, dntime_skew_percent integer, min_cpu_time bigint, max_cpu_time bigint, total_cpu_time bigint, cpu_skew_percent integer, min_peak_iops integer, max_peak_iops integer, average_peak_iops integer, iops_skew_percent integer, warning text, query text, query_plan text, cpu_top1_node_name text, cpu_top2_node_name text, cpu_top3_node_name text, cpu_top4_node_name text, cpu_top5_node_name text, mem_top1_node_name text, mem_top2_node_name text, mem_top3_node_name text, mem_top4_node_name text, mem_top5_node_name text, cpu_top1_value bigint, cpu_top2_value bigint, cpu_top3_value bigint, cpu_top4_value bigint, cpu_top5_value bigint, mem_top1_value bigint, mem_top2_value bigint, mem_top3_value bigint, mem_top4_value bigint, mem_top5_value bigint, top_mem_dn text, top_cpu_dn text
+
+- pg_stat_get_wlm_session_iostat_info
+
+  描述：返回会话负载IO信息。
+
+  参数：nan
+
+  返回值类型：threadid bigint, maxcurr_iops integer, mincurr_iops integer, maxpeak_iops integer, minpeak_iops integer, iops_limits integer, io_priority integer, curr_io_limits integer
+
+- pg_stat_get_wlm_statistics
+
+  描述：返回会话负载统计数据。
+
+  参数：nan
+
+  返回值类型：statement text, block_time bigint, elapsed_time bigint, total_cpu_time bigint, qualification_time bigint, skew_percent integer, control_group text, status text, action text
+
+## 其他函数
+
+- sys_guid函数 <a id = 'sys_guid'> </a>
+
+  描述：sys_guid生成并返回一个由16个字节组成的全球唯一标识符。生成的标识符由主机时间、线程标识符和随机值构成。
+
+  示例：
+
+  ```sql
+  mogdb=# select sys_guid();
+             sys_guid
+  ----------------------------------
+  0005D3DE87AB3147177B0300B2E3FED6
+  (1 row)
+  ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/1-configuration-settings-functions.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/1-configuration-settings-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..67b5d4b9f6dd06aeb8b758de44298058a1ce1d38
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/1-configuration-settings-functions.md
@@ -0,0 +1,62 @@
+---
+title: 配置设置函数
+summary: 配置设置函数
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 配置设置函数
+
+配置设置函数是可以用于查询以及修改运行时配置参数的函数。
+
+- current_setting(setting_name)
+
+  描述: 当前的设置值。
+
+  返回值类型: text
+
+  备注: current_setting用于以查询形式获取setting_name的当前值。和SQL语句SHOW是等效的。比如:
+
+  ```sql
+  mogdb=# SELECT current_setting('datestyle');
+
+   current_setting
+  -----------------
+   ISO, MDY
+  (1 row)
+  ```
+
+- set_working_grand_version_num_manually(tmp_version)
+
+    描述：通过切换授权版本号来更新和升级数据库的新特性。
+
+    返回值类型：void
+
+- shell_in(type)
+
+    描述： 为shell类型输入路由（那些尚未填充的类型）。
+
+    返回值类型：void
+
+- shell_out(type)
+
+    描述：为shell 类型输出路由（那些尚未填充的类型）。
+
+    返回值类型：void
+
+- set_config(setting_name, new_value, is_local)
+
+  描述: 设置参数并返回新值。
+
+  返回值类型: text
+
+  备注: set_config将参数setting_name设置为new_value。如果is_local为true，则new_value将只应用于当前事务。如果希望new_value应用于当前会话，可以使用false，和SQL语句SET是等效的。比如：
+
+  ```sql
+  mogdb=# SELECT set_config('log_statement_stats', 'off', false);
+
+   set_config
+  ------------
+   off
+  (1 row)
+  ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/10-undo-system-functions.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/10-undo-system-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..5ffe2f3fcb506ad3b3a645d015fd6d78ee5fda64
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/10-undo-system-functions.md
@@ -0,0 +1,62 @@
+---
+title: Undo系统函数
+summary: Undo系统函数
+author: Guo Huan
+date: 2021-10-28
+---
+
+# Undo系统函数
+
+- gs_undo_meta(type, zid, location)
+
+  描述：Undo各模块元信息。
+
+  参数说明：
+
+  - type(元信息类型)
+
+    0表示Undo Zone(Record) 对应的元信息。
+
+    1表示Undo Zone(Transaction Slot) 对应的元信息。
+
+    2表示Undo Space(Record) 对应的元信息。
+
+    3表示Undo Space(Transaction Slot) 对应的元信息。
+
+  - zid(undo zone编号)
+
+    -1表示所有undo zone的元信息。
+
+    0-1024*1024表示对应zoneid的元信息。
+
+  - location(读取位置）
+
+    0表示从当前内存中读取。
+
+    1表示从物理文件中读取。
+
+  返回值类型：record
+
+- gs_undo_translot(type, zid)
+
+  描述：Undo事务槽信息。
+
+  参数说明：
+
+  - type(元信息类型)
+
+    0表示Undo Zone(Record) 对应的元信息。
+
+    1表示Undo Zone(Transaction Slot) 对应的元信息。
+
+    2表示Undo Space(Record) 对应的元信息。
+
+    3表示Undo Space(Transaction Slot) 对应的元信息。
+
+  - zid(undo zone编号)
+
+    -1表示所有undo zone的元信息。
+
+    0-1024*1024表示对应zoneid的元信息。
+
+  返回值类型：record
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/2-universal-file-access-functions.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/2-universal-file-access-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..f3fc9a0335cd479635926f320cde5e6d17e11fbb
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/2-universal-file-access-functions.md
@@ -0,0 +1,148 @@
+---
+title: 通用文件访问函数
+summary: 通用文件访问函数
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 通用文件访问函数
+
+通用文件访问函数提供了对数据库服务器上的文件的本地访问接口。只有MogDB目录和log_directory目录里面的文件可以访问。使用相对路径访问MogDB目录里面的文件，以及匹配log_directory配置而设置的路径访问日志文件。只有数据库初始化用户才能使用这些函数。
+
+- pg_ls_dir(dirname text)
+
+  描述: 列出目录中的文件。
+
+  返回值类型: setof text
+
+  备注: pg_ls_dir返回指定目录里面的除了特殊项"."和".."之外所有名称。
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT pg_ls_dir('./');
+        pg_ls_dir
+  ----------------------
+   .postgresql.conf.swp
+   postgresql.conf
+   pg_tblspc
+   PG_VERSION
+   pg_ident.conf
+   core
+   server.crt
+   pg_serial
+   pg_twophase
+   postgresql.conf.lock
+   pg_stat_tmp
+   pg_notify
+   pg_subtrans
+   pg_ctl.lock
+   pg_xlog
+   pg_clog
+   base
+   pg_snapshots
+   postmaster.opts
+   postmaster.pid
+   server.key.rand
+   server.key.cipher
+   pg_multixact
+   pg_errorinfo
+   server.key
+   pg_hba.conf
+   pg_replslot
+   .pg_hba.conf.swp
+   cacert.pem
+   pg_hba.conf.lock
+   global
+   mogdb.state
+  (32 rows)
+  ```
+
+- pg_read_file(filename text, offset bigint, length bigint)
+
+  描述: 返回一个文本文件的内容。
+
+  返回值类型: text
+
+  备注: pg_read_file返回一个文本文件的一部分，从offset开始，最多返回length字节（如果先达到文件结尾，则小于这个数值）。如果offset是负数，则它是相对于文件结尾回退的长度。如果省略了offset和length，则返回整个文件。
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT pg_read_file('postmaster.pid',0,100);
+               pg_read_file
+  ---------------------------------------
+   53078                                +
+   /srv/BigData/hadoop/data1/dbnode+
+   1500022474                           +
+   8000                                +
+   /var/run/FusionInsight               +
+   localhost                            +
+    2
+  (1 row)
+  ```
+
+- pg_read_binary_file(filename text [, offset bigint, length bigint,missing_ok boolean])
+
+  描述: 返回一个二进制文件的内容。
+
+  返回值类型: bytea
+
+  备注: pg_read_binary_file的功能与pg_read_file类似，除了结果的返回值为bytea类型不一致，相应地不会执行编码检查。与convert_from函数结合，这个函数可以用来读取用指定编码的一个文件。
+
+  ```sql
+  mogdb=# SELECT convert_from(pg_read_binary_file('filename'), 'UTF8');
+  ```
+
+- pg_stat_file(filename text)
+
+  描述: 返回一个文本文件的状态信息。
+
+  返回值类型: record
+
+  备注: pg_stat_file返回一条记录，其中包含: 文件大小、最后访问时间戳、最后更改时间戳、最后文件状态修改时间戳以及标识传入参数是否为目录的Boolean值。典型的用法:
+
+  ```sql
+  mogdb=# SELECT * FROM pg_stat_file('filename');
+  ```
+
+  ```sql
+  mogdb=# SELECT (pg_stat_file('filename')).modification;
+  ```
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT convert_from(pg_read_binary_file('postmaster.pid'), 'UTF8');
+               convert_from
+  --------------------------------------
+   4881                                +
+   /srv/BigData/mogdb/data1/dbnode+
+   1496308688                          +
+   25108                               +
+   /opt/user/Bigdata/mogdb/mogdb_tmp +
+   *                                   +
+    25108001  43352069                 +
+
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT * FROM pg_stat_file('postmaster.pid');
+
+   size |         access         |      modification      |         change
+  | creation | isdir
+  ------+------------------------+------------------------+------------------------
+  +----------+-------
+    117 | 2017-06-05 11:06:34+08 | 2017-06-01 17:18:08+08 | 2017-06-01 17:18:08+08
+  |          | f
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT (pg_stat_file('postmaster.pid')).modification;
+        modification
+  ------------------------
+   2017-06-01 17:18:08+08
+  (1 row)
+  ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/3-server-signal-functions.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/3-server-signal-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..fb4deb3307989ce4adaebb16173f2e90fec5c8ea
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/3-server-signal-functions.md
@@ -0,0 +1,66 @@
+---
+title: 服务器信号函数
+summary: 服务器信号函数
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 服务器信号函数
+
+服务器信号函数向其他服务器进程发送控制信号。只有系统管理员才能使用这些函数。
+
+- pg_cancel_backend(pid int)
+
+  描述：取消一个后端的当前查询。
+
+  返回值类型：Boolean
+
+  备注：pg_cancel_backend向由pid标识的后端进程发送一个查询取消（SIGINT）信号。一个活动的后端进程的PID可以从pg_stat_activity视图的pid字段找到，或者在服务器上用ps列出数据库进程。具有SYSADMIN权限的用户，后端进程所连接的数据库的属主，后端进程的属主或者继承了内置角色gs_role_signal_backend权限的用户有权使用该函数。
+
+- pg_reload_conf()
+
+  描述：导致所有服务器进程重新装载它们的配置文件（需要系统管理员角色）。
+
+  返回值类型：Boolean
+
+  备注：pg_reload_conf给服务器发送一个SIGHUP信号，导致所有服务器进程重新装载配置文件。
+
+- pg_rotate_logfile()
+
+  描述：滚动服务器的日志文件（需要系统管理员角色）。
+
+  返回值类型：Boolean
+
+  备注：pg_rotate_logfile给日志文件管理器发送信号，告诉它立即切换到一个新的输出文件。这个函数只有在redirect_stderr用于日志输出的时候才有用，否则根本不存在日志文件管理器子进程。
+
+- pg_terminate_backend(pid int)
+
+  描述：终止一个后台线程。
+
+  返回值类型：Boolean
+
+  备注：如果成功，函数返回true，否则返回false。具有SYSADMIN权限的用户，后端进程所连接的数据库的属主，后端进程的属主或者继承了内置角色gs_role_signal_backend权限的用户有权使用该函数。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT pid from pg_stat_activity;
+         pid
+  -----------------
+   140657876268816
+  (1 rows)
+
+  mogdb=# SELECT pg_terminate_backend(140657876268816);
+   pg_terminate_backend
+  ----------------------
+   t
+  (1 row)
+  ```
+
+- pg_terminate_session(pid int64, sessionid int64)
+
+  描述：终止一个后台session。
+
+  返回值类型：Boolean
+
+  备注：如果成功，函数返回true，否则返回false。具有SYSADMIN权限的用户，会话所连接的数据库的属主，会话的属主或者继承了内置角色gs_role_signal_backend权限的用户有权使用该函数。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/4-backup-and-restoration-control-functions.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/4-backup-and-restoration-control-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..d7c2cd4741b80eb6ed6bfdda3943a798d74d94bd
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/4-backup-and-restoration-control-functions.md
@@ -0,0 +1,256 @@
+---
+title: 备份恢复控制函数
+summary: 备份恢复控制函数
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 备份恢复控制函数
+
+## 备份控制函数
+
+备份控制函数可帮助进行在线备份。
+
+- pg_create_restore_point(name text)
+
+  描述: 为执行恢复创建一个命名点。（需要管理员角色）
+
+  返回值类型: text
+
+  备注: pg_create_restore_point创建了一个可以用作恢复目的、有命名的事务日志记录，并返回相应的事务日志位置。在恢复过程中，recovery_target_name可以通过这个名称定位对应的日志恢复点，并从此处开始执行恢复操作。避免使用相同的名称创建多个恢复点，因为恢复操作将在第一个匹配（恢复目标）的名称上停止。
+
+- pg_current_xlog_location()
+
+  描述: 获取当前事务日志的写入位置。
+
+  返回值类型: text
+
+  备注: pg_current_xlog_location使用与前面那些函数相同的格式显示当前事务日志的写入位置。如果是只读操作，不需要系统管理员权限。
+
+- pg_current_xlog_insert_location()
+
+  描述: 获取当前事务日志的插入位置。
+
+  返回值类型: text
+
+  备注: pg_current_xlog_insert_location显示当前事务日志的插入位置。插入点是事务日志在某个瞬间的"逻辑终点"，而实际的写入位置则是从服务器内部缓冲区写出时的终点。写入位置是可以从服务器外部检测到的终点，如果要归档部分完成事务日志文件，则该操作即可实现。插入点主要用于服务器调试目的。如果是只读操作，不需要系统管理员权限。
+
+- gs_current_xlog_insert_end_location()
+
+    描述：获取当前事务日志的插入位置。
+
+    返回值类型：text
+
+    备注：gs_current_xlog_insert_end_location显示当前事务日志的实际插入位置。
+
+- pg_start_backup(label text [, fast boolean ])
+
+  描述: 开始执行在线备份。（需要管理员角色或复制的角色）
+
+  返回值类型: text
+
+  备注: pg_start_backup接受一个用户定义的备份标签（通常这是备份转储文件存放地点的名称）。这个函数向MogDB的数据目录写入一个备份标签文件，然后以文本方式返回备份的事务日志起始位置。
+
+  ```sql
+  mogdb=# SELECT pg_start_backup('label_goes_here');
+   pg_start_backup
+  -----------------
+   0/3000020
+  (1 row)
+  ```
+
+- pg_stop_backup()
+
+  描述: 完成执行在线备份。（需要管理员角色或复制的角色）
+
+  返回值类型: text
+
+  备注: pg_stop_backup删除pg_start_backup创建的标签文件，并且在事务日志归档区里创建一个备份历史文件。这个历史文件包含给予pg_start_backup的标签、备份的事务日志起始与终止位置、备份的起始和终止时间。返回值是备份的事务日志终止位置。计算出中止位置后，当前事务日志的插入点将自动前进到下一个事务日志文件，这样，结束的事务日志文件可以被立即归档从而完成备份。
+
+- pg_switch_xlog()
+
+  描述: 切换到一个新的事务日志文件。（需要管理员角色）
+
+  返回值类型: text
+
+  备注: pg_switch_xlog移动到下一个事务日志文件，以允许将当前日志文件归档（假定使用连续归档）。返回值是刚完成的事务日志文件的事务日志结束位置+1。如果从最后一次事务日志切换以来没有活动的事务日志，则pg_switch_xlog什么事也不做，直接返回当前事务日志文件的开始位置。
+
+- pg_xlogfile_name(location text)
+
+  描述: 将事务日志的位置字符串转换为文件名。
+
+  返回值类型: text
+
+  备注: pg_xlogfile_name仅抽取事务日志文件名称。如果给定的事务日志位置恰好位于事务日志文件的交界上，这两个函数都返回前一个事务日志文件的名称。这对于管理事务日志归档来说是非常有利的，因为前一个文件是当前最后一个需要归档的文件。
+
+- pg_xlogfile_name_offset(location text)
+
+  描述: 将事务日志的位置字符串转换为文件名并返回在文件中的字节偏移量。
+
+  返回值类型: text,integer
+
+  备注: 可以使用pg_xlogfile_name_offset从前述函数的返回结果中抽取相应的事务日志文件名称和字节偏移量。例如:
+
+  ```sql
+  mogdb=# SELECT * FROM pg_xlogfile_name_offset(pg_stop_backup());
+  NOTICE:  pg_stop_backup cleanup done, waiting for required WAL segments to be archived
+  NOTICE:  pg_stop_backup complete, all required WAL segments have been archived
+          file_name         | file_offset
+  --------------------------+-------------
+  000000010000000000000003  |         272
+  (1 row)
+  ```
+
+- pg_xlog_location_diff(location text, location text)
+
+  描述: 计算两个事务日志位置之间在字节上的区别。
+
+  返回值类型: numeric
+
+- pg_cbm_tracked_location()
+
+  描述: 用于查询cbm解析到的lsn位置。
+
+  返回值类型: text
+
+- pg_cbm_get_merged_file(startLSNArg text, endLSNArg text)
+
+  描述: 用于将指定lsn范围之内的cbm文件合并成一个cbm文件，并返回合并完的cbm文件名。
+
+  返回值类型: text
+
+  备注：必须是系统管理员或运维管理员才能获取cbm合并文件。
+
+- pg_cbm_get_changed_block(startLSNArg text, endLSNArg text)
+
+  描述: 用于将指定lsn范围之内的cbm文件合并成一个表，并返回表的各行记录。
+
+  返回值类型: records
+
+  备注: pg_cbm_get_changed_block返回的表字段包含: 合并起始的lsn，合并截止的lsn， 表空间oid，库oid，表的relfilenode，表的fork number，表是否被删除，表是否被创建，表是否被截断，表被截断后的页面数，有多少页被修改以及被修改的页号的列表。
+
+- pg_cbm_recycle_file(targetLSNArg text)
+
+  描述: 删除不再使用的cbm文件，并返回删除后的第一条lsn。
+
+  返回值类型: text
+
+- pg_cbm_force_track(targetLSNArg text,timeOut int)
+
+  描述: 强制执行一次cbm追踪到指定的xlog位置，并返回实际追踪结束点的xlog位置。
+
+  返回值类型: text
+
+- pg_enable_delay_ddl_recycle()
+
+  描述：开启延迟DDL功能，并返回开启点的xlog位置。需要管理员角色或运维管理员角色打开operate_mode。
+
+  返回值类型：text
+
+- pg_disable_delay_ddl_recycle(barrierLSNArg text, isForce bool)
+
+    描述：关闭延迟DDL功能，并返回本次延迟DDL生效的xlog范围。需要管理员角色或运维管理员角色打开operate_mode。
+
+    返回值类型：records
+
+- pg_enable_delay_xlog_recycle()
+
+    描述：开启延迟xlog回收功能，数据库主节点修复使用。
+
+    返回值类型：void
+
+- pg_disable_delay_xlog_recycle()
+
+    描述：关闭延迟xlog回收功能，数据库主节点修复使用。
+
+    返回值类型：void
+
+- pg_cbm_rotate_file(rotate_lsn text)
+
+    描述：等待cbm解析到rotate_lsn之后，强制切换文件，在build期间调用。
+
+    返回值类型：void。
+
+- gs_roach_stop_backup(backupid text)
+
+    描述：停止一个内部备份工具GaussRoach开启的备份。与pg_stop_backup系统函数类似，但更轻量。
+
+    返回值类型：text，内容为当前日志的插入位置。
+
+    备注：目前MogDB不支持。
+
+- gs_roach_enable_delay_ddl_recycle(backupid name)
+
+    描述：开启延迟DDL功能，并返回开启点的日志位置。与pg_enable_delay_ddl_recycle系统函数类似，但更轻量。并且，通过传入不同的backupid，可以支持并发打开延迟DDL。
+
+    返回值类型：text，内容为返回开启点的日志位置。
+
+    备注：目前MogDB不支持。
+
+- gs_roach_disable_delay_ddl_recycle(backupid text)
+
+    描述：关闭延迟DDL功能，并返回本次延迟DDL生效的日志范围，并删除该范围内被用户删除的列存表物理文件。与pg_enable_delay_ddl_recycle系统函数类似，但更轻量。并且，通过传入不同的backupid，可以支持并发关闭延迟DDL功能。
+
+    返回值类型：records，内容为本次延迟DDL生效的日志范围。
+
+    备注：目前MogDB不支持。
+
+- gs_roach_switch_xlog(request_ckpt bool)
+
+    描述：切换当前使用的日志段文件，并且，如果request_ckpt为true，则触发一个全量检查点。
+
+    返回值类型：text，内容为切段日志的位置。
+
+    备注：目前MogDB不支持。
+
+## 恢复控制函数
+
+恢复信息函数提供了当前备机状态的信息。这些函数可能在恢复期间或正常运行中执行。
+
+- pg_is_in_recovery()
+
+  描述: 如果恢复仍然在进行中则返回true。
+
+  返回值类型: bool
+
+- pg_last_xlog_receive_location()
+
+  描述: 获取最后接收事务日志的位置并通过流复制将其同步到磁盘。当流复制正在进行时，事务日志将持续递增。如果恢复已完成，则最后一次获取的WAL记录会被静态保持并在恢复过程中同步到磁盘。如果流复制不可用，或还没有开始，这个函数返回NULL。
+
+  返回值类型: text
+
+- pg_last_xlog_replay_location()
+
+  描述: 获取最后一个事务日志在恢复时重放的位置。如果恢复仍在进行，事务日志将持续递增。如果已经完成恢复，则将保持在恢复期间最后接收WAL记录的值。如果未进行恢复但服务器正常启动时，则这个函数返回NULL。
+
+  返回值类型: text
+
+- pg_last_xact_replay_timestamp()
+
+  描述: 获取最后一个事务在恢复时重放的时间戳。这是为在主节点上生成事务提交或终止WAL记录的时间。如果在恢复时没有事务重放，则这个函数返回NULL。如果恢复仍在进行，则事务日志将持续递增。如果恢复已经完成，则将保持在恢复期间最后接收WAL记录的值。如果服务器无需恢复就已正常启动，则这个函数返回NULL。
+
+  返回值类型: timestamp with time zone
+
+恢复控制函数控制恢复的进程。这些函数可能只在恢复时被执行。
+
+- pg_is_xlog_replay_paused()
+
+  描述: 如果恢复暂停则返回true。
+
+  返回值类型: bool
+
+- pg_xlog_replay_pause()
+
+  描述: 立即暂停恢复。
+
+  返回值类型: void
+
+- pg_xlog_replay_resume()
+
+  描述: 如果恢复处于暂停状态，则重新启动。
+
+  返回值类型: void
+
+当恢复暂停时，没有发生数据库更改。如果是在热备里，所有新的查询将看到一致的数据库快照，并且不会有进一步的查询冲突产生，直到恢复继续。
+
+如果不能使用流复制，则暂停状态将无限的延续。当流复制正在进行时，将连续接收WAL记录，最终将填满可用磁盘空间，这个进度取决于暂停的持续时间，WAL生成的速度和可用的磁盘空间。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/5-snapshot-synchronization-functions.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/5-snapshot-synchronization-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..f112b6ee51d8da8eea0bc1c83c37e4ac0a5cc4a8
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/5-snapshot-synchronization-functions.md
@@ -0,0 +1,24 @@
+---
+title: 快照同步函数
+summary: 快照同步函数
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 快照同步函数
+
+快照同步函数是导出当前快照的标识符。
+
+- pg_export_snapshot()
+
+描述: 保存当前的快照并返回它的标识符。
+
+返回值类型: text
+
+备注: 函数pg_export_snapshot保存当前的快照并返回一个文本字符串标识此快照。这个字符串必须传递给想要导入快照的客户端。可用在set transaction snapshot snapshot_id时导入snapshot，但是应用的前提是该事务设置了SERIALIZABLE或REPEATABLE READ隔离级别。该函数的输出不可用做set transaction snapshot的输入。
+
+- pg_export_snapshot_and_csn()
+
+描述: 保存当前的快照并返回它的标识符。比pg_export_snapshot()多返回一列CSN，表示当前快照的CSN。
+
+返回值类型: text
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/6-database-object-functions.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/6-database-object-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..ef465ad490a1f0972197b4ad1d57c9bc9598f6b6
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/6-database-object-functions.md
@@ -0,0 +1,430 @@
+---
+title: 数据库对象函数
+summary: 数据库对象函数
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 数据库对象函数
+
+## 数据库对象尺寸函数
+
+数据库对象尺寸函数计算数据库对象使用的实际磁盘空间。
+
+- pg_column_size(any)
+
+  描述: 存储一个指定的数值需要的字节数（可能压缩过）。
+
+  返回值类型: int
+
+  备注: pg_column_size显示用于存储某个独立数据值的空间。
+
+  ```sql
+  mogdb=# SELECT pg_column_size(1);
+   pg_column_size
+  ----------------
+                4
+  (1 row)
+  ```
+
+- pg_database_size(oid)
+
+  描述: 指定OID代表的数据库使用的磁盘空间。
+
+  返回值类型: bigint
+
+- pg_database_size(name)
+
+  描述: 指定名称的数据库使用的磁盘空间。
+
+  返回值类型: bigint
+
+  备注: pg_database_size接受一个数据库的OID或者名称，然后返回该对象使用的全部磁盘空间。
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT pg_database_size('mogdb');
+   pg_database_size
+  ------------------
+           51590112
+  (1 row)
+  ```
+
+- pg_relation_size(oid)
+
+  描述: 指定OID代表的表或者索引所使用的磁盘空间。
+
+  返回值类型: bigint
+
+- get_db_source_datasize()
+
+  描述: 估算当前数据库非压缩态的数据总容量。
+
+  返回值类型: bigint
+
+  备注: （1）调用该函数前需要做analyze；（2）通过估算列存的压缩率计算非压缩态的数据总容量。
+
+  示例:
+
+  ```sql
+  mogdb=# analyze;
+  ANALYZE
+  mogdb=# select get_db_source_datasize();
+   get_db_source_datasize
+  ------------------------
+              35384925667
+  (1 row)
+  ```
+
+- pg_relation_size(text)
+
+  描述: 指定名称的表或者索引使用的磁盘空间。表名称可以用模式名修饰。
+
+  返回值类型: bigint
+
+- pg_relation_size(relation regclass, fork text)
+
+  描述: 指定表或索引的指定分叉树（'main'，'fsm'或'vm'）使用的磁盘空间。
+
+  返回值类型: bigint
+
+- pg_relation_size(relation regclass)
+
+  描述: pg_relation_size(…, 'main')的简写。
+
+  返回值类型: bigint
+
+  备注: pg_relation_size接受一个表、索引、压缩表的OID或者名称，然后返回它们的字节大小。
+
+- pg_partition_size(oid,oid)
+
+  描述: 指定OID代表的分区使用的磁盘空间。其中，第一个oid为表的OID，第二个oid为分区的OID。
+
+  返回值类型: bigint
+
+- pg_partition_size(text, text)
+
+  描述: 指定名称的分区使用的磁盘空间。其中，第一个text为表名，第二个text为分区名。
+
+  返回值类型: bigint
+
+- pg_partition_indexes_size(oid,oid)
+
+  描述: 指定OID代表的分区的索引使用的磁盘空间。其中，第一个oid为表的OID，第二个oid为分区的OID。
+
+  返回值类型: bigint
+
+- pg_partition_indexes_size(text,text)
+
+  描述: 指定名称的分区的索引使用的磁盘空间。其中，第一个text为表名，第二个text为分区名。
+
+  返回值类型: bigint
+
+- pg_indexes_size(regclass)
+
+  描述: 附加到指定表的索引使用的总磁盘空间。
+
+  返回值类型: bigint
+
+- pg_size_pretty(bigint)
+
+  描述: 将以64位整数表示的字节值转换为具有单位的易读格式。
+
+  返回值类型: text
+
+- pg_size_pretty(numeric)
+
+  描述: 将以数值表示的字节值转换为具有单位的易读格式。
+
+  返回值类型: text
+
+  备注: pg_size_pretty用于把其他函数的结果格式化成一种易读的格式，可以根据情况使用KB 、MB 、GB 、TB。
+
+- pg_table_size(regclass)
+
+  描述: 指定的表使用的磁盘空间，不计索引（但是包含TOAST，自由空间映射和可见性映射）。
+
+  返回值类型: bigint
+
+- pg_tablespace_size(oid)
+
+  描述: 指定OID代表的表空间使用的磁盘空间。
+
+  返回值类型: bigint
+
+- pg_tablespace_size(name)
+
+  描述: 指定名称的表空间使用的磁盘空间。
+
+  返回值类型: bigint
+
+  备注:
+
+  pg_tablespace_size接受一个数据库的OID或者名称，然后返回该对象使用的全部磁盘空间。
+
+- pg_total_relation_size(oid)
+
+  描述: 指定OID代表的表使用的磁盘空间，包括索引和压缩数据。
+
+  返回值类型: bigint
+
+- pg_total_relation_size(regclass)
+
+  描述: 指定的表使用的总磁盘空间，包括所有的索引和TOAST数据。
+
+  返回值类型: bigint
+
+- pg_total_relation_size(text)
+
+  描述: 指定名称的表所使用的全部磁盘空间，包括索引和压缩数据。表名称可以用模式名修饰。
+
+  返回值类型: bigint
+
+  备注: pg_total_relation_size接受一个表或者一个压缩表的OID或者名称，然后返回以字节计的数据和所有相关的索引和压缩表的尺寸。
+
+- datalength(any)
+
+  描述: 计算一个指定的数据需要的字节数（不考虑数据的管理空间和数据压缩，数据类型转换等情况）。
+
+  返回值类型: int
+
+  备注: datalength用于计算某个独立数据值的空间。
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT datalength(1);
+  datalength
+  ------------
+  4
+  (1 row)
+  ```
+
+  目前支持的数据类型及计算方式见下表：
+
+  <table>
+      <tr>
+          <th colspan=3>数据类型</th>
+          <th>存储空间</th>
+      </tr>
+      <tr>
+          <td rowspan=18>数值类型</td>
+          <td rowspan=5>整数类型</td>
+          <td>TINYINT</td>
+          <td>1</td>
+      </tr>
+      <tr>
+          <td>SMALLINT</td>
+          <td>2</td>
+      </tr>
+      <tr>
+          <td>INTEGER</td>
+          <td>4</td>
+      </tr>
+      <tr>
+          <td>BINARY_INTEGER</td>
+          <td>4</td>
+      </tr>
+      <tr>
+          <td>BIGINT</td>
+          <td>8</td>
+      </tr>
+      <tr>
+          <td rowspan=3>任意精度型</td>
+          <td>DECIMAL</td>
+          <td>每4位十进制数占两个字节，小数点前后数字分别计算</td>
+      </tr>
+      <tr>
+          <td>NUMERIC</td>
+          <td>每4位十进制数占两个字节，小数点前后数字分别计算</td>
+      </tr>
+      <tr>
+          <td>NUMBER</td>
+          <td>每4位十进制数占两个字节，小数点前后数字分别计算</td>
+      </tr>
+      <tr>
+          <td rowspan=3>序列整型</td>
+          <td>SMALLSERIAL</td>
+          <td>2</td>
+      </tr>
+      <tr>
+          <td>SERIAL</td>
+          <td>4</td>
+      </tr>
+      <tr>
+          <td>BIGSERIAL</td>
+          <td>8</td>
+      </tr>
+      <tr>
+          <td rowspan=7>浮点类型</td>
+          <td>FLOAT4</td>
+          <td>4</td>
+      </tr>
+      <tr>
+          <td>DOUBLE PRECISION</td>
+          <td>8</td>
+      </tr>
+      <tr>
+          <td>FLOAT8</td>
+          <td>8</td>
+      </tr>
+      <tr>
+          <td>BINARY_DOUBLE</td>
+          <td>8</td>
+      </tr>
+      <tr>
+          <td>FLOAT[(p)]</td>
+          <td>每4位十进制数占两个字节，小数点前后数字分别计算</td>
+      </tr>
+      <tr>
+          <td>DEC[(p[,s])]</td>
+          <td>每4位十进制数占两个字节，小数点前后数字分别计算</td>
+      </tr>
+      <tr>
+          <td>INTEGER[(p[,s])]</td>
+          <td>每4位十进制数占两个字节，小数点前后数字分别计算</td>
+      </tr>
+      <tr>
+          <td>布尔类型</td>
+          <td>布尔类型</td>
+          <td>BOOLEAN</td>
+          <td>1</td>
+      </tr>
+      <tr>
+          <td rowspan=11>字符类型</td>
+          <td rowspan=11>字符类型</td>
+          <td>CHAR</td>
+          <td>n</td>
+      </tr>
+      <tr>
+          <td>CHAR(n)</td>
+          <td>n</td>
+      </tr>
+      <tr>
+          <td>CHARACTER(n)</td>
+          <td>n</td>
+      </tr>
+      <tr>
+          <td>NCHAR(n)</td>
+          <td>n</td>
+      </tr>
+      <tr>
+          <td>VARCHAR(n)</td>
+          <td>n</td>
+      </tr>
+      <tr>
+          <td>CHARACTER</td>
+          <td>字符实际字节数</td>
+      </tr>
+      <tr>
+          <td>VARYING(n)</td>
+          <td>字符实际字节数</td>
+      </tr>
+      <tr>
+          <td>VARCHAR2(n)</td>
+          <td>字符实际字节数</td>
+      </tr>
+      <tr>
+          <td>NVARCHAR2(n)</td>
+          <td>字符实际字节数</td>
+      </tr>
+      <tr>
+          <td>TEXT</td>
+          <td>字符实际字节数</td>
+      </tr>
+      <tr>
+          <td>CLOB</td>
+          <td>字符实际字节数</td>
+      </tr>
+      <tr>
+          <td rowspan=11>时间类型</td>
+          <td rowspan=11>时间类型</td>
+          <td>DATE</td>
+          <td>8</td>
+      </tr>
+      <tr>
+          <td>TIME</td>
+          <td>8</td>
+      </tr>
+      <tr>
+          <td>TIMEZ</td>
+          <td>12</td>
+      </tr>
+      <tr>
+          <td>TIMESTAMP</td>
+          <td>8</td>
+      </tr>
+      <tr>
+          <td>TIMESTAMPZ</td>
+          <td>8</td>
+      </tr>
+      <tr>
+          <td>SMALLDATETIME</td>
+          <td>8</td>
+      </tr>
+      <tr>
+          <td>INTERVAL DAY TO SECOND</td>
+          <td>16</td>
+      </tr>
+      <tr>
+          <td>INTERVAL</td>
+          <td>16</td>
+      </tr>
+      <tr>
+          <td>RELTIME</td>
+          <td>4</td>
+      </tr>
+      <tr>
+          <td>ABSTIME</td>
+          <td>4</td>
+      </tr>
+      <tr>
+          <td>TINTERVAL</td>
+          <td>12</td>
+      </tr>
+  </table>
+
+## 数据库对象位置函数
+
+- pg_relation_filenode(relation regclass)
+
+  描述: 指定关系的文件节点数。
+
+  返回值类型: oid
+
+  备注: pg_relation_filenode接受一个表、索引、序列或压缩表的OID或者名称，并且返回当前分配给它的“filenode”数。文件节点是关系使用的文件名称的基本组件。对大多数表来说，结果和pg_class.relfilenode相同，但对确定的系统目录来说， relfilenode为0而且这个函数必须用来获取正确的值。如果传递一个没有存储的关系，比如一个视图，那么这个函数返回NULL。
+
+- pg_relation_filepath(relation regclass)
+
+  描述: 指定关系的文件路径名。
+
+  返回值类型: text
+
+  备注: pg_relation_filepath类似于pg_relation_filenode，但是它返回关系的整个文件路径名（相对于MogDB的数据目录PGDATA）。
+
+- pg_filenode_relation(tablespace oid, filenode oid)
+
+    描述：获取对应的tablespace和relfilenode所对应的表名。
+
+    返回类型：regclass
+
+- pg_partition_filenode(partition_oid)
+
+    描述：获取到指定分区表的oid锁对应的filenode。
+
+    返回类型：oid
+
+- pg_partition_filepath(partition_oid)
+
+    描述：指定分区的文件路径名。
+
+    返回值类型：text
+
+## 回收站对象函数
+
+- gs_is_recycle_object(classid, objid, objname)
+
+    描述：判断是否为回收站对象。
+
+    返回值类型：bool
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/7-advisory-lock-functions.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/7-advisory-lock-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..b18559e284c13dcd83af0470fb8285b095824945
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/7-advisory-lock-functions.md
@@ -0,0 +1,190 @@
+---
+title: 咨询锁函数
+summary: 咨询锁函数
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 咨询锁函数
+
+咨询锁函数用于管理咨询锁（Advisory Lock）。
+
+- pg_advisory_lock(key bigint)
+
+  描述: 获取会话级别的排它咨询锁。
+
+  返回值类型: void
+
+  备注: pg_advisory_lock锁定应用程序定义的资源，该资源可以用一个64位或两个不重叠的32位键值标识。如果已经有另外的会话锁定了该资源，则该函数将阻塞到该资源可用为止。这个锁是排它的。多个锁定请求将会被压入栈中，因此，如果同一个资源被锁定了三次，它必须被解锁三次以将资源释放给其他会话使用。
+
+- pg_advisory_lock(key1 int, key2 int)
+
+  描述: 获取会话级别的排它咨询锁。
+
+  返回值类型: void
+
+  备注: 只允许sysadmin对键值对(65535, 65535)加会话级别的排它咨询锁，普通用户无权限。
+
+- pg_advisory_lock(int4, int4, Name)
+
+    描述：获取指定数据库的排它咨询锁。
+
+    返回值类型：void
+
+- pg_advisory_lock_shared(key bigint)
+
+  描述: 获取会话级别的共享咨询锁。
+
+  返回值类型: void
+
+- pg_advisory_lock_shared(key1 int, key2 int)
+
+  描述: 获取会话级别的共享咨询锁。
+
+  返回值类型: void
+
+  备注: pg_advisory_lock_shared类似于pg_advisory_lock，不同之处仅在于共享锁会话可以和其他请求共享锁的会话共享资源，但排它锁除外。
+
+- pg_advisory_unlock(key bigint)
+
+  描述: 释放会话级别的排它咨询锁。
+
+  返回值类型: Boolean
+
+- pg_advisory_unlock(key1 int, key2 int)
+
+  描述: 释放会话级别的排它咨询锁。
+
+  返回值类型: Boolean
+
+  备注: pg_advisory_unlock释放先前取得的排它咨询锁。如果释放成功则返回true。如果实际上并未持有指定的锁，将返回false并在服务器中产生一条SQL警告信息。
+
+- pg_advisory_unlock(int4, int4, Name)
+
+    描述：释放指定数据库上的排它咨询锁。
+
+    返回值类型：Boolean
+
+    备注：如果释放成功则返回true；如果未持有锁，则返回false。
+
+- pg_advisory_unlock_shared(key bigint)
+
+  描述: 释放会话级别的共享咨询锁。
+
+  返回值类型: Boolean
+
+- pg_advisory_unlock_shared(key1 int, key2 int)
+
+  描述: 释放会话级别的共享咨询锁。
+
+  返回值类型: Boolean
+
+  备注: pg_advisory_unlock_shared类似于pg_advisory_unlock，不同之处在于该函数释放的是共享咨询锁。
+
+- pg_advisory_unlock_all()
+
+  描述: 释放当前会话持有的所有咨询锁。
+
+  返回值类型: void
+
+  备注: pg_advisory_unlock_all将会释放当前会话持有的所有咨询锁，该函数在会话结束的时候被隐含调用，即使客户端异常地断开连接也是一样。
+
+- pg_advisory_xact_lock(key bigint)
+
+  描述: 获取事务级别的排它咨询锁。
+
+  返回值类型: void
+
+- pg_advisory_xact_lock(key1 int, key2 int)
+
+  描述: 获取事务级别的排它咨询锁。
+
+  返回值类型: void
+
+  备注: pg_advisory_xact_lock类似于pg_advisory_lock，不同之处在于锁是自动在当前事务结束时释放，而且不能被显式的释放。只允许sysadmin对键值对(65535, 65535)加事务级别的排它咨询锁，普通用户无权限。
+
+- pg_advisory_xact_lock_shared(key bigint)
+
+  描述: 获取事务级别的共享咨询锁。
+
+  返回值类型: void
+
+- pg_advisory_xact_lock_shared(key1 int, key2 int)
+
+  描述: 获取事务级别的共享咨询锁。
+
+  返回值类型: void
+
+  备注: pg_advisory_xact_lock_shared类似于pg_advisory_lock_shared，不同之处在于锁是在当前事务结束时自动释放，而且不能被显式的释放。
+
+- pg_try_advisory_lock(key bigint)
+
+  描述: 尝试获取会话级排它咨询锁。
+
+  返回值类型: Boolean
+
+  备注: pg_try_advisory_lock类似于pg_advisory_lock，不同之处在于该函数不会阻塞以等待资源的释放。它要么立即获得锁并返回true，要么返回false表示目前不能锁定。
+
+- pg_try_advisory_lock(key1 int, key2 int)
+
+  描述: 尝试获取会话级排它咨询锁。
+
+  返回值类型: Boolean
+
+  备注: 只允许sysadmin对键值对(65535, 65535)加会话级别的排它咨询锁，普通用户无权限。
+
+- pg_try_advisory_lock_shared(key bigint)
+
+  描述: 尝试获取会话级共享咨询锁。
+
+  返回值类型: Boolean
+
+- pg_try_advisory_lock_shared(key1 int, key2 int)
+
+  描述: 尝试获取会话级共享咨询锁。
+
+  返回值类型: Boolean
+
+  备注: pg_try_advisory_lock_shared类似于pg_try_advisory_lock，不同之处在于该函数尝试获得共享锁而不是排它锁。
+
+- pg_try_advisory_xact_lock(key bigint)
+
+  描述: 尝试获取事务级别的排它咨询锁。
+
+  返回值类型: Boolean
+
+- pg_try_advisory_xact_lock(key1 int, key2 int)
+
+  描述: 尝试获取事务级别的排它咨询锁。
+
+  返回值类型: Boolean
+
+  备注: pg_try_advisory_xact_lock类似于pg_try_advisory_lock，不同之处在于如果得到锁，在当前事务的结束时自动释放，而且不能被显式的释放。只允许sysadmin对键值对(65535, 65535)加事务级别的排它咨询锁，普通用户无权限。
+
+- pg_try_advisory_xact_lock_shared(key bigint)
+
+  描述: 尝试获取事务级别的共享咨询锁。
+
+  返回值类型: Boolean
+
+- pg_try_advisory_xact_lock_shared(key1 int, key2 int)
+
+  描述: 尝试获取事务级别的共享咨询锁。
+
+  返回值类型: Boolean
+
+  备注: pg_try_advisory_xact_lock_shared类似于pg_try_advisory_lock_shared，不同之处在于如果得到锁，在当前事务结束时自动释放，而且不能被显式的释放。
+
+- lock_cluster_ddl()
+
+  描述: 尝试对MogDB内所有存活的数据库主节点获取会话级别的排他咨询锁。
+
+  返回值类型: Boolean
+
+  备注: 只允许sysadmin调用，普通用户无权限。
+
+- unlock_cluster_ddl()
+
+  描述: 尝试对数据库主节点会话级别的排他咨询锁。
+
+  返回值类型: Boolean
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/8-logical-replication-functions.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/8-logical-replication-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..210f387a468216f32b4af13944b37f50e0c45588
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/8-logical-replication-functions.md
@@ -0,0 +1,168 @@
+---
+title: 逻辑复制函数
+summary: 逻辑复制函数
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 逻辑复制函数
+
+- pg_create_logical_replication_slot('slot_name', 'plugin_name')
+
+  描述: 创建逻辑复制槽。
+
+  参数说明:
+
+  - slot_name
+
+    流复制槽名称。
+
+    取值范围: 字符串，不支持除字母，数字,以及（_?-.）以外的字符。
+
+  - plugin_name
+
+    插件名称。
+
+    取值范围: 字符串，当前支持mppdb_decoding。
+
+  返回值类型: name, text
+
+  备注: 第一个返回值表示slot_name，第二个返回值表示该逻辑复制槽解码的起始LSN位置。
+
+- pg_create_physical_replication_slot('slot_name', 'isDummyStandby')
+
+  描述: 创建新的物理复制槽。
+
+  参数说明:
+
+  - slot_name
+
+    流复制槽名称。
+
+    取值范围: 字符串，不支持除字母，数字,以及（_?-.）以外的字符。
+
+  - isDummyStandby
+
+    是否是从从备连接主机创建的复制槽。
+
+    类型: bool。
+
+    返回值类型: name, text
+
+- pg_drop_replication_slot('slot_name')
+
+  描述: 删除流复制槽。
+
+  参数说明:
+
+  - slot_name
+
+    流复制槽名称。
+
+    取值范围: 字符串，不支持除字母，数字,以及（_?-.）以外的字符。
+
+  返回值类型: void
+
+- pg_logical_slot_peek_changes('slot_name', 'LSN', upto_nchanges, 'options_name', 'options_value')
+
+  描述: 解码并不推进流复制槽（下次解码可以再次获取本次解出的数据）。
+
+  参数说明:
+
+  - slot_name
+
+    流复制槽名称。
+
+    取值范围: 字符串，不支持除字母，数字,以及（_?-.）以外的字符。
+
+  - LSN
+
+    日志的LSN，表示只解码小于等于此LSN的日志。
+
+    取值范围: 字符串（LSN，格式为xlogid/xrecoff），如'1/2AAFC60'。为NULL时表示不对解码截止的日志位置做限制。
+
+  - upto_nchanges
+
+    解码条数（包含begin和commit）。假设一共有三条事务，分别包含3、5、7条记录，如果upto_nchanges为4，那么会解码出前两个事务共8条记录。解码完第二条事务时发现解码条数记录大于等于upto_nchanges，会停止解码。
+
+    取值范围: 非负整数。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:** LSN和upto_nchanges中任一参数达到限制，解码都会结束。
+
+  - options: 此项为可选参数。
+
+    - include-xids
+
+    解码出的data列是否包含xid信息。
+
+    取值范围: 0或1，默认值为1。
+
+    - 0: 设为0时，解码出的data列不包含xid信息。
+    - 1: 设为1时，解码出的data列包含xid信息。
+
+    - skip-empty-xacts
+
+    解码时是否忽略空事务信息。
+
+    取值范围: 0或1，默认值为0。
+
+    - 0: 设为0时，解码时不忽略空事务信息。
+    - 1: 设为1时，解码时会忽略空事务信息。
+
+    - include-timestamp
+
+    解码信息是否包含commit时间戳。
+
+    取值范围: 0或1，默认值为0。
+
+    - 0: 设为0时，解码信息不包含commit时间戳。
+    - 1: 设为1时，解码信息包含commit时间戳。
+
+  返回值类型: text, uint, text 备注: 函数返回解码结果，每一条解码结果包含三列，对应上述返回值类型，分别表示LSN位置、xid和解码内容。
+
+- pg_logical_slot_get_changes('slot_name', 'LSN', upto_nchanges, 'options_name', 'options_value')
+
+  描述: 解码并推进流复制槽。
+
+  参数说明: 与pg_logical_slot_peek_changes一致，详细内容请参见 pg_logical_slot_peek_ch…。
+
+- pg_replication_slot_advance ('slot_name', 'LSN')
+
+  描述: 直接推进流复制槽到指定LSN，不输出解码结果。
+
+  参数说明:
+
+  - slot_name
+
+    流复制槽名称。
+
+    取值范围: 字符串，不支持除字母，数字,以及（_?-.）以外的字符。
+
+  - LSN
+
+    推进到的日志LSN位置，下次解码时只会输出提交位置比该LSN大的事务结果。如果输入的LSN比当前流复制槽记录的推进位置还要小，则直接返回；如果输入的LSN比当前最新物理日志LSN还要大，则推进到当前最新物理日志LSN。
+
+    取值范围: 字符串（LSN，格式为xlogid/xrecoff）。
+
+  返回值类型: name, text
+
+  备注: 返回值分别对应slot_name和实际推进至的LSN。
+
+- pg_get_replication_slots
+
+  描述: 获取复制槽列表。
+
+  返回值类型: text，text，text，oid，boolean，xid，xid，text，boolean
+
+  示例:
+
+  ```sql
+    mogdb=# select * from pg_get_replication_slots();
+     slot_name |     plugin     | slot_type | datoid | active | xmin | catalog_xmin | restart_lsn | dummy_standby
+    -----------+----------------+-----------+--------+--------+------+--------------+-------------+---------------
+     wkl001    | mppdb_decoding | logical   |  15914 | f      |      |      2079556 | 4/1B81D920  | f
+     dn_6002   |                | physical  |      0 | t      |      |              | 8/7CB63BD8  | f
+     dn_6004   |                | physical  |      0 | t      |      |              | 8/7CB63BD8  | f
+     dn_6003   |                | physical  |      0 | t      |      |              | 8/7CB63BD8  | f
+     gfslot001 | mppdb_decoding | logical   |  15914 | f      |      |      2412553 | 4/A54B2428  | (5 rows)
+  ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/9-other-functions.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/9-other-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..7f76eb8d065cb69d379e08749061a0d50060f1b3
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/9-other-functions.md
@@ -0,0 +1,472 @@
+---
+title: 其它函数
+summary: 其它函数
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 其它函数
+
+- plan_seed()
+
+  描述：获取前一次查询语句的seed值（内部使用）。
+
+  返回值类型：int
+
+- pg_stat_get_env()
+
+  描述：获取当前节点的环境变量信息，仅sysadmin和monitor admin可以访问。
+
+  返回值类型：record
+
+  示例：
+
+  ```sql
+  mogdb=# select pg_stat_get_env();
+                                                                                pg_stat_get_env
+  ---------------------------------------------------------------------------------------------------------------------------------------
+   (coordinator1,localhost,144773,49100,/data1/GaussDB_Kernel_TRUNK/install,/data1/GaussDB_Kernel_TRUNK/install/data/coordinator1,pg_log)
+  (1 row)
+  ```
+
+- pg_catalog.plancache_clean()
+
+  描述：清理节点上无人使用的全局计划缓存。
+
+  返回值类型：bool
+
+- pg_catalog.plancache_status()
+
+  描述：显示节点上全局计划缓存的信息，函数返回信息和GLOBAL_PLANCACHE_STATUS一致。
+
+  返回值类型：record
+
+- textlen(text)
+
+  描述：提供查询text的逻辑长度的方法。
+
+  返回值类型：int
+
+- threadpool_status()
+
+  描述：显示线程池中工作线程及会话的状态信息。
+
+  返回值类型：record
+
+- get_local_active_session()
+
+  描述：提供当前节点保存在内存中的历史活跃session状态的采样记录。
+
+  返回值类型：record
+
+- pg_stat_get_thread()
+
+    描述：提供当前节点下所有线程的状态信息，sysadmin和monitor admin用户可以查看所有线程信息，普通用户查看本用户的线程信息。
+
+    返回值类型：record
+
+- pg_stat_get_sql_count()
+
+    描述：提供当前节点中用户执行的SELECT/UPDATE/INSERT/DELETE/MERGE INTO语句的计数结果，sysadmin和monitor admin用户可以查看所有用户的信息，普通用户查看本用户的统计信息。
+
+    返回值类型：record
+
+- pg_stat_get_data_senders()
+
+  描述：提供当前活跃的数据复制发送线程的详细信息。
+
+  返回值类型：record
+
+- get_wait_event_info()
+
+    描述：提供wait event事件的具体信息。
+
+    返回值类型：record
+
+- generate_wdr_report(begin_snap_id bigint, end_snap_id bigint, report_type cstring, report_scope cstring, node_name cstring)
+
+  描述：基于两个snapshot生成系统诊断报告。需要在postgres库下执行，默认初始化用户或monadmin用户可以访问，V500R001C20SPC002及其之前的版本初始化用户或sysadmin用户可以访问。只可在系统库中查询到结果，用户库中无法查询。
+
+  返回值类型：record
+
+  **表 1** generate_wdr_report 参数说明
+
+  | 参数          | 说明                                                         | 取值范围                                        |
+  | ------------- | ------------------------------------------------------------ | ----------------------------------------------- |
+  | begin_snap_id | 生成某段时间内性能诊断报告的开始snapshotid。                 | -                                               |
+  | end_snap_id   | 结束snapshot的id，默认end_snap_id大于begin_snap_id。         | -                                               |
+  | report_type   | 指定生成report的类型。                                       | summarydetailall，即同时包含summary 和 detail。 |
+  | report_scope  | 指定生成report的范围。                                       | cluster：数据库级别的信息node：节点级别的信息   |
+  | node_name     | 在report_scope指定为node时，需要把该参数指定为对应节点的名称。（节点名称可以执行select * from pg_node_env;查询）。在report_scope为cluster时，该值可以省略或者指定为空或NULL。 | cluster：省略/空/NULLnode： MogDB中的节点名称   |
+
+- create_wdr_snapshot()
+
+  描述：手工生成系统诊断快照，该函数需要sysadmin权限。
+
+  返回值类型：text
+
+- kill_snapshot()
+
+    描述：kill后台的WDR snapshot线程，调用该函数的用户需要具有SYSADMIN权限或具有REPLICATION权限或继承了内置角色gs_role_replication的权限。
+
+    返回值类型：void
+
+- capture_view_to_json(text,integer)
+
+    描述：将视图的结果存入GUC: perf_directory所指定的目录，如果is_crossdb为1，则表示对于所有的database都会访问一次view；如果is_crossdb为0，则表示仅对当前database进行一次视图访问。该函数只有sysadmin和monitor admin用户可以执行。
+
+    返回值类型：int
+
+- reset_unique_sql
+
+  描述：用来清理数据库节点内存中的Unique SQL（需要sysadmin权限）。
+
+  返回值类型：bool
+
+  **表 2** reset_unique_sql参数说明
+
+  | 参数        | 类型 | 描述                                                         |
+  | :---------- | :--- | :----------------------------------------------------------- |
+  | scope       | text | 清理范围类型：'GLOBAL'：清理所有的节点，如果是'GLOBAL'，则只可以为主节点执行此函数。'LOCAL'：清理本节点。 |
+  | clean_type  | text | 'BY_USERID'：按用户ID来进行清理Unique SQL。'BY_CNID'：按主节点的ID来进行清理Unique SQL。'ALL'：全部清理。 |
+  | clean_value | int8 | 具体清理type对应的清理值。                                   |
+
+  > **须知：**
+  >
+  > - scope的取值GLOBAL和LOCAL针对分布式，对于MogDB而言两者意义相同，均表示清理本节点。
+  > - clean_type的值BY_CNID仅针对分布式，对于MogDB无效。
+
+- wdr_xdb_query(db_name_str text, query text)
+
+  描述：提供本地跨数据库执行query的能力。例如: 在连接到mogdb库时, 访问test库下的表。
+
+  ```sql
+  select col1 from wdr_xdb_query('dbname=test','select col1 from t1') as dd(col1 int);
+  ```
+
+  返回值类型：record
+
+- pg_wlm_jump_queue(pid int)
+
+  描述：调整任务到数据库主节点队列的最前端。
+
+  返回值类型：boolean
+
+  - true：成功。
+  - false：失败。
+
+- gs_wlm_switch_cgroup(pid int, cgroup text)
+
+  描述：调整作业的优先级到新控制组。
+
+  返回值类型：boolean
+
+  - true：成功。
+  - false：失败。
+
+- pv_session_memctx_detail(threadid tid, MemoryContextName text)
+
+  描述：将线程tid的MemoryContextName内存上下文信息记录到“$GAUSSLOG/pg_log/${node_name}/dumpmem”目录下的“threadid_timestamp.log”文件中。其中threadid可通过视图GS_SESSION_MEMORY_DETAIL中的sessid后获得。在正式发布的版本中仅接受MemoryContextName为空串（两个单引号表示输入为空串，即”）的输入，此时会记录所有的内存上下文信息，否则不会有任何操作。对供内部开发人员和测试人员调试用的DEBUG版本，可以指定需要统计的MemoryContextName，此时会将该Context所有的内存使用情况记录到指定文件。该函数需要管理员权限的用户才能执行。
+
+  返回值类型：boolean
+
+  - true：成功。
+  - false：失败。
+
+- pg_shared_memctx_detail(MemoryContextName text)
+
+  描述：将MemoryContextName内存上下文信息记录到“$GAUSSLOG/pg_log/${node_name}/dumpmem”目录下的“threadid_timestamp.log”文件中。该函数功能仅在DEBUG版本中供内部开发人员和测试人员调试使用，在正式发布版本中调用该函数不会有任何操作。该函数需要管理员权限的用户才能执行。
+
+  返回值类型：boolean
+
+  - true：成功。
+  - false：失败。
+
+- local_bgwriter_stat()
+
+  描述：显示本实例的bgwriter线程刷页信息，候选buffer链中页面个数，buffer淘汰信息。
+
+  返回值类型：record
+
+- local_candidate_stat()
+
+    描述：显示本实例的候选buffer链中页面个数，buffer淘汰信息，包含normal buffer pool和segment buffer pool。
+
+    返回值类型：record
+
+- local_ckpt_stat()
+
+  描述：显示本实例的检查点信息和各类日志刷页情况。
+
+  返回值类型：record
+
+- local_double_write_stat()
+
+  描述：显示本实例的双写文件的情况。
+
+  返回值类型：record
+
+- local_single_flush_dw_stat()
+
+  描述：显示本实例的单页面淘汰双写文件的情况。
+
+  返回值类型：record
+
+- local_pagewriter_stat()
+
+  描述：显示本实例的刷页信息和检查点信息。
+
+  返回值类型：record
+
+- local_redo_stat()
+
+  描述：显示本实例的备机的当前回放状态。
+
+  返回值类型：record
+
+  备注：返回的回放状态主要包括当前回放位置，回放最小恢复点位置等信息。
+
+- local_recovery_status()
+
+  描述：显示本实例的主机和备机的日志流控信息。
+
+  返回值类型：record
+
+- gs_wlm_node_recover(boolean isForce)
+
+  描述：获取当前内存中记录的TopSQL查询语句级别相关统计信息，当传入的参数不为0时，会将这部分信息从内存中清理掉。
+
+  返回值类型：record
+
+- gs_cgroup_map_ng_conf(group name)
+
+  描述：读取指定逻辑数据库的cgroup配置文件。
+
+  返回值类型：record
+
+- gs_wlm_switch_cgroup(sess_id int8, cgroup name)
+
+  描述：切换指定会话的控制组。
+
+  返回值类型：record
+
+- hdfs_fdw_handler()
+
+  描述：用于外表重写功能，定义外表时需要定义的函数。
+
+  返回值类型：record
+
+- hdfs_fdw_validator(text[], oid)
+
+  描述：用于外表重写功能，定义外表时需要定义的函数。
+
+  返回值类型：record
+
+- comm_client_info()
+
+  描述：用于查询单个节点活跃的客户端连接信息。
+
+  返回值类型：setof record
+
+- pg_sync_cstore_delta(text)
+
+  描述：同步指定列存表的delta表表结构，使其与列存表主表一致。
+
+  返回值类型：bigint
+
+- pg_sync_cstore_delta()
+
+  描述：同步所有列存表的delta表表结构，使其与列存表主表一致。
+
+  返回值类型：bigint
+
+- pg_get_flush_lsn()
+
+  描述：返回当前节点flush的xlog位置。
+
+  返回值类型：text
+
+- pg_get_sync_flush_lsn()
+
+  描述：返回当前节点多数派flush的xlog位置。
+
+  返回值类型：text
+
+- gs_create_log_tables()
+
+  描述：用于创建运行日志和性能日志的外表和视图。
+
+  返回值类型：void
+
+  示例：
+
+  ```sql
+  mogdb=# select gs_create_log_tables();
+   gs_create_log_tables
+  ----------------------
+
+  (1 row)
+  ```
+
+- dbe_perf.get_global_full_sql_by_timestamp(start_timestamp timestamp with time zone, end_timestamp timestamp with time zone)
+
+  描述：获取数据库级的全量SQL(Full SQL)信息。只可在系统库中查询到结果，用户库中无法查询。
+
+  返回值类型：record
+
+  **表 3** dbe_perf.get_global_full_sql_by_timestamp参数说明
+
+  | 参数            | 类型                     | 描述                          |
+  | :-------------- | :----------------------- | :---------------------------- |
+  | start_timestamp | timestamp with time zone | SQL启动时间范围的开始时间点。 |
+  | end_timestamp   | timestamp with time zone | SQL启动时间范围的结束时间点。 |
+
+- dbe_perf.get_global_slow_sql_by_timestamp(start_timestamp timestamp with time zone, end_timestamp timestamp with time zone)
+
+  描述：获取数据库级的慢SQL(Slow SQL)信息。只可在系统库中查询到结果，用户库中无法查询。
+
+  返回值类型：record
+
+  **表 4** dbe_perf.get_global_slow_sql_by_timestamp参数说明
+
+  | 参数            | 类型                     | 描述                          |
+  | :-------------- | :----------------------- | :---------------------------- |
+  | start_timestamp | timestamp with time zone | SQL启动时间范围的开始时间点。 |
+  | end_timestamp   | timestamp with time zone | SQL启动时间范围的结束时间点。 |
+
+- statement_detail_decode(detail text, format text, pretty boolean)
+
+  描述：解析全量/慢SQL语句中的details字段的信息。只可在系统库中查询到结果，用户库中无法查询。
+
+  返回值类型：text
+
+  **表 5** statement_detail_decode参数说明
+
+  | 参数   | 类型    | 描述                                                         |
+  | :----- | :------ | :----------------------------------------------------------- |
+  | detail | text    | SQL语句产生的事件的集合（不可读）。                          |
+  | format | text    | 解析输出格式，取值为 plaintext。                             |
+  | pretty | boolean | 当format为plaintext时，是否以优雅的格式展示：true表示通过“\n”分隔事。false表示通过“，”分隔事件。 |
+
+- get_prepared_pending_xid
+
+    描述：当恢复完成时，返回nextxid。
+
+    参数：nan
+
+    返回值类型：text
+
+- pg_clean_region_info
+
+    描述：清理regionmap。
+
+    参数：nan
+
+    返回值类型：character varying
+
+- pg_get_delta_info
+
+    描述：从单个dn获取delta info。
+
+    参数：rel text, schema_name text
+
+    返回值类型：part_name text, live_tuple bigint, data_size bigint, blocknum bigint
+
+- pg_get_replication_slot_name
+
+    描述：获取slot name。
+
+    参数：nan
+
+    返回值类型：text
+
+- pg_get_running_xacts
+
+    描述：获取运行中的xact。
+
+    参数：nan
+
+    返回值类型：handle integer, gxid xid, state tinyint, node text, xmin xid, vacuum boolean, timeline bigint, prepare_xid xid, pid bigint, next_xid xid
+
+- pg_get_variable_info
+
+    描述：获取共享内存变量cache。
+
+    参数：nan
+
+    返回值类型：node_name text, nextOid oid, nextXid xid, oldestXid xid, xidVacLimit xid, oldestXidDB oid, lastExtendCSNLogpage xid, startExtendCSNLogpage xid, nextCommitSeqNo xid, latestCompletedXid xid, startupMaxXid xid
+
+- pg_get_xidlimit
+
+    描述：从共享内存获取事物id信息。
+
+    参数：nan
+
+    返回值类型：nextXid xid, oldestXid xid, xidVacLimit xid, xidWarnLimit xid, xidStopLimit xid, xidWrapLimit xid, oldestXidDB oid
+
+- get_global_user_transaction()
+
+  描述：返回所有节点上各用户的事务相关信息。
+
+  返回值类型：node_name name, usename name, commit_counter bigint, rollback_counter bigint, resp_min bigint, resp_max bigint, resp_avg bigint, resp_total bigint, bg_commit_counter bigint, bg_rollback_counter bigint, bg_resp_min bigint, bg_resp_max bigint, bg_resp_avg bigint, bg_resp_total bigint
+
+- pg_collation_for
+
+  描述：返回入参字符串对应的排序规则。
+
+  参数：any（如果是常量必须进行显式类型转换）
+
+  返回值类型：text
+
+- pgxc_unlock_for_sp_database(name Name)
+
+  描述：释放指定数据库锁。
+
+  参数：数据库名
+
+  返回值类型：布尔
+
+- pgxc_lock_for_sp_database(name Name)
+
+  描述：对指定的数据库加锁。
+
+  参数：数据库名
+
+  返回值类型：布尔
+
+- copy_error_log_create()
+
+  描述：创建COPY FROM容错机制所需要的错误表（public.pgxc_copy_error_log）。
+
+  返回值类型：Boolean
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  >
+  > - 此函数会尝试创建public.pgxc_copy_error_log表，表的详细信息请参见表6。
+  > - 在relname列上创建B-tree索引，并REVOKE ALL on public.pgxc_copy_error_log FROM public对错误表进行权限控制（与COPY语句权限一致）。
+  > - 由于尝试创建的public.pgxc_copy_error_log定义是一张行存表，因此数据库实例上必须支持行存表的创建才能够正常运行此函数，并使用后续的COPY容错功能。需要特别注意的是，enable_hadoop_env这个GUC参数开启后会禁止在数据库实例内创建行存表（MogDB默认为off）。
+  > - 此函数自身权限为Sysadmin及以上（与错误表、COPY权限一致）。
+  > - 若创建前public.pgxc_copy_error_log表已存在或者copy_error_log_relname_idx索引已存在，则此函数会报错回滚。
+
+  **表 6** 错误表public.pgxc_copy_error_log信息 <a id="cuowubiao"></a>
+
+  | 列名称    | 类型                     | 描述                                         |
+  | :-------- | :----------------------- | :------------------------------------------- |
+  | relname   | character varying        | 表名称。以模式名.表名形式显示。              |
+  | begintime | timestamp with time zone | 出现数据格式错误的时间。                     |
+  | filename  | character varying        | 出现数据格式错误的数据源文件名。             |
+  | lineno    | bigint                   | 在数据源文件中，出现数据格式错误的行号。     |
+  | rawrecord | text                     | 在数据源文件中，出现数据格式错误的原始记录。 |
+  | detail    | text                     | 详细错误信息。                               |
+
+- gs_comm_proxy_thread_status()
+
+    描述：用于在集群配置用户态网络的场景下，代理通信库comm_proxy收发数据包统计
+
+    参数：nan
+
+    返回值类型：record
+
+    >**说明：**
+    >
+    >- 此函数的查询仅在集中式环境开始部署用户态网络，且comm_proxy_attr参数中enable_dfx配置为true的条件下显示具体信息。其他场景报错不支持查询。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/9.1-segment-page-storage-functions.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/9.1-segment-page-storage-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..4ce182eb41abcadd3ee2c428c6ba3f167fe99e53
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/24-system-management-functions/9.1-segment-page-storage-functions.md
@@ -0,0 +1,113 @@
+---
+title: 段页式存储函数
+summary: 段页式存储函数
+author: Guo Huan
+date: 2021-10-28
+---
+
+# 段页式存储函数
+
+- local_segment_space_info(tablespacename TEXT, databasename TEXT)
+
+  描述：输出为该表空间下所有ExtentGroup的使用信息。
+
+  返回值类型：
+
+  | node_name        | 节点名称。                                                   |
+  | ---------------- | ------------------------------------------------------------ |
+  | extent_size      | 该ExtentGroup的extent规格，单位是block数。                   |
+  | forknum          | Fork号。                                                     |
+  | total_blocks     | 物理文件总extent数目。                                       |
+  | meta_data_blocks | 表空间管理的metadata占用的block数，只包括space header，map page等，不包括segment head。 |
+  | used_data_blocks | 存数据占用的extent数目。包括segment head。                   |
+  | utilization      | 使用的block数占总block数的百分比。即(used_data_blocks+meta_data_block)/total_blocks。 |
+  | high_water_mark  | 高水位线，被分配出去的extent，最大的物理页号。超过高水位线的block都没有被使用，可以被直接回收。 |
+
+  例如：
+
+  ```sql
+  select * from local_segment_space_info('pg_default', 'postgres');
+       node_name     | extent_size | forknum | total_blocks | meta_data_blocks | used_data_blocks | utilization | high_water_mark
+  -------------------+-------------+---------+--------------+------------------+------------------+-------------+-----------------
+   dn_6001_6002_6003 |           1 |       0 |        16384 |             4157 |                1 |     .253784 |            4158
+   dn_6001_6002_6003 |           8 |       0 |        16384 |             4157 |                8 |     .254211 |            4165
+  (2 rows)
+  ```
+
+- pg_stat_segment_extent_usage(int4 tablespace oid, int4 database oid, int4 extent_type, int4 forknum)
+
+  描述：每次返回一个ExtentGroup中，每个被分配出去的extent的使用情况。extent_type表示ExtentGroup的类型，合理取值为[1,5]的int值。在此范围外的会报error。forknum 表示fork号，合法取值为[0,4]的int值，目前只有三种值有效，数据文件为0，FSM文件为1，visibility map文件为2。
+
+  返回值类型：
+
+  | 名称          | 描述                                                         |
+  | :------------ | :----------------------------------------------------------- |
+  | start_block   | Extent的起始物理页号。                                       |
+  | extent_size   | Extent的大小。                                               |
+  | usage_type    | Extent的使用类型，比如segment head，data extent等。          |
+  | ower_location | 有指针指向该extent的对象的位置。比如data extent的owner就是它所属的segment的head位置。 |
+  | special_data  | 该extent在它owner中的位置。该字段的数据跟使用类型有关。比如data extent的special data就是它在所属segment中的extent id。 |
+
+  其中，usage_type为枚举类型，每一项的含义为：
+
+  - Non-bucket table segment head ： 非hashbucket表的数据段头。
+  - Non-bucket table fork head： 非段页式表的fork段头。
+  - Data extent： 数据块。
+
+  例如：
+
+  ```sql
+  select * from pg_stat_segment_extent_usage((select oid::int4 from pg_tablespace where spcname='pg_default'), (select oid::int4 from pg_database where datname='postgres'), 1, 0);
+  start_block | extent_size |       usage_type       | ower_location | special_data
+  -------------+-------------+------------------------+---------------+--------------
+  4157 |           1 | Data extent |    4294967295 |            0
+  4158 |           1 | Data extent |          4157 |            0
+  ```
+
+- local_space_shrink(tablespacename TEXT, databasename TEXT)
+
+  描述：当前节点上对指定段页式空间做物理空间压缩。注意，目前只支持对当前连接的database做shrink。
+
+  返回值：空
+
+- gs_space_shrink(int4 tablespace, int4 database, int4 extent_type, int4 forknum)
+
+  描述：效果跟local_space_shrink类似，对指定段页式空间做物理空间压缩,但参数不同，传入的是tablespace和database的oid，extent_type为[2,5]的int值。注意：extent_type = 1表示段页式元数据，目前不支持对元数据所在的物理文件做压缩。该函数仅限工具使用，不建议用户直接使用。
+
+  返回值：空
+
+- pg_stat_remain_segment_info()
+
+  描述：展示在当前节点上，因为故障等原因而残留的extent。残留extent主要分为两类：分配而未被利用的segment和分配出去而未被利用的extent。两者主要区别在于segment会包含多个extent，回收时，要将segment上的extent一并全部回收。
+
+  返回值类型：
+
+  | 名称     | 描述                                                         |
+  | -------- | ------------------------------------------------------------ |
+  | space_id | 表空间ID                                                     |
+  | db_id    | 数据库ID                                                     |
+  | block_id | Extent的ID                                                   |
+  | type     | Extent的类型，当前有三种：ALLOC_SEGMENT\|DROP_SEGMENT\|SHRINK_EXTENT |
+
+  其中type的三种类型分别表示：
+
+  - ALLOC_SEGMENT:用户创建一张段页式表，当segment刚被分配，但是建表语句所在事务仍未提交时，节点故障，导致该segment被分配后，没有被使用。
+
+  - DROP_SEGMENT:用户删除段页式表，当该事务成功提交，但是此表的segment页面对应的bit位未被重置，就发生掉电等故障，造成该segment未被使用，也未被释放。
+
+  - SHRINK_EXTENT:用户对段页式表执行shrink操作，在未对空置出的extent进行释放时，发生掉电等故障，造成该extent残留，无法被重新利用。
+
+    例如：
+
+    ```sql
+    select * from pg_stat_remain_segment_info();
+    space_id | db_id | block_id | type
+    ----------+-------+----------+------
+    1663       |   16385|        4156| ALLOC_SEGMENT
+    ```
+
+- pg_free_remain_segment(int4 spaceId, int4 dbId, int4 segmentId)
+
+  描述：释放指定的残留extent。参数取值必须为从函数pg_stat_remain_segment_info中查询获取。函数会对传入值校验，如果指定extent不在记录的残留extent中，将返回错误信息。指定的extent如果为单个extent，则只将其独自释放；如果为一个segment，则会将此segment以及此segment上记录的所有extent释放。
+
+  返回值：空
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/25-statistics-information-functions.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/25-statistics-information-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..10978bc94399aac0d0c79f850c4e690f635a7855
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/25-statistics-information-functions.md
@@ -0,0 +1,1777 @@
+---
+title: 统计信息函数
+summary: 统计信息函数
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 统计信息函数
+
+统计信息函数根据访问对象分为两种类型：针对某个数据库进行访问的函数，以数据库中每个表或索引的OID作为参数，标识需要报告的数据库；针对某个服务器进行访问的函数，以一个服务器进程号为参数，其范围从1到当前活跃服务器的数目。
+
+- global_comm_get_status()
+
+  描述：获取所有DN节点的通信库状态。
+
+  返回值类型：record
+
+- global_comm_get_send_stream()
+
+  描述：获取所有DN节点上所有的通信库发送流状态。
+
+  返回值类型：record
+
+- global_comm_get_recv_stream()
+
+  描述：获取所有DN节点上所有的通信库接收流状态。
+
+  返回值类型：record
+
+- global_comm_get_client_info()
+
+  描述：获取全局节点客户端连接信息。
+
+  返回值类型：record
+
+- pg_stat_get_db_conflict_tablespace(oid)
+
+  描述：由于恢复与数据库中删除的表空间发生冲突而取消的查询数。
+
+  返回值类型：bigint
+
+- pg_control_group_config
+
+  描述：在当前节点上打印cgroup配置。
+
+  返回值类型：record
+
+- pg_stat_get_db_stat_reset_time(oid)
+
+  描述：上次重置数据库统计信息的时间。首次连接到每个数据库期间初始化为系统时间。当您在数据库上调用pg_stat_reset以及针对其中的任何表或索引执行pg_stat_reset_single_table_counters时，重置时间都会更新。
+
+  返回值类型：timestamptz
+
+- pg_stat_get_function_total_time(oid)
+
+  描述：该函数花费的总挂钟时间，以微秒为单位。包括花费在此函数调用其它函数上的时间。
+
+  返回值类型：bigint
+
+- pg_stat_get_xact_tuples_returned(oid)
+
+  描述：当前事务中参数为表时通过顺序扫描读取的行数，或参数为索引时返回的索引条目数。
+
+  返回值类型：bigint
+
+- pg_stat_get_xact_numscans(oid)
+
+  描述：当前事务中参数为表时执行的顺序扫描次数，或参数为索引时执行的索引扫描次数。
+
+  返回值类型：bigint
+
+- pg_stat_get_xact_blocks_fetched(oid)
+
+  描述：当前事务中对表或索引的磁盘块获取请求数。
+
+  返回值类型：bigint
+
+- pg_stat_get_xact_blocks_hit(oid)
+
+  描述：当前事务中对缓存中找到的表或索引的磁盘块获取请求数。
+
+  返回值类型：bigint
+
+- pg_stat_get_xact_function_calls(oid)
+
+  描述：在当前事务中调用该函数的次数。
+
+  返回值类型：bigint
+
+- pg_stat_get_xact_function_self_time(oid)
+
+  描述：在当前事务中仅花费在此函数上的时间，不包括花费在此函数内部调用其它函数上的时间。
+
+  返回值类型：bigint
+
+- pg_stat_get_xact_function_total_time(oid)
+
+  描述：当前事务中该函数所花费的总挂钟时间（以微秒为单位），包括花费在此函数内部调用其它函数上的时间。
+
+  返回值类型：bigint
+
+- pg_stat_get_wal_senders()
+
+  描述：在主机端查询walsender信息。
+
+  返回值类型：setofrecord
+
+  返回字段说明如下：
+
+  **表 1** 返回字段说明
+
+  | 字段名称                   | 字段类型                 | 字段说明                           |
+  | :------------------------- | :----------------------- | :--------------------------------- |
+  | pid                        | bigint                   | walsender的线程号。                |
+  | sender_pid                 | integer                  | walsender的pid相对的轻量级线程号。 |
+  | local_role                 | text                     | 主节点类型。                       |
+  | peer_role                  | text                     | 备节点类型。                       |
+  | peer_state                 | text                     | 备节点状态。                       |
+  | state                      | text                     | walsender状态。                    |
+  | catchup_start              | timestamp with time zone | catchup启动时间。                  |
+  | catchup_end                | timestamp with time zone | catchup结束时间。                  |
+  | sender_sent_location       | text                     | 主节点发送位置。                   |
+  | sender_write_location      | text                     | 主节点落盘位置。                   |
+  | sender_flush_location      | text                     | 主节点flush磁盘位置。              |
+  | sender_replay_location     | text                     | 主节点redo位置。                   |
+  | receiver_received_location | text                     | 备节点接收位置。                   |
+  | receiver_write_location    | text                     | 备节点落盘位置。                   |
+  | receiver_flush_location    | text                     | 备节点flush磁盘位置。              |
+  | receiver_replay_location   | text                     | 备节点redo磁盘位置。               |
+  | sync_percent               | text                     | 同步百分比。                       |
+  | sync_state                 | text                     | 同步状态。                         |
+  | sync_priority              | text                     | 同步复制的优先级。                 |
+  | sync_most_available        | text                     | 最大可用模式设置。                 |
+  | channel                    | text                     | walsender信道信息。                |
+
+- get_paxos_replication_info()
+
+  描述：查询Paxos模式下主机或备机的复制状态。
+
+  返回值类型：setofrecord
+
+  返回字段说明如下：
+
+  **表 2** 返回字段说明
+
+  | 字段名称              | 字段类型 | 字段说明                        |
+  | :-------------------- | :------- | :------------------------------ |
+  | paxos_write_location  | text     | 已经写入DCF的XLog位置。         |
+  | paxos_commit_location | text     | 已经在DCF中达成一致的XLog位置。 |
+  | local_write_location  | text     | 节点的落盘位置。                |
+  | local_flush_location  | text     | 节点的flush磁盘位置。           |
+  | local_replay_location | text     | 节点的redo磁盘位置。            |
+  | dcf_replication_info  | text     | 节点的DCF模块信息。             |
+
+- pg_stat_get_stream_replications()
+
+  描述：查询主备复制状态。
+
+  返回值类型：setofrecord
+
+  返回值说明如下。
+
+  **表 3** 返回值说明
+
+  | 返回参数           | 返回参数类型 | 返回参数说明 |
+  | :----------------- | :----------- | :----------- |
+  | local_role         | text         | 本地角色。   |
+  | static_connections | integer      | 连接统计。   |
+  | db_state           | text         | 数据库状态。 |
+  | detail_information | text         | 详细信息。   |
+
+- pg_stat_get_db_numbackends(oid)
+
+  描述：处理该数据库活跃的服务器进程数目。
+
+  返回值类型：integer
+
+- pg_stat_get_db_xact_commit(oid)
+
+  描述：数据库中已提交事务的数量。
+
+  返回值类型：bigint
+
+- pg_stat_get_db_xact_rollback(oid)
+
+  描述：数据库中回滚事务的数量。
+
+  返回值类型：bigint
+
+- pg_stat_get_db_blocks_fetched(oid)
+
+  描述：数据库中磁盘块抓取请求的总数。
+
+  返回值类型：bigint
+
+- pg_stat_get_db_blocks_hit(oid)
+
+  描述：数据库在缓冲区中找到的磁盘块抓取请求的总数。
+
+  返回值类型：bigint
+
+- pg_stat_get_db_tuples_returned(oid)
+
+  描述：为数据库返回的Tuple数。
+
+  返回值类型：bigint
+
+- pg_stat_get_db_tuples_fetched(oid)
+
+  描述：为数据库中获取的Tuple数。
+
+  返回值类型：bigint
+
+- pg_stat_get_db_tuples_inserted(oid)
+
+  描述：在数据库中插入Tuple数。
+
+  返回值类型：bigint
+
+- pg_stat_get_db_tuples_updated(oid)
+
+  描述：在数据库中更新的Tuple数。
+
+  返回值类型：bigint
+
+- pg_stat_get_db_tuples_deleted(oid)
+
+  描述：数据库中删除Tuple数。
+
+  返回值类型：bigint
+
+- pg_stat_get_db_conflict_lock(oid)
+
+  描述：数据库中锁冲突的数量。
+
+  返回值类型：bigint
+
+- pg_stat_get_db_deadlocks(oid)
+
+  描述：数据库中死锁的数量。
+
+  返回值类型：bigint
+
+- pg_stat_get_numscans(oid)
+
+  描述：如果参数是一个表，则顺序扫描读取的行数目。如果参数是一个索引，则返回索引行的数目。
+
+  返回值类型：bigint
+
+- pg_stat_get_role_name(oid)
+
+  描述：根据用户oid获取用户名。仅sysadmin和monitor admin用户可以访问。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# select pg_stat_get_role_name(10);
+   pg_stat_get_role_name
+  -----------------------
+   aabbcc
+  (1 row)
+  ```
+
+- pg_stat_get_tuples_returned(oid)
+
+  描述：如果参数是一个表，则顺序扫描读取的行数目。如果参数是一个索引，则返回的索引行的数目。
+
+  返回值类型：bigint
+
+- pg_stat_get_tuples_fetched(oid)
+
+  描述：如果参数是一个表，则位图扫描抓取的行数目。如果参数是一个索引，则用简单索引扫描抓取的行数目。
+
+  返回值类型：bigint
+
+- pg_stat_get_tuples_inserted(oid)
+
+  描述：插入表中行的数量。
+
+  返回值类型：bigint
+
+- pg_stat_get_tuples_updated(oid)
+
+  描述：在表中已更新行的数量。
+
+  返回值类型：bigint
+
+- pg_stat_get_tuples_deleted(oid)
+
+  描述：从表中删除行的数量。
+
+  返回值类型：bigint
+
+- pg_stat_get_tuples_changed(oid)
+
+  描述：该表上一次analyze或autoanalyze之后插入、更新、删除行的总数量。
+
+  返回值类型：bigint
+
+- pg_stat_get_tuples_hot_updated(oid)
+
+  描述：表热更新的行数。
+
+  返回值类型：bigint
+
+- pg_stat_get_live_tuples(oid)
+
+  描述：表活行数。
+
+  返回值类型：bigint
+
+- pg_stat_get_dead_tuples(oid)
+
+  描述：表死行数。
+
+  返回值类型：bigint
+
+- pg_stat_get_blocks_fetched(oid)
+
+  描述：表或者索引的磁盘块抓取请求的数量。
+
+  返回值类型：bigint
+
+- pg_stat_get_blocks_hit(oid)
+
+  描述：在缓冲区中找到的表或者索引的磁盘块请求数目。
+
+  返回值类型：bigint
+
+- pg_stat_get_partition_tuples_inserted(oid)
+
+  描述：插入相应表分区中行的数量。
+
+  返回值类型：bigint
+
+- pg_stat_get_partition_tuples_updated(oid)
+
+  描述：在相应表分区中已更新行的数量。
+
+  返回值类型：bigint
+
+- pg_stat_get_partition_tuples_deleted(oid)
+
+  描述：从相应表分区中删除行的数量。
+
+  返回值类型：bigint
+
+- pg_stat_get_partition_tuples_changed(oid)
+
+  描述：该表分区上一次analyze或autoanalyze之后插入、更新、删除行的总数量。
+
+  返回值类型：bigint
+
+- pg_stat_get_partition_live_tuples(oid)
+
+  描述：分区表活行数。
+
+  返回值类型：bigint
+
+- pg_stat_get_partition_dead_tuples(oid)
+
+  描述：分区表死行数。
+
+  返回值类型：bigint
+
+- pg_stat_get_xact_tuples_fetched(oid)
+
+  描述：事务中扫描的tuple行数。
+
+  返回值类型：bigint
+
+- pg_stat_get_xact_tuples_inserted(oid)
+
+  描述：表相关的活跃子事务中插入的tuple数。
+
+  返回值类型：bigint
+
+- pg_stat_get_xact_tuples_deleted(oid)
+
+  描述：表相关的活跃子事务中删除的tuple数。
+
+  返回值类型：bigint
+
+- pg_stat_get_xact_tuples_hot_updated(oid)
+
+  描述：表相关的活跃子事务中热更新的tuple数。
+
+  返回值类型：bigint
+
+- pg_stat_get_xact_tuples_updated(oid)
+
+  描述：表相关的活跃子事务中更新的tuple数。
+
+  返回值类型：bigint
+
+- pg_stat_get_xact_partition_tuples_inserted(oid)
+
+  描述：表分区相关的活跃子事务中插入的tuple数。
+
+  返回值类型：bigint
+
+- pg_stat_get_xact_partition_tuples_deleted(oid)
+
+  描述：表分区相关的活跃子事务中删除的tuple数。
+
+  返回值类型：bigint
+
+- pg_stat_get_xact_partition_tuples_hot_updated(oid)
+
+  描述：表分区相关的活跃子事务中热更新的tuple数。
+
+  返回值类型：bigint
+
+- pg_stat_get_xact_partition_tuples_updated(oid)
+
+  描述：表分区相关的活跃子事务中更新的tuple数。
+
+  返回值类型：bigint
+
+- pg_stat_get_last_vacuum_time(oid)
+
+  描述：用户在该表上最后一次手动启动清理或者autovacuum线程启动清理的时间。
+
+  返回值类型：timestamptz
+
+- pg_stat_get_last_autovacuum_time(oid)
+
+  描述：autovacuum守护进程在该表上最后一次启动清理的时间。
+
+  返回值类型：timestamptz
+
+- pg_stat_get_vacuum_count(oid)
+
+  描述：用户在该表上启动清理的次数。
+
+  返回值类型：bigint
+
+- pg_stat_get_autovacuum_count(oid)
+
+  描述：autovacuum守护进程在该表上启动清理的次数。
+
+  返回值类型：bigint
+
+- pg_stat_get_last_analyze_time(oid)
+
+  描述：用户在该表上最后一次手动启动分析或者autovacuum线程启动分析的时间。
+
+  返回值类型：timestamptz
+
+- pg_stat_get_last_autoanalyze_time(oid)
+
+  描述：autovacuum守护进程在该表上最后一次启动分析的时间。
+
+  返回值类型：timestamptz
+
+- pg_stat_get_analyze_count(oid)
+
+  描述：用户在该表上启动分析的次数。
+
+  返回值类型：bigint
+
+- pg_stat_get_autoanalyze_count(oid)
+
+  描述：autovacuum守护进程在该表上启动分析的次数。
+
+  返回值类型：bigint
+
+- pg_total_autovac_tuples(bool,bool)
+
+  描述：返回total autovac相关的tuple记录，如nodename、nspname、relname以及各类tuple的IUD信息，入参分别为：是否查询relation信息、是否查询local信息。
+
+  返回值类型：setofrecord
+
+  返回参数说明如下。
+
+  **表 4** 返回参数说明
+
+  | 返回参数              | 返回参数类型 | 返回参数说明               |
+  | :-------------------- | :----------- | :------------------------- |
+  | nodename              | name         | 节点名称。                 |
+  | nspname               | name         | 名称空间名称。             |
+  | relname               | name         | 表、索引、视图等对象名称。 |
+  | partname              | name         | 分区名称。                 |
+  | n_dead_tuples         | bigint       | 表分区内的死行数。         |
+  | n_live_tuples         | bigint       | 表分区内的活行数。         |
+  | changes_since_analyze | bigint       | analyze产生改变的数量。    |
+
+- pg_autovac_status(oid)
+
+  描述：返回和autovac状态相关的参数信息，如nodename、nspname、relname、analyze、vacuum设置，analyze/vacuum阈值, analyze/vacuum tuple数等。仅sysadmin可以使用该函数。
+
+  返回值类型：setofrecord
+
+  返回值参数说明如下。
+
+  **表 5** 返回值参数说明
+
+  | 返回参数  | 返回参数类型 | 返回参数说明               |
+  | :-------- | :----------- | :------------------------- |
+  | nspname   | text         | 名称空间名称。             |
+  | relname   | text         | 表、索引、视图等对象名称。 |
+  | nodename  | text         | 节点名称。                 |
+  | doanalyze | Boolean      | 是否执行analyze。          |
+  | anltuples | bigint       | analyze tuple数量。        |
+  | anlthresh | bigint       | analyze阈值。              |
+  | dovacuum  | Boolean      | 是否执行vacuum。           |
+  | vactuples | bigint       | vacuum tuple数量。         |
+  | vacthresh | bigint       | vacuum阈值。               |
+
+- pg_autovac_timeout(oid)
+
+  描述：返回某个表做autovac连续超时的次数，表信息非法或node信息异常返回NULL。
+
+  返回值类型：bigint
+
+- pg_stat_get_last_data_changed_time(oid)
+
+  描述：insert/update/delete, exchange/truncate/drop partition在该表上最后一次操作的时间，PG_STAT_ALL_TABLES视图last_data_changed列的数据是通过该函数求值，在表数量很大的场景中，通过视图获取表数据最后修改时间的性能较差，建议直接使用该函数获取表数据的最后修改时间。
+
+  返回值类型：timestamptz
+
+- pg_stat_set_last_data_changed_time(oid)
+
+  描述：手动设置该表上最后一次insert/update/delete, exchange/truncate/drop partition操作的时间。
+
+  返回值类型：void
+
+- pg_backend_pid()
+
+  描述：当前会话的服务器线程的线程ID。
+
+  返回值类型：integer
+
+- pg_stat_get_activity(integer)
+
+  描述：返回一个关于带有特殊PID的后台进程的记录信息，当参数为NULL时，则返回每个活动的后台进程的记录。返回结果是PG_STAT_ACTIVITY视图中的一个子集，不包含connection_info列。
+
+  示例：
+
+  ```sql
+  mogdb=# select * from pg_stat_get_activity(139754904483584);
+   datid |       pid       |    sessionid    | usesysid | application_name | state |                    query                     | waiting | xact_start |          query_start          |         backend_start         |         state_cha
+  nge          | client_addr | client_hostname | client_port | enqueue | query_id | srespool | global_sessionid
+  -------+-----------------+-----------------+----------+------------------+-------+----------------------------------------------+---------+------------+-------------------------------+-------------------------------+------------------
+  -------------+-------------+-----------------+-------------+---------+----------+----------+------------------
+   16099 | 139754904483584 | 139754904483584 |       10 | coordinator2     | idle  | SET SESSION AUTHORIZATION DEFAULT;RESET ALL; | f       |            | 2021-06-09 16:40:58.391727+08 | 2021-06-09 16:03:52.040929+08 | 2021-06-09 16:40:
+  58.392143+08 | ::1         |                 |       35210 |         |        0 | unknown  | 0#0#0
+  (1 row)
+  ```
+
+  返回值类型：setofrecord
+
+  返回参数说明如下。
+
+  **表 6** 返回参数说明
+
+  | 返回参数         | 返回参数类型             | 返回参数说明                                                 |
+  | :--------------- | :----------------------- | :----------------------------------------------------------- |
+  | datid            | oid                      | 用户会话在后台连接到的数据库OID。                            |
+  | pid              | bigint                   | 后台线程ID。                                                 |
+  | sessionid        | bigint                   | 会话ID。                                                     |
+  | usesysid         | oid                      | 登录该后台的用户名。                                         |
+  | application_name | text                     | 连接到该后台的应用名。                                       |
+  | state            | text                     | 该后台当前总体状态。                                         |
+  | query            | text                     | 该后台的最新查询。如果state状态是active（活跃的），此字段显示当前正在执行的查询。所有其他情况表示上一个查询。 |
+  | waiting          | Boolean                  | 如果后台当前正等待锁则为true。                               |
+  | xact_start       | timestamp with time zone | 启动当前事务的时间，如果没有事务是活跃的，则为null。如果当前查询是首个事务，则这列等同于query_start列。 |
+  | query_start      | timestamp with time zone | 开始当前活跃查询的时间，如果state的值不是active，则这个值是上一个查询的开始时间。 |
+  | backend_start    | timestamp with time zone | 该过程开始的时间，即当客户端连接服务器时。                   |
+  | state_change     | timestamp with time zone | 上次状态改变的时间。                                         |
+  | client_addr      | inet                     | 连接到该后台的客户端的IP地址。如果此字段是null，它表明通过服务器机器上UNIX套接字连接客户端或者这是内部进程，如autovacuum。 |
+  | client_hostname  | text                     | 客户端的主机名，这个字段是通过client_addr的反向DNS查找得到。这个字段只有在启动log_hostname且使用IP连接时才非空。 |
+  | client_port      | integer                  | 客户端用于与后台通讯的TCP端口号，如果使用Unix套接字，则为-1。 |
+  | enqueue          | text                     | 该字段暂不支持。                                             |
+  | query_id         | bigint                   | 查询语句的ID。                                               |
+  | global_sessionid | text                     | 全局会话id。                                                 |
+
+- pg_stat_get_activity_with_conninfo(integer)
+
+  描述：返回一个关于带有特殊PID的后台进程的记录信息，当参数为NULL时，则返回每个活动的后台进程的记录。PG_STAT_ACTIVITY视图是该函数的一个子集。
+
+  返回值类型：setofrecord
+
+  返回值说明如下。
+
+  **表 7** 返回值说明
+
+  | 返回值           | 返回值类型               | 返回值说明                                                   |
+  | :--------------- | :----------------------- | :----------------------------------------------------------- |
+  | datid            | oid                      | 用户会话在后台连接到的数据库OID。                            |
+  | pid              | bigint                   | 后台线程ID。                                                 |
+  | sessionid        | bigint                   | 会话ID。                                                     |
+  | usesysid         | oid                      | 登录该后台的用户名。                                         |
+  | application_name | text                     | 连接到该后台的应用名。                                       |
+  | state            | text                     | 改后台当前总体状态。                                         |
+  | query            | text                     | 该后台的最新查询。如果state状态是active（活跃的），此字段显示当前正在执行的查询。所有其他情况表示上一个查询。 |
+  | waiting          | Boolean                  | 如果后台当前正等待锁则为true                                 |
+  | xact_start       | timestamp with time zone | 启动当前事务的时间，如果没有事务是活跃的，则为null。如果当前查询是首个事务，则这列等同于query_start列。 |
+  | query_start      | timestamp with time zone | 开始当前活跃查询的时间，如果state的值不是active，则这个值是上一个查询的开始时间。 |
+  | backend_start    | timestamp with time zone | 该过程开始的时间，即当客户端连接服务器时。                   |
+  | state_change     | timestamp with time zone | 上次状态改变的时间。                                         |
+  | client_addr      | inet                     | 连接到该后台的客户端的IP地址。如果此字段是null，它表明通过服务器机器上UNIX套接字连接客户端或者这是内部进程，如autovacuum |
+  | client_hostname  | text                     | 客户端的主机名，这个字段是通过client_addr的反向DNS查找得到。这个字段只有在启动log_hostname且使用IP连接时才非空。 |
+  | client_port      | integer                  | 客户端用于与后台通讯的TCP端口号，如果使用Unix套接字，则为-1。 |
+  | enqueue          | text                     | 该字段暂不支持。                                             |
+  | query_id         | bigint                   | 查询语句的ID。                                               |
+  | connection_info  | text                     | json格式字符串，记录当前连接数据库的驱动类型、驱动版本号、当前驱动的部署路径、进程属主用户等信息。 |
+  | global_sessionid | text                     | 全局会话ID。                                                 |
+
+- pg_user_iostat(text)
+
+  描述：显示和当前用户执行作业正在运行时的IO负载管理相关信息。
+
+  返回值类型：record
+
+  函数返回字段说明如下：
+
+  | 名称           | 类型 | 描述                                                         |
+  | :------------- | :--- | :----------------------------------------------------------- |
+  | userid         | oid  | 用户id。                                                     |
+  | min_curr_iops  | int4 | 当前该用户io在数据库节点中的最小值。对于行存，以万次/s为单位；对于列存，以次/s为单位。 |
+  | max_curr_iops  | int4 | 当前该用户io在数据库节点中的最大值。对于行存，以万次/s为单位；对于列存，以次/s为单位。 |
+  | min_peak_iops  | int4 | 该用户io峰值中，数据库节点的最小值。对于行存，以万次/s为单位；对于列存，以次/s为单位。 |
+  | max_peak_iops  | int4 | 该用户io峰值中，数据库节点的最大值。对于行存，以万次/s为单位；对于列存，以次/s为单位。 |
+  | io_limits      | int4 | 用户指定的资源池所设置的io_limits。对于行存，以万次/s为单位；对于列存，以次/s为单位。 |
+  | io_priority    | text | 该用户所设io_priority。对于行存，以万次/s为单位；对于列存，以次/s为单位。 |
+  | curr_io_limits | int4 | 使用io_priority管控io时的实时io_limits值。                   |
+
+- pg_stat_get_function_calls(oid)
+
+  描述：函数已被调用次数。
+
+  返回值类型：bigint
+
+- pg_stat_get_function_self_time(oid)
+
+  描述：只有在此函数上所花费的时间。此函数调用其它函数上花费的时间被排除在外。
+
+  返回值类型：bigint
+
+- pg_stat_get_backend_idset()
+
+  描述：设置当前活动的服务器进程数（从1到活动服务器进程的数量）。
+
+  返回值类型：setofinteger
+
+- pg_stat_get_backend_pid(integer)
+
+  描述：给定的服务器线程的线程ID。
+
+  返回值类型：bigint
+
+- pg_stat_get_backend_dbid(integer)
+
+  描述：给定服务器进程的数据库ID。
+
+  返回值类型：oid
+
+- pg_stat_get_backend_userid(integer)
+
+  描述：给定服务器进程的用户ID。
+
+  返回值类型：oid
+
+- pg_stat_get_backend_activity(integer)
+
+  描述：给定服务器进程的当前活动查询，仅在调用者是系统管理员或被查询会话的用户，并且打开track_activities的时候才能获得结果。
+
+  返回值类型：text
+
+- pg_stat_get_backend_waiting(integer)
+
+  描述：如果给定服务器进程在等待某个锁，并且调用者是系统管理员或被查询会话的用户，并且打开track_activities的时候才返回真。
+
+  返回值类型：Boolean
+
+- pg_stat_get_backend_activity_start(integer)
+
+  描述：给定服务器进程当前正在执行的查询的起始时间，仅在调用者是系统管理员或被查询会话的用户，并且打开track_activities的时候才能获得结果。
+
+  返回值类型：timestampwithtimezone
+
+- pg_stat_get_backend_xact_start(integer)
+
+  描述：给定服务器进程当前正在执行的事务的开始时间，但只有当前用户是系统管理员或被查询会话的用户，并且打开track_activities的时候才能获得结果。
+
+  返回值类型：timestampwithtimezone
+
+- pg_stat_get_backend_start(integer)
+
+  描述：给定服务器进程启动的时间，如果当前用户不是系统管理员或被查询的后端的用户，则返回NULL。
+
+  返回值类型：timestampwithtimezone
+
+- pg_stat_get_backend_client_addr(integer)
+
+  描述：连接到给定客户端后端的IP地址。如果是通过Unix域套接字连接的则返回NULL；如果当前用户不是系统管理员或被查询会话的用户，也返回NULL。
+
+  返回值类型：inet
+
+- pg_stat_get_backend_client_port(integer)
+
+  描述：连接到给定客户端后端的TCP端口。如果是通过Unix域套接字连接的则返回-1；如果当前用户不是系统管理员或被查询会话的用户，也返回NULL。
+
+  返回值类型：integer
+
+- pg_stat_get_bgwriter_timed_checkpoints()
+
+  描述：后台写进程开启定时检查点的时间（因为checkpoint_timeout时间已经过期了）。
+
+  返回值类型：bigint
+
+- pg_stat_get_bgwriter_requested_checkpoints()
+
+  描述：后台写进程开启基于后端请求的检查点的时间，因为已经超过了checkpoint_segments或因为已经执行了CHECKPOINT。
+
+  返回值类型：bigint
+
+- pg_stat_get_bgwriter_buf_written_checkpoints()
+
+  描述：在检查点期间后台写进程写入的缓冲区数目。
+
+  返回值类型：bigint
+
+- pg_stat_get_bgwriter_buf_written_clean()
+
+  描述：为日常清理脏块，后台写进程写入的缓冲区数目。
+
+  返回值类型：bigint
+
+- pg_stat_get_bgwriter_maxwritten_clean()
+
+  描述：后台写进程停止清理扫描的时间，因为已经写入了更多的缓冲区（相比bgwriter_lru_maxpages参数声明的缓冲区数）。
+
+  返回值类型：bigint
+
+- pg_stat_get_buf_written_backend()
+
+  描述：后端进程写入的缓冲区数，因为它们需要分配一个新的缓冲区。
+
+  返回值类型：bigint
+
+- pg_stat_get_buf_alloc()
+
+  描述：分配的总缓冲区数。
+
+  返回值类型：bigint
+
+- pg_stat_clear_snapshot()
+
+  描述：清理当前的统计快照。
+
+  返回值类型：void
+
+- pg_stat_reset()
+
+  描述：为当前数据库重置统计计数器为0（需要系统管理员权限）。
+
+  返回值类型：void
+
+- pg_stat_reset_shared(text)
+
+  描述：重置shared cluster每个节点当前数据统计计数器为0（需要系统管理员权限）。
+
+  返回值类型：void
+
+- pg_stat_reset_single_table_counters(oid)
+
+  描述：为当前数据库中的一个表或索引重置统计为0（需要系统管理员权限）。
+
+  返回值类型：void
+
+- pg_stat_reset_single_function_counters(oid)
+
+  描述：为当前数据库中的一个函数重置统计为0（需要系统管理员权限）。
+
+  返回值类型：void
+
+- pg_stat_session_cu(int, int, int)
+
+  描述：获取当前节点所运行session的CU命中统计信息。
+
+  返回值类型：record
+
+- pg_stat_get_cu_mem_hit(oid)
+
+  描述：获取当前节点当前数据库中一个列存表的CU内存命中次数。
+
+  返回值类型：bigint
+
+- pg_stat_get_cu_hdd_sync(oid)
+
+  描述：获取当前节点当前数据库中一个列存表从磁盘同步读取CU次数。
+
+  返回值类型：bigint
+
+- pg_stat_get_cu_hdd_asyn(oid)
+
+  描述：获取当前节点当前数据库中一个列存表从磁盘异步读取CU次数。
+
+  返回值类型：bigint
+
+- pg_stat_get_db_cu_mem_hit(oid)
+
+  描述：获取当前节点一个数据库CU内存命中次数。
+
+  返回值类型：bigint
+
+- pg_stat_get_db_cu_hdd_sync(oid)
+
+  描述：获取当前节点一个数据库从磁盘同步读取CU次数。
+
+  返回值类型：bigint
+
+- fenced_udf_process()
+
+  描述：查看本地UDF Master和Work进程数。
+
+  返回值类型：record
+
+- total_cpu()
+
+  描述：获取当前节点使用的CPU时间，单位是jiffies。
+
+  返回值类型：bigint
+
+- mot_global_memory_detail()
+
+  描述：检查MOT全局内存的大小，主要包括数据和索引。
+
+  返回值类型：record
+
+- mot_local_memory_detail()
+
+  描述：检查MOT局部内存的大小，主要包括数据和索引。
+
+  返回值类型：record
+
+- mot_session_memory_detail()
+
+  描述：检查所有会话对MOT内存的使用情况。
+
+  返回值类型：record
+
+- total_memory()
+
+  描述：获取当前节点使用的虚拟内存大小，单位KB。
+
+  返回值类型：bigint
+
+- pg_stat_get_db_cu_hdd_asyn(oid)
+
+  描述：获取当前节点一个数据库从磁盘异步读取CU次数。
+
+  返回值类型：bigint
+
+- pg_stat_bad_block(text, int, int, int, int, int, timestamp with time zone, timestamp with time zone)
+
+  描述：获取当前节点自启动后，读取出现Page/CU的损坏信息。
+
+  例: select * from pg_stat_bad_block();
+
+  返回值类型：record
+
+- pg_stat_bad_block_clear()
+
+  描述：清理节点记录的读取出现的Page/CU损坏信息（需要系统管理员权限）。
+
+  返回值类型：void
+
+- gs_respool_exception_info(pool text)
+
+  描述：查看某个资源池关联的查询规则信息。
+
+  返回值类型：record
+
+- gs_control_group_info(pool text)
+
+  描述：查看资源池关联的控制组信息
+
+  返回值类型：record
+
+  返回信息如下：
+
+  | 属性     | 属性值              | 描述                                         |
+  | :------- | :------------------ | :------------------------------------------- |
+  | name     | class_a:workload_a1 | class和workload名称                          |
+  | class    | class_a             | Class控制组名称                              |
+  | workload | workload_a1         | Workload控制组名称                           |
+  | type     | DEFWD               | 控制组类型（Top、CLASS、BAKWD、DEFWD、TSWD） |
+  | gid      | 87                  | 控制组id                                     |
+  | shares   | 30                  | 占父节点CPU资源的百分比                      |
+  | limits   | 0                   | 占父节点CPU核数的百分比                      |
+  | rate     | 0                   | Timeshare中的分配比例                        |
+  | cpucores | 0-3                 | CPU核心数                                    |
+
+- gs_all_control_group_info()
+
+  描述：查看数据库内所有的控制组信息。
+
+  返回值类型：record
+
+- gs_get_control_group_info()
+
+  描述：查看所有的控制组信息。
+
+  返回值类型：record
+
+- get_instr_workload_info(integer)
+
+  描述：获取数据库主节点上事务量信息，事务时间信息。
+
+  返回值类型：record
+
+  | 属性                | 属性值       | 描述                               |
+  | :------------------ | :----------- | :--------------------------------- |
+  | resourcepool_oid    | 10           | 资源池的oid(逻辑同负载等价)        |
+  | commit_counter      | 4            | 前端事务commit数量                 |
+  | rollback_counter    | 1            | 前端事务rollback数量               |
+  | resp_min            | 949          | 前端事务最小响应时间（单位：微秒） |
+  | resp_max            | 201891       | 前端事务最大响应时间（单位：微秒） |
+  | resp_avg            | 43564        | 前端事务平均响应时间(单位：微秒)   |
+  | resp_total          | 217822       | 前端事务总响应时间（单位：微秒）   |
+  | bg_commit_counter   | 910          | 后端事务commit数量                 |
+  | bg_rollback_counter | 0            | 后端事务rollback数量               |
+  | bg_resp_min         | 97           | 后端事务最小响应时间（单位：微秒） |
+  | bg_resp_max         | 678080687    | 后端事务最大响应时间（单位：微秒） |
+  | bg_resp_avg         | 327847884    | 后端事务平均响应时间（单位：微秒） |
+  | bg_resp_total       | 298341575300 | 后端事务总响应时间（单位：微秒）   |
+
+- pv_instance_time()
+
+  描述：获取当前节点上各个关键阶段的时间消耗。
+
+  返回值类型：record
+
+  | Stat_name属性       | 属性值  | 描述                                                       |
+  | :------------------ | :------ | :--------------------------------------------------------- |
+  | DB_TIME             | 1062385 | 所有线程端到端的墙上时间（WALL TIME）消耗总和(单位： 微秒) |
+  | CPU_TIME            | 311777  | 所有线程CPU时间消耗总和(单位： 微秒)                       |
+  | EXECUTION_TIME      | 380037  | 消耗在执行器上的时间总和(单位： 微秒)                      |
+  | PARSE_TIME          | 6033    | 消耗在SQL解析上的时间总和(单位： 微秒)                     |
+  | PLAN_TIME           | 173356  | 消耗在执行计划生成上的时间总和(单位： 微秒)                |
+  | REWRITE_TIME        | 2274    | 消耗在查询重写上的时间总和(单位： 微秒)                    |
+  | PL_EXECUTION_TIME   | 0       | 消耗在PL/SQL执行上的时间总和(单位： 微秒)                  |
+  | PL_COMPILATION_TIME | 557     | 消耗在SQL编译上的时间总和(单位： 微秒)                     |
+  | NET_SEND_TIME       | 1673    | 消耗在网络发送上的时间总和(单位： 微秒)                    |
+  | DATA_IO_TIME        | 426622  | 消耗在数据读写上的时间总和(单位： 微秒)                    |
+
+- DBE_PERF.get_global_instance_time()
+
+  描述：提供MogDB各个关键阶段的时间消耗，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- get_instr_unique_sql()
+
+  描述：获取当前节点的执行语句（归一化SQL）信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- reset_unique_sql(text, text, bigint)
+
+描述：重置系统执行语句（归一化SQL）信息，执行该函数必须具有sysadmin权限。第一个参数取值范围“global/local”，global表示清理所有节点上的信息，local表示只清理当前节点；第二参数取值范围“ALL/BY_USERID/BY_CNID”，ALL表示清理所有信息，BY_USERID表示通过指定USERID清理只属于该用户的sql信息，BY_CNID表示清理系统中涉及到该数据库主节点的sql信息；第三个参数表示具体的CNID和USERID，如果第二个参数为ALL，第三个参数不起作用，可以取任意值。
+
+返回值类型：boolean
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> 此函数中所说节点指分布式节点，当前MogDB为集中式数据库，global与local功能一致，取值范围不支持BY_CNID。
+
+- get_instr_wait_event(NULL)
+
+  描述：获取当前节点event等待的统计信息。
+
+  返回值类型：record
+
+- get_instr_user_login()
+
+  描述：获取当前节点的用户登入登出次数信息，查询该函数必须具有sysadmin或者monitor admin权限。
+
+  返回值类型：record
+
+- get_instr_rt_percentile(integer)
+
+  描述：获取数据库SQL响应时间P80、P95分布信息。
+
+  返回值类型：record
+
+- get_node_stat_reset_time()
+
+  描述：获取当前节点的统计信息重置（重启、主备倒换、数据库删除）时间。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_os_runtime()
+
+  描述：显示当前操作系统运行的状态信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_os_threads()
+
+  描述：提供MogDB中所有正常节点下的线程状态信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_summary_workload_sql_count()
+
+  描述：提供MogDB中不同负载SELECT，UPDATE，INSERT，DELETE，DDL，DML，DCL计数信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_summary_workload_sql_elapse_time()
+
+  描述：提供MogDB中不同负载SELECT，UPDATE，INSERT，DELETE，响应时间信息（TOTAL,AVG, MIN, MAX），查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_workload_transaction()
+
+  描述：获取MogDB内所有节点上的事务量信息，事务时间信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_session_stat()
+
+描述：获取MogDB节点上的会话状态信息，查询该函数必须具有sysadmin权限。
+
+返回值类型：record
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> 状态信息有17项：commit、rollback、sql、table_scan、blocks_fetched、physical_read_operation、 shared_blocks_dirtied、local_blocks_dirtied、shared_blocks_read、local_blocks_read、 blocks_read_time、blocks_write_time、sort_imemory、sort_idisk、cu_mem_hit、 cu_hdd_sync_read、cu_hdd_asyread。
+
+- DBE_PERF.get_global_session_time()
+
+  描述：提供MogDB各节点各个关键阶段的时间消耗，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_session_memory()
+
+  描述：汇聚各节点的Session级别的内存使用情况，包含执行作业在数据节点上Postgres线程和Stream线程分配的所有内存，单位为MB，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_session_memory_detail()
+
+  描述：汇聚各节点的线程的内存使用情况，以MemoryContext节点来统计，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- create_wlm_session_info(int flag)
+
+  描述：将当前内存中记录的TopSQL查询语句级别相关统计信息清理。该函数只有管理员用户可以执行。
+
+  返回值类型：int
+
+- pg_stat_get_wlm_session_info(int flag)
+
+  描述：获取当前内存中记录的TopSQL查询语句级别相关统计信息，当传入的参数不为0时，会将这部分信息从内存中清理掉。该函数只有system admin和monitor admin用户可以执行。
+
+  返回值类型：record
+
+- gs_paxos_stat_replication()
+
+  描述：在主机端查询备机信息。目前只支持集中式DCF模式。
+
+  返回值类型：setofrecord
+
+  返回字段说明如下：
+
+  | 字段名称                 | 字段类型 | 字段说明                            |
+  | ------------------------ | -------- | ----------------------------------- |
+  | local_role               | text     | 发送日志节点的角色。                |
+  | peer_role                | text     | 接收日志节点的角色。                |
+  | local_dcf_role           | text     | 发送日志节点的DCF角色。             |
+  | peer_dcf_role            | text     | 接收日志节点的DCF角色。             |
+  | peer_state               | text     | 接收日志节点的状态。                |
+  | sender_write_location    | text     | 发送日志节点写到xlog buffer的位置。 |
+  | sender_commit_location   | text     | 发送日志节点DCF日志达成一致性点。   |
+  | sender_flush_location    | text     | 发送日志节点写到xlog disk的位置。   |
+  | sender_replay_location   | text     | 发送日志节点replay的位置。          |
+  | receiver_write_location  | text     | 接收日志节点写到xlog buffer的位置。 |
+  | receiver_commit_location | text     | 接收日志节点DCF日志达成一致性点。   |
+  | receiver_flush_location  | text     | 接收日志节点写到xlog disk的位置。   |
+  | receiver_replay_location | text     | 接收日志节点重演xlog的位置。        |
+  | sync_percent             | text     | 同步百分比。                        |
+  | dcf_run_mode             | int4     | DCF同步模式。                       |
+  | channel                  | text     | 信道信息。                          |
+
+- gs_wlm_get_resource_pool_info(int)
+
+  描述：获取所有用户的资源使用统计信息，入参为int类型可以为可以为任意int值或NULL。
+
+  返回值类型：record
+
+- gs_wlm_get_all_user_resource_info()
+
+  描述：获取所有用户的资源使用统计信息。
+
+  返回值类型：record
+
+- gs_wlm_get_user_info(int)
+
+  描述：获取所有用户的相关信息，入参为int类型可以为可以为任意int值或NULL。该函数只有sysadmin权限的用户可以执行。
+
+  返回值类型：record
+
+- gs_wlm_get_workload_records()
+
+  描述：获取动态负载管理下的所有作业信息，该函数只在动态负载管理开的情况下有效。
+
+  返回值类型：record
+
+- gs_wlm_readjust_user_space()
+
+  描述：修正所有用户的存储空间使用情况。该函数只有管理员用户可以执行。
+
+  返回值类型：record
+
+- gs_wlm_readjust_user_space_through_username(text name)
+
+  描述：修正指定用户的存储空间使用情况。该函数普通用户只能修正自己的使用情况，只有管理员用户可以修正所有用户的使用情况。当name指定位“0000”，表示需要修正所有用户的使用情况。
+
+  返回值类型：record
+
+- gs_wlm_readjust_user_space_with_reset_flag(text name, boolean isfirst)
+
+  描述：修正指定用户的存储空间使用情况。入参isfirst为true表示从0开始统计，否则从上一次结果继续统计。该函数普通用户只能修正自己的使用情况，只有管理员用户可以修正所有用户的使用情况。当name指定位“0000”，表示需要修正所有用户的使用情况。
+
+  返回值类型：record
+
+- gs_wlm_session_respool(bigint)
+
+  描述：获取当前所有后台线程的session resouce pool相关信息，入参为bigint类型可以为可以为任意bigint值或NULL。
+
+  返回值类型：record
+
+- gs_wlm_get_session_info()
+
+  描述：目前该接口已废弃，暂不可用。
+
+- gs_wlm_get_user_session_info()
+
+  描述：目前该接口已废弃，暂不可用。
+
+- gs_io_wait_status()
+
+  描述：目前该接口不支持单机和集中式，暂不可用。
+
+- global_stat_get_hotkeys_info()
+
+  描述：获取整个集群中热点key的统计情况。目前该接口不支持单机和集中式，暂不可用。
+
+- global_stat_clean_hotkeys()
+
+  描述：清理整个集群中热点key的统计信息。目前该接口不支持单机和集中式，暂不可用。
+
+- DBE_PERF.get_global_session_stat_activity()
+
+  描述：汇聚MogDB内各节点上正在运行的线程相关的信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_thread_wait_status()
+
+  描述：汇聚所有节点上工作线程（backend thread）以及辅助线程（auxiliary thread）的阻塞等待情况，查询该函数必须具有sysadmin和monitoradmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_operator_history_table()
+
+  描述：汇聚当前用户数据库主节点上执行作业结束后的算子相关记录（持久化），查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_operator_history()
+
+  描述：汇聚当前用户数据库主节点上执行作业结束后的算子相关记录，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_operator_runtime()
+
+  描述：汇聚当前用户数据库主节点上执行作业实时的算子相关记录，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_statement_complex_history()
+
+  描述：汇聚当前用户数据库主节点上复杂查询的历史记录，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_statement_complex_history_table()
+
+  描述：汇聚当前用户数据库主节点上复杂查询的历史记录（持久化），查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_statement_complex_runtime()
+
+  描述：汇聚当前用户数据库主节点上复杂查询的实时信息，查询该函数必须具有sysadmin和monadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_memory_node_detail()
+
+  描述：汇聚所有节点某个数据库节点内存使用情况，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_shared_memory_detail()
+
+  描述：汇聚所有节点已产生的共享内存上下文的使用信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_statio_all_indexes()
+
+  描述：汇聚所有节点当前数据库中的每个索引行，显示特定索引的I/O的统计，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_summary_stat_all_tables()
+
+  描述：显示汇聚各节点数据中每个表（包括TOAST表）的一行的统计信息
+
+  返回值类型：record
+
+- DBE_PERF.get_global_stat_all_tables()
+
+  描述：显示各节点数据中每个表（包括TOAST表）的一行的统计信息。
+
+  返回值类型：record
+
+- DBE_PERF.get_local_toastname_and_toastindexname()
+
+  描述：提供本地toast表的name和index和其关联表的对应关系，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_summary_statio_all_indexes()
+
+  描述：统计所有节点当前数据库中的每个索引行，显示特定索引的I/O的统计，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_statio_all_sequences()
+
+  描述：提供命名空间中所有sequences的IO状态信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_statio_all_tables()
+
+  描述：汇聚各节点的数据库中每个表I/O的统计，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_summary_statio_all_tables()
+
+  描述：统计MogDB内数据库中每个表I/O的统计，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_local_toast_relation()
+
+  描述：提供本地toast表的name和其关联表的对应关系，查询该函数必须具有sysadmin权限
+
+  返回值类型：record
+
+- DBE_PERF.get_global_statio_sys_indexes()
+
+  描述：汇聚各节点的命名空间中所有系统表索引的IO状态信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_summary_statio_sys_indexes()
+
+  描述：统计各节点的命名空间中所有系统表索引的IO状态信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_statio_sys_sequences()
+
+  描述：提供命名空间中所有系统表为sequences的IO状态信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_statio_sys_tables()
+
+  描述：提供各节点的命名空间中所有系统表的IO状态信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_summary_statio_sys_tables()
+
+  描述：MogDB内汇聚命名空间中所有系统表的IO状态信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_statio_user_indexes()
+
+  描述：各节点的命名空间中所有用户关系表索引的IO状态信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_summary_statio_user_indexes()
+
+  描述：MogDB内汇聚命名空间中所有用户关系表索引的IO状态信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_statio_user_sequences()
+
+  描述：显示各节点的命名空间中所有用户的sequences的IO状态信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_statio_user_tables()
+
+  描述：显示各节点的命名空间中所有用户关系表的IO状态信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_summary_statio_user_tables()
+
+  描述：MogDB内汇聚命名空间中所有用户关系表的IO状态信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_stat_db_cu()
+
+  描述：视图查询MogDB各个节点，每个数据库的CU命中情况，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_stat_all_indexes()
+
+  描述：汇聚所有节点数据库中每个索引的统计信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_summary_stat_all_indexes()
+
+  描述：统计所有节点数据库中每个索引的统计信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_stat_sys_tables()
+
+  描述：汇聚各节点pg_catalog、information_schema模式的所有命名空间中系统表的统计信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_summary_stat_sys_tables()
+
+  描述：统计各节点pg_catalog、information_schema模式的所有命名空间中系统表的统计信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_stat_sys_indexes()
+
+  描述：汇聚各节点pg_catalog、information_schema模式中所有系统表的索引状态信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_summary_stat_sys_indexes()
+
+  描述：统计各节点pg_catalog、information_schema模式中所有系统表的索引状态信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_stat_user_tables()
+
+  描述：汇聚所有命名空间中用户自定义普通表的状态信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_summary_stat_user_tables()
+
+  描述：统计所有命名空间中用户自定义普通表的状态信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_stat_user_indexes()
+
+  描述：汇聚所有数据库中用户自定义普通表的索引状态信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_summary_stat_user_indexes()
+
+  描述：统计所有数据库中用户自定义普通表的索引状态信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_stat_database()
+
+  描述：汇聚所有节点数据库统计信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_stat_database_conflicts()
+
+  描述：统计所有节点数据库统计信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_stat_xact_all_tables()
+
+  描述：汇聚命名空间中所有普通表和toast表的事务状态信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_summary_stat_xact_all_tables()
+
+  描述：统计命名空间中所有普通表和toast表的事务状态信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_stat_xact_sys_tables()
+
+  描述：汇聚所有节点命名空间中系统表的事务状态信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_summary_stat_xact_sys_tables()
+
+  描述：统计所有节点命名空间中系统表的事务状态信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_stat_xact_user_tables()
+
+  描述：汇聚所有节点命名空间中用户表的事务状态信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_summary_stat_xact_user_tables()
+
+  描述：统计所有节点命名空间中用户表的事务状态信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_stat_user_functions()
+
+  描述：汇聚所有节点命名空间中用户定义函数的事务状态信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_stat_xact_user_functions()
+
+  描述：统计所有节点命名空间中用户定义函数的事务状态信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_stat_bad_block()
+
+  描述：汇聚所有节点表、索引等文件的读取失败信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_file_redo_iostat()
+
+  描述：统计所有节点表、索引等文件的读取失败信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_file_iostat()
+
+  描述：汇聚所有节点数据文件IO的统计，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_locks()
+
+  描述：汇聚所有节点的锁信息，查询该函数必须具有sysadmin和monadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_replication_slots()
+
+  描述：汇聚所有节点上逻辑复制信息，查询该函数必须具有sysadmin和monadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_bgwriter_stat()
+
+  描述：汇聚所有节点后端写进程活动的统计信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_replication_stat()
+
+  描述：汇聚各节点日志同步状态信息，如发起端发送日志位置、收端接收日志位置等，查询该函数必须具有sysadmin和monadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_transactions_running_xacts()
+
+  描述：汇聚各节点运行事务的信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_summary_transactions_running_xacts()
+
+  描述：统计各节点运行事务的信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_transactions_prepared_xacts()
+
+  描述：汇聚各节点当前准备好进行两阶段提交的事务的信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_summary_transactions_prepared_xacts()
+
+  描述：统计各节点当前准备好进行两阶段提交的事务的信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_summary_statement()
+
+  描述：汇聚各节点历史执行语句状态信息，查询该函数必须具有sysadmin权限或者monitor admin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_statement_count()
+
+  描述：汇聚各节点SELECT、UPDATE、INSERT、DELETE，响应时间信息（TOTAL、AVG、MIN、 MAX），查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_config_settings()
+
+  描述：汇聚各节点GUC参数配置信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_wait_events()
+
+  描述：汇聚各节点wait events状态信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_statement_responsetime_percentile()
+
+  描述：获取MogDB SQL响应时间P80、P95分布信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_summary_user_login()
+
+  描述：统计MogDB各节点用户登入登出次数信息，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_record_reset_time()
+
+  描述：汇聚MogDB统计信息重置（重启、主备倒换、数据库删除）时间，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.track_memory_context(context_list text)
+
+  描述：设置需要统计内存申请详细信息的内存上下文。入参为内存上下文的名称，使用“，”分隔，如“ThreadTopMemoryContext, SessionCacheMemoryContext”，注意该内存上下文名称是上下文敏感的。此外，单个内存上下文的长度为63，超过的部分会被截断。而且一次能够统计的内存上下文上限为16个，设置超过16个内存上下文会设置失败。每一次调用该函数都会将上次统计的结果清空，当入参指定为“”时，表示取消该统计功能。只有初始用户（super user）或者具有monadmin权限的用户可以执行该函数。
+
+  返回值类型：boolean
+
+- DBE_PERF.track_memory_context_detail()
+
+  描述：获取DBE_PERF.track_memory_context函数指定的内存上下文的内存申请详细信息。返回值的定义见视图DBE_PERF.track_memory_context_detail。只有初始用户（super user）或者具有monadmin权限的用户可以执行该函数。
+
+  返回值类型：record
+
+- pg_stat_get_mem_mbytes_reserved(tid)
+
+  描述：统计资源管理相关变量值，仅用于定位问题使用。
+
+  参数：线程id。
+
+  返回值类型：text
+
+- gs_wlm_user_resource_info(name text)
+
+  描述：查询具体某个用户的资源限额和资源使用情况。
+
+  返回值类型：record
+
+- pg_stat_get_file_stat()
+
+  描述：通过对数据文件IO的统计，反映数据的IO性能，用以发现IO操作异常等性能问题。
+
+  返回值类型: record
+
+- pg_stat_get_redo_stat()
+
+  描述：用于统计会话线程日志回放情况。
+
+  返回值类型: record
+
+- pg_stat_get_status(int8)
+
+  描述：可以检测当前实例中工作线程（backend thread）以及辅助线程（auxiliary thread）的阻塞等待情况。
+
+  返回值类型：record
+
+- get_local_rel_iostat()
+
+  描述：查询当前节点的数据文件IO状态累计值。
+
+  返回值类型：record
+
+- DBE_PERF.get_global_rel_iostat()
+
+  描述：汇聚所有节点数据文件IO的统计，查询该函数必须具有sysadmin权限。
+
+  返回值类型：record
+
+- DBE_PERF.global_threadpool_status()
+
+  描述：显示在所有节点上的线程池中工作线程及会话的状态信息。函数返回信息具体字段GLOBAL_THREADPOOL_STATUS字段。
+
+  返回值类型：record
+
+- remote_bgwriter_stat()
+
+  描述：显示数据库所有实例的bgwriter线程刷页信息，候选buffer链中页面个数，buffer淘汰信息（本节点除外、DN上不可使用）。
+
+  返回值类型：record
+
+- pv_os_run_info
+
+  描述：显示当前操作系统运行的状态信息，具体字段信息参考GS_OS_RUN_INFO。
+
+  参数：nan
+
+  返回值类型：setof record
+
+- pv_session_stat
+
+  描述：以会话线程或AutoVacuum线程为单位，统计会话状态信息，具体字段信息参考GS_SESSION_STAT。
+
+  参数：nan
+
+  返回值类型：setof record
+
+- pv_session_time
+
+  描述：用于统计会话线程的运行时间信息，及各执行阶段所消耗时间，具体字段信息参考GS_SESSION_TIME。
+
+  参数：nan
+
+  返回值类型：setof record
+
+- pg_stat_get_db_temp_bytes
+
+  描述：用于统计通过数据库查询写入临时文件的数据总量。计算所有临时文件，不论为什么创建临时文件，而且不管log_temp_files设置。
+
+  参数：oid
+
+  返回值类型：bigint
+
+- pg_stat_get_db_temp_files
+
+  描述：通过数据库查询创建的临时文件数量。计算所有临时文件，不论为什么创建临时文件（比如排序或者哈希），而且不管log_temp_files设置。
+
+  参数：oid
+
+  返回值类型：bigint
+
+- remote_candidate_stat()
+
+  描述：用于显示数据库所有实例的检查点信息和各类日志刷页情况（本节点除外），集中式不支持。
+
+  返回值类型：record
+
+- dbe_perf.gs_stat_activity_timeout(int)
+
+  描述：获取当前节点上执行时间超过超时阈值的查询作业信息。需要GUC参数track_activities设置为on才能正确返回结果。超时阈值的取值范围是0~2147483。
+
+  返回值类型：setof record
+
+  | 名称             | 类型        | 描述                       |
+  | :--------------- | :---------- | :------------------------- |
+  | database         | name        | 用户会话连接的数据库名称。 |
+  | pid              | bigint      | 后台线程ID。               |
+  | sessionid        | bigint      | 会话ID。                   |
+  | usesysid         | oid         | 登录该后台的用户OID。      |
+  | application_name | text        | 连接到该后台的应用名。     |
+  | query            | text        | 该后台正在执行的查询。     |
+  | xact_start       | timestamptz | 启动当前事务的时间。       |
+  | query_start      | timestamptz | 开始当前查询的时间。       |
+  | query_id         | bigint      | 查询语句ID。               |
+
+- gs_wlm_user_resource_info(name text)
+
+  描述：查询具体某个用户的资源限额和资源使用情况。普通用户只能查询到自己相关的信息，管理员权限的用户可以查看全部用户的信息。
+
+  返回值类型：record
+
+- create_wlm_instance_statistics_info
+
+  描述：将当前实例的历史监控数据进行持久化保存。
+
+  参数：nan
+
+  返回值类型：integer
+
+- gs_session_memory
+
+描述：统计Session级别的内存使用情况，包含执行作业在数据节点上Postgres线程和Stream线程分配的所有内存。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> 若GUC参数enable_memory_limit=off，该函数不能使用。
+
+返回值类型：record
+
+**表 8** 返回值说明
+
+| 名称     | 类型    | 描述                                               |
+| :------- | :------ | :------------------------------------------------- |
+| sessid   | text    | 线程启动时间+线程标识。                            |
+| init_mem | integer | 当前正在执行作业进入执行器前已分配的内存，单位MB。 |
+| used_mem | integer | 当前正在执行作业已分配的内存，单位MB。             |
+| peak_mem | integer | 当前正在执行作业已分配的内存峰值，单位MB。         |
+
+- gs_wlm_persistent_user_resource_info()
+
+  描述：将当前所有的用户资源使用统计信息归档到gs_wlm_user_resource_history系统表中，只有sysadmin有权限查询。
+
+  返回值类型：record
+
+- create_wlm_operator_info(int flag)
+
+  描述：将当前内存中记录的TopSQL算子级别相关统计信息清理，当传入的参数大于0时，会将这部分信息归档到gs_wlm_operator_info和gs_wlm_ec_operator_info中，否则不会归档。该函数只有sysadmin权限的用户可以执行。
+
+  返回值类型：int
+
+- GS_ALL_NODEGROUP_CONTROL_GROUP_INFO(text)
+
+描述：提供了所有逻辑数据库实例的控制组信息。该函数在调用的时候需要指定要查询逻辑数据库实例的名称。例如要查询'installation'逻辑数据库实例的控制组信息：
+
+```sql
+SELECT * FROM GS_ALL_NODEGROUP_CONTROL_GROUP_INFO('installation')
+```
+
+返回值类型：record
+
+函数返回字段如下：
+
+| 名称     | 类型   | 描述                          |
+| :------- | :----- | :---------------------------- |
+| name     | text   | 控制组的名称。                |
+| type     | text   | 控制组的类型。                |
+| gid      | bigint | 控制组ID。                    |
+| classgid | bigint | Workload所属Class的控制组ID。 |
+| class    | text   | Class控制组。                 |
+| workload | text   | Workload控制组。              |
+| shares   | bigint | 控制组分配的CPU资源配额。     |
+| limits   | bigint | 控制组分配的CPU资源限额。     |
+| wdlevel  | bigint | Workload控制组层级。          |
+| cpucores | text   | 控制组使用的CPU核的信息。     |
+
+- gs_total_nodegroup_memory_detail
+
+  描述：返回当前数据库逻辑数据库使用内存的信息，单位为MB得到一个逻辑数据库。
+
+  返回值类型：setof record
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/26-trigger-functions.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/26-trigger-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..bc63c6b78b58a02fb43ee223c21f01cd55c528bb
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/26-trigger-functions.md
@@ -0,0 +1,55 @@
+---
+title: 触发器函数
+summary: 触发器函数
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 触发器函数
+
+- pg_get_triggerdef(oid)
+
+  描述: 获取触发器的定义信息。
+
+  参数: 待查触发器的OID。
+
+  返回值类型: text
+
+  示例:
+
+  ```sql
+  mogdb=# select pg_get_triggerdef(oid) from pg_trigger;
+                                                                                       pg_get_triggerdef
+  --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+   CREATE TRIGGER tg1 BEFORE INSERT ON gtest26 FOR EACH STATEMENT EXECUTE PROCEDURE gtest_trigger_func()
+   CREATE TRIGGER tg03 AFTER INSERT ON gtest26 FOR EACH ROW WHEN ((new.a IS NOT NULL)) EXECUTE PROCEDURE gtest_trigger_func()
+  (2 rows)
+  ```
+
+- pg_get_triggerdef(oid, boolean)
+
+  描述: 获取触发器的定义信息。
+
+  参数: 待查触发器的OID及是否以pretty方式展示。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:** 仅在创建trigger时指定WHEN条件的情况下，布尔类型参数才生效。
+
+  返回值类型: text
+
+  示例:
+
+  ```sql
+  mogdb=# select pg_get_triggerdef(oid,true) from pg_trigger;
+                                                                                       pg_get_triggerdef
+  --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+   CREATE TRIGGER tg1 BEFORE INSERT ON gtest26 FOR EACH STATEMENT EXECUTE PROCEDURE gtest_trigger_func()
+   CREATE TRIGGER tg03 AFTER INSERT ON gtest26 FOR EACH ROW WHEN (new.a IS NOT NULL) EXECUTE PROCEDURE gtest_trigger_func()
+  (2 rows)
+
+  mogdb=# select pg_get_triggerdef(oid,false) from pg_trigger;
+                                                                                       pg_get_triggerdef
+  --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+   CREATE TRIGGER tg1 BEFORE INSERT ON gtest26 FOR EACH STATEMENT EXECUTE PROCEDURE gtest_trigger_func()
+   CREATE TRIGGER tg03 AFTER INSERT ON gtest26 FOR EACH ROW WHEN ((new.a IS NOT NULL)) EXECUTE PROCEDURE gtest_trigger_func()
+  (2 rows)
+  ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/27-global-temporary-table-functions.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/27-global-temporary-table-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..a6156515c8cd5e1f8e6599bdd3df9943cb767c34
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/27-global-temporary-table-functions.md
@@ -0,0 +1,132 @@
+---
+title: 全局临时表函数
+summary: 全局临时表函数
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 全局临时表函数
+
+- pg_get_gtt_relstats(relOid)
+
+  描述：显示当前会话指定的全局临时表的基本信息。
+
+  参数：全局临时表的OID。
+
+  返回值类型：record
+
+  示例：
+
+  ```sql
+  mogdb=# select * from pg_get_gtt_relstats(74069);
+   relfilenode | relpages | reltuples | relallvisible | relfrozenxid | relminmxid
+  -------------+----------+-----------+---------------+--------------+------------
+         74069 |       58 |     13000 |             0 |        11151 |          0
+  (1 row)
+  ```
+
+- pg_get_gtt_statistics(relOid, attnum, "::text)
+
+  描述：显示当前会话指定的全局临时表的单列统计信息。
+
+  参数：全局临时表的OID和属性attnum。
+
+  返回值类型：record
+
+  示例：
+
+  ```sql
+  mogdb=# select * from pg_get_gtt_statistics(74069,1,''::text);
+   starelid | starelkind | staattnum | stainherit | stanullfrac | stawidth | stadistinct | stakind1 | stakind2 | stakind3 | stakind4 | stakind5 | staop1 | staop2 | staop3 | staop4 | staop5 | stanumbers1 | stanumbers2 | stanumbers3 | stanu
+  mbers4 | stanumbers5 |
+                                            stavalues1
+                                                                          | stavalues2 | stavalues3 | stavalues4 | stavalues5 | stadndistinct | staextinfo
+  ----------+------------+-----------+------------+-------------+----------+-------------+----------+----------+----------+----------+----------+--------+--------+--------+--------+--------+-------------+-------------+-------------+------
+  -------+-------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+  --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+  ------------------------------------------------------------------------+------------+------------+------------+------------+---------------+------------
+      74069 | c          |         1 | f          |           0 |        4 |          -1 |        2 |        3 |        0 |        0 |        0 |     97 |     97 |      0 |      0 |      0 |             | {1}         |             |
+         |             | {1,130,260,390,520,650,780,910,1040,1170,1300,1430,1560,1690,1820,1950,2080,2210,2340,2470,2600,2730,2860,2990,3120,3250,3380,3510,3640,3770,3900,4030,4160,4290,4420,4550,4680,4810,4940,5070,5200,5330,5460,5590,57
+  20,5850,5980,6110,6240,6370,6500,6630,6760,6890,7020,7150,7280,7410,7540,7670,7800,7930,8060,8190,8320,8450,8580,8710,8840,8970,9100,9230,9360,9490,9620,9750,9880,10010,10140,10270,10400,10530,10660,10790,10920,11050,11180,11310,11440,1
+  1570,11700,11830,11960,12090,12220,12350,12480,12610,12740,12870,13000} |            |            |            |            |             0 |
+  (1 row)
+  ```
+
+- pg_gtt_attached_pid(relOid)
+
+  描述：显示正在使用指定全局临时表的所有线程pid。
+
+  参数：全局临时表的OID。
+
+  返回值类型：record
+
+  示例：
+
+  ```sql
+  mogdb=# select * from pg_gtt_attached_pid(74069);
+   relid |       pid
+  -------+-----------------
+   74069 | 139648170456832
+   74069 | 139648123270912
+  (2 rows)
+  ```
+
+- dbe_perf.get_global_full_sql_by_timestamp(start_timestamp timestamp, end_timestamp timestamp)
+
+  描述：获取实例级的全量SQL(Full SQL)信息。
+
+  返回值类型：record
+
+  **表 1** dbe_perf.get_global_full_sql_by_timestamp参数说明
+
+  | 参数            | 类型      | 描述                          |
+  | :-------------- | :-------- | :---------------------------- |
+  | start_timestamp | timestamp | SQL启动时间范围的开始时间点。 |
+  | end_timestamp   | timestamp | SQL启动时间范围的结束时间点。 |
+
+- dbe_perf.get_global_slow_sql_by_timestamp(start_timestamp timestamp, end_timestamp timestamp)
+
+  描述：获取实例级的慢SQL(Slow SQL)信息。
+
+  返回值类型：record
+
+  **表 2** dbe_perf.get_global_slow_sql_by_timestamp参数说明
+
+  | 参数            | 类型      | 描述                          |
+  | :-------------- | :-------- | :---------------------------- |
+  | start_timestamp | timestamp | SQL启动时间范围的开始时间点。 |
+  | end_timestamp   | timestamp | SQL启动时间范围的结束时间点。 |
+
+- statement_detail_decode(detail text, format text, pretty bool)
+
+  解析全量/慢SQL语句中的details字段的信息。
+
+  **表 3** statement_detail_decode参数说明
+
+  | 参数   | 类型 | 描述                                                         |
+  | :----- | :--- | :----------------------------------------------------------- |
+  | detail | text | SQL语句产生的事件的集合（不可读）。                          |
+  | format | text | 解析输出格式，取值为plaintext或json。                        |
+  | pretty | bool | 当format为plaintext时，是否以优雅的格式展示：<br/>- true表示通过`\n`分隔事件。<br/>- false表示通过“，”分隔事件。 |
+
+- pg_list_gtt_relfrozenxids()
+
+  描述：显示各会话的冻结事务xid。
+
+  pid=0的行，显示所有会话中最老的冻结事务xid。
+
+  参数：无。
+
+  返回值类型：record
+
+  示例：
+
+  ```sql
+  mogdb=# select * from pg_list_gtt_relfrozenxids();
+         pid       | relfrozenxid
+  -----------------+--------------
+   139648123270912 |        11151
+   139648170456832 |        11155
+                 0 |        11151
+  (3 rows)
+  ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/27.1-hash-function.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/27.1-hash-function.md
new file mode 100644
index 0000000000000000000000000000000000000000..1c9f468173d1df4ed1885c7ac54fce4607999da7
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/27.1-hash-function.md
@@ -0,0 +1,595 @@
+---
+title: HashFunc函数
+summary: HashFunc函数
+author: Guo Huan
+date: 2021-10-28
+---
+
+# HashFunc函数
+
+- bucketabstime(value，flag)
+
+  描述：对abstime格式的数值value计算hash值并找到对应的hashbucket桶。
+
+  参数：value为需要转换的数值，类型为abstime，flag为int类型表示数据分布方式，0表示hash分布。
+
+  返回值类型：int32
+
+  示例：
+
+  ```sql
+  mogdb=# select bucketabstime('2011-10-01 10:10:10.112',1);
+   bucketabstime
+  ---------------
+           13954
+  (1 row)
+  ```
+
+- bucketbool(value，flag)
+
+  描述：对bool格式的数值value计算hash值并找到对应的hashbucket桶。
+
+  参数：value为需要转换的数值，类型为bool，flag为int类型表示数据分布方式，0表示hash分布。
+
+  返回值类型：int32
+
+  示例：
+
+  ```sql
+  mogdb=# select bucketbool(true,1);
+   bucketbool
+  ------------
+            1
+  (1 row)
+  mogdb=#  select bucketbool(false,1);
+   bucketbool
+  ------------
+            0
+  (1 row)
+  ```
+
+- bucketbpchar(value, flag)
+
+  描述：对bpchar格式的数值value计算hash值并找到对应的hashbucket桶。
+
+  参数：value为需要转换的数值，类型为bpchar，flag为int类型表示数据分布方式，0表示hash分布。
+
+  返回值类型：int32
+
+  示例：
+
+  ```sql
+  mogdb=# select bucketbpchar('test',1);
+   bucketbpchar
+  --------------
+           9761
+  (1 row)
+  ```
+
+- bucketbytea(value，flag)
+
+  描述：对bytea格式的数值value计算hash值并找到对应的hashbucket桶。
+
+  参数：value为需要转换的数值，类型为bytea，flag为int类型表示数据分布方式，0表示hash分布。
+
+  返回值类型：int32
+
+  示例：
+
+  ```sql
+  mogdb=# select bucketbytea('test',1);
+   bucketbytea
+  -------------
+          9761
+  (1 row)
+  ```
+
+- bucketcash(value，flag)
+
+  描述：对money格式的数值value计算hash值并找到对应的hashbucket桶。
+
+  参数：value为需要转换的数值，类型为money，flag为int类型表示数据分布方式，0表示hash分布。
+
+  返回值类型：int32
+
+  示例：
+
+  ```sql
+  mogdb=# select bucketcash(10::money,1);
+   bucketcash
+  ------------
+         8468
+  (1 row)
+  ```
+
+- getbucket(value，flag)
+
+  描述：从分布列获取hashbucket桶。
+
+  value为需要输入的数值，类型：
+
+  “char”,abstime,bigint,boolean,bytea,character varying,character,date,double precision,int2vector,integer,interval,money,name,numeric,nvarchar2,oid,oidvector,raw,real,record,reltime,smalldatetime,smallint,text,time with time zone,time without time zone,timestamp with time zone,timestamp without time zone,tinyint,uuid。
+
+  flag表示数据分布方式，类型：integer
+
+  返回值类型：integer
+
+  示例：
+
+  ```sql
+  mogdb=# select getbucket(10,'H');
+   getbucket
+  -----------
+       14535
+  (1 row)
+
+  mogdb=# select getbucket(11,'H');
+   getbucket
+  -----------
+       13449
+  (1 row)
+
+  mogdb=# select getbucket(11,'R');
+   getbucket
+  -----------
+       13449
+  (1 row)
+
+  mogdb=# select getbucket(12,'R');
+   getbucket
+  -----------
+        9412
+  (1 row)
+
+  ```
+
+- hash_array(anyarray)
+
+  描述：数组哈希，将数组的元素通过哈希函数得到结果，并返回合并结果。
+
+  参数：数据类型为anyarray。
+
+  返回值类型：integer
+
+  示例：
+
+  ```sql
+  mogdb=# select hash_array(ARRAY[[1,2,3],[1,2,3]]);
+   hash_array
+  ------------
+   -382888479
+  (1 row)
+  ```
+
+- hash_group(key)
+
+  描述：流引擎中，该函数可将Group Clause中的各列计算为一个hash值。
+
+  参数：key为Group Clause中各列的值。
+
+  返回值类型：32位hash值
+
+  示例：
+
+  ```sql
+  按照步骤依次执行。
+  mogdb=# CREATE TABLE tt(a int, b int,c int,d int);
+  NOTICE:  The 'DISTRIBUTE BY' clause is not specified. Using 'a' as the distribution column by default.
+  HINT:  Please use 'DISTRIBUTE BY' clause to specify suitable data distribution column.
+  CREATE TABLE
+  mogdb=# select * from tt;
+   a | b | c | d
+  ---+---+---+---
+  (0 rows)
+
+  mogdb=# insert into tt values(1,2,3,4);
+  INSERT 0 1
+  mogdb=# select * from tt;
+   a | b | c | d
+  ---+---+---+---
+   1 | 2 | 3 | 4
+  (1 row)
+
+  mogdb=# insert into tt values(5,6,7,8);
+  INSERT 0 1
+  mogdb=# select * from tt;
+   a | b | c | d
+  ---+---+---+---
+   1 | 2 | 3 | 4
+   5 | 6 | 7 | 8
+  (2 rows)
+
+  mogdb=# select hash_group(a,b) from tt where a=1 and b=2;
+   hash_group
+  ------------
+    990882385
+  (1 row)
+  ```
+
+- hash_numeric(numeric)
+
+  描述：计算Numeric类型的数据的hash值。
+
+  参数：Numeric类型的数据。
+
+  返回值类型：integer
+
+  示例：
+
+  ```sql
+  mogdb=# select hash_numeric(30);
+   hash_numeric
+  --------------
+     -282860963
+  (1 row)
+  ```
+
+- hash_range(anyrange)
+
+  描述：计算range的哈希值。
+
+  参数：anyrange类型的数据。
+
+  返回值类型：integer
+
+  示例：
+
+  ```sql
+  mogdb=# select hash_range(numrange(1.1,2.2));
+   hash_range
+  ------------
+    683508754
+  (1 row)
+  ```
+
+- hashbpchar(character)
+
+  描述：计算bpchar的哈希值。
+
+  参数：character类型的数据。
+
+  返回值类型：integer
+
+  示例：
+
+  ```sql
+  mogdb=# select hashbpchar('hello');
+   hashbpchar
+  -------------
+   -1870292951
+  (1 row)
+  ```
+
+- hashchar(char)
+
+  描述：char和布尔数据转换为哈希值。
+
+  参数：char类型的数据或者bool类型的数据。
+
+  返回值类型：integer
+
+  示例：
+
+  ```sql
+  mogdb=# select hashbpchar('hello');
+   hashbpchar
+  -------------
+   -1870292951
+  (1 row)
+
+  mogdb=# select hashchar('true');
+    hashchar
+  ------------
+   1686226652
+  (1 row)
+  ```
+
+- hashenum(anyenum)
+
+  描述：枚举类型转哈希值。
+
+  参数：anyenum类型的数据。
+
+  返回值类型：integer
+
+  示例：
+
+  ```sql
+  mogdb=# CREATE TYPE b1 AS ENUM('good', 'bad', 'ugly');
+  CREATE TYPE
+  mogdb=# call hashenum('good'::b1);
+    hashenum
+  ------------
+   1821213359
+  (1 row)
+  ```
+
+- hashfloat4(real)
+
+  描述：float4转哈希值。
+
+  参数：real类型的数据。
+
+  返回值类型：integer
+
+  示例：
+
+  ```sql
+  mogdb=# select hashfloat4(12.1234);
+   hashfloat4
+  ------------
+   1398514061
+  (1 row)
+  ```
+
+- hashfloat8(double precision)
+
+  描述：float8转哈希值。
+
+  参数：double precision类型的数据。
+
+  返回值类型：integer
+
+  示例：
+
+  ```sql
+  mogdb=# select hashfloat8(123456.1234);
+   hashfloat8
+  ------------
+   1673665593
+  (1 row)
+  ```
+
+- hashinet(inet)
+
+  描述：支持inet / cidr上的哈希索引的功能。返回传入inet的hash值。
+
+  参数：inet类型的数据。
+
+  返回值类型：integer
+
+  示例：
+
+  ```sql
+  mogdb=# select hashinet('127.0.0.1'::inet);
+    hashinet
+  -------------
+   -1435793109
+  (1 row)
+  ```
+
+- hashint1(tinyint)
+
+  描述：INT1转哈希值。
+
+  参数：tinyint类型的数据。
+
+  返回值类型：uint32
+
+  示例：
+
+  ```sql
+  mogdb=# select hashint1(20);
+    hashint1
+  -------------
+   -2014641093
+  (1 row)
+  ```
+
+- hashint2(smallint)
+
+  描述：INT2转哈希值。
+
+  参数：smallint类型的数据。
+
+  返回值类型：uint32
+
+  示例：
+
+  ```sql
+  mogdb=# select hashint2(20000);
+    hashint2
+  ------------
+   -863179081
+  (1 row)
+  ```
+
+- bucketchar
+
+  描述：计算入参的哈希值。
+
+  参数：char, integer
+
+  返回值类型：integer
+
+- bucketdate
+
+  描述：计算入参的哈希值。
+
+  参数：date, integer
+
+  返回值类型：integer
+
+- bucketfloat4
+
+  描述：计算入参的哈希值。
+
+  参数：real, integer
+
+  返回值类型：integer
+
+- bucketfloat8
+
+  描述：计算入参的哈希值。
+
+  参数：double precision, integer
+
+  返回值类型：integer
+
+- bucketint1
+
+  描述：计算入参的哈希值。
+
+  参数：tinyint, integer
+
+  返回值类型：integer
+
+- bucketint2
+
+  描述：计算入参的哈希值。
+
+  参数：smallint, integer
+
+  返回值类型：integer
+
+- bucketint2vector
+
+  描述：计算入参的哈希值。
+
+  参数：int2vector, integer
+
+  返回值类型：integer
+
+- bucketint4
+
+  描述：计算入参的哈希值。
+
+  参数：integer, integer
+
+  返回值类型：integer
+
+- bucketint8
+
+  描述：计算入参的哈希值。
+
+  参数：bigint, integer
+
+  返回值类型：integer
+
+- bucketinterval
+
+  描述：计算入参的哈希值。
+
+  参数：interval, integer
+
+  返回值类型：integer
+
+- bucketname
+
+  描述：计算入参的哈希值。
+
+  参数：name, integer
+
+  返回值类型：integer
+
+- bucketnumeric
+
+  描述：计算入参的哈希值。
+
+  参数：numeric, integer
+
+  返回值类型：integer
+
+- bucketnvarchar2
+
+  描述：计算入参的哈希值。
+
+  参数：nvarchar2, integer
+
+  返回值类型：integer
+
+- bucketoid
+
+  描述：计算入参的哈希值。
+
+  参数：oid, integer
+
+  返回值类型：integer
+
+- bucketoidvector
+
+  描述：计算入参的哈希值。
+
+  参数：oidvector, integer
+
+  返回值类型：integer
+
+- bucketraw
+
+  描述：计算入参的哈希值。
+
+  参数：raw, integer
+
+  返回值类型：integer
+
+- bucketreltime
+
+  描述：计算入参的哈希值。
+
+  参数：reltime, integer
+
+  返回值类型：integer
+
+- bucketsmalldatetime
+
+  描述：计算入参的哈希值。
+
+  参数：smalldatetime, integer
+
+  返回值类型：integer
+
+- buckettext
+
+  描述：计算入参的哈希值。
+
+  参数：text, integer
+
+  返回值类型：integer
+
+- buckettime
+
+  描述：计算入参的哈希值。
+
+  参数：time without time zone, integer
+
+  返回值类型：integer
+
+- buckettimestamp
+
+  描述：计算入参的哈希值。
+
+  参数：timestamp without time zone, integer
+
+  返回值类型：integer
+
+- buckettimestamptz
+
+  描述：计算入参的哈希值。
+
+  参数：timestamp with time zone, integer
+
+  返回值类型：integer
+
+- buckettimetz
+
+  描述：计算入参的哈希值。
+
+  参数：time with time zone, integer
+
+  返回值类型：integer
+
+- bucketuuid
+
+  描述：计算入参的哈希值。
+
+  参数：uuid, integer
+
+  返回值类型：integer
+
+- bucketvarchar
+
+  描述：计算入参的哈希值。
+
+  参数：character varying, integer
+
+  返回值类型：integer
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/27.2-prompt-message-function.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/27.2-prompt-message-function.md
new file mode 100644
index 0000000000000000000000000000000000000000..80a9262d9e175030e6c1f88855b0131a5c0722e1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/27.2-prompt-message-function.md
@@ -0,0 +1,21 @@
+---
+title: 提示信息函数
+summary: 提示信息函数
+author: Guo Huan
+date: 2021-10-28
+---
+
+# 提示信息函数
+
+- report_application_error
+
+  描述：PL执行过程中，可以使用此函数来抛ERROR。
+
+  返回值类型：void
+
+  **表 1** report_application_error参数说明
+
+  | 参数 | 类型 | 说明                                                 | 是否必选 |
+  | :--- | :--- | :--------------------------------------------------- | :------- |
+  | log  | text | error消息的内容。                                    | 是       |
+  | code | int4 | error消息对应的error code，范围为：-20999 ~ -20000。 | 否       |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/28-ai-feature-functions.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/28-ai-feature-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..ac88e818f14e15aed5aeec4555948ff86b462d75
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/28-ai-feature-functions.md
@@ -0,0 +1,184 @@
+---
+title: AI特性函数
+summary: AI特性函数
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# AI特性函数
+
+- gs_index_advise(text)
+
+  描述：针对单条查询语句推荐索引。
+
+  参数：SQL语句字符串
+
+  返回值类型：record
+
+  示例请参见单query索引推荐。
+
+- hypopg_create_index(text)
+
+  描述：创建虚拟索引。
+
+  参数：创建索引语句的字符串
+
+  返回值类型：record
+
+  示例请参见虚拟索引。
+
+- hypopg_display_index()
+
+  描述：显示所有创建的虚拟索引信息。
+
+  参数：无
+
+  返回值类型：record
+
+  示例请参见虚拟索引。
+
+- hypopg_drop_index(oid)
+
+  描述：删除指定的虚拟索引。
+
+  参数：索引的oid
+
+  返回值类型：bool
+
+  示例请参见虚拟索引。
+
+- hypopg_reset_index()
+
+  描述：清除所有虚拟索引。
+
+  参数：无
+
+  返回值类型：无
+
+  示例请参见虚拟索引。
+
+- hypopg_estimate_size(oid)
+
+  描述：估计指定索引创建所需的空间大小。
+
+  参数：索引的oid
+
+  返回值类型：int8
+
+  示例请参见虚拟索引。
+
+- check_engine_status(ip text, port text)
+
+  描述：测试给定的ip和port上是否有predictor engine提供服务。
+
+  参数：predictor engine的ip地址和端口号。
+
+  返回值类型：text
+
+  示例请参见使用指导。
+
+- encode_plan_node(optname text, orientation text, strategy text, options text, dop int8, quals text, projection text)
+
+  描述：对入参的计划算子信息进行编码。
+
+  参数：计划算子信息。
+
+  返回值类型：text。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 该函数为内部功能调用函数，不建议用户直接使用。
+
+- model_train_opt(template text, model text)
+
+  描述：训练给定的查询性能预测模型。
+
+  参数：性能预测模型的模板名和模型名。
+
+  返回值类型：tartup_time_accuracy FLOAT8, total_time_accuracy FLOAT8, rows_accuracy FLOAT8, peak_memory_accuracy FLOAT8
+
+  示例请参见使用指导。
+
+- track_model_train_opt(ip text, port text)
+
+  描述：返回给定ip和port predictor engine的训练日志地址。
+
+  参数：predictor engine的ip地址和端口号。
+
+  返回值类型：text
+
+  示例请参见使用指导。
+
+- encode_feature_perf_hist(datname text)
+
+  描述：将目标数据库已收集的历史计划算子进行编码。
+
+  参数：数据库名。
+
+  返回值类型：queryid bigint, plan_node_id int, parent_node_id int, left_child_id int, right_child_id int, encode text, startup_time bigint, total_time bigint, rows bigint, peak_memory int
+
+  示例请参见使用指导。
+
+- gather_encoding_info(datname text)
+
+  描述：调用encode_feature_perf_hist，将编码好的数据进行持久化保存。
+
+  参数：数据库名。
+
+  返回值类型：int
+
+  示例请参见使用指导。
+
+- db4ai_predict_by_bool (text, VARIADIC "any")
+
+    描述：获取返回值为布尔型的模型进行模型推断任务。此函数为内部调用函数，建议直接使用语法PREDICT BY进行推断任务。
+
+    参数：模型名称和推断任务的输入列。
+
+    返回值类型：bool
+
+- db4ai_predict_by_float4(text, VARIADIC "any")
+
+    描述：获取返回值为float4的模型进行模型推断任务。此函数为内部调用函数，建议直接使用语法PREDICT BY进行推断任务。
+
+    参数：模型名称和推断任务的输入列。
+
+    返回值类型：float
+
+- db4ai_predict_by_float8(text, VARIADIC "any")
+
+    描述：获取返回值为float8的模型进行模型推断任务。此函数为内部调用函数，建议直接使用语法PREDICT BY进行推断任务。
+
+    参数：模型名称和推断任务的输入列。
+
+    返回值类型：float
+
+- db4ai_predict_by_int32(text, VARIADIC "any")
+
+    描述：获取返回值为int32的模型进行模型推断任务。此函数为内部调用函数，建议直接使用语法PREDICT BY进行推断任务。
+
+    参数：模型名称和推断任务的输入列。
+
+    返回值类型：int
+
+- db4ai_predict_by_int64(text, VARIADIC "any")
+
+    描述：获取返回值为int64的模型进行模型推断任务。此函数为内部调用函数，建议直接使用语法PREDICT BY进行推断任务。
+
+    参数：模型名称和推断任务的输入列。
+
+    返回值类型：int
+
+- db4ai_predict_by_numeric(text, VARIADIC "any")
+
+    描述：获取返回值为numeric的模型进行模型推断任务。此函数为内部调用函数，建议直接使用语法PREDICT BY进行推断任务。
+
+    参数：模型名称和推断任务的输入列。
+
+    返回值类型：numeric
+
+- db4ai_predict_by_text(text, VARIADIC "any")
+
+    描述：获取返回值为字符型的模型进行模型推断任务。此函数为内部调用函数，建议直接使用语法PREDICT BY进行推断任务。
+
+    参数：模型名称和推断任务的输入列。
+
+    返回值类型：text
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/28.1-fault-injection-system-function.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/28.1-fault-injection-system-function.md
new file mode 100644
index 0000000000000000000000000000000000000000..95cb558261363934ee7b9943f9409b2c0431ea1c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/28.1-fault-injection-system-function.md
@@ -0,0 +1,20 @@
+---
+title: 故障注入系统函数
+summary: 故障注入系统函数
+author: Guo Huan
+date: 2021-10-28
+---
+
+# 故障注入系统函数
+
+- gs_fault_inject(int64, text, text, text, text, text)
+
+  描述：该函数不能调用，调用时会报WARNING信息：”unsupported fault injection”，并不会对数据库产生任何影响和改变。
+
+  参数：int64注入故障类型（0：CLOG扩展页面，1：读取CLOG页面，2：强制死锁）。
+
+  - text第二个入参在第一入参为2的模式下若为“1”则死锁，其余不死锁；第二个入参在第一入参为0，1时，表示CLOG开始扩展或读取的起始页面号。
+  - text第三个入参在第一入参为0，1时，表示扩展或读取的页面个数。
+  - text第四到六入参为预留参数。
+
+  返回值类型：int64
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/29-other-system-functions.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/29-other-system-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..e7e2767f677448478d7260d514e01ee9fec85f96
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/29-other-system-functions.md
@@ -0,0 +1,683 @@
+---
+title: 其他系统函数
+summary: 其他系统函数
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 其他系统函数
+
+MogDB的内建函数和操作符继承自开源PG，下述函数不作赘述，详情请参见[PG官方文档](https://www.postgresql.org/docs/9.2/functions.html)。
+
+| _pg_char_max_length              | _pg_char_octet_length                    | _pg_datetime_precision            | _pg_expandarray                | _pg_index_position             | _pg_interval_type                  | _pg_numeric_precision                |
+| -------------------------------- | ---------------------------------------- | --------------------------------- | ------------------------------ | ------------------------------ | ---------------------------------- | ------------------------------------ |
+| _pg_numeric_precision_radix      | _pg_numeric_scale                        | _pg_truetypid                     | _pg_truetypmod                 | abbrev                         | abs                                | abstime                              |
+| abstimeeq                        | abstimege                                | abstimegt                         | abstimein                      | abstimele                      | abstimelt                          | abstimene                            |
+| abstimeout                       | abstimerecv                              | abstimesend                       | aclcontains                    | acldefault                     | aclexplode                         | aclinsert                            |
+| aclitemeq                        | aclitemin                                | aclitemout                        | aclremove                      | acos                           | age                                | akeys                                |
+| any_in                           | any_out                                  | anyarray_in                       | anyarray_out                   | anyarray_recv                  | anyarray_send                      | anyelement_in                        |
+| anyelement_out                   | anyenum_in                               | anyenum_out                       | anynonarray_in                 | anynonarray_out                | anyrange_in                        | anyrange_out                         |
+| anytextcat                       | area                                     | areajoinsel                       | areasel                        | array_agg                      | array_agg_finalfn                  | array_agg_transfn                    |
+| array_append                     | array_cat                                | array_dims                        | array_eq                       | array_fill                     | array_ge                           | array_gt                             |
+| array_in                         | array_larger                             | array_le                          | array_length                   | array_lower                    | array_lt                           | array_ndims                          |
+| array_ne                         | array_out                                | array_prepend                     | array_recv                     | array_send                     | array_smaller                      | array_to_json                        |
+| array_to_string                  | array_typanalyze                         | array_upper                       | arraycontained                 | arraycontains                  | arraycontjoinsel                   | arraycontsel                         |
+| arrayoverlap                     | ascii                                    | asin                              | atan                           | atan2                          | avals                              | avg                                  |
+| big5_to_euc_tw                   | big5_to_mic                              | big5_to_utf8                      | bit                            | bit_and                        | bit_in                             | bit_length                           |
+| bit_or                           | bit_out                                  | bit_recv                          | bit_send                       | bitand                         | bitcat                             | bitcmp                               |
+| biteq                            | bitge                                    | bitgt                             | bitle                          | bitlt                          | bitne                              | bitnot                               |
+| bitor                            | bitshiftleft                             | bitshiftright                     | bittypmodin                    | bittypmodout                   | bitxor                             | bool                                 |
+| bool_and                         | bool_or                                  | booland_statefunc                 | booleq                         | boolge                         | boolgt                             | boolin                               |
+| boolle                           | boollt                                   | boolne                            | boolor_statefunc               | boolout                        | boolrecv                           | boolsend                             |
+| box                              | box_above                                | box_above_eq                      | box_add                        | box_below                      | box_below_eq                       | box_center                           |
+| box_contain                      | box_contain_pt                           | box_contained                     | box_distance                   | box_div                        | box_eq                             | box_ge                               |
+| box_gt                           | box_in                                   | box_intersect                     | box_le                         | box_left                       | box_lt                             | box_mul                              |
+| box_out                          | box_overabove                            | box_overbelow                     | box_overlap                    | box_overleft                   | box_overright                      | box_recv                             |
+| box_right                        | box_same                                 | box_send                          | box_sub                        | bpchar                         | bpchar_larger                      | bpchar_pattern_ge                    |
+| bpchar_pattern_gt                | bpchar_pattern_le                        | bpchar_pattern_lt                 | bpchar_smaller                 | bpchar_sortsupport             | bpcharcmp                          | bpchareq                             |
+| bpcharge                         | bpchargt                                 | bpchariclike                      | bpcharicnlike                  | bpcharicregexeq                | bpcharicregexne                    | bpcharin                             |
+| bpcharle                         | bpcharlike                               | bpcharlt                          | bpcharne                       | bpcharnlike                    | bpcharout                          | bpcharrecv                           |
+| bpcharregexeq                    | bpcharregexne                            | bpcharsend                        | bpchartypmodin                 | bpchartypmodout                | broadcast                          | btabstimecmp                         |
+| btarraycmp                       | btbeginscan                              | btboolcmp                         | btbpchar_pattern_cmp           | btbuild                        | btbuildempty                       | btbulkdelete                         |
+| btcanreturn                      | btcharcmp                                | btcostestimate                    | btendscan                      | btfloat48cmp                   | btfloat4cmp                        | btfloat4sortsupport                  |
+| btfloat84cmp                     | btfloat8cmp                              | btfloat8sortsupport               | btgetbitmap                    | btgettuple                     | btinsert                           | btint24cmp                           |
+| btint28cmp                       | btint2cmp                                | btint2sortsupport                 | btint42cmp                     | btint48cmp                     | btint4cmp                          | btint4sortsupport                    |
+| btint82cmp                       | btint84cmp                               | btint8cmp                         | btint8sortsupport              | btmarkpos                      | btnamecmp                          | btnamesortsupport                    |
+| btoidcmp                         | btoidsortsupport                         | btoidvectorcmp                    | btoptions                      | btrecordcmp                    | btreltimecmp                       | btrescan                             |
+| btrestrpos                       | btrim                                    | bttext_pattern_cmp                | bttextcmp                      | bttextsortsupport              | bttidcmp                           | bttintervalcmp                       |
+| btvacuumcleanup                  | bytea_sortsupport                        | bytea_string_agg_finalfn          | bytea_string_agg_transfn       | byteacat                       | byteacmp                           | byteaeq                              |
+| byteage                          | byteagt                                  | byteain                           | byteale                        | bytealike                      | bytealt                            | byteane                              |
+| byteanlike                       | byteaout                                 | bytearecv                         | byteasend                      | cash_cmp                       | cash_div_cash                      | cash_div_flt4                        |
+| cash_div_flt8                    | cash_div_int2                            | cash_div_int4                     | cash_div_int8                  | cash_eq                        | cash_ge                            | cash_gt                              |
+| cash_in                          | cash_le                                  | cash_lt                           | cash_mi                        | cash_mul_flt4                  | cash_mul_flt8                      | cash_mul_int2                        |
+| cash_mul_int4                    | cash_mul_int8                            | cash_ne                           | cash_out                       | cash_pl                        | cash_recv                          | cash_send                            |
+| cashlarger                       | cashsmaller                              | cbrt                              | ceil                           | ceiling                        | center                             | char                                 |
+| char_length                      | character_length                         | chareq                            | charge                         | chargt                         | charin                             | charle                               |
+| charlt                           | charne                                   | charout                           | charrecv                       | charsend                       | chr                                | cideq                                |
+| cidin                            | cidout                                   | cidr                              | cidr_in                        | cidr_out                       | cidr_recv                          | cidr_send                            |
+| cidrecv                          | cidsend                                  | circle                            | circle_above                   | circle_add_pt                  | circle_below                       | circle_center                        |
+| circle_contain                   | circle_contain_pt                        | circle_contained                  | circle_distance                | circle_div_pt                  | circle_eq                          | circle_ge                            |
+| circle_gt                        | circle_in                                | circle_le                         | circle_left                    | circle_lt                      | circle_mul_pt                      | circle_ne                            |
+| circle_out                       | circle_overabove                         | circle_overbelow                  | circle_overlap                 | circle_overleft                | circle_overright                   | circle_recv                          |
+| circle_right                     | circle_same                              | circle_send                       | circle_sub_pt                  | clock_timestamp                | close_lb                           | close_ls                             |
+| close_lseg                       | close_pb                                 | close_pl                          | close_ps                       | close_sb                       | close_sl                           | col_description                      |
+| concat                           | concat_ws                                | contjoinsel                       | contsel                        | convert                        | convert_from                       | convert_to                           |
+| corr                             | cos                                      | cot                               | count                          | covar_pop                      | covar_samp                         | cstring_in                           |
+| cstring_out                      | cstring_recv                             | cstring_send                      | cume_dist                      | current_database               | current_query                      | current_schema                       |
+| xpath_exists                     | current_setting                          | current_user                      | currtid                        | currtid2                       | currval                            | cursor_to_xml                        |
+| cursor_to_xmlschema              | database_to_xml                          | database_to_xml_and_xmlschema     | database_to_xmlschema          | date                           | date_cmp                           | date_cmp_timestamp                   |
+| date_cmp_timestamptz             | date_eq                                  | date_eq_timestamp                 | date_eq_timestamptz            | date_ge                        | date_ge_timestamp                  | date_ge_timestamptz                  |
+| date_gt                          | date_gt_timestamp                        | date_gt_timestamptz               | date_in                        | date_larger                    | date_le                            | date_le_timestamp                    |
+| date_le_timestamptz              | date_lt                                  | date_lt_timestamp                 | date_lt_timestamptz            | date_mi                        | date_mi_interval                   | date_mii                             |
+| date_ne                          | date_ne_timestamp                        | date_ne_timestamptz               | date_out                       | date_pl_interval               | date_pli                           | date_recv                            |
+| date_send                        | date_smaller                             | date_sortsupport                  | daterange_canonical            | daterange_subdiff              | datetime_pl                        | datetimetz_pl                        |
+| dcbrt                            | decode                                   | defined                           | degrees                        | delete                         | dense_rank                         | dexp                                 |
+| diagonal                         | diameter                                 | dispell_init                      | dispell_lexize                 | dist_cpoly                     | dist_lb                            | dist_pb                              |
+| dist_pc                          | dist_pl                                  | dist_ppath                        | dist_ps                        | dist_sb                        | dist_sl                            | div                                  |
+| dlog1                            | dlog10                                   | domain_in                         | domain_recv                    | dpow                           | dround                             | dsimple_init                         |
+| dsimple_lexize                   | dsnowball_init                           | dsnowball_lexize                  | dsqrt                          | dsynonym_init                  | dsynonym_lexize                    | dtrunc                               |
+| each                             | enum_ne                                  | enum_out                          | enum_range                     | enum_recv                      | enum_send                          | enum_smaller                         |
+| eqjoinsel                        | eqsel                                    | euc_cn_to_mic                     | euc_cn_to_utf8                 | euc_jis_2004_to_shift_jis_2004 | euc_jis_2004_to_utf8               | euc_jp_to_mic                        |
+| euc_jp_to_sjis                   | euc_jp_to_utf8                           | euc_kr_to_mic                     | euc_kr_to_utf8                 | euc_tw_to_big5                 | euc_tw_to_mic                      | euc_tw_to_utf8                       |
+| every                            | exist                                    | exists_all                        | exists_any                     | exp                            | factorial                          | family                               |
+| fdw_handler_in                   | fdw_handler_out                          | fetchval                          | first_value                    | float4                         | float4_accum                       | float48div                           |
+| float48eq                        | float48ge                                | float48gt                         | float48le                      | float48lt                      | float48mi                          | float48mul                           |
+| float48ne                        | float48pl                                | float4abs                         | float4div                      | float4eq                       | float4ge                           | float4gt                             |
+| float4in                         | float4larger                             | float4le                          | float4lt                       | float4mi                       | float4mul                          | float4ne                             |
+| float4out                        | float4pl                                 | float4recv                        | float4send                     | float4smaller                  | float4um                           | float4up                             |
+| float8                           | float8_accum                             | float8_avg                        | float8_collect                 | float8_corr                    | float8_covar_pop                   | float8_covar_samp                    |
+| float8_regr_accum                | float8_regr_avgx                         | float8_regr_avgy                  | float8_regr_collect            | float8_regr_intercept          | float8_regr_r2                     | float8_regr_slope                    |
+| float8_regr_sxx                  | float8_regr_sxy                          | float8_regr_syy                   | float8_stddev_pop              | float8_stddev_samp             | float8_var_pop                     | float8_var_samp                      |
+| float84div                       | float84eq                                | float84ge                         | float84gt                      | float84le                      | float84lt                          | float84mi                            |
+| float84mul                       | float84ne                                | float84pl                         | float8abs                      | float8div                      | float8eq                           | float8ge                             |
+| float8gt                         | float8in                                 | float8larger                      | float8le                       | float8lt                       | float8mi                           | float8mul                            |
+| float8ne                         | float8out                                | float8pl                          | float8recv                     | float8send                     | float8smaller                      | float8um                             |
+| float8up                         | floor                                    | flt4_mul_cash                     | flt8_mul_cash                  | fmgr_c_validator               | fmgr_internal_validator            | fmgr_sql_validator                   |
+| format                           | format_type                              | gb18030_to_utf8                   | gbk_to_utf8                    | generate_series                | generate_subscripts                | get_bit                              |
+| get_byte                         | get_current_ts_config                    | -                                 | -                              | gin_clean_pending_list         | gin_cmp_prefix                     | gin_cmp_tslexeme                     |
+| gin_extract_tsquery              | gin_extract_tsvector                     | gin_tsquery_consistent            | gin_tsquery_triconsistent      | ginarrayconsistent             | ginarrayextract                    | ginarraytriconsistent                |
+| ginbeginscan                     | ginbuild                                 | ginbuildempty                     | ginbulkdelete                  | gincostestimate                | ginendscan                         | gingetbitmap                         |
+| gininsert                        | ginmarkpos                               | ginoptions                        | ginqueryarrayextract           | ginrescan                      | ginrestrpos                        | ginvacuumcleanup                     |
+| gist_box_compress                | gist_box_consistent                      | gist_box_decompress               | gist_box_penalty               | gist_box_picksplit             | gist_box_same                      | gist_box_union                       |
+| gist_circle_compress             | gist_circle_consistent                   | gist_point_compress               | gist_point_consistent          | gist_point_distance            | gist_poly_compress                 | gist_poly_consistent                 |
+| gistbeginscan                    | gistbuild                                | gistbuildempty                    | gistbulkdelete                 | gistcostestimate               | gistendscan                        | gistgetbitmap                        |
+| gistgettuple                     | gistinsert                               | gistmarkpos                       | gistoptions                    | gistrescan                     | gistrestrpos                       | gistvacuumcleanup                    |
+| gtsquery_compress                | gtsquery_consistent                      | gtsquery_decompress               | gtsquery_penalty               | gtsquery_picksplit             | gtsquery_same                      | gtsquery_union                       |
+| gtsvector_compress               | gtsvector_consistent                     | gtsvector_decompress              | gtsvector_penalty              | gtsvector_picksplit            | gtsvector_same                     | gtsvector_union                      |
+| gtsvectorin                      | gtsvectorout                             | has_tablespace_privilege          | has_type_privilege             | hash_aclitem                   | hashbeginscan                      | hashbuild                            |
+| hashbuildempty                   | hashbulkdelete                           | hashcostestimate                  | hashendscan                    | hashgetbitmap                  | hashgettuple                       | hashinsert                           |
+| hashint2vector                   | hashint4                                 | hashint8                          | hashmacaddr                    | hashmarkpos                    | hashname                           | hashoid                              |
+| hashoidvector                    | hashoptions                              | hashrescan                        | hashrestrpos                   | hashtext                       | hashvacuumcleanup                  | hashvarlena                          |
+| host                             | hostmask                                 | iclikejoinsel                     | iclikesel                      | icnlikejoinsel                 | icnlikesel                         | icregexeqjoinsel                     |
+| icregexeqsel                     | icregexnejoinsel                         | icregexnesel                      | inet_client_addr               | inet_client_port               | inet_in                            | inet_out                             |
+| inet_recv                        | inet_send                                | inet_server_addr                  | inet_server_port               | inetand                        | inetmi                             | inetmi_int8                          |
+| inetnot                          | inetor                                   | inetpl                            | initcap                        | int2_accum                     | int2_avg_accum                     | int2_mul_cash                        |
+| int2_sum                         | int24div                                 | int24eq                           | int24ge                        | int24gt                        | int24le                            | int24lt                              |
+| int24mi                          | int24mul                                 | int24ne                           | int24pl                        | int28div                       | int28eq                            | int28ge                              |
+| int28gt                          | int28le                                  | int28lt                           | int28mi                        | int28mul                       | int28ne                            | int28pl                              |
+| int2abs                          | int2and                                  | int2div                           | int2eq                         | int2ge                         | int2gt                             | int2in                               |
+| int2larger                       | int2le                                   | int2lt                            | int2mi                         | int2mod                        | int2mul                            | int2ne                               |
+| int2not                          | int2or                                   | int2out                           | int2pl                         | int2recv                       | int2send                           | int2shl                              |
+| int2shr                          | int2smaller                              | int2um                            | int2up                         | int2vectoreq                   | int2vectorin                       | int2vectorout                        |
+| int2vectorrecv                   | int2vectorsend                           | int2xor                           | int4_accum                     | int4_avg_accum                 | int4_mul_cash                      | int4_sum                             |
+| int42div                         | int42eq                                  | int42ge                           | int42gt                        | int42le                        | int42lt                            | int42mi                              |
+| int42mul                         | int42ne                                  | int42pl                           | int48div                       | int48eq                        | int48ge                            | int48gt                              |
+| int48le                          | int48lt                                  | int48mi                           | int48mul                       | int48ne                        | int48pl                            | int4abs                              |
+| int4and                          | int4div                                  | int4eq                            | int4ge                         | int4gt                         | int4in                             | int4inc                              |
+| int4larger                       | int4le                                   | int4lt                            | int4mi                         | int4mod                        | int4mul                            | int4ne                               |
+| int4not                          | int4or                                   | int4out                           | int4pl                         | int4range                      | int4range_canonical                | int4range_subdiff                    |
+| int4recv                         | int4send                                 | int4shl                           | int4shr                        | int4smaller                    | int4um                             | int4up                               |
+| int4xor                          | int8                                     | int8_avg                          | int8_avg_accum                 | int8_avg_collect               | int8_mul_cash                      | int8_sum                             |
+| int8_sum_to_int8                 | int8_accum                               | int82div                          | int82eq                        | int82ge                        | int82gt                            | int82le                              |
+| int82lt                          | int82mi                                  | int82mul                          | int82ne                        | int82pl                        | int84div                           | int84eq                              |
+| int84ge                          | int84gt                                  | int84le                           | int84lt                        | int84mi                        | int84mul                           | int84ne                              |
+| int84pl                          | int8abs                                  | int8and                           | int8div                        | int8eq                         | int8ge                             | int8gt                               |
+| int8in                           | int8inc                                  | int8inc_any                       | int8inc_float8_float8          | int8larger                     | int8le                             | int8lt                               |
+| int8mi                           | int8mod                                  | int8mul                           | int8ne                         | int8not                        | int8or                             | int8out                              |
+| int8pl                           | int8pl_inet                              | int8range                         | int8range_canonical            | int8range_subdiff              | int8recv                           | int8send                             |
+| int8shl                          | int8shr                                  | int8smaller                       | int8um                         | int8up                         | int8xor                            | integer_pl_date                      |
+| inter_lb                         | inter_sb                                 | inter_sl                          | internal_in                    | internal_out                   | interval                           | interval_accum                       |
+| interval_avg                     | interval_cmp                             | interval_collect                  | interval_div                   | interval_eq                    | interval_ge                        | interval_gt                          |
+| interval_hash                    | interval_in                              | interval_larger                   | interval_le                    | interval_lt                    | interval_mi                        | interval_mul                         |
+| interval_ne                      | interval_out                             | interval_pl                       | interval_pl_date               | interval_pl_time               | interval_pl_timestamp              | interval_pl_timestamptz              |
+| interval_pl_timetz               | interval_recv                            | interval_send                     | interval_smaller               | interval_transform             | interval_um                        | intervaltypmodin                     |
+| intervaltypmodout                | intinterval                              | isexists                          | ishorizontal                   | iso_to_koi8r                   | iso_to_mic                         | iso_to_win1251                       |
+| iso_to_win866                    | iso8859_1_to_utf8                        | iso8859_to_utf8                   | isparallel                     | isperp                         | isvertical                         | johab_to_utf8                        |
+| json_in                          | json_out                                 | json_recv                         | json_send                      | justify_days                   | justify_hours                      | justify_interval                     |
+| koi8r_to_iso                     | koi8r_to_mic                             | koi8r_to_utf8                     | koi8r_to_win1251               | koi8r_to_win866                | koi8u_to_utf8                      | language_handler_in                  |
+| language_handler_out             | latin1_to_mic                            | latin2_to_mic                     | latin2_to_win1250              | latin3_to_mic                  | latin4_to_mic                      | like_escape                          |
+| likejoinsel                      | likesel                                  | line                              | line_distance                  | line_eq                        | line_horizontal                    | line_in                              |
+| line_interpt                     | line_intersect                           | line_out                          | line_parallel                  | line_perp                      | line_recv                          | line_send                            |
+| line_vertical                    | ln                                       | lo_close                          | lo_creat                       | lo_create                      | lo_export                          | lo_import                            |
+| lo_lseek                         | lo_open                                  | lo_tell                           | lo_truncate                    | lo_unlink                      | log                                | loread                               |
+| lower                            | lower_inc                                | lower_inf                         | lowrite                        | lpad                           | lseg                               | lseg_center                          |
+| lseg_distance                    | lseg_eq                                  | lseg_ge                           | lseg_gt                        | lseg_horizontal                | lseg_in                            | lseg_interpt                         |
+| lseg_intersect                   | lseg_le                                  | lseg_length                       | lseg_lt                        | lseg_ne                        | lseg_out                           | lseg_parallel                        |
+| lseg_perp                        | lseg_recv                                | lseg_send                         | lseg_vertical                  | ltrim                          | macaddr_and                        | macaddr_cmp                          |
+| macaddr_eq                       | macaddr_ge                               | macaddr_gt                        | macaddr_in                     | macaddr_le                     | macaddr_lt                         | macaddr_ne                           |
+| macaddr_not                      | macaddr_or                               | macaddr_out                       | macaddr_recv                   | macaddr_send                   | makeaclitem                        | masklen                              |
+| max                              | md5                                      | mic_to_big5                       | mic_to_euc_cn                  | mic_to_euc_jp                  | mic_to_euc_kr                      | mic_to_euc_tw                        |
+| mic_to_iso                       | mic_to_koi8r                             | mic_to_latin1                     | mic_to_latin2                  | mic_to_latin3                  | mic_to_latin4                      | mic_to_sjis                          |
+| mic_to_win1250                   | mic_to_win1251                           | mic_to_win866                     | min                            | mktinterval                    | money                              | mul_d_interval                       |
+| name                             | nameeq                                   | namege                            | namegt                         | nameiclike                     | nameicnlike                        | nameicregexeq                        |
+| nameicregexne                    | namein                                   | namele                            | namelike                       | namelt                         | namene                             | namenlike                            |
+| nameout                          | namerecv                                 | nameregexeq                       | nameregexne                    | namesend                       | neqjoinsel                         | neqsel                               |
+| network_cmp                      | network_eq                               | network_ge                        | network_gt                     | network_le                     | network_lt                         | network_ne                           |
+| network_sub                      | network_subeq                            | network_sup                       | network_supeq                  | nlikejoinsel                   | nlikesel                           | numeric                              |
+| numeric_abs                      | numeric_accum                            | numeric_add                       | numeric_avg                    | numeric_avg_accum              | numeric_avg_collect                | numeric_cmp                          |
+| numeric_collect                  | numeric_div                              | numeric_div_trunc                 | numeric_eq                     | numeric_exp                    | numeric_fac                        | numeric_ge                           |
+| numeric_gt                       | numeric_in                               | numeric_inc                       | numeric_larger                 | numeric_le                     | numeric_ln                         | numeric_log                          |
+| numeric_lt                       | numeric_mod                              | numeric_mul                       | numeric_ne                     | numeric_out                    | numeric_power                      | numeric_recv                         |
+| numeric_send                     | numeric_smaller                          | numeric_sortsupport               | numeric_sqrt                   | numeric_stddev_pop             | numeric_stddev_samp                | numeric_sub                          |
+| numeric_transform                | numeric_uminus                           | numeric_uplus                     | numeric_var_pop                | numeric_var_samp               | numerictypmodin                    | numerictypmodout                     |
+| numrange_subdiff                 | oid                                      | oideq                             | oidge                          | oidgt                          | oidin                              | oidlarger                            |
+| oidle                            | oidlt                                    | oidne                             | oidout                         | oidrecv                        | oidsend                            | oidsmaller                           |
+| oidvectoreq                      | oidvectorge                              | oidvectorgt                       | oidvectorin                    | oidvectorle                    | oidvectorlt                        | oidvectorne                          |
+| oidvectorout                     | oidvectorrecv                            | oidvectorsend                     | oidvectortypes                 | on_pb                          | on_pl                              | on_ppath                             |
+| on_ps                            | on_sb                                    | on_sl                             | opaque_in                      | opaque_out                     | ordered_set_transition             | overlaps                             |
+| overlay                          | path                                     | path_add                          | path_add_pt                    | path_center                    | path_contain_pt                    | path_distance                        |
+| path_div_pt                      | path_in                                  | path_inter                        | path_length                    | path_mul_pt                    | path_n_eq                          | path_n_ge                            |
+| path_n_gt                        | path_n_le                                | path_n_lt                         | path_npoints                   | path_out                       | path_recv                          | path_send                            |
+| path_sub_pt                      | percentile_cont                          | percentile_cont_float8_final      | percentile_cont_interval_final | pg_char_to_encoding            | pg_cursor                          | pg_encoding_max_length               |
+| pg_encoding_to_char              | pg_extension_config_dump                 | -                                 | -                              | pg_node_tree_in                | pg_node_tree_out                   | pg_node_tree_recv                    |
+| pg_node_tree_send                | pg_prepared_statement                    | pg_prepared_xact                  | -                              | -                              | pg_show_all_settings               | pg_stat_get_bgwriter_stat_reset_time |
+| pg_stat_get_buf_fsync_backend    | pg_stat_get_checkpoint_sync_time         | pg_stat_get_checkpoint_write_time | pg_stat_get_db_blk_read_time   | pg_stat_get_db_blk_write_time  | pg_stat_get_db_conflict_all        | pg_stat_get_db_conflict_bufferpin    |
+| pg_stat_get_db_conflict_snapshot | pg_stat_get_db_conflict_startup_deadlock | pg_switch_xlog                    | xpath                          | pg_timezone_abbrevs            | pg_timezone_names                  | -                                    |
+| plpgsql_call_handler             | plpgsql_inline_handler                   | plpgsql_validator                 | point_above                    | point_add                      | point_below                        | point_distance                       |
+| point_div                        | point_eq                                 | point_horiz                       | point_in                       | point_left                     | point_mul                          | point_ne                             |
+| point_out                        | point_recv                               | point_right                       | point_send                     | point_sub                      | point_vert                         | poly_above                           |
+| poly_below                       | poly_center                              | poly_contain                      | poly_contain_pt                | poly_contained                 | poly_distance                      | poly_in                              |
+| poly_left                        | poly_npoints                             | poly_out                          | poly_overabove                 | poly_overbelow                 | poly_overlap                       | poly_overleft                        |
+| poly_overright                   | poly_recv                                | poly_right                        | poly_same                      | poly_send                      | polygon                            | position                             |
+| positionjoinsel                  | positionsel                              | postgresql_fdw_validator          | pow                            | power                          | prsd_end                           | prsd_headline                        |
+| prsd_lextype                     | prsd_nexttoken                           | prsd_start                        | pt_contained_circle            | pt_contained_poly              | query_to_xml                       | query_to_xml_and_xmlschema           |
+| query_to_xmlschema               | quote_ident                              | quote_literal                     | quote_nullable                 | radians                        | radius                             | random                               |
+| range_adjacent                   | range_after                              | range_before                      | range_cmp                      | range_contained_by             | range_contains                     | range_contains_elem                  |
+| range_eq                         | range_ge                                 | range_gist_compress               | range_gist_consistent          | range_gist_decompress          | range_gist_penalty                 | range_gist_picksplit                 |
+| range_gist_same                  | range_gist_union                         | range_gt                          | range_in                       | range_intersect                | range_le                           | range_lt                             |
+| range_minus                      | range_ne                                 | range_out                         | range_overlaps                 | range_overleft                 | range_overright                    | range_recv                           |
+| range_send                       | range_typanalyze                         | range_union                       | rank                           | record_eq                      | record_ge                          | record_gt                            |
+| record_in                        | record_le                                | record_lt                         | record_ne                      | record_out                     | record_recv                        | record_send                          |
+| regclass                         | regclassin                               | regclassout                       | regclassrecv                   | regclasssend                   | regconfigin                        | regconfigout                         |
+| regconfigrecv                    | regconfigsend                            | regdictionaryin                   | regdictionaryout               | regdictionaryrecv              | regdictionarysend                  | regexeqjoinsel                       |
+| regexeqsel                       | regexnejoinsel                           | regexnesel                        | regexp_matches                 | regexp_replace                 | regexp_split_to_array              | regexp_split_to_table                |
+| regoperatorin                    | regoperatorout                           | regoperatorrecv                   | regoperatorsend                | regoperin                      | regoperout                         | regoperrecv                          |
+| regopersend                      | regprocedurein                           | regprocedureout                   | regprocedurerecv               | regproceduresend               | regprocin                          | regprocout                           |
+| regprocrecv                      | regprocsend                              | regr_avgx                         | regr_avgy                      | regr_count                     | regr_intercept                     | regr_r2                              |
+| regr_slope                       | regr_sxx                                 | regr_sxy                          | regr_syy                       | regtypein                      | regtypeout                         | regtyperecv                          |
+| regtypesend                      | reltime                                  | reltimeeq                         | reltimege                      | reltimegt                      | reltimein                          | reltimele                            |
+| reltimelt                        | reltimene                                | reltimeout                        | reltimerecv                    | reltimesend                    | repeat                             | replace                              |
+| reverse                          | RI_FKey_cascade_del                      | RI_FKey_cascade_upd               | RI_FKey_check_ins              | RI_FKey_check_upd              | RI_FKey_noaction_del               | RI_FKey_noaction_upd                 |
+| RI_FKey_restrict_del             | RI_FKey_restrict_upd                     | RI_FKey_setdefault_del            | RI_FKey_setdefault_upd         | RI_FKey_setnull_del            | RI_FKey_setnull_upd                | right                                |
+| round                            | row_number                               | row_to_json                       | rpad                           | rtrim                          | scalargtjoinsel                    | scalargtsel                          |
+| scalarltjoinsel                  | scalarltsel                              | schema_to_xml                     | schema_to_xml_and_xmlschema    | schema_to_xmlschema            | session_user                       | set_bit                              |
+| set_byte                         | set_config                               | set_masklen                       | shift_jis_2004_to_euc_jis_2004 | shift_jis_2004_to_utf8         | sjis_to_euc_jp                     | sjis_to_mic                          |
+| sjis_to_utf8                     | smgrin                                   | smgrout                           | spg_kd_choose                  | spg_kd_config                  | spg_kd_inner_consistent            | spg_kd_picksplit                     |
+| spg_quad_choose                  | spg_quad_config                          | spg_quad_inner_consistent         | spg_quad_leaf_consistent       | spg_quad_picksplit             | spg_text_choose                    | spg_text_config                      |
+| spg_text_inner_consistent        | spg_text_leaf_consistent                 | spg_text_picksplit                | spgbeginscan                   | spgbuild                       | spgbuildempty                      | spgbulkdelete                        |
+| spgcanreturn                     | spgcostestimate                          | spgendscan                        | spggetbitmap                   | spggettuple                    | spginsert                          | spgmarkpos                           |
+| spgoptions                       | spgrescan                                | spgrestrpos                       | spgvacuumcleanup               | stddev                         | stddev_pop                         | stddev_samp                          |
+| string_agg                       | string_agg_finalfn                       | string_agg_transfn                | strip                          | sum                            | suppress_redundant_updates_trigger | table_to_xml                         |
+| table_to_xml_and_xmlschema       | table_to_xmlschema                       | tan                               | text                           | text_ge                        | text_gt                            | text_larger                          |
+| text_le                          | text_lt                                  | text_pattern_ge                   | text_pattern_gt                | text_pattern_le                | text_pattern_lt                    | text_smaller                         |
+| textanycat                       | textcat                                  | texteq                            | texticlike                     | texticnlike                    | texticregexeq                      | texticregexne                        |
+| textin                           | textlike                                 | textne                            | textnlike                      | textout                        | textrecv                           | textregexeq                          |
+| textregexne                      | textsend                                 | thesaurus_init                    | thesaurus_lexize               | tideq                          | tidge                              | tidgt                                |
+| tidin                            | tidlarger                                | tidle                             | tidlt                          | tidne                          | tidout                             | tidrecv                              |
+| tidsend                          | tidsmaller                               | time                              | time_cmp                       | time_eq                        | time_ge                            | time_gt                              |
+| time_hash                        | time_in                                  | time_larger                       | time_le                        | time_lt                        | time_mi_interval                   | time_mi_time                         |
+| time_ne                          | time_out                                 | time_pl_interval                  | time_recv                      | time_send                      | time_smaller                       | time_transform                       |
+| timedate_pl                      | timemi                                   | timepl                            | timestamp                      | timestamp_cmp                  | timestamp_cmp_date                 | timestamp_cmp_timestamptz            |
+| timestamp_eq                     | timestamp_eq_date                        | timestamp_eq_timestamptz          | timestamp_ge                   | timestamp_ge_date              | timestamp_ge_timestamptz           | timestamp_gt                         |
+| timestamp_gt_date                | timestamp_gt_timestamptz                 | timestamp_hash                    | timestamp_in                   | timestamp_larger               | timestamp_le                       | timestamp_le_date                    |
+| timestamp_le_timestamptz         | timestamp_lt                             | timestamp_lt_date                 | timestamp_lt_timestamptz       | timestamp_mi                   | timestamp_mi_interval              | timestamp_ne                         |
+| timestamp_ne_date                | timestamp_ne_timestamptz                 | timestamp_out                     | timestamp_pl_interval          | timestamp_recv                 | timestamp_send                     | timestamp_smaller                    |
+| timestamp_sortsupport            | timestamp_transform                      | timestamptypmodin                 | timestamptypmodout             | timestamptz                    | timestamptz_cmp                    | timestamptz_cmp_date                 |
+| timestamptz_cmp_timestamp        | timestamptz_eq                           | timestamptz_eq_date               | timestamptz_eq_timestamp       | timestamptz_ge                 | timestamptz_ge_date                | timestamptz_ge_timestamp             |
+| timestamptz_gt                   | timestamptz_gt_date                      | timestamptz_gt_timestamp          | timestamptz_in                 | timestamptz_larger             | timestamptz_le                     | timestamptz_le_date                  |
+| timestamptz_le_timestamp         | timestamptz_lt                           | timestamptz_lt_date               | timestamptz_lt_timestamp       | timestamptz_mi                 | timestamptz_mi_interval            | timestamptz_ne                       |
+| timestamptz_ne_date              | timestamptz_ne_timestamp                 | timestamptz_out                   | timestamptz_pl_interval        | timestamptz_recv               | timestamptz_send                   | timestamptz_smaller                  |
+| timestamptztypmodin              | timestamptztypmodout                     | timetypmodin                      | timetypmodout                  | timetz                         | timetz_cmp                         | timetz_eq                            |
+| timetz_ge                        | timetz_gt                                | timetz_hash                       | timetz_in                      | timetz_larger                  | timetz_le                          | timetz_lt                            |
+| timetz_mi_interval               | timetz_ne                                | timetz_out                        | timetz_pl_interval             | timetz_recv                    | timetz_send                        | timetz_smaller                       |
+| timetzdate_pl                    | timetztypmodin                           | timetztypmodout                   | timezone（2069）               | timezone（1159)                | timezone（2037）                   | timezone (2070)                      |
+| timezone (1026)                  | timezone (2038)                          | tintervalct                       | tintervaleq                    | tintervalge                    | tintervalgt                        | tintervalin                          |
+| tintervalle                      | tintervalleneq                           | tintervallenge                    | tintervallengt                 | tintervallenle                 | tintervallenlt                     | tintervallenne                       |
+| tintervallt                      | tintervalne                              | tintervalout                      | tintervalov                    | tintervalrecv                  | tintervalsame                      | tintervalsend                        |
+| tintervalstart                   | to_ascii（1845）                         | to_ascii（1847）                  | to_ascii（1846）               | trigger_in                     | trigger_out                        | ts_match_qv                          |
+| ts_match_tq                      | ts_match_tt                              | ts_match_vq                       | ts_rank                        | ts_rank_cd                     | ts_rewrite                         | ts_stat                              |
+| ts_token_type                    | ts_typanalyze                            | tsmatchjoinsel                    | tsmatchsel                     | tsq_mcontained                 | tsq_mcontains                      | tsquery_and                          |
+| tsquery_cmp                      | tsquery_eq                               | tsquery_ge                        | tsquery_gt                     | tsquery_le                     | tsquery_lt                         | tsquery_ne                           |
+| tsquery_not                      | tsquery_or                               | tsqueryin                         | tsqueryout                     | tsqueryrecv                    | tsquerysend                        | tsrange                              |
+| tsrange_subdiff                  | tstzrange                                | tstzrange_subdiff                 | tsvector_cmp                   | tsvector_concat                | tsvector_eq                        | tsvector_ge                          |
+| tsvector_gt                      | tsvector_le                              | tsvector_lt                       | tsvector_ne                    | tsvector_update_trigger        | tsvector_update_trigger_column     | tsvectorin                           |
+| tsvectorout                      | tsvectorrecv                             | tsvectorsend                      | txid_current                   | txid_current_snapshot          | txid_snapshot_in                   | txid_snapshot_out                    |
+| txid_snapshot_recv               | txid_snapshot_send                       | txid_snapshot_xip                 | txid_snapshot_xmax             | txid_snapshot_xmin             | txid_visible_in_snapshot           | uhc_to_utf8                          |
+| unique_key_recheck               | unknownin                                | unknownout                        | unknownrecv                    | unknownsend                    | unnest                             | utf8_to_big5                         |
+| utf8_to_euc_cn                   | utf8_to_euc_jis_2004                     | utf8_to_euc_jp                    | utf8_to_euc_kr                 | utf8_to_euc_tw                 | utf8_to_gb18030                    | utf8_to_gbk                          |
+| utf8_to_iso8859                  | utf8_to_iso8859_1                        | utf8_to_johab                     | utf8_to_koi8r                  | utf8_to_koi8u                  | utf8_to_shift_jis_2004             | utf8_to_sjis                         |
+| utf8_to_uhc                      | utf8_to_win                              | uuid_cmp                          | uuid_eq                        | uuid_ge                        | uuid_gt                            | uuid_hash                            |
+| uuid_in                          | uuid_le                                  | uuid_lt                           | uuid_ne                        | uuid_out                       | uuid_recv                          | uuid_send                            |
+| var_pop                          | var_samp                                 | varbit                            | varbit_in                      | varbit_out                     | varbit_recv                        | varbit_send                          |
+| varbit_transform                 | varbitcmp                                | varbiteq                          | varbitge                       | varbitgt                       | varbitle                           | varbitlt                             |
+| varbitne                         | varbittypmodin                           | varbittypmodout                   | varchar                        | varchar_transform              | varcharin                          | varcharout                           |
+| varcharrecv                      | varcharsend                              | varchartypmodin                   | varchartypmodout               | variance                       | void_in                            | void_out                             |
+| void_recv                        | void_send                                | win_to_utf8                       | win1250_to_latin2              | win1250_to_mic                 | win1251_to_iso                     | win1251_to_koi8r                     |
+| win1251_to_mic                   | win1251_to_win866                        | win866_to_iso                     | win866_to_koi8r                | win866_to_mic                  | win866_to_win1251                  | xideq                                |
+| xideqint4                        | xidin                                    | xidout                            | xidrecv                        | xidsend                        | xml                                | xml_in                               |
+| xml_is_well_formed               | xml_is_well_formed_content               | xml_is_well_formed_document       | xml_out                        | xml_recv                       | xml_send                           | xmlagg                               |
+| xmlcomment                       | xmlconcat2                               | xmlexists                         | xmlvalidate                    | pg_notify                      | pg_stat_get_wal_receiver           | -                                    |
+
+下述列表为MogDB Kernel实现系统内部功能所使用的函数，不推荐使用，若需使用，请联系云和恩墨技术支持工程师。
+
+- pv_compute_pool_workload()
+
+    描述：提供云上加速集群当前负载信息。
+
+    返回值类型：record
+
+- locktag_decode(locktag text)
+
+    描述：从locktag中解析锁的具体信息。
+
+    返回值类型：text
+
+- smgreq(a smgr, b smgr)
+
+  描述：比较两个smgr是否一样。
+
+  参数：smgr, smgr
+
+  返回值类型：boolean
+
+- smgrne(a smgr, b smgr)
+
+  描述：判断两个smgr是否不一样。
+
+  参数：smgr, smgr
+
+  返回值类型：boolean
+
+- xidin4
+
+  描述：输入4字节的xid。
+
+  参数：cstring
+
+  返回值类型：xid32
+
+- set_hashbucket_info
+
+  描述：设置哈希桶信息。
+
+  参数：text
+
+  返回值类型：boolean
+
+- hs_concat
+
+  描述：拼接两个hstore类型数据。
+
+  参数：hstore, hstore
+
+  返回值类型：hstore
+
+- hs_contained
+
+  描述：判断两个hstore类型数据是否包含，返回值布尔类型。
+
+  参数：hstore, hstore
+
+  返回值类型：boolean
+
+- hs_contains
+
+  描述：判断两个hstore类型数据是否包含，返回值布尔类型。
+
+  参数：hstore, hstore
+
+  返回值类型：boolean
+
+- hstore
+
+  描述：将参数转为hstore类型。
+
+  参数：text, text
+
+  返回值类型：hstore
+
+- hstore_in
+
+  描述：以string格式接收hstore数据。
+
+  参数：cstring
+
+  返回值类型：hstore
+
+- hstore_out
+
+  描述：以string格式发送hstore数据。
+
+  参数：hstore
+
+  返回值类型：cstring
+
+- hstore_send
+
+  描述：以bytea格式发送hstore数据。
+
+  参数：hstore
+
+  返回值类型：bytea
+
+- hstore_to_array
+
+  描述：以text数组格式发送hstore数据。
+
+  参数：hstore
+
+  返回值类型：text[]
+
+- hstore_to_matrix
+
+  描述：以text数组格式发送hstore数据。
+
+  参数：hstore
+
+  返回值类型：text[]
+
+- hstore_version_diag
+
+  描述：以integer数组格式发送hstore数据。
+
+  参数：hstore
+
+  返回值类型：integer
+
+- int1send
+
+  描述：将无符号一字节整数打包放入内部数据缓冲流。
+
+  参数：tinyint
+
+  返回值类型：bytea
+
+- isdefined
+
+  描述：判断指定key是否存在。
+
+  参数：hstore, text
+
+  返回值类型：boolean
+
+- listagg
+
+  描述：list类型agg聚集函数。
+
+  参数：smallint, text
+
+  返回值类型：text
+
+- log_fdw_validator
+
+  描述：验证函数。
+
+  参数：text[], oid
+
+  返回值类型：void
+
+- nvarchar2typmodin
+
+  描述：获取varchar的typmod信息。
+
+  参数：cstring[]
+
+  返回值类型：integer
+
+- nvarchar2typmodout
+
+  描述：获取varchar的typmod信息，并构造字符串返回。
+
+  参数：integer
+
+  返回值类型：cstring
+
+- read_disable_conn_file
+
+  描述：读取禁止的连接文件。
+
+  参数：nan
+
+  返回值类型：disconn_mode text, disconn_host text, disconn_port text, local_host text, local_port text, redo_finished text
+
+- regex_like_m
+
+  描述：正则匹配，判断字符串是否符合给定的正则表达式。
+
+  参数：text, text
+
+  返回值类型：boolean
+
+- update_pgjob
+
+  描述：更新job。
+
+  参数：bigint, “char”, bigint, timestamp without time zone, timestamp without time zone, timestamp without time zone, timestamp without time zone, timestamp without time zone, smallint
+
+  返回值类型：void
+
+- enum_cmp
+
+  描述：枚举类比较函数，用于判断两个枚举类是否相等，以及相对大小。
+
+  参数：anyenum, anyenum
+
+  返回值类型：integer
+
+- enum_eq
+
+  描述：枚举类比较函数，用于实现=符号。
+
+  参数：anyenum, anyenum
+
+  返回值类型：boolean
+
+- enum_first
+
+  描述：返回枚举类中的第一个元素。
+
+  参数：anyenum
+
+  返回值类型：anyenum
+
+- enum_ge
+
+  描述：枚举类比较函数，用于实现>=符号。
+
+  参数：anyenum, anyenum
+
+  返回值类型：boolean
+
+- enum_gt
+
+  描述：枚举类比较函数，用于实现>符号。
+
+  参数：anyenum, anyenum
+
+  返回值类型：boolean
+
+- enum_in
+
+  描述：枚举类比较函数，用于判断元素是否在枚举类中。
+
+  参数：cstring, oid
+
+  返回值类型：anyenum
+
+- enum_larger
+
+  描述：枚举类比较函数，用于实现>符号。
+
+  参数：anyenum, anyenum
+
+  返回值类型：anyenum
+
+- enum_last
+
+  描述：返回枚举类中的最后一个元素。
+
+  参数：anyenum
+
+  返回值类型：anyenum
+
+- enum_le
+
+  描述：枚举类比较函数，用于实现<=符号。
+
+  参数：anyenum, anyenum
+
+  返回值类型：boolean
+
+- enum_lt
+
+  描述：枚举类比较函数，用于实现<符号。
+
+  参数：anyenum, anyenum
+
+  返回值类型：boolean
+
+- enum_smaller
+
+  描述：枚举类比较函数，用于实现<符号。
+
+  参数：anyenum, anyenum
+
+  返回值类型：boolean
+
+- node_oid_name
+
+  描述：不支持。
+
+  参数：oid
+
+  返回值类型：cstring
+
+- pg_buffercache_pages
+
+  描述：从共享buffer缓存里读取数据。
+
+  参数：nan
+
+  返回值类型：bufferid integer, relfilenode oid, bucketid smallint, reltablespace oid, reldatabase oid, relforknumber smallint, relblocknumber bigint, isdirty boolean, usage_count smallint
+
+- pg_check_xidlimit
+
+  描述：判断nextxid是否>= xidwarnlimit。
+
+  参数：nan
+
+  返回值类型：boolean
+
+- pg_comm_delay
+
+  描述：展示单个DN的通信库时延状态。
+
+  参数：nan
+
+  返回值类型：text, text, integer, integer, integer, integer
+
+- pg_comm_recv_stream
+
+  描述：展示单个DN上所有的通信库接收流状态。
+
+  参数：nan
+
+  返回值类型：text, bigint, text, bigint, integer, integer, integer, text, bigint, integer, integer, integer, bigint, bigint, bigint, bigint, bigint
+
+- pg_comm_send_stream
+
+  描述：展示单个DN上所有的通信库发送流状态。
+
+  参数：nan
+
+  返回值类型：text, bigint, text, bigint, integer, integer, integer, text, bigint, integer, integer, integer, bigint, bigint, bigint, bigint, bigint
+
+- pg_comm_status
+
+  描述： 展示单个DN的通信状态。
+
+  参数：nan
+
+  返回值类型：text, integer, integer, bigint, bigint, bigint, bigint, bigint, integer, integer, integer, integer, integer
+
+- pg_log_comm_status
+
+  描述：在DN上打印一些log。
+
+  参数：nan
+
+  返回值类型：boolean
+
+- pg_parse_clog
+
+  描述：解析clog获取xid的status。
+
+  参数：nan
+
+  返回值类型：xid xid, status text
+
+- pg_pool_ping
+
+  描述：设置PoolerPing。
+
+  参数：boolean
+
+  返回值类型：SETOF boolean
+
+- pg_resume_bkp_flag
+
+  描述：用于备份恢复获取delay xlong标志。
+
+  参数：slot_name name
+
+  返回值类型：start_backup_flag boolean, to_delay boolean, ddl_delay_recycle_ptr text, rewind_time text
+
+- psortoptions
+
+  描述：返回psort属性。
+
+  参数：text[], boolean
+
+  返回值类型：bytea
+
+- xideq4
+
+  描述：对比两个xid类型的值是否相等。
+
+  参数：xid32, xid32
+
+  返回值类型：boolean
+
+- xideqint8
+
+  描述：对比xid类型和int8类型的值是否相等。
+
+  参数：xid, bigint
+
+  返回值类型：boolean
+
+- xidlt
+
+  描述：返回xid1 < xid2是否成立。
+
+  参数：xid, xid
+
+  返回值类型：boolean
+
+- xidlt4
+
+  描述：返回xid1 < xid2是否成立。
+
+  参数：xid32, xid32
+
+  返回值类型：boolean
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/29.1-dynamic-data-masking-functions.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/29.1-dynamic-data-masking-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..73f3748b79f6929ff6648fa3277d12910e31afba
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/29.1-dynamic-data-masking-functions.md
@@ -0,0 +1,60 @@
+---
+title: 动态数据脱敏函数
+summary: 动态数据脱敏函数
+author: Guo Huan
+date: 2021-10-28
+---
+
+# 动态数据脱敏函数
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> 该函数为内部功能调用函数，详见“数据库安全-动态数据脱敏机制”章节。
+
+- creditcardmasking(col text, letter char default 'x')
+
+  描述：将col字符串后四位之前的数字使用letter替换。
+
+  参数：待替换的字符串、替换字符。
+
+  返回值类型：text
+
+- basicmailmasking(col text, letter char default 'x')
+
+  描述：将col字符串中第一个'@'之前的字符使用letter替换。
+
+  参数：待替换的字符串、替换字符。
+
+  返回值类型：text
+
+- fullmailmasking(col text, letter char default 'x')
+
+  描述：将col字符串中出现最后一个'.'之前的字符(除'@'外)使用letter替换。
+
+  参数：待替换的字符串、替换字符。
+
+  返回值类型：text
+
+- alldigitsmasking(col text, letter char default '0')
+
+  描述：将col字符串中出现的数字使用letter替换。
+
+  参数：待替换的字符串、替换字符。
+
+  返回值类型：text
+
+- shufflemasking(col text)
+
+  描述：将col字符串中的字符乱序排列。
+
+  参数：待替换的字符串、替换字符。
+
+  返回值类型：text
+
+- randommasking(col text)
+
+  描述：将col字符串中的字符随机化。
+
+  参数：待替换的字符串、替换字符。
+
+  返回值类型：text
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/3-character-processing-functions-and-operators.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/3-character-processing-functions-and-operators.md
new file mode 100644
index 0000000000000000000000000000000000000000..5a0ddfe2235959ef270f8487cf05fed4a2c0986d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/3-character-processing-functions-and-operators.md
@@ -0,0 +1,1613 @@
+---
+title: 字符处理函数和操作符
+summary: 字符处理函数和操作符
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 字符处理函数和操作符
+
+MogDB提供的字符处理函数和操作符主要用于字符串与字符串、字符串与非字符串之间的连接，以及字符串的模式匹配操作。
+
+- bit_length(string)
+
+  描述：字符串的位数。
+
+  返回值类型：int
+
+  示例：
+
+  ```sql
+    mogdb=# SELECT bit_length('world');
+     bit_length
+    ------------
+             40
+    (1 row)
+  ```
+
+- btrim(string text [, characters text])
+
+  描述：从string开头和结尾删除只包含characters中字符（缺省是空白）的最长字符串。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT btrim('sring' , 'ing');
+   btrim
+  -------
+   sr
+  (1 row)
+  ```
+
+- char_length(string)或character_length(string)
+
+  描述：字符串中的字符个数。
+
+  返回值类型：int
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT char_length('hello');
+   char_length
+  -------------
+             5
+  (1 row)
+  ```
+
+- instr(text,text,int,int)
+
+  描述：instr(string1,string2,int1,int2)返回在string1中从int1位置开始匹配到第int2次string2的位置，第一个int表示开始匹配起始位置，第二个int表示匹配的次数。
+
+  返回值类型：int
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT instr( 'abcdabcdabcd', 'bcd', 2, 2 );
+   instr
+  -------
+       6
+  (1 row)
+  ```
+
+- lengthb(text/bpchar)
+
+  描述：获取指定字符串的字节数。
+
+  返回值类型：int
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT lengthb('hello');
+   lengthb
+  ---------
+         5
+  (1 row)
+  ```
+
+- left(str text, n int)
+
+  描述：返回字符串的前n个字符。当n是负数时，返回除最后|n|个字符以外的所有字符。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT left('abcde', 2);s
+   left
+  ------
+   ab
+  (1 row)
+  ```
+
+- length(string bytea, encoding name )
+
+  描述：指定encoding编码格式的string的字符数。在这个编码格式中，string必须是有效的。
+
+  返回值类型：int
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT length('jose', 'UTF8');
+   length
+  --------
+        4
+  (1 row)
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  >
+  > 如果是查询bytea类型的长度，指定utf8编码时，最大长度只能为536870888。
+
+- lpad(string text, length int [, fill text])
+
+  描述：通过填充字符fill（缺省时为空白），把string填充为length长度。如果string已经比length长则将其尾部截断。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT lpad('hi', 5, 'xyza');
+   lpad
+  -------
+   xyzhi
+  (1 row)
+  ```
+
+- notlike(x bytea name text, y bytea text)
+
+    描述：比较x和y是否不一致。
+
+    返回值类型：bool
+
+    示例：
+
+    ```sql
+    mogdb=# SELECT notlike(1,2);
+        notlike
+    --------------
+                t
+    (1 row)
+    mogdb=# SELECT notlike(1,1);
+        notlike
+    --------------
+                f
+    (1 row)
+    ```
+
+- octet_length(string)
+
+  描述：字符串中的字节数。
+
+  返回值类型：int
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT octet_length('jose');
+   octet_length
+  --------------
+              4
+  (1 row)
+  ```
+
+- overlay(string placing string FROM int [for int])
+
+  描述：替换子字符串。FROM int表示从第一个string的第几个字符开始替换，for int表示替换第一个string的字符数目。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT overlay('hello' placing 'world' from 2 for 3 );
+   overlay
+  ---------
+   hworldo
+  (1 row)
+  ```
+
+- position(substring in string)
+
+  描述：指定子字符串的位置。字符串区分大小写。
+
+  返回值类型：int，字符串不存在时返回0。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT position('ing' in 'string');
+   position
+  ----------
+          4
+  (1 row)
+  ```
+
+- pg_client_encoding()
+
+  描述：当前客户端编码名称。
+
+  返回值类型：name
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT pg_client_encoding();
+   pg_client_encoding
+  --------------------
+   UTF8
+  (1 row)
+  ```
+
+- quote_ident(string text)
+
+  描述：返回适用于SQL语句的标识符形式（使用适当的引号进行界定）。只有在必要的时候才会添加引号（字符串包含非标识符字符或者会转换大小写的字符）。返回值中嵌入的引号都写了两次。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT quote_ident('hello world');
+   quote_ident
+  --------------
+   "hello world"
+  (1 row)
+  ```
+
+- quote_literal(string text)
+
+  描述：返回适用于在SQL语句里当作文本使用的形式（使用适当的引号进行界定）。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT quote_literal('hello');
+   quote_literal
+  ---------------
+   'hello'
+  (1 row)
+  ```
+
+  如果出现如下写法，text文本将进行转义。
+
+  ```sql
+  mogdb=# SELECT quote_literal(E'O\'hello');
+   quote_literal
+  ---------------
+   'O''hello'
+  (1 row)
+  ```
+
+  如果出现如下写法，反斜杠会写入两次。
+
+  ```sql
+  mogdb=# SELECT quote_literal('O\hello');
+   quote_literal
+  ---------------
+   E'O\\hello'
+  (1 row)
+  ```
+
+  如果参数为NULL，返回空。如果参数可能为null，通常使用函数quote_nullable更适用。
+
+  ```sql
+  mogdb=# SELECT quote_literal(NULL);
+   quote_literal
+  ---------------
+
+  (1 row)
+  ```
+
+- quote_literal(value anyelement)
+
+  描述：将给定的值强制转换为text，加上引号作为文本。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT quote_literal(42.5);
+   quote_literal
+  ---------------
+   '42.5'
+  (1 row)
+  ```
+
+  如果出现如下写法，定值将进行转义。
+
+  ```sql
+  mogdb=# SELECT quote_literal(E'O\'42.5');
+   quote_literal
+  ---------------
+   '0''42.5'
+  (1 row)
+  ```
+
+  如果出现如下写法，反斜杠会写入两次。
+
+  ```sql
+  mogdb=# SELECT quote_literal('O\42.5');
+   quote_literal
+  ---------------
+   E'O\\42.5'
+  (1 row)
+  ```
+
+- quote_nullable(string text)
+
+  描述：返回适用于在SQL语句里当作字符串使用的形式（使用适当的引号进行界定）。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT quote_nullable('hello');
+   quote_nullable
+  ----------------
+   'hello'
+  (1 row)
+  ```
+
+  如果出现如下写法，text文本将进行转义。
+
+  ```sql
+  mogdb=# SELECT quote_nullable(E'O\'hello');
+   quote_nullable
+  ----------------
+   'O''hello'
+  (1 row)
+  ```
+
+  如果出现如下写法，反斜杠会写入两次。
+
+  ```sql
+  mogdb=# SELECT quote_nullable('O\hello');
+   quote_nullable
+  ----------------
+   E'O\\hello'
+  (1 row)
+  ```
+
+  如果参数为NULL，返回NULL。
+
+  ```sql
+  mogdb=# SELECT quote_nullable(NULL);
+   quote_nullable
+  ----------------
+   NULL
+  (1 row)
+  ```
+
+- quote_nullable(value anyelement)
+
+  描述：将给定的参数值转化为text，加上引号作为文本。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT quote_nullable(42.5);
+   quote_nullable
+  ----------------
+   '42.5'
+  (1 row)
+  ```
+
+  如果出现如下写法，定值将进行转义。
+
+  ```sql
+  mogdb=# SELECT quote_nullable(E'O\'42.5');
+   quote_nullable
+  ----------------
+   'O''42.5'
+  (1 row)
+  ```
+
+  如果出现如下写法，反斜杠会写入两次。
+
+  ```sql
+  mogdb=# SELECT quote_nullable('O\42.5');
+   quote_nullable
+  ----------------
+   E'O\\42.5'
+  (1 row)
+  ```
+
+  如果参数为NULL，返回NULL。
+
+  ```sql
+  mogdb=# SELECT quote_nullable(NULL);
+   quote_nullable
+  ----------------
+   NULL
+  (1 row)
+  ```
+
+- substring_inner(string [from int] [for int])
+
+    描述：截取子字符串，from int表示从第几个字符开始截取，for int表示截取几个字节。
+
+    返回值类型：text
+
+    示例：
+
+    ```sql
+    mogdb=# select substring_inner('adcde', 2,3);
+     substring_inner
+    -----------------
+     dcd
+    (1 row)
+    ```
+
+- substring(string [from int] [for int])
+
+  描述：截取子字符串，from int表示从第几个字符开始截取，for int表示截取几个字节。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT substring('Thomas' from 2 for 3);
+   substring
+  -----------
+   hom
+  (1 row)
+  ```
+
+- substring(string from *pattern*)
+
+  描述：截取匹配POSIX正则表达式的子字符串。如果没有匹配它返回空值，否则返回文本中匹配模式的那部分。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT substring('Thomas' from '...$');
+   substring
+  -----------
+   mas
+  (1 row)
+  mogdb=# SELECT substring('foobar' from 'o(.)b');
+   result
+  --------
+   o
+  (1 row)
+  mogdb=# SELECT substring('foobar' from '(o(.)b)');
+   result
+  --------
+   oob
+  (1 row)
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  > 如果POSIX正则表达式模式包含任何圆括号，那么将返回匹配第一对子表达式（对应第一个左圆括号的) 的文本。如果你想在表达式里使用圆括号而又不想导致这个例外，那么你可以在整个表达式外边放上一对圆括号。
+
+- substring(string from *pattern* for *escape*)
+
+  描述：截取匹配SQL正则表达式的子字符串。声明的模式必须匹配整个数据串，否则函数失败并返回空值。为了标识在成功的时候应该返回的模式部分，模式必须包含逃逸字符的两次出现，并且后面要跟上双引号（"）。匹配这两个标记之间的模式的文本将被返回。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT substring('Thomas' from '%#"o_a#"_' for '#');
+   substring
+  -----------
+   oma
+  (1 row)
+  ```
+
+- rawcat(raw,raw)
+
+  描述：字符串拼接函数。
+
+  返回值类型：raw
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT rawcat('ab','cd');
+   rawcat
+  --------
+   ABCD
+  (1 row)
+  ```
+
+- regexp_like(text,text,text)
+
+  描述：正则表达式的模式匹配函数。
+
+  返回值类型：bool
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT regexp_like('str','[ac]');
+   regexp_like
+  -------------
+   f
+  (1 row)
+  ```
+
+- regexp_substr(text,text)
+
+  描述：正则表达式的抽取子串函数。与substr功能相似，正则表达式出现多个并列的括号时，也全部处理。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT regexp_substr('str','[ac]');
+   regexp_substr
+  ---------------
+
+  (1 row)
+  ```
+
+- regexp_matches(string text, pattern text [, flags text])
+
+  描述：返回string中所有匹配POSIX正则表达式的子字符串。如果pattern不匹配，该函数不返回行。如果模式不包含圆括号子表达式，则每一个被返回的行都是一个单一元素的文本数组，其中包括匹配整个模式的子串。如果模式包含圆括号子表达式，该函数返回一个文本数组，它的第n个元素是匹配模式的第n个圆括号子表达式的子串。
+
+  flags参数为可选参数，包含零个或多个改变函数行为的单字母标记。i表示进行大小写无关的匹配，g表示替换每一个匹配的子字符串而不仅仅是第一个。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+  > 如果提供了最后一个参数，但参数值是空字符串（")，且数据库SQL兼容模式设置为A的情况下，会导致返回结果为空集。这是因为A兼容模式将"作为NULL处理，避免此类行为的方式有如下几种：
+  >
+  > - 将数据库SQL兼容模式改为C；
+  > - 不提供最后一个参数，或最后一个参数不为空字符串。
+
+  返回值类型：setof text[]
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT regexp_matches('foobarbequebaz', '(bar)(beque)');
+   regexp_matches
+  ----------------
+   {bar,beque}
+  (1 row)
+  mogdb=# SELECT regexp_matches('foobarbequebaz', 'barbeque');
+   regexp_matches
+  ----------------
+   {barbeque}
+  (1 row)
+  mogdb=#  SELECT regexp_matches('foobarbequebazilbarfbonk', '(b[^b]+)(b[^b]+)', 'g');
+      result
+  --------------
+   {bar,beque}
+   {bazil,barf}
+  (2 rows)
+  ```
+
+- regexp_split_to_array(string text, pattern text [, flags text ])
+
+  描述：用POSIX正则表达式作为分隔符，分隔string。和regexp_split_to_table相同，不过regexp_split_to_array会把它的结果以一个text数组的形式返回。
+
+  返回值类型：text[]
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT regexp_split_to_array('hello world', E'\\s+');
+   regexp_split_to_array
+  -----------------------
+   {hello,world}
+  (1 row)
+  ```
+
+- regexp_split_to_table(string text, pattern text [, flags text])
+
+  描述：用POSIX正则表达式作为分隔符，分隔string。如果没有与pattern的匹配，该函数返回string。如果有至少有一个匹配，对每一个匹配它都返回从上一个匹配的末尾（或者串的开头）到这次匹配开头之间的文本。当没有更多匹配时，它返回从上一次匹配的末尾到串末尾之间的文本。
+
+  flags参数包含零个或多个改变函数行为的单字母标记。i表示进行大小写无关的匹配。
+
+  返回值类型：setof text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT regexp_split_to_table('hello world', E'\\s+');
+   regexp_split_to_table
+  -----------------------
+   hello
+   world
+  (2 rows)
+  ```
+
+- repeat(string text, number int )
+
+  描述：将string重复number次。
+
+  返回值类型：text。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT repeat('Pg', 4);
+    repeat
+  ----------
+   PgPgPgPg
+  (1 row)
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  > 由于数据库内存分配机制限制单次内存分配不可超过1GB，因此number最大值不应超过(1G-x)/lengthb(string) - 1。x为头信息长度，通常大于4字节，其具体值在不同的场景下存在差异。
+
+- replace(string text, from text, to text)
+
+  描述：把字符串string里出现地所有子字符串from的内容替换成子字符串to的内容。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT replace('abcdefabcdef', 'cd', 'XXX');
+      replace
+  ----------------
+   abXXXefabXXXef
+  (1 row)
+  ```
+
+- reverse(str)
+
+  描述：返回颠倒的字符串。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT reverse('abcde');
+   reverse
+  ---------
+   edcba
+  (1 row)
+  ```
+
+- right(str text, n int)
+
+  描述：返回字符串中的后n个字符。当n是负值时，返回除前|n|个字符以外的所有字符。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT right('abcde', 2);
+   right
+  -------
+   de
+  (1 row)
+
+  mogdb=# SELECT right('abcde', -2);
+   right
+  -------
+   cde
+  (1 row)
+  ```
+
+- rpad(string text, length int [, fill text])
+
+  描述：使用填充字符fill（缺省时为空白），把string填充到length长度。如果string已经比length长则将其从尾部截断。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT rpad('hi', 5, 'xy');
+   rpad
+  -------
+   hixyx
+  (1 row)
+  ```
+
+- rtrim(string text [, characters text])
+
+  描述：从字符串string的结尾删除只包含characters中字符（缺省是个空白）的最长的字符串。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT rtrim('trimxxxx', 'x');
+   rtrim
+  -------
+   trim
+  (1 row)
+  ```
+
+- substrb(text,int,int)
+
+  描述：提取子字符串，第一个int表示提取的起始位置，第二个表示提取几位字符。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT substrb('string',2,3);
+   substrb
+  ---------
+   tri
+  (1 row)
+  ```
+
+- substrb(text,int)
+
+  描述：提取子字符串，int表示提取的起始位置。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT substrb('string',2);
+   substrb
+  ---------
+   tring
+  (1 row)
+  ```
+
+- substr(bytea,from,count)
+
+  描述：从参数bytea中抽取子字符串。from表示抽取的起始位置，count表示抽取的子字符串长度。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT substr('string',2,3);
+   substr
+  --------
+   tri
+  (1 row)
+  ```
+
+- string || string
+
+  描述：连接字符串。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT 'MPP'||'DB' AS RESULT;
+   result
+  --------
+   MPPDB
+  (1 row)
+  ```
+
+- string || non-string或non-string || string
+
+  描述：连接字符串和非字符串。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT 'Value: '||42 AS RESULT;
+    result
+  -----------
+   Value: 42
+  (1 row)
+  ```
+
+- split_part(string text, delimiter text, field int)
+
+  描述：根据delimiter分隔string返回生成的第field个子字符串（从出现第一个delimiter的text为基础）。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT split_part('abc~@~def~@~ghi', '~@~', 2);
+   split_part
+  ------------
+   def
+  (1 row)
+  ```
+
+- strpos(string, substring)
+
+  描述：指定的子字符串的位置。和position(substring in string)一样，不过参数顺序相反。
+
+  返回值类型：int
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT strpos('source', 'rc');
+   strpos
+  --------
+        4
+  (1 row)
+  ```
+
+- to_hex(number int or bigint)
+
+  描述：把number转换成十六进制表现形式。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT to_hex(2147483647);
+    to_hex
+  ----------
+   7fffffff
+  (1 row)
+  ```
+
+- translate(string text, from text, to text)
+
+  描述：把在string中包含的任何匹配from中字符的字符转化为对应的在to中的字符。如果from比to长，删掉在from中出现的额外的字符。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT translate('12345', '143', 'ax');
+   translate
+  -----------
+   a2x5
+  (1 row)
+  ```
+
+- length(string)
+
+  描述：获取参数string中字符的数目。
+
+  返回值类型：integer
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT length('abcd');
+   length
+  --------
+        4
+  (1 row)
+  ```
+
+- lengthb(string)
+
+  描述：获取参数string中字节的数目。与字符集有关，同样的中文字符，在GBK与UTF8中，返回的字节数不同。
+
+  返回值类型：integer
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT lengthb('Chinese');
+   lengthb
+  ---------
+         7
+  (1 row)
+  ```
+
+- substr(string,from)
+
+  描述：
+
+  从参数string中抽取子字符串。
+
+  from表示抽取的起始位置。
+
+  - from为0时，按1处理。
+  - from为正数时，抽取从from到末尾的所有字符。
+  - from为负数时，抽取字符串的后n个字符，n为from的绝对值。
+
+  返回值类型：varchar
+
+  示例：
+
+  from为正数时：
+
+  ```sql
+  mogdb=# SELECT substr('ABCDEF',2);
+   substr
+  --------
+   BCDEF
+  (1 row)
+  ```
+
+  from为负数时：
+
+  ```sql
+  mogdb=# SELECT substr('ABCDEF',-2);
+   substr
+  --------
+   EF
+  (1 row)
+  ```
+
+- substr(string,from,count)
+
+  描述：
+
+  从参数string中抽取子字符串。
+
+  from表示抽取的起始位置。
+
+  count表示抽取的子字符串长度。
+
+  - from为0时，按1处理。
+  - from为正数时，抽取从from开始的count个字符。
+  - from为负数时，抽取从倒数第n个开始的count个字符，n为from的绝对值。
+  - count小于1时，返回null。
+
+  返回值类型：varchar
+
+  示例：
+
+  from为正数时：
+
+  ```sql
+  mogdb=# SELECT substr('ABCDEF',2,2);
+   substr
+  --------
+   BC
+  (1 row)
+  ```
+
+  from为负数时：
+
+  ```sql
+  mogdb=# SELECT substr('ABCDEF',-3,2);
+   substr
+  --------
+   DE
+  (1 row)
+  ```
+
+- substrb(string,from)
+
+  描述：该函数和SUBSTR(string,from)函数功能一致，但是计算单位为字节。
+
+  返回值类型：bytea
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT substrb('ABCDEF',-2);
+   substrb
+  ---------
+   EF
+  (1 row)
+  ```
+
+- substrb(string,from,count)
+
+  描述：该函数和SUBSTR(string,from,count)函数功能一致，但是计算单位为字节。
+
+  返回值类型：bytea
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT substrb('ABCDEF',2,2);
+   substrb
+  ---------
+   BC
+  (1 row)
+  ```
+
+- trim([leading |trailing |both] [characters] from string)
+
+  描述：从字符串string的开头、结尾或两边删除只包含characters中字符（缺省是一个空白）的最长的字符串。
+
+  返回值类型：varchar
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT trim(BOTH 'x' FROM 'xTomxx');
+   btrim
+  -------
+   Tom
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT trim(LEADING 'x' FROM 'xTomxx');
+   ltrim
+  -------
+   Tomxx
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT trim(TRAILING 'x' FROM 'xTomxx');
+   rtrim
+  -------
+   xTom
+  (1 row)
+  ```
+
+- rtrim(string [, characters])
+
+  描述：从字符串string的结尾删除只包含characters中字符（缺省是个空白）的最长的字符串。
+
+  返回值类型：varchar
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT rtrim('TRIMxxxx','x');
+   rtrim
+  -------
+   TRIM
+  (1 row)
+  ```
+
+- ltrim(string [, characters])
+
+  描述：从字符串string的开头删除只包含characters中字符（缺省是一个空白）的最长的字符串。
+
+  返回值类型：varchar
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT ltrim('xxxxTRIM','x');
+   ltrim
+  -------
+   TRIM
+  (1 row)
+  ```
+
+- upper(string)
+
+  描述：把字符串转化为大写。
+
+  返回值类型：varchar
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT upper('tom');
+   upper
+  -------
+   TOM
+  (1 row)
+  ```
+
+- lower(string)
+
+  描述：把字符串转化为小写。
+
+  返回值类型：varchar
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT lower('TOM');
+   lower
+  -------
+   tom
+  (1 row)
+  ```
+
+- rpad(string varchar, length int [, fill varchar])
+
+  描述：使用填充字符fill（缺省时为空白），把string填充到length长度。如果string已经比length长则将其从尾部截断。
+
+  length参数在MogDB中表示字符长度。一个汉字长度计算为一个字符。
+
+  返回值类型：varchar
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT rpad('hi',5,'xyza');
+   rpad
+  -------
+   hixyz
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT rpad('hi',5,'abcdefg');
+   rpad
+  -------
+   hiabc
+  (1 row)
+  ```
+
+- instr(string,substring[,position,occurrence])
+
+  描述：从字符串string的position（缺省时为1）所指的位置开始查找并返回第occurrence（缺省时为1）次出现子串substring的位置的值。
+
+  - 当position为0时，返回0。
+  - 当position为负数时，从字符串倒数第n个字符往前逆向搜索。n为position的绝对值。
+
+  本函数以字符为计算单位，如一个汉字为一个字符。
+
+  返回值类型：integer
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT instr('corporate floor','or', 3);
+   instr
+  -------
+       5
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT instr('corporate floor','or',-3,2);
+   instr
+  -------
+       2
+  (1 row)
+  ```
+
+- initcap(string)
+
+  描述：将字符串中的每个单词的首字母转化为大写，其他字母转化为小写。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT initcap('hi THOMAS');
+    initcap
+  -----------
+   Hi Thomas
+  (1 row)
+  ```
+
+- ascii(string)
+
+  描述：参数string的第一个字符的ASCII码。
+
+  返回值类型：integer
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT ascii('xyz');
+   ascii
+  -------
+     120
+  (1 row)
+  ```
+
+- replace(string varchar, search_string varchar, replacement_string varchar)
+
+  描述：把字符串string中所有子字符串search_string替换成子字符串replacement_string。
+
+  返回值类型：varchar
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT replace('jack and jue','j','bl');
+      replace
+  ----------------
+   black and blue
+  (1 row)
+  ```
+
+- lpad(string varchar, length int[, repeat_string varchar])
+
+  描述：在string的左侧添上一系列的repeat_string（缺省为空白）来组成一个总长度为n的新字符串。
+
+  如果string本身的长度比指定的长度length长，则本函数将把string截断并把前面长度为length的字符串内容返回。
+
+  返回值类型：varchar
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT lpad('PAGE 1',15,'*.');
+        lpad
+  -----------------
+   *.*.*.*.*PAGE 1
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT lpad('hello world',5,'abcd');
+   lpad
+  -------
+   hello
+  (1 row)
+  ```
+
+- concat(str1,str2)
+
+  描述：将字符串str1和str2连接并返回。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**数据库SQL兼容模式设置为MY的情况下，参数str1或str2为NULL会导致返回结果为NULL。
+
+  返回值类型：varchar
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT concat('Hello', ' World!');
+      concat
+  --------------
+   Hello World!
+  (1 row)
+  mogdb=# SELECT concat('Hello', NULL);
+   concat
+  --------
+   Hello
+  (1 row)
+  ```
+
+- chr(integer)
+
+  描述：给出ASCII码的字符。
+
+  返回值类型：varchar
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT chr(65);
+   chr
+  -----
+   A
+  (1 row)
+  ```
+
+- regexp_substr(source_char, pattern)
+
+  描述：正则表达式的抽取子串函数。
+
+  返回值类型：varchar
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT regexp_substr('500 Hello World, Redwood Shores, CA', ',[^,]+,') "REGEXPR_SUBSTR";
+    REGEXPR_SUBSTR
+  -------------------
+   , Redwood Shores,
+  (1 row)
+  ```
+
+- regexp_replace(string, pattern, replacement [,flags ])
+
+  描述：替换匹配POSIX正则表达式的子字符串。 如果没有匹配pattern，那么返回不加修改的string串。 如果有匹配，则返回的string串里面的匹配子串将被replacement串替换掉。
+
+  \\n， 其中\\n是1 到9， 表明string串里匹配模式里第n个圆括号子表达式的子串应该被插入， 并且它可以包含\&表示应该插入匹配整个模式的子串。
+
+  可选的flags参数包含零个或多个改变函数行为的单字母标记。i表示进行大小写无关的匹配，g表示替换每一个匹配的子字符串而不仅仅是第一个。
+
+  返回值类型：varchar
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT regexp_replace('Thomas', '.[mN]a.', 'M');
+   regexp_replace
+  ----------------
+   ThM
+  (1 row)
+  mogdb=# SELECT regexp_replace('foobarbaz','b(..)', E'X\\1Y', 'g') AS RESULT;
+     result
+  -------------
+   fooXarYXazY
+  (1 row)
+  ```
+
+- concat_ws(sep text, str"any" [, str"any" [, …] ])
+
+  描述：以第一个参数为分隔符，链接第二个以后的所有参数。NULL参数被忽略。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+  >
+  > - 如果第一个参数值是NULL，会导致返回结果为NULL。
+  > - 如果第一个参数值是空字符串（"），且数据库SQL兼容模式设置为A的情况下，会导致返回结果为NULL。这是因为A兼容模式&gt;将"作为NULL处理，避免此类行为，可以将数据库SQL兼容模式改为B、C或者PG。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT concat_ws(',', 'ABCDE', 2, NULL, 22);
+   concat_ws
+  ------------
+   ABCDE,2,22
+  (1 row)
+  ```
+
+- convert(string bytea, src_encoding name, dest_encoding name)
+
+  描述：以dest_encoding指定的目标编码方式转化字符串bytea。src_encoding指定源编码方式，在该编码下，string必须是合法的。
+
+  返回值类型：bytea
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT convert('text_in_utf8', 'UTF8', 'GBK');
+            convert
+  ----------------------------
+   \x746578745f696e5f75746638
+  (1 row)
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  > 如果源编码格式到目标编码格式的转化规则不存在，则字符串不进行任何转换直接返回，如GBK和LATIN1之间的转换规则是不存在的，具体转换规则可以通过查看系统表pg_conversion获得。
+  > 示例：
+  >
+  > ```sql
+  > mogdb=# show server_encoding;
+  > server_encoding
+  > -----------------
+  > LATIN1
+  > (1 row)
+  > mogdb=# SELECT convert_from('some text', 'GBK');
+  > convert_from
+  > --------------
+  > some text
+  > (1 row)
+  > db_latin1=# SELECT convert_to('some text', 'GBK');
+  >   convert_to
+  > ----------------------
+  > \x736f6d652074657874
+  > (1 row)
+  > db_latin1=# SELECT convert('some text', 'GBK', 'LATIN1');
+  >    convert
+  > ----------------------
+  > \x736f6d652074657874
+  > (1 row)
+  > ```
+
+- convert_from(string bytea, src_encoding name)
+
+  描述：以数据库的编码方式转化字符串bytea。
+
+  src_encoding指定源编码方式，在该编码下，string必须是合法的。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT convert_from('text_in_utf8', 'UTF8');
+   convert_from
+  --------------
+   text_in_utf8
+  (1 row)
+  ```
+
+- convert_to(string text, dest_encoding name)
+
+  描述：将字符串转化为dest_encoding的编码格式。
+
+  返回值类型：bytea
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT convert_to('some text', 'UTF8');
+        convert_to
+  ----------------------
+   \x736f6d652074657874
+  (1 row)
+  ```
+
+- string [NOT] LIKE pattern [ESCAPE escape-character]
+
+  描述：模式匹配函数。
+
+  如果pattern不包含百分号或者下划线，该模式只代表它本身，这时候LIKE的行为就像等号操作符。在pattern里的下划线（_）匹配任何单个字符；而一个百分号（%）匹配零或多个任何字符。
+
+  要匹配下划线或者百分号本身，在pattern里相应的字符必须前导逃逸字符。缺省的逃逸字符是反斜杠，但是用户可以用ESCAPE子句指定一个。要匹配逃逸字符本身，写两个逃逸字符。
+
+  返回值类型：Boolean
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT 'AA_BBCC' LIKE '%A@_B%' ESCAPE '@' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT 'AA_BBCC' LIKE '%A@_B%' AS RESULT;
+   result
+  --------
+   f
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT 'AA@_BBCC' LIKE '%A@_B%' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+- REGEXP_LIKE(source_string, pattern [, match_parameter])
+
+  描述：正则表达式的模式匹配函数。
+
+  source_string为源字符串，pattern为正则表达式匹配模式。 match_parameter为匹配选项，可取值为：
+
+  - 'i'：大小写不敏感。
+  - 'c'：大小写敏感。
+  - 'n'：允许正则表达式元字符"."匹配换行符。
+  - 'm'：将source_string视为多行。
+
+  若忽略match_parameter选项，默认为大小写敏感，"."不匹配换行符，source_string视为单行。
+
+  返回值类型：Boolean
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT regexp_like('ABC', '[A-Z]');
+   regexp_like
+  -------------
+   t
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT regexp_like('ABC', '[D-Z]');
+   regexp_like
+  -------------
+   f
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT regexp_like('ABC', '[a-z]','i');
+   regexp_like
+  -------------
+   t
+  (1 row)
+  ```
+
+- format(formatstr text [, str"any" [, …] ])
+
+  描述：格式化字符串。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT format('Hello %s, %1$s', 'World');
+         format
+  --------------------
+   Hello World, World
+  (1 row)
+  ```
+
+- md5(string)
+
+  描述：将string使用MD5加密，并以16进制数作为返回值。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  > MD5加密算法安全性低，存在安全风险，不建议使用。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT md5('ABC');
+                 md5
+  ----------------------------------
+   902fbdd2b1df0c4f70b4a5d23525e932
+  (1 row)
+  ```
+
+- decode(string text, format text)
+
+  描述：将二进制数据从文本数据中解码。
+
+  返回值类型：bytea
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT decode('MTIzAAE=', 'base64');
+      decode
+  --------------
+   \x3132330001
+  (1 row)
+  ```
+
+- similar_escape(pat text, esc text)
+
+    描述：将一个 SQL:2008风格的正则表达式转换为POSIX风格。
+
+    返回值类型：text
+
+    示例：
+
+    ```sql
+    mogdb=# select similar_escape('\s+ab','2');
+     similar_escape
+    ----------------
+     ^(?:\\s+ab)$
+    (1 row)
+    ```
+
+- svals(hstore)
+
+    描述：获取hstore中的值。
+
+    返回值类型：SETOF text
+
+    示例：
+
+    ```sql
+    mogdb=# select svals('"aa"=>"bb"');
+     svals
+    -------
+     bb
+    (1 row)
+    ```
+
+- tconvert(key text, value text)
+
+    描述：将字符串转换为hstore格式。
+
+    返回值类型：hstore
+
+    示例：
+
+    ```sql
+    mogdb=# select tconvert('aa', 'bb');
+      tconvert
+    ------------
+     "aa"=>"bb"
+    (1 row)
+    ```
+
+- encode(data bytea, format text)
+
+  描述：将二进制数据编码为文本数据。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT encode(E'123\\000\\001', 'base64');
+    encode
+  ----------
+   MTIzAAE=
+  (1 row)
+  ```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 若字符串中存在换行符，如字符串由一个换行符和一个空格组成，在MogDB中LENGTH和LENGTHB的值为2。
+>
+> - 对于CHAR(n) 类型，MogDB中n是指字符个数。因此，对于多字节编码的字符集， LENGTHB函数返回的长度可能大于n。
+>
+> - MogDB支持多种类型的数据库，目前有4种，分别是A类型、B类型、C类型以及PG类型。在不指定数据库类型时，我们的数据库默认是A类型，A的词法分析器与另外三种不一样，在A中空字符串会被当作是NULL。所以，当使用A类型的数据库时，假如上述字符操作函数中有空字符串作为参数，会出现没有输出的情况。例如：
+>
+>   ```sql
+>   mogdb=# SELECT translate('12345','123','');
+>   translate
+>   -----------
+>
+>   (1 row)
+>   ```
+>
+> 这是因为内核在调用相应的函数进行处理前，会判断所输入的参数中是否含有NULL，假如 有，则不会调用相应的函数，因此会没有输出。而在PG模式下，字符串的处理方式与PostgreSQL保持一致，因此不会有上述问题产生。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/30-internal-functions.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/30-internal-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..ba18c959b6f383d4b729c54c20e0df19f8458c27
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/30-internal-functions.md
@@ -0,0 +1,171 @@
+---
+title: 内部函数
+summary: 内部函数
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# 内部函数
+
+MogDB中下列函数使用了内部数据类型，用户无法直接调用，在此章节列出。
+
+- 选择率计算函数
+
+  | areajoinsel      | areasel         | arraycontjoinsel | arraycontsel   | contjoinsel    | contsel          | eqjoinsel    |
+  | ---------------- | --------------- | ---------------- | -------------- | -------------- | ---------------- | ------------ |
+  | eqsel            | iclikejoinsel   | iclikesel        | icnlikejoinsel | icnlikesel     | icregexeqjoinsel | icregexeqsel |
+  | icregexnejoinsel | icregexnesel    | likejoinsel      | likesel        | neqjoinsel     | neqsel           | nlikejoinsel |
+  | nlikesel         | positionjoinsel | positionsel      | regexeqjoinsel | regexeqsel     | regexnejoinsel   | regexnesel   |
+  | scalargtjoinsel  | scalargtsel     | scalarltjoinsel  | scalarltsel    | tsmatchjoinsel | tsmatchsel       | -            |
+
+- 统计信息收集函数
+
+  | array_typanalyze | range_typanalyze | ts_typanalyze |
+  | ---------------- | ---------------- | ------------- |
+  | local_rto_stat   |                  |               |
+
+- 排序内部功能函数
+
+  | bpchar_sortsupport | bytea_sortsupport | date_sortsupport | numeric_sortsupport | timestamp_sortsupport |
+  | ------------------ | ----------------- | ---------------- | ------------------- | --------------------- |
+
+- 全文检索内部功能函数
+
+  | dispell_init    | dispell_lexize    | dsimple_init        | dsimple_lexize      | dsnowball_init   | dsnowball_lexize   | dsynonym_init |
+  | --------------- | ----------------- | ------------------- | ------------------- | ---------------- | ------------------ | ------------- |
+  | dsynonym_lexize | gtsquery_compress | gtsquery_consistent | gtsquery_decompress | gtsquery_penalty | gtsquery_picksplit | gtsquery_same |
+  | gtsquery_union  | ngram_end         | ngram_lextype       | ngram_start         | pound_end        | pound_lextype      | pound_start   |
+  | prsd_end        | prsd_headline     | prsd_lextype        | prsd_start          | thesaurus_init   | thesaurus_lexize   | zhprs_end     |
+  | zhprs_getlexeme | zhprs_lextype     | zhprs_start         | -                   | -                | -                  | -             |
+
+- 内部类型处理函数
+
+  | abstimerecv                       | euc_jis_2004_to_utf8 | int2recv           | line_recv         | oidvectorrecv_extend           | tidrecv              | utf8_to_koi8u          |
+  | --------------------------------- | -------------------- | ------------------ | ----------------- | ------------------------------ | -------------------- | ---------------------- |
+  | anyarray_recv                     | euc_jp_to_mic        | int2vectorrecv     | lseg_recv         | path_recv                      | time_recv            | utf8_to_shift_jis_2004 |
+  | array_recv                        | euc_jp_to_sjis       | int4recv           | macaddr_recv      | pg_node_tree_recv              | time_transform       | utf8_to_sjis           |
+  | ascii_to_mic                      | euc_jp_to_utf8       | int8recv           | mic_to_ascii      | point_recv                     | timestamp_recv       | utf8_to_uhc            |
+  | ascii_to_utf8                     | euc_kr_to_mic        | internal_out       | mic_to_big5       | poly_recv                      | timestamp_transform  | utf8_to_win            |
+  | big5_to_euc_tw                    | euc_kr_to_utf8       | interval_recv      | mic_to_euc_cn     | pound_nexttoken                | timestamptz_recv     | uuid_recv              |
+  | big5_to_mic                       | euc_tw_to_big5       | interval_transform | mic_to_euc_jp     | prsd_nexttoken                 | timetz_recv          | varbit_recv            |
+  | big5_to_utf8                      | euc_tw_to_mic        | iso_to_koi8r       | mic_to_euc_kr     | range_recv                     | tintervalrecv        | varbit_transform       |
+  | bit_recv                          | euc_tw_to_utf8       | iso_to_mic         | mic_to_euc_tw     | rawrecv                        | tsqueryrecv          | varchar_transform      |
+  | boolrecv                          | float4recv           | iso_to_win1251     | mic_to_iso        | record_recv                    | tsvectorrecv         | varcharrecv            |
+  | box_recv                          | float8recv           | iso_to_win866      | mic_to_koi8r      | regclassrecv                   | txid_snapshot_recv   | void_recv              |
+  | bpcharrecv                        | gb18030_to_utf8      | iso8859_1_to_utf8  | mic_to_latin1     | regconfigrecv                  | uhc_to_utf8          | win_to_utf8            |
+  | btoidsortsupport                  | gbk_to_utf8          | iso8859_to_utf8    | mic_to_latin2     | regdictionaryrecv              | unknownrecv          | win1250_to_latin2      |
+  | bytearecv                         | gin_extract_tsvector | johab_to_utf8      | mic_to_latin3     | regoperatorrecv                | utf8_to_ascii        | win1250_to_mic         |
+  | byteawithoutorderwithequalcolrecv | gtsvector_compress   | json_recv          | mic_to_latin4     | regoperrecv                    | utf8_to_big5         | win1251_to_iso         |
+  | cash_recv                         | gtsvector_consistent | koi8r_to_iso       | mic_to_sjis       | regprocedurerecv               | utf8_to_euc_cn       | win1251_to_koi8r       |
+  | charrecv                          | gtsvector_decompress | koi8r_to_mic       | mic_to_win1250    | regprocrecv                    | utf8_to_euc_jis_2004 | win1251_to_mic         |
+  | cidr_recv                         | gtsvector_penalty    | koi8r_to_utf8      | mic_to_win1251    | regtyperecv                    | utf8_to_euc_jp       | win1251_to_win866      |
+  | cidrecv                           | gtsvector_picksplit  | koi8r_to_win1251   | mic_to_win866     | reltimerecv                    | utf8_to_euc_kr       | win866_to_iso          |
+  | circle_recv                       | gtsvector_same       | koi8r_to_win866    | namerecv          | shift_jis_2004_to_euc_jis_2004 | utf8_to_euc_tw       | win866_to_koi8r        |
+  | cstring_recv                      | gtsvector_union      | koi8u_to_utf8      | ngram_nexttoken   | shift_jis_2004_to_utf8         | utf8_to_gb18030      | win866_to_mic          |
+  | date_recv                         | hll_recv             | latin1_to_mic      | numeric_recv      | sjis_to_euc_jp                 | utf8_to_gbk          | win866_to_win1251      |
+  | domain_recv                       | hll_trans_recv       | latin2_to_mic      | numeric_transform | sjis_to_mic                    | utf8_to_iso8859      | xidrecv                |
+  | euc_cn_to_mic                     | hstore_recv          | latin2_to_win1250  | nvarchar2recv     | sjis_to_utf8                   | utf8_to_iso8859_1    | xidrecv4               |
+  | euc_cn_to_utf8                    | inet_recv            | latin3_to_mic      | oidrecv           | smalldatetime_recv             | utf8_to_johab        | xml_recv               |
+  | euc_jis_2004_to_shift_jis_2004    | int1recv             | latin4_to_mic      | oidvectorrecv     | textrecv                       | utf8_to_koi8r        | cstore_tid_out         |
+  | i16toi1                           | int16                | int16_bool         | int16eq           | int16div                       | int16ge              | int16gt                |
+  | int16in                           | int16le              | int16lt            | int16mi           | int16mul                       | int16ne              | int16out               |
+  | int16pl                           | int16recv            | int16send          | numeric_bool      |                                |                      |                        |
+  | jsonb_in                          | jsonb_out            | jsonb_recv         | jsonb_send        |                                |                      |                        |
+
+- 聚合操作内部函数
+
+  | array_agg_finalfn            | array_agg_transfn              | bytea_string_agg_finalfn         | bytea_string_agg_transfn     | date_list_agg_noarg2_transfn      | date_list_agg_transfn        | float4_list_agg_noarg2_transfn      |
+  | ---------------------------- | ------------------------------ | -------------------------------- | ---------------------------- | --------------------------------- | ---------------------------- | ----------------------------------- |
+  | float4_list_agg_transfn      | float8_list_agg_noarg2_transfn | float8_list_agg_transfn          | int2_list_agg_noarg2_transfn | int2_list_agg_transfn             | int4_list_agg_noarg2_transfn | int4_list_agg_transfn               |
+  | int8_list_agg_noarg2_transfn | int8_list_agg_transfn          | interval_list_agg_noarg2_transfn | interval_list_agg_transfn    | list_agg_finalfn                  | list_agg_noarg2_transfn      | list_agg_transfn                    |
+  | median_float8_finalfn        | median_interval_finalfn        | median_transfn                   | mode_final                   | numeric_list_agg_noarg2_transfn   | numeric_list_agg_transfn     | ordered_set_transition              |
+  | percentile_cont_float8_final | percentile_cont_interval_final | string_agg_finalfn               | string_agg_transfn           | timestamp_list_agg_noarg2_transfn | timestamp_list_agg_transfn   | timestamptz_list_agg_noarg2_transfn |
+  | timestamptz_list_agg_transfn | checksumtext_agg_transfn       | -                                | -                            | -                                 | -                            | -                                   |
+  | json_agg_finalfn             | json_agg_transfn               | json_object_agg_finalfn          | json_object_agg_transfn      | -                                 | -                            | -                                   |
+
+- 哈希内部功能函数
+
+  | hashbeginscan | hashbuild  | hashbuildempty | hashbulkdelete | hashcostestimate | hashendscan  | hashgetbitmap     |
+  | ------------- | ---------- | -------------- | -------------- | ---------------- | ------------ | ----------------- |
+  | hashgettuple  | hashinsert | hashmarkpos    | hashmerge      | hashrescan       | hashrestrpos | hashvacuumcleanup |
+  | hashvarlena   | -          | -              | -              | -                | -            | -                 |
+
+- Btree索引内部功能函数
+
+  | cbtreebuild  | cbtreecanreturn   | cbtreecostestimate | cbtreegetbitmap   | cbtreegettuple    | btbeginscan         | btbuild             |
+  | ------------ | ----------------- | ------------------ | ----------------- | ----------------- | ------------------- | ------------------- |
+  | btbuildempty | btbulkdelete      | btcanreturn        | btcostestimate    | btendscan         | btfloat4sortsupport | btfloat8sortsupport |
+  | btgetbitmap  | btgettuple        | btinsert           | btint2sortsupport | btint4sortsupport | btint8sortsupport   | btmarkpos           |
+  | btmerge      | btnamesortsupport | btrescan           | btrestrpos        | bttextsortsupport | btvacuumcleanup     | cbtreeoptions       |
+
+- GiST索引内部功能函数
+
+  | gist_box_compress         | gist_box_consistent      | gist_box_decompress  | gist_box_penalty          | gist_box_picksplit       | gist_box_same      | gist_box_union       |
+  | ------------------------- | ------------------------ | -------------------- | ------------------------- | ------------------------ | ------------------ | -------------------- |
+  | gist_circle_compress      | gist_circle_consistent   | gist_point_compress  | gist_point_consistent     | gist_point_distance      | gist_poly_compress | gist_poly_consistent |
+  | gistbeginscan             | gistbuild                | gistbuildempty       | gistbulkdelete            | gistcostestimate         | gistendscan        | gistgetbitmap        |
+  | gistinsert                | gistmarkpos              | gistmerge            | gistrescan                | gistrestrpos             | gistvacuumcleanup  | range_gist_compress  |
+  | range_gist_decompress     | range_gist_penalty       | range_gist_picksplit | range_gist_same           | range_gist_union         | spg_kd_choose      | spg_kd_config        |
+  | spg_kd_picksplit          | spg_quad_choose          | spg_quad_config      | spg_quad_inner_consistent | spg_quad_leaf_consistent | spg_quad_picksplit | spg_text_choose      |
+  | spg_text_inner_consistent | spg_text_leaf_consistent | spg_text_picksplit   | spgbeginscan              | spgbuild                 | spgbuildempty      | spgbulkdelete        |
+  | spgcostestimate           | spgendscan               | spggetbitmap         | spggettuple               | spginsert                | spgmarkpos         | spgmerge             |
+  | spgrestrpos               | spgvacuumcleanup         | -                    | -                         | -                        | -                  | -                    |
+
+- Gin索引内部功能函数
+
+  | gin_cmp_prefix    | gin_extract_tsquery  | gin_tsquery_consistent    | gin_tsquery_triconsistent               | ginarrayconsistent | ginarrayextract         | ginarraytriconsistent   |
+  | ----------------- | -------------------- | ------------------------- | --------------------------------------- | ------------------ | ----------------------- | ----------------------- |
+  | ginbeginscan      | ginbuild             | ginbuildempty             | ginbulkdelete                           | gincostestimate    | ginendscan              | gingetbitmap            |
+  | gininsert         | ginmarkpos           | ginmerge                  | ginqueryarrayextract                    | ginrescan          | ginrestrpos             | ginvacuumcleanup        |
+  | cginbuild         | cgingetbitmap        | -                         | -                                       | -                  | -                       | -                       |
+  | gin_compare_jsonb | gin_consistent_jsonb | gin_consistent_jsonb_hash | gin_extract_jsonbgin_extract_jsonb_hash | cginbuild          | gin_extract_jsonb_query | gin_triconsistent_jsonb |
+
+- Psort索引内部函数
+
+  | psortbuild | psortcanreturn | psortcostestimate | psortgetbitmap | psortgettuple |
+  | ---------- | -------------- | ----------------- | -------------- | ------------- |
+
+- Ubtree索引内部函数
+
+  | ubtbeginscan     | ubtbuild   | ubtbuildempty | ubtbulkdelete | ubtcanreturn |
+  | ---------------- | ---------- | ------------- | ------------- | ------------ |
+  | ubtcostestimate  | ubtendscan | ubtgetbitmap  | ubtgettuple   | ubtinsert    |
+  | ubtmarkpos       | ubtmerge   | ubtoptions    | ubtrescan     | ubtrestrpos  |
+  | ubtvacuumcleanup |            |               |               |              |
+
+- plpgsql内部函数
+
+  plpgsql_inline_handler
+
+- 外表相关内部函数
+
+  | dist_fdw_handler | roach_handler | streaming_fdw_handler | dist_fdw_validator | file_fdw_handler | file_fdw_validator | log_fdw_handler |
+  | ---------------- | ------------- | --------------------- | ------------------ | ---------------- | ------------------ | --------------- |
+
+- 主DN远程读取备DN数据页辅助函数
+
+  gs_read_block_from_remote
+
+- 账本数据库函数
+
+  get_dn_hist_relhash
+
+- AI特性函数
+
+    | create_snapshot         | create_snapshot_internal | prepare_snapshot_internal | prepare_snapshot | manage_snapshot_internal | archive_snapshot | publish_snapshot |
+    | ----------------------- | ------------------------ | ------------------------- | ---------------- | ------------------------ | ---------------- | ---------------- |
+    | purge_snapshot_internal | purge_snapshot           | sample_snapshot           |                  |                          |                  |                  |
+
+  - PKG_SERVICE函数
+
+    | isubmit_on_nodes | submit_on_nodes |      |      |      |      |      |
+    | ---------------- | --------------- | ---- | ---- | ---- | ---- | ---- |
+
+- 其他函数
+
+  | to_tsvector_for_batch     | value_of_percentile         | session_context   | bind_variable               | job_update         | job_cancel        | job_finish                 |
+  | ------------------------- | --------------------------- | ----------------- | --------------------------- | ------------------ | ----------------- | -------------------------- |
+  | similar_escape            | table_skewness （不可用）   | timetz_text       | time_text                   | reltime_text       | abstime_text      | _pg_keysequal              |
+  | analyze_query(不可用）    | analyze_workload （不可用） | ssign_table_type  | gs_comm_proxy_thread_status | gs_txid_oldestxmin | pg_cancel_session | pg_stat_segment_space_info |
+  | remote_segment_space_info | set_cost_params             | set_weight_params | start_collect_workload      | tdigest_in         | tdigest_merge     | tdigest_merge_to_one       |
+  | tdigest_mergep            | tdigest_out                 | pg_get_delta_info |                             |                    |                   |                            |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/31-obsolete-functions.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/31-obsolete-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..0bcffb9dae2aa72bea91bb33d1694252d490792c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/31-obsolete-functions.md
@@ -0,0 +1,18 @@
+---
+title: 废弃函数
+summary: 废弃函数
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# 废弃函数
+
+MogDB中下列函数在最新版本中已废弃：
+
+| gs_wlm_get_session_info     | gs_wlm_get_user_session_info       | pgxc_get_csn                          | pgxc_get_stat_dirty_tables                | pgxc_get_thread_wait_status              | pgxc_gtm_snapshot_status               | pgxc_is_committed                  |
+| --------------------------- | ---------------------------------- | ------------------------------------- | ----------------------------------------- | ---------------------------------------- | -------------------------------------- | ---------------------------------- |
+| pgxc_lock_for_backup        | pgxc_lock_for_sp_database          | pgxc_lock_for_transfer                | pgxc_log_comm_status                      | pgxc_max_datanode_size                   | pgxc_node_str                          | pgxc_pool_check                    |
+| pgxc_pool_connection_status | pgxc_pool_reload                   | pgxc_prepared_xact                    | pgxc_snapshot_status                      | pgxc_stat_dirty_tables                   | pgxc_unlock_for_sp_database            | pgxc_unlock_for_transfer           |
+| pgxc_version                | array_extend                       | prepare_statement_status              | remote_rto_stat                           | dbe_perf.global_slow_query_info          | dbe_perf.global_slow_query_info_bytime | dbe_perf.global_slow_query_history |
+| pg_stat_get_pooler_status   | pg_stat_get_wlm_node_resource_info | pg_stat_get_wlm_session_info_internal | DBE_PERF.get_wlm_controlgroup_ng_config() | DBE_PERF.get_wlm_user_resource_runtime() | global_space_shrink                    | pg_pool_validate                   |
+| gs_stat_ustore              | table_skewness(text)               | table_skewness(text, text, text)      | -                                         | -                                        | -                                      | -                                  |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/4-binary-string-functions-and-operators.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/4-binary-string-functions-and-operators.md
new file mode 100644
index 0000000000000000000000000000000000000000..590e8f8bf879e5f48db29c440205df7511b5b9c5
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/4-binary-string-functions-and-operators.md
@@ -0,0 +1,192 @@
+---
+title: 二进制字符串函数和操作符
+summary: 二进制字符串函数和操作符
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 二进制字符串函数和操作符
+
+<span style="font:14px">**字符串操作符**</span>
+
+SQL定义了一些字符串函数，在这些函数里使用关键字而不是逗号来分隔参数。
+
+- octet_length(string)
+
+  描述: 二进制字符串中的字节数。
+
+  返回值类型: int
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT octet_length(E'jo\\000se'::bytea) AS RESULT;
+   result
+  --------
+        5
+  (1 row)
+  ```
+
+- overlay(string placing string from int [for int])
+
+  描述: 替换子串。
+
+  返回值类型: bytea
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT overlay(E'Th\\000omas'::bytea placing E'\\002\\003'::bytea from 2 for 3) AS RESULT;
+       result
+  ----------------
+   \x5402036d6173
+  (1 row)
+  ```
+
+- position(substring in string)
+
+  描述: 特定子字符串的位置。
+
+  返回值类型: int
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT position(E'\\000om'::bytea in E'Th\\000omas'::bytea) AS RESULT;
+   result
+  --------
+        3
+  (1 row)
+  ```
+
+- substring(string [from int] [for int])
+
+  描述: 截取子串。
+
+  返回值类型: bytea
+
+  示例:
+
+  ```sql
+  mogdb=# select substr(E'Th\\000omas'::bytea,2, 3) as result;
+    result
+  ----------
+   \x68006f
+  (1 row)
+  ```
+
+- substr(string, from int [, for int])
+
+  描述: 截取子串。
+
+  返回值类型: bytea
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT substr(E'Th\\000omas'::bytea from 2 for 3) AS RESULT;
+    result
+  ----------
+   \x68006f
+  (1 row)
+  ```
+
+- trim([both] bytes from string)
+
+  描述: 从string的开头和结尾删除只包含bytes中字节的最长字符串。
+
+  返回值类型: bytea
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT trim(E'\\000'::bytea from E'\\000Tom\\000'::bytea) AS RESULT;
+    result
+  ----------
+   \x546f6d
+  (1 row)
+  ```
+
+<span style="font:14px">**二进制字符串函数**</span>
+
+MogDB也提供了函数调用所使用的常用语法。
+
+- btrim(string bytea,bytes bytea)
+
+  描述: 从string的开头和结尾删除只包含bytes中字节的最长的字符串。
+
+  返回值类型: bytea
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT btrim(E'\\000trim\\000'::bytea, E'\\000'::bytea) AS RESULT;
+     result
+  ------------
+   \x7472696d
+  (1 row)
+  ```
+
+- get_bit(string, offset)
+
+  描述: 从字符串中抽取位。
+
+  返回值类型: int
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT get_bit(E'Th\\000omas'::bytea, 45) AS RESULT;
+   result
+  --------
+        1
+  (1 row)
+  ```
+
+- get_byte(string, offset)
+
+  描述: 从字符串中抽取字节。
+
+  返回值类型: int
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT get_byte(E'Th\\000omas'::bytea, 4) AS RESULT;
+   result
+  --------
+      109
+  (1 row)
+  ```
+
+- set_bit(string,offset, newvalue)
+
+  描述: 设置字符串中的位。
+
+  返回值类型: bytea
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT set_bit(E'Th\\000omas'::bytea, 45, 0) AS RESULT;
+        result
+  ------------------
+   \x5468006f6d4173
+  (1 row)
+  ```
+
+- set_byte(string,offset, newvalue)
+
+  描述: 设置字符串中的字节。
+
+  返回值类型: bytea
+
+  示例:
+
+  ```sql
+  mogdb=# SELECT set_byte(E'Th\\000omas'::bytea, 4, 64) AS RESULT;
+        result
+  ------------------
+   \x5468006f406173
+  (1 row)
+  ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/5-bit-string-functions-and-operators.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/5-bit-string-functions-and-operators.md
new file mode 100644
index 0000000000000000000000000000000000000000..de6a6c9a0a1e4b1877d3487370317e4fafb9dbf9
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/5-bit-string-functions-and-operators.md
@@ -0,0 +1,155 @@
+---
+title: 位串函数和操作符
+summary: 位串函数和操作符
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 位串函数和操作符
+
+<span style="font:14px">**位串操作符**</span>
+
+除了常用的比较操作符之外，还可以使用以下的操作符。&、|和#的位串操作数必须等长。在位移的时候，保留原始的位串长度（并以0填充）。
+
+- ||
+
+  描述：位串之间进行连接。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT B'10001' || B'011' AS RESULT;
+    result
+  ----------
+   10001011
+  (1 row)
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  > 单字段内部连续连接操作不建议超过180次。如果超过180次，需拆分为多个连续连接的字符串，在它们之间再执行连接操作。
+  > 例如：str1||str2||str3||str4 拆分为 (str1||str2)||(str3||str4)。
+
+- &
+
+  描述：位串之间进行“与”操作。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT B'10001' & B'01101' AS RESULT;
+   result
+  --------
+   00001
+  (1 row)
+  ```
+
+- |
+
+  描述：位串之间进行"或"操作。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT B'10001' | B'01101' AS RESULT;
+   result
+  --------
+   11101
+  (1 row)
+  ```
+
+- \#
+
+  描述：位串之间如果不一致进行"或"操作。如果两个位串中对应位置都为1或者0，则该位置返回为0。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT B'10001' # B'01101' AS RESULT;
+   result
+  --------
+   11100
+  (1 row)
+  ```
+
+- ~
+
+  描述：位串之间进行"非"操作。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT ~B'10001'AS RESULT;
+   result
+  ----------
+   01110
+  (1 row)
+  ```
+
+- &lt;&lt;
+
+  描述：位串进行左移操作。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT B'10001' << 3 AS RESULT;
+   result
+  ----------
+   01000
+  (1 row)
+  ```
+
+- &gt;&gt;
+
+  描述：位串进行右移操作。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT B'10001' >> 2 AS RESULT;
+   result
+  ----------
+   00100
+  (1 row)
+  ```
+
+下面的SQL标准函数除了可以用于字符串之外，也可以用于位串：length、bit_length、octet_length、position、substring、overlay。
+
+下面的函数用于位串和二进制字符串：get_bit、set_bit。当用于位串时，这些函数位数从字符串的第一位（最左边）作为0位。
+
+另外，可以在整数和bit之间来回转换。示例：
+
+```sql
+mogdb=# SELECT 44::bit(10) AS RESULT;
+   result
+------------
+ 0000101100
+(1 row)
+
+mogdb=# SELECT 44::bit(3) AS RESULT;
+ result
+--------
+ 100
+(1 row)
+
+mogdb=# SELECT cast(-44 as bit(12)) AS RESULT;
+    result
+--------------
+ 111111010100
+(1 row)
+
+mogdb=# SELECT '1110'::bit(4)::integer AS RESULT;
+ result
+--------
+     14
+(1 row)
+
+mogdb=# select substring('10101111'::bit(8), 2);
+ substring
+-----------
+ 0101111
+(1 row)
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+> 只是转换为“bit”的意思是转换成bit(1)，因此只会转换成整数的最低位。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/6-mode-matching-operators.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/6-mode-matching-operators.md
new file mode 100644
index 0000000000000000000000000000000000000000..4c19d85943d04ec2d582606d4353ba8408ffd7d7
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/6-mode-matching-operators.md
@@ -0,0 +1,224 @@
+---
+title: 模式匹配操作符
+summary: 模式匹配操作符
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 模式匹配操作符
+
+数据库提供了三种独立的实现模式匹配的方法：SQL LIKE操作符、SIMILAR TO操作符和POSIX-风格的正则表达式。除了这些基本的操作符外，还有一些函数可用于提取或替换匹配子串并在匹配位置分离一个串。
+
+- LIKE
+
+  描述：判断字符串是否能匹配上LIKE后的模式字符串。如果字符串与提供的模式匹配，则LIKE表达式返回为真（NOT LIKE表达式返回假），否则返回为假（NOT LIKE表达式返回真）。
+
+  匹配规则：
+
+  1. 此操作符只有在它的模式匹配整个串的时候才能成功。如果要匹配在串内任何位置的序列，该模式必须以百分号开头和结尾。
+
+  2. 下划线 （\_）代表（匹配）任何单个字符； 百分号（%）代表任意串的通配符。
+
+  3. 要匹配文本里的下划线或者百分号，在提供的模式里相应字符必须前导逃逸字符。逃逸字符的作用是禁用元字符的特殊含义，缺省的逃逸字符是反斜线，也可以用ESCAPE子句指定一个不同的逃逸字符。
+
+  4. 要匹配逃逸字符本身，写两个逃逸字符。例如要写一个包含反斜线的模式常量，那你就要在SQL语句里写两个反斜线。
+
+     > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif)**说明：**
+     > 参数standard_conforming_strings设置为off时，在文串常量中写的任何反斜线都需要被双写。因此，写一个匹配单个反斜线的模式实际上要在语句里写四个反斜线（你可以通过用ESCAPE选择一个不同的逃逸字符来避免这种情况，这样反斜线就不再是LIKE的特殊字符了。但仍然是字符文本分析器的特殊字符，所以你还是需要两个反斜线)。
+     >
+     > 在兼容MYSQL数据模式时，您也可以通过写ESCAPE ''的方式不选择逃逸字符，这样可以有效地禁用逃逸机制，但是没有办法关闭下划线和百分号在模式中的特殊含义。
+
+  5. 关键字ILIKE可以用于替换LIKE，区别是LIKE大小写敏感，ILIKE大小写不敏感。
+
+  6. 操作符\~\~等效于LIKE，操作符\~\~\*等效于ILIKE。
+
+  示例：
+
+  ```sql
+    mogdb=# SELECT 'abc' LIKE 'abc' AS RESULT;
+     result
+    -----------
+     t
+    (1 row)
+    mogdb=# SELECT 'abc' LIKE 'a%' AS RESULT;
+     result
+    -----------
+     t
+    (1 row)
+    mogdb=# SELECT 'abc' LIKE '_b_' AS RESULT;
+     result
+    -----------
+     t
+    (1 row)
+    mogdb=# SELECT 'abc' LIKE 'c' AS RESULT;
+     result
+    -----------
+     f
+    (1 row)
+  ```
+
+- SIMILAR TO
+
+  描述：SIMILAR TO操作符根据自己的模式是否匹配给定串而返回真或者假。他和LIKE非常类似，只不过他使用SQL标准定义的正则表达式理解模式。
+
+  匹配规则：
+
+  1. 和LIKE一样，此操作符只有在它的模式匹配整个串的时候才能成功。如果要匹配在串内任何位置的序列，该模式必须以百分号开头和结尾。
+
+  2. 下划线 （\_）代表（匹配）任何单个字符； 百分号（%）代表任意串的通配符。
+
+  3. SIMILAR TO也支持下面这些从POSIX正则表达式借用的模式匹配元字符。
+
+     | 元字符 | 含义                                    |
+     | :----- | :-------------------------------------- |
+     | \|     | 表示选择（两个候选之一）                |
+     | *      | 表示重复前面的项零次或更多次            |
+     | +      | 表示重复前面的项一次或更多次            |
+     | ?      | 表示重复前面的项零次或一次              |
+     | {m}    | 表示重复前面的项刚好m次                 |
+     | {m,}   | 表示重复前面的项m次或更多次             |
+     | {m,n}  | 表示重复前面的项至少m次并且不超过n次    |
+     | ()     | 把多个项组合成一个逻辑项                |
+     | \[…\]    | 声明一个字符类，就像POSIX正则表达式一样 |
+
+  4. 前导逃逸字符可以禁止所有这些元字符的特殊含义。逃逸字符的使用规则和LIKE一样。
+
+  正则表达式函数：
+
+  支持使用函数[substring(string from pattern)](3-character-processing-functions-and-operators)截取匹配SQL正则表达式的子字符串。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT 'abc' SIMILAR TO 'abc' AS RESULT;
+   result
+  -----------
+   t
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT 'abc' SIMILAR TO 'a' AS RESULT;
+   result
+  -----------
+   f
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT 'abc' SIMILAR TO '%(b|d)%' AS RESULT;
+   result
+  -----------
+   t
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT 'abc' SIMILAR TO '(b|c)%'  AS RESULT;
+   result
+  -----------
+   f
+  (1 row)
+  ```
+
+- POSIX正则表达式
+
+  描述：正则表达式是一个字符序列，它是定义一个串集合 （一个正则集）的缩写。 如果一个串是正则表达式描述的正则集中的一员时， 我们就说这个串匹配该正则表达式。 POSIX正则表达式提供了比LIKE和SIMILAR TO操作符更强大的含义。[表1](#正则表达式匹配操作符)列出了所有可用于POSIX正则表达式模式匹配的操作符。
+
+  **表 1** 正则表达式匹配操作符<a id="正则表达式匹配操作符"> </a>
+
+  | 操作符 | 描述                           | 例子                     |
+  | :----- | :----------------------------- | :----------------------- |
+  | ~      | 匹配正则表达式，大小写敏感     | 'thomas' ~ '.*thomas.*'  |
+  | ~      | 匹配正则表达式，大小写不敏感   | 'thomas' ~ '.*Thomas.*'  |
+  | !~     | 不匹配正则表达式，大小写敏感   | 'thomas' !~ '.*Thomas.*' |
+  | !~     | 不匹配正则表达式，大小写不敏感 | 'thomas' !~ '.*vadim.*'  |
+
+  匹配规则：
+
+  1. 与LIKE不同，正则表达式允许匹配串里的任何位置，除非该正则表达式显式地挂接在串的开头或者结尾。
+
+  2. 除了上文提到的元字符外， POSIX正则表达式还支持下列模式匹配元字符。
+
+     | 元字符 | 含义             |
+     | :----- | :--------------- |
+     | ^      | 表示串开头的匹配 |
+     | $      | 表示串末尾的匹配 |
+     | .      | 匹配任意单个字符 |
+
+  正则表达式函数：
+
+  POSIX正则表达式支持下面函数。
+
+  - [substring(string from pattern)](3-character-processing-functions-and-operators)函数提供了抽取一个匹配POSIX正则表达式模式的子串的方法。
+
+  - [regexp_replace(string, pattern, replacement [,flags ])](3-character-processing-functions-and-operators)函数提供了将匹配POSIX正则表达式模式的子串替换为新文本的功能。
+
+  - [regexp_matches(string text, pattern text [, flags text])](3-character-processing-functions-and-operators)函数返回一个文本数组，该数组由匹配一个POSIX正则表达式模式得到的所有被捕获子串构成。
+
+  - [regexp_split_to_table(string text, pattern text [, flags text])](3-character-processing-functions-and-operators)函数把一个POSIX正则表达式模式当作一个定界符来分离一个串。
+
+  - [regexp_split_to_array(string text, pattern text [, flags text ])](3-character-processing-functions-and-operators)和regexp_split_to_table类似，是一个正则表达式分离函数，不过它的结果以一个text数组的形式返回。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+    > 正则表达式分离函数会忽略零长度的匹配，这种匹配发生在串的开头或结尾或者正好发生在前一个匹配之后。这和正则表达式匹配的严格定义是相悖的，后者由regexp_matches实现，但是通常前者是实际中最常用的行为。
+
+  示例：
+
+  ```sql
+  mogdb=#  SELECT 'abc' ~ 'Abc' AS RESULT;
+  result
+  --------
+   f
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT 'abc' ~* 'Abc' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT 'abc' !~ 'Abc' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT 'abc'!~* 'Abc' AS RESULT;
+   result
+  --------
+   f
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT 'abc' ~ '^a' AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT 'abc' ~ '(b|d)'AS RESULT;
+   result
+  --------
+   t
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT 'abc' ~ '^(b|c)'AS RESULT;
+   result
+  --------
+   f
+  (1 row)
+  ```
+
+  虽然大部分的正则表达式搜索都能很快地执行，但是正则表达式仍可能被人为地弄成需要任意长的时间和任意量的内存进行处理。不建议从非安全模式来源接受正则表达式搜索模式，如果必须这样做，建议加上语句超时限制。使用SIMILAR TO模式的搜索具有同样的安全性危险， 因为SIMILAR TO提供了很多和POSIX-风格正则表达式相同的能力。LIKE搜索比其他两种选项简单得多，因此在接受非安全模式来源搜索时要更安全些。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/7-mathematical-functions-and-operators.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/7-mathematical-functions-and-operators.md
new file mode 100644
index 0000000000000000000000000000000000000000..eadfaa158291a831217826e27402da9c46190f58
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/7-mathematical-functions-and-operators.md
@@ -0,0 +1,1122 @@
+---
+title: 数字操作函数和操作符
+summary: 数字操作函数和操作符
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 数字操作函数和操作符
+
+## 数字操作符
+
+- \+
+
+  描述：加
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT 2+3 AS RESULT;
+   result
+  --------
+        5
+  (1 row)
+  ```
+
+- \-
+
+  描述：减
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT 2-3 AS RESULT;
+   result
+  --------
+       -1
+  (1 row)
+  ```
+
+- \*
+
+  描述：乘
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT 2*3 AS RESULT;
+   result
+  --------
+        6
+  (1 row)
+  ```
+
+- /
+
+  描述：除（除法操作符不会取整）
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT 4/2 AS RESULT;
+   result
+  --------
+        2
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT 4/3 AS RESULT;
+        result
+  ------------------
+   1.33333333333333
+  (1 row)
+  ```
+
+- +/-
+
+  描述：正/负
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT -2 AS RESULT;
+   result
+  --------
+       -2
+  (1 row)
+  ```
+
+- %
+
+  描述：模（求余）
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT 5%4 AS RESULT;
+   result
+  --------
+        1
+  (1 row)
+  ```
+
+- @
+
+  描述：绝对值
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT @ -5.0 AS RESULT;
+   result
+  --------
+      5.0
+  (1 row)
+  ```
+
+- \^
+
+  描述：幂（指数运算）
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT 2.0^3.0 AS RESULT;
+         result
+  --------------------
+   8.0000000000000000
+  (1 row)
+  ```
+
+- |/
+
+  描述：平方根
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT |/ 25.0 AS RESULT;
+   result
+  --------
+        5
+  (1 row)
+  ```
+
+- ||/
+
+  描述：立方根
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT ||/ 27.0 AS RESULT;
+   result
+  --------
+        3
+  (1 row)
+  ```
+
+- !
+
+  描述：阶乘
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT 5! AS RESULT;
+   result
+  --------
+      120
+  (1 row)
+  ```
+
+- !!
+
+  描述：阶乘（前缀操作符）
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT !!5 AS RESULT;
+   result
+  --------
+      120
+  (1 row)
+  ```
+
+- &
+
+  描述：二进制AND
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT 91&15  AS RESULT;
+   result
+  --------
+       11
+  (1 row)
+  ```
+
+- |
+
+  描述：二进制OR
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT 32|3  AS RESULT;
+   result
+  --------
+       35
+  (1 row)
+  ```
+
+- \#
+
+  描述：二进制XOR
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT 17#5  AS RESULT;
+   result
+  --------
+       20
+  (1 row)
+  ```
+
+- ~
+
+  描述：二进制NOT
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT ~1 AS RESULT;
+   result
+  --------
+       -2
+  (1 row)
+  ```
+
+- &lt;&lt;
+
+  描述：二进制左移
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT 1<<4 AS RESULT;
+   result
+  --------
+       16
+  (1 row)
+  ```
+
+- &gt;&gt;
+
+  描述：二进制右移
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT 8>>2 AS RESULT;
+   result
+  --------
+        2
+  (1 row)
+  ```
+
+## 数字操作函数
+
+- abs(x)
+
+  描述：绝对值。
+
+  返回值类型：和输入相同。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT abs(-17.4);
+   abs
+  ------
+   17.4
+  (1 row)
+  ```
+
+- acos(x)
+
+  描述：反余弦。
+
+  返回值类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT acos(-1);
+         acos
+  ------------------
+   3.14159265358979
+  (1 row)
+  ```
+
+- asin(x)
+
+  描述：反正弦。
+
+  返回值类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT asin(0.5);
+         asin
+  ------------------
+   .523598775598299
+  (1 row)
+  ```
+
+- atan(x)
+
+  描述：反正切。
+
+  返回值类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT atan(1);
+         atan
+  ------------------
+   .785398163397448
+  (1 row)
+  ```
+
+- atan2(y, x)
+
+  描述：y/x的反正切。
+
+  返回值类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT atan2(2, 1);
+        atan2
+  ------------------
+   1.10714871779409
+  (1 row)
+  ```
+
+- bitand(integer, integer)
+
+  描述：计算两个数字与运算(&)的结果。
+
+  返回值类型：bigint类型数字。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT bitand(127, 63);
+   bitand
+  --------
+       63
+  (1 row)
+  ```
+
+- cbrt(dp)
+
+  描述：立方根。
+
+  返回值类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT cbrt(27.0);
+   cbrt
+  ------
+      3
+  (1 row)
+  ```
+
+- ceil(x)
+
+  描述：不小于参数的最小的整数。
+
+  返回值类型：整数。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT ceil(-42.8);
+   ceil
+  ------
+    -42
+  (1 row)
+  ```
+
+- ceiling(dp or numeric)
+
+  描述：不小于参数的最小整数（ceil的别名）。
+
+  返回值类型：dp or numeric，不考虑隐式类型转换的情况下与输入相同。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT ceiling(-95.3);
+   ceiling
+  ---------
+       -95
+  (1 row)
+  ```
+
+- cos(x)
+
+  描述：余弦。
+
+  返回值类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT cos(-3.1415927);
+          cos
+  -------------------
+   -.999999999999999
+  (1 row)
+  ```
+
+- cot(x)
+
+  描述：余切。
+
+  返回值类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT cot(1);
+         cot
+  ------------------
+   .642092615934331
+  (1 row)
+  ```
+
+- degrees(dp)
+
+  描述：把弧度转为角度。
+
+  返回值类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT degrees(0.5);
+       degrees
+  ------------------
+   28.6478897565412
+  (1 row)
+  ```
+
+- div(y numeric, x numeric)
+
+  描述：y除以x的商的整数部分。
+
+  返回值类型：numeric
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT div(9,4);
+   div
+  -----
+     2
+  (1 row)
+  ```
+
+- exp(x)
+
+  描述：自然指数。
+
+  返回值类型：dp or numeric，不考虑隐式类型转换的情况下与输入相同。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT exp(1.0);
+          exp
+  --------------------
+   2.7182818284590452
+  (1 row)
+  ```
+
+- floor(x)
+
+  描述：不大于参数的最大整数。
+
+  返回值类型：与输入相同。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT floor(-42.8);
+   floor
+  -------
+     -43
+  (1 row)
+  ```
+
+- int1(in)
+
+  描述：将传入的text参数转换为int1类型值并返回。
+
+  返回值类型：int1
+
+  示例：
+
+  ```sql
+  mogdb=# select int1('123');
+   int1
+  ------
+   123
+  (1 row)
+  mogdb=# select int1('a');
+   int1
+  ------
+     0
+  (1 row)
+  ```
+
+- int2(in)
+
+  描述：将传入参数转换为int2类型值并返回。
+
+  支持的入参类型包括float4、float8、numeric、text。
+
+  返回值类型：int2
+
+  示例：
+
+  ```sql
+  mogdb=# select int2('1234');
+   int2
+  ------
+   1234
+  (1 row)
+  mogdb=# select int2(25.3);
+   int2
+  ------
+     25
+  (1 row)
+  ```
+
+- int4(in)
+
+  描述：将传入参数转换为int4类型值并返回。
+
+  支持的入参类型包括bit、boolean、char、duoble precision、numeric、real、smallint、text。
+
+  返回值类型：int4
+
+  示例：
+
+  ```sql
+  mogdb=# select int4('789');
+   int4
+  ------
+   789
+  (1 row)
+  mogdb=# select int4(99.9);
+   int4
+  ------
+     99
+  (1 row)
+  ```
+
+- radians(dp)
+
+  描述：把角度转为弧度。
+
+  返回值类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT radians(45.0);
+       radians
+  ------------------
+   .785398163397448
+  (1 row)
+  ```
+
+- random()
+
+  描述：0.0到1.0之间的随机数。
+
+  返回值类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT random();
+        random
+  ------------------
+   .824823560658842
+  (1 row)
+  ```
+
+- multiply(x double precision or text, y double precision or text)
+
+  描述：x和y的乘积。
+
+  返回值类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT multiply(9.0, '3.0');
+       multiply
+  -------------------
+                 27
+  (1 row)
+  mogdb=# SELECT multiply('9.0', 3.0);
+       multiply
+  -------------------
+                 27
+  (1 row)
+  ```
+
+- ln(x)
+
+  描述：自然对数。
+
+  返回值类型：dp or numeric，不考虑隐式类型转换的情况下与输入相同。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT ln(2.0);
+          ln
+  -------------------
+   .6931471805599453
+  (1 row)
+  ```
+
+- log(x)
+
+  描述：以10为底的对数。
+
+  返回值类型：与输入相同。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT log(100.0);
+          log
+  --------------------
+   2.0000000000000000
+  (1 row)
+  ```
+
+- log(b numeric, x numeric)
+
+  描述：以b为底的对数。
+
+  返回值类型：numeric
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT log(2.0, 64.0);
+          log
+  --------------------
+   6.0000000000000000
+  (1 row)
+  ```
+
+- mod(x,y)
+
+  描述：x/y的余数（模）。如果x是0，则返回0。
+
+  返回值类型：与参数类型相同。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT mod(9,4);
+   mod
+  -----
+     1
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT mod(9,0);
+   mod
+  -----
+     9
+  (1 row)
+  ```
+
+- pi()
+
+  描述："π"常量。
+
+  返回值类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT pi();
+          pi
+  ------------------
+   3.14159265358979
+  (1 row)
+  ```
+
+- power(a double precision, b double precision)
+
+  描述：a的b次幂。
+
+  返回值类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT power(9.0, 3.0);
+          power
+  ----------------------
+   729.0000000000000000
+  (1 row)
+  ```
+
+- round(x)
+
+  描述：离输入参数最近的整数。
+
+  返回值类型：与输入相同。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT round(42.4);
+   round
+  -------
+      42
+  (1 row)
+
+  mogdb=# SELECT round(42.6);
+   round
+  -------
+      43
+  (1 row)
+  ```
+
+- round(v numeric, s int)
+
+  描述：保留小数点后s位，s后一位进行四舍五入。
+
+  返回值类型：numeric
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT round(42.4382, 2);
+   round
+  -------
+   42.44
+  (1 row)
+  ```
+
+- setseed(dp)
+
+  描述：为随后的random()调用设置种子(-1.0到1.0之间，包含)。
+
+  返回值类型：void
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT setseed(0.54823);
+   setseed
+  ---------
+
+  (1 row)
+  ```
+
+- sign(x)
+
+  描述：输出此参数的符号。
+
+  返回值类型：-1表示负数，0表示0，1表示正数。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT sign(-8.4);
+   sign
+  ------
+     -1
+  (1 row)
+  ```
+
+- sin(x)
+
+  描述：正弦。
+
+  返回值类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT sin(1.57079);
+         sin
+  ------------------
+   .999999999979986
+  (1 row)
+  ```
+
+- sqrt(x)
+
+  描述：平方根。
+
+  返回值类型：dp or numeric，不考虑隐式类型转换的情况下与输入相同。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT sqrt(2.0);
+         sqrt
+  -------------------
+   1.414213562373095
+  (1 row)
+  ```
+
+- tan(x)
+
+  描述：正切。
+
+  返回值类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT tan(20);
+         tan
+  ------------------
+   2.23716094422474
+  (1 row)
+  ```
+
+- trunc(x)
+
+  描述：截断（取整数部分）。
+
+  返回值类型：与输入相同。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT trunc(42.8);
+   trunc
+  -------
+      42
+  (1 row)
+  ```
+
+- trunc(v numeric, s int)
+
+  描述：截断为s位小数。
+
+  返回值类型：numeric
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT trunc(42.4382, 2);
+   trunc
+  -------
+   42.43
+  (1 row)
+  ```
+
+- smgrne(a smgr, b smgr)
+
+  描述：比较两个smgr类型整数是否不相等。
+
+  返回值类型：bool
+
+- smgreq(a smgr, b smgr)
+
+  描述：比较两个smgr类型整数是否相等。
+
+  返回值类型：bool
+
+- int1abs
+
+    描述：返回uint8类型数据的绝对值。
+
+    参数：tinyint
+
+    返回值类型：tinyint
+
+- int1and
+
+    描述：返回两个uint8类型数据按位与的结果。
+
+    参数：tinyint, tinyint
+
+    返回值类型：tinyint
+
+- int1cmp
+
+    描述：返回两个uint8类型数据比较的结果，若第一个参数大，则返回1；若第二个参数大，则返回-1；若相等，则返回0。
+
+    参数：tinyint, tinyint
+
+    返回值类型：integer
+
+- int1div
+
+    描述：返回两个uint8类型数据相除的结果，结果为float8类型。
+
+    参数：tinyint, tinyint
+
+    返回值类型：tinyint
+
+- int1eq
+
+    描述：比较两个uint8类型数据是否相等。
+
+    参数：tinyint, tinyint
+
+    返回值类型：boolean
+
+- int1ge
+
+    描述：判断两个uint8类型数据是否第一个参数大于等于第二个参数。
+
+    参数：tinyint, tinyint
+
+    返回值类型：boolean
+
+- int1gt
+
+    描述：无符号1字节整数做大于运算。
+
+    参数：tinyint, tinyint
+
+    返回值类型：boolean
+
+- int1larger
+
+    描述：无符号1字节整数求最大值。
+
+    参数：tinyint, tinyint
+
+    返回值类型：tinyint
+
+- int1le
+
+    描述：无符号1字节整数做小于等于运算。
+
+    参数：tinyint, tinyint
+
+    返回值类型：boolean
+
+- int1lt
+
+    描述：无符号1字节整数做小于运算。
+
+    参数：tinyint, tinyint
+
+    返回值类型：boolean
+
+- int1smaller
+
+    描述：无符号1字节整数求最小算。
+
+    参数：tinyint, tinyint
+
+    返回值类型：tinyint
+
+- int1inc
+
+    描述：无符号1字节整数加一。
+
+    参数：tinyint
+
+    返回值类型：tinyint
+
+- int1mi
+
+    描述：无符号一字节整数做差运算。
+
+    参数：tinyint, tinyint
+
+    返回值类型：tinyint
+
+- int1mod
+
+    描述：无符号一字节整数做取余运算。
+
+    参数：tinyint, tinyint
+
+    返回值类型：tinyint
+
+- int1mul
+
+    描述：无符号一字节整数做乘法运算。
+
+    参数：tinyint, tinyint
+
+    返回值类型：tinyint
+
+- int1ne
+
+    描述：无符号一字节整数不等于运算。
+
+    参数：tinyint, tinyint
+
+    返回值类型：boolean
+
+- int1pl
+
+    描述：无符号一字节整数加法。
+
+    参数：tinyint, tinyint
+
+    返回值类型：tinyint
+
+- int1um
+
+    描述：无符号一字节数去相反数并返回有符号二字节整数。
+
+    参数：tinyint
+
+    返回值类型：smallint
+
+- int1xor
+
+    描述：无符号一字节整数异或操作。
+
+    参数：tinyint, tinyint
+
+    返回值类型：tinyint
+
+- cash_div_int1
+
+    描述：对money类型进行除法运算。
+
+    参数：money, tinyint
+
+    返回值类型：money
+
+- cash_mul_int1
+
+    描述：对money类型进行乘法运算。
+
+    参数：money, tinyint
+
+    返回值类型：money
+
+- int1not
+
+    描述：无符号一字节整数二进制位翻转。
+
+    参数：tinyint
+
+    返回值类型：tinyint
+
+- int1or
+
+    描述：无符号一字节整数或运算。
+
+    参数：tinyint, tinyint
+
+    返回值类型：tinyint
+
+- int1shl
+
+    描述：无符号一字节整数左移指定位数。
+
+    参数：tinyint, integer
+
+    返回值类型：tinyint
+
+- width_bucket(op numeric, b1 numeric, b2 numeric, count int)
+
+  描述：返回一个桶，这个桶是在一个有count个桶，上界为b1下界为b2的等深柱图中operand将被赋予的那个桶。
+
+  返回值类型：int
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT width_bucket(5.35, 0.024, 10.06, 5);
+   width_bucket
+  --------------
+              3
+  (1 row)
+  ```
+
+- width_bucket(op dp, b1 dp, b2 dp, count int)
+
+  描述：返回一个桶，这个桶是在一个有count个桶，上界为b1下界为b2的等深柱图中operand将被赋予的那个桶。
+
+  返回值类型：int
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT width_bucket(5.35, 0.024, 10.06, 5);
+   width_bucket
+  --------------
+              3
+  (1 row)
+  ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/8-date-and-time-processing-functions-and-operators.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/8-date-and-time-processing-functions-and-operators.md
new file mode 100644
index 0000000000000000000000000000000000000000..41cf8cca28e8b462741e850320b1c77dfd58ff2c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/8-date-and-time-processing-functions-and-operators.md
@@ -0,0 +1,1324 @@
+---
+title: 时间和日期处理函数和操作符
+summary: 时间和日期处理函数和操作符
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 时间和日期处理函数和操作符
+
+## 时间日期操作符
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-warning.gif) **警告:**
+> 用户在使用时间和日期操作符时，对应的操作数请使用明确的类型前缀修饰，以确保数据库在解析操作数的时候能够与用户预期一致，不会产生用户非预期的结果。
+> 比如下面示例没有明确数据类型就会出现异常错误。
+>
+> ```sql
+> SELECT date '2001-10-01' - '7' AS RESULT;
+> ```
+
+**表 1** 时间和日期操作符
+
+| 操作符 | 示例                                                         |
+| ------ | ------------------------------------------------------------ |
+| +      | `mogdb=# SELECT date '2001-09-28' + integer '7' AS RESULT;       result -------- 2001-10-05 (1 row)` |
+|        | `mogdb=# SELECT date '2001-09-28' + interval '1 hour' AS RESULT;       result -------- 2001-09-28 01:00:00 (1 row)` |
+|        | `mogdb=# SELECT date '2001-09-28' + time '03:00' AS RESULT;       result -------- 2001-09-28 03:00:00 (1 row)` |
+|        | `mogdb=# SELECT interval '1 day' + interval '1 hour' AS RESULT;     result ------ 1 day 01:00:00 (1 row)` |
+|        | `mogdb=# SELECT timestamp '2001-09-28 01:00' + interval '23 hours' AS RESULT;       result -------- 2001-09-29 00:00:00 (1 row)` |
+|        | `mogdb=# SELECT time '01:00' + interval '3 hours' AS RESULT;  result ---- 04:00:00 (1 row)` |
+| -      | `mogdb=# SELECT date '2001-10-01' - date '2001-09-28' AS RESULT; result ---- 3 (1 row)` |
+|        | `mogdb=# SELECT date '2001-10-01' - integer '7' AS RESULT;       result -------- 2001-09-24 00:00:00 (1 row)` |
+|        | `mogdb=# SELECT date '2001-09-28' - interval '1 hour' AS RESULT;       result -------- 2001-09-27 23:00:00 (1 row)` |
+|        | `mogdb=# SELECT time '05:00' - time '03:00' AS RESULT;  result ---- 02:00:00 (1 row)` |
+|        | `mogdb=# SELECT time '05:00' - interval '2 hours' AS RESULT;  result ---- 03:00:00 (1 row)` |
+|        | `mogdb=# SELECT timestamp '2001-09-28 23:00' - interval '23 hours' AS RESULT;       result -------- 2001-09-28 00:00:00 (1 row)` |
+|        | `mogdb=# SELECT interval '1 day' - interval '1 hour' AS RESULT;  result ---- 23:00:00 (1 row)` |
+|        | `mogdb=# SELECT timestamp '2001-09-29 03:00' - timestamp '2001-09-27 12:00' AS RESULT;     result ------ 1 day 15:00:00 (1 row)` |
+| *      | `mogdb=# SELECT 900 * interval '1 second' AS RESULT;  result ---- 00:15:00 (1 row)` |
+|        | `mogdb=# SELECT 21 * interval '1 day' AS RESULT; result ---- 21 days (1 row)` |
+|        | `mogdb=# SELECT double precision '3.5' * interval '1 hour' AS RESULT;  result ---- 03:30:00 (1 row)` |
+| /      | `mogdb=# SELECT interval '1 hour' / double precision '1.5' AS RESULT;  result ---- 00:40:00 (1 row)` |
+
+## 时间/日期函数
+
+- age(timestamp, timestamp)
+
+  描述：将两个参数相减，并以年、月、日作为返回值。若相减值为负，则函数返回亦为负，入参可以都带timezone或都不带timezone。
+
+  返回值类型：interval
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT age(timestamp '2001-04-10', timestamp '1957-06-13');
+             age
+  -------------------------
+   43 years 9 mons 27 days
+  (1 row)
+  ```
+
+- age(timestamp)
+
+  描述：当前时间和参数相减，入参可以带或者不带timezone。
+
+  返回值类型：interval
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT age(timestamp '1957-06-13');
+             age
+  -------------------------
+   60 years 2 mons 18 days
+  (1 row)
+  ```
+
+- clock_timestamp()
+
+  描述：实时时钟的当前时间戳。
+
+  返回值类型：timestamp with time zone
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT clock_timestamp();
+          clock_timestamp
+  -------------------------------
+   2017-09-01 16:57:36.636205+08
+  (1 row)
+  ```
+
+- current_date
+
+  描述：当前日期。
+
+  返回值类型：date
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT current_date;
+      date
+  ------------
+   2017-09-01
+  (1 row)
+  ```
+
+- current_time
+
+  描述：当前时间。
+
+  返回值类型：time with time zone
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT current_time;
+         timetz
+  --------------------
+   16:58:07.086215+08
+  (1 row)
+  ```
+
+- current_timestamp
+
+  描述：当前日期及时间。
+
+  返回值类型：timestamp with time zone
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT current_timestamp;
+         pg_systimestamp
+  ------------------------------
+   2017-09-01 16:58:19.22173+08
+  (1 row)
+  ```
+
+- systimestamp <a id = 'systimestamp'> </a>
+
+  描述：返回数据库所在系统的系统日期，包括分数秒和时区。
+
+  返回值类型：TIMESTAMP WITH TIME ZONE
+
+  示例：
+
+  ```sql
+  mogdb=# select systimestamp;
+  pg_systimestamp
+  -----------------------------
+  2021-12-24 14:34:24.6903+08
+  (1 row)
+  ```
+
+- date_part(text, timestamp)
+
+  描述：获取日期/时间值中子域的值，例如年或者小时的值。等效于extract(field from timestamp)。
+
+  timestamp类型：abstime、date、interval、reltime、time with time zone、time without time zone、timestamp with time zone、timestamp without time zone。
+
+  返回值类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT date_part('hour', timestamp '2001-02-16 20:38:40');
+   date_part
+           20
+  (1 row)
+  ```
+
+- date_part(text, interval)
+
+  描述：获取日期/时间值中子域的值。获取月份值时，如果月份值大于12，则取与12的模。等效于extract(field from timestamp)。
+
+  返回值类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT date_part('month', interval '2 years 3 months');
+   date_part
+  -----------
+           3
+  (1 row)
+  ```
+
+- date_trunc(text, timestamp)
+
+  描述：截取到参数text指定的精度。
+
+  返回值类型：interval、timestamp with time zone、timestamp without time zone
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT date_trunc('hour', timestamp  '2001-02-16 20:38:40');
+       date_trunc
+  ---------------------
+   2001-02-16 20:00:00
+  (1 row)
+  ```
+
+- trunc(timestamp)
+
+  描述：默认按天截取。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT trunc(timestamp  '2001-02-16 20:38:40');                                                                                                                                                                   trunc
+  ---------------------
+  2001-02-16 00:00:00
+  (1 row)
+  ```
+
+- daterange(arg1, arg2)
+
+    描述：获取时间边界信息。arg1和arg2的类型为date。
+
+    返回值类型：daterange
+
+    示例：
+
+    ```sql
+    mogdb=# select daterange('2000-05-06','2000-08-08');
+            daterange
+    -------------------------
+     [2000-05-06,2000-08-08)
+    (1 row)
+    ```
+
+- daterange(arg1, arg2, text)
+
+    描述：获取时间边界信息。arg1和arg2的类型为date，text类型为text。
+
+    返回值类型：daterange
+
+    示例：
+
+    ```sql
+    mogdb=# select daterange('2000-05-06','2000-08-08','[]');
+            daterange
+    -------------------------
+     [2000-05-06,2000-08-09)
+    (1 row)
+    ```
+
+- extract(field from timestamp)
+
+  描述：获取小时的值。
+
+  返回值类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT extract(hour from timestamp '2001-02-16 20:38:40');
+   date_part
+  -----------
+          20
+  (1 row)
+  ```
+
+- extract(field from interval)
+
+  描述：获取月份的值。如果大于12，则取与12的模。
+
+  返回值类型：double precision
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT extract(month from interval '2 years 3 months');
+   date_part
+  -----------
+           3
+  (1 row)
+  ```
+
+- isfinite(date)
+
+  描述：测试是否为有效日期。
+
+  返回值类型：Boolean
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT isfinite(date '2001-02-16');
+   isfinite
+  ----------
+   t
+  (1 row)
+  ```
+
+- isfinite(timestamp)
+
+  描述：测试判断是否为有效时间。
+
+  返回值类型：Boolean
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT isfinite(timestamp '2001-02-16 21:28:30');
+   isfinite
+  ----------
+   t
+  (1 row)
+  ```
+
+- isfinite(interval)
+
+  描述：测试是否为有效区间。
+
+  返回值类型：Boolean
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT isfinite(interval '4 hours');
+   isfinite
+  ----------
+   t
+  (1 row)
+  ```
+
+- justify_days(interval)
+
+  描述：将时间间隔以月（30天为一月）为单位。
+
+  返回值类型：interval
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT justify_days(interval '35 days');
+   justify_days
+  --------------
+   1 mon 5 days
+  (1 row)
+  ```
+
+- justify_hours(interval)
+
+  描述：将时间间隔以天（24小时为一天）为单位。
+
+  返回值类型：interval
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT JUSTIFY_HOURS(INTERVAL '27 HOURS');
+   justify_hours
+  ----------------
+   1 day 03:00:00
+  (1 row)
+  ```
+
+- justify_interval(interval)
+
+  描述：结合justify_days和justify_hours，调整interval。
+
+  返回值类型：interval
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT JUSTIFY_INTERVAL(INTERVAL '1 MON -1 HOUR');
+   justify_interval
+  ------------------
+   29 days 23:00:00
+  (1 row)
+  ```
+
+- localtime
+
+  描述：当前时间。
+
+  返回值类型：time
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT localtime AS RESULT;
+       result
+  ----------------
+   16:05:55.664681
+  (1 row)
+  ```
+
+- localtimestamp
+
+  描述：当前日期及时间。
+
+  返回值类型：timestamp
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT localtimestamp;
+           timestamp
+  ----------------------------
+   2017-09-01 17:03:30.781902
+  (1 row)
+  ```
+
+- now()
+
+  描述：当前日期及时间。
+
+  返回值类型：timestamp with time zone
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT now();
+                now
+  -------------------------------
+   2017-09-01 17:03:42.549426+08
+  (1 row)
+  ```
+
+- timenow
+
+    描述：当前日期及时间。
+
+    返回值类型：timestamp with time zone
+
+    示例：
+
+    ```sql
+    mogdb=# select timenow();
+            timenow
+    ------------------------
+     2020-06-23 20:36:56+08
+    (1 row)
+    ```
+
+- numtodsinterval(num, interval_unit)
+
+  描述：将数字转换为interval类型。num为numeric类型数字，interval_unit为固定格式字符串（'DAY' | 'HOUR' | 'MINUTE' | 'SECOND'）。
+
+  可以通过设置参数IntervalStyle为a，兼容该函数interval输出格式。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT numtodsinterval(100, 'HOUR');
+   numtodsinterval
+  -----------------
+   100:00:00
+  (1 row)
+
+  mogdb=# SET intervalstyle = a;
+  SET
+  mogdb=# SELECT numtodsinterval(100, 'HOUR');
+          numtodsinterval
+  -------------------------------
+   +000000004 04:00:00.000000000
+  (1 row)
+  ```
+
+- pg_sleep(seconds)
+
+  描述：服务器线程延迟时间，单位为秒。
+
+  返回值类型：void
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT pg_sleep(10);
+   pg_sleep
+  ----------
+
+  (1 row)
+  ```
+
+- statement_timestamp()
+
+  描述：当前日期及时间。
+
+  返回值类型：timestamp with time zone
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT statement_timestamp();
+        statement_timestamp
+  -------------------------------
+   2017-09-01 17:04:39.119267+08
+  (1 row)
+  ```
+
+- sysdate
+
+  描述：当前日期及时间。
+
+  返回值类型：timestamp
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT sysdate;
+         sysdate
+  ---------------------
+   2017-09-01 17:04:49
+  (1 row)
+  ```
+
+- timeofday()
+
+  描述：当前日期及时间（像clock_timestamp，但是返回时为text）。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT timeofday();
+                timeofday
+  -------------------------------------
+   Fri Sep 01 17:05:01.167506 2017 CST
+  (1 row)
+  ```
+
+- transaction_timestamp()
+
+  描述：当前日期及时间，与current_timestamp等效。
+
+  返回值类型：timestamp with time zone
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT transaction_timestamp();
+       transaction_timestamp
+  -------------------------------
+   2017-09-01 17:05:13.534454+08
+  (1 row)
+  ```
+
+- add_months(d,n)
+
+  描述：用于计算时间点d再加上n个月的时间。
+
+  返回值类型：timestamp
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT add_months(to_date('2017-5-29', 'yyyy-mm-dd'), 11) FROM dual;
+       add_months
+  ---------------------
+   2018-04-29 00:00:00
+  (1 row)
+  ```
+
+- last_day(d)
+
+  描述：用于计算时间点d当月最后一天的时间。
+
+  返回值类型：timestamp
+
+  示例：
+
+  ```sql
+  mogdb=# select last_day(to_date('2017-01-01', 'YYYY-MM-DD')) AS cal_result;
+       cal_result
+  ---------------------
+   2017-01-31 00:00:00
+  (1 row)
+  ```
+
+- next_day(x,y)
+
+  描述：用于计算时间点x开始的下一个星期几（y）的时间。
+
+  返回值类型：timestamp
+
+  示例：
+
+  ```sql
+  mogdb=# select next_day(timestamp '2017-05-25 00:00:00','Sunday')AS cal_result;
+       cal_result
+  ---------------------
+   2017-05-28 00:00:00
+  (1 row)
+  ```
+
+- tinterval(abstime, abstime )
+
+    描述：用两个绝对时间创建时间间隔。
+
+    返回值类型：tinterval
+
+    示例：
+
+    ```sql
+    mogdb=# call tinterval(abstime 'May 10, 1947 23:59:12', abstime 'Mon May  1 00:30:30 1995');
+                          tinterval
+    -----------------------------------------------------
+     ["1947-05-10 23:59:12+08" "1995-05-01 00:30:30+08"]
+    (1 row)
+    ```
+
+- tintervalend(tinterval)
+
+    描述：返回tinteval的结束时间。
+
+    返回值类型：abstime
+
+    示例：
+
+    ```sql
+    mogdb=# select tintervalend('["Sep 4, 1983 23:59:12" "Oct4, 1983 23:59:12"]');
+          tintervalend
+    ------------------------
+     1983-10-04 23:59:12+08
+    (1 row)
+    ```
+
+- tintervalrel(tinterval)
+
+    描述：计算并返回tinterval的相对时间。
+
+    返回值类型：reltime
+
+    示例：
+
+    ```sql
+    mogdb=# select tintervalrel('["Sep 4, 1983 23:59:12" "Oct4, 1983 23:59:12"]');
+     tintervalrel
+    --------------
+     1 mon
+    (1 row)
+    ```
+
+- smalldatetime_ge
+
+    描述：判断是否第一个参数大于等于第二个参数。
+
+    参数：smalldatetime, smalldatetime
+
+    返回值类型：boolean
+
+- smalldatetime_cmp
+
+    描述：对比smalldatetime是否相等。
+
+    参数：smalldatetime, smalldatetime
+
+    返回值类型：integer
+
+- smalldatetime_eq
+
+    描述：对比smalldatetime是否相等。
+
+    参数：smalldatetime, smalldatetime
+
+    返回值类型：boolean。
+
+- smalldatetime_gt
+
+    描述：判断是否第一个参数大于第二个参数。
+
+    参数：smalldatetime, smalldatetime
+
+    返回值类型：boolean
+
+- smalldatetime_hash
+
+    描述：计算timestamp对应的哈希值。
+
+    参数：smalldatetime
+
+    返回值类型：integer
+
+- smalldatetime_in
+
+    描述：输入timestamp。
+
+    参数：cstring, oid, integer
+
+    返回值类型：smalldatetime
+
+- smalldatetime_larger
+
+    描述：返回较大的timestamp。
+
+    参数：smalldatetime, smalldatetime
+
+    返回值类型：smalldatetime
+
+- smalldatetime_le
+
+    描述：判断是否第一个参数小于等于第二个参数。
+
+    参数：smalldatetime, smalldatetime
+
+    返回值类型：boolean
+
+- smalldatetime_lt
+
+    描述：判断是否第一个参数小于第二个参数。
+
+    参数：smalldatetime, smalldatetime
+
+    返回值类型：boolean
+
+- smalldatetime_ne
+
+    描述：比较两个timestamp是否不相等。
+
+    参数：smalldatetime, smalldatetime
+
+    返回值类型：boolean
+
+- smalldatetime_out
+
+    描述：timestamp转换为外部形式。
+
+    参数：smalldatetime
+
+    返回值类型：cstring
+
+- smalldatetime_send
+
+    描述：timestamp转换为二进制格式。
+
+    参数：smalldatetime
+
+    返回值类型：bytea
+
+- smalldatetime_smaller
+
+    描述：返回较小的一个smalldatetime。
+
+    参数：smalldatetime, smalldatetime
+
+    返回值类型：smalldatetime
+
+- smalldatetime_to_abstime
+
+    描述：smalldatetime转换为abstime。
+
+    参数：smalldatetime
+
+    返回值类型：abstime
+
+- smalldatetime_to_time
+
+    描述：smalldatetime转换为time。
+
+    参数：smalldatetime
+
+    返回值类型：time without time zone
+
+- smalldatetime_to_timestamp
+
+    描述：smalldatetime转换为timestamp。
+
+    参数：smalldatetime
+
+    返回值类型：timestamp without time zone
+
+- smalldatetime_to_timestamptz
+
+    描述：smalldatetime转换为timestamptz。
+
+    参数：smalldatetime
+
+    返回值类型：timestamp with time zone
+
+- smalldatetime_to_varchar2
+
+    描述：smalldatetime转换为varchar2。
+
+    参数：smalldatetime
+
+    返回值类型：character varying
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+    >
+    > 获取当前时间有多种方式，请根据实际业务从场景选择合适的接口：
+    >
+    > 1. 以下接口按照当前事务的开始时刻返回值：
+    >
+    >    ```sql
+    >    CURRENT_DATE CURRENT_TIME CURRENT_TIMESTAMP CURRENT_TIME(precision) CURRENT_TIMESTAMP(precision) LOCALTIME LOCALTIMESTAMP LOCALTIME(precision) LOCALTIMESTAMP(precision)
+    >    ```
+    >
+    >    其中CURRENT_TIME和CURRENT_TIMESTAMP传递带有时区的值；LOCALTIME和LOCALTIMESTAMP传递的值不带时区。CURRENT_TIME、CURRENT_TIMESTAMP、LOCALTIME和 LOCALTIMESTAMP可以有选择地接受一个精度参数， 该精度导致结果的秒域被园整为指定小数位。如果没有精度参数，结果将被给予所能得到的全部精度。
+    >
+    >    因为这些函数全部都按照当前事务的开始时刻返回结果，所以它们的值在事务运行的整个期间内都不改变。 我们认为这是一个特性：目的是为了允许一个事务在“当前”时间上有一致的概念， 这样在同一个事务里的多个修改可以保持同样的时间戳。
+    >
+    > 2. 以下接口返回当前语句开始时间：
+    >
+    >    ```sql
+    >    transaction_timestamp() statement_timestamp() now()
+    >    ```
+    >
+    >    其中transaction_timestamp()等价于CURRENT_TIMESTAMP，但是其命名清楚地反映了它的返回值。statement_timestamp()返回当前语句的开始时刻（更准确的说是收到 客户端最后一条命令的时间）。statement_timestamp()和transaction_timestamp()在一个事务的第一条命令期间返回值相同，但是在随后的命令中却不一定相同。
+    >
+    >    now()等效于transaction_timestamp()。
+    >
+    > 3. 以下接口返回函数被调用时的真实当前时间：
+    >
+    >    ```sql
+    >    clock_timestamp() timeofday()
+    >    ```
+    >
+    >    clock_timestamp()返回真正的当前时间，因此它的值甚至在同一条 SQL 命令中都会变化。timeofday()和clock_timestamp()相似，timeofday()也返回真实的当前时间，但是它的结果是一个格式化的text串，而不是timestamp with time zone值。
+
+## TIMESTAMPDIFF
+
+- **TIMESTAMPDIFF(unit , timestamp_expr1, timestamp_expr2)**
+
+timestampdiff函数是计算两个日期时间之间(timestamp_expr2-timestamp_expr1)的差值，并以unit形式返回结果。timestamp_expr1，timestamp_expr2必须是一个timestamp、timestamptz、date类型的值表达式。unit表示的是两个日期差的单位。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+> 该函数仅在MogDB兼容MY类型时（即dbcompatibility = 'B'）有效，其他类型不支持该函数。
+
+- year
+
+  年份。
+
+  ```sql
+  mogdb=#  SELECT TIMESTAMPDIFF(YEAR, '2018-01-01', '2020-01-01');
+   timestamp_diff
+  ----------------
+                2
+  (1 row)
+  ```
+
+- quarter
+
+  季度。
+
+  ```sql
+  mogdb=#  SELECT TIMESTAMPDIFF(QUARTER, '2018-01-01', '2020-01-01');
+   timestamp_diff
+  ----------------
+                8
+  (1 row)
+  ```
+
+- month
+
+  月份。
+
+  ```sql
+  mogdb=#  SELECT TIMESTAMPDIFF(MONTH, '2018-01-01', '2020-01-01');
+   timestamp_diff
+  ----------------
+               24
+  (1 row)
+  ```
+
+- week
+
+  星期。
+
+  ```sql
+  mogdb=#  SELECT TIMESTAMPDIFF(WEEK, '2018-01-01', '2020-01-01');
+   timestamp_diff
+  ----------------
+              104
+  (1 row)
+  ```
+
+- day
+
+  天。
+
+  ```sql
+  mogdb=#  SELECT TIMESTAMPDIFF(DAY, '2018-01-01', '2020-01-01');
+   timestamp_diff
+  ----------------
+              730
+  (1 row)
+  ```
+
+- hour
+
+  小时。
+
+  ```sql
+  mogdb=#  SELECT TIMESTAMPDIFF(HOUR, '2020-01-01 10:10:10', '2020-01-01 11:11:11');
+   timestamp_diff
+  ----------------
+                1
+  (1 row)
+
+  ```
+
+- minute
+
+  分钟。
+
+  ```sql
+  mogdb=#  SELECT TIMESTAMPDIFF(MINUTE, '2020-01-01 10:10:10', '2020-01-01 11:11:11');
+   timestamp_diff
+  ----------------
+               61
+  (1 row)
+
+  ```
+
+- second
+
+  秒。
+
+  ```sql
+  mogdb=#  SELECT TIMESTAMPDIFF(SECOND, '2020-01-01 10:10:10', '2020-01-01 11:11:11');
+   timestamp_diff
+  ----------------
+             3661
+  (1 row)
+
+  ```
+
+- microseconds
+
+  秒域（包括小数部分）乘以1,000,000。
+
+  ```sql
+  mogdb=#  SELECT TIMESTAMPDIFF(MICROSECOND, '2020-01-01 10:10:10.000000', '2020-01-01 10:10:10.111111');
+   timestamp_diff
+  ----------------
+           111111
+  (1 row)
+
+  ```
+
+- timestamp_expr含有时区
+
+    ```sql
+    mogdb=# SELECT TIMESTAMPDIFF(HOUR,'2020-05-01 10:10:10-01','2020-05-01 10:10:10-03');
+     timestamp_diff
+    ----------------
+                  2
+    (1 row)
+    ```
+
+## EXTRACT
+
+- **EXTRACT(**_field_**FROM**source)
+
+  extract函数从日期或时间的数值里抽取子域，比如年、小时等。source必须是一个timestamp、time或interval类型的值表达式（类型为date的表达式转换为timestamp，因此也可以用）。field是一个标识符或者字符串，它指定从源数据中抽取的域。extract函数返回类型为double precision的数值。field的取值范围如下所示。
+
+- century
+
+  世纪。
+
+  第一个世纪从0001-01-01 00:00:00 AD开始。这个定义适用于所有使用阳历的国家。没有0世纪，直接从公元前1世纪到公元1世纪。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT EXTRACT(CENTURY FROM TIMESTAMP '2000-12-16 12:21:13');
+   date_part
+  -----------
+          20
+  (1 row)
+  ```
+
+- day
+
+  - 如果source为timestamp，表示月份里的日期（1-31）。
+
+    ```sql
+    mogdb=# SELECT EXTRACT(DAY FROM TIMESTAMP '2001-02-16 20:38:40');
+     date_part
+    -----------
+            16
+    (1 row)
+    ```
+
+  - 如果source为interval，表示天数。
+
+    ```sql
+    mogdb=# SELECT EXTRACT(DAY FROM INTERVAL '40 days 1 minute');
+     date_part
+    -----------
+            40
+    (1 row)
+    ```
+
+- decade
+
+  年份除以10。
+
+  ```sql
+  mogdb=# SELECT EXTRACT(DECADE FROM TIMESTAMP '2001-02-16 20:38:40');
+   date_part
+  -----------
+         200
+  (1 row)
+  ```
+
+- dow
+
+  每周的星期几，星期天（0）到星期六（6）。
+
+  ```sql
+  mogdb=# SELECT EXTRACT(DOW FROM TIMESTAMP '2001-02-16 20:38:40');
+   date_part
+  -----------
+           5
+  (1 row)
+  ```
+
+- doy
+
+  一年的第几天（1~365/366）。
+
+  ```sql
+  mogdb=# SELECT EXTRACT(DOY FROM TIMESTAMP '2001-02-16 20:38:40');
+   date_part
+  -----------
+          47
+  (1 row)
+  ```
+
+- epoch
+
+  - 如果source为timestamp with time zone，表示自1970-01-01 00:00:00-00 UTC以来的秒数（结果可能是负数）；
+
+    如果source为date和timestamp，表示自1970-01-01 00:00:00-00当地时间以来的秒数；
+
+    如果source为interval，表示时间间隔的总秒数。
+
+    ```sql
+    mogdb=# SELECT EXTRACT(EPOCH FROM TIMESTAMP WITH TIME ZONE '2001-02-16 20:38:40.12-08');
+      date_part
+    --------------
+     982384720.12
+    (1 row)
+    ```
+
+    ```sql
+    mogdb=# SELECT EXTRACT(EPOCH FROM INTERVAL '5 days 3 hours');
+     date_part
+    -----------
+        442800
+    (1 row)
+    ```
+
+  - 将epoch值转换为时间戳的方法。
+
+    ```sql
+    mogdb=# SELECT TIMESTAMP WITH TIME ZONE 'epoch' + 982384720.12 * INTERVAL '1 second' AS RESULT;
+              result
+    ---------------------------
+     2001-02-17 12:38:40.12+08
+    (1 row)
+    ```
+
+- hour
+
+  小时域（0-23）。
+
+  ```sql
+  mogdb=# SELECT EXTRACT(HOUR FROM TIMESTAMP '2001-02-16 20:38:40');
+   date_part
+  -----------
+          20
+  (1 row)
+  ```
+
+- isodow
+
+  一周的第几天（1-7）。
+
+  星期一为1，星期天为7。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+  > 除了星期天外，都与dow相同。
+
+  ```sql
+  mogdb=# SELECT EXTRACT(ISODOW FROM TIMESTAMP '2001-02-18 20:38:40');
+   date_part
+  -----------
+           7
+  (1 row)
+  ```
+
+- isoyear
+
+  日期中的ISO 8601标准年（不适用于间隔）。
+
+  每个带有星期一开始的周中包含1月4日的ISO年，所以在年初的1月或12月下旬的ISO年可能会不同于阳历的年。详细信息请参见后续的week描述。
+
+  ```sql
+  mogdb=# SELECT EXTRACT(ISOYEAR FROM DATE '2006-01-01');
+   date_part
+  -----------
+        2005
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT EXTRACT(ISOYEAR FROM DATE '2006-01-02');
+   date_part
+  -----------
+        2006
+  (1 row)
+  ```
+
+- microseconds
+
+  秒域（包括小数部分）乘以1,000,000。
+
+  ```sql
+  mogdb=# SELECT EXTRACT(MICROSECONDS FROM TIME '17:12:28.5');
+   date_part
+  -----------
+    28500000
+  (1 row)
+  ```
+
+- millennium
+
+  千年。
+
+  20世纪（19xx年）里面的年份在第二个千年里。第三个千年从2001年1月1日零时开始。
+
+  ```sql
+  mogdb=# SELECT EXTRACT(MILLENNIUM FROM TIMESTAMP '2001-02-16 20:38:40');
+   date_part
+  -----------
+           3
+  (1 row)
+  ```
+
+- milliseconds
+
+  秒域（包括小数部分）乘以1000。请注意它包括完整的秒。
+
+  ```sql
+  mogdb=# SELECT EXTRACT(MILLISECONDS FROM TIME '17:12:28.5');
+   date_part
+  -----------
+       28500
+  (1 row)
+  ```
+
+- minute
+
+  分钟域（0-59）。
+
+  ```sql
+  mogdb=# SELECT EXTRACT(MINUTE FROM TIMESTAMP '2001-02-16 20:38:40');
+   date_part
+  -----------
+          38
+  (1 row)
+  ```
+
+- month
+
+  如果source为timestamp，表示一年里的月份数（1-12）。
+
+  ```sql
+  mogdb=# SELECT EXTRACT(MONTH FROM TIMESTAMP '2001-02-16 20:38:40');
+   date_part
+  -----------
+           2
+  (1 row)
+  ```
+
+  如果source为interval，表示月的数目，然后对12取模（0-11）。
+
+  ```sql
+  mogdb=# SELECT EXTRACT(MONTH FROM INTERVAL '2 years 13 months');
+   date_part
+  -----------
+           1
+  (1 row)
+  ```
+
+- quarter
+
+  该天所在的该年的季度（1-4）。
+
+  ```sql
+  mogdb=# SELECT EXTRACT(QUARTER FROM TIMESTAMP '2001-02-16 20:38:40');
+   date_part
+  -----------
+           1
+  (1 row)
+  ```
+
+- second
+
+  秒域，包括小数部分（0-59）。
+
+  ```sql
+  mogdb=# SELECT EXTRACT(SECOND FROM TIME '17:12:28.5');
+   date_part
+  -----------
+        28.5
+  (1 row)
+  ```
+
+- timezone
+
+  与UTC的时区偏移量，单位为秒。正数对应UTC东边的时区，负数对应UTC西边的时区。
+
+- timezone_hour
+
+  时区偏移量的小时部分。
+
+- timezone_minute
+
+  时区偏移量的分钟部分。
+
+- week
+
+  该天在所在的年份里是第几周。ISO 8601定义一年的第一周包含该年的一月四日（ISO-8601 的周从星期一开始）。换句话说，一年的第一个星期四在第一周。
+
+  在ISO定义里，一月的头几天可能是前一年的第52或者第53周，十二月的后几天可能是下一年第一周。比如，2005-01-01是2004年的第53周，而2006-01-01是2005年的第52周，2012-12-31是2013年的第一周。建议isoyear字段和week一起使用以得到一致的结果。
+
+  ```sql
+  mogdb=# SELECT EXTRACT(WEEK FROM TIMESTAMP '2001-02-16 20:38:40');
+   date_part
+  -----------
+           7
+  (1 row)
+  ```
+
+- year
+
+  年份域。
+
+  ```sql
+  mogdb=# SELECT EXTRACT(YEAR FROM TIMESTAMP '2001-02-16 20:38:40');
+   date_part
+  -----------
+        2001
+  (1 row)
+  ```
+
+## date_part
+
+date_part函数是在传统的Ingres函数的基础上制作的（该函数等效于SQL标准函数extract）：
+
+- **date_part('field', source)**
+
+这里的field参数必须是一个字符串，而不是一个名称。有效的field与extract一样，详细信息请参见[EXTRACT](#EXTRACT)。
+
+示例：
+
+```sql
+mogdb=# SELECT date_part('day', TIMESTAMP '2001-02-16 20:38:40');
+ date_part
+-----------
+        16
+(1 row)
+mogdb=# SELECT date_part('hour', INTERVAL '4 hours 3 minutes');
+ date_part
+-----------
+         4
+(1 row)
+```
+
+表2显示了可以用于格式化日期和时间值的模版。
+
+**表 2** 用于日期/时间格式化的模式<a id="用于"> </a>
+
+| 类别             | 模式                                                         | 描述                                            |
+| ---------------- | ------------------------------------------------------------ | ----------------------------------------------- |
+| 小时             | HH                                                           | 一天的小时数（01-12）                           |
+| HH12             | 一天的小时数（01-12）                                        |                                                 |
+| HH24             | 一天的小时数（00-23）                                        |                                                 |
+| 分钟             | MI                                                           | 分钟（00-59）                                   |
+| 秒               | SS                                                           | 秒（00-59）                                     |
+| FF               | 微秒（000000-999999）                                        |                                                 |
+| SSSSS            | 午夜后的秒（0-86399）                                        |                                                 |
+| 上、下午         | AM或A.M.                                                     | 上午标识                                        |
+| PM或P.M.         | 下午标识                                                     |                                                 |
+| 年               | Y,YYY                                                        | 带逗号的年（4和更多位）                         |
+| SYYYY            | 公元前四位年                                                 |                                                 |
+| YYYY             | 年（4和更多位）                                              |                                                 |
+| YYY              | 年的后三位                                                   |                                                 |
+| YY               | 年的后两位                                                   |                                                 |
+| Y                | 年的最后一位                                                 |                                                 |
+| IYYY             | ISO年（4位或更多位）                                         |                                                 |
+| IYY              | ISO年的最后三位                                              |                                                 |
+| IY               | ISO年的最后两位                                              |                                                 |
+| I                | ISO年的最后一位                                              |                                                 |
+| RR               | 年的后两位（可在21世纪存储20世纪的年份）                     |                                                 |
+| RRRR             | 可接收4位年或两位年。若是两位，则和RR的返回值相同，若是四位，则和YYYY相同。 |                                                 |
+| BC或B.C.AD或A.D. | 纪元标识。BC（公元前），AD（公元后）。                       |                                                 |
+| 月               | MONTH                                                        | 全长大写月份名（空白填充为9字符）               |
+| MON              | 大写缩写月份名（3字符）                                      |                                                 |
+| MM               | 月份数（01-12）                                              |                                                 |
+| RM               | 罗马数字的月份（I-XII ；I=JAN）（大写）                      |                                                 |
+| 天               | DAY                                                          | 全长大写日期名（空白填充为9字符）               |
+| DY               | 缩写大写日期名（3字符）                                      |                                                 |
+| DDD              | 一年里的日（001-366）                                        |                                                 |
+| DD               | 一个月里的日（01-31）                                        |                                                 |
+| D                | 一周里的日（1-7 ；周日是 1）                                 |                                                 |
+| 周               | W                                                            | 一个月里的周数（1-5）（第一周从该月第一天开始） |
+| WW               | 一年里的周数（1-53）（第一周从该年的第一天开始）             |                                                 |
+| IW               | ISO一年里的周数（第一个星期四在第一周里）                    |                                                 |
+| 世纪             | CC                                                           | 世纪（2位）（21 世纪从 2001-01-01 开始）        |
+| 儒略日           | J                                                            | 儒略日（自公元前 4712 年 1 月 1 日来的天数）    |
+| 季度             | Q                                                            | 季度                                            |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+> 上表中RR计算年的规则如下：
+>
+> - 输入的两位年份在00~49之间：
+>   当前年份的后两位在00~49之间，返回值年份的前两位和当前年份的前两位相同；
+>   当前年份的后两位在50~99之间，返回值年份的前两位是当前年份的前两位加1。
+> - 输入的两位年份在50~99之间：
+>   当前年份的后两位在00~49之间，返回值年份的前两位是当前年份的前两位减1；
+> - 当前年份的后两位在50~99之间，返回值年份的前两位和当前年份的前两位相同。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/9-type-conversion-functions.md b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/9-type-conversion-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..779e3d8ed0e60c3bc09fb15bed44b6234392aab4
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/functions-and-operators/9-type-conversion-functions.md
@@ -0,0 +1,1418 @@
+---
+title: 类型转换函数
+summary: 类型转换函数
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 类型转换函数
+
+- cash_words(money)
+
+    描述：类型转换函数，将money转换成text。
+
+    示例：
+
+    ```sql
+    mogdb=# SELECT cash_words('1.23');
+                cash_words
+    -----------------------------------
+     One dollar and twenty three cents
+    (1 row)
+    ```
+
+- cast(x as y)
+
+  描述：类型转换函数，将x转换成y指定的类型。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT cast('22-oct-1997' as timestamp);
+        timestamp
+  ---------------------
+   1997-10-22 00:00:00
+  (1 row)
+  ```
+
+- hextoraw(raw)
+
+  描述：将一个十六进制构成的字符串转换为raw类型。
+
+  返回值类型：raw
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT hextoraw('7D');
+   hextoraw
+  ----------
+   7D
+  (1 row)
+  ```
+
+- numtoday(numeric)
+
+  描述：将数字类型的值转换为指定格式的时间戳。
+
+  返回值类型：timestamp
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT numtoday(2);
+   numtoday
+  ----------
+   2 days
+  (1 row)
+  ```
+
+- pg_systimestamp()
+
+  描述：获取系统时间戳。
+
+  返回值类型：timestamp with time zone
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT pg_systimestamp();
+          pg_systimestamp
+  -------------------------------
+   2015-10-14 11:21:28.317367+08
+  (1 row)
+  ```
+
+- rawtohex(string)
+
+  描述：将一个二进制构成的字符串转换为十六进制的字符串。
+
+  结果为输入字符的ACSII码，以十六进制表示。
+
+  返回值类型：varchar
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT rawtohex('1234567');
+      rawtohex
+  ----------------
+   31323334353637
+  (1 row)
+  ```
+
+- to_bigint(varchar)
+
+    描述：将字符类型转换为bigint类型。
+
+    返回值类型：bigint
+
+    示例：
+
+    ```sql
+    mogdb=# SELECT to_bigint('123364545554455');
+        to_bigint
+    ----------------
+     123364545554455
+    (1 row)
+    ```
+
+- to_char (datetime/interval [, fmt]) <a id = 'to_char'> </a>
+
+  描述：将一个DATE、TIMESTAMP、TIMESTAMP WITH TIME ZONE或者TIMESTAMP WITH LOCAL TIME ZONE类型的DATETIME或者INTERVAL值按照fmt指定的格式转换为VARCHAR类型。
+
+  - 可选参数fmt可以为以下几类：日期、时间、星期、季度和世纪。每类都可以有不同的模板，模板之间可以合理组合，常见的模板有：HH、MM、SS、YYYY、MM、DD。
+  - 模板可以有修饰词，常用的修饰词是FM，可以用来抑制前导的零或尾随的空白。
+  - 对于TIMESTAMP WITH TIME ZONE，可以在to_char使用TZH、TZM、TZD、TZR参数来输出时区信息。
+
+  返回值类型：varchar
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT to_char(current_timestamp,'HH12:MI:SS');
+   to_char
+  ----------
+   10:19:26
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT to_char(current_timestamp,'FMHH12:FMMI:FMSS');
+   to_char
+  ----------
+   10:19:46
+  (1 row)
+  ```
+
+  ```sql
+
+  mogdb=# select to_char(systimestamp, 'TZH');
+  to_char
+  ---------
+  +08
+  (1 row)
+
+  mogdb=# select to_char(systimestamp, 'TZM');
+  to_char
+  ---------
+  00
+  (1 row)
+
+  mogdb=# select to_char(systimestamp, 'TZD');
+  to_char
+  ---------
+  CST
+  (1 row)
+
+  mogdb=# select to_char(systimestamp, 'TZR');
+  to_char
+  ---------------
+  Asia/Shanghai
+  (1 row)
+  ```
+
+  **表 1** 日期/时间格式化的模版模式
+
+  | 模式                           | 描述                                                         |
+  | :----------------------------- | :----------------------------------------------------------- |
+  | `HH`                           | 一天的小时数 (01-12)                                         |
+  | `HH12`                         | 一天的小时数 (01-12)                                         |
+  | `HH24`                         | 一天的小时数 (00-23)                                         |
+  | `MI`                           | 分钟 (00-59)                                                 |
+  | `SS`                           | 秒 (00-59)                                                   |
+  | `MS`                           | 毫秒 (000-999)                                               |
+  | `US`                           | 微妙 (000000-999999)                                         |
+  | `SSSS`                         | 午夜之后的秒数(0-86399)                                      |
+  | `AM`，`am`，`PM`或`pm`         | 子午线 Metrics(无期限)                                       |
+  | `A.M.`，`a.m.`，`P.M.`或`p.m.` | 子午线 Metrics(带句号)                                       |
+  | `Y,YYY`                        | 年份(4 个或更多数字)，带逗号                                 |
+  | `YYYY`                         | 年(4 个或更多数字)                                           |
+  | `YYY`                          | 年份的后三位数                                               |
+  | `YY`                           | 年份的后两位数字                                             |
+  | `Y`                            | 年份的最后一位                                               |
+  | `IYYY`                         | ISO 8601 周编号年份(4 个或更多数字)                          |
+  | `IYY`                          | ISO 8601 周编号年份的后 3 位数字                             |
+  | `IY`                           | ISO 8601 周编号年份的后两位数字                              |
+  | `I`                            | ISO 8601 周编号年的最后一位数字                              |
+  | `BC`，`bc`，`AD`或`ad`         | 时代 Metrics(无期限)                                         |
+  | `B.C.`，`b.c.`，`A.D.`或`a.d.` | 时代 Metrics(带句号)                                         |
+  | `MONTH`                        | 完整的大写月份名称(空格填充为 9 个字符)                      |
+  | `Month`                        | 完整的大写月份名称(空白，最多 9 个字符)                      |
+  | `month`                        | 完整的小写月份名称(空格填充为 9 个字符)                      |
+  | `MON`                          | 大写月份名称的缩写(英语为 3 个字符，本地化长度有所不同)      |
+  | `Mon`                          | 缩写的大写月份名称(英文为 3 个字符，本地化长度有所不同)      |
+  | `mon`                          | 小写的月份缩写名称(英语为 3 个字符，本地化长度有所不同)      |
+  | `MM`                           | 月数(01-12)                                                  |
+  | `DAY`                          | 完整的大写日期名称(空白，最多 9 个字符)                      |
+  | `Day`                          | 完整的大写日期名称(空白，最多 9 个字符)                      |
+  | `day`                          | 完整的小写日期名称(空白，最多 9 个字符)                      |
+  | `DY`                           | 缩写的大写星期名称(英语为 3 个字符，本地化长度有所不同)      |
+  | `Dy`                           | 缩写的大写星期名称(英语为 3 个字符，本地化长度有所不同)      |
+  | `dy`                           | 缩写的小写星期名称(英语为 3 个字符，本地化长度有所不同)      |
+  | `DDD`                          | 一年中的哪一天(001-366)                                      |
+  | `IDDD`                         | ISO 8601 周编号年份的天(001-371；一年中的第 1 天是第一个 ISO 周的星期一) |
+  | `DD`                           | 每月的一天(01-31)                                            |
+  | `D`                            | 星期几，星期日(`1`)至星期六(`7`)                             |
+  | `ID`                           | ISO 8601 是星期几，星期一(`1`)至星期日(`7`)                  |
+  | `W`                            | 一个月中的第几周(1-5)(第一个星期从该月的第一天开始)          |
+  | `WW`                           | 年的周数(1-53)(第一周从一年的第一天开始)                     |
+  | `IW`                           | ISO 8601 周编号年的周号(01-53；该年的第一个星期四在第 1 周)  |
+  | `CC`                           | 世纪(2 位数字)(二十一世纪始于 2001-01-01)                    |
+  | `J`                            | 朱利安日(自公元前 4714 年 11 月 24 日午夜 UTC 以来的整数天)  |
+  | `Q`                            | quarter                                                      |
+  | `RM`                           | 大写罗马数字表示月份(I-XII； I =一月)                        |
+  | `rm`                           | 小写罗马数字表示月份(i-xii； i =一月)                        |
+  | `TZ`                           | 大写的时区缩写(仅在`to_char`中受支持)                        |
+  | `tz`                           | 小写的时区缩写(仅在`to_char`中受支持)                        |
+  | `TZH`                          | 时区的小时                                                   |
+  | `TZM`                          | 时区的分钟                                                   |
+  | `TZD`                          | 夏令时信息                                                   |
+  | `TZR`                          | 时区区域信息                                                 |
+
+- to_char(double precision/real, text)
+
+  描述：将浮点类型的值转换为指定格式的字符串。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT to_char(125.8::real, '999D99');
+   to_char
+  ---------
+    125.80
+  (1 row)
+  ```
+
+- to_char(numeric/smallint/integer/bigint/double precision/real[, fmt])
+
+  描述：将一个整型或者浮点类型的值转换为指定格式的字符串。
+
+  - 可选参数fmt可以为以下几类：十进制字符、"分组"符、正负号和货币符号，每类都可以有不同的模板，模板之间可以合理组合，常见的模板有：9、0、,（千分隔符）、.（小数点）。
+  - 模板可以有类似FM的修饰词，但FM不抑制由模板0指定而输出的0。
+  - 要将整型类型的值转换成对应16进制值的字符串，使用模板X或x。
+
+  返回值类型：varchar
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT to_char(1485,'9,999');
+   to_char
+  ---------
+    1,485
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT to_char( 1148.5,'9,999.999');
+    to_char
+  ------------
+    1,148.500
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT to_char(148.5,'990999.909');
+     to_char
+  -------------
+      0148.500
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT to_char(123,'XXX');
+   to_char
+  ---------
+     7B
+  (1 row)
+  ```
+
+- to_char(interval, text)
+
+  描述：将时间间隔类型的值转换为指定格式的字符串。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT to_char(interval '15h 2m 12s', 'HH24:MI:SS');
+   to_char
+  ----------
+   15:02:12
+  (1 row)
+  ```
+
+- to_char(int, text)
+
+  描述：将整数类型的值转换为指定格式的字符串。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT to_char(125, '999');
+   to_char
+  ---------
+    125
+  (1 row)
+  ```
+
+- to_char(numeric, text)
+
+  描述：将数字类型的值转换为指定格式的字符串。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT to_char(-125.8, '999D99S');
+   to_char
+  ---------
+   125.80-
+  (1 row)
+  ```
+
+- to_char (string)
+
+  描述：将CHAR、VARCHAR、VARCHAR2、CLOB类型转换为VARCHAR类型。
+
+  如使用该函数对CLOB类型进行转换，且待转换CLOB类型的值超出目标类型的范围，则返回错误。
+
+  返回值类型：varchar
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT to_char('01110');
+   to_char
+  ---------
+   01110
+  (1 row)
+  ```
+
+- to_char(timestamp, text)
+
+  描述：将时间戳类型的值转换为指定格式的字符串。
+
+  返回值类型：text
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT to_char(current_timestamp, 'HH12:MI:SS');
+   to_char
+  ----------
+   10:55:59
+  (1 row)
+  ```
+
+- to_clob(char/nchar/varchar/varchar2/nvarchar2/text/raw)
+
+  描述：将RAW类型或者文本字符集类型CHAR、NCHAR、VARCHAR、VARCHAR2、NVARCHAR2、TEXT转成CLOB类型。
+
+  返回值类型：clob
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT to_clob('ABCDEF'::RAW(10));
+   to_clob
+  ---------
+   ABCDEF
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT to_clob('hello111'::CHAR(15));
+   to_clob
+  ----------
+   hello111
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT to_clob('gauss123'::NCHAR(10));
+   to_clob
+  ----------
+   gauss123
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT to_clob('gauss234'::VARCHAR(10));
+   to_clob
+  ----------
+   gauss234
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT to_clob('gauss345'::VARCHAR2(10));
+   to_clob
+  ----------
+   gauss345
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT to_clob('gauss456'::NVARCHAR2(10));
+   to_clob
+  ----------
+   gauss456
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT to_clob('World222!'::TEXT);
+    to_clob
+  -----------
+   World222!
+  (1 row)
+  ```
+
+- to_date(text)
+
+  描述：将文本类型的值转换为指定格式的时间戳。目前只支持两类格式。
+
+  - 格式一：无分隔符日期，如20150814，需要包括完整的年月日。
+
+  - 格式二：带分隔符日期，如2014-08-14，分隔符可以是单个任意非数字字符。
+
+  返回值类型：timestamp without time zone
+
+  示例：
+
+  ```sql
+    mogdb=# SELECT to_date('2015-08-14');
+           to_date
+    ---------------------
+     2015-08-14 00:00:00
+    (1 row)
+  ```
+
+- to_date(text, text)
+
+  描述：将字符串类型的值转换为指定格式的日期。
+
+  返回值类型：timestamp without time zone
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT to_date('05 Dec 2000', 'DD Mon YYYY');
+         to_date
+  ---------------------
+   2000-12-05 00:00:00
+  (1 row)
+  ```
+
+- to_number ( expr [, fmt])
+
+  描述：将expr按指定格式转换为一个NUMBER类型的值。
+
+  类型转换格式请参考[表2](#数值格式化)。
+
+  转换十六进制字符串为十进制数字时，最多支持16个字节的十六进制字符串转换为无符号数。
+
+  转换十六进制字符串为十进制数字时，格式字符串中不允许出现除'x'或'X'以外的其他字符，否则报错。
+
+  返回值类型：number
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT to_number('12,454.8-', '99G999D9S');
+   to_number
+  -----------
+    -12454.8
+  (1 row)
+  ```
+
+- to_number(text, text)
+
+  描述：将字符串类型的值转换为指定格式的数字。
+
+  返回值类型：numeric
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT to_number('12,454.8-', '99G999D9S');
+   to_number
+  -----------
+    -12454.8
+  (1 row)
+  ```
+
+- to_timestamp(double precision)
+
+  描述：把UNIX纪元转换成时间戳。
+
+  返回值类型：timestamp with time zone
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT to_timestamp(1284352323);
+        to_timestamp
+  ------------------------
+   2010-09-13 12:32:03+08
+  (1 row)
+  ```
+
+- to_timestamp(string [,fmt])
+
+  描述：将字符串string按fmt指定的格式转换成时间戳类型的值。不指定fmt时，按参数nls_timestamp_format所指定的格式转换。
+
+  MogDB的to_timestamp中，
+
+  - 如果输入的年份YYYY=0，系统报错。
+  - 如果输入的年份YYYY&lt;0，在fmt中指定SYYYY，则正确输出公元前绝对值n的年份。
+
+  fmt中出现的字符必须与日期/时间格式化的模式相匹配，否则报错。
+
+  返回值类型：timestamp without time zone
+
+  示例：
+
+  ```sql
+  mogdb=# SHOW nls_timestamp_format;
+      nls_timestamp_format
+  ----------------------------
+   DD-Mon-YYYY HH:MI:SS.FF AM
+  (1 row)
+
+  mogdb=# SELECT to_timestamp('12-sep-2014');
+      to_timestamp
+  ---------------------
+   2014-09-12 00:00:00
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT to_timestamp('12-Sep-10 14:10:10.123000','DD-Mon-YY HH24:MI:SS.FF');
+        to_timestamp
+  -------------------------
+   2010-09-12 14:10:10.123
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT to_timestamp('-1','SYYYY');
+        to_timestamp
+  ------------------------
+   0001-01-01 00:00:00 BC
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT to_timestamp('98','RR');
+      to_timestamp
+  ---------------------
+   1998-01-01 00:00:00
+  (1 row)
+  ```
+
+  ```sql
+  mogdb=# SELECT to_timestamp('01','RR');
+      to_timestamp
+  ---------------------
+   2001-01-01 00:00:00
+  (1 row)
+  ```
+
+- to_timestamp(text, text)
+
+  描述：将字符串类型的值转换为指定格式的时间戳。
+
+  返回值类型：timestamp
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT to_timestamp('05 Dec 2000', 'DD Mon YYYY');
+      to_timestamp
+  ---------------------
+   2000-12-05 00:00:00
+  (1 row)
+  ```
+
+**表 2** 数值格式化的模版模式<a id="数值格式化"> </a>
+
+| 模式      | 描述                                  |
+| --------- | ------------------------------------- |
+| 9         | 带有指定数值位数的值                  |
+| 0         | 带前导零的值                          |
+| .（句点） | 小数点                                |
+| ,（逗号） | 分组（千）分隔符                      |
+| PR        | 尖括号内负值                          |
+| S         | 带符号的数值（使用区域设置）          |
+| L         | 货币符号（使用区域设置）              |
+| D         | 小数点（使用区域设置）                |
+| G         | 分组分隔符（使用区域设置）            |
+| MI        | 在指明的位置的负号（如果数字 &lt; 0） |
+| PL        | 在指明的位置的正号（如果数字 &gt; 0） |
+| SG        | 在指明的位置的正/负号                 |
+| RN        | 罗马数字（输入在 1 和 3999 之间）     |
+| TH或th    | 序数后缀                              |
+| V         | 移动指定位（小数）                    |
+
+- abstime_text
+
+    描述：将abstime类型转为text类型输出。
+
+    参数：abstime
+
+    返回值类型：text
+
+- abstime_to_smalldatetime
+
+    描述：将abstime类型转为smalldatatime类型。
+
+    参数：abstime
+
+    返回值类型：smalldatetime
+
+- bigint_tid
+
+    描述：将bigint转为tid。
+
+    参数：bigint
+
+    返回值类型：tid
+
+- bool_int1
+
+    描述：将bool转为int1。
+
+    参数：boolean
+
+    返回值类型：tinyint
+
+- bool_int2
+
+    描述：将bool转为int2。
+
+    参数：boolean
+
+    返回值类型：smallint
+
+- bool_int8
+
+    描述：将bool转为int8。
+
+    参数：boolean
+
+    返回值类型：bigint
+
+- bpchar_date
+
+    描述：将字符串转为日期。
+
+    参数：character
+
+    返回值类型：date
+
+- bpchar_float4
+
+    描述：将字符串转为float4。
+
+    参数：character
+
+    返回值类型：real
+
+- bpchar_float8
+
+    描述：将字符串转为float8。
+
+    参数：character
+
+    返回值类型：double precision
+
+- bpchar_int4
+
+    描述：将字符串转为int4。
+
+    参数：character
+
+    返回值类型：integer
+
+- bpchar_int8
+
+    描述：将字符串转为int8。
+
+    参数：character
+
+    返回值类型：bigint
+
+- bpchar_numeric
+
+    描述：将字符串转为numeric。
+
+    参数：character
+
+    返回值类型：numeric
+
+- bpchar_timestamp
+
+    描述：将字符串转为时间戳。
+
+    参数：character
+
+    返回值类型：timestamp without time zone
+
+- bpchar_to_smalldatetime
+
+    描述：将字符串转为smalldatetime。
+
+    参数：character
+
+    返回值类型：smalldatetime
+
+- cupointer_bigint
+
+    描述：将列存CU指针类型转为bigint类型。
+
+    参数：text
+
+    返回值类型：bigint
+
+- date_bpchar
+
+    描述：将date类型转换为bpchar类型。
+
+    参数：date
+
+    返回值类型：character
+
+- date_text
+
+    描述：将date类型转换为text类型。
+
+    参数：date
+
+    返回值类型：text
+
+- date_varchar
+
+    描述：将date类型转换为varchar类型。
+
+    参数：date
+
+    返回值类型：character varying
+
+- f4toi1
+
+    描述：把float4类型强转为uint8类型。
+
+    参数：real
+
+    返回值类型：tinyint
+
+- f8toi1
+
+    描述：把float8类型强转为uint8类型。
+
+    参数：double precision
+
+    返回值类型：tinyint
+
+- float4_bpchar
+
+    描述：float4转换为bpchar。
+
+    参数：real
+
+    返回值类型：character
+
+- float4_text
+
+    描述：float4转换为text。
+
+    参数：real
+
+    返回值类型：text
+
+- float4_varchar
+
+    描述：float4转换为varchar。
+
+    参数：real
+
+    返回值类型：character varying
+
+- float8_bpchar
+
+    描述：float4转换为bpchar。
+
+    参数：double precision
+
+    返回值类型：character
+
+- float8_interval
+
+    描述：float4转换为interval。
+
+    参数：double precision
+
+    返回值类型：interval
+
+- float8_text
+
+    描述：float8转换为text。
+
+    参数：double precision
+
+    返回值类型：text
+
+- float8_varchar
+
+    描述：float8转换为varchar。
+
+    参数：double precision
+
+    返回值类型：character varying
+
+- i1tof4
+
+    描述：uint8转换为float4。
+
+    参数：tinyint
+
+    返回值类型：real
+
+- i1tof8
+
+    描述：uint8转换为float8。
+
+    参数：tinyint
+
+    返回值类型：double precision
+
+- i1toi2
+
+    描述：uint8转换为int16。
+
+    参数：tinyint
+
+    返回值类型：smallint
+
+- i1toi4
+
+    描述：uint8转换为int32。
+
+    参数：tinyint
+
+    返回值类型：integer
+
+- i1toi8
+
+    描述：uint8转换为int64。
+
+    参数：tinyint
+
+    返回值类型：bigint
+
+- i2toi1
+
+    描述：int16转换为uint8。
+
+    参数：smallint
+
+    返回值类型：tinyint
+
+- i4toi1
+
+    描述：int32转换为uint8。
+
+    参数：integer
+
+    返回值类型：tinyint
+
+- i8toi1
+
+    描述：int64转换为uint8。
+
+    参数：bigint
+
+    返回值类型：tinyint
+
+- int1_avg_accum
+
+    描述：将第二个uint8类型参数，加入到第一个参数中，一个参数为bigint类型数组。
+
+    参数：bigint[], tinyint
+
+    返回值类型：bigint[]
+
+- int1_bool
+
+    描述：uint8转换为bool。
+
+    参数：tinyint
+
+    返回值类型：boolean
+
+- int1_bpchar
+
+    描述：uint8转换为bpchar。
+
+    参数：tinyint
+
+    返回值类型：character
+
+- int1_mul_cash
+
+    描述：返回一个int8类型参数和一个cash类型参数的乘积，返回值为cash类型。
+
+    参数：tinyint, money
+
+    返回值类型：money
+
+- int1_numeric
+
+    描述：uint8转换为numeric。
+
+    参数：tinyint
+
+    返回值类型：numeric
+
+- int1_nvarchar2
+
+    描述：uint8转换为nvarchar2。
+
+    参数：tinyint
+
+    返回值类型：nvarchar2
+
+- int1_text
+
+    描述：uint8转换为text。
+
+    参数：tinyint
+
+    返回值类型：text
+
+- int1_varchar
+
+    描述：uint8转换为varchar。
+
+    参数：tinyint
+
+    返回值类型：character varying
+
+- int1in
+
+    描述：字符串转化为无符号一字节整数。
+
+    参数：cstring
+
+    返回值类型：tinyint
+
+- int1out
+
+    描述：无符号一字节整数转化为字符串。
+
+    参数：tinyint
+
+    返回值类型：cstring
+
+- int1up
+
+    描述：输入整数转化为无符号一字节整数。
+
+    参数：tinyint
+
+    返回值类型：tinyint
+
+- int2_bool
+
+    描述：将有符号二字节整数转化为bool型。
+
+    参数：smallint
+
+    返回值类型：boolean
+
+- int2_bpchar
+
+    描述：将有符号二字节整数转化为BpChar。
+
+    参数：smallint
+
+    返回值类型：character
+
+- int2_text
+
+    描述：有符号二字节整数转化为text类型。
+
+    参数：smallint
+
+    返回值类型：text
+
+- int2_varchar
+
+    描述：有符号二字节整数转化为varchar类型。
+
+    参数：smallint
+
+    返回值类型：character varying
+
+- int8_text
+
+    描述：有符号八字节整数转化为text类型。
+
+    参数：bigint
+
+    返回值类型：text
+
+- int8_varchar
+
+    描述：有符号八字节整数转化为varchar。
+
+    参数：bigint
+
+    返回值类型：character varying
+
+- intervaltonum
+
+    描述：将内部数据类型日期转化为numeric类型。
+
+    参数：interval
+
+    返回值类型：numeric
+
+- numeric_bpchar
+
+    描述：numeric转化为bpchar。
+
+    参数：numeric
+
+    返回值类型：character
+
+- numeric_int1
+
+    描述：numeric转化为有符号1字节整数。
+
+    参数：numeric
+
+    返回值类型：tinyint
+
+- numeric_text
+
+    描述：numeric转化为text。
+
+    参数：numeric
+
+    返回值类型：text
+
+- numeric_varchar
+
+    描述：numeric转化为varchar。
+
+    参数：numeric
+
+    返回值类型：character varying
+
+- nvarchar2in
+
+    描述：将c字符串转化为varchar。
+
+    参数：cstring, oid, integer
+
+    返回值类型：nvarchar2
+
+- nvarchar2out
+
+    描述：将text转化为c字符串。
+
+    参数：nvarchar2
+
+    返回值类型：cstring
+
+- nvarchar2send
+
+    描述：将varchar转化为二进制。
+
+    参数：nvarchar2
+
+    返回值类型：bytea
+
+- oidvectorin_extend
+
+    描述：将字符串转化为oidvector。
+
+    参数：cstring
+
+    返回值类型：oidvector_extend
+
+- oidvectorout_extend
+
+    描述：将oidvector转化为字符串。
+
+    参数：oidvector_extend
+
+    返回值类型：cstring
+
+- oidvectorsend_extend
+
+    描述：将oidvector转化为字符串。
+
+    参数：oidvector_extend
+
+    返回值类型：bytea
+
+- reltime_text
+
+    描述：reltime转换为text。
+
+    参数：reltime
+
+    返回值类型：text
+
+- text_date
+
+    描述：text类型转换为date类型。
+
+    参数：text
+
+    返回值类型：date
+
+- text_float4
+
+    描述：text类型转换为float4类型。
+
+    参数：text
+
+    返回值类型：real
+
+- text_float8
+
+    描述：text类型转换为float8类型。
+
+    参数：text
+
+    返回值类型：double precision
+
+- text_int1
+
+    描述：text类型转换为int1类型。
+
+    参数：text
+
+    返回值类型：tinyint
+
+- text_int2
+
+    描述：text类型转换为int2类型。
+
+    参数：text
+
+    返回值类型：smallint
+
+- text_int4
+
+    描述：text类型转换为int4类型。
+
+    参数：text
+
+    返回值类型：integer
+
+- text_int8
+
+    描述：text类型转换为int8类型。
+
+    参数：text
+
+    返回值类型：bigint
+
+- text_numeric
+
+    描述：text类型转换为numeric类型。
+
+    参数：text
+
+    返回值类型：numeric
+
+- text_timestamp
+
+    描述：text类型转换为timestamp类型。
+
+    参数：text
+
+    返回值类型：timestamp without time zone
+
+- time_text
+
+    描述：time类型转换为text类型。
+
+    参数：time without time zone
+
+    返回值类型：text
+
+- timestamp_text
+
+    描述：timestamp类型转换为text类型。
+
+    参数：timestamp without time zone
+
+    返回值类型：text
+
+- timestamp_to_smalldatetime
+
+    描述：timestamp类型转换为smalldatetime类型。
+
+    参数：timestamp without time zone
+
+    返回值类型：smalldatetime
+
+- timestamp_varchar
+
+    描述：timestamp类型转换为varchar类型。
+
+    参数：timestamp without time zone
+
+    返回值类型：character varying
+
+- timestamptz_to_smalldatetime
+
+    描述：timestamptz类型转换为smalldatetime。
+
+    参数：timestamp with time zone
+
+    返回值类型：smalldatetime
+
+- timestampzone_text
+
+    描述：timestampzone类型转换为text类型。
+
+    参数：timestamp with time zone
+
+    返回值类型：text
+
+- timetz_text
+
+    描述：timetz类型转换为text类型。
+
+    参数：time with time zone
+
+    返回值类型：text
+
+- to_integer
+
+    描述：转换为integer类型。
+
+    参数：character varying
+
+    返回值类型：integer
+
+- to_interval
+
+    描述：转换为interval类型。
+
+    参数：character varying
+
+    返回值类型：interval
+
+- to_numeric
+
+    描述：转换为numeric类型。
+
+    参数：character varying
+
+    返回值类型：numeric
+
+- to_nvarchar2
+
+    描述：转换为nvarchar2类型。
+
+    参数：numeric
+
+    返回值类型：nvarchar2
+
+- to_text
+
+    描述：转换为text类型。
+
+    参数：smallint
+
+    返回值类型：text
+
+- to_ts
+
+    描述：转换为ts类型。
+
+    参数：character varying
+
+    返回值类型：timestamp without time zone
+
+- to_varchar2
+
+    描述：转换为varchar2类型。
+
+    参数：timestamp without time zone
+
+    返回值类型：character varying
+
+- varchar_date
+
+    描述：varchar类型转换为date。
+
+    参数：character varying
+
+    返回值类型：date
+
+- varchar_float4
+
+    描述：varchar类型转换为float4。
+
+    参数：character varying
+
+    返回值类型：real
+
+- varchar_float8
+
+    描述：varchar类型转换为float8。
+
+    参数：character varying
+
+    返回值类型：double precision
+
+- varchar_int4
+
+    描述：varchar类型转换为int4。
+
+    参数：character varying
+
+    返回值类型：integer
+
+- varchar_int8
+
+    描述：varchar类型转换为int8。
+
+    参数：character varying
+
+    返回值类型：bigint
+
+- varchar_numeric
+
+    描述：varchar类型转换为numeric。
+
+    参数：character varying
+
+    返回值类型：numeric
+
+- varchar_timestamp
+
+    描述：varchar类型转换为timestamp。
+
+    参数：character varying
+
+    返回值类型：timestamp without time zone
+
+- varchar2_to_smlldatetime
+
+    描述：varchar2类型转换为smlldatetime。
+
+    参数：character varying
+
+    返回值类型：smalldatetime
+
+- xidout4
+
+    描述：xid输出为4字节数字。
+
+    参数：xid32
+
+    返回值类型：cstring
+
+- xidsend4
+
+    描述：xid转换为二进制格式。
+
+    参数：xid32
+
+    返回值类型：bytea
+
+## 编码类型转换
+
+- convert_to_nocase(text, text)
+
+    描述：将字符串转换为指定的编码类型。
+
+    返回值类型：bytea
+
+    示例：
+
+    ```sql
+    mogdb=# SELECT convert_to_nocase('12345', 'GBK');
+     convert_to_nocase
+    -------------------
+     \x3132333435
+    (1 row)
+    ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/1-guc-parameter-usage.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/1-guc-parameter-usage.md
new file mode 100644
index 0000000000000000000000000000000000000000..309324a52c7339ce297772fc528da5d2d3f502fa
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/1-guc-parameter-usage.md
@@ -0,0 +1,18 @@
+---
+title: GUC使用说明
+summary: GUC使用说明
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# GUC使用说明
+
+数据库提供了许多运行参数，配置这些参数可以影响数据库系统的行为。在修改这些参数时请确保用户理解了这些参数对数据库的影响，否则可能会导致无法预料的结果。
+
+**注意事项**
+
+- 参数中如果取值范围为字符串，此字符串应遵循操作系统的路径和文件名命名规则。
+
+- 取值范围最大值为INT_MAX的参数，此选项最大值跟所在的操作系统有关。
+
+- 取值范围最大值为DBL_MAX的参数，此选项最大值跟所在的操作系统有关。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/1-logging-destination.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/1-logging-destination.md
new file mode 100644
index 0000000000000000000000000000000000000000..cab9bdbfc9b5be670ed9f698daf68d87b97884de
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/1-logging-destination.md
@@ -0,0 +1,175 @@
+---
+title: 记录日志的位置
+summary: 记录日志的位置
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 记录日志的位置
+
+## log_destination
+
+**参数说明**: MogDB支持多种方法记录服务器日志，log_destination的取值为一个逗号分隔开的列表（如log_destination="stderr,csvlog"）。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串
+
+有效值为stderr、csvlog、syslog。
+
+- 取值为stderr，表示日志打印到屏幕。
+
+- 取值为csvlog，表示日志的输出格式为"逗号分隔值"即CSV （Comma Separated Value）格式。使用csvlog记录日志的前提是将[logging_collector](#logging_collector)设置为on，请参见**使用CSV格式写日志**。
+
+- 取值为syslog，表示通过操作系统的syslog记录日志。MogDB使用syslog的LOCAL0 ～ LOCAL7记录日志，请参见[syslog_facility](#syslog_facility)。使用syslog记录日志需在操作系统后台服务配置文件中添加代码:
+
+  ```
+  local0.*  /var/log/omm
+  ```
+
+**默认值**: stderr
+
+## logging_collector
+
+**参数说明**: 控制开启后端日志收集进程logger进行日志收集。该进程捕获发送到stderr或csvlog的日志消息并写入日志文件。
+
+这种记录日志的方法比将日志记录到syslog更加有效，因为某些类型的消息在syslog的输出中无法显示。例如动态链接库加载失败消息和脚本（例如archive_command）产生的错误消息。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> 将服务器日志发送到stderr时可以不使用logging_collector参数，此时日志消息会被发送到服务器的stderr指向的空间。这种方法的缺点是日志回滚困难，只适用于较小的日志容量。
+
+**取值范围:**布尔型
+
+- on表示开启日志收集功能。
+- off表示关闭日志收集功能。
+
+**默认值**: on
+
+## log_directory
+
+**参数说明**: logging_collector设置为on时，log_directory决定存放服务器日志文件的目录。它可以是绝对路径，或者是相对路径（相对于数据目录的路径）。log_directory支持动态修改，可以通过gs_guc reload实现。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+>
+> - 当配置文件中log_directory的值为非法路径时，会导致MogDB无法重新启动。
+> - 通过gs_guc reload动态修改log_directory时，当指定路径为合法路径时，日志输出到新的路径下。当指定路径为非法路径时，日志输出到上一次合法的日志输出路径下而不影响数据库正常运行。此时即使指定的log_directory的值非法，也会写入到配置文件中。
+> - 在沙箱环境，路径中不可以包含/var/chroot，例如log的绝对路径是/var/chroot/var/lib/log/Ruby/pg_log/cn_log，则只需要设置为/var/lib/log/Ruby/pg_log/cn_log。
+>
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+>
+> - 合法路径: 用户对此路径有读写权限
+> - 非法路径: 用户对此路径无读写权限
+
+**取值范围:**字符串
+
+**默认值**: 安装时指定。
+
+## log_filename
+
+**参数说明**: logging_collector设置为on时，log_filename决定服务器运行日志文件的名称。通常日志文件名是按照strftime模式生成，因此可以用系统时间定义日志文件名，用%转义字符实现。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+>
+> - 建议使用%转义字符定义日志文件名称，否则难以对日志文件进行有效的管理。
+> - 当log_destination设为csvlog时，系统会生成附加了时间戳的日志文件名，文件格式为csv格式，例如"server_log.1093827753.csv"。
+
+**取值范围:**字符串
+
+**默认值**: postgresql-%Y-%m-%d_%H%M%S.log
+
+## log_file_mode
+
+**参数说明**: [logging_collector](#logging_collector)设置为on时，log_file_mode设置服务器日志文件的权限。通常log_file_mode的取值是能够被chmod和umask系统调用接受的数字。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+>
+> - 使用此选项前请设置log_directory，将日志存储到数据目录之外的地方。
+> - 因日志文件可能含有敏感数据，故不能将其设为对外可读。
+
+**取值范围:**整型，0000～0777（8进制计数，转化为十进制 0 ~ 511）。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+>
+> - 0600表示只允许服务器管理员读写日志文件。
+> - 0640表示允许管理员所在用户组成员只能读日志文件。
+
+**默认值**: 0600
+
+## log_truncate_on_rotation
+
+**参数说明**: logging_collector设置为on时，log_truncate_on_rotation设置日志消息的写入方式。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+示例如下:
+
+假设日志需要保留7天，每天生成一个日志文件，日志文件名设置为server_log.Mon、server_log.Tue等。第二周的周二生成的日志消息会覆盖写入到server_log.Tue。设置方法: 将log_filename设置为server_log.%a ，log_truncate_on_rotation设置为on，log_rotation_age设置为1440，即日志有效时间为1天。
+
+**取值范围:** 布尔型
+
+- on表示MogDB以覆盖写入的方式写服务器日志消息。
+- off表示MogDB将日志消息附加到同名的现有日志文件上。
+
+**默认值**: off
+
+## log_rotation_age
+
+**参数说明**: logging_collector设置为on时，log_rotation_age决定创建一个新日志文件的时间间隔。当现在的时间减去上次创建一个服务器日志的时间超过了log_rotation_age的值时，将生成一个新的日志文件。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，0 ~ 35791394，单位为min。其中0表示关闭基于时间的新日志文件的创建。
+
+**默认值**: 1440(min)
+
+## log_rotation_size
+
+**参数说明**: logging_collector设置为on时，log_rotation_size决定服务器日志文件的最大容量。当日志消息的总量超过日志文件容量时，服务器将生成一个新的日志文件。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，0 ~ INT_MAX / 1024，单位为kB。
+
+0表示关闭基于容量的新日志文件的创建。
+
+建议该值大小设置级别至少为MB级,利于日志文件的及时划分。
+
+**默认值**: 20MB
+
+## syslog_facility
+
+**参数说明**: log_destination设置为syslog时，syslog_facility配置使用syslog记录日志的"设备"。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**枚举类型，有效值有local0、local1、local2、local3、local4、local5、local6、local7。
+
+**默认值**: local0
+
+## syslog_ident
+
+**参数说明**: [log_destination](#log_destination)设置为syslog时，syslog_ident设置在syslog日志中MogDB日志消息的标识。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串
+
+**默认值**: postgres
+
+## event_source
+
+**参数说明**: 该参数仅在windows环境下生效, MogDB暂不支持。log_destination设置为eventlog时，event_source设置在日志中MogDB日志消息的标识。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串
+
+**默认值**: PostgreSQL
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/2-logging-time.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/2-logging-time.md
new file mode 100644
index 0000000000000000000000000000000000000000..6d627746763eaf93875d20c4c1e1bd2e225489a9
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/2-logging-time.md
@@ -0,0 +1,115 @@
+---
+title: 记录日志的时间
+summary: 记录日志的时间
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 记录日志的时间
+
+## client_min_messages
+
+**参数说明**: 控制发送到客户端的消息级别。每个级别都包含排在它后面的所有级别中的信息。级别越低，发送给客户端的消息就越少。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> 当client_min_messages和[log_min_messages](#log_min_messages)取相同值时，其值所代表的级别不同。
+
+**取值范围:**枚举类型，有效值有debug、debug5、debug4、debug3、debug2、debug1、info、log、notice、warning、error、fatal、panic。参数的详细信息请参见表**信息严重程度分类**。在实际设置过程中，如果设置的级别大于error，为fatal或panic，系统会默认将级别转为error。
+
+**默认值**: notice
+
+## log_min_messages
+
+**参数说明**: 控制写到服务器日志文件中的消息级别。每个级别都包含排在它后面的所有级别中的信息。级别越低，服务器运行日志中记录的消息就越少。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> 当[client_min_messages](#client_min_messages)和log_min_messages取相同值log时所代表的消息级别不同。
+
+**取值范围:**枚举类型，有效值有debug、debug5、debug4、debug3、debug2、debug1、info、log、notice、warning、error、fatal、panic。参数的详细信息请参见表**信息严重程度分类**。
+
+**默认值**: warning
+
+## log_min_error_statement
+
+**参数说明**: 控制在服务器日志中记录错误的SQL语句。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**枚举类型，有效值有debug、debug5、debug4、debug3、debug2、debug1、info、log、notice、warning、error、fatal、panic。参数的详细信息请参见表**信息严重程度分类**。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+>
+> - 设置为error，表示导致错误、日志消息、致命错误、panic的语句都将被记录。
+> - 设置为panic，表示关闭此特性。
+
+**默认值**: error
+
+## log_min_duration_statement
+
+**参数说明**: 当某条语句的持续时间大于或者等于特定的毫秒数时，log_min_duration_statement参数用于控制记录每条完成语句的持续时间。
+
+设置log_min_duration_statement可以很方便地跟踪需要优化的查询语句。对于使用扩展查询协议的客户端，语法分析、绑定、执行每一步所花时间被独立记录。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> 当此选项与log_statement同时使用时，已经被log_statement记录的语句文本不会被重复记录。在没有使用syslog情况下，推荐使用log_line_prefix记录PID或会话ID，方便将当前语句消息连接到最后的持续时间消息。
+
+**取值范围:**整型，-1 ~ INT_MAX，单位为毫秒。
+
+- 设置为250，所有运行时间不短于250ms的SQL语句都会被记录。
+- 设置为0，输出所有语句的持续时间。
+- 设置为-1，关闭此功能。
+
+**默认值**: 30min
+
+## backtrace_min_messages
+
+**参数说明**: 控制当产生该设置参数级别相等或更高级别的信息时，会打印函数的堆栈信息到服务器日志文件中。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> 该参数作为客户现场问题定位手段使用，且由于频繁的打印函数栈会对系统的开销及稳定性有一定的影响，因此如果需要进行问题定位时，建议避免将backtrace_min_messages的值设置为fatal及panic以外的级别。
+
+**取值范围:**枚举类型
+
+有效值有debug、debug5、debug4、debug3、debug2、debug1、info、log、notice、warning、error、fatal、panic。参数的详细信息请参见表**信息严重程度分类**。
+
+**默认值**: panic
+
+[表1](#信息严重程度分类)解释MogDB中使用的消息安全级别。当日志输出到syslog或者eventlog（仅windows环境下, MogDB版本不涉及该参数）时，MogDB进行如表中的转换。
+
+**表 1** 信息严重程度分类<a id="信息严重程度分类"> </a>
+
+| 信息严重程度类型 | 详细说明                   | 系统日志 | 事件日志    |
+| :--------------- | :---------------------- | :------- | :---------- |
+| debug[1-5]       | 报告详细调试信息。                                           | DEBUG    | INFORMATION |
+| log              | 报告对数据库管理员有用的信息，比如检查点操作统计信息。       | INFO     | INFORMATION |
+| info             | 报告用户可能需求的信息，比如在VACUUM VERBOSE过程中的信息。   | INFO     | INFORMATION |
+| notice           | 报告可能对用户有帮助的信息， 比如，长标识符的截断， 作为主键一部分创建的索引等。 | NOTICE   | INFORMATION |
+| warning          | 报告警告信息，比如在事务块范围之外的COMMIT。                 | NOTICE   | WARNING     |
+| error            | 报告导致当前命令退出的错误。                                 | WARNING  | ERROR       |
+| fatal            | 报告导致当前会话终止的原因。                                 | ERR      | ERROR       |
+| panic            | 报告导致整个数据库被关闭的原因。                             | CRIT     | ERROR       |
+
+## plog_merge_age
+
+**参数说明**: 该参数用于控制性能日志数据输出的周期。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> 该参数以毫秒为单位的，建议在使用过程中设置值为1000的整数倍，即设置值以秒为最小单位。该参数所控制的性能日志文件以prf为扩展名，文件放置在$GAUSSLOG/gs_profile/目录下面，其中node_name是由postgres.conf文件中的pgxc_node_name的值，不建议外部使用该参数。
+
+**取值范围:**0~2147483647，单位为毫秒（ms）。
+
+当设置为0时，当前会话不再输出性能日志数据。当设置为非0时，当前会话按照指定的时间周期进行输出性能日志数据。
+
+该参数设置得越小，输出的日志数据越多，对性能的负面影响越大。
+
+**默认值**: 0
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/3-logging-content.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/3-logging-content.md
new file mode 100644
index 0000000000000000000000000000000000000000..b83bc75bb1dd8de07931483afb6980a7c2aaedeb
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/3-logging-content.md
@@ -0,0 +1,348 @@
+---
+title: 记录日志的内容
+summary: 记录日志的内容
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 记录日志的内容
+
+## debug_print_parse
+
+**参数说明**: 用于控制打印解析树结果。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示开启打印结果的功能。
+- off表示关闭打印结果的功能。
+
+**默认值**: off
+
+## debug_print_rewritten
+
+**参数说明**: 用于控制打印查询重写结果。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示开启打印结果的功能。
+- off表示关闭打印结果的功能。
+
+**默认值**: off
+
+## debug_print_plan
+
+**参数说明**: 用于设置是否将查询的执行计划打印到日志中。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示开启打印结果的功能。
+- off表示关闭打印结果的功能。
+
+**默认值**: off
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+
+- 只有当日志的级别为log及以上时，debug_print_parse、debug_print_rewritten和debug_print_plan的调试信息才会输出。当这些选项打开时，调试信息只会记录在服务器的日志中，而不会输出到客户端的日志中。通过设置client_min_messages和log_min_messages参数可以改变日志级别。
+
+- 在打开debug_print_plan开关的情况下需尽量避免调用gs_encrypt_aes128及gs_decrypt_aes128函数，避免敏感参数信息在日志中泄露的风险。同时建议用户在打开debug_print_plan开关生成的日志中对gs_encrypt_aes128及gs_decrypt_aes128函数的参数信息进行过滤后再提供给外部维护人员定位，日志使用完成后请及时删除。
+
+## debug_pretty_print
+
+**参数说明**: 设置此选项对debug_print_parse、debug_print_rewritten和debug_print_plan产生的日志进行缩进，会生成易读但比设置为off时更长的输出格式。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示进行缩进。
+- off表示不进行缩进。
+
+**默认值**: on
+
+## log_checkpoints
+
+**参数说明**: 控制在服务器日志中记录检查点和重启点的信息。打开此参数时，服务器日志消息包含涉及检查点和重启点的统计量，其中包含需要写的缓存区的数量及写入所花费的时间等。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示打开此参数时，服务器日志消息包含涉及检查点和重启点的统计量。
+- off表示关闭此参数时，服务器日志消息包含不涉及检查点和重启点的统计量。
+
+**默认值**: off
+
+## log_connections
+
+**参数说明**: 控制记录客户端的连接请求信息。
+
+该参数属于BACKEND类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> 有些客户端程序（例如gsql），在判断是否需要口令的时候会尝试连接两次，因此日志消息中重复的"connection receive"（收到连接请求）并不意味着一定是问题。
+
+**取值范围:**布尔型
+
+- on表示记录信息。
+- off表示不记录信息。
+
+**默认值**: off
+
+## log_disconnections
+
+**参数说明**: 控制记录客户端结束连接信息。
+
+该参数属于BACKEND类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示记录信息。
+- off表示不记录信息。
+
+**默认值**: off
+
+## log_duration
+
+**参数说明**: 控制记录每个已完成SQL语句的执行时间。对使用扩展查询协议的客户端、会记录语法分析、绑定和执行每一步所花费的时间。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- 设置为off，该选项与log_min_duration_statement的不同之处在于log_min_duration_statement强制记录查询文本。
+- 设置为on并且log_min_duration_statement大于零，记录所有持续时间，但是仅记录超过阈值的语句。这可用于在高负载情况下搜集统计信息。
+
+**默认值**: on
+
+## log_error_verbosity
+
+**参数说明**: 控制服务器日志中每条记录的消息写入的详细度。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**枚举类型
+
+- terse输出不包括DETAIL、HINT、QUERY及CONTEXT错误信息的记录。
+- verbose输出包括SQLSTATE错误代码、源代码文件名、函数名及产生错误所在的行号。
+- default输出包括DETAIL、HINT、QUERY及CONTEXT错误信息的记录，不包括SQLSTATE错误代码 、源代码文件名、函数名及产生错误所在的行号。
+
+**默认值**: default
+
+## log_hostname
+
+**参数说明**: 选项关闭状态下，连接消息日志只显示正在连接主机的IP地址。打开此选项同时可以记录主机名。由于解析主机名可能需要一定的时间，可能影响数据库的性能。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示可以同时记录主机名。
+- off表示不可以同时记录主机名。
+
+**默认值**: on
+
+## log_line_prefix
+
+**参数说明**: 控制每条日志信息的前缀格式。日志前缀类似于printf风格的字符串，在日志的每行开头输出。用以%为开头的"转义字符"代替[表1](#转义字符表)中的状态信息。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**表 1** 转义字符表<a id="转义字符表"> </a>
+
+| <span style="white-space:nowrap;">转义字符</span> | 效果
+| -----------------------| ------------------------------- |
+| %a                                                       | 应用程序名称。                                               |
+| %u                                                       | 用户名。                                                     |
+| %d                                                       | 数据库名。                                                   |
+| %r                                                       | 远端主机名或者IP地址以及远端端口，在不启动log_hostname时显示IP地址及远端端口。 |
+| %h                                                       | 远端主机名或者IP地址，在不启动log_hostname时只显示IP地址。   |
+| %p                                                       | 线程ID。                                                     |
+| %t                                                       | 时间戳（没有毫秒）。                                         |
+| %m                                                       | 带毫秒的时间戳。                                             |
+| %n                                                       | 表示指定错误从哪个节点上报的。                               |
+| %i                                                       | 命令标签: 会话当前执行的命令类型。                           |
+| %e                                                       | SQLSTATE错误码。                                             |
+| %c                                                       | 会话ID，详见说明。                                           |
+| %l                                                       | 每个会话或线程的日志编号，从1开始。                          |
+| %s                                                       | 进程启动时间。                                               |
+| %v                                                       | 虚拟事务ID（backendID/ localXID）。                          |
+| %x                                                       | 事务ID（0表示没有分配事务ID）。                              |
+| %q                                                       | 不产生任何输出。如果当前线程是后端线程，忽略这个转义序列，继续处理后面的转义序列；如果当前线程不是后端线程，忽略这个转义序列和它后面的所有转义序列。 |
+| %S                                                       | 会话ID。                                                     |
+| %%                                                       | 字符% 。                                                     |
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+转义字符%c打印一个独一无二的会话ID，由两个4字节的十六进制数组成，通过字符"."分开。这两个十六进制数分别表示进程的启动时间及进程编号，所以%c也可以看作是保存打印这些名目的途径的空间。比如，从pg_stat_activity中产生会话ID，可以用下面的查询:
+
+```sql
+SELECT to_hex(EXTRACT(EPOCH FROM backend_start)::integer) || '.' ||
+       to_hex(pid)
+FROM pg_stat_activity;
+```
+
+- 当log_line_prefix设置为非空值时，请将其最后一个字符作为一个独立的段，以此来直观地与后续的日志进行区分，也可以使用一个标点符号。
+- Syslog生成自己的时间戳及进程ID信息，所以当登录日志时，不需要包含这些转义字符。
+
+**取值范围:**字符串
+
+**默认值**: %m %c %d %p %a %x %n %e
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+
+%m %c %d %p %a %x %n %e表示在日志开头附加会话开始时间戳，会话ID，数据库名，线程ID，应用程序名，事务ID，报错节点，SQLSTATE错误码。
+
+## log_lock_waits
+
+**参数说明**: 当一个会话的等待获得一个锁的时间超过deadlock_timeout的值时，此选项控制在数据库日志中记录此消息。这对于决定锁等待是否会产生一个坏的行为是非常有用的。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示记录此信息。
+- off表示不记录此信息。
+
+**默认值**: off
+
+## log_statement
+
+**参数说明**: 控制记录SQL语句。对于使用扩展查询协议的客户端，记录接收到执行消息的事件和绑定参数的值（内置单引号要双写）。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+
+即使log_statement设置为all，包含简单语法错误的语句也不会被记录，因为仅在完成基本的语法分析并确定了语句类型之后才记录日志。在使用扩展查询协议的情况下，在执行阶段之前（语法分析或规划阶段）同样不会记录。将log_min_error_statement设为ERROR或更低才能记录这些语句。
+
+**取值范围:**枚举类型
+
+- none表示不记录语句。
+- ddl表示记录所有的数据定义语句，比如CREATE、ALTER和DROP语句。
+- mod表示记录所有DDL语句，还包括数据修改语句INSERT、UPDATE、DELETE、TRUNCATE和COPY FROM 。
+- all表示记录所有语句，PREPARE、EXECUTE和EXPLAIN ANALYZE语句也同样被记录。
+
+**默认值**: none
+
+## log_temp_files
+
+**参数说明**: 控制记录临时文件的删除信息。临时文件可以用来排序、哈希及临时查询结果。当一个临时文件被删除时，将会产生一条日志消息。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，最小值为-1，最大值2147483647，单位KB。
+
+- 正整数表示只记录比log_temp_files设定值大的临时文件的删除信息。
+- 值0 表示记录所有的临时文件的删除信息。
+- 值-1 表示不记录任何临时文件的删除信息。
+
+**默认值**: -1
+
+## log_timezone
+
+**参数说明**: 设置服务器写日志文件时使用的时区。与TimeZone不同，这个值是数据库范围的，针对所有连接到本数据库的会话生效。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串
+
+**默认值**: PRC
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+
+gs_initdb进行相应系统环境设置时会对默认值进行修改。
+
+## logging_module
+
+**参数说明**: 用于设置或者显示模块日志在服务端的可输出性。该参数属于会话级参数，不建议通过gs_guc工具来设置。
+
+该参数属于USERSET类型参数，设置请参考表[GUC参数分类](30-appendix)中对应设置的方法进行设置。
+
+**取值范围:**字符串
+
+**默认值**: 所有模块日志在服务端是不输出的，可由SHOW logging_module查看
+
+```sql
+ALL,on(),off(DFS,GUC,ORC,SLRU,MEM_CTL,AUTOVAC,CACHE,ADIO,SSL,TBLSPC,WLM,EXECUTOR,OPFUSION,VEC_EXECUTOR,LLVM,OPT,OPT_REWRITE,OPT_JOIN,OPT_AGG,OPT_SUBPLAN,OPT_SETOP,OPT_SKEW,UDF,COOP_ANALYZE,WLMCP,ACCELERATE,,PLANHINT,SNAPSHOT,XACT,HANDLE,CLOG,EC,REMOTE,CN_RETRY,PLSQL,TEXTSEARCH,SEQ,REDO,FUNCTION,PARSER,INSTR,INCRE_CKPT,DBL_WRT,RTO,HEARTBEAT
+```
+
+**设置方法**: 首先，可以通过SHOW logging_module来查看哪些模块是支持可控制的。例如，查询输出结果为:
+
+```sql
+mogdb=# show logging_module;
+logging_module
+----------------------------------------------------
+ALL,on(),off(DFS,GUC,ORC,SLRU,MEM_CTL,AUTOVAC,CACHE,ADIO,SSL,TBLSPC,WLM,EXECUTOR,VEC_EXECUTOR,LLVM,OPT,OPT_REWRITE,OPT_JOIN,OPT_AGG,OPT_SUBPLAN,OPT_SETOP,OPT_SKEW,UDF,COOP_ANALYZE,WLMCP,ACCELERATE,T,PLANHINT,SNAPSHOT,XACT,HANDLE,CLOG,EC,REMOTE,CN_RETRY,PLSQL,TEXTSEARCH,SEQ,REDO,FUNCTION,PARSER,INSTR,INCRE_CKPT,DBL_WRT,RTO,HEARTBEAT)
+(1 row)
+```
+
+支持可控制的模块使用大写来标识，特殊标识ALL用于对所有模块日志进行设置。可以使用on/off来控制模块日志的输出。设置SSL模块日志为可输出，使用如下命令:
+
+```sql
+mogdb=# set logging_module='on(SSL)';
+SET
+mogdb=# show logging_module;
+logging_module
+---------------------------------------------------------------------
+ALL,on(SSL),off(DFS,GUC,ORC,SLRU,MEM_CTL,AUTOVAC,CACHE,ADIO,TBLSPC,WLM,EXECUTOR,VEC_EXECUTOR,LLVM,OPT,OPT_REWRITE,OPT_JOIN,OPT_AGG,OPT_SUBPLAN,OPT_SETOP,OPT_SKEW,UDF,COOP_ANALYZE,WLMCP,ACCELERATE,,PLANHINT,SNAPSHOT,XACT,HANDLE,CLOG,EC,REMOTE,CN_RETRY,PLSQL,TEXTSEARCH,SEQ,REDO,FUNCTION,PARSER,INSTR,INCRE_CKPT,DBL_WRT,RTO,HEARTBEAT,COMM_IPC,COMM_PARAM)
+(1 row)
+```
+
+可以看到模块SSL的日志输出被打开。
+
+ALL标识是相当于一个快捷操作，即对所有模块的日志可输出进行开启或关闭。
+
+```sql
+mogdb=# set logging_module='off(ALL)';
+SET
+mogdb=# show logging_module;
+logging_module
+-------------------------------------
+LL,on(),off(DFS,GUC,ORC,SLRU,MEM_CTL,AUTOVAC,CACHE,ADIO,SSL,TBLSPC,WLM,EXECUTOR,VEC_EXECUTOR,LLVM,OPT,OPT_REWRITE,OPT_JOIN,OPT_AGG,OPT_SUBPLAN,OPT_SETOP,OPT_SKEW,UDF,COOP_ANALYZE,WLMCP,ACCELERATE,PLANHINT,SNAPSHOT,XACT,HANDLE,CLOG,EC,REMOTE,CN_RETRY,PLSQL,TEXTSEARCH,SEQ,REDO,FUNCTION,PARSER,INSTR,INCRE_CKPT,DBL_WRT,RTO,HEARTBEAT)
+(1 row)
+
+mogdb=# set logging_module='on(ALL)';
+SET
+mogdb=# show logging_module;
+logging_module
+-----------------------------------------
+ALL,on(DFS,GUC,ORC,SLRU,MEM_CTL,AUTOVAC,CACHE,ADIO,SSL,TBLSPC,WLM,EXECUTOR,VEC_EXECUTOR,LLVM,OPT,OPT_REWRITE,OPT_JOIN,OPT_AGG,OPT_SUBPLAN,OPT_SETOP,OPT_SKEW,UDF,COOP_ANALYZE,WLMCP,ACCELERATE,PLANHINT,SNAPSHOT,XACT,HANDLE,CLOG,EC,REMOTE,CN_RETRY,PLSQL,TEXTSEARCH,SEQ,REDO,FUNCTION,PARSER,INSTR,INCRE_CKPT,DBL_WRT,RTO,HEARTBEAT),off()
+(1 row)
+```
+
+**依赖关系**: 该参数依赖于log_min_messages参数的设置
+
+## opfusion_debug_mode
+
+**参数说明**: 用于调试简单查询是否进行查询优化。设置成log级别可以在数据库节点的执行计划中看到没有查询优化的具体原因。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**枚举类型
+
+- off表示不打开该功能。
+- log表示打开该功能，可以在数据库节点的执行计划中看到没有查询优化的具体原因。
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+
+提供在log中显示语句没有查询优化的具体原因，需要将参数设置成log级别，log_min_messages设置成debug4级别，logging_module设置'on(OPFUSION)'，注意log内容可能会比较多，尽可能在调优期间执行少量作业使用。
+
+**默认值**: off
+
+## enable_debug_vacuum
+
+**参数说明**: 允许输出一些与VACUUM相关的日志，便于定位VACUUM相关问题。开发人员专用，不建议普通用户使用。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on/true表示开启此日志开关。
+- off/false表示关闭此日志开关。
+
+**默认值**: off
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/4-using-csv-log-output.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/4-using-csv-log-output.md
new file mode 100644
index 0000000000000000000000000000000000000000..b769ac086bcf93e87820c8fadc26feb178dc4e67
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/10-error-reporting-and-logging/4-using-csv-log-output.md
@@ -0,0 +1,88 @@
+---
+title: 使用CSV格式写日志
+summary: 使用CSV格式写日志
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 使用CSV格式写日志
+
+**前提条件**
+
+- log_destination的值设置为csvlog。
+- logging_collector的值设置为on。
+
+**csvlog定义**
+
+以"逗号分隔值" 即CSV（Comma Separated Value）的形式发出日志。
+
+以下是简单的用来存储CSV形式日志输出的表定义:
+
+```sql
+CREATE TABLE gaussdb_log
+(
+log_time timestamp(3) with time zone,
+node_name text,
+user_name text,
+database_name text,
+process_id bigint,
+connection_from text,
+"session_id" text,
+session_line_num bigint,
+command_tag text,
+session_start_time timestamp with time zone,
+virtual_transaction_id text,
+transaction_id bigint,
+query_id bigint,
+module text,
+error_severity text,
+sql_state_code text,
+message text,
+detail text,
+hint text,
+internal_query text,
+internal_query_pos integer,
+context text,
+query text,
+query_pos integer,
+location text,
+application_name text
+);
+```
+
+详细说明请参见[表1](#csvlog)。
+
+**表 1** csvlog字段含义表<a id="csvlog"> </a>
+
+| 字段名                 | 字段含义         | 字段名             | 字段含义                                                     |
+| :--------------------- | :--------------- | :----------------- | :----------------------------------------------------------- |
+| log_time               | 毫秒级的时间戳   | module             | 日志所属模块                                                 |
+| node_name              | 节点名称         | error_severity     | ERRORSTATE代码                                               |
+| user_name              | 用户名           | sql_state_code     | SQLSTATE代码                                                 |
+| database_name          | 数据库名         | message            | 错误消息                                                     |
+| process_id             | 进程ID           | detail             | 详细错误消息                                                 |
+| connection_from        | 客户主机: 端口号 | hint               | 提示                                                         |
+| session_id             | 会话ID           | internal_query     | 内部查询（查询那些导致错误的信息，如果有的话）               |
+| session_line_num       | 每个会话的行数   | internal_query_pos | 内部查询指针                                                 |
+| command_tag            | 命令标签         | context            | 环境                                                         |
+| session_start_time     | 会话开始时间     | query              | 错误发生位置的字符统计                                       |
+| virtual_transaction_id | 常规事务         | query_pos          | 错误发生位置指针                                             |
+| transaction_id         | 事务ID           | location           | 在MogDB源代码中错误的位置（如果log_error_verbosity的值设为verbose ） |
+| query_id               | 查询ID           | application_name   | 应用名称                                                     |
+
+使用COPY FROM命令将日志文件导入这个表:
+
+```shell
+COPY gaussdb_log FROM '/opt/data/pg_log/logfile.csv' WITH csv;
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+> 此处的日志名"logfile.csv"要换成实际生成的日志的名称。
+
+**简化输入**
+
+简化输入到CSV日志文件，可以通过如下操作:
+
+- 设置log_filename和log_rotation_age，为日志文件提供一个一致的、可预测的命名方案。通过日志文件名，预测一个独立的日志文件完成并进入准备导入状态的时间。
+- 将log_rotation_size设为0来终止基于尺寸的日志回滚，因为基于尺寸的日志回滚让预测日志文件名变得非常的困难。
+- 将log_truncate_on_rotation设为on以便区分在同一日志文件中旧的日志数据和新的日志数据。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/11-alarm-detection.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/11-alarm-detection.md
new file mode 100644
index 0000000000000000000000000000000000000000..7a97fa12ac22408404116499f87ab048d3e507b6
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/11-alarm-detection.md
@@ -0,0 +1,73 @@
+---
+title: 告警检测
+summary: 告警检测
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 告警检测
+
+在MogDB运行的过程中，会对数据库中的错误场景进行检测，便于用户及早感知到MogDB的错误。
+
+## enable_alarm
+
+**参数说明**: 允许打开告警检测线程，检测数据库中可能的错误场景。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示允许打开告警检测线程。
+- off表示不允许打开告警检测线程。
+
+**默认值**: on
+
+## connection_alarm_rate
+
+**参数说明**: 允许和数据库连接的最大并发连接数的比率限制。数据库连接的最大并发连接数为max_connections* connection_alarm_rate。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**浮点型，0.0~1.0
+
+**默认值**: 0.9
+
+## alarm_report_interval
+
+**参数说明**: 指定告警上报的时间间隔。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，单位为秒。
+
+**默认值**: 10
+
+## alarm_component
+
+**参数说明**: 在对告警做上报时，会进行告警抑制，即同一个实例的同一个告警项在alarm_report_interval（默认值为10s）内不做重复上报。在这种情况下设置用于处理告警内容的告警组件的位置。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串
+
+**默认值**: /opt/huawei/snas/bin/snas_cm_cmd
+
+## table_skewness_warning_threshold
+
+**参数说明**：设置用于表倾斜告警的阈值。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：浮点型，0～1
+
+**默认值**：1
+
+## table_skewness_warning_rows
+
+**参数说明**：设置用于表倾斜告警的行数。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：整型，0～INT_MAX
+
+**默认值**：100000
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/12-statistics-during-the-database-running/1-query-and-index-statistics-collector.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/12-statistics-during-the-database-running/1-query-and-index-statistics-collector.md
new file mode 100644
index 0000000000000000000000000000000000000000..8eb2c847f0b96e0254214398e171cec482fd52d2
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/12-statistics-during-the-database-running/1-query-and-index-statistics-collector.md
@@ -0,0 +1,139 @@
+---
+title: 查询和索引统计收集器
+summary: 查询和索引统计收集器
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 查询和索引统计收集器
+
+查询和索引统计收集器负责收集数据库系统运行中的统计数据，如在一个表和索引上进行了多少次插入与更新操作、磁盘块的数量和元组的数量、每个表上最近一次执行清理和分析操作的时间等。可以通过查询系统视图pg_stats和pg_statistic查看统计数据。下面的参数设置服务器范围内的统计收集特性。
+
+## track_activities
+
+**参数说明**: 控制收集每个会话中当前正在执行命令的统计数据。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示开启收集功能。
+- off表示关闭收集功能。
+
+**默认值**: on
+
+## track_counts
+
+**参数说明**: 控制收集数据库活动的统计数据。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示开启收集功能。
+- off表示关闭收集功能。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+>
+> 在AutoVacuum自动清理进程中选择清理的数据库时，需要数据库的统计数据，故默认值设为on。
+
+**默认值**: on
+
+## track_io_timing
+
+**参数说明**: 控制收集数据库I/O调用时序的统计数据。I/O时序统计数据可以在pg_stat_database中查询。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示开启收集功能，开启时，收集器会在重复地去查询当前时间的操作系统，这可能会引起某些平台的重大开销，故默认值设置为off。
+- off表示关闭收集功能。
+
+**默认值**: off
+
+## track_functions
+
+**参数说明**: 控制收集函数的调用次数和调用耗时的统计数据。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+>
+> 当SQL语言函数设置为调用查询的"内联"函数时，不管是否设置此选项，这些SQL语言函数无法被追踪到。
+
+**取值范围:**枚举类型
+
+- pl表示只追踪过程语言函数。
+- all表示追踪SQL语言函数。
+- none表示关闭函数追踪功能。
+
+**默认值**: none
+
+## track_activity_query_size
+
+**参数说明**: 设置用于跟踪每一个活动会话的当前正在执行命令的字节数。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，100～102400
+
+**默认值**: 1024
+
+## stats_temp_directory
+
+**参数说明**: 设置存储临时统计数据的目录。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+>
+> 将其设置为一个基于RAM的文件系统目录会减少实际的I/O开销并可以提升其性能。
+
+**取值范围:**字符串
+
+**默认值**: pg_stat_tmp
+
+## track_thread_wait_status_interval
+
+**参数说明**: 用来定期收集thread状态信息的时间间隔。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**0～1天，单位为min。
+
+**默认值**: 30min
+
+## enable_save_datachanged_timestamp
+
+**参数说明**: 确定是否收集insert/update/delete, exchange/truncate/drop partition操作对表数据改动的时间。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示允许收集相关操作对表数据改动的时间。
+- off表示禁止收集相关操作对表数据改动的时间。
+
+**默认值**: on
+
+## track_sql_count
+
+**参数说明**: 控制对每个会话中当前正在执行的SELECT、INSERT、UPDATE、DELETE、MERGE INTO语句进行计数的统计数据。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示开启计数功能。
+- off表示关闭计数功能。
+
+**默认值: on**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+>
+> - track_sql_count参数受track_activities约束。
+> - track_activities开启而track_sql_count关闭时，如果查询了gs_sql_count视图，日志中将会有WARNING提示track_sql_count是关闭的。
+> - track_activities和track_sql_count同时关闭，那么此时日志中将会有两条WARNING，分别提示track_activities是关闭的和track_sql_count是关闭的。
+> - track_activities关闭而track_sql_count开启，此时日志中将仅有WARNING提示track_activities是关闭。
+> - 当参数关闭时，查询视图的结果为0行。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/12-statistics-during-the-database-running/2-performance-statistics.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/12-statistics-during-the-database-running/2-performance-statistics.md
new file mode 100644
index 0000000000000000000000000000000000000000..69ad235210244b2864f59602519a3a4d385fb0d3
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/12-statistics-during-the-database-running/2-performance-statistics.md
@@ -0,0 +1,35 @@
+---
+title: 性能统计
+summary: 性能统计
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 性能统计
+
+在数据库运行过程中，会涉及到锁的访问、磁盘IO操作、无效消息的处理，这些操作都可能是数据库的性能瓶颈，通过MogDB提供的性能统计方法，可以方便定位性能问题。
+
+**输出性能统计日志**
+
+**参数说明**: 对每条查询，以下4个选项控制在服务器日志里记录相应模块的性能统计数据，具体含义如下:
+
+- log_parser_stats控制在服务器日志里记录解析器的性能统计数据。
+- log_planner_stats控制在服务器日志里记录查询优化器的性能统计数据。
+- log_executor_stats控制在服务器日志里记录执行器的性能统计数据。
+- log_statement_stats控制在服务器日志里记录整个语句的性能统计数据。
+
+这些参数只能辅助管理员进行粗略分析，类似Linux中的操作系统工具getrusage() 。
+
+这些参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+>
+> - log_statement_stats记录总的语句统计数据，而其他的只记录针对每个模块的统计数据。
+> - log_statement_stats不能和其他任何针对每个模块统计的选项一起打开。
+
+**取值范围:**布尔型
+
+- on表示开启记录性能统计数据的功能。
+- off表示关闭记录性能统计数据的功能。
+
+**默认值: off**
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/13-load-management.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/13-load-management.md
new file mode 100644
index 0000000000000000000000000000000000000000..08282f5d43307aa769bdf817a4a613d93188e4b7
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/13-load-management.md
@@ -0,0 +1,407 @@
+---
+title: 负载管理
+summary: 负载管理
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 负载管理
+
+未对数据库资源做控制时，容易出现并发任务抢占资源导致操作系统过载甚至最终崩溃。操作系统过载时，其响应用户任务的速度会变慢甚至无响应；操作系统崩溃时，整个系统将无法对用户提供任何服务。MogDB的负载管理功能能够基于可用资源的多少均衡数据库的负载，以避免数据库系统过载。
+
+## use_workload_manager
+
+**参数说明**: 是否开启资源管理功能。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**： 布尔型
+
+- on表示打开资源管理。
+
+- off表示关闭资源管理。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  >
+  > - 当使用表[GUC参数设置方式](30-appendix)中的方式二来修改参数值时，新参数值只能对更改操作执行后启动的线程生效。此外，对于后台线程以及线程复用执行的新作业，该参数值的改动不会生效。如果希望这类线程即时识别参数变化，可以使用kill session或重启节点的方式来实现。
+  > - use_workload_manager参数由off变为on状态后，不会统计off时的存储资源。如果需要统计off时用户使用的存储资源，请在数据库中执行以下命令：
+  >
+  > ```sql
+  > select gs_wlm_readjust_user_space(0);
+  > ```
+
+**默认值**: off
+
+## cgroup_name
+
+**参数说明**: 设置当前使用的Cgroups的名称或者调整当前group下排队的优先级。
+
+即如果先设置cgroup_name，再设置session_respool，那么session_respool关联的控制组起作用，如果再切换cgroup_name，那么新切换的cgroup_name起作用。
+
+切换cgroup_name的过程中如果指定到Workload控制组级别，数据库不对级别进行验证。级别的范围只要在1-10范围内都可以。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中方式三的方法进行设置。
+
+建议尽量不要混合使用cgroup_name和session_respool。
+
+**取值范围**： 字符串
+
+**默认值**: InvalidGroup
+
+## cpu_collect_timer
+
+**参数说明**: 设置语句执行时在数据库节点上收集CPU时间的周期。
+
+数据库管理员需根据系统资源（如CPU资源、IO资源和内存资源）情况，调整此数值大小，使得系统支持较合适的收集周期，太小会影响执行效率，太大会影响异常处理的精确度。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**： 整型，1~INT_MAX， 单位为秒。
+
+**默认值**: 30
+
+## memory_tracking_mode
+
+**参数说明**: 设置记录内存信息的模式。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：
+
+- none，不启动内存统计功能。
+- peak：表示统计query级内存peak值，此数值计入数据库日志，也可以由explain analyze输出。
+- normal，仅做内存实时统计，不生成文件。
+- executor，生成统计文件，包含执行层使用过的所有已分配内存的上下文信息。
+- fullexec，生成文件包含执行层申请过的所有内存上下文信息。
+
+**默认值**: none
+
+## memory_detail_tracking
+
+**参数说明**: 设置需要的线程内分配内存上下文的顺序号以及当前线程所在query的plannodeid。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**： 字符型
+
+**默认值**: 空
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+>
+> 该参数不允许用户进行设置，建议保持默认值。
+
+## enable_resource_track
+
+**参数说明**: 是否开启资源实时监控功能。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**： 布尔型
+
+- on表示打开资源监控。
+- off表示关闭资源监控。
+
+**默认值**: on
+
+## enable_resource_record
+
+**参数说明**: 是否开启资源监控记录归档功能。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**： 布尔型
+
+- on表示开启资源监控记录归档功能。
+- off表示关闭资源监控记录归档功能。
+
+**默认值**: off
+
+## enable_logical_io_statistics
+
+**参数说明**: 设置是否开启资源监控逻辑IO统计功能。开启时，对于PG_TOTAL_USER_RESOURCE_INFO视图中的read_kbytes、write_kbytes、read_counts、write_counts、read_speed和write_speed字段，会统计对应用户的逻辑读写字节数、次数以及速率。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**： 布尔型
+
+- on表示开启资源监控逻辑IO统计功能。
+- off表示关闭资源监控逻辑IO统计功能。
+
+**默认值**: on
+
+## enable_user_metric_persistent
+
+**参数说明**：设置是否开启用户历史资源监控转存功能。开启时，对于PG_TOTAL_USER_RESOURCE_INFO视图中数据，会定期采样保存到GS_WLM_USER_RESOURCE_HISTORY系统表中。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**： 布尔型
+
+● on表示开启用户历史资源监控转存功能。
+
+● off表示关闭用户历史资源监控转存功能。
+
+**默认值**： on
+
+## user_metric_retention_time
+
+**参数说明**：设置用户历史资源监控数据的保存天数。该参数仅在 enable_user_metric_persistent为on时有效。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中的方法一和方法二进行设置。
+
+**取值范围**： 整型，0～730，单位为天。
+
+● 值等于0时，用户历史资源监控数据将永久保存。
+
+● 值大于0时，用户历史资源监控数据将保存对应天数。
+
+**默认值**： 7
+
+## enable_instance_metric_persistent
+
+**参数说明**: 设置是否开启实例资源监控转存功能。开启时，对实例的监控数据会保存到GS_WLM_INSTANCE_HISTORY系统表中。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**： 布尔型
+
+- on表示开启实例资源监控转存功能。
+- off表示关闭实例资源监控转存功能。
+
+**默认值**: on
+
+## instance_metric_retention_time
+
+**参数说明**: 设置实例历史资源监控数据的保存天数。该参数仅在enable_instance_metric_persistent为on时有效。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中的方法一和方法二进行设置。
+
+**取值范围**： 整型，0～3650，单位为天。
+
+- 值等于0时，实例历史资源监控数据将永久保存。
+- 值大于0时，实例历史资源监控数据将保存对应设置天数。
+
+**默认值**: 7
+
+## resource_track_level
+
+**参数说明**: 设置当前会话的资源监控的等级。该参数只有当参数enable_resource_track为on时才有效。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**： 枚举型
+
+- none，不开启资源监控功能。
+- query，开启query级别资源监控功能。
+- operator，开启query级别和算子级别资源监控功能。
+
+**默认值**: query
+
+## resource_track_cost
+
+**参数说明**: 设置对当前会话的语句进行资源监控的最小执行代价。该参数只有当参数enable_resource_track为on时才有效。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**： 整型，-1～INT_MAX
+
+- 值为-1时，不进行资源监控。
+- 值大于或等于0时，值大于或等于0且小于等于9时，对执行代价大于等于10的语句进行资源监控。
+- 值大于或等于10时，对执行代价超过该参数值的语句进行资源监控。
+
+**默认值**: 100000
+
+## resource_track_duration
+
+**参数说明**: 设置资源监控实时视图中记录的语句执行结束后进行历史信息转存的最小执行时间。当执行完成的作业，其执行时间不小于此参数值时，作业信息会从实时视图（以statistics为后缀的视图）转存到相应的历史视图（以history为后缀的视图）中。该参数只有当[enable_resource_track](#enable_resource_track)为on时才有效。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**： 整型，0～INT_MAX，单位为秒。
+
+- 值为0时，资源监控实时视图中记录的所有语句都进行历史信息归档。
+- 值大于0时，资源监控实时视图中记录的语句的执行时间超过这个值就会进行历史信息归档。
+
+**默认值**: 1min
+
+## disable_memory_protect
+
+**参数说明**: 禁止内存保护功能。当系统内存不足时如果需要查询系统视图，可以先将此参数置为on，禁止内存保护功能，保证视图可以正常查询。该参数只适用于在系统内存不足时进行系统诊断和调试，正常运行时请保持该参数配置为off。
+
+该参数属于USERSET类型参数，且只对当前会话有效。请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**： 布尔型
+
+- on表示禁止内存保护功能。
+- off表示启动内存保护功能。
+
+**默认值**: off
+
+## query_band
+
+**参数说明**: 用于标示当前会话的作业类型，由用户自定义。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**： 字符型
+
+**默认值**: 空
+
+## memory_fault_percent
+
+**参数说明**：内存故障测试时内存申请失败的比例，仅用在DEBUG版本。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：整型，0～2147483647
+
+**默认值**：0
+
+## enable_bbox_dump
+
+**参数说明**： 是否开启黑匣子功能，在系统不配置core机制的时候仍可产生core文件。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**： 布尔型
+
+- on表示打开黑匣子功能。
+- off表示关闭黑匣子功能。
+
+**默认值**: off
+
+## bbox_dump_count
+
+**参数说明**: 在[bbox_dump_path](#bbox_dump_path)定义的路径下，允许存储的MogDB所产生core文件最大数。超过此数量，旧的core文件会被删除。此参数只有当[enable_bbox_dump](#enable_bbox_dump)为on时才生效。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**： 整型，1～20
+
+**默认值**: 8
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> 在并发产生core文件时，core文件的产生个数可能大于bbox_dump_count。
+
+## bbox_dump_path
+
+**参数说明**: 黑匣子core文件的生成路径。此参数只有当[enable_bbox_dump](#enable_bbox_dump)为on时才生效。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**： 字符型
+
+**默认值**: 空。默认生成黑匣子core文件的路径为读取/proc/sys/mogdb/core_pattern下的路径，如果这个路径不是一个目录，或者用户对此目录没有写权限，黑匣子core文件将生成在数据库的data目录下。或者以安装时指定的目录为准。
+
+## enable_ffic_log
+
+**参数说明**： 是否开启FFIC（First Failure Info Capture）功能。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**： 布尔型
+
+- on表示打开FFIC功能。
+- off表示关闭FFIC功能。
+
+**默认值**: on
+
+## io_limits
+
+**参数说明**： 每秒触发IO的上限。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应类型的设置的方法进行设置。
+
+**取值范围**： 整型，0～1073741823
+
+**默认值**: 0
+
+## io_priority
+
+**参数说明**： IO利用率高达50%时，重消耗IO作业进行IO资源管控时关联的优先级等级。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应类型的设置的方法进行设置。
+
+**取值范围**： 枚举型
+
+- None：表示不受控。
+- Low：表示限制iops为该作业原始触发数值的10%。
+- Medium：表示限制iops为该作业原始触发数值的20%。
+- High：表示限制iops为该作业原始触发数值的50%。
+
+**默认值**: None
+
+## io_control_unit
+
+**参数说明**： 行存场景下，io管控时用来对io次数进行计数的单位。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数设置方式](30-appendix)中对应类型的设置方法进行设置。
+
+记多少次io触发为一计数单位，通过此计数单位所记录的次数进行io管控。
+
+**取值范围**： 整型，1000~1000000
+
+**默认值**: 6000
+
+## session_respool
+
+**参数说明**： 当前的session关联的resource pool。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应类型的设置方法进行设置。
+
+即如果先设置cgroup_name，再设置session_respool，那么session_respool关联的控制组起作用，如果再切换cgroup_name，那么新切换的cgroup_name起作用。
+
+切换cgroup_name的过程中如果指定到Workload控制组级别，数据库不对级别进行验证。级别的范围只要在1-10范围内都可以。
+
+建议尽量不要混合使用cgroup_name和session_respool。
+
+**取值范围**： string类型，通过create resource pool所设置的资源池。
+
+**默认值**: invalid_pool
+
+## session_statistics_memory
+
+**参数说明**： 设置实时查询视图的内存大小。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**： 整型，5 * 1024 ～ max_process_memory的50%，单位KB。
+
+**默认值**: 5MB
+
+## topsql_retention_time
+
+**参数说明**： 设置历史TopSQL中gs_wlm_operator_info表中数据的保存时间。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+取值范围:  整型，0~730，单位为天。
+
+- 值为0时，表示数据永久保存。
+- 值大于0时，表示数据能够保存的对应天数。
+
+默认值： 0
+
+## session_history_memory
+
+**参数说明**： 设置历史查询视图的内存大小。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**： 整型，10 * 1024～max_process_memory的50%，单位KB。
+
+**默认值**: 10MB
+
+## transaction_pending_time
+
+**参数说明**： 事务块语句和存储过程语句排队的最大时间。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**： 整型，-1～INT_MAX/2，单位为秒。
+
+- 值为-1或0： 事务块语句和存储过程语句无超时判断，排队至资源满足可执行条件。
+- 值大于0： 事务块语句和存储过程语句排队超过所设数值的时间后，无视当前资源情况强制执行。
+
+**默认值**: 0
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/14-automatic-vacuuming.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/14-automatic-vacuuming.md
new file mode 100644
index 0000000000000000000000000000000000000000..4f2fa9c2de5466a6b2ae785c4d0acf3b5505db23
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/14-automatic-vacuuming.md
@@ -0,0 +1,186 @@
+---
+title: 自动清理
+summary: 自动清理
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 自动清理
+
+系统自动清理线程（autovacuum）自动执行VACUUM和ANALYZE命令，回收被标识为删除状态的记录空间，并更新表的统计数据。
+
+## autovacuum
+
+**参数说明**: 控制数据库自动清理线程（autovacuum）的启动。自动清理线程运行的前提是将track_counts设置为on。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+>
+> - 如果希望系统在故障恢复后，具备自动清理两阶段事务的功能，请将autovacuum设置为on;
+> - 当设置autovacuum为on，[autovacuum_max_workers](#autovacuum_max_workers)为0时，表示系统不会自动进行autovacuum，只会在故障恢复后，自动清理两阶段事务；
+> - 当设置autovacuum为on，[autovacuum_max_workers](#autovacuum_max_workers)大于0时，表示系统不仅在故障恢复后，自动清理两阶段事务，并且还可以自动清理线程。
+>
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> 即使此参数设置为off，当事务ID回绕即将发生时，数据库也会自动启动自动清理线程。对于create/drop database发生异常时，可能有的节点提交或回滚，有的节点未提交（prepared状态），此时系统不能自动修复，需要手动修复。
+
+**取值范围:**布尔型
+
+- on表示开启数据库自动清理线程。
+- off表示关闭数据库自动清理线程。
+
+**默认值**: on
+
+## autovacuum_mode
+
+**参数说明**: 该参数仅在autovacuum设置为on的场景下生效，它控制autoanalyze或autovacuum的打开情况。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**枚举类型
+
+- analyze表示只做autoanalyze。
+- vacuum表示只做autovacuum。
+- mix表示autoanalyze和autovacuum都做。
+- none表示二者都不做。
+
+**默认值**: mix
+
+## autoanalyze_timeout
+
+**参数说明**: 设置autoanalyze的超时时间。在对某张表做autoanalyze时，如果该表的analyze时长超过了autoanalyze_timeout，则自动取消该表此次analyze。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**int类型，单位是s，0~2147483。
+
+**默认值**: 5min（即300s）
+
+## autovacuum_io_limits
+
+**参数说明**: 控制autovacuum线程每秒触发IO的上限。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，0～1073741823和-1。其中-1表示不控制，而是使用系统默认控制组。
+
+**默认值**: -1
+
+## log_autovacuum_min_duration
+
+**参数说明**: 当自动清理的执行时间大于或者等于某个特定的值时，向服务器日志中记录自动清理执行的每一步操作。设置此选项有助于追踪自动清理的行为。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+举例如下:
+
+将log_autovacuum_min_duration设置为250ms，记录所有运行大于或者等于250ms的自动清理命令的相关信息。
+
+**取值范围:**整型，最小值为-1，最大值为2147483647，单位为毫秒。
+
+- 当参数设置为0时，表示所有的自动清理操作都记录到日志中。
+- 当参数设置为-1时，表示所有的自动清理操作都不记录到日志中。
+- 当参数设置为非-1时，当由于锁冲突的存在导致一个自动清理操作被跳过，记录一条消息。
+
+**默认值**: -1
+
+## autovacuum_max_workers
+
+**参数说明**: 设置能同时运行的自动清理线程的最大数量，该参数的取值上限与GUC参数max_connections和job_queue_processes大小有关。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，最小值为0（表示不会自动进行autovacuum），理论最大值为262143，实际最大值为动态值，计算公式为"262143 - max_connections - job_queue_processes - 辅助线程数 - autovacuum的lancher线程数 - 1"，其中辅助线程数和autovacuum的lancher线程数由两个宏来指定，当前版本的默认值分别为20和2。
+
+**默认值**: 3
+
+## autovacuum_naptime
+
+**参数说明**: 设置两次自动清理操作的时间间隔。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，单位为s，最小值为1，最大值为2147483。
+
+**默认值**: 10min（即600s）
+
+## autovacuum_vacuum_threshold
+
+**参数说明**: 设置触发VACUUM的阈值。当表上被删除或更新的记录数超过设定的阈值时才会对这个表执行VACUUM操作。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，最小值为0，最大值为2147483647。
+
+**默认值**: 50
+
+## autovacuum_analyze_threshold
+
+**参数说明**: 设置触发ANALYZE操作的阈值。当表上被删除、插入或更新的记录数超过设定的阈值时才会对这个表执行ANALYZE操作。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，最小值为0，最大值为2147483647。
+
+**默认值**: 50
+
+## autovacuum_vacuum_scale_factor
+
+**参数说明**: 设置触发一个VACUUM时增加到autovacuum_vacuum_threshold的表大小的缩放系数。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**浮点型，0.0～100.0
+
+**默认值**: 0.2
+
+## autovacuum_analyze_scale_factor
+
+**参数说明**: 设置触发一个ANALYZE时增加到autovacuum_analyze_threshold的表大小的缩放系数。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**浮点型，0.0～100.0
+
+**默认值**: 0.1
+
+## autovacuum_freeze_max_age
+
+**参数说明**: 设置事务内的最大时间，使得表的pg_class.relfrozenxid字段在VACUUM操作执行之前被写入。
+
+- VACUUM也可以删除pg_clog/子目录中的旧文件。
+- 即使自动清理线程被禁止，系统也会调用自动清理线程来防止循环重复。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围: 长**整型，100 000～576 460 752 303 423 487
+
+**默认值**: 20000000000
+
+## autovacuum_vacuum_cost_delay
+
+**参数说明**: 设置在自动VACUUM操作里使用的开销延迟数值。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，-1～100，单位为毫秒（ms）。其中-1表示使用常规的vacuum_cost_delay。
+
+**默认值**: 20ms
+
+## autovacuum_vacuum_cost_limit
+
+**参数说明**: 设置在自动VACUUM操作里使用的开销限制数值。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，-1～10000。其中-1表示使用常规的vacuum_cost_limit。
+
+**默认值**: -1
+
+## defer_csn_cleanup_time
+
+**参数说明**: 用来指定本地回收时间间隔，单位为毫秒（ms）。
+
+**取值范围:**整型，0~INT_MAX。
+
+**默认值**: 5s（即5000ms）
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/15-default-settings-of-client-connection/1-statement-behavior.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/15-default-settings-of-client-connection/1-statement-behavior.md
new file mode 100644
index 0000000000000000000000000000000000000000..1ba03642e55ea97b6dfd0c662558f7e8b5b4044a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/15-default-settings-of-client-connection/1-statement-behavior.md
@@ -0,0 +1,255 @@
+---
+title: 语句行为
+summary: 语句行为
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 语句行为
+
+介绍SQL语句执行过程的相关默认参数。
+
+## search_path
+
+**参数说明**: 当一个被引用对象没有指定模式时，此参数设置模式搜索顺序。它的值由一个或多个模式名构成，不同的模式名用逗号隔开。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+- 当前会话如果存放临时表的模式时，可以使用别名pg_temp将它列在搜索路径中，如'pg_temp，public'。存放临时表的模式始终会作为第一个被搜索的对象，排在pg_catalog和search_path中所有模式的前面，即具有第一搜索优先级。建议用户不要在search_path中显示设置pg_temp。如果在search_path中指定了pg_temp，但不是在最前面，系统会提示设置无效，pg_temp仍被优先搜索。通过使用别名pg_temp，系统只会在存放临时表的模式中搜索表、视图和数据类型这样的数据库对象，不会在里面搜索函数或运算符这样的数据库对象。
+- 系统表所在的模式pg_catalog，总是排在search_path中指定的所有模式前面被搜索，即具有第二搜索优先级（pg_temp具有第一搜索优先级）。建议用户不要在search_path中显式设置pg_catalog。如果在search_path中指定了pg_catalog，但不是在最前面，系统会提示设置无效，pg_catalog仍被第二优先搜索。
+- 当没有指定一个特定模式而创建一个对象时，它们被放置到以search_path为命名的第一个有效模式中。当搜索路径为空时，会报错误。
+- 通过SQL函数current_schema可以检测当前搜索路径的有效值。这和检测search_path的值不尽相同，因为current_schema显示search_path中首位有效的模式名称。
+
+**取值范围:**字符串
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+>
+> - 设置为"$user",public时，支持共享数据库（没有用户具有私有模式和所有共享使用public），用户私有模式和这些功能的组合使用。可以通过改变默认搜索路径来获得其他效果，无论是全局化的还是私有化的。
+> - 设置为空串（"）的时候，系统会自动转换成一对双引号。
+> - 设置的内容中包含双引号，系统会认为是不安全字符，会将每个双引号转换成一对双引号。
+
+**默认值**:  `"$user",public`
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+> `$user`表示与当前会话用户名同名的模式名，如果这样的模式不存在，`$user`将被忽略。
+
+## current_schema
+
+**参数说明**: 此参数设置当前的模式。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串
+
+**默认值**: `"$user",public`
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+> `$user`表示与当前会话用户名同名的模式名，如果这样的模式不存在，`$user`将被忽略。
+
+## default_tablespace
+
+**参数说明**: 当CREATE命令没有明确声明表空间时，所创建对象（表和索引等）的缺省表空间。
+
+- 值是一个表空间的名称或者一个表示使用当前数据库缺省表空间的空字符串。若指定的是一个非默认表空间，用户必须具有它的CREATE权限，否则尝试创建会失败。
+
+- 临时表不使用此参数，可以用[temp_tablespaces](#temp_tablespaces)代替。
+
+- 创建数据库时不使用此参数。默认情况下，一个新的数据库从模板数据库继承表空间配置。
+
+  该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串，其中空表示使用默认表空间。
+
+**默认值**: 空
+
+## default_storage_nodegroup
+
+**参数说明**: 此参数设置当前的默认建表所在的Node Group，目前只适用普通表。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+- 值为"installation"表示建表会默认建在安装的Node Group上。
+- 值为其他字符串表示建表会默认建在设置的Node Group上。
+
+**取值范围:**字符串
+
+**默认值**: installation
+
+## temp_tablespaces
+
+**参数说明**: 当一个CREATE命令没有明确指定一个表空间时，temp_tablespaces指定了创建临时对象（临时表和临时表的索引）所在的表空间。在这些表空间中创建临时文件用来做大型数据的排序工作。
+
+其值是一系列表空间名的列表。如果列表中有多个表空间时，每次临时对象的创建，MogDB会在列表中随机选择一个表空间；如果在事务中，连续创建的临时对象被放置在列表里连续的表空间中。如果选择的列表中的元素是一个空串，MogDB将自动将当前的数据库设为默认的表空间。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串。空字符串表示所有的临时对象仅在当前数据库默认的表空间中创建，请参见[default_tablespace](#default_tablespace)。
+
+**默认值**: 空
+
+## check_function_bodies
+
+**参数说明**: 设置是否在CREATE FUNCTION执行过程中进行函数体字符串的合法性验证。为了避免产生问题（比如避免从转储中恢复函数定义时向前引用的问题），偶尔会禁用验证。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示在CREATE FUNCTION执行过程中进行函数体字符串的合法性验证。
+- off表示在CREATE FUNCTION执行过程中不进行函数体字符串的合法性验证。
+
+**默认值**: on
+
+## default_transaction_isolation
+
+**参数说明**: 设置默认的事务隔离级别。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**枚举类型
+
+- read committed表示事务读已提交。
+- repeatable read表示事务可重复读。
+- serializable，MogDB目前功能上不支持此隔离级别，等价于repeatable read。
+
+**默认值**: read committed
+
+## default_transaction_read_only
+
+**参数说明**: 设置每个新创建事务是否是只读状态。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示只读状态。
+- off表示非只读状态。
+
+**默认值**: off
+
+## default_transaction_deferrable
+
+**参数说明**: 控制每个新事务的默认延迟状态。只读事务或者那些比序列化更加低的隔离级别的事务除外。
+
+MogDB不支持可串行化的隔离级别，因此，该参数无实际意义。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示默认延迟。
+- off表示默认不延迟。
+
+**默认值**: off
+
+## session_replication_role
+
+**参数说明**: 控制当前会话与复制相关的触发器和规则的行为。
+
+该参数属于SUSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> 设置此参数会丢弃之前任何缓存的执行计划。
+
+**取值范围:**枚举类型
+
+- origin表示从当前会话中复制插入、删除、更新等操作。
+- replica表示从其他地方复制插入、删除、更新等操作到当前会话。
+- local表示函数执行复制时会检测当前登录数据库的角色并采取相应的操作。
+
+**默认值**: origin
+
+## statement_timeout
+
+**参数说明**: 当语句执行时间超过该参数设置的时间（从服务器收到命令时开始计时）时，该语句将会报错并退出执行。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，最小值为0，最大值为2147483647，单位为毫秒。
+
+**默认值**: 0
+
+## vacuum_freeze_min_age
+
+**参数说明**: 指定VACUUM在扫描一个表时用于判断是否用FrozenXID替换事务ID的中断寿命（在同一个事务中）。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，0～576 460 752 303 423 487
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+> 尽管随时可以将此参数设为0到10亿之间的任意值，但是，VACUUM将默认其有效值范围限制在autovacuum_freeze_max_age的50%以内。
+
+**默认值**: 5000000000
+
+## vacuum_freeze_table_age
+
+**参数说明**: 指定VACUUM对全表的扫描冻结元组的时间。如果表的pg_class.relfrozenxid字段的值已经达到了参数指定的时间，VACUUM对全表进行扫描。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，0～576 460 752 303 423 487
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+> 尽管随时可以将此参数设为零到20亿之间的值，但是，VACUUM将默认其有效值范围限制在autovacuum_freeze_max_age的95%以内。定期的手动VACUUM可以在对此表的反重叠自动清理启动之前运行。
+
+**默认值**: 15000000000
+
+## bytea_output
+
+**参数说明**: 设置bytea类型值的输出格式。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**枚举类型
+
+- hex: 将二进制数据编码为每字节2位十六进制数字。
+- escape: 传统化的PostgreSQL格式。采用以ASCII字符序列表示二进制串的方法，同时将那些无法表示成ASCII字符的二进制串转换成特殊的转义序列。
+
+**默认值**: hex
+
+## xmlbinary
+
+**参数说明**: 设置二进制值是如何在XML中进行编码的。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**枚举类型
+
+- base64
+- hex
+
+**默认值**: base64
+
+## xmloption
+
+**参数说明**: 当XML和字符串值之间进行转换时，设置document或content是否是隐含的。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**枚举类型
+
+- document: 表示HTML格式的文档。
+- content: 普通的字符串。
+
+**默认值**: content
+
+## max_compile_functions
+
+**参数说明**: 设置服务器存储的函数编译结果的最大数量。存储过多的函数和存储过程的编译结果可能占用很大内存。将此参数设置为一个合理的值，有助于减少内存占用，提升系统性能。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，取值必须大于等于1。
+
+**默认值**: 1000
+
+## gin_pending_list_limit
+
+**参数说明**: 设置当GIN索引启用fastupdate时，pending list容量的最大值。当pending list的容量大于设置值时，会把pending list中数据批量移动到GIN索引数据结构中以进行清理。单个GIN索引可通过更改索引存储参数覆盖此设置值。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，最小值为64，最大值为INT_MAX，单位为KB。
+
+**默认值**: 4MB
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/15-default-settings-of-client-connection/2-zone-and-formatting.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/15-default-settings-of-client-connection/2-zone-and-formatting.md
new file mode 100644
index 0000000000000000000000000000000000000000..6c2b5dc089132484f15ccff4344bcf14a1ac7c49
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/15-default-settings-of-client-connection/2-zone-and-formatting.md
@@ -0,0 +1,190 @@
+---
+title: 区域和格式化
+summary: 区域和格式化
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 区域和格式化
+
+介绍时间格式设置的相关参数。
+
+## DateStyle <a id="DateStyle"> </a>
+
+**参数说明**: 设置日期和时间值的显示格式，以及有歧义的输入值的解析规则。
+
+这个变量包含两个独立的加载部分: 输出格式声明（ISO、Postgres、SQL、German）和输入输出的年/月/日顺序（DMY、MDY、YMD）。这两个可以独立设置或者一起设置。关键字Euro和European等价于DMY；关键字US、NonEuro、NonEuropean等价于MDY。
+
+该参数属于USERSET类型参数，请**参考表GUC参数设置方式**中对应设置方法进行设置。
+
+**取值范围:**字符串
+
+**默认值**: ISO，MDY
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+> gs_initdb会将这个参数初始化成与[lc_time](#lc_time)一致的值。
+
+**设置建议:**优先推荐使用ISO格式。Postgres、SQL和German均采用字母缩写的形式来表示时区，例如"EST、WST、CST"等。这些缩写可同时指代不同的时区，比如CST可同时代表美国中部时间（Central Standard Time （USA）UT-6:00）、澳大利亚中部时间（Central Standard Time（Australia）UT+9:30）、中国标准时间（China Standard Time UT+8:00）、古巴标准时间（Cuba Standard Time UT-4:00）。这种情况下在时区转化时可能会得不到正确的结果，从而引发其他问题。
+
+## IntervalStyle
+
+**参数说明**: 设置区间值的显示格式。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**枚举类型
+
+- sql_standard表示产生与SQL标准规定匹配的输出。
+- postgres表示产生与PostgreSQL 8.4版本相匹配的输出，当[DateStyle](#DateStyle)参数被设为ISO时。
+- postgres_verbose表示产生与PostgreSQL 8.4版本相匹配的输出，当[DateStyle](#DateStyle)参数被设为non_ISO时。
+- iso_8601表示产生与在ISO 8601中定义的"格式与代号"相匹配的输出。
+- a表示与numtodsinterval函数相匹配的输出结果，详细请参考numtodsinterval。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> IntervalStyle参数也会影响不明确的间隔输入的说明。
+
+**默认值**: postgres
+
+## TimeZone
+
+**参数说明**: 设置显示和解释时间类型数值时使用的时区。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串，可查询视图PG_TIMEZONE_NAMES获得。
+
+**默认值**: PRC
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+> gs_initdb将设置一个与其系统环境一致的时区值。
+
+## timezone_abbreviations
+
+**参数说明**: 设置服务器接受的时区缩写值。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串，可查询视图pg_timezone_names获得。
+
+**默认值**: Default
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+> Default表示通用时区的缩写, 适合绝大部分情况。但也可设置其他诸如 'Australia' 和 'India' 等用来定义特定的安装。而设置除此之外的时区缩写, 需要在建数据库之前通过相应的配置文件进行设置。
+
+## extra_float_digits
+
+**参数说明**: 这个参数为浮点数值调整显示的数据位数，浮点类型包括float4、float8 以及几何数据类型。参数值加在标准的数据位数上（FLT_DIG或DBL_DIG中合适的）。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，-15～3
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+>
+> - 设置为3，表示包括部分关键的数据位。这个功能对转储那些需要精确恢复的浮点数据特别有用。
+> - 设置为负数，表示消除不需要的数据位。
+
+**默认值**: 0
+
+## client_encoding
+
+**参数说明**: 设置客户端的字符编码类型。
+
+请根据前端业务的情况确定。尽量客户端编码和服务器端编码一致，提高效率。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**兼容PostgreSQL所有的字符编码类型。其中UTF8表示使用数据库的字符编码类型。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+>
+> - 使用命令locale -a查看当前系统支持的区域和相应的编码格式，并可以选择进行设置。
+> - 默认情况下，gs_initdb会根据当前的系统环境初始化此参数，通过locale命令可以查看当前的配置环境。
+> - 参数建议保持默认值，不建议通过gs_guc工具或其他方式直接在postgresql.conf文件中设置client_encoding参数，即使设置也不会生效，以保证MogDB内部通信编码格式一致。
+
+**默认值**: UTF8
+
+**推荐值:**SQL_ASCII/UTF8
+
+## lc_messages
+
+**参数说明**: 设置信息显示的语言。
+
+- 可接受的值是与系统相关的。
+
+- 在一些系统上，这个区域范畴并不存在，不过仍然允许设置这个变量，只是不会有任何效果。同样，也有可能是所期望的语言的翻译信息不存在。在这种情况下，用户仍然能看到英文信息。
+
+  该参数属于SUSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+>
+> - 使用命令locale -a查看当前系统支持的区域和相应的编码格式，并可以选择进行设置。
+> - 默认情况下，gs_initdb会根据当前的系统环境初始化此参数，通过locale命令可以查看当前的配置环境。
+
+**默认值**: C
+
+## lc_monetary
+
+**参数说明**: 设置货币值的显示格式，影响to_char之类的函数的输出。可接受的值是系统相关的。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+>
+> - 使用命令locale -a查看当前系统支持的区域和相应的编码格式，并可以选择进行设置。
+> - 默认情况下，gs_initdb会根据当前的系统环境初始化此参数，通过locale命令可以查看当前的配置环境。
+
+**默认值**: C
+
+## lc_numeric
+
+**参数说明**: 设置数值的显示格式，影响to_char之类的函数的输出。可接受的值是系统相关的。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+>
+> - 使用命令locale -a查看当前系统支持的区域和相应的编码格式，并可以选择进行设置。
+> - 默认情况下，gs_initdb会根据当前的系统环境初始化此参数，通过locale命令可以查看当前的配置环境。
+
+**默认值**: C
+
+## lc_time
+
+**参数说明**: 设置时间和区域的显示格式，影响to_char之类的函数的输出。可接受的值是系统相关的。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+>
+> - 使用命令locale -a查看当前系统支持的区域和相应的编码格式，并可以选择进行设置。
+> - 默认情况下，gs_initdb会根据当前的系统环境初始化此参数，通过locale命令可以查看当前的配置环境。
+
+**默认值**: C
+
+## default_text_search_config
+
+**参数说明**: 设置全文检索的配置信息。
+
+如果设置为不存在的文本搜索配置时将会报错。如果default_text_search_config对应的文本搜索配置被删除，需要重新设置default_text_search_config，否则会报设置错误。
+
+- 其被文本搜索函数使用，这些函数并没有一个明确指定的配置。
+
+- 当与环境相匹配的配置文件确定时，gs_initdb会选择一个与环境相对应的设置来初始化配置文件。
+
+  该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+> MogDB支持pg_catalog.english，pg_catalog.simple两种配置。
+
+**默认值**: pg_catalog.english
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/15-default-settings-of-client-connection/3-other-default-parameters.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/15-default-settings-of-client-connection/3-other-default-parameters.md
new file mode 100644
index 0000000000000000000000000000000000000000..e5abb7a17c020686e6949ddd0f443e89c42ee881
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/15-default-settings-of-client-connection/3-other-default-parameters.md
@@ -0,0 +1,54 @@
+---
+title: 其他缺省
+summary: 其他缺省
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 其他缺省
+
+主要介绍数据库系统默认的库加载参数。
+
+## dynamic_library_path
+
+**参数说明**: 设置数据查找动态加载的共享库文件的路径。当需要打开一个可以动态装载的模块并且在CREATE FUNCTION或LOAD命令里面声明的名称没有目录部分时，系统将搜索这个目录以查找声明的文件。
+
+用于dynamic_library_path的数值必须是一个冒号分隔的绝对路径列表。当一个路径名称以特殊变量\$libdir为开头时，会替换为MogDB发布提供的模块安装路径。例如:
+
+```bash
+dynamic_library_path = '/usr/local/lib/gaussdb:/opt/testgs/lib:$libdir'
+```
+
+该参数属于SUSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**字符串
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+> 设置为空字符串，表示关闭自动路径搜索。
+
+**默认值**:  `$libdir`
+
+## gin_fuzzy_search_limit
+
+**参数说明**: 设置GIN索引返回的集合大小的上限。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，0~2147483647
+
+**默认值**: 0
+
+## local_preload_libraries
+
+**参数说明**: 指定一个或多个共享库，它们在开始连接前预先加载。多个加载库之间用逗号分隔，除了双引号，所有的库名都转换为小写。
+
+- 并非只有系统管理员才能更改此选项，因此只能加载安装的标准库目录下plugins子目录中的库文件，数据库管理员有责任确保该目录中的库都是安全的。local_preload_libraries中指定的项可以明确含有该目录，例如`$libdir/plugins/mylib`; 也可以仅指定库的名称，例如mylib（等价于`$libdir/plugins/mylib`）。
+- 与shared_preload_libraries不同，在会话开始之前加载模块与在会话中使用到该模块的时候临时加载相比并不具有性能优势。相反，这个特性的目的是为了调试或者测量在特定会话中不明确使用LOAD加载的库。例如针对某个用户将该参数设为ALTER USER SET来进行调试。
+- 当指定的库未找到时，连接会失败。
+- 每一个支持MogDB的库都有一个"magic block"用于确保兼容性，因此不支持MogDB的库不能通过这个方法加载。
+
+该参数属于BACKEND类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串
+
+**默认值**: 空
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/16-lock-management.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/16-lock-management.md
new file mode 100644
index 0000000000000000000000000000000000000000..5c21e89e641bce95e537d5bb4076742aad02db82
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/16-lock-management.md
@@ -0,0 +1,152 @@
+---
+title: 锁管理
+summary: 锁管理
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 锁管理
+
+在MogDB中，并发执行的事务由于竞争资源会导致死锁。本节介绍的参数主要管理事务锁的机制。
+
+## deadlock_timeout
+
+**参数说明**: 设置死锁超时检测时间，以毫秒为单位。当申请的锁超过设定值时，系统会检查是否产生了死锁。
+
+- 死锁的检查代价是比较高的，服务器不会在每次等待锁的时候都运行这个过程。在系统运行过程中死锁是不经常出现的，因此在检查死锁前只需等待一个相对较短的时间。增加这个值就减少了无用的死锁检查浪费的时间，但是会减慢真正的死锁错误报告的速度。在一个负载过重的服务器上，用户可能需要增大它。这个值的设置应该超过事务持续时间，这样就可以减少在锁释放之前就开始死锁检查的问题。
+- 如果要通过设置log_lock_waits来将查询执行过程中的锁等待耗时信息写入日志，请确保log_lock_waits的设置值小于deadlock_timeout的设置值（或默认值）。
+
+该参数属于SUSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，1~2147483647，单位为毫秒（ms）。
+
+**默认值**: 1s
+
+## lockwait_timeout
+
+**参数说明**: 控制单个锁的最长等待时间。当申请的锁等待时间超过设定值时，系统会报错。
+
+该参数属于SUSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，0 ~ INT_MAX，单位为毫秒（ms）。
+
+**默认值**: 20min
+
+## update_lockwait_timeout
+
+**参数说明**: 允许并发更新参数开启情况下，该参数控制并发更新同一行时单个锁的最长等待时间。当申请的锁等待时间超过设定值时，系统会报错。
+
+该参数属于SUSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，0 ~ INT_MAX，单位为毫秒（ms）。
+
+**默认值**: 2min
+
+## max_locks_per_transaction
+
+**参数说明**: 控制每个事务能够得到的平均的对象锁的数量。
+
+- 共享的锁表的大小是以假设任意时刻最多只有max_locks_per_transaction*(max_connections+max_prepared_transactions) 个独立的对象需要被锁住为基础进行计算的。不超过设定数量的多个对象可以在任一时刻同时被锁定。当在一个事务里面修改很多不同的表时，可能需要提高这个默认数值。只能在数据库启动的时候设置。
+- 增大这个参数可能导致MogDB请求更多的System V共享内存，有可能超过操作系统的缺省配置。
+- 当运行备机时，请将此参数设置不小于主机上的值，否则，在备机上查询操作不会被允许。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，10 ~ INT_MAX
+
+**默认值**: 256
+
+## max_pred_locks_per_transaction
+
+**参数说明**: 控制每个事务允许断定锁的最大数量，是一个平均值。
+
+- 共享的断定锁表的大小是以假设任意时刻最多只有max_pred_locks_per_transaction*(max_connections+max_prepared_transactions) 个独立的对象需要被锁住为基础进行计算的。不超过设定数量的多个对象可以在任一时刻同时被锁定。当在一个事务里面修改很多不同的表时，可能需要提高这个默认数值。只能在服务器启动的时候设置。
+- 增大这个参数可能导致MogDB请求更多的System V共享内存，有可能超过操作系统的缺省配置。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，10 ~ INT_MAX
+
+**默认值**: 64
+
+## gs_clean_timeout
+
+**参数说明**: 控制主节点周期性清理临时表的时间，是一个平均值。
+
+- 数据库连接异常终止时，通常会有临时表残留，此时需要对数据库中的临时表进行清理。
+- 增大这个参数可能导致MogDB临时表清理时间延长。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，0 ~ 2147483，单位为秒（s）。
+
+**默认值**: 1min
+
+## partition_lock_upgrade_timeout
+
+**参数说明**: 在执行某些查询语句的过程中，会需要将分区表上的锁级别由允许读的ExclusiveLock级别升级到读写阻塞的AccessExclusiveLock级别。如果此时已经存在并发的读事务，那么该锁升级操作将阻塞等待。partition_lock_upgrade_timeout为尝试锁升级的等待超时时间。
+
+- 在分区表上进行MERGE PARTITION和CLUSTER PARTITION操作时，都利用了临时表进行数据重排和文件交换，为了最大程度提高分区上的操作并发度，在数据重排阶段给相关分区加锁ExclusiveLock，在文件交换阶段加锁AccessExclusiveLock。
+
+- 常规加锁方式是等待加锁，直到加锁成功，或者等待时间超过[lockwait_timeout](#lockwait_timeout)发生超时失败。
+
+- 在分区表上进行MERGE PARTITION或CLUSTER PARTITION操作时，进入文件交换阶段需要申请加锁AccessExclusiveLock，加锁方式是尝试性加锁，加锁成功了则立即返回，不成功则等待50ms后继续下次尝试，加锁超时时间使用会话级设置参数partition_lock_upgrade_timeout。
+
+- 特殊值： 若partition_lock_upgrade_timeout取值-1，表示无限等待，即不停的尝试锁升级，直到加锁成功。
+
+  该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，最小值-1，最大值3000，单位为秒（s）。
+
+**默认值**: 1800
+
+## fault_mon_timeout
+
+**参数说明**: 轻量级死锁检测周期。该参数属于SIGHUP类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，最小值0，最大值1440，单位为分钟（min）
+
+**默认值**: 5min
+
+## enable_online_ddl_waitlock
+
+**参数说明**: 控制DDL是否会阻塞等待pg_advisory_lock/pgxc_lock_for_backup等MogDB锁。主要用于OM在线操作场景，不建议用户设置。
+
+该参数属于SIGHUP类型参数，参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示开启。
+- off表示关闭。
+
+**默认值**: off
+
+## xloginsert_locks
+
+**参数说明**：控制用于并发写预写式日志锁的个数。主要用于提高写预写式日志的效率。
+
+该参数属于POSTMASTER类型参数，参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**： 整型，最小值1，最大值1000
+
+**默认值**：8
+
+## num_internal_lock_partitions
+
+**参数说明**: 控制内部轻量级锁分区的个数。主要用于各类场景的性能调优。内容以关键字和数字的KV方式组织，各个不同类型锁之间以逗号隔开。先后顺序对设置结果不影响，例如“CLOG_PART=256,CSNLOG_PART=512”等同于“CSNLOG_PART=512,CLOG_PART=256”。重复设置同一关键字时，以最后一次设置为准，例如“CLOG_PART=256,CLOG_PART=2”，设置的结果为CLOG_PART=2。当没有设置关键字时，则为默认值，各类锁的使用描述和最大、最小、默认值如下。
+
+- CLOG_PART：CLOG文件控制器的个数。增大该值可以提高CLOG日志写入效率，提升事务提交性能，但是会增大内存使用；减小该值会减少相应内存使用，但可能使得CLOG日志写入冲突变大，影响性能。最小值为1，最大值为256。
+- CSNLOG_PART：CSNLOG文件控制器的个数。增大该值可以提高CSNLOG日志写入效率，提升事务提交性能，但是会增大内存使用；减小该值会减少相应内存使用，但可能使得CSNLOG日志写入冲突变大，影响性能。最小值为1，最大值为512。
+- LOG2_LOCKTABLE_PART：常规锁表锁分区个数的2对数。增大该值可以提升正常流程常规锁获取锁的并行度，但是可能增加锁转移和锁消除时的耗时，对于等待事件在LockMgrLock时，可以调大该锁增加性能。最小值为4，即锁分区数为16；最大值为16，即锁分区数为65536。
+- TWOPHASE_PART：两阶段事务锁的分区数。调大该值可以提高两阶段事务提交的并发数。最小值为1，最大值为64。
+
+该参数属于POSTMASTER类型参数，参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串
+
+**默认值**:
+
+- CLOG_PART：256
+- CSNLOG_PART：512
+- LOG2_LOCKTABLE_PART：4
+- TWOPHASE_PART：1
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/17-version-and-platform-compatibility/1-compatibility-with-earlier-versions.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/17-version-and-platform-compatibility/1-compatibility-with-earlier-versions.md
new file mode 100644
index 0000000000000000000000000000000000000000..bbb335211d88f564c532f7acb57310271be318b1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/17-version-and-platform-compatibility/1-compatibility-with-earlier-versions.md
@@ -0,0 +1,133 @@
+---
+title: 历史版本兼容性
+summary: 历史版本兼容性
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 历史版本兼容性
+
+MogDB介绍数据库的向下兼容性和对外兼容性特性的参数控制。数据库系统的向后兼容性能够为旧版本的数据库应用提供支持。本节介绍的参数主要控制数据库的向后兼容性。
+
+## array_nulls
+
+**参数说明**: 控制数组输入解析器是否将未用引用的NULL识别为数组的一个NULL元素。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示允许向数组中输入空元素。
+- off表示向下兼容旧式模式。仍然能够创建包含NULL值的数组。
+
+**默认值**: on
+
+## backslash_quote
+
+**参数说明**: 控制字符串文本中的单引号是否能够用\'表示。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> 在字符串文本符合SQL标准的情况下，\\没有任何其他含义。这个参数影响的是如何处理不符合标准的字符串文本，包括明确的字符串转义语法是（E'…'）。
+
+**取值范围:**枚举类型
+
+- on表示一直允许使用\'表示。
+- off表示拒绝使用\'表示。
+- safe_encoding表示仅在客户端字符集编码不会在多字节字符末尾包含\\的ASCII值时允许。
+
+**默认值**: safe_encoding
+
+## escape_string_warning
+
+**参数说明**: 警告在普通字符串中直接使用反斜杠转义。
+
+- 如果需要使用反斜杠作为转义，可以调整为使用转义字符串语法（E'…'）来做转义，因为在每个SQL标准中，普通字符串的默认行为现在将反斜杠作为一个普通字符。
+- 这个变量可以帮助定位需要改变的代码。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+**默认值**: on
+
+## lo_compat_privileges
+
+**参数说明**: 控制是否启动对大对象权限检查的向后兼容模式。
+
+该参数属于SUSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+on表示当读取或修改大对象时禁用权限检查，与PostgreSQL 9.0以前的版本兼容。
+
+**默认值**: off
+
+## quote_all_identifiers
+
+**参数说明**: 当数据库生成SQL时，此选项强制引用所有的标识符（包括非关键字）。这将影响到EXPLAIN的输出及函数的结果，例如pg_get_viewdef。详细说明请参见gs_dump的-quote-all-identifiers选项。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示打开强制引用。
+- off表示关闭强制引用。
+
+**默认值**: off
+
+## sql_inheritance
+
+**参数说明**: 控制继承语义。用来控制继承表的访问策略，off表示各种命令不能访问子表，即默认使用ONLY关键字。这是为了兼容旧版本而设置的。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示可以访问子表。
+- off表示不访问子表。
+
+**默认值**: on
+
+## standard_conforming_strings
+
+**参数说明**: 控制普通字符串文本（'…'）中是否按照SQL标准把反斜扛当普通文本。
+
+- 应用程序通过检查这个参数可以判断字符串文本的处理方式。
+- 建议明确使用转义字符串语法（E'…'）来转义字符。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示打开控制功能。
+- off表示关闭控制功能。
+
+**默认值**: on
+
+## synchronize_seqscans
+
+**参数说明**: 控制启动同步的顺序扫描。在大约相同的时间内并行扫描读取相同的数据块，共享I/O负载。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示扫描可能从表的中间开始，然后选择"环绕"方式来覆盖所有的行，为了与已经在进行中的扫描活动同步。这可能会造成没有用ORDER BY子句的查询得到行排序造成不可预测的后果。
+- off表示确保顺序扫描是从表头开始的。
+
+**默认值**: on
+
+## enable_beta_features
+
+**参数说明**: 控制开启某些非正式发布的特性，仅用于POC验证。这些特性属于延伸特性，建议客户谨慎开启，在某些功能场景下可能存在问题。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示开启这些功能受限的特性，保持前向兼容。但某些场景可能存在功能上的问题。
+- off表示禁止使用这些特性。
+
+**默认值**: off
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/17-version-and-platform-compatibility/2-platform-and-client-compatibility.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/17-version-and-platform-compatibility/2-platform-and-client-compatibility.md
new file mode 100644
index 0000000000000000000000000000000000000000..4c192bdba612eb647fb160d2f634a831668db2cc
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/17-version-and-platform-compatibility/2-platform-and-client-compatibility.md
@@ -0,0 +1,168 @@
+---
+title: 平台和客户端兼容性
+summary: 平台和客户端兼容性
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 平台和客户端兼容性
+
+很多平台都使用数据库系统，数据库系统的对外兼容性给平台提供了很大的方便。
+
+## convert_string_to_digit
+
+**参数说明**：设置隐式转换优先级，是否优先将字符串转为数字。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示优先将字符串转为数字。
+- off表示不优先将字符串转为数字。
+
+**默认值**：on
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 该参数调整会修改内部数据类型转换规则，导致不可预期的行为，请谨慎操作。
+
+## nls_timestamp_format
+
+**参数说明**：设置时间戳默认格式。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：字符串
+
+**默认值**：DD-Mon-YYYY HH:MI:SS.FF AM
+
+## max_function_args
+
+**参数说明**：函数参数最大个数。
+
+该参数属于INTERNAL类型参数，为固定参数，用户无法修改此参数，只能查看。
+
+**取值范围**：整型
+
+**默认值**：8192
+
+## transform_null_equals
+
+**参数说明**: 控制表达式expr = NULL（或NULL = expr）当做expr IS NULL处理。如果expr得出NULL值则返回真，否则返回假。
+
+- 正确的SQL标准兼容的expr = NULL总是返回NULL（未知）。
+- Microsoft Access里的过滤表单生成的查询使用expr = NULL来测试空值。打开这个选项，可以使用该接口来访问数据库。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示控制表达式expr = NULL（或NULL = expr）当做expr IS NULL处理。
+- off表示不控制，即expr = NULL总是返回NULL（未知）。
+
+**默认值**: off
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 新用户经常在涉及NULL的表达式上语义混淆，故默认值设为off。
+
+## support_extended_features
+
+**参数说明**: 控制是否支持数据库的扩展特性。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示支持数据库的扩展特性。
+- off表示不支持数据库的扩展特性。
+
+**默认值**: off
+
+## sql_compatibility
+
+**参数说明**: 控制数据库的SQL语法和语句行为同哪一个主流数据库兼容。该参数属于INTERNAL类型参数，用户无法修改，只能查看。
+
+**取值范围**: 枚举型
+
+- A表示同O数据库兼容。
+- B表示同MY数据库兼容。
+- C表示同TD数据库兼容。
+- PG表示同POSTGRES数据库兼容。
+
+**默认值**: A
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+>
+> - 该参数只能在执行**CREATE DATABASE**命令创建数据库的时候设置。
+> - 在数据库中，该参数只能是确定的一个值，要么始终设置为A，要么始终设置为B，请勿任意改动，否则会导致数据库行为不一致。
+
+## behavior_compat_options
+
+**参数说明**: 数据库兼容性行为配置项，该参数的值由若干个配置项用逗号隔开构成。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串
+
+**默认值**: 空
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 当前只支持[表1](#jianrongxing)。
+> - 配置多个兼容性配置项时，相邻配置项用逗号隔开，例如：set behavior_compat_options='end_month_calculate,display_leading_zero';
+
+**表 1** 兼容性配置项 <a id="jianrongxing"> </a>
+
+| **兼容性配置项**          | **兼容性行为控制**                                           |
+| :------------------------ | :----------------------------------------------------------- |
+| display_leading_zero      | 浮点数显示配置项。<br />- 不设置此配置项时，对于-1\~0和0\~1之间的小数，不显示小数点前的0。比如，0.25显示为.25。<br />- 设置此配置项时，对于-1\~0和0\~1之间的小数，显示小数点前的0。比如，0.25显示为0.25。 |
+| end_month_calculate       | add_months函数计算逻辑配置项。<br />假定函数add_months的两个参数分别为param1和param2，param1的月份和param2的和为月份result。<br />- 不设置此配置项时，如果param1的日期（Day字段）为月末，并且param1的日期（Day字段）比result月份的月末日期小，计算结果中的日期字段（Day字段）和param1的日期字段保持一致。比如，<br />`mogdb=# select add_months('2018-02-28',3) from sys_dummy; add_months ---------------------- 2018-05-28 00:00:00 (1 row)`<br />- 设置此配置项时，如果param1的日期（Day字段）为月末，并且param1的日期（Day字段）比result月份的月末日期比小，计算结果中的日期字段（Day字段）和result的月末日期保持一致。比如，<br />`mogdb=# select add_months('2018-02-28',3) from sys_dummy; add_months ---------------------- 2018-05-31 00:00:00 (1 row)` |
+| compat_analyze_sample     | analyze采样行为配置项。<br />设置此配置项时，会优化analyze的采样行为，主要体现在analyze时全局采样会更精确的控制在3万条左右，更好的控制analyze时DBnode端的内存消耗，保证analyze性能的稳定性。 |
+| bind_schema_tablespace    | 绑定模式与同名表空间配置项。<br />如果存在与模式名sche_name相同的表空间名，那么如果设置search_path为sche_name， default_tablespace也会同步切换到sche_name。 |
+| bind_procedure_searchpath | 未指定模式名的数据库对象的搜索路径配置项。<br />在存储过程中如果不显示指定模式名，会优先在存储过程所属的模式下搜索。<br />如果找不到，则有两种情况：<br />- 若不设置此参数，报错退出。<br />- 若设置此参数，按照search_path中指定的顺序继续搜索。如果还是找不到，报错退出。 |
+| correct_to_number         | 控制to_number()结果兼容性的配置项。<br />若设置此配置项，则to_number()函数结果与pg11保持一致，否则默认与O db保持一致。 |
+| unbind_dive_bound         | 控制对整数除法的结果进行范围校验。<br />若设置此配置项，则不需要对除法结果做范围校验，例如，INT_MIN/(-1)可以得到输出结果为INT_MAX+1，反之，则会因为超过结果大于INT_MAX而报越界错误。 |
+| merge_update_multi        | 控制merge into匹配多行时是否进行update操作。<br />若设置此配置项，匹配多行时update不报错，否则默认与a db保持一致，报错。 |
+| return_null_string        | 控制函数lpad()和rpad()结果为空字符串”的显示配置项。<br />- 不设置此配置项时，空字符串显示为NULL。<br />`mogdb=# select length(lpad('123',0,'*')) from sys_dummy; length -----------------------  (1 row)*`<br />- 设置此配置项时，空字符串显示为”。<br />`mogdb=# select length(lpad('123',0,'*')) from sys_dummy; length ----------------------- 0 (1 row)` |
+| compat_concat_variadic    | 控制函数concat()和concat_ws()对variadic类型结果兼容性的配置项。<br />若设置此配置项，当concat函数参数为variadic类型时，保留a db和Teradata兼容模式下不同的结果形式；否则默认a db和Teradata兼容模式下结果相同，且与a db保持一致。由于MY无variadic类型，所以该选项对MY无影响。 |
+| merge_update_multi        | 控制在使用MERGE INTO … WHEN MATCHED THEN UPDATE（参考**MERGE INTO**） 和INSERT … ON DUPLICATE KEY UPDATE（参考**INSERT**）时，当目标表中一条目标数据与多条源数据冲突时UPDATE行为。<br />若设置此配置项，当存在上述场景时，该冲突行将会多次执行UPDATE；否则（默认）报错，即MERGE或INSERT操作失败。 |
+| hide_tailing_zero         | numeric显示配置项。不设置此项时，numeric按照指定精度显示。设置此项时，隐藏小数点后的末尾0。<br />`set behavior_compat_options='hide_tailing_zero'; select cast(123.123 as numeric(15,10)); numeric ---- 123.123 (1 row)` |
+
+## plpgsql.variable_conflict
+
+**参数说明**：设置同名的存储过程变量和表的列的使用优先级。
+
+该参数属于USERSET类型参数，仅支持表[GUC参数设置方式](30-appendix)中对应设置方法3进行设置。
+
+**取值范围**：字符串
+
+- error表示遇到存储过程变量和表的列名同名则编译报错。
+- use_variable表示存储过程变量和表的列名同名则优先使用变量。
+- use_column表示存储过程变量和表的列名同名则优先使用列名。
+
+**默认值**：error
+
+## td_compatible_truncation
+
+**参数说明**: 控制是否开启与Teradata数据库相应兼容的特征。该参数在用户连接上与TD兼容的数据库时，可以将参数设置成为on（即超长字符串自动截断功能启用），该功能启用后，在后续的insert语句中，对目标表中char和varchar类型的列插入超长字符串时，会按照目标表中相应列定义的最大长度对超长字符串进行自动截断。保证数据都能插入目标表中，而不是报错。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 超长字符串自动截断功能不适用于insert语句包含外表的场景。 如果向字符集为字节类型编码（SQL_ASCII，LATIN1等）的数据库中插入多字节字符数据（如汉字等），且字符数据跨越截断位置，这种情况下，按照字节长度自动截断，自动截断后会在尾部产生非预期结果。如果用户有对于截断结果正确性的要求，建议用户采用UTF8等能够按照字符截断的输入字符集作为数据库的编码集。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示启动超长字符串自动截断功能。
+- off表示停止超长字符串自动截断功能。
+
+**默认值**: off
+
+## lastval_supported
+
+**参数说明**: 控制是否可以使用lastval函数。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示支持lastval函数，同时nextval函数不支持下推。
+- off表示不支持lastval函数，同时nextval函数可以下推。
+
+**默认值**: off
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/18-fault-tolerance.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/18-fault-tolerance.md
new file mode 100644
index 0000000000000000000000000000000000000000..3b529c838538b6a950d9e5721ce83698645b9950
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/18-fault-tolerance.md
@@ -0,0 +1,109 @@
+---
+title: 容错性
+summary: 容错性
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 容错性
+
+当数据库系统发生错误时，以下参数控制服务器处理错误的方式。
+
+## exit_on_error
+
+**参数说明**: 打开该开关，ERROR级别报错会升级为PANIC报错，从而可以产生core堆栈。主要用于问题定位和业务测试。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示ERROR级别报错会升级为PANIC报错。
+- off表示不会对ERROR级别报错进行升级。
+
+**默认值**: off
+
+## restart_after_crash
+
+**参数说明**: 设置为on，后端进程崩溃时，MogDB将自动重新初始化此后端进程。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示能够最大限度地提高数据库的可用性。
+
+  在某些情况（比如当采用管理工具（例如xCAT）管理MogDB时），能够最大限度地提高数据库的可用性。
+
+- off表示能够使得管理工具在后端进程崩溃时获取控制权并采取适当的措施进行处理。
+
+**默认值**: on
+
+## omit_encoding_error
+
+**参数说明**: 设置为on，数据库的客户端字符集编码为UTF-8时，出现的字符编码转换错误将打印在日志中，有转换错误的被转换字符会被忽略，以“?”代替。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示有转换错误的字符将被忽略，以"?"代替，打印错误信息到日志中。
+- off表示有转换错误的字符不能被转换，打印错误信息到终端。
+
+**默认值**: off
+
+## max_query_retry_times
+
+**参数说明**: 指定SQL语句出错自动重试功能的最大重跑次数（目前支持重跑的错误类型为"Connection reset by peer"、"Lock wait timeout"和"Connection timed out"等），设定为0时关闭重跑功能。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，0~20。
+
+**默认值**: 0
+
+## cn_send_buffer_size
+
+**参数说明**: 指定数据库主节点发送数据缓存区的大小。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，8~128， 单位为KB。
+
+**默认值**: 8KB
+
+## retry_ecode_list
+
+**参数说明**: 指定SQL语句出错自动重试功能支持的错误类型列表。
+
+该参数属于USERSET类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串。
+
+**默认值**: YY001 YY002 YY003 YY004 YY005 YY006 YY007 YY008 YY009 YY010 YY011 YY012 YY013 YY014 YY015 53200 08006 08000 57P01 XX003 XX009 YY016
+
+## data_sync_retry
+
+**参数说明**: 控制当fsync到磁盘失败后是否继续运行数据库。由于在某些操作系统的场景下，fsync失败后重试阶段即使再次fsync失败也不会报错，从而导致数据丢失。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示当fsync同步到磁盘失败后采取重试机制，数据库继续运行。
+- off表示当fsync同步到磁盘失败后直接报panic，停止数据库。
+
+**默认值**: off
+
+## remote_read_mode
+
+**参数说明**：远程读功能开关。读取主机上的页面失败时可以从备机上读取对应的页面。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：枚举类型
+
+- off表示关闭远程读功能。
+- non_authentication表示开启远程读功能，但不进行证书认证。
+- authentication表示开启远程读功能，但要进行证书认证。
+
+**默认值**：authentication
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/19-connection-pool-parameters.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/19-connection-pool-parameters.md
new file mode 100644
index 0000000000000000000000000000000000000000..b257330b6342026486ccdfc910a819b22195ed4d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/19-connection-pool-parameters.md
@@ -0,0 +1,23 @@
+---
+title: 连接池参数
+summary: 连接池参数
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 连接池参数
+
+当使用连接池访问数据库时，在系统运行过程中，数据库连接是被当作对象存储在内存中的，当用户需要访问数据库时，并非建立一个新的连接，而是从连接池中取出一个已建立的空闲连接来使用。用户使用完毕后，数据库并非将连接关闭，而是将连接放回连接池中，以供下一个请求访问使用。
+
+## cache_connection
+
+**参数说明**: 是否回收连接池的连接。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数设置方式](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示回收连接池的连接。
+- off表示不回收连接池的连接。
+
+**默认值**: on
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/2-file-location.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/2-file-location.md
new file mode 100644
index 0000000000000000000000000000000000000000..d9b660ca61f0f62621061a4a1cc8bc37646f0016
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/2-file-location.md
@@ -0,0 +1,69 @@
+---
+title: 文件位置
+summary: 文件位置
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 文件位置
+
+数据库安装后会自动生成三个配置文件（postgresql.conf、pg_hba.conf和pg_ident.conf），并统一存放在数据目录（data）下。用户可以使用本节介绍的方法修改配置文件的名称和存放路径。
+
+修改任意一个配置文件的存放目录时，postgresql.conf里的data_directory参数必须设置为实际数据目录（data）。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> 考虑到配置文件修改一旦出错对数据库的影响很大，不建议安装后再修改本节的配置文件。
+
+## data_directory
+
+**参数说明**: 设置MogDB的数据目录（data目录）。此参数可以通过如下方式指定。
+
+- 在安装MogDB时指定。
+- 该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串，长度大于0
+
+**默认值**: 安装时指定，如果在安装时不指定，则默认不初始化数据库。
+
+## config_file
+
+**参数说明**: 设置主服务器配置文件名称（postgresql.conf）。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置，不支持使用表[GUC参数设置方式](30-appendix)中的方式四进行修改。
+
+**取值范围:**字符串，长度大于0
+
+**默认值**: postgresql.conf（实际安装可能带有绝对目录）
+
+## hba_file
+
+**参数说明**: 设置基于主机认证（HBA）的配置文件（pg_hba.conf）。此参数只能在配置文件postgresql.conf中指定。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串
+
+**默认值**: pg_hba.conf（实际安装可能带有绝对目录）
+
+## ident_file
+
+**参数说明**: 设置用于客户端认证的配置文件的名称（pg_ident.conf）。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串
+
+**默认值**: pg_ident.conf（实际安装可能带有绝对目录）
+
+## external_pid_file
+
+**参数说明**: 声明可被服务器管理程序使用的额外PID文件。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> 这个参数只能在数据库服务重新启动后生效。
+
+**取值范围:**字符串
+
+**默认值**: 空
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/20-MogDB-transaction.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/20-MogDB-transaction.md
new file mode 100644
index 0000000000000000000000000000000000000000..972ebf0d376896a08b7e7e1369239e95bc1f2bab
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/20-MogDB-transaction.md
@@ -0,0 +1,122 @@
+---
+title: MogDB事务
+summary: MogDB事务
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# MogDB事务
+
+介绍MogDB事务隔离、事务只读、最大prepared事务数、维护模式目的参数设置及取值范围等内容。
+
+## transaction_isolation
+
+**参数说明**: 设置当前事务的隔离级别。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串，只识别以下字符串，大小写空格敏感:
+
+- serializable: MogDB中等价于REPEATABLE READ。
+- read committed: 只能读取已提交的事务的数据（缺省），不能读取到未提交的数据。
+- repeatable read: 仅能读取事务开始之前提交的数据，不能读取未提交的数据以及在事务执行期间由其它并发事务提交的修改。
+- default: 设置为default_transaction_isolation所设隔离级别。
+
+**默认值**: read committed
+
+## transaction_read_only
+
+**参数说明**: 设置当前事务是只读事务。
+
+该参数在数据库恢复过程中或者在备机里，固定为on；否则，固定为default_transaction_read_only的值。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示设置当前事务为只读事务。
+- off表示该事务可以是非只读事务。
+
+**默认值**: off
+
+## xc_maintenance_mode
+
+**参数说明**: 设置系统进入维护模式。
+
+该参数属于SUSET类型参数，仅支持表[GUC参数分类](30-appendix)中的方式三进行设置。
+
+**取值范围:**布尔型
+
+- on表示该功能启用。
+- off表示该功能被禁用。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+>
+> 谨慎打开这个开关，避免引起MogDB数据不一致。
+
+**默认值**: off
+
+## allow_concurrent_tuple_update
+
+**参数说明**: 设置是否允许并发更新。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示该功能启用。
+- off表示该功能被禁用。
+
+**默认值**: on
+
+## transaction_deferrable
+
+**参数说明**: 指定是否允许一个只读串行事务延迟执行，使其不会执行失败。该参数设置为on时，当一个只读事务发现读取的元组正在被其他事务修改，则延迟该只读事务直到其他事务修改完成。目前，MogDB暂时未用到这个参数。与该参数类似的还有一个default_transaction_deferrable，设置它来指定一个事务是否允许延迟。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示允许执行。
+- off表示不允许执行。
+
+**默认值**: off
+
+## enable_show_any_tuples
+
+**参数说明**: 该参数只有在只读事务中可用，用于分析。当这个参数被置为on/true时，表中元组的所有版本都会可见。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on/true表示表中元组的所有版本都会可见。
+- off/false表示表中元组的所有版本都不可见。
+
+**默认值**: off
+
+## replication_type
+
+**参数说明**: 标记当前HA模式是单主机模式、主备从模式还是一主多备模式。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+该参数用户不能自己去设置参数值。
+
+**取值范围:**0~2
+
+- 2 表示单主机模式，此模式无法扩展备机。
+- 1 表示使用一主多备模式，全场景覆盖，推荐使用。
+- 0 表示主备从模式，目前此模式暂不支持。
+
+**默认值**: 1
+
+## pgxc_node_name
+
+**参数说明**: 指定节点名称。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。此参数修改后会导致连接数据库实例失败，不建议进行修改。
+
+**取值范围**: 字符串
+
+**默认值**: 当前节点名称
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/21-developer-options.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/21-developer-options.md
new file mode 100644
index 0000000000000000000000000000000000000000..a9b146af79b20c83aa69e7067765607ded788739
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/21-developer-options.md
@@ -0,0 +1,288 @@
+---
+title: 开发人员选项
+summary: 开发人员选项
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 开发人员选项
+
+## allow_system_table_mods
+
+**参数说明**: 设置是否允许修改系统表的结构。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+不建议修改该参数默认值，如果设置为on，可能导致系统表损坏，甚至数据库无法启动。
+
+**取值范围:**布尔型
+
+- on表示允许修改系统表的结构。
+- off表示不允许修改系统表的结构。
+
+**默认值**: off
+
+## debug_assertions
+
+**参数说明**: 控制打开各种断言检查。能够协助调试，当遇到奇怪的问题或者崩溃，请把此参数打开，因为它能暴露编程的错误。要使用这个参数，必须在编译MogDB的时候定义宏USE_ASSERT_CHECKING（通过configure选项 -enable-cassert完成）。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示打开断言检查。
+- off表示不打开断言检查。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+>
+> 当启用断言选项编译MogDB时，debug_assertions缺省值为on 。
+
+**默认值**: off
+
+## ignore_checksum_failure
+
+**参数说明**: 设置读取数据时是否忽略校验信息检查失败（但仍然会告警），继续执行可能导致崩溃，传播或隐藏损坏数据，无法从远程节点恢复数据及其他严重问题。不建议用户修改设置。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示忽略数据校验错误。
+- off表示数据校验错误正常报错。
+
+**默认值**: off
+
+## ignore_system_indexes
+
+**参数说明**: 读取系统表时忽略系统索引（但是修改系统表时依然同时修改索引）。
+
+该参数属于BACKEND类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+>
+> 这个参数在从系统索引被破坏的表中恢复数据的时候非常有用。
+
+**取值范围:**布尔型
+
+- on表示忽略系统索引。
+- off表示不忽略系统索引。
+
+**默认值**: off
+
+## post_auth_delay
+
+**参数说明**: 在认证成功后，延迟指定时间，启动服务器连接。允许调试器附加到启动进程上。
+
+该参数属于BACKEND类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，最小值为0，最大值为2147，单位为秒。
+
+**默认值**: 0
+
+## pre_auth_delay
+
+**参数说明**: 启动服务器连接后，延迟指定时间，进行认证。允许调试器附加到认证过程上。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，最小值为0～60，单位为秒。
+
+**默认值**: 0
+
+## trace_notify
+
+**参数说明**: 为LISTEN和NOTIFY命令生成大量调试输出。client_min_messages或log_min_messages级别必须是DEBUG1或者更低时，才能把这些输出分别发送到客户端或者服务器日志。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示打开输出功能。
+- off表示关闭输出功能。
+
+**默认值**: off
+
+## trace_recovery_messages
+
+**参数说明**: 启用恢复相关调试输出的日志录，否则将不会被记录。该参数允许覆盖正常设置的log_min_messages，但是仅限于特定的消息，这是为了在调试备机中使用。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**枚举类型，有效值有debug5、debug4、debug3、debug2、debug1、log，取值的详细信息请参见log_min_messages。
+
+**默认值**: log
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+>
+> - 默认值log表示不影响记录决策。
+> - 除默认值外，其他值会导致优先级更高的恢复相关调试信息被记录，因为它们有log优先权。对于常见的log_min_messages设置，这会导致无条件地将它们记录到服务器日志上。
+
+## trace_sort
+
+**参数说明**: 控制是否在日志中打印排序操作中的资源使用相关信息。这个选项只有在编译MogDB的时候定义了TRACE_SORT宏的时候才可用，不过目前TRACE_SORT是由缺省定义的。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示打开控制功能。
+- off表示关闭控制功能。
+
+**默认值**: off
+
+## zero_damaged_pages
+
+**参数说明**: 控制检测导致MogDB报告错误的损坏的页头，终止当前事务。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+设置为on时，会导致系统报告一个警告，把损坏的页面填充为零然后继续处理。这种行为会破坏数据，也就是所有在已经损坏页面上的行记录。但是它允许绕开坏页面然后从表中尚存的未损坏页面上继续检索数据行。因此它在因为硬件或者软件错误导致的崩溃中进行恢复是很有用的。通常不应该把它设置为on，除非不需要从崩溃的页面中恢复数据。
+
+**默认值**: off
+
+## remotetype
+
+**参数说明**: 设置远程连接类型。
+
+该参数不支持修改。
+
+**取值范围**: 枚举类型，有效值有application，datanode，internaltool。
+
+**默认值**: application
+
+## max_user_defined_exception
+
+**参数说明**: 异常最大个数，默认值不可更改。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，当前只能取固定值1000
+
+**默认值**: 1000
+
+## enable_fast_numeric
+
+**参数说明**: 标识是否开启Numeric类型数据运算优化。Numeric数据运算是较为耗时的操作之一，通过将Numeric转化为int64/int128类型，提高Numeric运算的性能。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on/true表示开启Numeric优化。
+- off/false表示关闭Numeric优化。
+
+**默认值**: on
+
+## enable_compress_spill
+
+**参数说明**: 标识是否开启下盘压缩功能。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on/true表示开启下盘优化。
+- off/false表示关闭下盘优化。
+
+**默认值**: on
+
+## resource_track_log
+
+**参数说明**: 控制自诊断的日志级别。目前仅对多列统计信息进行控制。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串
+
+- summary: 显示简略的诊断信息。
+- detail: 显示详细的诊断信息。
+
+目前这两个参数值只在显示多列统计信息未收集的告警的情况下有差别，summary不显示未收集多列统计信息的告警，detail会显示这类告警。
+
+**默认值**: summary
+
+## show_acce_estimate_detail
+
+**参数说明**: 评估信息一般用于运维人员在维护工作中使用，因此该参数默认关闭，此外为了避免这些信息干扰正常的explain信息显示，只有在explain命令的verbose选项打开的情况下才显示评估信息
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示可以在explain命令的输出中显示评估信息。
+- off表示不在explain命令的输出中显示评估信息。
+
+**默认值**: off
+
+## support_batch_bind
+
+**参数说明**: 控制是否允许通过JDBC、ODBC、Libpq等接口批量绑定和执行PBE形式的语句。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示使用批量绑定和执行。
+- off表示不使用批量绑定和执行。
+
+**默认值**: on
+
+## numa_distribute_mode
+
+**参数说明**: 用于控制部分共享数据和线程在NUMA节点间分布的属性。用于大型多NUMA节点的ARM服务器性能调优，一般不用设置。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串，当前有效取值为'none', 'all'。
+
+- none:  表示不启用本特性。
+- all: 表示将部分共享数据和线程分布到不同的NUMA节点下，减少远端访存次数，提高性能。目前仅适用于拥有多个NUMA节点的ARM服务器，并且要求全部NUMA节点都可用于数据库进程，不支持仅选择一部分NUMA节点。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 当前版本x86平台下不支持numa_distribute_mode设置为all。
+
+**默认值**: 'none'
+
+## log_pagewriter
+
+**参数说明**: 设置用于增量检查点打开后，显示线程的刷页信息以及增量检查点的详细信息，信息比较多，不建议设置为true。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+**默认值**: off
+
+## advance_xlog_file_num
+
+**参数说明**: 用于控制在后台周期性地提前初始化xlog文件的数目。该参数是为了避免事务提交时执行xlog文件初始化影响性能，但仅在超重负载时才可能出现，因此一般不用配置。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，0~1000000（0表示不提前初始化）。例如，取值10，表示后台线程会周期性地根据当前xlog写入位置提前初始化10个xlog文件。
+
+**默认值**: 0
+
+## enable_beta_opfusion
+
+**参数说明**: 当参数enable_opfusion设置为on时，是否加速TPC-C中聚合函数、排序、nestloop join等SQL语句的执行。对于nestloop join SQL语句，enable_beta_nestloop_fusion必须设置为on。
+
+**取值范围**:  布尔型
+
+**默认值**: off
+
+## string_hash_compatible
+
+**参数说明**: 该参数用来说明char类型和varchar/text类型的hash值计算方式是否相同，以此来判断进行分布列从char类型到相同值的varchar/text类型转换，数据分布变化时，是否需要进行重分布。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：布尔型
+
+- on表示计算方式相同，不需要进行重分布。
+- off表示计算方式不同，需要进行重分布。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 计算方式的不同主要体现在字符串计算hash值时传入的字节长度上。（如果为char，则会忽略字符串后面空格的长度，如果为text或varchar，则会保留字符串后面空格的长度。）hash值的计算会影响到查询的计算结果，因此此参数一旦设置后，在整个数据库使用过程中不能再对其进行修改，以避免查询错误。
+
+**默认值**: off
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/22-auditing/1-audit-switch.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/22-auditing/1-audit-switch.md
new file mode 100644
index 0000000000000000000000000000000000000000..e47124e53490a1a2e74c4ffbbe14f5706c56b88e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/22-auditing/1-audit-switch.md
@@ -0,0 +1,113 @@
+---
+title: 审计开关
+summary: 审计开关
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 审计开关
+
+## audit_enabled
+
+**参数说明**: 控制审计进程的开启和关闭。审计进程开启后，将从管道读取后台进程写入的审计信息，并写入审计文件。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示启动审计功能。
+- off表示关闭审计功能。
+
+**默认值**: on
+
+## audit_directory
+
+**参数说明**: 审计文件的存储目录。一个相对于数据目录data的路径，可自行指定。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串
+
+**默认值**: pg_audit。如果使用om工具部署MogDB，则审计日志路径为"$GAUSSLOG/pg_audit/实例名称"。
+
+## audit_data_format
+
+**参数说明**: 审计日志文件的格式。当前仅支持二进制格式。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串
+
+**默认值**: binary
+
+## audit_rotation_interval
+
+**参数说明**: 指定创建一个新审计日志文件的时间间隔。当现在的时间减去上次创建一个审计日志的时间超过了此参数值时，服务器将生成一个新的审计日志文件。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，1~INT_MAX/60，单位为min。
+
+**默认值**: 1d
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> 请不要随意调整此参数，否侧可能会导致audit_resource_policy无法生效，如果需要控制审计日志的存储空间和时间，请使用[audit_resource_policy](#audit_resource_policy)、[audit_space_limit](#audit_space_limit)和[audit_file_remain_time](#audit_file_remain_time)参数进行控制。
+
+## audit_rotation_size
+
+**参数说明**: 指定审计日志文件的最大容量。当审计日志消息的总量超过此参数值时，服务器将生成一个新的审计日志文件。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，1024~1048576，单位为KB。
+
+**默认值**: 10MB
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> 请不要随意调整此参数，否侧可能会导致audit_resource_policy无法生效，如果需要控制审计日志的存储空间和时间，请使用audit_resource_policy、audit_space_limit和audit_file_remain_time参数进行控制。
+
+## audit_resource_policy
+
+**参数说明**: 控制审计日志的保存策略，以空间还是时间限制为优先策略。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示采用空间优先策略，最多存储[audit_space_limit](#audit_space_limit)大小的日志。
+- off表示采用时间优先策略，最少存储[audit_file_remain_time](#audit_file_remain_time)长度时间的日志。
+
+**默认值**: on
+
+## audit_file_remain_time
+
+**参数说明**: 表示需记录审计日志的最短时间要求，该参数在[audit_resource_policy](#audit_resource_policy)为off时生效。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，0~730，单位为day，0表示无时间限制。
+
+**默认值**: 90
+
+## audit_space_limit
+
+**参数说明**: 审计文件占用的磁盘空间总量。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，1024KB~1024GB，单位为KB。
+
+**默认值**: 1GB
+
+## audit_file_remain_threshold
+
+**参数说明**: 审计目录下审计文件个数的最大值。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，1~1048576
+
+**默认值**: 1048576
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> 请尽量保证此参数为1048576，并不要随意调整此参数，否则可能会导致audit_resource_policy无法生效，如果需要控制审计日志的存储空间和时间，请使用audit_resource_policy、audit_space_limit和audit_file_remain_time参数进行控制。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/22-auditing/2-user-and-permission-audit.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/22-auditing/2-user-and-permission-audit.md
new file mode 100644
index 0000000000000000000000000000000000000000..8d262b3d691bd92535669dc09fbc8ac51e112853
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/22-auditing/2-user-and-permission-audit.md
@@ -0,0 +1,83 @@
+---
+title: 用户和权限审计
+summary: 用户和权限审计
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 用户和权限审计
+
+## audit_login_logout
+
+**参数说明**: 这个参数决定是否审计MogDB用户的登录（包括登录成功和登录失败）、注销。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，0~7。
+
+- 0表示关闭用户登录、注销审计功能。
+- 1表示只审计用户登录成功。
+- 2表示只审计用户登录失败。
+- 3表示只审计用户登录成功和失败。
+- 4表示只审计用户注销。
+- 5表示只审计用户注销和登录成功。
+- 6表示只审计用户注销和登录失败。
+- 7表示审计用户登录成功、失败和注销。
+
+**默认值**: 7
+
+## audit_database_process
+
+**参数说明**: 该参数决定是否对MogDB的启动、停止、切换和恢复进行审计。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，0、1。
+
+- 0表示关闭MogDB启动、停止、恢复和切换审计功能。
+- 1表示开启MogDB启动、停止、恢复和切换审计功能。
+
+**默认值**: 1
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> MogDB启动时DN执行备升主流程，因此DN启动时审计日志中类型为system_switch。
+
+## audit_user_locked
+
+**参数说明**: 该参数决定是否审计MogDB用户的锁定和解锁。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，0、1。
+
+- 0表示关闭用户锁定和解锁审计功能。
+- 1表示开启审计用户锁定和解锁功能。
+
+**默认值**: 1
+
+## audit_user_violation
+
+**参数说明**: 该参数决定是否审计用户的越权访问操作。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，0、1。
+
+- 0表示关闭用户越权操作审计功能。
+- 1表示开启用户越权操作审计功能。
+
+**默认值**: 0
+
+## audit_grant_revoke
+
+**参数说明**: 该参数决定是否审计MogDB用户权限授予和回收的操作。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，0、1。
+
+- 0表示关闭审计用户权限授予和回收功能。
+- 1表示开启审计用户权限授予和回收功能。
+
+**默认值**: 1
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/22-auditing/3-operation-audit.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/22-auditing/3-operation-audit.md
new file mode 100644
index 0000000000000000000000000000000000000000..789d2818b7737c0c5d79242575e01151aa008010
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/22-auditing/3-operation-audit.md
@@ -0,0 +1,161 @@
+---
+title: 操作审计
+summary: 操作审计
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 操作审计
+
+## audit_system_object
+
+**参数说明**: 该参数决定是否对MogDB数据库对象的CREATE、DROP、ALTER操作进行审计。MogDB数据库对象包括DATABASE、USER、schema、TABLE等。通过修改该配置参数的值，可以只审计需要的数据库对象的操作。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，0～524287
+
+- 0代表关闭MogDB数据库对象的CREATE、DROP、ALTER操作审计功能。
+- 非0代表只审计MogDB的某类或者某些数据库对象的CREATE、DROP、ALTER操作。
+
+**取值说明**:
+
+该参数的值由20个二进制位的组合求出，这20个二进制位分别代表MogDB的20类数据库对象。如果对应的二进制位取值为0，表示不审计对应的数据库对象的CREATE、DROP、ALTER操作；取值为1，表示审计对应的数据库对象的CREATE、DROP、ALTER操作。这19个二进制位代表的具体审计内容请参见[表1](#audit_system_object)。
+
+**默认值**: 12295
+
+**表 1** audit_system_object取值含义说明<a id="audit_system_object"> </a>
+
+| <span style="white-space:nowrap;">二进制位 </span> | 含义                                                         | 取值说明                                                     |
+| -------------------------------------------------- | ------------------------------------------------------------ | ------------------------------------------------------------ |
+| 第0位                                              | 是否审计DATABASE对象的CREATE、DROP、ALTER操作。              | - 0表示不审计该对象的CREATE、DROP、ALTER操作；<br />- 1表示审计该对象的CREATE、DROP、ALTER操作。 |
+| 第1位                                              | 是否审计SCHEMA对象的CREATE、DROP、ALTER操作。                | - 0表示不审计该对象的CREATE、DROP、ALTER操作；<br />- 1表示审计该对象的CREATE、DROP、ALTER操作。 |
+| 第2位                                              | 是否审计USER对象的CREATE、DROP、ALTER操作。                  | - 0表示不审计该对象的CREATE、DROP、ALTER操作；<br />- 1表示审计该对象的CREATE、DROP、ALTER操作。 |
+| 第3位                                              | 是否审计TABLE对象的CREATE、DROP、ALTER、TRUNCATE操作。       | - 0表示不审计该对象的CREATE、DROP、ALTER、TRUNCATE操作；<br />- 1表示审计该对象的CREATE、DROP、ALTER、TRUNCATE操作。 |
+| 第4位                                              | 是否审计INDEX对象的CREATE、DROP、ALTER操作。                 | - 0表示不审计该对象的CREATE、DROP、ALTER操作；<br />- 1表示审计该对象的CREATE、DROP、ALTER操作。 |
+| 第5位                                              | 是否审计VIEW对象的CREATE、DROP操作。                         | - 0表示不审计该对象的CREATE、DROP操作；<br />- 1表示审计该对象的CREATE、DROP操作。 |
+| 第6位                                              | 是否审计TRIGGER对象的CREATE、DROP、ALTER操作。               | - 0表示不审计该对象的CREATE、DROP、ALTER操作；<br />- 1表示审计该对象的CREATE、DROP、ALTER操作。 |
+| 第7位                                              | 是否审计PROCEDURE/FUNCTION对象的CREATE、DROP、ALTER操作。    | - 0表示不审计该对象的CREATE、DROP、ALTER操作；<br />- 1表示审计该对象的CREATE、DROP、ALTER操作。 |
+| 第8位                                              | 是否审计TABLESPACE对象的CREATE、DROP、ALTER操作。            | - 0表示不审计该对象的CREATE、DROP、ALTER操作；<br />- 1表示审计该对象的CREATE、DROP、ALTER操作。 |
+| 第9位                                              | 是否审计RESOURCE POOL对象的CREATE、DROP、ALTER操作。         | - 0表示不审计该对象的CREATE、DROP、ALTER操作；<br />- 1表示审计该对象的CREATE、DROP、ALTER操作 |
+| 第10位                                             | 是否审计WORKLOAD对象的CREATE、DROP、ALTER操作。              | - 0表示不审计该对象的CREATE、DROP、ALTER操作；<br />- 1表示审计该对象的CREATE、DROP、ALTER操作 |
+| 第11位                                             | 是否审计SERVER FOR HADOOP对象的CREATE、DROP、ALTER操作。     | - 0表示不审计该对象的CREATE、DROP、ALTER操作；<br />- 1表示审计该对象的CREATE、DROP、ALTER操作 |
+| 第12位                                             | 是否审计DATA SOURCE对象的CRAETE、DROP、ALTER操作。           | - 0表示不审计该对象的CREATE、DROP、ALTER操作；<br />- 1表示审计该对象的CREATE、DROP、ALTER操作。 |
+| 第13位                                             | 是否审计NODE GROUP对象的CREATE、DROP操作。                   | - 0表示不审计该对象的CREATE、DROP操作；<br />- 1表示审计该对象的CREATE、DROP操作。 |
+| 第14位                                             | 是否审计ROW LEVEL SECURITY对象的CREATE、DROP、ALTER操作。    | - 0表示不审计该对象的CREATE、DROP、ALTER操作；<br />- 1表示审计该对象的CREATE、DROP、ALTER操作。 |
+| 第15位                                             | 是否审计TYPE对象的CREATE、DROP、ALTER操作。                  | - 0表示不审计TYPE对象的CREATE、DROP、ALTER操作；<br />- 1表示审计TYPE对象的CREATE、DROP、ALTER操作。 |
+| 第16位                                             | 是否审计TEXT SEARCH对象（CONFIGURATION和DICTIONARY）的CREATE、DROP、ALTER操作。 | - 0表示不审计TEXT SEARCH对象的CREATE、DROP、ALTER操作；<br />- 1表示审计TEXT SEARCH对象的CREATE、DROP、ALTER操作。 |
+| 第17位                                             | 是否审计DIRECTORY对象的CREATE、DROP、ALTER操作。             | - 0表示不审计DIRECTORY对象的CREATE、DROP、ALTER操作；<br />- 1表示审计DIRECTORY对象的CREATE、DROP、ALTER操作。 |
+| 第18位                                             | 是否审计SYNONYM对象的CREATE、DROP、ALTER操作。               | - 0表示不审计SYNONYM对象的CREATE、DROP、ALTER操作；<br />- 1表示审计SYNONYM对象的CREATE、DROP、ALTER操作。 |
+| 第19位                                             | 是否审计SEQUENCE对象的CREATE、DROP、ALTER操作。              | - 0表示不审计SEQUENCE对象的CREATE、DROP、ALTER操作；<br />- 1表示审计SEQUENCE对象的CREATE、DROP、ALTER操作。 |
+| 第20位                                             | 是否审计CMK、CEK对象的CREATE、DROP操作。                     | - 0表示不审计CMK、CEK对象的CREATE、DROP操作；<br />- 1表示审计CMK、CEK对象的CREATE、DROP操作。 |
+
+## audit_dml_state
+
+**参数说明**: 这个参数决定是否对具体表的INSERT、UPDATE、DELETE操作进行审计。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，0、1。
+
+- 0表示关闭具体表的DML操作（SELECT除外）审计功能。
+- 1表示开启具体表的DML操作（SELECT除外）审计功能。
+
+**默认值**: 0
+
+## audit_dml_state_select
+
+**参数说明**: 这个参数决定是否对SELECT操作进行审计。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，0、1。
+
+- 0表示关闭SELECT操作审计功能。
+- 1表示开启SELECT审计操作功能。
+
+**默认值**: 0
+
+## audit_function_exec
+
+参数说明:这个参数决定在执行存储过程、匿名块或自定义函数（不包括系统自带函数）时是否记录审计信息。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，0、1。
+
+- 0表示关闭过程或函数执行的审计功能。
+- 1表示开启过程或函数执行的审计功能。
+
+**默认值**: 0
+
+## audit_copy_exec
+
+**参数说明**: 这个参数决定是否对COPY操作进行审计。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，0、1。
+
+- 0表示关闭COPY审计功能。
+- 1表示开启COPY审计功能。
+
+**默认值**: 0
+
+## audit_set_parameter
+
+**参数说明**: 这个参数决定是否对SET操作进行审计。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，0、1。
+
+- 0表示关闭SET审计功能。
+- 1表示开启SET审计功能。
+
+**默认值**: 1
+
+## enableSeparationOfDuty
+
+**参数说明**: 是否开启三权分立选项。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示开启三权分立。
+- off表示不开启三权分立。
+
+**默认值**: off
+
+## enable_nonsysadmin_execute_direct
+
+**参数说明**: 是否允许非系统管理员执行EXECUTE DIRECT ON语句。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示允许任意用户执行EXECUTE DIRECT ON语句。
+- off表示只允许系统管理员执行EXECUTE DIRECT ON语句。
+
+**默认值**: off
+
+## enable_access_server_directory
+
+**参数说明**: 是否开启非初始用户创建、修改和删除DIRECTORY的权限。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示开启非初始用户创建、修改和删除DIRECTORY的权限。
+- off表示不开启非初始用户创建、修改和删除DIRECTORY的权限。
+
+**默认值**: off
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+>
+> - 出于安全考虑，默认情况下，只有初始用户才能够创建、修改和删除DIRECTORY对象。
+>
+> - 如果开启了enable_access_server_directory，具有SYSADMIN权限的用户和继承了内置角色gs_role_directory_create权限的用户可以创建directory对象；具有SYSADMIN权限的用户、directory对象的属主、被授予了该directory的DROP权限的用户或者继承了内置角色gs_role_directory_drop权限的用户可以删除directory对象；具有SYSADMIN权限的用户和directory对象的属主可以修改directory对象的所有者，且要求该用户是新属主的成员。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/23-upgrade-parameters.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/23-upgrade-parameters.md
new file mode 100644
index 0000000000000000000000000000000000000000..9780d6e605bfbd37f1c55ad08c0bc83bb3864627
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/23-upgrade-parameters.md
@@ -0,0 +1,43 @@
+---
+title: 升级参数
+summary: 升级参数
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 升级参数
+
+## IsInplaceUpgrade
+
+**参数说明**: 标示是否在升级的过程中。该参数用户无法修改。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示在升级过程中。
+- off表示不在升级过程中。
+
+**默认值**: off
+
+## inplace_upgrade_next_system_object_oids
+
+**参数说明**: 标示就地升级过程中，新增系统对象的OID。该参数用户无法修改。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串
+
+**默认值**: 空
+
+## upgrade_mode
+
+**参数说明**: 标示升级模式。该参数不建议用户自己修改。
+
+**取值范围:**整数，0~INT_MAX
+
+- 0表示不在升级过程中。
+- 1表示在就地升级过程中。
+- 2表示在灰度升级过程中。
+
+**默认值**: 0
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/24-miscellaneous-parameters.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/24-miscellaneous-parameters.md
new file mode 100644
index 0000000000000000000000000000000000000000..7d9d198b1f120b314105bd730933f8b4f7a97afc
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/24-miscellaneous-parameters.md
@@ -0,0 +1,204 @@
+---
+title: 其它选项
+summary: 其它选项
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 其它选项
+
+## enable_default_ustore_table
+
+**参数说明**: 指定是否开启默认支持Ustore存储引擎。该参数为on时，创建的表类型都为Ustore表。
+
+该参数属于USERSET类型，请参考表[GUC参数分类](30-appendix)对应设置方法进行设置。
+
+**取值范围**: [off,on]
+
+**默认值**: off
+
+## reserve_space_for_nullable_atts
+
+**参数说明**: 指定是否为Ustore表的可空属性预留空间。该参数为on时默认为Ustore表的可空属性预留空间。
+
+该参数属于USERSET类型，请参考表[GUC参数分类](30-appendix)对应设置方法进行设置。
+
+**取值范围**: [off,on]
+
+**默认值**: off
+
+## ustore_attr
+
+**参数说明**: Ustore测试参数。
+
+该参数属于USERSET类型，可以设置包括enable_ustore_partial_seqscan（仅在ustore表中顺序扫描时复制选择性列），enable_candidate_buf_usage_count（是否脏页淘汰加入使用次数权重），ustats_tracker_naptime（重新加载统计文件所用的时间），umax_search_length_for_prune（扩展表前要修剪的块数），ustore_unit_test（开启Ustore白盒测试），设置方法为 ustore_att='需要设置的参数'，例如需要设置enable_ustore_partial_seqscan时，ustore_attr='enable_ustore_partial_seqscan=on'。
+
+**取值范围**: 字符串
+
+## server_version
+
+**参数说明**: 报告服务器版本号（字符串形式）。
+
+该参数属于INTERNAL类型参数，为固定参数，用户无法修改此参数，只能查看。该参数继承自PostgreSQL内核，表示当前数据库内核兼容PostgreSQL对应的server_version版本，无实际含义，为保持北向对外工具接口的生态兼容性（工具连接时查询），保留该参数。该参数不推荐使用，如想查询服务器版本号，可通过函数opengauss_version()获取。
+
+**取值范围:** 字符串
+
+**默认值**:  9.2.4
+
+## server_version_num
+
+**参数说明**: 报告服务器版本号（整数形式）。
+
+该参数属于INTERNAL类型参数，为固定参数，用户无法修改此参数，只能查看。该参数继承自PostgreSQL内核，表示当前数据库内核兼容PostgreSQL对应的server_version_num版本，无实际含义，为保持北向对外工具接口的生态兼容性（工具连接时查询），保留该参数。
+
+**取值范围:**整数
+
+**默认值**: 90204
+
+## block_size
+
+**参数说明**: 报告当前数据库所使用的块大小。
+
+该参数属于INTERNAL类型参数，为固定参数，用户无法修改此参数，只能查看。
+
+**取值范围:**8192
+
+**默认值**: 8192
+
+## segment_size
+
+**参数说明**: 报告当前数据库所使用的段文件大小。
+
+该参数属于INTERNAL类型参数，为固定参数，用户无法修改此参数，只能查看。
+
+**单位**: 8KB
+
+**默认值**: 131072, 即1GB
+
+## max_index_keys
+
+**参数说明**: 报告当前数据库能够支持的索引键值的最大数目。
+
+该参数属于INTERNAL类型参数，为固定参数，用户无法修改此参数，只能查看。
+
+**默认值**: 32
+
+## integer_datetimes
+
+**参数说明**: 报告是否支持64位整数形式的日期和时间格式。
+
+该参数属于INTERNAL类型参数，为固定参数，用户无法修改此参数，只能查看。
+
+**取值范围:**布尔型
+
+- on表示支持。
+- off表示不支持。
+
+**默认值**: on
+
+## lc_collate
+
+**参数说明**: 报告当前数据库的字符串排序区域设置。
+
+该参数属于INTERNAL类型参数，为固定参数，用户无法修改此参数，只能查看。
+
+**默认值**: 依赖于MogDB安装部署时的配置
+
+## lc_ctype
+
+**参数说明**: 报告当前数据库的字母类别区域设置。如: 哪些字符属于字母，它对应的大写形式是什么。
+
+该参数属于INTERNAL类型参数，为固定参数，用户无法修改此参数，只能查看。
+
+**默认值**: 依赖于MogDB安装部署时的配置
+
+## max_identifier_length
+
+**参数说明**: 报告当前系统允许的标识符最大长度。
+
+该参数属于INTERNAL类型参数，为固定参数，用户无法修改此参数，只能查看。
+
+**取值范围:**整型
+
+**默认值**: 63
+
+## server_encoding
+
+**参数说明**: 报告当前数据库的服务端编码字符集。
+
+默认情况下，gs_initdb会根据当前的系统环境初始化此参数，通过locale命令可以查看当前的配置环境。
+
+该参数属于INTERNAL类型参数，为固定参数，用户无法修改此参数，只能查看。
+
+**默认值**: 在创建数据库的时候由当前系统环境决定的。
+
+## enable_upgrade_merge_lock_mode
+
+**参数说明**: 当该参数设置为on时，通过提升deltamerge内部实现的锁级别，避免和update/delete并发操作时的报错。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:** 布尔型
+
+- on，提升deltamerge内部实现的锁级别，并发执行deltamerge和update/delete操作时，一个操作先执行，另一个操作被阻塞，在前一个操作完成后，后一个操作再执行。
+- off，在对表的delta table的同一行并发执行deltamerge和update/delete操作时，后一个对同一行数据更新的操作会报错退出。
+
+**默认值**: off
+
+## transparent_encrypted_string
+
+**参数说明**: 它存储的是透明加密的一个样本串，使用数据库加密密钥加密固定串"TRANS_ENCRYPT_SAMPLE_STRING"后的密文，用来校验二次启动时获取的DEK是否正确。如果校验失败，那么数据库节点将拒绝启动。该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串，设置为空表示MogDB非加密。
+
+**默认值**: 空
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:** 请勿手动设置该参数，设置不当将导致MogDB不可用。
+
+## transparent_encrypt_kms_url
+
+**参数说明**: 它存储的是透明加密的数据库密钥获取地址，内容要求不可出现RFC3986标准外的字符，最大长度2047字节。格式为"kms://协议@KMS主机名1;KMS主机名2:KMS端口号/kms"，例如 kms://https@linux175:29800/。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串
+
+**默认值**: 空
+
+## transparent_encrypt_kms_region
+
+**参数说明**: 它存储的是MogDB的部署区域，内容要求不可出现RFC3986标准外的字符，最大长度2047字节。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串
+
+**默认值**: 空
+
+## basebackup_timeout
+
+**参数说明**: 备份传输完成后连接无读写的超时时间。 通过gs_basebackup工具作传输时，如果指定较高压缩率时，可能在传输表空间完成后超时（客户端需要压缩传输数据）。
+
+**取值范围**: 整型，0 ~ INT_MAX，单位为秒。其中0表示禁用该功能。
+
+**默认值**:  600s
+
+## datanode_heartbeat_interval
+
+**参数说明**: 设置心跳线程间心跳消息发送时间间隔，建议值不超过wal_receiver_timeout / 2。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，1000～60000（毫秒）
+
+**默认值**: 1s
+
+## max_concurrent_autonomous_transactions
+
+**参数说明**：自治事务最大链接数，同一时间自治事务执行的最大并发数。当设置为0时，将无法执行自治事务。
+
+该参数属于INTERNAL类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：0-1024
+
+**默认值**：10
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/25-wait-events.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/25-wait-events.md
new file mode 100644
index 0000000000000000000000000000000000000000..e50c3c56bbc44c15a52ae8b7fae193c5c3bbe1cd
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/25-wait-events.md
@@ -0,0 +1,21 @@
+---
+title: 等待事件
+summary: 等待事件
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 等待事件
+
+## enable_instr_track_wait
+
+**参数说明**: 是否开启等待事件信息实时收集功能。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on: 表示打开等待事件信息收集功能。
+- off: 表示关闭等待事件信息收集功能。
+
+**默认值**: on
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/26-query.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/26-query.md
new file mode 100644
index 0000000000000000000000000000000000000000..b4fd3418170043c61339ae0fc7f846465d007aa9
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/26-query.md
@@ -0,0 +1,181 @@
+---
+title: Query
+summary: Query
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# Query
+
+## instr_unique_sql_count
+
+**参数说明**: 控制系统中unique sql信息实时收集功能。配置为0表示不启用unique sql信息收集功能。
+
+该值由大变小将会清空系统中原有的数据重新统计；从小变大不受影响。
+
+当系统中产生的unique sql条目数量大于instr_unique_sql_count时，若开启了unique sql自动淘汰，则系统会按unique sql的更新时间由远到近自动淘汰一定比例的条目，使得新产生的unique sql信息可以继续被统计。若没有开启自动淘汰，则系统产生的新的unique sql信息将不再被统计。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：整型，0~2147483647
+
+**默认值**：100
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **注意：**
+>
+> - 在开启自动淘汰的情况下，如果该值设置的较小，可能会导致系统频繁的进行自动淘汰，有可能会影响数据库系统性能，所以实际场景中建议不要将该值设置的过小，建议值为200000。
+>
+> - 在开启自动淘汰的情况下，如果该值设置的较大（例如38347922），清理过程中可能会引发大内存问题而无法清理。
+
+## instr_unique_sql_track_type
+
+**参数说明**: unique sql记录SQL方式。
+
+该参数属于INTERNAL类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 枚举类型
+
+top：只记录顶层SQL。
+
+**默认值**：top
+
+## enable_instr_rt_percentile
+
+**参数说明**: 是否开启计算系统中80%和95%的SQL响应时间的功能。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on：表示打开sql响应时间信息计算功能。
+- off：表示关闭sql响应时间信息计算功能。
+
+**默认值**：on
+
+## percentile
+
+**参数说明**: sql响应时间百分比信息，后台计算线程根据设置的值计算相应的百分比信息。
+
+该参数属于INTERNAL类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串。
+
+**默认值**：80,95
+
+## instr_rt_percentile_interval
+
+**参数说明**: sql响应时间信息计算间隔，sql响应时间信息计算功能打开后，后台计算线程每隔设置的时间进行一次计算。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，0～3600（秒）。
+
+**默认值**：10s
+
+## enable_instr_cpu_timer
+
+**参数说明**: 是否捕获sql执行的cpu时间消耗 。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on：表示捕获sql执行的cpu时间消耗。
+- off：表示不捕获sql执行的cpu时间消耗。
+
+**默认值**：on
+
+## enable_stmt_track
+
+**参数说明**: 控制是否启用Full /Slow SQL特性。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on：表示开启Full /Slow SQL捕获。
+- off：表示关闭Full /Slow SQL捕获。
+
+**默认值**: on
+
+## track_stmt_session_slot
+
+**参数说明**: 设置一个session缓存的最大的全量/慢SQL的数量，超过这个数量，新的语句执行将不会被跟踪，直到落盘线程将缓存语句落盘，留出空闲的空间。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，0 ~ 2147483647
+
+**默认值**: 1000
+
+## track_stmt_details_size
+
+**参数说明**: 设置单语句可以收集的最大的执行事件的大小（byte）。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，0 ~ 100000000
+
+**默认值**: 4096
+
+## track_stmt_retention_time
+
+**参数说明**: 组合参数，控制全量/慢SQL记录的保留时间。以60秒为周期读取该参数，并执行清理超过保留时间的记录，仅sysadmin用户可以访问。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符型
+
+该参数分为两部分，形式为'full sql retention time, slow sql retention time'
+
+full sql retention time为全量SQL保留时间，取值范围为0 ~ 86400
+
+slow sql retention time为慢SQL的保留时间，取值范围为0 ~ 604800
+
+**默认值**: 3600,604800
+
+## track_stmt_stat_level
+
+**参数说明**: 控制语句执行跟踪的级别。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置，不区分英文字母大小写。
+
+**取值范围**: 字符型
+
+该参数分为两部分，形式为'full sql stat level, slow sql stat level'
+
+第一部分为全量SQL跟踪级别，取值范围为OFF、L0、L1、L2
+
+第二部分为慢SQL的跟踪级别，取值范围为OFF、L0、L1、L2
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 若全量SQL跟踪级别值为非OFF时，当前SQL跟踪级别值为全量SQL和慢SQL的较高级别（L2 &gt; L1 &gt; L0），级别说明请参见表[GUC参数分类](30-appendix)。
+
+**默认值**: OFF,L0
+
+## unique_sql_clean_ratio
+
+**参数说明**: 当系统中产生的unique sql条目数量大于等于instr_unique_sql_count时，每次自动淘汰的unique sql条目数量占总条目数量预设上限instr_unique_sql_count的比例。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: double类型，0~0.2
+
+**默认值**: 0.1
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **注意：**
+>
+> - 该值设置过小每次清理的条目较少，可能会导致频繁进行清理；设置过大时每次清理的条目较多，可能会导致频繁插入。建议值0.1。
+>
+> - unique_sql_clean_ratio设置为0不代表关闭自动淘汰功能，请通过enable_auto_clean_unique_sql来控制是否开启自动淘汰。当开启自动淘汰，且将unique_sql_clean_ratio设置为0时，将自动把unique_sql_clean_ratio重置为默认值0.1。
+
+## enable_auto_clean_unique_sql
+
+**参数说明**: 当系统中产生的unique sql条目数量大于等于instr_unique_sql_count时，是否启用unique sql自动淘汰功能。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+**默认值**: off
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **注意：** 由于快照有部分信息是来源于unique sql，所以开启自动淘汰的情况下，在生成wdr报告时，如果选择的起始快照和终止快照跨过了淘汰发生的时间，会导致无法生成wdr报告。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/27-system-performance-snapshot.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/27-system-performance-snapshot.md
new file mode 100644
index 0000000000000000000000000000000000000000..93fb5c673a48df8e221fd87d7447e83449d1ff20
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/27-system-performance-snapshot.md
@@ -0,0 +1,124 @@
+---
+title: 系统性能快照
+summary: 系统性能快照
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 系统性能快照
+
+## enable_wdr_snapshot
+
+**参数说明**: 是否开启数据库监控快照功能。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on: 打开数据库监控快照功能。
+- off: 关闭数据库监控快照功能。
+
+**默认值**: off
+
+## wdr_snapshot_retention_days
+
+**参数说明**: 系统中数据库监控快照数据的保留天数，超过设置的值之后，系统每隔wdr_snapshot_interval时间间隔，清理snapshot_id最小的快照数据。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，1～8。
+
+**默认值**: 8
+
+## wdr_snapshot_query_timeout
+
+**参数说明**: 系统执行数据库监控快照操作时，设置快照操作相关的sql语句的执行超时时间。如果语句超过设置的时间没有执行完并返回结果，则本次快照操作失败。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，100～INT_MAX（秒）。
+
+**默认值**: 100s
+
+## wdr_snapshot_interval
+
+**参数说明**: 后台线程Snapshot自动对数据库监控数据执行快照操作的时间间隔。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，10～60（分钟）。
+
+**默认值**: 1h
+
+## asp_flush_mode
+
+**参数说明**: ASP刷新到磁盘上的方式分为写文件和写系统表，当为‘file’时，默认写文件，为‘table’时写系统表，为‘all’时，即写文件也写系统表，仅sysadmin用户可以访问。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串，‘table’、‘file’、‘all’。
+
+**默认值**：‘table’
+
+## asp_flush_rate
+
+**参数说明**: 当内存中样本个数达到asp_sample_num时，会按一定比例把内存中样本刷新到磁盘上，asp_flush_rate为刷新比例。该参数为10时表示按10：1进行刷新。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，1~10。
+
+**默认值**：10
+
+## asp_log_filename
+
+**参数说明**: 当ASP写文件时，该参数设置文件名的格式，仅sysadmin用户可以访问。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串。
+
+**默认值**：“asp-%Y-%m-%d_%H%M%S.log”
+
+## asp_retention_days
+
+**参数说明**: 当ASP样本写到系统表时，该参数表示保留的最大天数。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，1~7。
+
+**默认值**：2
+
+## asp_sample_interval
+
+**参数说明**: 每次采样的间隔。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，1~10，单位为秒。
+
+**默认值**：1s
+
+## asp_sample_num
+
+**参数说明**: LOCAL_ACTIVE_SESSION视图最大的样本个数，仅sysadmin用户可以访问。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，10000～100000。
+
+**默认值**：100000
+
+## enable_asp
+
+**参数说明**: 是否开启活跃会话信息active session profile。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on：打开active session profile功能。
+- off：关闭active session profile功能。
+
+**默认值**：on
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/27.1-security-configuration.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/27.1-security-configuration.md
new file mode 100644
index 0000000000000000000000000000000000000000..f6ee251f47b729ff7e995a6dab548421e21c716d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/27.1-security-configuration.md
@@ -0,0 +1,84 @@
+---
+title: 安全配置
+summary: 安全配置
+author: Zhang Cuiping
+date: 2021-11-08
+---
+
+# 安全配置
+
+## elastic_search_ip_addr
+
+**参数说明**: Elastic Search系统IP地址。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串。
+
+**默认值**：'https:127.0.0.1'
+
+## enable_security_policy
+
+**参数说明**: 安全策略开关，控制统一审计和数据动态脱敏策略是否生效。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型。
+
+on：安全策略开关打开。
+
+off：安全策略开关关闭。
+
+**默认值**：off
+
+## use_elastic_search
+
+**参数说明**: 使能统一审计发送日志至Elastic Search系统, enable_security_policy打开且本参数打开后，统一审计日志会通过http(https)传递至Elastic Search系统（默认使用https安全协议）。此参数打开后需要保证elastic_search_ip_addr对应的es服务可正常连通，否则进程启动失败。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型。
+
+on：使能统一审计日志发送至Elastic Search。
+
+off：关闭统一审计日志发送至Elastic Search。
+
+**默认值**：off
+
+## is_sysadmin
+
+**参数说明**: 表示当前用户是否是初始用户。
+
+该参数属于INTERNAL类型参数，为固定参数，用户无法修改此参数，只能查看。
+
+**取值范围**: 布尔型。
+
+on表示是初始用户。
+
+off表示不是初始用户。
+
+**默认值**：off
+
+## enable_tde
+
+**参数说明**: 透明数据加密功能开关。创建加密表前需要将此参数置为on。当前参数值为off时，禁止创建新的加密表，对于已经创建的加密表只在读取数据时解密，写入数据时不再加密。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型。
+
+on：开启透明数据加密功能。
+
+off：关闭透明数据加密功能。
+
+**默认值**：off
+
+## tde_cmk_id
+
+**参数说明**: 透明数据加密功能使用的数据库实例主密钥CMK的ID编号，由使用的密钥管理服务KMS生成。数据库实例主密钥CMK用于对数据加密密钥DEK进行加密保护，当前需要对DEK进行解密时，需要给KMS发起请求报文，将DEK密文和对应CMK的ID编号一起发送给KMS。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串。
+
+**默认值**：””
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/28-equality-query-in-a-fully-encrypted-database.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/28-equality-query-in-a-fully-encrypted-database.md
new file mode 100644
index 0000000000000000000000000000000000000000..44d9608450c8c1352955485846fb6a3a7c005942
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/28-equality-query-in-a-fully-encrypted-database.md
@@ -0,0 +1,23 @@
+---
+title: 全密态数据库支持等值查询
+summary: 全密态数据库支持等值查询
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 全密态数据库支持等值查询
+
+## enable_full_encryption
+
+**参数说明**: 全密态数据库开关，控制全密态数据库是否生效。
+
+该参数属于BACKEND类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+enable_full_encryption设置为on后，使用gsql连接数据库时需要输入"-C"参数，或"-enable-client-encryption"，否则连接不成功。
+
+**取值范围:**布尔型
+
+- on: 全密态数据库开关打开。
+- off: 全密态数据库开关关闭。
+
+**默认值**: off
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/29-global-temporary-table.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/29-global-temporary-table.md
new file mode 100644
index 0000000000000000000000000000000000000000..740311c804f31e099465d5ac129a4be1f92b5978
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/29-global-temporary-table.md
@@ -0,0 +1,31 @@
+---
+title: 全局临时表
+summary: 全局临时表
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 全局临时表
+
+## max_active_global_temporary_table
+
+**参数说明**: 全局临时表功能开关，控制是否可以创建全局临时表。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，0 ~ 1000000
+
+- 0: 全局临时表功能关闭。
+- &gt; 0: 全局临时表功能打开。
+
+**默认值**: 1000
+
+## vacuum_gtt_defer_check_age
+
+**参数说明**: vacuum执行后检查全局临时表relfrozenxid与普通表的差异。如果全局临时表relfrozenxid落后超过指定参数值，就产生WARNING。一般不用修改。
+
+该参数USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，0 ~ 1000000
+
+**默认值**: 10000
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/29.1-HyperLogLog.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/29.1-HyperLogLog.md
new file mode 100644
index 0000000000000000000000000000000000000000..dd801b9374df402599c9e8bef7b68410a72c8859
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/29.1-HyperLogLog.md
@@ -0,0 +1,101 @@
+---
+title: HyperLogLog
+summary: HyperLogLog
+author: Zhang Cuiping
+date: 2021-11-08
+---
+
+# HyperLogLog
+
+## hll_default_log2m
+
+**参数说明**: 该参数可以指定hll数据结构桶的个数。桶的个数会影响hll计算distinct值的精度，桶的个数越多，误差越小。误差范围为：[-1.04/2log2m\*1⁄2,+1.04/2log2m*1⁄2]。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，10~16。
+
+**默认值**: 14
+
+## hll_default_log2explicit
+
+**参数说明**: 该参数可以用来设置从Explicit模式到Sparse模式的默认阈值大小。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，0~12。0表示跳过Explicit模式，取1-12表示在基数到达2hll_default_log2explicit时切换模式。
+
+**默认值**: 10
+
+## hll_default_log2sparse
+
+**参数说明**: 该参数可以用来设置从Sparse模式到Full模式的默认阈值大小。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，0~14。0表示跳过Explicit模式，取1-14表示在基数到达2hll_default_log2sparse时切换模式。
+
+**默认值**: 12
+
+## hll_duplicate_check
+
+**参数说明**: 该参数可以用来指定是否默认开启duplicatecheck。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 0，1。0表示默认关闭，1表示默认开启
+
+**默认值**: 0
+
+## hll_default_regwidth（废弃）
+
+**参数说明**: 该参数可以指定hll数据结构每个桶的位数，该值越大，hll所占内存越高。hll_default_regwidth和hll_default_log2m可以决定当前hll能够计算的最大distinct value。当前regwidth设为固定值，该参数不再使用。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，1~5。
+
+**默认值**: 5
+
+## hll_default_expthresh（废弃）
+
+**参数说明**: 该参数可以用来设置从Explicit模式到Sparse模式的默认阈值大小。当前已经使用参数hll_default_log2explicit替代类似功能。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，-1~7。-1表示自动模式，0表示跳过Explicit模式，取1-7表示在基数到达2hll_default_expthresh时切换模式。
+
+**默认值**: -1
+
+## hll_default_sparseon（废弃）
+
+**参数说明**: 该参数可用来指定是否默认开启Sparse模式。当前已经使用参数hll_default_log2sparse替代类似功能，hll_default_log2sparse设置为0时关闭Sparse模式。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 0，1。0表示默认关闭，1表示默认开启。
+
+**默认值**: 1
+
+## hll_max_sparse（废弃）
+
+**参数说明**: 该参数可以用来指定max_sparse的大小。当前已经使用参数hll_default_log2sparse替代类似功能。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，-1~2147483647
+
+**默认值**: -1
+
+## enable_compress_hll（废弃）
+
+**参数说明**: 该参数可以用来指定是否对hll开启内存优化模式。目前hll内存已经进行了优化设计，该参数不再使用。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on/true表示对hll开启内存优化模式。
+- off/false表示不开启内存优化模式。
+
+**默认值**: off
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/3-connection-and-authentication/1-connection-settings.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/3-connection-and-authentication/1-connection-settings.md
new file mode 100644
index 0000000000000000000000000000000000000000..c255db0b7231e2bdcfe26ba88d9deb296f1bd9a9
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/3-connection-and-authentication/1-connection-settings.md
@@ -0,0 +1,198 @@
+---
+title: 连接设置
+summary: 连接设置
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 连接设置
+
+介绍设置客户端和服务器连接方式相关的参数。
+
+## listen_addresses
+
+**参数说明**: 声明服务器侦听客户端的TCP/IP地址。
+
+该参数指定MogDB服务器使用哪些IP地址进行侦听，如IPV4或IPV6（若支持）。服务器主机上可能存在多个网卡，每个网卡可以绑定多个IP地址，该参数就是控制MogDB到底绑定在哪个或者哪几个IP地址上。而客户端则可以通过该参数中指定的IP地址来连接MogDB或者给MogDB发送请求。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**:
+
+- 主机名或IP地址，多个值之间用英文逗号分隔。
+- 星号`*`或`0.0.0.0`表示侦听所有IP地址。配置侦听所有IP地址存在安全风险，不推荐用户使用。必须与有效地址结合使用（比如本地IP等），否则，可能造成Build失败的问题。同时，主备环境下配置为`*`或`0.0.0.0`时，主节点数据库路径下postgresql.conf文件中的localport端口号不能为数据库dataPortBase+1，否则会导致数据库无法启动。
+- 置空则服务器不会侦听任何IP地址，这种情况下，只有Unix域套接字可以用于连接数据库。
+
+**默认值**: 数据库实例安装好后，根据XML配置文件中不同实例的IP地址配置不同默认值。DN的默认参数值为：listen_addresses = 'x.x.x.x'。
+
+## local_bind_address
+
+**参数说明**: 声明当前节点连接MogDB其他节点绑定的本地IP地址。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**默认值**: 数据库实例安装好后，根据XML配置文件中不同实例的IP地址配置不同默认值。DN的默认参数值为：local_bind_address = 'x.x.x.x'。。
+
+## port
+
+**参数说明**: MogDB服务侦听的TCP端口号。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> 该参数由安装时的配置文件指定，请勿轻易修改，否则修改后会影响数据库正常通信。
+>
+
+**取值范围**: 整型，1～65535
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 设置端口号时，请设置一个未被占用的端口号。设置多个实例的端口号，不可冲突。
+> - 1~1023为操作系统保留端口号，请不要使用。
+> - 通过配置文件安装数据库实例时，配置文件中的端口号需要注意通信矩阵预留端口。如：DN还需保留dataPortBase+1作为内部工具使用端口，保留dataPortBase+6作为流引擎消息队列通信端口等。故数据库实例安装阶段，port最大值为：DN可设置65529，同时需要保证端口号不冲突。
+
+**默认值**: 5432（实际值由安装时的配置文件指定）
+
+## max_connections
+
+**参数说明**: 允许和数据库连接的最大并发连接数。此参数会影响MogDB的并发能力。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型。最小值为10（要大于max_wal_senders），理论最大值为262143，实际最大值为动态值，计算公式为“262143 - job_queue_processes - autovacuum_max_workers - AUXILIARY_BACKENDS - AV_LAUNCHER_PROCS - max_inner_tool_connections”。job_queue_processes、autovacuum_max_workers和max_inner_tool_connections的值取决于对应GUC参数的设置。AUXILIARY_BACKENDS为预留辅助线程数，固定为20，AV_LAUNCHER_PROCS为预留autovacuum的lancher线程数，固定为2。
+
+**默认值**: 200
+
+**设置建议：**
+
+数据库主节点中此参数建议保持默认值。
+
+当修改此默认值时，请同时修改undo_zone_count取值，具体设置原则请参见[undo章节](35-undo)。
+
+**配置不当时影响：**
+
+- 若配置max_connections过大，超过计算公式所描述的最大动态值，会出现节点拉起失败问题，报错提示“invalid value for parameter “max_connections””。
+- 若未按照对外出口规格配置仅调大max_connections参数值，未同比例调整内存参数。业务压力大时，容易出现内存不足，报错提示“memory is temporarily unavailable”。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 对于管理员用户的连接数限制会略超过max_connections设置，目的是为了让管理员在链接被普通用户占满后仍可以连接上数据库，再超过一定范围（sysadmin_reserved_connections参数）后才会报错。即管理员用户的最大连接数等于max_connections + sysadmin_reserved_connections。
+> - 对于普通用户来说，由于内部作业也会使用一些链接，因此会略小于max_connections，具体值取决于内部链接个数。
+
+## max_inner_tool_connections
+
+**参数说明**: 允许和数据库连接的工具的最大并发连接数。此参数会影响MogDB的工具连接并发能力。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，最小值为1，最大值为MIN(262143, max_connections)，max_connections的计算方法见上文。
+
+**默认值**: 数据库节点为50。如果该默认值超过内核支持的最大值（在执行gs_initdb的时候判断），系统会提示错误。
+
+**设置建议：**
+
+数据库主节点中此参数建议保持默认值。
+
+增大此参数可能导致MogDB要求更多的SystemV共享内存或者信号量，可能超过操作系统缺省配置的最大值。这种情况下，请酌情对数值加以调整。
+
+## sysadmin_reserved_connections
+
+**参数说明**: 为管理员用户预留的最少连接数, 不建议设置过大。该参数和max_connections参数配合使用，管理员用户的最大连接数等于max_connections+sysadmin_reserved_connections。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，最小值为0，最大值为MIN(262143, max_connections)，max_connections的计算方法见上文。
+
+**默认值**: 3
+
+## unix_socket_directory
+
+**参数说明**: 设置MogDB服务器侦听客户端连接的Unix域套接字目录。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+该参数的长度限制于操作系统的长度，超过该限制将会导致Unix-domain socket path "xxx" is too long的问题。
+
+**取值范围**: 字符串
+
+**默认值**: 空字符串（实际值由安装时配置文件指定）
+
+## unix_socket_group
+
+**参数说明**: 设置Unix域套接字的所属组（套接字的所属用户总是启动服务器的用户）。可以与选项[unix_socket_permissions](#unix_socket_permissions)一起用于对套接字进行访问控制。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串，其中空字符串表示当前用户的缺省组。
+
+**默认值**: 空字符串
+
+## unix_socket_permissions
+
+**参数说明**: 设置Unix域套接字的访问权限。
+
+Unix域套接字使用普通的Unix文件系统权限集。这个参数的值应该是数值的格式（chmod和umask命令可接受的格式）。如果使用自定义的八进制格式，数字必须以0开头。
+
+建议设置为0770（只有当前连接数据库的用户和同组的人可以访问）或者0700（只有当前连接数据库的用户自己可以访问，同组或者其他人都没有权限）。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 0000-0777
+
+**默认值**: 0777
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> 在Linux中，文档具有十个属性，其中第一个属性为文档类型，后面九个为权限属性，分别为Owner，Group及Others这三个组别的read、write、execute属性。 文档的权限属性分别简写为r，w，x，这九个属性三个为一组，也可以使用数字来表示文档的权限，对照表如下：
+>
+> r： 4
+>
+> w： 2
+>
+> x： 1
+>
+> -： 0
+>
+> 同一组（owner/group/others）的三个属性是累加的。
+>
+> 例如，-rwxrwx-表示这个文档的权限为：
+>
+> owner = rwx = 4+2+1 = 7
+>
+> group = rwx = 4+2+1 = 7
+>
+> others = - = 0+0+0 = 0
+>
+> 所以其权限为0770。
+
+## application_name
+
+**参数说明**: 当前连接请求当中，所使用的客户端名称。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串。
+
+**默认值**: 空字符串（连接到后端的应用名，以实际安装为准）
+
+## connection_info
+
+**参数说明**: 连接数据库的驱动类型、驱动版本号、当前驱动的部署路径和进程属主用户。
+
+该参数属于USERSET类型参数，属于运维类参数，不建议用户设置。
+
+**取值范围**: 字符串。
+
+**默认值**: 空字符串**。**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 空字符串，表示当前连接数据库的驱动不支持自动设置connection_info参数或应用程序未设置。
+> - 驱动连接数据库的时候自行拼接的connection_info参数格式如下：
+>
+> ```sql
+> {"driver_name"："ODBC","driver_version"： "(MogDB 2.1.1 build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr","driver_path"："/usr/local/lib/psqlodbcw.so","os_user"："omm"}
+> ```
+>
+> 默认显示driver_name和driver_version，driver_path和os_user的显示由用户控制。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/3-connection-and-authentication/2-security-and-authentication.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/3-connection-and-authentication/2-security-and-authentication.md
new file mode 100644
index 0000000000000000000000000000000000000000..2413f38faa920e1de0954d7b2d3daefa5c2b90fb
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/3-connection-and-authentication/2-security-and-authentication.md
@@ -0,0 +1,402 @@
+---
+title: 安全和认证（postgresql.conf）
+summary: 安全和认证（postgresql.conf）
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 安全和认证（postgresql.conf）
+
+介绍设置客户端和服务器的安全认证方式的相关参数。
+
+## authentication_timeout
+
+**参数说明**: 完成客户端认证的最长时间。如果一个客户端没有在这段时间里完成与服务器端的认证，则服务器自动中断与客户端的连接，这样就避免了出问题的客户端无限制地占用连接数。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，最小值为1，最大值为600，最小单位为s。
+
+**默认值**: 1min
+
+## auth_iteration_count
+
+**参数说明**: 认证加密信息生成过程中使用的迭代次数。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，2048-134217728。
+
+**默认值**: 10000
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> 迭代次数设置过小会降低口令存储的安全性，设置过大会导致认证、用户创建等涉及口令加密的场景性能劣化，请根据实际硬件条件合理设置迭代次数，推荐采用默认迭代次数。
+
+## session_authorization
+
+**参数说明**: 当前会话的用户标识。
+
+该参数属于USERSET类型参数，此参数为内部参数，只能通过[SET SESSION AUTHORIZATION](130-SET-SESSION-AUTHORIZATION)语法设置，不支持直接设置。
+
+**取值范围**: 字符串。
+
+**默认值**: NULL
+
+## session_timeout
+
+**参数说明**: 表明与服务器建立链接后，不进行任何操作的最长时间。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，0-86400，最小单位为s，0表示关闭超时设置。
+
+**默认值**: 10min
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> MogDB gsql客户端中有自动重连机制，所以针对初始化用户本地连接，超时后gsql表现的现象为断开后重连。
+
+## ssl
+
+**参数说明**: 启用SSL连接。请在使用这个选项之前阅读**使用gsql连接**。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示启用SSL连接。
+- off表示不启用SSL连接。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> MogDB目前支持SSL的场景为客户端连接数据库主节点场景，该参数目前建议只在数据库主节点中开启，数据库节点默认值为off。开启此参数需要同时配置ssl_cert_file、ssl_key_file和ssl_ca_file等参数及对应文件，不正确的配置可能会导致MogDB无法正常启动。
+
+**默认值**: off
+
+## require_ssl
+
+**参数说明**: 设置服务器端是否强制要求SSL连接，该参数只有当参数[ssl](#ssl)为on时才有效。请在使用这个选项之前阅读**使用gsql连接**。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示服务器端强制要求SSL连接。
+- off表示服务器端对是否通过SSL连接不作强制要求。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> MogDB目前支持SSL的场景为客户端连接数据库主节点场景，该参数目前建议只在数据库主节点中开启。
+
+**默认值**: off
+
+## ssl_ciphers
+
+**参数说明**: 指定SSL支持的加密算法列表。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串，如果指定多个加密算法，加密算法之间需要以分号分割。详细请参见**用SSL进行安全的TCP/IP连接**获取支持的加密算法。
+
+**默认值**: ALL
+
+## ssl_renegotiation_limit
+
+**参数说明**: 指定在会话密钥重新协商之前，通过SSL加密通道可以传输的流量。这个重新协商流量限制机制可以减少攻击者针对大量数据使用密码分析法破解密钥的几率，但是也带来较大的性能损失。流量是指发送和接受的流量总和。使用SSL重协商机制可能引入其他风险，因此已禁用SSL重协商机制，为保持版本兼容保留此参数，修改参数配置不再起作用。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，最小值为0，最大值为2147483647。单位为KB。其中0表示禁用重新协商机制。
+
+**默认值**: 0
+
+## ssl_cert_file
+
+**参数说明**: 指定包含SSL服务器证书的文件的名称。相对路径是相对于数据目录的。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串
+
+**默认值**: server.crt
+
+## ssl_key_file
+
+**参数说明**: 指定包含SSL私钥的文件名称。相对路径是相对于数据目录的。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+取值范围:字符串
+
+**默认值**: server.key
+
+## ssl_ca_file
+
+**参数说明**: 指定包含CA信息的文件的名称。相对路径是相对于数据目录的。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串
+
+**默认值**: cacert.pem
+
+## ssl_crl_file
+
+**参数说明**: 指定包含CRL信息的文件的名称。必须使用相对路径，相对路径是相对于数据目录的。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串，其中空表示没有CA文件被加载，不进行客户端证书验证。
+
+**默认值**: 空
+
+## krb_server_keyfile
+
+**参数说明**: 指定Kerberos服务主配置文件的位置，详细请参见**配置客户端接入认证**。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串
+
+**默认值**: 空
+
+## krb_srvname
+
+**参数说明**: 设置Kerberos服务名，详细请参见**配置客户端接入认证**。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串
+
+**默认值**: postgres
+
+## krb_caseins_users
+
+**参数说明**: 设置Kerberos用户名是否大小写敏感。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示大小写不敏感。
+- off表示大小写敏感。
+
+**默认值**: off
+
+## modify_initial_password
+
+**参数说明**: 当MogDB安装成功后，数据库中仅存在一个初始用户（UID为10的用户）。客户通过该帐户初次登录数据库进行操作时，该参数决定是否要对该初始帐户的密码进行修改。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+如果安装过程中未指定初始用户密码，则安装后初始用户密码默认为空，执行其他操作前需要先通过gsql客户端设置初始用户的密码。此参数功能不再生效，保留此参数仅为兼容升级场景。
+
+**取值范围:**布尔型
+
+- on表示MogDB安装成功后初始用户首次登录操作前需要修改初始密码。
+- off表示MogDB安装成功后初始用户无需修改初始密码即可进行操作。
+
+**默认值**: off
+
+## password_policy
+
+**参数说明**: 在使用CREATE ROLE/USER或者ALTER ROLE/USER命令创建或者修改MogDB帐户时，该参数决定是否进行密码复杂度检查。关于密码复杂度检查策略请参见**设置密码安全策略**。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> 从安全性考虑，请勿关闭密码复杂度策略。
+
+**取值范围:**0、1
+
+- 0表示不采用任何密码复杂度策略。
+- 1表示采用默认密码复杂度校验策略。
+
+**默认值**: 1
+
+## password_reuse_time
+
+**参数说明**: 在使用ALTER USER或者ALTER ROLE修改用户密码时，该参数指定是否对新密码进行可重用天数检查。关于密码可重用策略请参见**设置密码安全策略**。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> 修改密码时会检查配置参数[password_reuse_time](#password_reuse_time)和[password_reuse_max](#password_reuse_max)。
+>
+> - 当[password_reuse_time](#password_reuse_time)和[password_reuse_max](#password_reuse_max)都为正数时，只要满足其中任一个，即可认为密码可以重用。
+> - 当[password_reuse_time](#password_reuse_time)为0时，表示不限制密码重用天数，仅限制密码重用次数。
+> - 当[password_reuse_max](#password_reuse_max)为0时，表示不限制密码重用次数，仅限制密码重用天数。
+> - 当[password_reuse_time](#password_reuse_time)和[password_reuse_max](#password_reuse_max)都为0时，表示不对密码重用进行限制。
+
+**取值范围:**浮点型，最小值为0，最大值为3650，单位为天。
+
+- 0表示不检查密码可重用的天数。
+- 正数表示新密码不能为该值指定的天数内使用过的密码。
+
+**默认值**: 60
+
+## password_reuse_max
+
+**参数说明**: 在使用ALTER USER或者ALTER ROLE修改用户密码时，该参数指定是否对新密码进行可重用次数检查。关于密码可重用策略请参见**设置密码安全策略**。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) 须知:
+> 修改密码时会检查配置参数[password_reuse_time](#password_reuse_time)和[password_reuse_max](#password_reuse_max)。
+>
+> - 当[password_reuse_time](#password_reuse_time)和[password_reuse_max](#password_reuse_max)都为正数时，只要满足其中任一个，即可认为密码可以重用。
+> - 当[password_reuse_time](#password_reuse_time)为0时，表示不限制密码重用天数，仅限制密码重用次数。
+> - 当[password_reuse_max](#password_reuse_max)为0时，表示不限制密码重用次数，仅限制密码重用天数。
+> - 当[password_reuse_time](#password_reuse_time)和[password_reuse_max](#password_reuse_max)都为0时，表示不对密码重用进行限制。
+
+**取值范围:**整型，最小值为0，最大值为1000。
+
+- 0表示不检查密码可重用次数。
+- 正整数表示新密码不能为该值指定的次数内使用过的密码。
+
+**默认值**: 0
+
+## password_lock_time
+
+**参数说明**: 该参数指定帐户被锁定后自动解锁的时间。关于帐户自动锁定策略请参见**设置密码安全策略**。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> password_lock_time和[failed_login_attempts](#failed_login_attempts)必须都为正数时锁定和解锁功能才能生效。
+
+**取值范围:**浮点型，最小值为0，最大值为365，单位为天。
+
+- 0表示密码验证失败时，自动锁定功能不生效。
+- 正数表示帐户被锁定后，当锁定时间超过password_lock_time设定的值时，帐户将会被自行解锁。
+
+**默认值**: 1d
+
+## failed_login_attempts
+
+**参数说明**: 在任意时在任意时候，如果输入密码错误的次数达到failed_login_attempts参数设定的值，则当前帐户会被锁定。password_lock_time参数设定的天数过后，帐户自动解锁。例如，登录时输入密码失败，ALTER USER时修改密码失败等。关于帐户自动锁定策略请参见**设置密码安全策略**。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> failed_login_attempts和[password_lock_time](#password_lock_time)必须都为正数时锁定和解锁功能才能生效。
+
+**取值范围:**整型，最小值为0，最大值为1000。
+
+- 0表示自动锁定功能不生效。
+- 正整数表示当错误密码次数达到failed_login_attempts设定的值时，当前帐户将被锁定。
+
+**默认值**: 10
+
+## password_encryption_type
+
+**参数说明**: 该字段决定采用何种加密方式对用户密码进行加密存储。修改此参数的配置不会自动触发已有用户密码加密方式的修改，只会影响新创建用户或修改用户密码操作。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**0、1、2、3
+
+- 0表示采用md5方式对密码加密。
+- 1表示采用sha256和md5两种方式分别对密码加密。
+- 2表示采用sha256方式对密码加密。
+- 3表示采用sm3方式对密码加密。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> md5加密算法安全性低，存在安全风险，不建议用户使用。
+
+**默认值**: 2
+
+## password_min_length
+
+**参数说明**: 该字段决定帐户密码的最小长度。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，6~999个字符。
+
+**默认值**: 8
+
+## password_max_length
+
+**参数说明**: 该字段决定帐户密码的最大长度。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，6~999个字符。
+
+**默认值**: 32
+
+## password_min_uppercase
+
+**参数说明**: 该字段决定帐户密码中至少需要包含大写字母个数。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，0~999
+
+- 0表示没有限制。
+- 1~999表示创建账户所指定的密码中至少需要包含大写字母个数。
+
+**默认值**: 0
+
+## password_min_lowercase
+
+**参数说明**: 该字段决定帐户密码中至少需要包含小写字母的个数。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，0~999
+
+- 0表示没有限制。
+- 1~999表示创建帐户所指定的密码中至少需要包含小写字母个数。
+
+**默认值**: 0
+
+## password_min_digital
+
+**参数说明**: 该字段决定帐户密码中至少需要包含数字的个数。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，0~999
+
+- 0表示没有限制。
+- 1~999表示创建帐户所指定的密码中至少需要包含数字个数。
+
+**默认值**: 0
+
+## password_min_special
+
+**参数说明**: 该字段决定帐户密码中至少需要包含特殊字符个数。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，0~999
+
+- 0表示没有限制。
+- 1~999表示创建帐户所指定的密码中至少需要包含特殊字符个数。
+
+**默认值**: 0
+
+## password_effect_time
+
+**参数说明**: 该字段决定帐户密码的有效时间。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**浮点型，最小值为0，最大值为999，单位为天。
+
+- 0表示不开启有效期限制功能。
+- 1~999表示创建帐户所指定的密码有效期，临近或超过有效期系统会提示用户修改密码。
+
+**默认值**: 90
+
+## password_notify_time
+
+**参数说明**: 该字段决定帐户密码到期前提醒的天数。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，最小值为0，最大值为999，单位为天。
+
+- 0表示不开启提醒功能。
+- 1~999表示帐户密码到期前提醒的天数。
+
+**默认值**: 7
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/3-connection-and-authentication/3-communication-library-parameters.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/3-connection-and-authentication/3-communication-library-parameters.md
new file mode 100644
index 0000000000000000000000000000000000000000..2b51a7f255fa13492d620a6b9feb5465f712ebe5
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/3-connection-and-authentication/3-communication-library-parameters.md
@@ -0,0 +1,87 @@
+---
+title: 通信库参数
+summary: 通信库参数
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 通信库参数
+
+本节介绍通信库相关的参数设置及取值范围等内容。
+
+## tcp_keepalives_idle
+
+**参数说明**: 在支持TCP_KEEPIDLE套接字选项的系统上，设置发送活跃信号的间隔秒数。不设置发送保持活跃信号，连接就会处于闲置状态。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+>
+> - 如果操作系统不支持TCP_KEEPIDLE选项，这个参数的值必须为0。
+> - 在通过Unix域套接字进行的连接的操作系统上，这个参数将被忽略。
+> - 将该值设置为0时，将使用系统的值。
+>
+> - 该参数在不同的**会话之间不共享**，也就是说不同的会话连接可能有不同的值。
+> - 查看该参数时查出来的是**当前会话连接内的参数值**，而不是**guc副本的值**。
+
+**取值范围**: 0-3600，单位为s。
+
+**默认值**: 0
+
+## tcp_keepalives_interval
+
+**参数说明**: 在支持TCP_KEEPINTVL套接字选项的操作系统上，以秒数声明在重新传输之间等待响应的时间。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 0-180，单位为s。
+
+**默认值**: 0
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+>
+> - 如果操作系统不支持TCP_KEEPINTVL选项，这个参数的值必须为0。
+> - 在通过Unix域套接字进行的连接的操作系统上，这个参数将被忽略。
+> - 将该值设置为0时，将使用系统的值。
+> - 该参数在不同的**会话之间不共享**，也就是说不同的会话连接可能有不同的值。
+> - 查看该参数时查出来的是**当前会话连接内的参数值**，而不是**guc副本的值**。
+
+## tcp_keepalives_count
+
+**参数说明**: 在支持TCP_KEEPCNT套接字选项的操作系统上，设置MogDB服务端在断开与客户端连接之前可以等待的保持活跃信号个数。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+>
+> - 如果操作系统不支持TCP_KEEPCNT选项，这个参数的值必须为0。
+> - 在通过Unix域套接字进行连接的操作系统上，这个参数将被忽略。
+> - 将该值设置为0时，将使用系统的值。
+> - 该参数在不同的**会话之间不共享**，也就是说不同的会话连接可能有不同的值。
+> - 查看该参数时查出来的是**当前会话连接内的参数值**，而不是**guc副本的值**。
+
+**取值范围**: 0-100，其中0表示MogDB未收到客户端反馈的保持活跃信号则立即断开连接。
+
+**默认值**: 0
+
+## comm_proxy_attr
+
+**参数说明**: 通信代理库相关参数配置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 该参数仅支持欧拉2.9系统下的集中式ARM单机。
+> - 本功能在线程池开启状态下生效，即enable_thread_pool为on。
+> - 配置该参数时需同步配置GUC参数local_bind_address为libos_kni的网卡IP。
+> - 参数模板：comm_proxy_attr = '{enable_libnet:true, enable_dfx:false, numa_num:4, numa_bind:[[30,31],[62,63],[94,95],[126,127]]}'
+> - 可配置参数说明。
+>   - enable_libnet：是否开启用户态协议，取值范围: true、false。
+>   - enable_dfx：是否开启通信代理库视图，取值范围: true、false。
+>   - numa_num：机器环境中numa的数量，支持2P、4P服务器，取值范围: 4、8。
+>   - numa_bind：代理线程绑核参数，每个numa两个CPU绑核，共numa_num组，取值范围: [0，cpu数-1]。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：字符串，长度大于0。
+
+**默认值**: 'none'
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/30-appendix.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/30-appendix.md
new file mode 100644
index 0000000000000000000000000000000000000000..2578e5a3d1dfc57f79934e2694816c5f6a97d85d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/30-appendix.md
@@ -0,0 +1,28 @@
+---
+title: 附录
+summary: 附录
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 附录
+
+## **表 1** GUC参数分类
+
+| 参数类型   | 说明                                                         | 设置方式                                                     |
+| ---------- | ------------------------------------------------------------ | ------------------------------------------------------------ |
+| INTERNAL   | 固定参数，在创建数据库的时候确定，用户无法修改，只能通过show语法或者pg_settings视图进行查看。 | 无                                                           |
+| POSTMASTER | 数据库服务端参数，在数据库启动时确定，可以通过配置文件指定。 | 支持表"GUC参数设置方式"中的方式一、方式四。                  |
+| SIGHUP     | 数据库全局参数，可在数据库启动时设置或者在数据库启动后，发送指令重新加载。 | 支持表"GUC参数设置方式"中的方式一、方式二、方式四。          |
+| BACKEND    | 会话连接参数。在创建会话连接时指定，连接建立后无法修改。连接断掉后参数失效。内部使用参数，不推荐用户设置。 | 支持表"GUC参数设置方式"中的方式一、方式二、方式四。说明:设置该参数后，下一次建立会话连接时生效。 |
+| SUSET      | 数据库管理员参数。可在数据库启动时、数据库启动后或者数据库管理员通过SQL进行设置。 | 支持表"GUC参数设置方式"中的方式一、方式二或由数据库管理员通过方式三设置。 |
+| USERSET    | 普通用户参数。可被任何用户在任何时刻设置。                   | 支持表"GUC参数设置方式"中的方式一、方式二或方式三设置。      |
+
+## **表 2** GUC参数设置方式
+
+| 序号   | 设置方法                                                     |
+| ------ | ------------------------------------------------------------ |
+| 方式一 | 1. 使用如下命令修改参数。<br />`gs_guc set -D datadir -c "paraname=value"`<br />说明:如果参数是一个字符串变量，则使用-c parameter="'value'"或者使用-c "parameter = 'value'"。<br />使用以下命令在数据库节点上同时设置某个参数。<br />`gs_guc set -N all -I all -c "paraname=value"`<br />2. 重启数据库使参数生效。<br />说明:<br />重启MogDB操作会导致用户执行操作中断，请在操作之前规划好合适的执行窗口。<br />`gs_om -t stop && gs_om -t start` |
+| 方式二 | `gs_guc reload -D datadir -c "paraname=value"`<br />说明:<br />使用以下命令在数据库节点上同时设置某个参数。<br />`gs_guc reload -N all -I all -c "paraname=value"` |
+| 方式三 | 修改指定数据库，用户，会话级别的参数。<br />- 设置数据库级别的参数<br />`postgres=# ALTER DATABASE dbname SET paraname TO value;`<br />在下次会话中生效。<br />- 设置用户级别的参数<br />`postgres=# ALTER USER username SET paraname TO value;`<br />在下次会话中生效。<br />- 设置会话级别的参数<br />`postgres=# SET paraname TO value;`<br />修改本次会话中的取值。退出会话后，设置将失效。 |
+| 方式四 | 使用ALTER SYSTEM SET修改数据库参数。<br />- 设置POSTMASERT级别的参数<br />`postgres=# ALTER SYSTEM SET paraname TO value;`<br />重启后生效。<br />- 设置SIGHUP级别的参数<br />`postgres=# ALTER SYSTEM SET paraname TO value;`<br />立刻生效(实际等待线程重新加载参数略有延迟)。<br />- 设置BACKEND级别的参数<br />`postgres=# ALTER SYSTEM SET paraname TO value;`<br />在下次会话中生效。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/31-scheduled-task.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/31-scheduled-task.md
new file mode 100644
index 0000000000000000000000000000000000000000..dca858ae58958dbcc952a7f7125c58fdde09ae93
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/31-scheduled-task.md
@@ -0,0 +1,42 @@
+---
+title: 定时任务
+summary: 定时任务
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# 定时任务
+
+## job_queue_processes
+
+**参数说明**: 表示系统可以并发执行的job数目。该参数为postmaster级别，通过gs_guc设置，需要重启gaussdb才能生效。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 0～1000
+
+功能：
+
+- 当job_queue_processes设置为0值，表示不启用定时任务功能，任何job都不会被执行（因为开启定时任务的功能会对系统的性能有影响，有些局点可能不需要定时任务的功能，可以通过设置为0不启用定时任务功能）。
+- 当job_queue_processes为大于0时，表示启用定时任务功能且系统能够并发处理的最大任务数。
+
+启用定时任务功能后，job_scheduler线程会在定时时间间隔轮询pg_job系统表，系统设置定时任务检查周期默认为1s。
+
+由于并行运行的任务数太多会消耗更多的系统资源，因此需要设置系统并发处理的任务数，当前并发的任务数达到job_queue_processes时，且此时又有任务到期，那么这些任务本次得不到执行而延期到下一轮询周期。因此，建议用户需要根据每个任务的执行时长合理的设置任务的时间间隔（即submit接口中的interval参数），来避免由于任务执行时间太长而导致下个轮询周期无法正常执行。
+
+注：如果同一时间内并行的job数很多，过小的参数值会导致job等待。而过大的参数值则消耗更多的系统资源，建议设置此参数为100，用户可以根据系统资源情况合理调整。
+
+**默认值**: 10
+
+## enable_prevent_job_task_startup
+
+**参数说明**：控制是否启动job线程。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：布尔型
+
+- on表示不能启动job线程。
+- off表示可以启动job线程。
+
+**默认值**：off
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/32-thread-pool.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/32-thread-pool.md
new file mode 100644
index 0000000000000000000000000000000000000000..0c272653dd9bc391a2b6e0a475a855e3079e0440
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/32-thread-pool.md
@@ -0,0 +1,37 @@
+---
+title: 线程池
+summary: 线程池
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# 线程池
+
+## enable_thread_pool
+
+**参数说明**：控制是否使用线程池功能。该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：布尔型
+
+- on表示开启线程池功能。
+- off表示不开启线程池功能。
+
+**默认值**：off
+
+## thread_pool_attr
+
+**参数说明**：用于控制线程池功能的详细属性，该参数仅在enable_thread_pool打开后生效。该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：字符串，长度大于0
+
+该参数分为3个部分，'thread_num, group_num, cpubind_info'，这3个部分的具体含义如下：
+
+- thread_num：线程池中的线程总数，取值范围是0~4096。其中0的含义是数据库根据系统CPU core的数量来自动配置线程池的线程数，如果参数值大于0，线程池中的线程数等于thread_num。线程池大小推荐根据硬件配置设置，计算公式为thread_num=CPU核数*3~5，thread_num最大值4096。
+- group_num：线程池中的线程分组个数，取值范围是0~64。其中0的含义是数据库根据系统NUMA组的个数来自动配置线程池的线程分组个数，如果参数值大于0，线程池中的线程组个数等于group_num。
+- cpubind_info：线程池是否绑核的配置参数。可选择的配置方式有集中：
+  1. '(nobind)' ，线程不做绑核；
+  2. '(allbind)'，利用当前系统所有能查询到的CPU core做线程绑核；
+  3. '(nodebind: 1, 2)'，利用NUMA组1，2中的CPU core进行绑核；
+  4. '(cpubind: 0-30)'，利用0-30号CPU core进行绑核。该参数不区分大小写。
+
+**默认值**：'16, 2, (nobind)'
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/33-user-defined-functions.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/33-user-defined-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..940b19cd7f1e8e7073f7ed394883b0e3d54648eb
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/33-user-defined-functions.md
@@ -0,0 +1,55 @@
+---
+title: 用户自定义函数
+summary: 用户自定义函数
+author: Zhang Cuiping
+date: 2021-11-08
+---
+
+# 用户自定义函数
+
+## udf_memory_limit
+
+**参数说明**: 控制每个数据库节点执行UDF时可用的最大物理内存量。本参数当前版本不生效，请使用FencedUDFMemoryLimit和UDFWorkerMemHardLimit参数控制fenced udf worker虚存。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，200\*1024～max_process_memory，单位为KB。
+
+**默认值**: 200MB
+
+## FencedUDFMemoryLimit
+
+**参数说明**: 控制每个fenced udf worker进程使用的虚拟内存。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整数，0 \~ 2147483647，单位为KB，设置可带单位（KB，MB，GB）。其中0表示不做内存控制。
+
+**默认值**: 0
+
+## UDFWorkerMemHardLimit
+
+**参数说明**: 控制fencedUDFMemoryLimit的最大值。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整数，0 \~ 2147483647，单位为KB，设置时可带单位（KB，MB，GB）。
+
+**默认值**: 1GB
+
+## pljava_vmoptions
+
+**参数说明**：用户自定义设置PL/Java函数所使用的JVM虚拟机的启动参数，仅sysadmin用户可以访问。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串，支持：
+
+- JDK8 JVM启动参数（可参见JDK[官方](https://docs.oracle.com/javase/8/docs/technotes/tools/unix/java.html)说明）
+- JDK8 JVM系统属性参数（以-D开头如-Djava.ext.dirs，可参见JDK[官方](https://docs.oracle.com/javase/tutorial/deployment/doingMoreWithRIA/properties.html)说明）
+- 用户自定义参数（以-D开头，如-Duser.defined.option）
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+>如果用户在pljava_vmoptions中设置参数不满足上述取值范围，会在使用PL/Java语言函数时报错。
+
+**默认值**: 空
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/34-backup-and-restoration.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/34-backup-and-restoration.md
new file mode 100644
index 0000000000000000000000000000000000000000..347be8f065f9f56eeae8c06df610198f405ddfb0
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/34-backup-and-restoration.md
@@ -0,0 +1,46 @@
+---
+title: 备份恢复
+summary: 备份恢复
+author: Zhang Cuiping
+date: 2021-11-08
+---
+
+# 备份恢复
+
+## operation_mode
+
+**参数说明**: 标示系统进入备份恢复模式。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示在备份恢复过程中。
+- off表示不在备份恢复过程中。
+
+**默认值**: off
+
+## enable_cbm_tracking
+
+**参数说明**: 当使用roach执行数据库实例的全量和增量备份时需要开启此参数，如果关闭会导致备份失败。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示追踪功能开启。
+- off表示追踪功能关闭。
+
+**默认值**: off
+
+## hadr_max_size_for_xlog_receiver
+
+**参数说明**：该参数为异地容灾参数，表示灾备数据库实例中实例获取obs端日志和本地回放日志的最大允许差距，若差距大于此值时停止获取obs端日志。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中方式对应设置方法进行设置。
+
+**修改建议：**该参数的取值应和本地磁盘大小相关，建议设置为磁盘大小的50%。
+
+**取值范围**：整型，0~2147483647
+
+**默认值**：256GB
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/35-undo.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/35-undo.md
new file mode 100644
index 0000000000000000000000000000000000000000..853f43e5617af81018417118157a2cf63a17345e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/35-undo.md
@@ -0,0 +1,43 @@
+---
+title: Undo
+summary: Undo
+author: Zhang Cuiping
+date: 2021-11-08
+---
+
+# Undo
+
+## undo_space_limit_size
+
+**参数说明**: 用于控制undo强制回收阈值，达到阈值的80%启动强制回收。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，800M~16TB
+
+**默认值**: 32GB
+
+## undo_limit_size_per_transaction
+
+**参数说明**: 用于控制单事务undo分配空间阈值，达到阈值时事务报错回滚。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，2M~16TB
+
+**默认值**: 32GB
+
+## undo_zone_count
+
+**参数说明**: 用于控制在内存中可分配的undo zone数量，达到阈值或本次设置的数值小于上次时报错，重新按规则设置合理取值后可恢复正常。当参数设置为0时，禁用undo，禁止创建ustore表。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，0~1,048,576
+
+取值约束：
+
+1. 本次设置数值不得小于上次设置的数值，设置错误时会导致数据库无法正常恢复，重新合理设置后重启数据库可恢复正常。
+2. 当前undo_zone_count取值需要根据max_connections来调节设置，修改max_connections取值后，需对应修改undo_zone_count，取值规则为max_connections取值的4倍。
+
+**默认值**: 0
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/36-DCF-parameters-settings.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/36-DCF-parameters-settings.md
new file mode 100644
index 0000000000000000000000000000000000000000..91d9766e5c3c17ad81dcd15280d2bd57e1d5aff1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/36-DCF-parameters-settings.md
@@ -0,0 +1,344 @@
+---
+title: DCF参数设置
+summary: DCF参数设置
+author: Zhang Cuiping
+date: 2021-11-08
+---
+
+# DCF参数设置
+
+## enable_dcf
+
+**参数说明**: 是否开启DCF模式，该参数不允许修改。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型，on/off。on表示当前安装部署方式为DCF模式，off表示当前安装部署方式为非DCF模式。
+
+**默认值**: off
+
+## dcf_ssl
+
+**参数说明**: 是否开启SSL，重启生效。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型，on/off。on表示使用SSL，off表示不使用SSL。
+
+**默认值**: on
+
+## dcf_config
+
+**参数说明**: 用户安装时自定义配置信息，该参数不允许修改。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**默认值**: 字符串，安装时用户自定义配置
+
+## dcf_data_path
+
+**参数说明**: DCF数据路径，该参数不允许修改。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**默认值**: 字符串，DN数据目录下的dcf_data目录
+
+## dcf_log_path
+
+**参数说明**: DCF日志路径，该参数不允许修改。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**默认值**: 字符串，DN数据目录下的dcf_log目录
+
+## dcf_node_id
+
+**参数说明**: DCF所在DN节点ID，用户安装时自定义，该参数不允许修改。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**默认值**: 整型，安装时用户自定义配置
+
+## dcf_max_workers
+
+**参数说明**: DCF回调函数线程个数。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，10~262143
+
+**默认值**: 10
+
+## dcf_truncate_threshold
+
+**参数说明**: DN对DCF日志进行truncate的门限阈值。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，1~2147483647
+
+**默认值**: 100000
+
+## dcf_election_timeout
+
+**参数说明**: DCF leader和follower选举超时时间。选举超时时间数值依赖于当前DN之间的网络状况，在超时时间较小且网络极差的情形下，会有超时选举发生，待网络恢复选举恢复正常。建议根据当前网络状态合理设置超时时间。对DCF节点时钟的约束：DCF节点间最大时钟差异小于选举超时时间的一半。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，单位s，1~600
+
+**默认值**: 3
+
+## dcf_run_mode
+
+**参数说明**: DCF选举模式，0表示自动选举模式，2表示去使能选举模式。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 枚举类型，0、2
+
+**默认值**: 0
+
+## dcf_log_level
+
+**参数说明**: DCF日志级别。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串
+
+- **关闭日志**：“NONE”，NONE表示关闭日志打印，不能与以下日志级别混合使用。
+
+- **开启日志：“**RUN_ERR|RUN_WAR|RUN_INF|DEBUG_ERR|DEBUG_WAR|DEBUG_INF|TRACE|PROFILE|OPER”
+
+  日志级别可以从上述字符串中选取字符串并使用竖线组合使用，不能配置空串。
+
+**默认值**: “RUN_ERR|RUN_WAR|DEBUG_ERR|OPER|RUN_INF|PROFILE”
+
+## dcf_log_backup_file_count
+
+**参数说明**: DCF运行日志备份保留个数。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，1~100
+
+**默认值**: 10
+
+## dcf_max_log_file_size
+
+**参数说明**: DCF运行日志单个文件最大大小。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，单位MB，1~1000
+
+**默认值**: 10
+
+## dcf_socket_timeout
+
+**参数说明**: DCF通信模块连接socket超时时间，参数重启生效。对于网络环境比较差的环境，若配置很小的超时时间，可能会导致建链不成功，此时需要适当增大此值。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，单位ms，10~600000
+
+**默认值**: 5000
+
+## dcf_connect_timeout
+
+**参数说明**: DCF通信模块建立连接超时时间，参数重启生效。对于网络环境比较差的环境，若配置很小的超时时间，可能会导致建链不成功，此时需要适当增大此值。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，单位ms，10~600000
+
+**默认值**: 60000
+
+## dcf_mec_fragment_size
+
+**参数说明**: DCF通信模块fragment大小，参数重启生效。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，单位KB，32~10240
+
+**默认值**: 64
+
+## dcf_stg_pool_max_size
+
+**参数说明**: DCF存储模内存池最大值，参数重启生效。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，单位MB，32~2147483647
+
+**默认值**: 2048
+
+## dcf_stg_pool_init_size
+
+**参数说明**: DCF存储模块内存池最小值，参数重启生效。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，单位MB，32~2147483647
+
+**默认值**: 32
+
+## dcf_mec_pool_max_size
+
+**参数说明**: DCF通信模块内存池最大值，参数重启生效。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，单位MB，32~2147483647
+
+**默认值**: 200
+
+## dcf_flow_control_disk_rawait_threshold
+
+**参数说明**: DCF流控功能的磁盘等待阈值。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，单位us，0~2147483647
+
+**默认值**: 100000
+
+## dcf_flow_control_net_queue_message_num_threshold
+
+**参数说明**: DCF流控功能的网络队列消息数阈值。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，0~2147483647
+
+**默认值**: 1024
+
+## dcf_flow_control_cpu_threshold
+
+**参数说明**: DCF CPU流控阈值。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，单位百分比，0~2147483647
+
+**默认值**: 100
+
+## dcf_mec_batch_size
+
+**参数说明**: DCF通信批量消息数，数值为0时，DCF会根据网络以及写入数据量自适应调整，参数重启生效。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，0~1024
+
+**默认值**: 0
+
+## dcf_mem_pool_max_size
+
+**参数说明**: DCF内存最大值，参数重启生效。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，单位MB，32~2147483647
+
+**默认值**: 2048
+
+## dcf_mem_pool_init_size
+
+**参数说明**: DCF内存初始化大小，参数重启生效。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，单位MB，32~2147483647
+
+**默认值**: 32
+
+## dcf_compress_algorithm
+
+**参数说明**: DCF运行日志传输压缩算法，参数重启生效。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型
+
+- 0表示不压缩
+- 1表示ZSTD压缩算法
+- 2表示LZ4压缩算法
+
+**默认值**: 0
+
+## dcf_compress_level
+
+**参数说明**: DCF日志传输压缩级别，参数重启生效，此参数生效前提必须配置有效的压缩算法，即设置合法的dcf_compress_algorithm参数。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型
+
+- 若不使用压缩算法，取值不生效
+- 若选择ZSTD压缩算法，取值范围1~22
+- 若选择LZ4压缩算法，取值范围1~9
+
+**默认值**: 1
+
+## dcf_mec_channel_num
+
+**参数说明**: DCF通信通道数量，参数重启生效。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，1~64
+
+**默认值**: 1
+
+## dcf_rep_append_thread_num
+
+**参数说明**: DCF日志复制线程数量，参数重启生效。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，1~1000
+
+**默认值**: 2
+
+## dcf_mec_agent_thread_num
+
+**参数说明**: DCF通信工作线程数量，参数重启生效。dcf_mec_agent_thread_num值建议不少于2*节点数*dcf_mec_channel_num。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，1~1000
+
+**默认值**: 10
+
+## dcf_mec_reactor_thread_num
+
+**参数说明**: DCF使用reactor线程数量，参数重启生效。dcf_mec_reactor_thread_num与dcf_mec_agent_thread_num比例建议1：40。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，1~100
+
+**默认值**: 1
+
+## dcf_log_file_permission
+
+**参数说明**: DCF运行日志文件属性，参数重启生效。若用户需要支持同组的其他用户访问日志，首先需要所有的父目录都支持同组的其他用户也能访问。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 枚举型，600、640
+
+**默认值**: 600
+
+## dcf_log_path_permission
+
+**参数说明**: DCF运行日志目录属性，参数重启生效，不支持修改。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 枚举型，700、750
+
+**默认值**: 700
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/37-flashback.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/37-flashback.md
new file mode 100644
index 0000000000000000000000000000000000000000..2d2fc0208d8a8ab68fd25fda41f9547d6ff9d5e2
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/37-flashback.md
@@ -0,0 +1,52 @@
+---
+title: 闪回相关参数
+summary: 闪回相关参数
+author: Zhang Cuiping
+date: 2021-11-08
+---
+
+# 闪回相关参数
+
+本章节介绍闪回功能相关参数。
+
+## enable_recyclebin
+
+**参数说明**：用来控制回收站的实时打开和关闭。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：布尔型
+
+**默认值**：off
+
+## recyclebin_retention_time
+
+参数说明：设置回收站对象保留时间，超过该时间的回收站对象将被自动清理。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+取值范围: 整型，单位为s，最小值为1，最大值为2147483647。
+
+默认值：15min（即900s）
+
+## version_retention_age
+
+**参数说明**：设置旧版本保留的事务数，超过该事务数的旧版本将被回收清理。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：整型，0～576460752303423487，值为0表示不延迟。
+
+**默认值**：0
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **注意：** 因系统表采用Heap引擎，为避免不必要的系统表膨胀问题（如业务上只是用Uheap闪回功能），在配置version_retention_age的同时，还需同值配置vacuum_defer_cleanup_age，才能有效保留旧版本。
+
+## vacuum_defer_cleanup_age
+
+**参数说明**：指定VACUUM使用的事务数，VACUUM会延迟清除无效的行存表记录，延迟的事务个数通过vacuum_defer_cleanup_age进行设置。即VACUUM和VACUUM FULL操作不会立即清理刚刚被删除元组。也可以通过设置该参数，配置闪回功能旧版本保留期限。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：整型，0～1000000，值为0表示不延迟。取值范围需要扩展到1亿。
+
+**默认值**：0
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/38-rollback-parameters.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/38-rollback-parameters.md
new file mode 100644
index 0000000000000000000000000000000000000000..9769c979bacec168b87d983640e76c1ebb8adeb2
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/38-rollback-parameters.md
@@ -0,0 +1,18 @@
+---
+title: 回滚相关参数
+summary: 回滚相关参数
+author: Zhang Cuiping
+date: 2021-11-08
+---
+
+# 回滚相关参数
+
+## max_undo_workers
+
+**参数说明**: 异步回滚调用的undoworker线程数量，参数重启生效。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，1~100
+
+**默认值**: 5
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/39-reserved-parameters.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/39-reserved-parameters.md
new file mode 100644
index 0000000000000000000000000000000000000000..de8e5fda6db7ccfe32ff606ac10f009ec5a53507
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/39-reserved-parameters.md
@@ -0,0 +1,26 @@
+---
+title: 预留参数
+summary: 预留参数
+author: Zhang Cuiping
+date: 2021-11-08
+---
+
+# 预留参数
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 下列参数为预留参数，该版本不生效。
+
+acce_min_datasize_per_thread
+
+cstore_insert_mode
+
+enable_constraint_optimization
+
+enable_hadoop_env
+
+enable_hdfs_predicate_pushdown
+
+enable_orc_cache
+
+schedule_splits_threshold
+
+backend_version
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/1-memory.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/1-memory.md
new file mode 100644
index 0000000000000000000000000000000000000000..73b901718fdf447c534a5d40379e94e73588d82c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/1-memory.md
@@ -0,0 +1,326 @@
+---
+title: 内存
+summary: 内存
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 内存
+
+介绍与内存相关的参数设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> 这些参数只能在数据库服务重新启动后生效。
+
+## memorypool_enable
+
+**参数说明**: 设置是否允许使用内存池。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示允许使用内存池。
+- off表示不允许使用内存池。
+
+**默认值**: off
+
+## memorypool_size
+
+**参数说明**: 设置内存池大小。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，128*1024～INT_MAX/2，单位为KB。
+
+**默认值**: 512MB
+
+## enable_memory_limit
+
+**参数说明**: 启用逻辑内存管理模块。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示启用逻辑内存管理模块。
+- off表示不启用逻辑内存管理模块。
+
+**默认值**: on
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+>
+> - 若max_process_memory-shared_buffers-cstore_buffers-元数据少于2G，MogDB强制把enable_memory_limit设置为off。其中元数据是MogDB内部使用的内存和部分并发参数，如max_connections、thread_pool_attr、max_prepared_transactions等参数相关。
+> - 当该值为off时，不对数据库使用的内存做限制，在大并发或者复杂查询时，使用内存过多，可能导致操作系统OOM问题。
+
+## max_process_memory
+
+**参数说明**: 设置一个数据库节点可用的最大物理内存。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型 , `2*1024*1024` ～ INT_MAX，单位为KB。
+
+**默认值**: 12GB。
+
+**设置建议:**
+
+数据库节点上该数值需要根据系统物理内存及单节点部署主数据库节点个数决定。建议计算公式如下: `(物理内存大小 - vm.min_free_kbytes) * 0.7 / (1 + 主节点个数)`。该系数的目的是尽可能保证系统的可靠性，不会因数据库内存膨胀导致节点OOM。这个公式中提到vm.min_free_kbytes，其含义是预留操作系统内存供内核使用，通常用作操作系统内核中通信收发内存分配，至少为5%内存。即，max_process_memory = `物理内存 * 0.665 / (1 + 主节点个数)`。
+
+## enable_memory_context_control
+
+**参数说明**: 启用检查内存上下文是否超过给定限制的功能。仅适用于DEBUG版本。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示启用最大内存上下文限制检查功能。
+- off表示关闭最大内存上下文限制检查功能。
+
+**默认值**: off
+
+## uncontrolled_memory_context
+
+**参数说明**: 启用检查内存上下文是否超过给定限制的功能时，设置不受此功能约束。仅适用于DEBUG版本。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+查询时会在参数值的最前面添加标题含义字符串“MemoryContext white list:”。
+
+**取值范围**: 字符串
+
+**默认值**: 空
+
+## shared_buffers
+
+**参数说明**: 设置MogDB使用的共享内存大小。增加此参数的值会使MogDB比系统默认设置需要更多的System V共享内存。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，16 ~ 1073741823 ，单位为KB。
+
+shared_buffers需要设置为BLCKSZ的整数倍，BLCKSZ目前设置为8KB，即shared_buffers需要设置为8KB整数倍。改变BLCKSZ的值会改变最小值。
+
+**默认值**: 数据库节点为1GB。如果操作系统支持的共享内存小于32MB，则在初始化数据存储区时会自动调整为操作系统支持的最大值。
+
+**设置建议:**
+
+建议设置shared_buffers值为内存的40%以内。行存列存分开对待。行存设大，列存设小。列存: `(单服务器内存/单服务器数据库节点个数) * 0.4 * 0.25`。
+
+如果设置较大的shared_buffers需要同时增加checkpoint_segments的值，因为写入大量新增、修改数据需要消耗更多的时间周期。
+
+## segment_buffers
+
+**参数说明**: 设置MogDB段页式元数据页的内存大小。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值说明：**整型，16 ~ 1073741823，单位为8KB。
+
+shared_buffers需要设置为BLCKSZ的整数倍，BLCKSZ目前设置为8KB，即shared_buffers需要设置为8KB整数倍。改变BLCKSZ的值会改变最小值。
+
+**默认值**: 8MB
+
+**设置建议：**
+
+segment_buffers 用来缓存段页式段头的内容，属于关键元数据信息，为了提高性能建议常用的表的段头都能缓存在buffer中，不被置换出去。建议按照`表的个数（包括索引和toast表）* 分区数 * 3 + 128` 来设置。乘以3是因为每个表（分区）会有一些额外的元数据段，一般一个表有3个段。最后+128因为段页式表空间管理需要一定数量的buffer。
+
+## bulk_write_ring_size
+
+**参数说明**: 数据并行导入使用的环形缓冲区大小。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，16384 ~ 2147483647，单位为KB。
+
+**默认值**: 2GB
+
+**设置建议:**建议导入压力大的场景中增加数据库节点中此参数配置。
+
+## standby_shared_buffers_fraction
+
+**参数说明**: 备实例所在服务器使用shared_buffers内存缓冲区大小的比例。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**双精度类型，0.1~1.0
+
+**默认值**: 0.3
+
+## temp_buffers
+
+**参数说明**: 设置每个数据库会话使用的LOCAL临时缓冲区的大小。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+在每个会话的第一次使用临时表之前可以改变temp_buffers的值，之后的设置将是无效的。
+
+一个会话将按照temp_buffers给出的限制，根据需要分配临时缓冲区。如果在一个并不需要大量临时缓冲区的会话里设置一个大的数值，其开销只是一个缓冲区描述符的大小。当缓冲区被使用，就会额外消耗8192字节。
+
+**取值范围:**整型，100~1073741823，单位为8KB。
+
+**默认值**: 1MB
+
+## max_prepared_transactions
+
+**参数说明**: 设置可以同时处于"预备"状态的事务的最大数目。增加此参数的值会使MogDB比系统默认设置需要更多的System V共享内存。
+
+当MogDB部署为主备双机时，在备机上此参数的设置必须要高于或等于主机上的，否则无法在备机上进行查询操作。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型。0~262143。
+
+**默认值**: 800
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+> 为避免在准备步骤失败，此参数的值不能小于max_connections。
+
+## work_mem
+
+**参数说明**:  设置内部排序操作和Hash表在开始写入临时磁盘文件之前使用的内存大小。ORDER BY，DISTINCT和merge joins都要用到排序操作。Hash表在散列连接、散列为基础的聚集、散列为基础的IN子查询处理中都要用到。
+
+对于复杂的查询，可能会同时并发运行好几个排序或者散列操作，每个都可以使用此参数所声明的内存量，不足时会使用临时文件。同样，好几个正在运行的会话可能会同时进行排序操作。因此使用的总内存可能是work_mem的好几倍。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:** 整型，64~2147483647，单位为KB。
+
+**默认值**: 64MB
+
+**设置建议:**
+
+> 依据查询特点和并发来确定，一旦work_mem限定的物理内存不够，算子运算数据将写入临时表空间，带来5-10倍的性能下降，查询响应时间从秒级下降到分钟级。
+>
+> - 对于串行无并发的复杂查询场景，平均每个查询有5-10关联操作，建议work_mem=50%内存/10。
+> - 对于串行无并发的简单查询场景，平均每个查询有2-5个关联操作，建议work_mem=50%内存/5。
+> - 对于并发场景，建议work_mem=串行下的work_mem/物理并发数。
+
+## query_mem
+
+**参数说明**: 设置执行作业所使用的内存。如果设置的query_mem值大于0，在生成执行计划时，优化器会将作业的估算内存调整为该值。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:** 0，或大于32M的整型，默认单位为KB。如果设置值为负数或小于32M，将设置为默认值0，此时优化器不会根据该值调整作业的估算内存。
+
+**默认值**: 0
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+>
+> - 如果设置的query_mem值大于0，在生成执行计划时，优化器会将作业的估算内存调整为该值。
+> - 如果设置值为负数或小于32MB，将设置为默认值0，此时优化器不会根据该值调整作业的估算内存。
+
+## query_max_mem
+
+**参数说明**: 设置执行作业所能够使用的最大内存。如果设置的query_max_mem值大于0，当作业执行时所使用内存超过该值时，将报错退出。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**0，或大于32M的整型，默认单位为KB。如果设置值为负数或小于32M，将设置为默认值0，此时不会根据该值限制作业的内存使用。
+
+**默认值**: 0
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+>
+> - 如果设置的query_max_mem值大于0，当作业执行时所使用内存超过该值时，将报错退出。
+> - 如果设置值为负数或小于32M，将设置为默认值0，此时不会根据该值限制作业的内存使用。
+
+## maintenance_work_mem
+
+**参数说明**: 设置在维护性操作（比如VACUUM、CREATE INDEX、ALTER TABLE ADD FOREIGN KEY等）中可使用的最大的内存。该参数的设置会影响VACUUM、VACUUM FULL、CLUSTER、CREATE INDEX的执行效率。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，1024~INT_MAX，单位为KB。
+
+**默认值**: 16MB
+
+**设置建议:**
+
+- 建议设置此参数的值大于[work_mem](#work_mem)，可以改进清理和恢复数据库转储的速度。因为在一个数据库会话里，任意时刻只有一个维护性操作可以执行，并且在执行维护性操作时不会有太多的会话。
+- 当自动清理线程运行时，autovacuum_max_workers倍数的内存将会被分配，所以此时设置maintenance_work_mem的值应该不小于[work_mem](#work_mem)。
+- 如果进行大数据量的cluster等，可以在session中调大该值。
+
+## psort_work_mem
+
+**参数说明**: 设置列存表在进行局部排序中，在开始写入临时磁盘文件之前使用的内存大小。带partial cluster key的表、带索引的表插入、创建表索引、删除表和更新表都会用到。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> 同样，多个正在运行的会话可能会同时进行表的局部排序操作。因此，使用的总内存可能是psort_work_mem的几倍。
+
+**取值范围:**整型64~2147483647，单位为KB。
+
+**默认值**: 512MB
+
+## max_loaded_cudesc
+
+**参数说明**: 设置列存表在做扫描时，每列缓存cudesc信息的个数。增大设置会提高查询性能，但也会增加内存占用，特别是当列存表的列非常多时。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> max_loaded_cudesc设置过高时，有可能引起内存分配不足。
+
+**取值范围:**100~1073741823。
+
+**默认值**: 1024
+
+## max_stack_depth
+
+**参数说明**: 设置MogDB执行堆栈的最大安全深度。需要这个安全界限是因为在服务器里，并非所有程序都检查了堆栈深度，只是在可能递规的过程，比如表达式计算这样的过程里面才进行检查。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，100~INT_MAX，单位为KB。
+
+**默认值**: 2MB
+
+**设置原则**:
+
+- 数据库需要预留640KB堆栈深度，因此此参数的最佳设置是等于操作系统内核允许的最大值（就是ulimit -s的设置）- 640KB。
+- 如果设置此参数的值大于实际的内核限制，则一个正在运行的递归函数可能会导致一个独立的服务器进程崩溃。在MogDB能够检测内核限制的操作系统上（SLES上），将自动限制设置为一个不安全的值。
+- 因为并非所有的操作都能够检测，所以建议用户在此设置一个明确的值。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+> 默认值2MB，这个值相对比较小，不容易导致系统崩溃。
+
+## cstore_buffers
+
+**参数说明**: 设置列存所使用的共享缓冲区的大小。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，16384～1073741823，单位为KB。
+
+**默认值**: 1GB
+
+**设置建议**:
+
+列存表使用cstore_buffers设置的共享缓冲区，几乎不用shared_buffers。因此在列存表为主的场景中，应减少shared_buffers，增加cstore_buffers。
+
+## bulk_read_ring_size
+
+**参数说明**: 并行导出，使用的环形缓冲区大小。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，256~2147483647，单位为KB。
+
+**默认值**: 16MB
+
+## enable_early_free
+
+**参数说明**：控制是否可以实现算子内存的提前释放。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：布尔型
+
+- on表示支持算子内存提前释放。
+- off表示不支持算子内存提前释放。
+
+**默认值**：on
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/2-disk-space.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/2-disk-space.md
new file mode 100644
index 0000000000000000000000000000000000000000..ac29f8e1617365cd52ece6ef5a5af73468e96dad
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/2-disk-space.md
@@ -0,0 +1,35 @@
+---
+title: 磁盘空间
+summary: 磁盘空间
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 磁盘空间
+
+介绍与磁盘空间相关的参数，用于限制临时文件所占用的磁盘空间。
+
+## sql_use_spacelimit
+
+**参数说明**: 限制单个SQL在单个数据库节点上，触发落盘操作时，落盘文件的空间大小，管控的空间包括普通表、临时表以及中间结果集落盘占用的空间。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置
+
+**取值范围:**整型，-1~2147483647，单位为KB。其中-1表示没有限制。
+
+**默认值**: -1
+
+## temp_file_limit
+
+**参数说明**: 限制一个会话中，触发下盘操作时，单个下盘文件的空间大小。例如一次会话中，排序和哈希表使用的临时文件，或者游标占用的临时文件。
+
+此设置为会话级别的下盘文件控制。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> SQL查询执行时使用的临时表空间不在此限制。
+
+**取值范围:**整型，-1~2147483647，单位为KB。其中-1表示没有限制。
+
+**默认值**: -1
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/3-kernel-resource-usage.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/3-kernel-resource-usage.md
new file mode 100644
index 0000000000000000000000000000000000000000..fb8ddeda7aedf83b8bccd1a280179295dc6510ac
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/3-kernel-resource-usage.md
@@ -0,0 +1,41 @@
+---
+title: 内核资源使用
+summary: 内核资源使用
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 内核资源使用
+
+介绍与操作系统内核相关的参数，这些参数是否生效依赖于操作系统的设置。
+
+## max_files_per_process
+
+**参数说明**: 设置每个服务器进程允许同时打开的最大文件数目。如果操作系统内核强制一个合理的数目，则不需要设置。
+
+但是在一些平台上（特别是大多数BSD系统），内核允许独立进程打开比系统真正可以支持的数目大得多的文件数。如果用户发现有的"Too many open files"这样的失败现象，请尝试缩小这个设置。通常情况下需要满足，系统FD（file descriptor）数量&gt;=`最大并发数*数据库节点个数*max_files_per_process*3`。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，25~2147483647。
+
+**默认值**: 1000
+
+## shared_preload_libraries
+
+**参数说明**: 此参数用于声明一个或者多个在服务器启动的时候预先装载的共享库，多个库名称之间用逗号分隔。比如 '$libdir/mylib' 会在加载标准库目录中的库文件之前预先加载mylib.so（某些平台上可能是mylib.sl）库文件。
+
+可以用这个方法预先装载MogDB的存储过程库，通常是使用 '$libdir/plXXX' 语法。XXX只能是pgsql，perl，tcl，python之一。
+
+通过预先装载一个共享库并在需要的时候初始化它，可以避免第一次使用这个库的加载时间。但是启动每个服务器进程的时间可能会增加，即使进程从来没有使用过这些库。因此建议对那些将被大多数会话使用的库才使用这个选项。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+>
+> - 如果被声明的库不存在，MogDB服务将会启动失败。
+> - 每一个支持MogDB的库都有一个特殊的标记用于保证兼容性。因此，不支持MogDB的库不能用这种方法加载。
+
+**取值范围:**字符串
+
+**默认值**: 空
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/4-cost-based-vacuum-delay.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/4-cost-based-vacuum-delay.md
new file mode 100644
index 0000000000000000000000000000000000000000..5761a33ca77a31ef85b42cfc136f28b29f56c26b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/4-cost-based-vacuum-delay.md
@@ -0,0 +1,76 @@
+---
+title: 基于开销的清理延迟
+summary: 基于开销的清理延迟
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 基于开销的清理延迟
+
+这个特性的目的是允许管理员减少VACUUM和ANALYZE语句在并发活动的数据库上的I/O影响。比如，像VACUUM和ANALYZE这样的维护语句并不需要迅速完成，并且不希望他们严重干扰系统执行其他的数据库操作。基于开销的清理延迟为管理员提供了一个实现这个目的手段。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> 有些清理操作会持有关键的锁，这些操作应该尽快结束并释放锁。所以MogDB的机制是，在这类操作过程中，基于开销的清理延迟不会发生作用。为了避免在这种情况下的长延时，实际的开销限制取下面两者之间的较大值:
+>
+> - vacuum_cost_delay*accumulated_balance/vacuum_cost_limit*
+> - vacuum_cost_delay*4
+
+**背景信息**
+
+在ANALYZE | ANALYSE和VACUUM语句执行过程中，系统维护一个内部的记数器，跟踪所执行的各种I/O操作的近似开销。如果积累的开销达到了vacuum_cost_limit声明的限制，则执行这个操作的进程将睡眠vacuum_cost_delay指定的时间。然后它会重置记数器然后继续执行。
+
+这个特性是缺省关闭的。如需开启，需要把vacuum_cost_delay变量设置为一个非零值。
+
+## vacuum_cost_delay
+
+**参数说明**: 指定开销超过vacuum_cost_limit的值时，进程睡眠的时间。
+
+要注意在许多系统上，睡眠的有效分辨率是10毫秒。因此把vacuum_cost_delay设置为一个不是10的整数倍的数值与将它设置为下一个10的整数倍作用相同。
+
+此参数一般设置较小，常见的设置是10或20毫秒。调整此特性资源占用率时，最好是调整其他参数，而不是此参数。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**integer（毫秒），0~100，正数值表示打开基于开销的清理延迟特性；0表示关闭基于开销的清理延迟特性。
+
+**默认值**: 0
+
+## vacuum_cost_page_hit
+
+**参数说明**: 清理一个在共享缓存里找到的缓冲区的预计开销。它代表锁住缓冲池、查找共享的Hash表、扫描页面内容的开销。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**integer，0~10000。
+
+**默认值**: 1
+
+## vacuum_cost_page_miss
+
+**参数说明**: 清理一个要从磁盘上读取的缓冲区的预计开销。它代表锁住缓冲池、查找共享Hash表、从磁盘读取需要的数据块、扫描它的内容的开销。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**integer，0~10000。
+
+**默认值**: 10
+
+## vacuum_cost_page_dirty
+
+**参数说明**: 清理修改一个原先是干净的块的预计开销。它代表把一个脏的磁盘块再次刷新到磁盘上的额外开销。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**integer，0~1000
+
+**默认值**: 20
+
+## vacuum_cost_limit
+
+**参数说明**: 导致清理进程休眠的开销限制。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**integer，1~10000。
+
+**默认值**: 200
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/5-background-writer.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/5-background-writer.md
new file mode 100644
index 0000000000000000000000000000000000000000..0ca5f021562729c616b21d0b2430331f6a1a7625
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/5-background-writer.md
@@ -0,0 +1,132 @@
+---
+title: 后端写进程
+summary: 后端写进程
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 后端写进程
+
+介绍后端写（background writer）进程的参数配置。后端写进程的功能就是把共享缓冲区中的脏数据（指共享缓冲区中新增或者修改的内容）写入到磁盘。目的是让数据库进程在进行用户查询时可以很少或者几乎不等待写动作的发生（写动作由后端写进程完成）。
+
+此机制同样也减少了检查点造成的性能下降。后端写进程将持续的把脏页面刷新到磁盘上，所以在检查点到来的时候，只有几个页面需要刷新到磁盘上。但是这样还是增加了I/O的总净负荷，因为以前的检查点间隔里，一个重复弄脏的页面可能只会冲刷一次，而同一个间隔里，后端写进程可能会写好几次。在大多数情况下，连续的低负荷要比周期性的尖峰负荷好，但是在本节讨论的参数可以用于按实际需要调节其行为。
+
+## bgwriter_thread_num
+
+**参数说明**：设置用于增量检查点打开后后台刷页的线程数，将可以淘汰的脏页刷盘，不脏的页面放入到候选buffer链，设置此选项有助于加快buffer淘汰速度，提升性能。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：整型，0～8
+
+- 开发期间为测试关闭该特性的效果，可以设置为0，但是当前如果设置为0，会在代码中修正为1，不再支持关闭该特性。
+- 当参数设置为1~8时，表示会启动相对应数量的background线程，用于维护候选buffer链，将满足条件的脏页刷盘，不脏的页放入到候选list中。
+
+**默认值**：2
+
+## bgwriter_delay
+
+**参数说明**: 设置后端写进程写“脏”共享缓冲区之间的时间间隔。每一次，后端写进程都会为一些脏的缓冲区发出写操作（用bgwriter_lru_maxpages参数控制每次写的量），然后休眠bgwriter_delay毫秒后才再次启动。
+
+在许多系统上，休眠延时的有效分辨率是10毫秒。因此，设置一个不是10的倍数的数值与把它设置为下一个10的倍数是一样的效果。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，10~10000，单位为毫秒。
+
+**默认值**: 2s
+
+**设置建议:**在数据写压力比较大的场景中可以尝试减小该值以降低checkpoint的压力。
+
+## candidate_buf_percent_target
+
+**参数说明**：设置用于增量检查点打开时，候选buffer链中可用buffer数目占据shared_buffer内存缓冲区百分比的期望值，当前候选链中的数目少于目标值时，bgwriter线程会启动将满足条件的脏页刷盘。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：双精度浮点类型，0.1～0.85
+
+**默认值**：0.3
+
+## bgwriter_lru_maxpages
+
+**参数说明**: 设置后端写进程每次可写入磁盘的"脏"缓存区的个数。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，0～1000
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+>
+> 此参数设置为0表示禁用后端写功能，禁用后端写功能不会对checkpoints产生影响。
+
+**默认值**: 100
+
+## bgwriter_lru_multiplier
+
+**参数说明**: 通过与已使用缓存区数目的乘积评估下次服务器需要的缓存区数目。
+
+写"脏"缓存区到磁盘的数目取决于服务器最近几次使用的缓存区数目。最近的buffers数目的平均值乘以bgwriter_lru_multiplier是为了评估下次服务器进程需要的buffers数目。在有足够多的干净的、可用的缓存区之前，后端写进程会一直写"脏"缓存区的（每次写的缓存区数目不会超过bgwriter_lru_maxpages的值）。
+
+设置bgwriter_lru_multiplier的值为1.0表示一种"实时"策略，其作用是精准预测下次写"脏"缓冲区的数目。设置为较大的值可以应对突然的需求高峰，而较小的值则可以让服务器进程执行更多的写操作。
+
+设置较小的bgwriter_lru_maxpages和bgwriter_lru_multiplier会减小后端写进程导致的额外I/O开销，但是服务器进程必须自己发出写操作，增加了对查询的响应时间。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**浮点型，0~10。
+
+**默认值**: 2
+
+## pagewriter_thread_num
+
+**参数说明**：设置用于增量检查点打开后后台刷页的线程数，主要是按照脏页置脏的顺序刷盘，用于推进recovery点。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：整型，1～16
+
+**默认值**：4
+
+## dirty_page_percent_max
+
+**参数说明**：设置用于增量检查点打开后脏页数量占shared_buffers的百分比。达到这个设定值时，后台刷页线程将以设置的max_io_capacity计算出的最大值刷脏页。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：浮点型，0.1～1
+
+**默认值**：0.9
+
+## pagewriter_sleep
+
+**参数说明**：设置用于增量检查点打开后，pagewrite线程每隔pagewriter_sleep的时间刷一批脏页下盘。当脏页占据shared_buffers的比例达到dirty_page_percent_max时，每批页面数量以设定的max_io_capacity计算出的值刷页，其余情况每批页面数量按比例相对减少。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：整型，0～3600000（毫秒）
+
+**默认值**：2000ms
+
+## max_io_capacity
+
+**参数说明**: 设置后端写进程批量刷页每秒的IO上限，需要根据具体业务场景和机器磁盘IO能力进行设置。要求RTO很短时间或者数据量比共享内存大多倍的情况，业务访问数据量又是随机访问时，该值不宜过小。该参数设置较小会减小后端写进程刷页个数，如果业务触发页面淘汰多时，该值设置小会影响业务。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，30720~10485760。单位是KB。
+
+**默认值**: 512000KB（500MB）
+
+## enable_consider_usecount
+
+**参数说明**: 设置backend线程在页面置换时是否考虑页面热度，建议大容量场景下开启此参数。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on/true表示考虑页面热度。
+- off/false表示不考虑页面热度。
+
+**默认值**: off
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/6-asynchronous-io-operations.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/6-asynchronous-io-operations.md
new file mode 100644
index 0000000000000000000000000000000000000000..f862334fb5de69d7d64c567dc801e4741fb0f774
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/4-resource-consumption/6-asynchronous-io-operations.md
@@ -0,0 +1,149 @@
+---
+title: 异步IO
+summary: 异步IO
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 异步IO
+
+## enable_adio_debug
+
+**参数说明**: 允许维护人员输出一些与ADIO相关的日志，便于定位ADIO相关问题。开发人员专用，不建议普通用户使用。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on/true表示开启此日志开关。
+- off/false表示关闭此日志开关。
+
+**默认值**: off
+
+## enable_adio_function
+
+**参数说明**: 是否开起ADIO功能。
+
+当前版本暂不支持开启异步IO功能，默认该功能关闭，请勿自行修改。
+
+**取值范围:**布尔型
+
+- on/true表示开启此功能。
+- off/false表示关闭此功能。
+
+**默认值**: off
+
+## enable_fast_allocate
+
+**参数说明**: 磁盘空间快速分配开关。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。只有在XFS文件系统上才能开启该开关。
+
+**取值范围:**布尔型
+
+- on/true表示开启此功能。
+- off/false表示关闭此功能。
+
+**默认值**: off
+
+## prefetch_quantity
+
+**参数说明**: 描述行存储使用ADIO预读取IO量的大小。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，128～131072，单位为8KB。
+
+**默认值**: 32MB (4096 * 8KB)
+
+## backwrite_quantity
+
+**参数说明**: 描述行存储使用ADIO预读取IO量的大小。
+
+**参数说明**: 描述行存储使用ADIO写入IO量的大小。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，128～131072，单位为8KB。
+
+**默认值**: 8MB (1024 * 8KB)
+
+## cstore_prefetch_quantity
+
+**参数说明**: 描述列存储使用ADIO预取IO量的大小。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，1024～1048576，单位为KB。
+
+**默认值**: 32MB
+
+## cstore_backwrite_quantity
+
+**参数说明**: 描述列存储使用ADIO写入IO量的大小。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，1024～1048576，单位为KB。
+
+**默认值**: 8MB
+
+## cstore_backwrite_max_threshold
+
+**参数说明**: 描述列存储使用ADIO写入数据库可缓存最大的IO量。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，4096～INT_MAX/2，单位为KB。
+
+**默认值**: 2GB
+
+## fast_extend_file_size
+
+**参数说明**: 描述列存储使用ADIO预扩展磁盘的大小。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，1024～1048576，单位为KB。
+
+**默认值**: 8MB
+
+## effective_io_concurrency
+
+**参数说明**: 磁盘子系统可以同时有效处理的请求数。对于RAID阵列，此参数应该是阵列中驱动器主轴的数量。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型 ，0~1000
+
+**默认值**: 1
+
+## checkpoint_flush_after
+
+**参数说明**：设置checkpointer线程刷页个数超过设定的阈值时，告知操作系统开始将操作系统缓存中的页面异步刷盘。MogDB中，磁盘页大小为8KB。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：整型，0~256（0表示关闭异步刷盘功能）。例如，取值32，表示checkpointer线程连续写32个磁盘页，即32*8=256KB磁盘空间后会进行异步刷盘。
+
+**默认值**：32
+
+## bgwriter_flush_after
+
+**参数说明**：设置background writer线程刷页个数超过设定的阈值时，告知操作系统开始将操作系统缓存中的页面异步刷盘。MogDB中，磁盘页大小为8KB。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：整型，0~256（0表示关闭异步刷盘功能），单位页面（8KB）。例如，取值64，表示background writer线程连续写64个磁盘页，即64*8=512KB磁盘空间后会进行异步刷盘。
+
+**默认值**：512KB（即64个页面）
+
+## backend_flush_after
+
+**参数说明**：设置backend线程刷页个数超过设定的阈值时，告知操作系统开始将操作系统缓存中的页面异步刷盘。MogDB中，磁盘页大小为8KB。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：整型，0~256（0表示关闭异步刷盘功能），单位页面（8KB）。例如，取值64，表示backend线程连续写64个磁盘页，即64*8=512KB磁盘空间后会进行异步刷盘。
+
+**默认值**：0
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/40-AI-features.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/40-AI-features.md
new file mode 100644
index 0000000000000000000000000000000000000000..8571058bde7423226245e9bce9fe3d3f2055688a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/40-AI-features.md
@@ -0,0 +1,64 @@
+---
+title: AI特性
+summary: AI特性
+author: Zhang Cuiping
+date: 2021-11-08
+---
+
+# AI特性
+
+## enable_hypo_index
+
+**参数说明**: 该参数控制数据库的优化器进行EXPLAIN时是否考虑创建虚拟索引。通过对特定的查询语句执行explain，用户可根据优化器给出的执行计划评估该索引是否能够提升该查询语句的执行效率。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示在进行EXPLAIN时创建虚拟索引。
+- off表示在进行EXPLAIN时不创建虚拟索引。
+
+**默认值**: off
+
+## db4ai_snapshot_mode
+
+**参数说明**: snapshot有2种模式：MSS（物化模式，存储数据实体）和CSS（计算模式，存储增量信息）。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串，MSS/CSS
+
+- MSS表示物化模式，db4ai在创建快照的时候存储数据实体。
+- CSS表示计算模式，db4ai在创建快照的时候存储增量信息。
+
+**默认值**: MSS
+
+## db4ai_snapshot_version_delimiter
+
+**参数说明**: 该参数为数据表快照版本分隔符。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串，长度大于0
+
+**默认值**: @
+
+## db4ai_snapshot_version_separator
+
+**参数说明**: 该参数用于指定数据表快照子版本分隔符。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串，长度大于0
+
+**默认值**: .
+
+## unix_socket_directory
+
+**参数说明**: 用于指定unix_socket通信方式中，文件存放的路径。此参数只能在配置文件postgresql.conf中指定。再启动fenced模式前需要设定该GUC参数。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串，长度大于等于0
+
+**默认值**: “
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/5-parallel-import.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/5-parallel-import.md
new file mode 100644
index 0000000000000000000000000000000000000000..4f3c01f85b0b5a8159a074c9a01becffaec07666
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/5-parallel-import.md
@@ -0,0 +1,58 @@
+---
+title: 并行导入
+summary: 并行导入
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 并行导入
+
+MogDB提供了并行导入功能，以快速、高效地完成大量数据导入。介绍MogDB并行导入的相关参数。
+
+## raise_errors_if_no_files
+
+**参数说明**: 导入时是否区分"导入文件记录数为空"和"导入文件不存在"。raise_errors_if_no_files=TRUE，则"导入文件不存在"的时候，MogDB将抛出"文件不存在的"错误。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示导入时区分"导入文件记录数为空"和"导入文件不存在"。
+- off表示导入时不区分"导入文件记录数为空"和"导入文件不存在"。
+
+**默认值**: off
+
+## partition_mem_batch
+
+**参数说明**: 为了优化对列存分区表的批量插入，在批量插入过程中会对数据进行缓存后再批量写盘。通过partition_mem_batch可指定缓存个数。该值设置过大，将消耗较多系统内存资源；设置过小，将降低系统列存分区表批量插入性能。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 1~ 65535
+
+**默认值**: 256
+
+## partition_max_cache_size
+
+**参数说明**: 为了优化对列存分区表的批量插入，在批量插入过程中会对数据进行缓存后再批量写盘。通过partition_max_cache_size可指定数据缓存区大小。该值设置过大，将消耗较多系统内存资源；设置过小，将降低列存分区表批量插入性能。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**:
+
+列存分区表: 4096~ INT_MAX / 2，最小单位为KB。
+
+**默认值**: 2GB
+
+## enable_delta_store
+
+**参数说明**: 为了增强列存单条数据导入的性能和解决磁盘冗余问题，可通过此参数选择是否开启支持列存delta表功能。该参数开启时，数据导入列存表，会根据表定义时指定的DELTAROW_THRESHOLD决定数据进入delta表存储还是主表CU存储，当数据量小于DELTAROW_THRESHOLD时，数据进入delta表。该参数影响的操作包括insert，copy，vacuum，vacuum full，vacuum deltamerge重分布等所有涉及列存表数据移动的操作。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**:
+
+- on表示开启列存delta表功能。
+- off表示不开启列存delta表功能。
+
+**默认值**: off
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/1-settings.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/1-settings.md
new file mode 100644
index 0000000000000000000000000000000000000000..6a97c9dc6ec343f8f0383c3c1417900bb9d3d795
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/1-settings.md
@@ -0,0 +1,264 @@
+---
+title: 设置
+summary: 设置
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 设置
+
+## wal_level
+
+**参数说明**: 设置写入WAL信息量的级别。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+>
+> - 如果需要启用WAL日志归档和主备机的数据流复制，必须将此参数设置为archive或者hot_standby。
+> - 如果此参数设置为minimal，archive_mode必须设置为off，hot_standby必须设置为off，max_wal_senders参数设置为0，且需为单机环境，否则将导致数据库无法启动。
+> - 如果此参数设置为archive，hot_standby必须设置为off，否则将导致数据库无法启动。但是，hot_standby在双机环境中不能设置为off，具体参见hot_standby参数说明。
+
+**取值范围**: 枚举类型
+
+- minimal
+
+  优点: 一些重要操作（包括创建表、创建索引、簇操作和表的复制）都能安全的跳过，这样就可以使操作变得更快。
+
+  缺点: WAL仅提供从数据库服务器崩溃或者紧急关闭状态恢复时所需要的基本信息，无法用WAL归档日志恢复数据。
+
+- archive
+
+  这个参数增加了WAL归档需要的日志信息，从而可以支持数据库的归档恢复。
+
+- hot_standby
+
+  - 这个参数进一步增加了在备机上运行的SQL查询的信息，这个参数只能在数据库服务重新启动后生效。
+  - 为了在备机上开启只读查询，wal_level必须在主机上设置成hot_standby ，并且备机必须打开hot_standby参数。hot_standby和archive级别之间的性能只有微小的差异，如果它们的设置对产品的性能影响有明显差异，欢迎反馈。
+
+- logical
+
+  这个参数表示WAL日志支持逻辑复制。
+
+**默认值**: hot_standby
+
+## fsync
+
+**参数说明**: 设置MogDB服务器是否使用fsync()系统函数（请参见[wal_sync_method](#wal_sync_method)）确保数据的更新及时写入物理磁盘中。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+>
+> - 使用fsync()系统函数可以保证在操作系统或者硬件崩溃的情况下将数据恢复到一个已知的状态。
+> - 如果将此参数关闭，可能会在系统崩溃时无法恢复原来的数据，导致数据库不可用。
+
+**取值范围:**布尔型
+
+- on表示使用fsync()系统函数。
+- off表示不使用fsync()系统函数。
+
+**默认值**: on
+
+## synchronous_commit
+
+**参数说明**: 设置当前事务的同步方式。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 枚举类型
+
+- on表示将备机的同步日志刷新到磁盘。
+- off表示异步提交。
+- local表示为本地提交。
+- remote_write表示要备机的同步日志写到磁盘。
+- remote_receive表示要备机同步日志接收数据。
+- remote_apply表示要备机同步日志回放完成。
+- true表示将备机的同步日志刷新到磁盘。
+- false表示异步提交。
+- yes表示将备机的同步日志刷新到磁盘。
+- no表示异步提交。
+- 1表示将备机的同步日志刷新到磁盘。
+- 0表示异步提交。
+- 2表示将备机同步日志回放完成。
+
+**默认值**: off
+
+## wal_sync_method
+
+**参数说明**: 设置向磁盘强制更新WAL数据的方法。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+>
+> 如果将[fsync](#fsync)关闭，这个参数的设置就没有意义，因为所有数据更新都不会强制写入磁盘。
+
+**取值范围**: 枚举类型
+
+- open_datasync表示用带O_DSYNC选项的open()打开"WAL"文件。
+
+- fdatasync表示每次提交的时候都调用fdatasync()。（支持suse10和suse11）。
+
+- fsync_writethrough表示每次提交的时候调用fsync()强制把缓冲区任何数据写入磁盘。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+  >
+  > 由于历史原因，Windows平台支持将wal_sync_method设置为fsync_writethrough。在windows平台上fsync_writethrough和fsync等效。
+
+- fsync表示每次提交的时候调用fsync()。（支持suse10和suse11）
+
+- open_sync表示用带O_SYNC选项的open()写"WAL"文件。（支持suse10和suse11）
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+  >
+  > 不是所有的平台都支持以上参数。
+
+**默认值**: fdatasync
+
+## full_page_writes
+
+**参数说明**: 设置MogDB服务器在检查点之后对页面的第一次修改时，是否将每个磁盘页面的全部内容写到WAL日志中。当增量检查点开关和enable_double_write同时打开时，则不使用full_page_writes。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+>
+> - 设置这个参数是因为在操作系统崩溃过程中可能磁盘页面只写入了一部分内容，从而导致在同一个页面中包含新旧数据的混合。在崩溃后的恢复期间，由于在WAL日志中存储的行变化信息不够完整，因此无法完全恢复该页。把完整的页面影像保存下来就可以保证页面被正确还原，代价是增加了写入WAL日志的数据量。
+> - 关闭此参数，在系统崩溃的时候，可能无法恢复原来的数据。如果服务器硬件的特质（比如电池供电的磁盘控制器）可以减小部分页面的写入风险，或者文件系统特性支持（比如ReiserFS 4），并且清楚知道写入风险在一个可以接受的范畴，可以关闭这个参数。
+
+**取值范围:**布尔型
+
+- on表示启用此特性。
+- off表示关闭此特性。
+
+**默认值**: on
+
+## wal_log_hints
+
+**参数说明**: 设置在检查点之后对页面的第一次修改为页面上元组hint bits的修改时，是否将整个页面的全部内容写到WAL日志中。不推荐用户修改此设置。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示整个页面全部内容写到WAL日志中。
+- off表示整个页面内容不会写到WAL日志中。
+
+**默认值**: on
+
+## wal_buffers
+
+**参数说明**: 设置用于存放WAL数据的共享内存空间的XLOG_BLCKSZ数，XLOG_BLCKSZ的大小默认为8KB。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**-1~218
+
+- 如果设置为-1，表示wal_buffers的大小随着参数shared_buffers自动调整，为shared_buffers的1/32，最小值为8个XLOG_BLCKSZ，最大值为2048个XLOG_BLCKSZ。
+- 如果设置为其他值，当小于4时，会被默认设置为4。
+
+**默认值**: 16MB
+
+**设置建议:**每次事务提交时，WAL缓冲区的内容都写入到磁盘中，因此设置为很大的值不会带来明显的性能提升。如果将它设置成几百兆，就可以在有很多即时事务提交的服务器上提高写入磁盘的性能。根据经验来说，默认值可以满足大多数的情况。
+
+## wal_writer_delay
+
+**参数说明**: WalWriter进程的写间隔时间。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+>
+> 如果时间过长可能造成WAL缓冲区的内存不足，时间过短会引起WAL不断写入，增加磁盘I/O负担。
+
+**取值范围**: 整型， 1～10000，单位为毫秒。
+
+**默认值**: 200ms
+
+## commit_delay
+
+**参数说明**: 表示一个已经提交的数据在WAL缓冲区中存放的时间。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+>
+> - 设置为非 0 值时事务执行commit后不会立即写入WAL中，而仍存放在WAL缓冲区中，等待WalWriter进程周期性写入磁盘。
+> - 如果系统负载很高，在延迟时间内，其他事务可能已经准备好提交。但如果没有事务准备提交，这个延迟就是在浪费时间。
+
+**取值范围**: 整型， 0～100000，单位为微秒，其中0表示无延迟。
+
+**默认值**: 0
+
+## commit_siblings
+
+**参数说明**: 当一个事务发出提交请求时，如果数据库中正在执行的事务数量大于此参数的值，则该事务将等待一段时间（[commit_delay](#commit_delay)的值），否则该事务则直接写入WAL。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型， 0～1000
+
+**默认值**: 5
+
+## wal_block_size
+
+**参数说明**: 说明WAL日志段文件中日志页面的大小。
+
+该参数属于INTERNAL类型参数，为固定参数，用户无法修改此参数，只能查看。
+
+**取值范围**: 整型，单位为Byte。
+
+**默认值**: 8192
+
+## wal_segment_size
+
+**参数说明**: 说明WAL日志段文件的大小。
+
+该参数属于INTERNAL类型参数，为固定参数，用户无法修改此参数，只能查看。
+
+**取值范围**: 整型，单位为8KB。
+
+**默认值**: 16MB (2048 * 8KB)
+
+## walwriter_cpu_bind
+
+**参数说明**: 绑定到WAL写入线程的CPU核，与thread pool配合使用。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：整型，-1~核数减1。
+
+**默认值**: -1
+
+## walwriter_sleep_threshold
+
+**参数说明**: xlogflusher进入sleep之前空闲xlog刷新的次数，达到阈值会休眠。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：整型，1~50000。
+
+**默认值**: 500
+
+## wal_file_init_num
+
+**参数说明**: WAL编写器将创建的xlog段文件的数量。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：整型，0~1000000。
+
+**默认值**: 10
+
+## force_promote
+
+**参考说明：**备机强切功能开关。
+
+备机强切在集群故障状态下，以丢失部分数据为代价换取集群尽可能快的恢复服务；是集群状态为不可用时的一个逃生方法，不建议频繁触发。如果操作者不清楚备机强切后丢失数据对业务的影响，请勿使用本功能。
+
+**取值范围**: 整型，0或1
+
+0表示关闭，1表示开启
+
+**默认值**: 0
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/2-checkpoints.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/2-checkpoints.md
new file mode 100644
index 0000000000000000000000000000000000000000..369c11f4c2343b3ad3f95b3f96dd1853c77f0950
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/2-checkpoints.md
@@ -0,0 +1,130 @@
+---
+title: 检查点
+summary: 检查点
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 检查点
+
+## checkpoint_segments
+
+**参数说明**: 设置[checkpoint_timeout](#checkpoint_timeout)周期内所保留的最少WAL日志段文件数量。每个日志文件大小为16MB。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，最小值1
+
+提升此参数可加快大数据的导入速度，但需要结合[checkpoint_timeout](#checkpoint_timeout)、shared_buffers这两个参数统一考虑。这个参数同时影响WAL日志段文件复用数量，通常情况下pg_xlog文件夹下最大的复用文件个数为2倍的checkpoint_segments个，复用的文件被改名为后续即将使用的WAL日志段文件，不会被真正删除。
+
+**默认值**: 64
+
+## checkpoint_timeout
+
+**参数说明**: 设置自动WAL检查点之间的最长时间。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，30～3600（秒）
+
+在提升[checkpoint_segments](#checkpoint_segments)以加快大数据导入的场景也需将此参数调大，同时这两个参数提升会加大shared_buffers的负担，需要综合考虑。
+
+**默认值**: 15min
+
+## checkpoint_completion_target
+
+**参数说明**: 指定检查点完成的目标。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 0.0～1.0
+
+**默认值**: 0.5
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+> 默认值0.5表示每个checkpoint需要在checkpoints间隔时间的50%内完成。
+
+## checkpoint_warning
+
+**参数说明**: 如果由于填充检查点段文件导致检查点发生的时间间隔接近这个参数表示的秒数，就向服务器日志发送一个建议增加[checkpoint_segments](#checkpoint_segments)值的消息。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，0~INT_MAX（秒），其中0表示关闭警告。
+
+**默认值**: 5min
+
+**推荐值**: 5min
+
+## checkpoint_wait_timeout
+
+**参数说明**: 设置请求检查点等待checkpointer线程启动的最长时间。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，2～3600（秒）
+
+**默认值**: 1min
+
+## enable_incremental_checkpoint
+
+**参数说明**: 增量检查点开关。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+**默认值**: on
+
+## enable_double_write
+
+**参数说明**: 双写开关。当增量检查点开关打开时，同时enable_double_write打开，则使用enable_double_write双写特性保护，不再使用full_page_writes防止半页写问题。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+**默认值**: on
+
+## incremental_checkpoint_timeout
+
+**参数说明**: 增量检查点开关打开之后，设置自动WAL检查点之间的最长时间。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，1~3600（秒）
+
+**默认值**: 1min
+
+## enable_xlog_prune
+
+**参数说明**: 设置在任一备机断联时，主机是否根据xlog日志的大小超过参数max_size_for_xlog_prune的值而回收日志。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- 设置为on时，如果任一备机断联时，主机不回收日志。
+- 设置为off时，如果任一备机断联时，主机回收日志。
+
+**默认值**: on
+
+## max_redo_log_size
+
+**参数说明**: 备DN表示当前回放的最新检查点位置和当前日志回放位置之间日志量的期望值，主DN表示恢复点到当前最新日志之间日志量的期望值，关注RTO的情况下，这个值建议不宜过大。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，163840~2147483647，单位为KB。
+
+**默认值**: 1GB
+
+## max_size_for_xlog_prune
+
+**参数说明**: 在enable_xlog_prune打开时生效，如果有备机断连且xlog日志大小大于此阈值，则回收日志。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，0～2147483647，单位为KB
+
+**默认值**: 2147483647，单位KB
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/3-log-replay.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/3-log-replay.md
new file mode 100644
index 0000000000000000000000000000000000000000..8f39c5a2acb78f1dd3a04cb52d20bd1e9b35c7bb
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/3-log-replay.md
@@ -0,0 +1,96 @@
+---
+title: 日志回放
+summary: 日志回放
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 日志回放
+
+## recovery_time_target
+
+**参数说明**: 设置recovery_time_target秒能够让备机完成日志写入和回放。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，0~3600（秒）
+
+0是指不开启日志流控，1~3600是指备机能够在recovery_time_target时间内完成日志的写入和回放，可以保证主机与备机切换时能够在recovery_time_target秒完成日志写入和回放，保证备机能够快速升主机。recovery_time_target设置时间过小会影响主机的性能，设置过大会失去流控效果。
+
+**默认值**: 0
+
+## recovery_max_workers
+
+**参数说明**: 设置最大并行回放线程个数。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，0~20
+
+**默认值**: 1 （安装工具默认将设置为4以获得更好的性能）
+
+## recovery_parse_workers
+
+**参数说明**: 是极致RTO特性中ParseRedoRecord线程的数量。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，1~16
+
+仅在开启极致RTO情况下可以设置recovery_parse_workers为&gt;1。需要配合recovery_redo_workers使用。若同时开启recovery_parse_workers和recovery_max_workers，以开启极致RTO的recovery_parse_workers为准，并行回放特性失效。因极致RTO不支持hot standby模式和主备从模式, 仅在参数hot_standby设置成off，replication_type设置成1时可以设置recovery_parse_workers为&gt;1。另外，极致RTO也不支持列存，在已经使用列存表或者即将使用列存表的系统中，请关闭极致RTO。
+
+**默认值**: 1
+
+## recovery_redo_workers
+
+**参数说明**: 是极致RTO特性中每个ParseRedoRecord线程对应的PageRedoWorker数量。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，1~8
+
+需要配合recovery_parse_workers使用。在配合recovery_parse_workers使用时，只有recovery_parse_workers大于0，recovery_redo_workers参数才生效。
+
+**默认值**: 1
+
+## recovery_parallelism
+
+**参数说明**: 查询实际回放线程个数，该参数为只读参数。
+
+**取值范围**: 整型，1~2147483647
+
+该参数受参数: recovery_max_workers及参数: recovery_parse_workers影响，上述任意一参数值大于0时，该参数值将重新计算。
+
+**默认值**: 1
+
+## enable_page_lsn_check
+
+**参数说明**: 数据页lsn检查开关。回放时，检查数据页当前的lsn是否是期望的lsn。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+**默认值**: on
+
+## recovery_min_apply_delay
+
+**参数说明**: 设置备节点回放的延迟时间。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+>
+> - 此参数主节点设置无效，必须设置在需要延迟的备节点上。
+> - 延迟时间是根据主服务器上事物提交的时间戳与备机上的当前时间来计算，因此需要保证主备系统时钟一致。
+> - 延迟时间设置过长时，可能会导致该备机XLOG文件所在的磁盘满，需要平衡考虑磁盘大小来设置延迟时间。
+> - 没有事务的操作不会被延迟。
+> - 主备切换之后，原主机若需延迟，需要再手动配置此参数。
+> - 当synchronous_commit被设置为remote_apply时，同步复制会受到这个延时的影响，每一个COMMIT都需要等待备机回放结束后才会返回。
+> - 使用这个特性也会让hot_standby_feedback被延迟，这可能导致主服务器的膨胀，两者一起使用时要小心。
+> - 主机执行了持有AccessExclusive锁的DDL操作，比如DROP和TRUNCATE操作，在备机延迟回放该条记录期间，在备机上对该操作对象执行查询操作会等待锁释放之后才会返回。
+> - 不支持MOT表。
+
+**取值范围**: 整型，0~INT_MAX，单位为毫秒。
+
+**默认值**: 0（不增加延迟）
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/4-archiving.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/4-archiving.md
new file mode 100644
index 0000000000000000000000000000000000000000..9f7029558ba6618e4f645977f277986705cfb0e3
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/6-write-ahead-log/4-archiving.md
@@ -0,0 +1,92 @@
+---
+title: 归档
+summary: 归档
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 归档
+
+## archive_mode
+
+**参数说明**: 表示是否进行归档操作。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> 当wal_level设置成minimal时，archive_mode参数无法使用。
+
+**取值范围**: 布尔型
+
+- on表示进行归档。
+- off表示不进行归档。
+
+**默认值**: off
+
+## archive_command
+
+**参数说明**: 由管理员设置的用于归档WAL日志的命令，建议归档路径为绝对路径。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+>
+> - 当archive_dest和archive_command同时配置时，WAL日志优先保存到archive_dest所设置的目录中，archive_command配置的命令不生效。
+>
+> - 字符串中任何%p都被要归档的文件的绝对路径代替，而任何%f都只被该文件名代替（相对路径都相对于数据目录的）。如果需要在命令里嵌入%字符就必须双写%。
+>
+> - 这个命令当且仅当成功的时候才返回零。示例如下:
+>
+>   ```
+>   archive_command = 'cp --remove-destination %p /mnt/server/archivedir/%f'
+>   ```
+>
+> - -remove-destination选项作用为: 拷贝前如果目标文件已存在，会先删除已存在的目标文件，然后执行拷贝操作。
+>
+> - 如果归档命令有多条，则需将其写入SHELL脚本文件中，然后将archive_command配置为执行该脚本的命令。示例如下:
+>
+>   ```sql
+>   --假设多条命令如下。
+>   test ! -f dir/%f && cp %p dir/%f
+>   --则test.sh脚本内容如下。
+>   test ! -f dir/$2 && cp $1 dir/$2
+>   --归档命令如下。
+>   archive_command='sh dir/test.sh %p %f'
+>   ```
+
+**取值范围**: 字符串
+
+**默认值**: (disabled)
+
+## archive_dest
+
+**参数说明**: 由管理员设置的用于归档WAL日志的目录，建议归档路径为绝对路径。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+>
+> - 当archive_dest和archive_command同时配置时，WAL日志优先保存到archive_dest所设置的目录中，archive_command配置的命令不生效。
+>
+> - 字符串中如果是相对路径为相对于数据目录的。示例如下。
+>
+>   ```
+>   archive_dest = '/mnt/server/archivedir/'
+>   ```
+
+**默认值**: 空字符串
+
+## archive_timeout
+
+**参数说明**: 表示归档周期。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+>
+> - 超过该参数设定的时间时强制切换WAL段。
+> - 由于强制切换而提早关闭的归档文件仍然与完整的归档文件长度相同。因此，将archive_timeout设为很小的值将导致占用巨大的归档存储空间，建议将archive_timeout设置为60秒。
+
+**取值范围**: 整型，0 ~ INT_MAX，单位为秒。其中0表示禁用该功能。
+
+**默认值**: 0
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/7-ha-replication/1-sending-server.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/7-ha-replication/1-sending-server.md
new file mode 100644
index 0000000000000000000000000000000000000000..aaa04d4204810e0f2538ada114e0a2896f3c8189
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/7-ha-replication/1-sending-server.md
@@ -0,0 +1,374 @@
+---
+title: 发送端服务器
+summary: 发送端服务器
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 发送端服务器
+
+## max_wal_senders
+
+**参数说明**: 指定事务日志发送进程的并发连接最大数量。不可大于等于max_connections。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:** wal_level必须设置为archive或者hot_standby以允许备机的连接。
+
+**取值范围**: 整型，0～262143
+
+**默认值**: 16
+
+## wal_keep_segments
+
+**参数说明**: Xlog日志文件段数量。设置"pg_xlog"目录下保留事务日志文件的最小数目，备机通过获取主机的日志进行流复制。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，2 ~ INT_MAX
+
+**默认值**: 16
+
+**设置建议:**
+
+- 当服务器开启日志归档或者从检查点恢复时，保留的日志文件数量可能大于wal_keep_segments设定的值。
+- 如果此参数设置过小，则在备机请求事务日志时，此事务日志可能已经被产生的新事务日志覆盖，导致请求失败，主备关系断开。
+- 当双机为异步传输时，以COPY方式连续导入4G以上数据需要增大wal_keep_segments配置。以T6000单板为例，如果导入数据量为50G，建议调整参数为1000。您可以在导入完成并且日志同步正常后，动态恢复此参数设置。
+- 若 synchronous_commit 级别小于LOCAL_FLUSH，重建备机时，建议调大改参数为1000，避免重建过程中，主机日志回收导致重建失败。
+
+## wal_sender_timeout
+
+**参数说明**: 设置本端等待事务日志接收端接收日志的最大等待时间。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+>
+> - 如果主机数据较大，重建备机数据库时需要增大此参数的值，主机数据在 500G时，此参数的参考值为600s。
+> - 此值不能大于wal_receiver_timeout或数据库重建时的超时参数。
+
+**取值范围:**整型，0 ~ INT_MAX，单位为毫秒（ms）。
+
+**默认值**: 6s
+
+## max_replication_slots
+
+**参数说明**: 设置主机端的日志复制slot个数。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型， 0~262143。
+
+**默认值**: 8
+
+**设置建议**:
+
+使用逻辑解码时，该参数值建议设为: 当前物理流复制槽数+所需的逻辑复制槽数。
+
+- 物理流复制槽提供了一种自动化的方法来确保主节点在所有备节点或从备节点收到xlog之前，xlog不会被移除。也就是说物理流复制槽用于支撑主备HA。数据库所需要的物理流复制槽数为备节点加从备的和与主节点之间的比例。例如，假设数据库高可用方案为1主、1备、1从备，则所需物理流复制槽数为2。假设数据库的高可用方案为1主3备，则所需物理流复制槽数为3。
+- 关于逻辑复制槽数，请按如下规则考虑:
+  - 一个逻辑复制槽只能解码一个数据库的修改，如果需要解码多个数据库，则需要创建多个逻辑复制槽。
+  - 如果需要多路逻辑复制同步给多个目标数据库，在源端数据库需要创建多个逻辑复制槽，每个逻辑复制槽对应一条逻辑复制链路。
+
+## enable_slot_log
+
+**参数说明**: 是否开启逻辑复制槽主备同步特性。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示开启逻辑复制槽主备同步特性。
+- off表示不开启逻辑复制槽主备同步特性。
+
+**默认值**: off
+
+## max_changes_in_memory
+
+**参数说明**: 逻辑解码时单条事务在内存中缓存的大小上限，单位字节。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，1~2147483647
+
+**默认值**: 4096
+
+## max_cached_tuplebufs
+
+**参数说明**: 逻辑解码时总元组信息在内存中缓存的大小上限，单位字节。建议设置为max_changes_in_memory的两倍以上。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，1~2147483647
+
+**默认值**: 8192
+
+## replconninfo1
+
+**参数说明**: 设置本端侦听和鉴权的第一个节点信息。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串。其中空字符串表示没有配置第一个节点信息。
+
+**默认值**: 空字符串
+
+## replconninfo2
+
+**参数说明**: 设置本端侦听和鉴权的第二个节点信息。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串。其中空字符串表示没有配置第二个节点信息。
+
+**默认值**: 空字符串
+
+## replconninfo3
+
+**参数说明**: 设置本端侦听和鉴权的第三个节点信息。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串。其中空字符串表示没有配置第三个节点信息。
+
+**默认值**: 空字符串
+
+## replconninfo4
+
+**参数说明**: 设置本端侦听和鉴权的第四个节点信息。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串。其中空字符串表示没有配置第四个节点信息。
+
+**默认值**: 空字符串
+
+## replconninfo5
+
+**参数说明**: 设置本端侦听和鉴权的第五个节点信息。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串。其中空字符串表示没有配置第五个节点信息。
+
+**默认值**: 空字符串
+
+## replconninfo6
+
+**参数说明**: 设置本端侦听和鉴权的第六个节点信息。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串。其中空字符串表示没有配置第六个节点信息。
+
+**默认值**: 空字符串
+
+## replconninfo7
+
+**参数说明**: 设置本端侦听和鉴权的第七个节点信息。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串。其中空字符串表示没有配置第七个节点信息。
+
+**默认值**: 空字符串
+
+## replconninfo8
+
+**参数说明**: 设置本端侦听和鉴权的第八个节点信息。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串。其中空字符串表示没有配置第八个节点信息。
+
+**默认值**: 空字符串
+
+## replconninfo9
+
+**参数说明**: 设置本端侦听和鉴权的第九个节点信息。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串。其中空字符串表示没有配置第九个节点信息。
+
+**默认值**: 空字符串
+
+## replconninfo10
+
+**参数说明**: 设置本端侦听和鉴权的第十个节点信息。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串。其中空字符串表示没有配置第十个节点信息。
+
+**默认值**: 空字符串
+
+## replconninfo11
+
+**参数说明**: 设置本端侦听和鉴权的第十一个节点信息。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串。其中空字符串表示没有配置第十一个节点信息。
+
+**默认值**: 空字符串
+
+## replconninfo12
+
+**参数说明**: 设置本端侦听和鉴权的第十二个节点信息。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串。其中空字符串表示没有配置第十二个节点信息。
+
+**默认值**: 空字符串
+
+## replconninfo13
+
+**参数说明**: 设置本端侦听和鉴权的第十三个节点信息。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串。其中空字符串表示没有配置第十三个节点信息。
+
+**默认值**: 空字符串
+
+## replconninfo14
+
+**参数说明**: 设置本端侦听和鉴权的第十四个节点信息。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串。其中空字符串表示没有配置第十四个节点信息。
+
+**默认值**: 空字符串
+
+## replconninfo15
+
+**参数说明**: 设置本端侦听和鉴权的第十五个节点信息。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串。其中空字符串表示没有配置第十五个节点信息。
+
+**默认值**: 空字符串
+
+## replconninfo16
+
+**参数说明**: 设置本端侦听和鉴权的第十六个节点信息。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串。其中空字符串表示没有配置第十六个节点信息。
+
+**默认值**: 空字符串
+
+## replconninfo17
+
+**参数说明**: 设置本端侦听和鉴权的第十七个节点信息。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串。其中空字符串表示没有配置第十七个节点信息。
+
+**默认值**: 空字符串
+
+## replconninfo18
+
+**参数说明**: 设置本端侦听和鉴权的第十八个节点信息。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串。其中空字符串表示没有配置第十八个节点信息。
+
+**默认值**: 空字符串
+
+## cross_cluster_replconninfo1
+
+**参数说明**: 设置跨集群的本端侦听和鉴权的第一个节点信息。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串。其中空字符串表示没有配置第一个节点信息。
+
+**默认值**: 空字符串
+
+## cross_cluster_replconninfo2
+
+**参数说明**: 设置跨集群的本端侦听和鉴权的第二个节点信息。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串。其中空字符串表示没有配置第二个节点信息。
+
+**默认值**: 空字符串
+
+## cross_cluster_replconninfo3
+
+**参数说明**: 设置跨集群的本端侦听和鉴权的第三个节点信息。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串。其中空字符串表示没有配置第三个节点信息。
+
+**默认值**: 空字符串
+
+## cross_cluster_replconninfo4
+
+**参数说明**: 设置跨集群的本端侦听和鉴权的第四个节点信息。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串。其中空字符串表示没有配置第四个节点信息。
+
+**默认值**: 空字符串
+
+## cross_cluster_replconninfo5
+
+**参数说明**: 设置跨集群的本端侦听和鉴权的第五个节点信息。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串。其中空字符串表示没有配置第五个节点信息。
+
+**默认值**: 空字符串
+
+## cross_cluster_replconninfo6
+
+**参数说明**: 设置跨集群的本端侦听和鉴权的第六个节点信息。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串。其中空字符串表示没有配置第六个节点信息。
+
+**默认值**: 空字符串
+
+## cross_cluster_replconninfo7
+
+**参数说明**: 设置跨集群的本端侦听和鉴权的第七个节点信息。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串。其中空字符串表示没有配置第七个节点信息。
+
+**默认值**: 空字符串
+
+## cross_cluster_replconninfo8
+
+**参数说明**: 设置跨集群的本端侦听和鉴权的第八个节点信息。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串。其中空字符串表示没有配置第八个节点信息。
+
+**默认值**: 空字符串
+
+## available_zone
+
+**参数说明**: 设置本端节点所在区域信息。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符串。其中空字符串表示没有配置节点信息。
+
+**默认值**: 空字符串
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/7-ha-replication/2-primary-server.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/7-ha-replication/2-primary-server.md
new file mode 100644
index 0000000000000000000000000000000000000000..370325a6cf06b60bb2af721fe5dd3202b026cfc3
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/7-ha-replication/2-primary-server.md
@@ -0,0 +1,215 @@
+---
+title: 主服务器
+summary: 主服务器
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 主服务器
+
+## synchronous_standby_names
+
+**参数说明**: 潜在同步复制的备机名称列表，每个名称用逗号分隔。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+>
+> - 当前连接的同步备机是列表中的第一个名称。如果当前同步备机失去连接，则它会立即更换下一个优先级更高的备机，并将此备机的名称放入列表中。
+> - 备机名称可以通过设置环境变量PGAPPNAME指定。
+
+**取值范围**: 字符串。当取值为*，表示匹配任意提供同步复制的备机名称。支持按如下格式配置：
+
+- ANY **num_sync (standby_name** [, …])
+- [FIRST] **num_sync (standby_name** [, …])
+- **standby_name** [, …]
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 其中 **num_sync** 是事务需要等待其回复的同步复制的备机的数量，**standby_name** 是备机的名称，FIRST以及ANY指定从所列服务器中选取同步复制的备机的策略。
+>
+> - ANY N (node1,node2,…) 表示在括号内任选N个主机名称作为同步复制的备机名称列表。例如，ANY 1 (node1,node2) 表示在node1和node2中任选一个作为同步复制的备机名称。
+>
+> - FIRST N (node1,node2,…)表示在括号内按出现顺序的先后作为优先级选择前N个主机名称作为同步复制的备机名称列表。例如，FIRST 1 (node1,node2)表示选择node1作为同步复制的备机名称。
+>
+> - node1,node2,…和FIRST 1 (node1,node2,…) 具有的含义相同。
+>
+> - 若使用gs_guc工具设置该参数，需要如下设置：
+>
+>   ```
+>   gs_guc reload -Z datanode -N @NODE_NAME@ -D @DN_PATH@ -c "synchronous_standby_names='ANY NODE 1(dn_instanceId1, dn_instanceId2)'";
+>   ```
+>
+> 或者：
+>
+> ```
+>  gs_guc reload -Z datanode -N @NODE_NAME@ -D @DN_PATH@ -c "synchronous_standby_names='ANY 1(AZ1, AZ2)'";
+> ```
+
+**默认值**: *
+
+## most_available_sync
+
+**参数说明**: 在有同步备机故障时，主机事务不因同步备机故障而被阻塞。比如有两个同步备机，一个故障，另一个正常，这个时候主机事务只会等好的这个同步备，而不被故障的同步备所阻塞； 再比如走quroum协议时，一主三同步备，配置ANY 2(node1,node2,node3)，当node1、node3故障，node2正常时，主机业务同样不被阻塞。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示在有同步备机故障时，不阻塞主机。
+- off表示在有同步备机故障时，阻塞主机。
+
+**默认值**: off
+
+## enable_stream_replication
+
+**参数说明**: 控制主备、主从是否进行数据和日志同步。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+>
+> - 此参数属于性能测试参数，用于测试带有备机和不带备机的性能参数。关闭参数后，不能进行切换、故障等异常场景测试，否则会出现主备从不一致的情况。
+> - 此参数属于受控参数，不建议正常业务场景下关闭此参数。
+
+**取值范围:**布尔型
+
+- on表示打开主备、主从同步。
+- off表示关闭主备、主从同步。
+
+**默认值**: on
+
+## enable_mix_replication
+
+**参数说明**: 控制主备、主从之间WAL日志及数据复制的方式。
+
+该参数属于INTERNAL类型参数，默认值为off，不允许外部修改。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+>
+> 此参数目前不允许正常业务场景下改变其值，即关闭WAL日志、数据页混合复制模式。
+
+**取值范围:**布尔型
+
+- on表示打开WAL日志、数据页混合复制模式。
+- off表示关闭WAL日志、数据页混合复制模式。
+
+**默认值**: off
+
+## vacuum_defer_cleanup_age
+
+**参数说明**: 指定VACUUM使用的事务数，VACUUM会延迟清除无效的行存表记录，延迟的事务个数通过vacuum_defer_cleanup_age进行设置。即VACUUM和VACUUM FULL操作不会立即清理刚刚被删除元组。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，0～1000000，值为0表示不延迟。
+
+**默认值**: 0
+
+## data_replicate_buffer_size
+
+**参数说明**: 发送端与接收端传递数据页时，队列占用内存的大小。此参数会影响主备之间复制的缓冲大小。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，4096~1072693248，单位为KB。
+
+**默认值**: 16MB（即16448KB）
+
+## walsender_max_send_size
+
+**参数说明**: 设置主机端日志或数据发送缓冲区的大小。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，8~INT_MAX，单位为KB。
+
+**默认值**: 8M（即8192KB）
+
+## enable_data_replicate
+
+**参数说明**: 当数据库在数据导入行存表时，主机与备机的数据同步方式可以进行选择。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示导入数据行存表时主备数据采用数据页的方式进行同步。当replication_type参数为1时，不允许设置为on，如果此时用guc工具设置成on，会强制改为off。
+- off表示导入数据行存表时主备数据采用日志（Xlog）方式进行同步。
+
+**默认值**: off
+
+## ha_module_debug
+
+**参数说明**: 用于查看数据复制时具体数据块的复制状态日志。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示日志中将打印数据复制时每个数据块的状态。
+- off表示日志中不打印数据复制时每个数据块的状态。
+
+**默认值**: off
+
+## enable_incremental_catchup
+
+**参数说明**: 控制主备之间数据追赶（catchup）的方式。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示备机catchup时用增量catchup方式，即从从备本地数据文件扫描获得主备差异数据文件列表，进行主备之间的catchup。
+- off表示备机catchup时用全量catchup方式，即从主机本地所有数据文件扫描获得主备差异数据文件列表，进行主备之间的catchup。
+
+**默认值**: on
+
+## wait_dummy_time
+
+**参数说明**: 同时控制增量数据追赶（catchup）时，MogDB主备从按顺序启动时等待从备启动的最长时间以及等待从备发回扫描列表的最长时间。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，范围1~INT_MAX，单位为秒
+
+**默认值**: 300
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+>
+> 单位只能设置为秒。
+
+## catchup2normal_wait_time
+
+**参数说明**: 打开最大可用模式most_available_sync，主备场景下，控制备机数据追赶（catchup）阻塞主机的最长时间。该时间为估算值，实际结果可能与参数值有偏差。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，范围-1~10000，单位为毫秒。
+
+- -1表示主机阻塞直到备机数据追赶完成。
+- 0表示备机数据追赶时始终不阻塞主机。
+- 其余值表示备机数据追赶时阻塞主机的最长时间。例如，取值5000，表示当备机数据追赶完成时间还剩5s时，阻塞主机等待其完成。
+
+**默认值**: -1
+
+## sync_config_strategy
+
+**参数说明**: 主机和备机、备机和级联备之间配置文件的同步策略。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**枚举类型
+
+- all_node: 主机配置为all_node时，表示允许主机向所有备机主动同步配置文件；备机配置为all_node时，表示允许当前备机向其主机发送同步请求，允许当前备机向其所有级联备主动同步配置文件；级联备配置为all_node时，表示允许当前级联备向其备机发送同步请求。
+- only_sync_node: 主机配置为only_sync_node时，表示仅允许主机向所有同步备机主动同步配置文件；备机配置为only_sync_node时，表示允许当前备机向其主机发送同步请求，不允许当前备机向其所有级联备主动同步配置文件；级联备配置为only_sync_node时，表示允许当前级联备向其备机发送同步请求。
+- none_node: 主机配置为none_node时，表示不允许主机向任何备机主动同步配置文件；备机配置为none_node时，表示不允许当前备机向其主机发送同步请求，不允许当前备机向其所有级联备主动同步配置文件；级联备配置为none_node时，表示不允许当前级联备向其备机发送同步请求。
+
+**默认值**: all_node
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+>
+> - 在一个包含了主机、备机和级联备的MogDB集群中，主机相对于备机是发送端，备机相对于主机是接收端，备机相对于级联备是发送端，级联备相对于备机是接收端。
+> - 发送端主动向接收端同步配置文件、接收端请求发送端同步配置文件是两个独立的事件，均会使得配置文件同步。若不希望配置文件同步，则需要将集群中所有节点的sync_config_strategy参数配置为none_node；若仅希望主机与同步备机同步配置文件，则需要将主机的sync_config_strategy参数配置为only_sync_node，其余节点配置为none_node；若希望所有节点同步配置文件，则需要将所有节点的sync_config_strategy参数配置为all_node。目前暂不支持自定义指定任意节点间的同步策略。
+> - 配置参数同步的具体表现为，发送端发送配置文件，对接收端配置文件中的对应参数直接覆盖。若设置了配置文件需要同步的策略，则修改接收端配置参数后，发送端会立刻覆盖接收端的配置参数，使得接收端修改不生效。
+> - 即使设置了配置文件需要同步的策略，仍有部分配置参数不会被同步。它们是： “application_name”, “archive_command”, “audit_directory”, “available_zone”, “comm_control_port”, “comm_sctp_port”, “listen_addresses”, “log_directory”, “port”, “replconninfo1”, “replconninfo2”, “replconninfo3”, “replconninfo4”, “replconninfo5”, “replconninfo6”, “replconninfo7”, “replconninfo8”, “ssl”, “ssl_ca_file”, “ssl_cert_file”, “ssl_ciphers”, “ssl_crl_file”, “ssl_key_file”, “ssl_renegotiation_limit”, “ssl_cert_notify_time”, “synchronous_standby_names”, “local_bind_address”, “perf_directory”, “query_log_directory”, “asp_log_directory”, “streaming_router_port”, “enable_upsert_to_merge”, “archive_dest”, “recovery_min_apply_delay”, “sync_config_strategy”。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/7-ha-replication/3-standby-server.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/7-ha-replication/3-standby-server.md
new file mode 100644
index 0000000000000000000000000000000000000000..7d3e8e6164420c0a6deb37d86b5409a8d4518814
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/7-ha-replication/3-standby-server.md
@@ -0,0 +1,134 @@
+---
+title: 备服务器
+summary: 备服务器
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 备服务器
+
+## hot_standby
+
+**参数说明**: 设置是否允许备机在恢复过程中连接和查询。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+>
+> - 如果此参数设置为on，wal_level必须设置为hot_standby，否则将导致数据库无法启动。
+> - 在双机环境中，因为会对双机其他一些功能产生影响，hot_standby参数不能设置成off。
+
+**取值范围:**布尔型
+
+- on表示允许备机在恢复过程中连接和查询。
+- off表示不允许备机在恢复过程中连接和查询。
+
+**默认值**: on
+
+## max_standby_archive_delay
+
+**参数说明**: 当开启双机热备模式时，如果备机正处理归档WAL日志数据，这时进行查询就会产生冲突，此参数就是设置备机取消查询之前所等待的时间。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+>
+> -1表示允许备机一直等待冲突的查询完成。
+
+**取值范围:**整型，范围: -1~INT_MAX，单位为毫秒。
+
+**默认值**: 3s（即3000ms）
+
+## max_standby_streaming_delay
+
+**参数说明**: 当开启双机热备模式时，如果备机正通过流复制接收WAL日志数据，这时进行查询就会产生冲突，这个参数就是设置备机取消查询之前所等待的时间。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+>
+> -1表示允许备机一直等待冲突的查询完成。
+
+**取值范围:**整型（毫秒），范围: -1~INT_MAX。
+
+**默认值**:  3s（即3000ms）
+
+## wal_receiver_status_interval
+
+**参数说明**: 设置WAL日志接收进程的状态通知给主机的最大时间间隔。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，范围: 0 ~ INT_MAX，单位为毫秒。
+
+**默认值**: 5s（即5000ms）
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+> 当该参数设置为0时，表示关闭备机向主机反馈日志接收位置等信息，可能会导致主机事务提交阻塞、switchover操作失败等异常现象。正常业务场景，不建议将该参数设置为0。
+
+## hot_standby_feedback
+
+**参数说明**: 设置是否允许将备机上执行查询的结果反馈给主机，这可以避免查询冲突。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示允许将备机上执行查询的最小事务号反馈给主机。
+- off表示不允许将备机上执行查询的最小事务号反馈给主机。
+
+**默认值**: off
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+>
+> 当该参数为on时，主机的旧版本数据的清理会受限于备机正在读的事务，即主机只允许清理小于备机反馈回来的事务所作的更改。 所以，若该参数开启时，会影响主机的性能。
+
+## wal_receiver_timeout
+
+**参数说明**: 设置从主机接收数据的最大等待时间。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，0 ~ INT_MAX，单位为毫秒。
+
+**默认值**: 6s（即6000ms）
+
+## wal_receiver_connect_timeout
+
+**参数说明**: 设置连接主机的最大等待超时时间。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，0 ~ INT_MAX / 1000，单位为秒。
+
+**默认值**: 2s
+
+## wal_receiver_connect_retries
+
+**参数说明**: 设置连接主机的最大尝试次数。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，1~ INT_MAX。
+
+**默认值**: 1
+
+## wal_receiver_buffer_size
+
+**参数说明**: 备机与从备接收Xlog存放到内存缓冲区的大小。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**整型，4096~1047552，单位为KB。
+
+**默认值**: 64MB（即65536KB）
+
+## primary_slotname
+
+**参数说明**: 设置备机对应主机的slot name，用于主备校验，与wal日志删除机制。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**字符型
+
+**默认值**: 空字符串
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/8-mot.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/8-mot.md
new file mode 100644
index 0000000000000000000000000000000000000000..2c35cdd3196c80f04ced18cd717e1251687e86a6
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/8-mot.md
@@ -0,0 +1,73 @@
+---
+title: 内存表
+summary: 内存表
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 内存表
+
+介绍内存表的配置参数。
+
+## enable_codegen_mot
+
+**参数说明**: 设置是否启用原生LLVM Lite执行简单查询。如果当前平台上不支持原生LLVM，那么将使用伪LLVM。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔值
+
+**默认值**: true
+
+## force_pseudo_codegen_mot
+
+**参数说明**: 设置是否强制伪LLVM Lite执行简单查询，即使当前平台上支持原生LLVM。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔值
+
+**默认值**: true
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+> 即使将force_pseudo_codegen_mot设置为true，而当前平台不支持原生LLVM，那么仍然会使用伪LLVM。
+
+## enable_codegen_mot_print
+
+**参数说明**: 设置是否打印生成函数的IR字节码（如果使用伪 LLVM，则打印伪IR字节码）。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔值
+
+**默认值**: true
+
+## codegen_mot_limit
+
+**参数说明**: 设置全局缓存计划源的数量限制，以及每个会话的克隆计划。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: uint32
+
+**默认值**: 100
+
+## mot_allow_index_on_nullable_column
+
+**参数说明**: 设置是否允许在内存表nullable列上创建索引。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔值
+
+**默认值**: true
+
+## mot_config_file
+
+**参数说明**: 指定MOT的主配置文件。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串
+
+**默认值**: NULL
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/1-optimizer-method-configuration.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/1-optimizer-method-configuration.md
new file mode 100644
index 0000000000000000000000000000000000000000..be3f0d2b9c5b0ad1411c2bcb2b38e436d9792044
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/1-optimizer-method-configuration.md
@@ -0,0 +1,317 @@
+---
+title: 优化器方法配置
+summary: 优化器方法配置
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 优化器方法配置
+
+这些配置参数提供了影响查询优化器选择查询规划的原始方法。如果优化器为特定的查询选择的缺省规划并不是最优的，可以通过使用这些配置参数强制优化器选择一个不同的规划来临时解决这个问题。更好的方法包括调节优化器开销常量、手动运行ANALYZE、增加配置参数default_statistics_target的值、增加使用ALTER TABLE SET STATISTICS为指定列增加收集的统计信息。
+
+## enable_bitmapscan
+
+**参数说明**: 控制优化器对位图扫描规划类型的使用。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示使用。
+- off表示不使用。
+
+**默认值**: on
+
+## force_bitmapand
+
+**参数说明**: 控制优化器强制使用bitmapand规划类型的使用。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示使用。
+- off表示不使用。
+
+**默认值**: off
+
+## enable_hashagg
+
+**参数说明**: 控制优化器对Hash聚集规划类型的使用。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示使用。
+- off表示不使用。
+
+**默认值**: on
+
+## enable_hashjoin
+
+**参数说明**: 控制优化器对Hash连接规划类型的使用。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示使用。
+- off表示不使用。
+
+**默认值**: on
+
+## enable_indexscan
+
+**参数说明**: 控制优化器对索引扫描规划类型的使用。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示使用。
+- off表示不使用。
+
+**默认值**: on
+
+## enable_indexonlyscan
+
+**参数说明**: 控制优化器对仅索引扫描规划类型的使用。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示使用。
+- off表示不使用。
+
+**默认值**: on
+
+## enable_material
+
+**参数说明**: 控制优化器对实体化的使用。消除整个实体化是不可能的，但是可以关闭这个变量以防止优化器插入实体节点。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示使用。
+- off表示不使用。
+
+**默认值**: on
+
+## enable_mergejoin
+
+**参数说明**: 控制优化器对融合连接规划类型的使用。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示使用。
+- off表示不使用。
+
+**默认值**: off
+
+## enable_nestloop
+
+**参数说明**: 控制优化器对内表全表扫描嵌套循环连接规划类型的使用。完全消除嵌套循环连接是不可能的，但是关闭这个变量就会让优化器在存在其他方法的时候优先选择其他方法。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示使用。
+- off表示不使用。
+
+**默认值**: off
+
+## enable_index_nestloop
+
+**参数说明**: 控制优化器对内表参数化索引扫描嵌套循环连接规划类型的使用。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示使用。
+- off表示不使用。
+
+**默认值**: on
+
+## enable_seqscan
+
+**参数说明**: 控制优化器对顺序扫描规划类型的使用。完全消除顺序扫描是不可能的，但是关闭这个变量会让优化器在存在其他方法的时候优先选择其他方法。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示使用。
+- off表示不使用。
+
+**默认值**: on
+
+## enable_sort
+
+**参数说明**: 控制优化器使用的排序步骤。完全消除明确的排序是不可能的，但是关闭这个变量可以让优化器在存在其他方法的时候优先选择其他方法。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示使用。
+- off表示不使用。
+
+**默认值**: on
+
+## enable_tidscan
+
+**参数说明**: 控制优化器对TID扫描规划类型的使用。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示使用。
+- off表示不使用。
+
+**默认值**: on
+
+## enable_kill_query
+
+**参数说明**: CASCADE模式删除用户时，会删除此用户拥有的所有对象。此参数标识是否允许在删除用户的时候，取消锁定此用户所属对象的query。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示允许取消锁定。
+- off表示不允许取消锁定。
+
+**默认值**: off
+
+## enforce_a_behavior
+
+**参数说明**: 控制正则表达式的规则匹配模式。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示正则表达式采用A格式的匹配规则。
+- off表示正则表达式采用POSIX格式的匹配规则。
+
+**默认值**: on
+
+## max_recursive_times
+
+**参数说明**: 控制with recursive的最大迭代次数。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，0～INT_MAX。
+
+**默认值**: 200
+
+## enable_vector_engine
+
+**参数说明**: 控制优化器对向量化执行引擎的使用。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示使用。
+- off表示不使用。
+
+**默认值**: on
+
+## enable_change_hjcost
+
+**参数说明**: 控制优化器在Hash Join代价估算路径选择时，是否使用将内表运行时代价排除在Hash Join节点运行时代价外的估算方式。如果使用，则有利于选择条数少，但运行代价大的表做内表。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示使用。
+- off表示不使用。
+
+**默认值**: off
+
+## enable_absolute_tablespace
+
+**参数说明**: 控制表空间是否可以使用绝对路径。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示可以使用绝对路径。
+- off表示不可以使用绝对路径。
+
+**默认值**: on
+
+## enable_valuepartition_pruning
+
+**参数说明**: 是否对DFS分区表进行静态/动态优化。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围:**布尔型
+
+- on表示对DFS分区表进行静态/动态优化。
+- off表示不对DFS分区表进行静态/动态优化。
+
+**默认值**: on
+
+## qrw_inlist2join_optmode
+
+**参数说明**: 控制是否使用inlist-to-join查询重写。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串
+
+- disable: 关闭inlist2join查询重写。
+- cost_base: 基于代价的inlist2join查询重写。
+- rule_base: 基于规则的inlist2join查询重写，即强制使用inlist2join查询重写。
+- 任意正整数: inlist2join查询重写阈值，即list内元素个数大于该阈值，进行inlist2join查询重写。
+
+**默认值**: cost_base
+
+## skew_option
+
+**参数说明**: 控制是否使用优化策略。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 字符串
+
+- off: 关闭策略。
+- normal: 采用激进策略。对于不确定是否出现倾斜的场景，认为存在倾斜，并进行相应优化。
+- lazy: 采用保守策略。对于不确定是否出现倾斜场景，认为不存在倾斜，不进行优化。
+
+**默认值**: normal
+
+## default_limit_rows
+
+**参数说明**: 设置生成genericplan的缺省limit估算行数。此参数设置为正数时意为直接将设置的值作为估算limit的行数，为负数时代表使用百分比的形式设置默认的估算值，负数转换为默认百分比，即-5代表5%。
+
+**取值范围**: 浮点型，-100~DBL_MAX。
+
+**默认值**: -10
+
+## check_implicit_conversions
+
+**参数说明**：控制是否对查询中有隐式类型转换的索引列是否会生成候选索引路径进行检查。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：布尔型
+
+- on表示对查询中有隐式类型转换的索引列是否会生成候选索引路径进行检查。
+- off表示不进行相关检查。
+
+**默认值**：off
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/2-optimizer-cost-constants.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/2-optimizer-cost-constants.md
new file mode 100644
index 0000000000000000000000000000000000000000..f13e16c31f87c1ff316b80071c0dd62cdd454637
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/2-optimizer-cost-constants.md
@@ -0,0 +1,94 @@
+---
+title: 优化器开销常量
+summary: 优化器开销常量
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 优化器开销常量
+
+介绍优化器开销常量。这里描述的开销可以按照任意标准度量。只关心其相对值，因此以相同的系数缩放它们将不会对优化器的选择产生任何影响。缺省时，它们以抓取顺序页的开销为基本单位。也就是说将seq_page_cost设为1.0，同时其他开销参数以它为基准设置。也可以使用其他基准，比如以毫秒计的实际执行时间。
+
+## seq_page_cost
+
+**参数说明**: 设置优化器计算一次顺序磁盘页面抓取的开销。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 浮点型，0～DBL_MAX。
+
+**默认值**: 1
+
+## random_page_cost
+
+**参数说明**: 设置优化器计算一次非顺序抓取磁盘页面的开销。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> 虽然服务器允许将random_page_cost设置的比seq_page_cost小，但是物理上实际不受影响。如果所有数据库都位于随机访问内存中时，两者设置为相等很合理。因为在此种情况下，非顺序抓取页并没有副作用。同样，在缓冲率很高的数据库上，应该相对于CPU参数同时降低这两个值，因为获取内存中的页要比通常情况下开销小很多。
+
+**取值范围**: 浮点型，0～DBL_MAX。
+
+**默认值**: 4
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+>
+> - 对于特别表空间中的表和索引，可以通过设置同名的表空间的参数来覆盖这个值。
+> - 相对于seq_page_cost，减少这个值将导致系统更倾向于使用索引扫描，而增加这个值使得索引扫描开销比较高。可以通过同时增加或减少这两个值来调整磁盘I/O相对于CPU的开销。
+
+## cpu_tuple_cost
+
+**参数说明**: 设置优化器计算在一次查询中处理每一行数据的开销。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 浮点型，0～DBL_MAX。
+
+**默认值**: 0.01
+
+## cpu_index_tuple_cost
+
+**参数说明**: 设置优化器计算在一次索引扫描中处理每条索引的开销。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 浮点型，0～DBL_MAX。
+
+**默认值**: 0.005
+
+## cpu_operator_cost
+
+**参数说明**: 设置优化器计算一次查询中执行一个操作符或函数的开销。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 浮点型，0～DBL_MAX。
+
+**默认值**: 0.0025
+
+## effective_cache_size
+
+**参数说明**: 设置优化器在一次单一的查询中可用的磁盘缓冲区的有效大小。
+
+设置这个参数，还要考虑MogDB的共享缓冲区以及内核的磁盘缓冲区。另外，还要考虑预计的在不同表之间的并发查询数目，因为它们将共享可用的空间。
+
+这个参数对MogDB分配的共享内存大小没有影响，它也不会使用内核磁盘缓冲，它只用于估算。数值是用磁盘页来计算的，通常每个页面是8192字节。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，1～INT_MAX，单位为8KB。
+
+比默认值高的数值可能会导致使用索引扫描，更低的数值可能会导致选择顺序扫描。
+
+**默认值**: 128MB
+
+## allocate_mem_cost
+
+**参数说明**: 设置优化器计算Hash Join创建Hash表开辟内存空间所需的开销，供Hash join估算不准时调优使用。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 浮点型，0～DBL_MAX。
+
+**默认值**: 0
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/3-genetic-query-optimizer.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/3-genetic-query-optimizer.md
new file mode 100644
index 0000000000000000000000000000000000000000..c2c0b0e560a2f07c93ab8f8892bb27e4fe8fe3a8
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/3-genetic-query-optimizer.md
@@ -0,0 +1,106 @@
+---
+title: 基因查询优化器
+summary: 基因查询优化器
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 基因查询优化器
+
+介绍基因查询优化器相关的参数。基因查询优化器（GEQO）是一种启发式的查询规划算法。这个算法减少了对复杂查询规划的时间，而且生成规划的开销有时也小于正常的详尽的查询算法。
+
+## geqo
+
+**参数说明**: 控制基因查询优化的使用。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> 通常情况下在执行过程中不要关闭，geqo_threshold变量提供了更精细的控制GEQO的方法。
+
+**取值范围**: 布尔型
+
+- on表示使用。
+- off表示不使用。
+
+**默认值**: on
+
+## geqo_threshold
+
+**参数说明**: 如果执行语句的数量超过设计的FROM的项数，则会使用基因查询优化来执行查询。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+>
+> - 对于简单的查询，通常用详尽搜索方法，当涉及多个表的查询的时候，用GEQO可以更好的管理查询。
+> - 一个FULL OUTER JOIN构造仅作为一个FROM项。
+
+**取值范围**: 整型，2～INT_MAX。
+
+**默认值**: 12
+
+## geqo_effort
+
+**参数说明**: 控制GEQO在规划时间和规划质量之间的平衡。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> geqo_effort实际上并没有直接做任何事情，只是用于计算其他影响GEQO的变量的默认值。如果愿意，可以手工设置其他参数。
+
+**取值范围**: 整型，1～10。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> 比默认值大的数值增加了查询规划的时间，但是也增加了选中有效查询的几率。
+
+**默认值**: 5
+
+## geqo_pool_size
+
+**参数说明**: 控制GEQO使用池的大小，也就是基因全体中的个体数量。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，0～INT_MAX。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> 至少是2，且有用的值一般在100到1000之间。设置为0，表示使用系统自适应方式，MogDB会基于geqo_effort和表的个数选取合适的值。
+
+**默认值**: 0
+
+## geqo_generations
+
+**参数说明**: 控制GEQO使用的算法的迭代次数。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，0～INT_MAX。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> 必须至少是1，且有用的值介于100和1000之间。如果设置为0，则基于geqo_pool_size选取合适的值。
+
+**默认值**: 0
+
+## geqo_selection_bias
+
+**参数说明**: 控制GEQO的选择性偏好，即就是一个种群中的选择性压力。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 浮点型，1.5～2.0。
+
+**默认值**: 2
+
+## geqo_seed
+
+**参数说明**: 控制GEQO使用的随机数生产器的初始化值，用来从顺序连接在一起的查询空间中查找随机路径。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 浮点型，0.0～1.0。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> 不同的值会改变搜索的连接路径，从而影响了所找路径的优劣。
+
+**默认值**: 0
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/4-other-optimizer-options.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/4-other-optimizer-options.md
new file mode 100644
index 0000000000000000000000000000000000000000..18ef5818be3b05a3d9e6c0d962d3d4ef94f6ef49
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/4-other-optimizer-options.md
@@ -0,0 +1,709 @@
+---
+title: 其他优化器选项
+summary: 其他优化器选项
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 其他优化器选项
+
+## explain_dna_file
+
+**参数说明**: 指定explain_perf_mode为run，导出的csv信息的目标文件。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 这个参数的取值必须是绝对路径加上.csv格式的文件名。
+
+**取值范围**: 字符串
+
+**默认值**: 空
+
+## explain_perf_mode
+
+**参数说明**：此参数用来指定explain的显示格式。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：normal、pretty、summary、run
+
+- normal：代表使用默认的打印格式。
+- pretty：代表使用MogDB改进后的新显示格式。新的格式层次清晰，计划包含了plan node id，性能分析简单直接。
+- summary：是在pretty的基础上增加了对打印信息的分析。
+- run：在summary的基础上，将统计的信息输出到csv格式的文件中，以便于进一步分析。
+
+**默认值**：pretty（当前版本参数取值仅normal生效，若设置为非normal，显示格式依然为normal）
+
+## analysis_options
+
+**参数说明**: 通过开启对应选项中所对应的功能选项使用相应的定位功能，包括数据校验，性能统计等，参见取值范围中的选项说明。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。设置时，选择开启或者关闭的选项请使用'on()'或'off()'包括，未被显示指定的功能选项会维持原来的值，参考格式：'on(option1, option2, …)'。
+
+**取值范围**: 字符串
+
+- LLVM_COMPILE表示在explain performance显示界面中显示每个线程的codegen编译时间。
+
+- HASH_CONFLICT表示在数据库节点进程的pg_log目录中的log日志中显示hash表的统计信息，包括hash表大小，hash链长，hash冲突情况。
+
+- STREAM_DATA_CHECK表示对网络传输前后的数据进行CRC校验。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** pretty模式当前版本不支持。
+
+**默认值**: ALL,on(),off(LLVM_COMPILE,HASH_CONFLICT,STREAM_DATA_CHECK)，不开启任何定位功能。
+
+## cost_param
+
+**参数说明**：该参数用于控制在特定的客户场景中，使用不同的估算方法使得估算值与真实值更接近。此参数可以同时控制多种方法，与某一方法对应的位做与操作，不为0表示该方法被选择。
+
+当cost_param & 1不为0，表示对于求不等值连接选择率时选择一种改良机制，此方法在自连接（两个相同的表之间连接）的估算中更加准确。目前，已弃用cost_param & 1不为0时的路径，默认选择更优的估算公式；
+
+当cost_param & 2不为0，表示求多个过滤条件（Filter）的选择率时，选择最小的作为总的选择率，而非两者乘积，此方法在过滤条件的列之间关联性较强时估算更加准确；
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：整型，0～INT_MAX
+
+**默认值**：0
+
+## enable_partitionwise
+
+**参数说明**：分区表连接操作是否选择智能算法。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：布尔型
+
+- on表示选择智能算法。
+- off表示不选择智能算法。
+
+**默认值**：off
+
+## rewrite_rule
+
+**参数说明**：标识开启的可选查询重写规则。有部分查询重写规则是可选的，开启它们并不能总是对查询效率有提升效果。在特定的客户场景中，通过此GUC参数对查询重写规则进行设置，使得查询效率最优。
+
+此参数可以控制查询重写规则的组合，比如有多个重写规则：rule1、rule2、rule3、rule4。可以设置：
+
+```sql
+set rewrite_rule=rule1;          --启用查询重写规则rule1
+set rewrite_rule=rule2,rule3;    --启用查询重写规则rule2和rule3
+set rewrite_rule=none;           --关闭所有可选查询重写规则
+```
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：字符串
+
+- none：不使用任何可选查询重写规则。
+- lazyagg：使用Lazy Agg查询重写规则（消除子查询中的聚集运算）。
+- magicset : 使用Magic Set查询重写规则（从主查询中下推条件到子查询）。
+- partialpush：使用Partial Push查询重写规则。
+- uniquecheck：使用Unique Check查询重写规则（提升目标列中无agg的子查询语句，在执行时检查返回行数是否为1行）。
+- disablerep：使用Disable Replicate查询重写规则。
+- intargetlist：使用In Target List查询重写规则（提升目标列中的子查询）。
+- predpushnormal：使用Predicate Push查询重写规则（下推谓词条件到子查询中）。
+- predpushforce：使用Predicate Push查询重写规则（下推谓词条件到子查询中，尽可能的利用索引加速）。
+- predpush：在predpushnormal和predpushforce中根据代价选择最优计划。
+
+**默认值**：magicset
+
+## enable_pbe_optimization
+
+**参数说明**：设置优化器是否对以PBE（Parse Bind Execute）形式执行的语句进行查询计划的优化。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：布尔型。
+
+- on表示优化器将优化PBE语句的查询计划。
+- off表示不使用优化。
+
+**默认值**：on
+
+## enable_light_proxy
+
+**参数说明**：设置优化器是否对简单查询在数据库主节点上优化执行，应用端和内核端字符集不匹配时，该参数不生效，建议建库时将字符集设为UTF8。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：布尔型。
+
+- on表示优化器将优化数据库主节点上简单查询的执行。
+- off表示不使用优化。
+
+**默认值**：on
+
+## enable_global_plancache
+
+**参数说明**：设置是否对PBE查询的执行计划进行缓存共享，开启该功能可以节省高并发下数据库节点的内存使用。
+
+在打开enable_global_plancache的情况下，为保证GPC生效，默认local_syscache_threshold不小于16MB。即如当前local_syscache_threshold小于16MB，则设置为16MB，如大于16MB，则不改变。
+
+该参数属于POSTMASTER类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：布尔型。
+
+- on表示对PBE查询的执行计划进行缓存共享。
+- off表示不共享。
+
+**默认值**：off
+
+## gpc_clean_timeout
+
+**参数说明**：开启enable_global_plancache的情况下，如果共享计划列表里的计划超过gpc_clean_timeout的时间没有被使用，则会被清理掉。本参数用于控制没有使用的共享计划的保留时间。
+
+该参数属于SIGHUP类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：整型，300~86400，单位为秒
+
+**默认值**：1800，即30min
+
+## enable_global_stats
+
+**参数说明**: 标识当前统计信息模式，区别采用全局统计信息收集模式还是单节点统计信息收集模式，默认创建为采用全局统计信息模式。当关闭该参数时，则默认收集MogDB第一个节点的统计信息，此时可能会影响生成查询计划的质量，但信息收集性能较优，建议客户谨慎考虑。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on/true表示全局统计信息。
+- off/false表示数据库节点统计信息。
+
+**默认值**: on
+
+## enable_opfusion
+
+**参数说明**：控制是否对简单增删改查进行优化。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+简单查询限制如下：
+
+- 只支持indexscan和indexonlyscan，且全部WHERE语句的过滤条件都在索引上。
+
+- 只支持单表增删改查，不支持join、using。
+
+- 只支持行存表，不支持分区表，表不支持有触发器。
+
+- 不支持active sql、QPS等信息统计特性。
+
+- 不支持正在扩容和缩容的表。
+
+- 不支持查询或者修改系统列。
+
+- 只支持简单SELECT语句，例如：
+
+  ```
+  SELECT c3 FROM t1 WHERE c1 = ? and c2 =10;
+  ```
+
+  仅可以查询目标表的列，c1和c2列为索引列，后边可以是常量或者参数，可以使用 for update。
+
+- 只支持简单INSERT语句，例如：
+
+  ```
+  INSERT INTO t1 VALUES (?,10,?);
+  ```
+
+  仅支持一个VALUES，VALUES里面的类型可以是常量和参数，不支持returning。
+
+- 只支持简单DELETE语句，例如：
+
+  ```
+  DELETE FROM t1 WHERE c1 = ? and c2 = 10;
+  ```
+
+  c1和c2列为索引列，后边可以是常量或者参数。
+
+- 只支持简单UPDATE语句，例如：
+
+  ```
+  UPDATE t1 SET c3 = c3+? WHERE c1 = ? and c2 = 10;
+  ```
+
+  c3列修改的值可以是常量和参数，也可以是一个简单的表达式，c1和c2列为索引列，后边可以是常量或者参数。
+
+**取值范围**：布尔型
+
+- on表示使用。
+- off表示不使用。
+
+**默认值**：off
+
+## enable_partition_opfusion
+
+**参数说明**：在enable_opfusion参数打开的状态下，如果开启该参数，可以对分区表的简单查询进行查询优化，提升SQL执行性能。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：布尔型
+
+- on表示使用。
+- off表示不使用。
+
+**默认值**：off
+
+## sql_beta_feature
+
+**参数说明**：标识开启的可选SQL引擎Beta特性，其中包括对行数估算、查询等价估算等优化。
+
+开启它们可以对特定的场景进行优化，但也可能会导致部分没有被测试覆盖的场景发生性能劣化。在特定的客户场景中，通过此GUC参数对查询重写规则进行设置，使得查询效率最优。
+
+此参数可以控制SQL引擎Beta特性的组合，比如有多个Beta特性：feature1、feature2、feature3、feature4。可以设置：
+
+```
+--启用SQL引擎Beta特性feature1。
+set sql_beta_feature=feature1;
+--启用SQL引擎Beta特性feature2和feature3。
+set sql_beta_feature=feature2,feature3;
+--关闭所有可选SQL引擎Beta特性。
+set sql_beta_feature=none;
+```
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：字符串
+
+- none：不使用任何Beta优化器特性。
+- sel_semi_poisson：使用泊松分布对等值的半连接和反连接选择率进行校准。
+- sel_expr_instr：使用字符串匹配的行数估算方法对instr(col, 'const') &gt; 0, = 0, = 1进行更准确的估算。
+- param_path_gen：生成更多可能的参数化路径。
+- rand_cost_opt：对小数据量表的随机读取代价进行优化。
+- param_path_opt：利用表的膨胀系数优化索引analyze信息。
+- page_est_opt：优化对非列存表索引analyze信息的relpages估算。
+- no_unique_index_first：关闭主键索引扫描路径优先的优化。
+- join_sel_with_cast_func：估算join行数的时候支持类型转换函数。
+- canonical_pathkey：正则化pathkey生成置后（pathkey是指标记数据有序性键值的集合）。
+- index_cost_with_leaf_pages_only：估算索引代价时考虑索引叶子结点。
+- partition_opfusion：开启分区表优化。
+
+**默认值**：none
+
+## ngram_gram_size
+
+**参数说明**: ngram解析器分词的长度。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，1～4
+
+**默认值**: 2
+
+## ngram_grapsymbol_ignore
+
+**参数说明**: ngram解析器是否忽略图形化字符。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示忽略图形化字符。
+- off表示不忽略图形化字符。
+
+**默认值**: off
+
+## ngram_punctuation_ignore
+
+**参数说明**: ngram解析器是否忽略标点符号。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示忽略标点符号。
+- off表示不忽略标点符号。
+
+**默认值**: on
+
+## default_statistics_target
+
+**参数说明**：为没有用ALTER TABLE SET STATISTICS设置字段目标的表设置缺省统计目标。此参数设置为正数是代表统计信息的样本数量，为负数时，代表使用百分比的形式设置统计目标，负数转换为对应的百分比，即-5代表5%。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：整型，-100～10000。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+>
+> - 比默认值大的正数数值增加了ANALYZE所需的时间，但是可能会改善优化器的估计质量。
+> - 调整此参数可能存在性能劣化的风险，如果某个查询劣化，可以考虑
+>   1. 恢复默认的统计信息。
+>   2. 使用plan hint来调整到之前的查询计划。（详细参见**使用Plan Hint进行调优**）
+> - 当此guc参数设置为负数时，如果计算的采样样本数大于等于总数据量的2%，且用户表的数据量小于1600000时，ANALYZE所需时间相比guc参数为默认值的时间会有所增加。
+> - 当此guc参数设置为负数时，则autoanalyze不生效。
+
+**默认值**：100
+
+## constraint_exclusion
+
+**参数说明**：控制查询优化器使用表约束查询的优化。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：枚举类型
+
+- on表示检查所有表的约束。
+
+- off表示不检查约束。
+
+- partition表示只检查继承的子表和UNION ALL子查询。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 当constraint_exclusion为on，优化器用查询条件和表的CHECK约束比较，并且在查询条件和约束冲突的时候忽略对表的扫描。
+
+**默认值**：partition
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 目前， constraint_exclusion缺省被打开，通常用来实现表分区。为所有的表打开它时，对于简单的查询强加了额外的规划，并且对简单查询没有什么好处。如果不用分区表，可以关掉它。
+
+## cursor_tuple_fraction
+
+**参数说明**：优化器估计游标获取行数在总行数中的占比。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：浮点型，0.0～1.0。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 比默认值小的值与使用 “fast start” 为游标规划的值相偏离，从而使得前几行恢复的很快而抓取全部的行需要很长的时间。比默认值大的值加大了总的估计的时间。在最大的值1.0处，像正常的查询一样规划游标，只考虑总的估计时间和传送第一行的时间。
+
+**默认值**：0.1
+
+## from_collapse_limit
+
+**参数说明**：根据生成的FROM列表的项数来判断优化器是否将把子查询合并到上层查询，如果FROM列表项个数小于等于该参数值，优化器会将子查询合并到上层查询。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：整型，1～INT_MAX。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 比默认值小的数值将降低规划时间，但是可能生成差的执行计划。
+
+**默认值**：8
+
+## join_collapse_limit
+
+**参数说明**：根据得出的列表项数来判断优化器是否执行把除FULL JOINS之外的JOIN构造重写到FROM列表中。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：整型，1～INT_MAX。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+>
+> - 设置为1会避免任何JOIN重排。这样就使得查询中指定的连接顺序就是实际的连接顺序。查询优化器并不是总能选取最优的连接顺序，高级用户可以选择暂时把这个变量设置为1，然后指定它们需要的连接顺序。
+> - 比默认值小的数值减少规划时间但也降低了执行计划的质量。
+
+**默认值**：8
+
+## plan_mode_seed
+
+**参数说明**：该参数为调测参数，目前仅支持OPTIMIZE_PLAN和RANDOM_PLAN两种。其中：OPTIMIZE_PLAN表示通过动态规划算法进行代价估算的最优plan，参数值设置为0；RANDOM_PLAN表示随机生成的plan；如果设置为-1，表示用户不指定随机数的种子标识符seed值，由优化器随机生成[1, 2147483647]范围整型值的随机数，并根据随机数生成随机的执行计划；如果用户指定guc参数值为[1, 2147483647]范围的整型值，表示指定的生成随机数的种子标识符seed，优化器需要根据seed值生成随机的执行计划。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：整型，-1~ 2147483647
+
+**默认值**：0
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+>
+> - 当该参数设置为随机执行计划模式时，优化器会生成不同的随机执行计划，该执行计划可能不是最优计划。因此在随机计划模式下，会对查询性能产生影响，所以建议在升级、扩容、缩容等正常业务操作或运维过程中将该参数保持为默认值0。
+> - 当该参数不为0时，查询指定的plan hint不会生效。
+
+## hashagg_table_size
+
+**参数说明**：用于设置执行HASH JOIN操作时HASH表的大小。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：整型，0～INT_MAX/2。
+
+**默认值**：0
+
+## enable_codegen
+
+**参数说明**: 标识是否允许开启代码生成优化，目前代码生成使用的是LLVM优化。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示允许开启代码生成优化。
+
+- off表示不允许开启代码生成优化。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 目前LLVM优化仅支持向量化执行引擎特性和SQL on Hadoop特性，在其他场景下建议关闭此参数。
+
+**默认值**: off
+
+## codegen_strategy
+
+**参数说明**: 标识在表达式codegen化过程中所使用的代码生成优化策略。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 枚举类型
+
+- partial表示当所计算表达式中即使包含部分未被codegen化的函数时，仍可借助表达式全codegen框架调用LLVM动态编译优化策略。
+
+- pure表示当所计算表达式整体可被codegen化时，才考虑调用LLVM动态编译优化策略。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 在开启代码生成优化会导致查询性能下降的场景下可以设置此参数为pure，其他场景下建议不改变此参数的默认值partial。
+
+**默认值**: partial
+
+## enable_codegen_print
+
+**参数说明**: 标识是否允许在log日志中打印所生成的LLVM IR函数。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示允许在log日志中打印IR函数。
+- off表示不允许在log日志中打印IR函数。
+
+**默认值**: off
+
+## codegen_cost_threshold
+
+**参数说明**: 由于LLVM编译生成最终的可执行机器码需要一定时间，因此只有当实际执行的代价大于编译生成机器码所需要的代码和优化后的执行代价之和时，利用代码生成才有收益。codegen_cost_threshold标识代价的阈值，当执行估算代价大于该代价时，使用LLVM优化。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，0 ~ 2147483647。
+
+**默认值**: 10000
+
+## enable_bloom_filter
+
+**参数说明**: 标识是否允许使用BloomFilter优化。该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示允许使用BloomFilter优化。
+- off表示不允许使用BloomFilter优化。
+
+**默认值**: on
+
+## enable_extrapolation_stats
+
+**参数说明**: 标识对于日期类型是否允许基于历史统计信息使用推理估算的逻辑。使用该逻辑对于未及时收集统计信息的表可以增大估算准确的可能性，但也存在错误推理导致估算过大的可能性，需要对于日期类型数据定期插入的场景开启此开关。该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示允许基于历史统计信息使用推理估算的逻辑。
+- off表示不允许基于历史统计信息使用推理估算的逻辑。
+
+**默认值**: off
+
+## autoanalyze
+
+**参数说明**: 标识是否允许在生成计划的时候，对于没有统计信息的表进行统计信息自动收集。对于外表和临时表，不支持autoanalyze，如果需要收集统计信息，用户需手动执行analyze操作。如果在auto analyze某个表的过程中数据库发生异常，当数据库正常运行之后再执行语句有可能仍提示需要收集此表的统计信息。此时需要用户对该表手动执行一次analyze操作，以同步统计信息数据。该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示允许自动进行统计信息收集。
+- off表示不允许自动进行统计信息收集。
+
+**默认值**: off
+
+## enable_analyze_check
+
+**参数说明**: 标识是否允许在生成计划的时候，对于在pg_class中显示reltuples和relpages均为0的表，检查该表是否曾进行过统计信息收集。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示允许检查。
+- off表示不允许检查。
+
+**默认值**: off
+
+## enable_sonic_hashagg
+
+**参数说明**: 标识是否依据规则约束使用基于面向列的hash表设计的Hash Agg算子。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示在满足约束条件时使用基于面向列的hash表设计的Hash Agg算子。
+- off表示不使用面向列的hash表设计的Hash Agg算子。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 在开启enable_sonic_hashagg，且查询达到约束条件使用基于面向列的hash表设计的Hash Agg算子时，查询对应的Hash Agg算子内存使用通常可获得精简。但对于代码生成技术可获得显著性能提升的场景enable_codegen打开后获得较大性能提升)，对应的算子查询性能可能会出现劣化。
+> - 开启enable_sonic_hashagg，且查询达到约束条件使用基于面向列的hash表设计的Hash Agg算子时，在Explain Analyze/Performance的执行计划和执行信息中，算子显示为“Sonic Hash Aggregation”，而未达到该约束条件时，算子名称将显示为“Hash Aggregation”，Explain详解请参见详解。
+
+**默认值**: on
+
+## enable_sonic_hashjoin
+
+**参数说明**: 标识是否依据规则约束使用基于面向列的hash表设计的Hash Join算子。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示在满足约束条件时使用基于面向列的hash表设计的Hash Join算子。
+- off表示不使用面向列的hash表设计的Hash Join算子。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 当前开关仅适用于Inner Join的场景。
+> - 在开启enable_sonic_hashjoin，查询对应的Hash Inner算子内存使用通常可获得精简。但对于代码生成技术可获得显著性能提升的场景，对应的算子查询性能可能会出现劣化。
+> - 开启enable_sonic_hashjoin，且查询达到约束条件使用基于面向列的hash表设计的Hash Join算子时，在Explain Analyze/Performance的执行计划和执行信息中，算子显示为“Sonic Hash Join”，而未达到该约束条件时，算子名称将显示为“Hash Join”，Explain详解请参见详解。
+
+**默认值**: on
+
+## enable_sonic_optspill
+
+**参数说明**: 标识是否对面向列的hash表设计的Hash Join算子进行下盘文件数优化。该参数打开时，在Hash Join算子下盘文件较多的时候，下盘文件数不会显著增加。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 布尔型
+
+- on表示优化面向列的hash表设计的Hash Join算子的下盘文件数。
+- off表示不优化面向列的hash表设计的Hash Join算子的下盘文件数。
+
+**默认值**: on
+
+## log_parser_stats
+
+**参数说明**：控制优化器输出parser模块的性能日志。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：布尔型
+
+- on表示使用。
+- off表示不使用。
+
+**默认值**：off
+
+## log_planner_stats
+
+**参数说明**：控制优化器输出planner模块的性能日志。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：布尔型
+
+- on表示使用。
+- off表示不使用。
+
+**默认值**：off
+
+## log_executor_stats
+
+**参数说明**：控制优化器输出executor模块的性能日志。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：布尔型
+
+- on表示使用。
+- off表示不使用。
+
+**默认值**：off
+
+## log_statement_stats
+
+**参数说明**：控制优化器输出该语句的性能日志。
+
+该参数属于SUSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：布尔型
+
+- on表示使用。
+- off表示不使用。
+
+**默认值**：off
+
+## plan_cache_mode
+
+**参数说明**：标识在prepare语句中，选择生成执行计划的策略。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：枚举类型
+
+- auto表示按照默认的方式选择custom plan或者generic plan。
+- force_generic_plan表示强制走generic plan。
+- force_custom_plan表示强制走custom plan。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 此参数只对prepare语句生效，一般用在prepare语句中参数化字段存在比较严重的数据倾斜的场景下。
+> - custom plan是指对于preapre语句，在执行execute的时候，把execute语句中的参数嵌套到语句之后生成的计划。custom plan会根据execute语句中具体的参数生成计划，这种方案的优点是每次都按照具体的参数生成优选计划，执行性能比较好；缺点是每次执行前都需要重新生成计划，存在大量的重复的优化器开销。
+> - generic plan是指对于preapre语句生成计划，该计划策略会在执行execute语句的时候把参数bind到plan中，然后执行计划。这种方案的优点是每次执行可以省去重复的优化器开销；缺点是当bind参数字段上数据存在倾斜时该计划可能不是最优的，部分bind参数场景下执行性能较差。
+
+**默认值**：auto
+
+## enable_hypo_index
+
+**参数说明**：控制优化器执行EXPLAIN命令时是否考虑虚拟索引。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：布尔型
+
+- on表示使用。
+- off表示不使用。
+
+**默认值**：off
+
+## enable_force_vector_engine
+
+**参数说明**：对于支持向量化的执行器算子，如果其子节点是非向量化的算子，通过设置此参数为on，强制生成向量化的执行计划。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：布尔型
+
+- on表示可以向量化的算子强制生成向量化。
+- off表示由向量化算子优化器决定是否向量化。
+
+**默认值**：off
+
+## enable_auto_explain
+
+**参数说明**：控制是否开启自动打印执行计划。该参数是用来定位慢存储过程或慢查询，只对当前连接的数据库主节点有效。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：布尔型，true表示开启，false表示关闭。
+
+**默认值**：false
+
+## auto_explain_level
+
+**参数说明**：控制自动打印执行计划的日志等级。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：枚举型，LOG或NOTICE，LOG表示在日志中打印执行计划，NOTICE表示以提示知的形式打印出计划。
+
+**默认值**：LOG
+
+## query_dop
+
+**参数说明**: 用户自定义的查询并行度。该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**: 整型，1~64。打开固定SMP功能，系统会使用固定并行度。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 在开启并行查询后，请保证系统CPU、内存、网络等资源充足，以达到最佳效果。
+
+**默认值**: 1
+
+## enable_startwith_debug
+
+**参数说明**：该参数为start with/connect by用于debug的参数，打开参数可以显示start with特性所有涉及的尾列相关信息。
+
+该参数属于USERSET类型参数，请参考表[GUC参数分类](30-appendix)中对应设置方法进行设置。
+
+**取值范围**：布尔型，true表示开启，false表示关闭。
+
+**默认值**：false
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/introduction-to-query-planning.md b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/introduction-to-query-planning.md
new file mode 100644
index 0000000000000000000000000000000000000000..c74144da39cdba57b573c6abb93a08c576da9c00
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/guc-parameters/9-query-planning/introduction-to-query-planning.md
@@ -0,0 +1,16 @@
+---
+title: 介绍
+summary: 介绍
+author: Zhang Cuiping
+date: 2021-04-20
+---
+
+# 介绍
+
+介绍查询优化器方法配置、开销常量、规划算法以及一些配置参数。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+> 优化器中涉及的两个参数:
+>
+> - INT_MAX数据类型INT的最大值，其值为2147483647。
+> - DBL_MAX数据类型FLOAT的最大值。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/oracle-plugins/dblink-user-guide.md b/product/zh/docs-mogdb/v3.0/reference-guide/oracle-plugins/dblink-user-guide.md
new file mode 100644
index 0000000000000000000000000000000000000000..ebbeeb6727a186140868249c9183f13aeb89de5c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/oracle-plugins/dblink-user-guide.md
@@ -0,0 +1,65 @@
+---
+title: DBlink使用手册
+summary: DBlink使用手册
+author: Guo Huan
+date: 2021-11-29
+---
+
+# dblink
+
+## dblink简介
+
+dblink用于在远程数据库中执行查询，通常是一个`SELECT`，但是也可以是任意返回行的SQL语句。
+
+当给出两个`text`参数时，首先将第一个作为持久连接的名称进行查找；如果找到，则在该连接上执行命令。如果未找到，则将第一个参数视为与`dblink_connect`一样的连接信息字符串，并且仅在此命令期间进行指示的连接。
+
+<br/>
+
+## dblink安装
+
+请参见[gs_install_plugin](gs_install_plugin)或[gs_install_plugin_local](gs_install_plugin_local)。
+
+<br/>
+
+## dblink使用
+
+### sql端创建拓展
+
+```sql
+create extension dblink;
+```
+
+### 检查dblink是否创建成功
+
+```
+\dx
+```
+
+### 连接远端数据库执行查询操作
+
+```sql
+select * from dblink('dbname=postgres host=127.0.0.1 port=12345 user=test password=Test123456'::text, 'select * from dblink_test'::text)t(id int, name varchar);
+```
+
+### 创建连接
+
+```sql
+select dblink_connect('dblink_conn','hostaddr=127.0.0.1 port=12345 dbname=postgres user=test password=Test123456');
+```
+
+### 数据库表操作
+
+（视图不支持查询操作）
+
+```sql
+select dblink_exec('dblink_conn', 'create table ss(id int, name int)');
+select dblink_exec('dblink_conn', 'insert into ss values(2,1)');
+select dblink_exec('dblink_conn', 'update ss set name=2 where id=1');
+select dblink_exec('dblink_conn', 'delete from ss where id=1');
+```
+
+### 解除连接
+
+```sql
+select dblink_disconnect('dblink_conn')
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/oracle-plugins/orafce-user-guide.md b/product/zh/docs-mogdb/v3.0/reference-guide/oracle-plugins/orafce-user-guide.md
new file mode 100644
index 0000000000000000000000000000000000000000..29649bca2429edda1886b350639db96b70886fee
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/oracle-plugins/orafce-user-guide.md
@@ -0,0 +1,250 @@
+---
+title: orafce 使用手册
+summary: orafce 使用手册
+author: Guo Huan
+date: 2021-11-29
+---
+
+# orafce
+
+## orafce简介
+
+orafce是MogDB针对Oracle的兼容包，可以支持一些Oracle的表、函数和数据类型。orafce提供兼容Oracle RDBMS的函数和操作符。
+
+本插件包含一些实用功能，能够帮助将Oracle应用程序迁移到MogDB/PostgreSQL。内置Oracle日期函数已针对Oracle 10进行了一致性测试，支持从1960到2070的日期范围。由于Oracle内含的bug，目前无法验证1100-03-01之前的日期。
+
+所有函数与Oracle完全兼容，并支持所有已知格式的字符串。详细介绍参见[GitHub orafce页面](https://github.com/orafce/orafce)。
+
+ <br/>
+
+## orafce安装
+
+请参见[gs_install_plugin](gs_install_plugin)或[gs_install_plugin_local](gs_install_plugin_local)。
+
+ <br/>
+
+## orafce创建及使用
+
+```sql
+create extension orafce;
+```
+
+检查所有模式：
+
+```sql
+\dn
+```
+
+ <br/>
+
+### dbms_output 使用方法
+
+检查函数，其中函数分为有参数、无参数，参数类型为boolean。
+
+```sql
+\df dbms_output.*
+```
+
+无参：
+
+```sql
+select dbms_output.disable();
+```
+
+有参：
+
+```sql
+select dbms_output.put_line('sss');
+```
+
+boolean：（这里boolean值为0、1）
+
+```sql
+select dbms_output.serveroutput(0);
+```
+
+<br/>
+
+### dbms_random使用方法
+
+检查函数，函数分为有参、无参
+
+```sql
+\df
+```
+
+有参：
+
+```sql
+select dbms_random.initialize(1);
+select dbms_random.value(256.1243434351237831823812312,12333.3111);
+```
+
+value可以不传参数。
+
+无参：
+
+```sql
+select dbms_random.value();
+```
+
+<br/>
+
+### dbms_utility使用
+
+检查函数
+
+```sql
+\df
+```
+
+```sql
+select dbms_utility.format_call_stack();
+select dbms_utility.format_call_stack('o');
+```
+
+有参数只允许使用[ops]
+
+```sql
+select dbms_utility.get_time();
+```
+
+<br/>
+
+### oracle函数使用
+
+检查函数:
+
+```sql
+\df
+```
+
+```sql
+select oracle.btrim('enmo');
+select oracle.get_full_version_num();
+select oracle.get_major_version();
+select oracle.get_major_version_num();
+select oracle.get_platform();
+select oracle.get_status();
+select oracle.length(1);
+select oracle.lpad('enmo', 1);
+select oracle.ltrim('enmo', 'enmo');
+select oracle.numtodsinterval(12.22,'1232');
+select oracle.nvl(1,2);
+select oracle.regexp_count('enmo', 'tech');
+select oracle.regexp_instr('enmo', 'tech');
+select oracle.regexp_replace('enmo', 'tech', 'sss', 1);
+select oracle.regexp_substr('enmo', 'tech', 1);
+```
+
+replace_empty_strings:
+
+```sql
+CREATE TABLE trg_test(a varchar, b int, c varchar, d date, e int);
+CREATE TRIGGER trg_test_xx BEFORE INSERT OR UPDATE ON trg_test FOR EACH ROW EXECUTE PROCEDURE oracle.replace_empty_strings(true);
+\pset null ***
+INSERT INTO trg_test VALUES('',10, 'AHOJ', NULL, NULL);
+INSERT INTO trg_test VALUES('AHOJ', NULL, '', '2020-01-01', 100);
+SELECT * FROM trg_test;
+```
+
+replace_null_strings:
+
+```sql
+CREATE TABLE trg_test(a varchar, b int, c varchar, d date, e int);
+CREATE TRIGGER trg_test_xx BEFORE INSERT OR UPDATE ON trg_test FOR EACH ROW EXECUTE PROCEDURE oracle.replace_null_strings();
+\pset null ***
+INSERT INTO trg_test VALUES(NULL, 10, 'AHOJ', NULL, NULL);
+INSERT INTO trg_test VALUES('AHOJ', NULL, NULL, '2020-01-01', 100);
+SELECT * FROM trg_test;
+```
+
+```sql
+SELECT * FROM trg_test;
+select oracle.round(1.212, 1);
+select oracle.rpad('enmo', 1);
+select oracle.rtrim('yunhe', 'enmo');
+select oracle.sessiontimezone();
+select oracle.substr(111.122,1);
+select oracle.to_char('14-Jan08 11:44:49+05:30');
+select oracle.translate_oracle_modifiers('icnsmx',true);
+```
+
+（参数必须为'icnsmx'一个或多个组合，会把m转换为n，n转换为s，boolean为true，字符串后边会添加一个g，false不添加）
+
+```sql
+select oracle.trunc(122.31, 1);
+select oracle.unistr('yunhe-enmo');
+```
+
+<br/>
+
+### utl_file使用
+
+检查函数
+
+```sql
+\df
+```
+
+<br/>
+
+### 文件检查操作
+
+```sql
+CREATE OR REPLACE FUNCTION checkFlushFile(dir text) RETURNS void AS $$
+DECLARE
+ f utl_file.file_type;
+ f1 utl_file.file_type;
+ ret_val text;
+ i integer;
+BEGIN
+ f := utl_file.fopen(dir, 'regressflush_orafce.txt', 'a');
+ PERFORM utl_file.put_line(f, 'ABC');
+ PERFORM utl_file.new_line(f);
+ PERFORM utl_file.put_line(f, '123'::numeric);
+ PERFORM utl_file.new_line(f);
+ PERFORM utl_file.putf(f, '[1=%s, 2=%s, 3=%s, 4=%s, 5=%s]', '1', '2', '3', '4', '5');
+ PERFORM utl_file.fflush(f);
+ f1 := utl_file.fopen(dir, 'regressflush_orafce.txt', 'r');
+ ret_val=utl_file.get_nextline(f1);
+ i:=1;
+ WHILE ret_val IS NOT NULL LOOP
+  RAISE NOTICE '[%] >>%<<', i,ret_val;
+  ret_val := utl_file.get_nextline(f1);
+  i:=i+1;
+ END LOOP;
+ RAISE NOTICE '>>%<<', ret_val;
+ f1 := utl_file.fclose(f1);
+ f := utl_file.fclose(f);
+END;
+$$ LANGUAGE plpgsql
+```
+
+<br/>
+
+### 文件读取操作
+
+```sql
+CREATE OR REPLACE FUNCTION read_file(dir text) RETURNS void AS $$
+DECLARE
+ f utl_file.file_type;
+BEGIN
+ f := utl_file.fopen(dir, 'regress_orafce.txt', 'r');
+ FOR i IN 1..11 LOOP
+  RAISE NOTICE '[%] >>%<<', i, utl_file.get_line(f);
+ END LOOP;
+ RAISE NOTICE '>>%<<', utl_file.get_line(f, 4);
+ RAISE NOTICE '>>%<<', utl_file.get_line(f, 4);
+ RAISE NOTICE '>>%<<', utl_file.get_line(f);
+ RAISE NOTICE '>>%<<', utl_file.get_line(f);
+ EXCEPTION
+  -- WHEN no_data_found THEN,  8.1 plpgsql doesn't know no_data_found
+  WHEN others THEN
+   RAISE NOTICE 'finish % ', sqlerrm;
+   RAISE NOTICE 'is_open = %', utl_file.is_open(f);
+   PERFORM utl_file.fclose_all();
+   RAISE NOTICE 'is_open = %', utl_file.is_open(f);
+ END;
+$$ LANGUAGE plpgsql;
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/oracle-plugins/pg_bulkload-user-guide.md b/product/zh/docs-mogdb/v3.0/reference-guide/oracle-plugins/pg_bulkload-user-guide.md
new file mode 100644
index 0000000000000000000000000000000000000000..5ef0c73bcf622324c1aaa7a5db2fd571663c0ec2
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/oracle-plugins/pg_bulkload-user-guide.md
@@ -0,0 +1,87 @@
+---
+title: pg_bulkload使用手册
+summary: pg_bulkload使用手册
+author: Guo Huan
+date: 2021-11-29
+---
+
+# pg_bulkload
+
+## pg_bulkload简介
+
+pg_bulkload是一种用于MogDB的高速数据加载工具，相比copy命令速度更快，能够跳过shared buffer、wal buffer直接写文件。
+
+<br/>
+
+## 安装pg_bulkload
+
+请参见[gs_install_plugin](gs_install_plugin)或[gs_install_plugin_local](gs_install_plugin_local)。
+
+<br/>
+
+## pg_bulkload使用
+
+```bash
+pg_bulkload --help
+gsql -p 5432 postgres -r
+```
+
+```sql
+CREATE EXTENSION pg_bulkload;
+create table test_bulkload(id int, name varchar(128));
+```
+
+创建一个txt文件，写10W条数据：
+
+```bash
+seq 100000| awk '{print $0"|bulkload"}' > bulkload_output.txt
+```
+
+<br/>
+
+### 使用参数
+
+文件创建成功，执行如下命令：
+
+```bash
+pg_bulkload -i ./bulkload_output.txt -O test_bulkload -l test_bulkload.log -p 5432 -o "TYPE=csv" -o "DELIMITER=|" -d postgres -U hlv
+```
+
+连接数据库，查看数据是否导入成功：
+
+```sql
+select count(1) from test_bulkload;
+```
+
+<br/>
+
+### 使用控制文件
+
+在使用控制文件进行数据导入之前，需要先清空之前表中导入的数据。
+
+编写.ctl文件
+
+```bash
+INPUT=/vdb/MogDB-server/dest/bulkload_output.txt
+LOGFILE = /vdb/MogDB-server/dest/test_bulkload.log
+LIMIT = INFINITE
+PARSE_ERRORS = 0
+CHECK_CONSTRAINTS = NO
+TYPE = CSV
+SKIP = 5  (该参数设置跳过几行)
+DELIMITER = |
+QUOTE = "\""
+ESCAPE = "\""
+OUTPUT = test_bulkload
+MULTI_PROCESS = NO
+WRITER = DIRECT
+DUPLICATE_ERRORS = 0
+ON_DUPLICATE_KEEP = NEW
+TRUNCATE = YES
+```
+
+执行命令：
+
+```bash
+pg_bulkload ./lottu.ctl -d postgres -U hlv
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/oracle-plugins/pg_prewarm-user-guide.md b/product/zh/docs-mogdb/v3.0/reference-guide/oracle-plugins/pg_prewarm-user-guide.md
new file mode 100644
index 0000000000000000000000000000000000000000..4636593b863ae140a9d490c1b34ea579ad92b24d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/oracle-plugins/pg_prewarm-user-guide.md
@@ -0,0 +1,89 @@
+---
+title: pg_prewarm使用手册
+summary: pg_prewarm使用手册
+author: Guo Huan
+date: 2021-11-29
+---
+
+# pg_prewarm
+
+## pg_prewarm简介
+
+pg_prewarm模块提供一种方便的方法把关系数据载入到操作系统缓冲区缓存或者MogDB缓冲区缓存。
+
+<br/>
+
+## pg_prewarm安装
+
+请参见[gs_install_plugin](gs_install_plugin)或[gs_install_plugin_local](gs_install_plugin_local)。
+
+<br/>
+
+## pg_prewarm加载模式
+
+- mode：加载模式，可选项有“prefetch”、“read”、“buffer”，默认为“buffer”
+- prefetch：异步地将数据预加载到操作系统缓存
+- read：最终结果跟prefetch一样，但它是同步方式，支持所有平台
+- buffer：将数据预加载到数据库缓存
+
+<br/>
+
+## pg_prewarm创建及使用
+
+1. 创建pg_prewarm。
+
+   ```sql
+   create extension pg_prewarm; 
+   ```
+
+2. 创建测试表。
+
+   ```sql
+   create table test_pre (id int4,name character varying(64),creat_time timestamp(6) without time zone); 
+   ```
+
+3. 插入数据。
+
+   ```sql
+   insert into test_pre select generate_series(1,100000),generate_series(1,100000)||  '_pre',clock_timestamp(); 
+   ```
+
+4. 查看数据表大小。
+
+   ```sql
+   mogdb=# select pg_size_pretty(pg_relation_size('test_pre'));
+   pg_size_pretty
+   ----------------
+   5136 kB
+   (1 row)
+   ```
+
+5. 加载数据到数据库缓存。这里可以看到pg_prewarm把所有数据分为了642块。
+
+   ```sql
+   mogdb=# select pg_prewarm('test_pre','buffer');
+    pg_prewarm
+   ------------
+        642
+   (1 row)
+   ```
+
+6. 查块大小。
+
+   ```sql
+   mogdb=# select current_setting('block_size');
+    current_setting
+   -----------------
+   8192
+   (1 row)
+   ```
+
+   MogDB默认每个数据块的大小为8KB。
+
+   ```sql
+   mogdb=# select 642*8; 
+    ?column?
+   ----------
+     5136
+   (1 row)
+   ```
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/oracle-plugins/pg_repack-user-guide.md b/product/zh/docs-mogdb/v3.0/reference-guide/oracle-plugins/pg_repack-user-guide.md
new file mode 100644
index 0000000000000000000000000000000000000000..3c726826695b8478f29bb42d88b32077b2543352
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/oracle-plugins/pg_repack-user-guide.md
@@ -0,0 +1,91 @@
+---
+title: pg_repack 安装流程
+summary: pg_repack 安装流程
+author: Guo Huan
+date: 2021-11-29
+---
+
+# pg_repack
+
+## pg_repack简介
+
+插件pg_repack用于在线清理表空间，有效解决因对全表大量更新等操作引起的表膨胀问题。pg_repack无需获取排它锁，相比CLUSTER或VACUUM FULL更加轻量化。
+
+<br/>
+
+## pg_repack安装
+
+请参见[gs_install_plugin](gs_install_plugin)或[gs_install_plugin_local](gs_install_plugin_local)。
+
+<br/>
+
+## pg_repack使用
+
+1. 连接数据库并且创建用户。
+
+   ```bash
+   gsql postgres -r -p 5001
+   ```
+
+   ```sql
+   create user test password 'Test123456' login sysadmin;
+   ```
+
+2. 在sql端执行：
+
+   ```sql
+   create extension pg_repack;
+   ```
+
+3. 在数据库中创建pg_repack表，必须包含主键。
+
+   ```sql
+   create table repack_test(id int primary key, name name);
+   ```
+
+4. 检查pg_repack是否创建成功。
+
+   ```sql
+   \dx
+   ```
+
+5. 在repack_test表中插入2000000条数据。
+
+   ```sql
+   insert into repack_test select generate_series(1,2000000),'a';
+   ```
+
+6. 查询表repack_test的大小。
+
+   ```sql
+   select pg_size_pretty(pg_relation_size('repack_test'));
+   ```
+
+7. 删除部分数据，然后查询表大小。
+
+   ```sql
+   Delete from repack_test where id>1000000;
+   ```
+
+   删除1000000条数据成功之后，可以看表大小并没有改变。这时需要使用pg_repack工具。
+
+8. 使用pg_repack工具。
+
+   ```bash
+   pg_repack -d postgres -t test.repack_test -h 127.0.0.1 -U test -p 5001
+   ```
+
+   参数含义：
+
+   - -d dbname（数据库名）
+   - -t test.repack_test -h hostip（服务端IP地址）
+   - -U     user（用户名）
+   - -p port（端口号）
+   - -e （输出repack过程中执行的所有SQL）
+   - -E DEBUG（设置，输出信息的日志级别为DEBUG）
+
+   sql查看repack_test表大小，表空间释放成功。
+
+   ```sql
+   select pg_size_pretty(pg_relation_size('repack_test'));
+   ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/oracle-plugins/pg_trgm-user-guide.md b/product/zh/docs-mogdb/v3.0/reference-guide/oracle-plugins/pg_trgm-user-guide.md
new file mode 100644
index 0000000000000000000000000000000000000000..d10c36ab19aa0bdda8c97de26f3a74231d3b367b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/oracle-plugins/pg_trgm-user-guide.md
@@ -0,0 +1,60 @@
+---
+title: pg_trgm使用手册
+summary: pg_trgm使用手册
+author: Guo Huan
+date: 2021-11-29
+---
+
+# pg_trgm
+
+## pg_trgm简介
+
+pg_trgm模块提供函数和操作符测定字母数字文本基于三元模型匹配的相似性，还有支持快速搜索相似字符串的索引操作符类。
+
+<br/>
+
+## pg_trgm安装
+
+请参见[gs_install_plugin](gs_install_plugin)或[gs_install_plugin_local](gs_install_plugin_local)。
+
+<br/>
+
+## pg_trgm使用
+
+1. sql端执行：
+
+   ```sql
+   -- 创建pg_trgm拓展
+   create extension pg_trgm;
+   ```
+
+2. 创建一张表插入一百万条数据。
+
+   ```sql
+   create table trgm_test(id int, name varchar);
+   insert into trgm_test select generate_series(1,1000000),md5(random()::name);
+   ```
+
+3. 不使用pg_trgm进行查询。
+
+   ```sql
+   explain analyze select * from trgm_test where name like '%69089%';
+   ```
+
+   ```sql
+   select * from trgm_test where name like '%69089%';
+   ```
+
+4. 创建索引。
+
+   ```sql
+   create index idx_trgm_test_1 on trgm_test using gin(name gin_trgm_ops);
+   ```
+
+   ```sql
+   explain analyze select * from trgm_test where name like '%ad44%';
+   ```
+
+   ```sql
+   select * from trgm_test where name like '%305696%';
+   ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/oracle-plugins/wal2json-user-guide.md b/product/zh/docs-mogdb/v3.0/reference-guide/oracle-plugins/wal2json-user-guide.md
new file mode 100644
index 0000000000000000000000000000000000000000..71faa66098501b5292fa07c1f4d991a040317253
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/oracle-plugins/wal2json-user-guide.md
@@ -0,0 +1,109 @@
+---
+title: wal2json使用手册
+summary: wal2json使用手册
+author: Guo Huan
+date: 2021-11-29
+---
+
+# wal2json
+
+## wal2json简介
+
+wal2json是逻辑解码插件，使用该插件可以访问由INSERT和UPDATE生成的元组，解析WAL中的内容。
+
+wal2json插件会在每个事务中生成一个JSON对象。JSON对象中提供了所有新/旧元组，额外选项还可以包括事务时间戳、限定架构、数据类型、事务ID等属性。
+
+<br/>
+
+## wal2json安装
+
+请参见[gs_install_plugin](gs_install_plugin)或[gs_install_plugin_local](gs_install_plugin_local)。
+
+<br/>
+
+## 修改数据库参数配置
+
+1. 修改数据库数据目录下postgresql.conf（主备都需要修改）。
+
+   ```bash
+   wal_level = logical
+   max_replication_slots = 10
+   max_wal_senders = 10
+   ```
+
+2. 修改pg_hba.conf（主备都需要修改）。
+
+   ```bash
+   host   replication   all     127.0.0.1/32       trust
+   ```
+
+3. 执行完成后重启数据库。
+
+<br/>
+
+## wal2json使用
+
+1. 重新开一个终端执行使用wal2json连接数据库。
+
+   ```bash
+   pg_recvlogical -d postgres --slot test2_slot --create -P wal2json -h 127.0.0.1 -p 5001 -U test
+   pg_recvlogical -d postgres -h 127.0.0.1 -p 5001 -U test --slot test2_slot --start  -f -
+   ```
+   
+2. sql端进行数据库增删改查操作。
+
+   ```sql
+   create table ff(id int, name int);
+   insert into ff values(1,2);
+   insert into ff values(2,4);
+   select * from ff;
+   ```
+
+3. wal2json端输出操作过程。
+
+   ```json
+   {"change":[]}
+   {"change":[]}
+   {"change":[{"kind":"insert","schema":"test","table":"ff","columnnames":["id","name"],"columntypes":["integer","integer"],"columnvalues":[1,10]}]}
+   {"change":[{"kind":"insert","schema":"test","table":"ff","columnnames":["id","name"],"columntypes":["integer","integer"],"columnvalues":[2,2]}]}
+   ```
+   
+   <br/>
+
+## wal2json参数
+
+在数据库数据目录下执行：
+
+```sql
+pg_recvlogical --help
+ -f, --file=FILE     receive log into this file. - for stdout
+ -n, --no-loop      do not loop on connection lost
+ -v, --verbose      output verbose messages
+ -V, --version      output version information, then exit
+ -?, --help       show this help, then exit
+
+Connection options:
+ -d, --dbname=DBNAME   database to connect to
+ -h, --host=HOSTNAME   database server host or socket directory
+ -p, --port=PORT     database server port number
+ -U, --username=NAME   connect as specified database user
+ -w, --no-password    never prompt for password
+ -W, --password     force password prompt (should happen automatically)
+
+Replication options:
+ -F  --fsync-interval=INTERVAL
+            frequency of syncs to the output file (in seconds, defaults to 10)
+ -o, --option=NAME[=VALUE]
+            Specify option NAME with optional value VAL, to be passed
+            to the output plugin
+ -P, --plugin=PLUGIN   use output plugin PLUGIN (defaults to mppdb_decoding)
+ -s, --status-interval=INTERVAL
+            time between status packets sent to server (in seconds, defaults to 10)
+ -S, --slot=SLOT     use existing replication slot SLOT instead of starting a new one
+ -I, --startpos=PTR   Where in an existing slot should the streaming start
+
+Action to be performed:
+   --create      create a new replication slot (for the slotname see --slot)
+   --start       start streaming in a replication slot (for the slotname see --slot)
+   --drop       drop the replication slot (for the slotname see --slot)
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.ARCHIVE_SNAPSHOT.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.ARCHIVE_SNAPSHOT.md
new file mode 100644
index 0000000000000000000000000000000000000000..fe25874ebafa9fc1ed424380fe28f5e993d15902
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.ARCHIVE_SNAPSHOT.md
@@ -0,0 +1,18 @@
+---
+title: DB4AI.ARCHIVE_SNAPSHOT
+summary: DB4AI.ARCHIVE_SNAPSHOT
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DB4AI.ARCHIVE_SNAPSHOT
+
+ARCHIVE_SNAPSHOT是DB4AI特性用于存档快照的接口函数。通过语法ARCHIVE SNAPSHOT调用。生效后的快照无法参数训练等任务。
+
+**表 1** DB4AI.ARCHIVE_SNAPSHOT入参和返回值列表
+
+| 参数     | 类型                    | 描述                    |
+| :------- | :---------------------- | :---------------------- |
+| i_schema | IN NAME                 | 快照存储的模式名字，默认值是当前用户 |
+| i_name   | IN NAME                 | 快照名称                             |
+| res      | OUT db4ai.snapshot_name | 结果                                 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.CREATE_SNAPSHOT.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.CREATE_SNAPSHOT.md
new file mode 100644
index 0000000000000000000000000000000000000000..cccf82ee96f076276a9f1cc7221d4c41529e4943
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.CREATE_SNAPSHOT.md
@@ -0,0 +1,21 @@
+---
+title: DB4AI.CREATE_SNAPSHOT
+summary: DB4AI.CREATE_SNAPSHOT
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DB4AI.CREATE_SNAPSHOT
+
+CREATE_SNAPSHOT是DB4AI特性用于创建快照的接口函数。通过语法CREATE SNAPSHOT调用。
+
+**表 1** DB4AI.CREATE_SNAPSHOT入参和返回值列表
+
+| 参数       | 类型                    | 描述                          |
+| :--------- | :---------------------- | :---------------------------- |
+| i_schema   | IN NAME                 | 快照存储的模式名字，默认值是当前用户或者PUBLIC。 |
+| i_name     | IN NAME                 | 快照名称。                                       |
+| i_commands | IN TEXT[]               | 定义数据获取的SQL命令。                          |
+| i_vers     | IN NAME                 | 版本后缀。                                       |
+| i_comment  | IN TEXT                 | 快照描述。                                       |
+| res        | OUT db4ai.snapshot_name | 结果。                                           |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.CREATE_SNAPSHOT_INTERNAL.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.CREATE_SNAPSHOT_INTERNAL.md
new file mode 100644
index 0000000000000000000000000000000000000000..a90f8c07e34ee411dc481b264929453d81792957
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.CREATE_SNAPSHOT_INTERNAL.md
@@ -0,0 +1,21 @@
+---
+title: DB4AI.CREATE_SNAPSHOT_INTERNAL
+summary: DB4AI.CREATE_SNAPSHOT_INTERNAL
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DB4AI.CREATE_SNAPSHOT_INTERNAL
+
+CREATE_SNAPSHOT_INTERNAL是db4ai.create_snapshot函数的内置执行函数。函数存在信息校验，无法直接调用。
+
+**表 1** DB4AI.CREATE_SNAPSHOT_INTERNAL入参和返回值列表
+
+| 参数       | 类型      | 描述                    |
+| :--------- | :-------- | :---------------------- |
+| s_id       | IN BIGINT | 快照ID。                |
+| i_schema   | IN NAME   | 快照存储的名字空间。    |
+| i_name     | IN NAME   | 快照名称。              |
+| i_commands | IN TEXT[] | 定义数据获取的SQL命令。 |
+| i_comment  | IN TEXT   | 快照描述。              |
+| i_owner    | IN NAME   | 快照拥有者。            |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.MANAGE_SNAPSHOT_INTERNAL.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.MANAGE_SNAPSHOT_INTERNAL.md
new file mode 100644
index 0000000000000000000000000000000000000000..d7b2c782afe6c591f5fd9ec5cd7227cbddac0555
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.MANAGE_SNAPSHOT_INTERNAL.md
@@ -0,0 +1,19 @@
+---
+title: DB4AI.MANAGE_SNAPSHOT_INTERNAL
+summary: DB4AI.MANAGE_SNAPSHOT_INTERNAL
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DB4AI.MANAGE_SNAPSHOT_INTERNAL
+
+MANAGE_SNAPSHOT_INTERNAL是DB4AI.PUBLISH_SNAPSHOT和DB4AI.ARCHIVE_SNAPSHOT函数的内置执行函数。函数存在信息校验，无法直接调用。
+
+**表 1** DB4AI.MANAGE_SNAPSHOT_INTERNAL入参和返回值列表
+
+| 参数     | 类型                    | 描述               |
+| :------- | :---------------------- | :----------------- |
+| i_schema | IN NAME                 | 快照存储的模式名字 |
+| i_name   | IN NAME                 | 快照名称           |
+| publish  | IN BOOLEN               | 是否是发布状态     |
+| res      | OUT db4ai.snapshot_name | 结果               |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.PREPARE_SNAPSHOT.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.PREPARE_SNAPSHOT.md
new file mode 100644
index 0000000000000000000000000000000000000000..8e2a4ef40c83a0f87d293c89e02c02e404314bf5
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.PREPARE_SNAPSHOT.md
@@ -0,0 +1,21 @@
+---
+title: DB4AI.PREPARE_SNAPSHOT
+summary: DB4AI.PREPARE_SNAPSHOT
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DB4AI.PREPARE_SNAPSHOT
+
+PREPARE_SNAPSHOT是DB4AI特性中数据准备模型训练和解释快照进行协作。快照为所有应用更改的数据和文档提供了完整的序列。通过语法PREPARE SNAPSHOT调用。
+
+**表 1** DB4AI.PREPARE_SNAPSHOT入参和返回值列表
+
+| 参数       | 类型                    | 描述                          |
+| :--------- | :---------------------- | :---------------------------- |
+| i_schema   | IN NAME                 | 快照存储的模式名字，默认值是当前用户或者PUBLIC。 |
+| i_parent   | IN NAME                 | 父快照名称。                                     |
+| i_commands | IN TEXT[]               | 定义快照修改的DDL和DML命令。                     |
+| i_vers     | IN NAME                 | 版本后缀。                                       |
+| i_comment  | IN TEXT                 | 此数据策展单元的说明。                           |
+| res        | OUT db4ai.snapshot_name | 结果。                                           |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.PREPARE_SNAPSHOT_INTERNAL.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.PREPARE_SNAPSHOT_INTERNAL.md
new file mode 100644
index 0000000000000000000000000000000000000000..5d8eb9e85498ddef5b1487ccafee56f3ca16bccf
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.PREPARE_SNAPSHOT_INTERNAL.md
@@ -0,0 +1,27 @@
+---
+title: DB4AI.PREPARE_SNAPSHOT_INTERNAL
+summary: DB4AI.PREPARE_SNAPSHOT_INTERNAL
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DB4AI.PREPARE_SNAPSHOT_INTERNAL
+
+PREPARE_SNAPSHOT_INTERNAL是db4ai.prepare_snapshot函数的内置执行函数。函数存在信息校验，无法直接调用。
+
+**表 1** DB4AI.PREPARE_SNAPSHOT_INTERNAL入参和返回值列表
+
+| 参数        | 类型         | 描述                    |
+| :---------- | :----------- | :-----------------------|
+| s_id        | IN BIGINT    | 快照ID。                                         |
+| p_id        | IN BIGINT    | 父快照ID。                                       |
+| m_id        | IN BIGINT    | 矩阵id。                                         |
+| r_id        | IN BIGINT    | 根快照ID。                                       |
+| i_schema    | IN NAME      | 快照模式。                                       |
+| i_name      | IN NAME      | 快照名称。                                       |
+| i_commands  | IN TEXT[]    | 定义快照修改的DDL和DML命令。                     |
+| i_comment   | IN TEXT      | 快照描述。                                       |
+| i_owner     | IN NAME      | 快照所有者。                                     |
+| i_idx       | INOUT INT    | exec_cmds的索引。                                |
+| i_exec_cmds | INOUT TEXT[] | 用于执行的DDL和DML。                             |
+| i_mapping   | IN NAME[]    | 将用户列映射到备份列；如果不为NULL，则生成规则。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.PUBLISH_SNAPSHOT.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.PUBLISH_SNAPSHOT.md
new file mode 100644
index 0000000000000000000000000000000000000000..2a68cabc78f332b3558a5d02bee9969184182e48
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.PUBLISH_SNAPSHOT.md
@@ -0,0 +1,18 @@
+---
+title: DB4AI.PUBLISH_SNAPSHOT
+summary: DB4AI.PUBLISH_SNAPSHOT
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DB4AI.PUBLISH_SNAPSHOT
+
+PUBLISH_SNAPSHOT是DB4AI特性用于发布快照的接口函数。通过语法PUBLISH SNAPSHOT调用。
+
+**表 1** DB4AI.PUBLISH_SNAPSHOT入参和返回值列表
+
+| 参数     | 类型                    | 描述                         |
+| :------- | :---------------------- | :--------------------------- |
+| i_schema | IN NAME                 | 快照存储的模式名字，默认值是当前用户或者PUBLIC |
+| i_name   | IN NAME                 | 快照名称                                       |
+| res      | OUT db4ai.snapshot_name | 结果                                           |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.PURGE_SNAPSHOT.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.PURGE_SNAPSHOT.md
new file mode 100644
index 0000000000000000000000000000000000000000..93bc8d9654e15c97e3c728ec1dd28c003ed38906
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.PURGE_SNAPSHOT.md
@@ -0,0 +1,18 @@
+---
+title: DB4AI.PURGE_SNAPSHOT
+summary: DB4AI.PURGE_SNAPSHOT
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DB4AI.PURGE_SNAPSHOT
+
+PURGE_SNAPSHOT是DB4AI特性用于删除快照的接口函数。通过语法PURGE SNAPSHOT调用。
+
+**表 1** DB4AI.PURGE_SNAPSHOT入参和返回值列表
+
+| 参数     | 类型                    | 描述               |
+| :------- | :---------------------- | :----------------- |
+| i_schema | IN NAME                 | 快照存储的模式名字 |
+| i_name   | IN NAME                 | 快照名称           |
+| res      | OUT db4ai.snapshot_name | 结果               |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.PURGE_SNAPSHOT_INTERNAL.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.PURGE_SNAPSHOT_INTERNAL.md
new file mode 100644
index 0000000000000000000000000000000000000000..3b1fbc653e6be815fb9d33ee447201d91864eb68
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.PURGE_SNAPSHOT_INTERNAL.md
@@ -0,0 +1,17 @@
+---
+title: DB4AI.PURGE_SNAPSHOT_INTERNAL
+summary: DB4AI.PURGE_SNAPSHOT_INTERNAL
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DB4AI.PURGE_SNAPSHOT_INTERNAL
+
+PURGE_SNAPSHOT_INTERNAL是DB4AI.PURGE_SNAPSHOT函数的内置执行函数。函数存在信息校验，无法直接调用
+
+**表 1** DB4AI.PURGE_SNAPSHOT_INTERNAL入参和返回值列表
+
+| 参数     | 类型    | 描述               |
+| :------- | :------ | :----------------- |
+| i_schema | IN NAME | 快照存储的模式名字 |
+| i_name   | IN NAME | 快照名称           |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.SAMPLE_SNAPSHOT.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.SAMPLE_SNAPSHOT.md
new file mode 100644
index 0000000000000000000000000000000000000000..f4e16baeb7edc9097cd71ba09a23b2d600d9c3a3
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.SAMPLE_SNAPSHOT.md
@@ -0,0 +1,22 @@
+---
+title: DB4AI.SAMPLE_SNAPSHOT
+summary: DB4AI.SAMPLE_SNAPSHOT
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DB4AI.SAMPLE_SNAPSHOT
+
+SAMPLE_SNAPSHOT是DB4AI特性用于对基数据进行采样生成快照的接口函数。通过语法SAMPLE SNAPSHOT调用。
+
+**表 1** DB4AI.SAMPLE_SNAPSHOT入参和返回值列表
+
+| 参数              | 类型                    | 描述                           |
+| :---------------- | :---------------------- | :----------------------------- |
+| i_schema          | IN NAME                 | 快照存储的模式名字             |
+| i_parent          | IN NAME                 | 父快照名称                     |
+| i_sample_infixes  | IN NAME[]               | 示例快照名称中缀               |
+| i_sample_ratios   | IN NUMBER[]             | 每个样本的大小，作为父集的比率 |
+| i_stratify        | IN NAME[]               | 分层策略                       |
+| i_sample_comments | IN TEXT[]               | 示例快照描述                   |
+| res               | OUT db4ai.snapshot_name | 结果                           |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.SNAPSHOT.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.SNAPSHOT.md
new file mode 100644
index 0000000000000000000000000000000000000000..b4ac423404f47f0509c0084da7bb71c2d85b178d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/DB4AI.SNAPSHOT.md
@@ -0,0 +1,28 @@
+---
+title: DB4AI.SNAPSHOT
+summary: DB4AI.SNAPSHOT
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DB4AI.SNAPSHOT
+
+SNAPSHOT表记录当前用户通过特性DB4AI.SNAPSHOT存储的快照。
+
+**表 1** db4ai.snapshot表属性
+
+| 名称      | 类型                | 描述                       | 实例                   |
+| :-------- | :-----------------| :-------------------------- | :--------------------- |
+| id        | bigint                      | 当前快照的ID。                                            | 1                          |
+| parent_id | bigint                      | 父快照的ID。                                              | 0                          |
+| matrix_id | bigint                      | CSS模式下快照的矩阵ID，否则为NULL。                       | 0                          |
+| root_id   | bigint                      | 初始快照的ID，通过db4ai.create_snapshot()从操作数据构建。 | 0                          |
+| schema    | name                        | 导出快照视图的模式。                                      | public                     |
+| name      | name                        | 快照的名称，包括版本后缀。                                | example0@1.1.0             |
+| owner     | name                        | 创建此快照的用户的名称。                                  | nw                         |
+| commands  | text[]                      | 记录如何从其根快照生成到此快照的SQL语句的完整列表。       | {DELETE,“WHERE id > 7”}    |
+| comment   | text                        | 快照说明。                                                | inherits from @1.0.0       |
+| published | boolean                     | TRUE，当且仅当快照当前已发布。                            | f                          |
+| archived  | boolean                     | TRUE，当且仅当快照当前已存档。                            | f                          |
+| created   | timestamp without time zone | 快照创建日期的时间戳。                                    | 2021-08-25 10:59:52.955604 |
+| row_count | bigint                      | 此快照中的数据行数。                                      | 8                          |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/overview-of-DB4AI-schema.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/overview-of-DB4AI-schema.md
new file mode 100644
index 0000000000000000000000000000000000000000..dcad74cf81fc68bc8fd25855fb00b8df3e53f79c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DB4AI-schema/overview-of-DB4AI-schema.md
@@ -0,0 +1,10 @@
+---
+title: DB4AI Schema概述
+summary: DB4AI Schema概述
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DB4AI Schema概述
+
+DB4AI模式在AI特性中主要是用来存储和管理数据集版本。模式中保存数据表的原始视图快照，每一个数据版本的更改记录以及版本快照的管理信息。模式面向普通用户，用户可在该模式下查找特性DB4AI.SNAPSHOT创建的快照版本信息。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/DBE_PERF_overview.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/DBE_PERF_overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..af1d447dc34d80939f99af2f895882834098e428
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/DBE_PERF_overview.md
@@ -0,0 +1,40 @@
+---
+title: 概述
+summary: 概述
+author: Guo Huan
+date: 2021-04-19
+---
+
+# 概述
+
+DBE_PERF Schema内视图主要用来诊断性能问题，也是WDR Snapshot的数据来源。数据库安装后，默认只有初始用户具有模式dbe_perf的权限。若是由旧版本升级而来，为保持权限的前向兼容，模式dbe_perf的权限与旧版本保持一致。从OS、Instance、Memory等多个维度划分组织视图，并且符合如下命名规范:
+
+- GLOBAL_开头的视图，代表从数据库节点请求数据，并将数据追加对外返回，不会处理数据。
+- SUMMARY_开头的视图，代表是将MogDB内的数据概述，多数情况下是返回数据库节点（有时只有数据库主节点的）的数据，会对数据进行加工和汇聚。
+- 非这两者开头的视图，一般代表本地视图，不会向其它数据库节点请求数据。
+
+<br/>
+
+## 为其它用户赋予dbe_perf访问权限
+
+如果查询dbe_perf模式下的视图遇到以下报错，则表示权限不足：
+
+```sql
+mogdb=> select * from dbe_perf.statement;
+permission denied for schema dbe_perf
+LINE 1: select * from dbe_perf.statement
+                      ^
+mogdb=> select * from dbe_perf.statement;
+ERROR:  only system/monitor admin can query unique sql view
+```
+
+解决方法如下：
+
+使用omm用户将需要访问dbe_perf模式的用户更改为监控管理员，如：
+
+```sql
+mogdb=# ALTER USER mogdb_usr MONADMIN;
+ALTER ROLE
+```
+
+监控管理员是指具有MONADMIN属性的帐户，具有查看dbe_perf模式下视图和函数的权限，亦可以对dbe_perf模式的对象权限进行授予或收回。有关用户及权限的更多信息请参考[管理用户及权限](2-managing-users-and-their-permissions)。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-1.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-1.md
new file mode 100644
index 0000000000000000000000000000000000000000..0fad8948bb79958bb7be57c91871b38aa4f90a66
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-1.md
@@ -0,0 +1,48 @@
+---
+title: 表 1
+summary: 表 1
+author: Guo Huan
+date: 2021-04-19
+---
+
+**表 1** 等待状态列表<a id="表1"> </a>
+
+| wait_status值                           | 含义                                                                                                                                                                                                                                                             |
+| :-------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| none                                    | 没在等任意事件。                                                                                                                                                                                                                                                 |
+| acquire lock                            | 等待加锁，要么加锁成功，要么加锁等待超时。                                                                                                                                                                                                                       |
+| acquire lwlock                          | 等待获取轻量级锁。                                                                                                                                                                                                                                               |
+| wait io                                 | 等待IO完成。                                                                                                                                                                                                                                                     |
+| wait cmd                                | 等待完成读取网络通信包。                                                                                                                                                                                                                                         |
+| wait pooler get conn                    | 等待pooler完成获取连接。                                                                                                                                                                                                                                         |
+| wait pooler abort conn                  | 等待pooler完成终止连接。                                                                                                                                                                                                                                         |
+| wait pooler clean conn                  | 等待pooler完成清理连接。                                                                                                                                                                                                                                         |
+| pooler create conn: [nodename], total N | 等待pooler建立连接，当前正在与nodename指定节点建立连接，且仍有N个连接等待建立。                                                                                                                                                                                  |
+| get conn                                | 获取到其他节点的连接。                                                                                                                                                                                                                                           |
+| set cmd: [nodename]                     | 在连接上执行SET/RESET/TRANSACTION BLOCK LEVEL PARA SET/SESSION LEVEL PARA SET，当前正在nodename指定节点上执行。                                                                                                                                                  |
+| cancel query                            | 取消某连接上正在执行的SQL语句。                                                                                                                                                                                                                                  |
+| stop query                              | 停止某连接上正在执行的查询。                                                                                                                                                                                                                                     |
+| wait node: nodename, total N, [phase]   | 等待接收与某节点的连接上的数据，当前正在等待nodename节点plevel线程的数据，且仍有N个连接的数据待返回。如果状态包含phase信息，则可能的阶段状态有: <br/>- begin: 表示处于事务开始阶段。<br/>- commit: 表示处于事务提交阶段。<br/>- rollback: 表示处于事务回滚阶段。 |
+| wait transaction sync: xid              | 等待xid指定事务同步。                                                                                                                                                                                                                                            |
+| wait wal sync                           | 等待特定LSN的wal log完成到备机的同步。                                                                                                                                                                                                                           |
+| wait data sync                          | 等待完成数据页到备机的同步。                                                                                                                                                                                                                                     |
+| wait data sync queue                    | 等待把行存的数据页或列存的CU放入同步队列。                                                                                                                                                                                                                       |
+| flush data: nodename, [phase]           | 等待向网络中nodename指定节点的plevel对应线程发送数据。如果状态包含phase信息，则可能的阶段状态为wait quota，即当前通信流正在等待quota值。                                                                                                                         |
+| stream get conn: [nodename], total N    | 初始化stream flow时，等待与nodename节点的consumer对象建立连接，且当前有N个待建连对象。                                                                                                                                                                           |
+| wait producer ready: nodename, total N  | 初始化stream flow时，等待每个producer都准备好，当前正在等待nodename节点plevel对应线程的producer对象准备好，且仍有N个producer对象处于等待状态。                                                                                                                   |
+| synchronize quit                        | stream plan结束时，等待stream线程组内的线程统一退出。                                                                                                                                                                                                            |
+| wait stream nodegroup destroy           | stream plan结束时，等待销毁stream node group。                                                                                                                                                                                                                   |
+| wait active statement                   | 等待作业执行，正在资源负载管控中。                                                                                                                                                                                                                               |
+| analyze: [relname], [phase]             | 当前正在对表relname执行analyze。如果状态包含phase信息，则为autovacuum，表示是数据库自动开启AutoVacuum线程执行的analyze分析操作。                                                                                                                                 |
+| vacuum: [relname], [phase]              | 当前正在对表relname执行vacuum。如果状态包含phase信息，则为autovacuum，表示是数据库自动开启AutoVacuum线程执行的vacuum清理操作。                                                                                                                                   |
+| vacuum full: [relname]                  | 当前正在对表relname执行vacuum full清理。                                                                                                                                                                                                                         |
+| create index                            | 当前正在创建索引。                                                                                                                                                                                                                                               |
+| HashJoin - [ build hash \| write file ] | 当前是HashJoin算子，主要关注耗时的执行阶段。<br/>- build hash: 表示当前HashJoin算子正在建立哈希表。<br/>- write file: 表示当前HashJoin算子正在将数据写入磁盘。                                                                                                   |
+| HashAgg - [ build hash \| write file ]  | 当前是HashAgg算子，主要关注耗时的执行阶段。<br/>- build hash: 表示当前HashAgg算子正在建立哈希表。<br/>- write file: 表示当前HashAgg算子正在将数据写入磁盘。                                                                                                      |
+| HashSetop - [build hash \| write file ] | 当前是HashSetop算子，主要关注耗时的执行阶段。<br/>- build hash: 表示当前HashSetop算子正在建立哈希表。<br/>- write file: 表示当前HashSetop算子正在将数据写入磁盘。                                                                                                |
+| Sort \| Sort - write file               | 当前是Sort算子做排序，write file表示Sort算子正在将数据写入磁盘。                                                                                                                                                                                                 |
+| Material \| Material - write file       | 当前是Material算子，write file表示Material算子正在将数据写入磁盘。                                                                                                                                                                                               |
+| NestLoop                                | 当前是NestLoop算子。                                                                                                                                                                                                                                             |
+| wait memory                             | 等待内存获取。                                                                                                                                                                                                                                                   |
+| wait sync consumer next step            | Stream算子等待消费者执行。                                                                                                                                                                                                                                       |
+| wait sync producer next step            | Stream算子等待生产者执行。                                                                                                                                                                                                                                       |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-2.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-2.md
new file mode 100644
index 0000000000000000000000000000000000000000..aedf59d10fb75de7b21c876268f2b0f35541435b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-2.md
@@ -0,0 +1,131 @@
+---
+title: 表 2
+summary: 表 2
+author: Guo Huan
+date: 2021-04-19
+---
+
+**表 2** 轻量级锁等待事件列表<a id="表2"> </a>
+
+| wait_event类型                           | 类型描述                                                     |
+| :--------------------------------------- | :----------------------------------------------------------- |
+| ShmemIndexLock                           | 用于保护共享内存中的主索引哈希表。                           |
+| OidGenLock                               | 用于避免不同线程产生相同的OID。                              |
+| XidGenLock                               | 用于避免两个事务获得相同的xid。                              |
+| ProcArrayLock                            | 用于避免并发访问或修改ProcArray共享数组。                    |
+| SInvalReadLock                           | 用于避免与清理失效消息并发执行。                             |
+| SInvalWriteLock                          | 用于避免与其它写失效消息、清理失效消息并发执行。             |
+| WALInsertLock                            | 用于避免与其它WAL插入操作并发执行。                          |
+| WALWriteLock                             | 用于避免并发WAL写盘。                                        |
+| ControlFileLock                          | 用于避免pg_control文件的读写并发、写写并发。                 |
+| CheckpointLock                           | 用于避免多个checkpoint并发执行。                             |
+| CLogControlLock                          | 用于避免并发访问或者修改Clog控制数据结构。                   |
+| SubtransControlLock                      | 用于避免并发访问或者修改子事务控制数据结构。                 |
+| MultiXactGenLock                         | 用于串行分配唯一MultiXact id。                               |
+| MultiXactOffsetControlLock               | 用于避免对pg_multixact/offset的写写并发和读写并发。          |
+| MultiXactMemberControlLock               | 用于避免对pg_multixact/members的写写并发和读写并发。         |
+| RelCacheInitLock                         | 用于失效消息场景对init文件进行操作时加锁。                   |
+| CheckpointerCommLock                     | 用于向checkpointer发起文件刷盘请求场景，需要串行的向请求队列插入请求结构。 |
+| TwoPhaseStateLock                        | 用于避免并发访问或者修改两阶段信息共享数组。                 |
+| TablespaceCreateLock                     | 用于确定tablespace是否已经存在。                             |
+| BtreeVacuumLock                          | 用于防止vacuum清理B-tree中还在使用的页面。                   |
+| AutovacuumLock                           | 用于串行化访问autovacuum worker数组。                        |
+| AutovacuumScheduleLock                   | 用于串行化分配需要vacuum的table。                            |
+| AutoanalyzeLock                          | 用于获取和释放允许执行Autoanalyze的任务资源。                |
+| SyncScanLock                             | 用于确定heap扫描时某个relfilenode的起始位置。                |
+| NodeTableLock                            | 用于保护存放数据库节点信息的共享结构。                       |
+| PoolerLock                               | 用于保证两个线程不会同时从连接池里取到相同的连接。           |
+| RelationMappingLock                      | 用于等待更新系统表到存储位置之间映射的文件。                 |
+| AsyncCtlLock                             | 用于避免并发访问或者修改共享通知状态。                       |
+| AsyncQueueLock                           | 用于避免并发访问或者修改共享通知信息队列。                   |
+| SerializableXactHashLock                 | 用于避免对于可串行事务共享结构的写写并发和读写并发。         |
+| SerializableFinishedListLock             | 用于避免对于已完成可串行事务共享链表的写写并发和读写并发。   |
+| SerializablePredicateLockListLock        | 用于保护对于可串行事务持有的锁链表。                         |
+| OldSerXidLock                            | 用于保护记录冲突可串行事务的结构。                           |
+| FileStatLock                             | 用于保护存储统计文件信息的数据结构。                         |
+| SyncRepLock                              | 用于在主备复制时保护xlog同步信息。                           |
+| DataSyncRepLock                          | 用于在主备复制时保护数据页同步信息。                         |
+| CStoreColspaceCacheLock                  | 用于保护列存表的CU空间分配。                                 |
+| CStoreCUCacheSweepLock                   | 用于列存CU Cache循环淘汰。                                   |
+| MetaCacheSweepLock                       | 用于元数据循环淘汰。                                         |
+| ExtensionConnectorLibLock                | 用于初始化ODBC连接场景，在加载与卸载特定动态库时进行加锁。   |
+| SearchServerLibLock                      | 用于GPU加速场景初始化加载特定动态库时，对读文件操作进行加锁。 |
+| LsnXlogChkFileLock                       | 用于串行更新特定结构中记录的主备机的xlog flush位置点。       |
+| ReplicationSlotAllocationLock            | 用于主备复制时保护主机端的流复制槽的分配。                   |
+| ReplicationSlotControlLock               | 用于主备复制时避免并发更新流复制槽状态。                     |
+| ResourcePoolHashLock                     | 用于避免并发访问或者修改资源池哈希表。                       |
+| WorkloadStatHashLock                     | 用于避免并发访问或者修改包含数据库主节点的SQL请求构成的哈希表。 |
+| WorkloadIoStatHashLock                   | 用于避免并发访问或者修改用于统计当前数据库节点的IO信息的哈希表。 |
+| WorkloadCGroupHashLock                   | 用于避免并发访问或者修改Cgroup信息构成的哈希表。             |
+| OBSGetPathLock                           | 用于避免对obs路径的写写并发和读写并发。                      |
+| WorkloadUserInfoLock                     | 用于避免并发访问或修改负载管理的用户信息哈希表。             |
+| WorkloadRecordLock                       | 用于避免并发访问或修改在内存自适应管理时对数据库主节点收到请求构成的哈希表。 |
+| WorkloadIOUtilLock                       | 用于保护记录iostat，CPU等负载信息的结构。                    |
+| WorkloadNodeGroupLock                    | 用于避免并发访问或者修改内存中的nodegroup信息构成的哈希表。  |
+| JobShmemLock                             | 用于定时任务功能中保护定时读取的全局变量。                   |
+| OBSRuntimeLock                           | 用于获取环境变量，如GASSHOME。                               |
+| LLVMDumpIRLock                           | 用于导出动态生成函数所对应的汇编语言。                       |
+| LLVMParseIRLock                          | 用于在查询开始处从IR文件中编译并解析已写好的IR函数。         |
+| CriticalCacheBuildLock                   | 用于从共享或者本地缓存初始化文件中加载cache的场景。          |
+| WaitCountHashLock                        | 用于保护用户语句计数功能场景中的共享结构。                   |
+| BufMappingLock                           | 用于保护对共享缓冲映射表的操作。                             |
+| LockMgrLock                              | 用于保护常规锁结构信息。                                     |
+| PredicateLockMgrLock                     | 用于保护可串行事务锁结构信息。                               |
+| OperatorRealTLock                        | 用于避免并发访问或者修改记录算子级实时数据的全局结构。       |
+| OperatorHistLock                         | 用于避免并发访问或者修改记录算子级历史数据的全局结构。       |
+| SessionRealTLock                         | 用于避免并发访问或者修改记录query级实时数据的全局结构。      |
+| SessionHistLock                          | 用于避免并发访问或者修改记录query级历史数据的全局结构。      |
+| CacheSlotMappingLock                     | 用于保护CU Cache全局信息。                                   |
+| BarrierLock                              | 用于保证当前只有一个线程在创建Barrier。                      |
+| dummyServerInfoCacheLock                 | 用于保护缓存加速MogDB连接信息的全局哈希表。                  |
+| RPNumberLock                             | 用于加速MogDB的数据库节点对正在执行计划的任务线程的计数。    |
+| ClusterRPLock                            | 用于加速MogDB的CCN中维护的MogDB负载数据的并发存取控制。      |
+| CBMParseXlogLock                         | Cbm 解析xlog时的保护锁                                       |
+| RelfilenodeReuseLock                     | 避免错误地取消已重用的列属性文件的链接。                     |
+| RcvWriteLock                             | 防止并发调用WalDataRcvWrite。                                |
+| PercentileLock                           | 用于保护全局PercentileBuffer                                 |
+| CSNBufMappingLock                        | 保护csn页面                                                  |
+| UniqueSQLMappingLock                     | 用于保护uniquesql hash table                                 |
+| DelayDDLLock                             | 防止并发ddl。                                                |
+| CLOG Ctl                                 | 用于避免并发访问或者修改Clog控制数据结构                     |
+| Async Ctl                                | 保护Async buffer                                             |
+| MultiXactOffset Ctl                      | 保护MultiXact offet的slru buffer                             |
+| MultiXactMember Ctl                      | 保护MultiXact member的slrubuffer                             |
+| OldSerXid SLRU Ctl                       | 保护old xids的slru buffer                                    |
+| ReplicationSlotLock                      | 用于保护ReplicationSlot                                      |
+| PGPROCLock                               | 用于保护pgproc                                               |
+| MetaCacheLock                            | 用于保护MetaCache                                            |
+| DataCacheLock                            | 用于保护datacache                                            |
+| InstrUserLock                            | 用于保护InstrUserHTAB。                                      |
+| BadBlockStatHashLock                     | 用于保护global_bad_block_stat hash表。                       |
+| BufFreelistLock                          | 用于保证共享缓冲区空闲列表操作的原子性。                     |
+| CUSlotListLock                           | 用于控制列存缓冲区槽位的并发操作。                           |
+| AddinShmemInitLock                       | 保护共享内存对象的初始化。                                   |
+| AlterPortLock                            | 保护协调节点更改注册端口号的操作。                           |
+| FdwPartitionCaheLock                     | HDFS分区表缓冲区的管理锁。                                   |
+| DfsConnectorCacheLock                    | DFSConnector缓冲区的管理锁。                                 |
+| DfsSpaceCacheLock                        | HDFS表空间管理缓冲区的管理锁。                               |
+| FullBuildXlogCopyStartPtrLock            | 用于保护全量Build中Xlog拷贝的操作。                          |
+| DfsUserLoginLock                         | 用于HDFS用户登录以及认证。                                   |
+| LogicalReplicationSlotPersistentDataLock | 用于保护逻辑复制过程中复制槽位的数据。                       |
+| WorkloadSessionInfoLock                  | 保护负载管理session info内存hash表访问。                     |
+| InstrWorkloadLock                        | 保护负载管理统计信息的内存hash表访问。                       |
+| PgfdwLock                                | 用于管理实例向Foreign server建立连接。                       |
+| InstanceTimeLock                         | 用于获取实例中会话的时间信息。                               |
+| XlogRemoveSegLock                        | 保护Xlog段文件的回收操作。                                   |
+| DnUsedSpaceHashLock                      | 用于更新会话对应的空间使用信息。                             |
+| CsnMinLock                               | 用于计算CSNmin。                                             |
+| GPCCommitLock                            | 用于保护全局Plan Cache hash表的添加操作。                    |
+| GPCClearLock                             | 用于保护全局Plan Cache hash表的清除操作。                    |
+| GPCTimelineLock                          | 用于保护全局Plan Cache hash表检查Timeline的操作。            |
+| TsTagsCacheLock                          | 用于时序tag缓存管理。                                        |
+| InstanceRealTLock                        | 用于保护共享实例统计信息hash表的更新操作。                   |
+| CLogBufMappingLock                       | 用于提交日志缓存管理。                                       |
+| GPCMappingLock                           | 用于全局Plan Cache缓存管理。                                 |
+| GPCPrepareMappingLock                    | 用于全局Plan Cache缓存管理。                                 |
+| BufferIOLock                             | 保护共享缓冲区页面的IO操作。                                 |
+| BufferContentLock                        | 保护共享缓冲区页面内容的读取、修改。                         |
+| CSNLOG Ctl                               | 用于CSN日志管理。                                            |
+| DoubleWriteLock                          | 用于双写的管理操作。                                         |
+| RowPageReplicationLock                   | 用于管理行存储的数据页复制。                                 |
+| extension                                | 其他轻量锁。                                                 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-3.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-3.md
new file mode 100644
index 0000000000000000000000000000000000000000..f9a351a8ab06eaceafa3e7a0433998a0021cb6b6
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-3.md
@@ -0,0 +1,71 @@
+---
+title: 表 3
+summary: 表 3
+author: Guo Huan
+date: 2021-04-19
+---
+
+**表 3** IO等待事件列表<a id="表3"> </a>
+
+| wait_event类型             | 类型描述                                                     |
+| :------------------------- | :----------------------------------------------------------- |
+| BufFileRead                | 从临时文件中读取数据到指定buffer。                           |
+| BufFileWrite               | 向临时文件中写入指定buffer中的内容。                         |
+| ControlFileRead            | 读取pg_control文件。主要在数据库启动、执行checkpoint和主备校验过程中发生。 |
+| ControlFileSync            | 将pg_control文件持久化到磁盘。数据库初始化时发生。           |
+| ControlFileSyncUpdate      | 将pg_control文件持久化到磁盘。主要在数据库启动、执行checkpoint和主备校验过程中发生。 |
+| ControlFileWrite           | 写入pg_control文件。数据库初始化时发生。                     |
+| ControlFileWriteUpdate     | 更新pg_control文件。主要在数据库启动、执行checkpoint和主备校验过程中发生。 |
+| CopyFileRead               | copy文件时读取文件内容。                                     |
+| CopyFileWrite              | copy文件时写入文件内容。                                     |
+| DataFileExtend             | 扩展文件时向文件写入内容。                                   |
+| DataFileFlush              | 将表数据文件持久化到磁盘                                     |
+| DataFileImmediateSync      | 将表数据文件立即持久化到磁盘。                               |
+| DataFilePrefetch           | 异步读取表数据文件。                                         |
+| DataFileRead               | 同步读取表数据文件。                                         |
+| DataFileSync               | 将表数据文件的修改持久化到磁盘。                             |
+| DataFileTruncate           | 表数据文件truncate。                                         |
+| DataFileWrite              | 向表数据文件写入内容。                                       |
+| LockFileAddToDataDirRead   | 读取"postmaster.pid"文件。                                   |
+| LockFileAddToDataDirSync   | 将"postmaster.pid"内容持久化到磁盘。                         |
+| LockFileAddToDataDirWrite  | 将pid信息写到"postmaster.pid"文件。                          |
+| LockFileCreateRead         | 读取LockFile文件"%s.lock"。                                  |
+| LockFileCreateSync         | 将LockFile文件"%s.lock"内容持久化到磁盘。                    |
+| LockFileCreateWRITE        | 将pid信息写到LockFile文件"%s.lock"。                         |
+| RelationMapRead            | 读取系统表到存储位置之间的映射文件                           |
+| RelationMapSync            | 将系统表到存储位置之间的映射文件持久化到磁盘。               |
+| RelationMapWrite           | 写入系统表到存储位置之间的映射文件。                         |
+| ReplicationSlotRead        | 读取流复制槽文件。重新启动时发生。                           |
+| ReplicationSlotRestoreSync | 将流复制槽文件持久化到磁盘。重新启动时发生。                 |
+| ReplicationSlotSync        | checkpoint时将流复制槽临时文件持久化到磁盘。                 |
+| ReplicationSlotWrite       | checkpoint时写流复制槽临时文件。                             |
+| SLRUFlushSync              | 将pg_clog、pg_subtrans和pg_multixact文件持久化到磁盘。主要在执行checkpoint和数据库停机时发生。 |
+| SLRURead                   | 读取pg_clog、pg_subtrans和pg_multixact文件。                 |
+| SLRUSync                   | 将脏页写入文件pg_clog、pg_subtrans和pg_multixact并持久化到磁盘。主要在执行checkpoint和数据库停机时发生。 |
+| SLRUWrite                  | 写入pg_clog、pg_subtrans和pg_multixact文件。                 |
+| TimelineHistoryRead        | 读取timeline history文件。在数据库启动时发生。               |
+| TimelineHistorySync        | 将timeline history文件持久化到磁盘。在数据库启动时发生。     |
+| TimelineHistoryWrite       | 写入timeline history文件。在数据库启动时发生。               |
+| TwophaseFileRead           | 读取pg_twophase文件。在两阶段事务提交、两阶段事务恢复时发生。 |
+| TwophaseFileSync           | 将pg_twophase文件持久化到磁盘。在两阶段事务提交、两阶段事务恢复时发生。 |
+| TwophaseFileWrite          | 写入pg_twophase文件。在两阶段事务提交、两阶段事务恢复时发生。 |
+| WALBootstrapSync           | 将初始化的WAL文件持久化到磁盘。在数据库初始化发生。          |
+| WALBootstrapWrite          | 写入初始化的WAL文件。在数据库初始化发生。                    |
+| WALCopyRead                | 读取已存在的WAL文件并进行复制时产生的读操作。在执行归档恢复完后发生。 |
+| WALCopySync                | 将复制的WAL文件持久化到磁盘。在执行归档恢复完后发生。        |
+| WALCopyWrite               | 读取已存在WAL文件并进行复制时产生的写操作。在执行归档恢复完后发生。 |
+| WALInitSync                | 将新初始化的WAL文件持久化磁盘。在日志回收或写日志时发生。    |
+| WALInitWrite               | 将新创建的WAL文件初始化为0。在日志回收或写日志时发生。       |
+| WALRead                    | 从xlog日志读取数据。两阶段文件redo相关的操作产生。           |
+| WALSyncMethodAssign        | 将当前打开的所有WAL文件持久化到磁盘。                        |
+| WALWrite                   | 写入WAL文件。                                                |
+| WALBufferAccess            | WAL Buffer访问（出于性能考虑，内核代码里只统计访问次数，未统计其访问耗时）。 |
+| WALBufferFull              | WAL Buffer满时，写wal文件相关的处理。                        |
+| DoubleWriteFileRead        | 双写 文件读取。                                              |
+| DoubleWriteFileSync        | 双写 文件强制刷盘。                                          |
+| DoubleWriteFileWrite       | 双写 文件写入。                                              |
+| PredoProcessPending        | 并行日志回放中当前记录回放等待其它记录回放完成。             |
+| PredoApply                 | 并行日志回放中等待当前工作线程等待其他线程回放至本线程LSN。  |
+| DisableConnectFileRead     | HA锁分片逻辑文件读取。                                       |
+| DisableConnectFileSync     | HA锁分片逻辑文件强制刷盘。                                   |
+| DisableConnectFileWrite    | HA锁分片逻辑文件写入。                                       |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-4.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-4.md
new file mode 100644
index 0000000000000000000000000000000000000000..fd6a1dfd15e01324c950a99f0021b1b672b97aa8
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-4.md
@@ -0,0 +1,23 @@
+---
+title: 表 4
+summary: 表 4
+author: Guo Huan
+date: 2021-04-19
+---
+
+**表 4** 事务锁等待事件列表<a id="表4"> </a>
+
+| wait_event类型   | 类型描述              |
+| :--------------- | :-------------------- |
+| relation         | 对表加锁。            |
+| extend           | 对表扩展空间时加锁。  |
+| partition        | 对分区表加锁。        |
+| partition_seq    | 对分区表的分区加锁。  |
+| page             | 对表页面加锁。        |
+| tuple            | 对页面上的tuple加锁。 |
+| transactionid    | 对事务ID加锁。        |
+| virtualxid       | 对虚拟事务ID加锁。    |
+| object           | 加对象锁。            |
+| cstore_freespace | 对列存空闲空间加锁。  |
+| userlock         | 加用户锁。            |
+| advisory         | 加advisory锁。        |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-5.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-5.md
new file mode 100644
index 0000000000000000000000000000000000000000..1dc56252a47e696c64536695d6bbb9b52e86d985
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-5.md
@@ -0,0 +1,79 @@
+---
+title: 表 5
+summary: 表 5
+author: Guo Huan
+date: 2021-04-19
+---
+
+**表 5** GS_WLM_SESSION_HISTORY的字段<a id="GS_WLM_SESSION_HISTORY的字段"> </a>
+
+| 名称                | 类型                     | 描述                                                         |
+| :------------------ | :----------------------- | :----------------------------------------------------------- |
+| datid               | oid                      | 连接后端的数据库OID。                                        |
+| dbname              | text                     | 连接后端的数据库名称。                                       |
+| schemaname          | text                     | 模式的名称。                                                 |
+| nodename            | text                     | 语句执行的数据库节点名称。                                   |
+| username            | text                     | 连接到后端的用户名。                                         |
+| application_name    | text                     | 连接到后端的应用名。                                         |
+| client_addr         | inet                     | 连接到后端的客户端的IP地址。 如果此字段是null，它表明通过服务器机器上UNIX套接字连接客户端或者这是内部进程，如autovacuum。 |
+| client_hostname     | text                     | 客户端的主机名，这个字段是通过client_addr的反向DNS查找得到。这个字段只有在启动log_hostname且使用IP连接时才非空。 |
+| client_port         | integer                  | 客户端用于与后端通讯的TCP端口号，如果使用Unix套接字，则为-1。 |
+| query_band          | text                     | 用于标示作业类型，可通过GUC参数query_band进行设置，默认为空字符串。 |
+| block_time          | bigint                   | 语句执行前的阻塞时间，包含语句解析和优化时间，单位ms。       |
+| start_time          | timestamp with time zone | 语句执行的开始时间。                                         |
+| finish_time         | timestamp with time zone | 语句执行的结束时间。                                         |
+| duration            | bigint                   | 语句实际执行的时间，单位ms。                                 |
+| estimate_total_time | bigint                   | 语句预估执行时间，单位ms。                                   |
+| status              | text                     | 语句执行结束状态: 正常为finished，异常为aborted。            |
+| abort_info          | text                     | 语句执行结束状态为aborted时显示异常信息。                    |
+| resource_pool       | text                     | 用户使用的资源池。                                           |
+| control_group       | text                     | 该字段不支持                                                 |
+| estimate_memory     | integer                  | 语句估算内存大小。                                           |
+| min_peak_memory     | integer                  | 语句在数据库节点上的最小内存峰值，单位MB。                   |
+| max_peak_memory     | integer                  | 语句在数据库节点上的最大内存峰值，单位MB。                   |
+| average_peak_memory | integer                  | 语句执行过程中的内存使用平均值，单位MB。                     |
+| memory_skew_percent | integer                  | 语句数据库节点间的内存使用倾斜率。                           |
+| spill_info          | text                     | 语句在数据库节点上的下盘信息: <br/>- None: 数据库节点均未下盘。<br/>- All: 数据库节点均下盘。<br/>- [a:b]: 数量为b个数据库节点中有a个数据库节点下盘。 |
+| min_spill_size      | integer                  | 若发生下盘，数据库节点上下盘的最小数据量，单位MB，默认为0。  |
+| max_spill_size      | integer                  | 若发生下盘，数据库节点上下盘的最大数据量，单位MB，默认为0。  |
+| average_spill_size  | integer                  | 若发生下盘，数据库节点上下盘的平均数据量，单位MB，默认为0。  |
+| spill_skew_percent  | integer                  | 若发生下盘，数据库节点间下盘倾斜率。                         |
+| min_dn_time         | bigint                   | 语句在数据库节点上的最小执行时间，单位ms。                   |
+| max_dn_time         | bigint                   | 语句在数据库节点上的最大执行时间，单位ms。                   |
+| average_dn_time     | bigint                   | 语句在数据库节点上的平均执行时间，单位ms。                   |
+| dntime_skew_percent | integer                  | 语句在数据库节点间的执行时间倾斜率。                         |
+| min_cpu_time        | bigint                   | 语句在数据库节点上的最小CPU时间，单位ms。                    |
+| max_cpu_time        | bigint                   | 语句在数据库节点上的最大CPU时间，单位ms。                    |
+| total_cpu_time      | bigint                   | 语句在数据库节点上的CPU总时间，单位ms。                      |
+| cpu_skew_percent    | integer                  | 语句在数据库节点间的CPU时间倾斜率。                          |
+| min_peak_iops       | integer                  | 语句在数据库节点上的每秒最小IO峰值（列存单位是次/s，行存单位是万次/s）。 |
+| max_peak_iops       | integer                  | 语句在数据库节点上的每秒最大IO峰值（列存单位是次/s，行存单位是万次/s）。 |
+| average_peak_iops   | integer                  | 语句在数据库节点上的每秒平均IO峰值（列存单位是次/s，行存单位是万次/s）。 |
+| iops_skew_percent   | integer                  | 语句在数据库节点间的IO倾斜率。                               |
+| warning             | text                     | 主要显示如下几类告警信息: <br/>- Spill file size large than 256MB<br/>- Broadcast size large than 100MB<br/>- Early spill<br/>- Spill times is greater than 3<br/>- Spill on memory adaptive<br/>- Hash table conflict |
+| queryid             | bigint                   | 语句执行使用的内部query id。                                 |
+| query               | text                     | 执行的语句。                                                 |
+| query_plan          | text                     | 语句的执行计划。                                             |
+| node_group          | text                     | 该字段不支持。                                               |
+| cpu_top1_node_name  | text                     | 当前数据库节点名称。                                         |
+| cpu_top2_node_name  | text                     | 该字段不支持。                                               |
+| cpu_top3_node_name  | text                     | 该字段不支持。                                               |
+| cpu_top4_node_name  | text                     | 该字段不支持。                                               |
+| cpu_top5_node_name  | text                     | 该字段不支持。                                               |
+| mem_top1_node_name  | text                     | 当前数据库节点名称。                                         |
+| mem_top2_node_name  | text                     | 该字段不支持。                                               |
+| mem_top3_node_name  | text                     | 该字段不支持。                                               |
+| mem_top4_node_name  | text                     | 该字段不支持。                                               |
+| mem_top5_node_name  | text                     | 该字段不支持。                                               |
+| cpu_top1_value      | bigint                   | 当前数据库节点cpu使用率。                                    |
+| cpu_top2_value      | bigint                   | 该字段不支持。                                               |
+| cpu_top3_value      | bigint                   | 该字段不支持。                                               |
+| cpu_top4_value      | bigint                   | 该字段不支持。                                               |
+| cpu_top5_value      | bigint                   | 该字段不支持。                                               |
+| mem_top1_value      | bigint                   | 当前数据库节点内存使用量。                                   |
+| mem_top2_value      | bigint                   | 该字段不支持。                                               |
+| mem_top3_value      | bigint                   | 该字段不支持。                                               |
+| mem_top4_value      | bigint                   | 该字段不支持。                                               |
+| mem_top5_value      | bigint                   | 该字段不支持。                                               |
+| top_mem_dn          | text                     | 当前数据库节点内存使用量信息。                               |
+| top_cpu_dn          | text                     | 当前数据库节点cpu使用量信息。                                |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-6.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-6.md
new file mode 100644
index 0000000000000000000000000000000000000000..4901beda5c26f6c50f5984026b65a54f40299a25
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/appendices/table-6.md
@@ -0,0 +1,33 @@
+---
+title: 表 6
+summary: 表 6
+author: Guo Huan
+date: 2021-04-19
+---
+
+**表 6** GS_WLM_OPERATOR_INFO的字段<a id="表6"> </a>
+
+| 名称                | 类型                     | 描述                                                         |
+| :------------------ | :----------------------- | :----------------------------------------------------------- |
+| queryid             | bigint                   | 语句执行使用的内部query_id。                                 |
+| pid                 | bigint                   | 后端线程id。                                                 |
+| plan_node_id        | integer                  | 查询对应的执行计划的plan node id。                           |
+| plan_node_name      | text                     | 对应于plan_node_id的算子的名称。                             |
+| start_time          | timestamp with time zone | 该算子处理第一条数据的开始时间。                             |
+| duration            | bigint                   | 该算子到结束时候总的执行时间(ms)。                           |
+| query_dop           | integer                  | 当前算子执行时的并行度。                                     |
+| estimated_rows      | bigint                   | 优化器估算的行数信息。                                       |
+| tuple_processed     | bigint                   | 当前算子返回的元素个数。                                     |
+| min_peak_memory     | integer                  | 当前算子在数据库节点上的最小内存峰值(MB)。                   |
+| max_peak_memory     | integer                  | 当前算子在数据库节点上的最大内存峰值(MB)。                   |
+| average_peak_memory | integer                  | 当前算子在数据库节点平均内存峰值(MB)。                       |
+| memory_skew_percent | integer                  | 当前算子在数据库节点间的内存使用倾斜率。                     |
+| min_spill_size      | integer                  | 若发生下盘，数据库节点盘的最小数据量(MB)，默认为0。          |
+| max_spill_size      | integer                  | 若发生下盘，数据库节点上下盘的最大数据量(MB)，默认为0。      |
+| average_spill_size  | integer                  | 若发生下盘，数据库节点盘的平均数据量(MB)，默认为0。          |
+| spill_skew_percent  | integer                  | 若发生下盘，数据库节点间下盘倾斜率。                         |
+| min_cpu_time        | bigint                   | 该算子在数据库节点最小执行时间(ms)。                         |
+| max_cpu_time        | bigint                   | 该算子在数据库节点上的最大执行时间(ms)。                     |
+| total_cpu_time      | bigint                   | 该算子在数据库节点上的总执行时间(ms)。                       |
+| cpu_skew_percent    | integer                  | 数据库节点间执行时间的倾斜率。                               |
+| warning             | text                     | 主要显示如下几类告警信息: <br/>- Sort/SetOp/HashAgg/HashJoin spill<br/>- Spill file size large than 256MB<br/>- Broadcast size large than 100MB<br/>- Early spill<br/>- Spill times is greater than 3<br/>- Spill on memory adaptive<br/>- Hash table conflict |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_ALL_INDEXES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_ALL_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..5ff44a51a0de6f94e44c9e9be2c8b976fbc56c39
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_ALL_INDEXES.md
@@ -0,0 +1,23 @@
+---
+title: GLOBAL_STATIO_ALL_INDEXES
+summary: GLOBAL_STATIO_ALL_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STATIO_ALL_INDEXES
+
+GLOBAL_STATIO_ALL_INDEXES视图包含各节点的数据库中的每个索引行，显示特定索引的I/O的统计。
+
+**表 1** GLOBAL_STATIO_ALL_INDEXES字段
+
+| **名称**      | **类型** | **描述**                 |
+| :------------ | :------- | :----------------------- |
+| node_name     | name     | 数据库进程名称。         |
+| relid         | oid      | 索引的表的OID。          |
+| indexrelid    | oid      | 该索引的OID。            |
+| schemaname    | name     | 该索引的模式名。         |
+| relname       | name     | 该索引的表名。           |
+| indexrelname  | name     | 索引名称。               |
+| idx_blks_read | numeric  | 从索引中读取的磁盘块数。 |
+| idx_blks_hit  | numeric  | 索引命中缓存数。         |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_ALL_SEQUENCES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_ALL_SEQUENCES.md
new file mode 100644
index 0000000000000000000000000000000000000000..5ddc20598b38b00fba8360034c9c6ad770d02c02
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_ALL_SEQUENCES.md
@@ -0,0 +1,21 @@
+---
+title: GLOBAL_STATIO_ALL_SEQUENCES
+summary: GLOBAL_STATIO_ALL_SEQUENCES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STATIO_ALL_SEQUENCES
+
+GLOBAL_STATIO_ALL_SEQUENCES包含各节点的数据库中每个序列的每一行，显示特定序列关于I/O的统计。
+
+**表 1** GLOBAL_STATIO_ALL_SEQUENCES字段
+
+| **名称**   | **类型** | **描述**                 |
+| :--------- | :------- | :----------------------- |
+| node_name  | name     | 数据库进程名称。         |
+| relid      | oid      | 序列OID。                |
+| schemaname | name     | 序列中模式名。           |
+| relname    | name     | 序列名。                 |
+| blks_read  | bigint   | 从序列中读取的磁盘块数。 |
+| blks_hit   | bigint   | 序列中缓存命中数。       |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_ALL_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_ALL_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..21c237191da5cacd494a29431d48597a45548863
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_ALL_TABLES.md
@@ -0,0 +1,27 @@
+---
+title: GLOBAL_STATIO_ALL_TABLES
+summary: GLOBAL_STATIO_ALL_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STATIO_ALL_TABLES
+
+GLOBAL_STATIO_ALL_TABLES视图将包含各节点的数据库中每个表（包括TOAST表）的I/O的统计。
+
+**表 1** GLOBAL_STATIO_ALL_TABLES字段
+
+| **名称**        | **类型** | **描述**                                      |
+| :-------------- | :------- | :-------------------------------------------- |
+| node_name       | name     | 数据库进程名称。                              |
+| relid           | oid      | 表OID。                                       |
+| schemaname      | name     | 该表模式名。                                  |
+| relname         | name     | 表名。                                        |
+| heap_blks_read  | bigint   | 从该表中读取的磁盘块数。                      |
+| heap_blks_hit   | bigint   | 此表缓存命中数。                              |
+| idx_blks_read   | bigint   | 从表中所有索引读取的磁盘块数。                |
+| idx_blks_hit    | bigint   | 表中所有索引命中缓存数。                      |
+| toast_blks_read | bigint   | 此表的TOAST表读取的磁盘块数（如果存在）。     |
+| toast_blks_hit  | bigint   | 此表的TOAST表命中缓冲区数（如果存在）。       |
+| tidx_blks_read  | bigint   | 此表的TOAST表索引读取的磁盘块数（如果存在）。 |
+| tidx_blks_hit   | bigint   | 此表的TOAST表索引命中缓冲区数（如果存在）。   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_SYS_INDEXES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_SYS_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..1047814a09c7e4ce6dca101d92677da452f67654
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_SYS_INDEXES.md
@@ -0,0 +1,23 @@
+---
+title: GLOBAL_STATIO_SYS_INDEXES
+summary: GLOBAL_STATIO_SYS_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STATIO_SYS_INDEXES
+
+GLOBAL_STATIO_SYS_INDEXES视图显示各节点的命名空间中所有系统表索引的IO状态信息。
+
+**表 1** GLOBAL_STATIO_SYS_INDEXES字段
+
+| **名称**      | **类型** | **描述**                 |
+| :------------ | :------- | :----------------------- |
+| node_name     | name     | 数据库进程名称。         |
+| relid         | oid      | 索引的表的OID。          |
+| indexrelid    | oid      | 该索引的OID。            |
+| schemaname    | name     | 该索引的模式名。         |
+| relname       | name     | 该索引的表名。           |
+| indexrelname  | name     | 索引名称。               |
+| idx_blks_read | numeric  | 从索引中读取的磁盘块数。 |
+| idx_blks_hit  | numeric  | 索引命中缓存数。         |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_SYS_SEQUENCES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_SYS_SEQUENCES.md
new file mode 100644
index 0000000000000000000000000000000000000000..26dad17018efb783d1dbf8aa3636b3dcba920c28
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_SYS_SEQUENCES.md
@@ -0,0 +1,21 @@
+---
+title: GLOBAL_STATIO_SYS_SEQUENCES
+summary: GLOBAL_STATIO_SYS_SEQUENCES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STATIO_SYS_SEQUENCES
+
+GLOBAL_STATIO_SYS_SEQUENCES视图显示各节点的命名空间中所有系统表为序列的IO状态信息。
+
+**表 1** GLOBAL_STATIO_SYS_SEQUENCES字段
+
+| **名称**   | **类型** | **描述**                 |
+| :--------- | :------- | :----------------------- |
+| node_name  | name     | 数据库进程名称。         |
+| relid      | oid      | 序列OID。                |
+| schemaname | name     | 序列中模式名。           |
+| relname    | name     | 序列名。                 |
+| blks_read  | bigint   | 从序列中读取的磁盘块数。 |
+| blks_hit   | bigint   | 序列中缓存命中数。       |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_SYS_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_SYS_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..ac2ec1c1071b0513032cc4530fb9155eeb950136
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_SYS_TABLES.md
@@ -0,0 +1,27 @@
+---
+title: GLOBAL_STATIO_SYS_TABLES
+summary: GLOBAL_STATIO_SYS_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STATIO_SYS_TABLES
+
+GLOBAL_STATIO_SYS_TABLES视图显示各节点的命名空间中所有系统表的IO状态信息。
+
+**表 1** GLOBAL_STATIO_SYS_TABLES字段
+
+| **名称**        | **类型** | **描述**                                      |
+| :-------------- | :------- | :-------------------------------------------- |
+| node_name       | name     | 数据库进程名称。                              |
+| relid           | oid      | 表OID。                                       |
+| schemaname      | name     | 该表模式名。                                  |
+| relname         | name     | 表名。                                        |
+| heap_blks_read  | bigint   | 从该表中读取的磁盘块数。                      |
+| heap_blks_hit   | bigint   | 此表缓存命中数。                              |
+| idx_blks_read   | bigint   | 从表中所有索引读取的磁盘块数。                |
+| idx_blks_hit    | bigint   | 表中所有索引命中缓存数。                      |
+| toast_blks_read | bigint   | 此表的TOAST表读取的磁盘块数（如果存在）。     |
+| toast_blks_hit  | bigint   | 此表的TOAST表命中缓冲区数（如果存在）。       |
+| tidx_blks_read  | bigint   | 此表的TOAST表索引读取的磁盘块数（如果存在）。 |
+| tidx_blks_hit   | bigint   | 此表的TOAST表索引命中缓冲区数（如果存在）。   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_USER_INDEXES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_USER_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..e68c8503657372d040e6119fec338083a301d9c6
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_USER_INDEXES.md
@@ -0,0 +1,23 @@
+---
+title: GLOBAL_STATIO_USER_INDEXES
+summary: GLOBAL_STATIO_USER_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STATIO_USER_INDEXES
+
+GLOBAL_STATIO_USER_INDEXES视图显示各节点的命名空间中所有用户关系表索引的IO状态信息。
+
+**表 1** GLOBAL_STATIO_USER_INDEXES字段
+
+| **名称**      | **类型** | **描述**                 |
+| :------------ | :------- | :----------------------- |
+| node_name     | name     | 数据库进程名称。         |
+| relid         | oid      | 索引的表的OID。          |
+| indexrelid    | oid      | 该索引的OID。            |
+| schemaname    | name     | 该索引的模式名。         |
+| relname       | name     | 该索引的表名。           |
+| indexrelname  | name     | 索引名称。               |
+| idx_blks_read | numeric  | 从索引中读取的磁盘块数。 |
+| idx_blks_hit  | numeric  | 索引命中缓存数。         |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_USER_SEQUENCES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_USER_SEQUENCES.md
new file mode 100644
index 0000000000000000000000000000000000000000..c66e96121135ea9cf57db9bebac602077907afe8
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_USER_SEQUENCES.md
@@ -0,0 +1,21 @@
+---
+title: GLOBAL_STATIO_USER_SEQUENCES
+summary: GLOBAL_STATIO_USER_SEQUENCES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STATIO_USER_SEQUENCES
+
+GLOBAL_STATIO_USER_SEQUENCES视图显示各节点的命名空间中所有用户关系表类型为序列的IO状态信息。
+
+**表 1** GLOBAL_STATIO_USER_SEQUENCES字段
+
+| **名称**   | **类型** | **描述**                 |
+| :--------- | :------- | :----------------------- |
+| node_name  | name     | 数据库进程名称。         |
+| relid      | oid      | 序列OID。                |
+| schemaname | name     | 序列中模式名。           |
+| relname    | name     | 序列名。                 |
+| blks_read  | bigint   | 从序列中读取的磁盘块数。 |
+| blks_hit   | bigint   | 序列中缓存命中数。       |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_USER_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_USER_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..bf44f8fbbdada36f0215b190b20728ffc9e588b4
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_USER_TABLES.md
@@ -0,0 +1,27 @@
+---
+title: GLOBAL_STATIO_USER_TABLES
+summary: GLOBAL_STATIO_USER_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STATIO_USER_TABLES
+
+GLOBAL_STATIO_USER_TABLES视图显示各节点的命名空间中所有用户关系表的IO状态信息。
+
+**表 1** GLOBAL_STATIO_USER_TABLES字段
+
+| **名称**        | **类型** | **描述**                                      |
+| :-------------- | :------- | :-------------------------------------------- |
+| node_name       | name     | 节点名称。                                    |
+| relid           | oid      | 表OID。                                       |
+| schemaname      | name     | 该表模式名。                                  |
+| relname         | name     | 表名。                                        |
+| heap_blks_read  | bigint   | 从该表中读取的磁盘块数。                      |
+| heap_blks_hit   | bigint   | 此表缓存命中数。                              |
+| idx_blks_read   | bigint   | 从表中所有索引读取的磁盘块数。                |
+| idx_blks_hit    | bigint   | 表中所有索引命中缓存数。                      |
+| toast_blks_read | bigint   | 此表的TOAST表读取的磁盘块数（如果存在）。     |
+| toast_blks_hit  | bigint   | 此表的TOAST表命中缓冲区数（如果存在）。       |
+| tidx_blks_read  | bigint   | 此表的TOAST表索引读取的磁盘块数（如果存在）。 |
+| tidx_blks_hit   | bigint   | 此表的TOAST表索引命中缓冲区数（如果存在）。   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STAT_DB_CU.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STAT_DB_CU.md
new file mode 100644
index 0000000000000000000000000000000000000000..4be800dbe0c0c0f7adf39d6f4bb96e4efd63bfbb
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STAT_DB_CU.md
@@ -0,0 +1,20 @@
+---
+title: GLOBAL_STAT_DB_CU
+summary: GLOBAL_STAT_DB_CU
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STAT_DB_CU
+
+GLOBAL_STAT_DB_CU视图用于查询MogDB，每个数据库的CU命中情况。可以通过pg_stat_reset()进行清零。
+
+**表 1** GLOBAL_STAT_DB_CU字段
+
+| **名称**      | **类型** | **描述**         |
+| :------------ | :------- | :--------------- |
+| node_name1    | text     | 数据库进程名称。 |
+| db_name       | text     | 数据库名。       |
+| mem_hit       | bigint   | 内存命中次数。   |
+| hdd_sync_read | bigint   | 硬盘同步读次数。 |
+| hdd_asyn_read | bigint   | 硬盘异步读次数。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STAT_SESSION_CU.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STAT_SESSION_CU.md
new file mode 100644
index 0000000000000000000000000000000000000000..80084c530f005b643913df3ec7bca030bd36a885
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STAT_SESSION_CU.md
@@ -0,0 +1,18 @@
+---
+title: GLOBAL_STAT_SESSION_CU
+summary: GLOBAL_STAT_SESSION_CU
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STAT_SESSION_CU
+
+GLOBAL_STAT_SESSION_CU用于查询MogDB各个节点，当前运行session的CU命中情况。session退出相应的统计数据会清零。MogDB重启后，统计数据也会清零。
+
+**表 1** GLOBAL_STAT_SESSION_CU字段
+
+| **名称**      | **类型** | **描述**         |
+| :------------ | :------- | :--------------- |
+| mem_hit       | integer  | 内存命中次数。   |
+| hdd_sync_read | integer  | 硬盘同步读次数。 |
+| hdd_asyn_read | integer  | 硬盘异步读次数。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_ALL_INDEXES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_ALL_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..4f72a7a4f9a78ba04eb818d0c0abe6703cb9747b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_ALL_INDEXES.md
@@ -0,0 +1,22 @@
+---
+title: STATIO_ALL_INDEXES
+summary: STATIO_ALL_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATIO_ALL_INDEXES
+
+STATIO_ALL_INDEXES视图包含数据库中的每个索引行，显示特定索引的I/O的统计。
+
+**表 1** STATIO_ALL_INDEXES字段
+
+| **名称**      | **类型** | **描述**                 |
+| :------------ | :------- | :----------------------- |
+| relid         | oid      | 索引的表的OID。          |
+| indexrelid    | oid      | 该索引的OID。            |
+| schemaname    | name     | 该索引的模式名。         |
+| relname       | name     | 该索引的表名。           |
+| indexrelname  | name     | 索引名称。               |
+| idx_blks_read | bigint   | 从索引中读取的磁盘块数。 |
+| idx_blks_hit  | bigint   | 索引命中缓存数。         |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_ALL_SEQUENCES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_ALL_SEQUENCES.md
new file mode 100644
index 0000000000000000000000000000000000000000..d7b4edd73d7e23065c81b900bac79780611836f6
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_ALL_SEQUENCES.md
@@ -0,0 +1,20 @@
+---
+title: STATIO_ALL_SEQUENCES
+summary: STATIO_ALL_SEQUENCES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATIO_ALL_SEQUENCES
+
+STATIO_ALL_SEQUENCES视图包含数据库中每个序列的每一行，显示特定序列关于I/O的统计。
+
+**表 1** STATIO_ALL_SEQUENCES字段
+
+| **名称**   | **类型** | **描述**                 |
+| :--------- | :------- | :----------------------- |
+| relid      | oid      | 序列OID。                |
+| schemaname | name     | 序列中模式名。           |
+| relname    | name     | 序列名。                 |
+| blks_read  | bigint   | 从序列中读取的磁盘块数。 |
+| blks_hit   | bigint   | 序列中缓存命中数。       |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_ALL_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_ALL_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..a7d09ecf5d503e7af957cdb0275b8dce3e6aa4db
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_ALL_TABLES.md
@@ -0,0 +1,26 @@
+---
+title: STATIO_ALL_TABLES
+summary: STATIO_ALL_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATIO_ALL_TABLES
+
+STATIO_ALL_TABLES视图将包含数据库中每个表（包括TOAST表）的一行，显示出特定表I/O的统计。
+
+**表 1** STATIO_ALL_TABLES字段
+
+| **名称**        | **类型** | **描述**                                      |
+| :-------------- | :------- | :-------------------------------------------- |
+| relid           | oid      | 表OID。                                       |
+| schemaname      | name     | 该表模式名。                                  |
+| relname         | name     | 表名。                                        |
+| heap_blks_read  | bigint   | 从该表中读取的磁盘块数。                      |
+| heap_blks_hit   | bigint   | 该表缓存命中数。                              |
+| idx_blks_read   | bigint   | 从表中所有索引读取的磁盘块数。                |
+| idx_blks_hit    | bigint   | 表中所有索引命中缓存数。                      |
+| toast_blks_read | bigint   | 该表的TOAST表读取的磁盘块数（如果存在）。     |
+| toast_blks_hit  | bigint   | 该表的TOAST表命中缓冲区数（如果存在）。       |
+| tidx_blks_read  | bigint   | 该表的TOAST表索引读取的磁盘块数（如果存在）。 |
+| tidx_blks_hit   | bigint   | 该表的TOAST表索引命中缓冲区数（如果存在）。   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_SYS_INDEXES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_SYS_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..11d09a628a8cf04a0080af430b789aa89afd65ea
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_SYS_INDEXES.md
@@ -0,0 +1,22 @@
+---
+title: STATIO_SYS_INDEXES
+summary: STATIO_SYS_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATIO_SYS_INDEXES
+
+STATIO_SYS_INDEXES显示命名空间中所有系统表索引的IO状态信息。
+
+**表 1** STATIO_SYS_INDEXES字段
+
+| **名称**      | **类型** | **描述**                 |
+| :------------ | :------- | :----------------------- |
+| relid         | oid      | 索引的表的OID。          |
+| indexrelid    | oid      | 该索引的OID。            |
+| schemaname    | name     | 该索引的模式名。         |
+| relname       | name     | 该索引的表名。           |
+| indexrelname  | name     | 索引名称。               |
+| idx_blks_read | bigint   | 从索引中读取的磁盘块数。 |
+| idx_blks_hit  | bigint   | 索引命中缓存数。         |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_SYS_SEQUENCES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_SYS_SEQUENCES.md
new file mode 100644
index 0000000000000000000000000000000000000000..1bfe6db083348353c37bc0a7a210d50957e28d52
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_SYS_SEQUENCES.md
@@ -0,0 +1,20 @@
+---
+title: STATIO_SYS_SEQUENCES
+summary: STATIO_SYS_SEQUENCES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATIO_SYS_SEQUENCES
+
+STATIO_SYS_SEQUENCES显示命名空间中所有系统表为序列的IO状态信息。
+
+**表 1** STATIO_SYS_SEQUENCES字段
+
+| **名称**   | **类型** | **描述**                 |
+| :--------- | :------- | :----------------------- |
+| relid      | oid      | 序列OID。                |
+| schemaname | name     | 序列中模式名。           |
+| relname    | name     | 序列名。                 |
+| blks_read  | bigint   | 从序列中读取的磁盘块数。 |
+| blks_hit   | bigint   | 序列中缓存命中数。       |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_SYS_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_SYS_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..62e954f71940e4a411b1b68746fbead3a76abfdf
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_SYS_TABLES.md
@@ -0,0 +1,26 @@
+---
+title: STATIO_SYS_TABLES
+summary: STATIO_SYS_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATIO_SYS_TABLES
+
+STATIO_SYS_TABLES视图显示命名空间中所有系统表的IO状态信息。
+
+**表 1** STATIO_SYS_TABLES字段
+
+| **名称**        | **类型** | **描述**                                      |
+| :-------------- | :------- | :-------------------------------------------- |
+| relid           | oid      | 表OID。                                       |
+| schemaname      | name     | 该表模式名。                                  |
+| relname         | name     | 表名。                                        |
+| heap_blks_read  | bigint   | 从该表中读取的磁盘块数。                      |
+| heap_blks_hit   | bigint   | 该表缓存命中数。                              |
+| idx_blks_read   | bigint   | 从表中所有索引读取的磁盘块数。                |
+| idx_blks_hit    | bigint   | 表中所有索引命中缓存数。                      |
+| toast_blks_read | bigint   | 该表的TOAST表读取的磁盘块数（如果存在）。     |
+| toast_blks_hit  | bigint   | 该表的TOAST表命中缓冲区数（如果存在）。       |
+| tidx_blks_read  | bigint   | 该表的TOAST表索引读取的磁盘块数（如果存在）。 |
+| tidx_blks_hit   | bigint   | 该表的TOAST表索引命中缓冲区数（如果存在）。   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_USER_INDEXES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_USER_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..c6731a4f9775e7bd96941c1a9e1b7ed8be146919
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_USER_INDEXES.md
@@ -0,0 +1,22 @@
+---
+title: STATIO_USER_INDEXES
+summary: STATIO_USER_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATIO_USER_INDEXES
+
+STATIO_USER_INDEXES视图显示当前节点命名空间中所有用户关系表索引的IO状态信息。
+
+**表 1** STATIO_USER_INDEXES字段
+
+| **名称**      | **类型** | **描述**                 |
+| :------------ | :------- | :----------------------- |
+| relid         | oid      | 索引的表的OID。          |
+| indexrelid    | oid      | 该索引的OID。            |
+| schemaname    | name     | 该索引的模式名。         |
+| relname       | name     | 该索引的表名。           |
+| indexrelname  | name     | 索引名称。               |
+| idx_blks_read | bigint   | 从索引中读取的磁盘块数。 |
+| idx_blks_hit  | bigint   | 索引命中缓存数。         |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_USER_SEQUENCES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_USER_SEQUENCES.md
new file mode 100644
index 0000000000000000000000000000000000000000..4e55e9cdaa37c626998b26ca1f5857f7132cde0b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_USER_SEQUENCES.md
@@ -0,0 +1,20 @@
+---
+title: STATIO_USER_SEQUENCES
+summary: STATIO_USER_SEQUENCES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATIO_USER_SEQUENCES
+
+STATIO_USER_SEQUENCE视图显示当前节点的命名空间中所有用户关系表类型为序列的IO状态信息。
+
+**表 1** STATIO_USER_SEQUENCE字段
+
+| **名称**   | **类型** | **描述**                 |
+| :--------- | :------- | :----------------------- |
+| relid      | oid      | 序列OID。                |
+| schemaname | name     | 序列中模式名。           |
+| relname    | name     | 序列名。                 |
+| blks_read  | bigint   | 从序列中读取的磁盘块数。 |
+| blks_hit   | bigint   | 序列中缓存命中数。       |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_USER_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_USER_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..1f85ce3d21db30d2baf7f651cc005df816e1612e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/STATIO_USER_TABLES.md
@@ -0,0 +1,26 @@
+---
+title: STATIO_USER_TABLES
+summary: STATIO_USER_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATIO_USER_TABLES
+
+STATIO_USER_TABLES视图显示命名空间中所有用户关系表的IO状态信息。
+
+**表 1** STATIO_USER_TABLES字段
+
+| **名称**        | **类型** | **描述**                                      |
+| :-------------- | :------- | :-------------------------------------------- |
+| relid           | oid      | 表OID。                                       |
+| schemaname      | name     | 该表模式名。                                  |
+| relname         | name     | 表名。                                        |
+| heap_blks_read  | bigint   | 从该表中读取的磁盘块数。                      |
+| heap_blks_hit   | bigint   | 该表缓存命中数。                              |
+| idx_blks_read   | bigint   | 从表中所有索引读取的磁盘块数。                |
+| idx_blks_hit    | bigint   | 表中所有索引命中缓存数。                      |
+| toast_blks_read | bigint   | 该表的TOAST表读取的磁盘块数（如果存在）。     |
+| toast_blks_hit  | bigint   | 该表的TOAST表命中缓冲区数（如果存在）。       |
+| tidx_blks_read  | bigint   | 该表的TOAST表索引读取的磁盘块数（如果存在）。 |
+| tidx_blks_hit   | bigint   | 该表的TOAST表索引命中缓冲区数（如果存在）。   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_ALL_INDEXES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_ALL_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..45ac0ab5f037d2329bc79ba9ee8317fa731ebc20
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_ALL_INDEXES.md
@@ -0,0 +1,18 @@
+---
+title: SUMMARY_STATIO_ALL_INDEXES
+summary: SUMMARY_STATIO_ALL_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STATIO_ALL_INDEXES
+
+SUMMARY_STATIO_ALL_INDEXES视图包含含MogDB内汇聚的数据库中的每个索引行， 显示特定索引的I/O的统计。
+
+| **名称**      | **类型** | **描述**                 |
+| :------------ | :------- | :----------------------- |
+| schemaname    | name     | 该索引的模式名。         |
+| relname       | name     | 该索引的表名。           |
+| indexrelname  | name     | 索引名称。               |
+| idx_blks_read | numeric  | 从索引中读取的磁盘块数。 |
+| idx_blks_hit  | numeric  | 索引命中缓存数。         |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_ALL_SEQUENCES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_ALL_SEQUENCES.md
new file mode 100644
index 0000000000000000000000000000000000000000..4518191b1ff00238ae6fabf4b51065e69790adf2
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_ALL_SEQUENCES.md
@@ -0,0 +1,19 @@
+---
+title: SUMMARY_STATIO_ALL_SEQUENCES
+summary: SUMMARY_STATIO_ALL_SEQUENCES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STATIO_ALL_SEQUENCES
+
+SUMMARY_STATIO_ALL_SEQUENCES视图包含MogDB内汇聚的数据库中每个序列的每一行,显示特定序列关于I/O的统计。
+
+**表 1** SUMMARY_STATIO_ALL_SEQUENCES字段
+
+| **名称**   | **类型** | **描述**                 |
+| :--------- | :------- | :----------------------- |
+| schemaname | name     | 序列中模式名。           |
+| relname    | name     | 序列名。                 |
+| blks_read  | numeric  | 从序列中读取的磁盘块数。 |
+| blks_hit   | numeric  | 序列中缓存命中数。       |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_ALL_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_ALL_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..bf0d6d6e7ca042cdbf4f294eb8485ff077ebebf4
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_ALL_TABLES.md
@@ -0,0 +1,25 @@
+---
+title: SUMMARY_STATIO_ALL_TABLES
+summary: SUMMARY_STATIO_ALL_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STATIO_ALL_TABLES
+
+SUMMARY_STATIO_ALL_TABLES视图将包含MogDB内汇聚的数据库中每个表（包括TOAST表）的I/O的统计。
+
+**表 1** SUMMARY_STATIO_ALL_TABLES字段
+
+| **名称**        | **类型** | **描述**                                      |
+| :-------------- | :------- | :-------------------------------------------- |
+| schemaname      | name     | 该表模式名。                                  |
+| relname         | name     | 表名。                                        |
+| heap_blks_read  | numeric  | 从该表中读取的磁盘块数。                      |
+| heap_blks_hit   | numeric  | 此表缓存命中数。                              |
+| idx_blks_read   | numeric  | 从表中所有索引读取的磁盘块数。                |
+| idx_blks_hit    | numeric  | 表中所有索引命中缓存数。                      |
+| toast_blks_read | numeric  | 此表的TOAST表读取的磁盘块数（如果存在）。     |
+| toast_blks_hit  | numeric  | 此表的TOAST表命中缓冲区数（如果存在）。       |
+| tidx_blks_read  | numeric  | 此表的TOAST表索引读取的磁盘块数（如果存在）。 |
+| tidx_blks_hit   | numeric  | 此表的TOAST表索引命中缓冲区数（如果存在）。   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_SYS_INDEXES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_SYS_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..e257eaf8701db4220d23d681bc2b34c03776bf9c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_SYS_INDEXES.md
@@ -0,0 +1,20 @@
+---
+title: SUMMARY_STATIO_SYS_INDEXES
+summary: SUMMARY_STATIO_SYS_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STATIO_SYS_INDEXES
+
+SUMMARY_STATIO_SYS_INDEXES视图显示MogDB内汇聚的命名空间中所有系统表索引的IO状态信息。
+
+**表 1** SUMMARY_STATIO_SYS_INDEXES字段
+
+| **名称**      | **类型** | **描述**                 |
+| :------------ | :------- | :----------------------- |
+| schemaname    | name     | 该索引的模式名。         |
+| relname       | name     | 该索引的表名。           |
+| indexrelname  | name     | 索引名称。               |
+| idx_blks_read | numeric  | 从索引中读取的磁盘块数。 |
+| idx_blks_hit  | numeric  | 索引命中缓存数。         |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_SYS_SEQUENCES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_SYS_SEQUENCES.md
new file mode 100644
index 0000000000000000000000000000000000000000..27f2a3cc1c888ef94046ed6d3224b369ae19c53e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_SYS_SEQUENCES.md
@@ -0,0 +1,19 @@
+---
+title: SUMMARY_STATIO_SYS_SEQUENCES
+summary: SUMMARY_STATIO_SYS_SEQUENCES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STATIO_SYS_SEQUENCES
+
+SUMMARY_STATIO_SYS_SEQUENCES视图显示MogDB内汇聚的命名空间中所有系统表为序列的IO状态信息。
+
+**表 1** SUMMARY_STATIO_SYS_SEQUENCES字段
+
+| **名称**   | **类型** | **描述**                 |
+| :--------- | :------- | :----------------------- |
+| schemaname | name     | 序列中模式名。           |
+| relname    | name     | 序列名。                 |
+| blks_read  | numeric  | 从序列中读取的磁盘块数。 |
+| blks_hit   | numeric  | 序列中缓存命中数。       |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_SYS_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_SYS_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..cc71ea13d34f8b9a113e6212db74717e04b1d760
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_SYS_TABLES.md
@@ -0,0 +1,25 @@
+---
+title: SUMMARY_STATIO_SYS_TABLES
+summary: SUMMARY_STATIO_SYS_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STATIO_SYS_TABLES
+
+SUMMARY_STATIO_SYS_TABLES视图显示MogDB内汇聚的命名空间中所有系统表的IO状态信息。
+
+**表 1** SUMMARY_STATIO_SYS_TABLES字段
+
+| **名称**        | **类型** | **描述**                                      |
+| :-------------- | :------- | :-------------------------------------------- |
+| schemaname      | name     | 该表模式名。                                  |
+| relname         | name     | 表名。                                        |
+| heap_blks_read  | numeric  | 从该表中读取的磁盘块数。                      |
+| heap_blks_hit   | numeric  | 此表缓存命中数。                              |
+| idx_blks_read   | numeric  | 从表中所有索引读取的磁盘块数。                |
+| idx_blks_hit    | numeric  | 表中所有索引命中缓存数。                      |
+| toast_blks_read | numeric  | 此表的TOAST表读取的磁盘块数（如果存在）。     |
+| toast_blks_hit  | numeric  | 此表的TOAST表命中缓冲区数（如果存在）。       |
+| tidx_blks_read  | numeric  | 此表的TOAST表索引读取的磁盘块数（如果存在）。 |
+| tidx_blks_hit   | numeric  | 此表的TOAST表索引命中缓冲区数（如果存在）。   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_USER_INDEXES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_USER_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..56b1b428b0af5380df56463e83abb5f323cd83cd
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_USER_INDEXES.md
@@ -0,0 +1,20 @@
+---
+title: SUMMARY_STATIO_USER_INDEXES
+summary: SUMMARY_STATIO_USER_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STATIO_USER_INDEXES
+
+SUMMARY_STATIO_USER_INDEXES视图显示MogDB内汇聚的命名空间中所有用户关系表索引的IO状态信息。
+
+**表 1** SUMMARY_STATIO_USER_INDEXES字段
+
+| **名称**      | **类型** | **描述**                 |
+| :------------ | :------- | :----------------------- |
+| schemaname    | name     | 该索引的模式名。         |
+| relname       | name     | 该索引的表名。           |
+| indexrelname  | name     | 索引名称。               |
+| idx_blks_read | numeric  | 从索引中读取的磁盘块数。 |
+| idx_blks_hit  | numeric  | 索引命中缓存数。         |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_USER_SEQUENCES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_USER_SEQUENCES.md
new file mode 100644
index 0000000000000000000000000000000000000000..fade5e9322280f1727a84bf0f9f3157caaae9cef
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_USER_SEQUENCES.md
@@ -0,0 +1,19 @@
+---
+title: SUMMARY_STATIO_USER_SEQUENCES
+summary: SUMMARY_STATIO_USER_SEQUENCES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STATIO_USER_SEQUENCES
+
+SUMMARY_STATIO_USER_SEQUENCES视图显示MogDB内汇聚的命名空间中所有用户关系表类型为序列的IO状态信息。
+
+**表 1** SUMMARY_STATIO_USER_SEQUENCES字段
+
+| **名称**   | **类型** | **描述**                 |
+| :--------- | :------- | :----------------------- |
+| schemaname | name     | 序列中模式名。           |
+| relname    | name     | 序列名。                 |
+| blks_read  | numeric  | 从序列中读取的磁盘块数。 |
+| blks_hit   | numeric  | 序列中缓存命中数。       |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_USER_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_USER_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..931a2ca4e72252bf6fcc1f947c6c093cc95fce0d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_USER_TABLES.md
@@ -0,0 +1,25 @@
+---
+title: SUMMARY_STATIO_USER_TABLES
+summary: SUMMARY_STATIO_USER_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STATIO_USER_TABLES
+
+SUMMARY_STATIO_USER_TABLES视图显示MogDB内汇聚的命名空间中所有用户关系表的IO状态信息。
+
+**表 1** SUMMARY_STATIO_USER_TABLES字段
+
+| **名称**        | **类型** | **描述**                                      |
+| :-------------- | :------- | :-------------------------------------------- |
+| schemaname      | name     | 该表模式名。                                  |
+| relname         | name     | 表名。                                        |
+| heap_blks_read  | numeric  | 从该表中读取的磁盘块数。                      |
+| heap_blks_hit   | numeric  | 此表缓存命中数。                              |
+| idx_blks_read   | numeric  | 从表中所有索引读取的磁盘块数。                |
+| idx_blks_hit    | numeric  | 表中所有索引命中缓存数。                      |
+| toast_blks_read | numeric  | 此表的TOAST表读取的磁盘块数（如果存在）。     |
+| toast_blks_hit  | numeric  | 此表的TOAST表命中缓冲区数（如果存在）。       |
+| tidx_blks_read  | numeric  | 此表的TOAST表索引读取的磁盘块数（如果存在）。 |
+| tidx_blks_hit   | numeric  | 此表的TOAST表索引命中缓冲区数（如果存在）。   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/configuration/CONFIG_SETTINGS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/configuration/CONFIG_SETTINGS.md
new file mode 100644
index 0000000000000000000000000000000000000000..939ea1f65d96e5dca5aabf79b956642cf980b594
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/configuration/CONFIG_SETTINGS.md
@@ -0,0 +1,31 @@
+---
+title: CONFIG_SETTINGS
+summary: CONFIG_SETTINGS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# CONFIG_SETTINGS
+
+CONFIG_SETTINGS视图显示数据库运行时参数的相关信息。
+
+**表 1** CONFIG_SETTINGS字段
+
+| **名称**   | **类型** | **描述**                                                     |
+| :--------- | :------- | :----------------------------------------------------------- |
+| name       | text     | 参数名称。                                                   |
+| setting    | text     | 参数当前值。                                                 |
+| unit       | text     | 参数的隐式结构。                                             |
+| category   | text     | 参数的逻辑组。                                               |
+| short_desc | text     | 参数的简单描述。                                             |
+| extra_desc | text     | 参数的详细描述。                                             |
+| context    | text     | 设置参数值的上下文，包括internal、postmaster、sighup、backend、superuser、user。 |
+| vartype    | text     | 参数类型，包括bool、enum、integer、real、string。            |
+| source     | text     | 参数的赋值方式。                                             |
+| min_val    | text     | 参数最大值。如果参数类型不是数值型，那么该字段值为null。     |
+| max_val    | text     | 参数最小值。如果参数类型不是数值型，那么该字段值为null。     |
+| enumvals   | text[]   | enum类型参数合法值。如果参数类型不是enum型，那么该字段值为null。 |
+| boot_val   | text     | 数据库启动时参数默认值。                                     |
+| reset_val  | text     | 数据库重置时参数默认值。                                     |
+| sourcefile | text     | 设置参数值的配置文件。如果参数不是通过配置文件赋值，那么该字段值为null。 |
+| sourceline | integer  | 设置参数值的配置文件的行号。如果参数不是通过配置文件赋值，那么该字段值为null。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/configuration/GLOBAL_CONFIG_SETTINGS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/configuration/GLOBAL_CONFIG_SETTINGS.md
new file mode 100644
index 0000000000000000000000000000000000000000..831a78dc3b1e76a382198df48889bb067492e5bd
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/configuration/GLOBAL_CONFIG_SETTINGS.md
@@ -0,0 +1,32 @@
+---
+title: GLOBAL_CONFIG_SETTINGS
+summary: GLOBAL_CONFIG_SETTINGS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_CONFIG_SETTINGS
+
+GLOBAL_CONFIG_SETTINGS显示各节点数据库运行时参数的相关信息。
+
+**表 1** GLOBAL_CONFIG_SETTINGS的字段
+
+| **名称**   | **类型** | **描述**                                                     |
+| :--------- | :------- | :----------------------------------------------------------- |
+| node_name  | text     | 数据库进程名称。                                             |
+| name       | text     | 参数名称。                                                   |
+| setting    | text     | 参数当前值。                                                 |
+| unit       | text     | 参数的隐式结构。                                             |
+| category   | text     | 参数的逻辑组。                                               |
+| short_desc | text     | 参数的简单描述。                                             |
+| extra_desc | text     | 参数的详细描述。                                             |
+| context    | text     | 设置参数值的上下文，包括internal、postmaster、sighup、backend、superuser、user。 |
+| vartype    | text     | 参数类型，包括bool、enum、integer、real、string。            |
+| source     | text     | 参数的赋值方式。                                             |
+| min_val    | text     | 参数最大值。如果参数类型不是数值型，那么该字段值为null。     |
+| max_val    | text     | 参数最小值。如果参数类型不是数值型，那么该字段值为null。     |
+| enumvals   | text[]   | enum类型参数合法值。如果参数类型不是enum型，那么该字段值为null。 |
+| boot_val   | text     | 数据库启动时参数默认值。                                     |
+| reset_val  | text     | 数据库重置时参数默认值。                                     |
+| sourcefile | text     | 设置参数值的配置文件。如果参数不是通过配置文件赋值，那么该字段值为null。 |
+| sourceline | integer  | 设置参数值的配置文件的行号。如果参数不是通过配置文件赋值，那么该字段值为null。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/FILE_IOSTAT.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/FILE_IOSTAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..2f880dd60903d702f7c66faab7fe2aa9bdcd5a51
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/FILE_IOSTAT.md
@@ -0,0 +1,28 @@
+---
+title: FILE_IOSTAT
+summary: FILE_IOSTAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# FILE_IOSTAT
+
+通过对数据文件IO的统计，反映数据的IO性能，用以发现IO操作异常等性能问题。
+
+**表 1** FILE_IOSTAT字段
+
+| **名称**  | **类型** | **描述**                           |
+| :-------- | :------- | :--------------------------------- |
+| filenum   | oid      | 文件标识。                         |
+| dbid      | oid      | 数据库标识。                       |
+| spcid     | oid      | 表空间标识。                       |
+| phyrds    | bigint   | 读物理文件的数目。                 |
+| phywrts   | bigint   | 写物理文件的数目。                 |
+| phyblkrd  | bigint   | 读物理文件块的数目。               |
+| phyblkwrt | bigint   | 写物理文件块的数目。               |
+| readtim   | bigint   | 读文件的总时长（单位: 微秒）。     |
+| writetim  | bigint   | 写文件的总时长（单位: 微秒）。     |
+| avgiotim  | bigint   | 读写文件的平均时长（单位: 微秒）。 |
+| lstiotim  | bigint   | 最后一次读文件时长（单位: 微秒）。 |
+| miniotim  | bigint   | 读写文件的最小时长（单位: 微秒）。 |
+| maxiowtm  | bigint   | 读写文件的最大时长（单位: 微秒）。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/FILE_REDO_IOSTAT.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/FILE_REDO_IOSTAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..141c66dff85c28cb9b44aff7dd0b5363104e8139
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/FILE_REDO_IOSTAT.md
@@ -0,0 +1,22 @@
+---
+title: FILE_REDO_IOSTAT
+summary: FILE_REDO_IOSTAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# FILE_REDO_IOSTAT
+
+本节点Redo（WAL）相关的统计信息。
+
+**表 1** FILE_REDO_IOSTAT字段
+
+| **名称**  | **类型** | **描述**                                             |
+| :-------- | :------- | :--------------------------------------------------- |
+| phywrts   | bigint   | 向wal buffer中写的次数。                             |
+| phyblkwrt | bigint   | 向wal buffer中写的block的块数。                      |
+| writetim  | bigint   | 向xlog文件中写操作的时间（单位: 微秒）。             |
+| avgiotim  | bigint   | 平均写xlog的时间（writetim/phywrts）（单位: 微秒）。 |
+| lstiotim  | bigint   | 最后一次写xlog的时间（单位: 微秒）。                 |
+| miniotim  | bigint   | 最小的写xlog时间（单位: 微秒）。                     |
+| maxiowtm  | bigint   | 最大的写xlog时间（单位: 微秒）。                     |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/GLOBAL_FILE_IOSTAT.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/GLOBAL_FILE_IOSTAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..7404c0a63d8ab33751ab84127b64814eb8b25864
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/GLOBAL_FILE_IOSTAT.md
@@ -0,0 +1,29 @@
+---
+title: GLOBAL_FILE_IOSTAT
+summary: GLOBAL_FILE_IOSTAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_FILE_IOSTAT
+
+得到所有节点上的数据文件IO统计信息。
+
+**表 1** GLOBAL_FILE_IOSTAT字段
+
+| **名称**  | **类型** | **描述**                           |
+| :-------- | :------- | :--------------------------------- |
+| node_name | name     | 数据库进程名称。                   |
+| filenum   | oid      | 文件标识。                         |
+| dbid      | oid      | 数据库标识。                       |
+| spcid     | oid      | 表空间标识。                       |
+| phyrds    | bigint   | 读物理文件的数目。                 |
+| phywrts   | bigint   | 写物理文件的数目。                 |
+| phyblkrd  | bigint   | 读物理文件块的数目。               |
+| phyblkwrt | bigint   | 写物理文件块的数目。               |
+| readtim   | bigint   | 读文件的总时长（单位: 微秒）。     |
+| writetim  | bigint   | 写文件的总时长（单位: 微秒）。     |
+| avgiotim  | bigint   | 读写文件的平均时长（单位: 微秒）。 |
+| lstiotim  | bigint   | 最后一次读文件时长（单位: 微秒）。 |
+| miniotim  | bigint   | 读写文件的最小时长（单位: 微秒）。 |
+| maxiowtm  | bigint   | 读写文件的最大时长（单位: 微秒）。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/GLOBAL_FILE_REDO_IOSTAT.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/GLOBAL_FILE_REDO_IOSTAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..77cdb05658bbbe217dca9ff0bee95a3eb8a5dfa5
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/GLOBAL_FILE_REDO_IOSTAT.md
@@ -0,0 +1,23 @@
+---
+title: GLOBAL_FILE_REDO_IOSTAT
+summary: GLOBAL_FILE_REDO_IOSTAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_FILE_REDO_IOSTAT
+
+得到MogDB内各节点的Redo（WAL）相关统计信息。
+
+**表 1** GLOBALXC_FILE_REDO_IOSTAT字段
+
+| **名称**  | **类型** | **描述**                                             |
+| :-------- | :------- | :--------------------------------------------------- |
+| node_name | name     | 数据库进程名称。                                     |
+| phywrts   | bigint   | 向wal buffer中写的次数。                             |
+| phyblkwrt | bigint   | 向wal buffer中写的block的块数。                      |
+| writetim  | bigint   | 向xlog文件中写操作的时间（单位: 微秒）。             |
+| avgiotim  | bigint   | 平均写xlog的时间（writetim/phywrts）（单位: 微秒）。 |
+| lstiotim  | bigint   | 最后一次写xlog的时间（单位: 微秒）。                 |
+| miniotim  | bigint   | 最小的写xlog时间（单位: 微秒）。                     |
+| maxiowtm  | bigint   | 最大的写xlog时间（单位: 微秒）。                     |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/GLOBAL_REL_IOSTAT.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/GLOBAL_REL_IOSTAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..87072d366243f9219dcef6d8c244a3d7e07c136b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/GLOBAL_REL_IOSTAT.md
@@ -0,0 +1,20 @@
+---
+title: GLOBAL_REL_IOSTAT
+summary: GLOBAL_REL_IOSTAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_REL_IOSTAT
+
+获取所有节点上的数据文件IO统计信息。
+
+**表 1** GLOBAL_REL_IOSTAT字段
+
+| **名称**  | **类型** | **描述**             |
+| :-------- | :------- | :------------------- |
+| node_name | name     | 数据库进程名称。     |
+| phyrds    | bigint   | 读物理文件的数目。   |
+| phywrts   | bigint   | 写物理文件的数目。   |
+| phyblkrd  | bigint   | 读物理文件块的数目。 |
+| phyblkwrt | bigint   | 写物理文件块的数目。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/LOCAL_REL_IOSTAT.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/LOCAL_REL_IOSTAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..6dfe33ab6c181381f103b486bd9361187d6aa9de
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/LOCAL_REL_IOSTAT.md
@@ -0,0 +1,19 @@
+---
+title: LOCAL_REL_IOSTAT
+summary: LOCAL_REL_IOSTAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# LOCAL_REL_IOSTAT
+
+获取当前节点中数据文件IO状态的累计值，显示为所有数据文件IO状态的总和。
+
+**表 1** LOCAL_REL_IOSTAT字段
+
+| **名称**  | **类型** | **描述**               |
+| :-------- | :------- | :--------------------- |
+| phyrds    | bigint   | 读物理文件的数目。     |
+| phywrts   | bigint   | 写物理文件的数目。     |
+| phyblkrd  | bigint   | 读物理文件的块的数目。 |
+| phyblkwrt | bigint   | 写物理文件的块的数目。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/SUMMARY_FILE_IOSTAT.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/SUMMARY_FILE_IOSTAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..ca5cf619892407a95ab58f0aa32bbfea775d740c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/SUMMARY_FILE_IOSTAT.md
@@ -0,0 +1,28 @@
+---
+title: SUMMARY_FILE_IOSTAT
+summary: SUMMARY_FILE_IOSTAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_FILE_IOSTAT
+
+通过MogDB内对数据文件汇聚IO的统计，反映数据的IO性能，用以发现IO操作异常等性能问题。
+
+**表 1** SUMMARY_FILE_IOSTAT字段
+
+| **名称**  | **类型** | **描述**                           |
+| :-------- | :------- | :--------------------------------- |
+| filenum   | oid      | 文件标识。                         |
+| dbid      | oid      | 数据库标识。                       |
+| spcid     | oid      | 表空间标识。                       |
+| phyrds    | numeric  | 读物理文件的数目。                 |
+| phywrts   | numeric  | 写物理文件的数目。                 |
+| phyblkrd  | numeric  | 读物理文件块的数目。               |
+| phyblkwrt | numeric  | 写物理文件块的数目。               |
+| readtim   | numeric  | 读文件的总时长（单位: 微秒）。     |
+| writetim  | numeric  | 写文件的总时长（单位: 微秒）。     |
+| avgiotim  | bigint   | 读写文件的平均时长（单位: 微秒）。 |
+| lstiotim  | bigint   | 最后一次读文件时长（单位: 微秒）。 |
+| miniotim  | bigint   | 读写文件的最小时长（单位: 微秒）。 |
+| maxiowtm  | bigint   | 读写文件的最大时长（单位: 微秒）。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/SUMMARY_FILE_REDO_IOSTAT.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/SUMMARY_FILE_REDO_IOSTAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..278e43778537a9c03a59b47557f220ab64bbd40b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/SUMMARY_FILE_REDO_IOSTAT.md
@@ -0,0 +1,22 @@
+---
+title: SUMMARY_FILE_REDO_IOSTAT
+summary: SUMMARY_FILE_REDO_IOSTAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_FILE_REDO_IOSTAT
+
+MogDB内汇聚所有的Redo（WAL）相关的统计信息。
+
+**表 1** SUMMARY_FILE_REDO_IOSTAT字段
+
+| **名称**  | **类型** | **描述**                                             |
+| :-------- | :------- | :--------------------------------------------------- |
+| phywrts   | numeric  | 向wal buffer中写的次数。                             |
+| phyblkwrt | numeric  | 向wal buffer中写的block的块数。                      |
+| writetim  | numeric  | 向xlog文件中写操作的时间（单位: 微秒）。             |
+| avgiotim  | bigint   | 平均写xlog的时间（writetim/phywrts）（单位: 微秒）。 |
+| lstiotim  | bigint   | 最后一次写xlog的时间（单位: 微秒）。                 |
+| miniotim  | bigint   | 最小的写xlog时间（单位: 微秒）。                     |
+| maxiowtm  | bigint   | 最大的写xlog时间（单位: 微秒）。                     |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/SUMMARY_REL_IOSTAT.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/SUMMARY_REL_IOSTAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..13767cb303ea73d4eef8bef01a3351c1a90d5f21
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/file/SUMMARY_REL_IOSTAT.md
@@ -0,0 +1,19 @@
+---
+title: SUMMARY_REL_IOSTAT
+summary: SUMMARY_REL_IOSTAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_REL_IOSTAT
+
+获取所有节点上的数据文件IO统计信息。
+
+**表 1** SUMMARY_REL_IOSTAT字段
+
+| **名称**  | **类型** | **描述**               |
+| :-------- | :------- | :--------------------- |
+| phyrds    | numeric  | 读物理文件的数目。     |
+| phywrts   | numeric  | 写物理文件的数目。     |
+| phyblkrd  | numeric  | 读物理文件的块的数目。 |
+| phyblkwrt | numeric  | 写物理文件的块的数目。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/global-plancache/GLOBAL_PLANCACHE_CLEAN.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/global-plancache/GLOBAL_PLANCACHE_CLEAN.md
new file mode 100644
index 0000000000000000000000000000000000000000..5f97dcb4b288871c0ffb2f06ad2cc6f3b524bc95
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/global-plancache/GLOBAL_PLANCACHE_CLEAN.md
@@ -0,0 +1,10 @@
+---
+title: GLOBAL_PLANCACHE_CLEAN
+summary: GLOBAL_PLANCACHE_CLEAN
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_PLANCACHE_CLEAN
+
+GLOBAL_PLANCACHE_CLEAN视图用于清理所有节点上无人使用的全局计划缓存。返回值为Boolean类型。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/global-plancache/GLOBAL_PLANCACHE_STATUS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/global-plancache/GLOBAL_PLANCACHE_STATUS.md
new file mode 100644
index 0000000000000000000000000000000000000000..f6456b02de1f6fd67c31a0d5e2d62c9c18a7a857
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/global-plancache/GLOBAL_PLANCACHE_STATUS.md
@@ -0,0 +1,23 @@
+---
+title: GLOBAL_PLANCACHE_STATUS
+summary: GLOBAL_PLANCACHE_STATUS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_PLANCACHE_STATUS
+
+GLOBAL_PLANCACHE_STATUS视图显示GPC全局计划缓存状态信息。
+
+**表 1** GLOBAL_PLANCACHE_STATUS字段
+
+| 名称        | 类型    | 描述                                                  |
+| :---------- | :------ | :---------------------------------------------------- |
+| nodename    | text    | 所属节点名称。                                        |
+| query       | text    | 查询语句text。                                        |
+| refcount    | integer | 被引用次数。                                          |
+| valid       | bool    | 是否合法。                                            |
+| databaseid  | oid     | 所属数据库id。                                        |
+| schema_name | text    | 所属schema。                                          |
+| params_num  | integer | 参数数量。                                            |
+| func_id     | oid     | 该plancache所在存储过程oid，如果不属于存储过程则为0。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/global-plancache/global-plancache-overview.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/global-plancache/global-plancache-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..83333b6d2d15ddcfc00ba42caf6eec994434de19
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/global-plancache/global-plancache-overview.md
@@ -0,0 +1,10 @@
+---
+title: Overview
+summary: Overview
+author: Guo Huan
+date: 2021-04-19
+---
+
+# 概述
+
+GPC相关视图在enable_global_plancache打开且线程池打开的状态下才有效。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/instance/GLOBAL_INSTANCE_TIME.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/instance/GLOBAL_INSTANCE_TIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..5e28ba6c08b2ee2350b8187336c8e435c9ba9eea
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/instance/GLOBAL_INSTANCE_TIME.md
@@ -0,0 +1,19 @@
+---
+title: GLOBAL_INSTANCE_TIME
+summary: GLOBAL_INSTANCE_TIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_INSTANCE_TIME
+
+提供MogDB中所有正常节点下的各种时间消耗信息（时间类型见instance_time视图）。
+
+**表 1** GLOBAL_INSTANCE_TIME字段
+
+| **名称**  | **类型** | **描述**               |
+| :-------- | :------- | :--------------------- |
+| node_name | name     | 数据库进程的名称。     |
+| stat_id   | integer  | 统计编号。             |
+| stat_name | text     | 类型名称。             |
+| value     | bigint   | 时间值（单位: 微秒）。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/instance/INSTANCE_TIME.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/instance/INSTANCE_TIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..55beabc9709cb4c13aeb2282a87fe9dd0e244e8f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/instance/INSTANCE_TIME.md
@@ -0,0 +1,29 @@
+---
+title: INSTANCE_TIME
+summary: INSTANCE_TIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# INSTANCE_TIME
+
+提供当前节点下的各种时间消耗信息，主要分为以下类型:
+
+- DB_TIME: 作业在多核下的有效时间花销。
+- CPU_TIME: CPU的时间花销。
+- EXECUTION_TIME: 执行器内的时间花销。
+- PARSE_TIME: SQL解析的时间花销。
+- PLAN_TIME: 生成Plan的时间花销。
+- REWRITE_TIME: SQL重写的时间花销。
+- PL_EXECUTION_TIME : plpgsql（存储过程）执行的时间花销。
+- PL_COMPILATION_TIME: plpgsql（存储过程）编译的时间花销。
+- NET_SEND_TIME: 网络上的时间花销。
+- DATA_IO_TIME: IO上的时间花销。
+
+**表 1** INSTANCE_TIME字段
+
+| **名称**  | **类型** | **描述**               |
+| :-------- | :------- | :--------------------- |
+| stat_id   | integer  | 统计编号。             |
+| stat_name | text     | 类型名称。             |
+| value     | bigint   | 时间值（单位: 微秒）。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/lock/GLOBAL_LOCKS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/lock/GLOBAL_LOCKS.md
new file mode 100644
index 0000000000000000000000000000000000000000..e71aaa802a36219664a1e837078caf53f961376b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/lock/GLOBAL_LOCKS.md
@@ -0,0 +1,29 @@
+---
+title: GLOBAL_LOCKS
+summary: GLOBAL_LOCKS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_LOCKS
+
+GLOBAL_LOCKS视图用于查看各节点各打开事务所持有的锁信息。
+
+| **名称**           | **类型** | **描述**                                                     |
+| :----------------- | :------- | :----------------------------------------------------------- |
+| node_name          | name     | 数据库进程名称。                                             |
+| locktype           | text     | 被锁定对象的类型: relation、extend、page、tuple、transactionid、virtualxid、object、userlock、advisory。 |
+| database           | oid      | 被锁定对象所在数据库的OID: <br/>- 如果被锁定的对象是共享对象，则OID为0。<br/>- 如果是一个事务ID，则为NULL。 |
+| relation           | oid      | 关系的OID，如果锁定的对象不是关系，也不是关系的一部分，则为NULL。 |
+| page               | integer  | 关系内部的页面编号，如果对象不是关系页或者不是行页，则为NULL。 |
+| tuple              | smallint | 页面里边的行编号，如果对象不是行，则为NULL。                 |
+| virtualxid         | text     | 事务的虚拟ID，如果对象不是一个虚拟事务ID，则为NULL。         |
+| transactionid      | xid      | 事务的ID，如果对象不是一个事务ID，则为NULL。                 |
+| classid            | oid      | 包含该对象的系统表的OID，如果对象不是普通的数据库对象，则为NULL。 |
+| objid              | oid      | 对象在其系统表内的OID，如果对象不是普通数据库对象，则为NULL。 |
+| objsubid           | smallint | 对于表的一个字段，这是字段编号；对于其他对象类型，这个字段是零；如果这个对象不是普通数据库对象，则为NULL。 |
+| virtualtransaction | text     | 持有此锁或者在等待此锁的事务的虚拟ID。                       |
+| pid                | bigint   | 持有或者等待这个锁的服务器线程的逻辑ID。如果锁是被一个预备事务持有的，则为NULL。 |
+| mode               | text     | 这个线程持有的或者是期望的锁模式。                           |
+| granted            | boolean  | - 如果锁是持有锁，则为TRUE。<br/>- 如果锁是等待锁，则为FALSE。 |
+| fastpath           | boolean  | 如果通过fast-path获得锁，则为TRUE；如果通过主要的锁表获得，则为FALSE。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/lock/LOCKS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/lock/LOCKS.md
new file mode 100644
index 0000000000000000000000000000000000000000..832045e3bdb6ffca27f698d841e44ef64cf42316
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/lock/LOCKS.md
@@ -0,0 +1,34 @@
+---
+title: LOCKS
+summary: LOCKS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# LOCKS
+
+LOCKS视图用于查看各打开事务所持有的锁信息。
+
+**表 1** LOCKS字段
+
+| **名称**           | **类型** | **描述**                                                     |
+| :----------------- | :------- | :----------------------------------------------------------- |
+| locktype           | text     | 被锁定对象的类型: relation、extend、page、tuple、transactionid、virtualxid、object、userlock、advisory。 |
+| database           | oid      | 被锁定对象所在数据库的OID: <br/>- 如果被锁定的对象是共享对象，则OID为0。<br/>- 如果是一个事务ID，则为NULL。 |
+| relation           | oid      | 关系的OID，如果锁定的对象不是关系，也不是关系的一部分，则为NULL。 |
+| page               | integer  | 关系内部的页面编号，如果对象不是关系页或者不是行页，则为NULL。 |
+| tuple              | smallint | 页面里边的行编号，如果对象不是行，则为NULL。                 |
+| bucket             | integer  | 哈希桶号。                                                   |
+| virtualxid         | text     | 事务的虚拟ID，如果对象不是一个虚拟事务ID，则为NULL。         |
+| transactionid      | xid      | 事务的ID，如果对象不是一个事务ID，则为NULL。                 |
+| classid            | oid      | 包含该对象的系统表的OID，如果对象不是普通的数据库对象，则为NULL。 |
+| objid              | oid      | 对象在其系统表内的OID，如果对象不是普通数据库对象，则为NULL。 |
+| objsubid           | smallint | 对于表的一个字段，这是字段编号；对于其他对象类型，这个字段是0；如果这个对象不是普通数据库对象，则为NULL。 |
+| virtualtransaction | text     | 持有此锁或者在等待此锁的事务的虚拟ID。                       |
+| pid                | bigint   | 持有或者等待这个锁的服务器线程的逻辑ID。如果锁是被一个预备事务持有的，则为NULL。 |
+| sessionid          | bigint   | 持有或者等待这个锁的会话ID。如果锁是被一个预备事务持有的，则为NULL。 |
+| mode               | text     | 这个线程持有的或者是期望的锁模式。                           |
+| granted            | boolean  | - 如果锁是持有锁，则为TRUE。<br/>- 如果锁是等待锁，则为FALSE。 |
+| fastpath           | boolean  | 如果通过fast-path获得锁，则为TRUE；如果通过主要的锁表获得，则为FALSE。 |
+| locktag            | text     | 会话等待锁信息，可通过locktag_decode()函数解析。             |
+| global_sessionid   | text     | 全局会话ID。                                                 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/memory/GLOBAL_MEMORY_NODE_DETAIL.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/memory/GLOBAL_MEMORY_NODE_DETAIL.md
new file mode 100644
index 0000000000000000000000000000000000000000..89904a8b770bf9e1a57ce5fe2b3cc2cd3383a623
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/memory/GLOBAL_MEMORY_NODE_DETAIL.md
@@ -0,0 +1,18 @@
+---
+title: GLOBAL_MEMORY_NODE_DETAIL
+summary: GLOBAL_MEMORY_NODE_DETAIL
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_MEMORY_NODE_DETAIL
+
+显示当前MogDB中所有正常节点下的内存使用情况。
+
+**表 1** GLOBAL_MEMORY_NODE_DETAIL字段
+
+| **名称**     | **类型** | **描述**                      |
+| :----------- | :------- | :---------------------------|
+| nodename     | text     | 数据库进程名称。                        |
+| memorytype   | text     | 内存使用的名称。<br/>- max_process_memory: MogDB实例所占用的内存大小。<br/>- process_used_memory: 进程所使用的内存大小。<br/>- max_dynamic_memory: 最大动态内存。<br/>- dynamic_used_memory: 已使用的动态内存。<br/>- dynamic_peak_memory: 内存的动态峰值。<br/>- dynamic_used_shrctx: 最大动态共享内存上下文。<br/>- dynamic_peak_shrctx: 共享内存上下文的动态峰值。<br/>- max_shared_memory: 最大共享内存。<br/>- shared_used_memory: 已使用的共享内存。<br/>- max_cstore_memory: 列存所允许使用的最大内存。<br/>- cstore_used_memory: 列存已使用的内存大小。<br/>- max_sctpcomm_memory: sctp通信所允许使用的最大内存。<br/>- sctpcomm_used_memory: sctp通信已使用的内存大小。<br/>- sctpcomm_peak_memory: sctp通信的内存峰值。<br/>- other_used_memory: 其他已使用的内存大小。<br/>- gpu_max_dynamic_memory: GPU最大动态内存。<br/>- gpu_dynamic_used_memory: GPU已使用的动态内存。<br/>- gpu_dynamic_peak_memory: GPU内存的动态峰值。<br/>- pooler_conn_memory: 链接池申请内存计数。<br/>- pooler_freeconn_memory: 链接池空闲连接的内存计数。<br/>- storage_compress_memory: 存储模块压缩使用的内存大小。<br/>- udf_reserved_memory: UDF预留的内存大小。 |
+| memorymbytes | integer  | 内存使用的大小，单位为MB。            |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/memory/GLOBAL_SHARED_MEMORY_DETAIL.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/memory/GLOBAL_SHARED_MEMORY_DETAIL.md
new file mode 100644
index 0000000000000000000000000000000000000000..41ffd594eb100e45dc4e33264af20d966c3ef90f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/memory/GLOBAL_SHARED_MEMORY_DETAIL.md
@@ -0,0 +1,22 @@
+---
+title: GLOBAL_SHARED_MEMORY_DETAIL
+summary: GLOBAL_SHARED_MEMORY_DETAIL
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_SHARED_MEMORY_DETAIL
+
+查询MogDB中所有正常节点下的共享内存上下文的使用信息。
+
+**表 1** GLOBAL_SHARED_MEMORY_DETAIL字段
+
+| **名称**    | **类型** | **描述**                         |
+| :---------- | :------- | :------------------------------- |
+| node_name   | name     | 数据库进程名称。                 |
+| contextname | text     | 内存上下文的名称。               |
+| level       | smallint | 内存上下文的级别。               |
+| parent      | text     | 上级内存上下文。                 |
+| totalsize   | bigint   | 共享内存总大小（单位: 字节）。   |
+| freesize    | bigint   | 共享内存剩余大小（单位: 字节）。 |
+| usedsize    | bigint   | 共享内存使用大小（单位: 字节）。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/memory/GS_SHARED_MEMORY_DETAIL.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/memory/GS_SHARED_MEMORY_DETAIL.md
new file mode 100644
index 0000000000000000000000000000000000000000..c6491f314f55447aca6830a4afe387dcc64c362b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/memory/GS_SHARED_MEMORY_DETAIL.md
@@ -0,0 +1,21 @@
+---
+title: GS_SHARED_MEMORY_DETAIL
+summary: GS_SHARED_MEMORY_DETAIL
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_SHARED_MEMORY_DETAIL
+
+查询当前节点所有已产生的共享内存上下文的使用信息。
+
+**表 1** GS_SHARED_MEMORY_DETAIL字段
+
+| **名称**    | **类型** | **描述**                         |
+| :---------- | :------- | :------------------------------- |
+| contextname | text     | 内存上下文的名称。               |
+| level       | smallint | 内存上下文的级别。               |
+| parent      | text     | 上级内存上下文。                 |
+| totalsize   | bigint   | 共享内存总大小（单位：字节）。   |
+| freesize    | bigint   | 共享内存剩余大小（单位：字节）。 |
+| usedsize    | bigint   | 共享内存使用大小（单位：字节）。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/memory/MEMORY_NODE_DETAIL.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/memory/MEMORY_NODE_DETAIL.md
new file mode 100644
index 0000000000000000000000000000000000000000..f5b7a2a5181a99bd0cb73fbdcc9be81872eb7506
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/memory/MEMORY_NODE_DETAIL.md
@@ -0,0 +1,18 @@
+---
+title: MEMORY_NODE_DETAIL
+summary: MEMORY_NODE_DETAIL
+author: Guo Huan
+date: 2021-04-19
+---
+
+# MEMORY_NODE_DETAIL
+
+显示某个数据库节点内存使用情况。
+
+**表 1** MEMORY_NODE_DETAIL字段
+
+| **名称**     | **类型** | **描述**                                                     |
+| :----------- | :------- | :----------------------------------------------------------- |
+| nodename     | text     | 节点名称。                                                   |
+| memorytype   | text     | 内存的名称。<br/>- max_process_memory: MogDB实例所占用的内存大小。<br/>- process_used_memory: 进程所使用的内存大小。<br/>- max_dynamic_memory: 最大动态内存。<br/>- dynamic_used_memory: 已使用的动态内存。<br/>- dynamic_peak_memory: 内存的动态峰值。<br/>- dynamic_used_shrctx: 最大动态共享内存上下文。<br/>- dynamic_peak_shrctx: 共享内存上下文的动态峰值。<br/>- max_shared_memory: 最大共享内存。<br/>- shared_used_memory: 已使用的共享内存。<br/>- max_cstore_memory: 列存所允许使用的最大内存。<br/>- cstore_used_memory: 列存已使用的内存大小。<br/>- max_sctpcomm_memory: sctp通信所允许使用的最大内存。<br/>- sctpcomm_used_memory: sctp通信已使用的内存大小。<br/>- sctpcomm_peak_memory: sctp通信的内存峰值。<br/>- other_used_memory: 其他已使用的内存大小。<br/>- gpu_max_dynamic_memory: GPU最大动态内存。<br/>- gpu_dynamic_used_memory: GPU已使用的动态内存。<br/>- gpu_dynamic_peak_memory: GPU内存的动态峰值。<br/>- pooler_conn_memory: 链接池申请内存计数。<br/>- pooler_freeconn_memory: 链接池空闲连接的内存计数。<br/>- storage_compress_memory: 存储模块压缩使用的内存大小。<br/>- udf_reserved_memory: UDF预留的内存大小。 |
+| memorymbytes | integer  | 内存使用的大小，单位为MB。                                   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_ALL_INDEXES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_ALL_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..9d97dae40fc2a332ffbde7c8ab0a3f1fe2ddd855
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_ALL_INDEXES.md
@@ -0,0 +1,24 @@
+---
+title: GLOBAL_STAT_ALL_INDEXES
+summary: GLOBAL_STAT_ALL_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STAT_ALL_INDEXES
+
+将包含各节点数据库中的每个索引行，显示访问特定索引的统计。
+
+**表 1** GLOBAL_STAT_ALL_INDEXES字段
+
+| **名称**      | **类型** | **描述**                                   |
+| :------------ | :------- | :----------------------------------------- |
+| node_name     | name     | 数据库进程名称。                           |
+| relid         | oid      | 这个索引的表的OID。                        |
+| indexrelid    | oid      | 索引的OID。                                |
+| schemaname    | name     | 索引中模式名。                             |
+| relname       | name     | 索引的表名。                               |
+| indexrelname  | name     | 索引名。                                   |
+| idx_scan      | bigint   | 索引上开始的索引扫描数。                   |
+| idx_tup_read  | bigint   | 通过索引上扫描返回的索引项数。             |
+| idx_tup_fetch | bigint   | 通过使用索引的简单索引扫描抓取的活表行数。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_ALL_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_ALL_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..dc50c700f04fdb52bf4541ceffe67a1528e24ec8
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_ALL_TABLES.md
@@ -0,0 +1,37 @@
+---
+title: GLOBAL_STAT_ALL_TABLES
+summary: GLOBAL_STAT_ALL_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STAT_ALL_TABLES
+
+得到各节点数据中每个表的一行（包括TOAST表）的统计信息。
+
+**表 1** GLOBAL_STAT_ALL_TABLES字段
+
+| **名称**          | **类型**                 | **描述**                                              |
+| :---------------- | :----------------------- | :---------------------------------------------------- |
+| node_name         | name                     | 数据库进程名称。                                      |
+| relid             | oid                      | 表的OID。                                             |
+| schemaname        | name                     | 此表的模式名。                                        |
+| relname           | name                     | 表名。                                                |
+| seq_scan          | bigint                   | 此表发起的顺序扫描数。                                |
+| seq_tup_read      | bigint                   | 顺序扫描抓取的活跃行数。                              |
+| idx_scan          | bigint                   | 此表发起的索引扫描数。                                |
+| idx_tup_fetch     | bigint                   | 索引扫描抓取的活跃行数。                              |
+| n_tup_ins         | bigint                   | 插入行数。                                            |
+| n_tup_upd         | bigint                   | 更新行数。                                            |
+| n_tup_del         | bigint                   | 删除行数。                                            |
+| n_tup_hot_upd     | bigint                   | HOT更新行数（比如没有更新所需的单独索引）。           |
+| n_live_tup        | bigint                   | 估计活跃行数。                                        |
+| n_dead_tup        | bigint                   | 估计死行数。                                          |
+| last_vacuum       | timestamp with time zone | 最后一次此表是手动清理的（不计算VACUUM FULL）的时间。 |
+| last_autovacuum   | timestamp with time zone | 上次被autovacuum守护进程清理的时间。                  |
+| last_analyze      | timestamp with time zone | 上次手动分析这个表的时间。                            |
+| last_autoanalyze  | timestamp with time zone | 上次被autovacuum守护进程分析时间。                    |
+| vacuum_count      | bigint                   | 这个表被手动清理的次数（不计算VACUUM FULL）。         |
+| autovacuum_count  | bigint                   | 这个表被autovacuum清理的次数。                        |
+| analyze_count     | bigint                   | 这个表被手动分析的次数。                              |
+| autoanalyze_count | bigint                   | 这个表被autovacuum守护进程分析的次数。                |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_BAD_BLOCK.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_BAD_BLOCK.md
new file mode 100644
index 0000000000000000000000000000000000000000..1bc2a83ad8458c83a3b5300529bd26c168ed2cc6
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_BAD_BLOCK.md
@@ -0,0 +1,23 @@
+---
+title: GLOBAL_STAT_BAD_BLOCK
+summary: GLOBAL_STAT_BAD_BLOCK
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STAT_BAD_BLOCK
+
+获得各节点的表、索引等文件的读取失败信息。
+
+**表 1** GLOBAL_STAT_BAD_BLOCK字段
+
+| **名称**     | **类型**                 | **描述**               |
+| :----------- | :----------------------- | :--------------------- |
+| node_name    | text                     | 数据库进程名称。       |
+| databaseid   | integer                  | database的oid。        |
+| tablespaceid | integer                  | tablespace的oid。      |
+| relfilenode  | integer                  | relation的file node。  |
+| forknum      | integer                  | fork编号。             |
+| error_count  | integer                  | error的数量。          |
+| first_time   | timestamp with time zone | 坏块第一次出现的时间。 |
+| last_time    | timestamp with time zone | 坏块最后出现的时间。   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_DATABASE.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_DATABASE.md
new file mode 100644
index 0000000000000000000000000000000000000000..6788daa663f8c09e66fce8122d7e5a770791c280
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_DATABASE.md
@@ -0,0 +1,35 @@
+---
+title: GLOBAL_STAT_DATABASE
+summary: GLOBAL_STAT_DATABASE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STAT_DATABASE
+
+视图将包含MogDB中各节点的每个数据库的每一行，显示数据库统计。
+
+**表 1** GLOBAL_STAT_DATABASE字段
+
+| **名称**       | **类型**                 | **描述**                                                                                                                     |
+| :------------- | :----------------------- | :--------------------------------------------------------------------------------------------------------------------------- |
+| node_name      | name                     | 数据库进程名称。                                                                                                             |
+| datid          | oid                      | 数据库的OID。                                                                                                                |
+| datname        | name                     | 这个数据库的名称。                                                                                                           |
+| numbackends    | integer                  | 当前连接到该数据库的后端数。这是在返回一个反映目前状态值的视图中唯一的列；自上次重置所有其他列返回累积值。                   |
+| xact_commit    | bigint                   | 此数据库中已经提交的事务数。                                                                                                 |
+| xact_rollback  | bigint                   | 此数据库中已经回滚的事务数。                                                                                                 |
+| blks_read      | bigint                   | 在这个数据库中读取的磁盘块的数量。                                                                                           |
+| blks_hit       | bigint                   | 高速缓存中已经发现的磁盘块的次数，这样读取是不必要的（这只包括数据库内核缓冲区高速缓存，没有操作系统的文件系统缓存）。       |
+| tup_returned   | bigint                   | 通过数据库查询返回的行数。                                                                                                   |
+| tup_fetched    | bigint                   | 通过数据库查询抓取的行数。                                                                                                   |
+| tup_inserted   | bigint                   | 通过数据库查询插入的行数。                                                                                                   |
+| tup_updated    | bigint                   | 通过数据库查询更新的行数。                                                                                                   |
+| tup_deleted    | bigint                   | 通过数据库查询删除的行数。                                                                                                   |
+| conflicts      | bigint                   | 由于数据库恢复冲突取消的查询数量（只在备用服务器发生的冲突）。请参见STAT_DATABASE_CONFLICTS获取更多信息。                    |
+| temp_files     | bigint                   | 通过数据库查询创建的临时文件数量。计算所有临时文件，不论为什么创建临时文件（比如排序或者哈希），而且不管log_temp_files设置。 |
+| temp_bytes     | bigint                   | 通过数据库查询写入临时文件的数据总量。计算所有临时文件，不论为什么创建临时文件，而且不管log_temp_files设置。                 |
+| deadlocks      | bigint                   | 在该数据库中检索的死锁数。                                                                                                   |
+| blk_read_time  | double precision         | 通过数据库后端读取数据文件块花费的时间，以毫秒计算。                                                                         |
+| blk_write_time | double precision         | 通过数据库后端写入数据文件块花费的时间，以毫秒计算。                                                                         |
+| stats_reset    | timestamp with time zone | 重置当前状态统计的时间。                                                                                                     |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_DATABASE_CONFLICTS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_DATABASE_CONFLICTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..874a2aaf58a2cedbe9abf41b8f535ab5a49dd781
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_DATABASE_CONFLICTS.md
@@ -0,0 +1,23 @@
+---
+title: GLOBAL_STAT_DATABASE_CONFLICTS
+summary: GLOBAL_STAT_DATABASE_CONFLICTS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STAT_DATABASE_CONFLICTS
+
+显示每个节点的数据库冲突状态的统计信息。
+
+**表 1** GLOBAL_STAT_DATABASE_CONFLICTS字段
+
+| 名称             | 类型   | 描述                 |
+| :--------------- | :----- | :------------------- |
+| node_name        | name   | 数据库进程名称。     |
+| datid            | oid    | 数据库标识。         |
+| datname          | name   | 数据库名称。         |
+| confl_tablespace | bigint | 冲突的表空间的数目。 |
+| confl_lock       | bigint | 冲突的锁数目。       |
+| confl_snapshot   | bigint | 冲突的快照数目。     |
+| confl_bufferpin  | bigint | 冲突的缓冲区数目。   |
+| confl_deadlock   | bigint | 冲突的死锁数目。     |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_SYS_INDEXES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_SYS_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..6c9c3fc1cd8eb178551d7079ac4eb721e7a948a5
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_SYS_INDEXES.md
@@ -0,0 +1,24 @@
+---
+title: GLOBAL_STAT_SYS_INDEXES
+summary: GLOBAL_STAT_SYS_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STAT_SYS_INDEXES
+
+得到各节点pg_catalog、information_schema以及pg_toast模式中所有系统表的索引状态信息。
+
+**表 1** GLOBAL_STAT_SYS_INDEXES字段
+
+| **名称**      | **类型** | **描述**                                   |
+| :------------ | :------- | :----------------------------------------- |
+| node_name     | name     | 数据库进程名称。                           |
+| relid         | oid      | 这个索引的表的OID。                        |
+| indexrelid    | oid      | 索引的OID。                                |
+| schemaname    | name     | 索引中模式名。                             |
+| relname       | name     | 索引的表名。                               |
+| indexrelname  | name     | 索引名。                                   |
+| idx_scan      | bigint   | 索引上开始的索引扫描数。                   |
+| idx_tup_read  | bigint   | 通过索引上扫描返回的索引项数。             |
+| idx_tup_fetch | bigint   | 通过使用索引的简单索引扫描抓取的活表行数。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_SYS_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_SYS_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..81895a6b888d131370da3ec92154d2337cf3ea38
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_SYS_TABLES.md
@@ -0,0 +1,37 @@
+---
+title: GLOBAL_STAT_SYS_TABLES
+summary: GLOBAL_STAT_SYS_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STAT_SYS_TABLES
+
+得到各节点pg_catalog、information_schema模式的所有命名空间中系统表的统计信息。
+
+**表 1** GLOBAL_STAT_SYS_TABLES字段
+
+| **名称**          | **类型**                 | **描述**                                            |
+| :---------------- | :----------------------- | :-------------------------------------------------- |
+| node_name         | name                     | 节点名称。                                          |
+| relid             | oid                      | 表的OID。                                           |
+| schemaname        | name                     | 此表的模式名。                                      |
+| relname           | name                     | 表名。                                              |
+| seq_scan          | bigint                   | 此表发起的顺序扫描数。                              |
+| seq_tup_read      | bigint                   | 顺序扫描抓取的活跃行数。                            |
+| idx_scan          | bigint                   | 此表发起的索引扫描数。                              |
+| idx_tup_fetch     | bigint                   | 索引扫描抓取的活跃行数。                            |
+| n_tup_ins         | bigint                   | 插入行数。                                          |
+| n_tup_upd         | bigint                   | 更新行数。                                          |
+| n_tup_del         | bigint                   | 删除行数。                                          |
+| n_tup_hot_upd     | bigint                   | HOT更新行数（比如没有更新所需的单独索引）。         |
+| n_live_tup        | bigint                   | 估计活跃行数。                                      |
+| n_dead_tup        | bigint                   | 估计死行数。                                        |
+| last_vacuum       | timestamp with time zone | 最后一次此表是手动清理的（不计算VACUUM FULL）时间。 |
+| last_autovacuum   | timestamp with time zone | 上次被autovacuum守护进程清理的时间。                |
+| last_analyze      | timestamp with time zone | 上次手动分析这个表的时间。                          |
+| last_autoanalyze  | timestamp with time zone | 上次被autovacuum守护进程分析的时间。                |
+| vacuum_count      | bigint                   | 这个表被手动清理的次数（不计算VACUUM FULL）。       |
+| autovacuum_count  | bigint                   | 这个表被autovacuum清理的次数。                      |
+| analyze_count     | bigint                   | 这个表被手动分析的次数。                            |
+| autoanalyze_count | bigint                   | 这个表被autovacuum守护进程分析的次数。              |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_USER_FUNCTIONS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_USER_FUNCTIONS.md
new file mode 100644
index 0000000000000000000000000000000000000000..44b39cbd5289c21dfff2b062d185b1b2e32df62c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_USER_FUNCTIONS.md
@@ -0,0 +1,22 @@
+---
+title: GLOBAL_STAT_USER_FUNCTIONS
+summary: GLOBAL_STAT_USER_FUNCTIONS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STAT_USER_FUNCTIONS
+
+提供MogDB中各个节点的用户所创建的函数的状态的统计信息。
+
+**表 1** GLOBAL_STAT_USER_FUNCTIONS字段
+
+| **名称**   | **类型**         | **描述**                                                             |
+| :--------- | :--------------- | :------------------------------------------------------------------- |
+| node_name  | name             | 数据库进程名称。                                                     |
+| funcid     | oid              | 函数的id。                                                           |
+| schemaname | name             | 此函数所在模式的名称。                                               |
+| funcname   | name             | 函数名称。                                                           |
+| calls      | bigint           | 该函数被调用的次数。                                                 |
+| total_time | double precision | 此函数及其调用的所有其他函数所花费的总时间（以毫秒为单位）。         |
+| self_time  | double precision | 在此函数本身中花费的总时间（不包括它调用的其他函数），以毫秒为单位。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_USER_INDEXES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_USER_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..7557e570d181841b1de4aca5c920daeb82673b8c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_USER_INDEXES.md
@@ -0,0 +1,24 @@
+---
+title: GLOBAL_STAT_USER_INDEXES
+summary: GLOBAL_STAT_USER_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STAT_USER_INDEXES
+
+得到各节点数据库中用户自定义普通表的索引状态信息。
+
+**表 1** GLOBAL_STAT_USER_INDEXES字段
+
+| **名称**      | **类型** | **描述**                                   |
+| :------------ | :------- | :----------------------------------------- |
+| node_name     | name     | 数据库进程名称。                           |
+| relid         | oid      | 这个索引的表的OID。                        |
+| indexrelid    | oid      | 索引的OID。                                |
+| schemaname    | name     | 索引中模式名。                             |
+| relname       | name     | 索引的表名。                               |
+| indexrelname  | name     | 索引名。                                   |
+| idx_scan      | bigint   | 索引上开始的索引扫描数。                   |
+| idx_tup_read  | bigint   | 通过索引上扫描返回的索引项数。             |
+| idx_tup_fetch | bigint   | 通过使用索引的简单索引扫描抓取的活表行数。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_USER_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_USER_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..6f067787db19673a7c241b3f2167446eea01e602
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_USER_TABLES.md
@@ -0,0 +1,37 @@
+---
+title: GLOBAL_STAT_USER_TABLES
+summary: GLOBAL_STAT_USER_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STAT_USER_TABLES
+
+得到各节点所有命名空间中用户自定义普通表的状态信息。
+
+**表 1** GLOBAL_STAT_USER_TABLES字段
+
+| **名称**          | **类型**                 | **描述**                                            |
+| :---------------- | :----------------------- | :-------------------------------------------------- |
+| node_name         | name                     | 数据库进程名称。                                    |
+| relid             | oid                      | 表的OID。                                           |
+| schemaname        | name                     | 此表的模式名。                                      |
+| relname           | name                     | 表名。                                              |
+| seq_scan          | bigint                   | 此表发起的顺序扫描数。                              |
+| seq_tup_read      | bigint                   | 顺序扫描抓取的活跃行数。                            |
+| idx_scan          | bigint                   | 此表发起的索引扫描数。                              |
+| idx_tup_fetch     | bigint                   | 索引扫描抓取的活跃行数。                            |
+| n_tup_ins         | bigint                   | 插入行数。                                          |
+| n_tup_upd         | bigint                   | 更新行数。                                          |
+| n_tup_del         | bigint                   | 删除行数。                                          |
+| n_tup_hot_upd     | bigint                   | HOT更新行数（即没有更新所需的单独索引）。           |
+| n_live_tup        | bigint                   | 估计活跃行数。                                      |
+| n_dead_tup        | bigint                   | 估计死行数。                                        |
+| last_vacuum       | timestamp with time zone | 最后一次此表是手动清理的（不计算VACUUM FULL）时间。 |
+| last_autovacuum   | timestamp with time zone | 上次被autovacuum守护进程清理的时间。                |
+| last_analyze      | timestamp with time zone | 上次手动分析这个表的时间。                          |
+| last_autoanalyze  | timestamp with time zone | 上次被autovacuum守护进程分析的时间。                |
+| vacuum_count      | bigint                   | 这个表被手动清理的次数（不计算VACUUM FULL）。       |
+| autovacuum_count  | bigint                   | 这个表被autovacuum清理的次数。                      |
+| analyze_count     | bigint                   | 这个表被手动分析的次数。                            |
+| autoanalyze_count | bigint                   | 这个表被autovacuum守护进程分析的次数。              |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_ALL_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_ALL_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..56ce304a8c90a7287f5c3c0da6b76a30d16de971
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_ALL_TABLES.md
@@ -0,0 +1,27 @@
+---
+title: GLOBAL_STAT_XACT_ALL_TABLES
+summary: GLOBAL_STAT_XACT_ALL_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STAT_XACT_ALL_TABLES
+
+显示各节点的命名空间中所有普通表和toast表的事务状态信息。
+
+**表 1** GLOBAL_STAT_XACT_ALL_TABLES字段
+
+| **名称**      | **类型** | **描述**                                    |
+| :------------ | :------- | :------------------------------------------ |
+| node_name     | name     | 数据库进程名称。                            |
+| relid         | oid      | 表的OID。                                   |
+| schemaname    | name     | 此表的模式名。                              |
+| relname       | name     | 表名。                                      |
+| seq_scan      | bigint   | 此表发起的顺序扫描数。                      |
+| seq_tup_read  | bigint   | 顺序扫描抓取的活跃行数。                    |
+| idx_scan      | bigint   | 此表发起的索引扫描数。                      |
+| idx_tup_fetch | bigint   | 索引扫描抓取的活跃行数。                    |
+| n_tup_ins     | bigint   | 插入行数。                                  |
+| n_tup_upd     | bigint   | 更新行数。                                  |
+| n_tup_del     | bigint   | 删除行数。                                  |
+| n_tup_hot_upd | bigint   | HOT更新行数（比如没有更新所需的单独索引）。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_SYS_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_SYS_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..ee19ffe46bd47ba045b09a42630cc52f59bdb3cc
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_SYS_TABLES.md
@@ -0,0 +1,27 @@
+---
+title: GLOBAL_STAT_XACT_SYS_TABLES
+summary: GLOBAL_STAT_XACT_SYS_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STAT_XACT_SYS_TABLES
+
+显示各节点命名空间中系统表的事务状态信息。
+
+**表 1** GLOBAL_STAT_XACT_SYS_TABLES字段
+
+| **名称**      | **类型** | **描述**                                    |
+| :------------ | :------- | :------------------------------------------ |
+| node_name     | name     | 节点名称。                                  |
+| relid         | oid      | 表的OID。                                   |
+| schemaname    | name     | 此表的模式名。                              |
+| relname       | name     | 表名。                                      |
+| seq_scan      | bigint   | 此表发起的顺序扫描数。                      |
+| seq_tup_read  | bigint   | 顺序扫描抓取的活跃行数。                    |
+| idx_scan      | bigint   | 此表发起的索引扫描数。                      |
+| idx_tup_fetch | bigint   | 索引扫描抓取的活跃行数。                    |
+| n_tup_ins     | bigint   | 插入行数。                                  |
+| n_tup_upd     | bigint   | 更新行数。                                  |
+| n_tup_del     | bigint   | 删除行数。                                  |
+| n_tup_hot_upd | bigint   | HOT更新行数（比如没有更新所需的单独索引）。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_USER_FUNCTIONS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_USER_FUNCTIONS.md
new file mode 100644
index 0000000000000000000000000000000000000000..197612fb340d2f5732be57d8ace86030954d4508
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_USER_FUNCTIONS.md
@@ -0,0 +1,22 @@
+---
+title: GLOBAL_STAT_XACT_USER_FUNCTIONS
+summary: GLOBAL_STAT_XACT_USER_FUNCTIONS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STAT_XACT_USER_FUNCTIONS
+
+视图包含各节点本事务内函数执行的统计信息。
+
+**表 1** GLOBAL_STAT_XACT_USER_FUNCTIONS字段
+
+| **名称**   | **类型**         | **描述**                                               |
+| :--------- | :--------------- | :----------------------------------------------------- |
+| node_name  | name             | 节点名称。                                             |
+| funcid     | oid              | 函数标识。                                             |
+| schemaname | name             | 模式的名称。                                           |
+| funcname   | name             | 函数名称。                                             |
+| calls      | bigint           | 函数被调用的次数。                                     |
+| total_time | double precision | 此函数及其调用的所有其他函数所花费的总时间。           |
+| self_time  | double precision | 在此函数本身中花费的总时间（不包括它调用的其他函数）。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_USER_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_USER_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..4bce746a14a31c67d867df7b71cbfbdbf709dba7
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_USER_TABLES.md
@@ -0,0 +1,27 @@
+---
+title: GLOBAL_STAT_XACT_USER_TABLES
+summary: GLOBAL_STAT_XACT_USER_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STAT_XACT_USER_TABLES
+
+显示各节点命名空间中用户表的事务状态信息。
+
+**表 1** GLOBAL_STAT_XACT_USER_TABLES字段
+
+| **名称**      | **类型** | **描述**                                    |
+| :------------ | :------- | :------------------------------------------ |
+| node_name     | name     | 数据库进程名称。                            |
+| relid         | oid      | 表的OID。                                   |
+| schemaname    | name     | 此表的模式名。                              |
+| relname       | name     | 表名。                                      |
+| seq_scan      | bigint   | 此表发起的顺序扫描数。                      |
+| seq_tup_read  | bigint   | 顺序扫描抓取的活跃行数。                    |
+| idx_scan      | bigint   | 此表发起的索引扫描数。                      |
+| idx_tup_fetch | bigint   | 索引扫描抓取的活跃行数。                    |
+| n_tup_ins     | bigint   | 插入行数。                                  |
+| n_tup_upd     | bigint   | 更新行数。                                  |
+| n_tup_del     | bigint   | 删除行数。                                  |
+| n_tup_hot_upd | bigint   | HOT更新行数（比如没有更新所需的单独索引）。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_ALL_INDEXES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_ALL_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..445e175fd35c1063bf9b809c7ae79910ae9bdf7e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_ALL_INDEXES.md
@@ -0,0 +1,23 @@
+---
+title: STAT_ALL_INDEXES
+summary: STAT_ALL_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STAT_ALL_INDEXES
+
+将包含本节点数据库中的每个索引行，显示访问特定索引的统计。
+
+**表 1** STAT_ALL_INDEXES字段
+
+| **名称**      | **类型** | **描述**                                   |
+| :------------ | :------- | :----------------------------------------- |
+| relid         | oid      | 这个索引的表的OID。                        |
+| indexrelid    | oid      | 索引的OID。                                |
+| schemaname    | name     | 索引中模式名。                             |
+| relname       | name     | 索引的表名。                               |
+| indexrelname  | name     | 索引名。                                   |
+| idx_scan      | bigint   | 索引上开始的索引扫描数。                   |
+| idx_tup_read  | bigint   | 通过索引上扫描返回的索引项数。             |
+| idx_tup_fetch | bigint   | 通过使用索引的简单索引扫描抓取的活表行数。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_ALL_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_ALL_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..78d06264972338a203d1db193411b560aae1d9dd
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_ALL_TABLES.md
@@ -0,0 +1,36 @@
+---
+title: STAT_ALL_TABLES
+summary: STAT_ALL_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STAT_ALL_TABLES
+
+本节点内数据库中每个表（包括TOAST表）的一行的统计信息。
+
+**表 1** STAT_ALL_TABLES字段
+
+| **名称**          | **类型**                 | **描述**                                              |
+| :---------------- | :----------------------- | :---------------------------------------------------- |
+| relid             | oid                      | 表的OID。                                             |
+| schemaname        | name                     | 该表的模式名。                                        |
+| relname           | name                     | 表名。                                                |
+| seq_scan          | bigint                   | 该表发起的顺序扫描数。                                |
+| seq_tup_read      | bigint                   | 顺序扫描抓取的活跃行数。                              |
+| idx_scan          | bigint                   | 该表发起的索引扫描数。                                |
+| idx_tup_fetch     | bigint                   | 索引扫描抓取的活跃行数。                              |
+| n_tup_ins         | bigint                   | 插入行数。                                            |
+| n_tup_upd         | bigint                   | 更新行数。                                            |
+| n_tup_del         | bigint                   | 删除行数。                                            |
+| n_tup_hot_upd     | bigint                   | HOT更新行数（比如没有更新所需的单独索引）。           |
+| n_live_tup        | bigint                   | 估计活跃行数。                                        |
+| n_dead_tup        | bigint                   | 估计死行数。                                          |
+| last_vacuum       | timestamp with time zone | 最后一次该表是手动清理的（不计算VACUUM FULL）的时间。 |
+| last_autovacuum   | timestamp with time zone | 上次被autovacuum守护进程清理的时间。                  |
+| last_analyze      | timestamp with time zone | 上次手动分析该表的时间。                              |
+| last_autoanalyze  | timestamp with time zone | 上次被autovacuum守护进程分析时间。                    |
+| vacuum_count      | bigint                   | 该表被手动清理的次数（不计算VACUUM FULL）。           |
+| autovacuum_count  | bigint                   | 该表被autovacuum清理的次数。                          |
+| analyze_count     | bigint                   | 该表被手动分析的次数。                                |
+| autoanalyze_count | bigint                   | 该表被autovacuum守护进程分析的次数。                  |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_BAD_BLOCK.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_BAD_BLOCK.md
new file mode 100644
index 0000000000000000000000000000000000000000..7b7313748e3215d10f019f73d2c62e6ba28d249a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_BAD_BLOCK.md
@@ -0,0 +1,24 @@
+---
+title: STAT_BAD_BLOCK
+summary: STAT_BAD_BLOCK
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STAT_BAD_BLOCK
+
+获得当前节点表、索引等文件的读取失败信息。
+
+**表 1** STAT_BAD_BLOCK字段
+
+| **名称**     | **类型**                 | **描述**               |
+| :----------- | :----------------------- | :--------------------- |
+| nodename     | text                     | 数据库进程名称。       |
+| databaseid   | integer                  | database的oid。        |
+| tablespaceid | integer                  | tablespace的oid。      |
+| relfilenode  | integer                  | relation的file node。  |
+| bucketid     | smallint                 | 一致性hash bucket ID。 |
+| forknum      | integer                  | fork编号。             |
+| error_count  | integer                  | error的数量。          |
+| first_time   | timestamp with time zone | 坏块第一次出现的时间。 |
+| last_time    | timestamp with time zone | 坏块最后出现的时间。   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_DATABASE.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_DATABASE.md
new file mode 100644
index 0000000000000000000000000000000000000000..abcccad89fe47f0ffc9f0e404ea5368dd7a61c76
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_DATABASE.md
@@ -0,0 +1,34 @@
+---
+title: STAT_DATABASE
+summary: STAT_DATABASE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STAT_DATABASE
+
+视图将包含本节点中每个数据库的统计信息。
+
+**表 1** STAT_DATABASE字段
+
+| **名称**       | **类型**                 | **描述**                                                                                                                     |
+| :------------- | :----------------------- | :--------------------------------------------------------------------------------------------------------------------------- |
+| datid          | oid                      | 数据库的OID。                                                                                                                |
+| datname        | name                     | 此数据库的名称。                                                                                                             |
+| numbackends    | integer                  | 当前连接到该数据库的后端数。这是在返回一个反映目前状态值的视图中唯一的列；自上次重置所有其他列返回累积值。                   |
+| xact_commit    | bigint                   | 此数据库中已经提交的事务数。                                                                                                 |
+| xact_rollback  | bigint                   | 此数据库中已经回滚的事务数。                                                                                                 |
+| blks_read      | bigint                   | 在这个数据库中读取的磁盘块的数量。                                                                                           |
+| blks_hit       | bigint                   | 高速缓存中已经发现的磁盘块的次数，这样读取是不必要的（这只包括PostgreSQL缓冲区高速缓存，没有操作系统的文件系统缓存）。       |
+| tup_returned   | bigint                   | 通过数据库查询返回的行数。                                                                                                   |
+| tup_fetched    | bigint                   | 通过数据库查询抓取的行数。                                                                                                   |
+| tup_inserted   | bigint                   | 通过数据库查询插入的行数。                                                                                                   |
+| tup_updated    | bigint                   | 通过数据库查询更新的行数。                                                                                                   |
+| tup_deleted    | bigint                   | 通过数据库查询删除的行数。                                                                                                   |
+| conflicts      | bigint                   | 由于数据库恢复冲突取消的查询数量（只在备用服务器发生的冲突）。请参见STAT_DATABASE_CONFLICTS获取更多信息。                    |
+| temp_files     | bigint                   | 通过数据库查询创建的临时文件数量。计算所有临时文件，不论为什么创建临时文件（比如排序或者哈希），而且不管log_temp_files设置。 |
+| temp_bytes     | bigint                   | 通过数据库查询写入临时文件的数据总量。计算所有临时文件，不论为什么创建临时文件，而且不管log_temp_files设置。                 |
+| deadlocks      | bigint                   | 在该数据库中检索的死锁数。                                                                                                   |
+| blk_read_time  | double precision         | 通过数据库后端读取数据文件块花费的时间，以毫秒计算。                                                                         |
+| blk_write_time | double precision         | 通过数据库后端写入数据文件块花费的时间，以毫秒计算。                                                                         |
+| stats_reset    | timestamp with time zone | 重置当前状态统计的时间。                                                                                                     |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_DATABASE_CONFLICTS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_DATABASE_CONFLICTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..605c90d5f599e5e46e07e4f26fa988f0c0dac6ec
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_DATABASE_CONFLICTS.md
@@ -0,0 +1,22 @@
+---
+title: STAT_DATABASE_CONFLICTS
+summary: STAT_DATABASE_CONFLICTS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STAT_DATABASE_CONFLICTS
+
+显示当前节点数据库冲突状态的统计信息。
+
+**表 1** STAT_DATABASE_CONFLICTS字段
+
+| **名称**         | **类型** | **描述**             |
+| :--------------- | :------- | :------------------- |
+| datid            | oid      | 数据库标识。         |
+| datname          | name     | 数据库名称。         |
+| confl_tablespace | bigint   | 冲突的表空间的数目。 |
+| confl_lock       | bigint   | 冲突的锁数目。       |
+| confl_snapshot   | bigint   | 冲突的快照数目。     |
+| confl_bufferpin  | bigint   | 冲突的缓冲区数目。   |
+| confl_deadlock   | bigint   | 冲突的死锁数目。     |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_SYS_INDEXES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_SYS_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..440b52e820e287a426b7a218f1bae4854a2f47de
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_SYS_INDEXES.md
@@ -0,0 +1,23 @@
+---
+title: STAT_SYS_INDEXES
+summary: STAT_SYS_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STAT_SYS_INDEXES
+
+显示pg_catalog、information_schema以及pg_toast模式中所有系统表的索引状态信息。
+
+**表 1** STAT_SYS_INDEXES字段
+
+| **名称**      | **类型** | **描述**                                   |
+| :------------ | :------- | :----------------------------------------- |
+| relid         | oid      | 此索引的表的OID。                          |
+| indexrelid    | oid      | 索引的OID。                                |
+| schemaname    | name     | 索引的模式名。                             |
+| relname       | name     | 索引的表名。                               |
+| indexrelname  | name     | 索引名。                                   |
+| idx_scan      | bigint   | 索引上开始的索引扫描数。                   |
+| idx_tup_read  | bigint   | 通过索引上扫描返回的索引项数。             |
+| idx_tup_fetch | bigint   | 通过使用索引的简单索引扫描抓取的活表行数。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_SYS_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_SYS_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..111f576985cc6e42d556997d2028a9bca3568a59
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_SYS_TABLES.md
@@ -0,0 +1,36 @@
+---
+title: STAT_SYS_TABLES
+summary: STAT_SYS_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STAT_SYS_TABLES
+
+显示pg_catalog、information_schema模式的所有命名空间中系统表的统计信息。
+
+**表 1** STAT_SYS_TABLES字段
+
+| **名称**          | **类型**                 | **描述**                                            |
+| :---------------- | :----------------------- | :-------------------------------------------------- |
+| relid             | oid                      | 表的OID。                                           |
+| schemaname        | name                     | 该表的模式名。                                      |
+| relname           | name                     | 表名。                                              |
+| seq_scan          | bigint                   | 该表发起的顺序扫描数。                              |
+| seq_tup_read      | bigint                   | 顺序扫描抓取的活跃行数。                            |
+| idx_scan          | bigint                   | 该表发起的索引扫描数。                              |
+| idx_tup_fetch     | bigint                   | 索引扫描抓取的活跃行数。                            |
+| n_tup_ins         | bigint                   | 插入行数。                                          |
+| n_tup_upd         | bigint                   | 更新行数。                                          |
+| n_tup_del         | bigint                   | 删除行数。                                          |
+| n_tup_hot_upd     | bigint                   | HOT更新行数（比如没有更新所需的单独索引）。         |
+| n_live_tup        | bigint                   | 估计活跃行数。                                      |
+| n_dead_tup        | bigint                   | 估计死行数。                                        |
+| last_vacuum       | timestamp with time zone | 最后一次该表是手动清理的（不计算VACUUM FULL）时间。 |
+| last_autovacuum   | timestamp with time zone | 上次被autovacuum守护进程清理的时间。                |
+| last_analyze      | timestamp with time zone | 上次手动分析该表的时间。                            |
+| last_autoanalyze  | timestamp with time zone | 上次被autovacuum守护进程分析的时间。                |
+| vacuum_count      | bigint                   | 这个表被手动清理的次数（不计算VACUUM FULL）。       |
+| autovacuum_count  | bigint                   | 该表被autovacuum清理的次数。                        |
+| analyze_count     | bigint                   | 该表被手动分析的次数。                              |
+| autoanalyze_count | bigint                   | 该表被autovacuum守护进程分析的次数。                |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_USER_FUNCTIONS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_USER_FUNCTIONS.md
new file mode 100644
index 0000000000000000000000000000000000000000..70a6b8872748119f03259e563717df26d1d6aef4
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_USER_FUNCTIONS.md
@@ -0,0 +1,21 @@
+---
+title: STAT_USER_FUNCTIONS
+summary: STAT_USER_FUNCTIONS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STAT_USER_FUNCTIONS
+
+STAT_USER_FUNCTIONS视图显示命名空间中用户自定义函数（函数语言为非内部语言）的状态信息。
+
+**表 1** STAT_USER_FUNCTIONS字段
+
+| 名称       | 类型             | 描述                                                         |
+| :--------- | :--------------- | :----------------------------------------------------------- |
+| funcid     | oid              | 函数标识。                                                   |
+| schemaname | name             | schema的名称。                                               |
+| funcname   | name             | 用户自定义函数的名称。                                       |
+| calls      | bigint           | 函数被调用的次数。                                           |
+| total_time | double precision | 调用此函数花费的总时间，包含调用其它函数的时间（单位: 毫秒）。 |
+| self_time  | double precision | 调用此函数自己花费的时间，不包含调用其它函数的时间（单位: 毫秒）。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_USER_INDEXES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_USER_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..c18128e0d031a39e02a4e479ee6753842b006d12
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_USER_INDEXES.md
@@ -0,0 +1,23 @@
+---
+title: STAT_USER_INDEXES
+summary: STAT_USER_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STAT_USER_INDEXES
+
+显示数据库中用户自定义普通表的索引状态信息。
+
+**表 1** STAT_USER_INDEXES字段
+
+| **名称**      | **类型** | **描述**                                   |
+| :------------ | :------- | :----------------------------------------- |
+| relid         | oid      | 此索引的表的OID。                          |
+| indexrelid    | oid      | 索引的OID。                                |
+| schemaname    | name     | 索引的模式名。                             |
+| relname       | name     | 索引的表名。                               |
+| indexrelname  | name     | 索引名。                                   |
+| idx_scan      | bigint   | 索引上开始的索引扫描数。                   |
+| idx_tup_read  | bigint   | 通过索引上扫描返回的索引项数。             |
+| idx_tup_fetch | bigint   | 通过使用索引的简单索引扫描抓取的活表行数。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_USER_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_USER_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..134be903b4bfc1acfc4bc81a207995c16558a08a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_USER_TABLES.md
@@ -0,0 +1,36 @@
+---
+title: STAT_USER_TABLES
+summary: STAT_USER_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STAT_USER_TABLES
+
+显示当前节点所有命名空间中用户自定义普通表的状态信息。
+
+**表 1** STAT_USER_TABLES字段
+
+| **名称**          | **类型**                 | **描述**                                            |
+| :---------------- | :----------------------- | :-------------------------------------------------- |
+| relid             | oid                      | 表的OID。                                           |
+| schemaname        | name                     | 该表的模式名。                                      |
+| relname           | name                     | 表名。                                              |
+| seq_scan          | bigint                   | 该表发起的顺序扫描数。                              |
+| seq_tup_read      | bigint                   | 顺序扫描抓取的活跃行数。                            |
+| idx_scan          | bigint                   | 该表发起的索引扫描数。                              |
+| idx_tup_fetch     | bigint                   | 索引扫描抓取的活跃行数。                            |
+| n_tup_ins         | bigint                   | 插入行数。                                          |
+| n_tup_upd         | bigint                   | 更新行数。                                          |
+| n_tup_del         | bigint                   | 删除行数。                                          |
+| n_tup_hot_upd     | bigint                   | HOT更新行数（即没有更新所需的单独索引）。           |
+| n_live_tup        | bigint                   | 估计活跃行数。                                      |
+| n_dead_tup        | bigint                   | 估计死行数。                                        |
+| last_vacuum       | timestamp with time zone | 最后一次该表是手动清理的（不计算VACUUM FULL）时间。 |
+| last_autovacuum   | timestamp with time zone | 上次被autovacuum守护进程清理的时间。                |
+| last_analyze      | timestamp with time zone | 上次手动分析该表的时间。                            |
+| last_autoanalyze  | timestamp with time zone | 上次被autovacuum守护进程分析的时间。                |
+| vacuum_count      | bigint                   | 该表被手动清理的次数（不计算VACUUM FULL）。         |
+| autovacuum_count  | bigint                   | 该表被autovacuum清理的次数。                        |
+| analyze_count     | bigint                   | 该表被手动分析的次数。                              |
+| autoanalyze_count | bigint                   | 该表被autovacuum守护进程分析的次数。                |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_XACT_ALL_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_XACT_ALL_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..9b4c73e3ad587994ec47bc07c8a19413c2d43f14
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_XACT_ALL_TABLES.md
@@ -0,0 +1,26 @@
+---
+title: STAT_XACT_ALL_TABLES
+summary: STAT_XACT_ALL_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STAT_XACT_ALL_TABLES
+
+显示命名空间中所有普通表和toast表的事务状态信息。
+
+**表 1** STAT_XACT_ALL_TABLES字段
+
+| 名称          | 类型   | 描述                                        |
+| :------------ | :----- | :------------------------------------------ |
+| relid         | oid    | 表的OID。                                   |
+| schemaname    | name   | 该表的模式名。                              |
+| relname       | name   | 表名。                                      |
+| seq_scan      | bigint | 该表发起的顺序扫描数。                      |
+| seq_tup_read  | bigint | 顺序扫描抓取的活跃行数。                    |
+| idx_scan      | bigint | 该表发起的索引扫描数。                      |
+| idx_tup_fetch | bigint | 索引扫描抓取的活跃行数。                    |
+| n_tup_ins     | bigint | 插入行数。                                  |
+| n_tup_upd     | bigint | 更新行数。                                  |
+| n_tup_del     | bigint | 删除行数。                                  |
+| n_tup_hot_upd | bigint | HOT更新行数（比如没有更新所需的单独索引）。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_XACT_SYS_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_XACT_SYS_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..7ca1fddf084b76aba35342fdb38632e8fca8ca03
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_XACT_SYS_TABLES.md
@@ -0,0 +1,26 @@
+---
+title: STAT_XACT_SYS_TABLES
+summary: STAT_XACT_SYS_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STAT_XACT_SYS_TABLES
+
+显示当前节点命名空间中系统表的事务状态信息。
+
+**表 1** STAT_XACT_SYS_TABLES字段
+
+| **名称**      | **类型** | **描述**                                    |
+| :------------ | :------- | :------------------------------------------ |
+| relid         | oid      | 表的OID。                                   |
+| schemaname    | name     | 该表的模式名。                              |
+| relname       | name     | 表名。                                      |
+| seq_scan      | bigint   | 该表发起的顺序扫描数。                      |
+| seq_tup_read  | bigint   | 顺序扫描抓取的活跃行数。                    |
+| idx_scan      | bigint   | 该表发起的索引扫描数。                      |
+| idx_tup_fetch | bigint   | 索引扫描抓取的活跃行数。                    |
+| n_tup_ins     | bigint   | 插入行数。                                  |
+| n_tup_upd     | bigint   | 更新行数。                                  |
+| n_tup_del     | bigint   | 删除行数。                                  |
+| n_tup_hot_upd | bigint   | HOT更新行数（比如没有更新所需的单独索引）。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_XACT_USER_FUNCTIONS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_XACT_USER_FUNCTIONS.md
new file mode 100644
index 0000000000000000000000000000000000000000..69611f1bd2e84becc07b40172da66f396d2c99f1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_XACT_USER_FUNCTIONS.md
@@ -0,0 +1,21 @@
+---
+title: STAT_XACT_USER_FUNCTIONS
+summary: STAT_XACT_USER_FUNCTIONS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STAT_XACT_USER_FUNCTIONS
+
+视图包含当前节点本事务内函数执行的统计信息。
+
+**表 1** STAT_XACT_USER_FUNCTIONS字段
+
+| **名称**   | **类型**         | **描述**                     |
+| :--------- | :--------------- | :--------------------------- |
+| funcid     | oid              | 函数标识。                   |
+| schemaname | name             | 模式的名称。                 |
+| funcname   | name             | 函数名称。                   |
+| calls      | bigint           | 函数被调用的次数。           |
+| total_time | double precision | 函数的总执行时长。           |
+| self_time  | double precision | 当前线程调用函数的总的时长。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_XACT_USER_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_XACT_USER_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..fef9af41c32112cc069d06147d55e96f7ad477f1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/STAT_XACT_USER_TABLES.md
@@ -0,0 +1,26 @@
+---
+title: STAT_XACT_USER_TABLES
+summary: STAT_XACT_USER_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STAT_XACT_USER_TABLES
+
+显示当前节点命名空间中用户表的事务状态信息。
+
+**表 1** STAT_XACT_USER_TABLES字段
+
+| **名称**      | **类型** | **描述**                                    |
+| :------------ | :------- | :------------------------------------------ |
+| relid         | oid      | 表的OID。                                   |
+| schemaname    | name     | 该表的模式名。                              |
+| relname       | name     | 表名。                                      |
+| seq_scan      | bigint   | 该表发起的顺序扫描数。                      |
+| seq_tup_read  | bigint   | 顺序扫描抓取的活跃行数。                    |
+| idx_scan      | bigint   | 该表发起的索引扫描数。                      |
+| idx_tup_fetch | bigint   | 索引扫描抓取的活跃行数。                    |
+| n_tup_ins     | bigint   | 插入行数。                                  |
+| n_tup_upd     | bigint   | 更新行数。                                  |
+| n_tup_del     | bigint   | 删除行数。                                  |
+| n_tup_hot_upd | bigint   | HOT更新行数（比如没有更新所需的单独索引）。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_ALL_INDEXES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_ALL_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..f11a53b66ea16da1be0621f96087d6149b15a241
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_ALL_INDEXES.md
@@ -0,0 +1,21 @@
+---
+title: SUMMARY_STAT_ALL_INDEXES
+summary: SUMMARY_STAT_ALL_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STAT_ALL_INDEXES
+
+将包含MogDB内汇聚数据库中的每个索引行，显示访问特定索引的统计。
+
+**表 1** SUMMARY_STAT_ALL_INDEXES字段
+
+| **名称**      | **类型** | **描述**                                   |
+| :------------ | :------- | :----------------------------------------- |
+| schemaname    | name     | 索引中模式名。                             |
+| relname       | name     | 索引的表名。                               |
+| indexrelname  | name     | 索引名。                                   |
+| idx_scan      | numeric  | 索引上开始的索引扫描数。                   |
+| idx_tup_read  | numeric  | 通过索引上扫描返回的索引项数。             |
+| idx_tup_fetch | numeric  | 通过使用索引的简单索引扫描抓取的活表行数。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_ALL_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_ALL_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..ccb67b4bb3928dd41b9ddf9d17b52436dc79f2fc
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_ALL_TABLES.md
@@ -0,0 +1,35 @@
+---
+title: SUMMARY_STAT_ALL_TABLES
+summary: SUMMARY_STAT_ALL_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STAT_ALL_TABLES
+
+MogDB内汇聚数据库中每个表的一行（包括TOAST表）的统计信息。
+
+**表 1** SUMMARY_STAT_ALL_TABLES字段
+
+| **名称**          | **类型**                 | **描述**                                              |
+| :---------------- | :----------------------- | :---------------------------------------------------- |
+| schemaname        | name                     | 此表的模式名。                                        |
+| relname           | name                     | 表名。                                                |
+| seq_scan          | numeric                  | 此表发起的顺序扫描数。                                |
+| seq_tup_read      | numeric                  | 顺序扫描抓取的活跃行数。                              |
+| idx_scan          | numeric                  | 此表发起的索引扫描数。                                |
+| idx_tup_fetch     | numeric                  | 索引扫描抓取的活跃行数。                              |
+| n_tup_ins         | numeric                  | 插入行数。                                            |
+| n_tup_upd         | numeric                  | 更新行数。                                            |
+| n_tup_del         | numeric                  | 删除行数。                                            |
+| n_tup_hot_upd     | numeric                  | HOT更新行数（比如没有更新所需的单独索引）。           |
+| n_live_tup        | numeric                  | 估计活跃行数。                                        |
+| n_dead_tup        | numeric                  | 估计死行数。                                          |
+| last_vacuum       | timestamp with time zone | 最后一次此表是手动清理的（不计算VACUUM FULL）的时间。 |
+| last_autovacuum   | timestamp with time zone | 上次被autovacuum守护进程清理的时间。                  |
+| last_analyze      | timestamp with time zone | 上次手动分析这个表的时间。                            |
+| last_autoanalyze  | timestamp with time zone | 上次被autovacuum守护进程分析时间。                    |
+| vacuum_count      | numeric                  | 这个表被手动清理的次数（不计算VACUUM FULL）。         |
+| autovacuum_count  | numeric                  | 这个表被autovacuum清理的次数。                        |
+| analyze_count     | numeric                  | 这个表被手动分析的次数。                              |
+| autoanalyze_count | numeric                  | 这个表被autovacuum守护进程分析的次数。                |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_BAD_BLOCK.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_BAD_BLOCK.md
new file mode 100644
index 0000000000000000000000000000000000000000..4186ed06b058cd5a419bb583f3c20a898402ac54
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_BAD_BLOCK.md
@@ -0,0 +1,22 @@
+---
+title: SUMMARY_STAT_BAD_BLOCK
+summary: SUMMARY_STAT_BAD_BLOCK
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STAT_BAD_BLOCK
+
+获得MogDB内汇聚的表、索引等文件的读取失败信息。
+
+**表 1** SUMMARY_STAT_BAD_BLOCK字段
+
+| **名称**     | **类型**                 | **描述**               |
+| :----------- | :----------------------- | :--------------------- |
+| databaseid   | integer                  | database的oid。        |
+| tablespaceid | integer                  | tablespace的oid。      |
+| relfilenode  | integer                  | relation的file node。  |
+| forknum      | bigint                   | fork编号。             |
+| error_count  | bigint                   | error的数量。          |
+| first_time   | timestamp with time zone | 坏块第一次出现的时间。 |
+| last_time    | timestamp with time zone | 坏块最后出现的时间。   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_DATABASE.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_DATABASE.md
new file mode 100644
index 0000000000000000000000000000000000000000..71d04e277dd12aab775dbe0ed6ad0b53428e446d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_DATABASE.md
@@ -0,0 +1,33 @@
+---
+title: SUMMARY_STAT_DATABASE
+summary: SUMMARY_STAT_DATABASE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STAT_DATABASE
+
+视图将包含数据库内汇聚的每个数据库的每一行，显示数据库统计。
+
+**表 1** SUMMARY_STAT_DATABASE字段
+
+| **名称**       | **类型**                 | **描述**                                                     |
+| :------------- | :----------------------- | :----------------------------------------------------------- |
+| datname        | name                     | 这个数据库的名称。                                           |
+| numbackends    | bigint                   | 当前连接到该数据库的后端数。这是在返回一个反映目前状态值的视图中唯一的列；自上次重置所有其他列返回累积值。 |
+| xact_commit    | numeric                  | 此数据库中已经提交的事务数。                                 |
+| xact_rollback  | numeric                  | 此数据库中已经回滚的事务数。                                 |
+| blks_read      | numeric                  | 在这个数据库中读取的磁盘块的数量。                           |
+| blks_hit       | numeric                  | 高速缓存中已经发现的磁盘块的次数，这样读取是不必要的（这只包括MogDB缓冲区高速缓存，没有操作系统的文件系统缓存）。 |
+| tup_returned   | numeric                  | 通过数据库查询返回的行数。                                   |
+| tup_fetched    | numeric                  | 通过数据库查询抓取的行数。                                   |
+| tup_inserted   | bigint                   | 通过数据库查询插入的行数。                                   |
+| tup_updated    | bigint                   | 通过数据库查询更新的行数。                                   |
+| tup_deleted    | bigint                   | 通过数据库查询删除的行数。                                   |
+| conflicts      | bigint                   | 由于数据库恢复冲突取消的查询数量（只在备用服务器发生的冲突）。请参见STAT_DATABASE_CONFLICTS获取更多信息。 |
+| temp_files     | numeric                  | 通过数据库查询创建的临时文件数量。计算所有临时文件，不论为什么创建临时文件（比如排序或者哈希），而且不管log_temp_files设置。 |
+| temp_bytes     | numeric                  | 通过数据库查询写入临时文件的数据总量。计算所有临时文件，不论为什么创建临时文件，而且不管log_temp_files设置。 |
+| deadlocks      | bigint                   | 在该数据库中检索的死锁数。                                   |
+| blk_read_time  | double precision         | 通过数据库后端读取数据文件块花费的时间，以毫秒计算。         |
+| blk_write_time | double precision         | 通过数据库后端写入数据文件块花费的时间，以毫秒计算。         |
+| stats_reset    | timestamp with time zone | 重置当前状态统计的时间。                                     |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_DATABASE_CONFLICTS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_DATABASE_CONFLICTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..671982a1869b230b88ef05083b142b79f8d6e5a8
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_DATABASE_CONFLICTS.md
@@ -0,0 +1,21 @@
+---
+title: SUMMARY_STAT_DATABASE_CONFLICTS
+summary: SUMMARY_STAT_DATABASE_CONFLICTS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STAT_DATABASE_CONFLICTS
+
+显示MogDB内汇聚的数据库冲突状态的统计信息。
+
+**表 1** SUMMARY_STAT_DATABASE_CONFLICTS字段
+
+| **名称**         | **类型** | **描述**             |
+| :--------------- | :------- | :------------------- |
+| datname          | name     | 数据库名称。         |
+| confl_tablespace | bigint   | 冲突的表空间的数目。 |
+| confl_lock       | bigint   | 冲突的锁数目。       |
+| confl_snapshot   | bigint   | 冲突的快照数目。     |
+| confl_bufferpin  | bigint   | 冲突的缓冲区数目。   |
+| confl_deadlock   | bigint   | 冲突的死锁数目。     |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_SYS_INDEXES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_SYS_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..ad0e41da8cacaf334dd407eb1f7ceb5a360c0b4d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_SYS_INDEXES.md
@@ -0,0 +1,21 @@
+---
+title: SUMMARY_STAT_SYS_INDEXES
+summary: SUMMARY_STAT_SYS_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STAT_SYS_INDEXES
+
+MogDB内汇聚pg_catalog、information_schema以及pg_toast模式中所有系统表的索引状态信息。
+
+**表 1** SUMMARY_STAT_SYS_INDEXES字段
+
+| **名称**      | **类型** | **描述**                                   |
+| :------------ | :------- | :----------------------------------------- |
+| schemaname    | name     | 索引中模式名。                             |
+| relname       | name     | 索引的表名。                               |
+| indexrelname  | name     | 索引名。                                   |
+| idx_scan      | numeric  | 索引上开始的索引扫描数。                   |
+| idx_tup_read  | numeric  | 通过索引上扫描返回的索引项数。             |
+| idx_tup_fetch | numeric  | 通过使用索引的简单索引扫描抓取的活表行数。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_SYS_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_SYS_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..b01260de8dab69e0bac35366eea06e74d9be30e1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_SYS_TABLES.md
@@ -0,0 +1,35 @@
+---
+title: SUMMARY_STAT_SYS_TABLES
+summary: SUMMARY_STAT_SYS_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STAT_SYS_TABLES
+
+MogDB内汇聚 pg_catalog、information_schema模式的所有命名空间中系统表的统计信息。
+
+**表 1** SUMMARY_STAT_SYS_TABLES字段
+
+| **名称**          | **类型**                 | **描述**                                            |
+| :---------------- | :----------------------- | :-------------------------------------------------- |
+| schemaname        | name                     | 此表的模式名。                                      |
+| relname           | name                     | 表名。                                              |
+| seq_scan          | numeric                  | 此表发起的顺序扫描数。                              |
+| seq_tup_read      | numeric                  | 顺序扫描抓取的活跃行数。                            |
+| idx_scan          | numeric                  | 此表发起的索引扫描数。                              |
+| idx_tup_fetch     | numeric                  | 索引扫描抓取的活跃行数。                            |
+| n_tup_ins         | numeric                  | 插入行数。                                          |
+| n_tup_upd         | numeric                  | 更新行数。                                          |
+| n_tup_del         | numeric                  | 删除行数。                                          |
+| n_tup_hot_upd     | numeric                  | HOT更新行数（比如没有更新所需的单独索引）。         |
+| n_live_tup        | numeric                  | 估计活跃行数。                                      |
+| n_dead_tup        | numeric                  | 估计死行数。                                        |
+| last_vacuum       | timestamp with time zone | 最后一次此表是手动清理的（不计算VACUUM FULL）时间。 |
+| last_autovacuum   | timestamp with time zone | 上次被autovacuum守护进程清理的时间。                |
+| last_analyze      | timestamp with time zone | 上次手动分析这个表的时间。                          |
+| last_autoanalyze  | timestamp with time zone | 上次被autovacuum守护进程分析的时间。                |
+| vacuum_count      | numeric                  | 这个表被手动清理的次数（不计算VACUUM FULL）。       |
+| autovacuum_count  | numeric                  | 这个表被autovacuum清理的次数。                      |
+| analyze_count     | numeric                  | 这个表被手动分析的次数。                            |
+| autoanalyze_count | numeric                  | 这个表被autovacuum守护进程分析的次数。              |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_USER_FUNCTIONS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_USER_FUNCTIONS.md
new file mode 100644
index 0000000000000000000000000000000000000000..c7878b2d44f701a7d7faa032b34a07f315387707
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_USER_FUNCTIONS.md
@@ -0,0 +1,20 @@
+---
+title: SUMMARY_STAT_USER_FUNCTIONS
+summary: SUMMARY_STAT_USER_FUNCTIONS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STAT_USER_FUNCTIONS
+
+SUMMARY_STAT_USER_FUNCTIONS用来统计所数据库节点用户自定义视图的相关统计信息。
+
+**表 1** SUMMARY_STAT_USER_FUNCTIONS字段
+
+| **名称**   | **类型**         | **描述**                        |
+| :--------- | :--------------- | :------------------------------ |
+| schemaname | name             | schema的名称。                                               |
+| funcname   | name             | 用户function的名称。                                         |
+| calls      | numeric          | 总调用次数。                                                 |
+| total_time | double precision | 调用此function的总时间花费，包含调用其它function的时间（单位: 毫秒）。 |
+| self_time  | double precision | 调用此function自己时间的花费，不包含调用其它function的时间（单位: 毫秒）。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_USER_INDEXES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_USER_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..af5afe4244a5c01084b9f68fa1353c77acf19b2a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_USER_INDEXES.md
@@ -0,0 +1,21 @@
+---
+title: SUMMARY_STAT_USER_INDEXES
+summary: SUMMARY_STAT_USER_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STAT_USER_INDEXES
+
+MogDB内汇聚所有数据库中用户自定义普通表的索引状态信息。
+
+**表 1** SUMMARY_STAT_USER_INDEXES字段
+
+| **名称**      | **类型** | **描述**                                   |
+| :------------ | :------- | :----------------------------------------- |
+| schemaname    | name     | 索引中模式名。                             |
+| relname       | name     | 索引的表名。                               |
+| indexrelname  | name     | 索引名。                                   |
+| idx_scan      | numeric  | 索引上开始的索引扫描数。                   |
+| idx_tup_read  | numeric  | 通过索引上扫描返回的索引项数。             |
+| idx_tup_fetch | numeric  | 通过使用索引的简单索引扫描抓取的活表行数。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_USER_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_USER_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..f941cbdb6932ed870a9135af57b342d230a6cd01
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_USER_TABLES.md
@@ -0,0 +1,35 @@
+---
+title: SUMMARY_STAT_USER_TABLES
+summary: SUMMARY_STAT_USER_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STAT_USER_TABLES
+
+MogDB内汇聚所有命名空间中用户自定义普通表的状态信息。
+
+**表 1** SUMMARY_STAT_USER_TABLES字段
+
+| **名称**          | **类型**                 | **描述**                                            |
+| :---------------- | :----------------------- | :-------------------------------------------------- |
+| schemaname        | name                     | 此表的模式名。                                      |
+| relname           | name                     | 表名。                                              |
+| seq_scan          | numeric                  | 此表发起的顺序扫描数。                              |
+| seq_tup_read      | numeric                  | 顺序扫描抓取的活跃行数。                            |
+| idx_scan          | numeric                  | 此表发起的索引扫描数。                              |
+| idx_tup_fetch     | numeric                  | 索引扫描抓取的活跃行数。                            |
+| n_tup_ins         | numeric                  | 插入行数。                                          |
+| n_tup_upd         | numeric                  | 更新行数。                                          |
+| n_tup_del         | numeric                  | 删除行数。                                          |
+| n_tup_hot_upd     | numeric                  | HOT更新行数（即没有更新所需的单独索引）。           |
+| n_live_tup        | numeric                  | 估计活跃行数。                                      |
+| n_dead_tup        | numeric                  | 估计死行数。                                        |
+| last_vacuum       | timestamp with time zone | 最后一次此表是手动清理的（不计算VACUUM FULL）时间。 |
+| last_autovacuum   | timestamp with time zone | 上次被autovacuum守护进程清理的时间。                |
+| last_analyze      | timestamp with time zone | 上次手动分析这个表的时间。                          |
+| last_autoanalyze  | timestamp with time zone | 上次被autovacuum守护进程分析的时间。                |
+| vacuum_count      | numeric                  | 这个表被手动清理的次数（不计算VACUUM FULL）。       |
+| autovacuum_count  | numeric                  | 这个表被autovacuum清理的次数。                      |
+| analyze_count     | numeric                  | 这个表被手动分析的次数。                            |
+| autoanalyze_count | numeric                  | 这个表被autovacuum守护进程分析的次数。              |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_ALL_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_ALL_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..0c0a8c45104876c599e629ab922572c705ba0db7
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_ALL_TABLES.md
@@ -0,0 +1,25 @@
+---
+title: SUMMARY_STAT_XACT_ALL_TABLES
+summary: SUMMARY_STAT_XACT_ALL_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STAT_XACT_ALL_TABLES
+
+显示MogDB内汇聚的命名空间中所有普通表和toast表的事务状态信息。
+
+**表 1** SUMMARY_STAT_XACT_ALL_TABLES字段
+
+| **名称**      | **类型** | **描述**                                    |
+| :------------ | :------- | :------------------------------------------ |
+| schemaname    | name     | 此表的模式名。                              |
+| relname       | name     | 表名。                                      |
+| seq_scan      | numeric  | 此表发起的顺序扫描数。                      |
+| seq_tup_read  | numeric  | 顺序扫描抓取的活跃行数。                    |
+| idx_scan      | numeric  | 此表发起的索引扫描数。                      |
+| idx_tup_fetch | numeric  | 索引扫描抓取的活跃行数。                    |
+| n_tup_ins     | numeric  | 插入行数。                                  |
+| n_tup_upd     | numeric  | 更新行数。                                  |
+| n_tup_del     | numeric  | 删除行数。                                  |
+| n_tup_hot_upd | numeric  | HOT更新行数（比如没有更新所需的单独索引）。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_SYS_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_SYS_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..68f31c6f76f5c0c4c1c8da8d0108ea3223755ab1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_SYS_TABLES.md
@@ -0,0 +1,25 @@
+---
+title: SUMMARY_STAT_XACT_SYS_TABLES
+summary: SUMMARY_STAT_XACT_SYS_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STAT_XACT_SYS_TABLES
+
+显示MogDB内汇聚的命名空间中系统表的事务状态信息。
+
+**表 1** SUMMARY_STAT_XACT_SYS_TABLES字段
+
+| **名称**      | **类型** | **描述**                                    |
+| :------------ | :------- | :------------------------------------------ |
+| schemaname    | name     | 此表的模式名。                              |
+| relname       | name     | 表名。                                      |
+| seq_scan      | numeric  | 此表发起的顺序扫描数。                      |
+| seq_tup_read  | numeric  | 顺序扫描抓取的活跃行数。                    |
+| idx_scan      | numeric  | 此表发起的索引扫描数。                      |
+| idx_tup_fetch | numeric  | 索引扫描抓取的活跃行数。                    |
+| n_tup_ins     | numeric  | 插入行数。                                  |
+| n_tup_upd     | numeric  | 更新行数。                                  |
+| n_tup_del     | numeric  | 删除行数。                                  |
+| n_tup_hot_upd | numeric  | HOT更新行数（比如没有更新所需的单独索引）。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_USER_FUNCTIONS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_USER_FUNCTIONS.md
new file mode 100644
index 0000000000000000000000000000000000000000..9e1132f27beb08541e6e2cb11731ccaf287cc617
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_USER_FUNCTIONS.md
@@ -0,0 +1,20 @@
+---
+title: SUMMARY_STAT_XACT_USER_FUNCTIONS
+summary: SUMMARY_STAT_XACT_USER_FUNCTIONS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STAT_XACT_USER_FUNCTIONS
+
+视图包含MogDB内汇聚的本事务内函数执行的统计信息。
+
+**表 1** SUMMARY_STAT_XACT_USER_FUNCTIONS字段
+
+| **名称**   | **类型**         | **描述**                     |
+| :--------- | :--------------- | :--------------------------- |
+| schemaname | name             | 模式的名称。                 |
+| funcname   | name             | 函数名称。                   |
+| calls      | numeric          | 函数被调用的次数。           |
+| total_time | double precision | 函数的总执行时长。           |
+| self_time  | double precision | 当前线程调用函数的总的时长。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_USER_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_USER_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..0738fe3c0e688a8a71a72a802267aadc722c6dc0
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_USER_TABLES.md
@@ -0,0 +1,25 @@
+---
+title: SUMMARY_STAT_XACT_USER_TABLES
+summary: SUMMARY_STAT_XACT_USER_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STAT_XACT_USER_TABLES
+
+显示数据库内汇聚的命名空间中用户表的事务状态信息。
+
+**表 1** SUMMARY_STAT_XACT_USER_TABLES字段
+
+| **名称**      | **类型** | **描述**                                    |
+| :------------ | :------- | :------------------------------------------ |
+| schemaname    | name     | 此表的模式名。                              |
+| relname       | name     | 表名。                                      |
+| seq_scan      | numeric  | 此表发起的顺序扫描数。                      |
+| seq_tup_read  | numeric  | 顺序扫描抓取的活跃行数。                    |
+| idx_scan      | numeric  | 此表发起的索引扫描数。                      |
+| idx_tup_fetch | numeric  | 索引扫描抓取的活跃行数。                    |
+| n_tup_ins     | numeric  | 插入行数。                                  |
+| n_tup_upd     | numeric  | 更新行数。                                  |
+| n_tup_del     | numeric  | 删除行数。                                  |
+| n_tup_hot_upd | numeric  | HOT更新行数（比如没有更新所需的单独索引）。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/GLOBAL_OPERATOR_HISTORY.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/GLOBAL_OPERATOR_HISTORY.md
new file mode 100644
index 0000000000000000000000000000000000000000..ef81cd3159bc0eeab9398dabf93410173380974a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/GLOBAL_OPERATOR_HISTORY.md
@@ -0,0 +1,37 @@
+---
+title: GLOBAL_OPERATOR_HISTORY
+summary: GLOBAL_OPERATOR_HISTORY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_OPERATOR_HISTORY
+
+GLOBAL_OPERATOR_HISTORY系统视图显示的是当前用户在数据库主节点上执行作业结束后的算子的相关记录。
+
+**表 1** GLOBAL_OPERATOR_HISTORY的字段<a id="GLOBAL_OPERATOR_HISTORY的字段"> </a>
+
+| 名称                | 类型                     | 描述                                                         |
+| :------------------ | :----------------------- | :----------------------------------------------------------- |
+| queryid             | bigint                   | 语句执行使用的内部query_id。                                 |
+| pid                 | bigint                   | 后端线程id。                                                 |
+| plan_node_id        | integer                  | 查询对应的执行计划的plan node id。                           |
+| plan_node_name      | text                     | 对应于plan_node_id的算子的名称。                             |
+| start_time          | timestamp with time zone | 该算子处理第一条数据的开始时间。                             |
+| duration            | bigint                   | 该算子到结束时候总的执行时间(ms)。                           |
+| query_dop           | integer                  | 当前算子执行时的并行度。                                     |
+| estimated_rows      | bigint                   | 优化器估算的行数信息。                                       |
+| tuple_processed     | bigint                   | 当前算子返回的元素个数。                                     |
+| min_peak_memory     | integer                  | 当前算子在数据库节点上的最小内存峰值(MB)。                   |
+| max_peak_memory     | integer                  | 当前算子在数据库节点上的最大内存峰值(MB)。                   |
+| average_peak_memory | integer                  | 当前算子在数据库节点上的平均内存峰值(MB)。                   |
+| memory_skew_percent | integer                  | 当前算子在数据库节点间的内存使用倾斜率。                     |
+| min_spill_size      | integer                  | 若发生下盘，数据库节点上下盘的最小数据量(MB)，默认为0。      |
+| max_spill_size      | integer                  | 若发生下盘，数据库节点上下盘的最大数据量(MB)，默认为0。      |
+| average_spill_size  | integer                  | 若发生下盘，数据库节点上下盘的平均数据量(MB)，默认为0。      |
+| spill_skew_percent  | integer                  | 若发生下盘，数据库节点间下盘倾斜率。                         |
+| min_cpu_time        | bigint                   | 该算子在数据库节点上的最小执行时间(ms)。                     |
+| max_cpu_time        | bigint                   | 该算子在数据库节点上的最大执行时间(ms)。                     |
+| total_cpu_time      | bigint                   | 该算子在数据库节点上的总执行时间(ms)。                       |
+| cpu_skew_percent    | integer                  | 数据库节点间执行时间的倾斜率。                               |
+| warning             | text                     | 主要显示如下几类告警信息: <br/>- Sort/SetOp/HashAgg/HashJoin spill。<br/>- Spill file size large than 256MB。<br/>- Broadcast size large than 100MB。<br/>- Early spill。<br/>- Spill times is greater than 3。<br/>- Spill on memory adaptive。<br/>- Hash table conflict。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/GLOBAL_OPERATOR_HISTORY_TABLE.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/GLOBAL_OPERATOR_HISTORY_TABLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..5a17957ed562b260586b2497f18f3f722f3262ca
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/GLOBAL_OPERATOR_HISTORY_TABLE.md
@@ -0,0 +1,10 @@
+---
+title: GLOBAL_OPERATOR_HISTORY_TABLE
+summary: GLOBAL_OPERATOR_HISTORY_TABLE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_OPERATOR_HISTORY_TABLE
+
+GLOBAL_OPERATOR_HISTORY_TABLE视图显示数据库主节点执行作业结束后的算子相关的记录。此数据是从内核中转储到系统表GS_WLM_OPERATOR_INFO中的数据。该视图是查询数据库主节点系统表GS_WLM_OPERATOR_INFO的汇聚视图。表字段同[GLOBAL_OPERATOR_HISTORY -&gt; 表1](GLOBAL_OPERATOR_HISTORY)。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/GLOBAL_OPERATOR_RUNTIME.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/GLOBAL_OPERATOR_RUNTIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..27a461e7f2c98acd11b2c2271c24af8a30e0bb23
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/GLOBAL_OPERATOR_RUNTIME.md
@@ -0,0 +1,38 @@
+---
+title: GLOBAL_OPERATOR_RUNTIME
+summary: GLOBAL_OPERATOR_RUNTIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_OPERATOR_RUNTIME
+
+GLOBAL_OPERATOR_RUNTIME视图显示当前用户在数据库主节点上正在执行的作业的算子相关信息。
+
+**表 1** GLOBAL_OPERATOR_RUNTIME的字段
+
+| 名称                | 类型                     | 描述                          |
+| :------------------ | :----------------------- | :-------------------------- |
+| queryid             | bigint                   | 语句执行使用的内部query_id。                                 |
+| pid                 | bigint                   | 后端线程id。                                                 |
+| plan_node_id        | integer                  | 查询对应的执行计划的plan node id。                           |
+| plan_node_name      | text                     | 对应于plan_node_id的算子的名称。                             |
+| start_time          | timestamp with time zone | 该算子处理第一条数据的开始时间。                             |
+| duration            | bigint                   | 该算子到结束时候总的执行时间(ms)。                           |
+| status              | text                     | 当前算子的执行状态，包括finished和running。                  |
+| query_dop           | integer                  | 当前算子执行时的并行度。                                     |
+| estimated_rows      | bigint                   | 优化器估算的行数信息。                                       |
+| tuple_processed     | bigint                   | 当前算子返回的元素个数。                                     |
+| min_peak_memory     | integer                  | 当前算子在数据库节点上的最小内存峰值(MB)。                   |
+| max_peak_memory     | integer                  | 当前算子在数据库节点上的最大内存峰值(MB)。                   |
+| average_peak_memory | integer                  | 当前算子在数据库节点上的平均内存峰值(MB)。                   |
+| memory_skew_percent | integer                  | 当前算子在数据库节点的内存使用倾斜率。                       |
+| min_spill_size      | integer                  | 若发生下盘，数据库节点上下盘的最小数据量(MB)，默认为0。      |
+| max_spill_size      | integer                  | 若发生下盘，数据库节点上下盘的最大数据量(MB)，默认为0。      |
+| average_spill_size  | integer                  | 若发生下盘，数据库节点上下盘的平均数据量(MB)，默认为0。      |
+| spill_skew_percent  | integer                  | 若发生下盘，数据库节点间下盘倾斜率。                         |
+| min_cpu_time        | bigint                   | 该算子在数据库节点上的最小执行时间(ms)。                     |
+| max_cpu_time        | bigint                   | 该算子在数据库节点上的最大执行时间(ms)。                     |
+| total_cpu_time      | bigint                   | 该算子在数据库节点上的总执行时间(ms)。                       |
+| cpu_skew_percent    | integer                  | 数据库节点间执行时间的倾斜率。                               |
+| warning             | text                     | 主要显示如下几类告警信息: <br/>- Sort/SetOp/HashAgg/HashJoin spill。<br/>- Spill file size large than 256MB。<br/>- Broadcast size large than 100MB。<br/>- Early spill。<br/>- Spill times is greater than 3。<br/>- Spill on memory adaptive。<br/>- Hash table conflict。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/OPERATOR_HISTORY.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/OPERATOR_HISTORY.md
new file mode 100644
index 0000000000000000000000000000000000000000..b39013b9eb60ba83226d8eac120d4506e1035fc1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/OPERATOR_HISTORY.md
@@ -0,0 +1,10 @@
+---
+title: OPERATOR_HISTORY
+summary: OPERATOR_HISTORY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# OPERATOR_HISTORY
+
+OPERATOR_HISTORY视图显示的是当前用户数据库主节点上执行作业结束后的算子的相关记录。记录的数据同[附录-表6](table-6)。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/OPERATOR_HISTORY_TABLE.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/OPERATOR_HISTORY_TABLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..c872167404881703a2f91a8fe865ac834346c244
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/OPERATOR_HISTORY_TABLE.md
@@ -0,0 +1,37 @@
+---
+title: OPERATOR_HISTORY_TABLE
+summary: OPERATOR_HISTORY_TABLE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# OPERATOR_HISTORY_TABLE
+
+OPERATOR_HISTORY_TABLE系统表显示执行作业结束后的算子相关的记录。此数据是从内核中转储到系统表中的数据。
+
+**表 1** OPERATOR_HISTORY_TABLE的字段
+
+| 名称                | 类型                     | 描述                           |
+| :------------------ | :----------------------- | :----------------------------|
+| queryid             | bigint                   | 语句执行使用的内部query_id。                                 |
+| pid                 | bigint                   | 后端线程id。                                                 |
+| plan_node_id        | integer                  | 查询对应的执行计划的plan node id。                           |
+| plan_node_name      | text                     | 对应于plan_node_id的算子的名称。                             |
+| start_time          | timestamp with time zone | 该算子处理第一条数据的开始时间。                             |
+| duration            | bigint                   | 该算子到结束时候总的执行时间（ms）。                         |
+| query_dop           | integer                  | 当前算子执行时的并行度。                                     |
+| estimated_rows      | bigint                   | 优化器估算的行数信息。                                       |
+| tuple_processed     | bigint                   | 当前算子返回的元素个数。                                     |
+| min_peak_memory     | integer                  | 当前算子在数据库节点上的最小内存峰值（MB）。                 |
+| max_peak_memory     | integer                  | 当前算子在数据库节点上的最大内存峰值（MB）。                 |
+| average_peak_memory | integer                  | 当前算子在数据库节点上的平均内存峰值（MB）。                 |
+| memory_skew_percent | integer                  | 当前算子在数据库节点间的内存使用倾斜率。                     |
+| min_spill_size      | integer                  | 若发生下盘，数据库节点上下盘的最小数据量（MB），默认为0。    |
+| max_spill_size      | integer                  | 若发生下盘，数据库节点上下盘的最大数据量（MB），默认为0。    |
+| average_spill_size  | integer                  | 若发生下盘，数据库节点上下盘的平均数据量（MB），默认为0。    |
+| spill_skew_percent  | integer                  | 若发生下盘，数据库节点间下盘倾斜率。                         |
+| min_cpu_time        | bigint                   | 该算子在数据库节点上的最小执行时间（ms）。                   |
+| max_cpu_time        | bigint                   | 该算子在数据库节点上的最大执行时间（ms）。                   |
+| total_cpu_time      | bigint                   | 该算子在数据库节点上的总执行时间（ms）。                     |
+| cpu_skew_percent    | integer                  | 数据库节点间执行时间的倾斜率。                               |
+| warning             | text                     | 主要显示如下几类告警信息: <br/>- Sort/SetOp/HashAgg/HashJoin spill。<br/>- Spill file size large than 256MB。<br/>- Broadcast size large than 100MB。<br/>- Early spill。<br/>- Spill times is greater than 3。<br/>- Spill on memory adaptive。<br/>- Hash table conflict。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/OPERATOR_RUNTIME.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/OPERATOR_RUNTIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..1881e5a44ddddbf925c0a4d88e65c9de729ae9a7
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/operator/OPERATOR_RUNTIME.md
@@ -0,0 +1,38 @@
+---
+title: OPERATOR_RUNTIME
+summary: OPERATOR_RUNTIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# OPERATOR_RUNTIME
+
+OPERATOR_RUNTIME视图显示当前用户正在执行的作业的算子相关信息。
+
+**表 1** OPERATOR_RUNTIME的字段
+
+| 名称                | 类型                     | 描述                               |
+| :------------------ | :----------------------- | :--------------------------------- |
+| queryid             | bigint                   | 语句执行使用的内部query_id。                                 |
+| pid                 | bigint                   | 后端线程id。                                                 |
+| plan_node_id        | integer                  | 查询对应的执行计划的plan node id。                           |
+| plan_node_name      | text                     | 对应于plan_node_id的算子的名称。                             |
+| start_time          | timestamp with time zone | 该算子处理第一条数据的开始时间。                             |
+| duration            | bigint                   | 该算子到结束时候总的执行时间（ms）。                         |
+| status              | text                     | 当前算子的执行状态，包括finished和running。                  |
+| query_dop           | integer                  | 当前算子执行时的并行度。                                     |
+| estimated_rows      | bigint                   | 优化器估算的行数信息。                                       |
+| tuple_processed     | bigint                   | 当前算子返回的元素个数。                                     |
+| min_peak_memory     | integer                  | 当前算子在数据库节点上的最小内存峰值（MB）。                 |
+| max_peak_memory     | integer                  | 当前算子在数据库节点上的最大内存峰值（MB）。                 |
+| average_peak_memory | integer                  | 当前算子在数据库节点上的平均内存峰值（MB）。                 |
+| memory_skew_percent | integer                  | 当前算子在数据库节点的内存使用倾斜率。                       |
+| min_spill_size      | integer                  | 若发生下盘，数据库节点上下盘的最小数据量（MB），默认为0。    |
+| max_spill_size      | integer                  | 若发生下盘，数据库节点上下盘的最大数据量（MB），默认为0。    |
+| average_spill_size  | integer                  | 若发生下盘，数据库节点上下盘的平均数据量（MB），默认为0。    |
+| spill_skew_percent  | integer                  | 若发生下盘，数据库节点间下盘倾斜率。                         |
+| min_cpu_time        | bigint                   | 该算子在数据库节点上的最小执行时间（ms）。                   |
+| max_cpu_time        | bigint                   | 该算子在数据库节点上的最大执行时间（ms）。                   |
+| total_cpu_time      | bigint                   | 该算子在数据库节点上的总执行时间（ms）。                     |
+| cpu_skew_percent    | integer                  | 数据库节点间执行时间的倾斜率。                               |
+| warning             | text                     | 主要显示如下几类告警信息: <br/>- Sort/SetOp/HashAgg/HashJoin spill。<br/>- Spill file size large than 256MB。<br/>- Broadcast size large than 100MB。<br/>- Early spill。<br/>- Spill times is greater than 3。<br/>- Spill on memory adaptive。<br/>- Hash table conflict。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/os/GLOBAL_OS_RUNTIME.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/os/GLOBAL_OS_RUNTIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..a07a87e3057992f2800a4bebca046e0dc270f352
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/os/GLOBAL_OS_RUNTIME.md
@@ -0,0 +1,21 @@
+---
+title: GLOBAL_OS_RUNTIME
+summary: GLOBAL_OS_RUNTIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_OS_RUNTIME
+
+提供MogDB中所有正常节点下的操作系统运行状态信息。
+
+**表 1** GLOBAL_OS_RUNTIME字段
+
+| **名称**   | **类型** | **描述**                           |
+| :--------- | :------- | :--------------------------------- |
+| node_name  | name     | 数据库进程名称。                   |
+| id         | integer  | 编号。                             |
+| name       | text     | 操作系统运行状态名称。             |
+| value      | numeric  | 操作系统运行状态值。               |
+| comments   | text     | 操作系统运行状态注释。             |
+| cumulative | boolean  | 操作系统运行状态的值是否为累加值。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/os/GLOBAL_OS_THREADS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/os/GLOBAL_OS_THREADS.md
new file mode 100644
index 0000000000000000000000000000000000000000..404bdf5f75306ac0b3d2cabf06db7da4ef4101c6
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/os/GLOBAL_OS_THREADS.md
@@ -0,0 +1,20 @@
+---
+title: GLOBAL_OS_THREADS
+summary: GLOBAL_OS_THREADS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_OS_THREADS
+
+提供MogDB中所有正常节点下的线程状态信息。
+
+**表 1** GLOBAL_OS_THREADS字段
+
+| **名称**      | **类型**                 | **描述**                         |
+| :------------ | :----------------------- | :------------------------------- |
+| node_name     | text                     | 数据库进程名称。                 |
+| pid           | bigint                   | 当前节点进程中正在运行的线程号。 |
+| lwpid         | integer                  | 与pid对应的轻量级线程号。        |
+| thread_name   | text                     | 与pid对应的线程名称。            |
+| creation_time | timestamp with time zone | 与pid对应的线程创建的时间。      |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/os/OS_RUNTIME.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/os/OS_RUNTIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..b88d00069cc20dfa74c3f88dfc5986a8e8ad9c7d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/os/OS_RUNTIME.md
@@ -0,0 +1,20 @@
+---
+title: OS_RUNTIME
+summary: OS_RUNTIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# OS_RUNTIME
+
+显示当前操作系统运行的状态信息。
+
+**表 1** OS_RUNTIME字段
+
+| **名称**   | **类型** | **描述**                           |
+| :--------- | :------- | :--------------------------------- |
+| id         | integer  | 编号。                             |
+| name       | text     | 操作系统运行状态名称。             |
+| value      | numeric  | 操作系统运行状态值。               |
+| comments   | text     | 操作系统运行状态注释。             |
+| cumulative | boolean  | 操作系统运行状态的值是否为累加值。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/os/OS_THREADS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/os/OS_THREADS.md
new file mode 100644
index 0000000000000000000000000000000000000000..20967c8989f47caf87a1379e7092691e9d639cb4
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/os/OS_THREADS.md
@@ -0,0 +1,20 @@
+---
+title: OS_THREADS
+summary: OS_THREADS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# OS_THREADS
+
+提供当前节点下所有线程的状态信息。
+
+**表 1** OS_THREADS字段
+
+| **名称**      | **类型**                 | **描述**                       |
+| :------------ | :----------------------- | :----------------------------- |
+| node_name     | text                     | 数据库进程名称。               |
+| pid           | bigint                   | 数据库进程中正在运行的线程号。 |
+| lwpid         | integer                  | 与pid对应的轻量级线程号。      |
+| thread_name   | text                     | 与pid对应的线程名称。          |
+| creation_time | timestamp with time zone | 与pid对应的线程创建的时间。    |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COMPLEX_HISTORY.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COMPLEX_HISTORY.md
new file mode 100644
index 0000000000000000000000000000000000000000..c3ce948b42dcc4ff50068a2fcef5cb76c1387cf8
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COMPLEX_HISTORY.md
@@ -0,0 +1,83 @@
+---
+title: GLOBAL_STATEMENT_COMPLEX_HISTORY
+summary: GLOBAL_STATEMENT_COMPLEX_HISTORY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STATEMENT_COMPLEX_HISTORY
+
+显示各个节点执行作业结束后的负载管理记录。
+
+**表 1** GLOBAL_STATEMENT_COMPLEX_HISTORY的字段
+
+| 名称                | 类型                     | 描述                     |
+| :------------------ | :----------------------- | :------------------------------ |
+| datid               | oid                      | 连接后端的数据库OID。                                        |
+| dbname              | text                     | 连接后端的数据库名称。                                       |
+| schemaname          | text                     | 模式的名称。                                                 |
+| nodename            | text                     | 数据库进程名称。                                             |
+| username            | text                     | 连接到后端的用户名。                                         |
+| application_name    | text                     | 连接到后端的应用名。                                         |
+| client_addr         | inet                     | 连接到后端的客户端的IP地址。 如果此字段是null，它表明通过服务器机器上UNIX套接字连接客户端或者这是内部进程，如autovacuum。 |
+| client_hostname     | text                     | 客户端的主机名，这个字段是通过client_addr的反向DNS查找得到。这个字段只有在启动log_hostname且使用IP连接时才非空。 |
+| client_port         | integer                  | 客户端用于与后端通讯的TCP端口号，如果使用Unix套接字，则为-1。 |
+| query_band          | text                     | 用于标示作业类型，可通过GUC参数query_band进行设置，默认为空字符串。 |
+| block_time          | bigint                   | 语句执行前的阻塞时间，包含语句解析和优化时间，单位ms。       |
+| start_time          | timestamp with time zone | 语句执行的开始时间。                                         |
+| finish_time         | timestamp with time zone | 语句执行的结束时间。                                         |
+| duration            | bigint                   | 语句实际执行的时间，单位ms。                                 |
+| estimate_total_time | bigint                   | 语句预估执行时间，单位ms。                                   |
+| status              | text                     | 语句执行结束状态: 正常为finished，异常为aborted。            |
+| abort_info          | text                     | 语句执行结束状态为aborted时显示异常信息。                    |
+| resource_pool       | text                     | 用户使用的资源池。                                           |
+| control_group       | text                     | 语句所使用的Cgroup。                                         |
+| estimate_memory     | integer                  | 语句预估使用内存。                                           |
+| min_peak_memory     | integer                  | 语句在数据库节点上的最小内存峰值，单位MB。                   |
+| max_peak_memory     | integer                  | 语句在数据库节点上的最大内存峰值，单位MB。                   |
+| average_peak_memory | integer                  | 语句执行过程中的内存使用平均值，单位MB。                     |
+| memory_skew_percent | integer                  | 语句数据库节点间的内存使用倾斜率。                           |
+| spill_info          | text                     | 语句在数据库节点上的下盘信息: <br/>- None: 数据库节点均未下盘。<br/>- All: 数据库节点均下盘。<br/>- [a:b]: 数量为b个数据库节点中有a个数据库节点下盘。 |
+| min_spill_size      | integer                  | 若发生下盘，数据库节点上下盘的最小数据量，单位MB，默认为0。  |
+| max_spill_size      | integer                  | 若发生下盘，数据库节点上下盘的最大数据量，单位MB，默认为0。  |
+| average_spill_size  | integer                  | 若发生下盘，数据库节点上下盘的平均数据量，单位MB，默认为0。  |
+| spill_skew_percent  | integer                  | 若发生下盘，数据库节点间下盘倾斜率。                         |
+| min_dn_time         | bigint                   | 语句在数据库节点上的最小执行时间，单位ms。                   |
+| max_dn_time         | bigint                   | 语句在数据库节点上的最大执行时间，单位ms。                   |
+| average_dn_time     | bigint                   | 语句在数据库节点上的平均执行时间，单位ms。                   |
+| dntime_skew_percent | integer                  | 语句在数据库节点的执行时间倾斜率。                           |
+| min_cpu_time        | bigint                   | 语句在数据库节点上的最小CPU时间，单位ms。                    |
+| max_cpu_time        | bigint                   | 语句在数据库节点上的最大CPU时间，单位ms。                    |
+| total_cpu_time      | bigint                   | 语句在数据库节点上的CPU总时间，单位ms。                      |
+| cpu_skew_percent    | integer                  | 语句在数据库节点间的CPU时间倾斜率。                          |
+| min_peak_iops       | integer                  | 语句在数据库节点上的每秒最小IO峰值（列存单位是次/s，行存单位是万次/s）。 |
+| max_peak_iops       | integer                  | 语句在数据库节点上的每秒最大IO峰值（列存单位是次/s，行存单位是万次/s）。 |
+| average_peak_iops   | integer                  | 语句在数据库节点上的每秒平均IO峰值（列存单位是次/s，行存单位是万次/s）。 |
+| iops_skew_percent   | integer                  | 语句在数据库节点间的IO倾斜率。                               |
+| warning             | text                     | 主要显示如下几类告警信息: <br/>- Spill file size large than 256MB。<br/>- Broadcast size large than 100MB。<br/>- Early spill。<br/>- Spill times is greater than 3。<br/>- Spill on memory adaptive。<br/>- Hash table conflict。 |
+| queryid             | bigint                   | 语句执行使用的内部query id。                                 |
+| query               | text                     | 执行的语句。                                                 |
+| query_plan          | text                     | 语句的执行计划。                                             |
+| node_group          | text                     | 语句所属用户对应的逻辑MogDB。                                |
+| cpu_top1_node_name  | text                     | cpu使用率第1的节点名称。                                     |
+| cpu_top2_node_name  | text                     | cpu使用率第2的节点名称。                                     |
+| cpu_top3_node_name  | text                     | cpu使用率第3的节点名称。                                     |
+| cpu_top4_node_name  | text                     | cpu使用率第4的节点名称。                                     |
+| cpu_top5_node_name  | text                     | cpu使用率第5的节点名称。                                     |
+| mem_top1_node_name  | text                     | 内存使用量第1的节点名称。                                    |
+| mem_top2_node_name  | text                     | 内存使用量第2的节点名称。                                    |
+| mem_top3_node_name  | text                     | 内存使用量第3的节点名称。                                    |
+| mem_top4_node_name  | text                     | 内存使用量第4的节点名称。                                    |
+| mem_top5_node_name  | text                     | 内存使用量第5的节点名称。                                    |
+| cpu_top1_value      | bigint                   | cpu使用率。                                                  |
+| cpu_top2_value      | bigint                   | cpu使用率。                                                  |
+| cpu_top3_value      | bigint                   | cpu使用率。                                                  |
+| cpu_top4_value      | bigint                   | cpu使用率。                                                  |
+| cpu_top5_value      | bigint                   | cpu使用率。                                                  |
+| mem_top1_value      | bigint                   | 内存使用量。                                                 |
+| mem_top2_value      | bigint                   | 内存使用量。                                                 |
+| mem_top3_value      | bigint                   | 内存使用量。                                                 |
+| mem_top4_value      | bigint                   | 内存使用量。                                                 |
+| mem_top5_value      | bigint                   | 内存使用量。                                                 |
+| top_mem_dn          | text                     | 内存使用量topN信息。                                         |
+| top_cpu_dn          | text                     | cpu使用量topN信息。                                          |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COMPLEX_HISTORY_TABLE.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COMPLEX_HISTORY_TABLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..b7425ca445d884e2f4141d9d3fcd7652ea99117b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COMPLEX_HISTORY_TABLE.md
@@ -0,0 +1,10 @@
+---
+title: GLOBAL_STATEMENT_COMPLEX_HISTORY_TABLE
+summary: GLOBAL_STATEMENT_COMPLEX_HISTORY_TABLE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STATEMENT_COMPLEX_HISTORY_TABLE
+
+显示各个节点执行作业结束后的负载管理记录。此数据是从内核中转储到系统表中的数据。具体的字段请参考GLOBAL_STATEMENT_COMPLEX_HISTORY中的字段。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COMPLEX_RUNTIME.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COMPLEX_RUNTIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..7ecabdd4daab58bf7c7144b0b99b2eb76f1279ac
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COMPLEX_RUNTIME.md
@@ -0,0 +1,63 @@
+---
+title: GLOBAL_STATEMENT_COMPLEX_RUNTIME
+summary: GLOBAL_STATEMENT_COMPLEX_RUNTIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STATEMENT_COMPLEX_RUNTIME
+
+显示当前用户在各个节点上正在执行的作业的负载管理记录。
+
+**表 1** GLOBAL_STATEMENT_COMPLEX_RUNTIME的字段
+
+| 名称                | 类型                     | 描述                               |
+| :------------------ | :----------------------- | :---------------------------------|
+| datid               | oid                      | 连接后端的数据OID。                                          |
+| dbname              | name                     | 连接后端的数据库名称。                                       |
+| schemaname          | text                     | 模式的名称。                                                 |
+| nodename            | text                     | 数据库进程名称                                               |
+| username            | name                     | 连接到后端的用户名。                                         |
+| application_name    | text                     | 连接到后端的应用名。                                         |
+| client_addr         | inet                     | 连接到后端的客户端的IP地址。 如果此字段是null，它表明通过服务器机器上UNIX套接字连接客户端或者这是内部进程，如autovacuum。 |
+| client_hostname     | text                     | 客户端的主机名，这个字段是通过client_addr的反向DNS查找得到。这个字段只有在启动log_hostname且使用IP连接时才非空。 |
+| client_port         | integer                  | 客户端用于与后端通讯的TCP端口号，如果使用Unix套接字，则为-1。 |
+| query_band          | text                     | 用于标示作业类型，可通过GUC参数query_band进行设置，默认为空字符串。 |
+| pid                 | bigint                   | 后端线程ID。                                                 |
+| block_time          | bigint                   | 语句执行前的阻塞时间，单位ms。                               |
+| start_time          | timestamp with time zone | 语句执行的开始时间。                                         |
+| duration            | bigint                   | 语句已经执行的时间，单位ms。                                 |
+| estimate_total_time | bigint                   | 语句执行预估总时间，单位ms。                                 |
+| estimate_left_time  | bigint                   | 语句执行预估剩余时间，单位ms。                               |
+| enqueue             | text                     | 工作负载管理资源状态。                                       |
+| resource_pool       | name                     | 用户使用的资源池。                                           |
+| control_group       | text                     | 语句所使用的Cgroup。                                         |
+| estimate_memory     | integer                  | 语句预估使用内存，单位MB。                                   |
+| min_peak_memory     | integer                  | 语句在数据库节点上的最小内存峰值，单位MB。                   |
+| max_peak_memory     | integer                  | 语句在数据库节点上的最大内存峰值，单位MB。                   |
+| average_peak_memory | integer                  | 语句执行过程中的内存使用平均值，单位MB。                     |
+| memory_skew_percent | integer                  | 语句在数据库节点间的内存使用倾斜率。                         |
+| spill_info          | text                     | 语句在数据库节点上的下盘信息: <br/>- None: 数据库节点均未下盘。<br/>- All: 数据库节点均下盘。<br/>- [a:b]: 数量为b个数据库节点中有a个数据库节点下盘。 |
+| min_spill_size      | integer                  | 若发生下盘，数据库节点上下盘的最小数据量，单位MB，默认为0。  |
+| max_spill_size      | integer                  | 若发生下盘，数据库节点上下盘的最大数据量，单位MB，默认为0。  |
+| average_spill_size  | integer                  | 若发生下盘，数据库节点上下盘的平均数据量，单位MB，默认为0。  |
+| spill_skew_percent  | integer                  | 若发生下盘，数据库节点间下盘倾斜率。                         |
+| min_dn_time         | bigint                   | 语句在数据库节点上的最小执行时间，单位ms。                   |
+| max_dn_time         | bigint                   | 语句在数据库节点上的最大执行时间，单位ms。                   |
+| average_dn_time     | bigint                   | 语句在数据库节点上的平均执行时间，单位ms。                   |
+| dntime_skew_percent | integer                  | 语句在数据库节点的执行时间倾斜率。                           |
+| min_cpu_time        | bigint                   | 语句在数据库节点上的最小CPU时间，单位ms。                    |
+| max_cpu_time        | bigint                   | 语句在数据库节点上的最大CPU时间，单位ms。                    |
+| total_cpu_time      | bigint                   | 语句在数据库节点上的CPU总时间，单位ms。                      |
+| cpu_skew_percent    | integer                  | 语句在数据库节点间的CPU时间倾斜率。                          |
+| min_peak_iops       | integer                  | 语句在数据库节点上的每秒最小IO峰值（列存单位是次/s，行存单位是万次/s）。 |
+| max_peak_iops       | integer                  | 语句在数据库节点上的每秒最大IO峰值（列存单位是次/s，行存单位是万次/s）。 |
+| average_peak_iops   | integer                  | 语句在数据库节点上的每秒平均IO峰值（列存单位是次/s，行存单位是万次/s）。 |
+| iops_skew_percent   | integer                  | 语句在数据库节点间的IO倾斜率。                               |
+| warning             | text                     | 主要显示如下几类告警信息: <br/>- Spill file size large than 256MB。<br/>- Broadcast size large than 100MB。<br/>- Early spill。<br/>- Spill times is greater than 3。<br/>- Spill on memory adaptive。<br/>- Hash table conflict。 |
+| queryid             | bigint                   | 语句执行使用的内部query id。                                 |
+| query               | text                     | 正在执行的语句。                                             |
+| query_plan          | text                     | 语句的执行计划。                                             |
+| node_group          | text                     | 语句所属用户对应的逻辑MogDB。                                |
+| top_cpu_dn          | text                     | cpu使用量topN信息。                                          |
+| top_mem_dn          | text                     | 内存使用量topN信息。                                         |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COUNT.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COUNT.md
new file mode 100644
index 0000000000000000000000000000000000000000..63dfca51633da9447f4f952b97d57d64ae5a9646
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COUNT.md
@@ -0,0 +1,41 @@
+---
+title: GLOBAL_STATEMENT_COUNT
+summary: GLOBAL_STATEMENT_COUNT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_STATEMENT_COUNT
+
+显示数据库各节点当前时刻执行的五类语句（SELECT、INSERT、UPDATE、DELETE、MERGE INTO）和（DDL、DML、DCL）统计信息。
+
+**表 1** GLOBAL_STATEMENT_COUNT字段
+
+| **名称**            | **类型** | **描述**                             |
+| :------------------ | :------- | :----------------------------------- |
+| node_name           | text     | 数据库进程名称。                     |
+| user_name           | text     | 用户名。                             |
+| select_count        | bigint   | select语句统计结果。                 |
+| update_count        | bigint   | update语句统计结果。                 |
+| insert_count        | bigint   | insert语句统计结果。                 |
+| delete_count        | bigint   | delete语句统计结果。                 |
+| mergeinto_count     | bigint   | merge into语句统计结果。             |
+| ddl_count           | bigint   | DDL语句的数量。                      |
+| dml_count           | bigint   | DML语句的数量。                      |
+| dcl_count           | bigint   | DCL语句的数量。                      |
+| total_select_elapse | bigint   | 总select的时间花费（单位: 微秒）。   |
+| avg_select_elapse   | bigint   | 平均select的时间花费（单位: 微秒）。 |
+| max_select_elapse   | bigint   | 最大select的时间花费（单位: 微秒）。 |
+| min_select_elapse   | bigint   | 最小select的时间花费（单位: 微秒）。 |
+| total_update_elapse | bigint   | 总update的时间花费（单位: 微秒）。   |
+| avg_update_elapse   | bigint   | 平均update的时间花费（单位: 微秒）。 |
+| max_update_elapse   | bigint   | 最大update的时间花费（单位: 微秒）。 |
+| min_update_elapse   | bigint   | 最小update的时间花费（单位: 微秒）。 |
+| total_insert_elapse | bigint   | 总insert的时间花费（单位: 微秒）。   |
+| avg_insert_elapse   | bigint   | 平均insert的时间花费（单位: 微秒）。 |
+| max_insert_elapse   | bigint   | 最大insert的时间花费（单位: 微秒）。 |
+| min_insert_elapse   | bigint   | 最小insert的时间花费（单位: 微秒）。 |
+| total_delete_elapse | bigint   | 总delete的时间花费（单位: 微秒）。   |
+| avg_delete_elapse   | bigint   | 平均delete的时间花费（单位: 微秒）。 |
+| max_delete_elapse   | bigint   | 最大delete的时间花费（单位: 微秒）。 |
+| min_delete_elapse   | bigint   | 最小delete的时间花费（单位: 微秒）。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT.md
new file mode 100644
index 0000000000000000000000000000000000000000..c7c104064f7857824c5a783a48262809f392ffce
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT.md
@@ -0,0 +1,56 @@
+---
+title: STATEMENT
+summary: STATEMENT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATEMENT
+
+获得当前节点的执行语句（归一化SQL）的信息。查询视图必须具有sysadmin权限或者monitor admin权限。数据库主节点上可以看到此数据库主节点接收到的归一化的SQL的全量统计信息（包含数据库节点）；数据库节点上仅可看到归一化的SQL的此节点执行的统计信息。
+
+**表 1** STATEMENT字段
+
+| **名称**            | **类型**                 | **描述**                                                     |
+| :------------------ | :----------------------- | :----------------------------------------------------------- |
+| node_name           | name                     | 数据库进程名称。                                             |
+| node_id             | integer                  | 节点的ID。                                                   |
+| user_name           | name                     | 用户名称。                                                   |
+| user_id             | oid                      | 用户OID。                                                    |
+| unique_sql_id       | bigint                   | 归一化的SQL ID。                                             |
+| query               | text                     | 归一化的SQL。                                                |
+| n_calls             | bigint                   | 调用次数。                                                   |
+| min_elapse_time     | bigint                   | SQL在内核内的最小运行时间（单位: 微秒）。                    |
+| max_elapse_time     | bigint                   | SQL在内核内的最大运行时间（单位: 微秒）。                    |
+| total_elapse_time   | bigint                   | SQL在内核内的总运行时间（单位: 微秒）。                      |
+| n_returned_rows     | bigint                   | SELECT返回的结果集行数。                                     |
+| n_tuples_fetched    | bigint                   | 随机扫描行。                                                 |
+| n_tuples_returned   | bigint                   | 顺序扫描行。                                                 |
+| n_tuples_inserted   | bigint                   | 插入行。                                                     |
+| n_tuples_updated    | bigint                   | 更新行。                                                     |
+| n_tuples_deleted    | bigint                   | 删除行。                                                     |
+| n_blocks_fetched    | bigint                   | buffer的块访问次数。                                         |
+| n_blocks_hit        | bigint                   | buffer的块命中次数。                                         |
+| n_soft_parse        | bigint                   | 软解析次数，n_soft_parse + n_hard_parse可能大于n_calls，因为子查询未计入n_calls。 |
+| n_hard_parse        | bigint                   | 硬解析次数，n_soft_parse + n_hard_parse可能大于n_calls，因为子查询未计入n_calls。 |
+| db_time             | bigint                   | 有效的DB时间花费，多线程将累加（单位: 微秒）。               |
+| cpu_time            | bigint                   | CPU时间（单位: 微秒）。                                      |
+| execution_time      | bigint                   | 执行器内执行时间（单位: 微秒）。                             |
+| parse_time          | bigint                   | SQL解析时间（单位: 微秒）。                                  |
+| plan_time           | bigint                   | SQL生成计划时间（单位: 微秒）。                              |
+| rewrite_time        | bigint                   | SQL重写时间（单位: 微秒）。                                  |
+| pl_execution_time   | bigint                   | plpgsql上的执行时间（单位: 微秒）。                          |
+| pl_compilation_time | bigint                   | plpgsql上的编译时间（单位: 微秒）。                          |
+| net_send_time       | bigint                   | 网络上的时间花费（单位: 微秒）。                             |
+| data_io_time        | bigint                   | IO上的时间花费（单位: 微秒）。                               |
+| sort_count          | bigint                   | 排序执行的次数。                                             |
+| sort_time           | bigint                   | 排序执行的时间（单位: 微秒）。                               |
+| sort_mem_used       | bigint                   | 排序过程中使用的work memory大小（单位: KB）。                |
+| sort_spill_count    | bigint                   | 排序过程中，若发生落盘，写文件的次数。                       |
+| sort_spill_size     | bigint                   | 排序过程中，若发生落盘，使用的文件大小（单位: KB）。         |
+| hash_count          | bigint                   | hash执行的次数。                                             |
+| hash_time           | bigint                   | hash执行的时间（单位: 微秒）。                               |
+| hash_mem_used       | bigint                   | hash过程中使用的work memory大小（单位: KB）。                |
+| hash_spill_count    | bigint                   | hash过程中，若发生落盘，写文件的次数。                       |
+| hash_spill_size     | bigint                   | hash过程中，若发生落盘，使用的文件大小（单位: KB）。         |
+| last_updated        | timestamp with time zone | 最后一次更新该语句的时间。                                   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_COMPLEX_HISTORY.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_COMPLEX_HISTORY.md
new file mode 100644
index 0000000000000000000000000000000000000000..15c77212027d2c1bb5213301d87e0c32f2ed5580
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_COMPLEX_HISTORY.md
@@ -0,0 +1,10 @@
+---
+title: STATEMENT_COMPLEX_HISTORY
+summary: STATEMENT_COMPLEX_HISTORY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATEMENT_COMPLEX_HISTORY
+
+STATEMENT_COMPLEX_HISTORY视图显示在数据库主节点上执行作业结束后的负载管理记录。此视图的数据直接从系统表GS_WLM_SESSION_QUERY_INFO_ALL获取。具体的字段请参考[附录-表5](table-5)。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_COMPLEX_HISTORY_TABLE.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_COMPLEX_HISTORY_TABLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..46c3c9d74bd9b9f7f5c69e3bd3ca30593ccc1440
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_COMPLEX_HISTORY_TABLE.md
@@ -0,0 +1,10 @@
+---
+title: STATEMENT_COMPLEX_HISTORY_TABLE
+summary: STATEMENT_COMPLEX_HISTORY_TABLE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATEMENT_COMPLEX_HISTORY_TABLE
+
+STATEMENT_COMPLEX_HISTORY_TABLE系统表显示数据库主节点执行作业结束后的负载管理记录。此数据是从内核中转储到系统表中的数据。具体的字段请参考附录-表5。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_COMPLEX_RUNTIME.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_COMPLEX_RUNTIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..4af3f9c366860af0987dcb1daef3dc9886377831
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_COMPLEX_RUNTIME.md
@@ -0,0 +1,63 @@
+---
+title: STATEMENT_COMPLEX_RUNTIME
+summary: STATEMENT_COMPLEX_RUNTIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATEMENT_COMPLEX_RUNTIME
+
+STATEMENT_COMPLEX_RUNTIME视图显示当前用户在数据库主节点上正在执行的作业的负载管理记录。
+
+**表 1** STATEMENT_COMPLEX_RUNTIME的字段
+
+| 名称                | 类型                     | 描述        |
+| :------------------ | :----------------------- | :---------------------------|
+| datid               | oid                      | 连接后端的数据OID。                                          |
+| dbname              | name                     | 连接后端的数据库名称。                                       |
+| schemaname          | text                     | 模式的名称。                                                 |
+| nodename            | text                     | 数据库进程名称。                                             |
+| username            | name                     | 连接到后端的用户名。                                         |
+| application_name    | text                     | 连接到后端的应用名。                                         |
+| client_addr         | inet                     | 连接到后端的客户端的IP地址。 如果此字段是null，它表明通过服务器机器上UNIX套接字连接客户端或者这是内部进程，如autovacuum。 |
+| client_hostname     | text                     | 客户端的主机名，这个字段是通过client_addr的反向DNS查找得到。这个字段只有在启动log_hostname且使用IP连接时才非空。 |
+| client_port         | integer                  | 客户端用于与后端通讯的TCP端口号，如果使用Unix套接字，则为-1。 |
+| query_band          | text                     | 用于标示作业类型，可通过GUC参数query_band进行设置，默认为空字符串。 |
+| pid                 | bigint                   | 后端线程ID。                                                 |
+| block_time          | bigint                   | 语句执行前的阻塞时间，单位ms。                               |
+| start_time          | timestamp with time zone | 语句执行的开始时间。                                         |
+| duration            | bigint                   | 语句已经执行的时间，单位ms。                                 |
+| estimate_total_time | bigint                   | 语句执行预估总时间，单位ms。                                 |
+| estimate_left_time  | bigint                   | 语句执行预估剩余时间，单位ms。                               |
+| enqueue             | text                     | 工作负载管理资源状态。                                       |
+| resource_pool       | name                     | 用户使用的资源池。                                           |
+| control_group       | text                     | 语句所使用的Cgroup。                                         |
+| estimate_memory     | integer                  | 语句预估使用内存，单位MB。                                   |
+| min_peak_memory     | integer                  | 语句在数据库节点上的最小内存峰值，单位MB。                   |
+| max_peak_memory     | integer                  | 语句在数据库节点上的最大内存峰值，单位MB。                   |
+| average_peak_memory | integer                  | 语句执行过程中的内存使用平均值，单位MB。                     |
+| memory_skew_percent | integer                  | 语句在数据库节点间的内存使用倾斜率。                         |
+| spill_info          | text                     | 语句在数据库节点上的下盘信息: <br/>- None: 数据库节点均未下盘。<br/>- All: 数据库节点均下盘。<br/>- [a:b]: 数量为b个数据库节点中有a个数据库节点下盘。 |
+| min_spill_size      | integer                  | 若发生下盘，数据库节点上下盘的最小数据量，单位MB，默认为0。  |
+| max_spill_size      | integer                  | 若发生下盘，数据库节点上下盘的最大数据量，单位MB，默认为0。  |
+| average_spill_size  | integer                  | 若发生下盘，数据库节点上下盘的平均数据量，单位MB，默认为0。  |
+| spill_skew_percent  | integer                  | 若发生下盘，数据库节点间下盘倾斜率。                         |
+| min_dn_time         | bigint                   | 语句在数据库节点上的最小执行时间，单位ms。                   |
+| max_dn_time         | bigint                   | 语句在数据库节点上的最大执行时间，单位ms。                   |
+| average_dn_time     | bigint                   | 语句在数据库节点上的平均执行时间，单位ms。                   |
+| dntime_skew_percent | integer                  | 语句在数据库节点的执行时间倾斜率。                           |
+| min_cpu_time        | bigint                   | 语句在数据库节点上的最小CPU时间，单位ms。                    |
+| max_cpu_time        | bigint                   | 语句在数据库节点上的最大CPU时间，单位ms。                    |
+| total_cpu_time      | bigint                   | 语句在数据库节点上的CPU总时间，单位ms。                      |
+| cpu_skew_percent    | integer                  | 语句在数据库节点间的CPU时间倾斜率。                          |
+| min_peak_iops       | integer                  | 语句在数据库节点上的每秒最小IO峰值（列存单位是次/s，行存单位是万次/s）。 |
+| max_peak_iops       | integer                  | 语句在数据库节点上的每秒最大IO峰值（列存单位是次/s，行存单位是万次/s）。 |
+| average_peak_iops   | integer                  | 语句在数据库节点上的每秒平均IO峰值（列存单位是次/s，行存单位是万次/s）。 |
+| iops_skew_percent   | integer                  | 语句在数据库节点间的IO倾斜率。                               |
+| warning             | text                     | 主要显示如下几类告警信息: <br/>- Spill file size large than 256MB。<br/>- Broadcast size large than 100MB。<br/>- Early spill。<br/>- Spill times is greater than 3。<br/>- Spill on memory adaptive。<br/>- Hash table conflict。 |
+| queryid             | bigint                   | 语句执行使用的内部query id。                                 |
+| query               | text                     | 正在执行的语句。                                             |
+| query_plan          | text                     | 语句的执行计划。                                             |
+| node_group          | text                     | 语句所属用户对应的逻辑MogDB。                                |
+| top_cpu_dn          | text                     | cpu使用量topN信息。                                          |
+| top_mem_dn          | text                     | 内存使用量topN信息。                                         |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_COUNT.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_COUNT.md
new file mode 100644
index 0000000000000000000000000000000000000000..cfbe2cc7018d36cd7889634fa9639d28560d99a4
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_COUNT.md
@@ -0,0 +1,44 @@
+---
+title: STATEMENT_COUNT
+summary: STATEMENT_COUNT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATEMENT_COUNT
+
+显示数据库当前节点当前时刻执行的五类语句（SELECT、INSERT、UPDATE、DELETE、MERGE INTO）和（DDL、DML、DCL）统计信息。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+> 普通用户查询STATEMENT_COUNT视图仅能看到该用户当前节点的统计信息；管理员权限用户查询STATEMENT_COUNT视图则能看到所有用户当前节点的统计信息。当MogDB或该节点重启时，计数将清零，并重新开始计数。计数以节点收到的查询数为准，MogDB内部进行的查询。例如，数据库主节点收到一条查询，若下发多条查询数据库节点，那将在数据库节点上进行相应次数的计数。
+
+**表 1** STATEMENT_COUNT字段
+
+| **名称**            | **类型** | **描述**                             |
+| :------------------ | :------- | :----------------------------------- |
+| node_name           | text     | 数据库进程名称。                     |
+| user_name           | text     | 用户名。                             |
+| select_count        | bigint   | select语句统计结果。                 |
+| update_count        | bigint   | update语句统计结果。                 |
+| insert_count        | bigint   | insert语句统计结果。                 |
+| delete_count        | bigint   | delete语句统计结果。                 |
+| mergeinto_count     | bigint   | merge into语句统计结果。             |
+| ddl_count           | bigint   | DDL语句的数量。                      |
+| dml_count           | bigint   | DML语句的数量。                      |
+| dcl_count           | bigint   | DCL语句的数量。                      |
+| total_select_elapse | bigint   | 总select的时间花费（单位: 微秒）。   |
+| avg_select_elapse   | bigint   | 平均select的时间花费（单位: 微秒）。 |
+| max_select_elapse   | bigint   | 最大select的时间花费（单位: 微秒）。 |
+| min_select_elapse   | bigint   | 最小select的时间花费（单位: 微秒）。 |
+| total_update_elapse | bigint   | 总update的时间花费（单位: 微秒）。   |
+| avg_update_elapse   | bigint   | 平均update的时间花费(单位: 微秒)。   |
+| max_update_elapse   | bigint   | 最大update的时间花费（单位: 微秒）。 |
+| min_update_elapse   | bigint   | 最小update的时间花费（单位: 微秒）。 |
+| total_insert_elapse | bigint   | 总insert的时间花费（单位: 微秒）。   |
+| avg_insert_elapse   | bigint   | 平均insert的时间花费（单位: 微秒）。 |
+| max_insert_elapse   | bigint   | 最大insert的时间花费（单位: 微秒）。 |
+| min_insert_elapse   | bigint   | 最小insert的时间花费（单位: 微秒）。 |
+| total_delete_elapse | bigint   | 总delete的时间花费（单位: 微秒）。   |
+| avg_delete_elapse   | bigint   | 平均delete的时间花费（单位: 微秒）。 |
+| max_delete_elapse   | bigint   | 最大delete的时间花费（单位: 微秒）。 |
+| min_delete_elapse   | bigint   | 最小delete的时间花费（单位: 微秒）。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_HISTORY.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_HISTORY.md
new file mode 100644
index 0000000000000000000000000000000000000000..357afcac5e7f56c997ba9bbc967158c1b635e789
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_HISTORY.md
@@ -0,0 +1,492 @@
+---
+title: STATEMENT_HISTORY
+summary: STATEMENT_HISTORY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATEMENT_HISTORY
+
+获得当前节点的执行语句的信息。查询系统表必须具有sysadmin权限。只可在系统库中查询到结果，用户库中无法查询。
+
+对于此系统表查询有如下约束：
+
+- 必须在postgres库内查询，其它库中不存数据。
+- 此系统表受track_stmt_stat_level控制，默认为“OFF,L0”，第一部分控制Full SQL，第二部分控制Slow SQL，具体字段记录级别见下表。
+- 对于Slow SQL，当track_stmt_stat_level的值为非OFF时，且SQL执行时间超过log_min_duration_statement，会记录为慢SQL。
+
+**表 1** STATEMENT_HISTORY字段
+
+<table><thead align="left"><tr id="row44901885283"><th class="cellrowborder" valign="top"  id="mcps1.2.5.1.1"><p id="p204912089289"><a name="p204912089289"></a><a name="p204912089289"></a>名称</p>
+</th>
+<th class="cellrowborder" valign="top"  id="mcps1.2.5.1.2"><p id="p17491108122820"><a name="p17491108122820"></a><a name="p17491108122820"></a>类型</p>
+</th>
+<th class="cellrowborder" valign="top"  id="mcps1.2.5.1.3"><p id="p13491282281"><a name="p13491282281"></a><a name="p13491282281"></a>描述</p>
+</th>
+<th class="cellrowborder" valign="top"  id="mcps1.2.5.1.4"><p id="p1528612136307"><a name="p1528612136307"></a><a name="p1528612136307"></a>记录级别</p>
+</th>
+</tr>
+</thead>
+<tbody><tr id="row16491158192819"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p1149178122814"><a name="p1149178122814"></a><a name="p1149178122814"></a>db_name</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p124911782289"><a name="p124911782289"></a><a name="p124911782289"></a>name</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p1445326163513"><a name="p1445326163513"></a><a name="p1445326163513"></a>数据库名称。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p028618138308"><a name="p028618138308"></a><a name="p028618138308"></a>L0</p>
+</td>
+</tr>
+<tr id="row14915892817"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p174910812286"><a name="p174910812286"></a><a name="p174910812286"></a>schema_name</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p1949128172817"><a name="p1949128172817"></a><a name="p1949128172817"></a>name</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p164911589285"><a name="p164911589285"></a><a name="p164911589285"></a>schema名称。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p1328616134303"><a name="p1328616134303"></a><a name="p1328616134303"></a>L0</p>
+</td>
+</tr>
+<tr id="row749113817286"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p1749115882810"><a name="p1749115882810"></a><a name="p1749115882810"></a>origin_node</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p449148162820"><a name="p449148162820"></a><a name="p449148162820"></a>integer</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p16491108182819"><a name="p16491108182819"></a><a name="p16491108182819"></a>节点名称。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p19286111393017"><a name="p19286111393017"></a><a name="p19286111393017"></a>L0</p>
+</td>
+</tr>
+<tr id="row649168132810"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p44917817289"><a name="p44917817289"></a><a name="p44917817289"></a>user_name</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p194912810285"><a name="p194912810285"></a><a name="p194912810285"></a>name</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p134914811289"><a name="p134914811289"></a><a name="p134914811289"></a>用户名。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p9286161313016"><a name="p9286161313016"></a><a name="p9286161313016"></a>L0</p>
+</td>
+</tr>
+<tr id="row249116815283"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p165338590242"><a name="p165338590242"></a><a name="p165338590242"></a>application_name</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p195321859102416"><a name="p195321859102416"></a><a name="p195321859102416"></a>text</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p105321759202415"><a name="p105321759202415"></a><a name="p105321759202415"></a>用户发起的请求的应用程序名称。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p1528671363015"><a name="p1528671363015"></a><a name="p1528671363015"></a>L0</p>
+</td>
+</tr>
+<tr id="row7491288288"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p1353125916241"><a name="p1353125916241"></a><a name="p1353125916241"></a>client_addr</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p14530125919243"><a name="p14530125919243"></a><a name="p14530125919243"></a>text</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p153025992418"><a name="p153025992418"></a><a name="p153025992418"></a>用户发起的请求的客户端地址。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p0286181333019"><a name="p0286181333019"></a><a name="p0286181333019"></a>L0</p>
+</td>
+</tr>
+<tr id="row1749158112812"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p1652975902410"><a name="p1652975902410"></a><a name="p1652975902410"></a>client_port</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p2529859102410"><a name="p2529859102410"></a><a name="p2529859102410"></a>integer</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p252865911245"><a name="p252865911245"></a><a name="p252865911245"></a>用户发起的请求的客户端端口。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p132861413123018"><a name="p132861413123018"></a><a name="p132861413123018"></a>L0</p>
+</td>
+</tr>
+<tr id="row148912328303"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p452716597243"><a name="p452716597243"></a><a name="p452716597243"></a>unique_query_id</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p115271059112417"><a name="p115271059112417"></a><a name="p115271059112417"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p1752618596243"><a name="p1752618596243"></a><a name="p1752618596243"></a>归一化SQL ID。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p1528631383020"><a name="p1528631383020"></a><a name="p1528631383020"></a>L0</p>
+</td>
+</tr>
+<tr id="row3770204193018"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p3525059192414"><a name="p3525059192414"></a><a name="p3525059192414"></a>debug_query_id</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p19525195982418"><a name="p19525195982418"></a><a name="p19525195982418"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p9524359162416"><a name="p9524359162416"></a><a name="p9524359162416"></a>唯一SQL ID。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p10286101318302"><a name="p10286101318302"></a><a name="p10286101318302"></a>L0</p>
+</td>
+</tr>
+<tr id="row1024411583535"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p124416583539"><a name="p124416583539"></a><a name="p124416583539"></a>query</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p024495835312"><a name="p024495835312"></a><a name="p024495835312"></a>text</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p192447585532"><a name="p192447585532"></a><a name="p192447585532"></a>归一化SQL。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p1428681313019"><a name="p1428681313019"></a><a name="p1428681313019"></a>L0</p>
+</td>
+</tr>
+<tr id="row3114174743016"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p10523459142411"><a name="p10523459142411"></a><a name="p10523459142411"></a>start_time</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p1752305914246"><a name="p1752305914246"></a><a name="p1752305914246"></a>timestamp with time zone</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p952265920244"><a name="p952265920244"></a><a name="p952265920244"></a>语句启动的时间。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p0286151314305"><a name="p0286151314305"></a><a name="p0286151314305"></a>L0</p>
+</td>
+</tr>
+<tr id="row769485863017"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p155224594242"><a name="p155224594242"></a><a name="p155224594242"></a>finish_time</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p752117599242"><a name="p752117599242"></a><a name="p752117599242"></a>timestamp with time zone</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p1952065952411"><a name="p1952065952411"></a><a name="p1952065952411"></a>语句结束的时间。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p17286201317309"><a name="p17286201317309"></a><a name="p17286201317309"></a>L0</p>
+</td>
+</tr>
+<tr id="row254515130314"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p1752095917241"><a name="p1752095917241"></a><a name="p1752095917241"></a>slow_sql_threshold</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p185191059122416"><a name="p185191059122416"></a><a name="p185191059122416"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p35181759122420"><a name="p35181759122420"></a><a name="p35181759122420"></a>语句执行时慢SQL的标准。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p11286171373011"><a name="p11286171373011"></a><a name="p11286171373011"></a>L0</p>
+</td>
+</tr>
+<tr id="row4589123123110"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p4518559182412"><a name="p4518559182412"></a><a name="p4518559182412"></a>transaction_id</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p5517185952411"><a name="p5517185952411"></a><a name="p5517185952411"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p2517125922414"><a name="p2517125922414"></a><a name="p2517125922414"></a>事务ID。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p928621319302"><a name="p928621319302"></a><a name="p928621319302"></a>L0</p>
+</td>
+</tr>
+<tr id="row858902319313"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p15516145982414"><a name="p15516145982414"></a><a name="p15516145982414"></a>thread_id</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p20515659162415"><a name="p20515659162415"></a><a name="p20515659162415"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p55151659102410"><a name="p55151659102410"></a><a name="p55151659102410"></a>执行线程ID。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p1428651323019"><a name="p1428651323019"></a><a name="p1428651323019"></a>L0</p>
+</td>
+</tr>
+<tr id="row358810234313"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p1251416594243"><a name="p1251416594243"></a><a name="p1251416594243"></a>session_id</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p205131359172418"><a name="p205131359172418"></a><a name="p205131359172418"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p185131159202420"><a name="p185131159202420"></a><a name="p185131159202420"></a>用户session id。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p12286813103010"><a name="p12286813103010"></a><a name="p12286813103010"></a>L0</p>
+</td>
+</tr>
+<tr id="row1858812314315"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p35121459142416"><a name="p35121459142416"></a><a name="p35121459142416"></a>n_soft_parse</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p105113599242"><a name="p105113599242"></a><a name="p105113599242"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p172795294391"><a name="p172795294391"></a><a name="p172795294391"></a>软解析次数，n_soft_parse + n_hard_parse可能大于n_calls，因为子查询未计入n_calls。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p1286161310302"><a name="p1286161310302"></a><a name="p1286161310302"></a>L0</p>
+</td>
+</tr>
+<tr id="row13775115215319"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p135106596249"><a name="p135106596249"></a><a name="p135106596249"></a>n_hard_parse</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p951015915249"><a name="p951015915249"></a><a name="p951015915249"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p18230133983919"><a name="p18230133983919"></a><a name="p18230133983919"></a>硬解析次数，n_soft_parse + n_hard_parse可能大于n_calls，因为子查询未计入n_calls。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p3286181310305"><a name="p3286181310305"></a><a name="p3286181310305"></a>L0</p>
+</td>
+</tr>
+<tr id="row877515216319"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p135081059162412"><a name="p135081059162412"></a><a name="p135081059162412"></a>query_plan</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p18508185911243"><a name="p18508185911243"></a><a name="p18508185911243"></a>text</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p150795912247"><a name="p150795912247"></a><a name="p150795912247"></a>语句执行计划。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p1328731383018"><a name="p1328731383018"></a><a name="p1328731383018"></a>L1</p>
+</td>
+</tr>
+<tr id="row17775052123118"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p1250610593248"><a name="p1250610593248"></a><a name="p1250610593248"></a>n_returned_rows</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p1150610599240"><a name="p1150610599240"></a><a name="p1150610599240"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p19505155942415"><a name="p19505155942415"></a><a name="p19505155942415"></a>SELECT返回的结果集行数。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p1628716136303"><a name="p1628716136303"></a><a name="p1628716136303"></a>L0</p>
+</td>
+</tr>
+<tr id="row1977515273114"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p45042059132410"><a name="p45042059132410"></a><a name="p45042059132410"></a>n_tuples_fetched</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p1450495913244"><a name="p1450495913244"></a><a name="p1450495913244"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p19503195917240"><a name="p19503195917240"></a><a name="p19503195917240"></a>随机扫描行。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p42877136308"><a name="p42877136308"></a><a name="p42877136308"></a>L0</p>
+</td>
+</tr>
+<tr id="row1677535213111"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p250235912413"><a name="p250235912413"></a><a name="p250235912413"></a>n_tuples_returned</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p185021959192418"><a name="p185021959192418"></a><a name="p185021959192418"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p350120599248"><a name="p350120599248"></a><a name="p350120599248"></a>顺序扫描行。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p8287413143018"><a name="p8287413143018"></a><a name="p8287413143018"></a>L0</p>
+</td>
+</tr>
+<tr id="row777417524311"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p16500195992414"><a name="p16500195992414"></a><a name="p16500195992414"></a>n_tuples_inserted</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p1150019594246"><a name="p1150019594246"></a><a name="p1150019594246"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p948105916244"><a name="p948105916244"></a><a name="p948105916244"></a>插入行。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p22871135302"><a name="p22871135302"></a><a name="p22871135302"></a>L0</p>
+</td>
+</tr>
+<tr id="row677415293112"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p2498222251"><a name="p2498222251"></a><a name="p2498222251"></a>n_tuples_updated</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p749722192515"><a name="p749722192515"></a><a name="p749722192515"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p549713212254"><a name="p549713212254"></a><a name="p549713212254"></a>更新行。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p628721314301"><a name="p628721314301"></a><a name="p628721314301"></a>L0</p>
+</td>
+</tr>
+<tr id="row1774185218312"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p749611272519"><a name="p749611272519"></a><a name="p749611272519"></a>n_tuples_deleted</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p349513202519"><a name="p349513202519"></a><a name="p349513202519"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p17495923250"><a name="p17495923250"></a><a name="p17495923250"></a>删除行。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p4287111343014"><a name="p4287111343014"></a><a name="p4287111343014"></a>L0</p>
+</td>
+</tr>
+<tr id="row277420523319"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p94943242512"><a name="p94943242512"></a><a name="p94943242512"></a>n_blocks_fetched</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p749317222510"><a name="p749317222510"></a><a name="p749317222510"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p449282182511"><a name="p449282182511"></a><a name="p449282182511"></a>buffer的块访问次数。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p5287131333016"><a name="p5287131333016"></a><a name="p5287131333016"></a>L0</p>
+</td>
+</tr>
+<tr id="row57742052153113"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p749211282517"><a name="p749211282517"></a><a name="p749211282517"></a>n_blocks_hit</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p849132102510"><a name="p849132102510"></a><a name="p849132102510"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p749012242515"><a name="p749012242515"></a><a name="p749012242515"></a>buffer的块命中次数。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p82871813143014"><a name="p82871813143014"></a><a name="p82871813143014"></a>L0</p>
+</td>
+</tr>
+<tr id="row777455214319"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p184893272519"><a name="p184893272519"></a><a name="p184893272519"></a>db_time</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p24891427257"><a name="p24891427257"></a><a name="p24891427257"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p1771542215411"><a name="p1771542215411"></a><a name="p1771542215411"></a>有效的DB时间花费，多线程将累加（单位：微秒）。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p14287131318305"><a name="p14287131318305"></a><a name="p14287131318305"></a>L0</p>
+</td>
+</tr>
+<tr id="row197745525319"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p1448713252518"><a name="p1448713252518"></a><a name="p1448713252518"></a>cpu_time</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p15486922257"><a name="p15486922257"></a><a name="p15486922257"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p948622132512"><a name="p948622132512"></a><a name="p948622132512"></a>CPU时间（单位：微秒）。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p182871113103018"><a name="p182871113103018"></a><a name="p182871113103018"></a>L0</p>
+</td>
+</tr>
+<tr id="row7761050202716"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p14761650132718"><a name="p14761650132718"></a><a name="p14761650132718"></a>execution_time</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p1276125014277"><a name="p1276125014277"></a><a name="p1276125014277"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p1976118507270"><a name="p1976118507270"></a><a name="p1976118507270"></a>执行器内执行时间（单位：微秒）。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p18287213183013"><a name="p18287213183013"></a><a name="p18287213183013"></a>L0</p>
+</td>
+</tr>
+<tr id="row96551157152710"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p765618575270"><a name="p765618575270"></a><a name="p765618575270"></a>parse_time</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p3656185752712"><a name="p3656185752712"></a><a name="p3656185752712"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p106561157142716"><a name="p106561157142716"></a><a name="p106561157142716"></a>SQL解析时间（单位：微秒）。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p6287161319308"><a name="p6287161319308"></a><a name="p6287161319308"></a>L0</p>
+</td>
+</tr>
+<tr id="row386316372814"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p98641331289"><a name="p98641331289"></a><a name="p98641331289"></a>plan_time</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p1686416312283"><a name="p1686416312283"></a><a name="p1686416312283"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p198640320288"><a name="p198640320288"></a><a name="p198640320288"></a>SQL生成计划时间（单位：微秒）。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p728751313307"><a name="p728751313307"></a><a name="p728751313307"></a>L0</p>
+</td>
+</tr>
+<tr id="row1236810134287"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p12368141313288"><a name="p12368141313288"></a><a name="p12368141313288"></a>rewrite_time</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p143681413202810"><a name="p143681413202810"></a><a name="p143681413202810"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p936861372810"><a name="p936861372810"></a><a name="p936861372810"></a>SQL重写时间（单位：微秒）。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p1287191312304"><a name="p1287191312304"></a><a name="p1287191312304"></a>L0</p>
+</td>
+</tr>
+<tr id="row1831252022816"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p14312102010285"><a name="p14312102010285"></a><a name="p14312102010285"></a>pl_execution_time</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p63121020102811"><a name="p63121020102811"></a><a name="p63121020102811"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p33121020172816"><a name="p33121020172816"></a><a name="p33121020172816"></a>plpgsql上的执行时间（单位：微秒）。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p128731312309"><a name="p128731312309"></a><a name="p128731312309"></a>L0</p>
+</td>
+</tr>
+<tr id="row12287162622811"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p18287182642811"><a name="p18287182642811"></a><a name="p18287182642811"></a>pl_compilation_time</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p1428782692815"><a name="p1428782692815"></a><a name="p1428782692815"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p628712617287"><a name="p628712617287"></a><a name="p628712617287"></a>plpgsql上的编译时间（单位：微秒）。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p102871113163013"><a name="p102871113163013"></a><a name="p102871113163013"></a>L0</p>
+</td>
+</tr>
+<tr id="row9895133272810"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p12895193212813"><a name="p12895193212813"></a><a name="p12895193212813"></a>data_io_time</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p6895103242810"><a name="p6895103242810"></a><a name="p6895103242810"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p10895203212289"><a name="p10895203212289"></a><a name="p10895203212289"></a>IO上的时间花费（单位：微秒）。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p1287181383013"><a name="p1287181383013"></a><a name="p1287181383013"></a>L0</p>
+</td>
+</tr>
+<tr id="row19021825295"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p790215242915"><a name="p790215242915"></a><a name="p790215242915"></a>net_send_info</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p19022242917"><a name="p19022242917"></a><a name="p19022242917"></a>text</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p166675265421"><a name="p166675265421"></a><a name="p166675265421"></a>通过物理连接发送消息的网络状态，包含时间（微秒）、调用次数、吞吐量（字节）。通过该字段可以分析SQL在分布式系统下的网络开销，单机模式下不支持该字段。例如：{"time":xxx, "n_calls":xxx, "size":xxx}。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p202871513143012"><a name="p202871513143012"></a><a name="p202871513143012"></a>L0</p>
+</td>
+</tr>
+<tr id="row1597621252919"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p129761512172910"><a name="p129761512172910"></a><a name="p129761512172910"></a>net_recv_info</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p19976131232915"><a name="p19976131232915"></a><a name="p19976131232915"></a>text</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p16967114513427"><a name="p16967114513427"></a><a name="p16967114513427"></a>通过物理连接接收消息的网络状态，包含时间（微秒）、调用次数、吞吐量（字节）。通过该字段可以分析SQL在分布式系统下的网络开销，单机模式下不支持该字段。例如：{"time":xxx, "n_calls":xxx, "size":xxx}。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p15287413123014"><a name="p15287413123014"></a><a name="p15287413123014"></a>L0</p>
+</td>
+</tr>
+<tr id="row2051215917299"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p2051269132917"><a name="p2051269132917"></a><a name="p2051269132917"></a>net_stream_send_info</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p1451215911291"><a name="p1451215911291"></a><a name="p1451215911291"></a>text</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p695315818427"><a name="p695315818427"></a><a name="p695315818427"></a>通过逻辑连接发送消息的网络状态，包含时间（微秒）、调用次数、吞吐量（字节）。通过该字段可以分析SQL在分布式系统下的网络开销，单机模式下不支持该字段。例如：{"time":xxx, "n_calls":xxx, "size":xxx}。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p192871113113013"><a name="p192871113113013"></a><a name="p192871113113013"></a>L0</p>
+</td>
+</tr>
+<tr id="row1978203162913"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p167818317296"><a name="p167818317296"></a><a name="p167818317296"></a>net_stream_recv_info</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p1578173110298"><a name="p1578173110298"></a><a name="p1578173110298"></a>text</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p292014112436"><a name="p292014112436"></a><a name="p292014112436"></a>通过逻辑连接接收消息的网络状态，包含时间（微秒）、调用次数、吞吐量（字节）。通过该字段可以分析SQL在分布式系统下的网络开销，单机模式下不支持该字段。例如：{"time":xxx, "n_calls":xxx, "size":xxx}。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p5287131303020"><a name="p5287131303020"></a><a name="p5287131303020"></a>L0</p>
+</td>
+</tr>
+<tr id="row15401123892910"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p154011138192918"><a name="p154011138192918"></a><a name="p154011138192918"></a>lock_count</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p1440123818299"><a name="p1440123818299"></a><a name="p1440123818299"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p840113386291"><a name="p840113386291"></a><a name="p840113386291"></a>加锁次数。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p16287141393017"><a name="p16287141393017"></a><a name="p16287141393017"></a>L0</p>
+</td>
+</tr>
+<tr id="row17958944152917"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p19958204410298"><a name="p19958204410298"></a><a name="p19958204410298"></a>lock_time</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p69582044122918"><a name="p69582044122918"></a><a name="p69582044122918"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p12958344142919"><a name="p12958344142919"></a><a name="p12958344142919"></a>加锁耗时。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p428713136307"><a name="p428713136307"></a><a name="p428713136307"></a>L1</p>
+</td>
+</tr>
+<tr id="row4438148112918"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p1043884818295"><a name="p1043884818295"></a><a name="p1043884818295"></a>lock_wait_count</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p1743816482294"><a name="p1743816482294"></a><a name="p1743816482294"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p11438144832911"><a name="p11438144832911"></a><a name="p11438144832911"></a>加锁等待次数。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p7287141313019"><a name="p7287141313019"></a><a name="p7287141313019"></a>L0</p>
+</td>
+</tr>
+<tr id="row12165137203010"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p01662710309"><a name="p01662710309"></a><a name="p01662710309"></a>lock_wait_time</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p11166379302"><a name="p11166379302"></a><a name="p11166379302"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p2016677173010"><a name="p2016677173010"></a><a name="p2016677173010"></a>加锁等待耗时。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p228791343012"><a name="p228791343012"></a><a name="p228791343012"></a>L1</p>
+</td>
+</tr>
+<tr id="row1594391063014"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p139437103309"><a name="p139437103309"></a><a name="p139437103309"></a>lock_max_count</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p3943910163018"><a name="p3943910163018"></a><a name="p3943910163018"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p394311015303"><a name="p394311015303"></a><a name="p394311015303"></a>最大持锁数量。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p228761311308"><a name="p228761311308"></a><a name="p228761311308"></a>L0</p>
+</td>
+</tr>
+<tr id="row15933436143016"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p199331936153019"><a name="p199331936153019"></a><a name="p199331936153019"></a>lwlock_count</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p5933183683016"><a name="p5933183683016"></a><a name="p5933183683016"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p893393612304"><a name="p893393612304"></a><a name="p893393612304"></a>轻量级加锁次数（预留）。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p02879138309"><a name="p02879138309"></a><a name="p02879138309"></a>L0</p>
+</td>
+</tr>
+<tr id="row92451440133019"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p624512407308"><a name="p624512407308"></a><a name="p624512407308"></a>lwlock_wait_count</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p1024613403300"><a name="p1024613403300"></a><a name="p1024613403300"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p162462407306"><a name="p162462407306"></a><a name="p162462407306"></a>轻量级等锁次数。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p0288161316307"><a name="p0288161316307"></a><a name="p0288161316307"></a>L0</p>
+</td>
+</tr>
+<tr id="row10701104318302"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p1470184333016"><a name="p1470184333016"></a><a name="p1470184333016"></a>lwlock_time</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p870104318305"><a name="p870104318305"></a><a name="p870104318305"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p17701543103012"><a name="p17701543103012"></a><a name="p17701543103012"></a>轻量级加锁时间（预留）。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p17288111343017"><a name="p17288111343017"></a><a name="p17288111343017"></a>L1</p>
+</td>
+</tr>
+<tr id="row551915663018"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p25199565301"><a name="p25199565301"></a><a name="p25199565301"></a>lwlock_wait_time</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p8519145615307"><a name="p8519145615307"></a><a name="p8519145615307"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p195190563305"><a name="p195190563305"></a><a name="p195190563305"></a>轻量级等锁时间。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p628881320304"><a name="p628881320304"></a><a name="p628881320304"></a>L1</p>
+</td>
+</tr>
+<tr id="row1139711323112"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p73972034315"><a name="p73972034315"></a><a name="p73972034315"></a>details</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p339717319319"><a name="p339717319319"></a><a name="p339717319319"></a>bytea</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p43971231315"><a name="p43971231315"></a><a name="p43971231315"></a>语句锁事件的列表，该列表按时间书序记录事件，记录的数量受参数track_stmt_details_size的影响。</p>
+<p id="p206443813496"><a name="p206443813496"></a><a name="p206443813496"></a>事件包括：</p>
+<a name="ul1619215224171"></a><a name="ul1619215224171"></a><ul id="ul1619215224171"><li>加锁开始。</li><li>加锁结束。</li><li>等锁开始。</li><li>等锁结束。</li><li>放锁开始。</li><li>放锁结束。</li><li>轻量级等锁开始。</li><li>轻量级等锁结束。</li></ul>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p162884132309"><a name="p162884132309"></a><a name="p162884132309"></a>L2</p>
+</td>
+</tr>
+<tr id="row1146417610552"><td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.1 "><p id="p174641163550"><a name="p174641163550"></a><a name="p174641163550"></a>is_slow_sql</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.2 "><p id="p44649617558"><a name="p44649617558"></a><a name="p44649617558"></a>boolean</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.3 "><p id="p13464660559"><a name="p13464660559"></a><a name="p13464660559"></a>该SQL是否为slow SQL。</p>
+</td>
+<td class="cellrowborder" valign="top"  headers="mcps1.2.5.1.4 "><p id="p17288713183018"><a name="p17288713183018"></a><a name="p17288713183018"></a>L0</p>
+</td>
+</tr>
+</tbody>
+</table>
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_RESPONSETIME_PERCENTILE.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_RESPONSETIME_PERCENTILE.md
new file mode 100644
index 0000000000000000000000000000000000000000..56c7a4d5d7693cb8c72fd1795c7a6852bf68db02
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_RESPONSETIME_PERCENTILE.md
@@ -0,0 +1,17 @@
+---
+title: STATEMENT_RESPONSETIME_PERCENTILE
+summary: STATEMENT_RESPONSETIME_PERCENTILE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATEMENT_RESPONSETIME_PERCENTILE
+
+获取MogDB SQL响应时间P80，P95分布信息。
+
+**表 1** STATEMENT_RESPONSETIME_PERCENTILE的字段
+
+| **名称** | **类型** | **描述**                                 |
+| :------- | :------- | :--------------------------------------- |
+| p80      | bigint   | MogDB 80%的SQL的响应时间（单位: 微秒）。 |
+| p95      | bigint   | MogDB 95%的SQL的响应时间（单位: 微秒）。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_USER_COMPLEX_HISTORY.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_USER_COMPLEX_HISTORY.md
new file mode 100644
index 0000000000000000000000000000000000000000..52f9dcab4e73ed295190810cc3db5cd187def65b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_USER_COMPLEX_HISTORY.md
@@ -0,0 +1,10 @@
+---
+title: STATEMENT_USER_COMPLEX_HISTORY
+summary: STATEMENT_USER_COMPLEX_HISTORY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATEMENT_USER_COMPLEX_HISTORY
+
+STATEMENT_USER_COMPLEX_HISTORY系统表显示数据库主节点执行作业结束后的负载管理记录。此数据是从内核中转储到系统表中的数据。具体的字段请参考附录-表5。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_WLMSTAT_COMPLEX_RUNTIME.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_WLMSTAT_COMPLEX_RUNTIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..252dd10a7f925051034c5f4eee0db356c8788cf7
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/STATEMENT_WLMSTAT_COMPLEX_RUNTIME.md
@@ -0,0 +1,38 @@
+---
+title: STATEMENT_WLMSTAT_COMPLEX_RUNTIME
+summary: STATEMENT_WLMSTAT_COMPLEX_RUNTIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATEMENT_WLMSTAT_COMPLEX_RUNTIME
+
+STATEMENT_WLMSTAT_COMPLEX_RUNTIME视图显示和当前用户执行作业正在运行时的负载管理相关信息。
+
+**表 1** STATEMENT_WLMSTAT_COMPLEX_RUNTIME字段
+
+| 名称             | 类型    | 描述                                                         |
+| :--------------- | :------ | :----------------------------------------------------------- |
+| datid            | oid     | 连接后端的数据库OID。                                        |
+| datname          | name    | 连接后端的数据库名称。                                       |
+| threadid         | bigint  | 后端线程ID。                                                 |
+| processid        | integer | 后端线程的pid。                                              |
+| usesysid         | oid     | 登录后端的用户OID。                                          |
+| appname          | text    | 连接到后端的应用名。                                         |
+| usename          | name    | 登录到该后端的用户名。                                       |
+| priority         | bigint  | 语句所在Cgroups的优先级。                                    |
+| attribute        | text    | 语句的属性: <br/>- Ordinary: 语句发送到数据库后被解析前的默认属性。<br/>- Simple: 简单语句。<br/>- Complicated: 复杂语句。<br/>- Internal: 数据库内部语句。 |
+| block_time       | bigint  | 语句当前为止的pending的时间，单位s。                         |
+| elapsed_time     | bigint  | 语句当前为止的实际执行时间，单位s。                          |
+| total_cpu_time   | bigint  | 语句在上一时间周期内的数据库节点上CPU使用的总时间，单位s。   |
+| cpu_skew_percent | integer | 语句在上一时间周期内的数据库节点上CPU使用的倾斜率。          |
+| statement_mem    | integer | 语句执行使用的statement_mem，预留字段。                      |
+| active_points    | integer | 语句占用的资源池并发点数。                                   |
+| dop_value        | integer | 语句的从资源池中获取的dop值。                                |
+| control_group    | text    | 该字段不支持。                                               |
+| status           | text    | 该字段不支持。                                               |
+| enqueue          | text    | 语句当前的排队情况，包括: <br/>- Global: 在全局队列中排队。<br/>- Respool: 在资源池队列中排队。<br/>- CentralQueue: 在中心协调节点（CCN）中排队。<br/>- Transaction: 语句处于一个事务块中。<br/>- StoredProc: 句处于一个存储过程中。<br/>- None: 未在排队。<br/>- Forced None: 事务块语句或存储过程语句由于超出设定的等待时间而强制执行。 |
+| resource_pool    | name    | 语句当前所在的资源池。                                       |
+| query            | text    | 该后端的最新查询。如果state状态是active（活的），此字段显示当前正在执行的查询。所有其他情况表示上一个查询。 |
+| is_plana         | boolean | 逻辑MogDB模式下，语句当前是否占用其他逻辑MogDB的资源执行。该值默认为f（否）。 |
+| node_group       | text    | 语句所属用户对应的逻辑MogDB。                                |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/SUMMARY_STATEMENT.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/SUMMARY_STATEMENT.md
new file mode 100644
index 0000000000000000000000000000000000000000..af41aefb6a888124da9d72f989016f26cde1968d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/SUMMARY_STATEMENT.md
@@ -0,0 +1,56 @@
+---
+title: SUMMARY_STATEMENT
+summary: SUMMARY_STATEMENT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STATEMENT
+
+获得各数据库主节点的执行语句（归一化SQL）的全量信息（包含数据库节点）。
+
+**表 1** SUMMARY_STATEMENT字段
+
+| **名称**            | **类型**                 | **描述**                                             |
+| :------------------ | :----------------------- | :--------------------------------------------------- |
+| node_name           | name                     | 数据库进程名称。                                     |
+| node_id             | integer                  | 节点的ID。                                           |
+| user_name           | name                     | 用户名称。                                           |
+| user_id             | oid                      | 用户OID。                                            |
+| unique_sql_id       | bigint                   | 归一化的SQL ID。                                     |
+| query               | text                     | 归一化的SQL。                                        |
+| n_calls             | bigint                   | 调用次数。                                           |
+| min_elapse_time     | bigint                   | SQL在内核内的最小运行时间（单位: 微秒）。            |
+| max_elapse_time     | bigint                   | SQL在内核内的最大运行时间（单位: 微秒）。            |
+| total_elapse_time   | bigint                   | SQL在内核内的总运行时间（单位: 微秒）。              |
+| n_returned_rows     | bigint                   | SELECT返回的结果集行数。                             |
+| n_tuples_fetched    | bigint                   | 随机扫描行。                                         |
+| n_tuples_returned   | bigint                   | 顺序扫描行。                                         |
+| n_tuples_inserted   | bigint                   | 插入行。                                             |
+| n_tuples_updated    | bigint                   | 更新行。                                             |
+| n_tuples_deleted    | bigint                   | 删除行。                                             |
+| n_blocks_fetched    | bigint                   | buffer的块访问次数。                                 |
+| n_blocks_hit        | bigint                   | buffer的块命中次数。                                 |
+| n_soft_parse        | bigint                   | 软解析次数。                                         |
+| n_hard_parse        | bigint                   | 硬解析次数。                                         |
+| db_time             | bigint                   | 有效的DB时间花费，多线程将累加（单位: 微秒）。       |
+| cpu_time            | bigint                   | CPU时间（单位: 微秒）。                              |
+| execution_time      | bigint                   | 执行器内执行时间（单位: 微秒）。                     |
+| parse_time          | bigint                   | SQL解析时间（单位: 微秒）。                          |
+| plan_time           | bigint                   | SQL生成计划时间（单位: 微秒）。                      |
+| rewrite_time        | bigint                   | SQL重写时间（单位: 微秒）。                          |
+| pl_execution_time   | bigint                   | plpgsql上的执行时间（单位: 微秒）。                  |
+| pl_compilation_time | bigint                   | plpgsql上的编译时间（单位: 微秒）。                  |
+| net_send_time       | bigint                   | 网络上的时间花费（单位: 微秒）。                     |
+| data_io_time        | bigint                   | IO上的时间花费（单位: 微秒）。                       |
+| last_updated        | timestamp with time zone | 最后一次更新该语句的时间。                           |
+| sort_count          | bigint                   | 排序执行的次数。                                     |
+| sort_time           | bigint                   | 排序执行的时间（单位: 微秒）。                       |
+| sort_mem_used       | bigint                   | 排序过程中使用的work memory大小（单位: KB）。        |
+| sort_spill_count    | bigint                   | 排序过程中，若发生落盘，写文件的次数。               |
+| sort_spill_size     | bigint                   | 排序过程中，若发生落盘，使用的文件大小（单位: KB）。 |
+| hash_count          | bigint                   | hash执行的次数。                                     |
+| hash_time           | bigint                   | hash执行的时间（单位: 微秒）。                       |
+| hash_mem_used       | bigint                   | hash过程中使用的work memory大小（单位: KB）。        |
+| hash_spill_count    | bigint                   | hash过程中，若发生落盘，写文件的次数。               |
+| hash_spill_size     | bigint                   | hash过程中，若发生落盘，使用的文件大小（单位: KB）。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/SUMMARY_STATEMENT_COUNT.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/SUMMARY_STATEMENT_COUNT.md
new file mode 100644
index 0000000000000000000000000000000000000000..479fe21a8ebf1eff71c88f5df258a3d892f097ce
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/query/SUMMARY_STATEMENT_COUNT.md
@@ -0,0 +1,40 @@
+---
+title: SUMMARY_STATEMENT_COUNT
+summary: SUMMARY_STATEMENT_COUNT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_STATEMENT_COUNT
+
+显示数据库汇聚各节点（数据库节点）当前时刻执行的五类语句（SELECT、INSERT、UPDATE、DELETE、MERGE INTO）和（DDL、DML、DCL）统计信息。
+
+**表 1** SUMMARY_STATEMENT_COUNT字段
+
+| **名称**            | **类型** | **描述**                             |
+| :------------------ | :------- | :----------------------------------- |
+| user_name           | text     | 用户名。                             |
+| select_count        | numeric  | select语句统计结果。                 |
+| update_count        | numeric  | update语句统计结果。                 |
+| insert_count        | numeric  | insert语句统计结果。                 |
+| delete_count        | numeric  | delete语句统计结果。                 |
+| mergeinto_count     | numeric  | merge into语句统计结果。             |
+| ddl_count           | numeric  | DDL语句的数量。                      |
+| dml_count           | numeric  | DML语句的数量。                      |
+| dcl_count           | numeric  | DCL语句的数量。                      |
+| total_select_elapse | numeric  | 总select的时间花费（单位: 微秒）。   |
+| avg_select_elapse   | bigint   | 平均select的时间花费（单位: 微秒）。 |
+| max_select_elapse   | bigint   | 最大select的时间花费（单位: 微秒）。 |
+| min_select_elapse   | bigint   | 最小select的时间花费（单位: 微秒）。 |
+| total_update_elapse | numeric  | 总update的时间花费（单位: 微秒）。   |
+| avg_update_elapse   | bigint   | 平均update的时间花费（单位: 微秒）。 |
+| max_update_elapse   | bigint   | 最大update的时间花费（单位: 微秒）。 |
+| min_update_elapse   | bigint   | 最小update的时间花费（单位: 微秒）。 |
+| total_insert_elapse | numeric  | 总insert的时间花费（单位: 微秒）。   |
+| avg_insert_elapse   | bigint   | 平均insert的时间花费（单位: 微秒）。 |
+| max_insert_elapse   | bigint   | 最大insert的时间花费（单位: 微秒）。 |
+| min_insert_elapse   | bigint   | 最小insert的时间花费（单位: 微秒）。 |
+| total_delete_elapse | numeric  | 总delete的时间花费（单位: 微秒）。   |
+| avg_delete_elapse   | bigint   | 平均delete的时间花费（单位: 微秒）。 |
+| max_delete_elapse   | bigint   | 最大delete的时间花费（单位: 微秒）。 |
+| min_delete_elapse   | bigint   | 最小delete的时间花费（单位: 微秒）。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/rto/global_rto_status.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/rto/global_rto_status.md
new file mode 100644
index 0000000000000000000000000000000000000000..7947ee5281c8eee048c1e93d1add2706d86145eb
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/rto/global_rto_status.md
@@ -0,0 +1,17 @@
+---
+title: global_rto_status
+summary: global_rto_status
+author: Guo Huan
+date: 2021-11-15
+---
+
+# global_rto_status
+
+global_rto_status视图显示关于主机和备机的日志流控信息（本节点除外、备DN上不可使用）。
+
+**表 1** remote_rto_status参数说明
+
+| 参数      | 类型 | 描述                                                         |
+| :-------- | :--- | :----------------------------------------------------------- |
+| node_name | text | 节点的名称，包含主机和备机。                                 |
+| rto_info  | text | 流控的信息，包含了备机当前的日志流控时间（单位：秒），备机通过GUC参数设置的预期流控时间（单位：秒），为了达到这个预期主机所需要的睡眠时间（单位：微秒）。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_MEMORY.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_MEMORY.md
new file mode 100644
index 0000000000000000000000000000000000000000..9995aeccff510d6682bbb155ab94db8db7f4b80c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_MEMORY.md
@@ -0,0 +1,20 @@
+---
+title: GLOBAL_SESSION_MEMORY
+summary: GLOBAL_SESSION_MEMORY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_SESSION_MEMORY
+
+统计各节点的Session级别的内存使用情况，包含执行作业在数据节点上MogDB线程和Stream线程分配的所有内存，单位为MB。
+
+**表 1** GLOBAL_SESSION_MEMORY字段
+
+| **名称**  | **类型** | **描述**                                   |
+| :-------- | :------- | :----------------------------------------- |
+| node_name | name     | 数据库进程名称。                           |
+| sessid    | text     | 线程启动时间+线程标识。                    |
+| init_mem  | integer  | 当前正在执行作业进入执行器前已分配的内存。 |
+| used_mem  | integer  | 当前正在执行作业已分配的内存。             |
+| peak_mem  | integer  | 当前正在执行作业已分配的内存峰值。         |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_MEMORY_DETAIL.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_MEMORY_DETAIL.md
new file mode 100644
index 0000000000000000000000000000000000000000..c0d8e5c82a5f67400050abdd9b2e393198dd1852
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_MEMORY_DETAIL.md
@@ -0,0 +1,24 @@
+---
+title: GLOBAL_SESSION_MEMORY_DETAIL
+summary: GLOBAL_SESSION_MEMORY_DETAIL
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_SESSION_MEMORY_DETAIL
+
+统计各节点的线程的内存使用情况，以MemoryContext节点来统计。
+
+**表 1** GLOBAL_SESSION_MEMORY_DETAIL字段
+
+| **名称**    | **类型** | **描述**                       |
+| :---------- | :------- | :----------------------------- |
+| node_name   | name     | 数据库进程名称。               |
+| sessid      | text     | 线程启动时间+线程标识。        |
+| sesstype    | text     | 线程名称。                     |
+| contextname | text     | 内存上下文名称。               |
+| level       | smallint | 内存上下文的重要级别。         |
+| parent      | text     | 父级内存上下文名称。           |
+| totalsize   | bigint   | 总申请内存大小（单位: 字节）。 |
+| freesize    | bigint   | 空闲内存大小（单位: 字节）。   |
+| usedsize    | bigint   | 使用内存大小（单位: 字节）。   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_STAT.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_STAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..31c3e5ddea5a6329a7c7c83356e3fda5dd2614d0
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_STAT.md
@@ -0,0 +1,21 @@
+---
+title: GLOBAL_SESSION_STAT
+summary: GLOBAL_SESSION_STAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_SESSION_STAT
+
+各节点上以会话线程或AutoVacuum线程为单位，统计会话状态信息。
+
+**表 1** GLOBAL_SESSION_STAT字段
+
+| **名称**  | **类型** | **描述**                |
+| :-------- | :------- | :---------------------- |
+| node_name | name     | 数据库进程名称。        |
+| sessid    | text     | 线程启动时间+线程标识。 |
+| statid    | integer  | 统计编号。              |
+| statname  | text     | 统计会话名称。          |
+| statunit  | text     | 统计会话单位。          |
+| value     | bigint   | 统计会话值。            |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_STAT_ACTIVITY.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_STAT_ACTIVITY.md
new file mode 100644
index 0000000000000000000000000000000000000000..1b066a4a5714dc00d6be0e7ac83583e77761108f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_STAT_ACTIVITY.md
@@ -0,0 +1,35 @@
+---
+title: GLOBAL_SESSION_STAT_ACTIVITY
+summary: GLOBAL_SESSION_STAT_ACTIVITY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_SESSION_STAT_ACTIVITY
+
+显示MogDB内各节点上正在运行的线程相关的信息。
+
+**表 1** GLOBAL_SESSION_STAT_ACTIVITY字段
+
+| **名称**         | **类型**                | **描述**                                                     |
+| :--------------- | :---------------------- | :----------------------------------------------------------- |
+| coorname         | text                    | 数据库进程名称。                                             |
+| datid            | oid                     | 用户会话在后台连接到的数据库OID。                            |
+| datname          | text                    | 用户会话在后台连接到的数据库名称。                           |
+| pid              | bigint                  | 后台线程ID。                                                 |
+| usesysid         | oid                     | 登录该后台的用户OID。                                        |
+| usename          | text                    | 登录该后台的用户名。                                         |
+| application_name | text                    | 连接到该后台的应用名。                                       |
+| client_addr      | inet                    | 连接到该后台的客户端的IP地址。如果此字段是null，它表明通过服务器机器上UNIX套接字连接客户端或者这是内部进程，如autovacuum。 |
+| client_hostname  | text                    | 客户端的主机名，这个字段是通过client_addr的反向DNS查找得到。这个字段只有在启动log_hostname且使用IP连接时才非空。 |
+| client_port      | integer                 | 客户端用于与后台通讯的TCP端口号，如果使用Unix套接字，则为-1。 |
+| backend_start    | timestampwith time zone | 该过程开始的时间，即当客户端连接服务器时间。                 |
+| xact_start       | timestampwith time zone | 启动当前事务的时间，如果没有事务是活跃的，则为null。如果当前查询是首个事务，则这列等同于query_start列。 |
+| query_start      | timestampwith time zone | 开始当前活跃查询的时间，如果state的值不是active，则这个值是上一个查询的开始时间。 |
+| state_change     | timestampwith time zone | 上次状态改变的时间。                                         |
+| waiting          | boolean                 | 如果后台当前正等待锁则为true。                               |
+| enqueue          | text                    | 该字段不支持。                                               |
+| state            | text                    | 该后台当前总体状态。可能值是: <br/>- active: 后台正在执行一个查询。<br/>- idle: 后台正在等待一个新的客户端命令。<br/>- idle in transaction: 后台在事务中，但是目前无法执行查询。<br/>- idle in transaction (aborted): 这个状态除说明事务中有某个语句导致了错误外，类似于idle in transaction。<br/>- fastpath function call: 后台正在执行一个fast-path函数。<br/>- disabled: 如果后台禁用track_activities，则报告这个状态。<br/>说明:<br/>普通用户只能查看到自己帐户所对应的会话状态。即其他帐户的state信息为空。例如以judy用户连接数据库后，在pg_stat_activity中查看到的普通用户joe及初始用户omm的state信息为空。 <br/>mogdb=# SELECT datname, usename, usesysid,state,pid FROM pg_stat_activity;<br/>datname \| usename \| usesysid \| state \| pid<br/>----+---+----+---+------mogdb \| omm \| 10 \| \|139968752121616<br/>mogdb \| omm \| 10 \| \|139968903116560<br/>db_tpcds \| judy \| 16398 \| active \|139968391403280<br/>mogdb \| omm \| 10 \| \|139968643069712<br/>mogdb \| omm \| 10 \| \|139968680818448<br/>mogdb \| joe \| 16390 \| \|139968563377936<br/>(6 rows) |
+| resource_pool    | name                    | 用户使用的资源池。                                           |
+| query_id         | bigint                  | 查询语句的ID。                                               |
+| query            | text                    | 该后台的最新查询。如果state状态是active（活跃的），此字段显示当前正在执行的查询。所有其他情况表示上一个查询。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_TIME.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_TIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..137b80605506b98e4e1bc4f0c07128fee23fecfa
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_TIME.md
@@ -0,0 +1,20 @@
+---
+title: GLOBAL_SESSION_TIME
+summary: GLOBAL_SESSION_TIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_SESSION_TIME
+
+用于统计各节点会话线程的运行时间信息，及各执行阶段所消耗时间。
+
+**表 1** GLOBAL_SESSION_TIME字段
+
+| **名称**  | **类型** | **描述**                |
+| :-------- | :------- | :---------------------- |
+| node_name | name     | 数据库进程名称。        |
+| sessid    | text     | 线程启动时间+线程标识。 |
+| stat_id   | integer  | 统计编号。              |
+| stat_name | text     | 会话类型名称。          |
+| value     | bigint   | 会话值。                |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_THREADPOOL_STATUS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_THREADPOOL_STATUS.md
new file mode 100644
index 0000000000000000000000000000000000000000..5a7f1fedaf648e37a7c1f1baf4312158e93c0c12
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_THREADPOOL_STATUS.md
@@ -0,0 +1,10 @@
+---
+title: GLOBAL_THREADPOOL_STATUS
+summary: GLOBAL_THREADPOOL_STATUS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_THREADPOOL_STATUS
+
+GLOBAL_THREADPOOL_STATUS视图显示在所有节点上的线程池中工作线程及会话的状态信息。具体的字段参见LOCAL_THREADPOOL_STATUS -&gt; 表1。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_THREAD_WAIT_STATUS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_THREAD_WAIT_STATUS.md
new file mode 100644
index 0000000000000000000000000000000000000000..599560115322b6887f34186e37a30dca0a385a38
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_THREAD_WAIT_STATUS.md
@@ -0,0 +1,31 @@
+---
+title: GLOBAL_THREAD_WAIT_STATUS
+summary: GLOBAL_THREAD_WAIT_STATUS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_THREAD_WAIT_STATUS
+
+通过该视图可以检测所有节点上工作线程（backend thread）以及辅助线程（auxiliary thread）的阻塞等待情况。具体事件信息请参见附录-表1 等待状态列表、附录-表2 轻量级锁等待事件列表、附录-表3 IO等待事件列表和附录-表4 事务锁等待事件列表。
+
+通过GLOBAL_THREAD_WAIT_STATUS视图，可以查看MogDB全局各个节点上所有SQL语句产生的线程之间的调用层次关系，以及各个线程的阻塞等待状态，从而更容易定位hang以及类似现象的原因。
+
+GLOBAL_THREAD_WAIT_STATUS视图和THREAD_WAIT_STATUS视图列定义完全相同，这是由于GLOBAL_THREAD_WAIT_STATUS视图本质是到MogDB中各个节点上查询THREAD_WAIT_STATUS视图汇总的结果。
+
+**表 1** GLOBAL_THREAD_WAIT_STATUS字段
+
+| **名称**    | **类型** | **描述**                                                     |
+| :---------- | :------- | :----------------------------------------------------------- |
+| node_name   | text     | 数据库进程名称。                                             |
+| db_name     | text     | 数据库名称。                                                 |
+| thread_name | text     | 线程名称。                                                   |
+| query_id    | bigint   | 查询ID，对应debug_query_id。                                 |
+| tid         | bigint   | 当前线程的线程号。                                           |
+| sessionid   | bigint   | session的ID。                                                |
+| lwtid       | integer  | 当前线程的轻量级线程号。                                     |
+| psessionid  | bigint   | streaming线程的父线程。                                      |
+| tlevel      | integer  | streaming线程的层级。                                        |
+| smpid       | integer  | 并行线程的ID。                                               |
+| wait_status | text     | 当前线程的等待状态。等待状态的详细信息请参见附录-表1 等待状态列表。 |
+| wait_event  | text     | 如果wait_status是acquire lock、acquire lwlock、wait io三种类型，此列描述具体的锁、轻量级锁、IO的信息。否则是空。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/LOCAL_ACTIVE_SESSION.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/LOCAL_ACTIVE_SESSION.md
new file mode 100644
index 0000000000000000000000000000000000000000..e27c67c5bb7f60cfc6d4d30ef98874127ba01b2c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/LOCAL_ACTIVE_SESSION.md
@@ -0,0 +1,43 @@
+---
+title: LOCAL_ACTIVE_SESSION
+summary: LOCAL_ACTIVE_SESSION
+author: Guo Huan
+date: 2021-11-15
+---
+
+# LOCAL_ACTIVE_SESSION
+
+LOCAL_ACTIVE_SESSION视图显示本节点上的ACTIVE SESSION PROFILE内存中的样本。
+
+**表 1** LOCAL_ACTIVE_SESSION字段
+
+| 名称                  | 类型                     | 描述          |
+| :--------------- | :----------------- | :----------------------|
+| sampleid              | bigint                   | 采样ID。                                                     |
+| sample_time           | timestamp with time zone | 采样的时间。                                                 |
+| need_flush_sample     | boolean                  | 该样本是否需要刷新的磁盘。                                   |
+| databaseid            | oid                      | 数据库ID。                                                   |
+| thread_id             | bigint                   | 线程的ID。                                                   |
+| sessionid             | bigint                   | 会话的ID。                                                   |
+| start_time            | timestamp with time zone | 会话的启动时间。                                             |
+| event                 | text                     | 具体的事件名称。                                             |
+| lwtid                 | integer                  | 当前线程的轻量级线程号。                                     |
+| psessionid            | bigint                   | streaming线程的父线程。                                      |
+| tlevel                | integer                  | streaming线程的层级。与执行计划的层级（ID）相对应。          |
+| smpid                 | integer                  | smp执行模式下并行线程的并行编号。                            |
+| userid                | oid                      | session用户的ID。                                            |
+| application_name      | text                     | 应用的名称。                                                 |
+| client_addr           | inet                     | client端的地址。                                             |
+| client_hostname       | text                     | client端的名称。                                             |
+| client_port           | integer                  | 客户端用于与后端通讯的TCP端口号。                            |
+| query_id              | bigint                   | debug query id。                                             |
+| unique_query_id       | bigint                   | unique query id。                                            |
+| user_id               | oid                      | unique query的key中的user_id。                               |
+| cn_id                 | integer                  | cn id，在DN上表示下发该unique sql的节点id，unique query的key中的cn_id。 |
+| unique_query          | text                     | 规范化后的UniqueSQL文本串。                                  |
+| locktag               | text                     | 会话等待锁信息，可通过locktag_decode解析。                   |
+| lockmode              | text                     | 会话等待锁模式。                                             |
+| block_sessionid       | bigint                   | 如果会话正在等待锁，阻塞该会话获取锁的会话标识。             |
+| final_block_sessionid | bigint                   | 表示源头阻塞会话ID。                                         |
+| wait_status           | text                     | 描述event列的更多详细信息。                                  |
+| global_sessionid      | text                     | 全局会话ID。                                                 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/LOCAL_THREADPOOL_STATUS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/LOCAL_THREADPOOL_STATUS.md
new file mode 100644
index 0000000000000000000000000000000000000000..96991973aeeca02a018bd7c345d450bdd89b20ad
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/LOCAL_THREADPOOL_STATUS.md
@@ -0,0 +1,22 @@
+---
+title: LOCAL_THREADPOOL_STATUS
+summary: LOCAL_THREADPOOL_STATUS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# LOCAL_THREADPOOL_STATUS
+
+LOCAL_THREADPOOL_STATUS视图显示线程池下工作线程及会话的状态信息。该视图仅在线程池开启（enable_thread_pool = on）时生效。
+
+**表 1** LOCAL_THREADPOOL_STATUS字段<a id="LOCAL_THREADPOOL_STATUS字段"> </a>
+
+| 名称            | 类型    | 描述                                                         |
+| :-------------- | :------ | :----------------------------------------------------------- |
+| node_name       | text    | 数据库进程名称。                                             |
+| group_id        | integer | 线程池组ID。                                                 |
+| bind_numa_id    | integer | 该线程池组绑定的NUMA ID。                                    |
+| bind_cpu_number | integer | 该线程池组绑定的CPU信息。如果未绑定CPU，该值为NULL。         |
+| listener        | integer | 该线程池组的Listener线程数量。                               |
+| worker_info     | text    | 线程池中线程相关信息，包括以下信息: <br/>- default: 该线程池组中的初始线程数量。<br/>- new: 该线程池组中新增线程的数量。<br/>- expect: 该线程池组中预期线程的数量。<br/>- actual: 该线程池组中实际线程的数量。<br/>- idle: 该线程池组中空闲线程的数量。<br/>- pending: 该线程池组中等待线程的数量。 |
+| session_info    | text    | 线程池中会话相关信息，包括以下信息: <br/>- total: 该线程池组中所有的会话数量。<br/>- waiting: 该线程池组中等待调度的会话数量。<br/>- running: 该线程池中正在执行的会话数量。<br/>- idle: 该线程池组中空闲的会话数量。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_CPU_RUNTIME.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_CPU_RUNTIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..5e560335c70631b915cff9f7a8eedb33baf73ac5
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_CPU_RUNTIME.md
@@ -0,0 +1,25 @@
+---
+title: SESSION_CPU_RUNTIME
+summary: SESSION_CPU_RUNTIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SESSION_CPU_RUNTIME
+
+SESSION_CPU_RUNTIME视图显示和当前用户执行复杂作业（正在运行）时的负载管理CPU使用的信息。
+
+**表 1** SESSION_CPU_RUNTIME字段
+
+| 名称           | 类型                     | 描述                                        |
+| :------------- | :----------------------- | :------------------------------------------ |
+| datid          | oid                      | 连接后端的数据库OID。                       |
+| usename        | name                     | 登录到该后端的用户名。                      |
+| pid            | bigint                   | 后端线程ID。                                |
+| start_time     | timestamp with time zone | 语句执行的开始时间。                        |
+| min_cpu_time   | bigint                   | 语句在数据库节点上的最小CPU时间，单位为ms。 |
+| max_cpu_time   | bigint                   | 语句在数据库节点上的最大CPU时间，单位为ms。 |
+| total_cpu_time | bigint                   | 语句在数据库节点上的CPU总时间，单位为ms。   |
+| query          | text                     | 正在执行的语句。                            |
+| node_group     | text                     | 语句所属用户对应的逻辑MogDB。               |
+| top_cpu_dn     | text                     | cpu使用量topN信息。                         |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_MEMORY.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_MEMORY.md
new file mode 100644
index 0000000000000000000000000000000000000000..309b9cfd73574ff4ea8624a4e707e8c917795860
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_MEMORY.md
@@ -0,0 +1,19 @@
+---
+title: SESSION_MEMORY
+summary: SESSION_MEMORY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SESSION_MEMORY
+
+统计Session级别的内存使用情况，包含执行作业在数据节点上MogDB线程和Stream线程分配的所有内存，单位为MB。
+
+**表 1** SESSION_MEMORY字段
+
+| **名称** | **类型** | **描述**                                   |
+| :------- | :------- | :----------------------------------------- |
+| sessid   | text     | 线程启动时间+线程标识。                    |
+| init_mem | integer  | 当前正在执行作业进入执行器前已分配的内存。 |
+| used_mem | integer  | 当前正在执行作业已分配的内存。             |
+| peak_mem | integer  | 当前正在执行作业已分配的内存峰值。         |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_MEMORY_DETAIL.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_MEMORY_DETAIL.md
new file mode 100644
index 0000000000000000000000000000000000000000..f76165fcaa8f66ae566cf599b3fd4c44aa0c161d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_MEMORY_DETAIL.md
@@ -0,0 +1,23 @@
+---
+title: SESSION_MEMORY_DETAIL
+summary: SESSION_MEMORY_DETAIL
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SESSION_MEMORY_DETAIL
+
+统计线程的内存使用情况，以MemoryContext节点来统计。
+
+**表 1** SESSION_MEMORY_DETAIL字段
+
+| **名称**    | **类型** | **描述**                       |
+| :---------- | :------- | :----------------------------- |
+| sessid      | text     | 线程启动时间+线程标识。        |
+| sesstype    | text     | 线程名称。                     |
+| contextname | text     | 内存上下文名称。               |
+| level       | smallint | 内存上下文的重要级别。         |
+| parent      | text     | 父级内存上下文名称。           |
+| totalsize   | bigint   | 总申请内存大小（单位: 字节）。 |
+| freesize    | bigint   | 空闲内存大小（单位: 字节）。   |
+| usedsize    | bigint   | 使用内存大小（单位: 字节）。   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_MEMORY_RUNTIME.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_MEMORY_RUNTIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..95de0c7ae0b3fd258091f7b1afb79595f4da9160
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_MEMORY_RUNTIME.md
@@ -0,0 +1,25 @@
+---
+title: SESSION_MEMORY_RUNTIME
+summary: SESSION_MEMORY_RUNTIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SESSION_MEMORY_RUNTIME
+
+SESSION_MEMORY_RUNTIME视图显示和当前用户执行复杂作业正在运行时的负载管理内存使用的信息。
+
+**表 1** SESSION_MEMORY_RUNTIME字段
+
+| 名称            | 类型                     | 描述                                                         |
+| :-------------- | :----------------------- | :----------------------------------------------------------- |
+| datid           | oid                      | 连接后端的数据库OID。                                        |
+| usename         | name                     | 登录到该后端的用户名。                                       |
+| pid             | bigint                   | 后端线程ID。                                                 |
+| start_time      | timestamp with time zone | 语句执行的开始时间。                                         |
+| min_peak_memory | integer                  | 语句在数据库节点上的最小内存峰值大小，单位MB。               |
+| max_peak_memory | integer                  | 语句在数据库节点上的最大内存峰值大小，单位MB。               |
+| spill_info      | text                     | 语句在数据库节点上的下盘信息：<br/>- None: 数据库节点均未下盘。<br/>- All: 数据库节点均下盘。<br/>- [a:b]: 数量为b个数据库节点中有a个数据库节点下盘。 |
+| query           | text                     | 正在执行的语句。                                             |
+| node_group      | text                     | 语句所属用户对应的逻辑MogDB。                                |
+| top_mem_dn      | text                     | mem使用量topN信息。                                          |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_STAT.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_STAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..dac3217e76c0915711bd677395d4b4fe1c6cf225
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_STAT.md
@@ -0,0 +1,20 @@
+---
+title: SESSION_STAT
+summary: SESSION_STAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SESSION_STAT
+
+当前节点以会话线程或AutoVacuum线程为单位，统计会话状态信息。
+
+**表 1** SESSION_STAT字段
+
+| **名称** | **类型** | **描述**                |
+| :------- | :------- | :---------------------- |
+| sessid   | text     | 线程启动时间+线程标识。 |
+| statid   | integer  | 统计编号。              |
+| statname | text     | 统计会话名称。          |
+| statunit | text     | 统计会话单位。          |
+| value    | bigint   | 统计会话值。            |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_STAT_ACTIVITY.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_STAT_ACTIVITY.md
new file mode 100644
index 0000000000000000000000000000000000000000..a5f0a4a84498218ab0dcb6dfd223356be8c6d445
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_STAT_ACTIVITY.md
@@ -0,0 +1,34 @@
+---
+title: SESSION_STAT_ACTIVITY
+summary: SESSION_STAT_ACTIVITY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SESSION_STAT_ACTIVITY
+
+显示当前节点上正在运行的线程相关的信息。
+
+**表 1** SESSION_STAT_ACTIVITY字段
+
+| **名称**         | **类型**                | **描述**                                                     |
+| :--------------- | :---------------------- | :----------------------------------------------------------- |
+| datid            | oid                     | 用户会话在后台连接到的数据库OID。                            |
+| datname          | name                    | 用户会话在后台连接到的数据库名称。                           |
+| pid              | bigint                  | 后台线程ID。                                                 |
+| usesysid         | oid                     | 登录该后台的用户OID。                                        |
+| usename          | name                    | 登录该后台的用户名。                                         |
+| application_name | text                    | 连接到该后台的应用名。                                       |
+| client_addr      | inet                    | 连接到该后台的客户端的IP地址。如果此字段是null，它表明通过服务器机器上UNIX套接字连接客户端或者这是内部进程，如autovacuum。 |
+| client_hostname  | text                    | 客户端的主机名，这个字段是通过client_addr的反向DNS查找得到。这个字段只有在启动log_hostname且使用IP连接时才非空。 |
+| client_port      | integer                 | 客户端用于与后台通讯的TCP端口号，如果使用Unix套接字，则为-1。 |
+| backend_start    | timestampwith time zone | 该过程开始的时间，即当客户端连接服务器时间。                 |
+| xact_start       | timestampwith time zone | 启动当前事务的时间，如果没有事务是活跃的，则为null。如果当前查询是首个事务，则这列等同于query_start列。 |
+| query_start      | timestampwith time zone | 开始当前活跃查询的时间，如果state的值不是active，则这个值是上一个查询的开始时间。 |
+| state_change     | timestampwith time zone | 上次状态改变的时间。                                         |
+| waiting          | boolean                 | 如果后台当前正等待锁则为true。                               |
+| enqueue          | text                    | 该字段不支持。                                               |
+| state            | text                    | 该后台当前总体状态。可能值是: <br/>- active: 后台正在执行一个查询。<br/>- idle: 后台正在等待一个新的客户端命令。<br/>- idle in transaction: 后台在事务中，但是目前无法执行查询。<br/>- idle in transaction (aborted): 这个状态除说明事务中有某个语句导致了错误外，类似于idle in transaction。<br/>- fastpath function call: 后台正在执行一个fast-path函数。<br/>- disabled: 如果后台禁用track_activities，则报告这个状态。<br/>说明:<br/>普通用户只能查看到自己帐户所对应的会话状态。即其他帐户的state信息为空。例如以judy用户连接数据库后，在pg_stat_activity中查看到的普通用户joe及初始用户omm的state信息为空: <br/>mogdb=# SELECT datname, usename, usesysid,state,pid FROM pg_stat_activity;<br/>datname \| usename \| usesysid \| state \| pid<br/>----+---+----+---+------postgres \| omm \| 10 \| \|139968752121616<br/>postgres \| omm \| 10 \| \|139968903116560<br/>db_tpcds \| judy \| 16398 \| active \|139968391403280<br/>postgres \| omm \| 10 \| \|139968643069712<br/>postgres \| omm \| 10 \| \|139968680818448<br/>postgres \| joe \| 16390 \| \|139968563377936<br/>(6 rows) |
+| resource_pool    | name                    | 用户使用的资源池。                                           |
+| query_id         | bigint                  | 查询语句的ID。                                               |
+| query            | text                    | 该后台的最新查询。如果state状态是active（活跃的），此字段显示当前正在执行的查询。所有其他情况表示上一个查询。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_TIME.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_TIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..0da65f191b01d036c3d1640d2d342b8ed27de913
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/SESSION_TIME.md
@@ -0,0 +1,19 @@
+---
+title: SESSION_TIME
+summary: SESSION_TIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SESSION_TIME
+
+用于统计当前节点会话线程的运行时间信息，及各执行阶段所消耗时间。
+
+**表 1** SESSION_TIME字段
+
+| **名称**  | **类型** | **描述**                |
+| :-------- | :------- | :---------------------- |
+| sessid    | text     | 线程启动时间+线程标识。 |
+| stat_id   | integer  | 统计编号。              |
+| stat_name | text     | 会话类型名称。          |
+| value     | bigint   | 会话值。                |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/STATEMENT_IOSTAT_COMPLEX_RUNTIME.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/STATEMENT_IOSTAT_COMPLEX_RUNTIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..44357525687840ec2b11ea69a85b0f74a0f83334
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/STATEMENT_IOSTAT_COMPLEX_RUNTIME.md
@@ -0,0 +1,24 @@
+---
+title: STATEMENT_IOSTAT_COMPLEX_RUNTIME
+summary: STATEMENT_IOSTAT_COMPLEX_RUNTIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATEMENT_IOSTAT_COMPLEX_RUNTIME
+
+STATEMENT_IOSTAT_COMPLEX_RUNTIME视图显示当前用户执行作业正在运行时的IO负载管理相关信息。以下涉及到iops，对于行存，均以万次/s为单位，对于列存，均以次/s为单位。
+
+**表 1** STATEMENT_IOSTAT_COMPLEX_RUNTIME字段
+
+| 名称        | 类型    | 描述                                               |
+| :---------- | :------ | :------------------------------------------------- |
+| query_id    | bigint  | 作业id。                                           |
+| mincurriops | integer | 该作业当前io在各数据库节点中的最小值。             |
+| maxcurriops | integer | 该作业当前io在各数据库节点中的最大值。             |
+| minpeakiops | integer | 在作业运行时，作业io峰值中，各数据库节点的最小值。 |
+| maxpeakiops | integer | 在作业运行时，作业io峰值中，各数据库节点的最大值。 |
+| io_limits   | integer | 该作业所设GUC参数io_limits。                       |
+| io_priority | text    | 该作业所设GUC参数io_priority。                     |
+| query       | text    | 作业。                                             |
+| node_group  | text    | 作业所属用户对应的逻辑MogDB。                      |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/THREAD_WAIT_STATUS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/THREAD_WAIT_STATUS.md
new file mode 100644
index 0000000000000000000000000000000000000000..b16a85aea0e772a35c4a7a47b76497e2e2c5a848
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/session-thread/THREAD_WAIT_STATUS.md
@@ -0,0 +1,27 @@
+---
+title: THREAD_WAIT_STATUS
+summary: THREAD_WAIT_STATUS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# THREAD_WAIT_STATUS
+
+通过该视图可以检测当前实例中工作线程（backend thread）以及辅助线程（auxiliary thread）的阻塞等待情况，具体事件信息请参见附录-[表1](table-1) 等待状态列表、附录-[表2](table-2) 轻量级锁等待事件列表、附录-[表3](table-3) IO等待事件列表和附录-[表4](table-4) 事务锁等待事件列表。
+
+**表 1** THREAD_WAIT_STATUS字段
+
+| **名称**    | **类型** | **描述**                                                     |
+| :---------- | :------- | :----------------------------------------------------------- |
+| node_name   | text     | 数据库进程名称。                                             |
+| db_name     | text     | 数据库名称。                                                 |
+| thread_name | text     | 线程名称。                                                   |
+| query_id    | bigint   | 查询ID，对应debug_query_id。                                 |
+| tid         | bigint   | 当前线程的线程号。                                           |
+| sessionid   | bigint   | session的ID。                                                |
+| lwtid       | integer  | 当前线程的轻量级线程号。                                     |
+| psessionid  | bigint   | streaming线程的父线程。                                      |
+| tlevel      | integer  | streaming线程的层级。                                        |
+| smpid       | integer  | 并行线程的ID。                                               |
+| wait_status | text     | 当前线程的等待状态。等待状态的详细信息请参见附录-[表1](table-1) 等待状态列表。 |
+| wait_event  | text     | 如果wait_status是acquire lock、acquire lwlock、wait io三种类型，此列描述具体的锁、轻量级锁、IO的信息。否则为空。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/GLOBAL_TRANSACTIONS_PREPARED_XACTS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/GLOBAL_TRANSACTIONS_PREPARED_XACTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..c2b16fa918d97e6c8315da0b56a0b192477e05b5
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/GLOBAL_TRANSACTIONS_PREPARED_XACTS.md
@@ -0,0 +1,20 @@
+---
+title: GLOBAL_TRANSACTIONS_PREPARED_XACTS
+summary: GLOBAL_TRANSACTIONS_PREPARED_XACTS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_TRANSACTIONS_PREPARED_XACTS
+
+显示各节点当前准备好进行两阶段提交的事务的信息。
+
+**表 1** GLOBAL_TRANSACTIONS_PREPARED_XACTS字段
+
+| **名称**    | **类型**                 | **描述**                   |
+| :---------- | :----------------------- | :------------------------- |
+| transaction | xid                      | 预备事务的数字事务标识。   |
+| gid         | text                     | 赋予该事务的全局事务标识。 |
+| prepared    | timestamp with time zone | 事务准备好提交的时间。     |
+| owner       | name                     | 执行该事务的用户的名称。   |
+| database    | name                     | 执行该事务所在的数据库名。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/GLOBAL_TRANSACTIONS_RUNNING_XACTS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/GLOBAL_TRANSACTIONS_RUNNING_XACTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..3781402793a2c2e26d62ca0b36b9ace709c74377
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/GLOBAL_TRANSACTIONS_RUNNING_XACTS.md
@@ -0,0 +1,25 @@
+---
+title: GLOBAL_TRANSACTIONS_RUNNING_XACTS
+summary: GLOBAL_TRANSACTIONS_RUNNING_XACTS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_TRANSACTIONS_RUNNING_XACTS
+
+显示集群中各个节点运行事务的信息。
+
+**表 1** GLOBAL_TRANSACTIONS_RUNNING_XACTS字段
+
+| **名称**    | **类型** | **描述**                                                  |
+| :---------- | :------- | :-------------------------------------------------------- |
+| handle      | integer  | 事务在GTM对应的句柄。                                     |
+| gxid        | xid      | 事务id号。                                                |
+| state       | tinyint  | 事务状态（3：prepared或者0：starting）。                  |
+| node        | text     | 节点名称。                                                |
+| xmin        | xid      | 节点上当前数据涉及的最小事务号xmin。                      |
+| vacuum      | boolean  | 标志当前事务是否是lazy vacuum事务。                       |
+| timeline    | bigint   | 标志数据库重启次数。                                      |
+| prepare_xid | xid      | 处于prepared状态的事务的id号，若不在prepared状态，值为0。 |
+| pid         | bigint   | 事务对应的线程id。                                        |
+| next_xid    | xid      | CN传给DN的事务id号。                                      |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/SUMMARY_TRANSACTIONS_PREPARED_XACTS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/SUMMARY_TRANSACTIONS_PREPARED_XACTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..86e8cc0d262feb597f3004add9c15289955cee4f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/SUMMARY_TRANSACTIONS_PREPARED_XACTS.md
@@ -0,0 +1,20 @@
+---
+title: SUMMARY_TRANSACTIONS_PREPARED_XACTS
+summary: SUMMARY_TRANSACTIONS_PREPARED_XACTS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_TRANSACTIONS_PREPARED_XACTS
+
+显示MogDB中数据库主节点当前准备好进行两阶段提交的事务的信息。
+
+**表 1** SUMMARY_TRANSACTIONS_PREPARED_XACTS字段
+
+| **名称**    | **类型**                 | **描述**                   |
+| :---------- | :----------------------- | :------------------------- |
+| transaction | xid                      | 预备事务的数字事务标识。   |
+| gid         | text                     | 赋予该事务的全局事务标识。 |
+| prepared    | timestamp with time zone | 事务准备好提交的时间。     |
+| owner       | name                     | 执行该事务的用户的名称。   |
+| database    | name                     | 执行该事务所在的数据库名。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/SUMMARY_TRANSACTIONS_RUNNING_XACTS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/SUMMARY_TRANSACTIONS_RUNNING_XACTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..60c36289fe234b7ac6a100b7a1b9f7b214f3285c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/SUMMARY_TRANSACTIONS_RUNNING_XACTS.md
@@ -0,0 +1,25 @@
+---
+title: SUMMARY_TRANSACTIONS_RUNNING_XACTS
+summary: SUMMARY_TRANSACTIONS_RUNNING_XACTS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_TRANSACTIONS_RUNNING_XACTS
+
+显示集群中各个节点运行事务的信息，字段内容和transactions_running_xacts一致。
+
+**表 1** SUMMARY_TRANSACTIONS_RUNNING_XACTS字段
+
+| **名称**    | **类型** | **描述**                                                  |
+| :---------- | :------- | :-------------------------------------------------------- |
+| handle      | integer  | 事务在GTM对应的句柄。                                     |
+| gxid        | xid      | 事务id号。                                                |
+| state       | tinyint  | 事务状态（3：prepared或者0：starting）。                  |
+| node        | text     | 节点名称。                                                |
+| xmin        | xid      | 节点上当前数据涉及的最小事务号xmin。                      |
+| vacuum      | boolean  | 标志当前事务是否是lazy vacuum事务。                       |
+| timeline    | bigint   | 标志数据库重启次数。                                      |
+| prepare_xid | xid      | 处于prepared状态的事务的id号，若不在prepared状态，值为0。 |
+| pid         | bigint   | 事务对应的线程id。                                        |
+| next_xid    | xid      | CN传给DN的事务id号。                                      |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/TRANSACTIONS_PREPARED_XACTS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/TRANSACTIONS_PREPARED_XACTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..d3291c3900df6cec86c486369153ef86f1ec37af
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/TRANSACTIONS_PREPARED_XACTS.md
@@ -0,0 +1,20 @@
+---
+title: TRANSACTIONS_PREPARED_XACTS
+summary: TRANSACTIONS_PREPARED_XACTS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# TRANSACTIONS_PREPARED_XACTS
+
+显示当前准备好进行两阶段提交的事务的信息。
+
+**表 1** TRANSACTIONS_PREPARED_XACTS字段
+
+| **名称**    | **类型**                 | **描述**                   |
+| :---------- | :----------------------- | :------------------------- |
+| transaction | xid                      | 预备事务的数字事务标识。   |
+| gid         | text                     | 赋予该事务的全局事务标识。 |
+| prepared    | timestamp with time zone | 事务准备好提交的时间。     |
+| owner       | name                     | 执行该事务的用户的名称。   |
+| database    | name                     | 执行该事务所在的数据库名。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/TRANSACTIONS_RUNNING_XACTS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/TRANSACTIONS_RUNNING_XACTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..326ba42a8b0ed6fd816792c2cbdb0cd62f48cbc3
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/transaction/TRANSACTIONS_RUNNING_XACTS.md
@@ -0,0 +1,25 @@
+---
+title: TRANSACTIONS_RUNNING_XACTS
+summary: TRANSACTIONS_RUNNING_XACTS
+author: Guo Huan
+date: 2021-11-15
+---
+
+# TRANSACTIONS_RUNNING_XACTS
+
+显示当前节点运行事务的信息。
+
+**表 1** TRANSACTIONS_RUNNING_XACTS字段
+
+| **名称**    | **类型** | **描述**                                                  |
+| :---------- | :------- | :-------------------------------------------------------- |
+| handle      | integer  | 事务在GTM对应的句柄。                                     |
+| gxid        | xid      | 事务id号。                                                |
+| state       | tinyint  | 事务状态（3：prepared或者0：starting）。                  |
+| node        | text     | 节点名称。                                                |
+| xmin        | xid      | 节点上当前数据涉及的最小事务号xmin。                      |
+| vacuum      | boolean  | 标志当前事务是否是lazy vacuum事务。                       |
+| timeline    | bigint   | 标志数据库重启次数。                                      |
+| prepare_xid | xid      | 处于prepared状态的事务的id号，若不在prepared状态，值为0。 |
+| pid         | bigint   | 事务对应的线程id。                                        |
+| next_xid    | xid      | CN传给DN的事务id号。                                      |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/BGWRITER_STAT.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/BGWRITER_STAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..2cfd3e4e8cb39f802a3c2dfc33d90d24a4836d12
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/BGWRITER_STAT.md
@@ -0,0 +1,26 @@
+---
+title: BGWRITER_STAT
+summary: BGWRITER_STAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# BGWRITER_STAT
+
+BGWRITER_STAT视图显示关于后端写进程活动的统计信息。
+
+**表 1** BGWRITER_STAT字段
+
+| **名称**              | **类型**                 | **描述**             |
+| :-------------------- | :----------------------- | :----------------------------- |
+| checkpoints_timed     | bigint                   | 执行的定期检查点数。                                         |
+| checkpoints_req       | bigint                   | 执行的需求检查点数。                                         |
+| checkpoint_write_time | double precision         | 花费在检查点处理部分的时间总量，其中文件被写入到磁盘，以毫秒为单位。 |
+| checkpoint_sync_time  | double precision         | 花费在检查点处理部分的时间总量，其中文件被同步到磁盘，以毫秒为单位。 |
+| buffers_checkpoint    | bigint                   | 检查点写缓冲区数量。                                         |
+| buffers_clean         | bigint                   | 后端写进程写缓冲区数量。                                     |
+| maxwritten_clean      | bigint                   | 后端写进程停止清理扫描时间数，因为它写了太多缓冲区。         |
+| buffers_backend       | bigint                   | 通过后端直接写缓冲区数。                                     |
+| buffers_backend_fsync | bigint                   | 后端不得不执行自己的fsync调用的时间数（通常后端写进程处理这些即使后端确实自己写）。 |
+| buffers_alloc         | bigint                   | 分配的缓冲区数量。                                           |
+| stats_reset           | timestamp with time zone | 这些统计被重置的时间。                                       |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/CLASS_VITAL_INFO.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/CLASS_VITAL_INFO.md
new file mode 100644
index 0000000000000000000000000000000000000000..05f723ca04dfac31712581201d082251041c07cc
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/CLASS_VITAL_INFO.md
@@ -0,0 +1,19 @@
+---
+title: CLASS_VITAL_INFO
+summary: CLASS_VITAL_INFO
+author: Guo Huan
+date: 2021-04-19
+---
+
+# CLASS_VITAL_INFO
+
+CLASS_VITAL_INFO视图用于做WDR时校验相同的表或者索引的oid是否一致。
+
+**表 1** CLASS_VITAL_INFO字段
+
+| 名称       | 类型   | 描述                                                         |
+| :--------- | :----- | :----------------------------------------------------------- |
+| relid      | oid    | 表的oid。                                                    |
+| schemaname | name   | schema名称。                                                 |
+| relname    | name   | 表名。                                                       |
+| relkind    | "char" | 表示对象类型，取值范围如下: <br/>- r: 表示普通表。<br/>- t: 表示toast表。<br/>- i: 表示索引。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_BGWRITER_STAT.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_BGWRITER_STAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..0429c8dbe04e587be5e75a38094e843f9d3b3f2a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_BGWRITER_STAT.md
@@ -0,0 +1,27 @@
+---
+title: GLOBAL_BGWRITER_STAT
+summary: GLOBAL_BGWRITER_STAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_BGWRITER_STAT
+
+GLOBAL_BGWRITER_STAT视图显示各节点关于后端写进程活动的统计信息。
+
+**表 1** GLOBAL_BGWRITER_STAT字段
+
+| **名称**              | **类型**                 | **描述**                         |
+| :-------------------- | :----------------------- | :--------------------------------|
+| node_name             | name                     | 数据库进程名称。                                             |
+| checkpoints_timed     | bigint                   | 执行的定期检查点数。                                         |
+| checkpoints_req       | bigint                   | 执行的需求检查点数。                                         |
+| checkpoint_write_time | double precision         | 花费在检查点处理部分的时间总量，其中文件被写入到磁盘，以毫秒为单位。 |
+| checkpoint_sync_time  | double precision         | 花费在检查点处理部分的时间总量，其中文件被同步到磁盘，以毫秒为单位。 |
+| buffers_checkpoint    | bigint                   | 检查点写缓冲区数量。                                         |
+| buffers_clean         | bigint                   | 后端写进程写缓冲区数量。                                     |
+| maxwritten_clean      | bigint                   | 后端写进程停止清理扫描时间数，因为它写了太多缓冲区。         |
+| buffers_backend       | bigint                   | 通过后端直接写缓冲区数。                                     |
+| buffers_backend_fsync | bigint                   | 后端不得不执行自己的fsync调用的时间数（通常后端写进程处理这些即使后端确实自己写）。 |
+| buffers_alloc         | bigint                   | 分配的缓冲区数量。                                           |
+| stats_reset           | timestamp with time zone | 这些统计被重置的时间。                                       |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_CANDIDATE_STATUS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_CANDIDATE_STATUS.md
new file mode 100644
index 0000000000000000000000000000000000000000..d7e5c2a68ba7a99229cced211311fe7913d34374
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_CANDIDATE_STATUS.md
@@ -0,0 +1,22 @@
+---
+title: GLOBAL_CANDIDATE_STATUS
+summary: GLOBAL_CANDIDATE_STATUS
+author: Guo Huan
+date: 2021-11-15
+---
+
+# GLOBAL_CANDIDATE_STATUS
+
+GLOBAL_CANDIDATE_STATUS视图显示整个数据库所有实例候选buffer个数，buffer淘汰信息。
+
+**表 1** GLOBAL_GET_BGWRITER_STATUS字段
+
+| 名称                    | 类型    | 描述                                                         |
+| :---------------------- | :------ | :----------------------------------------------------------- |
+| node_name               | text    | 节点名称。                                                   |
+| candidate_slots         | integer | 当前Normal Buffer Pool候选buffer链中页面个数。               |
+| get_buf_from_list       | bigint  | Normal Buffer Pool，buffer淘汰从候选buffer链中获取页面的次数。 |
+| get_buf_clock_sweep     | bigint  | Normal Buffer Pool，buffer淘汰从原淘汰方案中获取页面的次数。 |
+| seg_candidate_slots     | integer | 当前Segment Buffer Pool候选buffer链中页面个数。              |
+| seg_get_buf_from_list   | bigint  | Segment Buffer Pool，buffer淘汰从候选buffer链中获取页面的次数。 |
+| seg_get_buf_clock_sweep | bigint  | Segment Buffer Pool，buffer淘汰从原淘汰方案中获取页面的次数。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_CKPT_STATUS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_CKPT_STATUS.md
new file mode 100644
index 0000000000000000000000000000000000000000..52cc9479077392c97113957c79c49d8c95c28b2b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_CKPT_STATUS.md
@@ -0,0 +1,22 @@
+---
+title: GLOBAL_CKPT_STATUS
+summary: GLOBAL_CKPT_STATUS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_CKPT_STATUS
+
+GLOBAL_CKPT_STATUS视图用于显示MogDB所有实例的检查点信息和各类日志刷页情况。
+
+**表 1** GLOBAL_CKPT_STATUS字段
+
+| 名称                     | 类型   | 描述                                  |
+| :----------------------- | :----- | :------------------------------------ |
+| node_name                | text   | 数据库进程名称。                      |
+| ckpt_redo_point          | test   | 当前实例的检查点。                    |
+| ckpt_clog_flush_num      | bigint | 从启动到当前时间clog刷盘页面数。      |
+| ckpt_csnlog_flush_num    | bigint | 从启动到当前时间csnlog刷盘页面数。    |
+| ckpt_multixact_flush_num | bigint | 从启动到当前时间multixact刷盘页面数。 |
+| ckpt_predicate_flush_num | bigint | 从启动到当前时间predicate刷盘页面数。 |
+| ckpt_twophase_flush_num  | bigint | 从启动到当前时间twophase刷盘页面数。  |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_DOUBLE_WRITE_STATUS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_DOUBLE_WRITE_STATUS.md
new file mode 100644
index 0000000000000000000000000000000000000000..f9f1fec76e561ec9cfdfbcfc1cee0db79e4c68d3
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_DOUBLE_WRITE_STATUS.md
@@ -0,0 +1,26 @@
+---
+title: GLOBAL_DOUBLE_WRITE_STATUS
+summary: GLOBAL_DOUBLE_WRITE_STATUS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_DOUBLE_WRITE_STATUS
+
+GLOBAL_DOUBLE_WRITE_STATUS视图显示MogDB所有实例的双写文件的情况。
+
+**表 1** GLOBAL_DOUBLEWRITE_STATUS字段
+
+| 名称                  | 类型   | 描述                                                         |
+| :-------------------- | :----- | :----------------------------------------------------------- |
+| node_name             | text   | 数据库进程名称。                                             |
+| curr_dwn              | bigint | 当前双写文件的序列号。                                       |
+| curr_start_page       | bigint | 当前双写文件恢复起始页面。                                   |
+| file_trunc_num        | bigint | 当前双写文件复用的次数。                                     |
+| file_reset_num        | bigint | 当前双写文件写满后发生重置的次数。                           |
+| total_writes          | bigint | 当前双写文件总的I/O次数。                                    |
+| low_threshold_writes  | bigint | 低效率写双写文件的I/O次数（一次I/O刷页数量少于16页面）。     |
+| high_threshold_writes | bigint | 高效率写双写文件的I/O次数（一次I/O刷页数量多于一批，421个页面）。 |
+| total_pages           | bigint | 当前刷页到双写文件区的总的页面个数。                         |
+| low_threshold_pages   | bigint | 低效率刷页的页面个数。                                       |
+| high_threshold_pages  | bigint | 高效率刷页的页面个数。                                       |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_GET_BGWRITER_STATUS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_GET_BGWRITER_STATUS.md
new file mode 100644
index 0000000000000000000000000000000000000000..802bc61f72fe6ee109fa9713c90421ebac928a1a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_GET_BGWRITER_STATUS.md
@@ -0,0 +1,21 @@
+---
+title: GLOBAL_GET_BGWRITER_STATUS
+summary: GLOBAL_GET_BGWRITER_STATUS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_GET_BGWRITER_STATUS
+
+GLOBAL_GET_BGWRITER_STATUS视图显示所有实例bgwriter线程刷页信息，候选buffer链中页面个数，buffer淘汰信息。
+
+**表 1** GLOBAL_GET_BGWRITER_STATUS字段
+
+| 名称                        | 类型    | 描述                                         |
+| :-------------------------- | :------ | :------------------------------------------- |
+| node_name                   | text    | 实例名称。                                   |
+| bgwr_actual_flush_total_num | bigint  | 从启动到当前时间bgwriter线程总计刷脏页数量。 |
+| bgwr_last_flush_num         | integer | bgwriter线程上一批刷脏页数量。               |
+| candidate_slots             | integer | 当前候选buffer链中页面个数。                 |
+| get_buffer_from_list        | bigint  | buffer淘汰从候选buffer链中获取页面的次数。   |
+| get_buffer_clock_sweep      | bigint  | buffer淘汰从原淘汰方案中获取页面的次数。     |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_PAGEWRITER_STATUS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_PAGEWRITER_STATUS.md
new file mode 100644
index 0000000000000000000000000000000000000000..0ae5f1be59f44e60fc244c24ca321060eb79726d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_PAGEWRITER_STATUS.md
@@ -0,0 +1,23 @@
+---
+title: GLOBAL_PAGEWRITER_STATUS
+summary: GLOBAL_PAGEWRITER_STATUS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_PAGEWRITER_STATUS
+
+GLOBAL_PAGEWRITER_STATUS视图显示MogDB实例的刷页信息和检查点信息。
+
+**表 1** GLOBAL_PAGEWRITER_STATUS字段
+
+| 名称                        | 类型    | 描述                                         |
+| :-------------------------- | :------ | :------------------------------------------- |
+| node_name                   | text    | 数据库进程名称。                             |
+| pgwr_actual_flush_total_num | bigint  | 从启动到当前时间总计刷脏页数量。             |
+| pgwr_last_flush_num         | integer | 上一批刷脏页数量。                           |
+| remain_dirty_page_num       | bigint  | 当前预计还剩余多少脏页。                     |
+| queue_head_page_rec_lsn     | text    | 当前实例的脏页队列第一个脏页的recovery_lsn。 |
+| queue_rec_lsn               | text    | 当前实例的脏页队列的recovery_lsn。           |
+| current_xlog_insert_lsn     | text    | 当前实例XLog写入的位置。                     |
+| ckpt_redo_point             | text    | 当前实例的检查点。                           |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_RECORD_RESET_TIME.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_RECORD_RESET_TIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..9f7a1e1cf52f3b7f85824eb9776bb8e735dd3f8b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_RECORD_RESET_TIME.md
@@ -0,0 +1,17 @@
+---
+title: GLOBAL_RECORD_RESET_TIME
+summary: GLOBAL_RECORD_RESET_TIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_RECORD_RESET_TIME
+
+GLOBAL_RECORD_RESET_TIME用于重置（重启、主备倒换、数据库删除）汇聚MogDB统计信息时间。
+
+**表 1** GLOBAL_RECORD_RESET_TIME字段
+
+| 名称       | 类型                     | 描述             |
+| :--------- | :----------------------- | :--------------- |
+| node_name  | text                     | 数据库进程名称。 |
+| reset_time | timestamp with time zone | 重置时间点。     |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_RECOVERY_STATUS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_RECOVERY_STATUS.md
new file mode 100644
index 0000000000000000000000000000000000000000..6b2c47d6f37e7efc8c087075375d600bc06d6b26
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_RECOVERY_STATUS.md
@@ -0,0 +1,24 @@
+---
+title: GLOBAL_RECOVERY_STATUS
+summary: GLOBAL_RECOVERY_STATUS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_RECOVERY_STATUS
+
+GLOBAL_RECOVERY_STATUS视图显示关于主机和备机的日志流控信息。
+
+**表 1** GLOBAL_RECOVERY_STATUS字段
+
+| 名称               | 类型    | 描述                                             |
+| :----------------- | :------ | :----------------------------------------------- |
+| node_name          | text    | 主机进程名称，包含主机和备机。                   |
+| standby_node_name  | text    | 备机进程名称。                                   |
+| source_ip          | text    | 主机的IP地址。                                   |
+| source_port        | integer | 主机的端口号。                                   |
+| dest_ip            | text    | 备机的IP地址。                                   |
+| dest_port          | integer | 备机的端口号。                                   |
+| current_rto        | bigint  | 备机当前的日志流控时间，单位秒。                 |
+| target_rto         | bigint  | 备机通过GUC参数设置的预期流控时间，单位秒。      |
+| current_sleep_time | bigint  | 为了达到这个预期主机所需要的睡眠时间，单位微妙。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_REDO_STATUS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_REDO_STATUS.md
new file mode 100644
index 0000000000000000000000000000000000000000..5bef1e15e489a0a4668868b0a54d5ffe4750dddc
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_REDO_STATUS.md
@@ -0,0 +1,38 @@
+---
+title: GLOBAL_REDO_STATUS
+summary: GLOBAL_REDO_STATUS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_REDO_STATUS
+
+GLOBAL_REDO_STATUS视图显示MogDB实例的日志回放情况。
+
+**表 1** GLOBAL_REDO_STATUS字段
+
+| 名称                      | 类型   | 描述                                               |
+| :------------------------ | :----- | :------------------------------------------------- |
+| node_name                 | text   | 数据库进程名称。                                   |
+| redo_start_ptr            | bigint | 当前实例日志回放的起始点。                         |
+| redo_start_time           | bigint | 当前实例日志回放的起始UTC时间。                    |
+| redo_done_time            | bigint | 当前实例日志回放的结束UTC时间。                    |
+| curr_time                 | bigint | 当前实例的当前UTC时间。                            |
+| min_recovery_point        | bigint | 当前实例日志的最小一致性点位置。                   |
+| read_ptr                  | bigint | 当前实例日志的读取位置。                           |
+| last_replayed_read_ptr    | bigint | 当前实例的日志回放位置。                           |
+| recovery_done_ptr         | bigint | 当前实例启动完成时的回放位置。                     |
+| read_xlog_io_counter      | bigint | 当前实例读取回放日志的io次数计数。                 |
+| read_xlog_io_total_dur    | bigint | 当前实例读取回放日志的io总时延。                   |
+| read_data_io_counter      | bigint | 当前实例回放过程中读取数据页面的io次数计数。       |
+| read_data_io_total_dur    | bigint | 当前实例回放过程中读取数据页面的io总时延。         |
+| write_data_io_counter     | bigint | 当前实例回放过程中写数据页面的io次数计数。         |
+| write_data_io_total_dur   | bigint | 当前实例回放过程中写数据页面的io总时延。           |
+| process_pending_counter   | bigint | 当前实例回放过程中日志分发线程的同步次数计数。     |
+| process_pending_total_dur | bigint | 当前实例回放过程中日志分发线程的同步总时延。       |
+| apply_counter             | bigint | 当前实例回放过程中回放线程的同步次数计数。         |
+| apply_total_dur           | bigint | 当前实例回放过程中回放线程的同步总时延。           |
+| speed                     | bigint | 当前实例日志回放速率。                             |
+| local_max_ptr             | bigint | 当前实例启动成功后本地收到的回放日志的最大值。     |
+| primary_flush_ptr         | bigint | 主机落盘日志的位置。                               |
+| worker_info               | text   | 当前实例回放线程信息，若没有开并行回放则该值为空。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_REPLICATION_SLOTS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_REPLICATION_SLOTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..03902418a47be34427b371e7bdfa0ff005a00c9a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_REPLICATION_SLOTS.md
@@ -0,0 +1,26 @@
+---
+title: GLOBAL_REPLICATION_SLOTS
+summary: GLOBAL_REPLICATION_SLOTS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_REPLICATION_SLOTS
+
+GLOBAL_REPLICATION_SLOTS视图用于查看MogDB各节点的复制节点的信息。
+
+**表 1** GLOBAL_REPLICATION_SLOTS字段
+
+| **名称**      | **类型** | **描述**                          |
+| :------------ | :------- | :-------------------------------- |
+| node_name     | name     | 数据库进程名称。                  |
+| slot_name     | text     | 复制节点的名称。                  |
+| plugin        | text     | 插件名称。                        |
+| slot_type     | text     | 复制节点的类型。                  |
+| datoid        | oid      | 复制节点的数据库OID。             |
+| database      | name     | 复制节点的数据库名称。            |
+| active        | boolean  | 复制节点是否为激活状态。          |
+| x_min         | xid      | 复制节点事务标识。                |
+| catalog_xmin  | xid      | 逻辑复制槽对应的最早解码事务标识. |
+| restart_lsn   | text     | 复制节点的Xlog文件信息。          |
+| dummy_standby | boolean  | 复制节点是否为假备。              |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_REPLICATION_STAT.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_REPLICATION_STAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..0b6e46fbd10381d45635002aa0a996314bdb2f1a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_REPLICATION_STAT.md
@@ -0,0 +1,31 @@
+---
+title: GLOBAL_REPLICATION_STAT
+summary: GLOBAL_REPLICATION_STAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_REPLICATION_STAT
+
+GLOBAL_REPLICATION_STAT视图用于获得各节点描述日志同步状态信息，如发起端发送日志位置、收端接收日志位置等。
+
+**表 1** GLOBAL_REPLICATION_STAT字段
+
+| **名称**                 | **类型**                 | **描述**                                                     |
+| :----------------------- | :----------------------- | :----------------------------------------------------------- |
+| node_name                | name                     | 数据库进程名称。                                             |
+| pid                      | bigint                   | 线程的PID。                                                  |
+| usesysid                 | oid                      | 用户系统ID。                                                 |
+| usename                  | name                     | 用户名。                                                     |
+| application_name         | text                     | 程序名称。                                                   |
+| client_addr              | inet                     | 客户端地址。                                                 |
+| client_hostname          | text                     | 客户端名。                                                   |
+| client_port              | integer                  | 客户端端口。                                                 |
+| backend_start            | timestamp with time zone | 程序启动时间。                                               |
+| state                    | text                     | 日志复制的状态: <br/>- 追赶状态。<br/>- 一致的流状态。       |
+| sender_sent_location     | text                     | 发送端发送日志位置。                                         |
+| receiver_write_location  | text                     | 接收端write日志位置。                                        |
+| receiver_flush_location  | text                     | 接收端flush日志位置。                                        |
+| receiver_replay_location | text                     | 接收端replay日志位置。                                       |
+| sync_priority            | integer                  | 同步复制的优先级（0表示异步）。                              |
+| sync_state               | text                     | 同步状态: <br/>- 异步复制。<br/>- 同步复制。<br/>- 潜在同步者。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_SINGLE_FLUSH_DW_STATUS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_SINGLE_FLUSH_DW_STATUS.md
new file mode 100644
index 0000000000000000000000000000000000000000..a4a67b304a666611c2e10cbcd77005d6c027d031
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/GLOBAL_SINGLE_FLUSH_DW_STATUS.md
@@ -0,0 +1,21 @@
+---
+title: GLOBAL_SINGLE_FLUSH_DW_STATUS
+summary: GLOBAL_SINGLE_FLUSH_DW_STATUS
+author: Guo Huan
+date: 2021-11-15
+---
+
+# GLOBAL_SINGLE_FLUSH_DW_STATUS
+
+GLOBAL_SINGLE_FLUSH_DW_STATUS视图显示数据库所有实例单页面淘汰双写文件信息。展示内容中，/前是第一个版本双写文件刷页情况，/后是第二个版本双写文件刷页情况。
+
+**表 1** GLOBAL_SINGLE_FLUSH_DW_STATUS字段
+
+| 名称            | 类型 | 描述                               |
+| :-------------- | :--- | :--------------------------------- |
+| node_name       | text | 实例名称。                         |
+| curr_dwn        | text | 当前双写文件的序列号。             |
+| curr_start_page | text | 当前双写文件start位置。            |
+| total_writes    | text | 当前双写文件总计写数据页面个数。   |
+| file_trunc_num  | text | 当前双写文件复用的次数。           |
+| file_reset_num  | text | 当前双写文件写满后发生重置的次数。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/REPLICATION_SLOTS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/REPLICATION_SLOTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..8e73593939bf6d76d8525d3c73407c631a2289b0
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/REPLICATION_SLOTS.md
@@ -0,0 +1,25 @@
+---
+title: REPLICATION_SLOTS
+summary: REPLICATION_SLOTS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# REPLICATION_SLOTS
+
+REPLICATION_SLOTS视图用于查看复制节点的信息。
+
+**表 1** REPLICATION_SLOTS字段
+
+| **名称**      | **类型** | **描述**                           |
+| :------------ | :------- | :--------------------------------- |
+| slot_name     | text     | 复制节点的名称。                   |
+| plugin        | text     | 插件名称。                         |
+| slot_type     | text     | 复制节点的类型。                   |
+| datoid        | oid      | 复制节点的数据库OID。              |
+| database      | name     | 复制节点的数据库名称。             |
+| active        | boolean  | 复制节点是否为激活状态。           |
+| xmin          | xid      | 复制节点事务标识。                 |
+| catalog_xmin  | xid      | 逻辑复制槽对应的最早解码事务标识。 |
+| restart_lsn   | text     | 复制节点的Xlog文件信息。           |
+| dummy_standby | boolean  | 复制节点是否为假备。               |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/REPLICATION_STAT.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/REPLICATION_STAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..52611f8a7c5b31b07b8f47c03b7e565ec5680f12
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/REPLICATION_STAT.md
@@ -0,0 +1,30 @@
+---
+title: REPLICATION_STAT
+summary: REPLICATION_STAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# REPLICATION_STAT
+
+REPLICATION_STAT用于描述日志同步状态信息，如发起端发送日志位置、收端接收日志位置等。
+
+**表 1** REPLICATION_STAT字段
+
+| **名称**                 | **类型**                 | **描述**                                                     |
+| :----------------------- | :----------------------- | :----------------------------------------------------------- |
+| pid                      | bigint                   | 线程的PID。                                                  |
+| usesysid                 | oid                      | 用户系统ID。                                                 |
+| usename                  | name                     | 用户名。                                                     |
+| application_name         | text                     | 程序名称。                                                   |
+| client_addr              | inet                     | 客户端地址。                                                 |
+| client_hostname          | text                     | 客户端名。                                                   |
+| client_port              | integer                  | 客户端端口。                                                 |
+| backend_start            | timestamp with time zone | 程序启动时间。                                               |
+| state                    | text                     | 日志复制的状态：<br/>- 追赶状态。<br/>- 一致的流状态。       |
+| sender_sent_location     | text                     | 发送端发送日志位置。                                         |
+| receiver_write_location  | text                     | 接收端write日志位置。                                        |
+| receiver_flush_location  | text                     | 接收端flush日志位置。                                        |
+| receiver_replay_location | text                     | 接收端replay日志位置。                                       |
+| sync_priority            | integer                  | 同步复制的优先级（0表示异步）。                              |
+| sync_state               | text                     | 同步状态：<br/>- 异步复制。<br/>- 同步复制。<br/>- 潜在同步者。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/SUMMARY_USER_LOGIN.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/SUMMARY_USER_LOGIN.md
new file mode 100644
index 0000000000000000000000000000000000000000..ac78e133670439ec2eb6b040d528876151aa3e14
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/SUMMARY_USER_LOGIN.md
@@ -0,0 +1,20 @@
+---
+title: SUMMARY_USER_LOGIN
+summary: SUMMARY_USER_LOGIN
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_USER_LOGIN
+
+SUMMARY_USER_LOGIN用来记录数据库主节点上用户登录和退出次数的相关信息。
+
+**表 1** SUMMARY_USER_LOGIN字段
+
+| **名称**       | **类型** | **描述**                            |
+| :------------- | :------- | :---------------------------------- |
+| node_name      | text     | 数据库进程名称。                    |
+| user_name      | text     | 用户名称。                          |
+| user_id        | integer  | 用户oid（同pg_authid中的oid字段）。 |
+| login_counter  | bigint   | 登录次数。                          |
+| logout_counter | bigint   | 退出次数。                          |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/USER_LOGIN.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/USER_LOGIN.md
new file mode 100644
index 0000000000000000000000000000000000000000..8e7e8a61beb72c7c207707a37bb2632e35e9972c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/utility/USER_LOGIN.md
@@ -0,0 +1,20 @@
+---
+title: USER_LOGIN
+summary: USER_LOGIN
+author: Guo Huan
+date: 2021-04-19
+---
+
+# USER_LOGIN
+
+USER_LOGIN用来记录用户登录和退出次数的相关信息。
+
+**表 1** USER_LOGIN字段
+
+| **名称**       | **类型** | **描述**                            |
+| :------------- | :------- | :---------------------------------- |
+| node_name      | text     | 数据库进程名称。                    |
+| user_name      | text     | 用户名称。                          |
+| user_id        | integer  | 用户oid（同pg_authid中的oid字段）。 |
+| login_counter  | bigint   | 登录次数。                          |
+| logout_counter | bigint   | 退出次数。                          |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/wait-events/GLOBAL_WAIT_EVENTS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/wait-events/GLOBAL_WAIT_EVENTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..9b93e19019809034dfa8372dcab3c925b59009a2
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/wait-events/GLOBAL_WAIT_EVENTS.md
@@ -0,0 +1,25 @@
+---
+title: GLOBAL_WAIT_EVENTS
+summary: GLOBAL_WAIT_EVENTS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_WAIT_EVENTS
+
+GLOBAL_WAIT_EVENTS视图显示各节点的event的等待相关的统计信息。
+
+**表 1** GLOBAL_WAIT_EVENTS字段
+
+| **名称**        | **类型**                 | **描述**                     |
+| :-------------- | :----------------------- | :--------------------------- |
+| nodename        | text                     | 数据库进程名称。             |
+| type            | text                     | event类型。                  |
+| event           | text                     | event名称。                  |
+| wait            | bigint                   | 等待次数。                   |
+| failed_wait     | bigint                   | 失败的等待次数。             |
+| total_wait_time | bigint                   | 总等待时间（单位: 微秒）。   |
+| avg_wait_time   | bigint                   | 平均等待时间（单位: 微秒）。 |
+| max_wait_time   | bigint                   | 最大等待时间（单位: 微秒）。 |
+| min_wait_time   | bigint                   | 最小等待时间（单位: 微秒）。 |
+| last_updated    | timestamp with time zone | 最后一次更新该事件的时间。   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/wait-events/WAIT_EVENTS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/wait-events/WAIT_EVENTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..a6a54ebd0d922b7dcd5d34e5a8caceea94bd32a1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/wait-events/WAIT_EVENTS.md
@@ -0,0 +1,25 @@
+---
+title: WAIT_EVENTS
+summary: WAIT_EVENTS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# WAIT_EVENTS
+
+WAIT_EVENTS显示当前节点的event的等待相关的统计信息。具体事件信息见[附录-表1 等待状态列表](table-1)、[附录-表2 轻量级锁等待事件列表](table-2)、[附录-表3 IO等待事件列表](table-3)和[附录-表4 事务锁等待事件列表](table-4)。关于每种事务锁对业务的影响程度，请参考[LOCK](110-LOCK)语法小节的详细描述。
+
+**表 1** WAIT_EVENTS字段
+
+| **名称**        | **类型**                 | **描述**                     |
+| :-------------- | :----------------------- | :--------------------------- |
+| nodename        | text                     | 数据库进程名称。             |
+| type            | text                     | event类型。                  |
+| event           | text                     | event名称。                  |
+| wait            | bigint                   | 等待次数。                   |
+| failed_wait     | bigint                   | 失败的等待次数。             |
+| total_wait_time | bigint                   | 总等待时间（单位: 微秒）。   |
+| avg_wait_time   | bigint                   | 平均等待时间（单位: 微秒）。 |
+| max_wait_time   | bigint                   | 最大等待时间（单位: 微秒）。 |
+| min_wait_time   | bigint                   | 最小等待时间（单位: 微秒）。 |
+| last_updated    | timestamp with time zone | 最后一次更新该事件的时间。   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload-manager/WLM_USER_RESOURCE_CONFIG.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload-manager/WLM_USER_RESOURCE_CONFIG.md
new file mode 100644
index 0000000000000000000000000000000000000000..e36cd866d41f6f584cd6cb8455ffb4da6f9dd6c9
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload-manager/WLM_USER_RESOURCE_CONFIG.md
@@ -0,0 +1,25 @@
+---
+title: WLM_USER_RESOURCE_CONFIG
+summary: WLM_USER_RESOURCE_CONFIG
+author: Guo Huan
+date: 2021-04-19
+---
+
+# WLM_USER_RESOURCE_CONFIG
+
+WLM_USER_RESOURCE_CONFIG视图显示用户的资源配置信息。
+
+**表 1** WLM_USER_RESOURCE_CONFIG字段
+
+| 名称       | 类型    | 描述             |
+| :--------- | :------ | :--------------- |
+| userid     | oid     | 用户oid。        |
+| username   | name    | 用户名称。       |
+| sysadmin   | boolean | 是否是sysadmin。 |
+| rpoid      | oid     | 资源池的oid。    |
+| respool    | name    | 资源池的名称。   |
+| parentid   | oid     | 父用户的oid。    |
+| totalspace | bigint  | 占用总空间大小。 |
+| spacelimit | bigint  | 空间大上限。     |
+| childcount | integer | 子用户数量。     |
+| childlist  | text    | 子用户的列表。   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload-manager/WLM_USER_RESOURCE_RUNTIME.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload-manager/WLM_USER_RESOURCE_RUNTIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..bf6603297078a6333b9cf75ba8531290cfa87e3e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload-manager/WLM_USER_RESOURCE_RUNTIME.md
@@ -0,0 +1,26 @@
+---
+title: WLM_USER_RESOURCE_RUNTIME
+summary: WLM_USER_RESOURCE_RUNTIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# WLM_USER_RESOURCE_RUNTIME
+
+WLM_USER_RESOURCE_RUNTIME视图显示所有用户资源使用情况，需要使用管理员用户进行查询。此视图在GUC参数“use_workload_manager”为“on”时才有效。
+
+**表 1** WLM_USER_RESOURCE_RUNTIME字段
+
+| 名称              | 类型    | 描述                              |
+| :---------------- | :------ | :-------------------------------- |
+| username          | name    | 用户名。                                                     |
+| used_memory       | integer | 正在使用的内存大小，单位MB。                                 |
+| total_memory      | integer | 可以使用的内存大小，单位MB。值为0表示未限制最大可用内存，其限制取决于数据库最大可用内存。 |
+| used_cpu          | integer | 正在使用的CPU核数。                                          |
+| total_cpu         | integer | 在该机器节点上，用户关联控制组的CPU核数总和。                |
+| used_space        | bigint  | 已使用的存储空间大小，单位KB。                               |
+| total_space       | bigint  | 可使用的存储空间大小，单位KB，值为-1表示未限制最大存储空间。 |
+| used_temp_space   | bigint  | 已使用的临时空间大小（预留字段，暂未使用），单位KB。         |
+| total_temp_space  | bigint  | 可使用的临时空间大小（预留字段，暂未使用），单位KB，值为-1表示未限制最大临时存储空间。 |
+| used_spill_space  | bigint  | 已使用的下盘空间大小（预留字段，暂未使用），单位KB。         |
+| total_spill_space | bigint  | 可使用的下盘空间大小（预留字段，暂未使用），单位KB，值为-1表示未限制最大下盘空间。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/GLOBAL_USER_TRANSACTION.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/GLOBAL_USER_TRANSACTION.md
new file mode 100644
index 0000000000000000000000000000000000000000..9b827919be57cb0d511098b4ff228c5a23b1d75e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/GLOBAL_USER_TRANSACTION.md
@@ -0,0 +1,29 @@
+---
+title: GLOBAL_USER_TRANSACTION
+summary: GLOBAL_USER_TRANSACTION
+author: Guo Huan
+date: 2021-11-15
+---
+
+# GLOBAL_USER_TRANSACTION
+
+GLOBAL_USER_TRANSACTION用来统计全局用户执行的事务信息。
+
+**表 1** GLOBAL_USER_TRANSACTION字段
+
+| **名称**            | **类型** | **描述**                             |
+| :------------------ | :------- | :----------------------------------- |
+| node_name           | name     | 节点名称。                           |
+| username            | name     | 用户的名称。                         |
+| commit_counter      | bigint   | 用户事务commit数量。                 |
+| rollback_counter    | bigint   | 用户事务rollback数量。               |
+| resp_min            | bigint   | 用户事务最小响应时间（单位：微秒）。 |
+| resp_max            | bigint   | 用户事务最大响应时间（单位：微秒）。 |
+| resp_avg            | bigint   | 用户事务平均响应时间（单位：微秒）。 |
+| resp_total          | bigint   | 用户事务总响应时间（单位：微秒）。   |
+| bg_commit_counter   | bigint   | 后台事务commit数量。                 |
+| bg_rollback_counter | bigint   | 后台事务rollback数量。               |
+| bg_resp_min         | bigint   | 后台事务最小响应时间（单位：微秒）。 |
+| bg_resp_max         | bigint   | 后台事务最大响应时间（单位：微秒）。 |
+| bg_resp_avg         | bigint   | 后台事务平均响应时间（单位：微秒）。 |
+| bg_resp_total       | bigint   | 后台事务总响应时间（单位：微秒）。   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/GLOBAL_WORKLOAD_TRANSACTION.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/GLOBAL_WORKLOAD_TRANSACTION.md
new file mode 100644
index 0000000000000000000000000000000000000000..6a8a9660f7dd041b57d924fe39df48aa742a8618
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/GLOBAL_WORKLOAD_TRANSACTION.md
@@ -0,0 +1,29 @@
+---
+title: GLOBAL_WORKLOAD_TRANSACTION
+summary: GLOBAL_WORKLOAD_TRANSACTION
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GLOBAL_WORKLOAD_TRANSACTION
+
+显示各节点上的workload的负载信息。
+
+**表 1** GLOBAL_WORKLOAD_TRANSACTION字段
+
+| **名称**            | **类型** | **描述**                             |
+| :------------------ | :------- | :----------------------------------- |
+| node_name           | name     | 数据库进程名称。                     |
+| workload            | name     | 负载的名称。                         |
+| commit_counter      | bigint   | 用户事务commit数量。                 |
+| rollback_counter    | bigint   | 用户事务rollback数量。               |
+| resp_min            | bigint   | 用户事务最小响应时间（单位: 微秒）。 |
+| resp_max            | bigint   | 用户事务最大响应时间（单位: 微秒）。 |
+| resp_avg            | bigint   | 用户事务平均响应时间（单位: 微秒）。 |
+| resp_total          | bigint   | 用户事务总响应时间（单位: 微秒）。   |
+| bg_commit_counter   | bigint   | 后台事务commit数量。                 |
+| bg_rollback_counter | bigint   | 后台事务rollback数量。               |
+| bg_resp_min         | bigint   | 后台事务最小响应时间（单位: 微秒）。 |
+| bg_resp_max         | bigint   | 后台事务最大响应时间（单位: 微秒）。 |
+| bg_resp_avg         | bigint   | 后台事务平均响应时间（单位: 微秒）。 |
+| bg_resp_total       | bigint   | 后台事务总响应时间（单位: 微秒）。   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/SUMMARY_WORKLOAD_SQL_COUNT.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/SUMMARY_WORKLOAD_SQL_COUNT.md
new file mode 100644
index 0000000000000000000000000000000000000000..68afee3e27d5d59959688102e11d648b2bf522a7
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/SUMMARY_WORKLOAD_SQL_COUNT.md
@@ -0,0 +1,24 @@
+---
+title: SUMMARY_WORKLOAD_SQL_COUNT
+summary: SUMMARY_WORKLOAD_SQL_COUNT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_WORKLOAD_SQL_COUNT
+
+显示MogDB内各数据库主节点的workload上的SQL数量分布。
+
+**表 1** SUMMARY_WORKLOAD_SQL_COUNT字段
+
+| **名称**     | **类型** | **描述**         |
+| :----------- | :------- | :--------------- |
+| node_name    | name     | 数据库进程名称。 |
+| workload     | name     | 负载名称。       |
+| select_count | bigint   | select数量。     |
+| update_count | bigint   | update数量。     |
+| insert_count | bigint   | insert数量。     |
+| delete_count | bigint   | delete数量。     |
+| ddl_count    | bigint   | ddl数量。        |
+| dml_count    | bigint   | dml数量。        |
+| dcl_count    | bigint   | dcl数量。        |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/SUMMARY_WORKLOAD_SQL_ELAPSE_TIME.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/SUMMARY_WORKLOAD_SQL_ELAPSE_TIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..e825fd9dd84c5bab652391982cef3982d1e6e5fd
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/SUMMARY_WORKLOAD_SQL_ELAPSE_TIME.md
@@ -0,0 +1,33 @@
+---
+title: SUMMARY_WORKLOAD_SQL_ELAPSE_TIME
+summary: SUMMARY_WORKLOAD_SQL_ELAPSE_TIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_WORKLOAD_SQL_ELAPSE_TIME
+
+SUMMARY_WORKLOAD_SQL_ELAPSE_TIME用来统计数据库主节点上workload（业务）负载的SUID信息。
+
+**表 1** SUMMARY_WORKLOAD_SQL_ELAPSE_TIM字段
+
+| **名称**            | **类型** | **描述**                             |
+| :------------------ | :------- | :----------------------------------- |
+| node_name           | name     | 数据库进程名称。                     |
+| workload            | name     | workload（业务负载）名称。           |
+| total_select_elapse | bigint   | 总select的时间花费（单位: 微秒）。   |
+| max_select_elapse   | bigint   | 最大select的时间花费（单位: 微秒）。 |
+| min_select_elapse   | bigint   | 最小select的时间花费（单位: 微秒）。 |
+| avg_select_elapse   | bigint   | 平均select的时间花费（单位: 微秒）。 |
+| total_update_elapse | bigint   | 总update的时间花费（单位: 微秒）。   |
+| max_update_elapse   | bigint   | 最大update的时间花费（单位: 微秒）。 |
+| min_update_elapse   | bigint   | 最小update的时间花费（单位: 微秒）。 |
+| avg_update_elapse   | bigint   | 平均update的时间花费（单位: 微秒）。 |
+| total_insert_elapse | bigint   | 总insert的时间花费（单位: 微秒）。   |
+| max_insert_elapse   | bigint   | 最大insert的时间花费（单位: 微秒）。 |
+| min_insert_elapse   | bigint   | 最小insert的时间花费（单位: 微秒）。 |
+| avg_insert_elapse   | bigint   | 平均insert的时间花费（单位: 微秒）。 |
+| total_delete_elapse | bigint   | 总delete的时间花费（单位: 微秒）。   |
+| max_delete_elapse   | bigint   | 最大delete的时间花费（单位: 微秒）。 |
+| min_delete_elapse   | bigint   | 最小delete的时间花费（单位: 微秒）。 |
+| avg_delete_elapse   | bigint   | 平均delete的时间花费（单位: 微秒）。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/SUMMARY_WORKLOAD_TRANSACTION.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/SUMMARY_WORKLOAD_TRANSACTION.md
new file mode 100644
index 0000000000000000000000000000000000000000..b185a4b609cd9e002d2bb889e0262ad028359e22
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/SUMMARY_WORKLOAD_TRANSACTION.md
@@ -0,0 +1,28 @@
+---
+title: SUMMARY_WORKLOAD_TRANSACTION
+summary: SUMMARY_WORKLOAD_TRANSACTION
+author: Guo Huan
+date: 2021-04-19
+---
+
+# SUMMARY_WORKLOAD_TRANSACTION
+
+显示MogDB内汇聚的负载事务信息。
+
+**表 1** SUMMARY_WORKLOAD_TRANSACTION字段
+
+| **名称**            | **类型** | **描述**                             |
+| :------------------ | :------- | :----------------------------------- |
+| workload            | name     | 负载的名称。                         |
+| commit_counter      | numeric  | 用户事务commit数量。                 |
+| rollback_counter    | numeric  | 用户事务rollback数量。               |
+| resp_min            | bigint   | 用户事务最小响应时间（单位: 微秒）。 |
+| resp_max            | bigint   | 用户事务最大响应时间（单位: 微秒）。 |
+| resp_avg            | bigint   | 用户事务平均响应时间（单位: 微秒）。 |
+| resp_total          | numeric  | 用户事务总响应时间（单位: 微秒）。   |
+| bg_commit_counter   | numeric  | 后台事务commit数量。                 |
+| bg_rollback_counter | numeric  | 后台事务rollback数量。               |
+| bg_resp_min         | bigint   | 后台事务最小响应时间（单位: 微秒）。 |
+| bg_resp_max         | bigint   | 后台事务最大响应时间（单位: 微秒）。 |
+| bg_resp_avg         | bigint   | 后台事务平均响应时间（单位: 微秒）。 |
+| bg_resp_total       | numeric  | 后台事务总响应时间（单位: 微秒）。   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/USER_TRANSACTION.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/USER_TRANSACTION.md
new file mode 100644
index 0000000000000000000000000000000000000000..7023751bdd96200050f003157585cc856dbbc817
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/USER_TRANSACTION.md
@@ -0,0 +1,28 @@
+---
+title: USER_TRANSACTION
+summary: USER_TRANSACTION
+author: Guo Huan
+date: 2021-11-15
+---
+
+# USER_TRANSACTION
+
+USER_TRANSACTION用来统计用户执行的事务信息。monadmin用户能看到所有用户执行事务的信息，普通用户只能查询到自己执行的事务信息。
+
+**表 1** USER_TRANSACTION字段
+
+| **名称**            | **类型** | **描述**                             |
+| :------------------ | :------- | :----------------------------------- |
+| username            | name     | 用户的名称。                         |
+| commit_counter      | bigint   | 用户事务commit数量。                 |
+| rollback_counter    | bigint   | 用户事务rollback数量。               |
+| resp_min            | bigint   | 用户事务最小响应时间（单位：微秒）。 |
+| resp_max            | bigint   | 用户事务最大响应时间（单位：微秒）。 |
+| resp_avg            | bigint   | 用户事务平均响应时间（单位：微秒）。 |
+| resp_total          | bigint   | 用户事务总响应时间（单位：微秒）。   |
+| bg_commit_counter   | bigint   | 后台事务commit数量。                 |
+| bg_rollback_counter | bigint   | 后台事务rollback数量。               |
+| bg_resp_min         | bigint   | 后台事务最小响应时间（单位：微秒）。 |
+| bg_resp_max         | bigint   | 后台事务最大响应时间（单位：微秒）。 |
+| bg_resp_avg         | bigint   | 后台事务平均响应时间（单位：微秒）。 |
+| bg_resp_total       | bigint   | 后台事务总响应时间（单位：微秒）。   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/WORKLOAD_SQL_COUNT.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/WORKLOAD_SQL_COUNT.md
new file mode 100644
index 0000000000000000000000000000000000000000..8a86e83463b96fad1f5267a9deff723754f0700f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/WORKLOAD_SQL_COUNT.md
@@ -0,0 +1,23 @@
+---
+title: WORKLOAD_SQL_COUNT
+summary: WORKLOAD_SQL_COUNT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# WORKLOAD_SQL_COUNT
+
+显示当前节点workload上的SQL数量分布。普通用户只可以看到自己在workload上的SQL分布；初始用户可以看到总的workload的负载情况。
+
+**表 1** WORKLOAD_SQL_COUNT字段
+
+| **名称**     | **类型** | **描述**     |
+| :----------- | :------- | :----------- |
+| workload     | name     | 负载名称。   |
+| select_count | bigint   | select数量。 |
+| update_count | bigint   | update数量。 |
+| insert_count | bigint   | insert数量。 |
+| delete_count | bigint   | delete数量。 |
+| ddl_count    | bigint   | ddl数量。    |
+| dml_count    | bigint   | dml数量。    |
+| dcl_count    | bigint   | dcl数量。    |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/WORKLOAD_SQL_ELAPSE_TIME.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/WORKLOAD_SQL_ELAPSE_TIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..9914a97c11ed09f61d309b0ec02ed845673ff897
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/WORKLOAD_SQL_ELAPSE_TIME.md
@@ -0,0 +1,32 @@
+---
+title: WORKLOAD_SQL_ELAPSE_TIME
+summary: WORKLOAD_SQL_ELAPSE_TIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# WORKLOAD_SQL_ELAPSE_TIME
+
+WORKLOAD_SQL_ELAPSE_TIME用来统计workload（业务负载）上的SUID信息。
+
+**表 1** WORKLOAD_SQL_ELAPSE_TIME字段
+
+| **名称**            | **类型** | **描述**                             |
+| :------------------ | :------- | :----------------------------------- |
+| workload            | name     | workload（业务负载）名称。           |
+| total_select_elapse | bigint   | 总select的时间花费（单位: 微秒）。   |
+| max_select_elapse   | bigint   | 最大select的时间花费（单位: 微秒）。 |
+| min_select_elapse   | bigint   | 最小select的时间花费（单位: 微秒）。 |
+| avg_select_elapse   | bigint   | 平均select的时间花费（单位: 微秒）。 |
+| total_update_elapse | bigint   | 总update的时间花费（单位: 微秒）。   |
+| max_update_elapse   | bigint   | 最大update的时间花费（单位: 微秒）。 |
+| min_update_elapse   | bigint   | 最小update的时间花费（单位: 微秒）。 |
+| avg_update_elapse   | bigint   | 平均update的时间花费（单位: 微秒）。 |
+| total_insert_elapse | bigint   | 总insert的时间花费（单位: 微秒）。   |
+| max_insert_elapse   | bigint   | 最大insert的时间花费（单位: 微秒）。 |
+| min_insert_elapse   | bigint   | 最小insert的时间花费（单位: 微秒）。 |
+| avg_insert_elapse   | bigint   | 平均insert的时间花费（单位: 微秒）。 |
+| total_delete_elapse | bigint   | 总delete的时间花费（单位: 微秒）。   |
+| max_delete_elapse   | bigint   | 最大delete的时间花费（单位: 微秒）。 |
+| min_delete_elapse   | bigint   | 最小delete的时间花费（单位: 微秒）。 |
+| avg_delete_elapse   | bigint   | 平均delete的时间花费（单位: 微秒）。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/WORKLOAD_TRANSACTION.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/WORKLOAD_TRANSACTION.md
new file mode 100644
index 0000000000000000000000000000000000000000..ad6a8e8e56f0ae45a20a00d831bf3333e6db5683
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PERF/workload/WORKLOAD_TRANSACTION.md
@@ -0,0 +1,28 @@
+---
+title: WORKLOAD_TRANSACTION
+summary: WORKLOAD_TRANSACTION
+author: Guo Huan
+date: 2021-04-19
+---
+
+# WORKLOAD_TRANSACTION
+
+当前节点上负载的事务信息。
+
+**表 1** WORKLOAD_TRANSACTION字段
+
+| **名称**            | **类型** | **描述**                             |
+| :------------------ | :------- | :----------------------------------- |
+| workload            | name     | 负载的名称。                         |
+| commit_counter      | bigint   | 用户事务commit数量。                 |
+| rollback_counter    | bigint   | 用户事务rollback数量。               |
+| resp_min            | bigint   | 用户事务最小响应时间（单位: 微秒）。 |
+| resp_max            | bigint   | 用户事务最大响应时间（单位: 微秒）。 |
+| resp_avg            | bigint   | 用户事务平均响应时间（单位: 微秒）。 |
+| resp_total          | bigint   | 用户事务总响应时间（单位: 微秒）。   |
+| bg_commit_counter   | bigint   | 后台事务commit数量。                 |
+| bg_rollback_counter | bigint   | 后台事务rollback数量。               |
+| bg_resp_min         | bigint   | 后台事务最小响应时间（单位: 微秒）。 |
+| bg_resp_max         | bigint   | 后台事务最大响应时间（单位: 微秒）。 |
+| bg_resp_avg         | bigint   | 后台事务平均响应时间（单位: 微秒）。 |
+| bg_resp_total       | bigint   | 后台事务总响应时间（单位: 微秒）。   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.abort.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.abort.md
new file mode 100644
index 0000000000000000000000000000000000000000..1b71f84bfca530528a196bf36ec570b38a658578
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.abort.md
@@ -0,0 +1,23 @@
+---
+title: DBE_PLDEBUGGER.abort
+summary: DBE_PLDEBUGGER.abort
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DBE_PLDEBUGGER.abort
+
+令server端执行的存储过程报错跳出。返回值表示是否成功发送abort。
+
+函数原型为：
+
+```sql
+DBE_PLDEBUGGER.abort()
+RETURN boolean;
+```
+
+**表 1** abort 返回值列表
+
+| 名称  | 类型        | 描述             |
+| :---- | :---------- | :--------------- |
+| abort | OUT boolean | 表示成功或失败。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.add_breakpoint.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.add_breakpoint.md
new file mode 100644
index 0000000000000000000000000000000000000000..49340cf210754260f0bbc0d3e4bff8d4ff0a9b7c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.add_breakpoint.md
@@ -0,0 +1,18 @@
+---
+title: DBE_PLDEBUGGER.add_breakpoint
+summary: DBE_PLDEBUGGER.add_breakpoint
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DBE_PLDEBUGGER.add_breakpoint
+
+debug端调试过程中，调用add_breakpoint增加新的断点。如果返回-1则说明指定的断点不合法，请参考[DBE_PLDEBUGGER.info_code](DBE_PLDEBUGGER.info_code)的canbreak字段确定断点合适的位置。
+
+**表 1** add_breakpoint入参和返回值列表
+
+| 名称         | 类型        | 描述       |
+| :----------- | :---------- | :--------- |
+| funcoid      | IN text     | 函数ID。   |
+| lineno       | IN integer  | 行号。     |
+| breakpointno | OUT integer | 断点编号。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.attach.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.attach.md
new file mode 100644
index 0000000000000000000000000000000000000000..306efd4adb903f7266f4c332d9e58ca06252b895
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.attach.md
@@ -0,0 +1,23 @@
+---
+title: DBE_PLDEBUGGER.attach
+summary: DBE_PLDEBUGGER.attach
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DBE_PLDEBUGGER.attach
+
+server端执行存储过程，停在第一条语句前，等待debug端关联。debug端调用attach，传入nodename和port，关联到该存储过程上。
+
+如果调试过程中报错，attach会自动失效；如果调试过程中attach到其他存储过程上，当前attach的调试也会失效。
+
+**表 1** attach 入参和返回值列表
+
+| 名称     | 类型        | 描述                       |
+| :------- | :---------- | :------------------------- |
+| nodename | IN text     | 节点名称。                 |
+| port     | IN integer  | 连接端口号。               |
+| funcoid  | OUT oid     | 函数id。                   |
+| funcname | OUT text    | 函数名。                   |
+| lineno   | OUT integer | 当前调试运行的下一行行号。 |
+| query    | OUT text    | 当前调试的下一行函数源码。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.backtrace.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.backtrace.md
new file mode 100644
index 0000000000000000000000000000000000000000..748cf4c0ef56365ddff8da54a698fb023d1ec420
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.backtrace.md
@@ -0,0 +1,20 @@
+---
+title: DBE_PLDEBUGGER.backtrace
+summary: DBE_PLDEBUGGER.backtrace
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DBE_PLDEBUGGER.backtrace
+
+debug端调试过程中，调用backtrace，查看当前的调用堆栈。
+
+**表 1** backtrace返回值列表
+
+| 名称     | 类型        | 描述         |
+| :------- | :---------- | :----------- |
+| frameno  | OUT integer | 调用栈编号。 |
+| funcname | OUT oid     | 函数名。     |
+| lineno   | OUT integer | 行号。       |
+| query    | OUT text    | 断点内容。   |
+| funcoid  | OUT oid     | 函数oid。    |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.continue.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.continue.md
new file mode 100644
index 0000000000000000000000000000000000000000..08590aae3bc8fabfd247b8388a0a2d9d6120e690
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.continue.md
@@ -0,0 +1,26 @@
+---
+title: DBE_PLDEBUGGER.continue
+summary: DBE_PLDEBUGGER.continue
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DBE_PLDEBUGGER.continue
+
+执行当前存储过程，直到下一个断点或结束。返回值表示执行的下一条的行数和对应query。
+
+函数原型为：
+
+```sql
+DBE_PLDEBUGGER.continue()
+RETURN Record;
+```
+
+**表 1** continue 返回值列表
+
+| 名称     | 类型        | 描述                       |
+| :------- | :---------- | :------------------------- |
+| funcoid  | OUT oid     | 函数id。                   |
+| funcname | OUT text    | 函数名。                   |
+| lineno   | OUT integer | 当前调试运行的下一行行号。 |
+| query    | OUT text    | 当前调试的下一行函数源码。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.delete_breakpoint.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.delete_breakpoint.md
new file mode 100644
index 0000000000000000000000000000000000000000..4583f4903441aaa34f398ea6d99c84a242b18cdc
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.delete_breakpoint.md
@@ -0,0 +1,17 @@
+---
+title: DBE_PLDEBUGGER.delete_breakpoint
+summary: DBE_PLDEBUGGER.delete_breakpoint
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DBE_PLDEBUGGER.delete_breakpoint
+
+debug端调试过程中，调用delete_breakpoint删除已有的断点。
+
+**表 1** delete_breakpoint入参和返回值列表
+
+| 名称         | 类型       | 描述       |
+| :----------- | :--------- | :--------- |
+| breakpointno | IN integer | 断点编号。 |
+| result       | OUT bool   | 是否成功。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.finish.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.finish.md
new file mode 100644
index 0000000000000000000000000000000000000000..05d6c2c135229d9cb0b2a00cb19185cf90292fda
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.finish.md
@@ -0,0 +1,19 @@
+---
+title: DBE_PLDEBUGGER.finish
+summary: DBE_PLDEBUGGER.finish
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DBE_PLDEBUGGER.finish
+
+执行存储过程中当前的SQL直到下一个断点触发或执行到上层栈的下一行。
+
+**表 1** finish入参和返回值列表
+
+| 名称     | 类型        | 描述                       |
+| :------- | :---------- | :------------------------- |
+| funcoid  | OUT oid     | 函数id。                   |
+| funcname | OUT text    | 函数名。                   |
+| lineno   | OUT integer | 当前调试运行的下一行行号。 |
+| query    | OUT text    | 当前调试的下一行函数源码。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.info_breakpoints.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.info_breakpoints.md
new file mode 100644
index 0000000000000000000000000000000000000000..b594f71866514cbd374d3bcb2df0ee703b3d6437
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.info_breakpoints.md
@@ -0,0 +1,19 @@
+---
+title: DBE_PLDEBUGGER.info_breakpoints
+summary: DBE_PLDEBUGGER.info_breakpoints
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DBE_PLDEBUGGER.info_breakpoints
+
+debug端调试过程中，调用info_breakpoints，查看当前的函数断点。
+
+**表 1** info_breakpoints返回值列表
+
+| 名称         | 类型        | 描述       |
+| :----------- | :---------- | :--------- |
+| breakpointno | OUT integer | 断点编号。 |
+| funcoid      | OUT oid     | 函数ID。   |
+| lineno       | OUT integer | 行号。     |
+| query        | OUT text    | 断点内容。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.info_code.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.info_code.md
new file mode 100644
index 0000000000000000000000000000000000000000..3b3bcce9c6be5a25ea072f06962317e0f884ee76
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.info_code.md
@@ -0,0 +1,19 @@
+---
+title: DBE_PLDEBUGGER.info_code
+summary: DBE_PLDEBUGGER.info_code
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DBE_PLDEBUGGER.info_code
+
+debug端调试过程中，调用info_code，查看指定存储过程的源语句和各行对应的行号，行号从函数体开始，函数头部分行号为空。
+
+**表 1** info_code入参和返回值列表
+
+| 名称     | 类型        | 描述                 |
+| :------- | :---------- | :------------------- |
+| funcoid  | IN oid      | 函数ID。             |
+| lineno   | OUT integer | 行号。               |
+| query    | OUT text    | 源语句。             |
+| canbreak | OUT bool    | 当前行是否支持断点。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.local_debug_server_info.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.local_debug_server_info.md
new file mode 100644
index 0000000000000000000000000000000000000000..00e0085d446708bddcb547a6465b7d239b6beb9c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.local_debug_server_info.md
@@ -0,0 +1,18 @@
+---
+title: DBE_PLDEBUGGER.local_debug_server_info
+summary: DBE_PLDEBUGGER.local_debug_server_info
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DBE_PLDEBUGGER.local_debug_server_info
+
+用于查找当前连接中已经turn_on的存储过程oid。便于用户确认在调试哪些存储过程，需要通过funcoid和pg_proc配合使用。
+
+**表 1** local_debug_server_info 返回值列表
+
+| 名称     | 类型       | 描述          |
+| :------- | :--------- | :------------ |
+| nodename | OUT text   | 节点名称。    |
+| port     | OUT bigint | 端口号。      |
+| funcoid  | OUT oid    | 存储过程oid。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.next.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.next.md
new file mode 100644
index 0000000000000000000000000000000000000000..50477bdeb460e0006a569629f303568d0d48b159
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.next.md
@@ -0,0 +1,19 @@
+---
+title: DBE_PLDEBUGGER.next
+summary: DBE_PLDEBUGGER.next
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DBE_PLDEBUGGER.next
+
+执行存储过程中当前的sql，返回执行的下一条的行数和对应query。
+
+**表 1** next返回值列表
+
+| 名称     | 类型        | 描述                       |
+| :------- | :---------- | :------------------------- |
+| funcoid  | OUT oid     | 函数id。                   |
+| funcname | OUT text    | 函数名。                   |
+| lineno   | OUT integer | 当前调试运行的下一行行号。 |
+| query    | OUT text    | 当前调试的下一行函数源码。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.print_var.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.print_var.md
new file mode 100644
index 0000000000000000000000000000000000000000..5b78dcf3e92fb18a3ee35ccd8dfd7f406c4300e9
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.print_var.md
@@ -0,0 +1,22 @@
+---
+title: DBE_PLDEBUGGER.print_var
+summary: DBE_PLDEBUGGER.print_var
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DBE_PLDEBUGGER.print_var
+
+debug端调试过程中，调用print_var，打印当前存储过程内变量中指定的变量名及其取值。该函数入参frameno表示查询遍历的栈层数，支持不加入该参数调用，缺省为查看最上层栈变量。
+
+**表 1** print_var入参和返回值列表
+
+| 名称         | 类型               | 描述                                        |
+| :----------- | :----------------- | :------------------------------------------ |
+| var_name     | IN text            | 变量。                                      |
+| frameno      | IN integer（可选） | 指定的栈层数，缺省为最顶层。                |
+| varname      | OUT text           | 变量名。                                    |
+| vartype      | OUT text           | 变量类型。                                  |
+| value        | OUT text           | 变量值。                                    |
+| package_name | OUT text           | 变量对应的package名，预留使用，当前均为空。 |
+| isconst      | OUT boolean        | 是否为常量。                                |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.set_var.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.set_var.md
new file mode 100644
index 0000000000000000000000000000000000000000..30d4dff2a52a86e144c72311869799793476a04c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.set_var.md
@@ -0,0 +1,18 @@
+---
+title: DBE_PLDEBUGGER.set_var
+summary: DBE_PLDEBUGGER.set_var
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DBE_PLDEBUGGER.set_var
+
+将指定的调试的存储过程中最上层栈上的变量修改为入参的取值。如果存储过程中包含同名的变量，set_var只支持第一个变量值的设置。
+
+**表 1** set_var入参和返回值列表
+
+| 名称     | 类型        | 描述             |
+| :------- | :---------- | :--------------- |
+| var_name | IN text     | 变量名。         |
+| value    | IN text     | 修改值。         |
+| result   | OUT boolean | 结果，是否成功。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.step.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.step.md
new file mode 100644
index 0000000000000000000000000000000000000000..bf3e4cfcbced598299abe8cf4c659c272684bc6d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.step.md
@@ -0,0 +1,19 @@
+---
+title: DBE_PLDEBUGGER.step
+summary: DBE_PLDEBUGGER.step
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DBE_PLDEBUGGER.step
+
+debug端调试过程中，如果当前执行的是一个存储过程，则进入该存储过程继续调试，返回该存储过程第一行的行号等信息，如果当前执行的不是存储过程，则和next行为一致，执行该sql后返回下一行的行号等信息。
+
+**表 1** step入参和返回值列表
+
+| 名称     | 类型        | 描述                       |
+| :------- | :---------- | :------------------------- |
+| funcoid  | OUT oid     | 函数id。                   |
+| funcname | OUT text    | 函数名。                   |
+| lineno   | OUT integer | 当前调试运行的下一行行号。 |
+| query    | OUT text    | 当前调试的下一行函数源码。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.turn_off.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.turn_off.md
new file mode 100644
index 0000000000000000000000000000000000000000..0d5951c3de2677b1de7958b74a26cf792ba8a6a2
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.turn_off.md
@@ -0,0 +1,24 @@
+---
+title: DBE_PLDEBUGGER.turn_off
+summary: DBE_PLDEBUGGER.turn_off
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DBE_PLDEBUGGER.turn_off
+
+用于去掉turn_on添加的调试标记，返回值表示成功或失败。可通过DBE_PLDEBUGGER.local_debug_server_info查找已经turn_on的存储过程oid。
+
+函数原型为：
+
+```sql
+DBE_PLDEBUGGER.turn_off(Oid)
+RETURN boolean;
+```
+
+**表 1** turn_off 入参和返回值列表
+
+| 名称     | 类型        | 描述               |
+| :------- | :---------- | :----------------- |
+| func_oid | IN oid      | 函数oid。          |
+| turn_off | OUT boolean | turn off是否成功。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.turn_on.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.turn_on.md
new file mode 100644
index 0000000000000000000000000000000000000000..900052d1ebc37ddbc469b54af0f97b8702b0111e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.turn_on.md
@@ -0,0 +1,25 @@
+---
+title: DBE_PLDEBUGGER.turn_on
+summary: DBE_PLDEBUGGER.turn_on
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DBE_PLDEBUGGER.turn_on
+
+该函数用于标记某一存储过程为可调试，执行turn_on后server端可以执行该存储过程来进行调试。需要用户根据系统表PG_PROC手动获取存储过程oid，传入函数中。turn_on后本session内执行该存储过程会停在第一条sql前等待debug端的调试操作。该设置会在session断连后默认被清理掉。目前不支持对启用自治事务的存储过程/函数进行调试。
+
+函数原型为：
+
+```sql
+DBE_PLDEBUGGER.turn_on(Oid)
+RETURN Record;
+```
+
+**表 1** turn_on 入参和返回值列表
+
+| 名称     | 类型        | 描述         |
+| :------- | :---------- | :----------- |
+| func_oid | IN oid      | 函数oid。    |
+| nodename | OUT text    | 节点名称。   |
+| port     | OUT integer | 连接端口号。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/overview-of-DBE_PLDEBUGGER-schema.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/overview-of-DBE_PLDEBUGGER-schema.md
new file mode 100644
index 0000000000000000000000000000000000000000..9b906dc0726b17103150ea0909871b3e3443e4ff
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/DBE_PLDEBUGGER-schema/overview-of-DBE_PLDEBUGGER-schema.md
@@ -0,0 +1,128 @@
+---
+title: DBE_PLDEBUGGER Schema概述
+summary: DBE_PLDEBUGGER Schema概述
+author: Guo Huan
+date: 2021-11-15
+---
+
+# DBE_PLDEBUGGER Schema概述
+
+DBE_PLDEBUGGER下系统函数用于单机下调试存储过程，目前支持的接口及其描述如下所示。仅管理员有权限执行这些调试接口。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 当在函数体中创建用户时，调用attach、next、continue、 info_code、step、info_breakpoint、backtrace、 finish中会返回密码的明文。因此不建议用户在函数体中创建用户。
+
+对应权限角色为gs_role_pldebugger，可以由管理员用户通过如下命令将debugger权限赋权给该用户。
+
+```sql
+GRANT gs_role_pldebugger to user;
+```
+
+需要有两个客户端连接数据库，一个客户端负责执行调试接口作为debug端，另一个客户端执行调试函数，控制server端存储过程执行。示例如下。
+
+- 准备调试
+
+  通过PG_PROC，查找到待调试存储过程的oid，并执行DBE_PLDEBUGGER.turn_on(oid)。本客户端就会作为server端使用。
+
+  ```sql
+  mogdb=# CREATE OR REPLACE PROCEDURE test_debug ( IN  x INT)
+  AS
+  BEGIN
+        INSERT INTO t1 (a) VALUES (x);
+  END;
+  /
+  CREATE PROCEDURE
+  mogdb=# SELECT OID FROM PG_PROC WHERE PRONAME='test_debug';
+    oid
+  -------
+   16389
+  (1 row)
+  mogdb=# SELECT * FROM DBE_PLDEBUGGER.turn_on(16389);
+   nodename | port
+  ----------+------
+   datanode |    0
+  (1 row)
+  ```
+
+- 开始调试
+
+  server端执行存储过程，会在存储过程内第一条SQL语句前hang住，等待debug端发送的调试消息。仅支持直接执行存储过程的调试，不支持通过trigger调用执行的存储过程调试。
+
+  ```sql
+  mogdb=# call test_debug(1);
+  ```
+
+  再起一个客户端，作为debug端，通过turn_on返回的数据，调用DBE_PLDEBUGGER.attach关联到该存储过程上进行调试。
+
+  ```sql
+  mogdb=# SELECT * FROM DBE_PLDEBUGGER.attach('datanode',0);
+   funcoid |  funcname  | lineno |              query
+  ---------+------------+--------+----------------------------------
+     16389 | test_debug |      3 |   INSERT INTO t1 (a) VALUES (x);
+  (1 row)
+  ```
+
+  在执行attach的客户端调试，执行下一条statement。
+
+  ```sql
+  mogdb=# SELECT * FROM DBE_PLDEBUGGER.next();
+   funcoid |  funcname  | lineno |        query
+  ---------+------------+--------+----------------------
+     16389 | test_debug |      0 | [EXECUTION FINISHED]
+  (1 row)
+  ```
+
+  在执行attach的客户端调试，将当前所有变量输出。
+
+  ```sql
+  mogdb=# SELECT * FROM DBE_PLDEBUGGER.info_locals();
+   varname | vartype | value | package_name
+  ---------+---------+-------+--------------
+   $1      | int4    | 1     |
+  (1 row)
+  ```
+
+  直接执行完成当前正在调试的存储过程。
+
+  ```sql
+  mogdb=# SELECT * FROM DBE_PLDEBUGGER.continue();
+   funcoid |  funcname  | lineno |        query
+  ---------+------------+--------+----------------------
+     16389 | test_debug |      0 | [EXECUTION FINISHED]
+  (1 row)
+  ```
+
+  直接退出当前正在调试的存储过程，不执行尚未执行的语句。
+
+  ```sql
+  mogdb=# SELECT * FROM DBE_PLDEBUGGER.abort();
+   abort
+  -------
+   t
+  (1 row)
+  ```
+
+  存储过程执行结束后，调试会自动退出，再进行调试需要重新attach关联。如果server端不需要继续调试，可执行turn_off关闭，或退出session。具体调试接口请见下面列表。
+
+  **表 1** DBE_PLDEBUGGER
+
+  | 接口名称                                                     | 描述                                                         |
+  | :----------------------------------------------------------- | :----------------------------------------------------------- |
+  | [DBE_PLDEBUGGER.turn_on](DBE_PLDEBUGGER.turn_on)             | server端调用，标记存储过程可以调试，调用后执行该存储过程时会hang住等待调试信息。 |
+  | [DBE_PLDEBUGGER.turn_off](DBE_PLDEBUGGER.turn_off)           | server端调用，标记存储过程关闭调试。                         |
+  | [DBE_PLDEBUGGER.local_debug_server_info](DBE_PLDEBUGGER.local_debug_server_info) | server端调用，打印本session内所有已turn_on的存储过程。       |
+  | [DBE_PLDEBUGGER.attach](DBE_PLDEBUGGER.attach)               | debug端调用，关联到正在调试存储过程。                        |
+  | [DBE_PLDEBUGGER.info_locals](DBE_PLDEBUGGER.info_locals)     | debug端调用，打印正在调试的存储过程中的变量当前值。          |
+  | [DBE_PLDEBUGGER.next](DBE_PLDEBUGGER.next)                   | debug端调用，单步执行。                                      |
+  | [DBE_PLDEBUGGER.continue](DBE_PLDEBUGGER.continue)           | debug端调用，继续执行，直到断点或存储过程结束。              |
+  | [DBE_PLDEBUGGER.abort](DBE_PLDEBUGGER.abort)                 | debug端调用，停止调试，server端报错长跳转。                  |
+  | [DBE_PLDEBUGGER.print_var](DBE_PLDEBUGGER.print_var)         | debug端调用，打印正在调试的存储过程中指定的变量当前值。      |
+  | [DBE_PLDEBUGGER.info_code](DBE_PLDEBUGGER.info_code)         | debug和server端都可以调用，打印指定存储过程的源语句和各行对应的行号。 |
+  | [DBE_PLDEBUGGER.step](DBE_PLDEBUGGER.step)                   | debug端调用，单步进入执行。                                  |
+  | [DBE_PLDEBUGGER.add_breakpoint](DBE_PLDEBUGGER.add_breakpoint) | debug端调用，新增断点。                                      |
+  | [DBE_PLDEBUGGER.delete_breakpoint](DBE_PLDEBUGGER.delete_breakpoint) | debug端调用，删除断点。                                      |
+  | [DBE_PLDEBUGGER.info_breakpoints](DBE_PLDEBUGGER.info_breakpoints) | debug端调用，查看当前的所有断点。                            |
+  | [DBE_PLDEBUGGER.backtrace](DBE_PLDEBUGGER.backtrace)         | debug端调用，查看当前的调用栈。                              |
+  | [DBE_PLDEBUGGER.enable_breakpoint](DBE_PLDEBUGGER.enable_breakpoint) | debug端调用，激活被禁用的断点。                              |
+  | [DBE_PLDEBUGGER.disable_breakpoint](DBE_PLDEBUGGER.disable_breakpoint) | debug端调用，禁用已激活的断点。                              |
+  | [DBE_PLDEBUGGER.finish](DBE_PLDEBUGGER.finish)               | debug端调用，继续调试，直到断点或返回上一层调用栈。          |
+  | [DBE_PLDEBUGGER.set_var](DBE_PLDEBUGGER.set_var)             | debug端调用，为变量进行赋值操作。                            |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/information-schema/1-information-schema-overview.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/information-schema/1-information-schema-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..9586f62ef1185ea7e13548dde7b213d695417de1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/information-schema/1-information-schema-overview.md
@@ -0,0 +1,18 @@
+---
+title: 概述
+summary: 概述
+author: Guo Huan
+date: 2021-06-23
+---
+
+# 概述
+
+信息模式本身是一个名为information_schema的模式。这个模式自动存在于所有数据库中。信息模式由一组视图构成，它们包含定义在当前数据库中对象的信息。这个模式的拥有者是初始数据库用户，并且该用户自然地拥有这个模式上的所有特权，包括删除它的能力。
+
+信息模式继承自开源PGXC/PG，相关细节描述请参见PGXC/PG官方文档，链接如下：
+
+<http://postgres-xc.sourceforge.net/docs/1_1/information-schema.html>
+
+<https://www.postgresql.org/docs/9.2/information-schema.html>
+
+后续章节只显示未在上述链接内的视图信息。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/information-schema/2-_PG_FOREIGN_DATA_WRAPPERS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/information-schema/2-_PG_FOREIGN_DATA_WRAPPERS.md
new file mode 100644
index 0000000000000000000000000000000000000000..4c5cc3bf9610728109fc1e804ed3d71b8f0e3485
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/information-schema/2-_PG_FOREIGN_DATA_WRAPPERS.md
@@ -0,0 +1,22 @@
+---
+title: _PG_FOREIGN_DATA_WRAPPERS
+summary: _PG_FOREIGN_DATA_WRAPPERS
+author: Guo Huan
+date: 2021-06-23
+---
+
+# _PG_FOREIGN_DATA_WRAPPERS
+
+显示外部数据封装器的信息。该视图只有sysadmin权限可以查看。
+
+**表 1** _PG_FOREIGN_DATA_WRAPPERS字段
+
+| **名称**                      | **类型**                          | **描述**                                                  |
+| ----------------------------- | --------------------------------- | --------------------------------------------------------- |
+| oid                           | oid                               | 外部数据封装器的oid。                                     |
+| fdwowner                      | oid                               | 外部数据封装器的所有者的oid。                             |
+| fdwoptions                    | text[]                            | 外部数据封装器指定选项，使用“keyword=value”格式的字符串。 |
+| foreign_data_wrapper_catalog  | information_schema.sql_identifier | 外部封装器所在的数据库名称（永远为当前数据库）。          |
+| foreign_data_wrapper_name     | information_schema.sql_identifier | 外部数据封装器名称。                                      |
+| authorization_identifier      | information_schema.sql_identifier | 外部数据封装器所有者的角色名称。                          |
+| foreign_data_wrapper_language | information_schema.character_data | 外部数据封装器的实现语言。                                |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/information-schema/3-_PG_FOREIGN_SERVERS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/information-schema/3-_PG_FOREIGN_SERVERS.md
new file mode 100644
index 0000000000000000000000000000000000000000..74b6139cf6242d90585c3dd24e733239652b90c0
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/information-schema/3-_PG_FOREIGN_SERVERS.md
@@ -0,0 +1,24 @@
+---
+title: _PG_FOREIGN_SERVERS
+summary: _PG_FOREIGN_SERVERS
+author: Guo Huan
+date: 2021-06-23
+---
+
+# _PG_FOREIGN_SERVERS
+
+显示外部服务器的信息。该视图只有sysadmin权限可以查看。
+
+**表 1** _PG_FOREIGN_SERVERS字段
+
+| **名称**                     | **类型**                          | **描述**                                              |
+| ---------------------------- | --------------------------------- | ----------------------------------------------------- |
+| oid                          | oid                               | 外部服务器的oid。                                     |
+| srvoptions                   | text[]                            | 外部服务器指定选项，使用“keyword=value”格式的字符串。 |
+| foreign_server_catalog       | information_schema.sql_identifier | 外部服务器所在database名称（永远为当前数据库）。      |
+| foreign_server_name          | information_schema.sql_identifier | 外部服务器名称。                                      |
+| foreign_data_wrapper_catalog | information_schema.sql_identifier | 外部数据封装器所在database名称（永远为当前数据库）。  |
+| foreign_data_wrapper_name    | information_schema.sql_identifier | 外部数据封装器名称。                                  |
+| foreign_server_type          | information_schema.character_data | 外部服务器的类型。                                    |
+| foreign_server_version       | information_schema.character_data | 外部服务器的版本。                                    |
+| authorization_identifier     | information_schema.sql_identifier | 外部服务器的所有者的角色名称。                        |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/information-schema/4-_PG_FOREIGN_TABLE_COLUMNS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/information-schema/4-_PG_FOREIGN_TABLE_COLUMNS.md
new file mode 100644
index 0000000000000000000000000000000000000000..a6b7bd6aa908a984f4e9ee999f4cd6f7aef93c14
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/information-schema/4-_PG_FOREIGN_TABLE_COLUMNS.md
@@ -0,0 +1,19 @@
+---
+title: _PG_FOREIGN_TABLE_COLUMNS
+summary: _PG_FOREIGN_TABLE_COLUMNS
+author: Guo Huan
+date: 2021-06-23
+---
+
+# _PG_FOREIGN_TABLE_COLUMNS
+
+显示外部表的列信息。该视图只有sysadmin权限可以查看。
+
+**表 1** _PG_FOREIGN_TABLE_COLUMNS字段
+
+| **名称**      | **类型** | **描述**                                                    |
+| ------------- | -------- | ----------------------------------------------------------- |
+| nspname       | name     | schema名称。                                                |
+| relname       | name     | 表名称。                                                    |
+| attname       | name     | 列名称。                                                    |
+| attfdwoptions | text[]   | 外部数据封装器的属性选项，使用“keyword=value”格式的字符串。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/information-schema/5-_PG_FOREIGN_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/information-schema/5-_PG_FOREIGN_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..2eef62059476a798270c990fc26c869dd0ff9c3d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/information-schema/5-_PG_FOREIGN_TABLES.md
@@ -0,0 +1,22 @@
+---
+title: _PG_FOREIGN_TABLES
+summary: _PG_FOREIGN_TABLES
+author: Guo Huan
+date: 2021-06-23
+---
+
+# _PG_FOREIGN_TABLES
+
+存储所有的定义在本数据库的外部表信息。只显示当前用户有权访问的外部表信息。该视图只有sysadmin权限可以查看。
+
+**表 1** _PG_FOREIGN_TABLES字段
+
+| **名称**                 | **类型**                          | **描述**                                         |
+| ------------------------ | --------------------------------- | ------------------------------------------------ |
+| foreign_table_catalog    | information_schema.sql_identifier | 外部表所在的数据库名称（永远是当前数据库）。     |
+| foreign_table_schema     | name                              | 外部表的schema名称。                             |
+| foreign_table_name       | name                              | 外部表的名称。                                   |
+| ftoptions                | text[]                            | 外部表的可选项。                                 |
+| foreign_server_catalog   | information_schema.sql_identifier | 外部服务器所在的数据库名称（永远是当前数据库）。 |
+| foreign_server_name      | information_schema.sql_identifier | 外部服务器的名称。                               |
+| authorization_identifier | information_schema.sql_identifier | 所有者的角色名称。                               |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/information-schema/6-_PG_USER_MAPPINGS.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/information-schema/6-_PG_USER_MAPPINGS.md
new file mode 100644
index 0000000000000000000000000000000000000000..9300dd02d4d07350364c7fa4b2d0ecdc92dc9434
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/information-schema/6-_PG_USER_MAPPINGS.md
@@ -0,0 +1,22 @@
+---
+title: _PG_USER_MAPPINGS
+summary: _PG_USER_MAPPINGS
+author: Guo Huan
+date: 2021-06-23
+---
+
+# _PG_USER_MAPPINGS
+
+存储从本地用户到远程的映射。该视图只有sysadmin权限可以查看。
+
+**表 1** _PG_USER_MAPPINGS字段
+
+| **名称**                 | **类型**                          | **描述**                                            |
+| ------------------------ | --------------------------------- | --------------------------------------------------- |
+| oid                      | oid                               | 从本地用户到远程的映射的oid。                       |
+| umoptions                | text[]                            | 用户映射指定选项，使用”keyword=value”格式的字符串。 |
+| umuser                   | oid                               | 被映射的本地用户的OID，如果用户映射是公共的则为0。  |
+| authorization_identifier | information_schema.sql_identifier | 本地用户角色名称。                                  |
+| foreign_server_catalog   | information_schema.sql_identifier | 外部服务器定义所在的database名称。                  |
+| foreign_server_name      | information_schema.sql_identifier | 外部服务器名称。                                    |
+| srvowner                 | information_schema.sql_identifier | 外部服务器所有者。                                  |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/schema/information-schema/7-INFORMATION_SCHEMA_CATALOG_NAME.md b/product/zh/docs-mogdb/v3.0/reference-guide/schema/information-schema/7-INFORMATION_SCHEMA_CATALOG_NAME.md
new file mode 100644
index 0000000000000000000000000000000000000000..f31ab8fcaaefcc60f48a0e709bd0952f09a6c135
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/schema/information-schema/7-INFORMATION_SCHEMA_CATALOG_NAME.md
@@ -0,0 +1,16 @@
+---
+title: INFORMATION_SCHEMA_CATALOG_NAME
+summary: INFORMATION_SCHEMA_CATALOG_NAME
+author: Guo Huan
+date: 2021-06-23
+---
+
+# INFORMATION_SCHEMA_CATALOG_NAME
+
+用来显示当前所在的database的名称。
+
+**表 1** INFORMATION_SCHEMA_CATALOG_NAME字段
+
+| **名称**     | **类型**                          | **描述**             |
+| :----------- | :-------------------------------- | :------------------- |
+| catalog_name | information_schema.sql_identifier | 当前database的名称。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/1-mogdb-sql.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/1-mogdb-sql.md
new file mode 100644
index 0000000000000000000000000000000000000000..5c093ea5ea5ebcb518efdb71137668a7a42ac838
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/1-mogdb-sql.md
@@ -0,0 +1,37 @@
+---
+title: MogDB SQL
+summary: MogDB SQL
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# MogDB SQL
+
+## 什么是SQL
+
+SQL是用于访问和处理数据库的标准计算机语言。
+
+SQL提供了各种任务的语句，包括：
+
+- 查询数据。
+- 在表中插入、更新和删除行。
+- 创建、替换、更改和删除对象。
+- 控制对数据库及其对象的访问。
+- 保证数据库的一致性和完整性。
+
+SQL语言由用于处理数据库和数据库对象的命令和函数组成。该语言还会强制实施有关数据类型、表达式和文本使用的规则。因此在SQL参考章节，除了SQL语法参考外，还会看到有关数据类型、表达式、函数和操作符等信息。
+
+## SQL发展简史
+
+SQL发展简史如下：
+
+- 1986年，ANSI X3.135-1986，ISO/IEC 9075:1986，SQL-86
+- 1989年，ANSI X3.135-1989，ISO/IEC 9075:1989，SQL-89
+- 1992年，ANSI X3.135-1992，ISO/IEC 9075:1992，SQL-92（SQL2）
+- 1999年，ISO/IEC 9075:1999，SQL:1999（SQL3）
+- 2003年，ISO/IEC 9075:2003，SQL:2003（SQL4）
+- 2011年，ISO/IEC 9075:200N，SQL:2011（SQL5）
+
+## MogDB支持的SQL标准
+
+MogDB默认支持SQL2、SQL3和SQL4的主要特性。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/10-dml-syntax-overview.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/10-dml-syntax-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..492a74e2bd1e8379f5bb03d8633ca2f8eb991353
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/10-dml-syntax-overview.md
@@ -0,0 +1,51 @@
+---
+title: DML语法一览表
+summary: DML语法一览表
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# DML语法一览表
+
+DML（Data Manipulation Language数据操作语言），用于对数据库表中的数据进行操作。如：插入、更新、查询、删除。
+
+## 插入数据
+
+插入数据是往数据库表中添加一条或多条记录，请参考[INSERT](109-INSERT)。
+
+## 修改数据
+
+修改数据是修改数据库表中的一条或多条记录，请参考[UPDATE](136-UPDATE)。
+
+## 查询数据
+
+数据库查询语句SELECT是用于在数据库中检索适合条件的信息，请参考[SELECT](125-SELECT)。
+
+## 删除数据
+
+MogDB提供了两种删除表数据的语句：删除表中指定条件的数据，请参考[DELETE](74-DELETE)；或删除表的所有数据，请参考[TRUNCATE](135-TRUNCATE)。
+
+TRUNCATE快速地从表中删除所有行，它和在每个表上进行无条件的DELETE有同样的效果，不过因为它不做表扫描，因而快得多。在大表上最有用。
+
+## 拷贝数据
+
+MogDB提供了在表和文件之间拷贝数据的语句，请参考[COPY](41-COPY)。
+
+## 锁定表
+
+MogDB提供了多种锁模式用于控制对表中数据的并发访问，请参考[LOCK](110-LOCK)。
+
+## 调用函数
+
+MogDB提供了三个用于调用函数的语句，它们在语法结构上没有差别，请参考[CALL](34-CALL)。
+
+## 操作会话
+
+用户与数据库之间建立的连接称为会话，请参考[表1](#sessionrelated)。
+
+**表 1** 会话相关SQL <a id="sessionrelated"></a>
+
+| 功能     | 相关SQL                                                   |
+| :------- | :-------------------------------------------------------- |
+| 修改会话 | [ALTER SESSION](18-ALTER-SESSION)                         |
+| 结束会话 | [ALTER SYSTEM KILL SESSION](20-ALTER-SYSTEM-KILL-SESSION) |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/11-dcl-syntax-overview.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/11-dcl-syntax-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..c85161c3f9d8a2364bd7ee659f7b8982c5e117c0
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/11-dcl-syntax-overview.md
@@ -0,0 +1,50 @@
+---
+title: DCL语法一览表
+summary: DCL语法一览表
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# DCL语法一览表
+
+DCL（Data Control Language数据控制语言），是用来创建用户角色、设置或更改数据库用户或角色权限的语句。
+
+## 定义角色
+
+角色是用来管理权限的，从数据库安全的角度考虑，可以把所有的管理和操作权限划分到不同的角色上。所涉及的SQL语句，请参考[表1](#roledefi)。
+
+**表 1** 角色定义相关SQL <a id="roledefi"> </a>
+
+| 功能         | 相关SQL                       |
+| :----------- | :---------------------------- |
+| 创建角色     | [CREATE ROLE](54-CREATE-ROLE) |
+| 修改角色属性 | [ALTER ROLE](12-ALTER-ROLE)   |
+| 删除角色     | [DROP ROLE](89-DROP-ROLE)     |
+
+## 定义用户
+
+用户是用来登录数据库的，通过对用户赋予不同的权限，可以方便地管理用户对数据库的访问及操作。所涉及的SQL语句，请参考[表2](#userdefi)。
+
+**表 2** 用户定义相关SQL <a id="userdefi"> </a>
+
+| 功能         | 相关SQL                       |
+| :----------- | :---------------------------- |
+| 创建用户     | [CREATE USER](68-CREATE-USER) |
+| 修改用户属性 | [ALTER USER](29-ALTER-USER)   |
+| 删除用户     | [DROP USER](101-DROP-USER)    |
+
+## 授权
+
+MogDB提供了针对数据对象和角色授权的语句，请参考[GRANT](108-GRANT)。
+
+## 收回权限
+
+MogDB提供了收回权限的语句，请参考[REVOKE](120-REVOKE)。
+
+## 设置默认权限
+
+MogDB允许设置应用于将来创建的对象的权限，请参考[ALTER DEFAULT PRIVILEGES](4-ALTER-DEFAULT-PRIVILEGES)。
+
+## 关闭当前节点
+
+MogDB支持使用shutdown命令关闭当前数据库节点，请参考[SHUTDOWN](133-SHUTDOWN)。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/1-gin-indexes/1-introduction.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/1-gin-indexes/1-introduction.md
new file mode 100644
index 0000000000000000000000000000000000000000..6dd15d74c0729c31ba45c14d38080791e9713e4b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/1-gin-indexes/1-introduction.md
@@ -0,0 +1,16 @@
+---
+title: 介绍
+summary: 介绍
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# 介绍
+
+GIN（Generalized Inverted Index）通用倒排索引。设计为处理索引项为组合值的情况，查询时需要通过索引搜索出出现在组合值中的特定元素值。例如，文档是由多个单词组成，需要查询出文档中包含的特定单词。
+
+使用item表示索引的组合值，key表示一个元素值。GIN用来存储和搜索key，而不是item。
+
+GIN索引存储一系列（key，posting list）键值对，这里的posting list是一组出现key的行ID。由于每个item都可能包含多个key，同一个行ID可能会出现在多个posting list中，而每个key值只被存储一次，所以在相同的key在item中出现多次的情况下，GIN索引是非常简洁的。
+
+因为GIN索引的访问方式不需要了解他的运行方式，所以GIN索引是通用的。GIN索引使用为特殊数据类型定义的策略。策略定义了如何从索引选项和查询条件中抽出key，以及如何确定在查询中包含某些key值的行是否实际满足查询条件。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/1-gin-indexes/2-scalability.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/1-gin-indexes/2-scalability.md
new file mode 100644
index 0000000000000000000000000000000000000000..04451b0e935571cc6cad2c1e6d4edff9beacec84
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/1-gin-indexes/2-scalability.md
@@ -0,0 +1,50 @@
+---
+title: 扩展性
+summary: 扩展性
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# 扩展性
+
+GIN索引的接口实现了一个高层次的抽象，要求访问用户仅需要实现被访问数据类型的语义。GIN层自身可以处理并发操作、记录日志、搜索树结构的任务。
+
+定义GIN索引的访问方式所要做的事情就是实现多个用户定义的方法，这些方法定义了键在树中的行为、键与键之间的关系、需要索引的item、能够使用索引的查询。简而言之，GIN索引将扩展性与普遍性、代码重用、清晰的接口结合在了一起。
+
+实现GIN索引的操作符类有如下四个方法：
+
+- int compare(Datum a, Datum b)
+
+  比较两个key（不是索引的item）然后返回一个小于零、零或大于零的值，分别表示第一个key小于、等于或大于第二个key。NULL不会被传入这个函数。
+
+- Datum `extractValue(Datum itemValue, int32 *nkeys, bool **nullFlags)`
+
+  给定一个要被索引的item，返回一个对应key的数组。返回key的数目必须存储在*nkeys中。如果任何key都可能为NULL，还要分配包含*nkeys个布尔元素的数组，将地址存储到*nullFlags，并且根据需要设置NULL值。 如果所有key都是非NULL，可以让*nullFlags保持为NULL（他的初始值）。如果item不包含任何key，返回值可以为NULL。
+
+- Datum `extractQuery(Datum query, int32 *nkeys, StrategyNumber n, bool **pmatch, Pointer **extra_data, bool **nullFlags, int32 *searchMode)`
+
+  给定一个被查询的值，返回一个对应的key的数组。也就是说，query是可索引操作符右侧的值，而该操作符左侧是被索引的字段。 n是操作符类中操作符的策略号。通常，extractQuery需要参考n来决定query的数据类型以及抽取键值的方法。返回key的个数必须存放在*nkeys中。如果任何key都可能为NULL，还要分配包含*nkeys个布尔元素的数组，将地址存储到*nullFlags，并且根据需要设置NULL值。 如果所有key都是非NULL的，可以让*nullFlags保持为NULL（他的初始值）。如果query不包含任何key，返回值可以为NULL。
+
+  searchMode是一个输出参数，他允许extractQuery指定一些关于如何执行搜索的细节。如果设置*searchMode为GIN_SEARCH_MODE_DEFAULT（这也是调用函数前此参数的初始化值），只有那些至少返回一个key的item才能被考虑作为候选匹配项。如果设置*searchMode为GIN_SEARCH_MODE_INCLUDE_EMPTY，除了包含至少一个匹配key的item之外，根本不包含任何key的item也被考虑作为候选匹配项。（这个模式对于实现像“是否是子集”这样的操作是有用的）如果设置*searchMode为GIN_SEARCH_MODE_ALL，索引中所有非NULL的item都被考虑作为候选匹配项，不管他们是否匹配返回key中的任何一个。
+
+  pmatch是一个允许支持部分匹配的输出参数。如果使用此参数，extractQuery必须分配有*nkeys个布尔元素的数组，并把数组地址保存到*pmatch。如果需要部分匹配相应的key，则数组的每个元素应该设置为TRUE；如果不需要匹配，则设置为FALSE。如果设置*pmatch为NULL，则假设GIN不需要部分匹配。在函数调用前这个值被初始化为NULL，因此，对于不支持部分匹配的操作符类，可以忽略这个参数。
+
+  extra_data是一个允许extractQuery以consistent和comparePartial的方式传递额外数据的输出参数。如果使用他，extractQuery必须分配一个包含*nkeys个Pointer元素的数组，并把数组地址保存到*extra_data，然后把他想附加的东西存储到各个独立的指针中。在函数调用前这个值初始化为NULL，因此，对于不需要附加数据的操作符类，可以忽略这个参数。如果设置了*extra_data，那么以consistent方式传递整个数组，使用comparePartial方式传递适当的元素。
+
+- bool consistent(bool check[], StrategyNumber n, Datum query, int32 nkeys, Pointer extra_data[], bool *recheck, Datum queryKeys[], bool nullFlags[])
+
+  如果被索引项满足StrategyNumber为n的查询操作符则返回TRUE。这个函数并不直接访问被索引项的值，因为GIN并没有精确的把项目保存下来，但是需要知道从查询中提取的哪些键值出现在给定的被索引项中。 check数组的长度是nkeys，这个与query调用extractQuery函数返回的键值的数目相同。如果索引项包含了相应的查询键，check数组中对应的元素值就是TRUE。比如，如果(check[i] == TRUE)，那么意味着extractQuery的结果数组的第i个键出现在索引项中。考虑可能会用到consistent方式，原始的query也被作为参数传入进来。与此相同的还有extractQuery函数返回的queryKeys[]和nullFlags[]。 extra_data是extractQuery函数返回的额外数据数组，如果没有的话就是NULL。
+
+  当extractQuery在queryKeys[]中返回一个NULL的键值，如果被索引项包含NULL键值，相应的check[]中的元素是TRUE。也就是说，check[]的语义很像IS NOT DISTINCT FROM。如果需要知道是通常值匹配还是NULL匹配，consistent函数可以检查相应的nullFlags[]元素。
+
+  成功执行后，如果堆元组需要针对查询运算符进行重新检查，*recheck需要设置为TRUE，如果索引测试已经是精确的了，则设为FALSE。也就是说，FALSE的返回值确保堆元组不匹配这个查询；设置*recheck为FALSE的TRUE的返回值确保堆元组匹配这个查询；设置*recheck为TRUE的TRUE的返回值意味着堆元组可能匹配这个查询，因此需要通过直接对照原始索引项对查询运算符进行获取和重新检查。
+
+GIN操作符类可以可选地提供第五个函数。
+
+- int comparePartial(Datum partial_key, Datum key, StrategyNumber n, Pointer extra_data)
+
+  比较一个部分匹配查询键和一个索引键。返回一个整型值，它的符号代表了不同的含义：小于0意味着索引键不匹配查询，但是索引扫描应该继续； 0意味着索引键匹配查询；大于0指示应该终止索引扫描，因为不可能再有更多的匹配。在需要确定何时结束扫描的语义的情况下，这里提供了生成部分一致查询的操作符的策略号n。同样的，extra_data是extractQuery生成的额外数据数组中的相应元素，如果没有对应的元素，则为NULL。 NULL的键永远不会被传入这个函数。
+
+为了支持”部分匹配”查询，一个操作符类必须提供comparePartial方法，并且当遇到部分匹配查询时，他的extractQuery方法必须设置pmatch参数。详细信息请参考[部分匹配算法](3-implementation#部分匹配算法)。
+
+上面的各种Datum值的实际数据类型根据操作符类的不同而不同。传入到extractValue中的项目值总是操作符类的输入类型，所有的键值类型必须是这个类的STORAGE类型。传入到extractQuery和consistent的query参数的类型是由策略号识别的类成员操作符的右操作数的输入类型。他不需要和项目类型相同，只要可以从中抽取出正确类型的键值。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/1-gin-indexes/3-implementation.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/1-gin-indexes/3-implementation.md
new file mode 100644
index 0000000000000000000000000000000000000000..eec7150db1f39c9db72a7f3590c9363004aa3f2e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/1-gin-indexes/3-implementation.md
@@ -0,0 +1,24 @@
+---
+title: 实现
+summary: 实现
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# 实现
+
+在内部，GIN索引包含一个在键上构造的B-tree索引，每个键是一个或多个被索引项的一个元素（比如，一个数组的一个成员）。并且页面上每个元组包含了堆指针的B-tree的一个指针（一个posting tree），当列表小到足以和键值一起存储到一个索引元组中时，则是堆指针的一个简单列表（一个posting list）。
+
+多列GIN索引通过在组合值（列号，键值）上建立一个单个的B-tree实现。不同列的键值可以有不同的类型。
+
+## GIN快速更新技术
+
+由于倒排索引的本身特性影响，更新一个GIN索引可能会比较慢。插入或更新一个堆行可能导致许多往索引的插入。当对表执行VACUUM后，或者如果待处理实体的列表太大了（大于work_mem），这些实体被使用和初始索引创建时用到的相同的bulk插入方法，移动到主要的GIN数据结构。即使把额外的VACUUM开销算进去，这也大大提升了GIN索引更新的速度。而且，这种额外开销的工作可以通过后台进程而不是前端查询来处理。
+
+这种方法的主要缺点在于搜索时除了常规的索引还必须要扫描待处理实体的列表。因此，大的待处理实体的列表会显著的拖慢搜索。另一个缺点是，虽然大多数更新很快，但是一个导致待处理列表（pending list）变得“太大”的更新将引发一个立即清理，并因此比起其它更新会非常慢。恰当的使用autovacuum可以弱化这两个问题。
+
+如果一致的响应时间（清理实体速度和更新速度的响应时间）比更新速度更重要，可以通过把GIN索引的存储参数FASTUPDATE设置为off而不使用待处理实体。详细请参考[CREATE INDEX](50-CREATE-INDEX)。
+
+## 部分匹配算法
+
+GIN可以支持“部分匹配”查询。即：查询并不决定单个或多个键的一个精确的匹配，而是，可能的匹配落在一个合理的狭窄键值范围内（根据compare支持函数决定的键值排序顺序）。此时，extractQuery方法并不返回一个用于精确匹配的键值，取而代之的是，返回一个要被搜索的键值范围的下边界，并且设置pmatch为true。然后，使用comparePartial方式扫描这个键值范围。comparePartial必须为一个相匹配的索引键返回0，如果不匹配但依然在被搜索范围内时返回小于0的值，对超过可以匹配的范围的索引键则返回大于0的值。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/1-gin-indexes/4-gin-tips-and-tricks.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/1-gin-indexes/4-gin-tips-and-tricks.md
new file mode 100644
index 0000000000000000000000000000000000000000..428bd718946397ef9484a92e0b784ff489fc92a2
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/1-gin-indexes/4-gin-tips-and-tricks.md
@@ -0,0 +1,26 @@
+---
+title: GIN提示与技巧
+summary: GIN提示与技巧
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# GIN提示与技巧
+
+创建vs插入
+
+由于可能要为每个项目插入很多键，所以GIN索引的插入可能比较慢。对于向表中大量插入的操作，我们建议先删除GIN索引，在完成插入之后再重建索引。与GIN索引创建、查询性能相关的GUC参数如下：
+
+- maintenance_work_mem
+
+  GIN索引的构建时间对maintenance_work_mem的设置非常敏感。
+
+- work_mem
+
+  在向启用了FASTUPDATE的GIN索引执行插入操作的期间，只要待处理实体列表的大小超过了work_mem，系统就会清理这个列表。为了避免可观察到的响应时间的大起大落，让待处理实体列表在后台被清理是比较合适的（比如通过autovacuum）。前端清理操作可以通过增加work_mem或者执行autovacuum来避免。然而，扩大work_mem意味着如果发生了前端清理，那么他的执行时间将更长。
+
+- gin_fuzzy_search_limit
+
+  开发GIN索引的主要目的是为了让MogDB支持高度可伸缩的全文索引，并且常常会遇见全文索引返回海量结果的情形。而且，这经常发生在查询高频词的时候，因而这样的结果集没什么用处。因为从磁盘读取大量记录并对其进行排序会消耗大量资源，这在产品环境下是不能接受的。
+
+  为了控制这种情况，GIN索引有一个可配置的返回结果行数的软上限的配置参数gin_fuzzy_search_limit。缺省值0表示没有限制。如果设置了非零值，那么返回结果就是从完整结果集中随机选择的一部分。“软上限”的意思是返回结果的实际数量可能与指定的限制有偏差，这取决于查询和系统随机数生成器的质量。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/2-extended-functions.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/2-extended-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..15434795b41fe40f48d062480ce36aa2f6844f51
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/2-extended-functions.md
@@ -0,0 +1,36 @@
+---
+title: 扩展函数
+summary: 扩展函数
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# 扩展函数
+
+下表列举了MogDB中支持的扩展函数，不作为商用特性交付，仅供参考。
+
+<table>
+    <tr>
+        <th>分类</th>
+        <th>函数名称</th>
+        <th>描述</th>
+    </tr>
+    <tr>
+        <td rowspan=2>访问权限查询函数</td>
+        <td>has_sequence_privilege(user, sequence, privilege)</td>
+        <td>指定用户是否有访问序列的权限</td>
+    </tr>
+    <tr>
+        <td>has_sequence_privilege(sequence, privilege)</td>
+        <td>当前用户是否有访问序列的权限</td>
+    </tr>
+    <tr>
+        <td rowspan=2>触发器函数</td>
+        <td>pg_get_triggerdef(oid)</td>
+        <td>为触发器获取CREATE [ CONSTRAINT ] TRIGGER命令</td>
+    </tr>
+    <tr>
+        <td>pg_get_triggerdef(oid, boolean)</td>
+        <td>为触发器获取CREATE [ CONSTRAINT ] TRIGGER命令</td>
+    </tr>
+</table>
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/3-extended-syntax.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/3-extended-syntax.md
new file mode 100644
index 0000000000000000000000000000000000000000..7638c2934c4c8fc1aeb01914884e48d635ea5aef
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/13-appendix/3-extended-syntax.md
@@ -0,0 +1,52 @@
+---
+title: 扩展语法
+summary: 扩展语法
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# 扩展语法
+
+MogDB提供的扩展语法如下。
+
+**表 1** 扩展SQL语法
+
+<table>
+    <tr>
+        <th>分类</th>
+        <th>语法关键字</th>
+        <th>描述</th>
+    </tr>
+    <tr>
+        <td rowspan=2>创建表CREATE TABLE</td>
+        <td>INHERITS ( parent_table [, … ] )</td>
+        <td>支持继承表。</td>
+    </tr>
+    <tr>
+        <td>column_constraint：<br/>REFERENCES reftable<br/>[ ( refcolumn ) ] [ MATCH<br/>
+FULL | MATCH PARTIAL |<br/>MATCH SIMPLE ][ ON<br/>DELETE action ] [ ON<br/>UPDATE action ]</td>
+        <td>支持用REFERENCES reftable[ ( refcolumn ) ] [ MATCH FULL |MATCH PARTIAL | MATCH SIMPLE ] [ ON DELETE action ] [ ON UPDATE action ] 为表创建外键约束。</td>
+    </tr>
+    <tr>
+        <td rowspan=2>加载模块</td>
+        <td>CREATE EXTENSION</td>
+        <td>把一个新的模块（例如DBLINK）加载进当前数据库中。</td>
+    </tr>
+    <tr>
+        <td>DROP EXTENSION</td>
+        <td>删除已加载的模块。</td>
+    </tr>
+    <tr>
+        <td rowspan=3>聚集函数</td>
+        <td>CREATE AGGREGATE</td>
+        <td>定义一个新的聚集函数。</td>
+    </tr>
+    <tr>
+        <td>ALTER AGGREGATE</td>
+        <td>修改一个聚集函数的定义。</td>
+    </tr>
+    <tr>
+        <td>DROP AGGREGATE</td>
+        <td>删除一个现存的聚集函数。</td>
+    </tr>
+</table>
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/2-keywords.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/2-keywords.md
new file mode 100644
index 0000000000000000000000000000000000000000..31abca86b9a9ede0bd018fa3e3af9983194f528a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/2-keywords.md
@@ -0,0 +1,210 @@
+---
+title: 关键字
+summary: 关键字
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 关键字
+
+SQL里有保留字和非保留字之分。根据标准，保留字决不能用做其他标识符。非保留字只是在特定的环境里有特殊的含义，而在其他环境里是可以用做标识符的。
+
+标识符的命名需要遵守如下规范：
+
+- 标识符需要为字母、下划线、数字（0-9）或美元符号（$）。
+
+- 标识符必须以字母（a-z）或下划线（_）开头。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  >
+  > - 此命名规范为建议项，非强制项。
+  > - 特殊情况下可以使用双引号规避特殊字符报错。
+
+**表 1** SQL关键字
+
+| 关键字                     | MogDB          |
+| :------------------------- | :------------- |
+| ALL                        | reserved       |
+| ANALYSE                    | reserved       |
+| ANALYZE                    | reserved       |
+| AND                        | reserved       |
+| ANY                        | reserved       |
+| ARRAY                      | reserved       |
+| AS                         | reserved       |
+| ASC                        | reserved       |
+| ASYMMETRIC                 | reserved       |
+| AUTHID                     | reserved       |
+| AUTHORIZATION              | type-func-name |
+| BETWEEN                    | col-name       |
+| BIGINT                     | col-name       |
+| BINARY                     | type-func-name |
+| BINARY_DOUBLE              | col-name       |
+| BINARY_FLOAT               | col-name       |
+| BINARY_INTEGER             | col-name       |
+| BIT                        | col-name       |
+| BOOLEAN                    | col-name       |
+| BOTH                       | reserved       |
+| BUCKETCNT                  | col-name       |
+| BUCKETS                    | reserved       |
+| BYTEAWITHOUTORDER          | col-name       |
+| BYTEAWITHOUTORDERWITHEQUAL | col-name       |
+| CASE                       | reserved       |
+| CAST                       | reserved       |
+| CHAR                       | col-name       |
+| CHARACTER                  | col-name       |
+| CHECK                      | reserved       |
+| COALESCE                   | col-name       |
+| COLLATE                    | reserved       |
+| COLLATION                  | type-func-name |
+| COLUMN                     | reserved       |
+| COMPACT                    | type-func-name |
+| CONCURRENTLY               | type-func-name |
+| CONSTRAINT                 | reserved       |
+| CREATE                     | reserved       |
+| CROSS                      | type-func-name |
+| CSN                        | type-func-name |
+| CURRENT_CATALOG            | reserved       |
+| CURRENT_DATE               | reserved       |
+| CURRENT_ROLE               | reserved       |
+| CURRENT_SCHEMA             | type-func-name |
+| CURRENT_TIME               | reserved       |
+| CURRENT_TIMESTAMP          | reserved       |
+| CURRENT_USER               | reserved       |
+| DATE                       | col-name       |
+| DEC                        | col-name       |
+| DECIMAL                    | col-name       |
+| DECODE                     | col-name       |
+| DEFAULT                    | reserved       |
+| DEFERRABLE                 | reserved       |
+| DELTAMERGE                 | type-func-name |
+| DESC                       | reserved       |
+| DISTINCT                   | reserved       |
+| DO                         | reserved       |
+| ELSE                       | reserved       |
+| END                        | reserved       |
+| EXCEPT                     | reserved       |
+| EXCLUDED                   | reserved       |
+| EXISTS                     | col-name       |
+| EXTRACT                    | col-name       |
+| FALSE                      | reserved       |
+| FENCED                     | reserved       |
+| FETCH                      | reserved       |
+| FLOAT                      | col-name       |
+| FOR                        | reserved       |
+| FOREIGN                    | reserved       |
+| FREEZE                     | type-func-name |
+| FROM                       | reserved       |
+| FULL                       | type-func-name |
+| GRANT                      | reserved       |
+| GREATEST                   | col-name       |
+| GROUP                      | reserved       |
+| GROUPING                   | col-name       |
+| GROUPPARENT                | reserved       |
+| HAVING                     | reserved       |
+| HDFSDIRECTORY              | type-func-name |
+| ILIKE                      | type-func-name |
+| IN                         | reserved       |
+| INITIALLY                  | reserved       |
+| INNER                      | type-func-name |
+| INOUT                      | col-name       |
+| INT                        | col-name       |
+| INTEGER                    | col-name       |
+| INTERSECT                  | reserved       |
+| INTERVAL                   | col-name       |
+| INTO                       | reserved       |
+| IS                         | reserved       |
+| JOIN                       | type-func-name |
+| LEADING                    | reserved       |
+| LEAST                      | col-name       |
+| LEFT                       | type-func-name |
+| LESS                       | reserved       |
+| LIKE                       | type-func-name |
+| LIMIT                      | reserved       |
+| LOCALTIME                  | reserved       |
+| LOCALTIMESTAMP             | reserved       |
+| MAXVALUE                   | reserved       |
+| MINUS                      | reserved       |
+| MODIFY                     | reserved       |
+| NATIONAL                   | col-name       |
+| NATURAL                    | type-func-name |
+| NCHAR                      | col-name       |
+| NLSSORT                    | reserved       |
+| NONE                       | col-name       |
+| NOT                        | reserved       |
+| NOTNULL                    | type-func-name |
+| NULL                       | reserved       |
+| NULLIF                     | col-name       |
+| NUMBER                     | col-name       |
+| NUMERIC                    | col-name       |
+| NVARCHAR2                  | col-name       |
+| NVL                        | col-name       |
+| OFFSET                     | reserved       |
+| ON                         | reserved       |
+| ONLY                       | reserved       |
+| OR                         | reserved       |
+| ORDER                      | reserved       |
+| OUT                        | col-name       |
+| OUTER                      | type-func-name |
+| OVERLAPS                   | type-func-name |
+| OVERLAY                    | col-name       |
+| PERFORMANCE                | reserved       |
+| PLACING                    | reserved       |
+| POSITION                   | col-name       |
+| PRECISION                  | col-name       |
+| PRIMARY                    | reserved       |
+| PROCEDURE                  | reserved       |
+| REAL                       | col-name       |
+| RECYCLEBIN                 | type-func-name |
+| REFERENCES                 | reserved       |
+| REJECT                     | reserved       |
+| RETURNING                  | reserved       |
+| RIGHT                      | type-func-name |
+| ROW                        | col-name       |
+| ROWNUM                     | reserved       |
+| SELECT                     | reserved       |
+| SESSION_USER               | reserved       |
+| SETOF                      | col-name       |
+| SIMILAR                    | type-func-name |
+| SMALLDATETIME              | col-name       |
+| SMALLINT                   | col-name       |
+| SOME                       | reserved       |
+| SUBSTRING                  | col-name       |
+| SYMMETRIC                  | reserved       |
+| SYSDATE                    | reserved       |
+| SYSTIMESTAMP               | reserved       |
+| TABLE                      | reserved       |
+| TABLESAMPLE                | type-func-name |
+| THEN                       | reserved       |
+| TIME                       | col-name       |
+| TIMECAPSULE                | type-func-name |
+| TIMESTAMP                  | col-name       |
+| TIMESTAMPDIFF              | col-name       |
+| TINYINT                    | col-name       |
+| TO                         | reserved       |
+| TRAILING                   | reserved       |
+| TREAT                      | col-name       |
+| TRIM                       | col-name       |
+| TRUE                       | reserved       |
+| UNION                      | reserved       |
+| UNIQUE                     | reserved       |
+| USER                       | reserved       |
+| USING                      | reserved       |
+| VALUES                     | col-name       |
+| VARCHAR                    | col-name       |
+| VARCHAR2                   | col-name       |
+| VARIADIC                   | reserved       |
+| VERBOSE                    | type-func-name |
+| VERIFY                     | reserved       |
+| WHEN                       | reserved       |
+| WHERE                      | reserved       |
+| WINDOW                     | reserved       |
+| WITH                       | reserved       |
+| XMLATTRIBUTES              | col-name       |
+| XMLCONCAT                  | col-name       |
+| XMLELEMENT                 | col-name       |
+| XMLEXISTS                  | col-name       |
+| XMLFOREST                  | col-name       |
+| XMLPARSE                   | col-name       |
+| XMLPI                      | col-name       |
+| XMLROOT                    | col-name       |
+| XMLSERIALIZE               | col-name       |
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/3-constant-and-macro.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/3-constant-and-macro.md
new file mode 100644
index 0000000000000000000000000000000000000000..6afdb0e1ecb88d5baf3245b8ed7e30e77cbb0315
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/3-constant-and-macro.md
@@ -0,0 +1,24 @@
+---
+title: 常量与宏
+summary: 常量与宏
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 常量与宏
+
+MogDB支持的常量和宏请参见[表1](#constants)。
+
+**表 1** 常量和宏 <a id="constants"> </a>
+
+| 参数            | 描述                 | 示例              |
+| :------------------ | :-------------- | :----------------------------------------- |
+| CURRENT_CATALOG | 当前数据库                             | `mogdb=# SELECT CURRENT_CATALOG; current_database ------------------- postgres (1 row)` |
+| CURRENT_ROLE    | 当前用户                               | `mogdb=# SELECT CURRENT_ROLE; current_user ------------------- omm (1 row)` |
+| CURRENT_SCHEMA  | 当前数据库模式                         | `mogdb=# SELECT CURRENT_SCHEMA; current_schema ------------------- public (1 row)` |
+| CURRENT_USER    | 当前用户                               | `mogdb=# SELECT CURRENT_USER; current_user ------------------- omm (1 row)` |
+| LOCALTIMESTAMP  | 当前会话时间（无时区）                 | `mogdb=# SELECT LOCALTIMESTAMP;         timestamp ------------------- 2015-10-10 15:37:30.968538 (1 row)` |
+| NULL            | 空值                                   | -                                                            |
+| SESSION_USER    | 当前系统用户                           | `mogdb=# SELECT SESSION_USER; session_user ------------------- omm (1 row)` |
+| SYSDATE         | 当前系统日期                           | `mogdb=# SELECT SYSDATE; sysdate ------------------- 2015-10-10 15:48:53 (1 row)` |
+| USER            | 当前用户，此用户为CURRENT_USER的别名。 | `mogdb=# SELECT USER; current_user ------------------- omm (1 row)`      |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/4-expressions/1-simple-expressions.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/4-expressions/1-simple-expressions.md
new file mode 100644
index 0000000000000000000000000000000000000000..53fd89c48c055923eb37b5a4ad1d439322e9bda7
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/4-expressions/1-simple-expressions.md
@@ -0,0 +1,132 @@
+---
+title: 简单表达式
+summary: 简单表达式
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 简单表达式
+
+## 逻辑表达式
+
+逻辑表达式的操作符和运算规则，请参见[逻辑操作符](1-logical-operators)。
+
+## 比较表达式
+
+常用的比较操作符，请参见[操作符](2-operators)。
+
+除比较操作符外，还可以使用以下句式结构：
+
+- BETWEEN操作符
+
+  a BETWEEN x AND y 等效于a &gt;= x AND a &lt;= y
+
+  a NOT BETWEEN x AND y 等效于a &lt; x OR a &gt; y
+
+- 检查一个值是不是null，可使用：
+
+  expression IS NULL
+
+  expression IS NOT NULL
+
+  或者与之等价的句式结构，但不是标准的：
+
+  expression ISNULL
+
+  expression NOTNULL
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+  > 不要写expression=NULL或expression&lt;&gt;(!=)NULL，因为NULL代表一个未知的值，不能通过该表达式判断两个未知值是否相等。
+
+- is distinct from/is not distinct from
+  - is distinct from
+
+    A和B的数据类型、值不完全相同时为true。
+
+    A和B的数据类型、值完全相同时为false。
+
+    将空值视为相同。
+
+  - is not distinct from
+
+    A和B的数据类型、值不完全相同时为false。
+
+    A和B的数据类型、值完全相同时为true。
+
+    将空值视为相同。
+
+## 伪列
+
+**ROWNUM**
+
+ROWNUM是一个伪列，它返回一个数字，表示从查询中获取结果的行编号。第一行的ROWNUM为1，第二行的为2，依此类推。
+
+ROWNUM的返回类型为BIGINT。ROWNUM可以用于限制查询返回的总行数，例如下面语句限制查询从Students表中返回最多10条记录。
+
+```sql
+select * from Students where rownum <= 10;
+```
+
+## 示例
+
+```sql
+mogdb=# SELECT 2 BETWEEN 1 AND 3 AS RESULT;
+ result
+----------
+ t
+(1 row)
+
+mogdb=# SELECT 2 >= 1 AND 2 <= 3 AS RESULT;
+ result
+----------
+ t
+(1 row)
+
+mogdb=# SELECT 2 NOT BETWEEN 1 AND 3 AS RESULT;
+ result
+----------
+ f
+(1 row)
+
+mogdb=# SELECT 2 < 1 OR 2 > 3 AS RESULT;
+ result
+----------
+ f
+(1 row)
+
+mogdb=# SELECT 2+2 IS NULL AS RESULT;
+ result
+----------
+ f
+(1 row)
+
+mogdb=# SELECT 2+2 IS NOT NULL AS RESULT;
+ result
+----------
+ t
+(1 row)
+
+mogdb=# SELECT 2+2 ISNULL AS RESULT;
+ result
+----------
+ f
+(1 row)
+
+mogdb=# SELECT 2+2 NOTNULL AS RESULT;
+ result
+----------
+ t
+(1 row)
+
+mogdb=# SELECT 2+2 IS DISTINCT FROM NULL AS RESULT;
+ result
+----------
+ t
+(1 row)
+
+mogdb=# SELECT 2+2 IS NOT DISTINCT FROM NULL AS RESULT;
+ result
+----------
+ f
+(1 row)
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/4-expressions/2-condition-expressions.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/4-expressions/2-condition-expressions.md
new file mode 100644
index 0000000000000000000000000000000000000000..b3cb9264fb204ae6cda8c82bc943d2eebc4bb090
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/4-expressions/2-condition-expressions.md
@@ -0,0 +1,225 @@
+---
+title: 条件表达式
+summary: 条件表达式
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 条件表达式
+
+在执行SQL语句时，可通过条件表达式筛选出符合条件的数据。
+
+条件表达式主要有以下几种：
+
+- CASE
+
+  CASE表达式是条件表达式，类似于其他编程语言中的CASE语句。
+
+  CASE表达式的语法图请参考[图1](#condition)。
+
+  **图 1** case::= <a id="condition"> </a>
+
+  ![case](https://cdn-mogdb.enmotech.com/docs-media/mogdb/reference-guide/condition-expressions-1.png)
+
+  CASE子句可以用于合法的表达式中。condition是一个返回BOOLEAN数据类型的表达式：
+
+  - 如果结果为真，CASE表达式的结果就是符合该条件所对应的result。
+  - 如果结果为假，则以相同方式处理随后的WHEN或ELSE子句。
+  - 如果各WHEN condition都不为真，表达式的结果就是在ELSE子句执行的result。如果省略了ELSE子句且没有匹配的条件，结果为NULL。
+
+  示例：
+
+  ```sql
+  mogdb=# CREATE TABLE tpcds.case_when_t1(CW_COL1 INT);
+
+  mogdb=# INSERT INTO tpcds.case_when_t1 VALUES (1), (2), (3);
+
+  mogdb=# SELECT * FROM tpcds.case_when_t1;
+  cw_col1
+  -------
+   1
+   2
+   3
+  (3 rows)
+
+  mogdb=# SELECT CW_COL1, CASE WHEN CW_COL1=1 THEN 'one' WHEN CW_COL1=2 THEN 'two' ELSE 'other' END FROM tpcds.case_when_t1 ORDER BY 1;
+   cw_col1 | case
+  ---------+-------
+         1 | one
+         2 | two
+         3 | other
+  (3 rows)
+
+  mogdb=# DROP TABLE tpcds.case_when_t1;
+  ```
+
+- DECODE
+
+  DECODE的语法图请参见[图2](#decode)。
+
+  **图 2** decode::= <a id="decode"> </a>
+
+  ![decode](https://cdn-mogdb.enmotech.com/docs-media/mogdb/reference-guide/condition-expressions-2.png)
+
+  将表达式base_expr与后面的每个compare(n) 进行比较，如果匹配返回相应的value(n)。如果没有发生匹配，则返回default。
+
+  示例请参见**条件表达式函数**。
+
+  ```sql
+  mogdb=# SELECT DECODE('A','A',1,'B',2,0);
+   case
+  ------
+      1
+  (1 row)
+  ```
+
+- COALESCE
+
+  COALESCE的语法图请参见[图3](#coalesce)。
+
+  **图 3** coalesce::= <a id="coalesce"> </a>
+
+  ![coalesce](https://cdn-mogdb.enmotech.com/docs-media/mogdb/reference-guide/condition-expressions-3.png)
+
+  COALESCE返回它的第一个非NULL的参数值。如果参数都为NULL，则返回NULL。它常用于在显示数据时用缺省值替换NULL。和CASE表达式一样，COALESCE只计算用来判断结果的参数，即在第一个非空参数右边的参数不会被计算。
+
+  示例
+
+  ```sql
+  mogdb=# CREATE TABLE tpcds.c_tabl(description varchar(10), short_description varchar(10), last_value varchar(10))
+  ;
+
+  mogdb=# INSERT INTO tpcds.c_tabl VALUES('abc', 'efg', '123');
+  mogdb=# INSERT INTO tpcds.c_tabl VALUES(NULL, 'efg', '123');
+
+  mogdb=# INSERT INTO tpcds.c_tabl VALUES(NULL, NULL, '123');
+
+  mogdb=# SELECT description, short_description, last_value, COALESCE(description, short_description, last_value) FROM tpcds.c_tabl ORDER BY 1, 2, 3, 4;
+   description | short_description | last_value | coalesce
+  -------------+-------------------+------------+----------
+   abc         | efg               | 123        | abc
+               | efg               | 123        | efg
+               |                   | 123        | 123
+  (3 rows)
+
+  mogdb=# DROP TABLE tpcds.c_tabl;
+  ```
+
+  如果description不为NULL，则返回description的值，否则计算下一个参数short_description；如果short_description不为NULL，则返回short_description的值，否则计算下一个参数last_value；如果last_value不为NULL，则返回last_value的值，否则返回（none）。
+
+  ```sql
+  mogdb=# SELECT COALESCE(NULL,'Hello World');
+     coalesce
+  ---------------
+   Hello World
+  (1 row)
+  ```
+
+- NULLIF
+
+  NULLIF的语法图请参见[图4](#nullif)。
+
+  **图 4** nullif::= <a id="nullif"> </a>
+
+  ![nullif](https://cdn-mogdb.enmotech.com/docs-media/mogdb/reference-guide/condition-expressions-4.png)
+
+  只有当value1和value2相等时，NULLIF才返回NULL。否则它返回value1。
+
+  示例
+
+  ```sql
+  mogdb=# CREATE TABLE tpcds.null_if_t1 (
+      NI_VALUE1 VARCHAR(10),
+      NI_VALUE2 VARCHAR(10)
+  );
+
+  mogdb=# INSERT INTO tpcds.null_if_t1 VALUES('abc', 'abc');
+  mogdb=# INSERT INTO tpcds.null_if_t1 VALUES('abc', 'efg');
+
+  mogdb=# SELECT NI_VALUE1, NI_VALUE2, NULLIF(NI_VALUE1, NI_VALUE2) FROM tpcds.null_if_t1 ORDER BY 1, 2, 3;
+
+   ni_value1 | ni_value2 | nullif
+  -----------+-----------+--------
+   abc       | abc       |
+   abc       | efg       | abc
+  (2 rows)
+  mogdb=# DROP TABLE tpcds.null_if_t1;
+  ```
+
+  如果value1等于value2则返回NULL，否则返回value1。
+
+  ```sql
+  mogdb=# SELECT NULLIF('Hello','Hello World');
+   nullif
+  --------
+   Hello
+  (1 row)
+  ```
+
+- GREATEST（最大值），LEAST（最小值）
+
+  GREATEST的语法图请参见[图5](#greatest)。
+
+  **图 5** greatest::= <a id="greatest"> </a>
+
+  ![greatest](https://cdn-mogdb.enmotech.com/docs-media/mogdb/reference-guide/condition-expressions-5.png)
+
+  从一个任意数字表达式的列表里选取最大的数值。
+
+  ```sql
+  mogdb=# SELECT greatest(9000,155555,2.01);
+   greatest
+  ----------
+     155555
+  (1 row)
+  ```
+
+  LEAST的语法图请参见[图6](#least)。
+
+  **图 6** least::= <a id="least"> </a>
+  ![least](https://cdn-mogdb.enmotech.com/docs-media/mogdb/reference-guide/condition-expressions-6.png)
+
+  从一个任意数字表达式的列表里选取最小的数值。
+
+  以上的数字表达式必须都可以转换成一个普通的数据类型，该数据类型将是结果类型。
+
+  列表中的NULL值将被忽略。只有所有表达式的结果都是NULL的时候，结果才是NULL。
+
+  ```sql
+  mogdb=# SELECT least(9000,2);
+   least
+  -------
+       2
+  (1 row)
+  ```
+
+  示例请参见**条件表达式函数**。
+
+- NVL
+
+  NVL的语法图请参见[图7](#nvl)。
+
+  **图 7** nvl::= <a id="nvl"> </a>
+
+  ![nvl](https://cdn-mogdb.enmotech.com/docs-media/mogdb/reference-guide/condition-expressions-7.png)
+
+  如果value1为NULL则返回value2，如果value1非NULL，则返回value1。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT nvl(null,1);
+  nvl
+  -----
+   1
+  (1 row)
+
+  ```
+
+  ```sql
+  mogdb=# SELECT nvl ('Hello World' ,1);
+        nvl
+  ---------------
+   Hello World
+  (1 row)
+  ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/4-expressions/3-subquery-expressions.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/4-expressions/3-subquery-expressions.md
new file mode 100644
index 0000000000000000000000000000000000000000..9696d1de10f5a3620e026ca0d5e8eb8ff6d12cad
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/4-expressions/3-subquery-expressions.md
@@ -0,0 +1,144 @@
+---
+title: 子查询表达式
+summary: 子查询表达式
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 子查询表达式
+
+子查询表达式主要有以下几种：
+
+- EXISTS/NOT EXISTS
+
+  EXISTS/NOT EXISTS的语法图请参见[图1](#existsnot)。
+
+  **图 1** EXISTS/NOT EXISTS::= <a id="existsnot"> </a>
+
+  ![EXISTS-NOT-EXISTS](https://cdn-mogdb.enmotech.com/docs-media/mogdb/reference-guide/subquery-expressions-1.png)
+
+  EXISTS的参数是一个任意的SELECT语句，或者说子查询。系统对子查询进行运算以判断它是否返回行。如果它至少返回一行，则EXISTS结果就为”真”；如果子查询没有返回任何行， EXISTS的结果是”假”。
+
+  这个子查询通常只是运行到能判断它是否可以生成至少一行为止，而不是等到全部结束。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT sr_reason_sk,sr_customer_sk FROM tpcds.store_returns WHERE EXISTS (SELECT d_dom FROM tpcds.date_dim WHERE d_dom = store_returns.sr_reason_sk and sr_customer_sk <10);
+  sr_reason_sk | sr_customer_sk
+  --------------+----------------
+             13 |              2
+             22 |              5
+             17 |              7
+             25 |              7
+              3 |              7
+             31 |              5
+              7 |              7
+             14 |              6
+             20 |              4
+              5 |              6
+             10 |              3
+              1 |              5
+             15 |              2
+              4 |              1
+             26 |              3
+  (15 rows)
+  ```
+
+- IN/NOT IN
+
+  IN/NOT IN的语法请参见[图2](#innotin)。
+
+  **图 2** IN/NOT IN::= <a id="innotin"> </a>
+
+  ![IN-NOT-IN](https://cdn-mogdb.enmotech.com/docs-media/mogdb/reference-guide/subquery-expressions-2.png)
+
+  右边是一个圆括弧括起来的子查询，它必须只返回一个字段。左边表达式对子查询结果的每一行进行一次计算和比较。如果找到任何相等的子查询行，则IN结果为”真”。如果没有找到任何相等行，则结果为”假”（包括子查询没有返回任何行的情况）。
+
+  表达式或子查询行里的NULL遵照SQL处理布尔值和NULL组合时的规则。如果两个行对应的字段都相等且非空，则这两行相等；如果任意对应字段不等且非空，则这两行不等；否则结果是未知（NULL）。如果每一行的结果都是不等或NULL ，并且至少有一个NULL ，则IN的结果是NULL 。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT sr_reason_sk,sr_customer_sk  FROM tpcds.store_returns WHERE sr_customer_sk IN (SELECT d_dom FROM tpcds.date_dim WHERE d_dom < 10);
+  sr_reason_sk | sr_customer_sk
+  --------------+----------------
+             10 |              3
+             26 |              3
+             22 |              5
+             31 |              5
+              1 |              5
+             32 |              5
+             32 |              5
+              4 |              1
+             15 |              2
+             13 |              2
+             33 |              4
+             20 |              4
+             33 |              8
+              5 |              6
+             14 |              6
+             17 |              7
+              3 |              7
+             25 |              7
+              7 |              7
+  (19 rows)
+  ```
+
+- ANY/SOME
+
+  ANY/SOME的语法图请参见[图3](#anysome)。
+
+  **图 3** any/some::= <a id="anysome"> </a>
+
+  ![any-some](https://cdn-mogdb.enmotech.com/docs-media/mogdb/reference-guide/subquery-expressions-3.png)
+
+  右边是一个圆括弧括起来的子查询，它必须只返回一个字段。左边表达式使用operator对子查询结果的每一行进行一次计算和比较，其结果必须是布尔值。如果至少获得一个真值，则ANY结果为“真”。如果全部获得假值，则结果是“假”（包括子查询没有返回任何行的情况）。SOME是ANY的同义词。IN与ANY可以等效替换 。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT sr_reason_sk,sr_customer_sk  FROM tpcds.store_returns WHERE sr_customer_sk < ANY (SELECT d_dom FROM tpcds.date_dim WHERE d_dom < 10);
+  sr_reason_sk | sr_customer_sk
+  --------------+----------------
+             26 |              3
+             17 |              7
+             32 |              5
+             32 |              5
+             13 |              2
+             31 |              5
+             25 |              7
+              5 |              6
+              7 |              7
+             10 |              3
+              1 |              5
+             14 |              6
+              4 |              1
+              3 |              7
+             22 |              5
+             33 |              4
+             20 |              4
+             33 |              8
+             15 |              2
+  (19 rows)
+  ```
+
+- ALL
+
+  ALL的语法请参见[图4](#all)。
+
+  **图 4** all::= <a id="all"> </a>
+
+  ![all](https://cdn-mogdb.enmotech.com/docs-media/mogdb/reference-guide/subquery-expressions-4.png)
+
+  右边是一个圆括弧括起来的子查询，它必须只返回一个字段。左边表达式使用operator对子查询结果的每一行进行一次计算和比较，其结果必须是布尔值。如果全部获得真值，ALL结果为”真”（包括子查询没有返回任何行的情况）。如果至少获得一个假值，则结果是”假”。
+
+  示例：
+
+  ```sql
+  mogdb=# SELECT sr_reason_sk,sr_customer_sk  FROM tpcds.store_returns WHERE sr_customer_sk < all(SELECT d_dom FROM tpcds.date_dim WHERE d_dom < 10);
+   sr_reason_sk | sr_customer_sk
+  --------------+----------------
+  (0 rows)
+
+  ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/4-expressions/4-array-expressions.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/4-expressions/4-array-expressions.md
new file mode 100644
index 0000000000000000000000000000000000000000..a08bf6f0979518d1b39ac9917201913b0bf70a50
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/4-expressions/4-array-expressions.md
@@ -0,0 +1,93 @@
+---
+title: 数组表达式
+summary: 数组表达式
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 数组表达式
+
+## IN
+
+expression **IN** (value [, …])
+
+右侧括号中的是一个表达式列表。左侧表达式的结果与表达式列表的内容进行比较。如果列表中的内容符合左侧表达式的结果，则IN的结果为true。如果没有相符的结果，则IN的结果为false。
+
+示例如下：
+
+```sql
+mogdb=# SELECT 8000+500 IN (10000, 9000) AS RESULT;
+  result
+----------
+ f
+(1 row)
+```
+
+如果表达式结果为null，或者表达式列表不符合表达式的条件且右侧表达式列表返回结果至少一处为空，则IN的返回结果为null，而不是false。这样的处理方式和SQL返回空值的布尔组合规则是一致的。
+
+## NOT IN
+
+expression **NOT IN** (value [, …])
+
+右侧括号中的是一个表达式列表。左侧表达式的结果与表达式列表的内容进行比较。如果在列表中的内容没有符合左侧表达式结果的内容，则NOT IN的结果为true。如果有符合的内容，则NOT IN的结果为false。
+
+示例如下：
+
+```sql
+mogdb=# SELECT 8000+500 NOT IN (10000, 9000) AS RESULT;
+  result
+----------
+ t
+(1 row)
+```
+
+如果查询语句返回结果为空，或者表达式列表不符合表达式的条件且右侧表达式列表返回结果至少一处为空，则NOT IN的返回结果为null，而不是false。这样的处理方式和SQL返回空值的布尔组合规则是一致的。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 在所有情况下X NOT IN Y等价于NOT(X IN Y)。
+
+## ANY/SOME (array)
+
+expression operator **ANY** (array expression)_
+
+expression operator **SOME** (array expression)_
+
+```sql
+mogdb=# SELECT 8000+500 < SOME (array[10000,9000]) AS RESULT;
+  result
+----------
+ t
+(1 row)
+mogdb=# SELECT 8000+500 < ANY (array[10000,9000]) AS RESULT;
+  result
+----------
+ t
+(1 row)
+```
+
+右侧括号中的是一个数组表达式，它必须产生一个数组值。左侧表达式的结果使用操作符对数组表达式的每一行结果都进行计算和比较，比较结果必须是布尔值。
+
+- 如果对比结果至少获取一个真值，则ANY的结果为true。
+- 如果对比结果没有真值，则ANY的结果为false。
+- 如果结果没有真值，并且数组表达式生成至少一个值为null，则ANY的值为NULL，而不是false。这样的处理方式和SQL返回空值的布尔组合规则是一致的。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** SOME是ANY的同义词。
+
+## ALL (array)
+
+expression operator **ALL** (array expression)
+
+右侧括号中的是一个数组表达式，它必须产生一个数组值。左侧表达式的结果使用操作符对数组表达式的每一行结果都进行计算和比较，比较结果必须是布尔值。
+
+- 如果所有的比较结果都为真值（包括数组不含任何元素的情况），则ALL的结果为true。
+
+- 如果存在一个或多个比较结果为假值，则ALL的结果为false。
+
+- 如果数组表达式产生一个NULL数组，则ALL的结果为NULL。如果左边表达式的值为NULL ，则ALL的结果通常也为NULL(某些不严格的比较操作符可能得到不同的结果)。另外，如果右边的数组表达式中包含null元素并且比较结果没有假值，则ALL的结果将是NULL(某些不严格的比较操作符可能得到不同的结果)， 而不是真。这样的处理方式和SQL返回空值的布尔组合规则是一致的。
+
+  ```sql
+  mogdb=# SELECT 8000+500 < ALL (array[10000,9000]) AS RESULT;
+  result
+  ----------
+  t
+  (1 row)
+  ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/4-expressions/5-row-expressions.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/4-expressions/5-row-expressions.md
new file mode 100644
index 0000000000000000000000000000000000000000..0d322821ed9995bc9f7954089f459db0508875de
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/4-expressions/5-row-expressions.md
@@ -0,0 +1,28 @@
+---
+title: 行表达式
+summary: 行表达式
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 行表达式
+
+语法：
+
+*row_constructor operator row_constructor*
+
+两边都是一个行构造器，两行值必须具有相同数目的字段，每一行都进行比较，行比较允许使用=，&lt;&gt;，&lt;，&lt;=，&gt;=等操作符，或其中一个相似的语义符。
+
+=&lt;&gt;和别的操作符使用略有不同。如果两行值的所有字段都是非空并且相等，则认为两行是相等的；如果两行值的任意字段为非空并且不相等，则认为两行是不相等的；否则比较结果是未知的（null）。
+
+对于&lt;，&lt;=，&gt;，&gt; =的情况下，行中元素从左到右依次比较，直到遇到一对不相等的元素或者一对为空的元素。如果这对元素中存在至少一个null值，则比较结果是未知的（null），否则这对元素的比较结果为最终的结果。
+
+示例：
+
+```sql
+mogdb=# SELECT ROW(1,2,NULL) < ROW(1,3,0) AS RESULT;
+  result
+----------
+ t
+(1 row)
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/5-type-conversion/1-type-conversion-overview.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/5-type-conversion/1-type-conversion-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..b1edf1db8adec314d4764543c9bbccb1986a660a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/5-type-conversion/1-type-conversion-overview.md
@@ -0,0 +1,52 @@
+---
+title: 概述
+summary: 概述
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 概述
+
+## 背景信息
+
+在SQL语言中，每个数据都与一个决定其行为和用法的数据类型相关。MogDB提供一个可扩展的数据类型系统，该系统比其它SQL实现更具通用性和灵活性。因而，MogDB中大多数类型转换是由通用规则来管理的，这种做法允许使用混合类型的表达式。
+
+MogDB扫描/分析器只将词法元素分解成五个基本种类：整数、浮点数、字符串、标识符和关键字。大多数非数字类型首先表现为字符串。SQL语言的定义允许将常量字符串声明为具体的类型。例，下面查询：
+
+```sql
+mogdb=# SELECT text 'Origin' AS "label", point '(0,0)' AS "value";
+ label  | value
+--------+-------
+ Origin | (0,0)
+(1 row)
+```
+
+示例中有两个文本常量，类型分别为text和point。如果没有为字符串文本声明类型，则该文本首先被定义成一个unknown类型。
+
+在MogDB分析器里，有四种基本的SQL结构需要独立的类型转换规则：
+
+- 函数调用
+
+  多数SQL类型系统是建筑在一套丰富的函数上的。函数调用可以有一个或多个参数。因为SQL允许函数重载，所以不能通过函数名直接找到要调用的函数，分析器必须根据函数提供的参数类型选择正确的函数。
+
+- 操作符
+
+  SQL允许在表达式上使用前缀或后缀（单目）操作符，也允许表达式内部使用双目操作符（两个参数）。像函数一样，操作符也可以被重载，因此操作符的选择也和函数一样取决于参数类型。
+
+- 值存储
+
+  INSERT和UPDATE语句将表达式结果存入表中。语句中的表达式类型必须和目标字段的类型一致或者可以转换为一致。
+
+- UNION，CASE和相关构造
+
+  因为联合SELECT语句中的所有查询结果必须在一列里显示出来，所以每个SELECT子句中的元素类型必须相互匹配并转换成一个统一类型。类似地，一个CASE构造的结果表达式必须转换成统一的类型，这样整个case表达式会有一个统一的输出类型。同样的要求也存在于ARRAY构造以及GREATEST和LEAST函数中。
+
+系统表pg_cast存储了有关数据类型之间的转换关系以及如何执行这些转换的信息。
+
+语义分析阶段会决定表达式的返回值类型并选择适当的转换行为。数据类型的基本类型分类，包括：Boolean，numeric，string，bitstring，datetime，timespan，geometric和network。每种类型都有一种或多种首选类型用于解决类型选择的问题。根据首选类型和可用的隐含转换，就可能保证有歧义的表达式（那些有多个候选解析方案的）得到有效的方式解决。
+
+所有类型转换规则都是建立在下面几个基本原则上的：
+
+- 隐含转换决不能有奇怪的或不可预见的输出。
+- 如果一个查询不需要隐含的类型转换，分析器和执行器不应该进行更多的额外操作。这就是说，任何一个类型匹配、格式清晰的查询不应该在分析器里耗费更多的时间，也不应该向查询中引入任何不必要的隐含类型转换调用。
+- 另外，如果一个查询在调用某个函数时需要进行隐式转换，当用户定义了一个有正确参数的函数后，解释器应该选择使用新函数。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/5-type-conversion/2-operators.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/5-type-conversion/2-operators.md
new file mode 100644
index 0000000000000000000000000000000000000000..5812536cbb585e34a9b33b1a2a8f2b4b64c7617f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/5-type-conversion/2-operators.md
@@ -0,0 +1,92 @@
+---
+title: 操作符
+summary: 操作符
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 操作符
+
+## 操作符类型解析
+
+1. 从系统表pg_operator中选出要考虑的操作符。如果可以找到一个参数类型以及参数个数都一致的操作符，那么这个操作符就是最终使用的操作符。如果找到了多个备选的操作符，我们将从中选择一个最合适的。
+2. 寻找最优匹配。
+
+   a. 抛弃那些输入类型不匹配并且也不能隐式转换成匹配的候选操作符。unknown文本在这种情况下可以转换成任何东西。如果只剩下一个候选项，则用之，否则继续下一步。
+
+   b. 遍历所有候选操作符，保留那些输入类型匹配最准确的。此时，域被看作和他们的基本类型相同。如果没有一个操作符能被保留，则保留所有候选。如果只剩下一个候选项，则用之，否则继续下一步。
+
+   c. 遍历所有候选操作符，保留那些需要类型转换时接受(属于输入数据类型的类型范畴的)首选类型位置最多的操作符。如果没有接受首选类型的操作符，则保留所有候选。如果只剩下一个候选项，则用之，否则继续下一步。
+
+   d. 如果有任何输入参数是unknown类型，检查剩余的候选操作符对应参数位置的类型范畴。在每一个能够接受字符串类型范畴的位置使用string类型（这种对字符串的偏爱是合适的，因为unknown文本确实像字符串）。另外，如果所有剩下的候选操作符都接受相同的类型范畴，则选择该类型范畴，否则抛出一个错误（因为在没有更多线索的条件下无法作出正确的选择）。现在抛弃不接受选定的类型范畴的候选操作符，然后，如果任意候选操作符在某个给定的参数位置接受一个首选类型，则抛弃那些在该参数位置接受非首选类型的候选操作符。如果没有一个操作符能被保留，则保留所有候选。如果只剩下一个候选项，则用之，否则继续下一步。
+
+   e. 如果同时有unknown和已知类型的参数，并且所有已知类型的参数都是相同的类型，那么假设unknown参数也是那种类型，并检查哪个候选操作符在unknown参数位置接受那个类型。如果只有一个操作符符合，那么使用它。否则，产生一个错误。
+
+## 示例
+
+示例1：阶乘操作符类型解析。在系统表中里只有一个阶乘操作符（后缀!），它以bigint作为参数。扫描器给下面查询表达式的参数赋予bigint的初始类型：
+
+```sql
+mogdb=# SELECT 40 ! AS "40 factorial";
+
+                   40 factorial
+--------------------------------------------------
+ 815915283247897734345611269596115894272000000000
+(1 row)
+```
+
+分析器对参数做类型转换，查询等效于：
+
+```sql
+mogdb=# SELECT CAST(40 AS bigint) ! AS "40 factorial";
+```
+
+示例2：字符串连接操作符类型分析。一种字符串风格的语法既可以用于字符串也可以用于复杂的扩展类型。未声明类型的字符串将被所有可能的候选操作符匹配。有一个未声明的参数的例子：
+
+```sql
+mogdb=# SELECT text 'abc' || 'def' AS "text and unknown";
+ text and unknown
+------------------
+ abcdef
+(1 row)
+```
+
+本例中分析器寻找两个参数都是text的操作符。确实有这样的操作符，两个参数都是text类型。
+
+下面是连接两个未声明类型的值：
+
+```sql
+mogdb=# SELECT 'abc' || 'def' AS "unspecified";
+ unspecified
+-------------
+ abcdef
+(1 row)
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+> 因为查询中没有声明任何类型，所以本例中对类型没有任何初始提示。因此，分析器查找所有候选操作符，发现既存在接受字符串类型范畴的操作符也存在接受位串类型范畴的操作符。因为字符串类型范畴是首选，所以选择字符串类型范畴的首选类型text作为解析未知类型文本的声明类型。
+
+示例3：绝对值和取反操作符类型分析。MogDB操作符表里面有几条记录对应于前缀操作符@，它们都用于为各种数值类型实现绝对值操作。其中之一用于float8类型，它是数值类型范畴中的首选类型。因此，在面对unknown输入的时候， MogDB会使用该类型：
+
+```sql
+mogdb=# SELECT @ '-4.5' AS "abs";
+ abs
+-----
+ 4.5
+(1 row)
+```
+
+此处，系统在应用选定的操作符之前隐式的转换unknown类型的文字为float8类型。
+
+示例4：数组包含操作符类型分析。这里是解决一个操作符带有一个已知和一个未知类型输入的例子：
+
+```sql
+mogdb=# SELECT array[1,2] <@ '{1,2,3}' as "is subset";
+ is subset
+-----------
+ t
+(1 row)
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+> MogDB操作符表有几条记录对应于中缀操作符&lt;@，但是只有两个可以在左侧接受一个整数数组的操作符是数组包含（anyarray &lt;@ anyarray）和范围包含（anyelement &lt;@ anyrange）的。因为没有多态的伪类型（参阅[伪类型](15-pseudo-types)）是首选的，所以解析器不能解决这个基础上的歧义。然而，最后一个解析规则告诉用户，假设未知类型的文字是和另外一个输入相同的类型，也就是，整数数组。现在只有两个操作符中的一个可以匹配，所以选择数组包含。（如果用户选择了范围包含，用户将得到一个错误，因为字符串没有正确的格式成为范围的文字。)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/5-type-conversion/3-functions.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/5-type-conversion/3-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..d94e7cd06b7eadbadd2a6b18f6db2084c3094638
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/5-type-conversion/3-functions.md
@@ -0,0 +1,103 @@
+---
+title: 函数
+summary: 函数
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 函数
+
+## 函数类型解析
+
+1. 从系统表pg_proc中选择所有可能被选到的函数。如果使用了一个不带模式修饰的函数名称，那么认为该函数是那些在当前搜索路径中的函数。如果给出一个带修饰的函数名，那么只考虑指定模式中的函数。
+
+   如果搜索路径中找到了多个不同参数类型的函数。将从中选择一个合适的函数。
+
+2. 查找和输入参数类型完全匹配的函数。如果找到一个，则用之。如果输入的实参类型都是unknown类型，则不会找到匹配的函数。
+
+3. 如果未找到完全匹配，请查看该函数是否为一个特殊的类型转换函数。
+
+4. 寻找最优匹配。
+
+   a. 抛弃那些输入类型不匹配并且也不能隐式转换成匹配的候选函数。unknown文本在这种情况下可以转换成任何东西。如果只剩下一个候选项，则用之，否则继续下一步。
+
+   b. 遍历所有候选函数，保留那些输入类型匹配最准确的。此时，域被看作和它们的基本类型相同。如果没有一个函数能准确匹配，则保留所有候选。如果只剩下一个候选项，则用之，否则继续下一步。
+
+   c. 遍历所有候选函数，保留那些需要类型转换时接受首选类型位置最多的函数。如果没有接受首选类型的函数，则保留所有候选。如果只剩下一个候选项，则用之，否则继续下一步。
+
+   d. 如果有任何输入参数是unknown类型，检查剩余的候选函数对应参数位置的类型范畴。在每一个能够接受字符串类型范畴的位置使用string类型（这种对字符串的偏爱是合适的，因为unknown文本确实像字符串）。另外，如果所有剩下的候选函数都接受相同的类型范畴，则选择该类型范畴，否则抛出一个错误（因为在没有更多线索的条件下无法作出正确的选择）。现在抛弃不接受选定的类型范畴的候选函数，然后，如果任意候选函数在那个范畴接受一个首选类型，则抛弃那些在该参数位置接受非首选类型的候选函数。如果没有一个候选符合这些测试则保留所有候选。如果只有一个候选函数符合，则使用它；否则，继续下一步。
+
+   e. 如果同时有unknown和已知类型的参数，并且所有已知类型的参数有相同的类型，假设unknown参数也是这种类型，检查哪个候选函数可以在unknown参数位置接受这种类型。如果正好一个候选符合，那么使用它。否则，产生一个错误。
+
+## 示例
+
+示例1：圆整函数参数类型解析。只有一个round函数有两个参数（第一个是numeric，第二个是integer）。所以下面的查询自动把第一个类型为integer的参数转换成numeric类型。
+
+```sql
+mogdb=# SELECT round(4, 4);
+ round
+--------
+ 4.0000
+(1 row)
+```
+
+实际上它被分析器转换成：
+
+```sql
+mogdb=# SELECT round(CAST (4 AS numeric), 4);
+```
+
+因为带小数点的数值常量初始时被赋予numeric类型，因此下面的查询将不需要类型转换，并且可能会略微高效一些：
+
+```sql
+mogdb=# SELECT round(4.0, 4);
+```
+
+示例2：子字符串函数类型解析。有好几个substr函数，其中一个接受text和integer类型。如果用一个未声明类型的字符串常量调用它，系统将选择接受string类型范畴的首选类型（也就是text类型）的候选函数。
+
+```sql
+mogdb=# SELECT substr('1234', 3);
+ substr
+--------
+     34
+(1 row)
+```
+
+如果该字符串声明为varchar类型，就像从表中取出来的数据一样，分析器将试着将其转换成text类型：
+
+```sql
+mogdb=# SELECT substr(varchar '1234', 3);
+ substr
+--------
+     34
+(1 row)
+```
+
+被分析器转换后实际上变成：
+
+```sql
+mogdb=# SELECT substr(CAST (varchar '1234' AS text), 3);
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+> 分析器从pg_cast表中了解到text和varchar是二进制兼容的，意思是说一个可以传递给接受另一个的函数而不需要做任何物理转换。因此，在这种情况下，实际上没有做任何类型转换。
+
+而且，如果以integer为参数调用函数，分析器将试图将其转换成text类型：
+
+```sql
+mogdb=# SELECT substr(1234, 3);
+substr
+--------
+ 34
+(1 row)
+```
+
+被分析器转换后实际上变成：
+
+```sql
+mogdb=# SELECT substr(CAST (1234 AS text), 3);
+ substr
+--------
+     34
+(1 row)
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/5-type-conversion/4-value-storage.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/5-type-conversion/4-value-storage.md
new file mode 100644
index 0000000000000000000000000000000000000000..da6d1dd40dbc04ac6299415d20cfc32c8fcbd8f5
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/5-type-conversion/4-value-storage.md
@@ -0,0 +1,36 @@
+---
+title: 值存储
+summary: 值存储
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 值存储
+
+## 值存储数据类型解析
+
+1. 查找与目标字段准确的匹配。
+2. 试着将表达式直接转换成目标类型。如果已知这两种类型之间存在一个已注册的转换函数，那么直接调用该转换函数即可。如果表达式是一个未知类型文本，该文本字符串的内容将交给目标类型的输入转换过程。
+3. 检查一下看目标类型是否有长度转换。长度转换是一个从某类型到自身的转换。如果在pg_cast表里面找到一个，那么在存储到目标字段之前先在表达式上应用。这样的转换函数总是接受一个额外的类型为integer的参数，它接收目标字段的atttypmod值（实际上是其声明长度，atttypmod的解释随不同的数据类型而不同），并且它可能接受一个Boolean类型的第三个参数，表示转换是显式的还是隐式的。转换函数负责施加那些长度相关的语义，比如长度检查或者截断。
+
+## 示例
+
+character存储类型转换。对一个目标列定义为character(20)的语句，下面的语句显示存储值的长度正确：
+
+```sql
+mogdb=# CREATE TABLE tpcds.value_storage_t1 (
+    VS_COL1 CHARACTER(20)
+);
+mogdb=# INSERT INTO tpcds.value_storage_t1 VALUES('abcdef');
+mogdb=# SELECT VS_COL1, octet_length(VS_COL1) FROM tpcds.value_storage_t1;
+       vs_col1        | octet_length
+----------------------+--------------
+ abcdef               |           20
+(1 row)
+)
+
+mogdb=# DROP TABLE tpcds.value_storage_t1;
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+> 这里真正发生的事情是两个unknown文本缺省解析成text，这样就允许||操作符解析成text连接。然后操作符的text结果转换成bpchar(“空白填充的字符型”， character类型内部名称)以匹配目标字段类型。不过，从text到bpchar的转换是二进制兼容的，这样的转换是隐含的并且实际上不做任何函数调用。最后，在系统表里找到长度转换函数bpchar(bpchar, integer, Boolean) 并且应用于该操作符的结果和存储的字段长。这个类型相关的函数执行所需的长度检查和额外的空白填充。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/5-type-conversion/5-union-case-and-related-constructs.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/5-type-conversion/5-union-case-and-related-constructs.md
new file mode 100644
index 0000000000000000000000000000000000000000..4ea7771e97922e451f9b869d17a1c1105efb38c5
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/5-type-conversion/5-union-case-and-related-constructs.md
@@ -0,0 +1,125 @@
+---
+title: UNION，CASE和相关构造
+summary: UNION，CASE和相关构造
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# UNION，CASE和相关构造
+
+SQL UNION构造必须把那些可能不太相似的类型匹配起来成为一个结果集。解析算法分别应用于联合查询的每个输出字段。INTERSECT和EXCEPT构造对不相同的类型使用和UNION相同的算法进行解析。CASE、ARRAY、VALUES、GREATEST和LEAST构造也使用同样的算法匹配它的部件表达式并且选择一个结果数据类型。
+
+## UNION，CASE和相关构造解析
+
+- 如果所有输入都是相同的类型，并且不是unknown类型，那么解析成这种类型。
+
+- 如果所有输入都是unknown类型则解析成text类型（字符串类型范畴的首选类型）。否则，忽略unknown输入。
+
+- 如果输入不属于同一个类型范畴，失败。（unknown类型除外）
+
+- 如果输入类型是同一个类型范畴，则选择该类型范畴的首选类型。（例外：union操作会选择第一个分支的类型作为所选类型。）
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  > 系统表pg_type中typcategory表示数据类型范畴， typispreferred表示是否是typcategory分类中的首选类型。
+
+- 把所有输入转换为所选的类型（对于字符串保持原有长度）。如果从给定的输入到所选的类型没有隐式转换则失败。
+
+- 若输入中含json、txid_snapshot、sys_refcursor或几何类型，则不能进行union。
+
+## 对于case和coalesce，在TD兼容模式下的处理
+
+- 如果所有输入都是相同的类型，并且不是unknown类型，那么解析成这种类型。
+- 如果所有输入都是unknown类型则解析成text类型。
+- 如果输入字符串（包括unknown，unknown当text来处理）和数字类型，那么解析成字符串类型，如果是其他不同的类型范畴，则报错。
+- 如果输入类型是同一个类型范畴，则选择该类型的优先级较高的类型。
+- 把所有输入转换为所选的类型。如果从给定的输入到所选的类型没有隐式转换则失败。
+
+## 示例
+
+示例1：Union中的待定类型解析。这里，unknown类型文本'b'将被解析成text类型。
+
+```sql
+mogdb=# SELECT text 'a' AS "text" UNION SELECT 'b';
+ text
+------
+ a
+ b
+(2 rows)
+```
+
+示例2：简单Union中的类型解析。文本1.2的类型为numeric，而且integer类型的1可以隐含地转换为numeric，因此使用这个类型。
+
+```sql
+mogdb=# SELECT 1.2 AS "numeric" UNION SELECT 1;
+ numeric
+---------
+       1
+     1.2
+(2 rows)
+```
+
+示例3：转置Union中的类型解析。这里，因为类型real不能被隐含转换成integer，但是integer可以隐含转换成real，那么联合的结果类型将是real。
+
+```sql
+mogdb=# SELECT 1 AS "real" UNION SELECT CAST('2.2' AS REAL);
+ real
+------
+    1
+  2.2
+(2 rows)
+```
+
+示例4：TD模式下，coalesce参数输入int和varchar类型，那么解析成varchar类型。A模式下会报错。
+
+```sql
+--在A模式下，创建A兼容模式的数据库a_1。
+mogdb=# CREATE DATABASE a_1 dbcompatibility = 'A';
+
+--切换数据库为a_1。
+mogdb=# \c a_1
+
+--创建表t1。
+a_1=# CREATE TABLE t1(a int, b varchar(10));
+
+--查看coalesce参数输入int和varchar类型的查询语句的执行计划。
+a_1=# EXPLAIN SELECT coalesce(a, b) FROM t1;
+ERROR:  COALESCE types integer and character varying cannot be matched
+LINE 1: EXPLAIN SELECT coalesce(a, b) FROM t1;
+                                   ^
+CONTEXT:  referenced column: coalesce
+
+--删除表。
+a_1=# DROP TABLE t1;
+
+--切换数据库为mogdb。
+a_1=# \c mogdb
+
+--在TD模式下，创建TD兼容模式的数据库td_1。
+mogdb=# CREATE DATABASE td_1 dbcompatibility = 'C';
+
+--切换数据库为td_1。
+mogdb=# \c td_1
+
+--创建表t2。
+td_1=# CREATE TABLE t2(a int, b varchar(10));
+
+--查看coalesce参数输入int和varchar类型的查询语句的执行计划。
+td_1=# EXPLAIN VERBOSE select coalesce(a, b) from t2;
+                                      QUERY PLAN
+---------------------------------------------------------------------------------------
+ Data Node Scan  (cost=0.00..0.00 rows=0 width=0)
+   Output: (COALESCE((t2.a)::character varying, t2.b))
+   Node/s: All dbnodes
+   Remote query: SELECT COALESCE(a::character varying, b) AS "coalesce" FROM public.t2
+(4 rows)
+
+--删除表。
+td_1=# DROP TABLE t2;
+
+--切换数据库为mogdb。
+td_1=# \c mogdb
+
+--删除A和TD模式的数据库。
+mogdb=# DROP DATABASE a_1;
+mogdb=# DROP DATABASE td_1;
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/1-introduction/1-full-text-retrieval.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/1-introduction/1-full-text-retrieval.md
new file mode 100644
index 0000000000000000000000000000000000000000..3852b3b2d62d5ab3bf80a07a15f1b1617703e03b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/1-introduction/1-full-text-retrieval.md
@@ -0,0 +1,38 @@
+---
+title: 全文检索概述
+summary: 全文检索概述
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 全文检索概述
+
+文本搜索操作符在数据库中已存在多年。MogDB为文本数据类型提供~、~*、LIKE和ILIKE操作符；但它们缺乏现代信息系统所要求的许多必要属性。这些缺憾可以通过使用索引及词典进行解决。
+
+文本检索缺乏信息系统所要求的必要属性：
+
+- 没有语义支持，即使是英语。
+
+  由于要识别派生词并不是那么容易，因此正则表达式也不能满足要求。如，satisfies和satisfy，当使用正则表达式寻找satisfy时，并不会查询到包含satisfies的文档。用户可以使用OR搜索多种派生形式，但过程非常繁琐。并且有些词会有上千的派生词，因此容易出错。
+
+- 没有对搜索结果的分类（排序）。当搜索出成千的文档时，查找效率很低。
+
+- 由于没有索引的支持，每一次的搜索需要遍历所有的文档，整体搜索比较缓慢。
+
+使用全文索引可以对文档进行预处理，并且可以使后续的搜索更快速。预处理过程包括：
+
+- 将文档解析成token。
+
+  为每个文档标记不同类别的token是非常有必要的，例如：数字、文字、复合词、电子邮件地址，这样就可以做不同的处理。原则上token的类别依赖于具体的应用，但对于大多数的应用来说，可以使用一组预定义的token类。
+
+- 将token转换为词素。
+
+  词素像token一样是一个字符串，但它已经标准化处理，这样同一个词的不同形式是一样的。例如，标准化通常包括：将大写字母折成小写字母、删除后缀（如英语中的s或者es）。这将允许通过搜索找到同一个词的不同形式，不需要繁琐地输入所有可能的变形样式。同时，这一步通常会删除停用词。这些停用词通常因为太常见而对搜索无用。（总之，token是文档文本的原片段，而词素被认为是有用的索引和搜索词。）MogDB使用词典执行这一步，且提供了各种标准的词典。
+
+- 保存搜索优化后的预处理文档。
+
+  比如，每个文档可以呈现为标准化词素的有序组合。伴随词素，通常还需要存储词素位置信息以用于邻近排序。因此文档包含的查询词越密集其排序越高。
+
+词典能够对token如何标准化做到细粒度控制。使用合适的词典，可以定义不被索引的停用词。
+
+数据类型tsvector用于存储预处理文档，tsquery用于存储查询条件，详细请参见[文本搜索类型](10-text-search-types)。为这些数据类型提供的函数和操作符请参见[文本检索函数和操作符](12-text-search-functions-and-operators)。其中最重要的是匹配运算符@@，将在[基本文本匹配](3-basic-text-matching)中介绍。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/1-introduction/2-what-is-a-document.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/1-introduction/2-what-is-a-document.md
new file mode 100644
index 0000000000000000000000000000000000000000..0f1388ecb4b5cfd3c31104faa91bf55561777f93
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/1-introduction/2-what-is-a-document.md
@@ -0,0 +1,33 @@
+---
+title: 文档概念
+summary: 文档概念
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 文档概念
+
+文档是全文搜索系统的搜索单元，例如：杂志上的一篇文章或电子邮件消息。文本搜索引擎必须能够解析文档，而且可以存储父文档的关联词素（关键词）。后续，这些关联词素用来搜索包含查询词的文档。
+
+在MogDB中，文档通常是一个数据库表中一行的文本字段，或者这些字段的可能组合（级联）。文档可能存储在多个表中或者需动态获取。换句话说，一个文档由被索引化的不同部分构成，因此无法存储为一个整体。比如：
+
+```sql
+mogdb=# SELECT d_dow || '-' || d_dom || '-' || d_fy_week_seq  AS identify_serials FROM tpcds.date_dim WHERE d_fy_week_seq = 1;
+identify_serials
+------------------
+ 5-6-1
+ 0-8-1
+ 2-3-1
+ 3-4-1
+ 4-5-1
+ 1-2-1
+ 6-7-1
+(7 rows)
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+> 实际上，在这些示例查询中，应该使用coalesce防止一个独立的NULL属性导致整个文档的NULL结果。
+
+另外一种可能是：文档在文件系统中作为简单的文本文件存储。在这种情况下，数据库可以用于存储全文索引并且执行搜索，同时可以使用一些唯一标识从文件系统中检索文档。然而，从数据库外部检索文件需要拥有系统管理员权限或者特殊函数支持。因此，还是将所有数据保存在数据库中比较方便。同时，将所有数据保存在数据库中可以方便地访问文档元数据以便于索引和显示。
+
+为了实现文本搜索目的，必须将每个文档减少至预处理后的tsvector格式。搜索和相关性排序都是在tsvector形式的文档上执行的。原始文档只有在被选中要呈现给用户时才会被检索。因此，我们常将tsvector说成文档，但是很显然其实它只是完整文档的一种紧凑表示。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/1-introduction/3-basic-text-matching.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/1-introduction/3-basic-text-matching.md
new file mode 100644
index 0000000000000000000000000000000000000000..a6f6ad3fcdb3a9c6b17f119a3a5dcee614dd0c46
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/1-introduction/3-basic-text-matching.md
@@ -0,0 +1,56 @@
+---
+title: 基本文本匹配
+summary: 基本文本匹配
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 基本文本匹配
+
+MogDB的全文检索基于匹配算子@@，当一个tsvector(document)匹配到一个tsquery(query)时，则返回true。其中，tsvector(document)和tsquery(query)两种数据类型可以任意排序。
+
+```sql
+mogdb=# SELECT 'a fat cat sat on a mat and ate a fat rat'::tsvector @@ 'cat & rat'::tsquery AS RESULT;
+ result
+----------
+ t
+(1 row)
+mogdb=# SELECT 'fat & cow'::tsquery @@ 'a fat cat sat on a mat and ate a fat rat'::tsvector AS RESULT;
+ result
+----------
+ f
+(1 row)
+```
+
+正如上面例子表明，tsquery不仅是文本，且比tsvector包含的要多。tsquery包含已经标注化为词条的搜索词，同时可能是使用AND、OR、或NOT操作符连接的多个术语。函数to_tsquery和plainto_tsquery对于将用户书写文本转换成适合的tsquery是非常有用的，比如将文本中的词标准化。类似地，to_tsvector用于解析和标准化文档字符串。因此，实际中文本搜索匹配看起来更像这样：
+
+```sql
+mogdb=# SELECT to_tsvector('fat cats ate fat rats') @@ to_tsquery('fat & rat') AS RESULT;
+result
+----------
+ t
+(1 row)
+```
+
+需要注意的是，下面这种方式是不可行的：
+
+```sql
+mogdb=# SELECT 'fat cats ate fat rats'::tsvector @@ to_tsquery('fat & rat')AS RESULT;
+result
+----------
+ f
+(1 row)
+```
+
+由于tsvector没有对rats进行标准化，所以rats不匹配rat。
+
+@@操作符也支持text输入，允许一个文本字符串的显示转换为tsvector或者在简单情况下忽略tsquery。可用形式是：
+
+```sql
+tsvector @@ tsquery
+tsquery  @@ tsvector
+text @@ tsquery
+text @@ text
+```
+
+我们已经看到了前面两种，形式text @@ tsquery等价于to_tsvector(text) @@ tsquery，而text @@ text等价于to_tsvector(text) @@ plainto_tsquery(text)。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/1-introduction/4-configurations.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/1-introduction/4-configurations.md
new file mode 100644
index 0000000000000000000000000000000000000000..ca4827c0e38df14935b08ff42bce4c87d97ca9f8
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/1-introduction/4-configurations.md
@@ -0,0 +1,21 @@
+---
+title: 分词器
+summary: 分词器
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 分词器
+
+全文检索功能还可以做更多事情：忽略索引某个词（停用词），处理同义词和使用复杂解析，例如：不仅基于空格的解析。这些功能通过文本搜索分词器控制。MogDB支持多语言的预定义的分词器，并且可以创建分词器（gsql的\\dF命令显示了所有可用分词器）。
+
+在安装期间选择一个合适的分词器，并且在postgresql.conf中相应的设置default_text_search_config。如果为了MogDB使用同一个文本搜索分词器可以使用postgresql.conf中的值。如果需要在MogDB中使用不同分词器，可以使用ALTER DATABASE … SET在任一数据库进行配置。用户也可以在每个会话中设置default_text_search_config。
+
+每个依赖于分词器的文本搜索函数有一个可选的配置参数，用以明确声明所使用的分词器。仅当忽略这个参数的时候，才使用default_text_search_config。
+
+为了更方便的建立自定义文本搜索分词器，可以通过简单的数据库对象建立分词器。 MogDB文本搜索功能提供了四种类型与分词器相关的数据库对象：
+
+- 文本搜索解析器将文档分解为token，并且分类每个token（例如：词和数字）。
+- 文本搜索词典将token转换成规范格式并且丢弃停用词。
+- 文本搜索模板提供潜在的词典功能：一个词典指定一个模板，并且为模板设置参数。
+- 文本搜索分词器选择一个解析器，并且使用一系列词典规范化语法分析器产生的token。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/2-tables-and-indexes/1-searching-a-table.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/2-tables-and-indexes/1-searching-a-table.md
new file mode 100644
index 0000000000000000000000000000000000000000..465de5d264970bd790aad678ac93bf8b85fd49df
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/2-tables-and-indexes/1-searching-a-table.md
@@ -0,0 +1,91 @@
+---
+title: 搜索表
+summary: 搜索表
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 搜索表
+
+在不使用索引的情况下也可以进行全文检索。
+
+- 一个简单查询：将body字段中包含america的每一行打印出来。
+
+  ```sql
+  mogdb=# DROP SCHEMA IF EXISTS tsearch CASCADE;
+
+  mogdb=# CREATE SCHEMA tsearch;
+
+  mogdb=# CREATE TABLE tsearch.pgweb(id int, body text, title text, last_mod_date date);
+
+  mogdb=# INSERT INTO tsearch.pgweb VALUES(1, 'China, officially the People''s Republic of China (PRC), located in Asia, is the world''s most populous state.', 'China', '2010-1-1');
+
+  mogdb=# INSERT INTO tsearch.pgweb VALUES(2, 'America is a rock band, formed in England in 1970 by multi-instrumentalists Dewey Bunnell, Dan Peek, and Gerry Beckley.', 'America', '2010-1-1');
+
+  mogdb=# INSERT INTO tsearch.pgweb VALUES(3, 'England is a country that is part of the United Kingdom. It shares land borders with Scotland to the north and Wales to the west.', 'England', '2010-1-1');
+
+  mogdb=# INSERT INTO tsearch.pgweb VALUES(4, 'Australia, officially the Commonwealth of Australia, is a country comprising the mainland of the Australian continent, the island of Tasmania, and numerous smaller islands.', 'Australia', '2010-1-1');
+
+  mogdb=# INSERT INTO tsearch.pgweb VALUES(5, 'Russia, also officially known as the Russian Federation, is a sovereign state in northern Eurasia.', 'Russia', '2010-1-1');
+
+  mogdb=# INSERT INTO tsearch.pgweb VALUES(6, 'Japan is an island country in East Asia.', 'Japan', '2010-1-1');
+
+  mogdb=# INSERT INTO tsearch.pgweb VALUES(7, 'Germany, officially the Federal Republic of Germany, is a sovereign state and federal parliamentary republic in central-western Europe.', 'Germany', '2010-1-1');
+
+  mogdb=# INSERT INTO tsearch.pgweb VALUES(8, 'France, is a sovereign state comprising territory in western Europe and several overseas regions and territories.', 'France', '2010-1-1');
+
+  mogdb=# INSERT INTO tsearch.pgweb VALUES(9, 'Italy officially the Italian Republic, is a unitary parliamentary republic in Europe.', 'Italy', '2010-1-1');
+
+  mogdb=# INSERT INTO tsearch.pgweb VALUES(10, 'India, officially the Republic of India, is a country in South Asia.', 'India', '2010-1-1');
+
+  mogdb=# INSERT INTO tsearch.pgweb VALUES(11, 'Brazil, officially the Federative Republic of Brazil, is the largest country in both South America and Latin America.', 'Brazil', '2010-1-1');
+
+  mogdb=# INSERT INTO tsearch.pgweb VALUES(12, 'Canada is a country in the northern half of North America.', 'Canada', '2010-1-1');
+
+  mogdb=# INSERT INTO tsearch.pgweb VALUES(13, 'Mexico, officially the United Mexican States, is a federal republic in the southern part of North America.', 'Mexico', '2010-1-1');
+
+  mogdb=# SELECT id, body, title FROM tsearch.pgweb WHERE to_tsvector('english', body) @@ to_tsquery('english', 'america');
+   id |                                                          body                                                           |  title
+  ----+-------------------------------------------------------------------------------------------------------------------------+---------
+    2 | America is a rock band, formed in England in 1970 by multi-instrumentalists Dewey Bunnell, Dan Peek, and Gerry Beckley. | America
+   12 | Canada is a country in the northern half of North America.                                                              | Canada
+   13 | Mexico, officially the United Mexican States, is a federal republic in the southern part of North America.              | Mexico
+   11 | Brazil, officially the Federative Republic of Brazil, is the largest country in both South America and Latin America.   | Brazil
+  (4 rows)
+  ```
+
+  像America这样的相关词也会被找到，因为这些词都被处理成了相同标准的词条。
+
+  上面的查询指定english配置来解析和规范化字符串。当然也可以省略此配置，通过default_text_search_config进行配置设置：
+
+  ```sql
+  mogdb=# SHOW default_text_search_config;
+   default_text_search_config
+  ----------------------------
+   pg_catalog.english
+  (1 row)
+
+  mogdb=# SELECT id, body, title FROM tsearch.pgweb WHERE to_tsvector(body) @@ to_tsquery('america');
+   id |                                                          body                                                           |  title
+  ----+-------------------------------------------------------------------------------------------------------------------------+---------
+   11 | Brazil, officially the Federative Republic of Brazil, is the largest country in both South America and Latin America.   | Brazil
+    2 | America is a rock band, formed in England in 1970 by multi-instrumentalists Dewey Bunnell, Dan Peek, and Gerry Beckley. | America
+   12 | Canada is a country in the northern half of North America.                                                              | Canada
+   13 | Mexico, officially the United Mexican States, is a federal republic in the southern part of North America.              | Mexico
+  (4 rows)
+  ```
+
+- 一个复杂查询：检索出在title或者body字段中包含north和america的最近10篇文档：
+
+  ```sql
+  mogdb=# SELECT title FROM tsearch.pgweb WHERE to_tsvector(title || ' ' || body) @@ to_tsquery('north & america') ORDER BY last_mod_date DESC LIMIT 10;
+   title
+  --------
+   Mexico
+   Canada
+  (2 rows)
+  ```
+
+  为了清晰，举例中没有调用coalesce函数在两个字段中查找包含NULL的行。
+
+  以上例子均在没有索引的情况下进行查询。对于大多数应用程序来说，这个方法很慢。因此除了偶尔的特定搜索，文本搜索在实际使用中通常需要创建索引。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/2-tables-and-indexes/2-creating-an-index.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/2-tables-and-indexes/2-creating-an-index.md
new file mode 100644
index 0000000000000000000000000000000000000000..1873b3d8f15b4274e0b79d2215a93a72f70fd14c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/2-tables-and-indexes/2-creating-an-index.md
@@ -0,0 +1,65 @@
+---
+title: 创建索引
+summary: 创建索引
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 创建索引
+
+为了加速文本搜索，可以创建GIN索引。
+
+```sql
+mogdb=# CREATE INDEX pgweb_idx_1 ON tsearch.pgweb USING gin(to_tsvector('english', body));
+```
+
+to_tsvector()函数有两个版本。只输一个参数的版本和输两个参数的版本。只输一个参数时，系统默认采用default_text_search_config所指定的分词器。
+
+请注意：创建索引时必须使用to_tsvector的两参数版本。只有指定了分词器名称的全文检索函数才可以在索引表达式中使用。这是因为索引的内容必须不受default_text_search_config的影响，否则索引内容可能不一致。由于default_text_search_config的值可以随时调整，从而导致不同条目生成的tsvector采用了不同的分词器，并且没有办法区分究竟使用了哪个分词器。正确地转储和恢复这样的索引也是不可能的。
+
+因为在上述创建索引中to_tsvector使用了两个参数，只有当查询时也使用了两个参数，且参数值与索引中相同时，才会使用该索引。也就是说，WHERE to_tsvector('english', body) @@ 'a & b' 可以使用索引，但WHERE to_tsvector(body) @@ 'a & b'不能使用索引。这确保只使用这样的索引,索引各条目是使用相同的分词器创建的。
+
+索引中的分词器名称由另一列指定时可以建立更复杂的表达式索引。例如：
+
+```sql
+mogdb=# CREATE INDEX pgweb_idx_2 ON tsearch.pgweb USING gin(to_tsvector('ngram', body));
+```
+
+其中body是pgweb表中的一列。当对索引的各条目使用了哪个分词器进行记录时，允许在同一索引中存在混合分词器。在某些场景下这将是有用的。例如，文档集合中包含不同语言的文档时。再次强调，打算使用索引的查询必须措辞匹配，例如，WHERE to_tsvector(config_name, body) @@ 'a & b'与索引中的to_tsvector措辞匹配。
+
+索引甚至可以连接列：
+
+```sql
+mogdb=# CREATE INDEX pgweb_idx_3 ON tsearch.pgweb USING gin(to_tsvector('english', title || ' ' || body));
+```
+
+另一个方法是创建一个单独的tsvector列控制to_tsvector的输出。下面的例子是title和body的连接， 当其它是NULL的时候，使用coalesce确保一个字段仍然会被索引：
+
+```sql
+mogdb=# ALTER TABLE tsearch.pgweb ADD COLUMN textsearchable_index_col tsvector;
+mogdb=# UPDATE tsearch.pgweb SET textsearchable_index_col = to_tsvector('english', coalesce(title,'') || ' ' || coalesce(body,''));
+```
+
+然后为加速搜索创建一个GIN索引：
+
+```sql
+mogdb=# CREATE INDEX textsearch_idx_4 ON tsearch.pgweb USING gin(textsearchable_index_col);
+```
+
+现在，就可以执行一个快速全文搜索了：
+
+```sql
+mogdb=# SELECT title
+FROM tsearch.pgweb
+WHERE textsearchable_index_col @@ to_tsquery('north & america')
+ORDER BY last_mod_date DESC
+LIMIT 10;
+
+ title
+--------
+ Canada
+ Mexico
+(2 rows)
+```
+
+相比于一个表达式索引，单独列方法的一个优势是：它没有必要在查询时明确指定分词器以便能使用索引。正如上面例子所示，查询可以依赖于default_text_search_config。另一个优势是搜索比较快速，因为它没有必要重新利用to_tsvector调用来验证索引匹配。表达式索引方法更容易建立，且它需要较少的磁盘空间，因为tsvector形式没有明确存储。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/2-tables-and-indexes/3-constraints-on-index-use.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/2-tables-and-indexes/3-constraints-on-index-use.md
new file mode 100644
index 0000000000000000000000000000000000000000..561569ba3febe95cfdaf6c8c5efe9ab3313be954
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/2-tables-and-indexes/3-constraints-on-index-use.md
@@ -0,0 +1,44 @@
+---
+title: 索引使用约束
+summary: 索引使用约束
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 索引使用约束
+
+下面是一个使用索引的例子：
+
+```sql
+mogdb=# create table table1 (c_int int,c_bigint bigint,c_varchar varchar,c_text text) with(orientation=row);
+
+mogdb=# create text search configuration ts_conf_1(parser=POUND);
+mogdb=# create text search configuration ts_conf_2(parser=POUND) with(split_flag='%');
+
+mogdb=# set default_text_search_config='ts_conf_1';
+mogdb=# create index idx1 on table1 using gin(to_tsvector(c_text));
+
+mogdb=# set default_text_search_config='ts_conf_2';
+mogdb=# create index idx2 on table1 using gin(to_tsvector(c_text));
+
+mogdb=# select c_varchar,to_tsvector(c_varchar) from table1 where to_tsvector(c_text) @@ plainto_tsquery('￥#@……&**')   and to_tsvector(c_text) @@ plainto_tsquery('某公司 ')   and c_varchar is not null order by 1 desc limit 3;
+```
+
+该例子的关键点是表table1的同一个列c_text上建立了两个gin索引：idx1和idx2，但这两个索引是在不同default_text_search_config的设置下建立的。该例子和同一张表的同一个列上建立普通索引的不同之处在于：
+
+- gin索引使用了不同的parser（即分隔符不同），那么idx1和idx2的索引数据是不同的；
+- 在同一张表的同一个列上建立的多个普通索引的索引数据是相同的。
+
+因此当执行同一个查询时，使用idx1和idx2查询出的结果是不同的。
+
+## 使用约束
+
+通过上面的例子，索引使用满足如下条件时：
+
+- 在同一个表的同一个列上建立了多个gin索引；
+
+- 这些gin索引使用了不同的parser（即分隔符不同）；
+
+- 在查询中使用了该列，且执行计划中使用索引进行扫描；
+
+  为了避免使用不同gin索引导致查询结果不同的问题，需要保证在物理表的一列上只有一个gin索引可用。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/1-parsing-documents.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/1-parsing-documents.md
new file mode 100644
index 0000000000000000000000000000000000000000..c7381d0da6f9d2b190ec6b9bc78b61242ad6a40b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/1-parsing-documents.md
@@ -0,0 +1,52 @@
+---
+title: 解析文档
+summary: 解析文档
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 解析文档
+
+MogDB中提供了to_tsvector函数把文档处理成tsvector数据类型。
+
+```sql
+to_tsvector([ config regconfig, ] document text) returns tsvector
+```
+
+to_tsvector将文本文档解析为token，再将token简化到词素，并返回一个tsvector。其中tsvector中列出了词素及它们在文档中的位置。文档是根据指定的或默认的文本搜索分词器进行处理的。这里有一个简单的例子：
+
+```sql
+mogdb=# SELECT to_tsvector('english', 'a fat  cat sat on a mat - it ate a fat rats');
+                  to_tsvector
+-----------------------------------------------------
+ 'ate':9 'cat':3 'fat':2,11 'mat':7 'rat':12 'sat':4
+```
+
+通过以上例子可发现结果tsvector不包含词a、on或者it，rats变成rat，并且忽略标点符号-。
+
+to_tsvector函数内部调用一个解析器，将文档的文本分解成token并给每个token指定一个类型。对于每个token，有一系列词典可供查询。词典系列因token类型的不同而不同。识别token的第一本词典将发出一个或多个标准词素来表示token。例如：
+
+- rats变成rat因为词典认为词rats是rat的复数形式。
+- 有些词被作为停用词（请参考[停用词](2-stop-words)），这样它们就会被忽略，因为它们出现得太过频繁以致于搜索中没有用处。比如例子中的a、on和it。
+- 如果没有词典识别token，那么它也被忽略。在这个例子中，符号“-”被忽略，因为词典没有给它分配token类型（空间符号），即空间记号永远不会被索引。
+
+语法解析器、词典和要索引的token类型由选定的文本搜索分词器决定。可以在同一个数据库中有多种不同的分词器，以及提供各种语言的预定义分词器。在以上例子中，使用缺省分词器english。
+
+函数setweight可以给tsvector的记录加权重，权重是字母A、B、C、D之一。这通常用于标记来自文档不同部分的记录，比如标题、正文。之后，这些信息可以用于排序搜索结果。
+
+因为to_tsvector(NULL)会返回空，当字段可能是空的时候，建议使用coalesce。以下是推荐的为结构化文档创建tsvector的方法：
+
+```sql
+mogdb=# CREATE TABLE tsearch.tt (id int, title text, keyword text, abstract text, body text, ti tsvector);
+
+mogdb=# INSERT INTO tsearch.tt(id, title, keyword, abstract, body) VALUES (1, 'China', 'Beijing', 'China','China, officially the People''s Republic of China (PRC), located in Asia, is the world''s most populous state.');
+
+mogdb=# UPDATE tsearch.tt SET ti =
+    setweight(to_tsvector(coalesce(title,'')), 'A')    ||
+    setweight(to_tsvector(coalesce(keyword,'')), 'B')  ||
+    setweight(to_tsvector(coalesce(abstract,'')), 'C') ||
+    setweight(to_tsvector(coalesce(body,'')), 'D');
+mogdb=# DROP TABLE tsearch.tt;
+```
+
+上例使用setweight标记已完成的tsvector中的每个词的来源，并且使用tsvector连接操作符||合并标记过的tsvector值，[处理tsvector](1-manipulating-tsvector)一节详细介绍了这些操作。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/2-parsing-queries.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/2-parsing-queries.md
new file mode 100644
index 0000000000000000000000000000000000000000..f7a4e804cb45c26617916df0d87387cf096ec1f8
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/2-parsing-queries.md
@@ -0,0 +1,74 @@
+---
+title: 解析查询
+summary: 解析查询
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 解析查询
+
+MogDB提供了函数to_tsquery和plainto_tsquery将查询转换为tsquery数据类型，to_tsquery提供比plainto_tsquery更多的功能，但对其输入要求更严格。
+
+```sql
+to_tsquery([ config regconfig, ] querytext text) returns tsquery
+```
+
+to_tsquery从querytext中创建一个tsquery，querytext必须由布尔运算符&（AND），|（OR）和!（NOT）分割的单个token组成。这些运算符可以用圆括弧分组。换句话说，to_tsquery输入必须遵循tsquery输入的通用规则，具体请参见[文本搜索类型](10-text-search-types)。不同的是基本tsquery以token表面值作为输入，而to_tsquery使用指定或默认分词器将每个token标准化成词素，并依据分词器丢弃属于停用词的token。例如：
+
+```sql
+mogdb=# SELECT to_tsquery('english', 'The & Fat & Rats');
+   to_tsquery
+---------------
+ 'fat' & 'rat'
+(1 row)
+```
+
+像在基本tsquery中的输入一样，weight(s)可以附加到每个词素来限制它只匹配那些有相同weight(s)的tsvector词素。比如：
+
+```sql
+mogdb=# SELECT to_tsquery('english', 'Fat | Rats:AB');
+    to_tsquery
+------------------
+ 'fat' | 'rat':AB
+(1 row)
+```
+
+同时，*也可以附加到词素来指定前缀匹配：
+
+```sql
+mogdb=# SELECT to_tsquery('supern:*A & star:A*B');
+        to_tsquery
+--------------------------
+ 'supern':*A & 'star':*AB
+(1 row)
+```
+
+这样的词素将匹配tsquery中指定字符串和权重的项。
+
+```
+plainto_tsquery([ config regconfig, ] querytext text) returns tsquery
+```
+
+plainto_tsquery将未格式化的文本querytext变换为tsquery。类似于to_tsvector，文本被解析并且标准化，然后在存在的词之间插入&（AND）布尔算子。
+
+比如：
+
+```sql
+mogdb=# SELECT plainto_tsquery('english', 'The Fat Rats');
+ plainto_tsquery
+-----------------
+ 'fat' & 'rat'
+(1 row)
+```
+
+请注意，plainto_tsquery无法识别布尔运算符、权重标签，或在其输入中的前缀匹配标签：
+
+```sql
+mogdb=# SELECT plainto_tsquery('english', 'The Fat & Rats:C');
+   plainto_tsquery
+---------------------
+ 'fat' & 'rat' & 'c'
+(1 row)
+```
+
+在这里，所有输入的标点符号作为空格符号丢弃。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/3-ranking-search-results.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/3-ranking-search-results.md
new file mode 100644
index 0000000000000000000000000000000000000000..4bc31f39e823ed6d055cdad2e9a8796bc378e621
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/3-ranking-search-results.md
@@ -0,0 +1,108 @@
+---
+title: 排序查询结果
+summary: 排序查询结果
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 排序查询结果
+
+排序试图针对特定查询衡量文档的相关度，从而将众多的匹配文档中相关度最高的文档排在最前。MogDB提供了两个预置的排序函数。函数考虑了词法，距离和结构信息；也就是，他们考虑查询词在文档中出现的频率、紧密程度、以及他们出现的地方在文档中的重要性。然而，相关性的概念是模糊的，并且是跟应用强相关的。不同的应用程序可能需要额外的信息来排序，比如，文档的修改时间，内置的排序函数等。也可以开发自己的排序函数或者采用附加因素组合这些排序函数的结果来满足特定需求。
+
+两个预置的排序函数：
+
+```sql
+ts_rank([ weights float4[], ] vector tsvector, query tsquery [, normalization integer ]) returns float4
+```
+
+基于词素匹配率对vector进行排序：
+
+```sql
+ts_rank_cd([ weights float4[], ] vector tsvector, query tsquery [, normalization integer ]) returns float4
+```
+
+该函数需要位置信息的输入。因此它不能在”剥离”tsvector值的情况下运行-它将总是返回零。
+
+对于这两个函数，可选的weights参数提供给词加权重的能力，词的权重大小取决于所加的权值。权重阵列指定在排序时为每类词汇加多大的权重。
+
+```sql
+{D-weight, C-weight, B-weight, A-weight}
+```
+
+如果没有提供weights，则使用缺省值：{0.1, 0.2, 0.4, 1.0}。
+
+通常的权重是用来标记文档特殊领域的词，如标题或最初的摘要，所以相对于文章主体中的词它们有着更高或更低的重要性。
+
+由于较长的文档有更多的机会包含查询词，因此有必要考虑文档的大小。例如，包含有5个搜索词的一百字文档比包含有5个搜索词的一千字文档相关性更高。两个预置的排序函数都采用了一个整型的标准化选项来定义文档长度是否影响排序及如何影响。这个整型选项控制多个行为，所以它是一个屏蔽字：可以使用|指定一个或多个行为（例如，2|4）。
+
+- 0（缺省）表示：跟长度大小没有关系
+- 1 表示：排名（rank）除以（文档长度的对数+1）
+- 2表示：排名除以文档的长度
+- 4表示：排名除以两个扩展词间的调和平均距离。只能使用ts_rank_cd实现
+- 8表示：排名除以文档中单独词的数量
+- 16表示：排名除以单独词数量的对数+1
+- 32表示：排名除以排名本身+1
+
+当指定多个标志位时，会按照所列的顺序依次进行转换。
+
+需要特别注意的是，排序函数不使用任何全局信息，所以不可能产生一个某些情况下需要的1%或100%的理想标准值。标准化选项32 (rank/(rank+1))可用于所有规模的从零到一之间的排序，当然，这只是一个表面变化；它不会影响搜索结果的排序。
+
+下面是一个例子，仅选择排名前十的匹配：
+
+```sql
+mogdb=# SELECT id, title, ts_rank_cd(to_tsvector(body), query) AS rank
+FROM tsearch.pgweb, to_tsquery('america') query
+WHERE query @@ to_tsvector(body)
+ORDER BY rank DESC
+LIMIT 10;
+ id |  title  | rank
+----+---------+------
+ 11 | Brazil  |   .2
+  2 | America |   .1
+ 12 | Canada  |   .1
+ 13 | Mexico  |   .1
+(4 rows)
+```
+
+这是使用标准化排序的相同例子：
+
+```sql
+mogdb=# SELECT id, title, ts_rank_cd(to_tsvector(body), query, 32 /* rank/(rank+1) */ ) AS rank
+FROM tsearch.pgweb, to_tsquery('america') query
+WHERE  query @@ to_tsvector(body)
+ORDER BY rank DESC
+LIMIT 10;
+ id |  title  |   rank
+----+---------+----------
+ 11 | Brazil  |  .166667
+  2 | America | .0909091
+ 12 | Canada  | .0909091
+ 13 | Mexico  | .0909091
+(4 rows)
+```
+
+下面是使用中文分词法排序查询的例子：
+
+```sql
+mogdb=# CREATE TABLE tsearch.ts_ngram(id int, body text);
+mogdb=# INSERT INTO tsearch.ts_ngram VALUES(1, '中文');
+mogdb=# INSERT INTO tsearch.ts_ngram VALUES(2, '中文检索');
+mogdb=# INSERT INTO tsearch.ts_ngram VALUES(3, '检索中文');
+--精确匹配
+mogdb=# SELECT id, body, ts_rank_cd(to_tsvector('ngram',body), query) AS rank FROM tsearch.ts_ngram, to_tsquery('中文') query WHERE query @@ to_tsvector(body);
+ id | body | rank
+----+------+------
+  1 | 中文 |   .1
+(1 row)
+
+--模糊匹配
+mogdb=# SELECT id, body, ts_rank_cd(to_tsvector('ngram',body), query) AS rank FROM tsearch.ts_ngram, to_tsquery('中文') query WHERE query @@ to_tsvector('ngram',body);
+ id |   body   | rank
+----+----------+------
+  3 | 检索中文 |   .1
+  1 | 中文     |   .1
+  2 | 中文检索 |   .1
+(3 rows)
+```
+
+排序要遍历每个匹配的tsvector，因此资源消耗多，可能会因为I/O限制导致排序慢。可是这是很难避免的，因为实际查询中通常会有大量的匹配。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/4-highlighting-results.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/4-highlighting-results.md
new file mode 100644
index 0000000000000000000000000000000000000000..793992919b253a77bc892dc1a7feba4359e9482d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/4-highlighting-results.md
@@ -0,0 +1,66 @@
+---
+title: 高亮搜索结果
+summary: 高亮搜索结果
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 高亮搜索结果
+
+搜索结果的理想显示是：列出每篇文档中与搜索相关的部分，并标识为什么与查询相关。搜索引擎能够显示标识了搜索词的文档片段。MogDB提供了函数ts_headline支持这部分功能。
+
+```sql
+ts_headline([ config regconfig, ] document text, query tsquery [, options text ]) returns text
+```
+
+ts_headline的输入是带有查询条件的文档，其返回文档中的摘录，在摘录中查询词是高亮显示的。用来解析文档的分词器由config参数指定。如果省略config，则使用default_text_search_config的值所指定的分词器。
+
+指定options字符串时，需由一个或多个option=value对组成，且必须用逗号分隔。options可以是下面的选项：
+
+- StartSel，StopSel：分隔文档中出现的查询词，以区别于其他摘录词。当包含有空格或逗号时，必须用双引号将字符串引起来。
+- MaxWords，MinWords：定义摘录的最长和最短值。
+- ShortWord：在摘录的开始和结束会丢弃此长度或更短的词。默认值3会消除常见的英语冠词。
+- HighlightAll：布尔标志。如果为真，整个文档将作为摘录。忽略前面三个参数的值。
+- MaxFragments：要显示的文本摘录或片段的最大数量。默认值0表示选择非片段的摘录生成方法。 大于0的值表示选择基于片段的摘录生成。此方法查找带有尽可能多查询词的文本片段，并显示查询词周围的上下文片段。因此，查询词临近每个片段的中间，且查询词两边都有词。每个片段至多有MaxWords，并且长度为ShortWord或更短的词在每一个片段开始和结束被丢弃。如果在文档中没有找到所有的查询词，则文档中开头将显示MinWords单片段。
+- FragmentDelimiter：当有一个以上的片段时，通过该字符串分隔这些片段。
+
+不声明选项时，采用下面的缺省值：
+
+```sql
+StartSel=<b>, StopSel=</b>,
+MaxWords=35, MinWords=15, ShortWord=3, HighlightAll=FALSE,
+MaxFragments=0, FragmentDelimiter=" ... "
+```
+
+例如：
+
+```sql
+mogdb=# SELECT ts_headline('english',
+'The most common type of search
+is to find all documents containing given query terms
+and return them in order of their similarity to the
+query.',
+to_tsquery('english', 'query & similarity'));
+                        ts_headline
+------------------------------------------------------------
+ containing given <b>query</b> terms
+ and return them in order of their <b>similarity</b> to the
+ <b>query</b>.
+(1 row)
+
+mogdb=# SELECT ts_headline('english',
+'The most common type of search
+is to find all documents containing given query terms
+and return them in order of their similarity to the
+query.',
+to_tsquery('english', 'query & similarity'),
+'StartSel = <, StopSel = >');
+                      ts_headline
+-------------------------------------------------------
+ containing given <query> terms
+ and return them in order of their <similarity> to the
+ <query>.
+(1 row)
+```
+
+ts_headline使用原始文档，而不是tsvector摘录，因此使用起来会慢，应慎重使用。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/4-additional-features/1-manipulating-tsvector.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/4-additional-features/1-manipulating-tsvector.md
new file mode 100644
index 0000000000000000000000000000000000000000..72583ded8217e34731aefa3fa6f9b73fe54d9ee4
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/4-additional-features/1-manipulating-tsvector.md
@@ -0,0 +1,31 @@
+---
+title: 处理tsvector
+summary: 处理tsvector
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 处理tsvector
+
+MogDB提供了用来操作tsvector类型的函数和操作符。
+
+- tsvector || tsvector
+
+  tsvector连接操作符返回一个新的tsvector类型，它综合了两个tsvector中词素和位置信息，并保留词素的位置信息和权重标签。右侧的tsvector的起始位置位于左侧tsvector的最后位置，因此，新生成的tsvector几乎等同于将两个原始文档字串连接后进行to_tsvector操作。（这个等价是不准确的，因为任何从左边tsvector中删除的停用词都不会影响结果，但是，在使用文本连接时，则会影响词素在右侧tsvector中的位置。）
+
+  相较于对文本进行连接后再执行to_tsvector操作，使用tsvector类型进行连接操作的优势在于，可以对文档的不同部分使用不同配置进行解析。因为setweight函数会对给定的tsvector中的语素进行统一设置，如果想要对文档的不同部分设置不同的权重，需要在连接之前对文本进行解析和权重设置。
+
+- setweight(vector tsvector, weight “char”) returns tsvector
+
+  setweight返回一个输入tsvector的副本，其中每一个位置都使用给定的权重做了标记。权值可以为A、B、C或D（D是tsvector副本的默认权重，并且不在输出中呈现）。当对tsvector进行连接操作时，这些权重标签将会被保留，文档不同部分以不同的权重进行排序。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+  > 权重标签作用于位置，而不是词素。如果传入的tsvector已经被剥离了位置信息，那么setweight函数将什么都不做。
+
+- length(vector tsvector) returns integer
+
+  返回vector中的词素的数量。
+
+- strip(vector tsvector) returns tsvector
+
+  返回一个tsvector类型，其中包含输入的tsvector的同义词，但不包含任何位置和权重信息。虽然在相关性排序中，这里返回的tsvector要比未拆分的tsvector的作用小很多，但它通常都比未拆分的tsvector小的多。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/4-additional-features/2-manipulating-queries.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/4-additional-features/2-manipulating-queries.md
new file mode 100644
index 0000000000000000000000000000000000000000..8e85ad650ae2b7cc10087ead8429ba34d5e44346
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/4-additional-features/2-manipulating-queries.md
@@ -0,0 +1,52 @@
+---
+title: 处理查询
+summary: 处理查询
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 处理查询
+
+MogDB提供了函数和操作符用来操作tsquery类型的查询。
+
+- tsquery && tsquery
+
+  返回两个给定查询tsquery的与结果。
+
+- tsquery || tsquery
+
+  返回两个给定查询tsquery的或结果。
+
+- !! tsquery
+
+  返回给定查询tsquery的非结果。
+
+- numnode(query tsquery) returns integer
+
+  返回tsquery中的节点数目（词素加操作符），这个函数在检查查询是否有效（返回值大于0），或者只包含停用词（返回值等于0）时，是有用的。例如：
+
+  ```sql
+  mogdb=# SELECT numnode(plainto_tsquery('the any'));
+  NOTICE:  text-search query contains only stop words or doesn't contain lexemes, ignored
+  CONTEXT:  referenced column: numnode
+   numnode
+  ---------
+         0
+
+  mogdb=# SELECT numnode('foo & bar'::tsquery);
+   numnode
+  ---------
+         3
+  ```
+
+- querytree(query tsquery) returns text
+
+  返回可用于索引搜索的tsquery部分，该函数对于检测非索引查询是有用的（例如只包含停用词或否定项）。例如:
+
+  ```sql
+  mogdb=# SELECT querytree(to_tsquery('!defined'));
+   querytree
+  -----------
+   T
+  (1 row)
+  ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/4-additional-features/3-rewriting-queries.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/4-additional-features/3-rewriting-queries.md
new file mode 100644
index 0000000000000000000000000000000000000000..06712a09566d0fb028acc65412f314c0c8e74e57
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/4-additional-features/3-rewriting-queries.md
@@ -0,0 +1,68 @@
+---
+title: 查询重写
+summary: 查询重写
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 查询重写
+
+ts_rewrite函数族可以从tsquery中搜索一个特定的目标子查询，并在该子查询每次出现的地方都替换为另一个子查询。 实际上这只是通过字串替换而得到的一个特定tsquery版本。目标子查询和替换查询组合起来可以被认为是一个重写规则。一组类似的重写规则可以为搜索提供强大的帮助。例如，可以使用同义词扩大搜索范围（例如，new york, big apple, nyc, gotham）或限制搜索范围在用户直接感兴趣的热点话题上。
+
+- ts_rewrite (query tsquery, target tsquery, substitute tsquery) returns tsquery
+
+  ts_rewrite的这种形式只适用于一个单一的重写规则：任何出现目标子查询的地方都被无条件替换。例如：
+
+  ```sql
+  mogdb=# SELECT ts_rewrite('a & b'::tsquery, 'a'::tsquery, 'c'::tsquery);
+   ts_rewrite
+  ------------
+   'b' & 'c'
+  ```
+
+- ts_rewrite (query tsquery, select text) returns tsquery
+
+  ts_rewrite的这种形式接受一个起始查询和SQL查询命令。 这里的查询命令是文本字串形式，必须产生两个tsquery列。查询结果的每一行，第一个字段的值（目标子查询） 都会被第二个字段（替代子查询）替换。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  > 当多个规则需要重写时，重写顺序非常重要； 因此在实践中需要使用ORDER BY将源查询按照某些字段进行排序。
+
+  例如：举一个现实生活中天文学上的例子。我们将使用表驱动的重写规则扩大supernovae的查询范围：
+
+  ```sql
+  mogdb=# CREATE TABLE tsearch.aliases (id int, t tsquery, s tsquery);
+
+  mogdb=# INSERT INTO tsearch.aliases VALUES(1, to_tsquery('supernovae'), to_tsquery('supernovae|sn'));
+
+  mogdb=# SELECT ts_rewrite(to_tsquery('supernovae & crab'), 'SELECT t, s FROM tsearch.aliases');
+
+             ts_rewrite
+  ---------------------------------
+   'crab' & ( 'supernova' | 'sn' )
+  ```
+
+  可以通过更新表修改重写规则：
+
+  ```sql
+  mogdb=# UPDATE tsearch.aliases
+  SET s = to_tsquery('supernovae|sn & !nebulae')
+  WHERE t = to_tsquery('supernovae');
+
+  mogdb=# SELECT ts_rewrite(to_tsquery('supernovae & crab'), 'SELECT t, s FROM tsearch.aliases');
+
+                   ts_rewrite
+  ---------------------------------------------
+   'crab' & ( 'supernova' | 'sn' & !'nebula' )
+  ```
+
+  需要重写的规则越多，重写操作就越慢。因为它要检查每一个可能匹配的规则。为了过滤明显的非候选规则，可以使用tsquery类型的操作符来实现。在下面的例子中， 我们只选择那些可能与原始查询匹配的规则：
+
+  ```sql
+  mogdb=# SELECT ts_rewrite('a & b'::tsquery, 'SELECT t,s FROM tsearch.aliases WHERE ''a & b''::tsquery @> t');
+
+   ts_rewrite
+  ------------
+   'b' & 'a'
+  (1 row)
+  mogdb=# DROP TABLE tsearch.aliases;
+  ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/4-additional-features/4-gathering-document-statistics.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/4-additional-features/4-gathering-document-statistics.md
new file mode 100644
index 0000000000000000000000000000000000000000..ab3b71f27040499a4266e390d616f3d1ef8406d3
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/4-additional-features/4-gathering-document-statistics.md
@@ -0,0 +1,50 @@
+---
+title: 收集文献统计
+summary: 收集文献统计
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 收集文献统计
+
+函数ts_stat可用于检查配置和查找候选停用词。
+
+```sql
+ts_stat(sqlquery text, [ weights text, ]
+        OUT word text, OUT ndoc integer,
+        OUT nentry integer) returns setof record
+```
+
+sqlquery是一个包含SQL查询语句的文本，该SQL查询将返回一个tsvector。ts_stat执行SQL查询语句并返回一个包含tsvector中每一个不同的语素（词）的统计信息。返回信息包括：
+
+- word text：词素。
+- ndoc integer：词素在文档（tsvector）中的编号。
+- nentry integer：词素出现的频率。
+
+如果设置了权重条件，只有标记了对应权重的词素才会统计频率。例如，在一个文档集中检索使用频率最高的十个单词：
+
+```sql
+mogdb=# SELECT * FROM ts_stat('SELECT to_tsvector(''english'', sr_reason_sk) FROM tpcds.store_returns WHERE sr_customer_sk < 10') ORDER BY nentry DESC, ndoc DESC, word LIMIT 10;
+   word | ndoc | nentry
+------+------+--------
+ 32   |    2 |      2
+ 33   |    2 |      2
+ 1    |    1 |      1
+ 10   |    1 |      1
+ 13   |    1 |      1
+ 14   |    1 |      1
+ 15   |    1 |      1
+ 17   |    1 |      1
+ 20   |    1 |      1
+ 22   |    1 |      1
+(10 rows)
+```
+
+同样的情况，但是只计算权重为A或者B的单词使用频率：
+
+```sql
+mogdb=# SELECT * FROM ts_stat('SELECT to_tsvector(''english'', sr_reason_sk) FROM tpcds.store_returns WHERE sr_customer_sk < 10', 'a') ORDER BY nentry DESC, ndoc DESC, word LIMIT 10;
+ word | ndoc | nentry
+------+------+--------
+(0 rows)
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/5-parser.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/5-parser.md
new file mode 100644
index 0000000000000000000000000000000000000000..bc7941a0bd8ccdb313fdb50b471daf06fb74e46f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/5-parser.md
@@ -0,0 +1,108 @@
+---
+title: 解析器
+summary: 解析器
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 解析器
+
+文本搜索解析器负责将原文档文本分解为多个token，并标识每个token的类型。这里的类型集由解析器本身定义。注意，解析器并不修改文本，它只是确定合理的单词边界。由于这一限制，人们更需要定制词典，而不是为每个应用程序定制解析器。
+
+目前MogDB提供了三个内置的解析器，分别为pg_catalog.default/pg_catalog.ngram/pg_catalog.pound，其中pg_catalog.default适用于英文分词场景，pg_catalog.ngram/pg_catalog.pound是为了支持中文全文检索功能新增的两种解析器，适用于中文及中英混合分词场景。
+
+内置解析器pg_catalog.default，它能识别23种token类型，显示在[表1](#defaultparsertype)中。
+
+**表 1** 默认解析器类型 <a id="defaultparsertype"> </a>
+
+| 别名            | 描述                                     | 示例                                                     |
+| :--------------------------------------- | :------------------ | :------------------------------------------------------- |
+| asciiword       | Word, all ASCII letters                  | elephant                                                 |
+| word            | Word, all letters                        | mañana                                                   |
+| numword         | Word, letters and digits                 | beta1                                                    |
+| asciihword      | Hyphenated word, all ASCII               | up-to-date                                               |
+| hword           | Hyphenated word, all letters             | lógico-matemática                                        |
+| numhword        | Hyphenated word, letters and digits      | mogdb-beta1                                              |
+| hword_asciipart | Hyphenated word part, all ASCII          | mogdb in the context mogdb-beta1                         |
+| hword_part      | Hyphenated word part, all letters        | lógico or matemática in the context lógico-matemática    |
+| hword_numpart   | Hyphenated word part, letters and digits | beta1 in the context mogdb-beta1                         |
+| email           | Email address                            | foo@example.com                                          |
+| protocol        | Protocol head                            | `http://`                                                  |
+| url             | URL                                      | example.com/stuff/index.html                             |
+| host            | Host                                     | example.com                                              |
+| url_path        | URL path                                 | /stuff/index.html, in the context of a URL               |
+| file            | File or path name                        | /usr/local/foo.txt, if not within a URL                  |
+| sfloat          | Scientific notation                      | -1.23E+56                                                |
+| float           | Decimal notation                         | -1.234                                                   |
+| int             | Signed integer                           | -1234                                                    |
+| uint            | Unsigned integer                         | 1234                                                     |
+| version         | Version number                           | 8.3.0                                                    |
+| tag             | XML tag                                  | &lt;a href="dictionaries.html"&gt;                       |
+| entity          | XML entity                               | &amp;                                                    |
+| blank           | Space symbols                            | (any whitespace or punctuation not otherwise recognized) |
+
+注意：对于解析器来说，一个“字母”的概念是由数据库的语言区域设置，即lc_ctype设置决定的。只包含基本ASCII字母的词被报告为一个单独的token类型，因为这类词有时需要被区分出来。大多数欧洲语言中，对token类型word和asciiword的处理方法是类似的。
+
+email不支持某些由RFC 5322定义的有效电子邮件字符。具体来说，可用于email用户名的非字母数字字符仅包含句号、破折号和下划线。
+
+解析器可能对同一内容进行重叠token。例如，包含连字符的单词将作为一个整体进行报告，其组件也会分别被报告：
+
+```sql
+mogdb=# SELECT alias, description, token FROM ts_debug('english','foo-bar-beta1');
+      alias      |               description                |     token
+-----------------+------------------------------------------+---------------
+ numhword        | Hyphenated word, letters and digits      | foo-bar-beta1
+ hword_asciipart | Hyphenated word part, all ASCII          | foo
+ blank           | Space symbols                            | -
+ hword_asciipart | Hyphenated word part, all ASCII          | bar
+ blank           | Space symbols                            | -
+ hword_numpart   | Hyphenated word part, letters and digits | beta1
+```
+
+这种行为是有必要的，因为它支持搜索整个复合词和各组件。这里是另一个例子：
+
+```sql
+mogdb=# SELECT alias, description, token FROM ts_debug('english','http://example.com/stuff/index.html');
+  alias   |  description  |            token
+----------+---------------+------------------------------
+ protocol | Protocol head | http://
+ url      | URL           | example.com/stuff/index.html
+ host     | Host          | example.com
+ url_path | URL path      | /stuff/index.html
+```
+
+N-gram是一种机械分词方法，适用于无语义中文分词场景。N-gram分词法可以保证分词的完备性，但是为了照顾所有可能，把很多不必要的词也加入到索引中，导致索引项增加。N-gram支持中文编码包括GBK、UTF-8。内置6种token类型，如[表2](#tokentype) 所示。
+
+**表 2** token类型 <a id="tokentype"> </a>
+
+| 别名        | 描述            |
+| :---------- | :-------------- |
+| zh_words    | chinese words   |
+| en_word     | english word    |
+| numeric     | numeric data    |
+| alnum       | alnum string    |
+| grapsymbol  | graphic symbol  |
+| multisymbol | multiple symbol |
+
+Pound是一种固定格式分词方法，适用于无语意但待解析文本以固定分隔符分割开来的中英文分词场景。支持中文编码包括GBK、UTF8，支持英文编码包括ASCII。内置6种token类型，如[表3 token类型](#biao3tokentype)所示；支持5种分隔符，如[表4](#biao4spacetype)所示，在用户不进行自定义设置的情况下分隔符默认为“#”。Pound限制单个token长度不能超过256个字符。
+
+**表 3** token类型 <a id="biao3tokentype"> </a>
+
+| 别名        | 描述            |
+| :---------- | :-------------- |
+| zh_words    | chinese words   |
+| en_word     | english word    |
+| numeric     | numeric data    |
+| alnum       | alnum string    |
+| grapsymbol  | graphic symbol  |
+| multisymbol | multiple symbol |
+
+**表 4** 分隔符类型 <a id="biao4spacetype"> </a>
+
+| 分隔符 | 描述              |
+| :----- | :---------------- |
+| @      | Special character |
+| #      | Special character |
+| $      | Special character |
+| %      | Special character |
+| /      | Special character |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/1-dictionaries-overview.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/1-dictionaries-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..ca93cc87462ca9db0813fb298701db58d0f144e0
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/1-dictionaries-overview.md
@@ -0,0 +1,36 @@
+---
+title: 词典概述
+summary: 词典概述
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 词典概述
+
+词典用于定义停用词（stop words），即全文检索时不搜索哪些词。
+
+词典还可以用于对同一词的不同形式进行规范化，这样同一个词的不同派生形式都可以进行匹配。规范化后的词称为词位（lexeme）。
+
+除了提高检索质量外，词的规范化和删除停用词可以减少文档tsvector格式的大小， 从而提高性能。词的规范化和删除停用词并不总是具有语言学意义，用户可以根据应用环境在词典定义文件中自定义规范化和删除规则。
+
+一个词典是一个程序，接收标记（token）作为输入，并返回：
+
+- 如果token在词典中已知，返回对应lexeme数组（注意，一个标记可能对应多个lexeme）。
+- 一个lexeme。一个新token会代替输入token被传递给后继词典（当前词典可被称为过滤词典）。
+- 如果token在词典中已知，但它是一个停用词，返回空数组。
+- 如果词典不能识别输入的token，返回NULL。
+
+MogDB提供了多种语言的预定义字典，同时提供了五种预定义的词典模板，分别是Simple、Synonym、Thesaurus、Ispell和Snowball，可用于创建自定义参数的新词典。
+
+在使用全文检索时，建议用户：
+
+- 可以在文本搜索配置中定义一个解析器，以及一组用于处理该解析器的输出标记词典。对于解析器返回的每个标记类型，可以在配置中指定不同的词典列表进行处理。当解析器输出一种类型的标记后，在对应列表的每个字典中会查阅该标记，直到某个词典识别它。如果它被识别为一个停用词， 或者没有任何词典识别，该token将被丢弃，即不被索引或检索到。通常情况下，第一个返回非空结果的词典决定了最终结果，后继词典将不会继续处理。但是一个过滤类型的词典可以依据规则替换输入token，然后将替换后的token传递给后继词典进行处理。
+
+- 配置字典列表的一般规则是，第一个位置放置一个应用范围最小的、最具体化定义的词典，其次是更一般化定义的词典， 最后是一个普适定义的词典，比如Snowball词干词典或Simple词典。在下面例子中，对于一个针对天文学的文本搜索配置astro_en，可以定义标记类型asciiword（ASCII词）对应的词典列表为：天文术语的Synonym同义词词典， Ispell英语词典和Snowball 英语词干词典。
+
+  ```sql
+  mogdb=# ALTER TEXT SEARCH CONFIGURATION astro_en
+    ADD MAPPING FOR asciiword WITH astro_syn, english_ispell, english_stem;
+  ```
+
+  过滤类型的词典可以放置在词典列表中除去末尾的任何地方，放置在末尾时是无效的。使用这些词典对标记进行部分规范化，可以有效简化后继词典的处理。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/2-stop-words.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/2-stop-words.md
new file mode 100644
index 0000000000000000000000000000000000000000..19ca18feb222e44f6a31f5d0015a719cb1aea091
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/2-stop-words.md
@@ -0,0 +1,33 @@
+---
+title: 停用词
+summary: 停用词
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 停用词
+
+停用词是很常见的词，几乎出现在每一个文档中，并且没有区分值。因此，在全文搜索的语境下可忽视它们。停用词处理逻辑和词典类型相关。例如，Ispell词典会先对标记进行规范化，然后再查看停用词表，而Snowball词典会最先检查输入标记是否为停用词。
+
+例如，每个英文文本包含像a和the的单词，因此没必要将它们存储在索引中。然而，停用词影响tsvector中的位置，同时位置也会影响相关度：
+
+```sql
+mogdb=# SELECT to_tsvector('english','in the list of stop words');
+        to_tsvector
+----------------------------
+ 'list':3 'stop':5 'word':6
+```
+
+位置1、2、4是停用词，所以不显示。为包含和不包含停用词的文档计算出的排序是完全不同的：
+
+```sql
+mogdb=# SELECT ts_rank_cd (to_tsvector('english','in the list of stop words'), to_tsquery('list & stop'));
+ ts_rank_cd
+------------
+        .05
+
+mogdb=# SELECT ts_rank_cd (to_tsvector('english','list stop words'), to_tsquery('list & stop'));
+ ts_rank_cd
+------------
+         .1
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/3-simple-dictionary.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/3-simple-dictionary.md
new file mode 100644
index 0000000000000000000000000000000000000000..16fa3ecfcefc2c678b81f494b65e345ae684c974
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/3-simple-dictionary.md
@@ -0,0 +1,64 @@
+---
+title: Simple词典
+summary: Simple词典
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Simple词典
+
+Simple词典首先将输入标记转换为小写字母，然后检查停用词表。如果识别为停用词则返回空数组，即表示该标记会被丢弃。否则，输入标记的小写形式作为规范化后的lexeme返回。此外，Simple词典可通过设置参数Accept为false（默认值true），将非停用词报告为未识别，传递给后继词典继续处理。
+
+## 注意事项
+
+- 大多数词典的功能依赖于词典定义文件，词典定义文件名仅支持小写字母、数字、下划线组合。
+- 临时模式pg_temp下不允许创建词典。
+- 词典定义文件的字符集编码必须为UTF-8格式。实际应用时，如果与数据库的字符编码格式不一致，在读入词典定义文件时会进行编码转换。
+- 通常情况下，每个session仅读取词典定义文件一次，当且仅当在第一次使用该词典时。需要修改词典文件时，可通过ALTER TEXT SEARCH DICTIONARY命令进行词典定义文件的更新和重新加载。
+
+## 操作步骤
+
+1. 创建Simple词典。
+
+   ```sql
+   mogdb=# CREATE TEXT SEARCH DICTIONARY public.simple_dict (
+        TEMPLATE = pg_catalog.simple,
+        STOPWORDS = english
+   );
+   ```
+
+   其中，停用词表文件全名为english.stop。关于创建simple词典的语法和更多参数，请参见[CREATE TEXT SEARCH DICTIONARY](65-CREATE-TEXT-SEARCH-DICTIONARY)。
+
+2. 使用Simple词典。
+
+   ```sql
+   mogdb=# SELECT ts_lexize('public.simple_dict','YeS');
+    ts_lexize
+   -----------
+    {yes}
+   (1 row)
+
+   mogdb=# SELECT ts_lexize('public.simple_dict','The');
+    ts_lexize
+   -----------
+    {}
+   (1 row)
+   ```
+
+3. 设置参数ACCEPT=false，使Simple词典返回NULL，而不是返回非停用词的小写形式。
+
+   ```sql
+   mogdb=# ALTER TEXT SEARCH DICTIONARY public.simple_dict ( Accept = false );
+   ALTER TEXT SEARCH DICTIONARY
+   mogdb=# SELECT ts_lexize('public.simple_dict','YeS');
+    ts_lexize
+   -----------
+
+   (1 row)
+
+   mogdb=# SELECT ts_lexize('public.simple_dict','The');
+    ts_lexize
+   -----------
+    {}
+   (1 row)
+   ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/4-synonym-dictionary.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/4-synonym-dictionary.md
new file mode 100644
index 0000000000000000000000000000000000000000..6504506c8139612d06e6d5d174809a385a397642
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/4-synonym-dictionary.md
@@ -0,0 +1,116 @@
+---
+title: Synonym词典
+summary: Synonym词典
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Synonym词典
+
+Synonym词典用于定义、识别token的同义词并转化，不支持词组（词组形式的同义词可用Thesaurus词典定义，详细请参见[Thesaurus词典](5-thesaurus-dictionary)）。
+
+## 示例
+
+- Synonym词典可用于解决语言学相关问题，例如，为避免使单词”Paris”变成”pari”，可在Synonym词典文件中定义一行”Paris paris”，并将该词典放置在预定义的english_stem词典之前。
+
+  ```sql
+  mogdb=# SELECT * FROM ts_debug('english', 'Paris');
+     alias   |   description   | token |  dictionaries  |  dictionary  | lexemes
+  -----------+-----------------+-------+----------------+--------------+---------
+   asciiword | Word, all ASCII | Paris | {english_stem} | english_stem | {pari}
+  (1 row)
+
+  mogdb=# CREATE TEXT SEARCH DICTIONARY my_synonym (
+      TEMPLATE = synonym,
+      SYNONYMS = my_synonyms,
+      FILEPATH = 'file:///home/dicts/'
+  );
+
+  mogdb=# ALTER TEXT SEARCH CONFIGURATION english
+      ALTER MAPPING FOR asciiword
+      WITH my_synonym, english_stem;
+
+  mogdb=# SELECT * FROM ts_debug('english', 'Paris');
+     alias   |   description   | token |       dictionaries        | dictionary | lexemes
+  -----------+-----------------+-------+---------------------------+------------+---------
+   asciiword | Word, all ASCII | Paris | {my_synonym,english_stem} | my_synonym | {paris}
+  (1 row)
+
+  mogdb=# SELECT * FROM ts_debug('english', 'paris');
+     alias   |   description   | token |       dictionaries        | dictionary | lexemes
+  -----------+-----------------+-------+---------------------------+------------+---------
+   asciiword | Word, all ASCII | Paris | {my_synonym,english_stem} | my_synonym | {paris}
+  (1 row)
+
+  mogdb=# ALTER TEXT SEARCH DICTIONARY my_synonym ( CASESENSITIVE=true);
+
+  mogdb=# SELECT * FROM ts_debug('english', 'Paris');
+     alias   |   description   | token |       dictionaries        | dictionary | lexemes
+  -----------+-----------------+-------+---------------------------+------------+---------
+   asciiword | Word, all ASCII | Paris | {my_synonym,english_stem} | my_synonym | {paris}
+  (1 row)
+
+  mogdb=# SELECT * FROM ts_debug('english', 'paris');
+     alias   |   description   | token |       dictionaries        | dictionary | lexemes
+  -----------+-----------------+-------+---------------------------+------------+---------
+   asciiword | Word, all ASCII | Paris | {my_synonym,english_stem} | my_synonym | {pari}
+  (1 row)
+
+  ```
+
+  其中，同义词词典文件全名为my_synonyms.syn，所在目录为当前连接数据库主节点的/home/dicts/下。关于创建词典的语法和更多参数，请参见[ALTER TEXT SEARCH DICTIONARY](26-ALTER-TEXT-SEARCH-DICTIONARY)。
+
+- 星号（*）可用于词典文件中的同义词结尾，表示该同义词是一个前缀。在to_tsvector()中该星号将被忽略，但在to_tsquery()中会匹配该前缀并对应输出结果（参照[处理查询](2-manipulating-queries)一节）。
+
+  假设词典文件synonym_sample.syn内容如下：
+
+  ```
+  postgres        pgsql
+  postgresql      pgsql
+  postgre pgsql
+  gogle   googl
+  indices index*
+  ```
+
+  创建并使用词典：
+
+  ```sql
+  mogdb=# CREATE TEXT SEARCH DICTIONARY syn (
+      TEMPLATE = synonym,
+      SYNONYMS = synonym_sample
+  );
+
+  mogdb=# SELECT ts_lexize('syn','indices');
+   ts_lexize
+  -----------
+   {index}
+  (1 row)
+
+  mogdb=# CREATE TEXT SEARCH CONFIGURATION tst (copy=simple);
+
+  mogdb=# ALTER TEXT SEARCH CONFIGURATION tst ALTER MAPPING FOR asciiword WITH syn;
+
+  mogdb=# SELECT to_tsvector('tst','indices');
+   to_tsvector
+  -------------
+   'index':1
+  (1 row)
+
+  mogdb=# SELECT to_tsquery('tst','indices');
+   to_tsquery
+  ------------
+   'index':*
+  (1 row)
+
+  mogdb=# SELECT 'indexes are very useful'::tsvector;
+              tsvector
+  ---------------------------------
+   'are' 'indexes' 'useful' 'very'
+  (1 row)
+
+  mogdb=# SELECT 'indexes are very useful'::tsvector @@ to_tsquery('tst','indices');
+   ?column?
+  ----------
+   t
+  (1 row)
+  ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/5-thesaurus-dictionary.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/5-thesaurus-dictionary.md
new file mode 100644
index 0000000000000000000000000000000000000000..fd6b10f36fd049b3ab32761ec6c9f065e97f39e8
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/5-thesaurus-dictionary.md
@@ -0,0 +1,92 @@
+---
+title: Thesaurus词典
+summary: Thesaurus词典
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Thesaurus词典
+
+Thesaurus词典，也叫做分类词典（缩写为TZ），是一组定义了词以及词组间关系的集合，包括广义词（BT）、狭义词（NT）、首选词、非首选词、相关词等。根据词典文件中的定义，TZ词典用一个指定的短语替换对应匹配的所有短语，并且可选择保留原始短语进行索引。TZ词典实际上是Synonym词典的一个扩展，增加了短语支持。
+
+## 注意事项
+
+- 由于TZ词典需要识别短语，所以在处理过程中必须保存当前状态并与解析器进行交互，以决定是否处理下一个token或是结束当前识别。此外，TZ词典配置时需谨慎，如果设置TZ词典仅处理asciiword类型的token，则类似one 7的分类词典定义将不会生效，因为uint类型的token不会传给TZ词典处理。
+- 在索引期间要用到分类词典，因此分类词典参数中的任何变化都要求重新索引。对于其他大多数类型的词典来说，类似添加或删除停用词这种修改并不需要强制重新索引。
+
+## 操作步骤
+
+1. 创建一个名为thesaurus_astro的TZ词典。
+
+   以一个简单的天文学词典thesaurus_astro为例，其中定义了两组天文短语及其同义词如下：
+
+   ```sql
+   supernovae stars : sn
+   crab nebulae : crab
+   ```
+
+   执行如下语句创建TZ词典：
+
+   ```sql
+   mogdb=# CREATE TEXT SEARCH DICTIONARY thesaurus_astro (
+       TEMPLATE = thesaurus,
+       DictFile = thesaurus_astro,
+       Dictionary = pg_catalog.english_stem,
+       FILEPATH = 'file:///home/dicts/'
+   );
+   ```
+
+   其中，词典定义文件全名为thesaurus_astro.ths，所在目录为当前连接数据库主节点的/home/dicts/下 。子词典pg_catalog.english_stem是预定义的Snowball类型的英语词干词典，用于规范化输入词，子词典自身相关配置（例如停用词等）不在此处显示。关于创建词典的语法和更多参数，请参见[CREATE TEXT SEARCH DICTIONARY](65-CREATE-TEXT-SEARCH-DICTIONARY)。
+
+2. 创建词典后，将其绑定到对应文本搜索配置中需要处理的token类型上：
+
+   ```sql
+   mogdb=# ALTER TEXT SEARCH CONFIGURATION russian
+       ALTER MAPPING FOR asciiword, asciihword, hword_asciipart
+       WITH thesaurus_astro, english_stem;
+   ```
+
+3. 使用TZ词典。
+
+   - 测试TZ词典。
+
+     ts_lexize函数对于测试TZ词典作用不大，因为该函数是按照单个token处理输入。可以使用plainto_tsquery、to_tsvector、to_tsquery函数测试TZ词典，这些函数能够将输入分解成多个token（to_tsquery函数需要将输入加上引号）。
+
+     ```sql
+     mogdb=# SELECT plainto_tsquery('russian','supernova star');
+      plainto_tsquery
+     -----------------
+      'sn'
+     (1 row)
+
+     mogdb=# SELECT to_tsvector('russian','supernova star');
+      to_tsvector
+     -------------
+      'sn':1
+     (1 row)
+
+     mogdb=# SELECT to_tsquery('russian','''supernova star''');
+      to_tsquery
+     ------------
+      'sn'
+     (1 row)
+
+     ```
+
+     其中，supernova star匹配了词典thesaurus_astro定义中的supernovae stars，这是因为在thesaurus_astro词典定义中指定了Snowball类型的子词典english_stem，该词典移除了e和s。
+
+   - 如果同时需要索引原始短语，只要将其同时放置在词典定义文件中对应定义的右侧即可，如下：
+
+     ```sql
+     supernovae stars : sn supernovae stars
+
+     mogdb=# ALTER TEXT SEARCH DICTIONARY thesaurus_astro (
+         DictFile = thesaurus_astro,
+         FILEPATH = 'file:///home/dicts/');
+
+     mogdb=# SELECT plainto_tsquery('russian','supernova star');
+            plainto_tsquery
+     -----------------------------
+      'sn' & 'supernova' & 'star'
+     (1 row)
+     ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/6-ispell-dictionary.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/6-ispell-dictionary.md
new file mode 100644
index 0000000000000000000000000000000000000000..0dff4a6a9ad0ba6a5d0c40d805f857ee4c800b99
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/6-ispell-dictionary.md
@@ -0,0 +1,49 @@
+---
+title: Ispell词典
+summary: Ispell词典
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Ispell词典
+
+Ispell词典模板支持词法词典，它可以把一个词的各种语言学形式规范化成相同的词位。比如，一个Ispell英语词典可以匹配搜索词bank的词尾变化和词形变化，如banking、banked、banks、banks'和bank's等。
+
+MogDB不提供任何预定义的Ispell类型词典或词典文件。dict文件和affix文件支持多种开源词典格式，包括Ispell、MySpell和Hunspell等。
+
+## 操作步骤
+
+1. 获取词典定义文件和词缀文件。
+
+   用户可以使用开源词典，直接获取的开源词典后缀名可能为.aff和.dic，此时需要将扩展名改为.affix和.dict。此外，对于某些词典文件，还需要使用下面的命令把字符转换成 UTF-8 编码，比如挪威语词典：
+
+   ```bash
+   iconv -f ISO_8859-1 -t UTF-8 -o nn_no.affix nn_NO.aff
+   iconv -f ISO_8859-1 -t UTF-8 -o nn_no.dict nn_NO.dic
+   ```
+
+2. 创建Ispell词典。
+
+   ```sql
+   mogdb=# CREATE TEXT SEARCH DICTIONARY norwegian_ispell (
+       TEMPLATE = ispell,
+       DictFile = nn_no,
+       AffFile = nn_no,
+       FilePath = 'file:///home/dicts'
+   );
+   ```
+
+   其中，词典文件全名为nn_no.dict和nn_no.affix，所在目录为当前连接数据库主节点的/home/dicts/下 。关于创建词典的语法和更多参数，请参见[CREATE TEXT SEARCH DICTIONARY](65-CREATE-TEXT-SEARCH-DICTIONARY)。
+
+3. 使用Ispell词典进行复合词拆分。
+
+   ```sql
+   mogdb=# SELECT ts_lexize('norwegian_ispell', 'sjokoladefabrikk');
+         ts_lexize
+   ---------------------
+    {sjokolade,fabrikk}
+   (1 row)
+
+   ```
+
+   MySpell不支持复合词，Hunspell对复合词有较好的支持。MogDB仅支持Hunspell中基本的复合词操作。通常情况下，Ispell词典能够识别的词是一个有限集合，其后应该配置一个更广义的词典，例如一个可以识别所有词的Snowball词典。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/7-snowball-dictionary.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/7-snowball-dictionary.md
new file mode 100644
index 0000000000000000000000000000000000000000..be21e1122a9729bc098cee354b05999c93e04681
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/6-dictionaries/7-snowball-dictionary.md
@@ -0,0 +1,14 @@
+---
+title: Snowball词典
+summary: Snowball词典
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# Snowball词典
+
+Snowball词典模板支持词干分析词典，基于Martin Porter的Snowball项目，内置有许多语言的词干分析算法。MogDB中预定义有多种语言的Snowball词典，可通过系统表[PG_TS_DICT](PG_TS_DICT)查看预定义的词干分析词典以及支持的语言词干分析算法。
+
+无论是否可以简化，Snowball词典将标示所有输入为已识别，因此它应当被放置在词典列表的最后。把Snowball词典放在任何其他词典前面会导致后继词典失效，因为输入token不会通过Snowball词典进入到下一个词典。
+
+关于Snowball词典的语法，请参见[CREATE TEXT SEARCH DICTIONARY](65-CREATE-TEXT-SEARCH-DICTIONARY)。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/7-configuration-examples.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/7-configuration-examples.md
new file mode 100644
index 0000000000000000000000000000000000000000..2e92ba0a9559d7543b74aed3759c2fc045e3fc17
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/7-configuration-examples.md
@@ -0,0 +1,116 @@
+---
+title: 配置示例
+summary: 配置示例
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 配置示例
+
+文本搜索配置（Text Search Configuration），指定了将文档转换成tsvector过程中所必需的组件：
+
+- 解析器，用于把文本分解成标记token。
+- 词典列表，用于将每个token转换成词位lexeme。
+
+每次to_tsvector或to_tsquery函数调用时，都需要指定一个文本搜索配置来指定具体的处理过程。GUC参数**default_text_search_config**指定了默认的文本搜索配置，当文本搜索函数中没有显式指定文本搜索配置参数时，将会使用该默认值进行处理。
+
+MogDB中预定义有一些可用的文本搜索配置，用户也可创建自定义的文本搜索配置。此外，为了便于管理文本搜索对象，还提供有多个gsql元命令，可以显示有关文本搜索对象的信息。（详细请参见《工具参考》中“客户端工具 \>[元命令参考](client-tool#元命令参考)”章节）。
+
+## 操作步骤
+
+1. 创建一个文本搜索配置ts_conf，复制预定义的文本搜索配置english。
+
+   ```sql
+   mogdb=# CREATE TEXT SEARCH CONFIGURATION ts_conf ( COPY = pg_catalog.english );
+   CREATE TEXT SEARCH CONFIGURATION
+   ```
+
+2. 创建Synonym词典。
+
+   假设同义词词典定义文件pg_dict.syn内容如下：
+
+   ```
+   postgres    pg
+   pgsql       pg
+   postgresql  pg
+   ```
+
+   执行如下语句创建Synonym词典：
+
+   ```sql
+   mogdb=# CREATE TEXT SEARCH DICTIONARY pg_dict (
+        TEMPLATE = synonym,
+        SYNONYMS = pg_dict,
+        FILEPATH = 'file:///home/dicts'
+    );
+   ```
+
+3. 创建一个Ispell词典english_ispell（词典定义文件来自开源词典）。
+
+   ```sql
+   mogdb=# CREATE TEXT SEARCH DICTIONARY english_ispell (
+       TEMPLATE = ispell,
+       DictFile = english,
+       AffFile = english,
+       StopWords = english,
+       FILEPATH = 'file:///home/dicts'
+   );
+   ```
+
+4. 设置文本搜索配置ts_conf，修改某些类型的token对应的词典列表。关于token类型的详细信息，请参见[解析器](5-parser)。
+
+   ```sql
+   mogdb=# ALTER TEXT SEARCH CONFIGURATION ts_conf
+       ALTER MAPPING FOR asciiword, asciihword, hword_asciipart,
+                         word, hword, hword_part
+       WITH pg_dict, english_ispell, english_stem;
+   ```
+
+5. 在文本搜索配置中，选择设置不索引或搜索某些token类型。
+
+   ```sql
+   mogdb=# ALTER TEXT SEARCH CONFIGURATION ts_conf
+       DROP MAPPING FOR email, url, url_path, sfloat, float;
+   ```
+
+6. 使用文本检索调测函数ts_debug()对所创建的词典配置ts_conf进行测试。
+
+   ```sql
+   mogdb=# SELECT * FROM ts_debug('ts_conf', '
+   PostgreSQL, the highly scalable, SQL compliant, open source object-relational
+   database management system, is now undergoing beta testing of the next
+   version of our software.
+   ');
+   ```
+
+7. 可以设置当前session使用ts_conf作为默认的文本搜索配置。此设置仅在当前session有效。
+
+   ```sql
+   mogdb=# \dF+ ts_conf
+         Text search configuration "public.ts_conf"
+   Parser: "pg_catalog.default"
+         Token      |            Dictionaries
+   -----------------+-------------------------------------
+    asciihword      | pg_dict,english_ispell,english_stem
+    asciiword       | pg_dict,english_ispell,english_stem
+    file            | simple
+    host            | simple
+    hword           | pg_dict,english_ispell,english_stem
+    hword_asciipart | pg_dict,english_ispell,english_stem
+    hword_numpart   | simple
+    hword_part      | pg_dict,english_ispell,english_stem
+    int             | simple
+    numhword        | simple
+    numword         | simple
+    uint            | simple
+    version         | simple
+    word            | pg_dict,english_ispell,english_stem
+
+   mogdb=# SET default_text_search_config = 'public.ts_conf';
+   SET
+   mogdb=# SHOW default_text_search_config;
+    default_text_search_config
+   ----------------------------
+    public.ts_conf
+   (1 row)
+   ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/8-testing-and-debugging-text-search/1-testing-a-configuration.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/8-testing-and-debugging-text-search/1-testing-a-configuration.md
new file mode 100644
index 0000000000000000000000000000000000000000..14f6838d1b00df7a01eca80c66c6e9cf132ec581
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/8-testing-and-debugging-text-search/1-testing-a-configuration.md
@@ -0,0 +1,65 @@
+---
+title: 分词器测试
+summary: 分词器测试
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 分词器测试
+
+函数ts_debug允许简单测试文本搜索分词器。
+
+```
+ts_debug([ config regconfig, ] document text,
+         OUT alias text,
+         OUT description text,
+         OUT token text,
+         OUT dictionaries regdictionary[],
+         OUT dictionary regdictionary,
+         OUT lexemes text[])
+         returns setof record
+```
+
+ts_debug显示document的每个token信息，token是由解析器生成，由指定的词典进行处理。如果忽略对应参数，则使用config指定的分词器或者default_text_search_config指定的分词器。
+
+ts_debug为文本解析器标识的每个token返回一行记录。记录中的列分别是：
+
+- alias：text类型，token的别名。
+- description：text类型，token的描述。
+- token：text类型，token的文本内容。
+- dictionaries：regdictionary数组类型，是分词器为token选定的词典。
+- dictionary：regdictionary类型，用来识别token的词典。如果为空，则不做识别。
+- lexemes：text数组类型，词典识别token时生成的词素。如果为空，则不生成词素。空数组（{}）意味着token将被识别成停用词。
+
+一个简单的例子：
+
+```sql
+mogdb=# SELECT * FROM ts_debug('english','a fat  cat sat on a mat - it ate a fat rats');
+   alias   |   description   | token |  dictionaries  |  dictionary  | lexemes
+-----------+-----------------+-------+----------------+--------------+---------
+ asciiword | Word, all ASCII | a     | {english_stem} | english_stem | {}
+ blank     | Space symbols   |       | {}             |              |
+ asciiword | Word, all ASCII | fat   | {english_stem} | english_stem | {fat}
+ blank     | Space symbols   |       | {}             |              |
+ asciiword | Word, all ASCII | cat   | {english_stem} | english_stem | {cat}
+ blank     | Space symbols   |       | {}             |              |
+ asciiword | Word, all ASCII | sat   | {english_stem} | english_stem | {sat}
+ blank     | Space symbols   |       | {}             |              |
+ asciiword | Word, all ASCII | on    | {english_stem} | english_stem | {}
+ blank     | Space symbols   |       | {}             |              |
+ asciiword | Word, all ASCII | a     | {english_stem} | english_stem | {}
+ blank     | Space symbols   |       | {}             |              |
+ asciiword | Word, all ASCII | mat   | {english_stem} | english_stem | {mat}
+ blank     | Space symbols   |       | {}             |              |
+ blank     | Space symbols   | -     | {}             |              |
+ asciiword | Word, all ASCII | it    | {english_stem} | english_stem | {}
+ blank     | Space symbols   |       | {}             |              |
+ asciiword | Word, all ASCII | ate   | {english_stem} | english_stem | {ate}
+ blank     | Space symbols   |       | {}             |              |
+ asciiword | Word, all ASCII | a     | {english_stem} | english_stem | {}
+ blank     | Space symbols   |       | {}             |              |
+ asciiword | Word, all ASCII | fat   | {english_stem} | english_stem | {fat}
+ blank     | Space symbols   |       | {}             |              |
+ asciiword | Word, all ASCII | rats  | {english_stem} | english_stem | {rat}
+(24 rows)
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/8-testing-and-debugging-text-search/2-testing-a-parser.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/8-testing-and-debugging-text-search/2-testing-a-parser.md
new file mode 100644
index 0000000000000000000000000000000000000000..86965f36e010cdab65087aa216516df477826189
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/8-testing-and-debugging-text-search/2-testing-a-parser.md
@@ -0,0 +1,74 @@
+---
+title: 解析器测试
+summary: 解析器测试
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 解析器测试
+
+函数ts_parse可以直接测试文本搜索解析器。
+
+```sql
+ts_parse(parser_name text, document text,
+         OUT tokid integer, OUT token text) returns setof record
+```
+
+ts_parse解析指定的document并返回一系列的记录，一条记录代表一个解析生成的token。每条记录包括标识token类型的tokid及token文本。例如：
+
+```sql
+mogdb=# SELECT * FROM ts_parse('default', '123 - a number');
+ tokid | token
+-------+--------
+    22 | 123
+    12 |
+    12 | -
+     1 | a
+    12 |
+     1 | number
+(6 rows)
+```
+
+函数ts_token_type返回指定解析器的token类型及其描述信息。
+
+```sql
+ts_token_type(parser_name text, OUT tokid integer,
+              OUT alias text, OUT description text) returns setof record
+```
+
+ts_token_type返回一个表，这个表描述了指定解析器可以识别的每种token类型。对于每个token类型，表中给出了整数类型的
+
+- tokid 用于解析器标记对应的token类型
+- alias 命名分词器命令中的token类型及简单描述
+
+比如:
+
+```sql
+mogdb=# SELECT * FROM ts_token_type('default');
+ tokid |      alias      |               description
+-------+-----------------+------------------------------------------
+     1 | asciiword       | Word, all ASCII
+     2 | word            | Word, all letters
+     3 | numword         | Word, letters and digits
+     4 | email           | Email address
+     5 | url             | URL
+     6 | host            | Host
+     7 | sfloat          | Scientific notation
+     8 | version         | Version number
+     9 | hword_numpart   | Hyphenated word part, letters and digits
+    10 | hword_part      | Hyphenated word part, all letters
+    11 | hword_asciipart | Hyphenated word part, all ASCII
+    12 | blank           | Space symbols
+    13 | tag             | XML tag
+    14 | protocol        | Protocol head
+    15 | numhword        | Hyphenated word, letters and digits
+    16 | asciihword      | Hyphenated word, all ASCII
+    17 | hword           | Hyphenated word, all letters
+    18 | url_path        | URL path
+    19 | file            | File or path name
+    20 | float           | Decimal notation
+    21 | int             | Signed integer
+    22 | uint            | Unsigned integer
+    23 | entity          | XML entity
+(23 rows)
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/8-testing-and-debugging-text-search/3-testing-a-dictionary.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/8-testing-and-debugging-text-search/3-testing-a-dictionary.md
new file mode 100644
index 0000000000000000000000000000000000000000..8e6d7d0f77574ba18cc3d518a74250e10532f3e8
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/8-testing-and-debugging-text-search/3-testing-a-dictionary.md
@@ -0,0 +1,29 @@
+---
+title: 词典测试
+summary: 词典测试
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 词典测试
+
+函数ts_lexize用于进行词典测试。
+
+ts_lexize(dict regdictionary, token text) returns text[]如果输入的token可以被词典识别，那么ts_lexize返回词素的数组；如果token可以被词典识别到它是一个停用词，则返回空数组；如果是一个不可识别的词则返回NULL。
+
+比如：
+
+```sql
+mogdb=# SELECT ts_lexize('english_stem', 'stars');
+ ts_lexize
+-----------
+ {star}
+
+mogdb=# SELECT ts_lexize('english_stem', 'a');
+ ts_lexize
+-----------
+ {}
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+> ts_lexize函数支持单一token，不支持文本。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/9-limitations.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/9-limitations.md
new file mode 100644
index 0000000000000000000000000000000000000000..1b4528349bf366cc0fa5ddc8eaa0f4fbab20afc1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/6-full-text-search/9-limitations.md
@@ -0,0 +1,16 @@
+---
+title: 限制约束
+summary: 限制约束
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 限制约束
+
+MogDB的全文检索功能当前限制约束是：
+
+- 每个分词长度必须小于2K字节。
+- tsvector结构（分词+位置）的长度必须小于1兆字节。
+- tsvector的位置值必须大于0，且小于等于16,383。
+- 每个分词在文档中位置数必须小于256，若超过将舍弃后面的位置信息。
+- tsquery中的关键字及对应运算符最大支持到32768。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/7-system-operation.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/7-system-operation.md
new file mode 100644
index 0000000000000000000000000000000000000000..0366dd6ff2ca3e286d8e63327a9191b466035dd7
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/7-system-operation.md
@@ -0,0 +1,38 @@
+---
+title: 系统操作
+summary: 系统操作
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 系统操作
+
+MogDB通过SQL语句执行不同的系统操作，比如：设置变量，显示执行计划和垃圾收集等操作。
+
+## 设置变量
+
+设置会话或事务中需要使用的各种参数，请参考[SET](127-SET)。
+
+## 显示执行计划
+
+显示MogDB为SQL语句规划的执行计划，请参考[EXPLAIN](105-EXPLAIN)。
+
+## 事务日志检查点
+
+预写式日志（WAL）缺省时在事务日志中每隔一段时间放置一个检查点。CHECKPOINT强制立即进行检查，而不是等到下一次调度时的检查点。请参考[CHECKPOINT](35-CHECKPOINT)。
+
+## 垃圾收集
+
+进行垃圾收集以及可选择的对数据库进行分析。请参考[VACUUM](137-VACUUM)。
+
+## 收集统计信息
+
+收集与数据库中表内容相关的统计信息。请参考[ANALYZE | ANALYSE](32-ANALYZE-ANALYSE)。
+
+## 设置当前事务的约束检查模式
+
+设置当前事务里的约束检查的特性。请参考[SET CONSTRAINTS](128-SET-CONSTRAINTS)。
+
+## 关闭当前数据库节点
+
+关闭当前数据库节点。请参考[SHUTDOWN](133-SHUTDOWN)。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/8-controlling-transactions.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/8-controlling-transactions.md
new file mode 100644
index 0000000000000000000000000000000000000000..80e31f3fff54c87f9d1cee40fb7f94ca3c3bdaf7
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/8-controlling-transactions.md
@@ -0,0 +1,29 @@
+---
+title: 事务控制
+summary: 事务控制
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# 事务控制
+
+事务是用户定义的一个数据库操作序列，这些操作要么全做要么全不做，是一个不可分割的工作单位。
+
+## 启动事务
+
+MogDB通过START TRANSACTION和BEGIN语法启动事务，请参考[START TRANSACTION](134-START-TRANSACTION)和[BEGIN](33-BEGIN)。
+
+## 设置事务
+
+MogDB通过SET TRANSACTION或者SET LOCAL TRANSACTION语法设置事务，请参考[SET TRANSACTION](131-SET-TRANSACTION)。
+
+## 提交事务
+
+MogDB通过COMMIT或者END可完成提交事务的功能，即提交事务的所有操作，请参考[COMMIT | END](39-COMMIT-END)。
+
+## 回滚事务
+
+回滚是在事务运行的过程中发生了某种故障，事务不能继续执行，系统将事务中对数据库的所有已完成的操作全部撤销。请参考[ROLLBACK](121-ROLLBACK)。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+> 数据库中收到的一次执行请求（不在事务块中），如果含有多条语句，将会被打包成一个事务，如果其中有一个语句失败，那么整个请求都将会被回滚。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/9-ddl-syntax-overview.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/9-ddl-syntax-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..6a25f1f54f6a95a002830dcecfc82aa941380e89
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-reference/9-ddl-syntax-overview.md
@@ -0,0 +1,228 @@
+---
+title: DDL语法一览表
+summary: DDL语法一览表
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# DDL语法一览表
+
+DDL（Data Definition Language数据定义语言），用于定义或修改数据库中的对象。如：表、索引、视图等。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> MogDB不支持数据库主节点不完整时进行DDL操作。例如：MogDB中有1个数据库主节点故障时执行新建数据库、表等操作都会失败。
+
+## 定义客户端加密主密钥
+
+客户端加密主密钥主要用于密态数据库特性，用来加密列加密密钥(cek)。客户端加密主密钥定义主要包括创建客户端加密主密钥以及删除客户端加密主密钥。所涉及的SQL语句，请参考表1。
+
+**表 1** 客户端加密主密钥定义相关SQL
+
+| 功能                 | 相关SQL                                                 |
+| :------------------- | :------------------------------------------------------ |
+| 创建客户端加密主密钥 | [CREATE CLIENT MASTER KEY](42-CREATE-CLIENT-MASTER-KEY) |
+| 删除客户端加密主密钥 | [DROP CLIENT MASTER KEY](76-DROP-CLIENT-MASTER-KEY)     |
+
+## 定义列加密密钥
+
+列加密密钥主要用于密态数据库特性中，用来加密数据。列加密密钥定义主要包括创建列加密密钥以及删除列加密密钥。所涉及的SQL语句，请参考表2。
+
+**表 2** 列加密密钥定义相关SQL
+
+| 功能           | 相关SQL                                                      |
+| :------------- | :----------------------------------------------------------- |
+| 创建列加密密钥 | [CREATE COLUMN ENCRYPTION KEY](43-CREATE-COLUMN-ENCRYPTION-KEY) |
+| 删列加密密钥   | [DROP COLUMN ENCRYPTION KEY](77-DROP-COLUMN-ENCRYPTION-KEY)  |
+
+## 定义数据库
+
+数据库是组织、存储和管理数据的仓库，而数据库定义主要包括：创建数据库、修改数据库属性以及删除数据库。所涉及的SQL语句，请参考表3。
+
+**表 3** 数据库定义相关SQL
+
+| 功能           | 相关SQL                               |
+| :------------- | :------------------------------------ |
+| 创建数据库     | [CREATE DATABASE](44-CREATE-DATABASE) |
+| 修改数据库属性 | [ALTER DATABASE](2-ALTER-DATABASE)    |
+| 删除数据库     | [DROP DATABASE](78-DROP-DATABASE)     |
+
+## 定义模式
+
+模式是一组数据库对象的集合，主要用于控制对数据库对象的访问。所涉及的SQL语句，请参考表4。
+
+**表 4** 模式定义相关SQL
+
+| 功能         | 相关SQL                           |
+| :----------- | :-------------------------------- |
+| 创建模式     | [CREATE SCHEMA](56-CREATE-SCHEMA) |
+| 修改模式属性 | [ALTER SCHEMA](15-ALTER-SCHEMA)   |
+| 删除模式     | [DROP SCHEMA](91-DROP-SCHEMA)     |
+
+## 定义表空间
+
+表空间用于管理数据对象，与磁盘上的一个目录对应。所涉及的SQL语句，请参考表5。
+
+**表 5** 表空间定义相关SQL
+
+| 功能           | 相关SQL                                   |
+| :------------- | :---------------------------------------- |
+| 创建表空间     | [CREATE TABLESPACE](63-CREATE-TABLESPACE) |
+| 修改表空间属性 | [ALTER TABLESPACE](24-ALTER-TABLESPACE)   |
+| 删除表空间     | [DROP TABLESPACE](96-DROP-TABLESPACE)     |
+
+## 定义表
+
+表是数据库中的一种特殊数据结构，用于存储数据对象以及对象之间的关系。所涉及的SQL语句，请参考表6。
+
+**表 6** 表定义相关SQL
+
+| 功能       | 相关SQL                         |
+| :--------- | :------------------------------ |
+| 创建表     | [CREATE TABLE](60-CREATE-TABLE) |
+| 修改表属性 | [ALTER TABLE](22-ALTER-TABLE)   |
+| 删除表     | [DROP TABLE](95-DROP-TABLE)     |
+
+## 定义分区表
+
+分区表是一种逻辑表，数据是由普通表存储的，主要用于提升查询性能。所涉及的SQL语句，请参考表7。
+
+**表 7** 分区表定义相关SQL
+
+| 功能           | 相关SQL                                             |
+| :------------- | :-------------------------------------------------- |
+| 创建分区表     | [CREATE TABLE PARTITION](62-CREATE-TABLE-PARTITION) |
+| 创建分区       | [ALTER TABLE PARTITION](23-ALTER-TABLE-PARTITION)   |
+| 修改分区表属性 | [ALTER TABLE PARTITION](23-ALTER-TABLE-PARTITION)   |
+| 删除分区       | [ALTER TABLE PARTITION](23-ALTER-TABLE-PARTITION)   |
+| 删除分区表     | [DROP TABLE](95-DROP-TABLE)                         |
+
+## 定义索引
+
+索引是对数据库表中一列或多列的值进行排序的一种结构，使用索引可快速访问数据库表中的特定信息。所涉及的SQL语句，请参考表8。
+
+**表 8** 索引定义相关SQL
+
+| 功能         | 相关SQL                         |
+| :----------- | :------------------------------ |
+| 创建索引     | [CREATE INDEX](50-CREATE-INDEX) |
+| 修改索引属性 | [ALTER INDEX](9-ALTER-INDEX)    |
+| 删除索引     | [DROP INDEX](84-DROP-INDEX)     |
+| 重建索引     | [REINDEX](117-REINDEX)          |
+
+## 定义存储过程
+
+存储过程是一组为了完成特定功能的SQL语句集，经编译后存储在数据库中，用户通过指定存储过程的名称并给出参数（如果该存储过程带有参数）来执行它。所涉及的SQL语句，请参考表9。
+
+**表 9** 存储过程定义相关SQL
+
+| 功能         | 相关SQL                                 |
+| :----------- | :-------------------------------------- |
+| 创建存储过程 | [CREATE PROCEDURE](53-CREATE-PROCEDURE) |
+| 删除存储过程 | [DROP PROCEDURE](88-DROP-PROCEDURE)     |
+
+## 定义函数
+
+在MogDB中，它和存储过程类似，也是一组SQL语句集，使用上没有差别。所涉及的SQL语句，请参考表10。
+
+**表 10** 函数定义相关SQL
+
+| 功能         | 相关SQL                               |
+| :----------- | :------------------------------------ |
+| 创建函数     | [CREATE FUNCTION](48-CREATE-FUNCTION) |
+| 修改函数属性 | [ALTER FUNCTION](7-ALTER-FUNCTION)    |
+| 删除函数     | [DROP FUNCTION](82-DROP-FUNCTION)     |
+
+## 定义包
+
+包是模块化的思想，由包头（package specification）和包体(package body)组成，用来分类管理存储过程和函数，类似于Java、C++等语言中的类。
+
+**表 11** 包定义相关SQL
+
+| 功能   | 相关SQL                               |
+| :----- | :------------------------------------ |
+| 创建包 | [CREATE PACKAGE](51.2-CREATE-PACKAGE) |
+| 删除包 | [DROP PACKAGE](86.3-DROP-PACKAGE)     |
+
+## 定义视图
+
+视图是从一个或几个基本表中导出的虚表，可用于控制用户对数据访问，请参考表12。
+
+**表 12** 视图定义相关SQL
+
+| 功能     | 相关SQL                       |
+| :------- | :---------------------------- |
+| 创建视图 | [CREATE VIEW](70-CREATE-VIEW) |
+| 删除视图 | [DROP VIEW](103-DROP-VIEW)    |
+
+## 定义游标
+
+为了处理SQL语句，存储过程进程分配一段内存区域来保存上下文联系。游标是指向上下文区域的句柄或指针。借助游标，存储过程可以控制上下文区域的变化，请参考表13。
+
+**表 13** 游标定义相关SQL
+
+| 功能             | 相关SQL             |
+| :--------------- | :------------------ |
+| 创建游标         | [CURSOR](71-CURSOR) |
+| 移动游标         | [MOVE](111-MOVE)    |
+| 从游标中提取数据 | [FETCH](107-FETCH)  |
+| 关闭游标         | [CLOSE](36-CLOSE)   |
+
+## 定义聚合函数
+
+**表 14** 聚合函数定义相关SQL
+
+| 功能                 | 相关SQL                                   |
+| :------------------- | :---------------------------------------- |
+| 创建一个新的聚合函数 | [CREATE AGGREGATE](41.1-CREATE-AGGREGATE) |
+| 修改聚合函数         | [ALTER AGGREGATE](1.1-ALTER-AGGREGATE)    |
+| 删除聚合函数         | [DROP AGGREGATE](75.1-DROP-AGGREGATE)     |
+
+## 定义数据类型转换
+
+**表 15** 数据类型定义相关SQL
+
+| 功能                               | 相关SQL                         |
+| :--------------------------------- | :------------------------------ |
+| 创建一个新的用户自定义数据类型转换 | [CREATE CAST](41.3-CREATE-CAST) |
+| 删除用户自定义数据类型转换         | [DROP CAST](75.3-DROP-CAST)     |
+
+## 定义插件扩展
+
+**表 16** 插件扩展定义相关SQL
+
+| 功能                 | 相关SQL                                   |
+| :------------------- | :---------------------------------------- |
+| 创建一个新的插件扩展 | [CREATE EXTENSION](46.1-CREATE-EXTENSION) |
+| 修改插件扩展         | [ALTER EXTENSION](5.1-ALTER-EXTENSION)    |
+| 删除插件扩展         | [DROP EXTENSION](80.1-DROP-EXTENSION)     |
+
+## 定义操作符
+
+**表 17** 操作符定义相关SQL
+
+| 功能               | 相关SQL                                 |
+| :----------------- | :-------------------------------------- |
+| 创建一个新的操作符 | [CREATE OPERATOR](51.1-CREATE-OPERATOR) |
+| 修改操作符         | [ALTER OPERATOR](11.1-ALTER-OPERATOR)   |
+| 删除操作符         | [DROP OPERATOR](85.1-DROP-OPERATOR)     |
+
+## 定义过程语言
+
+**表 18** 过程语言定义相关SQL
+
+| 功能                 | 相关SQL                                 |
+| :------------------- | :-------------------------------------- |
+| 创建一个新的过程语言 | [CREATE LANGUAGE](50.1-CREATE-LANGUAGE) |
+| 修改过程语言         | [ALTER LANGUAGE](9.1-ALTER-LANGUAGE)    |
+| 删除过程语言         | [DROP LANGUAGE](84.1-DROP-LANGUAGE)     |
+
+## 定义数据类型
+
+**表 19** 数据类型定义相关SQL
+
+| 功能                 | 相关SQL                       |
+| :------------------- | :---------------------------- |
+| 创建一个新的数据类型 | [CREATE TYPE](67-CREATE-TYPE) |
+| 修改数据类型         | [ALTER TYPE](28-ALTER-TYPE)   |
+| 删除数据类型         | [DROP TYPE](100-DROP-TYPE)    |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/1-ABORT.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/1-ABORT.md
new file mode 100644
index 0000000000000000000000000000000000000000..bfb1bdfcfb4343b43c594d52d083b6d5a1a6d1c0
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/1-ABORT.md
@@ -0,0 +1,76 @@
+---
+title: ABORT
+summary: ABORT
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ABORT
+
+## 功能描述
+
+回滚当前事务并且撤销所有当前事务中所做的更改。
+
+作用等同于ROLLBACK，早期SQL有用ABORT，现在推荐使用ROLLBACK。
+
+## 注意事项
+
+在事务外部执行ABORT语句不会影响事务的执行，但是会抛出一个NOTICE信息。
+
+## 语法格式
+
+```ebnf+diagram
+Abort ::= ABORT [ WORK | TRANSACTION ];
+```
+
+## 参数说明
+
+**WORK | TRANSACTION**
+
+可选关键字，除了增加可读性没有其他任何作用。
+
+## 示例
+
+```sql
+--创建表customer_demographics_t1。
+mogdb=# CREATE TABLE customer_demographics_t1
+(
+    CD_DEMO_SK                INTEGER               NOT NULL,
+    CD_GENDER                 CHAR(1)                       ,
+    CD_MARITAL_STATUS         CHAR(1)                       ,
+    CD_EDUCATION_STATUS       CHAR(20)                      ,
+    CD_PURCHASE_ESTIMATE      INTEGER                       ,
+    CD_CREDIT_RATING          CHAR(10)                      ,
+    CD_DEP_COUNT              INTEGER                       ,
+    CD_DEP_EMPLOYED_COUNT     INTEGER                       ,
+    CD_DEP_COLLEGE_COUNT      INTEGER
+)
+WITH (ORIENTATION = COLUMN,COMPRESSION=MIDDLE)
+;
+
+--插入记录。
+mogdb=# INSERT INTO customer_demographics_t1 VALUES(1920801,'M', 'U', 'DOCTOR DEGREE', 200, 'GOOD', 1, 0,0);
+
+--开启事务。
+mogdb=# START TRANSACTION;
+
+--更新字段值。
+mogdb=# UPDATE customer_demographics_t1 SET cd_education_status= 'Unknown';
+
+--终止事务，上面所执行的更新会被撤销掉。
+mogdb=# ABORT;
+
+--查询数据。
+mogdb=# SELECT * FROM customer_demographics_t1 WHERE cd_demo_sk = 1920801;
+cd_demo_sk | cd_gender | cd_marital_status | cd_education_status  | cd_purchase_estimate | cd_credit_rating | cd_dep_count | cd_dep_employed_count | cd_dep_college_count
+------------+-----------+-------------------+----------------------+----------------------+------------------+--------------+-----------------------+----------------------
+    1920801 | M         | U                 | DOCTOR DEGREE        |                  200 | GOOD             |            1 |                     0 |                    0
+(1 row)
+
+--删除表。
+mogdb=# DROP TABLE customer_demographics_t1;
+```
+
+## 相关链接
+
+[SET TRANSACTION](131-SET-TRANSACTION)，[COMMIT | END](39-COMMIT-END)，[ROLLBACK](121-ROLLBACK)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/1.1-ALTER-AGGREGATE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/1.1-ALTER-AGGREGATE.md
new file mode 100644
index 0000000000000000000000000000000000000000..b3244705f5c8b9290b290c26897942c08c3bedba
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/1.1-ALTER-AGGREGATE.md
@@ -0,0 +1,76 @@
+---
+title: ALTER AGGREGATE
+summary: ALTER AGGREGATE
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# ALTER AGGREGATE
+
+## 功能描述
+
+修改一个聚合函数的定义。
+
+## 注意事项
+
+要使用 ALTER AGGREGATE ，你必须是该聚合函数的所有者。 要改变一个聚合函数的模式，你必须在新模式上有 CREATE 权限。 要改变所有者，你必须是新所有角色的一个直接或间接成员，并且该角色必须在聚合函数的模式上有 CREATE 权限。（这些限制强制了修改该所有者不会做任何通过删除和重建聚合函数不能做的事情。不过，超级用户可以用任何方法任意更改聚合函数的所属关系）。
+
+## 语法格式
+
+```ebnf+diagram
+AlterAggregate ::= ALTER AGGREGATE name ( argtype [ , ... ] ) RENAME TO new_name;
+```
+
+```ebnf+diagram
+AlterAggregate ::= ALTER AGGREGATE name ( argtype [ , ... ] ) OWNER TO new_owner;
+```
+
+```ebnf+diagram
+AlterAggregate ::= ALTER AGGREGATE name ( argtype [ , ... ] ) SET SCHEMA new_schema;
+```
+
+## 参数说明
+
+- **name**
+
+  现有的聚合函数的名称(可以有模式修饰)。
+
+- **argtype**
+
+  聚合函数操作的输入数据类型。要引用一个零参数聚合函数，可以写入*代替输入数据类型列表。
+
+- **new_name**
+
+  聚合函数的新名字。
+
+- **new_owner**
+
+  聚合函数的新所有者。
+
+- **new_schema**
+
+  聚合函数的新模式。
+
+## 示例
+
+把一个接受integer 类型参数的聚合函数myavg重命名为 my_average ：
+
+```sql
+ALTER AGGREGATE myavg(integer) RENAME TO my_average;
+```
+
+把一个接受integer 类型参数的聚合函数myavg的所有者改为joe ：
+
+```sql
+ALTER AGGREGATE myavg(integer) OWNER TO joe;
+```
+
+把一个接受integer 类型参数的聚合函数myavg移动到模式myschema里：
+
+```sql
+ALTER AGGREGATE myavg(integer) SET SCHEMA myschema;
+```
+
+## 兼容性
+
+SQL标准里没有ALTER AGGREGATE语句。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/1.2-ALTER-AUDIT-POLICY.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/1.2-ALTER-AUDIT-POLICY.md
new file mode 100644
index 0000000000000000000000000000000000000000..08962badd06fbc1dcbafb0c52280e8b0a191064e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/1.2-ALTER-AUDIT-POLICY.md
@@ -0,0 +1,98 @@
+---
+title: ALTER AUDIT POLICY
+summary: ALTER AUDIT POLICY
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# ALTER AUDIT POLICY
+
+## 功能描述
+
+修改统一审计策略。
+
+## 注意事项
+
+- 只有poladmin，sysadmin或初始用户用户才能进行此操作。
+- 需要打开enable_security_policy，开关统一审计策略才可以生效。
+
+## 语法格式
+
+```ebnf+diagram
+AlterAuditPolicy ::= ALTER AUDIT POLICY [ IF EXISTS ] policy_name { ADD | REMOVE } { [ privilege_audit_clause ] [ access_audit_clause ] };
+```
+
+```ebnf+diagram
+AlterAuditPolicy ::= ALTER AUDIT POLICY [ IF EXISTS ] policy_name MODIFY ( filter_group_clause );
+ALTER AUDIT POLICY [ IF EXISTS ] policy_name DROP FILTER;
+```
+
+```ebnf+diagram
+AlterAuditPolicy ::= ALTER AUDIT POLICY [ IF EXISTS ] policy_name COMMENTS policy_comments;
+```
+
+```ebnf+diagram
+AlterAuditPolicy ::= ALTER AUDIT POLICY [ IF EXISTS ] policy_name { ENABLE | DISABLE };
+```
+
+- privilege_audit_clause：
+
+  ```ebnf+diagram
+  privilege_audit_clause ::= PRIVILEGES { DDL | ALL };
+  ```
+
+- access_audit_clause：
+
+  ```ebnf+diagram
+  access_audit_clause ::= ACCESS { DML | ALL };
+  ```
+
+- filter_group_clause：
+
+  ```ebnf+diagram
+  filter_group_clause ::= FILTER ON {(FILTER_TYPE (filter_value [, ...])) [, ...]};
+  ```
+
+## 参数说明
+
+- **policy_name**
+
+  审计策略名称，需要唯一，不可重复。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- **DDL**
+
+  指的是针对数据库执行如下操作时进行审计，目前支持：CREATE、ALTER、DROP、ANALYZE、COMMENT、GRANT、REVOKE、SET、SHOW、LOGIN_ANY、LOGIN_FAILURE、LOGIN_SUCCESS、LOGOUT。
+
+- **ALL**
+
+  指的是上述DDL支持的所有对数据库的操作。
+
+- **DML**
+
+  指的是针对数据库执行如下操作时进行审计，目前支持：SELECT、COPY、DEALLOCATE、DELETE、EXECUTE、INSERT、PREPARE、REINDEX、TRUNCATE、UPDATE。
+
+- **FILTER_TYPE**
+
+  指定审计策略的过滤信息，过滤类型包括：IP、ROLES、APP。
+
+- **filter_value**
+
+  指具体过滤信息内容。
+
+- **policy_comments**
+
+  用于记录策略相关的描述信息。
+
+- **ENABLE|DISABLE**
+
+  可以打开或关闭统一审计策略。若不指定ENABLE|DISABLE，语句默认为ENABLE。
+
+## 示例
+
+请参考[CREATE AUDIT POLICY](41.2-CREATE-AUDIT-POLICY)的示例。
+
+## 相关链接
+
+[CREATE AUDIT POLICY](41.2-CREATE-AUDIT-POLICY)，[DROP AUDIT POLICY](75.2-DROP-AUDIT-POLICY)。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/10-ALTER-LARGE-OBJECT.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/10-ALTER-LARGE-OBJECT.md
new file mode 100644
index 0000000000000000000000000000000000000000..b3d7e031d36c077220771e131065fd53f90cb775
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/10-ALTER-LARGE-OBJECT.md
@@ -0,0 +1,41 @@
+---
+title: ALTER LARGE OBJECT
+summary: ALTER LARGE OBJECT
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER LARGE OBJECT
+
+## 功能描述
+
+ALTER LARGE OBJECT用于更改一个large object的定义。它的唯一的功能是分配一个新的所有者。
+
+## 注意事项
+
+使用ALTER LARGE OBJECT必须是系统管理员或者是其所有者。
+
+## 语法格式
+
+```ebnf+diagram
+AlterLargeObject ::= ALTER LARGE OBJECT large_object_oid
+    OWNER TO new_owner;
+```
+
+## 参数说明
+
+- **large_object_oid**
+
+  要被变large object的OID 。
+
+  取值范围: 已存在的大对象名。
+
+- **OWNER TO new_owner**
+
+  large object新的所有者。
+
+  取值范围: 已存在的用户名/角色名。
+
+## 示例
+
+无。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/10.1-ALTER-MASKING-POLICY.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/10.1-ALTER-MASKING-POLICY.md
new file mode 100644
index 0000000000000000000000000000000000000000..366bfe9e2d7ddbffc89d956c02cd15cd9d99d8f5
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/10.1-ALTER-MASKING-POLICY.md
@@ -0,0 +1,140 @@
+---
+title: ALTER MASKING POLICY
+summary: ALTER MASKING POLICY
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# ALTER MASKING POLICY
+
+## 功能描述
+
+修改脱敏策略。
+
+## 注意事项
+
+- 只有poladmin，sysadmin或初始用户才能执行此操作。
+- 需要打开enable_security_policy开关，脱敏策略才可以生效。
+
+## 语法格式
+
+- 修改策略描述：
+
+  ```ebnf+diagram
+  AlterMaskingPolicy ::= ALTER MASKING POLICY policy_name COMMENTS policy_comments;
+  ```
+
+- 修改脱敏方式：
+
+  ```ebnf+diagram
+  AlterMaskingPolicy ::= ALTER MASKING POLICY policy_name [ADD | REMOVE | MODIFY] masking_actions[, ...]*;
+  ```
+
+  其中masking_action:
+
+  ```ebnf+diagram
+  masking_action ::= masking_function ON LABEL(label_name[, ...]*)
+  ```
+
+- 修改脱敏策略生效场景：
+
+  ```ebnf+diagram
+  AlterMaskingPolicy ::= ALTER MASKING POLICY policy_name MODIFY(FILTER ON FILTER_TYPE(filter_value[, ...]*)[, ...]*);
+  ```
+
+- 移除脱敏策略生效场景，使策略对所用场景生效：
+
+  ```ebnf+diagram
+  AlterMaskingPolicy ::= ALTER MASKING POLICY policy_name DROP FILTER;
+  ```
+
+- 修改脱敏策略开启/关闭：
+
+  ```ebnf+diagram
+  AlterMaskingPolicy ::= ALTER MASKING POLICY policy_name [ENABLE | DISABLE];
+  ```
+
+## 参数说明
+
+- **policy_name**
+
+  脱敏策略名称，需要唯一，不可重复。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- **policy_comments**
+
+  需要为脱敏策略添加或修改的描述信息。
+
+- **masking_function**
+
+  指的是预置的八种脱敏方式或者用户自定义的函数，支持模式。
+
+  maskall不是预置函数，硬编码在代码中，不支持\\df展示。
+
+  预置时脱敏方式如下：
+
+  ```sql
+  maskall | randommasking | creditcardmasking | basicemailmasking | fullemailmasking | shufflemasking | alldigitsmasking | regexpmasking
+  ```
+
+- **label_name**
+
+  资源标签名称。
+
+- **FILTER_TYPE**
+
+  指定脱敏策略的过滤信息，过滤类型包括：IP、ROLES、APP。
+
+- **filter_value**
+
+  指具体过滤信息内容，例如具体的IP，具体的APP名称，具体的用户名。
+
+- **ENABLE|DISABLE**
+
+  可以打开或关闭脱敏策略。若不指定ENABLE|DISABLE，语句默认为ENABLE。
+
+## 示例
+
+```sql
+--创建dev_mask和bob_mask用户。
+mogdb=# CREATE USER dev_mask PASSWORD 'dev@1234';
+mogdb=# CREATE USER bob_mask PASSWORD 'bob@1234';
+
+--创建一个表tb_for_masking
+mogdb=# CREATE TABLE tb_for_masking(col1 text, col2 text, col3 text);
+
+--创建资源标签标记敏感列col1
+mogdb=# CREATE RESOURCE LABEL mask_lb1 ADD COLUMN(tb_for_masking.col1);
+
+--创建资源标签标记敏感列col2
+mogdb=# CREATE RESOURCE LABEL mask_lb2 ADD COLUMN(tb_for_masking.col2);
+
+--对访问敏感列col1的操作创建脱敏策略
+mogdb=# CREATE MASKING POLICY maskpol1 maskall ON LABEL(mask_lb1);
+
+--为脱敏策略maskpol1添加描述
+mogdb=# ALTER MASKING POLICY maskpol1 COMMENTS 'masking policy for tb_for_masking.col1';
+
+--修改脱敏策略maskpol1，新增一项脱敏方式
+mogdb=# ALTER MASKING POLICY maskpol1 ADD randommasking ON LABEL(mask_lb2);
+
+--修改脱敏策略maskpol1，移除一项脱敏方式
+mogdb=# ALTER MASKING POLICY maskpol1 REMOVE randommasking ON LABEL(mask_lb2);
+
+--修改脱敏策略maskpol1，修改一项脱敏方式
+mogdb=# ALTER MASKING POLICY maskpol1 MODIFY randommasking ON LABEL(mask_lb1);
+
+--修改脱敏策略maskpol1使之仅对用户dev_mask和bob_mask,客户端工具为psql和gsql，IP地址为'10.20.30.40', '127.0.0.0/24'场景生效。
+mogdb=# ALTER MASKING POLICY maskpol1 MODIFY (FILTER ON ROLES(dev_mask, bob_mask), APP(psql, gsql), IP('10.20.30.40', '127.0.0.0/24'));
+
+--修改脱敏策略maskpol1，使之对所有用户场景生效
+mogdb=# ALTER MASKING POLICY maskpol1 DROP FILTER;
+
+--禁用脱敏策略maskpol1
+mogdb=# ALTER MASKING POLICY maskpol1 DISABLE;
+```
+
+## 相关链接
+
+[CREATE MASKING POLICY](50.2-CREATE-MASKING-POLICY)，[DROP MASKING POLICY](84.2-DROP-MASKING-POLICY)。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/100-DROP-TYPE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/100-DROP-TYPE.md
new file mode 100644
index 0000000000000000000000000000000000000000..27d1f2bb31e3fc4ddb20ca79da1e6dc91e72fe3a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/100-DROP-TYPE.md
@@ -0,0 +1,48 @@
+---
+title: DROP TYPE
+summary: DROP TYPE
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP TYPE
+
+## 功能描述
+
+删除一个用户定义的数据类型。
+
+## 注意事项
+
+只有类型的所有者或者被授予了类型DROP权限的用户有权限执行DROP TYPE命令，系统管理员默认拥有此权限。
+
+## 语法格式
+
+```ebnf+diagram
+DropType ::= DROP TYPE [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]
+```
+
+## 参数说明
+
+- **IF EXISTS**
+
+  如果指定的类型不存在，那么发出一个notice而不是抛出一个错误。
+
+- **name**
+
+  要删除的类型名(可以有模式修饰)。
+
+- **CASCADE**
+
+  级联删除依赖该类型的对象(比如字段、函数、操作符等)
+
+  **RESTRICT**
+
+  如果有依赖对象，则拒绝删除该类型（缺省行为）。
+
+## 示例
+
+请参考CREATE TYPE的示例。
+
+## 相关链接
+
+[CREATE TYPE](67-CREATE-TYPE)，[ALTER TYPE](28-ALTER-TYPE)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/101-DROP-USER.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/101-DROP-USER.md
new file mode 100644
index 0000000000000000000000000000000000000000..77e042ea23d82277923c1ad3c463f999fb60b06c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/101-DROP-USER.md
@@ -0,0 +1,59 @@
+---
+title: DROP USER
+summary: DROP USER
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP USER
+
+## 功能描述
+
+删除用户，同时会删除同名的schema。
+
+## 注意事项
+
+- 须使用CASCADE级联删除依赖用户的对象（除数据库外）。当删除用户的级联对象时，如果级联对象处于锁定状态，则此级联对象无法被删除，直到对象被解锁或锁定级联对象的进程被杀死。
+- 在MogDB中，存在一个配置参数enable_kill_query，此参数在配置文件postgresql.conf中。此参数影响级联删除用户对象的行为：
+  - 当参数enable_kill_query为on ，且使用CASCADE模式删除用户时，会自动kill锁定用户级联对象的进程，并删除用户。
+  - 当参数enable_kill_query为off，且使用CASCADE模式删除用户时，会等待锁定级联对象的进程结束之后再删除用户。
+- 在数据库中删除用户时，如果依赖用户的对象在其他数据库中或者依赖用户的对象是其他数据库，请用户先手动删除其他数据库中的依赖对象或直接删除依赖数据库，再删除用户。即drop user不支持跨数据库进行级联删除。
+- 如果该用户被DATA SOURCE对象依赖时，无法直接级联删除该用户，需要手动删除对应的DATA SOURCE对象之后再删除该用户。
+
+## 语法格式
+
+```ebnf+diagram
+DropUser ::= DROP USER [ IF EXISTS ] user_name [, ...] [ CASCADE | RESTRICT ];
+```
+
+## 参数说明
+
+- **IF EXISTS**
+
+  如果指定的用户不存在，发出一个notice而不是抛出一个错误。
+
+- **user_name**
+
+  待删除的用户名。
+
+  取值范围: 已存在的用户名。
+
+- **CASCADE | RESTRICT**
+
+  - CASCADE：级联删除依赖用户的对象。
+
+  - RESTRICT：如果用户还有任何依赖的对象，则拒绝删除该用户（缺省行为）。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+    > 在MogDB中，存在一个配置参数enable_kill_query，此参数在配置文件postgresql.conf中。此参数影响级联删除用户对象的行为：
+    >
+    > - 当参数enable_kill_query为on ，且使用CASCADE模式删除用户时，会自动kill锁定用户级联对象的进程，并删除用户。
+    > - 当参数enable_kill_query为off，且使用CASCADE模式删除用户时，会等待锁定级联对象的进程结束之后再删除用户。
+
+## 示例
+
+请参考CREATE USER的示例。
+
+## 相关链接
+
+[ALTER USER](29-ALTER-USER)，[CREATE USER](68-CREATE-USER)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/102-DROP-USER-MAPPING.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/102-DROP-USER-MAPPING.md
new file mode 100644
index 0000000000000000000000000000000000000000..80d3d52d9b201fd53e8ae757ca8be74d293c5170
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/102-DROP-USER-MAPPING.md
@@ -0,0 +1,38 @@
+---
+title: DROP USER MAPPING
+summary: DROP USER MAPPING
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP USER MAPPING
+
+## 功能描述
+
+移除一个用于外部服务器的用户映射。
+
+## 语法格式
+
+```ebnf+diagram
+DropUserMapping ::= DROP USER MAPPING [ IF EXISTS ] FOR { user_name | USER | CURRENT_USER | PUBLIC } SERVER server_name;
+```
+
+## 参数描述
+
+- **IF EXISTS**
+
+  如果该用户映射不存在则不要抛出一个错误，而是发出一个提示。
+
+- **user_name**
+
+  该映射的用户名。
+
+  CURRENT_USER和USER匹配当前用户的名称。PUBLIC被用来匹配系统中所有现存和未来的用户名。
+
+- **server_name**
+
+  用户映射的服务器名。
+
+## 相关链接
+
+[ALTER USER MAPPING](30-ALTER-USER-MAPPING)，[CREATE USER MAPPING](69-CREATE-USER-MAPPING)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/103-DROP-VIEW.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/103-DROP-VIEW.md
new file mode 100644
index 0000000000000000000000000000000000000000..4e3401ce2f94462aa4d848b5560f24763effc3bd
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/103-DROP-VIEW.md
@@ -0,0 +1,47 @@
+---
+title: DROP VIEW
+summary: DROP VIEW
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP VIEW
+
+## 功能描述
+
+数据库中强制删除已有的视图。
+
+## 注意事项
+
+只有视图的所有者或者被授予了视图DROP权限的用户才有权限执行DROP VIEW的命令，系统管理员默认拥有此权限。
+
+## 语法格式
+
+```ebnf+diagram
+DropView ::= DROP VIEW [ IF EXISTS ] view_name [, ...] [ CASCADE | RESTRICT ];
+```
+
+## 参数说明
+
+- **IF EXISTS**
+
+  如果指定的视图不存在，则发出一个notice而不是抛出一个错误。
+
+- **view_name**
+
+  要删除的视图名称。
+
+  取值范围: 已存在的视图。
+
+- **CASCADE | RESTRICT**
+
+  - CASCADE：级联删除依赖此视图的对象（比如其他视图）。
+  - RESTRICT：如果有依赖对象存在，则拒绝删除此视图。此选项为缺省值。
+
+## 示例
+
+请参见CREATE VIEW的示例。
+
+## 相关链接
+
+[ALTER VIEW](31-ALTER-VIEW)，[CREATE VIEW](70-CREATE-VIEW)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/103.1-DROP-WEAK-PASSWORD-DICTIONARY.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/103.1-DROP-WEAK-PASSWORD-DICTIONARY.md
new file mode 100644
index 0000000000000000000000000000000000000000..540289be115dcd0ebd71fde358f07a7ba0a5ee19
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/103.1-DROP-WEAK-PASSWORD-DICTIONARY.md
@@ -0,0 +1,34 @@
+---
+title: DROP WEAK PASSWORD DICTIONARY
+summary: DROP WEAK PASSWORD DICTIONARY
+author: Zhang Cuiping
+date: 2021-11-01
+---
+
+# DROP WEAK PASSWORD DICTIONARY
+
+## 功能描述
+
+清空gs_global_config中的所有弱口令。
+
+## 注意事项
+
+只有初始用户、系统管理员和安全管理员拥有权限执行本语法。
+
+## 语法格式
+
+```ebnf+diagram
+DropWeakPasswordDictionary ::= DROP WEAK PASSWORD DICTIONARY;
+```
+
+## 参数说明
+
+无。
+
+## 示例
+
+参见CREATE WEAK PASSWORD DICTIONARY的示例。
+
+## 相关链接
+
+[CREATE WEAK PASSWORD DICTIONARY](70.1-CREATE-WEAK-PASSWORD-DICTIONARY)
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/104-EXECUTE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/104-EXECUTE.md
new file mode 100644
index 0000000000000000000000000000000000000000..a31b19c6363d4efe8733dbd6785f8d732ddcfa0b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/104-EXECUTE.md
@@ -0,0 +1,59 @@
+---
+title: EXECUTE
+summary: EXECUTE
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# EXECUTE
+
+## 功能描述
+
+执行一个前面准备好的预备语句。因为一个预备语句只在会话的生命期里存在，那么预备语句必须是在当前会话的前些时候用PREPARE语句创建的。
+
+## 注意事项
+
+如果创建预备语句的PREPARE语句声明了一些参数，那么传递给EXECUTE语句的必须是一个兼容的参数集，否则就会生成一个错误。
+
+## 语法格式
+
+```ebnf+diagram
+Execute ::= EXECUTE name [ ( parameter [, ...] ) ];
+```
+
+## 参数说明
+
+- **name**
+
+  要执行的预备语句的名称。
+
+- **parameter**
+
+  给预备语句的一个参数的具体数值。它必须是一个和生成与创建这个预备语句时指定参数的数据类型相兼容的值的表达式。
+
+## 示例
+
+```sql
+--创建表reason。
+mogdb=# CREATE TABLE tpcds.reason (
+    CD_DEMO_SK          INTEGER          NOT NULL,
+    CD_GENDER           character(16)            ,
+    CD_MARITAL_STATUS   character(100)
+)
+;
+
+--插入数据。
+mogdb=# INSERT INTO tpcds.reason VALUES(51, 'AAAAAAAADDAAAAAA', 'reason 51');
+
+--创建表reason_t1。
+mogdb=# CREATE TABLE tpcds.reason_t1 AS TABLE tpcds.reason;
+
+--为一个INSERT语句创建一个预备语句然后执行它。
+mogdb=# PREPARE insert_reason(integer,character(16),character(100)) AS INSERT INTO tpcds.reason_t1 VALUES($1,$2,$3);
+
+mogdb=# EXECUTE insert_reason(52, 'AAAAAAAADDAAAAAA', 'reason 52');
+
+--删除表reason和reason_t1。
+mogdb=# DROP TABLE tpcds.reason;
+mogdb=# DROP TABLE tpcds.reason_t1;
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/104.1-EXECUTE-DIRECT.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/104.1-EXECUTE-DIRECT.md
new file mode 100644
index 0000000000000000000000000000000000000000..f74ece64750149b4d328217943428cb8642e784d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/104.1-EXECUTE-DIRECT.md
@@ -0,0 +1,83 @@
+---
+title: EXECUTE DIRECT
+summary: EXECUTE DIRECT
+author: Zhang Cuiping
+date: 2021-11-01
+---
+
+# EXECUTE DIRECT
+
+## 功能描述
+
+在指定的节点上执行SQL语句。一般情况下，SQL语句的执行是由集群负载自动分配到合适的节点上，execute direct主要用于数据库维护和测试。
+
+## 注意事项
+
+- 当enable_nonsysadmin_execute_direct=off时，只有系统管理员和监控管理员才能执行EXECUTE DIRECT。
+- 为了各个节点上数据的一致性，SQL语句仅支持SELECT，不允许执行事务语句、DDL、DML。
+- 使用此类型语句在指定的DN执行stddev聚集计算时，返回结果集是以三元数组形式返回，如{3, 8, 30}，表示count结果为3，sum结果为8，平方和为30。使用此类型语句在指定的DN执行AVG聚集计算时，返回结果集以二元组形式返回，如{4，2}，表示sum结果为4，count结果为2。注意，当数据为列存时，调用avg函数结果未定义，请使用stddev_samp函数。
+- 当指定多个节点时，不支持agg函数，当query中包含agg函数时，会返回“EXECUTE DIRECT on multinode not support agg functions.”
+- 由于CN节点不存储用户表数据，不允许指定CN节点执行用户表上的SELECT查询。
+- 不允许执行嵌套的EXECUTE DIRECT语句，即执行的SQL语句不能同样是EXECUTE DIRECT语句，此时可直接执行最内层EXECUTE DIRECT语句代替。
+- agg函数查询结果与直接在CN上查询不一致，会返回多个信息，不支持array_avg函数。
+
+## 语法格式
+
+```ebnf+diagram
+ExecuteDirect ::= EXECUTE DIRECT ON ( nodename [, ... ] ) query ;
+EXECUTE DIRECT ON { COORDINATORS | DATANODES | ALL } query;
+```
+
+## 参数说明
+
+- nodename
+
+  节点名称。
+
+  取值范围: 已存在的节点。
+
+- query
+
+  要执行查询语句。
+
+- COORDINATORS
+
+  在所有coordinator执行查询语句。
+
+- DATANODES
+
+  在所有datanode执行查询语句。
+
+- ALL
+
+  在所有coordinator和datanode执行查询语句。
+
+## 示例
+
+```sql
+--查询当前数据库实例的节点分布状态。
+mogdb=# SELECT * FROM pgxc_node;
+ node_name   | node_type | node_port |   node_host    | node_port1 |   node_host1   | hostis_primary | nodeis_primary | nodeis_preferred |   node_id   | sctp_port | control_port | sctp_port1 | control_port1
+--------------+-----------+-----------+----------------+------------+----------------+----------------+----------------+------------------+-------------+-----------+--------------+------------+---------------
+ cn_5001      | C         |      8050 | 10.180.155.74  |       8050 | 10.180.155.74  | t              | f              | f                |  1120683504 |         0 |            0 |          0 |             0
+ cn_5003      | C         |      8050 | 10.180.157.130 |       8050 | 10.180.157.130 | t              | f              | f                |  -125853378 |         0 |            0 |          0 |             0
+ dn_6001_6002 | D         |     40050 | 10.180.155.74  |      45050 | 10.146.187.231 | t              | f              | f                |  1644780306 |     40052 |        40052 |      45052 |         45052
+ dn_6003_6004 | D         |     40050 | 10.146.187.231 |      45050 | 10.180.157.130 | t              | f              | f                |  -966646068 |     40052 |        40052 |      45052 |         45052
+ dn_6005_6006 | D         |     40050 | 10.180.157.130 |      45050 | 10.180.155.74  | t              | f              | f                |   868850011 |     40052 |        40052 |      45052 |         45052
+ cn_5002      | C         |      8050 | localhost      |       8050 | localhost      | t              | f              | f                | -1736975100 |         0 |            0 |          0 |             0
+(6 rows)
+
+--查询dn_6001_6002上tpcds.customer_address记录。
+mogdb=# EXECUTE DIRECT ON(dn_6001_6002) 'select count(*) from tpcds.customer_address';
+ count
+-------
+ 16922
+(1 row)
+
+--查询tpcds.customer_address所有记录。
+mogdb=# SELECT count(*) FROM tpcds.customer_address;
+ count
+-------
+ 50000
+(1 row)
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/105-EXPLAIN.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/105-EXPLAIN.md
new file mode 100644
index 0000000000000000000000000000000000000000..c2853700d7da09945ea555cc91711d4c3d66b094
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/105-EXPLAIN.md
@@ -0,0 +1,262 @@
+---
+title: EXPLAIN
+summary: EXPLAIN
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# EXPLAIN
+
+## 功能描述
+
+显示SQL语句的执行计划。
+
+执行计划将显示SQL语句所引用的表会采用什么样的扫描方式，如：简单的顺序扫描、索引扫描等。如果引用了多个表，执行计划还会显示用到的JOIN算法。
+
+执行计划的最关键的部分是语句的预计执行开销，这是计划生成器估算执行该语句将花费多长的时间。
+
+若指定了ANALYZE选项，则该语句会被执行，然后根据实际的运行结果显示统计数据，包括每个计划节点内时间总开销（毫秒为单位）和实际返回的总行数。这对于判断计划生成器的估计是否接近现实非常有用。
+
+## 注意事项
+
+- 在指定ANALYZE选项时，语句会被执行。如果用户想使用EXPLAIN分析INSERT，UPDATE，DELETE，CREATE TABLE AS或EXECUTE语句，而不想改动数据（执行这些语句会影响数据），请使用如下方法。
+
+  ```
+  START TRANSACTION;
+  EXPLAIN ANALYZE ...;
+  ROLLBACK;
+  ```
+
+- 由于参数DETAIL，NODES，NUM_NODES是分布式模式下的功能，在单机模式中是被禁止使用的。假如使用，会产生如下错误。
+
+  ```
+  mogdb=# create table student(id int, name char(20));
+  CREATE TABLE
+  mogdb=# explain (nodes true) insert into student values(5,'a'),(6,'b');
+  ERROR:  unrecognized EXPLAIN option "nodes"
+  mogdb=# explain (num_nodes true) insert into student values(5,'a'),(6,'b');
+  ERROR:  unrecognized EXPLAIN option "num_nodes"
+  ```
+
+## 语法格式
+
+- 显示SQL语句的执行计划，支持多种选项，对选项顺序无要求。
+
+  ```ebnf+diagram
+  Explain ::= EXPLAIN [ (  option  [, ...] )  ] statement;
+  ```
+
+  其中选项option子句的语法为。
+
+  ```ebnf+diagram
+  option ::= ANALYZE [ boolean ] |
+      ANALYSE [ boolean ] |
+      VERBOSE [ boolean ] |
+      COSTS [ boolean ] |
+      CPU [ boolean ] |
+      DETAIL [ boolean ] |
+      NODES [ boolean ] |
+      NUM_NODES [ boolean ] |
+      BUFFERS [ boolean ] |
+      TIMING [ boolean ] |
+      PLAN [ boolean ] |
+      FORMAT { TEXT | XML | JSON | YAML }
+  ```
+
+- 显示SQL语句的执行计划，且要按顺序给出选项。
+
+  ```ebnf+diagram
+  Explain ::= EXPLAIN  { [  { ANALYZE  | ANALYSE  }  ] [ VERBOSE  ]  | PERFORMANCE  } statement;
+  ```
+
+## 参数说明
+
+- **statement**
+
+  指定要分析的SQL语句。
+
+- **ANALYZE boolean | ANALYSE boolean**
+
+  显示实际运行时间和其他统计数据。
+
+  取值范围:
+
+  - TRUE（缺省值）：显示实际运行时间和其他统计数据。
+  - FALSE：不显示。
+
+- **VERBOSE boolean**
+
+  显示有关计划的额外信息。
+
+  取值范围:
+
+  - TRUE（缺省值）：显示额外信息。
+  - FALSE：不显示。
+
+- **COSTS boolean**
+
+  包括每个规划节点的估计总成本，以及估计的行数和每行的宽度。
+
+  取值范围:
+
+  - TRUE（缺省值）：显示估计总成本和宽度。
+  - FALSE：不显示。
+
+- **CPU boolean**
+
+  打印CPU的使用情况的信息。
+
+  取值范围:
+
+  - TRUE（缺省值）：显示CPU的使用情况。
+  - FALSE：不显示。
+
+- **DETAIL boolean**（不可用）
+
+  打印数据库节点上的信息。
+
+  取值范围:
+
+  - TRUE（缺省值）：打印数据库节点的信息。
+  - FALSE：不打印。
+
+- **NODES boolean**（不可用）
+
+  打印query执行的节点信息。
+
+  取值范围:
+
+  - TRUE（缺省值）：打印执行的节点的信息。
+  - FALSE：不打印。
+
+- **NUM_NODES boolean**（不可用）
+
+  打印执行中的节点的个数信息。
+
+  取值范围:
+
+  - TRUE（缺省值）：打印数据库节点个数的信息。
+  - FALSE：不打印。
+
+- **BUFFERS boolean**
+
+  包括缓冲区的使用情况的信息。
+
+  取值范围:
+
+  - TRUE：显示缓冲区的使用情况。
+  - FALSE（缺省值）：不显示。
+
+- **TIMING boolean**
+
+  包括实际的启动时间和花费在输出节点上的时间信息。
+
+  取值范围:
+
+  - TRUE（缺省值）：显示启动时间和花费在输出节点上的时间信息。
+  - FALSE：不显示。
+
+- **PLAN**
+
+  是否将执行计划存储在plan_table中。当该选项开启时，会将执行计划存储在PLAN_TABLE中，不打印到当前屏幕，因此该选项为on时，不能与其他选项同时使用。
+
+  取值范围:
+
+  - ON（缺省值）：将执行计划存储在plan_table中，不打印到当前屏幕。执行成功返回EXPLAIN SUCCESS。
+  - OFF：不存储执行计划，将执行计划打印到当前屏幕。
+
+- **FORMAT**
+
+  指定输出格式。
+
+  取值范围: TEXT，XML，JSON和YAML。
+
+  默认值：TEXT。
+
+- **PERFORMANCE**
+
+  使用此选项时，即打印执行中的所有相关信息。
+
+## 示例
+
+```
+--创建一个表tpcds.customer_address_p1。
+mogdb=# CREATE TABLE tpcds.customer_address_p1 AS TABLE tpcds.customer_address;
+
+--修改explain_perf_mode为normal
+mogdb=# SET explain_perf_mode=normal;
+
+--显示表简单查询的执行计划。
+mogdb=# EXPLAIN SELECT * FROM tpcds.customer_address_p1;
+QUERY PLAN
+--------------------------------------------------
+Data Node Scan  (cost=0.00..0.00 rows=0 width=0)
+Node/s: All dbnodes
+(2 rows)
+
+--以JSON格式输出的执行计划（explain_perf_mode为normal时）。
+mogdb=# EXPLAIN(FORMAT JSON) SELECT * FROM tpcds.customer_address_p1;
+              QUERY PLAN
+--------------------------------------
+ [                                   +
+   {                                 +
+     "Plan": {                       +
+       "Node Type": "Data Node Scan",+
+       "Startup Cost": 0.00,         +
+       "Total Cost": 0.00,           +
+       "Plan Rows": 0,               +
+       "Plan Width": 0,              +
+       "Node/s": "All dbnodes"     +
+     }                               +
+   }                                 +
+ ]
+(1 row)
+
+--如果有一个索引，当使用一个带索引WHERE条件的查询，可能会显示一个不同的计划。
+mogdb=# EXPLAIN SELECT * FROM tpcds.customer_address_p1 WHERE ca_address_sk=10000;
+QUERY PLAN
+--------------------------------------------------
+Data Node Scan  (cost=0.00..0.00 rows=0 width=0)
+Node/s: dn_6005_6006
+(2 rows)
+
+--以YAML格式输出的执行计划（explain_perf_mode为normal时）。
+mogdb=# EXPLAIN(FORMAT YAML) SELECT * FROM tpcds.customer_address_p1 WHERE ca_address_sk=10000;
+           QUERY PLAN
+---------------------------------
+ - Plan:                        +
+     Node Type: "Data Node Scan"+
+     Startup Cost: 0.00         +
+     Total Cost: 0.00           +
+     Plan Rows: 0               +
+     Plan Width: 0              +
+     Node/s: "dn_6005_6006"
+(1 row)
+
+--禁止开销估计的执行计划。
+mogdb=# EXPLAIN(COSTS FALSE)SELECT * FROM tpcds.customer_address_p1 WHERE ca_address_sk=10000;
+       QUERY PLAN
+------------------------
+ Data Node Scan
+   Node/s: dn_6005_6006
+(2 rows)
+
+--带有聚集函数查询的执行计划。
+mogdb=# EXPLAIN SELECT SUM(ca_address_sk) FROM tpcds.customer_address_p1 WHERE ca_address_sk<10000;
+                                      QUERY PLAN
+---------------------------------------------------------------------------------------
+ Aggregate  (cost=18.19..14.32 rows=1 width=4)
+   ->  Streaming (type: GATHER)  (cost=18.19..14.32 rows=3 width=4)
+         Node/s: All dbnodes
+         ->  Aggregate  (cost=14.19..14.20 rows=3 width=4)
+               ->  Seq Scan on customer_address_p1  (cost=0.00..14.18 rows=10 width=4)
+                     Filter: (ca_address_sk < 10000)
+(6 rows)
+
+--删除表tpcds.customer_address_p1。
+mogdb=# DROP TABLE tpcds.customer_address_p1;
+```
+
+## 相关链接
+
+[ANALYZE | ANALYSE](32-ANALYZE-ANALYSE)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/106-EXPLAIN-PLAN.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/106-EXPLAIN-PLAN.md
new file mode 100644
index 0000000000000000000000000000000000000000..1ff98cb622ada53682cff2afff7efc461c06cfb6
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/106-EXPLAIN-PLAN.md
@@ -0,0 +1,84 @@
+---
+title: EXPLAIN PLAN
+summary: EXPLAIN PLAN
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# EXPLAIN PLAN
+
+## 功能描述
+
+通过EXPLAIN PLAN命令可以将查询执行的计划信息存储于PLAN_TABLE表中。与EXPLAIN命令不同的是，EXPLAIN PLAN仅将计划信息进行存储，而不会打印到屏幕。
+
+## 语法格式
+
+```ebnf+diagram
+ExplainPlan ::= EXPLAIN PLAN
+[ SET STATEMENT_ID = string ]
+FOR statement ;
+```
+
+## 参数说明
+
+- EXPLAIN中的PLAN选项表示需要将计划信息存储于PLAN_TABLE中，存储成功将返回“EXPLAIN SUCCESS”。
+
+- STATEMENT_ID用户可以对查询设置标签，输入的标签信息也将存储于PLAN_TABLE中。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  > 用户在执行EXPLAIN PLAN时，如果没有进行SET STATEMENT_ID，则默认为空值。同时，用户可输入的STATEMENT_ID最大长度为30个字节，超过长度将会产生报错。
+
+## 注意事项
+
+- EXPLAIN PLAN不支持在数据库节点上执行。
+- 对于执行错误的SQL无法进行计划信息的收集。
+- PLAN_TABLE中的数据是session级生命周期并且session隔离和用户隔离，用户只能看到当前session、当前用户的数据。
+
+## 示例
+
+使用EXPLAIN PLAN收集SQL语句的执行计划，通常包括以下步骤：
+
+1. 执行EXPLAN PLAN。
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+   > 执行EXPLAIN PLAN 后会将计划信息自动存储于PLAN_TABLE中，不支持对PLAN_TABLE进行INSERT、UPDATE、ANALYZE等操作。
+   > PLAN_TABLE详细介绍见**PLAN_TABLE**。
+
+   ```sql
+   explain plan set statement_id='TPCH-Q4' for
+   select
+   o_orderpriority,
+   count(*) as order_count
+   from
+   orders
+   where
+   o_orderdate >= '1993-07-01'::date
+   and o_orderdate < '1993-07-01'::date + interval '3 month'
+   and exists (
+   select
+   *
+   from
+   lineitem
+   where
+   l_orderkey = o_orderkey
+   and l_commitdate < l_receiptdate
+   )
+   group by
+   o_orderpriority
+   order by
+   o_orderpriority;
+   ```
+
+2. 查询PLAN_TABLE。
+
+   ```sql
+   SELECT * FROM PLAN_TABLE;
+   ```
+
+   ![img](https://cdn-mogdb.enmotech.com/docs-media/mogdb/reference-guide/EXPLAIN-PLAN.png)
+
+3. 清理PLAN_TABLE表中的数据。
+
+   ```sql
+   DELETE FROM PLAN_TABLE WHERE xxx;
+   ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/107-FETCH.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/107-FETCH.md
new file mode 100644
index 0000000000000000000000000000000000000000..1af4510a148f700eed1bb19fa0e5828a9b4ca56b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/107-FETCH.md
@@ -0,0 +1,218 @@
+---
+title: FETCH
+summary: FETCH
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# FETCH
+
+## 功能描述
+
+FETCH通过已创建的游标来检索数据。
+
+每个游标都有一个供FETCH使用的关联位置。游标的关联位置可以在查询结果的第一行之前，或者在结果中的任意行，或者在结果的最后一行之后：
+
+- 游标刚创建完之后，关联位置在第一行之前的。
+- 在抓取了一些移动行之后，关联位置在检索到的最后一行上。
+- 如果FETCH抓取完了所有可用行，它就停在最后一行后面，或者在反向抓取的情况下是停在第一行前面。
+- FETCH ALL或FETCH BACKWARD ALL将总是把游标的关联位置放在最后一行或者在第一行前面。
+
+## 注意事项
+
+- 如果游标定义了NO SCROLL，则不允许使用例如FETCH BACKWARD之类的反向抓取。
+- NEXT，PRIOR，FIRST，LAST，ABSOLUTE，RELATIVE形式在恰当地移动游标之后抓取一条记录。如果后面没有数据行，就返回一个空的结果，此时游标就会停在查询结果的最后一行之后（向后查询时）或者第一行之前（向前查询时）。
+- FORWARD和BACKWARD形式在向前或者向后移动的过程中抓取指定的行数，然后把游标定位在最后返回的行上；或者是，如果count大于可用的行数，则在所有行之后（向后查询时）或者之前（向前查询时）。
+- RELATIVE 0，FORWARD 0，BACKWARD 0都要求在不移动游标的前提下抓取当前行，也就是重新抓取最近刚抓取过的行。除非游标定位在第一行之前或者最后一行之后，这个动作都应该成功，而在那两种情况下，不返回任何行。
+- 当FETCH的游标上涉及列存表时，不支持BACKWARD、PRIOR等涉及反向获取操作。
+
+## 语法格式
+
+```ebnf+diagram
+Fetch ::= FETCH [ direction { FROM | IN } ] cursor_name;
+```
+
+其中direction子句为可选参数。
+
+```ebnf+diagram
+direction ::= NEXT
+   | PRIOR
+   | FIRST
+   | LAST
+   | ABSOLUTE count
+   | RELATIVE count
+   | count
+   | ALL
+   | FORWARD
+   | FORWARD count
+   | FORWARD ALL
+   | BACKWARD
+   | BACKWARD count
+   | BACKWARD ALL
+```
+
+## 参数说明
+
+- **direction_clause**
+
+  定义抓取数据的方向。
+
+  取值范围:
+
+  - NEXT（缺省值）
+
+    从当前关联位置开始，抓取下一行。
+
+  - PRIOR
+
+    从当前关联位置开始，抓取上一行。
+
+  - FIRST
+
+    抓取查询的第一行（和ABSOLUTE 1相同）。
+
+  - LAST
+
+    抓取查询的最后一行（和ABSOLUTE -1相同）。
+
+  - ABSOLUTE count
+
+    抓取查询中第count行。
+
+    ABSOLUTE抓取不会比用相对位移移动到需要的数据行更快，因为下层的实现必须遍历所有中间的行。
+
+    count取值范围: 有符号的整数
+
+    - count为正数，就从查询结果的第一行开始，抓取第count行。
+    - count为负数，就从查询结果末尾抓取第abs（count）行。
+    - count为0时，定位在第一行之前。
+
+  - RELATIVE count
+
+    从当前关联位置开始，抓取随后或前面的第count行。
+
+    取值范围: 有符号的整数
+
+    - count为正数就抓取当前关联位置之后的第count行。
+    - count为负数就抓取当前关联位置之前的第abs（count）行。
+    - 如果当前行没有数据的话，RELATIVE 0返回空。
+
+  - count
+
+    抓取随后的count行（和FORWARD count一样）。
+
+  - ALL
+
+    从当前关联位置开始，抓取所有剩余的行（和FORWARD ALL一样）。
+
+  - FORWARD
+
+    抓取下一行（和NEXT一样）。
+
+  - FORWARD count
+
+    从当前关联位置开始，抓取随后或前面的count行。
+
+  - FORWARD ALL
+
+    从当前关联位置开始，抓取所有剩余行。
+
+  - BACKWARD
+
+    从当前关联位置开始，抓取前面一行(和PRIOR一样) 。
+
+  - BACKWARD count
+
+    从当前关联位置开始，抓取前面的count行（向后扫描）。
+
+    取值范围: 有符号的整数
+
+    - count为正数就抓取当前关联位置之前的count行。
+    - count为负数就抓取当前关联位置之后的abs（count）行。
+    - 如果有数据的话，BACKWARD 0重新抓取当前行。
+
+  - BACKWARD ALL
+
+    从当前关联位置开始，抓取所有前面的行（向后扫描） 。
+
+- **{ FROM | IN } cursor_name**
+
+  使用关键字FROM或IN指定游标名称。
+
+  取值范围: 已创建的游标的名称。
+
+## 示例
+
+```sql
+--SELECT语句，用一个游标读取一个表。开始一个事务。
+mogdb=# START TRANSACTION;
+
+--建立一个名为cursor1的游标。
+mogdb=# CURSOR cursor1 FOR SELECT * FROM tpcds.customer_address ORDER BY 1;
+
+--抓取头3行到游标cursor1里。
+mogdb=# FETCH FORWARD 3 FROM cursor1;
+ ca_address_sk |  ca_address_id   | ca_street_number |   ca_street_name   | ca_street_type  | ca_suite_number |     ca_city     |    ca_county    | ca_state |   ca_zip   |  ca_country   | ca_gmt_offset |   ca_location_type
+---------------+------------------+------------------+--------------------+-----------------+-----------------+-----------------+-----------------+----------+------------+---------------+---------------+----------------------
+             1 | AAAAAAAABAAAAAAA | 18               | Jackson            | Parkway         | Suite 280       | Fairfield       | Maricopa County | AZ       | 86192      | United States |         -7.00 | condo
+             2 | AAAAAAAACAAAAAAA | 362              | Washington 6th     | RD              | Suite 80        | Fairview        | Taos County     | NM       | 85709      | United States |         -7.00 | condo
+             3 | AAAAAAAADAAAAAAA | 585              | Dogwood Washington | Circle          | Suite Q         | Pleasant Valley | York County     | PA       | 12477      | United States |         -5.00 | single family
+(3 rows)
+
+--关闭游标并提交事务。
+mogdb=# CLOSE cursor1;
+
+--结束一个事务。
+mogdb=# END;
+
+--VALUES子句，用一个游标读取VALUES子句中的内容。开始一个事务。
+mogdb=# START TRANSACTION;
+
+--建立一个名为cursor2的游标。
+mogdb=# CURSOR cursor2 FOR VALUES(1,2),(0,3) ORDER BY 1;
+
+--抓取头2行到游标cursor2里。
+mogdb=# FETCH FORWARD 2 FROM cursor2;
+column1 | column2
+---------+---------
+0 |       3
+1 |       2
+(2 rows)
+
+--关闭游标并提交事务。
+mogdb=# CLOSE cursor2;
+
+--结束一个事务。
+mogdb=# END;
+
+--WITH HOLD游标的使用，开启事务。
+mogdb=# START TRANSACTION;
+
+--创建一个with hold游标。
+mogdb=# DECLARE cursor1 CURSOR WITH HOLD FOR SELECT * FROM tpcds.customer_address ORDER BY 1;
+
+--抓取头2行到游标cursor1里。
+mogdb=# FETCH FORWARD 2 FROM cursor1;
+ ca_address_sk |  ca_address_id   | ca_street_number |   ca_street_name   | ca_street_type  | ca_suite_number |     ca_city     |    ca_county    | ca_state |   ca_zip   |  ca_country   | ca_gmt_offset |   ca_location_type
+---------------+------------------+------------------+--------------------+-----------------+-----------------+-----------------+-----------------+----------+------------+---------------+---------------+----------------------
+             1 | AAAAAAAABAAAAAAA | 18               | Jackson            | Parkway         | Suite 280       | Fairfield       | Maricopa County | AZ       | 86192      | United States |         -7.00 | condo
+             2 | AAAAAAAACAAAAAAA | 362              | Washington 6th     | RD              | Suite 80        | Fairview        | Taos County     | NM       | 85709      | United States |         -7.00 | condo
+(2 rows)
+
+--结束事务。
+mogdb=# END;
+
+--抓取下一行到游标cursor1里。
+mogdb=# FETCH FORWARD 1 FROM cursor1;
+ ca_address_sk |  ca_address_id   | ca_street_number |   ca_street_name   | ca_street_type  | ca_suite_number |     ca_city     |    ca_county    | ca_state |   ca_zip   |  ca_country   | ca_gmt_offset |   ca_location_type
+---------------+------------------+------------------+--------------------+-----------------+-----------------+-----------------+-----------------+----------+------------+---------------+---------------+----------------------
+             3 | AAAAAAAADAAAAAAA | 585              | Dogwood Washington | Circle          | Suite Q         | Pleasant Valley | York County     | PA       | 12477      | United States |         -5.00 | single family
+(1 row)
+
+--关闭游标。
+mogdb=# CLOSE cursor1;
+```
+
+## 相关链接
+
+[CLOSE](36-CLOSE)，[MOVE](111-MOVE)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/108-GRANT.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/108-GRANT.md
new file mode 100644
index 0000000000000000000000000000000000000000..a54c0adad0a8f36645ce7466cd2018f7c80e735d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/108-GRANT.md
@@ -0,0 +1,573 @@
+---
+title: GRANT
+summary: GRANT
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# GRANT
+
+## 功能描述
+
+对角色和用户进行授权操作。
+
+使用GRANT命令进行用户授权包括以下三种场景：
+
+- **将系统权限授权给角色或用户**
+
+  系统权限又称为用户属性，包括SYSADMIN、CREATEDB、CREATEROLE、AUDITADMIN、MONADMIN、OPRADMIN、POLADMIN和LOGIN。
+
+  系统权限一般通过CREATE/ALTER ROLE语法来指定。其中，SYSADMIN权限可以通过GRANT/REVOKE ALL PRIVILEGE授予或撤销。但系统权限无法通过ROLE和USER的权限被继承，也无法授予PUBLIC。
+
+- **将数据库对象授权给角色或用户**
+
+  将数据库对象（表和视图、指定字段、数据库、函数、模式、表空间等）的相关权限授予特定角色或用户；
+
+  GRANT命令将数据库对象的特定权限授予一个或多个角色。这些权限会追加到已有的权限上。
+
+  关键字PUBLIC表示该权限要赋予所有角色，包括以后创建的用户。PUBLIC可以看做是一个隐含定义好的组，它总是包括所有角色。任何角色或用户都将拥有通过GRANT直接赋予的权限和所属的权限，再加上PUBLIC的权限。
+
+  如果声明了WITH GRANT OPTION，则被授权的用户也可以将此权限赋予他人，否则就不能授权给他人。这个选项不能赋予PUBLIC，这是MogDB特有的属性。
+
+  MogDB会将某些类型的对象上的权限授予PUBLIC。默认情况下，对表、表字段、序列、外部数据源、外部服务器、模式或表空间对象的权限不会授予PUBLIC，而以下这些对象的权限会授予PUBLIC：数据库的CONNECT权限和CREATE TEMP TABLE权限、函数的EXECUTE特权、语言和数据类型（包括域）的USAGE特权。当然，对象拥有者可以撤销默认授予PUBLIC的权限并专门授予权限给其他用户。为了更安全，建议在同一个事务中创建对象并设置权限，这样其他用户就没有时间窗口使用该对象。另外，这些初始的默认权限可以使用ALTER DEFAULT PRIVILEGES命令修改。
+
+  对象的所有者缺省具有该对象上的所有权限，出于安全考虑所有者可以舍弃部分权限，但ALTER、DROP、COMMENT、INDEX、VACUUM以及对象的可再授予权限属于所有者固有的权限，隐式拥有。
+
+- **将角色或用户的权限授权给其他角色或用户**
+
+  将一个角色或用户的权限授予一个或多个其他角色或用户。在这种情况下，每个角色或用户都可视为拥有一个或多个数据库权限的集合。
+
+  当声明了WITH ADMIN OPTION，被授权的用户可以将该权限再次授予其他角色或用户，以及撤销所有由该角色或用户继承到的权限。当授权的角色或用户发生变更或被撤销时，所有继承该角色或用户权限的用户拥有的权限都会随之发生变更。
+
+  数据库系统管理员可以给任何角色或用户授予/撤销任何权限。拥有CREATEROLE权限的角色可以赋予或者撤销任何非系统管理员角色的权限。
+
+## 注意事项
+
+无。
+
+## 语法格式
+
+- 将表或视图的访问权限赋予指定的用户或角色。
+
+  ```ebnf+diagram
+  Grant ::= GRANT { { SELECT | INSERT | UPDATE | DELETE | TRUNCATE | REFERENCES | ALTER | DROP | COMMENT | INDEX | VACUUM } [, ...]
+        | ALL [ PRIVILEGES ] }
+      ON { [ TABLE ] table_name [, ...]
+         | ALL TABLES IN SCHEMA schema_name [, ...] }
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ];
+
+  ```
+
+- 将表中字段的访问权限赋予指定的用户或角色。
+
+  ```ebnf+diagram
+  Grant ::= GRANT { {{ SELECT | INSERT | UPDATE | REFERENCES | COMMENT } ( column_name [, ...] )} [, ...]
+        | ALL [ PRIVILEGES ] ( column_name [, ...] ) }
+      ON [ TABLE ] table_name [, ...]
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ];
+  ```
+
+- 将序列的访问权限赋予指定的用户或角色。
+
+  ```ebnf+diagram
+  Grant ::= GRANT { { SELECT | UPDATE | USAGE | ALTER | DROP | COMMENT } [, ...]
+        | ALL [ PRIVILEGES ] }
+      ON { [ [ LARGE ] SEQUENCE ] sequence_name [, ...]
+         | ALL SEQUENCES IN SCHEMA schema_name [, ...] }
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ];
+  ```
+
+- 将数据库的访问权限赋予指定的用户或角色。
+
+  ```ebnf+diagram
+  Grant ::= GRANT { { CREATE | CONNECT | TEMPORARY | TEMP | ALTER | DROP | COMMENT } [, ...]
+        | ALL [ PRIVILEGES ] }
+      ON DATABASE database_name [, ...]
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ];
+  ```
+
+- 将域的访问权限赋予指定的用户或角色。
+
+  ```ebnf+diagram
+  Grant ::= GRANT { USAGE | ALL [ PRIVILEGES ] }
+      ON DOMAIN domain_name [, ...]
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ];
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 本版本暂时不支持赋予域的访问权限。
+
+- 将客户端加密主密钥CMK的访问权限赋予指定的用户或角色。
+
+  ```ebnf+diagram
+  Grant ::= GRANT { { USAGE | DROP } [, ...] | ALL [ PRIVILEGES ] }
+      ON CLIENT_MASTER_KEY client_master_key [, ...]
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ];
+  ```
+
+- 将列加密密钥CEK的访问权限赋予指定的用户或角色。
+
+  ```ebnf+diagram
+  Grant ::= GRANT { { USAGE | DROP } [, ...] | ALL [ PRIVILEGES ] }
+      ON COLUMN_ENCRYPTION_KEY column_encryption_key [, ...]
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ];
+  ```
+
+- 将外部数据源的访问权限赋予给指定的用户或角色。
+
+  ```ebnf+diagram
+  Grant ::= GRANT { USAGE | ALL [ PRIVILEGES ] }
+      ON FOREIGN DATA WRAPPER fdw_name [, ...]
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ];
+  ```
+
+- 将外部服务器的访问权限赋予给指定的用户或角色。
+
+  ```ebnf+diagram
+  Grant ::= GRANT { { USAGE | ALTER | DROP | COMMENT } [, ...] | ALL [ PRIVILEGES ] }
+      ON FOREIGN SERVER server_name [, ...]
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ];
+  ```
+
+- 将函数的访问权限赋予给指定的用户或角色。
+
+  ```ebnf+diagram
+  Grant ::= GRANT { { EXECUTE | ALTER | DROP | COMMENT } [, ...] | ALL [ PRIVILEGES ] }
+      ON { FUNCTION {function_name ( [ {[ argmode ] [ arg_name ] arg_type} [, ...] ] )} [, ...]
+         | ALL FUNCTIONS IN SCHEMA schema_name [, ...] }
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ];
+  ```
+
+- 将过程语言的访问权限赋予给指定的用户或角色。
+
+  ```ebnf+diagram
+  Grant ::= GRANT { USAGE | ALL [ PRIVILEGES ] }
+      ON LANGUAGE lang_name [, ...]
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ];
+  ```
+
+- 将大对象的访问权限赋予指定的用户或角色。
+
+  ```ebnf+diagram
+  Grant ::= GRANT { { SELECT | UPDATE } [, ...] | ALL [ PRIVILEGES ] }
+      ON LARGE OBJECT loid [, ...]
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ];
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 本版本暂时不支持大对象。
+
+- 将模式的访问权限赋予指定的用户或角色。
+
+  ```ebnf+diagram
+  Grant ::= GRANT { { CREATE | USAGE | ALTER | DROP | COMMENT } [, ...] | ALL [ PRIVILEGES ] }
+      ON SCHEMA schema_name [, ...]
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ];
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 将模式中的表或者视图对象授权给其他用户时，需要将表或视图所属的模式的USAGE权限同时授予该用户，若没有该权限，则只能看到这些对象的名称，并不能实际进行对象访问。同名模式下创建表的权限无法通过此语法赋予，可以通过将角色的权限赋予其他用户或角色的语法，赋予同名模式下创建表的权限。
+
+- 将表空间的访问权限赋予指定的用户或角色。
+
+  ```ebnf+diagram
+  Grant ::= GRANT { { CREATE | ALTER | DROP | COMMENT } [, ...] | ALL [ PRIVILEGES ] }
+      ON TABLESPACE tablespace_name [, ...]
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ];
+  ```
+
+- 将类型的访问权限赋予指定的用户或角色。
+
+  ```ebnf+diagram
+  Grant ::= GRANT { { USAGE | ALTER | DROP | COMMENT } [, ...] | ALL [ PRIVILEGES ] }
+      ON TYPE type_name [, ...]
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ];
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 本版本暂时不支持赋予类型的访问权限。
+
+- 将Data Source对象的权限赋予指定的角色。
+
+  ```ebnf+diagram
+  Grant ::= GRANT { USAGE | ALL [PRIVILEGES]}
+     ON DATA SOURCE src_name [, ...]
+     TO { [GROUP] role_name | PUBLIC } [, ...]
+     [WITH GRANT OPTION];
+  ```
+
+- 将directory对象的权限赋予指定的角色。
+
+  ```ebnf+diagram
+  Grant ::= GRANT { { READ | WRITE | ALTER | DROP } [, ...] | ALL [PRIVILEGES] }
+     ON DIRECTORY directory_name [, ...]
+     TO { [GROUP] role_name | PUBLIC } [, ...]
+     [WITH GRANT OPTION];
+  ```
+
+- 将package对象的权限赋予指定的角色。
+
+  ```ebnf+diagram
+  Grant ::= GRANT { { EXECUTE | ALTER | DROP | COMMENT } [, ...] | ALL [PRIVILEGES] }
+     ON PACKAGE package_name [, ...]
+     TO { [GROUP] role_name | PUBLIC } [, ...]
+     [WITH GRANT OPTION];
+  ```
+
+- 将角色的权限赋予其他用户或角色的语法。
+
+  ```ebnf+diagram
+  Grant ::= GRANT role_name [, ...]
+     TO role_name [, ...]
+     [ WITH ADMIN OPTION ];
+  ```
+
+- 将sysadmin权限赋予指定的角色。
+
+  ```ebnf+diagram
+  Grant ::= GRANT ALL { PRIVILEGES | PRIVILEGE }
+     TO role_name;
+  ```
+
+## 参数说明
+
+GRANT的权限分类如下所示。
+
+- **SELECT**
+
+  允许对指定的表、视图、序列执行SELECT命令，update或delete时也需要对应字段上的select权限。
+
+- **INSERT**
+
+  允许对指定的表执行INSERT命令。
+
+- **UPDATE**
+
+  允许对声明的表中任意字段执行UPDATE命令。通常，update命令也需要select权限来查询出哪些行需要更新。SELECT… FOR UPDATE和SELECT… FOR SHARE除了需要SELECT权限外，还需要UPDATE权限。
+
+- **DELETE**
+
+  允许执行DELETE命令删除指定表中的数据。通常，delete命令也需要select权限来查询出哪些行需要删除。
+
+- **TRUNCATE**
+
+  允许执行TRUNCATE语句删除指定表中的所有记录。
+
+- **REFERENCES**
+
+  创建一个外键约束，必须拥有参考表和被参考表的REFERENCES权限。
+
+- **CREATE**
+
+  - 对于数据库，允许在数据库里创建新的模式。
+  - 对于模式，允许在模式中创建新的对象。如果要重命名一个对象，用户除了必须是该对象的所有者外，还必须拥有该对象所在模式的CREATE权限。
+  - 对于表空间，允许在表空间中创建表，允许在创建数据库和模式的时候把该表空间指定为缺省表空间。
+
+- **CONNECT**
+
+  允许用户连接到指定的数据库。
+
+- **EXECUTE**
+
+  允许使用指定的函数，以及利用这些函数实现的操作符。
+
+- **USAGE**
+
+  - 对于过程语言，允许用户在创建函数的时候指定过程语言。
+  - 对于模式，USAGE允许访问包含在指定模式中的对象，若没有该权限，则只能看到这些对象的名称。
+  - 对于序列，USAGE允许使用nextval函数。
+  - 对于Data Source对象，USAGE是指访问权限，也是可赋予的所有权限，即USAGE与ALL PRIVILEGES等价。
+
+- **ALTER**
+
+  允许用户修改指定对象的属性，但不包括修改对象的所有者和修改对象所在的模式。
+
+- **DROP**
+
+  允许用户删除指定的对象。
+
+- **COMMENT**
+
+  允许用户定义或修改指定对象的注释。
+
+- **INDEX**
+
+  允许用户在指定表上创建索引，并管理指定表上的索引，还允许用户对指定表执行REINDEX和CLUSTER操作。
+
+- **VACUUM**
+
+  允许用户对指定的表执行ANALYZE和VACUUM操作。
+
+- **ALL PRIVILEGES**
+
+  一次性给指定用户/角色赋予所有可赋予的权限。只有系统管理员有权执行GRANT ALL PRIVILEGES。
+
+GRANT的参数说明如下所示。
+
+- **role_name**
+
+  已存在用户名称。
+
+- **table_name**
+
+  已存在表名称。
+
+- **column_name**
+
+  已存在字段名称。
+
+- **schema_name**
+
+  已存在模式名称。
+
+- **database_name**
+
+  已存在数据库名称。
+
+- **function_name**
+
+  已存在函数名称。
+
+- **sequence_name**
+
+  已存在序列名称。
+
+- **domain_name**
+
+  已存在域类型名称。
+
+- **fdw_name**
+
+  已存在外部数据包名称。
+
+- **lang_name**
+
+  已存在语言名称。
+
+- **type_name**
+
+  已存在类型名称。
+
+- **src_name**
+
+  已存在的Data Source对象名称。
+
+- **argmode**
+
+  参数模式。
+
+  取值范围: 字符串，要符合标识符命名规范。
+
+- **arg_name**
+
+  参数名称。
+
+  取值范围: 字符串，要符合标识符命名规范。
+
+- **arg_type**
+
+  参数类型。
+
+  取值范围: 字符串，要符合标识符命名规范。
+
+- **loid**
+
+  包含本页的大对象的标识符。
+
+  取值范围: 字符串，要符合标识符命名规范。
+
+- **tablespace_name**
+
+  表空间名称。
+
+- client_master_key
+
+  客户端加密主密钥的名称。
+
+  取值范围: 字符串，要符合标识符命名规范。
+
+- column_encryption_key
+
+  列加密密钥的名称。
+
+  取值范围: 字符串，要符合标识符命名规范。
+
+- **directory_name**
+
+  目录名称。
+
+  取值范围: 字符串，要符合标识符命名规范。
+
+- **WITH GRANT OPTION**
+
+  如果声明了WITH GRANT OPTION，则被授权的用户也可以将此权限赋予他人，否则就不能授权给他人。这个选项不能赋予PUBLIC。
+
+非对象所有者给其他用户授予对象权限时，命令按照以下规则执行：
+
+- 如果用户没有该对象上指定的权限，命令立即失败。
+- 如果用户有该对象上的部分权限，则GRANT命令只授予他有授权选项的权限。
+- 如果用户没有可用的授权选项，GRANT ALL PRIVILEGES形式将发出一个警告信息，其他命令形式将发出在命令中提到的且没有授权选项的相关警告信息。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 数据库系统管理员可以访问所有对象，而不会受对象的权限设置影响。这个特点类似Unix系统的root的权限。和root一样，除了必要的情况外，建议不要总是以系统管理员身份进行操作。 不允许对表分区进行GRANT操作，对分区表进行GRANT操作会引起告警。
+
+## 示例
+
+**示例：将系统权限授权给用户或者角色。**
+
+创建名为joe的用户，并将sysadmin权限授权给他。
+
+```sql
+mogdb=# CREATE USER joe PASSWORD 'Bigdata@123';
+mogdb=# GRANT ALL PRIVILEGES TO joe;
+```
+
+授权成功后，用户joe会拥有sysadmin的所有权限。
+
+**示例：将对象权限授权给用户或者角色**。
+
+1. 撤销joe用户的sysadmin权限，然后将模式tpcds的使用权限和表tpcds.reason的所有权限授权给用户joe。
+
+   ```sql
+   mogdb=# REVOKE ALL PRIVILEGES FROM joe;
+   mogdb=# GRANT USAGE ON SCHEMA tpcds TO joe;
+   mogdb=# GRANT ALL PRIVILEGES ON tpcds.reason TO joe;
+   ```
+
+   授权成功后，joe用户就拥有了tpcds.reason表的所有权限，包括增删改查等权限。
+
+2. 将tpcds.reason表中r_reason_sk、r_reason_id、r_reason_desc列的查询权限，r_reason_desc的更新权限授权给joe。
+
+   ```sql
+   mogdb=# GRANT select (r_reason_sk,r_reason_id,r_reason_desc),update (r_reason_desc) ON tpcds.reason TO joe;
+   ```
+
+   授权成功后，用户joe对tpcds.reason表中r_reason_sk，r_reason_id的查询权限会立即生效。如果joe用户需要拥有将这些权限授权给其他用户的权限，可以通过以下语法对joe用户进行授权。
+
+   ```sql
+   mogdb=# GRANT select (r_reason_sk, r_reason_id) ON tpcds.reason TO joe WITH GRANT OPTION;
+   ```
+
+   将数据库mogdb的连接权限授权给用户joe，并给予其在mogdb中创建schema的权限，而且允许joe将此权限授权给其他用户。
+
+   ```sql
+   mogdb=# GRANT create,connect on database mogdb TO joe WITH GRANT OPTION;
+   ```
+
+   创建角色tpcds_manager，将模式tpcds的访问权限授权给角色tpcds_manager，并授予该角色在tpcds下创建对象的权限，不允许该角色中的用户将权限授权给其他人。
+
+   ```sql
+   mogdb=# CREATE ROLE tpcds_manager PASSWORD 'Bigdata@123';
+   mogdb=# GRANT USAGE,CREATE ON SCHEMA tpcds TO tpcds_manager;
+   ```
+
+   将表空间tpcds_tbspc的所有权限授权给用户joe，但用户joe无法将权限继续授予其他用户。
+
+   ```sql
+   mogdb=# CREATE TABLESPACE tpcds_tbspc RELATIVE LOCATION 'tablespace/tablespace_1';
+   mogdb=# GRANT ALL ON TABLESPACE tpcds_tbspc TO joe;
+   ```
+
+**示例：将用户或者角色的权限授权给其他用户或角色。**
+
+1. 创建角色manager，将joe的权限授权给manager，并允许该角色将权限授权给其他人。
+
+   ```sql
+   mogdb=# CREATE ROLE manager PASSWORD 'Bigdata@123';
+   mogdb=# GRANT joe TO manager WITH ADMIN OPTION;
+   ```
+
+2. 创建用户senior_manager，将用户manager的权限授权给该用户。
+
+   ```sql
+   mogdb=# CREATE ROLE senior_manager PASSWORD 'Bigdata@123';
+   mogdb=# GRANT manager TO senior_manager;
+   ```
+
+3. 撤销权限，并清理用户。
+
+   ```sql
+   mogdb=# REVOKE manager FROM joe;
+   mogdb=# REVOKE senior_manager FROM manager;
+   mogdb=# DROP USER manager;
+   ```
+
+**示例：将CMK或者CEK的权限授权给其他用户或角色。**
+
+1. 连接密态数据库
+
+   ```sql
+   gsql -p 57101 mogdb -r -C
+   mogdb=#  CREATE CLIENT MASTER KEY MyCMK1 WITH ( KEY_STORE = localkms , KEY_PATH = "key_path_value" , ALGORITHM = RSA_2048);
+   CREATE CLIENT MASTER KEY
+   mogdb=# CREATE COLUMN ENCRYPTION KEY MyCEK1 WITH VALUES (CLIENT_MASTER_KEY = MyCMK1, ALGORITHM = AEAD_AES_256_CBC_HMAC_SHA256);
+   CREATE COLUMN ENCRYPTION KEY
+   ```
+
+2. 创建角色newuser，将密钥的权限授权给newuser。
+
+   ```sql
+   mogdb=# CREATE USER newuser PASSWORD 'gauss@123';
+   CREATE ROLE
+   mogdb=# GRANT ALL ON SCHEMA public TO newuser;
+   GRANT
+   mogdb=# GRANT USAGE ON COLUMN_ENCRYPTION_KEY MyCEK1 to newuser;
+   GRANT
+   mogdb=# GRANT USAGE ON CLIENT_MASTER_KEY MyCMK1 to newuser;
+   GRANT
+   ```
+
+3. 设置该用户连接数据库,使用该CEK创建加密表。
+
+   ```sql
+   mogdb=# SET SESSION AUTHORIZATION newuser PASSWORD 'gauss@123';
+   mogdb=>  CREATE TABLE acltest1 (x int, x2 varchar(50) ENCRYPTED WITH (COLUMN_ENCRYPTION_KEY = MyCEK1, ENCRYPTION_TYPE = DETERMINISTIC));
+   NOTICE:  The 'DISTRIBUTE BY' clause is not specified. Using 'x' as the distribution column by default.
+   HINT:  Please use 'DISTRIBUTE BY' clause to specify suitable data distribution column.
+   CREATE TABLE
+   mogdb=> SELECT has_cek_privilege('newuser', 'MyCEK1', 'USAGE');
+    has_cek_privilege
+   -------------------
+    t
+   (1 row)
+   ```
+
+4. 撤销权限，并清理用户。
+
+   ```sql
+   mogdb=# REVOKE USAGE ON COLUMN_ENCRYPTION_KEY MyCEK1 FROM newuser;
+   mogdb=# REVOKE USAGE ON CLIENT_MASTER_KEY MyCMK1 FROM newuser;
+   mogdb=# DROP TABLE newuser.acltest1;
+   mogdb=# DROP COLUMN ENCRYPTION KEY MyCEK1;
+   mogdb=# DROP CLIENT MASTER KEY MyCMK1;
+   mogdb=# DROP SCHEMA IF EXISTS newuser CASCADE;
+   mogdb=# REVOKE ALL ON SCHEMA public FROM newuser;
+   mogdb=# DROP ROLE IF EXISTS newuser;
+   ```
+
+**示例：撤销上述授予的权限，并清理角色和用户。**
+
+```sql
+mogdb=# REVOKE ALL PRIVILEGES ON tpcds.reason FROM joe;
+mogdb=# REVOKE ALL PRIVILEGES ON SCHEMA tpcds FROM joe;
+mogdb=# REVOKE ALL ON TABLESPACE tpcds_tbspc FROM joe;
+mogdb=# DROP TABLESPACE tpcds_tbspc;
+mogdb=# REVOKE USAGE,CREATE ON SCHEMA tpcds FROM tpcds_manager;
+mogdb=# DROP ROLE tpcds_manager;
+mogdb=# DROP ROLE senior_manager;
+mogdb=# DROP USER joe CASCADE;
+```
+
+## 相关链接
+
+[REVOKE](120-REVOKE)，[ALTER DEFAULT PRIVILEGES](4-ALTER-DEFAULT-PRIVILEGES)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/109-INSERT.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/109-INSERT.md
new file mode 100644
index 0000000000000000000000000000000000000000..4e39da66c5c69cfe506302c838af8f3c8b30166d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/109-INSERT.md
@@ -0,0 +1,167 @@
+---
+title: INSERT
+summary: INSERT
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# INSERT
+
+## 功能描述
+
+向表中添加一行或多行数据。
+
+## 注意事项
+
+- 只有拥有表INSERT权限的用户，才可以向表中插入数据。
+
+- 如果使用RETURNING子句，用户必须要有该表的SELECT权限。
+
+- 如果使用ON DUPLICATE KEY UPDATE，用户必须要有该表的SELECT、UPDATE权限，唯一约束（主键或唯一索引）的SELECT权限。
+
+- 如果使用query子句插入来自查询里的数据行，用户还需要拥有在查询里使用的表的SELECT权限。
+
+- 当连接到TD兼容的数据库时，td_compatible_truncation参数设置为on时，将启用超长字符串自动截断功能，在后续的insert语句中（不包含外表的场景下），对目标表中char和varchar类型的列上插入超长字符串时，系统会自动按照目标表中相应列定义的最大长度对超长字符串进行截断。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  > 如果向字符集为字节类型编码（SQL_ASCII，LATIN1等）的数据库中插入多字节字符数据（如汉字等），且字符数据跨越截断位置，这种情况下，按照字节长度自动截断，自动截断后会在尾部产生非预期结果。如果用户有对于截断结果正确性的要求，建议用户采用UTF8等能够按照字符截断的输入字符集作为数据库的编码集。
+
+## 语法格式
+
+```ebnf+diagram
+Insert ::= [ WITH [ RECURSIVE ] with_query [, ...] ]
+INSERT INTO table_name [ ( column_name [, ...] ) ]
+    { DEFAULT VALUES
+    | VALUES {( { expression | DEFAULT } [, ...] ) }[, ...]
+    | query }
+    [ ON DUPLICATE KEY UPDATE {{ column_name = { expression | DEFAULT } } [, ...] | NOTHING} ]
+    [ RETURNING {* | {output_expression [ [ AS ] output_name ] }[, ...]} ];
+```
+
+## 参数说明
+
+- **WITH [ RECURSIVE ] with_query [, …]**
+
+  用于声明一个或多个可以在主查询中通过名称引用的子查询，相当于临时表。
+
+  如果声明了RECURSIVE，那么允许SELECT子查询通过名称引用它自己。
+
+  其中with_query的详细格式为：with_query_name [ ( column_name [, …] ) ] AS
+
+  ( {select | values | insert | update | delete} )
+
+  - with_query_name指定子查询生成的结果集名称，在查询中可使用该名称访问子查询的结果集。
+
+  - column_name指定子查询结果集中显示的列名。
+
+  - 每个子查询可以是SELECT，VALUES，INSERT，UPDATE或DELETE语句。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  >
+> INSERT ON DUPLICATE KEY UPDATE不支持WITH及WITH RECURSIVE子句。
+
+- **table_name**
+
+  要插入数据的目标表名。
+
+  取值范围: 已存在的表名。
+
+- **column_name**
+
+  目标表中的字段名：
+
+  - 字段名可以有子字段名或者数组下标修饰。
+  - 没有在字段列表中出现的每个字段，将由系统默认值，或者声明时的默认值填充，若都没有则用NULL填充。例如，向一个复合类型中的某些字段插入数据的话，其他字段将是NULL。
+  - 目标字段（column_name）可以按顺序排列。如果没有列出任何字段，则默认全部字段，且顺序为表声明时的顺序。
+  - 如果value子句和query中只提供了N个字段，则目标字段为前N个字段。
+  - value子句和query提供的值在表中从左到右关联到对应列。
+
+  取值范围: 已存在的字段名。
+
+- **expression**
+
+  赋予对应column的一个有效表达式或值：
+
+  - 如果是INSERT ON DUPLICATE KEY UPDATE语句下，expression可以为VALUES(column_name)或EXCLUDED.column_name用来表示引用冲突行对应的column_name字段的值。需注意，其中VALUES(column_name)不支持嵌套在表达式中（例如VALUES(column_name)+1），但EXCLUDED不受此限制。
+  - 向表中字段插入单引号 “ ' “时需要使用单引号自身进行转义。
+  - 如果插入行的表达式不是正确的数据类型，系统试图进行类型转换，若转换不成功，则插入数据失败，系统返回错误信息。
+
+- **DEFAULT**
+
+  对应字段名的缺省值。如果没有缺省值，则为NULL。
+
+- **query**
+
+  一个查询语句（SELECT语句），将查询结果作为插入的数据。
+
+- **RETURNING**
+
+  返回实际插入的行，RETURNING列表的语法与SELECT的输出列表一致。注意：INSERT ON DUPLICATE KEY UPDATE不支持RETURNING子句。
+
+- **output_expression**
+
+  INSERT命令在每一行都被插入之后用于计算输出结果的表达式。
+
+  取值范围: 该表达式可以使用table的任意字段。可以使用*返回被插入行的所有字段。
+
+- **output_name**
+
+  字段的输出名称。
+
+  取值范围: 字符串，符合标识符命名规范。
+
+- **ON DUPLICATE KEY UPDATE**
+
+  对于带有唯一约束（UNIQUE INDEX或PRIMARY KEY）的表，如果插入数据违反唯一约束，则对冲突行执行UPDATE子句完成更新，对于不带唯一约束的表，则仅执行插入。UPDATE时，若指定NOTHING则忽略此条插入，可通过”EXCLUDE.” 或者 “VALUES()” 来选择源数据相应的列。
+
+  - 支持触发器，触发器执行顺序由实际执行流程决定：
+    - 执行insert：触发before insert、after insert触发器。
+    - 执行update：触发before insert、before update、after update触发器。
+    - 执行update nothing：触发before insert触发器。
+  - 不支持延迟生效（DEFERRABLE）的唯一约束或主键。
+  - 如果表中存在多个唯一约束，如果所插入数据违反多个唯一约束，对于检测到冲突的第一行进行更新，其他冲突行不更新（检查顺序与索引维护具有强相关性，一般先创建的索引先进行冲突检查）。
+
+  - 如果插入多行，这些行均与表中同一行数据存在唯一约束冲突，则按照顺序，第一条执行插入或更新，之后依次执行更新。
+  - 主键、唯一索引列不允许UPDATE。
+
+  - 不支持列存，不支持外表、内存表。
+  - expression支持使用子查询表达式，其语法与功能同UPDATE。子查询表达式中支持使用“EXCLUDED.”来选择源数据相应的列。
+
+## 示例
+
+```sql
+--创建表tpcds.reason_t2。
+mogdb=# CREATE TABLE tpcds.reason_t2
+(
+  r_reason_sk    integer,
+  r_reason_id    character(16),
+  r_reason_desc  character(100)
+);
+
+--向表中插入一条记录。
+mogdb=# INSERT INTO tpcds.reason_t2(r_reason_sk, r_reason_id, r_reason_desc) VALUES (1, 'AAAAAAAABAAAAAAA', 'reason1');
+
+--向表中插入一条记录，和上一条语法等效。
+mogdb=# INSERT INTO tpcds.reason_t2 VALUES (2, 'AAAAAAAABAAAAAAA', 'reason2');
+
+--向表中插入多条记录。
+mogdb=# INSERT INTO tpcds.reason_t2 VALUES (3, 'AAAAAAAACAAAAAAA','reason3'),(4, 'AAAAAAAADAAAAAAA', 'reason4'),(5, 'AAAAAAAAEAAAAAAA','reason5');
+
+--向表中插入tpcds.reason中r_reason_sk小于5的记录。
+mogdb=# INSERT INTO tpcds.reason_t2 SELECT * FROM tpcds.reason WHERE r_reason_sk <5;
+
+--对表创建唯一索引
+mogdb=# CREATE UNIQUE INDEX reason_t2_u_index ON tpcds.reason_t2(r_reason_sk);
+
+--向表中插入多条记录，如果冲突则更新冲突数据行中r_reason_id字段为'BBBBBBBBCAAAAAAA'。
+mogdb=# INSERT INTO tpcds.reason_t2 VALUES (5, 'BBBBBBBBCAAAAAAA','reason5'),(6, 'AAAAAAAADAAAAAAA', 'reason6') ON DUPLICATE KEY UPDATE r_reason_id = 'BBBBBBBBCAAAAAAA';
+
+--删除表tpcds.reason_t2。
+mogdb=# DROP TABLE tpcds.reason_t2;
+```
+
+## 优化建议
+
+- VALUES
+
+  通过insert语句批量插入数据时，建议将多条记录合并入一条语句中执行插入，以提高数据加载性能。例如，INSERT INTO sections VALUES (30, 'Administration', 31, 1900),(40, 'Development', 35, 2000), (50, 'Development' , 60 , 2001);
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/11-ALTER-MATERIALIZED-VIEW.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/11-ALTER-MATERIALIZED-VIEW.md
new file mode 100644
index 0000000000000000000000000000000000000000..2805dd574285a6d5913f0659172005b32ec8c5ad
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/11-ALTER-MATERIALIZED-VIEW.md
@@ -0,0 +1,79 @@
+---
+title: ALTER MATERIALIZED VIEW
+summary: ALTER MATERIALIZED VIEW
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER MATERIALIZED VIEW
+
+## 功能描述
+
+更改一个现有物化视图的多个辅助属性。
+
+可用于ALTER MATERIALIZED VIEW的语句形式和动作是ALTER TABLE的一个子集，并且在用于物化视图时具有相同的含义。
+
+## 注意事项
+
+- 只有物化视图的所有者有权限执行ALTER TMATERIALIZED VIEW命令，系统管理员默认拥有此权限。
+- 不支持更改物化视图结构。
+
+## 语法格式
+
+- 修改物化视图的定义。
+
+  ```ebnf+diagram
+  AlterMaterializedView ::= ALTER MATERIALIZED VIEW [ IF EXISTS ] mv_name
+   OWNER TO new_owner;
+  ```
+
+- 修改物化视图的列。
+
+  ```ebnf+diagram
+  AlterMaterializedView ::= ALTER MATERIALIZED VIEW [ IF EXISTS ] mv_name
+   RENAME [ COLUMN ] column_name TO new_column_name;
+  ```
+
+- 重命名物化视图。
+
+  ```ebnf+diagram
+  AlterMaterializedView ::= ALTER MATERIALIZED VIEW [ IF EXISTS ] mv_name
+   RENAME TO new_name;
+  ```
+
+## 参数说明
+
+- **mv_name**
+
+  一个现有物化视图的名称，可以用模式修饰。
+
+  取值范围: 字符串，符合标识符命名规范。
+
+- **column_name**
+
+  一个新的或者现有的。
+
+  取值范围: 字符串，符合标识符命名规范。
+
+- **new_column_name**
+
+  一个现有列的新名称。
+
+- **new_owner**
+
+  该物化视图的新拥有者的用户名。
+
+- **new_name**
+
+  该物化视图的新名称。
+
+## 示例
+
+```sql
+--把物化视图foo重命名为bar。
+mogdb=# ALTER MATERIALIZED VIEW foo RENAME TO bar;
+```
+
+## 相关链接
+
+[CREATE MATERIALIZED VIEW](51-CREATE-MATERIALIZED-VIEW)，[CREATE INCREMENTAL MATERIALIZED VIEW](49.1-CREATE-INCREMENTAL-MATERIALIZED-VIEW)，[DROP MATERIALIZED VIEW](85-DROP-MATERIALIZED-VIEW)，[REFRESH INCREMENTAL MATERIALIZED VIEW](115.1-REFRESH-INCREMENTAL-MATERIALIZED-VIEW)  ，[REFRESH MATERIALIZED VIEW](116-REFRESH-MATERIALIZED-VIEW)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/11.1-ALTER-OPERATOR.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/11.1-ALTER-OPERATOR.md
new file mode 100644
index 0000000000000000000000000000000000000000..df825ea4d77e5ac84925a9b595e327d205f76c22
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/11.1-ALTER-OPERATOR.md
@@ -0,0 +1,62 @@
+---
+title: ALTER OPERATOR
+summary: ALTER OPERATOR
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# ALTER OPERATOR
+
+## 功能描述
+
+修改一个操作符的定义。
+
+## 注意事项
+
+ALTER OPERATOR改变一个操作符的定义。 目前唯一能用的功能是改变操作符的所有者。
+
+要使用ALTER OPERATOR，你必须是该操作符的所有者。 要修改所有者，你还必须是新的所有角色的直接或间接成员，并且该成员必须在此操作符的模式上有CREATE权限。 （这些限制强制了修改该所有者不会做任何通过删除和重建操作符不能做的事情。不过，超级用户可以以任何方式修改任意操作符的所有权。）
+
+## 语法格式
+
+```ebnf+diagram
+AlterOperator ::= ALTER OPERATOR name ( { left_type | NONE } , { right_type | NONE } ) OWNER TO new_owner;
+```
+
+```ebnf+diagram
+AlterOperator ::= ALTER OPERATOR name ( { left_type | NONE } , { right_type | NONE } ) SET SCHEMA new_schema;
+```
+
+## 参数说明
+
+- **name**
+
+  一个现有操作符的名字。
+
+- **left_type**
+
+  操作符的左操作数的数据类型；如果没有左操作数，那么写NONE。
+
+- **right_type**
+
+  操作符的右操作数的数据类型；如果没有右操作数，那么写NONE。
+
+- **new_owner**
+
+  操作符的新所有者。
+
+- **new_schema**
+
+  操作符的新模式名。
+
+## 示例
+
+改变一个用于text的用户定义操作符a @@ b：
+
+```sql
+ALTER OPERATOR @@ (text, text) OWNER TO joe;
+```
+
+## 兼容性
+
+SQL 标准里没有ALTER OPERATOR语句。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/11.2-ALTER-RESOURCE-LABEL.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/11.2-ALTER-RESOURCE-LABEL.md
new file mode 100644
index 0000000000000000000000000000000000000000..cb9691fdfc312f658734e97df6ccd31c9859c1a1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/11.2-ALTER-RESOURCE-LABEL.md
@@ -0,0 +1,71 @@
+---
+title: ALTER RESOURCE LABEL
+summary: ALTER RESOURCE LABEL
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# ALTER RESOURCE LABEL
+
+## 功能描述
+
+修改资源标签。
+
+## 注意事项
+
+只有poladmin, sysadmin或初始用户才能执行此操作。
+
+## 语法格式
+
+```ebnf+diagram
+AlterResourceLabel ::= ALTER RESOURCE LABEL label_name (ADD|REMOVE)
+  label_item_list[, ...]*;
+```
+
+- label_item_list：
+
+  ```ebnf+diagram
+  label_item_list ::= resource_type(resource_path[, ...]*)
+  ```
+
+- resource_type：
+
+  ```ebnf+diagram
+  label_item_list ::= TABLE | COLUMN | SCHEMA | VIEW | FUNCTION
+  ```
+
+## 参数说明
+
+- **label_name**
+
+  资源标签名称。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- **resource_type**
+
+  指的是要标记的数据库资源类型。
+
+- **resource_path**
+
+  指的是描述具体的数据库资源的路径。
+
+## 示例
+
+```sql
+--创建基本表table_for_label。
+mogdb=# CREATE TABLE table_for_label(col1 int, col2 text);
+
+--创建资源标签table_label。
+mogdb=# CREATE RESOURCE LABEL table_label ADD COLUMN(table_for_label.col1);
+
+--将col2添加至资源标签table_label中
+mogdb=# ALTER RESOURCE LABEL table_label ADD COLUMN(table_for_label.col2)
+
+--将资源标签table_label中的一项移除
+mogdb=# ALTER RESOURCE LABEL table_label REMOVE COLUMN(table_for_label.col1);
+```
+
+## 相关链接
+
+[CREATE RESOURCE LABEL](53.1-CREATE-RESOURCE-LABEL)，[DROP RESOURCE LABEL](86.1-DROP-RESOURCE-LABEL)。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/11.3-ALTER-RESOURCE-POOL.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/11.3-ALTER-RESOURCE-POOL.md
new file mode 100644
index 0000000000000000000000000000000000000000..f80d3fbef5dcc1b0558b9b50fdb8e8c4c7b251ee
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/11.3-ALTER-RESOURCE-POOL.md
@@ -0,0 +1,117 @@
+---
+title: ALTER RESOURCE POOL
+summary: ALTER RESOURCE POOL
+author: Zhang Cuiping
+date: 2021-11-01
+---
+
+# ALTER RESOURCE POOL
+
+## 功能描述
+
+修改一个资源池，指定其他控制组。
+
+## 注意事项
+
+只要用户对当前数据库有ALTER权限，就可以修改资源池。
+
+## 语法格式
+
+```ebnf+diagram
+AlterResourcePool ::= ALTER RESOURCE POOL pool_name
+    WITH ({MEM_PERCENT= pct | CONTROL_GROUP="group_name" | ACTIVE_STATEMENTS=stmt | MAX_DOP = dop | MEMORY_LIMIT='memory_size' | io_limits=io_limits | io_priority='io_priority'}[, ... ]);
+```
+
+## 参数说明
+
+- **pool_name**
+
+  资源池名称。
+
+  资源池名称为已创建的资源池。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- **group_name**
+
+  控制组名称。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  >
+  > - 设置控制组名称时，语法可以使用双引号，也可以使用单引号。
+  >
+  > - group_name对大小写敏感。
+  > - 不指定group_name时，默认指定的字符串为 “Medium”，代表指定DefaultClass控制组的”Medium” Timeshare控制组。
+  > - 若数据库管理员指定自定义Class组下的Workload控制组，如control_group的字符串为：”class1:workload1”；代表此资源池指定到class1控制组下的workload1控制组。也可同时指定Workload控制组的层次，如control_group的字符串为：”class1:workload1:1”。
+  > - 若数据库用户指定Timeshare控制组代表的字符串，即”Rush”、”High”、”Medium”或”Low”其中一种，如control_group的字符串为”High”；代表资源池指定到DefaultClass控制组下的”High” Timeshare控制组。
+
+  取值范围: 已创建的控制组。
+
+- **stmt**
+
+  资源池语句执行的最大并发数量。
+
+  取值范围: 数值型，-1~2147483647。
+
+- **dop**
+
+  资源池最大并发度，语句执行时能够创建的最多线程数量。
+
+  取值范围: 数值型，1~2147483647。
+
+- **memory_size**
+
+  资源池最大使用内存。
+
+  取值范围: 字符串，内容范围1KB~2047GB。
+
+- **mem_percent**
+
+  资源池可用内存占全部内存或者组用户内存使用的比例。
+
+  在多租户场景下，组用户和业务用户的mem_percent范围为1-100的整数，默认为20。
+
+  在普通场景下，普通用户的mem_percent范围为0-100的整数，默认值为0。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** mem_percent和memory_limit同时指定时，只有mem_percent起作用。
+
+- **io_limits**
+
+  资源池每秒可触发IO次数上限。
+
+  对于行存，以万次为单位计数，而列存则以正常次数计数。
+
+- **io_priority**
+
+  IO利用率高达90%时，重消耗IO作业进行IO资源管控时关联的优先级等级。
+
+  包括三档可选：Low、Medium和High。不控制时可设置为None，默认为None。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** io_limits和io_priority的设置都仅对复杂作业有效。包括批量导入（INSERT INTO SELECT，COPY FROM，CREATE TABLE AS等），单DN数据量大约超过500MB的复杂查询和VACUUM FULL等操作。
+
+## 示例
+
+本示例假定用户已成功创建自定义的class1控制组及其下属的Low、wg1、wg2 三个Workload控制组。
+
+```sql
+--创建一个资源池。
+mogdb=# CREATE RESOURCE POOL pool1;
+
+--更新一个资源池，其控制组指定为"DefaultClass"组下属的"High" Timeshare Workload控制组。
+mogdb=# ALTER RESOURCE POOL pool1 WITH (CONTROL_GROUP="High");
+
+--更新一个资源池，其控制组指定为"class1"组下属的"Low" Timeshare Workload控制组。
+mogdb=# ALTER RESOURCE POOL pool1 WITH (CONTROL_GROUP="class1:Low");
+
+--更新一个资源池，其控制组指定为"class1"组下属的"wg1" Workload控制组。
+mogdb=# ALTER RESOURCE POOL pool1 WITH (CONTROL_GROUP="class1:wg1");
+
+--更新一个资源池，其控制组指定为"class1"组下属的"wg2" Workload控制组。
+mogdb=# ALTER RESOURCE POOL pool1 WITH (CONTROL_GROUP="class1:wg2:3");
+--删除资源池pool1。
+mogdb=# DROP RESOURCE POOL pool1;
+```
+
+## 相关链接
+
+[CREATE RESOURCE POOL](53.2-CREATE-RESOURCE-POOL)，[DROP RESOURCE POOL](86.2-DROP-RESOURCE-POOL)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/110-LOCK.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/110-LOCK.md
new file mode 100644
index 0000000000000000000000000000000000000000..f26e9453db9dd95281e5eb9b66a9fa1a34ff0614
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/110-LOCK.md
@@ -0,0 +1,136 @@
+---
+title: LOCK
+summary: LOCK
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# LOCK
+
+## 功能描述
+
+LOCK TABLE获取表级锁。
+
+MogDB在为一个引用了表的命令自动请求锁时，尽可能选择最小限制的锁模式。如果用户需要一种更为严格的锁模式，可以使用LOCK命令。例如，一个应用是在Read Committed隔离级别上运行事务，并且它需要保证表中的数据在事务的运行过程中不被修改。为实现这个目的，则可以在查询之前对表使用SHARE锁模式进行锁定。这样将防止数据不被并发修改，从而保证后续的查询可以读到已提交的持久化的数据。因为SHARE锁模式与任何写操作需要的ROW EXCLUSIVE模式冲突，并且LOCK TABLE name IN SHARE MODE语句将等到所有当前持有ROW EXCLUSIVE模式锁的事务提交或回滚后才能执行。因此，一旦获得该锁，就不会存在未提交的写操作，并且其他操作也只能等到该锁释放之后才能开始。
+
+## 注意事项
+
+- LOCK TABLE只能在一个事务块的内部有用，因为锁在事务结束时就会被释放。出现在任意事务块外面的LOCK TABLE都会报错。
+- 如果没有声明锁模式，缺省为最严格的模式ACCESS EXCLUSIVE。
+- LOCK TABLE … IN ACCESS SHARE MODE需要在目标表上有SELECT权限。所有其他形式的LOCK需要UPDATE和/或DELETE权限。
+- 没有UNLOCK TABLE命令，锁总是在事务结束时释放。
+- LOCK TABLE只处理表级的锁，因此那些带“ROW”字样的锁模式都是有歧义的。这些模式名称通常可理解为用户试图在一个被锁定的表中获取行级的锁。同样，ROW EXCLUSIVE模式也是一个可共享的表级锁。注意，只要是涉及到LOCK TABLE ，所有锁模式都有相同的语意，区别仅在于规则中锁与锁之间是否冲突，规则请参见[表1](#conflict)。
+
+- 如果没有打开xc_maintenance_mode参数，那么对系统表申请ACCESS EXCLUSIVE级别锁将报错。
+
+## 语法格式
+
+```ebnf+diagram
+Lock ::=
+LOCK [ TABLE ] {[ ONLY ] name [, ...]| {name [ * ]} [, ...]}
+    [ IN {ACCESS SHARE | ROW SHARE | ROW EXCLUSIVE | SHARE UPDATE EXCLUSIVE | SHARE | SHARE ROW EXCLUSIVE | EXCLUSIVE | ACCESS EXCLUSIVE} MODE ]
+    [ NOWAIT ];
+```
+
+## 参数说明
+
+**表 1** 冲突的锁模式 <a id="conflict"></a>
+
+| 请求的锁模式/当前锁模式 | ACCESS SHARE | ROW SHARE | ROW EXCLUSIVE | SHARE UPDATE EXCLUSIVE | SHARE | SHARE ROW EXCLUSIVE | EXCLUSIVE | ACCESS EXCLUSIVE |
+| :---------------------- | :----------- | :-------- | :------------ | :--------------------- | :---- | :------------------ | :-------- | :--------------- |
+| ACCESS SHARE            | -            | -         | -             | -                      | -     | -                   | -         | X                |
+| ROW SHARE               | -            | -         | -             | -                      | -     | -                   | X         | X                |
+| ROW EXCLUSIVE           | -            | -         | -             | -                      | X     | X                   | X         | X                |
+| SHARE UPDATE EXCLUSIVE  | -            | -         | -             | X                      | X     | X                   | X         | X                |
+| SHARE                   | -            | -         | X             | X                      | -     | X                   | X         | X                |
+| SHARE ROW EXCLUSIVE     | -            | -         | X             | X                      | X     | X                   | X         | X                |
+| EXCLUSIVE               | -            | X         | X             | X                      | X     | X                   | X         | X                |
+| ACCESS EXCLUSIVE        | X            | X         | X             | X                      | X     | X                   | X         | X                |
+
+LOCK的参数说明如下所示：
+
+- **name**
+
+  要锁定的表的名称，可以有模式修饰。
+
+  LOCK TABLE命令中声明的表的顺序就是上锁的顺序。
+
+  取值范围: 已存在的表名。
+
+- **ONLY**
+
+  如果指定ONLY，只有该表被锁定。如果没有声明，该表和他的所有子表将都被锁定。
+
+- **ACCESS SHARE**
+
+  ACCESS锁只允许对表进行读取，而禁止对表进行修改。所有对表进行读取而不修改的SQL语句都会自动请求这种锁。例如，SELECT命令会自动在被引用的表上请求一个这种锁。
+
+- **ROW SHARE**
+
+  与EXCLUSIVE和ACCESS EXCLUSIVE锁模式冲突。
+
+  SELECT FOR UPDATE和SELECT FOR SHARE命令会自动在目标表上请求ROW SHARE锁（且所有被引用但不是FOR SHARE/FOR UPDATE的其他表上，还会自动加上ACCESS SHARE锁）。
+
+- **ROW EXCLUSIVE**
+
+  与ROW SHARE锁相同，ROW EXCLUSIVE允许并发读取表，但是禁止修改表中数据。UPDATE，DELETE，INSERT命令会自动在目标表上请求这个锁（且所有被引用的其他表上还会自动加上的ACCESS SHARE锁）。通常情况下，所有会修改表数据的命令都会请求表的ROW EXCLUSIVE锁。
+
+- **SHARE UPDATE EXCLUSIVE**
+
+  这个模式保护一个表的模式不被并发修改，以及禁止在目标表上执行垃圾回收命令（VACUUM ）。
+
+  VACUUM（不带FULL选项），ANALYZE，CREATE INDEX CONCURRENTLY命令会自动请求这样的锁。
+
+- **SHARE**
+
+  SHARE锁允许并发的查询，但是禁止对表进行修改。
+
+  CREATE INDEX（不带CONCURRENTLY选项）语句会自动请求这种锁。
+
+- **SHARE ROW EXCLUSIVE**
+
+  SHARE ROW EXCLUSIVE锁禁止对表进行任何的并发修改，而且是独占锁，因此一个会话中只能获取一次。
+
+  任何SQL语句都不会自动请求这个锁模式。
+
+- **EXCLUSIVE**
+
+  EXCLUSIVE锁允许对目标表进行并发查询，但是禁止任何其他操作。
+
+  这个模式只允许并发加ACCESS SHARE锁，也就是说，只有对表的读动作可以和持有这个锁模式的事务并发执行。
+
+  任何SQL语句都不会在用户表上自动请求这个锁模式。然而在某些操作的时候，会在某些系统表上请求它。
+
+- **ACCESS EXCLUSIVE**
+
+  这个模式保证其所有者（事务）是可以访问该表的唯一事务。
+
+  ALTER TABLE，DROP TABLE，TRUNCATE，REINDEX命令会自动请求这种锁。
+
+  在LOCK TABLE命令没有明确声明需要的锁模式时，它是缺省锁模式。
+
+- **NOWAIT**
+
+  声明LOCK TABLE不去等待任何冲突的锁释放，如果无法立即获取该锁，该命令退出并且发出一个错误信息。
+
+  在不指定NOWAIT的情况下获取表级锁时，如果有其他互斥锁存在的话，则等待其他锁的释放。
+
+## 示例
+
+```sql
+--在执行删除操作时对一个有主键的表进行 SHARE ROW EXCLUSIVE 锁。
+mogdb=# CREATE TABLE tpcds.reason_t1 AS TABLE tpcds.reason;
+
+mogdb=# START TRANSACTION;
+
+mogdb=# LOCK TABLE tpcds.reason_t1 IN SHARE ROW EXCLUSIVE MODE;
+
+mogdb=# DELETE FROM tpcds.reason_t1 WHERE r_reason_desc IN(SELECT r_reason_desc FROM tpcds.reason_t1 WHERE r_reason_sk < 6 );
+
+mogdb=# DELETE FROM tpcds.reason_t1 WHERE r_reason_sk = 7;
+
+mogdb=# COMMIT;
+
+--删除表tpcds.reason_t1。
+mogdb=# DROP TABLE tpcds.reason_t1;
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/111-MOVE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/111-MOVE.md
new file mode 100644
index 0000000000000000000000000000000000000000..62b62221e721f556ca1aed3c2f352b149340ecc0
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/111-MOVE.md
@@ -0,0 +1,81 @@
+---
+title: MOVE
+summary: MOVE
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# MOVE
+
+## 功能描述
+
+MOVE在不检索数据的情况下重新定位一个游标。MOVE的作用类似于FETCH命令，但只是重定位游标而不返回行。
+
+## 注意事项
+
+无。
+
+## 语法格式
+
+```ebnf+diagram
+Move ::= MOVE [ direction [ FROM | IN ] ] cursor_name;
+```
+
+其中direction子句为可选参数。
+
+```ebnf+diagram
+direction ::= NEXT
+   | PRIOR
+   | FIRST
+   | LAST
+   | ABSOLUTE count
+   | RELATIVE count
+   | count
+   | ALL
+   | FORWARD
+   | FORWARD count
+   | FORWARD ALL
+   | BACKWARD
+   | BACKWARD count
+   | BACKWARD ALL
+```
+
+## 参数说明
+
+MOVE命令的参数与FETCH的相同，详细请参见FETCH的参数说明。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+> 成功完成时，MOVE命令将返回一个“MOVE count”的标签，count是一个使用相同参数的FETCH命令会返回的行数（可能为零）。
+
+## 示例
+
+```sql
+--开始一个事务。
+mogdb=# START TRANSACTION;
+
+--定义一个名为cursor1的游标。
+mogdb=# CURSOR cursor1 FOR SELECT * FROM tpcds.reason;
+
+--忽略游标cursor1的前3行。
+mogdb=# MOVE FORWARD 3 FROM cursor1;
+
+--抓取游标cursor1的前4行。
+mogdb=# FETCH 4 FROM cursor1;
+ r_reason_sk |   r_reason_id    |                                            r_reason_desc
+-------------+------------------+------------------------------------------------------------------------------------------------------
+           4 | AAAAAAAAEAAAAAAA | Not the product that was ordred
+           5 | AAAAAAAAFAAAAAAA | Parts missing
+           6 | AAAAAAAAGAAAAAAA | Does not work with a product that I have
+           7 | AAAAAAAAHAAAAAAA | Gift exchange
+(4 rows)
+
+--关闭游标。
+mogdb=# CLOSE cursor1;
+
+--结束一个事务。
+mogdb=# END;
+```
+
+## 相关链接
+
+[CLOSE](36-CLOSE)，[FETCH](107-FETCH)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/112-MERGE-INTO.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/112-MERGE-INTO.md
new file mode 100644
index 0000000000000000000000000000000000000000..77a39fc93479fb7e47637b98b897c8e22a9f5e36
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/112-MERGE-INTO.md
@@ -0,0 +1,143 @@
+---
+title: MERGE INTO
+summary: MERGE INTO
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# MERGE INTO
+
+## 功能描述
+
+通过MERGE INTO语句，将目标表和源表中数据针对关联条件进行匹配，若关联条件匹配时对目标表进行UPDATE，无法匹配时对目标表执行INSERT。此语法可以很方便地用来合并执行UPDATE和INSERT，避免多次执行。
+
+## 注意事项
+
+进行MERGE INTO操作的用户需要同时拥有目标表的UPDATE和INSERT权限，以及源表的SELECT权限。
+
+## 语法格式
+
+```ebnf+diagram
+MergeInto ::= MERGE [/*+ plan_hint */] INTO table_name [ [ AS ] alias ]
+USING { { table_name | view_name } | subquery } [ [ AS ] alias ]
+ON ( condition )
+[
+  WHEN MATCHED THEN
+  UPDATE SET { column_name = { expression | DEFAULT } |
+          ( column_name [, ...] ) = ( { expression | DEFAULT } [, ...] ) } [, ...]
+  [ WHERE condition ]
+]
+[
+  WHEN NOT MATCHED THEN
+  INSERT { DEFAULT VALUES |
+  [ ( column_name [, ...] ) ] VALUES ( { expression | DEFAULT } [, ...] ) [, ...] [ WHERE condition ] }
+];
+```
+
+## 参数说明
+
+- **plan_hint子句**
+
+  以/\*+ \*/的形式在MERGE关键字后，用于对MERGE对应的语句块生成的计划进行hint调优，详细用法请参见章节[使用Plan Hint进行调优](9-hint-based-tuning)。每条语句中只有第一个/\*+ plan_hint \*/注释块会作为hint生效，里面可以写多条hint。
+
+- **INTO子句**
+
+  指定正在更新或插入的目标表。
+
+  - **table_name**
+
+  目标表的表名。
+
+  - **alias**
+
+    目标表的别名。
+
+    取值范围: 字符串，符合标识符命名规范。
+
+- **USING子句**
+
+  指定源表，源表可以为表、视图或子查询。
+
+- **ON子句**
+
+  关联条件，用于指定目标表和源表的关联条件。不支持更新关联条件中的字段。
+
+- **WHEN MATCHED子句**
+
+  当源表和目标表中数据针对关联条件可以匹配上时，选择WHEN MATCHED子句进行UPDATE操作。
+
+  不支持更新系统表、系统列。
+
+- **WHEN NOT MATCHED子句**
+
+  当源表和目标表中数据针对关联条件无法匹配时，选择WHEN NOT MATCHED子句进行INSERT操作。
+
+  不支持INSERT子句中包含多个VALUES。
+
+  WHEN MATCHED和WHEN NOT MATCHED子句顺序可以交换，可以缺省其中一个，但不能同时缺省，不支持同时指定两个WHEN MATCHED或WHEN NOT MATCHED子句。
+
+- **DEFAULT**
+
+  用对应字段的缺省值填充该字段。
+
+  如果没有缺省值，则为NULL。
+
+- **WHERE condition**
+
+  UPDATE子句和INSERT子句的条件，只有在条件满足时才进行更新操作，可缺省。不支持WHERE条件中引用系统列。
+
+## 示例
+
+```sql
+-- 创建目标表products和源表newproducts，并插入数据
+mogdb=# CREATE TABLE products
+(
+product_id INTEGER,
+product_name VARCHAR2(60),
+category VARCHAR2(60)
+);
+
+mogdb=# INSERT INTO products VALUES (1501, 'vivitar 35mm', 'electrncs');
+mogdb=# INSERT INTO products VALUES (1502, 'olympus is50', 'electrncs');
+mogdb=# INSERT INTO products VALUES (1600, 'play gym', 'toys');
+mogdb=# INSERT INTO products VALUES (1601, 'lamaze', 'toys');
+mogdb=# INSERT INTO products VALUES (1666, 'harry potter', 'dvd');
+
+mogdb=# CREATE TABLE newproducts
+(
+product_id INTEGER,
+product_name VARCHAR2(60),
+category VARCHAR2(60)
+);
+
+mogdb=# INSERT INTO newproducts VALUES (1502, 'olympus camera', 'electrncs');
+mogdb=# INSERT INTO newproducts VALUES (1601, 'lamaze', 'toys');
+mogdb=# INSERT INTO newproducts VALUES (1666, 'harry potter', 'toys');
+mogdb=# INSERT INTO newproducts VALUES (1700, 'wait interface', 'books');
+
+-- 进行MERGE INTO操作
+mogdb=# MERGE INTO products p
+USING newproducts np
+ON (p.product_id = np.product_id)
+WHEN MATCHED THEN
+  UPDATE SET p.product_name = np.product_name, p.category = np.category WHERE p.product_name != 'play gym'
+WHEN NOT MATCHED THEN
+  INSERT VALUES (np.product_id, np.product_name, np.category) WHERE np.category = 'books';
+MERGE 4
+
+-- 查询更新后的结果
+mogdb=# SELECT * FROM products ORDER BY product_id;
+ product_id |  product_name  | category
+------------+----------------+-----------
+       1501 | vivitar 35mm   | electrncs
+       1502 | olympus camera | electrncs
+       1600 | play gym       | toys
+       1601 | lamaze         | toys
+       1666 | harry potter   | toys
+       1700 | wait interface | books
+(6 rows)
+
+-- 删除表
+mogdb=# DROP TABLE products;
+mogdb=# DROP TABLE newproducts;
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/112.1-PREDICT-BY.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/112.1-PREDICT-BY.md
new file mode 100644
index 0000000000000000000000000000000000000000..4539575898e797c7985cf7f0e853aac03c9da290
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/112.1-PREDICT-BY.md
@@ -0,0 +1,47 @@
+---
+title: PREDICT BY
+summary: PREDICT BY
+author: Zhang Cuiping
+date: 2021-11-01
+---
+
+# PREDICT BY
+
+## 功能描述
+
+利用完成训练的模型进行推测任务。
+
+## 注意事项
+
+调用的模型名称在系统表gs_model_warehouse中可查看到。
+
+## 语法格式
+
+```ebnf+diagram
+PredictBy ::= PREDICT BY model_name [ (FEATURES attribute [, attribute] ) ];
+```
+
+## 参数说明
+
+- model_name
+
+  用于推测任务的模型名称。
+
+  取值范围: 字符串，需要符合标识符的命名规则。
+
+- attribute
+
+  推测任务的输入特征列名。
+
+  取值范围: 字符串，需要符合标识符的命名规则。
+
+## 示例
+
+```
+SELECT id, PREDICT BY price_model (FEATURES size,lot), price
+FROM houses;
+```
+
+## 相关链接
+
+[CREATE MODEL](50.3-CREATE-MODEL)，[DROP MODEL](84.3-DROP-MODEL)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/113-PREPARE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/113-PREPARE.md
new file mode 100644
index 0000000000000000000000000000000000000000..9304c5accf6cbac1ba11bb24b840eb153467094d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/113-PREPARE.md
@@ -0,0 +1,46 @@
+---
+title: PREPARE
+summary: PREPARE
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# PREPARE
+
+## 功能描述
+
+创建一个预备语句。
+
+预备语句是服务端的对象，可以用于优化性能。在执行PREPARE语句的时候，指定的查询被解析、分析、重写。当随后发出EXECUTE语句的时候，预备语句被规划和执行。这种设计避免了重复解析、分析工作。PREPARE语句创建后在整个数据库会话期间一直存在，一旦创建成功，即便是在事务块中创建，事务回滚，PREPARE也不会删除。只能通过显式调用DEALLOCATE进行删除，会话结束时，PREPARE也会自动删除。
+
+## 注意事项
+
+无。
+
+## 语法格式
+
+```ebnf+diagram
+Prepare ::= PREPARE name [ ( data_type [, ...] ) ] AS statement;
+```
+
+## 参数说明
+
+- **name**
+
+  指定预备语句的名称。它必须在该会话中是唯一的。
+
+- **data_type**
+
+  参数的数据类型。
+
+- **statement**
+
+  是SELECT INSERT、UPDATE、DELETE、MERGE INTO或VALUES语句之一。
+
+## 示例
+
+请参见EXECUTE的示例。
+
+## 相关链接
+
+[DEALLOCATE](72-DEALLOCATE)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/114-PREPARE-TRANSACTION.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/114-PREPARE-TRANSACTION.md
new file mode 100644
index 0000000000000000000000000000000000000000..127268c2c9e5e9415e8fa2048110d181cf7c68d7
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/114-PREPARE-TRANSACTION.md
@@ -0,0 +1,43 @@
+---
+title: PREPARE TRANSACTION
+summary: PREPARE TRANSACTION
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# PREPARE TRANSACTION
+
+## 功能描述
+
+为当前事务做两阶段提交的准备。
+
+在命令之后，事务就不再和当前会话关联了；它的状态完全保存在磁盘上，它被提交成功的可能性非常高，即使是在请求提交之前数据库发生了崩溃也如此。
+
+一旦准备好了，一个事务就可以在稍后用COMMIT PREPARED或 ROLLBACK PREPARED命令分别进行提交或者回滚。这些命令可以从任何会话中发出，而不光是最初执行事务的那个会话。
+
+从发出命令的会话的角度来看，PREPARE TRANSACTION不同于ROLLBACK：在执行它之后，就不再有活跃的当前事务了，并且预备事务的效果无法见到（在事务提交的时候其效果会再次可见）。
+
+如果PREPARE TRANSACTION因为某些原因失败，那么它就会变成一个ROLLBACK，当前事务被取消。
+
+## 注意事项
+
+- 事务功能由数据库自动维护，不应显式使用事务功能。
+- 在运行PREPARE TRANSACTION命令时，必须在postgresql.conf配置文件中增大max_prepared_transactions的数值。建议至少将其设置为等于max_connections，这样每个会话都可以有一个等待中的预备事务。
+
+## 语法格式
+
+```ebnf+diagram
+PrepareTransaction ::= PREPARE TRANSACTION transaction_id;
+```
+
+## 参数说明
+
+**transaction_id**
+
+待提交事务的标识符，用于后面在COMMIT PREPARED或ROLLBACK PREPARED的时候标识这个事务。它不能和任何当前预备事务已经使用了的标识符同名。
+
+取值范围: 标识符必须以字符串文本的方式书写，并且必须小于200字节长。
+
+## 相关链接
+
+[COMMIT PREPARED](40-COMMIT-PREPARED)，[ROLLBACK PREPARED](122-ROLLBACK-PREPARED)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/114.1-PURGE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/114.1-PURGE.md
new file mode 100644
index 0000000000000000000000000000000000000000..b73bbaa678a1859921bfd813fcb8d3603de79e9b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/114.1-PURGE.md
@@ -0,0 +1,108 @@
+---
+title: PURGE
+summary: PURGE
+author: Zhang Cuiping
+date: 2021-11-01
+---
+
+# PURGE
+
+## 功能描述
+
+使用PURGE语句可以实现如下功能：
+
+- 从回收站中清理表或索引，并释放对象相关的全部空间。
+- 清理回收站。
+- 清理回收站中指定表空间的对象
+
+## 注意事项
+
+- 清除（PURGE）操作支持：表（PURGE TABLE）、索引（PURGE INDEX）、回收站（PURGE RECYCLEBIN）、表空间（PURGE TABLESPACE）。
+- 执行PURGE操作的权限要求如下：
+  - PURGE TABLE：用户必须是表的所有者，且用户必须拥有表所在模式的USAGE权限，系统管理员默认拥有此权限。
+  - PURGE INDEX：用户必须是索引的所有者，用户必须拥有索引所在模式的USAGE权限，系统管理员默认拥有此权限。
+  - PURGE TABLESPACE：用户必须是表空间的所有者，用户必须拥有对象所在模式的USAGE权限，且普通用户只允许删除回收站中指定表空间下所有者为自己的表，系统管理员默认可以删除回收站中指定表空间下所有的对象。
+  - PURGE RECYCLEBIN：普通用户只能清理回收站中当前用户拥有的对象，且用户必须拥有对象所在模式的USAGE权限，系统管理员默认可以清理回收站所有对象。
+
+## 语法格式
+
+```ebnf+diagram
+Purge ::= PURGE { TABLE [schema_name'.']table_name
+        | INDEX index_name
+        | RECYCLEBIN
+      };
+```
+
+## 参数说明
+
+- _[ **schema_name.** ]_
+
+  模式名。
+
+- TABLE *[ schema_name. ] table_name*
+
+  清空回收站中指定的表。
+
+- INDEX *index_name*
+
+  清空回收站中指定的索引。
+
+- RECYCLEBIN
+
+  清空回收站中的对象。
+
+## 示例
+
+```
+-- 创建表空间reason_table_space
+mogdb=#  CREATE TABLESPACE REASON_TABLE_SPACE1 owner tpcds RELATIVE location 'tablespace/tsp_reason1';
+-- 在表空间创建表tpcds.reason_t1
+mogdb=#  CREATE TABLE tpcds.reason_t1
+ (
+  r_reason_sk    integer,
+  r_reason_id    character(16),
+  r_reason_desc  character(100)
+  ) tablespace reason_table_space1;
+-- 在表空间创建表tpcds.reason_t2
+mogdb=#  CREATE TABLE tpcds.reason_t2
+ (
+  r_reason_sk    integer,
+  r_reason_id    character(16),
+  r_reason_desc  character(100)
+  ) tablespace reason_table_space1;
+-- 在表空间创建表tpcds.reason_t3
+mogdb=#  CREATE TABLE tpcds.reason_t3
+ (
+  r_reason_sk    integer,
+  r_reason_id    character(16),
+  r_reason_desc  character(100)
+  ) tablespace reason_table_space1;
+mogdb=#  CREATE TABLE tpcds.reason_t4
+ (
+  r_reason_sk    integer,
+  r_reason_id    character(16),
+  r_reason_desc  character(100)
+  );
+mogdb=#  DROP TABLE tpcds.reason_t1;
+mogdb=#  DROP TABLE tpcds.reason_t2;
+mogdb=#  DROP TABLE tpcds.reason_t3;
+mogdb=#  DROP TABLE tpcds.reason_t4;
+--查看回收站
+mogdb=#  SELECT rcyname,rcyoriginname,rcytablespace FROM GS_RECYCLEBIN;
+        rcyname        | rcyoriginname | rcytablespace
+-----------------------+---------------+---------------
+ BIN$16409$2CEE988==$0 | reason_t1     |         16408
+ BIN$16412$2CF2188==$0 | reason_t2     |         16408
+ BIN$16415$2CF2EC8==$0 | reason_t3     |         16408
+ BIN$16418$2CF3EC8==$0 | reason_t4     |             0
+(4 rows)
+--清空表
+mogdb=#  PURGE TABLE tpcds.reason_t1;
+mogdb=#  SELECT rcyname,rcyoriginname,rcytablespace FROM GS_RECYCLEBIN;
+        rcyname        | rcyoriginname | rcytablespace
+-----------------------+---------------+---------------
+ BIN$16412$2CF2188==$0 | reason_t2     |         16408
+ BIN$16415$2CF2EC8==$0 | reason_t3     |         16408
+ BIN$16418$2CF3EC8==$0 | reason_t4     |             0
+(3 rows)
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/115-REASSIGN-OWNED.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/115-REASSIGN-OWNED.md
new file mode 100644
index 0000000000000000000000000000000000000000..9e66cd3dca2c7cee3831449ab1cc918599d2e457
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/115-REASSIGN-OWNED.md
@@ -0,0 +1,39 @@
+---
+title: REASSIGN OWNED
+summary: REASSIGN OWNED
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# REASSIGN OWNED
+
+## 功能描述
+
+修改数据库对象的属主。
+
+REASSIGN OWNED要求系统将所有old_roles拥有的数据库对象的属主更改为new_role。
+
+## 注意事项
+
+- REASSIGN OWNED常用于在删除角色之前的准备工作。
+- 执行REASSIGN OWNED需要有原角色和目标角色上的权限。
+
+## 语法格式
+
+```ebnf+diagram
+ReassignOwned ::= REASSIGN OWNED BY old_role [, ...] TO new_role;
+```
+
+## 参数说明
+
+- **old_role**
+
+  旧属主的角色名。
+
+- **new_role**
+
+  将要成为这些对象属主的新角色的名称。
+
+## 示例
+
+无。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/115.1-REFRESH-INCREMENTAL-MATERIALIZED-VIEW.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/115.1-REFRESH-INCREMENTAL-MATERIALIZED-VIEW.md
new file mode 100644
index 0000000000000000000000000000000000000000..3303c8700af575f06d6791b7eb46fbac53467466
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/115.1-REFRESH-INCREMENTAL-MATERIALIZED-VIEW.md
@@ -0,0 +1,46 @@
+---
+title: REFRESH INCREMENTAL MATERIALIZED VIEW
+summary: REFRESH INCREMENTAL MATERIALIZED VIEW
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# REFRESH INCREMENTAL MATERIALIZED VIEW
+
+## 功能描述
+
+REFRESH INCREMENTAL MATERIALIZED VIEW会以增量刷新的方式对物化视图进行刷新。
+
+## 注意事项
+
+- 增量刷新仅支持增量物化视图。
+- 刷新物化视图需要当前用户拥有基表的SELECT权限。
+
+## 语法格式
+
+```ebnf+diagram
+RefreshIncrementalMaterializedView ::= REFRESH INCREMENTAL MATERIALIZED VIEW mv_name;
+```
+
+## 参数说明
+
+- **mv_name**
+
+  要刷新的物化视图的名称。
+
+## 示例
+
+```sql
+--创建一个普通表
+mogdb=# CREATE TABLE my_table (c1 int, c2 int);
+--创建增量物化视图
+mogdb=# CREATE INCREMENTAL MATERIALIZED VIEW my_imv AS SELECT * FROM my_table;
+--基表写入数据
+mogdb=# INSERT INTO my_table VALUES(1,1),(2,2);
+--对增量物化视图my_imv进行增量刷新
+mogdb=# REFRESH INCREMENTAL MATERIALIZED VIEW my_imv;
+```
+
+## 相关链接
+
+[ALTER MATERIALIZED VIEW](11-ALTER-MATERIALIZED-VIEW)，[CREATE INCREMENTAL MATERIALIZED VIEW](49.1-CREATE-INCREMENTAL-MATERIALIZED-VIEW)，[CREATE MATERIALIZED VIEW](51-CREATE-MATERIALIZED-VIEW)，[CREATE TABLE](60-CREATE-TABLE)， [DROP MATERIALIZED VIEW](85-DROP-MATERIALIZED-VIEW)，[REFRESH MATERIALIZED VIEW](116-REFRESH-MATERIALIZED-VIEW)
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/116-REFRESH-MATERIALIZED-VIEW.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/116-REFRESH-MATERIALIZED-VIEW.md
new file mode 100644
index 0000000000000000000000000000000000000000..1c3c1c08c538586618a517906114c430e5a48362
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/116-REFRESH-MATERIALIZED-VIEW.md
@@ -0,0 +1,50 @@
+---
+title: REFRESH MATERIALIZED VIEW
+summary: REFRESH MATERIALIZED VIEW
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# REFRESH MATERIALIZED VIEW
+
+## 功能描述
+
+REFRESH MATERIALIZED VIEW会以全量刷新的方式对物化视图进行刷新。
+
+## 注意事项
+
+- 全量刷新既可以对全量物化视图执行，也可以对增量物化视图执行。
+- 刷新物化视图需要当前用户拥有基表的SELECT权限。
+
+## 语法格式
+
+```ebnf+diagram
+RefreshMaterializedView ::= REFRESH MATERIALIZED VIEW mv_name;
+```
+
+## 参数说明
+
+- **mv_name**
+
+  要刷新的物化视图的名称。
+
+## 示例
+
+```
+--创建一个普通表
+mogdb=# CREATE TABLE my_table (c1 int, c2 int);
+--创建全量物化视图
+mogdb=# CREATE MATERIALIZED VIEW my_mv AS SELECT * FROM my_table;
+--创建增量物化视图
+mogdb=# CREATE INCREMENTAL MATERIALIZED VIEW my_imv AS SELECT * FROM my_table;
+--基表写入数据
+mogdb=# INSERT INTO my_table VALUES(1,1),(2,2);
+--对全量物化视图my_mv进行全量刷新
+mogdb=# REFRESH MATERIALIZED VIEW my_mv;
+--对增量物化视图my_imv进行全量刷新
+mogdb=# REFRESH MATERIALIZED VIEW my_imv;
+```
+
+## 相关链接
+
+[ALTER MATERIALIZED VIEW](11-ALTER-MATERIALIZED-VIEW)，[CREATE INCREMENTAL MATERIALIZED VIEW](49.1-CREATE-INCREMENTAL-MATERIALIZED-VIEW)， [CREATE MATERIALIZED VIEW](51-CREATE-MATERIALIZED-VIEW)，[CREATE TABLE](60-CREATE-TABLE)， [DROP MATERIALIZED VIEW](85-DROP-MATERIALIZED-VIEW)，[REFRESH INCREMENTAL MATERIALIZED VIEW](115.1-REFRESH-INCREMENTAL-MATERIALIZED-VIEW)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/117-REINDEX.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/117-REINDEX.md
new file mode 100644
index 0000000000000000000000000000000000000000..8909d872f4e0f7028b793ed5d911afeeaa864597
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/117-REINDEX.md
@@ -0,0 +1,143 @@
+---
+title: REINDEX
+summary: REINDEX
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# REINDEX
+
+## 功能描述
+
+为表中的数据重建索引。
+
+在以下几种情况下需要使用REINDEX重建索引：
+
+- 索引崩溃，并且不再包含有效的数据。
+- 索引变得“臃肿”，包含大量的空页或接近空页。
+- 为索引更改了存储参数（例如填充因子），并且希望这个更改完全生效。
+- 使用CONCURRENTLY选项创建索引失败，留下了一个“非法”索引。
+
+## 注意事项
+
+REINDEX DATABASE和SYSTEM这种形式的重建索引不能在事务块中执行。
+
+## 语法格式
+
+- 重建普通索引。
+
+  ```ebnf+diagram
+  Reindex ::= REINDEX { INDEX  [ CONCURRENTLY ] | [INTERNAL] TABLE | DATABASE | SYSTEM } name [ FORCE ];
+  ```
+
+- 重建索引分区。
+
+  ```ebnf+diagram
+  Reindex ::= REINDEX  { INDEX|  [INTERNAL] TABLE} name
+      PARTITION partition_name [ FORCE  ];
+  ```
+
+## 参数说明
+
+- **INDEX**
+
+  重新建立指定的索引。
+
+- **CONCURRENTLY** <a id = 'CONCURRENTLY'> </a>
+
+  以不阻塞DML语句执行的方式重建索引。
+
+- **INTERNAL TABLE**
+
+  重建列存表或Hadoop内表的Desc表的索引，如果表有从属的“TOAST”表，则这个表也会重建索引。
+
+- **TABLE**
+
+  重新建立指定表的所有索引，如果表有从属的“TOAST”表，则这个表也会重建索引。如果表上有索引已经被alter unusable失效，则这个索引无法被重新创建。
+
+- **DATABASE**
+
+  重建当前数据库里的所有索引。
+
+- **SYSTEM**
+
+  在当前数据库上重建所有系统表上的索引。不会处理在用户表上的索引。
+
+- **name**
+
+  需要重建索引的索引、表、数据库的名称。表和索引可以有模式修饰。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  > REINDEX DATABASE和SYSTEM只能重建当前数据库的索引，所以name必须和当前数据库名称相同。
+
+- **FORCE**
+
+  无效选项，会被忽略。
+
+- **partition_name**
+
+  需要重建索引的分区的名称或者索引分区的名称。
+
+  取值范围:
+
+  - 如果前面是REINDEX INDEX，则这里应该指定索引分区的名称；
+  - 如果前面是REINDEX TABLE，则这里应该指定分区的名称；
+  - 如果前面是REINDEX INTERNAL TABLE，则这里应该指定列存分区表的分区的名称。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+> REINDEX DATABASE和SYSTEM这种形式的重建索引不能在事务块中执行。
+
+## 示例
+
+```sql
+--创建一个行存表tpcds.customer_t1，并在tpcds.customer_t1表上的c_customer_sk字段创建索引。
+mogdb=# CREATE TABLE tpcds.customer_t1
+(
+    c_customer_sk             integer               not null,
+    c_customer_id             char(16)              not null,
+    c_current_cdemo_sk        integer                       ,
+    c_current_hdemo_sk        integer                       ,
+    c_current_addr_sk         integer                       ,
+    c_first_shipto_date_sk    integer                       ,
+    c_first_sales_date_sk     integer                       ,
+    c_salutation              char(10)                      ,
+    c_first_name              char(20)                      ,
+    c_last_name               char(30)                      ,
+    c_preferred_cust_flag     char(1)                       ,
+    c_birth_day               integer                       ,
+    c_birth_month             integer                       ,
+    c_birth_year              integer                       ,
+    c_birth_country           varchar(20)                   ,
+    c_login                   char(13)                      ,
+    c_email_address           char(50)                      ,
+    c_last_review_date        char(10)
+)
+WITH (orientation = row);
+
+mogdb=# CREATE INDEX tpcds_customer_index1 ON tpcds.customer_t1 (c_customer_sk);
+
+mogdb=# INSERT INTO tpcds.customer_t1 SELECT * FROM tpcds.customer WHERE c_customer_sk < 10;
+
+--重建一个单独索引。
+mogdb=# REINDEX INDEX tpcds.tpcds_customer_index1;
+
+--重建表tpcds.customer_t1上的所有索引。
+mogdb=# REINDEX TABLE tpcds.customer_t1;
+
+--删除tpcds.customer_t1表。
+mogdb=# DROP TABLE tpcds.customer_t1;
+```
+
+## 优化建议
+
+- INTERNAL TABLE
+
+  此种情况大多用于故障恢复，不建议进行并发操作。
+
+- DATABASE
+
+  不能在事务中reindex database。
+
+- SYSTEM
+
+  不能在事务中reindex系统表。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/118-RELEASE-SAVEPOINT.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/118-RELEASE-SAVEPOINT.md
new file mode 100644
index 0000000000000000000000000000000000000000..37e60a846c0687fcceb0298d4bf4942d9c658db9
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/118-RELEASE-SAVEPOINT.md
@@ -0,0 +1,69 @@
+---
+title: RELEASE SAVEPOINT
+summary: RELEASE SAVEPOINT
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# RELEASE SAVEPOINT
+
+## 功能描述
+
+RELEASE SAVEPOINT删除一个当前事务先前定义的保存点。
+
+把一个保存点删除就令其无法作为回滚点使用，除此之外它没有其它用户可见的行为。它并不能撤销在保存点建立起来之后执行的命令的影响。要撤销那些命令可以使用ROLLBACK TO SAVEPOINT 。在不再需要的时候删除一个保存点可以令系统在事务结束之前提前回收一些资源。
+
+RELEASE SAVEPOINT也删除所有在指定的保存点建立之后的所有保存点。
+
+## 注意事项
+
+- 不能RELEASE一个没有定义的保存点，语法上会报错。
+- 如果事务在回滚状态，则不能释放保存点。
+- 如果多个保存点拥有同样的名称，只有最近定义的那个才被释放。
+
+## 语法格式
+
+```ebnf+diagram
+ReleaseSavepoint ::= RELEASE [ SAVEPOINT ] savepoint_name;
+```
+
+## 参数说明
+
+**savepoint_name**
+
+要删除的保存点的名称
+
+## 示例
+
+```sql
+--创建一个新表。
+mogdb=# CREATE TABLE tpcds.table1(a int);
+
+--开启事务。
+mogdb=# START TRANSACTION;
+
+--插入数据。
+mogdb=# INSERT INTO tpcds.table1 VALUES (3);
+
+--建立保存点。
+mogdb=# SAVEPOINT my_savepoint;
+
+--插入数据。
+mogdb=# INSERT INTO tpcds.table1 VALUES (4);
+
+--删除保存点。
+mogdb=# RELEASE SAVEPOINT my_savepoint;
+
+--提交事务。
+mogdb=# COMMIT;
+
+--查询表的内容，会同时看到3和4。
+mogdb=# SELECT * FROM tpcds.table1;
+
+--删除表。
+mogdb=# DROP TABLE tpcds.table1;
+```
+
+## 相关链接
+
+[SAVEPOINT](124-SAVEPOINT)，[ROLLBACK TO SAVEPOINT](123-ROLLBACK-TO-SAVEPOINT)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/119-RESET.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/119-RESET.md
new file mode 100644
index 0000000000000000000000000000000000000000..17151512727d5d149757aa14246cc1cb6d2fdfcd
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/119-RESET.md
@@ -0,0 +1,68 @@
+---
+title: RESET
+summary: RESET
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# RESET
+
+## 功能描述
+
+RESET将指定的运行时参数恢复为缺省值。这些参数的缺省值是指postgresql.conf配置文件中所描述的参数缺省值。
+
+RESET命令与如下命令的作用相同：
+
+SET configuration_parameter TO DEFAULT
+
+## 注意事项
+
+RESET的事务性行为和SET相同：它的影响将会被事务回滚撤销。
+
+## 语法格式
+
+```ebnf+diagram
+Reset ::= RESET {configuration_parameter | CURRENT_SCHEMA | TIME ZONE | TRANSACTION ISOLATION LEVEL | SESSION AUTHORIZATION | ALL };
+```
+
+## 参数说明
+
+- **configuration_parameter**
+
+  运行时参数的名称。
+
+  取值范围: 可以使用SHOW ALL命令查看运行时参数。
+
+- **CURRENT_SCHEMA**
+
+  当前模式
+
+- **TIME ZONE**
+
+  时区。
+
+- **TRANSACTION ISOLATION LEVEL**
+
+  事务的隔离级别。
+
+- **SESSION AUTHORIZATION**
+
+  当前会话的用户标识符。
+
+- **ALL**
+
+  所有运行时参数。
+
+## 示例
+
+```
+--把timezone设为缺省值。
+mogdb=# RESET timezone;
+
+--把所有参数设置为缺省值。
+mogdb=# RESET ALL;
+```
+
+## 相关链接
+
+[SET](127-SET)，[SHOW](132-SHOW)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/12-ALTER-ROLE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/12-ALTER-ROLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..331c49544d00aa47995af2ee32288c2fa0c60679
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/12-ALTER-ROLE.md
@@ -0,0 +1,130 @@
+---
+title: ALTER ROLE
+summary: ALTER ROLE
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER ROLE
+
+## 功能描述
+
+修改角色属性。
+
+## 注意事项
+
+无。
+
+## 语法格式
+
+- 修改角色的权限。
+
+  ```ebnf+diagram
+  AlterRole ::= ALTER ROLE role_name [ [ WITH ] option [ ... ] ];
+  ```
+
+  其中权限项子句option为：
+
+  ```ebnf+diagram
+  option ::= {CREATEDB | NOCREATEDB}
+      | {CREATEROLE | NOCREATEROLE}
+      | {INHERIT | NOINHERIT}
+      | {AUDITADMIN | NOAUDITADMIN}
+      | {SYSADMIN | NOSYSADMIN}
+      | {USEFT | NOUSEFT}
+      | {LOGIN | NOLOGIN}
+      | {REPLICATION | NOREPLICATION}
+      | {INDEPENDENT | NOINDEPENDENT}
+      | {VCADMIN | NOVCADMIN}
+      | CONNECTION LIMIT connlimit
+      | [ ENCRYPTED | UNENCRYPTED ] PASSWORD 'password' [EXPIRED]
+      | [ ENCRYPTED | UNENCRYPTED ] IDENTIFIED BY 'password' [ REPLACE 'old_password' | EXPIRED ]
+      | [ ENCRYPTED | UNENCRYPTED ] PASSWORD { 'password' | DISABLE | EXPIRED }
+      | [ ENCRYPTED | UNENCRYPTED ] IDENTIFIED BY { 'password' [ REPLACE 'old_password' ] | DISABLE }
+      | VALID BEGIN 'timestamp'
+      | VALID UNTIL 'timestamp'
+      | RESOURCE POOL 'respool'
+      | PERM SPACE 'spacelimit'
+      | ACCOUNT { LOCK | UNLOCK }
+      | PGUSER
+  ```
+
+- 修改角色的名称。
+
+  ```ebnf+diagram
+  AlterRole ::= ALTER ROLE role_name
+      RENAME TO new_name;
+  ```
+
+- 设置角色的配置参数。
+
+  ```ebnf+diagram
+  AlterRole ::= ALTER ROLE role_name [ IN DATABASE database_name ]
+      SET configuration_parameter {{ TO | = } { value | DEFAULT } | FROM CURRENT};
+  ```
+
+- 重置角色的配置参数。
+
+  ```ebnf+diagram
+  AlterRole ::= ALTER ROLE role_name
+      [ IN DATABASE database_name ] RESET {configuration_parameter|ALL};
+  ```
+
+## 参数说明
+
+- **role_name**
+
+  现有角色名。
+
+  取值范围: 已存在的用户名。
+
+- **IN DATABASE database_name**
+
+  表示修改角色在指定数据库上的参数。
+
+- **SET configuration_parameter**
+
+  设置角色的参数。ALTER ROLE中修改的会话参数只针对指定的角色，且在下一次该角色启动的会话中有效。
+
+  取值范围:
+
+  configuration_parameter和value的取值请参见**SET**。
+
+  DEFAULT：表示清除configuration_parameter参数的值，configuration_parameter参数的值将继承本角色新产生的SESSION的默认值。
+
+  FROM CURRENT：取当前会话中的值设置为configuration_parameter参数的值。
+
+- **RESET configuration_parameter/ALL**
+
+  清除configuration_parameter参数的值。与SET configuration_parameter TO DEFAULT的效果相同。
+
+  取值范围: ALL表示清除所有参数的值。
+
+- **ACCOUNT LOCK | ACCOUNT UNLOCK**
+
+  - ACCOUNT LOCK：锁定帐户，禁止登录数据库。
+  - ACCOUNT UNLOCK：解锁帐户，允许登录数据库。
+
+- **PGUSER**
+
+  当前版本不允许修改角色的PGUSER属性
+
+- **PASSWORD/IDENTIFIED BY**'password'
+
+    重置或修改用户密码。除了初始用户外其他管理员或普通用户修改自己的密码需要输入正确的旧密码。只有初始用户、系统管理员（sysadmin）或拥有创建用户（CREATEROLE）权限的用户才可以重置普通用户密码，无需输入旧密码。初始用户可以重置系统管理员的密码，系统管理员不允许重置其他系统管理员的密码。
+
+- **EXPIRED**
+
+    设置密码失效。只有初始用户、系统管理员（sysadmin）或拥有创建用户（CREATEROLE）权限的用户才可以设置用户密码失效，其中系统管理员也可以设置自己或其他系统管理员密码失效。不允许设置初始用户密码失效。
+
+    密码失效的用户可以登录数据库但不能执行查询操作，只有修改密码或由管理员重置密码后才可以恢复正常查询操作。
+
+其他参数请参见[CREATE ROLE](54-CREATE-ROLE)的参数说明。
+
+## 示例
+
+请参见[CREATE ROLE](54-CREATE-ROLE)的示例。
+
+## 相关链接
+
+[CREATE ROLE](54-CREATE-ROLE)，[DROP ROLE](89-DROP-ROLE)，[SET](127-SET)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/120-REVOKE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/120-REVOKE.md
new file mode 100644
index 0000000000000000000000000000000000000000..a44f48cf38d421031b033175449050b48ebe1161
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/120-REVOKE.md
@@ -0,0 +1,248 @@
+---
+title: REVOKE
+summary: REVOKE
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# REVOKE
+
+## 功能描述
+
+REVOKE用于撤销一个或多个角色的权限。
+
+## 注意事项
+
+非对象所有者试图在对象上REVOKE权限，命令按照以下规则执行：
+
+- 如果授权用户没有该对象上的权限，则命令立即失败。
+- 如果授权用户有部分权限，则只撤销那些有授权选项的权限。
+- 如果授权用户没有授权选项，REVOKE ALL PRIVILEGES形式将发出一个错误信息，而对于其他形式的命令而言，如果是命令中指定名称的权限没有相应的授权选项，该命令将发出一个警告。
+- 不允许对表分区进行REVOKE操作，对分区表进行REVOKE操作会引起告警。
+
+## 语法格式
+
+- 回收指定表或视图上权限。
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+      { { SELECT | INSERT | UPDATE | DELETE | TRUNCATE | REFERENCES | ALTER | DROP | COMMENT | INDEX | VACUUM }[, ...]
+      | ALL [ PRIVILEGES ] }
+      ON { [ TABLE ] table_name [, ...]
+         | ALL TABLES IN SCHEMA schema_name [, ...] }
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT ];
+  ```
+
+- 回收表上指定字段权限。
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+      { {{ SELECT | INSERT | UPDATE | REFERENCES | COMMENT } ( column_name [, ...] )}[, ...]
+      | ALL [ PRIVILEGES ] ( column_name [, ...] ) }
+      ON [ TABLE ] table_name [, ...]
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT ];
+  ```
+
+- 回收指定序列上权限。
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+      { { SELECT | UPDATE | ALTER | DROP | COMMENT }[, ...]
+      | ALL [ PRIVILEGES ] }
+      ON { [  SEQUENCE ] sequence_name [, ...]
+         | ALL SEQUENCES IN SCHEMA schema_name [, ...] }
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT ];
+  ```
+
+- 回收指定数据库上权限。
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+      { { CREATE | CONNECT | TEMPORARY | TEMP | ALTER | DROP | COMMENT } [, ...]
+      | ALL [ PRIVILEGES ] }
+      ON DATABASE database_name [, ...]
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT ];
+  ```
+
+- 回收指定域上权限。
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+      { USAGE | ALL [ PRIVILEGES ] }
+      ON DOMAIN domain_name [, ...]
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT ];
+  ```
+
+- 回收指定客户端加密主密钥上的权限。
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+      { { USAGE | DROP } [, ...] | ALL [PRIVILEGES] }
+      ON CLIENT_MASTER_KEYS client_master_keys_name [, ...]
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT ];
+  ```
+
+- 回收指定列加密密钥上的权限。
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+      { { USAGE | DROP } [, ...] | ALL [PRIVILEGES]}
+      ON COLUMN_ENCRYPTION_KEYS column_encryption_keys_name [, ...]
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT ];
+  ```
+
+- 回收指定目录上权限。
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+      { { READ | WRITE | ALTER |DROP } [, ...] | ALL [ PRIVILEGES ] }
+      ON DIRECTORY directory_name [, ...]
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT ];
+  ```
+
+- 回收指定外部数据源上权限。
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+     { USAGE | ALL [ PRIVILEGES ] }
+      ON FOREIGN DATA WRAPPER fdw_name [, ...]
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT ];
+  ```
+
+- 回收指定外部服务器上权限。
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+      { { USAGE | ALTER | DROP | COMMENT } [, ...] | ALL [ PRIVILEGES ] }
+      ON FOREIGN SERVER server_name [, ...]
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT ];
+  ```
+
+- 回收指定函数上权限。
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+      { { EXECUTE | ALTER | DROP | COMMENT } [, ...] | ALL [ PRIVILEGES ] }
+      ON { FUNCTION {function_name ( [ {[ argmode ] [ arg_name ] arg_type} [, ...] ] )} [, ...]
+         | ALL FUNCTIONS IN SCHEMA schema_name [, ...] }
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT ];
+  ```
+
+- 回收指定过程语言上权限。
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+     { USAGE | ALL [ PRIVILEGES ] }
+      ON LANGUAGE lang_name [, ...]
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT ];
+  ```
+
+- 回收指定大对象上权限。
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+      { { SELECT | UPDATE } [, ...] | ALL [ PRIVILEGES ] }
+      ON LARGE OBJECT loid [, ...]
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT ];
+  ```
+
+- 回收指定模式上权限。
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+      { { CREATE | USAGE | ALTER | DROP | COMMENT } [, ...] | ALL [ PRIVILEGES ] }
+      ON SCHEMA schema_name [, ...]
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT ];
+  ```
+
+- 回收指定表空间上权限。
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+      { { CREATE | ALTER | DROP | COMMENT } [, ...] | ALL [ PRIVILEGES ] }
+      ON TABLESPACE tablespace_name [, ...]
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT ];
+  ```
+
+- 回收指定类型上权限。
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+     { { USAGE | ALTER | DROP | COMMENT } [, ...] | ALL [ PRIVILEGES ] }
+      ON TYPE type_name [, ...]
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT ];
+  ```
+
+- 回收Data Source对象上的权限。
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+     { USAGE | ALL [PRIVILEGES] }
+      ON DATA SOURCE src_name [, ...]
+      FROM {[GROUP] role_name | PUBLIC} [, ...]
+     [ CASCADE | RESTRICT ];
+  ```
+
+- 回收package对象的权限。
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ GRANT OPTION FOR ]
+     { { EXECUTE | ALTER | DROP | COMMENT } [, ...] | ALL [PRIVILEGES] }
+     ON PACKAGE package_name [, ...]
+     FROM {[GROUP] role_name | PUBLIC} [, ...]
+     [ CASCADE | RESTRICT ];
+  ```
+
+- 按角色回收角色上的权限。
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE [ ADMIN OPTION FOR ]
+      role_name [, ...] FROM role_name [, ...]
+      [ CASCADE | RESTRICT ];
+  ```
+
+- 回收角色上的sysadmin权限。
+
+  ```ebnf+diagram
+  Revoke ::= REVOKE ALL { PRIVILEGES | PRIVILEGE } FROM role_name;
+  ```
+
+## 参数说明
+
+关键字PUBLIC表示一个隐式定义的拥有所有角色的组。
+
+权限类别和参数说明，请参见GRANT的参数说明。
+
+任何特定角色拥有的特权包括直接授予该角色的特权、从该角色作为其成员的角色中得到的权限以及授予给PUBLIC的权限。因此，从PUBLIC收回SELECT特权并不一定会意味着所有角色都会失去在该对象上的SELECT特权，那些直接被授予的或者通过另一个角色被授予的角色仍然会拥有它。类似地，从一个用户收回SELECT后，如果PUBLIC仍有SELECT权限，该用户还是可以使用SELECT。
+
+指定GRANT OPTION FOR时，只撤销对该权限授权的权力，而不撤销该权限本身。
+
+如用户A拥有某个表的UPDATE权限，及WITH GRANT OPTION选项，同时A把这个权限赋予了用户B，则用户B持有的权限称为依赖性权限。当用户A持有的权限或者授权选项被撤销时，必须声明CASCADE，将所有依赖性权限都撤销。
+
+一个用户只能撤销由它自己直接赋予的权限。例如，如果用户A被指定授权（WITH ADMIN OPTION）选项，且把一个权限赋予了用户B，然后用户B又赋予了用户C，则用户A不能直接将C的权限撤销。但是，用户A可以撤销用户B的授权选项，并且使用CASCADE。这样，用户C的权限就会自动被撤销。另外一个例子：如果A和B都赋予了C同样的权限，则A可以撤销他自己的授权选项，但是不能撤销B的，因此C仍然拥有该权限。
+
+如果执行REVOKE的角色持有的权限是通过多层成员关系获得的，则具体是哪个包含的角色执行的该命令是不确定的。在这种场合下，最好的方法是使用SET ROLE成为特定角色，然后执行REVOKE，否则可能导致删除了不想删除的权限，或者是任何权限都没有删除。
+
+## 示例
+
+请参考GRANT的示例。
+
+## 相关链接
+
+[GRANT](108-GRANT)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/121-ROLLBACK.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/121-ROLLBACK.md
new file mode 100644
index 0000000000000000000000000000000000000000..6283569cec2ea65d6af576aed6e33c95c8f9a348
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/121-ROLLBACK.md
@@ -0,0 +1,44 @@
+---
+title: ROLLBACK
+summary: ROLLBACK
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# ROLLBACK
+
+## 功能描述
+
+回滚当前事务并取消当前事务中的所有更新。
+
+在事务运行的过程中发生了某种故障，事务不能继续执行，系统将事务中对数据库的所有已完成的操作全部撤销，数据库状态回到事务开始时。
+
+## 注意事项
+
+如果不在一个事务内部发出ROLLBACK不会有问题，但是将抛出一个NOTICE信息。
+
+## 语法格式
+
+```ebnf+diagram
+Rollback ::= ROLLBACK [ WORK | TRANSACTION ];
+```
+
+## 参数说明
+
+**WORK | TRANSACTION**
+
+可选关键字。除了增加可读性，没有任何其他作用。
+
+## 示例
+
+```sql
+--开启一个事务
+mogdb=# START TRANSACTION;
+
+--取消所有更改
+mogdb=# ROLLBACK;
+```
+
+## 相关链接
+
+[COMMIT | END](39-COMMIT-END)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/122-ROLLBACK-PREPARED.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/122-ROLLBACK-PREPARED.md
new file mode 100644
index 0000000000000000000000000000000000000000..e416fd5e2874b0a97106e13cc29fcad5a6d8c043
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/122-ROLLBACK-PREPARED.md
@@ -0,0 +1,34 @@
+---
+title: ROLLBACK PREPARED
+summary: ROLLBACK PREPARED
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# ROLLBACK PREPARED
+
+## 功能描述
+
+取消一个先前为两阶段提交准备好的事务。
+
+## 注意事项
+
+- 该功能仅在维护模式（GUC参数xc_maintenance_mode为on时）下可用。该模式谨慎打开，一般供维护人员排查问题使用，一般用户不应使用该模式。
+- 要想回滚一个预备事务，必须是最初发起事务的用户，或者是系统管理员。
+- 事务功能由数据库自动维护，不应显式使用事务功能。
+
+## 语法格式
+
+```ebnf+diagram
+RollbackPrepared ::= ROLLBACK PREPARED transaction_id ;
+```
+
+## 参数说明
+
+**transaction_id**
+
+待提交事务的标识符。它不能和任何当前预备事务已经使用了的标识符同名。
+
+## 相关链接
+
+[COMMIT PREPARED](40-COMMIT-PREPARED)，[PREPARE TRANSACTION](114-PREPARE-TRANSACTION)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/123-ROLLBACK-TO-SAVEPOINT.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/123-ROLLBACK-TO-SAVEPOINT.md
new file mode 100644
index 0000000000000000000000000000000000000000..313cac00134478a9b17d7db437fd6d28028bbd17
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/123-ROLLBACK-TO-SAVEPOINT.md
@@ -0,0 +1,59 @@
+---
+title: ROLLBACK TO SAVEPOINT
+summary: ROLLBACK TO SAVEPOINT
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# ROLLBACK TO SAVEPOINT
+
+## 功能描述
+
+ROLLBACK TO SAVEPOINT用于回滚到一个保存点，隐含地删除所有在该保存点之后建立的保存点。
+
+回滚所有指定保存点建立之后执行的命令。保存点仍然有效，并且需要时可以再次回滚到该点。
+
+## 注意事项
+
+- 不能回滚到一个未定义的保存点，语法上会报错。
+- 在保存点方面，游标有一些非事务性的行为。任何在保存点里打开的游标都会在回滚掉这个保存点之后关闭。如果一个前面打开了的游标在保存点里面，并且游标被一个FETCH命令影响，而这个保存点稍后回滚了，那么这个游标的位置仍然在FETCH让它指向的位置（也就是FETCH不会被回滚）。关闭一个游标的行为也不会被回滚给撤消掉。如果一个游标的操作导致事务回滚，那么这个游标就会置于不可执行状态，所以，尽管一个事务可以用ROLLBACK TO SAVEPOINT重新恢复，但是游标不能再使用了。
+- 使用ROLLBACK TO SAVEPOINT回滚到一个保存点。使用RELEASE SAVEPOINT删除一个保存点，但是保留该保存点建立后执行的命令的效果。
+
+## 语法格式
+
+```ebnf+diagram
+RollbackToSavepoint ::= ROLLBACK [ WORK | TRANSACTION ] TO [ SAVEPOINT ] savepoint_name;
+```
+
+## 参数说明
+
+savepoint_name
+
+回滚截至的保存点
+
+## 示例
+
+```sql
+--撤销 my_savepoint 建立之后执行的命令的影响。
+mogdb=# START TRANSACTION;
+mogdb=# SAVEPOINT my_savepoint;
+mogdb=# ROLLBACK TO SAVEPOINT my_savepoint;
+--游标位置不受保存点回滚的影响。
+mogdb=# DECLARE foo CURSOR FOR SELECT 1 UNION SELECT 2;
+mogdb=# SAVEPOINT foo;
+mogdb=# FETCH 1 FROM foo;
+ ?column?
+----------
+        1
+mogdb=# ROLLBACK TO SAVEPOINT foo;
+mogdb=# FETCH 1 FROM foo;
+ ?column?
+----------
+        2
+mogdb=# RELEASE SAVEPOINT my_savepoint;
+mogdb=# COMMIT;
+```
+
+## 相关链接
+
+[SAVEPOINT](124-SAVEPOINT)，[RELEASE SAVEPOINT](118-RELEASE-SAVEPOINT)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/124-SAVEPOINT.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/124-SAVEPOINT.md
new file mode 100644
index 0000000000000000000000000000000000000000..20e2cfb43e30e1dffb0a87fb08a82c7490340c7d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/124-SAVEPOINT.md
@@ -0,0 +1,98 @@
+---
+title: SAVEPOINT
+summary: SAVEPOINT
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# SAVEPOINT
+
+## 功能描述
+
+SAVEPOINT用于在当前事务里建立一个新的保存点。
+
+保存点是事务中的一个特殊记号，它允许将那些在它建立后执行的命令全部回滚，把事务的状态恢复到保存点所在的时刻。
+
+## 注意事项
+
+- 使用ROLLBACK TO SAVEPOINT回滚到一个保存点。使用RELEASE SAVEPOINT删除一个保存点，但是保留该保存点建立后执行的命令的效果。
+- 保存点只能在一个事务块里面建立。在一个事务里面可以定义多个保存点。
+- 由于节点故障或者通信故障引起的节点线程或进程退出导致的报错，以及由于COPY FROM操作中源数据与目标表的表结构不一致导致的报错，均不能正常回滚到保存点之前，而是整个事务回滚。
+- SQL标准要求，使用savepoint建立一个同名保存点时，需要自动删除前面那个同名保存点。在MogDB数据库里，我们将保留旧的保存点，但是在回滚或者释放的时候，只使用最近的那个。释放了新的保存点将导致旧的再次成为ROLLBACK TO SAVEPOINT和RELEASE SAVEPOINT可以访问的保存点。除此之外，SAVEPOINT是完全符合SQL标准的。
+
+## 语法格式
+
+```ebnf+diagram
+Savepoint ::= SAVEPOINT savepoint_name;
+```
+
+## 参数说明
+
+savepoint_name
+
+新建保存点的名称。
+
+## 示例
+
+```sql
+--创建一个新表。
+mogdb=# CREATE TABLE table1(a int);
+
+--开启事务。
+mogdb=# START TRANSACTION;
+
+--插入数据。
+mogdb=# INSERT INTO table1 VALUES (1);
+
+--建立保存点。
+mogdb=# SAVEPOINT my_savepoint;
+
+--插入数据。
+mogdb=# INSERT INTO table1 VALUES (2);
+
+--回滚保存点。
+mogdb=# ROLLBACK TO SAVEPOINT my_savepoint;
+
+--插入数据。
+mogdb=# INSERT INTO table1 VALUES (3);
+
+--提交事务。
+mogdb=# COMMIT;
+
+--查询表的内容，会同时看到1和3,不能看到2，因为2被回滚。
+mogdb=# SELECT * FROM table1;
+
+--删除表。
+mogdb=# DROP TABLE table1;
+
+--创建一个新表。
+mogdb=# CREATE TABLE table2(a int);
+
+--开启事务。
+mogdb=# START TRANSACTION;
+
+--插入数据。
+mogdb=# INSERT INTO table2 VALUES (3);
+
+--建立保存点。
+mogdb=# SAVEPOINT my_savepoint;
+
+--插入数据。
+mogdb=# INSERT INTO table2 VALUES (4);
+
+--回滚保存点。
+mogdb=# RELEASE SAVEPOINT my_savepoint;
+
+--提交事务。
+mogdb=# COMMIT;
+
+--查询表的内容，会同时看到3和4。
+mogdb=# SELECT * FROM table2;
+
+--删除表。
+mogdb=# DROP TABLE table2;
+```
+
+## 相关链接
+
+[RELEASE SAVEPOINT](118-RELEASE-SAVEPOINT)，[ROLLBACK TO SAVEPOINT](123-ROLLBACK-TO-SAVEPOINT)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/125-SELECT.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/125-SELECT.md
new file mode 100644
index 0000000000000000000000000000000000000000..bb7a3be1083ab00ea78661ab87061d20837b640f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/125-SELECT.md
@@ -0,0 +1,653 @@
+---
+title: SELECT
+summary: SELECT
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# SELECT
+
+## 功能描述
+
+SELECT用于从表或视图中取出数据。
+
+SELECT语句就像叠加在数据库表上的过滤器，利用SQL关键字从数据表中过滤出用户需要的数据。
+
+## 注意事项
+
+- 必须对每个在SELECT命令中使用的字段有SELECT权限。
+- 使用FOR UPDATE或FOR SHARE还要求UPDATE权限。
+
+## 语法格式
+
+- 查询数据
+
+  ```ebnf+diagram
+  Select ::= [ WITH [ RECURSIVE ] with_query [, ...] ]
+  SELECT [/*+ plan_hint */] [ ALL | DISTINCT [ ON ( expression [, ...] ) ] ]
+  { * | {expression [ [ AS ] output_name ]} [, ...] }
+  [ FROM from_item [, ...] ]
+  [ WHERE condition ]
+  [ GROUP BY grouping_element [, ...] ]
+  [ HAVING condition [, ...] ]
+  [ WINDOW {window_name AS ( window_definition )} [, ...] ]
+  [ { UNION | INTERSECT | EXCEPT | MINUS } [ ALL | DISTINCT ] select ]
+  [ ORDER BY {expression [ [ ASC | DESC | USING operator ] | nlssort_expression_clause ] [ NULLS { FIRST | LAST } ]} [, ...] ]
+  [ LIMIT { [offset,] count | ALL } ]
+  [ OFFSET start [ ROW | ROWS ] ]
+  [ FETCH { FIRST | NEXT } [ count ] { ROW | ROWS } ONLY ]
+  [ {FOR { UPDATE | SHARE } [ OF table_name [, ...] ] [ NOWAIT ]} [...] ];
+  ```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> condition和expression中可以使用targetlist中表达式的别名。
+>
+> - 只能同一层引用。
+>
+> - 只能引用targetlist中的别名。
+> - 只能是后面的表达式引用前面的表达式。
+> - 不能包含volatile函数。
+> - 不能包含Window function函数。
+> - 不支持在join on条件中引用别名。
+> - targetlist中有多个要应用的别名则报错。
+
+- 其中子查询with_query为：
+
+  ```ebnf+diagram
+  with_query ::= with_query_name [ ( column_name [, ...] ) ]
+      AS ( {select | values | insert | update | delete} )
+  ```
+
+- 其中指定查询源from_item为：
+
+  ```ebnf+diagram
+  from_item ::= {[ ONLY ] table_name [ * ] [ partition_clause ] [ [ AS ] alias [ ( column_alias [, ...] ) ] ]
+  [ TABLESAMPLE sampling_method ( argument [, ...] ) [ REPEATABLE ( seed ) ] ]
+  [TIMECAPSULE {TIMESTAMP|CSN} expression]
+  |( select ) [ AS ] alias [ ( column_alias [, ...] ) ]
+  |with_query_name [ [ AS ] alias [ ( column_alias [, ...] ) ] ]
+  |function_name ( [ argument [, ...] ] ) [ AS ] alias [ ( column_alias [, ...] | column_definition [, ...] ) ]
+  |function_name ( [ argument [, ...] ] ) AS ( column_definition [, ...] )
+  |from_item [ NATURAL ] join_type from_item [ ON join_condition | USING ( join_column [, ...] ) ]};
+  ```
+
+- 其中group子句为：
+
+  ```ebnf+diagram
+    group ::= {
+    expression
+    | ( expression [, '...'] )
+    | ROLLUP ( { expression | ( expression [, '...'] ) } [, '...'] )
+    | CUBE ( { expression | ( expression [, '...'] ) } [, '...'] )
+    | GROUPING SETS ( grouping_element [, '...'] )};
+  ```
+
+- 其中指定分区partition_clause为：
+
+  ```ebnf+diagram
+  partition_clause ::= PARTITION { ( partition_name ) |
+          FOR (  partition_value [, ...] ) };
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 指定分区只适合普通表。
+
+- 其中设置排序方式nlssort_expression_clause为：
+
+  ```ebnf+diagram
+  nlssort_expression_clause ::= NLSSORT ( column_name, ' NLS_SORT = { SCHINESE_PINYIN_M | generic_m_ci } ' );
+  ```
+
+- 简化版查询语法，功能相当于select * from table_name。
+
+  ```ebnf+diagram
+  SimpleSelect ::= TABLE { ONLY {(table_name)| table_name} | table_name [ * ]};
+  ```
+
+## 参数说明
+
+- **WITH [ RECURSIVE ] with_query [, …]**
+
+    用于声明一个或多个可以在主查询中通过名称引用的子查询，相当于临时表。
+
+    如果声明了RECURSIVE，那么允许SELECT子查询通过名称引用它自己。
+
+    其中with_query的详细格式为：
+
+    ```sql
+    with_query_name [ ( column_name [, …] ) ] AS( {select | values | insert | update | delete} )
+    ```
+
+  - with_query_name指定子查询生成的结果集名称，在查询中可使用该名称访问子查询的结果集。
+  - column_name指定子查询结果集中显示的列名。
+  - 每个子查询可以是SELECT，VALUES，INSERT，UPDATE或DELETE语句。
+
+- **plan_hint子句**
+
+  以/\*+ \*/的形式在SELECT关键字后，用于对SELECT对应的语句块生成的计划进行hint调优，详细用法请参见章节[使用Plan Hint进行调优](9-hint-based-tuning)。每条语句中只有第一个/\*+ plan_hint \*/注释块会作为hint生效，里面可以写多条hint。
+
+- **ALL**
+
+  声明返回所有符合条件的行，是默认行为，可以省略该关键字。
+
+- **DISTINCT [ ON ( expression [, …] ) ]**
+
+  从SELECT的结果集中删除所有重复的行，使结果集中的每行都是唯一的。
+
+  ON ( expression [, …] ) 只保留那些在给出的表达式上运算出相同结果的行集合中的第一行。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** DISTINCT ON表达式是使用与ORDER BY相同的规则进行解释的。除非使用了ORDER BY来保证需要的行首先出现，否则，”第一行” 是不可预测的。
+
+- **SELECT列表**
+
+    指定查询表中列名，可以是部分列或者是全部（使用通配符*表示）。
+
+    通过使用子句AS output_name可以为输出字段取个别名，这个别名通常用于输出字段的显示。支持关键字name、value和type作为列别名。
+
+    列名可以用下面几种形式表达：
+
+  - 手动输入列名，多个列之间用英文逗号（,）分隔。
+  - 可以是FROM子句里面计算出来的字段。
+
+- **FROM子句**
+
+    为SELECT声明一个或者多个源表。
+
+    FROM子句涉及的元素如下所示。
+
+  - table_name
+
+    表名或视图名，名称前可加上模式名，如：schema_name.table_name。
+
+  - alias
+
+    给表或复杂的表引用起一个临时的表别名，以便被其余的查询引用。
+
+    别名用于缩写或者在自连接中消除歧义。如果提供了别名，它就会完全隐藏表的实际名称。
+
+  - TABLESAMPLE *sampling_method* ( *argument* [, …] ) [ REPEATABLE ( *seed* ) ]
+
+    table_name_之后的TABLESAMPLE子句表示应该用指定的_sampling_method_来检索表中行的子集。
+
+    可选的REPEATABLE子句指定一个用于产生采样方法中随机数的_种子_数。种子值可以是任何非空常量值。如果查询时表没有被更改，指定相同种子和_argument_值的两个查询将会选择该表相同的采样。但是不同的种子值通常将会产生不同的采样。如果没有给出REPEATABLE，则会基于一个系统产生的种子为每一个查询选择一个新的随机采样。
+
+  - TIMECAPSULE { TIMESTAMP | CSN } expression
+
+    查询指定CSN点或者指定时间点表的内容。
+
+    目前不支持闪回查询的表：系统表、列存表、内存表、DFS表、全局临时表、本地临时表、UNLOGGED表、分区表、视图、序列表、Hbkt表、共享表、继承表、带有PARTIAL CLUSTER KEY约束的表。
+
+    - TIMECAPSULE TIMESTAMP
+
+        关键字，闪回查询的标识，根据date日期，闪回查找指定时间点的结果集。date日期必须是一个过去有效的时间戳。
+
+    - TIMECAPSULE CSN
+
+        关键字，闪回查询的标识，根据表的CSN闪回查询指定CSN点的结果集。其中CSN可从gs_txn_snapshot记录的snpcsn号查得。
+
+        > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+        >
+        > - 闪回查询不能跨越影响表结构或物理存储的语句，否则会报错。即闪回点和当前点之间，如果执行过修改表结构或影响物理存储的语句（DDL、DCL、VACUUM FULL），则闪回失败，报错:“ERROR: The table definition of T1 has been changed.”。
+        > - 闪回点过旧时，因闪回版本被回收等导致无法获取旧版本会导致闪回失败，报错：Restore point too old。可通过将version_retention_age和vacuum_defer_cleanup_age设置成同值，配置闪回功能旧版本保留期限，取值范围是0~1000000，值为0表示VACUUM不会延迟清除无效的行存记录。
+        > - 通过时间方式指定闪回点，闪回数据和实际时间点最多偏差为3秒。
+
+  - column_alias
+
+    列别名
+
+  - PARTITION
+
+    查询分区表的某个分区的数据。
+
+  - partition_name
+
+    分区名。
+
+  - partition_value
+
+    指定的分区键值。在创建分区表时，如果指定了多个分区键，可以通过PARTITION FOR子句指定的这一组分区键的值，唯一确定一个分区。
+
+  - subquery
+
+    FROM子句中可以出现子查询，创建一个临时表保存子查询的输出。
+
+  - with_query_name
+
+    WITH子句同样可以作为FROM子句的源，可以通过WITH查询的名称对其进行引用。
+
+  - function_name
+
+    函数名称。函数调用也可以出现在FROM子句中。
+
+  - join_type
+
+    有5种类型，如下所示。
+
+    - [ INNER ] JOIN
+
+        一个JOIN子句组合两个FROM项。可使用圆括弧以决定嵌套的顺序。如果没有圆括弧，JOIN从左向右嵌套。
+
+        在任何情况下，JOIN都比逗号分隔的FROM项绑定得更紧。
+
+    - LEFT [ OUTER ] JOIN
+
+        返回笛卡尔积中所有符合连接条件的行，再加上左表中通过连接条件没有匹配到右表行的那些行。这样，左边的行将扩展为生成表的全长，方法是在那些右表对应的字段位置填上NULL。请注意，只在计算匹配的时候，才使用JOIN子句的条件，外层的条件是在计算完毕之后施加的。
+
+    - RIGHT [ OUTER ] JOIN
+
+        返回所有内连接的结果行，加上每个不匹配的右边行（左边用NULL扩展）。
+
+        这只是一个符号上的方便，因为总是可以把它转换成一个LEFT OUTER JOIN，只要把左边和右边的输入互换位置即可。
+
+    - FULL [ OUTER ] JOIN
+
+        返回所有内连接的结果行，加上每个不匹配的左边行（右边用NULL扩展），再加上每个不匹配的右边行（左边用NULL扩展）。
+
+    - CROSS JOIN
+
+        CROSS JOIN等效于INNER JOIN ON（TRUE） ，即没有被条件删除的行。这种连接类型只是符号上的方便，因为它们与简单的FROM和WHERE的效果相同。
+
+        > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 必须为INNER和OUTER连接类型声明一个连接条件，即NATURAL ON，join_condition，USING (join_column [， …]) 之一。但是它们不能出现在CROSS JOIN中。
+
+        其中CROSS JOIN和INNER JOIN生成一个简单的笛卡尔积，和在FROM的顶层列出两个项的结果相同。
+
+  - ON join_condition
+
+    连接条件，用于限定连接中的哪些行是匹配的。如：ON left_table.a = right_table.a。
+
+  - USING(join_column[，…])
+
+    ON left_table.a = right_table.a AND left_table.b = right_table.b … 的简写。要求对应的列必须同名。
+
+  - NATURAL
+
+    NATURAL是具有相同名称的两个表的所有列的USING列表的简写。
+
+  - from item
+
+    用于连接的查询源对象的名称。
+
+- **WHERE子句**
+
+  WHERE子句构成一个行选择表达式，用来缩小SELECT查询的范围。condition是返回值为布尔型的任意表达式，任何不满足该条件的行都不会被检索。
+
+  WHERE子句中可以通过指定”(+)“操作符的方法将表的连接关系转换为外连接。但是不建议用户使用这种用法，因为这并不是SQL的标准语法，在做平台迁移的时候可能面临语法兼容性的问题。同时，使用”(+)“有很多限制：
+
+  1. “(+)“只能出现在where子句中。
+  2. 如果from子句中已经有指定表连接关系，那么不能再在where子句中使用”(+)“。
+  3. “(+)“只能作用在表或者视图的列上，不能作用在表达式上。
+  4. 如果表A和表B有多个连接条件，那么必须在所有的连接条件中指定”(+)“，否则”(+)“将不会生效，表连接会转化成内连接，并且不给出任何提示信息。
+  5. “(+)“作用的连接条件中的表不能跨查询或者子查询。如果”(+)“作用的表，不在当前查询或者子查询的from子句中，则会报错。如果”(+)“作用的对端的表不存在，则不报错，同时连接关系会转化为内连接。
+  6. “(+)“作用的表达式不能直接通过”OR”连接。
+  7. 如果”(+)“作用的列是和一个常量的比较关系， 那么这个表达式会成为join条件的一部分。
+  8. 同一个表不能对应多个外表。
+  9. “(+)“只能出现”比较表达式”，”NOT表达式”，“ANY表达式”，“ALL表达式”，“IN表达式”，“NULLIF表达式”，“IS DISTINCT FROM表达式”，“IS OF”表达式。”(+)“不能出现在其他类型表达式中，并且这些表达式中不允许出现通过“AND”和“OR”连接的表达式。
+  10. “(+)“只能转化为左外连接或者右外连接，不能转化为全连接，即不能在一个表达式的两个表上同时指定”(+)“
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 对于WHERE子句的LIKE操作符，当LIKE中要查询特殊字符“%”、“_”、“\”的时候需要使用反斜杠“\”来进行转义。
+
+- **START WITH**
+
+  START WITH子句通常与CONNECT BY子句同时出现， 是一种递归语句对数据进行图遍历。START WITH代表递归的初始条数，CONNECT BY条件中可以对列指定PRIOR关键字。代表以这列为递归进行递归。当前约束只能对表中的列指定PRIOR，不支持对表达式、类型转换指定PRIOR关键字。
+
+- **GROUP BY子句**
+
+    将查询结果按某一列或多列的值分组，值相等的为一组。
+
+  - CUBE ( { expression | ( expression [, …] ) } [, …] )
+
+    CUBE是自动对group by子句中列出的字段进行分组汇总，结果集将包含维度列中各值的所有可能组合，以及与这些维度值组合相匹配的基础行中的聚合值。它会为每个分组返回一行汇总信息， 用户可以使用CUBE来产生交叉表值。比如，在CUBE子句中给出三个表达式（n = 3），运算结果为2n = 23 = 8组。 以n个表达式的值分组的行称为常规行，其余的行称为超级聚集行。
+
+  - GROUPING SETS ( grouping_element [, …] )
+
+    GROUPING SETS子句是GROUP BY子句的进一步扩展，它可以使用户指定多个GROUP BY选项。 这样做可以通过裁剪用户不需要的数据组来提高效率。 当用户指定了所需的数据组时，数据库不需要执行完整CUBE或ROLLUP生成的聚合集合。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 如果SELECT列表的表达式中引用了那些没有分组的字段，则会报错，除非使用了聚集函数，因为对于未分组的字段，可能返回多个数值。
+
+- **HAVING子句**
+
+  与GROUP BY子句配合用来选择特殊的组。HAVING子句将组的一些属性与一个常数值比较，只有满足HAVING子句中的逻辑表达式的组才会被提取出来。
+
+- **WINDOW子句**
+
+  一般形式为WINDOW window_name AS ( window_definition ) [， …]，window_name是可以被随后的窗口定义所引用的名称，window_definition可以是以下的形式：
+
+  ```
+  [ existing_window_name ]
+
+  [ PARTITION BY expression [, …] ]
+
+  [ ORDER BY expression [ ASC | DESC | USING operator ] [ NULLS { FIRST | LAST } ] [, …] ]
+
+  [ frame_clause ]
+  ```
+
+  frame_clause为窗函数定义一个窗口框架window frame，窗函数（并非所有）依赖于框架，window frame是当前查询行的一组相关行。frame_clause可以是以下的形式：
+
+  ```
+  [ RANGE | ROWS ] frame_start
+
+  [ RANGE | ROWS ] BETWEEN frame_start AND frame_end
+
+  frame_start和frame_end可以是：
+
+  UNBOUNDED PRECEDING
+
+  value PRECEDING
+
+  CURRENT ROW
+
+  value FOLLOWING
+
+  UNBOUNDED FOLLOWING
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 对列存表的查询目前只支持row_number窗口函数，不支持frame_clause。
+
+- **UNION子句**
+
+    UNION计算多个SELECT语句返回行集合的并集。
+
+    UNION子句有如下约束条件：
+
+  - 除非声明了ALL子句，否则缺省的UNION结果不包含重复的行。
+  - 同一个SELECT语句中的多个UNION操作符是从左向右计算的，除非用圆括弧进行了标识。
+  - FOR UPDATE不能在UNION的结果或输入中声明。
+
+    一般表达式：
+
+    select_statement UNION [ALL] select_statement
+
+  - select_statement可以是任何没有ORDER BY、LIMIT、FOR UPDATE子句的SELECT语句。
+  - 如果用圆括弧包围，ORDER BY和LIMIT可以附着在子表达式里。
+
+- **INTERSECT子句**
+
+    INTERSECT计算多个SELECT语句返回行集合的交集，不含重复的记录。
+
+    INTERSECT子句有如下约束条件：
+
+  - 同一个SELECT语句中的多个INTERSECT操作符是从左向右计算的，除非用圆括弧进行了标识。
+  - 当对多个SELECT语句的执行结果进行UNION和INTERSECT操作的时候，会优先处理INTERSECT。
+
+    一般形式：
+
+    select_statement INTERSECT select_statement
+
+    select_statement可以是任何没有FOR UPDATE子句的SELECT语句。
+
+- **EXCEPT子句**
+
+  EXCEPT子句有如下的通用形式：
+
+  select_statement EXCEPT [ ALL ] select_statement
+
+  select_statement是任何没有FOR UPDATE子句的SELECT表达式。
+
+  EXCEPT操作符计算存在于左边SELECT语句的输出而不存在于右边SELECT语句输出的行。
+
+  EXCEPT的结果不包含任何重复的行，除非声明了ALL选项。使用ALL时，一个在左边表中有m个重复而在右边表中有n个重复的行将在结果中出现max(m-n,0) 次。
+
+  除非用圆括弧指明顺序，否则同一个SELECT语句中的多个EXCEPT操作符是从左向右计算的。EXCEPT和UNION的绑定级别相同。
+
+  目前，不能给EXCEPT的结果或者任何EXCEPT的输入声明FOR UPDATE子句。
+
+- **MINUS子句**
+
+  与EXCEPT子句具有相同的功能和用法。
+
+- **ORDER BY子句**
+
+    对SELECT语句检索得到的数据进行升序或降序排序。对于ORDER BY表达式中包含多列的情况：
+
+  - 首先根据最左边的列进行排序，如果这一列的值相同，则根据下一个表达式进行比较，依此类推。
+  - 如果对于所有声明的表达式都相同，则按随机顺序返回。
+  - 在与DISTINCT关键字一起使用的情况下，ORDER BY中排序的列必须包括在SELECT语句所检索的结果集的列中。
+  - 在与GROUP BY子句一起使用的情况下，ORDER BY中排序的列必须包括在SELECT语句所检索的结果集的列中。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 如果要支持中文拼音排序，需要在初始化数据库时指定编码格式为UTF-8或GBK。 命令如下: initdb -E UTF8 -D ../data -locale=zh_CN.UTF-8或initdb -E GBK -D ../data -locale=zh_CN.GBK。
+
+- **LIMIT子句**
+
+  LIMIT子句由两个独立的子句组成：
+
+  LIMIT { count | ALL }
+
+  OFFSET start count声明返回的最大行数，而start声明开始返回行之前忽略的行数。如果两个都指定了，会在开始计算count个返回行之前先跳过start行。
+
+- **OFFSET子句**
+
+  SQL：2008开始提出一种不同的语法：
+
+  OFFSET start { ROW | ROWS }
+
+  start声明开始返回行之前忽略的行数。
+
+- **FETCH { FIRST | NEXT } [ count ] { ROW | ROWS } ONLY**
+
+  如果不指定count，默认值为1，FETCH子句限定返回查询结果从第一行开始的总行数。
+
+- **FOR UPDATE子句**
+
+  FOR UPDATE子句将对SELECT检索出来的行进行加锁。这样避免它们在当前事务结束前被其他事务修改或者删除，即其他企图UPDATE、 DELETE、 SELECT FOR UPDATE这些行的事务将被阻塞，直到当前事务结束。
+
+  为了避免操作等待其他事务提交，可使用NOWAIT选项，如果被选择的行不能立即被锁住，执行SELECT FOR UPDATE NOWAIT将会立即汇报一个错误，而不是等待。
+
+  FOR SHARE的行为类似，只是它在每个检索出来的行上要求一个共享锁，而不是一个排他锁。一个共享锁阻塞其它事务执行UPDATE、DELETE、SELECT，不阻塞SELECT FOR SHARE。
+
+  如果在FOR UPDATE或FOR SHARE中明确指定了表名称，则只有这些指定的表被锁定，其他在SELECT中使用的表将不会被锁定。否则，将锁定该命令中所有使用的表。
+
+  如果FOR UPDATE或FOR SHARE应用于一个视图或者子查询，它同样将锁定所有该视图或子查询中使用到的表。
+
+  多个FOR UPDATE和FOR SHARE子句可以用于为不同的表指定不同的锁定模式。
+
+  如果一个表中同时出现（或隐含同时出现）在FOR UPDATE和FOR SHARE子句中，则按照FOR UPDATE处理。类似的，如果影响一个表的任意子句中出现了NOWAIT，该表将按照NOWAIT处理。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 对列存表的查询不支持for update/share。
+
+- **NLS_SORT** <a id = 'nlssort'> </a>
+
+    指定某字段按照特殊方式排序。支持中文拼音格式排序和不区分大小写排序。支持GBK字符集生僻字按拼音排序。
+
+    取值范围:
+
+  - SCHINESE_PINYIN_M，按照中文拼音排序。如果要支持此排序方式，在创建数据库时需要指定编码格式为“UTF8”或“GBK”，否则排序无效。
+  - generic_m_ci，不区分大小写排序。
+
+- **PARTITION子句**
+
+  查询某个分区表中相应分区的数据。
+
+## 示例
+
+```sql
+--先通过子查询得到一张临时表temp_t，然后查询表temp_t中的所有数据。
+mogdb=# WITH temp_t(name,isdba) AS (SELECT usename,usesuper FROM pg_user) SELECT * FROM temp_t;
+
+--查询tpcds.reason表的所有r_reason_sk记录，且去除重复。
+mogdb=# SELECT DISTINCT(r_reason_sk) FROM tpcds.reason;
+
+--LIMIT子句示例：获取表中一条记录。
+mogdb=# SELECT * FROM tpcds.reason LIMIT 1;
+
+--查询所有记录，且按字母升序排列。
+mogdb=# SELECT r_reason_desc FROM tpcds.reason ORDER BY r_reason_desc;
+
+--通过表别名，从pg_user和pg_user_status这两张表中获取数据。
+mogdb=# SELECT a.usename,b.locktime FROM pg_user a,pg_user_status b WHERE a.usesysid=b.roloid;
+
+--FULL JOIN子句示例：将pg_user和pg_user_status这两张表的数据进行全连接显示，即数据的合集。
+mogdb=# SELECT a.usename,b.locktime,a.usesuper FROM pg_user a FULL JOIN pg_user_status b on a.usesysid=b.roloid;
+
+--GROUP BY子句示例：根据查询条件过滤，并对结果进行分组。
+mogdb=# SELECT r_reason_id, AVG(r_reason_sk) FROM tpcds.reason GROUP BY r_reason_id HAVING AVG(r_reason_sk) > 25;
+
+--GROUP BY CUBE子句示例：根据查询条件过滤，并对结果进行分组汇总。
+mogdb=# SELECT r_reason_id,AVG(r_reason_sk) FROM tpcds.reason GROUP BY CUBE(r_reason_id,r_reason_sk);
+
+--GROUP BY GROUPING SETS子句示例:根据查询条件过滤，并对结果进行分组汇总。
+mogdb=# SELECT r_reason_id,AVG(r_reason_sk) FROM tpcds.reason GROUP BY GROUPING SETS((r_reason_id,r_reason_sk),r_reason_sk);
+
+--UNION子句示例：将表tpcds.reason里r_reason_desc字段中的内容以W开头和以N开头的进行合并。
+mogdb=# SELECT r_reason_sk, tpcds.reason.r_reason_desc
+    FROM tpcds.reason
+    WHERE tpcds.reason.r_reason_desc LIKE 'W%'
+UNION
+SELECT r_reason_sk, tpcds.reason.r_reason_desc
+    FROM tpcds.reason
+    WHERE tpcds.reason.r_reason_desc LIKE 'N%';
+
+--NLS_SORT子句示例：中文拼音排序。
+mogdb=# SELECT * FROM tpcds.reason ORDER BY NLSSORT( r_reason_desc, 'NLS_SORT = SCHINESE_PINYIN_M');
+
+--不区分大小写排序:
+mogdb=# SELECT * FROM tpcds.reason ORDER BY NLSSORT( r_reason_desc, 'NLS_SORT = generic_m_ci');
+
+--创建分区表tpcds.reason_p
+mogdb=# CREATE TABLE tpcds.reason_p
+(
+  r_reason_sk integer,
+  r_reason_id character(16),
+  r_reason_desc character(100)
+)
+PARTITION BY RANGE (r_reason_sk)
+(
+  partition P_05_BEFORE values less than (05),
+  partition P_15 values less than (15),
+  partition P_25 values less than (25),
+  partition P_35 values less than (35),
+  partition P_45_AFTER values less than (MAXVALUE)
+)
+;
+
+--插入数据。
+mogdb=# INSERT INTO tpcds.reason_p values(3,'AAAAAAAABAAAAAAA','reason 1'),(10,'AAAAAAAABAAAAAAA','reason 2'),(4,'AAAAAAAABAAAAAAA','reason 3'),(10,'AAAAAAAABAAAAAAA','reason 4'),(10,'AAAAAAAABAAAAAAA','reason 5'),(20,'AAAAAAAACAAAAAAA','reason 6'),(30,'AAAAAAAACAAAAAAA','reason 7');
+
+--PARTITION子句示例：从tpcds.reason_p的表分区P_05_BEFORE中获取数据。
+mogdb=#  SELECT * FROM tpcds.reason_p PARTITION (P_05_BEFORE);
+ r_reason_sk |   r_reason_id    |   r_reason_desc
+-------------+------------------+------------------------------------
+           4 | AAAAAAAABAAAAAAA | reason 3
+           3 | AAAAAAAABAAAAAAA | reason 1
+(2 rows)
+
+--GROUP BY子句示例：按r_reason_id分组统计tpcds.reason_p表中的记录数。
+mogdb=# SELECT COUNT(*),r_reason_id FROM tpcds.reason_p GROUP BY r_reason_id;
+ count |   r_reason_id
+-------+------------------
+     2 | AAAAAAAACAAAAAAA
+     5 | AAAAAAAABAAAAAAA
+(2 rows)
+
+--GROUP BY CUBE子句示例：根据查询条件过滤，并对查询结果分组汇总。
+mogdb=# SELECT * FROM tpcds.reason GROUP BY  CUBE (r_reason_id,r_reason_sk,r_reason_desc);
+
+--GROUP BY GROUPING SETS子句示例：根据查询条件过滤，并对查询结果分组汇总。
+mogdb=# SELECT * FROM tpcds.reason GROUP BY  GROUPING SETS ((r_reason_id,r_reason_sk),r_reason_desc);
+
+--HAVING子句示例：按r_reason_id分组统计tpcds.reason_p表中的记录，并只显示r_reason_id个数大于2的信息。
+mogdb=# SELECT COUNT(*) c,r_reason_id FROM tpcds.reason_p GROUP BY r_reason_id HAVING c>2;
+ c |   r_reason_id
+---+------------------
+ 5 | AAAAAAAABAAAAAAA
+(1 row)
+
+--IN子句示例：按r_reason_id分组统计tpcds.reason_p表中的r_reason_id个数，并只显示r_reason_id值为 AAAAAAAABAAAAAAA或AAAAAAAADAAAAAAA的个数。
+mogdb=# SELECT COUNT(*),r_reason_id FROM tpcds.reason_p GROUP BY r_reason_id HAVING r_reason_id IN('AAAAAAAABAAAAAAA','AAAAAAAADAAAAAAA');
+count |   r_reason_id
+-------+------------------
+     5 | AAAAAAAABAAAAAAA
+(1 row)
+
+--INTERSECT子句示例：查询r_reason_id等于AAAAAAAABAAAAAAA，并且r_reason_sk小于5的信息。
+mogdb=# SELECT * FROM tpcds.reason_p WHERE r_reason_id='AAAAAAAABAAAAAAA' INTERSECT SELECT * FROM tpcds.reason_p WHERE r_reason_sk<5;
+ r_reason_sk |   r_reason_id    |     r_reason_desc
+-------------+------------------+------------------------------------
+           4 | AAAAAAAABAAAAAAA | reason 3
+           3 | AAAAAAAABAAAAAAA | reason 1
+(2 rows)
+
+--EXCEPT子句示例：查询r_reason_id等于AAAAAAAABAAAAAAA，并且去除r_reason_sk小于4的信息。
+mogdb=# SELECT * FROM tpcds.reason_p WHERE r_reason_id='AAAAAAAABAAAAAAA' EXCEPT SELECT * FROM tpcds.reason_p WHERE r_reason_sk<4;
+r_reason_sk |   r_reason_id    |      r_reason_desc
+-------------+------------------+------------------------------------
+          10 | AAAAAAAABAAAAAAA | reason 2
+          10 | AAAAAAAABAAAAAAA | reason 5
+          10 | AAAAAAAABAAAAAAA | reason 4
+           4 | AAAAAAAABAAAAAAA | reason 3
+(4 rows)
+
+--通过在where子句中指定"(+)"来实现左连接。
+mogdb=# select t1.sr_item_sk ,t2.c_customer_id from store_returns t1, customer t2 where t1.sr_customer_sk  = t2.c_customer_sk(+)
+order by 1 desc limit 1;
+ sr_item_sk | c_customer_id
+------------+---------------
+      18000 |
+(1 row)
+
+--通过在where子句中指定"(+)"来实现右连接。
+mogdb=# select t1.sr_item_sk ,t2.c_customer_id from store_returns t1, customer t2 where t1.sr_customer_sk(+)  = t2.c_customer_sk
+order by 1 desc limit 1;
+ sr_item_sk |  c_customer_id
+------------+------------------
+            | AAAAAAAAJNGEBAAA
+(1 row)
+
+--通过在where子句中指定"(+)"来实现左连接，并且增加连接条件。
+mogdb=# select t1.sr_item_sk ,t2.c_customer_id from store_returns t1, customer t2 where t1.sr_customer_sk  = t2.c_customer_sk(+) and t2.c_customer_sk(+) < 1 order by 1  limit 1;
+ sr_item_sk | c_customer_id
+------------+---------------
+          1 |
+(1 row)
+
+--不支持在where子句中指定"(+)"的同时使用内层嵌套AND/OR的表达式。
+mogdb=# select t1.sr_item_sk ,t2.c_customer_id from store_returns t1, customer t2 where not(t1.sr_customer_sk  = t2.c_customer_sk(+) and t2.c_customer_sk(+) < 1);
+ERROR:  Operator "(+)" can not be used in nesting expression.
+LINE 1: ...tomer_id from store_returns t1, customer t2 where not(t1.sr_...
+                                                             ^
+--where子句在不支持表达式宏指定"(+)"会报错。
+mogdb=# select t1.sr_item_sk ,t2.c_customer_id from store_returns t1, customer t2 where (t1.sr_customer_sk  = t2.c_customer_sk(+))::bool;
+ERROR:  Operator "(+)" can only be used in common expression.
+
+--where子句在表达式的两边都指定"(+)"会报错。
+mogdb=# select t1.sr_item_sk ,t2.c_customer_id from store_returns t1, customer t2 where t1.sr_customer_sk(+)  = t2.c_customer_sk(+);
+ERROR:  Operator "(+)" can't be specified on more than one relation in one join condition
+HINT:  "t1", "t2"...are specified Operator "(+)" in one condition.
+
+--删除表。
+mogdb=# DROP TABLE tpcds.reason_p;
+
+--闪回查询示例
+--创建表tpcds.time_table
+mogdb=#  create table tpcds.time_table(idx integer, snaptime timestamp, snapcsn bigint, timeDesc character(100));
+--向表tpcds.time_table中插入记录
+mogdb=#  INSERT INTO tpcds.time_table select 1, now(),int8in(xidout(next_csn)), 'time1' from gs_get_next_xid_csn();
+mogdb=#  INSERT INTO tpcds.time_table select 2, now(),int8in(xidout(next_csn)), 'time2' from gs_get_next_xid_csn();
+mogdb=#  INSERT INTO tpcds.time_table select 3, now(),int8in(xidout(next_csn)), 'time3' from gs_get_next_xid_csn();
+mogdb=#  INSERT INTO tpcds.time_table select 4, now(),int8in(xidout(next_csn)), 'time4' from gs_get_next_xid_csn();
+mogdb=#  select * from tpcds.time_table;
+
+ idx |          snaptime          | snapcsn |                                               timedesc
+-----+----------------------------+---------+------------------------------------------------------------------------------------------------------
+   1 | 2021-04-25 17:50:05.360326 |  107322 | time1
+   2 | 2021-04-25 17:50:10.886848 |  107324 | time2
+   3 | 2021-04-25 17:50:16.12921  |  107327 | time3
+   4 | 2021-04-25 17:50:22.311176 |  107330 | time4
+(4 rows)
+mogdb=#  delete tpcds.time_table;
+DELETE 4
+mogdb=#  SELECT * FROM tpcds.time_table TIMECAPSULE TIMESTAMP to_timestamp('2021-04-25 17:50:22.311176','YYYY-MM-DD HH24:MI:SS.FF');
+ idx |          snaptime          | snapcsn |                                               timedesc
+-----+----------------------------+---------+------------------------------------------------------------------------------------------------------
+   1 | 2021-04-25 17:50:05.360326 |  107322 | time1
+   2 | 2021-04-25 17:50:10.886848 |  107324 | time2
+   3 | 2021-04-25 17:50:16.12921  |  107327 | time3
+(3 rows)
+mogdb=#  SELECT * FROM tpcds.time_table TIMECAPSULE CSN 107330;
+ idx |          snaptime          | snapcsn |                                               timedesc
+-----+----------------------------+---------+------------------------------------------------------------------------------------------------------
+   1 | 2021-04-25 17:50:05.360326 |  107322 | time1
+   2 | 2021-04-25 17:50:10.886848 |  107324 | time2
+   3 | 2021-04-25 17:50:16.12921  |  107327 | time3
+(3 rows)
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/126-SELECT-INTO.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/126-SELECT-INTO.md
new file mode 100644
index 0000000000000000000000000000000000000000..e7058d3aec5ca18062a34248ee174c9faf8cb724
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/126-SELECT-INTO.md
@@ -0,0 +1,100 @@
+---
+title: SELECT INTO
+summary: SELECT INTO
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# SELECT INTO
+
+## 功能描述
+
+SELECT INTO用于根据查询结果创建一个新表，并且将查询到的数据插入到新表中。
+
+数据并不返回给客户端，这一点和普通的SELECT不同。新表的字段具有和SELECT的输出字段相同的名称和数据类型。
+
+## 注意事项
+
+CREATE TABLE AS的作用和SELECT INTO类似，且提供了SELECT INTO所提供功能的超集。建议使用CREATE TABLE AS语法替代SELECT INTO，因为SELECT INTO不能在存储过程中使用。
+
+## 语法格式
+
+```ebnf+diagram
+SelectInto ::= [ WITH [ RECURSIVE ] with_query [, ...] ]
+SELECT [ ALL | DISTINCT [ ON ( expression [, ...] ) ] ]
+    { * | {expression [ [ AS ] output_name ]} [, ...] }
+    INTO [ [ GLOBAL | LOCAL ] [ TEMPORARY | TEMP ] | UNLOGGED ] [ TABLE ] new_table
+    [ FROM from_item [, ...] ]
+    [ WHERE condition ]
+    [ GROUP BY expression [, ...] ]
+    [ HAVING condition [, ...] ]
+    [ WINDOW {window_name AS ( window_definition )} [, ...] ]
+    [ { UNION | INTERSECT | EXCEPT | MINUS } [ ALL | DISTINCT ] select ]
+    [ ORDER BY {expression [ [ ASC | DESC | USING operator ] | nlssort_expression_clause ] [ NULLS { FIRST | LAST } ]} [, ...] ]
+    [ LIMIT { count | ALL } ]
+    [ OFFSET start [ ROW | ROWS ] ]
+    [ FETCH { FIRST | NEXT } [ count ] { ROW | ROWS } ONLY ]
+    [ {FOR { UPDATE | SHARE } [ OF table_name [, ...] ] [ NOWAIT ]} [...] ];
+```
+
+## 参数说明
+
+**new_table**
+
+new_table指定新建表的名称。
+
+参数说明
+
+- **UNLOGGED**
+
+  指定表为非日志表。在非日志表中写入的数据不会被写入到预写日志中，这样就会比普通表快很多。但是，它也是不安全的，非日志表在冲突或异常关机后会被自动删截。非日志表中的内容也不会被复制到备用服务器中。在该类表中创建的索引也不会被自动记录。
+
+  - 使用场景：非日志表不能保证数据的安全性，用户应该在确保数据已经做好备份的前提下使用，例如系统升级时进行数据的备份。
+  - 故障处理：当异常关机等操作导致非日志表上的索引发生数据丢失时，用户应该对发生错误的索引进行重建。
+
+- **GLOBAL | LOCAL**
+
+  创建临时表时可以在TEMP或TEMPORARY前指定GLOBAL或LOCAL关键字。如果指定GLOBAL关键字，MogDB会创建全局临时表，否则MogDB会创建本地临时表。
+
+- **TEMPORARY | TEMP**
+
+  如果指定TEMP或TEMPORARY关键字，则创建的表为临时表。临时表分为全局临时表和本地临时表两种类型。创建临时表时如果指定GLOBAL关键字则为全局临时表，否则为本地临时表。
+
+  全局临时表的元数据对所有会话可见，会话结束后元数据继续存在。会话与会话之间的用户数据、索引和统计信息相互隔离，每个会话只能看到和更改自己提交的数据。全局临时表有两种模式：一种是基于会话级别的（ON COMMIT PRESERVE ROWS），当会话结束时自动清空用户数据；一种是基于事务级别的（ON COMMIT PRESERVE ROWS），当执行commit或rollback时自动清空用户数据。建表时如果没有指定ON COMMIT选项，则缺省为会话级别。与本地临时表不同，全局临时表建表时可以指定非pg_temp_开头的schema。
+
+  本地临时表只在当前会话可见，本会话结束后会自动删除。因此，在除当前会话连接的数据库节点故障时，仍然可以在当前会话上创建和使用临时表。由于临时表只在当前会话创建，对于涉及对临时表操作的DDL语句，会产生DDL失败的报错。因此，建议DDL语句中不要对临时表进行操作。TEMP和TEMPORARY等价。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+  >
+  > - 本地临时表通过每个会话独立的以pg_temp开头的schema来保证只对当前会话可见，因此，不建议用户在日常操作中手动删除以pg_temp，pg_toast_temp开头的schema。
+  > - 如果建表时不指定TEMPORARY/TEMP关键字，而指定表的schema为当前会话的pg_temp_开头的schema，则此表会被创建为临时表。
+  > - ALTER/DROP全局临时表和索引，如果其它会话正在使用它，禁止操作。
+  > - 全局临时表的DDL只会影响当前会话的用户数据和索引。例如truncate、reindex、analyze只对当前会话有效。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+> SELECT INTO的其它参数可参考SELECT的参数说明。
+
+## 示例
+
+```sql
+--将tpcds.reason表中r_reason_sk小于5的值加入到新建表中。
+mogdb=# SELECT * INTO tpcds.reason_t1 FROM tpcds.reason WHERE r_reason_sk < 5;
+INSERT 0 6
+s
+--删除tpcds.reason_t1表。
+mogdb=# DROP TABLE tpcds.reason_t1;
+```
+
+## 相关链接
+
+[SELECT](125-SELECT)
+
+## 优化建议
+
+- **DATABASE**
+
+  不建议在事务中reindex database。
+
+- **SYSTEM**
+
+  不建议在事务中reindex系统表。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/127-SET.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/127-SET.md
new file mode 100644
index 0000000000000000000000000000000000000000..eae68cc4f3fce21a1fa8ff40526995f3391b0331
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/127-SET.md
@@ -0,0 +1,122 @@
+---
+title: SET
+summary: SET
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# SET
+
+## 功能描述
+
+用于修改运行时配置参数。
+
+## 注意事项
+
+大多数运行时参数都可以用SET在运行时设置，但有些则在服务运行过程中或会话开始之后不能修改。
+
+## 语法格式
+
+- 设置所处的时区。
+
+  ```ebnf+diagram
+  Set ::= SET [ SESSION | LOCAL ] TIME ZONE { timezone | LOCAL | DEFAULT };
+  ```
+
+- 设置所属的模式。
+
+  ```ebnf+diagram
+  Set ::= SET [ SESSION | LOCAL ]
+      {CURRENT_SCHEMA { TO | = } { schema | DEFAULT }
+      | SCHEMA 'schema'};
+  ```
+
+- 设置客户端编码集。
+
+  ```ebnf+diagram
+  Set ::= SET [ SESSION | LOCAL ] NAMES encoding_name;
+  ```
+
+- 设置XML的解析方式。
+
+  ```ebnf+diagram
+  Set ::= SET [ SESSION | LOCAL ] XML OPTION { DOCUMENT | CONTENT };
+  ```
+
+- 设置其他运行时参数。
+
+  ```ebnf+diagram
+  Set ::= SET [ LOCAL | SESSION ]
+      { {config_parameter { { TO | = } { value | DEFAULT }
+                          | FROM CURRENT }}};
+  ```
+
+## 参数说明
+
+- **SESSION**
+
+  声明的参数只对当前会话起作用。如果SESSION和LOCAL都没出现，则SESSION为缺省值。
+
+  如果在事务中执行了此命令，命令的产生影响将在事务回滚之后消失。如果该事务已提交，影响将持续到会话的结束，除非被另外一个SET命令重置参数。
+
+- **LOCAL**
+
+  声明的参数只在当前事务中有效。在COMMIT或ROLLBACK之后，会话级别的设置将再次生效。
+
+  不论事务是否提交，此命令的影响只持续到当前事务结束。一个特例是：在一个事务里面，即有SET命令，又有SET LOCAL命令，且SET LOCAL在SET后面，则在事务结束之前，SET LOCAL命令会起作用，但事务提交之后，则是SET命令会生效。
+
+- **TIME ZONE timezone**
+
+  用于指定当前会话的本地时区。
+
+  取值范围: 有效的本地时区。该选项对应的运行时参数名称为TimeZone，DEFAULT缺省值为PRC。
+
+- **CURRENT_SCHEMA**
+
+  **schema**
+
+  CURRENT_SCHEMA用于指定当前的模式。
+
+  取值范围: 已存在模式名称。如果模式名不存在，会导致CURRENT_SCHEMA值为空。
+
+- **SCHEMA schema**
+
+  同CURRENT_SCHEMA。此处的schema是个字符串。
+
+  例如：set schema 'public';
+
+- **NAMES encoding_name**
+
+  用于设置客户端的字符编码。等价于set client_encoding to encoding_name。
+
+  取值范围: 有效的字符编码。该选项对应的运行时参数名称为client_encoding，默认编码为UTF8。
+
+- **XML OPTION option**
+
+  用于设置XML的解析方式。
+
+  取值范围: CONTENT（缺省）、DOCUMENT
+
+- **config_parameter**
+
+  可设置的运行时参数的名称。可用的运行时参数可以使用SHOW ALL命令查看。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 部分通过SHOW ALL查看的参数不能通过SET设置。如max_datanodes。
+
+- **value**
+
+  config_parameter的新值。可以声明为字符串常量、标识符、数字，或者逗号分隔的列表。DEFAULT用于把这些参数设置为它们的缺省值。
+
+## 示例
+
+```sql
+--设置模式搜索路径。
+mogdb=# SET search_path TO tpcds, public;
+
+--把日期时间风格设置为传统的 POSTGRES 风格(日在月前)。
+mogdb=# SET datestyle TO postgres，dym;
+```
+
+## 相关链接
+
+[RESET](119-RESET)，[SHOW](132-SHOW)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/128-SET-CONSTRAINTS.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/128-SET-CONSTRAINTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..aebb9bd0864e6f522b23fa4748a16a1a2a398662
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/128-SET-CONSTRAINTS.md
@@ -0,0 +1,59 @@
+---
+title: SET CONSTRAINTS
+summary: SET CONSTRAINTS
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# SET CONSTRAINTS
+
+## 功能描述
+
+SET CONSTRAINTS设置当前事务检查行为的约束条件。
+
+IMMEDIATE约束是在每条语句后面进行检查。DEFERRED约束一直到事务提交时才检查。每个约束都有自己的模式。
+
+从创建约束条件开始，一个约束总是设定为DEFERRABLE INITIALLY DEFERRED，DEFERRABLE INITIALLY IMMEDIATE，NOT DEFERRABLE三个特性之一。第三种总是IMMEDIATE，并且不会受SET CONSTRAINTS影响。前两种以指定的方式启动每个事务，但是其行为可以在事务里用SET CONSTRAINTS改变。
+
+带着一个约束名列表的SET CONSTRAINTS改变这些约束的模式（都必须是可推迟的）。如果有多个约束匹配某个名称，则所有都会被影响。SET CONSTRAINTS ALL改变所有可推迟约束的模式。
+
+当SET CONSTRAINTS把一个约束从DEFERRED改成IMMEDIATE的时候，新模式反作用式地起作用：任何将在事务结束准备进行的数据修改都将在SET CONSTRAINTS的时候执行检查。如果违反了任何约束，SET CONSTRAINTS都会失败（并且不会修改约束模式）。因此，SET CONSTRAINTS可以用于强制在事务中某一点进行约束检查。
+
+检查约束总是不可推迟的。
+
+## 注意事项
+
+SET CONSTRAINTS只在当前事务里设置约束的行为。因此，如果用户在事务块之外（START TRANSACTION/COMMIT对）执行这个命令，它将没有任何作用。
+
+## 语法格式
+
+```ebnf+diagram
+SetConstraints ::= SET CONSTRAINTS  { ALL  |  { name  }  [, ...]  }  { DEFERRED  | IMMEDIATE  } ;
+```
+
+## 参数说明
+
+- **name**
+
+  约束名。
+
+  取值范围: 已存在的约束名。可以在系统表pg_constraint中查到。
+
+- **ALL**
+
+  所有约束。
+
+- **DEFERRED**
+
+  约束一直到事务提交时才检查。
+
+- **IMMEDIATE**
+
+  约束在每条语句后进行检查。
+
+## 示例
+
+```sql
+--设置所有约束在事务提交时检查。
+mogdb=# SET CONSTRAINTS ALL DEFERRED;
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/129-SET-ROLE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/129-SET-ROLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..10da5298ff9afd8adba4435e4d74d578e31f1aea
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/129-SET-ROLE.md
@@ -0,0 +1,74 @@
+---
+title: SET ROLE
+summary: SET ROLE
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# SET ROLE
+
+## 功能描述
+
+设置当前会话的当前用户标识符。
+
+## 注意事项
+
+- 当前会话的用户必须是指定的rolename角色的成员，但系统管理员可以选择任何角色。
+- 使用这条命令，它可能会增加一个用户的权限，也可能会限制一个用户的权限。如果会话用户的角色有INHERITS属性，则它自动拥有它能SET ROLE变成的角色的所有权限；在这种情况下，SET ROLE实际上是删除了所有直接赋予会话用户的权限，以及它的所属角色的权限，只剩下指定角色的权限。另一方面，如果会话用户的角色有NOINHERITS属性，SET ROLE删除直接赋予会话用户的权限，而获取指定角色的权限。
+
+## 语法格式
+
+- 设置当前会话的当前用户标识符。
+
+  ```ebnf+diagram
+  SetRole ::= SET [ SESSION | LOCAL ] ROLE role_name PASSWORD 'password';
+  ```
+
+- 重置当前用户标识为当前会话用户标识符。
+
+  ```ebnf+diagram
+  ResetRole ::= RESET ROLE;
+  ```
+
+## 参数说明
+
+- **SESSION**
+
+  声明这个命令只对当前会话起作用，此参数为缺省值。
+
+- **LOCAL**
+
+  声明该命令只在当前事务中有效。
+
+- **role_name**
+
+  角色名。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- **password**
+
+  角色的密码。要求符合密码的命名规则。
+
+- **RESET ROLE**
+
+  用于重置当前用户标识。
+
+## 示例
+
+```sql
+--创建角色paul。
+mogdb=# CREATE ROLE paul IDENTIFIED BY 'Bigdata@123';
+
+--设置当前用户为paul。
+mogdb=# SET ROLE paul PASSWORD 'Bigdata@123';
+
+--查看当前会话用户，当前用户。
+mogdb=# SELECT SESSION_USER, CURRENT_USER;
+
+--重置当前用户。
+mogdb=# RESET role;
+
+--删除用户。
+mogdb=# DROP USER paul;
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/13-ALTER-ROW-LEVEL-SECURITY-POLICY.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/13-ALTER-ROW-LEVEL-SECURITY-POLICY.md
new file mode 100644
index 0000000000000000000000000000000000000000..634ae22a3b3eb7f21af1825ed35e9e6a0802fc37
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/13-ALTER-ROW-LEVEL-SECURITY-POLICY.md
@@ -0,0 +1,114 @@
+---
+title: ALTER ROW LEVEL SECURITY POLICY
+summary: ALTER ROW LEVEL SECURITY POLICY
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER ROW LEVEL SECURITY POLICY
+
+## 功能描述
+
+对已存在的行访问控制策略（包括行访问控制策略的名称，行访问控制指定的用户，行访问控制的策略表达式）进行修改。
+
+## 注意事项
+
+表的所有者或管理员用户才能进行此操作。
+
+## 语法格式
+
+```ebnf+diagram
+AlterRowLevelSecurityPolicy ::= ALTER [ ROW LEVEL SECURITY ] POLICY [ IF EXISTS ] policy_name ON table_name RENAME TO new_policy_name;
+```
+
+```ebnf+diagram
+AlterRowLevelSecurityPolicy ::= ALTER [ ROW LEVEL SECURITY ] POLICY policy_name ON table_name
+    [ TO { role_name | PUBLIC } [, ...] ]
+    [ USING ( using_expression ) ];
+```
+
+## 参数说明
+
+- policy_name
+
+  行访问控制策略名称。
+
+- table_name
+
+  行访问控制策略的表名。
+
+- new_policy_name
+
+  新的行访问控制策略名称。
+
+- role_name
+
+  行访问控制策略应用的数据库用户，可以指定多个用户，PUBLIC表示应用到所有用户。
+
+- using_expression
+
+  行访问控制的表达式，返回值为boolean类型。
+
+## 示例
+
+```sql
+--创建数据表all_data
+mogdb=# CREATE TABLE all_data(id int, role varchar(100), data varchar(100));
+
+--创建行访问控制策略，当前用户只能查看用户自身的数据
+mogdb=# CREATE ROW LEVEL SECURITY POLICY all_data_rls ON all_data USING(role = CURRENT_USER);
+mogdb=# \d+ all_data
+                               Table "public.all_data"
+ Column |          Type          | Modifiers | Storage  | Stats target | Description
+--------+------------------------+-----------+----------+--------------+-------------
+ id     | integer                |           | plain    |              |
+ role   | character varying(100) |           | extended |              |
+ data   | character varying(100) |           | extended |              |
+Row Level Security Policies:
+    POLICY "all_data_rls"
+      USING (((role)::name = "current_user"()))
+Has OIDs: no
+Location Nodes: ALL DATANODES
+Options: orientation=row, compression=no
+
+--修改行访问控制all_data_rls的名称
+mogdb=# ALTER ROW LEVEL SECURITY POLICY all_data_rls ON all_data RENAME TO all_data_new_rls;
+
+--修改行访问控制策略影响的用户
+mogdb=# ALTER ROW LEVEL SECURITY POLICY all_data_new_rls ON all_data TO alice, bob;
+mogdb=# \d+ all_data
+                               Table "public.all_data"
+ Column |          Type          | Modifiers | Storage  | Stats target | Description
+--------+------------------------+-----------+----------+--------------+-------------
+ id     | integer                |           | plain    |              |
+ role   | character varying(100) |           | extended |              |
+ data   | character varying(100) |           | extended |              |
+Row Level Security Policies:
+    POLICY "all_data_new_rls"
+      TO alice,bob
+      USING (((role)::name = "current_user"()))
+Has OIDs: no
+Location Nodes: ALL DATANODES
+Options: orientation=row, compression=no, enable_rowsecurity=true
+
+--修改行访问控制策略表达式
+mogdb=# ALTER ROW LEVEL SECURITY POLICY all_data_new_rls ON all_data USING (id > 100 AND role = current_user);
+mogdb=# \d+ all_data
+                               Table "public.all_data"
+ Column |          Type          | Modifiers | Storage  | Stats target | Description
+--------+------------------------+-----------+----------+--------------+-------------
+ id     | integer                |           | plain    |              |
+ role   | character varying(100) |           | extended |              |
+ data   | character varying(100) |           | extended |              |
+Row Level Security Policies:
+    POLICY "all_data_new_rls"
+      TO alice,bob
+      USING (((id > 100) AND ((role)::name = "current_user"())))
+Has OIDs: no
+Location Nodes: ALL DATANODES
+Options: orientation=row, compression=no, enable_rowsecurity=true
+```
+
+## 相关链接
+
+[CREATE ROW LEVEL SECURITY POLICY](52-CREATE-ROW-LEVEL-SECURITY-POLICY)，[DROP ROW LEVEL SECURITY POLICY](87-DROP-ROW-LEVEL-SECURITY-POLICY)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/130-SET-SESSION-AUTHORIZATION.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/130-SET-SESSION-AUTHORIZATION.md
new file mode 100644
index 0000000000000000000000000000000000000000..d9a1668304eca3ae2e15cbf015af14bebc9a9d08
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/130-SET-SESSION-AUTHORIZATION.md
@@ -0,0 +1,78 @@
+---
+title: SET SESSION AUTHORIZATION
+summary: SET SESSION AUTHORIZATION
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# SET SESSION AUTHORIZATION
+
+## 功能描述
+
+把当前会话里的会话用户标识和当前用户标识都设置为指定的用户。
+
+## 注意事项
+
+只有在初始会话用户有系统管理员权限的时候，会话用户标识符才能改变。否则，只有在指定了被认证的用户名的情况下，系统才接受该命令。
+
+## 语法格式
+
+- 为当前会话设置会话用户标识符和当前用户标识符。
+
+  ```ebnf+diagram
+  SetSessionAuthorization ::= SET [ SESSION | LOCAL ] SESSION AUTHORIZATION role_name PASSWORD 'password';
+  ```
+
+- 重置会话和当前用户标识符为初始认证的用户名。
+
+  ```ebnf+diagram
+  ResetSessionAuthorization ::= {SET [ SESSION | LOCAL ] SESSION AUTHORIZATION DEFAULT
+      | RESET SESSION AUTHORIZATION};
+  ```
+
+## 参数说明
+
+- **SESSION**
+
+  声明这个命令只对当前会话起作用。
+
+- **LOCAL**
+
+  声明该命令只在当前事务中有效。
+
+- **role_name**
+
+  用户名。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- **password**
+
+  角色的密码。要求符合密码的命名规则。
+
+- **DEFAULT**
+
+  重置会话和当前用户标识符为初始认证的用户名。
+
+## 示例
+
+```sql
+--创建角色paul。
+mogdb=# CREATE ROLE paul IDENTIFIED BY 'Bigdata@123';
+
+--设置当前用户为paul。
+mogdb=# SET SESSION AUTHORIZATION paul password 'Bigdata@123';
+
+--查看当前会话用户，当前用户。
+mogdb=# SELECT SESSION_USER, CURRENT_USER;
+
+--重置当前用户。
+mogdb=# RESET SESSION AUTHORIZATION;
+
+--删除用户。
+mogdb=# DROP USER paul;
+```
+
+## 相关参考
+
+[SET ROLE](129-SET-ROLE)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/131-SET-TRANSACTION.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/131-SET-TRANSACTION.md
new file mode 100644
index 0000000000000000000000000000000000000000..1db8cb9a7e64232fc396f0d85949e3bb2304813d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/131-SET-TRANSACTION.md
@@ -0,0 +1,63 @@
+---
+title: SET TRANSACTION
+summary: SET TRANSACTION
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# SET TRANSACTION
+
+## 功能描述
+
+为事务设置特性。事务特性包括事务隔离级别、事务访问模式(读/写或者只读)。可以设置当前事务的特性（LOCAL)，也可以设置会话的默认事务特性(SESSION)。
+
+## 注意事项
+
+设置当前事务特性需要在事务中执行（即执行SET TRANSACTION之前需要执行START TRANSACTION或者BEGIN），否则设置不生效。
+
+## 语法格式
+
+设置事务的隔离级别、读写模式。
+
+```ebnf+diagram
+SetTransaction ::= { SET [ LOCAL ] TRANSACTION|SET SESSION CHARACTERISTICS AS TRANSACTION }
+  { ISOLATION LEVEL { READ COMMITTED | SERIALIZABLE | REPEATABLE READ }
+  | { READ WRITE | READ ONLY } } [, ...];
+```
+
+## 参数说明
+
+- **LOCAL**
+
+  声明该命令只在当前事务中有效。
+
+- **SESSION**
+
+  声明这个命令只对当前会话起作用。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- **ISOLATION_LEVEL**
+
+  指定事务隔离级别，该参数决定当一个事务中存在其他并发运行事务时能够看到什么数据。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 在事务中第一个数据修改语句（SELECT，INSERT，DELETE，UPDATE，FETCH，COPY）执行之后，当前事务的隔离级别就不能再次设置。
+
+  取值范围:
+
+  - READ COMMITTED：读已提交隔离级别，只能读到已经提交的数据，而不会读到未提交的数据。这是缺省值。
+  - REPEATABLE READ：可重复读隔离级别，仅仅能看到事务开始之前提交的数据，不能看到未提交的数据，以及在事务执行期间由其它并发事务提交的修改。
+  - SERIALIZABLE：openGauss目前功能上不支持此隔离级别，等价于REPEATABLE READ。
+
+- **READ WRITE | READ ONLY**
+
+  指定事务访问模式（读/写或者只读）。
+
+## 示例
+
+```sql
+--开启一个事务，设置事务的隔离级别为READ COMMITTED，访问模式为READ ONLY。
+mogdb=# START TRANSACTION;
+mogdb=# SET LOCAL TRANSACTION ISOLATION LEVEL READ COMMITTED READ ONLY;
+mogdb=# COMMIT;
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/132-SHOW.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/132-SHOW.md
new file mode 100644
index 0000000000000000000000000000000000000000..c72f073dcbc12ce0eb67f1fb7b82b0b74dd86a81
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/132-SHOW.md
@@ -0,0 +1,51 @@
+---
+title: SHOW
+summary: SHOW
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# SHOW
+
+## 功能描述
+
+SHOW将显示当前运行时参数的数值。
+
+## 注意事项
+
+无。
+
+## 语法格式
+
+```ebnf+diagram
+Show ::= SHOW
+  {
+    [VARIABLES LIKE] configuration_parameter |
+    CURRENT_SCHEMA |
+    TIME ZONE |
+    TRANSACTION ISOLATION LEVEL |
+    SESSION AUTHORIZATION |
+    ALL
+  };
+```
+
+## 参数说明
+
+显示变量的参数请参见RESET的参数说明。
+
+## 示例
+
+```sql
+--显示 timezone 参数值。
+mogdb=# SHOW timezone;
+
+--显示所有参数。
+mogdb=# SHOW ALL;
+
+--显示参数名中包含”var”的所有参数
+mogdb=# SHOW VARIABLES LIKE var;
+```
+
+## 相关链接
+
+[SET](127-SET)，[RESET](119-RESET)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/133-SHUTDOWN.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/133-SHUTDOWN.md
new file mode 100644
index 0000000000000000000000000000000000000000..856ed03d852fc29b11505034c2af2b9f1d746dd6
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/133-SHUTDOWN.md
@@ -0,0 +1,50 @@
+---
+title: SHUTDOWN
+summary: SHUTDOWN
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# SHUTDOWN
+
+## 功能描述
+
+SHUTDOWN将关闭当前连接的数据库节点。
+
+## 注意事项
+
+仅拥有管理员权限的用户可以运行此命令。
+
+## 语法格式
+
+```ebnf+diagram
+Shutdown ::= SHUTDOWN
+  {
+    fast |
+    immediate
+  };
+```
+
+## 参数说明
+
+- **””**
+
+  不指定关闭模式，默认为fast。
+
+- **fast**
+
+  不等待客户端中断连接，将所有活跃事务回滚并且强制断开客户端，然后关闭数据库节点。
+
+- **immediate**
+
+  强行关闭，在下次重新启动的时候将导致故障恢复。
+
+## 示例
+
+```sql
+--关闭当前数据库节点。
+mogdb=# SHUTDOWN;
+
+--使用fast模式关闭当前数据库节点。
+mogdb=# SHUTDOWN FAST;
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/133.1-SNAPSHOT.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/133.1-SNAPSHOT.md
new file mode 100644
index 0000000000000000000000000000000000000000..76631077244ef36ab89b5b496c1b68b4b6d8b38a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/133.1-SNAPSHOT.md
@@ -0,0 +1,110 @@
+---
+title: SNAPSHOT
+summary: SNAPSHOT
+author: Zhang Cuiping
+date: 2021-11-01
+---
+
+# SNAPSHOT
+
+## 功能描述
+
+针对多用户情况下，对数据进行统一的版本控制。
+
+## 注意事项
+
+- 本特性GUC参数db4ai_snapshot_mode，快照存储模型分为MSS和CSS两种；GUC参数db4ai_snapshot_version_delimiter，用于设定版本分隔符，默认为“@”;GUC参数db4ai_snapshot_version_separator，用于设定子版本分隔符，默认为“.”。
+- 当快照选用增量存储方式时，各个快照中具有依赖关系。删除快照需要按照依赖顺序进行删除。
+- snapshot特性用于团队不同成员间维护数据，涉及管理员和普通用户之间的数据转写。所以在私有用户、三权分立(enableSeparationOfDuty=ON)等状态下，数据库不支持snapshot功能特性。
+- 当需要稳定可用的快照用于AI训练等任务时，用户需要将快照发布。
+
+## 语法格式
+
+1. 创建快照。
+
+   可以采用“CREATE SNAPSHOT … AS”以及“CREATE SNAPSHOT … FROM”语句创建**数据表快照**。
+
+   - CREATE SNAPSHOT AS
+
+        ```ebnf+diagram
+        CreateSnapshotAs ::= CREATE SNAPSHOT qualified_name '@'[ version | ident | sconst]
+            [COMMENT IS 'sconst' AS query];
+        ```
+
+    - CREATE SNAPSHOT FROM
+
+        ```ebnf+diagram
+        CreateSnapshotFrom ::= CREATE SNAPSHOT 'qualified_name'  '@' [ version | ident | sconst]
+            FROM '@'  [version | ident | sconst ]
+            [COMMENT IS 'sconst'
+                USING (
+                { INSERT [INTO SNAPSHOT] '…'
+                | UPDATE [SNAPSHOT] [AS 'alias'] SET '…' [FROM '…'] [WHERE' …']
+                | DELETE [FROM SNAPSHOT] [AS 'alias'] [USING '…'] [WHERE '…']
+                | ALTER [SNAPSHOT] { ADD '… '| DROP '…' } [, '…']
+            } [;'...'])];
+        ```
+
+2. 删除快照。
+
+   PURGE SNAPSHOT
+
+   ```ebnf+diagram
+   PurgeSnapshot ::= PURGE SNAPSHOT 'qualified_name' '@'  [version | ident | sconst];
+   ```
+
+3. 快照采样。
+
+   SAMPLE SNAPSHOT
+
+   ```ebnf+diagram
+   SampleSnapshot ::= SAMPLE SNAPSHOT [qualified_name] '@' [version | ident | sconst]
+       [STRATIFY BY attr_list]
+       { AS [label] AT RATIO [num] [COMMENT IS [comment]] } [, '…']
+   ```
+
+4. 快照发布。
+
+   PUBLISH SNAPSHOT
+
+   ```ebnf+diagram
+   PublishSnapshot ::= PUBLISH SNAPSHOT [qualified_name] '@'  [version | ident | sconst];
+   ```
+
+5. 快照存档。
+
+   ARCHIVE SNAPSHOT
+
+   ```ebnf+diagram
+   ArchiveSnapshot ::= ARCHIVE SNAPSHOT [qualified_name] '@ '[version | ident | sconst];
+   ```
+
+## 参数说明
+
+- qualified_name
+
+  创建snapshot的名称。
+
+  取值范围: 字符串，需要符合标识符命名规则。
+
+- version
+
+  (可省略)snapshot的版本号，当省略设置。系统会自动顺延编号。
+
+  取值范围: 字符串，数字编号配合分隔符。
+
+## 示例
+
+```
+create snapshot s1@1.0 comment is 'first version' as select * from t1;
+create snapshot s1@3.0 from @1.0 comment is 'inherits from @1.0' using (INSERT VALUES(6, 'john'), (7, 'tim'); DELETE WHERE id = 1);
+SELECT * FROM s1@1.0;
+purge snapshot s1@1.0;
+sample snapshot s1@2.0 stratify by name as nick at ratio .5;
+publish snapshot s1@2.0;
+archive snapshot s1@2.0;
+```
+
+## 相关链接
+
+无
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/134-START-TRANSACTION.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/134-START-TRANSACTION.md
new file mode 100644
index 0000000000000000000000000000000000000000..512b4c4cac1d4dbb5d3e7f18ff6d5e2f29ff989f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/134-START-TRANSACTION.md
@@ -0,0 +1,88 @@
+---
+title: START TRANSACTION
+summary: START TRANSACTION
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# START TRANSACTION
+
+## 功能描述
+
+通过START TRANSACTION启动事务。如果声明了隔离级别、读写模式，那么新事务就使用这些特性，类似执行了SET TRANSACTION。
+
+## 注意事项
+
+无。
+
+## 语法格式
+
+格式一：START TRANSACTION格式
+
+```ebnf+diagram
+StartTransaction ::= START TRANSACTION
+  [
+    {
+       ISOLATION LEVEL { READ COMMITTED | SERIALIZABLE | REPEATABLE READ }
+       | { READ WRITE | READ ONLY }
+     } [, ...]
+  ];
+```
+
+格式二：BEGIN格式
+
+```ebnf+diagram
+Begin ::= BEGIN [ WORK | TRANSACTION ]
+  [
+    {
+       ISOLATION LEVEL { READ COMMITTED | SERIALIZABLE | REPEATABLE READ }
+       | { READ WRITE | READ ONLY }
+      } [, ...]
+  ];
+```
+
+## 参数说明
+
+- **WORK | TRANSACTION**
+
+  BEGIN格式中的可选关键字，没有实际作用。
+
+- **ISOLATION LEVEL**
+
+  指定事务隔离级别，它决定当一个事务中存在其他并发运行事务时它能够看到什么数据。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  > 在事务中第一个数据修改语句（SELECT, INSERT，DELETE，UPDATE，FETCH，COPY）执行之后，事务隔离级别就不能再次设置。
+
+  取值范围:
+
+  - READ COMMITTED：读已提交隔离级别，只能读到已经提交的数据，而不会读到未提交的数据。这是缺省值。
+  - REPEATABLE READ：可重复读隔离级别，仅仅看到事务开始之前提交的数据，它不能看到未提交的数据，以及在事务执行期间由其它并发事务提交的修改。
+  - SERIALIZABLE：MogDB目前功能上不支持此隔离级别，等价于REPEATABLE READ。
+
+- **READ WRITE | READ ONLY**
+
+  指定事务访问模式（读/写或者只读）。
+
+## 示例
+
+```sql
+--以默认方式启动事务。
+mogdb=# START TRANSACTION;
+mogdb=# SELECT * FROM tpcds.reason;
+mogdb=# END;
+
+--以默认方式启动事务。
+mogdb=# BEGIN;
+mogdb=# SELECT * FROM tpcds.reason;
+mogdb=# END;
+
+--以隔离级别为READ COMMITTED，读/写方式启动事务。
+mogdb=# START TRANSACTION ISOLATION LEVEL READ COMMITTED READ WRITE;
+mogdb=# SELECT * FROM tpcds.reason;
+mogdb=# COMMIT;
+```
+
+## 相关链接
+
+[COMMIT | END](39-COMMIT-END)，[ROLLBACK](121-ROLLBACK)，[SET TRANSACTION](131-SET-TRANSACTION)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/134.1-TIMECAPSULE-TABLE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/134.1-TIMECAPSULE-TABLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..b942226d41154248da9c369ca396f7859899bd80
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/134.1-TIMECAPSULE-TABLE.md
@@ -0,0 +1,122 @@
+---
+title: TIMECAPSULE TABLE
+summary: TIMECAPSULE TABLE
+author: Zhang Cuiping
+date: 2021-11-01
+---
+
+# TIMECAPSULE TABLE
+
+## 功能描述
+
+在人为操作或应用程序错误时，使用TIMECAPSULE TABLE语句恢复可将表恢复到一个早期状态。
+
+表可以闪回到过去的时间点，这依赖于系统中保存的旧版本数据。此外MogDB数据库不能恢复到通过DDL操作改变了表结构的早期状态。
+
+## 注意事项
+
+- TIMECAPSULE TABLE语句的用法主要分为两大类：闪回旧版本数据和从回收站中闪回。
+
+  - TO TIMECAPSULE和TO CSN能够将表闪回到过去的某个版本。
+  - 回收站记录了DROP和TRUNCATE的对象数据。TO BEFORE DROP和TO BEFORE TRUNCATE就是从回收站中闪回。
+
+- 不支持闪回表的对象类型：系统表、列存表、内存表、DFS表、全局临时表、本地临时表、UNLOGGED表、序列表、Hbkt表。
+
+- 闪回点和当前点之间，执行过修改表结构或影响物理存储的语句（DDL、DCL、VACUUM FULL），闪回失败。
+
+- 执行闪回删除需要用户具有如下权限：用户必须具有垃圾对象所在schema的create和usage权限，并且用户必须是schema的所有者或者是垃圾对象的所有者。
+
+  执行闪回TRUNCATE需要用户具有如下权限：用户必须具有垃圾对象所在schema的create和usage权限，并且用户必须是schema的所有者或者是垃圾对象的所有者，另外用户必须具有垃圾对象的TRUNCATE权限。
+
+- 不适用闪回drop/truncate功能的场景或表：
+
+  - 回收站关闭场景：enable_recyclebin = off；
+  - 系统处于维护态（xc_maintenance_mode = on）或升级场景；
+  - 多对象删除场景：DROP/TRUNCATE TABLE命令同时指定多个对象；
+  - 系统表、列存表、内存表、DFS表、全局临时表、本地临时表、UNLOGGED表、序列表、Hbkt表。
+
+## 语法格式
+
+```ebnf+diagram
+TimecapsuleTable ::= TIMECAPSULE TABLE [ schema_name'.']table_name TO {CSN expr | TIMESTAMP expr | BEFORE { DROP [RENAME TO table_name] | TRUNCATE } }
+```
+
+## 参数说明
+
+- **schema_name**
+
+  指定模式包含的表。如果缺省，则为当前模式。
+
+- **table_name**
+
+  指定表名。
+
+- **TO CSN**
+
+  指定要返回表的时间点对应的事务提交序列号（CSN）。expr必须计算一个数字，代表有效的CSN。
+
+- **TO TIMESTAMP**
+
+  指定要返回表的时间点对应的时间戳。expr必须计算一个过去有效的时间戳（使用TO_TIMESTAMP函数将字符串转换为时间类型）。表将被闪回到指定时间戳大约3秒内的时间点。
+
+  说明：闪回点过旧时，因旧版本被回收导致无法获取旧版本，会导致闪回失败并报错：Restore point too old。可通过同值配置vacuum_defer_cleanup_age 和 version_retention_age 设置旧版本保留期限。
+
+- **TO BEFORE DROP**
+
+  使用这个子句检索回收站中已删除的表及其子对象。
+
+  你可以指定原始用户指定的表的名称，或对象删除时数据库分配的系统生成名称。
+
+  - 回收站中系统生成的对象名称是唯一的。因此，如果指定系统生成名称，那么数据库检索指定的对象。使用“select * from gs_recyclebin;”语句查看回收站中的内容。
+  - 如果指定了用户指定的名称，且如果回收站中包含多个该名称的对象，然后数据库检索回收站中最近移动的对象。如果想要检索更早版本的表，你可以这样做：
+    - 指定你想要检索的表的系统生成名称。
+    - 执行TIMECAPSULE TABLE … TO BEFORE DROP语句，直到你要检索的表。
+  - 恢复DROP表时，只恢复基表名，其他子对象名均保持回收站对象名。用户可根据需要，执行DDL命令手工调整子对象名。
+  - 回收站对象不支持DML、DCL、DDL等写操作，不支持DQL查询操作（后续支持）。
+  - recyclebin_retention_time配置参数用于设置回收站对象保留时间，超过该时间的回收站对象将被自动清理。
+
+- **RENAME TO**
+
+  为从回收站中检索的表指定一个新名称。
+
+- **TRUNCATE**
+
+  闪回到TRUNCATE之前。
+
+## 示例
+
+```
+-- 删除表tpcds.reason_t2
+DROP TABLE IF EXISTS tpcds.reason_t2;
+-- 创建表tpcds.reason_t2
+mogdb=# CREATE TABLE tpcds.reason_t2
+ (
+  r_reason_sk    integer,
+  r_reason_id    character(16),
+  r_reason_desc  character(100)
+  );
+--向表tpcds.reason_t2中插入记录
+mogdb=#  INSERT INTO tpcds.reason_t2 VALUES (1, 'AA', 'reason1'),(2, 'AB', 'reason2'),(3, 'AC', 'reason3');
+INSERT 0 3
+--清空tpcds.reason_t2表中的数据
+mogdb=#  TRUNCATE TABLE tpcds.reason_t2;
+--查询tpcds.reason_t2表中的数据
+mogdb=#  select * from tpcds.reason_t2;
+ r_reason_sk | r_reason_id | r_reason_desc
+-------------+-------------+---------------
+(0 rows)
+--执行闪回TRUNCATE
+mogdb=#  TIMECAPSULE TABLE tpcds.reason_t2 to BEFORE TRUNCATE;
+mogdb=#  select * from tpcds.reason_t2;
+ r_reason_sk |   r_reason_id    |                                            r_reason_desc
+-------------+------------------+------------------------------------------------------------------------------------------------------
+           1 | AA               | reason1
+           2 | AB               | reason2
+           3 | AC               | reason3
+(3 rows)
+--删除表tpcds.reason_t2
+mogdb=#  DROP TABLE tpcds.reason_t2;
+--执行闪回DROP
+mogdb=#  TIMECAPSULE TABLE tpcds.reason_t2 to BEFORE DROP;
+TimeCapsule Table
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/135-TRUNCATE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/135-TRUNCATE.md
new file mode 100644
index 0000000000000000000000000000000000000000..d00febbb727623cfba459f15d2d18ed19bb9ad4b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/135-TRUNCATE.md
@@ -0,0 +1,130 @@
+---
+title: TRUNCATE
+summary: TRUNCATE
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# TRUNCATE
+
+## 功能描述
+
+清理表数据，TRUNCATE快速地从表中删除所有行。
+
+它和在目标表上进行无条件的DELETE有同样的效果，但由于TRUNCATE不做表扫描，因而快得多。在大表上操作效果更明显。
+
+## 注意事项
+
+- TRUNCATE TABLE在功能上与不带WHERE子句DELETE语句相同：二者均删除表中的全部行。
+- TRUNCATE TABLE比DELETE速度快且使用系统和事务日志资源少：
+  - DELETE语句每次删除一行，并在事务日志中为所删除每行记录一项。
+  - TRUNCATE TABLE通过释放存储表数据所用数据页来删除数据，并且只在事务日志中记录页的释放。
+- TRUNCATE，DELETE，DROP三者的差异如下：
+  - TRUNCATE TABLE，删除内容，释放空间，但不删除定义。
+  - DELETE TABLE，删除内容，不删除定义，不释放空间。
+  - DROP TABLE，删除内容和定义，释放空间。
+
+## 语法格式
+
+- 清理表数据。
+
+  ```ebnf+diagram
+  Truncate ::= TRUNCATE {[ TABLE ] [ ONLY ] {table_name [ * ]} [, ... ]
+  [ CONTINUE IDENTITY ] [ CASCADE | RESTRICT][PURGE]};
+  ```
+
+- 清理表分区的数据。
+
+  ```ebnf+diagram
+  TruncatePartition ::= ALTER TABLE [ IF EXISTS  ] { [ ONLY  ] table_name
+                         | table_name *
+                         | ONLY ( table_name )  }
+  TRUNCATE PARTITION { partition_name
+                     | FOR (  partition_value  [, ...] )  } [ UPDATE GLOBAL INDEX ];
+  ```
+
+## 参数说明
+
+- **ONLY**
+
+  如果声明ONLY，只有指定的表会被清空。如果没有声明ONLY，这个表以及其所有子表（若有）会被清空。
+
+- **table_name**
+
+  目标表的名称（可以有模式修饰）。
+
+  取值范围: 已存在的表名。
+
+- **CONTINUE IDENTITY**
+
+  不改变序列的值。这是缺省值。
+
+- **CASCADE | RESTRICT**
+
+  - CASCADE：级联清空所有由于CASCADE而被添加到组中的表。
+  - RESTRICT（缺省值）：完全清空。
+
+- PURGE：默认将表数据放入回收站中，PURGE直接清理。
+
+- **partition_name**
+
+  目标分区表的分区名。
+
+  取值范围: 已存在的分区名。
+
+- **partition_value**
+
+  指定的分区键值。
+
+  通过PARTITION FOR子句指定的这一组值，可以唯一确定一个分区。
+
+  取值范围: 需要进行删除数据分区的分区键的取值范围。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+  > 使用PARTITION FOR子句时，partition_value所在的整个分区会被清空。
+
+- **UPDATE GLOBAL INDEX**
+
+  如果使用该参数，则会更新分区表上的所有全局索引，以确保使用全局索引可以查询出正确的数据；如果不使用该参数，则分区表上的所有全局索引将会失效。
+
+## 示例
+
+```sql
+--创建表。
+mogdb=# CREATE TABLE tpcds.reason_t1 AS TABLE tpcds.reason;
+
+--清空表tpcds.reason_t1。
+mogdb=# TRUNCATE TABLE tpcds.reason_t1;
+
+--删除表。
+mogdb=# DROP TABLE tpcds.reason_t1;
+--创建分区表。
+mogdb=# CREATE TABLE tpcds.reason_p
+(
+  r_reason_sk integer,
+  r_reason_id character(16),
+  r_reason_desc character(100)
+)PARTITION BY RANGE (r_reason_sk)
+(
+  partition p_05_before values less than (05),
+  partition p_15 values less than (15),
+  partition p_25 values less than (25),
+  partition p_35 values less than (35),
+  partition p_45_after values less than (MAXVALUE)
+);
+
+--插入数据。
+mogdb=# INSERT INTO tpcds.reason_p SELECT * FROM tpcds.reason;
+
+--清空分区p_05_before。
+mogdb=# ALTER TABLE tpcds.reason_p TRUNCATE PARTITION p_05_before;
+
+--清空分区p_15。
+mogdb=# ALTER TABLE tpcds.reason_p TRUNCATE PARTITION for (13);
+
+--清空分区表。
+mogdb=# TRUNCATE TABLE tpcds.reason_p;
+
+--删除表。
+mogdb=# DROP TABLE tpcds.reason_p;
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/136-UPDATE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/136-UPDATE.md
new file mode 100644
index 0000000000000000000000000000000000000000..9632080bb06aecf10112b25fa63227859ed13106
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/136-UPDATE.md
@@ -0,0 +1,136 @@
+---
+title: UPDATE
+summary: UPDATE
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# UPDATE
+
+## 功能描述
+
+更新表中的数据。UPDATE修改满足条件的所有行中指定的字段值，WHERE子句声明条件，SET子句指定的字段会被修改，没有出现的字段则保持它们的原值。
+
+## 注意事项
+
+- 要修改表，用户必须对该表有UPDATE权限。
+- 对expression或condition条件里涉及到的任何表要有SELECT权限。
+- 对于列存表，暂时不支持RETURNING子句。
+- 列存表不支持结果不确定的更新(non-deterministic update)。试图对列存表用多行数据更新一行时会报错。
+- 列存表的更新操作，旧记录空间不会回收，需要执行VACUUM FULL table_name进行清理。
+- 对于列存复制表，暂不支持UPDATE操作。
+
+## 语法格式
+
+```ebnf+diagram
+Update ::= UPDATE [/*+ plan_hint */] [ ONLY ] table_name [ * ] [ [ AS ] alias ]
+SET {column_name = { expression | DEFAULT }
+    |( column_name [, ...] ) = {( { expression | DEFAULT } [, ...] ) |sub_query }}[, ...]
+    [ FROM from_list] [ WHERE condition ]
+    [ RETURNING {*
+                | {output_expression [ [ AS ] output_name ]} [, ...] }];
+```
+
+其中sub_query为：
+
+```ebnf+diagram
+sub_query ::= SELECT [ ALL | DISTINCT [ ON ( expression [, ...] ) ] ]
+{ * | {expression [ [ AS ] output_name ]} [, ...] }
+[ FROM from_item [, ...] ]
+[ WHERE condition ]
+[ GROUP BY grouping_element [, ...] ]
+[ HAVING condition [, ...] ]
+```
+
+## 参数说明
+
+- **plan_hint子句**
+
+  以/\*+ \*/的形式在UPDATE关键字后，用于对UPDATE对应的语句块生成的计划进行hint调优，详细用法请参见章节[使用Plan Hint进行调优](9-hint-based-tuning)。每条语句中只有第一个/\*+ plan_hint \*/注释块会作为hint生效，里面可以写多条hint。
+
+- **table_name**
+
+  要更新的表名，可以使用模式修饰。
+
+  取值范围: 已存在的表名称。
+
+- **alias**
+
+  目标表的别名。
+
+  取值范围: 字符串，符合标识符命名规范。
+
+- **column_name**
+
+  要修改的字段名。
+
+  支持使用目标表的别名加字段名来引用这个字段。例如：
+
+  UPDATE foo AS f SET f.col_name = 'namecol';
+
+  取值范围: 已存在的字段名。
+
+- **expression**
+
+  赋给字段的值或表达式。
+
+- **DEFAULT**
+
+  用对应字段的缺省值填充该字段。
+
+  如果没有缺省值，则为NULL。
+
+- **sub_query**
+
+  子查询。
+
+  使用同一数据库里其他表的信息来更新一个表可以使用子查询的方法。其中SELECT子句具体介绍请参考**SELECT**。
+
+- **from_list**
+
+  一个表的表达式列表，允许在WHERE条件里使用其他表的字段。与在一个SELECT语句的FROM子句里声明表列表类似。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+  > 目标表绝对不能出现在from_list里，除非在使用一个自连接（此时它必须以from_list的别名出现）。
+
+- **condition**
+
+  一个返回Boolean类型结果的表达式。只有这个表达式返回true的行才会被更新。
+
+- **output_expression**
+
+  在所有需要更新的行都被更新之后，UPDATE命令用于计算返回值的表达式。
+
+  取值范围: 使用任何table以及FROM中列出的表的字段。*表示返回所有字段。
+
+- **output_name**
+
+  字段的返回名称。
+
+## 示例
+
+```sql
+--创建表student1。
+mogdb=# CREATE TABLE student1
+(
+   stuno     int,
+   classno   int
+);
+
+--插入数据。
+mogdb=# INSERT INTO student1 VALUES(1,1);
+mogdb=# INSERT INTO student1 VALUES(2,2);
+mogdb=# INSERT INTO student1 VALUES(3,3);
+
+--查看数据。
+mogdb=# SELECT * FROM student1;
+
+--直接更新所有记录的值。
+mogdb=# UPDATE student1 SET classno = classno*2;
+
+--查看数据。
+mogdb=# SELECT * FROM student1;
+
+--删除表。
+mogdb=# DROP TABLE student1;
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/137-VACUUM.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/137-VACUUM.md
new file mode 100644
index 0000000000000000000000000000000000000000..8c899975c96f34b73b05573110b82270f0ee0bcf
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/137-VACUUM.md
@@ -0,0 +1,118 @@
+---
+title: VACUUM
+summary: VACUUM
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# VACUUM
+
+## 功能描述
+
+VACUUM回收表或B-Tree索引中已经删除的行所占据的存储空间。在一般的数据库操作里，那些已经DELETE的行并没有从它们所属的表中物理删除；在完成VACUUM之前它们仍然存在。因此有必要周期地运行VACUUM，特别是在经常更新的表上。
+
+## 注意事项
+
+- 如果没有参数，VACUUM处理当前数据库里用户拥有相应权限的每个表。如果参数指定了一个表，VACUUM只处理指定的那个表。
+- 要对一个表进行VACUUM操作，通常用户必须是表的所有者或者被授予了指定表VACUUM权限的用户，默认系统管理员有该权限。数据库的所有者允许对数据库中除了共享目录以外的所有表进行VACUUM操作（该限制意味着只有系统管理员才能真正对一个数据库进行VACUUM操作）。VACUUM命令会跳过那些用户没有权限的表进行垃圾回收操作。
+- VACUUM不能在事务块内执行。
+- 建议生产数据库经常清理（至少每晚一次），以保证不断地删除失效的行。尤其是在增删了大量记录之后，对受影响的表执行VACUUM ANALYZE命令是一个很好的习惯。这样将更新系统目录为最近的更改，并且允许查询优化器在规划用户查询时有更好地选择。
+- 不建议日常使用FULL选项，但是可以在特殊情况下使用。例如在用户删除了一个表的大部分行之后，希望从物理上缩小该表以减少磁盘空间占用。VACUUM FULL通常要比单纯的VACUUM收缩更多的表尺寸。FULL选项并不清理索引，所以推荐周期性的运行REINDEX命令。实际上，首先删除所有索引，再运行VACUUM FULL命令，最后重建索引通常是更快的选择。如果执行此命令后所占用物理空间无变化（未减少），请确认是否有其他活跃事务（删除数据事务开始之前开始的事务，并在VACUUM FULL执行前未结束）存在，如果有等其他活跃事务退出进行重试。
+- VACUUM会导致I/O流量的大幅增加，这可能会影响其他活动会话的性能。因此，有时候会建议使用基于开销的VACUUM延迟特性。
+- 如果指定了VERBOSE选项，VACUUM将打印处理过程中的信息，以表明当前正在处理的表。各种有关当前表的统计信息也会打印出来。但是对于列存表执行VACUUM操作，指定了VERBOSE选项，无信息输出。
+- 当含有带括号的选项列表时，选项可以以任何顺序写入。如果没有括号，则选项必须按语法显示的顺序给出。
+- VACUUM和VACUUM FULL时，会根据参数vacuum_defer_cleanup_age延迟清理行存表记录，即不会立即清理刚刚删除的元组。
+- VACUUM ANALYZE先执行一个VACUUM操作，然后给每个选定的表执行一个ANALYZE。对于日常维护脚本而言，这是一个很方便的组合。
+- 简单的VACUUM（不带FULL选项）只是简单地回收空间并且令其可以再次使用。这种形式的命令可以和对表的普通读写并发操作，因为没有请求排他锁。VACUUM FULL执行更广泛的处理，包括跨块移动行，以便把表压缩到最少的磁盘块数目里。这种形式要慢许多并且在处理的时候需要在表上施加一个排他锁。
+- VACUUM列存表内部执行的操作包括三个：迁移delta表中的数据到主表、VACUUM主表的delta表、VACUUM主表的desc表。该操作不会回收delta表的存储空间，如果要回收delta表的冗余存储空间，需要对该列存表执行VACUUM DELTAMERGE。
+- 同时执行多个VACUUM FULL可能出现死锁。
+- 如果没有打开xc_maintenance_mode参数，那么VACUUM FULL操作将跳过所有系统表。
+- 执行DELETE后立即执行VACUUM FULL命令不会回收空间。执行DELETE后再执行1000个非SELECT事务，或者等待1s后再执行1个事务，之后再执行VACUUM FULL命令空间才会回收。
+
+## 语法格式
+
+- 回收空间并更新统计信息，对关键字顺序无要求。
+
+  ```ebnf+diagram
+  Vacuum ::= VACUUM [ ( { FULL | FREEZE | VERBOSE | {ANALYZE | ANALYSE }} [,...] ) ]
+      [ table_name [ (column_name [, ...] ) ] ] [ PARTITION ( partition_name ) ];
+  ```
+
+- 仅回收空间，不更新统计信息。
+
+  ```ebnf+diagram
+  Vacuum ::= VACUUM [ FULL [COMPACT] ] [ FREEZE ] [ VERBOSE ] [ table_name ] [ PARTITION ( partition_name ) ];
+  ```
+
+- 回收空间并更新统计信息，且对关键字顺序有要求。
+
+  ```ebnf+diagram
+  Vacuum ::= VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] { ANALYZE | ANALYSE } [ VERBOSE ]
+      [ table_name [ (column_name [, ...] ) ] ] [ PARTITION ( partition_name ) ];
+  ```
+
+## 参数说明
+
+- **FULL**
+
+  选择“FULL”清理，这样可以恢复更多的空间，但是需要耗时更多，并且在表上施加了排他锁。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 使用FULL参数会导致统计信息丢失，如果需要收集统计信息，请在VACUUM FULL语句中加上analyze关键字。
+
+- **FREEZE**
+
+  指定FREEZE相当于执行VACUUM时将vacuum_freeze_min_age参数设为0。
+
+- **VERBOSE**
+
+  为每个表打印一份详细的清理工作报告。
+
+- **ANALYZE | ANALYSE**
+
+  更新用于优化器的统计信息，以决定执行查询的最有效方法。
+
+- **table_name**
+
+  要清理的表的名称（可以有模式修饰）。
+
+  取值范围: 要清理的表的名称。缺省时为当前数据库中的所有表。
+
+- **column_name**
+
+  要分析的具体的字段名称，需要配合analyze选项使用。
+
+  取值范围: 要分析的具体的字段名称。缺省时为所有字段。
+
+- **PARTITION**
+
+  COMPACT和PARTITION参数不能同时使用。
+
+- **partition_name**
+
+  要清理的表的分区名称。缺省时为所有分区。
+
+- **DELTAMERGE**
+
+  只针对列存表，将列存表的delta table中的数据转移到主表存储上。对列存表而言，此操作受enable_delta_store和参数说明中的deltarow_threshold控制。
+
+## 示例
+
+```sql
+--在表tpcds.reason上创建索引。
+mogdb=# CREATE UNIQUE INDEX ds_reason_index1 ON tpcds.reason(r_reason_sk);
+
+--对带索引的表tpcds.reason执行VACUUM操作。
+mogdb=# VACUUM (VERBOSE, ANALYZE) tpcds.reason;
+
+--删除索引。
+mogdb=# DROP INDEX ds_reason_index1 CASCADE;
+mogdb=# DROP TABLE tpcds.reason;
+```
+
+## 优化建议
+
+- vacuum
+  - VACUUM不能在事务块内执行。
+  - 建议生产数据库经常清理（至少每晚一次），以保证不断地删除失效的行。尤其是在增删了大量记录后，对相关表执行VACUUM ANALYZE命令。
+  - 不建议日常使用FULL选项，但是可以在特殊情况下使用。例如，一个例子就是在用户删除了一个表的大部分行之后，希望从物理上缩小该表以减少磁盘空间占用。
+  - 执行VACUUM FULL操作时，建议首先删除相关表上的所有索引，再运行VACUUM FULL命令，最后重建索引。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/138-VALUES.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/138-VALUES.md
new file mode 100644
index 0000000000000000000000000000000000000000..248bf70d2799198cd88d429a2faa020df2644b32
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/138-VALUES.md
@@ -0,0 +1,67 @@
+---
+title: VALUES
+summary: VALUES
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# VALUES
+
+## 功能描述
+
+根据给定的值表达式计算一个或一组行的值。它通常用于在一个较大的命令内生成一个“常数表”。
+
+## 注意事项
+
+- 应当避免使用VALUES返回数量非常大的结果行，否则可能会遭遇内存耗尽或者性能低下。出现在INSERT中的VALUES是一个特殊情况，因为目标字段类型可以从INSERT的目标表获知，并不需要通过扫描VALUES列表来推测，所以在此情况下可以处理非常大的结果行。
+- 如果指定了多行，那么每一行都必须拥有相同的元素个数。
+
+## 语法格式
+
+```ebnf+diagram
+Values ::= VALUES {( expression [, ...] )} [, ...]
+    [ ORDER BY { sort_expression [ ASC | DESC | USING operator ] } [, ...] ]
+    [ LIMIT { count | ALL } ]
+    [ OFFSET start [ ROW | ROWS ] ]
+    [ FETCH { FIRST | NEXT } [ count ] { ROW | ROWS } ONLY ];
+```
+
+## 参数说明
+
+- **expression**
+
+  用于计算或插入结果表指定地点的常量或者表达式。
+
+  在一个出现在INSERT顶层的VALUES列表中，expression可以被DEFAULT替换以表示插入目的字段的缺省值。除此以外，当VALUES出现在其他场合的时候是不能使用DEFAULT的。
+
+- **sort_expression**
+
+  一个表示如何排序结果行的表达式或者整数常量。
+
+- **ASC**
+
+  指定按照升序排列。
+
+- **DESC**
+
+  指定按照降序排列。
+
+- **operator**
+
+  一个排序操作符。
+
+- **count**
+
+  返回的最大行数。
+
+- **OFFSET start { ROW | ROWS }**
+
+  声明返回的最大行数，而start声明开始返回行之前忽略的行数。
+
+- **FETCH { FIRST | NEXT } [ count ] { ROW | ROWS } ONLY**
+
+  FETCH子句限定返回查询结果从第一行开始的总行数，count的缺省值为1。
+
+## 示例
+
+请参见INSERT的[示例](109-INSERT#示例)。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/139-CONNECT-BY.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/139-CONNECT-BY.md
new file mode 100644
index 0000000000000000000000000000000000000000..ce0061bec722a8dbe2fae5641ae28348b7025ed0
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/139-CONNECT-BY.md
@@ -0,0 +1,209 @@
+---
+title: CONNECT BY
+summary: CONNECT BY
+author: Guo Huan
+date: 2022-01-11
+---
+
+# CONNECT BY
+
+## 功能描述
+
+- 提供兼容oracle的connect by语法，实现层级结构的数据查询控制，并展示等级、循环、起始层级等。
+- 提供oracle兼容的层级查询功能，可以按照指定的连接关系，起始条件等按照树状结构展示数据内容，数据层级，路径等。
+- 通过start with条件指定层级查询的根行，根据这些行进行递归查询来获取所有子行，以及子行的子行等。
+- 通过connect by条件指定层级间父行与子行关系，来确定每一行满足条件的所有子行。
+
+## 注意事项
+
+- 如果存在连接，无论是连接语句，还是from或where子句中，先获取连接后的结果集，然后再进行层级查询。
+- 语句中如果存在where过滤条件，先执行层级查询后再将结果集进行过滤，而不是过滤掉不满足的行以及其所有子行。
+- 可以通过level伪列查看该行所在层级，sys_connect_by_path查看从根行到该行的路径，以及connect_by_root查看根行等辅助功能。
+
+## 语法格式
+
+```ebnf+diagram
+ConnectBy ::= [ START WITH condition ]  CONNECT BY [ NOCYCLE ] condition [ ORDER SIBLINGS BY expr ]
+```
+
+CONNECT BY 的condition通过prior修饰符来表示父级的列信息，如下，可以为多个条件
+
+- PRIOR expr = expr
+- expr = PRIOR expr
+
+## 参数说明
+
+- START WITH是层级数据的根节点数据需要满足的条件。
+
+- CONNECT BY condition可以是复合条件，可以有多个PRIOR，例如
+
+  ```sql
+  CONNECT BY last_name != 'King' AND PRIOR employee_id = manager_id ...
+  CONNECT BY PRIOR employee_id = manager_id and
+  PRIOR account_mgr_id = customer_id ...
+  ```
+
+- NOCYCLE表示即使数据存在循环的条件下也使数据库返回数据
+
+- level、sys_connect_by_path、connect_by_root等伪列
+
+  - level表示该行数据所在的层数
+
+  - sys_connect_by_path (cname,’delimiter’) 表示cname列从root到该行的路径
+
+  - connect_by_root修饰符修饰列名，显示该列的root值
+
+    ```sql
+    SELECT last_name "Employee", CONNECT_BY_ROOT last_name "Manager",
+    LEVEL-1 "Pathlen", SYS_CONNECT_BY_PATH(last_name, '/') "Path"
+    FROM employees
+    WHERE LEVEL > 1 and department_id = 110
+    CONNECT BY PRIOR employee_id = manager_id;
+    Employee  Manager   Pathlen  Path
+    --------------- ------------ ---------- -----------------------------------
+    Higgins Kochhar 1 /Kochhar/Higgins
+    Gietz Kochhar 2 /Kochhar/Higgins/Gietz
+    Gietz Higgins 1 /Higgins/Gietz
+    Higgins King 2 /King/Kochhar/Higgins
+    Gietz King 3 /King/Kochhar/Higgins/Gietz
+    ```
+
+- ORDER SIBLINGS BY
+
+  使层级查询的返回数据在相同层之间保持有序， 例如
+
+  ```sql
+  select t.*, level from employee t
+  start with t.managerid = 'xx'
+  connect by prior t.empid = t.managerid
+  order siblings by name desc;
+  ```
+
+## 示例
+
+```sql
+create table mogdb210_connectby_01
+(id int,
+ pid int,
+ note varchar(20)
+);
+insert into mogdb210_connectby_01 values(1,null,'A01');
+insert into mogdb210_connectby_01 values(101,1,'X01');
+insert into mogdb210_connectby_01 values(201,101,'Y01');
+insert into mogdb210_connectby_01 values(202,101,'Y02');
+insert into mogdb210_connectby_01 values(301,201,'Z01');
+insert into mogdb210_connectby_01 values(302,201,'Z02');
+insert into mogdb210_connectby_01 values(303,202,'Z03');
+insert into mogdb210_connectby_01 values(304,202,'Z04');
+```
+
+**只有connect by关键字（基础表的每一行都做为根行按照connect by条件来获取所有的下层行）**
+
+```sql
+select id,pid,note,level,connect_by_root id,connect_by_root pid,connect_by_root note,sys_connect_by_path(note,'/') 
+from mogdb210_connectby_01
+connect by id = pid 
+order by id,pid;
+ id  | pid | note | level | connect_by_rootid | connect_by_rootpid | connect_by_rootnote | sys_connect_by_path 
+-----+-----+------+-------+-------------------+--------------------+---------------------+---------------------
+   1 |     | A01  |     1 |                 1 |                    | A01                 | /A01
+ 101 |   1 | X01  |     1 |               101 |                  1 | X01                 | /X01
+ 201 | 101 | Y01  |     1 |               201 |                101 | Y01                 | /Y01
+ 202 | 101 | Y02  |     1 |               202 |                101 | Y02                 | /Y02
+ 301 | 201 | Z01  |     1 |               301 |                201 | Z01                 | /Z01
+ 302 | 201 | Z02  |     1 |               302 |                201 | Z02                 | /Z02
+ 303 | 202 | Z03  |     1 |               303 |                202 | Z03                 | /Z03
+ 304 | 202 | Z04  |     1 |               304 |                202 | Z04                 | /Z04
+(8 rows)
+```
+
+**加nocycle关键字（没有该关键词时，如果层级之间存在循环会报错，增加nocycle关键字，某一行的子行如果存在循环就跳过该子行，继续输出其他结果）**
+
+```sql
+select id,pid,note,level,connect_by_root id,connect_by_root pid,connect_by_root note,sys_connect_by_path(note,'/') 
+from mogdb210_connectby_01
+connect by nocycle id = pid 
+order by id,pid;
+ id  | pid | note | level | connect_by_rootid | connect_by_rootpid | connect_by_rootnote | sys_connect_by_path 
+-----+-----+------+-------+-------------------+--------------------+---------------------+---------------------
+   1 |     | A01  |     1 |                 1 |                    | A01                 | /A01
+ 101 |   1 | X01  |     1 |               101 |                  1 | X01                 | /X01
+ 201 | 101 | Y01  |     1 |               201 |                101 | Y01                 | /Y01
+ 202 | 101 | Y02  |     1 |               202 |                101 | Y02                 | /Y02
+ 301 | 201 | Z01  |     1 |               301 |                201 | Z01                 | /Z01
+ 302 | 201 | Z02  |     1 |               302 |                201 | Z02                 | /Z02
+ 303 | 202 | Z03  |     1 |               303 |                202 | Z03                 | /Z03
+ 304 | 202 | Z04  |     1 |               304 |                202 | Z04                 | /Z04
+(8 rows)
+```
+
+**加siblings关键字（使同一行的子行之间以及其每一个子行的子行之间保持指定顺序）**
+
+```sql
+select id,pid,note,level,connect_by_root id,connect_by_root pid,connect_by_root note,sys_connect_by_path(note,'/') 
+from mogdb210_connectby_01
+connect by id = pid 
+order siblings by id,pid;
+ id  | pid | note | level | connect_by_rootid | connect_by_rootpid | connect_by_rootnote | sys_connect_by_path 
+-----+-----+------+-------+-------------------+--------------------+---------------------+---------------------
+   1 |     | A01  |     1 |                 1 |                    | A01                 | /A01
+ 101 |   1 | X01  |     1 |               101 |                  1 | X01                 | /X01
+ 201 | 101 | Y01  |     1 |               201 |                101 | Y01                 | /Y01
+ 202 | 101 | Y02  |     1 |               202 |                101 | Y02                 | /Y02
+ 301 | 201 | Z01  |     1 |               301 |                201 | Z01                 | /Z01
+ 302 | 201 | Z02  |     1 |               302 |                201 | Z02                 | /Z02
+ 303 | 202 | Z03  |     1 |               303 |                202 | Z03                 | /Z03
+ 304 | 202 | Z04  |     1 |               304 |                202 | Z04                 | /Z04
+(8 rows)
+```
+
+**加prior关键字（该关键字在connect by连接条件中指定上层列信息）**
+
+```sql
+select id,pid,note,level,connect_by_root id,connect_by_root pid,connect_by_root note,sys_connect_by_path(note,'/') 
+from mogdb210_connectby_01
+connect by prior id = pid 
+order by connect_by_root id, level, id;
+ id  | pid | note | level | connect_by_rootid | connect_by_rootpid | connect_by_rootnote | sys_connect_by_path 
+-----+-----+------+-------+-------------------+--------------------+---------------------+---------------------
+   1 |     | A01  |     1 |                 1 |                    | A01                 | /A01
+ 101 |   1 | X01  |     2 |                 1 |                    | A01                 | /A01/X01
+ 201 | 101 | Y01  |     3 |                 1 |                    | A01                 | /A01/X01/Y01
+ 202 | 101 | Y02  |     3 |                 1 |                    | A01                 | /A01/X01/Y02
+ 301 | 201 | Z01  |     4 |                 1 |                    | A01                 | /A01/X01/Y01/Z01
+ 302 | 201 | Z02  |     4 |                 1 |                    | A01                 | /A01/X01/Y01/Z02
+ 303 | 202 | Z03  |     4 |                 1 |                    | A01                 | /A01/X01/Y02/Z03
+ 304 | 202 | Z04  |     4 |                 1 |                    | A01                 | /A01/X01/Y02/Z04
+ 101 |   1 | X01  |     1 |               101 |                  1 | X01                 | /X01
+ 201 | 101 | Y01  |     2 |               101 |                  1 | X01                 | /X01/Y01
+ 202 | 101 | Y02  |     2 |               101 |                  1 | X01                 | /X01/Y02
+ 301 | 201 | Z01  |     3 |               101 |                  1 | X01                 | /X01/Y01/Z01
+ 302 | 201 | Z02  |     3 |               101 |                  1 | X01                 | /X01/Y01/Z02
+ 303 | 202 | Z03  |     3 |               101 |                  1 | X01                 | /X01/Y02/Z03
+ 304 | 202 | Z04  |     3 |               101 |                  1 | X01                 | /X01/Y02/Z04
+ 201 | 101 | Y01  |     1 |               201 |                101 | Y01                 | /Y01
+ 301 | 201 | Z01  |     2 |               201 |                101 | Y01                 | /Y01/Z01
+ 302 | 201 | Z02  |     2 |               201 |                101 | Y01                 | /Y01/Z02
+ 202 | 101 | Y02  |     1 |               202 |                101 | Y02                 | /Y02
+ 303 | 202 | Z03  |     2 |               202 |                101 | Y02                 | /Y02/Z03
+ 304 | 202 | Z04  |     2 |               202 |                101 | Y02                 | /Y02/Z04
+ 301 | 201 | Z01  |     1 |               301 |                201 | Z01                 | /Z01
+ 302 | 201 | Z02  |     1 |               302 |                201 | Z02                 | /Z02
+ 303 | 202 | Z03  |     1 |               303 |                202 | Z03                 | /Z03
+ 304 | 202 | Z04  |     1 |               304 |                202 | Z04                 | /Z04
+(25 rows)
+```
+
+**加start with关键字（该关键字用于获取根行，条件对于基础表进行过滤，使满足条件的行做为根行）**
+
+```sql
+select id,pid,note,level,connect_by_root id,connect_by_root pid,connect_by_root note,sys_connect_by_path(note,'/') 
+from mogdb210_connectby_01
+start with id = 101
+connect by id = pid 
+order by id,pid;
+ id  | pid | note | level | connect_by_rootid | connect_by_rootpid | connect_by_rootnote | sys_connect_by_path 
+-----+-----+------+-------+-------------------+--------------------+---------------------+---------------------
+ 101 |   1 | X01  |     1 |               101 |                  1 | X01                 | /X01
+(1 row)
+```
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/14-ALTER-RULE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/14-ALTER-RULE.md
new file mode 100644
index 0000000000000000000000000000000000000000..e754882aaa1942737d4ed46bb235d46edd8f1c1a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/14-ALTER-RULE.md
@@ -0,0 +1,45 @@
+---
+title: ALTER RULE
+summary: ALTER RULE
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER RULE
+
+## 功能描述
+
+修改一个规则的定义。
+
+## 注意事项
+
+- 要使用ALTER RULE，用户必须为应用了指定规则的表或视图的所有者。
+- 目前仅支持修改规则的名称。
+
+## 语法格式
+
+```ebnf+diagram
+AlterRule ::= ALTER RULE name ON table_name RENAME TO new_name;
+```
+
+## 参数说明
+
+- **name**
+
+  需要修改的规则名称。
+
+- **table_name**
+
+  需要创建规则的表名称。
+
+  取值范围: 数据库中已经存在的表名称。
+
+- **new_name**
+
+  规则的新名称。
+
+## 示例
+
+```sql
+ALTER RULE notify_all ON emp RENAME TO notify_me;
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/15-ALTER-SCHEMA.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/15-ALTER-SCHEMA.md
new file mode 100644
index 0000000000000000000000000000000000000000..4cf0fcad6b41dff0b3f3fb498b99b7a473a27bfb
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/15-ALTER-SCHEMA.md
@@ -0,0 +1,90 @@
+---
+title: ALTER SCHEMA
+summary: ALTER SCHEMA
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER SCHEMA
+
+## 功能描述
+
+修改模式属性。
+
+## 注意事项
+
+只有模式的所有者或者被授予了模式ALTER权限的用户有权限执行ALTER SCHEMA命令，系统管理员默认拥有此权限。但要修改模式的所有者，当前用户必须是该模式的所有者或者系统管理员，且该用户是新所有者角色的成员。
+
+## 语法格式
+
+- 修改模式的防篡改属性。
+
+    ```ebnf+diagram
+    AlterSchema ::= ALTER SCHEMA schema_name { WITH | WITHOUT } BLOCKCHAIN
+    ```
+
+- 修改模式的名称。
+
+  ```ebnf+diagram
+  AlterSchema ::= ALTER SCHEMA schema_name
+      RENAME TO new_name;
+  ```
+
+- 修改模式的所有者。
+
+  ```ebnf+diagram
+  AlterSchema ::= ALTER SCHEMA schema_name
+      OWNER TO new_owner;
+  ```
+
+## 参数说明
+
+- **schema_name**
+
+  现有模式的名称。
+
+  取值范围: 已存在的模式名。
+
+- **RENAME TO new_name**
+
+  修改模式的名称。非系统管理员要改变模式的名称，则该用户必须在此数据库上有CREATE权限。
+
+  new_name：模式的新名称。
+
+  取值范围: 字符串，要符合标识符命名规范。
+
+- **OWNER TO new_owner**
+
+  修改模式的所有者。非系统管理员要改变模式的所有者，该用户还必须是新的所有角色的直接或间接成员， 并且该成员必须在此数据库上有CREATE权限。
+
+  new_owner：模式的新所有者。
+
+  取值范围: 已存在的用户名/角色名。
+
+- **{ WITH | WITHOUT } BLOCKCHAIN**
+
+    修改模式的防篡改属性。具有防篡改属性模式下的普通行存表均为防篡改历史表，不包括外表，临时表，系统表。当该模式下不包含任何表时才可修改防篡改属性。另外，不支持临时表模式。toast表模式、dbe_perf模式、blockchain模式修改防篡改属性。
+
+## 示例
+
+```sql
+--创建模式ds。
+mogdb=# CREATE SCHEMA ds;
+
+--将当前模式ds更名为ds_new。
+mogdb=# ALTER SCHEMA ds RENAME TO ds_new;
+
+--创建用户jack。
+mogdb=# CREATE USER jack PASSWORD 'xxxxxxxxx';
+
+--将DS_NEW的所有者修改为jack。
+mogdb=# ALTER SCHEMA ds_new OWNER TO jack;
+
+--删除用户jack和模式ds_new。
+mogdb=# DROP SCHEMA ds_new;
+mogdb=# DROP USER jack;
+```
+
+## 相关链接
+
+[CREATE SCHEMA](56-CREATE-SCHEMA)，[DROP SCHEMA](91-DROP-SCHEMA)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/16-ALTER-SEQUENCE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/16-ALTER-SEQUENCE.md
new file mode 100644
index 0000000000000000000000000000000000000000..ed6948a03e068b81885793793ed1ab391ade8234
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/16-ALTER-SEQUENCE.md
@@ -0,0 +1,95 @@
+---
+title: ALTER SEQUENCE
+summary: ALTER SEQUENCE
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER SEQUENCE
+
+## 功能描述
+
+修改一个现有的序列的参数。
+
+## 注意事项
+
+- 只有序列的所有者或者被授予了序列ALTER权限的用户才能执行ALTER SEQUENCE命令，系统管理员默认拥有该权限。但要修改序列的所有者，当前用户必须是该序列的所有者或者系统管理员，且该用户是新所有者角色的成员。
+- 当前版本仅支持修改拥有者、归属列和最大值和increment。若要修改其他参数，可以删除重建，并用Setval函数恢复当前值。
+- ALTER SEQUENCE MAXVALUE不支持在事务、函数和存储过程中使用。
+- 修改序列的最大值后，会清空该序列在所有会话的cache。
+- ALTER SEQUENCE会阻塞nextval、setval、currval和lastval的调用。
+
+## 语法格式
+
+- 修改序列归属列
+
+  ```ebnf+diagram
+  AlterSequence ::= ALTER SEQUENCE [ IF EXISTS ] name
+      [MAXVALUE maxvalue | NO MAXVALUE | NOMAXVALUE | CACHE cache]
+      [ OWNED BY { table_name'.'column_name | NONE } ]
+  ```
+
+- 修改序列的拥有者
+
+  ```ebnf+diagram
+  AlterSequence ::= ALTER SEQUENCE [ IF EXISTS ] name OWNER TO new_owner;
+  ```
+
+- 修改increment <a id = 'increment'> </a>
+
+  ```ebnf+diagram
+  AlterSequence ::= ALTER SEQUENCE [ IF EXISTS ] name [ INCREMENT [ BY ] increment ];
+  ```
+
+## 参数说明
+
+- name
+
+  将要修改的序列名称。
+
+- IF EXISTS
+
+  当序列不存在时使用该选项不会出现错误消息，仅有一个通知。
+
+- CACHE
+
+    为了快速访问，而在内存中预先存储序列号的个数。如果没有指定，将保持旧的缓冲值。
+
+- OWNED BY
+
+  将序列和一个表的指定字段进行关联。这样，在删除那个字段或其所在表的时候会自动删除已关联的序列。
+
+  如果序列已经和表有关联后，使用这个选项后新的关联关系会覆盖旧的关联。
+
+  关联的表和序列的所有者必须是同一个用户，并且在同一个模式中。
+
+  使用OWNED BY NONE将删除任何已经存在的关联。
+
+- new_owner
+
+  序列新所有者的用户名。用户要修改序列的所有者，必须是新角色的直接或者间接成员，并且那个角色必须有序列所在模式上的CREATE权限。
+
+## 示例
+
+```sql
+-- 创建一个名为serial的递增序列，从101开始。
+mogdb=# CREATE SEQUENCE serial START 101;
+
+-- 创建一个表,定义默认值。
+mogdb=# CREATE TABLE T1(C1 bigint default nextval('serial'));
+
+-- 将序列serial的归属列变为T1.C1。
+mogdb=# ALTER SEQUENCE serial OWNED BY T1.C1;
+
+-- 修改increment
+mogdb=# ALTER SEQUENCE serial increment by 5;
+
+
+-- 删除序列和表。
+mogdb=# DROP SEQUENCE serial cascade;
+mogdb=# DROP TABLE T1;
+```
+
+## 相关链接
+
+[CREATE SEQUENCE](57-CREATE-SEQUENCE)，[DROP SEQUENCE](92-DROP-SEQUENCE)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/17-ALTER-SERVER.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/17-ALTER-SERVER.md
new file mode 100644
index 0000000000000000000000000000000000000000..269a759763aaff482f621b25bba68eb62cd5ae50
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/17-ALTER-SERVER.md
@@ -0,0 +1,106 @@
+---
+title: ALTER SERVER
+summary: ALTER SERVER
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER SERVER
+
+## 功能描述
+
+增加、修改和删除一个现有server的参数。已有server可以从pg_foreign_server系统表中查询。
+
+## 注意事项
+
+只有SERVER的所有者或者被授予了SERVER的ALTER权限的用户才可以执行ALTER SERVER命令，系统管理员默认拥有该权限。但要修改SERVER的所有者，当前用户必须是该SERVER的所有者或者系统管理员，且该用户是新所有者角色的成员。
+
+## 语法格式
+
+- 修改外部服务的参数。
+
+  ```ebnf+diagram
+  AlterServer ::= ALTER SERVER server_name [ VERSION 'new_version' ]
+    [ OPTIONS ( {[ ADD | SET | DROP ] option ['value']} [, ... ] ) ];
+  ```
+
+  在OPTIONS选项里，ADD、SET和DROP指定要执行的操作，未指定时默认为ADD操作。option和value为对应操作的参数。
+
+- 修改外部服务的名称。
+
+  ```ebnf+diagram
+  AlterServer ::= ALTER SERVER server_name
+     RENAME TO new_name;
+  ```
+
+## 参数说明
+
+- **server_name**
+
+  所修改的server的名称。
+
+- **new_version**
+
+  修改后server的新版本名称。
+
+- **OPTIONS**
+
+    更改该服务器的选项。ADD、SET和 DROP指定要执行的动作。如果没有显式地指定操作， 将会假定为ADD。选项名称必须唯一，名称和值也会使用该服务器的外部数据包装器库进行验证。
+
+  - oracle_fdw支持的options包括：
+
+    - **dbserver**
+
+        远端oracle数据库的连接字符串。
+
+    - **isolation_level** （默认值为serializable）
+
+        oracle数据库的事务隔离级别。
+
+        取值范围: serializable, read_committed , read_only
+
+  - mysql_fdw支持的options包括：
+
+    - **host** （默认值为 127.0.0.1）
+
+        MySQL Server/MariaDB的地址。
+
+    - **port** （默认值为 3306）
+
+        MySQL Server/MariaDB侦听的端口号。
+
+  - postgres_fdw支持的options同libpq支持的连接参数一致，可参考[链接字符](6-connection-characters)。需要注意的是，以下几个options不支持修改：
+
+    - **user**和**password**
+
+        用户名和密码将在创建user mapping时指定
+
+    - **client_encoding**
+
+        将自动获取本地server的编码方式并设置该值
+
+    - **application_name**
+
+        总是设置成postgres_fdw
+
+        除了libpq支持的连接参数外，还额外提供3个options：
+
+    - **use_remote_estimate**
+
+        控制postgres_fdw是否发出EXPLAIN命令以获取运行消耗估算。默认值为false。
+
+    - **fdw_startup_cost**
+
+        执行一个外表扫描时的启动耗时估算。这个值通常包含建立连接、远端对请求的分析和生成计划的耗时。默认值为100。
+
+    - **fdw_typle_cost**
+
+        在远端服务器上对每一个元组进行扫描时的额外消耗。这个值通常表示数据在server间传输的额外消耗。默认值为0.01。
+
+- **new_name**
+
+  修改后server的新名称。
+
+## 相关链接
+
+[CREATE SERVER](58-CREATE-SERVER), [DROP SERVER](93-DROP-SERVER)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/18-ALTER-SESSION.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/18-ALTER-SESSION.md
new file mode 100644
index 0000000000000000000000000000000000000000..7533d6ae7fc2e28b107f7a389b6ac37bddb3fb5b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/18-ALTER-SESSION.md
@@ -0,0 +1,90 @@
+---
+title: ALTER SESSION
+summary: ALTER SESSION
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER SESSION
+
+## 功能描述
+
+ALTER SESSION命令用于定义或修改那些对当前会话有影响的条件或参数。修改后的会话参数会一直保持，直到断开当前会话。
+
+## 注意事项
+
+- 如果执行SET TRANSACTION之前没有执行START TRANSACTION，则事务立即结束，命令无法显示效果。
+- 可以用START TRANSACTION里面声明所需要的transaction_mode(s)的方法来避免使用SET TRANSACTION。
+
+## 语法格式
+
+- 设置会话的事务参数。
+
+  ```ebnf+diagram
+  AlterSession ::= ALTER SESSION SET [ SESSION CHARACTERISTICS AS ] TRANSACTION
+      { ISOLATION LEVEL { READ COMMITTED } | { READ ONLY  | READ WRITE } } [, ...] ;
+  ```
+
+- 设置会话的其他运行时参数。
+
+  ```ebnf+diagram
+  AlterSession ::= ALTER SESSION SET
+      {{config_parameter { { TO  | =  }  { value | DEFAULT }
+        | FROM CURRENT }}
+        | TIME ZONE time_zone
+        | CURRENT_SCHEMA schema
+        | NAMES encoding_name
+        | ROLE role_name PASSWORD 'password'
+        | SESSION AUTHORIZATION { role_name PASSWORD 'password' | DEFAULT }
+        | XML OPTION { DOCUMENT | CONTENT }
+      } ;
+  ```
+
+## 参数说明
+
+修改会话涉及到的参数说明请参见SET语法中的参数说明。
+
+## 示例
+
+```sql
+-- 创建模式ds。
+mogdb=# CREATE SCHEMA ds;
+
+--设置模式搜索路径。
+mogdb=# SET SEARCH_PATH TO ds, public;
+
+--设置日期时间风格为传统的POSTGRES风格（日在月前）。
+mogdb=# SET DATESTYLE TO postgres, dmy;
+
+--设置当前会话的字符编码为UTF8。
+mogdb=# ALTER SESSION SET NAMES 'UTF8';
+
+--设置时区为加州伯克利。
+mogdb=# SET TIME ZONE 'PST8PDT';
+
+--设置时区为意大利。
+mogdb=# SET TIME ZONE 'Europe/Rome';
+
+--设置当前模式。
+mogdb=# ALTER SESSION SET CURRENT_SCHEMA TO tpcds;
+
+--设置XML OPTION为DOCUMENT。
+mogdb=# ALTER SESSION SET XML OPTION DOCUMENT;
+
+--创建角色joe，并设置会话的角色为joe。
+mogdb=# CREATE ROLE joe WITH PASSWORD 'xxxxxxxxx';
+mogdb=# ALTER SESSION SET SESSION AUTHORIZATION joe PASSWORD 'xxxxxxxxx';
+
+--切换到默认用户。
+mogdb=> ALTER SESSION SET SESSION AUTHORIZATION default;
+
+--删除ds模式。
+mogdb=# DROP SCHEMA ds;
+
+--删除joe。
+mogdb=# DROP ROLE joe;
+```
+
+## 相关链接
+
+[SET](127-SET)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/19-ALTER-SYNONYM.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/19-ALTER-SYNONYM.md
new file mode 100644
index 0000000000000000000000000000000000000000..e69350af454dc386bc872658edc3f1bf01d262ab
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/19-ALTER-SYNONYM.md
@@ -0,0 +1,62 @@
+---
+title: ALTER SYNONYM
+summary: ALTER SYNONYM
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER SYNONYM
+
+## 功能描述
+
+修改SYNONYM对象的属性。
+
+## 注意事项
+
+- 目前仅支持修改SYNONYM对象的属主。
+- 只有系统管理员有权限修改SYNONYM对象的属主信息。
+- 新属主必须具有SYNONYM对象所在模式的CREATE权限。
+
+## 语法格式
+
+```ebnf+diagram
+AlterSynonym ::= ALTER SYNONYM synonym_name
+    OWNER TO new_owner;
+```
+
+## 参数描述
+
+- **synonym**
+
+  待修改的同义词名字，可以带模式名。
+
+  取值范围: 字符串，需要符合标识符的命名规范。
+
+- **new_owner**
+
+  同义词对象的新所有者。
+
+  取值范围: 字符串，有效的用户名。
+
+## 示例
+
+```sql
+--创建同义词t1。
+mogdb=#  CREATE OR REPLACE SYNONYM t1 FOR ot.t1;
+
+--创建新用户u1。
+mogdb=# CREATE USER u1 PASSWORD 'user@111';
+
+--修改同义词t1的owner为u1。
+mogdb=# ALTER SYNONYM t1 OWNER TO u1;
+
+--删除同义词t1。
+mogdb=# DROP SYNONYM t1;
+
+--删除用户u1。
+mogdb=# DROP USER u1;
+```
+
+## 相关链接
+
+[CREATE SYNONYM](59-CREATE-SYNONYM)，[DROP SYNONYM](94-DROP-SYNONYM)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/2-ALTER-DATABASE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/2-ALTER-DATABASE.md
new file mode 100644
index 0000000000000000000000000000000000000000..65445262b784e067ab684c171b16704172728f06
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/2-ALTER-DATABASE.md
@@ -0,0 +1,144 @@
+---
+title: ALTER DATABASE
+summary: ALTER DATABASE
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER DATABASE
+
+## 功能描述
+
+修改数据库的属性，包括它的名称、所有者、连接数限制、对象隔离属性等。
+
+## 注意事项
+
+- 只有数据库的所有者或者被授予了数据库ALTER权限的用户才能执行ALTER DATABASE命令，系统管理员默认拥有此权限。针对所要修改属性的不同，还有以下权限约束：
+  - 修改数据库名称，必须拥有CREATEDB权限。
+  - 修改数据库所有者，当前用户必须是该database的所有者或者系统管理员，必须拥有CREATEDB权限，且该用户是新所有者角色的成员。
+  - 修改数据库默认表空间，必须拥有新表空间的CREATE权限。这个语句会从物理上将一个数据库原来缺省表空间上的表和索引移至新的表空间。注意不在缺省表空间的表和索引不受此影响。
+- 不能重命名当前使用的数据库，如果需要重新命名，须连接至其他数据库上。
+
+## 语法格式
+
+- 修改数据库的最大连接数。
+
+  ```ebnf+diagram
+  AlterDatabase ::= ALTER DATABASE database_name
+      [ [ WITH ] CONNECTION LIMIT connlimit ];
+  ```
+
+- 修改数据库名称。
+
+  ```ebnf+diagram
+  AlterDatabase ::= ALTER DATABASE database_name
+      RENAME TO new_name;
+  ```
+
+- 修改数据库所属者。
+
+  ```ebnf+diagram
+  AlterDatabase ::= ALTER DATABASE database_name
+      OWNER TO new_owner;
+  ```
+
+- 修改数据库默认表空间。
+
+  ```ebnf+diagram
+  AlterDatabase ::= ALTER DATABASE database_name
+      SET TABLESPACE new_tablespace;
+  ```
+
+- 修改数据库指定会话参数值。
+
+  ```ebnf+diagram
+  AlterDatabase ::= ALTER DATABASE database_name
+      SET configuration_parameter { { TO | = } { value | DEFAULT } | FROM CURRENT };
+  ```
+
+- 数据库配置参数重置。
+
+  ```ebnf+diagram
+  AlterDatabase ::= ALTER DATABASE database_name RESET
+      { configuration_parameter | ALL };
+  ```
+
+- 修改数据库对象隔离属性。
+
+  ```ebnf+diagram
+  AlterDatabase ::= ALTER DATABASE database_name [ WITH ] { ENABLE | DISABLE } PRIVATE OBJECT;
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  >
+  > - 修改数据库的对象隔离属性时须连接至该数据库，否则无法更改。
+  > - 新创建的数据库，对象隔离属性默认是关闭的。当开启数据库对象隔离属性后，普通用户只能查看有权访问的对象（表、函数、视图、字段等）。对象隔离特性对管理员用户不生效，当开启对象隔离特性后，管理员也可以查看到全量的数据库对象。
+
+## 参数说明
+
+- **database_name**
+
+  需要修改属性的数据库名称。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- **connlimit**
+
+  数据库可以接收的最大并发连接数（管理员用户连接除外）。
+
+  取值范围: 整数，建议填写1~50的整数。-1（缺省）表示没有限制。
+
+- **new_name**
+
+  数据库的新名称。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- **new_owner**
+
+  数据库的新所有者。
+
+  取值范围: 字符串，有效的用户名。
+
+- **new_tablespace**
+
+  数据库新的默认表空间，该表空间为数据库中已经存在的表空间。默认的表空间为pg_default。
+
+  取值范围: 字符串，有效的表空间名。
+
+- **configuration_parameter**
+
+    **value**
+
+    把指定的数据库会话参数值设置为给定的值。如果value是DEFAULT或者RESET，则在新的会话中使用系统的缺省设置。OFF关闭设置。
+
+    取值范围: 字符串
+
+  - DEFAULT
+  - OFF
+  - RESET
+
+- **FROM CURRENT**
+
+  根据当前会话连接的数据库设置该参数的值。
+
+- **RESET configuration_parameter**
+
+  重置指定的数据库会话参数值。
+
+- **RESET ALL**
+
+  重置全部的数据库会话参数值。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 修改数据库默认表空间，会将旧表空间中的所有表和索引转移到新表空间中，该操作不会影响其他非默认表空间中的表和索引。
+> - 修改的数据库会话参数值，将在下一次会话中生效。
+
+## 示例
+
+请参考[CREATE DATABASE](44-CREATE-DATABASE)的示例。
+
+## 相关链接
+
+[CREATE DATABASE](44-CREATE-DATABASE)，[DROP DATABASE](78-DROP-DATABASE)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/20-ALTER-SYSTEM-KILL-SESSION.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/20-ALTER-SYSTEM-KILL-SESSION.md
new file mode 100644
index 0000000000000000000000000000000000000000..b820eabbc9d06e7cc3ecd2cea731f25c9ce0e2a6
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/20-ALTER-SYSTEM-KILL-SESSION.md
@@ -0,0 +1,55 @@
+---
+title: ALTER SYSTEM KILL SESSION
+summary: ALTER SYSTEM KILL SESSION
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER SYSTEM KILL SESSION
+
+## 功能描述
+
+ALTER SYSTEM KILL SESSION命令用于结束一个会话。
+
+## 注意事项
+
+无。
+
+## 语法格式
+
+```ebnf+diagram
+AlterSystemKillSession ::= ALTER SYSTEM KILL SESSION 'session_sid, serial' [ IMMEDIATE ];
+```
+
+## 参数说明
+
+- **session_sid, serial**
+
+  会话的SID和SERIAL（获取方法请参考示例）。
+
+- **IMMEDIATE**
+
+  表明会话将在命令执行后立即结束。
+
+## 示例
+
+```sql
+--查询会话信息。
+mogdb=#
+SELECT sa.sessionid AS sid,0::integer AS serial#,ad.rolname AS username FROM pg_stat_get_activity(NULL) AS sa
+LEFT JOIN pg_authid ad ON(sa.usesysid = ad.oid)WHERE sa.application_name <> 'JobScheduler';
+       sid       | serial# | username
+-----------------+---------+----------
+ 140131075880720 |       0 | omm
+ 140131025549072 |       0 | omm
+ 140131073779472 |       0 | omm
+ 140131071678224 |       0 | omm
+ 140131125774096 |       0 |
+ 140131127875344 |       0 |
+ 140131113629456 |       0 |
+ 140131094742800 |       0 |
+(8 rows)
+
+--结束SID为140131075880720的会话。
+mogdb=#  ALTER SYSTEM KILL SESSION '140131075880720,0' IMMEDIATE;
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/21-ALTER-SYSTEM-SET.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/21-ALTER-SYSTEM-SET.md
new file mode 100644
index 0000000000000000000000000000000000000000..9bfa75c74c045e2720d3e5d05f13fded91df423d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/21-ALTER-SYSTEM-SET.md
@@ -0,0 +1,79 @@
+---
+title: ALTER SYSTEM SET
+summary: ALTER SYSTEM SET
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER SYSTEM SET
+
+## 功能描述
+
+ALTER SYSTEM SET命令用于设置POSTMASTER、SIGHUP、BACKEND级别的GUC参数。此命令会将参数写入配置文件，不同级别生效方式有所不同。
+
+## 注意事项
+
+- 此命令仅限初始用户和拥有sysadmin权限的用户才可使用。
+
+- 不同级别GUC参数生效时间如下：
+  - POSTMASTER级别的GUC参数需要重启后才生效。
+  - BACKEND级别的GUC参数需要会话重新连接后才生效。
+  - SIGHUP级别的GUC参数立即生效（需要等待线程重新加载参数，实际略微有延迟）。
+
+- 通过配置[audit_set_parameter](3-operation-audit)参数，可以配置此操作是否被审计。
+
+- 操作可被备机同步。
+
+- 同gs_guc一致，并不关注数据库是主或备节点、是否只读。
+
+- 不可在事务中执行，因为此操作无法被回滚。
+
+- 部分参数只能由初始用户修改，具体如下：
+
+  ```
+  audit_copy_exec, audit_data_format, audit_database_process, audit_directory, audit_dml_state,
+  audit_dml_state_select, audit_enabled, audit_file_remain_threshold, audit_file_remain_time,
+  audit_function_exec, audit_grant_revoke, audit_login_logout, audit_resource_policy,
+  audit_rotation_interval, audit_rotation_size, audit_set_parameter, audit_space_limit,
+  audit_system_object, audit_user_locked, audit_user_violation,
+  asp_log_directory, config_file, data_directory, enable_access_server_directory,
+  enable_copy_server_files, external_pid_file, hba_file, ident_file, log_directory, perf_directory,
+  query_log_directory, ssl_ca_file, ssl_cert_file, ssl_crl_file, ssl_key_file, stats_temp_directory,
+  unix_socket_directory, unix_socket_group, unix_socket_permissions,
+  krb_caseins_users, krb_server_keyfile, krb_srvname, allow_system_table_mods, enableSeparationOfDuty,
+  modify_initial_password, password_encryption_type, password_policy
+  ```
+
+## 语法格式
+
+```ebnf+diagram
+AlterSystemSet ::= ALTER SYSTEM SET parameter TO value;
+```
+
+## 参数说明
+
+- **parameter**
+
+  GUC参数名。
+
+- **value**
+
+  GUC参数值。
+
+## 示例
+
+```sql
+--设置SIGHUP级别参数audit_enabled。
+mogdb=#  alter system set audit_enabled to off;
+ALTER SYSTEM SET
+mogdb=#  show audit_enabled;
+ audit_enabled
+---------------
+ off
+(1 row)
+
+--设置POSTMASTER级别参数 enable_thread_pool，将在重启之后生效。
+mogdb=# alter system set enable_thread_pool to on;
+NOTICE:  please restart the database for the POSTMASTER level parameter to take effect.
+ALTER SYSTEM SET
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/22-ALTER-TABLE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/22-ALTER-TABLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..9422d65e41b825a36b849c6d7699a80285fc7834
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/22-ALTER-TABLE.md
@@ -0,0 +1,451 @@
+---
+title: ALTER TABLE
+summary: ALTER TABLE
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER TABLE
+
+## 功能描述
+
+修改表，包括修改表的定义、重命名表、重命名表中指定的列、重命名表的约束、设置表的所属模式、添加/更新多个列、打开/关闭行访问控制开关。
+
+## 注意事项
+
+- 只有表的所有者或者被授予了表ALTER权限的用户有权限执行ALTER TABLE命令，系统管理员默认拥有此权限。但要修改表的所有者或者修改表的模式，当前用户必须是该表的所有者或者系统管理员，且该用户是新所有者角色的成员。
+- 不能修改分区表的tablespace，但可以修改分区的tablespace。
+- 不支持修改存储参数ORIENTATION。
+- SET SCHEMA操作不支持修改为系统内部模式，当前仅支持用户模式之间的修改。
+- 列存表只支持PARTIAL CLUSTER KEY、UNIQUE、PRIMARY KEY表级约束，不支持外键等表级约束。
+- 列存表只支持添加字段ADD COLUMN、修改字段的数据类型ALTER TYPE、设置单个字段的收集目标SET STATISTICS、支持更改表名称、支持更改表空间，支持删除字段DROP COLUMN。对于添加的字段和修改的字段类型要求是列存[支持的数据类型](1-numeric-data-types)。ALTER TYPE的USING选项只支持常量表达式和涉及本字段的表达式，暂不支持涉及其他字段的表达式。
+- 列存表支持的字段约束包括NULL、NOT NULL、DEFAULT常量值、UNIQUE和PRIMARY KEY；对字段约束的修改当前只支持对DEFAULT值的修改（SET DEFAULT）和删除（DROP DEFAULT），暂不支持对非空约束NULL/NOT NULL的修改。
+- 不支持增加自增列，或者增加DEFAULT值中包含nextval()表达式的列。
+- 不支持对外表、临时表开启行访问控制开关。
+- 通过约束名删除PRIMARY KEY约束时，不会删除NOT NULL约束，如果有需要，请手动删除NOT NULL约束。
+- 使用JDBC时，支持通过PrepareStatement对DEFAUTL值进行参数化设置。
+
+## 语法格式
+
+- 修改表的定义。
+
+  ```ebnf+diagram
+  AlterTable ::= ALTER TABLE [ IF EXISTS ] { table_name [*] | ONLY table_name | ONLY ( table_name ) }
+      action [, ... ];
+  ```
+
+  其中具体表操作action可以是以下子句之一：
+
+  ```ebnf+diagram
+  action ::= column_clause
+        | ADD table_constraint [ NOT VALID ]
+        | ADD table_constraint_using_index
+        | VALIDATE CONSTRAINT constraint_name
+        | DROP CONSTRAINT [ IF EXISTS ]  constraint_name [ RESTRICT | CASCADE ]
+        | ADD INDEX index_name (column_name)
+        | CLUSTER ON index_name
+        | SET WITHOUT CLUSTER
+        | SET ( {storage_parameter = value} [, ... ] )
+        | RESET ( storage_parameter [, ... ] )
+        | OWNER TO new_owner
+        | SET TABLESPACE new_tablespace
+        | SET {COMPRESS|NOCOMPRESS}
+        | TO { GROUP groupname | NODE ( nodename [, ... ] ) }
+        | ADD NODE ( nodename [, ... ] )
+        | DELETE NODE ( nodename [, ... ] )
+        | DISABLE TRIGGER [ trigger_name | ALL | USER ]
+        | ENABLE TRIGGER [ trigger_name | ALL | USER ]
+        | ENABLE REPLICA TRIGGER trigger_name
+        | ENABLE ALWAYS TRIGGER trigger_name
+        | DISABLE '/' ENABLE [ REPLICA | ALWAYS ] RULE
+        | DISABLE ROW LEVEL SECURITY
+        | ENABLE ROW LEVEL SECURITY
+        | FORCE ROW LEVEL SECURITY
+        | NO FORCE ROW LEVEL SECURITY
+        | ENCRYPTION KEY ROTATION
+        | SET WITH OIDS
+        | SET WITHOUT OIDS
+        | INHERIT parents
+        | NO INHERIT parents
+        | OF type_name
+        | NOT OF
+        | REPLICA IDENTITY { DEFAULT | USING INDEX index_name | FULL | NOTHING }
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  >
+  > - **ADD table_constraint [ NOT VALID ]** 给表增加一个新的约束。
+  > - **ADD table_constraint_using_index** 根据已有唯一索引为表增加主键约束或唯一约束。
+  > - **VALIDATE CONSTRAINT constraint_name** 验证一个使用NOT VALID选项创建的检查类约束，通过扫描全表来保证所有记录都符合约束条件。如果约束已标记为有效时，什么操作也不会发生。
+  > - **DROP CONSTRAINT [ IF EXISTS ] constraint_name [ RESTRICT | CASCADE ]** 删除一个表上的约束。
+  > - **ADD INDEX index_name (column_name)** 在表中column_name字段上创建名为index_name的索引。
+  > - **CLUSTER ON index_name** 为将来的CLUSTER（聚簇）操作选择默认索引。实际上并没有重新盘簇化处理该表。
+  > - **SET WITHOUT CLUSTER** 从表中删除最新使用的CLUSTER索引。这样会影响将来那些没有声明索引的CLUSTER（聚簇）操作。
+  > - **SET ( {storage_parameter = value} [, … ] )** 修改表的一个或多个存储参数。
+  > - **RESET ( storage_parameter [, … ] )** 重置表的一个或多个存储参数。与SET一样，根据参数的不同可能需要重写表才能获得想要的效果。
+  > - **OWNER TO new_owner** 将表、序列、视图的属主改变成指定的用户。
+  > - **SET TABLESPACE new_tablespace** 这种形式将表空间修改为指定的表空间并将相关的数据文件移动到新的表空间。但是表上的所有索引都不会被移动，索引可以通过ALTER INDEX语法的SET TABLESPACE选项来修改索引的表空间。
+  > - **SET {COMPRESS|NOCOMPRESS}** 修改表的压缩特性。表压缩特性的改变只会影响后续批量插入的数据的存储方式，对已有数据的存储毫无影响。也就是说，表压缩特性的修改会导致该表中同时存在着已压缩和未压缩的数据。<a id = 'COMPRESS'> </a>
+  > - **TO { GROUP groupname | NODE ( nodename [, … ] ) }** 此语法仅在扩展模式（GUC参数support_extended_features为on时）下可用。该模式谨慎打开，主要供内部扩容工具使用，一般用户不应使用该模式。
+  > - **ADD NODE ( nodename [, … ] )** 此语法主要供内部扩容工具使用，一般用户不建议使用。
+  > - **DELETE NODE ( nodename [, … ] )** 此语法主要供内部缩容工具使用，一般用户不建议使用。
+  > - **DISABLE TRIGGER [ trigger_name | ALL | USER ]** 禁用trigger_name所表示的单个触发器，或禁用所有触发器，或仅禁用用户触发器（此选项不包括内部生成的约束触发器，例如，可延迟唯一性和排除约束的约束触发器）。 应谨慎使用此功能，因为如果不执行触发器，则无法保证原先期望的约束的完整性。
+  > - **| ENABLE TRIGGER [ trigger_name | ALL | USER ]** 启用trigger_name所表示的单个触发器，或启用所有触发器，或仅启用用户触发器。
+  > - **| ENABLE REPLICA TRIGGER trigger_name** 触发器触发机制受配置变量[session_replication_role](1-statement-behavior)的影响，当复制角色为“origin”（默认值）或“local”时，将触发简单启用的触发器。 配置为ENABLE REPLICA的触发器仅在会话处于“replica”模式时触发。
+  > - **| ENABLE ALWAYS TRIGGER trigger_name** 无论当前复制模式如何，配置为ENABLE ALWAYS的触发器都将触发。
+  > - **| DISABLE/ENABLE [ REPLICA | ALWAYS ] RULE** 配置属于表的重写规则,已禁用的规则对系统来说仍然是可见的，只是在查询重写期间不被应用。语义为关闭/启动规则。由于关系到视图的实现，ON SELECT规则不可禁用。 配置为ENABLE REPLICA的规则将会仅在会话为”replica” 模式时启动，而配置为ENABLE ALWAYS的触发器将总是会启动，不考虑当前复制模式。规则触发机制也受配置变量[session_replication_role](1-statement-behavior)的影响，类似于上述触发器。
+  > - **| DISABLE/ENABLE ROW LEVEL SECURITY** 开启或关闭表的行访问控制开关。 当开启行访问控制开关时，如果未在该数据表定义相关行访问控制策略，数据表的行级访问将不受影响；如果关闭表的行访问控制开关，即使定义了行访问控制策略，数据表的行访问也不受影响。详细信息参见[CREATE ROW LEVEL SECURITY POLICY](52-CREATE-ROW-LEVEL-SECURITY-POLICY)章节。
+  > - **| NO FORCE/FORCE ROW LEVEL SECURITY** 强制开启或关闭表的行访问控制开关。 默认情况，表所有者不受行访问控制特性影响，但当强制开启表的行访问控制开关时，表的所有者（不包含系统管理员用户）会受影响。系统管理员可以绕过所有的行访问控制策略，不受影响。
+  > - **| REPLICA IDENTITY {DEFAULT | USING INDEX index_name | FULL | NOTHING}** 调整逻辑复制时写入WAL日志中的信息量，该选项仅在wal_level配置为logical时才有效。 当原数据表发生更新时，默认的逻辑复制流只包含主键的历史记录，如果需要输出所需字段更新或删除的历史记录，可修改本参数。“DEFAULT”（非系统表的默认值）会记录主键字段的旧值。“USING INDEX”会记录名为index_name索引包含的字段的旧值，索引的所有列必须NOT NULL。“FULL”记录了所有列的旧值。“NOTHING”（系统表默认值）不记录旧值的信息。
+  > - **SET WITH OIDS** 在资料表中增加了一个OID系统栏位。如果资料表中已经有OID，则此语法什么都不改变。
+  > - **SET WITHOUT OIDS** 从资料表中一处OID系统栏位。如果资料表中没有OID，则此语法什么都不改变。
+  > - **INHERIT parent_table** 将目标资料表加到指定的父资料表中成为新的子资料表。之后，针对父资料表的查询将会包含目标资料表的资料。要作为子资料表加入前，目标资料表必须已经包含父资料表的所有栏位。这些栏位必须具有可匹配的资料类别，并且如果他们在父资料表中具有NOT NULL的限制条件，那么他们必须在子资料表中也具有NOT NULL的限制条件。对于父资料表的所有CHECK限制条件，必须还有相对应的子资料表限制条件，除非父资料表中标记为不可继承。
+  > - **NO INHERIT parent_table** 从指定的父资料表的子资料表中产出目标资料表。针对父资料表的查询将不再包含从目标资料表中所产生的记录。
+  > - **OF type_name** 将表连接至一种复合类型，与CREATE TABLE OF选项创建表一样。表的字段的名称和类型必须精确匹配复合类型中的定义，不过oid系统字段允许不一样。表不能是从任何其他表继承的。这些限制确保CREATE TABLE OF选项允许一个相同的表定义。
+  > - **NOT OF** 将一个与某类型进行关联的表进行关联的解除。
+  > - **REPLICA IDENTITY { DEFAULT | USING INDEX index_name | FULL | NOTHING }** DEFAULT记录主键的列的旧值。USING INDEX记录命名索引覆盖的列的旧值，这些纸必须是唯一的，不局部的，不可延迟的，并且仅包括标记为NOT NULL的列。FULL记录该行中所有列的旧值。NOTHING不记录有关旧行的信息。在所有情况下，除非该行的新旧版本中至少要记录的列之一不同，否则不会记录任何旧值。
+
+  - 其中列相关的操作column_clause可以是以下子句之一：
+
+    ```ebnf+diagram
+    column_clause ::= ADD [ COLUMN ] column_name data_type [ compress_mode ] [ COLLATE collation ] [ column_constraint [ ... ] ]
+    | MODIFY column_name data_type
+    | MODIFY column_name [ CONSTRAINT constraint_name ] NOT NULL [ ENABLE ]
+    | MODIFY column_name [ CONSTRAINT constraint_name ] NULL
+    | DROP [ COLUMN ] [ IF EXISTS ] column_name [ RESTRICT | CASCADE ]
+    | ALTER [ COLUMN ] column_name [ SET DATA ] TYPE data_type [ COLLATE collation ] [ USING expression ]
+    | ALTER [ COLUMN ] column_name { SET DEFAULT expression | DROP DEFAULT }
+    | ALTER [ COLUMN ] column_name { SET | DROP } NOT NULL
+    | ALTER [ COLUMN ] column_name SET STATISTICS [PERCENT] integer
+    | ADD STATISTICS (( column_1_name, column_2_name [, ...] ))
+    | DELETE STATISTICS (( column_1_name, column_2_name [, ...] ))
+    | ALTER [ COLUMN ] column_name SET ( {attribute_option = value} [, ... ] )
+    | ALTER [ COLUMN ] column_name RESET ( attribute_option [, ... ] )
+    | ALTER [ COLUMN ] column_name SET STORAGE { PLAIN | EXTERNAL | EXTENDED | MAIN }
+    ```
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+    >
+    > - **ADD [ COLUMN ] column_name data_type [ compress_mode ] [ COLLATE collation ] [ column_constraint [ … ] ]** 向表中增加一个新的字段。用ADD COLUMN增加一个字段，所有表中现有行都初始化为该字段的缺省值（如果没有声明DEFAULT子句，值为NULL）。
+    >
+    > - **ADD ( { column_name data_type [ compress_mode ] } [, …] )** 向表中增加多列。
+    >
+    > - **MODIFY ( { column_name data_type | column_name [ CONSTRAINT constraint_name ] NOT NULL [ ENABLE ] | column_name [ CONSTRAINT constraint_name ] NULL } [, …] )** 修改表已存在字段的数据类型。
+    >
+    > - **DROP [ COLUMN ] [ IF EXISTS ] column_name [ RESTRICT | CASCADE ]** 从表中删除一个字段，和这个字段相关的索引和表约束也会被自动删除。如果任何表之外的对象依赖于这个字段，必须声明CASCADE ，比如视图。 DROP COLUMN命令并不是物理上把字段删除，而只是简单地把它标记为对SQL操作不可见。随后对该表的插入和更新将在该字段存储一个NULL。因此，删除一个字段是很快的，但是它不会立即释放表在磁盘上的空间，因为被删除了的字段占据的空间还没有回收。这些空间将在执行VACUUM时而得到回收。
+    >
+    > - **ALTER [ COLUMN ] column_name [ SET DATA ] TYPE data_type [ COLLATE collation ] [ USING expression ]** 改变表字段的数据类型。该字段涉及的索引和简单的表约束将被自动地转换为使用新的字段类型，方法是重新分析最初提供的表达式。 ALTER TYPE要求重写整个表的特性有时候是一个优点，因为重写的过程消除了表中没用的空间。比如，要想立刻回收被一个已经删除的字段占据的空间，最快的方法是
+    >
+    >   ```sql
+    >   ALTER TABLE table ALTER COLUMN anycol TYPE anytype;
+    >   ```
+    >
+    >   这里的anycol是任何在表中还存在的字段，而anytype是和该字段的原类型一样的类型。这样的结果是在表上没有任何可见的语意的变化，但是这个命令强制重写，这样就删除了不再使用的数据。
+    >
+    > - **ALTER [ COLUMN ] column_name { SET DEFAULT expression | DROP DEFAULT }** 为一个字段设置或者删除缺省值。请注意缺省值只应用于随后的INSERT命令，它们不会修改表中已经存在的行。也可以为视图创建缺省，这个时候它们是在视图的ON INSERT规则应用之前插入到INSERT句中的。
+    >
+    > - **ALTER [ COLUMN ] column_name { SET | DROP } NOT NULL** 修改一个字段是否允许NULL值或者拒绝NULL值。如果表在字段中包含非NULL，则只能使用SET NOT NULL。
+    >
+    > - **ALTER [ COLUMN ] column_name SET STATISTICS [PERCENT] integer** 为随后的ANALYZE操作设置针对每个字段的统计收集目标。目标的范围可以在0到10000之内设置。设置为-1时表示重新恢复到使用系统缺省的统计目标。
+    >
+    > - **{ADD | DELETE} STATISTICS ((column_1_name, column_2_name [, …]))** 用于添加和删除多列统计信息声明（不实际进行多列统计信息收集），以便在后续进行全表或全库analyze时进行多列统计信息收集。每组多列统计信息最多支持32列。不支持添加/删除多列统计信息声明的表：系统表、外表。
+    >
+    > - **ALTER [ COLUMN ] column_name SET ( {attribute_option = value} [, … ] )** **ALTER [ COLUMN ] column_name RESET ( attribute_option [, … ] )** 设置/重置属性选项。 目前，属性选项只定义了n_distinct和n_distinct_inherited。n_distinct影响表本身的统计值，而n_distinct_inherited影响表及其继承子表的统计。目前，只支持SET/RESET n_distinct参数，禁止SET/RESET n_distinct_inherited参数。
+    >
+    > - **ALTER [ COLUMN ] column_name SET STORAGE { PLAIN | EXTERNAL | EXTENDED | MAIN }** 为一个字段设置存储模式。这个设置控制这个字段是内联保存还是保存在一个附属的表里，以及数据是否要压缩。仅支持对行存表的设置；对列存表没有意义，执行时报错。SET STORAGE本身并不改变表上的任何东西，只是设置将来的表操作时，建议使用的策略。
+
+  - 其中列约束column_constraint为：
+
+    ```ebnf+diagram
+    column_constraint ::= [ CONSTRAINT constraint_name ]
+        { NOT NULL |
+        NULL |
+        CHECK ( expression ) |
+        DEFAULT default_expr  |
+        UNIQUE index_parameters |
+        PRIMARY KEY index_parameters |
+        ENCRYPTED WITH ( COLUMN_ENCRYPTION_KEY = column_encryption_key, ENCRYPTION_TYPE = encryption_type_value ) |
+        REFERENCES reftable [ ( refcolumn ) ] [ MATCH FULL | MATCH PARTIAL | MATCH SIMPLE ]
+            [ ON DELETE action ] [ ON UPDATE action ] }    [ DEFERRABLE | NOT DEFERRABLE | INITIALLY DEFERRED | INITIALLY IMMEDIATE ]
+    ```
+
+  - 其中压缩可选项compress_mode为：
+
+    ```ebnf+diagram
+    compress_mode ::= [ DELTA | PREFIX | DICTIONARY | NUMSTR | NOCOMPRESS ]
+    ```
+
+  - 其中根据已有唯一索引为表增加主键约束或唯一约束table_constraint_using_index为：
+
+    ```ebnf+diagram
+    table_constraint_using_index ::= [ CONSTRAINT constraint_name ]
+        { UNIQUE | PRIMARY KEY } USING INDEX index_name
+        [ DEFERRABLE | NOT DEFERRABLE | INITIALLY DEFERRED | INITIALLY IMMEDIATE ]
+    ```
+
+  - 其中表约束table_constraint为：
+
+    ```ebnf+diagram
+    table_constraint ::= [ CONSTRAINT constraint_name ]
+                { CHECK ( expression ) |
+                  UNIQUE ( column_name [, ... ] ) index_parameters |
+                  PRIMARY KEY ( column_name [, ... ] ) index_parameters |
+                  PARTIAL CLUSTER KEY ( column_name [, ... ] )
+                  FOREIGN KEY ( column_name [, ... ] )  REFERENCES reftable [ ( refcolumn [, ... ] ) ]
+                      [ MATCH FULL | MATCH PARTIAL | MATCH SIMPLE ] [ ON DELETE action ] [ ON UPDATE action ] }
+                [ DEFERRABLE | NOT DEFERRABLE | INITIALLY DEFERRED | INITIALLY IMMEDIATE ]
+    ```
+
+    其中索引参数index_parameters为：
+
+    ```ebnf+diagram
+    index_parameters ::= [ WITH ( {storage_parameter = value} [, ... ] ) ]
+        [ USING INDEX TABLESPACE tablespace_name ]
+    ```
+
+- 重命名表。对名称的修改不会影响所存储的数据。
+
+  ```ebnf+diagram
+  AlterTable ::= ALTER TABLE [ IF EXISTS ] table_name
+      RENAME TO new_table_name;
+  ```
+
+- 重命名表中指定的列。
+
+  ```ebnf+diagram
+  AlterTable ::= ALTER TABLE [ IF EXISTS ] { table_name [*] | ONLY table_name | ONLY ( table_name )}
+      RENAME [ COLUMN ] column_name TO new_column_name;
+  ```
+
+- 重命名表的约束。
+
+  ```ebnf+diagram
+  AlterTable ::= ALTER TABLE [ IF EXISTS ] { table_name [*] | ONLY table_name | ONLY ( table_name ) }
+      RENAME CONSTRAINT constraint_name TO new_constraint_name;
+  ```
+
+- 设置表的所属模式。
+
+  ```ebnf+diagram
+  AlterTable ::= ALTER TABLE [ IF EXISTS ] table_name
+      SET SCHEMA new_schema;
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  >
+  > - 这种形式把表移动到另外一个模式。相关的索引、约束都跟着移动。目前序列不支持改变schema。 若该表拥有序列，需要将序列删除，重建，或者取消拥有关系， 才能将表schema更改成功。
+  > - 要修改一个表的模式，用户必须在新模式上拥有CREATE权限。要把该表添加为一个父表的新子表，用户必须同时又是父表的所有者。要修改所有者，用户还必须是新的所有角色的直接或间接成员，并且该成员必须在此表的模式上有CREATE权限。这些限制规定了该用户不能做出了重建和删除表之外的事情。不过，系统管理员可以以任何方式修改任意表的所有权限。
+  > - 除了RENAME和SET SCHEMA之外所有动作都可以捆绑在一个经过多次修改的列表中并行使用。比如，可以在一个命令里增加几个字段或修改几个字段的类型。对于大表，此种操作带来的效率提升更明显，原因在于只需要对该大表做一次处理。
+  > - 增加一个CHECK或NOT NULL约束将会扫描该表，以保证现有的行符合约束要求。
+  > - 用一个非空缺省值增加一个字段或者改变一个字段的现有类型会重写整个表。对于大表来说，这个操作可能会花很长时间，并且它还临时需要两倍的磁盘空间。
+
+- 添加多个列。
+
+  ```ebnf+diagram
+  AlterTable ::= ALTER TABLE [ IF EXISTS ] table_name
+      ADD ( { column_name data_type [ compress_mode ] [ COLLATE collation ] [ column_constraint [ ... ] ]} [, ...] );
+  ```
+
+- 更新多个列。
+
+  ```ebnf+diagram
+  AlterTable ::= ALTER TABLE [ IF EXISTS ] table_name
+      MODIFY ( { column_name data_type | column_name [ CONSTRAINT constraint_name ] NOT NULL [ ENABLE ] | column_name [ CONSTRAINT constraint_name ] NULL } [, ...] );
+  ```
+
+## 参数说明
+
+- **IF EXISTS**
+
+  如果不存在相同名称的表，不会抛出一个错误，而会发出一个通知，告知表不存在。
+
+- **table_name [\*] | ONLY table_name | ONLY ( table_name )**
+
+  table_name是需要修改的表名。
+
+  若声明了ONLY选项，则只有那个表被更改。若未声明ONLY，该表及其所有子表都将会被更改。另外，可以在表名称后面显示地增加*选项来指定包括子表，即表示所有后代表都被扫描，这是默认行为。
+
+- **constraint_name**
+
+  要删除的现有约束的名称。
+
+- **index_name**
+
+  索引名称。
+
+- **storage_parameter**
+
+  表的存储参数的名称。
+
+  创建索引新增一个选项：
+
+  - parallel_workers（int类型）
+
+      取值范围: [0,32]，0表示关闭并发。
+
+      表示创建索引时起的bgworker线程数量，例如2就表示将会起2个bgworker线程并发创建索引。
+
+      如果未设置，启动bgworker线程数量与表大小相关，一般不超过4个线程。
+
+- **new_owner**
+
+  表新拥有者的名称。
+
+- **new_tablespace**
+
+  表所属新的表空间名称。
+
+- **column_name**，**column_1_name， column_2_name**
+
+  现存的或新字段的名称。
+
+- **data_type**
+
+  新字段的类型，或者现存字段的新类型。
+
+- **compress_mode**
+
+  表字段的压缩可选项。该子句指定该字段优先使用的压缩算法。
+
+- **collation**
+
+  字段排序规则名称。可选字段COLLATE指定了新字段的排序规则，如果省略，排序规则为新字段的默认类型。排序规则可以使用“select * from pg_collation;”命令从pg_collation系统表中查询，默认的排序规则为查询结果中以default开始的行。
+
+- **USING expression**
+
+  USING子句声明如何从旧的字段值里计算新的字段值；如果省略，缺省从旧类型向新类型的赋值转换。如果从旧数据类型到新类型没有隐含或者赋值的转换，则必须提供一个USING子句。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  >
+  > ALTER TYPE的USING选项实际上可以声明涉及该行旧值的任何表达式，即它可以引用除了正在被转换的字段之外其他的字段。这样，就可以用ALTER TYPE语法做非常普遍性的转换。因为这个灵活性，USING表达式并没有作用于该字段的缺省值（如果有的话)，结果可能不是缺省表达式要求的常量表达式。这就意味着如果从旧类型到新类型没有隐含或者赋值转换的话，即使存在USING子句，ALTER TYPE也可能无法把缺省值转换成新的类型。在这种情况下，应该用DROP DEFAULT先删除缺省，执行ALTER TYPE，然后使用SET DEFAULT增加一个合适的新缺省值。类似的考虑也适用于涉及该字段的索引和约束。
+
+- **NOT NULL | NULL**
+
+  设置列是否允许空值。
+
+- **integer**
+
+  带符号的整数常值。当使用PERCENT时表示按照表数据的百分比收集统计信息，integer的取值范围为0-100。
+
+- **attribute_option**
+
+  属性选项。
+
+- **PLAIN | EXTERNAL | EXTENDED | MAIN**
+
+  字段存储模式。
+
+  - PLAIN必需用于定长的数值（比如integer）并且是内联的、不压缩的。
+  - MAIN用于内联、可压缩的数据。
+  - EXTERNAL用于外部保存、不压缩的数据。使用EXTERNAL将令在text和bytea字段上的子字符串操作更快，但付出的代价是增加了存储空间。
+  - EXTENDED用于外部的压缩数据，EXTENDED是大多数支持非PLAIN存储的数据的缺省。
+
+- **CHECK ( expression )**
+
+  每次将要插入的新行或者将要被更新的行必须使表达式结果为真才能成功，否则会抛出一个异常并且不会修改数据库。
+
+  声明为字段约束的检查约束应该只引用该字段的数值，而在表约束里出现的表达式可以引用多个字段。
+
+  目前，CHECK表达式不能包含子查询也不能引用除当前行字段之外的变量。
+
+- **DEFAULT default_expr**
+
+  给字段指定缺省值。
+
+  缺省表达式的数据类型必须和字段类型匹配。
+
+  缺省表达式将被用于任何未声明该字段数值的插入操作。如果没有指定缺省值则缺省值为NULL 。
+
+- **UNIQUE index_parameters**
+
+  **UNIQUE ( column_name [, … ] ) index_parameters**
+
+  UNIQUE约束表示表里的一个或多个字段的组合必须在全表范围内唯一。
+
+- **PRIMARY KEY index_parameters**
+
+  **PRIMARY KEY ( column_name [, … ] ) index_parameters**
+
+  主键约束表明表中的一个或者一些字段只能包含唯一（不重复）的非NULL值。
+
+- **REFERENCES reftable [ ( refcolum ) ] [ MATCH matchtype ] [ ON DELETE action ] [ ON UPDATE action ] (column constraint)**
+
+    **FOREIGN KEY ( column_name [, ... ] ) REFERENCES reftable [ ( refcolumn [, ... ] ) ] [ MATCH matchtype ] [ ON DELETE action ] [ ON UPDATE action ] (table constraint)**
+
+    外键约束要求新表中一列或多列构成的组应该只包含、匹配被参考表中被参考字段值。若省略refcolum，则将使用reftable的主键。被参考列应该是被参考表中的唯一字段或主键。外键约束不能被定义在临时表和永久表之间。
+
+    参考字段与被参考字段之间存在三种类型匹配，分别是：
+
+  - MATCH FULL：不允许一个多字段外键的字段为NULL，除非全部外键字段都是NULL。
+  - MATCH SIMPLE（缺省）：允许任意外键字段为NULL。
+  - MATCH PARTIAL：目前暂不支持。
+
+    另外，当被参考表中的数据发生改变时，某些操作也会在新表对应字段的数据上执行。ON DELETE子句声明当被参考表中的被参考行被删除时要执行的操作。ON UPDATE子句声明当被参考表中的被参考字段数据更新时要执行的操作。对于ON DELETE子句、ON UPDATE子句的可能动作：
+
+  - NO ACTION（缺省）：删除或更新时，创建一个表明违反外键约束的错误。若约束可推迟，且若仍存在任何引用行，那这个错误将会在检查约束的时候产生。
+  - RESTRICT：删除或更新时，创建一个表明违反外键约束的错误。与NO ACTION相同，只是动作不可推迟。
+  - CASCADE：删除新表中任何引用了被删除行的行，或更新新表中引用行的字段值为被参考字段的新值。
+  - SET NULL：设置引用字段为NULL。
+  - SET DEFAULT：设置引用字段为它们的缺省值。
+
+- **DEFERRABLE | NOT DEFERRABLE | INITIALLY DEFERRED | INITIALLY IMMEDIATE**
+
+  设置该约束是否可推迟。
+
+  - DEFERRABLE：可以推迟到事务结尾使用SET CONSTRAINTS命令检查。
+  - NOT DEFERRABLE：在每条命令之后马上检查。
+  - INITIALLY IMMEDIATE：那么每条语句之后就立即检查它。
+  - INITIALLY DEFERRED：只有在事务结尾才检查它。
+
+- **PARTIAL CLUSTER KEY**
+
+    局部聚簇存储，列存表导入数据时按照指定的列(单列或多列)，进行局部排序。
+
+- **WITH ( {storage_parameter = value} [, … ] )**
+
+  为表或索引指定一个可选的存储参数。
+
+- **tablespace_name**
+
+  索引所在表空间的名称。
+
+- **COMPRESS|NOCOMPRESS**
+
+  - NOCOMPRESS：如果指定关键字NOCOMPRESS则不会修改表的现有压缩特性。
+  - COMPRESS：如果指定COMPRESS关键字，则对该表进行批量插入元组时触发该特性。
+
+- **new_table_name**
+
+  修改后新的表名称。
+
+- **new_column_name**
+
+  表中指定列修改后新的列名称。
+
+- **new_constraint_name**
+
+  修改后表约束的新名称。
+
+- **new_schema**
+
+  修改后新的模式名称。
+
+- **CASCADE**
+
+  级联删除依赖于被依赖字段或者约束的对象（比如引用该字段的视图）。
+
+- **RESTRICT**
+
+  如果字段或者约束还有任何依赖的对象，则拒绝删除该字段。这是缺省行为。
+
+- **schema_name**
+
+  表所在的模式名称。
+
+## 示例
+
+请参考[CREATE TABLE](60-CREATE-TABLE)的示例。
+
+## 相关链接
+
+[CREATE TABLE](60-CREATE-TABLE)，[DROP TABLE](95-DROP-TABLE)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/23-ALTER-TABLE-PARTITION.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/23-ALTER-TABLE-PARTITION.md
new file mode 100644
index 0000000000000000000000000000000000000000..564f986d3d3bd7edb8bf749b39bb1cddc131fbdc
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/23-ALTER-TABLE-PARTITION.md
@@ -0,0 +1,281 @@
+---
+title: ALTER TABLE PARTITION
+summary: ALTER TABLE PARTITION
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER TABLE PARTITION
+
+## 功能描述
+
+修改表分区，包括增删分区、切割分区、合成分区以及修改分区属性等。
+
+## 注意事项
+
+- 添加分区的表空间不能是PG_GLOBAL。
+- 添加分区的名称不能与该分区表已有分区的名称相同。
+- 添加分区的分区键值要和分区表的分区键的类型一致，且要大于分区表中最后一个范围分区的上边界。
+- 如果目标分区表中已有分区数达到了最大值，则不能继续添加分区（范围分区表的分区数最大值是32767，哈希/列表分区表最大值是64）。
+- 当分区表只有一个分区时，不能删除该分区。
+- 选择分区使用PARTITION FOR()，括号里指定值个数应该与定义分区时使用的列个数相同，并且一一对应。
+- Value分区表不支持相应的Alter Partition操作。
+- 列存分区表不支持切割分区。
+- 间隔分区表不支持添加分区。
+- 哈希分区表不支持切割分区，不支持合成分区，不支持添加和删除分区。
+- 列表分区表不支持切割分区，不支持合成分区。
+- 只有分区表的所有者或者被授予了分区表ALTER权限的用户有权限执行ALTER TABLE PARTITION命令，系统管理员默认拥有此权限。
+
+## 语法格式
+
+- 修改表分区主语法。
+
+  ```ebnf+diagram
+  AlterTable ::= ALTER TABLE [ IF EXISTS ] { table_name  [*] | ONLY table_name | ONLY ( table_name  )}
+      action [, ... ];
+  ```
+
+  其中action统指如下分区维护子语法。当存在多个分区维护子句时，保证了分区的连续性，无论这些子句的排序如何，MogDB总会先执行DROP PARTITION再执行ADD PARTITION操作，最后顺序执行其它分区维护操作。
+
+  ```ebnf+diagram
+  action ::= move_clause  |
+      exchange_clause  |
+      row_clause  |
+      merge_clause  |
+      modify_clause  |
+      split_clause  |
+      add_clause  |
+      drop_clause  |
+      truncate_clause
+  ```
+
+- move_clause子语法用于移动分区到新的表空间。
+
+    ```ebnf+diagram
+    move_clause ::= MOVE PARTITION { partion_name | FOR ( partition_value [, ...] ) } TABLESPACE tablespacename
+    ```
+
+- exchange_clause子语法用于把普通表的数据迁移到指定的分区。
+
+    ```ebnf+diagram
+    exchange_clause ::= EXCHANGE PARTITION { ( partition_name ) | FOR ( partition_value [, ...] ) }
+        WITH TABLE {[ ONLY ] ordinary_table_name | ordinary_table_name * | ONLY ( ordinary_table_name )}
+        [ { WITH | WITHOUT } VALIDATION ] [ VERBOSE ] [ UPDATE GLOBAL INDEX ]
+    ```
+
+    进行交换的普通表和分区必须满足如下条件：
+
+  - 普通表和分区的列数目相同，对应列的信息严格一致，包括：列名、列的数据类型、列约束、列的Collation信息、列的存储参数、列的压缩信息等。
+  - 普通表和分区的表压缩信息严格一致。
+  - 普通表和分区的索引个数相同，且对应索引的信息严格一致。
+  - 普通表和分区的表约束个数相同，且对应表约束的信息严格一致。
+  - 普通表不可以是临时表，分区表只能是范围分区表、列表分区表、哈希分区表。
+  - 普通表和分区表上不可以有动态数据脱敏，行访问控制约束。
+  - 列表分区表，哈希分区表不能是列存储。
+
+    > **须知：**
+    >
+    > - 完成交换后，普通表和分区的数据被置换，同时普通表和分区的表空间信息被置换。此时，普通表和分区的统计信息变得不可靠，需要对普通表和分区重新执行analyze。
+    > - 由于非分区键不能建立本地唯一索引，只能建立全局唯一索引，所以如果普通表含有唯一索引时，会导致不能交换数据。
+
+- row_clause子语法用于设置分区表的行迁移开关。
+
+    ```ebnf+diagram
+    row_clause ::= { ENABLE | DISABLE } ROW MOVEMENT
+    ```
+
+- merge_clause子语法用于把多个分区合并成一个分区。
+
+    ```ebnf+diagram
+    merge_clause ::= MERGE PARTITIONS { partition_name } [, ...] INTO PARTITION partition_name
+        [ TABLESPACE tablespacename ] [ UPDATE GLOBAL INDEX ]
+    ```
+
+- modify_clause子语法用于设置分区索引是否可用。
+
+    ```ebnf+diagram
+    modify_clause ::= MODIFY PARTITION partition_name { UNUSABLE LOCAL INDEXES | REBUILD UNUSABLE LOCAL INDEXES }
+    ```
+
+- split_clause子语法用于把一个分区切割成多个分区。
+
+    ```ebnf+diagram
+    split_clause ::= SPLIT PARTITION { partition_name | FOR ( partition_value [, ...] ) } { split_point_clause | no_split_point_clause } [ UPDATE GLOBAL INDEX ]
+    ```
+
+  - 指定切割点split_point_clause的语法为。
+
+      ```ebnf+diagram
+      split_point_clause ::= AT ( partition_value ) INTO ( PARTITION partition_name [ TABLESPACE tablespacename ] , PARTITION partition_name [ TABLESPACE tablespacename ] )
+      ```
+
+      > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+      >
+      > - 列存分区表不支持切割分区。
+      > - 切割点的大小要位于正在被切割的分区的分区键范围内，指定切割点的方式只能把一个分区切割成两个新分区。
+
+  - 不指定切割点no_split_point_clause的语法为。
+
+      ```ebnf+diagram
+      no_split_point_clause ::= INTO { ( partition_less_than_item [, ...] ) | ( partition_start_end_item [, ...] ) }
+      ```
+
+      > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+      >
+      > - 不指定切割点的方式，partition_less_than_item指定的第一个新分区的分区键要大于正在被切割的分区的前一个分区（如果存在的话）的分区键，partition_less_than_item指定的最后一个分区的分区键要等于正在被切割的分区的分区键大小。
+      > - 不指定切割点的方式，partition_start_end_item指定的第一个新分区的起始点（如果存在的话）必须等于正在被切割的分区的前一个分区（如果存在的话）的分区键，partition_start_end_item指定的最后一个分区的终止点（如果存在的话）必须等于正在被切割的分区的分区键。
+      > - partition_less_than_item支持的分区键个数最多为4，而partition_start_end_item仅支持1个分区键，其支持的数据类型参见[CREATE TABLE PARTITON](62-CREATE-TABLE-PARTITION)。
+      > - 在同一语句中partition_less_than_item和partition_start_end_item两者不可同时使用；不同split语句之间没有限制。
+
+  - 分区项partition_less_than_item的语法为：
+
+      ```ebnf+diagram
+      partition_less_than_item ::= PARTITION partition_name VALUES LESS THAN ( { partition_value | MAXVALUE }  [, ...] )
+          [ TABLESPACE tablespacename ]
+      ```
+
+  - 分区项partition_start_end_item的语法为，其约束参见[CREATE TABLE PARTITON](62-CREATE-TABLE-PARTITION)。
+
+      ```ebnf+diagram
+      partition_start_end_item ::= PARTITION partition_name {
+              {START(partition_value) END (partition_value) EVERY (interval_value)} |
+              {START(partition_value) END ({partition_value | MAXVALUE})} |
+              {START(partition_value)} |
+              {END({partition_value | MAXVALUE})}
+      } [TABLESPACE tablespace_name]
+
+      ```
+
+- add_clause子语法用于为指定的分区表添加一个或多个分区。
+
+    ```ebnf+diagram
+    add_clause ::= ADD PARTITION ( partition_col1_name = partition_col1_value [, partition_col2_name = partition_col2_value ] [, ...] )
+                [ LOCATION 'location1' ]
+                [ PARTITION (partition_colA_name = partition_colA_value [, partition_colB_name = partition_colB_value ] [, ...] ) ]
+                [ LOCATION 'location2' ]
+                ADD {partition_less_than_item | partition_start_end_item | partition_list_item }
+    ```
+
+    分区项partition_list_item的语法如下。
+
+    ```ebnf+diagram
+    partition_list_item ::= PARTITION partition_name VALUES (list_values_clause)
+        [ TABLESPACE tablespacename ]
+    ```
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+    >
+    > - partition_list_item仅支持的1个分区键，其支持的数据类型参见**PARTITION BY LIST(partit…**。
+    > - 间隔/哈希分区表不支持添加分区。
+
+- drop_clause子语法用于删除分区表中的指定分区。
+
+    ```ebnf+diagram
+    drop_clause ::= DROP PARTITION  { partition_name | FOR (  partition_value [, ...] )  } [ UPDATE GLOBAL INDEX ]
+    ```
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+    >
+    > - 哈希分区表不支持删除分区。
+    > - 列表分区表仅支持通过子分区名称删除子分区。
+
+- truncate_clause子语法用于清空分区表中的指定分区。
+
+    ```ebnf+diagram
+    truncate_clause ::= TRUNCATE PARTITION  { partition_name | FOR (  partition_value [, ...] )  } [ UPDATE GLOBAL INDEX ]
+    ```
+
+- 修改表分区名称的语法。
+
+  ```ebnf+diagram
+  AlterTable ::= ALTER TABLE [ IF EXISTS ] { table_name [*] | ONLY table_name | ONLY ( table_name  )}
+      RENAME PARTITION { partion_name | FOR ( partition_value [, ...] ) } TO partition_new_name;
+  ```
+
+## 参数说明
+
+- **table_name**
+
+  分区表名。
+
+  取值范围: 已存在的分区表名。
+
+- **partition_name**
+
+  分区名。
+
+  取值范围: 已存在的分区名。
+
+- **tablespacename**
+
+  指定分区要移动到哪个表空间。
+
+  取值范围: 已存在的表空间名。
+
+- **partition_value**
+
+  分区键值。
+
+  通过PARTITION FOR ( partition_value [, …] )子句指定的这一组值，可以唯一确定一个分区。
+
+  取值范围: 需要进行重命名的分区的分区键的取值范围。
+
+- **UNUSABLE LOCAL INDEXES**
+
+  设置该分区上的所有索引不可用。
+
+- **REBUILD UNUSABLE LOCAL INDEXES**
+
+  重建该分区上的所有索引。
+
+- **ENABLE/DISABLE ROW MOVEMET**
+
+    行迁移开关。
+
+    如果进行UPDATE操作时，更新了元组在分区键上的值，造成了该元组所在分区发生变化，就会根据该开关给出报错信息，或者进行元组在分区间的转移。
+
+    取值范围:
+
+  - ENABLE：打开行迁移开关。
+  - DISABLE：关闭行迁移开关。
+
+    默认是打开状态。
+
+- **ordinary_table_name**
+
+  进行迁移的普通表的名称。
+
+  取值范围: 已存在的普通表名。
+
+- **{ WITH | WITHOUT } VALIDATION**
+
+    在进行数据迁移时，是否检查普通表中的数据满足指定分区的分区键范围。
+
+    取值范围:
+
+  - WITH：对于普通表中的数据要检查是否满足分区的分区键范围，如果有数据不满足，则报错。
+  - WITHOUT：对于普通表中的数据不检查是否满足分区的分区键范围。
+
+    默认是WITH状态。
+
+    由于检查比较耗时，特别是当数据量很大的情况下更甚。所以在保证当前普通表中的数据满足分区的分区键范围时，可以加上WITHOUT来指明不进行检查。
+
+- **VERBOSE**
+
+  在VALIDATION是WITH状态时，如果检查出普通表有不满足要交换分区的分区键范围的数据，那么把这些数据插入到正确的分区，如果路由不到任何分区，再报错。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 只有在VALIDATION是WITH状态时，才可以指定VERBOSE。
+
+- **partition_new_name**
+
+  分区的新名称。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+## 示例
+
+请参考[CREATE TABLE PARTITION](62-CREATE-TABLE-PARTITION)的示例。
+
+## 相关链接
+
+[CREATE TABLE PARTITION](62-CREATE-TABLE-PARTITION)，[DROP TABLE](95-DROP-TABLE)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/23.1-ALTER-TABLE-SUBPARTITION.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/23.1-ALTER-TABLE-SUBPARTITION.md
new file mode 100644
index 0000000000000000000000000000000000000000..92798922f19debcac153873083ad0650830783e1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/23.1-ALTER-TABLE-SUBPARTITION.md
@@ -0,0 +1,82 @@
+---
+title: ALTER TABLE SUBPARTITION
+summary: ALTER TABLE SUBPARTITION
+author: Zhang Cuiping
+date: 2021-11-01
+---
+
+# ALTER TABLE SUBPARTITION
+
+## 功能描述
+
+修改二级分区表分区，包括清空分区、切割分区等。
+
+## 注意事项
+
+- 目前二级分区表只支持清空分区、切割分区。
+- 切割分区只能对二级分区（叶子节点）进行切割，被切割分区只能是Range，List分区策略，List分区策略只能是default分区才能被切割。
+- 只有分区表的所有者或者被授予了分区表ALTER权限的用户有权限执行ALTER TABLE PARTITION命令，系统管理员默认拥有此权限。
+
+## 语法格式
+
+- 修改表分区主语法。
+
+  ```ebnf+diagram
+  AlterTable ::= ALTER TABLE [ IF EXISTS ] { table_name  [*] | ONLY table_name | ONLY ( table_name  )}
+      action [, ... ];
+  ```
+
+  其中action统指如下分区维护子语法。
+
+  ```ebnf+diagram
+  action::= split_clause  |
+     truncate_clause
+  ```
+
+- split_clause子语法用于把一个分区切割成多个分区。
+
+  ```ebnf+diagram
+  split_clause ::= SPLIT SUBPARTITION { subpartition_name} { split_point_clause  } [ UPDATE GLOBAL INDEX ]
+  ```
+
+  指定切割点split_point_clause的语法为：
+
+  ```ebnf+diagram
+  split_point_clause ::= AT ( subpartition_value ) INTO ( SUBPARTITION subpartition_name [ TABLESPACE tablespacename ] , SUBPARTITION subpartition_name [ TABLESPACE tablespacename ] )
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+  >
+  > - 切割点的大小要位于正在被切割的分区的分区键范围内。
+  >
+  > - 只能把一个分区切割成两个新分区。
+
+- truncate_clause子语法用于清空分区表中的指定分区。
+
+  ```ebnf+diagram
+  truncate_clause ::= TRUNCATE SUBPARTITION  { subpartition_name } [ UPDATE GLOBAL INDEX ]
+  ```
+
+## 参数说明
+
+- **table_name**
+
+  分区表名。
+
+  取值范围: 已存在的分区表名。
+
+- **subpartition_name**
+
+  二级分区名。
+
+  取值范围: 已存在的二级分区名。
+
+- **tablespacename**
+
+  指定分区要移动到哪个表空间。
+
+  取值范围: 已存在的表空间名。
+
+## 示例
+
+请参考[CREATE TABLE SUBPARTITION](62.1-CREATE-TABLE-SUBPARTITION)的示例。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/24-ALTER-TABLESPACE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/24-ALTER-TABLESPACE.md
new file mode 100644
index 0000000000000000000000000000000000000000..e8780b8faae6a2a601d3e9d287265da0a2af230b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/24-ALTER-TABLESPACE.md
@@ -0,0 +1,127 @@
+---
+title: ALTER TABLESPACE
+summary: ALTER TABLESPACE
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER TABLESPACE
+
+## 功能描述
+
+修改表空间的属性。
+
+## 注意事项
+
+- 只有表空间的所有者或者被授予了表空间ALTER权限的用户有权限执行ALTER TABLESPACE命令，系统管理员默认拥有此权限。但要修改表空间的所有者，当前用户必须是该表空间的所有者或系统管理员，且该用户是新所有者角色的成员。
+
+- 要修改表空间的所有者A为B，则A必须是B的直接或者间接成员。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 如果new_owner与old_owner一致，此处不再校验当前执行操作的用户是否具有修改权限，而直接显示ALTER成功。
+
+## 语法格式
+
+- 重命名表空间的语法。
+
+  ```ebnf+diagram
+  AlterTablespace ::= ALTER TABLESPACE tablespace_name
+      RENAME TO new_tablespace_name;
+  ```
+
+- 设置表空间所有者的语法。
+
+  ```ebnf+diagram
+  AlterTablespace ::= ALTER TABLESPACE tablespace_name
+      OWNER TO new_owner;
+  ```
+
+- 设置表空间属性的语法。
+
+  ```ebnf+diagram
+  AlterTablespace ::= ALTER TABLESPACE tablespace_name
+      SET ( {tablespace_option = value} [, ... ] );
+  ```
+
+- 重置表空间属性的语法。
+
+  ```ebnf+diagram
+  AlterTablespace ::= ALTER TABLESPACE tablespace_name
+      RESET ( { tablespace_option } [, ...] );
+  ```
+
+- 设置表空间限额的语法。
+
+  ```ebnf+diagram
+  AlterTablespace ::= ALTER TABLESPACE tablespace_name
+      RESIZE MAXSIZE { UNLIMITED | 'space_size'};
+  ```
+
+## 参数说明
+
+- **tablespace_name**
+
+  要修改的表空间。
+
+  取值范围: 已存在的表空间名。
+
+- **new_tablespace_name**
+
+  表空间的新名称。
+
+  新名称不能以”PG_“开头。
+
+  取值范围: 字符串，符合标识符命名规范。
+
+- **new_owner**
+
+  表空间的新所有者。
+
+  取值范围: 已存在的用户名。
+
+- **tablespace_option**
+
+    设置或者重置表空间的参数。
+
+    取值范围:
+
+  - seq_page_cost：设置优化器计算一次顺序获取磁盘页面的开销。缺省为1.0。
+
+  - random_page_cost：设置优化器计算一次非顺序获取磁盘页面的开销。缺省为4.0。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+    >
+    > - random_page_cost是相对于seq_page_cost的取值，等于或者小于seq_page_cost时毫无意义。
+    > - 默认值为4.0的前提条件是，优化器采用索引来扫描表数据，并且表数据在cache中命中率可以90%左右。
+    > - 如果表数据空间要比物理内存小，那么减小该值到一个适当水平；相反地，如果表数据在cache中命中率要低于90%，那么适当增大该值。
+    > - 如果采用了类似于SSD的随机访问代价较小的存储器，可以适当减小该值，以反映真正的随机扫描代价。
+
+  value的取值范围: 正的浮点类型。
+
+- **RESIZE MAXSIZE**
+
+    重新设置表空间限额的数值。
+
+    取值范围:
+
+  - UNLIMITED，该表空间不设置限额。
+
+  - 由space_size来确定，其格式参考[CREATE TABLESPACE](63-CREATE-TABLESPACE)。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+    >
+    > - 若调整后的限额值比当前表空间实际使用的值要小，调整操作可以执行成功，后续用户需要将该表空间的使用值降低到新限额值之下，才能继续往该表空间中写入数据。
+    >
+    > - 修改参数MAXSIZE时也可使用：
+    >
+    > ```sql
+    > ALTER TABLESPACE tablespace_name RESIZE MAXSIZE
+    > { 'UNLIMITED' | 'space_size'};
+    > ```
+
+## 示例
+
+请参考[CREATE TABLESPACE](63-CREATE-TABLESPACE)的示例。
+
+## 相关链接
+
+[CREATE TABLESPACE](63-CREATE-TABLESPACE)，[DROP TABLESPACE](96-DROP-TABLESPACE)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/25-ALTER-TEXT-SEARCH-CONFIGURATION.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/25-ALTER-TEXT-SEARCH-CONFIGURATION.md
new file mode 100644
index 0000000000000000000000000000000000000000..2cf39583b5f13eaa2db619f9f0db6b9ba1ca88f5
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/25-ALTER-TEXT-SEARCH-CONFIGURATION.md
@@ -0,0 +1,180 @@
+---
+title: ALTER TEXT SEARCH CONFIGURATION
+summary: ALTER TEXT SEARCH CONFIGURATION
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER TEXT SEARCH CONFIGURATION
+
+## 功能描述
+
+更改文本搜索配置的定义。用户可以将映射从字串类型调整为字典，或者改变配置的名称或者所有者，或者修改搜索配置的配置参数。
+
+ADD MAPPING FOR选项为文本搜索配置增加字串类型映射；如果ADD MAPPING FOR后面任何一个字串类型的映射已经存在于此文本搜索配置中，那么系统将会报错。
+
+ALTER MAPPING FOR选项会首先清除已有的字串类型映射，然后添加指定的字串类型映射。
+
+ALTER MAPPING REPLACE … WITH … 与ALTER MAPPING FOR … REPLACE … WITH …选项会直接使用new_dictionary替换old_dictionary。需要注意的是，只有pg_ts_config_map系统表中存在maptokentype与old_dictionary对应关系的元组时，才能更新成功，否则不会成功，也不会有任何提示信息返回。
+
+DROP MAPPING FOR选项会删除当前文本搜索配置中指定的字串类型映射。 如果没有指定IF EXISTS选项，当DROP MAPPING FOR选项指定的字串类型映射在文本搜索配置中不存在时，数据库会报错。
+
+## 注意事项
+
+- 当一个搜索配置已经被引用（如被用来创建索引），则不允许用户修改此文本搜索配置。
+- 要使用ALTER TEXT SEARCH CONFIGURATION，用户必须是配置的所有者。
+
+## 语法格式
+
+- 增加文本搜索配置字串类型映射语法
+
+  ```ebnf+diagram
+  AlterTextSearchConfiguration ::= ALTER TEXT SEARCH CONFIGURATION name
+  ADD MAPPING FOR token_type [, ... ] WITH dictionary_name [, ... ];
+  ```
+
+- 修改文本搜索配置字典语法
+
+  ```ebnf+diagram
+  AlterTextSearchConfiguration ::= ALTER TEXT SEARCH CONFIGURATION name
+  ALTER MAPPING FOR token_type [, ... ] REPLACE old_dictionary WITH new_dictionary;
+  ```
+
+- 修改文本搜索配置字串类型语法
+
+  ```ebnf+diagram
+  AlterTextSearchConfiguration ::= ALTER TEXT SEARCH CONFIGURATION name
+  ALTER MAPPING FOR token_type [, ... ] WITH dictionary_name [, ... ];
+  ```
+
+- 更改文本搜索配置字典语法
+
+  ```ebnf+diagram
+  AlterTextSearchConfiguration ::= ALTER TEXT SEARCH CONFIGURATION name
+  ALTER MAPPING REPLACE old_dictionary WITH new_dictionary;
+  ```
+
+- 删除文本搜索配置字串类型映射语法
+
+  ```ebnf+diagram
+  AlterTextSearchConfiguration ::= ALTER TEXT SEARCH CONFIGURATION name
+  DROP MAPPING [ IF EXISTS ] FOR token_type [, ... ];
+  ```
+
+- 重命名文本搜索配置所有者语法
+
+  ```ebnf+diagram
+  AlterTextSearchConfiguration ::= ALTER TEXT SEARCH CONFIGURATION name OWNER TO new_owner;
+  ```
+
+- 重命名文本搜索配置名称语法
+
+  ```ebnf+diagram
+  AlterTextSearchConfiguration ::= ALTER TEXT SEARCH CONFIGURATION name RENAME TO new_name;
+  ```
+
+- 重命名文本搜索配置命名空间语法
+
+  ```ebnf+diagram
+  AlterTextSearchConfiguration ::= ALTER TEXT SEARCH CONFIGURATION name SET SCHEMA new_schema;
+  ```
+
+- 修改文本搜索配置属性语法
+
+  ```ebnf+diagram
+  AlterTextSearchConfiguration ::= ALTER TEXT SEARCH CONFIGURATION name SET ( { configuration_option = value } [, ...] );
+  ```
+
+- 重置文本搜索配置属性语法
+
+  ```ebnf+diagram
+  AlterTextSearchConfiguration ::= ALTER TEXT SEARCH CONFIGURATION name RESET ( {configuration_option} [, ...] );
+  ```
+
+## 参数说明
+
+- **name**
+
+  已有文本搜索配置的名称（可以有模式修饰）。
+
+- **token_type**
+
+  与配置的语法解析器关联的字串类型的名称。
+
+- **dictionary_name**
+
+  文本搜索字典名称。 如果有多个字典，则它们会按指定的顺序搜索。
+
+- **old_dictionary**
+
+  映身中拟被替换的文本搜索字典名称。
+
+- **new_dictionary**
+
+  替换old_dictionary的文本搜索字典的名称。
+
+- **new_owner**
+
+  文本搜索配置的新所有者。
+
+- **new_name**
+
+  文本搜索配置的新名称。
+
+- **new_schema**
+
+  文本搜索配置的新模式名。
+
+- **configuration_option**
+
+  文本搜索配置项。
+
+- **value**
+
+  文本搜索配置项的值。
+
+## 示例
+
+```sql
+--创建文本搜索配置。
+mogdb=# CREATE TEXT SEARCH CONFIGURATION english_1 (parser=default);
+CREATE TEXT SEARCH CONFIGURATION
+
+--增加文本搜索配置字串类型映射语法。
+mogdb=# ALTER TEXT SEARCH CONFIGURATION english_1 ADD MAPPING FOR word WITH simple,english_stem;
+ALTER TEXT SEARCH CONFIGURATION
+
+--增加文本搜索配置字串类型映射语法。
+mogdb=# ALTER TEXT SEARCH CONFIGURATION english_1 ADD MAPPING FOR email WITH english_stem, french_stem;
+ALTER TEXT SEARCH CONFIGURATION
+
+--查询文本搜索配置相关信息。
+mogdb=# SELECT b.cfgname,a.maptokentype,a.mapseqno,a.mapdict,c.dictname FROM pg_ts_config_map a,pg_ts_config b, pg_ts_dict c WHERE a.mapcfg=b.oid AND a.mapdict=c.oid AND b.cfgname='english_1' ORDER BY 1,2,3,4,5;
+  cfgname  | maptokentype | mapseqno | mapdict |   dictname
+-----------+--------------+----------+---------+--------------
+ english_1 |            2 |        1 |    3765 | simple
+ english_1 |            2 |        2 |   12960 | english_stem
+ english_1 |            4 |        1 |   12960 | english_stem
+ english_1 |            4 |        2 |   12964 | french_stem
+(4 rows)
+
+--增加文本搜索配置字串类型映射语法。
+mogdb=# ALTER TEXT SEARCH CONFIGURATION english_1 ALTER MAPPING REPLACE french_stem with german_stem;
+ALTER TEXT SEARCH CONFIGURATION
+
+--查询文本搜索配置相关信息。
+mogdb=# SELECT b.cfgname,a.maptokentype,a.mapseqno,a.mapdict,c.dictname FROM pg_ts_config_map a,pg_ts_config b, pg_ts_dict c WHERE a.mapcfg=b.oid AND a.mapdict=c.oid AND b.cfgname='english_1' ORDER BY 1,2,3,4,5;
+  cfgname  | maptokentype | mapseqno | mapdict |   dictname
+-----------+--------------+----------+---------+--------------
+ english_1 |            2 |        1 |    3765 | simple
+ english_1 |            2 |        2 |   12960 | english_stem
+ english_1 |            4 |        1 |   12960 | english_stem
+ english_1 |            4 |        2 |   12966 | german_stem
+(4 rows)
+```
+
+请参见[CREATE TEXT SEARCH CONFIGURATION](64-CREATE-TEXT-SEARCH-CONFIGURATION)的示例。
+
+## 相关链接
+
+[CREATE TEXT SEARCH CONFIGURATION](64-CREATE-TEXT-SEARCH-CONFIGURATION)，  [DROP TEXT SEARCH CONFIGURATION](97-DROP-TEXT-SEARCH-CONFIGURATION)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/26-ALTER-TEXT-SEARCH-DICTIONARY.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/26-ALTER-TEXT-SEARCH-DICTIONARY.md
new file mode 100644
index 0000000000000000000000000000000000000000..d5e2277ac85d31c1ff5bc832071aec069dbd1197
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/26-ALTER-TEXT-SEARCH-DICTIONARY.md
@@ -0,0 +1,105 @@
+---
+title: ALTER TEXT SEARCH DICTIONARY
+summary: ALTER TEXT SEARCH DICTIONARY
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER TEXT SEARCH DICTIONARY
+
+## 功能描述
+
+修改全文检索词典的相关定义，包括参数、名称、所有者以及模式等。
+
+## 注意事项
+
+- 预定义词典不支持ALTER操作。
+- 只有词典的所有者可以执行ALTER操作，系统管理员默认拥有此权限。
+- 创建或修改词典之后，任何对于filepath路径下用户自定义的词典定义文件的修改，将不会影响到数据库中的词典。如果需要在数据库中使用这些修改，需使用ALTER TEXT SEARCH DICTIONARY语句更新对应词典的定义文件。
+
+## 语法格式
+
+- 修改词典定义。
+
+  ```ebnf+diagram
+  AlterTextSearchDictionary ::= ALTER TEXT SEARCH DICTIONARY name (
+      option [ = value ] [, ... ]
+  );
+  ```
+
+- 重命名词典。
+
+  ```ebnf+diagram
+  AlterTextSearchDictionary ::= ALTER TEXT SEARCH DICTIONARY name RENAME TO new_name;
+  ```
+
+- 设置词典的所属模式。
+
+  ```ebnf+diagram
+  AlterTextSearchDictionary ::= ALTER TEXT SEARCH DICTIONARY name SET SCHEMA new_schema;
+  ```
+
+- 修改词典的所属者。
+
+  ```ebnf+diagram
+  AlterTextSearchDictionary ::= ALTER TEXT SEARCH DICTIONARY name OWNER TO new_owner;
+  ```
+
+## 参数说明
+
+- **name**
+
+  已存在的词典名（可指定模式名，否则默认在当前模式下）。
+
+  取值范围: 已存在的词典名。
+
+- **option**
+
+  要修改的参数名。与template对应，不同的词典类型具有不同的参数列表，且与指定顺序无关。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  >
+  > - 不支持修改词典的TEMPLATE参数值。
+  > - 不支持仅修改FILEPATH参数而不修改对应的词典定义文件参数。
+  > - 词典定义文件的文件名仅支持小写字母、数据、下划线混合。
+
+- **value**
+
+  要修改的参数值。如果省略等号（=）和value，则表示删除该option的先前设置，使用默认值。
+
+  取值范围: 对应option定义。
+
+- **new_name**
+
+  词典的新名称。
+
+  取值范围: 符合标识符命名规范的字符串，且最大长度不超过63个字符。
+
+- **new_owner**
+
+  词典新的所有者。
+
+  取值范围: 已存在的用户。
+
+- **new_schema**
+
+  词典的新模式。
+
+  取值范围: 已存在的模式。
+
+## 示例
+
+```sql
+--更改Snowball类型字典的停用词定义，其他参数保持不变。
+mogdb=# ALTER TEXT SEARCH DICTIONARY my_dict ( StopWords = newrussian, FilePath = 'file:///home/dicts' );
+
+--更改Snowball类型字典的Language参数，并删除停用词定义。
+mogdb=# ALTER TEXT SEARCH DICTIONARY my_dict ( Language = dutch， StopWords );
+
+--更新词典定义，不实际更改任何内容。
+mogdb=# ALTER TEXT SEARCH DICTIONARY my_dict ( dummy );
+```
+
+## 相关链接
+
+[CREATE TEXT SEARCH DICTIONARY](65-CREATE-TEXT-SEARCH-DICTIONARY)，[DROP TEXT SEARCH DICTIONARY](98-DROP-TEXT-SEARCH-DICTIONARY)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/27-ALTER-TRIGGER.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/27-ALTER-TRIGGER.md
new file mode 100644
index 0000000000000000000000000000000000000000..34c27a043378d055f203dc344e6e95cf640ee6d6
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/27-ALTER-TRIGGER.md
@@ -0,0 +1,50 @@
+---
+title: ALTER TRIGGER
+summary: ALTER TRIGGER
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER TRIGGER
+
+## 功能描述
+
+修改触发器定义。
+
+## 注意事项
+
+只有触发器所在表的所有者可以执行ALTER TRIGGER操作，系统管理员默认拥有此权限。
+
+## 语法格式
+
+```ebnf+diagram
+AlterTrigger ::= ALTER TRIGGER trigger_name ON table_name RENAME TO new_name;
+```
+
+## 参数说明
+
+- **trigger_name**
+
+  要修改的触发器名称。
+
+  取值范围: 已存在的触发器。
+
+- **table_name**
+
+  要修改的触发器所在的表名称。
+
+  取值范围: 已存在的含触发器的表。
+
+- **new_name**
+
+  修改后的新名称。
+
+  取值范围: 符合标识符命名规范的字符串，最大长度不超过63个字符，且不能与所在表上其他触发器同名。
+
+## 示例
+
+请参见[CREATE TRIGGER](66-CREATE-TRIGGER)的示例。
+
+## 相关链接
+
+[CREATE TRIGGER](66-CREATE-TRIGGER)，[DROP TRIGGER](99-DROP-TRIGGER)，[ALTER TABLE](27-ALTER-TRIGGER)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/28-ALTER-TYPE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/28-ALTER-TYPE.md
new file mode 100644
index 0000000000000000000000000000000000000000..4bbc18aa0a0048bec309b47ebed3be07ff92b6da
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/28-ALTER-TYPE.md
@@ -0,0 +1,177 @@
+---
+title: ALTER TYPE
+summary: ALTER TYPE
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER TYPE
+
+## 功能描述
+
+修改一个类型的定义。
+
+## 注意事项
+
+只有类型的所有者或者被授予了类型ALTER权限的用户可以执行ALTER TYPE命令，系统管理员默认拥有此权限。但要修改类型的所有者或者修改类型的模式，当前用户必须是该类型的所有者或者系统管理员，且该用户是新所有者角色的成员。
+
+## 语法格式
+
+- 修改类型。
+
+  ```ebnf+diagram
+  AlterType ::= ALTER TYPE name action [, ... ];
+  ```
+
+  ```ebnf+diagram
+  AlterType ::= ALTER TYPE name OWNER TO { new_owner | CURRENT_USER | SESSION_USER };
+  ```
+
+  ```ebnf+diagram
+  AlterType ::= ALTER TYPE name RENAME ATTRIBUTE attribute_name TO new_attribute_name [ CASCADE | RESTRICT ];
+  ```
+
+  ```ebnf+diagram
+  AlterType ::= ALTER TYPE name RENAME TO new_name;
+  ```
+
+  ```ebnf+diagram
+  AlterType ::= ALTER TYPE name SET SCHEMA new_schema;
+  ```
+
+  ```ebnf+diagram
+  AlterType ::= ALTER TYPE name ADD VALUE [ IF NOT EXISTS ] new_enum_value [ { BEFORE | AFTER } neighbor_enum_value ];
+  ```
+
+  ```ebnf+diagram
+  AlterType ::= ALTER TYPE name RENAME VALUE existing_enum_value TO new_enum_value;
+  ```
+
+  其中action为：
+
+  ```ebnf+diagram
+  action ::= ADD ATTRIBUTE attribute_name data_type [ COLLATE collation ] [ CASCADE | RESTRICT ];
+  ```
+
+  ```ebnf+diagram
+  action ::= DROP ATTRIBUTE [ IF EXISTS ] attribute_name [ CASCADE | RESTRICT ];
+  ```
+
+  ```ebnf+diagram
+  action ::= ALTER ATTRIBUTE attribute_name [ SET DATA ] TYPE data_type [ COLLATE collation ] [ CASCADE | RESTRICT ];
+  ```
+
+- 给复合类型增加新的属性。
+
+  ```ebnf+diagram
+  AlterType ::= ALTER TYPE name ADD ATTRIBUTE attribute_name data_type [ COLLATE collation ] [ CASCADE | RESTRICT ];
+  ```
+
+- 从复合类型删除一个属性。
+
+  ```ebnf+diagram
+  AlterType ::= ALTER TYPE name DROP ATTRIBUTE [ IF EXISTS ] attribute_name [ CASCADE | RESTRICT ];
+  ```
+
+- 改变一种复合类型中某个属性的类型。
+
+  ```ebnf+diagram
+  AlterType ::= ALTER TYPE name ALTER ATTRIBUTE attribute_name [ SET DATA ] TYPE data_type [ COLLATE collation ] [ CASCADE | RESTRICT ];
+  ```
+
+- 改变类型的所有者。
+
+  ```ebnf+diagram
+  AlterType ::= ALTER TYPE name OWNER TO { new_owner | CURRENT_USER | SESSION_USER };
+  ```
+
+- 改变类型的名称或是一个复合类型中的一个属性的名称。
+
+  ```ebnf+diagram
+  AlterType ::= ALTER TYPE name RENAME TO new_name;
+  ```
+
+  ```ebnf+diagram
+  AlterType ::= ALTER TYPE name RENAME ATTRIBUTE attribute_name TO new_attribute_name [ CASCADE | RESTRICT ];
+  ```
+
+- 将类型移至一个新的模式中。
+
+  ```ebnf+diagram
+  AlterType ::= ALTER TYPE name SET SCHEMA new_schema;
+  ```
+
+- 为枚举类型增加一个新值。
+
+  ```ebnf+diagram
+  AlterType ::= ALTER TYPE name ADD VALUE [ IF NOT EXISTS ] new_enum_value [ { BEFORE | AFTER } neighbor_enum_value ];
+  ```
+
+- 重命名枚举类型的一个标签值。
+
+  ```ebnf+diagram
+  AlterType ::= ALTER TYPE name RENAME VALUE existing_enum_value TO new_enum_value;
+  ```
+
+## 参数说明
+
+- **name**
+
+  一个需要修改的现有的类型的名称(可以有模式修饰) 。
+
+- **new_name**
+
+  该类型的新名称。
+
+- **new_owner**
+
+  新所有者的用户名 。
+
+- **new_schema**
+
+  该类型的新模式 。
+
+- **attribute_name**
+
+  拟增加、更改或删除的属性的名称。
+
+- **new_attribute_name**
+
+  拟改名的属性的新名称。
+
+- **data_type**
+
+  拟新增属性的数据类型或是拟更改的属性的新类型名。
+
+- **new_enum_value**
+
+  枚举类型新增加的标签值，是一个非空的长度不超过63个字节的字符串。
+
+- **neighbor_enum_value**
+
+  一个已有枚举标签值，新值应该被增加在紧接着该枚举值之前或者之后的位置上。
+
+- **existing_enum_value**
+
+  现有的要重命名的枚举值，是一个非空的长度不超过63个字节的字符串
+
+- **CASCADE**
+
+  自动级联更新需更新类型以及相关联的记录和继承它们的子表。
+
+- **RESTRICT**
+
+  如果需联动更新类型是已更新类型的关联记录，则拒绝更新。这是缺省选项。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+  >
+  > - ADD ATTRIBUTE、DROP ATTRIBUTE和ALTER ATTRIBUTE选项可以组合成一个列表同时处理。 例如，在一条命令中同时增加几个属性或是更改几个属性的类型是可以实现的。
+  > - 要修改一个类型的模式，必须在新模式上拥有CREATE权限。 要修改所有者，必须是新的所有角色的直接或间接成员， 并且该成员必须在此类型的模式上有CREATE权限。 （这些限制强制了修改所有者不会做任何通过删除和重建类型不能做的事情。 不过，系统管理员可以以任何方式修改任意类型的所有权。） 要增加一个属性或是修改一个属性的类型，也必须有该类型的USAGE权限。
+
+## 示例
+
+请参考[CREATE TYPE](67-CREATE-TYPE)的示例。
+
+## 相关链接
+
+[CREATE TYPE](67-CREATE-TYPE)，[DROP TYPE](100-DROP-TYPE)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/29-ALTER-USER.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/29-ALTER-USER.md
new file mode 100644
index 0000000000000000000000000000000000000000..5594b96c138a5a8af090d247f32c5a63813e2e83
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/29-ALTER-USER.md
@@ -0,0 +1,113 @@
+---
+title: ALTER USER
+summary: ALTER USER
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER USER
+
+## 功能描述
+
+修改数据库用户的属性。
+
+## 注意事项
+
+ALTER USER中修改的会话参数只针对指定的用户，且在下一次会话中有效。
+
+## 语法格式
+
+- 修改用户的权限等信息。
+
+  ```ebnf+diagram
+  AlterUser ::= ALTER USER user_name [ [ WITH ] option [ ... ] ];
+  ```
+
+  其中option子句为。
+
+  ```ebnf+diagram
+  option ::= { CREATEDB | NOCREATEDB }
+      | { CREATEROLE | NOCREATEROLE }
+      | { INHERIT | NOINHERIT }
+      | { AUDITADMIN | NOAUDITADMIN }
+      | { SYSADMIN | NOSYSADMIN }
+      | { USEFT | NOUSEFT }
+      | { LOGIN | NOLOGIN }
+      | { REPLICATION | NOREPLICATION }
+      | {INDEPENDENT | NOINDEPENDENT}
+      | {VCADMIN | NOVCADMIN}
+      | CONNECTION LIMIT connlimit
+      | [ ENCRYPTED | UNENCRYPTED ] PASSWORD { 'password' [EXPIRED] | DISABLE | EXPIRED }
+      | [ ENCRYPTED | UNENCRYPTED ] IDENTIFIED BY { 'password' [ REPLACE 'old_password' | EXPIRED ] | DISABLE }
+      | VALID BEGIN 'timestamp'
+      | VALID UNTIL 'timestamp'
+      | RESOURCE POOL 'respool'
+      | PERM SPACE 'spacelimit'
+      | ACCOUNT { LOCK | UNLOCK }
+      | PGUSER
+  ```
+
+- 修改用户名。
+
+  ```ebnf+diagram
+  AlterUser ::= ALTER USER user_name
+      RENAME TO new_name;
+  ```
+
+- 修改与用户关联的指定会话参数值。
+
+  ```ebnf+diagram
+  AlterUser ::= ALTER USER user_name
+      SET configuration_parameter { { TO | = } { value | DEFAULT } | FROM CURRENT };
+  ```
+
+- 重置与用户关联的指定会话参数值。
+
+  ```ebnf+diagram
+  AlterUser ::= ALTER USER user_name
+      RESET { configuration_parameter | ALL };
+  ```
+
+## 参数说明
+
+- **user_name**
+
+  现有用户名。
+
+  取值范围: 已存在的用户名。
+
+- **new_password**
+
+    新密码。
+
+    密码规则如下：
+
+  - 不能与当前密码相同。
+  - 密码默认不少于8个字符。
+  - 不能与用户名及用户名倒序相同。
+  - 至少包含大写字母（A-Z），小写字母（a-z），数字（0-9），非字母数字字符（限定为~!@#$%^&*()-_=+\|[{}];:,&lt;.&gt;/?）四类字符中的三类字符。
+
+    取值范围: 字符串。
+
+- **old_password**
+
+  旧密码。
+
+- **ACCOUNT LOCK | ACCOUNT UNLOCK**
+
+  - ACCOUNT LOCK：锁定帐户，禁止登录数据库。
+  - ACCOUNT UNLOCK：解锁帐户，允许登录数据库。
+
+- **PGUSER**
+
+  当前版本不允许修改用户的PGUSER属性。
+
+其他参数请参见[CREATE ROLE](54-CREATE-ROLE)和[ALTER ROLE](12-ALTER-ROLE)的参数说明。
+
+## 示例
+
+请参考[CREATE USER](68-CREATE-USER)的示例。
+
+## 相关链接
+
+[CREATE ROLE](54-CREATE-ROLE),  [CREATE USER](68-CREATE-USER), and  [DROP USER](101-DROP-USER)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/3-ALTER-DATA-SOURCE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/3-ALTER-DATA-SOURCE.md
new file mode 100644
index 0000000000000000000000000000000000000000..d112496e6815455b0dbb8b5f54c55015a6e8e14d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/3-ALTER-DATA-SOURCE.md
@@ -0,0 +1,114 @@
+---
+title: ALTER DATA SOURCE
+summary: ALTER DATA SOURCE
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER DATA SOURCE
+
+## 功能描述
+
+修改Data Source对象的属性和内容。
+
+属性有：名称和属主；内容有：类型、版本和连接选项。
+
+## 注意事项
+
+- 只有初始用户/系统管理员/属主才拥有修改Data Source的权限。
+- 修改属主时，新的属主用户必须是初始用户或系统管理员。
+- 当在OPTIONS中出现password选项时，需要保证MogDB每个节点的`$GAUSSHOME/bin`目录下存在datasource.key.cipher和datasource.key.rand文件，如果不存在这两个文件，请使用`gs_guc`工具生成并使用`gs_ssh`工具发布到每个节点的`$GAUSSHOME/bin`目录下。
+
+## 语法格式
+
+```ebnf+diagram
+AlterDataSource ::= ALTER DATA SOURCE src_name
+    [TYPE  'type_str']
+    [VERSION  {'version_str' | NULL}]
+    [OPTIONS ( {[ ADD | SET | DROP ] optname ['optvalue']} [, ...] )];
+```
+
+```ebnf+diagram
+AlterDataSource ::= ALTER DATA SOURCE src_name RENAME TO src_new_name;
+```
+
+```ebnf+diagram
+AlterDataSource ::= ALTER DATA SOURCE src_name OWNER TO new_owner;
+```
+
+## 参数说明
+
+- **src_name**
+
+  待修改的Data Source的名称。
+
+  取值范围: 字符串，需要符合标识符的命名规范。
+
+- **TYPE**
+
+  将Data Source原来的TYPE修改为指定值。
+
+  取值范围: 空串或非空字符串。
+
+- **VERSION**
+
+  将Data Source原来的VERSION修改为指定值。
+
+  取值范围: 空串或非空字符串或NULL。
+
+- **OPTIONS**
+
+  修改OPTIONS中的字段：增加（ADD）、修改（SET）、删除（DROP），且字段名称optname需唯一，具体要求如下：
+
+  增加字段：ADD可以省略，待增加字段不能已经存在了；
+
+  修改字段：SET不可省略，待修改字段必须存在；
+
+  删除字段：DROP不可省略，待删除字段必须存在，且不能指定optvalue；
+
+- **src_new_name**
+
+  新的Data Source名称。
+
+  取值范围: 字符串，需符合标识符命名规范。
+
+- **new_user**
+
+  对象的新属主。
+
+  取值范围: 字符串，有效的用户名。
+
+## 示例
+
+```sql
+--创建一个空Data Source对象。
+mogdb=# CREATE DATA SOURCE ds_test1;
+
+--修改名称。
+mogdb=# ALTER DATA SOURCE ds_test1 RENAME TO ds_test;
+
+--修改属主。
+mogdb=# CREATE USER user_test1 IDENTIFIED BY 'Gs@123456';
+mogdb=# ALTER USER user_test1 WITH SYSADMIN;
+mogdb=# ALTER DATA SOURCE ds_test OWNER TO user_test1;
+
+--修改TYPE和VERSION。
+mogdb=# ALTER DATA SOURCE ds_test TYPE 'MPPDB_TYPE' VERSION 'XXX';
+
+--添加字段。
+mogdb=# ALTER DATA SOURCE ds_test OPTIONS (add dsn 'mogdb', username 'test_user');
+
+--修改字段。
+mogdb=# ALTER DATA SOURCE ds_test OPTIONS (set dsn 'unknown');
+
+--删除字段。
+mogdb=# ALTER DATA SOURCE ds_test OPTIONS (drop username);
+
+--删除Data Source和user对象。
+mogdb=# DROP DATA SOURCE ds_test;
+mogdb=# DROP USER user_test1;
+```
+
+## 相关链接
+
+[CREATE DATA SOURCE](45-CREATE-DATA-SOURCE)，[DROP DATA SOURCE](79-DROP-DATA-SOURCE)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/30-ALTER-USER-MAPPING.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/30-ALTER-USER-MAPPING.md
new file mode 100644
index 0000000000000000000000000000000000000000..9b2c2ae6c2257ad1ef49d93d0a497ee84827ecef
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/30-ALTER-USER-MAPPING.md
@@ -0,0 +1,73 @@
+---
+title: ALTER USER MAPPING
+summary: ALTER USER MAPPING
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER USER MAPPING
+
+## 功能描述
+
+更改一个用户映射的定义。
+
+## 注意事项
+
+当在OPTIONS中出现password选项时，需要保证MogDB每个节点的`$GAUSSHOME/bin`目录下存在usermapping.key.cipher和usermapping.key.rand文件，如果不存在这两个文件，请使用`gs_guc`工具生成并使用`gs_ssh`工具发布到每个节点的`$GAUSSHOME/bin`目录下。
+
+## 语法格式
+
+```ebnf+diagram
+AlterUserMapping ::= ALTER USER MAPPING FOR { user_name | USER | CURRENT_USER | PUBLIC }
+    SERVER server_name
+    OPTIONS ( [ ADD | SET | DROP ] option ['value'] [, ... ] )
+```
+
+在OPTIONS选项里，`ADD`、`SET`和`DROP`指定要执行的操作，未指定时默认为`ADD`操作。option和value为对应操作的参数及参数值。
+
+## 参数说明
+
+- **user_name**
+
+  该映射的用户名。
+
+  `CURRENT_USER`和`USER`匹配当前 用户的名称。`PUBLIC`被用来匹配系统中所有当前以及未来的用户名。
+
+- **server_name**
+
+  该用户映射的服务器名。
+
+- **OPTIONS**
+
+  为该用户映射更改选项。新选项会覆盖任何之前指定的选项。ADD、 SET和DROP指定要被执行的动作。如果没有显式地指定操作，将假定为ADD。选项名称必须为唯一，该服务器的外部数据包装器也会验证选项。
+
+  - oracle_fdw支持的options包括：
+    - **user**
+
+        oracle server的用户名。
+
+    - **password**
+
+        oracle用户对应的密码。
+
+  - mysql_fdw支持的options包括：
+    - **username**
+
+        MySQL Server/MariaDB的用户名。
+
+    - **password**
+
+        MySQL Server/MariaDB用户对应的密码。
+
+  - postgres_fdw支持的options包括：
+    - **user**
+
+        远端MogDB数据库用户的用户名。
+
+    - **password**
+
+        远端MogDB数据库用户对应的密码。
+
+## 相关链接
+
+[CREATE USER MAPPING](69-CREATE-USER-MAPPING)，[DROP USER MAPPING](102-DROP-USER-MAPPING)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/31-ALTER-VIEW.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/31-ALTER-VIEW.md
new file mode 100644
index 0000000000000000000000000000000000000000..9134e4fea14fdc2a3cebd84c358bae462dc3b6eb
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/31-ALTER-VIEW.md
@@ -0,0 +1,134 @@
+---
+title: ALTER VIEW
+summary: ALTER VIEW
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER VIEW
+
+## 功能描述
+
+ALTER VIEW更改视图的各种辅助属性。（如果用户是更改视图的查询定义，要使用CREATE OR REPLACE VIEW。）
+
+## 注意事项
+
+只有视图的所有者或者被授予了视图ALTER权限的用户才可以执行ALTER VIEW命令，系统管理员默认拥有该权限。针对所要修改属性的不同，对其还有以下权限约束：
+
+- 修改视图的模式，当前用户必须是视图的所有者或者系统管理员，且要有新模式的CREATE权限。
+- 修改视图的所有者，当前用户必须是视图的所有者或者系统管理员，且该用户必须是新所有者角色的成员，并且此角色必须有视图所在模式的CREATE权限。
+
+## 语法格式
+
+- 设置视图列的默认值。
+
+  ```ebnf+diagram
+  AlterView ::= ALTER VIEW [ IF EXISTS ] view_name
+      ALTER [ COLUMN ] column_name SET DEFAULT expression;
+  ```
+
+- 取消列视图列的默认值。
+
+  ```ebnf+diagram
+  AlterView ::= ALTER VIEW [ IF EXISTS ] view_name
+      ALTER [ COLUMN ] column_name DROP DEFAULT;
+  ```
+
+- 修改视图的所有者。
+
+  ```ebnf+diagram
+  AlterView ::= ALTER VIEW [ IF EXISTS ] view_name
+      OWNER TO new_owner;
+  ```
+
+- 重命名视图。
+
+  ```ebnf+diagram
+  AlterView ::= ALTER VIEW [ IF EXISTS ] view_name
+      RENAME TO new_name;
+  ```
+
+- 设置视图的所属模式。
+
+  ```ebnf+diagram
+  AlterView ::= ALTER VIEW [ IF EXISTS ] view_name
+      SET SCHEMA new_schema;
+  ```
+
+- 设置视图的选项。
+
+  ```ebnf+diagram
+  AlterView ::= ALTER VIEW [ IF EXISTS ] view_name
+      SET ( { view_option_name [ = view_option_value ] } [, ... ] );
+  ```
+
+- 重置视图的选项。
+
+  ```ebnf+diagram
+  AlterView ::= ALTER VIEW [ IF EXISTS ] view_name
+      RESET ( view_option_name [, ... ] );
+  ```
+
+## 参数说明
+
+- **IF EXISTS**
+
+  使用这个选项，如果视图不存在时不会产生错误，仅有会有一个提示信息。
+
+- **view_name**
+
+  视图名称，可以用模式修饰。
+
+  取值范围: 字符串，符合标识符命名规范。
+
+- **column_name**
+
+  可选的名称列表，视图的字段名。如果没有给出，字段名取自查询中的字段名。
+
+  取值范围: 字符串，符合标识符命名规范。
+
+- **SET/DROP DEFAULT**
+
+  设置或删除一个列的缺省值，该参数暂无实际意义。
+
+- **new_owner**
+
+  视图新所有者的用户名称。
+
+- **new_name**
+
+  视图的新名称。
+
+- **new_schema**
+
+  视图的新模式。
+
+- **view_option_name [ = view_option_value ]**
+
+  该子句为视图指定一个可选的参数。
+
+  目前view_option_name支持的参数仅有security_barrier，当VIEW试图提供行级安全时，应使用该参数。
+
+  取值范围: Boolean类型，TRUE、FALSE。
+
+## 示例
+
+```sql
+--创建一个由c_customer_sk小于150的内容组成的视图。
+mogdb=# CREATE VIEW tpcds.customer_details_view_v1 AS
+    SELECT * FROM tpcds.customer
+    WHERE c_customer_sk < 150;
+
+--修改视图名称。
+mogdb=# ALTER VIEW tpcds.customer_details_view_v1 RENAME TO customer_details_view_v2;
+
+--修改视图所属schema。
+mogdb=# ALTER VIEW tpcds.customer_details_view_v2 SET schema public;
+
+--删除视图。
+mogdb=# DROP VIEW public.customer_details_view_v2;
+```
+
+## 相关链接
+
+[CREATE VIEW](70-CREATE-VIEW), [DROP VIEW](103-DROP-VIEW)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/32-ANALYZE-ANALYSE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/32-ANALYZE-ANALYSE.md
new file mode 100644
index 0000000000000000000000000000000000000000..4be3ed5cff129082bdc494dcc581570232333b30
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/32-ANALYZE-ANALYSE.md
@@ -0,0 +1,192 @@
+---
+title: ANALYZE | ANALYSE
+summary: ANALYZE | ANALYSE
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ANALYZE | ANALYSE
+
+## 功能描述
+
+用于收集与数据库中普通表内容相关的统计信息，统计结果存储在系统表PG_STATISTIC下。执行计划生成器会使用这些统计数据，以确定最有效的执行计划。
+
+如果没有指定参数，ANALYZE会分析当前数据库中的每个表和分区表。同时也可以通过指定table_name、column和partition_name参数把分析限定在特定的表、列或分区表中。
+
+ANALYZE|ANALYSE VERIFY用于检测数据库中普通表（行存表、列存表）的数据文件是否损坏。
+
+## 注意事项
+
+- ANALYZE非临时表不能在一个匿名块、事务块、函数或存储过程内被执行。支持存储过程中ANALYZE临时表，不支持统计信息回滚操作。
+- ANALYZE VERIFY操作处理的大多为异常场景检测需要使用RELEASE版本。ANALYZE VERIFY 场景不触发远程读，因此远程读参数不生效。对于关键系统表出现错误被系统检测出页面损坏时，将直接报错不再继续检测。
+- 如果没有指定参数，ANALYZE处理当前数据库里用户拥有相应权限的每个表。如果参数中指定了表，ANALYZE只处理指定的表。
+- 要对一个表进行ANALYZE操作，通常用户必须是表的所有者或者被授予了指定表VACUUM权限的用户，默认系统管理员有该权限。数据库的所有者允许对数据库中除了共享目录以外的所有表进行ANALYZE操作（该限制意味着只有系统管理员才能真正对一个数据库进行ANALYZE操作）。ANALYZE命令会跳过那些用户没有权限的表。
+
+## 语法格式
+
+- 收集表的统计信息。
+
+  ```ebnf+diagram
+  AnalyzeAnalyse ::= { ANALYZE | ANALYSE } [ VERBOSE ]
+      [ table_name [ ( column_name [, ...] ) ] ];
+  ```
+
+- 收集分区表的统计信息。
+
+  ```ebnf+diagram
+  AnalyzeAnalyse ::= { ANALYZE | ANALYSE } [ VERBOSE ]
+      [ table_name [ ( column_name [, ...] ) ] ]
+      PARTITION ( patrition_name ) ;
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 普通分区表目前支持针对某个分区的统计信息的语法，但功能上不支持针对某个分区的统计信息收集。
+
+- 收集多列统计信息。
+
+  ```ebnf+diagram
+  AnalyzeAnalyse ::= {ANALYZE | ANALYSE} [ VERBOSE ]
+      table_name (( column_1_name, column_2_name [, ...] ));
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  >
+  > - 收集多列统计信息时，请设置GUC参数default_statistics_target为负数，以使用百分比采样方式。
+  > - 每组多列统计信息最多支持32列。
+  > - 不支持收集多列统计信息的表：系统表。
+
+- 检测当前库的数据文件。
+
+  ```ebnf+diagram
+  AnalyzeAnalyse ::= {ANALYZE | ANALYSE} VERIFY {FAST|COMPLETE};
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  >
+  > - Fast模式校验时，需要对校验的表有并发的DML操作，会导致校验过程中有误报的问题，因为当前Fast模式是直接从磁盘上读取，并发有其他线程修改文件时，会导致获取的数据不准确，建议离线操作。
+  > - 支持对全库进行操作，由于涉及的表较多，建议以重定向保存结果**gsql -d database -p port -f “verify.sql”&gt; verify_warning.txt 2&gt;&1**。
+  > - 对外提示NOTICE只核对外可见的表，内部表的检测会包含在它所依赖的外部表，不对外显示和呈现。
+  > - 此命令的处理可容错ERROR级别的处理。由于debug版本的Assert可能会导致core无法继续执行命令，建议在release模式下操作。
+  > - 对于全库操作时，当关键系统表出现损坏则直接报错，不再继续执行。
+
+- 检测表和索引的数据文件
+
+  ```ebnf+diagram
+  AnalyzeAnalyse ::= {ANALYZE | ANALYSE} VERIFY {FAST|COMPLETE} table_name|index_name [CASCADE];
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  >
+  > - 支持对普通表的操作和索引表的操作，但不支持对索引表index使用CASCADE操作。原因是由于CASCADE模式用于处理主表的所有索引表，当单独对索引表进行检测时，无需使用CASCADE模式。
+  > - 对于主表的检测会同步检测主表的内部表，例如toast表、cudesc表等。
+  > - 当提示索引表损坏时，建议使用reindex命令进行重建索引操作。
+
+- 检测表分区的数据文件
+
+  ```ebnf+diagram
+  AnalyzeAnalyse ::= {ANALYZE | ANALYSE} VERIFY {FAST|COMPLETE} table_name PARTITION {(patrition_name)}[CASCADE];
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 支持对表的单独分区进行检测操作，但不支持对索引表index使用CASCADE操作。
+
+## 参数说明
+
+- **VERBOSE**
+
+  启用显示进度信息。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 如果指定了VERBOSE，ANALYZE发出进度信息，表明目前正在处理的表。各种有关表的统计信息也会打印出来。
+
+- **table_name**
+
+  需要分析的特定表的表名（可能会带模式名），如果省略，将对数据库中的所有表（非外部表）进行分析。
+
+  对于ANALYZE收集统计信息，目前仅支持行存表、列存表。
+
+  取值范围: 已有的表名。
+
+- **column_name**，column_1_name，column_2_name
+
+  需要分析特定列的列名，默认为所有列。
+
+  取值范围: 已有的列名。
+
+- **partition_name**
+
+  如果table为分区表，在关键字PARTITION后面指定分区名partition_name表示分析该分区表的统计信息。目前语法上支持分区表做ANALYZE，但功能实现上暂不支持对指定分区统计信息的分析。
+
+  取值范围: 表的某一个分区名。
+
+- **index_name**
+
+  需要分析的特定索引表的表名（可能会带模式名）。
+
+  取值范围: 已有的表名。
+
+- **FAST|COMPLETE**
+
+  对于行存表，FAST模式下主要对于行存表的CRC和page header进行校验，如果校验失败则会告警; 而COMPLETE模式下，则主要对行存表的指针、tuple进行解析校验。 对于列存表，FAST模式下主要对于列存表的CRC和magic进行校验，如果校验失败则会告警; 而COMPLETE模式下，则主要对列存表的CU进行解析校验。
+
+- **CASCADE**
+
+  CASCADE模式下会对当前表的所有索引进行检测处理。
+
+## 示例
+
+- 创建表。
+
+```sql
+mogdb=# CREATE TABLE customer_info
+(
+WR_RETURNED_DATE_SK       INTEGER                       ,
+WR_RETURNED_TIME_SK       INTEGER                       ,
+WR_ITEM_SK                INTEGER               NOT NULL,
+WR_REFUNDED_CUSTOMER_SK   INTEGER
+)
+;
+```
+
+- 创建分区表。
+
+```sql
+mogdb=# CREATE TABLE customer_par
+(
+WR_RETURNED_DATE_SK       INTEGER                       ,
+WR_RETURNED_TIME_SK       INTEGER                       ,
+WR_ITEM_SK                INTEGER               NOT NULL,
+WR_REFUNDED_CUSTOMER_SK   INTEGER
+)
+PARTITION BY RANGE(WR_RETURNED_DATE_SK)
+(
+PARTITION P1 VALUES LESS THAN(2452275),
+PARTITION P2 VALUES LESS THAN(2452640),
+PARTITION P3 VALUES LESS THAN(2453000),
+PARTITION P4 VALUES LESS THAN(MAXVALUE)
+)
+ENABLE ROW MOVEMENT;
+```
+
+- 使用ANALYZE语句更新统计信息。
+
+```sql
+mogdb=# ANALYZE customer_info;
+mogdb=# ANALYZE customer_par;
+```
+
+- 使用ANALYZE VERBOSE语句更新统计信息，并输出表的相关信息。
+
+```sql
+mogdb=# ANALYZE VERBOSE customer_info;
+INFO:  analyzing "cstore.pg_delta_3394584009"(cn_5002 pid=53078)
+INFO:  analyzing "public.customer_info"(cn_5002 pid=53078)
+INFO:  analyzing "public.customer_info" inheritance tree(cn_5002 pid=53078)
+ANALYZE
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 若环境若有故障，需查看数据库主节点的log。
+
+- 删除表。
+
+```sql
+mogdb=# DROP TABLE customer_info;
+mogdb=# DROP TABLE customer_par;
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/33-BEGIN.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/33-BEGIN.md
new file mode 100644
index 0000000000000000000000000000000000000000..0b6cba7759f54af4d13b412036a015ebf92adb13
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/33-BEGIN.md
@@ -0,0 +1,62 @@
+---
+title: BEGIN
+summary: BEGIN
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# BEGIN
+
+## 功能描述
+
+BEGIN可以用于开始一个匿名块，也可以用于开始一个事务。本节描述用BEGIN开始匿名块的语法，以BEGIN开始事务的语法见**START TRANSACTION**。
+
+匿名块是能够动态地创建和执行过程代码的结构，而不需要以持久化的方式将代码作为数据库对象储存在数据库中。
+
+## 注意事项
+
+无。
+
+## 语法格式
+
+- 开启匿名块
+
+  ```ebnf+diagram
+  Begin ::= [DECLARE [declare_statements]]
+  BEGIN
+  execution_statements
+  END;
+
+  ```
+
+- 开启事务
+
+  ```ebnf+diagram
+  Begin ::= BEGIN [ WORK | TRANSACTION ]
+    [
+      {
+         ISOLATION LEVEL { READ COMMITTED | SERIALIZABLE | REPEATABLE READ }
+         | { READ WRITE | READ ONLY }
+        } [, ...]
+    ];
+  ```
+
+## 参数说明
+
+- **declare_statements**
+
+  声明变量，包括变量名和变量类型，如“sales_cnt int”。
+
+- **execution_statements**
+
+  匿名块中要执行的语句。
+
+  取值范围: DML操作（数据操纵操作：select、insert、delete、update）或系统表中已经注册的函数名称。
+
+## 示例
+
+无
+
+## 相关链接
+
+[START TRANSACTION](134-START-TRANSACTION)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/34-CALL.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/34-CALL.md
new file mode 100644
index 0000000000000000000000000000000000000000..21957f8af31b44afd23a6e4e991f61dadfc48a2b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/34-CALL.md
@@ -0,0 +1,84 @@
+---
+title: CALL
+summary: CALL
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CALL
+
+## 功能描述
+
+使用CALL命令可以调用已定义的函数和存储过程。
+
+## 注意事项
+
+无。
+
+## 语法格式
+
+```ebnf+diagram
+Call ::= CALL [schema'.'|package'.'] {func_name| procedure_name} ( param_expr );
+```
+
+## 参数说明
+
+- **schema**
+
+  函数或存储过程所在的模式名称。
+
+- **package**
+
+    函数或存储过程所在的package名称。
+
+- **func_name**
+
+  所调用函数或存储过程的名称。
+
+  取值范围: 已存在的函数名称。
+
+- **param_expr**
+
+  参数列表可以用符号”:=“或者”=&gt;“将参数名和参数值隔开，这种方法的好处是参数可以以任意顺序排列。若参数列表中仅出现参数值，则参数值的排列顺序必须和函数或存储过程定义时的相同。
+
+  取值范围: 已存在的函数参数名称或存储过程参数名称。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  > 参数可以包含入参（参数名和类型之间指定“IN”关键字）和出参（参数名和类型之间指定“OUT”关键字），使用CALL命令调用函数或存储过程时，对于非重载的函数，参数列表必须包含出参，出参可以传入一个变量或者任一常量，详见示例。对于重载的package函数，参数列表里可以忽略出参，忽略出参时可能会导致函数找不到。包含出参时，出参只能是常量。
+
+## 示例
+
+```sql
+--创建一个函数func_add_sql，计算两个整数的和，并返回结果。
+mogdb=# CREATE FUNCTION func_add_sql(num1 integer, num2 integer) RETURN integer
+AS
+BEGIN
+RETURN num1 + num2;
+END;
+/
+
+--按参数值传递。
+mogdb=# CALL func_add_sql(1, 3);
+
+--使用命名标记法传参。
+mogdb=# CALL func_add_sql(num1 => 1,num2 => 3);
+mogdb=# CALL func_add_sql(num2 := 2, num1 := 3);
+
+--删除函数。
+mogdb=# DROP FUNCTION func_add_sql;
+
+--创建带出参的函数。
+mogdb=# CREATE FUNCTION func_increment_sql(num1 IN integer, num2 IN integer, res OUT integer)
+RETURN integer
+AS
+BEGIN
+res := num1 + num2;
+END;
+/
+
+--出参传入常量。
+mogdb=# CALL func_increment_sql(1,2,1);
+
+--删除函数。
+mogdb=# DROP FUNCTION func_increment_sql;
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/35-CHECKPOINT.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/35-CHECKPOINT.md
new file mode 100644
index 0000000000000000000000000000000000000000..be8bb583f4b8f4315b9b9da583a46e0147df66d9
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/35-CHECKPOINT.md
@@ -0,0 +1,36 @@
+---
+title: CHECKPOINT
+summary: CHECKPOINT
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CHECKPOINT
+
+## 功能描述
+
+检查点（CHECKPOINT）是一个事务日志中的点，所有数据文件都在该点被更新以反映日志中的信息，所有数据文件都将被刷新到磁盘。
+
+设置事务日志检查点。预写式日志（WAL）缺省时在事务日志中每隔一段时间放置一个检查点。可以使用gs_guc命令设置相关运行时参数（checkpoint_segments和checkpoint_timeout）来调整这个原子化检查点的间隔。
+
+## 注意事项
+
+- 只有系统管理员可以调用CHECKPOINT。
+- CHECKPOINT强制立即进行检查，而不是等到下一次调度时的检查点。
+
+## 语法格式
+
+```ebnf+diagram
+Checkpoint ::= CHECKPOINT;
+```
+
+## 参数说明
+
+无。
+
+## 示例
+
+```sql
+--设置检查点。
+mogdb=# CHECKPOINT;
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/35.1-CLEAN-CONNECTION.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/35.1-CLEAN-CONNECTION.md
new file mode 100644
index 0000000000000000000000000000000000000000..1cf240d8782382ed9fda75e9dc260b99e34a3c00
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/35.1-CLEAN-CONNECTION.md
@@ -0,0 +1,76 @@
+---
+title: CLEAN CONNECTION
+summary: CLEAN CONNECTION
+author: Zhang Cuiping
+date: 2021-11-01
+---
+
+# CLEAN CONNECTION
+
+## 功能描述
+
+用来清理数据库连接。允许在节点上清理指定数据库的指定用户的相关连接。
+
+## 注意事项
+
+1、MogDB下不支持指定节点，仅支持TO ALL。
+
+2、在非force模式下，该功能不清理连接，在fore模式下，可以清理正在使用的正常连接。
+
+## 语法格式
+
+```ebnf+diagram
+CleanConnection ::= CLEAN CONNECTION
+      TO { COORDINATOR ( nodename [, ... ] ) | NODE ( nodename [, ... ] )| ALL [ CHECK ] [ FORCE ] }
+      [ FOR DATABASE dbname ]
+      [ TO USER username ];
+```
+
+## 参数说明
+
+- **CHECK**
+
+  仅在节点列表为TO ALL时可以指定。如果指定该参数，会在清理连接之前检查数据库是否被其他会话连接访问。此参数主要用于DROP DATABASE之前的连接访问检查，如果发现有其他会话连接，则将报错并停止删除数据库。
+
+- **FORCE**
+
+  仅在节点列表为TO ALL时可以指定，如果指定该参数，所有和指定dbname和username相关的线程都会收到SIGTERM信号，然后被强制关闭。
+
+- **COORDINATOR ( nodename [, … ] ) | NODE ( nodename [, … ] ) | ALL**
+
+    删除指定节点上的连接。有三种场景：
+
+  - 删除指定CN上的连接，MogDB不支持。
+  - 删除指定DN上的连接，MogDB不支持。
+  - 删除所有节点上的连接(TO ALL)，MogDB仅支持该场景。
+
+- **dbname**
+
+  删除指定数据库上的连接。如果不指定，则删除所有数据库的连接。
+
+  取值范围: 已存在数据库名
+
+- **username**
+
+  删除指定用户上的连接。如果不指定，则删除所有用户的连接。
+
+  取值范围: 已存在的用户
+
+## 示例
+
+```sql
+--创建jack用户。
+CREATE USER jack PASSWORD 'Bigdata123@';
+
+--删除用户jack在数据库template1上的所有连接。
+CLEAN CONNECTION TO ALL FOR DATABASE template1 TO USER jack;
+
+--删除用户jack的所有连接。
+CLEAN CONNECTION TO ALL TO USER jack;
+
+--删除在数据库gaussdb上的所有连接。
+CLEAN CONNECTION TO ALL FORCE FOR DATABASE gaussdb;
+
+--删除用户jack。
+DROP USER jack;
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/36-CLOSE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/36-CLOSE.md
new file mode 100644
index 0000000000000000000000000000000000000000..48e5eb7794f70898e2d66b0be3c82c83741b0fc9
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/36-CLOSE.md
@@ -0,0 +1,45 @@
+---
+title: CLOSE
+summary: CLOSE
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CLOSE
+
+## 功能描述
+
+CLOSE释放和一个游标关联的所有资源。
+
+## 注意事项
+
+- 不允许对一个已关闭的游标再做任何操作。
+- 一个不再使用的游标应该尽早关闭。
+- 当创建游标的事务用COMMIT或ROLLBACK终止之后，每个不可保持的已打开游标都隐含关闭。
+- 当创建游标的事务通过ROLLBACK退出之后，每个可以保持的游标都将隐含关闭。
+- 当创建游标的事务成功提交，可保持的游标将保持打开，直到执行一个明确的CLOSE或者客户端断开。
+- MogDB没有明确打开游标的OPEN语句，因为一个游标在使用CURSOR命令定义的时候就打开了。可以通过查询系统视图pg_cursors看到所有可用的游标。
+
+## 语法格式
+
+```ebnf+diagram
+Close ::= CLOSE { cursor_name | ALL } ;
+```
+
+## 参数说明
+
+- **cursor_name**
+
+  一个待关闭的游标名称。
+
+- **ALL**
+
+  关闭所有已打开的游标。
+
+## 示例
+
+请参考[FETCH](107-FETCH)的示例。
+
+## 相关链接
+
+[FETCH](107-FETCH)，[MOVE](111-MOVE)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/37-CLUSTER.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/37-CLUSTER.md
new file mode 100644
index 0000000000000000000000000000000000000000..5600933a8fe79d674222e2715e400ece09797f07
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/37-CLUSTER.md
@@ -0,0 +1,128 @@
+---
+title: CLUSTER
+summary: CLUSTER
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CLUSTER
+
+## 功能描述
+
+根据一个索引对表进行聚簇排序。
+
+CLUSTER指定MogDB通过索引名指定的索引聚簇由表名指定的表。 表名上必须已经定义该索引。
+
+当对一个表聚集后，该表将基于索引信息进行物理存储。聚集是一次性操作：当表被更新之后， 更改的内容不会被聚集。也就是说，系统不会试图按照索引顺序对新的存储内容及更新记录进行重新聚集。
+
+在对一个表聚簇之后，MogDB会记录在哪个索引上建立了聚集。 CLUSTER table_name的聚集形式在之前的同一个索引的表上重新聚集。用户也可以用ALTER TABLE的CLUSTER或SET WITHOUT CLUSTER形式来设置索引来用于后续的聚集操作或清除任何之前的设置。
+
+不含参数的CLUSTER会将当前用户所拥有的数据库中的先前做过聚簇的所有表重新处理，或者系统管理员调用的这些表。
+
+在对一个表进行聚簇的时候，会在其上请求一个ACCESS EXCLUSIVE锁。这样就避免了在CLUSTER完成之前对此表执行其它的操作(包括读写)。
+
+## 注意事项
+
+- 只有行存B-tree索引支持CLUSTER操作。
+
+- 如果用户只是随机访问表中的行，那么表中数据的实际存储顺序是无关紧要的。但是， 如果对某些数据的访问多于其它数据，而且有一个索引将这些数据分组， 那么将使用CLUSTER中会有所帮助。如果从一个表中请求一定索引范围的值， 或者是一个索引值对应多行，CLUSTER也会有助于应用，因为如果索引标识出第一匹配行所在的存储页，所有其它行也可能已经在同一个存储页里了，这样便节省了磁盘访问的时间，加速了查询。
+
+- 在聚簇过程中，系统先创建一个按照索引顺序建立的表的临时拷贝。同时也建立表上的每个索引的临时拷贝。因此，需要磁盘上有足够的剩余空间， 至少是表大小和索引大小的和。
+
+- 因为CLUSTER记忆聚集信息，可以在第一次的时候手工对表进行聚簇，然后设置一个类似VACUUM的时间，这样就可以周期地自动对表进行聚簇操作。
+
+- 因为优化器记录着有关表的排序的统计，所以建议在新近聚簇的表上运行ANALYZE。否则，优化器可能会选择很差劲的查询规划。
+
+- CLUSTER不允许在事务中执行。
+- 如果没有打开xc_maintenance_mode参数，那么CLUSTER操作将跳过所有系统表。
+
+## 语法格式
+
+- 对一个表进行聚簇排序。
+
+  ```ebnf+diagram
+  Cluster ::= CLUSTER [ VERBOSE ] table_name [ USING index_name ];
+  ```
+
+- 对一个分区进行聚簇排序。
+
+  ```ebnf+diagram
+  Cluster ::= CLUSTER [ VERBOSE ] table_name PARTITION ( partition_name ) [ USING index_name ];
+  ```
+
+- 对已做过聚簇的表重新进行聚簇。
+
+  ```ebnf+diagram
+  Cluster ::= CLUSTER [ VERBOSE ];
+  ```
+
+## 参数说明
+
+- **VERBOSE**
+
+  启用显示进度信息。
+
+- **table_name**
+
+  表名称。
+
+  取值范围: 已存在的表名称。
+
+- **index_name**
+
+  索引名称。
+
+  取值范围: 已存在的索引名称。
+
+- **partition_name**
+
+  分区名称。
+
+  取值范围: 已存在的分区名称。
+
+## 示例
+
+```sql
+-- 创建一个分区表。
+mogdb=# CREATE TABLE tpcds.inventory_p1
+(
+    INV_DATE_SK               INTEGER               NOT NULL,
+    INV_ITEM_SK               INTEGER               NOT NULL,
+    INV_WAREHOUSE_SK          INTEGER               NOT NULL,
+    INV_QUANTITY_ON_HAND      INTEGER
+)
+PARTITION BY RANGE(INV_DATE_SK)
+(
+        PARTITION P1 VALUES LESS THAN(2451179),
+        PARTITION P2 VALUES LESS THAN(2451544),
+        PARTITION P3 VALUES LESS THAN(2451910),
+        PARTITION P4 VALUES LESS THAN(2452275),
+        PARTITION P5 VALUES LESS THAN(2452640),
+        PARTITION P6 VALUES LESS THAN(2453005),
+        PARTITION P7 VALUES LESS THAN(MAXVALUE)
+);
+
+-- 创建索引ds_inventory_p1_index1。
+mogdb=# CREATE INDEX ds_inventory_p1_index1 ON tpcds.inventory_p1 (INV_ITEM_SK) LOCAL;
+
+-- 对表tpcds.inventory_p1进行聚集。
+mogdb=# CLUSTER tpcds.inventory_p1 USING ds_inventory_p1_index1;
+
+-- 对分区p3进行聚集。
+mogdb=# CLUSTER tpcds.inventory_p1 PARTITION (p3) USING ds_inventory_p1_index1;
+
+-- 对数据库中可以进行聚集的表进聚集。
+mogdb=# CLUSTER;
+
+--删除索引。
+mogdb=# DROP INDEX tpcds.ds_inventory_p1_index1;
+
+--删除分区表。
+mogdb=# DROP TABLE tpcds.inventory_p1;
+```
+
+## 优化建议
+
+- cluster
+  - 建议在新近聚簇的表上运行ANALYZE。否则，优化器可能会选择很差劲的查询规划。
+  - 不允许在事务中执行CLUSTER。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/38-COMMENT.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/38-COMMENT.md
new file mode 100644
index 0000000000000000000000000000000000000000..67ef064541b0c971e5ce9c1def96f7aa397d7cc1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/38-COMMENT.md
@@ -0,0 +1,159 @@
+---
+title: COMMENT
+summary: COMMENT
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# COMMENT
+
+## 功能描述
+
+定义或修改一个对象的注释。
+
+## 注意事项
+
+- 每个对象只存储一条注释，因此要修改一个注释，对同一个对象发出一条新的COMMENT命令即可。要删除注释，在文本字符串的位置写上NULL即可。当删除对象时，注释自动被删除掉。
+- 目前注释浏览没有安全机制：任何连接到某数据库上的用户都可以看到所有该数据库对象的注释。共享对象（比如数据库、角色、表空间）的注释是全局存储的，连接到任何数据库的任何用户都可以看到它们。因此，不要在注释里存放与安全有关的敏感信息。
+- 对大多数对象，只有对象的所有者或者被授予了对象COMMENT权限的用户可以设置注释，系统管理员默认拥有该权限。
+- 角色没有所有者，所以COMMENT ON ROLE命令仅可以由系统管理员对系统管理员角色执行，有CREATEROLE权限的角色也可以为非系统管理员角色设置注释。系统管理员可以对所有对象进行注释。
+
+## 语法格式
+
+```ebnf+diagram
+Comment ::= COMMENT ON
+{
+  AGGREGATE agg_name (agg_type [, ...] ) |
+  CAST (source_type AS target_type) |
+  COLLATION object_name |
+  COLUMN { table_name'.'column_name | view_name'.'column_name } |
+  CONSTRAINT constraint_name ON table_name |
+  CONVERSION object_name |
+  DATABASE object_name |
+  DOMAIN object_name |
+  EXTENSION object_name |
+  FOREIGN DATA WRAPPER object_name |
+  FOREIGN TABLE object_name |
+  FUNCTION function_name ( [ {[ argmode ] [ argname ] argtype} [, ...] ] ) |
+  INDEX object_name |
+  LARGE OBJECT large_object_oid |
+  OPERATOR operator_name (left_type, right_type) |
+  OPERATOR CLASS object_name USING index_method |
+  OPERATOR FAMILY object_name USING index_method |
+  [ PROCEDURAL ] LANGUAGE object_name |
+  ROLE object_name |
+  SCHEMA object_name |
+  SERVER object_name |
+  TABLE object_name |
+  TABLESPACE object_name |
+  TEXT SEARCH CONFIGURATION object_name |
+  TEXT SEARCH DICTIONARY object_name |
+  TEXT SEARCH PARSER object_name |
+  TEXT SEARCH TEMPLATE object_name |
+  TYPE object_name |
+  VIEW object_name |
+  TRIGGER trigger_name ON table_name
+}
+   IS 'text';
+```
+
+## 参数说明
+
+- **agg_name**
+
+  聚集函数的名称。
+
+- **agg_type**
+
+  聚集函数参数的类型。
+
+- **source_type**
+
+  类型转换的源数据类型。
+
+- **target_type**
+
+  类型转换的目标数据类型。
+
+- **object_name**
+
+  对象名。
+
+- **table_name.column_name**
+
+  **view_name.column_name**
+
+  定义/修改注释的列名称。前缀可加表名称或者视图名称。
+
+- **constraint_name**
+
+  定义/修改注释的表约束的名称。
+
+- **table_name**
+
+  表的名称。
+
+- **function_name**
+
+  定义/修改注释的函数名称。
+
+- **argmode,argname,argtype**
+
+  函数参数的模式、名称、类型。
+
+- **large_object_oid**
+
+  定义/修改注释的大对象的OID值。
+
+- **operator_name**
+
+  操作符名称。
+
+- **left_type,right_type**
+
+  操作参数的数据类型（可以用模式修饰）。当前置或者后置操作符不存在时，可以增加NONE选项。
+
+- **trigger_name**
+
+  触发器名称。
+
+- **text**
+
+  注释。
+
+## 示例
+
+```sql
+mogdb=# CREATE TABLE tpcds.customer_demographics_t2
+(
+    CD_DEMO_SK                INTEGER               NOT NULL,
+    CD_GENDER                 CHAR(1)                       ,
+    CD_MARITAL_STATUS         CHAR(1)                       ,
+    CD_EDUCATION_STATUS       CHAR(20)                      ,
+    CD_PURCHASE_ESTIMATE      INTEGER                       ,
+    CD_CREDIT_RATING          CHAR(10)                      ,
+    CD_DEP_COUNT              INTEGER                       ,
+    CD_DEP_EMPLOYED_COUNT     INTEGER                       ,
+    CD_DEP_COLLEGE_COUNT      INTEGER
+)
+WITH (ORIENTATION = COLUMN,COMPRESSION=MIDDLE)
+;
+
+-- 为tpcds.customer_demographics_t2.cd_demo_sk列加注释。
+mogdb=# COMMENT ON COLUMN tpcds.customer_demographics_t2.cd_demo_sk IS 'Primary key of customer demographics table.';
+
+--创建一个由c_customer_sk小于150的内容组成的视图。
+mogdb=# CREATE VIEW tpcds.customer_details_view_v2 AS
+    SELECT *
+    FROM tpcds.customer
+    WHERE c_customer_sk < 150;
+
+-- 为tpcds.customer_details_view_v2视图加注释。
+mogdb=# COMMENT ON VIEW tpcds.customer_details_view_v2 IS 'View of customer detail';
+
+-- 删除view。
+mogdb=# DROP VIEW tpcds.customer_details_view_v2;
+
+-- 删除tpcds.customer_demographics_t2。
+mogdb=# DROP TABLE tpcds.customer_demographics_t2;
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/39-COMMIT-END.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/39-COMMIT-END.md
new file mode 100644
index 0000000000000000000000000000000000000000..7ce40210e1ad21b5ac06349087d8b33640d71326
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/39-COMMIT-END.md
@@ -0,0 +1,72 @@
+---
+title: COMMIT | END
+summary: COMMIT | END
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# COMMIT | END
+
+## 功能描述
+
+通过COMMIT或者END可完成提交事务的功能，即提交事务的所有操作。
+
+## 注意事项
+
+执行COMMIT这个命令的时候，命令执行者必须是该事务的创建者或系统管理员，且创建和提交操作可以不在同一个会话中。
+
+## 语法格式
+
+```ebnf+diagram
+CommitEnd ::= { COMMIT | END } [ WORK | TRANSACTION ] ;
+```
+
+## 参数说明
+
+- **COMMIT | END**
+
+  提交当前事务，让所有当前事务的更改为其他事务可见。
+
+- **WORK | TRANSACTION**
+
+  可选关键字，除了增加可读性没有其他任何作用。
+
+## 示例
+
+```sql
+--创建表。
+mogdb=# CREATE TABLE tpcds.customer_demographics_t2
+(
+    CD_DEMO_SK                INTEGER               NOT NULL,
+    CD_GENDER                 CHAR(1)                       ,
+    CD_MARITAL_STATUS         CHAR(1)                       ,
+    CD_EDUCATION_STATUS       CHAR(20)                      ,
+    CD_PURCHASE_ESTIMATE      INTEGER                       ,
+    CD_CREDIT_RATING          CHAR(10)                      ,
+    CD_DEP_COUNT              INTEGER                       ,
+    CD_DEP_EMPLOYED_COUNT     INTEGER                       ,
+    CD_DEP_COLLEGE_COUNT      INTEGER
+)
+WITH (ORIENTATION = COLUMN,COMPRESSION=MIDDLE)
+;
+
+--开启事务。
+mogdb=# START TRANSACTION;
+
+--插入数据。
+mogdb=# INSERT INTO tpcds.customer_demographics_t2 VALUES(1,'M', 'U', 'DOCTOR DEGREE', 1200, 'GOOD', 1, 0, 0);
+mogdb=# INSERT INTO tpcds.customer_demographics_t2 VALUES(2,'F', 'U', 'MASTER DEGREE', 300, 'BAD', 1, 0, 0);
+
+--提交事务，让所有更改永久化。
+mogdb=# COMMIT;
+
+--查询数据。
+mogdb=# SELECT * FROM tpcds.customer_demographics_t2;
+
+--删除表tpcds.customer_demographics_t2。
+mogdb=# DROP TABLE tpcds.customer_demographics_t2;
+```
+
+## 相关链接
+
+[ROLLBACK](121-ROLLBACK)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/4-ALTER-DEFAULT-PRIVILEGES.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/4-ALTER-DEFAULT-PRIVILEGES.md
new file mode 100644
index 0000000000000000000000000000000000000000..3620dec3c17eade523d8450efc70482690590720
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/4-ALTER-DEFAULT-PRIVILEGES.md
@@ -0,0 +1,208 @@
+---
+title: ALTER DEFAULT PRIVILEGES
+summary: ALTER DEFAULT PRIVILEGES
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER DEFAULT PRIVILEGES
+
+## 功能描述
+
+设置应用于将来创建的对象的权限（这不会影响分配到已有对象中的权限）。
+
+## 注意事项
+
+目前只支持表（包括视图）、 序列、函数、类型、密态数据库客户端主密钥和列加密密钥的权限更改。
+
+## 语法格式
+
+```ebnf+diagram
+AlterDafaultPrivileges ::= ALTER DEFAULT PRIVILEGES
+    [ FOR { ROLE | USER } target_role [, ...] ]
+    [ IN SCHEMA schema_name [, ...] ]
+    abbreviated_grant_or_revoke;
+```
+
+- 其中abbreviated_grant_or_revoke子句用于指定对哪些对象进行授权或回收权限。
+
+  ```ebnf+diagram
+  abbreviated_grant_or_revoke ::= grant_on_tables_clause
+        | grant_on_sequences_clause
+        | grant_on_functions_clause
+        | grant_on_types_clause
+        | grant_on_client_master_keys_clause
+        | grant_on_column_encryption_keys_clause
+        | revoke_on_tables_clause
+        | revoke_on_sequences_clause
+        | revoke_on_functions_clause
+        | revoke_on_types_clause
+        | revoke_on_client_master_keys_clause
+        | revoke_on_column_encryption_keys_clause
+  ```
+
+- 其中grant_on_tables_clause子句用于对表授权。
+
+  ```ebnf+diagram
+  grant_on_tables_clause ::= GRANT { { SELECT | INSERT | UPDATE | DELETE | TRUNCATE | REFERENCES | ALTER | DROP | COMMENT | INDEX | VACUUM }
+      [, ...] | ALL [ PRIVILEGES ] }
+      ON TABLES
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ]
+  ```
+
+- 其中grant_on_sequences_clause子句用于对序列授权。
+
+  ```ebnf+diagram
+  grant_on_sequences_clause ::= GRANT { { SELECT | UPDATE | USAGE | ALTER | DROP | COMMENT }
+      [, ...] | ALL [ PRIVILEGES ] }
+      ON SEQUENCES
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ]
+  ```
+
+- 其中grant_on_functions_clause子句用于对函数授权。
+
+  ```ebnf+diagram
+  grant_on_functions_clause ::= GRANT { { EXECUTE | ALTER | DROP | COMMENT } [, ...] | ALL [ PRIVILEGES ] }
+      ON FUNCTIONS
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ]
+  ```
+
+- 其中grant_on_types_clause子句用于对类型授权。
+
+  ```ebnf+diagram
+  grant_on_types_clause ::= GRANT { { USAGE | ALTER | DROP | COMMENT } [, ...] | ALL [ PRIVILEGES ] }
+      ON TYPES
+      TO { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ WITH GRANT OPTION ]
+  ```
+
+- 其中grant_on_client_master_keys_clause子句用于对客户端主密钥授权。
+
+    ```ebnf+diagram
+    grant_on_client_master_keys_clause ::= GRANT { { USAGE  | DROP } [, ...] | ALL [ PRIVILEGES ] }
+        ON CLIENT_MASTER_KEYS
+        TO { [ GROUP ] role_name | PUBLIC } [, ...]
+        [ WITH GRANT OPTION ]
+    ```
+
+- 其中grant_on_column_encryption_keys_clause子句用于对列加密密钥授权。
+
+    ```ebnf+diagram
+    grant_on_column_encryption_keys_clause ::= GRANT { { USAGE | DROP } [, ...] | ALL [ PRIVILEGES ] }
+        ON COLUMN_ENCRYPTION_KEYS
+        TO { [ GROUP ] role_name | PUBLIC } [, ...]
+        [ WITH GRANT OPTION ]
+    ```
+
+- 其中revoke_on_tables_clause子句用于回收表对象的权限。
+
+  ```ebnf+diagram
+  revoke_on_tables_clause ::= REVOKE [ GRANT OPTION FOR ]
+      { { SELECT | INSERT | UPDATE | DELETE | TRUNCATE | REFERENCES | ALTER | DROP | COMMENT | INDEX | VACUUM }
+      [, ...] | ALL [ PRIVILEGES ] }
+      ON TABLES
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT | CASCADE CONSTRAINTS ]
+  ```
+
+- 其中revoke_on_sequences_clause子句用于回收序列的权限。
+
+  ```ebnf+diagram
+  revoke_on_sequences_clause ::= REVOKE [ GRANT OPTION FOR ]
+      { { SELECT | UPDATE | USAGE | ALTER | DROP | COMMENT }
+      [, ...] | ALL [ PRIVILEGES ] }
+      ON SEQUENCES
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT | CASCADE CONSTRAINTS ]
+  ```
+
+- 其中revoke_on_functions_clause子句用于回收函数的权限。
+
+  ```ebnf+diagram
+  revoke_on_functions_clause ::= REVOKE [ GRANT OPTION FOR ]
+      { {EXECUTE | ALTER | DROP | COMMENT } [, ...] | ALL [ PRIVILEGES ] }
+      ON FUNCTIONS
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT | CASCADE CONSTRAINTS ]
+  ```
+
+- 其中revoke_on_types_clause子句用于回收类型的权限。
+
+  ```ebnf+diagram
+  revoke_on_types_clause ::= REVOKE [ GRANT OPTION FOR ]
+      { { USAGE | ALTER | DROP | COMMENT } [, ...] | ALL [ PRIVILEGES ] }
+      ON TYPES
+      FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+      [ CASCADE | RESTRICT | CASCADE CONSTRAINTS ]
+  ```
+
+- 其中revoke_on_client_master_keys_clause子句用于回收客户端主密钥的权限。
+
+    ```ebnf+diagram
+    revoke_on_client_master_keys_clause ::= REVOKE [ GRANT OPTION FOR ]
+        { { USAGE | DROP } [, ...] | ALL [ PRIVILEGES ] }
+        ON CLIENT_MASTER_KEYS
+        FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+        [ CASCADE | RESTRICT | CASCADE CONSTRAINTS ]
+    ```
+
+- 其中revoke_on_column_encryption_keys_clause子句用于回收列加密密钥的权限。
+
+    ```ebnf+diagram
+    revoke_on_column_encryption_keys_clause ::= REVOKE [ GRANT OPTION FOR ]
+        { { USAGE | DROP } [, ...] | ALL [ PRIVILEGES ] }
+        ON COLUMN_ENCRYPTION_KEYS
+        FROM { [ GROUP ] role_name | PUBLIC } [, ...]
+        [ CASCADE | RESTRICT | CASCADE CONSTRAINTS ]
+    ```
+
+## 参数说明
+
+- **target_role**
+
+  已有角色的名称。如果省略FOR ROLE/USER，则缺省值为当前角色/用户。
+
+  取值范围: 已有角色的名称。
+
+- **schema_name**
+
+  现有模式的名称。
+
+  target_role必须有schema_name的CREATE权限。
+
+  取值范围: 现有模式的名称。
+
+- **role_name**
+
+  被授予或者取消权限角色的名称。
+
+  取值范围: 已存在的角色名称。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 如果想删除一个被赋予了默认权限的角色，有必要恢复改变的缺省权限或者使用DROP OWNED BY来为角色脱离缺省的权限记录。
+
+## 示例
+
+```sql
+--将创建在模式tpcds里的所有表（和视图）的SELECT权限授予每一个用户。
+mogdb=# ALTER DEFAULT PRIVILEGES IN SCHEMA tpcds GRANT SELECT ON TABLES TO PUBLIC;
+
+--创建用户普通用户jack。
+mogdb=# CREATE USER jack PASSWORD 'xxxxxxxxx';
+
+--将tpcds下的所有表的插入权限授予用户jack。
+mogdb=# ALTER DEFAULT PRIVILEGES IN SCHEMA tpcds GRANT INSERT ON TABLES TO jack;
+
+--撤销上述权限。
+mogdb=# ALTER DEFAULT PRIVILEGES IN SCHEMA tpcds REVOKE SELECT ON TABLES FROM PUBLIC;
+mogdb=# ALTER DEFAULT PRIVILEGES IN SCHEMA tpcds REVOKE INSERT ON TABLES FROM jack;
+
+--删除用户jack。
+mogdb=# DROP USER jack;
+```
+
+## 相关链接
+
+[GRANT](108-GRANT)，[REVOKE](120-REVOKE)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/40-COMMIT-PREPARED.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/40-COMMIT-PREPARED.md
new file mode 100644
index 0000000000000000000000000000000000000000..887d95c232c327556b72131e34b2b327de7159e5
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/40-COMMIT-PREPARED.md
@@ -0,0 +1,49 @@
+---
+title: COMMIT PREPARED
+summary: COMMIT PREPARED
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# COMMIT PREPARED
+
+## 功能描述
+
+提交一个早先为两阶段提交准备好的事务。
+
+## 注意事项
+
+- 该功能仅在维护模式（GUC参数xc_maintenance_mode为on时）下可用。该模式谨慎打开，一般供维护人员排查问题使用，一般用户不应使用该模式。
+- 命令执行者必须是该事务的创建者或系统管理员，且创建和提交操作可以不在同一个会话中。
+- 事务功能由数据库自动维护，不应显式使用事务功能。
+
+## 语法格式
+
+```ebnf+diagram
+CommitPrepared ::= COMMIT PREPARED transaction_id ;
+```
+
+```ebnf+diagram
+CommitPrepared ::= COMMIT PREPARED transaction_id WITH CSN;
+```
+
+## 参数说明
+
+- **transaction_id**
+
+  待提交事务的标识符。它不能和任何当前预备事务已经使用了的标识符同名。
+
+- **CSN(commit sequence number)**
+
+  待提交事务的序列号。它是一个64位递增无符号数。
+
+## 示例
+
+```sql
+--提交标识符为的trans_test的事务。
+mogdb=# COMMIT PREPARED 'trans_test';
+```
+
+## 相关链接
+
+[PREPARE TRANSACTION](114-PREPARE-TRANSACTION)，[ROLLBACK PREPARED](122-ROLLBACK-PREPARED)。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/41-COPY.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/41-COPY.md
new file mode 100644
index 0000000000000000000000000000000000000000..08c59c3c43bf7cd8da8675761daf9a7f23d1a972
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/41-COPY.md
@@ -0,0 +1,637 @@
+---
+title: COPY
+summary: COPY
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# COPY
+
+## 功能描述
+
+通过COPY命令实现在表和文件之间拷贝数据。
+
+COPY FROM从一个文件拷贝数据到一个表，COPY TO把一个表的数据拷贝到一个文件。
+
+## 注意事项
+
+- 当参数enable_copy_server_files关闭时，只允许初始用户执行COPY FROM FILENAME或COPY TO FILENAME命令，当参数enable_copy_server_files打开，允许具有SYSADMIN权限的用户或继承了内置角色gs_role_copy_files权限的用户执行，但默认禁止对数据库配置文件，密钥文件，证书文件和审计日志执行COPY FROM FILENAME或COPY TO FILENAME，以防止用户越权查看或修改敏感文件。
+- COPY只能用于表，不能用于视图。
+- COPY TO需要读取的表的select权限，copy from需要插入的表的insert权限。
+- 如果声明了一个字段列表，COPY将只在文件和表之间拷贝已声明字段的数据。如果表中有任何不在字段列表里的字段，COPY FROM将为那些字段插入缺省值。
+- 如果声明了数据源文件，服务器必须可以访问该文件；如果指定了STDIN，数据将在客户前端和服务器之间流动，输入时，表的列与列之间使用TAB键分隔，在新的一行中以反斜杠和句点（\.）表示输入结束。
+- 如果数据文件的任意行包含比预期多或者少的字段，COPY FROM将抛出一个错误。
+- 数据的结束可以用一个只包含反斜杠和句点（\.）的行表示。如果从文件中读取数据，数据结束的标记是不必要的；如果在客户端应用之间拷贝数据，必须要有结束标记。
+- COPY FROM中\\N为空字符串，如果要输入实际数据值\\N ，使用\\N。
+- COPY FROM不支持在导入过程中对数据做预处理（比如说表达式运算，填充指定默认值等）。如果需要在导入过程中对数据做预处理，用户需先把数据导入到临时表中，然后执行SQL语句通过运算插入到表中，但此方法会导致I/O膨胀，降低导入性能。
+- COPY FROM在遇到数据格式错误时会回滚事务，但没有足够的错误信息，不方便用户从大量的原始数据中定位错误数据。
+- COPY FROM/TO适合低并发，本地小数据量导入导出。
+- 目标表存在trigger，支持COPY操作。
+
+## 语法格式
+
+- 从一个文件拷贝数据到一个表。
+
+  ```ebnf+diagram
+  Copy ::= COPY table_name [ ( column_name [, ...] ) ]
+        FROM { 'filename' | STDIN }
+            [ [ USING ] DELIMITERS 'delimiters' ]
+            [ WITHOUT ESCAPING ]
+            [ LOG ERRORS ]
+            [ REJECT LIMIT 'limit' ]
+            [ WITH ( option [, ...] ) ]
+            | copy_option
+            | TRANSFORM  ( { column_name [ data_type ] [ AS transform_expr ] } [, ...] )
+            | FIXED FORMATTER ( { column_name( offset, length ) } [, ...] ) [ ( option [, ...] ) | copy_option [  ...] ] ;
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  >
+  > 语法中的FIXED FORMATTER ( { column_name( offset, length ) } [, ...] )以及 [ ( option [, ...] ) | copy_option [ ...] ] 可以任意排列组合。
+
+- 把一个表的数据拷贝到一个文件。
+
+  ```ebnf+diagram
+  Copy ::= COPY table_name [ ( column_name [, ...] ) ]
+        TO { 'filename' | STDOUT }
+        [ [ USING ] DELIMITERS 'delimiters' ]
+        [ WITHOUT ESCAPING ]
+        [ WITH ( option [, ...] ) ]
+        | copy_option
+        | FIXED FORMATTER ( { column_name( offset, length ) } [, ...] ) [ ( option [, ...] ) | copy_option [  ...] ] ;
+  ```
+
+  ```ebnf+diagram
+  Copy ::= COPY query
+      TO { 'filename' | STDOUT }
+      [ WITHOUT ESCAPING ]
+      [ WITH ( option [, ...] ) ]
+      | copy_option
+      | FIXED FORMATTER ( { column_name( offset, length ) } [, ...] ) [ ( option [, ...] ) | copy_option [  ...] ] ;
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  >
+  > 1. COPY TO语法形式约束如下：
+  >    (query)与[USING] DELIMITER不兼容，即若COPY TO的数据来自于一个query的查询结果，那么COPY TO语法不能再指定[USING] DELIMITERS语法子句。
+  > 2. 对于FIXED FORMATTTER语法后面跟随的copy_option是以空格进行分隔的。
+  > 3. copy_option是指COPY原生的参数形式，而option是兼容外表导入的参数形式。
+  > 4. 语法中的FIXED FORMATTER ( { column_name( offset, length ) } [, ...] )以及 [ ( option [, ...] ) | copy_option [ ...] ] 可以任意排列组合。
+
+  其中可选参数option子句语法为：
+
+  ```ebnf+diagram
+  option ::= FORMAT 'format_name'
+  | OIDS [ boolean ]
+  | DELIMITER 'delimiter_character'
+  | NULL 'null_string'
+  | HEADER [ boolean ]
+  | FILEHEADER 'header_file_string'
+  | FREEZE [ boolean ]
+  | QUOTE 'quote_character'
+  | ESCAPE 'escape_character'
+  | EOL 'newline_character'
+  | NOESCAPING [ boolean ]
+  | FORCE_QUOTE { ( column_name [, ...] ) | * }
+  | FORCE_NOT_NULL ( column_name [, ...] )
+  | ENCODING 'encoding_name'
+  | IGNORE_EXTRA_DATA [ boolean ]
+  | FILL_MISSING_FIELDS [ boolean ]
+  | COMPATIBLE_ILLEGAL_CHARS [ boolean ]
+  | DATE_FORMAT 'date_format_string'
+  | TIME_FORMAT 'time_format_string'
+  | TIMESTAMP_FORMAT 'timestamp_format_string'
+  | SMALLDATETIME_FORMAT 'smalldatetime_format_string'
+  ```
+
+  其中可选参数copy_option子句语法为：
+
+  ```ebnf+diagram
+  copy_option ::= OIDS
+  | NULL 'null_string'
+  | HEADER
+  | FILEHEADER 'header_file_string'
+  | FREEZE
+  | FORCE_NOT_NULL column_name [, ...]
+  | FORCE_QUOTE { column_name [, ...] | * }
+  | BINARY
+  | CSV
+  | QUOTE [ AS ] 'quote_character'
+  | ESCAPE [ AS ] 'escape_character'
+  | EOL 'newline_character'
+  | ENCODING 'encoding_name'
+  | IGNORE_EXTRA_DATA
+  | FILL_MISSING_FIELDS
+  | COMPATIBLE_ILLEGAL_CHARS
+  | DATE_FORMAT 'date_format_string'
+  | TIME_FORMAT 'time_format_string'
+  | TIMESTAMP_FORMAT 'timestamp_format_string'
+  | SMALLDATETIME_FORMAT 'smalldatetime_format_string'
+  ```
+
+## 参数说明
+
+- **query**
+
+  其结果将被拷贝。
+
+  取值范围: 一个必须用圆括弧包围的SELECT或VALUES命令。
+
+- **table_name**
+
+  表的名称（可以有模式修饰）。
+
+  取值范围: 已存在的表名。
+
+- **column_name**
+
+  可选的待拷贝字段列表。
+
+  取值范围: 如果没有声明字段列表，将使用所有字段。
+
+- **STDIN**
+
+  声明输入是来自标准输入。
+
+- **STDOUT**
+
+  声明输出打印到标准输出。
+
+- **FIXED**
+
+  打开字段固定长度模式。在字段固定长度模式下，不能声明DELIMITER，NULL，CSV选项。指定FIXED类型后，不能再通过option或copy_option指定BINARY、CSV、TEXT等类型。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  > 定长格式定义如下：
+  >
+  > 1. 每条记录的每个字段长度相同。
+  > 2. 长度不足的字段以空格填充，数字类型字段左对齐，字符字段右对齐。
+  > 3. 字段和字段之间没有分隔符。
+
+- **[USING] DELIMITER 'delimiters'**
+
+  在文件中分隔各个字段的字符串，分隔符最大长度不超过10个字节。
+
+  取值范围: 不允许包含\.abcdefghijklmnopqrstuvwxyz0123456789中的任何一个字符。
+
+  缺省值：在文本模式下，缺省是水平制表符，在CSV模式下是一个逗号。
+
+- **WITHOUT ESCAPING**
+
+  在TEXT格式中，不对'\'和后面的字符进行转义。
+
+  取值范围: 仅支持TEXT格式。
+
+- **LOG ERRORS**
+
+  若指定，则开启对于COPY FROM语句中数据类型错误的容错机制。
+
+  取值范围: 仅支持导入（即COPY FROM）时指定。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  > 此容错选项的使用限制如下：
+  >
+  > - 此容错机制仅捕捉COPY FROM过程中数据库主节点上数据解析过程中相关的数据类型错误（DATA_EXCEPTION）。
+  > - COPY已有的容错选项（如IGNORE_EXTRA_DATA）开启时，对应类型的错误会按照已有的方式处理而不会报出异常，因此错误表也不会有相应数据。
+
+- **LOG ERRORS DATA**
+
+  LOG ERRORS DATA和LOG ERRORS的区别:
+
+  1. LOG ERRORS DATA会填充容错表的rawrecord字段。
+
+  2. 只有supper权限的用户才能使用LOG ERRORS DATA参数选项。
+
+     > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **注意：**
+     > 使用**“LOG ERRORS DATA”**时，若错误内容过于复杂可能存在写入容错表失败的风险，导致任务失败。
+
+- **REJECT LIMIT**'**limit'**
+
+  与LOG ERROR选项共同使用，对COPY FROM的容错机制设置数值上限，一旦此COPY FROM语句错误数据超过选项指定条数，则会按照原有机制报错。
+
+  取值范围: 正整数（1-INTMAX），'unlimited'（无最大值限制）
+
+  缺省值：若未指定LOG ERRORS，则会报错；若指定LOG ERRORS，则默认为0。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  > 如上述LOG ERRORS中描述的容错机制，REJECT LIMIT的计数也是按照执行COPY FROM的数据库主节点上遇到的解析错误数量计算，而不是数据库节点的错误数量。
+
+- **FORMATTER**
+
+  在固定长度模式中，定义每一个字段在数据文件中的位置。按照column(offset,length)格式定义每一列在数据文件中的位置。
+
+  取值范围:
+
+  - offset取值不能小于0，以字节为单位。
+  - length取值不能小于0，以字节为单位。
+
+  所有列的总长度和不能大于1GB。
+
+  文件中没有出现的列默认以空值代替。
+
+- **OPTION { option_name ' value ' }**
+
+  用于指定兼容外表的各类参数。
+
+  - FORMAT
+
+     数据源文件的格式。
+
+    取值范围: CSV、TEXT、FIXED、BINARY。
+
+    - CSV格式的文件，可以有效处理数据列中的换行符，但对一些特殊字符处理有欠缺。
+    - TEXT格式的文件，可以有效处理一些特殊字符，但无法正确处理数据列中的换行符。
+    - FIXED格式的文件，适用于每条数据的数据列都比较固定的数据，长度不足的列会添加空格补齐，过长的列则会自动截断。
+    - BINARY形式的选项会使得所有的数据被存储/读作二进制格式而不是文本。 这比TEXT和CSV格式的要快一些，但是一个BINARY格式文件可移植性比较差。
+
+    缺省值：TEXT
+
+  - DELIMITER
+
+    指定数据文件行数据的字段分隔符。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+    >
+    > - 分隔符不能是\\r和\\n。
+    > - 分隔符不能和null参数相同，CSV格式数据的分隔符不能和quote参数相同。
+    > - TEXT格式数据的分隔符不能包含： 小写字母、数字和特殊字符.\。
+    > - 数据文件中单行数据长度需&lt;1GB，如果分隔符较长且数据列较多的情况下，会影响导出有效数据的长度。
+    > - 分隔符推荐使用多字符和不可见字符。多字符例如'$^&'；不可见字符例如0x07，0x08，0x1b等。
+
+    取值范围: 支持多字符分隔符，但分隔符不能超过10个字节。
+
+    缺省值：
+
+    - TEXT格式的默认分隔符是水平制表符（tab）。
+    - CSV格式的默认分隔符为“,”。
+    - FIXED格式没有分隔符。
+
+  - NULL
+
+    用来指定数据文件中空值的表示。
+
+    取值范围:
+
+    - null值不能是\\r和\\n，最大为100个字符。
+    - null值不能和分隔符、quote参数相同。
+
+    缺省值：
+
+    - CSV格式下默认值是一个没有引号的空字符串。
+    - 在TEXT格式下默认值是\\N。
+
+  - HEADER
+
+    指定导出数据文件是否包含标题行，标题行一般用来描述表中每个字段的信息。header只能用于CSV，FIXED格式的文件中。
+
+    在导入数据时，如果header选项为on，则数据文本第一行会被识别为标题行，会忽略此行。如果header为off，而数据文件中第一行会被识别为数据。
+
+    在导出数据时，如果header选项为on，则需要指定fileheader。如果header为off，则导出数据文件不包含标题行。
+
+    取值范围: true/on，false/off。
+
+    缺省值：false
+
+  - QUOTE
+
+    CSV格式文件下的引号字符。
+
+    缺省值：双引号
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+    >
+    > - quote参数不能和分隔符、null参数相同。
+    > - quote参数只能是单字节的字符。
+    > - 推荐不可见字符作为quote，例如0x07，0x08，0x1b等。
+
+  - ESCAPE
+
+    CSV格式下，用来指定逃逸字符，逃逸字符只能指定为单字节字符。
+
+    缺省值：双引号。当与quote值相同时，会被替换为'\0'。
+
+    - EOL 'newline_character'
+
+        指定导入导出数据文件换行符样式。
+
+        取值范围: 支持多字符换行符，但换行符不能超过10个字节。常见的换行符，如\\r、\\n、\\r\\n（设成0x0D、0x0A、0x0D0A效果是相同的），其他字符或字符串，如$、#。
+
+        > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+        >
+        > - EOL参数只能用于TEXT格式的导入导出，不支持CSV格式和FIXED格式导入。为了兼容原有EOL参数，仍然支持导出CSV格式和FIXED格式时指定EOL参数为0x0D或0x0D0A。
+        > - EOL参数不能和分隔符、null参数相同。
+        > - EOL参数不能包含：.abcdefghijklmnopqrstuvwxyz0123456789。
+
+  - FORCE_QUOTE { ( column_name [, …] ) | * }
+
+    在CSV COPY TO模式下，强制在每个声明的字段周围对所有非NULL值都使用引号包围。NULL输出不会被引号包围。
+
+    取值范围: 已存在的字段。
+
+  - FORCE_NOT_NULL ( column_name [, …] )
+
+    在CSV COPY FROM模式下，指定的字段输入不能为空。
+
+    取值范围: 已存在的字段。
+
+  - ENCODING
+
+    指定数据文件的编码格式名称，缺省为当前数据库编码格式。
+
+  - IGNORE_EXTRA_DATA
+
+    若数据源文件比外表定义列数多，是否会忽略对多出的列。该参数只在数据导入过程中使用。
+
+    取值范围: true/on、false/off。
+
+    - 参数为true/on，若数据源文件比外表定义列数多，则忽略行尾多出来的列。
+
+    - 参数为false/off，若数据源文件比外表定义列数多，会显示如下错误信息。
+
+        ```sql
+        extra data after last expected column
+        ```
+
+        缺省值：false。
+
+        > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+        > 如果行尾换行符丢失，使两行变成一行时，设置此参数为true将导致后一行数据被忽略掉。
+
+  - COMPATIBLE_ILLEGAL_CHARS
+
+    导入非法字符容错参数。此语法仅对COPY FROM导入有效。
+
+    取值范围: true/on，false/off。
+
+    - 参数为true/on，则导入时遇到非法字符进行容错处理，非法字符转换后入库，不报错，不中断导入。
+    - 参数为false/off，导入时遇到非法字符进行报错，中断导入。
+
+        缺省值：false/off
+
+        > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+        > 导入非法字符容错规则如下：
+        > （1）对于'\0'，容错后转换为空格；
+        > （2）对于其他非法字符，容错后转换为问号；
+        > （3）若compatible_illegal_chars为true/on标识导入时对于非法字符进行容错处理，则若NULL、DELIMITER、QUOTE、ESCAPE设置为空格或问号则会通过如”illegal chars conversion may confuse COPY escape 0x20”等报错信息提示用户修改可能引起混淆的参数以避免导入错误。
+
+  - FILL_MISSING_FIELDS
+
+    当数据加载时，若数据源文件中一行的最后一个字段缺失的处理方式。
+
+    取值范围: true/on，false/off。
+
+    缺省值：false/off
+
+  - DATE_FORMAT
+
+    导入对于DATE类型指定格式。此参数不支持BINARY格式，会报“cannot specify bulkload compatibility options in BINARY mode”错误信息。此参数仅对COPY FROM导入有效。
+
+    取值范围: 合法DATE格式。可参考[时间和日期处理函数和操作符](8-date-and-time-processing-functions-and-operators)。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+    > 对于DATE类型内建为TIMESTAMP类型的数据库，在导入的时候，若需指定格式，可以参考下面的timestamp_format参数。
+
+  - TIME_FORMAT
+
+    导入对于TIME类型指定格式。此参数不支持BINARY格式，会报“cannot specify bulkload compatibility options in BINARY mode”错误信息。此参数仅对COPY FROM导入有效。
+
+    取值范围: 合法TIME格式，不支持时区。可参考[时间和日期处理函数和操作符](8-date-and-time-processing-functions-and-operators)。
+
+  - TIMESTAMP_FORMAT
+
+    导入对于TIMESTAMP类型指定格式。此参数不支持BINARY格式，会报“cannot specify bulkload compatibility options in BINARY mode”错误信息。此参数仅对COPY FROM导入有效。
+
+    取值范围: 合法TIMESTAMP格式，不支持时区。可参考[时间和日期处理函数和操作符](8-date-and-time-processing-functions-and-operators)。
+
+  - SMALLDATETIME_FORMAT
+
+    导入对于SMALLDATETIME类型指定格式。此参数不支持BINARY格式，会报“cannot specify bulkload compatibility options in BINARY mode”错误信息。此参数仅对COPY FROM导入有效。
+
+    取值范围: 合法SMALLDATETIME格式。可参考[时间和日期处理函数和操作符](8-date-and-time-processing-functions-and-operators)。
+
+- **COPY_OPTION { option_name ' value ' }**
+
+  用于指定COPY原生的各类参数。
+
+  - NULL null_string
+
+    用来指定数据文件中空值的表示。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+    > 在使用COPY FROM的时候，任何匹配这个字符串的字符串将被存储为NULL值，所以应该确保指定的字符串和COPY TO相同。
+
+    取值范围:
+
+    - null值不能是\\r和\\n，最大为100个字符。
+    - null值不能和分隔符、quote参数相同。
+
+    缺省值：
+
+    - 在TEXT格式下默认值是\\N。
+    - CSV格式下默认值是一个没有引号的空字符串。
+
+  - HEADER
+
+    指定导出数据文件是否包含标题行，标题行一般用来描述表中每个字段的信息。header只能用于CSV，FIXED格式的文件中。
+
+    在导入数据时，如果header选项为on，则数据文本第一行会被识别为标题行，会忽略此行。如果header为off，而数据文件中第一行会被识别为数据。
+
+    在导出数据时，如果header选项为on，则需要指定fileheader。如果header为off，则导出数据文件不包含标题行。
+
+  - FILEHEADER
+
+    导出数据时用于定义标题行的文件，一般用来描述每一列的数据信息。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+    >
+    > - 仅在header为on或true的情况下有效。
+    > - fileheader指定的是绝对路径。
+    > - 该文件只能包含一行标题信息，并以换行符结尾，多余的行将被丢弃（标题信息不能包含换行符）。
+    > - 该文件包括换行符在内长度不超过1M。
+
+  - FREEZE
+
+    将COPY加载的数据行设置为已经被frozen，就像这些数据行执行过VACUUM FREEZE。
+
+    这是一个初始数据加载的性能选项。仅当以下三个条件同时满足时，数据行会被frozen：
+
+    - 在同一事务中create或truncate这张表之后执行COPY。
+    - 当前事务中没有打开的游标。
+    - 当前事务中没有原有的快照。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+    > COPY完成后，所有其他会话将会立刻看到这些数据。但是这违反了MVCC可见性的一般原则，用户应当了解这样会导致潜在的风险。
+
+  - FORCE NOT NULL column_name [, …]
+
+    在CSV COPY FROM模式下，指定的字段不为空。若输入为空，则将视为长度为0的字符串。
+
+    取值范围: 已存在的字段。
+
+  - FORCE QUOTE { column_name [, …] | * }
+
+    在CSV COPY TO模式下，强制在每个声明的字段周围对所有非NULL值都使用引号包围。NULL输出不会被引号包围。
+
+    取值范围: 已存在的字段。
+
+  - BINARY
+
+    使用二进制格式存储和读取，而不是以文本的方式。在二进制模式下，不能声明DELIMITER、NULL、CSV选项。指定BINARY类型后，不能再通过option或copy_option指定CSV、FIXED、TEXT等类型。
+
+  - CSV
+
+    打开逗号分隔变量（CSV）模式。指定CSV类型后，不能再通过option或copy_option指定BINARY、FIXED、TEXT等类型。
+
+  - QUOTE [AS] 'quote_character'
+
+    CSV格式文件下的引号字符。
+
+    缺省值：双引号。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+    >
+    > - quote参数不能和分隔符、null参数相同。
+    > - quote参数只能是单字节的字符。
+    > - 推荐不可见字符作为quote，例如0x07，0x08，0x1b等。
+
+  - ESCAPE [AS] 'escape_character'
+
+    CSV格式下，用来指定逃逸字符，逃逸字符只能指定为单字节字符。
+
+    默认值为双引号。当与quote值相同时，会被替换为'\0'。
+
+  - EOL 'newline_character'
+
+    指定导入导出数据文件换行符样式。
+
+    取值范围: 支持多字符换行符，但换行符不能超过10个字节。常见的换行符，如\\r、\\n、\\r\\n（设成0x0D、0x0A、0x0D0A效果是相同的），其他字符或字符串，如$、#。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+    >
+    > - EOL参数只能用于TEXT格式的导入导出，不支持CSV格式和FIXED格式。为了兼容原有EOL参数，仍然支持导出CSV格式和FIXED格式时指定EOL参数为0x0D或0x0D0A。
+    > - EOL参数不能和分隔符、null参数相同。
+    > - EOL参数不能包含：.abcdefghijklmnopqrstuvwxyz0123456789。
+
+  - ENCODING 'encoding_name'
+
+    指定文件编码格式名称。
+
+    取值范围: 有效的编码格式。
+
+    缺省值：当前编码格式。
+
+  - IGNORE_EXTRA_DATA
+
+    指定当数据源文件比外表定义列数多时，忽略行尾多出来的列。该参数只在数据导入过程中使用。
+
+    若不使用该参数，在数据源文件比外表定义列数多，会显示如下错误信息。
+
+    ```sql
+    extra data after last expected column
+    ```
+
+  - COMPATIBLE_ILLEGAL_CHARS
+
+    指定导入时对非法字符进行容错处理，非法字符转换后入库。不报错，不中断导入。此参数不支持BINARY格式，会报“cannot specify bulkload compatibility options in BINARY mode”错误信息。此参数仅对COPY FROM导入有效。
+
+    若不使用该参数，导入时遇到非法字符进行报错，中断导入。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+    > 导入非法字符容错规则如下：
+    > （1）对于'\0'，容错后转换为空格；
+    > （2）对于其他非法字符，容错后转换为问号；
+    > （3）若compatible_illegal_chars为true/on标识，导入时对于非法字符进行容错处理，则若NULL、DELIMITER、QUOTE、ESCAPE设置为空格或问号则会通过如”illegal chars conversion may confuse COPY escape 0x20”等报错信息提示用户修改可能引起混淆的参数以避免导入错误。
+
+  - FILL_MISSING_FIELDS
+
+    当数据加载时，若数据源文件中一行的最后一个字段缺失的处理方式。
+
+    取值范围: true/on，false/off。
+
+    缺省值：false/off。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+    > 目前COPY指定此Option实际不会生效，即不会有相应的容错处理效果（不生效）。需要额外注意的是，打开此选项会导致解析器在数据库主节点数据解析阶段（即COPY错误表容错的涵盖范围）忽略此数据问题，而到数据库节点重新报错，从而使得COPY错误表（打开LOG ERRORS REJECT LIMIT）在此选项打开的情况下无法成功捕获这类少列的数据异常。因此请不要指定此选项。
+
+  - DATE_FORMAT 'date_format_string'
+
+    导入对于DATE类型指定格式。此参数不支持BINARY格式，会报“cannot specify bulkload compatibility options in BINARY mode”错误信息。此参数仅对COPY FROM导入有效。
+
+    取值范围: 合法DATE格式。可参考[时间和日期处理函数和操作符](8-date-and-time-processing-functions-and-operators)。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+    > 对于DATE类型内建为TIMESTAMP类型的数据库，在导入的时候，若需指定格式，可以参考下面的timestamp_format参数。
+
+  - TIME_FORMAT 'time_format_string'
+
+    导入对于TIME类型指定格式。此参数不支持BINARY格式，会报“cannot specify bulkload compatibility options in BINARY mode”错误信息。此参数仅对COPY FROM导入有效。
+
+    取值范围: 合法TIME格式，不支持时区。可参考[时间和日期处理函数和操作符](8-date-and-time-processing-functions-and-operators)。
+
+  - TIMESTAMP_FORMAT 'timestamp_format_string'
+
+    导入对于TIMESTAMP类型指定格式。此参数不支持BINARY格式，会报“cannot specify bulkload compatibility options in BINARY mode”错误信息。此参数仅对COPY FROM导入有效。
+
+    取值范围: 合法TIMESTAMP格式，不支持时区。可参考[时间和日期处理函数和操作符](8-date-and-time-processing-functions-and-operators)。
+
+  - SMALLDATETIME_FORMAT 'smalldatetime_format_string'
+
+    导入对于SMALLDATETIME类型指定格式。此参数不支持BINARY格式，会报“cannot specify bulkload compatibility options in BINARY mode”错误信息。此参数仅对COPY FROM导入有效。
+
+    取值范围: 合法SMALLDATETIME格式。可参考[时间和日期处理函数和操作符](8-date-and-time-processing-functions-and-operators)。
+
+  - TRANSFORM ( { column_name [ data_type ] [ AS transform_expr ] } [, ...] )
+
+    指定表中各个列的转换表达式；其中data_type指定该列在表达式参数中的数据类型；transform_expr为目标表达式，返回与表中目标列数据类型一致的结果值，表达式可参考[表达式](1-simple-expressions)。
+
+  COPY FROM能够识别的特殊反斜杠序列如下所示。
+
+  - **\\b**：反斜杠 （ASCII 8）
+  - **\\f**：换页（ASCII 12）
+  - **\\n**：换行符 （ASCII 10）
+  - **\\r**：回车符 （ASCII 13）
+  - **\\t**：水平制表符 （ASCII 9）
+  - **\\v**：垂直制表符 （ASCII 11）
+  - **\\digits**：反斜杠后面跟着一到三个八进制数，表示ASCII值为该数的字符。
+  - **\\xdigits**：反斜杠x后面跟着一个或两个十六进制位声明指定数值编码的字符。
+
+## 示例
+
+```sql
+--将tpcds.ship_mode中的数据拷贝到/home/omm/ds_ship_mode.dat文件中。
+mogdb=# COPY tpcds.ship_mode TO '/home/omm/ds_ship_mode.dat';
+
+--将tpcds.ship_mode 输出到stdout。
+mogdb=# COPY tpcds.ship_mode TO stdout;
+
+--创建tpcds.ship_mode_t1表。
+mogdb=# CREATE TABLE tpcds.ship_mode_t1
+(
+    SM_SHIP_MODE_SK           INTEGER               NOT NULL,
+    SM_SHIP_MODE_ID           CHAR(16)              NOT NULL,
+    SM_TYPE                   CHAR(30)                      ,
+    SM_CODE                   CHAR(10)                      ,
+    SM_CARRIER                CHAR(20)                      ,
+    SM_CONTRACT               CHAR(20)
+)
+WITH (ORIENTATION = COLUMN,COMPRESSION=MIDDLE)
+;
+
+--从stdin拷贝数据到表tpcds.ship_mode_t1。
+mogdb=# COPY tpcds.ship_mode_t1 FROM stdin;
+
+--从/home/omm/ds_ship_mode.dat文件拷贝数据到表tpcds.ship_mode_t1。
+mogdb=# COPY tpcds.ship_mode_t1 FROM '/home/omm/ds_ship_mode.dat';
+
+--从/home/omm/ds_ship_mode.dat文件拷贝数据到表tpcds.ship_mode_t1，应用TRANSFORM表达式转换，取SM_TYPE列左边10个字符插入到表中。
+openGauss=# COPY tpcds.ship_mode_t1 FROM '/home/omm/ds_ship_mode.dat' TRANSFORM (SM_TYPE AS LEFT(SM_TYPE, 10));
+
+--从/home/omm/ds_ship_mode.dat文件拷贝数据到表tpcds.ship_mode_t1，使用参数如下：导入格式为TEXT（format 'text'），分隔符为'\t'（delimiter E'\t'），忽略多余列（ignore_extra_data 'true'），不指定转义（noescaping 'true'）。
+mogdb=# COPY tpcds.ship_mode_t1 FROM '/home/omm/ds_ship_mode.dat' WITH(format 'text', delimiter E'\t', ignore_extra_data 'true', noescaping 'true');
+
+--从/home/omm/ds_ship_mode.dat文件拷贝数据到表tpcds.ship_mode_t1，使用参数如下：导入格式为FIXED（FIXED），指定定长格式（FORMATTER(SM_SHIP_MODE_SK(0, 2), SM_SHIP_MODE_ID(2,16), SM_TYPE(18,30), SM_CODE(50,10), SM_CARRIER(61,20), SM_CONTRACT(82,20))），忽略多余列（ignore_extra_data），有数据头（header）。
+mogdb=# COPY tpcds.ship_mode_t1 FROM '/home/omm/ds_ship_mode.dat' FIXED FORMATTER(SM_SHIP_MODE_SK(0, 2), SM_SHIP_MODE_ID(2,16), SM_TYPE(18,30), SM_CODE(50,10), SM_CARRIER(61,20), SM_CONTRACT(82,20)) header ignore_extra_data;
+
+--删除tpcds.ship_mode_t1。
+mogdb=# DROP TABLE tpcds.ship_mode_t1;
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/41.1-CREATE-AGGREGATE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/41.1-CREATE-AGGREGATE.md
new file mode 100644
index 0000000000000000000000000000000000000000..7b62c3546451338f5abb5e5fac561688aa5a237f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/41.1-CREATE-AGGREGATE.md
@@ -0,0 +1,88 @@
+---
+title: CREATE AGGREGATE
+summary: CREATE AGGREGATE
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# CREATE AGGREGATE
+
+## 功能描述
+
+定义一个新的聚合函数。
+
+## 语法格式
+
+```ebnf+diagram
+CreateAggregate ::= CREATE AGGREGATE name ( input_data_type [ , ... ] ) (
+    SFUNC = sfunc,
+    STYPE = state_data_type
+    [ , FINALFUNC = ffunc ]
+    [ , INITCOND = initial_condition ]
+    [ , SORTOP = sort_operator ]
+)
+```
+
+或者旧语法
+
+```ebnf+diagram
+CreateAggregate ::= CREATE AGGREGATE name (
+    BASETYPE = base_type,
+    SFUNC = sfunc,
+    STYPE = state_data_type
+    [ , FINALFUNC = ffunc ]
+    [ , INITCOND = initial_condition ]
+    [ , SORTOP = sort_operator ]
+)
+```
+
+## 参数说明
+
+- **name**
+
+  要创建的聚合函数名(可以有模式修饰) 。
+
+- **input_data_type**
+
+  该聚合函数要处理的输入数据类型。要创建一个零参数聚合函数，可以使用*代替输入数据类型列表。 （count(*)就是这种聚合函数的一个实例。 ）
+
+- **base_type**
+
+  在以前的CREATE AGGREGATE语法中，输入数据类型是通过basetype参数指定的，而不是写在聚合的名称之后。 需要注意的是这种以前语法仅允许一个输入参数。 要创建一个零参数聚合函数，可以将basetype指定为“ANY”（而不是*）。
+
+- **sfunc**
+
+  将在每一个输入行上调用的状态转换函数的名称。 对于有N个参数的聚合函数，sfunc必须有 +1 个参数，其中的第一个参数类型为state_data_type，其余的匹配已声明的输入数据类型。 函数必须返回一个state_data_type类型的值。 这个函数接受当前状态值和当前输入数据，并返回下个状态值。
+
+- **state_data_type**
+
+  聚合的状态值的数据类型。
+
+- **ffunc**
+
+  在转换完所有输入行后调用的最终处理函数，它计算聚合的结果。 此函数必须接受一个类型为state_data_type的参数。 聚合的输出数据 类型被定义为此函数的返回类型。 如果没有声明ffunc则使用聚合结果的状态值作为聚合的结果，且输出类型为state_data_type。
+
+- **initial_condition**
+
+  状态值的初始设置(值)。 它必须是一个state_data_type类型可以接受的文本常量值。 如果没有声明，状态值初始为 NULL 。
+
+- **sort_operator**
+
+  用于MIN或MAX类型聚合的排序操作符。 这个只是一个操作符名 (可以有模式修饰)。这个操作符假设接受和聚合一样的输入数据类型。
+
+## 示例
+
+```sql
+CREATE AGGREGATE sum (complex)
+(
+    sfunc = complex_add,
+    stype = complex,
+    initcond = '(0,0)'
+);
+
+SELECT sum(a) FROM test_complex;
+
+   sum
+-----------
+ (34,53.9)
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/41.2-CREATE-AUDIT-POLICY.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/41.2-CREATE-AUDIT-POLICY.md
new file mode 100644
index 0000000000000000000000000000000000000000..5092199a2f2461b9b6650f6a56b0de6f5b49e495
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/41.2-CREATE-AUDIT-POLICY.md
@@ -0,0 +1,108 @@
+---
+title: CREATE AUDIT POLICY
+summary: CREATE AUDIT POLICY
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# CREATE AUDIT POLICY
+
+## 功能描述
+
+创建统一审计策略。
+
+## 注意事项
+
+只有poladmin，sysadmin或初始用户能进行此操作。
+
+需要开启安全策略开关，即设置GUC参数enable_security_policy=on，审计策略才可以生效。
+
+## 语法格式
+
+```ebnf+diagram
+CreateAuditPolicy ::= CREATE AUDIT POLICY [ IF NOT EXISTS ] policy_name { { privilege_audit_clause | access_audit_clause } [ filter_group_clause ] [ ENABLE | DISABLE ] };
+```
+
+- privilege_audit_clause：
+
+  ```ebnf+diagram
+  privilege_audit_clause ::= PRIVILEGES { DDL | ALL } [ ON LABEL ( resource_label_name [, ... ] ) ]
+  ```
+
+- access_audit_clause：
+
+  ```ebnf+diagram
+  access_audit_clause ::= ACCESS { DML | ALL } [ ON LABEL ( resource_label_name [, ... ] ) ]
+  ```
+
+- filter_group_clause：
+
+  ```ebnf+diagram
+  filter_group_clause ::= FILTER ON { ( FILTER_TYPE ( filter_value [, ... ] ) ) [, ... ] }
+  ```
+
+## 参数说明
+
+- **policy_name**
+
+  审计策略名称，需要唯一，不可重复；
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- **DDL**
+
+  指的是针对数据库执行如下操作时进行审计，目前支持：CREATE、ALTER、DROP、ANALYZE、COMMENT、GRANT、REVOKE、SET、SHOW、LOGIN_ANY、LOGIN_FAILURE、LOGIN_SUCCESS、LOGOUT。
+
+- **ALL**
+
+  指的是上述DDL支持的所有对数据库的操作。
+
+- **resource_label_name**
+
+  资源标签名称。
+
+- **DML**
+
+  指的是针对数据库执行如下操作时进行审计，目前支持：SELECT、COPY、DEALLOCATE、DELETE、EXECUTE、INSERT、PREPARE、REINDEX、TRUNCATE、UPDATE。
+
+- **FILTER_TYPE**
+
+  描述策略过滤的条件类型，包括IP | APP | ROLES。
+
+- **filter_value**
+
+  指具体过滤信息内容。
+
+- **ENABLE|DISABLE**
+
+  可以打开或关闭统一审计策略。若不指定ENABLE|DISABLE，语句默认为ENABLE。
+
+## 示例
+
+```sql
+--创建dev_audit和bob_audit用户。
+mogdb=# CREATE USER dev_audit PASSWORD 'dev@1234';
+mogdb=# CREATE USER bob_audit password 'bob@1234';
+
+--创建一个表tb_for_audit
+mogdb=# CREATE TABLE tb_for_audit(col1 text, col2 text, col3 text);
+
+--创建资源标签
+mogdb=# CREATE RESOURCE LABEL adt_lb0 add TABLE(tb_for_audit);
+
+--对数据库执行create操作创建审计策略
+mogdb=# CREATE AUDIT POLICY adt1 PRIVILEGES CREATE;
+
+--对数据库执行select操作创建审计策略
+mogdb=# CREATE AUDIT POLICY adt2 ACCESS SELECT;
+
+--仅审计记录用户dev_audit和bob_audit在执行针对adt_lb0资源进行的create操作数据库创建审计策略
+mogdb=# CREATE AUDIT POLICY adt3 PRIVILEGES CREATE ON LABEL(adt_lb0) FILTER ON ROLES(dev_audit, bob_audit);
+
+--仅审计记录用户dev_audit和bob_audit,客户端工具为psql和gsql，IP地址为'10.20.30.40', '127.0.0.0/24'，在执行针对adt_lb0资源进行的select、insert、delete操作数据库创建审计策略。
+mogdb=# CREATE AUDIT POLICY adt4 ACCESS SELECT ON LABEL(adt_lb0), INSERT ON LABEL(adt_lb0), DELETE FILTER ON ROLES(dev_audit, bob_audit), APP(psql, gsql), IP('10.20.30.40', '127.0.0.0/24');
+```
+
+## 相关链接
+
+[ALTER AUDIT POLICY](1.2-ALTER-AUDIT-POLICY)，[DROP AUDIT POLICY](75.2-DROP-AUDIT-POLICY)。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/41.3-CREATE-CAST.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/41.3-CREATE-CAST.md
new file mode 100644
index 0000000000000000000000000000000000000000..166ade841f449bdc6533276e12ef893e0572eaa7
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/41.3-CREATE-CAST.md
@@ -0,0 +1,90 @@
+---
+title: CREATE CAST
+summary: CREATE CAST
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# CREATE CAST
+
+## 功能描述
+
+定义一个用户自定义的转换。
+
+## 注意事项
+
+DROP AGGREGATE删除一个现存的聚合函数，执行这条命令的用户必须是该聚合函数的所有者。
+
+## 语法格式
+
+```ebnf+diagram
+CreateCast ::= CREATE CAST (source_type AS target_type)
+    WITH FUNCTION function_name (argument_type [, ...])
+    [ AS ASSIGNMENT | AS IMPLICIT ]
+```
+
+```ebnf+diagram
+CreateCast ::= CREATE CAST (source_type AS target_type)
+    WITHOUT FUNCTION
+    [ AS ASSIGNMENT | AS IMPLICIT ]
+```
+
+```ebnf+diagram
+CreateCast ::= CREATE CAST (source_type AS target_type)
+    WITH INOUT
+    [ AS ASSIGNMENT | AS IMPLICIT ]
+```
+
+## 参数说明
+
+- **source_type**
+
+  转换的源数据类型。
+
+- **target_type**
+
+  转换的目标数据类型。
+
+- **function_name(argument_type [, …])**
+
+  用于执行转换的函数。 这个函数名可以是用模式名修饰的。 如果它没有用模式名修饰， 那么该函数将从模式搜索路径中找出来。 函数的结果数据类型必须匹配转换的目标类型。 它的参数在下面讨论。
+
+- **WITHOUT FUNCTION**
+
+  表明源类型是对目标类型是二进制可强制转换的，所以没有函数需要执行此转换。
+
+- **WITH INOUT**
+
+  表明转换是I/O转换，通过调用源数据类型的输出函数来执行，并将结果传给目标数据类型的输入函数。
+
+- **AS ASSIGNMENT**
+
+  表示转换可以在赋值模式下隐含调用。
+
+- **AS IMPLICIT**
+
+  表示转换可以在任何环境里隐含调用。
+
+  转换实现函数可以有一到三个参数。 第一个参数的类型必须与转换的源类型相同的，或可以从转换的源类型二进制可强制转换的。 第二个参数，如果存在，必须是integer类型；它接收这些与目标类型相关联的类型修饰符，或者若什么都没有则是-1。 第三个参数，如果存在，必须是boolean类型；若转换是一个显式类型转换则会收到true，否则是false。
+
+  一个转换函数的返回类型必须是与转换的目标类型相同或者对转换的目标类型二进制可强制转换 。
+
+  通常，一个转换必须有不同的源和目标数据类型。 然而，若有多于一个参数的转换实现函数，则允许声明一个有相同的源和目标类型的转换。 这用于表示系统目录中的特定类型的长度强制函数。 命名的函数用于强制一个该类型的值为第二个参数给出的类型修饰符值。
+
+  如果一个类型转换的源类型和目标类型不同，并且接收多于一个参数，它就表示从一种类型转换成另外一种类型只用一个步骤，并且同时实施长度转换。 如果没有这样的项可用， 那么转换成一个使用了类型修饰词的类型将涉及两个步骤，一个是在数据类型之间转换， 另外一个是施加修饰词指定的转换。
+
+  对域类型的转换目前没有作用。转换一般是针对域相关的所属数据类型。
+
+## 示例
+
+为了从类型bigint到类型int4创建一个指派映射要通过使用函数int4(bigint):
+
+```sql
+CREATE CAST (bigint AS int4) WITH FUNCTION int4(bigint) AS ASSIGNMENT;
+```
+
+（这个转换在系统中已经预先定义了。）
+
+## 兼容性
+
+CREATE CAST指令符合SQL标准，除了SQL没有为二进制可强制转换类型或者实现函数的额外参数来实现功能。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/42-CREATE-CLIENT-MASTER-KEY.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/42-CREATE-CLIENT-MASTER-KEY.md
new file mode 100644
index 0000000000000000000000000000000000000000..f13ee4b1abb2f5d501f306dc3c07d4baf6563c7a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/42-CREATE-CLIENT-MASTER-KEY.md
@@ -0,0 +1,59 @@
+---
+title: CREATE CLIENT MASTER KEY
+summary: CREATE CLIENT MASTER KEY
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE CLIENT MASTER KEY
+
+## 功能描述
+
+创建一个客户端主密钥对象，该对象可用于加密Column Encryption Key对象。
+
+## 注意事项
+
+本语法属于全密态数据库特有语法。
+
+当使用gsql连接数据库服务器时，需使用‘-C’参数，打开全密态数据库的开关，才能使用本语法。
+
+由本语法创建的CMK对象中，仅存储从独立的密钥管理工具/服务/组件中读取密钥的方法，而不存储密钥本身。
+
+## 语法格式
+
+```ebnf+diagram
+CreateClientMasterKey ::= CREATE CLIENT MASTER KEY client_master_key_name WITH (KEY_STORE = key_store_name, KEY_PATH = "key_path_value", ALGORITHM = algorithm_type)
+```
+
+## 参数说明
+
+- **client_master_key_name**
+
+  该参数作为密钥对象名，在同一命名空间下，需满足命名唯一性约束。
+
+  取值范围: 字符串，需符合标识符的命名规范。
+
+- **KEY_STORE**
+
+  指定管理CMK的密钥工具或组件；取值：目前仅支持localkms。
+
+- **KEY_PATH**
+
+  KEY_STORE负责管理多个CMK密钥，KEY_PATH选项用于在KEY_STORE中唯一标识CMK。取值类似：“key_path_value”。
+
+- **ALGORITHM**
+
+  由本语法创建的用于加密COLUMN ENCRYPTION KEY，该参数用于指定加密算法的类型。取值范围: RSA_2048、RSA3072和SM2。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** **密钥存储路径：**默认情况下，localkms将在`$LOCALKMS_FILE_PATH`路径下生成/读取/删除密钥文件，用户可手动配置该环境变量。但是，用户也可以不用单独配置该环境变量，在尝试获取`$LOCALKMS_FILE_PATH`失败时，localkms会尝试获取$GAUSSHOME/etc/localkms/路径，如果该路径存在，则将其作为密钥存储路径。 **密钥相关文件名：**使用CREATE CMK语法时，localkms将会创建四个与存储密钥相关的文件。示例：当KEY_PATH = “key_path_value”, 四个文件的名称分别为key_path_value.pub、key_path_value.pub.rand、 key_path_value.priv、 key_path_value.priv.rand。 所以，为了能够成功创建密钥相关文件，在密钥存储路径下，应该保证没有已存在的与密钥相关文件名同名的文件。
+
+## 示例
+
+```sql
+-- （1）使用普通账户alice，连接全密态数据库，
+[cmd] gsql -U alice -h $host -p $port -d $database -C -r
+
+-- （2）使用本语法创建客户端加密主密钥(CMK)对象
+mogdb=> CREATE CLIENT MASTER KEY a_cmk WITH (KEY_STORE = localkms, KEY_PATH = "key_path_value", ALGORITHM = RSA_2048);
+mogdb=> CREATE CLIENT MASTER KEY another_cmk WITH (KEY_STORE = localkms, KEY_PATH = "another_path_value", ALGORITHM = SM2);
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/43-CREATE-COLUMN-ENCRYPTION-KEY.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/43-CREATE-COLUMN-ENCRYPTION-KEY.md
new file mode 100644
index 0000000000000000000000000000000000000000..4dc914acbea5e00b1f384318e3279b93af2fa722
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/43-CREATE-COLUMN-ENCRYPTION-KEY.md
@@ -0,0 +1,58 @@
+---
+title: CREATE COLUMN ENCRYPTION KEY
+summary: CREATE COLUMN ENCRYPTION KEY
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE COLUMN ENCRYPTION KEY
+
+## 功能描述
+
+创建一个列加密密钥，该密钥可用于加密表中指定列。
+
+## 注意事项
+
+本语法属于全密态数据库特有语法。
+
+当使用gsql连接数据库服务器时，需使用‘-C’参数，打开全密态数据库的开关，才能使用本语法。
+
+由该语法创建CEK对象可用于列级加密。在定义表中列字段时，可指定一个CEK对象，用于加密该列。
+
+## 语法格式
+
+```ebnf+diagram
+CreateColumnEncryption ::= CREATE COLUMN ENCRYPTION KEY column_encryption_key_name WITH(CLIENT_MASTER_KEY = client_master_key_name, ALGORITHM = algorithm_type, ENCRYPTED_VALUE = encrypted_value);
+```
+
+## 参数说明
+
+- **column_encryption_key_name**
+
+  该参数作为密钥对象名，在同一命名空间下，需满足命名唯一性约束。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- **CLIENT_MASTER_KEY**
+
+  指定用于加密本CEK的CMK，取值为：CMK对象名，该CMK对象由CREATE CLIENT MASTER KEY语法创建。
+
+- **ALGORITHM**
+
+  指定该CEK将用于何种加密算法，取值范围为：AEAD_AES_256_CBC_HMAC_SHA256、AEAD_AES_128_CBC_HMAC_SHA256和SM4_SM3；
+
+- **ENCRYPTED_VALUE（可选项）**
+
+  该值为用户指定的密钥口令，密钥口令长度范围为28 ~ 256位，28位派生出来的密钥安全强度满足AES128，若用户需要用AES256，密钥口令的长度需要39位，如果不指定，则会自动生成256比特的密钥。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 国密算法约束：由于SM2、SM3、SM4等算法属于中国国家密码标准算法，为规避法律风险，需配套使用。即如果将CEK用于SM4_SM3算法，则仅能使用SM4算法来对该CEK进行加密。
+
+## 示例
+
+```sql
+--创建列加密密钥(CEK)
+mogdb=> CREATE COLUMN ENCRYPTION KEY a_cek WITH VALUES (CLIENT_MASTER_KEY = a_cmk, ALGORITHM  = AEAD_AES_256_CBC_HMAC_SHA256);
+CREATE COLUMN ENCRYPTION KEY
+mogdb=> CREATE COLUMN ENCRYPTION KEY another_cek WITH VALUES (CLIENT_MASTER_KEY = a_cmk, ALGORITHM  = SM4_SM3);
+CREATE COLUMN ENCRYPTION KEY
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/44-CREATE-DATABASE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/44-CREATE-DATABASE.md
new file mode 100644
index 0000000000000000000000000000000000000000..e77a621ca49797f631dd842c87c4577f6bfc6636
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/44-CREATE-DATABASE.md
@@ -0,0 +1,230 @@
+---
+title: CREATE DATABASE
+summary: CREATE DATABASE
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE DATABASE
+
+## 功能描述
+
+创建一个新的数据库。缺省情况下新数据库将通过复制标准系统数据库template0来创建，且仅支持使用template0来创建。
+
+## 注意事项
+
+- 只有拥有CREATEDB权限的用户才可以创建新数据库，系统管理员默认拥有此权限。
+- 不能在事务块中执行创建数据库语句。
+- 在创建数据库过程中，出现类似“Permission denied”的错误提示，可能是由于文件系统上数据目录的权限不足。出现类似“No space left on device”的错误提示，可能是由于磁盘满引起的。
+
+## 语法格式
+
+```ebnf+diagram
+CreateDatabase ::= CREATE DATABASE database_name
+    [ [ WITH ] { [ OWNER [=] user_name ] |
+               [ TEMPLATE [=] template ] |
+               [ ENCODING [=] encoding ] |
+               [ LC_COLLATE [=] lc_collate ] |
+               [ LC_CTYPE [=] lc_ctype ] |
+               [ DBCOMPATIBILITY [=] compatibilty_type ] |
+               [ TABLESPACE [=] tablespace_name ] |
+               [ CONNECTION LIMIT [=] connlimit ]}[...] ];
+```
+
+## 参数说明
+
+- **database_name**
+
+  数据库名称。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- **OWNER [ = ] user_name**
+
+  数据库所有者。缺省时，新数据库的所有者是当前用户。
+
+  取值范围: 已存在的用户名。
+
+- **TEMPLATE [ = ] template**
+
+  模板名。即从哪个模板创建新数据库。MogDB采用从模板数据库复制的方式来创建新的数据库。初始时，MogDB包含两个模板数据库template0、template1，以及一个默认的用户数据库postgres。
+
+  取值范围: 仅template0。
+
+- **ENCODING [ = ] encoding**
+
+  指定数据库使用的字符编码，可以是字符串（如'SQL_ASCII'）、整数编号。
+
+  不指定时，默认使用模版数据库的编码。模板数据库template0和template1的编码默认与操作系统环境相关。template1不允许修改字符编码，因此若要变更编码，请使用template0创建数据库。
+
+  常用取值：GBK、UTF8、Latin1。
+
+  **表 1** MogDB字符集
+
+  | **名称**       | **描述**                      | **语言**               | **是否服务器端？** | **ICU?** | **字节/字符** | **别名**                              |
+  | :---------------------------- | :---------------------------- | :--------------------- | :----------------- | :------- | :------------ | :------------------------------------ |
+  | BIG5           | Big Five                      | 繁体中文               | 否                 | 否       | 1-2           | WIN950, Windows950                    |
+  | EUC_CN         | 扩展UNIX编码-中国             | 简体中文               | 是                 | 是       | 1-3           | -                                     |
+  | EUC_JP         | 扩展UNIX编码-日本             | 日文                   | 是                 | 是       | 1-3           | -                                     |
+  | EUC_JIS_2004   | 扩展UNIX编码-日本, JIS X 0213 | 日文                   | 是                 | 否       | 1-3           | -                                     |
+  | EUC_KR         | 扩展UNIX编码-韩国             | 韩文                   | 是                 | 是       | 1-3           | -                                     |
+  | EUC_TW         | 扩展UNIX编码-台湾             | 繁体中文，台湾话       | 是                 | 是       | 1-3           | -                                     |
+  | GB18030        | 国家标准                      | 中文                   | 否                 | 否       | 1-4           | -                                     |
+  | GBK            | 扩展国家标准                  | 简体中文               | 是                 | 否       | 1-2           | WIN936, Windows936                    |
+  | ISO_8859_5     | ISO 8859-5, ECMA 113          | 拉丁语/西里尔语        | 是                 | 是       | 1             | -                                     |
+  | ISO_8859_6     | ISO 8859-6, ECMA 114          | 拉丁语/阿拉伯语        | 是                 | 是       | 1             | -                                     |
+  | ISO_8859_7     | ISO 8859-7, ECMA 118          | 拉丁语/希腊语          | 是                 | 是       | 1             | -                                     |
+  | ISO_8859_8     | ISO 8859-8, ECMA 121          | 拉丁语/希伯来语        | 是                 | 是       | 1             | -                                     |
+  | JOHAB          | JOHAB                         | 韩语                   | 否                 | 否       | 1-3           | -                                     |
+  | KOI8R          | KOI8-R                        | 西里尔语（俄语）       | 是                 | 是       | 1             | KOI8                                  |
+  | KOI8U          | KOI8-U                        | 西里尔语（乌克兰语）   | 是                 | 是       | 1             | -                                     |
+  | LATIN1         | ISO 8859-1, ECMA 94           | 西欧                   | 是                 | 是       | 1             | ISO88591                              |
+  | LATIN2         | ISO 8859-2, ECMA 94           | 中欧                   | 是                 | 是       | 1             | ISO88592                              |
+  | LATIN3         | ISO 8859-3, ECMA 94           | 南欧                   | 是                 | 是       | 1             | ISO88593                              |
+  | LATIN4         | ISO 8859-4, ECMA 94           | 北欧                   | 是                 | 是       | 1             | ISO88594                              |
+  | LATIN5         | ISO 8859-9, ECMA 128          | 土耳其语               | 是                 | 是       | 1             | ISO88599                              |
+  | LATIN6         | ISO 8859-10, ECMA 144         | 日耳曼语               | 是                 | 是       | 1             | ISO885910                             |
+  | LATIN7         | ISO 8859-13                   | 波罗的海               | 是                 | 是       | 1             | ISO885913                             |
+  | LATIN8         | ISO 8859-14                   | 凯尔特语               | 是                 | 是       | 1             | ISO885914                             |
+  | LATIN9         | ISO 8859-15                   | 带欧罗巴和口音的LATIN1 | 是                 | 是       | 1             | ISO885915                             |
+  | LATIN10        | ISO 8859-16, ASRO SR 14111    | 罗马尼亚语             | 是                 | 否       | 1             | ISO885916                             |
+  | MULE_INTERNAL  | Mule内部编码                  | 多语种编辑器           | 是                 | 否       | 1-4           | -                                     |
+  | SJIS           | Shift JIS                     | 日语                   | 否                 | 否       | 1-2           | Mskanji, ShiftJIS, WIN932, Windows932 |
+  | SHIFT_JIS_2004 | Shift JIS, JIS X 0213         | 日语                   | 否                 | 否       | 1-2           | -                                     |
+  | SQL_ASCII      | 未指定（见文本）              | ***任意\***            | 是                 | 否       | 1             | -                                     |
+  | UHC            | 统一韩语编码                  | 韩语                   | 否                 | 否       | 1-2           | WIN949, Windows949                    |
+  | UTF8           | Unicode, 8-bit                | ***所有\***            | 是                 | 是       | 1-4           | Unicode                               |
+  | WIN866         | Windows CP866                 | 西里尔语               | 是                 | 是       | 1             | ALT                                   |
+  | WIN874         | Windows CP874                 | 泰语                   | 是                 | 否       | 1             | -                                     |
+  | WIN1250        | Windows CP1250                | 中欧                   | 是                 | 是       | 1             | -                                     |
+  | WIN1251        | Windows CP1251                | 西里尔语               | 是                 | 是       | 1             | WIN                                   |
+  | WIN1252        | Windows CP1252                | 西欧                   | 是                 | 是       | 1             | -                                     |
+  | WIN1253        | Windows CP1253                | 希腊语                 | 是                 | 是       | 1             | -                                     |
+  | WIN1254        | Windows CP1254                | 土耳其语               | 是                 | 是       | 1             | -                                     |
+  | WIN1255        | Windows CP1255                | 希伯来语               | 是                 | 是       | 1             | -                                     |
+  | WIN1256        | Windows CP1256                | 阿拉伯语               | 是                 | 是       | 1             | -                                     |
+  | WIN1257        | Windows CP1257                | 波罗的海               | 是                 | 是       | 1             | -                                     |
+  | WIN1258        | Windows CP1258                | 越南语                 | 是                 | 是       | 1             | ABC, TCVN, TCVN5712, VSCII            |
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **注意：** 需要注意并非所有的客户端API都支持上面列出的字符集。 SQL_ASCII设置与其他设置表现得相当不同。如果服务器字符集是SQL_ASCII，服务器把字节值0-127根据 ASCII标准解释，而字节值128-255则当作无法解析的字符。如果设置为SQL_ASCII，就不会有编码转换。因此，这个设置基本不是用来声明所使用的指定编码， 因为这个声明会忽略编码。在大多数情况下，如果你使用了任何非ASCII数据，那么使用 SQL_ASCII设置都是不明智的，因为MogDB将无法帮助你转换或者校验非ASCII字符。
+  >
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+  >
+  > - 指定新的数据库字符集编码必须与所选择的本地环境中（LC_COLLATE和LC_CTYPE）的设置兼容。
+  > - 当指定的字符编码集为GBK时，部分中文生僻字无法直接作为对象名。这是因为GBK第二个字节的编码范围在0x40-0x7E之间时，字节编码与ASCII字符@A-Z[]\^_`a-z{|}重叠。其中@[]^_'{|}是数据库中的操作符，直接作为对象名时，会语法报错。例如“侤”字，GBK16进制编码为0x8240，第二个字节为0x40，与ASCII“@”符号编码相同，因此无法直接作为对象名使用。如果确实要使用，可以在创建和访问对象时，通过增加双引号来规避这个问题。
+  > - 若客户端编码为A，服务器端编码为B，则需要满足数据库中存在编码格式A与B的转换，例如：若服务器端编码为gb18030，由于当前数据库不支持gb18030与gbk的相互转换，所以此时设置客户端编码格式为gbk时，会报错"Conversion between GB18030 and GBK is not supported."。数据库能够支持的所有的编码格式转换详见系统表pg_conversion。
+
+- **LC_COLLATE [ = ] lc_collate**
+
+  指定新数据库使用的字符集。例如，通过lc_collate = 'zh_CN.gbk'设定该参数。
+
+  该参数的使用会影响到对字符串的排序顺序（如使用ORDER BY执行，以及在文本列上使用索引的顺序）。默认是使用模板数据库的排序顺序。
+
+  取值范围: 有效的排序类型。
+
+- **LC_CTYPE [ = ] lc_ctype**
+
+  指定新数据库使用的字符分类。例如，通过lc_ctype = 'zh_CN.gbk'设定该参数。该参数的使用会影响到字符的分类，如大写、小写和数字。默认是使用模板数据库的字符分类。
+
+  取值范围: 有效的字符分类。
+
+- **DBCOMPATIBILITY [ = ] compatibility_type**
+
+  指定兼容的数据库的类型。取值范围: A、B、C、PG。分别表示兼容Oracle、MySQL、Teradata和PostgreSQL。但是C目前已经放弃支持，因此常用的取值是A、B、PG，默认兼容A。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  >
+  > - A兼容性下，数据库将空字符串作为NULL处理，数据类型DATE会被替换为TIMESTAMP(0) WITHOUT TIME ZONE。
+  > - 将字符串转换成整数类型时，如果输入不合法，B兼容性会将输入转换为0，而其它兼容性则会报错。
+  > - PG兼容性下，CHAR和VARCHAR以字符为计数单位，其它兼容性以字节为计数单位。例如，对于UTF-8字符集，CHAR(3)在PG兼容性下能存放3个中文字符，而在其它兼容性下只能存放1个中文字符。
+
+- **TABLESPACE [ = ] tablespace_name**
+
+  指定数据库对应的表空间。
+
+  取值范围: 已存在表空间名。
+
+- **CONNECTION LIMIT [ = ] connlimit**
+
+  数据库可以接受的并发连接数。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+  >
+  > - 系统管理员不受此参数的限制。
+  > - connlimit数据库主节点单独统计，MogDB整体的连接数 = connlimit * 当前正常数据库主节点个数。
+
+  取值范围: &gt;=-1的整数。默认值为-1，表示没有限制。
+
+有关字符编码的一些限制：
+
+- 若区域设置为C（或POSIX），则允许所有的编码类型，但是对于其他的区域设置，字符编码必须和区域设置相同。
+- 若字符编码方式是SQL_ASCII，并且修改者为管理员用户时，则字符编码可以和区域设置不相同。
+- 编码和区域设置必须匹配模板数据库，除了将template0当作模板。 因为其他数据库可能会包含不匹配指定编码的数据，或者可能包含排序顺序受LC_COLLATE和LC_CTYPE影响的索引。复制这些数据会导致在新数据库中的索引失效。template0是不包含任何会受到影响的数据或者索引。
+
+## 示例
+
+```sql
+--创建jim和tom用户。
+mogdb=# CREATE USER jim PASSWORD 'xxxxxxxxx';
+mogdb=# CREATE USER tom PASSWORD 'xxxxxxxxx';
+
+--创建一个GBK编码的数据库music（本地环境的编码格式必须也为GBK）。
+mogdb=# CREATE DATABASE music ENCODING 'GBK' template = template0;
+
+--创建数据库music2，并指定所有者为jim。
+mogdb=# CREATE DATABASE music2 OWNER jim;
+
+--用模板template0创建数据库music3，并指定所有者为jim。
+mogdb=# CREATE DATABASE music3 OWNER jim TEMPLATE template0;
+
+--设置music数据库的连接数为10。
+mogdb=# ALTER DATABASE music CONNECTION LIMIT= 10;
+
+--将music名称改为music4。
+mogdb=# ALTER DATABASE music RENAME TO music4;
+
+--将数据库music2的所属者改为tom。
+mogdb=# ALTER DATABASE music2 OWNER TO tom;
+
+--设置music3的表空间为PG_DEFAULT。
+mogdb=# ALTER DATABASE music3 SET TABLESPACE PG_DEFAULT;
+
+--关闭在数据库music3上缺省的索引扫描。
+mogdb=# ALTER DATABASE music3 SET enable_indexscan TO off;
+
+--重置enable_indexscan参数。
+mogdb=# ALTER DATABASE music3 RESET enable_indexscan;
+
+--删除数据库。
+mogdb=# DROP DATABASE music2;
+mogdb=# DROP DATABASE music3;
+mogdb=# DROP DATABASE music4;
+
+--删除jim和tom用户。
+mogdb=# DROP USER jim;
+mogdb=# DROP USER tom;
+
+--创建兼容PG格式的数据库。
+mogdb=# CREATE DATABASE pg_compatible_db DBCOMPATIBILITY 'C';
+
+--创建兼容Oracle的数据库。
+mogdb=# CREATE DATABASE ora_compatible_db DBCOMPATIBILITY 'A';
+
+--删除兼容PG、Oracle格式的数据库。
+mogdb=# DROP DATABASE pg_compatible_db;
+mogdb=# DROP DATABASE ora_compatible_db;
+```
+
+## 相关链接
+
+[ALTER DATABASE](2-ALTER-DATABASE)，[DROP DATABASE](78-DROP-DATABASE)
+
+## 优化建议
+
+- **create database**
+
+  事务中不支持创建database。
+
+- **ENCODING LC_COLLATE LC_CTYPE**
+
+  当新建数据库Encoding、LC-Collate 或LC_Ctype与模板数据库（SQL_ASCII）不匹配（为'GBK' /'UTF8'/'LATIN1'）时，必须指定template [=] template0。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/45-CREATE-DATA-SOURCE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/45-CREATE-DATA-SOURCE.md
new file mode 100644
index 0000000000000000000000000000000000000000..ba86c18f850c3eafc1f3e4dd0ca86766ce3c1dd4
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/45-CREATE-DATA-SOURCE.md
@@ -0,0 +1,96 @@
+---
+title: CREATE DATA SOURCE
+summary: CREATE DATA SOURCE
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE DATA SOURCE
+
+## 功能描述
+
+创建一个新的外部数据源对象，该对象用于定义MogDB要连接的目标库信息。
+
+## 注意事项
+
+- Data Source名称在数据库中需唯一，遵循标识符命名规范，长度限制为63字节，过长则会被截断。
+- 只有系统管理员或初始用户才有权限创建Data Source对象。且创建该对象的用户为其默认属主。
+- 当在OPTIONS中出现password选项时，需要保证MogDB每个节点的`$GAUSSHOME/bin`目录下存在datasource.key.cipher和datasource.key.rand文件，如果不存在这两个文件，请使用`gs_guc`工具生成并使用`gs_ssh`工具发布到openGauss每个节`$GAUSSHOME/bin`目录下。
+
+## 语法格式
+
+```ebnf+diagram
+CreateDataSource ::= CREATE DATA SOURCE src_name
+    [TYPE 'type_str']
+    [VERSION {'version_str' | NULL}]
+    [OPTIONS (optname 'optvalue' )];
+```
+
+## 参数说明
+
+- **src_name**
+
+  新建Data Source对象的名称，需在数据库内部唯一。
+
+  取值范围: 字符串，要符标识符的命名规范。
+
+- **TYPE**
+
+  新建Data Source对象的类型，可缺省。
+
+  取值范围: 空串或非空字符串。
+
+- **VERSION**
+
+  新建Data Source对象的版本号，可缺省或NULL值。
+
+  取值范围: 空串或非空字符串或NULL。
+
+- **OPTIONS**
+
+  Data Source对象的选项字段，创建时可省略，如若指定，其关键字如下：
+
+  - optname
+
+    选项名称。
+
+    取值范围: dsn， username， password， encoding。不区分大小写
+
+    - dsn  对应odbc配置文件中的DSN
+    - username/password对应连接目标库的用户名和密码。
+
+        MogDB在后台会对用户输入的username/password加密以保证安全性。该加密所需密钥文件需要使用gs_guc工具生成并使用gs_ssh工具发布到MogDB每个节点的$GAUSSHOME/bin目录下。username/password不应当包含'encryptOpt'前缀，否则会被认为是加密后的密文。
+
+    - encoding表示与目标库交互的字符串编码方式（含发送的SQL语句和返回的字符类型数据），此处创建对象时不检查encoding取值的合法性，能否正确编解码取决于用户提供的编码方式是否在数据库本身支持的字符编码范围内。
+
+  - optvalue
+
+    选项值。
+
+    取值范围: 空或者非空字符串。
+
+## 示例
+
+```sql
+--创建一个空的Data Source对象，不含任何信息。
+mogdb=# CREATE DATA SOURCE ds_test1;
+
+--创建一个Data Source对象，含TYPE信息，VERSION为NULL。
+mogdb=# CREATE DATA SOURCE ds_test2 TYPE 'MPPDB' VERSION NULL;
+
+--创建一个Data Source对象，仅含OPTIONS。
+mogdb=#  CREATE DATA SOURCE ds_test3 OPTIONS (dsn 'MogDB', encoding 'utf8');
+
+--创建一个Data Source对象，含TYPE, VERSION, OPTIONS。
+mogdb=# CREATE DATA SOURCE ds_test4 TYPE 'unknown' VERSION '11.2.3' OPTIONS (dsn 'MogDB', username 'userid', password 'pwd@123456', encoding '');
+
+--删除Data Source对象。
+mogdb=# DROP DATA SOURCE ds_test1;
+mogdb=# DROP DATA SOURCE ds_test2;
+mogdb=# DROP DATA SOURCE ds_test3;
+mogdb=# DROP DATA SOURCE ds_test4;
+```
+
+## 相关链接
+
+[ALTER DATA SOURCE](3-ALTER-DATA-SOURCE),  [DROP DATA SOURCE](79-DROP-DATA-SOURCE)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/46-CREATE-DIRECTORY.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/46-CREATE-DIRECTORY.md
new file mode 100644
index 0000000000000000000000000000000000000000..0fa88bf5368df6ac431c8aed4196078fb78b726b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/46-CREATE-DIRECTORY.md
@@ -0,0 +1,58 @@
+---
+title: CREATE DIRECTORY
+summary: CREATE DIRECTORY
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE DIRECTORY
+
+## 功能描述
+
+使用CREATE DIRECTORY语句创建一个目录对象，该目录对象定义了服务器文件系统上目录的别名，用于存放用户使用的数据文件。
+
+## 注意事项
+
+- 当enable_access_server_directory=off时，只允许初始用户创建directory对象；当enable_access_server_directory=on时，具有SYSADMIN权限的用户和继承了内置角色gs_role_directory_create权限的用户可以创建directory对象。
+- 创建用户默认拥有此路径的READ和WRITE操作权限。
+- 目录的默认owner为创建directory的用户。
+- 以下路径禁止创建：
+  - 路径含特殊字符。
+  - 路径是相对路径。
+  - 路径是符号连接。
+- 创建目录时会进行以下合法性校验：
+  - 创建时会检查添加路径是否为操作系统实际存在路径，如不存在会提示用户使用风险。
+  - 创建时会校验数据库初始化（omm）用户对于添加路径的权限(即操作系统目录权限，读/写/执行 - R/W/X)，如果权限不全，会提示用户使用风险。
+- 在MogDB环境下用户指定的路径需要用户保证各节点上路径的一致性，否则在不同节点上执行会产生找不到路径的问题。
+
+## 语法格式
+
+```ebnf+diagram
+CreateDirectory ::= CREATE [OR REPLACE] DIRECTORY directory_name
+AS 'path_name';
+```
+
+## 参数说明
+
+- **directory_name**
+
+  目录名称。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- **path_name**
+
+  操作系统的路径。
+
+  取值范围:  有效的操作系统路径。
+
+## 示例
+
+```sql
+--创建目录。
+mogdb=# CREATE OR REPLACE DIRECTORY  dir  as '/tmp/';
+```
+
+## 相关链接
+
+[ALTER DIRECTORY](5-ALTER-DIRECTORY)，[DROP DIRECTORY](80-DROP-DIRECTORY)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/46.1-CREATE-EXTENSION.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/46.1-CREATE-EXTENSION.md
new file mode 100644
index 0000000000000000000000000000000000000000..62df15f77d6faa16bec6fba8d7e3ef1d5ec6ae52
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/46.1-CREATE-EXTENSION.md
@@ -0,0 +1,59 @@
+---
+title: CREATE EXTENSION
+summary: CREATE EXTENSION
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# CREATE EXTENSION
+
+## 功能描述
+
+安装一个扩展。
+
+## 注意事项
+
+- CREATE EXTENSION命令安装一个新的扩展到一个数据库中，必须保证没有同名的扩展已经被安装。
+- 安装一个扩展意味着执行一个扩展的脚本文件，这个脚本会创建一个新的SQL实体，例如函数、数据类型、操作符、和索引支持的方法。
+- 安装扩展需要有和创建他的组件对象相同的权限。对于大多数扩展这意味着需要超户或者数据库所有者的权限，对于后续的权限检查和该扩展脚本所创建的实体，运行CREATE EXTENSION命令的角色将变为扩展的所有者。
+
+## 语法格式
+
+```ebnf+diagram
+CreateExtension ::= CREATE EXTENSION [ IF NOT EXISTS ] extension_name
+[ WITH ] [ SCHEMA schema_name ]
+[ VERSION version ]
+[ FROM old_version ]
+```
+
+## 参数说明
+
+- **IF NOT EXISTS**
+
+  如果系统已经存在一个同名的扩展，不会报错。这种情况下会给出一个提示。请注意该参数不保证系统存在的扩展和现在脚本创建的扩展相同。
+
+- **extension_name**
+
+  将被安装扩展的名字。
+
+- **schema_name**
+
+  扩展的实例被安装在该模式下，扩展的内容可以被重新安装。指定的模式必须已经存在，如果没有指定，扩展的控制文件也不指定一个模式，这样将使用默认模式。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **注意：** 扩展不认为它在任何模式里面：扩展在一个数据库范围内的名字是不受限制的，但是一个扩展的实例是属于一个模式的。
+
+- **version**
+
+  安装扩展的版本，可以写为一个标识符或者字符串.默认的版本在扩展的控制文件中指定。
+
+- **old_version**
+
+  当你想升级安装“old style”模块中没有的内容时,你必须指定FROM old_version。这个选项使CREATE EXTENSION 运行一个安装脚本将新的内容安装到扩展中，而不是创建一个新的实体。注意SCHEMA指定了包括这些已存在实体的模式。
+
+## 示例
+
+在当前数据库安装hstore扩展：
+
+```sql
+CREATE EXTENSION hstore;
+```
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/47-CREATE-FOREIGN-TABLE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/47-CREATE-FOREIGN-TABLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..9c518dc343df70f14ddd99d3725d1160ea77c35c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/47-CREATE-FOREIGN-TABLE.md
@@ -0,0 +1,145 @@
+---
+title: CREATE FOREIGN TABLE
+summary: CREATE FOREIGN TABLE
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE FOREIGN TABLE
+
+## 功能描述
+
+创建外表。
+
+## 注意事项
+
+- 外表中暂不支持使用系统列（如tableoid，ctid等）。
+- 其中Private和Shares模式的外表，需要初始用户和运维模式下（operation_mode）的运维管理员权限。
+
+## 语法格式
+
+```ebnf+diagram
+CreateForeignTable ::= CREATE FOREIGN TABLE [ IF NOT EXISTS ] table_name ( [
+    column_name type_name [ OPTIONS ( option 'value') ] [ COLLATE collation ] [ column_constraint [ ... ] ]
+    [, ... ]
+] )
+  SERVER server_name
+[ OPTIONS ( option 'value' ) ]
+```
+
+这里column_constraint可以是:
+
+```ebnf+diagram
+column_constraint ::= [ CONSTRAINT constraint_name ]
+{ NOT NULL |
+  NULL |
+  DEFAULT default_expr }
+```
+
+## 参数说明
+
+- **IF NOT EXISTS**
+
+  如果已经存在相同名称的表，不会抛出一个错误，而会发出一个通知，告知表关系已存在。
+
+- **table_name**
+
+  外表的表名。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- **column_name**
+
+  外表中的字段名。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- **type_name**
+
+  字段的数据类型。
+
+- **SERVER server_name**
+
+  外表的server名称。默认值为mot_server。
+
+- **OPTIONS ( option 'value' [, … ] )**
+
+  选项与新外部表或外部表中的字段有关。允许的选项名称和值，是由每一个外部数据封装器指定的。 也是通过外部数据封装器的验证函数来验证。重复的选项名称是不被允许的（尽管表选项和表字段选项可以有相同的名字）。
+
+  - oracle_fdw支持的options包括：
+
+    - **table**
+
+        oracle server侧的表名。需要同oracle系统表中记录的表名完全一致，通常是由大写字符组成。
+
+    - **schema**
+
+        表所对应的schema（或owner）。需要同oracle系统表中记录的表名完全一致，通常是由大写字符组成。
+
+  - mysql_fdw支持的options包括：
+
+    - **dbname**
+
+        MySQL的database名称。
+
+    - **table_name**
+
+        MySQL侧的表名。
+
+  - postgres_fdw支持的options包括：
+
+    - **schema_name**
+
+        远端server的schema名称。如果不指定的话，将使用外表自身的schema名称作为远端的schema名称。
+
+    - **table_name**
+
+        远端server的表名。如果不指定的话，将使用外表自身的表名作为远端的表名。
+
+    - **column_name**
+
+        远端server的表的列名。如果不指定的话，将使用外表自身的列名作为远端的的表的列名。
+
+  - file_fdw支持的options包括：
+
+    - filename
+
+        指定要读取的文件，必需的参数，且必须是一个绝对路径名。
+
+    - format
+
+        远端server的文件格式，支持text/csv/binary/fixed四种格式，和COPY语句的FORMAT选项相同。
+
+    - header
+
+        指定的文件是否有标题行，与COPY语句的HEADER选项相同。
+
+    - delimiter
+
+        指定文件的分隔符，与COPY的DELIMITER选项相同。
+
+    - quote
+
+        指定文件的引用字符，与COPY的QUOTE选项相同。
+
+    - escape
+
+        指定文件的转义字符，与COPY的ESCAPE选项相同。
+
+    - null
+
+        指定文件的null字符串，与COPY的NULL选项相同。
+
+    - encoding
+
+        指定文件的编码，与COPY的ENCODING选项相同。
+
+    - force_not_null
+
+        这是一个布尔选项。如果为真，则声明字段的值不应该匹配空字符串（也就是， 文件级别null选项）。与COPY的 FORCE_NOT_NULL选项里的字段相同。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** file_fdw更多使用请参见[file_fdw](file_fdw)。
+
+## 相关链接
+
+[ALTER FOREIGN TABLE](6-ALTER-FOREIGN-TABLE)，[DROP FOREIGN TABLE](81-DROP-FOREIGN-TABLE)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/48-CREATE-FUNCTION.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/48-CREATE-FUNCTION.md
new file mode 100644
index 0000000000000000000000000000000000000000..a77ef2b355caaf9b56798981420cbfbede6b5967
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/48-CREATE-FUNCTION.md
@@ -0,0 +1,318 @@
+---
+title: CREATE FUNCTION
+summary: CREATE FUNCTION
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE FUNCTION
+
+## 功能描述
+
+创建一个函数。
+
+## 注意事项
+
+- 如果创建函数时参数或返回值带有精度，不进行精度检测。
+- 创建函数时，函数定义中对表对象的操作建议都显式指定模式，否则可能会导致函数执行异常。
+- 在创建函数时，函数内部通过SET语句设置current_schema和search_path无效。执行完函数search_path和current_schema与执行函数前的search_path和current_schema保持一致。
+- 如果函数参数中带有出参，SELECT调用函数必须缺省出参，CALL调用函数必须指定出参，对于调用重载的带有PACKAGE属性的函数，CALL调用函数可以缺省出参，具体信息参见[CALL](34-CALL)的示例。
+- 兼容Postgresql风格的函数或者带有PACKAGE属性的函数支持重载。在指定REPLACE的时候，如果参数个数、类型、返回值有变化，不会替换原有函数，而是会建立新的函数。
+- SELECT调用可以指定不同参数来进行同名函数调用。由于语法不支持调用不带有PACKAGE属性的同名函数。
+- 在创建function时，不能在avg函数外面嵌套其他agg函数或者其他系统函数。
+- 新创建的函数默认会给PUBLIC授予执行权限（详见[GRANT](108-GRANT)）。用户可以选择收回PUBLIC默认执行权限，然后根据需要将执行权限授予其他用户，为了避免出现新函数能被所有人访问的时间窗口，应在一个事务中创建函数并且设置函数执行权限。
+- 在函数内部调用其它无参数的函数时，可以省略括号，直接使用函数名进行调用。
+- 兼容Oracle风格的函数支持参数注释的查看与导出、导入。
+- 兼容Oracle风格的函数支持介于IS/AS与plsql_body之间的注释的查看与导出、导入。
+
+## 语法格式
+
+- 兼容PostgreSQL风格的创建自定义函数语法。
+
+  ```ebnf+diagram
+  CreateFunction ::= CREATE [ OR REPLACE  ] FUNCTION function_name
+        [ ( [  { argname [ argmode  ] argtype [  { DEFAULT  | ':='  | =  } expression  ]}  [, ...]  ] ) ]
+        [ RETURNS rettype [ DETERMINISTIC  ]  | RETURNS TABLE (  { column_name column_type  }  [, '...'] )]
+        LANGUAGE lang_name
+        [
+           {IMMUTABLE  | STABLE  | VOLATILE }
+      | {SHIPPABLE | NOT SHIPPABLE}
+            | WINDOW
+            | [ NOT  ] LEAKPROOF
+            | {CALLED ON NULL INPUT  | RETURNS NULL ON NULL INPUT | STRICT }
+            | {[ EXTERNAL  ] SECURITY INVOKER | [ EXTERNAL  ] SECURITY DEFINER | AUTHID DEFINER  | AUTHID CURRENT_USER}
+            | {fenced | not fenced}
+            | {PACKAGE}
+            | COST execution_cost
+            | ROWS result_rows
+            | SET configuration_parameter { {TO | =} value | FROM CURRENT }
+
+         ]['...']
+        {
+            AS 'definition'
+        }
+  ```
+
+- O风格的创建自定义函数的语法。
+
+  ```ebnf+diagram
+  CreateFunction ::= CREATE [ OR REPLACE  ] FUNCTION function_name
+        ( [  { argname [ argmode  ] argtype [  { DEFAULT | ':=' | =  } expression  ] }  [, '...']  ] )
+        RETURN rettype [ DETERMINISTIC  ]
+
+  [
+
+            {IMMUTABLE  | STABLE  | VOLATILE }
+            | {SHIPPABLE | NOT SHIPPABLE}
+            | {PACKAGE}
+            | {FENCED | NOT FENCED}
+            | [ NOT  ] LEAKPROOF
+            | {CALLED ON NULL INPUT | RETURNS NULL ON NULL INPUT | STRICT }
+            | {[ EXTERNAL  ] SECURITY INVOKER  | [ EXTERNAL  ] SECURITY DEFINER |
+    AUTHID DEFINER | AUTHID CURRENT_USER
+    }
+
+            |{ COST execution_cost  }
+            | ROWS result_rows
+            | SET configuration_parameter { {TO | =} value
+            | FROM CURRENT}
+
+        ]
+
+  ['...']
+
+        {
+          IS  | AS
+    } plsql_body
+  ```
+
+## 参数说明
+
+- **function_name**
+
+  要创建的函数名称（可以用模式修饰）。
+
+  取值范围: 字符串，要符合标识符的命名规范。且最多为63个字符。若超过63个字符，数据库会截断并保留前63个字符当做函数名称。
+
+- **argname**
+
+  函数参数的名称。
+
+  取值范围: 字符串，要符合标识符的命名规范。且最多为63个字符。若超过63个字符，数据库会截断并保留前63个字符当做函数参数名称。
+
+- **argmode**
+
+  函数参数的模式。
+
+  取值范围: IN、OUT、INOUT或VARIADIC。缺省值是IN。并且OUT和INOUT模式的参数不能用在RETURNS TABLE的函数定义中。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** VARIADIC用于声明数组类型的参数。
+
+- **argtype**
+
+  函数参数的类型。可以使用%TYPE或%ROWTYPE间接引用变量或表的类型，详细可参考存储过程章节[定义变量](1-6-basic-statements)。
+
+- **expression**
+
+  参数的默认表达式。
+
+- **rettype**
+
+  函数返回值的数据类型。
+
+  如果存在OUT或INOUT参数，可以省略RETURNS子句。如果存在，该子句必须和输出参数所表示的结果类型一致：如果有多个输出参数，则为RECORD，否则与单个输出参数的类型相同。
+
+  SETOF修饰词表示该函数将返回一个集合，而不是单独一项。
+
+  与argtype相同，同样可以使用%TYPE或%ROWTYPE间接引用类型。
+
+- **column_name**
+
+  字段名称。
+
+- **column_type**
+
+  字段类型。
+
+- **definition**
+
+  一个定义函数的字符串常量，含义取决于语言。它可以是一个内部函数名称、一个指向某个目标文件的路径、一个SQL查询、一个过程语言文本。
+
+- **DETERMINISTIC**
+
+  SQL语法兼容接口，未实现功能，不推荐使用。
+
+- **LANGUAGE lang_name**
+
+  用以实现函数的语言的名称。可以是SQL、internal或者是用户定义的过程语言名称。为了保证向下兼容，该名称可以用单引号（包围）。若采用单引号，则引号内必须为大写。
+
+- **WINDOW**
+
+  表示该函数是窗口函数。替换函数定义时不能改变WINDOW属性。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 自定义窗口函数只支持LANGUAGE是internal，并且引用的内部函数必须是窗口函数。
+
+- **IMMUTABLE**
+
+  表示该函数在给出同样的参数值时总是返回同样的结果。
+
+- **STABLE**
+
+  表示该函数不能修改数据库，对相同参数值，在同一次表扫描里，该函数的返回值不变，但是返回值可能在不同SQL语句之间变化。
+
+- **VOLATILE**
+
+  表示该函数值可以在一次表扫描内改变，因此不会做任何优化。
+
+- **SHIPPABLE**|**NOT SHIPPABLE**
+
+  表示该函数是否可以下推执行。预留接口，不推荐使用。
+
+- **FENCED**|**NOT FENCED**
+
+  声明用户定义的C函数是在保护模式还是非保护模式下执行。预留接口，不推荐使用。
+
+- **PACKAGE**
+
+  表示该函数是否支持重载。PostgreSQL风格的函数本身就支持重载，此参数主要是针对其它风格的函数。
+
+  - 不允许package函数和非package函数重载或者替换。
+  - package函数不支持VARIADIC类型的参数。
+  - 不允许修改函数的package属性。
+
+- **LEAKPROOF**
+
+  指出该函数的参数只包括返回值。LEAKPROOF只能由系统管理员设置。
+
+- **CALLED ON NULL INPUT**
+
+  表明该函数的某些参数是NULL的时候可以按照正常的方式调用。该参数可以省略。
+
+- **RETURNS NULL ON NULL INPUT**
+
+  **STRICT**
+
+  STRICT用于指定如果函数的某个参数是NULL，此函数总是返回NULL。如果声明了这个参数，当有NULL值参数时该函数不会被执行；而只是自动返回一个NULL结果。
+
+  RETURNS NULL ON NULL INPUT和STRICT的功能相同。
+
+- **EXTERNAL**
+
+  目的是和SQL兼容，是可选的，这个特性适合于所有函数，而不仅是外部函数。
+
+- **SECURITY INVOKER**
+
+  **AUTHID CURRENT_USER**
+
+  表明该函数将带着调用它的用户的权限执行。该参数可以省略。
+
+  SECURITY INVOKER和AUTHID CURRENT_USER的功能相同。
+
+- **SECURITY DEFINER**
+
+  **AUTHID DEFINER**
+
+  声明该函数将以创建它的用户的权限执行。
+
+  AUTHID DEFINER和SECURITY DEFINER的功能相同。
+
+- **COST execution_cost**
+
+  用来估计函数的执行成本。
+
+  execution_cost以cpu_operator_cost为单位。
+
+  取值范围: 正数
+
+- **ROWS result_rows**
+
+  估计函数返回的行数。用于函数返回的是一个集合。
+
+  取值范围: 正数，默认值是1000行。
+
+- **configuration_parameter**
+
+  - **value**
+
+    把指定的数据库会话参数值设置为给定的值。如果value是DEFAULT或者RESET，则在新的会话中使用系统的缺省设置。OFF关闭设置。
+
+    取值范围: 字符串
+
+    - DEFAULT
+    - OFF
+    - RESET
+
+    指定默认值。
+
+  - **from current**
+
+    取当前会话中的值设置为configuration_parameter的值。
+
+- **plsql_body**
+
+  PL/SQL存储过程体。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 当在函数体中创建用户时，日志中会记录密码的明文。因此不建议用户在函数体中创建用户。
+
+## 示例
+
+```sql
+--定义函数为SQL查询。
+mogdb=# CREATE FUNCTION func_add_sql(integer, integer) RETURNS integer
+    AS 'select $1 + $2;'
+    LANGUAGE SQL
+    IMMUTABLE
+    RETURNS NULL ON NULL INPUT;
+
+--利用参数名用 PL/pgSQL 自增一个整数。
+mogdb=# CREATE OR REPLACE FUNCTION func_increment_plsql(i integer) RETURNS integer AS $$
+        BEGIN
+                RETURN i + 1;
+        END;
+$$ LANGUAGE plpgsql;
+
+--返回RECORD类型
+mogdb=# CREATE OR REPLACE FUNCTION func_increment_sql(i int, out result_1 bigint, out result_2 bigint)
+returns SETOF RECORD
+as $$
+begin
+    result_1 = i + 1;
+    result_2 = i * 10;
+return next;
+end;
+$$language plpgsql;
+
+--返回一个包含多个输出参数的记录。
+mogdb=# CREATE FUNCTION func_dup_sql(in int, out f1 int, out f2 text)
+    AS $$ SELECT $1, CAST($1 AS text) || ' is text' $$
+    LANGUAGE SQL;
+
+mogdb=# SELECT * FROM func_dup_sql(42);
+
+--计算两个整数的和，并返回结果。如果输入为null，则返回null。
+mogdb=# CREATE FUNCTION func_add_sql2(num1 integer, num2 integer) RETURN integer
+AS
+BEGIN
+RETURN num1 + num2;
+END;
+/
+--修改函数func_add_sql2的执行规则为IMMUTABLE，即参数不变时返回相同结果。
+mogdb=# ALTER FUNCTION func_add_sql2(INTEGER, INTEGER) IMMUTABLE;
+
+--将函数func_add_sql2的名称修改为add_two_number。
+mogdb=# ALTER FUNCTION func_add_sql2(INTEGER, INTEGER) RENAME TO add_two_number;
+
+--将函数add_two_number的属者改为omm。
+mogdb=# ALTER FUNCTION add_two_number(INTEGER, INTEGER) OWNER TO omm;
+
+--删除函数。
+mogdb=# DROP FUNCTION add_two_number;
+mogdb=# DROP FUNCTION func_increment_sql;
+mogdb=# DROP FUNCTION func_dup_sql;
+mogdb=# DROP FUNCTION func_increment_plsql;
+mogdb=# DROP FUNCTION func_add_sql;
+```
+
+## 相关链接
+
+[ALTER FUNCTION](7-ALTER-FUNCTION)，[DROP FUNCTION](82-DROP-FUNCTION)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/49-CREATE-GROUP.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/49-CREATE-GROUP.md
new file mode 100644
index 0000000000000000000000000000000000000000..6dc998a61a8432075ea31275aa25da77395360bb
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/49-CREATE-GROUP.md
@@ -0,0 +1,62 @@
+---
+title: CREATE GROUP
+summary: CREATE GROUP
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE GROUP
+
+## 功能描述
+
+创建一个新用户组。
+
+## 注意事项
+
+CREATE GROUP是CREATE ROLE的别名，非SQL标准语法，不推荐使用，建议用户直接使用CREATE ROLE替代。
+
+## 语法格式
+
+```ebnf+diagram
+CreateGroup ::= CREATE GROUP group_name [ [ WITH ] option [ ... ] ] [ ENCRYPTED | UNENCRYPTED ] { PASSWORD | IDENTIFIED BY } { 'password' [EXPIRED] | DISABLE };
+```
+
+其中可选项option子句语法为：
+
+```ebnf+diagram
+option ::= {SYSADMIN | NOSYSADMIN}
+    | {AUDITADMIN | NOAUDITADMIN}
+    | {CREATEDB | NOCREATEDB}
+    | {USEFT | NOUSEFT}
+    | {CREATEROLE | NOCREATEROLE}
+    | {INHERIT | NOINHERIT}
+    | {LOGIN | NOLOGIN}
+    | {REPLICATION | NOREPLICATION}
+    | {INDEPENDENT | NOINDEPENDENT}
+    | {VCADMIN | NOVCADMIN}
+    | CONNECTION LIMIT connlimit
+    | VALID BEGIN 'timestamp'
+    | VALID UNTIL 'timestamp'
+    | RESOURCE POOL 'respool'
+    | PERM SPACE 'spacelimit'
+    | TEMP SPACE 'tmpspacelimit'
+    | SPILL SPACE 'spillspacelimit'
+    | IN ROLE role_name [, ...]
+    | IN GROUP role_name [, ...]
+    | ROLE role_name [, ...]
+    | ADMIN rol e_name [, ...]
+    | USER role_name [, ...]
+    | SYSID uid
+    | DEFAULT TABLESPACE tablespace_name
+    | PROFILE DEFAULT
+    | PROFILE profile_name
+    | PGUSER
+```
+
+## 参数说明
+
+请参考[CREATE ROLE](54-CREATE-ROLE)的参数说明。
+
+## 相关链接
+
+[ALTER GROUP](8-ALTER-GROUP),  [DROP GROUP](83-DROP-GROUP), and  [CREATE ROLE](54-CREATE-ROLE)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/49.1-CREATE-INCREMENTAL-MATERIALIZED-VIEW.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/49.1-CREATE-INCREMENTAL-MATERIALIZED-VIEW.md
new file mode 100644
index 0000000000000000000000000000000000000000..0be8ab20a36a8cb9a7f4395b6d0b4a86aab4bbf0
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/49.1-CREATE-INCREMENTAL-MATERIALIZED-VIEW.md
@@ -0,0 +1,71 @@
+---
+title: CREATE INCREMENTAL MATERIALIZED VIEW
+summary: CREATE INCREMENTAL MATERIALIZED VIEW
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# CREATE INCREMENTAL MATERIALIZED VIEW
+
+## 功能描述
+
+CREATE INCREMENTAL MATERIALIZED VIEW会创建一个增量物化视图，并且后续可以使用REFRESH MATERIALIZED VIEW（全量刷新）和REFRESH INCREMENTAL MATERIALIZED VIEW（增量刷新）刷新物化视图的数据。
+
+CREATE INCREMENTAL MATERIALIZED VIEW类似于CREATE TABLE AS，不过它会记住被用来初始化该视图的查询， 因此它可以在后续中进行数据刷新。一个物化视图有很多和表相同的属性，但是不支持临时物化视图。
+
+## 注意事项
+
+- 增量物化视图不可以在临时表或全局临时表上创建。
+- 增量物化视图仅支持简单过滤查询和基表UNION ALL查询。
+- 创建增量物化视图不可指定分布列。
+- 创建增量物化视图后，基表中的绝大多数DDL操作不再支持。
+- 不支持对增量物化视图进行IUD操作。
+- 增量物化视图创建后，当基表数据发生变化时，需要使用刷新（REFRESH）命令保持物化视图与基表同步。
+
+## 语法格式
+
+```ebnf+diagram
+CreateIncrementalMaterializedView ::= CREATE INCREMENTAL MATERIALIZED VIEW mv_name
+    [ (column_name [, ...] ) ]
+    [ TABLESPACE tablespace_name ]
+    AS query;
+```
+
+## 参数说明
+
+- **mv_name**
+
+  要创建的物化视图的名称（可以被模式限定）。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- **column_name**
+
+  新物化视图中的一个列名。物化视图支持指定列，指定列需要和后面的查询语句结果的列数量保持一致；如果没有提供列名，会从查询的输出列名中获取列名。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- **TABLESPACE tablespace_name**
+
+  指定新建物化视图所属表空间。如果没有声明，将使用默认表空间。
+
+- **AS query**
+
+  一个SELECT、TABLE 或者VALUES命令。这个查询将在一个安全受限的操作中运行。
+
+## 示例
+
+```sql
+--创建一个普通表
+mogdb=# CREATE TABLE my_table (c1 int, c2 int);
+--创建增量物化视图
+mogdb=# CREATE INCREMENTAL MATERIALIZED VIEW my_imv AS SELECT * FROM my_table;
+--基表写入数据
+mogdb=# INSERT INTO my_table VALUES(1,1),(2,2);
+--对增量物化视图my_imv进行增量刷新
+mogdb=# REFRESH INCREMENTAL MATERIALIZED VIEW my_imv;
+```
+
+## 相关链接
+
+[ALTER MATERIALIZED VIEW](11-ALTER-MATERIALIZED-VIEW)，  [CREATE MATERIALIZED VIEW](51-CREATE-MATERIALIZED-VIEW)，[CREATE TABLE](60-CREATE-TABLE)，  [DROP MATERIALIZED VIEW](85-DROP-MATERIALIZED-VIEW)，[REFRESH INCREMENTAL MATERIALIZED VIEW](115.1-REFRESH-INCREMENTAL-MATERIALIZED-VIEW)  ，[REFRESH MATERIALIZED VIEW](116-REFRESH-MATERIALIZED-VIEW)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/5-ALTER-DIRECTORY.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/5-ALTER-DIRECTORY.md
new file mode 100644
index 0000000000000000000000000000000000000000..e2f629ab80417bc0793db2e4450e7b1b5447cdcf
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/5-ALTER-DIRECTORY.md
@@ -0,0 +1,47 @@
+---
+title: ALTER DIRECTORY
+summary: ALTER DIRECTORY
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER DIRECTORY
+
+## 功能描述
+
+对directory属性进行修改。
+
+## 注意事项
+
+- 目前只支持修改directory属主。
+- 当enable_access_server_directory=off时，只允许初始用户修改directory属主；当enable_access_server_directory=on时，具有SYSADMIN权限的用户和directory对象的属主可以修改directory，且要求该用户是新属主的成员。
+
+## 语法格式
+
+```ebnf+diagram
+AlterDirectory ::= ALTER DIRECTORY directory_name
+    OWNER TO new_owner;
+```
+
+## 参数描述
+
+**directory_name**
+
+需要修改的目录名称，范围为已经存在的目录名称。
+
+## 示例
+
+```sql
+--创建目录。
+mogdb=# CREATE OR REPLACE DIRECTORY  dir  as '/tmp/';
+
+--修改目录的owner。
+mogdb=# ALTER DIRECTORY dir OWNER TO system;
+
+--删除目录。
+mogdb=# DROP DIRECTORY dir;
+```
+
+## 相关链接
+
+[CREATE DIRECTORY](46-CREATE-DIRECTORY)，[DROP DIRECTORY](80-DROP-DIRECTORY)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/5.1-ALTER-EXTENSION.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/5.1-ALTER-EXTENSION.md
new file mode 100644
index 0000000000000000000000000000000000000000..1360d9d76b83668250f2e63853deeb10a1407adf
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/5.1-ALTER-EXTENSION.md
@@ -0,0 +1,155 @@
+---
+title: ALTER EXTENSION
+summary: ALTER EXTENSION
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# ALTER EXTENSION
+
+## 功能描述
+
+修改插件扩展。
+
+## 注意事项
+
+ALTER EXTENSION 修改一个已安装的扩展的定义。这里有几种方式：
+
+- UPDATE
+
+  这种方式更新这个扩展到一个新的版本。这个扩展必须满足一个适用的更新脚本（或者一系列脚本） 这样就能修改当前安装版本到一个要求的版本。
+
+- SET SCHEMA
+
+  这种方式移动扩展对象到另一个模式。这个扩展必须relocatable才能使命令成功。
+
+- ADD member_object
+
+  这种方式添加一个已存在对象到扩展。这主要在扩展更新脚本上有用。这个对象接着会被视为扩展的成员；显而易见,该对象只能通过取消扩展来取消。
+
+- DROP member_object
+
+  这个方式从扩展上移除一个成员对象。主要在扩展更新脚本上有用。这个对象没有被取消，只是从扩展里分开了。
+
+  你必须拥有扩展来使用 ALTER EXTENSION。这个 ADD/DROP 方式要求 添加/删除对象的所有权。
+
+## 语法格式
+
+```ebnf+diagram
+AlterExtension ::= ALTER EXTENSION name UPDATE [ TO new_version ];
+```
+
+```ebnf+diagram
+AlterExtension ::= ALTER EXTENSION name SET SCHEMA new_schema;
+```
+
+```ebnf+diagram
+AlterExtension ::= ALTER EXTENSION name ADD member_object;
+```
+
+```ebnf+diagram
+AlterExtension ::= ALTER EXTENSION name DROP member_object;
+```
+
+其中member_object为：
+
+```ebnf+diagram
+member_object ::= AGGREGATE agg_name (agg_type [, ...] ) |
+  CAST (source_type AS target_type) |
+  COLLATION object_name |
+  CONVERSION object_name |
+  DOMAIN object_name |
+  EVENT TRIGGER object_name |
+  FOREIGN DATA WRAPPER object_name |
+  FOREIGN TABLE object_name |
+  FUNCTION function_name ( [ [ argmode ] [ argname ] argtype [, ...] ] ) |
+  MATERIALIZED VIEW object_name |
+  OPERATOR operator_name (left_type, right_type) |
+  OPERATOR CLASS object_name USING index_method |
+  OPERATOR FAMILY object_name USING index_method |
+  [ PROCEDURAL ] LANGUAGE object_name |
+  SCHEMA object_name |
+  SEQUENCE object_name |
+  SERVER object_name |
+  TABLE object_name |
+  TEXT SEARCH CONFIGURATION object_name |
+  TEXT SEARCH DICTIONARY object_name |
+  TEXT SEARCH PARSER object_name |
+  TEXT SEARCH TEMPLATE object_name |
+  TYPE object_name |
+  VIEW object_name
+```
+
+## 参数说明
+
+- **name**
+
+  已安装扩展的名称。
+
+- **new_version**
+
+  扩展的新版本。可以通过被标识符和字面字符重写。如果不指定的扩展的新版本，ALTER EXTENSION UPDATE会更新到扩展的控制文件中显示的默认版本。
+
+- **new_schema**
+
+  扩展的新模式。
+
+- **object_name**
+
+  **agg_name**
+
+  **function_name**
+
+  **operator_name**
+
+  从扩展里被被添加或移除的对象的名称。包含表、聚合 、域、外链表、函数、操作符、操作符类、操作符族、序列、文本搜索对象、类型和能被模式合格的视图的名称。
+
+- **agg_type**
+
+  在聚合函数操作上的一个输入数据类型，去引用一个零参数聚合函数，写 \* 代替这些输入数据类型列表。
+
+- **source_type**
+
+  强制转换的源数据类型的名称。
+
+- **target_type**
+
+  强制转换的目标数据类型的名称。
+
+- **argmode**
+
+  这个函数参数的模型：IN、OUT、INOUT或者VARIADIC。如果省略的话，默认值为IN。ALTER EXTENSION 不关心OUT参数 ，因为确认函数的一致性只需要输入参数，因此列出IN、INOUT和VARIADIC参数就足够了。
+
+- **argname**
+
+  函数参数的名称。注意ALTER EXTENSION不关心参数名称，因为确认函数的一致性只需要参数数据类型。
+
+- **argtype**
+
+  函数参数的数据类型（可以有模式修饰）。
+
+- **left_type**
+
+  **right_type**
+
+  操作符的参数的数据类型（可以有模式修饰）。为前缀或后缀运算符的丢失参数写NONE。
+
+## 示例
+
+更新 hstore 扩展到版本 2.0：
+
+```sql
+ALTER EXTENSION hstore UPDATE TO '2.0';
+```
+
+更新 hstore扩展的模式为utils：
+
+```sql
+ALTER EXTENSION hstore SET SCHEMA utils;
+```
+
+添加一个已存在的函数给 hstore 扩展：
+
+```sql
+ALTER EXTENSION hstore ADD FUNCTION populate_record(anyelement, hstore);
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/50-CREATE-INDEX.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/50-CREATE-INDEX.md
new file mode 100644
index 0000000000000000000000000000000000000000..b8ea672454a33c92f52279fed59ba1e820e22ae5
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/50-CREATE-INDEX.md
@@ -0,0 +1,356 @@
+---
+title: CREATE INDEX
+summary: CREATE INDEX
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE INDEX
+
+## 功能描述
+
+在指定的表上创建索引。
+
+索引可以用来提高数据库查询性能，但是不恰当的使用将导致数据库性能下降。建议仅在匹配如下某条原则时创建索引：
+
+- 经常执行查询的字段。
+- 在连接条件上创建索引，对于存在多字段连接的查询，建议在这些字段上建立组合索引。例如，select * from t1 join t2 on t1.a=t2.a and t1.b=t2.b，可以在t1表上的a，b字段上建立组合索引。
+- where子句的过滤条件字段上（尤其是范围条件）。
+- 在经常出现在order by、group by和distinct后的字段。
+
+在分区表上创建索引与在普通表上创建索引的语法不太一样，使用时请注意，如分区表上不支持并行创建索引、不支持创建部分索引。
+
+## 注意事项
+
+- 索引自身也占用存储空间、消耗计算资源，创建过多的索引将对数据库性能造成负面影响（尤其影响数据导入的性能，建议在数据导入后再建索引）。因此，仅在必要时创建索引。
+- 索引定义里的所有函数和操作符都必须是immutable类型的，即它们的结果必须只能依赖于它们的输入参数，而不受任何外部的影响（如另外一个表的内容或者当前时间）。这个限制可以确保该索引的行为是定义良好的。要在一个索引上或WHERE中使用用户定义函数，请把它标记为immutable类型函数。
+- 分区表索引分为LOCAL索引与GLOBAL索引，LOCAL索引与某个具体分区绑定，而GLOBAL索引则对应整个分区表。
+- 列存表支持的PSORT和B-tree索引都不支持创建表达式索引、部分索引，PSORT不支持创建唯一索引，B-tree支持创建唯一索引。
+- 列存表支持的GIN索引支持创建表达式索引，但表达式不能包含空分词、空列和多列，不支持创建部分索引和唯一索引。
+- HASH索引目前仅限于行存表索引、临时表索引和分区表LOCAL索引，且不支持创建多字段索引。
+
+## 语法格式
+
+- 在表上创建索引。
+
+  ```ebnf+diagram
+  CreateIndex ::= CREATE [ UNIQUE ] INDEX [ CONCURRENTLY ] [ [schema_name'.']index_name ] ON table_name [ USING method ]
+        ({ { column_name | ( expression ) } [ COLLATE collation ] [ opclass ] [ ASC | DESC ] [ NULLS { FIRST | LAST } ] }[, ...] )
+        [ WITH ( {storage_parameter = value} [, ... ] ) ]
+        [ TABLESPACE tablespace_name ]
+        [ WHERE predicate ];
+  ```
+
+- 在分区表上创建索引。
+
+  ```ebnf+diagram
+  CreateIndex ::= CREATE [ UNIQUE ] INDEX [ [schema_name'.']index_name ] ON table_name [ USING method ]
+      ( {{ column_name | ( expression ) } [ COLLATE collation ] [ opclass ] [ ASC | DESC ] [ NULLS LAST ] }[, ...] )
+      [ LOCAL [ ( { PARTITION index_partition_name [ TABLESPACE index_partition_tablespace ] } [, ...] ) ] | GLOBAL ]
+      [ WITH ( { storage_parameter = value } [, ...] ) ]
+      [ TABLESPACE tablespace_name ];
+  ```
+
+## 参数说明
+
+- **UNIQUE**
+
+  创建唯一性索引，每次添加数据时检测表中是否有重复值。如果插入或更新的值会引起重复的记录时，将导致一个错误。
+
+  目前只有B-tree索引支持唯一索引。
+
+- **CONCURRENTLY** <a id = 'CONCURRENTLY'> </a>
+
+  以不阻塞DML的方式创建索引（加ShareUpdateExclusiveLock锁）。创建索引时，一般会阻塞其他语句对该索引所依赖表的访问。指定此关键字，可以实现创建过程中不阻塞DML。
+
+  - 此选项只能指定一个索引的名称。
+  - 普通CREATE INDEX命令可以在事务内执行，但是CREATE INDEX CONCURRENTLY不可以在事务内执行。
+  - 列存表、分区表和临时表不支持CONCURRENTLY方式创建索引。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  >
+  > - 创建索引时指定此关键字，需要执行先后两次对该表的全表扫描来完成build，第一次扫描的时候创建索引，不阻塞读写操作；第二次扫描的时候合并更新第一次扫描到目前为止发生的变更。
+  > - 由于需要执行两次对表的扫描和build，而且必须等待现有的所有可能对该表执行修改的事务结束。这意味着该索引的创建比正常耗时更长，同时因此带来的CPU和I/O消耗对其他业务也会造成影响。
+  > - 如果在索引构建时发生失败，那会留下一个“不可用”的索引。这个索引会被查询忽略，但它仍消耗更新开销。这种情况推荐的恢复方法是删除该索引并尝试再次CONCURRENTLY建索引。
+  > - 由于在第二次扫描之后，索引构建必须等待任何持有早于第二次扫描拿的快照的事务终止，而且建索引时加的ShareUpdateExclusiveLock锁（4级）会和大于等于4级的锁冲突，在创建这类索引时，容易引发卡住（hang）或者死锁问题。例如：
+  >   - 两个会话对同一个表创建CONCURRENTLY索引，会引起死锁问题；
+  >   - 两个会话，一个对表创建CONCURRENTLY索引，一个drop table，会引起死锁问题；
+  >   - 三个会话，会话1先对表a加锁，不提交，会话2接着对表b创建CONCURRENTLY索引，会话3接着对表a执行写入操作，在会话1事务未提交之前，会话2会一直被阻塞；
+  >   - 将事务隔离级别设置成可重复读（默认为读已提交），起两个会话，会话1起事务对表a执行写入操作，不提交，会话2对表b创建CONCURRENTLY索引，在会话1事务未提交之前，会话2会一直被阻塞。
+
+- **schema_name**
+
+  模式的名称。
+
+  取值范围: 已存在模式名。
+
+- **index_name**
+
+  要创建的索引名，索引的模式与表相同。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- **table_name**
+
+  需要为其创建索引的表的名称，可以用模式修饰。
+
+  取值范围: 已存在的表名。
+
+- **USING method**
+
+  指定创建索引的方法。
+
+  取值范围:
+
+  - btree：B-tree索引使用一种类似于B+树的结构来存储数据的键值，通过这种结构能够快速的查找索引。btree适合支持比较查询以及查询范围。
+  - hash：Hash索引使用Hash函数对索引的关键字进行散列。只能处理简单等值比较，比较适合在索引值较长的情况下使用。
+  - gin：GIN索引是倒排索引，可以处理包含多个键的值（比如数组）。
+  - gist：Gist索引适用于几何和地理等多维数据类型和集合数据类型。目前支持的数据类型有box、point、poly、circle、tsvector、tsquery、range。
+  - Psort：Psort索引。针对列存表进行局部排序索引。
+  - ubtree：仅供ustore表使用的多版本B-tree索引，索引页面上包含事务信息，能并自主回收页面。
+
+  行存表（ASTORE存储引擎）支持的索引类型：btree（行存表缺省值）、hash、gin、gist。行存表（USTORE存储引擎）支持的索引类型：ubtree。列存表支持的索引类型：Psort（列存表缺省值）、btree、gin。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 列存表对GIN索引支持仅限于对于tsvector类型的支持，即创建列存GIN索引入参需要为to_tsvector函数（的返回值）。此方法为GIN索引比较普遍的使用方式。
+
+- **column_name**
+
+  表中需要创建索引的列的名称（字段名）。
+
+  如果索引方式支持多字段索引，可以声明多个字段。全局索引最多可以声明31个字段，其他索引最多可以声明32个字段。
+
+- **expression**
+
+  创建一个基于该表的一个或多个字段的表达式索引，通常必须写在圆括弧中。如果表达式有函数调用的形式，圆括弧可以省略。
+
+  表达式索引可用于获取对基本数据的某种变形的快速访问。比如，一个在upper(col)上的函数索引将允许WHERE upper(col) = 'JIM'子句使用索引。
+
+  在创建表达式索引时，如果表达式中包含IS NULL子句，则这种索引是无效的。此时，建议用户尝试创建一个部分索引。
+
+- **COLLATE collation**
+
+  COLLATE子句指定列的排序规则（该列必须是可排列的数据类型）。如果没有指定，则使用默认的排序规则。排序规则可以使用“select \* from pg_collation”命令从pg_collation系统表中查询，默认的排序规则为查询结果中以default开始的行。
+
+- **opclass**
+
+  操作符类的名称。对于索引的每一列可以指定一个操作符类，操作符类标识了索引那一列的使用的操作符。例如一个B-tree索引在一个四字节整数上可以使用int4_ops；这个操作符类包括四字节整数的比较函数。实际上对于列上的数据类型默认的操作符类是足够用的。操作符类主要用于一些有多种排序的数据。例如，用户想按照绝对值或者实数部分排序一个复数。能通过定义两个操作符类然后当建立索引时选择合适的类。
+
+- **ASC**
+
+  指定按升序排序 （默认）。
+
+- **DESC**
+
+  指定按降序排序。
+
+- **NULLS FIRST**
+
+  指定空值在排序中排在非空值之前，当指定DESC排序时，本选项为默认的。
+
+- **NULLS LAST**
+
+  指定空值在排序中排在非空值之后，未指定DESC排序时，本选项为默认的。
+
+- **LOCAL**
+
+  指定创建的分区索引为LOCAL索引。
+
+- **GLOBAL**
+
+  指定创建的分区索引为GLOBAL索引，当不指定LOCAL、GLOBAL关键字时，默认创建GLOBAL索引。
+
+- **WITH ( {storage_parameter = value} [, … ] )**
+
+  指定索引方法的存储参数。
+
+  取值范围:
+
+  只有GIN索引支持FASTUPDATE，GIN_PENDING_LIST_LIMIT参数。GIN和Psort之外的索引都支持FILLFACTOR参数。
+
+  - FILLFACTOR
+
+    一个索引的填充因子（fillfactor）是一个介于10和100之间的百分数。
+
+    取值范围: 10~100
+
+  - FASTUPDATE
+
+    GIN索引是否使用快速更新。
+
+    取值范围: ON，OFF
+
+    默认值：ON
+
+  - GIN_PENDING_LIST_LIMIT
+
+    当GIN索引启用fastupdate时，设置该索引pending list容量的最大值。
+
+    取值范围: 64~INT_MAX，单位KB。
+
+    默认值：gin_pending_list_limit的默认取决于GUC中gin_pending_list_limit的值（默认为4MB）
+
+- **TABLESPACE tablespace_name**
+
+  指定索引的表空间，如果没有声明则使用默认的表空间。
+
+  取值范围: 已存在的表空间名。
+
+- **WHERE predicate**
+
+  创建一个部分索引。部分索引是一个只包含表的一部分记录的索引，通常是该表中比其他部分数据更有用的部分。例如，有一个表，表里包含已记账和未记账的定单，未记账的定单只占表的一小部分而且这部分是最常用的部分，此时就可以通过只在未记账部分创建一个索引来改善性能。另外一个可能的用途是使用带有UNIQUE的WHERE强制一个表的某个子集的唯一性。
+
+  取值范围: predicate表达式只能引用表的字段，它可以使用所有字段，而不仅是被索引的字段。目前，子查询和聚集表达式不能出现在WHERE子句里。
+
+- **PARTITION index_partition_name**
+
+  索引分区的名称。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- **TABLESPACE index_partition_tablespace**
+
+  索引分区的表空间。
+
+  取值范围: 如果没有声明，将使用分区表索引的表空间index_tablespace。
+
+## 示例
+
+```sql
+--创建表tpcds.ship_mode_t1。
+mogdb=# create schema tpcds;
+mogdb=# CREATE TABLE tpcds.ship_mode_t1
+(
+    SM_SHIP_MODE_SK           INTEGER               NOT NULL,
+    SM_SHIP_MODE_ID           CHAR(16)              NOT NULL,
+    SM_TYPE                   CHAR(30)                      ,
+    SM_CODE                   CHAR(10)                      ,
+    SM_CARRIER                CHAR(20)                      ,
+    SM_CONTRACT               CHAR(20)
+)
+;
+
+--在表tpcds.ship_mode_t1上的SM_SHIP_MODE_SK字段上创建普通的唯一索引。
+mogdb=# CREATE UNIQUE INDEX ds_ship_mode_t1_index1 ON tpcds.ship_mode_t1(SM_SHIP_MODE_SK);
+
+--在表tpcds.ship_mode_t1上的SM_SHIP_MODE_SK字段上创建指定B-tree索引。
+mogdb=# CREATE INDEX ds_ship_mode_t1_index4 ON tpcds.ship_mode_t1 USING btree(SM_SHIP_MODE_SK);
+
+--在表tpcds.ship_mode_t1上SM_CODE字段上创建表达式索引。
+mogdb=# CREATE INDEX ds_ship_mode_t1_index2 ON tpcds.ship_mode_t1(SUBSTR(SM_CODE,1 ,4));
+
+--在表tpcds.ship_mode_t1上的SM_SHIP_MODE_SK字段上创建SM_SHIP_MODE_SK大于10的部分索引。
+mogdb=# CREATE UNIQUE INDEX ds_ship_mode_t1_index3 ON tpcds.ship_mode_t1(SM_SHIP_MODE_SK) WHERE SM_SHIP_MODE_SK>10;
+
+--重命名一个现有的索引。
+mogdb=# ALTER INDEX tpcds.ds_ship_mode_t1_index1 RENAME TO ds_ship_mode_t1_index5;
+
+--设置索引不可用。
+mogdb=# ALTER INDEX tpcds.ds_ship_mode_t1_index2 UNUSABLE;
+
+--重建索引。
+mogdb=# ALTER INDEX tpcds.ds_ship_mode_t1_index2 REBUILD;
+
+--删除一个现有的索引。
+mogdb=# DROP INDEX tpcds.ds_ship_mode_t1_index2;
+
+--删除表。
+mogdb=# DROP TABLE tpcds.ship_mode_t1;
+
+--创建表空间。
+mogdb=# CREATE TABLESPACE example1 RELATIVE LOCATION 'tablespace1/tablespace_1';
+mogdb=# CREATE TABLESPACE example2 RELATIVE LOCATION 'tablespace2/tablespace_2';
+mogdb=# CREATE TABLESPACE example3 RELATIVE LOCATION 'tablespace3/tablespace_3';
+mogdb=# CREATE TABLESPACE example4 RELATIVE LOCATION 'tablespace4/tablespace_4';
+--创建表tpcds.customer_address_p1。
+mogdb=# CREATE TABLE tpcds.customer_address_p1
+(
+    CA_ADDRESS_SK             INTEGER               NOT NULL,
+    CA_ADDRESS_ID             CHAR(16)              NOT NULL,
+    CA_STREET_NUMBER          CHAR(10)                      ,
+    CA_STREET_NAME            VARCHAR(60)                   ,
+    CA_STREET_TYPE            CHAR(15)                      ,
+    CA_SUITE_NUMBER           CHAR(10)                      ,
+    CA_CITY                   VARCHAR(60)                   ,
+    CA_COUNTY                 VARCHAR(30)                   ,
+    CA_STATE                  CHAR(2)                       ,
+    CA_ZIP                    CHAR(10)                      ,
+    CA_COUNTRY                VARCHAR(20)                   ,
+    CA_GMT_OFFSET             DECIMAL(5,2)                  ,
+    CA_LOCATION_TYPE          CHAR(20)
+)
+TABLESPACE example1
+PARTITION BY RANGE(CA_ADDRESS_SK)
+(
+   PARTITION p1 VALUES LESS THAN (3000),
+   PARTITION p2 VALUES LESS THAN (5000) TABLESPACE example1,
+   PARTITION p3 VALUES LESS THAN (MAXVALUE) TABLESPACE example2
+)
+ENABLE ROW MOVEMENT;
+--创建分区表索引ds_customer_address_p1_index1，不指定索引分区的名称。
+mogdb=# CREATE INDEX ds_customer_address_p1_index1 ON tpcds.customer_address_p1(CA_ADDRESS_SK) LOCAL;
+--创建分区表索引ds_customer_address_p1_index2，并指定索引分区的名称。
+mogdb=# CREATE INDEX ds_customer_address_p1_index2 ON tpcds.customer_address_p1(CA_ADDRESS_SK) LOCAL
+(
+    PARTITION CA_ADDRESS_SK_index1,
+    PARTITION CA_ADDRESS_SK_index2 TABLESPACE example3,
+    PARTITION CA_ADDRESS_SK_index3 TABLESPACE example4
+)
+TABLESPACE example2;
+
+--创建GLOBAL分区索引
+mogdb=CREATE INDEX ds_customer_address_p1_index3 ON tpcds.customer_address_p1(CA_ADDRESS_ID) GLOBAL;
+
+--不指定关键字，默认创建GLOBAL分区索引
+mogdb=CREATE INDEX ds_customer_address_p1_index4 ON tpcds.customer_address_p1(CA_ADDRESS_ID);
+
+--修改分区表索引CA_ADDRESS_SK_index2的表空间为example1。
+mogdb=# ALTER INDEX tpcds.ds_customer_address_p1_index2 MOVE PARTITION CA_ADDRESS_SK_index2 TABLESPACE example1;
+
+--修改分区表索引CA_ADDRESS_SK_index3的表空间为example2。
+mogdb=# ALTER INDEX tpcds.ds_customer_address_p1_index2 MOVE PARTITION CA_ADDRESS_SK_index3 TABLESPACE example2;
+
+--重命名分区表索引。
+mogdb=# ALTER INDEX tpcds.ds_customer_address_p1_index2 RENAME PARTITION CA_ADDRESS_SK_index1 TO CA_ADDRESS_SK_index4;
+
+--删除索引和分区表。
+mogdb=# DROP INDEX tpcds.ds_customer_address_p1_index1;
+mogdb=# DROP INDEX tpcds.ds_customer_address_p1_index2;
+mogdb=# DROP TABLE tpcds.customer_address_p1;
+--删除表空间。
+mogdb=# DROP TABLESPACE example1;
+mogdb=# DROP TABLESPACE example2;
+mogdb=# DROP TABLESPACE example3;
+mogdb=# DROP TABLESPACE example4;
+
+--创建列存表以及列存表GIN索引。
+mogdb=# create table cgin_create_test(a int, b text) with (orientation = column);
+CREATE TABLE
+mogdb=# create index cgin_test on cgin_create_test using gin(to_tsvector('ngram', b));
+CREATE INDEX
+```
+
+## 相关链接
+
+[ALTER INDEX](9-ALTER-INDEX)，[DROP INDEX](84-DROP-INDEX)
+
+## 优化建议
+
+### create index
+
+建议仅在匹配如下条件之一时创建索引：
+
+- 经常执行查询的字段。
+- 在连接条件上创建索引，对于存在多字段连接的查询，建议在这些字段上建立组合索引。例如，select * from t1 join t2 on t1.a=t2.a and t1.b=t2.b，可以在t1表上的a，b字段上建立组合索引。
+- where子句的过滤条件字段上（尤其是范围条件）。
+- 在经常出现在order by、group by和distinct后的字段。
+
+约束限制：
+
+- 分区表上不支持创建部分索引。
+- 分区表创建GLOBAL索引时，存在以下约束条件：
+  - 不支持表达式索引、部分索引
+  - 不支持列存表
+  - 仅支持B-tree索引
+- 在相同属性列上，分区LOCAL索引与GLOBAL索引不能共存。
+- GLOBAL索引，最大支持31列。
+- 如果alter语句不带有UPDATE GLOBAL INDEX，那么原有的GLOBAL索引将失效，查询时将使用其他索引进行查询；如果alter语句带有UPDATE GLOBAL INDEX，原有的GLOBAL索引仍然有效，并且索引功能正确。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/50.1-CREATE-LANGUAGE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/50.1-CREATE-LANGUAGE.md
new file mode 100644
index 0000000000000000000000000000000000000000..3f7a56e0a7f92b8ede14ac277ead854d4ad4ed6d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/50.1-CREATE-LANGUAGE.md
@@ -0,0 +1,71 @@
+---
+title: CREATE LANGUAGE
+summary: CREATE LANGUAGE
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# CREATE LANGUAGE
+
+## 功能描述
+
+定义一种新的过程语言。单机和集中式暂不支持创建过程语言。
+
+## 语法格式
+
+```ebnf+diagram
+CreateLanguage ::= CREATE [ OR REPLACE ] [ PROCEDURAL ] LANGUAGE name;
+```
+
+```ebnf+diagram
+CreateLanguage ::= CREATE [ OR REPLACE ] [ TRUSTED ] [ PROCEDURAL ] LANGUAGE name
+    HANDLER call_handler [ INLINE inline_handler ] [ VALIDATOR valfunction ];
+```
+
+## 参数说明
+
+- **TRUSTED**
+
+  TRUSTED说明该语言并不授权没有权限的用户访问数据。 如果在注册该语言时忽略这个关键字，则只有超级用户权限可以使用。
+
+- **PROCEDURAL**
+
+  这是个没有用的字。
+
+- **name**
+
+  新过程语言的名称。这个名字应该在数据库的所有语言中唯一。
+
+  出于向下兼容的原因，这个名字可以用单引号包围。
+
+- **HANDLER call_handler**
+
+  call_handler是一个以前注册过的函数名字， 该函数将被用来执行该过程语言的函数。过程语言的调用处理器必须用一种编译语言(比如 C) 书写，调用风格必须是版本1的调用风格，并且注册为不接受参数并且返回 language_handler类型的函数。language_handler 是用于将函数声明为调用处理器的占位符。
+
+- **INLINE inline_handler**
+
+  inline_handler是以前注册过的函数名字， 用来在该语言中执行一个匿名代码块(DO 命令)。 如果没有指定inline_handler函数， 那么该语言不支持匿名代码块。处理器函数必须接受一个internal 类型的参数，这将是DO命令的内部表示，并且它通常返回void。 忽略该处理器的返回值。
+
+- **VALIDATOR valfunction**
+
+  valfunction是一个以前注册过的函数名字， 在用该语言创建新函数的时候将用它来校验新函数。如果没有声明校验函数， 那么建立新函数的时候就不会检查它。校验函数必须接受一个类型为oid的参数， 它是将要创建的函数的 OID ，并且通常会返回void。
+
+  校验函数通常会检查函数体，看看有没有语法错误，但是它也可以查看函数的其它属性， 比如该语言是否不能处理某种参数类型。校验函数应该用ereport() 函数报告错误。该函数的返回值将被忽略。
+
+## 示例
+
+创建标准的过程语言的比较好的方法：
+
+```sql
+CREATE LANGUAGE plperl;
+```
+
+对于pg_pltemplate还不知道的语言，需要下面这样的序列：
+
+```sql
+CREATE FUNCTION plsample_call_handler() RETURNS language_handler
+    AS '$libdir/plsample'
+    LANGUAGE C;
+CREATE LANGUAGE plsample
+    HANDLER plsample_call_handler;
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/50.2-CREATE-MASKING-POLICY.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/50.2-CREATE-MASKING-POLICY.md
new file mode 100644
index 0000000000000000000000000000000000000000..01f61d3a9de1ba0a606ebec683b9ce34a80455a0
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/50.2-CREATE-MASKING-POLICY.md
@@ -0,0 +1,111 @@
+---
+title: CREATE MASKING POLICY
+summary: CREATE MASKING POLICY
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# CREATE MASKING POLICY
+
+## 功能描述
+
+创建脱敏策略。
+
+## 注意事项
+
+只有poladmin、sysadmin或初始用户能执行此操作。
+
+需要开启安全策略开关，即设置GUC参数enable_security_policy=on，脱敏策略才可以生效。具体设置请参考《安全加固指南》中“数据库配置&gt;数据库安全管理策略&gt;数据动态脱敏”章节。
+
+## 语法格式
+
+```ebnf+diagram
+CreateMaskingPolicy ::= CREATE MASKING POLICY policy_name masking_clause[, ...]* policy_filter [ENABLE | DISABLE];
+```
+
+- masking_clause：
+
+  ```ebnf+diagram
+  masking_clause ::= masking_function ON LABEL(label_name[, ...]*)
+  ```
+
+- masking_function：
+
+  maskall不是预置函数，硬编码在代码中，不支持\\df展示。
+
+  预置时脱敏方式如下：
+
+  ```ebnf+diagram
+  masking_function ::= maskall | randommasking | creditcardmasking | basicemailmasking | fullemailmasking | shufflemasking | alldigitsmasking | regexpmasking
+  ```
+
+- policy_filter:
+
+  ```ebnf+diagram
+  policy_filter ::= FILTER ON FILTER_TYPE(filter_value [,...]*)[,...]*
+  ```
+
+- FILTER_TYPE:
+
+  ```ebnf+diagram
+  filter_type ::= IP | APP | ROLES
+  ```
+
+## 参数说明
+
+- **policy_name**
+
+  审计策略名称，需要唯一，不可重复。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- **label_name**
+
+  资源标签名称。
+
+- **masking_clause**
+
+  指出使用何种脱敏函数对被label_name标签标记的数据库资源进行脱敏，支持用schema.function的方式指定脱敏函数。
+
+- **policy_filter**
+
+  指出该脱敏策略对何种身份的用户生效，若为空表示对所用用户生效。
+
+- **FILTER_TYPE**
+
+  描述策略过滤的条件类型，包括IP | APP | ROLES。
+
+- **filter_value**
+
+  指具体过滤信息内容，例如具体的IP，具体的APP名称，具体的用户名。
+
+- **ENABLE|DISABLE**
+
+  可以打开或关闭脱敏策略。若不指定ENABLE|DISABLE，语句默认为ENABLE。
+
+## 示例
+
+```sql
+--创建dev_mask和bob_mask用户。
+mogdb=# CREATE USER dev_mask PASSWORD 'dev@1234';
+mogdb=# CREATE USER bob_mask PASSWORD 'bob@1234';
+
+--创建一个表tb_for_masking
+mogdb=# CREATE TABLE tb_for_masking(col1 text, col2 text, col3 text);
+
+--创建资源标签标记敏感列col1
+mogdb=# CREATE RESOURCE LABEL mask_lb1 ADD COLUMN(tb_for_masking.col1);
+
+--创建资源标签标记敏感列col2
+mogdb=# CREATE RESOURCE LABEL mask_lb2 ADD COLUMN(tb_for_masking.col2);
+
+--对访问敏感列col1的操作创建脱敏策略
+mogdb=# CREATE MASKING POLICY maskpol1 maskall ON LABEL(mask_lb1);
+
+--创建仅对用户dev_mask和bob_mask,客户端工具为psql和gsql，IP地址为'10.20.30.40', '127.0.0.0/24'场景下生效的脱敏策略。
+mogdb=# CREATE MASKING POLICY maskpol2 randommasking ON LABEL(mask_lb2) FILTER ON ROLES(dev_mask, bob_mask), APP(psql, gsql), IP('10.20.30.40', '127.0.0.0/24');
+```
+
+## 相关链接
+
+[ALTER MASKING POLICY](10.1-ALTER-MASKING-POLICY)，[DROP MASKING POLICY](84.2-DROP-MASKING-POLICY)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/50.3-CREATE-MODEL.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/50.3-CREATE-MODEL.md
new file mode 100644
index 0000000000000000000000000000000000000000..14ccb0fea88c62e7e9610765c5ac1289ff0c2a38
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/50.3-CREATE-MODEL.md
@@ -0,0 +1,85 @@
+---
+title: CREATE MODEL
+summary: CREATE MODEL
+author: Zhang Cuiping
+date: 2021-11-01
+---
+
+# CREATE MODEL
+
+## 功能描述
+
+训练机器学习模型并保存模型。
+
+## 注意事项
+
+- 模型名称具有唯一性约束，注意命名格式。
+- AI训练时长波动较大，在部分情况下训练运行时间较长，设置的GUC参数statement_timeout时长过短会导致训练中断。建议statement_timeout设置为0，不对语句执行时长进行限制。
+
+## 语法格式
+
+```ebnf+diagram
+CreateModel ::= CREATE MODEL model_name USING algorithm_name
+[FEATURES { {expression [ [ AS ] output_name ]} [, ...] }]
+[TARGET { {expression [ [ AS ] output_name ]} [, ...] }]
+FROM { table_name | select_query }
+WITH hyperparameter_name = { hyperparameter_value | DEFAULT } [, ...]
+```
+
+## 参数说明
+
+- **model_name**
+
+  对训练模型进行命名，模型名称具有唯一性约束。
+
+  取值范围: 字符串，需要符合标识符的命名规范。
+
+- **architecture_name**
+
+  训练模型的算法类型。
+
+  取值范围: 字符型，当前支持：logistic_regression、linear_regression、svm_classification、kmeans。
+
+- **attribute_list**
+
+  枚举训练模型的输入列名。
+
+  取值范围: 字符型，需要符合数据属性名的命名规范。
+
+- **attribute_name**
+
+  在监督学习任务重训练模型的目标列名(可进行简单的表达式处理)。
+
+  取值范围: 字符型，需要符合数据属性名的命名规范。
+
+- **subquery**
+
+  数据源。
+
+  取值范围: 字符串，符合数据库SQL语法。
+
+- **hyper_parameter_name**
+
+  机器学习模型的超参名称。
+
+  取值范围: 字符串，针对不同算法范围不同。
+
+- **hp_value**
+
+  超参数值。
+
+  取值范围: 字符串，针对不同算法范围不同。
+
+## 示例
+
+```sql
+CREATE MODEL price_model USING logistic_regression
+ FEATURES size, lot
+ TARGET price
+ FROM HOUSES
+ (WITH learning_rate=0.88, max_iterations=default);
+```
+
+## 相关链接
+
+[DROP MODEL](84.3-DROP-MODEL)，[PREDICT BY](112.1-PREDICT-BY)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/51-CREATE-MATERIALIZED-VIEW.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/51-CREATE-MATERIALIZED-VIEW.md
new file mode 100644
index 0000000000000000000000000000000000000000..e10832d28a74a189bb3db144f53bfa7b04fff898
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/51-CREATE-MATERIALIZED-VIEW.md
@@ -0,0 +1,76 @@
+---
+title: CREATE MATERIALIZED VIEW
+summary: CREATE MATERIALIZED VIEW
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE MATERIALIZED VIEW
+
+## 功能描述
+
+CREATE MATERIALIZED VIEW会创建一个全量物化视图，并且后续可以使用REFRESH MATERIALIZED VIEW（全量刷新）刷新物化视图的数据。
+
+CREATE MATERIALIZED VIEW类似于CREATE TABLE AS，不过它会记住被用来初始化该视图的查询， 因此它可以在后续中进行数据刷新。一个物化视图有很多和表相同的属性，但是不支持临时物化视图。
+
+## 注意事项
+
+- 全量物化视图不可以在临时表或全局临时表上创建。
+- 全量物化视图不支持nodegroup。
+- 创建全量物化视图后，基表中的绝大多数DDL操作不再支持。
+- 不支持对全量物化视图进行IUD操作。
+- 全量物化视图创建后，当基表数据发生变化时，需要使用刷新（REFRESH）命令保持物化视图与基表同步。
+
+## 语法格式
+
+```ebnf+diagram
+CreateMaterializedView ::= CREATE MATERIALIZED VIEW mv_name
+    [ (column_name [, ...] ) ]
+    [ WITH ( {storage_parameter = value} [, ... ] ) ]
+      [ TABLESPACE tablespace_name ]
+    AS query
+    [ WITH [ NO ] DATA ];
+```
+
+## 参数说明
+
+- **mv_name**
+
+  要创建的物化视图的名称（可以被模式限定）。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- **column_name**
+
+  新物化视图中的一个列名。物化视图支持指定列，指定列需要和后面的查询语句结果的列数量保持一致；如果没有提供列名，会从查询的输出列名中获取列名。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- **WITH ( storage_parameter [= value] [, … ] )**
+
+  这个子句为表或索引指定一个可选的存储参数。详见[CREATE TABLE](60-CREATE-TABLE)。
+
+- **TABLESPACE tablespace_name**
+
+  指定新建物化视图所属表空间。如果没有声明，将使用默认表空间。
+
+- **AS query**
+
+  一个SELECT、TABLE 或者VALUES命令。这个查询将在一个安全受限的操作中运行。
+
+## 示例
+
+```sql
+--创建一个普通表
+mogdb=# CREATE TABLE my_table (c1 int, c2 int);
+--创建全量物化视图
+mogdb=# CREATE MATERIALIZED VIEW my_mv AS SELECT * FROM my_table;
+--基表写入数据
+mogdb=# INSERT INTO my_table VALUES(1,1),(2,2);
+--对全量物化视图my_mv进行全量刷新
+mogdb=# REFRESH MATERIALIZED VIEW my_mv;
+```
+
+## 相关链接
+
+[ALTER MATERIALIZED VIEW](11-ALTER-MATERIALIZED-VIEW)，  [CREATE INCREMENTAL MATERIALIZED VIEW](49.1-CREATE-INCREMENTAL-MATERIALIZED-VIEW)，[CREATE TABLE](60-CREATE-TABLE)，[DROP MATERIALIZED VIEW](85-DROP-MATERIALIZED-VIEW)，[REFRESH INCREMENTAL MATERIALIZED VIEW](115.1-REFRESH-INCREMENTAL-MATERIALIZED-VIEW)，[REFRESH MATERIALIZED VIEW](116-REFRESH-MATERIALIZED-VIEW)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/51.1-CREATE-OPERATOR.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/51.1-CREATE-OPERATOR.md
new file mode 100644
index 0000000000000000000000000000000000000000..e4ba5aefe4eabea6f87e1991afb9d8dcaf6c210e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/51.1-CREATE-OPERATOR.md
@@ -0,0 +1,117 @@
+---
+title: CREATE OPERATOR
+summary: CREATE OPERATOR
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# CREATE OPERATOR
+
+## 功能描述
+
+定义一个新操作符。
+
+## 注意事项
+
+CREATE OPERATOR定义一个新的 name操作符。 定义该操作符的用户将成为其所有者。如果给出了一个模式名， 那么该操作符将在指定的模式中创建。否则它会在当前模式中创建。
+
+操作符 name 是一个由下列字符组成的字符串：
+
+- \- * / &lt; &gt; = ~ ! @ # % ^ & | \` ?
+
+选择名字的时候有几个限制：
+
+- -和/*不能在操作符名的任何地方出现， 因为它们会被认为是一个注释的开始。
+
+- 一个多字符的操作符不能以+或-结尾， 除非该名字还包含至少下面字符之一：
+
+    \~ ! @ # % ^ & | \` ?
+
+- =&gt; 作为一个操作符名的使用已经废弃了。
+
+操作符!=在输入时映射成&lt;&gt;， 因此这两个名称总是等价的。
+
+至少需要定义一个LEFTARG和RIGHTARG。对于双目操作符来说， 两者都需要定义。对右目操作符来说，只需要定义LEFTARG， 而对于左目操作符来说，只需要定义RIGHTARG。
+
+同样，function_name 过程必须已经用CREATE FUNCTION定义过， 而且必须定义为接受正确数量的指定类型参数(一个或是两个)。
+
+其它子句声明可选的操作符优化子句。他们的含义在[第 35.13 节](http://postgres.cn/docs/9.3/xoper-optimization.html)里定义。
+
+要想能够创建一个操作符，你必须在参数类型和返回类型上有USAGE权限， 还要在底层函数上有EXECUTE权限。如果指定了交换或者负操作符， 你必须拥有这些操作符。
+
+## 语法格式
+
+```ebnf+diagram
+CreateOperator ::= CREATE OPERATOR name (
+    PROCEDURE = function_name
+    [, LEFTARG = left_type ] [, RIGHTARG = right_type ]
+    [, COMMUTATOR = com_op ] [, NEGATOR = neg_op ]
+    [, RESTRICT = res_proc ] [, JOIN = join_proc ]
+    [, HASHES ] [, MERGES ]
+)
+```
+
+## 参数说明
+
+- **name**
+
+  要定义的操作符。可用的字符见上文。其名字可以用模式修饰， 比如CREATE OPERATOR myschema.+ (…)。如果没有模式， 则在当前模式中创建操作符。同一个模式中的两个操作符可以有一样的名字， 只要他们操作不同的数据类型。这是一个重载过程。
+
+- **function_name**
+
+  用于实现该操作符的函数。
+
+- **left_type**
+
+  操作符左边的参数数据类型，如果存在的话。如果是左目操作符，这个参数可以省略。
+
+- **right_type**
+
+  操作符右边的参数数据类型，如果存在的话。如果是右目操作符，这个参数可以省略。
+
+- **com_op**
+
+  该操作符对应的交换操作符。
+
+- **neg_op**
+
+  该操作符对应的负操作符。
+
+- **res_proc**
+
+  此操作符约束选择性评估函数。
+
+- **join_proc**
+
+  此操作符连接选择性评估函数。
+
+- **HASHES**
+
+  表明此操作符支持 Hash 连接。
+
+- **MERGES**
+
+  表明此操作符可以支持一个融合连接。
+
+  使用OPERATOR()语法在com_op 或者其它可选参数里给出一个模式修饰的操作符名，比如：
+
+  ```sql
+  COMMUTATOR = OPERATOR(myschema.===) ,
+  ```
+
+## 示例
+
+下面命令定义一个新操作符：面积相等，用于box数据类型。
+
+```sql
+CREATE OPERATOR === (
+    LEFTARG = box,
+    RIGHTARG = box,
+    PROCEDURE = area_equal_procedure,
+    COMMUTATOR = ===,
+    NEGATOR = !==,
+    RESTRICT = area_restriction_procedure,
+    JOIN = area_join_procedure,
+    HASHES, MERGES
+);
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/51.2-CREATE-PACKAGE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/51.2-CREATE-PACKAGE.md
new file mode 100644
index 0000000000000000000000000000000000000000..b4661ab40432a9890bbf2868c789b61fc8aba0ab
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/51.2-CREATE-PACKAGE.md
@@ -0,0 +1,88 @@
+---
+title: CREATE PACKAGE
+summary: CREATE PACKAGE
+author: Zhang Cuiping
+date: 2021-11-01
+---
+
+# CREATE PACKAGE
+
+## 功能描述
+
+创建一个新的PACKAGE。
+
+## 注意事项
+
+- 由于升级的限制，在V5R2C00版本中，即使在不同的Package间，也无法创建同名同参的存储过程。
+- package只支持集中式，无法在分布式中使用。
+- 在package specification中声明过的函数或者存储过程，必须在package body中找到定义。
+- 在实例化中，无法调用带有commit/rollback的存储过程。
+- 不能在Trigger中调用package函数。
+- 不能在外部SQL中直接使用package当中的变量。
+- 不允许在package外部调用package的私有变量和存储过程。
+- 不支持其它存储过程不支持的用法，例如，在function中不允许调用commit/rollback，则package的function中同样无法调用commit/rollback。
+- 不支持schema与package同名。
+- 只支持A风格的存储过程和函数定义。
+- 不支持package内有同名变量，包括包内同名参数。
+- package的全局变量为session级，不同session之间package的变量不共享。
+- package中调用自治事务的函数，不允许使用公有变量，以及递归的使用公有变量的函数。
+- package中不支持声明ref cursor类型。
+
+## 语法格式
+
+- CREATE PACKAGE SPECIFICATION语法格式
+
+  ```ebnf+diagram
+  CreatePackage ::= CREATE [ OR REPLACE ] PACKAGE [ schema ] package_name
+      [ invoker_rights_clause ] { IS | AS } item_list_1 END package_name;
+  ```
+
+  invoker_rights_clause可以被声明为AUTHID DEFINER或者AUTHID INVOKER，分别为定义者权限和调用者权限。
+  item_list_1可以为声明的变量或者存储过程以及函数。
+
+  PACKAGE SPECIFICATION(包规格)声明了包内的公有变量、函数、异常等，可以被外部函数或者存储过程调用。在PACKAGE SPECIFICATION中只能声明存储过程、函数，不能定义存储过程或者函数。
+
+- CREATE PACKAGE BODY语法格式。
+
+  ```ebnf+diagram
+  CreatePackageBody ::= CREATE [ OR REPLACE ] PACKAGE BODY [ schema ] package_name
+      { IS | AS } declare_section [ initialize_section ] END package_name;
+  ```
+
+  PACKAGE BODY(包体内)定义了包的私有变量、函数等。如果变量或者函数没有在PACKAGE SPECIFICATION中声明过，那么这个变量或者函数则为私有变量或者函数。
+
+  PACKAGE BODY也可以声明实例化部分，用来初始化package，详见示例。
+
+## 示例
+
+- CREATE PACKAGE SPECIFICATION示例
+
+  ```sql
+  CREATE OR REPLACE PACKAGE emp_bonus IS
+  var1 int:=1;--公有变量
+  var2 int:=2;
+  PROCEDURE testpro1(var3 int);--公有存储过程，可以被外部调用
+  END emp_bonus;
+  /
+  ```
+
+- CREATE PACKAGE BODY示例
+
+  ```sql
+  drop table if exists test1;
+  create or replace package body emp_bonus is
+  var3 int:=3;
+  var4 int:=4;
+  procedure testpro1(var5 int)
+  is
+  begin
+  create table if not exists test1(col1 int);
+  insert into test1 values(var1);
+  insert into test1 values(var5);
+  end;
+  begin  --实例化开始
+  var4:=9;
+  testpro1(var4);
+  end emp_bonus;
+  /
+  ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/52-CREATE-ROW-LEVEL-SECURITY-POLICY.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/52-CREATE-ROW-LEVEL-SECURITY-POLICY.md
new file mode 100644
index 0000000000000000000000000000000000000000..03a330df70b3a89d543fe2bf5b34badab72199e1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/52-CREATE-ROW-LEVEL-SECURITY-POLICY.md
@@ -0,0 +1,175 @@
+---
+title: CREATE ROW LEVEL SECURITY POLICY
+summary: CREATE ROW LEVEL SECURITY POLICY
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE ROW LEVEL SECURITY POLICY
+
+## 功能描述
+
+对表创建行访问控制策略。
+
+当对表创建了行访问控制策略，只有打开该表的行访问控制开关(ALTER TABLE … ENABLE ROW LEVEL SECURITY)，策略才能生效。否则不生效。
+
+当前行访问控制影响数据表的读取操作(SELECT、UPDATE、DELETE)，暂不影响数据表的写入操作(INSERT、MERGE INTO)。表所有者或系统管理员可以在USING子句中创建表达式，在客户端执行数据表读取操作时，数据库后台在查询重写阶段会将满足条件的表达式拼接并应用到执行计划中。针对数据表的每一条元组，当USING表达式返回TRUE时，元组对当前用户可见，当USING表达式返回FALSE或NULL时，元组对当前用户不可见。
+
+行访问控制策略名称是针对表的，同一个数据表上不能有同名的行访问控制策略；对不同的数据表，可以有同名的行访问控制策略。
+
+行访问控制策略可以应用到指定的操作(SELECT、UPDATE、DELETE、ALL)，ALL表示会影响SELECT、UPDATE、DELETE三种操作；定义行访问控制策略时，若未指定受影响的相关操作，默认为ALL。
+
+行访问控制策略可以应用到指定的用户(角色)，也可应用到全部用户(PUBLIC)；定义行访问控制策略时，若未指定受影响的用户，默认为PUBLIC。
+
+## 注意事项
+
+- 支持对行存表、行存分区表、列存表、列存分区表、unlogged表、hash表定义行访问控制策略。
+- 不支持外表、本地临时表定义行访问控制策略。
+- 不支持对视图定义行访问控制策略。
+- 同一张表上可以创建多个行访问控制策略，一张表最多创建100个行访问控制策略。
+- 系统管理员不受行访问控制影响，可以查看表的全量数据。
+- 通过SQL语句、视图、函数、存储过程查询包含行访问控制策略的表，都会受影响。
+
+## 语法格式
+
+```ebnf+diagram
+CreateRowLevelSecurityPolicy ::= CREATE [ ROW LEVEL SECURITY ] POLICY policy_name ON table_name
+     [ AS { PERMISSIVE | RESTRICTIVE } ]
+     [ FOR { ALL | SELECT | UPDATE | DELETE } ]
+     [ TO { role_name | PUBLIC | CURRENT_USER | SESSION_USER } [, ...] ]
+     USING ( using_expression )
+```
+
+## 参数说明
+
+- **policy_name**
+
+  行访问控制策略名称，同一个数据表上行访问控制策略名称不能相同。
+
+- **table_name**
+
+  行访问控制策略的表名。
+
+- **PERMISSIVE | RESTRICTIVE**
+
+  PERMISSIVE指定行访问控制策略为宽容性策略，宽容性策略的条件用OR表达式拼接。
+
+  RESTRICTIVE指定行访问控制策略为限制性策略，限制性策略的条件用AND表达式拼接。拼接方式如下：
+
+  ```
+  (using_expression_permissive_1 OR using_expression_permissive_2 ...) AND (using_expression_restrictive_1 AND using_expression_restrictive_2 ...)
+  ```
+
+  缺省值为PERMISSIVE。
+
+- **command**
+
+  当前行访问控制影响的SQL操作，可指定操作包括：ALL、SELECT、UPDATE、DELETE。当未指定时，ALL为默认值，涵盖SELECT、UPDATE、DELETE操作。
+
+  当command为SELECT时，SELECT类操作受行访问控制的影响，只能查看到满足条件(using_expression返回值为TRUE)的元组数据，受影响的操作包括SELECT、UPDATE ... RETURNING、DELETE ... RETURNING。
+
+  当command为UPDATE时，UPDATE类操作受行访问控制的影响，只能更新满足条件(using_expression返回值为TRUE)的元组数据，受影响的操作包括UPDATE、 UPDATE ... RETURNING、 SELECT ... FOR UPDATE/SHARE。
+
+  当command为DELETE时，DELETE类操作受行访问控制的影响，只能删除满足条件(using_expression返回值为TRUE)的元组数据，受影响的操作包括DELETE、 DELETE ... RETURNING。
+
+  行访问控制策略与适配的SQL语法关系参加下表：
+
+  **表 1** ROW LEVEL SECURITY策略与适配SQL语法关系
+
+  | **Command**                 | **SELECT/ALL policy** | **UPDATE/ALL policy** | **DELETE/ALL policy** |
+  | :-------------------------- | :-------------------- | :-------------------- | :-------------------- |
+  | **SELECT**                  | Existing row          | No                    | No                    |
+  | **SELECT FOR UPDATE/SHARE** | Existing row          | Existing row          | No                    |
+  | **UPDATE**                  | No                    | Existing row          | No                    |
+  | **UPDATE RETURNING**        | Existing row          | Existing row          | No                    |
+  | **DELETE**                  | No                    | No                    | Existing row          |
+  | **DELETE RETURNING**        | Existing row          | No                    | Existing row          |
+
+- **role_name**
+
+  行访问控制影响的数据库用户。
+
+  当未指定时，PUBLIC为默认值，PUBLIC表示影响所有数据库用户，可以指定多个受影响的数据库用户。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 系统管理员不受行访问控制特性影响。
+
+- **using_expression**
+
+  行访问控制的表达式（返回boolean值）。
+
+  条件表达式中不能包含AGG函数和窗口（WINDOW）函数。在查询重写阶段，如果数据表的行访问控制开关打开，满足条件的表达式会添加到计划树中。针对数据表的每条元组，会进行表达式计算，只有表达式返回值为TRUE时，行数据对用户才可见（SELECT、UPDATE、DELETE）；当表达式返回FALSE时，该元组对当前用户不可见，用户无法通过SELECT语句查看此元组，无法通过UPDATE语句更新此元组，无法通过DELETE语句删除此元组。
+
+## 示例
+
+```sql
+--创建用户alice
+mogdb=# CREATE USER alice PASSWORD 'xxxxxxxxx';
+
+--创建用户bob
+mogdb=# CREATE USER bob PASSWORD 'xxxxxxxxx';
+
+--创建数据表all_data
+mogdb=# CREATE TABLE all_data(id int, role varchar(100), data varchar(100));
+
+--向数据表插入数据
+mogdb=# INSERT INTO all_data VALUES(1, 'alice', 'alice data');
+mogdb=# INSERT INTO all_data VALUES(2, 'bob', 'bob data');
+mogdb=# INSERT INTO all_data VALUES(3, 'peter', 'peter data');
+
+--将表all_data的读取权限赋予alice和bob用户
+mogdb=# GRANT SELECT ON all_data TO alice, bob;
+
+--打开行访问控制策略开关
+mogdb=# ALTER TABLE all_data ENABLE ROW LEVEL SECURITY;
+
+--创建行访问控制策略，当前用户只能查看用户自身的数据
+mogdb=# CREATE ROW LEVEL SECURITY POLICY all_data_rls ON all_data USING(role = CURRENT_USER);
+
+--查看表all_data相关信息
+mogdb=# \d+ all_data
+                               Table "public.all_data"
+ Column |          Type          | Modifiers | Storage  | Stats target | Description
+--------+------------------------+-----------+----------+--------------+-------------
+ id     | integer                |           | plain    |              |
+ role   | character varying(100) |           | extended |              |
+ data   | character varying(100) |           | extended |              |
+Row Level Security Policies:
+    POLICY "all_data_rls"
+      USING (((role)::name = "current_user"()))
+Has OIDs: no
+Options: orientation=row, compression=no, enable_rowsecurity=true
+
+--当前用户执行SELECT操作
+mogdb=# SELECT * FROM all_data;
+ id | role  |    data
+----+-------+------------
+  1 | alice | alice data
+  2 | bob   | bob data
+  3 | peter | peter data
+(3 rows)
+
+mogdb=# EXPLAIN(COSTS OFF) SELECT * FROM all_data;
+      QUERY PLAN
+----------------------
+ Seq Scan on all_data
+(1 row)
+
+--切换至alice用户执行SELECT操作
+mogdb=# SELECT * FROM all_data;
+ id | role  |    data
+----+-------+------------
+  1 | alice | alice data
+(1 row)
+
+mogdb=# EXPLAIN(COSTS OFF) SELECT * FROM all_data;
+ QUERY PLAN
+----------------------------------------------------------------
+ Seq Scan on all_data
+   Filter: ((role)::name = 'alice'::name)
+ Notice: This query is influenced by row level security feature
+(3 rows)
+```
+
+## 相关链接
+
+[DROP ROW LEVEL SECURITY POLICY](87-DROP-ROW-LEVEL-SECURITY-POLICY)，[ALTER ROW LEVEL SECURITY POLICY](13-ALTER-ROW-LEVEL-SECURITY-POLICY)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/53-CREATE-PROCEDURE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/53-CREATE-PROCEDURE.md
new file mode 100644
index 0000000000000000000000000000000000000000..01036ab5544a21cdc7a07acb25d4ce626fc42981
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/53-CREATE-PROCEDURE.md
@@ -0,0 +1,113 @@
+---
+title: CREATE PROCEDURE
+summary: CREATE PROCEDURE
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE PROCEDURE
+
+## 功能描述
+
+创建一个新的存储过程。
+
+## 注意事项
+
+- 如果创建存储过程时参数或返回值带有精度，不进行精度检测。
+- 创建存储过程时，存储过程定义中对表对象的操作建议都显示指定模式，否则可能会导致存储过程执行异常。
+- 在创建存储过程时，存储过程内部通过SET语句设置current_schema和search_path无效。执行完函数search_path和current_schema与执行函数前的search_path和current_schema保持一致。
+- 如果存储过程参数中带有出参，SELECT调用存储过程必须缺省出参，CALL调用存储过程调用非重载函数时必须指定出参，对于重载的package函数，out参数可以缺省，具体信息参见[CALL](34-CALL)的示例。
+- 存储过程指定package属性时支持重载。
+- 在创建procedure时，不能在avg函数外面嵌套其他agg函数，或者其他系统函数。
+- 在存储过程内部调用其它无参数的存储过程时，可以省略括号，直接使用存储过程名进行调用。
+- 存储过程支持参数注释的查看与导出、导入。
+- 存储过程支持介于IS/AS与plsql_body之间的注释的查看与导出、导入。
+
+## 语法格式
+
+```ebnf+diagram
+CreateProcedure ::= CREATE [ OR REPLACE ] PROCEDURE procedure_name
+    [ ( {[ argmode ] [ argname ] argtype [ { DEFAULT | ':=' | = } expression ]}[, '...']) ]
+    [
+       { IMMUTABLE | STABLE | VOLATILE }
+       | { SHIPPABLE | NOT SHIPPABLE }
+       | {PACKAGE}
+       | [ NOT ] LEAKPROOF
+       | { CALLED ON NULL INPUT | RETURNS NULL ON NULL INPUT | STRICT }
+       | {[ EXTERNAL ] SECURITY INVOKER | [ EXTERNAL ] SECURITY DEFINER | AUTHID DEFINER | AUTHID CURRENT_USER}
+       | COST execution_cost
+       | SET configuration_parameter { TO value | = value | FROM CURRENT }
+    ][ '...' ]
+ { IS | AS }
+plsql_body
+```
+
+## 参数说明
+
+- **OR REPLACE**
+
+  当存在同名的存储过程时，替换原来的定义。
+
+- **procedure_name**
+
+  创建的存储过程名称，可以带有模式名。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- **argmode**
+
+  参数的模式。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** VARIADIC用于声明数组类型的参数。
+
+  取值范围:  IN、OUT、INOUT或VARIADIC。缺省值是IN。只有OUT模式的参数能跟在VARIADIC参数之后。
+
+- **argname**
+
+  参数的名称。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- **argtype**
+
+  参数的数据类型。可以使用%TYPE或%ROWTYPE间接引用变量或表的类型，详细可参考存储过程章节[定义变量](1-6-basic-statements)。
+
+  取值范围: 可用的数据类型。
+
+- **configuration_parameter**
+
+  - **value**
+
+    把指定的配置参数设置为给定的值。如果value是DEFAULT，则在新的会话中使用系统的缺省设置。OFF关闭设置。
+
+    取值范围: 字符串
+
+    - DEFAULT
+    - OFF
+    - 指定默认值。
+
+  - **from current**
+
+    取当前会话中的值设置为configuration_parameter的值。
+
+- **IMMUTABLE、STABLE**等
+
+  行为约束可选项。各参数的功能与CREATE FUNCTION类似，详细说明见[CREATE FUNCTION](48-CREATE-FUNCTION)。
+
+- **plsql_body**
+
+  PL/SQL存储过程体。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 当在存储过程体中进行创建用户等涉及用户密码相关操作时，系统表及csv日志中会记录密码的明文。因此不建议用户在存储过程体中进行涉及用户密码的相关操作。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** argument_name和argmode的顺序没有严格要求，推荐按照argument_name、argmode、argument_type的顺序使用。
+
+## 相关链接
+
+[DROP PROCEDURE](88-DROP-PROCEDURE)
+
+## 优化建议
+
+- analyse | analyze
+  - 不支持在事务或匿名块中执行analyze 。
+  - 不支持在函数或存储过程中执行analyze操作。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/53.1-CREATE-RESOURCE-LABEL.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/53.1-CREATE-RESOURCE-LABEL.md
new file mode 100644
index 0000000000000000000000000000000000000000..769fd8cadf8581d5c80e07447aa93f18b5d7f69e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/53.1-CREATE-RESOURCE-LABEL.md
@@ -0,0 +1,85 @@
+---
+title: CREATE RESOURCE LABEL
+summary: CREATE RESOURCE LABEL
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# CREATE RESOURCE LABEL
+
+## 功能描述
+
+创建资源标签。
+
+## 注意事项
+
+只有poladmin、sysadmin或初始用户能正常执行此操作。
+
+## 语法格式
+
+```ebnf+diagram
+CreateResourceLabel ::= CREATE RESOURCE LABEL [IF NOT EXISTS] label_name ADD label_item_list[, ...]*;
+```
+
+- label_item_list：
+
+  ```ebnf+diagram
+  label_item_list ::= resource_type(resource_path[, ...]*)
+  ```
+
+- resource_type：
+
+  ```ebnf+diagram
+  resource_type ::= TABLE | COLUMN | SCHEMA | VIEW | FUNCTION
+  ```
+
+## 参数说明
+
+- **label_name**
+
+  资源标签名称，创建时要求不能与已有标签重名。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- **resource_type**
+
+  指的是要标记的数据库资源类型。
+
+- **resource_path**
+
+  指的是描述具体的数据库资源的路径。
+
+## 示例
+
+```sql
+--创建一个表tb_for_label
+mogdb=# CREATE TABLE tb_for_label(col1 text, col2 text, col3 text);
+
+--创建一个模式schema_for_label
+mogdb=# CREATE SCHEMA schema_for_label;
+
+--创建一个视图view_for_label
+mogdb=# CREATE VIEW view_for_label AS SELECT 1;
+
+--创建一个函数func_for_label
+mogdb=# CREATE FUNCTION func_for_label RETURNS TEXT AS $$ SELECT col1 FROM tb_for_label; $$ LANGUAGE SQL;
+
+--基于表创建资源标签
+mogdb=# CREATE RESOURCE LABEL IF NOT EXISTS table_label add TABLE(public.tb_for_label);
+
+--基于列创建资源标签
+mogdb=# CREATE RESOURCE LABEL IF NOT EXISTS column_label add COLUMN(public.tb_for_label.col1);
+
+--基于模式创建资源标签
+mogdb=# CREATE RESOURCE LABEL IF NOT EXISTS schema_label add SCHEMA(schema_for_label);
+
+--基于视图创建资源标签
+mogdb=# CREATE RESOURCE LABEL IF NOT EXISTS view_label add VIEW(view_for_label);
+
+--基于函数创建资源标签
+mogdb=# CREATE RESOURCE LABEL IF NOT EXISTS func_label add FUNCTION(func_for_label);
+```
+
+## 相关链接
+
+[ALTER RESOURCE LABEL](11.2-ALTER-RESOURCE-LABEL)，[DROP RESOURCE LABEL](86.1-DROP-RESOURCE-LABEL)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/53.2-CREATE-RESOURCE-POOL.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/53.2-CREATE-RESOURCE-POOL.md
new file mode 100644
index 0000000000000000000000000000000000000000..211b8f52cb35d63a14e827d61697fe7ed71c7184
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/53.2-CREATE-RESOURCE-POOL.md
@@ -0,0 +1,136 @@
+---
+title: CREATE RESOURCE POOL
+summary: CREATE RESOURCE POOL
+author: Zhang Cuiping
+date: 2021-11-01
+---
+
+# CREATE RESOURCE POOL
+
+## 功能描述
+
+创建一个资源池，并指定此资源池相关联的控制组。
+
+## 注意事项
+
+只要用户对当前数据库有CREATE权限，就可以创建资源池。
+
+## 语法格式
+
+```ebnf+diagram
+CreateResourcePool ::= CREATE RESOURCE POOL pool_name
+    [WITH ({MEM_PERCENT=pct | CONTROL_GROUP="group_name" | ACTIVE_STATEMENTS=stmt | MAX_DOP = dop | MEMORY_LIMIT='memory_size' | io_limits=io_limits | io_priority='io_priority' | nodegroup="nodegroupname" | is_foreign=boolean }[, ... ])];
+```
+
+## 参数说明
+
+- **pool_name**
+
+  资源池名称。
+
+  资源池名称不能和当前数据库里已有的资源池重名。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- **group_name**
+
+  控制组名称。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  >
+  > - 设置控制组名称时，语法可以使用双引号，也可以使用单引号。
+  > - group_name对大小写敏感。
+  > - 不指定group_name时，默认指定的字符串为 “Medium”，代表指定DefaultClass控制组的”Medium” Timeshare控制组。
+  > - 若数据库管理员指定自定义Class组下的Workload控制组，如control_group的字符串为：”class1:workload1”；代表此资源池指定到class1控制组下的workload1控制组。也可同时指定Workload控制组的层次，如control_group的字符串为：”class1:workload1:1”。
+  > - 若数据库用户指定Timeshare控制组代表的字符串，即”Rush”、”High”、”Medium”或”Low”其中一种，如control_group的字符串为”High”；代表资源池指定到DefaultClass控制组下的”High” Timeshare控制组。
+
+  取值范围: 字符串，要符合说明中的规则，其指定已创建的控制组。
+
+- **stmt**
+
+  资源池语句执行的最大并发数量。
+
+  取值范围: 数值型，-1~2147483647。
+
+- **dop**
+
+  资源池最大并发度，语句执行时能够创建的最多线程数量。
+
+  取值范围: 数值型，1~2147483647
+
+- **memory_size**
+
+  资源池最大使用内存。
+
+  取值范围: 字符串，内容范围1KB~2047GB
+
+- **mem_percent**
+
+  资源池可用内存占全部内存或者组用户内存使用的比例。
+
+  在多租户场景下，组用户和业务用户的mem_percent范围1-100，默认为20。
+
+  在普通场景下，普通用户的mem_percent范围为0-100，默认值为0。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** mem_percent和memory_limit同时指定时，只有mem_percent起作用。
+
+- **io_limits**
+
+  资源池每秒可触发IO次数上限。
+
+  对于行存，以万次为单位计数，而列存则以正常次数计数。
+
+- **io_priority**
+
+  IO利用率高达90%时，重消耗IO作业进行IO资源管控时关联的优先级等级。
+
+  包括三档可选：Low、Medium和High。不控制时可设置为None。默认为None。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** io_limits和io_priority的设置都仅对复杂作业有效。包括批量导入（INSERT INTO SELECT、COPY FROM、CREATE TABLE AS等），单DN数据量大约超过500MB的复杂查询和VACUUM FULL等操作。
+
+- **nodegroup**
+
+  在逻辑集群模式下，指定逻辑集群名称。必须是存在的逻辑集群。
+
+  如果逻辑集群名称包含大写字符、特殊符号或以数字开头，SQL语句中对逻辑集群名称需要加双引号。
+
+- **is_foreign**
+
+  在逻辑集群模式下，指定当前资源池用于控制没有关联本逻辑集群的普通用户的资源。这里的逻辑集群是由资源池nodegroup字段指定的。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  >
+  > - nodegroup必须是存在的逻辑集群，不能是elastic_group和安装的nodegroup (group_version1)。
+  > - 如果指定了is_foreign为true，则资源池不能再关联用户，即不允许通过CREATE USER … RESOURCE POOL语句来将该资源池配置给用户。该资源池自动检查用户是否关联到资源池指定的逻辑集群，如果用户没有关联到该逻辑集群，则这些用户在逻辑集群所包含的DN上运行将受到该资源池的资源控制。
+
+## 示例
+
+本示例假定用户已预先成功创建控制组。
+
+```sql
+--创建一个默认资源池，其控制组为"DefaultClass"组下属的"Medium" Timeshare Workload控制组。
+mogdb=# CREATE RESOURCE POOL pool1;
+
+-- 创建一个资源池，其控制组指定为"DefaultClass"组下属的"High" Timeshare Workload控制组。
+mogdb=# CREATE RESOURCE POOL pool2 WITH (CONTROL_GROUP="High");
+
+-- 创建一个资源池，其控制组指定为"class1"组下属的"Low" Timeshare Workload控制组。
+mogdb=# CREATE RESOURCE POOL pool3 WITH (CONTROL_GROUP="class1:Low");
+
+-- 创建一个资源池，其控制组指定为"class1"组下属的"wg1" Workload控制组。
+mogdb=# CREATE RESOURCE POOL pool4 WITH (CONTROL_GROUP="class1:wg1");
+
+-- 创建一个资源池，其控制组指定为"class1"组下属的"wg2" Workload控制组。
+mogdb=# CREATE RESOURCE POOL pool5 WITH (CONTROL_GROUP="class1:wg2:3");
+
+--删除资源池。
+mogdb=# DROP RESOURCE POOL pool1;
+mogdb=# DROP RESOURCE POOL pool2;
+mogdb=# DROP RESOURCE POOL pool3;
+mogdb=# DROP RESOURCE POOL pool4;
+mogdb=# DROP RESOURCE POOL pool5;
+```
+
+## 相关链接
+
+[ALTER RESOURCE POOL](11.3-ALTER-RESOURCE-POOL)，[DROP RESOURCE POOL](86.2-DROP-RESOURCE-POOL)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/54-CREATE-ROLE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/54-CREATE-ROLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..4621d6389a4d1f4a91ed7dc5de3b6e3a19110e3d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/54-CREATE-ROLE.md
@@ -0,0 +1,260 @@
+---
+title: CREATE ROLE
+summary: CREATE ROLE
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE ROLE
+
+## 功能描述
+
+创建角色。
+
+角色是拥有数据库对象和权限的实体。在不同的环境中角色可以认为是一个用户，一个组或者兼顾两者。
+
+## 注意事项
+
+- 在数据库中添加一个新角色，角色无登录权限。
+- 创建角色的用户必须具备CREATE ROLE的权限或者是系统管理员。
+
+## 语法格式
+
+```ebnf+diagram
+CreateRole ::= CREATE ROLE role_name [ [ WITH ] option [ ... ] ] [ ENCRYPTED | UNENCRYPTED ] { PASSWORD | IDENTIFIED BY } { 'password' [EXPIRED] | DISABLE };
+```
+
+其中角色信息设置子句option语法为：
+
+```ebnf+diagram
+option ::= {SYSADMIN | NOSYSADMIN}
+    | {MONADMIN | NOMONADMIN}
+    | {OPRADMIN | NOOPRADMIN}
+    | {POLADMIN | NOPOLADMIN}
+    | {AUDITADMIN | NOAUDITADMIN}
+    | {CREATEDB | NOCREATEDB}
+    | {USEFT | NOUSEFT}
+    | {CREATEROLE | NOCREATEROLE}
+    | {INHERIT | NOINHERIT}
+    | {LOGIN | NOLOGIN}
+    | {REPLICATION | NOREPLICATION}
+    | {INDEPENDENT | NOINDEPENDENT}
+    | {VCADMIN | NOVCADMIN}
+    | CONNECTION LIMIT connlimit
+    | VALID BEGIN 'timestamp'
+    | VALID UNTIL 'timestamp'
+    | RESOURCE POOL 'respool'
+    | PERM SPACE 'spacelimit'
+    | TEMP SPACE 'tmpspacelimit'
+    | SPILL SPACE 'spillspacelimit'
+    | IN ROLE role_name [, ...]
+    | IN GROUP role_name [, ...]
+    | ROLE role_name [, ...]
+    | ADMIN rol e_name [, ...]
+    | USER role_name [, ...]
+    | SYSID uid
+    | DEFAULT TABLESPACE tablespace_name
+    | PROFILE DEFAULT
+    | PROFILE profile_name
+    | PGUSER
+```
+
+## 参数说明
+
+- **role_name**
+
+  角色名称。
+
+  取值范围: 字符串，要符合标识符的命名规范，且最多为63个字符。若超过63个字符，数据库会截断并保留前63个字符当做角色名称。在创建角色时，数据库的时候会给出提示信息。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 标识符需要为字母、下划线、数字（0-9）或美元符号（$），且必须以字母（a-z）或下划线（_）开头。
+
+- **password**
+
+    登录密码。
+
+    密码规则如下：
+
+  - 密码默认不少于8个字符。
+  - 不能与用户名及用户名倒序相同。
+  - 至少包含大写字母（A-Z），小写字母（a-z），数字（0-9），非字母数字字符（限定为~!@#$%^&*()-_=+\|[{}];:,&lt;.&gt;/?）四类字符中的三类字符。
+  - 密码也可以是符合格式要求的密文字符串，这种情况主要用于用户数据导入场景，不推荐用户直接使用。如果直接使用密文密码，用户需要知道密文密码对应的明文，并且保证明文密码复杂度，数据库不会校验密文密码复杂度，直接使用密文密码的安全性由用户保证。
+  - 创建角色时，应当使用双引号或单引号将用户密码括起来。
+
+    取值范围: 字符串。
+
+- **EXPIRED**
+
+  在创建用户时可指定EXPIRED参数，即创建密码失效用户，该用户不允许执行简单查询和扩展查询。只有在修改自身密码后才可正常执行语句。
+
+- DISABLE
+
+  默认情况下，用户可以更改自己的密码，除非密码被禁用。要禁用用户的密码，请指定DISABLE。禁用某个用户的密码后，将从系统中删除该密码，此类用户只能通过外部认证来连接数据库，例如：kerberos认证。只有管理员才能启用或禁用密码。普通用户不能禁用初始用户的密码。要启用密码，请运行ALTER USER并指定密码。
+
+- **ENCRYPTED | UNENCRYPTED**
+
+  控制密码存储在系统表里的口令是否加密。按照产品安全要求，密码必须加密存储，所以，UNENCRYPTED在MogDB中禁止使用。因为系统无法对指定的加密口令字符串进行解密，所以如果目前的口令字符串已经是用SHA256加密的格式，则会继续照此存放，而不管是否声明了ENCRYPTED或UNENCRYPTED。这样就允许在dump/restore的时候重新加载加密的口令。
+
+- **SYSADMIN | NOSYSADMIN**
+
+  决定一个新角色是否为“系统管理员”，具有SYSADMIN属性的角色拥有系统最高权限。
+
+  缺省为NOSYSADMIN。
+
+- **AUDITADMIN | NOAUDITADMIN**
+
+  定义角色是否有审计管理属性。
+
+  缺省为NOAUDITADMIN。
+
+- **CREATEDB | NOCREATEDB**
+
+  决定一个新角色是否能创建数据库。
+
+  新角色没有创建数据库的权限。
+
+  缺省为NOCREATEDB。
+
+- **USEFT | NOUSEFT**
+
+  该参数为保留参数，暂未启用。
+
+- **CREATEROLE | NOCREATEROLE**
+
+  决定一个角色是否可以创建新角色（也就是执行CREATE ROLE和CREATE USER）。 一个拥有CREATEROLE权限的角色也可以修改和删除其他角色。
+
+  缺省为NOCREATEROLE。
+
+- **INHERIT | NOINHERIT**
+
+  这些子句决定一个角色是否“继承”它所在组的角色的权限。不推荐使用。
+
+- **LOGIN | NOLOGIN**
+
+  具有LOGIN属性的角色才可以登录数据库。一个拥有LOGIN属性的角色可以认为是一个用户。
+
+  缺省为NOLOGIN。
+
+- **REPLICATION | NOREPLICATION**
+
+  定义角色是否允许流复制或设置系统为备份模式。REPLICATION属性是特定的角色，仅用于复制。
+
+  缺省为NOREPLICATION。
+
+- **INDEPENDENT | NOINDEPENDENT**
+
+    定义私有、独立的角色。具有INDEPENDENT属性的角色，管理员对其进行的控制、访问的权限被分离，具体规则如下：
+
+  - 未经INDEPENDENT角色授权，系统管理员无权对其表对象进行增、删、查、改、拷贝、授权操作。
+  - 若将私有用户表的相关权限授予其他非私有用户，系统管理员也会获得同样的权限。
+  - 未经INDEPENDENT角色授权，系统管理员和拥有CREATEROLE属性的安全管理员无权修改INDEPENDENT角色的继承关系。
+  - 系统管理员无权修改INDEPENDENT角色的表对象的属主。
+  - 系统管理员和拥有CREATEROLE属性的安全管理员无权去除INDEPENDENT角色的INDEPENDENT属性。
+  - 系统管理员和拥有CREATEROLE属性的安全管理员无权修改INDEPENDENT角色的数据库口令，INDEPENDENT角色需管理好自身口令，口令丢失无法重置。
+  - 管理员属性用户不允许定义修改为INDEPENDENT属性。
+
+- **CONNECTION LIMIT**
+
+  声明该角色可以使用的并发连接数量。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+  >
+  > - 系统管理员不受此参数的限制。
+  > - connlimit数据库主节点单独统计，MogDB整体的连接数 = connlimit * 当前正常数据库主节点个数。
+
+  取值范围: 整数，&gt;=-1，缺省值为-1，表示没有限制。
+
+- **VALID BEGIN**
+
+  设置角色生效的时间戳。如果省略了该子句，角色无有效开始时间限制。
+
+- **VALID UNTIL**
+
+  设置角色失效的时间戳。如果省略了该子句，角色无有效结束时间限制。
+
+- **RESOURCE POOL**
+
+  设置角色使用的resource pool名称，该名称属于系统表：pg_resource_pool。
+
+- **PERM SPACE**
+
+  设置用户使用空间的大小，具体大小采用‘数字+单位’的格式，示例见下文。
+
+- **TEMP SPACE**
+
+  设置用户临时表存储空间限额，具体限额采用‘数字+单位’的格式，示例见下文。
+
+- **SPILL SPACE**
+
+  设置用户算子落盘空间限额，具体限额采用‘数字+单位’的格式，示例见下文。
+
+- **IN ROLE**
+
+  新角色立即拥有IN ROLE子句中列出的一个或多个现有角色拥有的权限。不推荐使用。
+
+- **IN GROUP**
+
+  IN GROUP是IN ROLE过时的拼法。不推荐使用。
+
+- **ROLE**
+
+  ROLE子句列出一个或多个现有的角色，它们将自动添加为这个新角色的成员，拥有新角色所有的权限。
+
+- **ADMIN**
+
+  ADMIN子句类似ROLE子句，不同的是ADMIN后的角色可以把新角色的权限赋给其他角色。
+
+- **USER**
+
+  USER子句是ROLE子句过时的拼法。
+
+- **SYSID**
+
+  SYSID子句将被忽略，无实际意义。
+
+- **DEFAULT TABLESPACE**
+
+  DEFAULT TABLESPACE子句将被忽略，无实际意义。
+
+- **PROFILE**
+
+  PROFILE子句将被忽略，无实际意义。
+
+- **PGUSER**
+
+  当前版本该属性没有实际意义，仅为了语法的前向兼容而保留。
+
+## 示例
+
+```sql
+--创建一个角色，名为manager，密码为xxxxxxxxx。
+mogdb=# CREATE ROLE manager IDENTIFIED BY 'xxxxxxxxx';
+
+--创建一个角色，从2015年1月1日开始生效，到2026年1月1日失效。
+mogdb=# CREATE ROLE miriam WITH LOGIN PASSWORD 'xxxxxxxxx' VALID BEGIN '2015-01-01' VALID UNTIL '2026-01-01';
+
+--修改角色manager的密码为abcd@123。
+mogdb=# ALTER ROLE manager IDENTIFIED BY 'abcd@123' REPLACE 'xxxxxxxxx';
+
+--修改角色manager为系统管理员。
+mogdb=# ALTER ROLE manager SYSADMIN;
+
+--删除角色manager。
+mogdb=# DROP ROLE manager;
+
+--删除角色miriam。
+mogdb=# DROP ROLE miriam;
+
+--创建角色r1并设置用户使用空间大小为1k。
+mogdb=# CREATE ROLE r1 PERM SPACE '1k' IDENTIFIED BY "Enmo@123";
+
+--创建角色r2并设置用户临时表存储空间限额为1k。
+mogdb=# CREATE ROLE r2 TEMP SPACE '1k' IDENTIFIED BY "Enmo@123";
+
+--创建角色r3并设置用户算子落盘空间限额为1M。
+mogdb=# CREATE ROLE r3 SPILL SPACE '1M' IDENTIFIED BY "Enmo@123";
+```
+
+## 相关链接
+
+[SET ROLE](129-SET-ROLE)，[ALTER ROLE](12-ALTER-ROLE)，[DROP ROLE](89-DROP-ROLE)，[GRANT](108-GRANT)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/55-CREATE-RULE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/55-CREATE-RULE.md
new file mode 100644
index 0000000000000000000000000000000000000000..0c04a78c952efb50d85849a9cd441d3f8df0fa3e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/55-CREATE-RULE.md
@@ -0,0 +1,72 @@
+---
+title: CREATE RULE
+summary: CREATE RULE
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE RULE
+
+## 功能描述
+
+定义一个新的重写规则。
+
+## 注意事项
+
+- 为了在表上定义或修改规则，你必须是该表的拥有者。
+- 如果在同一个表定义了多个相同类型的规则，则按规则的名称字母顺序触发它们。
+- 在视图上用于INSERT、UPDATE、DELETE的规则中可以添加RETURNING子句基于视图的字段返回。如果规则被INSERT RETURNING、UPDATE RETURNING、DELETE RETURNING命令触发，这些子句将用来计算输出结果。如果规则被不带RETURNING的命令触发，那么规则的RETURNING子句将被忽略。目前仅允许无条件的INSTEAD规则包含RETURNING子句，而且在同一个事件内的所有规则中最多只能有一个RETURNING子句。这样就确保只有一个RETURNING子句可以用于计算结果。如果在任何有效规则中都不存在RETURNING子句，该视图上的RETURNING查询将被拒绝。
+
+## 语法格式
+
+```ebnf+diagram
+CreateRule ::= CREATE [ OR REPLACE ] RULE name AS ON event
+    TO table_name [ WHERE condition ]
+    DO [ ALSO | INSTEAD ] { NOTHING | command | ( command ; command '...' ) }
+```
+
+其中event包含以下几种：
+
+```sql
+   SELECT
+   INSERT
+   DELETE
+   UPDATE
+```
+
+## 参数说明
+
+- **name**
+
+  创建的规则名。它必须在同一个表上的所有规则名字中唯一。
+
+  取值范围: 符合标识符命名规范的字符串，且最大长度不超过63个字符。
+
+- **table_name**
+
+  规则作用的表或者视图的名字（可以有模式修饰）。
+
+- **condition**
+
+  返回boolean的SQL条件表达式，决定是否实际执行规则。表达式除了引用NEW和OLD之外不能引用任何表， 并且不能有聚合函数。
+
+- **INSTEAD**
+
+  INSTEAD指示使用该命令**替换**初始事件。
+
+- **ALSO**
+
+  ALSO指示该命令应该在初始事件执行之后执行。如果既没有声明ALSO也没有声明INSTEAD， 那么ALSO为缺省值。
+
+- **command**
+
+  组成规则动作的命令。有效的命令是SELECT、 INSERT、UPDATE、 DELETE语句之一。
+
+## 示例
+
+```sql
+CREATE RULE "_RETURN" AS
+    ON SELECT TO t1
+    DO INSTEAD
+        SELECT * FROM t2;
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/56-CREATE-SCHEMA.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/56-CREATE-SCHEMA.md
new file mode 100644
index 0000000000000000000000000000000000000000..43f32930869a3f5be69213cece313c2decafa8e7
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/56-CREATE-SCHEMA.md
@@ -0,0 +1,89 @@
+---
+title: CREATE SCHEMA
+summary: CREATE SCHEMA
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE SCHEMA
+
+## 功能描述
+
+创建模式。
+
+访问命名对象时可以使用模式名作为前缀进行访问，如果无模式名前缀，则访问当前模式下的命名对象。创建命名对象时也可用模式名作为前缀修饰。
+
+另外，CREATE SCHEMA可以包括在新模式中创建对象的子命令，这些子命令和那些在创建完模式后发出的命令没有任何区别。如果使用了AUTHORIZATION子句，则所有创建的对象都将被该用户所拥有。
+
+## 注意事项
+
+- 只要用户对当前数据库有CREATE权限，就可以创建模式。
+- 系统管理员在普通用户同名schema下创建的对象，所有者为schema的同名用户（非系统管理员）。
+
+## 语法格式
+
+- 根据指定的名称创建模式。
+
+  ```ebnf+diagram
+  CreateSchema ::= CREATE SCHEMA schema_name
+      [ AUTHORIZATION user_name ] [WITH BLOCKCHAIN] [ schema_element [ ... ] ];
+  ```
+
+- 根据用户名创建模式。
+
+  ```ebnf+diagram
+  CreateSchema ::= CREATE SCHEMA AUTHORIZATION user_name [ schema_element [ ... ] ];
+  ```
+
+## 参数说明
+
+- **schema_name**
+
+  模式名称。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+  > 模式名不能和当前数据库里其他的模式重名。
+  > 模式的名称不可以“pg_”开头。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- **AUTHORIZATION user_name**
+
+  指定模式的所有者。当不指定schema_name时，把user_name当作模式名，此时user_name只能是角色名。
+
+  取值范围: 已存在的用户名/角色名。
+
+- **WITH BLOCKCHAIN**
+
+    指定模式的防篡改属性，防篡改模式下的行存普通用户表将自动扩展为防篡改用户表。
+
+- **schema_element**
+
+  在模式里创建对象的SQL语句。目前仅支持CREATE TABLE、CREATE VIEW、CREATE INDEX、CREATE PARTITION、CREATE SEQUENCE、CREATE TRIGGER、GRANT子句。
+
+  子命令所创建的对象都被AUTHORIZATION子句指定的用户所拥有。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+> 如果当前搜索路径上的模式中存在同名对象时，需要明确指定引用对象所在的模式。可以通过命令SHOW SEARCH_PATH来查看当前搜索路径上的模式。
+
+## 示例
+
+```sql
+--创建一个角色role1。
+mogdb=# CREATE ROLE role1 IDENTIFIED BY 'xxxxxx';
+
+--为用户role1创建一个同名schema，子命令创建的表films和winners的拥有者为role1。
+mogdb=# CREATE SCHEMA AUTHORIZATION role1
+     CREATE TABLE films (title text, release date, awards text[])
+     CREATE VIEW winners AS
+     SELECT title, release FROM films WHERE awards IS NOT NULL;
+
+--删除schema。
+mogdb=# DROP SCHEMA role1 CASCADE;
+--删除用户。
+mogdb=# DROP USER role1 CASCADE;
+```
+
+## 相关链接
+
+[ALTER SCHEMA](15-ALTER-SCHEMA)，[DROP SCHEMA](91-DROP-SCHEMA)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/57-CREATE-SEQUENCE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/57-CREATE-SEQUENCE.md
new file mode 100644
index 0000000000000000000000000000000000000000..3e80288e1363dc235d94e75f0298412bd0a1d3f3
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/57-CREATE-SEQUENCE.md
@@ -0,0 +1,145 @@
+---
+title: CREATE SEQUENCE
+summary: CREATE SEQUENCE
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE SEQUENCE
+
+## 功能描述
+
+CREATE SEQUENCE用于向当前数据库里增加一个新的序列。序列的Owner为创建此序列的用户。
+
+## 注意事项
+
+- Sequence是一个存放等差数列的特殊表。这个表没有实际意义，通常用于为行或者表生成唯一的标识符。
+- 如果给出一个模式名，则该序列就在给定的模式中创建，否则会在当前模式中创建。序列名必须和同一个模式中的其他序列、表、索引、视图或外表的名称不同。
+- 创建序列后，在表中使用序列的nextval()函数和generate_series(1,N)函数对表插入数据，请保证nextval的可调用次数大于等于N+1次，否则会因为generate_series()函数会调用N+1次而导致报错。
+
+## 语法格式
+
+```ebnf+diagram
+CreateSequence ::= CREATE SEQUENCE name [ INCREMENT [ BY ] increment ]
+    [ MINVALUE minvalue | NO MINVALUE | NOMINVALUE ] [ MAXVALUE maxvalue | NO MAXVALUE | NOMAXVALUE]
+    [ START [ WITH ] start ] [ CACHE cache ] [ [ NO ] CYCLE | NOCYCLE ]
+    [ OWNED BY { table_name'.'column_name | NONE } ];
+```
+
+## 参数说明
+
+- **name**
+
+  将要创建的序列名称。
+
+  取值范围: 仅可以使用小写字母（a\~z）、 大写字母（A\~Z），数字和特殊字符“\#”，“_”，“$”的组合。
+
+- **increment**
+
+  指定序列的步长。一个正数将生成一个递增的序列，一个负数将生成一个递减的序列。
+
+  缺省值为1。
+
+- **MINVALUE minvalue | NO MINVALUE| NOMINVALUE**
+
+  执行序列的最小值。如果没有声明minvalue或者声明了NO MINVALUE，则递增序列的缺省值为1，递减序列的缺省值为-263-1。NOMINVALUE等价于NO MINVALUE
+
+- **MAXVALUE maxvalue | NO MAXVALUE| NOMAXVALUE**
+
+  执行序列的最大值。如果没有声明maxvalue或者声明了NO MAXVALUE，则递增序列的缺省值为263-1，递减序列的缺省值为-1。NOMAXVALUE等价于NO MAXVALUE
+
+- **start**
+
+  指定序列的起始值。缺省值：对于递增序列为minvalue，递减序列为maxvalue。
+
+- **cache**
+
+  为了快速访问，而在内存中预先存储序列号的个数。
+
+  缺省值为1，表示一次只能生成一个值，也就是没有缓存。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  > 不建议同时定义cache和maxvalue或minvalue。因为定义cache后不能保证序列的连续性，可能会产生空洞，造成序列号段浪费。
+
+- **CYCLE**
+
+  用于使序列达到maxvalue或者minvalue后可循环并继续下去。
+
+  如果声明了NO CYCLE，则在序列达到其最大值后任何对nextval的调用都会返回一个错误。
+
+  NOCYCLE的作用等价于NO CYCLE。
+
+  缺省值为NO CYCLE。
+
+  若定义序列为CYCLE，则不能保证序列的唯一性。
+
+- **OWNED BY**
+
+  将序列和一个表的指定字段进行关联。这样，在删除那个字段或其所在表的时候会自动删除已关联的序列。关联的表和序列的所有者必须是同一个用户，并且在同一个模式中。需要注意的是，通过指定OWNED BY，仅仅是建立了表的对应列和sequence之间关联关系，并不会在插入数据时在该列上产生自增序列。
+
+  缺省值为OWNED BY NONE，表示不存在这样的关联。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+  > 通过OWNED BY创建的Sequence不建议用于其他表，如果希望多个表共享Sequence，该Sequence不应该从属于特定表。
+
+## 示例
+
+创建一个名为serial的递增序列，从101开始：
+
+```sql
+mogdb=# CREATE SEQUENCE serial
+ START 101
+ CACHE 20;
+```
+
+从序列中选出下一个数字：
+
+```sql
+mogdb=# SELECT nextval('serial');
+ nextval
+ ---------
+      101
+```
+
+从序列中选出下一个数字：
+
+```sql
+mogdb=# SELECT nextval('serial');
+ nextval
+ ---------
+      102
+```
+
+创建与表关联的序列：
+
+```sql
+mogdb=# CREATE TABLE customer_address
+(
+    ca_address_sk             integer               not null,
+    ca_address_id             char(16)              not null,
+    ca_street_number          char(10)                      ,
+    ca_street_name            varchar(60)                   ,
+    ca_street_type            char(15)                      ,
+    ca_suite_number           char(10)                      ,
+    ca_city                   varchar(60)                   ,
+    ca_county                 varchar(30)                   ,
+    ca_state                  char(2)                       ,
+    ca_zip                    char(10)                      ,
+    ca_country                varchar(20)                   ,
+    ca_gmt_offset             decimal(5,2)                  ,
+    ca_location_type          char(20)
+);
+
+mogdb=# CREATE SEQUENCE serial1
+ START 101
+ CACHE 20
+OWNED BY customer_address.ca_address_sk;
+--删除表和序列
+mogdb=# DROP TABLE customer_address;
+mogdb=# DROP SEQUENCE serial cascade;
+mogdb=# DROP SEQUENCE serial1 cascade;
+```
+
+## 相关链接
+
+[DROP SEQUENCE](92-DROP-SEQUENCE)，[ALTER SEQUENCE](16-ALTER-SEQUENCE)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/58-CREATE-SERVER.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/58-CREATE-SERVER.md
new file mode 100644
index 0000000000000000000000000000000000000000..c44ddf130ceefc3834c9957bc002c3eb9b16c448
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/58-CREATE-SERVER.md
@@ -0,0 +1,120 @@
+---
+title: CREATE SERVER
+summary: CREATE SERVER
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE SERVER
+
+## 功能描述
+
+定义一个新的外部服务器。
+
+## 语法格式
+
+```ebnf+diagram
+CreateServer ::= CREATE SERVER server_name
+    FOREIGN DATA WRAPPER fdw_name
+    OPTIONS ( { option_name ' value ' } [, ...] ) ;
+```
+
+## 参数说明
+
+- **server_name**
+
+  server的名称。
+
+  取值范围: 长度必须小于等于63。
+
+- **fdw_name**
+
+  指定外部数据封装器的名称。
+
+  取值范围: oracle_fdw，mysql_fdw，postgres_fdw，file_fdw，mot_fdw。
+
+- **OPTIONS ( { option_name ' value ' } [, …] )**
+
+    这个子句为服务器指定选项。这些选项通常定义该服务器的连接细节， 但是实际的名称和值取决于该服务器的外部数据包装器。
+
+  - oracle_fdw支持的options包括：
+
+    - **dbserver**
+
+        远端Oracle数据库的连接字符串。
+
+    - **isolation_level** （默认值为`serializable`）
+
+        oracle数据库的事务隔离级别。
+
+        取值范围: `serializable`, `read_committed` , `read_only`
+
+  - mysql_fdw支持的options包括：
+
+    - **host** （默认值为 `127.0.0.1`）
+
+        MySQL Server/MariaDB的地址。
+
+    - **port** （默认值为 `3306`）
+
+        MySQL Server/MariaDB侦听的端口号。
+
+  - postgres_fdw支持的options同libpq支持的连接参数一致，可参考[链接字符](6-connection-characters)。需要注意的是，以下几个options不支持设置：
+
+    - **user** 和 **password**
+
+        用户名和密码将在创建user mapping时指定。
+
+    - **client_encoding**
+
+        将自动获取本地server的编码方式并设置该值。
+
+    - **application_name**
+
+        总是设置成`postgres_fdw`。
+
+  - 用于指定外部服务器的各类参数，详细的参数说明如下所示。
+
+    - **encrypt**
+
+      是否对数据进行加密，该参数仅支持type为OBS时设置。默认值为on。
+
+      取值范围:
+
+      - on表示对数据进行加密，使用HTTPS协议通信。
+      - off表示不对数据进行加密，使用HTTP协议通信。
+
+    - **access_key**
+
+        OBS访问协议对应的AK值（OBS云服务界面由用户获取），创建外表时AK值会加密保存到数据库的元数据表中。该参数仅支持type为OBS时设置。
+
+    - **secret_access_key**
+
+        OBS访问协议对应的SK值（OBS云服务界面由用户获取），创建外表时SK值会加密保存到数据库的元数据表中。该参数仅支持type为OBS时设置。
+
+除了libpq支持的连接参数外，还额外提供3个options：
+
+- **use_remote_estimate**
+
+  控制postgres_fdw是否发出EXPLAIN命令以获取运行消耗估算。默认值为false。
+
+- **fdw_startup_cost**
+
+  执行一个外表扫描时的启动耗时估算。这个值通常包含建立连接、远端对请求的分析和生成计划的耗时。默认值为`100`。
+
+- **fdw_typle_cost**
+
+  在远端服务器上对每一个元组进行扫描时的额外消耗。这个值通常表示数据在server间传输的额外消耗。默认值为`0.01`。
+
+## 示例
+
+创建server。
+
+```sql
+mogdb=# create server my_server foreign data wrapper log_fdw;
+CREATE SERVER
+```
+
+## 相关链接
+
+[ALTER SERVER](17-ALTER-SERVER)，[DROP SERVER](93-DROP-SERVER)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/59-CREATE-SYNONYM.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/59-CREATE-SYNONYM.md
new file mode 100644
index 0000000000000000000000000000000000000000..e946e50ae4d1fdce4093ce1451d0790296cd267e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/59-CREATE-SYNONYM.md
@@ -0,0 +1,112 @@
+---
+title: CREATE SYNONYM
+summary: CREATE SYNONYM
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE SYNONYM
+
+## 功能描述
+
+创建一个同义词对象。同义词是数据库对象的别名，用于记录与其他数据库对象名间的映射关系，用户可以使用同义词访问关联的数据库对象。
+
+## 注意事项
+
+- 定义同义词的用户成为其所有者。
+- 若指定模式名称，则同义词在指定模式中创建。否则，在当前模式创建。
+- 支持通过同义词访问的数据库对象包括：表、视图、函数和存储过程。
+- 使用同义词时，用户需要具有对关联对象的相应权限。
+- 支持使用同义词的DML语句包括：SELECT、INSERT、UPDATE、DELETE、EXPLAIN、CALL。
+- 不建议对临时表创建同义词。如果需要创建的话，需要指定同义词的目标临时表的模式名，负责无法正常使用同义词，并且在当前会话结束前执行DROP SYNONYM命令。
+
+## 语法格式
+
+```ebnf+diagram
+CreateSynonym ::= CREATE [ OR REPLACE ] SYNONYM synonym_name
+    FOR object_name;
+```
+
+## 参数说明
+
+- **synonym**
+
+  创建的同义词名字，可以带模式名。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- **object_name**
+
+  关联的对象名字，可以带模式名。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  > object_name可以是不存在的对象名称。
+
+## 示例
+
+```sql
+--创建模式ot。
+mogdb=# CREATE SCHEMA ot;
+
+--创建表ot.t1及其同义词t1。
+mogdb=# CREATE TABLE ot.t1(id int, name varchar2(10));
+mogdb=# CREATE OR REPLACE SYNONYM t1 FOR ot.t1;
+
+--使用同义词t1。
+mogdb=# SELECT * FROM t1;
+mogdb=# INSERT INTO t1 VALUES (1, 'ada'), (2, 'bob');
+mogdb=# UPDATE t1 SET t1.name = 'cici' WHERE t1.id = 2;
+
+--创建同义词v1及其关联视图ot.v_t1。
+mogdb=# CREATE SYNONYM v1 FOR ot.v_t1;
+mogdb=# CREATE VIEW ot.v_t1 AS SELECT * FROM ot.t1;
+
+--使用同义词v1。
+mogdb=# SELECT * FROM v1;
+
+--创建重载函数ot.add及其同义词add。
+mogdb=# CREATE OR REPLACE FUNCTION ot.add(a integer, b integer) RETURNS integer AS
+$$
+SELECT $1 + $2
+$$
+LANGUAGE sql;
+
+mogdb=# CREATE OR REPLACE FUNCTION ot.add(a decimal(5,2), b decimal(5,2)) RETURNS decimal(5,2) AS
+$$
+SELECT $1 + $2
+$$
+LANGUAGE sql;
+
+mogdb=# CREATE OR REPLACE SYNONYM add FOR ot.add;
+
+--使用同义词add。
+mogdb=# SELECT add(1,2);
+mogdb=# SELECT add(1.2,2.3);
+
+--创建存储过程ot.register及其同义词register。
+mogdb=# CREATE PROCEDURE ot.register(n_id integer, n_name varchar2(10))
+SECURITY INVOKER
+AS
+BEGIN
+    INSERT INTO ot.t1 VALUES(n_id, n_name);
+END;
+/
+
+mogdb=# CREATE OR REPLACE SYNONYM register FOR ot.register;
+
+--使用同义词register，调用存储过程。
+mogdb=# CALL register(3,'mia');
+
+--删除同义词。
+mogdb=# DROP SYNONYM t1;
+mogdb=# DROP SYNONYM IF EXISTS v1;
+mogdb=# DROP SYNONYM IF EXISTS add;
+mogdb=# DROP SYNONYM register;
+mogdb=# DROP SCHEMA ot CASCADE;
+```
+
+## 相关链接
+
+[ALTER SYNONYM](19-ALTER-SYNONYM)，[DROP SYNONYM](94-DROP-SYNONYM)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/6-ALTER-FOREIGN-TABLE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/6-ALTER-FOREIGN-TABLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..fb1c04bfc4bd88007886b265c96e5ad1236d455b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/6-ALTER-FOREIGN-TABLE.md
@@ -0,0 +1,118 @@
+---
+title: ALTER FOREIGN TABLE
+summary: ALTER FOREIGN TABLE
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER FOREIGN TABLE
+
+## 功能描述
+
+对外表进行修改。
+
+## 语法格式
+
+```ebnf+diagram
+AlterForeignTable ::= ALTER FOREIGN TABLE [ IF EXISTS ]  table_name
+    OPTIONS ( {[ ADD | SET | DROP ] option ['value']}[, ... ]);
+```
+
+```ebnf+diagram
+AlterForeignTable ::= ALTER FOREIGN TABLE [ IF EXISTS ] table_name
+    ALTER column_name OPTIONS;
+```
+
+## 参数说明
+
+- **table_name**
+
+  需要修改的外表名称。
+
+  取值范围: 已存在的外表名。
+
+- **option**
+
+  改变外表或者外表字段的选项。ADD、SET和DROP指定执行的操作。如果没有显式设置，那么默认为ADD。选项的名字不允许重复（尽管表选项和表字段选项可以有相同的名字）。选项的名称和值也会通过外部数据封装器的类库进行校验。
+
+  oracle_fdw支持的options包括：
+
+  - **table**
+
+    oracle server侧的表名。需要同oracle系统表中记录的表名完全一致，通常是由大写字符组成。
+
+  - **schema**
+
+    表所对应的schema（或owner）。需要与oracle系统表中记录的表名完全一致，通常是由大写字符组成。
+
+  mysql_fdw支持的options包括：
+
+  - **dbname**
+
+    MySQL的database名称。
+
+  - **table_name**
+
+    MySQL侧的表名。
+
+  postgres_fdw支持的options包括：
+
+  - **schema_name**
+
+    远端server的schema名称。如果不指定的话，将使用外表自身的schema名称作为远端的schema名称。
+
+  - **table_name**
+
+    远端server的表名。如果不指定的话，将使用外表自身的表名作为远端的表名。
+
+  - **column_name**
+
+    远端server的表的列名。如果不指定的话，将使用外表自身的列名作为远端的的表的列名。
+
+- file_fdw支持的options包括：
+
+  - filename
+
+    指定要读取的文件，必需的参数，且必须是一个绝对路径名。
+
+  - format
+
+    远端server的文件格式，支持text/csv/binary/fixed四种格式，和COPY语句的FORMAT选项相同。
+
+  - header
+
+    指定的文件是否有标题行，与COPY语句的HEADER选项相同。
+
+  - delimiter
+
+      指定文件的分隔符，与COPY的DELIMITER选项相同。
+
+  - quote
+
+      指定文件的引用字符，与COPY的QUOTE选项相同。
+
+  - escape
+
+      指定文件的转义字符，与COPY的ESCAPE选项相同。
+
+  - null
+
+      指定文件的null字符串，与COPY的NULL选项相同。
+
+  - encoding
+
+      指定文件的编码，与COPY的ENCODING选项相同。
+
+  - force_not_null
+
+      这是一个布尔选项。如果为真，则声明字段的值不应该匹配空字符串（也就是， 文件级别null选项）。与COPY的 FORCE_NOT_NULL选项里的字段相同。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** file_fdw更多使用请参见[file_fdw](file_fdw)。
+
+- **value**
+
+  option的新值。
+
+## 相关链接
+
+[CREATE FOREIGN TABLE](47-CREATE-FOREIGN-TABLE)，[DROP FOREIGN TABLE](81-DROP-FOREIGN-TABLE)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/60-CREATE-TABLE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/60-CREATE-TABLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..18d387d951baef0bd3e1f7bfe5a925653721e46d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/60-CREATE-TABLE.md
@@ -0,0 +1,1053 @@
+---
+title: CREATE TABLE
+summary: CREATE TABLE
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE TABLE
+
+## 功能描述
+
+在当前数据库中创建一个新的空白表，该表由命令执行者所有。
+
+## 注意事项
+
+- 列存表支持的数据类型请参考[列存表支持的数据类型](16-data-types-supported-by-column-store-tables)。
+- 列存表不支持数组。
+- 列存表不支持生成列。
+- 列存表不支持创建全局临时表。
+- 创建列存表的数量建议不超过1000个。
+- 如果在建表过程中数据库系统发生故障，系统恢复后可能无法自动清除之前已创建的、大小为0的磁盘文件。此种情况出现概率小，不影响数据库系统的正常运行。
+- 列存表的表级约束只支持PARTIAL CLUSTER KEY、UNIQUE、PRIAMRY KEY，不支持外键等表级约束。
+- 列存表的字段约束只支持NULL、NOT NULL、DEFAULT常量值、UNIQUE和PRIMARY KEY。
+- 列存表支持delta表，受参数enable_delta_store控制是否开启，受参数deltarow_threshold控制进入delta表的阀值。
+- 使用JDBC时，支持通过PrepareStatement对DEFAUTL值进行参数化设置。
+- 每张表的列数最大为1600，具体取决于列的类型，所有列的大小加起来不能超过8192 byte，text、varchar、char等长度可变的类型除外。
+
+## 语法格式
+
+创建表。
+
+```ebnf+diagram
+CreateTable ::= CREATE [ [ GLOBAL | LOCAL ] [ TEMPORARY | TEMP ] | UNLOGGED ] TABLE [ IF NOT EXISTS ] table_name
+    ({ column_name data_type [ compress_mode ] [ COLLATE collation ] [ column_constraint [ ... ] ]
+        | table_constraint
+        | LIKE source_table [ like_option [...] ] }
+        [, ... ])
+    [ WITH ( {storage_parameter = value} [, ... ] ) ]
+    [ ON COMMIT { PRESERVE ROWS | DELETE ROWS | DROP } ]
+    [ COMPRESS | NOCOMPRESS ]
+    [ TABLESPACE tablespace_name ];
+```
+
+- 其中列约束column_constraint为：
+
+  ```ebnf+diagram
+  column_constraint ::= [ CONSTRAINT constraint_name ]
+  { NOT NULL |
+    NULL |
+    CHECK ( expression ) |
+    DEFAULT default_expr |
+    UNIQUE index_parameters |
+    ENCRYPTED WITH ( COLUMN_ENCRYPTION_KEY = column_encryption_key, ENCRYPTION_TYPE = encryption_type_value) |
+    PRIMARY KEY index_parameters |
+    REFERENCES reftable [ ( refcolumn ) ] [ MATCH FULL | MATCH PARTIAL | MATCH SIMPLE ]
+        [ ON DELETE action ] [ ON UPDATE action ] }
+  [ DEFERRABLE | NOT DEFERRABLE | INITIALLY DEFERRED | INITIALLY IMMEDIATE ]
+  ```
+
+- 其中压缩可选项compress_mode为：
+
+  ```ebnf+diagram
+  compress_mode ::= { DELTA | PREFIX | DICTIONARY | NUMSTR | NOCOMPRESS }
+  ```
+
+- 其中表约束table_constraint为：
+
+  ```ebnf+diagram
+  table_constraint ::= [ CONSTRAINT constraint_name ]
+  { CHECK ( expression ) |
+    UNIQUE ( column_name [, ... ] ) index_parameters |
+    PRIMARY KEY ( column_name [, ... ] ) index_parameters |
+    FOREIGN KEY ( column_name [, ... ] ) REFERENCES reftable [ (refcolumn [, ... ] ) ]
+        [ MATCH FULL | MATCH PARTIAL | MATCH SIMPLE ] [ ON DELETE action ] [ ON UPDATE action ] |
+    PARTIAL CLUSTER KEY ( column_name [, ... ] ) }
+  [ DEFERRABLE | NOT DEFERRABLE | INITIALLY DEFERRED | INITIALLY IMMEDIATE ]
+  ```
+
+- 其中like选项like_option为：
+
+  ```ebnf+diagram
+  like_option ::= { INCLUDING | EXCLUDING } { DEFAULTS | GENERATED | CONSTRAINTS | INDEXES | STORAGE | COMMENTS | PARTITION | RELOPTIONS | ALL }
+  ```
+
+- 其中索引参数index_parameters为：
+
+  ```ebnf+diagram
+  index_parameters ::= [ WITH ( {storage_parameter = value} [, ... ] ) ]
+  [ USING INDEX TABLESPACE tablespace_name ]
+  ```
+
+## 参数说明
+
+- **UNLOGGED**
+
+  如果指定此关键字，则创建的表为非日志表。在非日志表中写入的数据不会被写入到预写日志中，这样就会比普通表快很多。但是非日志表在冲突、执行操作系统重启、强制重启、切断电源操作或异常关机后会被自动截断，会造成数据丢失的风险。非日志表中的内容也不会被复制到备服务器中。在非日志表中创建的索引也不会被自动记录。
+
+  使用场景：非日志表不能保证数据的安全性，用户应该在确保数据已经做好备份的前提下使用，例如系统升级时进行数据的备份。
+
+  故障处理：当异常关机等操作导致非日志表上的索引发生数据丢失时，用户应该对发生错误的索引进行重建。
+
+- **GLOBAL | LOCAL**
+
+  创建临时表时可以在TEMP或TEMPORARY前指定GLOBAL或LOCAL关键字。如果指定GLOBAL关键字，MogDB会创建全局临时表，否则MogDB会创建本地临时表。
+
+- **TEMPORARY | TEMP**
+
+  如果指定TEMP或TEMPORARY关键字，则创建的表为临时表。临时表分为全局临时表和本地临时表两种类型。创建临时表时如果指定GLOBAL关键字则为全局临时表，否则为本地临时表。
+
+  全局临时表的元数据对所有会话可见，会话结束后元数据继续存在。会话与会话之间的用户数据、索引和统计信息相互隔离，每个会话只能看到和更改自己提交的数据。全局临时表有两种模式：一种是基于会话级别的(ON COMMIT PRESERVE ROWS)，当会话结束时自动清空用户数据；一种是基于事务级别的(ON COMMIT DELETE ROWS)，当执行commit或rollback时自动清空用户数据。建表时如果没有指定ON COMMIT选项，则缺省为会话级别。与本地临时表不同，全局临时表建表时可以指定非pg_temp_开头的schema。
+
+  本地临时表只在当前会话可见，本会话结束后会自动删除。因此，在除当前会话连接的数据库节点故障时，仍然可以在当前会话上创建和使用临时表。由于临时表只在当前会话创建，对于涉及对临时表操作的DDL语句，会产生DDL失败的报错。因此，建议DDL语句中不要对临时表进行操作。TEMP和TEMPORARY等价。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+  >
+  > - 本地临时表通过每个会话独立的以pg_temp开头的schema来保证只对当前会话可见，因此，不建议用户在日常操作中手动删除以pg_temp，pg_toast_temp开头的schema。
+  > - 如果建表时不指定TEMPORARY/TEMP关键字，而指定表的schema为当前会话的pg_temp_开头的schema，则此表会被创建为临时表。
+  > - ALTER/DROP全局临时表和索引，如果其它会话正在使用它，禁止操作（ALTER INDEX index_name REBUILD除外）。
+  > - 全局临时表的DDL只会影响当前会话的用户数据和索引。例如truncate、reindex、analyze只对当前会话有效。
+  > - 全局临时表功能可以通过设置GUC参数max_active_global_temporary_table控制是否启用。如果max_active_global_temporary_table=0，关闭全局临时表功能。
+  > - 临时表只对当前会话可见，因此不支持与\parallel on并行执行一起使用。
+  > - \\parallel on临时表不支持主备切换。
+
+- **IF NOT EXISTS**
+
+  如果已经存在相同名称的表，不会报出错误，而会发出通知，告知通知此表已存在。
+
+- **table_name**
+
+  要创建的表名。
+
+- **column_name**
+
+  新表中要创建的字段名。
+
+- **data_type**
+
+  字段的数据类型。
+
+- **compress_mode**
+
+  表字段的压缩选项。该选项指定表字段优先使用的压缩算法。
+
+  取值范围: DELTA、PREFIX、DICTIONARY、NUMSTR、NOCOMPRESS
+
+- **COLLATE collation**
+
+  COLLATE子句指定列的排序规则（该列必须是可排列的数据类型）。如果没有指定，则使用默认的排序规则。排序规则可以使用“select * from pg_collation;”命令从pg_collation系统表中查询，默认的排序规则为查询结果中以default开始的行。
+
+- **LIKE source_table [ like_option … ]**
+
+  LIKE子句声明一个表，新表自动从这个表中继承所有字段名及其数据类型和非空约束。
+
+  新表与源表之间在创建动作完毕之后是完全无关的。在源表做的任何修改都不会传播到新表中，并且也不可能在扫描源表的时候包含新表的数据。
+
+  被复制的列和约束并不使用相同的名称进行融合。如果明确的指定了相同的名称或者在另外一个LIKE子句中，将会报错。
+
+  - 源表上的字段缺省表达式只有在指定INCLUDING DEFAULTS时，才会复制到新表中。缺省是不包含缺省表达式的，即新表中的所有字段的缺省值都是NULL。
+  - 源表上的CHECK约束仅在指定INCLUDING CONSTRAINTS时，会复制到新表中，而其他类型的约束永远不会复制到新表中。非空约束总是复制到新表中。此规则同时适用于表约束和列约束。
+  - 如果指定了INCLUDING INDEXES，则源表上的索引也将在新表上创建，默认不建立索引。
+  - 如果指定了INCLUDING STORAGE，则复制列的STORAGE设置会复制到新表中，默认情况下不包含STORAGE设置。
+  - 如果指定了INCLUDING COMMENTS，则源表列、约束和索引的注释会复制到新表中。默认情况下，不复制源表的注释。
+  - 如果指定了INCLUDING PARTITION，则源表的分区定义会复制到新表中，同时新表将不能再使用PARTITION BY子句。默认情况下，不拷贝源表的分区定义。如果源表上带有索引，可以使用INCLUDING PARTITION INCLUDING INDEXES语法实现。如果对分区表只使用INCLUDING INDEXES，目标表定义将是普通表，但是索引是分区索引，最后结果会报错，因为普通表不支持分区索引。
+  - 如果指定了INCLUDING RELOPTIONS，则源表的存储参数（即源表的WITH子句）会复制到新表中。默认情况下，不复制源表的存储参数。
+  - INCLUDING ALL包含了INCLUDING DEFAULTS、INCLUDING CONSTRAINTS、INCLUDING INDEXES、INCLUDING STORAGE、INCLUDING COMMENTS、INCLUDING PARTITION和INCLUDING RELOPTIONS的内容。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+  >
+  > - 如果源表包含serial、bigserial、smallserial类型，或者源表字段的默认值是sequence，且sequence属于源表（通过CREATE SEQUENCE … OWNED BY创建），这些Sequence不会关联到新表中，新表中会重新创建属于自己的sequence。这和之前版本的处理逻辑不同。如果用户希望源表和新表共享Sequence，需要首先创建一个共享的Sequence（避免使用OWNED BY），并配置为源表字段默认值，这样创建的新表会和源表共享该Sequence。
+  > - 不建议将其他表私有的Sequence配置为源表字段的默认值，尤其是其他表只分布在特定的NodeGroup上，这可能导致CREATE TABLE … LIKE执行失败。另外，如果源表配置其他表私有的Sequence，当该表删除时Sequence也会连带删除，这样源表的Sequence将不可用。如果用户希望多个表共享Sequence，建议创建共享的Sequence。
+  > - 对于分区表EXCLUDING，需要配合INCLUDING ALL使用，如INCLUDING ALL EXCLUDING DEFAULTS，除源分区表的DEFAULTS，其它全包含。
+
+- **WITH ( { storage_parameter = value } [, … ] )**
+
+  这个子句为表或索引指定一个可选的存储参数。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 使用任意精度类型Numeric定义列时，建议指定精度p以及刻度s。在不指定精度和刻度时，会按输入的显示出来。
+
+  参数的详细描述如下所示。
+
+  - FILLFACTOR
+
+    一个表的填充因子（fillfactor）是一个介于10和100之间的百分数。100（完全填充）是默认值。如果指定了较小的填充因子，INSERT操作仅按照填充因子指定的百分率填充表页。每个页上的剩余空间将用于在该页上更新行，这就使得UPDATE有机会在同一页上放置同一条记录的新版本，这比把新版本放置在其他页上更有效。对于一个从不更新的表将填充因子设为100是最佳选择，但是对于频繁更新的表，选择较小的填充因子则更加合适。该参数对于列存表没有意义。
+
+    取值范围: 10~100
+
+  - ORIENTATION
+
+    指定表数据的存储方式，即行存方式、列存方式、ORC格式的方式，该参数设置成功后就不再支持修改。
+
+    取值范围:
+
+    - ROW，表示表的数据将以行式存储。
+
+        行存储适合于OLTP业务，适用于点查询或者增删操作较多的场景。
+
+    - COLUMN，表示表的数据将以列式存储。
+
+        列存储适合于数据仓库业务，此类型的表上会做大量的汇聚计算，且涉及的列操作较少。
+
+    默认值：
+
+    若指定表空间为普通表空间，默认值为ROW。
+
+  - STORAGE_TYPE
+
+    指定存储引擎类型，该参数设置成功后就不再支持修改。
+
+    取值范围:
+
+    - USTORE，表示表支持Inplace-Update存储引擎。
+    - ASTORE，表示表支持Append-Only存储引擎。
+
+    默认值：
+
+    不指定表时，默认是Append-Only存储。
+
+  - COMPRESSION <a id = 'COMPRESSION'> </a>
+
+    指定表数据的压缩级别，它决定了表数据的压缩比以及压缩时间。一般来讲，压缩级别越高，压缩比也越大，压缩时间也越长；反之亦然。实际压缩比取决于加载的表数据的分布特征。MogDB 2.1版本之后支持行存表压缩。
+
+    取值范围:
+
+    列存表的有效值为YES/NO/LOW/MIDDLE/HIGH，默认值为LOW。
+
+  - COMPRESSLEVEL
+
+    指定表数据同一压缩级别下的不同压缩水平，它决定了同一压缩级别下表数据的压缩比以及压缩时间。对同一压缩级别进行了更加详细的划分，为用户选择压缩比和压缩时间提供了更多的空间。总体来讲，此值越大，表示同一压缩级别下压缩比越大，压缩时间越长；反之亦然。
+
+    取值范围: 0~3，默认值为0。
+
+  - MAX_BATCHROW
+
+    指定了在数据加载过程中一个存储单元可以容纳记录的最大数目。该参数只对列存表有效。
+
+    取值范围: 10000~60000，默认60000。
+
+  - PARTIAL_CLUSTER_ROWS
+
+    指定了在数据加载过程中进行将局部聚簇存储的记录数目。该参数只对列存表有效。
+
+    取值范围: 大于等于MAX_BATCHROW，建议取值为MAX_BATCHROW的整数倍。
+
+  - DELTAROW_THRESHOLD
+
+    指定列存表导入时小于多少行的数据进入delta表，只在GUC参数enable_delta_store开启时生效。该参数只对列存表有效。
+
+    取值范围: 0～9999，默认值为100
+
+  - VERSION
+
+    指定ORC存储格式的版本。
+
+    取值范围: 0.12，目前支持ORC 0.12格式，后续会随着ORC格式的发展，支持更多格式。
+
+    默认值：0.12
+
+  - segment
+
+    使用段页式的方式存储。本参数仅支持行存表。不支持列存表、临时表、unlog表。不支持ustore存储引擎。
+
+    取值范围: on/off
+
+    默认值：off
+
+  - dek_cipher
+
+    透明数据加密密钥的密文。当开启enable_tde选项时会自动申请创建，用户不可单独指定。通过密钥轮转功能可以对密钥进行更新。
+
+    取值范围: 字符串。
+
+    默认值：不开启加密时默认为空。
+
+- **ON COMMIT { PRESERVE ROWS | DELETE ROWS | DROP }**
+
+  ON COMMIT选项决定在事务中执行创建临时表操作，当事务提交时，此临时表的后续操作。有以下三个选项，当前支持PRESERVE ROWS和DELETE ROWS选项。
+
+  - PRESERVE ROWS（缺省值）：提交时不对临时表做任何操作，临时表及其表数据保持不变。
+  - DELETE ROWS：提交时删除临时表中数据。
+  - DROP：提交时删除此临时表。只支持本地临时表，不支持全局临时表。
+
+- **COMPRESS | NOCOMPRESS**
+
+  创建新表时，需要在CREATE TABLE语句中指定关键字COMPRESS，这样，当对该表进行批量插入时就会触发压缩特性。该特性会在页范围内扫描所有元组数据，生成字典、压缩元组数据并进行存储。指定关键字NOCOMPRESS则不对表进行压缩。
+
+  缺省值：NOCOMPRESS，即不对元组数据进行压缩。
+
+- **TABLESPACE tablespace_name**
+
+  创建新表时指定此关键字，表示新表将要在指定表空间内创建。如果没有声明，将使用默认表空间。
+
+- **CONSTRAINT constraint_name**
+
+  列约束或表约束的名称。可选的约束子句用于声明约束，新行或者更新的行必须满足这些约束才能成功插入或更新。
+
+  定义约束有两种方法：
+
+  - 列约束：作为一个列定义的一部分，仅影响该列。
+  - 表约束：不和某个列绑在一起，可以作用于多个列。
+
+- **NOT NULL**
+
+  字段值不允许为NULL。
+
+- **NULL**
+
+  字段值允许为NULL ，这是缺省值。
+
+  这个子句只是为和非标准SQL数据库兼容。不建议使用。
+
+- **CHECK ( expression )**
+
+  CHECK约束声明一个布尔表达式，每次要插入的新行或者要更新的行的新值必须使表达式结果为真或未知才能成功，否则会抛出一个异常并且不会修改数据库。
+
+  声明为字段约束的检查约束应该只引用该字段的数值，而在表约束里出现的表达式可以引用多个字段。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** expression表达式中，如果存在“&lt;&gt;NULL”或“！=NULL”，这种写法是无效的，需要写成“is NOT NULL”。
+
+- **DEFAULT default_expr**
+
+  DEFAULT子句给字段指定缺省值。该数值可以是任何不含变量的表达式(不允许使用子查询和对本表中的其他字段的交叉引用)。缺省表达式的数据类型必须和字段类型匹配。
+
+  缺省表达式将被用于任何未声明该字段数值的插入操作。如果没有指定缺省值则缺省值为NULL 。
+
+- **UNIQUE index_parameters**
+
+  **UNIQUE ( column_name [, … ] ) index_parameters**
+
+  UNIQUE约束表示表里的一个字段或多个字段的组合必须在全表范围内唯一。
+
+  对于唯一约束，NULL被认为是互不相等的。
+
+- **PRIMARY KEY index_parameters**
+
+  **PRIMARY KEY ( column_name [, … ] ) index_parameters**
+
+  主键约束声明表中的一个或者多个字段只能包含唯一的非NULL值。
+
+  一个表只能声明一个主键。
+
+- **REFERENCES reftable [ ( refcolum ) ] [ MATCH matchtype ] [ ON DELETE action ] [ ON UPDATE action ] (column constraint)**
+
+  **FOREIGN KEY ( column_name [, … ] ) REFERENCES reftable [ ( refcolumn [, … ] ) ] [ MATCH matchtype ] [ ON DELETE action ] [ ON UPDATE action ] (table constraint)**
+
+  外键约束要求新表中一列或多列构成的组应该只包含、匹配被参考表中被参考字段值。若省略refcolum，则将使用reftable的主键。被参考列应该是被参考表中的唯一字段或主键。外键约束不能被定义在临时表和永久表之间。
+
+  参考字段与被参考字段之间存在三种类型匹配，分别是：
+
+  - MATCH FULL：不允许一个多字段外键的字段为NULL，除非全部外键字段都是NULL。
+  - MATCH SIMPLE（缺省）：允许任意外键字段为NULL。
+  - MATCH PARTIAL：目前暂不支持。
+
+  另外，当被参考表中的数据发生改变时，某些操作也会在新表对应字段的数据上执行。ON DELETE子句声明当被参考表中的被参考行被删除时要执行的操作。ON UPDATE子句声明当被参考表中的被参考字段数据更新时要执行的操作。对于ON DELETE子句、ON UPDATE子句的可能动作：
+
+  - NO ACTION（缺省）：删除或更新时，创建一个表明违反外键约束的错误。若约束可推迟，且若仍存在任何引用行，那这个错误将会在检查约束的时候产生。
+  - RESTRICT：删除或更新时，创建一个表明违反外键约束的错误。与NO ACTION相同，只是动作不可推迟。
+  - CASCADE：删除新表中任何引用了被删除行的行，或更新新表中引用行的字段值为被参考字段的新值。
+  - SET NULL：设置引用字段为NULL。
+  - SET DEFAULT：设置引用字段为它们的缺省值。
+
+- **DEFERRABLE | NOT DEFERRABLE**
+
+  这两个关键字设置该约束是否可推迟。一个不可推迟的约束将在每条命令之后马上检查。可推迟约束可以推迟到事务结尾使用SET CONSTRAINTS命令检查。缺省是NOT DEFERRABLE。目前，UNIQUE约束、主键约束、外键约束可以接受这个子句。所有其他约束类型都是不可推迟的。
+
+- **PARTIAL CLUSTER KEY**
+
+  局部聚簇存储，列存表导入数据时按照指定的列(单列或多列)，进行局部排序。
+
+- **INITIALLY IMMEDIATE | INITIALLY DEFERRED**
+
+  如果约束是可推迟的，则这个子句声明检查约束的缺省时间。
+
+  - 如果约束是INITIALLY IMMEDIATE（缺省），则在每条语句执行之后就立即检查它；
+  - 如果约束是INITIALLY DEFERRED ，则只有在事务结尾才检查它。
+
+  约束检查的时间可以用SET CONSTRAINTS命令修改。
+
+- **USING INDEX TABLESPACE tablespace_name**
+
+  为UNIQUE或PRIMARY KEY约束相关的索引声明一个表空间。如果没有提供这个子句，这个索引将在default_tablespace中创建，如果default_tablespace为空，将使用数据库的缺省表空间。
+
+- **ENCRYPTION_TYPE = encryption_type_value**
+
+  为ENCRYPTED WITH约束中的加密类型，encryption_type_value的值为[ DETERMINISTIC | RANDOMIZED ]
+
+## 示例
+
+```sql
+--创建简单的表。
+mogdb=# CREATE TABLE tpcds.warehouse_t1
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2)
+);
+
+mogdb=# CREATE TABLE tpcds.warehouse_t2
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60),
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2)
+);
+--创建表，并指定W_STATE字段的缺省值为GA。
+mogdb=# CREATE TABLE tpcds.warehouse_t3
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)           DEFAULT 'GA',
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2)
+);
+
+--创建表，并在事务结束时检查W_WAREHOUSE_NAME字段是否有重复。
+mogdb=# CREATE TABLE tpcds.warehouse_t4
+(
+    W_WAREHOUSE_SK            INTEGER                NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)               NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)   UNIQUE DEFERRABLE,
+    W_WAREHOUSE_SQ_FT         INTEGER                        ,
+    W_STREET_NUMBER           CHAR(10)                       ,
+    W_STREET_NAME             VARCHAR(60)                    ,
+    W_STREET_TYPE             CHAR(15)                       ,
+    W_SUITE_NUMBER            CHAR(10)                       ,
+    W_CITY                    VARCHAR(60)                    ,
+    W_COUNTY                  VARCHAR(30)                    ,
+    W_STATE                   CHAR(2)                        ,
+    W_ZIP                     CHAR(10)                       ,
+    W_COUNTRY                 VARCHAR(20)                    ,
+    W_GMT_OFFSET              DECIMAL(5,2)
+);
+--创建一个带有70%填充因子的表。
+mogdb=# CREATE TABLE tpcds.warehouse_t5
+(
+    W_WAREHOUSE_SK            INTEGER                NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)               NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                    ,
+    W_WAREHOUSE_SQ_FT         INTEGER                        ,
+    W_STREET_NUMBER           CHAR(10)                       ,
+    W_STREET_NAME             VARCHAR(60)                    ,
+    W_STREET_TYPE             CHAR(15)                       ,
+    W_SUITE_NUMBER            CHAR(10)                       ,
+    W_CITY                    VARCHAR(60)                    ,
+    W_COUNTY                  VARCHAR(30)                    ,
+    W_STATE                   CHAR(2)                        ,
+    W_ZIP                     CHAR(10)                       ,
+    W_COUNTRY                 VARCHAR(20)                    ,
+    W_GMT_OFFSET              DECIMAL(5,2),
+    UNIQUE(W_WAREHOUSE_NAME) WITH(fillfactor=70)
+);
+
+--或者用下面的语法。
+mogdb=# CREATE TABLE tpcds.warehouse_t6
+(
+    W_WAREHOUSE_SK            INTEGER                NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)               NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)              UNIQUE,
+    W_WAREHOUSE_SQ_FT         INTEGER                        ,
+    W_STREET_NUMBER           CHAR(10)                       ,
+    W_STREET_NAME             VARCHAR(60)                    ,
+    W_STREET_TYPE             CHAR(15)                       ,
+    W_SUITE_NUMBER            CHAR(10)                       ,
+    W_CITY                    VARCHAR(60)                    ,
+    W_COUNTY                  VARCHAR(30)                    ,
+    W_STATE                   CHAR(2)                        ,
+    W_ZIP                     CHAR(10)                       ,
+    W_COUNTRY                 VARCHAR(20)                    ,
+    W_GMT_OFFSET              DECIMAL(5,2)
+) WITH(fillfactor=70);
+
+--创建表，并指定该表数据不写入预写日志。
+mogdb=# CREATE UNLOGGED TABLE tpcds.warehouse_t7
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2)
+);
+
+--创建临时表。
+mogdb=# CREATE TEMPORARY TABLE warehouse_t24
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2)
+);
+
+--创建本地临时表，并指定提交事务时删除该临时表数据。
+mogdb=# CREATE TEMPORARY TABLE warehouse_t25
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2)
+) ON COMMIT DELETE ROWS;
+
+--创建全局临时表，并指定会话结束时删除该临时表数据。
+mogdb=# CREATE GLOBAL TEMPORARY TABLE gtt1
+(
+    ID                        INTEGER               NOT NULL,
+    NAME                      CHAR(16)              NOT NULL,
+    ADDRESS                   VARCHAR(50)                   ,
+    POSTCODE                  CHAR(6)
+) ON COMMIT PRESERVE ROWS;
+
+--创建表时，不希望因为表已存在而报错。
+mogdb=# CREATE TABLE IF NOT EXISTS tpcds.warehouse_t8
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2)
+);
+
+--创建普通表空间。
+mogdb=# CREATE TABLESPACE DS_TABLESPACE1 RELATIVE LOCATION 'tablespace/tablespace_1';
+--创建表时，指定表空间。
+mogdb=# CREATE TABLE tpcds.warehouse_t9
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2)
+) TABLESPACE DS_TABLESPACE1;
+
+--创建表时，单独指定W_WAREHOUSE_NAME的索引表空间。
+mogdb=# CREATE TABLE tpcds.warehouse_t10
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)           UNIQUE USING INDEX TABLESPACE DS_TABLESPACE1,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2)
+);
+--创建一个有主键约束的表。
+mogdb=# CREATE TABLE tpcds.warehouse_t11
+(
+    W_WAREHOUSE_SK            INTEGER            PRIMARY KEY,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2)
+);
+
+---或是用下面的语法，效果完全一样。
+mogdb=# CREATE TABLE tpcds.warehouse_t12
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2),
+    PRIMARY KEY(W_WAREHOUSE_SK)
+);
+
+--或是用下面的语法，指定约束的名称。
+mogdb=# CREATE TABLE tpcds.warehouse_t13
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2),
+    CONSTRAINT W_CSTR_KEY1 PRIMARY KEY(W_WAREHOUSE_SK)
+);
+
+--创建一个有复合主键约束的表。
+mogdb=# CREATE TABLE tpcds.warehouse_t14
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2),
+    CONSTRAINT W_CSTR_KEY2 PRIMARY KEY(W_WAREHOUSE_SK, W_WAREHOUSE_ID)
+);
+--创建列存表。
+mogdb=# CREATE TABLE tpcds.warehouse_t15
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2)
+) WITH (ORIENTATION = COLUMN);
+
+--创建局部聚簇存储的列存表。
+mogdb=# CREATE TABLE tpcds.warehouse_t16
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2),
+    PARTIAL CLUSTER KEY(W_WAREHOUSE_SK, W_WAREHOUSE_ID)
+) WITH (ORIENTATION = COLUMN);
+
+--定义一个带压缩的列存表。
+mogdb=# CREATE TABLE tpcds.warehouse_t17
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2)
+) WITH (ORIENTATION = COLUMN, COMPRESSION=HIGH);
+
+--定义一个带压缩的行存表。
+mogdb=# CREATE TABLE table_3213
+(
+  c_w_id         integer        not null,
+  c_d_id         integer        not null,
+  c_id           integer        not null,
+  c_discount     decimal(4,4),
+  c_credit       char(2),
+  c_last         varchar(16),
+  c_first        varchar(16),
+  c_credit_lim   decimal(12,2),
+  c_balance      decimal(12,2),
+  c_ytd_payment  decimal(12,2),
+  c_payment_cnt  integer,
+  c_delivery_cnt integer,
+  c_street_1     varchar(20),
+  c_street_2     varchar(20),
+  c_city         varchar(20),
+  c_state        char(2),
+  c_zip          char(9),
+  c_phone        char(16),
+  c_since        timestamp,
+  c_middle       char(2),
+  c_data         varchar(500)
+) WITH (COMPRESSION = YES);
+
+--创建行压缩表时，指定列的mode。
+mogdb=# CREATE TABLE compress_18
+(
+  a00 int DELTA,
+  a01 int DICTIONARY,
+  a02 int NOCOMPRESS,
+  a03 varchar(100) PREFIX,
+  a04 int
+) WITH (COMPRESSION = YES);
+
+--对于通过WITH (COMPRESSION = YES)所创建的行压缩表，或者普通表通过SET COMPRESS改过之后的行压缩表，新增列可以通过下面的方式指定新增列的mode。
+mogdb=# ALTER TABLE test1 ADD COLUMN al char(5) PREFIX;
+
+--定义一个检查列约束。
+mogdb=# CREATE TABLE tpcds.warehouse_t19
+(
+    W_WAREHOUSE_SK            INTEGER               PRIMARY KEY CHECK (W_WAREHOUSE_SK > 0),
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)           CHECK (W_WAREHOUSE_NAME IS NOT NULL),
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2)
+);
+
+mogdb=# CREATE TABLE tpcds.warehouse_t20
+(
+    W_WAREHOUSE_SK            INTEGER               PRIMARY KEY,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)           CHECK (W_WAREHOUSE_NAME IS NOT NULL),
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2),
+    CONSTRAINT W_CONSTR_KEY2 CHECK(W_WAREHOUSE_SK > 0 AND W_WAREHOUSE_NAME IS NOT NULL)
+);
+
+--创建一个有外键约束的表。
+mogdb=# CREATE TABLE tpcds.city_t23
+(
+    W_CITY            VARCHAR(60)                PRIMARY KEY,
+    W_ADDRESS       TEXT
+);
+mogdb=# CREATE TABLE tpcds.warehouse_t23
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)           REFERENCES tpcds.city_t23(W_CITY),
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2)
+);
+
+--或是用下面的语法，效果完全一样。
+mogdb=# CREATE TABLE tpcds.warehouse_t23
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2)                  ,
+    FOREIGN KEY(W_CITY) REFERENCES tpcds.city_t23(W_CITY)
+);
+
+--或是用下面的语法，指定约束的名称。
+mogdb=# CREATE TABLE tpcds.warehouse_t23
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER                       ,
+    W_STREET_NUMBER           CHAR(10)                      ,
+    W_STREET_NAME             VARCHAR(60)                   ,
+    W_STREET_TYPE             CHAR(15)                      ,
+    W_SUITE_NUMBER            CHAR(10)                      ,
+    W_CITY                    VARCHAR(60)                   ,
+    W_COUNTY                  VARCHAR(30)                   ,
+    W_STATE                   CHAR(2)                       ,
+    W_ZIP                     CHAR(10)                      ,
+    W_COUNTRY                 VARCHAR(20)                   ,
+    W_GMT_OFFSET              DECIMAL(5,2)                  ,
+    CONSTRAINT W_FORE_KEY1 FOREIGN KEY(W_CITY) REFERENCES tpcds.city_t23(W_CITY)
+);
+
+--向tpcds.warehouse_t19表中增加一个varchar列。
+mogdb=# ALTER TABLE tpcds.warehouse_t19 ADD W_GOODS_CATEGORY varchar(30);
+
+--给tpcds.warehouse_t19表增加一个检查约束。
+mogdb=# ALTER TABLE tpcds.warehouse_t19 ADD CONSTRAINT W_CONSTR_KEY4 CHECK (W_STATE IS NOT NULL);
+
+--在一个操作中改变两个现存字段的类型。
+mogdb=# ALTER TABLE tpcds.warehouse_t19
+    ALTER COLUMN W_GOODS_CATEGORY TYPE varchar(80),
+    ALTER COLUMN W_STREET_NAME TYPE varchar(100);
+
+--此语句与上面语句等效。
+mogdb=# ALTER TABLE tpcds.warehouse_t19 MODIFY (W_GOODS_CATEGORY varchar(30), W_STREET_NAME varchar(60));
+
+--给一个已存在字段添加非空约束。
+mogdb=# ALTER TABLE tpcds.warehouse_t19 ALTER COLUMN W_GOODS_CATEGORY SET NOT NULL;
+
+--移除已存在字段的非空约束。
+mogdb=# ALTER TABLE tpcds.warehouse_t19 ALTER COLUMN W_GOODS_CATEGORY DROP NOT NULL;
+
+--如果列存表中还未指定局部聚簇，向在一个列存表中添加局部聚簇列。
+mogdb=# ALTER TABLE tpcds.warehouse_t17 ADD PARTIAL CLUSTER KEY(W_WAREHOUSE_SK);
+
+--查看约束的名称，并删除一个列存表中的局部聚簇列。
+mogdb=# \d+ tpcds.warehouse_t17
+                              Table "tpcds.warehouse_t17"
+      Column       |         Type          | Modifiers | Storage  | Stats target | Description
+-------------------+-----------------------+-----------+----------+--------------+-------------
+ w_warehouse_sk    | integer               | not null  | plain    |              |
+ w_warehouse_id    | character(16)         | not null  | extended |              |
+ w_warehouse_name  | character varying(20) |           | extended |              |
+ w_warehouse_sq_ft | integer               |           | plain    |              |
+ w_street_number   | character(10)         |           | extended |              |
+ w_street_name     | character varying(60) |           | extended |              |
+ w_street_type     | character(15)         |           | extended |              |
+ w_suite_number    | character(10)         |           | extended |              |
+ w_city            | character varying(60) |           | extended |              |
+ w_county          | character varying(30) |           | extended |              |
+ w_state           | character(2)          |           | extended |              |
+ w_zip             | character(10)         |           | extended |              |
+ w_country         | character varying(20) |           | extended |              |
+ w_gmt_offset      | numeric(5,2)          |           | main     |              |
+Partial Cluster :
+    "warehouse_t17_cluster" PARTIAL CLUSTER KEY (w_warehouse_sk)
+Has OIDs: no
+Location Nodes: ALL DATANODES
+Options: compression=no, version=0.12
+mogdb=# ALTER TABLE tpcds.warehouse_t17 DROP CONSTRAINT warehouse_t17_cluster;
+
+--将表移动到另一个表空间。
+mogdb=# ALTER TABLE tpcds.warehouse_t19 SET TABLESPACE PG_DEFAULT;
+--创建模式joe。
+mogdb=# CREATE SCHEMA joe;
+
+--将表移动到另一个模式中。
+mogdb=# ALTER TABLE tpcds.warehouse_t19 SET SCHEMA joe;
+
+--重命名已存在的表。
+mogdb=# ALTER TABLE joe.warehouse_t19 RENAME TO warehouse_t23;
+
+--从warehouse_t23表中删除一个字段。
+mogdb=# ALTER TABLE joe.warehouse_t23 DROP COLUMN W_STREET_NAME;
+
+--删除表空间、模式joe和模式表warehouse。
+mogdb=# DROP TABLE tpcds.warehouse_t1;
+mogdb=# DROP TABLE tpcds.warehouse_t2;
+mogdb=# DROP TABLE tpcds.warehouse_t3;
+mogdb=# DROP TABLE tpcds.warehouse_t4;
+mogdb=# DROP TABLE tpcds.warehouse_t5;
+mogdb=# DROP TABLE tpcds.warehouse_t6;
+mogdb=# DROP TABLE tpcds.warehouse_t7;
+mogdb=# DROP TABLE tpcds.warehouse_t8;
+mogdb=# DROP TABLE tpcds.warehouse_t9;
+mogdb=# DROP TABLE tpcds.warehouse_t10;
+mogdb=# DROP TABLE tpcds.warehouse_t11;
+mogdb=# DROP TABLE tpcds.warehouse_t12;
+mogdb=# DROP TABLE tpcds.warehouse_t13;
+mogdb=# DROP TABLE tpcds.warehouse_t14;
+mogdb=# DROP TABLE tpcds.warehouse_t15;
+mogdb=# DROP TABLE tpcds.warehouse_t16;
+mogdb=# DROP TABLE tpcds.warehouse_t17;
+mogdb=# DROP TABLE tpcds.warehouse_t18;
+mogdb=# DROP TABLE tpcds.warehouse_t20;
+mogdb=# DROP TABLE tpcds.warehouse_t21;
+mogdb=# DROP TABLE tpcds.warehouse_t22;
+mogdb=# DROP TABLE joe.warehouse_t23;
+mogdb=# DROP TABLE tpcds.warehouse_t24;
+mogdb=# DROP TABLE tpcds.warehouse_t25;
+mogdb=# DROP TABLESPACE DS_TABLESPACE1;
+mogdb=# DROP SCHEMA IF EXISTS joe CASCADE;
+```
+
+## 相关链接
+
+[ALTER TABLE](22-ALTER-TABLE),  [DROP TABLE](95-DROP-TABLE)， [CREATE TABLESPACE](63-CREATE-TABLESPACE)
+
+## 优化建议
+
+- UNLOGGED
+
+  - UNLOGGED表和表上的索引因为数据写入时不通过WAL日志机制，写入速度远高于普通表。因此，可以用于缓冲存储复杂查询的中间结果集，增强复杂查询的性能。
+  - UNLOGGED表无主备机制，在系统故障或异常断点等情况下，会有数据丢失风险，因此，不可用来存储基础数据。
+
+- TEMPORARY | TEMP
+
+- 临时表只在当前会话可见，会话结束后会自动删除。
+
+- LIKE
+
+- 新表自动从这个表中继承所有字段名及其数据类型和非空约束，新表与源表之间在创建动作完毕之后是完全无关的。
+
+- LIKE INCLUDING DEFAULTS
+
+- 源表上的字段缺省表达式只有在指定INCLUDING DEFAULTS时，才会复制到新表中。缺省是不包含缺省表达式的，即新表中的所有字段的缺省值都是NULL。
+
+- LIKE INCLUDING CONSTRAINTS
+
+- 源表上的CHECK约束仅在指定INCLUDING CONSTRAINTS时，会复制到新表中，而其他类型的约束永远不会复制到新表中。非空约束总是复制到新表中。此规则同时适用于表约束和列约束。
+
+- LIKE INCLUDING INDEXES
+
+- 如果指定了INCLUDING INDEXES，则源表上的索引也将在新表上创建，默认不建立索引。
+
+- LIKE INCLUDING STORAGE
+
+- 如果指定了INCLUDING STORAGE，则复制列的STORAGE设置会复制到新表中，默认情况下不包含STORAGE设置。
+
+- LIKE INCLUDING COMMENTS
+
+- 如果指定了INCLUDING COMMENTS，则源表列、约束和索引的注释会复制到新表中。默认情况下，不复制源表的注释。
+
+- LIKE INCLUDING PARTITION
+
+  - 如果指定了INCLUDING PARTITION，则源表的分区定义会复制到新表中，同时新表将不能再使用PARTITION BY子句。默认情况下，不拷贝源表的分区定义。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 列表/哈希分区表暂不支持LIKE INCLUDING PARTITION。
+
+- LIKE INCLUDING RELOPTIONS
+
+- 如果指定了INCLUDING RELOPTIONS，则源表的存储参数（即源表的WITH子句）会复制到新表中。默认情况下，不复制源表的存储参数。
+
+- LIKE INCLUDING ALL
+
+- INCLUDING ALL包含了INCLUDING DEFAULTS、INCLUDING CONSTRAINTS、INCLUDING INDEXES、INCLUDING STORAGE、INCLUDING COMMENTS、INCLUDING PARTITION、INCLUDING RELOPTIONS的内容。
+
+- ORIENTATION ROW
+
+- 创建行存表，行存储适合于OLTP业务，此类型的表上交互事务比较多，一次交互会涉及表中的多个列，用行存查询效率较高。
+
+- ORIENTATION COLUMN
+
+  - 创建列存表，列存储适合于数据仓库业务，此类型的表上会做大量的汇聚计算，且涉及的列操作较少。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/61-CREATE-TABLE-AS.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/61-CREATE-TABLE-AS.md
new file mode 100644
index 0000000000000000000000000000000000000000..88c5e9de7ce26a11b0e8f35330c45478262079d4
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/61-CREATE-TABLE-AS.md
@@ -0,0 +1,161 @@
+---
+title: CREATE TABLE AS
+summary: CREATE TABLE AS
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE TABLE AS
+
+## 功能描述
+
+根据查询结果创建表。
+
+CREATE TABLE AS创建一个表并且用来自SELECT命令的结果填充该表。该表的字段和SELECT输出字段的名称及数据类型相关。不过用户可以通过明确地给出一个字段名称列表来覆盖SELECT输出字段的名称。
+
+CREATE TABLE AS对源表进行一次查询，然后将数据写入新表中，而查询视图结果会根据源表的变化而有所改变。相比之下，每次做查询的时候，视图都重新计算定义它的SELECT语句。
+
+## 注意事项
+
+- 分区表不能采用此方式进行创建。
+- 如果在建表过程中数据库系统发生故障，系统恢复后可能无法自动清除之前已创建的、大小非0的磁盘文件。此种情况出现概率小，不影响数据库系统的正常运行。
+
+## 语法格式
+
+```ebnf+diagram
+CreateTableAs ::= CREATE [ [ GLOBAL | LOCAL ] [ TEMPORARY | TEMP ] | UNLOGGED ] TABLE table_name
+    [ (column_name [, ...] ) ]
+    [ WITH ( {storage_parameter = value} [, ... ] ) ]
+    [ ON COMMIT { PRESERVE ROWS | DELETE ROWS | DROP } ]
+    [ COMPRESS | NOCOMPRESS ]
+    [ TABLESPACE tablespace_name ]
+    AS query
+    [ WITH [ NO ] DATA ];
+```
+
+## 参数说明
+
+- **UNLOGGED**
+
+    指定表为非日志表。在非日志表中写入的数据不会被写入到预写日志中，这样就会比普通表快很多。但是，它也是不安全的，非日志表在冲突或异常关机后会被自动删截。非日志表中的内容也不会被复制到备用服务器中。在该类表中创建的索引也不会被自动记录。
+
+  - 使用场景：非日志表不能保证数据的安全性，用户应该在确保数据已经做好备份的前提下使用，例如系统升级时进行数据的备份。
+  - 故障处理：当异常关机等操作导致非日志表上的索引发生数据丢失时，用户应该对发生错误的索引进行重建。
+
+- **GLOBAL | LOCAL**
+
+  创建临时表时可以在TEMP或TEMPORARY前指定GLOBAL或LOCAL关键字。如果指定GLOBAL关键字，MogDB会创建全局临时表，否则MogDB会创建本地临时表。
+
+- **TEMPORARY | TEMP**
+
+  如果指定TEMP或TEMPORARY关键字，则创建的表为临时表。临时表分为全局临时表和本地临时表两种类型。创建临时表时如果指定GLOBAL关键字则为全局临时表，否则为本地临时表。
+
+  全局临时表的元数据对所有会话可见，会话结束后元数据继续存在。会话与会话之间的用户数据、索引和统计信息相互隔离，每个会话只能看到和更改自己提交的数据。全局临时表有两种模式：一种是基于会话级别的(ON COMMIT PRESERVE ROWS), 当会话结束时自动清空用户数据；一种是基于事务级别的(ON COMMIT DELETE ROWS), 当执行commit或rollback时自动清空用户数据。建表时如果没有指定ON COMMIT选项，则缺省为会话级别。与本地临时表不同，全局临时表建表时可以指定非pg_temp_开头的schema。
+
+  本地临时表只在当前会话可见，本会话结束后会自动删除。因此，在除当前会话连接的数据库节点故障时，仍然可以在当前会话上创建和使用临时表。由于临时表只在当前会话创建，对于涉及对临时表操作的DDL语句，会产生DDL失败的报错。因此，建议DDL语句中不要对临时表进行操作。TEMP和TEMPORARY等价。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+  >
+  > - 本地临时表通过每个会话独立的以pg_temp开头的schema来保证只对当前会话可见，因此，不建议用户在日常操作中手动删除以pg_temp，pg_toast_temp开头的schema。
+  > - 如果建表时不指定TEMPORARY/TEMP关键字，而指定表的schema为当前会话的pg_temp_开头的schema，则此表会被创建为临时表。
+  > - ALTER/DROP全局临时表和索引，如果其它会话正在使用它，禁止操作。
+  > - 全局临时表的DDL只会影响当前会话的用户数据和索引。例如truncate、reindex、analyze只对当前会话有效。
+
+- **table_name**
+
+  要创建的表名。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- **column_name**
+
+  新表中要创建的字段名。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- **WITH ( storage_parameter [= value] [, … ] )**
+
+    这个子句为表或索引指定一个可选的存储参数。参数的详细说明如下所示。
+
+  - FILLFACTOR
+
+    一个表的填充因子（fillfactor）是一个介于10和100之间的百分数。100（完全填充）是默认值。如果指定了较小的填充因子，INSERT操作仅按照填充因子指定的百分率填充表页。每个页上的剩余空间将用于在该页上更新行，这就使得UPDATE有机会在同一页上放置同一条记录的新版本，这比把新版本放置在其他页上更有效。对于一个从不更新的表将填充因子设为100是最佳选择，但是对于频繁更新的表，选择较小的填充因子则更加合适。该参数只对行存表有效。
+
+    取值范围: 10~100
+
+  - ORIENTATION
+
+    取值范围:
+
+    COLUMN：表的数据将以列式存储。
+
+    ROW（缺省值）：表的数据将以行式存储。
+
+  - COMPRESSION
+
+    指定表数据的压缩级别，它决定了表数据的压缩比以及压缩时间。一般来讲，压缩级别越高，压缩比也越大，压缩时间也越长；反之亦然。实际压缩比取决于加载的表数据的分布特征。
+
+    取值范围:
+
+    列存表的有效值为YES/NO/LOW/MIDDLE/HIGH，默认值为LOW。
+
+    行存表不支持压缩。
+
+  - MAX_BATCHROW
+
+    指定了在数据加载过程中一个存储单元可以容纳记录的最大数目。该参数只对列存表有效。
+
+    取值范围: 10000~60000
+
+- **ON COMMIT { PRESERVE ROWS | DELETE ROWS | DROP }**
+
+    ON COMMIT选项决定在事务中执行创建临时表操作，当事务提交时，此临时表的后续操作。有以下三个选项，当前仅支持PRESERVE ROWS和DELETE ROWS选项。
+
+  - PRESERVE ROWS（缺省值）：提交时不对临时表执行任何操作，临时表及其表数据保持不变。
+  - DELETE ROWS：提交时删除临时表中数据。
+  - DROP：提交时删除此临时表。只支持删除本地临时表，不支持删除全局临时表。
+
+- **COMPRESS / NOCOMPRESS**
+
+  创建一个新表时，需要在创建表语句中指定关键字COMPRESS，这样，当对该表进行批量插入时就会触发压缩特性。该特性会在页范围内扫描所有元组数据，生成字典、压缩元组数据并进行存储。指定关键字NOCOMPRESS则不对表进行压缩。行存表不支持压缩。
+
+  缺省值：NOCOMPRESS，即不对元组数据进行压缩。
+
+- **TABLESPACE tablespace_name**
+
+  指定新表将要在tablespace_name表空间内创建。如果没有声明，将使用默认表空间。
+
+- **AS query**
+
+  一个SELECT VALUES命令或者一个运行预备好的SELECT或VALUES查询的EXECUTE命令。
+
+- **[ WITH [ NO ] DATA ]**
+
+  创建表时，是否也插入查询到的数据。默认是要数据，选择“NO”参数时，则不要数据。
+
+## 示例
+
+```SQL
+--创建一个表tpcds.store_returns表。
+mogdb=# CREATE TABLE tpcds.store_returns
+(
+    W_WAREHOUSE_SK            INTEGER               NOT NULL,
+    W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+    sr_item_sk                VARCHAR(20)                   ,
+    W_WAREHOUSE_SQ_FT         INTEGER
+);
+--创建一个表tpcds.store_returns_t1并插入tpcds.store_returns表中sr_item_sk字段中大于16的数值。
+mogdb=# CREATE TABLE tpcds.store_returns_t1 AS SELECT * FROM tpcds.store_returns WHERE sr_item_sk > '4795';
+
+--使用tpcds.store_returns拷贝一个新表tpcds.store_returns_t2。
+mogdb=# CREATE TABLE tpcds.store_returns_t2 AS table tpcds.store_returns;
+
+--删除表。
+mogdb=# DROP TABLE tpcds.store_returns_t1 ;
+mogdb=# DROP TABLE tpcds.store_returns_t2 ;
+mogdb=# DROP TABLE tpcds.store_returns;
+```
+
+## 相关链接
+
+[CREATE TABLE](60-CREATE-TABLE)，[SELECT](125-SELECT)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/62-CREATE-TABLE-PARTITION.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/62-CREATE-TABLE-PARTITION.md
new file mode 100644
index 0000000000000000000000000000000000000000..0fbc4c77f16efc79f56211a0b0fcd29c604d4804
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/62-CREATE-TABLE-PARTITION.md
@@ -0,0 +1,938 @@
+---
+title: CREATE TABLE PARTITION
+summary: CREATE TABLE PARTITION
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE TABLE PARTITION
+
+## 功能描述
+
+创建分区表。分区表是把逻辑上的一张表根据某种方案分成几张物理块进行存储，这张逻辑上的表称之为分区表，物理块称之为分区。分区表是一张逻辑表，不存储数据，数据实际是存储在分区上的。
+
+常见的分区方案有范围分区（Range Partitioning）、间隔分区（Interval Partitioning）、哈希分区（Hash Partitioning）、列表分区（List Partitioning）、数值分区（Value Partition）等。目前行存表支持范围分区、间隔分区、哈希分区、列表分区，列存表仅支持范围分区。
+
+范围分区是根据表的一列或者多列，将要插入表的记录分为若干个范围，这些范围在不同的分区里没有重叠。为每个范围创建一个分区，用来存储相应的数据。
+
+范围分区的分区策略是指记录插入分区的方式。目前范围分区仅支持范围分区策略。
+
+范围分区策略：根据分区键值将记录映射到已创建的某个分区上，如果可以映射到已创建的某一分区上，则把记录插入到对应的分区上，否则给出报错和提示信息。这是最常用的分区策略。
+
+间隔分区是一种特殊的范围分区，相比范围分区，新增间隔值定义，当插入记录找不到匹配的分区时，可以根据间隔值自动创建分区。
+
+间隔分区只支持基于表的一列分区，并且该列只支持TIMESTAMP[(p)] [WITHOUT TIME ZONE]、TIMESTAMP[(p)] [WITH TIME ZONE]、DATE数据类型。
+
+间隔分区策略：根据分区键值将记录映射到已创建的某个分区上，如果可以映射到已创建的某一分区上，则把记录插入到对应的分区上，否则根据分区键值和表定义信息自动创建一个分区，然后将记录插入新分区中，新创建的分区数据范围等于间隔值。
+
+哈希分区是根据表的一列，为每个分区指定模数和余数，将要插入表的记录划分到对应的分区中，每个分区所持有的行都需要满足条件：分区键的值除以为其指定的模数将产生为其指定的余数。
+
+哈希分区策：根据分区键值将记录映射到已创建的某个分区上，如果可以映射到已创建的某一分区上，则把记录插入到对应的分区上，否则返回报错和提示信息。
+
+列表分区是根据表的一列，将要插入表的记录通过每一个分区中出现的键值划分到对应的分区中，这些键值在不同的分区里没有重叠。为每组键值创建一个分区，用来存储相应的数据。
+
+列表分区策略：根据分区键值将记录映射到已创建的某个分区上，如果可以映射到已创建的某一分区上，则把记录插入到对应的分区上，否则给出报错和提示信息。
+
+分区可以提供若干好处：
+
+- 某些类型的查询性能可以得到极大提升。特别是表中访问率较高的行位于一个单独分区或少数几个分区上的情况下。分区可以减少数据的搜索空间，提高数据访问效率。
+- 当查询或更新一个分区的大部分记录时，连续扫描那个分区而不是访问整个表可以获得巨大的性能提升。
+- 如果需要大量加载或者删除的记录位于单独的分区上，则可以通过直接读取或删除那个分区以获得巨大的性能提升，同时还可以避免由于大量DELETE导致的VACUUM超载（仅范围分区）。
+
+## 注意事项
+
+- 唯一约束和主键约束的约束键包含所有分区键将为约束创建LOCAL索引，否则创建GLOBAL索引。
+- 目前哈希分区和列表分区仅支持单列构建分区键，暂不支持多列构建分区键。
+- 只需要有间隔分区表的INSERT权限，往该表INSERT数据时就可以自动创建分区。
+
+## 语法格式
+
+```ebnf+diagram
+CreateTablePartition ::= CREATE TABLE [ IF NOT EXISTS ] partition_table_name
+( [
+    { column_name data_type [ COLLATE collation ] [ column_constraint [ ... ] ]
+    | table_constraint
+    | LIKE source_table [ like_option [...] ] }[, ... ]
+] )
+    [ WITH ( {storage_parameter = value} [, ... ] ) ]
+    [ COMPRESS | NOCOMPRESS ]
+    [ TABLESPACE tablespace_name ]
+     PARTITION BY {
+        {RANGE (partition_key) [ INTERVAL ('interval_expr') [ STORE IN (tablespace_name [, ... ] ) ] ] ( partition_less_than_item [, ... ] )} |
+        {RANGE (partition_key) [ INTERVAL ('interval_expr') [ STORE IN (tablespace_name [, ... ] ) ] ] ( partition_start_end_item [, ... ] )} |
+        {LIST | HASH (partition_key) (PARTITION partition_name [VALUES (list_values_clause)] opt_table_space )}
+    } [ { ENABLE | DISABLE } ROW MOVEMENT ];
+```
+
+- 列约束column_constraint：
+
+  ```ebnf+diagram
+  column_constraint ::= [ CONSTRAINT constraint_name ]
+  { NOT NULL |
+    NULL |
+    CHECK ( expression ) |
+    DEFAULT default_expr |
+    GENERATED ALWAYS AS ( generation_expr ) STORED |
+    UNIQUE index_parameters |
+    PRIMARY KEY index_parameters |
+    REFERENCES reftable [ ( refcolumn ) ] [ MATCH FULL | MATCH PARTIAL | MATCH SIMPLE ]
+        [ ON DELETE action ] [ ON UPDATE action ] }
+  [ DEFERRABLE | NOT DEFERRABLE | INITIALLY DEFERRED | INITIALLY IMMEDIATE ]
+  ```
+
+- 表约束table_constraint：
+
+  ```ebnf+diagram
+  table_constraint ::= [ CONSTRAINT constraint_name ]
+  { CHECK ( expression ) |
+    UNIQUE ( column_name [, ... ] ) index_parameters |
+    PRIMARY KEY ( column_name [, ... ] ) index_parameters |
+    FOREIGN KEY ( column_name [, ... ] ) REFERENCES reftable [ ( refcolumn [, ... ] ) ]
+        [ MATCH FULL | MATCH PARTIAL | MATCH SIMPLE ] [ ON DELETE action ] [ ON UPDATE action ] }
+  [ DEFERRABLE | NOT DEFERRABLE | INITIALLY DEFERRED | INITIALLY IMMEDIATE ]
+  ```
+
+- like选项like_option：
+
+  ```ebnf+diagram
+  like_option ::= { INCLUDING | EXCLUDING } { DEFAULTS | GENERATED | CONSTRAINTS | INDEXES | STORAGE | COMMENTS | RELOPTIONS| ALL }
+  ```
+
+- 索引存储参数index_parameters：
+
+  ```ebnf+diagram
+  index_parameters ::= [ WITH ( {storage_parameter = value} [, ... ] ) ]
+  [ USING INDEX TABLESPACE tablespace_name ]
+  ```
+
+- partition_less_than_item：
+
+  ```ebnf+diagram
+  partition_less_than_item ::= PARTITION partition_name VALUES LESS THAN ( { partition_value | MAXVALUE } ) [TABLESPACE tablespace_name]
+  ```
+
+- partition_start_end_item：
+
+  ```ebnf+diagram
+  partition_start_end_item ::= PARTITION partition_name {
+          {START(partition_value) END (partition_value) EVERY (interval_value)} |
+          {START(partition_value) END ({partition_value | MAXVALUE})} |
+          {START(partition_value)} |
+          {END({partition_value | MAXVALUE})}
+  } [TABLESPACE tablespace_name]
+  ```
+
+## 参数说明
+
+- **IF NOT EXISTS**
+
+  如果已经存在相同名称的表，不会抛出一个错误，而会发出一个通知，告知表关系已存在。
+
+- **partition_table_name**
+
+  分区表的名称。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- **column_name**
+
+  新表中要创建的字段名。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- **data_type**
+
+  字段的数据类型。
+
+- **COLLATE collation**
+
+  COLLATE子句指定列的排序规则（该列必须是可排列的数据类型）。如果没有指定，则使用默认的排序规则。排序规则可以使用“select * from pg_collation;”命令从pg_collation系统表中查询，默认的排序规则为查询结果中以default开始的行。
+
+- **CONSTRAINT constraint_name**
+
+  列约束或表约束的名称。可选的约束子句用于声明约束，新行或者更新的行必须满足这些约束才能成功插入或更新。
+
+  定义约束有两种方法：
+
+  - 列约束：作为一个列定义的一部分，仅影响该列。
+  - 表约束：不和某个列绑在一起，可以作用于多个列。
+
+- **LIKE source_table [ like_option … ]**
+
+  LIKE子句声明一个表，新表自动从这个表里面继承所有字段名及其数据类型和非空约束。
+
+  和INHERITS不同，新表与原来的表之间在创建动作完毕之后是完全无关的。在源表做的任何修改都不会传播到新表中，并且也不可能在扫描源表的时候包含新表的数据。
+
+  - 字段缺省表达式只有在声明了INCLUDING DEFAULTS之后才会包含进来。缺省是不包含缺省表达式的，即新表中所有字段的缺省值都是NULL。
+  - 如果指定了INCLUDING GENERATED，则源表列的生成表达式会复制到新表中。默认不复制生成表达式。
+
+  - 非空约束将总是复制到新表中，CHECK约束则仅在指定了INCLUDING CONSTRAINTS的时候才复制，而其他类型的约束则永远也不会被复制。此规则同时适用于表约束和列约束。
+
+  - 和INHERITS不同，被复制的列和约束并不使用相同的名称进行融合。如果明确的指定了相同的名称或者在另外一个LIKE子句中，将会报错。
+
+  - 如果指定了INCLUDING INDEXES，则源表上的索引也将在新表上创建，默认不建立索引。
+  - 如果指定了INCLUDING STORAGE，则拷贝列的STORAGE设置也将被拷贝，默认情况下不包含STORAGE设置。
+  - 如果指定了INCLUDING COMMENTS，则源表列、约束和索引的注释也会被拷贝过来。默认情况下，不拷贝源表的注释。
+  - 如果指定了INCLUDING RELOPTIONS，则源表的存储参数（即源表的WITH子句）也将拷贝至新表。默认情况下，不拷贝源表的存储参数。
+  - INCLUDING ALL包含了INCLUDING DEFAULTS、INCLUDING CONSTRAINTS、INCLUDING INDEXES、INCLUDING STORAGE、INCLUDING COMMENTS、INCLUDING PARTITION和INCLUDING RELOPTIONS的内容。
+
+- **WITH ( storage_parameter [= value] [, … ] )**
+
+  这个子句为表或索引指定一个可选的存储参数。参数的详细描述如下所示：
+
+  - FILLFACTOR
+
+    一个表的填充因子（fillfactor）是一个介于10和100之间的百分数。100（完全填充）是默认值。如果指定了较小的填充因子，INSERT操作仅按照填充因子指定的百分率填充表页。每个页上的剩余空间将用于在该页上更新行，这就使得UPDATE有机会在同一页上放置同一条记录的新版本，这比把新版本放置在其他页上更有效。对于一个从不更新的表将填充因子设为100是最佳选择，但是对于频繁更新的表，选择较小的填充因子则更加合适。该参数对于列存表没有意义。
+
+    取值范围: 10~100
+
+  - ORIENTATION
+
+    决定了表的数据的存储方式。
+
+    取值范围:
+
+    - COLUMN：表的数据将以列式存储。
+
+    - ROW（缺省值）：表的数据将以行式存储。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** orientation不支持修改。
+
+  - COMPRESSION
+
+    - 列存表的有效值为LOW/MIDDLE/HIGH/YES/NO，压缩级别依次升高，默认值为LOW。
+    - 行存表不支持压缩。
+
+  - MAX_BATCHROW
+
+    指定了在数据加载过程中一个存储单元可以容纳记录的最大数目。该参数只对列存表有效。
+
+    取值范围: 10000~60000，默认60000。
+
+  - PARTIAL_CLUSTER_ROWS
+
+    指定了在数据加载过程中进行将局部聚簇存储的记录数目。该参数只对列存表有效。
+
+    取值范围: 大于等于MAX_BATCHROW，建议取值为MAX_BATCHROW的整数倍数。
+
+  - DELTAROW_THRESHOLD
+
+    预留参数。该参数只对列存表有效。
+
+    取值范围: 0～9999
+
+- **COMPRESS / NOCOMPRESS**
+
+  创建一个新表时，需要在创建表语句中指定关键字COMPRESS，这样，当对该表进行批量插入时就会触发压缩特性。该特性会在页范围内扫描所有元组数据，生成字典、压缩元组数据并进行存储。指定关键字NOCOMPRESS则不对表进行压缩。行存表不支持压缩。
+
+  缺省值为NOCOMPRESS，即不对元组数据进行压缩。
+
+- **TABLESPACE tablespace_name**
+
+  指定新表将要在tablespace_name表空间内创建。如果没有声明，将使用默认表空间。
+
+- **PARTITION BY RANGE(partition_key)**
+
+  创建范围分区。partition_key为分区键的名称。
+
+  （1）对于从句是VALUES LESS THAN的语法格式：
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 对于从句是VALUE LESS THAN的语法格式，范围分区策略的分区键最多支持4列。
+
+  该情形下，分区键支持的数据类型为：SMALLINT、INTEGER、BIGINT、DECIMAL、NUMERIC、REAL、DOUBLE PRECISION、CHARACTER VARYING(n)、VARCHAR(n)、CHARACTER(n)、CHAR(n)、CHARACTER、CHAR、TEXT、NVARCHAR2、NAME、TIMESTAMP[(p)] [WITHOUT TIME ZONE]、TIMESTAMP[(p)] [WITH TIME ZONE]、DATE。
+
+  （2）对于从句是START END的语法格式：
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 对于从句是START END的语法格式，范围分区策略的分区键仅支持1列。
+
+  该情形下，分区键支持的数据类型为：SMALLINT、INTEGER、BIGINT、DECIMAL、NUMERIC、REAL、DOUBLE PRECISION、TIMESTAMP[(p)] [WITHOUT TIME ZONE]、TIMESTAMP[(p)] [WITH TIME ZONE]、DATE。
+
+  （3）对于指定了INTERVAL子句的语法格式：
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 对于指定了INTERVAL子句的语法格式，范围分区策略的分区键仅支持1列。
+
+  该情形下，分区键支持的数据类型为：TIMESTAMP[(p)] [WITHOUT TIME ZONE]、TIMESTAMP[(p)] [WITH TIME ZONE]、DATE。
+
+- **PARTITION partition_name VALUES LESS THAN ( { partition_value | MAXVALUE } )**
+
+  指定各分区的信息。partition_name为范围分区的名称。partition_value为范围分区的上边界，取值依赖于partition_key的类型。MAXVALUE表示分区的上边界，它通常用于设置最后一个范围分区的上边界。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+  >
+  > - 每个分区都需要指定一个上边界。
+  > - 分区上边界的类型应当和分区键的类型一致。
+  > - 分区列表是按照分区上边界升序排列的，值较小的分区位于值较大的分区之前。
+
+- **PARTITION partition_name {START (partition_value) END (partition_value) EVERY (interval_value)} |**{START (partition_value) END (partition_value|MAXVALUE)} | {START(partition_value)} | **{END (partition_value | MAXVALUE)**}
+
+  指定各分区的信息，各参数意义如下：
+
+  - partition_name：范围分区的名称或名称前缀，除以下情形外（假定其中的partition_name是p1），均为分区的名称。
+    - 若该定义是START+END+EVERY从句，则语义上定义的分区的名称依次为p1_1, p1_2, …。例如对于定义“PARTITION p1 START(1) END(4) EVERY(1)”，则生成的分区是：[1, 2), [2, 3) 和 [3, 4)，名称依次为p1_1, p1_2和p1_3，即此处的p1是名称前缀。
+    - 若该定义是第一个分区定义，且该定义有START值，则范围（MINVALUE, START）将自动作为第一个实际分区，其名称为p1_0，然后该定义语义描述的分区名称依次为p1_1, p1_2, …。例如对于完整定义“PARTITION p1 START(1), PARTITION p2 START(2)”，则生成的分区是：(MINVALUE, 1), [1, 2) 和 [2, MAXVALUE)，其名称依次为p1_0, p1_1和p2，即此处p1是名称前缀，p2是分区名称。这里MINVALUE表示最小值。
+  - partition_value：范围分区的端点值（起始或终点），取值依赖于partition_key的类型，不可是MAXVALUE。
+  - interval_value：对[START，END) 表示的范围进行切分，interval_value是指定切分后每个分区的宽度，不可是MAXVALUE；如果（END-START）值不能整除以EVERY值，则仅最后一个分区的宽度小于EVERY值。
+  - MAXVALUE：表示最大值，它通常用于设置最后一个范围分区的上边界。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+  >
+  > 1. 在创建分区表若第一个分区定义含START值，则范围（MINVALUE，START）将自动作为实际的第一个分区。
+  > 2. START END语法需要遵循以下限制：
+  >    - 每个partition_start_end_item中的START值（如果有的话，下同）必须小于其END值。
+  >    - 相邻的两个partition_start_end_item，第一个的END值必须等于第二个的START值； - 每个partition_start_end_item中的EVERY值必须是正向递增的，且必须小于（END-START）值；
+  >    - 每个分区包含起始值，不包含终点值，即形如：[起始值，终点值)，起始值是MINVALUE时则不包含；
+  >    - 一个partition_start_end_item创建的每个分区所属的TABLESPACE一样；
+  >    - partition_name作为分区名称前缀时，其长度不要超过57字节，超过时自动截断；
+  >    - 在创建、修改分区表时请注意分区表的分区总数不可超过最大限制（1048575）；
+  > 3. 在创建分区表时START END与LESS THAN语法不可混合使用。
+  > 4. 即使创建分区表时使用START END语法，备份（gs_dump）出的SQL语句也是VALUES LESS THAN语法格式。
+
+- **INTERVAL ('interval_expr') [ STORE IN (tablespace_name [, … ] ) ]**
+
+  间隔分区定义信息。
+
+  - interval_expr：自动创建分区的间隔，例如：1 day、1 month。
+  - STORE IN (tablespace_name [, … ] )：指定存放自动创建分区的表空间列表，如果有指定，则自动创建的分区从表空间列表中循环选择使用，否则使用分区表默认的表空间。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 列存表不支持间隔分区。
+
+- **PARTITION BY LIST(partition_key)**
+
+  创建列表分区。partition_key为分区键的名称。
+
+  - 对于partition_key，列表分区策略的分区键仅支持1列。
+  - 对于从句是VALUES (list_values_clause)的语法格式，list_values_clause中包含了对应分区存在的键值，推荐每个分区的键值数量不超过1048575个。
+
+  分区键支持的数据类型为：INT1、INT2、INT4、INT8、NUMERIC、VARCHAR(n)、CHAR、BPCHAR、NVARCHAR2、TIMESTAMP[(p)] [WITHOUT TIME ZONE]、TIMESTAMP[(p)] [WITH TIME ZONE]、DATE。分区个数不能超过64个。
+
+- **PARTITION BY HASH(partition_key)**
+
+  创建哈希分区。partition_key为分区键的名称。
+
+  对于partition_key，哈希分区策略的分区键仅支持1列。
+
+  分区键支持的数据类型为：INT1、INT2、INT4、INT8、NUMERIC、VARCHAR(n)、CHAR、BPCHAR、TEXT、NVARCHAR2、TIMESTAMP[(p)] [WITHOUT TIME ZONE]、TIMESTAMP[(p)] [WITH TIME ZONE]、DATE。分区个数不能超过1048575个。
+
+- **{ ENABLE | DISABLE } ROW MOVEMENT**
+
+  行迁移开关。
+
+  如果进行UPDATE操作时，更新了元组在分区键上的值，造成了该元组所在分区发生变化，就会根据该开关给出报错信息，或者进行元组在分区间的转移。
+
+  取值范围:
+
+  - ENABLE（缺省值）：行迁移开关打开。
+  - DISABLE：行迁移开关关闭。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 列表/哈希分区表暂不支持ROW MOVEMENT。
+
+- **NOT NULL**
+
+  字段值不允许为NULL。ENABLE用于语法兼容，可省略。
+
+- **NULL**
+
+  字段值允许NULL ，这是缺省。
+
+  这个子句只是为和非标准SQL数据库兼容。不建议使用。
+
+- **CHECK (condition) [ NO INHERIT ]**
+
+  CHECK约束声明一个布尔表达式，每次要插入的新行或者要更新的行的新值必须使表达式结果为真或未知才能成功，否则会抛出一个异常并且不会修改数据库。
+
+  声明为字段约束的检查约束应该只引用该字段的数值，而在表约束里出现的表达式可以引用多个字段。
+
+  用NO INHERIT标记的约束将不会传递到子表中去。
+
+  ENABLE用于语法兼容，可省略。
+
+- **DEFAULT default_expr**
+
+  DEFAULT子句给字段指定缺省值。该数值可以是任何不含变量的表达式(不允许使用子查询和对本表中的其他字段的交叉引用)。缺省表达式的数据类型必须和字段类型匹配。
+
+  缺省表达式将被用于任何未声明该字段数值的插入操作。如果没有指定缺省值则缺省值为NULL 。
+
+- **GENERATED ALWAYS AS ( generation_expr ) STORED**
+
+  该子句将字段创建为生成列，生成列的值在写入（插入或更新）数据时由generation_expr计算得到，STORED表示像普通列一样存储生成列的值。
+
+  >**说明：**
+  >
+  >- 生成表达式不能以任何方式引用当前行以外的其他数据。生成表达式不能引用其他生成列，不能引用系统列。生成表达式不能返回结果集，不能使用子查询，不能使用聚集函数，不能使用窗口函数。生成表达式调用的函数只能是不可变（IMMUTABLE）函数。
+  >
+  >- 不能为生成列指定默认值。
+  >
+  >- 生成列不能作为分区键的一部分。
+  >
+  >- 生成列不能和ON UPDATE约束字句的CASCADE,SET NULL,SET DEFAULT动作同时指定。生成列不能和ON DELETE约束字句的SET NULL,SET DEFAULT动作同时指定。
+  >
+  >- 修改和删除生成列的方法和普通列相同。删除生成列依赖的普通列，生成列被自动删除。不能改变生成列所依赖的列的类型。
+  >
+  >- 生成列不能被直接写入。在INSERT或UPDATE命令中, 不能为生成列指定值, 但是可以指定关键字DEFAULT。
+  >
+  >- 生成列的权限控制和普通列一样。
+  >
+  >- 列存表、内存表MOT不支持生成列。外表中仅postgres_fdw支持生成列。
+
+- **UNIQUE index_parameters**
+
+  **UNIQUE ( column_name [, … ] ) index_parameters**
+
+  UNIQUE约束表示表里的一个字段或多个字段的组合必须在全表范围内唯一。
+
+  对于唯一约束，NULL被认为是互不相等的。
+
+- **PRIMARY KEY index_parameters**
+
+  **PRIMARY KEY ( column_name [, … ] ) index_parameters**
+
+  主键约束声明表中的一个或者多个字段只能包含唯一的非NULL值。
+
+  一个表只能声明一个主键。
+
+- **DEFERRABLE | NOT DEFERRABLE**
+
+  这两个关键字设置该约束是否可推迟。一个不可推迟的约束将在每条命令之后马上检查。可推迟约束可以推迟到事务结尾使用SET CONSTRAINTS命令检查。缺省是NOT DEFERRABLE。目前，UNIQUE约束、主键约束、外键约束可以接受这个子句。所有其他约束类型都是不可推迟的。
+
+- **INITIALLY IMMEDIATE | INITIALLY DEFERRED**
+
+  如果约束是可推迟的，则这个子句声明检查约束的缺省时间。
+
+  - 如果约束是INITIALLY IMMEDIATE（缺省），则在每条语句执行之后就立即检查它；
+  - 如果约束是INITIALLY DEFERRED ，则只有在事务结尾才检查它。
+
+  约束检查的时间可以用SET CONSTRAINTS命令修改。
+
+- **USING INDEX TABLESPACE tablespace_name**
+
+  为UNIQUE或PRIMARY KEY约束相关的索引声明一个表空间。如果没有提供这个子句，这个索引将在default_tablespace中创建，如果default_tablespace为空，将使用数据库的缺省表空间。
+
+## 示例
+
+- 示例1：创建范围分区表tpcds.web_returns_p1，含有8个分区，分区键为integer类型。 分区的范围分别为：wr_returned_date_sk&lt; 2450815，2450815&lt;= wr_returned_date_sk&lt; 2451179，2451179&lt;=wr_returned_date_sk&lt; 2451544，2451544 &lt;= wr_returned_date_sk&lt; 2451910，2451910 &lt;= wr_returned_date_sk&lt; 2452275，2452275 &lt;= wr_returned_date_sk&lt; 2452640，2452640 &lt;= wr_returned_date_sk&lt; 2453005，wr_returned_date_sk&gt;=2453005。
+
+  ```sql
+  --创建表tpcds.web_returns。
+  mogdb=# CREATE TABLE tpcds.web_returns
+  (
+      W_WAREHOUSE_SK            INTEGER               NOT NULL,
+      W_WAREHOUSE_ID            CHAR(16)              NOT NULL,
+      W_WAREHOUSE_NAME          VARCHAR(20)                   ,
+      W_WAREHOUSE_SQ_FT         INTEGER                       ,
+      W_STREET_NUMBER           CHAR(10)                      ,
+      W_STREET_NAME             VARCHAR(60)                   ,
+      W_STREET_TYPE             CHAR(15)                      ,
+      W_SUITE_NUMBER            CHAR(10)                      ,
+      W_CITY                    VARCHAR(60)                   ,
+      W_COUNTY                  VARCHAR(30)                   ,
+      W_STATE                   CHAR(2)                       ,
+      W_ZIP                     CHAR(10)                      ,
+      W_COUNTRY                 VARCHAR(20)                   ,
+      W_GMT_OFFSET              DECIMAL(5,2)
+  );
+  --创建分区表tpcds.web_returns_p1。
+  mogdb=# CREATE TABLE tpcds.web_returns_p1
+  (
+      WR_RETURNED_DATE_SK       INTEGER                       ,
+      WR_RETURNED_TIME_SK       INTEGER                       ,
+      WR_ITEM_SK                INTEGER               NOT NULL,
+      WR_REFUNDED_CUSTOMER_SK   INTEGER                       ,
+      WR_REFUNDED_CDEMO_SK      INTEGER                       ,
+      WR_REFUNDED_HDEMO_SK      INTEGER                       ,
+      WR_REFUNDED_ADDR_SK       INTEGER                       ,
+      WR_RETURNING_CUSTOMER_SK  INTEGER                       ,
+      WR_RETURNING_CDEMO_SK     INTEGER                       ,
+      WR_RETURNING_HDEMO_SK     INTEGER                       ,
+      WR_RETURNING_ADDR_SK      INTEGER                       ,
+      WR_WEB_PAGE_SK            INTEGER                       ,
+      WR_REASON_SK              INTEGER                       ,
+      WR_ORDER_NUMBER           BIGINT                NOT NULL,
+      WR_RETURN_QUANTITY        INTEGER                       ,
+      WR_RETURN_AMT             DECIMAL(7,2)                  ,
+      WR_RETURN_TAX             DECIMAL(7,2)                  ,
+      WR_RETURN_AMT_INC_TAX     DECIMAL(7,2)                  ,
+      WR_FEE                    DECIMAL(7,2)                  ,
+      WR_RETURN_SHIP_COST       DECIMAL(7,2)                  ,
+      WR_REFUNDED_CASH          DECIMAL(7,2)                  ,
+      WR_REVERSED_CHARGE        DECIMAL(7,2)                  ,
+      WR_ACCOUNT_CREDIT         DECIMAL(7,2)                  ,
+      WR_NET_LOSS               DECIMAL(7,2)
+  )
+  WITH (ORIENTATION = COLUMN,COMPRESSION=MIDDLE)
+  PARTITION BY RANGE(WR_RETURNED_DATE_SK)
+  (
+          PARTITION P1 VALUES LESS THAN(2450815),
+          PARTITION P2 VALUES LESS THAN(2451179),
+          PARTITION P3 VALUES LESS THAN(2451544),
+          PARTITION P4 VALUES LESS THAN(2451910),
+          PARTITION P5 VALUES LESS THAN(2452275),
+          PARTITION P6 VALUES LESS THAN(2452640),
+          PARTITION P7 VALUES LESS THAN(2453005),
+          PARTITION P8 VALUES LESS THAN(MAXVALUE)
+  );
+
+  --从示例数据表导入数据。
+  mogdb=# INSERT INTO tpcds.web_returns_p1 SELECT * FROM tpcds.web_returns;
+
+  --删除分区P8。
+  mogdb=# ALTER TABLE tpcds.web_returns_p1 DROP PARTITION P8;
+
+  --增加分区WR_RETURNED_DATE_SK介于2453005和2453105之间。
+  mogdb=# ALTER TABLE tpcds.web_returns_p1 ADD PARTITION P8 VALUES LESS THAN (2453105);
+
+  --增加分区WR_RETURNED_DATE_SK介于2453105和MAXVALUE之间。
+  mogdb=# ALTER TABLE tpcds.web_returns_p1 ADD PARTITION P9 VALUES LESS THAN (MAXVALUE);
+
+  --删除分区P8。
+  mogdb=# ALTER TABLE tpcds.web_returns_p1 DROP PARTITION FOR (2453005);
+
+  --分区P7重命名为P10。
+  mogdb=# ALTER TABLE tpcds.web_returns_p1 RENAME PARTITION P7 TO P10;
+
+  --分区P6重命名为P11。
+  mogdb=# ALTER TABLE tpcds.web_returns_p1 RENAME PARTITION FOR (2452639) TO P11;
+
+  --查询分区P10的行数。
+  mogdb=# SELECT count(*) FROM tpcds.web_returns_p1 PARTITION (P10);
+   count
+  --------
+   0
+  (1 row)
+
+  --查询分区P1的行数。
+  mogdb=# SELECT COUNT(*) FROM tpcds.web_returns_p1 PARTITION FOR (2450815);
+   count
+  --------
+   0
+  (1 row)
+  ```
+
+- 示例2：创建范围分区表tpcds.web_returns_p2，含有8个分区，分区键类型为integer类型，其中第8个分区上边界为MAXVALUE。
+
+  八个分区的范围分别为： wr_returned_date_sk&lt; 2450815，2450815&lt;= wr_returned_date_sk&lt; 2451179，2451179&lt;=wr_returned_date_sk&lt; 2451544，2451544 &lt;= wr_returned_date_sk&lt; 2451910，2451910 &lt;= wr_returned_date_sk&lt; 2452275，2452275 &lt;= wr_returned_date_sk&lt; 2452640，2452640 &lt;= wr_returned_date_sk&lt; 2453005，wr_returned_date_sk&gt;=2453005。
+
+  分区表tpcds.web_returns_p2的表空间为example1；分区P1到P7没有声明表空间，使用采用分区表tpcds.web_returns_p2的表空间example1；指定分区P8的表空间为example2。
+
+  假定数据库节点的数据目录/pg_location/mount1/path1，数据库节点的数据目录/pg_location/mount2/path2，数据库节点的数据目录/pg_location/mount3/path3，数据库节点的数据目录/pg_location/mount4/path4是dwsadmin用户拥有读写权限的空目录。
+
+  ```sql
+  mogdb=# CREATE TABLESPACE example1 RELATIVE LOCATION 'tablespace1/tablespace_1';
+  mogdb=# CREATE TABLESPACE example2 RELATIVE LOCATION 'tablespace2/tablespace_2';
+  mogdb=# CREATE TABLESPACE example3 RELATIVE LOCATION 'tablespace3/tablespace_3';
+  mogdb=# CREATE TABLESPACE example4 RELATIVE LOCATION 'tablespace4/tablespace_4';
+
+  mogdb=# CREATE TABLE tpcds.web_returns_p2
+  (
+      WR_RETURNED_DATE_SK       INTEGER                       ,
+      WR_RETURNED_TIME_SK       INTEGER                       ,
+      WR_ITEM_SK                INTEGER               NOT NULL,
+      WR_REFUNDED_CUSTOMER_SK   INTEGER                       ,
+      WR_REFUNDED_CDEMO_SK      INTEGER                       ,
+      WR_REFUNDED_HDEMO_SK      INTEGER                       ,
+      WR_REFUNDED_ADDR_SK       INTEGER                       ,
+      WR_RETURNING_CUSTOMER_SK  INTEGER                       ,
+      WR_RETURNING_CDEMO_SK     INTEGER                       ,
+      WR_RETURNING_HDEMO_SK     INTEGER                       ,
+      WR_RETURNING_ADDR_SK      INTEGER                       ,
+      WR_WEB_PAGE_SK            INTEGER                       ,
+      WR_REASON_SK              INTEGER                       ,
+      WR_ORDER_NUMBER           BIGINT                NOT NULL,
+      WR_RETURN_QUANTITY        INTEGER                       ,
+      WR_RETURN_AMT             DECIMAL(7,2)                  ,
+      WR_RETURN_TAX             DECIMAL(7,2)                  ,
+      WR_RETURN_AMT_INC_TAX     DECIMAL(7,2)                  ,
+      WR_FEE                    DECIMAL(7,2)                  ,
+      WR_RETURN_SHIP_COST       DECIMAL(7,2)                  ,
+      WR_REFUNDED_CASH          DECIMAL(7,2)                  ,
+      WR_REVERSED_CHARGE        DECIMAL(7,2)                  ,
+      WR_ACCOUNT_CREDIT         DECIMAL(7,2)                  ,
+      WR_NET_LOSS               DECIMAL(7,2)
+  )
+  TABLESPACE example1
+  PARTITION BY RANGE(WR_RETURNED_DATE_SK)
+  (
+          PARTITION P1 VALUES LESS THAN(2450815),
+          PARTITION P2 VALUES LESS THAN(2451179),
+          PARTITION P3 VALUES LESS THAN(2451544),
+          PARTITION P4 VALUES LESS THAN(2451910),
+          PARTITION P5 VALUES LESS THAN(2452275),
+          PARTITION P6 VALUES LESS THAN(2452640),
+          PARTITION P7 VALUES LESS THAN(2453005),
+          PARTITION P8 VALUES LESS THAN(MAXVALUE) TABLESPACE example2
+  )
+  ENABLE ROW MOVEMENT;
+
+  --以like方式创建一个分区表。
+  mogdb=# CREATE TABLE tpcds.web_returns_p3 (LIKE tpcds.web_returns_p2 INCLUDING PARTITION);
+
+  --修改分区P1的表空间为example2。
+  mogdb=# ALTER TABLE tpcds.web_returns_p2 MOVE PARTITION P1 TABLESPACE example2;
+
+  --修改分区P2的表空间为example3。
+  mogdb=# ALTER TABLE tpcds.web_returns_p2 MOVE PARTITION P2 TABLESPACE example3;
+
+  --以2453010为分割点切分P8。
+  mogdb=# ALTER TABLE tpcds.web_returns_p2 SPLIT PARTITION P8 AT (2453010) INTO
+  (
+          PARTITION P9,
+          PARTITION P10
+  );
+
+  --将P6，P7合并为一个分区。
+  mogdb=# ALTER TABLE tpcds.web_returns_p2 MERGE PARTITIONS P6, P7 INTO PARTITION P8;
+
+  --修改分区表迁移属性。
+  mogdb=# ALTER TABLE tpcds.web_returns_p2 DISABLE ROW MOVEMENT;
+  --删除表和表空间。
+  mogdb=# DROP TABLE tpcds.web_returns_p1;
+  mogdb=# DROP TABLE tpcds.web_returns_p2;
+  mogdb=# DROP TABLE tpcds.web_returns_p3;
+  mogdb=# DROP TABLESPACE example1;
+  mogdb=# DROP TABLESPACE example2;
+  mogdb=# DROP TABLESPACE example3;
+  mogdb=# DROP TABLESPACE example4;
+  ```
+
+- 示例3：START END语法创建、修改Range分区表。
+
+  假定/home/omm/startend_tbs1，/home/omm/startend_tbs2，/home/omm/startend_tbs3，/home/omm/startend_tbs4是omm用户拥有读写权限的空目录。
+
+  ```sql
+  -- 创建表空间
+  mogdb=# CREATE TABLESPACE startend_tbs1 LOCATION '/home/omm/startend_tbs1';
+  mogdb=# CREATE TABLESPACE startend_tbs2 LOCATION '/home/omm/startend_tbs2';
+  mogdb=# CREATE TABLESPACE startend_tbs3 LOCATION '/home/omm/startend_tbs3';
+  mogdb=# CREATE TABLESPACE startend_tbs4 LOCATION '/home/omm/startend_tbs4';
+
+  -- 创建临时schema
+  mogdb=# CREATE SCHEMA tpcds;
+  mogdb=# SET CURRENT_SCHEMA TO tpcds;
+
+  -- 创建分区表，分区键是integer类型
+  mogdb=# CREATE TABLE tpcds.startend_pt (c1 INT, c2 INT)
+  TABLESPACE startend_tbs1
+  PARTITION BY RANGE (c2) (
+      PARTITION p1 START(1) END(1000) EVERY(200) TABLESPACE startend_tbs2,
+      PARTITION p2 END(2000),
+      PARTITION p3 START(2000) END(2500) TABLESPACE startend_tbs3,
+      PARTITION p4 START(2500),
+      PARTITION p5 START(3000) END(5000) EVERY(1000) TABLESPACE startend_tbs4
+  )
+  ENABLE ROW MOVEMENT;
+
+  -- 查看分区表信息
+  mogdb=# SELECT relname, boundaries, spcname FROM pg_partition p JOIN pg_tablespace t ON p.reltablespace=t.oid and p.parentid='tpcds.startend_pt'::regclass ORDER BY 1;
+     relname   | boundaries |    spcname
+  -------------+------------+---------------
+   p1_0        | {1}        | startend_tbs2
+   p1_1        | {201}      | startend_tbs2
+   p1_2        | {401}      | startend_tbs2
+   p1_3        | {601}      | startend_tbs2
+   p1_4        | {801}      | startend_tbs2
+   p1_5        | {1000}     | startend_tbs2
+   p2          | {2000}     | startend_tbs1
+   p3          | {2500}     | startend_tbs3
+   p4          | {3000}     | startend_tbs1
+   p5_1        | {4000}     | startend_tbs4
+   p5_2        | {5000}     | startend_tbs4
+   startend_pt |            | startend_tbs1
+  (12 rows)
+
+  -- 导入数据，查看分区数据量
+  mogdb=# INSERT INTO tpcds.startend_pt VALUES (GENERATE_SERIES(0, 4999), GENERATE_SERIES(0, 4999));
+  mogdb=# SELECT COUNT(*) FROM tpcds.startend_pt PARTITION FOR (0);
+   count
+  -------
+       1
+  (1 row)
+
+  mogdb=# SELECT COUNT(*) FROM tpcds.startend_pt PARTITION (p3);
+   count
+  -------
+     500
+  (1 row)
+
+  -- 增加分区: [5000, 5300), [5300, 5600), [5600, 5900), [5900, 6000)
+  mogdb=# ALTER TABLE tpcds.startend_pt ADD PARTITION p6 START(5000) END(6000) EVERY(300) TABLESPACE startend_tbs4;
+
+  -- 增加MAXVALUE分区: p7
+  mogdb=# ALTER TABLE tpcds.startend_pt ADD PARTITION p7 END(MAXVALUE);
+
+  -- 重命名分区p7为p8
+  mogdb=# ALTER TABLE tpcds.startend_pt RENAME PARTITION p7 TO p8;
+
+  -- 删除分区p8
+  mogdb=# ALTER TABLE tpcds.startend_pt DROP PARTITION p8;
+
+  -- 重命名5950所在的分区为：p71
+  mogdb=# ALTER TABLE tpcds.startend_pt RENAME PARTITION FOR(5950) TO p71;
+
+  -- 分裂4500所在的分区[4000, 5000)
+  mogdb=# ALTER TABLE tpcds.startend_pt SPLIT PARTITION FOR(4500) INTO(PARTITION q1 START(4000) END(5000) EVERY(250) TABLESPACE startend_tbs3);
+
+  -- 修改分区p2的表空间为startend_tbs4
+  mogdb=# ALTER TABLE tpcds.startend_pt MOVE PARTITION p2 TABLESPACE startend_tbs4;
+
+  -- 查看分区情形
+  mogdb=# SELECT relname, boundaries, spcname FROM pg_partition p JOIN pg_tablespace t ON p.reltablespace=t.oid and p.parentid='tpcds.startend_pt'::regclass ORDER BY 1;
+     relname   | boundaries |    spcname
+  -------------+------------+---------------
+   p1_0        | {1}        | startend_tbs2
+   p1_1        | {201}      | startend_tbs2
+   p1_2        | {401}      | startend_tbs2
+   p1_3        | {601}      | startend_tbs2
+   p1_4        | {801}      | startend_tbs2
+   p1_5        | {1000}     | startend_tbs2
+   p2          | {2000}     | startend_tbs4
+   p3          | {2500}     | startend_tbs3
+   p4          | {3000}     | startend_tbs1
+   p5_1        | {4000}     | startend_tbs4
+   p6_1        | {5300}     | startend_tbs4
+   p6_2        | {5600}     | startend_tbs4
+   p6_3        | {5900}     | startend_tbs4
+   p71         | {6000}     | startend_tbs4
+   q1_1        | {4250}     | startend_tbs3
+   q1_2        | {4500}     | startend_tbs3
+   q1_3        | {4750}     | startend_tbs3
+   q1_4        | {5000}     | startend_tbs3
+   startend_pt |            | startend_tbs1
+  (19 rows)
+
+  -- 删除表和表空间
+  mogdb=# DROP SCHEMA tpcds CASCADE;
+  mogdb=# DROP TABLESPACE startend_tbs1;
+  mogdb=# DROP TABLESPACE startend_tbs2;
+  mogdb=# DROP TABLESPACE startend_tbs3;
+  mogdb=# DROP TABLESPACE startend_tbs4;
+  ```
+
+- 示例4：创建间隔分区表sales，初始包含2个分区，分区键为DATE类型。 分区的范围分别为：time_id &lt; '2019-02-01 00:00:00'，
+
+  '2019-02-01 00:00:00' &lt;= time_id &lt; '2019-02-02 00:00:00' 。
+
+  ```sql
+  --创建表sales
+  mogdb=# CREATE TABLE sales
+  (prod_id NUMBER(6),
+   cust_id NUMBER,
+   time_id DATE,
+   channel_id CHAR(1),
+   promo_id NUMBER(6),
+   quantity_sold NUMBER(3),
+   amount_sold NUMBER(10,2)
+  )
+  PARTITION BY RANGE (time_id)
+  INTERVAL('1 day')
+  ( PARTITION p1 VALUES LESS THAN ('2019-02-01 00:00:00'),
+    PARTITION p2 VALUES LESS THAN ('2019-02-02 00:00:00')
+  );
+
+  -- 数据插入分区p1
+  mogdb=# INSERT INTO sales VALUES(1, 12, '2019-01-10 00:00:00', 'a', 1, 1, 1);
+
+  -- 数据插入分区p2
+  mogdb=# INSERT INTO sales VALUES(1, 12, '2019-02-01 00:00:00', 'a', 1, 1, 1);
+
+  -- 查看分区信息
+  mogdb=# SELECT t1.relname, partstrategy, boundaries FROM pg_partition t1, pg_class t2 WHERE t1.parentid = t2.oid AND t2.relname = 'sales' AND t1.parttype = 'p';
+   relname | partstrategy |       boundaries
+  ---------+--------------+-------------------------
+   p1      | r            | {"2019-02-01 00:00:00"}
+   p2      | r            | {"2019-02-02 00:00:00"}
+  (2 rows)
+
+  -- 插入数据没有匹配的分区，新创建一个分区，并将数据插入该分区
+  -- 新分区的范围为 '2019-02-05 00:00:00' <= time_id < '2019-02-06 00:00:00'
+  mogdb=# INSERT INTO sales VALUES(1, 12, '2019-02-05 00:00:00', 'a', 1, 1, 1);
+
+  -- 插入数据没有匹配的分区，新创建一个分区，并将数据插入该分区
+  -- 新分区的范围为 '2019-02-03 00:00:00' <= time_id < '2019-02-04 00:00:00'
+  mogdb=# INSERT INTO sales VALUES(1, 12, '2019-02-03 00:00:00', 'a', 1, 1, 1);
+
+  -- 查看分区信息
+  mogdb=# SELECT t1.relname, partstrategy, boundaries FROM pg_partition t1, pg_class t2 WHERE t1.parentid = t2.oid AND t2.relname = 'sales' AND t1.parttype = 'p';
+   relname | partstrategy |       boundaries
+  ---------+--------------+-------------------------
+   sys_p1  | i            | {"2019-02-06 00:00:00"}
+   sys_p2  | i            | {"2019-02-04 00:00:00"}
+   p1      | r            | {"2019-02-01 00:00:00"}
+   p2      | r            | {"2019-02-02 00:00:00"}
+  (4 rows)
+
+  ```
+
+- 示例5：创建LIST分区表test_list，初始包含4个分区，分区键为INT类型。4个分区的范围分别为：2000，3000，4000，5000。
+
+    ```sql
+    --创建表test_list
+    mogdb=# create table test_list (col1 int, col2 int)
+    partition by list(col1)
+    (
+    partition p1 values (2000),
+    partition p2 values (3000),
+    partition p3 values (4000),
+    partition p4 values (5000)
+    );
+
+    -- 数据插入
+    mogdb=# INSERT INTO test_list VALUES(2000, 2000);
+    INSERT 0 1
+    mogdb=# INSERT INTO test_list VALUES(3000, 3000);
+    INSERT 0 1
+
+    -- 查看分区信息
+    mogdb=# SELECT t1.relname, partstrategy, boundaries FROM pg_partition t1, pg_class t2 WHERE t1.parentid = t2.oid AND t2.relname = 'test_list' AND t1.parttype = 'p';
+     relname | partstrategy | boundaries
+    ---------+--------------+------------
+     p1      | l            | {2000}
+     p2      | l            | {3000}
+     p3      | l            | {4000}
+     p4      | l            | {5000}
+    (4 rows)
+
+    -- 插入数据没有匹配到分区，报错处理
+    mogdb=# INSERT INTO test_list VALUES(6000, 6000);
+    ERROR:  inserted partition key does not map to any table partition
+
+    -- 添加分区
+    mogdb=# alter table test_list add partition p5 values (6000);
+    ALTER TABLE
+    mogdb=# SELECT t1.relname, partstrategy, boundaries FROM pg_partition t1, pg_class t2 WHERE t1.parentid = t2.oid AND t2.relname = 'test_list' AND t1.parttype = 'p';
+     relname | partstrategy | boundaries
+    ---------+--------------+------------
+     p5      | l            | {6000}
+     p4      | l            | {5000}
+     p1      | l            | {2000}
+     p2      | l            | {3000}
+     p3      | l            | {4000}
+    (5 rows)
+    mogdb=# INSERT INTO test_list VALUES(6000, 6000);
+    INSERT 0 1
+
+    -- 分区表和普通表交换数据
+    mogdb=# create table t1 (col1 int, col2 int);
+    CREATE TABLE
+    mogdb=# select * from test_list partition (p1);
+     col1 | col2
+    ------+------
+     2000 | 2000
+    (1 row)
+    mogdb=# alter table test_list exchange partition (p1) with table t1;
+    ALTER TABLE
+    mogdb=# select * from test_list partition (p1);
+     col1 | col2
+    ------+------
+    (0 rows)
+    mogdb=# select * from t1;
+     col1 | col2
+    ------+------
+     2000 | 2000
+    (1 row)
+
+    -- truncate分区
+    mogdb=# select * from test_list partition (p2);
+     col1 | col2
+    ------+------
+     3000 | 3000
+    (1 row)
+    mogdb=# alter table test_list truncate partition p2;
+    ALTER TABLE
+    mogdb=# select * from test_list partition (p2);
+     col1 | col2
+    ------+------
+    (0 rows)
+
+    -- 删除分区
+    mogdb=# alter table test_list drop partition p5;
+    ALTER TABLE
+    mogdb=# SELECT t1.relname, partstrategy, boundaries FROM pg_partition t1, pg_class t2 WHERE t1.parentid = t2.oid AND t2.relname = 'test_list' AND t1.parttype = 'p';
+     relname | partstrategy | boundaries
+    ---------+--------------+------------
+     p4      | l            | {5000}
+     p1      | l            | {2000}
+     p2      | l            | {3000}
+     p3      | l            | {4000}
+    (4 rows)
+
+    mogdb=# INSERT INTO test_list VALUES(6000, 6000);
+    ERROR:  inserted partition key does not map to any table partition
+
+    -- 删除分区表
+    mogdb=# drop table test_list;
+    ```
+
+- 示例6：创建HASH分区表test_hash，初始包含2个分区，分区键为INT类型。
+
+    ```sql
+    --创建表test_hash
+    mogdb=# create table test_hash (col1 int, col2 int)
+    partition by hash(col1)
+    (
+    partition p1,
+    partition p2
+    );
+
+    -- 数据插入
+    mogdb=# INSERT INTO test_hash VALUES(1, 1);
+    INSERT 0 1
+    mogdb=# INSERT INTO test_hash VALUES(2, 2);
+    INSERT 0 1
+    mogdb=# INSERT INTO test_hash VALUES(3, 3);
+    INSERT 0 1
+    mogdb=# INSERT INTO test_hash VALUES(4, 4);
+    INSERT 0 1
+
+    -- 查看分区信息
+    mogdb=# SELECT t1.relname, partstrategy, boundaries FROM pg_partition t1, pg_class t2 WHERE t1.parentid = t2.oid AND t2.relname = 'test_hash' AND t1.parttype = 'p';
+     relname | partstrategy | boundaries
+    ---------+--------------+------------
+     p1      | h            | {0}
+     p2      | h            | {1}
+    (2 rows)
+
+    -- 查看数据
+    mogdb=# select * from test_hash partition (p1);
+     col1 | col2
+    ------+------
+        3 |    3
+        4 |    4
+    (2 rows)
+
+    mogdb=# select * from test_hash partition (p2);
+     col1 | col2
+    ------+------
+        1 |    1
+        2 |    2
+    (2 rows)
+
+    -- 分区表和普通表交换数据
+    mogdb=# create table t1 (col1 int, col2 int);
+    CREATE TABLE
+    mogdb=# alter table test_hash exchange partition (p1) with table t1;
+    ALTER TABLE
+    mogdb=# select * from test_hash partition (p1);
+     col1 | col2
+    ------+------
+    (0 rows)
+    mogdb=# select * from t1;
+     col1 | col2
+    ------+------
+        3 |    3
+        4 |    4
+    (2 rows)
+
+    -- truncate分区
+    mogdb=# alter table test_hash truncate partition p2;
+    ALTER TABLE
+    mogdb=#  select * from test_hash partition (p2);
+     col1 | col2
+    ------+------
+    (0 rows)
+
+    -- 删除分区表
+    mogdb=# drop table test_hash;
+    ```
+
+## 相关链接
+
+[ALTER TABLE PARTITION](23-ALTER-TABLE-PARTITION)，[DROP TABLE](95-DROP-TABLE)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/62.1-CREATE-TABLE-SUBPARTITION.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/62.1-CREATE-TABLE-SUBPARTITION.md
new file mode 100644
index 0000000000000000000000000000000000000000..b84b77c8258e300b096b97c52fbecf89b4199884
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/62.1-CREATE-TABLE-SUBPARTITION.md
@@ -0,0 +1,780 @@
+---
+title: CREATE TABLE SUBPARTITION
+summary: CREATE TABLE SUBPARTITION
+author: Zhang Cuiping
+date: 2021-11-01
+---
+
+# CREATE TABLE SUBPARTITION
+
+## 功能描述
+
+创建二级分区表。分区表是把逻辑上的一张表根据某种方案分成几张物理块进行存储，这张逻辑上的表称之为分区表，物理块称之为分区。分区表是一张逻辑表，不存储数据，数据实际是存储在分区上的。对于二级分区表，顶层节点表和一级分区都是逻辑表，不存储数据，只有二级分区（叶子节点）存储数据。
+
+二级分区表的分区方案是由两个一级分区的分区方案组合而来的，一级分区的分区方案详见章节[CREATE TABLE PARTITION](62-CREATE-TABLE-PARTITION)。
+
+常见的二级分区表组合方案有Range-Range分区、Range-List分区、Range-Hash分区、List-Range分区、List-List分区、List-Hash分区。目前二级分区仅支持行存表。
+
+## 注意事项
+
+- 二级分区表有两个分区键，每个分区键只能支持1列。
+- 唯一约束和主键约束的约束键包含所有分区键将为约束创建LOCAL索引，否则创建GLOBAL索引。
+- 二级分区表的二级分区（叶子节点）个数不能超过1048575个，一级分区最多64个，一级分区下面至少有一个二级分区。
+- 二级分区表只支持行存，不支持列存、段页式、hashbucket。
+- 不支持Upsert、Merge into。
+- 指定分区查询时，如select * from tablename partition/subpartition (partitionname)，关键字partition和subpartition注意不要写错。如果写错，查询会报错，这时查询会变为对表起别名进行查询。
+- 不支持对二级分区 subpartition for (values)查询。如select * from tablename subpartition for (values)。
+- 不支持密态数据库、账本数据库和行级访问控制。
+- 不支持INTERVAL分区下的子分区。
+
+## 语法格式
+
+```ebnf+diagram
+CreateTableSubpartition ::= CREATE TABLE [ IF NOT EXISTS ] subpartition_table_name
+(
+{ column_name data_type [ COLLATE collation ] [ column_constraint [ ... ] ]
+| table_constraint
+| LIKE source_table [ like_option [...] ] }[, ... ]
+)
+[ WITH ( {storage_parameter = value} [, ... ] ) ]
+[ COMPRESS | NOCOMPRESS ]
+[ TABLESPACE tablespace_name ]
+PARTITION BY {RANGE | LIST} (partition_key) SUBPARTITION BY {RANGE | LIST | HASH} (subpartition_key)
+(
+  PARTITION partition_name1 [ VALUES LESS THAN (val1) | VALUES (val1[, ...]) ] [ TABLESPACE tablespace ]
+  (
+       { SUBPARTITION subpartition_name1 [ VALUES LESS THAN (val1_1) | VALUES (val1_1[, ...])]  [ TABLESPACE tablespace ] } [, ...]
+  )[, ...]
+)[ { ENABLE | DISABLE } ROW MOVEMENT ];
+```
+
+- 列约束column_constraint：
+
+  ```ebnf+diagram
+  column_constraint ::= [ CONSTRAINT constraint_name ]
+  { NOT NULL |
+    NULL |
+    CHECK ( expression ) |
+    DEFAULT default_e xpr |
+    GENERATED ALWAYS AS ( generation_expr ) STORED |
+    UNIQUE index_parameters |
+    PRIMARY KEY index_parameters |
+    REFERENCES reftable [ ( refcolumn ) ] [ MATCH FULL | MATCH PARTIAL | MATCH SIMPLE ]
+          [ ON DELETE action ] [ ON UPDATE action ] }
+  [ DEFERRABLE | NOT DEFERRABLE | INITIALLY DEFERRED | INITIALLY IMMEDIATE ]
+  ```
+
+- 表约束table_constraint：
+
+  ```ebnf+diagram
+  table_constraint ::= [ CONSTRAINT constraint_name ]
+  { CHECK ( expression ) |
+    UNIQUE ( column_name [, ... ] ) index_parameters |
+    PRIMARY KEY ( column_name [, ... ] ) index_parameters |
+    FOREIGN KEY ( column_name [, ... ] ) REFERENCES reftable [ ( refcolumn [, ... ] ) ]
+        [ MATCH FULL | MATCH PARTIAL | MATCH SIMPLE ] [ ON DELETE action ] [ ON UPDATE action ] }
+  [ DEFERRABLE | NOT DEFERRABLE | INITIALLY DEFERRED | INITIALLY IMMEDIATE ]
+  ```
+
+- like选项like_option：
+
+  ```ebnf+diagram
+  like_option ::= { INCLUDING | EXCLUDING } { DEFAULTS | GENERATED | CONSTRAINTS | INDEXES | STORAGE | COMMENTS | RELOPTIONS| ALL }
+  ```
+
+- 索引存储参数index_parameters：
+
+  ```ebnf+diagram
+  index_parameters ::= [ WITH ( {storage_parameter = value} [, ... ] ) ]
+  [ USING INDEX TABLESPACE tablespace_name ]
+  ```
+
+## 参数说明
+
+- **IF NOT EXISTS**
+
+  如果已经存在相同名称的表，不会抛出一个错误，而会发出一个通知，告知表关系已存在。
+
+- **subpartition_table_name**
+
+  二级分区表的名称。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- **column_name**
+
+  新表中要创建的字段名。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- **data_type**
+
+  字段的数据类型。
+
+- **COLLATE collation**
+
+  COLLATE子句指定列的排序规则（该列必须是可排列的数据类型）。如果没有指定，则使用默认的排序规则。排序规则可以使用“select * from pg_collation;”命令从pg_collation系统表中查询，默认的排序规则为查询结果中以default开始的行。
+
+- **CONSTRAINT constraint_name**
+
+  列约束或表约束的名称。可选的约束子句用于声明约束，新行或者更新的行必须满足这些约束才能成功插入或更新。
+
+  定义约束有两种方法：
+
+  - 列约束：作为一个列定义的一部分，仅影响该列。
+  - 表约束：不和某个列绑在一起，可以作用于多个列。
+
+- **LIKE source_table [ like_option … ]**
+
+二级分区表暂不支持该功能。
+
+- **WITH ( storage_parameter [= value] [, … ] )**
+
+  这个子句为表或索引指定一个可选的存储参数。参数的详细描述如下所示：
+
+  - FILLFACTOR
+
+    一个表的填充因子（fillfactor）是一个介于10和100之间的百分数。100（完全填充）是默认值。如果指定了较小的填充因子，INSERT操作仅按照填充因子指定的百分率填充表页。每个页上的剩余空间将用于在该页上更新行，这就使得UPDATE有机会在同一页上放置同一条记录的新版本，这比把新版本放置在其他页上更有效。对于一个从不更新的表将填充因子设为100是最佳选择，但是对于频繁更新的表，选择较小的填充因子则更加合适。该参数对于列存表没有意义。
+
+    取值范围: 10~100
+
+  - ORIENTATION
+
+    决定了表的数据的存储方式。
+
+    取值范围:
+
+    - COLUMN：表的数据将以列式存储。
+
+    - ROW（缺省值）：表的数据将以行式存储。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** orientation不支持修改。
+
+  - COMPRESSION
+
+    - 列存表的有效值为LOW/MIDDLE/HIGH/YES/NO，压缩级别依次升高，默认值为LOW。
+    - 行存表不支持压缩。
+
+  - MAX_BATCHROW
+
+    指定了在数据加载过程中一个存储单元可以容纳记录的最大数目。该参数只对列存表有效。
+
+    取值范围: 10000~60000，默认60000。
+
+  - PARTIAL_CLUSTER_ROWS
+
+    指定了在数据加载过程中进行将局部聚簇存储的记录数目。该参数只对列存表有效。
+
+    取值范围: 大于等于MAX_BATCHROW，建议取值为MAX_BATCHROW的整数倍数。
+
+  - DELTAROW_THRESHOLD
+
+    预留参数。该参数只对列存表有效。
+
+    取值范围: 0～9999
+
+- **COMPRESS / NOCOMPRESS**
+
+  创建一个新表时，需要在创建表语句中指定关键字COMPRESS，这样，当对该表进行批量插入时就会触发压缩特性。该特性会在页范围内扫描所有元组数据，生成字典、压缩元组数据并进行存储。指定关键字NOCOMPRESS则不对表进行压缩。行存表不支持压缩。
+
+  缺省值为NOCOMPRESS，即不对元组数据进行压缩。
+
+- **TABLESPACE tablespace_name**
+
+  指定新表将要在tablespace_name表空间内创建。如果没有声明，将使用默认表空间。
+
+- **PARTITION BY {RANGE | LIST | HASH} (partition_key)**
+
+  - 对于partition_key，分区策略的分区键仅支持1列。
+  - 分区键支持的数据类型和一级分区表约束保持一致。
+
+- **SUBPARTITION BY {RANGE | LIST | HASH} (subpartition_key)**
+
+  - 对于subpartition_key，分区策略的分区键仅支持1列。
+  - 分区键支持的数据类型和一级分区表约束保持一致。
+
+- **{ ENABLE | DISABLE } ROW MOVEMENT**
+
+  行迁移开关。
+
+  如果进行UPDATE操作时，更新了元组在分区键上的值，造成了该元组所在分区发生变化，就会根据该开关给出报错信息，或者进行元组在分区间的转移。
+
+  取值范围:
+
+  - ENABLE（缺省值）：行迁移开关打开。
+  - DISABLE：行迁移开关关闭。
+
+- **NOT NULL**
+
+  字段值不允许为NULL。ENABLE用于语法兼容，可省略。
+
+- **NULL**
+
+  字段值允许NULL ，这是缺省。
+
+  这个子句只是为和非标准SQL数据库兼容。不建议使用。
+
+- **CHECK (condition) [ NO INHERIT ]**
+
+  CHECK约束声明一个布尔表达式，每次要插入的新行或者要更新的行的新值必须使表达式结果为真或未知才能成功，否则会抛出一个异常并且不会修改数据库。
+
+  声明为字段约束的检查约束应该只引用该字段的数值，而在表约束里出现的表达式可以引用多个字段。
+
+  用NO INHERIT标记的约束将不会传递到子表中去。
+
+  ENABLE用于语法兼容，可省略。
+
+- **DEFAULT default_expr**
+
+  DEFAULT子句给字段指定缺省值。该数值可以是任何不含变量的表达式(不允许使用子查询和对本表中的其他字段的交叉引用)。缺省表达式的数据类型必须和字段类型匹配。
+
+  缺省表达式将被用于任何未声明该字段数值的插入操作。如果没有指定缺省值则缺省值为NULL 。
+
+- **GENERATED ALWAYS AS ( generation_expr ) STORED**
+
+  该子句将字段创建为生成列，生成列的值在写入（插入或更新）数据时由generation_expr计算得到，STORED表示像普通列一样存储生成列的值。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  >
+  > - 生成表达式不能以任何方式引用当前行以外的其他数据。生成表达式不能引用其他生成列，不能引用系统列。生成表达式不能返回结果集，不能使用子查询，不能使用聚集函数，不能使用窗口函数。生成表达式调用的函数只能是不可变（IMMUTABLE）函数。
+  > - 不能为生成列指定默认值。
+  > - 生成列不能作为分区键的一部分。
+  > - 生成列不能和ON UPDATE约束字句的CASCADE，SET NULL，SET DEFAULT动作同时指定。生成列不能和ON DELETE约束字句的SET NULL，SET DEFAULT动作同时指定。
+  > - 修改和删除生成列的方法和普通列相同。删除生成列依赖的普通列，生成列被自动删除。不能改变生成列所依赖的列的类型。
+  > - 生成列不能被直接写入。在INSERT或UPDATE命令中，不能为生成列指定值，但是可以指定关键字DEFAULT。
+  > - 生成列的权限控制和普通列一样。
+  > - 不能为生成列指定默认值。
+  > - 生成列不能作为分区键的一部分。
+  > - 生成列不能和ON UPDATE约束字句的CASCADE，SET NULL，SET DEFAULT动作同时指定。生成列不能和ON DELETE约束字句的SET NULL，SET DEFAULT动作同时指定。
+  > - 修改和删除生成列的方法和普通列相同。删除生成列依赖的普通列，生成列被自动删除。不能改变生成列所依赖的列的类型。
+  > - 生成列不能被直接写入。在INSERT或UPDATE命令中, 不能为生成列指定值, 但是可以指定关键字DEFAULT。
+  > - 生成列的权限控制和普通列一样。
+  > - 列存表、内存表MOT不支持生成列。外表中仅postgres_fdw支持生成列。
+
+- **UNIQUE index_parameters**
+
+  **UNIQUE ( column_name [, … ] ) index_parameters**
+
+  UNIQUE约束表示表里的一个字段或多个字段的组合必须在全表范围内唯一。
+
+  对于唯一约束，NULL被认为是互不相等的。
+
+- **PRIMARY KEY index_parameters**
+
+  **PRIMARY KEY ( column_name [, … ] ) index_parameters**
+
+  主键约束声明表中的一个或者多个字段只能包含唯一的非NULL值。
+
+  一个表只能声明一个主键。
+
+- **DEFERRABLE | NOT DEFERRABLE**
+
+  这两个关键字设置该约束是否可推迟。一个不可推迟的约束将在每条命令之后马上检查。可推迟约束可以推迟到事务结尾使用SET CONSTRAINTS命令检查。缺省是NOT DEFERRABLE。目前，UNIQUE约束、主键约束、外键约束可以接受这个子句。所有其他约束类型都是不可推迟的。
+
+- **INITIALLY IMMEDIATE | INITIALLY DEFERRED**
+
+  如果约束是可推迟的，则这个子句声明检查约束的缺省时间。
+
+  - 如果约束是INITIALLY IMMEDIATE（缺省），则在每条语句执行之后就立即检查它；
+  - 如果约束是INITIALLY DEFERRED ，则只有在事务结尾才检查它。
+
+  约束检查的时间可以用SET CONSTRAINTS命令修改。
+
+- **USING INDEX TABLESPACE tablespace_name**
+
+  为UNIQUE或PRIMARY KEY约束相关的索引声明一个表空间。如果没有提供这个子句，这个索引将在default_tablespace中创建，如果default_tablespace为空，将使用数据库的缺省表空间。
+
+## 示例
+
+- 示例1：创建各种组合类型的二级分区表
+
+  ```sql
+  CREATE TABLE list_list
+  (
+      month_code VARCHAR2 ( 30 ) NOT NULL ,
+      dept_code  VARCHAR2 ( 30 ) NOT NULL ,
+      user_no    VARCHAR2 ( 30 ) NOT NULL ,
+      sales_amt  int
+  )
+  PARTITION BY LIST (month_code) SUBPARTITION BY LIST (dept_code)
+  (
+    PARTITION p_201901 VALUES ( '201902' )
+    (
+      SUBPARTITION p_201901_a VALUES ( '1' ),
+      SUBPARTITION p_201901_b VALUES ( '2' )
+    ),
+    PARTITION p_201902 VALUES ( '201903' )
+    (
+      SUBPARTITION p_201902_a VALUES ( '1' ),
+      SUBPARTITION p_201902_b VALUES ( '2' )
+    )
+  );
+  insert into list_list values('201902', '1', '1', 1);
+  insert into list_list values('201902', '2', '1', 1);
+  insert into list_list values('201902', '1', '1', 1);
+  insert into list_list values('201903', '2', '1', 1);
+  insert into list_list values('201903', '1', '1', 1);
+  insert into list_list values('201903', '2', '1', 1);
+  select * from list_list;
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201903     | 2         | 1       |         1
+   201903     | 2         | 1       |         1
+   201903     | 1         | 1       |         1
+   201902     | 2         | 1       |         1
+   201902     | 1         | 1       |         1
+   201902     | 1         | 1       |         1
+  (6 rows)
+  
+  drop table list_list;
+  CREATE TABLE list_hash
+  (
+      month_code VARCHAR2 ( 30 ) NOT NULL ,
+      dept_code  VARCHAR2 ( 30 ) NOT NULL ,
+      user_no    VARCHAR2 ( 30 ) NOT NULL ,
+      sales_amt  int
+  )
+  PARTITION BY LIST (month_code) SUBPARTITION BY HASH (dept_code)
+  (
+    PARTITION p_201901 VALUES ( '201902' )
+    (
+      SUBPARTITION p_201901_a,
+      SUBPARTITION p_201901_b
+    ),
+    PARTITION p_201902 VALUES ( '201903' )
+    (
+      SUBPARTITION p_201902_a,
+      SUBPARTITION p_201902_b
+    )
+  );
+  insert into list_hash values('201902', '1', '1', 1);
+  insert into list_hash values('201902', '2', '1', 1);
+  insert into list_hash values('201902', '3', '1', 1);
+  insert into list_hash values('201903', '4', '1', 1);
+  insert into list_hash values('201903', '5', '1', 1);
+  insert into list_hash values('201903', '6', '1', 1);
+  select * from list_hash;
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201903     | 4         | 1       |         1
+   201903     | 5         | 1       |         1
+   201903     | 6         | 1       |         1
+   201902     | 2         | 1       |         1
+   201902     | 3         | 1       |         1
+   201902     | 1         | 1       |         1
+  (6 rows)
+  
+  drop table list_hash;
+  CREATE TABLE list_range
+  (
+      month_code VARCHAR2 ( 30 ) NOT NULL ,
+      dept_code  VARCHAR2 ( 30 ) NOT NULL ,
+      user_no    VARCHAR2 ( 30 ) NOT NULL ,
+      sales_amt  int
+  )
+  PARTITION BY LIST (month_code) SUBPARTITION BY RANGE (dept_code)
+  (
+    PARTITION p_201901 VALUES ( '201902' )
+    (
+      SUBPARTITION p_201901_a values less than ('4'),
+      SUBPARTITION p_201901_b values less than ('6')
+    ),
+    PARTITION p_201902 VALUES ( '201903' )
+    (
+      SUBPARTITION p_201902_a values less than ('3'),
+      SUBPARTITION p_201902_b values less than ('6')
+    )
+  );
+  insert into list_range values('201902', '1', '1', 1);
+  insert into list_range values('201902', '2', '1', 1);
+  insert into list_range values('201902', '3', '1', 1);
+  insert into list_range values('201903', '4', '1', 1);
+  insert into list_range values('201903', '5', '1', 1);
+  insert into list_range values('201903', '6', '1', 1);
+  ERROR:  inserted partition key does not map to any table partition
+  select * from list_range;
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201903     | 4         | 1       |         1
+   201903     | 5         | 1       |         1
+   201902     | 1         | 1       |         1
+   201902     | 2         | 1       |         1
+   201902     | 3         | 1       |         1
+  (5 rows)
+  
+  drop table list_range;
+  CREATE TABLE range_list
+  (
+      month_code VARCHAR2 ( 30 ) NOT NULL ,
+      dept_code  VARCHAR2 ( 30 ) NOT NULL ,
+      user_no    VARCHAR2 ( 30 ) NOT NULL ,
+      sales_amt  int
+  )
+  PARTITION BY RANGE (month_code) SUBPARTITION BY LIST (dept_code)
+  (
+    PARTITION p_201901 VALUES LESS THAN( '201903' )
+    (
+      SUBPARTITION p_201901_a values ('1'),
+      SUBPARTITION p_201901_b values ('2')
+    ),
+    PARTITION p_201902 VALUES LESS THAN( '201904' )
+    (
+      SUBPARTITION p_201902_a values ('1'),
+      SUBPARTITION p_201902_b values ('2')
+    )
+  );
+  insert into range_list values('201902', '1', '1', 1);
+  insert into range_list values('201902', '2', '1', 1);
+  insert into range_list values('201902', '1', '1', 1);
+  insert into range_list values('201903', '2', '1', 1);
+  insert into range_list values('201903', '1', '1', 1);
+  insert into range_list values('201903', '2', '1', 1);
+  select * from range_list;
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201902     | 2         | 1       |         1
+   201902     | 1         | 1       |         1
+   201902     | 1         | 1       |         1
+   201903     | 2         | 1       |         1
+   201903     | 2         | 1       |         1
+   201903     | 1         | 1       |         1
+  (6 rows)
+  
+  drop table range_list;
+  CREATE TABLE range_hash
+  (
+      month_code VARCHAR2 ( 30 ) NOT NULL ,
+      dept_code  VARCHAR2 ( 30 ) NOT NULL ,
+      user_no    VARCHAR2 ( 30 ) NOT NULL ,
+      sales_amt  int
+  )
+  PARTITION BY RANGE (month_code) SUBPARTITION BY HASH (dept_code)
+  (
+    PARTITION p_201901 VALUES LESS THAN( '201903' )
+    (
+      SUBPARTITION p_201901_a,
+      SUBPARTITION p_201901_b
+    ),
+    PARTITION p_201902 VALUES LESS THAN( '201904' )
+    (
+      SUBPARTITION p_201902_a,
+      SUBPARTITION p_201902_b
+    )
+  );
+  insert into range_hash values('201902', '1', '1', 1);
+  insert into range_hash values('201902', '2', '1', 1);
+  insert into range_hash values('201902', '1', '1', 1);
+  insert into range_hash values('201903', '2', '1', 1);
+  insert into range_hash values('201903', '1', '1', 1);
+  insert into range_hash values('201903', '2', '1', 1);
+  select * from range_hash;
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201902     | 2         | 1       |         1
+   201902     | 1         | 1       |         1
+   201902     | 1         | 1       |         1
+   201903     | 2         | 1       |         1
+   201903     | 2         | 1       |         1
+   201903     | 1         | 1       |         1
+  (6 rows)
+  
+  drop table range_hash;
+  CREATE TABLE range_range
+  (
+      month_code VARCHAR2 ( 30 ) NOT NULL ,
+      dept_code  VARCHAR2 ( 30 ) NOT NULL ,
+      user_no    VARCHAR2 ( 30 ) NOT NULL ,
+      sales_amt  int
+  )
+  PARTITION BY RANGE (month_code) SUBPARTITION BY RANGE (dept_code)
+  (
+    PARTITION p_201901 VALUES LESS THAN( '201903' )
+    (
+      SUBPARTITION p_201901_a VALUES LESS THAN( '2' ),
+      SUBPARTITION p_201901_b VALUES LESS THAN( '3' )
+    ),
+    PARTITION p_201902 VALUES LESS THAN( '201904' )
+    (
+      SUBPARTITION p_201902_a VALUES LESS THAN( '2' ),
+      SUBPARTITION p_201902_b VALUES LESS THAN( '3' )
+    )
+  );
+  insert into range_range values('201902', '1', '1', 1);
+  insert into range_range values('201902', '2', '1', 1);
+  insert into range_range values('201902', '1', '1', 1);
+  insert into range_range values('201903', '2', '1', 1);
+  insert into range_range values('201903', '1', '1', 1);
+  insert into range_range values('201903', '2', '1', 1);
+  select * from range_range;
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201902     | 1         | 1       |         1
+   201902     | 1         | 1       |         1
+   201902     | 2         | 1       |         1
+   201903     | 1         | 1       |         1
+   201903     | 2         | 1       |         1
+   201903     | 2         | 1       |         1
+  (6 rows)
+  
+  drop table range_range;
+  ```
+  
+- 示例2：对二级分区表进行truncate操作
+
+  ```sql
+  CREATE TABLE list_list
+  (
+      month_code VARCHAR2 ( 30 ) NOT NULL ,
+      dept_code  VARCHAR2 ( 30 ) NOT NULL ,
+      user_no    VARCHAR2 ( 30 ) NOT NULL ,
+      sales_amt  int
+  )
+  PARTITION BY LIST (month_code) SUBPARTITION BY LIST (dept_code)
+  (
+    PARTITION p_201901 VALUES ( '201902' )
+    (
+      SUBPARTITION p_201901_a VALUES ( '1' ),
+      SUBPARTITION p_201901_b VALUES ( default )
+    ),
+    PARTITION p_201902 VALUES ( '201903' )
+    (
+      SUBPARTITION p_201902_a VALUES ( '1' ),
+      SUBPARTITION p_201902_b VALUES ( '2' )
+    )
+  );
+  insert into list_list values('201902', '1', '1', 1);
+  insert into list_list values('201902', '2', '1', 1);
+  insert into list_list values('201902', '1', '1', 1);
+  insert into list_list values('201903', '2', '1', 1);
+  insert into list_list values('201903', '1', '1', 1);
+  insert into list_list values('201903', '2', '1', 1);
+  select * from list_list;
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201903     | 2         | 1       |         1
+   201903     | 2         | 1       |         1
+   201903     | 1         | 1       |         1
+   201902     | 2         | 1       |         1
+   201902     | 1         | 1       |         1
+   201902     | 1         | 1       |         1
+  (6 rows)
+  
+  select * from list_list partition (p_201901);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201902     | 2         | 1       |         1
+   201902     | 1         | 1       |         1
+   201902     | 1         | 1       |         1
+  (3 rows)
+  
+  alter table list_list truncate partition p_201901;
+  select * from list_list partition (p_201901);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+  (0 rows)
+  
+  select * from list_list partition (p_201902);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201903     | 2         | 1       |         1
+   201903     | 2         | 1       |         1
+   201903     | 1         | 1       |         1
+  (3 rows)
+  
+  alter table list_list truncate partition p_201902;
+  select * from list_list partition (p_201902);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+  (0 rows)
+  
+  select * from list_list;
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+  (0 rows)
+  
+  insert into list_list values('201902', '1', '1', 1);
+  insert into list_list values('201902', '2', '1', 1);
+  insert into list_list values('201902', '1', '1', 1);
+  insert into list_list values('201903', '2', '1', 1);
+  insert into list_list values('201903', '1', '1', 1);
+  insert into list_list values('201903', '2', '1', 1);
+  select * from list_list subpartition (p_201901_a);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201902     | 1         | 1       |         1
+   201902     | 1         | 1       |         1
+  (2 rows)
+  
+  alter table list_list truncate subpartition p_201901_a;
+  select * from list_list subpartition (p_201901_a);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+  (0 rows)
+  
+  select * from list_list subpartition (p_201901_b);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201902     | 2         | 1       |         1
+  (1 row)
+  
+  alter table list_list truncate subpartition p_201901_b;
+  select * from list_list subpartition (p_201901_b);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+  (0 rows)
+  
+  select * from list_list subpartition (p_201902_a);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201903     | 1         | 1       |         1
+  (1 row)
+  
+  alter table list_list truncate subpartition p_201902_a;
+  select * from list_list subpartition (p_201902_a);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+  (0 rows)
+  
+  select * from list_list subpartition (p_201902_b);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201903     | 2         | 1       |         1
+   201903     | 2         | 1       |         1
+  (2 rows)
+  
+  alter table list_list truncate subpartition p_201902_b;
+  select * from list_list subpartition (p_201902_b);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+  (0 rows)
+  
+  select * from list_list;
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+  (0 rows)
+  
+  drop table list_list;
+  ```
+  
+- 示例3：对二级分区表进行split操作
+
+  ```sql
+  CREATE TABLE list_list
+  (
+      month_code VARCHAR2 ( 30 ) NOT NULL ,
+      dept_code  VARCHAR2 ( 30 ) NOT NULL ,
+      user_no    VARCHAR2 ( 30 ) NOT NULL ,
+      sales_amt  int
+  )
+  PARTITION BY LIST (month_code) SUBPARTITION BY LIST (dept_code)
+  (
+    PARTITION p_201901 VALUES ( '201902' )
+    (
+      SUBPARTITION p_201901_a VALUES ( '1' ),
+      SUBPARTITION p_201901_b VALUES ( default )
+    ),
+    PARTITION p_201902 VALUES ( '201903' )
+    (
+      SUBPARTITION p_201902_a VALUES ( '1' ),
+      SUBPARTITION p_201902_b VALUES ( default )
+    )
+  );
+  insert into list_list values('201902', '1', '1', 1);
+  insert into list_list values('201902', '2', '1', 1);
+  insert into list_list values('201902', '1', '1', 1);
+  insert into list_list values('201903', '2', '1', 1);
+  insert into list_list values('201903', '1', '1', 1);
+  insert into list_list values('201903', '2', '1', 1);
+  select * from list_list;
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201903     | 2         | 1       |         1
+   201903     | 2         | 1       |         1
+   201903     | 1         | 1       |         1
+   201902     | 2         | 1       |         1
+   201902     | 1         | 1       |         1
+   201902     | 1         | 1       |         1
+  (6 rows)
+  
+  select * from list_list subpartition (p_201901_a);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201902     | 1         | 1       |         1
+   201902     | 1         | 1       |         1
+  (2 rows)
+  
+  select * from list_list subpartition (p_201901_b);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201902     | 2         | 1       |         1
+  (1 row)
+  
+  alter table list_list split subpartition p_201901_b values (2) into
+  (
+   subpartition p_201901_b,
+   subpartition p_201901_c
+  );
+  select * from list_list subpartition (p_201901_a);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201902     | 1         | 1       |         1
+   201902     | 1         | 1       |         1
+  (2 rows)
+  
+  select * from list_list subpartition (p_201901_b);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201902     | 2         | 1       |         1
+  (1 row)
+  
+  select * from list_list subpartition (p_201901_c);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+  (0 rows)
+  
+  select * from list_list partition (p_201901);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201902     | 2         | 1       |         1
+   201902     | 1         | 1       |         1
+   201902     | 1         | 1       |         1
+  (3 rows)
+  
+  select * from list_list subpartition (p_201902_a);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201903     | 1         | 1       |         1
+  (1 row)
+  
+  select * from list_list subpartition (p_201902_b);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201903     | 2         | 1       |         1
+   201903     | 2         | 1       |         1
+  (2 rows)
+  
+  alter table list_list split subpartition p_201902_b values (3) into
+  (
+   subpartition p_201902_b,
+   subpartition p_201902_c
+  );
+  select * from list_list subpartition (p_201902_a);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201903     | 1         | 1       |         1
+  (1 row)
+  
+  select * from list_list subpartition (p_201902_b);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+  (0 rows)
+  
+  select * from list_list subpartition (p_201902_c);
+   month_code | dept_code | user_no | sales_amt
+  ------------+-----------+---------+-----------
+   201903     | 2         | 1       |         1
+   201903     | 2         | 1       |         1
+  (2 rows)
+  
+  drop table list_list;
+  ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/63-CREATE-TABLESPACE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/63-CREATE-TABLESPACE.md
new file mode 100644
index 0000000000000000000000000000000000000000..87ec9c3120e67bf52df1a08ce985421215994a51
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/63-CREATE-TABLESPACE.md
@@ -0,0 +1,136 @@
+---
+title: CREATE TABLESPACE
+summary: CREATE TABLESPACE
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE TABLESPACE
+
+## 功能描述
+
+在数据库中创建一个新的表空间。
+
+## 注意事项
+
+- 系统管理员或者继承了内置角色gs_roles_tablespace权限的用户可以创建表空间。
+- 不允许在一个事务块内部执行CREATE TABLESPACE。
+- 执行CREATE TABLESPACE失败，如果内部创建目录（文件）操作成功了就会产生残留的目录（文件），重新创建时需要用户手动清理表空间指定的目录下残留的内容。如果在创建过程中涉及到数据目录下的表空间软连接残留，需要先将软连接的残留文件删除，再重新执行OM相关操作。
+- CREATE TABLESPACE不支持两阶段事务，如果部分节点执行失败，不支持回滚。
+- 创建表空间前的准备工作参考下述参数说明。
+- 在HCS等场景下一般不建议用户使用自定义的表空间。原因：用户自定义表空间通常配合主存（即默认表空间所在的存储设备，如磁盘）以外的其它存储介质使用，以隔离不同业务可以使用的IO资源，而在HCS等场景下，存储设备都是采用标准化的配置，无其它可用的存储介质，自定义表空间使用不当不利于系统长稳运行以及影响整体性能，因此建议使用默认表空间即可。
+
+## 语法格式
+
+```ebnf+diagram
+CreateTablespace ::= CREATE TABLESPACE tablespace_name
+    [ OWNER user_name ] [RELATIVE] LOCATION 'directory' [ MAXSIZE 'space_size' ]
+    [with_option_clause];
+```
+
+其中普通表空间的with_option_clause为：
+
+```ebnf+diagram
+with_option_clause ::= WITH ( {filesystem= { 'general'| "general" | general} |
+    random_page_cost = { 'value ' | value } |
+    seq_page_cost = { 'value ' | value }}[,...]);
+```
+
+## 参数说明
+
+- **tablespace_name**
+
+  要创建的表空间名称。
+
+  表空间名称不能和MogDB中的其他表空间重名，且名称不能以“pg”开头，这样的名称留给系统表空间使用。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- **OWNER user_name**
+
+  指定该表空间的所有者。缺省时，新表空间的所有者是当前用户。
+
+  只有系统管理员可以创建表空间，但是可以通过OWNER子句把表空间的所有权赋给其他非系统管理员。
+
+  取值范围: 字符串，已存在的用户。
+
+- **RELATIVE**
+
+  使用相对路径，LOCATION目录是相对于各个数据库节点数据目录下的。
+
+  目录层次：数据库节点的数据目录/pg_location/相对路径
+
+  相对路径最多指定两层。
+
+- **LOCATION directory**
+
+    用于表空间的目录，对于目录有如下要求：
+
+  - MogDB系统用户必须对该目录拥有读写权限，并且目录为空。如果该目录不存在，将由系统自动创建。
+  - 目录必须是绝对路径，目录中不得含有特殊字符（如$,&gt; 等）。
+  - 目录不允许指定在数据库数据目录下。
+  - 目录需为本地路径。
+
+    取值范围: 字符串，有效的目录。
+
+- **MAXSIZE 'space_size'**
+
+  指定表空间在单个数据库节点上的最大值。
+
+  取值范围: 字符串格式为正整数+单位，单位当前支持K/M/G/T/P。解析后的数值以K为单位，且范围不能够超过64比特表示的有符号整数，即1KB~9007199254740991KB。
+
+- **random_page_cost**
+
+  指定随机读取page的开销。
+
+  取值范围: 0~1.79769e+308。
+
+  默认值：使用GUC参数random_page_cost的值。
+
+- **seq_page_cost**
+
+  指定顺序读取page的开销。
+
+  取值范围: 0~1.79769e+308。
+
+  默认值：使用GUC参数seq_page_cost的值。
+
+## 示例
+
+```sql
+--创建表空间。
+mogdb=# CREATE TABLESPACE ds_location1 RELATIVE LOCATION 'tablespace/tablespace_1';
+
+--创建用户joe。
+mogdb=# CREATE ROLE joe IDENTIFIED BY 'xxxxxxxxx';
+
+--创建用户jay。
+mogdb=# CREATE ROLE jay IDENTIFIED BY 'xxxxxxxxx';
+
+--创建表空间，且所有者指定为用户joe。
+mogdb=# CREATE TABLESPACE ds_location2 OWNER joe RELATIVE LOCATION 'tablespace/tablespace_1';
+
+--把表空间ds_location1重命名为ds_location3。
+mogdb=# ALTER TABLESPACE ds_location1 RENAME TO ds_location3;
+
+--改变表空间ds_location2的所有者。
+mogdb=# ALTER TABLESPACE ds_location2 OWNER TO jay;
+
+--删除表空间。
+mogdb=# DROP TABLESPACE ds_location2;
+mogdb=# DROP TABLESPACE ds_location3;
+
+--删除用户。
+mogdb=# DROP ROLE joe;
+mogdb=# DROP ROLE jay;
+```
+
+## 相关链接
+
+[CREATE DATABASE](44-CREATE-DATABASE)，[CREATE TABLE](60-CREATE-TABLE)，[CREATE INDEX](50-CREATE-INDEX)，[DROP TABLESPACE](96-DROP-TABLESPACE)，[ALTER TABLESPACE](24-ALTER-TABLESPACE)
+
+## 优化建议
+
+- create tablespace
+
+  不建议在事务内部创建表空间。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/64-CREATE-TEXT-SEARCH-CONFIGURATION.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/64-CREATE-TEXT-SEARCH-CONFIGURATION.md
new file mode 100644
index 0000000000000000000000000000000000000000..a7a1433b733d8f1bd43c9999598775dd967d9b13
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/64-CREATE-TEXT-SEARCH-CONFIGURATION.md
@@ -0,0 +1,96 @@
+---
+title: CREATE TEXT SEARCH CONFIGURATION
+summary: CREATE TEXT SEARCH CONFIGURATION
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE TEXT SEARCH CONFIGURATION
+
+## 功能描述
+
+创建新的文本搜索配置。一个文本搜索配置声明一个能将一个字符串划分成符号的文本搜索解析器，加上可以用于确定搜索对哪些标记感兴趣的字典。
+
+## 注意事项
+
+- 若仅声明分析器，那么新的文本搜索配置初始没有从符号类型到词典的映射， 因此会忽略所有的单词。后面必须调用ALTER TEXT SEARCH CONFIGURATION命令创建映射使配置生效。如果声明了COPY选项，那么会自动拷贝指定的文本搜索配置的解析器、映射、配置选项等信息。
+- 若模式名称已给出，那么文本搜索配置会在声明的模式中创建。否则会在当前模式创建。
+- 定义文本搜索配置的用户成为其所有者。
+- PARSER和COPY选项是互相排斥的，因为当一个现有配置被复制，其分析器配置也被复制了。
+- 若仅声明分析器，那么新的文本搜索配置初始没有从符号类型到词典的映射， 因此会忽略所有的单词。
+
+## 语法格式
+
+```ebnf+diagram
+CreateTextSearchConfiguration ::= CREATE TEXT SEARCH CONFIGURATION name
+    ( PARSER = parser_name | COPY = source_config )
+    [ WITH ( {configuration_option = value} [, ...] )];
+```
+
+## 参数说明
+
+- **name**
+
+  要创建的文本搜索配置的名称。该名称可以有模式修饰。
+
+- **parser_name**
+
+  用于该配置的文本搜索分析器的名称。
+
+- **source_config**
+
+  要复制的现有文本搜索配置的名称。
+
+- **configuration_option**
+
+  文本搜索配置的配置参数，主要是针对parser_name执行的解析器，或者source_config隐含的解析器而言的。
+
+  取值范围: 目前共支持default、ngram两种类型的解析器，其中default类型的解析器没有对应的configuration_option，ngram类型解析器对应的configuration_option如表1所示。
+
+  **表 1** ngram类型解析器对应的配置参数 <a id="ngram"> </a>
+
+  | 解析器             | 配置参数             | 参数描述                                                     | 取值范围                   |
+  | :------------------------------------- | :------------------- | :-------------------------- | :------------------------- |
+  | ngram              | gram_size            | 分词长度。                                                   | 正整数，1~4<br />默认值：2 |
+  | punctuation_ignore | 是否忽略标点符号。   | - true（默认值）：忽略标点符号。<br />- false：不忽略标点符号。 |                            |
+  | grapsymbol_ignore  | 是否忽略图形化字符。 | - true：忽略图形化字符。<br />- false（默认值）：不忽略图形化字符。 |                            |
+
+## 示例
+
+```sql
+--创建文本搜索配置。
+mogdb=# CREATE TEXT SEARCH CONFIGURATION ngram2 (parser=ngram) WITH (gram_size = 2, grapsymbol_ignore = false);
+
+--创建文本搜索配置。
+mogdb=# CREATE TEXT SEARCH CONFIGURATION ngram3 (copy=ngram2) WITH (gram_size = 2, grapsymbol_ignore = false);
+
+--添加类型映射。
+mogdb=# ALTER TEXT SEARCH CONFIGURATION ngram2 ADD MAPPING FOR multisymbol WITH simple;
+
+--创建用户joe。
+mogdb=# CREATE USER joe IDENTIFIED BY 'xxxxxx';
+
+--修改文本搜索配置的所有者。
+mogdb=# ALTER TEXT SEARCH CONFIGURATION ngram2 OWNER TO joe;
+
+--修改文本搜索配置的schema。
+mogdb=# ALTER TEXT SEARCH CONFIGURATION ngram2 SET SCHEMA joe;
+
+--重命名文本搜索配置。
+mogdb=# ALTER TEXT SEARCH CONFIGURATION joe.ngram2 RENAME TO ngram_2;
+
+--删除类型映射。
+mogdb=# ALTER TEXT SEARCH CONFIGURATION joe.ngram_2 DROP MAPPING IF EXISTS FOR multisymbol;
+
+--删除文本搜索配置。
+mogdb=# DROP TEXT SEARCH CONFIGURATION joe.ngram_2;
+mogdb=# DROP TEXT SEARCH CONFIGURATION ngram3;
+
+--删除Schema及用户joe。
+mogdb=# DROP SCHEMA IF EXISTS joe CASCADE;
+mogdb=# DROP ROLE IF EXISTS joe;
+```
+
+## 相关链接
+
+[ALTER TEXT SEARCH CONFIGURATION](25-ALTER-TEXT-SEARCH-CONFIGURATION)，  [DROP TEXT SEARCH CONFIGURATION](97-DROP-TEXT-SEARCH-CONFIGURATION)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/65-CREATE-TEXT-SEARCH-DICTIONARY.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/65-CREATE-TEXT-SEARCH-DICTIONARY.md
new file mode 100644
index 0000000000000000000000000000000000000000..778b2837c8aff727246ed97f9f776138092a3800
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/65-CREATE-TEXT-SEARCH-DICTIONARY.md
@@ -0,0 +1,152 @@
+---
+title: CREATE TEXT SEARCH DICTIONARY
+summary: CREATE TEXT SEARCH DICTIONARY
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE TEXT SEARCH DICTIONARY
+
+## 功能描述
+
+创建一个新的全文检索词典。词典是一种指定在全文检索时识别特定词并处理的方法。
+
+词典的创建依赖于预定义模板（在系统表**PG_TS_TEMPLATE**中定义），支持创建五种类型的词典，分别是Simple、Ispell、Synonym、Thesaurus、以及Snowball，每种类型的词典可以完成不同的任务。
+
+## 注意事项
+
+- 具有SYSADMIN权限的用户可以执行创建词典操作，创建该词典的用户自动成为其所有者。
+- 临时模式（pg_temp）下不允许创建词典。
+- 创建或修改词典之后，任何对于用户自定义的词典定义文件的修改，将不会影响到数据库中的词典。如果需要在数据库中使用这些修改，需使用ALTER语句更新对应词典的定义文件。
+
+## 语法格式
+
+```ebnf+diagram
+CreateTextSearchDictionary ::= CREATE TEXT SEARCH DICTIONARY name (
+    TEMPLATE = template
+    [, option = value [, ... ]]
+);
+```
+
+## 参数说明
+
+- **name**
+
+  要创建的词典的名称（可指定模式名，否则在当前模式下创建）。
+
+  取值范围: 符合标识符命名规范的字符串，且最大长度不超过63个字符。
+
+- **template**
+
+  模板名。
+
+  取值范围: 系统表**PG_TS_TEMPLATE**中定义的模板：Simple/Synonym/Thesaurus/Ispell/Snowball。
+
+- **option**
+
+    参数名。与template值对应，不同的词典模板具有不同的参数列表，且与指定顺序无关。
+
+  - Simple词典对应的option
+
+    - **STOPWORDS**
+
+        停用词表文件名，默认后缀名为stop。停用词文件格式为一组word列表，每行定义一个停用词。词典处理时，文件中的空行和空格会被忽略，并将stopword词组转换为小写形式。
+
+    - **ACCEPT**
+
+        是否将非停用词设置为已识别。默认值为true。
+
+        当Simple词典设置参数ACCEPT=true时，将不会传递任何token给后继词典，此时建议将其放置在词典列表的最后。反之，当ACCEPT=false时，建议将该Simple词典放置在列表中的至少一个词典之前。
+
+    - **FILEPATH**
+
+        词典文件所在目录。目录可以指定为本地目录和OBS目录（只能在安全模式下指定OBS目录，通过启动时添加securitymode选项进入安全模式）。其中，本地目录格式为”file://absolute_path”，OBS目录格式为”obs://bucket_name/path accesskey=ak secretkey=sk region=rg”。默认值为预定义词典文件所在目录。FILEPATH参数必须和STOPWORDS参数同时指定，不允许单独指定。
+
+  - Synonym词典对应的option
+
+    - **SYNONYM**
+
+        同义词词典的定义文件名，默认后缀名为syn。
+
+        文件格式为一组同义词列表，每行格式为”token synonym”，即token和其对应的synonym，中间以空格相连。
+
+    - **CASESENSITIVE**
+
+        设置是否大小写敏感，默认值为false，此时词典文件中的token和synonym均会转为小写形式处理。如果设置为true，则不会进行小写转换。
+
+    - **FILEPATH**
+
+        同义词词典文件所在目录。目录可以指定为本地目录和OBS目录两种形式（只能在安全模式下指定OBS目录，通过启动时添加securitymode选项进入安全模式）。其中，本地目录格式为”file://absolute_path”，OBS目录格式为”obs://bucket_name/path accesskey=ak secretkey=sk region=rg”。默认值为预定义词典文件所在目录。
+
+  - Thesaurus词典对应的option
+
+    - **DICTFILE**
+
+        词典定义文件名，默认后缀名为ths。
+
+        文件格式为一组同义词列表，每行格式为“sample words : indexed words”，中间冒号（:）作为短语和其替换词间的分隔符。TZ词典处理时，如果有多个匹配的sample words，将选择最长匹配输出。
+
+    - **DICTIONARY**
+
+        用于词规范化的子词典名，必须且仅能定义一个。该词典必须是已经存在的，在检查短语匹配之前使用，用于识别和规范输入文本。
+
+        如果子词典无法识别输入词，将会报错。此时，需要移除该词或者更新子词典使其识别。此外，可在indexed words的开头放上一个星号（*）来跳过在其上应用子词典，但是所有sample words必须可以被子词典识别。
+
+        如果词典文件定义的sample words中，含有子词典中定义的停用词，需要用问号（？）替代停用词。假设a和the是子词典中所定义的停用词，如下：
+
+        ```
+        ? one ? two : swsw
+        ```
+
+        上述同义词组定义会匹配”a one the two”以及”the one a two”，这两个短语均会被swsw替代输出。
+
+    - **FILEPATH**
+
+        词典定义文件所在目录。目录可以指定为本地目录和OBS目录两种形式（只能在安全模式下指定OBS目录，通过启动时添加securitymode选项进入安全模式）。其中，本地目录格式为”file://absolute_path”，OBS目录格式为”obs://bucket_name/path accesskey=ak secretkey=sk region=rg”。默认值为预定义词典文件所在目录。
+
+  - Ispell词典
+
+    - **DICTFILE**
+
+        词典定义文件名，默认后缀名为dict。
+
+    - **AFFFILE**
+
+        词缀文件名，默认后缀名为affix。
+
+    - **STOPWORDS**
+
+        停用词文件名，默认后缀名为stop，文件格式要求与Simple类型词典的停用词文件相同。
+
+    - **FILEPATH**
+
+        词典文件所在目录。可以指定为本地目录和OBS目录两种形式（只能在安全模式下指定OBS目录，通过启动时添加securitymode选项进入安全模式）。其中，本地目录格式为”file://absolute_path”，OBS目录格式为”obs://bucket_name/path accesskey=ak secretkey=sk region=rg”。默认值为预定义词典文件所在目录。
+
+  - Snowball词典
+
+    - **LANGUAGE**
+
+        语言名，标识使用哪种语言的词干分析算法。算法按照对应语言中的拼写规则，缩减输入词的常见变体形式为一个基础词或词干。
+
+    - **STOPWORDS**
+
+        停用词表文件名，默认后缀名为stop，文件格式要求与Simple类型词典的停用词文件相同。
+
+    - **FILEPATH**
+
+        词典定义文件所在目录。可以指定为本地目录或者OBS目录（只能在安全模式下指定OBS目录，通过启动时添加securitymode选项进入安全模式）。其中，本地目录格式为”file://absolute_path”，OBS目录格式为”obs://bucket_name/path accesskey=ak secretkey=sk region=rg”。默认值为预定义词典文件所在目录。FILEPATH参数必须和STOPWORDS参数同时指定，不允许单独指定。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+    > 词典定义文件的文件名仅支持小写字母、数据、下划线混合。
+
+- **value**
+
+  参数值。如果不是简单的标识符或数字，则参数值必须加单引号（标示符和数字同样可以加上单引号）。
+
+## 示例
+
+请参见[配置示例](7-configuration-examples)一节的示例。
+
+## 相关链接
+
+[ALTER TEXT SEARCH DICTIONARY](26-ALTER-TEXT-SEARCH-DICTIONARY)，[CREATE TEXT SEARCH DICTIONARY](65-CREATE-TEXT-SEARCH-DICTIONARY)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/66-CREATE-TRIGGER.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/66-CREATE-TRIGGER.md
new file mode 100644
index 0000000000000000000000000000000000000000..c60fd1d27c546ce7aef34c0fb219a5191c1ea5d8
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/66-CREATE-TRIGGER.md
@@ -0,0 +1,250 @@
+---
+title: CREATE TRIGGER
+summary: CREATE TRIGGER
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE TRIGGER
+
+## 功能描述
+
+创建一个触发器。 触发器将与指定的表或视图关联，并在特定条件下执行指定的函数。
+
+## 注意事项
+
+- 当前仅支持在普通行存表上创建触发器，不支持在列存表、临时表、unlogged表等类型表上创建触发器。
+- 如果为同一事件定义了多个相同类型的触发器，则按触发器的名称字母顺序触发它们。
+- 触发器常用于多表间数据关联同步场景，对SQL执行性能影响较大，不建议在大数据量同步及对性能要求高的场景中使用。
+
+## 语法格式
+
+```ebnf+diagram
+CreateTrigger ::= CREATE [ CONSTRAINT ] TRIGGER trigger_name { BEFORE | AFTER | INSTEAD OF } { event [ OR '...'] }
+    ON table_name
+    [ FROM referenced_table_name ]
+    { NOT DEFERRABLE | [ DEFERRABLE ] { INITIALLY IMMEDIATE | INITIALLY DEFERRED } }
+    [ FOR [ EACH ] { ROW | STATEMENT } ]
+    [ WHEN ( condition ) ]
+    EXECUTE PROCEDURE function_name ( arguments );
+```
+
+其中event包含以下几种：
+
+```ebnf+diagram
+   INSERT
+   UPDATE [ OF column_name [, ... ] ]
+   DELETE
+   TRUNCATE
+```
+
+## 参数说明
+
+- **CONSTRAINT**
+
+  可选项，指定此参数将创建约束触发器，即触发器作为约束来使用。除了可以使用SET CONSTRAINTS调整触发器触发的时间之外，这与常规触发器相同。 约束触发器必须是AFTER ROW触发器。
+
+- **trigger_name**
+
+  触发器名称，该名称不能限定模式，因为触发器自动继承其所在表的模式，且同一个表的触发器不能重名。 对于约束触发器，使用**SET CONSTRAINTS**修改触发器行为时也使用此名称。
+
+  取值范围: 符合标识符命名规范的字符串，且最大长度不超过63个字符。
+
+- **BEFORE**
+
+  触发器函数是在触发事件发生前执行。
+
+- **AFTER**
+
+  触发器函数是在触发事件发生后执行，约束触发器只能指定为AFTER。
+
+- **INSTEAD OF**
+
+  触发器函数直接替代触发事件。
+
+- **event**
+
+  启动触发器的事件，取值范围包括：INSERT、UPDATE、DELETE或TRUNCATE，也可以通过OR同时指定多个触发事件。
+
+  对于UPDATE事件类型，可以使用下面语法指定列：
+
+  ```sql
+  UPDATE OF column_name1 [, column_name2 ... ]
+  ```
+
+  表示当这些列作为UPDATE语句的目标列时，才会启动触发器，但是INSTEAD OF UPDATE类型不支持指定列信息。
+
+- **table_name**
+
+  需要创建触发器的表名称。
+
+  取值范围: 数据库中已经存在的表名称。
+
+- **referenced_table_name**
+
+  约束引用的另一个表的名称。 只能为约束触发器指定，常见于外键约束。
+
+  取值范围: 数据库中已经存在的表名称。
+
+- **DEFERRABLE | NOT DEFERRABLE**
+
+  约束触发器的启动时机，仅作用于约束触发器。这两个关键字设置该约束是否可推迟。
+
+  详细介绍请参见**CREATE TABLE**。
+
+- **INITIALLY IMMEDIATE** **| INITIALLY DEFERRED**
+
+  如果约束是可推迟的，则这个子句声明检查约束的缺省时间，仅作用于约束触发器。
+
+  详细介绍请参见**CREATE TABLE**。
+
+- **FOR EACH ROW | FOR EACH STATEMENT**
+
+    触发器的触发频率。
+
+  - FOR EACH ROW是指该触发器是受触发事件影响的每一行触发一次。
+  - FOR EACH STATEMENT是指该触发器是每个SQL语句只触发一次。
+
+    未指定时默认值为FOR EACH STATEMENT。约束触发器只能指定为FOR EACH ROW。
+
+- **condition**
+
+  决定是否实际执行触发器函数的条件表达式。当指定WHEN时，只有在条件返回true时才会调用该函数。
+
+  在FOR EACH ROW触发器中，WHEN条件可以通过分别写入OLD.column_name或NEW.column_name来引用旧行或新行值的列。 当然，INSERT触发器不能引用OLD和DELETE触发器不能引用NEW。
+
+  INSTEAD OF触发器不支持WHEN条件。
+
+  WHEN表达式不能包含子查询。
+
+  对于约束触发器，WHEN条件的评估不会延迟，而是在执行更新操作后立即发生。 如果条件返回值不为true，则触发器不会排队等待延迟执行。
+
+- **function_name**
+
+  用户定义的函数，必须声明为不带参数并返回类型为触发器，在触发器触发时执行。
+
+- **arguments**
+
+  执行触发器时要提供给函数的可选的以逗号分隔的参数列表。参数是文字字符串常量，简单的名称和数字常量也可以写在这里，但它们都将被转换为字符串。 请检查触发器函数的实现语言的描述，以了解如何在函数内访问这些参数。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  > 关于触发器种类：
+  >
+  > - INSTEAD OF的触发器必须标记为FOR EACH ROW，并且只能在视图上定义。
+  > - BEFORE和AFTER触发器作用在视图上时，只能标记为FOR EACH STATEMENT。
+  > - TRUNCATE类型触发器仅限FOR EACH STATEMENT。
+
+  **表 1** 表和视图上支持的触发器种类：
+
+  | 触发时机   | 触发事件             | 行级   | 语句级   |
+  | :--------- | :------------------- | :----- | :------- |
+  | BEFORE     | INSERT/UPDATE/DELETE | 表     | 表和视图 |
+  | TRUNCATE   | 不支持               | 表     |          |
+  | AFTER      | INSERT/UPDATE/DELETE | 表     | 表和视图 |
+  | TRUNCATE   | 不支持               | 表     |          |
+  | INSTEAD OF | INSERT/UPDATE/DELETE | 视图   | 不支持   |
+  | TRUNCATE   | 不支持               | 不支持 |          |
+
+  **表 2** PLPGSQL类型触发器函数特殊变量：
+
+  | 变量名          | 变量含义                                                |
+  | :-------------- | :------------------------------------------------------ |
+  | NEW             | INSERT及UPDATE操作涉及tuple信息中的新值，对DELETE为空。 |
+  | OLD             | UPDATE及DELETE操作涉及tuple信息中的旧值，对INSERT为空。 |
+  | TG_NAME         | 触发器名称。                                            |
+  | TG_WHEN         | 触发器触发时机（BEFORE/AFTER/INSTEAD OF）。             |
+  | TG_LEVEL        | 触发频率（ROW/STATEMENT）。                             |
+  | TG_OP           | 触发操作（INSERT/UPDATE/DELETE/TRUNCATE）。             |
+  | TG_RELID        | 触发器所在表OID。                                       |
+  | TG_RELNAME      | 触发器所在表名（已废弃，现用TG_TABLE_NAME替代）。       |
+  | TG_TABLE_NAME   | 触发器所在表名。                                        |
+  | TG_TABLE_SCHEMA | 触发器所在表的SCHEMA信息。                              |
+  | TG_NARGS        | 触发器函数参数个数。                                    |
+  | TG_ARGV[]       | 触发器函数参数列表。                                    |
+
+## 示例
+
+```sql
+--创建源表及触发表
+mogdb=# CREATE TABLE test_trigger_src_tbl(id1 INT, id2 INT, id3 INT);
+mogdb=# CREATE TABLE test_trigger_des_tbl(id1 INT, id2 INT, id3 INT);
+
+--创建触发器函数
+mogdb=# CREATE OR REPLACE FUNCTION tri_insert_func() RETURNS TRIGGER AS
+           $$
+           DECLARE
+           BEGIN
+                   INSERT INTO test_trigger_des_tbl VALUES(NEW.id1, NEW.id2, NEW.id3);
+                   RETURN NEW;
+           END
+           $$ LANGUAGE PLPGSQL;
+
+mogdb=# CREATE OR REPLACE FUNCTION tri_update_func() RETURNS TRIGGER AS
+           $$
+           DECLARE
+           BEGIN
+                   UPDATE test_trigger_des_tbl SET id3 = NEW.id3 WHERE id1=OLD.id1;
+                   RETURN OLD;
+           END
+           $$ LANGUAGE PLPGSQL;
+
+mogdb=# CREATE OR REPLACE FUNCTION TRI_DELETE_FUNC() RETURNS TRIGGER AS
+           $$
+           DECLARE
+           BEGIN
+                   DELETE FROM test_trigger_des_tbl WHERE id1=OLD.id1;
+                   RETURN OLD;
+           END
+           $$ LANGUAGE PLPGSQL;
+
+--创建INSERT触发器
+mogdb=# CREATE TRIGGER insert_trigger
+           BEFORE INSERT ON test_trigger_src_tbl
+           FOR EACH ROW
+           EXECUTE PROCEDURE tri_insert_func();
+
+--创建UPDATE触发器
+mogdb=# CREATE TRIGGER update_trigger
+           AFTER UPDATE ON test_trigger_src_tbl
+           FOR EACH ROW
+           EXECUTE PROCEDURE tri_update_func();
+
+--创建DELETE触发器
+mogdb=# CREATE TRIGGER delete_trigger
+           BEFORE DELETE ON test_trigger_src_tbl
+           FOR EACH ROW
+           EXECUTE PROCEDURE tri_delete_func();
+
+--执行INSERT触发事件并检查触发结果
+mogdb=# INSERT INTO test_trigger_src_tbl VALUES(100,200,300);
+mogdb=# SELECT * FROM test_trigger_src_tbl;
+mogdb=# SELECT * FROM test_trigger_des_tbl;  //查看触发操作是否生效。
+
+--执行UPDATE触发事件并检查触发结果
+mogdb=# UPDATE test_trigger_src_tbl SET id3=400 WHERE id1=100;
+mogdb=# SELECT * FROM test_trigger_src_tbl;
+mogdb=# SELECT * FROM test_trigger_des_tbl;  //查看触发操作是否生效
+
+--执行DELETE触发事件并检查触发结果
+mogdb=# DELETE FROM test_trigger_src_tbl WHERE id1=100;
+mogdb=# SELECT * FROM test_trigger_src_tbl;
+mogdb=# SELECT * FROM test_trigger_des_tbl;  //查看触发操作是否生效
+
+--修改触发器
+mogdb=# ALTER TRIGGER delete_trigger ON test_trigger_src_tbl RENAME TO delete_trigger_renamed;
+
+--禁用insert_trigger触发器
+mogdb=# ALTER TABLE test_trigger_src_tbl DISABLE TRIGGER insert_trigger;
+
+--禁用当前表上所有触发器
+mogdb=# ALTER TABLE test_trigger_src_tbl DISABLE TRIGGER ALL;
+
+--删除触发器
+mogdb=# DROP TRIGGER insert_trigger ON test_trigger_src_tbl;
+mogdb=# DROP TRIGGER update_trigger ON test_trigger_src_tbl;
+mogdb=# DROP TRIGGER delete_trigger_renamed ON test_trigger_src_tbl;
+```
+
+## 相关链接
+
+[ALTER TRIGGER](27-ALTER-TRIGGER)，[DROP TRIGGER](99-DROP-TRIGGER)，[ALTER TABLE](22-ALTER-TABLE)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/67-CREATE-TYPE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/67-CREATE-TYPE.md
new file mode 100644
index 0000000000000000000000000000000000000000..2581c37ae6ae3dcc4d927cb384cf858d2a465f5b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/67-CREATE-TYPE.md
@@ -0,0 +1,285 @@
+---
+title: CREATE TYPE
+summary: CREATE TYPE
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE TYPE
+
+## 功能描述
+
+在当前数据库中定义一种新的数据类型。定义数据类型的用户将成为该数据类型的拥有者。类型只适用于行存表
+
+有四种形式的CREATE TYPE，分别为：复合类型、基本类型、shell类型和枚举类型。
+
+- 复合类型
+
+  复合类型由一个属性名和数据类型的列表指定。如果属性的数据类型是可排序的，也可以指定该属性的排序规则。复合类型本质上和表的行类型相同，但是如果只想定义一种类型，使用CREATE TYPE避免了创建一个实际的表。单独的复合类型也是很有用的，例如可以作为函数的参数或者返回类型。
+
+  为了能够创建复合类型，必须拥有在其所有属性类型上的USAGE特权。
+
+- 基本类型
+
+  用户可以自定义一种新的基本类型（标量类型）。通常来说这些函数必须是底层语言所编写。
+
+- shell类型
+
+  shell类型是一种用于后面要定义的类型的占位符，通过发出一个不带除类型名之外其他参数的CREATE TYPE命令可以创建这种类型。在创建基本类型时，需要shell类型作为一种向前引用。
+
+- 枚举类型
+
+  由若干个标签构成的列表，每一个标签值都是一个非空字符串，且字符串长度必须不超过63个字节。
+
+## 注意事项
+
+如果给定一个模式名，那么该类型将被创建在指定的模式中。否则它会被创建在当前模式中。类型名称必须与同一个模式中任何现有的类型或者域相区别（因为表具有相关的数据类型，类型名称也必须与同一个模式中任何现有表的名称不同）。
+
+## 语法格式
+
+```ebnf+diagram
+CreateType ::= CREATE TYPE name AS
+    ( [ attribute_name data_type [ COLLATE collation ] [, ... ] ] )
+```
+
+```ebnf+diagram
+CreateType ::= CREATE TYPE name (
+    INPUT = input_function,
+    OUTPUT = output_function
+    [ , RECEIVE = receive_function ]
+    [ , SEND = send_function ]
+    [ , TYPMOD_IN =
+type_modifier_input_function ]
+    [ , TYPMOD_OUT =
+type_modifier_output_function ]
+    [ , ANALYZE = analyze_function ]
+    [ , INTERNALLENGTH = { internallength |
+VARIABLE } ]
+    [ , PASSEDBYVALUE ]
+    [ , ALIGNMENT = alignment ]
+  [ , STORAGE = storage ]
+    [ , LIKE = like_type ]
+    [ , CATEGORY = category ]
+    [ , PREFERRED = preferred ]
+    [ , DEFAULT = default ]
+    [ , ELEMENT = element ]
+    [ , DELIMITER = delimiter ]
+    [ , COLLATABLE = collatable ]
+)
+```
+
+```ebnf+diagram
+CreateType ::= CREATE TYPE name
+```
+
+```ebnf+diagram
+CreateType ::= CREATE TYPE name AS ENUM
+    ( [ 'label' [, '... '] ] )
+```
+
+## 参数说明
+
+复合类型
+
+- **name**
+
+  要创建的类型的名称（可以被模式限定）。
+
+- **attribute_name**
+
+  复合类型的一个属性（列）的名称。
+
+- **data_type**
+
+  要成为复合类型的一个列的现有数据类型的名称。
+
+- **collation**
+
+  要关联到复合类型的一列的现有排序规则的名称。排序规则可以使用“select \* from pg_collation”命令从pg_collation系统表中查询，默认的排序规则为查询结果中以default开始的行。
+
+基本类型
+
+自定义基本类型时，参数可以以任意顺序出现，input_function和output_function为必选参数，其它为可选参数。
+
+- **input_function**
+
+  将数据从类型的外部文本形式转换为内部形式的函数名。
+
+  输入函数可以被声明为有一个cstring类型的参数，或者有三个类型分别为cstring、 oid、integer的参数。
+
+  - cstring参数是以C字符串存在的输入文本。
+  - oid参数是该类型自身的OID（对于数组类型则是其元素类型的OID）。
+  - integer参数是目标列的typmod（如果知道，不知道则将传递 -1）。
+
+  输入函数必须返回一个该数据类型本身的值。通常，一个输入函数应该被声明为STRICT。 如果不是这样，在读到一个NULL输入值时，调用输入函数时第一个参数会是NULL。在这种情况下，该函数必须仍然返回NULL，除非调用函数发生了错误（这种情况主要是想支持域输入函数，域输入函数可能需要拒绝NULL输入）。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  > 输入和输出函数能被声明为具有新类型的结果或参数是因为：必须在创建新类型之前创建这两个函数。而新类型应该首先被定义为一种shell type，它是一种占位符类型，除了名称和拥有者之外它没有其他属性。这可以通过不带额外参数的命令CREATE TYPE name做到。然后用C写的I/O函数可以被定义为引用这种shell type。最后，用带有完整定义的CREATE TYPE把该shell type替换为一个完全的、合法的类型定义，之后新类型就可以正常使用了。
+
+- **output_function**
+
+  将数据从类型的内部形式转换为外部文本形式的函数名。
+
+  输出函数必须被声明为有一个新数据类型的参数。输出函数必须返回类型cstring。对于NULL值不会调用输出函数。
+
+- **receive_function**
+
+  可选参数。将数据从类型的外部二进制形式转换成内部形式的函数名。
+
+  如果没有该函数，该类型不能参与到二进制输入中。二进制表达转换成内部形式代价更低，然而却更容易移植（例如，标准的整数数据类型使用网络字节序作为外部二进制表达，而内部表达是机器本地的字节序）。receive_function应该执行足够的检查以确保该值是有效的。
+
+  接收函数可以被声明为有一个internal类型的参数，或者有三个类型分别为internal、oid、integer的参数。
+
+  - internal参数是一个指向StringInfo缓冲区的指针，其中保存着接收到的字节串。
+  - oid和integer参数和文本输入函数的相同。
+
+  接收函数必须返回一个该数据类型本身的值。通常，一个接收函数应该被声明为STRICT。如果不是这样，在读到一个NULL输入值时调用接收函数时第一个参数会是NULL。在这种情况下，该函数必须仍然返回NULL，除非接收函数发生了错误（这种情况主要是想支持域接收函数，域接收函数可能需要拒绝NULL输入）。
+
+- **send_function**
+
+  可选参数。将数据从类型的内部形式转换为外部二进制形式的函数名。
+
+  如果没有该函数，该类型将不能参与到二进制输出中。发送函数必须被声明为有一个新数据类型的参数。发送函数必须返回类型bytea。对于NULL值不会调用发送函数。
+
+- **type_modifier_input_function**
+
+  可选参数。将类型的修饰符数组转换为内部形式的函数名。
+
+- **type_modifier_output_function**
+
+  可选参数。将类型的修饰符的内部形式转换为外部文本形式的函数名。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  > 如果该类型支持修饰符（附加在类型声明上的可选约束，例如，char(5)或numeric(30,2)），则需要可选的type_modifier_input_function以及type_modifier_output_function。MogDB允许用户定义的类型有一个或者多个简单常量或者标识符作为修饰符。不过，为了存储在系统目录中，该信息必须能被打包到一个非负整数值中。所声明的修饰符会被以cstring数组的形式传递给type_modifier_input_function。 type_modifier_input_function必须检查该值的合法性（如果值错误就抛出一个错误），如果值正确，要返回一个非负integer值，该值将被存储在“typmod”列中。如果类型没有 type_modifier_input_function则类型修饰符将被拒绝。type_modifier_output_function把内部的整数typmod值转换回正确的形式用于用户显示。type_modifier_output_function必须返回一个cstring值，该值就是追加到类型名称后的字符串。例如，numeric的函数可能会返回(30,2)。如果默认的显示格式就是只把存储的typmod整数值放在圆括号内，则允许省略type_modifier_output_function。
+
+- **analyze_function**
+
+  可选参数。为该数据类型执行统计分析的函数名的可选参数。
+
+  默认情况下，如果该类型有一个默认的B-tree操作符类，ANALYZE将尝试用类型的“equals”和“less-than”操作符来收集统计信息。这种行为对于非标量类型并不合适，因此可以通过指定一个自定义分析函数来覆盖这种行为。分析函数必须被声明为有一个类型为internal的参数，并且返回一个boolean结果。
+
+- **internallength**
+
+  可选参数。一个数字常量，用于指定新类型的内部表达的字节长度。默认为变长。
+
+  虽然只有I/O函数和其他为该类型创建的函数才知道新类型的内部表达的细节， 但是内部表达的一些属性必须被向MogDB声明。其中最重要的是internallength。基本数据类型可以是定长的（这种情况下internallength是一个正整数）或者是变长的（把internallength设置为VARIABLE，在内部通过把typlen设置为-1表示）。所有变长类型的内部表达都必须以一个4字节整数开始，internallength定义了总长度。
+
+- **PASSEDBYVALUE**
+
+  可选参数。表示这种数据类型的值需要被传值而不是传引用。传值的类型必须是定长的，并且它们的内部表达不能超过Datum类型（某些机器上是4字节，其他机器上是8字节）的尺寸。
+
+- **alignment**
+
+  可选参数。该参数指定数据类型的存储对齐需求。如果被指定，必须是char、int2、int4或者double。默认是int4。
+
+  允许的值等同于以1、2、4或8字节边界对齐。要注意变长类型的alignment参数必须至少为4，因为它们需要包含一个int4作为它们的第一个组成部分。
+
+- **storage**
+
+    可选参数。该数据类型的存储策略。
+
+    如果被指定，必须是plain、external、extended或者main。 默认是plain。
+
+  - plain指定该类型的数据将总是被存储在线内并且不会被压缩。（对定长类型只允许plain）
+
+  - extended 指定系统将首先尝试压缩一个长的数据值，并且将在数据仍然太长的情况下把值移出主表行。
+
+    external允许值被移出主表， 但是系统将不会尝试对它进行压缩。
+
+  - main允许压缩，但是不鼓励把值移出主表（如果没有其他办法让行的大小变得合适，具有这种存储策略的数据项仍将被移出主表，但比起extended以及external项来，这种存储策略的数据项会被优先考虑保留在主表中）。
+
+    除plain之外所有的storage值都暗示该数据类型的函数能处理被TOAST过的值。指定的值仅仅是决定一种可TOAST数据类型的列的默认TOAST存储策略，用户可以使用ALTER TABLE SET STORAGE为列选取其他策略。
+
+- **like_type**
+
+  可选参数。与新类型具有相同表达的现有数据类型的名称。会从这个类型中复制internallength、 passedbyvalue、 alignment以及storage的值（ 除非在这个CREATE TYPE命令的其他地方用显式说明覆盖）。
+
+  当新类型的低层实现是以一种现有的类型为参考时，用这种方式指定表达特别有用。
+
+- **category**
+
+  可选参数。这种类型的分类码（一个ASCII 字符）。 默认是“用户定义类型”的'U'。为了创建自定义分类， 也可以选择其他 ASCII字符。
+
+- **preferred**
+
+  可选参数。如果这种类型是其类型分类中的优先类型则为TRUE，否则为FALSE。默认为假。在一个现有类型分类中创建一种新的优先类型要非常谨慎， 因为这可能会导致很大的改变。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  > category和preferred参数可以被用来帮助控制在混淆的情况下应用哪一种隐式造型。每一种数据类型都属于一个用单个ASCII 字符命名的分类，并且每一种类型可以是其所属分类中的“首选”。当有助于解决重载函数或操作符时，解析器将优先造型到首选类型（但是只能从同类的其他类型造型）。对于没有隐式转换到或来自任意其他类型的类型，让这些设置保持默认即可。不过，对于有隐式转换的相关类型的组，把它们都标记为属于同一个类别并且选择一种或两种“最常用”的类型作为该类别的首选通常是很有用的。在把一种用户定义的类型增加到一个现有的内建类别（例如，数字或者字符串类型）中时，category参数特别有用。不过，也可以创建新的全部是用户定义类型的类别。对这样的类别，可选择除大写字母之外的任何ASCII 字符。
+
+- **default**
+
+  可选参数。数据类型的默认值。如果被省略，默认值是空。
+
+  如果用户希望该数据类型的列被默认为某种非空值，可以指定一个默认值。默认值可以用DEFAULT关键词指定（这样一个默认值可以被附加到一个特定列的显式DEFAULT子句覆盖）。
+
+- **element**
+
+  可选参数。被创建的类型是一个数组，element指定了数组元素的类型。例如，要定义一个4字节整数的数组（int4）， 应指定ELEMENT = int4。
+
+- **delimiter**
+
+  可选参数。指定这种类型组成的数组中分隔值的定界符。
+
+  可以把delimiter设置为一个特定字符，默认的定界符是逗号（,）。注意定界符是与数组元素类型相关的，而不是数组类型本身相关。
+
+- **collatable**
+
+  可选参数。如果这个类型的操作可以使用排序规则信息，则为TRUE。默认为FALSE。
+
+  如果collatable为TRUE，这种类型的列定义和表达式可能通过使用COLLATE子句携带有排序规则信息。在该类型上操作的函数的实现负责真正利用这些信息，仅把类型标记为可排序的并不会让它们自动地去使用这类信息。
+
+- **lable**
+
+  可选参数。与枚举类型的一个值相关的文本标签，其值为长度不超过63个字符的非空字符串。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+> 在创建用户定义类型的时候， MogDB会自动创建一个与之关联的数组类型，其名称由该元素类型的名称前缀一个下划线组成。
+
+## 示例
+
+```sql
+--创建一种复合类型，建表并插入数据以及查询。
+mogdb=# CREATE TYPE compfoo AS (f1 int, f2 text);
+mogdb=# CREATE TABLE t1_compfoo(a int, b compfoo);
+mogdb=# CREATE TABLE t2_compfoo(a int, b compfoo);
+mogdb=# INSERT INTO t1_compfoo values(1,(1,'demo'));
+mogdb=# INSERT INTO t2_compfoo select * from t1_compfoo;
+mogdb=# SELECT (b).f1 FROM t1_compfoo;
+mogdb=# SELECT * FROM t1_compfoo t1 join t2_compfoo t2 on (t1.b).f1=(t1.b).f1;
+
+--重命名数据类型。
+mogdb=# ALTER TYPE compfoo RENAME TO compfoo1;
+
+--要改变一个用户定义类型compfoo1的所有者为usr1。
+mogdb=# CREATE USER usr1 PASSWORD 'xxxxxxxxx';
+mogdb=# ALTER TYPE compfoo1 OWNER TO usr1;
+
+--把用户定义类型compfoo1的模式改变为usr1。
+mogdb=# ALTER TYPE compfoo1 SET SCHEMA usr1;
+
+--给一个数据类型增加一个新的属性。
+mogdb=# ALTER TYPE usr1.compfoo1 ADD ATTRIBUTE f3 int;
+
+--删除compfoo1类型。
+mogdb=# DROP TYPE usr1.compfoo1 cascade;
+
+--删除相关表和用户。
+mogdb=# DROP TABLE t1_compfoo;
+mogdb=# DROP TABLE t2_compfoo;
+mogdb=# DROP SCHEMA usr1;
+mogdb=# DROP USER usr1;
+
+--创建一个枚举类型。
+mogdb=# CREATE TYPE bugstatus AS ENUM ('create', 'modify', 'closed');
+
+--添加一个标签值。
+mogdb=# ALTER TYPE bugstatus ADD VALUE IF NOT EXISTS 'regress' BEFORE 'closed';
+
+--重命名一个标签值。
+mogdb=# ALTER TYPE bugstatus RENAME VALUE 'create' TO 'new';
+```
+
+## 相关链接
+
+[ALTER TYPE](28-ALTER-TYPE)，[DROP TYPE](100-DROP-TYPE)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/68-CREATE-USER.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/68-CREATE-USER.md
new file mode 100644
index 0000000000000000000000000000000000000000..bda1a5b1d06a0c109270900c1617876ce1c7dc0c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/68-CREATE-USER.md
@@ -0,0 +1,121 @@
+---
+title: CREATE USER
+summary: CREATE USER
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE USER
+
+## 功能描述
+
+创建一个用户。
+
+## 注意事项
+
+- 通过CREATE USER创建的用户，默认具有LOGIN权限。
+- 通过CREATE USER创建用户的同时，系统会在执行该命令的数据库中，为该用户创建一个同名的SCHEMA。
+- 系统管理员在普通用户同名schema下创建的对象，所有者为schema的同名用户（非系统管理员）。
+
+## 语法格式
+
+```ebnf+diagram
+CreateUser ::= CREATE USER user_name [ [ WITH ] option [ ... ] ] [ ENCRYPTED | UNENCRYPTED ] { PASSWORD | IDENTIFIED BY } { 'password' [EXPIRED] | DISABLE };
+```
+
+其中option子句用于设置权限及属性等信息。
+
+```ebnf+diagram
+option ::= {SYSADMIN | NOSYSADMIN}
+    | {MONADMIN | NOMONADMIN}
+    | {OPRADMIN | NOPRADMIN}
+    | {POLADMIN | NOPOLADMIN}
+    | {AUDITADMIN | NOAUDITADMIN}
+    | {CREATEDB | NOCREATEDB}
+    | {USEFT | NOUSEFT}
+    | {CREATEROLE | NOCREATEROLE}
+    | {INHERIT | NOINHERIT}
+    | {LOGIN | NOLOGIN}
+    | {REPLICATION | NOREPLICATION}
+    | {INDEPENDENT | NOINDEPENDENT}
+    | {VCADMIN | NOVCADMIN}
+    | CONNECTION LIMIT connlimit
+    | VALID BEGIN 'timestamp'
+    | VALID UNTIL 'timestamp'
+    | RESOURCE POOL 'respool'
+    | PERM SPACE 'spacelimit'
+    | TEMP SPACE 'tmpspacelimit'
+    | SPILL SPACE 'spillspacelimit'
+    | IN ROLE role_name [, ...]
+    | IN GROUP role_name [, ...]
+    | ROLE role_name [, ...]
+    | ADMIN role_name [, ...]
+    | USER role_name [, ...]
+    | SYSID uid
+    | DEFAULT TABLESPACE tablespace_name
+    | PROFILE DEFAULT
+    | PROFILE profile_name
+    | PGUSER
+```
+
+## 参数说明
+
+- **user_name**
+
+  用户名称。
+
+  取值范围: 字符串，要符合标识符的命名规范。且最大长度不超过63个字符。
+
+- **password**
+
+    登录密码。
+
+    密码规则如下：
+
+  - 密码默认不少于8个字符。
+  - 不能与用户名及用户名倒序相同。
+  - 至少包含大写字母（A-Z），小写字母（a-z），数字（0-9），非字母数字字符（限定为~!@#$%^&*()-_=+\|[{}];:,&lt;.&gt;/?）四类字符中的三类字符。
+  - 密码也可以是符合格式要求的密文字符串，这种情况主要用于用户数据导入场景，不推荐用户直接使用。如果直接使用密文密码，用户需要知道密文密码对应的明文，并且保证明文密码复杂度，数据库不会校验密文密码复杂度，直接使用密文密码的安全性由用户保证。
+
+- 创建用户时，应当使用双引号或单引号将用户密码括起来。
+
+  取值范围: 字符串。
+
+CREATE USER的其他参数值请参考[CREATE ROLE](54-CREATE-ROLE#参数说明)。
+
+## 示例
+
+```sql
+--创建用户jim，登录密码为xxxxxxxxx。
+mogdb=# CREATE USER jim PASSWORD 'xxxxxxxxx';
+
+--下面语句与上面的等价。
+mogdb=# CREATE USER kim IDENTIFIED BY 'xxxxxxxxx';
+
+--如果创建有“创建数据库”权限的用户，则需要加CREATEDB关键字。
+mogdb=# CREATE USER dim CREATEDB PASSWORD 'xxxxxxxxx';
+
+--将用户jim的登录密码由xxxxxxxx修改为Abcd@123。
+mogdb=# ALTER USER jim IDENTIFIED BY 'Abcd@123' REPLACE 'xxxxxxxxx';
+
+--为用户jim追加CREATEROLE权限。
+mogdb=# ALTER USER jim CREATEROLE;
+
+--将enable_seqscan的值设置为on， 设置成功后，在下一会话中生效。
+mogdb=# ALTER USER jim SET enable_seqscan TO on;
+
+--重置jim的enable_seqscan参数。
+mogdb=# ALTER USER jim RESET enable_seqscan;
+
+--锁定jim帐户。
+mogdb=# ALTER USER jim ACCOUNT LOCK;
+
+--删除用户。
+mogdb=# DROP USER kim CASCADE;
+mogdb=# DROP USER jim CASCADE;
+mogdb=# DROP USER dim CASCADE;
+```
+
+## 相关链接
+
+[ALTER USER](68-CREATE-USER)，[CREATE ROLE](54-CREATE-ROLE)，[DROP USER](101-DROP-USER)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/69-CREATE-USER-MAPPING.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/69-CREATE-USER-MAPPING.md
new file mode 100644
index 0000000000000000000000000000000000000000..431654fd40e32364ccdd0bf36e52d654705948e5
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/69-CREATE-USER-MAPPING.md
@@ -0,0 +1,85 @@
+---
+title: CREATE USER MAPPING
+summary: CREATE USER MAPPING
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE USER MAPPING
+
+## 功能描述
+
+定义一个用户到一个外部服务器的新映射。
+
+## 注意事项
+
+当在OPTIONS中出现password选项时，需要保证MogDB每个节点的`$GAUSSHOME/bin`目录下存在usermapping.key.cipher和usermapping.key.rand文件，如果不存在这两个文件，请使用`gs_guc`工具生成并使用`gs_ssh`工具发布到MogDB每个节点的`$GAUSSHOME/bin`目录下。
+
+## 语法格式
+
+```ebnf+diagram
+CreateUserMapping ::= CREATE USER MAPPING FOR { user_name | USER | CURRENT_USER | PUBLIC }
+    SERVER server_name
+    [ OPTIONS ( option 'value' [ ,' ... '] ) ];
+```
+
+## 参数说明
+
+- **user_name**
+
+  要映射到外部服务器的一个现有用户的名称。 `CURRENT_USER`和`USER`匹配当前用户的名称。 当PUBLIC被指定时，一个公共映射会被创建，当没有特定用户的映射可用时将会使用它。
+
+- **server_name**
+
+  将为其创建用户映射的现有服务器的名称。
+
+- **OPTIONS ( { option_name ' value ' } [, …] )**
+
+  这个子句指定用户映射的选项。这些选项通常定义该映射实际的用户名和口令。选项名必须唯一。允许的选项名和值与该服务器的外部数据包装器有关。
+
+  >**说明：**
+  >
+  >- 用户的口令会加密后保存到系统表[PG_USER_MAPPING](PG_USER_MAPPING)中，加密时需要使用usermapping.key.cipher和usermapping.key.rand作为加密密码文件和加密因子。首次使用前需要通过如下命令创建这两个文件，并将这两个文件放入各节点目录$GAUSSHOME/bin，且确保具有读权限。gs_ssh工具可以协助您快速将文件放入各节点对应目录下。
+  >
+  >    ```bash
+  >    gs_ssh -c "gs_guc generate -o usermapping -S default -D $GAUSSHOME/bin"
+  >    ```
+  >
+  >- 其中-S参数指定default时会随机生成密码，用户也可为-S参数指定密码，此密码用于保证生成密码文件的安全性和唯一性，用户无需保存或记忆。其他参数详见工具参考中gs_guc工具说明。
+
+  oracle_fdw支持的options包括：
+
+  - **user**
+
+    oracle server的用户名。
+
+  - **password**
+
+    oracle用户对应的密码。
+
+  mysql_fdw支持的options包括：
+
+  - **username**
+
+    MySQL Server/MariaDB的用户名。
+
+  - **password**
+
+    MySQL Server/MariaDB用户对应的密码。
+
+  postgres_fdw支持的options包括：
+
+  - **user**
+
+    远端MogDB的用户名。
+
+  - **password**
+
+    远端MogDB用户对应的密码。
+
+    > **说明：**
+    > MogDB在后台会对用户输入的password加密以保证安全性。该加密所需密钥文件需要使用gs_guc工具生成并使用gs_ssh工具发布到MogDB每个节点的`$GAUSSHOME/bin`目录下。password不应当包含'encryptOpt'前缀，否则会被认为是加密后的密文。
+
+## 相关链接
+
+[ALTER USER MAPPING](30-ALTER-USER-MAPPING)，[DROP USER MAPPING](102-DROP-USER-MAPPING)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/7-ALTER-FUNCTION.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/7-ALTER-FUNCTION.md
new file mode 100644
index 0000000000000000000000000000000000000000..bb01121cfea54365096b7427709d8100e85e7ba2
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/7-ALTER-FUNCTION.md
@@ -0,0 +1,197 @@
+---
+title: ALTER FUNCTION
+summary: ALTER FUNCTION
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER FUNCTION
+
+## 功能描述
+
+修改自定义函数的属性。
+
+## 注意事项
+
+只有函数的所有者或者被授予了函数ALTER权限的用户才能执行ALTER FUNCTION命令，系统管理员默认拥有该权限。针对所要修改属性的不同，还有以下权限约束：
+
+- 如果函数中涉及对临时表相关的操作，则无法使用ALTER FUNCTION。
+- 修改函数的所有者或修改函数的模式，当前用户必须是该函数的所有者或者系统管理员，且该用户是新所有者角色的成员。
+
+- 只有系统管理员和初始化用户可以将function的schema修改成public。
+
+## 语法格式
+
+- 修改自定义函数的附加参数。
+
+  ```ebnf+diagram
+  AlterFunction ::= ALTER FUNCTION function_name ( [ { [ argmode ] [ argname ] argtype} [, ...] ] )
+      action [ ... ] [ RESTRICT ];
+  ```
+
+  其中附加参数action子句语法为：
+
+  ```ebnf+diagram
+  action ::= {CALLED ON NULL INPUT | RETURNS NULL ON NULL INPUT | STRICT}
+   | {IMMUTABLE | STABLE | VOLATILE}
+   | {SHIPPABLE | NOT SHIPPABLE}
+   | {NOT FENCED | FENCED}
+   | [ NOT ] LEAKPROOF
+   | { [ EXTERNAL ] SECURITY INVOKER | [ EXTERNAL ] SECURITY DEFINER }
+   | AUTHID { DEFINER | CURRENT_USER }
+   | COST execution_cost
+   | ROWS result_rows
+   | SET configuration_parameter { { TO | = } { value | DEFAULT }| FROM CURRENT}
+   | RESET {configuration_parameter | ALL}
+  ```
+
+- 修改自定义函数的名称。
+
+  ```ebnf+diagram
+  AlterFunction ::= ALTER FUNCTION funname ( [ { [ argmode ] [ argname ] argtype} [, ...] ] )
+      RENAME TO new_name;
+  ```
+
+- 修改自定义函数的所属者。
+
+  ```ebnf+diagram
+  AlterFunction ::= ALTER FUNCTION funname ( [ { [ argmode ] [ argname ] argtype} [, ...] ] )
+      OWNER TO new_owner;
+  ```
+
+- 修改自定义函数的模式。
+
+  ```ebnf+diagram
+  AlterFunction ::= ALTER FUNCTION funname ( [ { [ argmode ] [ argname ] argtype} [, ...] ] )
+      SET SCHEMA new_schema;
+  ```
+
+## 参数说明
+
+- **function_name**
+
+  要修改的函数名称。
+
+  取值范围: 已存在的函数名。
+
+- **argmode**
+
+  标识该参数是输入、输出参数。
+
+  取值范围: IN/OUT/INOUT/VARIADIC
+
+- **argname**
+
+  参数名称。
+
+  取值范围: 字符串，符合标识符命名规范。
+
+- **argtype**
+
+  函数参数的类型。
+
+- **CALLED ON NULL INPUT**
+
+  表明该函数的某些参数是NULL的时候可以按照正常的方式调用。缺省时与指定此参数的作用相同。
+
+- **RETURNS NULL ON NULL INPUT**
+
+  **STRICT**
+
+  STRICT用于指定如果函数的某个参数是NULL，此函数总是返回NULL。如果声明了这个参数，则如果存在NULL参数时不会执行该函数；而只是自动假设一个NULL结果。
+
+  RETURNS NULL ON NULL INPUT和STRICT的功能相同。
+
+- **IMMUTABLE**
+
+  表示该函数在给出同样的参数值时总是返回同样的结果。
+
+- **STABLE**
+
+  表示该函数不能修改数据库，对相同参数值，在同一次表扫描里，该函数的返回值不变，但是返回值可能在不同SQL语句之间变化。
+
+- **VOLATILE**
+
+  表示该函数值可以在一次表扫描内改变，不会做任何优化。
+
+- **LEAKPROOF**
+
+  表示该函数没有副作用，指出参数只包括返回值。LEAKPROOF只能由系统管理员设置。
+
+- **EXTERNAL**
+
+  （可选）目的是和SQL兼容，这个特性适合于所有函数，而不仅是外部函数。
+
+- **SECURITY INVOKER**
+
+  **AUTHID CURRENT_USER**
+
+  表明该函数将以调用它的用户的权限执行。缺省时与指定此参数的作用相同。
+
+  SECURITY INVOKER和AUTHID CURRENT_USER的功能相同。
+
+- **SECURITY DEFINER**
+
+  **AUTHID DEFINER**
+
+  声明该函数将以创建它的用户的权限执行。
+
+  AUTHID DEFINER和SECURITY DEFINER的功能相同。
+
+- **COST execution_cost**
+
+  用来估计函数的执行成本。
+
+  execution_cost以cpu_operator_cost为单位。
+
+  取值范围: 正数
+
+- **ROWS result_rows**
+
+  估计函数返回的行数。用于函数返回的是一个集合。
+
+  取值范围: 正数，默认值是1000行。
+
+- **configuration_parameter**
+
+  - **value**
+
+    把指定的数据库会话参数值设置为给定的值。如果value是DEFAULT或者RESET，则在新的会话中使用系统的缺省设置。OFF关闭设置。
+
+    取值范围: 字符串
+
+    - DEFAULT
+    - OFF
+    - RESET
+
+    指定默认值。
+
+  - **from current**
+
+    取当前会话中的值设置为configuration_parameter的值。
+
+- **new_name**
+
+  函数的新名称。要修改函数的所属模式，必须拥有新模式的CREATE权限。
+
+  取值范围: 字符串，符合标识符命名规范。
+
+- **new_owner**
+
+  函数的新所有者。要修改函数的所有者，新所有者必须拥有该函数所属模式的CREATE权限。
+
+  取值范围: 已存在的用户角色。
+
+- **new_schema**
+
+  函数的新模式。
+
+  取值范围: 已存在的模式。
+
+## 示例
+
+请参见[CREATE FUNCTION](48-CREATE-FUNCTION)的示例。
+
+## 相关链接
+
+[CREATE FUNCTION](48-CREATE-FUNCTION)，[DROP FUNCTION](82-DROP-FUNCTION)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/70-CREATE-VIEW.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/70-CREATE-VIEW.md
new file mode 100644
index 0000000000000000000000000000000000000000..b282c8eaa6ea5eb89f1ca4e2b03e50d305c8e772
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/70-CREATE-VIEW.md
@@ -0,0 +1,81 @@
+---
+title: CREATE VIEW
+summary: CREATE VIEW
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CREATE VIEW
+
+## 功能描述
+
+创建一个视图。视图与基本表不同，是一个虚拟的表。数据库中仅存放视图的定义，而不存放视图对应的数据，这些数据仍存放在原来的基本表中。若基本表中的数据发生变化，从视图中查询出的数据也随之改变。从这个意义上讲，视图就像一个窗口，透过它可以看到数据库中用户感兴趣的数据及变化。
+
+## 注意事项
+
+无。
+
+## 语法格式
+
+```ebnf+diagram
+CreateView ::= CREATE [ OR REPLACE ] [ TEMP | TEMPORARY ] VIEW view_name [ ( column_name [, ...] ) ]
+    [ WITH ( {view_option_name [= view_option_value]} [, ... ] ) ]
+    AS query;
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 创建视图时使用WITH(security_barriers)可以创建一个相对安全的视图，避免攻击者利用低成本函数的RAISE语句打印出隐藏的基表数据。
+> - 旧版MogDB在create or replace创建视图的时候，如果存在同名视图，则replace时不可以更改列信息或者删除列，只能追加列。2.1版之后的MogDB支持REPLACE VIEW语法更新或者删除列信息。
+
+## 参数说明
+
+- **OR REPLACE** <a id = 'replace'> </a>
+
+  如果视图已存在，则重新定义。支持减少列、更改列名操作，仅对非物化视图有效。
+
+- **TEMP | TEMPORARY**
+
+  创建临时视图。
+
+- **view_name**
+
+  要创建的视图名称。可以用模式修饰。
+
+  取值范围: 字符串，符合标识符命名规范。
+
+- **column_name**
+
+  可选的名称列表，用作视图的字段名。如果没有给出，字段名取自查询中的字段名。
+
+  取值范围: 字符串，符合标识符命名规范。
+
+- **view_option_name [= view_option_value]**
+
+  该子句为视图指定一个可选的参数。
+
+  目前view_option_name支持的参数仅有security_barrier，当VIEW试图提供行级安全时，应使用该参数。
+
+  取值范围: Boolean类型，TRUE、FALSE
+
+- **query**
+
+  为视图提供行和列的SELECT或VALUES语句。
+
+## 示例
+
+```sql
+--创建字段spcname为pg_default组成的视图。
+mogdb=# CREATE VIEW myView AS
+    SELECT * FROM pg_tablespace WHERE spcname = 'pg_default';
+
+--查看视图。
+mogdb=# SELECT * FROM myView ;
+
+--删除视图myView。
+mogdb=# DROP VIEW myView;
+```
+
+## 相关链接
+
+[ALTER VIEW](31-ALTER-VIEW)，[DROP VIEW](103-DROP-VIEW)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/70.1-CREATE-WEAK-PASSWORD-DICTIONARY.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/70.1-CREATE-WEAK-PASSWORD-DICTIONARY.md
new file mode 100644
index 0000000000000000000000000000000000000000..1efecd7dce5b148c9c3ab45927462ef078b59b7a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/70.1-CREATE-WEAK-PASSWORD-DICTIONARY.md
@@ -0,0 +1,54 @@
+---
+title: CREATE WEAK PASSWORD DICTIONARY
+summary: CREATE WEAK PASSWORD DICTIONARY
+author: Zhang Cuiping
+date: 2021-11-01
+---
+
+# CREATE WEAK PASSWORD DICTIONARY
+
+## 功能描述
+
+向gs_global_config表中插入一个或者多个弱口令。
+
+## 注意事项
+
+- 只有初始用户、系统管理员和安全管理员拥有权限执行本语法。
+- 弱口令字典中的口令存放在gs_global_config系统表中。
+- 弱口令字典默认为空，用户通过本语法可以新增一条或多条弱口令。
+- 当用户尝试通过本语法插入gs_global_config表中已存在的弱口令时，会只在表中保留一条该弱口令。
+
+## 语法格式
+
+```ebnf+diagram
+CreateWeakPasswordDictionary ::= CREATE WEAK PASSWORD DICTIONARY
+       [WITH VALUES] ( {'weak_password'} [, ...] );
+```
+
+## 参数说明
+
+weak_password
+
+弱口令。
+
+范围：字符串。
+
+## 示例
+
+```sql
+--向gs_global_config系统表中插入单个弱口令。
+mogdb=# CREATE WEAK PASSWORD DICTIONARY WITH VALUES ('password1');
+
+--向gs_global_config系统表中插入多个弱口令。
+mogdb=# CREATE WEAK PASSWORD DICTIONARY WITH VALUES ('password2'),('password3');
+
+--清空gs_global_config系统表中所有弱口令。
+mogdb=# DROP WEAK PASSWORD DICTIONARY;
+
+--查看现有弱口令。
+mogdb=# SELECT * FROM gs_global_config WHERE NAME LIKE 'weak_password';
+```
+
+## 相关链接
+
+[DROP WEAK PASSWORD DICTIONARY](103.1-DROP-WEAK-PASSWORD-DICTIONARY)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/71-CURSOR.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/71-CURSOR.md
new file mode 100644
index 0000000000000000000000000000000000000000..a94ae108c1a2c12ba8c60fb0c9c6bfa556eaffc8
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/71-CURSOR.md
@@ -0,0 +1,70 @@
+---
+title: CURSOR
+summary: CURSOR
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# CURSOR
+
+## 功能描述
+
+CURSOR命令定义一个游标，用于在一个大的查询里面检索少数几行数据。
+
+为了处理SQL语句，存储过程进程分配一段内存区域来保存上下文联系。游标是指向上下文区域的句柄或指针。借助游标，存储过程可以控制上下文区域的变化。
+
+## 注意事项
+
+- 游标命令只能在事务块里使用。
+- 通常游标和SELECT一样返回文本格式。因为数据在系统内部是用二进制格式存储的，系统必须对数据做一定转换以生成文本格式。一旦数据是以文本形式返回，客户端应用需要把它们转换成二进制进行操作。使用FETCH语句，游标可以返回文本或二进制格式。
+- 应该小心使用二进制游标。文本格式一般都比对应的二进制格式占用的存储空间大。二进制游标返回内部二进制形态的数据，可能更易于操作。如果想以文本方式显示数据，则以文本方式检索会为用户节约很多客户端的工作。比如，如果查询从某个整数列返回1，在缺省的游标里将获得一个字符串1，但在二进制游标里将得到一个4字节的包含该数值内部形式的数值（大端顺序）。
+
+## 语法格式
+
+```ebnf+diagram
+Cursor ::= CURSOR cursor_name
+    [ BINARY ]  [ NO SCROLL ]  [ { WITH | WITHOUT } HOLD ]
+    FOR query ;
+```
+
+## 参数说明
+
+- **cursor_name**
+
+  将要创建的游标名。
+
+  取值范围: 遵循数据库对象命名规范。
+
+- **BINARY**
+
+  指明游标以二进制而不是文本格式返回数据。
+
+- **NO SCROLL**
+
+  声明游标检索数据行的方式。
+
+  - NO SCROLL：声明该游标不能用于以倒序的方式检索数据行。
+  - 未声明：根据执行计划的不同，自动判断该游标是否可以用于以倒序的方式检索数据行。
+
+- **WITH HOLD | WITHOUT HOLD**
+
+  声明当创建游标的事务结束后，游标是否能继续使用。
+
+  - WITH HOLD：声明该游标在创建它的事务结束后仍可继续使用。
+  - WITHOUT HOLD：声明该游标在创建它的事务之外不能再继续使用，此游标将在事务结束时被自动关闭。
+  - 如果不指定WITH HOLD或WITHOUT HOLD，默认行为是WITHOUT HOLD。
+  - 跨节点事务不支持WITH HOLD（例如在多DBnode部署openGauss中所创建的含有DDL的事务属于跨节点事务）。
+
+- **query**
+
+  使用SELECT或VALUES子句指定游标返回的行。
+
+  取值范围: SELECT或VALUES子句。
+
+## 示例
+
+请参考FETCH的示例。
+
+## 相关链接
+
+[FETCH](107-FETCH)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/72-DEALLOCATE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/72-DEALLOCATE.md
new file mode 100644
index 0000000000000000000000000000000000000000..7be53c575cab88276d99c4be0e71bb981e202791
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/72-DEALLOCATE.md
@@ -0,0 +1,38 @@
+---
+title: DEALLOCATE
+summary: DEALLOCATE
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# DEALLOCATE
+
+## 功能描述
+
+DEALLOCATE用于删除前面编写的预备语句。如果用户没有明确删除一个预备语句，那么它将在会话结束的时候被删除。
+
+PREPARE关键字总被忽略。
+
+## 注意事项
+
+无。
+
+## 语法格式
+
+```ebnf+diagram
+Deallocate ::= DEALLOCATE [ PREPARE ] { name | ALL };
+```
+
+## 参数说明
+
+- **name**
+
+  将要删除的预备语句。
+
+- **ALL**
+
+  删除所有预备语句。
+
+## 示例
+
+无。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/73-DECLARE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/73-DECLARE.md
new file mode 100644
index 0000000000000000000000000000000000000000..e5cb3685a848fb1aa2a3c721acfe458dde6b5a60
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/73-DECLARE.md
@@ -0,0 +1,94 @@
+---
+title: DECLARE
+summary: DECLARE
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# DECLARE
+
+## 功能描述
+
+DECLARE命令既可以定义一个游标，用于在一个大的查询里面检索少数几行数据，也可以作为一个匿名块的开始。
+
+本节主要描述定义为游标的用法，开启匿名块的用法见**BEGIN**。
+
+为了处理SQL语句，存储过程进程分配一段内存区域来保存上下文联系。游标是指向上下文区域的句柄或指针。借助游标，存储过程可以控制上下文区域的变化。
+
+通常游标和SELECT一样返回文本格式。因为数据在系统内部是用二进制格式存储的，系统必须对数据做一定转换以生成文本格式。一旦数据是以文本形式返回，客户端应用需要把它们转换成二进制进行操作。使用FETCH语句，游标可以返回文本或二进制格式。
+
+## 注意事项
+
+- 游标命令只能在事务块里使用。
+- 应该小心使用二进制游标。文本格式一般都比对应的二进制格式占用的存储空间大。二进制游标返回内部二进制形态的数据，可能更易于操作。如果想以文本方式显示数据，则以文本方式检索会为用户节约很多客户端的工作。比如，如果查询从某个整数列返回1，在缺省的游标里将获得一个字符串1，但在二进制游标里将得到一个4字节的包含该数值内部形式的数值（大端顺序）。
+
+## 语法格式
+
+- 定义游标
+
+  ```ebnf+diagram
+  Declare ::= DECLARE cursor_name [ BINARY ] [ NO SCROLL ]
+      CURSOR [ { WITH | WITHOUT } HOLD ] FOR query ;
+  ```
+
+- 开启匿名块
+
+  ```ebnf+diagram
+  Declare ::= [DECLARE [declare_statements]]
+  BEGIN
+  execution_statements
+  END;
+  ```
+
+## 参数说明
+
+- **cursor_name**
+
+  将要创建的游标名。
+
+  取值范围: 遵循数据库对象命名规范。
+
+- **BINARY**
+
+  指明游标以二进制而不是文本格式返回数据。
+
+- **NO SCROLL**
+
+  声明游标检索数据行的方式。
+
+  - NO SCROLL：声明该游标不能用于以倒序的方式检索数据行。
+  - 未声明：根据执行计划的不同，自动判断该游标是否可以用于以倒序的方式检索数据行。
+
+- **WITH HOLD**
+
+  **WITHOUT HOLD**
+
+  声明当创建游标的事务结束后，游标是否能继续使用。
+
+  - WITH HOLD：声明该游标在创建它的事务结束后仍可继续使用。
+  - WITHOUT HOLD：声明该游标在创建它的事务之外不能再继续使用，此游标将在事务结束时被自动关闭。
+  - 如果不指定WITH HOLD或WITHOUT HOLD，默认行为是WITHOUT HOLD。
+
+- **query**
+
+  使用SELECT或VALUES子句指定游标返回的行。
+
+  取值范围: SELECT或VALUES子句。
+
+- **declare_statements**
+
+  声明变量，包括变量名和变量类型，如“sales_cnt int”。
+
+- **execution_statements**
+
+  匿名块中要执行的语句。
+
+  取值范围: 已存在的函数名称。
+
+## 示例
+
+定义游标示例请参考FETCH的示例。
+
+## 相关链接
+
+[BEGIN](33-BEGIN)，[FETCH](107-FETCH)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/74-DELETE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/74-DELETE.md
new file mode 100644
index 0000000000000000000000000000000000000000..1c9b230e6fc579207056bd8ba914642e9edda147
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/74-DELETE.md
@@ -0,0 +1,110 @@
+---
+title: DELETE
+summary: DELETE
+author: GUO HUAN
+date: 2022-04-15
+---
+
+# DELETE
+
+## 功能描述
+
+DELETE从指定的表里删除满足WHERE子句的行。如果WHERE子句不存在，将删除表中所有行，结果只保留表结构。
+
+## 注意事项
+
+- 要删除表中的数据，用户必须对它有DELETE权限。同样也必须有USING子句引用的表以及condition上读取的表的SELECT权限。
+- 对于列存表，暂时不支持RETURNING子句。
+
+## 语法格式
+
+```ebnf+diagram
+Delete ::= [ WITH [ RECURSIVE ] with_query [, ...] ]
+DELETE [/*+ plan_hint */] [ FROM ] [ ONLY ] table_name [ * ] [ [ AS ] alias ]
+    [ USING using_list ]
+    [ WHERE condition | WHERE CURRENT OF cursor_name ]
+    [ RETURNING { * | { output_expr [ [ AS ] output_name ] } [, ...] } ];
+```
+
+## 参数说明
+
+- **WITH [ RECURSIVE ] with_query [, …]**
+
+  用于声明一个或多个可以在主查询中通过名称引用的子查询，相当于临时表。
+
+  如果声明了RECURSIVE，那么允许SELECT子查询通过名称引用它自己。
+
+  其中with_query的详细格式为：
+
+  ```ebnf+diagram
+  with_query_name ::= with_query_name [ ( column_name [, ...] ) ] AS
+  ( {select | values | insert | update | delete} )
+  ```
+
+  - with_query_name指定子查询生成的结果集名称，在查询中可使用该名称访问子查询的结果集。
+  - column_name指定子查询结果集中显示的列名。
+  - 每个子查询可以是SELECT，VALUES，INSERT，UPDATE或DELETE语句。
+
+- **plan_hint子句**
+
+  以`/*+ */`的形式在DELETE关键字后，用于对DELETE对应的语句块生成的计划进行hint调优，详细用法请参见章节[使用Plan Hint进行调优](9-hint-based-tuning)。每条语句中只有第一个`/*+ plan_hint */`注释块会作为hint生效，里面可以写多条hint。
+
+- **ONLY**
+
+  如果指定ONLY则只有该表被删除；如果没有声明，则该表和它的所有子表将都被删除。
+
+- **table_name**
+
+  目标表的名称（可以有模式修饰）。
+
+  取值范围: 已存在的表名。
+
+- **alias**
+
+  目标表的别名。
+
+  取值范围: 字符串，符合标识符命名规范。
+
+- **using_list**
+
+  using子句。
+
+- **condition**
+
+  一个返回Boolean值的表达式，用于判断哪些行需要被删除。
+
+- **WHERE CURRENT OF cursor_name**
+
+  当前不支持，仅保留语法接口。
+
+- **output_expr**
+
+  DELETE命令删除行之后计算输出结果的表达式。该表达式可以使用表的任意字段。可以使用*返回被删除行的所有字段。
+
+- **output_name**
+
+  一个字段的输出名称。
+
+  取值范围: 字符串，符合标识符命名规范。
+
+## 示例
+
+```sql
+--创建表tpcds.customer_address_bak。
+mogdb=# CREATE TABLE tpcds.customer_address_bak AS TABLE tpcds.customer_address;
+
+--删除tpcds.customer_address_bak中ca_address_sk小于14888的职员。
+mogdb=# DELETE FROM tpcds.customer_address_bak WHERE ca_address_sk < 14888;
+
+--删除tpcds.customer_address_bak中所有数据。
+mogdb=# DELETE FROM tpcds.customer_address_bak;
+
+--删除tpcds.customer_address_bak表。
+mogdb=# DROP TABLE tpcds.customer_address_bak;
+```
+
+## 优化建议
+
+- delete
+
+  如果要删除表中的所有记录，建议使用truncate语法。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/75-DO.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/75-DO.md
new file mode 100644
index 0000000000000000000000000000000000000000..a807ef31a79bf8a731619eab362c048e6e04c667
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/75-DO.md
@@ -0,0 +1,55 @@
+---
+title: DO
+summary: DO
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# DO
+
+## 功能描述
+
+执行匿名代码块。
+
+代码块被看做是没有参数的一段函数体，返回值类型是void。它的解析和执行是同一时刻发生的。
+
+## 注意事项
+
+- 程序语言在使用之前，必须通过命令CREATE LANGUAGE安装到当前的数据库中。 plpgsql是默认的安装语言，其它语言安装时必须指定。
+- 如果语言是不受信任的，用户必须有使用程序语言的USAGE权限，或者是系统管理员。
+
+## 语法格式
+
+```ebnf+diagram
+Do ::= DO [ LANGUAGE lang_name ] code;
+```
+
+## 参数说明
+
+- **lang_name**
+
+  用来解析代码的程序语言的名称，如果缺省，默认的语言是plpgsql。
+
+- **code**
+
+  程序语言代码可以被执行的。程序语言必须指定为字符串才行。
+
+## 示例
+
+```sql
+--创建用户webuser。
+mogdb=# CREATE USER webuser PASSWORD 'xxxxxx';
+
+--授予用户webuser对模式tpcds下视图的所有操作权限。
+mogdb=# DO $$DECLARE r record;
+BEGIN
+    FOR r IN SELECT c.relname table_name,n.nspname table_schema FROM pg_class c,pg_namespace n
+             WHERE c.relnamespace = n.oid AND n.nspname = 'tpcds' AND relkind IN ('r','v')
+    LOOP
+        EXECUTE 'GRANT ALL ON ' || quote_ident(r.table_schema) || '.' || quote_ident(r.table_name) || ' TO webuser';
+    END LOOP;
+END$$;
+
+--删除用户webuser。
+mogdb=# DROP USER webuser CASCADE;
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/75.1-DROP-AGGREGATE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/75.1-DROP-AGGREGATE.md
new file mode 100644
index 0000000000000000000000000000000000000000..f9f23cde98329985831adf89ebbe4a914180a694
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/75.1-DROP-AGGREGATE.md
@@ -0,0 +1,56 @@
+---
+title: DROP AGGREGATE
+summary: DROP AGGREGATE
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# DROP AGGREGATE
+
+## 功能描述
+
+删除一个聚合函数。
+
+## 注意事项
+
+DROP AGGREGATE删除一个现存的聚合函数，执行这条命令的用户必须是该聚合函数的所有者。
+
+## 语法格式
+
+```ebnf+diagram
+DropAggregate ::= DROP AGGREGATE [ IF EXISTS ] name ( argtype [ , ... ] ) [ CASCADE | RESTRICT ];
+```
+
+## 参数说明
+
+- **IF EXISTS**
+
+  如果指定的聚合不存在，那么发出一个 notice 而不是抛出一个错误。
+
+- **name**
+
+  现存的聚合函数名(可以有模式修饰)
+
+- **argtype**
+
+  聚合函数操作的输入数据类型，要引用一个零参数聚合函数，请用*代替输入数据类型列表。
+
+- **CASCADE**
+
+  级联删除依赖于这个聚合函数的对象
+
+- **RESTRICT**
+
+  如果有任何依赖对象，则拒绝删除这个聚合函数。这是缺省处理。
+
+## 示例
+
+将integer类型的聚合函数myavg删除：
+
+```sql
+DROP AGGREGATE myavg(integer);
+```
+
+## 兼容性
+
+SQL 标准里没有DROP AGGREGATE语句。
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/75.2-DROP-AUDIT-POLICY.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/75.2-DROP-AUDIT-POLICY.md
new file mode 100644
index 0000000000000000000000000000000000000000..1fa0fffaac217c388b49d40b2ee96d7ef0c1310b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/75.2-DROP-AUDIT-POLICY.md
@@ -0,0 +1,38 @@
+---
+title: DROP AUDIT POLICY
+summary: DROP AUDIT POLICY
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# DROP AUDIT POLICY
+
+## 功能描述
+
+删除一个审计策略。
+
+## 注意事项
+
+只有poladmin，sysadmin或初始用户才能进行此操作。
+
+## 语法格式
+
+```ebnf+diagram
+DropAuditPolicy ::= DROP AUDIT POLICY [IF EXISTS] policy_name;
+```
+
+## 参数说明
+
+policy_name
+
+审计策略名称，需要唯一，不可重复。
+
+取值范围: 字符串，要符合标识符的命名规范。
+
+## 示例
+
+请参考CREATE AUDIT POLICY的示例。
+
+## 相关链接
+
+[ALTER AUDIT POLICY](1.2-ALTER-AUDIT-POLICY)，[CREATE AUDIT POLICY](41.2-CREATE-AUDIT-POLICY)。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/75.3-DROP-CAST.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/75.3-DROP-CAST.md
new file mode 100644
index 0000000000000000000000000000000000000000..d7d4dc1a91d77e2d6214db850480849281893a99
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/75.3-DROP-CAST.md
@@ -0,0 +1,56 @@
+---
+title: DROP CAST
+summary: DROP CAST
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# DROP CAST
+
+## 功能描述
+
+删除一个类型转换.
+
+## 注意事项
+
+DROP CAST删除一个先前定义过的类型转换。
+
+要能删除一个类型转换，你必须拥有源或者目的数据类型。这是和创建一个类型转换相同的权限。
+
+## 语法格式
+
+```ebnf+diagram
+DropCast ::= DROP CAST [ IF EXISTS ] (source_type AS target_type) [ CASCADE | RESTRICT ]
+```
+
+## 参数说明
+
+- **IF EXISTS**
+
+  如果指定的转换不存在，那么发出一个 notice 而不是抛出一个错误。
+
+- **source_type**
+
+  类型转换里的源数据类型。
+
+- **target_type**
+
+  类型转换里的目标数据类型。
+
+- **CASCADE**
+
+  **RESTRICT**
+
+  这些键字没有任何效果，因为在类型转换上没有依赖关系。
+
+## 示例
+
+删除从text到int的转换：
+
+```sql
+DROP CAST (text AS int);
+```
+
+## 兼容性
+
+DROP CAST遵循 SQL 标准。
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/76-DROP-CLIENT-MASTER-KEY.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/76-DROP-CLIENT-MASTER-KEY.md
new file mode 100644
index 0000000000000000000000000000000000000000..9698ee8bdcb23e459792e068e0f5b153ec8de759
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/76-DROP-CLIENT-MASTER-KEY.md
@@ -0,0 +1,50 @@
+---
+title: DROP CLIENT MASTER KEY
+summary: DROP CLIENT MASTER KEY
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# DROP CLIENT MASTER KEY
+
+## 功能描述
+
+删除一个客户端加密主密钥(cmk)。
+
+## 注意事项
+
+- 只有客户端加密主密钥所有者或者被授予了DROP权限的用户有权限执行命令，系统管理员默认拥有此权限。
+- 该命令只能删除数据库中系统表记录的元数据信息，不能真正删除CMK密钥文件，需要通过KeyTool工具才能删除CMK密钥文件。
+
+## 语法格式
+
+```ebnf+diagram
+DropClientMasterKey ::= DROP CLIENT MASTER KEY [ IF EXISTS ] client_master_key_name [CASCADE];
+```
+
+## 参数说明
+
+- **IF EXISTS**
+
+  如果指定的客户端加密主密钥不存在，则发出一个notice而不是抛出一个错误。
+
+- **client_master_key_name**
+
+  要删除的客户端加密主密钥名称。
+
+  取值范围: 字符串，已存在的客户端加密主密钥名称。
+
+- **CASCADE**
+
+  - **CASCADE**：表示允许级联删除依赖于客户端加密主密钥的对象。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 在执行本语法的生命周期中，同时需要客户端和服务端更改状态，发生异常时可能存在服务端已删除密钥信息，但客户端未删除密钥文件的情况。 此时，客户端并不会在执行下一条语法的生命周期中，检查是否有期望被删除但却因发生异常而未被删除的密钥文件，而是需要用户定期检查密钥文件夹，对未被使用的密钥文件进行确认并处理。
+
+## **示例**
+
+```sql
+--删除客户端加密主密钥对象。
+mogdb=> DROP CLIENT MASTER KEY ImgCMK CASCADE;
+NOTICE:  drop cascades to column setting: imgcek
+DROP GLOBAL SETTING
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/77-DROP-COLUMN-ENCRYPTION-KEY.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/77-DROP-COLUMN-ENCRYPTION-KEY.md
new file mode 100644
index 0000000000000000000000000000000000000000..2dcd87d9a5ee292a17168214921c56e1c574ed58
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/77-DROP-COLUMN-ENCRYPTION-KEY.md
@@ -0,0 +1,43 @@
+---
+title: DROP COLUMN ENCRYPTION KEY
+summary: DROP COLUMN ENCRYPTION KEY
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# DROP COLUMN ENCRYPTION KEY
+
+## 功能描述
+
+删除一个列加密密钥(cek)。
+
+## 注意事项
+
+只有列加密密钥所有者或者被授予了DROP权限的用户有权限执行命令，系统管理员默认拥有此权限。
+
+## 语法格式
+
+```ebnf+diagram
+DropColumnEncryptionKey ::= DROP COLUMN ENCRYPTION KEY [ IF EXISTS ] column_encryption_key_name [CASCADE];
+```
+
+## 参数说明
+
+- **IF EXISTS**
+
+  如果指定的列加密密钥不存在，则发出一个notice而不是抛出一个错误。
+
+- **column_encryption_key_name**
+
+  要删除的列加密密钥名称。
+
+  取值范围: 字符串，已存在的列加密密钥名称。
+
+## 示例
+
+```sql
+--删除客户端加密主密钥对象。
+mogdb=# DROP COLUMN ENCRYPTION KEY ImgCEK CASCADE;
+ERROR:  cannot drop column setting: imgcek cascadely because encrypted column depend on it.
+HINT:  we have to drop encrypted column: name, ... before drop column setting: imgcek cascadely.
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/78-DROP-DATABASE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/78-DROP-DATABASE.md
new file mode 100644
index 0000000000000000000000000000000000000000..78a9bd94a4938aa7d14108a2593d74ca22281c73
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/78-DROP-DATABASE.md
@@ -0,0 +1,54 @@
+---
+title: DROP DATABASE
+summary: DROP DATABASE
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# DROP DATABASE
+
+## 功能描述
+
+删除一个数据库。
+
+## 注意事项
+
+- 只有数据库所有者或者被授予了数据库DROP权限的用户有权限执行DROP DATABASE命令，系统管理员默认拥有此权限。
+- 不能对系统默认安装的三个数据库（POSTGRES、TEMPLATE0和TEMPLATE1）执行删除操作，系统做了保护。如果想查看当前服务中有哪几个数据库，可以用gsql的\l命令查看。
+- 如果有用户正在与要删除的数据库连接，则删除操作失败。
+- 不能在事务块中执行DROP DATABASE命令。
+- 如果执行DROP DATABASE失败，事务回滚，需要再次执行一次DROP DATABASE IF EXISTS。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** DROP DATABASE一旦执行将无法撤销，请谨慎使用。
+
+## 语法格式
+
+```ebnf+diagram
+DropDatabase ::= DROP DATABASE [ IF EXISTS ] database_name ;
+```
+
+## 参数说明
+
+- **IF EXISTS**
+
+  如果指定的数据库不存在，则发出一个notice而不是抛出一个错误。
+
+- **database_name**
+
+  要删除的数据库名称。
+
+  取值范围: 字符串，已存在的数据库名称。
+
+## 示例
+
+请参见CREATE DATABASE的示例。
+
+## 相关链接
+
+[CREATE DATABASE](44-CREATE-DATABASE)
+
+## 优化建议
+
+- drop database
+
+  不支持在事务中删除database。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/79-DROP-DATA-SOURCE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/79-DROP-DATA-SOURCE.md
new file mode 100644
index 0000000000000000000000000000000000000000..98b9a7fbead9d17eb2553896fe6bf1c9732d6232
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/79-DROP-DATA-SOURCE.md
@@ -0,0 +1,57 @@
+---
+title: DROP DATA SOURCE
+summary: DROP DATA SOURCE
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# DROP DATA SOURCE
+
+## 功能描述
+
+删除一个Data Source对象。
+
+## 注意事项
+
+只有属主/系统管理员/初始用户才可以删除一个Data Source对象。
+
+## 语法格式
+
+```ebnf+diagram
+DropDataSource ::= DROP DATA SOURCE [IF EXISTS] src_name [CASCADE | RESTRICT];
+```
+
+## 参数说明
+
+- **src_name**
+
+  待删除的Data Source对象名称。
+
+  取值范围: 字符串，符合标识符命名规范。
+
+- **IF EXISTS**
+
+  如果指定的Data Source不存在，则发出一个notice而不是报错。
+
+- **CASCADE | RESTRICT**
+
+  - **CASCADE**：表示允许级联删除依赖于Data Source的对象
+
+  - **RESTRICT**（缺省值）：表示有依赖于该Data Source的对象存在，则该Data Source无法删除。
+
+  目前Data Source对象没有被依赖的对象，CASCADE和RESTRICT效果一样，保留此选项是为了向后兼容性。
+
+## 示例
+
+```sql
+--创建Data Source对象。
+mogdb=# CREATE DATA SOURCE ds_tst1;
+
+--删除Data Source对象。
+mogdb=# DROP DATA SOURCE ds_tst1 CASCADE;
+mogdb=# DROP DATA SOURCE IF EXISTS ds_tst1 RESTRICT;
+```
+
+## 相关链接
+
+[CREATE DATA SOURCE](45-CREATE-DATA-SOURCE)，[ALTER DATA SOURCE](3-ALTER-DATA-SOURCE)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/8-ALTER-GROUP.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/8-ALTER-GROUP.md
new file mode 100644
index 0000000000000000000000000000000000000000..79ac4abc527aa9a959f0729e2f3115da0ac0a632
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/8-ALTER-GROUP.md
@@ -0,0 +1,60 @@
+---
+title: ALTER GROUP
+summary: ALTER GROUP
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER GROUP
+
+## 功能描述
+
+修改一个用户组的属性。
+
+## 注意事项
+
+ALTER GROUP是ALTER ROLE的别名，非SQL标准语法，不推荐使用，建议用户直接使用ALTER ROLE替代。
+
+## 语法格式
+
+- 向用户组中添加用户。
+
+  ```ebnf+diagram
+  AlterGroup ::= ALTER GROUP group_name
+      ADD USER user_name [, ... ];
+  ```
+
+- 从用户组中删除用户。
+
+  ```ebnf+diagram
+  AlterGroup ::= ALTER GROUP group_name
+      DROP USER user_name [, ... ];
+  ```
+
+- 修改用户组的名称。
+
+  ```ebnf+diagram
+  AlterGroup ::= ALTER GROUP group_name
+      RENAME TO new_name;
+  ```
+
+## 参数说明
+
+请参考[ALTER ROLE](12-ALTER-ROLE)的参数说明。
+
+## 示例
+
+```sql
+--向用户组中添加用户。
+mogdb=# ALTER GROUP super_users ADD USER lche, jim;
+
+--从用户组中删除用户。
+mogdb=# ALTER GROUP super_users DROP USER jim;
+
+--修改用户组的名称。
+mogdb=# ALTER GROUP super_users RENAME TO normal_users;
+```
+
+## 相关链接
+
+[ALTER GROUP](8-ALTER-GROUP)，[DROP GROUP](83-DROP-GROUP)，[ALTER ROLE](12-ALTER-ROLE)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/80-DROP-DIRECTORY.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/80-DROP-DIRECTORY.md
new file mode 100644
index 0000000000000000000000000000000000000000..8063972c845089e2891bf2efbeb07f71dcc88865
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/80-DROP-DIRECTORY.md
@@ -0,0 +1,44 @@
+---
+title: DROP DIRECTORY
+summary: DROP DIRECTORY
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# DROP DIRECTORY
+
+## 功能描述
+
+删除指定的directory对象。
+
+## 注意事项
+
+默认只有初始化用户可以执行drop操作，当enable_access_server_directory开启时，sysadmin权限的用户也可以执行drop操作。
+
+## 语法格式
+
+```ebnf+diagram
+DropDictionary ::= DROP DIRECTORY [ IF EXISTS ] directory_name;
+```
+
+## 参数说明
+
+- **directory_name**
+
+  目录名称。
+
+  取值范围: 已经存在的目录名。
+
+## 示例
+
+```sql
+--创建目录。
+mogdb=# CREATE OR REPLACE DIRECTORY  dir  as '/tmp/';
+
+--删除目录。
+mogdb=# DROP DIRECTORY dir;
+```
+
+## 相关链接
+
+[CREATE DIRECTORY](46-CREATE-DIRECTORY)，[ALTER DIRECTORY](5-ALTER-DIRECTORY)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/80.1-DROP-EXTENSION.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/80.1-DROP-EXTENSION.md
new file mode 100644
index 0000000000000000000000000000000000000000..2beaaa554f184aa412fff8eb5a3fc6d7bd2a4cf1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/80.1-DROP-EXTENSION.md
@@ -0,0 +1,51 @@
+---
+title: DROP EXTENSION
+summary: DROP EXTENSION
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# DROP EXTENSION
+
+## 功能描述
+
+删除一个扩展。
+
+## 注意事项
+
+- DROP EXTENSION 命令从数据库中删除一个扩展。 在删除扩展的过程中，构成扩展的组件也会一起删除。
+- 必须是扩展的拥有者才能够使用DROP EXTENSION命令。
+
+## 语法格式
+
+```ebnf+diagram
+DropExtension ::= DROP EXTENSION [ IF EXISTS ] name [, ...] [ CASCADE | RESTRICT ]
+```
+
+## 参数说明
+
+- **IF EXISTS**
+
+  当使用IF EXISTS参数，如果扩展不存在时，不会抛出错误，而是产生一个通知。
+
+- **name**
+
+  已经安装的扩展模块的名称。
+
+- **CASCADE**
+
+  自动删除依赖于该扩展的对象。
+
+- **RESTRICT**
+
+  如果有依赖于扩展的对象，则不允许删除次扩展（除非它所有的成员对象和其它扩展对象在一条 DROP命令一起删除）。 这是缺省行为。
+
+## 示例
+
+从当前数据库中删除扩展hstore
+
+```sql
+DROP EXTENSION hstore;
+```
+
+在当前数据库中，如果有使用hstore的对象的，这条命令就会失败，比如 任一表中的字段使用hstore类型。这时增加CASCADE选项会强制删除扩展和 依赖于扩展的对象。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/81-DROP-FOREIGN-TABLE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/81-DROP-FOREIGN-TABLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..34438c350ffb74a1e5cb8ebcca00d871180a1c61
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/81-DROP-FOREIGN-TABLE.md
@@ -0,0 +1,44 @@
+---
+title: DROP FOREIGN TABLE
+summary: DROP FOREIGN TABLE
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# DROP FOREIGN TABLE
+
+## 功能描述
+
+删除指定的外表。
+
+## 注意事项
+
+DROP FOREIGN TABLE会强制删除指定的表，删除表后，依赖该表的索引会被删除，而使用到该表的函数和存储过程将无法执行。
+
+## 语法格式
+
+```ebnf+diagram
+DropForeignTable ::= DROP FOREIGN TABLE [ IF EXISTS ]
+    table_name [, ...] [ CASCADE | RESTRICT ];
+```
+
+## 参数说明
+
+- **IF EXISTS**
+
+  如果指定的表不存在，则发出一个notice而不是抛出一个错误。
+
+- **table_name**
+
+  表名称。
+
+  取值范围: 已存在的表名。
+
+- **CASCADE | RESTRICT**
+
+  - CASCADE：级联删除依赖于表的对象（比如视图）。
+  - RESTRICT：如果存在依赖对象，则拒绝删除该表。这个是缺省。
+
+## 相关链接
+
+[ALTER FOREIGN TABLE](6-ALTER-FOREIGN-TABLE)，[CREATE FOREIGN TABLE](47-CREATE-FOREIGN-TABLE)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/82-DROP-FUNCTION.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/82-DROP-FUNCTION.md
new file mode 100644
index 0000000000000000000000000000000000000000..f22df27e7550a2ff84e920210920dc99de31a8b8
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/82-DROP-FUNCTION.md
@@ -0,0 +1,56 @@
+---
+title: DROP FUNCTION
+summary: DROP FUNCTION
+author: Zhang Cuiping
+date: 2021-05-10
+---
+
+# DROP FUNCTION
+
+## 功能描述
+
+删除一个已存在的函数。
+
+## 注意事项
+
+- 如果函数中涉及对临时表相关操作，则无法使用DROP FUNCTION删除函数。
+- 只有函数的所有者或者被授予了函数DROP权限的用户才能执行DROP FUNCTION命令，系统管理员默认拥有该权限。
+
+## 语法格式
+
+```ebnf+diagram
+DropFunction ::= DROP FUNCTION [ IF EXISTS ] function_name
+[ ( [ {[ argmode ] [ argname ] argtype} [, ...] ] ) [ CASCADE | RESTRICT ] ];
+```
+
+## 参数说明
+
+- **IF EXISTS**
+
+  IF EXISTS表示，如果函数存在则执行删除操作，函数不存在也不会报错，只是发出一个notice。
+
+- **function_name**
+
+  要删除的函数名称。
+
+  取值范围: 已存在的函数名。
+
+- **argmode**
+
+  函数参数的模式。
+
+- **argname**
+
+  函数参数的名称。
+
+- **argtype**
+
+  函数参数的类型
+
+## 示例
+
+请参见的示例。
+
+## 相关链接
+
+[ALTER FUNCTION](7-ALTER-FUNCTION)，[CREATE FUNCTION](48-CREATE-FUNCTION)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/83-DROP-GROUP.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/83-DROP-GROUP.md
new file mode 100644
index 0000000000000000000000000000000000000000..513acfc27ed87833e086f985ca8af960a5f85601
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/83-DROP-GROUP.md
@@ -0,0 +1,32 @@
+---
+title: DROP GROUP
+summary: DROP GROUP
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP GROUP
+
+## 功能描述
+
+删除用户组。
+
+DROP GROUP是DROP ROLE的别名。
+
+## 注意事项
+
+DROP GROUP是MogDB管理工具封装的内部接口，用来实现MogDB管理。该接口不建议用户直接使用，以免对MogDB状态造成影响。
+
+## 语法格式
+
+```ebnf+diagram
+DropGroup ::= DROP GROUP [ IF EXISTS ] group_name [, ...];
+```
+
+## 参数说明
+
+请参见DROP ROLE的参数说明。
+
+## 相关链接
+
+[CREATE GROUP](49-CREATE-GROUP)，[ALTER GROUP](8-ALTER-GROUP)，[DROP ROLE](89-DROP-ROLE)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/84-DROP-INDEX.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/84-DROP-INDEX.md
new file mode 100644
index 0000000000000000000000000000000000000000..a7f77bbbf93fbfc3b98383bfb2df36896d6dbcf3
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/84-DROP-INDEX.md
@@ -0,0 +1,56 @@
+---
+title: DROP INDEX
+summary: DROP INDEX
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP INDEX
+
+## 功能描述
+
+删除索引。
+
+## 注意事项
+
+只有索引的所有者或者拥有索引所在表的INDEX权限的用户有权限执行DROP INDEX命令，系统管理员默认拥有此权限。
+
+## 语法格式
+
+```ebnf+diagram
+DropIndex ::= DROP INDEX [ CONCURRENTLY ] [ IF EXISTS ]
+    index_name [, ...] [ CASCADE | RESTRICT ];
+```
+
+## 参数说明
+
+- **CONCURRENTLY**
+
+  以不加锁的方式删除索引。删除索引时，一般会阻塞其他语句对该索引所依赖表的访问。加此关键字，可实现删除过程中不做阻塞。
+
+  此选项只能指定一个索引的名称， 并且CASCADE选项不支持。
+
+  普通DROP INDEX命令可以在事务内执行，但是DROP INDEX CONCURRENTLY不可以在事务内执行。
+
+- **IF EXISTS**
+
+  如果指定的索引不存在，则发出一个notice而不是抛出一个错误。
+
+- **index_name**
+
+  要删除的索引名。
+
+  取值范围: 已存在的索引。
+
+- **CASCADE | RESTRICT**
+
+  - CASCADE：表示允许级联删除依赖于该索引的对象。
+  - RESTRICT（缺省值）：表示有依赖与此索引的对象存在，则该索引无法被删除。
+
+## 示例
+
+请参见CREATE INDEX的示例。
+
+## 相关链接
+
+[ALTER INDEX](9-ALTER-INDEX)，[CREATE INDEX](50-CREATE-INDEX)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/84.1-DROP-LANGUAGE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/84.1-DROP-LANGUAGE.md
new file mode 100644
index 0000000000000000000000000000000000000000..d007b276bdfb655dd961a29f97589e2581c59da8
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/84.1-DROP-LANGUAGE.md
@@ -0,0 +1,48 @@
+---
+title: DROP LANGUAGE
+summary: DROP LANGUAGE
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# DROP LANGUAGE
+
+## 功能描述
+
+删除一个过程语言
+
+## 语法格式
+
+```ebnf+diagram
+DropLanguage ::= DROP [ PROCEDURAL ] LANGUAGE [ IF EXISTS ] name [ CASCADE | RESTRICT ]
+```
+
+## 参数说明
+
+- **IF EXISTS**
+
+  如果指定的过程语言不存在，那么发出一个 notice 而不是抛出一个错误。
+
+- **name**
+
+  现存语言的名称。出于向下兼容的考虑，这个名字可以用单引号包围。
+
+- **CASCADE**
+
+  级联删除依赖于该语言的对象(比如该语言写的函数)。
+
+- **RESTRICT**
+
+  如果存在依赖对象，则拒绝删除。这个是缺省。
+
+## 示例
+
+下面命令删除plsample语言：
+
+```sql
+DROP LANGUAGE plsample;
+```
+
+## 兼容性
+
+SQL标准里没有DROP LANGUAGE语句。
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/84.2-DROP-MASKING-POLICY.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/84.2-DROP-MASKING-POLICY.md
new file mode 100644
index 0000000000000000000000000000000000000000..3149b0d7fda231b42c8aa9556d466159f38250ef
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/84.2-DROP-MASKING-POLICY.md
@@ -0,0 +1,44 @@
+---
+title: DROP MASKING POLICY
+summary: DROP MASKING POLICY
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# DROP MASKING POLICY
+
+## 功能描述
+
+删除脱敏策略。
+
+## 注意事项
+
+只有poladmin，sysadmin或初始用户才能执行此操作。
+
+## 语法格式
+
+```ebnf+diagram
+DropMaskingPolicy ::= DROP MASKING POLICY [IF EXISTS] policy_name;
+```
+
+## 参数说明
+
+**policy_name**
+
+审计策略名称，需要唯一，不可重复。
+
+取值范围: 字符串，要符合标识符的命名规范。
+
+## 示例
+
+```sql
+--删除一个脱敏策略。
+mogdb=# DROP MASKING POLICY IF EXISTS maskpol1;
+
+--删除一组脱敏策略。
+mogdb=# DROP MASKING POLICY IF EXISTS maskpol1, maskpol2, maskpol3;
+```
+
+## 相关链接
+
+[ALTER MASKING POLICY](10.1-ALTER-MASKING-POLICY)，[CREATE MASKING POLICY](50.2-CREATE-MASKING-POLICY)。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/84.3-DROP-MODEL.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/84.3-DROP-MODEL.md
new file mode 100644
index 0000000000000000000000000000000000000000..f998e6ab782a47b6da53d3ced494c0c44206f11c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/84.3-DROP-MODEL.md
@@ -0,0 +1,34 @@
+---
+title: DROP MODEL
+summary: DROP MODEL
+author: Zhang Cuiping
+date: 2021-11-01
+---
+
+# DROP MODEL
+
+## 功能描述
+
+删除一个已训练完成保存的模型对象。
+
+## 注意事项
+
+所删除模型可在系统表gs_model_warehouse中查看到。
+
+## 语法格式
+
+```ebnf+diagram
+DropModel ::= DROP MODEL model_name;
+```
+
+## 参数说明
+
+model_name
+
+模型名称
+
+取值范围: 字符串，需要符合标识符的命名规范。
+
+## 相关链接
+
+[CREATE MODEL](50.3-CREATE-MODEL)，[PREDICT BY](112.1-PREDICT-BY)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/85-DROP-MATERIALIZED-VIEW.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/85-DROP-MATERIALIZED-VIEW.md
new file mode 100644
index 0000000000000000000000000000000000000000..e474098b7e424707c691806a1cdae98e581a87f0
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/85-DROP-MATERIALIZED-VIEW.md
@@ -0,0 +1,48 @@
+---
+title: DROP MATERIALIZED VIEW
+summary: DROP MATERIALIZED VIEW
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP MATERIALIZED VIEW
+
+## 功能描述
+
+强制删除数据库中已有的物化视图。
+
+## 注意事项
+
+只有物化视图的所有者有权限执行DROP MATERIALIZED VIEW命令，系统管理员默认拥有此权限。
+
+## 语法格式
+
+```ebnf+diagram
+DropMaterializedView ::= DROP MATERIALIZED VIEW [ IF EXISTS ] mv_name [, ...] [ CASCADE | RESTRICT ];
+```
+
+## 参数说明
+
+- **IF EXISTS**
+
+  如果指定的物化视图不存在，则发出一个notice而不是抛出一个错误。
+
+- **mv_name**
+
+  要删除的物化视图名称。
+
+- **CASCADE | RESTRICT**
+
+  - CASCADE：级联删除依赖此物化视图的对象。
+  - RESTRICT：如果有依赖对象存在，则拒绝删除此物化视图。此选项为缺省值。
+
+## 示例
+
+```sql
+--删除名为my_mv的物化视图。
+mogdb=# DROP MATERIALIZED VIEW my_mv;
+```
+
+## 相关链接
+
+[ALTER MATERIALIZED VIEW](11-ALTER-MATERIALIZED-VIEW)，[CREATE INCREMENTAL MATERIALIZED VIEW](49.1-CREATE-INCREMENTAL-MATERIALIZED-VIEW)， [CREATE MATERIALIZED VIEW](51-CREATE-MATERIALIZED-VIEW)，[CREATE TABLE](60-CREATE-TABLE)，[REFRESH INCREMENTAL MATERIALIZED VIEW](115.1-REFRESH-INCREMENTAL-MATERIALIZED-VIEW)，[REFRESH MATERIALIZED VIEW](116-REFRESH-MATERIALIZED-VIEW)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/85.1-DROP-OPERATOR.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/85.1-DROP-OPERATOR.md
new file mode 100644
index 0000000000000000000000000000000000000000..6e8a312895bd3b122b2723bdeeab2eb71ba6d6f3
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/85.1-DROP-OPERATOR.md
@@ -0,0 +1,72 @@
+---
+title: DROP OPERATOR
+summary: DROP OPERATOR
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# DROP OPERATOR
+
+## 功能描述
+
+删除一个操作符。
+
+## 注意事项
+
+DROP OPERATOR语句从数据库中删除一个现存的操作符。要执行这个命令，你必须是操作符所有者。
+
+## 语法格式
+
+```ebnf+diagram
+DropOperator ::= DROP OPERATOR [ IF EXISTS ] name ( { left_type | NONE } , { right_type | NONE } ) [ CASCADE | RESTRICT ]
+```
+
+## 参数说明
+
+- **IF EXISTS**
+
+  如果指定的操作符不存在，那么发出一个 notice 而不是抛出一个错误。
+
+- **name**
+
+  一个现存的操作符的名字（可以有模式修饰）。
+
+- **left_type**
+
+  该操作符左操作数的类型。如果没有则写NONE。
+
+- **right_type**
+
+  该操作符右操作数的类型。如果没有则写NONE。
+
+- **CASCADE**
+
+  级联删除依赖于此操作符的所有对象。
+
+- **RESTRICT**
+
+  如果有任何依赖对象则拒绝删除此操作符。这个是缺省项。
+
+## 示例
+
+将用于integer的幂操作符a^b删除：
+
+```sql
+DROP OPERATOR ^ (integer, integer);
+```
+
+为类型bit删除左单目位操作符~b：
+
+```sql
+DROP OPERATOR ~ (none, bit);
+```
+
+删除用于bigint的阶乘x!：
+
+```sql
+DROP OPERATOR ! (bigint, none);
+```
+
+## 兼容性
+
+SQL 标准里没有DROP OPERATOR语句
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/86-DROP-OWNED.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/86-DROP-OWNED.md
new file mode 100644
index 0000000000000000000000000000000000000000..f42f4d606c263fbb6124d39306fd7a1c2dbc120f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/86-DROP-OWNED.md
@@ -0,0 +1,40 @@
+---
+title: DROP OWNED
+summary: DROP OWNED
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP OWNED
+
+## 功能描述
+
+删除一个数据库角色所拥有的数据库对象。
+
+## 注意事项
+
+- 所有该角色在当前数据库里和共享对象（数据库，表空间） 上的所有对象上的权限都将被撤销。
+- DROP OWNED常常被用来为移除一个或者多个角色做准备。因为DROP OWNED只影响当前数据库中的对象，通常需要在包含将被移除角色所拥有的对象的每一个数据库中都执行这个命令。
+- 使用CASCADE选项可能导致这个命令递归去删除由其他用户所拥有的对象。
+- 角色所拥有的数据库、表空间将不会被移除。
+
+## 语法格式
+
+```ebnf+diagram
+DropOwned ::= DROP OWNED BY name [, ...] [ CASCADE | RESTRICT ];
+```
+
+## 参数说明
+
+- **name**
+
+  角色名。
+
+- **CASCADE | RESTRICT**
+
+  - CASCADE：级联删除所有依赖于被删除对象的对象。
+  - RESTRICT（缺省值）：拒绝删除那些有任何依赖对象存在的对象。
+
+## 相关链接
+
+[REASSIGN OWNED](115-REASSIGN-OWNED) , [DROP ROLE](89-DROP-ROLE)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/86.1-DROP-RESOURCE-LABEL.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/86.1-DROP-RESOURCE-LABEL.md
new file mode 100644
index 0000000000000000000000000000000000000000..1ef2e437488c308342095c4c8ab0834cc2f30d5a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/86.1-DROP-RESOURCE-LABEL.md
@@ -0,0 +1,44 @@
+---
+title: DROP RESOURCE LABEL
+summary: DROP RESOURCE LABEL
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# DROP RESOURCE LABEL
+
+## 功能描述
+
+删除资源标签。
+
+## 注意事项
+
+只有poladmin，sysadmin或初始用户才能执行此操作。
+
+## 语法格式
+
+```ebnf+diagram
+DropResourceLabel ::= DROP RESOURCE LABEL [IF EXISTS] policy_name[, ...]*;
+```
+
+## 参数说明
+
+**label_name**
+
+资源标签名称；
+
+取值范围: 字符串，要符合标识符的命名规范。
+
+## 示例
+
+```sql
+--删除一个资源标签。
+mogdb=# DROP RESOURCE LABEL IF EXISTS res_label1;
+
+--删除一组资源标签。
+mogdb=# DROP RESOURCE LABEL IF EXISTS res_label1, res_label2, res_label3;
+```
+
+## 相关链接
+
+[ALTER RESOURCE LABEL](11.2-ALTER-RESOURCE-LABEL)，[CREATE RESOURCE LABEL](53.1-CREATE-RESOURCE-LABEL)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/86.2-DROP-RESOURCE-POOL.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/86.2-DROP-RESOURCE-POOL.md
new file mode 100644
index 0000000000000000000000000000000000000000..74b5510d9dc7b8638a39c72b8b9da0493713fb99
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/86.2-DROP-RESOURCE-POOL.md
@@ -0,0 +1,44 @@
+---
+title: DROP RESOURCE POOL
+summary: DROP RESOURCE POOL
+author: Zhang Cuiping
+date: 2021-11-01
+---
+
+# DROP RESOURCE POOL
+
+## 功能描述
+
+删除一个资源池。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 如果某个角色已关联到该资源池，无法删除。
+
+## 注意事项
+
+只要用户对当前数据库有DROP权限，就可以删除资源池。
+
+## 语法格式
+
+```ebnf+diagram
+DropResourcePool ::= DROP RESOURCE POOL [ IF EXISTS ] pool_name;
+```
+
+## 参数说明
+
+- **IF EXISTS**
+
+  如果指定的资源池不存在，发出一个notice而不是抛出一个错误。
+
+- **pool_name**
+
+  已创建过的资源池名称。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+## 示例
+
+请参见CREATE RESOURCE POOL的示例。
+
+## 相关链接
+
+[ALTER RESOURCE POOL](11.3-ALTER-RESOURCE-POOL)，[CREATE RESOURCE POOL](53.2-CREATE-RESOURCE-POOL)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/86.3-DROP-PACKAGE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/86.3-DROP-PACKAGE.md
new file mode 100644
index 0000000000000000000000000000000000000000..b2b989160f92a904a004f52fc4fb07241f67b1fd
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/86.3-DROP-PACKAGE.md
@@ -0,0 +1,23 @@
+---
+title: DROP PACKAGE
+summary: DROP PACKAGE
+author: Zhang Cuiping
+date: 2021-11-08
+---
+
+# DROP PACKAGE
+
+## 功能描述
+
+删除已存在的PACKAGE或者PACKAGE BODY。
+
+## 注意事项
+
+删除PACKAGE BODY后，PACKAGE内的存储过程及函数会同时失效。
+
+## 语法格式
+
+```sql
+DROP PACKAGE [ IF EXISTS ] package_name;
+DROP PACKAGE BODY [ IF EXISTS ] package_name;
+```
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/87-DROP-ROW-LEVEL-SECURITY-POLICY.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/87-DROP-ROW-LEVEL-SECURITY-POLICY.md
new file mode 100644
index 0000000000000000000000000000000000000000..1de3049f81dbf99a9b51ad759e789334cc1ae302
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/87-DROP-ROW-LEVEL-SECURITY-POLICY.md
@@ -0,0 +1,57 @@
+---
+title: DROP ROW LEVEL SECURITY POLICY
+summary: DROP ROW LEVEL SECURITY POLICY
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP ROW LEVEL SECURITY POLICY
+
+## 功能描述
+
+删除表上某个行访问控制策略。
+
+## 注意事项
+
+仅表的所有者或者管理员用户才能删除表的行访问控制策略。
+
+## 语法格式
+
+```ebnf+diagram
+DropRowLevelSecurityPolicy ::= DROP [ ROW LEVEL SECURITY ] POLICY [ IF EXISTS ] policy_name ON table_name [ CASCADE | RESTRICT ]
+```
+
+## 参数说明
+
+- **IF EXISTS**
+
+  如果指定的行访问控制策略不存在，发出一个notice而不是抛出一个错误。
+
+- **policy_name**
+
+  要删除的行访问控制策略的名称。
+
+  - table_name
+
+    行访问控制策略所在的数据表名。
+
+  - CASCADE/RESTRICT
+
+    仅适配此语法，无对象依赖于该行访问控制策略，CASCADE和RESTRICT效果相同。
+
+## 示例
+
+```sql
+--创建数据表all_data
+mogdb=# CREATE TABLE all_data(id int, role varchar(100), data varchar(100));
+
+--创建行访问控制策略
+mogdb=# CREATE ROW LEVEL SECURITY POLICY all_data_rls ON all_data USING(role = CURRENT_USER);
+
+--删除行访问控制策略
+mogdb=# DROP ROW LEVEL SECURITY POLICY all_data_rls ON all_data;
+```
+
+## 相关链接
+
+[ALTER ROW LEVEL SECURITY POLICY](13-ALTER-ROW-LEVEL-SECURITY-POLICY)，[CREATE ROW LEVEL SECURITY POLICY](52-CREATE-ROW-LEVEL-SECURITY-POLICY)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/88-DROP-PROCEDURE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/88-DROP-PROCEDURE.md
new file mode 100644
index 0000000000000000000000000000000000000000..ebef86fca21d75abf7acde2e09775060485d216d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/88-DROP-PROCEDURE.md
@@ -0,0 +1,38 @@
+---
+title: DROP PROCEDURE
+summary: DROP PROCEDURE
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP PROCEDURE
+
+## 功能描述
+
+删除已存在的存储过程。
+
+## 注意事项
+
+无。
+
+## 语法格式
+
+```ebnf+diagram
+DropProcedure ::= DROP PROCEDURE [ IF EXISTS  ] procedure_name;
+```
+
+## 参数说明
+
+- **IF EXISTS**
+
+  如果指定的存储过程不存在，发出一个notice而不是抛出一个错误。
+
+- **procedure_name**
+
+  要删除的存储过程名称。
+
+  取值范围: 已存在的存储过程名。
+
+## 相关链接
+
+[CREATE PROCEDURE](53-CREATE-PROCEDURE)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/89-DROP-ROLE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/89-DROP-ROLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..f227b6168c7f01a958574d63779a4f29351ffc9f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/89-DROP-ROLE.md
@@ -0,0 +1,42 @@
+---
+title: DROP ROLE
+summary: DROP ROLE
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP ROLE
+
+## 功能描述
+
+删除指定的角色。
+
+## 注意事项
+
+无。
+
+## 语法格式
+
+```ebnf+diagram
+DropRole ::= DROP ROLE [ IF EXISTS ] role_name [, ...];
+```
+
+## 参数说明
+
+- **IF EXISTS**
+
+  如果指定的角色不存在，则发出一个notice而不是抛出一个错误。
+
+- **role_name**
+
+  要删除的角色名称。
+
+  取值范围: 已存在的角色。
+
+## 示例
+
+请参见CREATE ROLE的示例。
+
+## 相关链接
+
+[CREATE ROLE](54-CREATE-ROLE)，[ALTER ROLE](12-ALTER-ROLE)，[SET ROLE](129-SET-ROLE)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/9-ALTER-INDEX.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/9-ALTER-INDEX.md
new file mode 100644
index 0000000000000000000000000000000000000000..51559d97d04d2c50586ace988622623ec61c5dfb
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/9-ALTER-INDEX.md
@@ -0,0 +1,160 @@
+---
+title: ALTER INDEX
+summary: ALTER INDEX
+author: Zhang Cuiping
+date: 2021-05-17
+---
+
+# ALTER INDEX
+
+## 功能描述
+
+ALTER INDEX用于修改现有索引的定义。
+
+它有几种子形式：
+
+- IF EXISTS
+
+  如果指定的索引不存在，则发出一个notice而不是error。
+
+- RENAME TO
+
+  只改变索引的名称。对存储的数据没有影响。
+
+- SET TABLESPACE
+
+  这个选项会改变索引的表空间为指定表空间，并且把索引相关的数据文件移动到新的表空间里。
+
+- SET ( { STORAGE_PARAMETER = value } [, …] )
+
+  改变索引的一个或多个索引方法特定的存储参数。 需要注意的是索引内容不会被这个命令立即修改，根据参数的不同，可能需要使用REINDEX重建索引来获得期望的效果。
+
+- RESET ( { storage_parameter } [, …] )
+
+  重置索引的一个或多个索引方法特定的存储参数为缺省值。与SET一样，可能需要使用REINDEX来完全更新索引。
+
+- [ MODIFY PARTITION index_partition_name ] UNUSABLE
+
+  用于设置表或者索引分区上的索引不可用。
+
+- REBUILD [ PARTITION index_partition_name ]
+
+  用于重建表或者索引分区上的索引。
+
+- RENAME PARTITION
+
+  用于重命名索引分区。
+
+- MOVE PARTITION
+
+  用于修改索引分区的所属表空间。
+
+## 注意事项
+
+只有索引的所有者或者拥有索引所在表的INDEX权限的用户有权限执行此命令，系统管理员默认拥有此权限。
+
+## 语法格式
+
+- 重命名表索引的名称。
+
+  ```ebnf+diagram
+  AlterIndex ::= ALTER INDEX [ IF EXISTS ] index_name
+      RENAME TO new_name;
+  ```
+
+- 修改表索引的所属空间。
+
+  ```ebnf+diagram
+  AlterIndex ::= ALTER INDEX [ IF EXISTS ] index_name
+      SET TABLESPACE tablespace_name;
+  ```
+
+- 修改表索引的存储参数。
+
+  ```ebnf+diagram
+  AlterIndex ::= ALTER INDEX [ IF EXISTS ] index_name
+      SET ( {storage_parameter = value} [, ... ] );
+  ```
+
+- 重置表索引的存储参数。
+
+  ```ebnf+diagram
+  AlterIndex ::= ALTER INDEX [ IF EXISTS ] index_name
+      RESET ( storage_parameter [, ... ] ) ;
+  ```
+
+- 设置表索引或索引分区不可用。
+
+  ```ebnf+diagram
+  AlterIndex ::= ALTER INDEX [ IF EXISTS ] index_name
+      [ MODIFY PARTITION index_partition_name ] UNUSABLE;
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 列存表不支持该语法。
+
+- 重建表索引或索引分区。
+
+  ```ebnf+diagram
+  AlterIndex ::= ALTER INDEX index_name
+      REBUILD [ PARTITION index_partition_name ];
+  ```
+
+- 重命名索引分区。
+
+  ```ebnf+diagram
+  AlterIndex ::= ALTER INDEX [ IF EXISTS ] index_name
+      RENAME PARTITION index_partition_name TO new_index_partition_name;
+  ```
+
+- 修改索引分区的所属表空间。
+
+  ```ebnf+diagram
+  AlterIndex ::= ALTER INDEX [ IF EXISTS ] index_name
+      MOVE PARTITION index_partition_name TABLESPACE new_tablespace;
+  ```
+
+## 参数说明
+
+- **index_name**
+
+  要修改的索引名。
+
+- **new_name**
+
+  新的索引名。
+
+  取值范围: 字符串，且符合标识符命名规范。
+
+- **tablespace_name**
+
+  表空间的名称。
+
+  取值范围: 已存在的表空间。
+
+- **storage_parameter**
+
+  索引方法特定的参数名。
+
+- **value**
+
+  索引方法特定的存储参数的新值。根据参数的不同，这可能是一个数字或单词。
+
+- **new_index_partition_name**
+
+  新索引分区名。
+
+- **index_partition_name**
+
+  索引分区名。
+
+- **new_tablespace**
+
+  新表空间。
+
+## 示例
+
+请参见[CREATE INDEX](50-CREATE-INDEX)的示例。
+
+## 相关链接
+
+[CREATE INDEX](50-CREATE-INDEX)，[DROP INDEX](84-DROP-INDEX)，[REINDEX](117-REINDEX)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/9.1-ALTER-LANGUAGE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/9.1-ALTER-LANGUAGE.md
new file mode 100644
index 0000000000000000000000000000000000000000..053b706928e74fa99d8d10b6376c433c52f75c68
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/9.1-ALTER-LANGUAGE.md
@@ -0,0 +1,36 @@
+---
+title: ALTER LANGUAGE
+summary: ALTER LANGUAGE
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# ALTER LANGUAGE
+
+## 功能描述
+
+修改一个过程语言的定义。单机和集中式暂不支持修改过程语言。
+
+## 语法格式
+
+```ebnf+diagram
+AlterLanguage ::= ALTER [ PROCEDURAL ] LANGUAGE name RENAME TO new_name ALTER [ PROCEDURAL ] LANGUAGE name OWNER TO new_owner;
+```
+
+## 参数说明
+
+- **name**
+
+  语言的名字。
+
+- **new_name**
+
+  语言的新名字。
+
+- **new_owner**
+
+  语言的新的所有者。
+
+## 兼容性
+
+SQL标准里没有ALTER LANGUAGE语句。
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/90-DROP-RULE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/90-DROP-RULE.md
new file mode 100644
index 0000000000000000000000000000000000000000..5fc43416badd2ca4f251b362064f7da1953fb062
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/90-DROP-RULE.md
@@ -0,0 +1,47 @@
+---
+title: DROP RULE
+summary: DROP RULE
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP RULE
+
+## 功能描述
+
+删除一个重写规则。
+
+## 语法格式
+
+```ebnf+diagram
+DropRule ::= DROP RULE [ IF EXISTS ] name ON table_name [ CASCADE | RESTRICT ]
+```
+
+## 参数说明
+
+- **IF EXISTS**
+
+  如果该规则不存在，会抛出一个NOTICE。
+
+- **name**
+
+  要删除的现存规则名称。
+
+- **table_name**
+
+  该规则应用的表名。
+
+- **CASCADE**
+
+  自动级联删除依赖于此规则的对象。
+
+- **RESTRICT**
+
+  缺省情况下，如果有任何依赖对象，则拒绝删除此规则。
+
+## 示例
+
+```sql
+--删除重写规则newrule
+DROP RULE newrule ON mytable;
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/91-DROP-SCHEMA.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/91-DROP-SCHEMA.md
new file mode 100644
index 0000000000000000000000000000000000000000..d4ce5925bf93457e9ed4b28324c8b8367368b732
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/91-DROP-SCHEMA.md
@@ -0,0 +1,51 @@
+---
+title: DROP SCHEMA
+summary: DROP SCHEMA
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP SCHEMA
+
+## 功能描述
+
+从数据库中删除模式。
+
+## 注意事项
+
+只有模式的所有者或者被授予了模式DROP权限的用户有权限执行DROP SCHEMA命令，系统管理员默认拥有此权限。
+
+## 语法格式
+
+```ebnf+diagram
+DropSchema ::= DROP SCHEMA [ IF EXISTS ] schema_name [, ...] [ CASCADE | RESTRICT ];
+```
+
+## 参数说明
+
+- **IF EXISTS**
+
+  如果指定的模式不存在，发出一个notice而不是抛出一个错误。
+
+- **schema_name**
+
+  模式的名称。
+
+  取值范围: 已存在模式名。
+
+- **CASCADE | RESTRICT**
+
+  - CASCADE：自动删除包含在模式中的对象。
+  - RESTRICT：如果模式包含任何对象，则删除失败（缺省行为）。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 不要随意删除pg_temp或pg_toast_temp开头的模式，这些模式是系统内部使用的，如果删除，可能导致无法预知的结果。
+>
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 无法删除当前模式。如果要删除当前模式，须切换到其他模式下。
+
+## 示例
+
+请参见CREATE SCHEMA的示例。
+
+## 相关链接
+
+[ALTER SCHEMA](15-ALTER-SCHEMA)，[CREATE SCHEMA](56-CREATE-SCHEMA)。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/92-DROP-SEQUENCE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/92-DROP-SEQUENCE.md
new file mode 100644
index 0000000000000000000000000000000000000000..c8d9d1420ab36b264c41d56fe68a602322edff3f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/92-DROP-SEQUENCE.md
@@ -0,0 +1,54 @@
+---
+title: DROP SEQUENCE
+summary: DROP SEQUENCE
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP SEQUENCE
+
+## 功能描述
+
+从当前数据库里删除序列。
+
+## 注意事项
+
+只有序列的所有者或者被授予了序列DROP权限的用户才能删除，系统管理员默认拥有该权限。
+
+## 语法格式
+
+```ebnf+diagram
+DropSequence ::= DROP SEQUENCE [ IF EXISTS ] {[schema'.']sequence_name} [ , ... ] [ CASCADE | RESTRICT ];
+```
+
+## 参数说明
+
+- **IF EXISTS**
+
+  如果指定的序列不存在，则发出一个notice而不是抛出一个错误。
+
+- **name**
+
+  序列名称。
+
+- **CASCADE**
+
+  级联删除依赖序列的对象。
+
+- **RESTRICT**
+
+  如果存在任何依赖的对象，则拒绝删除序列。此项是缺省值。
+
+## 示例
+
+```sql
+--创建一个名为serial的递增序列，从101开始。
+mogdb=# CREATE SEQUENCE serial START 101;
+
+--删除序列。
+mogdb=# DROP SEQUENCE serial;
+```
+
+## 相关链接
+
+[ALTER SEQUENCE](16-ALTER-SEQUENCE)， [CREATE SEQUENCE](57-CREATE-SEQUENCE)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/93-DROP-SERVER.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/93-DROP-SERVER.md
new file mode 100644
index 0000000000000000000000000000000000000000..94cbc6e7c6234c6947fccb8ee001b9fd2dc6172a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/93-DROP-SERVER.md
@@ -0,0 +1,41 @@
+---
+title: DROP SERVER
+summary: DROP SERVER
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP SERVER
+
+## 功能描述
+
+删除现有的一个数据服务器。
+
+## 注意事项
+
+只有server的所有者或者被授予了server的DROP权限的用户才可以删除，系统管理员默认拥有该权限。
+
+## 语法格式
+
+```ebnf+diagram
+DropServer ::= DROP SERVER [ IF EXISTS ] server_name [ {CASCADE | RESTRICT} ] ;
+```
+
+## 参数描述
+
+- **IF EXISTS**
+
+  如果指定的数据服务器不存在，则发出一个notice而不是抛出一个错误。
+
+- **server_name**
+
+  服务器名称。
+
+- **CASCADE | RESTRICT**
+
+  - CASCADE：级联删除依赖于server的对象 。
+  - RESTRICT（缺省值）：如果存在依赖对象，则拒绝删除该server。
+
+## 相关链接
+
+[ALTER SERVER](17-ALTER-SERVER)，[CREATE SERVER](58-CREATE-SERVER)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/94-DROP-SYNONYM.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/94-DROP-SYNONYM.md
new file mode 100644
index 0000000000000000000000000000000000000000..3491cbd40ecc5317247ec893b4a7df3dc638706f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/94-DROP-SYNONYM.md
@@ -0,0 +1,45 @@
+---
+title: DROP SYNONYM
+summary: DROP SYNONYM
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP SYNONYM
+
+## 功能描述
+
+删除指定的SYNONYM对象。
+
+## 注意事项
+
+只有SYNONYM的所有者有权限执行DROP SYNONYM命令，系统管理员默认拥有此权限。
+
+## 语法格式
+
+```ebnf+diagram
+DropSynonym ::= DROP SYNONYM [ IF EXISTS ] synonym_name [ CASCADE | RESTRICT ];
+```
+
+## 参数描述
+
+- **IF EXISTS**
+
+  如果指定的同义词不存在，则发出一个notice而不是抛出一个错误。
+
+- **synonym_name**
+
+  同义词名字，可以带模式名。
+
+- **CASCADE | RESTRICT**
+
+  - CASCADE：级联删除依赖同义词的对象（比如视图）。
+  - RESTRICT：如果有依赖对象存在，则拒绝删除同义词。此选项为缺省值。
+
+## 示例
+
+请参考CREATE SYNONYM的示例。
+
+## 相关链接
+
+[ALTER SYNONYM](19-ALTER-SYNONYM)，[CREATE SYNONYM](59-CREATE-SYNONYM)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/95-DROP-TABLE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/95-DROP-TABLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..b509ce8e01dcbe3fb27f19e1453d2982f111cb6a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/95-DROP-TABLE.md
@@ -0,0 +1,51 @@
+---
+title: DROP TABLE
+summary: DROP TABLE
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP TABLE
+
+## 功能描述
+
+删除指定的表。
+
+## 注意事项
+
+- DROP TABLE会强制删除指定的表，删除表后，依赖该表的索引会被删除，而使用到该表的函数和存储过程将无法执行。删除分区表，会同时删除分区表中的所有分区。
+- 只有表的所有者或者被授予了表的DROP权限的用户才能执行DROP TABLE，系统管理员默认拥有该权限。
+
+## 语法格式
+
+```ebnf+diagram
+DropTable ::= DROP TABLE [ IF EXISTS ]
+    { [schema'.']table_name } [, ...] [ CASCADE | RESTRICT ];
+```
+
+## 参数说明
+
+- **IF EXISTS**
+
+  如果指定的表不存在，则发出一个notice而不是抛出一个错误。
+
+- **schema**
+
+  模式名称。
+
+- **table_name**
+
+  表名称。
+
+- **CASCADE | RESTRICT**
+
+  - CASCADE：级联删除依赖于表的对象（比如视图）。
+  - RESTRICT（缺省项）：如果存在依赖对象，则拒绝删除该表。这个是缺省。
+
+## 示例
+
+请参考CREATE TABLE的示例。
+
+## 相关链接
+
+[ALTER TABLE](22-ALTER-TABLE)，[CREATE TABLE](60-CREATE-TABLE)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/96-DROP-TABLESPACE.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/96-DROP-TABLESPACE.md
new file mode 100644
index 0000000000000000000000000000000000000000..b663eb4799dac44d7a42c59703d3ba292ab638b0
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/96-DROP-TABLESPACE.md
@@ -0,0 +1,52 @@
+---
+title: DROP TABLESPACE
+summary: DROP TABLESPACE
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP TABLESPACE
+
+## 功能描述
+
+删除一个表空间。
+
+## 注意事项
+
+- 只有表空间所有者或者被授予了表空间DROP权限的用户有权限执行DROP TABLESPACE命令，系统管理员默认拥有此权限。
+- 在删除一个表空间之前，表空间里面不能有任何数据库对象，否则会报错。
+- DROP TABLESPACE不支持回滚，因此，不能出现在事务块内部。
+- 执行DROP TABLESPACE操作时，如果有另外的会话执行\db查询操作，可能会由于tablespace事务的原因导致查询失败，请重新执行\db查询操作。
+- 如果执行DROP TABLESPACE失败，需要再次执行一次DROP TABLESPACE IF EXISTS。
+
+## 语法格式
+
+```ebnf+diagram
+DropTablespace ::= DROP TABLESPACE [ IF EXISTS ] tablespace_name;
+```
+
+## 参数说明
+
+- **IF EXISTS**
+
+  如果指定的表空间不存在，则发出一个notice而不是抛出一个错误。
+
+- **tablespace_name**
+
+  表空间的名称。
+
+  取值范围: 已存在的表空间的名称。
+
+## 示例
+
+请参见CREATE TABLESPACE的示例。
+
+## 相关链接
+
+[ALTER TABLESPACE](24-ALTER-TABLESPACE)， [CREATE TABLESPACE](63-CREATE-TABLESPACE)
+
+## 优化建议
+
+- drop database
+
+  不支持在事务中删除database。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/97-DROP-TEXT-SEARCH-CONFIGURATION.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/97-DROP-TEXT-SEARCH-CONFIGURATION.md
new file mode 100644
index 0000000000000000000000000000000000000000..ff7bf84f86694f89252fc9ee53033454d57f9069
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/97-DROP-TEXT-SEARCH-CONFIGURATION.md
@@ -0,0 +1,48 @@
+---
+title: DROP TEXT SEARCH CONFIGURATION
+summary: DROP TEXT SEARCH CONFIGURATION
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP TEXT SEARCH CONFIGURATION
+
+## 功能描述
+
+删除已有文本搜索配置。
+
+## 注意事项
+
+要执行这个命令，用户必须是该配置的所有者。
+
+## 语法格式
+
+```ebnf+diagram
+DropTextSearchConfiguration ::= DROP TEXT SEARCH CONFIGURATION [ IF EXISTS ] name [ CASCADE | RESTRICT ];
+```
+
+## 参数说明
+
+- **IF EXISTS**
+
+  如果指定的文本搜索配置不存在，那么发出一个notice而不是抛出一个错误。
+
+- **name**
+
+  要删除的文本搜索配置名称（可有模式修饰）。
+
+- **CASCADE**
+
+  级联删除依赖文本搜索配置的对象。
+
+- **RESTRICT**
+
+  若有任何对象依赖文本搜索配置则拒绝删除它。这是默认情况。
+
+## 示例
+
+请参见CREATE TEXT SEARCH CONFIGURATION的示例。
+
+## 相关链接
+
+[ALTER TEXT SEARCH CONFIGURATION](25-ALTER-TEXT-SEARCH-CONFIGURATION)， [CREATE TEXT SEARCH CONFIGURATION](64-CREATE-TEXT-SEARCH-CONFIGURATION)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/98-DROP-TEXT-SEARCH-DICTIONARY.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/98-DROP-TEXT-SEARCH-DICTIONARY.md
new file mode 100644
index 0000000000000000000000000000000000000000..2921638658dbf8264610678202c092fabaa4da07
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/98-DROP-TEXT-SEARCH-DICTIONARY.md
@@ -0,0 +1,57 @@
+---
+title: DROP TEXT SEARCH DICTIONARY
+summary: DROP TEXT SEARCH DICTIONARY
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP TEXT SEARCH DICTIONARY
+
+## 功能描述
+
+删除全文检索词典。
+
+## 注意事项
+
+- 预定义词典不支持DROP操作。
+- 只有词典的所有者可以执行DROP操作，系统管理员默认拥有此权限。
+- 谨慎执行DROP…CASCADE操作，该操作将级联删除使用该词典的文本搜索配置（TEXT SEARCH CONFIGURATION）。
+
+## 语法格式
+
+```ebnf+diagram
+DropTextSearchDictionary ::= DROP TEXT SEARCH DICTIONARY [ IF EXISTS ] name [ CASCADE | RESTRICT ]
+```
+
+## 参数说明
+
+- **IF EXISTS**
+
+  如果指定的全文检索词典不存在，那么发出一个Notice而不是报错。
+
+- **name**
+
+  要删除的词典名称（可指定模式名，否则默认在当前模式下）。
+
+  取值范围: 已存在的词典名。
+
+- **CASCADE**
+
+  自动删除依赖于该词典的对象，并依次删除依赖于这些对象的所有对象。
+
+  如果存在任何一个使用该词典的文本搜索配置，此DROP命令将不会成功。可添加CASCADE以删除引用该词典的所有文本搜索配置以及词典。
+
+- **RESTRICT**
+
+  如果任何对象依赖词典，则拒绝删除该词典。这是缺省值。
+
+## 示例
+
+```sql
+--删除词典english
+mogdb=# DROP TEXT SEARCH DICTIONARY english;
+```
+
+## 相关链接
+
+[ALTER TEXT SEARCH DICTIONARY](26-ALTER-TEXT-SEARCH-DICTIONARY)，[CREATE TEXT SEARCH DICTIONARY](65-CREATE-TEXT-SEARCH-DICTIONARY)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/99-DROP-TRIGGER.md b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/99-DROP-TRIGGER.md
new file mode 100644
index 0000000000000000000000000000000000000000..835cba2be8897335bbf5818a17545712a6c9ff18
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/sql-syntax/99-DROP-TRIGGER.md
@@ -0,0 +1,53 @@
+---
+title: DROP TRIGGER
+summary: DROP TRIGGER
+author: Zhang Cuiping
+date: 2021-05-18
+---
+
+# DROP TRIGGER
+
+## 功能描述
+
+删除触发器。
+
+## 注意事项
+
+只有触发器的所有者可以执行DROP TRIGGER操作，系统管理员默认拥有此权限。
+
+## 语法格式
+
+```ebnf+diagram
+DropTrigger ::= DROP TRIGGER [ IF EXISTS ] trigger_name ON table_name [ CASCADE | RESTRICT ];
+```
+
+## 参数说明
+
+- **IF EXISTS**
+
+  如果指定的触发器不存在，则发出一个notice而不是抛出一个错误。
+
+- **trigger_name**
+
+  要删除的触发器名称。
+
+  取值范围: 已存在的触发器。
+
+- **table_name**
+
+  要删除的触发器所在的表名称。
+
+  取值范围: 已存在的含触发器的表。
+
+- **CASCADE | RESTRICT**
+
+  - CASCADE：级联删除依赖此触发器的对象。
+  - RESTRICT：如果有依赖对象存在，则拒绝删除此触发器。此选项为缺省值。
+
+## 示例
+
+请参见CREATE TRIGGER的示例。
+
+## 相关链接
+
+[CREATE TRIGGER](66-CREATE-TRIGGER)，[ALTER TRIGGER](27-ALTER-TRIGGER)，[ALTER TABLE](22-ALTER-TABLE)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/1-numeric-data-types.md b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/1-numeric-data-types.md
new file mode 100644
index 0000000000000000000000000000000000000000..92ed639eb87003f09699196fb1e8e02028fee172
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/1-numeric-data-types.md
@@ -0,0 +1,243 @@
+---
+title: 数值类型
+summary: 数值类型
+author: Guo Huan
+date: 2021-04-06
+---
+
+# 数值类型
+
+表1列出了所有的可用类型。数字操作符和相关的内置函数请参见[数字操作函数和操作符](7-mathematical-functions-and-operators)。
+
+**表 1** 整数类型
+
+| 名称           | 描述                       | 存储空间 | 范围            |
+| :------------------- | :------------------------- | :------- | :------------------------------------------------------ |
+| TINYINT        | 微整数，别名为INT1。       | 1字节    | 0 ~ 255         |
+| SMALLINT       | 小范围整数，别名为INT2。   | 2字节    | -32,768 ~ +32,767           |
+| INTEGER        | 常用的整数，别名为INT4。   | 4字节    | -2,147,483,648 ~ +2,147,483,647                         |
+| BINARY_INTEGER | 常用的整数INTEGER的别名。  | 4字节    | -2,147,483,648 ~ +2,147,483,647                         |
+| BIGINT         | 大范围的整数，别名为INT8。 | 8字节    | -9,223,372,036,854,775,808 ~ +9,223,372,036,854,775,807 |
+| int16 | 十六字节的大范围证书，目前不支持用户用于建表等使用。 | 16字节 | -170,141,183,460,469,231,731,687,303,715,884,105,728 ~ +170,141,183,460,469,231,731,687,303,715,884,105,727 |
+
+示例:
+
+```sql
+--创建具有TINYINT类型数据的表。
+mogdb=# CREATE TABLE int_type_t1
+           (
+            IT_COL1 TINYINT
+           );
+
+--向创建的表中插入数据。
+mogdb=# INSERT INTO int_type_t1 VALUES(10);
+
+--查看数据。
+mogdb=# SELECT * FROM int_type_t1;
+ it_col1
+---------
+ 10
+(1 row)
+
+--删除表。
+mogdb=# DROP TABLE int_type_t1;
+```
+
+```sql
+--创建具有TINYINT,INTEGER,BIGINT类型数据的表。
+mogdb=# CREATE TABLE int_type_t2
+(
+    a TINYINT,
+    b TINYINT,
+    c INTEGER,
+    d BIGINT
+);
+
+--插入数据。
+mogdb=# INSERT INTO int_type_t2 VALUES(100, 10, 1000, 10000);
+
+--查看数据。
+mogdb=# SELECT * FROM int_type_t2;
+  a  | b  |  c   |   d
+-----+----+------+-------
+ 100 | 10 | 1000 | 10000
+(1 row)
+
+--删除表。
+mogdb=# DROP TABLE int_type_t2;
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+>
+> - TINYINT、SMALLINT、INTEGER、BIGINT和INT16类型存储各种范围的数字，也就是整数。试图存储超出范围以外的数值将会导致错误。
+> - 常用的类型是INTEGER，因为它提供了在范围、存储空间、性能之间的最佳平衡。一般只有取值范围确定不超过SMALLINT的情况下，才会使用SMALLINT类型。而只有在INTEGER的范围不够的时候才使用BIGINT，因为前者相对快得多。
+
+**表 2** 任意精度型
+
+| 名称               | 描述                  | 存储空间              | 范围  |
+| :------------------------------------- | :-------------------------| :------------------------|--------------------------|
+| NUMERIC[(p[,s])],<br/>DECIMAL[(p[,s])] | 精度p取值范围为[1,1000]，标度s取值范围为[0,p]。<br/>说明：<br />p为总位数，s为小数位数。 | 用户声明精度。每四位（十进制位）占用两个字节，然后在整个数据上加上八个字节的额外开销。 | 未指定精度的情况下，小数点前最大131,072位，小数点后最大16,383位。 |
+| NUMBER[(p[,s])]                        | NUMERIC类型的别名。                       | 用户声明精度。每四位（十进制位）占用两个字节，然后在整个数据上加上八个字节的额外开销。 | 未指定精度的情况下，小数点前最大131,072位，小数点后最大16,383位。 |
+
+示例:
+
+```sql
+--创建表。
+mogdb=# CREATE TABLE decimal_type_t1
+(
+    DT_COL1 DECIMAL(10,4)
+);
+
+--插入数据。
+mogdb=# INSERT INTO decimal_type_t1 VALUES(123456.122331);
+
+--查询表中的数据。
+mogdb=# SELECT * FROM decimal_type_t1;
+   dt_col1
+-------------
+ 123456.1223
+(1 row)
+
+--删除表。
+mogdb=# DROP TABLE decimal_type_t1;
+```
+
+```sql
+--创建表。
+mogdb=# CREATE TABLE numeric_type_t1
+(
+    NT_COL1 NUMERIC(10,4)
+);
+
+--插入数据。
+mogdb=# INSERT INTO numeric_type_t1 VALUES(123456.12354);
+
+--查询表中的数据。
+mogdb=# SELECT * FROM numeric_type_t1;
+   nt_col1
+-------------
+ 123456.1235
+(1 row)
+
+--删除表。
+mogdb=# DROP TABLE numeric_type_t1;
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+>
+> - 与整数类型相比，任意精度类型需要更大的存储空间，其存储效率、运算效率以及压缩比效果都要差一些。在进行数值类型定义时，优先选择整数类型。当且仅当数值超出整数可表示最大范围时，再选用任意精度类型。
+> - 使用Numeric/Decimal进行列定义时，建议指定该列的精度p以及标度s。
+
+**表 3** 序列整型
+
+| 名称        | 描述  | 存储空间 | 范围                      |
+| :------- | :----- | :----- | :--------------------------- |
+| SMALLSERIAL | 二字节序列整型。   | 2字节    | -32,768 ~ +32,767                                            |
+| SERIAL      | 四字节序列整型。   | 4字节    | -2,147,483,648 ~ +2,147,483,647                              |
+| BIGSERIAL   | 八字节序列整型。   | 8字节    | -9,223,372,036,854,775,808 ~ +9,223,372,036,854,775,807      |
+| LARGESERIAL | 十六字节序列整形。 | 16字节   | -170,141,183,460,469,231,731,687,303,715,884,105,728 ~ +170,141,183,460,469,231,731,687,303,715,884,105,727 |
+
+示例:
+
+```sql
+--创建表。
+mogdb=# CREATE TABLE smallserial_type_tab(a SMALLSERIAL);
+
+--插入数据。
+mogdb=# INSERT INTO smallserial_type_tab VALUES(default);
+
+--再次插入数据。
+mogdb=# INSERT INTO smallserial_type_tab VALUES(default);
+
+--查看数据。
+mogdb=# SELECT * FROM smallserial_type_tab;
+ a
+---
+ 1
+ 2
+(2 rows)
+
+--创建表。
+mogdb=# CREATE TABLE serial_type_tab(b SERIAL);
+
+--插入数据。
+mogdb=# INSERT INTO serial_type_tab VALUES(default);
+
+--再次插入数据。
+mogdb=# INSERT INTO serial_type_tab VALUES(default);
+
+--查看数据。
+mogdb=# SELECT * FROM serial_type_tab;
+ b
+---
+ 1
+ 2
+(2 rows)
+
+--创建表。
+mogdb=# CREATE TABLE bigserial_type_tab(c BIGSERIAL);
+
+--插入数据。
+mogdb=# INSERT INTO bigserial_type_tab VALUES(default);
+
+--插入数据。
+mogdb=# INSERT INTO bigserial_type_tab VALUES(default);
+
+--查看数据。
+mogdb=# SELECT * FROM bigserial_type_tab;
+ c
+---
+ 1
+ 2
+(2 rows)
+
+--删除表。
+mogdb=# DROP TABLE smallserial_type_tab;
+
+mogdb=# DROP TABLE serial_type_tab;
+
+mogdb=# DROP TABLE bigserial_type_tab;
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+> SMALLSERIAL，SERIAL和BIGSERIAL类型不是真正的类型，只是为在表中设置唯一标识做的概念上的便利。因此，创建一个整数字段，并且把它的缺省数值安排为从一个序列发生器读取。应用了一个NOT NULL约束以确保NULL不会被插入。在大多数情况下用户可能还希望附加一个UNIQUE或PRIMARY KEY约束避免意外地插入重复的数值，但这个不是自动的。最后，将序列发生器从属于那个字段，这样当该字段或表被删除的时候也一并删除它。目前只支持在创建表时候指定SERIAL列，不可以在已有的表中，增加SERIAL列。另外临时表也不支持创建SERIAL列。因为SERIAL不是真正的类型，也不可以将表中存在的列类型转化为SERIAL。
+
+**表 4** 浮点类型
+
+| 名称                    | 描述                 | 存储空间                  | 范围                         |
+| :---------------------- | :-----------------| :----------------------- | :---------------------- |
+| REAL,FLOAT4             | 单精度浮点数，不精准。                                       | 4字节                                                        | -3.402E+38~3.402E+38，6位十进制数字精度。                    |
+| DOUBLE PRECISION,FLOAT8 | 双精度浮点数，不精准。                                       | 8字节                                                        | -1.79E+308~1.79E+308，15位十进制数字精度。                   |
+| FLOAT[(p)]              | 浮点数，不精准。精度p取值范围为[1,53]。<br />说明：<br />p为精度，表示总位数。 | 4字节或8字节                                                 | 根据精度p不同选择REAL或DOUBLE PRECISION作为内部表示。如不指定精度，内部用DOUBLE PRECISION表示。 |
+| BINARY_DOUBLE           | 是DOUBLE PRECISION的别名。                                   | 8字节                                                        | -1.79E+308~1.79E+308，15位十进制数字精度。                   |
+| DEC[(p[,s])]            | 精度p取值范围为[1,1000]，标度s取值范围为[0,p]。<br />说明：<br />p为总位数，s为小数位位数。 | 用户声明精度。每四位（十进制位）占用两个字节，然后在整个数据上加上八个字节的额外开销。 | 未指定精度的情况下，小数点前最大131,072位，小数点后最大16,383位。 |
+| INTEGER[(p[,s])]        | 精度p取值范围为[1,1000]，标度s取值范围为[0,p]。              | 用户声明精度。每四位（十进制位）占用两个字节，然后在整个数据上加上八个字节的额外开销。 | -                                                            |
+
+示例:
+
+```sql
+--创建表。
+mogdb=# CREATE TABLE float_type_t2
+(
+    FT_COL1 INTEGER,
+    FT_COL2 FLOAT4,
+    FT_COL3 FLOAT8,
+    FT_COL4 FLOAT(3),
+    FT_COL5 BINARY_DOUBLE,
+    FT_COL6 DECIMAL(10,4),
+    FT_COL7 INTEGER(6,3)
+);
+
+--插入数据。
+mogdb=# INSERT INTO float_type_t2 VALUES(10,10.365456,123456.1234,10.3214, 321.321, 123.123654, 123.123654);
+
+--查看数据。
+mogdb=# SELECT * FROM float_type_t2 ;
+ ft_col1 | ft_col2 |   ft_col3   | ft_col4 | ft_col5 | ft_col6  | ft_col7
+---------+---------+-------------+---------+---------+----------+---------
+      10 | 10.3655 | 123456.1234 | 10.3214 | 321.321 | 123.1237 | 123.124
+(1 row)
+
+--删除表。
+mogdb=# DROP TABLE float_type_t2;
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/10-text-search-types.md b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/10-text-search-types.md
new file mode 100644
index 0000000000000000000000000000000000000000..554c74f3695853d89befc916ee946ffe8ffcdf17
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/10-text-search-types.md
@@ -0,0 +1,168 @@
+---
+title: 文本搜索类型
+summary: 文本搜索类型
+author: Guo Huan
+date: 2021-04-06
+---
+
+# 文本搜索类型
+
+MogDB提供了两种数据类型用于支持全文检索。tsvector类型表示为文本搜索优化的文件格式，tsquery类型表示文本查询。
+
+## tsvector
+
+tsvector类型表示一个检索单元，通常是一个数据库表中一行的文本字段或者这些字段的组合，tsvector类型的值是一个标准词位的有序列表，标准词位就是把同一个词的变型体都标准化成相同的，在输入的同时会自动排序和消除重复。to_tsvector函数通常用于解析和标准化文档字符串。
+
+tsvector的值是唯一分词的分类列表，把一句话的词格式化为不同的词条，在进行分词处理的时候tsvector会自动去掉分词中重复的词条，按照一定的顺序录入。如:
+
+```sql
+mogdb=# SELECT 'a fat cat sat on a mat and ate a fat rat'::tsvector;
+                      tsvector
+----------------------------------------------------
+ 'a' 'and' 'ate' 'cat' 'fat' 'mat' 'on' 'rat' 'sat'
+(1 row)
+```
+
+从上面的例子可以看出，通过tsvector把一个字符串按照空格进行分词，分词的顺序是按照长短和字母排序的。但是如果词条中需要包含空格或标点符号，可以用引号标记:
+
+```sql
+mogdb=# SELECT $$the lexeme '    ' contains spaces$$::tsvector;
+                 tsvector
+-------------------------------------------
+ '    ' 'contains' 'lexeme' 'spaces' 'the'
+(1 row)
+```
+
+如果在词条中使用引号，可以使用双$$符号作为标记:
+
+```sql
+mogdb=# SELECT $$the lexeme 'Joe''s' contains a quote$$::tsvector;
+                    tsvector
+------------------------------------------------
+ 'Joe''s' 'a' 'contains' 'lexeme' 'quote' 'the'
+(1 row)
+```
+
+词条位置常量也可以放到词汇中:
+
+```sql
+mogdb=# SELECT 'a:1 fat:2 cat:3 sat:4 on:5 a:6 mat:7 and:8 ate:9 a:10 fat:11 rat:12'::tsvector;
+                                   tsvector
+-------------------------------------------------------------------------------
+ 'a':1,6,10 'and':8 'ate':9 'cat':3 'fat':2,11 'mat':7 'on':5 'rat':12 'sat':4
+(1 row)
+```
+
+位置常量通常表示文档中源字的位置。位置信息可以用于进行排名。位置常量的范围是1到16383，最大值默认是16383。相同词的重复位会被忽略掉。
+
+拥有位置的词汇甚至可以用一个权来标记，这个权可以是A，B，C或D。默认的是D，因此输出中不会出现:
+
+```sql
+mogdb=# SELECT 'a:1A fat:2B,4C cat:5D'::tsvector;
+          tsvector
+----------------------------
+ 'a':1A 'cat':5 'fat':2B,4C
+(1 row)
+```
+
+权可以用来反映文档结构，如: 标记标题与主体文字的区别。全文检索排序函数可以为不同的权标记分配不同的优先级。
+
+下面的示例是tsvector类型标准用法。如:
+
+```sql
+mogdb=# SELECT 'The Fat Rats'::tsvector;
+      tsvector
+--------------------
+ 'Fat' 'Rats' 'The'
+(1 row)
+```
+
+但是对于英文全文检索应用来说，上面的单词会被认为非规范化的，所以需要通过to_tsvector函数对这些单词进行规范化处理:
+
+```sql
+mogdb=# SELECT to_tsvector('english', 'The Fat Rats');
+   to_tsvector
+-----------------
+ 'fat':2 'rat':3
+(1 row)
+```
+
+## tsquery
+
+tsquery类型表示一个检索条件，存储用于检索的词汇，并且使用布尔操作符&（AND），|（OR）和!（NOT）来组合他们，括号用来强调操作符的分组。to_tsquery函数及plainto_tsquery函数会将单词转换为tsquery类型前进行规范化处理。
+
+```sql
+mogdb=# SELECT 'fat & rat'::tsquery;
+    tsquery
+---------------
+ 'fat' & 'rat'
+(1 row)
+
+mogdb=# SELECT 'fat & (rat | cat)'::tsquery;
+          tsquery
+---------------------------
+ 'fat' & ( 'rat' | 'cat' )
+(1 row)
+
+mogdb=# SELECT 'fat & rat & ! cat'::tsquery;
+        tsquery
+------------------------
+ 'fat' & 'rat' & !'cat'
+(1 row)
+```
+
+在没有括号的情况下，!（非）结合的最紧密，而&（和）结合的比|（或）紧密。
+
+tsquery中的词汇可以用一个或多个权字母来标记，这些权字母限制这次词汇只能与带有匹配权的tsvector词汇进行匹配。
+
+```sql
+mogdb=# SELECT 'fat:ab & cat'::tsquery;
+     tsquery
+------------------
+ 'fat':AB & 'cat'
+(1 row)
+```
+
+同样，tsquery中的词汇可以用*标记来指定前缀匹配:
+
+```sql
+mogdb=# SELECT 'super:*'::tsquery;
+  tsquery
+-----------
+ 'super':*
+(1 row)
+```
+
+这个查询可以匹配tsvector中以"super"开始的任意单词。
+
+请注意，前缀首先被文本搜索分词器处理，这也就意味着下面的结果为真:
+
+```sql
+mogdb=# SELECT to_tsvector( 'postgraduate' ) @@ to_tsquery( 'postgres:*' ) AS RESULT;
+  result
+----------
+ t
+(1 row)
+```
+
+因为postgres经过处理后得到postgr:
+
+```sql
+mogdb=# SELECT to_tsquery('postgres:*');
+ to_tsquery
+------------
+ 'postgr':*
+(1 row)
+```
+
+这样就匹配postgraduate了。
+
+'Fat:ab & Cats'规范化转为tsquery类型结果如下:
+
+```sql
+mogdb=# SELECT to_tsquery('Fat:ab & Cats');
+    to_tsquery
+------------------
+ 'fat':AB & 'cat'
+(1 row)
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/11-uuid-type.md b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/11-uuid-type.md
new file mode 100644
index 0000000000000000000000000000000000000000..0d8700e9ca989674c423480d8b57710fc9667900
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/11-uuid-type.md
@@ -0,0 +1,27 @@
+---
+title: UUID类型
+summary: UUID类型
+author: Guo Huan
+date: 2021-04-06
+---
+
+# UUID类型
+
+UUID数据类型用来存储RFC 4122，ISO/IEF 9834-8:2005以及相关标准定义的通用唯一标识符（UUID）。这个标识符是一个由算法产生的128位标识符，确保它不可能使用相同算法在已知的模块中产生的相同标识符。
+
+UUID是一个小写十六进制数字的序列，由分字符分成几组，一组8位数字+三组4位数字+一组12位数字，总共32个数字代表128位，标准的UUID示例如下:
+
+```sql
+a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11
+```
+
+MogDB同样支持以其他方式输入: 大写字母和数字、由花括号包围的标准格式、省略部分或所有连字符、在任意一组四位数字之后加一个连字符。示例:
+
+```sql
+A0EEBC99-9C0B-4EF8-BB6D-6BB9BD380A11
+{a0eebc99-9c0b-4ef8-bb6d-6bb9bd380a11}
+a0eebc999c0b4ef8bb6d6bb9bd380a11
+a0ee-bc99-9c0b-4ef8-bb6d-6bb9-bd38-0a11
+```
+
+一般是以标准格式输出。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/12-json-types.md b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/12-json-types.md
new file mode 100644
index 0000000000000000000000000000000000000000..d0ad3a30f6a24600419578574ba32bd545d3fced
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/12-json-types.md
@@ -0,0 +1,146 @@
+---
+title: JSON/JSONB类型
+summary: JSON/JSONB类型
+author: Guo Huan
+date: 2021-04-06
+---
+
+# JSON/JSONB类型
+
+JSON（JavaScript Object Notation）数据，可以是单独的一个标量，也可以是一个数组，也可以是一个键值对象，其中数组和对象可以统称容器（container）：
+
+- 标量（scalar）：单一的数字、bool、string、null都可以叫做标量。
+- 数组（array）：[]结构，里面存放的元素可以是任意类型的JSON，并且不要求数组内所有元素都是同一类型。
+- 对象（object）：{}结构，存储key:value的键值对，其键只能是用“”包裹起来的字符串，值可以是任意类型的JSON，对于重复的键，按最后一个键值对为准。
+
+MogDB内存在两种数据类型JSON和JSONB，可以用来存储JSON数据。其中JSON是对输入的字符串的完整拷贝，使用时再去解析，所以它会保留输入的空格，重复键以及顺序等；JSONB解析输入后保存的二进制，它在解析时会删除语义无关的细节和重复的键，对键值也会进行排序，使用时不用再次解析。
+
+因此可以发现，两者其实都是JSON，它们接受相同的字符串作为输入。它们实际的主要差别是效率。JSON数据类型存储输入文本的精确拷贝，处理函数必须在每个执行上重新解析； 而JSONB数据以分解的二进制格式存储，这使得它由于添加了转换机制而在输入上稍微慢些，但是在处理上明显更快，因为不需要重新解析。同时由于JSONB类型存在解析后的格式归一化等操作，同等的语义下只会有一种格式，因此可以更好更强大的支持很多其他额外的操作，比如按照一定的规则进行大小比较等。JSONB也支持索引，这也是一个明显的优势。
+
+## 输入格式
+
+输入必须是一个符合JSON数据格式的字符串，此字符串用单引号”声明。
+
+null（null-json）：仅null，全小写。
+
+```
+select 'null'::json;   -- sucselect 'NULL'::jsonb;  -- err
+```
+
+数字（num-json）：正负整数、小数、0，支持科学计数法。
+
+```
+select '1'::json;select '-1.5'::json;select '-1.5e-5'::jsonb, '-1.5e+2'::jsonb;select '001'::json, '+15'::json, 'NaN'::json;
+-- 不支持多余的前导0，正数的+号，以及NaN和infinity。
+```
+
+布尔（bool-json）：仅true、false，全小写。
+
+```
+select 'true'::json;select 'false'::jsonb;
+```
+
+字符串（str-json）：必须是加双引号的字符串。
+
+```
+select '"a"'::json;select '"abc"'::jsonb;
+```
+
+数组（array-json）：使用中括号[]包裹，满足数组书写条件。数组内元素类型可以是任意合法的JSON，且不要求类型一致。
+
+```
+select '[1, 2, "foo", null]'::json;select '[]'::json;select '[1, 2, "foo", null, [[]], {}]'::jsonb;
+```
+
+对象（object-json）：使用大括号{}包裹，键必须是满足JSON字符串规则的字符串，值可以是任意合法的JSON。
+
+```
+select '{}'::json;select '{"a": 1, "b": {"a": 2,  "b": null}}'::json;select '{"foo": [true, "bar"], "tags": {"a": 1, "b": null}}'::jsonb;
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **注意：**
+>
+> - 区分 'null'::json 和 null::json 是两个不同的概念，类似于字符串 str=“” 和 str=null。
+> - 对于数字，当使用科学计数法的时候，jsonb类型会将其展开，而json会精准拷贝输入。
+
+## JSONB高级特性
+
+- 注意事项
+  - 不支持列存。
+  - 不支持作为分区键。
+  - 不支持外表、mot。
+
+JSON和JSONB的主要差异在于存储方式上的不同，JSONB存储的是解析后的二进制，能够体现JSON的层次结构，更方便直接访问等，因此JSONB会有很多JSON所不具有的高级特性。
+
+- 格式归一化
+
+  - 对于输入的object-json字符串，解析成jsonb二进制后，会天然的丢弃语义上无关紧要的细节，比如空格：
+
+    ```
+    mogdb=# select '   [1, " a ", {"a"   :1    }]  '::jsonb;        jsonb
+    ----------------------
+    [1, " a ", {"a": 1}](1 row)
+    ```
+
+  - 对于object-json，会删除重复的键值，只保留最后一个出现的，如：
+
+    ```
+    mogdb=# select '{"a" : 1, "a" : 2}'::jsonb;  jsonb---------- {"a": 2}(1 row)
+    ```
+
+  - 对于object-json，键值会重新进行排序，排序规则：长度长的在后、长度相等则ascii码大的在后，如：
+
+    ```
+    mogdb=# select '{"aa" : 1, "b" : 2, "a" : 3}'::jsonb;           jsonb
+    ---------------------------
+    {"a": 3, "b": 2, "aa": 1}(1 row)
+    ```
+
+- 大小比较
+
+  由于经过了格式归一化，保证了同一种语义下的jsonb只会有一种存在形式，因此按照制定的规则，可以比较大小。
+
+  - 首先比较类型：object-jsonb &gt; array-jsonb &gt; bool-jsonb &gt; num-jsonb &gt; str-jsonb &gt; null-jsonb
+
+  - 同类型则比较内容：
+
+    - str-json类型：依据text比较的方法，使用数据库默认排序规则进行比较，返回值正数代表大于，负数代表小于，0表示相等。
+    - num-json类型：数值比较
+    - bool-json类型：true &gt; false
+    - array-jsonb类型：长度长的 &gt; 长度短的，长度相等则依次比较每个元素。
+    - object-jsonb类型：长度长的 &gt; 长度短的，长度相等则依次比较每个键值对，先比较键，在比较值。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **注意：**
+    >
+    > object-jsonb类型内比较时，比较时使用的是格式整理后的最终结果进行比较，因此相对于我们直接的输入未必会很直观。
+
+- 创建索引、主外键
+
+  - BTREE索引
+
+    jsonb类型支持创建btree索引，支持创建主键、外键。
+
+  - GIN索引
+
+    GIN索引可以用来有效的搜索出现在大量jsonb文档（datums）中的键或者键/值对。提供了两个GIN操作符类（jsonb_ops、jsonb_hash_ops），提供了不同的性能和灵活性取舍。缺省的GIN操作符类支持使用@&gt;、&lt;@、?、 ?&和?|操作符查询，非缺省的GIN操作符类jsonb_path_ops只支持索引@&gt;、&lt;@操作符。
+
+    相关的操作符请参见[JSON/JSONB函数和操作符](13-json-functions)。
+
+- 包含存在
+
+  查询一个JSON之中是否包含某些元素，或者某些元素是否存在于某个JSON中是jsonb的一个重要能力。
+
+  ```
+  -- 简单的标量/原始值只包含相同的值：SELECT '"foo"'::jsonb @> '"foo"'::jsonb;
+  -- 左侧数组包含了右侧字符串：SELECT '[1, “aa”, 3]'::jsonb ? 'aa';
+  -- 左侧数组包含了右侧的数组所有元素，顺序、重复不重要：SELECT '[1, 2, 3]'::jsonb @> '[1, 3, 1]'::jsonb;
+  -- 左侧object-json包含了右侧object-json的所有键值对：SELECT '{"product": "PostgreSQL", "version": 9.4, "jsonb":true}'::jsonb @> '{"version":9.4}'::jsonb;
+  -- 左侧数组并没有包含右侧的数组所有元素，因为左侧数组的三个元素为1、2、[1,3]，右侧的为1、3：SELECT '[1, 2, [1, 3]]'::jsonb @> '[1, 3]'::jsonb;
+  -- 产生假-- 相似的，这样也不对：SELECT '{"foo": {"bar": "baz"}}'::jsonb @> '{"bar": "baz"}'::jsonb; -- false
+  ```
+
+  相关的操作符请参见[JSON/JSONB函数和操作符](13-json-functions)。
+
+- 函数和操作符
+
+  json/jsonb类型相关支持的函数和操作符请参见[JSON/JSONB函数和操作符](13-json-functions)。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/13-HLL.md b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/13-HLL.md
new file mode 100644
index 0000000000000000000000000000000000000000..1878adb1b7e9841ae6c1ced617ba561337eb361f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/13-HLL.md
@@ -0,0 +1,210 @@
+---
+title: HLL数据类型
+summary: HLL数据类型
+author: Guo Huan
+date: 2021-04-06
+---
+
+# HLL数据类型
+
+HLL（HyperLoglog）是统计数据集中唯一值个数的高效近似算法。它有着计算速度快，节省空间的特点，不需要直接存储集合本身，而是存储一种名为HLL的数据结构。每当有新数据加入进行统计时，只需要把数据经过哈希计算并插入到HLL中，最后根据HLL就可以得到结果。
+
+HLL与其他算法的比较请参见[表1](#biao11)。
+
+**表 1** HLL与其他算法比较 <a id="biao11"> </a>
+
+| 项目         | Sort算法     | Hash算法     | HLL                |
+| :----------- | :----------- | :----------- | :----------------- |
+| 时间复杂度   | O(nlogn)     | O(n)         | O(n)               |
+| 空间复杂度   | O(n)         | O(n)         | log(logn)          |
+| 误差率       | 0            | 0            | ≈0.8%              |
+| 所需存储空间 | 原始数据大小 | 原始数据大小 | 默认规格下最大16KB |
+
+HLL在计算速度和所占存储空间上都占优势。在时间复杂度上，Sort算法需要排序至少O(nlogn)的时间，虽说Hash算法和HLL一样扫描一次全表O(n)的时间就可以得出结果，但是存储空间上，Sort算法和Hash算法都需要先把原始数据存起来再进行统计，会导致存储空间消耗巨大，而对HLL来说不需要存原始数据，只需要维护HLL数据结构，故占用空间有很大的压缩，默认规格下HLL数据结构的最大空间约为16KB。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+>
+> - 当前默认规格下可计算最大distinct值的数量约为1.1e+15个，误差率为0.8%。用户应注意如果计算结果超过当前规格下distinct最大值会导致计算结果误差率变大，或导致计算结果失败并报错。
+> - 用户在首次使用该特性时，应该对业务的distinct value做评估，选取适当的配置参数并做验证，以确保精度符合要求：
+>   - 当前默认参数下，可以计算的distinct值为1.1e+15，如果计算得到的distinct值为NaN，需要调整log2m，或者采用其他算法计算distinct值。
+>   - 虽然hash算法存在极低的hash collision概率，但是建议用户在首次使用时，选取2-3个hash seed验证，如果得到的distinct value相差不大，则可以从该组seed中任选一个作为hash seed。
+
+HLL中主要的数据结构，请参见[表2](#hyper)。
+
+**表 2** HyperLogLog中主要数据结构<a id="hyper">  </a>
+
+| 数据类型 | 功能描述                                                     |
+| :------- | :----------------------------------------------------------- |
+| hll      | hll头部为27字节长度字段，默认规格下数据段长度0~16KB，可直接计算得到distinct值。 |
+
+创建HLL数据类型时，可以支持0~4个参数入参，具体的参数含义与参数规格同函数hll_empty一致。第一个参数为log2m，表示分桶数的对数值，取值范围10~16；第二个参数为log2explicit，表示Explicit模式的阈值大小，取值范围0~12；第三个参数为log2sparse，表示Sparse模式的阈值大小，取值范围0~14；第四个参数为duplicatecheck，表示是否启用duplicatecheck，取值范围为0~1。当入参输入值为-1时，会采用默认值设定HLL的参数。可以通过\d或\d+查看HLL类型的参数。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> 创建HLL数据类型时，根据入参的行为不同，结果不同：
+>
+> - 创建HLL类型时对应入参不输入或输入-1，采用默认值设定对应的HLL参数。
+> - 输入合法范围的入参，对应HLL参数采用输入值。
+> - 输入不合法范围的入参，创建HLL类型报错。
+
+```
+-- 创建hll类型的表，不指定入参
+mogdb=# create table t1 (id integer, set hll);
+mogdb=# \d t1
+      Table "public.t1"
+ Column |  Type   | Modifiers
+--------+---------+-----------
+ c1     | integer |
+ c2     | hll     |
+
+-- 创建hll类型的表，指定前两个入参，后两个采用默认值
+mogdb=# create table t2 (id integer, set hll(12,4));
+          Table "public.t2"
+ Column |      Type      | Modifiers
+--------+----------------+-----------
+ c1     | integer        |
+ c2     | hll(12,4,12,0) |
+
+--创建hll类型的表，指定第三个入参，其余采用默认值
+mogdb=# create table t3(id int, set hll(-1,-1,8,-1));
+mogdb=# \d t3
+          Table "public.t3"
+ Column |      Type      | Modifiers
+--------+----------------+-----------
+ c1     | integer        |
+ c2     | hll(14,10,8,0) |
+
+--创建hll类型的表，指定入参不合法报错
+mogdb=# create table t4(id int, set hll(5,-1));
+ERROR:  log2m = 5 is out of range, it should be in range 10 to 16, or set -1 as default
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> 对含有HLL类型的表插入HLL对象时，HLL类型的设定参数须同插入对象的设定参数一致，否则报错。
+
+```
+-- 创建带有hll类型的表
+mogdb=# create table t1(id integer, set hll(14));
+
+-- 向表中插入hll对象,参数一致，成功
+mogdb=# insert into t1 values (1, hll_empty(14,-1));
+
+-- 向表中插入hll对象，参数不一致，失败
+mogdb=# insert into t1(id, set) values (1, hll_empty(14,5));
+ERROR:  log2explicit does not match: source is 5 and dest is 10
+```
+
+HLL的应用场景。
+
+- 场景1：“Hello World”
+
+  通过下面的示例说明如何使用hll数据类型：
+
+  ```
+  -- 创建带有hll类型的表
+  mogdb=# create table helloworld (id integer, set hll);
+
+  -- 向表中插入空的hll
+  mogdb=# insert into helloworld(id, set) values (1, hll_empty());
+
+  -- 把整数经过哈希计算加入到hll中
+  mogdb=# update helloworld set set = hll_add(set, hll_hash_integer(12345)) where id = 1;
+
+  -- 把字符串经过哈希计算加入到hll中
+  mogdb=# update helloworld set set = hll_add(set, hll_hash_text('hello world')) where id = 1;
+
+  -- 得到hll中的distinct值
+  mogdb=# select hll_cardinality(set) from helloworld where id = 1;
+   hll_cardinality
+  -----------------
+                 2
+  (1 row)
+
+  -- 删除表
+  mogdb=#  drop table helloworld;
+  ```
+
+- 场景2：“网站访客数量统计”
+
+  通过下面的示例说明hll如何统计在一段时间内访问网站的不同用户数量：
+
+  ```
+  -- 创建原始数据表，表示某个用户在某个时间访问过网站。
+  mogdb=# create table facts (
+           date            date,
+           user_id         integer
+  );
+
+  -- 构造数据，表示一天中有哪些用户访问过网站。
+  mogdb=# insert into facts values ('2019-02-20', generate_series(1,100));
+  mogdb=# insert into facts values ('2019-02-21', generate_series(1,200));
+  mogdb=# insert into facts values ('2019-02-22', generate_series(1,300));
+  mogdb=# insert into facts values ('2019-02-23', generate_series(1,400));
+  mogdb=# insert into facts values ('2019-02-24', generate_series(1,500));
+  mogdb=# insert into facts values ('2019-02-25', generate_series(1,600));
+  mogdb=# insert into facts values ('2019-02-26', generate_series(1,700));
+  mogdb=# insert into facts values ('2019-02-27', generate_series(1,800));
+
+  -- 创建表并指定列为hll。
+  mogdb=# create table daily_uniques (
+      date            date UNIQUE,
+      users           hll
+  );
+
+  -- 根据日期把数据分组，并把数据插入到hll中。
+  mogdb=# insert into daily_uniques(date, users)
+      select date, hll_add_agg(hll_hash_integer(user_id))
+      from facts
+      group by 1;
+
+  -- 计算每一天访问网站不同用户数量
+  mogdb=# select date, hll_cardinality(users) from daily_uniques order by date;
+      date    | hll_cardinality
+  ------------+------------------
+   2019-02-20 |              100
+   2019-02-21 | 200.217913059312
+   2019-02-22 |  301.76494508014
+   2019-02-23 | 400.862858326446
+   2019-02-24 | 502.626933349694
+   2019-02-25 | 601.922606454213
+   2019-02-26 | 696.602316769498
+   2019-02-27 | 798.111731634412
+  (8 rows)
+
+  -- 计算在2019.02.20到2019.02.26一周中有多少不同用户访问过网站
+  mogdb=# select hll_cardinality(hll_union_agg(users)) from daily_uniques where date >= '2019-02-20'::date and date <= '2019-02-26'::date;
+   hll_cardinality
+  ------------------
+   702.941844662509
+  (1 row)
+
+  -- 计算昨天访问过网站而今天没访问网站的用户数量。
+  mogdb=# SELECT date, (#hll_union_agg(users) OVER two_days) - #users AS lost_uniques FROM daily_uniques WINDOW two_days AS (ORDER BY date ASC ROWS 1 PRECEDING);
+      date    | lost_uniques
+  ------------+--------------
+   2019-02-20 |            0
+   2019-02-21 |            0
+   2019-02-22 |            0
+   2019-02-23 |            0
+   2019-02-24 |            0
+   2019-02-25 |            0
+   2019-02-26 |            0
+   2019-02-27 |            0
+  (8 rows)
+
+  -- 删除表
+  mogdb=# drop table facts;
+  mogdb=# drop table daily_uniques;
+  ```
+
+- 场景3：“插入数据不满足hll数据结构要求”
+
+  当用户给hll类型的字段插入数据的时候，必须保证插入的数据满足hll数据结构要求，如果解析后不满足就会报错。如下示例中： 插入数据'E\\1234'时，该数据不满足hll数据结构，不能解析成功因此失败报错。
+
+  ```
+  mogdb=# create table test(id integer, set hll);
+  mogdb=# insert into test values(1, 'E\\1234');
+  ERROR:  not a hll type, size=6 is not enough
+  mogdb=# drop table test;
+  ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/13.0-array-types.md b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/13.0-array-types.md
new file mode 100644
index 0000000000000000000000000000000000000000..3298be6d45ae10d335e11c766701e4e51579cb0f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/13.0-array-types.md
@@ -0,0 +1,477 @@
+---
+title: 数组类型
+summary: 数组类型
+author: Guo Huan
+date: 2021-11-19
+---
+
+# 数组类型
+
+MogDB允许一个表中的列定义为变长多维数组。可以创建任何内建或用户定义的基类、枚举类型或组合类型的数组。 域的数组目前还不支持。
+
+## 数组类型的定义
+
+为了展示数组类型的使用，我们创建这样一个表：
+
+```sql
+CREATE TABLE sal_emp (
+    name            text,
+    pay_by_quarter  integer[],
+    schedule        text[][]
+);
+```
+
+如上所示，一个数组数据类型可以通过在数组元素的数据类型名称后面加上方括号（`[]`）来命名。上述命令将创建一个名为`sal_emp`的表，它有一个类型为`text`的列（`name`），一个表示雇员的季度工资的一维`integer`类型数组（`pay_by_quarter`），以及一个表示雇员每周日程表的二维`text`类型数组（`schedule`）。
+
+`CREATE TABLE`的语法允许指定数组的确切大小，例如：
+
+```sql
+CREATE TABLE tictactoe (
+    squares   integer[3][3]
+);
+```
+
+然而，当前的实现忽略任何提供的数组尺寸限制，即其行为与未指定长度的数组相同。
+
+当前的实现也不会强制所声明的维度数。一个特定元素类型的数组全部被当作是相同的类型，而不论其尺寸或维度数。因此，在`CREATE TABLE`中声明数组的尺寸或维度数仅仅只是文档而已，它并不影响运行时的行为。
+
+另一种符合SQL标准的语法是使用关键词`ARRAY`，可以用来定义一维数组。`pay_by_quarter`可以这样定义：
+
+```sql
+pay_by_quarter  integer ARRAY[4],
+```
+
+或者，不指定数组尺寸：
+
+```sql
+pay_by_quarter  integer ARRAY,
+```
+
+但是和前面一样，MogDB在任何情况下都不会强制尺寸限制。
+
+## 数组值输入
+
+要把一个数组值写成一个文字常数，将元素值用花括号包围并用逗号分隔（如果你懂C，这和初始化结构的C语法没什么两样）。在任意元素值周围可以使用双引号，并且在元素值包含逗号或花括号时必须这样做（更多细节如下所示）。因此，一个数组常量的一般格式如下：
+
+```sql
+'{ val1 delim val2 delim ... }'
+```
+
+这里`*delim*`是类型的定界符，记录在类型的`pg_type`项中。在MogDB发行提供的标准数据类型中，所有的都使用一个逗号（`,`），除了类型`box`使用一个分号（`;`）。每个`*val*`可以是数组元素类型的一个常量，也可以是一个子数组。一个数组常量的例子是：
+
+```sql
+'{{1,2,3},{4,5,6},{7,8,9}}'
+```
+
+该常量是一个二维的，3乘3数组，它由3个整数子数组构成。
+
+要设置一个数组常量的一个元素为NULL，在该元素值处写`NULL`（任何`NULL`的大写或小写变体都有效）。如果你需要一个真正的字符串值"NULL"，你必须在它两边放上双引号。
+
+常数最初被当做一个字符串，然后被传给数组的输入转换例程。有必要时可能需要一个显式的类型指定。
+
+现在我们可以展示一些`INSERT`语句：
+
+```sql
+INSERT INTO sal_emp
+    VALUES ('Bill',
+    '{10000, 10000, 10000, 10000}',
+    '{{"meeting", "lunch"}, {"training", "presentation"}}');
+
+INSERT INTO sal_emp
+    VALUES ('Carol',
+    '{20000, 25000, 25000, 25000}',
+    '{{"breakfast", "consulting"}, {"meeting", "lunch"}}');
+```
+
+前两个插入的结果看起来像这样：
+
+```sql
+SELECT * FROM sal_emp;
+ name  |      pay_by_quarter       |                 schedule
+-------+---------------------------+-------------------------------------------
+ Bill  | {10000,10000,10000,10000} | {{meeting,lunch},{training,presentation}}
+ Carol | {20000,25000,25000,25000} | {{breakfast,consulting},{meeting,lunch}}
+(2 rows)
+```
+
+多维数组的每一维都必须有相匹配的长度。不匹配会造成错误，例如：
+
+```sql
+INSERT INTO sal_emp
+    VALUES ('Bill',
+    '{10000, 10000, 10000, 10000}',
+    '{{"meeting", "lunch"}, {"meeting"}}');
+ERROR:  multidimensional arrays must have array expressions with matching dimensions
+```
+
+`ARRAY`构造器语法也可以被用于：
+
+```sql
+INSERT INTO sal_emp
+    VALUES ('Bill',
+    ARRAY[10000, 10000, 10000, 10000],
+    ARRAY[['meeting', 'lunch'], ['training', 'presentation']]);
+
+INSERT INTO sal_emp
+    VALUES ('Carol',
+    ARRAY[20000, 25000, 25000, 25000],
+    ARRAY[['breakfast', 'consulting'], ['meeting', 'lunch']]);
+```
+
+注意数组元素是普通SQL常数或表达式，例如，字符串文字使用单引号而不是双引号包围，因为双引号可以出现在一个数组文字中。
+
+## 访问数组
+
+现在，我们可以在该表上运行一些查询。首先，我们展示如何访问一个数组中的一个元素。下面的查询检索在第二季度工资发生变化的雇员的名字：
+
+```sql
+SELECT name FROM sal_emp WHERE pay_by_quarter[1] <> pay_by_quarter[2];
+
+ name
+-------
+ Carol
+(1 row)
+```
+
+数组下标写在方括号内。默认情况下，MogDB为数组使用了一种从1开始的编号习惯，即一个具有`n`个元素的数组从`array[1]`开始，结束于`array[n]`。
+
+下面的查询检索所有员工第三季度的工资：
+
+```sql
+SELECT pay_by_quarter[3] FROM sal_emp;
+
+ pay_by_quarter
+----------------
+          10000
+          25000
+(2 rows)
+```
+
+我们也可以访问一个数组的任意矩形切片或者子数组。一个数组切片可以通过在一个或多个数组维度上指定`*下界*:*上界*`来定义例如，下面的查询检索Bill在本周头两天日程中的第一项：
+
+```sql
+SELECT schedule[1:2][1:1] FROM sal_emp WHERE name = 'Bill';
+
+        schedule
+------------------------
+ {{meeting},{training}}
+(1 row)
+```
+
+如果任何维度被写成一个切片，即包含一个冒号，那么所有的维度都被看成是切片对待。其中任何只有一个数字（无冒号）的维度被视作是从1到指定的数字。例如，下面例子中的`[2]`被认为是`[1:2]`：
+
+```sql
+SELECT schedule[1:2][2] FROM sal_emp WHERE name = 'Bill';
+
+                 schedule
+-------------------------------------------
+ {{meeting,lunch},{training,presentation}}
+(1 row)
+```
+
+为了避免和非切片情况搞混，最好在所有的维度上都使用切片语法，例如`[1:2][1:1]`而不是`[2][1:1]`。
+
+可以省略一个切片说明符的`*lower-bound*`或者 `*upper-bound*`（亦可两者都省略），缺失的 边界会被数组下标的上下限所替代。例如：
+
+```sql
+SELECT schedule[:2][2:] FROM sal_emp WHERE name = 'Bill';
+
+        schedule
+------------------------
+ {{lunch},{presentation}}
+(1 row)
+
+SELECT schedule[:][1:1] FROM sal_emp WHERE name = 'Bill';
+
+        schedule
+------------------------
+ {{meeting},{training}}
+(1 row)
+```
+
+如果数组本身为空或者任何一个下标表达式为空，访问数组下标表达式将会返回空值。如果下标超过了数组边界，下标表达式也会返回空值（这种情况不会抛出错误）。例如，如果`schedule`目前具有的维度是`[1:3][1:2]`，那么引用`schedule[3][3]`将得到NULL。相似地，使用错误的下标号引用一个数组会得到空值而不是错误。
+
+如果数组本身或者任何一个下标表达式为空，则一个数组切片表达式也会得到空值。但是，在其他情况例如选择一个完全位于当前数组边界之外的切片时，一个切片表达式会得到一个空（零维）数组而不是空值（由于历史原因，这并不符合非切片行为）。 如果所请求的切片和数组边界重叠，那么它会被缩减为重叠的区域而不是返回空。
+
+任何数组值的当前维度可以使用`array_dims`函数获得：
+
+```sql
+SELECT array_dims(schedule) FROM sal_emp WHERE name = 'Carol';
+
+ array_dims
+------------
+ [1:2][1:2]
+(1 row)
+```
+
+`array_dims`产生一个`text`结果，它便于人类阅读但是不便于程序读取。 Dimensions can also be retrieved with 也可以通过`array_upper`和`array_lower`来获得维度，它们将分别返回一个指定数组的上界和下界：
+
+```sql
+SELECT array_upper(schedule, 1) FROM sal_emp WHERE name = 'Carol';
+
+ array_upper
+-------------
+           2
+(1 row)
+```
+
+`array_length`将返回一个指定数组维度的长度：
+
+```sql
+SELECT array_length(schedule, 1) FROM sal_emp WHERE name = 'Carol';
+
+ array_length
+--------------
+            2
+(1 row)
+```
+
+`cardinality`返回一个数组中在所有维度上的元素总数。 这实际上是调用`unnest`将会得到的行数：
+
+```sql
+SELECT cardinality(schedule) FROM sal_emp WHERE name = 'Carol';
+
+ cardinality
+-------------
+           4
+(1 row)
+```
+
+## 修改数组
+
+一个数组值可以被整个替换：
+
+```sql
+UPDATE sal_emp SET pay_by_quarter = '{25000,25000,27000,27000}'
+    WHERE name = 'Carol';
+```
+
+或者使用`ARRAY`表达式语法：
+
+```sql
+UPDATE sal_emp SET pay_by_quarter = ARRAY[25000,25000,27000,27000]
+    WHERE name = 'Carol';
+```
+
+一个数组也可以在一个元素上被更新：
+
+```sql
+UPDATE sal_emp SET pay_by_quarter[4] = 15000
+    WHERE name = 'Bill';
+```
+
+或者在一个切片上被更新：
+
+```sql
+UPDATE sal_emp SET pay_by_quarter[1:2] = '{27000,27000}'
+    WHERE name = 'Carol';
+```
+
+也可以使用省略`*lower-bound*`或者 `*upper-bound*`的切片语法，但是只能用于 更新一个不是 NULL 或者零维的数组值（否则无法替换现有的下标界线）。
+
+一个已存储的数组值可以被通过为其还不存在的元素赋值来扩大之。任何位于之前已存在的元素和新元素之间的位置都将被空值填充。例如，如果数组`myarray`目前有4个元素，在用一个更新对`myarray[6]`赋值后它将有6个元素，其中`myarray[5]`为空值。目前，采用这种方式扩大数组只允许使用在一维数组上。
+
+带下标的赋值方式允许创建下标不是从1开始的数组。例如，我们可以为`myarray[-2:7]`赋值来创建一个下标值从-2到7的数组。
+
+新的数组值也可以通过串接操作符`||`构建：
+
+```sql
+SELECT ARRAY[1,2] || ARRAY[3,4];
+ ?column?
+-----------
+ {1,2,3,4}
+(1 row)
+
+SELECT ARRAY[5,6] || ARRAY[[1,2],[3,4]];
+      ?column?
+---------------------
+ {{5,6},{1,2},{3,4}}
+(1 row)
+```
+
+串接操作符允许把一个单独的元素加入到一个一维数组的开头或末尾。它也能接受两个`*N*`维数组，或者一个`*N*`维数组和一个`*N+1*`维数组。
+
+当一个单独的元素被加入到一个一维数组的开头或末尾时，其结果是一个和数组操作数具有相同下界下标的新数组。例如：
+
+```sql
+SELECT array_dims(1 || '[0:1]={2,3}'::int[]);
+ array_dims
+------------
+ [0:2]
+(1 row)
+
+SELECT array_dims(ARRAY[1,2] || 3);
+ array_dims
+------------
+ [1:3]
+(1 row)
+```
+
+当两个具有相同维度数的数组被串接时，其结果保留左操作数的外维度的下界下标。结果将是一个数组，它由左操作数的每一个元素以及紧接着的右操作数的每一个元素。例如：
+
+```sql
+SELECT array_dims(ARRAY[1,2] || ARRAY[3,4,5]);
+ array_dims
+------------
+ [1:5]
+(1 row)
+
+SELECT array_dims(ARRAY[[1,2],[3,4]] || ARRAY[[5,6],[7,8],[9,0]]);
+ array_dims
+------------
+ [1:5][1:2]
+(1 row)
+```
+
+当一个`*N*`维数组被放在另一个`*N+1*`维数组的前面或者后面时，结果和上面的例子相似。每一个`*N*`维子数组实际上是`*N+1*`维数组外维度的一个元素。例如：
+
+```sql
+SELECT array_dims(ARRAY[1,2] || ARRAY[[3,4],[5,6]]);
+ array_dims
+------------
+ [1:3][1:2]
+(1 row)
+```
+
+一个数组也可以通过使用函数`array_prepend`、`array_append`或`array_cat`构建。前两个函数仅支持一维数组，但`array_cat`支持多维数组。 一些例子：
+
+```sql
+SELECT array_prepend(1, ARRAY[2,3]);
+ array_prepend
+---------------
+ {1,2,3}
+(1 row)
+
+SELECT array_append(ARRAY[1,2], 3);
+ array_append
+--------------
+ {1,2,3}
+(1 row)
+
+SELECT array_cat(ARRAY[1,2], ARRAY[3,4]);
+ array_cat
+-----------
+ {1,2,3,4}
+(1 row)
+
+SELECT array_cat(ARRAY[[1,2],[3,4]], ARRAY[5,6]);
+      array_cat
+---------------------
+ {{1,2},{3,4},{5,6}}
+(1 row)
+
+SELECT array_cat(ARRAY[5,6], ARRAY[[1,2],[3,4]]);
+      array_cat
+---------------------
+ {{5,6},{1,2},{3,4}}
+```
+
+在简单的情况中，上面讨论的串接操作符比直接使用这些函数更好。不过，由于 串接操作符需要服务于所有三种情况，所以它的负担比较重，在有些情况下使用 这些函数之一有助于避免混淆。例如：
+
+```sql
+SELECT ARRAY[1, 2] || '{3, 4}';  -- 没有指定类型的文字被当做一个数组
+ ?column?
+-----------
+ {1,2,3,4}
+
+SELECT ARRAY[1, 2] || '7';                 -- 这个也是
+ERROR:  malformed array literal: "7"
+
+SELECT ARRAY[1, 2] || NULL;                -- 未修饰的 NULL 也是如此
+ ?column?
+----------
+ {1,2}
+(1 row)
+
+SELECT array_append(ARRAY[1, 2], NULL);    -- 这可能才是想要的意思
+ array_append
+--------------
+ {1,2,NULL}
+```
+
+在上面的例子中，解析器看到在串接操作符的一遍看到了一个整数数组，并且在 另一边看到了一个未确定类型的常量。它用来决定该常量类型的启发式规则是假 定它和该操作符的另一个输入具有相同的类型 - 在这种情况中是整数数 组。因此串接操作符表示`array_cat`而不是 `array_append`。如果这样做是错误的选择，它可以通过将该常 量造型成数组的元素类型来修复。但是显式地使用`array_append` 可能是一种最好的方案。
+
+## 在数组中搜索
+
+要在一个数组中搜索一个值，每一个值都必须被检查。这可以手动完成，但是我们必须知道数组的尺寸。例如：
+
+```sql
+SELECT * FROM sal_emp WHERE pay_by_quarter[1] = 10000 OR
+                            pay_by_quarter[2] = 10000 OR
+                            pay_by_quarter[3] = 10000 OR
+                            pay_by_quarter[4] = 10000;
+```
+
+但是这对于大型数组来说太过冗长，且在数组尺寸未知时无法使用。上面的查询可以被替换为：
+
+```sql
+SELECT * FROM sal_emp WHERE 10000 = ANY (pay_by_quarter);
+```
+
+此外，我们还可以查找所有元素值都为10000的数组所在的行：
+
+```sql
+SELECT * FROM sal_emp WHERE 10000 = ALL (pay_by_quarter);
+```
+
+另外，`generate_subscripts`函数也可以用来完成类似的查找。例如：
+
+```sql
+SELECT * FROM
+   (SELECT pay_by_quarter,
+           generate_subscripts(pay_by_quarter, 1) AS s
+      FROM sal_emp) AS foo
+ WHERE pay_by_quarter[s] = 10000;
+```
+
+我们也可以使用`&&`操作符来搜索一个数组，它会检查左操作数是否与右操作数重叠。例如：
+
+```sql
+SELECT * FROM sal_emp WHERE pay_by_quarter && ARRAY[10000];
+```
+
+该操作符和其他数组操作符的进一步描述请见[数组函数和操作符](15-array-functions-and-operators)。
+
+你也可以使用`array_position`和`array_positions`在一个 数组中搜索特定值。前者返回值在数组中第一次出现的位置的下标。后者返回一个数组， 其中有该值在数组中的所有出现位置的下标。例如：
+
+```sql
+SELECT array_position(ARRAY['sun','mon','tue','wed','thu','fri','sat'], 'mon');
+ array_positions
+-----------------
+ 2
+
+SELECT array_positions(ARRAY[1, 4, 3, 1, 3, 4, 2, 1], 1);
+ array_positions
+-----------------
+ {1,4,8}
+```
+
+> **提示:** 数组不是集合，在其中搜索指定数组元素可能是数据设计失误的表现。考虑使用一个独立的表来替代，其中每一行都对应于一个数组元素。这将更有利于搜索，并且对于大量元素的可扩展性更好。
+
+## 数组输入和输出语法
+
+一个数组值的外部文本表现由根据数组元素类型的I/O转换规则解释的项构成，并在其上加上修饰用于指示数组结构。修饰包括数组值周围的花括号（`{`和`}`）以及相邻项之间的定界字符。定界字符通常是一个逗号（`,`），但是也可能是别的：它由数组元素类型的`typdelim`设置决定。在MogDB发行版提供的标准数据类型中，除了`box`类型使用分号（`;`）之外，其他都是用逗号。在一个多维数组中，每一个维度（行、平面、方体等）都有其自己的花括号层次，且同层的被花括号限定的相邻实体之间也必须有定界符。
+
+如果元素值是空字符串、包含花括号、包含定界字符、包含双引号、包含反斜线、包含空白或者匹配词`NULL`，数组输出例程将在元素值周围放上双引号。嵌在元素值中的双引号以及反斜线将被反斜线转义。对于数字数据类型可以安全地假设双引号绝不会出现，但是对于文本数据类型我们必须准备好处理可能出现亦可能不出现的引号。
+
+默认情况下，一个数组的一个维度的下界索引值被设置为1。要表示具有其他下界的数组，数组下标的范围应在填充数组内容之前被显式地指定好。这种修饰包括在每个数组维度上下界周围的方括号（`[]`），以及上下界之间的一个冒号（`:`）定界符。数组维度修饰后面要跟一个等号（`=`）。例如：
+
+```sql
+SELECT f1[1][-2][3] AS e1, f1[1][-1][5] AS e2
+ FROM (SELECT '[1:1][-2:-1][3:5]={{{1,2,3},{4,5,6}}}'::int[] AS f1) AS ss;
+
+ e1 | e2
+----+----
+  1 |  6
+(1 row)
+```
+
+只有当数组的维度中有一个或多个的下界不为1时，数组输出例程才会在结果中包括维度。
+
+如果为一个元素给定的值是`NULL`（或者是任何变体），该元素将被设置为NULL。任何引号或反斜线的存在将阻止这种行为，而允许为元素值输入"NULL"的字面意思。为了向后兼容之前的版本，可将[array_nulls](1-compatibility-with-earlier-versions)配置参数设置为`off`来阻止将`NULL`识别为NULL。
+
+如前所示，在写一个数组值时我们可以在任何单独数组元素周围使用引号。如果元素值可能混淆数组值分析器时，我们*必须* 这样做。例如，包含花括号、逗号（或者数据类型的定界符）、双引号、反斜线或首尾有空白的元素必须使用双引号。空字符串和匹配单词`NULL`的字符串也必须使用双引号。要把一个双引号或反斜线放在一个使用了双引号的数组元素值中，需要使用转义字符串语法并在其前面使用一个反斜线。作为一种选择，我们可以免去使用引号而使用反斜线转义的方式来保护可能被认为是数组语法的所有数据字符。
+
+我们可以在左括号前面或右括号后面增加空白。我们也可以在任何单独的项之前或之后加上空白。在所有这些情况中空白将被忽略。但是，在被使用了双引号的元素中的空白以及周围有其他非空白字符的空白不会被忽略。
+
+> **提示:** 在SQL命令中写数组值时，`ARRAY`构造器语法常常比数组文字语法要更容易使用。在`ARRAY`中，单独的元素值可以使用不属于数组成员时的方式来书写。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/13.1-range.md b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/13.1-range.md
new file mode 100644
index 0000000000000000000000000000000000000000..8c9a8088f8603d0c532976b30752c4cca2e27c44
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/13.1-range.md
@@ -0,0 +1,163 @@
+---
+title: 范围类型
+summary: 范围类型
+author: Zhang Cuiping
+date: 2021-10-25
+---
+
+# 范围类型
+
+范围类型是表达某种元素类型（称为范围的_subtype_）的一个值的范围的数据类型。例如，timestamp的范围可以被用来表达一个会议室被保留的时间范围。在这种情况下，数据类型是tsrange（“timestamp range”的简写）而timestamp是 subtype。subtype 必须具有一种总体的顺序，这样对于元素值是在一个范围值之内、之前或之后就是界线清楚的。
+
+范围类型非常有用，因为它们可以表达一种单一范围值中的多个元素值，并且可以很清晰地表达诸如范围重叠等概念。用于时间安排的时间和日期范围是最清晰的例子；但是价格范围、一种仪器的量程等等也都有用。
+
+## 内建范围类型
+
+有下列内建范围类型：
+
+- int4range - integer的范围
+- int8range - bigint的范围
+- numrange - numeric的范围
+- tsrange - 不带时区的 timestamp的范围
+- tstzrange - 带时区的 timestamp的范围
+- daterange - date的范围
+
+此外，你可以定义自己的范围类型，详见[CREATE TYPE](67-CREATE-TYPE)。
+
+## 例子
+
+```sql
+CREATE TABLE reservation (room int, during tsrange);
+INSERT INTO reservation VALUES (1108, '[2010-01-01 14:30, 2010-01-01 15:30)');
+-- 包含
+SELECT int4range(10, 20) @> 3;
+-- 重叠
+SELECT numrange(11.1, 22.2) && numrange(20.0, 30.0);
+-- 抽取上界
+SELECT upper(int8range(15, 25));
+-- 计算交集
+SELECT int4range(10, 20) * int4range(15, 25);
+-- 范围为空吗？
+SELECT isempty(numrange(1, 5));
+```
+
+范围类型上的操作符和函数的完整列表可见[范围函数和操作符](16-range-functions-and-operators)。
+
+## 包含和排除边界
+
+每一个非空范围都有两个界限，下界和上界。上下界之间的所有值都被包括在范围内。一个包含界限意味着边界点本身也被包括在范围内，而一个排除边界意味着边界点不被包括在范围内。
+
+在一个范围的文本形式中，一个包含下界被表达为“[”而一个排除下界被表达为“(”。同样，一个包含上界被表达为“]”而一个排除上界被表达为“)”（详见[范围输入/输出](范围输入输出)）。
+
+函数lower_inc和upper_inc分别测试一个范围值的上下界。
+
+## 无限（无界）范围
+
+一个范围的下界可以被忽略，意味着所有小于上界的值都被包括在范围中，例如(,3]。 同样，如果范围的上界被忽略，那么所有比上界大的值都被包括在范围中。如果上下界都被忽略，该元素类型的所有值都被认为在该范围中。 规定缺失的包括界限自动转换为排除，例如，[,] 转换为 (,)。 你可以认为这些缺失值为 +/- 无穷大，但它们是特殊范围类型值，并且被视为超出任何范围元素类型的 +/- 无穷大值。
+
+具有“infinity”概念的元素类型可以用它们作为显式边界值。例如，在时间戳范围，[today,infinity)不包括特殊的timestamp值infinity，尽管 [today,infinity] 包括它，就好比 [today,) 和 [today,]。
+
+函数lower_inf和upper_inf分别测试一个范围的无限上下界。
+
+## 范围输入/输出
+
+一个范围值的输入必须遵循下列模式之一：
+
+```sql
+(lower-bound,upper-bound)
+(lower-bound,upper-bound]
+[lower-bound,upper-bound)
+[lower-bound,upper-bound]
+empty
+```
+
+圆括号或方括号指示上下界是否为排除的或者包含的。注意最后一个模式是empty，它表示一个空范围（一个不包含点的范围）。
+
+_lower-bound_可以是作为subtype的合法输入的一个字符串，或者是空表示没有下界。同样，_upper-bound_可以是作为 subtype 的合法输入的一个字符串，或者是空表示没有上界。
+
+每个界限值可以使用”（双引号）字符引用。如果界限值包含圆括号、方括号、逗号、双引号或反斜线时，这样做是必须的，因为否则那些字符会被认作范围语法的一部分。要把一个双引号或反斜线放在一个被引用的界限值中，就在它前面放一个反斜线（还有，在一个双引号引用的界限值中的一对双引号表示一个双引号字符，这与 SQL 字符串中的单引号规则类似）。此外，你可以避免引用并且使用反斜线转义来保护所有数据字符，否则它们会被当做返回语法的一部分。还有，要写一个是空字符串的界限值，则可以写成”“，因为什么都不写表示一个无限界限。
+
+范围值前后允许有空格，但是圆括号或方括号之间的任何空格会被当做上下界值的一部分（取决于元素类型，它可能是也可能不是有意义的）。
+
+例子：
+
+```sql
+-- 包括 3，不包括 7，并且包括 3 和 7 之间的所有点
+SELECT '[3,7)'::int4range;
+-- 既不包括 3 也不包括 7，但是包括之间的所有点
+SELECT '(3,7)'::int4range;
+-- 只包括单独一个点 4
+SELECT '[4,4]'::int4range;
+-- 不包括点（并且将被标准化为 '空'）
+SELECT '[4,4)'::int4range;
+```
+
+## 构造范围
+
+每一种范围类型都有一个与其同名的构造器函数。使用构造器函数常常比写一个范围文字常数更方便，因为它避免了对界限值的额外引用。构造器函数接受两个或三个参数。两个参数的形式以标准的形式构造一个范围（下界是包含的，上界是排除的），而三个参数的形式按照第三个参数指定的界限形式构造一个范围。第三个参数必须是下列字符串之一： “()”、 “(]”、 “[)”或者 “[]”。 例如：
+
+```sql
+-- 完整形式是：下界、上界以及指示界限包含性/排除性的文本参数。
+SELECT numrange(1.0, 14.0, '(]');
+-- 如果第三个参数被忽略，则假定为 '[)'。
+SELECT numrange(1.0, 14.0);
+-- 尽管这里指定了 '(]'，显示时该值将被转换成标准形式，因为 int8range 是一种离散范围类型（见下文）。
+SELECT int8range(1, 14, '(]');
+-- 为一个界限使用 NULL 导致范围在那一边是无界的。
+SELECT numrange(NULL, 2.2);
+```
+
+## 离散范围类型
+
+一种范围的元素类型具有一个良定义的“步长”，例如integer或date。在这些类型中，如果两个元素之间没有合法值，它们可以被说成是相邻。这与连续范围相反，连续范围中总是（或者几乎总是）可以在两个给定值之间标识其他元素值。例如，numeric类型之上的一个范围就是连续的，timestamp上的范围也是（尽管timestamp具有有限的精度，并且在理论上可以被当做离散的，最好认为它是连续的，因为通常并不关心它的步长）。
+
+另一种考虑离散范围类型的方法是对每一个元素值都有一种清晰的“下一个”或“上一个”值。了解了这种思想之后，通过选择原来给定的下一个或上一个元素值来取代它，就可以在一个范围界限的包含和排除表达之间转换。例如，在一个整数范围类型中，[4,8]和(3,9)表示相同的值集合，但是对于 numeric 上的范围就不是这样。
+
+一个离散范围类型应该具有一个_正规化_函数，它知道元素类型期望的步长。正规化函数负责把范围类型的相等值转换成具有相同的表达，特别是与包含或者排除界限一致。如果没有指定一个正规化函数，那么具有不同格式的范围将总是会被当作不等，即使它们实际上是表达相同的一组值。
+
+内建的范围类型int4range、int8range和daterange都使用一种正规的形式，该形式包括下界并且排除上界，也就是[)。不过，用户定义的范围类型可以使用其他习惯。
+
+## 定义新的范围类型
+
+用户可以定义他们自己的范围类型。这样做最常见的原因是为了使用内建范围类型中没有提供的 subtype 上的范围。例如，要创建一个 subtype float8的范围类型：
+
+```sql
+CREATE TYPE floatrange AS RANGE (
+     subtype = float8,
+     subtype_diff = float8mi
+);
+SELECT '[1.234, 5.678]'::floatrange;
+```
+
+因为float8没有有意义的“步长”，我们在这个例子中没有定义一个正规化函数。
+
+定义自己的范围类型也允许你指定使用一个不同的子类型 B-树操作符类或者集合， 以便更改排序顺序来决定哪些值会落入到给定的范围中。
+
+如果 subtype 被认为是具有离散值而不是连续值，CREATE TYPE命令应当指定一个canonical函数。正规化函数接收一个输入的范围值，并且必须返回一个可能具有不同界限和格式的等价的范围值。对于两个表示相同值集合的范围（例如[1, 7]和[1, 8)），正规的输出必须一样。选择哪一种表达作为正规的没有关系，只要两个具有不同格式的等价值总是能被映射到具有相同格式的相同值就行。除了调整包含/排除界限格式外，假使期望的补偿比 subtype 能够存储的要大，一个正规化函数可能会舍入边界值。例如，一个timestamp之上的范围类型可能被定义为具有一个一小时的步长，这样正规化函数可能需要对不是一小时的倍数的界限进行舍入，或者可能直接抛出一个错误。
+
+另外，任何打算要和 GiST 或 SP-GiST 索引一起使用的范围类型应当定一个 subtype 差异或subtype_diff函数（没有subtype_diff时索引仍然能工作，但是可能效率不如提供了差异函数时高）。subtype 差异函数采用两个 subtype 输入值，并且返回表示为一个float8值的差（即_X_减_Y_）。在我们上面的例子中，可以使用常规float8减法操作符之下的函数。但是对于任何其他 subtype，可能需要某种类型转换。还可能需要一些关于如何把差异表达为数字的创新型想法。为了最大的可扩展性，subtype_diff函数应该同意选中的操作符类和排序规则所蕴含的排序顺序，也就是说，只要它的第一个参数根据排序顺序大于第二个参数，它的结果就应该是正值。
+
+subtype_diff函数的一个不那么过度简化的例子：
+
+```sql
+CREATE FUNCTION time_subtype_diff(x time, y time) RETURNS float8 AS 'SELECT EXTRACT(EPOCH FROM (x - y))' LANGUAGE sql STRICT IMMUTABLE;
+CREATE TYPE timerange AS RANGE (
+     subtype = time,
+     subtype_diff = time_subtype_diff
+ );
+SELECT '[11:10, 23:00]'::timerange;
+```
+
+更多关于创建范围类型的信息请参考[CREATE TYPE](67-CREATE-TYPE)。
+
+## 索引
+
+可以为范围类型的表列创建 GiST 和 SP-GiST 索引。例如，要创建一个 GiST 索引：
+
+```sql
+CREATE INDEX reservation_idx ON reservation USING GIST (during);
+```
+
+一个 GiST 或 SP-GiST 索引可以加速涉及以下范围操作符的查询： =、 &&、 &lt;@、 @&gt;、 &lt;&lt;、 &gt;&gt;、 -|-、 &&lt;以及 &&gt; （详见[范围函数和操作符](16-range-functions-and-operators)）。
+
+此外，B-树和哈希索引可以在范围类型的表列上创建。对于这些索引类型，基本上唯一有用的范围操作就是等值。使用相应的&lt; 和 &gt;操作符，对于范围值定义有一种 B-树排序顺序，但是该顺序相当任意并且在真实世界中通常不怎么有用。范围类型的 B-树和哈希支持主要是为了允许在查询内部进行排序和哈希，而不是创建真正的索引。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/14-object-identifier-types.md b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/14-object-identifier-types.md
new file mode 100644
index 0000000000000000000000000000000000000000..bf388d3e5cc4dc00e7d8f8e635219a61939c1506
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/14-object-identifier-types.md
@@ -0,0 +1,90 @@
+---
+title: 对象标识符类型
+summary: 对象标识符类型
+author: Guo Huan
+date: 2021-04-06
+---
+
+# 对象标识符类型
+
+MogDB在内部使用对象标识符（OID）作为各种系统表的主键。系统不会给用户创建的表增加一个OID系统字段，OID类型代表一个对象标识符。
+
+目前OID类型用一个四字节的无符号整数实现。因此不建议在创建的表中使用OID字段做主键。
+
+**表 1** 对象标识符类型
+
+| 名称          | 引用         | 描述         | 示例            |
+| :------------ | :----------- | :--------------- | :------------------|
+| OID           | -            | 数字化的对象标识符。             | 564182          |
+| CID           | -            | 命令标识符。它是系统字段cmin和cmax的数据类型。命令标识符是32位的量。     | -               |
+| XID           | -            | 事务标识符。它是系统字段xmin和xmax的数据类型。事务标识符是64位的量。 | -               |
+| TID           | -            | 行标识符。它是系统表字段ctid的数据类型。行ID是一对数值（块号，块内的行索引），它标识该行在其所在表内的物理位置。 | -               |
+| REGCONFIG     | pg_ts_config | 文本搜索配置。     | english         |
+| REGDICTIONARY | pg_ts_dict   | 文本搜索字典。               | simple          |
+| REGOPER       | pg_operator  | 操作符名。                   | -               |
+| REGOPERATOR   | pg_operator  | 带参数类型的操作符。         | *(integer,integer)或-(NONE,integer) |
+| REGPROC       | pg_proc      | 函数名称。                   | sum             |
+| REGPROCEDURE  | pg_proc      | 带参数类型的函数。           | sum(int4)       |
+| REGCLASS      | pg_class     | 关系名。 | pg_type         |
+| REGTYPE       | pg_type      | 数据类型名。                 | integer         |
+
+OID类型: 主要作为数据库系统表中字段使用。
+
+示例:
+
+```sql
+mogdb=# SELECT oid FROM pg_class WHERE relname = 'pg_type';
+ oid
+------
+ 1247
+(1 row)
+```
+
+OID别名类型REGCLASS: 主要用于对象OID值的简化查找。
+
+示例:
+
+```sql
+mogdb=# SELECT attrelid,attname,atttypid,attstattarget FROM pg_attribute WHERE attrelid = 'pg_type'::REGCLASS;
+ attrelid |  attname   | atttypid | attstattarget
+----------+------------+----------+---------------
+     1247 | xc_node_id     |       23 |             0
+     1247 | tableoid       |       26 |             0
+     1247 | cmax           |       29 |             0
+     1247 | xmax           |       28 |             0
+     1247 | cmin           |       29 |             0
+     1247 | xmin           |       28 |             0
+     1247 | oid            |       26 |             0
+     1247 | ctid           |       27 |             0
+     1247 | typname        |       19 |            -1
+     1247 | typnamespace   |       26 |            -1
+     1247 | typowner       |       26 |            -1
+     1247 | typlen         |       21 |            -1
+     1247 | typbyval       |       16 |            -1
+     1247 | typtype        |       18 |            -1
+     1247 | typcategory    |       18 |            -1
+     1247 | typispreferred |       16 |            -1
+     1247 | typisdefined   |       16 |            -1
+     1247 | typdelim       |       18 |            -1
+     1247 | typrelid       |       26 |            -1
+     1247 | typelem        |       26 |            -1
+     1247 | typarray       |       26 |            -1
+     1247 | typinput       |       24 |            -1
+     1247 | typoutput      |       24 |            -1
+     1247 | typreceive     |       24 |            -1
+     1247 | typsend        |       24 |            -1
+     1247 | typmodin       |       24 |            -1
+     1247 | typmodout      |       24 |            -1
+     1247 | typanalyze     |       24 |            -1
+     1247 | typalign       |       18 |            -1
+     1247 | typstorage     |       18 |            -1
+     1247 | typnotnull     |       16 |            -1
+     1247 | typbasetype    |       26 |            -1
+     1247 | typtypmod      |       23 |            -1
+     1247 | typndims       |       23 |            -1
+     1247 | typcollation   |       26 |            -1
+     1247 | typdefaultbin  |      194 |            -1
+     1247 | typdefault     |       25 |            -1
+     1247 | typacl         |     1034 |            -1
+(38 rows)
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/15-pseudo-types.md b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/15-pseudo-types.md
new file mode 100644
index 0000000000000000000000000000000000000000..356e84af9ddc99b131686bc07a867bcf174ed01e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/15-pseudo-types.md
@@ -0,0 +1,65 @@
+---
+title: 伪类型
+summary: 伪类型
+author: Guo Huan
+date: 2021-04-06
+---
+
+# 伪类型
+
+MogDB数据类型中包含一系列特殊用途的类型，这些类型按照类别被称为伪类型。伪类型不能作为字段的数据类型，但是可以用于声明函数的参数或者结果类型。
+
+当一个函数不仅是简单地接受并返回某种SQL数据类型的情况下伪类型是很有用的。[表1](#biao1)列出了所有的伪类型。
+
+**表 1** 伪类型 <a id="biao1"></a>
+
+| 名称             | 描述                                           |
+| :--------------- | :--------------------------------------------- |
+| any              | 表示函数接受任何输入数据类型。                 |
+| anyelement       | 表示函数接受任何数据类型。                     |
+| anyarray         | 表示函数接受任意数组数据类型。                 |
+| anynonarray      | 表示函数接受任意非数组数据类型。               |
+| anyenum          | 表示函数接受任意枚举数据类型。                 |
+| anyrange         | 表示函数接受任意范围数据类型。                 |
+| cstring          | 表示函数接受或者返回一个空结尾的C字符串。      |
+| internal         | 表示函数接受或者返回一种服务器内部的数据类型。 |
+| language_handler | 声明一个过程语言调用句柄返回language_handler。 |
+| fdw_handler      | 声明一个外部数据封装器返回fdw_handler。        |
+| record           | 标识函数返回一个未声明的行类型。               |
+| trigger          | 声明一个触发器函数返回trigger。                |
+| void             | 表示函数不返回数值。                           |
+| opaque           | 一个已经过时的类型，以前用于所有上面这些用途。 |
+
+声明用C编写的函数（不管是内置的还是动态装载的）都可以接受或者返回任何这样的伪数据类型。当伪类型作为参数类型使用时，用户需要保证函数的正常运行。
+
+用过程语言编写的函数只能使用实现语言允许的伪类型。目前，过程语言都不允许使用作为参数类型的伪类型，并且只允许使用void和record作为结果类型。一些多态的函数还支持使用anyelement，anyarray，anynonarray anyenum和anyrange类型。
+
+伪类型internal用于声明那种只能在数据库系统内部调用的函数，他们不能直接在SQL查询里调用。如果函数至少有一个internal类型的参数，则不能从SQL里调用他。建议不要创建任何声明返回internal的函数，除非他至少有一个internal类型的参数。
+
+示例:
+
+```sql
+--创建表
+mogdb=# create table t1 (a int);
+
+--插入两条数据
+mogdb=# insert into t1 values(1),(2);
+
+--创建函数showall()。
+mogdb=# CREATE OR REPLACE FUNCTION showall() RETURNS SETOF record
+AS $$ SELECT count(*) from t1; $$
+LANGUAGE SQL;
+
+--调用函数showall()。
+mogdb=# SELECT showall();
+ showall
+---------
+ (2)
+(1 row)
+
+--删除函数。
+mogdb=# DROP FUNCTION showall();
+
+--删除表
+mogdb=# drop table t1;
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/16-data-types-supported-by-column-store-tables.md b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/16-data-types-supported-by-column-store-tables.md
new file mode 100644
index 0000000000000000000000000000000000000000..7eba57ccf025e2f3cf26a17c53795b77eeecbfe8
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/16-data-types-supported-by-column-store-tables.md
@@ -0,0 +1,219 @@
+---
+title: 列存表支持的数据类型
+summary: 列存表支持的数据类型
+author: Guo Huan
+date: 2021-04-06
+---
+
+# 列存表支持的数据类型
+
+列存表支持的数据类型如表1所示。
+
+**表 1** 列存表支持的数据类型
+
+<table><thead align="left"><tr id="zh-cn_topic_0237121962_row829010145541"><th class="cellrowborder" id="mcps1.2.5.1.1"><p id="zh-cn_topic_0237121962_p182901514135411"><a name="zh-cn_topic_0237121962_p182901514135411"></a><a name="zh-cn_topic_0237121962_p182901514135411"></a>类别</p>
+</th>
+<th class="cellrowborder" valign="top" id="mcps1.2.5.1.2"><p id="zh-cn_topic_0237121962_p15290191416548"><a name="zh-cn_topic_0237121962_p15290191416548"></a><a name="zh-cn_topic_0237121962_p15290191416548"></a>数据类型</p>
+</th>
+<th class="cellrowborder" valign="top" id="mcps1.2.5.1.3"><p id="zh-cn_topic_0237121962_p16290114125415"><a name="zh-cn_topic_0237121962_p16290114125415"></a><a name="zh-cn_topic_0237121962_p16290114125415"></a>长度</p>
+</th>
+<th class="cellrowborder" valign="top" id="mcps1.2.5.1.4"><p id="zh-cn_topic_0237121962_p10290131475415"><a name="zh-cn_topic_0237121962_p10290131475415"></a><a name="zh-cn_topic_0237121962_p10290131475415"></a>是否支持</p>
+</th>
+</tr>
+</thead>
+<tbody><tr id="zh-cn_topic_0237121962_row729018142548"><td class="cellrowborder" rowspan="10" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p4290171415543"><a name="zh-cn_topic_0237121962_p4290171415543"></a><a name="zh-cn_topic_0237121962_p4290171415543"></a>Numeric Types</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p142901314175410"><a name="zh-cn_topic_0237121962_p142901314175410"></a><a name="zh-cn_topic_0237121962_p142901314175410"></a>smallint</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p1629011148541"><a name="zh-cn_topic_0237121962_p1629011148541"></a><a name="zh-cn_topic_0237121962_p1629011148541"></a>2</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.4 "><p id="zh-cn_topic_0237121962_p729031415540"><a name="zh-cn_topic_0237121962_p729031415540"></a><a name="zh-cn_topic_0237121962_p729031415540"></a>支持</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row17290191415415"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p12290101405412"><a name="zh-cn_topic_0237121962_p12290101405412"></a><a name="zh-cn_topic_0237121962_p12290101405412"></a>integer</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p929001420541"><a name="zh-cn_topic_0237121962_p929001420541"></a><a name="zh-cn_topic_0237121962_p929001420541"></a>4</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p17290114165413"><a name="zh-cn_topic_0237121962_p17290114165413"></a><a name="zh-cn_topic_0237121962_p17290114165413"></a>支持</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row329091415410"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p1929011418548"><a name="zh-cn_topic_0237121962_p1929011418548"></a><a name="zh-cn_topic_0237121962_p1929011418548"></a>bigint</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p1129018145546"><a name="zh-cn_topic_0237121962_p1129018145546"></a><a name="zh-cn_topic_0237121962_p1129018145546"></a>8</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p529021435416"><a name="zh-cn_topic_0237121962_p529021435416"></a><a name="zh-cn_topic_0237121962_p529021435416"></a>支持</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row6290161445410"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p16290614175414"><a name="zh-cn_topic_0237121962_p16290614175414"></a><a name="zh-cn_topic_0237121962_p16290614175414"></a>decimal</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p13290151417543"><a name="zh-cn_topic_0237121962_p13290151417543"></a><a name="zh-cn_topic_0237121962_p13290151417543"></a>-1</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p1029031418543"><a name="zh-cn_topic_0237121962_p1029031418543"></a><a name="zh-cn_topic_0237121962_p1029031418543"></a>支持</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row629041410543"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p1129031485418"><a name="zh-cn_topic_0237121962_p1129031485418"></a><a name="zh-cn_topic_0237121962_p1129031485418"></a>numeric</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p1329071465410"><a name="zh-cn_topic_0237121962_p1329071465410"></a><a name="zh-cn_topic_0237121962_p1329071465410"></a>-1</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p1629001435418"><a name="zh-cn_topic_0237121962_p1629001435418"></a><a name="zh-cn_topic_0237121962_p1629001435418"></a>支持</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row1290114155417"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p1290101435412"><a name="zh-cn_topic_0237121962_p1290101435412"></a><a name="zh-cn_topic_0237121962_p1290101435412"></a>real</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p1729012143548"><a name="zh-cn_topic_0237121962_p1729012143548"></a><a name="zh-cn_topic_0237121962_p1729012143548"></a>4</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p15290514175418"><a name="zh-cn_topic_0237121962_p15290514175418"></a><a name="zh-cn_topic_0237121962_p15290514175418"></a>支持</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row1829015147548"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p6290101411549"><a name="zh-cn_topic_0237121962_p6290101411549"></a><a name="zh-cn_topic_0237121962_p6290101411549"></a>double precision</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p16290114165416"><a name="zh-cn_topic_0237121962_p16290114165416"></a><a name="zh-cn_topic_0237121962_p16290114165416"></a>8</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p72901414155413"><a name="zh-cn_topic_0237121962_p72901414155413"></a><a name="zh-cn_topic_0237121962_p72901414155413"></a>支持</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row11290201411546"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p142901014115417"><a name="zh-cn_topic_0237121962_p142901014115417"></a><a name="zh-cn_topic_0237121962_p142901014115417"></a>smallserial</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p14290141414543"><a name="zh-cn_topic_0237121962_p14290141414543"></a><a name="zh-cn_topic_0237121962_p14290141414543"></a>2</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p2290181419545"><a name="zh-cn_topic_0237121962_p2290181419545"></a><a name="zh-cn_topic_0237121962_p2290181419545"></a>支持</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row329031414544"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p16290121416541"><a name="zh-cn_topic_0237121962_p16290121416541"></a><a name="zh-cn_topic_0237121962_p16290121416541"></a>serial</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p17290101435418"><a name="zh-cn_topic_0237121962_p17290101435418"></a><a name="zh-cn_topic_0237121962_p17290101435418"></a>4</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p129020141544"><a name="zh-cn_topic_0237121962_p129020141544"></a><a name="zh-cn_topic_0237121962_p129020141544"></a>支持</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row122901114185414"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p1229051411545"><a name="zh-cn_topic_0237121962_p1229051411545"></a><a name="zh-cn_topic_0237121962_p1229051411545"></a>bigserial</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p8290314155413"><a name="zh-cn_topic_0237121962_p8290314155413"></a><a name="zh-cn_topic_0237121962_p8290314155413"></a>8</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p329061475416"><a name="zh-cn_topic_0237121962_p329061475416"></a><a name="zh-cn_topic_0237121962_p329061475416"></a>支持</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row152905140543"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p129081465413"><a name="zh-cn_topic_0237121962_p129081465413"></a><a name="zh-cn_topic_0237121962_p129081465413"></a>Monetary Types</p>
+</td>
+<td class="cellrowborder" valign="top" width="46.839999999999996%" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p2029014148549"><a name="zh-cn_topic_0237121962_p2029014148549"></a><a name="zh-cn_topic_0237121962_p2029014148549"></a>money</p>
+</td>
+<td class="cellrowborder" valign="top" width="11.67%" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p14290181475411"><a name="zh-cn_topic_0237121962_p14290181475411"></a><a name="zh-cn_topic_0237121962_p14290181475411"></a>8</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.4 "><p id="zh-cn_topic_0237121962_p1729041412543"><a name="zh-cn_topic_0237121962_p1729041412543"></a><a name="zh-cn_topic_0237121962_p1729041412543"></a>支持</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row17290141495413"><td class="cellrowborder" rowspan="6" valign="top" width="29.82%" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p6290171485411"><a name="zh-cn_topic_0237121962_p6290171485411"></a><a name="zh-cn_topic_0237121962_p6290171485411"></a>Character Types</p>
+</td>
+<td class="cellrowborder" valign="top" width="46.839999999999996%" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p1629015140543"><a name="zh-cn_topic_0237121962_p1629015140543"></a><a name="zh-cn_topic_0237121962_p1629015140543"></a>character varying(n), varchar(n)</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p14290181415418"><a name="zh-cn_topic_0237121962_p14290181415418"></a><a name="zh-cn_topic_0237121962_p14290181415418"></a>-1</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.4 "><p id="zh-cn_topic_0237121962_p16290171418540"><a name="zh-cn_topic_0237121962_p16290171418540"></a><a name="zh-cn_topic_0237121962_p16290171418540"></a>支持</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row172904145544"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p929015143540"><a name="zh-cn_topic_0237121962_p929015143540"></a><a name="zh-cn_topic_0237121962_p929015143540"></a>character(n), char(n)</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p16290111418547"><a name="zh-cn_topic_0237121962_p16290111418547"></a><a name="zh-cn_topic_0237121962_p16290111418547"></a>n</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p8290111419540"><a name="zh-cn_topic_0237121962_p8290111419540"></a><a name="zh-cn_topic_0237121962_p8290111419540"></a>支持</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row20290914115417"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p32901214145415"><a name="zh-cn_topic_0237121962_p32901214145415"></a><a name="zh-cn_topic_0237121962_p32901214145415"></a>character、char</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p142901914115411"><a name="zh-cn_topic_0237121962_p142901914115411"></a><a name="zh-cn_topic_0237121962_p142901914115411"></a>1</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p1429001418542"><a name="zh-cn_topic_0237121962_p1429001418542"></a><a name="zh-cn_topic_0237121962_p1429001418542"></a>支持</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row12290814125418"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p4290101485417"><a name="zh-cn_topic_0237121962_p4290101485417"></a><a name="zh-cn_topic_0237121962_p4290101485417"></a>text</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p1229020141546"><a name="zh-cn_topic_0237121962_p1229020141546"></a><a name="zh-cn_topic_0237121962_p1229020141546"></a>-1</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p1529016148543"><a name="zh-cn_topic_0237121962_p1529016148543"></a><a name="zh-cn_topic_0237121962_p1529016148543"></a>支持</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row7290101405415"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p029012140542"><a name="zh-cn_topic_0237121962_p029012140542"></a><a name="zh-cn_topic_0237121962_p029012140542"></a>nvarchar2</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p129014147548"><a name="zh-cn_topic_0237121962_p129014147548"></a><a name="zh-cn_topic_0237121962_p129014147548"></a>-1</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p202901614135412"><a name="zh-cn_topic_0237121962_p202901614135412"></a><a name="zh-cn_topic_0237121962_p202901614135412"></a>支持</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row172907148542"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p5290914125415"><a name="zh-cn_topic_0237121962_p5290914125415"></a><a name="zh-cn_topic_0237121962_p5290914125415"></a>name</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p629081412547"><a name="zh-cn_topic_0237121962_p629081412547"></a><a name="zh-cn_topic_0237121962_p629081412547"></a>64</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p142908146549"><a name="zh-cn_topic_0237121962_p142908146549"></a><a name="zh-cn_topic_0237121962_p142908146549"></a>不支持</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row19290141414543"><td class="cellrowborder" rowspan="6" valign="top" width="29.82%" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p14290131412540"><a name="zh-cn_topic_0237121962_p14290131412540"></a><a name="zh-cn_topic_0237121962_p14290131412540"></a>Date/Time Types</p>
+</td>
+<td class="cellrowborder" valign="top" width="46.839999999999996%" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p3290151495415"><a name="zh-cn_topic_0237121962_p3290151495415"></a><a name="zh-cn_topic_0237121962_p3290151495415"></a>timestamp with time zone</p>
+</td>
+<td class="cellrowborder" valign="top" width="11.67%" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p20290111495420"><a name="zh-cn_topic_0237121962_p20290111495420"></a><a name="zh-cn_topic_0237121962_p20290111495420"></a>8</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.4 "><p id="zh-cn_topic_0237121962_p132908147546"><a name="zh-cn_topic_0237121962_p132908147546"></a><a name="zh-cn_topic_0237121962_p132908147546"></a>支持</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row172901014155417"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p1829041445411"><a name="zh-cn_topic_0237121962_p1829041445411"></a><a name="zh-cn_topic_0237121962_p1829041445411"></a>timestamp without time zone</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p192902145542"><a name="zh-cn_topic_0237121962_p192902145542"></a><a name="zh-cn_topic_0237121962_p192902145542"></a>8</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p5290121485410"><a name="zh-cn_topic_0237121962_p5290121485410"></a><a name="zh-cn_topic_0237121962_p5290121485410"></a>支持</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row132901514165419"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p14290181415547"><a name="zh-cn_topic_0237121962_p14290181415547"></a><a name="zh-cn_topic_0237121962_p14290181415547"></a>date</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p929071410545"><a name="zh-cn_topic_0237121962_p929071410545"></a><a name="zh-cn_topic_0237121962_p929071410545"></a>4</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p102900146546"><a name="zh-cn_topic_0237121962_p102900146546"></a><a name="zh-cn_topic_0237121962_p102900146546"></a>支持</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row13290181445412"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p1929020147545"><a name="zh-cn_topic_0237121962_p1929020147545"></a><a name="zh-cn_topic_0237121962_p1929020147545"></a>time without time zone</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p12290114145411"><a name="zh-cn_topic_0237121962_p12290114145411"></a><a name="zh-cn_topic_0237121962_p12290114145411"></a>8</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p10290614175411"><a name="zh-cn_topic_0237121962_p10290614175411"></a><a name="zh-cn_topic_0237121962_p10290614175411"></a>支持</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row102901714155411"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p13290131485413"><a name="zh-cn_topic_0237121962_p13290131485413"></a><a name="zh-cn_topic_0237121962_p13290131485413"></a>time with time zone</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p92902014105420"><a name="zh-cn_topic_0237121962_p92902014105420"></a><a name="zh-cn_topic_0237121962_p92902014105420"></a>12</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p82901814155415"><a name="zh-cn_topic_0237121962_p82901814155415"></a><a name="zh-cn_topic_0237121962_p82901814155415"></a>支持</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row1029061411542"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p1729012141543"><a name="zh-cn_topic_0237121962_p1729012141543"></a><a name="zh-cn_topic_0237121962_p1729012141543"></a>interval</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p172901314105418"><a name="zh-cn_topic_0237121962_p172901314105418"></a><a name="zh-cn_topic_0237121962_p172901314105418"></a>16</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p1529071414545"><a name="zh-cn_topic_0237121962_p1529071414545"></a><a name="zh-cn_topic_0237121962_p1529071414545"></a>支持</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row1729021435410"><td class="cellrowborder" rowspan="2" valign="top" width="29.82%" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p1290191455417"><a name="zh-cn_topic_0237121962_p1290191455417"></a><a name="zh-cn_topic_0237121962_p1290191455417"></a>big object</p>
+</td>
+<td class="cellrowborder" valign="top" width="46.839999999999996%" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p11290314165418"><a name="zh-cn_topic_0237121962_p11290314165418"></a><a name="zh-cn_topic_0237121962_p11290314165418"></a>clob</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p172901143541"><a name="zh-cn_topic_0237121962_p172901143541"></a><a name="zh-cn_topic_0237121962_p172901143541"></a>-1</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.4 "><p id="zh-cn_topic_0237121962_p629020143542"><a name="zh-cn_topic_0237121962_p629020143542"></a><a name="zh-cn_topic_0237121962_p629020143542"></a>支持</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row7290121435417"><td class="cellrowborder" valign="top" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p629019144544"><a name="zh-cn_topic_0237121962_p629019144544"></a><a name="zh-cn_topic_0237121962_p629019144544"></a>blob</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p1729091425412"><a name="zh-cn_topic_0237121962_p1729091425412"></a><a name="zh-cn_topic_0237121962_p1729091425412"></a>-1</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p0290514105414"><a name="zh-cn_topic_0237121962_p0290514105414"></a><a name="zh-cn_topic_0237121962_p0290514105414"></a>不支持</p>
+</td>
+</tr>
+<tr id="zh-cn_topic_0237121962_row12290514165416"><td class="cellrowborder" valign="top" width="29.82%" headers="mcps1.2.5.1.1 "><p id="zh-cn_topic_0237121962_p1229011417541"><a name="zh-cn_topic_0237121962_p1229011417541"></a><a name="zh-cn_topic_0237121962_p1229011417541"></a>other types</p>
+</td>
+<td class="cellrowborder" valign="top" width="46.839999999999996%" headers="mcps1.2.5.1.2 "><p id="zh-cn_topic_0237121962_p3290191475416"><a name="zh-cn_topic_0237121962_p3290191475416"></a><a name="zh-cn_topic_0237121962_p3290191475416"></a>…</p>
+</td>
+<td class="cellrowborder" valign="top" width="11.67%" headers="mcps1.2.5.1.3 "><p id="zh-cn_topic_0237121962_p1029013140546"><a name="zh-cn_topic_0237121962_p1029013140546"></a><a name="zh-cn_topic_0237121962_p1029013140546"></a>…</p>
+</td>
+<td class="cellrowborder" valign="top" headers="mcps1.2.5.1.4 "><p id="zh-cn_topic_0237121962_p1229019143547"><a name="zh-cn_topic_0237121962_p1229019143547"></a><a name="zh-cn_topic_0237121962_p1229019143547"></a>不支持</p>
+</td>
+</tr>
+</tbody>
+</table>
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/17-xml-type.md b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/17-xml-type.md
new file mode 100644
index 0000000000000000000000000000000000000000..84dfee7fdbdbf2fa60b57fcf17a323cf25f3f241
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/17-xml-type.md
@@ -0,0 +1,34 @@
+---
+title: XML类型
+summary: XML类型
+author: Guo Huan
+date: 2021-04-06
+---
+
+# XML类型
+
+MogDB支持XML类型，使用示例如下。
+
+```sql
+mogdb= CREATE TABLE xmltest ( id int, data xml );
+mogdb= INSERT INTO xmltest VALUES (1, 'one');
+mogdb= INSERT INTO xmltest VALUES (2, 'two');
+mogdb= SELECT * FROM xmltest ORDER BY 1;
+ id | data
+----+--------------------
+1 | one
+2 | two
+(2 rows)
+openGauss= SELECT xmlconcat('', NULL, '');
+xmlconcat
+(1 row)
+openGauss= SELECT xmlconcat('', NULL, '');
+xmlconcat
+(1 row)
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 该功能默认未开启，如需使用，需要重新使用build.sh脚本编译数据库，修改./configure配置参数，在其中加入-with-libxml参数。
+> - 在执行编译之前，需要先执行yum install -y libxml2-devel，否则会有”configure: error: library 'xml2' (version &gt;= 2.6.23) is required for XML support”的报错。
+> - 在执行编译之前，需要三方库二进制文件中dependeny操作系统环境/libobs/comm/lib加入到系统环境变量LD_LIBRARY_PATH中，否则会报错”libiconv.so不存在”。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/18-data-type-used-by-the-ledger-database.md b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/18-data-type-used-by-the-ledger-database.md
new file mode 100644
index 0000000000000000000000000000000000000000..354ebe4fbe1bda1dd5402d2952599bcf475278a8
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/18-data-type-used-by-the-ledger-database.md
@@ -0,0 +1,31 @@
+---
+title: 账本数据库使用的数据类型
+summary: 账本数据库使用的数据类型
+author: Zhang Cuiping
+date: 2021-10-25
+---
+
+# 账本数据库使用的数据类型
+
+账本数据库使用HASH16数据类型来存储行级hash摘要或表级hash摘要，使用HASH32数据类型来存储全局hash摘要或者历史表校验hash。
+
+**表 1** 账本数据库HAS
+
+| 名称   | 描述                   | 存储空间 | 范围                      |
+| :-------------- | :-------------------| :------- | :----------------------------------------- |
+| HASH16 | 以无符号64位整数存储。                 | 8字节    | 0 ~ +18446744073709551615                  |
+| HASH32 | 以包含16个的无符号整形元素数的组存储。 | 16字节   | 16个元素的无符号整形数组能够包含的取值范围 |
+
+HASH16数据类型用来在账本数据库中存储行级或表级hash摘要，在获得长度为16个字符串的十六进制字符串的hash序列后，系统将调用hash16in函数将该序列转换为一个无符号64位整数存储进HASH16类型变量中。示例如下：
+
+```
+十六进制字符串：e697da2eaa3a775b   对应的无符号64位整数：16615989244166043483
+十六进制字符串：ffffffffffffffff   对应的无符号64位整数：18446744073709551615
+```
+
+HASH32数据类型用来在账本数据库中存储全局hash摘要或者历史表校验hash，在获得长度为32个字符串的十六进制字符串的hash序列后，系统将调用hash32in函数将该序列转换到一个包含16个无符号整形元素的数组中。示例如下：
+
+```
+十六进制字符串：685847ed1fe38e18f6b0e2b18c00edee
+对应的HASH32数组：[104,88,71,237,31,227,142,24,246,176,226,177,140,0,237,238]
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/2-monetary.md b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/2-monetary.md
new file mode 100644
index 0000000000000000000000000000000000000000..1b3d1b57c53484c29773e6d128340cac29bec48b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/2-monetary.md
@@ -0,0 +1,34 @@
+---
+title: 货币类型
+summary: 货币类型
+author: Guo Huan
+date: 2021-04-06
+---
+
+# 货币类型
+
+货币类型存储带有固定小数精度的货币金额。
+
+表1中显示的范围假设有两位小数。可以以任意格式输入，包括整型、浮点型或者典型的货币格式（如“$1,000.00”）。根据区域字符集，输出一般是最后一种形式。
+
+**表 1** 货币类型
+
+| 名称  | 存储容量 | 描述     | 范围                                           |
+| :---- | :------- | :------- | :--------------------------------------------- |
+| money | 8 字节   | 货币金额 | -92233720368547758.08 到 +92233720368547758.07 |
+
+numeric、int和bigint类型的值可以转化为money类型。如果从real和double precision类型转换到money类型，可以先转化为numeric类型，再转化为money类型，例如：
+
+```sql
+mogdb=# SELECT '12.34'::float8::numeric::money;
+```
+
+这种用法是不推荐使用的。浮点数不应该用来处理货币类型，因为小数点的位数可能会导致错误。
+
+money类型的值可以转换为numeric类型而不丢失精度。转换为其他类型可能丢失精度，并且必须通过以下两步来完成：
+
+```sql
+mogdb=# SELECT '52093.89'::money::numeric::float8;
+```
+
+当一个money类型的值除以另一个money类型的值时，结果是double precision（也就是一个纯数字，而不是money类型）；在运算过程中货币单位相互抵消。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/3-boolean-data-types.md b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/3-boolean-data-types.md
new file mode 100644
index 0000000000000000000000000000000000000000..d9e0eeed32806e02f6272e384f0a7ee1e375176e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/3-boolean-data-types.md
@@ -0,0 +1,59 @@
+---
+title: 布尔类型
+summary: 布尔类型
+author: Guo Huan
+date: 2021-04-06
+---
+
+# 布尔类型
+
+**表 1** 布尔类型
+
+| 名称    | 描述     | 存储空间 | 取值                                                   |
+| :------ | :------- | :------- | :----------------------------------------------------- |
+| BOOLEAN | 布尔类型 | 1字节。  | - true: 真<br/>- false: 假<br/>- null: 未知（unknown） |
+
+- "真"值的有效文本值是:
+
+  TRUE、't'、'true'、'y'、'yes'、'1'、'TRUE'、true、整数范围内1~2^63-1、整数范围内-1~2^63。
+
+- "假"值的有效文本值是:
+
+  FALSE、'f'、'false'、'n'、'no'、'0'、0、'FALSE'、false。
+
+使用TRUE和FALSE是比较规范的用法（也是SQL兼容的用法）。
+
+## 示例
+
+显示用字母t和f输出Boolean值。
+
+```sql
+--创建表。
+mogdb=# CREATE TABLE bool_type_t1
+(
+    BT_COL1 BOOLEAN,
+    BT_COL2 TEXT
+);
+
+--插入数据。
+mogdb=# INSERT INTO bool_type_t1 VALUES (TRUE, 'sic est');
+
+mogdb=# INSERT INTO bool_type_t1 VALUES (FALSE, 'non est');
+
+--查看数据。
+mogdb=# SELECT * FROM bool_type_t1;
+ bt_col1 | bt_col2
+---------+---------
+ t       | sic est
+ f       | non est
+(2 rows)
+
+mogdb=# SELECT * FROM bool_type_t1 WHERE bt_col1 = 't';
+ bt_col1 | bt_col2
+---------+---------
+ t       | sic est
+(1 row)
+
+--删除表。
+mogdb=# DROP TABLE bool_type_t1;
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/4-character-data-types.md b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/4-character-data-types.md
new file mode 100644
index 0000000000000000000000000000000000000000..119c43df7c0a9961e0150583793a1be3d994fe23
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/4-character-data-types.md
@@ -0,0 +1,89 @@
+---
+title: 字符类型
+summary: 字符类型
+author: Guo Huan
+date: 2021-04-06
+---
+
+# 字符类型
+
+MogDB支持的字符类型请参见表1。字符串操作符和相关的内置函数请参见[字符处理函数和操作符](3-character-processing-functions-and-operators)。
+
+**表 1** 字符类型
+
+| 名称                           | 描述                  | 存储空间                    |
+| :----------------------------- | :------------------------- | :------------------------- |
+| CHAR(n)CHARACTER(n)NCHAR(n)    | 定长字符串，不足补空格。n是指字节长度，如不带精度n，默认精度为1。 | 最大为10MB。                                                 |
+| VARCHAR(n)CHARACTER VARYING(n) | 变长字符串。n是指字节长度。                                  | 最大为10MB。                                                 |
+| VARCHAR2(n)                    | 变长字符串。是VARCHAR(n)类型的别名。n是指字节长度。          | 最大为10MB。                                                 |
+| NVARCHAR2(n)                   | 变长字符串。n是指字符长度。                                  | 最大为10MB。                                                 |
+| TEXT                           | 变长字符串。                                                 | 最大为1GB-1，但还需要考虑到列描述头信息的大小， 以及列所在元组的大小限制（也小于1GB-1），因此TEXT类型最大大小可能小于1GB-1。 |
+| CLOB                           | 文本大对象。是TEXT类型的别名。                               | 最大为1GB-1，但还需要考虑到列描述头信息的大小， 以及列所在元组的大小限制（也小于1GB-1），因此CLOB类型最大大小可能小于1GB-1。 |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+> 除了每列的大小限制以外，每个元组的总大小也不可超过1GB-1字节，主要受列的控制头信息、元组控制头信息等、以及元组中是否存在`NULL`字段等影响。
+
+在MogDB里另外还有两种定长字符类型。在表2里显示。name类型只用在内部系统表中，作为存储标识符，不建议普通用户使用。该类型长度当前定为64字节（63可用字符加结束符）。类型"char"只用了一个字节的存储空间。他在系统内部主要用于系统表，主要作为简单化的枚举类型使用。
+
+**表 2** 特殊字符类型
+
+| 名称   | 描述                   | 存储空间 |
+| :----- | :--------------------- | :------- |
+| name   | 用于对象名的内部类型。 | 64字节。 |
+| "char" | 单字节内部类型。       | 1字节。  |
+
+## 示例
+
+```sql
+--创建表。
+mogdb=# CREATE TABLE char_type_t1
+(
+    CT_COL1 CHARACTER(4)
+);
+
+--插入数据。
+mogdb=# INSERT INTO char_type_t1 VALUES ('ok');
+
+--查询表中的数据。
+mogdb=# SELECT ct_col1, char_length(ct_col1) FROM char_type_t1;
+ ct_col1 | char_length
+---------+-------------
+ ok      |           4
+(1 row)
+
+--删除表。
+mogdb=# DROP TABLE char_type_t1;
+```
+
+```sql
+--创建表。
+mogdb=# CREATE TABLE char_type_t2
+(
+    CT_COL1 VARCHAR(5)
+);
+
+--插入数据。
+mogdb=# INSERT INTO char_type_t2 VALUES ('ok');
+
+mogdb=# INSERT INTO char_type_t2 VALUES ('good');
+
+--插入的数据长度超过类型规定的长度报错。
+mogdb=# INSERT INTO char_type_t2 VALUES ('too long');
+ERROR:  value too long for type character varying(5)
+CONTEXT:  referenced column: ct_col1
+
+--明确类型的长度，超过数据类型长度后会自动截断。
+mogdb=# INSERT INTO char_type_t2 VALUES ('too long'::varchar(5));
+
+--查询数据。
+mogdb=# SELECT ct_col1, char_length(ct_col1) FROM char_type_t2;
+ ct_col1 | char_length
+---------+-------------
+ ok      |           2
+ good    |           4
+ too l   |           5
+(3 rows)
+
+--删除数据。
+mogdb=# DROP TABLE char_type_t2;
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/4.1-enumerated-types.md b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/4.1-enumerated-types.md
new file mode 100644
index 0000000000000000000000000000000000000000..28b0c2df750bfe2ecd796863aa982a9051894352
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/4.1-enumerated-types.md
@@ -0,0 +1,101 @@
+---
+title: 枚举类型
+summary: 枚举类型
+author: Guo Huan
+date: 2021-11-19
+---
+
+# 枚举类型
+
+枚举（enum）类型是由一个静态、值的有序集合构成的数据类型。它们等效于很多编程语言所支持的`enum`类型。枚举类型的一个例子可以是一周中的日期，或者一个数据的状态值集合。
+
+## 枚举类型的声明
+
+枚举类型可以使用[CREATE TYPE](67-CREATE-TYPE)命令创建，例如：
+
+```sql
+CREATE TYPE mood AS ENUM ('sad', 'ok', 'happy');
+```
+
+一旦被创建，枚举类型可以像很多其他类型一样在表和函数定义中使用：
+
+```sql
+CREATE TYPE mood AS ENUM ('sad', 'ok', 'happy');
+CREATE TABLE person (
+    name text,
+    current_mood mood
+);
+INSERT INTO person VALUES ('Moe', 'happy');
+SELECT * FROM person WHERE current_mood = 'happy';
+ name | current_mood
+------+--------------
+ Moe  | happy
+(1 row)
+```
+
+## 排序
+
+一个枚举类型的值的排序是该类型被创建时所列出的值的顺序。枚举类型的所有标准的比较操作符以及相关聚集函数都被支持。例如：
+
+```sql
+INSERT INTO person VALUES ('Larry', 'sad');
+INSERT INTO person VALUES ('Curly', 'ok');
+SELECT * FROM person WHERE current_mood > 'sad';
+ name  | current_mood
+-------+--------------
+ Moe   | happy
+ Curly | ok
+(2 rows)
+
+SELECT * FROM person WHERE current_mood > 'sad' ORDER BY current_mood;
+ name  | current_mood
+-------+--------------
+ Curly | ok
+ Moe   | happy
+(2 rows)
+
+SELECT name
+FROM person
+WHERE current_mood = (SELECT MIN(current_mood) FROM person);
+ name
+-------
+ Larry
+(1 row)
+```
+
+## 类型安全性
+
+每一种枚举数据类型都是独立的并且不能和其他枚举类型相比较。看这样一个例子：
+
+```sql
+CREATE TYPE happiness AS ENUM ('happy', 'very happy', 'ecstatic');
+CREATE TABLE holidays (
+    num_weeks integer,
+    happiness happiness
+);
+INSERT INTO holidays(num_weeks,happiness) VALUES (4, 'happy');
+INSERT INTO holidays(num_weeks,happiness) VALUES (6, 'very happy');
+INSERT INTO holidays(num_weeks,happiness) VALUES (8, 'ecstatic');
+INSERT INTO holidays(num_weeks,happiness) VALUES (2, 'sad');
+ERROR:  invalid input value for enum happiness: "sad"
+SELECT person.name, holidays.num_weeks FROM person, holidays
+  WHERE person.current_mood = holidays.happiness;
+ERROR:  operator does not exist: mood = happiness
+```
+
+如果你确实需要做这样的事情，你可以写一个自定义的操作符或者在查询中加上显式造型：
+
+```sql
+SELECT person.name, holidays.num_weeks FROM person, holidays
+  WHERE person.current_mood::text = holidays.happiness::text;
+ name | num_weeks
+------+-----------
+ Moe  |         4
+(1 row)
+```
+
+## 实现细节
+
+一个枚举值在磁盘上占据4个字节。一个枚举值的文本标签的长度受限于`NAMEDATALEN`设置，该设置被编译在MogDB中，在标准编译下它表示最多63字节。
+
+枚举标签是大小写敏感的，因此`'happy'`是不同于`'HAPPY'`的。标签内的空白也是有效的。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/5-binary-data-types.md b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/5-binary-data-types.md
new file mode 100644
index 0000000000000000000000000000000000000000..3321a1d7ea1d2c34c789c82cafb96c306fdf1a6a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/5-binary-data-types.md
@@ -0,0 +1,54 @@
+---
+title: 二进制类型
+summary: 二进制类型
+author: Guo Huan
+date: 2021-04-06
+---
+
+# 二进制类型
+
+MogDB支持的二进制类型请参见[表1](#biao1)。
+
+**表 1** 二进制类型 <a id="biao1"> </a>
+
+| 名称                           | 描述            | 存储空间                             |
+| :-------------------------------- | :------------------ | :----------------------- |
+| BLOB                           | 二进制大对象<br/>说明：<br />列存不支持BLOB类型     | 最大为1GB-8203字节（即1073733621字节）。                                |
+| RAW                            | 变长的十六进制类型<br/>说明：<br />列存不支持RAW类型 | 4字节加上实际的十六进制字符串。最大为1GB-8203字节（即1073733621字节）。 |
+| BYTEA                          | 变长的二进制字符串                                  | 4字节加上实际的二进制字符串。最大为1GB-8203字节（即1073733621字节）。   |
+| BYTEAWITHOUTORDERWITHEQUALCOL  | 变长的二进制字符串（密态特性新增的类型，如果加密列的加密类型指定为确定性加密，则该列的实际类型为BYTEAWITHOUTORDERWITHEQUALCO），元命令打印加密表将显示原始数据类型。 | 4字节加上实际的二进制字符串。最大为1GB减去53字节（即1073741771字节）。  |
+| BYTEAWITHOUTORDERCOL           | 变长的二进制字符串（密态特性新增的类型，如果加密列的加密类型指定为随机加密，则该列的实际类型为BYTEAWITHOUTORDERCOL），元命令打印加密表将显示原始数据类型。 | 4字节加上实际的二进制字符串。最大为1GB减去53字节（即1073741771字节）。  |
+| _BYTEAWITHOUTORDERWITHEQUALCOL | 变长的二进制字符串，密态特性新增的类型              | 4字节加上实际的二进制字符串。最大为1GB减去53字节（即1073741771字节）。  |
+| _BYTEAWITHOUTORDERCOL          | 变长的二进制字符串，密态特性新增的类型              | 4字节加上实际的二进制字符串。最大为1GB减去53字节（即1073741771字节）。  |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 除了每列的大小限制以外，每个元组的总大小也不可超过1GB-8203字节（即1073733621字节）。
+> - 不支持直接使用BYTEAWITHOUTORDERWITHEQUALCOL和BYTEAWITHOUTORDERCOL，_BYTEAWITHOUTORDERWITHEQUALCOL，_BYTEAWITHOUTORDERCOL类型创建表。
+
+示例:
+
+```sql
+--创建表。
+mogdb=# CREATE TABLE blob_type_t1
+(
+    BT_COL1 INTEGER,
+    BT_COL2 BLOB,
+    BT_COL3 RAW,
+    BT_COL4 BYTEA
+) ;
+
+--插入数据。
+mogdb=# INSERT INTO blob_type_t1 VALUES(10,empty_blob(),
+HEXTORAW('DEADBEEF'),E'\\xDEADBEEF');
+
+--查询表中的数据。
+mogdb=# SELECT * FROM blob_type_t1;
+ bt_col1 | bt_col2 | bt_col3  |  bt_col4
+---------+---------+----------+------------
+      10 |         | DEADBEEF | \xdeadbeef
+(1 row)
+
+--删除表。
+mogdb=# DROP TABLE blob_type_t1;
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/6-date-time-types.md b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/6-date-time-types.md
new file mode 100644
index 0000000000000000000000000000000000000000..94c0881d9715bf95e1549c1d075b19aa507035ec
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/6-date-time-types.md
@@ -0,0 +1,323 @@
+---
+title: 日期/时间类型
+summary: 日期/时间类型
+author: Guo Huan
+date: 2021-06-16
+---
+
+# 日期/时间类型
+
+MogDB支持的日期/时间类型请参见表1。该类型的操作符和内置函数请参见时间和日期处理函数和操作符。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:** 如果其他的数据库时间格式和MogDB的时间格式不一致，可通过修改配置参数DateStyle的值来保持一致。
+
+**表 1** 日期/时间类型
+
+| 名称                               | 描述            | 存储空间                         |
+| :--------------------------------- | :-------------------------------------- | :------------------------------- |
+| DATE                               | 日期和时间。 | 4字节（实际存储空间大小为8字节） |
+| TIME [(p)] [WITHOUT TIME ZONE]     | 只用于一日内时间。<br/>p表示小数点后的精度，取值范围为0~6。 | 8字节                            |
+| TIME [(p)] [WITH TIME ZONE]        | 只用于一日内时间，带时区。<br/>p表示小数点后的精度，取值范围为0~6。      | 12字节                           |
+| TIMESTAMP[(p)] [WITHOUT TIME ZONE] | 日期和时间。<br/>p表示小数点后的精度，取值范围为0~6。  | 8字节                            |
+| TIMESTAMP[(p)][WITH TIME ZONE]    | 日期和时间，带时区。TIMESTAMP的别名为TIMESTAMPTZ。<br/>p表示小数点后的精度，取值范围为0~6。         | 8字节                            |
+| SMALLDATETIME                      | 日期和时间，不带时区。<br/>精确到分钟，秒位大于等于30秒进一位。          | 8字节                            |
+| INTERVAL DAY (l) TO SECOND (p)     | 时间间隔，X天X小时X分X秒。<br/>- l: 天数的精度，取值范围为0-6。兼容性考虑，目前未实现具体功能。<br/>- p: 秒数的精度，取值范围为0-6。小数末尾的零不显示。                         | 16字节                           |
+| INTERVAL [FIELDS] [ (p) ]          | 时间间隔。<br/>- fields: 可以是YEAR，MONTH，DAY，HOUR，MINUTE，SECOND，DAY TO HOUR，DAY TO MINUTE，DAY TO SECOND，HOUR TO MINUTE，HOUR TO SECOND，MINUTE TO SECOND。<br/>- p: 秒数的精度，取值范围为0-6，且fields为SECOND，DAY TO SECOND，HOUR TO SECOND或MINUTE TO SECOND时，参数p才有效。小数末尾的零不显示。 | 12字节                           |
+| reltime                            | 相对时间间隔。格式为: <br/>X years X mons X days XX:XX:XX。<br/>采用儒略历计时，规定一年为365.25天，一个月为30天，计算输入值对应的相对时间间隔，输出采用POSTGRES格式。           | 4字节                            |
+| abstime                            | 日期和时间。格式为: <br/>YYYY-MM-DD hh:mm:ss+timezone<br/>取值范围为1901-12-13 20:45:53 GMT~2038-01-18 23:59:59 GMT，精度为秒。 | 4字节                            |
+
+示例:
+
+```sql
+--创建表。
+mogdb=# CREATE TABLE date_type_tab(coll date);
+
+--插入数据。
+mogdb=# INSERT INTO date_type_tab VALUES (date '12-10-2010');
+
+--查看数据。
+mogdb=# SELECT * FROM date_type_tab;
+        coll
+---------------------
+ 2010-12-10 00:00:00
+(1 row)
+
+--删除表。
+mogdb=# DROP TABLE date_type_tab;
+
+--创建表。
+mogdb=# CREATE TABLE time_type_tab (da time without time zone ,dai time with time zone,dfgh timestamp without time zone,dfga timestamp with time zone, vbg smalldatetime);
+
+--插入数据。
+mogdb=# INSERT INTO time_type_tab VALUES ('21:21:21','21:21:21 pst','2010-12-12','2013-12-11 pst','2003-04-12 04:05:06');
+
+--查看数据。
+mogdb=# SELECT * FROM time_type_tab;
+    da    |     dai     |        dfgh         |          dfga          |         vbg
+----------+-------------+---------------------+------------------------+---------------------
+ 21:21:21 | 21:21:21-08 | 2010-12-12 00:00:00 | 2013-12-11 16:00:00+08 | 2003-04-12 04:05:00
+(1 row)
+
+--删除表。
+mogdb=# DROP TABLE time_type_tab;
+
+--创建表。
+mogdb=# CREATE TABLE day_type_tab (a int,b INTERVAL DAY(3) TO SECOND (4));
+
+--插入数据。
+mogdb=# INSERT INTO day_type_tab VALUES (1, INTERVAL '3' DAY);
+
+--查看数据。
+mogdb=# SELECT * FROM day_type_tab;
+ a |   b
+---+--------
+ 1 | 3 days
+(1 row)
+
+--删除表。
+mogdb=# DROP TABLE day_type_tab;
+
+--创建表。
+mogdb=# CREATE TABLE year_type_tab(a int, b interval year (6));
+
+--插入数据。
+mogdb=# INSERT INTO year_type_tab VALUES(1,interval '2' year);
+
+--查看数据。
+mogdb=# SELECT * FROM year_type_tab;
+ a |    b
+---+---------
+ 1 | 2 years
+(1 row)
+
+--删除表。
+mogdb=# DROP TABLE year_type_tab;
+```
+
+## 日期输入
+
+日期和时间的输入几乎可以是任何合理的格式，包括ISO-8601格式、SQL-兼容格式、传统POSTGRES格式或者其它的形式。系统支持按照日、月、年的顺序自定义日期输入。如果把DateStyle参数设置为MDY就按照"月-日-年"解析，设置为DMY就按照"日-月-年"解析，设置为YMD就按照"年-月-日"解析。
+
+日期的文本输入需要加单引号包围，语法如下:
+
+type [ ( p ) ] 'value'
+
+可选的精度声明中的p是一个整数，表示在秒域中小数部分的位数。表2显示了date类型的输入方式。
+
+**表 2** 日期输入方式
+
+| 例子             | 描述           |
+| :------------------------ | :------------------------------------------------------------ |
+| 1999-01-08       | ISO 8601格式（建议格式），任何方式下都是1999年1月8号。                                      |
+| January 8, 1999  | 在任何datestyle输入模式下都无歧义。       |
+| 1/8/1999         | 有歧义，在MDY模式下是一月八号，在DMY模式下是八月一号。                                      |
+| 1/18/1999        | MDY模式下是一月十八日，其它模式下被拒绝。 |
+| 01/02/03         | - MDY模式下的2003年1月2日。<br/>- DMY模式下的2003年2月1日。<br/>- YMD模式下的2001年2月3日。 |
+| 1999-Jan-08      | 任何模式下都是1月8日。                    |
+| Jan-08-1999      | 任何模式下都是1月8日。                    |
+| 08-Jan-1999      | 任何模式下都是1月8日。                    |
+| 99-Jan-08        | YMD模式下是1月8日，否则错误。             |
+| 08-Jan-99        | 一月八日，除了在YMD模式下是错误的之外。   |
+| Jan-08-99        | 一月八日，除了在YMD模式下是错误的之外。   |
+| 19990108         | ISO 8601；任何模式下都是1999年1月8日。    |
+| 990108           | ISO 8601；任何模式下都是1999年1月8日。    |
+| 1999.008         | 年和年里的第几天。                        |
+| J2451187         | 儒略日。       |
+| January 8, 99 BC | 公元前99年。   |
+
+示例:
+
+```sql
+--创建表。
+mogdb=# CREATE TABLE date_type_tab(coll date);
+
+--插入数据。
+mogdb=# INSERT INTO date_type_tab VALUES (date '12-10-2010');
+
+--查看数据。
+mogdb=# SELECT * FROM date_type_tab;
+        coll
+---------------------
+ 2010-12-10 00:00:00
+(1 row)
+
+--查看日期格式。
+mogdb=# SHOW datestyle;
+ DateStyle
+-----------
+ ISO, MDY
+(1 row)
+
+--设置日期格式。
+mogdb=# SET datestyle='YMD';
+SET
+
+--插入数据。
+mogdb=# INSERT INTO date_type_tab VALUES(date '2010-12-11');
+
+--查看数据。
+mogdb=# SELECT * FROM date_type_tab;
+        coll
+---------------------
+ 2010-12-10 00:00:00
+ 2010-12-11 00:00:00
+(2 rows)
+
+--删除表。
+mogdb=# DROP TABLE date_type_tab;
+```
+
+## 时间
+
+时间类型包括time [ (p) ] without time zone和time [ (p) ] with time zone。如果只写time等效于time without time zone。
+
+如果在time without time zone类型的输入中声明了时区，则会忽略这个时区。
+
+时间输入类型的详细信息请参见表3，时区输入类型的详细信息请参加表4。
+
+**表 3** 时间输入
+
+| 例子                                 | 描述                             |
+| :----------------------------------- | :------------------------------- |
+| 05:06.8                              | ISO 8601                         |
+| 4:05:06                              | ISO 8601                         |
+| 4:05                                 | ISO 8601                         |
+| 40506                                | ISO 8601                         |
+| 4:05 AM                              | 与04:05一样，AM不影响数值        |
+| 4:05 PM                              | 与16:05一样，输入小时数必须<= 12 |
+| 04:05:06.789-8                       | ISO 8601                         |
+| 04:05:06-08:00                       | ISO 8601                         |
+| 04:05-08:00                          | ISO 8601                         |
+| 040506-08                            | ISO 8601                         |
+| 04:05:06 PST                         | 缩写的时区                       |
+| 2003-04-12 04:05:06 America/New_York | 用名称声明的时区                 |
+
+**表 4** 时区输入
+
+| 例子             | 描述                                    |
+| :--------------- | :-------------------------------------- |
+| PST              | 太平洋标准时间（Pacific Standard Time） |
+| America/New_York | 完整时区名称                            |
+| -8:00            | ISO 8601与PST的偏移                     |
+| -800             | ISO 8601与PST的偏移                     |
+| -8               | ISO 8601与PST的偏移                     |
+
+示例:
+
+```sql
+mogdb=# SELECT time '04:05:06';
+   time
+----------
+ 04:05:06
+(1 row)
+
+mogdb=# SELECT time '04:05:06 PST';
+   time
+----------
+ 04:05:06
+(1 row)
+
+mogdb=# SELECT time with time zone '04:05:06 PST';
+   timetz
+-------------
+ 04:05:06-08
+(1 row)
+```
+
+## 特殊值
+
+MogDB支持几个特殊值，在读取的时候将被转换成普通的日期/时间值，请参考表5。
+
+**表 5** 特殊值
+
+| 输入字符串 | 适用类型              | 描述                                    |
+| :--------- | :-------------------- | :-------------------------------------- |
+| epoch      | date，timestamp       | 1970-01-01 00:00:00+00 （Unix系统零时） |
+| infinity   | timestamp             | 比任何其他时间戳都晚                    |
+| -infinity  | timestamp             | 比任何其他时间戳都早                    |
+| now        | date，time，timestamp | 当前事务的开始时间                      |
+| today      | date，timestamp       | 今日午夜                                |
+| tomorrow   | date，timestamp       | 明日午夜                                |
+| yesterday  | date，timestamp       | 昨日午夜                                |
+| allballs   | time                  | 00:00:00.00 UTC                         |
+
+## 时间段输入
+
+reltime的输入方式可以采用任何合法的时间段文本格式，包括数字形式（含负数和小数）及时间形式，其中时间形式的输入支持SQL标准格式、ISO-8601格式、POSTGRES格式等。另外，文本输入需要加单引号。
+
+时间段输入的详细信息请参考表6。
+
+**表 6** 时间段输入
+
+<table>
+    <tr>
+        <th>输入示例</th>
+        <th>输出结果</th>
+        <th>描述</th>
+    </tr>
+    <tr>
+        <td>60</td>
+        <td>2 mons</td>
+        <td rowspan="3">采用数字表示时间段，默认单位是day，可以是小数或负数。特别的，负数时间段，在语义上，可以理解为"早于多久"。</td>
+    </tr>
+    <tr>
+        <td>31.25</td>
+        <td>1 mons 1 days 06:00:00</td>
+    </tr>
+    <tr>
+        <td>-365</td>
+        <td>-12 mons -5 days</td>
+    </tr>
+    <tr>
+        <td>1 years 1 mons 8 days 12:00:00</td>
+        <td>1 years 1 mons 8 days 12:00:00</td>
+        <td rowspan="3">采用POSTGRES格式表示时间段，可以正负混用，不区分大小写，输出结果为将输入时间段计算并转换得到的简化POSTGRES格式时间段。</td>
+    </tr>
+    <tr>
+        <td>-13 months -10 hours</td>
+        <td>-1 years -25 days -04:00:00</td>
+    </tr>
+    <tr>
+        <td>-2 YEARS +5 MONTHS 10 DAYS</td>
+        <td>-1 years -6 mons -25 days -06:00:00</td>
+    </tr>
+    <tr>
+        <td>P-1.1Y10M</td>
+        <td>-3 mons -5 days -06:00:00</td>
+        <td rowspan="2">采用ISO-8601格式表示时间段，可以正负混用，不区分大小写，输出结果为将输入时间段计算并转换得到的简化POSTGRES格式时间段。</td>
+    </tr>
+    <tr>
+        <td>-12H</td>
+        <td>-12:00:00</td>
+    </tr>
+</table>
+
+示例:
+
+```sql
+--创建表。
+mogdb=# CREATE TABLE reltime_type_tab(col1 character(30), col2 reltime);
+
+--插入数据。
+mogdb=# INSERT INTO reltime_type_tab VALUES ('90', '90');
+mogdb=# INSERT INTO reltime_type_tab VALUES ('-366', '-366');
+mogdb=# INSERT INTO reltime_type_tab VALUES ('1975.25', '1975.25');
+mogdb=# INSERT INTO reltime_type_tab VALUES ('-2 YEARS +5 MONTHS 10 DAYS', '-2 YEARS +5 MONTHS 10 DAYS');
+mogdb=# INSERT INTO reltime_type_tab VALUES ('30 DAYS 12:00:00', '30 DAYS 12:00:00');
+mogdb=# INSERT INTO reltime_type_tab VALUES ('P-1.1Y10M', 'P-1.1Y10M');
+
+--查看数据。
+mogdb=# SELECT * FROM reltime_type_tab;
+              col1              |                col2
+--------------------------------+-------------------------------------
+ 1975.25                        | 5 years 4 mons 29 days
+ -2 YEARS +5 MONTHS 10 DAYS     | -1 years -6 mons -25 days -06:00:00
+ P-1.1Y10M                      | -3 mons -5 days -06:00:00
+ -366                           | -1 years -18:00:00
+ 90                             | 3 mons
+ 30 DAYS 12:00:00               | 1 mon 12:00:00
+(6 rows)
+
+--删除表。
+mogdb=# DROP TABLE reltime_type_tab;
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/7-geometric.md b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/7-geometric.md
new file mode 100644
index 0000000000000000000000000000000000000000..5edb3afc2193c5a39d51ec9a37b9f574e955eefb
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/7-geometric.md
@@ -0,0 +1,118 @@
+---
+title: 几何类型
+summary: 几何类型
+author: Guo Huan
+date: 2021-04-06
+---
+
+# 几何类型
+
+MogDB支持的几何类型请参见表1。最基本的类型: 点，是其它类型的基础。
+
+**表 1** 几何类型
+
+| 名称    | 存储空间   | 说明                     | 表现形式                 |
+| :------ | :--------- | :----------------------- | :----------------------- |
+| point   | 16字节     | 平面中的点               | (x,y)                    |
+| lseg    | 32字节     | （有限）线段             | ((x1,y1),(x2,y2))        |
+| box     | 32字节     | 矩形                     | ((x1,y1),(x2,y2))        |
+| path    | 16+16n字节 | 闭合路径（与多边形类似） | ((x1,y1),…)              |
+| path    | 16+16n字节 | 开放路径                 | [(x1,y1),…]              |
+| polygon | 40+16n字节 | 多边形（与闭合路径相似） | ((x1,y1),…)              |
+| circle  | 24 字节    | 圆                       | <(x,y),r> （圆心和半径） |
+
+MogDB提供了一系列的函数和操作符用来进行各种几何计算，如拉伸、转换、旋转、计算相交等。详细信息请参考几何函数和操作符。
+
+## 点
+
+点是几何类型的基本二维构造单位。用下面语法描述point的数值:
+
+```
+( x , y )
+x , y
+```
+
+x和y是用浮点数表示的点的坐标。
+
+点输出使用第一种语法。
+
+## 线段
+
+线段（lseg）是用一对点来代表的。用下面的语法描述lseg的数值:
+
+```
+[ ( x1 , y1 ) , ( x2 , y2 ) ]
+( ( x1 , y1 ) , ( x2 , y2 ) )
+( x1 , y1 ) , ( x2 , y2 )
+x1 , y1   ,   x2 , y2
+```
+
+(x1,y1)和(x2,y2)表示线段的端点。
+
+线段输出使用第一种语法。
+
+## 矩形
+
+矩形是用一对对角点来表示的。用下面的语法描述box的值:
+
+```
+( ( x1 , y1 ) , ( x2 , y2 ) )
+( x1 , y1 ) , ( x2 , y2 )
+x1 , y1   ,   x2 , y2
+```
+
+(x1,y1)和(x2,y2)表示矩形的一对对角点。
+
+矩形的输出使用第二种语法。
+
+任何两个对角都可以出现在输入中，但按照那样的顺序，右上角和左下角的值会被重新排序以存储。
+
+## 路径
+
+路径由一系列连接的点组成。路径可能是开放的，也就是认为列表中第一个点和最后一个点没有连接，也可能是闭合的，这时认为第一个和最后一个点连接起来。
+
+用下面的语法描述path的数值:
+
+```
+[ ( x1 , y1 ) , ... , ( xn , yn ) ]
+( ( x1 , y1 ) , ... , ( xn , yn ) )
+( x1 , y1 ) , ... , ( xn , yn )
+( x1 , y1   , ... ,   xn , yn )
+x1 , y1   , ... ,   xn , yn
+```
+
+点表示组成路径的线段的端点。方括弧（[]）表明一个开放的路径，圆括弧（()）表明一个闭合的路径。当最外层的括号被省略，如在第三至第五语法，会假定一个封闭的路径。
+
+路径的输出使用第一种或第二种语法输出。
+
+## 多边形
+
+多边形由一系列点代表（多边形的顶点）。多边形可以认为与闭合路径一样，但是存储方式不一样而且有自己的一套支持函数。
+
+用下面的语法描述polygon的数值:
+
+```
+( ( x1 , y1 ) , ... , ( xn , yn ) )
+( x1 , y1 ) , ... , ( xn , yn )
+( x1 , y1   , ... ,   xn , yn )
+x1 , y1   , ... ,   xn , yn
+```
+
+点表示多边形的端点。
+
+多边形输出使用第一种语法。
+
+## 圆
+
+圆由一个圆心和半径标识。用下面的语法描述circle的数值:
+
+```
+< ( x , y ) , r >
+( ( x , y ) , r )
+( x , y ) , r
+x , y   , r
+```
+
+(x,y)表示圆心，r表示半径。
+
+圆的输出用第一种格式。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/8-network-address.md b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/8-network-address.md
new file mode 100644
index 0000000000000000000000000000000000000000..95ea667fa13984ffa29fb710d8740235d5262938
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/8-network-address.md
@@ -0,0 +1,67 @@
+---
+title: 网络地址类型
+summary: 网络地址类型
+author: Guo Huan
+date: 2021-04-06
+---
+
+# 网络地址类型
+
+MogDB提供用于存储IPv4、IPv6、MAC地址的数据类型。
+
+用这些数据类型存储网络地址比用纯文本类型好，因为这些类型提供输入错误检查和特殊的操作和功能。
+
+**表 1** 网络地址类型
+
+| 名称    | 存储空间  | 描述                 |
+| :------ | :-------- | :------------------- |
+| cidr    | 7或19字节 | IPv4或IPv6网络       |
+| inet    | 7或19字节 | IPv4或IPv6主机和网络 |
+| macaddr | 6字节     | MAC地址              |
+
+在对inet或cidr数据类型进行排序的时候，IPv4地址总是排在IPv6地址前面，包括那些封装或者是映射在IPv6地址里的IPv4地址，比如::10.2.3.4或::ffff:10.4.3.2。
+
+## cidr
+
+cidr（无类别域间路由，Classless Inter-Domain Routing）类型，保存一个IPv4或IPv6网络地址。声明网络格式为address/y，address表示IPv4或者IPv6地址，y表示子网掩码的二进制位数。如果省略y，则掩码部分使用已有类别的网络编号系统进行计算，但要求输入的数据已经包括了确定掩码所需的所有字节。
+
+**表 2** cidr类型输入举例
+
+| cidr输入                             | cidr输出                             | abbrev（cidr）                   |
+| :----------------------------------- | :----------------------------------- | :------------------------------- |
+| 192.168.100.128⁄25                   | 192.168.100.128⁄25                   | 192.168.100.128⁄25               |
+| 192.168⁄24                           | 192.168.0.0/24                       | 192.168.0/24                     |
+| 192.168⁄25                           | 192.168.0.0/25                       | 192.168.0.0/25                   |
+| 192.168.1                            | 192.168.1.0/24                       | 192.168.1⁄24                     |
+| 192.168                              | 192.168.0.0/24                       | 192.168.0/24                     |
+| 10.1.2                               | 10.1.2.0/24                          | 10.1.2⁄24                        |
+| 10.1                                 | 10.1.0.1⁄16                          | 10.1⁄16                          |
+| 10                                   | 10.0.0.0/8                           | 10⁄8                             |
+| 10.1.2.3⁄32                          | 10.1.2.3⁄32                          | 10.1.2.3⁄32                      |
+| 2001:4f8:3:ba::/64                   | 2001:4f8:3:ba::/64                   | 2001:4f8:3:ba::/64               |
+| 2001:4f8:3:ba:2e0:81ff:fe22:d1f1/128 | 2001:4f8:3:ba:2e0:81ff:fe22:d1f1/128 | 2001:4f8:3:ba:2e0:81ff:fe22:d1f1 |
+| ::ffff:1.2.3.0/120                   | ::ffff:1.2.3.0/120                   | ::ffff:1.2.3⁄120                 |
+| ::ffff:1.2.3.0/128                   | ::ffff:1.2.3.0/128                   | ::ffff:1.2.3.0/128               |
+
+## inet
+
+inet类型在一个数据区域内保存主机的IPv4或IPv6地址，以及一个可选子网。主机地址中网络地址的位数表示子网（"子网掩码"）。如果子网掩码是32并且地址是IPv4，则这个值不表示任何子网，只表示一台主机。在IPv6里，地址长度是128位，因此128位表示唯一的主机地址。
+
+该类型的输入格式是address/y，address表示IPv4或者IPv6地址，y是子网掩码的二进制位数。如果省略/y，则子网掩码对IPv4是32，对IPv6是128，所以该值表示只有一台主机。如果该值表示只有一台主机，/y将不会显示。
+
+inet和cidr类型之间的基本区别是inet接受子网掩码，而cidr不接受。
+
+## macaddr
+
+macaddr类型存储MAC地址，也就是以太网卡硬件地址（尽管MAC地址还用于其它用途）。可以接受下列格式:
+
+```
+'08:00:2b:01:02:03'
+'08-00-2b-01-02-03'
+'08002b:010203'
+'08002b-010203'
+'0800.2b01.0203'
+'08002b010203'
+```
+
+这些示例都表示同一个地址。对于数据位a到f，大小写都行。输出时都是以第一种形式展示。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/9-bit-string-types.md b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/9-bit-string-types.md
new file mode 100644
index 0000000000000000000000000000000000000000..6c7355606bd707060961531f473446bd28b01a6b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/supported-data-types/9-bit-string-types.md
@@ -0,0 +1,50 @@
+---
+title: 位串类型
+summary: 位串类型
+author: Guo Huan
+date: 2021-04-06
+---
+
+# 位串类型
+
+位串就是一串1和0的字符串。它们可以用于存储位掩码。
+
+MogDB支持两种位串类型: bit(n)和bit varying(n)，这里的n是一个正整数。
+
+bit类型的数据必须准确匹配长度n，如果存储短或者长的数据都会报错。bit varying类型的数据是最长为n的变长类型，超过n的类型会被拒绝。一个没有长度的bit等效于bit(1)，没有长度的bit varying表示没有长度限制。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+> 如果用户明确地把一个位串值转换成bit(n)，则此位串右边的内容将被截断或者在右边补齐零，直到刚好n位，而不会抛出任何错误。
+> 如果用户明确地把一个位串数值转换成bit varying(n)，如果它超过了n位，则它的右边将被截断。
+
+```sql
+--创建表。
+mogdb=# CREATE TABLE bit_type_t1
+(
+    BT_COL1 INTEGER,
+    BT_COL2 BIT(3),
+    BT_COL3 BIT VARYING(5)
+) ;
+
+--插入数据。
+mogdb=# INSERT INTO bit_type_t1 VALUES(1, B'101', B'00');
+
+--插入数据的长度不符合类型的标准会报错。
+mogdb=# INSERT INTO bit_type_t1 VALUES(2, B'10', B'101');
+ERROR:  bit string length 2 does not match type bit(3)
+CONTEXT:  referenced column: bt_col2
+
+--将不符合类型长度的数据进行转换。
+mogdb=# INSERT INTO bit_type_t1 VALUES(2, B'10'::bit(3), B'101');
+
+--查看数据。
+mogdb=# SELECT * FROM bit_type_t1;
+ bt_col1 | bt_col2 | bt_col3
+---------+---------+---------
+       1 | 101     | 00
+       2 | 100     | 101
+(2 rows)
+
+--删除表。
+mogdb=# DROP TABLE bit_type_t1;
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/overview-of-system-catalogs-and-system-views.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/overview-of-system-catalogs-and-system-views.md
new file mode 100644
index 0000000000000000000000000000000000000000..43fddeaa038f1a3d71b47751880957f0b684e4b7
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/overview-of-system-catalogs-and-system-views.md
@@ -0,0 +1,119 @@
+---
+title: 系统表和系统视图概述
+summary: 系统表和系统视图概述
+author: Guo Huan
+date: 2021-04-19
+---
+
+# 系统表和系统视图概述
+
+系统表是MogDB存放结构元数据的地方，它是MogDB数据库系统运行控制信息的来源，是数据库系统的核心组成部分。
+
+系统视图提供了查询系统表和访问数据库内部状态的方法。
+
+系统表和系统视图要么只对管理员可见，要么对所有用户可见。下面的系统表和视图有些标识了需要管理员权限，这些系统表和视图只有管理员可以查询。
+
+用户可以删除后重新创建这些表、增加列、插入和更新数值，但是用户修改系统表会导致系统信息的不一致，从而导致系统控制紊乱。正常情况下不应该由用户手工修改系统表或系统视图，或者手工重命名系统表或系统视图所在的模式，而是由SQL语句关联的系统表操作自动维护系统表信息。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+> 用户应该禁止对系统表进行增删改等操作，人为对系统表的修改或破坏可能会导致系统各种异常情况甚至MogDB不可用。
+
+## 支持updatable-views
+
+视图可更新指的是用户可以通过视图对视图对应的基表进行INSERT/UPDATE/DELETE操作来更新基表的数据。
+
+为了使视图可更新，视图中的行与基表中的数据行必须要有一一对应的关系，具体来说，视图中存在以下内容的时候，则该视图不可更新：
+
++ 聚合函数或者窗口函数，比如sum、count、min、max、avg等
+
++ DISTINCT语句
+
++ HAVING、GROUP BY、START WITH、CONNECT BY
+
++ UNION、UNION ALL、INTERSECT、EXCEPT
+
++ 选择列中有子查询
+
++ FROM子句中有不可更新的视图
+
++ WHERE子句中的字子查询引用了FROM子句中的表
+
++ 视图定义中的列由函数或者表达式产生，例如`decode(...)`
+
++ 对于JOIN视图
+
+  + 多表连接的视图做DML的时候必须存在不少于1张带有唯一键或者主键的基表
+
+  + 多表连接的视图上的任何INSERT、UPDATE或DELETE操作一次只能修改一个基表
+  
+## 示例
+
+### INSERT VIEW
+
+```sql
+CREATE TABLE IF NOT EXISTS table1(id int, a char(6), b varchar(6), c varchar(6));
+
+INSERT INTO table1 VALUES(1, reverse('123A78'), '123A78', '1sdfBB');
+INSERT INTO table1 VALUES(2, reverse('E3gw78'), 'E3g78', 'lkoier');
+INSERT INTO table1 VALUES(3, reverse('HHiiw6'), 'Hiw6', '23fdsg');
+
+CREATE VIEW test_view AS SELECT * FROM table1 WHERE id > 1;
+
+INSERT INTO test_view VALUES(4, '2sdafd', '23ata', 'dstsee'); 
+
+SELECT * FROM table1 WHERE id = 4;
+ id |   a    |   b   |   c    
+----+--------+-------+--------
+  4 | 2sdafd | 23ata | dstsee
+(1 row)
+
+DROP VIEW IF EXISTS test_view;
+DROP TABLE IF EXISTS table1;
+```
+
+### UPDATE VIEW
+
+```sql
+CREATE TABLE IF NOT EXISTS table1(id int, a char(6), b varchar(6), c varchar(6));
+INSERT INTO table1 VALUES(1, reverse('123A78'), '123A78', '1sdfBB');
+INSERT INTO table1 VALUES(2, reverse('E3gw78'), 'E3g78', 'lkoier');
+INSERT INTO table1 VALUES(3, reverse('HHiiw6'), 'Hiw6', '23fdsg');
+
+CREATE VIEW test_view AS SELECT * FROM table1 WHERE id > 1;
+
+UPDATE test_view SET a = '2222' WHERE id = 2;
+
+SELECT * FROM table1;
+ id |   a    |   b    |   c    
+----+--------+--------+--------
+  1 | 87A321 | 123A78 | 1sdfBB
+  3 | 6wiiHH | Hiw6   | 23fdsg
+  2 | 2222   | E3g78  | lkoier
+(3 rows)
+
+DROP VIEW IF EXISTS test_view;
+DROP TABLE IF EXISTS table1;
+```
+
+### DELETE VIEW
+
+```sql
+CREATE TABLE IF NOT EXISTS table1(id int, a char(6), b varchar(6), c varchar(6));
+
+INSERT INTO table1 VALUES(1, reverse('123A78'), '123A78', '1sdfBB');
+INSERT INTO table1 VALUES(2, reverse('E3gw78'), 'E3g78', 'lkoier');
+INSERT INTO table1 VALUES(3, reverse('HHiiw6'), 'Hiw6', '23fdsg');
+
+CREATE VIEW test_view AS SELECT * FROM table1 WHERE id > 1;
+
+DELETE FROM test_view WHERE id = 2; 
+
+SELECT * FROM table1 WHERE id > 1;
+ id |   a    |  b   |   c    
+----+--------+------+--------
+  3 | 6wiiHH | Hiw6 | 23fdsg
+(1 row)
+
+DROP VIEW IF EXISTS test_view;
+DROP TABLE IF EXISTS table1;
+```
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY.md
new file mode 100644
index 0000000000000000000000000000000000000000..a71ab413f3a30f2048eb5496093925e3e6a22909
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY.md
@@ -0,0 +1,20 @@
+---
+title: GS_AUDITING_POLICY
+summary: GS_AUDITING_POLICY
+author: Guo Huan
+date: 2021-06-07
+---
+
+# GS_AUDITING_POLICY
+
+GS_AUDITING_POLICY系统表记录统一审计的主体信息，每条记录对应一个设计策略。需要有系统管理员或安全策略管理员权限才可以访问此系统表。
+
+**表 1** GS_AUDITING_POLICY字段
+
+| 名称        | 类型                        | 描述                         |
+| :---------- | :-------------------------- | :--------------------------- |
+| oid         | oid                         | 行标识符（隐藏属性，必须明确选择）。                         |
+| polname     | name                        | 策略名称，需要唯一，不可重复。                               |
+| polcomments | name                        | 策略描述字段，记录策略相关的描述信息，通过COMMENTS关键字体现。 |
+| modifydate  | timestamp without time zone | 策略创建或修改的最新时间戳。                                 |
+| polenabled  | boolean                     | 用来表示策略启动开关。                                       |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY_ACCESS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY_ACCESS.md
new file mode 100644
index 0000000000000000000000000000000000000000..b0e0d07905a7e226109bac6185fcd9f05ed2a5d5
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY_ACCESS.md
@@ -0,0 +1,20 @@
+---
+title: GS_AUDITING_POLICY_ACCESS
+summary: GS_AUDITING_POLICY_ACCESS
+author: Guo Huan
+date: 2021-06-07
+---
+
+# GS_AUDITING_POLICY_ACCESS
+
+GS_AUDITING_POLICY_ACCESS系统表记录与DML数据库相关操作的统一审计信息。需要有系统管理员或安全策略管理员权限才可以访问此系统表。
+
+**表 1** GS_AUDITING_POLICY_ACCESS字段
+
+| 名称       | 类型                        | 描述                                                        |
+| :--------- | :-------------------------- | :---------------------------------------------------------- |
+| oid        | oid                         | 行标识符（隐藏属性，必须明确选择）。                        |
+| accesstype | name                        | DML数据库操作相关类型。例如SELECT、INSERT、DELETE等。       |
+| labelname  | name                        | 资源标签名称。对应系统表gs_auditing_policy中的polname字段。 |
+| policyoid  | oid                         | 对应审计策略系统表GS_AUDITING_POLICY中的oid。               |
+| modifydate | timestamp without time zone | 创建或修改的最新时间戳。                                    |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY_FILTERS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY_FILTERS.md
new file mode 100644
index 0000000000000000000000000000000000000000..74a8e79f83d88102e6ca836c635e0f45fb66189d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY_FILTERS.md
@@ -0,0 +1,21 @@
+---
+title: GS_AUDITING_POLICY_FILTERS
+summary: GS_AUDITING_POLICY_FILTERS
+author: Guo Huan
+date: 2021-06-07
+---
+
+# GS_AUDITING_POLICY_FILTERS
+
+GS_AUDITING_POLICY_FILTERS系统表记录统一审计相关的过滤策略相关信息，每条记录对应一个设计策略。需要有系统管理员或安全策略管理员权限才可以访问此系统表。
+
+**表 1** GS_AUDITING_POLICY_FILTERS字段
+
+| 名称            | 类型      | 描述                                                     |
+| :-------------- | :-------- | :------------------------------------------------------- |
+| oid             | oid       | 行标识符（隐藏属性，必须明确选择）。                     |
+| filtertype      | name      | 过滤类型。目前值仅为logical_expr。                       |
+| labelname       | name      | 名称。目前值仅为logical_expr。                           |
+| policyoid       | oid       | 所属审计策略的Oid，对应系统表GS_AUDITING_POLICY中的oid。 |
+| modifydate      | timestamp | 创建或修改的最新时间戳。                                 |
+| logicaloperator | text      | 过滤条件的逻辑字符串。                                   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY_PRIVILEGES.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY_PRIVILEGES.md
new file mode 100644
index 0000000000000000000000000000000000000000..f2eda33f4a5ff828553044d9c8ca3d8a892f6d4f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY_PRIVILEGES.md
@@ -0,0 +1,20 @@
+---
+title: GS_AUDITING_POLICY_PRIVILEGES
+summary: GS_AUDITING_POLICY_PRIVILEGES
+author: Guo Huan
+date: 2021-06-07
+---
+
+# GS_AUDITING_POLICY_PRIVILEGES
+
+GS_AUDITING_POLICY_PRIVILEGES系统表记录统一审计DDL数据库相关操作信息，每条记录对应一个设计策略。需要有系统管理员或安全策略管理员权限才可以访问此系统表。
+
+**表 1** GS_AUDITING_POLICY_PRIVI字段
+
+| 名称          | 类型      | 描述                                                        |
+| :------------ | :-------- | :---------------------------------------------------------- |
+| oid           | oid       | 行标识符（隐藏属性，必须明确选择）。                        |
+| privilegetype | name      | DDL数据库操作相关类型。例如CREATE、ALTER、DROP等。          |
+| labelname     | name      | 资源标签名称。对应系统表gs_auditing_policy中的polname字段。 |
+| policyoid     | oid       | 对应审计策略系统表GS_AUDITING_POLICY中的oid。               |
+| modifydate    | timestamp | 创建或修改的最新时间戳。                                    |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_CLIENT_GLOBAL_KEYS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_CLIENT_GLOBAL_KEYS.md
new file mode 100644
index 0000000000000000000000000000000000000000..92f79571a31d365276e56934d591c042e98b591e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_CLIENT_GLOBAL_KEYS.md
@@ -0,0 +1,21 @@
+---
+title: GS_CLIENT_GLOBAL_KEYS
+summary: GS_CLIENT_GLOBAL_KEYS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_CLIENT_GLOBAL_KEYS
+
+GS_CLIENT_GLOBAL_KEYS系统表记录密态等值特性中客户端加密主密钥相关信息，每条记录对应一个客户端加密主密钥。
+
+**表 1** GS_CLIENT_GLOBAL_KEYS字段
+
+| 名称            | 类型      | 描述                                         |
+| :-------------- | :-------- | :------------------------------------------- |
+| oid             | oid       | 行标识符（隐含字段）。                       |
+| global_key_name | name      | 客户端加密主密钥（cmk）名称。                |
+| key_namespace   | oid       | 包含此客户端加密主密钥（cmk）的命名空间OID。 |
+| key_owner       | oid       | 客户端加密主密钥（cmk）的所有者。            |
+| key_acl         | aclitem[] | 创建该密钥时所拥有的访问权限。               |
+| create_date     | timestamp | 创建密钥的时间。                             |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_CLIENT_GLOBAL_KEYS_ARGS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_CLIENT_GLOBAL_KEYS_ARGS.md
new file mode 100644
index 0000000000000000000000000000000000000000..677d52c6a75d6cd71ea0dd3b71145c83266ee0d3
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_CLIENT_GLOBAL_KEYS_ARGS.md
@@ -0,0 +1,20 @@
+---
+title: GS_CLIENT_GLOBAL_KEYS_ARGS
+summary: GS_CLIENT_GLOBAL_KEYS_ARGS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_CLIENT_GLOBAL_KEYS_ARGS
+
+GS_CLIENT_GLOBAL_KEYS_ARGS系统表记录密态等值特性中客户端加密主密钥相关元数据信息，每条记录对应客户端加密主密钥的一个键值对信息。
+
+**表 1** GS_CLIENT_GLOBAL_KEYS_ARGS字段
+
+| 名称          | 类型  | 描述                                            |
+| :------------ | :---- | :---------------------------------------------- |
+| oid           | oid   | 行标识符（隐含字段）。                          |
+| global_key_id | oid   | 客户端加密主密钥（cmk）oid。                    |
+| function_name | name  | 值为encryption。                                |
+| key           | name  | 客户端加密主密钥（cmk）的元数据信息对应的名称。 |
+| value         | bytea | 客户端加密主密钥（cmk）的元数据信息名称的值。   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_COLUMN_KEYS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_COLUMN_KEYS.md
new file mode 100644
index 0000000000000000000000000000000000000000..fa6cef82d9bb868f94ed47816ad1239c2c565078
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_COLUMN_KEYS.md
@@ -0,0 +1,23 @@
+---
+title: GS_COLUMN_KEYS
+summary: GS_COLUMN_KEYS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_COLUMN_KEYS
+
+GS_COLUMN_KEYS系统表记录密态等值特性中列加密密钥相关信息，每条记录对应一个列加密密钥。
+
+**表 1** GS_COLUMN_KEYS字段
+
+| 名称                      | 类型      | 描述                                        |
+| :------------------------ | :-------- | :------------------------------------------ |
+| oid                       | oid       | 行标识符（隐含字段）。                      |
+| column_key_name           | name      | 列加密密钥（cek）名称。                     |
+| column_key_distributed_id | oid       | 根据加密密钥（cek）全称域名hash值得到的id。 |
+| global_key_id             | oid       | 外键。客户端加密主密钥（cmk）的OID。        |
+| key_namespace             | oid       | 包含此列加密密钥（cek）的命名空间OID。      |
+| key_owner                 | oid       | 列加密密钥（cek）的所有者。                 |
+| create_date               | timestamp | 创建列加密密钥的时间。                      |
+| key_acl                   | aclitem[] | 创建该列加密密钥时所拥有的访问权限。        |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_COLUMN_KEYS_ARGS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_COLUMN_KEYS_ARGS.md
new file mode 100644
index 0000000000000000000000000000000000000000..d53376341c19d948d1aa26af716b1a9f74102fe1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_COLUMN_KEYS_ARGS.md
@@ -0,0 +1,20 @@
+---
+title: GS_COLUMN_KEYS_ARGS
+summary: GS_COLUMN_KEYS_ARGS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_COLUMN_KEYS_ARGS
+
+GS_COLUMN_KEYS_ARGS系统表记录密态等值特性中客户端加密主密钥相关元数据信息，每条记录对应客户端加密主密钥的一个键值对信息。
+
+**表 1** GS_COLUMN_KEYS_ARGS字段
+
+| 名称          | 类型  | 描述                                      |
+| :------------ | :---- | :---------------------------------------- |
+| oid           | oid   | 行标识符（隐含字段）。                    |
+| column_key_id | oid   | 列加密密钥（cek）oid。                    |
+| function_name | name  | 值为encryption。                          |
+| key           | name  | 列加密密钥（cek）的元数据信息对应的名称。 |
+| value         | bytea | 列加密密钥（cek）的元数据信息名称的值。   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_ENCRYPTED_COLUMNS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_ENCRYPTED_COLUMNS.md
new file mode 100644
index 0000000000000000000000000000000000000000..657bd910b6726b65d62d3e35e5b93180979a3d2d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_ENCRYPTED_COLUMNS.md
@@ -0,0 +1,23 @@
+---
+title: GS_ENCRYPTED_COLUMNS
+summary: GS_ENCRYPTED_COLUMNS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_ENCRYPTED_COLUMNS
+
+GS_ENCRYPTED_COLUMNS系统表记录密态等值特性中表的加密列相关信息，每条记录对应一条加密列信息。
+
+**表 1** GS_ENCRYPTED_COLUMNS字段
+
+| 名称                   | 类型      | 描述                                                         |
+| :--------------------- | :-------- | :----------------------------------------------------------- |
+| oid                    | oid       | 行标识符（隐含字段）。                                       |
+| rel_id                 | oid       | 表的OID。                                                    |
+| column_name            | name      | 加密列的名称。                                               |
+| column_key_id          | oid       | 外键，列加密密钥的OID。                                      |
+| encryption_type        | int1      | 加密类型。取值为2（DETERMINISTIC）或者1（RANDOMIZED）。      |
+| data_type_original_oid | oid       | 加密列的原始数据类型id，参考系统表[PG_TYPE](PG_TYPE)中的oid。 |
+| data_type_original_mod | int4      | 加密列的原始数据类型修饰符，参考系统表[PG_ATTRIBUTE](PG_ATTRIBUTE)中的atttypmod。其值对那些不需要的类型data_type_original_mod通常为-1。 |
+| create_date            | timestamp | 创建加密列的时间。                                           |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_ENCRYPTED_PROC.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_ENCRYPTED_PROC.md
new file mode 100644
index 0000000000000000000000000000000000000000..a5ee0993509538f6156e0ba5a8a6293507a5140e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_ENCRYPTED_PROC.md
@@ -0,0 +1,20 @@
+---
+title: GS_ENCRYPTED_PROC
+summary: GS_ENCRYPTED_PROC
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# GS_ENCRYPTED_PROC
+
+GS_ENCRYPTED_PROC系统表提供了密态函数/存储过程函数参数、返回值的原始数据类型，加密列等信息。
+
+**表 1** GS_ENCRYPTED_PROC字段
+
+| 名称                | 类型      | 描述                                                         |
+| :------------------ | :-------- | :----------------------------------------------------------- |
+| oid                 | oid       | 行标识符（隐含字段）。                                       |
+| func_id             | oid       | function的oid，对应pg_proc系统表中的oid行标识符。            |
+| prorettype_orig     | int4      | 返回值的原始数据类型。                                       |
+| proargcachedcol     | oidvector | 函数INPUT参数对应的加密列的oid，对应gs_encrypted_columns系统表中的oid行标识符。 |
+| proallargtypes_orig | oid[]     | 所有函数参数的原始数据类型。                                 |
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_GLOBAL_CHAIN.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_GLOBAL_CHAIN.md
new file mode 100644
index 0000000000000000000000000000000000000000..a894dfbe32a8157cf45124918b3c0943a1afb148
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_GLOBAL_CHAIN.md
@@ -0,0 +1,26 @@
+---
+title: GS_GLOBAL_CHAIN
+summary: GS_GLOBAL_CHAIN
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# GS_GLOBAL_CHAIN
+
+GS_GLOBAL_CHAIN系统表记录用户对防篡改用户表的修改操作信息，每条记录对应一次表级修改操作。具有审计管理员权限的用户可以查询此系统表，所有用户均不允许修改此系统表。
+
+**表 1** GS_GLOBAL_CHAIN字段
+
+| 名称       | 类型                     | 描述                                                         |
+| :--------- | :----------------------- | :----------------------------------------------------------- |
+| oid        | oid                      | 行标识符（隐藏属性，必须明确选择）。                         |
+| blocknum   | bigint                   | 区块号，当前用户操作在账本中记录的序号。                     |
+| dbname     | name                     | 数据库名称。被修改的防篡改用户表所属的database。             |
+| username   | name                     | 用户名，执行用户表修改操作的用户名。                         |
+| starttime  | timestamp with time zone | 用户操作执行的最新时间戳。                                   |
+| relid      | oid                      | 用户表Oid，被修改的防篡改用户表Oid。                         |
+| relnsp     | name                     | 模式Oid，被修改的防篡改用户表所属的namesapce oid。           |
+| relname    | name                     | 用户表名，被修改的防篡改用户表名。                           |
+| relhash    | hash16                   | 当前操作产生的表级别hash变化量。                             |
+| globalhash | hash32                   | 全局摘要，由当前行信息与前一行globalhash计算而来，将整个表串联起来，用于验证GS_GLOBAL_CHAIN数据完整性。 |
+| txcommand  | text                     | 被记录操作的SQL语句。                                        |
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MASKING_POLICY.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MASKING_POLICY.md
new file mode 100644
index 0000000000000000000000000000000000000000..a9206a2feffd63bf35ba124e65791f3bc252e8b0
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MASKING_POLICY.md
@@ -0,0 +1,20 @@
+---
+title: GS_MASKING_POLICY
+summary: GS_MASKING_POLICY
+author: Guo Huan
+date: 2021-06-07
+---
+
+# GS_MASKING_POLICY
+
+GS_MASKING_POLICY系统表记录动态数据脱敏策略的主体信息，每条记录对应一个脱敏策略。需要有系统管理员或安全策略管理员权限才可以访问此系统表。
+
+**表 1** GS_MASKING_POLICY表字段
+
+| 名称        | 类型      | 描述                                                         |
+| :---------- | :-------- | :----------------------------------------------------------- |
+| oid         | oid       | 行标识符（隐藏属性，必须明确选择）。                         |
+| polname     | name      | 策略名称，唯一不可重复。                                     |
+| polcomments | name      | 策略描述字段，记录策略相关的描述信息，通过COMMENTS关键字体现。 |
+| modifydate  | timestamp | 策略创建或修改的最新时间戳。                                 |
+| polenabled  | Boolean   | 策略启动开关。                                               |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MASKING_POLICY_ACTIONS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MASKING_POLICY_ACTIONS.md
new file mode 100644
index 0000000000000000000000000000000000000000..4915abd5b46d96e435f3eadcd5fe633a1dd390a2
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MASKING_POLICY_ACTIONS.md
@@ -0,0 +1,21 @@
+---
+title: GS_MASKING_POLICY_ACTIONS
+summary: GS_MASKING_POLICY_ACTIONS
+author: Guo Huan
+date: 2021-06-07
+---
+
+# GS_MASKING_POLICY_ACTIONS
+
+GS_MASKING_POLICY_ACTIONS系统表记录动态数据脱敏策略中相应的脱敏策略包含的脱敏行为，一个脱敏策略对应着该表的一行或多行记录。需要有系统管理员或安全策略管理员权限才可以访问此系统表。
+
+**表 1** GS_MASKING_POLICY_ACTIONS表字段
+
+| 名称         | 类型      | 描述                                                         |
+| :----------- | :-------- | :----------------------------------------------------------- |
+| oid          | oid       | 行标识符（隐藏属性，必须明确选择）。                         |
+| actiontype   | name      | 脱敏函数，标识脱敏策略使用的脱敏函数。                       |
+| actparams    | name      | 向脱敏函数中传递的参数信息。                                 |
+| actlabelname | name      | 被脱敏的label名称。                                          |
+| policyoid    | oid       | 该条记录所属的脱敏策略oid，对应[GS_MASKING_POLICY](GS_MASKING_POLICY)中的oid。 |
+| modifydate   | timestamp | 该条记录创建或修改的最新时间戳。                             |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MASKING_POLICY_FILTERS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MASKING_POLICY_FILTERS.md
new file mode 100644
index 0000000000000000000000000000000000000000..dcc9bf0477c6c6a13ea8538a5e18ae2ab14baaaa
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MASKING_POLICY_FILTERS.md
@@ -0,0 +1,21 @@
+---
+title: GS_MASKING_POLICY_FILTERS
+summary: GS_MASKING_POLICY_FILTERS
+author: Guo Huan
+date: 2021-06-07
+---
+
+# GS_MASKING_POLICY_FILTERS
+
+GS_MASKING_POLICY_FILTERS系统表记录动态数据脱敏策略对应的用户过滤条件，当用户条件满足FILTER条件时，对应的脱敏策略才会生效。需要有系统管理员或安全策略管理员权限才可以访问此系统表。
+
+**表 1** GS_MASKING_POLICY_FILTERS表字段
+
+| 名称            | 类型      | 描述                                                         |
+| :-------------- | :-------- | :----------------------------------------------------------- |
+| oid             | oid       | 行标识符（隐藏属性，必须明确选择）。                         |
+| filtertype      | name      | 过滤类型。目前值仅为logical_expr。                           |
+| filterlabelname | name      | 过滤范围。目前值仅为logical_expr。                           |
+| policyoid       | oid       | 该条用户过滤条件所属的脱敏策略oid，对应[GS_MASKING_POLICY](GS_MASKING_POLICY)中的oid。 |
+| modifydate      | timestamp | 该条用户过滤条件创建或修改的最新时间戳。                     |
+| logicaloperator | text      | 过滤条件的波兰表达式。                                       |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MATVIEW.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MATVIEW.md
new file mode 100644
index 0000000000000000000000000000000000000000..ad6c573d18d6cf09b0729d81a328b29149277764
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MATVIEW.md
@@ -0,0 +1,21 @@
+---
+title: GS_MATVIEW
+summary: GS_MATVIEW
+author: Guo Huan
+date: 2021-06-07
+---
+
+# GS_MATVIEW
+
+GS_MATVIEW系统表提供了关于数据库中每一个物化视图的信息。
+
+**表 1** GS_MATVIEW字段
+
+| 名称        | 类型      | 描述          |
+| :---------- | :-------- | :---------- |
+| oid         | oid       | 行标识符（隐藏属性，必须明确选择）。                         |
+| matviewid   | oid       | 物化视图的oid。                                              |
+| mapid       | oid       | 物化视图map表的oid，map表为物化视图关联表，与物化视图一一对应。全量物化视图不存在对应的map表，该字段为0。 |
+| ivm         | boolean   | 物化视图的类型，t为增量物化视图，f为全量物化视图。           |
+| needrefresh | boolean   | 保留字段。                                                   |
+| refreshtime | timestamp | 物化视图上一次刷新时间，若未刷新则为null。仅对增量物化视图维护该字段，全量物化视图为null。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MATVIEW_DEPENDENCY.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MATVIEW_DEPENDENCY.md
new file mode 100644
index 0000000000000000000000000000000000000000..f33708d6b19950ac274557f27e8dbd31529ab50f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MATVIEW_DEPENDENCY.md
@@ -0,0 +1,20 @@
+---
+title: GS_MATVIEW_DEPENDENCY
+summary: GS_MATVIEW_DEPENDENCY
+author: Guo Huan
+date: 2021-06-07
+---
+
+# GS_MATVIEW_DEPENDENCY
+
+GS_MATVIEW_DEPENDENCY系统表提供了关于数据库中每一个物化视图的基表和mlog表的关联信息。
+
+**表 1** GS_MATVIEW_DEPENDENCY字段
+
+| 名称      | 类型 | 描述                                                         |
+| :-------- | :--- | :----------------------------------------------------------- |
+| oid       | oid  | 行标识符（隐藏属性，必须明确选择）。                         |
+| matviewid | oid  | 物化视图的oid。                                              |
+| relid     | oid  | 物化视图基表的oid。                                          |
+| mlogid    | oid  | 物化视图mlog表的oid，mlog表为物化视图日志表，与基表一一对应。 |
+| mxmin     | int4 | 保留字段。                                                   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_OPT_MODEL.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_OPT_MODEL.md
new file mode 100644
index 0000000000000000000000000000000000000000..948955c7b83d34c00c0719a27543ac8a17d7ee3e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_OPT_MODEL.md
@@ -0,0 +1,33 @@
+---
+title: GS_OPT_MODEL
+summary: GS_OPT_MODEL
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_OPT_MODEL
+
+GS_OPT_MODEL是启用AiEngine执行计划时间预测功能时的数据表，记录机器学习模型的配置、训练结果、功能、对应系统函数、训练历史等相关信息。
+
+**表 1** GS_OPT_MODEL字段
+
+| 名称          | 类型     | 描述                                                         |
+| :------------ | :------- | :----------------------------------------------------------- |
+| oid           | oid      | 数据库对象id。                                               |
+| template_name | name     | 机器学习模型的模板名，决定训练和预测调用的函数接口，目前只实现了rlstm，方便后续扩展。 |
+| model_name    | name     | 模型的实例名，每个模型对应aiEngine在线学习进程中的一套参数、训练日志、模型系数。此列需为unique。 |
+| datname       | name     | 该模型所服务的database名，每个模型只针对单个database。此参数决定训练时所使用的数据。 |
+| ip            | name     | AiEngine端所部署的host ip地址。                              |
+| port          | integer  | AiEngine端所监听的端口号。                                   |
+| max_epoch     | integer  | 模型每次训练的迭代次数上限。                                 |
+| learning_rate | real     | 模型训练的学习速率，推荐缺省值1。                            |
+| dim_red       | real     | 模型特征维度降维系数。                                       |
+| hidden_units  | integer  | 模型隐藏层神经元个数。如果训练发现模型长期无法收敛，可以适量提升本参数。 |
+| batch_size    | integer  | 模型每次迭代时一个batch的大小，尽量设为大于等于训练数据总量的值，加快模型的收敛速度。 |
+| feature_size  | integer  | [不需设置] 模型特征的长度，用于触发重新训练，模型训练后该参数自动更新。 |
+| available     | boolean  | [不需设置]标识模型是否收敛。                                 |
+| Is_training   | boolean  | [不需设置]标识模型是否正在训练。                             |
+| label         | "char"[] | 模型的目标任务: <br/>- S: startup time<br/>- T: total time<br/>- R: rows<br/>- M: peak memory<br/>目前受模型性能限制，推荐{S, T}或{R}。 |
+| max           | bigint[] | [不需设置]标识模型各任务标签的最大值，用于触发重新训练。     |
+| acc           | real[]   | [不需设置]标识模型各任务的准确率。                           |
+| description   | text     | 模型注释。                                                   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_POLICY_LABEL.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_POLICY_LABEL.md
new file mode 100644
index 0000000000000000000000000000000000000000..df53824e6cddb26b9eb822f812a214c4e4f45beb
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_POLICY_LABEL.md
@@ -0,0 +1,24 @@
+---
+title: GS_POLICY_LABEL
+summary: GS_POLICY_LABEL
+author: Guo Huan
+date: 2021-06-07
+---
+
+# GS_POLICY_LABEL
+
+GS_POLICY_LABEL系统表记录资源标签配置信息，一个资源标签对应着一条或多条记录，每条记录标记了数据库资源所属的资源标签。需要有系统管理员或安全策略管理员权限才可以访问此系统表。
+
+FQDN（Fully Qualified Domain Name）标识了数据库资源所属的绝对路径。
+
+**表 1** GS_POLICY_LABEL表字段
+
+| 名称          | 类型 | 描述                                                         |
+| :------------ | :--- | :----------------------------------------------------------- |
+| oid           | oid  | 行标识符（隐藏属性，必须明确选择）。                         |
+| labelname     | name | 资源标签名称。                                               |
+| labeltype     | name | 资源标签类型，目前仅为RESOURCE。                             |
+| fqdnnamespace | oid  | 被标识的数据库资源所属的namespace oid。                      |
+| fqdnid        | oid  | 被标识的数据库资源的oid，若数据库资源为列，则该列为所属表的oid。 |
+| relcolumn     | name | 列名，若被标识的数据库资源为列，该列指出列名，否则该列为空。 |
+| fqdntype      | name | 被标识的数据库资源的类型名称，例如：schema，table，column，view等。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_RECYCLEBIN.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_RECYCLEBIN.md
new file mode 100644
index 0000000000000000000000000000000000000000..507267c20b00ddc2e11a614d0a2f68526f4a9025
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_RECYCLEBIN.md
@@ -0,0 +1,35 @@
+---
+title: GS_RECYCLEBIN
+summary: GS_RECYCLEBIN
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# GS_RECYCLEBIN
+
+gs_recyclebin描述了回收站对象的详细信息。
+
+**表 1** gs_recyclebin字段
+
+| 名称           | 类型        | 描述                                                         |
+| :------------- | :---------- | :----------------------------------------------------------- |
+| oid            | oid         | 系统列。                                                     |
+| rcybaseid      | oid         | 基表对象id，引用gs_recyclebin.oid。                          |
+| rcydbid        | oid         | 当前对象所属数据库oid。                                      |
+| rcyrelid       | oid         | 当前对象oid。                                                |
+| rcyname        | name        | 回收站对象名称，格式`BIN$unique_id$oid$0`，其中unique_id为最多16字符唯一标识，oid为对象标识符。 |
+| rcyoriginname  | name        | 原始对象名称。                                               |
+| rcyoperation   | “char”      | 操作类型。<br />- d表示drop<br />- t表示truncate             |
+| rcytype        | int         | 对象类型。<br />- 0表示table。<br />- 1表示index。<br />- 2表示toast table。<br />- 3表示toast index。<br />- 4表示sequence，指serial、bigserial类型自动关联的序列对象。 |
+| rcyrecyclecsn  | bigint      | 对象drop、truncate时csn。                                    |
+| rcyrecycletime | timestamptz | 对象drop、truncate时间。                                     |
+| rcycreatecsn   | bigint      | 对象创建时csn。                                              |
+| rcychangecsn   | bigint      | 对象定义改变的csn。                                          |
+| rcynamespace   | oid         | 包含这个关系的名字空间的OID。                                |
+| rcyowner       | oid         | 关系所有者。                                                 |
+| rcytablespace  | oid         | 这个关系存储所在的表空间。如果为0，则意味着使用该数据库的缺省表空间。如果关系在磁盘上没有文件，则这个字段没有什么意义。 |
+| rcyrelfilenode | oid         | 回收站对象在磁盘上的文件的名称，如果没有则为0，用于TRUNCATE对象恢复时纹理文件还原。 |
+| rcycanrestore  | bool        | 是否可以被单独闪回。                                         |
+| rcycanpurge    | bool        | 是否可以被单独purge。                                        |
+| rcyfrozenxid   | xid32       | 该表中所有在这个之前的事务ID已经被一个固定的（“frozen”）事务ID替换。 |
+| rcyfrozenxid64 | xid         | 该表中所有在这个之前的事务ID已经被一个固定的（“frozen”）事务ID替换。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_TXN_SNAPSHOT.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_TXN_SNAPSHOT.md
new file mode 100644
index 0000000000000000000000000000000000000000..1ac7dd12bd0dc02482986468d8c0d9ce70524fd2
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_TXN_SNAPSHOT.md
@@ -0,0 +1,19 @@
+---
+title: GS_TXN_SNAPSHOT
+summary: GS_TXN_SNAPSHOT
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# GS_TXN_SNAPSHOT
+
+GS_TXN_SNAPSHOT是“时间戳-CSN”映射表，周期性采样，并维护适当的时间范围，用于估算范围内的时间戳对应的CSN值。
+
+**表 1** GS_TXN_SNAPSHOT字段
+
+| 名称        | 类型        | 描述           |
+| :---------- | :---------- | :------------- |
+| snptime     | timestamptz | 快照捕获时间   |
+| snpxmin     | bigint      | 快照xmin       |
+| snpcsn      | bigint      | 快照csn        |
+| snpsnapshot | TEXT        | 快照序列化文本 |
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_EC_OPERATOR_INFO.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_EC_OPERATOR_INFO.md
new file mode 100644
index 0000000000000000000000000000000000000000..44fbcedef0400870b810736e15999f336d63711b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_EC_OPERATOR_INFO.md
@@ -0,0 +1,29 @@
+---
+title: GS_WLM_EC_OPERATOR_INFO
+summary: GS_WLM_EC_OPERATOR_INFO
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_WLM_EC_OPERATOR_INFO
+
+GS_WLM_EC_OPERATOR_INFO系统表存储执行EC（Extension Connector）作业结束后的算子相关的记录。当设置GUC参数enable_resource_record为on时，系统会每3分钟将GS_WLM_EC_OPERATOR_HISTORY中的记录导入此系统表，开启此功能会占用系统存储空间并对性能有一定影响。查询该系统表需要sysadmin权限。
+
+**表 1** GS_WLM_EC_OPERATOR_INFO的字段
+
+| 名称                | 类型                     | 描述                          |
+| :------------------ | :----------------------- | :-------------------------- |
+| queryid             | bigint                   | EC语句执行使用的内部query_id。                               |
+| plan_node_id        | integer                  | EC算子对应的执行计划的plan node id。                         |
+| start_time          | timestamp with time zone | EC算子处理第一条数据的开始时间。                             |
+| duration            | bigint                   | EC算子到结束时候总的执行时间（ms）。                         |
+| tuple_processed     | bigint                   | EC算子返回的元素个数。                                       |
+| min_peak_memory     | integer                  | EC算子在所有DN上的最小内存峰值（MB）。                       |
+| max_peak_memory     | integer                  | EC算子在所有DN上的最大内存峰值（MB）。                       |
+| average_peak_memory | integer                  | EC算子在所有DN上的平均内存峰值（MB）。                       |
+| ec_status           | text                     | EC作业的执行状态。                                           |
+| ec_execute_datanode | text                     | 执行EC作业的DN名称。                                         |
+| ec_dsn              | text                     | EC作业所使用的DSN。                                          |
+| ec_username         | text                     | EC作业访问远端数据库实例的USERNAME（远端数据库实例为SPARK类型时该值为空）。 |
+| ec_query            | text                     | EC作业发送给远端数据库实例执行的语句。                       |
+| ec_libodbc_type     | text                     | EC作业使用的unixODBC驱动类型。                               |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_INSTANCE_HISTORY.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_INSTANCE_HISTORY.md
new file mode 100644
index 0000000000000000000000000000000000000000..79e7639a61f0482c61f638b35101fedd3e197ef2
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_INSTANCE_HISTORY.md
@@ -0,0 +1,30 @@
+---
+title: GS_WLM_INSTANCE_HISTORY
+summary: GS_WLM_INSTANCE_HISTORY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_WLM_INSTANCE_HISTORY
+
+GS_WLM_INSTANCE_HISTORY系统表存储与实例（数据库主节点或数据库节点）相关的资源使用相关信息。该系统表里每条记录都是对应时间点某实例资源使用情况，包括: 内存、CPU核数、磁盘IO、进程物理IO和进程逻辑IO信息。查询该系统表需要sysadmin权限，且仅在数据库postgres下面查询时有数据。
+
+**表 1** GS_WLM_INSTANCE_HISTORY字段
+
+| 名称          | 类型                     | 描述       |
+| :------------ | :----------------------- | :--------------------------- |
+| instancename  | text                     | 实例名称。       |
+| timestamp     | timestamp with time zone | 时间戳。   |
+| used_cpu      | int                      | 实例使用CPU所占用的百分比。         |
+| free_mem      | int                      | 实例未使用的内存大小，单位MB。      |
+| used_mem      | int                      | 实例已使用的内存大小，单位MB。      |
+| io_await      | real                     | 实例所使用磁盘的io_wait值（10秒均值）。                      |
+| io_util       | real                     | 实例所使用磁盘的io_util值（10秒均值）。                      |
+| disk_read     | real                     | 实例所使用磁盘的读速率（10秒均值），单位KB/s。               |
+| disk_write    | real                     | 实例所使用磁盘的写速率（10秒均值），单位KB/s。               |
+| process_read  | bigint                   | 实例对应进程从磁盘读数据的读速率（不包括从磁盘pagecache中读取的字节数，10秒均值），单位KB/s。 |
+| process_write | bigint                   | 实例对应进程向磁盘写数据的写速率（不包括向磁盘pagecache中写入的字节数，10秒均值），单位KB/s。 |
+| logical_read  | bigint                   | 数据库主节点实例: 不统计。数据库节点实例: 该实例在本次统计间隙（10秒）内逻辑读字节速率，单位KB/s。 |
+| logical_write | bigint                   | 数据库主节点实例: 不统计。数据库节点实例: 该实例在本次统计间隙（10秒）内逻辑写字节速率，单位KB/s。 |
+| read_counts   | bigint                   | 数据库主节点实例: 不统计。数据库节点实例: 该实例在本次统计间隙（10秒）内逻辑读操作次数之和，单位次。 |
+| write_counts  | bigint                   | 数据库主节点实例: 不统计。数据库节点实例: 该实例在本次统计间隙（10秒）内逻辑写操作次数之和，单位次。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_OPERATOR_INFO.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_OPERATOR_INFO.md
new file mode 100644
index 0000000000000000000000000000000000000000..a2bb2358afcf38a6994fb4e6723cfa3d942b15d3
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_OPERATOR_INFO.md
@@ -0,0 +1,37 @@
+---
+title: GS_WLM_OPERATOR_INFO
+summary: GS_WLM_OPERATOR_INFO
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_WLM_OPERATOR_INFO
+
+GS_WLM_OPERATOR_INFO系统表显示执行作业结束后的算子相关的记录。此数据是从内核中转储到系统表中的数据。查询该系统表需要sysadmin权限，且仅在数据库postgres下面查询时有数据。
+
+**表 1** GS_WLM_OPERATOR_INFO的字段<a id="GS_WLM_OPERATOR_INFO的字段"> </a>
+
+| 名称                | 类型                     | 描述                        |
+| :------------------ | :----------------------- | :------------------------- |
+| queryid             | bigint                   | 语句执行使用的内部query_id。                 |
+| pid                 | bigint                   | 后端线程id。                                 |
+| plan_node_id        | integer                  | 查询对应的执行计划的plan node id。           |
+| plan_node_name      | text                     | 对应于plan_node_id的算子的名称。             |
+| start_time          | timestamp with time zone | 该算子处理第一条数据的开始时间。             |
+| duration            | bigint                   | 该算子到结束时候总的执行时间（ms）。        |
+| query_dop           | integer                  | 当前算子执行时的并行度。                     |
+| estimated_rows      | bigint                   | 优化器估算的行数信息。                       |
+| tuple_processed     | bigint                   | 当前算子返回的元素个数。                     |
+| min_peak_memory     | integer                  | 当前算子在数据库节点上的最小内存峰值（MB）。 |
+| max_peak_memory     | integer                  | 当前算子在数据库节点上的最大内存峰值（MB）。 |
+| average_peak_memory | integer                  | 当前算子在数据库节点平均内存峰值（MB）。        |
+| memory_skew_percent | integer                  | 当前算子在数据库节点间的内存使用倾斜率。              |
+| min_spill_size      | integer                  | 若发生下盘，数据库节点盘的最小数据量（MB），默认为0。        |
+| max_spill_size      | integer                  | 若发生下盘，数据库节点上下盘的最大数据量（MB），默认为0。    |
+| average_spill_size  | integer                  | 若发生下盘，数据库节点盘的平均数据量（MB），默认为0。        |
+| spill_skew_percent  | integer                  | 若发生下盘，数据库节点间下盘倾斜率。                         |
+| min_cpu_time        | bigint                   | 该算子在数据库节点最小执行时间（ms）。                       |
+| max_cpu_time        | bigint                   | 该算子在数据库节点上的最大执行时间（ms）。                   |
+| total_cpu_time      | bigint                   | 该算子在数据库节点上的总执行时间（ms）。                     |
+| cpu_skew_percent    | integer                  | 数据库节点间执行时间的倾斜率。                               |
+| warning             | text                     | 主要显示如下几类告警信息: <br/>- Sort/SetOp/HashAgg/HashJoin spill<br/>- Spill file size large than 256MB<br/>- Broadcast size large than 100MB<br/>- Early spill<br/>- Spill times is greater than 3<br/>- Spill on memory adaptive<br/>- Hash table conflict |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_PLAN_ENCODING_TABLE.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_PLAN_ENCODING_TABLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..84584e998b2edf64d3b2b61193ac653fb8fb5f74
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_PLAN_ENCODING_TABLE.md
@@ -0,0 +1,23 @@
+---
+title: GS_WLM_PLAN_ENCODING_TABLE
+summary: GS_WLM_PLAN_ENCODING_TABLE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_WLM_PLAN_ENCODING_TABLE
+
+GS_WLM_PLAN_ENCODING_TABLE系统表显示计划算子级的编码信息，为机器学习模型的提供包括startup time，total time，peak memory，rows等标签值的训练、预测集。
+
+**表 1** GS_WLM_PLAN_ENCODING_TABLE的字段
+
+| 名称           | 类型    | 描述                                       |
+| :------------- | :------ | :----------------------------------------- |
+| queryid        | bigint  | 语句执行使用的内部query_id。               |
+| plan_node_id   | integer | 查询对应的执行计划的plan node id。         |
+| parent_node_id | integer | 当前算子的父节点node id。                  |
+| startup_time   | bignit  | 该算子处理第一条数据的开始时间。           |
+| total_time     | bigint  | 该算子到结束时候总的执行时间(ms)。         |
+| rows           | bigint  | 当前算子执行的行数信息。                   |
+| peak_memory    | integer | 当前算子在数据库节点上的最大内存峰值(MB)。 |
+| encode         | text    | 当前计划算子的编码信息。                   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_PLAN_OPERATOR_INFO.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_PLAN_OPERATOR_INFO.md
new file mode 100644
index 0000000000000000000000000000000000000000..8f50dd989c7c5c9ca985c30a54d07643d3c6fec6
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_PLAN_OPERATOR_INFO.md
@@ -0,0 +1,32 @@
+---
+title: GS_WLM_PLAN_OPERATOR_INFO
+summary: GS_WLM_PLAN_OPERATOR_INFO
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_WLM_PLAN_OPERATOR_INFO
+
+GS_WLM_PLAN_OPERATOR_INFO系统表显示执行作业结束后计划算子级的相关的记录。此数据是从内核中转储到系统表中的数据。
+
+**表 1** GS_WLM_PLAN_OPERATOR_INFO的字段<a id="GS_WLM_PLAN_OPERATOR_INFO的字段"> </a>
+
+| 名称            | 类型    | 描述                                       |
+| :-------------- | :------ | :----------------------------------------- |
+| datname         | name    | 收集计划信息所在的database名。             |
+| queryid         | bigint  | 语句执行使用的内部query_id。               |
+| plan_node_id    | integer | 查询对应的执行计划的plan node id。         |
+| startup_time    | bigint  | 该算子处理第一条数据的开始时间。           |
+| total_time      | bigint  | 该算子到结束时候总的执行时间(ms)。         |
+| actual_rows     | bigint  | 实际执行的行数信息。                       |
+| max_peak_memory | integer | 当前算子在数据库节点上的最大内存峰值(MB)。 |
+| query_dop       | integer | 当前算子执行时的并行度。                   |
+| parent_node_id  | integer | 当前算子的父节点node id。                  |
+| left_child_id   | integer | 当前算子的左孩子节点node id。              |
+| right_child_id  | integer | 当前算子的右孩子节点node id。              |
+| operation       | text    | 当前算子进行的操作名称。                   |
+| orientation     | text    | 当前算子的对齐方式。                       |
+| strategy        | text    | 当前算子操作的实现方法。                   |
+| options         | text    | 当前算子操作的选择方式。                   |
+| condition       | text    | 当前算子操作的过滤条件。                   |
+| projection      | text    | 当前算子的映射关系。                       |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AGGREGATE.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AGGREGATE.md
new file mode 100644
index 0000000000000000000000000000000000000000..955f7c01ebb8fbff9c36842156e334ecf80c4106
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AGGREGATE.md
@@ -0,0 +1,25 @@
+---
+title: PG_AGGREGATE
+summary: PG_AGGREGATE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_AGGREGATE
+
+PG_AGGREGATE系统表存储与聚集函数有关的信息。PG_AGGREGATE里的每条记录都是一条pg_proc里面的记录的扩展。PG_PROC记录承载该聚集的名称、输入和输出数据类型，以及其它一些和普通函数类似的信息。
+
+**表 1** PG_AGGREGATE字段
+
+| 名称             | 类型     | 引用            | 描述                        |
+| :--------------- | :------- | :-------------- | :------------------------|
+| aggfnoid         | regproc  | PG_PROC.proname | 此聚集函数的PG_PROC proname。                                |
+| aggtransfn       | regproc  | PG_PROC.proname | 转换函数。                                                   |
+| aggcollectfn     | regproc  | PG_PROC.proname | 收集函数。                                                   |
+| aggfinalfn       | regproc  | PG_PROC.proname | 最终处理函数（如果没有则为零）。                             |
+| aggsortop        | oid      | PG_OPERATOR.oid | 关联排序操作符（如果没有则为零）。                           |
+| aggtranstype     | oid      | PG_TYPE.oid     | 此聚集函数的内部转换（状态）数据的数据类型。                 |
+| agginitval       | text     | -               | 转换状态的初始值。这是一个文本数据域，它包含初始值的外部字符串表现形式。如果数据域是null，则转换状态值从null开始。 |
+| agginitcollect   | text     | -               | 收集状态的初始值。这是一个文本数据域，它包含初始值的外部字符串表现形式。如果数据域是null，则收集状态值从null开始。 |
+| aggkind          | "char"   | -               | 此聚集函数类型: <br/>- 'n' : 表示Normal Agg<br/>- 'o' : 表示Ordered Set Agg |
+| aggnumdirectargs | smallint | -               | Ordered Set Agg类型聚集函数的直接参数（非聚集相关参数）数量。对Normal Agg类型聚集函数，该值为0。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AM.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AM.md
new file mode 100644
index 0000000000000000000000000000000000000000..ef9f13b5a79386ece7a49b3602a48094791fd49c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AM.md
@@ -0,0 +1,47 @@
+---
+title: PG_AM
+summary: PG_AM
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_AM
+
+PG_AM系统表存储有关索引访问方法的信息。系统支持的每种索引访问方法都有一行。
+
+**表 1** PG_AM字段
+
+| 名称            | 类型     | 引用            | 描述                |
+| :-------------- | :------- | :-------------- | :------------------ |
+| oid             | oid      | -               | 行标识符（隐藏属性，必须明确选择）。                         |
+| amname          | name     | -               | 访问方法的名称。                                             |
+| amstrategies    | smallint | -               | 访问方法的操作符策略个数，或者如果访问方法没有一个固定的操作符策略集则为0。 |
+| amsupport       | smallint | -               | 访问方法的支持过程个数。                                     |
+| amcanorder      | Boolean  | -               | 这种访问方式是否支持通过索引字段值的命令扫描排序。           |
+| amcanorderbyop  | Boolean  | -               | 这种访问方式是否支持通过索引字段上操作符的结果的命令扫描排序。 |
+| amcanbackward   | Boolean  | -               | 访问方式是否支持向后扫描。                                   |
+| amcanunique     | Boolean  | -               | 访问方式是否支持唯一索引。                                   |
+| amcanmulticol   | Boolean  | -               | 访问方式是否支持多字段索引。                                 |
+| amoptionalkey   | Boolean  | -               | 访问方式是否支持第一个索引字段上没有任何约束的扫描。         |
+| amsearcharray   | Boolean  | -               | 访问方式是否支持ScalarArrayOpExpr搜索。                      |
+| amsearchnulls   | Boolean  | -               | 访问方式是否支持IS NULL/NOT NULL搜索。                       |
+| amstorage       | Boolean  | -               | 允许索引存储的数据类型与列的数据类型是否不同。               |
+| amclusterable   | Boolean  | -               | 是否允许在一个这种类型的索引上聚簇。                         |
+| ampredlocks     | Boolean  | -               | 是否允许这种类型的一个索引管理细粒度的谓词锁定。             |
+| amkeytype       | oid      | PG_TYPE.oid     | 存储在索引里数据的类型，如果不是一个固定的类型则为0。        |
+| aminsert        | regproc  | PG_PROC.proname | "插入这个行"函数。                                           |
+| ambeginscan     | regproc  | PG_PROC.proname | "准备索引扫描" 函数。                                        |
+| amgettuple      | regproc  | PG_PROC.proname | "下一个有效行"函数，如果没有则为0。                          |
+| amgetbitmap     | regproc  | PG_PROC.proname | "抓取所有的有效行" 函数，如果没有则为0。                     |
+| amrescan        | regproc  | PG_PROC.proname | "（重新）开始索引扫描"函数。                                 |
+| amendscan       | regproc  | PG_PROC.proname | "索引扫描后清理" 函数。                                      |
+| ammarkpos       | regproc  | PG_PROC.proname | "标记当前扫描位置"函数。                                     |
+| amrestrpos      | regproc  | PG_PROC.proname | "恢复已标记的扫描位置"函数。                                 |
+| ammerge         | regproc  | PG_PROC.proname | "归并多个索引对象"函数。                                     |
+| ambuild         | regproc  | PG_PROC.proname | "建立新索引"函数。                                           |
+| ambuildempty    | regproc  | PG_PROC.proname | "建立空索引"函数。                                           |
+| ambulkdelete    | regproc  | PG_PROC.proname | 批量删除函数。                                               |
+| amvacuumcleanup | regproc  | PG_PROC.proname | VACUUM后的清理函数。                                         |
+| amcanreturn     | regproc  | PG_PROC.proname | 检查是否索引支持唯一索引扫描的函数，如果没有则为0。          |
+| amcostestimate  | regproc  | PG_PROC.proname | 估计一个索引扫描开销的函数。                                 |
+| amoptions       | regproc  | PG_PROC.proname | 为一个索引分析和确认reloptions的函数。                       |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AMOP.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AMOP.md
new file mode 100644
index 0000000000000000000000000000000000000000..8c137488c03bd84526657b17ea1439c031ba270d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AMOP.md
@@ -0,0 +1,28 @@
+---
+title: PG_AMOP
+summary: PG_AMOP
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_AMOP
+
+PG_AMOP系统表存储有关和访问方法操作符族关联的信息。如果一个操作符是一个操作符族中的成员，则在这个表中会占据一行。一个族成员是一个search操作符或一个ordering操作符。一个操作符可以在多个族中出现，但是不能在一个族中的多个搜索位置或多个排序位置中出现。
+
+**表 1** PG_AMOP字段
+
+| 名称           | 类型     | 引用            | 描述                   |
+| :------------- | :------- | :-------------- | :----------------------|
+| oid            | oid      | -               | 行标识符（隐藏属性，必须明确选择）。                         |
+| amopfamily     | oid      | PG_OPFAMILY.oid | 这个项的操作符族。                                           |
+| amoplefttype   | oid      | PG_TYPE.oid     | 操作符的左输入类型。可能取值及其描述见于pg_type.h。          |
+| amoprighttype  | oid      | PG_TYPE.oid     | 操作符的右输入类型。可能取值及其描述见于pg_type.h。          |
+| amopstrategy   | smallint | -               | 操作符策略数。                                               |
+| amoppurpose    | "char"   | -               | 操作符目的，s为搜索或o为排序。                               |
+| amopopr        | oid      | PG_OPERATOR.oid | 该操作符的OID。                                              |
+| amopmethod     | oid      | PG_AM.oid       | 索引访问方式操作符族。                                       |
+| amopsortfamily | oid      | PG_OPFAMILY.oid | 如果是一个排序操作符，则为这个项排序所依据的btree操作符族；如果是一个搜索操作符，则为0。 |
+
+search操作符表明这个操作符族的一个索引可以被搜索，找到所有满足WHERE indexed_column operator constant的行。显然，这样的操作符必须返回布尔值，并且它的左输入类型必须匹配索引的字段数据类型。
+
+ordering操作符表明这个操作符族的一个索引可以被扫描，返回以ORDER BY indexed_column operator constant顺序表示的行。这样的操作符可以返回任意可排序的数据类型，它的左输入类型也必须匹配索引的字段数据类型。 ORDER BY的确切的语义是由amopsortfamily字段指定的，该字段必须为操作符的返回类型引用一个btree操作符族。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AMPROC.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AMPROC.md
new file mode 100644
index 0000000000000000000000000000000000000000..a097f6102e0571f316006cf8f8b9d061c6c8e641
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AMPROC.md
@@ -0,0 +1,23 @@
+---
+title: PG_AMPROC
+summary: PG_AMPROC
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_AMPROC
+
+PG_AMPROC系统表存储有关与访问方法操作符族相关联的支持过程的信息。每个属于某个操作符族的支持过程都占有一行。
+
+**表 1** PG_AMPROC字段
+
+| 名称            | 类型     | 引用            | 描述                    |
+| :-------------- | :------- | :-------------- | :---------------------- |
+| oid             | oid      | -               | 行标识符（隐藏属性，必须明确选择）。                        |
+| amprocfamily    | oid      | PG_OPFAMILY.oid | 该项的操作符族。                                            |
+| amproclefttype  | oid      | PG_TYPE.oid     | 相关操作符的左输入数据类型。可能取值及其描述见于pg_type.h。 |
+| amprocrighttype | oid      | PG_TYPE.oid     | 相关操作符的右输入数据类型。可能取值及其描述见于pg_type.h。 |
+| amprocnum       | smallint | -               | 支持过程编号。                                              |
+| amproc          | regproc  | PG_PROC.proname | 过程的OID。                                                 |
+
+amproclefttype和amprocrighttype字段的习惯解释，标识一个特定支持过程支持的操作符的左和右输入类型。对于某些访问方式，匹配支持过程本身的输入数据类型，对其他的则不这样。有一个对索引的"缺省"支持过程的概念，amproclefttype和amprocrighttype都等于索引操作符类的opcintype。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_APP_WORKLOADGROUP_MAPPING.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_APP_WORKLOADGROUP_MAPPING.md
new file mode 100644
index 0000000000000000000000000000000000000000..8fd219f10a93921efcbe827772929cd6128b9dcd
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_APP_WORKLOADGROUP_MAPPING.md
@@ -0,0 +1,18 @@
+---
+title: PG_APP_WORKLOADGROUP_MAPPING
+summary: PG_APP_WORKLOADGROUP_MAPPING
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_APP_WORKLOADGROUP_MAPPING
+
+PG_APP_WORKLOADGROUP_MAPPING系统表提供了数据库负载映射组的信息。
+
+**表 1** PG_APP_WORKLOADGROUP_MAPPING字段
+
+| 名称            | 类型 | 描述                                 |
+| :-------------- | :--- | :----------------------------------- |
+| oid             | oid  | 行标识符（隐藏属性，必须明确选择）。 |
+| appname         | name | 应用名称。                           |
+| workload_gpname | name | 映射到的负载组名称。                 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_ATTRDEF.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_ATTRDEF.md
new file mode 100644
index 0000000000000000000000000000000000000000..db3aa6e006bc7642abd4ca5f11d121160643d05c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_ATTRDEF.md
@@ -0,0 +1,21 @@
+---
+title: PG_ATTRDEF
+summary: PG_ATTRDEF
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_ATTRDEF
+
+PG_ATTRDEF系统表存储列的默认值。
+
+**表 1** PG_ATTRDEF字段
+
+| 名称     | 类型         | 描述                    |
+| :------- | :----------- | :---------------------- |
+| oid      | oid          | 行标识符（隐藏属性，必须明确选择）。                         |
+| adrelid  | oid          | 该列的所属表。                                               |
+| adnum    | smallint     | 该列的数目。                                                 |
+| adbin    | pg_node_tree | 字段缺省值或生成表达式的内部表现形式。                       |
+| adsrc    | text         | 可读的缺省值或生成表达式的内部表现形式。                     |
+| adgencol | char         | 标识该列是否为生成列。取值为's'表示该列为生成列，取值为'\0'表示该列为普通列，默认值为'\0'。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_ATTRIBUTE.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_ATTRIBUTE.md
new file mode 100644
index 0000000000000000000000000000000000000000..dbe951f42ae1ff9461cac7707cce593c6086398e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_ATTRIBUTE.md
@@ -0,0 +1,39 @@
+---
+title: PG_ATTRIBUTE
+summary: PG_ATTRIBUTE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_ATTRIBUTE
+
+PG_ATTRIBUTE系统表存储关于表字段的信息。
+
+**表 1** PG_ATTRIBUTE字段
+
+| 名称          | 类型      | 描述                                                         |
+| :------------ | :-------- | :----------------------------------------------------------- |
+| attrelid      | oid       | 此字段所属表。                                               |
+| attname       | name      | 字段名。                                                     |
+| atttypid      | oid       | 字段类型。                                                   |
+| attstattarget | integer   | 控制ANALYZE为这个字段积累的统计细节的级别。<br/>- 零值表示不收集统计信息。<br/>- 负数表示使用系统缺省的统计对象。<br/>- 正数值的确切信息是和数据类型相关的。<br/>对于标量数据类型，ATTSTATTARGET既是要收集的"最常用数值"的目标数目，也是要创建的柱状图的目标数量。 |
+| attlen        | smallint  | 是本字段类型的pg_type.typlen的拷贝。                         |
+| attnum        | smallint  | 字段编号。                                                   |
+| attndims      | integer   | 如果该字段是数组，则是维数，否则是0 。                       |
+| attcacheoff   | integer   | 在磁盘上的时候总是-1 ，但是如果加载入内存中的行描述器中，它可能会被更新以缓冲在行中字段的偏移量。 |
+| atttypmod     | integer   | 记录创建新表时支持的类型特定的数据（比如一个varchar字段的最大长度）。它传递给类型相关的输入和长度转换函数当做第三个参数。其值对那些不需要ATTTYPMOD的类型通常为-1。 |
+| attbyval      | Boolean   | 这个字段类型的pg_type.typbyval的拷贝。                       |
+| attstorage    | "char"    | 这个字段类型的pg_type.typstorage的拷贝。                     |
+| attalign      | "char"    | 这个字段类型的pg_type.typalign的拷贝。                       |
+| attnotnull    | Boolean   | 这代表一个非空约束。可以改变这个字段以打开或者关闭这个约束。 |
+| atthasdef     | Boolean   | 这个字段有一个缺省值，此时它对应pg_attrdef表里实际定义此值的记录。 |
+| attisdropped  | Boolean   | 这个字段已经被删除了，不再有效。一个已经删除的字段物理上仍然存在表中，但会被分析器忽略，因此不能再通过SQL访问。 |
+| attislocal    | Boolean   | 这个字段是局部定义在关系中的。请注意一个字段可以同时是局部定义和继承的。 |
+| attcmprmode   | tinyint   | 对某一列指定压缩方式。压缩方式包括: <br/>- ATT_CMPR_NOCOMPRESS<br/>- ATT_CMPR_DELTA<br/>- ATT_CMPR_DICTIONARY<br/>- ATT_CMPR_PREFIX<br/>- ATT_CMPR_NUMSTR |
+| attinhcount   | integer   | 这个字段所拥有的直接父表的个数。如果一个字段的父表个数非零，则它就不能被删除或重命名。 |
+| attcollation  | oid       | 对此列定义的校对列。                                         |
+| attacl        | aclitem[] | 列级访问权限控制。                                           |
+| attoptions    | text[]    | 字段属性。目前支持以下两种属性：<br />n_distinct，表示该字段的distinct值数量（不包含字表）<br />n_distinct_inherited，表示该字段的distinct值数量（包含字表） |
+| attfdwoptions | text[]    | 外表字段属性。当前支持的dist_fdw、file_fdw、log_fdw未使用外表字段属性。 |
+| attinitdefval | bytea     | 存储了此列默认的值表达式。行存表的ADD COLUMN需要使用此字段。 |
+| attkvtype     | tinyint   | 对某一列指定key value类型。类型包括: <br/>0. ATT_KV_UNDEFINED : 默认<br/>1. ATT_KV_TAG : 维度<br/>2. ATT_KV_FIELD : 指标<br/>3. ATT_KV_TIMETAG : 时间列 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AUTHID.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AUTHID.md
new file mode 100644
index 0000000000000000000000000000000000000000..485e4e17ab4da8db690a93791a8a05b126f30d60
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AUTHID.md
@@ -0,0 +1,44 @@
+---
+title: PG_AUTHID
+summary: PG_AUTHID
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_AUTHID
+
+PG_AUTHID系统表存储有关数据库认证标识符（角色）的信息。角色把"用户"的概念包含在内。一个用户实际上就是一个rolcanlogin标志被设置的角色。任何角色（不管rolcanlogin设置与否）都能够把其他角色作为成员。
+
+MogDB中只有一份pg_authid，不是每个数据库有一份。需要有系统管理员权限才可以访问此系统表。
+
+**表 1** PG_AUTHID字段
+
+| 名称             | 类型                     | 描述                                                         |
+| :--------------- | :----------------------- | :----------------------------------------------------------- |
+| oid              | oid                      | 行标识符（隐藏属性，必须明确选择）。                         |
+| rolname          | name                     | 角色名称。                                                   |
+| rolsuper         | Boolean                  | 角色是否是拥有最高权限的初始系统管理员。<br />- t（true）：表示是。<br />- f（false）：表示不是。 |
+| rolinherit       | Boolean                  | 角色是否自动继承其所属角色的权限。<br />- t（true）：表示自动继承。<br />- f（false）：表示不自动继承。 |
+| rolcreaterole    | Boolean                  | 角色是否可以创建更多角色。<br />- t（true）：表示可以。<br />- f（false）：表示不可以。 |
+| rolcreatedb      | Boolean                  | 角色是否可以创建数据库。<br />- t（true）：表示可以。<br />- f（false）：表示不可以。 |
+| rolcatupdate     | Boolean                  | 角色是否可以直接更新系统表。只有usesysid=10的初始系统管理员拥有此权限。其他用户无法获得此权限。<br />- t（true）：表示可以。<br />- f（false）：表示不可以。 |
+| rolcanlogin      | Boolean                  | 角色是否可以登录，也就是说，这个角色可以给予会话认证标识符。<br />- t（true）：表示可以。<br />- f（false）：表示不可以。 |
+| rolreplication   | Boolean                  | 角色是否具有复制权限。<br />- t（true）：表示有。<br />- f（false）：表示没有。 |
+| rolauditadmin    | Boolean                  | 角色是否具有审计管理员权限：<br />- t（true）：表示有。<br />- f（false）：表示没有。 |
+| rolsystemadmin   | Boolean                  | 角色是否具有系统管理员权限：<br />- t（true）：表示有。<br />- f（false）：表示没有。 |
+| rolconnlimit     | integer                  | 对于可以登录的角色，限制其最大并发连接数量。<br/>-1 表示没有限制。 |
+| rolpassword      | text                     | 口令(可能是加密的)，如果没有口令，则为NULL。                 |
+| rolvalidbegin    | timestamp with time zone | 帐户的有效开始时间，如果没有开始时间，则为NULL。             |
+| rolvaliduntil    | timestamp with time zone | 帐户的有效结束时间，如果没有结束时间，则为NULL。             |
+| rolrespool       | name                     | 用户所能够使用的resource pool。                              |
+| roluseft         | Boolean                  | 角色是否可以操作外表。<br />- t（true）：表示可以。<br />- f（false）：表示不可以。 |
+| rolparentid      | oid                      | 用户所在组用户的OID。                                        |
+| roltabspace      | text                     | 用户数据表的最大空间限额。                                   |
+| rolkind          | char                     | 特殊用户种类，包括私有用户、普通用户。                       |
+| rolnodegroup     | oid                      | 该字段不支持。                                               |
+| roltempspace     | text                     | 用户临时表的最大空间限额，单位为K。                          |
+| rolspillspace    | text                     | 用户执行作业时下盘数据的最大空间限额，单位为K。              |
+| rolexcpdata      | text                     | 用户可以设置的查询规则（当前未使用）。                       |
+| rolmonitoradmin  | Boolean                  | 角色是否具有监控管理员权限：<br />- t（true）：表示有。<br />- f（false）：表示没有。 |
+| roloperatoradmin | Boolean                  | 角色是否具有运维管理员权限：<br />- t（true）：表示有。<br />- f（false）：表示没有。 |
+| rolpolicyadmin   | Boolean                  | 角色是否具有安全策略管理员权限：<br />- t（true）：表示有。<br />- f（false）：表示没有。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AUTH_HISTORY.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AUTH_HISTORY.md
new file mode 100644
index 0000000000000000000000000000000000000000..14a899f8f89d0cfc0883e3bcec7161631211727d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AUTH_HISTORY.md
@@ -0,0 +1,19 @@
+---
+title: PG_AUTH_HISTORY
+summary: PG_AUTH_HISTORY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_AUTH_HISTORY
+
+PG_AUTH_HISTORY系统表记录了角色的认证历史。需要有系统管理员权限才可以访问此系统表。
+
+**表 1** PG_AUTH_HISTORY字段
+
+| 名称         | 类型                     | 描述                     |
+| :----------- | :----------------------- | :------------------------|
+| oid          | oid                      | 行标识符（隐藏属性，必须明确选择）。                         |
+| roloid       | oid                      | 角色标识。                                                   |
+| passwordtime | timestamp with time zone | 创建和修改密码的时间。                                       |
+| rolpassword  | text                     | 角色密码密文，加密方式由GUC参数**password_encryption_type**确定。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AUTH_MEMBERS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AUTH_MEMBERS.md
new file mode 100644
index 0000000000000000000000000000000000000000..7bd75dee01ae9378365286be02a4552842dcafeb
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AUTH_MEMBERS.md
@@ -0,0 +1,19 @@
+---
+title: PG_AUTH_MEMBERS
+summary: PG_AUTH_MEMBERS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_AUTH_MEMBERS
+
+PG_AUTH_MEMBERS系统表存储显示角色之间的成员关系。
+
+**表 1** PG_AUTH_MEMBERS字段
+
+| 名称         | 类型    | 描述                                                       |
+| :----------- | :------ | :--------------------------------------------------------- |
+| roleid       | oid     | 拥有成员的角色ID。                                         |
+| member       | oid     | 属于ROLEID角色的一个成员的角色ID。                         |
+| grantor      | oid     | 赋予此成员关系的角色ID。                                   |
+| admin_option | Boolean | 如果MEMBER可以把ROLEID角色的成员关系赋予其他角色，则为真。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CAST.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CAST.md
new file mode 100644
index 0000000000000000000000000000000000000000..0544f7c8ca2799136016aecb6ce8d8536b9e2e21
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CAST.md
@@ -0,0 +1,21 @@
+---
+title: PG_CAST
+summary: PG_CAST
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_CAST
+
+PG_CAST系统表存储数据类型之间的转化关系。
+
+**表 1** PG_CAST字段
+
+| 名称        | 类型   | 描述                                                         |
+| :---------- | :----- | :----------------------------------------------------------- |
+| oid         | oid    | 行标识符（隐藏属性，必须明确选择）。                         |
+| castsource  | oid    | 源数据类型的OID。                                            |
+| casttarget  | oid    | 目标数据类型的OID。                                          |
+| castfunc    | oid    | 转化函数的OID。如果为零表明不需要转化函数。                  |
+| castcontext | "char" | 源数据类型和目标数据类型间的转化方式: <br/>- 'e': 表示只能进行显式转化（使用CAST或::语法）。<br/>- 'i': 表示只能进行隐式转化。<br/>- 'a': 表示类型间同时支持隐式和显式转化。 |
+| castmethod  | "char" | 转化方法: <br/>- 'f': 使用castfunc字段中指定的函数进行转化。<br/>- 'b': 类型间是二进制强制转化，不使用castfunc。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CLASS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CLASS.md
new file mode 100644
index 0000000000000000000000000000000000000000..e4336c641fd57e349a943140c8b2c774ec31206f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CLASS.md
@@ -0,0 +1,77 @@
+---
+title: PG_CLASS
+summary: PG_CLASS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_CLASS
+
+PG_CLASS系统表存储数据库对象信息及其之间的关系。
+
+**表 1** PG_CLASS字段
+
+| 名称             | 类型             | 描述                                                         |
+| :--------------- | :--------------- | :----------------------------------------------------------- |
+| oid              | oid              | 行标识符（隐藏属性，必须明确选择）。                         |
+| relname          | name             | 表、索引、视图等对象的名称。                                 |
+| relnamespace     | oid              | 包含这个关系的名称空间的OID。                                |
+| reltype          | oid              | 对应这个表的行类型的数据类型（索引为零，因为索引没有pg_type记录）。 |
+| reloftype        | oid              | 复合类型的OID，0表示其他类型。                               |
+| relowner         | oid              | 关系所有者。                                                 |
+| relam            | oid              | 如果行是索引，则就是所用的访问模式（B-tree，hash等）。       |
+| relfilenode      | oid              | 这个关系在磁盘上的文件的名称，如果没有则为0。                |
+| reltablespace    | oid              | 这个关系存储所在的表空间。如果为零，则意味着使用该数据库的缺省表空间。如果关系在磁盘上没有文件，则这个字段没有什么意义。 |
+| relpages         | double precision | 以页（大小为BLCKSZ）为单位的此表在磁盘上的大小，它只是优化器用的一个近似值。 |
+| reltuples        | double precision | 表中行的数目，只是优化器使用的一个估计值。                   |
+| relallvisible    | integer          | 被标识为全可见的表中的页的数量。此字段是优化器用来做SQL执行优化使用的。VACUUM、ANALYZE和一些DDL语句（例如，CREATE INDEX）会引起此字段更新。 |
+| reltoastrelid    | oid              | 与此表关联的TOAST表的OID，如果没有则为0。<br/>TOAST表在一个从属表里"离线"存储大字段。 |
+| reltoastidxid    | oid              | 对于TOAST表是它的索引的OID，如果不是TOAST表则为0。           |
+| reldeltarelid    | oid              | Delta表的OID。<br/>Delta表附属于列存表。用于存储数据导入过程中的甩尾数据。 |
+| reldeltaidx      | oid              | Delta表的索引表OID。                                         |
+| relcudescrelid   | oid              | CU描述表的OID。<br/>CU描述表（Desc表）附属于列存表。用于控制表目录中存储数据的可见性。 |
+| relcudescidx     | oid              | CU描述表的索引表OID。                                        |
+| relhasindex      | Boolean          | 如果它是一个表而且至少有（或者最近有过）一个索引，则为真。<br/>它是由CREATE INDEX设置的，但DROP INDEX不会立即将它清除。如果VACUUM进程检测一个表没有索引，将会把它将清理relhasindex字段，将值设置为假。 |
+| relisshared      | Boolean          | 如果该表在MogDB中由所有数据库共享则为真。只有某些系统表（比如pg_database）是共享的。 |
+| relpersistence   | "char"           | - p: 表示永久表。<br/>- u: 表示非日志表。<br/>- g: 表示临时表。 |
+| relkind          | "char"           | - r: 表示普通表。<br/>- i: 表示索引。<br/>- I: 表示分区表GLOBAL索引。<br/>- S: 表示序列。<br/>- v: 表示视图。<br/>- c: 表示复合类型。<br/>- t: 表示TOAST表。<br/>- f: 表示外表。 |
+| relnatts         | smallint         | 关系中用户字段数目（除了系统字段以外）。在pg_attribute里肯定有相同数目对应行。 |
+| relchecks        | smallint         | 表里的检查约束的数目；参阅pg_constraint表。                  |
+| relhasoids       | Boolean          | 如果为关系中每行都生成一个OID则为真。                        |
+| relhaspkey       | Boolean          | 如果这个表有一个（或者曾经有一个）主键，则为真。             |
+| relhasrules      | Boolean          | 如表有规则就为真。是否有规则可参考系统表PG_REWRITE。         |
+| relhastriggers   | Boolean          | True表示表中有触发器，或者曾经有过触发器。系统表pg_trigger中记录了表和视图的触发器。 |
+| relhassubclass   | Boolean          | 如果有（或者曾经有）任何继承的子表，为真。                   |
+| relcmprs         | tinyint          | 表示是否启用表的启用压缩特性。需要特别注意，当且仅当批量插入才会触发压缩，普通的CRUD并不能够触发压缩。<br/>- 0表示其他不支持压缩的表（主要是指系统表，不支持压缩属性的修改操作）。<br/>- 1表示表数据的压缩特性为NOCOMPRESS或者无指定关键字。<br/>- 2表示表数据的压缩特性为COMPRESS。 |
+| relhasclusterkey | Boolean          | 是否有局部聚簇存储。                                         |
+| relrowmovement   | Boolean          | 针对分区表进行update操作时，是否允许行迁移。<br/>- true: 表示允许行迁移。<br/>- false: 表示不允许行迁移。 |
+| parttype         | "char"           | 表或者索引是否具有分区表的性质。<br/>- p: 表示带有分区表性质。<br/>- n: 表示没有分区表特性。<br/>- v: 表示该表为HDFS的Value分区表。 |
+| relfrozenxid     | xid32            | 该表中所有在这个之前的事务ID已经被一个固定的（"frozen"）事务ID替换。该字段用于跟踪此表是否需要为了防止事务ID重叠（或者允许收缩pg_clog）而进行清理。如果该关系不是表则为零（InvalidTransactionId）。<br/>为保持前向兼容，保留此字段，新增relfrozenxid64用于记录此信息。 |
+| relacl           | aclitem[]        | 访问权限。<br />查询的回显结果为以下形式: <br/>`rolename=xxxx/yyyy  -赋予一个角色的权限`<br/>`=xxxx/yyyy  -赋予public的权限`<br/>xxxx表示赋予的权限，yyyy表示授予这个权限的角色。权限的参数说明请参见[表2](#表2权限的参数说明)。 |
+| relreplident     | "char"           | 逻辑解码中解码列的标识: <br/>- d = 默认 (主键，如果存在)。<br/>- n = 无。<br/>- f = 所有列。<br/>- i = 索引的indisreplident被设置或者为默认。 |
+| relfrozenxid64   | xid              | 该表中所有在这个之前的事务ID已经被一个固定的（"frozen"）事务ID替换。该字段用于跟踪此表是否需要为了防止事务ID重叠（或者允许收缩pg_clog）而进行清理。如果该关系不是表则为零（InvalidTransactionId）。 |
+| relbucket        | oid              | pg_hashbucket中的桶信息。                                    |
+| relbucketkey     | int2vector       | 哈希分区列号。                                               |
+
+**表 2** 权限的参数说明<a id="表2权限的参数说明"> </a>
+
+| 参数 | 参数说明             |
+| :--- | :------------------- |
+| r    | SELECT（读）         |
+| w    | UPDATE（写）         |
+| a    | INSERT（插入）       |
+| d    | DELETE               |
+| D    | TRUNCATE             |
+| x    | REFERENCES           |
+| t    | TRIGGER              |
+| X    | EXECUTE              |
+| U    | USAGE                |
+| C    | CREATE               |
+| c    | CONNECT              |
+| T    | TEMPORARY            |
+| A    | ALTER                |
+| P    | DROP                 |
+| m    | COMMENT              |
+| i    | INDEX                |
+| v    | VACUUM               |
+| *    | 给前面权限的授权选项 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_COLLATION.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_COLLATION.md
new file mode 100644
index 0000000000000000000000000000000000000000..8e90b3a9b79ea7a4c3195c374364a430c9b0c4da
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_COLLATION.md
@@ -0,0 +1,22 @@
+---
+title: PG_COLLATION
+summary: PG_COLLATION
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_COLLATION
+
+PG_COLLATION系统表描述可用的排序规则，本质上从一个SQL名称映射到操作系统本地类别。
+
+**表 1** PG_COLLATION字段
+
+| 名称          | 类型    | 引用             | 描述                        |
+| :------------ | :------ | :--------------- | :-------------------------- |
+| oid           | oid     | -                | 行标识符（隐藏属性，必须明确选择）。                         |
+| collname      | name    | -                | 排序规则名（每个名称空间和编码唯一）。                       |
+| collnamespace | oid     | PG_NAMESPACE.oid | 包含这个排序规则的名称空间的OID。                            |
+| collowner     | oid     | PG_AUTHID.oid    | 排序规则的所有者。                                           |
+| collencoding  | integer | -                | 排序规则可用的编码，兼容PostgreSQL所有的字符编码类型，如果适用于任意编码为-1。 |
+| collcollate   | name    | -                | 这个排序规则对象的LC_COLLATE。                               |
+| collctype     | name    | -                | 这个排序规则对象的LC_CTYPE。                                 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CONSTRAINT.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CONSTRAINT.md
new file mode 100644
index 0000000000000000000000000000000000000000..733d903804e4f2b92c69a50f90da786d481554c1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CONSTRAINT.md
@@ -0,0 +1,48 @@
+---
+title: PG_CONSTRAINT
+summary: PG_CONSTRAINT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_CONSTRAINT
+
+PG_CONSTRAINT系统表存储表上的检查约束、主键和唯一约束。
+
+**表 1** PG_CONSTRAINT字段
+
+| 名称          | 类型         | 描述                                                         |
+| :------------ | :----------- | :----------------------------------------------------------- |
+| oid           | oid          | 行标识符（隐藏属性，必须明确选择）。                         |
+| conname       | name         | 约束名称（不一定是唯一的）。                                 |
+| connamespace  | oid          | 包含这个约束的名称空间的OID。                                |
+| contype       | "char"       | - c = 检查约束<br/>- p = 主键约束<br/>- u = 唯一约束<br/>- t = 触发器约束 |
+| condeferrable | Boolean      | 这个约束是否可以推迟。                                       |
+| condeferred   | Boolean      | 缺省时这个约束是否可以推迟。                                 |
+| convalidated  | Boolean      | 约束是否有效。目前，只有外键和CHECK约束可将其设置为FALSE。   |
+| conrelid      | oid          | 这个约束所在的表；如果不是表约束则为0。                      |
+| contypid      | oid          | 这个约束所在的域；如果不是一个域约束则为0。                  |
+| conindid      | oid          | 与约束关联的索引ID。                                         |
+| confrelid     | oid          | 如果是外键，则为参考的表；否则为0。                          |
+| confupdtype   | "char"       | 外键更新动作代码。<br/>- a = 没动作<br/>- r = 限制<br/>- c = 级联<br/>- n =设置为null<br/>- d =设置为缺省 |
+| confdeltype   | "char"       | 外键删除动作代码。<br/>- a = 没动作<br/>- r = 限制<br/>- c = 级联<br/>- n =设置为null<br/>- d =设置为缺省 |
+| confmatchtype | "char"       | 外键匹配类型。<br/>- f = 全部<br/>- p = 部分<br/>- u = 简单（未指定） |
+| conislocal    | Boolean      | 是否是为关系创建的本地约束。                                 |
+| coninhcount   | integer      | 约束直接继承父表的数目。继承父表数非零时，不能删除或重命名该约束。 |
+| connoinherit  | Boolean      | 是否可以被继承。                                             |
+| consoft       | Boolean      | 是否为信息约束(Informational Constraint)。                   |
+| conopt        | Boolean      | 是否使用信息约束优化执行计划。                               |
+| conkey        | smallint[]   | 如果是表约束，则是约束控制的字段列表。                       |
+| confkey       | smallint[]   | 如果是一个外键，是参考的字段的列表。                         |
+| conpfeqop     | oid[]        | 如果是一个外键，是做PK=FK比较的相等操作符ID的列表。          |
+| conppeqop     | oid[]        | 如果是一个外键，是做PK=PK比较的相等操作符ID的列表。          |
+| conffeqop     | oid[]        | 如果是一个外键，是做FK=FK比较的相等操作符ID的列表。由于当前不支持外键，所以值为空。 |
+| conexclop     | oid[]        | 如果是一个排他约束，是列的排他操作符ID列表。                 |
+| conbin        | pg_node_tree | 如果是检查约束，那就是其表达式的内部形式。                   |
+| consrc        | text         | 如果是检查约束，则是表达式的人类可读形式。                   |
+| conincluding  | smallint[]   | 不用做约束，但是会包含在INDEX中的属性列。                    |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+>
+> - consrc在被引用的对象改变之后不会被更新，它不会跟踪字段的名称修改。与其依赖这个字段，最好还是使用pg_get_constraintdef()来抽取一个检查约束的定义。
+> - pg_class.relchecks需要和在此表上为给定关系找到的检查约束的数目一致。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CONVERSION.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CONVERSION.md
new file mode 100644
index 0000000000000000000000000000000000000000..2c971c36f003375b5ff894a22259b64484eeacd6
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CONVERSION.md
@@ -0,0 +1,23 @@
+---
+title: PG_CONVERSION
+summary: PG_CONVERSION
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_CONVERSION
+
+PG_CONVERSION系统表描述编码转换信息。
+
+**表 1** PG_CONVERSION字段
+
+| 名称           | 类型    | 引用             | 描述                                   |
+| :------------- | :------ | :--------------- | :------------------------------------- |
+| oid            | oid     | -                | 行标识符（隐藏属性，必须明确选择）。   |
+| conname        | name    | -                | 转换名称（在一个名称空间里是唯一的）。 |
+| connamespace   | oid     | PG_NAMESPACE.oid | 包含这个转换的名称空间的OID。          |
+| conowner       | oid     | PG_AUTHID.oid    | 编码转换的属主。                       |
+| conforencoding | integer | -                | 源编码ID。                             |
+| contoencoding  | integer | -                | 目的编码ID。                           |
+| conproc        | regproc | PG_PROC.proname  | 转换过程。                             |
+| condefault     | Boolean | -                | 如果这是缺省转换则为真。               |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DATABASE.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DATABASE.md
new file mode 100644
index 0000000000000000000000000000000000000000..d118f9c83ba30467a6a19aef36fdc0b99f298f1d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DATABASE.md
@@ -0,0 +1,30 @@
+---
+title: PG_DATABASE
+summary: PG_DATABASE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_DATABASE
+
+PG_DATABASE系统表存储关于可用数据库的信息。
+
+**表 1** PG_DATABASE字段
+
+| 名称             | 类型      | 描述                                                         |
+| :--------------- | :-------- | :----------------------------------------------------------- |
+| oid              | oid       | 行标识符（隐藏属性，必须明确选择）。                         |
+| datname          | name      | 数据库名称。                                                 |
+| datdba           | oid       | 数据库所有人，通常为其创建者。                               |
+| encoding         | integer   | 数据库的字符编码方式。                                       |
+| datcollate       | name      | 数据库使用的排序顺序。                                       |
+| datctype         | name      | 数据库使用的字符分类。                                       |
+| datistemplate    | Boolean   | 是否允许作为模板数据库。                                     |
+| datallowconn     | Boolean   | 如果为假，则没有用户可以连接到这个数据库。这个字段用于保护template0数据库不被更改。 |
+| datconnlimit     | integer   | 该数据库上允许的最大并发连接数，-1表示无限制。               |
+| datlastsysoid    | oid       | 数据库里最后一个系统OID 。                                   |
+| datfrozenxid     | xid32     | 用于跟踪该数据库是否需要为了防止事务ID重叠而进行清理。为保持前向兼容，保留此字段，新增datfrozenxid64用于记录此信息。 |
+| dattablespace    | oid       | 数据库的缺省表空间。                                         |
+| datcompatibility | name      | 数据库兼容模式，当前支持四种兼容模式：A、B、C、PG，分别表示兼容O、MY、TD和POSTGRES。 |
+| datacl           | aclitem[] | 访问权限。                                                   |
+| datfrozenxid64   | xid       | 用于跟踪该数据库是否需要为了防止事务ID重叠而进行清理。       |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DB_ROLE_SETTING.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DB_ROLE_SETTING.md
new file mode 100644
index 0000000000000000000000000000000000000000..76a5de80114ca83443ea8b4d97bd2d55917199a5
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DB_ROLE_SETTING.md
@@ -0,0 +1,18 @@
+---
+title: PG_DB_ROLE_SETTING
+summary: PG_DB_ROLE_SETTING
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_DB_ROLE_SETTING
+
+PG_DB_ROLE_SETTING系统表存储数据库运行时每个角色与数据绑定的配置项的默认值 。
+
+**表 1** PG_DB_ROLE_SETTING字段
+
+| 名称        | 类型   | 描述                                            |
+| :---------- | :----- | :---------------------------------------------- |
+| setdatabase | oid    | 配置项所对应的数据库，如果未指定数据库，则为0。 |
+| setrole     | oid    | 配置项所对应的角色，如果未指定角色，则为0。     |
+| setconfig   | text[] | 运行时配置项的默认值。                          |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DEFAULT_ACL.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DEFAULT_ACL.md
new file mode 100644
index 0000000000000000000000000000000000000000..9e584b03ccdc4fd253caf030b542e5c5297ac364
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DEFAULT_ACL.md
@@ -0,0 +1,20 @@
+---
+title: PG_DEFAULT_ACL
+summary: PG_DEFAULT_ACL
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_DEFAULT_ACL
+
+PG_DEFAULT_ACL系统表存储为新建对象设置的初始权限。
+
+**表 1** PG_DEFAULT_ACL字段
+
+| 名称            | 类型      | 描述                                                         |
+| :-------------- | :-------- | :----------------------------------------------------------- |
+| oid             | oid       | 行标识符（隐藏属性，必须明确选择）。                         |
+| defaclrole      | oid       | 与此权限相关的角色ID。                                       |
+| defaclnamespace | oid       | 与此权限相关的名称空间，如果没有，则为0。                    |
+| defaclobjtype   | "char"    | 此权限的对象类型。<br />- r表示表或视图。<br />- S表示序列。<br />- f表示函数。<br />- T表示类型。<br />- K表示客户端主密钥。<br />- k表示列加密密钥。 |
+| defaclacl       | aclitem[] | 创建该类型时所拥有的访问权限。                               |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DEPEND.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DEPEND.md
new file mode 100644
index 0000000000000000000000000000000000000000..f650e3c117bb03ae6860e6faa871224d9d26d76f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DEPEND.md
@@ -0,0 +1,32 @@
+---
+title: PG_DEPEND
+summary: PG_DEPEND
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_DEPEND
+
+PG_DEPEND系统表记录数据库对象之间的依赖关系。这个信息允许DROP命令找出哪些其它对象必须由DROP CASCADE删除，或者是在DROP RESTRICT的情况下避免删除。
+
+这个表的功能类似PG_SHDEPEND，用于记录那些在MogDB之间共享的对象之间的依赖性关系。
+
+**表 1** PG_DEPEND字段
+
+| 名称        | 类型    | 引用         | 描述                                                         |
+| :---------- | :------ | :----------- | :----------------------------------------------------------- |
+| classid     | oid     | PG_CLASS.oid | 有依赖对象所在系统表的OID。                                  |
+| objid       | oid     | 任意OID属性  | 指定的依赖对象的OID。                                        |
+| objsubid    | integer | -            | 对于表字段，这个是该属性的字段数（objid和classid引用表本身）。对于所有其它对象类型，目前这个字段是零。 |
+| refclassid  | oid     | PG_CLASS.oid | 被引用对象所在的系统表的OID。                                |
+| refobjid    | oid     | 任意OID属性  | 指定的被引用对象的OID。                                      |
+| refobjsubid | integer | -            | 对于表字段，这个是该字段的字段号（refobjid和refclassid引用表本身）。对于所有其它对象类型，目前这个字段是零。 |
+| deptype     | "char"  | -            | 一个定义这个依赖关系特定语义的代码。                         |
+
+在所有情况下，一个PG_DEPEND记录表示被引用的对象不能在有依赖的对象被删除前删除。不过，这里还有几种由deptype定义的情况:
+
+- DEPENDENCY_NORMAL (n): 独立创建的对象之间的一般关系。有依赖的对象可以在不影响被引用对象的情况下删除。被引用对象只有在声明了CASCADE的情况下删除，这时有依赖的对象也被删除。例子: 一个表字段对其数据类型有一般依赖关系。
+- DEPENDENCY_AUTO (a): 有依赖对象可以和被引用对象分别删除，并且如果删除了被引用对象则应该被自动删除（不管是RESTRICT或CASCADE模式）。例子: 一个表上面的命名约束是在该表上的自动依赖关系，因此如果删除了表，它也会被删除。
+- DEPENDENCY_INTERNAL (i): 有依赖的对象是作为被引用对象的一部分创建的，实际上只是它的内部实现的一部分。DROP有依赖对象是不能直接允许的（将告诉用户发出一条删除被引用对象的DROP）。一个对被引用对象的DROP将传播到有依赖对象，不管是否声明了CASCADE。
+- DEPENDENCY_EXTENSION (e): 依赖对象是被依赖对象extension的一个成员（请参见PG_EXTENSION）。依赖对象只可以通过在被依赖对象上DROP EXTENSION删除。函数上这个依赖类型和内部依赖一样动作，但是它为了清晰和简化gs_dump保持分开。
+- DEPENDENCY_PIN (p): 没有依赖对象；这种类型的记录标志着系统本身依赖于被引用对象，因此这个对象决不能被删除。这种类型的记录只有在initdb的时候创建。有依赖对象的字段里是零。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DESCRIPTION.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DESCRIPTION.md
new file mode 100644
index 0000000000000000000000000000000000000000..07514d73c2bbc7fd18e98a83a86d152325925e3e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DESCRIPTION.md
@@ -0,0 +1,21 @@
+---
+title: PG_DESCRIPTION
+summary: PG_DESCRIPTION
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_DESCRIPTION
+
+PG_DESCRIPTION系统表可以给每个数据库对象存储一个可选的描述（注释）。许多内置的系统对象的描述提供了PG_DESCRIPTION的初始内容。
+
+这个表的功能类似PG_SHDESCRIPTION，用于记录MogDB范围内共享对象的注释。
+
+**表 1** PG_DESCRIPTION字段
+
+| 名称        | 类型    | 引用         | 描述       |
+| :---------- | :------ | :----------- | :--------|
+| objoid      | oid     | 任意OID属性  | 这条描述所描述的对象的OID。                                  |
+| classoid    | oid     | PG_CLASS.oid | 这个对象出现的系统表的OID。                                  |
+| objsubid    | integer | -            | 对于一个表字段的注释，它是字段号（objoid和classoid指向表自身）。对于其它对象类型，它是零。 |
+| description | text    | -            | 对该对象描述的任意文本。                                     |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DIRECTORY.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DIRECTORY.md
new file mode 100644
index 0000000000000000000000000000000000000000..c9d8e2bb2600b46aafac6b24cd1baa4acd059cfa
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DIRECTORY.md
@@ -0,0 +1,20 @@
+---
+title: PG_DIRECTORY
+summary: PG_DIRECTORY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_DIRECTORY
+
+PG_DIRECTORY系统表用于保存用户添加的directory对象可以通过CREATE DIRECTORY语句向该表中添加记录，目前只有系统管理员用户可以向该表中添加记录。
+
+**表 1** PG_DIRECTORY字段
+
+| 名称    | 类型      | 描述                                 |
+| :------ | :-------- | :----------------------------------- |
+| oid     | oid       | 行标识符（隐藏属性，必须明确选择）。 |
+| dirname | name      | 目录对象的名称。                     |
+| owner   | oid       | 目录对象的所有者。                   |
+| dirpath | text      | 目录路径。                           |
+| diracl  | aclitem[] | 访问权限。                           |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_ENUM.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_ENUM.md
new file mode 100644
index 0000000000000000000000000000000000000000..55a292759fcd41feae04f50b1b0b6d2aa203cca8
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_ENUM.md
@@ -0,0 +1,23 @@
+---
+title: PG_ENUM
+summary: PG_ENUM
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_ENUM
+
+PG_ENUM系统表包含显示每个枚举类型值和标签的记录。给定枚举类型的内部表示实际上是PG_ENUM里面相关行的OID。
+
+**表 1** PG_ENUM字段
+
+| 名称          | 类型 | 引用        | 描述                                   |
+| :------------ | :--- | :---------- | :------------------------------------- |
+| oid           | oid  | -           | 行标识符（隐藏属性，必须明确选择）。   |
+| enumtypid     | oid  | PG_TYPE.oid | 拥有这个枚举值的pg_type记录的OID。     |
+| enumsortorder | real | -           | 这个枚举值在它的枚举类型中的排序位置。 |
+| enumlabel     | name | -           | 这个枚举值的文本标签。                 |
+
+PG_ENUM行的OID跟着一个特殊规则: 偶数的OID保证用和它们的枚举类型一样的排序顺序排序。也就是，如果两个偶数OID属于相同的枚举类型，那么较小的OID必须有较小enumsortorder值。奇数OID需要毫无关系的排序顺序。这个规则允许枚举比较例程在许多常见情况下避开目录查找。创建和修改枚举类型的例程只要可能就尝试分配偶数OID给枚举值。
+
+当创建了一个枚举类型时，它的成员赋予了排序顺序位置1到n。但是随后添加的成员可能会分配enumsortorder的负值或分数值。对这些值的唯一要求是它们要正确的排序和在每个枚举类型中唯一。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_EXTENSION.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_EXTENSION.md
new file mode 100644
index 0000000000000000000000000000000000000000..d2a3aa6c8363844b0bd00523dd48bdd4ad8b1c20
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_EXTENSION.md
@@ -0,0 +1,23 @@
+---
+title: PG_EXTENSION
+summary: PG_EXTENSION
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_EXTENSION
+
+PG_EXTENSION系统表存储关于所安装扩展的信息。MogDB默认扩展是PLPGSQL和MOT_FDW。
+
+**表 1** PG_EXTENSION
+
+| 名称           | 类型    | 描述                                               |
+| :------------- | :------ | :------------------------------------------------- |
+| oid            | oid     | 数据库对象id。                                     |
+| extname        | name    | 扩展名。                                           |
+| extowner       | oid     | 扩展的所有者。                                     |
+| extnamespace   | oid     | 扩展导出对象的名称空间。                           |
+| extrelocatable | Boolean | 标识此扩展是否可迁移到其他名称空间，true表示允许。 |
+| extversion     | text    | 扩展的版本号。                                     |
+| extconfig      | oid[]   | 扩展的配置信息。                                   |
+| extcondition   | text[]  | 扩展配置信息的过滤条件。                           |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_EXTENSION_DATA_SOURCE.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_EXTENSION_DATA_SOURCE.md
new file mode 100644
index 0000000000000000000000000000000000000000..0e55a3daf7899c36018c5d0fa8a9ea5521424b10
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_EXTENSION_DATA_SOURCE.md
@@ -0,0 +1,22 @@
+---
+title: PG_EXTENSION_DATA_SOURCE
+summary: PG_EXTENSION_DATA_SOURCE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_EXTENSION_DATA_SOURCE
+
+PG_EXTENSION_DATA_SOURCE系统表存储外部数据源对象的信息。一个外部数据源对象（Data Source）包含了外部数据库的一些口令编码等信息，主要配合Extension Connector使用。
+
+**表 1** PG_EXTENSION_DATA_SOURCE字段
+
+| 名称       | 类型      | 引用          | 描述                                                        |
+| :--------- | :-------- | :------------ | :---------------------------------------------------------- |
+| oid        | oid       | -             | 行标识符（隐藏属性，必须明确选择）。                        |
+| srcname    | name      | -             | 外部数据源对象的名称。                                      |
+| srcowner   | oid       | PG_AUTHID.oid | 外部数据源对象的所有者。                                    |
+| srctype    | text      | -             | 外部数据源对象的类型，缺省为空。                            |
+| srcversion | text      | -             | 外部数据源对象的版本，缺省为空。                            |
+| srcacl     | aclitem[] | -             | 访问权限。                                                  |
+| srcoptions | text[]    | -             | 外部数据源对象的指定选项，使用"keyword=value"格式的字符串。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_FOREIGN_DATA_WRAPPER.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_FOREIGN_DATA_WRAPPER.md
new file mode 100644
index 0000000000000000000000000000000000000000..b565593420f67a072da366a400e148782fa6a55f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_FOREIGN_DATA_WRAPPER.md
@@ -0,0 +1,22 @@
+---
+title: PG_FOREIGN_DATA_WRAPPER
+summary: PG_FOREIGN_DATA_WRAPPER
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_FOREIGN_DATA_WRAPPER
+
+PG_FOREIGN_DATA_WRAPPER系统表存储外部数据封装器定义。一个外部数据封装器是在外部服务器上驻留外部数据的机制，是可以访问的。
+
+**表 1** PG_FOREIGN_DATA_WRAPPER字段
+
+| 名称         | 类型      | 引用          | 描述                                                         |
+| :----------- | :-------- | :------------ | :----------------------------------------------------------- |
+| oid          | oid       | -             | 行标识符(隐藏属性，必须明确选择)。                           |
+| fdwname      | name      | -             | 外部数据封装器名。                                           |
+| fdwowner     | oid       | PG_AUTHID.oid | 外部数据封装器的所有者。                                     |
+| fdwhandler   | oid       | PG_PROC.oid   | 引用一个负责为外部数据封装器提供扩展例程的处理函数。如果没有提供处理函数则为零。 |
+| fdwvalidator | oid       | PG_PROC.oid   | 引用一个验证器函数，这个验证器函数负责验证给予外部数据封装器的选项、 外部服务器选项和使用外部数据封装器的用户映射的有效性。 如果没有提供验证器函数则为零。 |
+| fdwacl       | aclitem[] | -             | 访问权限。                                                   |
+| fdwoptions   | text[]    | -             | 外部数据封装器指定选项，使用"keyword=value"格式的字符串。    |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_FOREIGN_SERVER.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_FOREIGN_SERVER.md
new file mode 100644
index 0000000000000000000000000000000000000000..c28a1e0f55e9ad0d38f2f2b54f71b10f1f66e58c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_FOREIGN_SERVER.md
@@ -0,0 +1,23 @@
+---
+title: PG_FOREIGN_SERVER
+summary: PG_FOREIGN_SERVER
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_FOREIGN_SERVER
+
+PG_FOREIGN_SERVER系统表存储外部服务器定义。一个外部服务器描述了一个外部数据源，例如一个远程服务器。外部服务器通过外部数据封装器访问。
+
+**表 1** PG_FOREIGN_SERVER字段
+
+| 名称       | 类型      | 引用                        | 描述                          |
+| :--------- | :-------- | :-------------------------- | :---------------------------- |
+| oid        | oid       | -                           | 行标识符（隐藏属性，必须明确选择）。                  |
+| srvname    | name      | -                           | 外部服务器名。                                        |
+| srvowner   | oid       | PG_AUTHID.oid               | 外部服务器的所有者。                                  |
+| srvfdw     | oid       | PG_FOREIGN_DATA_WRAPPER.oid | 这个外部服务器的外部数据封装器的OID。                 |
+| srvtype    | text      | -                           | 服务器的类型（可选）。                                |
+| srvversion | text      | -                           | 服务器的版本（可选）。                                |
+| srvacl     | aclitem[] | -                           | 访问权限。                                            |
+| srvoptions | text[]    | -                           | 外部服务器指定选项，使用"keyword=value"格式的字符串。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_FOREIGN_TABLE.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_FOREIGN_TABLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..035a7c4a217aab74b1cfe880e5dcd35be5aa5702
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_FOREIGN_TABLE.md
@@ -0,0 +1,19 @@
+---
+title: PG_FOREIGN_TABLE
+summary: PG_FOREIGN_TABLE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_FOREIGN_TABLE
+
+PG_FOREIGN_TABLE系统表存储外部表的辅助信息。
+
+**表 1** PG_FOREIGN_TABLE字段
+
+| 名称        | 类型    | 描述                                                         |
+| :---------- | :------ | :----------------------------------------------------------- |
+| ftrelid     | oid     | 外部表的ID。                                                 |
+| ftserver    | oid     | 外部表的所在服务器。                                         |
+| ftwriteonly | Boolean | 外部表是否可写。取值如下：<br />- t（true）：表示可写<br />- f（false）：表示不可写 |
+| ftoptions   | text[]  | 外部表的可选项，具体参考CREATE FOREIGN TABLE语法说明。       |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_INDEX.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_INDEX.md
new file mode 100644
index 0000000000000000000000000000000000000000..a39b496de4a71a81828aaddcdabf52edd9d9b375
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_INDEX.md
@@ -0,0 +1,35 @@
+---
+title: PG_INDEX
+summary: PG_INDEX
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_INDEX
+
+PG_INDEX系统表存储索引的一部分信息，其他的信息大多数在PG_CLASS中。
+
+**表 1** PG_INDEX字段
+
+| 名称           | 类型         | 描述                                                         |
+| :------------- | :----------- | :----------------------------------------------------------- |
+| indexrelid     | oid          | 这个索引在pg_class里的记录的OID。                            |
+| indrelid       | oid          | 使用这个索引的表在pg_class里的记录的OID。                    |
+| indnatts       | smallint     | 索引中的字段数目。                                           |
+| indisunique    | Boolean      | 如果为真，这是个唯一索引。<br />如果为假，这不是唯一索引。   |
+| indisprimary   | Boolean      | 如果为真，该索引代表该表的主键。这个字段为真的时候indisunique总是为真。<br />如果为假，该索引不是该表的主键。 |
+| indisexclusion | Boolean      | 如果为真，该索引支持排他约束。<br />如果为假，该索引不支持排他约束。 |
+| indimmediate   | Boolean      | 如果为真，在插入数据时会立即进行唯一性检查。<br />如果为假，在插入数据时不会进行唯一性检查。 |
+| indisclustered | Boolean      | 如果为真，则该表最后在这个索引上建了簇。<br />如果为假，则该表没有再这个索引上建簇。 |
+| indisusable    | Boolean      | 如果为真，该索引对insert/select可用。<br />如果为假，该索引对insert/select不可用。 |
+| indisvalid     | Boolean      | 如果为真，则该索引可以用于查询。<br />如果为假，则该索引可能不完整，仍然必须在INSERT/UPDATE操作时进行更新，不过不能安全的用于查询。如果是唯一索引，则唯一属性也将不为真。 |
+| indcheckxmin   | Boolean      | 如果为true，查询不能使用索引，直到pg_index此行的xmin低于其快照的TransactionXmin，因为该表可能包含它们能看到的不兼容行断开的HOT链。<br />如果为false，查询可以用于索引。 |
+| indisready     | Boolean      | 如果为真，表示此索引对插入数据是可用的，否则，在插入或修改数据时忽略此索引。 |
+| indkey         | int2vector   | 这是一个包含indnatts值的数组，这些数组值表示这个索引所建立的表字段。比如一个值为1 3的意思是第一个字段和第三个字段组成这个索引键字。这个数组里的零表明对应的索引属性是在这个表字段上的一个表达式，而不是一个简单的字段引用。 |
+| indcollation   | oidvector    | 索引用到的各列的ID。                                         |
+| indclass       | oidvector    | 对于索引键字里面的每个字段，这个字段都包含一个指向所使用的操作符类的OID，参阅pg_opclass获取细节。 |
+| indoption      | int2vector   | 存储列前标识位，该标识位是由索引的访问方法定义。             |
+| indexprs       | pg_node_tree | 表达式树（以nodeToString()形式表现）用于那些非简单字段引用的索引属性。它是一个列表，个数与INDKEY中的零值个数相同。如果所有索引属性都是简单的引用，则为空。 |
+| indpred        | pg_node_tree | 部分索引断言的表达式树（以nodeToString()的形式表现）。如果不是部分索引，则是空字符串。 |
+| indisreplident | Boolean      | 如果为真，则此索引的列成为逻辑解码的解码列。如果为假，则此索引的列不是逻辑解码的解码列。 |
+| indnkeyatts    | smallint     | 索引中的总字段数，超出indnatts的部分不参与索引查询。         |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_INHERITS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_INHERITS.md
new file mode 100644
index 0000000000000000000000000000000000000000..593d2b3243f6ff410036ff06c47fd6eedc2449a0
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_INHERITS.md
@@ -0,0 +1,18 @@
+---
+title: PG_INHERITS
+summary: PG_INHERITS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_INHERITS
+
+PG_INHERITS系统表记录关于表继承层次的信息。数据库里每个直接的子系表都有一条记录。间接的继承可以通过追溯记录链来判断。
+
+**表 1** PG_INHERITS字段
+
+| 名称      | 类型    | 引用         | 描述           |
+| :-------- | :------ | :----------- | :------------ |
+| inhrelid  | oid     | PG_CLASS.oid | 子表的OID。                                                  |
+| inhparent | oid     | PG_CLASS.oid | 父表的OID。                                                  |
+| inhseqno  | integer | -            | 如果一个子表存在多个直系父表（多重继承），这个数字表明此继承字段的排列顺序。计数从1开始。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_JOB.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_JOB.md
new file mode 100644
index 0000000000000000000000000000000000000000..d379dea5f7e489f51da2d467586f8ffcc369f16d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_JOB.md
@@ -0,0 +1,32 @@
+---
+title: PG_JOB
+summary: PG_JOB
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_JOB
+
+PG_JOB系统表存储用户创建的定时任务的任务详细信息，定时任务线程定时轮询pg_job系统表中的时间，当任务到期会触发任务的执行，并更新pg_job表中的任务状态。该系统表属于Shared Relation，所有创建的job记录对所有数据库可见。
+
+**表 1** PG_JOB字段
+
+| 名称                 | 类型                        | 描述                                                         |
+| :------------------- | :-------------------------- | :----------------------------------------------------------- |
+| oid                  | oid                         | 行标识符（隐藏属性，必须明确选择）。                         |
+| job_id               | bigint                      | 作业ID，主键，是唯一的（有唯一索引）                         |
+| current_postgres_pid | bigint                      | 如果当前任务已被执行，那么此处记录运行此任务的postgres线程ID。默认为 -1，表示此任务未被执行过。 |
+| log_user             | name                        | 创建者的UserName                                             |
+| priv_user            | name                        | 作业执行者的UserName                                         |
+| dbname               | name                        | 标识作业要在哪个数据库执行的数据库名称                       |
+| node_name            | name                        | 标识当前作业是在哪个数据库主节点上创建和执行                 |
+| job_status           | "char"                      | 当前任务的执行状态，取值范围: ('r', 's', 'f', 'd')，默认为's'，取值含义: <br/>Status of job step: r=running, s=successfully finished, f=job failed, d=disable<br/>当job连续执行失败16次，会将job_status自动设置为失效状态'd'，后续不再执行该job。<br/>注: 当用户将定时任务关闭（即: guc参数job_queue_processes为0时），由于监控job执行的线程不会启动，所以该状态不会根据job的实时状态进行设置，用户不需要关注此状态。只有当开启定时任务功能（即: guc参数job_queue_processes为非0时），系统才会根据当前job的实时状态刷新该字段值。 |
+| start_date           | timestamp without time zone | 作业第一次开始执行时间，时间精确到毫秒。                     |
+| next_run_date        | timestamp without time zone | 下次定时执行任务的时间，时间精确到毫秒。                     |
+| failure_count        | smallint                    | 失败计数，作业连续执行失败16次，不再继续执行。               |
+| interval             | text                        | 作业执行的重复时间间隔。                                     |
+| last_start_date      | timestamp without time zone | 上次运行开始时间，时间精确到毫秒。                           |
+| last_end_date        | timestamp without time zone | 上次运行的结束时间，时间精确到毫秒。                         |
+| last_suc_date        | timestamp without time zone | 上次成功运行的开始时间，时间精确到毫秒。                     |
+| this_run_date        | timestamp without time zone | 正在运行任务的开始时间，时间精确到毫秒。                     |
+| nspname              | name                        | 标识作业执行时的schema的名称。                               |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_JOB_PROC.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_JOB_PROC.md
new file mode 100644
index 0000000000000000000000000000000000000000..748f88ece9491c2227b42ef228b74a8f653ab7cb
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_JOB_PROC.md
@@ -0,0 +1,19 @@
+---
+title: PG_JOB_PROC
+summary: PG_JOB_PROC
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_JOB_PROC
+
+PG_JOB_PROC系统表对应PG_JOB表中每个任务的作业内容（包括: PL/SQL代码块、匿名块）。将存储过程信息独立出来，如果放到PG_JOB中，被加载到共享内存的时候，会占用不必要的空间，所以在使用的时候再进行查询获取。
+
+**表 1** PG_JOB_PROC字段
+
+| 名称     | 类型    | 描述                                 |
+| :------- | :------ | :----------------------------------- |
+| oid      | oid     | 行标识符（隐藏属性，必须明确选择）。 |
+| job_oid  | integer | 外键，关联pg_job表中的job_id。       |
+| what     | text    | 作业内容。                           |
+| job_name | text    | 作业名称。                           |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_LANGUAGE.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_LANGUAGE.md
new file mode 100644
index 0000000000000000000000000000000000000000..8c43dcb452843b1a578ad2c4bc8a7e09f38210c5
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_LANGUAGE.md
@@ -0,0 +1,24 @@
+---
+title: PG_LANGUAGE
+summary: PG_LANGUAGE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_LANGUAGE
+
+PG_LANGUAGE系统表登记编程语言，用户可以用这些语言或接口写函数或者存储过程。
+
+**表 1** PG_LANGUAGE字段
+
+| 名称          | 类型      | 引用          | 描述                                                         |
+| :------------ | :-------- | :------------ | :----------------------------------------------------------- |
+| oid           | oid       | -             | 行标识符（隐藏属性；必须明确选择）。                         |
+| lanname       | name      | -             | 语言的名称。                                                 |
+| lanowner      | oid       | PG_AUTHID.oid | 语言的所有者。                                               |
+| lanispl       | Boolean   | -             | 对于内部语言而言是假（比如SQL），对于用户定义的语言则是真。目前，gs_dump仍然使用这个东西判断哪种语言需要转储，但是这些可能在将来被其它机制取代。 |
+| lanpltrusted  | Boolean   | -             | 如果这是可信语言则为真，意味着系统相信它不会被授予任何正常SQL执行环境之外的权限。只有初始用户可以用不可信的语言创建函数。 |
+| lanplcallfoid | oid       | PG_PROC.oid   | 对于非内部语言，这是指向该语言处理器的引用，语言处理器是一个特殊函数， 负责执行以某种语言写的所有函数。 |
+| laninline     | oid       | PG_PROC.oid   | 这个字段引用一个负责执行"inline"匿名代码块的函数（DO块）。如果不支持内联块则为零。 |
+| lanvalidator  | oid       | PG_PROC.oid   | 这个字段引用一个语言校验器函数，它负责检查新创建的函数的语法和有效性。如果没有提供校验器，则为零。 |
+| lanacl        | aclitem[] | -             | 访问权限。                                                   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_LARGEOBJECT.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_LARGEOBJECT.md
new file mode 100644
index 0000000000000000000000000000000000000000..05667b5aa6caea3c3f77d69dfb4ad69263c62dbd
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_LARGEOBJECT.md
@@ -0,0 +1,22 @@
+---
+title: PG_LARGEOBJECT
+summary: PG_LARGEOBJECT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_LARGEOBJECT
+
+PG_LARGEOBJECT系统表保存那些标记着"大对象"的数据。一个大对象是使用其创建时分配的OID标识的。每个大对象都分解成足够小的小段或者"页面"以便以行的形式存储在PG_LARGEOBJECT里。每页的数据定义为LOBLKSIZE。
+
+需要有系统管理员权限才可以访问此系统表。
+
+**表 1** PG_LARGEOBJECT字段
+
+| 名称   | 类型    | 引用                | 描述             |
+| :----- | :------ | :-----------------| :------------------|
+| loid   | oid     | PG_LARGEOBJECT_METADATA.oid | 包含本页的大对象的标识符。                                   |
+| pageno | integer | -                           | 本页在其大对象数据中的页码从零开始计算。                     |
+| data   | bytea   | -                           | 存储在大对象中的实际数据。这些数据绝不会超过LOBLKSIZE字节，而且可能更少。 |
+
+PG_LARGEOBJECT的每一行保存一个大对象的一个页面，从该对象内部的字节偏移（pageno * LOBLKSIZE）开始。这种实现允许松散的存储: 页面可以丢失，而且可以比LOBLKSIZE字节少（即使它们不是对象的最后一页）。大对象内丢失的部分读做零。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_LARGEOBJECT_METADATA.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_LARGEOBJECT_METADATA.md
new file mode 100644
index 0000000000000000000000000000000000000000..ba2c692172f8cbfe6224f2c974c6206da882541b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_LARGEOBJECT_METADATA.md
@@ -0,0 +1,18 @@
+---
+title: PG_LARGEOBJECT_METADATA
+summary: PG_LARGEOBJECT_METADATA
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_LARGEOBJECT_METADATA
+
+PG_LARGEOBJECT_METADATA系统表存储与大数据相关的元数据。实际的大对象数据存储在PG_LARGEOBJECT里。
+
+**表 1** PG_LARGEOBJECT_METADATA字段
+
+| 名称     | 类型      | 引用          | 描述                                 |
+| :------- | :-------- | :------------ | :----------------------------------- |
+| oid      | oid       | -             | 行标识符（隐藏属性，必须明确选择）。 |
+| lomowner | oid       | PG_AUTHID.oid | 大对象的所有者。                     |
+| lomacl   | aclitem[] | -             | 访问权限。                           |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_NAMESPACE.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_NAMESPACE.md
new file mode 100644
index 0000000000000000000000000000000000000000..633f5378db7525cca93d135c8ead3cfd3c150c9b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_NAMESPACE.md
@@ -0,0 +1,22 @@
+---
+title: PG_NAMESPACE
+summary: PG_NAMESPACE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_NAMESPACE
+
+PG_NAMESPACE系统表存储名称空间，即存储schema相关的信息。
+
+**表 1** PG_NAMESPACE字段
+
+| 名称              | 类型      | 描述                    |
+| :---------------- | :-------- | :---------------------- |
+| oid               | oid       | 行标识符（隐藏属性，必须明确选择）。                         |
+| nspname           | name      | 名称空间的名称。                                             |
+| nspowner          | oid       | 名称空间的所有者。                                           |
+| nsptimeline       | bigint    | 在数据库节点上创建此命名空间时的时间线。此字段为内部使用，仅在数据库节点上有效。 |
+| nspacl            | aclitem[] | 访问权限。                                                   |
+| in_redistribution | "char"    | 是否处于重发布状态。                                         |
+| nspblockchain     | Boolean   | - 如果为真，则该模式为防篡改模式。<br />- 如果为假，则此模式为非防篡改模式。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OBJECT.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OBJECT.md
new file mode 100644
index 0000000000000000000000000000000000000000..38a6a3901ea4f67a96ddbe749156624b03a724a3
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OBJECT.md
@@ -0,0 +1,30 @@
+---
+title: PG_OBJECT
+summary: PG_OBJECT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_OBJECT
+
+PG_OBJECT系统表存储限定类型对象（普通表，索引，序列，视图，存储过程和函数）的创建用户、创建时间和最后修改时间。
+
+**表 1** PG_OBJECT字段
+
+| 名称        | 类型                     | 描述                                                         |
+| :---------- | :----------------------- | :----------------------------------------------------------- |
+| object_oid  | oid                      | 对象标识符                                                   |
+| object_type | "char"                   | 对象类型: <br/>- r 表示普通表<br/>- i 表示索引<br/>- s 表示序列<br/>- v 表示视图<br/>- p 表示存储过程和函数 |
+| creator     | oid                      | 创建用户的标识符                                             |
+| ctime       | timestamp with time zone | 对象的创建时间                                               |
+| mtime       | timestamp with time zone | 对象的最后修改时间，修改行为包括ALTER操作和GRANT、REVOKE操作 |
+| createcsn   | int8                     | 对象创建时的CSN。                                            |
+| changecsn   | int8                     | 对表或索引执行DDL操作时的CSN。                               |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+>
+> - 无法记录初始化数据库（initdb）过程中所创建或修改的对象，即PG_OBJECT无法查询到该对象记录。
+> - 对于升级前创建的对象，再次修改时会记录其修改时间（mtime），对表或索引执行DDL操作时会记录其所属事务的事务提交序列号（changecsn）。由于无法得知该对象创建时间，因此ctime和createcsn为空。
+> - ctime和mtime所记录的时间为用户当次操作所属事务的起始时间。
+> - 由扩容引起的对象修改时间也会被记录。
+> - createcsn和changecsn记录的是用户当次操作所属事务的事务提交序列号。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OPCLASS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OPCLASS.md
new file mode 100644
index 0000000000000000000000000000000000000000..6584031e5f9c6ac5d165cc6c79577880a0734704
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OPCLASS.md
@@ -0,0 +1,28 @@
+---
+title: PG_OPCLASS
+summary: PG_OPCLASS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_OPCLASS
+
+PG_OPCLASS系统表定义索引访问方法操作符类。
+
+每个操作符类为一种特定数据类型和一种特定索引访问方法定义索引字段的语义。一个操作符类本质上指定一个特定的操作符族适用于一个特定的可索引的字段数据类型。索引的字段实际可用的族中的操作符集是接受字段的数据类型作为它们的左边的输入的那个。
+
+**表 1** PG_OPCLASS字段
+
+| 名称         | 类型    | 引用             | 描述                                        |
+| :----------- | :------ | :--------------- | :------------------------------------------ |
+| oid          | oid     | -                | 行标识符（隐藏属性，必须明确选择）。        |
+| opcmethod    | oid     | PG_AM.oid        | 操作符类所服务的索引访问方法。              |
+| opcname      | name    | -                | 这个操作符类的名称。                        |
+| opcnamespace | oid     | PG_NAMESPACE.oid | 这个操作符类的名称空间。                    |
+| opcowner     | oid     | PG_AUTHID.oid    | 操作符类属主。                              |
+| opcfamily    | oid     | PG_OPFAMILY.oid  | 包含该操作符类的操作符族。                  |
+| opcintype    | oid     | PG_TYPE.oid      | 操作符类索引的数据类型。                    |
+| opcdefault   | Boolean | -                | 如果操作符类是opcintype的缺省，则为真。     |
+| opckeytype   | oid     | PG_TYPE.oid      | 索引数据的类型，如果和opcintype相同则为零。 |
+
+一个操作符类的opcmethod必须匹配包含它的操作符族的opfmethod。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OPERATOR.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OPERATOR.md
new file mode 100644
index 0000000000000000000000000000000000000000..99fba746decf6b9192965fe36152c03e34466582
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OPERATOR.md
@@ -0,0 +1,30 @@
+---
+title: PG_OPERATOR
+summary: PG_OPERATOR
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_OPERATOR
+
+PG_OPERATOR系统表存储有关操作符的信息。
+
+**表 1** PG_OPERATOR字段
+
+| 名称         | 类型    | 引用             | 描述                          |
+| :----------- | :------ | :--------------- | :---------------------------- |
+| oid          | oid     | -                | 行标识符（隐藏属性，必须明确选择）。                         |
+| oprname      | name    | -                | 操作符的名称。                                               |
+| oprnamespace | oid     | PG_NAMESPACE.oid | 包含此操作符的名称空间的OID。                                |
+| oprowner     | oid     | PG_AUTHID.oid    | 操作符所有者。                                               |
+| oprkind      | "char"  | -                | - b=infix =中缀("两边")<br/>- l=前缀("左边")<br/>- r=后缀("右边") |
+| oprcanmerge  | Boolean | -                | 这个操作符是否支持合并连接。<br />- t（true）：表示支持合并连接。<br />- f（false）：表示不支持合并连接。 |
+| oprcanhash   | Boolean | -                | 这个操作符是否支持Hash连接。<br />- t（true）：表示支持Hash连接。<br />- f（false）：表示不支持Hash连接。 |
+| oprleft      | oid     | PG_TYPE.oid      | 左操作数的类型。                                             |
+| oprright     | oid     | PG_TYPE.oid      | 右操作数的类型。                                             |
+| oprresult    | oid     | PG_TYPE.oid      | 结果类型。                                                   |
+| oprcom       | oid     | PG_OPERATOR.oid  | 此操作符的交换符，如果存在的话。                             |
+| oprnegate    | oid     | PG_OPERATOR.oid  | 此操作符的反转器，如果存在的话。                             |
+| oprcode      | regproc | PG_PROC.proname  | 实现这个操作符的函数。                                       |
+| oprrest      | regproc | PG_PROC.proname  | 此操作符的约束选择性计算函数。                               |
+| oprjoin      | regproc | PG_PROC.proname  | 此操作符的连接选择性计算函数。                               |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OPFAMILY.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OPFAMILY.md
new file mode 100644
index 0000000000000000000000000000000000000000..718c3276c44ff9332d5cb7570438006086f75640
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OPFAMILY.md
@@ -0,0 +1,24 @@
+---
+title: PG_OPFAMILY
+summary: PG_OPFAMILY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_OPFAMILY
+
+PG_OPFAMILY系统表定义操作符族。
+
+每个操作符族是一个操作符和相关支持例程的集合，其中的例程实现为一个特定的索引访问方式指定的语义。另外，族中的操作符都是"兼容的"，通过由访问方式指定的方法。操作符族的概念允许交叉数据类型操作符和索引一起使用，并且合理的使用访问方式的语义的知识。
+
+**表 1** PG_OPFAMILY字段
+
+| 名称         | 类型 | 引用             | 描述                                 |
+| :----------- | :--- | :--------------- | :----------------------------------- |
+| oid          | oid  | -                | 行标识符（隐藏属性，必须明确选择）。 |
+| opfmethod    | oid  | PG_AM.oid        | 操作符族使用的索引方法。             |
+| opfname      | name | -                | 这个操作符族的名称。                 |
+| opfnamespace | oid  | PG_NAMESPACE.oid | 这个操作符的名称空间。               |
+| opfowner     | oid  | PG_AUTHID.oid    | 操作符族的所有者。                   |
+
+定义一个操作符族的大多数信息不在它的PG_OPFAMILY行里面，而是在相关的行PG_AMOP，PG_AMPROC和PG_OPCLASS里。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_PARTITION.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_PARTITION.md
new file mode 100644
index 0000000000000000000000000000000000000000..76f7ec09773cb5f050d16a9baf435880ba8d61d3
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_PARTITION.md
@@ -0,0 +1,44 @@
+---
+title: PG_PARTITION
+summary: PG_PARTITION
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_PARTITION
+
+PG_PARTITION系统表存储数据库内所有分区表（partitioned table）、分区（table partition）、分区上toast表和分区索引（index partition）四类对象的信息。分区表索引（partitioned index）的信息不在PG_PARTITION系统表中保存。
+
+**表 1** PG_PARTITION字段
+
+| 名称               | 类型             | 描述                                                         |
+| :----------------- | :--------------- | :----------------------------------------------------------- |
+| oid                | oid              | 行标识符（隐藏属性，必须明确选择）。                         |
+| relname            | name             | 分区表、分区、分区上toast表和分区索引的名称。                |
+| parttype           | "char"           | 对象类型: <br/>- 'r': partitioned table<br/>- 'p': table partition<br/>- 'x': index partition<br/>- 't': toast table |
+| parentid           | oid              | 当对象为分区表或分区时，此字段表示分区表在PG_CLASS中的OID。当对象为index partition时，此字段表示所属分区表索引（partitioned index）的OID。 |
+| rangenum           | integer          | 保留字段。                                                   |
+| intervalnum        | integer          | 保留字段。                                                   |
+| partstrategy       | "char"           | 分区表分区策略，现在仅支持: <br/>- 'r': 范围分区。<br/>- 'v': 数值分区。<br/>- 'i': 间隔分区。<br />- 'l'：list分区。<br />- 'h'：hash分区。<br />- 'n'：无效分区。 |
+| relfilenode        | oid              | table partition、index partition、分区上toast表的物理存储位置。 |
+| reltablespace      | oid              | table partition、index partition、分区上toast表所属表空间的OID。 |
+| relpages           | double precision | 统计信息: table partition、index partition的数据页数量。     |
+| reltuples          | double precision | 统计信息: table partition、index partition的元组数。         |
+| relallvisible      | integer          | 统计信息: table partition、index partition的可见数据页数。   |
+| reltoastrelid      | oid              | table partition所对应toast表的OID。                          |
+| reltoastidxid      | oid              | table partition所对应toast表的索引的OID。                    |
+| indextblid         | oid              | index partition对应table partition的OID。                    |
+| indisusable        | Boolean          | 分区索引是否可用。                                           |
+| reldeltarelid      | oid              | Delta表的OID。                                               |
+| reldeltaidx        | oid              | Delta表的索引表的OID。                                       |
+| relcudescrelid     | oid              | CU描述表的OID。                                              |
+| relcudescidx       | oid              | CU描述表的索引表的OID。                                      |
+| relfrozenxid       | xid32            | 冻结事务ID号。<br />为保持前向兼容，保留此字段，新增relfrozenxid64用于记录此信息。 |
+| intspnum           | integer          | 间隔分区所属表空间的个数。                                   |
+| partkey            | int2vector       | 分区键的列号。                                               |
+| intervaltablespace | oidvector        | 间隔分区所属的表空间，间隔分区以round-robin方式落在这些表空间内。 |
+| interval           | text[]           | 间隔分区的间隔值。                                           |
+| boundaries         | text[]           | 范围分区和间隔分区的上边界。                                 |
+| transit            | text[]           | 间隔分区的跳转点。                                           |
+| reloptions         | text[]           | 设置partition的存储属性，与pg_class.reloptions的形态一样，用"keyword=value"格式的字符串来表示 ，目前用于在线扩容的信息搜集。 |
+| relfrozenxid64     | xid              | 冻结事务ID号。                                               |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_PLTEMPLATE.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_PLTEMPLATE.md
new file mode 100644
index 0000000000000000000000000000000000000000..474e28237ea571eb6284588a1ce751aad31e0e32
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_PLTEMPLATE.md
@@ -0,0 +1,23 @@
+---
+title: PG_PLTEMPLATE
+summary: PG_PLTEMPLATE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_PLTEMPLATE
+
+PG_PLTEMPLATE系统表存储过程语言的"模板"信息。
+
+**表 1** PG_PLTEMPLATE字段
+
+| 名称          | 类型      | 描述                                     |
+| :------------ | :-------- | :--------------------------------------- |
+| tmplname      | name      | 这个模板所应用的语言的名称。             |
+| tmpltrusted   | Boolean   | 如果语言被认为是可信的，则为真。         |
+| tmpldbacreate | Boolean   | 如果语言是由数据库所有者创建的，则为真。 |
+| tmplhandler   | text      | 调用处理器函数的名称。                   |
+| tmplinline    | text      | 匿名块处理器的名称，若没有则为NULL。     |
+| tmplvalidator | text      | 校验函数的名称，如果没有则为NULL。       |
+| tmpllibrary   | text      | 实现语言的共享库的路径。                 |
+| tmplacl       | aclitem[] | 模板的访问权限（未使用）。               |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_PROC.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_PROC.md
new file mode 100644
index 0000000000000000000000000000000000000000..ddc20b278eb1b9713c0e3bcf01be32b43c5dab6d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_PROC.md
@@ -0,0 +1,53 @@
+---
+title: PG_PROC
+summary: PG_PROC
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_PROC
+
+PG_PROC系统表存储函数或过程的信息。
+
+**表 1** PG_PROC字段
+
+| 名称                | 类型              | 描述                                                         |
+| :------------------ | :---------------- | :----------------------------------------------------------- |
+| oid                 | oid               | 行标识符（隐藏属性，必须明确选择）。                         |
+| proname             | name              | 函数名称。                                                   |
+| pronamespace        | oid               | 包含该函数名称空间的OID。                                    |
+| proowner            | oid               | 函数的所有者。                                               |
+| prolang             | oid               | 这个函数的实现语言或调用接口。                               |
+| procost             | real              | 估算的执行成本。                                             |
+| prorows             | real              | 估算的影响行的数目。                                         |
+| provariadic         | oid               | 参数元素的数据类型。                                         |
+| protransform        | regproc           | 此函数的简化调用方式。                                       |
+| proisagg            | Boolean           | 函数是聚集函数。<br />- t（true）：表示是。<br />- f（false）：表示不是。 |
+| proiswindow         | Boolean           | 函数是窗口函数。<br />- t（true）：表示是。<br />- f（false）：表示不是。 |
+| prosecdef           | Boolean           | 函数是一个安全定义器（也就是一个“setuid”函数）。<br />- t（true）：表示是。<br />- f（false）：表示不是。 |
+| proleakproof        | Boolean           | 函数没副作用。如果函数没有对参数进行防泄露处理，则会抛出错误。<br />- t（true）：表示没副作用。<br />- f（false）：表示有副作用。 |
+| proisstrict         | Boolean           | 如果任何调用参数是空，则函数返回空。这时函数实际上连调用都不调用。不是“strict”的函数必须准备处理空输入。 |
+| proretset           | Boolean           | 函数返回一个集合（也就是说，指定数据类型的多个数值）。       |
+| provolatile         | “char”            | 告诉该函数的结果是否只依赖于它的输入参数，或者还会被外界因素影响。<br />- i：“不可变的”（immutable）函数，这样的函数对于相同的输入总是产生相同的结果。<br />- s：稳定的”（stable）函数它是s，（对于固定输入）其结果在一次扫描里不变。<br />- v：“易变”（volatile）函数它是v，其结果可能在任何时候变化v也用于那些有副作用的函数，因此调用它们无法得到优化。 |
+| pronargs            | smallint          | 参数数目。                                                   |
+| pronargdefaults     | smallint          | 有默认值的参数数目。                                         |
+| prorettype          | oid               | 返回值的数据类型。                                           |
+| proargtypes         | oidvector         | 一个存放函数参数的数据类型的数组。数组里只包括输入参数（包括INOUT参数）此代表该函数的调用签名（接口）。 |
+| proallargtypes      | oid[]             | 一个包含函数参数的数据类型的数组。数组里包括所有参数的类型（包括OUT和INOUT参数），如果所有参数都是IN参数，则这个字段就会是空。请注意数组下标是以1为起点的，而因为历史原因，proargtypes的下标起点为0。 |
+| proargmodes         | “char”[]          | 一个保存函数参数模式的数组，编码如下：<br />- i表示IN参数。<br />- o表示OUT参数。<br />- b表示INOUT参数。<br />- v表示VARIADIC参数。<br />如果所有参数都是IN参数，则这个字段为空。请注意，下标对应的是proallargtypes的位置，而不是proargtypes。 |
+| proargnames         | text[]            | 一个保存函数参数的名称的数组。没有名称的参数在数组里设置为空字符串。如果没有一个参数有名称，这个字段将是空。请注意，此数组的下标对应proallargtypes而不是proargtypes。 |
+| proargdefaults      | pg_node_tree      | 默认值的表达式树。是PRONARGDEFAULTS元素的列表。              |
+| prosrc              | text              | 描述函数或存储过程的定义。例如，对于解释型语言来说就是函数的源程序，或者一个链接符号，一个文件名，或者函数和存储过程创建时指定的其他任何函数体内容，具体取决于语言/调用习惯的实现。 |
+| probin              | text              | 关于如何调用该函数的附加信息。同样，其含义也是和语言相关的。 |
+| proconfig           | text[]            | 函数针对运行时配置变量的本地设置。                           |
+| proacl              | aclitem[]         | 访问权限。具体请参见GRANT和REVOKE。                          |
+| prodefaultargpos    | int2vector        | 函数具有默认值的入参的位置。                                 |
+| fencedmode          | Boolean           | 函数的执行模式，表示函数是在fence还是not fence模式下执行。如果是fence执行模式，函数的执行会在重新fork的进程中执行。<br />用户创建的C函数，fencedmode字段默认值均为true，即fence模式；系统内建函数，fencedmode字段均为false，即not fence模式。 |
+| proshippable        | Boolean           | 表示该函数是否可以下推到数据库节点上执行，默认值是false。<br />- 对于IMMUTABLE类型的函数，函数始终可以下推到数据库节点上执行。<br />- 对于STABLE/VOLATILE类型的函数，仅当函数的属性是SHIPPABLE的时候，函数可以下推到数据库节点执行。 |
+| propackage          | Boolean           | 表示该函数是否支持重载，默认值是false。<br />- t（true）：表示支持。<br />- f（false）：表示不支持。 |
+| prokind             | “char”            | 表示该对象为函数还是存储过程：<br />- 值为'f'表示该对象为函数。<br />- 值为'p'表示该对象为存储过程。 |
+| proargsrc           | text              | 描述兼容oracle语法定义的函数或存储过程的参数输入字符串，包括参数注释。默认值为NULL。 |
+| proisprivate        | Boolean           | 描述函数是否是PACKAGE内的私有函数，默认为false。             |
+| propackageid        | oid               | 函数所属的package oid，如果不在package内，则为0。            |
+| proargtypesext      | oidvector_extend  | 当函数参数较多时，用来存放函数参数的数据类型的数组。数组里只包括输入参数（包括INOUT参数）此代表该函数的调用签名（接口）。 |
+| prodefaultargposext | int2vector_extend | 当函数参数较多时，函数具有默认值的入参的位置。               |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_RANGE.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_RANGE.md
new file mode 100644
index 0000000000000000000000000000000000000000..49f8bf6600766a5b44a201c94773d3be3d1ff5f0
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_RANGE.md
@@ -0,0 +1,23 @@
+---
+-title: PG_RANGE
+summary: PG_RANGE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_RANGE
+
+PG_RANGE系统表存储关于范围类型的信息。除了PG_TYPE里类型的记录。
+
+**表 1** PG_RANGE字段
+
+| 名称         | 类型    | 引用             | 描述                                                         |
+| :----------- | :------ | :--------------- | :----------------------------------------------------------- |
+| rngtypid     | oid     | PG_TYPE.oid      | 范围类型的OID。                                              |
+| rngsubtype   | oid     | PG_TYPE.oid      | 这个范围类型的元素类型（子类型）的OID。                      |
+| rngcollation | oid     | PG_COLLATION.oid | 用于范围比较的排序规则的OID，如果没有则为零。                |
+| rngsubopc    | oid     | PG_OPCLASS.oid   | 用于范围比较的子类型的操作符类的OID。                        |
+| rngcanonical | regproc | PG_PROC.proname  | 转换范围类型为规范格式的函数名，如果没有则为0。              |
+| rngsubdiff   | regproc | PG_PROC.proname  | 返回两个double precision元素值的不同的函数名，如果没有则为0。 |
+
+rngsubopc（如果元素类型是可排序的，则加上rngcollation）决定用于范围类型的排序顺序。当元素类型是离散的时使用rngcanonical。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_RESOURCE_POOL.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_RESOURCE_POOL.md
new file mode 100644
index 0000000000000000000000000000000000000000..11d8b9384b5c8eb3f76c45f1278c90cd2f7b6e60
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_RESOURCE_POOL.md
@@ -0,0 +1,31 @@
+---
+title: PG_RESOURCE_POOL
+summary: PG_RESOURCE_POOL
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_RESOURCE_POOL
+
+PG_RESOURCE_POOL系统表提供了数据库资源池的信息。
+
+**表 1** PG_RESOURCE_POOL字段
+
+| 名称              | 类型    | 描述        |
+| :---------------- | :------ | :----------------- |
+| oid               | oid     | 行标识符（隐藏属性，必须明确选择）。                         |
+| respool_name      | name    | 资源池名称。                          |
+| mem_percent       | integer | 内存配置的百分比。                    |
+| cpu_affinity      | bigint  | CPU绑定core的数值。                   |
+| control_group     | name    | 资源池所在的control group名称。       |
+| active_statements | integer | 资源池上最大的并发数。                |
+| max_dop           | integer | 最大并发度。用作扩容的接口，表示数据重分布时，扫描并发度。 |
+| memory_limit      | name    | 资源池最大的内存。                    |
+| parentid          | oid     | 父资源池OID。  |
+| io_limits         | integer | 每秒触发IO的次数上限。行存单位是万次/s，列存是次/s。         |
+| io_priority       | name    | IO利用率高达90%时，重消耗IO作业进行IO资源管控时关联的优先级等级。 |
+| nodegroup         | name    | 表示资源池所在的逻辑MogDB的名称。     |
+| is_foreign        | boolean | 表示资源池是否用于逻辑MogDB之外的用户。如果为true，表示资源池用来控制不属于当前资源池的普通用户的资源。 |
+| max_worker | integer | 只用于扩容的接口，表示扩容数据重分布时，表内并发度。 |
+
+注：max_dop和max_worker用户扩容，不适用于MogDB。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_REWRITE.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_REWRITE.md
new file mode 100644
index 0000000000000000000000000000000000000000..af349b4e07028218aefafcb4fa1e691ee5effb2e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_REWRITE.md
@@ -0,0 +1,24 @@
+---
+title: PG_REWRITE
+summary: PG_REWRITE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_REWRITE
+
+PG_REWRITE系统表存储为表和视图定义的重写规则。
+
+**表 1** PG_REWRITE字段
+
+| 名称       | 类型         | 描述                                                         |
+| :--------- | :----------- | :----------------------------------------------------------- |
+| oid        | oid          | 行标识符（隐藏属性，必须明确选择）。                         |
+| rulename   | name         | 规则名称。                                                   |
+| ev_class   | oid          | 使用这条规则的表名称。                                       |
+| ev_attr    | smallint     | 这条规则适用的字段（目前总是为零，表示整个表）。             |
+| ev_type    | "char"       | 规则适用的事件类型: <br/>- 1 = SELECT<br/>- 2 = UPDATE<br/>- 3 = INSERT<br/>- 4 = DELETE |
+| ev_enabled | "char"       | 用于控制复制的触发。<br/>- O ="origin"和"local"模式时触发。<br/>- D =禁用触发。<br/>- R ="replica"时触发。<br/>- A ＝任何模式是都会触发。 |
+| is_instead | Boolean      | 如果该规则是INSTEAD规则，则为真。                            |
+| ev_qual    | pg_node_tree | 规则的资格条件的表达式树（以nodeToString() 形式存在）。      |
+| ev_action  | pg_node_tree | 规则动作的查询树（以nodeToString() 形式存在）。              |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_RLSPOLICY.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_RLSPOLICY.md
new file mode 100644
index 0000000000000000000000000000000000000000..6e9d4992f84561b109c95cb7c2057c47f3cd3869
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_RLSPOLICY.md
@@ -0,0 +1,22 @@
+---
+title: PG_RLSPOLICY
+summary: PG_RLSPOLICY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_RLSPOLICY
+
+PG_RLSPOLICY系统表存储行级访问控制策略。
+
+**表 1** PG_RLSPOLICY字段
+
+| 名称          | 类型         | 描述                                                         |
+| :------------ | :----------- | :----------------------------------------------------------- |
+| oid           | oid          | 行标识符（隐藏属性，必须明确选择）。                         |
+| polname       | name         | 行级访问控制策略的名称。                                     |
+| polrelid      | oid          | 行级访问控制策略作用的表对象oid。                            |
+| polcmd        | "char"       | 行级访问控制策略影响的SQL操作。                              |
+| polpermissive | boolean      | 行级访问控制策略的属性，t为表达式OR条件拼接，f为表达式AND条件拼接。 |
+| polroles      | oid[]        | 行级访问控制策略影响的用户oid列表，不指定表示影响所有的用户。 |
+| polqual       | pg_node_tree | 行级访问控制策略的表达式。                                   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SECLABEL.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SECLABEL.md
new file mode 100644
index 0000000000000000000000000000000000000000..ede35fbb968837b6b146cfa633d220d5f6b951c2
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SECLABEL.md
@@ -0,0 +1,22 @@
+---
+title: PG_SECLABEL
+summary: PG_SECLABEL
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_SECLABEL
+
+PG_SECLABEL系统表存储数据对象上的安全标签。
+
+PG_SHSECLABEL的作用类似，只是它是用于在一个MogDB内共享的数据库对象的安全标签上的。
+
+**表 1** PG_SECLABEL字段
+
+| 名称     | 类型    | 引用         | 描述                           |
+| :------- | :------ | :----------- | :----------------------------- |
+| objoid   | oid     | 任意OID属性  | 这个安全标签所属的对象的OID。  |
+| classoid | oid     | PG_CLASS.oid | 出现这个对象的系统目录的OID。  |
+| objsubid | integer | -            | 出现在这个对象中的列的序号。   |
+| provider | text    | -            | 与这个标签相关的标签提供程序。 |
+| label    | text    | -            | 应用于这个对象的安全标签。     |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SHDEPEND.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SHDEPEND.md
new file mode 100644
index 0000000000000000000000000000000000000000..8e507582525b23dd73b927e0763b98c8fe9e318c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SHDEPEND.md
@@ -0,0 +1,41 @@
+---
+title: PG_SHDEPEND
+summary: PG_SHDEPEND
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_SHDEPEND
+
+PG_SHDEPEND系统表记录数据库对象和共享对象（比如角色）之间的依赖性关系。这些信息允许MogDB保证在企图删除这些对象之前，这些对象是没有被引用的。
+
+PG_DEPEND的作用类似，只是它是用于在一个数据库内部的对象的依赖性关系的。
+
+和其它大多数系统表不同，PG_SHDEPEND是在MogDB里面所有的数据库之间共享的: 每个MogDB只有一个PG_SHDEPEND，而不是每个数据库一个。
+
+**表 1** PG_SHDEPEND字段
+
+| 名称       | 类型    | 引用            | 描述                                                         |
+| :--------- | :------ | :-------------- | :----------------------------------------------------------- |
+| dbid       | oid     | PG_DATABASE.oid | 依赖对象所在的数据库的OID，如果是共享对象，则为零。          |
+| classid    | oid     | PG_CLASS.oid    | 依赖对象所在的系统表的OID。                                  |
+| objid      | oid     | 任意OID属性     | 指定的依赖对象的OID。                                        |
+| objsubid   | integer | -               | 对于一个表字段，这是字段号（objid和classid参考表本身）。对于所有其他对象类型，这个字段为零。 |
+| refclassid | oid     | PG_CLASS.oid    | 被引用对象所在的系统表的OID(必须是一个共享表)。              |
+| refobjid   | oid     | 任意OID属性     | 指定的被引用对象的OID。                                      |
+| deptype    | "char"  | -               | 一段代码，定义了这个依赖性关系的特定语义；参阅下文。         |
+| objfile    | text    | -               | 用户定义函数库文件路径。                                     |
+
+在任何情况下，一条PG_SHDEPEND记录就表明这个被引用的对象不能在未删除依赖对象的前提下删除。不过，deptype同时还标出了几种不同的子风格:
+
+- SHARED_DEPENDENCY_OWNER (o)
+
+  被引用的对象（必须是一个角色）是依赖对象的所有者。
+
+- SHARED_DEPENDENCY_ACL (a)
+
+  被引用的对象（必须是一个角色）在依赖对象的ACL（访问控制列表，也就是权限列表）里提到。SHARED_DEPENDENCY_ACL不会在对象的所有者头上添加的，因为所有者会有一个SHARED_DEPENDENCY_OWNER记录。
+
+- SHARED_DEPENDENCY_PIN (p)
+
+  没有依赖对象；这类记录标识系统自身依赖于该被依赖对象，因此这样的对象绝对不能被删除。这种类型的记录只是由initdb创建。这样的依赖对象的字段都是零。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SHDESCRIPTION.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SHDESCRIPTION.md
new file mode 100644
index 0000000000000000000000000000000000000000..d92907d2d8ce1502c456f0a1e6d22633f2fe2151
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SHDESCRIPTION.md
@@ -0,0 +1,22 @@
+---
+title: PG_SHDESCRIPTION
+summary: PG_SHDESCRIPTION
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_SHDESCRIPTION
+
+PG_SHDESCRIPTION系统表为共享数据库对象存储可选的注释。可以使用COMMENT命令操作注释的内容，使用psql的\\d命令查看注释内容。
+
+PG_DESCRIPTION提供了类似的功能，它记录了单个数据库中对象的注释。
+
+不同于大多数系统表，PG_SHDESCRIPTION是在MogDB里面所有的数据库之间共享的: 每个MogDB只有一个PG_SHDESCRIPTION，而不是每个数据库一个。
+
+**表 1** PG_SHDESCRIPTION字段
+
+| 名称        | 类型 | 引用         | 描述                           |
+| :---------- | :--- | :----------- | :----------------------------- |
+| objoid      | oid  | 任意OID属性  | 这条描述所描述的对象的OID。    |
+| classoid    | oid  | PG_CLASS.oid | 这个对象出现的系统表的OID。    |
+| description | text | -            | 作为对该对象的描述的任意文本。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SHSECLABEL.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SHSECLABEL.md
new file mode 100644
index 0000000000000000000000000000000000000000..5367d7ab52e008f0b4db04353cdc7fcaa84968e3
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SHSECLABEL.md
@@ -0,0 +1,25 @@
+---
+title: PG_SHSECLABEL
+summary: PG_SHSECLABEL
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_SHSECLABEL
+
+PG_SHSECLABEL系统表存储在共享数据库对象上的安全标签。安全标签可以用SECURITY LABEL命令操作。
+
+查看安全标签的简单点的方法，请参阅PG_SECLABELS。
+
+PG_SECLABEL的作用类似，只是它是用于在单个数据库内部的对象的安全标签的。
+
+不同于大多数的系统表，PG_SHSECLABEL在MogDB中的所有数据库中共享: 每个MogDB只有一个PG_SHSECLABEL，而不是每个数据库一个。
+
+**表 1** PG_SHSECLABEL字段
+
+| 名称     | 类型 | 引用         | 描述                           |
+| :------- | :--- | :----------- | :----------------------------- |
+| objoid   | oid  | 任意OID属性  | 这个安全标签所属的对象的OID。  |
+| classoid | oid  | PG_CLASS.oid | 出现这个对象的系统目录的OID。  |
+| provider | text | -            | 与这个标签相关的标签提供程序。 |
+| label    | text | -            | 应用于这个对象的安全标签。     |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_STATISTIC.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_STATISTIC.md
new file mode 100644
index 0000000000000000000000000000000000000000..1c624735d3b52bae1f29f33a6ef73198ab4fff53
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_STATISTIC.md
@@ -0,0 +1,28 @@
+---
+title: PG_STATISTIC
+summary: PG_STATISTIC
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STATISTIC
+
+PG_STATISTIC系统表存储有关该数据库中表和索引列的统计数据。默认只有系统管理员权限才可以访问此系统表，普通用户需要授权才可以访问。
+
+**表 1** PG_STATISTIC字段
+
+| 名称          | 类型     | 描述                                                         |
+| :------------ | :------- | :----------------------------------------------------------- |
+| starelid      | oid      | 所描述的字段所属的表或者索引。                               |
+| starelkind    | "char"   | 所属对象的类型。                                             |
+| staattnum     | smallint | 所描述的字段在表中的编号，从1开始。                          |
+| stainherit    | Boolean  | 是否统计有继承关系的对象。                                   |
+| stanullfrac   | real     | 该字段中为NULL的记录的比率。                                 |
+| stawidth      | integer  | 非NULL记录的平均存储宽度，以字节计。                         |
+| stadistinct   | real     | 标识全局统计信息中数据库节点上字段里唯一的非NULL数据值的数目。<br/>- 一个大于零的数值是独立数值的实际数目。<br/>- 一个小于零的数值是表中行数的分数的负数（比如，一个字段的数值平均出现概率为两次，则可以表示为stadistinct=-0.5）。<br/>- 零值表示独立数值的数目未知。 |
+| stakindN      | smallint | 一个编码，表示这种类型的统计存储在pg_statistic行的第n个"槽位"。<br/>n的取值范围: 1～5 |
+| staopN        | oid      | 一个用于生成这些存储在第n个"槽位"的统计信息的操作符。比如，一个柱面图槽位会显示<操作符，该操作符定义了该数据的排序顺序。<br/>n的取值范围: 1～5 |
+| stanumbersN   | real[]   | 第n个"槽位"的相关类型的数值类型统计，如果该槽位和数值类型没有关系，则就是NULL。<br/>n的取值范围: 1～5 |
+| stavaluesN    | anyarray | 第n个"槽位"类型的字段数据值，如果该槽位类型不存储任何数据值，则就是NULL。每个数组的元素值实际上都是指定字段的数据类型，因此，除了把这些字段的类型定义成anyarray之外，没有更好的办法。<br/>n的取值范围: 1～5 |
+| stadndistinct | real     | 标识dn1上字段里唯一的非NULL数据值的数目。<br/>- 一个大于零的数值是独立数值的实际数目。<br/>- 一个小于零的数值是表中行数的分数的负数（比如，一个字段的数值平均出现概率为两次，则可以表示为stadistinct=-0.5）。<br/>- 零值表示独立数值的数目未知。 |
+| staextinfo    | text     | 统计信息的扩展信息。预留字段。                               |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_STATISTIC_EXT.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_STATISTIC_EXT.md
new file mode 100644
index 0000000000000000000000000000000000000000..71c025daac37b4164e7ed926d8e6d8cb44963dbd
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_STATISTIC_EXT.md
@@ -0,0 +1,28 @@
+---
+title: PG_STATISTIC_EXT
+summary: PG_STATISTIC_EXT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STATISTIC_EXT
+
+PG_STATISTIC_EXT系统表存储有关该数据库中表的扩展统计数据，包括多列统计数据和表达式统计数据（后续支持）。收集哪些扩展统计数据是由用户指定的。需要有系统管理员权限才可以访问此系统表。
+
+**表 1** PG_STATISTIC_EXT字段
+
+| 名称          | 类型         | 描述                                                         |
+| :------------ | :----------- | :----------------------------------------------------------- |
+| starelid      | oid          | 所描述的字段所属的表或者索引。                               |
+| starelkind    | "char"       | 所属对象的类型，'c'表示普通表，'p'表示分区表。               |
+| stainherit    | Boolean      | 是否统计有继承关系的对象。                                   |
+| stanullfrac   | real         | 该字段中为NULL的记录的比率。                                 |
+| stawidth      | integer      | 非NULL记录的平均存储宽度，以字节计。                         |
+| stadistinct   | real         | 标识全局统计信息中数据库节点上字段里唯一的非NULL数据值的数目。<br/>- 一个大于零的数值是独立数值的实际数目。<br/>- 一个小于零的数值是表中行数的分数的负数（比如，一个字段的数值平均出现概率为两次，则可以表示为stadistinct=-0.5）。<br/>- 零值表示独立数值的数目未知。 |
+| stadndistinct | real         | 标识dn1上字段里唯一的非NULL数据值的数目。<br/>- 一个大于零的数值是独立数值的实际数目。<br/>- 一个小于零的数值是表中行数的分数的负数（比如，一个字段的数值平均出现概率为两次，则可以表示为stadistinct=-0.5）。<br/>- 零值表示独立数值的数目未知。 |
+| stakindN      | smallint     | 一个编码，表示这种类型的统计存储在pg_statistic行的第n个"槽位"。<br/>n的取值范围: 1～5 |
+| staopN        | oid          | 一个用于生成这些存储在第n个"槽位"的统计信息的操作符。比如，一个柱面图槽位会显示<操作符，该操作符定义了该数据的排序顺序。<br/>n的取值范围: 1～5 |
+| stakey        | int2vector   | 所描述的字段编号的数组。                                     |
+| stanumbersN   | real[]       | 第n个"槽位"的相关类型的数值类型统计，如果该槽位和数值类型没有关系，则就是NULL。<br/>n的取值范围: 1～5 |
+| stavaluesN    | anyarray     | 第n个"槽位"类型的字段数据值，如果该槽位类型不存储任何数据值，则就是NULL。每个数组的元素值实际上都是指定字段的数据类型，因此，除了把这些字段的类型定义成anyarray之外，没有更好的办法。<br/>n的取值范围: 1～5 |
+| staexprs      | pg_node_tree | 扩展统计信息对应的表达式。                                   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SYNONYM.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SYNONYM.md
new file mode 100644
index 0000000000000000000000000000000000000000..870e86969dbc6440d0042417e8ab8c3369c381c0
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SYNONYM.md
@@ -0,0 +1,21 @@
+---
+title: PG_SYNONYM
+summary: PG_SYNONYM
+author: Guo Huan
+date: 2021-07-26
+---
+
+# PG_SYNONYM
+
+PG_SYNONYM系统表存储同义词对象名与其他数据库对象名间的映射信息。
+
+**表 1** PG_SYNONYM字段
+
+| 名称         | 类型 | 描述                                    |
+| :----------- | :--- | :-------------------------------------- |
+| oid          | oid  | 数据库对象id。                          |
+| synname      | name | 同义词名称。                            |
+| synnamespace | oid  | 包含该同义词的名字空间的OID。           |
+| synowner     | oid  | 同义词的所有者，通常是创建它的用户OID。 |
+| synobjschema | name | 关联对象指定的模式名。                  |
+| synobjname   | name | 关联对象名。                            |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TABLESPACE.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TABLESPACE.md
new file mode 100644
index 0000000000000000000000000000000000000000..9ced9980df0458138939eb7b6496ac65386dca33
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TABLESPACE.md
@@ -0,0 +1,22 @@
+---
+title: PG_TABLESPACE
+summary: PG_TABLESPACE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_TABLESPACE
+
+PG_TABLESPACE系统表存储表空间信息。
+
+**表 1** PG_TABLESPACE字段
+
+| 名称       | 类型      | 描述                                                         |
+| :--------- | :-------- | :----------------------------------------------------------- |
+| oid        | oid       | 行标识符（隐藏属性，必须明确选择）。                         |
+| spcname    | name      | 表空间名称。                                                 |
+| spcowner   | oid       | 表空间的所有者，通常是创建它的人。                           |
+| spcacl     | aclitem[] | 访问权限。具体请参见[GRANT](108-GRANT)和[REVOKE](120-REVOKE)。 |
+| spcoptions | text[]    | 表空间的选项。                                               |
+| spcmaxsize | text      | 可使用的最大磁盘空间大小，单位Byte。                         |
+| relative   | boolean   | 标识表空间指定的存储路径是否为相对路径。                     |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TRIGGER.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TRIGGER.md
new file mode 100644
index 0000000000000000000000000000000000000000..160b8e4169322ecdf317f8a08394955148539e6a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TRIGGER.md
@@ -0,0 +1,32 @@
+---
+title: PG_TRIGGER
+summary: PG_TRIGGER
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_TRIGGER
+
+PG_TRIGGER系统表存储触发器信息。
+
+**表 1** PG_TRIGGER字段
+
+| 名称           | 类型         | 描述                                                         |
+| :------------- | :----------- | :----------------------------------------------------------- |
+| oid            | oid          | 行标识符（隐藏属性，必须明确选择）。                         |
+| tgrelid        | oid          | 触发器所在表的OID。                                          |
+| tgname         | name         | 触发器名。                                                   |
+| tgfoid         | oid          | 要被触发器调用的函数。                                       |
+| tgtype         | smallint     | 触发器类型。                                                 |
+| tgenabled      | "char"       | O =触发器在"origin"和"local"模式下触发。<br/>D =触发器被禁用。<br/>R =触发器在"replica"模式下触发。<br/>A =触发器始终触发。 |
+| tgisinternal   | boolean      | 内部触发器标识，如果为true表示内部触发器。                   |
+| tgconstrrelid  | oid          | 完整性约束引用的表。                                         |
+| tgconstrindid  | oid          | 完整性约束的索引。                                           |
+| tgconstraint   | oid          | 约束触发器在pg_constraint中的OID。                           |
+| tgdeferrable   | boolean      | 约束触发器是为DEFERRABLE类型。                               |
+| tginitdeferred | boolean      | 约束触发器是否为INITIALLY DEFERRED类型。                     |
+| tgnargs        | smallint     | 触发器函数入参个数。                                         |
+| tgattr         | int2vector   | 当触发器指定列时的列号，未指定则为空数组。                   |
+| tgargs         | bytea        | 传递给触发器的参数。                                         |
+| tgqual         | pg_node_tree | 表示触发器的WHEN条件，如果没有则为null。                     |
+| tgowner        | oid          | 触发器的所有者。                                             |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_CONFIG.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_CONFIG.md
new file mode 100644
index 0000000000000000000000000000000000000000..560aa9e5a84b73257fe6e292f5a764b62cc9e949
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_CONFIG.md
@@ -0,0 +1,23 @@
+---
+title: PG_TS_CONFIG
+summary: PG_TS_CONFIG
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_TS_CONFIG
+
+PG_TS_CONFIG系统表包含表示文本搜索配置的记录。一个配置指定一个特定的文本搜索解析器和一个为了每个解析器的输出类型使用的字典的列表。
+
+解析器在PG_TS_CONFIG记录中显示，但是字典映射的标记是由PG_TS_CONFIG_MAP里面的辅助记录定义的。
+
+**表 1** PG_TS_CONFIG字段
+
+| 名称         | 类型   | 引用             | 描述                                 |
+| :----------- | :----- | :--------------- | :----------------------------------- |
+| oid          | oid    | -                | 行标识符（隐藏属性，必须明确选择）。 |
+| cfgname      | name   | -                | 文本搜索配置名。                     |
+| cfgnamespace | oid    | PG_NAMESPACE.oid | 包含这个配置的名称空间的OID。        |
+| cfgowner     | oid    | PG_AUTHID.oid    | 配置的所有者。                       |
+| cfgparser    | oid    | PG_TS_PARSER.oid | 这个配置的文本搜索解析器的OID。      |
+| cfoptions    | text[] | -                | 分词相关配置选项。                   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_CONFIG_MAP.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_CONFIG_MAP.md
new file mode 100644
index 0000000000000000000000000000000000000000..5d6b0b08e590073f166002aa98b08026933f7e3e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_CONFIG_MAP.md
@@ -0,0 +1,19 @@
+---
+title: PG_TS_CONFIG_MAP
+summary: PG_TS_CONFIG_MAP
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_TS_CONFIG_MAP
+
+PG_TS_CONFIG_MAP系统表包含为每个文本搜索配置的解析器的每个输出符号类型，显示哪个文本搜索字典应该被咨询、以什么顺序搜索的记录。
+
+**表 1** PG_TS_CONFIG_MAP字段
+
+| 名称         | 类型    | 引用             | 描述                         |
+| :----------- | :------ | :--------------- | :--------------------------- |
+| mapcfg       | oid     | PG_TS_CONFIG.oid | 拥有这个映射记录的PG_TS_CONFIG记录的OID。                  |
+| maptokentype | integer | -                | 由配置的解析器产生的一个符号类型值。                       |
+| mapseqno     | integer | -                | 在相同mapcfg或maptokentype值的情况下，该符号类型的顺序号。 |
+| mapdict      | oid     | PG_TS_DICT.oid   | 要咨询的文本搜索字典的OID。                                |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_DICT.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_DICT.md
new file mode 100644
index 0000000000000000000000000000000000000000..3ba943e00f75f503b744eef46f6ab1de98492a46
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_DICT.md
@@ -0,0 +1,23 @@
+---
+title: PG_TS_DICT
+summary: PG_TS_DICT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_TS_DICT
+
+PG_TS_DICT系统表包含定义文本搜索字典的记录。字典取决于文本搜索模板，该模板声明所有需要的实现函数；字典本身提供模板支持的用户可设置的参数的值。
+
+这种分工允许字典通过非权限用户创建。参数由文本字符串dictinitoption指定，参数的格式和意义取决于模板。
+
+**表 1** PG_TS_DICT字段
+
+| 名称           | 类型 | 引用               | 描述                                 |
+| :------------- | :--- | :----------------- | :----------------------------------- |
+| oid            | oid  | -                  | 行标识符（隐藏属性，必须明确选择）。 |
+| dictname       | name | -                  | 文本搜索字典名。                     |
+| dictnamespace  | oid  | PG_NAMESPACE.oid   | 包含这个字典的名称空间的OID。        |
+| dictowner      | oid  | PG_AUTHID.oid      | 字典的所有者。                       |
+| dicttemplate   | oid  | PG_TS_TEMPLATE.oid | 这个字典的文本搜索模板的OID。        |
+| dictinitoption | text | -                  | 该模板的初始化选项字符串。           |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_PARSER.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_PARSER.md
new file mode 100644
index 0000000000000000000000000000000000000000..dd3a3c6ef254734b0bf1303aea3e60153ae436d3
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_PARSER.md
@@ -0,0 +1,23 @@
+---
+title: PG_TS_PARSER
+summary: PG_TS_PARSER
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_TS_PARSER
+
+PG_TS_PARSER系统表包含定义文本解析器的记录。解析器负责分裂输入文本为词位，并且为每个词位分配标记类型。新解析器必须由数据库系统管理员创建。
+
+**表 1** PG_TS_PARSER字段
+
+| 名称         | 类型    | 引用             | 描述                                 |
+| :----------- | :------ | :--------------- | :----------------------------------- |
+| oid          | oid     | -                | 行标识符（隐藏属性；必须明确选择）。 |
+| prsname      | name    | -                | 文本搜索解析器名。                   |
+| prsnamespace | oid     | PG_NAMESPACE.oid | 包含这个解析器的名称空间的OID。      |
+| prsstart     | regproc | PG_PROC.proname  | 解析器的启动函数名。                 |
+| prstoken     | regproc | PG_PROC.proname  | 解析器的下一个标记函数名。           |
+| prsend       | regproc | PG_PROC.proname  | 解析器的关闭函数名。                 |
+| prsheadline  | regproc | PG_PROC.proname  | 解析器的标题函数名。                 |
+| prslextype   | regproc | PG_PROC.proname  | 解析器的lextype函数名。              |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_TEMPLATE.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_TEMPLATE.md
new file mode 100644
index 0000000000000000000000000000000000000000..6c36a8cf3e335e7474b33c652944e656f68f49b3
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_TEMPLATE.md
@@ -0,0 +1,20 @@
+---
+title: PG_TS_TEMPLATE
+summary: PG_TS_TEMPLATE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_TS_TEMPLATE
+
+PG_TS_TEMPLATE系统表包含定义文本搜索模板的记录。模板是文本搜索字典的类的实现框架。因为模板必须通过C语言级别的函数实现，索引新模板的创建必须由数据库系统管理员创建。
+
+**表 1** PG_TS_TEMPLATE字段
+
+| 名称          | 类型    | 引用             | 描述                                 |
+| :------------ | :------ | :--------------- | :----------------------------------- |
+| oid           | oid     | -                | 行标识符（隐藏属性；必须明确选择）。 |
+| tmplname      | name    | -                | 文本搜索模板名。                     |
+| tmplnamespace | oid     | PG_NAMESPACE.oid | 包含这个模板的名称空间的OID。        |
+| tmplinit      | regproc | PG_PROC.proname  | 模板的初始化函数名。                 |
+| tmpllexize    | regproc | PG_PROC.proname  | 模板的lexize函数名。                 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TYPE.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TYPE.md
new file mode 100644
index 0000000000000000000000000000000000000000..e915c2357242682163de0ad9c12161e19e91c89c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TYPE.md
@@ -0,0 +1,46 @@
+---
+title: PG_TYPE
+summary: PG_TYPE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_TYPE
+
+PG_TYPE系统表存储数据类型的相关信息。
+
+**表 1** PG_TYPE字段
+
+| 名称           | 类型         | 描述                                                         |
+| :------------- | :----------- | :----------------------------------------------------------- |
+| oid            | oid          | 行标识符（隐藏属性，必须明确选择）。                         |
+| typname        | name         | 数据类型名称。                                               |
+| typnamespace   | oid          | 包含这个类型的名称空间的OID。                                |
+| typowner       | oid          | 该类型的所有者。                                             |
+| typlen         | smallint     | 对于定长类型是该类型内部表现形式的字节数目。对于变长类型是负数。<br/>-1表示一种"变长"（有长度字属性的数据）。<br/>-2表示这是一个NULL结尾的C字符串。 |
+| typbyval       | Boolean      | 指定内部传递这个类型的数值时是传值（该值为true）还是传引用（该值为false）。如果该类型的TYPLEN不是1，2，4，8， TYPBYVAL最好为false。变长类型通常是传引用。即使TYPLEN允许传值，TYPBYVAL也可以为false。 |
+| typtype        | "char"       | - 对于基础类型是b。<br/>- 对于复合类型是c（比如，一个表的行类型）。<br/>- 对于域类型是d。<br/>- 对于伪类型是p。<br/>参见typrelid和typbasetype。 |
+| typcategory    | "char"       | 是数据类型的模糊分类，可用于解析器做为数据转换的依据。       |
+| typispreferred | Boolean      | 如果为真，则数据符合TYPCATEGORY所指定的转换规则时进行转换。  |
+| typisdefined   | Boolean      | 如果定义了类型则为真，如果是一种尚未定义的类型的占位符则为假。如果为假，则除了该类型名称，名称空间和OID之外没有可靠的信息。 |
+| typdelim       | "char"       | 当分析数组输入时，分隔两个此类型数值的字符请注意该分隔符是与数组元素数据类型相关联的，而不是和数组数据类型关联。 |
+| typrelid       | oid          | 如果是复合类型（请参见typtype），则这个字段指向pg_class中定义该表的行。对于自由存在的复合类型，pg_class记录并不表示一个表，但是总需要它来查找该类型连接的pg_attribute记录。对于非复合类型为零。 |
+| typelem        | oid          | 如果不为0，则它标识pg_type里面的另外一行。当前类型可以当做一个产生类型为typelem的数组来描述。一个"真正的"数组类型是变长的（typlen= -1），但是一些定长的（typlen &gt; 0）类型也拥有非零的typelem（比如name和point）。如果一个定长类型拥有一个typelem ，则他的内部形式必须是typelem数据类型的某个数目的个数值，不能有其他数据。变长数组类型有一个该数组子过程定义的头（文件）。 |
+| typarray       | oid          | 如果不为0，则表示在pg_type中有对应的类型记录。               |
+| typinput       | regproc      | 输入转换函数（文本格式）。                                   |
+| typoutput      | regproc      | 输出转换函数（文本格式）。                                   |
+| typreceive     | regproc      | 输入转换函数（二进制格式），如果没有则为0。                  |
+| typsend        | regproc      | 输出转换函数（二进制格式），如果没有则为0。                  |
+| typmodin       | regproc      | 输入类型修改符函数，如果为0，则不支持。                      |
+| typmodout      | regproc      | 输出类型修改符函数，如果为0，则不支持。                      |
+| typanalyze     | regproc      | 自定义的ANALYZE函数，如果使用标准函数，则为0。               |
+| typalign       | "char"       | 当存储此类型的数值时要求的对齐性质。它应用于磁盘存储以及该值在PostgreSQL内部的大多数形式。如果数值是连续存放的，比如在磁盘上以完全的裸数据的形式存放时，则先在此类型的数据前填充空白，这样它就可以按照要求的界限存储。对齐引用是该序列中第一个数据的开头。可能的值包含: <br/>- c = char对齐，也就是不需要对齐。<br/>- s = short对齐（在大多数机器上是2字节）<br/>- i = int对齐（在大多数机器上是4字节）<br/>- d = double对齐（在大多数机器上是8字节，但不一定是全部）<br/>须知: <br/>对于在系统表里使用的类型，在pg_type里定义的尺寸和对齐必须和编译器在一个表示表的一行的结构里的布局一样。 |
+| typstorage     | "char"       | 指明一个变长类型（那些有typlen = -1）是否准备好应付非常规值，以及对这种属性的类型的缺省策略是什么。可能的值包含: <br/>- p: 数值总是以简单方式存储。<br/>- e: 数值可以存储在一个"次要"关系中（如果该关系有这么一个，请参见pg_class.reltoastrelid）。<br/>- m: 数值可以以内联的压缩方式存储。<br/>- x: 数值可以以内联的压缩方式或者在"次要"表里存储。<br/>须知: <br/>m域也可以移到从属表里存储，但只是最后的解决方法（e和x域先移走）。 |
+| typenotnull    | Boolean      | 该类型是否存在NOTNULL约束。目前只用于域。                    |
+| typbasetype    | oid          | 如果这是一个衍生类型（请参见typtype），则该标识作为这个类型的基础的类型。如果不是衍生类型则为零。 |
+| typtypmod      | integer      | 域使用typtypmod记录要作用到它们的基础类型上的typmod（如果基础类型不使用typmod则为-1）。如果这种类型不是域，则为-1。 |
+| typndims       | integer      | 如果一个域是数组，则typndims是数组维数的数值（也就是说，typbasetype是一个数组类型；域的typelem将匹配基本类型的typelem）。非域非数组域为零。 |
+| typcollation   | oid          | 指定类型的排序规则。如果为0，则表示不支持排序。              |
+| typdefaultbin  | pg_node_tree | 如果为非NULL，则它是该类型缺省表达式的nodeToString() 表现形式。目前这个字段只用于域。 |
+| typdefault     | text         | 如果某类型没有相关缺省值，则取值是NULL。<br/>- 如果typdefaultbin为非NULL，则typdefault必须包含一个typdefaultbin代表的缺省表达式。<br/>- 如果typdefaultbin为NULL但typdefault不是，typdefault则是该类型缺省值的外部表现形式，可以把它作为该类型的输入，转换器生成一个常量。 |
+| typacl         | aclitem[]    | 访问权限。                                                   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_USER_MAPPING.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_USER_MAPPING.md
new file mode 100644
index 0000000000000000000000000000000000000000..3cad12fcc31275df01f4aefca3510cbb9270c91c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_USER_MAPPING.md
@@ -0,0 +1,21 @@
+---
+title: PG_USER_MAPPING
+summary: PG_USER_MAPPING
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_USER_MAPPING
+
+PG_USER_MAPPING系统表存储从本地用户到远程的映射。
+
+需要有系统管理员权限才可以访问此系统表。普通用户可以使用视图PG_USER_MAPPINGS进行查询。
+
+**表 1** PG_USER_MAPPING字段
+
+| 名称      | 类型   | 引用                  | 描述                                                |
+| :-------- | :----- | :-------------------- | :-------------------------------------------------- |
+| oid       | oid    | -                     | 行标识符（隐藏属性，必须明确选择）。                |
+| umuser    | oid    | PG_AUTHID.oid         | 被映射的本地用户的OID，如果用户映射是公共的则为0。  |
+| umserver  | oid    | PG_FOREIGN_SERVER.oid | 包含这个映射的外部服务器的OID。                     |
+| umoptions | text[] | -                     | 用户映射指定选项，使用"keyword=value"格式的字符串。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_USER_STATUS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_USER_STATUS.md
new file mode 100644
index 0000000000000000000000000000000000000000..dca9bdd5885301b6bc6dfc41ca8debfbe167c9b6
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_USER_STATUS.md
@@ -0,0 +1,23 @@
+---
+title: PG_USER_STATUS
+summary: PG_USER_STATUS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_USER_STATUS
+
+PG_USER_STATUS系统表提供了访问数据库用户的状态。需要有系统管理员权限才可以访问此系统表。
+
+**表 1** PG_USER_STATUS字段
+
+| 名称            | 类型                     | 描述 |
+| :-------------- | :----------------------- | :---------------------- |
+| oid | oid | 行标识符（隐含字段，必须明确选择）。 |
+| roloid          | oid                      | 角色的标识。          |
+| failcount       | integer                  | 尝试失败次数。        |
+| locktime        | timestamp with time zone | 角色被锁定的时间点。  |
+| rolstatus       | smallint                 | 角色的状态。<br/>- 0: 正常状态。<br/>- 1: 由于登录失败次数超过阈值被锁定了一定的时间。<br/>- 2: 被管理员锁定。 |
+| permspace       | bigint                   | 角色已经使用的永久表存储空间大小。                           |
+| tempspace       | bigint                   | 角色已经使用的临时表存储空间大小。                           |
+| passwordexpired | smallint                 | 密码是否失效。<br/>- 0: 密码有效。<br/>- 1: 密码失效。       |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_WORKLOAD_GROUP.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_WORKLOAD_GROUP.md
new file mode 100644
index 0000000000000000000000000000000000000000..da35ed62e3cffd8dfc5dde1f84e0e97a756201d6
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_WORKLOAD_GROUP.md
@@ -0,0 +1,19 @@
+---
+title: PG_WORKLOAD_GROUP
+summary: PG_WORKLOAD_GROUP
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_WORKLOAD_GROUP
+
+PG_WORKLOAD_GROUP系统表提供了数据库负载组的信息。
+
+**表 1** PG_WORKLOAD_GROUP字段
+
+| 名称            | 类型    | 描述                                 |
+| :-------------- | :------ | :----------------------------------- |
+| oid             | oid     | 行标识符（隐藏属性，必须明确选择）。 |
+| workload_gpname | name    | 负载组名称。                         |
+| respool_oid     | oid     | 绑定到的资源池的id。                 |
+| act_statements  | integer | 负载组内最大的活跃语句数。           |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PLAN_TABLE_DATA.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PLAN_TABLE_DATA.md
new file mode 100644
index 0000000000000000000000000000000000000000..b2da0f5be56181cb2ad4e5364b4ab40b12b9d816
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/PLAN_TABLE_DATA.md
@@ -0,0 +1,32 @@
+---
+title: PLAN_TABLE_DATA
+summary: PLAN_TABLE_DATA
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PLAN_TABLE_DATA
+
+PLAN_TABLE_DATA存储了用户通过执行EXPLAIN PLAN收集到的计划信息。与PLAN_TABLE视图不同的是PLAN_TABLE_DATA表存储了所有session和user执行EXPLAIN PLAN收集的计划信息。
+
+**表 1** PLAN_TABLE_DATA字段
+
+| 名称         | 类型           | 描述                              |
+| :----------- | :------------- | :-------------------------------- |
+| session_id   | text           | 表示插入该条数据的会话，由服务线程启动时间戳和服务线程ID组成。受非空约束限制。 |
+| user_id      | oid            | 用户ID，用于标识触发插入该条数据的用户。受非空约束限制。     |
+| statement_id | varchar2(30)   | 用户输入的查询标签。                                         |
+| plan_id      | bigint         | 查询标识。该标识在计划生成阶段自动产生，供内核工程师调试使用。 |
+| id           | int            | 计划中的节点编号。                                           |
+| operation    | varchar2(30)   | 操作描述。                                                   |
+| options      | varchar2(255)  | 操作选项。                                                   |
+| object_name  | name           | 操作对应的对象名，来自于用户定义。                           |
+| object_type  | varchar2(30)   | 对象类型。                                                   |
+| object_owner | name           | 对象所属schema，来自于用户定义。                             |
+| projection   | varchar2(4000) | 操作输出的列信息。                                           |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+>
+> - PLAN_TABLE_DATA中包含了当前节点所有用户、所有会话的数据，仅管理员有访问权限。普通用户可以通过PLAN_TABLE视图查看属于自己的数据。
+> - PLAN_TABLE_DATA中的数据是用户通过执行EXPLAIN PLAN命令后由系统自动插入表中，因此禁止用户手动对数据进行插入或更新，否则会引起表中的数据混乱。需要对表中数据删除时，建议通过PLAN_TABLE视图。
+> - statement_id、object_name、object_owner和projection字段内容遵循用户定义的大小写存储，其它字段内容采用大写存储。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/STATEMENT_HISTORY.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/STATEMENT_HISTORY.md
new file mode 100644
index 0000000000000000000000000000000000000000..b856efe766b514063306b2e6b9614c5aacf8a694
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-catalogs/STATEMENT_HISTORY.md
@@ -0,0 +1,72 @@
+---
+title: STATEMENT_HISTORY
+summary: STATEMENT_HISTORY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# STATEMENT_HISTORY
+
+获得当前节点的执行语句的信息。查询系统表必须具有sysadmin权限。只可在系统库中查询到结果，用户库中无法查询。
+
+对于此系统表查询有如下约束：
+
+- 必须在postgres库内查询，其它库中不存数据。
+- 此系统表受track_stmt_stat_level控制，默认为”OFF,L0”，第一部分控制Full SQL，第二部分控制Slow SQL，具体字段记录级别见下表。
+- 对于Slow SQL，当track_stmt_stat_level的值为非OFF时，且SQL执行时间超过log_min_duration_statement，会记录为慢SQL。
+
+**表 1** STATEMENT_HISTORY字段
+
+| 名称                 | 类型                     | 描述                                                         | 记录级别 |
+| :------------------- | :----------------------- | :----------------------------------------------------------- | :------- |
+| db_name              | name                     | 数据库名称。                                                 | L0       |
+| schema_name          | name                     | schema名称。                                                 | L0       |
+| origin_node          | integer                  | 节点名称。                                                   | L0       |
+| user_name            | name                     | 用户名。                                                     | L0       |
+| application_name     | text                     | 用户发起的请求的应用程序名称。                               | L0       |
+| client_addr          | text                     | 用户发起的请求的客户端地址。                                 | L0       |
+| client_port          | integer                  | 用户发起的请求的客户端端口。                                 | L0       |
+| unique_query_id      | bigint                   | 归一化SQL ID。                                               | L0       |
+| debug_query_id       | bigint                   | 唯一SQL ID。                                                 | L0       |
+| query                | text                     | 归一化SQL。                                                  | L0       |
+| start_time           | timestamp with time zone | 语句启动的时间。                                             | L0       |
+| finish_time          | timestamp with time zone | 语句结束的时间。                                             | L0       |
+| slow_sql_threshold   | bigint                   | 语句执行时慢SQL的标准。                                      | L0       |
+| transaction_id       | bigint                   | 事务ID。                                                     | L0       |
+| thread_id            | bigint                   | 执行线程ID。                                                 | L0       |
+| session_id           | bigint                   | 用户session id。                                             | L0       |
+| n_soft_parse         | bigint                   | 软解析次数，n_soft_parse + n_hard_parse可能大于n_calls，因为子查询未计入n_calls。 | L0       |
+| n_hard_parse         | bigint                   | 硬解析次数，n_soft_parse + n_hard_parse可能大于n_calls，因为子查询未计入n_calls。 | L0       |
+| query_plan           | text                     | 语句执行计划。                                               | L1       |
+| n_returned_rows      | bigint                   | SELECT返回的结果集行数。                                     | L0       |
+| n_tuples_fetched     | bigint                   | 随机扫描行。                                                 | L0       |
+| n_tuples_returned    | bigint                   | 顺序扫描行。                                                 | L0       |
+| n_tuples_inserted    | bigint                   | 插入行。                                                     | L0       |
+| n_tuples_updated     | bigint                   | 更新行。                                                     | L0       |
+| n_tuples_deleted     | bigint                   | 删除行。                                                     | L0       |
+| n_blocks_fetched     | bigint                   | buffer的块访问次数。                                         | L0       |
+| n_blocks_hit         | bigint                   | buffer的块命中次数。                                         | L0       |
+| db_time              | bigint                   | 有效的DB时间花费，多线程将累加（单位：微秒）。               | L0       |
+| cpu_time             | bigint                   | CPU时间（单位：微秒）。                                      | L0       |
+| execution_time       | bigint                   | 执行器内执行时间（单位：微秒）。                             | L0       |
+| parse_time           | bigint                   | SQL解析时间（单位：微秒）。                                  | L0       |
+| plan_time            | bigint                   | SQL生成计划时间（单位：微秒）。                              | L0       |
+| rewrite_time         | bigint                   | SQL重写时间（单位：微秒）。                                  | L0       |
+| pl_execution_time    | bigint                   | plpgsql上的执行时间（单位：微秒）。                          | L0       |
+| pl_compilation_time  | bigint                   | plpgsql上的编译时间（单位：微秒）。                          | L0       |
+| data_io_time         | bigint                   | IO上的时间花费（单位：微秒）。                               | L0       |
+| net_send_info        | text                     | 通过物理连接发送消息的网络状态，包含时间（微秒）、调用次数、吞吐量（字节）。通过该字段可以分析SQL在分布式系统下的网络开销，单机模式下不支持该字段。例如：{“time”:xxx, “n_calls”:xxx, “size”:xxx}。 | L0       |
+| net_recv_info        | text                     | 通过物理连接接收消息的网络状态，包含时间（微秒）、调用次数、吞吐量（字节）。通过该字段可以分析SQL在分布式系统下的网络开销，单机模式下不支持该字段。例如：{“time”:xxx, “n_calls”:xxx, “size”:xxx}。 | L0       |
+| net_stream_send_info | text                     | 通过逻辑连接发送消息的网络状态，包含时间（微秒）、调用次数、吞吐量（字节）。通过该字段可以分析SQL在分布式系统下的网络开销，单机模式下不支持该字段。例如：{“time”:xxx, “n_calls”:xxx, “size”:xxx}。 | L0       |
+| net_stream_recv_info | text                     | 通过逻辑连接接收消息的网络状态，包含时间（微秒）、调用次数、吞吐量（字节）。通过该字段可以分析SQL在分布式系统下的网络开销，单机模式下不支持该字段。例如：{“time”:xxx, “n_calls”:xxx, “size”:xxx}。 | L0       |
+| lock_count           | bigint                   | 加锁次数。                                                   | L0       |
+| lock_time            | bigint                   | 加锁耗时。                                                   | L1       |
+| lock_wait_count      | bigint                   | 加锁等待次数。                                               | L0       |
+| lock_wait_time       | bigint                   | 加锁等待耗时。                                               | L1       |
+| lock_max_count       | bigint                   | 最大持锁数量。                                               | L0       |
+| lwlock_count         | bigint                   | 轻量级加锁次数（预留）。                                     | L0       |
+| lwlock_wait_count    | bigint                   | 轻量级等锁次数。                                             | L0       |
+| lwlock_time          | bigint                   | 轻量级加锁时间（预留）。                                     | L1       |
+| lwlock_wait_time     | bigint                   | 轻量级等锁时间。                                             | L1       |
+| details              | bytea                    | 语句锁事件的列表，该列表按时间书序记录事件，记录的数量受参数track_stmt_details_size的影响。<br />事件包括：<br />- 加锁开始<br />- 加锁结束<br />- 等锁开始<br />- 等锁结束<br />- 放锁开始<br />- 放锁结束<br />- 轻量级等锁开始<br />- 轻量级等锁结束 | L2       |
+| is_slow_sql          | boolean                  | 该SQL是否为slow SQL。                                        | L0       |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GET_GLOBAL_PREPARED_XACTS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GET_GLOBAL_PREPARED_XACTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..f6d9ada6012a206c436386d03e2d4613ff9380fd
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GET_GLOBAL_PREPARED_XACTS.md
@@ -0,0 +1,10 @@
+---
+title: GET_GLOBAL_PREPARED_XACTS
+summary: GET_GLOBAL_PREPARED_XACTS
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# GET_GLOBAL_PREPARED_XACTS（废弃）
+
+集中式及MogDB不支持该视图。
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_AUDITING.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_AUDITING.md
new file mode 100644
index 0000000000000000000000000000000000000000..0046f0f06878652170241a0530b047863bfe0fa1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_AUDITING.md
@@ -0,0 +1,22 @@
+---
+title: GS_AUDITING
+summary: GS_AUDITING
+author: Guo Huan
+date: 2021-06-07
+---
+
+# GS_AUDITING
+
+GS_AUDITING视图显示对数据库相关操作的所有审计信息。需要有系统管理员或安全策略管理员权限才可以访问此视图。
+
+**表 1** GS_AUDITING字段
+
+| 名称        | 类型    | 描述                                                         |
+| :---------- | :------ | :----------------------------------------------------------- |
+| polname     | name    | 策略名称，需要唯一，不可重复。                               |
+| pol_type    | text    | 审计策略类型，值为‘access’或者‘privilege’。<br />- access：表示审计DML操作。<br />- privilege：表示审计DDL操作。 |
+| polenabled  | boolean | 用来表示策略启动开关。<br />- t（true）：表示启动。<br />- f（false）：表示不启动。 |
+| access_type | bigint  | DML数据库操作相关类型。例如SELECT、INSERT、DELETE等。        |
+| label_name  | name    | 资源标签名称。对应系统表gs_auditing_policy中的polname字段。  |
+| priv_object | name    | 用来描述数据库资产的路径。                                   |
+| filter_name | text    | 过滤条件的逻辑字符串。                                       |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_AUDITING_ACCESS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_AUDITING_ACCESS.md
new file mode 100644
index 0000000000000000000000000000000000000000..cb0329f261a47024fe3df32feb8db753a1ea2e2d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_AUDITING_ACCESS.md
@@ -0,0 +1,22 @@
+---
+title: GS_AUDITING_ACCESS
+summary: GS_AUDITING_ACCESS
+author: Guo Huan
+date: 2021-06-07
+---
+
+# GS_AUDITING_ACCESS
+
+GS_AUDITING_ACCESS视图显示对数据库DML相关操作的所有审计信息。需要有系统管理员或安全策略管理员权限才可以访问此视图。
+
+**表 1** GS_AUDITING_ACCESS字段
+
+| 名称          | 类型    | 描述                                                        |
+| :------------ | :------ | :---------------------------------------------------------- |
+| polname       | name    | 策略名称，需要唯一，不可重复。                              |
+| pol_type      | text    | 审计策略类型，值为‘access’，表示审计DML操作。               |
+| polenabled    | boolean | 用来表示策略启动开关。                                      |
+| access_type   | name    | DML数据库操作相关类型。例如SELECT、INSERT、DELETE等。       |
+| label_name    | name    | 资源标签名称。对应系统表gs_auditing_policy中的polname字段。 |
+| access_object | text    | 用来描述数据库资产的路径。                                  |
+| filter_name   | text    | 过滤条件的逻辑字符串。                                      |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_AUDITING_PRIVILEGE.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_AUDITING_PRIVILEGE.md
new file mode 100644
index 0000000000000000000000000000000000000000..d6a291323af74908fb361a06d936514e4313c3ea
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_AUDITING_PRIVILEGE.md
@@ -0,0 +1,20 @@
+---
+title: GS_AUDITING_PRIVILEGE
+summary: GS_AUDITING_PRIVILEGE
+author: Guo Huan
+date: 2021-06-07
+---
+
+# GS_AUDITING_PRIVILEGE
+
+GS_AUDITING_PRIVILEGE视图显示对数据库DDL相关操作的所有审计信息。需要有系统管理员或安全策略管理员权限才可以访问此视图。
+
+| 名称        | 类型    | 描述                                                        |
+| :---------- | :------ | :---------------------------------------------------------- |
+| polname     | name    | 策略名称，需要唯一，不可重复。                              |
+| pol_type    | text    | 审计策略类型，值为‘privilege’，表示审计DDL 操作。           |
+| polenabled  | boolean | 用来表示策略启动开关。                                      |
+| access_type | name    | DDL数据库操作相关类型。例如CREATE、ALTER、DROP等。          |
+| label_name  | name    | 资源标签名称。对应系统表gs_auditing_policy中的polname字段。 |
+| priv_object | text    | 带有数据库对象的全称域名。                                  |
+| filter_name | text    | 过滤条件的逻辑字符串。                                      |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_CLUSTER_RESOURCE_INFO.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_CLUSTER_RESOURCE_INFO.md
new file mode 100644
index 0000000000000000000000000000000000000000..d9845729e4fecaaee34efe58bfb1051883aacccf
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_CLUSTER_RESOURCE_INFO.md
@@ -0,0 +1,22 @@
+---
+title: GS_CLUSTER_RESOURCE_INFO
+summary: GS_CLUSTER_RESOURCE_INFO
+author: Guo Huan
+date: 2021-06-07
+---
+
+# GS_CLUSTER_RESOURCE_INFO
+
+GS_CLUSTER_RESOURCE_INFO视图显示的是所有DN资源的汇总信息。该视图需要设置enable_dynamic_workload=on才能查询，并且该视图不支持在DN执行。查询该视图需要sysadmin权限。
+
+**表 1** GS_CLUSTER_RESOURCE_INFO字段
+
+| 名称          | 类型    | 描述                     |
+| :------------ | :------ | :----------------------- |
+| min_mem_util  | integer | DN最小内存使用率。       |
+| max_mem_util  | integer | DN最大内存使用率。       |
+| min_cpu_util  | integer | DN最小CPU使用率。        |
+| max_cpu_util  | integer | DN最大CPU使用率。        |
+| min_io_util   | integer | DN最小IO使用率。         |
+| max_io_util   | integer | DN最大IO使用率。         |
+| used_mem_rate | integer | 物理节点最大内存使用率。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_FILE_STAT.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_FILE_STAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..7a3bedc627ea45790463464fb8f9ecb333d5471c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_FILE_STAT.md
@@ -0,0 +1,28 @@
+---
+title: GS_FILE_STAT
+summary: GS_FILE_STAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_FILE_STAT
+
+GS_FILE_STAT视图通过对数据文件IO的统计，反映数据的IO性能，用以发现IO操作异常等性能问题。
+
+**表 1** GS_FILE_STAT字段
+
+| 名称      | 类型   | 描述                           |
+| :-------- | :----- | :----------------------------- |
+| filenum   | oid    | 文件标识。                     |
+| dbid      | oid    | 数据库标识。                   |
+| spcid     | oid    | 表空间标识。                   |
+| phyrds    | bigint | 读物理文件的数目。             |
+| phywrts   | bigint | 写物理文件的数目。             |
+| phyblkrd  | bigint | 读物理文件块的数目。           |
+| phyblkwrt | bigint | 写物理文件块的数目。           |
+| readtim   | bigint | 读文件的总时长，单位微秒。     |
+| writetim  | bigint | 写文件的总时长，单位微秒。     |
+| avgiotim  | bigint | 读写文件的平均时长，单位微秒。 |
+| lstiotim  | bigint | 最后一次读文件时长，单位微秒。 |
+| miniotim  | bigint | 读写文件的最小时长，单位微秒。 |
+| maxiowtm  | bigint | 读写文件的最大时长，单位微秒。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_INSTANCE_TIME.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_INSTANCE_TIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..0e2757715a6a78d7397c1e907120dc477837d4c1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_INSTANCE_TIME.md
@@ -0,0 +1,29 @@
+---
+title: GS_INSTANCE_TIME
+summary: GS_INSTANCE_TIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_INSTANCE_TIME
+
+提供当前集节点下的各种时间消耗信息，主要分为以下类型：
+
+- DB_TIME：作业在多核下的有效时间花销。
+- CPU_TIME：CPU的时间花销。
+- EXECUTION_TIME：执行器内的时间花销。
+- PARSE_TIME：SQL解析的时间花销。
+- PLAN_TIME：生成Plan的时间花销。
+- REWRITE_TIME：SQL重写的时间花销。
+- PL_EXECUTION_TIME：plpgsql（存储过程）执行的时间花销。
+- PL_COMPILATION_TIME：plpgsql（存储过程）编译的时间花销。
+- NET_SEND_TIME：网络上的时间花销。
+- DATA_IO_TIME：IO的时间花销。
+
+**表 1** GS_INSTANCE_TIME字段
+
+| **名称**  | **类型** | **描述**               |
+| :-------- | :------- | :--------------------- |
+| stat_id   | integer  | 统计编号。             |
+| stat_name | text     | 类型名称。             |
+| value     | bigint   | 时间值（单位: 微秒）。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_LABELS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_LABELS.md
new file mode 100644
index 0000000000000000000000000000000000000000..0ad8bde349d2ffce8654f8fe21292ce86f9e01d6
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_LABELS.md
@@ -0,0 +1,19 @@
+---
+title: GS_LABELS
+summary: GS_LABELS
+author: Guo Huan
+date: 2021-06-07
+---
+
+# GS_LABELS
+
+GS_LABELS视图显示所有已配置的资源标签信息。需要有系统管理员或安全策略管理员权限才可以访问此视图。
+
+| 名称       | 类型 | 描述                                                         |
+| :--------- | :--- | :----------------------------------------------------------- |
+| labelname  | name | 资源标签的名称。                                             |
+| labeltype  | name | 资源标签的类型。对应系统表GS_POLICY_LABEL中的labeltype字段。 |
+| fqdntype   | name | 数据库资源的类型。如table、schema、index等。                 |
+| schemaname | name | 数据库资源所属的schema名称。                                 |
+| fqdnname   | name | 数据库资源名称。                                             |
+| columnname | name | 数据库资源列名称，若标记的数据库资源不为表的列则该项为空。   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_MASKING.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_MASKING.md
new file mode 100644
index 0000000000000000000000000000000000000000..74a67376dd86256f1758d8f77c010b0317207b6d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_MASKING.md
@@ -0,0 +1,19 @@
+---
+title: GS_MASKING
+summary: GS_MASKING
+author: Guo Huan
+date: 2021-06-07
+---
+
+# GS_MASKING
+
+GS_MASKING视图显示所有已配置的动态脱敏策略信息。需要有系统管理员或安全策略管理员权限才可以访问此视图。
+
+| 名称           | 类型    | 描述                     |
+| :------------- | :------ | :----------------------- |
+| polname        | name    | 脱敏策略名称。           |
+| polenabled     | boolean | 脱敏策略开关。           |
+| maskaction     | name    | 脱敏函数。               |
+| labelname      | name    | 脱敏函数作用的标签名称。 |
+| masking_object | text    | 脱敏数据库资源对象。     |
+| filter_name    | text    | 过滤条件的逻辑表达式。   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_MATVIEWS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_MATVIEWS.md
new file mode 100644
index 0000000000000000000000000000000000000000..991b29f599ab90cc56afda9eb32e409f710f6cda
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_MATVIEWS.md
@@ -0,0 +1,21 @@
+---
+title: GS_MATVIEWS
+summary: GS_MATVIEWS
+author: Guo Huan
+date: 2021-06-07
+---
+
+# GS_MATVIEWS
+
+GS_MATVIEWS视图提供了关于数据库中每一个物化视图的信息。
+
+**表 1** GS_MATVIEWS字段
+
+| 名称         | 类型    | 引用                  | 描述                                                   |
+| :----------- | :------ | :-------------------- | :----------------------------------------------------- |
+| schemaname   | name    | PG_NAMESPACE.nspname  | 物化视图的模式名。                                     |
+| matviewname  | name    | PG_CLASS.relname      | 物化视图名。                                           |
+| matviewowner | name    | PG_AUTHID.Erolname    | 物化视图的所有者。                                     |
+| tablespace   | name    | PG_TABLESPACE.spcname | 物化视图的表空间名（如果使用数据库默认表空间则为空）。 |
+| hasindexes   | boolean | -                     | 如果物化视图有（或者最近有过）任何索引，则此列为真。   |
+| definition   | text    | -                     | 物化视图的定义（一个重构的SELECT查询）。               |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_OS_RUN_INFO.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_OS_RUN_INFO.md
new file mode 100644
index 0000000000000000000000000000000000000000..2b9668a3e35311b2efe04ad747a68e123f911692
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_OS_RUN_INFO.md
@@ -0,0 +1,20 @@
+---
+title: GS_OS_RUN_INFO
+summary: GS_OS_RUN_INFO
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_OS_RUN_INFO
+
+GS_OS_RUN_INFO视图显示当前操作系统运行的状态信息。
+
+**表 1** GS_OS_RUN_INFO字段
+
+| 名称       | 类型    | 描述                               |
+| :--------- | :------ | :--------------------------------- |
+| id         | integer | 编号。                             |
+| name       | text    | 操作系统运行状态名称。             |
+| value      | numeric | 操作系统运行状态值。               |
+| comments   | text    | 操作系统运行状态注释。             |
+| cumulative | Boolean | 操作系统运行状态的值是否为累加值。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_REDO_STAT.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_REDO_STAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..10d8e46c8f427618e0594a1c0f1a1d45c78f4df4
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_REDO_STAT.md
@@ -0,0 +1,22 @@
+---
+title: GS_REDO_STAT
+summary: GS_REDO_STAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_REDO_STAT
+
+GS_REDO_STAT视图用于统计回话线程日志回放情况。
+
+**表 1** GS_REDO_STAT字段
+
+| 名称      | 类型   | 描述                                     |
+| :-------- | :----- | :--------------------------------------- |
+| phywrts   | bigint | 日志回放过程中写数据的次数。             |
+| phyblkwrt | bigint | 日志回放过程中写数据的块数。             |
+| writetim  | bigint | 日志回放过程中写数据所耗的总时间。       |
+| avgiotim  | bigint | 日志回放过程中写一次数据的平均消耗时间。 |
+| lstiotim  | bigint | 日志回放过程中最后一次写数据消耗的时间。 |
+| miniotim  | bigint | 日志回放过程中单次写数据消耗的最短时间。 |
+| maxiowtm  | bigint | 日志回放过程中单次写数据消耗的最长时间。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_CPU_STATISTICS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_CPU_STATISTICS.md
new file mode 100644
index 0000000000000000000000000000000000000000..a71aea1b0ba160a1f9471f299d816ae5319e8b6b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_CPU_STATISTICS.md
@@ -0,0 +1,25 @@
+---
+title: GS_SESSION_CPU_STATISTICS
+summary: GS_SESSION_CPU_STATISTICS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_SESSION_CPU_STATISTICS
+
+GS_SESSION_CPU_STATISTICS视图显示当前用户执行的正在运行的复杂作业的CPU使用的负载管理信息。
+
+**表 1** GS_SESSION_CPU_STATISTICS字段
+
+| 名称           | 类型                     | 描述                                        |
+| :------------- | :----------------------- | :------------------------------------------ |
+| datid          | oid                      | 连接后端的数据库OID。                       |
+| usename        | name                     | 登录到该后端的用户名。                      |
+| pid            | bigint                   | 后端线程ID。                                |
+| start_time     | timestamp with time zone | 语句执行的开始时间。                        |
+| min_cpu_time   | bigint                   | 语句在数据库节点上的最小CPU时间，单位为ms。 |
+| max_cpu_time   | bigint                   | 语句在数据库节点上的最大CPU时间，单位为ms。 |
+| total_cpu_time | bigint                   | 语句在数据库节点上的CPU总时间，单位为ms。   |
+| query          | text                     | 正在执行的语句                              |
+| node_group     | text                     | 该字段不支持。                              |
+| top_cpu_dn     | text                     | cpu使用量信息。                             |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY.md
new file mode 100644
index 0000000000000000000000000000000000000000..482de222ff65410613e289defb4e4af2a2cd29ee
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY.md
@@ -0,0 +1,19 @@
+---
+title: GS_SESSION_MEMORY
+summary: GS_SESSION_MEMORY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_SESSION_MEMORY
+
+GS_SESSION_MEMORY视图统计Session级别的内存使用情况，包含执行作业在数据节点上Postgres线程分配的所有内存。当GUC参数enable_memory_limit的值为off时，本视图不可用。
+
+**表 1** GS_SESSION_MEMORY字段
+
+| 名称     | 类型    | 描述                                               |
+| :------- | :------ | :---------------------- |
+| sessid   | text    | 线程启动时间+线程标识。                            |
+| init_mem | integer | 当前正在执行作业进入执行器前已分配的内存，单位MB。 |
+| used_mem | integer | 当前正在执行作业已分配的内存，单位MB。             |
+| peak_mem | integer | 当前正在执行作业已分配的内存峰值，单位MB。         |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY_CONTEXT.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY_CONTEXT.md
new file mode 100644
index 0000000000000000000000000000000000000000..6d6525239c9d60a4e7c9da3e6a69e07baaf47ad1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY_CONTEXT.md
@@ -0,0 +1,25 @@
+---
+title: GS_SESSION_MEMORY_CONTEXT
+summary: GS_SESSION_MEMORY_CONTEXT
+author: Guo Huan
+date: 2021-06-07
+---
+
+# GS_SESSION_MEMORY_CONTEXT
+
+GS_SESSION_MEMORY_CONTEXT视图统计所有的会话的内存使用情况，以MemoryContext节点来统计。该视图仅在开启线程池（enable_thread_pool = on）时生效。当GUC参数enable_memory_limit的值为off时，本视图不可用。
+
+其中内存上下文“TempSmallContextGroup”，记录当前线程中所有内存上下文字段“totalsize”小于8192字节的信息汇总，并且内存上下文统计计数记录到“usedsize”字段中。所以在视图中，“TempSmallContextGroup”内存上下文中的“totalsize”和“freesize”是该线程中所有内存上下文“totalsize”小于8192字节的汇总总和，usedsize字段表示统计的内存上下文个数。
+
+**表 1** GS_SESSION_MEMORY_CONTEXT字段
+
+| 名称        | 类型     | 描述                                                         |
+| :---------- | :------- | :----------------------------------------------------------- |
+| sessid      | text     | 会话启动时间+会话标识（字符串信息为timestamp.sessionid）。   |
+| threadid    | bigint   | 会话绑定的线程标识，如果未绑定线程，该值为-1。               |
+| contextname | text     | 内存上下文名称。                                             |
+| level       | smallint | 当前上下文在整体内存上下文中的层级。                         |
+| parent      | text     | 父内存上下文名称。                                           |
+| totalsize   | bigint   | 当前内存上下文的内存总数，单位Byte。                         |
+| freesize    | bigint   | 当前内存上下文中已释放的内存总数，单位Byte。                 |
+| usedsize    | bigint   | 当前内存上下文中已使用的内存总数，单位Byte；“TempSmallContextGroup”内存上下文中该字段含义为统计计数。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY_DETAIL.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY_DETAIL.md
new file mode 100644
index 0000000000000000000000000000000000000000..a0225ee2e77e170c9ce7bd4e914b481d80a9b42c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY_DETAIL.md
@@ -0,0 +1,27 @@
+---
+title: GS_SESSION_MEMORY_DETAIL
+summary: GS_SESSION_MEMORY_DETAIL
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_SESSION_MEMORY_DETAIL
+
+GS_SESSION_MEMORY_DETAIL统计线程的内存使用情况，以MemoryContext节点来统计。当开启线程池 (enable_thread_pool = on) 时，该视图包含所有的线程和会话的内存使用情况。当GUC参数enable_memory_limit的值为off时，本视图不可用。
+
+其中内存上下文"TempSmallContextGroup"，记录当前线程中所有内存上下文字段"totalsize"小于8192字节的信息汇总，并且内存上下文统计计数记录到"usedsize"字段中。所以在视图中，"TempSmallContextGroup"内存上下文中的"totalsize"和"freesize"是该线程中所有内存上下文"totalsize"小于8192字节的汇总总和，usedsize字段表示统计的内存上下文个数。
+
+可通过"select * from gs_session_memctx_detail(threadid, ");"将某个线程所有内存上下文信息记录到"/tmp/dumpmem"目录下的"threadid_timestamp.log"文件中。其中threadid可通过下表sessid中获得。
+
+**表 1** GS_SESSION_MEMORY_DETAIL字段
+
+| 名称        | 类型     | 描述                |
+| :---------- | :------- | :------------------|
+| sessid      | text     | 线程启动时间+线程标识（字符串信息为timestamp.threadid）。    |
+| sesstype    | text     | 线程名称。                                                   |
+| contextname | text     | 内存上下文名称。                                             |
+| level       | smallint | 当前上下文在整体内存上下文中的层级。                         |
+| parent      | text     | 父内存上下文名称。                                           |
+| totalsize   | bigint   | 当前内存上下文的内存总数，单位Byte。                         |
+| freesize    | bigint   | 当前内存上下文中已释放的内存总数，单位Byte。                 |
+| usedsize    | bigint   | 当前内存上下文中已使用的内存总数，单位Byte；"TempSmallContextGroup"内存上下文中该字段含义为统计计数。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY_STATISTICS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY_STATISTICS.md
new file mode 100644
index 0000000000000000000000000000000000000000..27a53449c322b06be7584ab5fdcec0ae016147e3
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY_STATISTICS.md
@@ -0,0 +1,25 @@
+---
+title: GS_SESSION_MEMORY_STATISTICS
+summary: GS_SESSION_MEMORY_STATISTICS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_SESSION_MEMORY_STATISTICS
+
+GS_SESSION_MEMORY_STATISTICS视图显示和当前用户执行复杂作业正在运行时的负载管理内存使用的信息。
+
+**表 1** GS_SESSION_MEMORY_STATISTICS字段
+
+| 名称            | 类型                     | 描述                                                         |
+| :-------------- | :----------------------- | :-------------------------------|
+| datid           | oid                      | 连接后端的数据库OID。                                        |
+| usename         | name                     | 登录到该后端的用户名。                                       |
+| pid             | bigint                   | 后端线程ID。                                                 |
+| start_time      | timestamp with time zone | 语句执行的开始时间。                                         |
+| min_peak_memory | integer                  | 语句在数据库节点上的最小内存峰值大小，单位MB。               |
+| max_peak_memory | integer                  | 语句在数据库节点上的最大内存峰值大小，单位MB。               |
+| spill_info      | text                     | 语句在数据库节点上的下盘信息: <br/>None: 数据库节点均未下盘。<br/>All: 数据库节点均下盘。<br/>[a:b]: 数量为b个数据库节点中有a个数据库节点下盘。 |
+| query           | text                     | 正在执行的语句。                                             |
+| node_group      | text                     | 该字段不支持。                                               |
+| top_mem_dn      | text                     | mem使用量信息。                                              |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_STAT.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_STAT.md
new file mode 100644
index 0000000000000000000000000000000000000000..0fae2cc111fa7863f1bd364b53cdf8caa4b45cfc
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_STAT.md
@@ -0,0 +1,20 @@
+---
+title: GS_SESSION_STAT
+summary: GS_SESSION_STAT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_SESSION_STAT
+
+GS_SESSION_STAT视图以会话线程或AutoVacuum线程为单位，统计会话状态信息。
+
+**表 1** GS_SESSION_STAT字段
+
+| 名称     | 类型    | 描述                    |
+| :------- | :------ | :---------------------- |
+| sessid   | text    | 线程标识+线程启动时间。 |
+| statid   | integer | 统计编号。              |
+| statname | text    | 统计会话名称。          |
+| statunit | text    | 统计会话单位。          |
+| value    | bigint  | 统计会话值。            |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_TIME.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_TIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..bd7b4d5702e880ee7a0e7dedb53d3f2704bce273
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_TIME.md
@@ -0,0 +1,19 @@
+---
+title: GS_SESSION_TIME
+summary: GS_SESSION_TIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_SESSION_TIME
+
+GS_SESSION_TIME视图用于统计会话线程的运行时间信息，及各执行阶段所消耗时间。
+
+**表 1** GS_SESSION_TIME字段
+
+| 名称      | 类型    | 描述                    |
+| :-------- | :------ | :---------------------- |
+| sessid    | text    | 线程标识+线程启动时间。 |
+| stat_id   | integer | 统计编号。              |
+| stat_name | text    | 会话类型名称。          |
+| value     | bigint  | 会话值。                |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SQL_COUNT.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SQL_COUNT.md
new file mode 100644
index 0000000000000000000000000000000000000000..832d85d3039e22f85a4c4cd4ec8f6f23ea2d5dad
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_SQL_COUNT.md
@@ -0,0 +1,45 @@
+---
+title: GS_SQL_COUNT
+summary: GS_SQL_COUNT
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_SQL_COUNT
+
+GS_SQL_COUNT视图显示数据库当前节点当前时刻执行的五类语句（SELECT、INSERT、UPDATE、DELETE、MERGE INTO）统计信息。
+
+- 普通用户查询GS_SQL_COUNT视图仅能看到该用户当前节点的统计信息；管理员权限用户查询GS_SQL_COUNT视图则能看到所有用户当前节点的统计信息。
+- 当MogDB或该节点重启时，计数将清零，并重新开始计数 。
+- 计数以节点收到的查询数为准，包括MogDB内部进行的查询。
+
+**表 1** GS_SQL_COUNT字段
+
+| 名称                | 类型   | 描述                                 |
+| :------------------ | :----- | :----------------------------------- |
+| node_name           | text   | 节点名称。                           |
+| user_name           | text   | 用户名。                             |
+| select_count        | bigint | select语句统计结果。                 |
+| update_count        | bigint | update语句统计结果。                 |
+| insert_count        | bigint | insert语句统计结果。                 |
+| delete_count        | bigint | delete语句统计结果。                 |
+| mergeinto_count     | bigint | MERGE INTO语句统计结果。             |
+| ddl_count           | bigint | DDL语句的数量。                      |
+| dml_count           | bigint | DML语句的数量。                      |
+| dcl_count           | bigint | DML语句的数量。                      |
+| total_select_elapse | bigint | 总select的时间花费（单位: 微秒）。   |
+| avg_select_elapse   | bigint | 平均select的时间花费（单位: 微秒）。 |
+| max_select_elapse   | bigint | 最大select的时间花费（单位: 微秒）。 |
+| min_select_elapse   | bigint | 最小select的时间花费（单位: 微秒）。 |
+| total_update_elapse | bigint | 总update的时间花费（单位: 微秒）。   |
+| avg_update_elapse   | bigint | 平均update的时间花费（单位: 微秒）。 |
+| max_update_elapse   | bigint | 最大update的时间花费（单位: 微秒）。 |
+| min_update_elapse   | bigint | 最小update的时间花费（单位: 微秒）。 |
+| total_insert_elapse | bigint | 总insert的时间花费（单位: 微秒）。   |
+| avg_insert_elapse   | bigint | 平均insert的时间花费（单位: 微秒）。 |
+| max_insert_elapse   | bigint | 最大insert的时间花费（单位: 微秒）。 |
+| min_insert_elapse   | bigint | 最小insert的时间花费（单位: 微秒）。 |
+| total_delete_elapse | bigint | 总delete的时间花费（单位: 微秒）。   |
+| avg_delete_elapse   | bigint | 平均delete的时间花费（单位: 微秒）。 |
+| max_delete_elapse   | bigint | 最大delete的时间花费（单位: 微秒）。 |
+| min_delete_elapse   | bigint | 最小delete的时间花费（单位: 微秒）。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_STAT_SESSION_CU.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_STAT_SESSION_CU.md
new file mode 100644
index 0000000000000000000000000000000000000000..26ed4f13757b385ec1d5f828c31a32d3e536e74c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_STAT_SESSION_CU.md
@@ -0,0 +1,18 @@
+---
+title: GS_STAT_SESSION_CU
+summary: GS_STAT_SESSION_CU
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_STAT_SESSION_CU
+
+GS_STAT_SESSION_CU视图查询MogDB各个节点，当前运行session的CU命中情况。session退出相应的统计数据会清零。MogDB重启后，统计数据也会清零。
+
+**表 1** GS_STAT_SESSION_CU字段
+
+| 名称          | 类型    | 描述             |
+| :------------ | :------ | :--------------- |
+| mem_hit       | integer | 内存命中次数。   |
+| hdd_sync_read | integer | 硬盘同步读次数。 |
+| hdd_asyn_read | integer | 硬盘异步读次数。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_THREAD_MEMORY_CONTEXT.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_THREAD_MEMORY_CONTEXT.md
new file mode 100644
index 0000000000000000000000000000000000000000..9d5679396f9bfc994980c47243cd6c21e91c1d2e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_THREAD_MEMORY_CONTEXT.md
@@ -0,0 +1,26 @@
+---
+title: GS_THREAD_MEMORY_CONTEXT
+summary: GS_THREAD_MEMORY_CONTEXT
+author: Guo Huan
+date: 2021-06-07
+---
+
+# GS_THREAD_MEMORY_CONTEXT
+
+GS_THREAD_MEMORY_CONTEXT视图统计所有的线程的内存使用情况，以MemoryContext节点来统计。该视图在关闭线程池（enable_thread_pool = off）时等价于GS_THREAD_MEMORY_CONTEXT视图。当GUC参数enable_memory_limit的值为off时，本视图不可用。
+
+其中内存上下文“TempSmallContextGroup”，记录当前线程中所有内存上下文字段“totalsize”小于8192字节的信息汇总，并且内存上下文统计计数记录到“usedsize”字段中。所以在视图中，“TempSmallContextGroup”内存上下文中的“totalsize”和“freesize”是该线程中所有内存上下文“totalsize”小于8192字节的汇总总和，usedsize字段表示统计的内存上下文个数。
+
+**表 1** GS_THREAD_MEMORY_CONTEXT字段
+
+| 名称        | 类型     | 描述                                                         |
+| :---------- | :------- | :----------------------------------------------------------- |
+| threadid    | text     | 线程启动时间+线程标识（字符串信息为timestamp.sessionid）。   |
+| tid         | bigint   | 线程标识。                                                   |
+| thrdtype    | text     | 线程类型。                                                   |
+| contextname | text     | 内存上下文名称。                                             |
+| level       | smallint | 当前上下文在整体内存上下文中的层级。                         |
+| parent      | text     | 父内存上下文名称。                                           |
+| totalsize   | bigint   | 当前内存上下文的内存总数，单位Byte。                         |
+| freesize    | bigint   | 当前内存上下文中已释放的内存总数，单位Byte。                 |
+| usedsize    | bigint   | 当前内存上下文中已使用的内存总数，单位Byte；“TempSmallContextGroup”内存上下文中该字段含义为统计计数。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_TOTAL_MEMORY_DETAIL.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_TOTAL_MEMORY_DETAIL.md
new file mode 100644
index 0000000000000000000000000000000000000000..86fb73504b4decb419d20bbcc3de410be27fcc54
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_TOTAL_MEMORY_DETAIL.md
@@ -0,0 +1,18 @@
+---
+title: GS_TOTAL_MEMORY_DETAIL
+summary: GS_TOTAL_MEMORY_DETAIL
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_TOTAL_MEMORY_DETAIL
+
+GS_TOTAL_MEMORY_DETAIL视图统计当前数据库节点使用内存的信息，单位为MB。当GUC参数enable_memory_limit的值为off时，本视图不可用。
+
+**表 1** GS_TOTAL_MEMORY_DETAIL字段
+
+| 名称         | 类型    | 描述                                                         |
+| :----------- | :------ | :----------------------------------------------------------- |
+| nodename     | text    | 节点名称。                                                   |
+| memorytype   | text    | 内存类型，包括以下几种: <br/>- max_process_memory: MogDB实例所占用的内存大小。<br/>- process_used_memory: MogDB进程所使用的内存大小。<br/>- max_dynamic_memory: 最大动态内存。<br/>- dynamic_used_memory: 已使用的动态内存。<br/>- dynamic_peak_memory: 内存的动态峰值。<br/>- dynamic_used_shrctx: 最大动态共享内存上下文。<br/>- dynamic_peak_shrctx: 共享内存上下文的动态峰值。<br/>- max_shared_memory: 最大共享内存。<br/>- shared_used_memory: 已使用的共享内存。<br/>- max_cstore_memory: 列存所允许使用的最大内存。<br/>- cstore_used_memory: 列存已使用的内存大小。<br/>- max_sctpcomm_memory: 通信库所允许使用的最大内存。<br/>- sctpcomm_used_memory: 通信库已使用的内存大小。<br/>- sctpcomm_peak_memory: 通信库的内存峰值。<br/>- other_used_memory: 其他已使用的内存大小。 |
+| memorymbytes | integer | 内存类型分配内存的大小。                                     |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_CGROUP_INFO.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_CGROUP_INFO.md
new file mode 100644
index 0000000000000000000000000000000000000000..603e9823f1a6bf6e606c693fa752d928c8c39e81
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_CGROUP_INFO.md
@@ -0,0 +1,24 @@
+---
+title: GS_WLM_CGROUP_INFO
+summary: GS_WLM_CGROUP_INFO
+author: Guo Huan
+date: 2021-06-07
+---
+
+# GS_WLM_CGROUP_INFO
+
+GS_WLM_CGROUP_INFO视图显示当前执行作业的控制组的信息。
+
+**表 1** GS_WLM_CGROUP_INFO字段
+
+| 名称         | 类型     | 描述                      |
+| :----------- | :------- | :------------------------ |
+| cgoup_name   | text     | 控制组的名称。            |
+| priority     | interger | 作业的优先级。            |
+| usage_pecent | interger | 控制组占用的百分比。      |
+| shares       | bigint   | 控制组分配的CPU资源配额。 |
+| cpuacct      | bigint   | CPU配额分配。             |
+| cpuset       | text     | CPU限额分配。             |
+| relpath      | text     | 控制组的相对路径。        |
+| valid        | text     | 该控制组是否有效。        |
+| node_group   | text     | 逻辑集群名称。            |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_PLAN_OPERATOR_HISTORY.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_PLAN_OPERATOR_HISTORY.md
new file mode 100644
index 0000000000000000000000000000000000000000..b18d41cb8586ad5dc2e1e33b523a8e6ee5e0d105
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_PLAN_OPERATOR_HISTORY.md
@@ -0,0 +1,35 @@
+---
+title: GS_WLM_PLAN_OPERATOR_HISTORY
+summary: GS_WLM_PLAN_OPERATOR_HISTORY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_WLM_PLAN_OPERATOR_HISTORY
+
+GS_WLM_PLAN_OPERATOR_HISTORY视图显示的是当前用户数据库主节点上执行作业结束后的执行计划算子级的相关记录。
+
+| 名称                | 类型                     | 描述                                                         |
+| :------------------ | :----------------------- | :----------------------------------------------------------- |
+| queryid             | bigint                   | 语句执行使用的内部query_id。                                 |
+| pid                 | bigint                   | 后端线程id。                                                 |
+| plan_node_id        | integer                  | 查询对应的执行计划的plan node id。                           |
+| plan_node_name      | text                     | 对应于plan_node_id的算子的名称。                             |
+| start_time          | timestamp with time zone | 该算子处理第一条数据的开始时间。                             |
+| duration            | bigint                   | 该算子到结束时候总的执行时间(ms)。                           |
+| query_dop           | integer                  | 当前算子执行时的并行度。                                     |
+| estimated_rows      | bigint                   | 优化器估算的行数信息。                                       |
+| tuple_processed     | bigint                   | 当前算子返回的元素个数。                                     |
+| min_peak_memory     | integer                  | 当前算子在数据库节点上的最小内存峰值(MB)。                   |
+| max_peak_memory     | integer                  | 当前算子在数据库节点上的最大内存峰值(MB)。                   |
+| average_peak_memory | integer                  | 当前算子在数据库节点平均内存峰值(MB)。                       |
+| memory_skew_percent | integer                  | 当前算子在数据库节点间的内存使用倾斜率。                     |
+| min_spill_size      | integer                  | 若发生下盘，数据库节点盘的最小数据量(MB)，默认为0。          |
+| max_spill_size      | integer                  | 若发生下盘，数据库节点上下盘的最大数据量(MB)，默认为0。      |
+| average_spill_size  | integer                  | 若发生下盘，数据库节点盘的平均数据量(MB)，默认为0。          |
+| spill_skew_percent  | integer                  | 若发生下盘，数据库节点间下盘倾斜率。                         |
+| min_cpu_time        | bigint                   | 该算子在数据库节点最小执行时间(ms)。                         |
+| max_cpu_time        | bigint                   | 该算子在数据库节点上的最大执行时间(ms)。                     |
+| total_cpu_time      | bigint                   | 该算子在数据库节点上的总执行时间(ms)。                       |
+| cpu_skew_percent    | integer                  | 数据库节点间执行时间的倾斜率。                               |
+| warning             | text                     | 主要显示如下几类告警信息: <br />- Sort/SetOp/HashAgg/HashJoin spill <br />- Spill file size large than 256MB <br />- Broadcast size large than 100MB <br />- Early spill <br />- Spill times is greater than 3 <br />- Spill on memory adaptive <br />- Hash table conflict |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_REBUILD_USER_RESOURCE_POOL.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_REBUILD_USER_RESOURCE_POOL.md
new file mode 100644
index 0000000000000000000000000000000000000000..b93c5442aae18b0f82df3e24e94950fb99fe71e3
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_REBUILD_USER_RESOURCE_POOL.md
@@ -0,0 +1,16 @@
+---
+title: GS_WLM_REBUILD_USER_RESOURCE_POOL
+summary: GS_WLM_REBUILD_USER_RESOURCE_POOL
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_WLM_REBUILD_USER_RESOURCE_POOL
+
+该视图用于在当前连接节点上重建内存中用户的资源池信息，无输出。只是用于资源池信息缺失或者错乱时用作补救措施。查询该视图需要sysadmin权限。
+
+**表 1** GS_WLM_REBUILD_USER_RESOURCE_POOL的字段
+
+| 名称                              | 类型    | 描述                                             |
+| :-------------------------------- | :------ | :----------------------------------------------- |
+| gs_wlm_rebuild_user_resource_pool | boolean | 重建内存中用户资源池信息结果。t为成功，f为失败。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_RESOURCE_POOL.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_RESOURCE_POOL.md
new file mode 100644
index 0000000000000000000000000000000000000000..fd6429d855f5c47769446e69f088b5a297c893eb
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_RESOURCE_POOL.md
@@ -0,0 +1,25 @@
+---
+title: GS_WLM_RESOURCE_POOL
+summary: GS_WLM_RESOURCE_POOL
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_WLM_RESOURCE_POOL
+
+这是资源池上的一些统计信息。
+
+**表 1** GS_WLM_RESOURCE_POOL的字段
+
+| 名称          | 类型    | 描述                         |
+| :------------ | :------ | :--------------------------- |
+| rpoid         | oid     | 资源池的OID。                |
+| respool       | name    | 资源池的名称。               |
+| control_group | name    | 该字段不支持。               |
+| parentid      | oid     | 父资源池的OID。              |
+| ref_count     | integer | 关联到该资源池上的作业数量。 |
+| active_points | integer | 资源池上已经使用的点数。     |
+| running_count | integer | 正在资源池上运行的作业数量。 |
+| waiting_count | integer | 正在资源池上排队的作业数量。 |
+| io_limits     | integer | 资源池的iops上限。           |
+| io_priority   | integer | 资源池的io优先级。           |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_USER_INFO.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_USER_INFO.md
new file mode 100644
index 0000000000000000000000000000000000000000..0e0f361354975a97f1e7780f10f846485ddcbb98
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_USER_INFO.md
@@ -0,0 +1,25 @@
+---
+title: GS_WLM_USER_INFO
+summary: GS_WLM_USER_INFO
+author: Guo Huan
+date: 2021-04-19
+---
+
+# GS_WLM_USER_INFO
+
+用户统计信息视图。
+
+**表 1** GS_WLM_USER_INFO字段
+
+| 名称       | 类型     | 描述                 |
+| :--------- | :------- | :------------------- |
+| userid     | oid      | 用户OID。            |
+| username   | name     | 用户名。             |
+| sysadmin   | boolean  | 是否是管理员用户。   |
+| rpoid      | oid      | 关联的资源池的OID。  |
+| respool    | name     | 关联的资源池的名称。 |
+| parentid   | oid      | 用户组的OID。        |
+| totalspace | bigint   | 用户的可用空间上限。 |
+| spacelimit | bigint   | 用户表空间限制。     |
+| childcount | interger | 子用户的个数。       |
+| childlist  | text     | 子用户列表。         |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/MPP_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/MPP_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..b731ae3b46aa23162772139e45aba964696d29ee
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/MPP_TABLES.md
@@ -0,0 +1,21 @@
+---
+title: MPP_TABLES
+summary: MPP_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# MPP_TABLES
+
+MPP_TABLES视图显示信息如下。
+
+**表 1** MPP_TABLES字段
+
+| 名称       | 类型             | 描述                  |
+| :--------- | :--------------- | :-------------------- |
+| schemaname | name             | 包含表的模式名。      |
+| tablename  | name             | 表名。                |
+| tableowner | name             | 表的所有者。          |
+| tablespace | name             | 表所在的表空间。      |
+| pgroup     | name             | 节点群的名称。        |
+| nodeoids   | oidvector_extend | 表分布的节点OID列表。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_AVAILABLE_EXTENSIONS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_AVAILABLE_EXTENSIONS.md
new file mode 100644
index 0000000000000000000000000000000000000000..3cd5e584d7c25174da415e37d055f65d25998c48
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_AVAILABLE_EXTENSIONS.md
@@ -0,0 +1,19 @@
+---
+title: PG_AVAILABLE_EXTENSIONS
+summary: PG_AVAILABLE_EXTENSIONS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_AVAILABLE_EXTENSIONS
+
+PG_AVAILABLE_EXTENSIONS视图显示数据库中某些特性的扩展信息。
+
+**表 1** PG_AVAILABLE_EXTENSIONS字段
+
+| 名称              | 类型 | 描述                                             |
+| :---------------- | :--- | :----------------------------------------------- |
+| name              | name | 扩展名。                                         |
+| default_version   | text | 缺省版本的名称，如果没有指定则为NULL。           |
+| installed_version | text | 扩展当前安装版本，如果没有安装任何版本则为NULL。 |
+| comment           | text | 扩展的控制文件中的评论字符串。                   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_AVAILABLE_EXTENSION_VERSIONS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_AVAILABLE_EXTENSION_VERSIONS.md
new file mode 100644
index 0000000000000000000000000000000000000000..8b657385b9c026de98309e9411b30b7568225925
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_AVAILABLE_EXTENSION_VERSIONS.md
@@ -0,0 +1,23 @@
+---
+title: PG_AVAILABLE_EXTENSION_VERSIONS
+summary: PG_AVAILABLE_EXTENSION_VERSIONS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_AVAILABLE_EXTENSION_VERSIONS
+
+PG_AVAILABLE_EXTENSION_VERSIONS视图显示数据库中某些特性的扩展版本信息。
+
+**表 1** PG_AVAILABLE_EXTENSION_VERSIONS字段
+
+| 名称        | 类型    | 描述                                                       |
+| :---------- | :------ | :--------------------------------------------------------- |
+| name        | name    | 扩展名。                                                   |
+| version     | text    | 版本名。                                                   |
+| installed   | Boolean | 如果这个扩展的版本是当前已经安装了的则为真。               |
+| superuser   | Boolean | 如果只允许系统管理员安装这个扩展则为真。                   |
+| relocatable | Boolean | 如果扩展可以重新加载到另一个模式则为真。                   |
+| schema      | name    | 扩展必须安装到的模式名，如果部分或全部可重新定位则为NULL。 |
+| requires    | name[]  | 先决条件扩展的名称，如果没有则为NULL。                     |
+| comment     | text    | 扩展的控制文件中的评论字符串。                             |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_DELAY.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_DELAY.md
new file mode 100644
index 0000000000000000000000000000000000000000..a8dd50f1dc81322791caa94ebb918419e054b48d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_DELAY.md
@@ -0,0 +1,22 @@
+---
+title: PG_COMM_DELAY
+summary: PG_COMM_DELAY
+author: Guo Huan
+date: 2021-06-07
+---
+
+# PG_COMM_DELAY
+
+PG_COMM_DELAY视图展示单个节点的通信库时延状态。
+
+**表 1** PG_COMM_DELAY字段
+
+| 名称        | 类型    | 描述                                                         |
+| :---------- | :------ | :----------------------------------------------------------- |
+| node_name   | text    | 节点名称。                                                   |
+| remote_name | text    | 连接对端节点名称。                                           |
+| remote_host | text    | 连接对端IP地址。                                             |
+| stream_num  | integer | 当前物理连接使用的stream逻辑连接数量。                       |
+| min_delay   | integer | 当前物理连接一分钟内探测到的最小时延，单位微秒。说明：负数结果无效，请重新等待时延状态更新后再执行。 |
+| average     | integer | 当前物理连接一分钟内探测时延的平均值，单位微秒。             |
+| max_delay   | integer | 当前物理连接一分钟内探测到的最大时延，单位微秒。             |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_RECV_STREAM.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_RECV_STREAM.md
new file mode 100644
index 0000000000000000000000000000000000000000..b4415f55b36892e5c07253585feabc83d4e2c41e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_RECV_STREAM.md
@@ -0,0 +1,32 @@
+---
+title: PG_COMM_RECV_STREAM
+summary: PG_COMM_RECV_STREAM
+author: Guo Huan
+date: 2021-06-07
+---
+
+# PG_COMM_RECV_STREAM
+
+PG_COMM_RECV_STREAM视图展示节点上所有的通信库接收流状态。
+
+**表 1** PG_COMM_RECV_STREAM字段
+
+| 名称        | 类型    | 描述                                                         |
+| :---------- | :------ | :----------------------------------------------------------- |
+| node_name   | text    | 节点名称。                                                   |
+| local_tid   | bigint  | 使用此通信流的线程ID。                                       |
+| remote_name | text    | 连接对端节点名称。                                           |
+| remote_tid  | bigint  | 连接对端线程ID。                                             |
+| idx         | integer | 通信对端DN在本DN内的标识编号。                               |
+| sid         | integer | 通信流在物理连接中的标识编号。                               |
+| tcp_sock    | integer | 通信流所使用的tcp通信socket。                                |
+| state       | text    | 通信流当前的状态。<br />- UNKNOWN：表示当前逻辑连接状态未知。<br />- READY：表示逻辑连接已就绪。 <br />- RUN：表示逻辑连接发送报文正常。<br />- HOLD：表示逻辑连接发送报文等待中。<br />- CLOSED：表示关闭逻辑连接。<br />- TO_CLOSED：表示将会关闭逻辑连接。 |
+| query_id    | bigint  | 通信流对应的debug_query_id编号。                             |
+| pn_id       | integer | 通信流所执行查询的plan_node_id编号。                         |
+| send_smp    | integer | 通信流所执行查询send端的smpid编号。                          |
+| recv_smp    | integer | 通信流所执行查询recv端的smpid编号。                          |
+| recv_bytes  | bigint  | 通信流接收的数据总量，单位Byte。                             |
+| time        | bigint  | 通信流当前生命周期使用时长，单位ms。                         |
+| speed       | bigint  | 通信流的平均接收速率，单位Byte/s。                           |
+| quota       | bigint  | 通信流当前的通信配额值，单位Byte。                           |
+| buff_usize  | bigint  | 通信流当前缓存的数据大小，单位Byte。                         |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_SEND_STREAM.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_SEND_STREAM.md
new file mode 100644
index 0000000000000000000000000000000000000000..ca1d712990ec96eae613a32018996803f050782b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_SEND_STREAM.md
@@ -0,0 +1,32 @@
+---
+title: PG_COMM_SEND_STREAM
+summary: PG_COMM_SEND_STREAM
+author: Guo Huan
+date: 2021-06-07
+---
+
+# PG_COMM_SEND_STREAM
+
+PG_COMM_SEND_STREAM视图展示节点上所有的通信库发送流状态。
+
+**表 1** PG_COMM_SEND_STREAM字段
+
+| 名称        | 类型    | 描述                                                         |
+| :---------- | :------ | :----------------------------------------------------------- |
+| node_name   | text    | 节点名称。                                                   |
+| local_tid   | bigint  | 使用此通信流的线程ID。                                       |
+| remote_name | text    | 连接对端节点名称。                                           |
+| remote_tid  | bigint  | 连接对端线程ID。                                             |
+| idx         | integer | 通信对端DN在本DN内的标识编号。                               |
+| sid         | integer | 通信流在物理连接中的标识编号。                               |
+| tcp_sock    | integer | 通信流所使用的tcp通信socket。                                |
+| state       | text    | 通信流当前的状态。<br />- UNKNOWN：表示当前逻辑连接状态未知。<br />- READY：表示逻辑连接已就绪。<br />- RUN：表示逻辑连接发送报文正常。<br />- HOLD：表示逻辑连接发送报文等待中。<br />- CLOSED：表示关闭逻辑连接。<br />- TO_CLOSED：表示将会关闭逻辑连接。 |
+| query_id    | bigint  | 通信流对应的debug_query_id编号。                             |
+| pn_id       | integer | 通信流所执行查询的plan_node_id编号。                         |
+| send_smp    | integer | 通信流所执行查询send端的smpid编号。                          |
+| recv_smp    | integer | 通信流所执行查询recv端的smpid编号。                          |
+| send_bytes  | bigint  | 通信流发送的数据总量，单位Byte。                             |
+| time        | bigint  | 通信流当前生命周期使用时长，单位ms。                         |
+| speed       | bigint  | 通信流的平均发送速率，单位Byte/s。                           |
+| quota       | bigint  | 通信流当前的通信配额值，单位Byte。                           |
+| wait_quota  | bigint  | 通信流等待quota值产生的额外时间开销，单位ms。                |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_STATUS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_STATUS.md
new file mode 100644
index 0000000000000000000000000000000000000000..d4961a5da0ba4edbf57f6dc6c7a7aa3514b1b852
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_STATUS.md
@@ -0,0 +1,28 @@
+---
+title: PG_COMM_STATUS
+summary: PG_COMM_STATUS
+author: Guo Huan
+date: 2021-06-07
+---
+
+# PG_COMM_STATUS
+
+PG_COMM_STATUS视图展示节点的通信库状态。
+
+**表 1** PG_COMM_STATUS字段
+
+| 名称          | 类型    | 描述                                        |
+| :------------ | :------ | :------------------------------------------ |
+| node_name     | text    | 节点名称。                                  |
+| rxpck_rate    | integer | 节点通信库接收速率，单位Byte/s。            |
+| txpck_rate    | integer | 节点通信库发送速率，单位Byte/s。            |
+| rxkB_rate     | bigint  | bigint节点通信库接收速率，单位KByte/s。     |
+| txkB_rate     | bigint  | bigint节点通信库发送速率，单位KByte/s。     |
+| buffer        | bigint  | cmailbox的buffer大小。                      |
+| memKB_libcomm | bigint  | libcomm进程通信内存大小，单位Byte。         |
+| memKB_libpq   | bigint  | libpq进程通信内存大小，单位Byte。           |
+| used_PM       | integer | postmaster线程实时使用率。                  |
+| used_sflow    | integer | gs_sender_flow_controller线程实时使用率。   |
+| used_rflow    | integer | gs_receiver_flow_controller线程实时使用率。 |
+| used_rloop    | integer | 多个gs_receivers_loop线程中高的实时使用率。 |
+| stream        | integer | 当前使用的逻辑连接总数。                    |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_CONTROL_GROUP_CONFIG.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_CONTROL_GROUP_CONFIG.md
new file mode 100644
index 0000000000000000000000000000000000000000..bb9fa285f5d9403a10ecb887d47d2569d28c9a36
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_CONTROL_GROUP_CONFIG.md
@@ -0,0 +1,16 @@
+---
+title: PG_CONTROL_GROUP_CONFIG
+summary: PG_CONTROL_GROUP_CONFIG
+author: Guo Huan
+date: 2021-06-07
+---
+
+# PG_CONTROL_GROUP_CONFIG
+
+PG_CONTROL_GROUP_CONFIG视图存储系统的控制组配置信息。查询该视图需要sysadmin权限。
+
+**表 1** PG_CONTROL_GROUP_CONFIG字段
+
+| 名称                    | 类型 | 描述               |
+| :---------------------- | :--- | :----------------- |
+| pg_control_group_config | text | 控制组的配置信息。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_CURSORS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_CURSORS.md
new file mode 100644
index 0000000000000000000000000000000000000000..03e4810962e2ce81941f2e6a48a1fd5d5e7eb090
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_CURSORS.md
@@ -0,0 +1,21 @@
+---
+title: PG_CURSORS
+summary: PG_CURSORS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_CURSORS
+
+PG_CURSORS视图列出了当前可用的游标。
+
+**表 1** PG_CURSORS字段
+
+| 名称          | 类型                   | 描述                   |
+| :------------ | :-------------------- | :--------------------- |
+| name          | text                     | 游标名。                                                     |
+| statement     | text                     | 声明改游标时的查询语句。                                     |
+| is_holdable   | Boolean                  | 如果该游标是持久的（就是在声明该游标的事务结束后仍然可以访问该游标）则为TRUE，否则为FALSE。 |
+| is_binary     | Boolean                  | 如果该游标被声明为BINARY则为TRUE，否则为FALSE。              |
+| is_scrollable | Boolean                  | 如果该游标可以滚动（就是允许以不连续的方式检索）则为TRUE，否则为FALSE。 |
+| creation_time | timestamp with time zone | 声明该游标的时间戳。                                         |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_EXT_STATS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_EXT_STATS.md
new file mode 100644
index 0000000000000000000000000000000000000000..2590de1411f804dc7481902519015de4a830cdd9
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_EXT_STATS.md
@@ -0,0 +1,28 @@
+---
+title: PG_EXT_STATS
+summary: PG_EXT_STATS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_EXT_STATS
+
+PG_EXT_STATS视图提供对存储在PG_STATISTIC_EXT表里面的扩展统计信息的访问。扩展统计信息目前包括多列统计信息。
+
+**表 1** PG_EXT_STATS字段
+
+| 名称                   | 类型       | 引用                    | 描述                      |
+| :--------------------- | :--------- | :---------------------- | :----------------------- |
+| schemaname             | name       | PG_NAMESPACE.nspname    | 包含表的模式名。                                             |
+| tablename              | name       | PG_CLASS.relname        | 表名。                                                       |
+| attname                | int2vector | PG_STATISTIC_EXT.stakey | 统计信息扩展的多列信息。                                     |
+| inherited              | Boolean    | -                       | 如果为真，则包含继承的子列，否则只是指定表的字段。           |
+| null_frac              | real       | -                       | 记录中字段组合为空的百分比。                                 |
+| avg_width              | integer    | -                       | 字段组合记录以字节记的平均宽度。                             |
+| n_distinct             | real       | -                       | - 如果大于零，表示字段组合中独立数值的估计数目。<br/>- 如果小于零，表示独立数值的数目被行数除的负数。<br/>    1. 用负数形式是因为ANALYZE认为独立数值的数目是随着表增长而增长；<br/>    2. 正数的形式用于在字段看上去好像有固定的可能值数目的情况下。比如，-1表示一个字段组合中独立数值的个数和行数相同。<br/>- 如果等于零，表示独立数值的数目未知。 |
+| n_dndistinct           | real       | -                       | 标识dn1上字段组合中非NULL数据的唯一值的数目。<br/>- 如果大于零，表示独立数值的实际数目。<br/>- 如果小于零，表示独立数值的数目被行数除的负数。（比如，一个字段组合的数值平均出现概率为两次，则可以表示为n_dndistinct=-0.5）。<br/>- 如果等于零，表示独立数值的数目未知。 |
+| most_common_vals       | anyarray   | -                       | 一个字段组合里最常用数值的列表。如果该字段组合不存在最常用数值，则为NULL。本列保存的多列常用数值均不为NULL。 |
+| most_common_freqs      | real[]     | -                       | 一个最常用数值组合的频率的列表，也就是说，每个出现的次数除以行数。如果most_common_vals是NULL，则为NULL。 |
+| most_common_vals_null  | anyarray   | -                       | 一个字段组合里最常用数值的列表。如果该字段组合不存在最常用数值，则为NULL。本列保存的多列常用数值中至少有一个值为NULL。 |
+| most_common_freqs_null | real[]     | -                       | 一个最常用数值组合的频率的列表，也就是说，每个出现的次数除以行数。如果most_common_vals_null是NULL，则为NULL。 |
+| histogram_bounds       | anyarray   | -                       | 直方图的边界值列表。                                         |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GET_INVALID_BACKENDS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GET_INVALID_BACKENDS.md
new file mode 100644
index 0000000000000000000000000000000000000000..82912a4f599ffce1413f293adf13fb45c5b972bd
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GET_INVALID_BACKENDS.md
@@ -0,0 +1,20 @@
+---
+title: PG_GET_INVALID_BACKENDS
+summary: PG_GET_INVALID_BACKENDS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_GET_INVALID_BACKENDS
+
+PG_GET_INVALID_BACKENDS视图提供显示数据库主节点上连接到当前备机的后台线程信息。
+
+**表 1** PG_GET_INVALID_BACKENDS字段
+
+| 名称          | 类型                     | 描述                         |
+| :------------ | :----------------------- | :--------------------------- |
+| pid           | bigint                   | 线程ID。                     |
+| node_name     | text                     | 后台线程中连接的节点信息。   |
+| dbname        | name                     | 当前连接的数据库。           |
+| backend_start | timestamp with time zone | 后台线程启动的时间。         |
+| query         | text                     | 后台线程正在执行的查询语句。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GET_SENDERS_CATCHUP_TIME.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GET_SENDERS_CATCHUP_TIME.md
new file mode 100644
index 0000000000000000000000000000000000000000..4ab89ac2bdc3f8a8721e91d42c16543753d3b2f4
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GET_SENDERS_CATCHUP_TIME.md
@@ -0,0 +1,23 @@
+---
+title: PG_GET_SENDERS_CATCHUP_TIME
+summary: PG_GET_SENDERS_CATCHUP_TIME
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_GET_SENDERS_CATCHUP_TIME
+
+PG_GET_SENDERS_CATCHUP_TIME视图显示数据库节点上当前活跃的主备发送线程的追赶信息。
+
+**表 1** PG_GET_SENDERS_CATCHUP_TIME字段
+
+| 名称          | 类型                     | 描述                   |
+| :------------ | :----------------------- | :--------------------- |
+| pid           | bigint                   | 当前sender的线程ID。   |
+| lwpid         | integer                  | 当前sender的lwpid。    |
+| local_role    | text                     | 本地的角色。           |
+| peer_role     | text                     | 对端的角色。           |
+| state         | text                     | 当前sender的复制状态。 |
+| type          | text                     | 当前sender的类型。     |
+| catchup_start | timestamp with time zone | catchup启动的时间。    |
+| catchup_end   | timestamp with time zone | catchup结束的时间。    |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GROUP.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GROUP.md
new file mode 100644
index 0000000000000000000000000000000000000000..ccecf12fb3f3c82796d3ca705fc70bd0091b5bb0
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GROUP.md
@@ -0,0 +1,18 @@
+---
+title: PG_GROUP
+summary: PG_GROUP
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_GROUP
+
+PG_GROUP视图查看数据库认证角色及角色之间的成员关系。
+
+**表 1** PG_GROUP字段
+
+| 名称     | 类型  | 描述                                   |
+| :------- | :---- | :------------------------------------- |
+| groname  | name  | 组的名称。                             |
+| grosysid | oid   | 组的ID。                               |
+| grolist  | oid[] | 一个数组，包含这个组里面所有角色的ID。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GTT_ATTACHED_PIDS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GTT_ATTACHED_PIDS.md
new file mode 100644
index 0000000000000000000000000000000000000000..5148502363e4ea2f489bd9c93e4fccf6bca5192a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GTT_ATTACHED_PIDS.md
@@ -0,0 +1,19 @@
+---
+title: PG_GTT_ATTACHED_PIDS
+summary: PG_GTT_ATTACHED_PIDS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_GTT_ATTACHED_PIDS
+
+PG_GTT_ATTACHED_PIDS视图查看哪些会话正在使用全局临时表，调用pg_get_attached_pid函数。
+
+**表 1** PG_GTT_ATTACHED_PIDS字段
+
+| 名称       | 类型     | 描述              |
+| :--------- | :------- | :---------------- |
+| schemaname | name     | schema名称。      |
+| tablename  | name     | 全局临时表名称。  |
+| relid      | oid      | 全局临时表的oid。 |
+| pids       | bigint[] | 线程pid列表。     |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GTT_RELSTATS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GTT_RELSTATS.md
new file mode 100644
index 0000000000000000000000000000000000000000..b1c4a8b1fbaa499710e648747661b2d2ef933227
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GTT_RELSTATS.md
@@ -0,0 +1,23 @@
+---
+title: PG_GTT_RELSTATS
+summary: PG_GTT_RELSTATS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_GTT_RELSTATS
+
+PG_GTT_RELSTATS视图查看当前会话所有全局临时表基本信息，调用pg_get_gtt_relstats函数。
+
+**表 1** PG_GTT_RELSTATS字段
+
+| 名称          | 类型    | 描述                                                         |
+| :------------ | :------ | :----------------------------------------------------------- |
+| schemaname    | name    | schema名称。                                                 |
+| tablename     | name    | 全局临时表名称。                                             |
+| relfilenode   | oid     | 文件对象的ID。                                               |
+| relpages      | integer | 全局临时表的磁盘页面数。                                     |
+| reltuples     | real    | 全局临时表的记录数。                                         |
+| relallvisible | integer | 被标识为全可见的页面数。                                     |
+| relfrozenxid  | xid     | 该表中所有在这个之前的事务ID已经被一个固定的（"frozen"）事务ID替换。 |
+| relminmxid    | xid     | 预留接口，暂未启用。                                         |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GTT_STATS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GTT_STATS.md
new file mode 100644
index 0000000000000000000000000000000000000000..ad5ac7e7bab00fbda33a49708bf9a7ece2757fa5
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_GTT_STATS.md
@@ -0,0 +1,29 @@
+---
+title: PG_GTT_STATS
+summary: PG_GTT_STATS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_GTT_STATS
+
+PG_GTT_STATS视图查看当前会话所有全局临时表单列统计信息，调用pg_get_gtt_statistics函数。
+
+**表 1** PG_GTT_STATS字段
+
+| 名称                   | 类型    | 描述                                               |
+| :--------------------- | :------ | :------------------------------------------------- |
+| schemaname             | name    | schema名称。                                       |
+| tablename              | name    | 全局临时表名称。                                   |
+| attname                | name    | 属性名称。                                         |
+| inherited              | boolean | 是否统计有继承关系的对象。                         |
+| null_frac              | real    | 该字段中为NULL的记录的比率。                       |
+| avg_width              | integer | 非NULL记录的平均存储宽度，以字节计算。             |
+| n_distinct             | real    | 标识全局统计信息中字段里唯一的非NULL数据值的数目。 |
+| most_common_vals       | text[]  | 高频值列表，按照出现的频率排序。                   |
+| most_common_freqs      | real[]  | 高频值的频率。                                     |
+| histogram_bounds       | text[]  | 等频直方图描述列中的数据分布（不包含高频值）。     |
+| correlation            | real    | 相关系数。                                         |
+| most_common_elems      | text[]  | 类型高频值列表，用于数组类型或一些其他类型。       |
+| most_common_elem_freqs | real[]  | 类型高频值的频率。                                 |
+| elem_count_histogram   | real[]  | 数组类型直方图。                                   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_INDEXES.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..a80aa2661c360048c7dfe053c7aca6b9b39b3eed
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_INDEXES.md
@@ -0,0 +1,20 @@
+---
+title: PG_INDEXES
+summary: PG_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_INDEXES
+
+PG_INDEXES视图提供对数据库中每个索引的有用信息的访问。
+
+**表 1** PG_INDEXES字段
+
+| 名称       | 类型 | 引用                  | 描述                                     |
+| :--------- | :--- | :-------------------- | :--------------------------------------- |
+| schemaname | name | PG_NAMESPACE.nspname  | 包含表和索引的模式名称。                 |
+| tablename  | name | PG_CLASS.relname      | 此索引所服务的表的名称。                 |
+| indexname  | name | PG_CLASS.relname      | 索引的名称。                             |
+| tablespace | name | PG_TABLESPACE.nspname | 包含索引的表空间名称。                   |
+| indexdef   | text | -                     | 索引定义（一个重建的CREATE INDEX命令）。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_LOCKS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_LOCKS.md
new file mode 100644
index 0000000000000000000000000000000000000000..5616fe212984c4abcf39aeab4dd4f59e49ef48be
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_LOCKS.md
@@ -0,0 +1,34 @@
+---
+title: PG_LOCKS
+summary: PG_LOCKS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_LOCKS
+
+PG_LOCKS视图存储各打开事务所持有的锁信息。
+
+**表 1** PG_LOCKS字段
+
+| 名称               | 类型     | 引用            | 描述                       |
+| :----------------- | :------- | :-------------- | :------------------------- |
+| locktype           | text     | -               | 被锁定对象的类型: relation，extend，page，tuple，transactionid，virtualxid，object，userlock，advisory。 |
+| database           | oid      | PG_DATABASE.oid | 被锁定对象所在数据库的OID。<br/>- 如果被锁定的对象是共享对象，则OID为0。<br/>- 如果是一个事务ID，则为NULL。 |
+| relation           | oid      | PG_CLASS.oid    | 关系的OID，如果锁定的对象不是关系，也不是关系的一部分，则为NULL。 |
+| page               | integer  | -               | 关系内部的页面编号，如果对象不是关系页或者不是行页，则为NULL。 |
+| tuple              | smallint | -               | 页面里边的行编号，如果对象不是行，则为NULL。                 |
+| bucket             | integer  | -               | 子表对应的bucket number。如果目标不是表的话，则为NULL。      |
+| virtualxid         | text     | -               | 事务的虚拟ID，如果对象不是一个虚拟事务ID，则为NULL。         |
+| transactionid      | xid      | -               | 事务的ID，如果对象不是一个事务ID，则为NULL。                 |
+| classid            | oid      | PG_CLASS.oid    | 包含该对象的系统表的OID，如果对象不是普通的数据库对象，则为NULL。 |
+| objid              | oid      | -               | 对象在其系统表内的OID，如果对象不是普通数据库对象，则为NULL。 |
+| objsubid           | smallint | -               | 对于表的一个字段，这是字段编号；对于其他对象类型，这个字段是0；如果这个对象不是普通数据库对象，则为NULL。 |
+| virtualtransaction | text     | -               | 持有此锁或者在等待此锁的事务的虚拟ID。                       |
+| pid                | bigint   | -               | 持有或者等待这个锁的服务器线程的逻辑ID。如果锁是被一个预备事务持有的，则为NULL。 |
+| sessionid          | bigint   | -               | 持有或者等待这个锁的会话ID。                                 |
+| mode               | text     | -               | 这个线程持有的或者是期望的锁模式。                           |
+| granted            | Boolean  | -               | - 如果锁是持有锁，则为TRUE。<br/>- 如果锁是等待锁，则为FALSE。 |
+| fastpath           | Boolean  | -               | 如果通过fast-path获得锁，则为TRUE；如果通过主要的锁表获得，则为FALSE。 |
+| locktag            | text     | -               | 会话等待锁信息，可通过locktag_decode()函数解析。             |
+| global_sessionid   | text     |                 | 全局会话ID。                                                 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_NODE_ENV.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_NODE_ENV.md
new file mode 100644
index 0000000000000000000000000000000000000000..ac589787956e96c54873310b2e544606130a75c9
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_NODE_ENV.md
@@ -0,0 +1,22 @@
+---
+title: PG_NODE_ENV
+summary: PG_NODE_ENV
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_NODE_ENV
+
+PG_NODE_ENV视图提供获取当前节点的环境变量信息。
+
+**表 1** PG_NODE_ENV字段
+
+| 名称          | 类型    | 描述                 |
+| :------------ | :------ | :------------------- |
+| node_name     | text    | 当前节点的名称。     |
+| host          | text    | 当前节点的主机名称。 |
+| process       | integer | 当前节点的进程号。   |
+| port          | integer | 当前节点的端口号。   |
+| installpath   | text    | 当前节点的安装目录。 |
+| datapath      | text    | 当前节点的数据目录。 |
+| log_directory | text    | 当前节点的日志目录。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_OS_THREADS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_OS_THREADS.md
new file mode 100644
index 0000000000000000000000000000000000000000..fe47bc336cc435d0a0d3eeca8ec0f3c8e423087a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_OS_THREADS.md
@@ -0,0 +1,20 @@
+---
+title: PG_OS_THREADS
+summary: PG_OS_THREADS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_OS_THREADS
+
+PG_OS_THREADS视图提供当前节点下所有线程的状态信息。
+
+**表 1** PG_OS_THREADS字段
+
+| 名称          | 类型                     | 描述                             |
+| :------------ | :----------------------- | :------------------------------- |
+| node_name     | text                     | 当前节点的名称。                 |
+| pid           | bigint                   | 当前节点进程中正在运行的线程号。 |
+| lwpid         | integer                  | 与pid对应的轻量级线程号。        |
+| thread_name   | text                     | 与pid对应的线程名称。            |
+| creation_time | timestamp with time zone | 与pid对应的线程创建的时间。      |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_PREPARED_STATEMENTS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_PREPARED_STATEMENTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..6f72a137f65efc647383789e7ea630e1c63eceb6
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_PREPARED_STATEMENTS.md
@@ -0,0 +1,20 @@
+---
+title: PG_PREPARED_STATEMENTS
+summary: PG_PREPARED_STATEMENTS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_PREPARED_STATEMENTS
+
+PG_PREPARED_STATEMENTS视图显示当前会话所有可用的预备语句。
+
+**表 1** PG_PREPARED_STATEMENTS字段
+
+| 名称            | 类型                     | 描述                                                         |
+| :-------------- | :----------------------- | :----------------------------------------------------------- |
+| name            | text                     | 预备语句的标识符。                                           |
+| statement       | text                     | 创建该预备语句的查询字符串。对于从SQL创建的预备语句而言是客户端提交的PREPARE语句；对于通过前/后端协议创建的预备语句而言是预备语句自身的文本。 |
+| prepare_time    | timestamp with time zone | 创建该预备语句的时间戳。                                     |
+| parameter_types | regtype[]                | 该预备语句期望的参数类型，以regtype类型的数组格式出现。与该数组元素相对应的OID可以通过把regtype转换为oid值得到。 |
+| from_sql        | Boolean                  | - 如果该预备语句是通过PREPARE语句创建的则为true。<br/>- 如果是通过前/后端协议创建的则为false。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_PREPARED_XACTS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_PREPARED_XACTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..67da2e6cb53da2b0c34d249250bdf35935dfebba
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_PREPARED_XACTS.md
@@ -0,0 +1,20 @@
+---
+title: PG_PREPARED_XACTS
+summary: PG_PREPARED_XACTS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_PREPARED_XACTS
+
+PG_PREPARED_XACTS视图显示当前准备好进行两阶段提交的事务的信息。
+
+**表 1** PG_PREPARED_XACTS字段
+
+| 名称        | 类型                     | 引用                | 描述                       |
+| :---------- | :----------------------- | :------------------ | :------------------------- |
+| transaction | xid                      | -                   | 预备事务的数字事务标识。   |
+| gid         | text                     | -                   | 赋予该事务的全局事务标识。 |
+| prepared    | timestamp with time zone | -                   | 事务准备好提交的时间。     |
+| owner       | name                     | PG_AUTHID.rolname   | 执行该事务的用户的名称。   |
+| database    | name                     | PG_DATABASE.datname | 执行该事务所在的数据库名。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_REPLICATION_SLOTS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_REPLICATION_SLOTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..5259be090afc97b9a4d701c0610ba5747357a331
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_REPLICATION_SLOTS.md
@@ -0,0 +1,25 @@
+---
+title: PG_REPLICATION_SLOTS
+summary: PG_REPLICATION_SLOTS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_REPLICATION_SLOTS
+
+PG_REPLICATION_SLOTS视图查看复制节点的信息。
+
+**表 1** PG_REPLICATION_SLOTS字段
+
+| 名称          | 类型    | 描述                               |
+| :------------ | :------ | :--------------------------------- |
+| slot_name     | text    | 复制节点的名称。                   |
+| plugin        | text    | 逻辑复制槽对应的输出插件名。       |
+| slot_type     | text    | 复制节点的类型。                   |
+| datoid        | oid     | 复制节点的数据库OID。              |
+| database      | name    | 复制节点的数据库名称。             |
+| active        | Boolean | 复制节点是否为激活状态。           |
+| xmin          | xid     | 复制节点事务标识。                 |
+| catalog_xmin  | xid     | 逻辑复制槽对应的最早解码事务标识。 |
+| restart_lsn   | text    | 复制节点的Xlog文件信息。           |
+| dummy_standby | Boolean | 复制节点是否为假备。               |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_RLSPOLICIES.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_RLSPOLICIES.md
new file mode 100644
index 0000000000000000000000000000000000000000..3bd72db71b9352b31e5c99d9d09b8072b3a3b8bc
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_RLSPOLICIES.md
@@ -0,0 +1,22 @@
+---
+title: PG_RLSPOLICIES
+summary: PG_RLSPOLICIES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_RLSPOLICIES
+
+PG_RLSPOLICIES视图提供查询行级访问控制策略。
+
+**表 1** PG_RLSPOLICIES字段
+
+| 名称             | 类型   | 描述                                                       |
+| :--------------- | :----- | :--------------------------------------------------------- |
+| schemaname       | name   | 行级访问控制策略作用的表对象所属模式名称。                 |
+| tablename        | name   | 行级访问控制策略作用的表对象名称。                         |
+| policyname       | name   | 行级访问控制策略名称。                                     |
+| policypermissive | text   | 行级访问控制策略属性。                                     |
+| policyroles      | name[] | 行级访问控制策略影响的用户列表，不指定表示影响所有的用户。 |
+| policycmd        | text   | 行级访问控制策略影响的SQL操作。                            |
+| policyqual       | text   | 行级访问控制策略的表达式。                                 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_ROLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_ROLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..d7f30efd81688e1d727a81b5736296415263f584
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_ROLES.md
@@ -0,0 +1,42 @@
+---
+title: PG_ROLES
+summary: PG_ROLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_ROLES
+
+PG_ROLES视图提供访问数据库角色的相关信息，初始化用户和具有sysadmin属性或createrole属性的用户可以查看全部角色的信息，其他用户只能查看自己的信息。
+
+**表 1** PG_ROLES字段
+
+| 名称             | 类型                     | 引用                  | 描述               |
+| :--------------- | :----------------------- | :-------------------- | :-------------------- |
+| rolname          | name                     | -                     | 角色名称。                                                   |
+| rolsuper         | Boolean                  | -                     | 该角色是否是拥有最高权限的初始系统管理员。                   |
+| rolinherit       | Boolean                  | -                     | 该角色是否继承角色的权限。                                   |
+| rolcreaterole    | Boolean                  | -                     | 该角色是否可以创建其他的角色。                               |
+| rolcreatedb      | Boolean                  | -                     | 该角色是否可以创建数据库。                                   |
+| rolcatupdate     | Boolean                  | -                     | 该角色是否可以直接更新系统表。只有usesysid=10的初始系统管理员拥有此权限。其他用户无法获得此权限。 |
+| rolcanlogin      | Boolean                  | -                     | 该角色是否可以登录数据库。                                   |
+| rolreplication   | Boolean                  | -                     | 该角色是否可以复制。                                         |
+| rolauditadmin    | Boolean                  | -                     | 该角色是否为审计管理员。                                     |
+| rolsystemadmin   | Boolean                  | -                     | 该角色是否为系统管理员。                                     |
+| rolconnlimit     | integer                  | -                     | 对于可以登录的角色，这里限制了该角色允许发起的最大并发连接数。 -1表示无限制。 |
+| rolpassword      | text                     | -                     | 不是口令，总是`******`。                             |
+| rolvalidbegin    | timestamp with time zone | -                     | 帐户的有效开始时间；如果没有设置有效开始时间，则为NULL。     |
+| rolvaliduntil    | timestamp with time zone | -                     | 帐户的有效结束时间；如果没有设置有效结束时间，则为NULL。     |
+| rolrespool       | name                     | -                     | 用户所能够使用的resource pool。                              |
+| rolparentid      | oid                      | PG_AUTHID.rolparentid | 用户所在组用户的OID。                                        |
+| roltabspace      | text                     | -                     | 用户永久表存储空间限额。                                     |
+| roltempspace     | text                     | -                     | 用户临时表存储空间限额。                                     |
+| rolspillspace    | text                     | -                     | 用户算子落盘空间限额。                                       |
+| rolconfig        | text[]                   | -                     | 运行时配置变量的会话缺省。                                   |
+| oid              | oid                      | PG_AUTHID.oid         | 角色的ID。                                                   |
+| roluseft         | Boolean                  | PG_AUTHID.roluseft    | 角色是否可以操作外表。                                       |
+| rolkind          | "char"                   | -                     | 角色类型。                                                   |
+| nodegroup        | name                     | -                     | 该字段不支持。                                               |
+| rolmonitoradmin  | Boolean                  | -                     | 该角色是否为监控管理员。                                     |
+| roloperatoradmin | Boolean                  | -                     | 该角色是否为运维管理员。                                     |
+| rolpolicyadmin   | Boolean                  | -                     | 该角色是否为安全策略管理员。                                 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_RULES.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_RULES.md
new file mode 100644
index 0000000000000000000000000000000000000000..a191a5320e640920a11f1f392b380cb152973851
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_RULES.md
@@ -0,0 +1,19 @@
+---
+title: PG_RULES
+summary: PG_RULES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_RULES
+
+PG_RULES视图提供对查询重写规则的有用信息访问的接口。
+
+**表 1** PG_RULES字段
+
+| 名称       | 类型 | 描述                                 |
+| :--------- | :--- | :----------------------------------- |
+| schemaname | name | 包含表的模式的名称。                 |
+| tablename  | name | 规则作用的表的名称。                 |
+| rulename   | name | 规则的名称。                         |
+| definition | text | 规则定义（一个重新构造的创建命令）。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_SECLABELS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_SECLABELS.md
new file mode 100644
index 0000000000000000000000000000000000000000..f5997821c469c7fb949e82670ec65edd5356eca5
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_SECLABELS.md
@@ -0,0 +1,23 @@
+---
+title: PG_SECLABELS
+summary: PG_SECLABELS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_SECLABELS
+
+PG_SECLABELS视图提供关于安全标签的信息。
+
+**表 1** PG_SECLABELS字段
+
+| 名称         | 类型    | 引用                 | 描述                                                         |
+| :----------- | :------ | :------------------- | :---------------------- |
+| objoid       | oid     | 任意OID属性          | 这个安全标签指向的对象的OID。                                |
+| classoid     | oid     | PG_CLASS.oid         | 这个对象出现的系统表的OID。                                  |
+| objsubid     | integer | -                    | 对于一个在表字段上的安全标签，是字段编号（引用表本身的objoid和classoid）。对于所有其他对象类型，这个字段为零。 |
+| objtype      | text    | -                    | 这个标签出现的对象的类型，文本格式。                         |
+| objnamespace | oid     | PG_NAMESPACE.oid     | 这个对象的名称空间的OID，如果适用；否则为NULL。              |
+| objname      | text    | -                    | 这个标签适用的对象的名称，文本格式。                         |
+| provider     | text    | PG_SECLABEL.provider | 与这个标签相关的标签提供者。                                 |
+| label        | text    | PG_SECLABEL.label    | 适用于这个对象的安全标签。                                   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_SETTINGS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_SETTINGS.md
new file mode 100644
index 0000000000000000000000000000000000000000..c6912a535f478f2865670b4d148e9bf82d0911d2
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_SETTINGS.md
@@ -0,0 +1,31 @@
+---
+title: PG_SETTINGS
+summary: PG_SETTINGS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_SETTINGS
+
+PG_SETTINGS视图显示数据库运行时参数的相关信息。
+
+**表 1** PG_SETTINGS字段
+
+| 名称       | 类型    | 描述                                                         |
+| :--------- | :------ | :----------------------------------------------------------- |
+| name       | text    | 参数名称。                                                   |
+| setting    | text    | 参数当前值。                                                 |
+| unit       | text    | 参数的隐式结构。                                             |
+| category   | text    | 参数的逻辑组。                                               |
+| short_desc | text    | 参数的简单描述。                                             |
+| extra_desc | text    | 参数的详细描述。                                             |
+| context    | text    | 设置参数值的上下文，包括internal，postmaster，sighup，backend，superuser，user。 |
+| vartype    | text    | 参数类型，包括bool，enum，integer，real，string。            |
+| source     | text    | 参数的赋值方式。                                             |
+| min_val    | text    | 参数最小值。如果参数类型不是数值型，那么该字段值为null。     |
+| max_val    | text    | 参数最大值。如果参数类型不是数值型，那么该字段值为null。     |
+| enumvals   | text[]  | enum类型参数合法值。如果参数类型不是enum型，那么该字段值为null。 |
+| boot_val   | text    | 数据库启动时参数默认值。                                     |
+| reset_val  | text    | 数据库重置时参数默认值。                                     |
+| sourcefile | text    | 设置参数值的配置文件。如果参数不是通过配置文件赋值，那么该字段值为null。 |
+| sourceline | integer | 设置参数值的配置文件的行号。如果参数不是通过配置文件赋值，那么该字段值为null。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_SHADOW.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_SHADOW.md
new file mode 100644
index 0000000000000000000000000000000000000000..5992173551c0506ae22adaca9b7a2546c1639ef5
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_SHADOW.md
@@ -0,0 +1,31 @@
+---
+title: PG_SHADOW
+summary: PG_SHADOW
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_SHADOW
+
+PG_SHADOW视图显示了所有在PG_AUTHID中标记了rolcanlogin的角色的属性。
+
+这个视图的名称来自于该视图是不可读的，因为它包含口令。PG_USER是一个在PG_SHADOW上公开可读的视图，只是把口令域填成了空白。
+
+**表 1** PG_SHADOW字段
+
+| 名称            | 类型            | 引用              | 描述             |
+| :-------------- | :-------------- | :---------------- | :-------------- |
+| usename         | name                     | PG_AUTHID.rolname | 用户名。   |
+| usesysid        | oid                      | PG_AUTHID.oid     | 用户的ID。              |
+| usecreatedb     | Boolean                  | -                 | 用户可以创建数据库。    |
+| usesuper        | Boolean                  | -                 | 用户是系统管理员。      |
+| usecatupd       | Boolean                  | -                 | 用户可以更新视图。即使是系统管理员，如果这个字段不是真，也不能更新视图。 |
+| userepl         | Boolean                  | -                 | 用户可以初始化流复制和使系统处于或不处于备份模式。           |
+| passwd          | text                     | -                 | 口令（可能是加密的）；如果没有则为null。参阅PG_AUTHID获取加密的口令是如何存储的信息。 |
+| valbegin        | timestamp with time zone | -                 | 帐户的有效开始时间；如果没有设置有效开始时间，则为NULL。     |
+| valuntil        | timestamp with time zone | -                 | 帐户的有效结束时间；如果没有设置有效结束时间，则为NULL。     |
+| respool         | name                     | -                 | 用户使用的资源池。      |
+| parent          | oid                      | -                 | 父资源池。              |
+| spacelimit      | text                     | -                 | 永久表存储空间限额。    |
+| tempspacelimit  | text                     | -                 | 临时表存储空间限额。    |
+| spillspacelimit | text                     | -                 | 算子落盘空间限额。      |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_ALL_INDEXES.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_ALL_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..6971a66eb7407d416b116934aba871febaa8121a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_ALL_INDEXES.md
@@ -0,0 +1,22 @@
+---
+title: PG_STATIO_ALL_INDEXES
+summary: PG_STATIO_ALL_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STATIO_ALL_INDEXES
+
+PG_STATIO_ALL_INDEXES视图将包含当前数据库中的每个索引行， 显示特定索引的I/O的统计。
+
+**表 1** PG_STATIO_ALL_INDEXES字段
+
+| 名称          | 类型   | 描述                     |
+| :------------ | :----- | :----------------------- |
+| relid         | oid    | 索引的表的OID。          |
+| indexrelid    | oid    | 该索引的OID。            |
+| schemaname    | name   | 该索引的模式名。         |
+| relname       | name   | 该索引的表名。           |
+| indexrelname  | name   | 索引名称。               |
+| idx_blks_read | bigint | 从索引中读取的磁盘块数。 |
+| idx_blks_hit  | bigint | 索引命中缓存数。         |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_ALL_SEQUENCES.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_ALL_SEQUENCES.md
new file mode 100644
index 0000000000000000000000000000000000000000..3c01e8f48bcab189aa5e00da1451cfc6470d925a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_ALL_SEQUENCES.md
@@ -0,0 +1,20 @@
+---
+title: PG_STATIO_ALL_SEQUENCES
+summary: PG_STATIO_ALL_SEQUENCES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STATIO_ALL_SEQUENCES
+
+PG_STATIO_ALL_SEQUENCES视图包含当前数据库中每个序列的I/O的统计信息。
+
+**表 1** PG_STATIO_ALL_SEQUENCES字段
+
+| 名称       | 类型   | 描述                     |
+| :--------- | :----- | :----------------------- |
+| relid      | oid    | 序列OID。                |
+| schemaname | name   | 序列中模式名。           |
+| relname    | name   | 序列名。                 |
+| blks_read  | bigint | 从序列中读取的磁盘块数。 |
+| blks_hit   | bigint | 序列中缓存命中数。       |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_ALL_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_ALL_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..670bd5de6f938052844a1a93a18caa5ac726b326
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_ALL_TABLES.md
@@ -0,0 +1,26 @@
+---
+title: PG_STATIO_ALL_TABLES
+summary: PG_STATIO_ALL_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STATIO_ALL_TABLES
+
+PG_STATIO_ALL_TABLES视图将包含当前数据库中每个表（包括TOAST表）的I/O统计信息。
+
+**表 1** PG_STATIO_ALL_TABLES字段
+
+| 名称            | 类型   | 描述                                          |
+| :-------------- | :----- | :-------------------------------------------- |
+| relid           | oid    | 表OID。                                       |
+| schemaname      | name   | 该表模式名。                                  |
+| relname         | name   | 表名。                                        |
+| heap_blks_read  | bigint | 从该表中读取的磁盘块数。                      |
+| heap_blks_hit   | bigint | 该表缓存命中数。                              |
+| idx_blks_read   | bigint | 从表中所有索引读取的磁盘块数。                |
+| idx_blks_hit    | bigint | 表中所有索引命中缓存数。                      |
+| toast_blks_read | bigint | 该表的TOAST表读取的磁盘块数（如果存在）。     |
+| toast_blks_hit  | bigint | 该表的TOAST表命中缓冲区数（如果存在）。       |
+| tidx_blks_read  | bigint | 该表的TOAST表索引读取的磁盘块数（如果存在）。 |
+| tidx_blks_hit   | bigint | 该表的TOAST表索引命中缓冲区数（如果存在）。   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_SYS_INDEXES.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_SYS_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..26a26656f96705ba633db6c6da6ff66deadc35c4
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_SYS_INDEXES.md
@@ -0,0 +1,22 @@
+---
+title: PG_STATIO_SYS_INDEXES
+summary: PG_STATIO_SYS_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STATIO_SYS_INDEXES
+
+PG_STATIO_SYS_INDEXES视图显示命名空间中所有系统表索引的IO状态信息。
+
+**表 1** PG_STATIO_SYS_INDEXES字段
+
+| 名称          | 类型   | 描述                     |
+| :------------ | :----- | :----------------------- |
+| relid         | oid    | 索引的表的OID。          |
+| indexrelid    | oid    | 该索引的OID。            |
+| schemaname    | name   | 该索引的模式名。         |
+| relname       | name   | 该索引的表名。           |
+| indexrelname  | name   | 索引名称。               |
+| idx_blks_read | bigint | 从索引中读取的磁盘块数。 |
+| idx_blks_hit  | bigint | 索引命中缓存数。         |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_SYS_SEQUENCES.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_SYS_SEQUENCES.md
new file mode 100644
index 0000000000000000000000000000000000000000..8ad58f8279469d43483b082eac2afe8abb680337
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_SYS_SEQUENCES.md
@@ -0,0 +1,20 @@
+---
+title: PG_STATIO_SYS_SEQUENCES
+summary: PG_STATIO_SYS_SEQUENCES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STATIO_SYS_SEQUENCES
+
+PG_STATIO_SYS_SEQUENCES视图显示命名空间中所有序列的IO状态信息。
+
+**表 1** PG_STATIO_SYS_SEQUENCES字段
+
+| 名称       | 类型   | 描述                     |
+| :--------- | :----- | :----------------------- |
+| relid      | oid    | 序列OID。                |
+| schemaname | name   | 序列中模式名。           |
+| relname    | name   | 序列名。                 |
+| blks_read  | bigint | 从序列中读取的磁盘块数。 |
+| blks_hit   | bigint | 序列中缓存命中数。       |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_SYS_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_SYS_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..0458c03fd776886a2f4ae4b9c7f186b8eab3e43a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_SYS_TABLES.md
@@ -0,0 +1,26 @@
+---
+title: PG_STATIO_SYS_TABLES
+summary: PG_STATIO_SYS_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STATIO_SYS_TABLES
+
+PG_STATIO_SYS_TABLES视图显示命名空间中所有系统表的IO状态信息。
+
+**表 1** PG_STATIO_SYS_TABLES字段
+
+| 名称            | 类型   | 描述                                          |
+| :-------------- | :----- | :-------------------------------------------- |
+| relid           | oid    | 表OID。                                       |
+| schemaname      | name   | 该表模式名。                                  |
+| relname         | name   | 表名。                                        |
+| heap_blks_read  | bigint | 从该表中读取的磁盘块数。                      |
+| heap_blks_hit   | bigint | 该表缓存命中数。                              |
+| idx_blks_read   | bigint | 从表中所有索引读取的磁盘块数。                |
+| idx_blks_hit    | bigint | 表中所有索引命中缓存数。                      |
+| toast_blks_read | bigint | 该表的TOAST表读取的磁盘块数（如果存在）。     |
+| toast_blks_hit  | bigint | 该表的TOAST表命中缓冲区数（如果存在）。       |
+| tidx_blks_read  | bigint | 该表的TOAST表索引读取的磁盘块数（如果存在）。 |
+| tidx_blks_hit   | bigint | 该表的TOAST表索引命中缓冲区数（如果存在）。   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_USER_INDEXES.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_USER_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..64bf5152b7c504209a853a1820203e74b15a302d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_USER_INDEXES.md
@@ -0,0 +1,22 @@
+---
+title: PG_STATIO_USER_INDEXES
+summary: PG_STATIO_USER_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STATIO_USER_INDEXES
+
+PG_STATIO_USER_INDEXES视图显示命名空间中所有用户关系表索引的IO状态信息。
+
+**表 1** PG_STATIO_USER_INDEXES字段
+
+| 名称          | 类型   | 描述                     |
+| :------------ | :----- | :----------------------- |
+| relid         | oid    | 索引的表的OID。          |
+| indexrelid    | oid    | 该索引的OID。            |
+| schemaname    | name   | 该索引的模式名。         |
+| relname       | name   | 该索引的表名。           |
+| indexrelname  | name   | 索引名称。               |
+| idx_blks_read | bigint | 从索引中读取的磁盘块数。 |
+| idx_blks_hit  | bigint | 索引命中缓存数。         |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_USER_SEQUENCES.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_USER_SEQUENCES.md
new file mode 100644
index 0000000000000000000000000000000000000000..d26fa19129c9cb7f2ecd30ace6644e7d6a307d89
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_USER_SEQUENCES.md
@@ -0,0 +1,20 @@
+---
+title: PG_STATIO_USER_SEQUENCES
+summary: PG_STATIO_USER_SEQUENCES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STATIO_USER_SEQUENCES
+
+PG_STATIO_USER_SEQUENCES视图显示命名空间中所有用户关系表类型为序列的IO状态信息。
+
+**表 1** PG_STATIO_USER_SEQUENCES字段
+
+| 名称       | 类型   | 描述                     |
+| :--------- | :----- | :----------------------- |
+| relid      | oid    | 序列OID。                |
+| schemaname | name   | 序列中模式名。           |
+| relname    | name   | 序列名。                 |
+| blks_read  | bigint | 从序列中读取的磁盘块数。 |
+| blks_hit   | bigint | 序列中缓存命中数。       |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_USER_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_USER_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..a79f0bd30e21a5d9ad4e0b9c6cc674a118605a5b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_USER_TABLES.md
@@ -0,0 +1,26 @@
+---
+title: PG_STATIO_USER_TABLES
+summary: PG_STATIO_USER_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STATIO_USER_TABLES
+
+PG_STATIO_USER_TABLES视图显示命名空间中所有用户关系表的IO状态信息。
+
+**表 1** PG_STATIO_USER_TABLES字段
+
+| 名称            | 类型   | 描述                                          |
+| :-------------- | :----- | :-------------------------------------------- |
+| relid           | oid    | 表OID。                                       |
+| schemaname      | name   | 该表模式名。                                  |
+| relname         | name   | 表名。                                        |
+| heap_blks_read  | bigint | 从该表中读取的磁盘块数。                      |
+| heap_blks_hit   | bigint | 该表缓存命中数。                              |
+| idx_blks_read   | bigint | 从表中所有索引读取的磁盘块数。                |
+| idx_blks_hit    | bigint | 表中所有索引命中缓存数。                      |
+| toast_blks_read | bigint | 该表的TOAST表读取的磁盘块数（如果存在）。     |
+| toast_blks_hit  | bigint | 该表的TOAST表命中缓冲区数（如果存在）。       |
+| tidx_blks_read  | bigint | 该表的TOAST表索引读取的磁盘块数（如果存在）。 |
+| tidx_blks_hit   | bigint | 该表的TOAST表索引命中缓冲区数（如果存在）。   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATS.md
new file mode 100644
index 0000000000000000000000000000000000000000..fd0d733ba1d2868595f4c0ce912b045603d2ab6d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STATS.md
@@ -0,0 +1,30 @@
+---
+title: PG_STATS
+summary: PG_STATS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STATS
+
+PG_STATS视图提供对存储在pg_statistic表里面的单列统计信息的访问。该视图记录的统计信息更新时间间隔由参数autovacuum_naptime设置。
+
+**表 1** PG_STATS字段
+
+| 名称                   | 类型     | 引用                 | 描述                       |
+| :--------------------- | :------- | :------------------- | :----------------------- |
+| schemaname             | name     | PG_NAMESPACE.nspname | 包含表的模式名。                                             |
+| tablename              | name     | PG_CLASS.relname     | 表名。                                                       |
+| attname                | name     | PG_ATTRIBUTE.attname | 字段的名称。                                                 |
+| inherited              | Boolean  | -                    | 如果为真，则包含继承的子列，否则只是指定表的字段。           |
+| null_frac              | real     | -                    | 记录中字段为空的百分比。                                     |
+| avg_width              | integer  | -                    | 字段记录以字节记的平均宽度。                                 |
+| n_distinct             | real     | -                    | - 如果大于零，表示字段中独立数值的估计数目。<br/>- 如果小于零，表示独立数值的数目被行数除的负数。<br/>    1. 用负数形式是因为ANALYZE认为独立数值的数目是随着表增长而增长；<br/>    2. 正数的形式用于在字段看上去好像有固定的可能值数目的情况下。比如，-1表示一个唯一字段，独立数值的个数和行数相同。 |
+| n_dndistinct           | real     | -                    | 标识dn1上字段中非NULL数据的唯一值的数目。<br/>- 如果大于零，表示独立数值的实际数目。<br/>- 如果小于零，表示独立数值的数目被行数除的负数。（比如，一个字段的数值平均出现概率为两次，则可以表示为n_dndistinct=-0.5）。<br/>- 如果等于零，表示独立数值的数目未知。 |
+| most_common_vals       | anyarray | -                    | 一个字段里最常用数值的列表。如果里面的字段数值是最常见的，则为NULL。 |
+| most_common_freqs      | real[]   | -                    | 一个最常用数值的频率的列表，也就是说，每个出现的次数除以行数。如果most_common_vals是NULL，则为NULL。 |
+| histogram_bounds       | anyarray | -                    | 一个数值的列表，它把字段的数值分成几组大致相同热门的组。如果在most_common_vals里有数值，则在这个饼图的计算中省略。如果字段数据类型没有&lt;操作符或者most_common_vals列表代表了整个分布性，则这个字段为NULL。 |
+| correlation            | real     | -                    | 统计与字段值的物理行序和逻辑行序有关。它的范围从-1到+1。在数值接近-1或者+1的时候，在字段上的索引扫描将被认为比它接近零的时候开销更少，因为减少了对磁盘的随机访问。如果字段数据类型没有&lt;操作符，则这个字段为NULL。 |
+| most_common_elems      | anyarray | -                    | 一个最常用的非空元素的列表。                                 |
+| most_common_elem_freqs | real[]   | -                    | 一个最常用元素的频率的列表。                                 |
+| elem_count_histogram   | real[]   | -                    | 对于独立的非空元素的统计直方图。                             |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_ACTIVITY.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_ACTIVITY.md
new file mode 100644
index 0000000000000000000000000000000000000000..503ee5f8a55033b5765047a88ad21ddd5b2ce851
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_ACTIVITY.md
@@ -0,0 +1,36 @@
+---
+title: PG_STAT_ACTIVITY
+summary: PG_STAT_ACTIVITY
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STAT_ACTIVITY
+
+PG_STAT_ACTIVITY视图显示和当前用户查询相关的信息，字段保存的是上一次执行的信息。
+
+**表 1** PG_STAT_ACTIVITY字段
+
+| 名称             | 类型                     | 描述                                                         |
+| :--------------- | :----------------------- | :----------------------------------------------------------- |
+| datid            | oid                      | 用户会话在后台连接到的数据库OID。                            |
+| datname          | name                     | 用户会话在后台连接到的数据库名称。                           |
+| pid              | bigint                   | 后台线程ID。                                                 |
+| sessionid        | bigint                   | 会话ID。                                                     |
+| usesysid         | oid                      | 登录该后台的用户OID。                                        |
+| usename          | name                     | 登录该后台的用户名。                                         |
+| application_name | text                     | 连接到该后台的应用名。                                       |
+| client_addr      | inet                     | 连接到该后台的客户端的IP地址。 如果此字段是null，它表明通过服务器机器上UNIX套接字连接客户端或者这是内部进程，如autovacuum。 |
+| client_hostname  | text                     | 客户端的主机名，这个字段是通过client_addr的反向DNS查找得到。这个字段只有在启动log_hostname且使用IP连接时才非空。 |
+| client_port      | integer                  | 客户端用于与后台通讯的TCP端口号，如果使用Unix套接字，则为-1。 |
+| backend_start    | timestamp with time zone | 该过程开始的时间，即当客户端连接服务器时。                   |
+| xact_start       | timestamp with time zone | 启动当前事务的时间，如果没有事务是活跃的，则为null。如果当前查询是首个事务，则这列等同于query_start列。 |
+| query_start      | timestamp with time zone | 开始当前活跃查询的时间， 如果state的值不是active，则这个值是上一个查询的开始时间。 |
+| state_change     | timestamp with time zone | 上次状态改变的时间。                                         |
+| waiting          | Boolean                  | 如果后台当前正等待锁则为true。                               |
+| enqueue          | text                     | 该字段不支持。                                               |
+| state            | text                     | 该后台当前总体状态。可能值是: <br/>- active: 后台正在执行一个查询。<br/>- idle: 后台正在等待一个新的客户端命令。<br/>- idle in transaction: 后台在事务中，但事务中没有语句在执行。<br/>- idle in transaction (aborted): 后台在事务中，但事务中有语句执行失败。<br/>- fastpath function call: 后台正在执行一个fast-path函数。<br/>- disabled: 如果后台禁用track_activities，则报告这个状态。<br/>说明:<br/>普通用户只能查看到自己帐户所对应的会话状态。即其他帐户的state信息为空。例如以judy用户连接数据库后，在pg_stat_activity中查看到的普通用户joe及初始用户omm的state信息为空: <br/>`SELECT datname, usename, usesysid, state,pid FROM pg_stat_activity;`<br/><br/>datname  \| usename \| usesysid \| state  \|       pid<br/>----------+---------+----------+-------+----------------<br/>postgres \| omm     \|       10 \|        \| 139968752121616<br/>postgres \| omm     \|       10 \|        \| 139968903116560<br/>db_tpcc \| judy    \|    16398 \| active \| 139968391403280<br/>postgres \| omm     \|       10 \|        \| 139968643069712<br/>postgres \| omm     \|       10 \|        \| 139968680818448<br/>postgres \| joe     \|    16390 \|        \| 139968563377936<br/>(6 rows) |
+| resource_pool    | name                     | 用户使用的资源池。                                           |
+| query_id         | bigint                   | 查询语句的ID。                                               |
+| query            | text                     | 该后台的最新查询。如果state状态是active（活跃的），此字段显示当前正在执行的查询。所有其他情况表示上一个查询。 |
+| connection_info  | text                     | json格式字符串，记录当前连接数据库的驱动类型、驱动版本号、当前驱动的部署路径、进程属主用户等信息。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_ALL_INDEXES.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_ALL_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..2dbe54642d6bd1ce3da551155788b1f9136498d8
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_ALL_INDEXES.md
@@ -0,0 +1,25 @@
+---
+title: PG_STAT_ALL_INDEXES
+summary: PG_STAT_ALL_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STAT_ALL_INDEXES
+
+PG_STAT_ALL_INDEXES视图将包含当前数据库中的每个索引行，显示访问特定索引的统计。
+
+索引可以通过简单的索引扫描或“位图”索引扫描进行使用。位图扫描中几个索引的输出可以通过AND或者OR规则进行组合， 因此当使用位图扫描的时候，很难将独立堆行抓取与特定索引进行组合，因此，一个位图扫描增加pg_stat_all_indexes.idx_tup_read使用索引计数，并且增加pg_stat_all_tables.idx_tup_fetch表计数，但不影响pg_stat_all_indexes.idx_tup_fetch。
+
+**表 1** PG_STAT_ALL_INDEXES字段
+
+| 名称          | 类型   | 描述                                       |
+| :------------ | :----- | :----------------------------------------- |
+| relid         | oid    | 这个索引的表的OID。                        |
+| indexrelid    | oid    | 索引的OID。                                |
+| schemaname    | name   | 索引的模式名。                             |
+| relname       | name   | 索引的表名。                               |
+| indexrelname  | name   | 索引名。                                   |
+| idx_scan      | bigint | 索引上开始的索引扫描数。                   |
+| idx_tup_read  | bigint | 通过索引上扫描返回的索引项数。             |
+| idx_tup_fetch | bigint | 通过使用索引的简单索引扫描抓取的活表行数。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_ALL_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_ALL_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..a9e5f72c922fe2e5f7fa1c5756b8df5cee9facd0
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_ALL_TABLES.md
@@ -0,0 +1,37 @@
+---
+title: PG_STAT_ALL_TABLES
+summary: PG_STAT_ALL_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STAT_ALL_TABLES
+
+PG_STAT_ALL_TABLES视图将包含当前数据库中每个表的一行（包括TOAST表），显示访问特定表的统计信息。
+
+**表 1** PG_STAT_ALL_TABLES字段
+
+| 名称              | 类型                     | 描述                                                         |
+| :---------------- | :----------------------- | :----------------------------------------------------------- |
+| relid             | oid                      | 表的OID。                                                    |
+| schemaname        | name                     | 该表的模式名。                                               |
+| relname           | name                     | 表名。                                                       |
+| seq_scan          | bigint                   | 该表发起的顺序扫描数。                                       |
+| seq_tup_read      | bigint                   | 顺序扫描抓取的活跃行数。                                     |
+| idx_scan          | bigint                   | 该表发起的索引扫描数。                                       |
+| idx_tup_fetch     | bigint                   | 索引扫描抓取的活跃行数。                                     |
+| n_tup_ins         | bigint                   | 插入行数。                                                   |
+| n_tup_upd         | bigint                   | 更新行数。                                                   |
+| n_tup_del         | bigint                   | 删除行数。                                                   |
+| n_tup_hot_upd     | bigint                   | HOT更新行数（比如没有更新所需的单独索引）。                  |
+| n_live_tup        | bigint                   | 估计活跃行数。                                               |
+| n_dead_tup        | bigint                   | 估计死行数。                                                 |
+| last_vacuum       | timestamp with time zone | 最后一次清理该表的时间。                                     |
+| last_autovacuum   | timestamp with time zone | 上次被autovacuum守护进程清理该表的时间。                     |
+| last_analyze      | timestamp with time zone | 上次分析该表的时间。                                         |
+| last_autoanalyze  | timestamp with time zone | 上次被autovacuum守护进程分析该表的时间。                     |
+| vacuum_count      | bigint                   | 这个表被清理的次数。                                         |
+| autovacuum_count  | bigint                   | 这个表被autovacuum清理的次数。                               |
+| analyze_count     | bigint                   | 这个表被分析的次数。                                         |
+| autoanalyze_count | bigint                   | 这个表被autovacuum守护进程分析的次数。                       |
+| last_data_changed | timestamp with time zone | 记录这个表上一次数据发生变化的时间（引起数据变化的操作包括INSERT/UPDATE/DELETE、EXCHANGE/TRUNCATE/DROP partition），该列数据仅在本地数据库主节点记录。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_BAD_BLOCK.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_BAD_BLOCK.md
new file mode 100644
index 0000000000000000000000000000000000000000..3363896da3a6215a7ff83ff9a3e0917d34680fba
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_BAD_BLOCK.md
@@ -0,0 +1,24 @@
+---
+title: PG_STAT_BAD_BLOCK
+summary: PG_STAT_BAD_BLOCK
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STAT_BAD_BLOCK
+
+PG_STAT_BAD_BLOCK视图显示自节点启动后，读取数据时出现Page/CU校验失败的统计信息。
+
+**表 1** PG_STAT_BAD_BLOCK字段
+
+| 名称         | 类型                     | 描述                                                         |
+| :----------- | :----------------------- | :----------------------------------------------------------- |
+| nodename     | text                     | 节点名。                                                     |
+| databaseid   | integer                  | 数据库OID。                                                  |
+| tablespaceid | integer                  | 表空间OID。                                                  |
+| relfilenode  | integer                  | 文件对象ID。                                                 |
+| bucketid     | smallint                 | 一致性hash bucket ID。                                       |
+| forknum      | integer                  | 文件类型。取值如下：<br />- 0，数据主文件。<br />- 1，FSM文件。<br />- 2，VM文件。<br />- 3，BCM文件。<br />大于4，列存表每个字段的数据文件。 |
+| error_count  | integer                  | 出现校验失败的次数。                                         |
+| first_time   | timestamp with time zone | 第一次出现时间。                                             |
+| last_time    | timestamp with time zone | 最近一次出现时间。                                           |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_BGWRITER.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_BGWRITER.md
new file mode 100644
index 0000000000000000000000000000000000000000..ed7d1a3ad15e20063a9260f9fd42bfe02b7e9859
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_BGWRITER.md
@@ -0,0 +1,26 @@
+---
+title: PG_STAT_BGWRITER
+summary: PG_STAT_BGWRITER
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STAT_BGWRITER
+
+PG_STAT_BGWRITER视图显示关于后端写进程活动的统计信息。
+
+**表 1** PG_STAT_BGWRITER字段
+
+| 名称                  | 类型                     | 描述                           |
+| :-------------------- | :----------------------- | :----------------------------- |
+| checkpoints_timed     | bigint                   | 执行的定期检查点数。                                         |
+| checkpoints_req       | bigint                   | 执行的需求检查点数。                                         |
+| checkpoint_write_time | double precision         | 花费在检查点处理部分的时间总量，其中文件被写入到磁盘，以毫秒为单位。 |
+| checkpoint_sync_time  | double precision         | 花费在检查点处理部分的时间总量，其中文件被同步到磁盘，以毫秒为单位。 |
+| buffers_checkpoint    | bigint                   | 检查点写缓冲区数量。                                         |
+| buffers_clean         | bigint                   | 后端写进程写缓冲区数量。                                     |
+| maxwritten_clean      | bigint                   | 后端写进程停止清理扫描时间数，因为它写了太多缓冲区。         |
+| buffers_backend       | bigint                   | 通过后端直接写缓冲区数。                                     |
+| buffers_backend_fsync | bigint                   | 后端不得不执行自己的fsync调用的时间数 （通常后端写进程处理这些即使后端确实自己写）。 |
+| buffers_alloc         | bigint                   | 分配的缓冲区数量。                                           |
+| stats_reset           | timestamp with time zone | 这些统计被重置的时间。                                       |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_DATABASE.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_DATABASE.md
new file mode 100644
index 0000000000000000000000000000000000000000..4be4d322079acd99397babdf56c40bbb8e0bca60
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_DATABASE.md
@@ -0,0 +1,34 @@
+---
+title: PG_STAT_DATABASE
+summary: PG_STAT_DATABASE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STAT_DATABASE
+
+PG_STAT_DATABASE视图将包含MogDB中每个数据库的数据库统计信息。
+
+**表 1** PG_STAT_DATABASE字段
+
+| 名称           | 类型                     | 描述                                                         |
+| :------------- | :----------------------- | :----------------------------------------------------------- |
+| datid          | oid                      | 数据库的OID。                                                |
+| datname        | name                     | 这个数据库的名称。                                           |
+| numbackends    | integer                  | 当前连接到该数据库的后端数。 这是在返回一个反映目前状态值的视图中唯一的列；自上次重置所有其他列返回累积值。 |
+| xact_commit    | bigint                   | 此数据库中已经提交的事务数。                                 |
+| xact_rollback  | bigint                   | 此数据库中已经回滚的事务数。                                 |
+| blks_read      | bigint                   | 在这个数据库中读取的磁盘块的数量。                           |
+| blks_hit       | bigint                   | 高速缓存中已经发现的磁盘块的次数， 这样读取是不必要的（这只包括PostgreSQL缓冲区高速缓存，没有操作系统的文件系统缓存）。 |
+| tup_returned   | bigint                   | 通过数据库查询返回的行数。                                   |
+| tup_fetched    | bigint                   | 通过数据库查询抓取的行数。                                   |
+| tup_inserted   | bigint                   | 通过数据库查询插入的行数。                                   |
+| tup_updated    | bigint                   | 通过数据库查询更新的行数。                                   |
+| tup_deleted    | bigint                   | 通过数据库查询删除的行数。                                   |
+| conflicts      | bigint                   | 由于数据库恢复冲突取消的查询数量（只在备用服务器发生的冲突）。请参见PG_STAT_DATABASE_CONFLICTS获取更多信息。 |
+| temp_files     | bigint                   | 通过数据库查询创建的临时文件数量。计算所有临时文件， 不论为什么创建临时文件（比如排序或者哈希）， 而且不管log_temp_files设置。 |
+| temp_bytes     | bigint                   | 通过数据库查询写入临时文件的数据总量。计算所有临时文件，不论为什么创建临时文件，而且不管log_temp_files设置。 |
+| deadlocks      | bigint                   | 在该数据库中检索的死锁数。                                   |
+| blk_read_time  | double precision         | 通过数据库后端读取数据文件块花费的时间，以毫秒计算。         |
+| blk_write_time | double precision         | 通过数据库后端写入数据文件块花费的时间，以毫秒计算。         |
+| stats_reset    | timestamp with time zone | 重置当前状态统计的时间。                                     |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_DATABASE_CONFLICTS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_DATABASE_CONFLICTS.md
new file mode 100644
index 0000000000000000000000000000000000000000..b91a12f1f183c279347e402ab412ad9575110db2
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_DATABASE_CONFLICTS.md
@@ -0,0 +1,22 @@
+---
+title: PG_STAT_DATABASE_CONFLICTS
+summary: PG_STAT_DATABASE_CONFLICTS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STAT_DATABASE_CONFLICTS
+
+PG_STAT_DATABASE_CONFLICTS视图显示数据库冲突状态的统计信息。
+
+**表 1** PG_STAT_DATABASE_CONFLICTS字段
+
+| 名称             | 类型   | 描述                 |
+| :--------------- | :----- | :------------------- |
+| datid            | oid    | 数据库标识。         |
+| datname          | name   | 数据库名称。         |
+| confl_tablespace | bigint | 冲突的表空间的数目。 |
+| confl_lock       | bigint | 冲突的锁数目。       |
+| confl_snapshot   | bigint | 冲突的快照数目。     |
+| confl_bufferpin  | bigint | 冲突的缓冲区数目。   |
+| confl_deadlock   | bigint | 冲突的死锁数目。     |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_REPLICATION.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_REPLICATION.md
new file mode 100644
index 0000000000000000000000000000000000000000..d304b5b4db37d70758ae0a69ddc775a2f98c9272
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_REPLICATION.md
@@ -0,0 +1,30 @@
+---
+title: PG_STAT_REPLICATION
+summary: PG_STAT_REPLICATION
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STAT_REPLICATION
+
+PG_STAT_REPLICATION视图用于描述日志同步状态信息，例如发起端发送日志位置，接收端接收日志位置等。
+
+**表 1** PG_STAT_REPLICATION字段
+
+| 名称                     | 类型                     | 描述                                                      |
+| :----------------------- | :----------------------- | :-------------------------------------------------------- |
+| pid                      | bigint                   | 线程的PID。                                               |
+| usesysid                 | oid                      | 用户系统ID。                                              |
+| usename                  | name                     | 用户名。                                                  |
+| application_name         | text                     | 程序名称。                                                |
+| client_addr              | inet                     | 客户端地址。                                              |
+| client_hostname          | text                     | 客户端名。                                                |
+| client_port              | integer                  | 客户端端口。                                              |
+| backend_start            | timestamp with time zone | 程序启动时间。                                            |
+| state                    | text                     | 日志复制的状态: <br/>- 追赶状态<br/>- 一致的流状态        |
+| sender_sent_location     | text                     | 发送端发送日志位置。                                      |
+| receiver_write_location  | text                     | 接收端write日志位置。                                     |
+| receiver_flush_location  | text                     | 接收端flush日志位置。                                     |
+| receiver_replay_location | text                     | 接收端replay日志位置。                                    |
+| sync_priority            | integer                  | 同步复制的优先级（0表示异步）。                           |
+| sync_state               | text                     | 同步状态: <br/>- 异步复制<br/>- 同步复制<br/>- 潜在同步者 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_SYS_INDEXES.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_SYS_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..31979ede466d8a8ef04911b2edc76581db4f058c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_SYS_INDEXES.md
@@ -0,0 +1,23 @@
+---
+title: PG_STAT_SYS_INDEXES
+summary: PG_STAT_SYS_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STAT_SYS_INDEXES
+
+PG_STAT_SYS_INDEXES视图显示pg_catalog、information_schema模式中所有系统表的索引状态信息。
+
+**表 1** PG_STAT_SYS_INDEXES字段
+
+| 名称          | 类型   | 描述                                       |
+| :------------ | :----- | :----------------------------------------- |
+| relid         | oid    | 这个索引的表的OID。                        |
+| indexrelid    | oid    | 索引的OID。                                |
+| schemaname    | name   | 索引的模式名。                             |
+| relname       | name   | 索引的表名。                               |
+| indexrelname  | name   | 索引名。                                   |
+| idx_scan      | bigint | 索引上开始的索引扫描数。                   |
+| idx_tup_read  | bigint | 通过索引上扫描返回的索引项数。             |
+| idx_tup_fetch | bigint | 通过使用索引的简单索引扫描抓取的活表行数。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_SYS_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_SYS_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..2938100d1500d6b687a573c686a48a019a1b15e0
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_SYS_TABLES.md
@@ -0,0 +1,37 @@
+---
+title: PG_STAT_SYS_TABLES
+summary: PG_STAT_SYS_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STAT_SYS_TABLES
+
+PG_STAT_SYS_TABLES视图显示pg_catalog、information_schema模式的所有命名空间中系统表的统计信息。
+
+**表 1** PG_STAT_SYS_TABLES字段
+
+| 名称              | 类型                     | 描述                                            |
+| :---------------- | :----------------------- | :---------------------------------------------- |
+| relid             | oid                      | 表的OID。                                       |
+| schemaname        | name                     | 该表的模式名。                                  |
+| relname           | name                     | 表名。                                          |
+| seq_scan          | bigint                   | 该表发起的顺序扫描数。                          |
+| seq_tup_read      | bigint                   | 顺序扫描抓取的活跃行数。                        |
+| idx_scan          | bigint                   | 该表发起的索引扫描数。                          |
+| idx_tup_fetch     | bigint                   | 索引扫描抓取的活跃行数。                        |
+| n_tup_ins         | bigint                   | 插入行数。                                      |
+| n_tup_upd         | bigint                   | 更新行数。                                      |
+| n_tup_del         | bigint                   | 删除行数。                                      |
+| n_tup_hot_upd     | bigint                   | HOT更新行数（比如没有更新所需的单独索引）。     |
+| n_live_tup        | bigint                   | 估计活跃行数。                                  |
+| n_dead_tup        | bigint                   | 估计死行数。                                    |
+| last_vacuum       | timestamp with time zone | 最后一次该表是手动清理的（不计算VACUUM FULL）。 |
+| last_autovacuum   | timestamp with time zone | 上次被autovacuum守护进程清理的时间。            |
+| last_analyze      | timestamp with time zone | 上次手动分析这个表的时间。                      |
+| last_autoanalyze  | timestamp with time zone | 上次被autovacuum守护进程分析的时间。            |
+| vacuum_count      | bigint                   | 这个表被手动清理的次数（不计算VACUUM FULL）。   |
+| autovacuum_count  | bigint                   | 这个表被autovacuum清理的次数。                  |
+| analyze_count     | bigint                   | 这个表被手动分析的次数。                        |
+| autoanalyze_count | bigint                   | 这个表被autovacuum守护进程分析的次数。          |
+| last_data_changed | timestamp with time zone | 这个表数据最近修改时间。                        |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_USER_FUNCTIONS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_USER_FUNCTIONS.md
new file mode 100644
index 0000000000000000000000000000000000000000..6d3684234f830558953208258d179f9ba593ccdd
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_USER_FUNCTIONS.md
@@ -0,0 +1,21 @@
+---
+title: PG_STAT_USER_FUNCTIONS
+summary: PG_STAT_USER_FUNCTIONS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STAT_USER_FUNCTIONS
+
+PG_STAT_USER_FUNCTIONS视图显示命名空间中用户自定义函数（函数语言为非内部语言）的状态信息。
+
+**表 1** PG_STAT_USER_FUNCTIONS字段
+
+| 名称       | 类型             | 描述                         |
+| :--------- | :--------------- | :--------------------------- |
+| funcid     | oid              | 函数标识。                   |
+| schemaname | name             | 模式的名称。                 |
+| funcname   | name             | 函数名称。                   |
+| calls      | bigint           | 函数被调用的次数。           |
+| total_time | double precision | 函数的总执行时长。           |
+| self_time  | double precision | 当前线程调用函数的总的时长。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_USER_INDEXES.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_USER_INDEXES.md
new file mode 100644
index 0000000000000000000000000000000000000000..69b13a910413ca0b82fa0409b9bb0787ecb1d4f2
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_USER_INDEXES.md
@@ -0,0 +1,23 @@
+---
+title: PG_STAT_USER_INDEXES
+summary: PG_STAT_USER_INDEXES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STAT_USER_INDEXES
+
+PG_STAT_USER_INDEXES视图显示数据库中用户自定义普通表和toast表的索引状态信息。
+
+**表 1** PG_STAT_USER_INDEXES字段
+
+| 名称          | 类型   | 描述                                       |
+| :------------ | :----- | :----------------------------------------- |
+| relid         | oid    | 这个索引的表的OID。                        |
+| indexrelid    | oid    | 索引的OID。                                |
+| schemaname    | name   | 索引的模式名。                             |
+| relname       | name   | 索引的表名。                               |
+| indexrelname  | name   | 索引名。                                   |
+| idx_scan      | bigint | 索引上开始的索引扫描数。                   |
+| idx_tup_read  | bigint | 通过索引上扫描返回的索引项数。             |
+| idx_tup_fetch | bigint | 通过使用索引的简单索引扫描抓取的活表行数。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_USER_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_USER_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..35c223c110ac4b4e912ec38b4fa3fa9edf73d594
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_USER_TABLES.md
@@ -0,0 +1,37 @@
+---
+title: PG_STAT_USER_TABLES
+summary: PG_STAT_USER_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STAT_USER_TABLES
+
+PG_STAT_USER_TABLES视图显示所有命名空间中用户自定义普通表和toast表的状态信息。
+
+**表 1** PG_STAT_USER_TABLES字段
+
+| 名称              | 类型                     | 描述                                            |
+| :---------------- | :----------------------- | :---------------------------------------------- |
+| relid             | oid                      | 表的OID。                                       |
+| schemaname        | name                     | 该表的模式名。                                  |
+| relname           | name                     | 表名。                                          |
+| seq_scan          | bigint                   | 该表发起的顺序扫描数。                          |
+| seq_tup_read      | bigint                   | 顺序扫描抓取的活跃行数。                        |
+| idx_scan          | bigint                   | 该表发起的索引扫描数。                          |
+| idx_tup_fetch     | bigint                   | 索引扫描抓取的活跃行数。                        |
+| n_tup_ins         | bigint                   | 插入行数。                                      |
+| n_tup_upd         | bigint                   | 更新行数。                                      |
+| n_tup_del         | bigint                   | 删除行数。                                      |
+| n_tup_hot_upd     | bigint                   | HOT更新行数（即没有更新所需的单独索引）。       |
+| n_live_tup        | bigint                   | 估计活跃行数。                                  |
+| n_dead_tup        | bigint                   | 估计死行数。                                    |
+| last_vacuum       | timestamp with time zone | 最后一次该表是手动清理的（不计算VACUUM FULL）。 |
+| last_autovacuum   | timestamp with time zone | 上次被autovacuum守护进程清理的表。              |
+| last_analyze      | timestamp with time zone | 上次手动分析这个表。                            |
+| last_autoanalyze  | timestamp with time zone | 上次被autovacuum守护进程分析的表。              |
+| vacuum_count      | bigint                   | 这个表被手动清理的次数（不计算VACUUM FULL）。   |
+| autovacuum_count  | bigint                   | 这个表被autovacuum清理的次数。                  |
+| analyze_count     | bigint                   | 这个表被手动分析的次数。                        |
+| autoanalyze_count | bigint                   | 这个表被autovacuum守护进程分析的次数。          |
+| last_data_changed | timestamp with time zone | 这个表数据最近修改时间。                        |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_ALL_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_ALL_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..fce8830107d52188b94d0cbc6b1c13f8e83ae632
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_ALL_TABLES.md
@@ -0,0 +1,26 @@
+---
+title: PG_STAT_XACT_ALL_TABLES
+summary: PG_STAT_XACT_ALL_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STAT_XACT_ALL_TABLES
+
+PG_STAT_XACT_ALL_TABLES视图显示命名空间中所有普通表和toast表的事务状态信息。
+
+**表 1** PG_STAT_XACT_ALL_TABLES字段
+
+| 名称          | 类型   | 描述                                        |
+| :------------ | :----- | :------------------------------------------ |
+| relid         | oid    | 表的OID。                                   |
+| schemaname    | name   | 该表的模式名。                              |
+| relname       | name   | 表名。                                      |
+| seq_scan      | bigint | 该表发起的顺序扫描数。                      |
+| seq_tup_read  | bigint | 顺序扫描抓取的活跃行数。                    |
+| idx_scan      | bigint | 该表发起的索引扫描数。                      |
+| idx_tup_fetch | bigint | 索引扫描抓取的活跃行数。                    |
+| n_tup_ins     | bigint | 插入行数。                                  |
+| n_tup_upd     | bigint | 更新行数。                                  |
+| n_tup_del     | bigint | 删除行数。                                  |
+| n_tup_hot_upd | bigint | HOT更新行数（比如没有更新所需的单独索引）。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_SYS_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_SYS_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..dc33ee6440edbfa181c3892db6f45cd72f9b5a7a
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_SYS_TABLES.md
@@ -0,0 +1,26 @@
+---
+title: PG_STAT_XACT_SYS_TABLES
+summary: PG_STAT_XACT_SYS_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STAT_XACT_SYS_TABLES
+
+PG_STAT_XACT_SYS_TABLES视图显示命名空间中系统表的事务状态信息。
+
+**表 1** PG_STAT_XACT_SYS_TABLES字段
+
+| 名称          | 类型   | 描述                                        |
+| :------------ | :----- | :------------------------------------------ |
+| relid         | oid    | 表的OID。                                   |
+| schemaname    | name   | 该表的模式名。                              |
+| relname       | name   | 表名。                                      |
+| seq_scan      | bigint | 该表发起的顺序扫描数。                      |
+| seq_tup_read  | bigint | 顺序扫描抓取的活跃行数。                    |
+| idx_scan      | bigint | 该表发起的索引扫描数。                      |
+| idx_tup_fetch | bigint | 索引扫描抓取的活跃行数。                    |
+| n_tup_ins     | bigint | 插入行数。                                  |
+| n_tup_upd     | bigint | 更新行数。                                  |
+| n_tup_del     | bigint | 删除行数。                                  |
+| n_tup_hot_upd | bigint | HOT更新行数（比如没有更新所需的单独索引）。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_USER_FUNCTIONS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_USER_FUNCTIONS.md
new file mode 100644
index 0000000000000000000000000000000000000000..a093ddb146b61c3bc4c65a3fb9281f58bef72e41
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_USER_FUNCTIONS.md
@@ -0,0 +1,21 @@
+---
+title: PG_STAT_XACT_USER_FUNCTIONS
+summary: PG_STAT_XACT_USER_FUNCTIONS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STAT_XACT_USER_FUNCTIONS
+
+PG_STAT_XACT_USER_FUNCTIONS视图包含每个函数的执行的统计信息。
+
+**表 1** PG_STAT_XACT_USER_FUNCTIONS字段
+
+| 名称       | 类型             | 描述                         |
+| :--------- | :--------------- | :--------------------------- |
+| funcid     | oid              | 函数标识。                   |
+| schemaname | name             | 模式的名称。                 |
+| funcname   | name             | 函数名称。                   |
+| calls      | bigint           | 函数被调用的次数。           |
+| total_time | double precision | 函数的总执行时长。           |
+| self_time  | double precision | 当前线程调用函数的总的时长。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_USER_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_USER_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..a1a97f1826616b2b427c00759bcfb0c5c1d40bc2
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_USER_TABLES.md
@@ -0,0 +1,26 @@
+---
+title: PG_STAT_XACT_USER_TABLES
+summary: PG_STAT_XACT_USER_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_STAT_XACT_USER_TABLES
+
+PG_STAT_XACT_USER_TABLES视图显示命名空间中用户表的事务状态信息。
+
+**表 1** PG_STAT_XACT_USER_TABLES字段
+
+| 名称          | 类型   | 描述                                        |
+| :------------ | :----- | :------------------------------------------ |
+| relid         | oid    | 表的OID。                                   |
+| schemaname    | name   | 该表的模式名。                              |
+| relname       | name   | 表名。                                      |
+| seq_scan      | bigint | 该表发起的顺序扫描数。                      |
+| seq_tup_read  | bigint | 顺序扫描抓取的活跃行数。                    |
+| idx_scan      | bigint | 该表发起的索引扫描数。                      |
+| idx_tup_fetch | bigint | 索引扫描抓取的活跃行数。                    |
+| n_tup_ins     | bigint | 插入行数。                                  |
+| n_tup_upd     | bigint | 更新行数。                                  |
+| n_tup_del     | bigint | 删除行数。                                  |
+| n_tup_hot_upd | bigint | HOT更新行数（比如没有更新所需的单独索引）。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TABLES.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TABLES.md
new file mode 100644
index 0000000000000000000000000000000000000000..a5aa711f1480df465c0a6583ae6f5933b42bf9a1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TABLES.md
@@ -0,0 +1,25 @@
+---
+title: PG_TABLES
+summary: PG_TABLES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_TABLES
+
+PG_TABLES视图提供了对数据库中每个表访问的有用信息。
+
+**表 1** PG_TABLES字段
+
+| 名称          | 类型                     | 引用                  | 描述            |
+| :------------ | :----------------------- | :--------------------| :------------------- |
+| schemaname    | name                     | PG_NAMESPACE.nspname               | 包含表的模式名。                                      |
+| tablename     | name                     | PG_CLASS.relname                   | 表名。                                                |
+| tableowner    | name                     | pg_get_userbyid(PG_CLASS.relowner) | 表的所有者。                                          |
+| tablespace    | name                     | PG_TABLESPACE.spcname              | 包含表的表空间，默认为NULL。                          |
+| hasindexes    | Boolean                  | PG_CLASS.relhasindex               | 如果表上有索引（或者最近拥有）则为TRUE，否则为FALSE。 |
+| hasrules      | Boolean                  | PG_CLASS.relhasruls                | 如果表上有规则，则为TRUE，否则为FALSE。               |
+| hastriggers   | Boolean                  | PG_CLASS.RELHASTRIGGERS            | 如果表上有触发器，则为TRUE，否则为FALSE。             |
+| tablecreator  | name                     | pg_get_userbyid(po.creator)        | 创建表的名称。                                        |
+| created       | timestamp with time zone | pg_object.ctime                    | 对象的创建时间。                                      |
+| last_ddl_time | timestamp with time zone | pg_object.mtime                    | 对象的最后修改时间。                                  |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TDE_INFO.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TDE_INFO.md
new file mode 100644
index 0000000000000000000000000000000000000000..417d524ca2ef04d77271cd8d661a4ae7e7baae20
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TDE_INFO.md
@@ -0,0 +1,18 @@
+---
+title: PG_TDE_INFO
+summary: PG_TDE_INFO
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_TDE_INFO
+
+PG_TDE_INFO视图提供了MogDB加密信息。
+
+**表 1** PG_TDE_INFO字段
+
+| 名称       | 类型    | 描述                                                        |
+| :--------- | :------ | :---------------------------------------------------------- |
+| is_encrypt | Boolean | 是否加密MogDB。<br/>- f: 非加密MogDB。<br/>- t: 加密MogDB。 |
+| g_tde_algo | text    | 加密算法。<br/>- SM4-CTR-128<br/>- AES-CTR-128              |
+| remain     | text    | 保留字段。                                                  |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_THREAD_WAIT_STATUS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_THREAD_WAIT_STATUS.md
new file mode 100644
index 0000000000000000000000000000000000000000..b6a3696a29591c3c18aaf52080f151d40b60e9f0
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_THREAD_WAIT_STATUS.md
@@ -0,0 +1,290 @@
+---
+title: PG_THREAD_WAIT_STATUS
+summary: PG_THREAD_WAIT_STATUS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_THREAD_WAIT_STATUS
+
+通过PG_THREAD_WAIT_STATUS视图可以检测当前实例中工作线程（backend thread）以及辅助线程（auxiliary thread）的阻塞等待情况。
+
+**表 1** PG_THREAD_WAIT_STATUS字段
+
+| 名称        | 类型    | 描述   |
+| :---------- | :------ | :----------------------|
+| node_name   | text    | 当前节点的名称。                  |
+| db_name     | text    | 数据库名称。                      |
+| thread_name | text    | 线程名称。                        |
+| query_id    | bigint  | 查询ID，对应debug_query_id。      |
+| tid         | bigint  | 当前线程的线程号。                |
+| sessionid   | bigint  | 当前会话ID。                      |
+| lwtid       | integer | 当前线程的轻量级线程号。          |
+| psessionid  | bigint  | 父会话ID。                        |
+| tlevel      | integer | streaming线程的层级。             |
+| smpid       | integer | 并行线程的ID。                    |
+| wait_status | text    | 当前线程的等待状态。等待状态的详细信息请参见[表2](#等待状态列表)。 |
+| wait_event  | text    | 如果wait_status是acquire lock、acquire lwlock、wait io三种类型，此列描述具体的锁、轻量级锁、IO的信息。否则是空。 |
+| locktag | text | 当前线程正在等待锁的信息。 |
+| lockmode | text | 当前线程正等待获取的锁模式。包含表级锁、行级锁、页级锁下的各模式。 |
+| block_sessionid | bigint | 阻塞当前线程获取锁的会话标识。 |
+| global_sessionid | text | 全局会话ID。 |
+
+wait_status列的等待状态有以下状态。
+
+**表 2** 等待状态列表<a id="等待状态列表"> </a>
+
+| wait_status值| 含义   |
+| :-------------------------| :------------------------------- |
+| none         | 没在等任意事件。                  |
+| acquire lock | 等待加锁，要么加锁成功，要么加锁等待超时。                   |
+| acquire lwlock                          | 等待获取轻量级锁。                |
+| wait io      | 等待IO完成。                      |
+| wait cmd     | 等待完成读取网络通信包。          |
+| wait pooler get conn                    | 等待pooler完成获取连接。          |
+| wait pooler abort conn                  | 等待pooler完成终止连接。          |
+| wait pooler clean conn                  | 等待pooler完成清理连接。          |
+| pooler create conn: [nodename], total N | 等待pooler建立连接，当前正在与nodename指定节点建立连接，且仍有N个连接等待建立。 |
+| get conn     | 获取到其他节点的连接。            |
+| set cmd: [nodename]                     | 在连接上执行SET/RESET/TRANSACTION BLOCK LEVEL PARA SET/SESSION LEVEL PARA SET，当前正在nodename指定节点上执行。 |
+| cancel query | 取消某连接上正在执行的SQL语句。   |
+| stop query   | 停止某连接上正在执行的查询。      |
+| wait node: nodename, total N, [phase]   | 等待接收与某节点的连接上的数据，当前正在等待nodename节点plevel线程的数据，且仍有N个连接的数据待返回。如果状态包含phase信息，则可能的阶段状态有: <br/>- begin: 表示处于事务开始阶段。<br/>- commit: 表示处于事务提交阶段。<br/>- rollback: 表示处于事务回滚阶段。 |
+| wait transaction sync: xid              | 等待xid指定事务同步。             |
+| wait wal sync| 等待特定LSN的wal log完成到备机的同步。                       |
+| wait data sync                          | 等待完成数据页到备机的同步。      |
+| wait data sync queue                    | 等待把行存的数据页或列存的CU放入同步队列。                   |
+| flush data: nodename, [phase]           | 等待向网络中nodename指定节点的plevel对应线程发送数据。如果状态包含phase信息，则可能的阶段状态为wait quota，即当前通信流正在等待quota值。 |
+| stream get conn: [nodename], total N    | 初始化stream flow时，等待与nodename节点的consumer对象建立连接，且当前有N个待建连对象。 |
+| wait producer ready: nodename, total N  | 初始化stream flow时，等待每个producer都准备好，当前正在等待nodename节点plevel对应线程的producer对象准备好，且仍有N个producer对象处于等待状态。 |
+| synchronize quit                        | stream plan结束时，等待stream线程组内的线程统一退出。        |
+| wait stream nodegroup destroy           | stream plan结束时，等待销毁stream node group。               |
+| wait active statement                   | 等待作业执行，正在资源负载管控中。|
+| analyze: [relname], [phase]             | 当前正在对表relname执行analyze。如果状态包含phase信息，则为autovacuum，表示是数据库自动开启AutoVacuum线程执行的analyze分析操作。 |
+| vacuum: [relname], [phase]              | 当前正在对表relname执行vacuum。如果状态包含phase信息，则为autovacuum，表示是数据库自动开启AutoVacuum线程执行的vacuum清理操作。 |
+| vacuum full: [relname]                  | 当前正在对表relname执行vacuum full清理。                     |
+| create index | 当前正在创建索引。                |
+| HashJoin - [ build hash | write file ] | 当前是HashJoin算子，主要关注耗时的执行阶段。<br/>- build hash: 表示当前HashJoin算子正在建立哈希表。<br/>- write file: 表示当前HashJoin算子正在将数据写入磁盘。 |
+| HashAgg - [ build hash | write file ]  | 当前是HashAgg算子，主要关注耗时的执行阶段。<br/>- build hash: 表示当前HashAgg算子正在建立哈希表。<br/>- write file: 表示当前HashAgg算子正在将数据写入磁盘。 |
+| HashSetop - [build hash | write file ] | 当前是HashSetop算子，主要关注耗时的执行阶段。<br/>- build hash: 表示当前HashSetop算子正在建立哈希表。<br/>- write file: 表示当前HashSetop算子正在将数据写入磁盘。 |
+| Sort | Sort - write file               | 当前是Sort算子做排序，write file表示Sort算子正在将数据写入磁盘。 |
+| Material | Material - write file       | 当前是Material算子，write file表示Material算子正在将数据写入磁盘。 |
+| NestLoop     | 当前是NestLoop算子。              |
+| wait memory  | 等待内存获取。                    |
+| wait sync consumer next step            | Stream算子等待消费者执行。        |
+| wait sync producer next step            | Stream算子等待生产者执行。        |
+
+当wait_status为acquire lwlock、acquire lock或者wait io时，表示有等待事件。正在等待获取wait_event列对应类型的轻量级锁、事务锁，或者正在进行IO。
+
+其中，wait_status值为acquire lwlock（轻量级锁）时对应的wait_event等待事件类型与描述信息如下。（wait_event为extension时，表示此时的轻量级锁是动态分配的锁，未被监控。）
+
+**表 3** 轻量级锁等待事件列表
+
+| wait_event类型| 类型描述     |
+| :--------------| :------------------|
+| ShmemIndexLock| 用于保护共享内存中的主索引哈希表。|
+| OidGenLock    | 用于避免不同线程产生相同的OID。   |
+| XidGenLock    | 用于避免两个事务获得相同的xid。   |
+| ProcArrayLock | 用于避免并发访问或修改ProcArray共享数组。                    |
+| SInvalReadLock| 用于避免与清理失效消息并发执行。  |
+| SInvalWriteLock                          | 用于避免与其它写失效消息、清理失效消息并发执行。             |
+| WALInsertLock | 用于避免与其它WAL插入操作并发执行。                          |
+| WALWriteLock  | 用于避免并发WAL写盘。             |
+| ControlFileLock                          | 用于避免pg_control文件的读写并发、写写并发。                 |
+| CheckpointLock| 用于避免多个checkpoint并发执行。  |
+| CLogControlLock                          | 用于避免并发访问或者修改Clog控制数据结构。                   |
+| SubtransControlLock                      | 用于避免并发访问或者修改子事务控制数据结构。                 |
+| MultiXactGenLock                         | 用于串行分配唯一MultiXact id。    |
+| MultiXactOffsetControlLock               | 用于避免对pg_multixact/offset的写写并发和读写并发。          |
+| MultiXactMemberControlLock               | 用于避免对pg_multixact/members的写写并发和读写并发。         |
+| RelCacheInitLock                         | 用于失效消息场景对init文件进行操作时加锁。                   |
+| CheckpointerCommLock                     | 用于向checkpointer发起文件刷盘请求场景，需要串行的向请求队列插入请求结构。 |
+| TwoPhaseStateLock                        | 用于避免并发访问或者修改两阶段信息共享数组。                 |
+| TablespaceCreateLock                     | 用于确定tablespace是否已经存在。  |
+| BtreeVacuumLock                          | 用于防止vacuum清理B-tree中还在使用的页面。                   |
+| AutovacuumLock| 用于串行化访问autovacuum worker数组。                        |
+| AutovacuumScheduleLock                   | 用于串行化分配需要vacuum的table。 |
+| AutoanalyzeLock                          | 用于获取和释放允许执行Autoanalyze的任务资源。                |
+| SyncScanLock  | 用于确定heap扫描时某个relfilenode的起始位置。                |
+| NodeTableLock | 用于保护存放数据库节点信息的共享结构。                       |
+| PoolerLock    | 用于保证两个线程不会同时从连接池里取到相同的连接。           |
+| RelationMappingLock                      | 用于等待更新系统表到存储位置之间映射的文件。                 |
+| AsyncCtlLock  | 用于避免并发访问或者修改共享通知状态。                       |
+| AsyncQueueLock| 用于避免并发访问或者修改共享通知信息队列。                   |
+| SerializableXactHashLock                 | 用于避免对于可串行事务共享结构的写写并发和读写并发。         |
+| SerializableFinishedListLock             | 用于避免对于已完成可串行事务共享链表的写写并发和读写并发。   |
+| SerializablePredicateLockListLock        | 用于保护对于可串行事务持有的锁链表。                         |
+| OldSerXidLock | 用于保护记录冲突可串行事务的结构。|
+| FileStatLock  | 用于保护存储统计文件信息的数据结构。                         |
+| SyncRepLock   | 用于在主备复制时保护xlog同步信息。|
+| DataSyncRepLock                          | 用于在主备复制时保护数据页同步信息。                         |
+| CStoreColspaceCacheLock                  | 用于保护列存表的CU空间分配。      |
+| CStoreCUCacheSweepLock                   | 用于列存CU Cache循环淘汰。        |
+| MetaCacheSweepLock                       | 用于元数据循环淘汰。              |
+| ExtensionConnectorLibLock                | 用于初始化ODBC连接场景，在加载与卸载特定动态库时进行加锁。   |
+| SearchServerLibLock                      | 用于GPU加速场景初始化加载特定动态库时，对读文件操作进行加锁。 |
+| LsnXlogChkFileLock                       | 用于串行更新特定结构中记录的主备机的xlog flush位置点。       |
+| ReplicationSlotAllocationLock            | 用于主备复制时保护主机端的流复制槽的分配。                   |
+| ReplicationSlotControlLock               | 用于主备复制时避免并发更新流复制槽状态。                     |
+| ResourcePoolHashLock                     | 用于避免并发访问或者修改资源池哈希表。                       |
+| WorkloadStatHashLock                     | 用于避免并发访问或者修改包含数据库主节点的SQL请求构成的哈希表。 |
+| WorkloadIoStatHashLock                   | 用于避免并发访问或者修改用于统计当前数据库节点的IO信息的哈希表。 |
+| WorkloadCGroupHashLock                   | 用于避免并发访问或者修改Cgroup信息构成的哈希表。             |
+| OBSGetPathLock| 用于避免对obs路径的写写并发和读写并发。                      |
+| WorkloadUserInfoLock                     | 用于避免并发访问或修改负载管理的用户信息哈希表。             |
+| WorkloadRecordLock                       | 用于避免并发访问或修改在内存自适应管理时对数据库主节点收到请求构成的哈希表。 |
+| WorkloadIOUtilLock                       | 用于保护记录iostat，CPU等负载信息的结构。                    |
+| WorkloadNodeGroupLock                    | 用于避免并发访问或者修改内存中的nodegroup信息构成的哈希表。  |
+| JobShmemLock  | 用于定时任务功能中保护定时读取的全局变量。                   |
+| OBSRuntimeLock| 用于获取环境变量，如GASSHOME。    |
+| LLVMDumpIRLock| 用于导出动态生成函数所对应的汇编语言。                       |
+| LLVMParseIRLock                          | 用于在查询开始处从IR文件中编译并解析已写好的IR函数。         |
+| CriticalCacheBuildLock                   | 用于从共享或者本地缓存初始化文件中加载cache的场景。          |
+| WaitCountHashLock                        | 用于保护用户语句计数功能场景中的共享结构。                   |
+| BufMappingLock| 用于保护对共享缓冲映射表的操作。  |
+| LockMgrLock   | 用于保护常规锁结构信息。          |
+| PredicateLockMgrLock                     | 用于保护可串行事务锁结构信息。    |
+| OperatorRealTLock                        | 用于避免并发访问或者修改记录算子级实时数据的全局结构。       |
+| OperatorHistLock                         | 用于避免并发访问或者修改记录算子级历史数据的全局结构。       |
+| SessionRealTLock                         | 用于避免并发访问或者修改记录query级实时数据的全局结构。      |
+| SessionHistLock                          | 用于避免并发访问或者修改记录query级历史数据的全局结构。      |
+| CacheSlotMappingLock                     | 用于保护CU Cache全局信息。        |
+| BarrierLock   | 用于保证当前只有一个线程在创建Barrier。                      |
+| dummyServerInfoCacheLock                 | 用于保护缓存加速MogDB连接信息的全局哈希表。                  |
+| RPNumberLock  | 用于加速MogDB的数据库节点对正在执行计划的任务线程的计数。    |
+| ClusterRPLock | 用于加速MogDB的CCN中维护的MogDB负载数据的并发存取控制。      |
+| CBMParseXlogLock                         | Cbm 解析xlog时的保护锁            |
+| RelfilenodeReuseLock                     | 避免错误地取消已重用的列属性文件的链接。                     |
+| RcvWriteLock  | 防止并发调用WalDataRcvWrite。     |
+| PercentileLock| 用于保护全局PercentileBuffer      |
+| CSNBufMappingLock                        | 保护csn页面                       |
+| UniqueSQLMappingLock                     | 用于保护uniquesql hash table      |
+| DelayDDLLock  | 防止并发ddl。                     |
+| CLOG Ctl      | 用于避免并发访问或者修改Clog控制数据结构                     |
+| Async Ctl     | 保护Async buffer                  |
+| MultiXactOffset Ctl                      | 保护MultiXact offet的slru buffer  |
+| MultiXactMember Ctl                      | 保护MultiXact member的slrubuffer  |
+| OldSerXid SLRU Ctl                       | 保护old xids的slru buffer         |
+| ReplicationSlotLock                      | 用于保护ReplicationSlot           |
+| PGPROCLock    | 用于保护pgproc                    |
+| MetaCacheLock | 用于保护MetaCache                 |
+| DataCacheLock | 用于保护datacache                 |
+| InstrUserLock | 用于保护InstrUserHTAB。           |
+| BadBlockStatHashLock                     | 用于保护global_bad_block_stat hash表。                       |
+| BufFreelistLock                          | 用于保证共享缓冲区空闲列表操作的原子性。                     |
+| CUSlotListLock| 用于控制列存缓冲区槽位的并发操作。|
+| AddinShmemInitLock                       | 保护共享内存对象的初始化。        |
+| AlterPortLock | 保护协调节点更改注册端口号的操作。|
+| FdwPartitionCaheLock                     | HDFS分区表缓冲区的管理锁。        |
+| DfsConnectorCacheLock                    | DFSConnector缓冲区的管理锁。      |
+| DfsSpaceCacheLock                        | HDFS表空间管理缓冲区的管理锁。    |
+| FullBuildXlogCopyStartPtrLock            | 用于保护全量Build中Xlog拷贝的操作。                          |
+| DfsUserLoginLock                         | 用于HDFS用户登录以及认证。        |
+| LogicalReplicationSlotPersistentDataLock | 用于保护逻辑复制过程中复制槽位的数据。                       |
+| WorkloadSessionInfoLock                  | 保护负载管理session info内存hash表访问。                     |
+| InstrWorkloadLock                        | 保护负载管理统计信息的内存hash表访问。                       |
+| PgfdwLock     | 用于管理实例向Foreign server建立连接。                       |
+| InstanceTimeLock                         | 用于获取实例中会话的时间信息。    |
+| XlogRemoveSegLock                        | 保护Xlog段文件的回收操作。        |
+| DnUsedSpaceHashLock                      | 用于更新会话对应的空间使用信息。  |
+| CsnMinLock    | 用于计算CSNmin。                  |
+| GPCCommitLock | 用于保护全局Plan Cache hash表的添加操作。                    |
+| GPCClearLock  | 用于保护全局Plan Cache hash表的清除操作。                    |
+| GPCTimelineLock                          | 用于保护全局Plan Cache hash表检查Timeline的操作。            |
+| TsTagsCacheLock                          | 用于时序tag缓存管理。             |
+| InstanceRealTLock                        | 用于保护共享实例统计信息hash表的更新操作。                   |
+| CLogBufMappingLock                       | 用于提交日志缓存管理。            |
+| GPCMappingLock| 用于全局Plan Cache缓存管理。      |
+| GPCPrepareMappingLock                    | 用于全局Plan Cache缓存管理。      |
+| BufferIOLock  | 保护共享缓冲区页面的IO操作。      |
+| BufferContentLock                        | 保护共享缓冲区页面内容的读取、修改。                         |
+| CSNLOG Ctl    | 用于CSN日志管理。                 |
+| DoubleWriteLock                          | 用于双写的管理操作。              |
+| RowPageReplicationLock                   | 用于管理行存储的数据页复制。      |
+| extension     | 其他轻量锁。                      |
+
+当wait_status值为wait io时对应的wait_event等待事件类型与描述信息如下。
+
+**表 4** IO等待事件列表
+
+| wait_event类型             | 类型描述                          |
+| :------------------------- | :----------------------------|
+| BufFileRead                | 从临时文件中读取数据到指定buffer。|
+| BufFileWrite               | 向临时文件中写入指定buffer中的内容。                         |
+| ControlFileRead            | 读取pg_control文件。主要在数据库启动、执行checkpoint和主备校验过程中发生。 |
+| ControlFileSync            | 将pg_control文件持久化到磁盘。数据库初始化时发生。           |
+| ControlFileSyncUpdate      | 将pg_control文件持久化到磁盘。主要在数据库启动、执行checkpoint和主备校验过程中发生。 |
+| ControlFileWrite           | 写入pg_control文件。数据库初始化时发生。                     |
+| ControlFileWriteUpdate     | 更新pg_control文件。主要在数据库启动、执行checkpoint和主备校验过程中发生。 |
+| CopyFileRead               | copy文件时读取文件内容。          |
+| CopyFileWrite              | copy文件时写入文件内容。          |
+| DataFileExtend             | 扩展文件时向文件写入内容。        |
+| DataFileFlush              | 将表数据文件持久化到磁盘          |
+| DataFileImmediateSync      | 将表数据文件立即持久化到磁盘。    |
+| DataFilePrefetch           | 异步读取表数据文件。              |
+| DataFileRead               | 同步读取表数据文件。              |
+| DataFileSync               | 将表数据文件的修改持久化到磁盘。  |
+| DataFileTruncate           | 表数据文件truncate。              |
+| DataFileWrite              | 向表数据文件写入内容。            |
+| LockFileAddToDataDirRead   | 读取"postmaster.pid"文件。        |
+| LockFileAddToDataDirSync   | 将"postmaster.pid"内容持久化到磁盘。                         |
+| LockFileAddToDataDirWrite  | 将pid信息写到"postmaster.pid"文件。                          |
+| LockFileCreateRead         | 读取LockFile文件"%s.lock"。       |
+| LockFileCreateSync         | 将LockFile文件"%s.lock"内容持久化到磁盘。                    |
+| LockFileCreateWRITE        | 将pid信息写到LockFile文件"%s.lock"。                         |
+| RelationMapRead            | 读取系统表到存储位置之间的映射文件|
+| RelationMapSync            | 将系统表到存储位置之间的映射文件持久化到磁盘。               |
+| RelationMapWrite           | 写入系统表到存储位置之间的映射文件。                         |
+| ReplicationSlotRead        | 读取流复制槽文件。重新启动时发生。|
+| ReplicationSlotRestoreSync | 将流复制槽文件持久化到磁盘。重新启动时发生。                 |
+| ReplicationSlotSync        | checkpoint时将流复制槽临时文件持久化到磁盘。                 |
+| ReplicationSlotWrite       | checkpoint时写流复制槽临时文件。  |
+| SLRUFlushSync              | 将pg_clog、pg_subtrans和pg_multixact文件持久化到磁盘。主要在执行checkpoint和数据库停机时发生。 |
+| SLRURead                   | 读取pg_clog、pg_subtrans和pg_multixact文件。                 |
+| SLRUSync                   | 将脏页写入文件pg_clog、pg_subtrans和pg_multixact并持久化到磁盘。主要在执行checkpoint和数据库停机时发生。 |
+| SLRUWrite                  | 写入pg_clog、pg_subtrans和pg_multixact文件。                 |
+| TimelineHistoryRead        | 读取timeline history文件。在数据库启动时发生。               |
+| TimelineHistorySync        | 将timeline history文件持久化到磁盘。在数据库启动时发生。     |
+| TimelineHistoryWrite       | 写入timeline history文件。在数据库启动时发生。               |
+| TwophaseFileRead           | 读取pg_twophase文件。在两阶段事务提交、两阶段事务恢复时发生。 |
+| TwophaseFileSync           | 将pg_twophase文件持久化到磁盘。在两阶段事务提交、两阶段事务恢复时发生。 |
+| TwophaseFileWrite          | 写入pg_twophase文件。在两阶段事务提交、两阶段事务恢复时发生。 |
+| WALBootstrapSync           | 将初始化的WAL文件持久化到磁盘。在数据库初始化发生。          |
+| WALBootstrapWrite          | 写入初始化的WAL文件。在数据库初始化发生。                    |
+| WALCopyRead                | 读取已存在的WAL文件并进行复制时产生的读操作。在执行归档恢复完后发生。 |
+| WALCopySync                | 将复制的WAL文件持久化到磁盘。在执行归档恢复完后发生。        |
+| WALCopyWrite               | 读取已存在WAL文件并进行复制时产生的写操作。在执行归档恢复完后发生。 |
+| WALInitSync                | 将新初始化的WAL文件持久化磁盘。在日志回收或写日志时发生。    |
+| WALInitWrite               | 将新创建的WAL文件初始化为0。在日志回收或写日志时发生。       |
+| WALRead                    | 从xlog日志读取数据。两阶段文件redo相关的操作产生。           |
+| WALSyncMethodAssign        | 将当前打开的所有WAL文件持久化到磁盘。                        |
+| WALWrite                   | 写入WAL文件。                     |
+| WALBufferAccess            | WAL Buffer访问（出于性能考虑，内核代码里只统计访问次数，未统计其访问耗时）。 |
+| WALBufferFull              | WAL Buffer满时，写wal文件相关的处理。                        |
+| DoubleWriteFileRead        | 双写 文件读取。                   |
+| DoubleWriteFileSync        | 双写 文件强制刷盘。               |
+| DoubleWriteFileWrite       | 双写 文件写入。                   |
+| PredoProcessPending        | 并行日志回放中当前记录回放等待其它记录回放完成。             |
+| PredoApply                 | 并行日志回放中等待当前工作线程等待其他线程回放至本线程LSN。  |
+| DisableConnectFileRead     | HA锁分片逻辑文件读取。            |
+| DisableConnectFileSync     | HA锁分片逻辑文件强制刷盘。        |
+| DisableConnectFileWrite    | HA锁分片逻辑文件写入。            |
+
+当wait_status值为acquire lock（事务锁）时对应的wait_event等待事件类型与描述信息如下。
+
+**表 5** 事务锁等待事件列表
+
+| wait_event类型   | 类型描述              |
+| :--------------- | :-------------------- |
+| relation         | 对表加锁。            |
+| extend           | 对表扩展空间时加锁。  |
+| partition        | 对分区表加锁。        |
+| partition_seq    | 对分区表的分区加锁。  |
+| page             | 对表页面加锁。        |
+| tuple            | 对页面上的tuple加锁。 |
+| transactionid    | 对事务ID加锁。        |
+| virtualxid       | 对虚拟事务ID加锁。    |
+| object           | 加对象锁。            |
+| cstore_freespace | 对列存空闲空间加锁。  |
+| userlock         | 加用户锁。            |
+| advisory         | 加advisory锁。        |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TIMEZONE_ABBREVS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TIMEZONE_ABBREVS.md
new file mode 100644
index 0000000000000000000000000000000000000000..e7016b537fd4330d2a4e0bc50edd86e17a7e5f03
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TIMEZONE_ABBREVS.md
@@ -0,0 +1,18 @@
+---
+title: PG_TIMEZONE_ABBREVS
+summary: PG_TIMEZONE_ABBREVS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_TIMEZONE_ABBREVS
+
+PG_TIMEZONE_ABBREVS视图提供了显示了所有可用的时区信息。
+
+**表 1** PG_TIMEZONE_ABBREVS字段
+
+| 名称       | 类型     | 描述                                            |
+| :--------- | :------- | :---------------------------------------------- |
+| abbrev     | text     | 时区名缩写。                                    |
+| utc_offset | interval | 相对于UTC的偏移量。                             |
+| is_dst     | Boolean  | 如果当前正处于夏令时范围则为TRUE，否则为FALSE。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TIMEZONE_NAMES.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TIMEZONE_NAMES.md
new file mode 100644
index 0000000000000000000000000000000000000000..c49e83c61c0e919c0589fa8bc584684491e70e19
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TIMEZONE_NAMES.md
@@ -0,0 +1,19 @@
+---
+title: PG_TIMEZONE_NAMES
+summary: PG_TIMEZONE_NAMES
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_TIMEZONE_NAMES
+
+PG_TIMEZONE_NAMES视图提供了显示了所有能够被SET TIMEZONE识别的时区名及其缩写、UTC偏移量、是否夏时制。
+
+**表 1** PG_TIMEZONE_NAMES字段
+
+| 名称       | 类型     | 描述                                            |
+| :--------- | :------- | :---------------------------------------------- |
+| name       | text     | 时区名。                                        |
+| abbrev     | text     | 时区名缩写。                                    |
+| utc_offset | interval | 相对于UTC的偏移量。                             |
+| is_dst     | Boolean  | 如果当前正处于夏令时范围则为TRUE，否则为FALSE。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TOTAL_MEMORY_DETAIL.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TOTAL_MEMORY_DETAIL.md
new file mode 100644
index 0000000000000000000000000000000000000000..96b6ace0ef72a5688d79e69c873fd7272c3e38a6
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TOTAL_MEMORY_DETAIL.md
@@ -0,0 +1,18 @@
+---
+title: PG_TOTAL_MEMORY_DETAIL
+summary: PG_TOTAL_MEMORY_DETAIL
+author: Guo Huan
+date: 2021-06-07
+---
+
+# PG_TOTAL_MEMORY_DETAIL
+
+PG_TOTAL_MEMORY_DETAIL视图显示某个数据库节点内存使用情况。
+
+**表 1** PG_TOTAL_MEMORY_DETAIL字段
+
+| 名称         | 类型    | 描述                       |
+| :----------- | :------ | :------------------------- |
+| nodename     | text    | 节点名称。                 |
+| memorytype   | text    | 内存的名称。               |
+| memorymbytes | integer | 内存使用的大小，单位为MB。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TOTAL_USER_RESOURCE_INFO.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TOTAL_USER_RESOURCE_INFO.md
new file mode 100644
index 0000000000000000000000000000000000000000..40beee736e99c0e46d8e7a4c16af3bdafc5bb732
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TOTAL_USER_RESOURCE_INFO.md
@@ -0,0 +1,32 @@
+---
+title: PG_TOTAL_USER_RESOURCE_INFO
+summary: PG_TOTAL_USER_RESOURCE_INFO
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_TOTAL_USER_RESOURCE_INFO
+
+PG_TOTAL_USER_RESOURCE_INFO视图显示所有用户资源使用情况，需要使用管理员用户进行查询。此视图在参数use_workload_manager为on时才有效。其中，IO相关监控项在参数enable_logical_io_statistics为on时才有效。
+
+**表 1** PG_TOTAL_USER_RESOURCE_INFO字段
+
+| 名称              | 类型             | 描述                                                         |
+| :---------------- | :--------------- | :----------------------------------------------------------- |
+| username          | name             | 用户名。                                                     |
+| used_memory       | integer          | 正在使用的内存大小，单位MB。                                 |
+| total_memory      | integer          | 可以使用的内存大小，单位MB。值为0表示未限制最大可用内存，其限制取决于数据库最大可用内存。 |
+| used_cpu          | double precision | 正在使用的CPU核数（仅统计复杂作业CPU使用情况，且该值为相关控制组的CPU使用统计值）。 |
+| total_cpu         | integer          | 在该机器节点上，用户关联控制组的CPU核数总和。                |
+| used_space        | bigint           | 已使用的永久表存储空间大小，单位KB。                         |
+| total_space       | bigint           | 可使用的永久表存储空间大小，单位KB，值为-1表示未限制最大存储空间。 |
+| used_temp_space   | bigint           | 已使用的临时空间大小，单位KB。                               |
+| total_temp_space  | bigint           | 可使用的临时空间总大小，单位KB，值为-1表示未限制。           |
+| used_spill_space  | bigint           | 已使用的算子落盘空间大小，单位KB。                           |
+| total_spill_space | bigint           | 可使用的算子落盘空间总大小，单位KB，值为-1表示未限制。       |
+| read_kbytes       | bigint           | 数据库主节点：过去5秒内，该用户在数据库节点上复杂作业read的字节总数（单位KB）。<br/>数据库节点：实例启动至当前时间为止，该用户复杂作业read的字节总数（单位KB）。 |
+| write_kbytes      | bigint           | 数据库主节点：过去5秒内，该用户在数据库节点上复杂作业write的字节总数（单位KB）。<br/>数据库节点：实例启动至当前时间为止，该用户复杂作业write的字节总数（单位KB）。 |
+| read_counts       | bigint           | 数据库主节点：过去5秒内，该用户在数据库节点上复杂作业read的次数之和（单位次）。<br/>数据库节点：实例启动至当前时间为止，该用户复杂作业read的次数之和（单位次）。 |
+| write_counts      | bigint           | 数据库主节点：过去5秒内，该用户在数据库节点上复杂作业write的次数之和（单位次）。<br/>数据库节点：实例启动至当前时间为止，该用户复杂作业write的次数之和（单位次）。 |
+| read_speed        | double precision | 数据库主节点：过去5秒内，该用户在单个数据库节点上复杂作业read平均速率（单位KB/s）。<br/>数据库节点：过去5秒内，该用户在该数据库节点上复杂作业read平均速率（单位KB/s）。 |
+| write_speed       | double precision | 数据库主节点：过去5秒内，该用户在单个数据库节点上复杂作业write平均速率（单位KB/s）。<br/>数据库节点：过去5秒内，该用户在该数据库节点上复杂作业write平均速率（单位KB/s）。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TOTAL_USER_RESOURCE_INFO_OID.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TOTAL_USER_RESOURCE_INFO_OID.md
new file mode 100644
index 0000000000000000000000000000000000000000..7d25d4b056897e3c3cc0fe29922bc6df2697444d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_TOTAL_USER_RESOURCE_INFO_OID.md
@@ -0,0 +1,32 @@
+---
+title: PG_TOTAL_USER_RESOURCE_INFO_OID
+summary: PG_TOTAL_USER_RESOURCE_INFO_OID
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_TOTAL_USER_RESOURCE_INFO_OID
+
+PG_TOTAL_USER_RESOURCE_INFO_OID视图显示所有用户资源使用情况，需要使用管理员用户进行查询。此视图在参数use_workload_manager为on时才有效。
+
+**表 1** PG_TOTAL_USER_RESOURCE_INFO_OID字段
+
+| 名称              | 类型             | 描述                                                         |
+| :---------------- | :--------------- | :----------------------------------------------------------- |
+| userid            | oid              | 用户ID。                                                     |
+| used_memory       | integer          | 正在使用的内存大小，单位MB。                                 |
+| total_memory      | integer          | 可以使用的内存大小，单位MB。值为0表示未限制最大可用内存，其限制取决于数据库最大可用内存。 |
+| used_cpu          | double precision | 正在使用的CPU核数。                                          |
+| total_cpu         | integer          | 在该机器节点上，用户关联控制组的CPU核数总和。                |
+| used_space        | bigint           | 已使用的存储空间大小，单位KB。                               |
+| total_space       | bigint           | 可使用的存储空间大小，单位KB，值为-1表示未限制最大存储空间。 |
+| used_temp_space   | bigint           | 已使用的临时空间大小，单位KB                                 |
+| total_temp_space  | bigint           | 可使用的临时空间总大小，单位KB，值为-1表示未限制。           |
+| used_spill_space  | bigint           | 已使用的下盘空间大小。单位KB。                               |
+| total_spill_space | bigint           | 可使用的下盘空间总大小，单位KB，值为-1表示未限制。           |
+| read_kbytes       | bigint           | 读磁盘数据量，单位KB。                                       |
+| write_kbytes      | bigint           | 写磁盘数据量，单位KB。                                       |
+| read_counts       | bigint           | 读磁盘次数。                                                 |
+| write_counts      | bigint           | 写磁盘次数。                                                 |
+| read_speed        | double precision | 读磁盘速率，单位B/ms。                                       |
+| write_speed       | double precision | 写磁盘速率，单位B/ms。                                       |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_USER.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_USER.md
new file mode 100644
index 0000000000000000000000000000000000000000..09ba7e1760b992f49f3e0b0da871d6f08020272d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_USER.md
@@ -0,0 +1,31 @@
+---
+title: PG_USER
+summary: PG_USER
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_USER
+
+PG_USER视图提供了访问数据库用户的信息，默认只有初始化用户和具有sysadmin属性的用户可以查看，其余用户需要赋权后才可以查看。
+
+**表 1** PG_USER字段
+
+| 名称            | 类型                     | 描述                                                         |
+| :-------------- | :----------------------- | :----------------------------------------------------------- |
+| usename         | name                     | 用户名。                                                     |
+| usesysid        | oid                      | 此用户的ID。                                                 |
+| usecreatedb     | Boolean                  | 用户是否可以创建数据库。                                     |
+| usesuper        | Boolean                  | 用户是否是拥有最高权限的初始系统管理员。                     |
+| usecatupd       | Boolean                  | 用户是否可以直接更新系统表。只有usesysid=10的初始系统管理员拥有此权限。其他用户无法获得此权限。 |
+| userepl         | Boolean                  | 用户是否可以复制数据流。                                     |
+| passwd          | text                     | 密文存储后的用户口令，始终为\*\*\*\*\*\*\*\*。               |
+| valbegin        | timestamp with time zone | 帐户的有效开始时间；如果没有设置有效开始时间，则为NULL。     |
+| valuntil        | timestamp with time zone | 帐户的有效结束时间；如果没有设置有效结束时间，则为NULL。     |
+| respool         | name                     | 用户所在的资源池。                                           |
+| parent          | oid                      | 父用户OID。                                                  |
+| spacelimit      | text                     | 永久表存储空间限额。                                         |
+| tempspacelimit  | text                     | 临时表存储空间限额。                                         |
+| spillspacelimit | text                     | 算子落盘空间限额。                                           |
+| useconfig       | text[]                   | 运行时配置参数的会话缺省。                                   |
+| nodegroup       | name                     | 用户关联的逻辑MogDB名称，如果该用户没有管理逻辑MogDB，则该字段为空。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_USER_MAPPINGS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_USER_MAPPINGS.md
new file mode 100644
index 0000000000000000000000000000000000000000..87d6b644b280e8f27211044d026dcafc1152d7d8
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_USER_MAPPINGS.md
@@ -0,0 +1,23 @@
+---
+title: PG_USER_MAPPINGS
+summary: PG_USER_MAPPINGS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_USER_MAPPINGS
+
+PG_USER_MAPPINGS视图提供访问关于用户映射的信息的接口。
+
+这个视图只是一个PG_USER_MAPPING的可读部分的视图化表现，如果用户无权使用它则查询该表时，有些选项字段会显示为空。普通用户需要授权才可以访问。
+
+**表 1** PG_USER_MAPPINGS字段
+
+| 名称      | 类型    | 引用                      | 描述                                                         |
+| :-------- | :------ | :------------------------ | :----------------------------------------------------------- |
+| umid      | oid     | PG_USER_MAPPING.oid       | 用户映射的OID。                                              |
+| srvid     | oid     | PG_FOREIGN_SERVER.oid     | 包含这个映射的外部服务器的OID。                              |
+| srvname   | name    | PG_FOREIGN_SERVER.srvname | 外部服务器的名称。                                           |
+| umuser    | oid     | PG_AUTHID.oid             | 被映射的本地角色的OID，如果用户映射是公共的则为0。           |
+| usename   | name    | -                         | 被映射的本地用户的名称。                                     |
+| umoptions | text[ ] | -                         | 如果当前用户是外部服务器的所有者，则为用户映射指定选项，使用"keyword=value"字符串，否则为null。 |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_VARIABLE_INFO.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_VARIABLE_INFO.md
new file mode 100644
index 0000000000000000000000000000000000000000..5ae1ec187fbc5f1e2bcbb397d8ce9df2bfb67c42
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_VARIABLE_INFO.md
@@ -0,0 +1,26 @@
+---
+title: PG_VARIABLE_INFO
+summary: PG_VARIABLE_INFO
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_VARIABLE_INFO
+
+PG_VARIABLE_INFO视图用于查询MogDB中当前节点的xid、oid的状态。
+
+**表 1** PG_VARIABLE_INFO字段
+
+| 名称                     | 类型 | 描述                                     |
+| :----------------------- | :--- | :--------------------------------------- |
+| node_name                | text | 节点名称。                               |
+| next_oid                 | oid  | 该节点下一次生成的oid。                  |
+| next_xid                 | xid  | 该节点下一次生成的事务号。               |
+| oldest_xid               | xid  | 该节点最老的事务号。                     |
+| xid_vac_limit            | xid  | 强制autovacuum的临界点。                 |
+| oldest_xid_db            | oid  | 该节点datafrozenxid最小的数据库oid。     |
+| last_extend_csn_logpage  | xid  | 最后一次扩展csnlog的页面号。             |
+| start_extend_csn_logpage | xid  | csnlog扩展的起始页面号。                 |
+| next_commit_seqno        | xid  | 该节点下次生成的csn号。                  |
+| latest_completed_xid     | xid  | 该节点提交或者回滚后节点上的最新事务号。 |
+| startup_max_xid          | xid  | 该节点关机前的最后一个事务号。           |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_VIEWS.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_VIEWS.md
new file mode 100644
index 0000000000000000000000000000000000000000..4a684b6d9017139b1be921079ff0087967ef0874
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PG_VIEWS.md
@@ -0,0 +1,19 @@
+---
+title: PG_VIEWS
+summary: PG_VIEWS
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PG_VIEWS
+
+PG_VIEWS视图提供访问数据库中每个视图的有用信息。
+
+**表 1** PG_VIEWS字段
+
+| 名称       | 类型 | 引用                 | 描述               |
+| :--------- | :--- | :------------------- | :----------------- |
+| schemaname | name | PG_NAMESPACE.nspname | 包含视图的模式名。 |
+| viewname   | name | PG_CLASS.relname     | 视图名。           |
+| viewowner  | name | PG_AUTHID.Erolname   | 视图的所有者。     |
+| definition | text | -                    | 视图的定义。       |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PLAN_TABLE.md b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PLAN_TABLE.md
new file mode 100644
index 0000000000000000000000000000000000000000..c6fa9983f091b29575ebc4c95233b3016d49e14b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/system-catalogs-and-system-views/system-views/PLAN_TABLE.md
@@ -0,0 +1,31 @@
+---
+title: PLAN_TABLE
+summary: PLAN_TABLE
+author: Guo Huan
+date: 2021-04-19
+---
+
+# PLAN_TABLE
+
+PLAN_TABLE显示用户通过执行EXPLAIN PLAN收集到的计划信息。计划信息的生命周期是session级别，session退出后相应的数据将被清除。同时不同session和不同user间的数据是相互隔离的。
+
+**表 1** PLAN_TABLE字段
+
+| 名称         | 类型           | 描述                                                         |
+| :----------- | :------------- | :----------------------------------------------------------- |
+| statement_id | varchar2(30)   | 用户输入的查询标签。                                         |
+| plan_id      | bigint         | 查询标识。                                                   |
+| id           | int            | 查询生成的计划中的每一个执行算子的编号。                     |
+| operation    | varchar2(30)   | 计划中算子的操作描述。                                       |
+| options      | varchar2(255)  | 操作选项。                                                   |
+| object_name  | name           | 操作对应的对象名，非查询中使用到的对象别名。来自于用户定义。 |
+| object_type  | varchar2(30)   | 对象类型。                                                   |
+| object_owner | name           | 对象所属schema，来自于用户定义。                             |
+| projection   | varchar2(4000) | 操作输出的列信息。                                           |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+>
+> - object_type取值范围为PG_CLASS中定义的relkind类型（TABLE普通表，INDEX索引，SEQUENCE序列，VIEW视图，COMPOSITE TYPE复合类型，TOASTVALUE TOAST表）和计划使用到的rtekind(SUBQUERY, JOIN, FUNCTION, VALUES, CTE, REMOTE_QUERY)。
+> - object_owner对于RTE来说是计划中使用的对象描述，非用户定义的类型不存在object_owner。
+> - statement_id、object_name、object_owner、projection字段内容遵循用户定义的大小写存储，其它字段内容采用大写存储。
+> - 支持用户对PLAN_TABLE进行SELECT和DELETE操作，不支持其它DML操作。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/FAQ.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/FAQ.md
new file mode 100644
index 0000000000000000000000000000000000000000..11474752456113ccc5465ed0ef569ac253c54111
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/FAQ.md
@@ -0,0 +1,133 @@
+---
+title: FAQ
+summary: FAQ
+author: Zhang Cuiping
+date: 2021-11-17
+---
+
+# FAQ
+
+## 执行命令报错“Failed to obtain the GPHOME”
+
+### 问题现象
+
+如果在root用户下执行工具命令时，出现如下信息。
+
+```bash
+Failed to obtain the GPHOME.
+```
+
+### 原因分析
+
+可能是环境变量中GPHOME变量没有配置正确。需要检查环境变量GPHOME是否包含MogDBXML中gaussdbToolPath路径。
+
+### 操作步骤
+
+使用如下命令检查$GPHOME路径。
+
+```bash
+echo $GPHOME
+```
+
+如果不是安装时默认的路径，请在配置文件中修改GPHOME的路径。
+
+```bash
+vim /etc/profile
+```
+
+## gs_ctl 重建备实例过程被中断导致秘钥文件不完整恢复方法
+
+### 问题现象
+
+用户在重建备实例的过程中被中断，再次重建备实例失败，出现以下报错信息。
+
+```bash
+CRC checksum does not match value stored in file, maybe the cipher file is corrupt
+non obs cipher file or random parameter file is invalid.
+read cipher file or random parameter file failed.
+2020-06-18 20:58:12.080 5eeb64e3.1 [unknown] 140697304617088 [unknown] 0 dn_6001_6002 F0000 0 [BACKEND] FATAL:  could not load server certificate file "server.crt": no start line
+[2020-06-18 20:58:12.086][24066][dn_6001_6002][gs_ctl]:  waitpid 24446 failed, exitstatus is 256, ret is 2
+```
+
+### 原因分析
+
+重建中断时证书文件不完整，再次重建会由于证书文件不完整而失败。
+
+### 操作步骤
+
+1. 在数据目录下查看证书文件大小。
+
+   ```bash
+   ll
+   查看秘钥文件大小
+   -rw------- 1 omm omm       0 Jun 18 20:58 server.crt
+   -rw------- 1 omm omm       0 Jun 18 20:58 server.key
+   -rw------- 1 omm omm       0 Jun 18 20:58 server.key.cipher
+   -rw------- 1 omm omm       0 Jun 18 20:58 server.key.rand
+   ```
+
+2. 若证书文件大小为0，删除证书文件。
+
+   ```bash
+   rm -rf server.crt server.key server.key.cipher server.key.rand
+   ```
+
+3. 重建备实例。
+
+   ```bash
+   gs_ctl build -D data_dir
+   ```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 若备机数据库已停止，需要重新生成证书文件或者复制证书文件（$GAUSSHOME/share下的证书文件）到数据目录，启动备机并重建备实例。生成证书文件的相关操作请参见《开发者指南》。
+
+## 使用gs_om -t status --all查询集群状态，长时间没有响应
+
+### 问题现象
+
+使用gs_om -t status --all命令后长时间无响应。
+
+### 原因分析
+
+可能是gaussdb进程hang住，查询动作会调用gsql或者gs_ctl工具查询数据库状态，进程hang住后不会给响应，直到超时后退出。
+
+### 操作步骤
+
+1. 查看gsql能否访问数据库，出现下面提示说明gaussdb进程hang住，数据库异常。
+
+   ```bash
+   gsql -d postgres -p 29776
+   gsql: wait (null):29776 timeout expired, errno: Success
+   ```
+
+2. 查看postgresql-*.log是否有错误提示，根据提示解决问题。
+
+   ```bash
+   cd $GAUSSLOG/pg_log/dn_6001;grep "ERROR\|FATAL" postgresql-*.log
+   ```
+
+3. 数据库已经hang住，gs_om命令不起作用，可以直接到每个节点上查找进程pid后kill。
+
+   ```bash
+   ps -ef|grep $GAUSSHOME/bin/gaussdb|grep -v grep
+   kill -9 $pid
+   ```
+
+4. 所有节点进程kill完毕后在某一节点执行启动命令。测试环境下可以直接重启数据库，生产商用环境请联系技术支持工程师。
+
+   ```bash
+   gs_om -t start
+   ```
+
+## gs_sshexkey 相同用户不同密码报错
+
+### 问题现象
+
+openEuler环境下，gs_sshexkey支持相同用户不同密码做互信，但是输入了正确的密码还是报鉴权失败。
+
+### 原因分析
+
+打开系统日志/var/log/secure,查看到有**pam_faillock(sshd:auth): Consecutive login failures for user**日志，说明当前用户密码试错次数太多被暂时锁定。
+
+### 操作步骤
+
+在/etc/pam.d目录下修改相关配置文件system-auth、password-auth、password-auth-crond，将文件中deny=3的地方适当放大，待互信全部建立完成后再恢复。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/client-tool.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/client-tool.md
new file mode 100644
index 0000000000000000000000000000000000000000..a222e142d56cf8239f968ec32453960dc5e0d2b5
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/client-tool.md
@@ -0,0 +1,941 @@
+---
+title: 客户端工具
+summary: 客户端工具
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# 客户端工具
+
+数据库在部署成功后，需要通过一些工具来便捷地连接数据库，对数据库进行各种操作和调试。MogDB提供了一些数据库连接工具。通过这些工具可以方便地连接数据库并对数据库进行数据操作。
+
+## gsql
+
+gsql是MogDB提供在命令行下运行的数据库连接工具，可以通过此工具连接服务器并对其进行操作和维护，除了具备操作数据库的基本功能，gsql还提供了若干高级特性，便于用户使用。
+
+### gsql概述
+
+**基本功能**
+
+- **连接数据库：**详细操作请参见《管理指南》中“日常运维 &gt; [gsql客户端连接](using-the-gsql-client-for-connection)”章节。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** gsql创建连接时，数据库默认设置会有5分钟超时时间。如果在这个时间内，数据库未正确地接受连接并对身份进行认证，gsql将超时退出。 针对此问题，可以参考[常见问题处理](#常见问题处理)。
+
+- **执行SQL语句：**支持交互式地键入并执行SQL语句，也可以执行一个文件中指定的SQL语句。
+
+- **执行元命令：**元命令可以帮助管理员查看数据库对象的信息、查询缓存区信息、格式化SQL输出结果，以及连接到新的数据库等。元命令的详细说明请参见[元命令参考](#元命令参考)。
+
+**高级特性**
+
+gsql的高级特性如[表1](#gsql)所示。
+
+**表 1** gsql高级特性 <a id="gsql"> </a>
+
+| 特性名称           | 描述                                     |
+| :----------------- | :--------------------------------------- |
+| 变量               | gsql提供类似于Linux的shell命令的变量特性，可以使用gsql的原命令\set设置一个变量，格式如下：<br />`\set varname value`<br />要删除一个变量请使用如下方式：<br />`\unset varname`<br />说明：<br />- 变量只是简单的名称/值对，这里的值可以是任意长度。<br />- 变量名称必须由字母（包括非拉丁字母）、数字和下划线组成，且对大小写敏感。<br />- 如果使用\\set varname的格式（不带第二个参数），则只是设置这个变量而没有给变量赋值。<br />- 可以使用不带参数的\\set来显示所有变量的值。<br />变量的示例和详细说明请参见**变量**。 |
+| SQL代换            | 利用gsql的变量特性，可以将常用的SQL语句设置为变量，以简化操作。<br />SQL代换的示例和详细说明请参见**SQL代换**。 |
+| 自定义提示符       | gsql使用的提示符支持用户自定义。可以通过修改gsql预留的三个变量PROMPT1、PROMPT2、PROMPT3来改变提示符。<br />这三个变量的值可以用户自定义，也可以使用gsql预定义的值。详细请参见**提示符**。 |
+| 命令自动补齐       | 根据MogDB语法规则，gsql支持使用Tab键进行命令的自动补齐，当编译时指定了选项-with-readline，且客户端连接时指定“-r”参数，此功能被打开。例如，crea后键入Tab，gsql会将其补齐为create。<br />说明：<br />- 支持数据库SQL关键字如select、create、table等。<br />- 支持表名、视图名等自定义标识符的补齐。<br />- 元命令选项'S'、'+'不支持自动补齐。<br />- 对表进行补齐时，只有前缀是”pg_“才会补齐系统表。<br />- 不支持建表时字段类型的补齐。<br />- select后不支持任何补齐。<br />- 不支持常量与宏的自动补齐。<br />- select * from a,b… 不支持第二个开始表的自动补齐, insert into t1 (col1, col2, …) 不支持第二个列的自动补齐。<br />- 不支持create tablespace语句with以及with后参数的自动补齐。<br />- 创建索引不支持local、global的自动补齐，修改索引不支持rebuild自动补齐。<br />- set语句仅支持自动补全user和superuser级别的参数。<br />- 不支持if exists的自动补齐。<br />- 不支持表名.列名的自动补齐，如alter sequence <name> owned by tableName.colName，owned by。<br />- 不支持自定义操作符自动补齐。<br />- 使用复制粘贴这种方式输入命令，如果粘贴的命令里面有TAB键有可能会使输入命令的格式错乱，无法正常执行。 |
+| 客户端操作历史记录 | gsql支持客户端操作历史记录，当客户端连接时指定“-r”参数，此功能被打开。可以通过\\set设置记录历史的条数，例如，\set HISTSIZE 50，将记录历史的条数设置为50，\\set HISTSIZE 0，不记录历史。<br />说明：<br />- 客户端操作历史记录条数默认设置为32条，最多支持记录500条。当客户端交互式输入包含中文字符时，只支持UTF-8 的编码环境。<br />- 出于安全考虑，将包含PASSWORD、IDENTIFIED敏感词的记录识别为敏感信息，不会记录到历史信息中，即不能通过上下翻回显
+
+- 变量
+
+  可以使用gsql元命令\\set设置一个变量。例如把变量foo的值设置为bar：
+
+  ```sql
+  mogdb=# \set foo bar
+  ```
+
+  要引用变量的值，在变量前面加冒号。例如查看变量的值：
+
+  ```sql
+  mogdb=# \echo :foo
+  bar
+  ```
+
+  这种变量的引用方法适用于正规的SQL语句和元命令。
+
+  gsql预定义了一些特殊变量，同时也规划了变量的取值。为了保证和后续版本最大限度地兼容，请避免以其他目的使用这些变量。所有特殊变量见[表2](#teshubian)。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  >
+  > - 所有特殊变量都由大写字母、数字和下划线组成。
+  > - 要查看特殊变量的默认值，请使用元命令`\echo : _varname_`（例如`\echo :DBNAME`）。
+
+  **表 2** 特殊变量设置 <a id="teshubian"> </a>
+
+  | 变量              | 设置方法                      | 变量说明                     |
+  | :---------------- | :--------------------------- | :--------------------------  |
+  | ECHO              | `\set ECHO all | queries`                         | - 如果设置为all，只显示查询信息。设置为all等效于使用gsql连接数据库时指定-a参数。 <br />- 如果设置为queries，显示命令行和查询信息。等效于使用gsql连接数据库时指定-e参数。 |
+  | ECHO_HIDDEN       | `\set ECHO_HIDDEN  on | off | noexec`             | 当使用元命令查询数据库信息（例如\\dg）时，此变量的取值决定了查询的行为：<br />- 设置为on，先显示元命令实际调用的查询语句，然后显示查询结果。等效于使用gsql连接数据库时指定-E参数。<br />- 设置为off，则只显示查询结果。<br />- 设置为noexec，则只显示查询信息，不执行查询操作。 |
+  | ENCODING          | `\set ENCODING   encoding`                        | 当前客户端的字符集编码。                                     |
+  | FETCH_COUNT       | `\set FETCH_COUNT variable`                       | - 如果该变量的值为大于0的整数，假设为n，则执行SELECT语句时每次从结果集中取n行到缓存并显示到屏幕。<br />- 如果不设置此变量，或设置的值小于等于0，则执行SELECT语句时一次性把结果都取到缓存。<br />说明：<br />设置合理的变量值，将减少内存使用量。一般来说，设为100到1000之间的值比较合理。 |
+  | HOST              | `\set HOST hostname`                              | 已连接的数据库主机名称。                                     |
+  | IGNOREEOF         | `\set IGNOREEOF variable`                         | - 若设置此变量为数值，假设为10，则在gsql中输入的前9次EOF字符（通常是Ctrl+D组合键）都会被忽略，在第10次按Ctrl+D才能退出gsql程序。<br />- 若设置此变量为非数值，则缺省为10。<br />- 若删除此变量，则向交互的gsql会话发送一个EOF终止应用。 |
+  | LASTOID           | `\set LASTOID oid`                                | 最后影响的oid值，即为从一条INSERT或lo_import命令返回的值。此变量只保证在下一条SQL语句的结果显示之前有效。 |
+  | ON_ERROR_ROLLBACK | `\set  ON_ERROR_ROLLBACK  on | interactive | off` | - 如果是on，当一个事务块里的语句产生错误的时候，这个错误将被忽略而事务继续。<br />- 如果是interactive，这样的错误只是在交互的会话里忽略。<br />- 如果是off（缺省），事务块里一个语句生成的错误将会回滚整个事务。on_error_rollback-on模式是通过在一个事务块的每个命令前隐含地发出一个SAVEPOINT的方式工作的，在发生错误的时候回滚到该事务块。 |
+  | ON_ERROR_STOP     | `\set ON_ERROR_STOP on | off`                     | - on：命令执行错误时会立即停止，在交互模式下，gsql会立即返回已执行命令的结果。<br />- off（缺省）：命令执行错误时将会跳过错误继续执行。 |
+  | PORT              | `\set PORT port`                                  | 正连接数据库的端口号。                                       |
+  | USER              | `\set USER username`                              | 当前用于连接的数据库用户。                                   |
+  | VERBOSITY         | `\set VERBOSITY   terse | default | verbose`      | 这个选项可以设置为值terse、default、verbose之一以控制错误报告的冗余行。<br />- terse：仅返回严重且主要的错误文本以及文本位置（一般适合于单行错误信息）。<br />- default：返回严重且主要的错误文本及其位置，还包括详细的错误细节、错误提示（可能会跨越多行）。<br />- verbose：返回所有的错误信息。 |
+
+- SQL代换
+
+  像元命令的参数一样，gsql变量的一个关键特性是可以把gsql变量替换成正规的SQL语句。此外，gsql还提供为变量更换新的别名或其他标识符等功能。使用SQL代换方式替换一个变量的值可在变量前加冒号。例如：
+
+  ```sql
+  mogdb=# \set foo 'HR.areaS'
+  mogdb=# select * from :foo;
+   area_id |       area_name
+  ---------+------------------------
+         4 | Middle East and Africa
+         3 | Asia
+         1 | Europe
+         2 | Americas
+  (4 rows)
+  ```
+
+  执行以上命令，将会查询HR.areaS表。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 变量的值是逐字复制的，甚至可以包含不对称的引号或反斜杠命令。所以必须保证输入的内容有意义。
+
+- 提示符
+
+  通过[表3](#tishifu)的三个变量可以设置gsql的提示符，这些变量是由字符和特殊的转义字符所组成。
+
+  **表 3** 提示符变量 <a id="tishifu"> </a>
+
+  | 变量    | 描述                    | 示例                      |
+  | :------ | :--------------------- | :------------------------ |
+  | PROMPT1 | gsql请求一个新命令时使用的正常提示符。<br />PROMPT1的默认值为：<br />`%/%R%#` | 使用变量PROMPT1切换提示符：<br />- 提示符变为[local]：<br />`mogdb=> \set PROMPT1 %M [local:/tmp/gaussdba_mppdb]`<br />- 提示符变为name：<br />`mogdb=> \set PROMPT1 name name`<br />- 提示符变为=：<br />`mogdb=> \set PROMPT1 %R =` |
+  | PROMPT2 | 在一个命令输入期待更多输入时（例如，查询没有用一个分号结束或者引号不完整）显示的提示符。 | 使用变量PROMPT2显示提示符：<br />`mogdb=# \set PROMPT2 TEST`<br />`mogdb=# select * from HR.areaS TEST;`<br />`area_id |  area_name`<br />`---------+-------------------`<br />`1 | Europe`<br />`2 | Americas`<br />`4 | Middle East and Africa`<br />`3 | Asia (4 rows))` |
+  | PROMPT3 | 当执行COPY命令，并期望在终端输入数据时（例如，COPY FROM STDIN），显示提示符。 | 使用变量PROMPT3显示COPY提示符：<br />`mogdb=#  \set PROMPT3 '>>>>'`<br />`mogdb=#  copy HR.areaS from STDIN;`<br />`Enter data to be copied followed by a newline.`<br />`End with a backslash and a period on a line by itself.`<br />`>>>>1 aa`<br />`>>>>2 bb`<br />`>>>>.` |
+
+  提示符变量的值是按实际字符显示的，但是，当设置提示符的命令中出现"%"时，变量的值根据"%"后的字符，替换为已定义的内容，已定义的提示符请参见[表4](#yidingyi)。
+
+  **表 4** 已定义的替换 <a id="yidingyi"> </a>
+
+  | 符号     | 符号说明                                            |
+  | :------- | :------------------------------------------------- |
+  | %M       | 主机的全名（包含域名），若连接是通过Unix域套接字进行的，则全名为[local]，若Unix域套接字不是编译的缺省位置，就是[local:/dir/name]。 |
+  | %m       | 主机名删去第一个点后面的部分。若通过Unix域套接字连接，则为[local]。 |
+  | %&gt;    | 主机正在侦听的端口号。                                       |
+  | %n       | 数据库会话的用户名。                                         |
+  | %/       | 当前数据库名称。                                             |
+  | %~       | 类似 %/，如果数据库是缺省数据库时输出的是波浪线\~。           |
+  | %#       | 如果会话用户是数据库系统管理员，使用#，否则用&gt;。          |
+  | %R       | - 对于PROMPT1通常是“=”，如果是单行模式则是“^”，如果会话与数据库断开（如果\\connect失败可能发生）则是“!”。<br />- 对于PROMPT2该序列被“ -”、单引号、双引号或“$”（取决于gsql是否等待更多的输入：查询没有终止、正在一个 / … / 注释里、正在引号或者美元符扩展里）代替。 |
+  | %x       | 事务状态：<br />- 如果不在事务块里，则是一个空字符串。<br />- 如果在事务块里，则是\*。<br />- 如果在一个失败的事务块里则是“!”。<br />- 如果无法判断事务状态时为“?”（比如没有连接）。 |
+  | %digits  | 指定字节值的字符将被替换到该位置。                           |
+  | %:name   | gsql变量“name”的值。                                         |
+  | %command | command的输出，类似于使用“^”替换。                           |
+  | %[ … %]  | 提示可以包含终端控制字符，这些字符可以改变颜色、背景、提示文本的风格、终端窗口的标题。例如，<br />`mogdb=> \set PROMPT1 '%[%033[1;33;40m%]%n@%/%R%[%033[0m%]%#'`<br />这个句式的结果是在VT100兼容的可显示彩色的终端上的一个宽体（1;）黑底黄字（33;40）。 |
+
+  **环境变量**
+
+  **表 5** 与gsql相关的环境变量
+
+  | 名称                       | 描述                                             |
+  | :------------------------- | :---------------------------------------------- |
+  | COLUMNS                    | 如果\\set columns为0，则由此参数控制wrapped格式的宽度。这个宽度用于决定在自动扩展的模式下，是否要把宽输出模式变成竖线的格式。 |
+  | PAGER                      | 如果查询结果无法在一页显示，它们就会被重定向到这个命令。可以用\\pset命令关闭分页器。典型的是用命令more或less来实现逐页查看。缺省值是平台相关的。<br />说明：<br />less的文本显示，受系统环境变量LC_CTYPE影响。 |
+  | PSQL_EDITOR                | \\e和\\ef命令使用环境变量指定的编辑器。变量是按照列出的先后顺序检查的。在Unix系统上默认的编辑工具是vi。 |
+  | EDITOR                     |                                                              |
+  | VISUAL                     |                                                              |
+  | PSQL_EDITOR_LINENUMBER_ARG | 当\\e和\\ef带上一行数字参数使用时，这个变量指定的命令行参数用于向编辑器传递起始行数。像Emacs或vi这样的编辑器，这只是个加号。如果选项和行号之间需要空白，在变量的值后加一个空格。例如：<br />`PSQL_EDITOR_LINENUMBER_ARG = '+' PSQL_EDITOR_LINENUMBER_ARG='-line '`<br />Unix系统默认的是+。 |
+  | PSQLRC                     | 用户的.gsqlrc文件的交互位置。                                |
+  | SHELL                      | 使用!命令跟shell执行的命令是一样的效果。                     |
+  | TMPDIR                     | 存储临时文件的目录。缺省是/tmp。                             |
+
+### 使用指导
+
+**前提条件**
+
+连接数据库时使用的用户需要具备访问数据库的权限。
+
+**背景信息**
+
+使用gsql命令可以连接远程数据库服务。连接远程数据库服务时，需要在服务器上设置允许远程连接，详细操作请参见《管理指南》中“日常运维 &gt; gsql客户端连接 &gt; [使用gsql远程连接](using-the-gsql-client-for-connection#使用gsql远程连接)”章节。
+
+**操作步骤**
+
+1. 使用gsql连接到MogDB服务器。
+
+   gsql工具使用-d参数指定目标数据库名、-U参数指定数据库用户名、-h参数指定主机名、-p参数指定端口号信息。
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 若未指定数据库名称，则使用初始化时默认生成的数据库名称；若未指定数据库用户名，则默认使用当前操作系统用户作为数据库用户名；当某个值没有前面的参数（-d、-U等）时，若连接的命令中没有指定数据库名（-d）则该参数会被解释成数据库名；如果已经指定数据库名（-d）而没有指定数据库用户名（-U）时，该参数则会被解释成数据库用户名。
+
+   示例1，使用omm用户连接到本机mogdb数据库的15400端口。
+
+   ```bash
+   gsql -d mogdb -p 15400
+   ```
+
+   示例2，使用jack用户连接到远程主机mogdb数据库的15400端口。
+
+   ```bash
+   gsql -h 10.180.123.163 -d mogdb -U jack -p 15400
+   ```
+
+   示例3，参数mogdb和omm不属于任何选项时，分别被解释成了数据库名和用户名。
+
+   ```bash
+   gsql mogdb omm -p 15400
+   ```
+
+   **等效于**
+
+   ```bash
+   gsql -d mogdb -U omm -p 15400
+   ```
+
+   详细的gsql参数请参见[命令参考](#命令参考)。
+
+2. 执行SQL语句。
+
+   以创建数据库human_staff为例。
+
+   ```sql
+   CREATE DATABASE human_staff;
+   ```
+
+   通常，输入的命令行在遇到分号的时候结束。如果输入的命令行没有错误，结果就会输出到屏幕上。
+
+3. 执行gsql元命令。
+
+   以列出MogDB中所有的数据库和描述信息为例。
+
+   ```sql
+   mogdb=#  \l
+                                   List of databases
+         Name      |  Owner   | Encoding  | Collate | Ctype |   Access privileges
+   ----------------+----------+-----------+---------+-------+-----------------------
+    human_resource | omm | SQL_ASCII | C       | C     |
+    postgres       | omm | SQL_ASCII | C       | C     |
+    template0      | omm | SQL_ASCII | C       | C     | =c/omm         +
+                   |          |           |         |       | omm=CTc/omm
+    template1      | omm | SQL_ASCII | C       | C     | =c/omm          +
+                   |          |           |         |       | omm=CTc/omm
+    human_staff    | omm | SQL_ASCII | C       | C     |
+   (5 rows)
+   ```
+
+   更多gsql元命令请参见[元命令参考](#元命令参考)。
+
+**示例**
+
+首先要创建一个表空间EXAMPLE：
+
+```sql
+mogdb=# CREATE TABLESPACE EXAMPLE RELATIVE LOCATION 'tablespace1/tablespace_1';
+CREATE TABLESPACE
+```
+
+表空间创建成功后，创建schema HR：
+
+```sql
+mogdb=# CREATE schema HR;
+CREATE SCHEMA
+```
+
+以把一个查询分成多行输入为例。注意提示符的变化：
+
+```sql
+mogdb=# CREATE TABLE HR.areaS(
+mogdb(# area_ID   NUMBER,
+mogdb(# area_NAME VARCHAR2(25)
+mogdb(# )tablespace EXAMPLE;
+CREATE TABLE
+```
+
+查看表的定义：
+
+```sql
+mogdb=# \d HR.areaS
+               Table "hr.areas"
+  Column   |         Type          | Modifiers
+-----------+-----------------------+-----------
+ area_id   | numeric               |
+ area_name | character varying(25) |
+Tablespace: "example"
+```
+
+向HR.areaS表插入四行数据：
+
+```sql
+mogdb=# INSERT INTO HR.areaS (area_ID, area_NAME) VALUES (1, 'Europe');
+INSERT 0 1
+mogdb=# INSERT INTO HR.areaS (area_ID, area_NAME) VALUES (2, 'Americas');
+INSERT 0 1
+mogdb=# INSERT INTO HR.areaS (area_ID, area_NAME) VALUES (3, 'Asia');
+INSERT 0 1
+mogdb=# INSERT INTO HR.areaS (area_ID, area_NAME) VALUES (4, 'Middle East and Africa');
+INSERT 0 1
+```
+
+切换提示符：
+
+```sql
+mogdb=# \set PROMPT1 '%n@%m %~%R%#'
+omm@[local] mogdb=#
+```
+
+查看表：
+
+```sql
+omm@[local] mogdb=#SELECT * FROM HR.areaS;
+ area_id |       area_name
+---------+------------------------
+       1 | Europe
+       4 | Middle East and Africa
+       2 | Americas
+       3 | Asia
+(4 rows)
+```
+
+可以用\\pset命令以不同的方法显示表：
+
+```sql
+omm@[local] mogdb=#\pset border 2
+Border style is 2.
+omm@[local] mogdb=#SELECT * FROM HR.areaS;
++---------+------------------------+
+| area_id |       area_name        |
++---------+------------------------+
+|       1 | Europe                 |
+|       2 | Americas               |
+|       3 | Asia                   |
+|       4 | Middle East and Africa |
++---------+------------------------+
+(4 rows)
+omm@[local] mogdb=#\pset border 0
+Border style is 0.
+omm@[local] mogdb=#SELECT * FROM HR.areaS;
+area_id       area_name
+------- ----------------------
+      1 Europe
+      2 Americas
+      3 Asia
+      4 Middle East and Africa
+(4 rows)
+omm@[local] mogdb=#\pset border 2
+Border style is 2.
+omm@[local] mogdb=#SELECT * FROM HR.areaS;
++---------+------------------------+
+| area_id |       area_name        |
++---------+------------------------+
+|       1 | Europe                 |
+|       2 | Americas               |
+|       3 | Asia                   |
+|       4 | Middle East and Africa |
++---------+------------------------+
+(4 rows)
+omm@[local] mogdb=#\pset border 0
+Border style is 0.
+omm@[local] mogdb=#SELECT * FROM HR.areaS;
+area_id       area_name
+------- ----------------------
+      1 Europe
+      2 Americas
+      3 Asia
+      4 Middle East and Africa
+(4 rows)
+omm@[local] mogdb=#\pset border 2
+Border style is 2.
+omm@[local] mogdb=#SELECT * FROM HR.areaS;
++---------+------------------------+
+| area_id |       area_name        |
++---------+------------------------+
+|       1 | Europe                 |
+|       2 | Americas               |
+|       3 | Asia                   |
+|       4 | Middle East and Africa |
++---------+------------------------+
+(4 rows)
+omm@[local] mogdb=#\pset border 0
+Border style is 0.
+omm@[local] mogdb=#SELECT * FROM HR.areaS;
+area_id       area_name
+------- ----------------------
+      1 Europe
+      2 Americas
+      3 Asia
+      4 Middle East and Africa
+(4 rows)
+```
+
+使用元命令：
+
+```sql
+omm@[local] mogdb=#\a \t \x
+Output format is unaligned.
+Showing only tuples.
+Expanded display is on.
+omm@[local] mogdb=#SELECT * FROM HR.areaS;
+area_id|2
+area_name|Americas
+
+area_id|1
+area_name|Europe
+
+area_id|4
+area_name|Middle East and Africa
+
+area_id|3
+area_name|Asia
+omm@[local] mogdb=#
+```
+
+### 获取帮助
+
+**操作步骤**
+
+- 连接数据库时，可以使用如下命令获取帮助信息。
+
+  ```sql
+  gsql --help
+  ```
+
+  显示如下帮助信息：
+
+  ```sql
+  ......
+  Usage:
+    gsql [OPTION]... [DBNAME [USERNAME]]
+
+  General options:
+    -c, --command=COMMAND    run only single command (SQL or internal) and exit
+    -d, --dbname=DBNAME      database name to connect to (default: "omm")
+    -f, --file=FILENAME      execute commands from file, then exit
+  ......
+  ```
+
+- 连接到数据库后，可以使用如下命令获取帮助信息。
+
+  ```
+  help
+  ```
+
+  显示如下帮助信息：
+
+  ```bash
+  You are using gsql, the command-line interface to gaussdb.
+  Type:  \copyright for distribution terms
+         \h for help with SQL commands
+         \? for help with gsql commands
+         \g or terminate with semicolon to execute query
+         \q to quit
+  ```
+
+**任务示例**
+
+1. 使用如下命令连接数据库。
+
+   ```sql
+   gsql -d mogdb -p 15400
+   ```
+
+   mogdb为需要连接的数据库名称，15400为数据库主节点的端口号。
+
+   连接成功后，系统显示类似如下信息：
+
+   ```sql
+   gsql ((MogDB x.x.x build 56189e20) compiled at 2022-01-07 18:47:53 commit 0 last mr )
+   Non-SSL connection (SSL connection is recommended when requiring high-security)
+   Type "help" for help.
+
+   mogdb=#
+   ```
+
+2. 查看gsql的帮助信息。具体执行命令请参见[表6 使用gsql联机帮助](#shiyong)。
+
+   **表 6** 使用gsql联机帮助 <a id="shiyong"> </a>
+
+   | 描述                         | 示例                                                         |
+   | :--------------------------- | :----------------------------------------------------------- |
+   | 查看版权信息                 | `\copyright`                                                 |
+   | 查看MogDB支持的SQL语句的帮助 | 查看MogDB支持的SQL语句的帮助<br />例如，查看MogDB支持的所有SQL语句：<br />`mogdb=# \h` <br />`Available help:`<br /> `ABORT`<br />`ALTER APP WORKLOAD GROUP`<br />`… …`<br />例如，查看CREATE DATABASE命令的参数可使用下面的命令：<br />`mogdb=# \help CREATE DATABASE`<br />`Command:     CREATE DATABASE`<br />`Description: create a new database`<br />`Syntax:`<br />`CREATE DATABASE database_name`<br />`[ [ WITH ] {[ OWNER [=] user_name ]|`<br />`[ TEMPLATE [=] template ]|`<br />`[ ENCODING [=] encoding ]|`<br />`[ LC_COLLATE [=] lc_collate ]|`<br />`[ LC_CTYPE [=] lc_ctype ]|`<br />`[ DBCOMPATIBILITY [=] compatibility_type ]|`<br />`[ TABLESPACE [=] tablespace_name ]|`<br />`[ CONNECTION LIMIT [=] connlimit ]}[…] ];` |
+   | 查看gsql命令的帮助           | 例如，查看gsql支持的命令：<br />`mogdb=# \?`<br />`General`<br />`\copyright       show FusionInsight LibrA usage and distribution terms`<br />`\g [FILE] or ;         execute query (and send results to file or |pipe)`<br />`\h(\help) [NAME]              help on syntax of SQL commands, * for all commands`<br />`\parallel [on [num]|off] toggle status of execute (currently off)`<br />`\q                     quit gsql`<br />`… …` |
+
+### 命令参考
+
+详细的gsql参数请参见[表7 常用参数](#changyong)、[表8 输入和输出参数](#shuruheshuchu)、[表9 输出格式参数](#shuchu)和[表10 连接参数](#lianjie)。
+
+**表 7** 常用参数 <a id="changyong"> </a>
+
+| 参数                            | 参数说明                                         | 取值范围                                |
+| :------------------------------ | :--------------------------------------------- | :--------------------------------------|
+| -c, -command=COMMAND            | 声明gsql要执行一条字符串命令然后退出。                       | -                                                |
+| -d, -dbname=DBNAME              | 指定想要连接的数据库名称。                                   | 字符串。                                         |
+| -f, -file=FILENAME              | 使用文件作为命令源而不是交互式输入。gsql将在处理完文件后结束。如果FILENAME是-（连字符），则从标准输入读取。<br />说明：<br />环境场景：一主一备（8U32G）。<br />实测：读取200M数据文件时，耗时约为8分钟21秒；<br />读取500M数据文件时，耗时约为18分41秒。<br />建议：文件读取的时间随文件数据量逐渐增加，如果文件太大，中间异常时需要重新读取，同时会导致系统OS的IO过载，建议文件大小控制在500M左右。 | 绝对路径或相对路径，且满足操作系统路径命名规则。 |
+| -l, -list                       | 列出所有可用的数据库，然后退出。                             | -                                                |
+| -v, -set, -variable=NAME=VALUE  | 设置gsql变量NAME为VALUE。<br />变量的示例和详细说明请参见**变量**。 | -                                                |
+| -X, -no-gsqlrc                  | 不读取启动文件（系统范围的gsqlrc或者用户`~/.gsqlrc`都不读取）。<br />说明：<br />启动文件默认为`~/.gsqlrc`，或通过PSQLRC环境变量指定。 | -                                                |
+| -1 (“one”), -single-transaction | 当gsql使用-f选项执行脚本时，会在脚本的开头和结尾分别加上START TRANSACTION/COMMIT用以把整个脚本当作一个事务执行。这将保证该脚本完全执行成功，或者脚本无效。<br />说明：<br />如果脚本中已经使用了START TRANSACTION、COMMIT、ROLLBACK，则该选项无效。 | -                                                |
+| -?, -help                       | 显示关于gsql命令行参数的帮助信息然后退出。                   | -                                                |
+| -V, -version                    | 打印gsql版本信息然后退出。                                   | -                                                |
+| -C, -enable-client-encryption   | 当使用-C参数连接本地数据库或者远程连接数据库时，可通过该选项打开全密态数据库开关。 | -                                                |
+
+**表 8** 输入和输出参数 <a id="shuruheshuchu"> </a>
+
+| 参数                   | 参数说明                | 取值范围                  |
+| :--------------------- | :-------------------- | :----------------------- |
+| -a, -echo-all          | 在读取行时向标准输出打印所有内容。<br />注意：<br />使用此参数可能会暴露部分SQL语句中的敏感信息，如创建用户语句中的password信息等，请谨慎使用。 | -                                                |
+| -e, -echo-queries      | 把所有发送给服务器的查询同时回显到标准输出。<br />注意：<br />使用此参数可能会暴露部分SQL语句中的敏感信息，如创建用户语句中的password信息等，请谨慎使用。 | -                                                |
+| -E, -echo-hidden       | 回显由\\d和其他反斜杠命令生成的实际查询。                     | -                                                |
+| -k, -with-key=KEY      | 使用gsql对导入的加密文件进行解密。<br />须知：<br />- 对于本身就是shell命令中的关键字符如单引号（'）或双引号（”），Linux shell会检测输入的单引号（'）或双引号（”）是否匹配。如果不匹配，shell认为用户没有输入完毕，会一直等待用户输入，从而不会进入到gsql程序。<br />- 不支持解密导入存储过程和函数。 | -                                                |
+| -L, -log-file=FILENAME | 除了正常的输出源之外，把所有查询输出记录到文件FILENAME中。<br />注意：<br />- 使用此参数可能会暴露部分SQL语句中的敏感信息，如创建用户语句中的password信息等，请谨慎使用。<br />- 此参数只保留查询结果到相应文件中，主要目标是为了查询结果能够更好更准确地被其他调用者（例如自动化运维脚本）解析；而不是保留gsql运行过程中的相关日志信息。 | 绝对路径或相对路径，且满足操作系统路径命名规则。 |
+| -m, -maintenance       | 允许在两阶段事务恢复期间连接MogDB。<br />说明：<br />该选项是一个开发选项，禁止用户使用，只限专业技术人员使用，功能是：使用该选项时，gsql可以连接到备机，用于校验主备机数据的一致性。 | -                                                |
+| -n, -no-libedit        | 关闭命令行编辑。                                             | -                                                |
+| -o, -output=FILENAME   | 将所有查询输出重定向到文件FILENAME。                         | 绝对路径或相对路径，且满足操作系统路径命名规则。 |
+| -q, -quiet             | 安静模式，执行时不会打印出额外信息。                         | 缺省时gsql将打印许多其他输出信息。               |
+| -s, -single-step       | 单步模式运行。意味着每个查询在发往服务器之前都要提示用户，用这个选项也可以取消执行。此选项主要用于调试脚本。<br />注意：<br />使用此参数可能会暴露部分SQL语句中的敏感信息，如创建用户语句中的password信息等，请谨慎使用。 | -                                                |
+| -S, -single-line       | 单行运行模式，这时每个命令都将由换行符结束，像分号那样。     | -                                                |
+
+**表 9** 输出格式参数 <a id="shuchu"> </a>
+
+| 参数                         | 参数说明                                       | 取值范围             |
+| :--------------------------- | :-------------------------------------------- | :------------------- |
+| -A, -no-align                | 切换为非对齐输出模式。                                       | 缺省为对齐输出模式。 |
+| -F, -field-separator=STRING  | 设置域分隔符（默认为`|`）。                                 | -                    |
+| -H, -html                    | 打开HTML格式输出。                                           | -                    |
+| -P, -pset=VAR[=ARG]          | 在命令行上以\\pset的风格设置打印选项。<br />说明：<br />这里必须用等号而不是空格分隔名称和值。例如，把输出格式设置为LaTeX，可以键入-P format=latex | -                    |
+| -R, -record-separator=STRING | 设置记录分隔符。                                             | -                    |
+| -r                           | 开启在客户端操作中可以进行编辑的模式。                       | 缺省为关闭。         |
+| -t, -tuples-only             | 只打印行。                                                   | -                    |
+| -T, -table-attr=TEXT         | 允许声明放在HTML table标签里的选项。<br />使用时请搭配参数“-H,-html”，指定为HTML格式输出。 | -                    |
+| -x, -expanded                | 打开扩展表格式模式。                                         | -                    |
+| -z, -field-separator-zero    | 设置非对齐输出模式的域分隔符为空。<br />使用时请搭配参数“-A, -no-align”，指定为非对齐输出模式。 | -                    |
+| -0, -record-separator-zero   | 设置非对齐输出模式的记录分隔符为空。<br />使用时请搭配参数“-A, -no-align”，指定为非对齐输出模式。 | -                    |
+
+**表 10** 连接参数 <a id="lianjie"> </a>
+
+| 参数                   | 参数说明                                      | 取值范围                                   |
+| :--------------------- | :-------------------------------------------- | :--------------------------------------- |
+| -h, -host=HOSTNAME     | 指定正在运行服务器的主机名或者Unix域套接字的路径。           | 如果省略主机名，gsql将通过Unix域套接字与本地主机的服务器相联，或者在没有Unix域套接字的机器上，通过TCP/IP与localhost连接。 |
+| -p, -port=PORT         | 指定数据库服务器的端口号。<br />可以通过port参数修改默认端口号。 | 默认为5432。                                                 |a
+| -U, -username=USERNAME | 指定连接数据库的用户。<br />说明：<br />- 通过该参数指定用户连接数据库时，需要同时提供用户密码用以身份验证。您可以通过交换方式输入密码，或者通过-W参数指定密码。<br />- 用户名中包含有字符 `$`，需要在字符`$`前增加转义字符才可成功连接数据库。 | 字符串。默认使用与当前操作系统用户同名的用户。               |
+| -W, -password=PASSWORD | 当使用-U参数连接远端数据库时，可通过该选项指定密码。<br />说明：<br />数据库主节点所在服务器后连接本地数据库主节点实例时，默认使用trust连接，会忽略此参数。<br />用户密码中包含特殊字符\\和\`时，需要增加转义字符才可成功连接数据库。<br />如果用户未输入该参数，但是数据库连接需要用户密码，这时将出现交互式输入，请用户输入当前连接的密码。该密码最长长度为999字节，受限于GUC参数password_max_length的最大值。 | 符合密码复杂度要求。                                         |
+
+### 元命令参考
+
+介绍使用MogDB数据库命令行交互工具登录数据库后，gsql所提供的元命令。所谓元命令就是在gsql里输入的任何以不带引号的反斜杠开头的命令。
+
+**注意事项**
+
+- 一个gsql元命令的格式是反斜杠后面紧跟一个动词，然后是任意参数。参数命令动词和其他参数以任意个空白字符间隔。
+- 要在参数里面包含空白，必须用单引号把它引起来。要在这样的参数里包含单引号，可以在前面加一个反斜杠。任何包含在单引号里的内容都会被进一步进行类似C语言的替换：\\n（新行）、\\t（制表符）、\\b（退格）、\\r（回车）、\\f（换页）、\\digits（八进制表示的字符）、\\xdigits（十六进制表示的字符）。
+- ”“包围的内容被当做一个命令行传入shell。该命令的输出（删除了结尾的新行）被当做参数值。
+- 如果不带引号的参数以冒号（:）开头，它会被当做一个gsql变量，并且该变量的值最终会成为真正的参数值。
+- 有些命令以一个SQL标识的名称（比如一个表）为参数。这些参数遵循SQL语法关于双引号的规则：不带双引号的标识强制转换成小写，而双引号保护字母不进行大小写转换，并且允许在标识符中使用空白。在双引号中，成对的双引号在结果名称中分析成一个双引号。比如，FOO”BAR”BAZ解析成fooBARbaz；而”A weird”“name”解析成“A weird”name。
+- 对参数的分析在遇到另一个不带引号的反斜杠时停止。这里会认为是一个新的元命令的开始。特殊的双反斜杠序列（\\）标识参数的结尾并将继续分析后面的SQL语句（如果存在）。这样SQL和gsql命令可以自由的在一行里面混合。但是在任何情况下，一条元命令的参数不能延续超过行尾。
+
+**元命令**
+
+元命令的详细说明请参见下表。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 以下命令中所提到的FILE代表文件路径。此路径可以是绝对路径（如/home/gauss/file.txt），也可以是相对路径（file.txt，file.txt会默认在用户执行gsql命令所在的路径下创建）。
+
+**表 11** 一般的元命令
+
+| 参数               | 参数说明                 | 取值范围             |
+| :----------------- | :------------------------ | :--------------------- |
+| \\copyright                | 显示MogDB的版本和版权信息。                                  | -                                  |
+| \\g [FILE] or ;            | 执行查询（并将结果发送到文件或管道）。                       | -                                   |
+| \\h(\\help) [NAME]          | 给出指定SQL语句的语法帮助。                                  | 如果没有给出NAME，gsql将列出可获得帮助的所有命令。如果NAME是一个星号（*），则显示所有SQL语句的语法帮助。 |
+| \\parallel [on [num]\|off] | 控制并发执行开关。<br /> - on：打开控制并发执行开关，且最大并发数为num。<br />- off：关闭控制并发执行开关。<br />说明：<br />- 不支持事务中开启并发执行以及并发中开启事务。<br />- 不支持\\d这类元命令的并发。<br />- 并发select返回结果混乱问题，此为客户可接受，core、进程停止响应不可接受。<br />- 不推荐在并发中使用set语句，否则导致结果与预期不一致。<br />- 不支持创建临时表！如需使用临时表，需要在开启parallel之前创建好，并在parallel内部使用。parallel内部不允许创建临时表。<br />- \\parallel执行时最多会启动num个独立的gsql进程连接服务器。<br />- \\parallel中所有作业的持续时间不能超过session_timeout，否则可能会导致并发执行过程中断连。 | num的默认值：1024。<br />须知：<br />- 服务器能接受的最大连接数受max_connection及当前已有连接数限制。<br />- 设置num时请考虑服务器当前可接受的实际连接数合理指定。 |
+| \\q                        | 退出gsql程序。在一个脚本文件里，只在脚本终止的时候执行。     | -                                                            |
+
+**表 12** 查询缓存区元命令
+
+| 参数                  | 参数说明                                                     |
+| :-------------------- | :----------------------------------------------------------- |
+| \\e [FILE] [LINE]      | 使用外部编辑器编辑查询缓冲区（或者文件）。                   |
+| \\ef [FUNCNAME [LINE]] | 使用外部编辑器编辑函数定义。如果指定了LINE（即行号），则光标会指到函数体的指定行。 |
+| \\p                    | 打印当前查询缓冲区到标准输出。                               |
+| \\r                    | 重置（或清空）查询缓冲区。                                   |
+| \\w FILE               | 将当前查询缓冲区输出到文件。                                 |
+
+**表 13** 输入/输出元命令
+
+| 参数                                                         | 参数说明                                                     |
+| :----------------------------------------------------------- | :----------------------------------------------------------- |
+| \\copy { table [ ( column_list ) ] \| ( query ) } { from \| to } { filename \| stdin \| stdout \| pstdin \| pstdout } [ with ] [ binary ] [ oids ] [ delimiter [ as ] 'character' ] [ null [ as ] 'string' ] [ csv [ header ] [ quote [ as ] 'character' ] [ escape [ as ] 'character' ] [ force quote column_list \| * ] [ force not null column_list ] ] [parallel integer] | 在任何psql客户端登录数据库成功后可以执行导入导出数据， 这是一个运行SQL COPY命令的操作，但不是读取或写入指定文件的服务器，而是读取或写入文件，并在服务器和本地文件系统之间路由数据。 这意味着文件的可访问性和权限是本地用户的权限，而不是服务器的权限，并且不需要数据库初始化用户权限。<br />说明：<br />\\COPY只适合小批量，格式良好的数据导入，不会对非法字符进行预处理，也无容错能力。导入数据应优先选择COPY。<br />\\COPY 可以指定数据导入时的客户端数量，从而实现数据文件的并行导入，目前并发数范围为[1, 8]。<br />\\COPY并行导入目前存在以下约束：临时表的并行导入不支持、在事务内的并行导入不支持、对二进制文件的并行导入不支持、数据导入支持AES128加密时不支持。在这些情况下，即使指定了parallel参数，仍然会走非并行流程。 |
+| \\echo [STRING]                                               | 把字符串写到标准输出。                                       |
+| \\i FILE                                                      | 从文件FILE中读取内容，并将其当作输入，执行查询。             |
+| \\i+ FILE KEY                                                 | 执行加密文件中的命令。                                       |
+| \\ir FILE                                                     | 和\\i类似，只是相对于存放当前脚本的路径。                     |
+| \\ir+ FILE KEY                                                | 和\\i+类似，只是相对于存放当前脚本的路径。                    |
+| \\o [FILE]                                                    | 把所有的查询结果发送到文件里。                               |
+| \\qecho [STRING]                                              | 把字符串写到查询结果输出流里。                               |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** [表14 显示信息元命令](#xianshi)中的选项S表示显示系统对象，PATTERN表示显示对象附加的描述信息。用来指定要被显示的对象名称。
+
+**表 14** 显示信息元命令 <a id="xianshi"> </a>
+
+| 参数                           | 参数说明                   | 取值范围                     | 示例                            |
+| :---------------------------- | :------------------------| :--------------------------- | :---------------------------- |
+| \\d[S+]                                                       | 列出当前search_path中模式下所有的表、视图和序列。当search_path中不同模式存在同名对象时，只显示search_path中位置靠前模式下的同名对象。 | -                                                            | 列出当前search_path中模式下所有的表、视图和序列。<br />`mogdb=# \d` |
+| \\d[S+] NAME                                                  | 列出指定表、视图和索引的结构。                               | -                                                            | 假设存在表a，列出指定表a的结构。<br />`mogdb=#  \dtable+ a`  |
+| \\d+ [PATTERN]                                                | 列出所有表、视图和索引。                                     | 如果声明了PATTERN，只显示名称匹配PATTERN的表、视图和索引。   | 列出所有名称以f开头的表、视图和索引。`mogdb=# \d+ f`         |
+| \\da[S] [PATTERN]                                             | 列出所有可用的聚集函数以及它们操作的数据类型和返回值类型。   | 如果声明了PATTERN，只显示名称匹配PATTERN的聚集函数。         | 列出所有名称以f开头可用的聚集函数以及它们操作的数据类型和返回值类型。<br />`mogdb=# \da f` |
+| \\db[+] [PATTERN]                                             | 列出所有可用的表空间。                                       | 如果声明了PATTERN，只显示名称匹配PATTERN的表空间。           | 列出所有名称以p开头的可用表空间。<br />`mogdb=# \db p*`      |
+| \\dc[S+] [PATTERN]                                            | 列出所有字符集之间的可用转换。                               | 如果声明了PATTERN，只显示名称匹配PATTERN的转换。             | 列出所有字符集之间的可用转换。<br />`mogdb=# \dc`           |
+| \\dC[+] [PATTERN]                                             | 列出所有类型转换。                                           | 如果声明了PATTERN，只显示名称匹配PATTERN的转换。             | 列出所有名称以c开头的类型转换。<br />`mogdb=# \dC c`         |
+| \\dd[S] [PATTERN]                                             | 显示所有匹配PATTERN的描述。                                  | 如果没有给出参数，则显示所有可视对象。“对象”包括：聚集、函数、操作符、类型、关系（表、视图、索引、序列、大对象）、规则。 | 列出所有可视对象。<br />`mogdb=# \dd`                        |
+| \\ddp [PATTERN]                                               | 显示所有默认的使用权限。                                     | 如果指定了PATTERN，只显示名称匹配PATTERN的使用权限。         | 列出所有默认的使用权限。<br />`mogdb=# \ddp`                 |
+| \\dD[S+] [PATTERN]                                            | 列出所有可用域。                                             | 如果声明了PATTERN，只显示名称匹配PATTERN的域。               | 列出所有可用域。<br />`mogdb=# \dD`                          |
+| \\ded[+] [PATTERN]                                            | 列出所有的Data Source对象。                                  | 如果声明了PATTERN，只显示名称匹配PATTERN的对象。             | 列出所有的Data Source对象。<br />`mogdb=# \ded`              |
+| \\det[+] [PATTERN]                                            | 列出所有的外部表。                                           | 如果声明了PATTERN，只显示名称匹配PATTERN的表。               | 列出所有的外部表。<br />`mogdb=# \det`                       |
+| \\des[+] [PATTERN]                                            | 列出所有的外部服务器。                                       | 如果声明了PATTERN，只显示名称匹配PATTERN的服务器。           | 列出所有的外部服务器。<br />`mogdb=# \des`                   |
+| \\deu[+] [PATTERN]                                            | 列出用户映射信息。                                           | 如果声明了PATTERN，只显示名称匹配PATTERN的信息。             | 列出用户映射信息。<br />`mogdb=# \deu`                       |
+| \\dew[+] [PATTERN]                                            | 列出封装的外部数据。                                         | 如果声明了PATTERN，只显示名称匹配PATTERN的数据。             | 列出封装的外部数据。<br />`mogdb=# \dew`                     |
+| \\df[antw][S+] [PATTERN]                                     | 列出所有可用函数以及它们的参数和返回的数据类型。a代表聚集函数，n代表普通函数，t代表触发器，w代表窗口函数。 | 如果声明了PATTERN，只显示名称匹配PATTERN的函数。             | 列出所有可用函数以及它们的参数和返回的数据类型。<br />`mogdb=# \df` |
+| \\dF[+] [PATTERN]                                             | 列出所有的文本搜索配置信息。                                 | 如果声明了PATTERN，只显示名称匹配PATTERN的配置信息。         | 列出所有的文本搜索配置信息。<br />`mogdb=# \dF+`             |
+| \\dFd[+] [PATTERN]                                            | 列出所有的文本搜索字典。                                     | 如果声明了PATTERN，只显示名称匹配PATTERN的字典。             | 列出所有的文本搜索字典。<br />`mogdb=# \dFd`                 |
+| \\dFp[+] [PATTERN]                                            | 列出所有的文本搜索分析器。                                   | 如果声明了PATTERN，只显示名称匹配PATTERN的分析器。           | 列出所有的文本搜索分析器。<br />`mogdb=# \dFp`               |
+| \\dFt[+] [PATTERN]                                            | 列出所有的文本搜索模板。                                     | 如果声明了PATTERN，只显示名称匹配PATTERN的模板。             | 列出所有的文本搜索模板。<br />`mogdb=# \dFt`                 |
+| \\dg[+] [PATTERN]                                             | 列出所有数据库角色。<br />说明：<br />因为用户和群组的概念被统一为角色，所以这个命令等价于\\du。为了和以前兼容，所以保留两个命令。 | 如果指定了PATTERN，只显示名称匹配PATTERN的角色。             | 列出名称为‘j_e’所有数据库角色。<br />`mogdb=# \dg j?e`       |
+| \\dl                                                          | \\lo_list的别名，显示一个大对象的列表。                       | -                                                            | 列出所有的大对象。<br />`mogdb=# \dl`                        |
+| \\dL[S+] [PATTERN]                                            | 列出可用的程序语言。                                         | 如果指定了PATTERN，只列出名称匹配PATTERN的语言。             | 列出可用的程序语言。<br />`mogdb=# \dL`                      |
+| \\dn[S+] [PATTERN]                                            | 列出所有的模式（名称空间）。                                 | 如果声明了PATTERN，只列出名称匹配PATTERN的模式名。缺省时，只列出用户创建的模式。 | 列出所有名称以d开头的模式以及相关信息。<br />`mogdb=#  \dn+ d*` |
+| \\do[S] [PATTERN]                                             | 列出所有可用的操作符以及它们的操作数和返回的数据类型。       | 如果声明了PATTERN，只列出名称匹配PATTERN的操作符。缺省时，只列出用户创建的操作符。 | 列出所有可用的操作符以及它们的操作数和返回的数据类型。<br />`mogdb=# \do` |
+| \\dO[S+] [PATTERN]                                            | 列出排序规则。                                               | 如果声明了PATTERN，只列出名称匹配PATTERN的规则。缺省时，只列出用户创建的规则。 | 列出排序规则。<br />`mogdb=# \dO`                            |
+| \\dp [PATTERN]                                                | 列出一列可用的表、视图以及相关的权限信息。<br />\\dp显示结果如下：<br />`rolename=xxxx/yyyy  -赋予一个角色的权限`<br />`=xxxx/yyyy  -赋予public的权限`<br />xxxx表示赋予的权限，yyyy表示授予这个权限的角色。权限的参数说明请参见**表15 权限的参数说明**。 | 如果指定了PATTERN，只列出名称匹配PATTERN的表、视图。         | 列出一列可用的表、视图以及相关的权限信息。<br />`mogdb=# \dp` |
+| \\drds [PATTERN1 [PATTERN2]]                                  | 列出所有修改过的配置参数。这些设置可以是针对角色的、针对数据库的或者同时针对两者的。PATTERN1和PATTERN2表示要列出的角色PATTERN和数据库PATTERN。 | 如果声明了PATTERN，只列出名称匹配PATTERN的规则。缺省或指定*时，则会列出所有设置。 | 列出mogdb数据库所有修改过的配置参数。<br />`mogdb=# \drds * mogdb` |
+| \\dT[S+] [PATTERN]                                            | 列出所有的数据类型。                                         | 如果指定了PATTERN，只列出名称匹配PATTERN的类型。             | 列出所有的数据类型。<br />`mogdb=# \dT`                      |
+| \\du[+] [PATTERN]                                             | 列出所有数据库角色。<br />说明：<br />因为用户和群组的概念被统一为角色，所以这个命令等价于\\dg。为了和以前兼容，所以保留两个命令。 | 如果指定了PATTERN，则只列出名称匹配PATTERN的角色。           | 列出所有数据库角色。<br />`mogdb=# \du`                      |
+| \\dE[S+] [PATTERN]\\di[S+] [PATTERN]\\ds[S+] [PATTERN]\\dt[S+] [PATTERN]\\dv[S+] [PATTERN] | 这一组命令，字母E、i、s、t和v分别代表着外部表、索引、序列、表和视图。可以以任意顺序指定其中一个或者它们的组合来列出这些对象。例如：\\dit列出所有的索引和表。在命令名称后面追加+，则每一个对象的物理尺寸以及相关的描述也会被列出。 | 如果指定了PATTERN，只列出名称匹配该PATTERN的对象。默认情况下只会显示用户创建的对象。通过PATTERN或者S修饰符可以把系统对象包括在内。 | 列出所有的索引和视图。<br />`mogdb=# \div`                   |
+| \\dx[+] [PATTERN]                                             | 列出安装数据库的扩展信息。                                   | 如果指定了PATTERN，则只列出名称匹配PATTERN的扩展信息。       | 列出安装数据库的扩展信息。<br />`mogdb=# \dx`                |
+| \\l[+]                                                        | 列出服务器上所有数据库的名称、所有者、字符集编码以及使用权限。 | -                                                            | 列出服务器上所有数据库的名称、所有者、字符集编码以及使用权限。<br />`mogdb=#  \l` |
+| \\sf[+] FUNCNAME                                              | 显示函数的定义。<br />说明：<br />对于带圆括号的函数名，需要在函数名两端添加双引号，并且在双引号后面加上参数类型列表。参数类型列表两端添加圆括号。 | -                                                            | 假设存在函数function_a和函数名带圆括号的函数func()name，列出函数的定义。<br />`mogdb=# \sf function_a`<br />`mogdb=# \sf “func()name”(argtype1, argtype2)` |
+| \\z [PATTERN]                                                 | 列出数据库中所有表、视图和序列以及它们相关的访问特权。       | 如果给出任何pattern ，则被当成一个正则表达式，只显示匹配的表、视图、序列。 | 列出数据库中所有表、视图和序列以及它们相关的访问特权。<br />`mogdb=# \z` |
+
+**表 15** 权限的参数说明
+
+| 参数 | 参数说明                                                     |
+| :--- | :----------------------------------------------------------- |
+| r    | SELECT：允许对指定的表、视图读取数据。                       |
+| w    | UPDATE：允许对指定表更新字段。                               |
+| a    | INSERT：允许对指定表插入数据。                               |
+| d    | DELETE：允许删除指定表中的数据。                             |
+| D    | TRUNCATE：允许清理指定表中的数据。                           |
+| x    | REFERENCES：允许创建外键约束。由于当前不支持外键，所以该参数暂不生效。 |
+| t    | TRIGGER：允许在指定表上创建触发器。                          |
+| X    | EXECUTE：允许使用指定的函数以及利用这些函数实现的操作符。    |
+| U    | USAGE：<br />- 对于过程语言，允许用户在创建函数时，指定过程语言。<br />- 对于模式，允许访问包含在指定模式中的对象。<br />- 对于序列，允许使用nextval函数。 |
+| C    | CREATE：<br />- 对于数据库，允许在该数据库里创建新的模式。<br />- 对于模式，允许在该模式中创建新的对象。<br />- 对于表空间，允许在其中创建表以及允许创建数据库和模式的时候把该表空间指定为其缺省表空间。 |
+| c    | CONNECT：允许用户连接到指定的数据库。                        |
+| T    | TEMPORARY：允许创建临时表。                                  |
+| A    | ALTER：允许用户修改指定对象的属性。                          |
+| P    | DROP：允许用户删除指定的对象。                               |
+| m    | COMMENT：允许用户定义或修改指定对象的注释。                  |
+| i    | INDEX：允许用户在指定表上创建索引。                          |
+| v    | VACUUM：允许用户对指定的表执行ANALYZE和VACUUM操作。          |
+| *    | 给前面权限的授权选项。                                       |
+
+**表 16** 格式化元命令
+
+| 参数               | 参数说明                 |
+| :----------------- | :-------------------------- |
+| \\a                 | 对齐模式和非对齐模式之间的切换。                             |
+| \\C [STRING]        | 把正在打印的表的标题设置为一个查询的结果或者取消这样的设置。 |
+| \\f [STRING]        | 对于不对齐的查询输出，显示或者设置域分隔符。                 |
+| \\H                 | - 若当前模式为文本格式，则切换为HTML输出格式。<br />- 若当前模式为HTML格式，则切换回文本格式。 |
+| \\pset NAME [VALUE] | 设置影响查询结果表输出的选项。NAME的取值见[表17 可调节的打印选项](#ketiaojie)。 |
+| \\t [on\|off]       | 切换输出的字段名的信息和行计数脚注。                         |
+| \\T [STRING]        | 指定在使用HTML输出格式时放在table标签里的属性。如果参数为空，不设置。 |
+| \\x [on\|off\|auto] | 切换扩展行格式。                                             |
+
+**表 17** 可调节的打印选项 <a id="ketiaojie"> </a>
+
+| 选项                  | 选项说明                                  | 取值范围                                |
+| :-------------------- | :----------------------------------------- | :-----------------------------------|
+| border                | value必须是一个数字。通常这个数字越大，表的边界就越宽线就越多，但是这个取决于特定的格式。 | - 在HTML格式下，取值范围为大于0的整数。<br />- 在其他格式下，取值范围: <br />  - 0：无边框<br />  - 1：内部分隔线<br />  - 2：台架 |
+| expanded (或x)        | 在正常和扩展格式之间切换。                                   | - 当打开扩展格式时，查询结果用两列显示，字段名称在左、数据在右。这个模式在数据无法放进通常的”水平”模式的屏幕时很有用。<br />- 在正常格式下，当查询输出的格式比屏幕宽时，用扩展格式。正常格式只对aligned和wrapped格式有用。 |
+| fieldsep              | 声明域分隔符来实现非对齐输出。这样就可以创建其他程序希望的制表符或逗号分隔的输出。要设置制表符域分隔符，键入\\pset fieldsep '\\t'。缺省域分隔符是 '\|' (竖条符)。 | -                                                            |
+| fieldsep_zero         | 声明域分隔符来实现非对齐输出到零字节。                       | -                                                            |
+| footer                | 用来切换脚注。                                               | -                                                            |
+| format                | 设置输出格式。允许使用唯一缩写（这意味着一个字母就够了）。   | 取值范围: <br />- unaligned：写一行的所有列在一条直线上中，当前活动字段分隔符分隔。<br />- aligned：此格式是标准的，可读性最好的文本输出。<br />- wrapped：类似aligned，但是包装跨行的宽数据值，使其适应目标字段的宽度输出。<br />- html：把表输出为可用于文档里的对应标记语言。输出不是完整的文档。<br />- latex：把表输出为可用于文档里的对应标记语言。输出不是完整的文档。<br />- troff-ms：把表输出为可用于文档里的对应标记语言。输出不是完整的文档。 |
+| null                  | 打印一个字符串，用来代替一个null值。                         | 缺省是什么都不打印，这样很容易和空字符串混淆。               |
+| numericlocale         | 切换分隔小数点左边的数值的区域相关的分组符号。               | - on：显示指定的分隔符。<br />- off：不显示分隔符。<br />忽略此参数，显示默认的分隔符。 |
+| pager                 | 控制查询和gsql帮助输出的分页器。如果设置了环境变量PAGER，输出将被指向到指定程序，否则使用系统缺省。 | - on：当输出到终端且不适合屏幕显示时，使用分页器。<br />- off：不使用分页器。<br />- always：当输出到终端无论是否符合屏幕显示时，都使用分页器。 |
+| recordsep             | 声明在非对齐输出格式时的记录分隔符。                         | -                                                            |
+| recordsep_zero        | 声明在非对齐输出到零字节时的记录分隔符。                     | -                                                            |
+| tableattr（或T）      | 声明放在html输出格式中HTML table标签的属性（例如：cellpadding或bgcolor）。注意：这里可能不需要声明border，因为已经在\\pset border里用过了。如果没有给出value，则不设置表的属性。 | -                                                            |
+| title                 | 为随后打印的表设置标题。这个可以用于给输出一个描述性标签。如果没有给出value，不设置标题。 | -                                                            |
+| tuples_only （或者t） | 在完全显示和只显示实际的表数据之间切换。完全显示将输出像列头、标题、各种脚注等信息。在tuples_only模式下，只显示实际的表数据。 | -                                                            |
+
+**表 18** 连接元命令
+
+| 参数                                           | 参数说明                                   | 取值范围                         |
+| :--------------------------------------------- | :------------------------------------------- | :------------------------------- |
+| \\c[onnect] [DBNAME\|- USER\|- HOST\|- PORT\|-] | 连接到一个新的数据库（当前数据库为mogdb）。当数据库名称长度超过63个字节时，默认前63个字节有效，连接到前63个字节对应的数据库，但是gsql的命令提示符中显示的数据库对象名仍为截断前的名称。<br />说明：<br />重新建立连接时，如果切换数据库登录用户，将可能会出现交互式输入，要求输入新用户的连接密码。该密码最长长度为999字节，受限于GUC参数password_max_length的最大值。 | -                                |
+| \\encoding [ENCODING]                           | 设置客户端字符编码格式。                                     | 不带参数时，显示当前的编码格式。 |
+| \\conninfo                                      | 输出当前连接的数据库的信息。                                 | -                                |
+
+**表 19** 操作系统元命令
+
+| 参数           | 参数说明            |取值范围                  |
+| :------------- | :-----------------| :------------------------ |
+| \\cd [DIR]            | 切换当前的工作目录。                                         | 绝对路径或相对路径，且满足操作系统路径命名规则。 |
+| \\setenv NAME [VALUE] | 设置环境变量NAME为VALUE，如果没有给出VALUE值，则不设置环境变量。 | -                                                |
+| \\timing [on\|off]    | 以毫秒为单位显示每条SQL语句的执行时间。                      | - on表示打开显示。<br />- off表示关闭显示。      |
+| ! [COMMAND]          | 返回到一个单独的Unix shell或者执行Unix命令COMMAND。          | -                                                |
+
+**表 20** 变量元命令
+
+| 参数                | 参数说明                                 |
+| :------------------ | :--------------------------------------- |
+| \\prompt [TEXT] NAME | 提示用户用文本格式来指定变量名称。                           |
+| \\set [NAME [VALUE]] | 设置内部变量NAME为VALUE或者如果给出了多于一个值，设置为所有这些值的连接结果。如果没有给出第二个参数，只设变量不设值。<br />有一些常用变量被gsql特殊对待，它们是一些选项设置，通常所有特殊对待的变量都是由大写字母组成(可能还有数字和下划线)。 [表21](#set)是一个所有特殊对待的变量列表。 |
+| \\unset NAME         | 不设置（或删除）gsql变量名。                                 |
+
+**表 21** \\set常用命令 <a id="set"> </a>
+
+| 名称                     | 命令说明                                | 取值范围                                 |
+| :----------------------- | :--------------------------------------- | :--------------------------------------|
+| \\set VERBOSITY value     | 这个选项可以设置为值default， verbose，terse之一以控制错误报告的冗余行。 | value取值范围: default， verbose，terse          |
+| \\set ON_ERROR_STOP value | 如果设置了这个变量，脚本处理将马上停止。如果该脚本是从另外一个脚本调用的，那个脚本也会按同样的方式停止。如果最外层的脚本不是从一次交互的gsql会话中调用的而是用-f选项调用的，gsql将返回错误代码3，以示这个情况与致命错误条件的区别（错误代码为1）。 | value取值范围为：on/off，true/false，yes/no，1/0 |
+| \\set RETRY [retry_times] | 用于控制是否开启语句出错场景下的重试功能，参数retry_times用来指定最大重试次数，缺省值为5，取值范围为5-10。当重试功能已经开启时，再次执行\\set RETRY可以关闭该功能。<br />使用配置文件retry_errcodes.conf列举需要重试的错误码列表，该文件和gsql可执行程序位于同一级目录下。该配置文件为系统配置，非用户定义，不允许用户直接修改。<br />当前支持以下出错场景的重试：<br />- YY001：TCP通信错误，Connection reset by peer<br />- YY002：TCP通信错误，Connection reset by peer<br />- YY003：锁超时，Lock wait timeout…/wait transaction xxx sync time exceed xxx<br />- YY004：TCP通信错误，Connection timed out<br />- YY005：SET命令发送失败，ERROR SET query<br />- YY006：内存申请失败，memory is temporarily unavailable<br />- YY007：通信库错误，Memory allocate error<br />- YY008：通信库错误，No data in buffer<br />- YY009：通信库错误，Close because release memory<br />- YY010：通信库错误，TCP disconnect<br />- YY011：通信库错误，SCTP disconnect<br />- YY012：通信库错误，Stream closed by remote<br />- YY013：通信库错误，Wait poll unknown error<br />- YY014,YY015,53200,08006,08000,57P01,XX003,XX009等<br />同时，出错时gsql会查询数据库节点的连接状态，当状态异常时会sleep 1分钟再进行重试，能够覆盖大部分主备切换场景下的出错重试。<br />说明：<br />1. 不支持事务块中的语句错误重试；<br />2. 不支持通过ODBC、JDBC接口查询的出错重试；<br />3. 含有unlogged表的sql语句，不支持节点故障后的出错重试；<br />4. gsql客户端本身出现的错误，不在重跑考虑范围之内； | retry_times取值范围为：5-10                      |
+
+**表 22** 大对象元命令
+
+| 参数     | 参数说明                                                     |
+| :------- | :----------------------------------------------------------- |
+| \\lo_list | 显示一个目前存储在该数据库里的所有MogDB大对象和提供给他们的注释。 |
+
+**PATTERN**
+
+很多\\d命令都可以用一个PATTERN参数来指定要被显示的对象名称。在最简单的情况下，PATTERN正好就是该对象的准确名称。在PATTERN中的字符通常会被变成小写形式（就像在SQL名称中那样），例如\\dt FOO将会显示名为foo的表。就像在SQL名称中那样，把PATTERN放在双引号中可以阻止它被转换成小写形式。如果需要在一个PATTERN中包括一个真正的双引号字符，则需要把它写成两个相邻的双引号，这同样是符合SQL引用标识符的规则。例如，\\dt “FOO”“BAR”将显示名为FOO”BAR（不是foo”bar）的表。和普通的SQL名称规则不同，不能只在PATTERN的一部分周围放上双引号，例如\\dt FOO”FOO”BAR将会显示名为fooFOObar的表。
+
+不使用PATTERN参数时，\\d命令会显示当前schema搜索路径中可见的全部对象.这等价于用\*作为PATTERN。所谓对象可见是指可以直接用名称引用该对象，而不需要用schema来进行限定。要查看数据库中所有的对象而不管它们的可见性，可以把*.*用作PATTERN。
+
+如果放在一个PATTERN中，\*将匹配任意字符序列（包括空序列），而?会匹配任意的单个字符（这种记号方法就像 Unix shell 的文件名PATTERN一样）。例如，\\dt int*会显示名称以int开始的表。但是如果被放在双引号内，*和?就会失去这些特殊含义而变成普通的字符。
+
+包含一个点号（.）的PATTERN被解释为一个schema名称模式后面跟上一个对象名称模式。例如，\\dt foo*.*bar会显示名称以foo开始的schema中所有名称包括bar的表。如果没有出现点号，那么模式将只匹配当前schema搜索路径中可见的对象。同样，双引号内的点号会失去其特殊含义并且变成普通的字符。
+
+高级用户可以使用字符类等正则表达式记法，如[0-9]可以匹配任意数字。所有的正则表达式特殊字符都按照POSIX正则表达式所说的工作。以下字符除外：
+
+- .会按照上面所说的作为一种分隔符。
+- \*会被翻译成正则表达式记号.*。
+- ?会被翻译成.。
+- $则按字面意思匹配。
+
+根据需要，可以通过书写?, (`R+|`), (`R|`)和`R?`来分别模拟PATTERN字符. `R*`和`R?`。`$`不需要作为一个正则表达式字符，因为PATTERN必须匹配整个名称，而不是像正则表达式的常规用法那样解释（换句话说，$会被自动地追加到PATTERN上）。如果不希望该PATTERN的匹配位置被固定，可以在开头或者结尾写上\*。注意在双引号内，所有的正则表达式特殊字符会失去其特殊含义并且按照其字面意思进行匹配。另外，在操作符名称PATTERN中（即\\do的PATTERN参数），正则表达式特殊字符也按照字面意思进行匹配。
+
+### 常见问题处理
+
+**连接性能问题**
+
+- 开启了log_hostname，但是配置了错误的DNS导致的连接性能问题。
+
+  在连接上数据库，通过“show log_hostname”语句，检查数据库中是否开启了log_hostname参数。
+
+  如果开启了相关参数，那么数据库内核会通过DNS反查客户端所在机器的主机名。这时如果数据库主节点配置了不正确的/不可达的DNS服务器，那么会导致数据库建立连接过程较慢。此参数的更多信息，详见《参考指南》中“GUC参数说明 &gt; 错误报告和日志 &gt; [记录日志的内容](3-logging-content)”章节中关于“log_hostname”的描述。
+
+- 数据库内核执行初始化语句较慢导致的性能问题。
+
+  此种情况定位较难，可以尝试使用Linux的跟踪命令：strace。
+
+  ```bash
+  strace gsql -U MyUserName -W MyPassWord -d mogdb -h 127.0.0.1 -p 23508 -r -c '\q'
+  ```
+
+  此时便会在屏幕上打印出数据库的连接过程。比如较长时间停留在下面的操作上：
+
+  ```bash
+  sendto(3, "Q\0\0\0\25SELECT VERSION()\0", 22, MSG_NOSIGNAL, NULL, 0) = 22
+  poll([{fd=3, events=POLLIN|POLLERR}], 1, -1) = 1 ([{fd=3, revents=POLLIN}])
+  ```
+
+  此时便可以确定是数据库执行“SELECT VERSION()”语句较慢。
+
+  在连接上数据库后，便可以通过执行“explain performance select version()”语句来确定初始化语句执行较慢的原因。更多信息，详见《性能优化指南》中“SQL优化指南 &gt; [SQL执行计划介绍](2-introduction-to-the-sql-execution-plan)”章节。
+
+  另外还有一种场景不太常见：由于数据库主节点所在机器的磁盘满或故障，此时所查询等受影响，无法进行用户认证，导致连接过程挂起，表现为假死。解决此问题清理数据库主节点的数据盘空间便可。
+
+- TCP连接创建较慢问题。
+
+  此问题可以参考上面的初始化语句较慢排查的做法，通过strace跟踪，如果长时间停留在：
+
+  ```bash
+  connect(3, {sa_family=AF_FILE, path="/home/test/tmp/gaussdb_llt1/.s.PGSQL.61052"}, 110) = 0
+  ```
+
+  或者
+
+  ```bash
+  connect(3, {sa_family=AF_INET, sin_port=htons(61052), sin_addr=inet_addr("127.0.0.1")}, 16) = -1 EINPROGRESS (Operation now in progress)
+  ```
+
+  那么说明客户端与数据库端建立物理连接过慢，此时应当检查网络是否存在不稳定、网络吞吐量太大的问题。
+
+**创建连接故障**
+
+- gsql: could not connect to server: No route to host
+
+  此问题一般是指定了不可达的地址或者端口导致的。请检查-h参数与-p参数是否添加正确。
+
+- gsql: FATAL: Invalid username/password,login denied.
+
+  此问题一般是输入了错误的用户名和密码导致的，请联系数据库管理员，确认用户名和密码的正确性。
+
+- gsql: FATAL: Forbid remote connection with trust method!
+
+  数据库由于安全问题，禁止远程登录时使用trust模式。这时需要修改pg_hba.conf里的连接认证信息。具体的设置信息请参见：《安全指南》中“数据库安全管理 &gt; 客户端接入认证 &gt; [配置文件参考](1-client-access-authentication#配置文件参考)”章节。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 请不要修改pg_hba.conf中MogDB主机的相关设置，否则可能导致数据库功能故障。建议业务应用部署在MogDB之外，而非MogDB内部。
+
+- 连接数据库，添加“-h 127.0.0.1”可以连接，去掉后无法连接问题。
+
+  通过执行SQL语句“show unix_socket_directory”检查数据库主节点使用的Unix套接字目录，是否与shell中的环境变量$PGHOST一致。
+
+  如果检查结果不一致，那么修改PGHOST环境变量到GUC参数unix_socket_directory指向的目录便可。
+
+  关于unix_socket_directory的更多信息，详见《参考指南》中“GUC参数说明 &gt; 连接和认证 &gt; [连接设置](1-connection-settings)”章节中的说明。
+
+- The “libpq.so” loaded mismatch the version of gsql, please check it.
+
+  此问题是由于环境中使用的libpq.so的版本与gsql的版本不匹配导致的，请通过“ldd gsql”命令确认当前加载的libpq.so的版本，并通过修改LD_LIBRARY_PATH环境变量来加载正确的libpq.so。
+
+- gsql: symbol lookup error: xxx/gsql: undefined symbol: libpqVersionString
+
+  此问题是由于环境中使用的libpq.so的版本与gsql的版本不匹配导致的（也有可能是环境中存在PostgreSQL的libpq.so），请通过“ldd gsql”命令确认当前加载的libpq.so的版本，并通过修改LD_LIBRARY_PATH环境变量来加载正确的libpq.so。
+
+- gsql: connect to server failed: Connection timed out
+
+  Is the server running on host “xx.xxx.xxx.xxx” and accepting TCP/IP connections on port xxxx?
+
+  此问题是由于网络连接故障造成。请检查客户端与数据库服务器间的网络连接。如果发现从客户端无法PING到数据库服务器端，则说明网络连接出现故障。请联系网络管理人员排查解决。
+
+  ```bash
+  ping -c 4 10.10.10.1
+  PING 10.10.10.1 (10.10.10.1) 56(84) bytes of data.
+  From 10.10.10.1: icmp_seq=2 Destination Host Unreachable
+  From 10.10.10.1 icmp_seq=2 Destination Host Unreachable
+  From 10.10.10.1 icmp_seq=3 Destination Host Unreachable
+  From 10.10.10.1 icmp_seq=4 Destination Host Unreachable
+  --- 10.10.10.1 ping statistics ---
+  4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 2999ms
+  ```
+
+- gsql: FATAL: permission denied for database “mogdb”
+
+  DETAIL: User does not have CONNECT privilege.
+
+  此问题是由于用户不具备访问该数据库的权限，可以使用如下方法解决。
+
+  1. 使用管理员用户dbadmin连接数据库。
+
+     ```bash
+     gsql -d mogdb -U dbadmin -p 15400
+     ```
+
+  2. 赋予该用户访问数据库的权限。
+
+     ```sql
+     GRANT CONNECT ON DATABASE mogdb TO user1;
+     ```
+
+     > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 实际上，常见的许多错误操作也可能产生用户无法连接上数据库的现象。如用户连接的数据库不存在，用户名或密码输入错误等。这些错误操作在客户端工具也有相应的提示信息。
+     >
+     > ```bash
+     > gsql -d mogdb -p 15400
+     > gsql: FATAL:  database "mogdb" does not exist
+     > gsql -d mogdb -U user1 -W gauss@789 -p 15400
+     > gsql: FATAL:  Invalid username/password,login denied.
+     > ```
+
+- gsql: FATAL: sorry, too many clients already，active/non-active: 2/10/3.
+
+    此问题是由于系统连接数量超过了最大连接数量。请联系数据库DBA进行会话连接数管理，释放无用会话。
+
+    关于查看用户会话连接数的方法见。
+
+    会话状态可以在视图PG_STAT_ACTIVITY中查看。无用会话可以使用函数pg_terminate_backend进行释放。
+
+    ```sql
+    select datid,pid,state from pg_stat_activity;
+     datid |       pid       | state
+    -------+-----------------+--------
+    13205 | 139834762094352 | active
+    13205 | 139834759993104 | idle
+    (2 rows)
+    ```
+
+    其中pid的值即为该会话的线程ID。根据线程ID结束会话。
+
+    ```sql
+    SELECT PG_TERMINATE_BACKEND(139834759993104);
+    PG_TERMINATE_BACKEND
+    ----------------------
+     t
+    (1 row)
+    ```
+
+  - 查看指定用户的会话连接数上限
+
+      执行如下命令查看连接到指定用户USER1的会话连接数上限。其中-1表示没有对用户user1设置连接数的限制
+
+      ```sql
+      SELECT ROLNAME,ROLCONNLIMIT FROM PG_ROLES WHERE ROLNAME='user1';
+      rolname | rolconnlimit
+      ------------------------+-------------
+      user1    |           -1
+      (1 row)
+      ```
+
+  - 查看指定数据库的会话连接数上限
+
+      执行如下命令查看连接到指定数据库mogdb的会话连接数上限。其中-1表示没有对数据库mogdb设置连接数的限制
+
+      ```sql
+      SELECT DATNAME,DATCONNLIMIT FROM PG_DATABASE WHERE DATNAME='mogdb';
+      datname  | datconnlimit
+      ------------------+-------------
+      mogdb |           -1 (1 row)
+      (1 row)
+      ```
+
+  - 查看指定数据库已使用的会话连接数
+
+      执行如下命令查看指定数据库mogdb上已使用的会话连接数。其中，1表示数据库mogdb上已使用的会话连接数
+
+      ```sql
+      SELECT COUNT(*) FROM PG_STAT_ACTIVITY WHERE DATNAME='mogdb';
+      count
+      ------------------
+      1
+      (1 row)
+      ```
+
+- gsql: wait xxx.xxx.xxx.xxx:xxxx timeout expired
+
+  gsql在向数据库发起连接的时候，会有5分钟超时机制，如果在这个超时时间内，数据库未能正常的对客户端请求进行校验和身份认证，那么gsql会退出当前会话的连接过程，并报出如上错误。
+
+  一般来说，此问题是由于连接时使用的-h参数及-p参数指定的连接主机及端口有误（即错误信息中的xxx部分），导致通信故障；极少数情况是网络故障导致。要排除此问题，请检查数据库的主机名及端口是否正确。
+
+- gsql: could not receive data from server: Connection reset by peer.
+
+  同时，检查数据库主节点日志中出现类似如下日志“ FATAL: cipher file “/data/dbnode/server.key.cipher” has group or world access”，一般是由于数据目录或部分关键文件的权限被误操作篡改导致。请参照其他正常实例下的相关文件权限，修改回来便可。
+
+- gsql: FATAL: GSS authentication method is not allowed because XXXX user password is not disabled.
+
+  目标数据库主节点的pg_hba.conf里配置了当前客户端IP使用”gss”方式来做认证，该认证算法不支持用作客户端的身份认证，请修改到”sha256”后再试。配置方法见《安全指南》中“数据库安全管理 &gt; 客户端接入认证 &gt; [配置文件参考](1-client-access-authentication#配置文件参考)”章节。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  >
+  > - 请不要修改pg_hba.conf中MogDB主机的相关设置，否则可能导致数据库功能故障。
+  > - 建议业务应用部署在MogDB之外，而非MogDB内部。
+
+**其他故障**
+
+- 出现因“总线错误”（Bus error）导致的core dump或异常退出
+
+  一般情况下出现此种问题，是进程运行过程中加载的共享动态库（在Linux为.so文件）出现变化；或者进程二进制文件本身出现变化，导致操作系统加载机器的执行码或者加载依赖库的入口发生变化，操作系统出于保护目的将进程杀死，产生core dump文件。
+
+  解决此问题，重试便可。同时请尽可能避免在升级等运维操作过程中，在MogDB内部运行业务程序，避免升级时因替换文件产生此问题。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 此故障的core dump文件的可能堆栈是dl_main及其子调用，它是操作系统用来初始化进程做共享动态库加载的。如果进程已经初始化，但是共享动态库还未加载完成，严格意义上来说，进程并未完全启动。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/0-gs_cgroup.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/0-gs_cgroup.md
new file mode 100644
index 0000000000000000000000000000000000000000..cb54bcbe69608d68d0189c2e44fb7a1ce7fb071e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/0-gs_cgroup.md
@@ -0,0 +1,424 @@
+---
+title: gs_cgroup
+summary: gs_cgroup
+author: Zhang Cuiping
+date: 2021-11-17
+---
+
+# gs_cgroup
+
+## 背景信息
+
+集群环境下做批量任务处理时，多任务复杂性，会导致不同机器间的负载差距很大。为了充分利用集群资源，负载管理变得尤为重要。gs_cgroup是MogDB提供的负载管理工具。负责创建默认控制组、创建用户自定义控制组、删除用户自定义控制组、更新用户自定义组的资源配额和资源限额、显示控制组配置文件内容、显示控制组树形结构和删除用户的所有控制组。
+
+gs_cgroup工具为使用数据库的操作系统用户创建Cgroups配置文件，并且在操作系统中生成用户设定的Cgroups。同时为用户提供增加、删除Cgroups、更新Cgroups资源配额、设定Cgroups的CPU或IO限额、设定异常处理阈值及相应操作等服务。此工具只负责当前操作系统节点的Cgroups操作，使用时需在各个节点上调用相同命令语句进行统一配置。
+
+这里假设读者已经了解了负载管理的相关原理，具体请参考《开发者指南》中“资源负载管理”章节。
+
+## 使用示例
+
+- 使用普通用户或数据库管理员执行命令。
+
+1. 前置条件: 需设置GAUSSHOME环境变量为数据库安装目录；且root用户已创建普通用户默认的控制组。
+
+2. 创建控制组及设置对应的资源配额，以便在数据库中运行作业时，指定到此控制组，使用此控制组管理的资源；通常数据库管理员为每个数据库用户创建Class组。
+
+    1. 创建Class控制组和Workload控制组。
+
+        ```bash
+        gs_cgroup -c -S class1 -s 40
+        ```
+
+        创建当前用户新的Class Cgroups命名为`class1`，资源配额为总Class的40%。
+
+        ```bash
+        gs_cgroup -c -S class1 -G grp1 -g 20
+        ```
+
+        创建当前用户新的“class1” Cgroups下属的Workload控制组，命名为`grp1`，资源配额为`class1`Cgroups的20%。
+
+    2. 删除grp1控制组和Class控制组。
+
+        ```bash
+        gs_cgroup -d -S class1 -G grp1
+        ```
+
+        删除当前用户已建的`grp1`Cgroups。
+
+        ```bash
+        gs_cgroup -d -S class1
+        ```
+
+        删除当前用户已建的`class1`Cgroups。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+    > 如果删除Class控制组，则Workload控制组也被删除。
+
+3. 更新已创建控制组的资源配额。
+
+    1. 更新动态资源配额
+
+        ```bash
+        gs_cgroup -u -S class1 -G grp1 -g 30
+        ```
+
+        更新当前用户的class1 Cgroups下属grp1 Cgroups资源配额为class1 Cgroups的30%。
+
+    2. 更新限制资源配额
+
+        ```bash
+        gs_cgroup --fixed -u -S class1 -G grp1 -g 30
+        ```
+
+    更新当前用户的class1 Cgroups下属grp1 Cgroups限制使用CPU核数范围占上一级class1可用核数的30%。
+
+4. 更新Gaussdb的CPU核数范围。
+
+    ```bash
+    gs_cgroup -u -T Gaussdb -f 0-20
+    ```
+
+    更新Gaussdb进程使用的CPU核数为0-20。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+    > -f参数只适用于对Gaussdb设置核数范围。对于其他各控制组，如需设置核数范围，需要使用-fixed参数。
+
+5. 设置异常处理信息（class:wg组需存在）。
+
+    1. 设置组class:wg下的作业阻塞到1200秒或执行2400秒时执行终止动作：
+
+        ```bash
+        gs_cgroup -S class -G wg -E "blocktime=1200,elapsedtime=2400" -a
+        ```
+
+    2. 设置组class:wg下的作业下盘数据量达到256MB或大表广播数据量达到100MB时执行终止动作：
+
+        ```bash
+        gs_cgroup -S class -G wg -E "spillsize=256,broadcastsize=100" -a
+        ```
+
+    3. 设置组Class下的作业在所有DN上CPU总时间到达100s时执行降级动作：
+
+        ```bash
+        gs_cgroup -S class -E "allcputime=100" --penalty
+        ```
+
+    4. 设置组Class下的作业在所有DN上执行时间到达2400秒，倾斜率达到90时执行降级动作:
+
+        ```bash
+        gs_cgroup -S class -E "qualificationtime=2400,cpuskewpercnt=90"
+        ```
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+    > 给控制组设置异常处理信息，需要确保对应的控制组已经创建。指定多个阈值时用“，”分隔，不指定任何动作时默认为“penalty”操作。
+
+6. 设置控制组使用的核数范围。
+
+    设置组class:wg的核数范围占Class控制组的20%
+
+    ```bash
+    gs_cgroup -S class -G wg -g 20 --fixed -u
+    ```
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+    > Class或Workload核数范围必须通过指定-fixed参数设置。
+
+7. 回退上一个步骤。
+
+    ```bash
+    gs_cgroup --recover
+    ```
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+    > -recover只支持对Class控制组和Workload控制组的增删改操作进行回退，且只支持回退一次操作。
+
+8. 查看已创建的控制组信息。
+
+    1. 查看配置文件中控制组信息。
+
+        ```bash
+        gs_cgroup -p
+        ```
+
+        控制组配置信息
+
+        ```bash
+        gs_cgroup -p
+
+        Top Group information is listed:
+        GID:   0 Type: Top    Percent(%): 1000( 50) Name: Root                  Cores: 0-47
+        GID:   1 Type: Top    Percent(%):  833( 83) Name: Gaussdb:omm           Cores: 0-20
+        GID:   2 Type: Top    Percent(%):  333( 40) Name: Backend               Cores: 0-20
+        GID:   3 Type: Top    Percent(%):  499( 60) Name: Class                 Cores: 0-20
+
+        Backend Group information is listed:
+        GID:   4 Type: BAKWD  Name: DefaultBackend   TopGID:   2 Percent(%): 266(80) Cores: 0-20
+        GID:   5 Type: BAKWD  Name: Vacuum           TopGID:   2 Percent(%):  66(20) Cores: 0-20
+
+        Class Group information is listed:
+        GID:  20 Type: CLASS  Name: DefaultClass     TopGID:   3 Percent(%): 166(20) MaxLevel: 1 RemPCT: 100 Cores: 0-20
+        GID:  21 Type: CLASS  Name: class1           TopGID:   3 Percent(%): 332(40) MaxLevel: 2 RemPCT:  70 Cores: 0-20
+
+        Workload Group information is listed:
+        GID:  86 Type: DEFWD  Name: grp1:2           ClsGID:  21 Percent(%):  99(30) WDLevel:  2 Quota(%): 30 Cores: 0-5
+
+        Timeshare Group information is listed:
+        GID: 724 Type: TSWD   Name: Low              Rate: 1
+        GID: 725 Type: TSWD   Name: Medium           Rate: 2
+        GID: 726 Type: TSWD   Name: High             Rate: 4
+        GID: 727 Type: TSWD   Name: Rush             Rate: 8
+
+        Group Exception information is listed:
+        GID:  20 Type: EXCEPTION Class: DefaultClass
+        PENALTY: QualificationTime=1800 CPUSkewPercent=30
+
+        GID:  21 Type: EXCEPTION Class: class1
+        PENALTY: AllCpuTime=100 QualificationTime=2400 CPUSkewPercent=90
+
+        GID:  86 Type: EXCEPTION Group: class1:grp1:2
+        ABORT: BlockTime=1200 ElapsedTime=2400
+        ```
+
+    2. 查看操作系统中树形结构的控制组信息
+
+        `gs_cgroup -P`显示控制组树形结构信息，其中shares代表操作系统中CPU资源的动态资源配额`cpu.shares`的数值，cpus代表操作系统中CPUSET资源的动态资源限额`cpuset.cpus`的数值，指的是该控制组能够使用的核数范围。
+
+        ```bash
+        gs_cgroup -P
+        Mount Information:
+        cpu:/dev/cgroup/cpu
+        blkio:/dev/cgroup/blkio
+        cpuset:/dev/cgroup/cpuset
+        cpuacct:/dev/cgroup/cpuacct
+
+        Group Tree Information:
+        - Gaussdb:wangrui (shares: 5120, cpus: 0-20, weight: 1000)
+                - Backend (shares: 4096, cpus: 0-20, weight: 400)
+                        - Vacuum (shares: 2048, cpus: 0-20, weight: 200)
+                        - DefaultBackend (shares: 8192, cpus: 0-20, weight: 800)
+                - Class (shares: 6144, cpus: 0-20, weight: 600)
+                        - class1 (shares: 4096, cpus: 0-20, weight: 400)
+                                - RemainWD:1 (shares: 1000, cpus: 0-20, weight: 100)
+                                        - RemainWD:2 (shares: 7000, cpus: 0-20, weight: 700)
+                                                - Timeshare (shares: 1024, cpus: 0-20, weight: 500)
+                                                        - Rush (shares: 8192, cpus: 0-20, weight: 800)
+                                                        - High (shares: 4096, cpus: 0-20, weight: 400)
+                                                        - Medium (shares: 2048, cpus: 0-20, weight: 200)
+                                                        - Low (shares: 1024, cpus: 0-20, weight: 100)
+                                        - grp1:2 (shares: 3000, cpus: 0-5, weight: 300)
+                                - TopWD:1 (shares: 9000, cpus: 0-20, weight: 900)
+                        - DefaultClass (shares: 2048, cpus: 0-20, weight: 200)
+                                - RemainWD:1 (shares: 1000, cpus: 0-20, weight: 100)
+                                        - Timeshare (shares: 1024, cpus: 0-20, weight: 500)
+                                                - Rush (shares: 8192, cpus: 0-20, weight: 800)
+                                                - High (shares: 4096, cpus: 0-20, weight: 400)
+                                                - Medium (shares: 2048, cpus: 0-20, weight: 200)
+                                                - Low (shares: 1024, cpus: 0-20, weight: 100)
+                                - TopWD:1 (shares: 9000, cpus: 0-20, weight: 900)
+        ```
+
+## 参数说明
+
+- -a [-abort]
+
+  对满足设定的异常阈值的作业执行终止动作。
+
+- -b pct
+
+  Backend Cgroups占用Top Backend资源的百分比，需同时指定`-B backendname`参数。
+
+  取值范围
+
+  - 为1 ~ 99。在不进行设置的情况下，默认CPU配额设置为Vacuum控制组占20%，DefaultBackend控制组占80%。Vacuum和DefaultBackend控制组配额之和设置应小于100%。
+
+- -B name
+
+  Backend Cgroups名称，仅可指定`-u`参数来更新此Cgroups的资源配额。
+
+  `-b percent`和`-B backendname`参数共同作用来控制数据库后备线程的资源比例。
+
+  取值范围: 字符串，最长为64个字节。
+
+- -c
+
+  创建Cgroups并指定其标识。
+
+  普通用户指定`-c`和`-S classname`可以创建新的Class Cgroups，如果再指定`-G groupname`则创建属于Class Cgroups的Workload Cgroups，新的Workload Cgroups位于Class Cgroups的最底层（4层是最底层）。
+
+- -d
+
+  删除Cgroups及标识。
+
+  普通用户指定`-d`和`-S classname`可以删除已有的Class Cgroups，如果再指定`-G groupname`则删除属于Class Cgroups的Workload Cgroups，并将附属的线程重置到`DefaultClass:DefaultWD:1`Cgroups中；若删除的Workload Cgroups位于Class Cgroups的高层（1层是最高层），则需调整低层的Cgroups的层级，重建新的Cgroups附属的线程加载到新的Cgroups。
+
+- -E data
+
+  设定异常阈值，目前阈值包括：`blocktime`、`elapsedtime`、`allcputime`、`spillsize`、`broadcastsize`以及`qualificationtime`和`cpuskewpercent`，指定多个阈值时用“，”分隔。参数值0表示取消设置，设置不合法的值时会提示。
+
+  **表 2** 异常阈值类型
+
+  | 异常阈值类型      | 说明                                                         | 取值范围（0表示取消设置） | 支持的异常操作 |
+  | :---------------- | :----------------------------------------------------------- | :------------------------ | :------------- |
+  | blocktime         | 作业的阻塞时间，单位秒。包括全局并发排队以及局部并发排队的总时间。 | 0~UINT_MAX                | abort          |
+  | elapsedtime       | 作业的已被执行时间，单位秒。从开始执行到当前所消耗的时间。   | 0~UINT_MAX                | abort          |
+  | allcputime        | 作业在所有DN上执行时所耗费的CPU总时间，单位秒。              | 0~UINT_MAX                | abort，penalty |
+  | cpuskewpercent    | 作业在DN上执行时的CPU时间的倾斜率，依赖于qualificationtime的设置。 | 0~100                     | abort，penalty |
+  | qualificationtime | 检查作业执行cpu倾斜率的间隔时间，单位秒，需同cpuskewpercent一起设置。 | 0~UINT_MAX                | none           |
+  | spillsize         | 作业在DN上下盘的数据量，单位MB。                             | 0~UINT_MAX                | abort          |
+  | broadcastsize     | 作业在DN上算子大表广播数据量，单位MB。                       | 0~UINT_MAX                | abort          |
+
+- -h [-help]
+
+  显示命令帮助信息。
+
+- -H
+
+  用户环境中`$GAUSSHOME`信息。
+
+  取值范围: 字符串，最长为1023个字符。
+
+- -f
+
+  设置Gaussdb控制组使用的核数范围，范围必须是a-b或a的形式。其他控制组可以使用-fixed进行设置核数范围。
+
+- -fixed
+
+  设置控制组使用的核数范围比例占上一层级的百分比或者设置IO资源。
+
+  设置核数范围比例时-fixed设置核数范围与'-s' '-g' '-t' '-b' 一起使用。
+
+  核数比例范围0-100，同一层级的核数比例总和小于或者等于100，0代表核数与上一层级相同，对于所有的控制组，CPU限额默认设置为0。-f和-fixed不能同时设置。设置-fixed之后，-f设置的范围自动失效。设置的比例以quota值在-p中进行显示。
+
+  设置IO资源配额时，与'-R' '-r' '-W' '-w'一起使用。
+
+- -g pct
+
+  指定Workload Cgroups的资源占用`Class Cgroups`资源的百分比，需同时指定`-G groupname`参数；用于创建`-c`或更新`-u`Workload Cgroups。
+
+  取值范围为1 ~ 99。默认Workload控制组CPU配额设置为20%。各Workload控制组配额之和应小于99%。
+
+- -G name
+
+  指定Workload Cgroups的名称，需同时指定`-S classname`参数来表示该group属于哪个Class Cgroups；可以连同`-c`参数创建新的Cgroups、`-d`参数删除此Cgroups及`-u`更新此Cgroups的资源配额；需要注意，此名称不可是Timeshare Cgroups的默认名称，如`Low`、`Medium”`、`High`或`Rush`。
+
+  如果用户自己创建Workload控制组，指定名称时不能指定带 ':' 的名称。不能创建同名控制组。
+
+  取值范围: 字符串，最长为28个字节。
+
+- -N [-group] name
+
+  可以将组名简写成class:wg。
+
+- -p
+
+  显示Cgroups配置文件的信息。
+
+- -P
+
+  显示Cgroups树形结构信息。
+
+- -penalty
+
+  对满足设定的异常阈值的作业执行降级动作，如果没有设定任何操作，则该操作将为默认操作。
+
+- -r data
+
+  仅用于更新I/O资源读数据上限，用于设置`blkio.throttle.read_bps_device`的数值；为字符串类型，该字符串由`major:minor value`构成，其中major为要访问的磁盘的主设备号，minor为要访问的磁盘的次设备号，value为设备每秒读操作次数上限数值，取值范围为0 ~ ULONG_MAX，其中取值0用来初始化此字段为空；需和“-u”参数及Cgroups名称一同使用；如果Class Cgroups和Workload Cgroups的名称同时指定，则只应用到Workload Cgroups。
+
+  取值范围: 字符串，最长为32个字符。
+
+- -R data
+
+  仅用于更新IO资源每秒读操作次数上限，用于设置`blkio.throttle.read_iops_device`的数值；取值信息同`-r`参数；需和`-u`参数及Cgroups名称一同使用；如果Class Cgroups和Workload Cgroups的名称同时指定，则只应用到Workload Cgroups。
+
+  取值范围: 字符串，最长为32个字符。
+
+- -recover
+
+  仅用于回退Class控制组和Workload控制组的增删改操作，且只能回退一步。
+
+- -revert
+
+  恢复控制组为默认状态。
+
+- -D mpoint
+
+  指定的挂载点，默认的挂载点`/dev/cgroup/subsystem`。
+
+- -m
+
+  挂载cgroup。
+
+- -M
+
+  取消挂载cgroup。
+
+- -U
+
+  数据库用户名称。
+
+- -refresh
+
+  刷新控制组状态。
+
+- -s pct
+
+  指定Class Cgroups的资源占用`Top Class Cgroups`资源的百分比，需同时指定`-S classname`参数；用于创建`-c`或更新`-u`Class Cgroups。
+
+  取值范围为1-99。默认Class控制组的CPU配额设置为20%，R6C10版本中，Class控制组的CPU配额设置为40%，升级过程中，不会对此配额做更新。新创建的Class控制组的CPU配额以及默认的DefaultClass之和应小于100%。
+
+- -S name
+
+  指定Class group的名称；可以连同`-c`参数创建新的Cgroups、`-d`参数删除此Cgroups及`-u`更新此Cgroups的资源配额。创建子Class名称不能带‘：’。
+
+  取值范围: 字符串，最长为31个字节。
+
+- -t percent
+
+  指定Top Cgroups（Root、Gaussdb:omm、Backend和Class Cgroups）占用资源的百分比，需同时指定“-T name”参数。若指定“-T Root”所在的Cgroups，其在Cgroups配置文件中显示的名称为“Root”，此数值代表的含义是blkio.weight值的百分比，最小值为10%，CPU资源配额如cpu.shares的数值不可修改；若指定“Gaussdb:omm” Cgroups，则表示占用整个系统CPU资源的百分比（可根据Root Cgroups的默认CPU配额1024得出该组的cpu.shares数值，此数值默认当前系统仅含有1套数据库环境），对于IO资源配额为1000，不再变化;若指定“Class”或“Backend”Cgroups，则表示资源占用“Gaussdb”Cgroups资源的百分比。
+
+  取值范围为1 ~ 99。默认Class控制组配额为60%， Backend控制组配额为40%。修改Class控制组配额，同时会自动更新Backend控制组配额，使两者之和保持100%。
+
+- -T name
+
+  指定Top Cgroups的名称。
+
+  取值范围: 字符串，最长为64个字节。
+
+- -u
+
+  更新Cgroups。
+
+- -V [-version]
+
+  显示gs_cgroup工具的版本信息。
+
+- -w data
+
+  仅用于更新I/O资源每秒写数据上限，用于设置`blkio.throttle.write_bps_device`的数值。取值信息同`-r`参数，需和`-u`参数及Cgroups名称一同使用。如果Class Cgroups和Workload Cgroups的名称同时指定，则只应用到Workload Cgroups。
+
+  取值范围: 字符串，最长为32个字符。
+
+- -W data
+
+  仅用于更新IO资源每秒写操作次数上限，用于设置`blkio.throttle.write_iops_device`的数值。取值信息同`-r`参数，需和`-u`参数及Cgroups名称一同使用。如果Class Cgroups和Workload Cgroups的名称同时指定，则只应用到Workload Cgroups。
+
+  取值范围: 字符串，最长为32个字符。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 对于磁盘major:minor的编号获取，可以通过下面方式。如获取/mpp目录对应的磁盘编号：
+>
+> ```bash
+> df
+> Filesystem      1K-blocks      Used  Available Use% Mounted on
+> /dev/sda1       524173248  41012784  456534008   9% /
+> devtmpfs         66059264       236   66059028   1% /dev
+> tmpfs            66059264        88   66059176   1% /dev/shm
+> /dev/sdb1      2920486864 135987592 2784499272   5% /data
+> /dev/sdc1      2920486864  24747868 2895738996   1% /data1
+> /dev/sdd1      2920486864  24736704 2895750160   1% /mpp
+> /dev/sde1      2920486864  24750068 2895736796   1% /mpp1
+> ls -l /dev/sdd
+> brw-rw---- 1 root disk 8, 48 Feb 26 11:20 /dev/sdd
+> ```
+>
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 这里一定要查sdd的磁盘号，不能是sdd1的磁盘号。否则执行时会报错。 如果更新IO的限额配置信息超过了可允许的最大配置字串，则新的更新不存储在配置文件中。如当前设置的字串长度为96，更新IO的磁盘数量大于8个，则有可能超出字串限制，更新成功，但是不存储在配置文件中。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/1-gs_check.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/1-gs_check.md
new file mode 100644
index 0000000000000000000000000000000000000000..5d29933391d528ebdafd9242d58498971a523922
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/1-gs_check.md
@@ -0,0 +1,1136 @@
+---
+title: gs_check
+summary: gs_check
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_check
+
+## 背景信息
+
+gs_check改进增强，统一化当前系统中存在的各种检查工具，例如gs_check，gs_checkos等，帮助用户在MogDB运行过程中，全量的检查MogDB运行环境，操作系统环境，网络环境及数据库执行环境，也有助于在MogDB重大操作之前对各类环境进行全面检查，有效保证操作执行成功。
+
+## 注意事项
+
+- 必须指定-i或-e参数，-i会检查指定的单项，-e会检查对应场景配置中的多项。
+- 如果-i参数中不包含root类检查项或-e场景配置列表中没有root类检查项，则不需要交互输入root权限的用户及其密码。
+- 可使用-skip-root-items跳过检查项中包含的root类检查，以免需要输入root权限用户及密码。
+- MTU值不一致时可能导致检查缓慢或进程停止响应，当巡检工具出现提示时请修改各节点MTU值一致后再进行巡检。
+- 交换机不支持当前设置的MTU值时，即使MTU值一致也会出现通信问题引起进程停止响应，需要根据交换机调整MTU大小。
+
+## 语法
+
+- 单项检查：
+
+  ```bash
+  gs_check -i ITEM [...] [-U USER] [-L] [-l LOGFILE] [-o OUTPUTDIR] [--skip-root-items][--set][--routing]
+  ```
+
+- 场景检查：
+
+  ```bash
+  gs_check -e SCENE_NAME [-U USER] [-L] [-l LOGFILE] [-o OUTPUTDIR] [--skip-root-items] [--time-out=SECS][--set][--routing][--skip-items]
+  ```
+
+- 显示帮助信息：
+
+  ```bash
+  gs_check -? | --help
+  ```
+
+- 显示版本号信息：
+
+  ```bash
+  gs_check -V | --version
+  ```
+
+## 参数说明
+
+- -U
+
+  运行MogDB的用户名称。
+
+  取值范围: 运行MogDB的用户名称。
+
+- -L
+
+  本地执行。
+
+- -i
+
+  指定检查项。格式-i CheckXX详细的检查项请参见[表1 MogDB状态检查表]（#zhuangtaijiancha)。
+
+- -e
+
+  场景检查项。默认的场景有inspect（例行巡检）、upgrade（升级前巡检）、binary_upgrade（就地升级前巡检）、health（健康检查巡检）、install（安装），等，用户可以根据需求自己编写场景。
+
+- -l
+
+  指定日志文件路径，指定路径时需添加.log后缀。
+
+- -o
+
+  指定检查结果输出文件夹路径。
+
+- -skip-root-items
+
+  跳过需要root权限执行的检查项。
+
+- -skip-items
+
+  跳过指定的检查项。
+
+- -format
+
+  设置结果报告的格式。
+
+- -set
+
+  修复支持设置的Abnormal项。
+
+- -cid
+
+  检查ID，仅被内部check进程使用。
+
+- -time-out
+
+  设置超时时间。单位为秒，默认为1500s，若用户自定义超时时间不得少于1500s。
+
+- -routing
+
+  指定业务IP的网段，格式为IP地址:子网掩码。
+
+- -disk-threshold=“PERCENT”
+
+  检查磁盘占用时可选指定告警阈值，可指定1-99之间的整数，不输入则默认为90。检查其他项时不需要该参数。
+
+- -?, -help
+
+  显示帮助信息。
+
+- -V, -version
+
+  显示版本号信息。
+
+### MogDB状态检查表 <a id="zhuangtaijiancha"> </a>
+
+- OS
+    <table>
+        <tr>
+            <td>巡检项</td>
+            <td>检查内容</td>
+            <td>是否支持--set</td>
+        </tr>
+        <tr>
+            <td>CheckCPU（检查CPU使用率）</td>
+            <td>检查主机CPU占用率，如果idle大于30%并且iowait小于30%。则检查项通过，否则检查项不通过。</td>
+            <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckFirewall（检查防火墙状态）</td>
+          <td>检查主机防火墙状态，如果防火墙关闭则检查项通过，否则检查项不通过。</td>
+          <td>是</td>
+        </tr>
+        <tr>
+          <td>CheckTimeZone（检查时区一致性）</td>
+          <td>检查MogDB内各节点时区，如果时区一致则检查通过，否则检查项不通过。</td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckSysParams（检查系统参数）</td>
+          <td>
+            检查各节点操作系统参数，判断是否等于预期值。检查项不满足warning域则报warning，不满足NG域则检查项不通过，并打印不满足项。
+          </td>
+          <td>是</td>
+        </tr>
+        <tr>
+          <td>CheckOSVer（检查操作系统版本）</td>
+          <td>
+            检查MogDB内各个节点的操作系统版本信息，如果满足版本兼容列表且MogDB在同一混搭列表中则检查通过，否则检查不通过。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckNTPD（检查NTPD服务）</td>
+          <td>
+            检查系统NTPD服务，如果服务开启且各节点时间误差在1分钟以内则检查项通过，否则检查项不通过。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckTHP（检查THP服务)</td>
+          <td>检查系统THP服务，如果服务开启则检查项通过，否则检查项不通过。</td>
+          <td>是</td>
+        </tr>
+        <tr>
+          <td>CheckSshdService（检查sshd服务是否已启动)</td>
+          <td>检查系统是否存在sshd服务，若存在则检查项通过，否则检查项不通过。</td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckCrondService（检查crontab服务是否已启动)</td>
+          <td>检查系统是否存在crontab服务，若存在则检查项通过，否则检查项不通过。</td>
+          <td>是<br /></td>
+        </tr>
+        <tr>
+          <td>CheckCrontabLeft（检查crontab是否有残留Gauss相关信息)</td>
+          <td>
+            检查crontab是否残留Gauss相关信息，若无该信息则检查项通过，否则检查项不通过。
+          </td>
+          <td>是</td>
+        </tr>
+        <tr>
+          <td>CheckDirLeft（检查文件目录是否有残留)</td>
+          <td>
+            检查文件目录（/opt/enmo/Bigdata/ ,/var/log/Bigdata/,
+            /home/omm）是否存在，（若mount目录包含此目录则忽略）若不存在则查项通过，否则检查项不通过。
+          </td>
+          <td>是</td>
+        </tr>
+        <tr>
+          <td>CheckProcessLeft（检查进程是否有残留)</td>
+          <td>
+            检查是否残留gaussdb和omm进程，若未残留则检查项通过，否则检查项不通过。
+          </td>
+          <td>是</td>
+        </tr>
+        <tr>
+          <td>CheckStack（栈深度检查)</td>
+          <td>
+            检查栈深度，若各个节点不一致则报warning
+            ，若大于等于3072则检查项通过，否则不通过。
+          </td>
+          <td>是</td>
+        </tr>
+        <tr>
+          <td>CheckOmmUserExist（检查omm用户是否存在)</td>
+          <td>
+            检查是否存在omm用户，若不存在omm用户则检查项通过，否则检查项不通过。
+          </td>
+          <td>是</td>
+        </tr>
+        <tr>
+          <td>CheckPortConflict（检查数据库节点端口是否占用)</td>
+          <td>
+            检查数据库节点端口是否已被占用，若未占用则检查项通过，否则检查项不通过。
+          </td>
+          <td>是</td>
+        </tr>
+        <tr>
+          <td>CheckSysPortRange（检查ip_local_port_range设置范围）</td>
+          <td>
+            检查ip_local_port_range系统参数范围，若范围在26000~65535则检查项通过，否则检查项不通过。
+          </td>
+          <td>是</td>
+        </tr>
+        <tr>
+          <td>CheckEtcHosts（检查/etc/hosts中是否有重复地址以及localhost配置）</td>
+          <td>
+            检查/etc/hosts没有配置localhost检查项不通过，存在带有#MogDB注释的映射则检查项不通过，相同IP不同hostname则检查项不通过，否则通过，若hostname相同，但ip不同检查项不通过。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckCpuCount（检查CPU核数）</td>
+          <td>
+            检查CPU核心与可用CPU不符检查项不通过，相符但存在不可用信息Warning。
+            所有节点CPU信息不相同检查项不通过。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckHyperThread（检查超线程是否打开）</td>
+          <td>检查超线程，若打开则检查项通过，否则检查项不通过。</td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckMemInfo（检查内存总大小）</td>
+          <td>
+            检查各节点总内存大小是否一致，若检查结果一致，则检查项通过，否则报warning。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckSshdConfig（检查sshd服务配置是否正确）</td>
+          <td>
+            检查/etc/ssh/sshd_config文件，<br />
+            （a)PasswordAuthentication=yes; <br />
+            （b)MaxStartups=1000; <br />
+            （c)UseDNS=no; <br />
+            （d)ClientAliveInterval大于10800或者等于0 <br />
+            配置如上所示则检查项通过，若a、c配置不正确则报warning，b、d配置不正确则检查项不通过。
+          </td>
+          <td>是</td>
+        </tr>
+        <tr>
+          <td>CheckMaxHandle（检查句柄最大设置）</td>
+          <td>
+            检查操作系统最大句柄值，如果该值大于等于1000000则检查项通过，否则检查项不通过。
+          </td>
+          <td>是</td>
+        </tr>
+        <tr>
+          <td>CheckKernelVer（检查内核版本）</td>
+          <td>
+            检查各节点系统内核版本信息，如果版本信息一致则检查项通过，否则报Warning。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckEncoding（检查编码格式）</td>
+          <td>
+            检查MogDB内各个节点的系统编码，如果编码一致则检查项通过，否则检查项不通过。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckBootItems（检查启动项）</td>
+          <td>检查是否有手动添加的启动项，如果没有则检查通过，否则检查不通过。</td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckDropCache（检查DropCache进程）</td>
+          <td>
+            检查各节点是否有dropcache进程在运行，若有则检查通过，否则检查不通过。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckFilehandle（检查文件句柄）</td>
+          <td>
+            此检查项检查以下两项，两项都通过为通过，否则为不通过：<br />-
+            检查每个gaussdb进程打开的进程数是否超过80万，不超过则检查通过，否则检查不通过。<br />-
+            检查是否有slave进程使用的句柄数超过master进程，如果没有则检查通过，否则检查不通过。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckKeyProAdj（检查关键进程omm_adj的值）</td>
+          <td>
+            检查所有关键进程，如果所有关键进程的omm_adj值为0，则通过，否则不通过。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckMaxProcMemory（检查max_process_memory参数设置是否合理）</td>
+          <td>
+            检查数据库节点的max_process_memory值，判断该参数的值是否大于1G，若不大于则检查项通过，否则检查项不通过。
+          </td>
+          <td>是</td>
+        </tr>
+    </table>
+
+- Device
+
+    <table>
+        <tr>
+            <td>巡检项</td>
+            <td>检查内容</td>
+            <td>是否支持--set</td>
+        </tr>
+        <tr>
+          <td>CheckSwapMemory（检查交换内存）</td>
+          <td>
+            检查交换内存和总内存大小，若检查结果为0则检查项通过，否则检查项报Warning大于总内存时检查项不通过。
+          </td>
+          <td>是</td>
+        </tr>
+        <tr>
+          <td>CheckLogicalBlock（检查磁盘逻辑块）</td>
+          <td>检查磁盘逻辑块大小，若为512则检查项通过，否则检查项不通过。</td>
+          <td>是</td>
+        </tr>
+        <tr>
+          <td>CheckIOrequestqueue（检查IO请求）</td>
+          <td>检查IO值，如果该值为32768则检查项通过，否则检查项不通过。</td>
+          <td>是</td>
+        </tr>
+        <tr>
+          <td>CheckMaxAsyIOrequests（检查最大异步IO请求）</td>
+          <td>
+            获取当前异步IO请求值，当前异步IO请求值大于当前节点数据库实例数*1048576和104857600则检查项通过，否则检查项不通过。
+          </td>
+          <td>是</td>
+        </tr>
+        <tr>
+          <td>CheckIOConfigure（检查IO配置）</td>
+          <td>检查IO配置，如果是deadline则检查项通过，否则检查项不通过。</td>
+          <td>是</td>
+        </tr>
+        <tr>
+          <td>CheckBlockdev（检查磁盘预读块）</td>
+          <td>
+            检查磁盘预读块大小，如果预读块大小为16384则检查项通过，否则检查项不通过。
+          </td>
+          <td>是</td>
+        </tr>
+        <tr>
+          <td>CheckDiskFormat（检查磁盘格式参数）</td>
+          <td>
+            检查磁盘XFS格式信息，如果配置为'rw,noatime,inode64,allocsize=16m'则检查项通过，否则报warning。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckInodeUsage（检查磁盘inodes使用率）</td>
+          <td>
+            MogDB路径（GAUSSHOME/PGHOST/GPHOME/GAUSSLOG/tmp及实例目录）<br />
+            检查以上指定目录使用率，如果使用率超过warning阈值（默认为60%）
+            报warning超过NG阈值（默认为80%）则检查项不通过，否则通过。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckSpaceUsage（检查磁盘使用率）</td>
+          <td>
+            MogDB路径（GAUSSHOME/PGHOST/GPHOME/GAUSSLOG/tmp及实例目录）<br />
+            检查磁盘以上指定目录（目录列表）使用率，如果使用率超过warning阈值（默认为70%）
+            报warning超过NG阈值（默认为90%）则检查项不通过。MogDB路径下检查GAUSSHOME/PGHOST/GPHOME/GAUSSLOG/tmp/data路径的剩余空间，不满足阈值则检查项不通过，否则通过。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckDiskConfig（检查磁盘空间大小一致性）</td>
+          <td>检查磁盘名大小挂载点是否一致，若一致则检查项通过，否则报warning。</td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckXid（检查CheckXid数值）</td>
+          <td>查询xid的数值，如果大于10亿报Warning，大于18亿则检查项不通过。</td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckSysTabSize（检查每个实例的系统表容量）</td>
+          <td>
+            如果每一块磁盘的剩余容量大于该磁盘上所有实例的系统表容量总和则检查项通过，否则检查项不通过。
+          </td>
+          <td>否</td>
+        </tr>
+    </table>
+
+- Cluster
+
+    <table>
+        <tr>
+            <td>巡检项</td>
+            <td>检查内容</td>
+            <td>是否支持--set</td>
+        </tr>
+        <tr>
+          <td>CheckClusterState（检查MogDB状态）</td>
+          <td>
+            检查fencedUDF状态，如果fencedUDF状态为down则报warning；检查MogDB状态，如果MogDB状态为Normal则检查项通过，否则检查项不通过。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckDBParams（检查MogDB参数）</td>
+          <td>
+            检查数据库主节点检查共享缓冲区大小和Sem参数。<br />
+            数据库节点检查共享缓冲区大小和最大连接数。<br />共享缓冲区需要大于128KB且大于shmmax且大于shmall*PAGESIZE
+            <br />
+            若存在数据库主节点，则Sem值需大于（数据库节点最大连接数+150)/16向上取整。<br />以上项完全满足则检查项通过，否则检查项不通过。
+          </td>
+          <td>是</td>
+        </tr>
+        <tr>
+          <td>CheckDebugSwitch（检查日志级别）</td>
+          <td>
+            在各节点检查各实例的配置文件中log_min_messages参数的值，为空则认为是Warning，判断日志级别非waring，则报warning。
+          </td>
+          <td>是</td>
+        </tr>
+        <tr>
+          <td>CheckUpVer（检查升级版本是否一致）</td>
+          <td>
+            检查MogDB各个节点上升级包的版本，如果一致则检查项通过，否则检查项不通过。使用时，需指定升级软件包路径。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckDirPermissions（检查目录权限）</td>
+          <td>
+            检查节点目录（实例Xlog路径、GAUSSHOME、GPHOME、PGHOST、GAUSSLOG）权限，如果目录有写入权限且不大于750则检查项通过，否则检查项不通过。
+          </td>
+          <td>是</td>
+        </tr>
+        <tr>
+          <td>CheckEnvProfile（检查环境变量）</td>
+          <td>
+            检查节点环境变量（\$GAUSSHOME、\$LD_LIBRARY_PATH、\$PATH），检查CMS/CMA/数据库节点进程的环境变量。如果环境变量存在并配置正确，进程的环境变量存在则检查项通过，否则检查项不通过。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckGaussVer（检查gaussdb版本）</td>
+          <td>
+            检查各个节点的网卡型号以及驱动版本是否一致，一致则通过，否则报warning。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckPortRange（检查端口范围）</td>
+          <td>
+            若ip_local_port_range的范围在阈值范围内（默认是26000
+            65535），并且实例端口不在ip_local_port_range范围内则检查项通过，否则检查项不通过。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckReadonlyMode（检查只读模式）</td>
+          <td>
+            检查MogDB数据库主节点default_transaction_read_only值若为off则检查通过，否则不通过。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckCatchup（检查Catchup）</td>
+          <td>
+            检查gaussdb进程堆栈是否能搜索到CatchupMain函数，若搜索不到则检查项通过，否则检查项不通过。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckProcessStatus（检查MogDB进程属主）</td>
+          <td>
+            检查
+            'gaussdb'进程属主，若不存在omm以外的属主则检查项通过，否则检查项不通过。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckSpecialFile（特殊文件检查）</td>
+          <td>
+            检查tmp目录（PGHOST)、OM目录（GPHOME)、日志目录（GAUSSLOG)、data目录、程序目录（GAUSSHOME)下文件是否存在特殊字符以及非omm用户的文件，若不存在则检查项通过，否则检查项不通过。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckCollector（检查MogDB的信息收集）</td>
+          <td>
+            在output目录下查看信息收集是否成功，若收集成功则检查项通过，否则检查项不通过。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckLargeFile（检查数据目录大文件）</td>
+          <td>
+            检查各个数据库节点目录是否存在超过4G的文件。任一数据库节点目录及其子目录有超过4G的单个文件，则检查不通过，否则检查通过。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckProStartTime（关键进程启动时间检测）</td>
+          <td>
+            检查关键进程启动时间是否间隔超过5分钟，超过则检查不通过，否则检查通过。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckDilateSysTab（检查系统表膨胀）</td>
+          <td>检查系统表是否膨胀，若膨胀则不通过，否则检查通过。</td>
+          <td>是</td>
+        </tr>
+        <tr>
+          <td>CheckMpprcFile（检测环境变量分离文件改动）</td>
+          <td>
+            检查是否存在对环境变量分离文件的改动，若存在则检查不通过，否则检查通过。
+          </td>
+          <td>否</td>
+        </tr>
+    </table>
+
+- Database
+    <table>
+        <tr>
+            <td>状态</td>
+            <td>巡检项</td>
+            <td>检查内容</td>
+            <td>是否支持--set</td>
+        </tr>
+        <tr>
+            <td>CheckLockNum（检查锁数量）</td>
+            <td>检查数据库锁数量，查询成功检查项通过。</td>
+            <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckArchiveParameter（检查归档参数）</td>
+          <td>
+            检查数据库归档参数，如果未打开或打开且在数据库节点下则检查项通过，
+            打开且不在数据库主节点目录下则检查项不通过。
+          </td>
+          <td>是</td>
+        </tr>
+        <tr>
+          <td>CheckCurConnCount（检查当前连接数)</td>
+          <td>
+            检查数据库连接数，如果连接数小于最大连接数的90%则检查项通过，否则检查项不通过。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckCursorNum（检查当前游标数)</td>
+          <td>检查数据库的游标数，检查成功则检查项通过，否则检查项不通过。</td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>
+            CheckMaxDatanode（检查comm_max_datanode参数值范围小于数据库节点个数)
+          </td>
+          <td>
+            检查最大数据库节点数，若最大数据库节点数小于xml配置的节点数*数据库节点数（默认值为90*5）报warning，否则检查项通过。
+          </td>
+          <td>是</td>
+        </tr>
+        <tr>
+          <td>CheckPgPreparedXacts（检查残留两阶段事务)</td>
+          <td>
+            检查pgxc_prepared_xacts参数，如果不存在二阶段事务则检查项通过，否则检查项不通过。
+          </td>
+          <td>是</td>
+        </tr>
+        <tr>
+          <td>CheckPgxcgroup（检查pgxc_group表中需要重分布的个数)</td>
+          <td>
+            检查pgxc_group表中需要重分布的个数，检查结果为0则通过， 否则不通过。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckLockState（MogDB是否被锁)</td>
+          <td>检查MogDB是否被锁，若MogDB被锁则不通过，否则检查项通过。</td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckIdleSession（检查业务停止)</td>
+          <td>检查非空闲会话数，如果数量为0则检查项通过，否则检查项不通过。</td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckDBConnection（检查数据库连接)</td>
+          <td>检查能否连接数据库，如果连接成功则检查项通过，否则检查项不通过。</td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckGUCValue（GUC参数检查)</td>
+          <td>
+            检查（max_connections + max_prepared_transactions) *
+            max_locks_per_transaction的值，若该值大于等于1000000则检查项通过，否则检查项不通过。
+          </td>
+          <td>是</td>
+        </tr>
+        <tr>
+          <td>CheckPMKData（检查PMK异常数据)</td>
+          <td>
+            检查数据库PMK
+            schema是否包含有异常数据，如果不存在异常数据则检查项通过，否则检查项不通过。
+          </td>
+          <td>是</td>
+        </tr>
+        <tr>
+          <td>CheckSysTable（检查系统表)</td>
+          <td>检查系统表，检查成功则检查项通过。</td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckSysTabSize（检查每个实例的系统表容量）</td>
+          <td>
+            如果每一块磁盘的剩余容量大于该磁盘上所有实例的系统表容量总和则检查项通过，否则检查项不通过。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckTableSpace（检查表空间路径)</td>
+          <td>
+            表空间路径和MogDB路径之间不能存在嵌套且表空间路径相互不能存在嵌套，则检查项通过，否则检查项不通过。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckTableSkew（检查表级别数据倾斜）</td>
+          <td>
+            若存在表在MogDB各数据库节点上的数据分布不均衡，且分布数据最多的数据库节点比最低的数据库节点所分布的数据多100000条以上，则检查不通过，否则检查通过。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckDNSkew（检查数据库节点级别数据分布倾斜）</td>
+          <td>
+            检查数据库节点级别的表倾斜数据，若分布数据最高的数据库节点比分布数据最低的数据库节点数据量高于5%，则检查不通过，否则检查通过。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckUnAnalyzeTable（检查未做analyze的表）</td>
+          <td>
+            若存在未做analyze的表，并且表中至少包含一条数据，则检查不通过，否则检查通过。
+          </td>
+          <td>是</td>
+        </tr>
+        <tr>
+          <td>CheckCreateView（创建视图检查）</td>
+          <td>
+            创建视图时，如果查询语句中含有子查询，并且子查询结果查询解析和重写之后存在别名重复，检查不通过，否则检查通过。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckHashIndex（hash index语法检查）</td>
+          <td>如果存在hash index则检查不通过，否则检查通过。</td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckNextvalInDefault（检查Default表达式中包含nextval（sequence））</td>
+          <td>
+            检查Default表达式中是否包含nextval（sequence)，若包含则不通过，否则通过。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckNodeGroupName（Node group编码格式检查）</td>
+          <td>
+            存在非SQL_ASCII字符的Node Group名称则检查不通过，不存在则检查通过 。
+          </td>
+          <td>是</td>
+        </tr>
+        <tr>
+          <td>CheckPgxcRedistb（检查重分布残留的临时表 ）</td>
+          <td>
+            检查数据库中是否存在重分布残留的临时表，若不存在则检查通过，否则检查不通过
+            。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckReturnType（用户自定义函数返回值类型检查）</td>
+          <td>
+            检查用户自定义函数是否包含非法返回类型，若包含则检查不通过，否则检查通过。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckSysadminUser（检查sysadmin用户）</td>
+          <td>
+            检查除MogDB属主外是否存在数据库管理员用户，若存在则不通过，否则检查通过。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckTDDate（TD数据库中orc表date类型列检查）</td>
+          <td>
+            检查TD模式数据库下的orc表中是否包含date类型的列，若包含检查不通过，否则检查通过。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckDropColumn（drop column检查）</td>
+          <td>如果存在drop column的表，则检查不通过，否则检查通过。</td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckDiskFailure（检查磁盘故障）</td>
+          <td>
+            对MogDB中的所有数据做全量查询，若存在查询错误则检查不通过，否则检查通过。
+          </td>
+          <td>否</td>
+        </tr>
+    </table>
+- Network
+
+    <table>
+        <tr>
+            <td>状态</td>
+            <td>巡检项</td>
+            <td>检查内容</td>
+            <td>是否支持--set</td>
+        </tr>
+        <tr>
+          <td>CheckPing（检查网络通畅)</td>
+          <td>
+            检查MogDB内所有节点的互通性，如果各节点所有IP均可ping通则检查项通过，否则检查项不通过。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckRXTX（检查网卡RXTX值)</td>
+          <td>
+            检查节点backIP的RX/TX值，如果该值为4096则检查项通过，否则检查项不通过。
+          </td>
+          <td>是</td>
+        </tr>
+        <tr>
+          <td>CheckMTU（检查网卡MTU值)</td>
+          <td>
+            检查节点backIP对应的网卡MTU值（
+            bond后的物理网卡要确保一致），如果该值不是8192或1500报warning若MogDBMTU值一致则检查项通过，否则检查项不通过。
+          </td>
+          <td>是</td>
+        </tr>
+        <tr>
+          <td>CheckNetWorkDrop（检查网络掉包率)</td>
+          <td>
+            检查各IP1分钟内网络掉包率，如果不超过1%则检查项通过，否则检查项不通过。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckBond（检查网卡绑定模式)</td>
+          <td>
+            检查是否有配置BONDING_OPTS或BONDING_MODULE_OPTS，若没有配置则报warning。检查各节点bond模式是否一致，如果同时满足则检查项通过，否则检查项不通过。
+          </td>
+          <td>是</td>
+        </tr>
+        <tr>
+          <td>CheckMultiQueue（检查网卡多队列)</td>
+          <td>
+            检查cat
+            /proc/interrupts，判断是否开启网卡多队列且绑定不同CPU，如果满足则检查项通过，否则检查项不通过。
+          </td>
+          <td>是</td>
+        </tr>
+        <tr>
+          <td>CheckUsedPort（检查随机端口使用数量)</td>
+          <td>
+            检查net.ipv4.ip_local_port_range，范围大于等于OS默认值通过（32768-61000）;
+            <br />检查TCP协议随机端口数，小于总随机端口数的80%通过。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckNICModel（网卡型号和驱动版本一致性检查）</td>
+          <td>
+            检查各个节点的网卡型号以及驱动版本是否一致，一致则通过，否则报warning。
+          </td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckRouting（本地路由表检查）</td>
+          <td>检查各节点在业务IP网段的IP个数，超过1个则报warning，否则检查通过。</td>
+          <td>否</td>
+        </tr>
+        <tr>
+          <td>CheckNetSpeed（检查网卡接收带宽，ping值，丢包率)</td>
+          <td>
+            网络满载时，检查网卡平均接收带宽大于600MB通过; <br />
+            网络满载时，检查网络ping值，小于1秒通过;<br />
+            网络满载时，检查网卡丢包率，小于1%通过。
+          </td>
+          <td>否</td>
+        </tr>
+    </table>
+
+- Others
+
+    <table>
+        <tr>
+            <td>巡检项</td>
+            <td>检查内容</td>
+            <td>是否支持--set</td>
+        </tr>
+        <tr>
+            <td>CheckDataDiskUsage（检查数据库节点磁盘空间使用率)</td>
+            <td>检查磁盘数据库节点目录使用率，如果使用率低于90%则检查项通过，否则检查项不通过。</td>
+            <td>否</td>
+        </tr>
+    </table>
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** CheckNetSpeed检查项：
+>
+> - CheckNetSpeed不支持-L本地检查模式，-L模式无法构造网络压力，检查的结果不准确。
+> - 在节点数小于6时，speed_test构造的网络压力可能无法跑满带宽，可能会造成检查结果不准确。
+
+## 用户自定义场景
+
+1. 以操作系统用户omm登录数据库主节点。
+
+2. 在script/gspylib/inspection/config路径下新建场景配置文件scene_XXX.xml。
+
+3. 将检查项写进场景配置文件中，书写格式为：
+
+   ```xml
+   <?xml version="1.0" encoding="utf-8" ?>
+   <scene name="XXX" desc="check cluster parameters before XXX.">
+   <configuration/>
+   <allowitems>
+   <item name="CheckXXX"/>
+   <item name="CheckXXX"/>
+   </allowitems>
+   </scene>
+   ```
+
+   item name为检查项名称
+
+   注：用户需自行保证自定义xml的正确性
+
+4. 在home/package/script/gspylib/inspection/config执行如下命令，将此文件分发至执行检查的各个节点
+
+   ```bash
+   scp scene_upgrade.xml SIA1000068994：home/package/script/gspylib/inspection/config/
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** home/package/script/gspylib/inspection/config就是新建的场景配置文件的绝对路径。
+
+5. 换至omm用户，执行以下命令查看检查结果。
+
+   ```bash
+   gs_check  -e XXX
+   ```
+
+## **用户自定义检查项**
+
+1. 新增巡检项配置，修改script/gspylib/inspection/config/items.xml文件，格式如下：
+
+   ```xml
+   <checkitem id="10010" name="CheckCPU">
+        <title>
+            <zh>检查CPU占用率</zh>
+            <en>Check CPU Idle and I/O wait</en>
+        </title>
+        <threshold>
+            StandardCPUIdle=30;
+            StandardWIO=30
+        </threshold>
+        <suggestion>
+            <zh>如果idle不足 CPU负载过高，请扩容CPU节点，如果iowait过高，则磁盘为瓶颈，更换高性能磁盘</zh>
+        </suggestion>
+            <standard>
+                <zh>检查主机CPU占用率，如果idle大于30%并且iowait小于30%，则检查项通过，否则检查项不通过</zh>
+            </standard>
+        <category>os</category>
+        <permission>user</permission>
+        <scope>all</scope>
+        <analysis>default</analysis>
+   </checkitems>
+   ```
+
+   - id：巡检项id。
+
+   - name：巡检项脚本名， 和巡检项脚本文件名相同。
+
+   - title: 巡检项描述名称 （支持多语言）。
+
+     ：中文版检查内容。
+
+     ：英文版检查内容。
+
+   - standard：巡检项标准说明（支持多语言）。
+
+   - suggestion： 巡检项修复建议说明（支持多语言）。
+
+   - threshold：巡检项阈值定义，多值之间使用分号隔开，示例Key1=Value1;Key2=Value2。
+
+   - category： 巡检项分类，可选参数：os，device，network，cluster，database，other。
+
+   - permission： 巡检项需要的执行权限，可选参数：root，user默认为user（普通用户）。
+
+   - scope：巡检项执行的节点范围，可选参数：cn-仅在数据库主节点执行，local-仅在当前节点执行，all-在MogDB所有节点执行，默认为all。
+
+   - analysis：巡检项执行结果分析方式，default-检查每个节点的结果，所有节点检查项通过，则最终检查通过，consistent-MogDB内所有节点一致性检查，单节点仅返回结果，各个节点结果一致则判定检查通过，custom-自定义结果分析方式，默认为default。
+
+   注：用户需保证自定义xml的正确性
+
+2. 新建检查脚本，脚本名称格式遵循CheckXXXX.py，必须以Check开头，脚本放置在script/gspylib/inspection/items目录下，该目录下脚本安装巡检项分类组织，每个分类一个单独的文件夹，巡检项脚本放置在对应的分类文件夹中。格式如下：
+
+   ```
+   class CheckCPU（BaseItem):
+   def __init__（self):
+   super（CheckCPU, self).__init__（self.__class__.__name__)
+   self.idle = None
+   self.wio = None
+   self.standard = None
+
+   def preCheck（self):
+   # check the threshold was set correctly
+   if （not self.threshold.has_key（'StandardCPUIdle')
+   or not self.threshold.has_key（'StandardWIO')):
+   raise Exception（"threshold can not be empty")
+   self.idle = self.threshold['StandardCPUIdle']
+   self.wio = self.threshold['StandardWIO']
+
+   # format the standard by threshold
+   self.standard = self.standard.format（idle=self.idle, iowait=self.wio)
+
+   def doCheck（self):
+   cmd = "sar 1 5 2>&1"
+   output = SharedFuncs.runShellCmd（cmd)
+   self.result.raw = output
+   # check the result with threshold
+   d = next（n.split（) for n in output.splitlines（) if "Average" in n)
+   iowait = d[-3]
+   idle = d[-1]
+   rst = ResultStatus.OK
+   vals = []
+   if （iowait > self.wio):
+   rst = ResultStatus.NG
+   vals.append（"The %s actual value %s is greater than expected value %s" % （"IOWait", iowait, self.wio))
+   if （idle < self.idle):
+   rst = ResultStatus.NG
+   vals.append（"The %s actual value %s is less than expected value %s" % （"Idle", idle, self.idle))
+   self.result.rst = rst
+   if （vals):
+   self.result.val = "\n".join（vals)
+   ```
+
+   所有脚本基于BaseItem基类开发，基类定义的通用的检查流程，通用的检查结果分析方法，默认的结果输出格式。可扩展方法：
+
+   - doCheck: 该方法包含该检查项具体的检查方法，检查结果格式如下：
+
+     result.rst - 检查结果状态，可选参数:
+
+     - OK - 检查项完成，结果通过。
+     - NA - 当前节点不涉及该检查项。
+     - NG - 检查项完成，结果不通过。
+     - WARNING - 检查项完成，结果警告。
+     - ERROR - 检查项发生内部错误，未完成检查。
+
+   - preCheck: 检查前条件判定，内置两种实现：cnPreCheck - 用于检查当前执行节点是否包含数据库主节点实例，localPreCheck - 用于检查当前执行节点是否指定节点。可通过巡检项配置文件中的scope参数进行配置。 可重载该方法实现自定义的前置检查
+
+   - postAnalysis：检查结果分析方法，内置两种实现：default，consistent。可通过巡检项配置文件中的analysis参数进行配置。可重载该方法实现自定义的结果分析。
+
+   注：用户自定义的检查项名称不得与已有检查项名称相同，同时用户需保证自定义检查项脚本的规范性。
+
+3. 将此脚本分发至所有的执行节点。
+
+4. 以omm用户登录，执行以下命令，查看结果。
+
+   本地执行：
+
+   ```bash
+   gs_check -i CheckXXX  -L
+   ```
+
+   非本地执行：
+
+   ```bash
+   gs_check  -i  CheckXXX
+   ```
+
+## 操作系统参数
+
+**表 2** 操作系统参数
+
+| 参数名称                      | 参数说明                   | 推荐取值               |
+| :---------------------------- | :------------------------- | :--------------------- |
+| net.ipv4.tcp_max_tw_buckets   | 表示同时保持TIME_WAIT状态的TCP/IP连接最大数量。如果超过所配置的取值，TIME_WAIT将立刻被释放并打印警告信息。 | 10000                  |
+| net.ipv4.tcp_tw_reuse         | 允许将TIME-WAIT状态的sockets重新用于新的TCP连接。<br />- 0表示关闭。<br />- 1表示开启。 | 1                      |
+| net.ipv4.tcp_tw_recycle       | 表示开启TCP连接中TIME-WAIT状态sockets的快速回收。<br />- 0表示关闭。<br />- 1表示开启。 | 1                      |
+| net.ipv4.tcp_keepalive_time   | 表示当keepalive启用的时候，TCP发送keepalive消息的频度。      | 30                     |
+| net.ipv4.tcp_keepalive_probes | 在认定连接失效之前，发送TCP的keepalive探测包数量。这个值乘以tcp_keepalive_intvl之后决定了一个连接发送了keepalive之后可以有多少时间没有回应。 | 9                      |
+| net.ipv4.tcp_keepalive_intvl  | 当探测没有确认时，重新发送探测的频度。                       | 30                     |
+| net.ipv4.tcp_retries1         | 在连接建立过程中TCP协议最大重试次数。                        | 5                      |
+| net.ipv4.tcp_syn_retries      | TCP协议SYN报文最大重试次数。                                 | 5                      |
+| net.ipv4.tcp_synack_retries   | TCP协议SYN应答报文最大重试次数。                             | 5                      |
+| net.ipv4.tcp_retries2         | 控制内核向已经建立连接的远程主机重新发送数据的次数，低值可以更早的检测到与远程主机失效的连接，因此服务器可以更快的释放该连接。<br />发生“connection reset by peer”时可以尝试调大该值规避问题。 | 12                     |
+| vm.overcommit_memory          | 控制在做内存分配的时候，内核的检查方式。<br />- 0：表示系统会尽量精确计算当前可用的内存。<br />- 1：表示不作检查直接返回成功。<br />- 2：内存总量×vm.overcommit_ratio/100＋SWAP的总量，如果申请空间超过此数值则返回失败。<br />内核默认是2过于保守，推荐设置为0，如果系统压力大可以设置为1。 | 0                      |
+| net.ipv4.tcp_rmem             | TCP协议接收端缓冲区的可用内存大小。分无压力、有压力、和压力大三个区间，单位为页面。 | 8192 250000 16777216   |
+| net.ipv4.tcp_wmem             | TCP协议发送端缓冲区的可用内存大小。分无压力、有压力、和压力大三个区间，单位为页面。 | 8192 250000 16777216   |
+| net.core.wmem_max             | socket发送端缓冲区大小的最大值。                             | 21299200               |
+| net.core.rmem_max             | socket接收端缓冲区大小的最大值。                             | 21299200               |
+| net.core.wmem_default         | socket发送端缓冲区大小的默认值。                             | 21299200               |
+| net.core.rmem_default         | socket接收端缓冲区大小的默认值。                             | 21299200               |
+| net.ipv4.ip_local_port_range  | 物理机可用临时端口范围。                                     | 26000-65535            |
+| kernel.sem                    | 内核信号量参数设置大小。                                     | 250 6400000 1000 25600 |
+| vm.min_free_kbytes            | 保证物理内存有足够空闲空间，防止突发性换页。                 | 系统总内存的5%         |
+| net.core.somaxconn            | 定义了系统中每一个端口最大的监听队列的长度，这是个全局的参数。 | 65535                  |
+| net.ipv4.tcp_syncookies       | 当出现SYN等待队列溢出时，启用cookies来处理，可防范少量SYN攻击。<br />- 0表示关闭SYN Cookies。<br />- 1表示开启SYN Cookies。 | 1                      |
+| net.core.netdev_max_backlog   | 在每个网络接口接收数据包的速率比内核处理这些包的速率快时，允许送到队列的数据包的最大数目。 | 65535                  |
+| net.ipv4.tcp_max_syn_backlog  | 记录的那些尚未收到客户端确认信息的连接请求的最大值。         | 65535                  |
+| net.ipv4.tcp_fin_timeout      | 系统默认的超时时间。                                         | 60                     |
+| kernel.shmall                 | 内核可用的共享内存总量。                                     | 1152921504606846720    |
+| kernel.shmmax                 | 内核参数定义单个共享内存段的最大值。                         | 18446744073709551615   |
+| net.ipv4.tcp_sack             | 启用有选择的应答，通过有选择地应答乱序接受到的报文来提高性能，让发送者只发送丢失的报文段（对于广域网来说）这个选项应该启用，但是会增加对CPU的占用。<br />- 0表示关闭。<br />- 1表示开启。 | 1                      |
+| net.ipv4.tcp_timestamps       | TCP时间戳（会在TCP包头增加12节），以一种比重发超时更精确的方式（参考RFC 1323）来启用对RTT的计算，启用可以实现更好的性能。<br />- 0表示关闭。<br />- 1表示开启。 | 1                      |
+| vm.extfrag_threshold          | 系统内存不够用时，linux会为当前系统内存碎片情况打分，如果超过vm.extfrag_threshold的值，kswapd就会触发memory compaction。所以这个值设置的接近1000，说明系统在内存碎片的处理倾向于把旧的页换出，以符合申请的需要，而设置接近0，表示系统在内存碎片的处理倾向做memory compaction。 | 500                    |
+| vm.overcommit_ratio           | 系统使用绝不过量使用内存的算法时，系统整个内存地址空间不得超过swap+RAM值的此参数百分比，当vm.overcommit_memory=2时此参数生效。 | 90                     |
+| MTU                           | 节点网卡最大传输单元。OS默认值为1500，调整为8192可以提升SCTP协议数据收发的性能。 | 8192                   |
+
+## 文件系统参数
+
+- soft nofile
+
+  说明：soft nofile表示软限制，用户使用的文件句柄数量可以超过该限制，但是如果超过会有告警信息。
+
+  推荐取值：1000000
+
+- hard nofile
+
+  说明：hard nofile表示硬限制，是一个严格的限制，用户使用的文件句柄数量一定不能超过该设置。
+
+  推荐取值：1000000
+
+- stack size
+
+  说明：线程堆栈大小。
+
+  推荐值：3072
+
+## 示例
+
+执行单项检查结果：
+
+```bash
+perfadm@lfgp000700749:/opt/huawei/perfadm/tool/script> gs_check -i CheckCPU
+Parsing the check items config file successfully
+Distribute the context file to remote hosts successfully
+Start to health check for the cluster. Total Items:1 Nodes:3
+
+Checking...               [=========================] 1/1
+Start to analysis the check result
+CheckCPU....................................OK
+The item run on 3 nodes.  success: 3
+
+Success. All check items run completed. Total:1  Success:1  Failed:0
+For more information please refer to /opt/mogdb/tools/script/gspylib/inspection/output/CheckReport_201902193704661604.tar.gz
+```
+
+本地执行结果：
+
+```bash
+perfadm@lfgp000700749:/opt/huawei/perfadm/tool/script> gs_check -i CheckCPU -L
+
+2017-12-29 17:09:29 [NAM] CheckCPU
+2017-12-29 17:09:29 [STD] 检查主机CPU占用率，如果idle 大于30%并且iowait 小于 30%.则检查项通过，否则检查项不通过
+2017-12-29 17:09:29 [RST] OK
+
+2017-12-29 17:09:29 [RAW]
+Linux 4.4.21-69-default （lfgp000700749)  12/29/17  _x86_64_
+
+17:09:24        CPU     %user     %nice   %system   %iowait    %steal     %idle
+17:09:25        all      0.25      0.00      0.25      0.00      0.00     99.50
+17:09:26        all      0.25      0.00      0.13      0.00      0.00     99.62
+17:09:27        all      0.25      0.00      0.25      0.13      0.00     99.37
+17:09:28        all      0.38      0.00      0.25      0.00      0.13     99.25
+17:09:29        all      1.00      0.00      0.88      0.00      0.00     98.12
+Average:        all      0.43      0.00      0.35      0.03      0.03     99.17
+```
+
+执行场景检查结果：
+
+```bash
+[perfadm@SIA1000131072 Check]$ gs_check -e inspect
+Skip CheckHdfsForeignTabEncoding because it only applies to V1R5 upgrade V1R6 with cluster.
+Parsing the check items config file successfully
+The below items require root privileges to execute:[CheckBlockdev CheckIOConfigure CheckMTU CheckRXTX CheckMultiQueue CheckFirewall CheckSshdService CheckSshdConfig CheckCrondService CheckMaxProcMemory CheckBootItems CheckFilehandle CheckNICModel CheckDropCache]
+Please enter root privileges user[root]:
+Please enter password for user[root]:
+Check root password connection successfully
+Distribute the context file to remote hosts successfully
+Start to health check for the cluster. Total Items:57 Nodes:3
+Checking...               [=========================] 57/57
+Start to analysis the check result
+CheckClusterState...........................OK
+The item run on 3 nodes.  success: 3
+CheckDBParams...............................OK
+.........................................................................
+CheckMpprcFile..............................OK
+The item run on 3 nodes.  success: 3
+
+Analysis the check result successfully
+Failed. All check items run completed. Total:57   Success:49   Warning:5   NG:3   Error:0
+For more information please refer to /opt/huawei/wisequery/script/gspylib/inspection/output/CheckReport_inspect_201902207129254785.tar.gz
+```
+
+## 相关命令
+
+[gs_checkos]（2-gs_checkos)，[gs_checkperf]（3-gs_checkperf)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/10-gs_ssh.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/10-gs_ssh.md
new file mode 100644
index 0000000000000000000000000000000000000000..b4f904153788f73feab6f2b7adeb8923e9156901
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/10-gs_ssh.md
@@ -0,0 +1,76 @@
+---
+title: gs_ssh
+summary: gs_ssh
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_ssh
+
+## 背景信息
+
+MogDB提供了gs_ssh工具帮助用户在MogDB各节点上执行相同的命令。
+
+## 注意事项
+
+- gs_ssh只可以执行当前数据库用户有权限执行的命令。
+- gs_ssh所执行的命令不会对当前执行的会话产生影响，比如类似cd或source的命令，只会在执行的进程环境中产生影响，而不会影响到当前执行的会话环境。
+
+## 前提条件
+
+- 各个主机间互信正常。
+- MogDB已经正确安装部署。
+- 调用命令可用which查询到且在当前用户下有执行权限。
+- 需以操作系统用户omm执行gs_ssh命令。
+
+## 语法
+
+- 同步执行命令
+
+  ```bash
+  gs_ssh -c cmd
+  ```
+
+- 显示帮助信息
+
+  ```bash
+  gs_ssh -? | --help
+  ```
+
+- 显示版本号信息
+
+  ```bash
+  gs_ssh -V | --version
+  ```
+
+## 参数说明
+
+- -c
+
+  指定需要在MogDB各主机上执行的linux shell命令名。
+
+- -?, -help
+
+  显示帮助信息。
+
+- -V, -version
+
+  显示版本号信息。
+
+## 示例
+
+在MogDB各主机上执行相同命令。以执行”hostname”命令为例。
+
+```bash
+gs_ssh -c "hostname"
+Successfully execute command on all nodes.
+Output:
+[SUCCESS] plat1:
+plat1
+[SUCCESS] plat2:
+plat2
+[SUCCESS] plat3:
+plat3
+[SUCCESS] plat4:
+plat4
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/2-gs_checkos.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/2-gs_checkos.md
new file mode 100644
index 0000000000000000000000000000000000000000..3bdccb4015726b5b1cbc8c49214cfd8c10cb9869
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/2-gs_checkos.md
@@ -0,0 +1,221 @@
+---
+title: gs_checkos
+summary: gs_checkos
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_checkos
+
+## 背景信息
+
+gs_checkos工具用来帮助检查操作系统、控制参数、磁盘配置等内容，并对系统控制参数、I/O配置、网络配置和THP服务等信息进行配置。
+
+## 前提条件
+
+- 当前的硬件和网络环境正常。
+- 各主机间root互信状态正常。
+- 只能使用root用户执行gs_checkos命令。
+
+## 语法
+
+- 检查操作系统信息
+
+  ```bash
+  gs_checkos -i ITEM [-f HOSTFILE] [-h HOSTNAME] [-X XMLFILE] [--detail] [-o OUTPUT] [-l LOGFILE]
+  ```
+
+- 显示帮助信息
+
+  ```bash
+  gs_checkos -? | --help
+  ```
+
+- 显示版本号信息
+
+  ```bash
+  gs_checkos -V | --version
+  ```
+
+## 参数说明
+
+- -i
+
+  列表编号。格式：-i A、-i B1、-i A1 -i A2或-i A1,A2。
+
+  取值范围: A1…A14、B1…B8。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** A1…A14 表示只检查操作系统参数，并不设置。 B1…B8 表示将参数系统参数设置为期望值。 A和B不能同时输入。
+
+  详细的检查项请参见[表1](#gs_checkos)。
+
+- -f
+
+  主机名称列表文件。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** -f和-h参数不能同时使用。
+
+  取值范围: 主机名称的列表。
+
+- -h
+
+  指定需要检查的主机名称，可以同时指定多个主机，主机之间使用“,”分割。
+
+  取值范围: MogDB的主机名称。如果不指定主机，则检查当前主机。
+
+- -X
+
+  MogDBXML配置文件。
+
+- -detail
+
+  显示检查结果详情。
+
+- -o
+
+  指定OS检查报告输出到指定的文件。
+
+  不指定则将检查结果输出到屏幕上。
+
+- -l
+
+  指定日志文件及存放路径。
+
+  默认值：/tmp/gs_checkos/gs_checkos-YYYY-MM-DD_hhmmss.log。
+
+- -?, -help
+
+  显示帮助信息。
+
+- -V, -version
+
+  显示版本号信息。
+
+**表 1** 操作系统检查项 <a id="gs_checkos"> </a>
+
+| 编号 | 检查项                                                    | 检查项详细说明                                               |
+| :--- | :-------------------------------------------------------- | :----------------------------------------------------------- |
+| A1   | 操作系统版本（OS version status）                         | 操作系统版本检查：保证主机平台是支持的openEuler和CentOS平台中的一种。同时保证MogDB各个主机的平台是属于同一混编范围的。 |
+| A2   | 内核版本（Kernel version status）                         | 内核版本检查。                                               |
+| A3   | Unicode状态（Unicode status）                             | 字符集设置检查：保证MogDB各个主机的字符集一致。              |
+| A4   | 时区状态（Time zone status）                              | 时区时间设置检查：保证MogDB各个主机的时区状态一致。          |
+| A5   | 交换内存状态（Swap memory status）                        | Swap分区检查：各个主机的swap分区大小必须小于等于各主机内存总大小。 |
+| A6   | 系统控制参数（System control parameters status）          | 内核参数检查：保证当前内核中的参数值和默认的期望值保持一致。详细的内核参数请参见**操作系统参数**。 |
+| A7   | 文件系统配置状态（File system configuration status）      | 系统文件句柄检查：系统文件句柄的参数值必须大于等于100万。线程堆栈大小检查：线程堆栈大小大于等于3072KB。进程最大可用虚拟内存：系统进程最大可用虚拟内存为unlimited。 |
+| A8   | 磁盘配置状态（Disk configuration status）                 | 硬盘挂载参数检查：格式为xfs的硬盘，其挂载格式必须为：”rw,noatime,inode64,allocsize=16m”。 |
+| A9   | 预读块大小状态（Pre-read block size status）              | 预读参数检查：预读参数期望值为16384。                        |
+| A10  | IO调度状态（IO scheduler status）                         | IO调度策略检查：IO调度策略的方式为deadline。                 |
+| A11  | 网卡配置状态（Network card configuration status）         | 万兆以下网卡参数检查：确保网卡mtu=1500。万兆及以上网卡参数检查：当网卡为非绑定模式，同时网卡类型为万兆时，确保mtu=1500，rx/tx &gt;=4096。当网卡为绑定模式时，需保证绑定的每个网卡类型均为万兆，然后再确保mtu=1500，rx/tx&gt;=4096。MogDB周边设备（例如交换机等）的网卡也要设置成与MogDB部署的主机一致的值。 |
+| A12  | 时间一致性（Time consistency status）                     | 时间一致性检查：确认ntp服务启动，MogDB各个主机的系统时间误差不超过60s。 |
+| A13  | 防火墙状态（Firewall service status）                     | 防火墙检查： 确认防火墙的状态为关闭状态。                    |
+| A14  | THP服务（THP service status）                             | THP服务检查：确认THP服务状态为关闭状态。                     |
+| B1   | 设置系统控制参数（Set system control parameters）         | 内核参数设置：当实际值不满足检查条件期望时，对结果为Abnormal项参数进行修改设置；对Warning项不进行设置，由用户根据实际环境设置。 |
+| B2   | 设置文件系统配置值（Set file system configuration value） | 系统文件句柄设置：当系统文件句柄的参数值小于100万时，对其进行修改设置。线程堆栈大小设置：线程堆栈大小小于3072KB时，对其进行设置。进程最大可用虚拟内存设置：系统进程最大可用虚拟内存不为unlimited时对其进行修改设置。 |
+| B3   | 设置预读块大小值（Set pre-read block size value）         | 硬盘预读参数设置：当系统的实际值小于16384时，对其进行修改设置。 |
+| B4   | 设置IO调度值（Set IO scheduler value）                    | IO配置项的设置：当系统的实际值不为deadline时，对其进行修改设置。 |
+| B5   | 设置网卡配置值（Set network card configuration value）    | 万兆网卡参数设置：对不满足万兆网卡的RX、TX参数进行设置，不对MTU参数进行设置。 |
+| B6   | 设置THP服务（Set THP service）                            | THP服务设置：如果THP服务启动，将该服务关闭。                 |
+| B7   | 设置欧拉系统属性（Set RemoveIPC value）                   | 欧拉系统属性检查：检查设置欧拉系统文件/usr/lib/systemd/system/systemd-logind.service，/etc/systemd/logind.conf中配置项RemoveIPC属性值是否为no，当不为no时，对其进行修改设置。 |
+| B8   | 设置sshd服务应用pam模块（Set Session Process）            | 远程设备继承系统默认资源：修改/etc/pam.d/sshd服务文件，添加配置项session required pam_limits.so，来控制用户使用的资源。 |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - A6选项检查标准来自配置文件check_list.conf下[/etc/sysctl.conf]、[SUGGEST:/etc/sysctl.conf]域： 若[/etc/sysctl.conf]下参数值与系统实际参数值不同，A6检查提示Abnormal，可以使用B1参数进行设置。 若[SUGGEST:/etc/sysctl.conf]下参数值与系统实际参数值不同，A6检查提示Warning，B1参数不会进行设置，需根据实际情况进行手动设置。
+> - A7选项检查系统文件句柄标准来自配置文件check_list.conf下[/etc/security/limits.conf]域open file参数，可以使用B2参数进行设置。
+> - A11选项检查万兆网卡参数”MTU”、”RX”、”TX”标准来自配置文件check_list.conf下[/sbin/ifconfig]域，可以使用B5参数对RX、TX进行设置，MTU需用户手动设置。
+> - 使用gs_checkos设置的内核参数值和文件句柄参数值，需重启新会话生效。
+
+## 操作系统参数
+
+**表 2** 操作系统参数
+
+| 参数名称                      | 参数说明                  | 推荐取值               |
+| :---------------------------- | :------------------------ | :--------------------- |
+| net.ipv4.tcp_max_tw_buckets   | 表示同时保持TIME_WAIT状态的TCP/IP连接最大数量。如果超过所配置的取值，TIME_WAIT将立刻被释放并打印警告信息。 | 10000                  |
+| net.ipv4.tcp_tw_reuse         | 允许将TIME-WAIT状态的sockets重新用于新的TCP连接。<br />- 0表示关闭。<br />- 1表示开启。 | 1                      |
+| net.ipv4.tcp_tw_recycle       | 表示开启TCP连接中TIME-WAIT状态sockets的快速回收。<br />- 0表示关闭。<br />- 1表示开启。 | 1                      |
+| net.ipv4.tcp_keepalive_time   | 表示当keepalive启用的时候，TCP发送keepalive消息的频度。      | 30                     |
+| net.ipv4.tcp_keepalive_probes | 在认定连接失效之前，发送TCP的keepalive探测包数量。这个值乘以tcp_keepalive_intvl之后决定了一个连接发送了keepalive之后可以有多少时间没有回应。 | 9                      |
+| net.ipv4.tcp_keepalive_intvl  | 当探测没有确认时，重新发送探测的频度。                       | 30                     |
+| net.ipv4.tcp_retries1         | 在连接建立过程中TCP协议最大重试次数。                        | 5                      |
+| net.ipv4.tcp_syn_retries      | TCP协议SYN报文最大重试次数。                                 | 5                      |
+| net.ipv4.tcp_synack_retries   | TCP协议SYN应答报文最大重试次数。                             | 5                      |
+| net.ipv4.tcp_retries2         | 控制内核向已经建立连接的远程主机重新发送数据的次数，低值可以更早的检测到与远程主机失效的连接，因此服务器可以更快的释放该连接。发生“connection reset by peer”时可以尝试调大该值规避问题。 | 12                     |
+| vm.overcommit_memory          | 控制在做内存分配的时候，内核的检查方式。<br />- 0：表示系统会尽量精确计算当前可用的内存。<br />- 1：表示不作检查直接返回成功。<br />- 2：内存总量×vm.overcommit_ratio/100＋SWAP的总量，如果申请空间超过此数值则返回失败。<br />内核默认是2过于保守，推荐设置为0，如果系统压力大可以设置为1。 | 0                      |
+| net.ipv4.tcp_rmem             | TCP协议接收端缓冲区的可用内存大小。分无压力、有压力、和压力大三个区间，单位为页面。 | 8192 250000 16777216   |
+| net.ipv4.tcp_wmem             | TCP协议发送端缓冲区的可用内存大小。分无压力、有压力、和压力大三个区间，单位为页面。 | 8192 250000 16777216   |
+| net.core.wmem_max             | socket发送端缓冲区大小的最大值。                             | 21299200               |
+| net.core.rmem_max             | socket接收端缓冲区大小的最大值。                             | 21299200               |
+| net.core.wmem_default         | socket发送端缓冲区大小的默认值。                             | 21299200               |
+| net.core.rmem_default         | socket接收端缓冲区大小的默认值。                             | 21299200               |
+| net.ipv4.ip_local_port_range  | 物理机可用临时端口范围。                                     | 26000-65535            |
+| kernel.sem                    | 内核信号量参数设置大小。                                     | 250 6400000 1000 25600 |
+| vm.min_free_kbytes            | 保证物理内存有足够空闲空间，防止突发性换页。                 | 系统总内存的5%         |
+| net.core.somaxconn            | 定义了系统中每一个端口最大的监听队列的长度，这是个全局的参数。 | 65535                  |
+| net.ipv4.tcp_syncookies       | 当出现SYN等待队列溢出时，启用cookies来处理，可防范少量SYN攻击。<br />- 0表示关闭SYN Cookies。<br />- 1表示开启SYN Cookies。 | 1                      |
+| net.core.netdev_max_backlog   | 在每个网络接口接收数据包的速率比内核处理这些包的速率快时，允许送到队列的数据包的最大数目。 | 65535                  |
+| net.ipv4.tcp_max_syn_backlog  | 记录的那些尚未收到客户端确认信息的连接请求的最大值。         | 65535                  |
+| net.ipv4.tcp_fin_timeout      | 系统默认的超时时间。                                         | 60                     |
+| kernel.shmall                 | 内核可用的共享内存总量。                                     | 1152921504606846720    |
+| kernel.shmmax                 | 内核参数定义单个共享内存段的最大值。                         | 18446744073709551615   |
+| net.ipv4.tcp_sack             | 启用有选择的应答，通过有选择地应答乱序接受到的报文来提高性能，让发送者只发送丢失的报文段（对于广域网来说）这个选项应该启用，但是会增加对CPU的占用。<br />- 0表示关闭。<br />- 1表示开启。 | 1                      |
+| net.ipv4.tcp_timestamps       | TCP时间戳（会在TCP包头增加12节），以一种比重发超时更精确的方式（参考RFC 1323）来启用对RTT的计算，启用可以实现更好的性能。<br />- 0表示关闭。<br />- 1表示开启。 | 1                      |
+| vm.extfrag_threshold          | 系统内存不够用时，linux会为当前系统内存碎片情况打分，如果超过vm.extfrag_threshold的值，kswapd就会触发memory compaction。所以这个值设置的接近1000，说明系统在内存碎片的处理倾向于把旧的页换出，以符合申请的需要，而设置接近0，表示系统在内存碎片的处理倾向做memory compaction。 | 500                    |
+| vm.overcommit_ratio           | 系统使用绝不过量使用内存的算法时，系统整个内存地址空间不得超过swap+RAM值的此参数百分比，当vm.overcommit_memory=2时此参数生效。 | 90                     |
+| MTU                           | 节点网卡最大传输单元。OS默认值为1500，调整为8192可以提升SCTP协议数据收发的性能。 | 8192                   |
+
+## 文件系统参数
+
+- soft nofile
+
+  说明：soft nofile表示软限制，用户使用的文件句柄数量可以超过该限制，但是如果超过会有告警信息。
+
+  推荐取值：1000000
+
+- hard nofile
+
+  说明：hard nofile表示硬限制，是一个严格的限制，用户使用的文件句柄数量一定不能超过该设置。
+
+  推荐取值：1000000
+
+- stack size
+
+  说明：线程堆栈大小。
+
+  推荐值：3072
+
+## 示例
+
+使用如下命令检查操作系统参数。
+
+```bash
+gs_checkos -i A -h plat1 -X /opt/software/MogDB/clusterconfig.xml --detail -o /var/log/checkos
+Performing operation system check/set. Output the result to the file /var/log/checkos.
+Operation system check/set is completed.
+Total numbers:14. Abnormal numbers:0. Warning number:1.
+```
+
+查看操作系统参数检查结果。
+
+```bash
+vim /var/log/checkos
+Checking items:
+    A1. [ OS version status ]                                   : Normal
+    A2. [ MogDB version status ]                               : Normal
+    A3. [ Unicode status ]                                      : Normal
+    A4. [ Time zone status ]                                    : Normal
+    A5. [ Swap memory status ]                                  : Normal
+    A6. [ System control parameters status ]                    : Normal
+    A7. [ File system configuration status ]                    : Normal
+    A8. [ Disk configuration status ]                           : Normal
+    A9. [ Pre-read block size status ]                          : Normal
+    A10.[ IO scheduler status ]                                 : Normal
+    A11.[ Network card configuration status ]                   : Normal
+    A12.[ Time consistency status ]                             : Warning
+    A13.[ Firewall service status ]                             : Normal
+    A14.[ THP service status ]                                  : Normal
+```
+
+## 相关命令
+
+[gs_check](1-gs_check)，[gs_checkperf](3-gs_checkperf)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/3-gs_checkperf.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/3-gs_checkperf.md
new file mode 100644
index 0000000000000000000000000000000000000000..656b9a8fff56e4e7e2af6c48e71047f9aa2a844b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/3-gs_checkperf.md
@@ -0,0 +1,294 @@
+---
+title: gs_checkperf
+summary: gs_checkperf
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_checkperf
+
+## 背景信息
+
+MogDB提供了gs_checkperf工具来帮助对MogDB级别（主机CPU占用率、Gauss CPU占用率、I/O使用情况等）、节点级别（CPU使用情况、内存使用情况、I/O使用情况）、会话/进程级别（CPU使用情况、内存使用情况、I/O使用情况）、SSD性能（写入、读取性能）进行定期检查，让用户了解MogDB的负载情况，采取对应的改进措施。
+
+## 前提条件
+
+- MogDB运行状态正常且不为只读模式。
+- 运行在数据库之上的业务运行正常。
+
+## 注意事项
+
+- gs_checkperf工具的监控信息依赖于pmk模式下的表的数据。如果pmk模式下的表未执行analyze操作，则可能导致gs_checkperf工具执行失败。其报错示例信息如下。
+
+  ```
+  LOG:  Statistics in some tables or columns(pmk.pmk_snapshot.snapshot_id) are not collected.
+  HINT:  Do analyze for them in order to generate optimized plan.
+  ```
+
+  此时需要登录任一数据库主节点，连接postgres数据库执行如下SQL。
+
+  ```sql
+  analyze pmk.pmk_configuration;
+  analyze pmk.pmk_meta_data;
+  analyze pmk.pmk_snapshot;
+  analyze pmk.pmk_snapshot_dbnode_stat;
+  analyze pmk.pmk_snapshot_datanode_stat;
+  ```
+
+## 语法
+
+- 检查SSD性能（root用户）
+
+  ```bash
+  gs_checkperf -U USER [-o OUTPUT] -i SSD [-l LOGFILE]
+  ```
+
+- 检查MogDB性能（MogDB安装用户）
+
+  ```bash
+  gs_checkperf [-U USER] [-o OUTPUT] [-i PMK] [--detail] [-l LOGFILE]
+  ```
+
+- 显示帮助信息
+
+  ```bash
+  gs_checkperf -? | --help
+  ```
+
+- 显示版本号信息
+
+  ```bash
+  gs_checkperf -V | --version
+  ```
+
+## 参数说明
+
+- -U
+
+  运行MogDB的用户名称。
+
+  取值范围: 运行MogDB的用户名称。
+
+  以root用户身份执行此命令必须指定该参数。
+
+- -o
+
+  指定性能检查报告输出到指定的文件。
+
+  取值范围: 指定的文件名称。
+
+  不指定则将检查结果输出到屏幕上。
+
+- -i
+
+  指定检查项编号，-i参数值不区分大小写。格式：-i PMK、-i SSD。
+
+  取值范围: PMK、SSD
+
+  只有MogDB用户才能检查PMK选项。
+
+  只有root用户才能检查SSD选项。
+
+  如果不指定该参数，以MogDB用户身份默认检查PMK，以root用户身份默认检查SSD。
+
+- -detail
+
+  显示PMK检查结果详情。
+
+- -l
+
+  指定日志文件的存储路径。
+
+  默认路径为：/var/log/mogdb/omm/om/gs_checkperf-YYYY-MM-DD_hhmmss.log
+
+- -?, -help
+
+  显示帮助信息。
+
+- -V, -version
+
+  显示版本号信息。
+
+**表 1** 性能检查项
+
+| 分类                            | 性能参数项                                                   | 描述                                                         |
+| :------------------------------ | :----------------------------------------------------------- | :----------------------------------------------------------- |
+| MogDB级别                       | 主机CPU占用率                                                | 主机CPU占用率。                                              |
+| Gauss CPU占用率                 | Gauss CPU占用率。                                            |                                                              |
+| 共享内存击中率                  | 共享内存的击中率。                                           |                                                              |
+| 内存中排序比率                  | 内存中完成的排序所占比率。                                   |                                                              |
+| I/O使用情况                     | 文件读写次数和时间。                                         |                                                              |
+| 磁盘使用情况                    | 文件写次数和平均写时间、最大写时间等。                       |                                                              |
+| 事务统计                        | 当前SQL执行数和Session数。                                   |                                                              |
+| 节点级别                        | CPU使用情况                                                  | 主机使用CPU情况，包括cpu busy time，cpu idle time等。        |
+| 内存使用情况                    | 主机使用内存情况，包括物理内存总量，已使用量等。             |                                                              |
+| I/O使用情况                     | 文件读写次数和时间。                                         |                                                              |
+| 会话/进程级别                   | CPU使用情况                                                  | 会话使用CPU情况，包括cpu busy time，cpu idle time等。        |
+| 内存使用情况                    | 会话使用内存情况，包括物理内存总量，已使用量等。             |                                                              |
+| I/O使用情况                     | 会话共享缓冲区命中次数等。                                   |                                                              |
+| SSD性能（只用root用户才能查看） | 写入性能                                                     | 使用dd命令（flag=direct bs=8M count=2560）向每个SSD写入内容，写入每个SSD时间应在10s左右。 |
+| 读取性能                        | 使用dd命令（flag=direct bs=8M count=2560）从每个SSD读取内容，读取每个SSD时间应在7s左右。 |                                                              |
+
+## 示例
+
+示例一：以简要格式在屏幕上显示性能统计结果。
+
+```bash
+gs_checkperf -i pmk -U omm
+Cluster statistics information:
+    Host CPU busy time ratio                     :    1.43       %
+    MPPDB CPU time % in busy time              :    1.88       %
+    Shared Buffer Hit ratio                      :    99.96      %
+    In-memory sort ratio                         :    100.00     %
+    Physical Reads                               :    4
+    Physical Writes                              :    25
+    DB size                                      :    70         MB
+    Total Physical writes                        :    25
+    Active SQL count                             :    2
+    Session count                                :    3
+```
+
+示例二：以详细格式在屏幕上显示性能统计结果。
+
+```bash
+ gs_checkperf -i pmk -U omm --detail
+Cluster statistics information:
+Host CPU usage rate:
+    Host total CPU time                          :    42386.667  Jiffies
+    Host CPU busy time                           :    1873.333   Jiffies
+    Host CPU iowait time                         :    20.000     Jiffies
+    Host CPU busy time ratio                     :    4.42       %
+    Host CPU iowait time ratio                   :    .05        %
+MPPDB CPU usage rate:
+    MPPDB CPU time % in busy time              :    19.04      %
+    MPPDB CPU time % in total time             :    .84        %
+Shared buffer hit rate:
+    Shared Buffer Reads                          :    0
+    Shared Buffer Hits                           :    24129
+    Shared Buffer Hit ratio                      :    100.00     %
+    In-memory sort ratio                         :    100.00     %
+I/O usage:
+    Number of files                              :    537
+    Physical Reads                               :    0
+    Physical Writes                              :    0
+    Read Time                                    :    0          ms
+    Write Time                                   :    0          ms
+Disk usage:
+    DB size                                      :    70         MB
+    Total Physical writes                        :    0
+    Average Physical write                       :    0
+    Maximum Physical write                       :    0
+Activity statistics:
+    Active SQL count                             :    2
+    Session count                                :    3
+Node statistics information:
+dn_6001_6002:
+    MPPDB CPU Time                             :    200        Jiffies
+    Host CPU Busy Time                           :    3490       Jiffies
+    Host CPU Total Time                          :    42330      Jiffies
+    MPPDB CPU Time % in Busy Time              :    5.73       %
+    MPPDB CPU Time % in Total Time             :    .47        %
+    Physical memory                              :    8231776256 Bytes
+    DB Memory usage                              :    877236224  Bytes
+    Shared buffer size                           :    33554432   Bytes
+    Shared buffer hit ratio                      :    100.00     %
+    Sorts in memory                              :    123
+    Sorts in disk                                :    0
+    In-memory sort ratio                         :    100.00     %
+    Number of files                              :    149
+    Physical Reads                               :    0
+    Physical Writes                              :    0
+    Read Time                                    :    0
+    Write Time                                   :    0
+dn_6003_6004:
+    MPPDB CPU Time                             :    170
+    Jiffies    Host CPU Busy Time                :    1030       Jiffies
+    Host CPU Total Time                          :    42470      Jiffies
+    MPPDB CPU Time % in Busy Time              :    16.50      %
+    MPPDB CPU Time % in Total Time             :    .40        %
+    Physical memory                              :    8231776256 Bytes
+    DB Memory usage                              :    881434624  Bytes
+    Shared buffer size                           :    33554432   Bytes
+    Shared buffer hit ratio                      :    100.00     %
+    Sorts in memory                              :    119
+    Sorts in disk                                :    0
+    In-memory sort ratio                         :    100.00     %
+    Number of files                              :    165
+    Physical Reads                               :    0
+    Physical Writes                              :    0
+    Read Time                                    :    0
+    Write Time                                   :    0
+dn_6005_6006:
+    MPPDB CPU Time                             :    220        Jiffies
+    Host CPU Busy Time                           :    1100       Jiffies
+    Host CPU Total Time                          :    42360      Jiffies
+    MPPDB CPU Time % in Busy Time              :    20.00      %
+    MPPDB CPU Time % in Total Time             :    .52        %
+    Physical memory                              :    8231776256 Bytes
+    DB Memory usage                              :    881430528  Bytes
+    Shared buffer size                           :    33554432   Bytes
+    Shared buffer hit ratio                      :    100.00     %
+    Sorts in memory                              :    122
+    Sorts in disk                                :    0
+    In-memory sort ratio                         :    100.00     %
+    Number of files                              :    115
+    Physical Reads                               :    0
+    Physical Writes                              :    0
+    Read Time                                    :    0
+    Write Time                                   :    0
+Session statistics information(Top 10):
+Session CPU statistics:
+1 dn_6003_6004-postgres-dbazt:
+    Session CPU time                             :    1211
+    Database CPU time                            :    37670
+    Session CPU time %                           :    3.21       %
+2 dn_6005_6006-postgres-dbazt:
+    Session CPU time                             :    1204
+    Database CPU time                            :    35730
+    Session CPU time %                           :    3.37       %
+3 dn_6001_6002-postgres-dbazt:
+    Session CPU time                             :    1064
+    Database CPU time                            :    34120
+    Session CPU time %                           :    3.12       %
+
+Session Memory statistics:
+1 dn_6005_6006-postgres-dbazt:
+    Buffer Reads                                 :    8989
+    Shared Buffer Hit ratio                      :    96.97
+    In Memory sorts                              :    136
+    In Disk sorts                                :    0
+    In Memory sorts ratio                        :    100.00
+    Total Memory Size                            :    21593048
+    Used Memory Size                             :    18496600
+2 dn_6003_6004-postgres-dbazt:
+    Buffer Reads                                 :    9030
+    Shared Buffer Hit ratio                      :    96.94
+    In Memory sorts                              :    133
+    In Disk sorts                                :    0
+    In Memory sorts ratio                        :    100.00
+    Total Memory Size                            :    21576664
+    Used Memory Size                             :    18495688
+3 dn_6001_6002-postgres-dbazt:
+    Buffer Reads                                 :    8668
+    Shared Buffer Hit ratio                      :    96.97
+    In Memory sorts                              :    138
+    In Disk sorts                                :    0
+    In Memory sorts ratio                        :    100.00
+    Total Memory Size                            :    21258856
+    Used Memory Size                             :    18159736
+
+Session IO statistics:
+1 dn_6003_6004-postgres-dbazt:
+    Physical Reads                               :    285
+    Read Time                                    :    5320
+2 dn_6005_6006-postgres-dbazt:
+    Physical Reads                               :    281
+    Read Time                                    :    5811
+3 dn_6001_6002-postgres-dbazt:
+    Physical Reads                               :    271
+    Read Time                                    :    4662
+```
+
+## 相关命令
+
+[gs_check](1-gs_check)，[gs_checkos](2-gs_checkos)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/3.1-gs_clean.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/3.1-gs_clean.md
new file mode 100644
index 0000000000000000000000000000000000000000..3b6c37a6da57958fc077e52efad4de4da2f71af7
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/3.1-gs_clean.md
@@ -0,0 +1,100 @@
+---
+title: gs_clean
+summary: gs_clean
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_clean
+
+## 背景信息
+
+数据库异常宕机后可能会有临时表残留，gs_clean可以用来清理残留的临时表。
+
+## 语法
+
+连上主DN，清理主DN事务残留临时表。
+
+```bash
+gs_clean [OPTION ...] [USERNAME]
+```
+
+## 参数说明
+
+OPTION的取值如下所示：
+
+- -a, -all
+
+  清理所有可用数据库中残留的临时表。
+
+- -h, -host=HOSTADDRESS
+
+  目标DN所在主机的IP地址。
+
+  取值范围: 目标DN所在主机的IP地址。
+
+  默认值：localhost
+
+- -p, -port=PORT
+
+  主DN的端口号。
+
+  取值范围: 目标DN的端口号。
+
+  默认值：5432。如果已经设置了操作系统的环境变量PGPORT，则默认为PGPORT的值。
+
+- -q, -quiet
+
+  静态模式，除了错误信息，不打印任何其它信息。
+
+- -r, -rollback
+
+  回滚所有异常事务。
+
+- -t, -timeout=SECS
+
+  连接超时机制。
+
+  默认值：5s。单位：秒（s）。
+
+- -U, -username=USERNAME
+
+  连接数据库的用户名称。
+
+  取值范围: 数据库中有效的用户名称。
+
+  默认值：操作系统用户名称。
+
+- -v, -verbose
+
+  打印详细的恢复信息。
+
+- -V, -version
+
+  打印该工具的版本信息。
+
+- -w, -no-password
+
+  无需输入密码验证。
+
+- -W, -password=PASSWORD
+
+  需要输入密码验证。
+
+  取值范围: 有效字符串。符合密码复杂度要求。
+
+- -e, -exclusive
+
+  仅清理临时表。
+
+- -j, -jobs
+
+  清理两阶段残留文件的并发数。
+
+  取值范围: 1~10。
+
+  默认值：3。
+
+- -?, -help
+
+  打印帮助信息。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/4-gs_collector.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/4-gs_collector.md
new file mode 100644
index 0000000000000000000000000000000000000000..ef9b557a4ba1a0dec81ad9d2d5581ba89f0f482b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/4-gs_collector.md
@@ -0,0 +1,227 @@
+---
+title: gs_collector
+summary: gs_collector
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_collector
+
+## 背景信息
+
+当MogDB发生故障时，使用此工具收集OS信息、日志信息以及配置文件等信息，来定位问题。可以使用-C参数，指定收集不同的信息内容，具体支持收集的内容信息如[表1](#gs_collector)所示。
+
+**表 1** gs_collector内容收集对照表<a id="gs_collector"> </a>
+
+| TypeName | Content                   | 描述                    | 是否默认收集                        |
+| :------- | :------------------------ | :-----------------------| :-------------------------------- |
+| System   | HardWareInfoRunTimeInfo                                      | 收集现在操作系统的状态信息：<br />- HardWareInfo<br />- Cpu（cat /proc/cpuinfo）<br />- 内存（cat /proc/meminfo）<br />- 磁盘（df -h）<br />- RunTimeInfo：<br />- topStatus（ps ux）<br />- ioStat（iostat -xm 2 3）<br />- 网络状态（cat /proc/net/dev）<br />- 内存使用情况（free -m） | 是                                                           |
+| Database | 具体列表见表**工具支持收集的系统表和视图列表**。             | 收集系统视图或者系统表的内容。                               | 是，默认收集pg_locks，pg_stat_activity和 pg_thread_wait_status三个视图的信息。 |
+| Log      | DataNodeClusterManager                                       | 收集DataNode的pg_log和gs_profile<br />收集ClusterManager的日志信息包括：<br />- om<br />- gs_ctl<br />- gs_guc<br />- gs_initdb | 是                                                           |
+| Config   | DataNode                                                     | 收集DataNode的配置信息:<br />- postgresql.conf<br />- gaussdb.state<br />- pg_hba.conf<br />- pg_control<br />- pg_replslot<br />- pg_ident.conf | 是                                                           |
+| Gstack   | DataNode                               | 利用gstack命令得到DataNode的当前堆栈信息。         | 否                                   |
+| CoreDump | gs_ctl、gaussdb、GaussMaster、AioWorker、AlarmChecker、Archiver、Auditor、AutoVacLauncher、AutoVacWorker、AuxMain、BackendMode、BgWriter、BootStrap、Catchup、CBMWriter、Checkpointer、CommAuxStream、CommPoolCleane、CommRcvStream、CommRcvWorker、CommSendStream、CpMonitor、DataRcvWriter、DataReceiver、DataSender、ExtremeRTO、FencedUDFMaster、Heartbeater、JobExecutor、JobScheduler、LWLockMonitor、PageWriter、ParallelRecov、PercentileJob、Reaper、RemoteSrv、StartupProcess、StatCollector、Stream、SysLogger、ThdPoolListener、TwoPhaseCleaner、WalRcvWriter、WalReceiver、WalSender、WalWriter、WDRSnapshot、WlmArbiter、WlmCollector、WlmMonitor | 通过时间筛选gaussdb进程的core文件。<br />注意：<br />关于Core的配置和方式请按照如下要求：在/proc/sys/mogdb/core_pattern文件中添加core文件的格式：core-%e-%p-%t。 | 否                                                           |
+| XLog     | DataNode                             通过时间筛选收集xlog。                      | 否                           |
+| Plan     | *                  | 收集计划复现信息：<br />- 用户输入*表示收集所有数据库上的计划复现信息。<br />- 用户输入具体的数据库名称表示收集指定数据库上的计划复现信息。 | 否                                                           |
+
+## 前提条件
+
+日志收集工具依赖操作系统工具，例如gstack为其中一种，如果未安装该工具，则提示错误后，跳过该收集项。
+
+## 语法
+
+- 日志收集（非root用户）
+
+  ```bash
+  gs_collector --begin-time="BEGINTIME" --end-time="ENDTIME" [-h HOSTNAME | -f HOSTFILE] [--keyword=KEYWORD] [--speed-limit=SPEED] [-o OUTPUT] [-l LOGFILE] [-C CONFIGFILE]
+  ```
+
+- 显示帮助信息
+
+  ```bash
+  gs_collector -? | --help
+  ```
+
+- 显示版本号信息
+
+  ```bash
+  gs_collector -V | --version
+  ```
+
+## 参数说明
+
+- -h
+
+  收集信息的主机名称。
+
+  取值范围: 主机名称，如果不指定则默认收集所有主机的信息。
+
+- -f
+
+  主机名称列表文件。该文件为纯文本格式。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** -f和-h参数不能同时使用。
+
+  取值范围: 主机名称列表。
+
+- -o
+
+  将收集日志以压缩包形式输出到指定的文件夹。
+
+  不指定则将检查结果以压缩包形式输出到配置文件中tmpMppdbPath选项所指定的目录中。
+
+  若配置文件中未配置tmpMppdbPath选项，则默认将检查结果以压缩包形式输出到“/tmp/用户名_mppdb/”目录中。
+
+- -l
+
+  指定的日志文件以及存放路径。
+
+- -C
+
+  指定待收集内容的配置文件，利用TypeName指定需要收集的信息类型，利用Content指定每一类信息的具体内容，利用Count指定此类信息收集的次数，利用Interval指定收集间隔，单位为秒。
+
+  TypeName和Content不允许缺失或者内容为空。
+
+  Interval和Count可以不指定，如果没有指定Count，则默认收集一次。如果没有指定Interval则表示间隔为0秒，Interval和Count的值不能小于0。
+
+  如果不指定则使用默认的配置文件。
+
+  配置文件格式采用json格式，模板如下：
+
+    ```json
+    {
+        "Collect":
+        [
+            {"TypeName": "name", "Content":"value","Interval":"seconds", "Count":"count"}
+        ]
+    }
+    ```
+
+  ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+
+  TypeName和对应的Content取值范围见表1gs_collector内容收集对照表。 对于Log、CoreDump、Config和XLog四种类型，Interval和Count参数不生效。
+
+  默认配置文件内容如下：
+
+    ```json
+    {
+        "Collect":[
+            {"TypeName": "System", "Content":"RunTimeInfo, HardWareInfo","Interval":"0", "Count":"1"},
+            {"TypeName": "Log", "Content" : "DataNode,ClusterManager", "Interval":"0", "Count":"1"},
+            {"TypeName": "Database", "Content": "pg_locks,pg_stat_activity,pg_thread_wait_status","Interval":"0", "Count":"1"},
+            {"TypeName": "Config", "Content": "DataNode", "Interval":"0", "Count":"1"}
+        ]
+    }
+    ```
+
+- -keyword=KEYWORD
+
+  包含关键字KEYWORD的日志文件。
+
+  若关键字KEYWORD中含有空格，需要使用双引号包围。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 性能日志为二进制日志，关键字搜集功能不支持该日志的搜集。
+
+- -begin-time
+
+  日志的开始时间。输入格式为“yyyymmdd hh:mm”。
+
+- -end-time
+
+  日志的结束时间。输入格式为“yyyymmdd hh:mm”。
+
+- -speed-limit
+
+  日志收集时的收集速率，输入格式为非负整数，单位为MB/s。
+
+  该参数主要是为了防止日志收集过程中产生过高的磁盘或网络IO，导致数据库节点故障（如果它们与\$GAUSSLOG/$PGHOST部署在同一个磁盘上）。该值应当不超过MogDB内上述磁盘IO与网络IO速率的最小值的1/3。
+
+- -?, -help
+
+  显示帮助信息。
+
+- -V, -version
+
+  显示版本号信息。
+
+## 示例
+
+执行如下命令收集OS信息和日志信息。
+
+```bash
+gs_collector --begin-time="20180131 23:00" --end-time="20180201 20:00" -h plat1
+Successfully parsed the configuration file.
+create Dir.
+Successfully create dir.
+do system check interval 0 : count 1
+Collecting OS information.
+Successfully collected OS information.
+do database check interval 0 : count 1
+Collecting catalog statistics.
+Successfully collected catalog statistics.
+do log check interval 0 : count 1
+Collecting Log files.
+Successfully collected Log files.
+do Config check 0:1
+Collecting Config files.
+Successfully collected Config files.
+Collecting files.
+Successfully collected files.
+All results are stored in $PGHOST/collector_20200624_134541.tar.gz.
+```
+
+查看收集到的统计信息。
+
+```bash
+tar -zxvf $PGHOST/collector_20200624_134541.tar.gz
+collector_20200624_134541/
+collector_20200624_134541/plat1.tar.gz
+collector_20200624_134541/Detail.log
+collector_20200624_134541/Summary.log
+cd collector_20200624_134541
+tar -zxvf plat1.tar.gz
+plat1/
+plat1/catalogfiles/
+plat1/catalogfiles/gs_clean_20200624_134548283647.txt
+plat1/catalogfiles/dn_6001_pg_locks_20200624_134547746215.csv
+plat1/catalogfiles/dn_6001_pg_thread_wait_status_20200624_134548068716.csv
+plat1/catalogfiles/dn_6001_pg_stat_activity_20200624_134547851117.csv
+plat1/configfiles/
+plat1/logfiles/
+plat1/logfiles/log_20200624_134548540916.tar.gz
+plat1/coreDumpfiles/
+plat1/gstackfiles/
+plat1/systemfiles/
+plat1/systemfiles/OS_information_20200624_134542218134.txt
+plat1/systemfiles/database_system_info_20200624_134546282006.txt
+plat1/planSimulatorfiles/
+plat1/xlogfiles/
+cd plat1/logfiles/
+tar -zxvf log_20200624_134548540916.tar.gz
+./
+./om/
+./om/gs_preinstall-2020-06-24_113654.log
+./om/gs_local-2020-06-24_113710.log
+./om/gs_install-2020-06-24_113911.log
+./om/gs_checkperf-2020-06-24_114311.log
+./om/gs_collector-2020-06-24_114240.log
+./om/gs_backup-2020-06-24_114101.log
+./om/gs_om-2020-06-24_114052.log
+./bin/
+./bin/gs_initdb/
+./bin/gs_initdb/gs_initdb-2020-06-24_114010-current.log
+./bin/gs_guc/
+./bin/gs_guc/gs_guc-2020-06-24_114033-current.log
+./bin/gs_ctl/
+./bin/gs_ctl/gs_ctl-2020-06-24_114041-current.log
+./pg_log/
+./pg_log/dn_6001/
+./pg_log/dn_6001/postgresql-2020-06-24_114043.log
+./pg_log/dn_6001/postgresql-2020-06-24_114330.log
+./pg_log/dn_6001/postgresql-2020-06-24_114316.log
+./gs_profile/
+./gs_profile/dn_6001_6002/
+./gs_profile/dn_6001_6002/postgresql-2020-06-24_114330.prf
+./gs_profile/dn_6001_6002/postgresql-2020-06-24_114316.prf
+./gs_profile/dn_6001_6002/postgresql-2020-06-24_114043.prf
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/5-gs_dump.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/5-gs_dump.md
new file mode 100644
index 0000000000000000000000000000000000000000..b11ae09e90dccc89d95d7abbb8a6e5c6d629159c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/5-gs_dump.md
@@ -0,0 +1,551 @@
+---
+title: gs_dump
+summary: gs_dump
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_dump
+
+## 背景信息
+
+gs_dump是MogDB用于导出数据库相关信息的工具，用户可以自定义导出一个数据库或其中的对象（模式、表、视图等），回收站对象除外。支持导出的数据库可以是默认数据库postgres，也可以是自定义数据库。
+
+gs_dump工具由操作系统用户omm执行。
+
+gs_dump工具在进行数据导出时，其他用户可以访问MogDB数据库（读或写）。
+
+gs_dump工具支持导出完整一致的数据。例如，T1时刻启动gs_dump导出A数据库，那么导出数据结果将会是T1时刻A数据库的数据状态，T1时刻之后对A数据库的修改不会被导出。
+
+gs_dump时生成列不会被转储。
+
+gs_dump支持导出兼容v1版本数据库的文本格式文件。
+
+gs_dump支持将数据库信息导出至纯文本格式的SQL脚本文件或其他归档文件中。
+
+- 纯文本格式的SQL脚本文件：包含将数据库恢复为其保存时的状态所需的SQL语句。通过gsql运行该SQL脚本文件，可以恢复数据库。即使在其他主机和其他数据库产品上，只要对SQL脚本文件稍作修改，也可以用来重建数据库。
+- 归档格式文件：包含将数据库恢复为其保存时的状态所需的数据，可以是tar格式、目录归档格式或自定义归档格式，详见[表1](#daochuwenjian)。该导出结果必须与**gs_restore**配合使用来恢复数据库，gs_restore工具在导入时，系统允许用户选择需要导入的内容，甚至可以在导入之前对等待导入的内容进行排序。
+
+## 主要功能
+
+gs_dump可以创建四种不同的导出文件格式，通过“-F”或者“-format=”选项指定，具体如[表1](#daochuwenjian)所示。
+
+**表 1** 导出文件格式 <a id="daochuwenjian"> </a>
+
+| 格式名称       | -F的参数值 | 说明                                      | 建议                                   | 对应导入工具                                    |
+| :------------- | :--------- | :------------------------------------ | :------------------------------------- | :-------------------------------------------- |
+| 纯文本格式     | p          | 纯文本脚本文件包含SQL语句和命令。命令可以由gsql命令行终端程序执行，用于重新创建数据库对象并加载表数据。 | 小型数据库，一般推荐纯文本格式。       | 使用gsql工具恢复数据库对象前，可根据需要使用文本编辑器编辑纯文本导出文件。 |
+| 自定义归档格式 | c          | 一种二进制文件。支持从导出文件中恢复所有或所选数据库对象。   | 中型或大型数据库，推荐自定义归档格式。 | 使用**gs_restore**可以选择要从自定义归档导出文件中导入相应的数据库对象。 |
+| 目录归档格式   | d          | 该格式会创建一个目录，该目录包含两类文件，一类是目录文件，另一类是每个表和blob对象对应的数据文件。 | -                                      |                                                              |
+| tar归档格式    | t          | tar归档文件支持从导出文件中恢复所有或所选数据库对象。tar归档格式不支持压缩且对于单独表大小应小于8GB。 | -                                      |                                                              |
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 可以使用gs_dump程序将文件压缩为目录归档或自定义归档导出文件，减少导出文件的大小。生成目录归档或自定义归档导出文件时，默认进行中等级别的压缩。gs_dump程序无法压缩已归档导出文件。
+
+## 注意事项
+
+- 禁止修改导出的文件和内容，否则可能无法恢复成功。
+- 为了保证数据一致性和完整性，gs_dump会对需要转储的表设置共享锁。如果表在别的事务中设置了共享锁，gs_dump会等待锁释放后锁定表。如果无法在指定时间内锁定某个表，转储会失败。用户可以通过指定-lock-wait-timeout选项，自定义等待锁超时时间。
+- 不支持加密导出存储过程和函数。
+
+## 语法
+
+```bash
+gs_dump [OPTION]... [DBNAME]
+```
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** “dbname”前面不需要加短或长选项。“dbname”指定要连接的数据库。 例如： 不需要-d，直接指定“dbname”。
+
+```bash
+gs_dump -p port_number  postgres -f dump1.sql
+```
+
+或者
+
+```bash
+export PGDATABASE=postgres
+gs_dump -p port_number -f dump1.sql
+```
+
+环境变量： PGDATABASE
+
+## 参数说明
+
+通用参数：
+
+- -f, -file=FILENAME
+
+  将输出发送至指定文件或目录。如果省略该参数，则使用标准输出。如果输出格式为（-F c/-F d/-F t）时，必须指定-f参数。如果-f的参数值含有目录，要求当前用户对该目录具有读写权限，并且不能指定已有目录。
+
+- -F, -format=c|d|t|p
+
+  选择输出格式。格式如下：
+
+  - p|plain：输出一个文本SQL脚本文件（默认）。
+
+  - c|custom：输出一个自定义格式的归档，并且以目录形式输出，作为gs_restore输入信息。该格式是最灵活的输出格式，因为能手动选择，而且能在恢复过程中将归档项重新排序。该格式默认状态下会被压缩。
+
+  - d|directory：该格式会创建一个目录，该目录包含两类文件，一类是目录文件，另一类是每个表和blob对象对应的数据文件。
+
+  - t|tar：输出一个tar格式的归档形式，作为gs_restore输入信息。tar格式与目录格式兼容；tar格式归档形式在提取过程中会生成一个有效的目录格式归档形式。但是，tar格式不支持压缩且对于单独表有8GB的大小限制。此外，表数据项的相应排序在恢复过程中不能更改。
+
+    输出一个tar格式的归档形式，也可以作为gsql输入信息。
+
+- -v, -verbose
+
+  指定verbose模式。该选项将导致gs_dump向转储文件输出详细的对象注解和启动/停止次数，向标准错误流输出处理信息。
+
+- -V, -version
+
+  打印gs_dump版本，然后退出。
+
+- -Z, -compress=0-9
+
+  指定使用的压缩比级别。
+
+  取值范围: 0~9
+
+  - 0表示无压缩。
+  - 1表示压缩比最小，处理速度最快。
+  - 9表示压缩比最大，处理速度最慢。
+
+  针对自定义归档格式，该选项指定单个表数据片段的压缩，默认方式是以中等级别进行压缩。纯文本格式或tar归档格式目前不支持压缩。
+
+- -lock-wait-timeout=TIMEOUT
+
+  请勿在转储刚开始时一直等待以获取共享表锁。如果无法在指定时间内锁定某个表，就选择失败。可以以任何符合SET statement_timeout的格式指定超时时间。
+
+- -?, -help
+
+  显示gs_dump命令行参数帮助，然后退出。
+
+转储参数：
+
+- -a, -data-only
+
+  只输出数据，不输出模式（数据定义）。转储表数据、大对象和序列值。
+
+- -b, -blobs
+
+  该参数为扩展预留接口，不建议使用。
+
+- -c, -clean
+
+  在将创建数据库对象的指令输出到备份文件之前，先将清理（删除）数据库对象的指令输出到备份文件中。（如果目标数据库中没有任何对象，gs_restore工具可能会输出一些提示性的错误信息）
+
+  该选项只对文本格式有意义。针对归档格式，可以调用gs_restore时指定选项。
+
+- -C, -create
+
+  备份文件以创建数据库和连接到创建的数据库的命令开始。（如果命令脚本是这种方式执行，可以先指定任意数据库用于执行创建数据库的命令，数据不会恢复到指定的数据库中，而是恢复到创建的数据库中。）
+
+  该选项只对文本格式有意义。针对归档格式，可以在调用gs_restore时指定选项。
+
+- -E, -encoding=ENCODING
+
+  以指定的字符集编码创建转储。默认情况下，以数据库编码创建转储。（得到相同结果的另一个办法是将环境变量“PGCLIENTENCODING”设置为所需的转储编码。）
+
+- -n, -schema=SCHEMA
+
+  只转储与模式名称匹配的模式，此选项包括模式本身和所有它包含的对象。如果该选项没有指定，所有在目标数据库中的非系统模式将会被转储。写入多个-n选项来选择多个模式。此外，根据gsql的\d命令所使用的相同规则，模式参数可被理解成一个pattern，所以多个模式也可以通过在该pattern中写入通配符来选择。使用通配符时，注意给pattern打引号，防止shell扩展通配符。
+
+  ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+
+  - 当-n已指定时，gs_dump不会转储已选模式所附着的任何其他数据库对象。因此，无法保证某个指定模式的转储结果能够自行成功地储存到一个空数据库中。
+  - 当-n指定时，非模式对象不会被转储。
+
+  转储支持多个模式的转储。多次输入-n schemaname转储多个模式。
+
+  例如：
+
+  ```bash
+  gs_dump -h host_name -p port_number postgres -f backup/bkp_shl2.sql -n sch1 -n sch2
+  ```
+
+  在上面这个例子中，sch1和sch2会被转储。
+
+- -N, -exclude-schema=SCHEMA
+
+  不转储任何与模式pattern匹配的模式。pattern将参照针对-n的相同规则来理解。可以通过输入多次-N，不转储与任何pattern匹配的模式。
+
+  当同时输入-n和-N时，会转储与至少一个-n选项匹配、与-N选项不匹配的模式。如果有-N没有-n，则不转储常规转储中与-N匹配的模式。
+
+  转储过程支持排除多个模式。
+
+  在转储过程中，输入-N exclude schema name排除多个模式。
+
+  例如：
+
+  ```bash
+  gs_dump -h host_name -p port_number postgres -f backup/bkp_shl2.sql -N sch1 -N sch2
+  ```
+
+  在上面这个例子中，sch1和sch2在转储过程中会被排除。
+
+- -o, -oids
+
+  转储每个表的对象标识符（OIDs），作为表的一部分数据。该选项用于应用以某种方式参照了OID列的情况。如果不是以上这种情况，请勿使用该选项。
+
+- -O, -no-owner
+
+  不输出设置对象的归属这样的命令，以匹配原始数据库。默认情况下，gs_dump会发出ALTER OWNER或SET SESSION AUTHORIZATION语句设置所创建的数据库对象的归属。如果脚本正在运行，该语句不会执行成功，除非是由系统管理员触发（或是拥有脚本中所有对象的同一个用户）。通过指定-O，编写一个任何用户都能存储的脚本，且该脚本会授予该用户拥有所有对象的权限。
+
+  该选项只对文本格式有意义。针对归档格式，可以在调用gs_restore时指定选项。
+
+- -s, -schema-only <a id="schema-only"> </a>
+
+  只转储对象定义（模式），而非数据。
+
+- -S, -sysadmin=NAME
+
+  该参数为扩展预留接口，不建议使用。
+
+- -t, -table=TABLE
+
+  指定转储的表（或视图、或序列、或外表）对象列表，可以使用多个-t选项来选择多个表，也可以使用通配符指定多个表对象。
+
+  当使用通配符指定多个表对象时，注意给pattern打引号，防止shell扩展通配符。
+
+  当使用-t时，-n和-N没有任何效应，这是因为由-t选择的表的转储不受那些选项的影响。
+
+  ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+
+  - -t参数选项个数必须小于等于100。
+  - 如果-t参数选项个数大于100，建议使用参数-include-table-file来替换。
+  - 当-t已指定时，gs_dump不会转储已选表所附着的任何其他数据库对象。因此，无法保证某个指定表的转储结果能够自行成功地储存到一个空数据库中。
+  - -t tablename只转储在默认搜索路径中可见的表。-t '*.tablename'转储数据库下所有模式下的tablename表。-t schema.table转储特定模式中的表。
+  - -t tablename不会导出表上的触发器信息。
+
+  例如：
+
+  ```bash
+  gs_dump -h host_name -p port_number postgres -f backup/bkp_shl2.sql -t schema1.table1 -t schema2.table2
+  ```
+
+  在上面这个例子中，schema1.table1和schema2.table2会被转储。
+
+- -include-table-file=FILENAME
+
+  指定需要dump的表文件。
+
+- -T, -exclude-table=TABLE
+
+  不转储的表（或视图、或序列、或外表）对象列表，可以使用多个-T选项来选择多个表，也可以使用通配符指定多个表对象。
+
+  当同时输入-t和-T时，会转储在-t列表中，而不在-T列表中的表对象。
+
+  例如：
+
+  ```bash
+  gs_dump -h host_name -p port_number postgres -f backup/bkp_shl2.sql -T table1 -T table2
+  ```
+
+  在上面这个例子中，table1和table2在转储过程中会被排除。
+
+- -exclude-table-file=FILENAME
+
+  指定不需要dump的表文件。
+
+  ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 同-include-table-file，其内容格式如下： schema1.table1 schema2.table2 ……
+
+- -x, -no-privileges|-no-acl
+
+  防止转储访问权限（授权/撤销命令）。
+
+- -q, -target
+
+  指定导出兼容其他版本数据库的文本文件，目前支持v1和v5参数。v1参数用于导出v5数据库的数据为兼容v1的文本文件。v5参数用于导出v5数据库的数据为v5格式的文本文件，减少了导入v5时的可能的报错情况。
+
+  在使用v1参数时，建议和-exclude-guc=“enable_cluster_resize”、-exclude-function、-exclude-with等选项共用，否则导入到v1时可能报错。
+
+- -exclude-guc
+
+  导出的文本文件中，不包括相关guc参数的set命令，目前只支持enable_cluster_resize。
+
+- -exclude-function
+
+  不导出函数和存储过程。
+
+- -exclude-with
+
+  导出的表定义，末尾不添加WITH(orientation=row，compression=on）这样的描述。
+
+- -binary-upgrade
+
+  该参数为扩展预留接口，不建议使用。
+
+- -binary-upgrade-usermap=“USER1=USER2”
+
+  该参数为扩展预留接口，不建议使用。
+
+- -column-inserts|-attribute-inserts
+
+  以INSERT命令带列名（INSERT INTO表（列、…）值…）方式导出数据。这会导致恢复缓慢。但是由于该选项会针对每行生成一个独立分开的命令，所以在重新加载某行时出现的错误只会导致那行丢失，而非整个表内容。
+
+- -disable-dollar-quoting
+
+  该选项将禁止在函数体前使用美元符号$，并强制使用SQL标准字符串语法对其进行引用。
+
+- -disable-triggers
+
+  该参数为扩展预留接口，不建议使用。
+
+- -exclude-table-data=TABLE
+
+  指定不转储任何匹配表pattern的表这方面的数据。依照针对-t的相同规则理解该pattern。
+
+  可多次输入-exclude-table-data来排除匹配任何pattern的表。当用户需要特定表的定义但不需要其中的数据时，这个选项很有帮助。
+
+  排除数据库中所有表的数据，参见[-schema-only](#schema-only)。
+
+- -inserts
+
+  发出INSERT命令（而非COPY命令）转储数据。这会导致恢复缓慢。
+
+  但是由于该选项会针对每行生成一个独立分开的命令，所以在重新加载某行时出现的错误只会导致那行丢失，而非整个表内容。注意：如果重排列顺序，可能会导致整个恢复失败。列顺序改变时，-column-inserts选项不受影响，虽然会更慢。
+
+- -no-security-labels
+
+  该参数为扩展预留接口，不建议使用。
+
+- -no-tablespaces
+
+  不输出选择表空间的命令。使用该选项，无论默认表空间是哪个，在恢复过程中所有对象都会被创建。
+
+  该选项只对文本格式有意义。针对归档格式，可以在调用gs_restore时指定选项。
+
+- -no-unlogged-table-data
+
+  该参数为扩展预留接口，不建议使用。
+
+- -non-lock-table
+
+  该参数为扩展预留接口，不建议使用。
+
+- -include-alter-table
+
+  转储表删除列。该选项会记录列的删除。
+
+- -quote-all-identifiers
+
+  强制对所有标识符加引号。为了向后续版本迁移，且其中可能涉及引入额外关键词，在转储相应数据库时该选项会有帮助。
+
+- -section=SECTION
+
+  指定已转储的名称区段（pre-data、data和post-data）。
+
+- -serializable-deferrable
+
+  转储过程中使用可串行化事务，以确保所使用的快照与之后的数据库状态一致；要实现该操作需要在无异常状况的事务流中等待某个点，因为这样才能保证转储成功，避免引起其他事务出现serialization_failure要重新再做。
+
+  但是该选项对于灾难恢复没有益处。对于在原始数据库进行升级的时候，加载一个数据库的拷贝作为报告或其他只读加载共享的转储是有帮助的。没有这个选项，转储会反映一个与任何事务最终提交的序列化执行不一致的状态。
+
+  如果当gs_dump启动时，读写事务仍处于非活动状态，即便使用该选项也不会对其产生影响。如果读写事务处于活动状态，转储的开始时间可能会延迟一段不确定的时间。
+
+- -use-set-session-authorization
+
+  输出符合SQL标准的SET SESSION AUTHORIZATION命令而不是ALTER OWNER命令来确定对象所有权。这样令转储更加符合标准，但是如果转储文件中的对象的历史有些问题，那么可能不能正确恢复。并且，使用SET SESSION AUTHORIZATION的转储需要数据库系统管理员的权限才能转储成功，而ALTER OWNER需要的权限则低得多。
+
+- -with-encryption=AES128
+
+  指定转储数据需用AES128进行加密。
+
+- -with-key=KEY
+
+  AES128密钥长度规则如下：
+
+  - 密钥长度为8~16字符。
+
+  - 至少包含大写字母（A-Z）、小写字母（a-z）、数字（0-9）、非字母数字字符（限定为~!@#$%^&*()-_=+|[]{};:,&lt;.&gt;/?）四类字符中的三类字符。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+    >
+    > - 使用gs_dump工具进行加密导出时，仅支持plain格式导出。通过-F plain导出的数据，需要通过gsql工具进行导入，且如果以加密方式导入，在通过gsql导入时，需要指定-with-key参数。
+    > - 不支持加密导出存储过程和函数。
+
+- -with-salt=RANDVALUES
+
+  gs_dumpall使用此参数传递随机值。
+
+- -include-extension
+
+  在转储中包含扩展。
+
+- -include-depend-objs
+
+  备份结果包含依赖于指定对象的对象信息。该参数需要同-t/-include-table-file参数关联使用才会生效。
+
+- -exclude-self
+
+  备份结果不包含指定对象自身的信息。该参数需要同-t/-include-table-file参数关联使用才会生效。
+
+- -dont-overwrite-file
+
+  文本、tar、以及自定义格式情况下会重写现有文件。这对目录格式不适用。
+
+  例如：
+
+  设想这样一种情景，即当前目录下backup.sql已存在。如果在输入命令中输入-f backup.sql选项时，当前目录恰好也生成backup.sql，文件就会被重写。
+
+  如果备份文件已存在，且输入-dont-overwrite-file选项，则会报告附带‘转储文件已经存在’信息的错误。
+
+  ```bash
+  gs_dump -p port_number postgres -f backup.sql -F plain --dont-overwrite-file
+  ```
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+
+- -s/-schema-only和-a/-data-only不能同时使用。
+- -c/-clean和-a/-data-only不能同时使用。
+- -inserts/-column-inserts和-o/-oids不能同时使用，因为INSERT命令不能设置OIDS。
+- -role和-rolepassword必须一起使用。
+- -binary-upgrade-usermap和-binary-upgrade必须一起使用。
+- -include-depend-objs/-exclude-self需要同-t/-include-table-file参数关联使用才会生效。
+- -exclude-self必须同-include-depend-objs一起使用。
+
+连接参数：
+
+- -h, -host=HOSTNAME
+
+  指定主机名称。如果数值以斜杠开头，则被用作到Unix域套接字的路径。缺省从PGHOST环境变量中获取（如果已设置），否则，尝试一个Unix域套接字连接。
+
+  该参数只针对MogDB外，对MogDB内本机只能用127.0.0.1。
+
+  例如：主机名
+
+  环境变量：PGHOST
+
+- -p, -port=PORT
+
+  指定主机端口。在开启线程池情况下，建议使用 pooler port，即主机端口+1。
+
+  环境变量：PGPORT
+
+- -U, -username=NAME
+
+  指定所连接主机的用户名。
+
+  不指定连接主机的用户名时，用户默认系统管理员。
+
+  环境变量：PGUSER
+
+- -w, -no-password
+
+  不出现输入密码提示。如果主机要求密码认证并且密码没有通过其它形式给出，则连接尝试将会失败。 该选项在批量工作和不存在用户输入密码的脚本中很有帮助。
+
+- -W, -password=PASSWORD
+
+  指定用户连接的密码。如果主机的认证策略是trust，则不会对系统管理员进行密码验证，即无需输入-W选项；如果没有-W选项，并且不是系统管理员，“Dump Restore工具”会提示用户输入密码。
+
+- -role=ROLENAME
+
+  指定创建转储使用的角色名。选择该选项，会使gs_dump连接数据库后，发起一个SET ROLE角色名命令。当所授权用户（由-U指定）没有gs_dump要求的权限时，该选项会起到作用，即切换到具备相应权限的角色。某些安装操作规定不允许直接以超系统管理员身份登录，而使用该选项能够在不违反该规定的情况下完成转储。
+
+- -rolepassword=ROLEPASSWORD
+
+  指定角色名的密码。
+
+## 说明
+
+如果MogDB有任何本地数据要添加到template1数据库，请谨慎将gs_dump的输出恢复到一个真正的空数据库中，否则可能会因为被添加对象的定义被复制，出现错误。要创建一个无本地添加的空数据库，需从template0而非template1复制，例如：
+
+```sql
+CREATE DATABASE foo WITH TEMPLATE template0;
+```
+
+tar归档形式的文件大小不得超过8GB（tar文件格式的固有限制）。tar文档整体大小和任何其他输出格式没有限制，操作系统可能对此有要求。
+
+由gs_dump生成的转储文件不包含优化程序用来做执行计划决定的统计数据。因此，最好从某转储文件恢复之后运行ANALYZE以确保最佳效果。转储文件不包含任何ALTER DATABASE…SET命令，这些设置由gs_dumpall转储，还有数据库用户和其他完成安装设置。
+
+## 示例
+
+使用gs_dump转储数据库为SQL文本文件或其它格式的操作，如下所示。
+
+示例中“Bigdata@123”表示数据库用户密码；“backup/MPPDB_backup.sql”表示导出的文件，其中backup表示相对于当前目录的相对目录；“37300”表示数据库服务器端口；“postgres”表示要访问的数据库名。
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 导出操作时，请确保该目录存在并且当前的操作系统用户对其具有读写权限。
+
+示例1：执行gs_dump，导出postgres数据库全量信息，导出的MPPDB_backup.sql文件格式为纯文本格式。
+
+```bash
+gs_dump -U omm -W Bigdata@123 -f backup/MPPDB_backup.sql -p 37300 postgres -F p
+gs_dump[port='37300'][postgres][2018-06-27 09:49:17]: The total objects number is 356.
+gs_dump[port='37300'][postgres][2018-06-27 09:49:17]: [100.00%] 356 objects have been dumped.
+gs_dump[port='37300'][postgres][2018-06-27 09:49:17]: dump database postgres successfully
+gs_dump[port='37300'][postgres][2018-06-27 09:49:17]: total time: 1274  ms
+```
+
+使用gsql程序从纯文本导出文件中导入数据。
+
+示例2：执行gs_dump，导出postgres数据库全量信息，导出的MPPDB_backup.tar文件格式为tar格式。
+
+```bash
+gs_dump -U omm -W Bigdata@123 -f backup/MPPDB_backup.tar -p 37300 postgres -F t
+gs_dump[port='37300'][postgres][2018-06-27 10:02:24]: The total objects number is 1369.
+gs_dump[port='37300'][postgres][2018-06-27 10:02:53]: [100.00%] 1369 objects have been dumped.
+gs_dump[port='37300'][postgres][2018-06-27 10:02:53]: dump database postgres successfully
+gs_dump[port='37300'][postgres][2018-06-27 10:02:53]: total time: 50086  ms
+```
+
+示例3：执行gs_dump，导出postgres数据库全量信息，导出的MPPDB_backup.dmp文件格式为自定义归档格式。
+
+```bash
+gs_dump -U omm -W Bigdata@123 -f backup/MPPDB_backup.dmp -p 37300 postgres -F c
+gs_dump[port='37300'][postgres][2018-06-27 10:05:40]: The total objects number is 1369.
+gs_dump[port='37300'][postgres][2018-06-27 10:06:03]: [100.00%] 1369 objects have been dumped.
+gs_dump[port='37300'][postgres][2018-06-27 10:06:03]: dump database postgres successfully
+gs_dump[port='37300'][postgres][2018-06-27 10:06:03]: total time: 36620  ms
+```
+
+示例4：执行gs_dump，导出postgres数据库全量信息，导出的MPPDB_backup文件格式为目录格式。
+
+```bash
+gs_dump -U omm -W Bigdata@123 -f backup/MPPDB_backup -p 37300  postgres -F d
+gs_dump[port='37300'][postgres][2018-06-27 10:16:04]: The total objects number is 1369.
+gs_dump[port='37300'][postgres][2018-06-27 10:16:23]: [100.00%] 1369 objects have been dumped.
+gs_dump[port='37300'][postgres][2018-06-27 10:16:23]: dump database postgres successfully
+gs_dump[port='37300'][postgres][2018-06-27 10:16:23]: total time: 33977  ms
+```
+
+示例5：执行gs_dump，导出postgres数据库信息，但不导出/home/MPPDB_temp.sql中指定的表信息。导出的MPPDB_backup.sql文件格式为纯文本格式。
+
+```bash
+gs_dump -U omm -W Bigdata@123 -p 37300 postgres --exclude-table-file=/home/MPPDB_temp.sql -f backup/MPPDB_backup.sql
+gs_dump[port='37300'][postgres][2018-06-27 10:37:01]: The total objects number is 1367.
+gs_dump[port='37300'][postgres][2018-06-27 10:37:22]: [100.00%] 1367 objects have been dumped.
+gs_dump[port='37300'][postgres][2018-06-27 10:37:22]: dump database postgres successfully
+gs_dump[port='37300'][postgres][2018-06-27 10:37:22]: total time: 37017  ms
+```
+
+示例6：执行gs_dump，仅导出依赖于指定表testtable的视图信息。然后创建新的testtable表，再恢复依赖其上的视图。
+
+- 备份仅依赖于testtable的视图。
+
+  ```bash
+  gs_dump -s -p 37300 postgres -t PUBLIC.testtable --include-depend-objs --exclude-self -f backup/MPPDB_backup.sql -F p
+  gs_dump[port='37300'][postgres][2018-06-15 14:12:54]: The total objects number is 331.
+  gs_dump[port='37300'][postgres][2018-06-15 14:12:54]: [100.00%] 331 objects have been dumped.
+  gs_dump[port='37300'][postgres][2018-06-15 14:12:54]: dump database postgres successfully
+  gs_dump[port='37300'][postgres][2018-06-15 14:12:54]: total time: 327  ms
+  ```
+
+- 修改testtable名称。
+
+  ```bash
+  gsql -p 37300 postgres -r -c "ALTER TABLE PUBLIC.testtable RENAME TO testtable_bak;"
+  ```
+
+- 创建新的testtable表。
+
+  ```sql
+  CREATE TABLE PUBLIC.testtable(a int, b int, c int);
+  ```
+
+- 还原依赖于testtable的视图。
+
+  ```
+  gsql -p 37300 postgres -r -f backup/MPPDB_backup.sql
+  ```
+
+## 相关命令
+
+[gs_dumpall](6-gs_dumpall)，[gs_restore](9-gs_restore)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/6-gs_dumpall.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/6-gs_dumpall.md
new file mode 100644
index 0000000000000000000000000000000000000000..b6a82a586f474c67dc34d3744a4d5731308df7c5
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/6-gs_dumpall.md
@@ -0,0 +1,273 @@
+---
+title: gs_dumpall
+summary: gs_dumpall
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_dumpall
+
+## 背景信息
+
+gs_dumpall是MogDB用于导出所有数据库相关信息工具，它可以导出MogDB数据库的所有数据，包括默认数据库postgres的数据、自定义数据库的数据、以及MogDB所有数据库公共的全局对象。
+
+gs_dumpall工具由操作系统用户omm执行。
+
+gs_dumpall工具在进行数据导出时，其他用户可以访问MogDB数据库（读或写）。
+
+gs_dumpall工具支持导出完整一致的数据。例如，T1时刻启动gs_dumpall导出MogDB数据库，那么导出数据结果将会是T1时刻该MogDB数据库的数据状态，T1时刻之后对MogDB的修改不会被导出。
+
+gs_dumpall时生成列不会被转储。
+
+gs_dumpall在导出MogDB所有数据库时分为两部分：
+
+- gs_dumpall自身对所有数据库公共的全局对象进行导出，包括有关数据库用户和组，表空间以及属性（例如，适用于数据库整体的访问权限）信息。
+- gs_dumpall通过调用gs_dump来完成MogDB中各数据库的SQL脚本文件导出，该脚本文件包含将数据库恢复为其保存时的状态所需要的全部SQL语句。
+
+以上两部分导出的结果为纯文本格式的SQL脚本文件，使用gsql运行该脚本文件可以恢复MogDB数据库。
+
+## 注意事项
+
+- 禁止修改导出的文件和内容，否则可能无法恢复成功。
+- 为了保证数据一致性和完整性，gs_dumpall会对需要转储的表设置共享锁。如果某张表在别的事务中设置了共享锁，gs_dumpall会等待此表的锁释放后锁定此表。如果无法在指定时间内锁定某张表，转储会失败。用户可以通过指定-lock-wait-timeout选项，自定义等待锁超时时间。
+- 由于gs_dumpall读取所有数据库中的表，因此必须以MogDB管理员身份进行连接，才能导出完整文件。在使用gsql执行脚本文件导入时，同样需要管理员权限，以便添加用户和组，以及创建数据库。
+
+## 语法
+
+```bash
+gs_dumpall [OPTION]...
+```
+
+## 参数说明
+
+通用参数：
+
+- -f, -filename=FILENAME
+
+  将输出发送至指定文件。如果这里省略，则使用标准输出。
+
+- -v, -verbose
+
+  指定verbose模式。该选项将导致gs_dumpall向转储文件输出详细的对象注解和启动/停止次数，向标准错误流输出处理信息。
+
+- -V, -version
+
+  打印gs_dumpall版本，然后退出。
+
+- -lock-wait-timeout=TIMEOUT
+
+  请勿在转储刚开始时一直等待以获取共享表锁。如果无法在指定时间内锁定某个表，就选择失败。可以以任何符合SET statement_timeout的格式指定超时时间。
+
+- -?, -help
+
+  显示gs_dumpall命令行参数帮助，然后退出。
+
+转储参数：
+
+- -a, -data-only
+
+  只转储数据，不转储模式（数据定义）。
+
+- -c, -clean
+
+  在重新创建数据库之前，执行SQL语句清理（删除）这些数据库。针对角色和表空间的转储命令已添加。
+
+- -g, -globals-only
+
+  只转储全局对象（角色和表空间），无数据库。
+
+- -o, -oids
+
+  转储每个表的对象标识符（OIDs），作为表的一部分数据。该选项用于应用以某种方式参照了OID列的情况。如果不是以上这种情况，请勿使用该选项。
+
+- -O, -no-owner
+
+  不输出设置对象的归属这样的命令，以匹配原始数据库。默认情况下，gs_dumpall会发出ALTER OWNER或SET SESSION AUTHORIZATION语句设置所创建的模式元素的所属。如果脚本正在运行，该语句不会执行成功，除非是由系统管理员触发（或是拥有脚本中所有对象的同一个用户）。通过指定-O，编写一个任何用户都能存储的脚本，且该脚本会授予该用户拥有所有对象的权限。
+
+- -r, -roles-only
+
+  只转储角色，不转储数据库或表空间。
+
+- -s, -schema-only
+
+  只转储对象定义（模式），而非数据。
+
+- -S, -sysadmin=NAME
+
+  在转储过程中使用的系统管理员名称。
+
+- -t, -tablespaces-only
+
+  只转储表空间，不转储数据库或角色。
+
+- -x, -no-privileges
+
+  防止转储访问权限（授权/撤销命令）。
+
+- -column-inserts|-attribute-inserts
+
+  以INSERT命令带列名（INSERT INTO表（列、…）值…）方式导出数据。这会导致恢复缓慢。但是由于该选项会针对每行生成一个独立分开的命令，所以在重新加载某行时出现的错误只会导致那行丢失，而非整个表内容。
+
+- -disable-dollar-quoting
+
+  该选项将禁止在函数体前使用美元符号$，并强制使用SQL标准字符串语法对其进行引用。
+
+- -disable-triggers
+
+  该参数为扩展预留接口，不建议使用。
+
+- -inserts
+
+  发出INSERT命令（而非COPY命令）转储数据。这会导致恢复缓慢。注意：如果重排列顺序，可能会导致恢复整个失败。-column-inserts选项更加安全，虽然可能更慢些。
+
+- -no-security-labels
+
+  该参数为扩展预留接口，不建议使用。
+
+- -no-tablespaces
+
+  请勿输出创建表空间的命令，也请勿针对对象选择表空间。使用该选项，无论默认表空间是哪个，在恢复过程中所有对象都会被创建。
+
+- -no-unlogged-table-data
+
+  该参数为扩展预留接口，不建议使用。
+
+- -include-alter-table
+
+  导出表中已删除的列信息。
+
+- -quote-all-identifiers
+
+  强制对所有标识符加引号。为了向后续版本迁移，且其中可能涉及引入额外关键词，在转储相应数据库时该选项会有帮助。
+
+- -dont-overwrite-file
+
+  不重写当前文件。
+
+- -use-set-session-authorization
+
+  输出符合SQL标准的SET SESSION AUTHORIZATION命令而不是ALTER OWNER命令来确定对象所有权。这样令转储更加符合标准，但是如果转储文件中的对象的历史有些问题，那么可能不能正确恢复。并且，使用SET SESSION AUTHORIZATION的转储需要数据库系统管理员的权限才能转储成功，而ALTER OWNER需要的权限则低得多。
+
+- -with-encryption=AES128
+
+  指定转储数据需用AES128进行加密。
+
+- -with-key=KEY
+
+  AES128密钥长度规则如下：
+
+  - 密钥长度为8~16字符。
+  - 至少包含大写字母（A-Z）、小写字母（a-z）、数字（0-9）、非字母数字字符（限定为~!@#$%^&*()-_=+|[]{};:,&lt;.&gt;/?）四类字符中的三类字符。
+
+- -include-extension
+
+  如果-include-extension参数被设置，将备份所有的CREATE EXTENSION语句。
+
+- -include-templatedb
+
+  转储过程中包含模板库。
+
+- -binary-upgrade
+
+  该参数为扩展预留接口，不建议使用。
+
+- -binary-upgrade-usermap=“USER1=USER2”
+
+  该参数为扩展预留接口，不建议使用。
+
+- -non-lock-table
+
+  该参数仅供OM工具使用。
+
+- -tablespaces-postfix
+
+  该参数为扩展预留接口，不建议使用。
+
+- -parallel-jobs
+
+  指定备份进程并发数，取值范围为1~1000。
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+
+- -g/-globals-only和-r/-roles-only不能同时使用。
+- -g/-globals-only和-t/-tablespaces-only不能同时使用。
+- -r/-roles-only和-t/-tablespaces-only不能同时使用。
+- -s/-schema-only和-a/-data-only不能同时使用。
+- -r/-roles-only和-a/-data-only不能同时使用。
+- -t/-tablespaces-only和-a/-data-only不能同时使用。
+- -g/-globals-only和-a/-data-only不能同时使用。
+- -tablespaces-postfix和-binary-upgrade必须一起使用。
+- -binary-upgrade-usermap和-binary-upgrade必须一起使用。
+- -parallel-jobs和-f/-file必须一起使用。
+
+连接参数：
+
+- -h, -host
+
+  指定主机的名称。如果取值是以斜线开头，它将用作Unix域套接字的目录。默认值取自PGHOST环境变量；如果没有设置，将启动某个Unix域套接字建立连接。
+
+  该参数只针对MogDB外，对MogDB内本机只能用127.0.0.1。
+
+  环境变量：PGHOST
+
+- -l, -database
+
+  指定所连接的转储全局对象的数据库名称，并去寻找还有其他哪些数据库需要被转储。如果没有指定，会使用postgres数据库，如果postgres数据库不存在，会使用template1。
+
+- -p, -port
+
+  指定服务器所侦听的TCP端口或本地Unix域套接字后缀，以确保连接。默认值设置为PGPORT环境变量。
+
+  在开启线程池情况下，建议使用 pooler port，即侦听端口+1。
+
+  环境变量：PGPORT
+
+- -U, -username
+
+  所连接的用户名。
+
+  环境变量：PGUSER
+
+- -w, -no-password
+
+  不出现输入密码提示。如果服务器要求密码认证并且密码没有通过其它形式给出，则连接尝试将会失败。 该选项在批量工作和不存在用户输入密码的脚本中很有帮助。
+
+- -W, -password
+
+  指定用户连接的密码。如果主机的认证策略是trust，则不会对系统管理员进行密码验证，即无需输入-W选项；如果没有-W选项，并且不是系统管理员，“Dump Restore工具”会提示用户输入密码。
+
+- -role
+
+  指定创建转储使用的角色名。选择该选项，会使gs_dumpall连接数据库后，发起一个SET ROLE角色名命令。当所授权用户（由-U指定）没有gs_dumpall要求的权限时，该选项会起到作用，即切换到具备相应权限的角色。某些安装操作规定不允许直接以系统管理员身份登录，而使用该选项能够在不违反该规定的情况下完成转储。
+
+- -rolepassword
+
+  指定具体角色用户的角色密码。
+
+## 说明
+
+由于gs_dumpall内部调用gs_dump，所以一些诊断信息参见[gs_dump](5-gs_dump)。
+
+一旦恢复，最好在每个数据库上运行ANALYZE，优化程序提供有用的统计数据。
+
+gs_dumpall恢复前需要所有必要的表空间目录才能退出；否则，对于处在非默认位置的数据库，数据库创建会失败。
+
+## 示例
+
+使用gs_dumpall一次导出MogDB的所有数据库。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** gs_dumpall仅支持纯文本格式导出。所以只能使用gsql恢复gs_dumpall导出的转储内容。
+
+```bash
+gs_dumpall -f backup/bkp2.sql -p 37300
+gs_dump[port='37300'][dbname='postgres'][2018-06-27 09:55:09]: The total objects number is 2371.
+gs_dump[port='37300'][dbname='postgres'][2018-06-27 09:55:35]: [100.00%] 2371 objects have been dumped.
+gs_dump[port='37300'][dbname='postgres'][2018-06-27 09:55:46]: dump database dbname='postgres' successfully
+gs_dump[port='37300'][dbname='postgres'][2018-06-27 09:55:46]: total time: 55567  ms
+gs_dumpall[port='37300'][2018-06-27 09:55:46]: dumpall operation successful
+gs_dumpall[port='37300'][2018-06-27 09:55:46]: total time: 56088  ms
+```
+
+## 相关命令
+
+[gs_dump](5-gs_dump)，[gs_restore](9-gs_restore)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/7-gs_guc.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/7-gs_guc.md
new file mode 100644
index 0000000000000000000000000000000000000000..e60c6cbafc3c28474d99854a93ab988bc8ab2a45
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/7-gs_guc.md
@@ -0,0 +1,382 @@
+---
+title: gs_guc
+summary: gs_guc
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_guc
+
+## 背景信息
+
+目前MogDB配置文件（“postgresql.conf”、“pg_hba.conf”）中的参数默认值都是单机的配置模式。应用程序可以通过调用gs_guc来设置适合自己的参数。
+
+gs_guc工具由操作系统用户omm执行。
+
+- “gs_guc-current.log”
+
+  这个文件记录gs_guc产生的日志。
+
+  默认路径：$GAUSSLOG/bin/gs_guc。
+
+- “gs_guc-年-月-日_HHMMSS.log”
+
+  当“gs_guc-current.log”文件大小满16M后，会根据当前时刻生成一个备份文件。
+
+- “server.key.cipher”，“server.key.rand”
+
+  使用gs_guc encrypt命令加密用户密码时，如果指定的-M的值为server，则会生成这两个文件。其中“server.key.cipher”存储用户密码的密文，“server.key.rand”存储的是加密因子。
+
+- “client.key.cipher”，“client.key.rand”
+
+  使用gs_guc encrypt命令加密用户密码时，如果指定的-M的值为client，则会生成这两个文件。其中“client.key.cipher”存储用户密码的密文，“client.key.rand”存储的是加密因子。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** “client.key.cipher”和“client.key.rand”是不指定-U选项时生成的密文文件和加密因子文件。如果通过-U指定了用户名，则会生成以用户名开头的文件。以指定-U test为例，生成的文件名为:“test.key.cipher、test.key.rand”。
+
+- “datasource.key.cipher”，“datasource.key.rand”
+
+  使用gs_guc encrypt命令加密用户密码时，如果指定的-M的值为source，则会生成这两个文件。其中“datasource.key.cipher”存储用户密码的密文，“datasource.key.rand”存储的是加密因子。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  >
+  > - “datasource.key.cipher”和“datasource.key.rand”是创建Data Source对象时调用的密钥文件。gs_guc生成时即有读权限。使用前需将这两个文件放入各节点目录$GAUSSHOME/bin，且确保具有读权限。gs_ssh工具可以协助您快速将文件放入集群各节点对应目录下。
+  >
+  > - 此外，使用gs_guc generate命令也可以生成这两个文件，可以选择以下两种方式中的任一种，并根据提示输入密码。 方式1：gs_guc encrypt -M source -D ./ 方式2：gs_guc generate -o datasource -D ./
+
+## 语法
+
+- 检查配置文件中参数。
+
+  ```
+  gs_guc check [-N NODE-NAME] [-I INSTANCE-NAME | -D DATADIR] -c "parameter"
+  ```
+
+- 修改配置文件中参数。
+
+  ```
+  gs_guc set [-N NODE-NAME] [-I INSTANCE-NAME | -D DATADIR] -c "parameter = value"
+  ```
+
+- 将已设置的参数值修改为默认值。
+
+  ```
+  gs_guc [ set | reload ] [-N NODE-NAME] [-I INSTANCE-NAME | -D DATADIR] -c "parameter"
+  ```
+
+- 修改配置文件中参数，同时发送信号量到postgresql.conf。
+
+  ```
+  gs_guc reload [-N NODE-NAME] [-I INSTANCE-NAME | -D DATADIR] -c parameter=value
+  ```
+
+- 修改客户端认证策略。若选择reload会同时发送信号量到pg_hba.conf，即无需重启即可生效。
+
+  ```
+  gs_guc {set | reload} -Z NODE-TYPE [-N NODE-NAME] {-I INSTANCE-NAME | -D DATADIR} -h "HOSTTYPE DATABASE USERNAME IPADDR IPMASK AUTHMEHOD authentication-options"
+  gs_guc {set | reload} -Z NODE-TYPE [-N NODE-NAME] {-I INSTANCE-NAME | -D DATADIR} -h "HOSTTYPE DATABASE USERNAME IPADDR-WITH-IPMASK AUTHMEHOD authentication-options"
+  gs_guc {set | reload} -Z NODE-TYPE [-N NODE-NAME] {-I INSTANCE-NAME | -D DATADIR} -h "HOSTTYPE DATABASE USERNAME HOSTNAME AUTHMEHOD authentication-options"
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  >
+  > - AUTHMEHOD后的authentication-options为可选参数，AUTHMEHOD支持以下选项：
+  >
+  > - trust：不验密，禁止远程主机使用trust方式访问数据库。
+  > - reject：拒绝访问。
+  > - md5：md5认证，默认不支持（MD5加密算法安全性低，存在安全风险，不建议使用）。
+  > - sha256：sha256认证（推荐使用）。
+  > - cert：客户端证书认证。
+  > - gss：kerberos认证，仅用于内部节点间认证。
+  > - sm3：sm3认证（国密SM3）。
+  > - pg_hba.conf中的认证策略越靠前优先级越高，使用gs_guc工具配置时会按一定规则排序将新策略插入到原有认证策略中。配置字段比较顺序为：IPADDR/HOSTNAME &gt; HOSTTYPE &gt; DATABASE &gt; USERNAME，即优先比较IPADDR或HOSTNAME，如果无法区分优先级则继续比较HOSTTYPE，以此类推。对于每个配置字段，通常越严格的配置参数优先级越高、排序越靠前，越宽松的配置参数优先级越低、排序越靠后，具体如下：
+  >   - IPADDR：当配置为全0时表示不限制IP，会放在指定具体某个IP地址的策略后面。
+  >   - DATABASE：当配置为all时表示不限制数据库，会放在指定具体某个数据库的策略后面；当数据库配置为replication时会放在其他策略后面。
+  >   - USERNAME：当配置为all时表示不限制用户，会放在指定具体某个用户的策略后面。
+  >   - HOSTTYPE：local &gt; hostssl &gt; hostnossl &gt; host。
+
+- 注释已经设置的客户端认证策略。若选择reload会同时发送信号量到pg_hba.conf，即无需重启即可生效。
+
+  ```bash
+  gs_guc [ set | reload ] [-N NODE-NAME] [-I INSTANCE-NAME | -D DATADIR] -h "HOSTTYPE DATABASE USERNAME IPADDR-WITH-IPMASK AUTHMEHOD"
+  ```
+
+- 显示帮助信息。
+
+  ```bash
+  gs_guc -? | --help
+  ```
+
+- 显示版本号信息。
+
+  ```bash
+  gs_guc -V | --version
+  ```
+
+- gs_guc encrypt生成加密密码和加密因子文件。
+
+  ```bash
+  gs_guc encrypt [-M keymode] -K password [-U username] -D DATADIR
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  >
+  > - -K是用户指定的密码，gs_guc会对该密码进行长度（8&lt;=len&lt;=16）和密码复杂度要求，如果不满足，将会报错。此密码用于保证生成密码文件的安全性和唯一性，用户无需保存或记忆。
+  >
+  > - -M是加密类型，当前仅支持server、client和source。默认值为server。
+
+- gs_guc generate生成其他前缀的加密密码和加密因子文件。
+
+  ```bash
+  gs_guc generate [-o prefix] [-S cipherkey] -D DATADIR
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  >
+  > - -o是输出cipher和rand文件前缀名称，默认输出文件名前缀为obsserver。其内容仅支持数字、字母和下划线。
+  >
+  > - -S是用户指定的密码，密码需要满足长度要求（8&lt;=len&lt;=16）和复杂度要求，如不满足将会报错。当其值为default时，会随机生成一段字符串作为密码，该密码长度为13。如果不带-S参数则会提示交互式输入密码。为了系统安全，推荐使用交互式输入密码方式。
+  > - 使用gs_guc encrypt或generate命令生成加密密码和加密因子文件时只是参数不同，本质上是一样的。生成过程中会使用随机数作为加密密钥材料和盐值，因此是每次生成的文件都是不同的。每次生成的加密密码和加密因子文件需要成对使用，不能更换或交替使用，加密和解密时需要使用相同的加密密码和加密因子文件。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - gs_guc工具不支持参数值中包含'#'的设置。可以使用vi工具通过手工修改配置文件来设置。
+>
+> - 如果已经在环境变量中设置PGDATA，则可以省略-D参数。否则提示设置参数失败。
+> - 环境变量PGDATA设置方法：先将参数PGDATA设置为_/gaussdb/data_，然后在执行“export PGDATA”使设置生效。
+> - authpolicy包含一串认证参数：HOSTTYPE DATABASE USERNAME IPADDR IPMASK或者HOSTTYPE DATABASE USERNAME IPADDR-WITH-IPMASK或者HOSTTYPE DATABASE USERNAME HOSTNAME。
+> - 如果设置GUC参数时使用-c “parameter”，则会将已设置的GUC参数值设置成该参数的内核默认值（注意log_directory和audit_directory不会被设置为内核参数默认值，而是设为$GAUSSLOG/pg_audit/instance_name）。因GUC参数间存在依赖关系，因此请慎用该功能。
+> - 设置-c参数时，参数都可以省略双引号。
+> - 如果value中含有特殊字符（如$），请转义后使用。
+> - 如果同一个配置参数在配置文件里面出现多行，且有两行或多于两行同时生效（即没有用“#”注释掉），那么只有最后一个配置参数会被设置，而前面的都会被忽略。
+> - 通过reload模式设置或修改MogDB节点配置文件（postgresql.conf）的参数，生效存在短暂延迟，有可能导致配置后MogDB各实例参数极短时间不一致。
+
+## 命令参考
+
+- set
+
+  表示只修改配置文件中的参数。
+
+- check
+
+  表示只检查配置文件中的参数。
+
+- reload
+
+  表示修改配置文件中的参数，同时发送信号量给数据库进程，使其重新加载配置文件。
+
+- encrypt/generate
+
+  生成加密密码文件。
+
+- -N
+
+  需要设置的主机名称。
+
+  取值范围: 已有主机名称。
+
+  当参数取值为ALL时，表示设置MogDB中所有的主机。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 需依赖静态文件，仅在om安装的情况下有效，编译安装由于没有静态文件，所以无效。
+
+- -I INSTANCE-NAME
+
+  需要设置的实例名称。
+
+  取值范围: 已有实例名称。
+
+  当参数取值为ALL时，表示设置主机中所有的实例。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 需依赖静态文件，仅在om安装的情况下有效，编译安装由于没有静态文件，所以无效。
+
+- -D
+
+需要执行命令的MogDB实例路径。使用encrypt命令时，此参数表示指定的密码文件生成的路径。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 与“-I” 不能一块使用
+
+- -c parameter=value
+
+  要设定的MogDB配置参数的名称和参数值。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  >
+  > - 如果参数是一个字符串变量，则使用-c parameter=“'value'“或者使用-c “parameter = 'value'“。
+  >
+  > - 当使用gs_guc set/reload为“log_directory” 恢复默认值时，其默认值会被置为具体的data目录。
+  > - 当使用gs_guc reload进行参数设定，并指定-N参数时，当指定的节点为主节点时，主备节点的参数值都会被修改；当指定节点为备节点时，只会修改备节点的参数值，不会修改主节点的参数值。
+  > - 当使用gs_guc reload进行参数设定，未指定-N参数时，当在主节点上执行时，主备节点的参数值都会被修改；当在备节点上执行时，只会修改备节点的参数值，不会修改主节点的参数值。
+
+  取值范围: postgresql.conf中的所有参数。
+
+- -lcname=LCNAME
+
+  要设定的逻辑数据库名称。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  >
+  > - 该参数必需同-Z datanode一起使用。即gs_guc只允许作用于逻辑数据库的DN实例。
+  >
+  > - 逻辑数据库允许操作的参数同完整数据库不同。具体差异可参见$GAUSSHOME/bin/cluster_guc.conf。
+
+  取值范围: 已经创建的逻辑数据库名称。
+
+- -c parameter
+
+  当进行check操作时，表示需要检查的参数名称；当进行set/reload操作时，参数值不允许为空，为空时不会恢复为数据库参数的默认值。
+
+- -h host-auth-policy
+
+指定需要在“pg_hba.conf”增加的客户端认证策略。
+
+取值范围:
+
+- HOSTTYPE DATABASE USERNAME IPADDR IPMASK [authmehod-options]
+- HOSTTYPE DATABASE USERNAME IPADDR-WITH-IPMASK [authmehod-options ]
+- HOSTTYPE DATABASE USERNAME HOSTNAME [authmehod-options ]
+
+HOSTTYPE是必选参数，取值：
+
+- local
+- host
+- hostssl
+- hostnossl
+
+其中“local”是一个Unix域套接字，“host”是普通或SSL加密的TCP / IP套接字，“hostssl”是SSL加密的TCP / IP套接字，“hostnossl”是一个纯TCP / IP套接字。
+
+authmehod-options是可选输入，取值：
+
+- trust
+- reject
+- md5
+- sha256
+- sm3
+- cert
+- gss
+
+详细的参数说明请参见“pg_hba.conf”配置文件中的描述。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 指定-h的情况下，默认会尝试修改所有节点的pg_hba文件，但是如果是编译安装，由于没有静态文件，可以成功修改本节点的pg_hba文件，但是会提示静态文件不存在。
+
+- -?, -help
+
+  显示帮助信息。
+
+- -V, -version
+
+  显示版本信息。
+
+- -M, -keymode=MODE
+
+  设定该密码在数据库运行过程中，用于服务端(server)、客户端(client)还是创建Data Source对象时调用。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 在使用ssl功能时，会涉及到服务端证书和私钥文件的加密密码和客户端证书和私钥文件的加密密码，在加密存储加密密码时，需要指定模式，否则默认是生成服务端的密码文件。
+
+  取值范围:
+
+  - server（缺省）
+  - client
+  - source
+
+- -K PASSWORD
+
+  指定需要加密的密码。
+
+  取值范围: 字符串，符合密码复杂度的要求。
+
+- -U, -keyuser=USER
+
+  指定要加密的用户，隶属于OS用户。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** MogDB可以为每个用户配置不同的ssl证书和私钥文件，指定该选项，可以生成按用户名区分的密码文件。
+
+- -S CIPHERKEY
+
+  指定需要加密的字符串。
+
+  取值范围: 字符串。
+
+- -o PREFIX
+
+  指定需要输出的OBS类型的cipher和rand文件前缀名称字符串，默认输出文件名前缀为obsserver。
+
+  取值范围: 仅支持数字、字母和下划线。
+
+- -Z NODE-TYPE
+
+  指定数据库实例节点类型，参数默认值为datanode。NODE-TYPE用于识别配置文件。
+
+  取值范围: datanode。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 数据库实例节点类型有coordinator、datanode、cmserver、cmagent和gtm。MogDB只能取值为datanode，当NODE-TYPE为datanode时，对应数据库的数据目录中的配置文件postgresql.conf。
+
+## 示例
+
+示例1：修改数据库允许的最大连接数为800。修改后需要重启数据库才能生效。
+
+```bash
+gs_guc set -D /gaussdb/data/dbnode -c "max_connections = 800" -N plat1
+
+Total instances: 1. Failed instances: 0.
+Success to perform gs_guc!
+```
+
+示例2：将已设置的数据库允许的最大连接数值修改为默认值。修改后需要重启数据库才能生效。
+
+```bash
+gs_guc set -D /gaussdb/data/dbnode -c "max_connections" -N plat1
+
+Total instances: 1. Failed instances: 0.
+Success to perform gs_guc!
+```
+
+示例3：设置客户端认证策略。
+
+```bash
+gs_guc set -N all -I all -h "host replication testuser 10.252.95.191/32 sha256"
+
+Total instances: 2. Failed instances: 0.
+Success to perform gs_guc!
+```
+
+示例4：注释清理已经设置的客户端认证策略。
+
+```bash
+gs_guc set -N all -I all -h "host replication testuser 10.252.95.191/32"
+
+Total instances: 2. Failed instances: 0.
+Success to perform gs_guc!
+```
+
+示例5：加密服务器端存储用户密码的明文，避免密码泄露。
+
+```bash
+gs_guc encrypt -K Gauss@123 -D /data/xzg/wisequery/gaussdb
+gs_guc encrypt -K ***
+```
+
+示例6：检查MogDB中各个实例的参数配置情况。
+
+```bash
+gs_guc check -D /gaussdb/data/dbnode -c "max_connections" -N plat1
+
+Total GUC values: 1. Failed GUC values: 0.
+The value of parameter max_connections is same on all instances.
+    max_connections=800
+```
+
+示例7：修改archive_command归档命令，由用户自己保证归档路径的有效性。修改后需要重启数据库才能生效。推荐使用此方法。
+
+```bash
+gs_guc set -N all -D /data/datanode  -c "archive_command= 'cp %p /data/datanode/pg_xlog/archive_status/%f'"
+Total instances: 3. Failed instances: 0.
+Success to perform gs_guc!
+```
+
+示例8：通过用户输入的明文密码，生自定义的test.key.cipher和test.key.rand文件。
+
+```bash
+gs_guc generate -S Mppdb@123 -D data/xzg/wisequery/gaussdb -o test
+gs_guc encrypt -S ***
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/7.1-gs_encrypt.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/7.1-gs_encrypt.md
new file mode 100644
index 0000000000000000000000000000000000000000..404bffabbd8981c5c259d52d1bcead1b5e200a50
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/7.1-gs_encrypt.md
@@ -0,0 +1,106 @@
+---
+title: gs_encrypt
+summary: gs_encrypt
+author: Zhang Cuiping
+date: 2021-11-17
+---
+
+# gs_encrypt
+
+## 背景信息
+
+MogDB提供了gs_encrypt工具为输入的明文字符串进行加密操作。
+
+## 语法
+
+```bash
+gs_encrypt [OPTION]... PLAINTEXT
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - “PLAINTEXT”前不需要加短选项或长选项。
+>
+> - “PLAINTEXT”是需要加密的明文字符串。
+
+## 参数说明
+
+- -?, -help
+
+  显示帮助信息。
+
+- -V, -version
+
+  显示版本号信息。
+
+- -k _PASSWORD_， -key=*PASSWORD*
+
+  用户输入的口令，用于派生出加密操作时使用的密钥。口令长度有效范围为8~16个字符，并且至少包含大写字母、小写字母、数字和特殊字符中的三种字符。
+
+- -v _VectorValue_，-vector=*VectorValue*
+
+  用户输入的盐值，计算口令单向哈希时用于对口令进行加扰。字符串长度必须等于16。
+
+- -f *FilePrefix*, -file-prefix=*FilePrefix*
+
+  加密操作时使用的cipher和rand文件前缀字符串。cipher和rand文件必须存放在$GAUSSHOME/bin目录下。
+
+- -B _Value_，-key-base64=*Value*
+
+  加密时使用的明文密钥，以base64编码。
+
+- -D _Value_， -vector-base64=*Value*
+
+  加密时使用的随机数，以base64编码。base64编码前的字符串长度必须为16。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 出于安全考虑，建议用户在使用gs_encrypt工具前设置HISTCONTROL=ignorespace，强制不记录敏感历史命令，然后在执行gs_encrypt命令行前面加空格。
+
+## 示例
+
+示例1：通过输入key和vector明文值来对明文字符串进行加密操作。由于每次加密时使用的IV值是随机生成的，因此使用同样的key和vector以及明文字符串加密后对应的密文串不相同。单次支持加密的明文字符串最大长度为335字节。
+
+```bash
+gs_encrypt -k password@123 -v 1234567890123456 test_encrypt
+G0R7Y2oROfuiEjWtUBx9+eHP3I21A1wMOJ2onVQIiAsxMjM0NTY3ODkwMTIzNDU2
+```
+
+示例2：已经存在cipher和rand文件，通过文件前缀来对明文字符串进行加密操作。
+
+1. 生成cipher和rand文件。
+
+   ```bash
+   gs_guc generate -S Mppdb@123 -D $GAUSSHOME/bin -o test
+   gs_guc encrypt -S ***
+   ```
+
+2. 执行加密操作。
+
+   ```bash
+   gs_encrypt -f test test_encrypt
+   tSWpR8aFyF4GHVIVO7QNXhEMNlTcqRMrk172nAf2hLgSQwhcFWyP7X0QVS0SONon
+   ```
+
+示例3：通过输入base64加密后的key和vector密文来对明文字符串进行加密操作。
+
+1. 输入base64加密后的key。
+
+   ```bash
+   python
+   >>> import base64
+   >>> print base64.b64encode("XXXXXXXXX");
+   R2F1c3NAMTIz
+   ```
+
+2. 输入base64加密后vector密文。
+
+   ```python
+   >>> print base64.b64encode("1234567890abcdef");
+   MTIzNDU2Nzg5MGFiY2RlZg==
+   ```
+
+3. 执行加密操作。
+
+   ```bash
+   gs_encrypt -B R2F1c3NAMTIz -D MTIzNDU2Nzg5MGFiY2RlZg==  test_encrypt
+   V7mpnsfIHTjVTYGw1YHI0c6aY0N4J5L7BtU4CqDoeIkxMjM0NTY3ODkwYWJjZGVm
+   ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/8-gs_om.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/8-gs_om.md
new file mode 100644
index 0000000000000000000000000000000000000000..cd3a7257fd157e4092c8f49287df6fe4b94436ea
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/8-gs_om.md
@@ -0,0 +1,407 @@
+---
+title: gs_om
+summary: gs_om
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_om
+
+## 背景信息
+
+MogDB提供了gs_om工具帮助对MogDB进行维护，包括启动MogDB、停止MogDB、查询MogDB状态、查询静态配置、生成静态配置文件、查询MogDB状态详细信息、生成动态配置文件、SSL证书替换、显示帮助信息和显示版本号信息等功能。
+
+## 前提条件
+
+需以操作系统用户omm执行gs_om命令。
+
+## 语法
+
+- 启动MogDB
+
+  ```bash
+  gs_om -t start [-h HOSTNAME] [-D dataDir] [--time-out=SECS] [--security-mode=MODE] [-l LOGFILE]
+  ```
+
+- 停止MogDB
+
+  ```bash
+  gs_om -t stop [-h HOSTNAME] [-D dataDir]  [--time-out=SECS] [-m MODE] [-l LOGFILE]
+  ```
+
+- 重启MogDB
+
+  ```bash
+  gs_om -t restart [-h HOSTNAME] [-D dataDir] [--time-out=SECS] [--security-mode=MODE] [-l LOGFILE] [-m MODE]
+  ```
+
+- 查询MogDB状态
+
+  ```bash
+  gs_om -t status [-h HOSTNAME] [-o OUTPUT] [--detail] [--all] [-l LOGFILE]
+  ```
+
+- 生成静态配置文件
+
+  ```bash
+  gs_om -t generateconf -X XMLFILE [--distribute] [-l LOGFILE]
+  ```
+
+- 生成动态配置文件，备机failover或switchover成主机后，需要执行此操作
+
+  ```bash
+  gs_om -t refreshconf
+  ```
+
+- 查看静态配置
+
+  ```bash
+  gs_om -t view [-o OUTPUT]
+  ```
+
+- 查询MogDB状态详细信息
+
+  ```bash
+  gs_om -t query [-o OUTPUT]
+  ```
+
+- SSL证书替换
+
+  ```bash
+  gs_om -t cert --cert-file=CERTFILE [-l LOGFILE]
+  gs_om -t cert --rollback
+  ```
+
+- 开启、关闭数据库内kerberos认证
+
+  ```bash
+  gs_om -t kerberos -m [install|uninstall] -U USER [-l LOGFILE] [--krb-client|--krb-server]
+  ```
+
+- 显示帮助信息
+
+  ```bash
+  gs_om -? | --help
+  ```
+
+- 显示版本号信息
+
+  ```bash
+  gs_om -V | --version
+  ```
+
+## 参数说明
+
+gs_om参数可以分为如下几类：
+
+- 通用参数：
+
+  - -t
+
+    gs_om命令的类型。
+
+    取值范围: start、stop、status、generateconf、cert、view、query、refreshconf、kerberos。
+
+  - -l
+
+    指定日志文件及存放路径。
+
+    默认值：$GAUSSLOG/om/gs_om-YYYY-MM-DD_hhmmss.log（virtualip的默认值：/tmp/gs_virtualip/gs_om-YYYY-MM-DD_hhmmss.log）
+
+  - -?, -help
+
+    显示帮助信息。
+
+  - -V, -version
+
+    显示版本号信息。
+
+- 启动MogDB参数：
+
+  - -h
+
+    指定需要启动的服务器名称。一次只能启动一个服务器。
+
+    取值范围: 服务器名称。
+
+    不指定服务器名称时，表示启动MogDB。
+
+  - -D
+
+    指定 dn路径
+
+    取值范围: dn路径
+
+    不指定dn路径，表示使用静态文件中的dn路径
+
+  - -time-out=SECS
+
+    指定超时时间，如果超时，om脚本自动退出。单位：s。
+
+    取值范围: 正整数，建议值300。
+
+    默认值：300
+
+  - -security-mode
+
+    指定是否以安全模式启动数据库。
+
+    取值范围:
+
+    - on以安全模式启动。
+    - off不以安全模式启动，默认不开启安全模式。
+
+- 停止MogDB参数：
+
+  - -h
+
+    指定需要停止实例所在的服务器名称。一次只能停止一个服务器。
+
+    取值范围: 实例所在的服务器名称。
+
+    不指定服务器名称时，表示停止MogDB。
+
+  - -m, -mode=MODE
+
+    停止模式设置。
+
+    取值范围: 支持两种停止模式。
+
+    - fast方式：保证有主备关系的实例数据是一致的。
+    - immediate方式：不保证有主备关系的实例数据是一致的。
+
+    默认值：fast方式。
+
+  - -time-out=SECS
+
+    指定超时时间，如果超时，om脚本自动退出。单位：s。
+
+    取值范围: 正整数，建议值300。
+
+    默认值：300
+
+- 查询状态参数：
+
+    MogDB状态显示结果的参数说明请参见[表1](#zhuangtaishuom)。
+
+  - -h
+
+    指定需要待查询的服务器名称。
+
+    取值范围: 服务器名称。
+
+    不指定服务器时，表示查询MogDB。
+
+  - -az
+
+    指定需要查询的AZ名称，比如-az=AZ1。
+
+    取值范围: AZ名称，不指定AZ名称时，表示查询所有AZ。
+
+  - -o
+
+    输出到指定的output文件中。
+
+    如果不指定，直接显示在屏幕上。
+
+  - -detail
+
+    显示详细信息。如果不指定，只提示该服务器是否正常。
+
+    ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 本参数通过在每个数据库节点执行gs_ctl query命令进行查询并汇总结果，来获取MogDB的详细信息。
+
+  - -all
+
+    显示MogDB所有节点信息。
+
+    ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 本参数通过在每个数据库节点执行gsql查询系统表并汇总结果，来获取MogDB所有节点的信息。为保证显示信息的正确性，在使用本参数前请确认gsql可以查询。
+
+- 生成配置文件参数：
+
+  - -X
+
+    选择MogDB配置文件路径。
+
+    取值范围: clusterconfig.xml的路径。
+
+  - -distribute
+
+    将静态配置文件发布到MogDB实例的安装目录。
+
+  - 开启、关闭数据库内kerberos认证：
+
+  - -U
+
+    指定数据库部署用户。
+
+    取值范围: 数据库部署用户
+
+  - -m
+
+    指定所要进行的操作。
+
+    取值范围:
+
+    install：开启数据库内kerberos认证。
+
+    uninstall：关闭数据库内kerberos认证。
+
+  - -krb-server安装kerberos服务端认证。
+
+  - -krb-client安装kerberos客户端认证。
+
+    注：需要先安装-krb-server，卸载时同步卸载不需要该参数
+
+- SSL证书替换：
+
+  - -cert-file
+
+    指定本地SSL证书zip压缩包所在路径。
+
+  - -rollback
+
+    证书回退到上一次成功备份的状态。
+
+  - -L
+
+    制定该参数时，仅对当前节点进行。
+
+**表 1** 状态说明 <a id="zhuangtaishuom"> </a>
+
+| 字段           | 字段含义                                                     | 字段值                                                       |
+| :------------- | :----------------------------------------------------------- | :----------------------------------------------------------- |
+| cluster_state  | MogDB状态。显示MogDB是否运行正常。                           | - Normal：表示MogDB可用，且数据有冗余备份。所有进程都在运行，主备关系正常。<br />- Unavailable：表示MogDB不可用。<br />- Degraded：表示MogDB可用，但数据没有冗余备份。 |
+| redistributing | 数据重分布状态                                               | - Yes：表示MogDB处于数据重分布状态。<br />- No：表示MogDB未处于数据重分步状态。 |
+| balanced       | 平衡状态。显示是否有MogDB实例发生过主备切换而导致主机负载不均衡。 | - Yes：表示MogDB处于负载均衡状态。<br />- No：表示MogDB未处于负载均衡状态。 |
+| node           | 主机名称                                                     | 表示该实例所在的主机名称。多AZ时会显示AZ编号。               |
+| node_ip        | 主机IP                                                       | 表示该实例所在的主机IP。                                     |
+| instance       | 实例ID                                                       | 表示该实例的ID。                                             |
+| state          | 实例状态                                                     | - P: 节点的初始角色是Primary，数据库安装后就不再变动，从系统静态文件读取。<br />- S: 节点的初始角色是Standby，数据库安装后就不再变动，从系统静态文件读取。<br />- C: 节点的初始角色是Cascade Standby，数据库安装后就不再变动，从系统静态文件读取。<br />- Primary：表示实例为主实例。<br />- Standby：表示实例为备实例。<br />- Cascade Standby：表示实例为级联备实例。<br />- Secondary：表示实例为从备实例。<br />- Pending：表示该实例在仲裁阶段。<br />- Unknown：表示实例状态未知。<br />- Down：表示实例处于宕机状态。 |
+
+**表 2** 特性ID说明
+
+| 特性名称                   | 特性ID | MogDB产品         |
+| :------------------------- | :----- | :---------------- |
+| 多值列                     | 0      | 基础版            |
+| JSON                       | 1      | 不支持License控制 |
+| XML                        | 2      | 不支持            |
+| 数据存储格式ORC            | 3      | 基础版            |
+| 单机支持一主多备，备机可读 | 5      | 策略不放开        |
+| 多维碰撞分析GPU加速        | 7      | 高级特性          |
+| 全文索引                   | 8      | 基础版            |
+| EXTENSION_CONNECTOR        | 9      | 基础版            |
+| EXPRESS_CLUSTER            | 12     | 高级版            |
+| 跨DC协同                   | 13     | 高级版            |
+| 图                         | 14     | 不支持            |
+| 时序                       | 15     | 不支持            |
+| PostGis对接                | 16     | 基础版            |
+| MogDB内高可用-一主多备     | 17     | 策略不放开        |
+| 行级权限控制               | 18     | 高级版            |
+| 透明加密                   | 19     | 高级版            |
+| 私有表                     | 20     | 高级版            |
+
+## 示例
+
+- 启动MogDB。
+
+  ```bash
+  gs_om -t start
+  Starting cluster.
+  ======================================================================
+  .
+  ======================================================================
+
+  Successfully started .
+  ```
+
+- 停止MogDB。
+
+  ```bash
+  gs_om -t stop
+  Stopping cluster.
+  =========================================
+  Successfully stopped cluster.
+  =========================================
+  End stop cluster.
+  ```
+
+- 查看MogDB详细状态信息，含实例状态信息。
+
+  ```bash
+  gs_om -t status --detail
+
+  [   Cluster State   ]
+
+  cluster_state   : Normal
+  redistributing  : No
+  current_az      : AZ_ALL
+
+  [  Datanode State   ]
+
+      node             node_ip         port      instance                                   state
+  -----------------------------------------------------------------------------------------------------
+  1  pekpopgsci00235  10.244.62.204    5432      6001 /opt/gaussdb/cluster/data/dn1   P Primary Normal
+  2  pekpopgsci00238  10.244.61.81     5432      6002 /opt/gaussdb/cluster/data/dn1   S Standby Normal
+  ```
+
+- 在MogDB上执行如下命令，生成配置文件。
+
+  ```bash
+  gs_om -t generateconf -X  /opt/software/mogdb/clusterconfig.xml  --distribute
+  Generating static configuration files for all nodes.
+  Creating temp directory to store static configuration files.
+  Successfully created the temp directory.
+  Generating static configuration files.
+  Successfully generated static configuration files.
+  Static configuration files for all nodes are saved in /opt/mogdb/Bigdata/gaussdb/wisequery/script/static_config_files.
+  Distributing static configuration files to all nodes.
+  Successfully distributed static configuration files.
+  ```
+
+  然后打开生成的配置文件目录，会看到新生成的3个文件。
+
+  ```bash
+  cd /opt/mogdb/Bigdata/gaussdb/wisequery/script/static_config_files
+  ll
+  total 456
+  -rwxr-xr-x 1 omm dbgrp 155648 2016-07-13 15:51 cluster_static_config_plat1
+  -rwxr-xr-x 1 omm dbgrp 155648 2016-07-13 15:51 cluster_static_config_plat2
+  -rwxr-xr-x 1 omm dbgrp 155648 2016-07-13 15:51 cluster_static_config_plat3
+  ```
+
+- SSL证书回退。
+
+  ```bash
+  gs_om -t cert --rollback
+  [plat1] SSL cert files rollback successfully.
+  [plat2] SSL cert files rollback successfully.
+  [plat3] SSL cert files rollback successfully.
+  ```
+
+- 新License注册。
+
+  ```bash
+  gs_om -t license -m register -f MTgsMTkK
+  Preparing for the program initialization.
+  Lock the OPS operation of OM components.
+  Check and make sure the consistency of the license file.
+  Backup the license file on all of the cluster hosts.
+  Encrypt the product feature information and generate the license file.
+  Send message to the 数据库节点 instances to reload the license file.
+  Remove the backup license file on all of the cluster hosts.
+  License register successfully.
+  ```
+
+- 新License反注册。
+
+  ```bash
+  gs_om -t license -m unregister -f MTgsMTkK
+  Preparing for the program initialization.
+  Lock the OPS operation of OM components.
+  Check and make sure the consistency of the license file.
+  Backup the license file on all of the cluster hosts.
+  Encrypt the product feature information and generate the license file.
+  Send message to the 数据库节点 instances to reload the license file.
+  Remove the backup license file on all of the cluster hosts.
+  License unregister successfully.
+  ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/8.1-gs_plan_simulator.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/8.1-gs_plan_simulator.md
new file mode 100644
index 0000000000000000000000000000000000000000..eefa3c7ec64cd483fadd04f64cba65cb8a8ae874
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/8.1-gs_plan_simulator.md
@@ -0,0 +1,115 @@
+---
+title: gs_plan_simulator
+summary: gs_plan_simulator
+author: Zhang Cuiping
+date: 2021-11-17
+---
+
+# gs_plan_simulator
+
+## 背景信息
+
+某些用户的生产环境不允许维护人员进行任何问题定位和分析的操作，因此对于此类场景，唯一的手段就是将生产环境的各种数据收集后，依据这些数据对问题进行分析和定位。对于和执行计划相关的问题，gs_plan_simulator可以收集与执行计划相关的数据并能够在其它环境上进行执行计划的复现，从而定位执行计划类相关问题。
+
+## 前提条件
+
+- 用户数据库正常运行。
+- 用户可以连接到数据库并正常执行功能。
+- 用于复现的OS环境和生产环境应该一致。
+- 用于复现的环境安装的MogDB安装包应和生产环境的安装包一致。
+
+## 注意事项
+
+- 收集数据功能目前已经整合到工具gs_collector中，需要使用gs_collector收集相关数据，之后再使用gs_plan_simulator复现执行计划。
+- 使用gs_collector收集数据时默认不会收集与执行计划相关数据，因为收集该类数据可能会需要很长时间。收集执行计划相关数据需要修改配置文件，详情见使用步骤。
+- 在复现环境上需要配置GAUSSHOME和LD_LIBRARY_PATH。
+- 工具使用时需要注意集群状态，扩容状态等影响执行计划相关数据的情况下，勿使用此工具。
+
+## 使用步骤
+
+1. 使用gs_collector收集数据。收集执行计划相关数据时，需要先写配置文件，例如plan.json，建议配置文件内容如下：
+
+   ```
+   {
+   "Collect":
+    [
+        {"TypeName": "Plan", "Content": "*", "Interval":"0", "Count":"1"}
+    ]
+   }
+   ```
+
+   这里Content内容为“*”，用于收集所有数据库的相关数据，也可以指定数据库进行收集如“test1,test2”。
+
+   收集命令示例：
+
+   ```bash
+   gs_collector --begin-time="20191219 15:00" --end-time="20191219 15:15" -C ../plan.json -l plan.log -o ./
+   ```
+
+   更多使用方法见[gs_collector](4-gs_collector)一节。
+
+2. 拷贝数据文件夹到复现环境。
+
+   数据收集成功后，放在指定的压缩包内，解压压缩包会有各个节点的压缩包。解压任意一个压缩包，目标数据在planSimulatorfiles文件夹下，进入planSimulatorfiles文件夹可以看到以数据库命名的文件夹，拷贝planSimulatorfiles文件夹到复现环境。
+
+3. 复现环境的配置。
+
+   1. 使用普通用户创建用于复现执行计划的目录。例如plan文件夹。
+   2. 在该目录中解压GaussDB安装包，再解压安装包解压出来的bin文件。
+   3. 配置GAUSSHOME为plan文件夹的路径，配置LD_LIBRARY_PATH为plan/lib文件夹的路径。
+
+4. 使用gs_plan_simulator复现执行计划。
+
+   在复现环境上运行如下命令，复现命令示例：
+
+   ```
+   $GAUSSHOME/bin/gs_plan_simulator.sh -m restore -p 39000 -A planSimulatorfiles/
+   ```
+
+   该命令会在复现环境创建一个数据库，CN端口号为39000，同时会有信息提示如何连接数据库，进入数据库就可以执行explain+SQL语句进行问题定位。命令参数见参数说明。
+
+## 语法
+
+- 复现数据库环境。
+
+  ```bash
+  $GAUSSHOME/bin/gs_plan_simulator.sh -m OPTION -p PORT -A DATADIR
+  ```
+
+- 关闭数据库。
+
+  ```bash
+  $GAUSSHOME/bin/gs_plan_simulator.sh -m off
+  ```
+
+- 打开数据库。
+
+  ```bash
+  $GAUSSHOME/bin/gs_plan_simulator.sh -m start
+  ```
+
+- 显示帮助信息。
+
+  ```bash
+  $GAUSSHOME/bin/gs_plan_simulator.sh --help
+  ```
+
+## 参数说明
+
+- -m
+
+  工具的功能信息，表示工具要执行的操作。
+
+  取值范围:
+
+  - restore：利用收集的数据库信息来复现数据库环境，同时创建数据库。
+  - off：关闭已经存在的由该工具复现数据库。
+  - start：启动由该工具复现的数据库。
+
+- -p
+
+  创建数据库的CN端口。
+
+- -A
+
+  从用户环境拷贝的数据文件夹。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/9-gs_restore.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/9-gs_restore.md
new file mode 100644
index 0000000000000000000000000000000000000000..fd076ac3270e493ccb773c37d5fbcda1a471fdd9
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/server-tools/9-gs_restore.md
@@ -0,0 +1,383 @@
+---
+title: gs_restore
+summary: gs_restore
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_restore
+
+## 背景信息
+
+gs_restore是MogDB提供的针对gs_dump导出数据的导入工具。通过此工具可将由gs_dump生成的导出文件进行导入。
+
+gs_restore工具由操作系统用户omm执行。
+
+主要功能包含：
+
+- 导入到数据库
+
+  如果连接参数中指定了数据库，则数据将被导入到指定的数据库中。其中，并行导入必须指定连接的密码。导入时生成列会自动更新，并像普通列一样保存。
+
+- 导入到脚本文件
+
+  如果未指定导入数据库，则创建包含重建数据库所必须的SQL语句脚本并写入到文件或者标准输出。等效于直接使用gs_dump导出为纯文本格式。
+
+## 命令格式
+
+```bash
+gs_restore [OPTION]... FILE
+```
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+
+- FILE没有短选项或长选项。用来指定归档文件所处的位置。
+- 作为前提条件，需输入dbname或-l选项。不允许用户同时输入dbname和-l选项。
+- gs_restore默认是以追加的方式进行数据导入。为避免多次导入造成数据异常，在进行导入时，建议使用”-c” 参数，在重新创建数据库对象前，清理（删除）已存在于将要还原的数据库中的数据库对象。
+- 日志打印无开关，若需隐藏日志，请将日志重定向到日志文件。若恢复表数据时，数据量很大，会分批恢复，因此会多次出现“表数据已完成导入”的日志。
+
+## 参数说明
+
+通用参数：
+
+- -d, -dbname=NAME
+
+  连接数据库dbname并直接导入到该数据库中。
+
+- -f, -file=FILENAME
+
+  指定生成脚本的输出文件，或使用-l时列表的输出文件。
+
+  默认是标准输出。
+
+  ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+
+  -f不能同-d一起使用。
+
+- -F, -format=c|d|t
+
+  指定归档格式。由于gs_restore会自动决定格式，因此不需要指定格式。
+
+  取值范围:
+
+  - c/custom：该归档形式为gs_dump的自定义格式。
+  - d/directory：该归档形式是一个目录归档形式。
+  - t/tar：该归档形式是一个tar归档形式。
+
+- -l, -list
+
+  列出归档形式内容。这一操作的输出可用作-L选项的输入。注意如果像-n或-t的过滤选项与-l使用，过滤选项将会限制列举的项目（即归档形式内容）。
+
+- -v, -verbose
+
+  指定verbose模式。
+
+- -V, -version
+
+  打印gs_restore版本，然后退出。
+
+- -?, -help
+
+  显示gs_restore命令行参数帮助，然后退出。
+
+导入参数：
+
+- -a, -data-only
+
+  只导入数据，不导入模式（数据定义）。gs_restore的导入是以追加方式进行的。
+
+- -c, -clean
+
+  在重新创建数据库对象前，清理（删除）已存在于将要还原的数据库中的数据库对象。
+
+- -C, -create
+
+  导入到数据库之前会先使用CREATE DATABASE创建数据库（指定该选项后，-d指定的数据库仅用以执行CREATE DATABASE命令，所有数据将被导入到创建的数据库中）。
+
+- -e, -exit-on-error
+
+  当发送SQL语句到数据库时如果出现错误，请退出。默认状态下会继续，且在导入后会显示一系列错误信息。
+
+- -I, -index=NAME
+
+  只导入已列举的index的定义。允许导入多个index。如果多次输入-I index导入多个index。
+
+  例如：
+
+  ```bash
+  gs_restore -h host_name -p port_number -d postgres -I Index1 -I Index2 backup/MPPDB_backup.tar
+  ```
+
+  在上面这个例子中，Index1和Index2会被导入。
+
+- -j, -jobs=NUM
+
+  运行gs_restore最耗时的部分（如加载数据、创建index、或创建约束）使用并发任务。该选项能大幅缩短导入时间，即将一个大型数据库导入到某一多处理器的服务器上。
+
+  每个任务可能是一个进程或一个线程，这由操作系统决定；每个任务与服务器进行单独连接。
+
+  该选项的最优值取决于服务器的硬件设置、客户端、以及网络。还包括这些因素，如CPU核数量、硬盘设置。建议是从增加服务器上的CPU核数量入手，更大的值（服务器上CPU核数量）在很多情况下也能导致数据文件更快的被导入。当然，过高的值会由于超负荷反而导致性能降低。
+
+  该选项只支持自定义归档格式。输入文件必须是常规文件（不能是像pipe的文件）。如果是通过脚本文件，而非直接连接数据库服务器，该选项可忽略。而且，多任务不能与-single-transaction选项一起使用。
+
+- -L, -use-list=FILENAME
+
+  只导入列举在list-file中的那些归档形式元素，导入顺序以它们在文件中的顺序为准。注意如果像-n或-t的过滤选项与-L使用，它们将会进一步限制导入的项目。
+
+  一般情况下，list-file是通过编辑前面提到的某个-l参数的输出创建的。文件行的位置可更改或直接删除，也可使用分号（;）在行的开始注出。
+
+- -n, -schema=NAME
+
+  只导入已列举的模式中的对象。
+
+  该选项可与-t选项一起用以导入某个指定的表。
+
+  多次输入-n _schemaname_可以导入多个模式。
+
+  例如：
+
+  ```bash
+  gs_restore -h host_name -p port_number -d postgres -n sch1 -n sch2 backup/MPPDB_backup.tar
+  ```
+
+  在上面这个例子中，sch1和sch2会被导入。
+
+- -O, -no-owner
+
+  不输出设置对象的归属这样的命令，以匹配原始数据库。默认情况下，gs_restore会发出ALTER OWNER或SET SESSION AUTHORIZATION语句设置所创建的模式元素的所属。除非是由系统管理员（或是拥有脚本中所有对象的同一个用户）进行数据库首次连接的操作，否则语句会失败。使用-O选项，任何用户名都可用于首次连接，且该用户拥有所有已创建的对象。
+
+- -P, -function=NAME(args)
+
+  只导入已列举的函数。请按照函数所在转储文件中的目录，准确拼写函数名称和参数。
+
+  当-P单独使用时，表示导入文件中所有'function-name(args)'函数；当-P同-n一起使用时，表示导入指定模式下的'function-name(args)'函数；多次输入-P，而仅指定一次-n，表示所有导入的函数默认都是位于-n模式下的。
+
+  可以多次输入-n schema-name -P 'function-name(args)'同时导入多个指定模式下的函数。
+
+  例如：
+
+  ```bash
+  gs_restore -h host_name -p port_number -d postgres -n test1 -P 'Func1(integer)' -n test2 -P 'Func2(integer)' backup/MPPDB_backup.tar
+  ```
+
+  在上面这个例子中，test1模式下的函数Func1(i integer)和test2模式下的函数Func2(j integer)会被一起导入。
+
+- -s, -schema-only
+
+  只导入模式（数据定义），不导入数据（表内容）。当前的序列值也不会导入。
+
+- -S, -sysadmin=NAME
+
+  该参数为扩展预留接口，不建议使用。
+
+- -t, -table=NAME
+
+只导入已列举的表定义、数据或定义和数据。该选项与-n选项同时使用时，用来指定某个模式下的表对象。-n参数不输入时，默认为PUBLIC模式。多次输入-n -t 可以导入指定模式下的多个表。
+
+例如：
+
+导入PUBLIC模式下的table1
+
+```
+gs_restore -h host_name -p port_number -d postgres -t table1 backup/MPPDB_backup.tar
+```
+
+导入test1模式下的test1和test2模式下test2
+
+```bash
+gs_restore -h host_name -p port_number -d postgres -n test1 -t test1 -n test2 -t test2 backup/MPPDB_backup.tar
+```
+
+导入PUBLIC模式下的table1和test1 模式下table1
+
+```bash
+gs_restore -h host_name -p port_number -d postgres -n PUBLIC -t table1 -n test1 -t table1 backup/MPPDB_backup.tar
+```
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+
+-t参数不支持schema_name.table_name的输入格式。
+
+- -T, -trigger=NAME
+
+  该参数为扩展预留接口。
+
+- -x, -no-privileges/-no-acl
+
+  防止导入访问权限（grant/revoke命令）。
+
+- -1, -single-transaction
+
+  执行导入作为一个单独事务（即把命令包围在BEGIN/COMMIT中）。
+
+  该选项确保要么所有命令成功完成，要么没有改变应用。该选项意为-exit-on-error。
+
+- -disable-triggers
+
+  该参数为扩展预留接口，不建议使用。
+
+- -no-data-for-failed-tables
+
+  默认状态下，即使创建表的命令失败（如表已经存在），表数据仍会被导入。使用该选项，像这种表的数据会被跳过。如果目标数据库已包含想要的表内容，这种行为会有帮助。
+
+  该选项只有在直接导入到某数据库中时有效，不针对生成SQL脚本文件输出。
+
+- -no-security-labels
+
+  该参数为扩展预留接口，不建议使用。
+
+- -no-tablespaces
+
+  不输出选择表空间的命令。使用该选项，无论默认表空间是哪个，在导入过程中所有对象都会被创建。
+
+- -section=SECTION
+
+  导入已列举的区段（如pre-data、data、或post-data）。
+
+- -use-set-session-authorization
+
+  该选项用来进行文本格式的备份。
+
+  输出SET SESSION AUTHORIZATION命令，而非ALTER OWNER命令，用以决定对象归属。该选项使转储更加兼容标准，但通过参考转储中对象的记录，导入过程可能会有问题。使用SET SESSION AUTHORIZATION的转储要求必须是系统管理员，同时在导入前还需参考”SET SESSION AUTHORIZATION”，手工对导出文件的密码进行修改验证，只有这样才能进行正确的导入操作，相比之下，ALTER OWNER对权限要求较低。
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+
+- 如果安装过程中有任何本地数据要添加到template1数据库，请谨慎将gs_restore的输出载入到一个真正的空数据库中；否则可能会因为被添加对象的定义被复制，而出现错误。要创建一个无本地添加的空数据库，需从template0而非template1复制，例如：
+
+  ```
+  CREATE DATABASE foo WITH TEMPLATE template0;
+  ```
+
+- gs_restore不能选择性地导入大对象；例如只能导入那些指定表的对象。如果某个归档形式包含大对象，那所有大对象都会被导入，或一个都不会被导入，如果它们通过-L、-t或其他选项被排除。
+
+![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+
+1. -d/-dbname 和 -f/-file 不能同时使用；
+2. -s/-schema-only 和 -a/-data-only不能同时使用；
+3. -c/-clean 和 -a/-data-only不能同时使用；
+4. 使用-single-transaction时，-j/-jobs必须为单任务；
+5. -role 和 -rolepassword必须一起使用。
+
+连接参数：
+
+- -h, -host=HOSTNAME
+
+  指定的主机名称。如果取值是以斜线开头，他将用作Unix域套接字的目录。默认值取自PGHOST环境变量；如果没有设置，将启动某个Unix域套接字建立连接。
+
+  该参数只针对MogDB外，对MogDB内本机只能用127.0.0.1。
+
+- -p, -port=PORT
+
+  指定服务器所侦听的TCP端口或本地Unix域套接字后缀，以确保连接。默认值设置为PGPORT环境变量。
+
+  在开启线程池情况下，建议使用 pooler port，即侦听端口+1。
+
+- -U, -username=NAME
+
+  所连接的用户名。
+
+- -w, -no-password
+
+  不出现输入密码提示。如果服务器要求密码认证并且密码没有通过其它形式给出，则连接尝试将会失败。 该选项在批量工作和不存在用户输入密码的脚本中很有帮助。
+
+- -W, -password=PASSWORD
+
+  指定用户连接的密码。如果主机的认证策略是trust，则不会对系统管理员进行密码验证，即无需输入-W参数；如果没有-W参数，并且不是系统管理员，“gs_restore”会提示用户输入密码。
+
+- -role=ROLENAME
+
+  指定导入操作使用的角色名。选择该参数，会使gs_restore连接数据库后，发起一个SET ROLE角色名命令。当所授权用户（由-U指定）没有gs_restore要求的权限时，该参数会起到作用，即切换到具备相应权限的角色。某些安装操作规定不允许直接以初始用户身份登录，而使用该参数能够在不违反该规定的情况下完成导入。
+
+- -rolepassword=ROLEPASSWORD
+
+  指定具体角色用户的角色密码。
+
+## 示例
+
+特例：执行gsql程序，使用如下选项导入由gs_dump/gs_dumpall生成导出文件夹（纯文本格式）的MPPDB_backup.sql文件到postgres数据库。
+
+```bash
+gsql -d postgres -p 15400 -W Bigdata@123 -f /home/omm/test/MPPDB_backup.sql
+SET
+SET
+SET
+SET
+SET
+ALTER TABLE
+ALTER TABLE
+ALTER TABLE
+ALTER TABLE
+ALTER TABLE
+CREATE INDEX
+CREATE INDEX
+CREATE INDEX
+SET
+CREATE INDEX
+REVOKE
+REVOKE
+GRANT
+GRANT
+total time: 30476  ms
+```
+
+gs_restore用来导入由gs_dump生成的导出文件。
+
+示例1：执行gs_restore，将导出的MPPDB_backup.dmp文件（自定义归档格式）导入到postgres数据库。
+
+```bash
+gs_restore -W Bigdata@123 backup/MPPDB_backup.dmp -p 15400 -d postgres
+gs_restore: restore operation successful
+gs_restore: total time: 13053  ms
+```
+
+示例2：执行gs_restore，将导出的MPPDB_backup.tar文件（tar格式）导入到postgres数据库。
+
+```bash
+gs_restore backup/MPPDB_backup.tar -p 15400 -d postgres
+gs_restore[2017-07-21 19:16:26]: restore operation successful
+gs_restore[2017-07-21 19:16:26]: total time: 21203  ms
+```
+
+示例3：执行gs_restore，将导出的MPPDB_backup文件（目录格式）导入到postgres数据库。
+
+```bash
+gs_restore backup/MPPDB_backup -p 15400 -d postgres
+gs_restore[2017-07-21 19:16:26]: restore operation successful
+gs_restore[2017-07-21 19:16:26]: total time: 21003  ms
+```
+
+示例4：执行gs_restore，使用自定义归档格式的MPPDB_backup.dmp文件来进行如下导入操作。 导入PUBLIC模式下所有对象的定义和数据。在导入时会先删除已经存在的对象，如果原对象存在跨模式的依赖则需手工强制干预。
+
+```bash
+gs_restore backup/MPPDB_backup.dmp -p 15400 -d postgres -e -c -n PUBLIC
+gs_restore: [archiver (db)] Error while PROCESSING TOC:
+gs_restore: [archiver (db)] Error from TOC entry 313; 1259 337399 TABLE table1 gaussdba
+gs_restore: [archiver (db)] could not execute query: ERROR:  cannot drop table table1 because other objects depend on it
+DETAIL:  view t1.v1 depends on table table1
+HINT:  Use DROP ... CASCADE to drop the dependent objects too.
+    Command was: DROP TABLE public.table1;
+```
+
+手工删除依赖，导入完成后再重新创建。
+
+```bash
+gs_restore backup/MPPDB_backup.dmp -p 15400 -d postgres -e -c -n PUBLIC
+gs_restore[2017-07-21 19:16:26]: restore operation successful
+gs_restore[2017-07-21 19:16:26]: total time: 2203  ms
+```
+
+示例5：执行gs_restore，使用自定义归档格式的MPPDB_backup.dmp文件来进行如下导入操作。只导入PUBLIC模式下表table1的定义。
+
+```bash
+gs_restore backup/MPPDB_backup.dmp -p 15400 -d postgres -e -c -s -n PUBLIC -t table1
+gs_restore[2017-07-21 19:16:26]: restore operation successful
+gs_restore[2017-07-21 19:16:26]: total time: 21000  ms
+```
+
+示例6：执行gs_restore，使用自定义归档格式的MPPDB_backup.dmp文件来进行如下导入操作。只导入PUBLIC模式下表table1的数据。
+
+```bash
+gs_restore backup/MPPDB_backup.dmp -p 15400 -d postgres -e -a -n PUBLIC -t table1
+gs_restore[2017-07-21 19:16:26]: restore operation successful
+gs_restore[2017-07-21 19:16:26]: total time: 20203  ms
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/system-catalogs-and-views-supported-by-gs_collector.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/system-catalogs-and-views-supported-by-gs_collector.md
new file mode 100644
index 0000000000000000000000000000000000000000..065ae36e36a60dcd61c88c532c5e8d8d6538fe62
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/system-catalogs-and-views-supported-by-gs_collector.md
@@ -0,0 +1,455 @@
+---
+title: gs_collector工具支持收集的系统表和视图列表
+summary: gs_collector工具支持收集的系统表和视图列表
+author: Zhang Cuiping
+date: 2021-11-17
+---
+
+# gs_collector工具支持收集的系统表和视图列表
+
+- OS
+  - gs_os_run_info
+  - pg_os_threads
+- Session/Thread
+  - gs_session_stat
+  - gs_session_time
+  - gs_session_cpu_statistics
+  - gs_session_memory_statistics
+  - gs_session_memory_context
+  - gs_session_memory
+  - gs_session_memory_detail
+  - pg_stat_activity
+  - gs_thread_memory_context
+- WLM
+  - gs_cluster_resource_info
+  - pg_total_user_resource_info
+  - pg_total_user_resource_info_oid
+  - gs_wlm_rebuild_user_resource_pool
+  - gs_wlm_resource_pool
+  - gs_wlm_workload_records
+  - pg_wlm_statistics
+  - pg_app_workloadgroup_mapping
+- Query-AP Operator
+  - gs_wlm_operator_info
+  - gs_wlm_operator_history
+  - gs_wlm_operator_statistics
+- Query-AP
+  - gs_wlm_session_info_all
+  - gs_wlm_session_history
+  - gs_wlm_session_info
+  - gs_wlm_user_session_info
+  - gs_wlm_session_statistics
+  - pg_session_iostat
+  - pg_session_wlmstat
+- Cache I/O
+  - pg_statio_all_indexes
+  - pg_statio_all_sequences
+  - pg_statio_all_tables
+  - pg_statio_sys_indexes
+  - pg_statio_sys_sequences
+  - pg_statio_sys_tables
+  - pg_statio_user_indexes
+  - pg_statio_user_sequences
+  - pg_statio_user_tables
+  - gs_stat_db_cu
+  - gs_stat_session_cu
+- Memory
+  - pg_total_memory_detail
+  - pg_shared_memory_detail
+  - gs_total_memory_detail
+- File
+  - gs_file_stat
+  - gs_redo_stat
+  - pg_stat_bad_block
+- Object
+  - pg_stat_user_tables
+  - pg_stat_user_indexes
+  - pg_stat_sys_tables
+  - pg_stat_sys_indexes
+  - pg_stat_all_tables
+  - pg_stat_all_indexes
+  - pg_stat_database
+  - pg_stat_database_conflicts
+  - pg_stat_xact_all_tables
+  - pg_stat_xact_sys_tables
+  - pg_stat_xact_user_tables
+  - pg_stat_xact_user_functions
+- Lock
+  - pg_locks
+- Utility
+  - pg_stat_replication
+  - pg_replication_slots
+  - pg_stat_bgwriter
+- Transaction
+  - pg_running_xacts
+  - pg_prepared_xacts
+- Waits
+  - pg_thread_wait_status
+
+<!--
+**表 1** gs_collector工具支持收集的系统表和视图列表
+
+<table>
+ <tr>
+  <td>Class</td>
+  <td>View Name</td>
+ </tr>
+ <tr>
+  <td rowspan="2">OS</td>
+  <td>gs_os_run_info</td>
+ </tr>
+ <tr>
+  <td>pg_os_threads</td>
+ </tr>
+ <tr>
+  <td rowspan="9">
+   Session/Thread
+  </td>
+  <td>
+   gs_session_stat
+  </td>
+ </tr>
+ <tr>
+  <td>
+   gs_session_time
+  </td>
+ </tr>
+ <tr>
+  <td>
+   gs_session_cpu_statistics
+  </td>
+ </tr>
+ <tr>
+  <td>
+   gs_session_memory_statistics
+  </td>
+ </tr>
+ <tr>
+  <td>
+   gs_session_memory_context
+  </td>
+ </tr>
+ <tr>
+  <td>
+   gs_session_memory
+  </td>
+ </tr>
+ <tr>
+  <td>
+   gs_session_memory_detail
+  </td>
+ </tr>
+ <tr>
+  <td>
+   pg_stat_activity
+  </td>
+ </tr>
+ <tr>
+  <td>
+   gs_thread_memory_context
+  </td>
+ </tr>
+ <tr>
+  <td rowspan="8">
+   WLM
+  </td>
+  <td>
+   gs_cluster_resource_info
+  </td>
+ </tr>
+ <tr>
+  <td>
+   pg_total_user_resource_info
+  </td>
+ </tr>
+ <tr>
+  <td>
+   pg_total_user_resource_info_oid
+  </td>
+ </tr>
+ <tr>
+  <td>
+   gs_wlm_rebuild_user_resource_pool
+  </td>
+ </tr>
+ <tr>
+  <td>
+   gs_wlm_resource_pool
+  </td>
+ </tr>
+ <tr>
+  <td>
+   gs_wlm_workload_records
+  </td>
+ </tr>
+ <tr>
+  <td>
+   pg_wlm_statistics
+  </td>
+ </tr>
+ <tr>
+  <td>
+   pg_app_workloadgroup_mapping
+  </td>
+ </tr>
+ <tr>
+  <td rowspan="3">
+   Query-AP Operator
+  </td>
+  <td>
+   gs_wlm_operator_info
+  </td>
+ </tr>
+ <tr>
+  <td>
+   gs_wlm_operator_history
+  </td>
+ </tr>
+ <tr>
+  <td>
+   gs_wlm_operator_statistics
+  </td>
+ </tr>
+ <tr>
+  <td rowspan="7">
+   Query-AP
+  </td>
+  <td>
+   gs_wlm_session_info_all
+  </td>
+ </tr>
+ <tr>
+  <td>
+   gs_wlm_session_history
+  </td>
+ </tr>
+ <tr>
+  <td>
+   gs_wlm_session_info
+  </td>
+ </tr>
+ <tr>
+  <td>
+   gs_wlm_user_session_info
+  </td>
+ </tr>
+ <tr>
+  <td>
+   gs_wlm_session_statistics
+  </td>
+ </tr>
+ <tr>
+  <td>
+   pg_session_iostat
+  </td>
+ </tr>
+ <tr>
+  <td>
+   pg_session_wlmstat
+  </td>
+ </tr>
+ <tr>
+  <td rowspan="11">
+   Cache I/O
+  </td>
+  <td>
+   pg_statio_all_indexes
+  </td>
+ </tr>
+ <tr>
+  <td>
+   pg_statio_all_sequences
+  </td>
+ </tr>
+ <tr>
+  <td>
+   pg_statio_all_tables
+  </td>
+ </tr>
+ <tr>
+  <td>
+   pg_statio_sys_indexes
+  </td>
+ </tr>
+ <tr>
+  <td>
+   pg_statio_sys_sequences
+  </td>
+ </tr>
+ <tr>
+  <td>
+   pg_statio_sys_tables
+  </td>
+ </tr>
+ <tr>
+  <td>
+   pg_statio_user_indexes
+  </td>
+ </tr>
+ <tr>
+  <td>
+   pg_statio_user_sequences
+  </td>
+ </tr>
+ <tr>
+  <td>
+   pg_statio_user_tables
+  </td>
+ </tr>
+ <tr>
+  <td>
+   gs_stat_db_cu
+  </td>
+ </tr>
+ <tr>
+  <td>
+   gs_stat_session_cu
+  </td>
+ </tr>
+ <tr>
+  <td rowspan="3">
+   Memory
+  </td>
+  <td>
+   pg_total_memory_detail
+  </td>
+ </tr>
+ <tr>
+  <td>
+   pg_shared_memory_detail
+  </td>
+ </tr>
+ <tr>
+  <td>
+   gs_total_memory_detail
+  </td>
+ </tr>
+ <tr>
+  <td rowspan="3">
+   File
+  </td>
+  <td>
+   gs_file_stat
+  </td>
+ </tr>
+ <tr>
+  <td>
+   gs_redo_stat
+  </td>
+ </tr>
+ <tr>
+  <td>
+   pg_stat_bad_block
+  </td>
+ </tr>
+ <tr>
+  <td rowspan="12">
+   Object
+  </td>
+  <td>
+   pg_stat_user_tables
+  </td>
+ </tr>
+ <tr>
+  <td>
+   pg_stat_user_indexes
+  </td>
+ </tr>
+ <tr>
+  <td>
+   pg_stat_sys_tables
+  </td>
+ </tr>
+ <tr>
+  <td>
+   pg_stat_sys_indexes
+  </td>
+ </tr>
+ <tr>
+  <td>
+   pg_stat_all_tables
+  </td>
+ </tr>
+ <tr>
+  <td>
+   pg_stat_all_indexes
+  </td>
+ </tr>
+ <tr>
+  <td>
+   pg_stat_database
+  </td>
+ </tr>
+ <tr>
+  <td>
+   pg_stat_database_conflicts
+  </td>
+ </tr>
+ <tr>
+  <td>
+   pg_stat_xact_all_tables
+  </td>
+ </tr>
+ <tr>
+  <td>
+   pg_stat_xact_sys_tables
+  </td>
+ </tr>
+ <tr>
+  <td>
+   pg_stat_xact_user_tables
+  </td>
+ </tr>
+ <tr>
+  <td>
+   pg_stat_xact_user_functions
+  </td>
+ </tr>
+ <tr>
+  <td>
+   Lock
+  </td>
+  <td>
+   pg_locks
+  </td>
+ </tr>
+ <tr>
+  <td rowspan="3">
+   Utility
+  </td>
+  <td>
+   pg_stat_replication
+  </td>
+ </tr>
+ <tr>
+  <td>
+   pg_replication_slots
+  </td>
+ </tr>
+ <tr>
+  <td>
+   pg_stat_bgwriter
+  </td>
+ </tr>
+ <tr>
+  <td rowspan="2">
+   Transaction
+  </td>
+  <td>
+   pg_running_xacts
+  </td>
+ </tr>
+ <tr>
+  <td>
+   pg_prepared_xacts
+  </td>
+ </tr>
+ <tr>
+  <td>
+   Waits
+  </td>
+  <td>
+   pg_thread_wait_status
+  </td>
+ </tr>
+</table> -->
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tool-overview.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tool-overview.md
new file mode 100644
index 0000000000000000000000000000000000000000..a59196f8027883124a65b77426a14d5b39f7111c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tool-overview.md
@@ -0,0 +1,78 @@
+---
+title: 工具一览表
+summary: 工具一览表
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# 工具一览表
+
+MogDB提供客户端和服务器端应用程序（工具），帮助用户更好地维护MogDB，提供的所有工具如[表1](#gongjuyilanbiao)所示。工具位于安装数据库服务器的\$GPHOME/script和$GAUSSHOME/bin路径下。
+
+**表 1** 工具一览表 <a id="gongjuyilanbiao"> </a>
+
+<table>
+    <tr>
+        <th>分类</th>
+        <th>工具名称</th>
+        <th>简介</th>
+    </tr>
+    <tr>
+        <td>客户端工具</td>
+        <td>gsql</td>
+        <td>gsql是MogDB提供在命令行下运行的数据库连接工具，可以通过此工具连接服务器并对其进行操作和维护，除了具备操作数据库的基本功能，gsql还提供了若干高级特性，便于用户使用。</td>
+    </tr>
+    <tr>
+        <td rowspan="14">服务端工具</td>
+        <td>gs_cgroup</td>
+        <td>gs_cgroup是MogDB提供的负载管理工具。负责创建默认控制组、创建用户自定义控制组、删除用户自定义控制组、更新用户自定义组的资源配额和资源限额、显示控制组配置文件内容、显示控制组树形结构和删除用户的所有控制组。</td>
+    <tr/>
+    <tr>
+        <td>gs_check</td>
+        <td>gs_check改进增强，统一化当前系统中存在的各种检查工具，例如gs_check，gs_checkos等，帮助用户在MogDB运行过程中，全量的检查MogDB运行环境、操作系统环境、网络环境及数据库执行环境，也有助于在MogDB重大操作之前对各类环境进行全面检查，有效保证操作执行成功。</td>
+    </tr>
+    <tr>
+        <td>gs_checkos</td>
+        <td>gs_checkos用于检查操作系统、控制参数、磁盘配置等内容，并对系统控制参数、I/O配置、网络配置和THP服务等信息进行配置。</td>
+    </tr>
+    <tr>
+        <td>gs_checkperf</td>
+        <td>gs_checkperf工具可定期对MogDB级别（主机CPU占用率、MogDB CPU占用率、I/O使用情况等）、节点级别（CPU使用情况、内存使用情况、I/O使用情况）、会话/进程级别（CPU使用情况、内存使用情况、I/O使用情况）、SSD性能（写入、读取性能）进行检查，让用户了解MogDB的负载情况，采取对应的改进措施。</td>
+    </tr>
+    <tr>
+        <td>gs_collector</td>
+        <td>gs_collector在MogDB发生故障时，收集OS信息、日志信息以及配置文件信息，来定位问题。</td>
+    </tr>
+    <tr>
+        <td>gs_dump</td>
+        <td>gs_dump是一款用于导出数据库相关信息的工具，支持导出完整一致的数据库对象（数据库、模式、表、视图等）数据，同时不影响用户对数据库的正常访问。</td>
+    </tr>
+    <tr>
+        <td>gs_dumpall</td>
+        <td>gs_dumpall是一款用于导出数据库相关信息的工具，支持导出完整一致的MogDB数据库所有数据，同时不影响用户对数据库的正常访问。</td>
+    </tr>
+    <tr>
+        <td>gs_guc</td>
+        <td>gs_guc用于设置MogDB配置文件（“postgresql.conf”、“pg_hba.conf”）中的参数，配置文件中参数的默认值是单机的配置模式，您可以使用gs_guc来设置适合的参数值。</td>
+    </tr>
+    <tr>
+        <td>gs_encrypt</td>
+        <td>gs_encrypt是一款用于为输入的明文字符串进行加密操作。</td>
+    </tr>
+    <tr>
+        <td>gs_om</td>
+        <td>MogDB提供了gs_om工具帮助对MogDB进行维护，包括启动MogDB、停止MogDB、查询MogDB状态、生成静态配置文件、刷新动态配置文件、SSL证书替换、启停kerberos认证、显示帮助信息和显示版本号信息的功能。</td>
+    </tr>
+    <tr>
+        <td>gs_plan_simulator</td>
+        <td>gs_plan_simulator工具用于收集与执行计划相关的数据并能够在其它环境上进行执行计划的复现，从而定位执行计划类相关问题。</td>
+    </tr>
+    <tr>
+        <td>gs_restore</td>
+        <td>gs_restore是MogDB提供的针对gs_dump导出数据的导入工具。通过此工具可由gs_dump生成的导出文件进行导入。</td>
+    </tr>
+    <tr>
+        <td>gs_ssh</td>
+        <td>MogDB提供了gs_ssh工具帮助用户在MogDB各节点上执行相同的命令。</td>
+    </tr>
+</table>
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/1-gaussdb.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/1-gaussdb.md
new file mode 100644
index 0000000000000000000000000000000000000000..617c8deb44f7ad54341e3d168ffeae0162ffd663
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/1-gaussdb.md
@@ -0,0 +1,176 @@
+---
+title: gaussdb
+summary: gaussdb
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gaussdb
+
+## 背景信息
+
+gaussdb是MogDB数据库的主进程，也是一个可执行的命令，能够通过其启动一个数据库进程。
+
+## 语法
+
+```
+gaussdb [OPTION]...
+```
+
+## 描述
+
+客户端应用程序为了访问数据库，将连接（通过网络或本地）到一个正在运行的gaussdb进程。然后该进程实例会启动一个独立的线程来处理这个连接。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** 通过gaussdb启动数据库时，需要再开一个窗口来连接到数据库，也可以使用&符号使程序在后台执行。
+
+一个gaussdb进程总是管理来自同一个数据库的数据。一个系统上可以同时运行多个gaussdb进程，只要使用不同的数据目录和不同的端口号。gaussdb启动时需要知道数据目录的位置，该位置必须通过-D指定。通常，-D直接指向由gs_initdb创建的数据库目录。
+
+缺省时gaussdb在前台启动并将日志信息输出到标准错误。但在实际应用中，gaussdb应当作为后台进程启动，而且多数是在系统启动时自动启动。
+
+gaussdb还能以单用户模式运行，这种用法主要用于gs_initdb的初始化过程中，有时候也被用于调试灾难性恢复。不过，单用户模式运行的服务器并不适合于调试，因为没有实际的进程间通讯和锁动作发生。当从shell上以单用户模式调用时，用户可以输入查询，然后结果会在屏幕上以一种更适合开发者阅读（不适合普通用户）的格式显示出来。在单用户模式下，将把会话用户ID设为1并赋予系统管理员权限。该用户不必实际存在，因此单用户模式运行的服务器可以用于对某些意外损坏的系统表进行手工恢复。
+
+## 选项
+
+gaussdb接受[表1](#canshushuoming)中所示的命令行参数。
+
+**表 1** 参数说明 <a id="canshushuoming"> </a>
+
+| 参数               | 参数说明                                                     | 取值范围                                                     |
+| :----------------- | :----------------------------------------------------------- | :----------------------------------------------------------- |
+| -B NBUFFERS        | 设置服务器进程使用的共享内存缓冲区的数量。                   | -                                                            |
+| -b BINARY UPGRADES | binary upgrade标志。                                         | -                                                            |
+| -c NAME=VALUE      | 给一个正在运行的参数赋值。-c可以出现多次从而设置多个参数。   | -                                                            |
+| -C NAME            | 打印一个命名的运行时的参数的值然后退出。可以用在正在运行的服务器上，从postgresql.conf返回值。 | 取值为postgresql.conf中的所有参数。                          |
+| -d 1-5             | 设置调试级别，1-5记录对应debug级别信息。级别越高，写到服务器日志的调试输出越多。 | 取值范围: 1-5。说明：如果取值小于等于0，则只会记录notice级别的信息。 |
+| -D DATADIR         | 声明数据目录或者配置文件的文件系统路径。                     | 用户自定义。                                                 |
+| -e                 | 把缺省日期风格设置为”European”，也就是说用DMY规则解释日期输入，并且在一些日期输出格式里日在月份前面打印。 | -                                                            |
+| -F                 | 关闭fsync调用以提高性能，但是要冒系统崩溃时数据毁坏的风险。声明这个选项等效关闭了fsync参数。 | -                                                            |
+| -h HOSTNAME        | 指定gaussdb侦听来自前端应用TCP/IP连接的主机名或IP地址。      | 前端存在的主机名或IP地址。                                   |
+| -i                 | 该选项允许远程客户通过TCP/IP（网际域套接字）与服务器通讯。   | -                                                            |
+| -k DIRECTORY       | 指定gaussdb侦听来自前端应用连接的Unix域套接字的目录。        | 缺省通常是/tmp ，但是可以在编译的时候修改。                  |
+| -l                 | 该选项允许远程客户通过SSL（ 安全套接层）与服务器通讯。       | -                                                            |
+| -N MAX-CONNECT     | 设置服务器接受的客户端连接的最大数。缺省时由gs_initdb自动选择。声明这个选项等价于声明max_connections配置参数。 | 取值范围: 正整数。                                           |
+| -M SERVERMODE      | 在启动时指定数据库的启动模式。                               | SERVERMODE可以取下面四个值：<br />- primary：本端以主机模式启动。<br />- standby：本端以备机模式启动。<br />- cascade_standby：本端以级联备机模式启动。<br />- pending：本端处于等待状态，等待提升为主机或者备机。 |
+| -o OPTIONS         | 向每个服务器进程传递 “OPTIONS”。保留语法，已没有实际功能。   | -                                                            |
+| -p PORT            | 指定gaussdb侦听客户端连接的TCP/IP端口或本地Unix domain socket文件的扩展。默认端口号为15400。 | 正整数，在操作系统支持的端口范围内。                         |
+| -s                 | 在每条命令结束时打印时间信息和其他统计信息。                 | -                                                            |
+| -S WORK-MEM        | 声明内部排序和散列在求助于临时磁盘文件之前可以使用的内存大小。 | 单位为KB。                                                   |
+| -single_node       | 拉起单机数据库。                                             | -                                                            |
+| -V, -version       | 打印gaussdb的版本信息然后退出。                              | -                                                            |
+| -NAME=VALUE        | 给一个正在运行的参数赋值。                                   | -                                                            |
+| -describe-config   | 描述配置参数然后退出。                                       | -                                                            |
+| -?, -help          | 显示关于gaussdb命令行参数的帮助信息，然后退出。              | -                                                            |
+
+[表2](#kaifazhexuanxiang)中的参数主要是便于开发人员调试使用，有时也用于帮助恢复严重损坏的数据库。在应用程序使用数据库提供服务时，请不要使用这些参数进行调试。
+
+**表 2** 开发者选项 <a id="kaifazhexuanxiang"></a>
+
+| 参数             | 参数说明                                                     | 取值范围                                                     |
+| :--------------- | :----------------------------------------------------------- | :----------------------------------------------------------- |
+| -f s\|i\|n\|m\|h | 禁止某种扫描和连接方法的使用。                               | 取值范围: <br />- s：关闭顺序<br />- i：索引扫描<br />- n：关闭嵌套循环<br />- m：融合（merge）连接<br />- h：Hash连接 |
+| -n               | 主要用于调试导致服务器进程异常崩溃的问题。一般策略是通知所有其他服务器进程终止并重新初始化共享内存和信号灯。该选项指定gaussdb不重新初始化共享内存。 | -                                                            |
+| -P               | 读系统表时忽略系统索引，但在修改表时仍然更新索引。           | -                                                            |
+| -t pa\|pl\|ex    | 打印与每个主要系统模块相关的查询记时统计。                   | -                                                            |
+| -T               | 主要用于调试导致服务器进程异常崩溃的问题。该选项指定gaussdb通过发送SIGSTOP信号停止其他所有服务器进程，但是并不让它们退出。这样就允许系统程序员手动从所有服务器进程搜集内核转储。 | -                                                            |
+| -W NUM           | 指定一个新的服务器进程开始需要等待的秒数。                   | 单位：秒                                                     |
+| -localxid        | 使用本地事务ID，而不是全局事务ID。须知：此选项仅用于gs_initdb。使用此选项可能会导致数据库不一致。 | 已存在的本地事务ID                                           |
+
+下面的选项[表3](#danyonghu)仅在单用户模式下可用。
+
+**表 3** 单用户模式选项 <a id="danyonghu"> </a>
+
+| 参数        | 参数说明                                             | 取值范围               |
+| :---------- | :--------------------------------------------------- | :--------------------- |
+| -single     | 启动单用户模式。必须是命令行中的第一个选项。         | -                      |
+| DBNAME      | 要访问的数据库的名称。必须是命令行中的最后一个选项。 | 字符串。默认为用户名。 |
+| -d 0-5      | 重新指定调试级别。                                   | 0-5                    |
+| -E          | 回显所有命令。                                       | -                      |
+| -j          | 禁止使用新行作为语句分隔符。                         | -                      |
+| -r FILENAME | 将所有服务器标准输出和标准错误保存到文件filename中。 | -                      |
+
+**表 4** 自启动模式选项
+
+| 参数        | 参数说明                                                     | 取值范围 |
+| :---------- | :----------------------------------------------------------- | :------- |
+| -boot       | 启动自启动模式。必须是命令行中的第一个选项。该参数是对数据库中的参数变量及相关配置初始化，常用在数据库安装的流程中，直接使用该参数，无明显行为感知。 | -        |
+| -r FILENAME | 将所有服务器标准输出和标准错误保存到文件filename中。         | -        |
+| -x NUM      | 指定一个新的服务器线程的类型。在初始化数据库时，会用到自启动模式，通过设置这个参数，启动不同线程来执行一些逻辑，正常情况下，不会用到，因为自启动模式很少会用到。 | -        |
+
+**表 5** 升级模式选项
+
+| 参数   | 参数说明                     | 取值范围 |
+| :----- | :--------------------------- | :------- |
+| -u NUM | 指定升级前数据库内核版本号。 | -        |
+
+除以上参数外，出现在postgres.conf中的所有参数，均可以用-guc_name=guc_value的方式在gaussdb启动时传给gaussdb。例如，-enable_fast_query_shipping=off。
+
+## 环境变量
+
+- PGLINETENCODING：客户端使用的缺省字符编码。客户端可以独立地覆盖它。这个值也可以在配置文件里设置。
+- PGDATESTYLE：运行时参数DateStyle的缺省值。现在反对使用该环境变量。
+- TZ：服务器的时区。
+
+## 错误处理
+
+一个提到了semget或shmget的错误信息可能意味着需要重新配置内核，提供足够的共享内存和信号灯。可以通过降低shared_buffers值以减少MogDB的共享内存的消耗，或者降低max_connections值减少MogDB的信号灯的消耗。
+
+如果发现类似“另外一个服务器正在运行”的错误信息，可以根据系统使用不同的命令：
+
+```bash
+ps ax | grep gaussdb
+```
+
+或
+
+```bash
+ps -ef | grep gaussdb
+```
+
+如果确信没有冲突的服务器正在运行，可以删除消息里提到的锁文件然后再次运行。
+
+无法绑定端口的错误信息可能表明该端口已经被其他非MogDB进程使用。如果终止gaussdb后又马上用同一端口号运行它，也可能得到错误信息。这时，必须多等几秒，等操作系统关闭了该端口再试。最后，如果使用了一个操作系统认为是保留的端口，也可能导致这个错误信息。例如：Unix版本认为低于1024的端口号是“可信任的”，因而只有Unix系统管理员可以使用它们。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+>
+> - 如果有可能，不要使用SIGKILL杀死主进程。这样会阻止gaussdb在退出前释放它持有的系统资源（例如共享内存和信号灯）。这样可能会影响到将来启动新的进程。
+> - 可以使用SIGTERM，SIGINT，SIGQUIT信号正常结束服务器进程。第一个信号将等待所有的客户端退出后才退出。第二个将强制断开所有客户端，而第三个将不停止立刻退出，导致在重启时的恢复运行。
+> - 信号SIGHUP将会重新加载服务器配置文件。它也可能给单个服务器进程发送SIGHUP信号，但是这通常是不明显的。
+> - 要取消一个正在执行的查询，向正在运行的进程发送SIGINT信号。
+> - 主服务器进程向子进程发送SIGTERM信号让它们正常退出；发送SIGQUIT信号立即退出且不做清理工作。用户有三种信号不能用。同时，发送SIGKILL信号也是不明智的：主进程将把这个信号当作崩溃信号，然后会强制其他兄弟进程作为标准的崩溃回复过程退出。
+
+## 用法
+
+启动一个单用户模式的服务器：
+
+```bash
+gaussdb --single -D /usr/local/pgsql/data other-options my_database
+```
+
+用-D给服务器提供正确的数据库目录的路径。同时还要声名已存在的特定数据库名称。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+>
+> - 通常，独立运行的服务器把换行符当做命令输入完成字符；要想把一行分成多行写，必需在除最后一个换行符以外的每个换行符前面敲一个反斜杠。
+> - 如果使用了-j命令行选项，新行将不被当作命令结束符。此时服务器将从标准输入一直读取到EOF标志为止，然后把所有读到的内容当作一个完整的命令字符串看待，并且反斜杠与换行符也被当作普通字符来看待。
+> - 输入EOF（Control+D）即可退出会话。如果已经使用了-j则必须连续使用两个EOF才行。
+> - 单用户模式运行的服务器不会提供复杂的行编辑功能（比如没有命令历史）。单用户模式也不会做任何后台处理，像自动检查点。
+
+## 示例
+
+1. 用缺省值在后台启动gaussdb：
+
+   ```bash
+   nohup gaussdb >logfile 2>&1 </dev/null  &
+   ```
+
+2. 在指定端口启动gaussdb，如1234：
+
+   ```bash
+   gaussdb --single_node -p -D data_dir
+   ```
+
+   使用gsql与服务器连接，用-p指定端口号：
+
+   ```bash
+   gsql -d postgres -p 1234
+   ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/10-gs_tar.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/10-gs_tar.md
new file mode 100644
index 0000000000000000000000000000000000000000..21357ff9cbcd8c58c761c3d01cf005102ffd83eb
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/10-gs_tar.md
@@ -0,0 +1,49 @@
+---
+title: gs_tar
+summary: gs_tar
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_tar
+
+## 背景信息
+
+通过gs_basebackup的压缩格式备份，主数据目录将被写入到一个名为 base.tar 的文件中，并且其他表空间将被以其 OID 命名。生成的数据文件，需要通过gs_tar命令作解压。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - gs_tar命令当前仅支持解压通过gs_basebackup生成的归档文件。
+> - 如果gs_basebackup制定了压缩等级，会生成以gz结尾的文件。此时需要使用gzip命令先解压缩生成tar包，之后才可以使用gs_tar命令解压生成的tar文件。
+
+## 语法
+
+- 显示帮助信息
+
+  ```bash
+  gs_tar -? | --help
+  ```
+
+- 显示版本号信息
+
+  ```bash
+  gs_tar -V | --version
+  ```
+
+## 参数说明
+
+gs_tar参数如下：
+
+- -F, -filename=FILENAME
+
+解压文件，必选项。
+
+- -D，-destination=DIRECTORY
+
+解压文件输出的目录，必选项。
+
+## 示例
+
+```bash
+gs_tar -D /home/test/dn1 -F /home/test/trunk/install/data/backup/base.tar
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/11-gs_uninstall.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/11-gs_uninstall.md
new file mode 100644
index 0000000000000000000000000000000000000000..5214bfc6e76be97d9a5e54ae2e36cc4e9adca970
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/11-gs_uninstall.md
@@ -0,0 +1,80 @@
+---
+title: gs_uninstall
+summary: gs_uninstall
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_uninstall
+
+## 背景信息
+
+MogDB提供了gs_uninstall工具来帮助完成MogDB的卸载。
+
+## 语法
+
+- 卸载MogDB
+
+  ```bash
+  gs_uninstall [--delete-data] [-L] [-l LOGFILE]
+  ```
+
+- 显示帮助信息
+
+  ```bash
+  gs_uninstall -? | --help
+  ```
+
+- 显示版本号信息
+
+  ```bash
+  gs_uninstall -V | --version
+  ```
+
+## 参数说明
+
+- -delete-data
+
+  删除数据文件。
+
+- -L
+
+  只卸载本地主机。如果MogDB内某主机做单点卸载后，MogDB不能再做全量卸载。
+
+- -l
+
+  指定日志文件名及可访问的绝对路径。在内部会自动给日志名添加一个时间戳。
+
+  - 当既不明确指定-l，又不在XML文件中配置gaussdbLogPath时，默认值为“$GAUSSLOG/om/gs_uninstall-YYYY-MM-DD_hhmmss.log”。
+
+  - 当不明确指定-l，但在XML文件中配置了gaussdbLogPath时，默认值为“gaussdbLogPath/用户名/om/gs_uninstall-YYYY-MM-DD_hhmmss.log”。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 由于在执行gs_uninstall时，系统会自动删除MogDB相关目录。因此建议用户通过该参数指定日志文件到非MogDB相关路径。
+
+- -?, -help
+
+  显示帮助信息。
+
+- -V, -version
+
+  显示版本号信息。
+
+## 示例
+
+使用数据库用户执行gs_uninstall脚本进行卸载MogDB。
+
+```
+gs_uninstall --delete-data
+Checking uninstallation.
+Successfully checked uninstallation.
+Stopping the cluster.
+Successfully stopped the cluster.
+Successfully deleted instances.
+Uninstalling application.
+Successfully uninstalled application.
+Uninstallation succeeded.
+```
+
+## 相关命令
+
+[gs_install](6-gs_install)，[gs_postuninstall](7-gs_postuninstall)
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/12-gs_upgradectl.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/12-gs_upgradectl.md
new file mode 100644
index 0000000000000000000000000000000000000000..3d87ed415f6e64d7fc4c80c50b193a17c9dc767c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/12-gs_upgradectl.md
@@ -0,0 +1,250 @@
+---
+title: gs_upgradectl
+summary: gs_upgradectl
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_upgradectl
+
+## 背景信息
+
+用户根据MogDB提供的新特性和数据库现状，确定是否对现有系统进行升级。
+
+当前支持的升级模式为就地升级和灰度升级。升级方式的策略又分为大版本升级和小版本升级。
+
+用户挑选升级方式后，系统会自动判断并选择合适的升级策略。
+
+就地升级：升级期间需停止业务进行，一次性升级所有节点。
+
+灰度升级：灰度升级支持全业务操作，也是一次性升级所有节点（MogDB 2.0版本之后的版本支持该功能）。
+
+## 注意事项
+
+- 升级操作不能和扩容、缩容同时执行。
+- 不支持虚拟IP。
+- 升级过程中，不允许对wal_level，max_connections，max_prepared_transactions，max_locks_per_transaction这四个GUC参数的值进行修改。如果修改，会导致回滚后实例启动异常。
+- 建议在数据库系统空闲情况下进行升级，尽量避开业务繁忙的时间段（可按照经验判断，如节假日等）。
+- 升级前尽可能保证数据库正常。可以通过gs_om -t status查询，查询结果的cluster_state为Normal代表数据库正常。
+- 升级前保证数据库互信正常，可以在任意节点上，通过ssh hostname命令，连接另外一个节点进行验证。如果各机器间互连不用输入密码，说明互信正常（通常数据库状态正常时，互信一般都是正常的）。
+- 升级前后，数据库的部署方式（配置文件）不能发生变化。升级前会对部署方式进行校验，如果改变，会报错。
+- 升级前要保证操作系统处于健康状态，通过gs_checkos工具可以完成操作系统状态检查。
+- 就地升级需要停止业务，灰度升级支持全业务操作。
+- 数据库运行正常且主DN的数据完全同步到备DN。
+- 升级过程中不允许打开kerberos开关。
+- 请不要修改安装包中解压出来的version.cfg文件。
+- 如果升级过程中出现异常导致升级失败，需用户手动回滚，并且必须回滚成功后才能进行下一次升级。
+- 如果升级回滚成功后，再次升级成功，未提交阶段设置的GUC参数将失效。
+- 执行升级的过程中请不要手动设置GUC参数。
+- 灰度升级中，升级的时候都会产生不超过10s的业务中断。
+- 升级过程中，必须保持内核版本与om版本一致才可执行om操作。这里的一致是指，内核代码和om代码都来自同一个软件包。如果执行了升级包的前置脚本却没有升级，或者升级回滚后没有执行基线包的前置脚本，就会造成内核代码和om代码的不一致。
+- 升级过程中如果系统表新增了字段，升级后通过**\d**命令将查看不到这些新增的字段。此时通过**select**命令可以查到这些新增的字段。
+- 升级需要guc参数enable_stream_replication=on，该参数为off时不允许升级。
+- 灰度升级中， 业务并发要小于200并发读加200并发写的情况。
+- 建议数据库节点磁盘使用率低于80%时再执行升级操作。
+- 执行gs_upgradectl -t auto-upgrade 之后，没有提交之前，不能执行快照生成，即升级过程中不能执行快照生成。
+
+## 语法
+
+- 显示帮助信息
+
+  ```bash
+  gs_upgradectl -? | --help
+  ```
+
+- 显示版本号信息
+
+  ```bash
+  gs_upgradectl -V | --version
+  ```
+
+- 选择升级策略
+
+  ```bash
+  gs_upgradectl -t chose-strategy [-l LOGFILE]
+  ```
+
+- 自动升级MogDB
+
+  ```bash
+  gs_upgradectl -t auto-upgrade -X XMLFILE  [-l LOGFILE] [--grey]
+  ```
+
+- 自动回滚升级
+
+  ```bash
+  gs_upgradectl -t auto-rollback -X XMLFILE [-l LOGFILE] [--force]
+  ```
+
+- 升级提交
+
+  ```bash
+  gs_upgradectl -t commit-upgrade -X XMLFILE [-l LOGFILE]
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  >
+  > - 一旦提交操作完成，则不能再执行回滚操作。
+
+## 参数说明
+
+- -t
+
+  gs_upgradectl命令的类型。
+
+  取值范围: chose-strategy、auto-upgrade、auto-rollback和commit-upgrade。
+
+- -l
+
+  用于记录升级或回滚过程中的日志信息。
+
+  取值范围: 任意存在的可访问的绝对路径。
+
+  默认值：/var/log/gaussdb/用户名/om/gs_upgradectl-YYYY-MM-DD_hhmmss.log
+
+- -?, -help
+
+  显示帮助信息。
+
+- -V, -version
+
+  显示版本号信息。
+
+- -X
+
+  指定MogDB配置文件。
+
+  取值范围: xml文件的存储路径。
+
+- -grey
+
+  使用灰度升级方式来进行升级操作。
+
+- -force
+
+  当MogDB状态不正常，无法支持正常回滚时，用此参数进行强制回滚操作。
+
+## 示例
+
+**示例一**：升级前使用新包进行前置操作。
+
+```bash
+./gs_preinstall -U roach -G users -X /data/xml/3node_3c3d_1m2s_etcd.xml
+Parsing the configuration file.
+Successfully parsed the configuration file.
+Installing the tools on the local node.
+Successfully installed the tools on the local node.
+Setting pssh path
+Successfully set core path.
+Distributing package.
+Begin to distribute package to tool path.
+Successfully distribute package to tool path.
+Begin to distribute package to package path.
+Successfully distribute package to package path.
+Successfully distributed package.
+Installing the tools in the cluster.
+Successfully installed the tools in the cluster.
+Checking hostname mapping.
+Successfully checked hostname mapping.
+Checking OS version.
+Successfully checked OS version.
+Creating cluster's path.
+Successfully created cluster's path.
+Set and check OS parameter.
+Setting OS parameters.
+Successfully set OS parameters.
+Set and check OS parameter completed.
+Preparing CRON service.
+Successfully prepared CRON service.
+Preparing SSH service.
+Successfully prepared SSH service.
+Setting user environmental variables.
+Successfully set user environmental variables.
+Configuring alarms on the cluster nodes.
+Successfully configured alarms on the cluster nodes.
+Setting the dynamic link library.
+Successfully set the dynamic link library.
+Setting pssh path
+Successfully set pssh path.
+Setting Cgroup.
+Successfully set Cgroup.
+Set ARM Optimization.
+Successfully set ARM Optimization.
+Preinstalling secbox.
+Successfully installed secbox.
+Setting finish flag.
+Successfully set finish flag.
+Preinstallation succeeded.
+```
+
+**示例二：**使用gs_upgradectl脚本执行就地升级。
+
+```bash
+gs_upgradectl -t upgrade -X /data/xml/3node_3c3d_1m2s_etcd.xml
+Static configuration matched with old static configuration files.
+Performing inplace rollback.
+Rollback succeeded.
+Checking upgrade environment.
+Successfully checked upgrade environment.
+Successfully checked upgrade environment.
+Successfully started cluster.
+Start to do health check.
+Successfully checked cluster status.
+Backing up current application and configurations.
+Successfully backed up current application and configurations.
+Stopping the cluster.
+Successfully stopped cluster.
+Backing up cluster configuration.
+Successfully backup hotpatch config file.
+Successfully backed up cluster configuration.
+Installing new binary.
+Restoring cluster configuration.
+Successfully restored cluster configuration.
+Modifying the socket path.
+Successfully modified socket path.
+Switch symbolic link to new binary directory.
+Successfully switch symbolic link to new binary directory.
+Successfully started cluster.
+Start to do health check.
+Successfully checked cluster status.
+Upgrade main process has been finished, user can do some check now.
+Once the check done, please execute following command to commit upgrade:
+```
+
+```bash
+gs_upgradectl -t commit-upgrade -X /data/xml/3node_3c3d_1m2s_etcd.xml
+```
+
+**示例三：**使用gs_upgradectl脚本执行自动回滚，撤销已经成功/失败的升级操作（升级回滚）。
+
+```bash
+gs_upgradectl -t rollback -X /data/xml/3node_3c3d_1m2s_etcd.xml
+Static configuration matched with old static configuration files.
+Performing inplace rollback.
+Checking static configuration files.
+Successfully checked static configuration files.
+Restoring cluster configuration.
+Successfully rollback hotpatch config file.
+Successfully restored cluster configuration.
+Switch symbolic link to old binary directory.
+Successfully switch symbolic link to old binary directory.
+Stopping the cluster.
+Successfully stopped cluster.
+Restoring application and configurations.
+Successfully restored application and configuration.
+Restoring cluster configuration.
+Successfully rollback hotpatch config file.
+Successfully restored cluster configuration.
+Successfully started cluster.
+Successfully cleaned new install path.
+Rollback succeeded.
+```
+
+**示例四：**使用gs_upgradectl脚本执行升级后提交（升级提交）。
+
+```bash
+gs_upgradectl -t commit -X /data/xml/3node_3c3d_1m2s_etcd.xml
+Old cluster app path is /data/gauss/app_e67b8bcd
+Successfully Cleaned old install path.
+Commit binary upgrade succeeded.
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/13-gs_expansion.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/13-gs_expansion.md
new file mode 100644
index 0000000000000000000000000000000000000000..0abc4f31d5113b22fd776d745d38c08187b12de1
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/13-gs_expansion.md
@@ -0,0 +1,169 @@
+---
+title: gs_expansion
+summary: gs_expansion
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_expansion
+
+## 背景信息
+
+MogDB提供了gs_expansion工具对数据库的备机进行扩容。支持从单机或者一主多备最多扩容到一主八备。
+
+## 注意事项
+
+- 扩容后不会自动更新synchronous_standby_names参数。如果需要为该参数增加扩容的机器，请在扩容完成后手动更新。
+- 扩容级联备之前要确保原集群中有处于同一AZ（Available Zone）且状态正常的备机，或扩容级联备的同时也扩容了处于同AZ的备机。
+- 对数据库集群进行扩容前，需要关注主机及新扩容节点CPU、IO、网络等情况，不建议在硬件压力较大时执行扩容，否则可能导致扩容耗时较长甚至扩容失败。
+- 当原集群数据量较大时，在进行扩容操作前应当在主机上先执行checkpoint，否则可能导致扩容耗时较长甚至扩容失败。
+
+## 前提条件
+
+- 数据库主机上存在MogDB镜像包，解压镜像包后，在script目录下执行./gs_expansion命令进行扩容。
+- 在新增的扩容备机上创建好与主机上相同的用户和用户组。
+- 已存在的数据库节点和新增的扩容节点之间需要建立好root用户互信以及数据库管理用户（如omm）的互信。
+- 正确配置xml文件，在已安装数据库配置文件的基础上，添加需要扩容的备机信息。
+- 只能使用root用户执行gs_expansion命令。
+- 不允许同时在主节点上执行gs_dropnode命令删除其他备机。
+- 执行扩容命令前需要通过source命令导入主机数据库的环境变量。如果当前数据库是分离环境变量方式安装，则source导入分离的环境变量。如果未进行分离，则需要source导入子用户的.bashrc配置文件。一般该文件路径为：/home/[user]/.bashrc。
+- 扩容备机的操作系统与主机保持一致。
+- 操作过程中不允许同时在其他备节点上执行主备倒换或者故障倒换的操作。
+- 不允许同时执行2次相同的gs_expansion命令。
+- 扩容备节点的操作只能在主节点上执行。
+
+## 语法
+
+- 备机扩容
+
+  ```bash
+  ./gs_expansion -U USER -G GROUP -X XMLFILE -h hostlist [-L]
+  ```
+
+- 显示帮助信息
+
+  ```bash
+  ./gs_expansion -? | --help
+  ```
+
+- 显示版本号信息
+
+  ```bash
+  ./gs_expansion -V | --version
+  ```
+
+## 参数说明
+
+- -U
+
+  运行MogDB的操作系统用户名。
+
+  新增扩容的备机用户名必须与已安装数据库的主机保持一致，且要提前创建好。
+
+- -G
+
+  运行MogDB的操作系统用户组。
+
+  新增扩容的备机用户组必须与已安装数据库的主机保持一致，且要提前创建好。
+
+- -X
+
+  MogDB配置文件路径。
+
+  取值范围: xml文件的存储路径。xml文件里面需要包含已安装的数据库以及新增扩容数据库所有节点配置信息。
+
+- -h
+
+  指定扩容备机的IP地址。
+
+  取值与xml配置文件里面的backip保持一致。如果有多个节点，节点之间以逗号分隔。
+
+- -L
+
+  如果要扩容的节点已经安装了单机版的数据库，扩容时候添加 -L 参数可以跳过在新扩容备机上安装数据库的步骤，直接建立主备关系。
+
+  需要注意：
+
+  1. 主备机器安装的数据库需要使用相同的用户和用户组，分离环境变量路径也需要保持一样。
+  2. 主备机器安装时候xml配置里面的gaussdbAppPath、gaussdbLogPath、gaussdbToolPath、corePath地址需要保持一致。
+  3. 扩容备机上的数据必须使用om方式安装，使用编译方式启动的数据库不支持与主机扩容。
+  4. 新增扩容节点的数据库版本需要与主库保持一致。
+
+- -?, -help
+
+  显示帮助信息。
+
+- -V, -version
+
+  显示版本号信息。
+
+## 示例
+
+使用gs_expansion扩容步骤。
+
+```bash
+plat1:/opt/software/MogDB/script # ./gs_expansion -U omm -G dbgrp -X /home/omm/cluster_config.xml -h 192.168.0.1
+Start to preinstall database on new nodes.
+Start to send soft to each standby nodes.
+End to send soft to each standby nodes.
+Start to preinstall database step.
+Preinstall 192.168.0.1 success
+End to preinstall database step.
+End to preinstall database on new nodes.
+
+Start to install database on new nodes.
+Installing database on node 192.168.0.1:
+Please enter the password of user [omm] on node [192.168.0.1]:
+Parsing the configuration file.
+Check preinstall on every node.
+Successfully checked preinstall on every node.
+Creating the backup directory.
+Successfully created the backup directory.
+begin deploy..
+Installing the cluster.
+begin prepare Install Cluster..
+Checking the installation environment on all nodes.
+begin install Cluster..
+Installing applications on all nodes.
+Successfully installed APP.
+begin init Instance..
+encrypt cipher and rand files for database.
+Please enter password for database:
+Please repeat for database:
+begin to create CA cert files
+The sslcert will be generated in /opt/gaussdb/cluster/app/share/sslcert/om
+Cluster installation is completed.
+Configuring.
+Deleting instances from all nodes.
+Successfully deleted instances from all nodes.
+Checking node configuration on all nodes.
+Initializing instances on all nodes.
+Updating instance configuration on all nodes.
+Check consistence of memCheck and coresCheck on database nodes.
+Configuring pg_hba on all nodes.
+Configuration is completed.
+Successfully started cluster.
+Successfully installed application.
+end deploy..
+192.168.0.1 install success.
+Finish to install database on all nodes.
+Database on standby nodes installed finished.
+
+Checking gaussdb and gs_om version.
+End to check gaussdb and gs_om version.
+
+Start to establish the relationship.
+Start to build standby 192.168.0.1.
+Build standby 192.168.0.1 success.
+Start to generate and send cluster static file.
+End to generate and send cluster static file.
+
+Expansion results:
+192.168.0.1:   Success
+Expansion Finish.
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：**
+>
+> - 对数据库集群进行扩容前，需要关注主机及新扩容节点cpu、io、网络等情况，不建议在硬件压力较大时执行扩容，否则可能导致扩容耗时较长甚至扩容失败。
+> - 当原集群数据量较大时，在进行扩容操作前应当在主机上先执行checkpoint，否则可能导致扩容耗时较长甚至扩容失败。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/14-gs_dropnode.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/14-gs_dropnode.md
new file mode 100644
index 0000000000000000000000000000000000000000..85230669308cc51a68e50e96ebb999f33ac16a10
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/14-gs_dropnode.md
@@ -0,0 +1,126 @@
+---
+title: gs_dropnode
+summary: gs_dropnode
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_dropnode
+
+## 背景信息
+
+MogDB提供了gs_dropnode工具从一主多备的数据库中移除不需要的备机，最多可以删除到只剩下单机。
+
+## 注意事项
+
+- 从主备数据库实例中移除当前仍可连通的备机时，会自动停止目标备机上正在运行的数据库服务，并删除备机上的GRPC证书（证书位置：$GAUSSHOME/share/sslcert/grpc/），但是不会删除备机上的应用。
+- 如果删除后数据库实例中只剩下一个主机时，会提示建议重启当前主机，此时建议用户根据当前业务运行环境重启主机。
+- 如果目标备机在执行操作前处于不可连通的状态，需要用户在目标备机恢复后手动停止或删除目标备机的数据库服务，并删除备机上的GRPC证书（证书位置：$GAUSSHOME/share/sslcert/grpc/）。
+- 仅支持使用om方式安装的主备数据库实例中移除备机，不支持使用编译方式安装组建的主备数据库。
+- 当移除的备机处于同步复制模式时，如果执行删除命令的同时主机上存在事务操作，事务提交时会出现短暂卡顿，删除完成后事务处理可继续。
+- 当目标备机被移除后，如果暂时不确定是否需要目标备机，可以选择如下方法拒绝从目标备机的远程ssh连接，避免在目标备机上的误操作。
+
+方式一：在当前主机上使用root用户修改/etc/ssh/sshd_config文件，添加如下记录（如果已存在DenyUsers记录，请在后面追加）
+
+ `DenyUsers omm@10.11.12.13`
+
+ 修改后需要重启ssh服务使其生效，修改后限制从目标备机不能使用omm用户远程到该主机。
+
+方式二：在当前主机上将目标备机加入到/etc/hosts.deny文件中（例如：sshd:10.11.12.13:deny），拒绝从目标备机的远程ssh连接（对所有用户生效），此方法需要系统sshd服务绑定到libwrap库。
+
+- 当目标备机被移除后，如果不再需要目标备机，请在目标备机上使用**gs_uninstall -delete-data -L**命令单点卸载，请注意务必添加-L选项。
+
+- 当目标备机被移除后，如果需要以单机方式使用目标备机且保留原数据，请在目标备机上先执行**gs_guc set -D /gaussdb/data/dbnode -c “replconninfoX“** 其中 */gaussdb/data/dbnode* 表示数据目录，*replconninfoX* 表示主备集群中的除本节点外的其他节点，比如一主一备则需要配置 *replconninfo1*, 一主两备需要配置 *replconninfo1* 和 *replconninfo2*, 以此类推；如果无需保留原数据，请先执行**gs_uninstall -delete-data -L**命令卸载后重新安装。
+
+- 当目标备机被移除后，如果需要以备机方式使用目标备机，请参考gs_expansion命令重新将目标备机添加到集群中。
+
+## 前提条件
+
+- 删除备节点的操作只能在主节点上执行。
+- 操作过程中不允许同时在其他备节点上执行主备倒换或者故障倒换的操作。
+- 不允许同时在主节点上执行gs_expansion命令进行扩容。
+- 不允许同时执行2次相同的gs_dropnode命令。
+- 执行删除操作前，需要确保主节点和备节点之间建立好omm用户（数据库管理用户）的互信。
+- 需要使用数据库管理用户（比如omm）执行该命令。
+- 执行命令前需要通过source命令导入主机数据库的环境变量。如果当前数据库是分离环境变量方式安装，则source导入分离的环境变量。如果未进行分离，则需要source导入子用户的.bashrc配置文件。一般该文件路径为：/home/[user]/.bashrc.
+
+## 语法
+
+- 移除备机
+
+  ```bash
+  gs_dropnode -U USER -G GROUP -h hostlist
+  ```
+
+- 显示帮助信息
+
+  ```bash
+  gs_dropnode -? | --help
+  ```
+
+- 显示版本号信息
+
+  ```bash
+  gs_dropnode -V | --version
+  ```
+
+## 参数说明
+
+- -U
+
+  运行MogDB的操作系统用户名。
+
+- -G
+
+  运行MogDB的操作系统用户组。
+
+- -h
+
+  指定需要移除的备机的IP地址。如果有多个节点，节点之间以逗号分隔。
+
+- -?, -help
+
+  显示帮助信息。
+
+- -V, -version
+
+  显示版本号信息。
+
+## 示例
+
+使用gs_dropnode移除步骤。
+
+```bash
+$ gs_dropnode -U omm -G dbgrp -h 10.11.12.13
+The target node to be dropped is (['StandbyNode1'])
+Do you want to continue to drop the target node (yes/no)? yes
+[gs_dropnode]Start to drop nodes of the cluster.
+[gs_dropnode]Start to stop the target node StandbyNode3.
+[gs_dropnode]End of stop the target node StandbyNode3.
+[gs_dropnode]Start to backup parameter config file on PrimaryNode.
+[gs_dropnode]End to backup parameter config file on PrimaryNode.
+[gs_dropnode]The backup file of PrimaryNode is /tmp/gs_dropnode_backup20201119205019/parameter_PrimaryNode.tar
+[gs_dropnode]Start to parse parameter config file on PrimaryNode.
+[gs_dropnode]End to parse parameter config file on PrimaryNode.
+[gs_dropnode]Start to parse backup parameter config file on PrimaryNode.
+[gs_dropnode]End to parse backup parameter config file on PrimaryNode.
+[gs_dropnode]Start to set postgresql config file on PrimaryNode.
+[gs_dropnode]End of set postgresql config file on PrimaryNode.
+[gs_dropnode]Start to backup parameter config file on StandbyNode2.
+[gs_dropnode]End to backup parameter config file on StandbyNode2.
+[gs_dropnode]The backup file of StandbyNode2 is /tmp/gs_dropnode_backup20201119205019/parameter_StandbyNode2.tar
+[gs_dropnode]Start to parse parameter config file on StandbyNode2.
+[gs_dropnode]End to parse parameter config file on StandbyNode2.
+[gs_dropnode]Start to parse backup parameter config file on StandbyNode2.
+[gs_dropnode]End to parse backup parameter config file on StandbyNode2.
+[gs_dropnode]Start to set postgresql config file on StandbyNode2.
+[gs_dropnode]End of set postgresql config file on StandbyNode2.
+[gs_dropnode]Start to get repl slot on PrimaryNode.
+[gs_dropnode]Start to set repl slot on PrimaryNode.
+[gs_dropnode]End of set repl slot on PrimaryNode.
+[gs_dropnode]Start to set pg_hba config file on PrimaryNode.
+[gs_dropnode]End of set pg_hba config file on PrimaryNode.
+[gs_dropnode]Start to modify the cluster static conf.
+[gs_dropnode]End of modify the cluster static conf.
+[gs_dropnode]Success to drop the target nodes.
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/15-gs_probackup.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/15-gs_probackup.md
new file mode 100644
index 0000000000000000000000000000000000000000..fc0d4339e89f5915d4c7f8e19d16e5c57e75edc3
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/15-gs_probackup.md
@@ -0,0 +1,624 @@
+---
+title: gs_probackup
+summary: gs_probackup
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_probackup
+
+## 背景信息
+
+gs_probackup是一个用于管理MogDB数据库备份和恢复的工具。它对MogDB实例进行定期备份，以便在数据库出现故障时能够恢复服务器。
+
+- 可用于备份单机数据库或者主节点数据库，为物理备份。
+- 可备份外部目录的内容，如脚本文件、配置文件、日志文件、dump文件等。
+- 支持增量备份、定期备份和远程备份。
+- 可设置备份的留存策略。
+
+## 前提条件
+
+- 可以正常连接MogDB数据库。
+- 若要使用PTRACK增量备份，需在postgresql.conf中手动添加参数“enable_cbm_tracking = on”。
+- 为了防止xlog在传输结束前被清理，请适当调高postgresql.conf文件中wal_keep_segements的值。
+
+## 限制说明
+
+- 备份必须由运行数据库服务器的用户执行。
+- 备份和恢复的数据库服务器的主版本号必须相同。
+- 如果要通过ssh在远程模式下备份数据库，需要在本地和远程主机安装相同主版本的数据库，并通过ssh-copy-id remote_user@remote_host命令设置本地主机备份用户和远程主机数据库用户的无密码ssh连接。
+- 远程模式下只能执行add-instance、backup、restore子命令。
+- 使用restore子命令前，应先停止gaussdb进程。
+- 当存在用户自定义表空间时，备份的时候要加上 -external-dirs 参数，否则，该表空间不会被备份。
+- 当备份的规模比较大时，为了防止备份过程中timeout发生，请适当调整postgresql.conf文件的参数 session_timeout、wal_sender_timeout。并且在备份的命令行参数中适当调整参数-rw-timeout的值。
+- 恢复时，使用-T选项把备份中的外部目录重定向到新目录时，请同时指定参数-external-mapping。
+
+## 命令说明
+
+- 打印gs_probackup版本。
+
+  ```bash
+  gs_probackup -V|--version
+  gs_probackup version
+  ```
+
+- 显示gs_probackup命令的摘要信息。如果指定了gs_probackup的子命令，则显示可用于此子命令的参数的详细信息。
+
+  ```bash
+  gs_probackup -?|--help
+  gs_probackup help [command]
+  ```
+
+- 初始化备份路径_backup-path_中的备份目录，该目录将存储已备份的内容。如果备份路径_backup-path_已存在，则_backup-path_必须为空目录。
+
+  ```bash
+  gs_probackup init -B backup-path [--help]
+  ```
+
+- 在备份路径_backup-path_内初始化一个新的备份实例，并生成pg_probackup.conf配置文件，该文件保存了指定数据目录_pgdata-path_的gs_probackup设置。
+
+  ```bash
+  gs_probackup add-instance -B backup-path -D pgdata-path --instance=instance_name
+  [-E external-directories-paths]
+  [remote_options]
+  [--help]
+  ```
+
+- 在备份路径_backup-path_内删除指定实例相关的备份内容。
+
+  ```bash
+  gs_probackup del-instance -B backup-path --instance=instance_name
+  [--help]
+  ```
+
+- 将指定的连接、压缩、日志等相关设置添加到pg_probackup.conf配置文件中，或修改已设置的值。不推荐手动编辑pg_probackup.conf配置文件。
+
+  ```bash
+  gs_probackup set-config -B backup-path --instance=instance_name
+  [-D pgdata-path] [-E external-directories-paths] [--archive-timeout=timeout]
+  [--retention-redundancy=retention-redundancy] [--retention-window=retention-window] [--wal-depth=wal-depth]
+  [--compress-algorithm=compress-algorithm] [--compress-level=compress-level]
+  [-d dbname] [-h hostname] [-p port] [-U username]
+  [logging_options] [remote_options]
+  [--help]
+  ```
+
+- 将备份相关设置添加到backup.control配置文件中，或修改已设置的值。
+
+  ```bash
+  gs_probackup set-backup -B backup-path --instance=instance_name -i backup-id
+  [--note=text] [pinning_options]
+  [--help]
+  ```
+
+- 显示位于备份目录中的pg_probackup.conf配置文件的内容。可以通过指定-format=json选项，以json格式显示。默认情况下，显示为纯文本格式。
+
+  ```bash
+  gs_probackup show-config -B backup-path --instance=instance_name
+  [--format=plain|json]
+  [--help]
+  ```
+
+- 显示备份目录的内容。如果指定了instance_name和backup_id，则显示该备份的详细信息。可以通过指定-format=json选项，以json格式显示。默认情况下，备份目录的内容显示为纯文本格式。
+
+  ```bash
+  gs_probackup show -B backup-path
+  [--instance=instance_name [-i backup-id]] [--archive] [--format=plain|json]
+  [--help]
+  ```
+
+- 创建指定实例的备份。
+
+  ```bash
+  gs_probackup backup -B backup-path --instance=instance_name -b backup-mode
+  [-D pgdata-path] [-C] [-S slot-name] [--temp-slot] [--backup-pg-log] [-j threads_num] [--progress]
+  [--no-validate] [--skip-block-validation] [-E external-directories-paths] [--no-sync] [--note=text]
+  [--archive-timeout=timeout] [-t rwtimeout]
+  [logging_options] [retention_options] [compression_options]
+  [connection_options] [remote_options] [pinning_options]
+  [--help]
+  ```
+
+- 从备份目录_backup-path_中的备份副本恢复指定实例。如果指定了恢复目标选项，gs_probackup将查找最近的备份并将其还原到指定的恢复目标。否则，使用最近一次备份。
+
+  ```bash
+  gs_probackup restore -B backup-path --instance=instance_name
+  [-D pgdata-path] [-i backup_id] [-j threads_num] [--progress] [--force] [--no-sync] [--no-validate] [--skip-block-validation]
+  [--external-mapping=OLDDIR=NEWDIR] [-T OLDDIR=NEWDIR] [--skip-external-dirs] [-I incremental_mode]
+  [recovery_options] [remote_options] [logging_options]
+  [--help]
+  ```
+
+- 将指定的增量备份与其父完全备份之间的所有增量备份合并到父完全备份。父完全备份将接收所有合并的数据，而已合并的增量备份将作为冗余被删除。
+
+  ```bash
+  gs_probackup merge -B backup-path --instance=instance_name -i backup_id
+  [-j threads_num] [--progress] [logging_options]
+  [--help]
+  ```
+
+- 删除指定备份，或删除不满足当前保留策略的备份。
+
+  ```bash
+  gs_probackup delete -B backup-path --instance=instance_name
+  [-i backup-id | --delete-expired | --merge-expired | --status=backup_status]
+  [--delete-wal] [-j threads_num] [--progress]
+  [--retention-redundancy=retention-redundancy] [--retention-window=retention-window]
+  [--wal-depth=wal-depth] [--dry-run]
+  [logging_options]
+  [--help]
+  ```
+
+- 验证恢复数据库所需的所有文件是否存在且未损坏。如果未指定_instance_name_，gs_probackup将验证备份目录中的所有可用备份。如果指定_instance_name_而不指定任何附加选项，gs_probackup将验证此备份实例的所有可用备份。如果指定了_instance_name_并且指定_backup-id_或恢复目标相关选项，gs_probackup将检查是否可以使用这些选项恢复数据库。
+
+  ```bash
+  gs_probackup validate -B backup-path
+  [--instance=instance_name] [-i backup-id]
+  [-j threads_num] [--progress] [--skip-block-validation]
+  [--recovery-target-time=time | --recovery-target-xid=xid | --recovery-target-lsn=lsn | --recovery-target-name=target-name]
+  [--recovery-target-inclusive=boolean]
+  [logging_options]
+  [--help]
+  ```
+
+## 参数说明
+
+**通用参数**
+
+- command
+
+  gs_probackup除version和help以外的子命令：init、add-instance、del-instance、set-config、set-backup、show-config、show、backup、restore、merge、delete、validate。
+
+- -?, -help
+
+  显示gs_probackup命令行参数的帮助信息，然后退出。
+
+  子命令中只能使用-help，不能使用-?。
+
+- -V, -version
+
+  打印gs_probackup版本，然后退出。
+
+- -B *backup-path*, -backup-path=*backup-path*
+
+  备份的路径。
+
+  系统环境变量：$BACKUP_PATH
+
+- -D *pgdata-path*, -pgdata=*pgdata-path*
+
+  数据目录的路径。
+
+  系统环境变量：$PGDATA
+
+- -instance=*instance_name*
+
+  实例名。
+
+- -i *backup-id*, -backup-id=*backup-id*
+
+  备份的唯一标识。
+
+- -format=*format*
+
+  指定显示备份信息的格式，支持plain和json格式。
+
+  默认值：plain
+
+- -status=*backup_status*
+
+  删除指定状态的所有备份，包含以下状态：
+
+  - OK：备份已完成且有效。
+  - DONE：备份已完成但未经过验证。
+  - RUNNING：备份正在进行中。
+  - MERGING：备份正在合并中。
+  - DELETING：备份正在删除中。
+  - CORRUPT：部分备份文件已损坏。
+  - ERROR：由于意外错误，备份失败。
+  - ORPHAN：由于其父备份之一已损坏或丢失，备份无效。
+
+- -j *threads_num*, -threads=*threads_num*
+
+  设置备份、还原、合并进程的并行线程数。
+
+- -archive
+
+  显示WAL归档信息。
+
+- -progress
+
+  显示进度。
+
+- -note=*text*
+
+  给备份添加note。
+
+**备份相关参数**
+
+- -b *backup-mode*, -backup-mode=*backup-mode*
+
+  指定备份模式，支持FULL和PTRACK。
+
+  FULL：创建全量备份，全量备份包含所有数据文件。
+
+  PTRACK：创建PTRACK增量备份。
+
+- -C, -smooth-checkpoint
+
+  将检查点在一段时间内展开。默认情况下，gs_probackup会尝试尽快完成检查点。
+
+- -S *slot-name*, -slot=*slot-name*
+
+  指定WAL流处理的复制slot。
+
+- -temp-slot
+
+  在备份的实例中为WAL流处理创建一个临时物理复制slot，它确保在备份过程中，所有所需的WAL段仍然是可用的。
+
+  默认的slot名为pg_probackup_slot，可通过选项-slot/-S更改。
+
+- -backup-pg-log
+
+  将日志目录包含到备份中。此目录通常包含日志消息。默认情况下包含日志目录，但不包含日志文件。如果修改了默认的日志路径，需要备份日志文件时可使用-E参数进行备份，使用方法见下文。
+
+- -E *external-directories-paths*, -external-dirs=*external-directories-paths*
+
+  将指定的目录包含到备份中。此选项对于备份位于数据目录外部的脚本、sql转储和配置文件很有用。如果要备份多个外部目录，请在Unix上用冒号分隔它们的路径。
+
+  例如：-E /tmp/dir1:/tmp/dir2
+
+- -skip-block-validation
+
+  关闭块级校验，加快备份速度。
+
+- -no-validate
+
+  在完成备份后跳过自动验证。
+
+- -no-sync
+
+  不将备份文件同步到磁盘。
+
+- -archive-timeout=*timeout*
+
+  以秒为单位设置流式处理的超时时间。
+
+  默认值：300
+
+- -t rwtimeout
+
+  以秒为单位的连接的超时时间。
+
+  默认值: 120
+
+**恢复相关参数**
+
+- -I, -incremental-mode=none|checksum|lsn
+
+  若PGDATA中可用的有效页没有修改，则重新使用它们。
+
+  默认值：none
+
+- -external-mapping=*OLDDIR=NEWDIR*
+
+  在恢复时，将包含在备份中的外部目录从_OLDDIR_重新定位到_NEWDIR_目录。_OLDDIR_和_NEWDIR_都必须是绝对路径。如果路径中包含“=”，则使用反斜杠转义。此选项可为多个目录多次指定。
+
+- -T *OLDDIR=NEWDIR*, -tablespace-mapping=*OLDDIR=NEWDIR*
+
+  在恢复时，将表空间从_OLDDIR_重新定位到_NEWDIR_目录。_OLDDIR_和_NEWDIR_必须都是绝对路径。如果路径中包含“=”，则使用反斜杠转义。多个表空间可以多次指定此选项。此选项必须和-external-mapping一起使用。
+
+- -skip-external-dirs
+
+  跳过备份中包含的使用-external-dirs选项指定的外部目录。这些目录的内容将不会被恢复。
+
+- -skip-block-validation
+
+  跳过块级校验，以加快验证速度。在恢复之前的自动验证期间，将仅做文件级别的校验。
+
+- -no-validate
+
+  跳过备份验证。
+
+- -force
+
+  允许忽略备份的无效状态。如果出于某种原因需要从损坏的或无效的备份中恢复数据，可以使用此标志。请谨慎使用。
+
+**恢复目标相关参数(recovery_options)**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 当前不支持配置连续的WAL归档的PITR，因而使用这些参数会有一定限制，具体如下描述。 如果需要使用持续归档的WAL日志进行PITR恢复，请按照下面描述的步骤： 1. 将物理备份的文件替换目标数据库目录。 2. 删除数据库目录下pg_xlog/中的所有文件。 3. 将归档的WAL日志文件复制到pg_xlog文件中（此步骤可以省略，通过配置recovery.conf恢复命令文件中的restore_command项替代）。 4. 在数据库目录下创建恢复命令文件recovery.conf，指定数据库恢复的程度。 5. 启动数据库。 6. 连接数据库，查看是否恢复到希望预期的状态。若已经恢复到预期状态，通过pg_xlog_replay_resume()指令使主节点对外提供服务。
+
+- -recovery-target-lsn=*lsn*
+
+  指定要恢复到的lsn，当前只能指定备份的stop lsn。
+
+- -recovery-target-name=*target-name*
+
+  指定要将数据恢复到的已命名的保存点，保存点可以通过查看备份中recovery-name字段得到。
+
+- -recovery-target-time=*time*
+
+  指定要恢复到的时间，当前只能指定备份中的recovery-time。
+
+- -recovery-target-xid=*xid*
+
+  指定要恢复到的事务ID，当前只能指定备份中的recovery-xid。
+
+- -recovery-target-inclusive=*boolean*
+
+  当该参数指定为true时，恢复目标将包括指定的内容。
+
+  当该参数指定为false时，恢复目标将不包括指定的内容。
+
+  该参数必须和-recovery-target-name、-recovery-target-time、-recovery-target-lsn或-recovery-target-xid一起使用。
+
+**留存相关参数(retention_options)**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 可以和backup和delete命令一起使用这些参数。
+
+- -retention-redundancy=*retention-redundancy*
+
+  指定在数据目录中留存的完整备份数。必须为正整数。0表示禁用此设置。
+
+  默认值：0
+
+- -retention-window=*retention-window*
+
+  指定留存的天数。必须为正整数。0表示禁用此设置。
+
+  默认值：0
+
+- -wal-depth=*wal-depth*
+
+  每个时间轴上必须留存的执行PITR能力的最新有效备份数。必须为正整数。0表示禁用此设置。
+
+  默认值：0
+
+- -delete-wal
+
+  从任何现有的备份中删除不需要的WAL文件。
+
+- -delete-expired
+
+  删除不符合pg_probackup.conf配置文件中定义的留存策略的备份。
+
+- -merge-expired
+
+  将满足留存策略要求的最旧的增量备份与其已过期的父备份合并。
+
+- -dry-run
+
+  显示所有可用备份的当前状态，不删除或合并过期备份。
+
+**固定备份相关参数(pinning_options)**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 如果要将某些备份从已建立的留存策略中排除，可以和backup和set-backup命令一起使用这些参数。
+
+- -ttl=*interval*
+
+  指定从恢复时间开始计算，备份要固定的时间量。必须为正整数。0表示取消备份固定。
+
+  支持的单位：ms、 s、 min、 h、 d（默认为s）。
+
+  例如：-ttl=30d。
+
+- -expire-time=*time*
+
+  指定备份固定失效的时间戳。必须是ISO-8601标准的时间戳。
+
+  例如：-expire-time='2020-01-01 00:00:00+03'
+
+**日志相关参数(logging_options)**
+
+日志级别：verbose、log、info、warning、error和off。
+
+- -log-level-console=*log-level-console*
+
+  设置要发送到控制台的日志级别。每个级别都包含其后的所有级别。级别越高，发送的消息越少。指定off级别表示禁用控制台日志记录。
+
+  默认值：info
+
+- -log-level-file=*log-level-file*
+
+  设置要发送到日志文件的日志级别。每个级别都包含其后的所有级别。级别越高，发送的消息越少。指定off级别表示禁用日志文件记录。
+
+  默认值：off
+
+- -log-filename=*log-filename*
+
+  指定要创建的日志文件的文件名。文件名可以使用strftime模式，因此可以使用%-escapes指定随时间变化的文件名。
+
+  例如，如果指定了“pg_probackup-%u.log”模式，则pg_probackup为每周的每一天生成单独的日志文件，其中%u替换为相应的十进制数字，即pg_probackup-1.log表示星期一；pg_probackup-2.log表示星期二，以此类推。
+
+  如果指定了-log-level-file参数启用日志文件记录，则该参数有效。
+
+  默认值：“pg_probackup.log”
+
+- -error-log-filename=*error-log-filename*
+
+  指定仅用于error日志的日志文件名。指定方式与-log-filename参数相同。
+
+  此参数用于故障排除和监视。
+
+- -log-directory=*log-directory*
+
+  指定创建日志文件的目录。必须是绝对路径。此目录会在写入第一条日志时创建。
+
+  默认值：$BACKUP_PATH/log
+
+- -log-rotation-size=*log-rotation-size*
+
+  指定单个日志文件的最大大小。如果达到此值，则启动gs_probackup命令后，日志文件将循环，但help和version命令除外。0表示禁用基于文件大小的循环。
+
+  支持的单位：KB、MB、GB、TB（默认为KB）。
+
+  默认值：0
+
+- -log-rotation-age=*log-rotation-age*
+
+  单个日志文件的最大生命周期。如果达到此值，则启动gs_probackup命令后，日志文件将循环，但help和version命令除外。$BACKUP_PATH/log/log_rotation目录下保存最后一次创建日志文件的时间。0表示禁用基于时间的循环。
+
+  支持的单位：ms、 s、 min、 h、 d（默认为min）。
+
+  默认值：0
+
+**连接相关参数(connection_options)**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 可以和backup命令一起使用这些参数。
+
+- -d *dbname*, -pgdatabase=*dbname*
+
+  指定要连接的数据库名称。该连接仅用于管理备份进程，因此您可以连接到任何现有的数据库。如果命令行、PGDATABASE环境变量或pg_probackup.conf配置文件中没有指定此参数，则gs_probackup会尝试从PGUSER环境变量中获取该值。如果未设置PGUSER变量，则从当前用户名获取。
+
+  系统环境变量：$PGDATABASE
+
+- -h *hostname*, -pghost=*hostname*
+
+  指定运行服务器的系统的主机名。如果该值以斜杠开头，则被用作到Unix域套接字的路径。
+
+  系统环境变量：$PGHOST
+
+  默认值：local socket
+
+- -p *port*, -pgport=_p_*ort*
+
+  指定服务器正在侦听连接的TCP端口或本地Unix域套接字文件扩展名。
+
+  系统环境变量：$PGPORT
+
+  默认值：5432
+
+- -U *username*, -pguser=*username*
+
+  指定所连接主机的用户名。
+
+  系统环境变量：$PGUSER
+
+- -w, -no-password
+
+  不出现输入密码提示。如果主机要求密码认证并且密码没有通过其它形式给出，则连接尝试将会失败。 该选项在批量工作和不存在用户输入密码的脚本中很有帮助。
+
+- -W *password*, -password=*password*
+
+  指定用户连接的密码。如果主机的认证策略是trust，则不会对系统管理员进行密码验证，即无需输入-W选项；如果没有-W选项，并且不是系统管理员，则会提示用户输入密码。
+
+**压缩相关参数(compression_options)**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 可以和backup命令一起使用这些参数。
+
+- -compress-algorithm=*compress-algorithm*
+
+  指定用于压缩数据文件的算法。
+
+  取值包括zlib、pglz和none。如果设置为zlib或pglz，此选项将启用压缩。默认情况下，压缩功能处于关闭状态。
+
+  默认值：none
+
+- -compress-level=*compress-level*
+
+  指定压缩级别。取值范围: 0~9
+
+  - 0表示无压缩。
+  - 1表示压缩比最小，处理速度最快。
+  - 9表示压缩比最大，处理速度最慢。
+  - 可与-compress-algorithm选项一起使用。
+
+  默认值：1
+
+- -compress
+
+  以-compress-algorithm=zlib和-compress-level=1进行压缩。
+
+**远程模式相关参数(remote_options)**
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 通过SSH远程运行gs_probackup操作的相关参数。可以和add-instance、set-config、backup、restore命令一起使用这些参数。
+
+- -remote-proto=*protocol*
+
+  指定用于远程操作的协议。目前只支持SSH协议。取值包括：
+
+  ssh：通过SSH启用远程备份模式。这是默认值。
+
+  none：显式禁用远程模式。
+
+  如果指定了-remote-host参数，可以省略此参数。
+
+- -remote-host=*destination*
+
+  指定要连接的远程主机的IP地址或主机名。
+
+- -remote-port=*port*
+
+  指定要连接的远程主机的端口号。
+
+  默认值：22
+
+- -remote-user=*username*
+
+  指定SSH连接的远程主机用户。如果省略此参数，则使用当前发起SSH连接的用户。
+
+  默认值：当前用户
+
+- -remote-path=*path*
+
+  指定gs_probackup在远程系统的安装目录。
+
+  默认值：当前路径
+
+- -remote-lib=*libpath*
+
+  指定gs_probackup在远程系统安装的lib库目录。
+
+- -ssh-options=*ssh_options*
+
+  指定SSH命令行参数的字符串。
+
+  例如：-ssh-options='-c cipher_spec -F configfile'
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+  >
+  > - 如果因为网络临时故障等原因导致server端无应答,gs_probackup将在等待archive-timeout（默认300秒）后退出。
+  >
+  > - 如果备机lsn与主机有差别时，数据库会不停地刷以下log信息，此时应重新build备机。
+  >
+  >   ```bash
+  >   LOG: walsender thread shut down
+  >   LOG: walsender thread started
+  >   LOG: received wal replication command: IDENTIFY_VERSION
+  >   LOG: received wal replication command: IDENTIFY_MODE
+  >   LOG: received wal replication command: IDENTIFY_SYSTEM
+  >   LOG: received wal replication command: IDENTIFY_CONSISTENCE 0/D0002D8
+  >   LOG: remote request lsn/crc: [xxxxx] local max lsn/crc: [xxxxx]
+  >   ```
+
+## 备份流程
+
+1. 初始化备份目录。在指定的目录下创建backups/和wal/子目录，分别用于存放备份文件和WAL文件。
+
+   ```bash
+   gs_probackup init -B backup_dir
+   ```
+
+2. 添加一个新的备份实例。gs_probackup可以在同一个备份目录下存放多个数据库实例的备份。
+
+   ```bash
+   gs_probackup add-instance -B backup_dir -D data_dir --instance instance_name
+   ```
+
+3. 创建指定实例的备份。在进行增量备份之前，必须至少创建一次全量备份。
+
+   ```bash
+   gs_probackup backup -B backup_dir --instance instance_name -b backup_mode
+   ```
+
+4. 从指定实例的备份中恢复数据。
+
+   ```bash
+   gs_probackup restore -B backup_dir --instance instance_name -D pgdata-path -i backup_id
+   ```
+
+## 故障处理
+
+| 问题描述                                                     | 原因和解决方案                                               |
+| :----------------------------------------------------------- | :----------------------------------------------------------- |
+| ERROR: query failed: ERROR: canceling statement due to conflict with recovery（错误：查询失败：由于与恢复操作冲突，正在取消语句命令） | 原因：在备机上执行的操作正在访问存储行，主机上更改或者删除了对应的行，并将xlog在备机上重放，迫使备机上操作取消。<br />解决方案：<br />1. 适当增加如下配置参数的值<br />max_standby_archive_delay<br />max_standby_streaming_delay<br />2. 增加如下配置<br />hot_standby_feedback = on |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/16-gstrace.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/16-gstrace.md
new file mode 100644
index 0000000000000000000000000000000000000000..b42fdcf4a34f5cbba8f03ed550b5590f8273ec8e
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/16-gstrace.md
@@ -0,0 +1,98 @@
+---
+title: gstrace
+summary: gstrace
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gstrace
+
+## 功能介绍
+
+gstrace是MogDB提供的用来跟踪内核代码执行路径、记录内核数据结构、分析代码性能的工具。Trace的有限点位和数据在版本中被固化，无法动态添加和删除。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-warning.gif) **警告：**
+>
+> 1. 对内核dump指定内存变量的数据用于诊断分析，不存在直接指定任意寄存器或者内存地址的行为。读取的内存地址均是在开发阶段硬编码，没有任意地读取或者修改寄存器或内存的操作。
+> 2. Trace点可能涉及敏感数据，收集trace信息前需要同用户协商，授权和许可后方可收集。
+> 3. openGauss不会在敏感信息上打点，不会TRACE和用户相关的数据。
+> 4. Trace仅用于诊断目的，开启trace将对性能产生一定影响，影响的大小视负载的高低，trace的模块而不同。
+> 5. Trace工具的权限为0700，仅限于数据库用户读、写和执行。
+>
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 如果进程异常终止，/dev/shm/ 目录下将会有gstrace_trace_cfg_*残留，可以手动清除。
+
+## 语法
+
+```bash
+gstrace [start|stop|config|dump|detailcodepath|analyze] [-p <port>][-s <BUFFER_SIZE>] [-f <DUMP_FILE>] [-o <OUTPUT_FILE>] [-t <STEP_SIZE>]
+```
+
+## 参数说明
+
+**表 1** gs_trace参数说明
+
+| 参数           | 说明                                                         |
+| :------------- | :----------------------------------------------------------- |
+| start          | 开始记录trace。                                              |
+| stop           | 停止trace，释放存储信息的共享内存trace buffer。注意：trace buffer中已捕获trace信息会丢失。 |
+| config         | 显示trace的配置信息。                                        |
+| dump           | 将共享内存中的trace信息写入指定文件。若没有启动trace将报错。 |
+| detail         | 将dump出来的二进制文件解析成文本文件，显示trace点的线程、时间信息。 |
+| codepath       | 提取dump文件中的函数调用信息，按照调用栈的方式显示。         |
+| analyze        | 统计各个函数的执行次数、总耗时、平均耗时、最长耗时、最短耗时。 |
+| -p PORT        | 指定启动trace功能的实例侦听的端口号。                        |
+| -f DUMP_FILE   | 指定dump导出的trace文件。                                    |
+| -o OUTPUT_FILE | 指定写入的文件。                                             |
+| -t STEP_SIZE   | 指定分片分析的时间跨度（秒）,可选。将生成单独的{OUTPUT_FILE}.step文件。 |
+| -m MASK        | 指定哪些模块、函数需要追踪，如果参数为空，则追踪添加trace接口的所有模块的所有函数。<br />格式：[comp…][ALL].[func…][ALL]<br />描述：<br />- comp 是模块列表，使用‘,’分隔，例如：executer,opengauss。也可以使用序号，例如：executer,2。<br />- func 是function列表，使用‘,’ 分隔。 例如：sql_execute_ddl, sql_execute_dcl。也可以使用序号指代模块中第几个function，例如：2。<br />- 设置成ALL表示所有模块或所有function被trace。<br />示例：<br />- executer,opengauss.ALL ：所有定义定义在executer和opengauss模块下的function被trace。<br />- executer,opengauss.sql_execute_ddl ：定义在executer 下的Function sql_execute_ddl被trace. opengauss模块被忽略，因为下面没有该function 。<br />- executer,opengauss.1 ：定义在模块executer和opengauss下的第一个function被trace。<br />ALL.1,2 ：定义在所有模块下的第一，二个function被trace。 |
+| -s BUFFER_SIZE | 指定用于trace功能的共享内存大小，默认为1G。如果指定的BUFFER_SIZE小于最小值2048，系统将自动调整为最小值。如果指定的BUFFER_SIZE不是2^N（二的N次方），则向下对齐2^N；例如：指定BUFFER_SIZE=3072，由于2^11<3072<2^12，系统将调整为2048。 |
+
+## 示例
+
+1. 启动trace
+
+   ```bash
+   gstrace start -p 8000
+   ```
+
+2. 停止trace
+
+   ```bash
+   gstrace stop -p 8000
+   ```
+
+3. 查看trace配置
+
+   ```bash
+   gstrace config -p 8000
+   ```
+
+4. dump trace
+
+   ```bash
+   gstrace dump -p 8000 -o /data/8000.dump
+   ```
+
+5. 解析dump detail信息
+
+   ```bash
+   gstrace detail -f /data/8000.dump -o /data/8000.detail
+   ```
+
+6. 解析dump codepath
+
+   ```bash
+   gstrace codepath -f /data/8000.dump -o /data/8000.codepath
+   ```
+
+7. 分析全局性能
+
+   ```bash
+   gstrace analyze -f /data/8000.dump -o /data/8000.perf
+   ```
+
+8. 分析分片性能
+
+   ```bash
+   gstrace analyze -f /data/8000.dump -o /data/8000.perf -t 1
+   ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/17-kdb5_util.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/17-kdb5_util.md
new file mode 100644
index 0000000000000000000000000000000000000000..4ca6afd8f7ba796d45970d350c005e891c5fbf69
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/17-kdb5_util.md
@@ -0,0 +1,16 @@
+---
+title: kdb5_util
+summary: kdb5_util
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# kdb5_util
+
+## 功能介绍
+
+为MogDB认证服务Kerberos提供数据库管理操作的工具，可以新建、销毁、导入和导出数据库。
+
+## 参数说明
+
+Kerberos工具为开源第三方提供，具体参数说明请参考Kerberos官方文档：<https://web.mit.edu/kerberos/krb5-1.17/doc/admin/admin_commands/index.html>
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/18-kadmin-local.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/18-kadmin-local.md
new file mode 100644
index 0000000000000000000000000000000000000000..7606270cc83f961f85f6c95e866f50fa807f28cd
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/18-kadmin-local.md
@@ -0,0 +1,16 @@
+---
+title: kadmin.local
+summary: kadmin.local
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# kadmin.local
+
+## 功能介绍
+
+为MogDB认证服务Kerberos提供命令行接口，直接接入kdc服务的数据库，进行增加、删除、修改Kerberos用户等操作。
+
+## 参数说明
+
+Kerberos工具为开源第三方提供，具体参数说明请参考Kerberos官方文档：<https://web.mit.edu/kerberos/krb5-1.17/doc/admin/admin_commands/index.html>
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/19-kinit.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/19-kinit.md
new file mode 100644
index 0000000000000000000000000000000000000000..407514d1cb84204fd7b6c86981a63a284dc2a3d3
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/19-kinit.md
@@ -0,0 +1,16 @@
+---
+title: kinit
+summary: kinit
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# kinit
+
+## 功能介绍
+
+为MogDB认证服务Kerberos提供特定用户获取和缓存TGT能力。
+
+## 参数说明
+
+Kerberos工具为开源第三方提供，具体参数说明请参考Kerberos官方文档：<https://web.mit.edu/kerberos/krb5-1.17/doc/admin/admin_commands/index.html>
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/2-gs_backup.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/2-gs_backup.md
new file mode 100644
index 0000000000000000000000000000000000000000..3b7021ce78dc4fc3fb284b32b97d16aa7c6cfd46
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/2-gs_backup.md
@@ -0,0 +1,154 @@
+---
+title: gs_backup
+summary: gs_backup
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_backup
+
+## 背景信息
+
+MogDB部署成功后，在数据库运行的过程中，会遇到各种问题及异常状态。MogDB提供了gs_backup工具帮助MogDB备份、恢复重要数据、显示帮助信息和版本号信息。
+
+## 前提条件
+
+- 可以正常连接MogDB数据库。
+- 在进行还原时，需要保证各节点备份目录中存在备份文件。
+- 需以操作系统用户omm执行gs_backup命令。
+
+## 语法
+
+- 备份数据库主机
+
+  ```bash
+  gs_backup -t backup --backup-dir=BACKUPDIR [-h HOSTNAME] [--parameter] [--binary] [--all] [-l LOGFILE]
+  ```
+
+- 恢复数据库主机
+
+  ```bash
+  gs_backup -t restore --backup-dir=BACKUPDIR [-h HOSTNAME] [--parameter] [--binary] [--all] [-l LOGFILE] [--force]
+  ```
+
+- 显示帮助信息
+
+  ```bash
+  gs_backup -? | --help
+  ```
+
+- 显示版本号信息
+
+  ```bash
+  gs_backup -V | --version
+  ```
+
+## 参数说明
+
+gs_backup参数可以分为如下几类：
+
+- 备份数据库主机参数：
+
+  - -h
+
+    指定存储备份文件的主机名称。
+
+    取值范围: 主机名称。如果不指定主机名称，则备份当前集群。
+
+  - -backup-dir=BACKUPDIR
+
+    备份文件保存路径。
+
+  - -parameter
+
+    备份参数文件，不指定-parameter、-binary、-all参数时默认只备份参数文件。
+
+  - -binary
+
+    备份app目录下的二进制文件。
+
+  - -all
+
+    备份app目录下的二进制文件、pg_hba.conf和postgsql.conf文件。
+
+  - -l
+
+    指定日志文件及存放路径。
+
+    默认值：$GAUSSLOG/om/gs_backup-YYYY-MM-DD_hhmmss.log
+
+- 恢复数据库主机参数：
+
+  - -h
+
+    指定需要恢复主机的名称。
+
+    取值范围: 主机名称。如果不指定主机，则恢复对应的备份节点。
+
+  - -backup-dir=BACKUPDIR
+
+    恢复文件提取路径。
+
+  - -parameter
+
+    恢复参数文件，不指定-parameter、-binary、-all参数时默认只恢复参数文件。
+
+  - -binary
+
+    恢复二进制文件。
+
+  - -all
+
+    恢复二进制和参数文件。
+
+  - -l
+
+    指定日志文件及存放路径。
+
+    默认值：$GAUSSLOG/om/gs_backup-YYYY-MM-DD_hhmmss.log
+
+  - -force
+
+    节点的静态文件丢失之后强行restore，仅限-all或者-binary参数使用时才生效。
+
+- 其他参数：
+
+  - -?, -help
+
+    显示帮助信息。
+
+  - -V, -version
+
+    显示版本号信息。
+
+  - -t
+
+    指定操作类型。
+
+    取值范围: backup或者restore。
+
+## 示例
+
+- 使用gs_backup脚本备份数据库主机。
+
+  ```bash
+  gs_backup -t backup --backup-dir=/opt/software/gaussdb/backup_dir -h plat1 --parameter
+  Backing up MogDB.
+  Parsing configuration files.
+  Successfully parsed the configuration file.
+  Performing remote backup.
+  Remote backup succeeded.
+  Successfully backed up MogDB.
+  ```
+
+- 使用gs_backup脚本恢复数据库主机。
+
+  ```bash
+  gs_backup -t restore --backup-dir=/opt/software/gaussdb/backup_dir -h plat1 --parameter
+  Restoring MogDB.
+  Parsing the configuration file.
+  Successfully parsed configuration files.
+  Performing remote restoration.
+  Remote restoration succeeded.
+  Successfully restored MogDB.
+  ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/20-klist.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/20-klist.md
new file mode 100644
index 0000000000000000000000000000000000000000..73c5420cdbee6846095093f4e00bdfdce4f4cf63
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/20-klist.md
@@ -0,0 +1,16 @@
+---
+title: klist
+summary: klist
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# klist
+
+## 功能介绍
+
+为MogDB认证服务Kerberos提供列出凭证缓存中的用户和票据能力。
+
+## 参数说明
+
+Kerberos工具为开源第三方提供，具体参数说明请参考Kerberos官方文档：<https://web.mit.edu/kerberos/krb5-1.17/doc/admin/admin_commands/index.html>
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/21-krb5kdc.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/21-krb5kdc.md
new file mode 100644
index 0000000000000000000000000000000000000000..6f1851fd5fdac8d9ef221cd2140bbf6b5ddc1882
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/21-krb5kdc.md
@@ -0,0 +1,16 @@
+---
+title: krb5kdc
+summary: krb5kdc
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# krb5kdc
+
+## 功能介绍
+
+为MogDB认证服务Kerberos提供列认证和秘钥管理服务。
+
+## 参数说明
+
+Kerberos工具为开源第三方提供，具体参数说明请参考Kerberos官方文档：<https://web.mit.edu/kerberos/krb5-1.17/doc/admin/admin_commands/index.html>
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/22-kdestroy.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/22-kdestroy.md
new file mode 100644
index 0000000000000000000000000000000000000000..8c0bfd4bbc73e50a1659232704e416ab5de09014
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/22-kdestroy.md
@@ -0,0 +1,16 @@
+---
+title: kdestroy
+summary: kdestroy
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# kdestroy
+
+## 功能介绍
+
+为MogDB认证服务Kerberos提供销毁用户的授权票据操作。
+
+## 参数说明
+
+Kerberos工具为开源第三方提供，具体参数说明请参考Kerberos官方文档：<https://web.mit.edu/kerberos/krb5-1.17/doc/admin/admin_commands/index.html>
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/23-pg_config.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/23-pg_config.md
new file mode 100644
index 0000000000000000000000000000000000000000..f46885bf6c03065ac1e7f70f873759ed2424f130
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/23-pg_config.md
@@ -0,0 +1,118 @@
+---
+title: pg_config
+summary: pg_config
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# pg_config
+
+## 功能介绍
+
+通过pg_config工具打印的当前所安装数据库的配置参数信息，可用于找到与数据库相关的软件包所对应的头文件和库。
+
+## 语法
+
+```bash
+pg_config [option...]
+```
+
+## 参数说明
+
+pg_config工具支持下面一个或多个选项，如果给出多于一个选项，那么信息以该顺序打印，每行一条。 如果没有给出选项，则打印所有可获得的信息，连着标签一起打印。
+
+- -bindir
+
+  打印用户可执行文件的路径。 比如，可以用这个找psql程序。 通常这也是pg_config程序存在的路径。
+
+- -docdir
+
+  打印文档文件的位置。
+
+- -htmldir
+
+  输出HTML文档文件的位置。
+
+- -includedir
+
+  打印客户端接口C头文件的路径。
+
+- -pkgincludedir
+
+  打印其它C头文件的位置。
+
+- -includedir-server
+
+  打印那些做服务器编程时使用的C头文件的位置。
+
+- -libdir
+
+  打印目标代码库的路径。
+
+- -pkglibdir
+
+  打印动态加载的模块的位置，或者服务器在哪里寻找他们。 其它体系相关的数据文件可能也放在这个目录里。
+
+- -localedir
+
+  打印区域支持文件的位置。如果在编译数据库的时候没有配置区域支持， 则其值为空字符串。
+
+- -mandir
+
+  打印手册页的位置。
+
+- -sharedir
+
+  打印体系无关的支持文件的位置。
+
+- -sysconfdir
+
+  打印系统范围的配置文件位置。
+
+- -pgxs
+
+  打印扩展makefiles文件的位置。
+
+- -configure
+
+  打印配置和编译数据库时给configure脚本传递的选项， 用于复制相同配置， 或者找出二进制包是用哪些选项编译的。 不过请注意二进制包通常包含供应商提供的补丁。
+
+- -cc
+
+  打印用于编译数据库的CC变量的数值。 这个选项显示使用的C编译器。
+
+- -cppflags
+
+  打印用于编译数据库的CPPFLAGS变量的数值。 这个选项显示在预处理的时候所需要的C编译器开关（通常是-I开关）。
+
+- -cflags
+
+  打印编译数据库时使用的CFLAGS变量的数值。 这个选项显示C编译器开关。
+
+- -cflags_sl
+
+  打印编译数据库时使用的CFLAGS_SL变量的数值。 这个选项显示了编译共享库的额外的C编译器开关。
+
+- -ldflags
+
+  打印编译数据库时使用的LDFLAGS变量的数值。 它显示了链接器的开关。
+
+- -ldflags_ex
+
+  输出用于创建数据库的LDFLAGS_EX变量的值。 这显示用于构建可执行文件的链接器开关。
+
+- -ldflags_sl
+
+  打印编译数据库时使用的LDFLAGS_SL变量的数值。 它显示了用于编译共享库的链接器的开关。
+
+- -libs
+
+  打印编译数据库时使用的LIBS变量的数值。 其内容通常包含连接到数据库的外部库的-l开关。
+
+- -version
+
+  打印数据库的版本。
+
+- -?, -help
+
+  显示关于pg_config命令行参数的帮助文件，并且退出。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/24-pg_controldata.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/24-pg_controldata.md
new file mode 100644
index 0000000000000000000000000000000000000000..321d8d1c272920c60166c90a0fff1c45b758ae83
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/24-pg_controldata.md
@@ -0,0 +1,50 @@
+---
+title: pg_controldata
+summary: pg_controldata
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# pg_controldata
+
+## 功能介绍
+
+pg_controldata工具用来显示数据库目录下control文件的信息。
+
+## 前提条件
+
+确保数据目录正确，以及相应数据目录下的pg_control文件存在。
+
+## 语法
+
+- 查看control文件信息
+
+  ```bash
+  pg_controldata DATADIR
+  ```
+
+- 显示版本号信息
+
+  ```bash
+  pg_controldata -V | --version
+  ```
+
+- 显示帮助信息
+
+  ```bash
+  pg_controldata -? | --help
+  ```
+
+## 参数说明
+
+- DATADIR
+
+  查看control文件信息时所用的参数，DATADIR为实例对应的数据库目录。
+
+- -V, -version
+
+  显示版本信息。
+
+- -?,-help
+
+  打印帮助信息。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/24.1-pg_recvlogical.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/24.1-pg_recvlogical.md
new file mode 100644
index 0000000000000000000000000000000000000000..3a5bc3d8221334234702b2340c900d60649b95ff
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/24.1-pg_recvlogical.md
@@ -0,0 +1,153 @@
+---
+title: pg_recvlogical
+summary: pg_recvlogical
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# pg_recvlogical
+
+## 功能介绍
+
+pg_recvlogical工具通过连接指定的节点，创建或删除逻辑复制槽，以及持续、实时的从该节点获取逻辑解码中间结果，输出到文件或标准输出。
+
+## 语法
+
+```bash
+pg_recvlogical [OPTION]...
+```
+
+其中，逻辑复制槽行为参数为必选参数，必须指定一个。其余参数为可选参数，如不指定，将会读取默认值。
+
+## 参数说明
+
+- 逻辑复制槽行为参数：必选参数。
+
+  - -create
+
+    创建一个新的逻辑复制槽。
+
+  - -start
+
+    启动该逻辑复制槽的流复制。
+
+  - -drop
+
+    删除一个逻辑复制槽。
+
+- 连接参数：
+
+  - -d, -dbname=DBNAME
+
+    连接的目标数据库名。
+
+  - -h, -host=HOSTNAME
+
+    连接的目标主机名或socket。
+
+  - -p, -port=PORT
+
+    连接的目标DN的HA端口号。
+
+  - -U, -username=NAME
+
+    连接目标库所使用的用户名。
+
+  - -w, -no-password
+
+    不使用密码进行连接。
+
+  - -W, -password
+
+    使用指定密码进行连接。
+
+- 复制参数：
+
+  - -F -fsync-interval=INTERVAL
+
+    同步到目标输出文件的间隔时间。
+
+    单位为秒，默认值10。
+
+  - -o, -option=NAME[=VALUE]
+
+    指定向逻辑复制槽的输出插件添加参数。
+
+    参数的取值为：include-xids、skip-empty-xacts、include-timestamp。
+
+    详细请参见《开发者指南》中“SQL参考 &gt; 函数和操作符 &gt; 系统管理函数 &gt; 逻辑复制函数 &gt; options”章节。
+
+  - -P, -plugin=PLUGIN
+
+    指定使用的逻辑复制槽输出插件。
+
+    默认值为mppdb_decoding。
+
+  - -s, -status-interval=INTERVAL
+
+    发送的心跳包间隔时间。
+
+    单位为秒，默认值10。
+
+  - -S, -slot=SLOT
+
+    指定逻辑复制槽的名称。
+
+  - -I, -startpos=PTR
+
+    当使用已有逻辑复制槽时，指定初始复制的LSN位置。
+
+- 其它参数:
+
+  - -f, -file=FILE
+
+    设置输出到指定文件。
+
+    直接使用“-”表示输出到stdout。
+
+  - -n, -no-loop
+
+    指定此参数，连接失败后不重试。
+
+  - -v, -verbose
+
+    输出详细信息。
+
+  - -V, -version
+
+    输出版本信息，随后立即退出。
+
+  - -?, -help
+
+    输出帮助信息，随后立即退出。
+
+## 示例
+
+1. 创建名为test_slot的逻辑复制槽。
+
+   ```bash
+   pg_recvlogical -d postgres -S test_slot -p 26000 --create
+   ```
+
+2. 开启流式解码，结果输出到stdout。
+
+   ```bash
+   pg_recvlogical -d postgres -S test_slot -p 26000 --start -v -f -
+   pg_recvlogical: starting log streaming at 0/0 (slot test_slot)
+   pg_recvlogical: initiated streaming
+   pg_recvlogical: confirming write up to 0/0, flush to 0/0 (slot test_slot)
+   pg_recvlogical: confirming write up to 0/2A342E8, flush to 0/2A342E8 (slot test_slot)
+   pg_recvlogical: confirming write up to 0/2A34320, flush to 0/2A34320 (slot test_slot)
+   pg_recvlogical: confirming write up to 0/2A34320, flush to 0/2A34320 (slot test_slot)
+   BEGIN 16039
+   table public.t: INSERT: a[integer]:4 b[integer]:4
+   COMMIT 16039
+   pg_recvlogical: confirming write up to 0/2A34450, flush to 0/2A34450 (slot test_slot)
+   pg_recvlogical: confirming write up to 0/2A34450, flush to 0/2A34450 (slot test_slot)
+   ```
+
+3. 删除逻辑复制槽。
+
+   ```bash
+   pg_recvlogical -d postgres -S test_slot -p 26000 --drop
+   ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/25-pg_resetxlog.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/25-pg_resetxlog.md
new file mode 100644
index 0000000000000000000000000000000000000000..5d929190369d9fc9b230274b2ab0e35ff8a44c7f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/25-pg_resetxlog.md
@@ -0,0 +1,72 @@
+---
+title: pg_resetxlog
+summary: pg_resetxlog
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# pg_resetxlog
+
+## 功能介绍
+
+pg_resetxlog是一个重新设置数据库事务文件的工具。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-caution.gif) **注意：** 通过pg_resetxlog重新设置之前，需要先停止数据库。
+
+## 前提条件
+
+保证数据库目录存在且路径正确。
+
+## 语法
+
+```bash
+pg_resetxlog [OPTION]... DATADIR
+```
+
+## 参数说明
+
+OPTION取值如下所示：
+
+- DATADIR
+
+  需要修改的数据库目录，确保路径正确。
+
+- -e XIDEPOCH
+
+  设置下一个事务id。
+
+- -f
+
+  强制更新。
+
+- -l xlogfile
+
+  为新的事务日志指定最小的WAL起始位置。
+
+- -m XID
+
+  设置下一个multitransaction ID。
+
+- -n
+
+  不更新，仅显示配置文件的值。
+
+- -o OID
+
+  设置下一个OID。
+
+- -O OFFSET
+
+  设置下一个multitransaction的偏移量。
+
+- -V, -version
+
+  显示版本信息。
+
+- -x XID
+
+  设置下一个事务ID。
+
+- -?, -help
+
+  打印帮助信息。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/26-pg_archivecleanup.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/26-pg_archivecleanup.md
new file mode 100644
index 0000000000000000000000000000000000000000..b69d7a0339a932d4d58beb3b5704fa1e780d46f7
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/26-pg_archivecleanup.md
@@ -0,0 +1,58 @@
+---
+title: pg_archivecleanup
+summary: pg_archivecleanup
+author: Zhang Cuiping
+date: 2021-11-17
+---
+
+# pg_archivecleanup
+
+## 功能介绍
+
+pg_archivecleanup是一个用于清理旧的归档日志的工具。
+
+## 语法
+
+```bash
+pg_archivecleanup [OPTION]... ARCHIVELOCATION OLDESTKEPTWALFILE
+```
+
+## 参数说明
+
+- -d
+
+  在stderr上打印调试日志。
+
+- -n
+
+  打印将要删除的文件名。
+
+- -V,-version
+
+  打印pg_archivecleanup的版本并退出。
+
+- -x extension
+
+  当该程序用作单独的工具时，提供一个扩展选项，只选择对应扩展名格式的文件。
+
+- -?,-help
+
+  显示关于pg_archivecleanup命令行参数的帮助信息。
+
+## 示例
+
+删除比000000010000000000000010更早的日志
+
+```bash
+pg_archivecleanup [OPTION]... ARCHIVELOCATION OLDESTKEPTWALFILE
+```
+
+## 扩展应用
+
+备机恢复时，在recovery.conf里配置archive_cleanup_command参数。
+
+```bash
+archive_cleanup_command = 'pg_archivecleanup /mnt/server/archiverdir %r'
+```
+
+恢复完成后从归档目录中清除不再需要的文件。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/27-pssh.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/27-pssh.md
new file mode 100644
index 0000000000000000000000000000000000000000..1d8f8fd71935828e3b84b1367fe49acdd2cffccf
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/27-pssh.md
@@ -0,0 +1,68 @@
+---
+title: pssh
+summary: pssh
+author: Zhang Cuiping
+date: 2021-11-17
+---
+
+# pssh
+
+## 基本功能
+
+用于执行数据库节点间的访问，发送命令给远程节点。
+
+## 语法
+
+```bash
+python3 pssh [OPTIONS]
+```
+
+## 参数说明
+
+- -help
+
+  显示帮助信息。
+
+- -H HOSTNAME
+
+  主机列表。
+
+- -h HOSTFILE
+
+  写入主机列表的文件全路径。
+
+- -t TIMEOUT
+
+  连接超时时间，单位秒，默认300s。
+
+- -p PARALLEL
+
+  最大并行个数，默认32。
+
+- -o OUTDIR
+
+  执行结果输出全文件路径。
+
+- -e ERRDIR
+
+  错误信息输出全文件路径。
+
+- -P
+
+  线上远端主机执行的命令。
+
+- -s
+
+  显示执行结果。
+
+- -x EXTRA
+
+  额外的命令行参数。
+
+- -i
+
+  显示所有节点的输出和错误。
+
+- -O OPT
+
+  补充的线下模式ssh的参数。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/28-pscp.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/28-pscp.md
new file mode 100644
index 0000000000000000000000000000000000000000..882f3b1b4ca29258a9626055f458360334799a14
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/28-pscp.md
@@ -0,0 +1,72 @@
+---
+title: pscp
+summary: pscp
+author: Zhang Cuiping
+date: 2021-11-17
+---
+
+# pscp
+
+## 基本功能
+
+用于执行数据库节点间的文件传输。
+
+## 语法
+
+```bash
+python3 pscp [OPTIONS]
+```
+
+## 参数说明
+
+- -help
+
+  显示帮助信息。
+
+- -H HOSTNAME
+
+  主机列表。
+
+- -h HOSTFILE
+
+  写入主机列表的文件全路径。
+
+- -t TIMEOUT
+
+  连接超时时间，单位秒，默认300s。
+
+- -p PARALLEL
+
+  最大并行个数，默认32。
+
+- -o OUTDIR
+
+  执行结果输出全文件路径。
+
+- -e ERRDIR
+
+  错误信息输出全文件路径。
+
+- -r
+
+  递归复制目录。
+
+- -v
+
+  打开诊断消息。
+
+- -s
+
+  显示执行结果。
+
+- -x EXTRA
+
+  额外的命令行参数。
+
+- -i
+
+  显示所有节点的输出和错误。
+
+- -O OPT
+
+  补充的线下模式scp的参数。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/29-transfer.py.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/29-transfer.py.md
new file mode 100644
index 0000000000000000000000000000000000000000..ec7f1df665dcd4b6c76dc1f323278272c737ad9d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/29-transfer.py.md
@@ -0,0 +1,60 @@
+---
+title: transfer.py
+summary: transfer.py
+author: Zhang Cuiping
+date: 2021-11-17
+---
+
+# transfer.py
+
+## 功能介绍
+
+在非单节点模式下，可以通过transfer.py工具将全文检索所使用的词典文件和PostGIS插件所需的文件发送到其他节点。
+
+## 前提条件
+
+- 执行该工具前，需确保在$GAUSSHOME目录下存在以下四个文件，否则会报错，错误码为52200。
+  - script/gspylib/common/DbClusterInfo.py。
+  - script/gspylib/common/Common.py。
+  - script/gspylib/common/GaussLog.py。
+  - script/gspylib/threads/SshTool.py。
+- $GPHOME环境变量配置正确。
+
+## 语法
+
+- 将sourcefile发送到所有节点的destinationpath路径。
+
+  ```bash
+  transfer.py 1 sourcefile destinationpath
+  ```
+
+- 将sourcefile发送到pgxc_node_name的standby节点的相同路径下。
+
+  ```bash
+  transfer.py 2 sourcefile pgxc_node_name
+  ```
+
+- 显示帮助信息。
+
+  ```bash
+  transfer.py -? | --help
+  ```
+
+## 参数说明
+
+- OPTION取值如下所示：
+
+  - 1：将当前文件发送到所有节点的目标文件路径下。
+  - 2：将当前文件发送到目标节点的standby节点的相同路径下。
+
+- sourcefile
+
+  被发送的源文件路径。
+
+- destinationpath
+
+  目标文件路径。
+
+- pgxc_node_name
+
+  目标节点名。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/3-gs_basebackup.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/3-gs_basebackup.md
new file mode 100644
index 0000000000000000000000000000000000000000..a3c30c7a470cf216d20acea62065e856f3189b47
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/3-gs_basebackup.md
@@ -0,0 +1,164 @@
+---
+title: gs_basebackup
+summary: gs_basebackup
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_basebackup
+
+## 背景信息
+
+MogDB部署成功后，在数据库运行的过程中，会遇到各种问题及异常状态。MogDB提供了gs_basebackup工具做基础的物理备份。gs_basebackup的实现目标是对服务器数据库文件的二进制进行拷贝，其实现原理使用了复制协议。远程执行gs_basebackup时，需要使用系统管理员账户。gs_basebackup当前支持热备份模式和压缩格式备份模式。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - gs_basebackup仅支持主机和备机的全量备份，不支持增量。
+> - gs_basebackup当前支持热备份模式和压缩格式备份模式。
+> - 若打开增量检测点功能且打开双写，gs_basebackup也会备份双写文件。
+> - gs_basebackup在备份包含绝对路径的表空间时，如果在同一台机器上进行备份，可以通过tablespace-mapping重定向表空间路径，或使用归档模式进行备份。
+> - 若pg_xlog目录为软链接，备份时将不会建立软链接，会直接将数据备份到目的路径的pg_xlog目录下。
+> - 备份过程中收回用户备份权限，可能导致备份失败，或者备份数据不可用。
+> - 如果因为网络临时故障等原因导致Server端无法应答，gs_basebackup将在最长等待120秒后退出。
+
+## 前提条件
+
+- 可以正常连接MogDB数据库。
+- 备份过程中用户权限没有被回收。
+- pg_hba.conf中需要配置允许复制链接，且该连接必须由一个系统管理员建立。
+- 如果xlog传输模式为stream模式，需要配置max_wal_senders的数量，至少有一个可用。
+- 如果xlog传输模式为fetch模式，有必要把wal_keep_segments参数设置得足够高，这样在备份末尾之前日志不会被移除。
+- 在进行还原时，需要保证各节点备份目录中存在备份文件，若备份文件丢失，则需要从其他节点进行拷贝。
+
+## 语法
+
+- 显示帮助信息
+
+  ```bash
+  gs_basebackup -? | --help
+  ```
+
+- 显示版本号信息
+
+  ```bash
+  gs_basebackup -V | --version
+  ```
+
+## 参数说明
+
+gs_basebackup参数可以分为如下几类：
+
+- -D directory
+
+  备份文件输出的目录，必选项。
+
+- 常用参数：
+
+  - -c，-checkpoint=fast|spread
+
+    设置检查点模式为fast或者spread（默认）。
+
+  - -l，-label=LABEL
+
+    为备份设置标签。
+
+  - -P，-progress
+
+    启用进展报告。
+
+  - -v， -verbose
+
+    启用冗长模式。
+
+  - -V， -version
+
+    打印版本后退出。
+
+  - -?，-help
+
+    显示gs_basebackup命令行参数。
+
+  - -T，-tablespace-mapping=olddir=newdir
+
+    在备份期间将目录olddir中的表空间重定位到newdir中。为使之有效，olddir必须正好匹配表空间所在的路径（但如果备份中没有包含olddir中的表空间也不是错误）。olddir和newdir必须是绝对路径。如果一个路径凑巧包含了一个=符号，可用反斜线对它转义。对于多个表空间可以多次使用这个选项。
+
+  - -F，-format=plain|tar
+
+    设置输出格式为plain（默认）或者tar。没有设置该参数的情况下，默认-format=plain。plain格式把输出写成平面文件，使用和当前数据目录和表空间相同的布局。当集簇没有额外表空间时，整个数据库将被放在目标目录中。如果集簇包含额外的表空间，主数据目录将被放置在目标目录中，但是所有其他表空间将被放在它们位于服务器上的相同的绝对路径中。tar模式将输出写成目标目录中的 tar 文件。主数据目录将被写入到一个名为base.tar的文件中，并且其他表空间将被以其 OID 命名。生成的tar包，需要用gs_tar命令解压。
+
+  - -X， -xlog-method=fetch|stream
+
+    设置xlog传输方式。没有设置该参数的情况下，默认-xlog-method=stream。在备份中包括所需的预写式日志文件（WAL文件）。这包括所有在备份期间产生的预写式日志。fetch方式在备份末尾收集预写式日志文件。因此，有必要把wal_keep_segments参数设置得足够高，这样在备份末尾之前日志不会被移除。如果在要传输日志时它已经被轮转，备份将失败并且是不可用的。stream方式在备份被创建时流传送预写式日志。这将开启一个到服务器的第二连接并且在运行备份时并行开始流传输预写式日志。因此，它将使用最多两个由max_wal_senders参数配置的连接。只要客户端能保持接收预写式日志，使用这种模式不需要在主控机上保存额外的预写式日志。
+
+  - -x，-xlog 使用这个选项等效于和方法fetch一起使用-X。
+
+  - -Z -compress=level
+
+    启用对 tar 文件输出的 gzip 压缩，并且制定压缩级别（0 到 9，0 是不压缩，9 是最佳压缩）。只有使用 tar 格式时压缩才可用，并且会在所有tar文件名后面自动加上后缀.gz。
+
+  - -z
+
+    启用对 tar 文件输出的 gzip 压缩，使用默认的压缩级别。只有使用 tar 格式时压缩才可用，并且会在所有tar文件名后面自动加上后缀.gz。
+
+  - -t，-rw-timeout
+
+    设置备份期间checkpoint的时间限制，默认限制时间为120s。当数据库全量checkpoint耗时较长时，可以适当增大rw-timeout限制时间。
+
+- 连接参数
+
+  - -h, -host=HOSTNAME
+
+    指定正在运行服务器的主机名或者Unix域套接字的路径。
+
+  - -p，-port=PORT
+
+    指定数据库服务器的端口号。
+
+    可以通过port参数修改默认端口号。
+
+  - -U，-username=USERNAME
+
+    指定连接数据库的用户。
+
+  - -s, -status-interval=INTERVAL
+
+    发送到服务器的状态包的时间（以秒为单位）。
+
+  - -w,-no-password
+
+    不出现输入密码提示。
+
+  - -W, -password
+
+    当使用-U参数连接本地数据库或者连接远端数据库时，可通过指定该选项出现输入密码提示。
+
+## 示例
+
+```bash
+gs_basebackup -D /home/test/trunk/install/data/backup -h 127.0.0.1 -p 21233
+INFO:  The starting position of the xlog copy of the full build is: 0/1B800000. The slot minimum LSN is: 0/1B800000.
+```
+
+## 从备份文件恢复数据
+
+当数据库发生故障时需要从备份文件进行恢复。因为gs_basebackup是对数据库按二进制进行备份，因此恢复时可以直接拷贝替换原有的文件，或者直接在备份的库上启动数据库。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 若当前数据库实例正在运行，直接从备份文件启动数据库可能会存在端口冲突，这时需要修改配置文件的port参数，或者在启动数据库时指定一下端口。
+> - 若当前备份文件为主备数据库，可能需要修改一下主备之间的复制连接。即配置文件中的postgresql.conf中的replconninfo1，replconninfo2等。
+> - 若配置文件postgresql.conf的参数data_directory打开且有配置，当使用备份目录启动数据库时候，data_directory和备份目录不同会导致启动失败。可以修改data_directory的值为新的数据目录，或者注释掉该参数。
+
+若要在原库的地方恢复数据库，参考步骤如下：
+
+1. 停止数据库服务器，具体操作请参见《管理员指南》。
+2. 将原数据库和所有表空间复制到另外一个位置, 以备后面需要。
+3. 清理原库中的所有或部分文件。
+4. 使用数据库系统用户权限从备份中还原需要的数据库文件。
+5. 若数据库中存在链接文件，需要修改使其链接到正确的文件。
+6. 重启数据库服务器，并检查数据库内容，确保数据库已经恢复到所需的状态。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 暂不支持备份文件增量恢复。
+> - 恢复后需要检查数据库中的链接文件是否链接到正确的文件。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/4-gs_ctl.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/4-gs_ctl.md
new file mode 100644
index 0000000000000000000000000000000000000000..97c7a1ed945ed0739b39e22a085910b7f9c51d60
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/4-gs_ctl.md
@@ -0,0 +1,126 @@
+---
+title: gs_ctl
+summary: gs_ctl
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_ctl
+
+## 背景信息
+
+gs_ctl是MogDB提供的数据库服务控制工具，可以用来启停数据库服务和查询数据库状态。主要供MogDB管理模块调用。
+
+gs_ctl工具由操作系统用户omm执行。
+
+- 启动、停止、重启MogDB节点。
+- 在不停止数据库的情况下，重新加载配置文件（postgresql.conf，pg_hba.conf）。
+- 主备切换、主备状态查询、重建和重建状态查询。
+
+## 参数说明
+
+gs_ctl参数可分为如下几类：
+
+- option参数，详细请参见[表1](#option)。
+
+- 公共参数，详细请参见[表2](#gonggong)。
+
+- start和restart模式的参数，详细请参见[表3](#startandrestart)。
+
+- stop和restart模式的参数，详细请参见[表4](#stopandrestart)。
+
+- switchover模式的参数，详细请参见[表5](#switchover)。
+
+- build参数，详细请参见[表6](#build)。
+
+**表 1** option参数<a id="option"> </a>
+
+| 参数       | 参数说明                                                     |
+| :--------- | :----------------------------------------------------------- |
+| init       | 创建数据库。                                                 |
+| start      | 启动数据库。                                                 |
+| restart    | 重启数据库。                                                 |
+| build      | 在主机上重建备实例或级联备实例。                             |
+| stop       | 停止数据库。                                                 |
+| reload     | 重载配置文件（postgresql.conf, pg_hba.conf）。               |
+| status     | 显示数据库运行状态。                                         |
+| promote    | 在指定的数据目录运行的备用服务器被命令退出故障恢复，并开始进行读写操作。 |
+| finishredo | 主机故障时，备机停止回放，强制升主。                         |
+| failover   | 在主机异常时，将备机切换为主机。<br />切换成功后，需要执行gs_om -t refreshconf 命令记录当前主备机信息，确保gs_om -t refreshconf 命令执行成功，否则再次重启会影响数据库状态。 |
+| switchover | 在主备机正常时，出于维护的需要，将备机切换为主机，可保证切换过程中数据不丢失。<br />必须在要切换为主机的备机上，执行switchover命令才会生效。在主机上执行switchover命令，仅做查询使用。<br />切换成功后，需要执行gs_om -t refreshconf 命令记录当前主备机信息，确保gs_om -t refreshconf 命令执行成功，否则再次重启会影响数据库状态。<br />switchover命令下发后，命令如果超时返回，后台进程的执行状态可能处于不可确定状态。 |
+| query      | 查询主备机之间的状态信息。                                   |
+| notify     | 启动后再指定主备机。                                         |
+| kill       | 给指定的进程发送信号量。                                     |
+| querybuild | 查看数据库的重建进度。                                       |
+
+**表 2** 公共参数
+
+| 参数                | 参数说明                                                     | 取值范围                                                     |
+| :------------------ | :----------------------------------------------------------- | :----------------------------------------------------------- |
+| -D, -pgdata=DATADIR | 指定数据目录的位置。                                         | DATADIR的取值必须为有效的数据目录。                          |
+| -s, -silent         | 对于promote、reload、restart、stop命令仅打印部分提示信息，对其他命令不生效。打印信息如：server promoting、server shuting down。不打印信息如：waiting for server to shut down、server stopped等提示信息。 | -                                                            |
+| -t, -timeout=SECS   | 等待数据库启动、关闭或者主备切换完成的最大秒数。如果等待超时，命令会结束退出，并通知不再等待。此后，可以通过gs_om -t status -detail或其他查看数据库状态的命令，来确认数据库是否启动、关闭或主备切换成功。 | 取值范围: 整型（秒）。<br />默认值：等待数据库启动、关闭或者主备切换完成：60秒。 |
+| -V , -version       | 打印gs_ctl的版本信息然后退出。                               | -                                                            |
+| -w                  | 需要等待操作完成。                                           | 默认值：数据库启动、停止或者重新启动时，需要等待操作完成。   |
+| -W                  | 不用等待操作完成。                                           | -                                                            |
+| -M                  | -M后面需要跟SERVERMODE参数，表示在启动时指定数据库的启动模式。 | SERVERMODE的取值范围: <br />- primary：本端以主机模式启动。<br />- standby：本端以备机模式启动。<br />- cascade_standby：本端以级联备机模式启动。<br />- pending：本端处于等待状态，等待提升为主机或者备机。 |
+| -T                  | -T 后面跟term，升主命令时会用此term作为主机term，build时会连接大于等于此term的主机进行build。 | term的取值范围，无符号整型。                                 |
+| -d                  | 打印更多调试信息。                                           | 无参数                                                       |
+| -q                  | 生成完成个后不自动启动，需要调用者启动。                     | 无参数                                                       |
+| -P PASSWORD         | 与-U参数配合使用，指定连接本地数据库的用户密码。<br />说明：<br />当省略-U参数，且认证方法为trust时，-P参数无效。 | -                                                            |
+| -U USERNAME         | 指定连接数据库的用户。此参数只能与notify、query、failover、switchover和querybuild参数配合使用。对于域用户，使用DOMAIN\username格式。 | 取值范围: MogDB中存在的用户。<br />默认值：省略此参数则使用与当前操作系统用户同名的用户。 |
+| -?, -help           | 显示关于gs_ctl命令行参数的帮助信息。                         | -                                                            |
+
+**表 2** 公共参数<a id="gonggong"> </a>
+
+| 参数                | 参数说明                                                     | 取值范围                                                     |
+| :------------------ | :----------------------------------------------------------- | :----------------------------------------------------------- |
+| -D, -pgdata=DATADIR | 指定数据目录的位置。                                         | DATADIR的取值必须为有效的数据目录。                          |
+| -s, -silent         | 对于promote，reload，restart，stop命令仅打印部分提示信息，对其他命令不生效。打印信息如：server promoting，server shuting down。不打印如”waiting for server to shut down, server stopped”等提示信息。 | -                                                            |
+| -t, -timeout=SECS   | 等待数据库启动、关闭或者主备切换完成的最大秒数。             | 取值范围: 整型（秒）。<br />默认值：等待数据库启动、关闭或者主备切换完成：60秒。 |
+| -V , -version       | 打印gs_ctl的版本信息然后退出。                               | -                                                            |
+| -w                  | 需要等待操作完成。                                           | 默认值：数据库启动、停止或者重新启动时，需要等待操作完成。   |
+| -W                  | 不用等待操作完成。                                           | -                                                            |
+| -M                  | -M后面需要跟SERVERMODE参数，表示在启动时指定数据库的启动模式。说明：当前主机处于一主零备，或单机环境时，不支持-M参数。 | SERVERMODE的取值范围: <br />- primary：本端以主机模式启动。<br />- standby：本端以备机模式启动。<br />- cascade_standby：本端以级联备机模式启动。<br />- pending：本端处于等待状态，等待提升为主机或者备机。 |
+| -T                  | -T 后面跟term，升主命令时会用此term作为主机term，build时会连接大于等于此term的主机进行build | term的取值范围，无符号整型。                                 |
+| -d                  | 打印更多调试信息                                             | 无参数                                                       |
+| -P PASSWORD         | 与-U参数配合使用，指定连接本地数据库的用户密码。说明：当省略-U参数，且认证方法为trust时，-P参数无效。 | -                                                            |
+| -U USERNAME         | 指定连接数据库的用户。此参数只能与notify、query、failover、switchover和querybuild参数配合使用。对于域用户，使用DOMAIN\username格式。 | 取值范围: MogDB中存在的用户。<br />默认值：省略此参数则使用与当前操作系统用户同名的用户。 |
+| -?, -help           | 显示关于gs_ctl命令行参数的帮助信息。                         | -                                                            |
+
+**表 3** start或restart共有参数<a id="startandrestart"> </a>
+
+| 参数                | 参数说明                                                     | 取值范围                                                     |
+| :------------------ | :----------------------------------------------------------- | :----------------------------------------------------------- |
+| 参数                | 参数说明                                                     | 取值范围                                                     |
+| :------------------ | :----------------------------------------------------------- | :----------------------------------------------------------- |
+| -c, -core-file      | 允许gaussdb进程产生内核文件。                                | -                                                            |
+| -p PATH-TO-POSTGRES | 声明gaussdb可执行文件的位置。                                | 缺省位于gs_ctl自身所在目录，一般不需要此选项。               |
+| -o OPTIONS          | 声明要直接传递给由MogDB执行的gaussdb的命令行选项。参数通常都用单或者双引号包围以保证它们作为一个整体传递。 | gaussdb支持的参数。                                          |
+| -l, -log=FILENAME   | 把服务器日志输出附加在FILENAME文件上。                       | FILENAME的取值为启动数据库服务的用户有权限的文件。<br />例如，data目录下的某文件。 |
+
+**表 4** stop和restart共有参数<a id="stopandrestart"> </a>
+
+| 参数           | 参数说明       | 取值范围                                                     |
+| :------------- | :------------- | :----------------------------------------------------------- |
+| -m, -mode=MODE | 声明关闭模式。 | mode的取值：<br />- fast：不等待客户端中断连接，所有活跃事务都被回滚并且客户端都被强制断开，然后服务器将被关闭。<br />- immediate：强行关闭，在下次重新启动的时候将导致故障恢复。<br />默认值：fast |
+
+**表 5** switchover参数<a id="switchover"> </a>
+
+| 参数               | 参数说明                               | 取值范围                                                     |
+| :----------------- | :------------------------------------- | :----------------------------------------------------------- |
+| -m SWITCHOVER-MODE | 声明双机主备实例正常时切换的切换模式。 | mode的取值：<br />- fast：不等待客户端中断连接，所有活跃事务都被回滚并且客户端都被强制断开，然后服务器将被切换。<br />- smart：本版本暂不支持该模式。<br />默认值：fast |
+
+**表 6** build参数<a id="build"> </a>
+
+| 参数                      | 参数说明                                                     | 取值范围                                                     |
+| :------------------------ | :----------------------------------------------------------- | :----------------------------------------------------------- |
+| -b MODE                   | 指定重建备机的模式。                                         | mode的取值：<br />- full：通过全量镜像的方式重新同步 主机的数据目录。<br />- incremental：通过解析Xlog日志获 取主备机差异的数据进行增量修复备机。<br />说明：增量重建适用于主备双主等因日志造成的不一致的场景。<br />警告 <br />- 增量重建适用于主备双主等因日志 造成的不一致场景。<br />- 增量重建不适用于一主一备并且没有开启最大高可用的场景，此种场景下需要使用全量重建或者开启最大高可用后再进行增量重建。<br />- 备机数据文件损坏、数据目录丢失 等故障通过增量重建的方式无法修复，此时可通过全量重建的方式重 新修复备机。<br />- auto(不指定)：先增量，增量失败后进行会自动进行一次全量重建。<br />默认值：auto<br />说明：重建级联备机需要加上-M cascade_standy参数。 |
+| -r, -recvtimeout=INTERVAL | 指定重建过程中备机日志接收等待主机响应的超时时间。           | 取值范围: 整型（秒）。<br />默认值：120秒<br />提示：超时时间需根据业务繁忙程度设置，业务繁忙等待主机的响应时间需加长，建议超时时间=checkpoint的执行时间+1min。 |
+| -q                        | 重建结束后，是否自动重启。<br />指定参数场合，不自动重启。<br />未指定场合，自动重启。重启默认最大等待时间是60秒。如果在此时间内数据库未能启动成功，就会报不再等待，命令退出。此后可以通过gs_om -t status --detail或其他查看数据库状态的命令，来确认数据库是否启动成功。 | 无参数                                                       |
+
+**表 7** query参数
+
+| 参数 | 参数说明                | 取值范围 |
+| :--- | :---------------------- | :------- |
+| -L   | 查询lsn并展示最大长度。 | 无参数   |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/5-gs_initdb.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/5-gs_initdb.md
new file mode 100644
index 0000000000000000000000000000000000000000..bff57171982a0c4fcb19fa8b4021ed0cbdc98e2c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/5-gs_initdb.md
@@ -0,0 +1,119 @@
+---
+title: gs_initdb
+summary: gs_initdb
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_initdb
+
+## 简介
+
+**背景信息**
+
+gs_initdb初始化数据库时，会创建数据库目录、生成系统表、创建默认数据库和模板数据库。
+
+**系统表**
+
+初始化数据库时会生成大量的系统表和视图，其中绝大部分都对任何数据库用户开放查看权限。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** pg_user_status、pg_auth_history系统表权限只对初始化数据库用户和sysadmin用户开放。
+
+**生成的数据库**
+
+- template1：是一个模板数据库，当以后再创建一个新的数据库时，template1数据库里的所有内容都会拷贝到新数据库中。通过gs_initdb的参数可以决定template1数据库的设置。
+- template0：是MogDB提供的最初始的备份数据库，当需要时可用template0作为模板生成“干净”的数据库。
+- postgres：是一个提供给用户、工具和第三方应用的缺省数据库。
+
+## 使用指导
+
+**背景信息**
+
+在安装时，推荐使用-D参数调用gs_initdb初始化数据库。如果由于故障恢复等原因，需要重新初始化一个数据库，可以通过执行gs_initdb来完成。
+
+- 尽管gs_initdb会尝试创建相应的数据目录，但可能没有权限执行此操作，因为要创建目录的父目录通常被root所拥有。如果要创建数据目录，首先用root用户创建一个空数据目录，然后用chown把该目录的所有权交给数据库用户。
+- gs_initdb决定template1数据库的设置，而该设置将会成为其他数据库的默认设置。
+- gs_initdb初始化数据库的缺省区域和字符集编码。字符集编码、字符编码排序（LC_COLLATE）和字符集类（LC_CTYPE，如大写、小写数字等）可以在创建数据库时独立设置。
+
+**语法**
+
+```bash
+gs_initdb [OPTION]... [DATADIR]
+```
+
+**操作步骤**
+
+1. 以操作系统用户omm登录数据库主节点。
+
+2. 规划数据库目录。
+
+   - 切换到root用户。
+
+     ```bash
+     su - root
+     ```
+
+   - 根据提示输入用户名和密码。
+
+3. 进入“/opt/gaussdb”目录，并创建“data1”目录。
+
+   ```bash
+   cd /opt/gaussdb
+   mkdir data1
+   ```
+
+   - 将data1目录的所有权分配给数据库用户omm，dbgrp是omm所属的用户组。
+
+     ```bash
+     chown omm:dbgrp data1
+     ```
+
+   - 退出root用户。
+
+     ```bash
+     exit
+     ```
+
+4. 执行gs_initdb命令初始化数据库。
+
+   ```bash
+   gs_initdb -D /opt/gaussdb/data1 -w "Gauss@123" --nodename='data1'
+   ```
+
+## 命令参考
+
+gs_initdb支持的常用参数和不常用参数请分别参见[表 常用参数说明](#changyong)和[表 不常用参数说明](#buchangyong)。
+
+**表 1** 常用参数说明 <a id="changyong">
+
+| 参数                                                         | 参数说明                                                     | 取值范围                                                     |
+| :----------------------------------------------------------- | :----------------------------------------------------------- | :----------------------------------------------------------- |
+| -A, --auth=METHOD                                            | 指定本地用户连接数据库时的认证方法，即“pg_hba.conf”配置文件中host和local所在行的认证方法。<br />除非用户对本地用户都是信任的，否则不要使用默认值trust。<br />须知：<br />若取值为md5，则需手动修改参数文件 postgresql.conf.sample 中的密码存储类型 password_encryption_type 参数的值，修改为0，且放开注释使之生效。gs_initdb工具需同时配合 -W 的使用。 | METHOD的取值：<br />- trust<br />- reject<br />- md5（不安全的算法，为了兼容老版本而存在）<br />- sha256<br />- sm3<br />默认值：trust |
+| --auth-host=METHOD                                           | 指定本地用户通过TCP/IP连接数据库时的认证方法，即：“pg_hba.conf”配置文件中host所在行的认证方法。<br />指定此参数则会覆盖-A参数的值。 | METHOD的取值：<br />- trust<br />- reject<br />- md5（不安全的算法，为了兼容老版本而存在）<br />- sha256<br />- sm3<br />默认值：trust |
+| --auth-local=METHOD                                          | 指定本地用户通过Unix域套接字连接数据库时的认证方法，即“pg_hba.conf”配置文件中local所在行的认证方法。指定此参数则会覆盖-A参数的值。 | METHOD的取值：<br />- trust<br />- reject<br />- md5（不安全的算法，为了兼容老版本而存在）<br />- sha256<br />- sm3<br />默认值：trust |
+| [-D, --pgdata=]DATADIR                                       | 指定数据目录的位置。                                         | DATADIR的取值：用户自定义。                                  |
+| --nodename=NODENAME                                          | 初始化的节点名称。                                           | 节点的命名需要遵守如下规范：<br />- 节点名称必须为小写字母（a-z）、下划线（_）、特殊符号#、数字（0-9）或美元符号（$）。<br />- 节点名称必须以小写字母（a-z）、或下划线（_）开头。<br />- 节点名称不能为空，且最大的长度为64个字符。 |
+| -E, --encoding=ENCODING                                      | 为新数据库设置编码格式。                                     | - 如果使用此参数，需要加上--locale选项指定支持此编码格式的区域。如果不加--locale选项，则采用系统默认的区域，如果系统默认区域的编码格式和用此参数指定的编码格式不匹配则会导致数据库初始化失败。<br />- 如果不指定此参数，则使用系统默认区域的编码格式。系统默认区域和编码格式可以使用locale命令查看，如下：<br />`omm@linux:~> locale|grep LC_CTYPE LC_CTYPE="en_US.UTF-8"`<br />其中`UTF-8`表示系统默认区域的编码格式。 |
+| --locale=LOCALE                                              | 为新数据库设置缺省的区域。可以用locale -a查看可用的区域，如`zh_CN.gbk`等。如果不希望指定特定的区域，则可以用C。<br />须知：<br />如果用户设置了数据库的编码格式，则用户选择区域的编码格式必须与用户设置的编码格式一致，否则数据库初始化会失败。 | 例如用户要将数据库编码格式初始化为GBK，可以采用如下步骤：<br />1. 用`locale -a |grep gbk`命令查看系统支持gbk编码的区域，如下：<br />`omm@linux:~>  locale -a|grep gbk zh_CN.gbk zh_SG.gbk`<br />2. 初始化数据库时加入`--locale=zh_CN.gbk`选项。 |
+| --dbcompatibility=DBCOMPATIBILITY                            | 指定兼容的数据库的类型。                                     | 取值范围: A、B、C、PG。分别表示兼容O、MY、TD和POSTGRES。     |
+| --lc-collate=LOCALE--lc-ctype=LOCALE--lc-messages=LOCALE--lc-monetary=LOCALE--lc-numeric=LOCALE--lc-time=LOCALE | 为新数据库设置指定范畴的区域。                               | 各参数的取值必须是操作系统支持的值。<br />说明：<br />如果用户在数据库安装的时候没有指定--lc-collate参数，则--lc-collate参数的默认值为C。 |
+| --no-locale                                                  | 和--locale=C等价。                                           | -                                                            |
+| --pwfile=FILE                                                | gs_initdb时从文件FILE中读取数据库中系统管理员的密码。该文件的第一行将被当作密码使用。 | FILE可以是“相对路径+文件”的形式，也可以是“绝对路径+文件”的形式。相对路径是相对当前路径的。 |
+| -T, --text-search-config=CFG                                 | 设置缺省的文本搜索方式。此配置项的值不会做正确性校验，配置成功后，有日志记录提醒当前配置项的取值。 | text-search-config的取值：<br />- english全文搜索<br />- simple普通文本搜索<br />默认值：simple |
+| -U, --username=NAME                                          | 选择数据库系统管理员的用户名。                               | 取值范围: 正常的数据库用户。<br />默认值：运行gs_initdb的操作系统用户。 |
+| -W, --pwprompt                                               | gs_initdb时强制交互式输入数据库管理员的密码。                | -                                                            |
+| -w, --pwpasswd=PASSWD                                        | gs_initdb时通过命令行指定的管理员用户的密码，而不是交互式输入。 | 设置的密码要符合复杂度要求：<br />- 最少包含8个字符；<br />- 不能和用户名和当前密码（ALTER）相同，或和当前密码反序；<br />- 至少包含大写字母（A-Z），小写字母（a-z），数字，非字母数字字符 四类字符中的三类字符。 |
+| -C, --enpwdfiledir=DIR                                       | gs_initdb时指定的经AES128加密算法加密过的密码文件所在目录。gs_initdb会将该目录下密码文件进行解密，同时把解密后的密码做密码复杂度校验，校验通过的话会将此密码作为用户的密码。<br />说明：<br />- 加密密码文件需使用gs_guc工具生成：gs_guc encrypt -K Gauss@123 -D Dir。<br />- 如果用户指定多个-w和-C参数，gs_initdb会将用户输入的最后一个-w或-C参数作为用户的需求，即输入密码的明文或经过AES128加密后的密码。 | -                                                            |
+| -X, --xlogdir=XLOGDIR                                        | 声明事务日志存储的目录。所设置的目录，必须满足运行MogDB的用户有读写权限。 | 只支持绝对路径。                                             |
+| -S, --security                                               | 安全方式初始化数据库。                                       | 以-S方式初始化的数据库后，创建的数据库用户权限受到限制，默认不再具有public schema的使用权限。 |
+
+**表 2** 不常用参数说明 <a id="buchangyong"> </a>
+
+| 参数         | 参数说明                                                     | 取值范围                         |
+| :----------- | :----------------------------------------------------------- | :------------------------------- |
+| -d, -debug   | 从初始化后端打印调试输出信息。初始化后端是gs_initdb用于创建系统表的程序。 | -                                |
+| -L DIRECTORY | gs_initdb初始化数据库所需要的输入文件的路径。通常是不必要的。如果需要明确声明的话，程序会提示输入。因该参数意为创建指定配置信息的数据库，建议将share/postgresql下的所有涉及启动相关的子目录及文件全部复制过来，避免其他因素的影响。 | 初始化数据库所需的输入文件路径。 |
+| -n, -noclean | 不指定该参数时，当gs_initdb发现一些错误妨碍它完成创建数据库的工作时，它将在检测到不能结束工作之前将其创建的所有文件删除。这个选项禁止任何清理动作，因而对调试很有用。 | -                                |
+| -s, -show    | 显示内部设置。                                               | -                                |
+| -V, -version | 打印gs_initdb版本信息，然后退出。                            | -                                |
+| -?, -help    | 显示关于gs_initdb命令行参数的帮助信息，然后退出。            | -                                |
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/6-gs_install.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/6-gs_install.md
new file mode 100644
index 0000000000000000000000000000000000000000..604cd9f7eb13de4eff3d5078c85d0e4ba9613bae
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/6-gs_install.md
@@ -0,0 +1,127 @@
+---
+title: gs_install
+summary: gs_install
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_install
+
+## 背景信息
+
+数据库的部署是一个复杂的过程。MogDB提供了gs_install工具来帮助完成MogDB的安装和部署。
+
+MogDB安装部署，要求用户指定配置文件，配置文件中会指定程序安装路径、实例数据目录、主备关系、实例数、各实例的业务IP端口等信息。
+
+## 前提条件
+
+- 已成功执行前置脚本gs_preinstall。
+- 用户需确保各个节点上的locale保持一致。
+- 需要使用前置时设置的MogDB用户进行安装操作。
+
+## 语法
+
+- 安装MogDB
+
+  ```bash
+  gs_install -X XMLFILE [--gsinit-parameter="PARAMETER" [...]] [--dn-guc="PARAMETER" [...]] [--alarm-component=ALARMCOMPONENT] [--time-out=SECS] [-l LOGFILE]
+  ```
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 安装时若不指定字符集，默认字符集为SQL_ASCII，为简化和统一区域loacle默认设置为C，若想指定其他字符集和区域，请在安装时使用参数-gsinit-parameter=“-locale=LOCALE”来指定，LOCALE为新数据库设置缺省的区域。
+
+- 显示帮助信息
+
+  ```bash
+  gs_install -? | --help
+  ```
+
+- 显示版本号信息
+
+  ```bash
+  gs_install -V | --version
+  ```
+
+## 参数说明
+
+- -X
+
+  MogDB配置文件。
+
+  取值范围: xml配置文件。
+
+- -l
+
+  指定安装日志文件及日志文件存放的路径。
+
+  当不明确指定-l，但在XML文件中配置了gaussdbLogPath时，默认值为“gaussdbLogPath的值、用户名和om/gs_install-YYYY-MM-DD_hhmmss.log”的组合。
+
+- -gsinit-parameter=PARAM
+
+  数据实例参数指定。
+
+  取值范围请参见gs_initdb的参数说明，其中对-A、-D、-U、-C、-X参数的设置不生效。
+
+- -dn-guc=PARAM
+
+  配置参数。
+
+  取值范围请参见gs_guc的参数说明。
+
+- -time-out=SECS
+
+  启动超时等待时间。单位：s。
+
+  若-time-out取值过小，有可能会因为需要启动的实例数过多而引起超时。若在超时时间内启动不成功，则会报错启动超时，但是MogDB会在后台继续启动。可以等待一段时间后，查询MogDB状态，检查MogDB是否启动成功。
+
+  取值范围: 正整数，若无特殊需求，不需要配置该参数，系统会自动调整超时时间。
+
+- -alarm-component=alarm_component
+
+  指定告警上报组件的绝对路径。
+
+- -?, -help
+
+  显示帮助信息。
+
+- -V, -version
+
+  显示版本号信息。
+
+## 示例
+
+使用gs_install脚本进行MogDB安装。
+
+```
+gs_install -X /opt/software/MogDB/clusterconfig.xml
+Parsing the configuration file.
+Check preinstall on every node.
+Successfully checked preinstall on every node.
+Creating the backup directory.
+Successfully created the backup directory.
+begin deploy..
+Installing the cluster.
+begin prepare Install Cluster..
+Checking the installation environment on all nodes.
+begin install Cluster..
+Installing applications on all nodes.
+Successfully installed APP.
+begin init Instance..
+encrypt cipher and rand files for database.
+Please enter password for database:
+Please repeat for database:
+begin to create CA cert files
+The sslcert will be generated in /opt/gaussdb/cluster/app/share/sslcert/om
+Cluster installation is completed.
+Configuring.
+Deleting instances from all nodes.
+Successfully deleted instances from all nodes.
+Checking node configuration on all nodes.
+Initializing instances on all nodes.
+Updating instance configuration on all nodes.
+Check consistence of memCheck and coresCheck on DN nodes.
+Successful check consistence of memCheck and coresCheck on all nodes.
+Configuring pg_hba on all nodes.
+Configuration is completed.
+Successfully started cluster.
+Successfully installed application.
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/7-gs_postuninstall.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/7-gs_postuninstall.md
new file mode 100644
index 0000000000000000000000000000000000000000..8e6a0c246f1a73592517d4c369655b88b8c7b8ae
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/7-gs_postuninstall.md
@@ -0,0 +1,117 @@
+---
+title: gs_postuninstall
+summary: gs_postuninstall
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_postuninstall
+
+## 背景信息
+
+MogDB提供了gs_postuninstall工具来帮助清理准备MogDB环境阶段所做配置，使得卸载后的环境得到清理。
+
+## 前提条件
+
+- MogDB卸载执行成功。
+- root用户互信可用。
+- 只能使用root用户执行gs_postuninstall命令。
+
+## 语法
+
+- MogDB清理用户、用户组以及虚拟IP清理
+
+  ```bash
+  gs_postuninstall -U USER -X XMLFILE [-L] [--delete-user] [--delete-group] [-l LOGFILE]
+  ```
+
+- 显示帮助信息
+
+  ```bash
+  gs_postuninstall -? | --help
+  ```
+
+- 显示版本号信息
+
+  ```bash
+  gs_postuninstall -V | --version
+  ```
+
+## 参数说明
+
+- -U
+
+  运行MogDB的操作系统用户名。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- -X
+
+  MogDB配置文件路径。
+
+  取值范围: xml文件的存储路径。
+
+- -L
+
+  只清理本主机的环境。
+
+  如果MogDB内某主机做单机环境清理后，MogDB不能再做全量环境清理。
+
+- -delete-user
+
+  删除-U参数指定的操作系统用户。
+
+  如果在Redhat环境下，且用户名与用户组名相同，选择此项必须指定-delete-group参数。
+
+- -delete-group
+
+  删除操作系统用户所在的用户组（选择此选项必须指定-delete-user参数）。
+
+- -l
+
+指定日志文件名及路径。在内部会自动给日志名添加一个时间戳。
+
+当既不明确指定-l，又不在XML文件中配置gaussdbLogPath时，默认值为：“/var/log/gaussdb/om/gs_local-YYYY-MMDD_hhmmss.log”。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 由于在执行gs_postuninstall后，系统会自动删除MogDB相关目录（包含$GAUSSLOG目录）。因此建议用户通过该参数指定日志文件到非MogDB相关路径。
+
+- -?, -help
+
+  显示帮助信息。
+
+- -V, -version
+
+  显示版本号信息。
+
+## 示例
+
+清理主机的环境
+
+```bash
+gs_postuninstall -U omm  -X /opt/software/MogDB/clusterconfig.xml --delete-user
+Parsing the configuration file.
+Successfully parsed the configuration file.
+Check log file path.
+Successfully checked log file path.
+Checking unpreinstallation.
+Successfully checked unpreinstallation.
+Deleting the instance's directory.
+Successfully deleted the instance's directory.
+Deleting the installation directory.
+Successfully deleted the installation directory.
+Deleting the temporary directory.
+Successfully deleted the temporary directory.
+Deleting remote OS user.
+Successfully deleted remote OS user.
+Deleting software packages and environmental variables of other nodes.
+Successfully deleted software packages and environmental variables of other nodes.
+Deleting logs of other nodes.
+Successfully deleted logs of other nodes.
+Deleting software packages and environmental variables of the local node.
+Successfully deleted software packages and environmental variables of the local nodes.
+Deleting local OS user.
+Successfully deleted local OS user.
+Deleting local node's logs.
+Successfully deleted local node's logs.
+Successfully cleaned environment.
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/8-gs_preinstall.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/8-gs_preinstall.md
new file mode 100644
index 0000000000000000000000000000000000000000..3e36184e531a7972950479a4387ae02486e0acce
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/8-gs_preinstall.md
@@ -0,0 +1,300 @@
+---
+title: gs_preinstall
+summary: gs_preinstall
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_preinstall
+
+## 背景信息
+
+MogDB提供了gs_preinstall工具来帮助完成MogDB的环境配置，以保证MogDB安装的正常进行。
+
+## 注意事项
+
+- 用户需要检查上层目录权限，保证安装用户对安装包和配置文件目录读写执行的权限。
+
+- xml文件中各主机的名称与IP映射配置正确。
+
+- 只能使用root用户执行gs_preinstall命令。
+
+- 执行gs_preinstall会清理/etc/hosts中的MogDB映射信息，可能存在已部署数据库连接丢失风险，可以在安装结束后手动添加其它数据库映射至/etc/hosts文件中。
+
+- 本产品支持同一操作系统大版本下的小版本混合部署，其支持列表如下：
+
+  ```
+  CentOS 6.4/6.5/6.6/6.7/6.8/6.9
+  CentOS 7.0/7.1/7.2/7.3/7.4
+  openEuler
+  ```
+
+## 语法
+
+- 准备MogDB环境
+
+  ```bash
+  gs_preinstall -U USER -G GROUP -X XMLFILE [-L] [--skip-os-set] [--env-var="ENVVAR" [...]] [--sep-env-file=MPPRCFILE] [--skip-hostname-set] [-l LOGFILE] [--non-interactive]
+  ```
+
+- 显示帮助信息
+
+  ```bash
+  gs_preinstall -? | --help
+  ```
+
+- 显示版本号信息
+
+  ```bash
+  gs_preinstall -V | --version
+  ```
+
+## 参数说明
+
+- -U
+
+  运行MogDB的操作系统用户名。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 配置-U参数值时，字符串中不能包含“|”、“;”、“&”、“$”、“<”、“>”、“`”、“\\”、“'”、“\”、“{”、“}”、“(”、“)”、“[”、“]”、“~”、“*”、“?”特殊字符。
+
+- -G
+
+  运行MogDB的操作系统用户的群组名。
+
+  取值范围: 字符串，要符合标识符的命名规范。
+
+- -X
+
+  MogDB配置文件路径。
+
+  取值范围: xml文件的存储路径。
+
+- -L
+
+  指定该参数则仅给当前节点准备好MogDB安装环境。适用于不允许使用root互信的场景和设置安全加固参数PermitRootLogin为no的场景。需要满足如下前提条件：
+
+  1. 安装包和MogDB配置文件已提前上传到所有主机；
+  2. MogDB安装用户已提前创建好并建立好互信关系；
+  3. 用户需要自己保证各台主机上所执行命令的一致性；
+  4. 手动将所有节点的主机名和ip映射关系写入各个主机的/etc/hosts，并在每个映射关系后边加入注释内容：#Gauss OM IP Hosts Mapping。
+
+- -skip-os-set
+
+  是否设置操作系统参数。默认设置系统参数。如果指定该参数则不设置。
+
+- -env-var=“ENVVAR”
+
+  配置普通用户环境变量。可以指定多个。
+
+  取值范围: 字符串。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 本参数不能指定为MogDB默认创建的环境变量。否则，MogDB的环境变量将被覆盖。MogDB默认创建的环境变量见[表1](#mogdbmoren)。
+
+- -sep-env-file=MPPRCFILE
+
+  保存环境变量的文件。如果指定该参数，表示将使用环境变量分离的版本。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 不能指定环境变量文件为MogDB相关目录或者和这些目录同名，不能和MogDB用户的目录相同。
+
+- -skip-hostname-set
+
+  是否将xml配置文件中主机名与IP的映射关系写入“/etc/hosts”文件中。默认写入，如果指定该参数则不写入。
+
+- -l
+
+指定日志文件名及路径。在内部会自动给日志名添加一个时间戳。
+
+默认值：/var/log/gaussdb/用户名/om/gs_preinstall.log
+
+当不明确指定-l，但在XML文件中配置了gaussdbLogPath时，默认值为gaussdbLogPath的值、用户名和om/gs_preinstall-YYYY-MM-DD_hhmmss.log的组合。
+
+- -non-interactive
+
+  指定前置执行模式。
+
+  - 当不指定该参数时，则为安全交互模式，在此模式下用户需要人机交互输入密码。
+  - 当指定该参数时，为非交互模式，不需要进行人机交互。
+
+- -?, -help
+
+  显示帮助信息。
+
+- -V, -version
+
+  显示版本号信息。
+
+  **表 1** MogDB默认创建的环境变量 <a id="mogdbmoren"></a>
+
+  | 环境变量名称            | 说明                      |
+  | :---------------------- | :------------------------ |
+  | MPPDB_ENV_SEPARATE_PATH | MogDB环境变量分离文件路径 |
+  | GPHOME                  | MogDB工具目录             |
+  | PATH                    | MogDB工具脚本目录         |
+  | LD_LIBRARY_PATH         | MogDB引用第三方动态库路径 |
+  | PYTHONPATH              | python软件路径            |
+  | GAUSS_WARNING_TYPE      | 告警类型                  |
+  | GAUSSHOME               | MogDB安装路径             |
+  | GAUSS_VERSION           | MogDB版本号               |
+  | PGHOST                  | MogDB用户的临时目录路径   |
+  | GS_CLUSTER_NAME         | MogDB名称                 |
+  | GAUSSLOG                | MogDB日志路径             |
+  | GAUSS_ENV               | MogDB环境变量标识         |
+
+## 手动设置服务端SYSLOG配置
+
+设置“/etc/syslog-ng/syslog-ng.conf”文件，在文件中添加如下内容：
+
+```bash
+template t_gaussdb {template("$DATE $SOURCEIP $MSGONLY\n");template_escape(no);};
+source s_gaussdb{ udp(); };
+filter f_gaussdb    { level(err,  crit) and match('GaussDB'); };
+destination d_gaussdb { file("/var/log/syslog_MPPDB", template(t_gaussdb)); };
+log { source(s_gaussdb); filter(f_gaussdb); destination(d_gaussdb); };
+```
+
+设置“/etc/sysconfig/syslog”文件，在文件中添加如下内容：
+
+```bash
+SYSLOGD_OPTIONS="-r -m 0"
+KLOGD_OPTIONS="-x"
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 该配置需要在MogDB每台机器上都要修改。
+
+## 示例
+
+使用非交互方式进行MogDB环境准备：
+
+```bash
+./gs_preinstall -U omm -G dbgrp -X /opt/software/MogDB/clusterconfig.xml --non-interactive
+Parsing the configuration file.
+Successfully parsed the configuration file.
+Installing the tools on the local node.
+Successfully installed the tools on the local node.
+Distributing package.
+Successfully distributed package.
+Installing the tools in the cluster.
+Successfully installed the tools in the cluster.
+Checking hostname mapping.
+Successfully checked hostname mapping.
+Checking OS version.
+Successfully checked OS version.
+Creating cluster's path.
+Successfully created cluster's path.
+Set and check OS parameter.
+Setting OS parameters.
+Successfully set OS parameters.
+Warning: Installation environment contains some warning messages.
+Please get more details by "/package_r8/sudo/gs_checkos -i A -h host179174,host179175,host179176".
+Set and check OS parameter completed.
+Preparing CRON service.
+Successfully prepared CRON service.
+Preparing SSH service.
+Successfully prepared SSH service.
+Setting user environmental variables.
+Successfully set user environmental variables.
+Configuring alarms on the cluster nodes.
+Successfully configured alarms on the cluster nodes.
+Setting the dynamic link library.
+Successfully set the dynamic link library.
+Setting finish flag.
+Successfully set finish flag.
+Preinstallation succeeded.
+```
+
+使用交互模式进行MogDB环境准备：
+
+```bash
+./gs_preinstall -U omm -G dbgrp -X /opt/software/MogDB/clusterconfig.xml
+Parsing the configuration file.
+Successfully parsed the configuration file.
+Installing the tools on the local node.
+Successfully installed the tools on the local node.
+Are you sure you want to create trust for root (yes/no)? yes
+Please enter password for root.
+Password:
+Creating SSH trust for the root permission user.
+Please enter password for current user[root].
+Password:
+Checking network information.
+All nodes in the network are Normal.
+Successfully checked network information.
+Creating SSH trust.
+Creating the local key file.
+Successfully created the local key files.
+Appending local ID to authorized_keys.
+Successfully appended local ID to authorized_keys.
+Updating the known_hosts file.
+Successfully updated the known_hosts file.
+Appending authorized_key on the remote node.
+Successfully appended authorized_key on all remote node.
+Checking common authentication file content.
+Successfully checked common authentication content.
+Distributing SSH trust file to all node.
+Successfully distributed SSH trust file to all node.
+Verifying SSH trust on all hosts.
+Successfully verified SSH trust on all hosts.
+Successfully created SSH trust.
+Successfully created SSH trust for the root permission user.
+Distributing package.
+Successfully distributed package.
+Are you sure you want to create the user[omm] and create trust for it (yes/no)? yes
+Please enter password for cluster user.
+Password:
+Please enter password for cluster user again.
+Password:
+Creating [omm] user on all nodes.
+Successfully created [omm] user on all nodes.
+Installing the tools in the cluster.
+Successfully installed the tools in the cluster.
+Checking hostname mapping.
+Successfully checked hostname mapping.
+Creating SSH trust for [omm] user.
+Please enter password for current user[omm].
+Password:
+Checking network information.
+All nodes in the network are Normal.
+Successfully checked network information.
+Creating SSH trust.
+Creating the local key file.
+Successfully created the local key files.
+Appending local ID to authorized_keys.
+Successfully appended local ID to authorized_keys.
+Updating the known_hosts file.
+Successfully updated the known_hosts file.
+Appending authorized_key on the remote node.
+Successfully appended authorized_key on all remote node.
+Checking common authentication file content.
+Successfully checked common authentication content.
+Distributing SSH trust file to all node.
+Successfully distributed SSH trust file to all node.
+Verifying SSH trust on all hosts.
+Successfully verified SSH trust on all hosts.
+Successfully created SSH trust.
+Successfully created SSH trust for [omm] user.
+Checking OS version.
+Successfully checked OS version.
+Creating cluster's path.
+Successfully created cluster's path.
+Set and check OS parameter.
+Setting OS parameters.
+Successfully set OS parameters.
+Warning: Installation environment contains some warning messages.
+Please get more details by "/package_r8/sudo/gs_checkos -i A -h host179174,host179175,host179176".
+Set and check OS parameter completed.
+Preparing CRON service.
+Successfully prepared CRON service.
+Preparing SSH service.
+Successfully prepared SSH service.
+Setting user environmental variables.
+Successfully set user environmental variables.
+Configuring alarms on the cluster nodes.
+Successfully configured alarms on the cluster nodes.
+Setting the dynamic link library.
+Successfully set the dynamic link library.
+Setting finish flag.
+Successfully set finish flag.
+Preinstallation succeeded.
+```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/9-gs_sshexkey.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/9-gs_sshexkey.md
new file mode 100644
index 0000000000000000000000000000000000000000..3bf145d4ee3ba380b5dc9e38538dba5cdc33e60b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/9-gs_sshexkey.md
@@ -0,0 +1,165 @@
+---
+title: gs_sshexkey
+summary: gs_sshexkey
+author: Zhang Cuiping
+date: 2021-06-07
+---
+
+# gs_sshexkey
+
+## 背景信息
+
+MogDB在安装过程中，需要在MogDB中的节点间执行命令，传送文件等操作。因此，安装前需要确保互信是连通的。MogDB提供了gs_sshexkey工具来帮助用户建立互信。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知：** root用户互信可能会存在安全隐患，因此建议用户在使用完成后，立即删除各主机上root用户的互信。
+
+## 前提条件
+
+- 确保ssh服务打开。
+
+- 确保ssh端口不会被防火墙关闭。
+
+- 确保xml文件中各主机名称和IP配置正确。
+
+- 确保所有机器节点间网络畅通。
+
+- 如果为普通用户建立互信，需要提前在各主机创建相同用户并设置密码。
+
+- 如果各主机安装并启动了SELinux服务，需要确保/root和/home目录安全上下文为默认值（root目录：system_u:object_r:home_root_t:s0，home目录：system_u:object_r:admin_home_t:s0）或者关闭掉SELinux服务。
+
+  检查系统SELinux状态的方法：执行命令getenforce，如果返回结果是Enforcing ，说明SELinux安装并启用。
+
+  检查目录安全上下文的命令：
+
+  ```bash
+  ls -ldZ  /root | awk '{print $4}'
+  ```
+
+  ```bash
+  ls -ldZ  /home | awk '{print $4}'
+  ```
+
+  恢复目录安全上下文命令：
+
+  ```bash
+  restorecon -r -vv /home/
+  ```
+
+  ```bash
+  restorecon -r -vv /root/
+  ```
+
+## 语法
+
+- 建立互信
+
+  ```bash
+  gs_sshexkey -f HOSTFILE  [...] [--skip-hostname-set] [-l LOGFILE]
+  ```
+
+- 显示帮助信息
+
+  ```bash
+  gs_sshexkey -? | --help
+  ```
+
+- 显示版本号信息
+
+  ```bash
+  gs_sshexkey -V | --version
+  ```
+
+## 参数说明
+
+- -f
+
+  主机列表，列出所有需要建立互信主机的IP。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 确保hostfile文件中只配置正确的主机IP，不包含其它信息。
+
+- -h
+
+  主机IP列表，多个节点之间用英文逗号隔开。
+
+- -l
+
+  指定日志文件的保存路径。
+
+  取值范围: 任意存在的可访问的绝对路径。
+
+- -skip-hostname-set
+
+  是否将“-f”参数文件中IP与其hostname的映射关系写入“/etc/hosts”文件中。默认写入，如果指定该参数则不写入。普通用户无权限编辑/etc/hosts文件，故有无指定该参数，普通用户均不生成映射关系。
+
+- -no-deduplicate
+
+  是否在配置互信修改/etc/hosts文件的时候，去除/etc/hosts文件中已经配置过的主机信息，默认是去重复。
+
+- -?, -help
+
+  显示帮助信息。
+
+- -V, -version
+
+  显示版本号信息。
+
+## 示例
+
+如下是为root用户建立互信的示例。仅支持交互式输入密码。
+
+- 用户密码相同情况下，交互式模式使用以下命令建立互信。
+
+  ```bash
+  gs_sshexkey -f /opt/software/hostfile
+  Please enter password for current user[root].
+  Password:
+  Checking network information.
+  All nodes in the network are Normal.
+  Successfully checked network information.
+  Creating SSH trust.
+  Creating the local key file.
+  Appending local ID to authorized_keys.
+  Successfully appended local ID to authorized_keys.
+  Updating the known_hosts file.
+  Successfully updated the known_hosts file.
+  Appending authorized_key on the remote node.
+  Successfully appended authorized_key on all remote node.
+  Checking common authentication file content.
+  Successfully checked common authentication content.
+  Distributing SSH trust file to all node.
+  Successfully distributed SSH trust file to all node.
+  Verifying SSH trust on all hosts.
+  Successfully verified SSH trust on all hosts.
+  Successfully created SSH trust.
+  ```
+
+- 用户密码不同情况下，交互式模式使用以下命令建立互信。
+
+  ```bash
+  gs_sshexkey -f /opt/software/hostfile
+  Please enter password for current user[root].
+  Password:
+  Notice :The password of some nodes is incorrect.
+  Please enter password for current user[root] on the node[10.180.10.112].
+  Password:
+  Please enter password for current user[root] on the node[10.180.10.113].
+  Password:
+  Checking network information.
+  All nodes in the network are Normal.
+  Successfully checked network information.
+  Creating SSH trust.
+  Creating the local key file.
+  Appending local ID to authorized_keys.
+  Successfully appended local ID to authorized_keys.
+  Updating the known_hosts file.
+  Successfully updated the known_hosts file.
+  Appending authorized_key on the remote node.
+  Successfully appended authorized_key on all remote node.
+  Checking common authentication file content.
+  Successfully checked common authentication content.
+  Distributing SSH trust file to all node.
+  Successfully distributed SSH trust file to all node.
+  Verifying SSH trust on all hosts.
+  Successfully verified SSH trust on all hosts.
+  Successfully created SSH trust.
+  ```
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/gs_install_plugin.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/gs_install_plugin.md
new file mode 100644
index 0000000000000000000000000000000000000000..18c56c5195ccaf4e977aad8999ae9963976503f0
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/gs_install_plugin.md
@@ -0,0 +1,168 @@
+---
+title: gs_install_plugin
+summary: gs_install_plugin
+author: Guo Huan
+date: 2021-11-29
+---
+
+# gs_install_plugin
+
+## 背景信息
+
+MogDB提供了gs_install_plugin工具用于安装插件，目前支持安装的插件包括pg_repack、pg_trgm、dblink、wal2json、orafce、pg_bulkload、pg_prewarm。本工具适用于一主多备部署的MogDB。
+
+&nbsp;
+
+## 前提条件
+
+已完成MogDB一主多备部署。
+
+&nbsp;
+
+## 语法
+
+```
+gs_install_plugin [-h] [-X XML] [--all] [--dblink] [--pg_trgm] [--wal2json] [--pg_repack] [--orafce] [--pg_bulkload] [--pg_prewarm] [--plugins PLUGINS [PLUGINS ...]]
+```
+
+&nbsp;
+
+## 参数说明
+
+- -h
+
+  显示帮助信息
+
+- -X
+
+  必填参数，后跟clusterconfig.xml配置文件的路径
+
+- --all
+
+  安装全部插件
+
+- --plugins
+
+  可安装多个插件，如：--plugins dblink pg_repack wal2json
+
+- --dblink
+
+  只安装dblink
+
+- --pg_trgm
+
+  只安装pg_trgm
+
+- --wal2json
+
+  只安装wal2json
+
+- --pg_repack
+
+  只安装pg_repack
+
+- --orafce
+
+  只安装orafce
+
+- --pg_bulkload
+
+  只安装pg_bulkload
+
+&nbsp;
+
+## 安装示例
+
+1. 进入数据库安装目录下的script文件夹：
+
+   ```bash
+   cd /opt/software/mogdb/script/
+   ```
+
+2. 创建static文件夹：
+
+    ```bash
+    mkdir -p static
+    ```
+
+    > 注意：文件夹名称请勿更改。
+
+3. 访问[MogDB官网下载页面](https://www.mogdb.io/downloads/mogdb)，根据您的操作系统及CPU架构下载对应版本的插件，并将插件放入static文件夹下。
+
+4. 权限设置
+
+    ```
+    chmod -R 755 /opt/software/mogdb/script
+    chown -R omm:dbgrp /opt/software/mogdb/script
+    ```
+
+5. 配置clusterconfig.xml配置文件，这里以一主一备配置文件作为示例，`backIp1s`为节点ip，`dataNode1`为数据目录，该程序默认获取到的数据目录为第一个节点的数据目录位置。
+
+    ```xml
+    <?xml version="1.0" encoding="UTF-8"?>
+    <ROOT>
+        <!-- MogDB整体信息 -->
+        <CLUSTER>
+            <PARAM name="clusterName" value="dbCluster" />
+            <PARAM name="nodeNames" value="node1,node2" />
+            <PARAM name="backIp1s" value="192.168.0.11,192.168.0.12"/>
+            <PARAM name="gaussdbAppPath" value="/opt/mogdb/app" />
+            <PARAM name="gaussdbLogPath" value="/var/log/mogdb" />
+            <PARAM name="gaussdbToolPath" value="/opt/mogdb/tools" />
+            <PARAM name="corePath" value="/opt/mogdb/corefile"/>
+            <PARAM name="clusterType" value="single-inst"/>
+        </CLUSTER>
+        <!-- 每台服务器上的节点部署信息 -->
+        <DEVICELIST>
+            <!-- node1上的节点部署信息 -->
+            <DEVICE sn="1000001">
+                <PARAM name="name" value="node1"/>
+                <PARAM name="azName" value="AZ1"/>
+                <PARAM name="azPriority" value="1"/>
+                <!-- 如果服务器只有一个网卡可用，将backIP1和sshIP1配置成同一个IP -->
+                <PARAM name="backIp1" value="192.168.0.11"/>
+                <PARAM name="sshIp1" value="192.168.0.11"/>
+
+        <!--dbnode-->
+        <PARAM name="dataNum" value="1"/>
+        <PARAM name="dataPortBase" value="26000"/>
+        <PARAM name="dataNode1" value="/mogdb/data/db1,node2,/mogdb/data/db1"/>
+            </DEVICE>
+
+            <!-- node2上的节点部署信息，其中“name”的值配置为主机名称 -->
+            <DEVICE sn="1000002">
+                <PARAM name="name" value="node2"/>
+                <PARAM name="azName" value="AZ1"/>
+                <PARAM name="azPriority" value="1"/>
+                <!-- 如果服务器只有一个网卡可用，将backIP1和sshIP1配置成同一个IP -->
+                <PARAM name="backIp1" value="192.168.0.12"/>
+                <PARAM name="sshIp1" value="192.168.0.12"/>
+    </DEVICE>
+        </DEVICELIST>
+    </ROOT>
+    ```
+
+6. 切换到omm用户
+
+    ```
+    su - omm
+    ```
+
+7. 安装全部插件
+
+    ```bash
+    /opt/software/mogdb/script/gs_install_plugin -X /opt/software/mogdb/clusterconfig.xml --all
+
+    # 安装成功时回显如下：
+    SUCCESS: dblink.
+    SUCCESS: pg_trgm.
+    SUCCESS: pg_repack.
+    SUCCESS: wal2json.
+    SUCCESS: orafce.
+    SUCCESS: pg_bulkload.
+    SUCCESS: pg_prewarm.
+    ```
+
+## 相关页面
+
+[orafce](orafce-user-guide)、[dblink](dblink-user-guide)、[pg_repack](pg_repack-user-guide)、[pg_trgm](pg_trgm-user-guide)、[wal2json](wal2json-user-guide)、[pg_bulkload](pg_bulkload-user-guide)、[pg_prewarm](pg_prewarm-user-guide)。
diff --git a/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/gs_install_plugin_local.md b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/gs_install_plugin_local.md
new file mode 100644
index 0000000000000000000000000000000000000000..291a1ec400a480c2c73e0f68bf713d815e999478
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/reference-guide/tool-reference/tools-used-in-the-internal-system/gs_install_plugin_local.md
@@ -0,0 +1,158 @@
+---
+title: gs_install_plugin_local
+summary: gs_install_plugin_local
+author: Guo Huan
+date: 2022-01-18
+---
+
+# gs_install_plugin_local
+
+## 背景信息
+
+MogDB提供了gs_install_plugin_local工具用于安装插件，目前支持安装的插件包括pg_repack、pg_trgm、dblink、wal2json、orafce、pg_bulkload、pg_prewarm。本工具适用于单机部署的MogDB。
+
+&nbsp;
+
+## 前提条件
+
+已完成MogDB单机部署。
+
+&nbsp;
+
+## 语法
+
+```
+gs_install_plugin_local [-h] [-X XML] [--all] [--dblink] [--pg_trgm] [--wal2json] [--pg_repack] [--orafce] [--pg_bulkload] [--pg_prewarm] [--plugins PLUGINS [PLUGINS ...]]
+```
+
+&nbsp;
+
+## 参数说明
+
+- -h
+
+  显示帮助信息
+
+- -X
+
+  必填参数，后跟clusterconfig.xml配置文件的路径
+
+- --all
+
+  安装全部插件
+
+- --plugins
+
+  可安装多个插件，如：--plugins dblink pg_repack wal2json
+
+- --dblink
+
+  只安装dblink
+
+- --pg_trgm
+
+  只安装pg_trgm
+
+- --wal2json
+
+  只安装wal2json
+
+- --pg_repack
+
+  只安装pg_repack
+
+- --orafce
+
+  只安装orafce
+
+- --pg_bulkload
+
+  只安装pg_bulkload
+
+&nbsp;
+
+## 安装示例
+
+1. 进入数据库安装目录下的script文件夹：
+
+   ```bash
+   cd /opt/software/mogdb/script/
+   ```
+
+2. 创建static文件夹：
+
+    ```bash
+    mkdir -p static
+    ```
+
+    > 注意：文件夹名称请勿更改。
+
+3. 访问[MogDB官网下载页面](https://www.mogdb.io/downloads/mogdb)，根据您的操作系统及CPU架构下载对应版本的插件，并将插件放入static文件夹下。
+
+4. 权限设置
+
+    ```
+    chmod -R 755 /opt/software/mogdb/script
+    chown -R omm:dbgrp /opt/software/mogdb/script
+    ```
+
+5. 配置clusterconfig.xml配置文件，这里以单节点配置文件作为示例，`backIp1s`为节点ip，`dataNode1`为数据目录，该程序默认获取到的数据目录为第一个节点的数据目录位置。
+
+    ```xml
+    <?xml version="1.0" encoding="UTF-8"?>
+    <ROOT>
+        <!-- MogDB整体信息 -->
+        <CLUSTER>
+            <PARAM name="clusterName" value="dbCluster" />
+            <PARAM name="nodeNames" value="node1" />
+            <PARAM name="backIp1s" value="192.168.0.11"/>
+            <PARAM name="gaussdbAppPath" value="/opt/mogdb/app" />
+            <PARAM name="gaussdbLogPath" value="/var/log/mogdb" />
+            <PARAM name="gaussdbToolPath" value="/opt/mogdb/tools" />
+            <PARAM name="corePath" value="/opt/mogdb/corefile"/>
+            <PARAM name="clusterType" value="single-inst"/>
+        </CLUSTER>
+
+        <!-- 每台服务器上的节点部署信息 -->
+        <DEVICELIST>
+            <!-- node1上的节点部署信息 -->
+            <DEVICE sn="1000001">
+                <PARAM name="name" value="node1"/>
+                <PARAM name="azName" value="AZ1"/>
+                <PARAM name="azPriority" value="1"/>
+                <!-- 如果服务器只有一个网卡可用，将backIP1和sshIP1配置成同一个IP -->
+                <PARAM name="backIp1" value="192.168.0.11"/>
+                <PARAM name="sshIp1" value="192.168.0.11"/>
+
+                <!--dbnode-->
+                <PARAM name="dataNum" value="1"/>
+                <PARAM name="dataPortBase" value="26000"/>
+                <PARAM name="dataNode1" value="/mogdb/data/db1"/>
+            </DEVICE>
+        </DEVICELIST>
+    </ROOT>
+
+6. 切换到omm用户
+
+    ```
+    su - omm
+    ```
+
+7. 安装全部插件
+
+    ```bash
+    /opt/software/mogdb/script/gs_install_plugin_local -X /opt/software/mogdb/clusterconfig.xml --all
+
+    # 安装成功时回显如下：
+    SUCCESS: dblink.
+    SUCCESS: pg_trgm.
+    SUCCESS: pg_repack.
+    SUCCESS: wal2json.
+    SUCCESS: orafce.
+    SUCCESS: pg_bulkload.
+    SUCCESS: pg_prewarm.
+    ```
+
+## 相关页面
+
+[orafce](orafce-user-guide)、[dblink](dblink-user-guide)、[pg_repack](pg_repack-user-guide)、[pg_trgm](pg_trgm-user-guide)、[wal2json](wal2json-user-guide)、[pg_bulkload](pg_bulkload-user-guide)、[pg_prewarm](pg_prewarm-user-guide)。
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/security-guide/security/1-client-access-authentication.md b/product/zh/docs-mogdb/v3.0/security-guide/security/1-client-access-authentication.md
new file mode 100644
index 0000000000000000000000000000000000000000..45e07cc7841d7f3704501c29a1d97157d748631b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/security-guide/security/1-client-access-authentication.md
@@ -0,0 +1,818 @@
+---
+title: 客户端接入认证
+summary: 客户端接入认证
+author: Guo Huan
+date: 2021-03-04
+---
+
+# 客户端接入认证
+
+<br/>
+
+## 配置客户端接入认证
+
+**背景信息**
+
+如果主机需要远程连接数据库，必须在数据库系统的配置文件中增加此主机的信息，并且进行客户端接入认证。配置文件（默认名称为pg_hba.conf）存放在数据库的数据目录里。hba（host-based authentication）表示是基于主机的认证。
+
+- 本产品支持如下三种认证方式，这三种方式都需要配置"pg_hba.conf"文件。
+  - 基于主机的认证: 服务端根据客户端的IP地址、用户名及要访问的数据库来查看配置文件从而判断用户是否通过认证。
+  - 口令认证: 包括远程连接的加密口令认证和本地连接的非加密口令认证。
+  - SSL加密: 使用OpenSSL（开源安全通信库）提供服务端和客户端安全连接的环境。
+- "pg_hba.conf"文件的格式是一行写一条信息，表示一个认证规则，空白和注释（以#开头）被忽略。
+- 每个认证规则是由若干空格和/，空格和制表符分隔的字段组成。如果字段用引号包围，则它可以包含空白。一条记录不能跨行存在。
+
+<br/>
+
+**操作步骤**
+
+1. 以操作系统用户omm登录数据库主节点。
+
+2. 配置客户端认证方式，允许客户端以"jack"用户连接到本机，此处远程连接禁止使用"omm"用户（即数据库初始化用户）。
+
+    例如，下面示例中配置允许IP地址为10.10.0.30的客户端访问本机。
+
+    ```bash
+    gs_guc set -N all -I all -h "host all jack 10.10.0.30/32 sha256"
+    ```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+>
+> - 使用"jack"用户前，需先本地连接数据库，并在数据库中使用如下语句建立"jack"用户:
+>
+>     ```sql
+>     mogdb=# CREATE USER jack PASSWORD 'Test@123';
+>     ```
+>
+> - -N all表示MogDB的所有主机。
+> - -I all表示主机的所有实例。
+> - -h表示指定需要在"pg_hba.conf"增加的语句。
+> - all表示允许客户端连接到任意的数据库。
+> - jack表示连接数据库的用户。
+> - 10.10.0.30/32表示只允许IP地址为10.10.0.30的主机连接。此处的IP地址不能为MogDB内的IP，在使用过程中，请根据用户的网络进行配置修改。32表示子网掩码为1的位数，即255.255.255.255。
+> - sha256表示连接时jack用户的密码使用sha256算法加密。
+
+这条命令在数据库主节点实例对应的"pg_hba.conf"文件中添加了一条规则，用于对连接数据库主节点的客户端进行鉴定。
+
+"pg_hba.conf"文件中的每条记录可以是下面四种格式之一，四种格式的参数说明请参见[配置文件参考](#配置文件参考)。
+
+```text
+local     DATABASE USER METHOD [OPTIONS]
+host      DATABASE USER ADDRESS METHOD [OPTIONS]
+hostssl   DATABASE USER ADDRESS METHOD [OPTIONS]
+hostnossl DATABASE USER ADDRESS METHOD [OPTIONS]
+```
+
+因为认证时系统是为每个连接请求顺序检查"pg_hba.conf"里的记录的，所以这些记录的顺序是非常关键的。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+> 在配置"pg_hba.conf"文件时，请依据通讯需求按照格式内容从上至下配置记录，优先级高的需求需要配置在前面。MogDB和扩容配置的IP优先级最高，用户手动配置的IP请放在这二者之后，如果已经进行的客户配置和扩容节点的IP在同一网段，请在扩容前删除，扩容成功后再进行配置。
+
+因此对于认证规则的配置建议如下:
+
+- 靠前的记录有比较严格的连接参数和比较弱的认证方法。
+- 靠后的记录有比较宽松的连接参数和比较强的认证方法。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+>
+> - 一个用户要想成功连接到特定的数据库，不仅需要通过pg_hba.conf中的规则检查，还必须要有该数据库上的CONNECT权限。如果希望控制某些用户只能连接到指定数据库，赋予/撤销CONNECT权限通常比在pg_hba.conf中设置规则更为简单。
+> - 对应MogDB外部客户端连接，trust为不安全的认证方式，请将认证方式设置为sha256。
+
+<br/>
+
+**异常处理**
+
+用户认证失败有很多原因，通过服务端返回给客户端的提示信息，可以看到用户认证失败的原因。常见的错误提示请参见[表1](#表1.1.1)。
+
+**表 1** 错误提示<a id="表1.1.1"> </a>
+
+| 问题现象             | 解决方法                                |
+| :------------------------- | :------------------------------- |
+| 用户名或密码错误: <br/>`FATAL: invalid username/password,login denied`                                          | 这条信息说明用户名或者密码错误，请检查输入是否有误。                                                                                                             |
+| 连接的数据库不存在: <br/>`FATAL: database "TESTDB" does not exist`                                              | 这条信息说明尝试连接的数据库不存在，请检查连接的数据库名输入是否有误。                                                                                           |
+| 未找到客户端匹配记录: <br/>`FATAL: no pg_hba.conf entry for host "10.10.0.60", user "ANDYM", database "TESTDB"` | 这条信息说明已经连接了服务器，但服务器拒绝了连接请求，因为没有在它的pg_hba.conf配置文件里找到匹配的记录。请联系数据库管理员在pg_hba.conf配置文件加入用户的信息。 |
+
+<br/>
+
+**示例**
+
+```
+TYPE  DATABASE        USER            ADDRESS                 METHOD
+
+#表示只允许在安装时-U参数指定的用户（默认是omm用户）从服务器本机进行连接。
+local   all             omm                                     trust
+IPv4 local connections:
+#表示允许jack用户从10.10.0.50主机上连接到任意数据库，使用sha256算法对密码进行加密。
+host    all           jack             10.10.0.50/32            sha256
+#表示允许任何用户从10.10.0.0/24网段的主机上连接到任意数据库，使用sha256算法对密码进行加密，并且经过SSL加密传输。
+hostssl    all             all             10.10.0.0/24            sha256
+#表示允许任何用户从10.10.0.0/24网段的主机上连接到任意数据库，使用Kerberos认证方式，当前版本暂不支持客户端kerberos认证。
+host    all             all             10.10.0.0/24            gss         include_realm=1        krb_realm=HADOOP.COM
+```
+
+<br/>
+
+## 配置文件参考
+
+**表 2** 参数说明
+
+| 参数名称    | 描述        | 取值范围  |
+| :---------- | :------------------- | :------------------|
+| local       | 表示这条记录只接受通过Unix域套接字进行的连接。没有这种类型的记录，就不允许Unix域套接字的连接。<br/>只有在从服务器本机使用gsql连接且在不指定-U参数的情况下，才是通过Unix域套接字连接。 | -   |
+| host        | 表示这条记录既接受一个普通的TCP/IP套接字连接，也接受一个经过SSL加密的TCP/IP套接字连接。   | - |
+| hostssl     | 表示这条记录只接受一个经过SSL加密的TCP/IP套接字连接。 | 用SSL进行安全的连接，需要配置申请数字证书并配置相关参数，详细信息请参见[用SSL进行安全的TCP/IP连接](#用SSL进行安全的TCP/IP连接)。|
+| hostnossl   | 表示这条记录只接受一个普通的TCP/IP套接字连接。    | -     |
+| DATABASEGUC | 声明记录所匹配且允许访问的数据库。         | - all: 表示该记录匹配所有数据库。<br/>- sameuser: 表示如果请求访问的数据库和请求的用户同名，则匹配。<br/>- samerole: 表示请求的用户必须是与数据库同名角色中的成员。<br/>- samegroup: 与samerole作用完全一致，表示请求的用户必须是与数据库同名角色中的成员。<br/>- 一个包含数据库名的文件或者文件中的数据库列表: 文件可以通过在文件名前面加前缀@来声明。文件中的数据库列表以逗号或者换行符分隔。<br/>- 特定的数据库名称或者用逗号分隔的数据库列表。<br/>说明:<br/>值replication表示如果请求一个复制链接，则匹配，但复制链接不表示任何特定的数据库。如需使用名为replication的数据库，需在database列使用记录"replication"作为数据库名。 |
+| USER        | 声明记录所匹配且允许访问的数据库用户。                                                                                                                                                | - all: 表明该记录匹配所有用户。<br/>- +用户角色: 表示匹配任何直接或者间接属于这个角色的成员。<br/>说明:<br/>+表示前缀符号。<br/>- 一个包含用户名的文件或者文件中的用户列表: 文件可以通过在文件名前面加前缀@来声明。文件中的用户列表以逗号或者换行符分隔。<br/>- 特定的数据库用户名或者用逗号分隔的用户列表。   |
+| ADDRESS     | 指定与记录匹配且允许访问的IP地址范围。                                                                                                                                                | 支持IPv4和IPv6，可以使用如下两种形式来表示: <br/>- IP地址/掩码长度。例如，10.10.0.0/24<br/>- IP地址子网掩码。例如，10.10.0.0 255.255.255.0<br/>说明:<br/>以IPv4格式给出的IP地址会匹配那些拥有对应地址的IPv6连接，比如127.0.0.1将匹配IPv6地址 ::ffff:127.0.0.1  |
+| METHOD      | 声明连接时使用的认证方法。                                                                                                                                                            | 本产品支持如下几种认证方式，详细解释请参见[表3](#表1.2.2): <br/>- trust<br/>- reject<br/>- md5（不推荐使用，默认不支持，可通过password_encryption_type参数配置）<br/>说明：<br />MD5加密算法安全性低，存在安全风险，建议使用更安全的加密算法。<br />- sha256<br/>- sm3<br />- cert<br/>- gss（仅用于MogDB内部节点间认证）<br />- peer (仅用于local模式)                |
+
+<br/>
+
+**表 3** 认证方式<a id="表1.2.2"> </a>
+
+| 认证方式 | 说明  |
+| :------------ | :----------------------------------------------- |
+| trust    | 采用这种认证模式时，本产品只完全信任从服务器本机使用gsql且不指定-U参数的连接，此时不需要口令。<br/>trust认证对于单用户工作站的本地连接是非常合适和方便的，通常不适用于多用户环境。如果想使用这种认证方法，可利用文件系统权限限制对服务器的Unix域套接字文件的访问。要使用这种限制有两个方法: <br/>- 设置参数unix_socket_permissions和unix_socket_group。<br/>- 设置参数unix_socket_directory，将Unix域套接字文件放在一个经过恰当限制的目录里。<br/>须知: 设置文件系统权限只能Unix域套接字连接，它不会限制本地TCP/IP连接。为保证本地TCP/IP安全，MogDB不允许远程连接使用trust认证方法。 |
+| reject   | 无条件地拒绝连接。常用于过滤某些主机。                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| md5      | 要求客户端提供一个md5加密的口令进行认证。<br/>须知: <br/>- MD5加密算法安全性低，存在安全风险，建议使用更安全的加密算法。<br />- MogDB保留md5认证和密码存储，是为了便于第三方工具的使用（比如TPCC评测工具）。                                                                                                                                                                                                                                                                                                                                    |
+| sha256   | 要求客户端提供一个sha256算法加密的口令进行认证，该口令在传送过程中结合salt（服务器发送给客户端的随机数）的单向sha256加密，增强了安全性。                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| sm3 | 要求客户端提供一个sm3算法加密口令进行认证，该口令在传送过程中结合salt（服务器发送给客户端的随机数）的单项sm3的加密，增加了安全性。 |
+| cert     | 客户端证书认证模式，此模式需进行SSL连接配置且需要客户端提供有效的SSL证书，不需要提供用户密码。<br/>须知: <br/>该认证方式只支持hostssl类型的规则。                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| gss      | 使用基于gssapi的kerberos认证。<br/>须知: <br/>- 该认证方式依赖kerberos server等组件，仅支持MogDB内部通信认证。当前版本暂不支持外部客户端通过kerberos认证连接。<br/>- 开启MogDB内部kerberos认证会使增加内部节点建连时间，即影响首次涉及内部建连的SQL操作性能，内部连接建立好后， 后续操作不受影响。                                                                                                                                                                                                                                                                                   |
+| peer | 获取客户端所在操作系统用户名，并检查与数据库初始用户名是否一致。此方式只支持local模式本地连接，并支持通过配置pg_ident.conf建立操作系统用户与数据库用户映射关系。<br />假设操作系统用户名为omm，数据库初始用户为dbAdmin，在pg_hba.conf中配置local模式为peer认证：<br />`local   all    all        peer    map=mymap`<br />其中map=mymap指定使用的用户名映射，并在pg_ident.conf中添加映射名称为mymap的用户名映射如下：<br />`# MAPNAME       SYSTEM-USERNAME         PG-USERNAME mymap                omm                                  dbAdmin`<br />说明：<br />通过gs_guc reload方式修改pg_hba.conf配置可以立即生效无需重启数据库。直接编辑修改pg_ident.conf配置后下次连接时自动生效无需重启数据库。 |
+
+<br/>
+
+## 用SSL进行安全的TCP/IP连接
+
+**背景信息**
+
+MogDB支持SSL标准协议（TLS 1.2），SSL协议是安全性更高的协议标准，它们加入了数字签名和数字证书来实现客户端和服务器的双向身份验证，保证了通信双方更加安全的数据传输。
+
+<br/>
+
+**前提条件**
+
+从CA认证中心申请到正式的服务器、客户端的证书和密钥。（假设服务器的私钥为server.key，证书为server.crt，客户端的私钥为client.key，证书为client.crt，CA根证书名称为cacert.pem。）
+
+<br/>
+
+**注意事项**
+
+- 当用户远程连接到数据库主节点时，需要使用sha256的认证方式。
+- 当内部服务器之间连接时，需要使用trust的认证方式，支持IP白名单认证。
+
+<br/>
+
+**操作步骤**
+
+MogDB在MogDB部署完成后，默认已开启SSL认证模式。服务器端证书，私钥以及根证书已经默认配置完成。用户需要配置客户端的相关参数。
+
+配置SSL认证相关的数字证书参数，具体要求请参见[表4](#表1.3.1)。
+
+- 配置客户端参数。
+
+    已从CA认证中心申请到客户端默认证书，私钥，根证书以及私钥密码加密文件。假设证书、私钥和根证书都放在"/home/omm"目录。
+
+    双向认证需配置如下参数:
+
+    ```bash
+    export PGSSLCERT="/home/omm/client.crt"
+    export PGSSLKEY="/home/omm/client.key"
+    export PGSSLMODE="verify-ca"
+    export PGSSLROOTCERT="/home/omm/cacert.pem"
+    ```
+
+    单向认证需要配置如下参数:
+
+    ```bash
+    export PGSSLMODE="verify-ca"
+    export PGSSLROOTCERT="/home/omm/cacert.pem"
+    ```
+
+- 修改客户端密钥的权限。
+
+    客户端根证书，密钥，证书以及密钥密码加密文件的权限，需保证权限为600。如果权限不满足要求，则客户端无法以SSL连接到MogDB。
+
+    ```bash
+    chmod 600 client.key
+    chmod 600 client.crt
+    chmod 600 client.key.cipher
+    chmod 600 client.key.rand
+    chmod 600 cacert.pem
+    ```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+> 从安全性考虑，建议使用双向认证方式。
+> 配置客户端环境变量，必须包含文件的绝对路径。
+
+**表 4** 认证方式<a id="表1.3.1"> </a>
+
+| 认证方式         | 含义         | 配置客户端环境变量            | 维护建议           |
+| :---------------------- | :----------------------------| :------------------------------- |:------------------------------- |
+| 双向认证（推荐） | 客户端验证服务器证书的有效性，同时服务器端也要验证客户端证书的有效性，只有认证成功，连接才能建立。                                                 | 设置如下环境变量: <br/>- PGSSLCERT<br/>- PGSSLKEY<br/>- PGSSLROOTCERT<br/>- PGSSLMODE | 该方式应用于安全性要求较高的场景。使用此方式时，建议设置客户端的PGSSLMODE变量为verify-ca。确保了网络数据的安全性。       |
+| 单向认证         | 客户端只验证服务器证书的有效性，而服务器端不验证客户端证书的有效性。服务器加载证书信息并发送给客户端，客户端使用根证书来验证服务器端证书的有效性。 | 设置如下环境变量: <br/>- PGSSLROOTCERT<br/>- PGSSLMODE                              | 为防止基于TCP链接的欺骗，建议使用SSL证书认证功能。除配置客户端根证书外，建议客户端使用PGSSLMODE变量为verify-ca方式连接。 |
+
+<br/>
+
+**相关参考**
+
+在服务器端的postgresql.conf文件中配置相关参数，详细信息请参见[表5](#表1.3.2)。
+
+**表 5** 服务器参数<a id="表1.3.2"> </a>
+
+| 参数          | 描述            | 取值范围   |
+| :------------ | :-------------------- | :-------------------|
+| ssl           | 表示是否启动SSL功能。                                                                                              | - on: 开启SSL功能。<br/>- off: 关闭SSL功能。<br/> **默认值** : on                                                                                      |
+| require_ssl   | 设置服务器端是否强制要求SSL连接。该参数只有当参数ssl为on时才有效。                                                 | - on: 服务器端强制要求SSL连接。<br/>- off: 服务器端对是否通过SSL连接不作强制要求。<br/> **默认值** :  off                                              |
+| ssl_cert_file | 指定服务器证书文件，包含服务器端的公钥。服务器证书用以表明服务器身份的合法性，公钥将发送给对端用来对数据进行加密。 | 请以实际的证书名为准。其相对路径是相对于数据目录的。<br/> **默认值** : server.crt                                                  |
+| ssl_key_file  | 指定服务器私钥文件，用以对公钥加密的数据进行解密。                                                                 | 请以实际的服务器私钥名称为准。其相对路径是相对于数据目录的。<br/> **默认值** : server.key                                            |
+| ssl_ca_file   | CA服务器的根证书。此参数可选择配置，需要验证客户端证书的合法性时才需要配置。                                       | 请以实际的CA服务器根证书名称为准。<br/> **默认值** : cacert.pem                                                                                       |
+| ssl_crl_file  | 证书吊销列表，如果客户端证书在该列表中，则当前客户端证书被视为无效证书。                                           | 请以实际的证书吊销列表名称为准。<br/> **默认值** : 空，表示没有吊销列表。                                                                             |
+| ssl_ciphers   | SSL通讯使用的加密算法。                                                                                            | 本产品支持的加密算法的详细信息请参见[表4](#表1.3.4)。<br/> **默认值:** ALL，表示允许对端使用产品支持的所有加密算法，但不包含ADH、LOW、EXP、MD5算法。 |
+| ssl_cert_notify_time | SSL服务器证书到期前提醒的天数。 | 请按照需求配置证书过期前提醒天数。<br/> **默认值:** 90 |
+
+在客户端配置SSL认证相关的环境变量，详细信息请参见[表6](#表1.3.3)。
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+> 客户端环境变量的路径以_/home/omm_为例，在实际操作中请使用实际路径进行替换。
+
+**表 6** 客户端参数<a id="表1.3.3"> </a>
+
+| 环境变量      | 描述                         | 取值范围                      |
+| :------------ | :--------------------------- | :-------------------------- |
+| PGSSLCERT     | 指定客户端证书文件，包含客户端的公钥。客户端证书用以表明客户端身份的合法性，公钥将发送给对端用来对数据进行加密。 | 必须包含文件的绝对路径，如：<br />`export PGSSLCERT='/home/omm/client.crt'`<br />**默认值**：空 |
+| PGSSLKEY      | 指定客户端私钥文件，用以对公钥加密的数据进行解密。           | 必须包含文件的绝对路径，如：<br />`export PGSSLKEY='/home/omm/client.key'`<br />**默认值**：空 |
+| PGSSLMODE     | 设置是否和服务器进行SSL连接协商，以及指定SSL连接的优先级。   | **取值及含义：**<br />- disable：只尝试非SSL连接。<br />- allow：首先尝试非SSL连接，如果连接失败，再尝试SSL连接。<br />- prefer：首先尝试SSL连接，如果连接失败，将尝试非SSL连接。<br />- require：只尝试SSL连接。如果存在CA文件，则按设置成verify-ca的方式验证。<br />- verify-ca：只尝试SSL连接，并且验证服务器是否具有由可信任的证书机构签发的证书。<br />- verify-full：只尝试SSL连接，并且验证服务器是否具有由可信任的证书机构签发的证书，以及验证服务器主机名是否与证书中的一致。<br />**默认值：**prefer |
+| PGSSLROOTCERT | 指定为客户端颁发证书的根证书文件，根证书用于验证服务器证书的有效性。 | 必须包含文件的绝对路径，如：<br />`export PGSSLROOTCERT='/home/omm/certca.pem'`<br />**默认值：**空 |
+| PGSSLCRL      | 指定证书吊销列表文件，用于验证服务器证书是否在废弃证书列表中，如果在，则服务器证书将会被视为无效证书。 | 必须包含文件的绝对路径，如：<br />`export PGSSLCRL='/home/omm/sslcrl-file.crl'`<br />**默认值：**空 |
+
+服务器端参数ssl、require_ssl与客户端参数sslmode配置组合结果如下:
+
+- 服务器 ssl = on
+
+    | sslmode(客户端) | require_ssl(服务器) | 结果               |
+    | :------- | :------- | :------- |
+    | disable      | on    | 由于服务器端要求使用SSL,但客户端连接禁用了SSL,无法建立连接。 |
+    | allow        | on    | 连接经过加密。                                 |
+    | prefer       | on    | 连接经过加密。                                 |
+    | require      | on    | 连接经过加密。                                 |
+    | verify-ca    | on    | 连接经过加密，且验证了服务器证书。                       |
+    | verify-full  | on    | 连接经过加密，且验证了服务器证书和主机名。                   |
+    | verify-full  | off   | 连接经过加密，且验证了服务器证书和主机名。                   |
+
+- 服务器 ssl = off
+
+    | sslmode(客户端) | require_ssl(服务器) | 结果               |
+    | :------- | :------- | :------- |
+    | disable      | on               | 连接未加密。                             |
+    | allow        | on               | 连接未加密。                             |
+    | prefer       | on               | 连接未加密。                             |
+    | require      | on               | 由于客户端要求使用SSL，但服务器端禁用了SSL，因此无法建立连接。 |
+    | verify-ca    | on               | 由于客户端要求使用SSL，但服务器端禁用了SSL，因此无法建立连接。 |
+    | verify-full  | on               | 由于客户端要求使用SSL，但服务器端禁用了SSL，因此无法建立连接。 |
+    | verify-full  | off              | 由于客户端要求使用SSL，但服务器端禁用了SSL，因此无法建立连接。 |
+
+SSL传输支持一系列不同强度的加密和认证算法。用户可以通过修改postgresql.conf中的ssl_ciphers参数指定数据库服务器使用的加密算法。目前本产品SSL支持的加密算法如[表7](#表1.3.4)所示。
+
+**表 7** 加密算法<a id="表1.3.4"> </a>
+
+| 加密强度 | 安全程度 | 加密算法描述              |
+| :------- | :------- | :------------------------ |
+| stronger | high     | DHE-RSA-AES256-GCM-SHA384 |
+| stronger | high     | DHE-RSA-AES128-GCM-SHA256 |
+| stronger | high     | DHE-DSS-AES256-GCM-SHA384 |
+| stronger | high     | DHE-DSS-AES128-GCM-SHA256 |
+| stronger | medium   | DHE-RSA-AES256-SHA256     |
+| stronger | medium   | DHE-RSA-AES128-SHA256     |
+| stronger | medium   | DHE-DSS-AES256-SHA256     |
+| stronger | medium   | DHE-DSS-AES128-SHA256     |
+| stronger | high     | DHE-RSA-AES256-CCM        |
+| stronger | high     | DHE-RSA-AES128-CCM        |
+| stronger | medium   | DHE-RSA-AES256-SHA        |
+| stronger | medium   | DHE-RSA-AES128-SHA        |
+| stronger | medium   | DHE-DSS-AES256-SHA        |
+| stronger | medium   | DHE-DSS-AES128-SHA        |
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+>
+> - SSL目前只支持加密强度在strong以上的加密算法。
+>
+> - 配置参数ssl_ciphers的默认值为ALL，表示支持上表中的所有加密算法。如果对加密算法没有特殊要求，建议用户使用该默认值。
+>
+> - 如指定以上多种加密，加密算法之间需要使用分号分割。
+>
+>   如在postgresql.conf设置ssl_ciphers='DHE-RSA-AES256-GCM-SHA384;DHE-RSA-AES256-SHA256;DHE-RSA-AES256-CCM'
+>
+> - 如果要使用上表中和DSS相关的加密算法（如DHE-DSS-AES256-GCM-SHA384、DHE-DSS-AES256-SHA256、DHE-DSS-AES256-SHA等）必须加载使用DSA算法签名的证书文件。如何使用openssl产生DSA算法签名的证书文件，请参见openssl官方文档。
+>
+> - SSL连接认证不仅增加了登录（创建SSL环境）及退出过程（清理SSL环境）的时间消耗，同时需要消耗额外的时间用于加解密所需传输的内容，因此对性能有一定影响。特别的，对于频繁的登录登出，短时查询等场景有较大的影响。
+>
+> - 在证书有效期小于7天的时候，连接登录会在日志中产生告警提醒。
+
+<br/>
+
+## 用SSH隧道进行安全的TCP/IP连接
+
+**背景信息**
+
+为了保证服务器和客户端之间的安全通讯，可以在服务器和客户端之间构建安全的SSH隧道。SSH是目前较可靠，专为远程登录会话和其他网络服务提供安全性的协议。
+
+从SSH客户端来看，SSH提供了两种级别的安全验证:
+
+- 基于口令的安全验证: 使用帐号和口令登录到远程主机。所有传输的数据都会被加密，但是不能保证正在连接的服务器就是需要连接的服务器。可能会有其他服务器冒充真正的服务器，也就是受到"中间人"方式的攻击。
+- 基于密钥的安全验证: 用户必须为自己创建一对密钥，并把公用密钥放在需要访问的服务器上。这种级别的认证不仅加密所有传送的数据，而且避免"中间人"攻击方式。但是整个登录的过程可能需要10秒。
+
+<br/>
+
+**前提条件**
+
+SSH服务和数据库运行在同一台服务器上。
+
+<br/>
+
+**操作步骤**
+
+以OpenSSH为例介绍配置SSH隧道，对于如何配置基于密钥的安全验证不作赘述，OpenSSH提供了多种配置适应网络的各种限制，更多详细信息请参考OpenSSH的相关文档。
+
+从本地主机建立到服务器的SSH隧道。
+
+```bash
+ssh -L 63333:localhost:8000 username@hostIP
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+>
+> - -L参数的第一串数字（63333）是通道本端的端口号，可以自由选择。
+> - 第二串数字（8000）是通道远端的端口号，也就是服务器使用的端口号。
+> - localhost是本机IP地址，username是要连接的服务器上的用户名，hostIP是要连接的主机IP地址。
+
+<br/>
+
+## 查看数据库连接数
+
+**背景信息**
+
+当用户连接数达到上限后，无法建立新的连接。因此，当数据库管理员发现某用户无法连接到数据库时，需要查看是否连接数达到了上限。控制数据库连接的主要以下几种选项。
+
+- 全局的最大连接数: 由运行参数max_connections指定，默认值为5000。
+- 某用户的连接数: 在创建用户时由CREATE ROLE命令的CONNECTION LIMIT connlimit子句直接设定，也可以在设定以后用ALTER ROLE的CONNECTION LIMIT connlimit子句修改。
+- 某数据库的连接数: 在创建数据库时，由CREATE DATABASE的CONNECTION LIMIT connlimit参数指定。
+
+<br/>
+
+**操作步骤**
+
+1. 以操作系统用户omm登录数据库主节点。
+
+2. 使用如下命令连接数据库。
+
+    ```bash
+    gsql -d mogdb -p 8000
+    ```
+
+    mogdb为需要连接的数据库名称，8000为数据库主节点的端口号。
+
+3. 查看全局会话连接数限制。
+
+    ```sql
+    mogdb=# SHOW max_connections;
+     max_connections
+    -----------------
+        800
+    (1 row)
+    ```
+
+    其中800是最大会话连接数。
+
+4. 查看已使用的会话连接数。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:**
+    > 除了创建的时候用双引号引起的数据库和用户名称外，以下命令中用到的数据库名称和用户名称，其中包含的英文字母必须使用小写。
+
+    + 查看指定用户的会话连接数上限
+
+        执行如下命令查看连接到指定用户omm的会话连接数上限。其中-1表示没有对用户omm设置连接数的限制。
+
+        ```sql
+        mogdb=# SELECT ROLNAME,ROLCONNLIMIT FROM PG_ROLES WHERE ROLNAME='omm';
+         rolname | rolconnlimit
+        ---------+--------------
+         omm     |           -1
+        (1 row)
+        ```
+
+    + 查看指定用户已使用的会话连接数
+
+        执行如下命令查看指定用户omm已使用的会话连接数。其中，1表示omm已使用的会话连接数。
+
+        ```sql
+        mogdb=# CREATE OR REPLACE VIEW DV_SESSIONS AS
+        SELECT
+        sa.sessionid AS SID,
+        0::integer AS SERIAL#,
+        sa.usesysid AS USER#,
+        ad.rolname AS USERNAME
+        FROM pg_stat_get_activity(NULL) AS sa
+        LEFT JOIN pg_authid ad ON(sa.usesysid = ad.oid)
+        WHERE sa.application_name <> 'JobScheduler';
+        mogdb=# SELECT COUNT() FROM DV_SESSIONS WHERE USERNAME='omm';
+        count
+        -------
+            1
+        (1 row)
+        ```
+
+    + 查看指定数据库的会话连接数上限
+
+        执行如下命令查看连接到指定数据库mogdb的会话连接数上限。其中-1表示没有对数据库mogdb设置连接数的限制。
+
+        ```sql
+        mogdb=# SELECT DATNAME,DATCONNLIMIT FROM PG_DATABASE WHERE DATNAME='mogdb';
+         datname | datconnlimit
+        ---------+--------------
+         mogdb   |           -1
+        (1 row)
+        ```
+
+    + 查看指定数据库已使用的会话连接数
+
+        执行如下命令查看指定数据库mogdb上已使用的会话连接数。其中，1表示数据库mogdb上已使用的会话连接数。
+
+        ```sql
+        mogdb=# SELECT COUNT() FROM PG_STAT_ACTIVITY WHERE DATNAME='mogdb';
+         count
+        -------
+            1
+        (1 row)
+        ```
+
+    + 查看所有用户已使用会话连接数
+
+        执行如下命令查看所有用户已使用的会话连接数。
+
+        ```sql
+        mogdb=# CREATE OR REPLACE VIEW DV_SESSIONS AS
+        SELECT
+        sa.sessionid AS SID,
+        0::integer AS SERIAL#,
+        sa.usesysid AS USER#,
+        ad.rolname AS USERNAME
+        FROM pg_stat_get_activity(NULL) AS sa
+        LEFT JOIN pg_authid ad ON(sa.usesysid = ad.oid)
+        WHERE sa.application_name <> 'JobScheduler';
+        mogdb=# SELECT COUNT(*) FROM DV_SESSIONS;
+         count
+        -------
+            23
+        (1 row)
+        ```
+
+## SSL证书管理
+
+MogDB默认配置了通过openssl生成的安全证书、私钥。并且提供证书替换的接口，方便用户进行证书的替换。
+
+<br/>
+
+### 证书生成
+
+**操作场景**
+
+在测试环境下，用户可以用通过以下方式进行数字证书测试。在客户的运行环境中，请使用从CA认证中心申请的数字证书。
+
+<br/>
+
+**前提条件**
+
+Linux环境安装了openssl组件。
+
+<br/>
+
+**自认证证书生成过程**
+
+1. 搭建CA环境。
+
+    ```bash
+    # 假设用户为omm已存在,搭建CA的路径为test
+    # 以root用户身份登录Linux环境,切换到用户omm
+    mkdir test
+    cd /etc/pki/tls
+    # copy 配置文件openssl.cnf到test下
+    cp openssl.cnf ~/test
+    cd ~/test
+    # 到test文件夹下，开始搭建CA环境
+    # 创建文件夹demoCA./demoCA/newcerts./demoCA/private
+    mkdir ./demoCA ./demoCA/newcerts ./demoCA/private
+    chmod 700 ./demoCA/private
+    # 创建serial文件,写入01
+    echo '01'>./demoCA/serial
+    # 创建文件index.txt
+    touch ./demoCA/index.txt
+    # 修改openssl.cnf配置文件中的参数
+    dir  = ./demoCA
+    default_md      = sha256
+    # 至此CA环境搭建完成
+    ```
+
+2. 生成根私钥。
+
+    ```bash
+    # 生成CA私钥
+    openssl genrsa -aes256 -out demoCA/private/cakey.pem 2048
+    Generating RSA private key, 2048 bit long modulus
+    .................+++
+    ..................+++
+    e is 65537 (0x10001)
+    # 设置根私钥的保护密码，假设为Test@123
+    Enter pass phrase for demoCA/private/cakey.pem:
+    # 再次输入私钥密码 Test@123
+    Verifying - Enter pass phrase for demoCA/private/cakey.pem:
+    ```
+
+3. 生成根证书请求文件。
+
+    ```bash
+    # 生成CA根证书申请文件careq.pem
+    openssl req -config openssl.cnf -new -key demoCA/private/cakey.pem -out demoCA/careq.pem
+    Enter pass phrase for demoCA/private/cakey.pem:
+    # 输入根私钥密码 Test@123
+    You are about to be asked to enter information that will be incorporated
+    into your certificate request.
+    What you are about to enter is what is called a Distinguished Name or a DN.
+    There are quite a few fields but you can leave some blank
+    For some fields there will be a default value,
+    If you enter '.', the field will be left blank.
+    -----
+
+    # 以下名称请牢记，生成服务器证书和客户端证书时填写的信息需要与此处的一致
+    Country Name (2 letter code) [AU]:CN
+    State or Province Name (full name) [Some-State]:shanxi
+    Locality Name (eg, city) []:xian
+    Organization Name (eg, company) [Internet Widgits Pty Ltd]:Abc
+    Organizational Unit Name (eg, section) []:hello
+    # Common Name可以随意命名
+    Common Name (eg, YOUR name) []:world
+    # Email可以选择性填写
+    Email Address []:
+
+    Please enter the following 'extra' attributes
+    to be sent with your certificate request
+    A challenge password []:
+    An optional company name []:
+    ```
+
+4. 生成自签发根证书。
+
+    ```bash
+    # 生成根证书时，需要修改openssl.cnf文件，设置basicConstraints=CA:TRUE
+    vi openssl.cnf
+    # 生成CA自签发根证书
+    openssl ca -config openssl.cnf -out demoCA/cacert.pem -keyfile demoCA/private/cakey.pem -selfsign -infiles demoCA/careq.pem
+    Using configuration from openssl.cnf
+    Enter pass phrase for demoCA/private/cakey.pem:
+    # 输入根私钥密码 Test@123
+    Check that the request matches the signature
+    Signature ok
+    Certificate Details:
+            Serial Number: 1 (0x1)
+            Validity
+                Not Before: Feb 28 02:17:11 2017 GMT
+                Not After : Feb 28 02:17:11 2018 GMT
+            Subject:
+                countryName               = CN
+                stateOrProvinceName       = shanxi
+                organizationName          = Abc
+                organizationalUnitName    = hello
+                commonName                = world
+            X509v3 extensions:
+                X509v3 Basic Constraints:
+                    CA:FALSE
+                Netscape Comment:
+                    OpenSSL Generated Certificate
+                X509v3 Subject Key Identifier:
+                    F9:91:50:B2:42:8C:A8:D3:41:B0:E4:42:CB:C2:BE:8D:B7:8C:17:1F
+                X509v3 Authority Key Identifier:
+                    keyid:F9:91:50:B2:42:8C:A8:D3:41:B0:E4:42:CB:C2:BE:8D:B7:8C:17:1F
+
+    Certificate is to be certified until Feb 28 02:17:11 2018 GMT (365 days)
+    Sign the certificate? [y/n]:y
+
+    1 out of 1 certificate requests certified, commit? [y/n]y
+    Write out database with 1 new entries
+    Data Base Updated
+    # 至此CA根证书自签发完成，根证书demoCA/cacert.pem。
+    ```
+
+5. 生成服务端证书私钥。
+
+    ```bash
+    # 生成服务器私钥文件server.key
+    openssl genrsa -aes256 -out server.key 2048
+    Generating a 2048 bit RSA private key
+    .......++++++
+    ..++++++
+    e is 65537 (0x10001)
+    Enter pass phrase for server.key:
+    # 服务器私钥的保护密码，假设为Test@123
+    Verifying - Enter pass phrase for server.key:
+    # 再次确认服务器私钥的保护密码，即为Test@123
+    ```
+
+6. 生成服务端证书请求文件。
+
+    ```bash
+    # 生成服务器证书请求文件server.req
+    openssl req -config openssl.cnf -new -key server.key -out server.req
+    Enter pass phrase for server.key:
+    You are about to be asked to enter information that will be incorporated
+    into your certificate request.
+    What you are about to enter is what is called a Distinguished Name or a DN.
+    There are quite a few fields but you can leave some blank
+    For some fields there will be a default value,
+    If you enter '.', the field will be left blank.
+    -----
+
+    # 以下填写的信息与创建CA时的信息一致
+    Country Name (2 letter code) [AU]:CN
+    State or Province Name (full name) [Some-State]:shanxi
+    Locality Name (eg, city) []:xian
+    Organization Name (eg, company) [Internet Widgits Pty Ltd]:Abc
+    Organizational Unit Name (eg, section) []:hello
+    # Common Name可以随意命名
+    Common Name (eg, YOUR name) []:world
+    Email Address []:
+    # 以下信息可以选择性填写
+    Please enter the following 'extra' attributes
+    to be sent with your certificate request
+    A challenge password []:
+    An optional company name []:
+    ```
+
+7. 生成服务端证书。
+
+    ```bash
+    # 生成服务端/客户端证书时，修改openssl.cnf文件，设置basicConstraints=CA:FALSE
+    vi openssl.cnf
+    # 修改demoCA/index.txt.attr中属性为no。
+    vi demoCA/index.txt.attr
+
+    # 对生成的服务端证书请求文件进行签发，签发后将生成正式的服务端证书server.crt
+    openssl ca  -config openssl.cnf -in server.req -out server.crt -days 3650 -md sha256
+    Using configuration from /etc/ssl/openssl.cnf
+    Enter pass phrase for ./demoCA/private/cakey.pem:
+    Check that the request matches the signature
+    Signature ok
+    Certificate Details:
+            Serial Number: 2 (0x2)
+            Validity
+                Not Before: Feb 27 10:11:12 2017 GMT
+                Not After : Feb 25 10:11:12 2027 GMT
+            Subject:
+                countryName               = CN
+                stateOrProvinceName       = shanxi
+                organizationName          = Abc
+                organizationalUnitName    = hello
+                commonName                = world
+            X509v3 extensions:
+                X509v3 Basic Constraints:
+                    CA:FALSE
+                Netscape Comment:
+                    OpenSSL Generated Certificate
+                X509v3 Subject Key Identifier:
+                    EB:D9:EE:C0:D2:14:48:AD:EB:BB:AD:B6:29:2C:6C:72:96:5C:38:35
+                X509v3 Authority Key Identifier:
+                    keyid:84:F6:A1:65:16:1F:28:8A:B7:0D:CB:7E:19:76:2A:8B:F5:2B:5C:6A
+
+    Certificate is to be certified until Feb 25 10:11:12 2027 GMT (3650 days)
+    # 选择y对证书进行签发
+    Sign the certificate? [y/n]:y
+
+    # 选择y，证书签发结束
+    1 out of 1 certificate requests certified, commit? [y/n]y
+    Write out database with 1 new entries
+    Data Base Updated
+    ```
+
+    去掉私钥密码保护，方法如下:
+
+    ```bash
+    # 去掉服务端私钥的密码保护
+    openssl rsa -in server.key -out server.key
+    # 如果不去掉服务端私钥的密码保护需要使用gs_guc工具对存储密码进行加密保护
+    gs_guc encrypt -M server -D ./
+    # 根据提示输入服务端私钥的密码，加密后会生成server.key.cipher,server.key.rand两个私钥密码保护文件
+    ```
+
+8. 客户端证书，私钥的生成。
+
+    生成客户端证书和客户端私钥的方法和要求与服务器相同。
+
+    ```bash
+    # 生成客户端私钥
+    openssl genrsa -aes256 -out client.key 2048
+    # 生成客户端证书请求文件
+    openssl req -config openssl.cnf -new -key client.key -out client.req
+    # 对生成的客户端证书请求文件进行签发，签发后将生成正式的客户端证书client.crt
+    openssl ca -config openssl.cnf -in client.req -out client.crt -days 3650 -md sha256
+    ```
+
+    去掉私钥密码保护，方法如下:
+
+    ```bash
+    # 去掉客户端私钥的密码保护
+    openssl rsa -in client.key -out client.key
+    # 如果不去掉客户端私钥的密码保护需要使用gs_guc工具对存储密码进行加密保护
+    gs_guc encrypt -M client -D ./
+    根据提示输入服务端私钥的密码，加密后会生成client.key.cipher,client.key.rand两个私钥密码保护文件。
+    ```
+
+    将客户端密钥转化为DER格式，方法如下:
+
+    ```bash
+    openssl pkcs8 -topk8 -outform DER -in client.key -out client.key.pk8 -nocrypt
+    ```
+
+9. 吊销证书列表的生成。
+
+    如果需要吊销列表，可按照如下方法生成:
+
+    ```
+    # 首先创建crlnumber文件
+    echo '00'>./demoCA/crlnumber
+    # 吊销服务端证书
+    openssl ca -config openssl.cnf -revoke server.crt
+    # 生成证书吊销列表sslcrl-file.crl
+    openssl ca -config openssl.cnf -gencrl -out sslcrl-file.crl
+    ```
+
+<br/>
+
+### 证书替换
+
+**操作场景**
+
+MogDB默认配置了SSL连接所需要的安全的证书、私钥，用户如果需要替换为自己的证书、私钥则可按照此方法进行替换。
+
+<br/>
+
+**前提条件**
+
+用户需要从CA认证中心申请到正式的服务器、客户端的证书和密钥。
+
+<br/>
+
+**注意事项**
+
+MogDB目前只支持X509v3的PEM格式证书。
+
+<br/>
+
+**操作步骤**
+
+1. 准备证书、私钥。
+
+    服务端各个配置文件名称约定:
+
+    - 证书名称约定: server.crt。
+
+    - 私钥名称约定: server.key。
+    - 私钥密码加密文件约定: server.key.cipher、server.key.rand。
+
+    客户端各个配置文件名称约定:
+
+    - 证书名称约定: client.crt。
+    - 私钥名称约定: client.key。
+    - 私钥密码加密文件约定: client.key.cipher、client.key.rand。
+    - 根证书名称约定: cacert.pem。
+    - 吊销证书列表文件名称约定: sslcrl-file.crl。
+
+2. 制作压缩包。
+
+    压缩包名称约定: db-cert-replacement.zip。
+
+    压缩包格式约定: ZIP。
+
+    压缩包文件列表约定: server.crt、server.key、server.key.cipher、server.key.rand、client.crt、client.key、client.key.cipher、client.key.   rand、cacert.pem。如果需要配置吊销证书列表，则列表中包含sslcrl-file.crl。
+
+3. 调用接口，执行替换。
+
+    a. 将制作好的压缩包db-cert-replacement.zip上传到MogDB用户下的任意路径。
+
+    例如: /home/xxxx/db-cert-replacement.zip。
+
+    b. 调用如下命令进行替换。
+
+    ```bash
+    gs_om -t cert --cert-file=/home/xxxx/db-cert-replacement.zip
+    ```
+
+4. 重启MogDB。
+
+    ```bash
+    gs_om -t stop
+    gs_om -t start
+    ```
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+    > 证书具有rollback功能，可以把上一次执行证书替换之前的证书，进行回退。可以使用gs_om -t cert -rollback进行远程调用该接口；使用gs_om -t cert -rollback -L进行本地调用该接口。以上一次成功执行证书替换后，被替换的证书版本为基础进行回退。
diff --git a/product/zh/docs-mogdb/v3.0/security-guide/security/2-managing-users-and-their-permissions.md b/product/zh/docs-mogdb/v3.0/security-guide/security/2-managing-users-and-their-permissions.md
new file mode 100644
index 0000000000000000000000000000000000000000..29e7d364398dbff98033845dd0bedd4e8c448db3
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/security-guide/security/2-managing-users-and-their-permissions.md
@@ -0,0 +1,1051 @@
+---
+title: 管理用户及权限
+summary: 管理用户及权限
+author: Guo Huan
+date: 2021-03-04
+---
+
+# 管理用户及权限
+
+<br/>
+
+## 默认权限机制
+
+数据库对象创建后，进行对象创建的用户就是该对象的所有者。MogDB安装后的默认情况下，未开启[三权分立](#三权分立)，数据库系统管理员具有与对象所有者相同的权限。也就是说对象创建后，默认只有对象所有者或者系统管理员可以查询、修改和销毁对象，以及通过GRANT将对象的权限授予其他用户。
+
+为使其他用户能够使用对象，必须向用户或包含该用户的角色授予必要的权限。
+
+MogDB支持以下的权限: SELECT、INSERT、UPDATE、DELETE、TRUNCATE、REFERENCES、CREATE、CONNECT、EXECUTE、ALTER、DROP、COMMENT、INDEX、VACUUM和USAGE。不同的权限与不同的对象类型关联。有关各权限的详细信息，请参见GRANT。
+
+要撤消已经授予的权限，可以使用REVOKE。对象所有者的权限（例如ALTER、 DROP、COMMENT、INDEX、VACUUM、GRANT和REVOKE）是隐式的，无法授予或撤消。即只要拥有对象就可以执行对象所有者的这些隐式权限。对象所有者可以撤消自己的普通权限，例如，使表对自己以及其他人只读，系统管理员用户除外。
+
+系统表和系统视图要么只对系统管理员可见，要么对所有用户可见。标识了需要系统管理员权限的系统表和视图只有系统管理员可以查询。 有关信息，请参考系统表和系统视图。
+
+数据库提供对象隔离的特性，对象隔离特性开启时，用户只能查看有权限访问的对象(表、视图、字段、函数)，系统管理员不受影响。有关信息，请参考ALTER DATABASE。
+
+<br/>
+
+## 管理员
+
+### 初始用户
+
+数据库安装过程中自动生成的帐户称为初始用户。初始用户拥有系统的最高权限，能够执行所有的操作。如果安装时不指定初始用户名称则该帐户与进行数据库安装的操作系统用户同名。如果在安装时不指定初始用户的密码，安装完成后密码为空，在执行其他操作前需要通过gsql客户端修改初始用户的密码。如果初始用户密码为空，则除修改密码外无法执行其他SQL操作以及升级、扩容、节点替换等操作。
+
+初始用户会绕过所有权限检查。建议仅将此初始用户作为DBA管理用途，而非业务应用。
+
+### 系统管理员
+
+系统管理员是指具有SYSADMIN属性的帐户，默认安装情况下具有与对象所有者相同的权限，但不包括dbe_perf模式的对象权限。
+
+要创建新的系统管理员，请以初始用户或者系统管理员用户身份连接数据库，并使用带SYSADMIN选项的CREATE USER语句或ALTER USER语句进行设置。
+
+```sql
+mogdb=# CREATE USER sysadmin WITH SYSADMIN password "xxxxxxxxx";
+```
+
+或者
+
+```sql
+mogdb=# ALTER USER joe SYSADMIN;
+```
+
+> ALTER USER时，要求用户已存在。
+
+### 监控管理员
+
+监控管理员是指具有MONADMIN属性的帐户，具有查看dbe_perf模式下视图和函数的权限，亦可以对dbe_perf模式的对象权限进行授予或收回。
+
+要创建新的监控管理员，请以系统管理员身份连接数据库，并使用带MONADMIN选项的CREATE USER语句或ALTER USER语句进行设置。
+
+```sql
+mogdb=# CREATE USER monadmin WITH MONADMIN password "xxxxxxxxx";
+```
+
+或者
+
+```sql
+mogdb=# ALTER USER joe MONADMIN;
+```
+
+> ALTER USER时，要求用户已存在。
+
+### 运维管理员
+
+运维管理员是指具有OPRADMIN属性的帐户，具有使用Roach工具执行备份恢复的权限。
+
+要创建新的运维管理员，请以初始用户身份连接数据库，并使用带OPRADMIN选项的CREATE USER语句或ALTER USER语句进行设置。
+
+```sql
+mogdb=# CREATE USER opradmin WITH OPRADMIN password "xxxxxxxxx";
+```
+
+或者
+
+```sql
+mogdb=# ALTER USER joe OPRADMIN;
+```
+
+> ALTER USER时，要求用户已存在。
+
+### 安全策略管理员
+
+安全策略管理员是指具有POLADMIN属性的帐户，具有创建资源标签，脱敏策略和统一审计策略的权限。
+
+要创建新的安全策略管理员，请以系统管理员用户身份连接数据库，并使用带POLADMIN选项的CREATE USER语句或ALTER USER语句进行设置。
+
+```sql
+mogdb=# CREATE USER poladmin WITH POLADMIN password "xxxxxxxxx";
+```
+
+或者
+
+```sql
+mogdb=# ALTER USER joe POLADMIN;
+```
+
+> ALTER USER时，要求用户已存在。
+
+<br/>
+
+## 三权分立
+
+[默认权限机制](#默认权限机制)和[管理员](#管理员)两节的描述基于的是MogDB创建之初的默认情况。从前面的介绍可以看出，默认情况下拥有SYSADMIN属性的系统管理员，具备系统最高权限。
+
+在实际业务管理中，为了避免系统管理员拥有过度集中的权利带来高风险，可以设置三权分立。将系统管理员的部分权限分立给安全管理员和审计管理员，形成系统管理员、安全管理员和审计管理员三权分立。
+
+三权分立后，系统管理员将不再具有CREATEROLE属性（安全管理员）和AUDITADMIN属性（审计管理员）能力。即不再拥有创建角色和用户的权限，并不再拥有查看和维护数据库审计日志的权限。关于CREATEROLE属性和AUDITADMIN属性的更多信息请参考CREATE ROLE。
+
+三权分立后，系统管理员只会对自己作为所有者的对象有权限。
+
+初始用户的权限不受三权分立设置影响。因此建议仅将此初始用户作为DBA管理用途，而非业务应用。
+
+三权分立的设置办法为: 将参数enableSeparationOfDuty设置为on。
+
+三权分立前的权限详情及三权分立后的权限变化，请分别参见[表1](#表2.3.1)和[表2](#表2.3.2)。
+
+**表 1** 默认的用户权限 <a id="表2.3.1"> </a>
+
+<table>
+  <tr>
+    <th>对象名称</th>
+    <th>初始用户（id为10）</th>
+    <th>系统管理员</th>
+    <th>监控管理员</th>
+    <th>运维管理员</th>
+    <th>安全策略管理员</th>
+    <th>安全管理员</th>
+    <th>审计管理员</th>
+    <th>普通用户</th>
+  </tr>
+  <tr>
+    <td>表空间</td>
+    <td rowspan="7">具有除私有用户表对象访问权限外，所有的权限。</td>
+    <td>对表空间有创建、修改、删除、访问、分配操作的权限。</td>
+    <td colspan="6">不具有对表空间进行创建、修改、删除、分配的权限，访问需要被赋权。</td>
+  </tr>
+  <tr>
+    <td>表</td>
+    <td>对所有表有所有的权限。</td>
+    <td colspan="6">仅对自己的表有所有的权限，对其他用户的表无权限。</td>
+  </tr>
+  <tr>
+    <td>索引</td>
+    <td>可以在所有的表上建立索引。</td>
+    <td colspan="6">仅可以在自己的表上建立索引。</td>
+  </tr>
+  <tr>
+    <td>模式</td>
+    <td>对除dbe_perf以外的所有模式有所有的权限。</td>
+    <td>仅对dbe_perf模式和自己的模式有所有的权限，对其他用户的模式无权限。</td>
+    <td colspan="5">仅对自己的模式有所有的权限，对其他用户的模式无权限。</td>
+  </tr>
+  <tr>
+    <td>函数</td>
+    <td>对除dbe_perf模式下的函数以外的所有的函数有所有的权限。</td>
+    <td>仅对dbe_perf模式下的和自己的函数有所有的权限，对其他用户放在public这个公共模式下的函数有调用的权限，对其他用户放在其他模式下的函数无权限。</td>
+    <td colspan="5">仅对自己的函数有所有的权限，对其他用户放在public这个公共模式下的函数有调用的权限，对其他用户放在其他模式下的函数无权限。</td>
+  </tr>
+  <tr>
+    <td>自定义视图</td>
+    <td>对除dbe_perf模式下的视图以外的所有的视图有所有的权限。</td>
+    <td>仅对dbe_perf模式下的和自己的视图有所有的权限，对其他用户的视图无权限。</td>
+    <td colspan="5">仅对自己的视图有所有的权限，对其他用户的视图无权限。</td>
+  </tr>
+  <tr>
+    <td>系统表和系统视图</td>
+    <td>可以查看所有系统表和视图。</td>
+    <td colspan="6">只可以查看部分系统表和视图。详细请参见系统表和系统视图。</td>
+  </tr>
+</table>
+
+**表 2** 三权分立较非三权分立权限变化说明 <a id="表2.3.2"> </a>
+
+<table>
+  <tr>
+    <th>对象名称</th>
+    <th>初始用户（id为10）</th>
+    <th>系统管理员</th>
+    <th>监控管理员</th>
+    <th>运维管理员</th>
+    <th>安全策略管理员</th>
+    <th>安全管理员</th>
+    <th>审计管理员</th>
+    <th>普通用户</th>
+  </tr>
+  <tr>
+    <td>表空间</td>
+    <td rowspan="7">无变化。<br/>依然具有除私有用户表对象访问权限外，所有的权限。</td>
+    <td>无变化。</td>
+    <td colspan="6">无变化。</td>
+  </tr>
+  <tr>
+    <td>表</td>
+    <td>权限缩小。<br/>只对自己的表及其他用户放在public模式下的表有所有的权限，对其他用户放在属于各自模式下的表无权限。</td>
+    <td colspan="6">无变化。</td>
+  </tr>
+  <tr>
+    <td>索引</td>
+    <td>权限缩小。<br/>只可以在自己的表及其他用户放在public模式下的表上建立索引。</td>
+    <td colspan="6">无变化。</td>
+  </tr>
+  <tr>
+    <td>模式</td>
+    <td>权限缩小。<br/>只对自己的模式有所有的权限，对其他用户的模式无权限。</td>
+    <td>无变化。</td>
+    <td colspan="5">无变化。</td>
+  </tr>
+  <tr>
+    <td>函数</td>
+    <td>权限缩小。<br/>只对自己的函数及其他用户放在public模式下的函数有所有的权限，对其他用户放在属于各自模式下的函数无权限。</td>
+    <td>无变化。</td>
+    <td colspan="5">无变化。</td>
+  </tr>
+  <tr>
+    <td>自定义视图</td>
+    <td>权限缩小。<br/>只对自己的视图及其他用户放在public模式下的视图有所有的权限，对其他用户放在属于各自模式下的视图无权限。</td>
+    <td>无变化。</td>
+    <td colspan="5">无变化。</td>
+  </tr>
+  <tr>
+    <td>系统表和系统视图</td>
+    <td>无变化。</td>
+    <td colspan="6">无变化。</td>
+  </tr>
+</table>
+<br/>
+
+## 用户
+
+使用CREATE USER和ALTER USER可以创建和管理数据库用户。MogDB包含一个或多个已命名数据库。用户和角色在整个MogDB范围内是共享的，但是其数据并不共享。即用户可以连接任何数据库，但当连接成功后，任何用户都只能访问连接请求里声明的那个数据库。
+
+非[三权分立](#三权分立)下，MogDB用户帐户只能由系统管理员或拥有CREATEROLE属性的安全管理员创建和删除。三权分立时，用户帐户只能由初始用户和安全管理员创建。
+
+在用户登录MogDB时会对其进行身份验证。用户可以拥有数据库和数据库对象（例如表），并且可以向用户和角色授予对这些对象的权限以控制谁可以访问哪个对象。除系统管理员外，具有CREATEDB属性的用户可以创建数据库并授予对这些数据库的权限。
+
+**创建、修改和删除用户**
+
+- 要创建用户，请使用SQL语句CREATE USER。
+
+  例如: 创建用户joe，并设置用户拥有CREATEDB属性。
+
+  ```sql
+  mogdb=# CREATE USER joe WITH CREATEDB PASSWORD "XXXXXXXXX";
+  CREATE ROLE
+  ```
+
+- 要创建系统管理员，请使用带有SYSADMIN选项的CREATE USER语句。
+
+- 要删除现有用户，请使用DROP USER。
+
+- 要更改用户帐户（例如，重命名用户或更改密码），请使用ALTER USER。
+
+- 要查看用户列表，请查询视图PG_USER:
+
+  ```sql
+  mogdb=# SELECT * FROM pg_user;
+  ```
+
+- 要查看用户属性，请查询系统表PG_AUTHID:
+
+  ```sql
+  mogdb=# SELECT * FROM pg_authid;
+  ```
+
+**私有用户**
+
+对于有多个业务部门，各部门间使用不同的数据库用户进行业务操作，同时有一个同级的数据库维护部门使用数据库管理员进行维护操作的场景下，业务部门可能希望在未经授权的情况下，管理员用户只能对各部门的数据进行控制操作（DROP、ALTER、TRUNCATE），但是不能进行访问操作（INSERT、DELETE、UPDATE、SELECT、COPY）。即针对管理员用户，表对象的控制权和访问权要能够分离，提高普通用户数据安全性。
+
+[三权分立](#三权分立)情况下，管理员对其他用户放在属于各自模式下的表无权限。但是，这种无权限包含了无控制权限，因此不能满足上面的诉求。为此，MogDB提供了私有用户方案。即在非三权分立模式下，创建具有INDEPENDENT属性的私有用户。
+
+```sql
+mogdb=# CREATE USER user_independent WITH INDEPENDENT IDENTIFIED BY "1234@abc";
+```
+
+针对该用户的对象，系统管理员和拥有CREATEROLE属性的安全管理员在未经其授权前，只能进行控制操作（DROP、ALTER、TRUNCATE），无权进行INSERT、DELETE、SELECT、UPDATE、COPY、GRANT、REVOKE、ALTER OWNER操作。
+
+**永久用户**
+
+MogDB提供永久用户方案，即创建具有PERSISTENCE属性的永久用户。
+
+```sql
+mogdb=# CREATE USER user_persistence WITH persistence IDENTIFIED BY "1234@abc";
+```
+
+只允许初始用户创建、修改和删除具有PERSISTENCE属性的永久用户。
+
+<br/>
+
+## 角色
+
+角色是一组用户的集合。通过GRANT把角色授予用户后，用户即具有了角色的所有权限。推荐使用角色进行高效权限分配。例如，可以为设计、开发和维护人员创建不同的角色，将角色GRANT给用户后，再向每个角色中的用户授予其工作所需数据的差异权限。在角色级别授予或撤消权限时，这些更改将作用到角色下的所有成员。
+
+MogDB提供了一个隐式定义的拥有所有角色的组PUBLIC，所有创建的用户和角色默认拥有PUBLIC所拥有的权限。关于PUBLIC默认拥有的权限请参考GRANT。要撤销或重新授予用户和角色对PUBLIC的权限， 可通过在GRANT和REVOKE指定关键字PUBLIC实现。
+
+要查看所有角色，请查询系统表PG_ROLES:
+
+```sql
+SELECT * FROM PG_ROLES;
+```
+
+**创建、修改和删除角色**
+
+非[三权分立](#三权分立)时，只有系统管理员和具有CREATEROLE属性的用户才能创建、修改或删除角色。三权分立下，只有初始用户和具有CREATEROLE属性的用户才能创建、修改或删除角色。
+
+- 要创建角色，请使用CREATE ROLE。
+- 要在现有角色中添加或删除用户，请使用ALTER ROLE。
+- 要删除角色，请使用DROP ROLE。DROP ROLE只会删除角色，并不会删除角色中的成员用户帐户。
+
+**内置角色**
+
+MogDB提供了一组默认角色，以gs_role_开头命名。它们提供对特定的、通常需要高权限的操作的访问，可以将这些角色GRANT给数据库内的其他用户或角色，让这些用户能够使用特定的功能。在授予这些角色时应当非常小心，以确保它们被用在需要的地方。[表3](#表1)描述了内置角色允许的权限范围：
+
+**表 3** 内置角色权限描述<a id="表1"></a>
+
+| 角色                     | 权限描述                                                     |
+| :----------------------- | :----------------------------------------------------------- |
+| gs_role_copy_files       | 具有执行copy … to/from filename 的权限，但需要先打开GUC参数enable_copy_server_files。 |
+| gs_role_signal_backend   | 具有调用函数pg_cancel_backend、pg_terminate_backend和pg_terminate_session来取消或终止其他会话的权限，但不能操作属于初始用户和PERSISTENCE用户的会话。 |
+| gs_role_tablespace       | 具有创建表空间（tablespace）的权限。                         |
+| gs_role_replication      | 具有调用逻辑复制相关函数的权限，例如kill_snapshot、pg_create_logical_replication_slot、pg_create_physical_replication_slot、pg_drop_replication_slot、pg_replication_slot_advance、pg_create_physical_replication_slot_extern、pg_logical_slot_get_changes、pg_logical_slot_peek_changes、pg_logical_slot_get_binary_changes、pg_logical_slot_peek_binary_changes。 |
+| gs_role_account_lock     | 具有加解锁用户的权限，但不能加解锁初始用户和PERSISTENCE用户。 |
+| gs_role_pldebugger       | 具有执行dbe_pldebugger下调试函数的权限。                     |
+| gs_role_directory_create | 具有执行创建directory对象的权限，但需要先打开GUC参数enable_access_server_directory。 |
+| gs_role_directory_drop   | 具有执行删除directory对象的权限，但需要先打开GUC参数enable_access_server_directory。 |
+
+关于内置角色的管理有如下约束：
+
+- 以gs_role_开头的角色名作为数据库的内置角色保留名，禁止新建以gs_role_开头的用户/角色，也禁止将已有的用户/角色重命名为以gs_role_开头；
+
+- 禁止对内置角色的ALTER和DROP操作；
+
+- 内置角色默认没有LOGIN权限，不设预置密码；
+
+- gsql元命令\\du和**\\dg**不显示内置角色的相关信息，但若显示指定了pattern为特定内置角色则会显示。
+
+- 三权分立关闭时，初始用户、具有SYSADMIN权限的用户和具有内置角色ADMIN OPTION权限的用户有权对内置角色执行GRANT/REVOKE管理。三权分立打开时，初始用户和具有内置角色ADMIN OPTION权限的用户有权对内置角色执行GRANT/REVOKE管理。例如：
+
+  ```sql
+  GRANT gs_role_signal_backend TO user1;
+  REVOKE gs_role_signal_backend FROM user1;
+  ```
+
+<br/>
+
+## Schema
+
+Schema又称作模式。通过管理Schema，允许多个用户使用同一数据库而不相互干扰，可以将数据库对象组织成易于管理的逻辑组，同时便于将第三方应用添加到相应的Schema下而不引起冲突。
+
+每个数据库包含一个或多个Schema。数据库中的每个Schema包含表和其他类型的对象。数据库创建初始，默认具有一个名为public的Schema，且所有用户都拥有此Schema的usage权限，只有系统管理员和初始化用户可以在public Schema下创建函数、存储过程和同义词对象，其他用户即使赋予create权限后也不可以创建上述三种对象。可以通过Schema分组数据库对象。Schema类似于操作系统目录，但Schema不能嵌套。
+
+相同的数据库对象名称可以应用在同一数据库的不同Schema中，而没有冲突。例如，a_schema和b_schema都可以包含名为mytable的表。具有所需权限的用户可以访问数据库的多个Schema中的对象。
+
+CREATE USER创建用户的同时，系统会在执行该命令的数据库中，为该用户创建一个同名的SCHEMA。
+
+数据库对象是创建在数据库搜索路径中的第一个Schema内的。有关默认情况下的第一个Schema情况及如何变更Schema顺序等更多信息，请参见[搜索路径](#搜索路径)。
+
+**创建、修改和删除Schema**
+
+- 要创建Schema，请使用CREATE SCHEMA。默认初始用户和系统管理员可以创建Schema，其他用户需要具备数据库的CREATE权限才可以在该数据库中创建Schema，赋权方式请参考GRANT中将数据库的访问权限赋予指定的用户或角色中的语法。
+
+- 要更改Schema名称或者所有者，请使用ALTER SCHEMA。Schema所有者可以更改Schema。
+
+- 要删除Schema及其对象，请使用DROP SCHEMA。Schema所有者可以删除Schema。
+
+- 要在Schema内创建表，请以schema_name.table_name格式创建表。不指定schema_name时，对象默认创建到[搜索路径](#搜索路径)中的第一个Schema内。
+
+- 要查看Schema所有者，请对系统表PG_NAMESPACE和PG_USER执行如下关联查询。语句中的schema_name请替换为实际要查找的Schema名称。
+
+  ```sql
+  mogdb=# SELECT s.nspname,u.usename AS nspowner FROM pg_namespace s, pg_user u WHERE nspname='schema_name' AND s.nspowner = u.usesysid;
+  ```
+
+- 要查看所有Schema的列表，请查询PG_NAMESPACE系统表。
+
+  ```sql
+  mogdb=# SELECT * FROM pg_namespace;
+  ```
+
+- 要查看属于某Schema下的表列表，请查询系统视图PG_TABLES。例如，以下查询会返回Schema PG_CATALOG中的表列表。
+
+  ```sql
+  mogdb=# SELECT distinct(tablename),schemaname from pg_tables where schemaname = 'pg_catalog';
+  ```
+
+**搜索路径** <a id="搜索路径"> </a>
+
+搜索路径定义在search_path参数中，参数取值形式为采用逗号分隔的Schema名称列表。如果创建对象时未指定目标Schema，则将该对象会被添加到搜索路径中列出的第一个Schema中。当不同Schema中存在同名的对象时，查询对象未指定Schema的情况下，将从搜索路径中包含该对象的第一个Schema中返回对象。
+
+- 要查看当前搜索路径，请使用SHOW。
+
+  ```sql
+  mogdb=# SHOW SEARCH_PATH;
+   search_path
+  ----------------
+   "$user",public
+  (1 row)
+  ```
+
+  search_path参数的默认值为: `"$user",public`。`$user`表示与当前会话用户名同名的Schema名，如果这样的模式不存在，`$user`将被忽略。所以默认情况下，用户连接数据库后，如果数据库下存在同名Schema，则对象会添加到同名Schema下，否则对象被添加到Public Schema下。
+
+- 要更改当前会话的默认Schema，请使用SET命令。
+
+  执行如下命令将搜索路径设置为myschema、public，首先搜索myschema。
+
+  ```sql
+  mogdb=# SET SEARCH_PATH TO myschema, public;
+  SET
+  ```
+
+<br/>
+
+## 用户权限设置
+
+- 给用户直接授予某对象的权限，请使用GRANT。
+
+  将Schema中的表或者视图对象授权给其他用户或角色时，需要将表或视图所属Schema的USAGE权限同时授予该用户或角色。否则用户或角色将只能看到这些对象的名称，并不能实际进行对象访问。
+
+  例如，下面示例将Schema tpcds的权限赋给用户joe后，将表tpcds.web_returns的select权限赋给用户joe。
+
+  ```sql
+  mogdb=# GRANT USAGE ON SCHEMA tpcds TO joe;
+  mogdb=# GRANT SELECT ON TABLE tpcds.web_returns to joe;
+  ```
+
+- 给用户指定角色，使用户继承角色所拥有的对象权限。
+
+  1. 创建角色。
+
+     新建一个角色lily，同时给角色指定系统权限CREATEDB:
+
+     ```sql
+     CREATE ROLE lily WITH CREATEDB PASSWORD "XXXXXXXXX";
+     ```
+
+  2. 给角色赋予对象权限，请使用GRANT。
+
+     例如，将模式tpcds的权限赋给角色lily后，将表tpcds.web_returns的select权限赋给角色lily。
+
+     ```sql
+     mogdb=# GRANT USAGE ON SCHEMA tpcds TO lily;
+     mogdb=# GRANT SELECT ON TABLE tpcds.web_returns to lily;
+     ```
+
+  3. 将角色的权限赋予用户。
+
+     ```sql
+     GRANT lily to joe;
+     ```
+
+     > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif)**说明:**
+     > 当将角色的权限赋予用户时，角色的属性并不会传递到用户。
+
+- 回收用户权限，请使用REVOKE。
+
+<br/>
+
+## 行级访问控制
+
+行级访问控制特性将数据库访问控制精确到数据表行级别，使数据库达到行级访问控制的能力。不同用户执行相同的SQL查询操作，读取到的结果是不同的。
+
+用户可以在数据表创建行访问控制(Row Level Security)策略，该策略是指针对特定数据库用户、特定SQL操作生效的表达式。当数据库用户对数据表访问时，若SQL满足数据表特定的Row Level Security策略，在查询优化阶段将满足条件的表达式，按照属性(PERMISSIVE | RESTRICTIVE)类型，通过AND或OR方式拼接，应用到执行计划上。
+
+行级访问控制的目的是控制表中行级数据可见性，通过在数据表上预定义Filter，在查询优化阶段将满足条件的表达式应用到执行计划上，影响最终的执行结果。当前受影响的SQL语句包括SELECT，UPDATE，DELETE。
+
+示例: 某表中汇总了不同用户的数据，但是不同用户只能查看自身相关的数据信息，不能查看其他用户的数据信息。
+
+```sql
+--创建用户alice, bob, peter
+mogdb=# CREATE ROLE alice PASSWORD 'Gauss@123';
+mogdb=# CREATE ROLE bob PASSWORD 'Gauss@123';
+mogdb=# CREATE ROLE peter PASSWORD 'Gauss@123';
+
+--创建表all_data，包含不同用户数据信息
+mogdb=# CREATE TABLE all_data(id int, role varchar(100), data varchar(100));
+
+--向数据表插入数据
+mogdb=# INSERT INTO all_data VALUES(1, 'alice', 'alice data');
+mogdb=# INSERT INTO all_data VALUES(2, 'bob', 'bob data');
+mogdb=# INSERT INTO all_data VALUES(3, 'peter', 'peter data');
+
+--将表all_data的读取权限赋予alice，bob和peter用户
+mogdb=# GRANT SELECT ON all_data TO alice, bob, peter;
+
+--打开行访问控制策略开关
+mogdb=# ALTER TABLE all_data ENABLE ROW LEVEL SECURITY;
+
+--创建行访问控制策略，当前用户只能查看用户自身的数据
+mogdb=# CREATE ROW LEVEL SECURITY POLICY all_data_rls ON all_data USING(role = CURRENT_USER);
+
+--查看表详细信息
+mogdb=# \d+ all_data
+                 Table "public.all_data"
+ Column |      Type      | Modifiers | Storage  | Stats target | Description
+--------+------------------------+-----------+----------+--------------+-------------
+ id   | integer        |       | plain  |        |
+ role   | character varying(100) |       | extended |        |
+ data   | character varying(100) |       | extended |        |
+Row Level Security Policies:
+  POLICY "all_data_rls"
+    USING (((role)::name = "current_user"()))
+Has OIDs: no
+Location Nodes: ALL DATANODES
+Options: orientation=row, compression=no, enable_rowsecurity=true
+
+--切换至用户alice，执行SQL"SELECT * FROM public.all_data"
+mogdb=# SELECT * FROM public.all_data;
+ id | role  |  data
+----+-------+------------
+  1 | alice | alice data
+(1 row)
+
+mogdb=# EXPLAIN(COSTS OFF) SELECT * FROM public.all_data;
+               QUERY PLAN
+----------------------------------------------------------------
+ Streaming (type: GATHER)
+   Node/s: All datanodes
+   ->  Seq Scan on all_data
+     Filter: ((role)::name = 'alice'::name)
+ Notice: This query is influenced by row level security feature
+(5 rows)
+
+--切换至用户peter，执行SQL"SELECT * FROM public.all_data"
+mogdb=# SELECT * FROM public.all_data;
+ id | role  |  data
+----+-------+------------
+  3 | peter | peter data
+(1 row)
+
+mogdb=#  EXPLAIN(COSTS OFF) SELECT * FROM public.all_data;
+               QUERY PLAN
+----------------------------------------------------------------
+ Streaming (type: GATHER)
+   Node/s: All datanodes
+   ->  Seq Scan on all_data
+     Filter: ((role)::name = 'peter'::name)
+ Notice: This query is influenced by row level security feature
+(5 rows)
+```
+
+<br/>
+
+## 设置安全策略
+
+### 设置帐户安全策略
+
+**背景信息**
+
+MogDB为帐户提供了自动锁定和解锁帐户、手动锁定和解锁异常帐户和删除不再使用的帐户等一系列的安全措施，保证数据安全。
+
+**自动锁定和解锁帐户**
+
+- 为了保证帐户安全，如果用户输入密码次数超过一定次数（failed_login_attempts），系统将自动锁定该帐户，默认值为10。次数设置越小越安全，但是在使用过程中会带来不便。
+
+- 当帐户被锁定时间超过设定值（password_lock_time），则当前帐户自动解锁，默认值为1天。时间设置越长越安全，但是在使用过程中会带来不便。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+  >
+  > - 参数password_lock_time的整数部分表示天数，小数部分可以换算成时、分、秒。
+  > - 当failed_login_attempts设置为0时，表示不限制密码错误次数。当password_lock_time设置为0时，表示即使超过密码错误次数限制导致帐户锁定，也会在短时间内自动解锁。因此，只有两个配置参数都为正数时，才可以进行常规的密码失败检查、帐户锁定和解锁操作。
+  > - 这两个参数的默认值都符合安全标准，用户可以根据需要重新设置参数，提高安全等级。建议用户使用默认值。
+
+配置failed_login_attempts参数。
+
+1. 以操作系统用户omm登录数据库主节点。
+
+2. 使用如下命令连接数据库。
+
+   ```bash
+   gsql -d postgres -p 8000
+   ```
+
+   postgres为需要连接的数据库名称，8000为数据库主节点的端口号。
+
+3. 查看已配置的参数。
+
+   ```sql
+   mogdb=# SHOW failed_login_attempts;
+      failed_login_attempts
+     -----------------------
+      10
+     (1 row)
+   ```
+
+   如果显示结果不为10，执行\\q命令退出数据库。
+
+4. 执行如下命令设置成默认值10。
+
+   ```bash
+   gs_guc reload -D /mogdb/data/dbnode -c "failed_login_attempts=10"
+   ```
+
+配置password_lock_time参数。
+
+1. 以操作系统用户omm登录数据库主节点。
+
+2. 使用如下命令连接数据库。
+
+   ```bash
+   gsql -d postgres -p 8000
+   ```
+
+   postgres为需要连接的数据库名称，8000为数据库主节点的端口号。
+
+3. 查看已配置的参数。
+
+   ```sql
+   mogdb=# SHOW password_lock_time;
+   password_lock_time
+   -----------------------
+    1
+   (1 row)
+   ```
+
+   如果显示结果不为1，执行\\q命令退出数据库。
+
+4. 执行如下命令设置成默认值1。
+
+   ```bash
+   gs_guc reload -N all -I all -c "password_lock_time=1"
+   ```
+
+**手动锁定和解锁帐户**
+
+若管理员发现某帐户被盗、非法访问等异常情况，可手动锁定该帐户。
+
+当管理员认为帐户恢复正常后，可手动解锁该帐户。
+
+以手动锁定和解锁用户joe为例，用户的创建请参见[用户](#用户)，命令格式如下:
+
+- 手动锁定
+
+  ```sql
+  mogdb=# ALTER USER joe ACCOUNT LOCK;
+  ALTER ROLE
+  ```
+
+- 手动解锁
+
+  ```sql
+  mogdb=# ALTER USER joe ACCOUNT UNLOCK;
+  ALTER ROLE
+  ```
+
+**删除不再使用的帐户**
+
+当确认帐户不再使用，管理员可以删除帐户。该操作不可恢复。
+
+当删除的用户正处于活动状态时，此会话状态不会立马断开，用户在会话状态断开后才会被完全删除。
+
+以删除帐户joe为例，命令格式如下:
+
+```sql
+mogdb=# DROP USER joe  CASCADE;
+DROP ROLE
+```
+
+<br/>
+
+### 设置帐号有效期
+
+<br/>
+
+**注意事项**
+
+创建新用户时，需要限制用户的操作期限（有效开始时间和有效结束时间）。
+
+不在有效操作期内的用户需要重新设定帐号的有效操作期。
+
+**操作步骤**
+
+1. 以操作系统用户omm登录数据库主节点。
+
+2. 使用如下命令连接数据库。
+
+   ```bash
+   gsql -d postgres -p 8000
+   ```
+
+   postgres为需要连接的数据库名称，8000为数据库主节点的端口号。
+
+3. 创建用户并制定用户的有效开始时间和有效结束时间。
+
+   ```sql
+   CREATE USER joe WITH PASSWORD 'XXXXXXXXX' VALID BEGIN '2015-10-10 08:00:00' VALID UNTIL '2016-10-10 08:00:00';
+   ```
+
+   显示如下信息表示创建用户成功。
+
+   ```sql
+    CREATE ROLE
+   ```
+
+4. 用户已不在有效使用期内，需要重新设定帐号的有效期，这包括有效开始时间和有效结束时间。
+
+   ```sql
+   ALTER USER joe WITH VALID BEGIN '2016-11-10 08:00:00' VALID UNTIL '2017-11-10 08:00:00';
+   ```
+
+   显示如下信息表示重新设定成功。
+
+   ```sql
+   ALTER ROLE
+   ```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+> 若在"CREATE ROLE"或"ALTER ROLE"语法中不指定"VALID BEGIN"，表示不对用户的开始操作时间做限定；若不指定"VALID UNTIL"，表示不对用户的结束操作时间做限定；若两者均不指定，表示该用户一直有效。
+
+<br/>
+
+### 设置密码安全策略
+
+<br/>
+
+**操作步骤**
+
+用户密码存储在系统表pg_authid中，为防止用户密码泄露，MogDB对用户密码进行加密存储，所采用的加密算法由配置参数password_encryption_type决定。
+
+- 当参数password_encryption_type设置为0时，表示采用md5方式对密码加密。MD5加密算法安全性低，存在安全风险，不建议使用。
+- 当参数password_encryption_type设置为1时，表示采用sha256和md5方式对密码加密。MD5加密算法安全性低，存在安全风险，不建议使用。
+- 当参数password_encryption_type设置为2时，表示采用sha256方式对密码加密，为默认配置。
+- 当参数password_encryption_type设置为3时，表示采用sm3方式对密码加密。
+
+1. 以操作系统用户omm登录数据库主节点。
+
+2. 使用如下命令连接数据库。
+
+   ```bash
+   gsql -d postgres -p 8000
+   ```
+
+   postgres为需要连接的数据库名称，8000为数据库主节点的端口号。
+
+3. 查看已配置的加密算法。
+
+   ```sql
+   mogdb=# SHOW password_encryption_type;
+   password_encryption_type
+   --------------------------
+   2
+   (1 row)
+   ```
+
+   如果显示结果为0或1，执行\\q命令退出数据库。
+
+4. 执行如下命令将其设置为安全的加密算法。
+
+   ```bash
+   gs_guc reload -N all -I all -c "password_encryption_type=2"
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-notice.gif) **须知:** 为防止用户密码泄露，在执行CREATE USER/ROLE命令创建数据库用户时，不能指定UNENCRYPTED属性，即新创建的用户的密码只能是加密存储的。
+
+5. 配置密码安全参数。
+
+   - 密码复杂度
+
+     初始化数据库、创建用户、修改用户时需要指定密码。密码必须要符合复杂度（password_policy）的要求，否则会提示用户重新输入密码。
+
+     - 参数password_policy设置为1时表示采用密码复杂度校验，默认值。
+     - 参数password_policy设置为0时表示不采用任何密码复杂度校验，设置为0会存在安全风险，不建议设置为0，即使需要设置也要将所有MogDB节点中的password_policy都设置为0才能生效。
+
+     配置password_policy参数。
+
+     a. 使用如下命令连接数据库。
+
+     ```bash
+     gsql -d postgres -p 8000
+     ```
+
+     postgres为需要连接的数据库名称，8000为数据库主节点的端口号。
+
+     b. 查看已配置的参数。
+
+     ```sql
+     mogdb=# SHOW password_policy;
+     password_policy
+     ---------------------
+     1
+     (1 row)
+     ```
+
+     如果显示结果不为1，执行\q命令退出数据库。
+
+     c. 执行如下命令设置成默认值1。
+
+     ```bash
+     gs_guc reload -N all -I all -c "password_policy=1"
+     ```
+
+     > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+     >
+     > 帐户密码的复杂度要求如下：
+     >
+     > - 包含大写字母（A-Z）的最少个数（password_min_uppercase）
+     >
+     > - 包含小写字母（a-z）的最少个数（password_min_lowercase）
+     >
+     > - 包含数字（0-9）的最少个数（password_min_digital）
+     >
+     > - 包含特殊字符的最少个数（password_min_special）（特殊字符的列表请参见[表3](#表2.9.3.1)。
+     >
+     > - 密码的最小长度（password_min_length）
+     >
+     > - 密码的最大长度（password_max_length）
+     >
+     > - 至少包含上述四类字符中的三类。
+     >
+     > - 不能和用户名、用户名倒写相同，本要求为非大小写敏感。
+     >
+     > - 不能和当前密码、当前密码的倒写相同。
+     >
+     > - 不能是弱口令。
+     >
+     > - 弱口令指的是强度较低，容易被破解的密码，对于不同的用户或群体，弱口令的定义可能会有所区别，用户需自己添加定制化的弱口令。
+     >
+     > - 弱口令字典中的口令存放在gs_global_config系统表中，当创建用户、修改用户需要设置密码时，系统将会把用户设置口令和弱口令字典中存放的口令进行对比，如果符合，则会提示用户该口令为弱口令，设置密码失败。
+     >
+     > - 弱口令字典默认为空，用户通过以下语法可以对弱口令字典进行增加和删除，示例
+     >
+     >   下：
+     >
+     >   ```sql
+     >   mogdb=# CREATE WEAK PASSWORD DICTIONARY WITH VALUES ('password1'), ('password2');
+     >   mogdb=# DROP WEAK PASSWORD DICTIONARY;
+     >   ```
+
+   - 密码重用
+
+     用户修改密码时，只有超过不可重用天数（password_reuse_time）或不可重用次数（password_reuse_max）的密码才可以使用。参数配置说明如[表5](#表2.9.3.2)所示。
+
+     > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:** 不可重用天数默认值为60天，不可重用次数默认值是0。这两个参数值越大越安全，但是在使用过程中会带来不便，其默认值符合安全标准，用户可以根据需要重新设置参数，提高安全等级。
+
+     配置password_reuse_time参数。
+
+     a. 使用如下命令连接数据库。
+
+     ```bash
+     gsql -d postgres -p 8000
+     ```
+
+     postgres为需要连接的数据库名称，8000为数据库主节点的端口号。
+
+     b. 查看已配置的参数。
+
+     ```sql
+     mogdb=# SHOW password_reuse_time;
+     password_reuse_time
+     ---------------------
+     60
+     (1 row)
+     ```
+
+     如果显示结果不为60，执行\q命令退出数据库。
+
+     c. 执行如下命令设置成默认值60。
+
+     > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:** 不建议设置为0，即使需要设置也要将所有MogDB节点中的password_reuse_time都设置为0才能生效。
+
+     ```bash
+     gs_guc reload -N all -I all -c "password_reuse_time=60"
+     ```
+
+     配置password_reuse_max参数。
+
+     a. 使用如下命令连接数据库。
+
+     ```bash
+     gsql -d postgres -p 8000
+     ```
+
+     postgres为需要连接的数据库名称，8000为数据库主节点的端口号。
+
+     b. 查看已配置的参数。
+
+     ```sql
+     mogdb=# SHOW password_reuse_max;
+     password_reuse_max
+     --------------------
+     0
+     (1 row)
+     ```
+
+     如果显示结果不为0，执行\q命令退出数据库。
+
+     c. 执行如下命令设置成默认值0。
+
+     ```bash
+     gs_guc reload -N all -I all -c "password_reuse_max = 0"
+     ```
+
+   - 密码有效期
+
+     数据库用户的密码都有密码有效期（password_effect_time），当达到密码到期提醒天数（password_notify_time）时，系统会在用户登录数据库时提示用户修改密码。
+
+     > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:** 考虑到数据库使用特殊性及业务连续性，密码过期后用户还可以登录数据库，但是每次登录都会提示修改密码，直至修改为止。
+
+     配置password_effect_time参数。
+
+     a. 使用如下命令连接数据库。
+
+     ```bash
+     gsql -d postgres -p 8000
+     ```
+
+     postgres为需要连接的数据库名称，8000为数据库主节点的端口号。
+
+     b. 查看已配置的参数。
+
+     ```sql
+     mogdb=# SHOW password_effect_time;
+     password_effect_time
+     ----------------------
+     90
+     (1 row)
+     ```
+
+     如果显示结果不为90，执行\q命令退出数据库。
+
+     c. 执行如下命令设置成默认值90（不建议设置为0）。
+
+     ```bash
+     gs_guc reload -N all -I all -c "password_effect_time = 90"
+     ```
+
+     配置password_notify_time参数。
+
+     a. 使用如下命令连接数据库。
+
+     ```bash
+     gsql -d postgres -p 8000
+     ```
+
+     postgres为需要连接的数据库名称，8000为数据库主节点的端口号。
+
+     b. 查看已配置的参数。
+
+     ```sql
+     mogdb=# SHOW password_notify_time;
+     password_notify_time
+     ----------------------
+     7
+     (1 row)
+     ```
+
+     c. 如果显示结果不为7，执行如下命令设置成默认值7（不建议设置为0）。
+
+     ```bash
+     gs_guc reload -N all -I all -c "password_notify_time = 7"
+     ```
+
+   - 密码修改
+
+     - 在安装数据库时，会新建一个和初始化用户重名的操作系统用户，为了保证帐户安全，请定期修改操作系统用户的密码。
+
+       以修改用户user1密码为例，命令格式如下:
+
+       ```sql
+       passwd user1
+       ```
+
+       根据提示信息完成修改密码操作。
+
+     - 建议系统管理员和普通用户都要定期修改自己的帐户密码，避免帐户密码被非法窃取。
+
+       以修改用户user1密码为例，以系统管理员用户连接数据库并执行如下命令：
+
+       ```sql
+       mogdb=# ALTER USER user1 IDENTIFIED BY "1234@abc" REPLACE "5678@def";
+       ALTER ROLE
+       ```
+
+       > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 1234@abc、5678@def分别代表用户user1的新密码和原始密码，这些密码要符合规则，否则会执行失败。
+
+     - 管理员可以修改自己的或者其他帐户的密码。通过修改其他帐户的密码，解决用户密码遗失所造成无法登录的问题。
+
+       以修改用户joe帐户密码为例，命令格式如下：
+
+       ```sql
+       mogdb=# ALTER USER joe IDENTIFIED BY "abc@1234";
+       ALTER ROLE
+       ```
+
+       > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+       >
+       > - 系统管理员之间不允许互相修改对方密码。
+       >
+       > - 系统管理员可以修改普通用户密码且不需要用户原密码。
+       > - 系统管理员修改自己密码但需要管理员原密码。
+
+   - 密码验证
+
+     设置当前会话的用户和角色时，需要验证密码。如果输入密码与用户的存储密码不一致，则会报错。
+
+     以设置用户joe为例，命令格式如下：
+
+     ```sql
+     mogdb=# SET ROLE joe PASSWORD "abc@1234";
+     ERROR:  Invalid username/password,set role denied.
+     ```
+
+     **表 4** 特殊字符<a id="表2.9.3.1"> </a>
+
+     | 编号 | 字符 | 编号 | 字符       | 编号 | 字符 | 编号 | 字符 |
+     | :--- | :--- | :--- | :--------- | :--- | :--- | :--- | :--- |
+     | 1    | ~    | 9    | *          | 17   | \|   | 25   | &lt; |
+     | 2    | ！   | 10   | (          | 18   | [    | 26   | .    |
+     | 3    | @    | 11   | )          | 19   | {    | 27   | &gt; |
+     | 4    | #    | 12   | -          | 20   | }    | 28   | /    |
+     | 5    | $    | 13   | _          | 21   | ]    | 29   | ？   |
+     | 6    | %    | 14   | =          | 22   | ；   | -    | -    |
+     | 7    | ^    | 15   | +          | 23   | :    | -    | -    |
+     | 8    | &    | 16   | &lt;/p&gt; | 24   | ，   | -    | -    |
+
+     **表 5** 不可重用天数和不可重用次数参数说明<a id="表2.9.3.2"> </a>
+
+     | 参数                                | 取值范围                                                     | 配置说明                                                     |
+     | :---------------------------------- | :----------------------------------------------------------- | :----------------------------------------------------------- |
+     | 不可重用天数（password_reuse_time） | 正数或0，其中整数部分表示天数，小数部分可以换算成时，分，秒。<br/>默认值为60。 | - 如果参数变小，则后续修改密码按新的参数进行检查。<br/>- 如果参数变大（比如由a变大为b），因为b天之前的历史密码可能已经删除，所以b天之前的密码仍有可能被重用。则后续修改密码按新的参数进行检查。<br/>说明:<br/>时间以绝对时间为准，历史密码记录的都是当时的时间，不识别时间的修改。 |
+     | 不可重用次数（password_reuse_max）  | 正整数或0。<br/>默认值为0，表示不检查重用次数。              | - 如果参数变小，则后续修改密码按新的参数进行检查。<br/>- 如果参数变大（比如由a变大为b），因为b次之前的历史密码可能已经删除，所以b次之前的密码仍有可能被重用。则后续修改密码按新的参数进行检查。 |
+
+6. 设置用户密码失效。
+
+   具有CREATEROLE权限的用户在创建用户时可以强制用户密码失效，新用户首次登陆数据库后需要修改密码才允许执行其他查询操作，命令格式如下：
+
+   ```sql
+   mogdb=# CREATE USER joe PASSWORD "abc@1234" EXPIRED;
+   CREATE ROLE
+   ```
+
+   具有CREATEROLE权限的用户可以强制用户密码失效或者强制修改密码且失效，命令格式如下：
+
+   ```sql
+   mogdb=# ALTER USER joe PASSWORD EXPIRED;
+   ALTER ROLE
+   mogdb=# ALTER USER joe PASSWORD "abc@2345" EXPIRED;
+   ALTER ROLE
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+   >
+   > - 密码失效的用户登录数据库后，当执行简单查询或者扩展查询时，会提示用户修改密码。修改密码后可以正常执行语句。
+   > - 只有初始用户、系统管理员（sysadmin）或拥有创建用户（CREATEROLE）权限的用户才可以设置用户密码失效，其中系统管理员也可以设置自己或其他系统管理员密码失效。不允许设置初始用户密码失效。
diff --git a/product/zh/docs-mogdb/v3.0/security-guide/security/3-configuring-database-audit.md b/product/zh/docs-mogdb/v3.0/security-guide/security/3-configuring-database-audit.md
new file mode 100644
index 0000000000000000000000000000000000000000..a67f27db06eb684409bceee46f4958e65d515894
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/security-guide/security/3-configuring-database-audit.md
@@ -0,0 +1,362 @@
+---
+title: 设置数据库审计
+summary: 设置数据库审计
+author: Guo Huan
+date: 2021-03-04
+---
+
+# 设置数据库审计
+
+<br/>
+
+## 审计概述
+
+**背景信息**
+
+数据库安全对数据库系统来说至关重要。MogDB将用户对数据库的所有操作写入审计日志。数据库安全管理员可以利用这些日志信息，重现导致数据库现状的一系列事件，找出非法操作的用户、时间和内容等。
+
+关于审计功能，用户需要了解以下几点内容:
+
+- 审计总开关audit_enabled支持动态加载。在数据库运行期间修改该配置项的值会立即生效，无需重启数据库。默认值为on，表示开启审计功能。
+- 除了审计总开关，各个审计项也有对应的开关。只有开关开启，对应的审计功能才能生效。
+- 各审计项的开关支持动态加载。在数据库运行期间修改审计开关的值，不需要重启数据库便可生效。
+
+目前，MogDB支持以下审计项如[表1](#表3.1.1)所示。
+
+**表 1** 配置审计项<a id="表3.1.1"> </a>
+
+| 配置项                                  | 描述                                                                                                                                          |
+| :-------------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------- |
+| 用户登录、注销审计                      | 参数: audit_login_logout<br/>默认值为7，表示开启用户登录、退出的审计功能。设置为0表示关闭用户登录、退出的审计功能。不推荐设置除0和7之外的值。 |
+| 数据库启动、停止、恢复和切换审计        | 参数: audit_database_process<br/>默认值为1，表示开启数据库启动、停止、恢复和切换的审计功能。                                                  |
+| 用户锁定和解锁审计                      | 参数: audit_user_locked<br/>默认值为1，表示开启审计用户锁定和解锁功能。                                                                       |
+| 用户访问越权审计                        | 参数: audit_user_violation<br/>默认值为0，表示关闭用户越权操作审计功能。                                                                      |
+| 授权和回收权限审计                      | 参数: audit_grant_revoke<br/>默认值为1，表示开启审计用户权限授予和回收功能。                                                                  |
+| 数据库对象的CREATE，ALTER，DROP操作审计 | 参数: audit_system_object<br/>默认值为12295，表示只对DATABASE、SCHEMA、USER、DATA SOURCE这四类数据库对象的CREATE、ALTER、DROP操作进行审计。   |
+| 具体表的INSERT、UPDATE和DELETE操作审计  | 参数: audit_dml_state<br/>默认值为0，表示关闭具体表的DML操作（SELECT除外）审计功能。                                                          |
+| SELECT操作审计                          | 参数: audit_dml_state_select<br/>默认值为0，表示关闭SELECT操作审计功能。                                                                      |
+| COPY审计                                | 参数: audit_copy_exec<br/>默认值为0，表示关闭copy操作审计功能。                                                                               |
+| 存储过程和自定义函数的执行审计          | 参数: audit_function_exec<br/>默认值为0，表示不记录存储过程和自定义函数的执行审计日志。                                                       |
+| SET审计                                 | 参数: audit_set_parameter<br/>默认值为1，表示记录set操作审计日志                                                                              |
+
+安全相关参数及默认值请参见[表2](#表3.1.2)。
+
+**表 2** 安全相关参数及默认值<a id="表3.1.2"> </a>
+
+| 参数名                      | 默认值     | 说明                                                         |
+| :-------------------------- | :--------- | :----------------------------------------------------------- |
+| ssl                         | on         | 指定是否启用SSL连接。                                        |
+| require_ssl                 | off        | 指定服务器端是否强制要求SSL连接。                            |
+| ssl_ciphers                 | ALL        | 指定SSL支持的加密算法列表。                                  |
+| ssl_cert_file               | server.crt | 指定包含SSL服务器证书的文件的名称。                          |
+| ssl_key_file                | server.key | 指定包含SSL私钥的文件名称。                                  |
+| ssl_ca_file                 | cacert.pem | 指定包含CA信息的文件的名称。                                 |
+| ssl_crl_file                | NULL       | 指定包含CRL信息的文件的名称。                                |
+| password_policy             | 1          | 指定是否进行密码复杂度检查。                                 |
+| password_reuse_time         | 60         | 指定是否对新密码进行可重用天数检查。                         |
+| password_reuse_max          | 0          | 指定是否对新密码进行可重用次数检查。                         |
+| password_lock_time          | 1          | 指定帐户被锁定后自动解锁的时间。                             |
+| failed_login_attempts       | 10         | 如果输入密码错误的次数达到此参数值时，当前帐户被锁定。       |
+| password_encryption_type    | 2          | 指定采用何种加密方式对用户密码进行加密存储。                 |
+| password_min_uppercase      | 0          | 密码中至少需要包含大写字母的个数。                           |
+| password_min_lowercase      | 0          | 密码中至少需要包含小写字母的个数。                           |
+| password_min_digital        | 0          | 密码中至少需要包含数字的个数。                               |
+| password_min_special        | 0          | 密码中至少需要包含特殊字符的个数。                           |
+| password_min_length         | 8          | 密码的最小长度。<br/>说明:<br/>在设置此参数时，请将其设置成不大于password_max_length，否则进行涉及密码的操作会一直出现密码长度错误的提示。 |
+| password_max_length         | 32         | 密码的最大长度。<br/>说明:<br/>在设置此参数时，请将其设置成不小于password_min_length，否则进行涉及密码的操作会一直出现密码长度错误的提示。 |
+| password_effect_time        | 90         | 密码的有效期限。                                             |
+| password_notify_time        | 7          | 密码到期提醒的天数。                                         |
+| audit_enabled               | on         | 控制审计进程的开启和关闭。                                   |
+| audit_directory             | pg_audit   | 审计文件的存储目录。                                         |
+| audit_data_format           | binary     | 审计日志文件的格式，当前仅支持二进制格式（binary）。         |
+| audit_rotation_interval     | 1d         | 指定创建一个新审计日志文件的时间间隔。当现在的时间减去上次创建一个审计日志的时间超过了此参数值时，服务器将生成一个新的审计日志文件。 |
+| audit_rotation_size         | 10MB       | 指定审计日志文件的最大容量。当审计日志消息的总量超过此参数值时，服务器将生成一个新的审计日志文件。 |
+| audit_resource_policy       | on         | 控制审计日志的保存策略，以空间还是时间限制为优先策略，on表示以空间为优先策略。 |
+| audit_file_remain_time      | 90         | 表示需记录审计日志的最短时间要求，该参数在audit_resource_policy为off时生效。 |
+| audit_space_limit           | 1GB        | 审计文件占用磁盘空间的最大值。                               |
+| audit_file_remain_threshold | 1048576    | 审计目录下审计文件的最大数量。                               |
+| audit_login_logout          | 7          | 指定是否审计数据库用户的登录（包括登录成功和登录失败）、注销。 |
+| audit_database_process      | 1          | 指定是否审计数据库启动、停止、切换和恢复的操作。             |
+| audit_user_locked           | 1          | 指定是否审计数据库用户的锁定和解锁。                         |
+| audit_user_violation        | 0          | 指定是否审计数据库用户的越权访问操作。                       |
+| audit_grant_revoke          | 1          | 指定是否审计数据库用户权限授予和回收的操作。                 |
+| audit_system_object         | 12295      | 指定是否审计数据库对象的CREATE、DROP、ALTER操作。            |
+| audit_dml_state             | 0          | 指定是否审计具体表的INSERT、UPDATE、DELETE操作。             |
+| audit_dml_state_select      | 0          | 指定是否审计SELECT操作。                                     |
+| audit_copy_exec             | 0          | 指定是否审计COPY操作。                                       |
+| audit_function_exec         | 0          | 指定在执行存储过程、匿名块或自定义函数（不包括系统自带函数）时是否记录审计信息。 |
+| audit_set_parameter         | 1          | 指定是否审计SET操作。                                        |
+| enableSeparationOfDuty      | off        | 指定是否开启三权分立。                                       |
+| session_timeout             | 10min      | 建立连接会话后，如果超过此参数的设置时间，则会自动断开连接。 |
+| auth_iteration_count        | 10000      | 认证加密信息生成过程中使用的迭代次数。                       |
+
+**操作步骤**
+
+1. 以操作系统用户omm登录数据库主节点。
+
+2. 使用如下命令连接数据库。
+
+    ```bash
+    gsql -d mogdb -p 8000
+    ```
+
+    mogdb为需要连接的数据库名称，8000为数据库主节点的端口号。
+
+3. 检查审计总开关状态。
+
+    a. 用show命令显示审计总开关audit_enabled的值。
+
+    ```sql
+    mogdb=# SHOW audit_enabled;
+    ```
+
+    如果显示为off，执行\\q命令退出数据库。
+
+    b. 执行如下命令开启审计功能，参数设置立即生效。
+
+    ```bash
+    gs_guc set -N all -I all -c "audit_enabled=on"
+    ```
+
+4. 配置具体的审计项。
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+    >
+    > - 只有开启审计功能，用户的操作才会被记录到审计文件中。
+    > - 各审计项的默认参数都符合安全标准，用户可以根据需要开启其他审计功能，但会对性能有一定影响。
+
+    以开启对数据库所有对象的增删改操作的审计开关为例，其他配置项的修改方法与此相同，修改配置项的方法如下所示:
+
+    ```bash
+    gs_guc reload -N all -I all -c "audit_system_object=12295"
+    ```
+
+    其中audit_system_object代表审计项开关，12295为该审计开关的值。
+
+<br/>
+
+## 查看审计结果
+
+**前提条件**
+
+- 审计功能总开关已开启。
+- 需要审计的审计项开关已开启。
+- 数据库正常运行，并且对数据库执行了一系列增、删、改、查操作，保证在查询时段内有审计结果产生。
+- 数据库各个节点审计日志单独记录。
+
+**背景信息**
+
+- 只有拥有AUDITADMIN属性的用户才可以查看审计记录。有关数据库用户及创建用户的办法请参见[用户](2-managing-users-and-their-permissions#用户)。
+
+- 审计查询命令是数据库提供的sql函数pg_query_audit，其原型为:
+
+    ```bash
+    pg_query_audit(timestamptz startime,timestamptz endtime,audit_log)
+    ```
+
+    参数startime和endtime分别表示审计记录的开始时间和结束时间，audit_log表示所查看的审计日志信息所在的物理文件路径，当不指定audit_log时，默认查看连接当前实例的审计日志信息。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+  > startime和endtime的差值代表要查询的时间段，其有效值为从startime日期中的00:00:00开始到endtime日期中的23:59:59之间的任何值。请正确指定这两个参数，否则将查不到需要的审计信息。
+
+**操作步骤**
+
+1. 以操作系统用户omm登录数据库主节点。
+
+2. 使用如下命令连接数据库。
+
+    ```bash
+    gsql -d mogdb -p 8000
+    ```
+
+    mogdb为需要连接的数据库名称，8000为数据库主节点的端口号。
+
+3. 查询审计记录。
+
+    ```sql
+    mogdb=# select * from pg_query_audit('2021-03-04 08:00:00','2021-03-04 17:00:00');
+    time          |      type      | result | userid | username  | database  |     client_conninfo     |    object_name    |  detail_info |     node_name     |            thread_id            | local_port | remote_port
+    ------------------------+----------------+--------+--------+-----------+-----------+-------------------------+-------------------+--------------+-------------------+---------------------------------+------------+-------------
+    2021-03-04 08:00:08+08 | login_success  | ok     | 10     | omm  | mogdb | gsql@::1 | mogdb    | login db(postgres) success,the current user is:omm | dn_6001_6002_6003 | 140477687527168@668131208211425 |   17778      | 46946
+    ```
+
+    该条记录表明，用户omm在time字段标识的时间点登录数据库mogdb。其中client_conninfo字段在log_hostname启动且IP连接时，字符@后显示反向DNS查找得到的主机名。
+
+<br/>
+
+## 维护审计日志
+
+**前提条件**
+
+用户必须拥有审计权限。
+
+**背景信息**
+
+- 与审计日志相关的配置参数及其含义请参见[表1](#表3.3.1)。
+
+    **表 1** 审计日志相关配置参数<a id="表3.3.1"> </a>
+
+    | 配置项                      | 含义                           | 默认值                         |
+    | :-------------------------- | :----------------------------- | :----------------------------- |
+    | audit_directory             | 审计文件的存储目录。           | /var/log/mogdb/用户名/pg_audit |
+    | audit_resource_policy       | 审计日志的保存策略。           | on（表示使用空间配置策略）     |
+    | audit_space_limit           | 审计文件占用的磁盘空间总量。   | 1GB                            |
+    | audit_file_remain_time      | 审计日志文件的最小保存时间。   | 90                             |
+    | audit_file_remain_threshold | 审计目录下审计文件的最大数量。 | 1048576                        |
+
+    > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+    >
+    > 如果使用gs_om工具部署MogDB，则审计日志路径为 "/var/log/mogdb/用户名/pg_audit"。
+
+- 审计日志删除命令为数据库提供的sql函数pg_delete_audit，其原型为:
+
+    ```bash
+    pg_delete_audit(timestamp startime,timestamp endtime)
+    ```
+
+    其中参数startime和endtime分别表示审计记录的开始时间和结束时间。
+
+- 目前常用的记录审计内容的方式有两种: 记录到数据库的表中、记录到OS文件中。这两种方式的优缺点比较如[表2](#表3.3.2)所示。
+
+    **表 2** 审计日志保存方式比较<a id="表3.3.2"> </a>
+
+    | 方式           | 优点                                                                   | 缺点                                                                                                                                 |
+    | :------------- | :--------------------------------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------------- |
+    | 记录到表中     | 不需要用户维护审计日志。                                               | 由于表是数据库的对象，如果一个数据库用户具有一定的权限，就能够访问到审计表。如果该用户非法操作审计表，审计记录的准确性难以得到保证。 |
+    | 记录到OS文件中 | 比较安全，即使一个帐户可以访问数据库，但不一定有访问OS这个文件的权限。 | 需要用户维护审计日志。                                                                                                               |
+
+    从数据库安全角度出发，MogDB采用记录到OS文件的方式来保存审计结果，保证了审计结果的可靠性。
+
+**操作步骤**
+
+1. 以操作系统用户omm登录数据库主节点。
+
+2. 使用如下命令连接数据库。
+
+    ```bash
+    gsql -d mogdb -p 8000
+    ```
+
+    mogdb为需要连接的数据库名称，8000为数据库主节点的端口号。
+
+3. 选择日志维护方式进行维护。
+
+    + 设置自动删除审计日志
+
+        审计文件占用的磁盘空间或者审计文件的个数超过指定的最大值时，系统将删除最早的审计文件，并记录审计文件删除信息到审计日志中。
+
+        > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明:**
+        > 审计文件占用的磁盘空间大小默认值为1024MB，用户可以根据磁盘空间大小重新设置参数。
+
+        配置审计文件占用磁盘空间的大小（audit_space_limit）
+
+        a. 查看已配置的参数。
+
+        ```sql
+        mogdb=# SHOW audit_space_limit;
+        audit_space_limit
+        -------------------
+        1GB
+        (1 row)
+        ```
+
+        如果显示结果不为1GB（1024MB），执行\\q命令退出数据库。
+
+        b. 建议执行如下命令设置成默认值1024MB。
+
+        ```bash
+        gs_guc reload -N all -I all -c "audit_space_limit=1024MB"
+        ```
+
+        配置审计文件个数的最大值（audit_file_remain_threshold）
+
+        a. 查看已配置的参数。
+
+        ```sql
+        mogdb=# SHOW audit_file_remain_threshold;
+        audit_file_remain_threshold
+        -----------------------------
+        1048576
+        (1 row)
+        ```
+
+        如果显示结果不为1048576，执行\\q命令退出数据库。
+
+        b. 建议执行如下命令设置成默认值1048576。
+
+        ```bash
+        gs_guc reload -N all -I all -c "audit_file_remain_threshold=1048576"
+        ```
+
+    + 手动备份审计文件
+
+        当审计文件占用的磁盘空间或者审计文件的个数超过配置文件指定的值时，系统将会自动删除较早的审计文件，因此建议用户周期性地对比较重要的审计日志进行保存。
+
+        a. 使用show命令获得审计文件所在目录（audit_directory）。
+
+        ```sql
+        mogdb=# SHOW audit_directory;
+        ```
+
+        b. 将审计目录整个拷贝出来进行保存。
+
+    + 手动删除审计日志
+
+        当不再需要某时段的审计记录时，可以使用审计接口命令pg_delete_audit进行手动删除。
+
+        以删除2012/9/20到2012/9/21之间的审计记录为例:
+
+        ```sql
+        SELECT pg_delete_audit('2012-09-20 00:00:00','2012-09-21 23:59:59');
+        ```
+
+<br/>
+
+## 设置文件权限安全策略
+
+**背景信息**
+
+数据库在安装过程中，会自动对其文件权限（包括运行过程中生成的文件，如日志文件等）进行设置。其权限规则如下:
+
+- 数据库程序目录的权限为0750。
+
+- 数据库数据文件目录的权限为0700。
+
+    MogDB部署时通过创建xml配置文件中的tmpMppdbPath参数指定目录（若未指定，则默认创建/tmp/$USER_mppdb目录）来存放".s.PGSQL.*"文件，该目录和文件权限设置为0700。
+
+- 数据库的数据文件、审计日志和其他数据库程序生成的数据文件的权限为0600，运行日志的权限默认不高于0640。
+
+- 普通操作系统用户不允许修改和删除数据库文件和日志文件。
+
+**数据库程序目录及文件权限**
+
+数据库安装后，部分程序目录及文件权限如[表1](#表3.4.1)所示。
+
+**表 1** 文件及目录权限<a id="表3.4.1"> </a>
+
+| 文件/目录                       | 父目录                 | 权限 |
+| :------------------------------ | :--------------------- | :--- |
+| bin                             | -                      | 0700 |
+| lib                             | -                      | 0700 |
+| share                           | -                      | 0700 |
+| data（数据库节点/数据库主节点） | -                      | 0700 |
+| base                            | 实例数据目录           | 0700 |
+| global                          | 实例数据目录           | 0700 |
+| pg_audit                        | 实例数据目录（可配置） | 0700 |
+| pg_log                          | 实例数据目录（可配置） | 0700 |
+| pg_xlog                         | 实例数据目录           | 0700 |
+| postgresql.conf                 | 实例数据目录           | 0600 |
+| pg_hba.conf                     | 实例数据目录           | 0600 |
+| postmaster.opts                 | 实例数据目录           | 0600 |
+| pg_ident.conf                   | 实例数据目录           | 0600 |
+| gs_initdb                       | bin                    | 0700 |
+| gs_dump                         | bin                    | 0700 |
+| gs_ctl                          | bin                    | 0700 |
+| gs_guc                          | bin                    | 0700 |
+| gsql                            | bin                    | 0700 |
+| archive_status                  | pg_xlog                | 0700 |
+| libpq.so.5.5                    | lib                    | 0600 |
+
+**建议**
+
+数据库在安装过程中，会自动对其文件权限（包括运行过程中生成的文件，如日志文件等）进行设置，适合大多数情况下的权限要求。如果用户产品对相关权限有特殊要求，建议用户安装后定期检查相关权限设置，确保完全符合产品要求。
diff --git a/product/zh/docs-mogdb/v3.0/security-guide/security/4-setting-encrypted-equality-query.md b/product/zh/docs-mogdb/v3.0/security-guide/security/4-setting-encrypted-equality-query.md
new file mode 100644
index 0000000000000000000000000000000000000000..730bfbb2bb533130c259cb2d41861ca0a08f866b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/security-guide/security/4-setting-encrypted-equality-query.md
@@ -0,0 +1,327 @@
+---
+title: 设置密态等值查询
+summary: 设置密态等值查询
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# 设置密态等值查询
+
+## 密态等值查询概述
+
+随着企业数据上云，数据的安全隐私保护面临越来越严重的挑战。密态数据库将解决数据整个生命周期中的隐私保护问题，涵盖网络传输、数据存储以及数据运行态；更进一步，密态数据库可以实现云化场景下的数据隐私权限分离，即实现数据拥有者和实际数据管理者的数据读取能力分离。密态等值查询将优先解决密文数据的等值类查询问题。密态等值查询目前支持客户端工具gsql和JDBC。接下来分别介绍如何使用客户端工具执行密态等值查询的相关操作。
+
+## 使用gsql操作密态数据库
+
+**操作步骤**
+
+1. 以操作系统用户omm登录CN所在主机。
+
+2. 使用gsql连接数据库服务器时，需使用“-C”参数或“--enable-client-encryption”，打开全密态数据库的开关。执行以下命令打开密态开关，连接密态数据库。
+
+   ```bash
+   gsql -p PORT postgres -r -C
+   ```
+
+3. 创建客户端主密钥CMK和列加密密钥CEK。创建CMK的语法请参考[CREATE CLIENT MASTER KEY](42-CREATE-CLIENT-MASTER-KEY)、创建的CEK的语法请参考[CREATE COLUMN ENCRYPTION KEY](43-CREATE-COLUMN-ENCRYPTION-KEY)。
+
+   ```sql
+   --创建客户端加密主密钥(CMK)
+   mogdb=# CREATE CLIENT MASTER KEY ImgCMK1 WITH (KEY_STORE = localkms, KEY_PATH = "key_path_value1", ALGORITHM = RSA_2048);
+   mogdb=# CREATE CLIENT MASTER KEY ImgCMK WITH (KEY_STORE = localkms, KEY_PATH = "key_path_value2", ALGORITHM = RSA_2048);
+   mogdb=# CREATE COLUMN ENCRYPTION KEY ImgCEK1 WITH VALUES (CLIENT_MASTER_KEY = ImgCMK1, ALGORITHM  = AEAD_AES_256_CBC_HMAC_SHA256);
+   CREATE COLUMN ENCRYPTION KEY
+   mogdb=# CREATE COLUMN ENCRYPTION KEY ImgCEK WITH VALUES (CLIENT_MASTER_KEY = ImgCMK, ALGORITHM  = AEAD_AES_256_CBC_HMAC_SHA256);
+   CREATE COLUMN ENCRYPTION KEY
+   ```
+
+   查询存储密钥信息的系统表结果如下。
+
+   ```sql
+   mogdb=# SELECT * FROM gs_client_global_keys;
+    global_key_name | key_namespace | key_owner | key_acl |        create_date
+   -----------------+---------------+-----------+---------+----------------------------
+    imgcmk1         |          2200 |        10 |         | 2021-04-21 11:04:00.656617
+    imgcmk          |          2200 |        10 |         | 2021-04-21 11:04:05.389746
+   (2 rows)
+   mogdb=# SELECT column_key_name,column_key_distributed_id ,global_key_id,key_owner  FROM gs_column_keys;
+    column_key_name | column_key_distributed_id | global_key_id | key_owner
+   -----------------+---------------------------+---------------+-----------
+    imgcek1         |                 760411027 |         16392 |        10
+    imgcek          |                3618369306 |         16398 |        10
+   (2 rows)
+   ```
+
+4. 创建加密表。
+
+   ```sql
+   mogdb=# CREATE TABLE creditcard_info (id_number    int, name         text encrypted with (column_encryption_key = ImgCEK, encryption_type = DETERMINISTIC),
+   credit_card  varchar(19) encrypted with (column_encryption_key = ImgCEK1, encryption_type = DETERMINISTIC));
+   NOTICE:  The 'DISTRIBUTE BY' clause is not specified. Using 'id_number' as the distribution column by default.
+   HINT:  Please use 'DISTRIBUTE BY' clause to specify suitable data distribution column.
+   CREATE TABLE
+   ```
+
+   查询表的详细信息如下，Modifiers值为encrypted则表示该列是加密列。
+
+   ```sql
+   mogdb=# \d creditcard_info
+           Table "public.creditcard_info"
+      Column    |       Type        | Modifiers
+   -------------+-------------------+------------
+    id_number   | integer           |
+    name        | text              |  encrypted
+    credit_card | character varying |  encrypted
+   ```
+
+5. 向加密表插入数据并进行等值查询。
+
+   ```sql
+   mogdb=# INSERT INTO creditcard_info VALUES (1,'joe','6217986500001288393');
+   INSERT 0 1
+   mogdb=# INSERT INTO creditcard_info VALUES (2, 'joy','6219985678349800033');
+   INSERT 0 1
+   mogdb=# select * from creditcard_info where name = 'joe';
+    id_number | name |     credit_card
+   -----------+------+---------------------
+            1 | joe  | 6217986500001288393
+   (1 row)
+   -- 注意：使用非密态客户端查看该加密表数据时是密文
+   mogdb=# select id_number,name from creditcard_info;
+   id_number  |                       name
+   -----------+--------------------------------------
+            1 | \x011aefabd754ded0a536a96664790622487c4d366d313aecd5839e410a46d29cba96a60e4831000000ee79056a114c9a6c041bb552b78052e912a8b730609142074c63791abebd0d38
+            2 | \x011aefabd76853108eb406c0f90e7c773b71648fa6e2b8028cf634b49aec65b4fcfb376f3531000000f7471c8686682de215d09aa87113f6fb03884be2031ef4dd967afc6f7901646b
+   (2 rows)
+   ```
+
+6. （可选）对加密表进行alter和update操作。
+
+   ```sql
+   mogdb=# ALTER TABLE creditcard_info ADD COLUMN age int ENCRYPTED WITH (COLUMN_ENCRYPTION_KEY = ImgCEK, ENCRYPTION_TYPE = DETERMINISTIC);
+   ALTER TABLE
+   mogdb=# \d creditcard_info
+           Table "public.creditcard_info"
+      Column    |       Type        | Modifiers
+   -------------+-------------------+------------
+    id_number   | integer           |
+    name        | text              |  encrypted
+    credit_card | character varying |  encrypted
+    age         | integer           |  encrypted
+   mogdb=# ALTER TABLE creditcard_info DROP COLUMN age;
+   ALTER TABLE
+   mogdb=# update creditcard_info set credit_card = '80000000011111111' where name = 'joy';
+   UPDATE 1
+   mogdb=# select * from creditcard_info  where name = 'joy';
+    id_number | name |    credit_card
+   -----------+------+-------------------
+            2 | joy  | 80000000011111111
+   (1 row)
+   ```
+
+## 使用JDBC操作密态数据库
+
+### 连接密态数据库
+
+具体JDBC连接参数参考[基于JDBC开发](1-development-based-on-jdbc-overview)章节介绍。JDBC支持密态数据库相关操作，需要设置enable_ce=1，示例如下。
+
+```java
+public static Connection getConnect(String username, String passwd)
+    {
+        //驱动类。
+        String driver = "org.postgresql.Driver";
+        //数据库连接描述符。
+        String sourceURL = "jdbc:postgresql://10.10.0.13:8000/postgres?enable_ce=1";
+        Connection conn = null;
+
+        try
+        {
+            //加载驱动。
+            Class.forName(driver);
+        }
+        catch( Exception e )
+        {
+            e.printStackTrace();
+            return null;
+        }
+
+        try
+        {
+             //创建连接。
+            conn = DriverManager.getConnection(sourceURL, username, passwd);
+            System.out.println("Connection succeed!");
+        }
+        catch(Exception e)
+        {
+            e.printStackTrace();
+            return null;
+        }
+
+        return conn;
+    };
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 【建议】使用JDBC操作密态数据库时，一个数据库连接对象对应一个线程，否则，不同线程变更可能导致冲突。
+> - 【建议】使用JDBC操作密态数据库时，不同connection对密态配置数据有变更，由客户端调用isvalid方法保证connection能够持有变更后的密态配置数据，此时需要保证参数refreshClientEncryption为1(默认值为1)，在单客户端操作密态数据场景下，refreshClientEncryption参数可以设置为0。
+
+### 调用isValid方法刷新缓存示例
+
+```java
+// 创建客户端主密钥
+Connection conn1 = DriverManager.getConnection("url","user","password");
+
+// conn1通过调用isValid刷新缓存
+try {
+ if (!conn1.getConnection().isValid(60)) {
+  conn1.getFileWriter().writeLine("isValid Failed for connection 1");
+ }
+} catch (SQLException e) {
+ conn1.getFileWriter().writeLine("isValid Failed with error");
+ e.printStackTrace();
+}
+```
+
+### 执行密态等值查询相关的创建密钥语句
+
+```java
+// 创建客户端主密钥
+Connection conn = DriverManager.getConnection("url","user","password");
+Statement stmt = conn.createStatement();
+int rc = stmt.executeUpdate("CREATE CLIENT MASTER KEY ImgCMK1 WITH ( KEY_STORE = gs_ktool, KEY_PATH = \"gs_ktool/1\", ALGORITHM = AES_256_CBC;");
+int rc = stmt.executeUpdate("CREATE CLIENT MASTER KEY ImgCMK1 WITH ( KEY_STORE = localkms, KEY_PATH = \"key_path_value\" , ALGORITHM = RSA_2048);
+```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 创建密钥之前需要使用gs_ktool工具提前生成密钥，才能创建CMK成功。
+
+```java
+// 创建列加密密钥
+int rc2 = stmt.executeUpdate("CREATE COLUMN ENCRYPTION KEY ImgCEK1 WITH VALUES (CLIENT_MASTER_KEY = ImgCMK1, ALGORITHM  = AEAD_AES_256_CBC_HMAC_SHA256);");
+```
+
+### 执行密态等值查询相关的创建加密表的语句
+
+```java
+int rc3 = stmt.executeUpdate("CREATE TABLE creditcard_info (id_number    int, name  varchar(50) encrypted with (column_encryption_key = ImgCEK1, encryption_type = DETERMINISTIC),credit_card  varchar(19) encrypted with (column_encryption_key = ImgCEK1, encryption_type = DETERMINISTIC));");
+// 插入数据
+int rc4 = stmt.executeUpdate("INSERT INTO creditcard_info VALUES (1,'joe','6217986500001288393');");
+// 查询加密表
+ResultSet rs = null;
+rs = stmt.executeQuery("select * from creditcard_info where name = 'joe';");
+// 关闭语句对象
+stmt.close();
+```
+
+### 执行加密表的预编译SQL语句
+
+```java
+// 调用Connection的prepareStatement方法创建预编译语句对象。
+PreparedStatement pstmt = con.prepareStatement("INSERT INTO creditcard_info VALUES (?, ?, ?);");
+// 调用PreparedStatement的setShort设置参数。
+pstmt.setInt(1, 2);
+pstmt.setString(2, "joy");
+pstmt.setString(3, "6219985678349800033");
+// 调用PreparedStatement的executeUpdate方法执行预编译SQL语句。
+int rowcount = pstmt.executeUpdate();
+// 调用PreparedStatement的close方法关闭预编译语句对象。
+pstmt.close();
+```
+
+### 执行加密表的批处理操作
+
+```java
+// 调用Connection的prepareStatement方法创建预编译语句对象。
+Connection conn = DriverManager.getConnection("url","user","password");
+PreparedStatement pstmt = conn.prepareStatement("INSERT INTO batch_table (id, name, address) VALUES (?,?,?)");
+// 针对每条数据都要调用setShort设置参数，以及调用addBatch确认该条设置完毕。
+int loopCount = 20;
+ for (int i = 1; i < loopCount + 1; ++i) {
+      statemnet.setInt(1, i);
+      statemnet.setString(2, "Name " + i);
+      statemnet.setString(3, "Address " + i);
+      // Add row to the batch.
+      statemnet.addBatch();
+}
+// 调用PreparedStatement的executeBatch方法执行批处理。
+int[] rowcount = pstmt.executeBatch();
+// 调用PreparedStatement的close方法关闭预编译语句对象。
+pstmt.close();
+```
+
+## 密态支持函数/存储过程
+
+密态支持函数/存储过程当前版本只支持sql和PL/pgsql两种语言。由于密态支持存储过程中创建和执行函数/存储过程对用户是无感知的，因此语法和非密态无区别。
+
+密态等值查询支持函数存储过程新增系统表gs_encrypted_proc，用于存储参数返回的原始数据类型。
+
+### 创建并执行涉及加密列的函数/存储过程
+
+1. 创建密钥，详细步骤请参考[使用gsql操作密态数据库](#使用gsql操作密态数据库)和[使用JDBC操作密态数据库](#使用JDBC操作密态数据库)。
+
+2. 创建加密表。
+
+   ```sql
+   mogdb=# CREATE TABLE creditcard_info (
+   mogdb(#   id_number int,
+   mogdb(#   name  text,
+   mogdb(#   credit_card varchar(19) encrypted with (column_encryption_key = ImgCEK1, encryption_type = DETERMINISTIC)
+   mogdb(# ) with (orientation=row) distribute by hash(id_number);
+   CREATE TABLE
+   ```
+
+3. 插入数据。
+
+   ```sql
+   mogdb=# insert into creditcard_info values(1, 'Avi', '1234567890123456');
+   INSERT 0 1
+   mogdb=# insert into creditcard_info values(2, 'Eli', '2345678901234567');
+   INSERT 0 1
+   ```
+
+4. 创建函数支持密态等值查询。
+
+   ```sql
+   mogdb=# CREATE FUNCTION f_encrypt_in_sql(val1 text, val2 varchar(19)) RETURNS text AS 'SELECT name from creditcard_info where name=$1 or credit_card=$2 LIMIT 1' LANGUAGE SQL;
+   CREATE FUNCTION
+   mogdb=# CREATE FUNCTION f_encrypt_in_plpgsql (val1 text, val2 varchar(19))
+   mogdb-# RETURNS text AS $$
+   mogdb$# DECLARE
+   mogdb$# c text;
+   mogdb$# BEGIN
+   mogdb$#     SELECT into c name from creditcard_info where name=$1 or credit_card =$2 LIMIT 1;
+   mogdb$#     RETURN c;
+   mogdb$# END; $$
+   mogdb-# LANGUAGE plpgsql;
+   CREATE FUNCTION
+   ```
+
+5. 执行函数。
+
+   ```sql
+   mogdb=# SELECT f_encrypt_in_sql('Avi','1234567890123456');
+    f_encrypt_in_sql
+   ------------------
+    Avi
+   (1 row)
+   
+   mogdb=# SELECT f_encrypt_in_plpgsql('Avi', val2=>'1234567890123456');
+    f_encrypt_in_plpgsql
+   ----------------------
+    Avi
+   (1 row)
+   ```
+
+> ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+>
+> - 函数/存储过程中的“执行动态查询语句”中的查询是在执行过程中编译，因此函数/存储过程中的表名、列名不能在创建阶段未知，输入参数不能用于表名、列名或以任何方式连接。
+> - 在RETURNS、IN和OUT的参数中，不支持混合使用加密和非加密类型参数。虽然参数类型都是原始数据类型，但实际类型不同。
+> - 对高级包接口中，如dbe_output.print_line()等在服务端打印输出的接口不会做解密操作，加密数据类型在强转成明文原始数据类型时会打印出该数据类型的默认值。
+> - 当前版本函数/存储过程的LANGUAGE只支持SQL和PL/pgSQL，不支持C和JAVA等其他过程语言。
+> - 不支持在函数/存储过程中执行其他查询加密列的函数/存储过程。
+> - 当前版本不支持default、DECLARE中为变量赋予默认值，且不支持对DECLARE中的返回值进行解密，用户可以用执行函数时用输入参数，输出参数来代替使用。
+> - 不支持gs_dump对涉及加密列的function进行备份。
+> - 不支持在函数/存储过程中创建密钥。
+> - 该版本密态函数/存储过程不支持触发器。
+> - 密态等值查询函数/存储过程不支持对plpgsql语言对语法进行转义，对于语法主体带有引号的语法CREATE FUNCTION AS ‘语法主体'， 可以用CREATE FUNCTION AS '语法主体' 代替。
+> - 不支持在密态等值查询函数/存储过程中执行修改加密列定义的操作，包括对创建加密表，添加加密列，由于执行函数是在服务端，客户端没法判断是否是需要刷新缓存，得断开连接后或触发刷新客户端加密列缓存才可以对该列做加密操作。
diff --git a/product/zh/docs-mogdb/v3.0/security-guide/security/5-setting-a-ledger-database.md b/product/zh/docs-mogdb/v3.0/security-guide/security/5-setting-a-ledger-database.md
new file mode 100644
index 0000000000000000000000000000000000000000..95e504e2c161f16fec9c631bd5c97f4268457f01
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/security-guide/security/5-setting-a-ledger-database.md
@@ -0,0 +1,416 @@
+---
+title: 设置账本数据库
+summary: 设置账本数据库
+author: Zhang Cuiping
+date: 2021-10-11
+---
+
+# 设置账本数据库
+
+## 账本数据库概述
+
+### 背景信息
+
+<br/>
+
+账本数据库融合了区块链思想，将用户操作记录至两种历史表中：
+
+- 用户历史表
+- 全局区块表
+
+当用户创建防篡改用户表时，系统将自动为该表添加一个hash列来保存每行数据的hash摘要信息，同时在blockchain模式下会创建一张用户历史表来记录对应用户表中每条数据的变更行为；而用户对防篡改用户表的一次修改行为将记录至全局区块表中。由于历史表具有只可追加不可修改的特点，因此历史表记录串联起来便形成了用户对防篡改用户表的修改历史。
+
+用户历史表命名和结构如下：
+
+**表 1** 用户历史表blockchain.__hist所包含的字段 <a id="table1"></a>
+
+| 字段名   | 类型   | 描述                                     |
+| :------- | :----- | :--------------------------------------- |
+| rec_num  | bigint | 行级修改操作在历史表中的执行序号。       |
+| hash_ins | hash16 | INSERT或UPDATE操作插入的数据行的hash值。 |
+| hash_del | hash16 | DELETE或UPDATE操作删除的数据行的hash值。 |
+| pre_hash | hash32 | 当前用户历史表的数据整体摘要。           |
+
+**表 2** hash_ins与hash_del场景对应关系
+
+| -      | hash_ins               | hash_del                 |
+| ------ | ---------------------- | ------------------------ |
+| INSERT | (√) 插入行的hash值     | 空                       |
+| DELETE | 空                     | (√) 删除行的hash值。     |
+| UPDATE | (√) 新插入数据的hash值 | (√) 删除前该行的hash值。 |
+
+### 操作步骤
+
+1. 创建防篡改模式。
+
+   例如，创建防篡改模式ledgernsp。
+
+   ```sql
+   mogdb=# CREATE SCHEMA ledgernsp WITH BLOCKCHAIN;
+   ```
+
+2. 在防篡改模式下创建防篡改用户表。
+
+   例如，创建防篡改用户表ledgernsp.usertable。
+
+   ```sql
+   mogdb=# CREATE TABLE ledgernsp.usertable(id int, name text);
+   ```
+
+    查看防篡改用户表结构及其对应的用户历史表结构。
+
+   ```sql
+   mogdb=# \d+ ledgernsp.usertable;
+   mogdb=# \d+ blockchain.ledgernsp_usertable_hist;
+   ```
+
+    执行结果如下：
+
+   ```sql
+   mogdb=# \d+ ledgernsp.usertable;
+                        Table "ledgernsp.usertable"
+    Column |  Type   | Modifiers | Storage  | Stats target | Description
+   --------+---------+-----------+----------+--------------+-------------
+    id     | integer |           | plain    |              |
+    name   | text    |           | extended |              |
+    hash   | hash16  |           | plain    |              |
+   Has OIDs: no
+   Distribute By: HASH(id)
+   Location Nodes: ALL DATANODES
+   Options: orientation=row, compression=no
+   History table name: ledgernsp_usertable_hist
+
+   mogdb=# \d+ blockchain.ledgernsp_usertable_hist;
+                Table "blockchain.ledgernsp_usertable_hist"
+     Column  |  Type  | Modifiers | Storage | Stats target | Description
+   ----------+--------+-----------+---------+--------------+-------------
+    rec_num  | bigint |           | plain   |              |
+    hash_ins | hash16 |           | plain   |              |
+    hash_del | hash16 |           | plain   |              |
+    pre_hash | hash32 |           | plain   |              |
+   Indexes:
+       "gs_hist_16388_index" PRIMARY KEY, btree (rec_num int4_ops) TABLESPACE pg_default
+   Has OIDs: no
+   Distribute By: HASH(rec_num)
+   Location Nodes: ALL DATANODES
+   Options: internal_mask=263
+   ```
+
+   > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：**
+   >
+   > - 防篡改表不支持非行存表、临时表、外表、unlog表、非行存表均无防篡改属性。
+   > - 防篡改表在创建时会自动增加一个名为hash的系统列，所以防篡改表单表最大列数为1599。
+
+3. 修改防篡改用户表数据。
+
+   例如，对防篡改用户表执行INSERT/UPDATE/DELETE。
+
+   ```sql
+   mogdb=# INSERT INTO ledgernsp.usertable VALUES(1, 'alex'), (2, 'bob'), (3, 'peter');
+   INSERT 0 3
+   mogdb=# SELECT *, hash FROM ledgernsp.usertable ORDER BY id;
+    id | name  |       hash
+   ----+-------+------------------
+     1 | alex  | 1f2e543c580cb8c5
+     2 | bob   | 8fcd74a8a6a4b484
+     3 | peter | f51b4b1b12d0354b
+   (3 rows)
+
+   mogdb=# UPDATE ledgernsp.usertable SET name = 'bob2' WHERE id = 2;
+   UPDATE 1
+   mogdb=# SELECT *, hash FROM ledgernsp.usertable ORDER BY id;
+    id | name  |       hash
+   ----+-------+------------------
+     1 | alex  | 1f2e543c580cb8c5
+     2 | bob2  | 437761affbb7c605
+     3 | peter | f51b4b1b12d0354b
+   (3 rows)
+
+   mogdb=# SELECT *, hash FROM ledgernsp.usertable ORDER BY id;
+    id | name  |       hash
+   ----+-------+------------------
+     1 | alex  | 1f2e543c580cb8c5
+     2 | bob2  | 437761affbb7c605
+     3 | peter | f51b4b1b12d0354b
+   (3 rows)
+
+   mogdb=# DELETE FROM ledgernsp.usertable WHERE id = 3;
+   DELETE 1
+   mogdb=# SELECT *, hash FROM ledgernsp.usertable ORDER BY id;
+    id | name |       hash
+   ----+------+------------------
+     1 | alex | 1f2e543c580cb8c5
+     2 | bob2 | 437761affbb7c605
+   (2 rows)
+   ```
+
+## 查看账本历史操作记录
+
+### 前提条件
+
+- 系统中需要有审计管理员或者具有审计管理员权限的角色。
+- 数据库正常运行，并且对防篡改数据库执行了一系列增、删、改等操作，保证在查询时段内有账本操作记录结果产生。
+
+### 背景信息
+
+- 只有拥有AUDITADMIN属性的用户才可以查看账本历史操作记录。有关数据库用户及创建用户的办法请参见[管理用户及权限](2-managing-users-and-their-permissions)。
+
+- 查询全局区块表命令是直接查询gs_global_chain表，操作为：
+
+  ```sql
+  SELECT * FROM gs_global_chain;
+  ```
+
+  该表有11个字段，每个字段的含义见章节[GS_GLOBAL_CHAIN](GS_GLOBAL_CHAIN)。
+
+- 查询用户历史表的命令是直接查询BLOCKCHAIN模式下的用户历史表，操作为：
+
+  例如用户表所在的模式为ledgernsp，表名为usertable，则对应的用户历史表名为blockchain.ledgernsp_usertable_hist；
+
+  ```sql
+  SELECT * FROM blockchain.ledgernsp_usertable_hist;
+  ```
+
+  用户历史表有4个字段，每个字段的含义见[表1](#table1)。
+
+  > ![img](https://cdn-mogdb.enmotech.com/docs-media/icon/icon-note.gif) **说明：** 用户历史表的表名一般为blockchain.hist形式。当防篡改用户表模式名或者表名过长导致前述方式生成的表名超出表名长度限制，则会采用blockchain.hist的方式命名。
+
+### 操作步骤
+
+1. 以操作系统用户omm登录数据库主节点。
+
+2. 使用如下命令连接数据库。
+
+   ```bash
+   gsql -d postgres -p 8000
+   ```
+
+   postgres为需要连接的数据库名称，8000为端口号。
+
+3. 查询全局区块表记录。
+
+   ```sql
+   mogdb=# SELECT * FROM gs_global_chain;
+
+    blocknum |  dbname  | username |           starttime           | relid |  relnsp   |  relname  |     relhash      |            globalhash            |
+                  txcommand
+   ----------+----------+----------+-------------------------------+-------+-----------+-----------+------------------+----------------------------------+------------------
+   ------------------------------------------------------------
+          0 | postgres | omm      | 2021-04-14 07:00:46.32757+08  | 16393 | ledgernsp | usertable | a41714001181a294 | 6b5624e039e8aee36bff3e8295c75b40 | insert into ledge
+   rnsp.usertable values(1, 'alex'), (2, 'bob'), (3, 'peter');
+          1 | postgres | omm      | 2021-04-14 07:01:19.767799+08 | 16393 | ledgernsp | usertable | b3a9ed0755131181 | 328b48c4370faed930937869783c23e0 | update ledgernsp.
+   usertable set name = 'bob2' where id = 2;
+          2 | postgres | omm      | 2021-04-14 07:01:29.896148+08 | 16393 | ledgernsp | usertable | 0ae4b4e4ed2fcab5 | aa8f0a236357cac4e5bc1648a739f2ef | delete from ledge
+   rnsp.usertable where id = 3;
+   ```
+
+   该结果表明，用户omm连续执行了三条DML命令，包括INSERT、UPDATE和DELETE操作。
+
+4. 查询历史表记录。
+
+   ```sql
+   mogdb=# SELECT * FROM blockchain.ledgernsp_usertable_hist;
+    rec_num |     hash_ins     |     hash_del     |             pre_hash
+   ---------+------------------+------------------+----------------------------------
+         0 | 1f2e543c580cb8c5 |                  | e1b664970d925d09caa295abd38d9b35
+         1 | 8fcd74a8a6a4b484 |                  | dad3ed8939a141bf3682043891776b67
+         2 | f51b4b1b12d0354b |                  | 53eb887fc7c4302402343c8914e43c69
+         3 | 437761affbb7c605 | 8fcd74a8a6a4b484 | c2868c5b49550801d0dbbbaa77a83a10
+         4 |                  | f51b4b1b12d0354b | 9c512619f6ffef38c098477933499fe3
+   (5 rows)
+   ```
+
+   查询结果显示，用户omm对ledgernsp.usertable表插入了3条数据，更新了1条数据，随后删除了1行数据，最后剩余2行数据，hash值分别为1f2e543c580cb8c5和437761affbb7c605。
+
+5. 查询用户表数据及hash校验列。
+
+   ```sql
+   mogdb=# SELECT *, hash FROM ledgernsp.usertable;
+
+    id | name |       hash
+   ----+------+------------------
+    1 | alex | 1f2e543c580cb8c5
+    2 | bob2 | 437761affbb7c605
+   (2 rows)
+   ```
+
+   查询结果显示，用户表中剩余2条数据，与步骤4中的记录一致。
+
+## 校验账本数据一致性
+
+### 前提条件
+
+数据库正常运行，并且对防篡改数据库执行了一系列增、删、改等操作，保证在查询时段内有账本操作记录结果产生。
+
+### 背景信息
+
+- 账本数据库校验功能目前提供两种校验接口，分别为：[ledger_hist_check(text, text)](20.1-ledger-database-functions)和[ledger_gchain_check(text, text)](20.1-ledger-database-functions)。普通用户调用校验接口，仅能校验自己有权限访问的表。
+
+- 校验防篡改用户表和用户历史表的接口为pg_catalog.ledger_hist_check，操作为：
+
+  ```sql
+  SELECT pg_catalog.ledger_hist_check(schema_name text,table_name text);
+  ```
+
+  如果校验通过，函数返回t，反之则返回f。
+
+- 校验防篡改用户表、用户历史表和全局区块表三者是否一致的接口为pg_catalog.ledger_gchain_check，操作为：
+
+  ```sql
+  SELECT pg_catalog.ledger_gchain_check(schema_name text, table_name text);
+  ```
+
+  如果校验通过，函数返回t，反之则返回f。
+
+### 操作步骤
+
+1. 校验防篡改用户表ledgernsp.usertable与其对应的历史表是否一致。
+
+   ```sql
+   mogdb=# SELECT pg_catalog.ledger_hist_check('ledgernsp', 'usertable');
+    ledger_hist_check
+   -------------------
+   t
+   (1 row)
+   ```
+
+   该结果表明防篡改用户表和用户历史表中记录的结果能够一一对应，保持一致。
+
+2. 查询防篡改用户表ledgernsp.usertable与其对应的历史表以及全局区块表中关于该表的记录是否一致。
+
+   ```sql
+   mogdb=#  SELECT pg_catalog.ledger_gchain_check('ledgernsp', 'usertable');
+    ledger_gchain_check
+   ---------------------
+   t
+   (1 row)
+   ```
+
+   查询结果显示，上述三表中关于ledgernsp.usertable的记录保持一致，未发生篡改行为。
+
+## 归档账本数据库
+
+### 前提条件
+
+- 系统中需要有审计管理员或者具有审计管理员权限的角色。
+- 数据库正常运行，并且对防篡改数据库执行了一系列增、删、改等操作，保证在查询时段内有账本操作记录结果产生。
+- 数据库已经正确配置审计文件的存储路径audit_directory。
+
+### 背景信息
+
+- 账本数据库归档功能目前提供两种校验接口，分别为：[ledger_hist_archive(text, text)](20.1-ledger-database-functions)和[ledger_gchain_archive(void)](20.1-ledger-database-functions)。账本数据库接口仅审计管理员可以调用。
+
+- 归档用户历史表的接口为pg_catalog.ledger_hist_archive，操作为：
+
+  ```sql
+  SELECT pg_catalog.ledger_hist_archive(schema_name text,table_name text);
+  ```
+
+  如果归档成功，函数返回t，反之则返回f。
+
+- 归档全局区块表的接口为pg_catalog.ledger_gchain_archive，操作为：
+
+  ```sql
+  SELECT pg_catalog.ledger_gchain_archive();
+  ```
+
+  如果归档成功，函数返回t，反之则返回f。
+
+### 操作步骤
+
+1. 对指定用户历史表进行归档操作。
+
+   ```sql
+   mogdb=# SELECT pg_catalog.ledger_hist_archive('ledgernsp', 'usertable')
+    ledger_hist_archive
+   ---------------------
+   t
+   (1 row)
+   ```
+
+   用户历史表将归档为一条数据：
+
+   ```sql
+   mogdb=# SELECT * FROM blockchain.ledgernsp_usertable_hist;
+    rec_num |     hash_ins     |     hash_del     |             pre_hash
+   ---------+------------------+------------------+----------------------------------
+          3 | e78e75b00d396899 | 8fcd74a8a6a4b484 | fd61cb772033da297d10c4e658e898d7
+   (1 row)
+   ```
+
+   该结果表明当前节点用户历史表导出成功。
+
+2. 执行全局区块表导出操作。
+
+   ```sql
+   mogdb=# SELECT pg_catalog.ledger_gchain_archive();
+    ledger_gchain_archive
+   -----------------------
+   t
+   (1 row)
+   ```
+
+   全局历史表将以用户表为单位归档为N（用户表数量）条数据：
+
+   ```sql
+   mogdb=# SELECT * FROM gs_global_chain;
+    blocknum |  dbname  | username |           starttime           | relid |  relnsp   |  relname  |     relhash      |            globalhash            | txcommand
+   ----------+----------+----------+-------------------------------+-------+-----------+-----------+------------------+----------------------------------+-----------
+           1 | postgres | libc     | 2021-05-10 19:59:38.619472+08 | 16388 | ledgernsp | usertable | 57c101076694b415 | be82f98ee68b2bc4e375f69209345406 | Archived.
+   (1 row)
+   ```
+
+   该结果表明，当前节点全局区块表导出成功。
+
+## 修复账本数据库
+
+### 前提条件
+
+- 系统中需要有审计管理员或者具有审计管理员权限的角色。
+- 数据库正常运行，并且对防篡改数据库执行了一系列增、删、改等操作，保证在查询时段内有账本操作记录结果产生。
+
+### 背景信息
+
+- 当在异常情况或表被损坏时需要使用[账本数据库的函数](ledger-database-functions)章节中的ledger_gchain_repair(text, text)或ledger_hist_repair(text, text)接口对全局区块表或用户历史表进行修复，修复后调用全局区块表或用户历史表校验接口结果为true。
+
+- 修复用户历史表的接口为pg_catalog.ledger_hist_repair，操作为：
+
+  ```sql
+  SELECT pg_catalog.ledger_hist_repair(schema_name text,table_name text);
+  ```
+
+  如果修复成功，函数返回修复过程中用户历史表hash的增量。
+
+- 归档全局区块表的接口为pg_catalog.ledger_gchain_repair，操作为：
+
+  ```sql
+  SELECT pg_catalog.ledger_gchain_repair(schema_name text,table_name text);
+  ```
+
+  如果修复成功，函数返回修复过程中全局区块表hash的增量。
+
+### 操作步骤
+
+1. 执行历史表修复操作。
+
+   ```sql
+   mogdb=# SELECT pg_catalog.ledger_hist_repair('ledgernsp', 'usertable');
+    ledger_hist_repair
+   --------------------
+   84e8bfc3b974e9cf
+   (1 row)
+   ```
+
+   该结果表明当前节点用户历史表修复成功，修复造成的用户历史表hash增量为84e8bfc3b974e9cf。
+
+2. 执行全局区块表修复操作。
+
+   ```sql
+   mogdb=# SELECT pg_catalog.ledger_gchain_repair('ledgernsp', 'usertable');
+    ledger_gchain_repair
+   ----------------------
+   a41714001181a294
+   (1 row)
+   ```
+
+   该结果表明，全局区块表修复成功，且插入一条修复数据，其hash值为a41714001181a294。
diff --git a/product/zh/docs-mogdb/v3.0/source-code-parsing.md b/product/zh/docs-mogdb/v3.0/source-code-parsing.md
new file mode 100644
index 0000000000000000000000000000000000000000..56f4d9c7535b890f9f7a6ad15026fe30cd6d3dd0
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/source-code-parsing.md
@@ -0,0 +1,88 @@
+---
+title: 源码解析
+summary: 源码解析
+author: Guo Huan
+date: 2022-02-07
+---
+
+# 源码解析
+
+本系列文章针对openGauss开源数据库的源码进行分模块解析，可以作为内核开发者了解openGauss数据库并基于openGauss进行数据库开发的参考教程，也可以作为广大高校计算机专业“数据库设计”课程的参考教材。
+
+您可以点击以下链接跳转至墨天轮专栏查看本系列文章。
+
+## openGauss简介
+
+[openGauss简介（上）](https://www.modb.pro/db/47895)
+
+[openGauss简介（下）](https://www.modb.pro/db/48291)
+
+## openGauss开发快速入门
+
+[openGauss开发快速入门（上）](https://www.modb.pro/db/48657)
+
+[openGauss开发快速入门（中）](https://www.modb.pro/db/48870)
+
+[openGauss开发快速入门（下）](https://www.modb.pro/db/49118)
+
+## 公共组件源码解析
+
+[公共组件源码解析（上）](https://www.modb.pro/db/49242)
+
+[公共组件源码解析（下）](https://www.modb.pro/db/49711)
+
+## 存储引擎源码解析
+
+[存储引擎源码解析（一）](https://www.modb.pro/db/51541)
+
+[存储引擎源码解析（二）](https://www.modb.pro/db/53926)
+
+[存储引擎源码解析（三）](https://www.modb.pro/db/57991)
+
+[存储引擎源码解析（四）](https://www.modb.pro/db/64255)
+
+[存储引擎源码解析（五）](https://www.modb.pro/db/77848)
+
+## 事务机制源码解析
+
+[事务机制源码解析（一）](https://www.modb.pro/db/78553)
+
+[事务机制源码解析（二）](https://www.modb.pro/db/79534)
+
+[事务机制源码解析（三）](https://www.modb.pro/db/81991)
+
+## SQL引擎源码解析
+
+[SQL引擎源码解析（一）](https://www.modb.pro/db/86068)
+
+[SQL引擎源码解析（二）](https://www.modb.pro/db/100257)
+
+## 执行器解析
+
+[执行器解析（一）](https://www.modb.pro/db/103591)
+
+[执行器解析（二）](https://www.modb.pro/db/106997)
+
+[执行器解析（三）](https://www.modb.pro/db/111770)
+
+## AI技术
+
+[AI技术（一）：自调优](https://www.modb.pro/db/162007)
+
+[AI技术（二）：慢SQL发现](https://www.modb.pro/db/171668)
+
+[AI技术（三）：智能索引推荐](https://www.modb.pro/db/210235)
+
+[AI技术（四）：指标采集、预测与异常检测](https://www.modb.pro/db/245341)
+
+[AI技术（五）：AI查询时间预测](https://www.modb.pro/db/251405)
+
+[AI技术（六）：DeepSQL](https://www.modb.pro/db/329691)
+
+## 安全管理源码解析
+
+[安全管理源码解析（一）](https://www.modb.pro/db/335331)
+
+[安全管理源码解析（二）](https://www.modb.pro/db/337160)
+
+[安全管理源码解析（三）](https://www.modb.pro/db/378249)
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/toc.md b/product/zh/docs-mogdb/v3.0/toc.md
new file mode 100644
index 0000000000000000000000000000000000000000..aa039c448f4f04fe976f4181095cf7db26bbd635
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/toc.md
@@ -0,0 +1,1413 @@
+<!-- markdownlint-disable MD007 -->
+<!-- markdownlint-disable MD041 -->
+# MogDB Documentation 3.0
+
+## Documentation List
+
++ 关于MogDB
+  + [MogDB简介](/overview.md)
+  + [MogDB与openGauss](/about-mogdb/MogDB-compared-to-openGauss.md)
+  + [MogDB发行说明](/about-mogdb/mogdb-release-notes.md)
+  + 高可用和高性能
+    + [高可用测试](/about-mogdb/test-report/ha/MogDB-ha-test-report.md)
+    + 性能测试
+      + [性能测试简述](/about-mogdb/test-report/performance/1-performance-test-overview.md)
+      + [MogDB on 鲲鹏性能测试](/about-mogdb/test-report/performance/2-mogdb-on-kunpeng-performance-test-report.md)
+      + [MogDB on x86性能测试](/about-mogdb/test-report/performance/3-mogdb-on-x86-performance-test-report.md)
+  + 开源组件
+    + [容器版本的MogDB](/about-mogdb/open-source-components/2-docker-based-mogdb.md)
+    + [compat-tools](/about-mogdb/open-source-components/compat-tools.md)
+    + [mogdb-monitor](/about-mogdb/open-source-components/mogdb-monitor.md)
+    + [wal2json](/about-mogdb/open-source-components/5-wal2json-extention-for-mogdb&opengauss.md)
+    + [mog_filedump](/about-mogdb/open-source-components/mog_filedump.md)
+    + [mog_xlogdump](/about-mogdb/open-source-components/mog_xlogdump.md)
+  + [使用限制](/about-mogdb/usage-limitations.md)
+  + [法律声明](/about-mogdb/terms-of-use.md)
++ 快速入门
+  + [MogDB实训平台](/quick-start/mogdb-playground.md)
+  + [容器化安装](/quick-start/container-based-installation.md)
+  + [单节点安装](/quick-start/installation-on-a-single-node.md)
+  + 访问数据库
+    + 使用命令行访问MogDB
+      + [gsql](/quick-start/mogdb-access/use-cli-to-access-mogdb/gsql.md)
+      + [pgcli](/quick-start/mogdb-access/use-cli-to-access-mogdb/pgcli.md)
+    + 使用图形工具访问MogDB
+      + [Data Studio](/quick-start/mogdb-access/use-gui-tools-to-access-mogdb/datastudio.md)
+      + [DBeaver](/quick-start/mogdb-access/use-gui-tools-to-access-mogdb/dbeaver.md)
+    + 使用中间件访问MogDB
+      + [WebLogic配置MogDB数据源参考](/quick-start/mogdb-access/use-middleware-to-access-mogdb/weblogic-configures-mogdb(postgresql)-data-source-reference.md)
+      + [WebSphere配置MogDB数据源参考](/quick-start/mogdb-access/use-middleware-to-access-mogdb/websphere-configures-mogdb(postgresql)-data-source-reference.md)
+    + 使用编程语言访问MogDB
+      + [Java](/quick-start/mogdb-access/use-programming-language-to-access-mogdb/java.md)
+      + [C/C++](/quick-start/mogdb-access/use-programming-language-to-access-mogdb/c-cpp.md)
+      + [Python](/quick-start/mogdb-access/use-programming-language-to-access-mogdb/python.md)
+      + [Go](/quick-start/mogdb-access/use-programming-language-to-access-mogdb/go.md)
+      + [Rust](/quick-start/mogdb-access/use-programming-language-to-access-mogdb/rust.md)
+      + [NodeJS](/quick-start/mogdb-access/use-programming-language-to-access-mogdb/nodejs.md)
+  + [使用样本数据集Mogila](/quick-start/mogila.md)
++ 安装指南
+  + [容器化安装](/installation-guide/docker-installation/docker-installation.md)
+  + 极简安装
+    + [安装准备](/installation-guide/simplified-installation-process/1-installation-preparation.md)
+    + [单节点安装](/installation-guide/simplified-installation-process/2-installation-on-a-single-node.md)
+    + [一主一备节点安装](/installation-guide/simplified-installation-process/3-installation-on-primary-standby-nodes.md)
+  + 标准安装
+    + [安装概述](/installation-guide/standard-installation/1-installation-overview.md)
+    + 安装准备
+      + [环境要求](/installation-guide/standard-installation/2-environment-requirement.md)
+      + [修改操作系统配置](/installation-guide/standard-installation/3-modifying-os-configuration.md)
+    + [安装MogDB](/installation-guide/standard-installation/4-installing-mogdb.md)
+    + [安装验证](/installation-guide/standard-installation/5-verifying-installation.md)
+    + [推荐参数设置及新建测试库](/installation-guide/standard-installation/7-recommended-parameter-settings.md)
+    + [卸载MogDB](/installation-guide/standard-installation/6-uninstallation.md)
+  + [手动安装](/installation-guide/manual-installation.md)
++ 管理指南
+  + 日常运维
+    + [启停MogDB](/administrator-guide/routine-maintenance/0-starting-and-stopping-mogdb.md)
+    + [gsql客户端连接](/administrator-guide/routine-maintenance/using-the-gsql-client-for-connection.md)
+    + [日维护检查项](/administrator-guide/routine-maintenance/1-routine-maintenance-check-items.md)
+    + [检查操作系统参数](/administrator-guide/routine-maintenance/2-checking-os-parameters.md)
+    + [检查MogDB健康状态](/administrator-guide/routine-maintenance/3-checking-mogdb-health-status.md)
+    + [检查数据库性能](/administrator-guide/routine-maintenance/4-checking-database-performance.md)
+    + [检查和清理日志](/administrator-guide/routine-maintenance/5-checking-and-deleting-logs.md)
+    + [检查时间一致性](/administrator-guide/routine-maintenance/6-checking-time-consistency.md)
+    + [检查应用连接数](/administrator-guide/routine-maintenance/7-checking-the-number-of-application-connections.md)
+    + [例行维护表](/administrator-guide/routine-maintenance/8-routinely-maintaining-tables.md)
+    + [例行重建索引](/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md)
+    + [数据安全维护建议](/administrator-guide/routine-maintenance/10-data-security-maintenance-suggestions.md)
+    + [慢SQL诊断](/administrator-guide/routine-maintenance/slow-sql-diagnosis.md)
+    + [日志参考](/administrator-guide/routine-maintenance/11-log-reference.md)
+  + [主备管理](/administrator-guide/primary-and-standby-management.md)
+  + MOT内存表管理
+    + MOT介绍
+      + [MOT简介](/administrator-guide/mot-engine/1-introducing-mot/1-mot-introduction.md)
+      + [MOT特性及价值](/administrator-guide/mot-engine/1-introducing-mot/2-mot-features-and-benefits.md)
+      + [MOT关键技术](/administrator-guide/mot-engine/1-introducing-mot/3-mot-key-technologies.md)
+      + [MOT应用场景](/administrator-guide/mot-engine/1-introducing-mot/4-mot-usage-scenarios.md)
+      + [MOT性能基准](/administrator-guide/mot-engine/1-introducing-mot/5-mot-performance-benchmarks.md)
+    + 使用MOT
+      + [MOT使用概述](/administrator-guide/mot-engine/2-using-mot/1-using-mot-overview.md)
+      + [MOT准备](/administrator-guide/mot-engine/2-using-mot/2-mot-preparation.md)
+      + [MOT部署](/administrator-guide/mot-engine/2-using-mot/3-mot-deployment.md)
+      + [MOT使用](/administrator-guide/mot-engine/2-using-mot/4-mot-usage.md)
+      + [MOT管理](/administrator-guide/mot-engine/2-using-mot/5-mot-administration.md)
+      + [MOT样例TPC-C基准](/administrator-guide/mot-engine/2-using-mot/6-mot-sample-tpcc-benchmark.md)
+    + MOT的概念
+      + [MOT纵向扩容架构](/administrator-guide/mot-engine/3-concepts-of-mot/3-1.md)
+      + [MOT并发控制机制](/administrator-guide/mot-engine/3-concepts-of-mot/3-2.md)
+      + [扩展FDW与其他MogDB特性](/administrator-guide/mot-engine/3-concepts-of-mot/3-3.md)
+      + [NUMA-aware分配和亲和性](/administrator-guide/mot-engine/3-concepts-of-mot/3-4.md)
+      + [MOT索引](/administrator-guide/mot-engine/3-concepts-of-mot/3-5.md)
+      + [MOT持久性概念](/administrator-guide/mot-engine/3-concepts-of-mot/3-6.md)
+      + [MOT恢复概念](/administrator-guide/mot-engine/3-concepts-of-mot/3-7.md)
+      + [MOT查询原生编译（JIT）](/administrator-guide/mot-engine/3-concepts-of-mot/3-8.md)
+      + [对比：磁盘与MOT](/administrator-guide/mot-engine/3-concepts-of-mot/3-9.md)
+    + 附录
+      + [参考文献](/administrator-guide/mot-engine/4-appendix/1-references.md)
+      + [术语表](/administrator-guide/mot-engine/4-appendix/2-glossary.md)
+  + [列存表管理](/administrator-guide/column-store-tables-management.md)
+  + 备份与恢复
+    + [概述](/administrator-guide/br/1-1-br.md)
+    + [物理备份恢复](/administrator-guide/br/1-2-br.md)
+    + [逻辑备份恢复](/administrator-guide/br/1-3-br.md)
+    + [闪回恢复](/administrator-guide/br/1-4-br.md)
+  + 数据导出导入
+    + 导入数据
+      + [导入方式](/administrator-guide/importing-and-exporting-data/importing-data/1-import-modes.md)
+      + [通过INSERT语句直接写入数据](/administrator-guide/importing-and-exporting-data/importing-data/2-running-the-INSERT-statement-to-insert-data.md)
+      + [使用COPY FROM STDIN导入数据](/administrator-guide/importing-and-exporting-data/importing-data/3-running-the-COPY-FROM-STDIN-statement-to-import-data.md)
+      + [使用gsql元命令导入数据](/administrator-guide/importing-and-exporting-data/importing-data/4-using-a-gsql-meta-command-to-import-data.md)
+      + [使用gs_restore命令导入数据](/administrator-guide/importing-and-exporting-data/importing-data/5-using-gs_restore-to-import-data.md)
+      + [更新表中数据](/administrator-guide/importing-and-exporting-data/importing-data/6-updating-data-in-a-table.md)
+      + [深层复制](/administrator-guide/importing-and-exporting-data/importing-data/7-deep-copy.md)
+      + [分析表](/administrator-guide/importing-and-exporting-data/importing-data/8-ANALYZE-table.md)
+      + [对表执行VACUUM](/administrator-guide/importing-and-exporting-data/importing-data/9-doing-VACUUM-to-a-table.md)
+      + [管理并发写入操作](/administrator-guide/importing-and-exporting-data/importing-data/10-managing-concurrent-write-operations.md)
+    + 导出数据
+      + [使用gs_dump和gs_dumpall命令导出数据概述](/administrator-guide/importing-and-exporting-data/exporting-data/1-using-gs_dump-and-gs_dumpall-to-export-data-overview.md)
+      + [导出单个数据库](/administrator-guide/importing-and-exporting-data/exporting-data/2-exporting-a-single-database.md)
+      + [导出所有数据库](/administrator-guide/importing-and-exporting-data/exporting-data/3-exporting-all-databases.md)
+      + [无权限角色导出数据](/administrator-guide/importing-and-exporting-data/exporting-data/4-data-export-by-a-user-without-required-permissions.md)
+  + [升级指南](/administrator-guide/upgrade-guide.md)
++ 故障诊断
+  + [常见故障定位手段](/common-faults-and-identification/common-fault-locating-methods.md)
+  + 常见故障定位案例
+    + core问题定位
+      + [磁盘满故障引起的core问题](/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/1-core-dump-occurs-due-to-full-disk-space.md)
+      + [GUC参数log_directory设置不正确引起的core问题](/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/2-core-dump-occurs-due-to-incorrect-settings-of-guc-parameter-log-directory.md)
+      + [开启RemoveIPC引起的core问题](/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/3-core-dump-occurs-when-removeipc-is-enabled.md)
+      + [x86下安装完成后发生coredump](/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/4-core-dump-occurs-after-installation-on-x86.md)
+    + 权限/会话/数据类型问题定位
+      + [强制结束指定的问题会话](/common-faults-and-identification/common-fault-locating-cases/13-forcibly-terminating-a-session.md)
+      + [不同用户查询同表显示数据不同](/common-faults-and-identification/common-fault-locating-cases/19-different-data-is-displayed.md)
+      + [业务运行时整数转换错](/common-faults-and-identification/common-fault-locating-cases/22-an-error-occurs-during-integer-conversion.md)
+    + 服务/高可用/并发问题定位
+      + [备机处于need repair(WAL)状态问题](/common-faults-and-identification/common-fault-locating-cases/3-standby-node-in-the-need-repair-state.md)
+      + [服务启动失败](/common-faults-and-identification/common-fault-locating-cases/5-service-startup-failure.md)
+      + [switchover操作时，主机降备卡住](/common-faults-and-identification/common-fault-locating-cases/9-primary-node-is-hung-in-demoting.md)
+      + [高并发报错”too many clients already”或无法创建线程](/common-faults-and-identification/common-fault-locating-cases/23-too-many-clients-already.md)
+    + 表/分区表问题定位
+      + [VACUUM FULL一张表后，表文件大小无变化](/common-faults-and-identification/common-fault-locating-cases/17-table-size-does-not-change.md)
+      + [执行修改表分区操作时报错](/common-faults-and-identification/common-fault-locating-cases/18-an-error-is-reported-when-the-table-partition-is-modified.md)
+    + 文件系统/磁盘/内存问题定位
+      + [在XFS文件系统中，使用du命令查询数据文件大小大于文件实际大小](/common-faults-and-identification/common-fault-locating-cases/7-after-you-run-the-du-command.md)
+      + [在XFS文件系统中，出现文件损坏](/common-faults-and-identification/common-fault-locating-cases/8-file-is-damaged-in-the-xfs-file-system.md)
+      + [内存不足问题](/common-faults-and-identification/common-fault-locating-cases/4-insufficient-memory.md)
+      + [出现“Error:No space left on device”提示](/common-faults-and-identification/common-fault-locating-cases/6-error-no-space-left-on-device-is-displayed.md)
+      + [TPCC运行时，注入磁盘满故障，TPCC卡住的问题](/common-faults-and-identification/common-fault-locating-cases/2-when-the-tpcc-is-running.md)
+      + [磁盘空间达到阈值，数据库只读](/common-faults-and-identification/common-fault-locating-cases/10-disk-space-usage-reaches-the-threshold.md)
+    + SQL问题定位
+      + [执行 SQL 语句时，提示 Lock wait timeout](/common-faults-and-identification/common-fault-locating-cases/16-lock-wait-timeout-is-displayed.md)
+      + [分析查询语句是否被阻塞](/common-faults-and-identification/common-fault-locating-cases/14-analyzing-whether-a-query-statement-is-blocked.md)
+      + [分析查询效率异常降低的问题](/common-faults-and-identification/common-fault-locating-cases/15-low-query-efficiency.md)
+      + [分析查询语句长时间运行的问题](/common-faults-and-identification/common-fault-locating-cases/11-slow-response-to-a-query-statement.md)
+      + [分析查询语句运行状态](/common-faults-and-identification/common-fault-locating-cases/12-analyzing-the-status-of-a-query-statement.md)
+    + 索引问题定位
+      + [修改索引时只调用索引名提示索引不存在](/common-faults-and-identification/common-fault-locating-cases/20-when-a-user-specifies-only-an-index-name.md)
+      + [重建索引失败](/common-faults-and-identification/common-fault-locating-cases/21-reindexing-fails.md)
+      + [btree 索引故障情况下应对策略](/common-faults-and-identification/common-fault-locating-cases/24-b-tree-index-faults.md)
++ 安全指南
+  + 数据库安全管理
+    + [客户端接入认证](/security-guide/security/1-client-access-authentication.md)
+    + [管理用户及权限](/security-guide/security/2-managing-users-and-their-permissions.md)
+    + [设置数据库审计](/security-guide/security/3-configuring-database-audit.md)
+    + [设置密态等值查询](/security-guide/security/4-setting-encrypted-equality-query.md)
+    + [设置账本数据库](/security-guide/security/5-setting-a-ledger-database.md)
++ 性能优化指南
+  + 系统优化指南
+    + [操作系统参数调优](/performance-tuning/1-system/1-optimizing-os-parameters.md)
+    + [数据库系统参数调优](/performance-tuning/1-system/2-optimizing-database-parameters.md)
+    + [配置SMP](/performance-tuning/1-system/4-configuring-smp.md)
+    + [配置LLVM](/performance-tuning/1-system/3-configuring-llvm.md)
+  + SQL优化指南
+    + [Query执行流程](/performance-tuning/2-sql/1-query-execution-process.md)
+    + [SQL执行计划介绍](/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md)
+    + [调优流程](/performance-tuning/2-sql/3-tuning-process.md)
+    + [更新统计信息](/performance-tuning/2-sql/4-updating-statistics.md)
+    + [审视和修改表定义](/performance-tuning/2-sql/5-reviewing-and-modifying-a-table-definition.md)
+    + [典型SQL调优点](/performance-tuning/2-sql/6-typical-sql-optimization-methods.md)
+    + [SQL语句改写规则](/performance-tuning/2-sql/7-experience-in-rewriting-sql-statements.md)
+    + [SQL调优关键参数调整](/performance-tuning/2-sql/8-resetting-key-parameters-during-sql-tuning.md)
+    + [使用Plan Hint进行调优](/performance-tuning/2-sql/9-hint-based-tuning.md)
+  + [WDR解读指南](/performance-tuning/wdr-snapshot-schema.md)
+  + [TPCC性能优化指南](/performance-tuning/TPCC-performance-tuning-guide.md)
++ 开发者指南
+  + 开发设计建议
+    + [概述](/developer-guide/development-and-design-proposal/overview-of-development-and-design-proposal.md)
+    + [数据库对象命名](/developer-guide/development-and-design-proposal/database-object-naming-conventions.md)
+    + 数据库对象设计
+      + [Database和Schema设计](/developer-guide/development-and-design-proposal/database-object-design/database-and-schema-design.md)
+      + [表设计](/developer-guide/development-and-design-proposal/database-object-design/table-design.md)
+      + [字段设计](/developer-guide/development-and-design-proposal/database-object-design/field-design.md)
+      + [约束设计](/developer-guide/development-and-design-proposal/database-object-design/constraint-design.md)
+      + [视图和关联表设计](/developer-guide/development-and-design-proposal/database-object-design/view-and-joined-table-design.md)
+    + 工具对接
+      + [JDBC配置](/developer-guide/development-and-design-proposal/tool-interconnection/jdbc-configuration.md)
+    + [SQL编写](/developer-guide/development-and-design-proposal/sql-compilation.md)
+  + 应用程序开发教程
+    + [开发规范](/developer-guide/dev/1-development-specifications.md)
+    + 基于JDBC开发
+      + [概述](/developer-guide/dev/2-development-based-on-jdbc/1-development-based-on-jdbc-overview.md)
+      + [JDBC包、驱动类和环境类](/developer-guide/dev/2-development-based-on-jdbc/2-jdbc-package-driver-class-and-environment-class.md)
+      + [开发流程](/developer-guide/dev/2-development-based-on-jdbc/3-development-process.md)
+      + [加载驱动](/developer-guide/dev/2-development-based-on-jdbc/4-loading-the-driver.md)
+      + [连接数据库](/developer-guide/dev/2-development-based-on-jdbc/5-connecting-to-a-database.md)
+      + [连接数据库（以SSL方式）](/developer-guide/dev/2-development-based-on-jdbc/6-connecting-to-a-database-using-ssl.md)
+      + [执行SQL语句](/developer-guide/dev/2-development-based-on-jdbc/7-running-sql-statements.md)
+      + [处理结果集](/developer-guide/dev/2-development-based-on-jdbc/8-processing-data-in-a-result-set.md)
+      + [关闭连接](/developer-guide/dev/2-development-based-on-jdbc/9-closing-a-connection.md)
+      + [日志管理](/developer-guide/dev/2-development-based-on-jdbc/8.1-log-management.md)
+      + [示例：常用操作](/developer-guide/dev/2-development-based-on-jdbc/10-example-common-operations.md)
+      + [示例：重新执行应用SQL](/developer-guide/dev/2-development-based-on-jdbc/11-example-retrying-sql-queries-for-applications.md)
+      + [示例：通过本地文件导入导出数据](/developer-guide/dev/2-development-based-on-jdbc/12-example-importing-and-exporting-data-through-local-files.md)
+      + [示例：从MY向MogDB进行数据迁移](/developer-guide/dev/2-development-based-on-jdbc/13-example-2-migrating-data-from-a-my-database-to-mogdb.md)
+      + [示例：逻辑复制代码示例](/developer-guide/dev/2-development-based-on-jdbc/14-example-logic-replication-code.md)
+      + [示例：不同场景下连接数据库参数配置](/developer-guide/dev/2-development-based-on-jdbc/14.1-example-parameters-for-connecting-to-the-database-in-different-scenarios.md)
+      + JDBC接口参考
+        + [java.sql.Connection](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/1-java-sql-Connection.md)
+        + [java.sql.CallableStatement](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/2-java-sql-CallableStatement.md)
+        + [java.sql.DatabaseMetaData](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/3-java-sql-DatabaseMetaData.md)
+        + [java.sql.Driver](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/4-java-sql-Driver.md)
+        + [java.sql.PreparedStatement](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/5-java-sql-PreparedStatement.md)
+        + [java.sql.ResultSet](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/6-java-sql-ResultSet.md)
+        + [java.sql.ResultSetMetaData](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/7-java-sql-ResultSetMetaData.md)
+        + [java.sql.Statement](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/8-java-sql-Statement.md)
+        + [javax.sql.ConnectionPoolDataSource](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/9-javax-sql-ConnectionPoolDataSource.md)
+        + [javax.sql.DataSource](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/10-javax-sql-DataSource.md)
+        + [javax.sql.PooledConnection](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/11-javax-sql-PooledConnection.md)
+        + [javax.naming.Context](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/12-javax-naming-Context.md)
+        + [javax.naming.spi.InitialContextFactory](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/13-javax-naming-spi-InitialContextFactory.md)
+        + [CopyManager](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/14-CopyManager.md)
+    + 基于ODBC开发
+      + [概述](/developer-guide/dev/3-development-based-on-odbc/1-development-based-on-odbc-overview.md)
+      + [ODBC包及依赖的库和头文件](/developer-guide/dev/3-development-based-on-odbc/2-odbc-packages-dependent-libraries-and-header-files.md)
+      + [Linux下配置数据源](/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md)
+      + [开发流程](/developer-guide/dev/3-development-based-on-odbc/4-development-process.md)
+      + [示例：常用功能和批量绑定](/developer-guide/dev/3-development-based-on-odbc/5-example-common-functions-and-batch-binding.md)
+      + [典型应用场景配置](/developer-guide/dev/3-development-based-on-odbc/5.1-typical-application-scenarios-and-configurations.md)
+      + ODBC接口参考
+        + [说明](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-0-odbc-overview.md)
+        + [SQLAllocEnv](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-1-SQLAllocEnv.md)
+        + [SQLAllocConnect](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-2-SQLAllocConnect.md)
+        + [SQLAllocHandle](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-3-SQLAllocHandle.md)
+        + [SQLAllocStmt](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-4-SQLAllocStmt.md)
+        + [SQLBindCol](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-5-SQLBindCol.md)
+        + [SQLBindParameter](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-6-SQLBindParameter.md)
+        + [SQLColAttribute](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-7-SQLColAttribute.md)
+        + [SQLConnect](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-8-SQLConnect.md)
+        + [SQLDisconnect](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-9-SQLDisconnect.md)
+        + [SQLExecDirect](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-10-SQLExecDirect.md)
+        + [SQLExecute](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-11-SQLExecute.md)
+        + [SQLFetch](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-12-SQLFetch.md)
+        + [SQLFreeStmt](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-13-SQLFreeStmt.md)
+        + [SQLFreeConnect](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-14-SQLFreeConnect.md)
+        + [SQLFreeHandle](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-15-SQLFreeHandle.md)
+        + [SQLFreeEnv](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-16-SQLFreeEnv.md)
+        + [SQLPrepare](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-17-SQLPrepare.md)
+        + [SQLGetData](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-18-SQLGetData.md)
+        + [SQLGetDiagRec](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-19-SQLGetDiagRec.md)
+        + [SQLSetConnectAttr](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-20-SQLSetConnectAttr.md)
+        + [SQLSetEnvAttr](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-21-SQLSetEnvAttr.md)
+        + [SQLSetStmtAttr](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-22-SQLSetStmtAttr.md)
+        + [示例](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-23-Examples.md)
+    + 基于libpq开发
+      + [基于libpq开发](/developer-guide/dev/4-development-based-on-libpq/1-development-based-on-libpq.md)
+      + libpq接口参考
+        + 数据库连接控制函数
+          + [说明](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/1-database-connection-control-functions-overview.md)
+          + [PQconnectdbParams](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/2-PQconnectdbParams.md)
+          + [PQconnectdb](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/3-PQconnectdb.md)
+          + [PQconninfoParse](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/4-PQconninfoParse.md)
+          + [PQconnectStart](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/5-PQconnectStart.md)
+          + [PQerrorMessage](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/6-PQerrorMessage.md)
+          + [PQsetdbLogin](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/7-PQsetdbLogin.md)
+          + [PQfinish](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/8-PQfinish.md)
+          + [PQreset](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/9-PQreset.md)
+          + [PQstatus](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/10-PQstatus.md)
+        + 数据库执行语句函数
+          + [PQclear](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/1-PQclear.md)
+          + [PQexec](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/2-PQexec.md)
+          + [PQexecParams](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/3-PQexecParams.md)
+          + [PQexecParamsBatch](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/4-PQexecParamsBatch.md)
+          + [PQexecPrepared](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/5-PQexecPrepared.md)
+          + [PQexecPreparedBatch](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/6-PQexecPreparedBatch.md)
+          + [PQfname](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/7-PQfname.md)
+          + [PQgetvalue](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/8-PQgetvalue.md)
+          + [PQnfields](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/9-PQnfields.md)
+          + [PQntuples](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/10-PQntuples.md)
+          + [PQprepare](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/11-PQprepare.md)
+          + [PQresultStatus](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/12-PQresultStatus.md)
+        + 异步命令处理
+          + [说明](/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/1-functions-for-asynchronous-command-processing-overview.md)
+          + [PQsendQuery](/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/2-PQsendQuery.md)
+          + [PQsendQueryParams](/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/3-PQsendQueryParams.md)
+          + [PQsendPrepare](/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/4-PQsendPrepare.md)
+          + [PQsendQueryPrepared](/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/5-PQsendQueryPrepared.md)
+          + [PQflush](/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/6-PQflush.md)
+        + 取消正在处理的查询
+          + [PQgetCancel](/developer-guide/dev/4-development-based-on-libpq/2-libpq/4-functions-for-canceling-queries-in-progress/1-PQgetCancel.md)
+          + [PQfreeCancel](/developer-guide/dev/4-development-based-on-libpq/2-libpq/4-functions-for-canceling-queries-in-progress/2-PQfreeCancel.md)
+          + [PQcancel](/developer-guide/dev/4-development-based-on-libpq/2-libpq/4-functions-for-canceling-queries-in-progress/3-PQcancel.md)
+        + [示例](/developer-guide/dev/4-development-based-on-libpq/2-libpq/5-libpq-example.md)
+        + [链接字符](/developer-guide/dev/4-development-based-on-libpq/2-libpq/6-connection-characters.md)
+    + 基于Psycopg开发
+      + [基于Psycopg开发](/developer-guide/dev/4.1-psycopg-based-development/1-psycopg-based-development.md)
+      + [Psycopg包](/developer-guide/dev/4.1-psycopg-based-development/2-psycopg-package.md)
+      + [开发流程](/developer-guide/dev/4.1-psycopg-based-development/3.1-development-process.md)
+      + [加载驱动](/developer-guide/dev/4.1-psycopg-based-development/4-loading-a-driver.md)
+      + [连接数据库](/developer-guide/dev/4.1-psycopg-based-development/5.1-connecting-to-a-database.md)
+      + [执行SQL语句](/developer-guide/dev/4.1-psycopg-based-development/6-executing-sql-statements.md)
+      + [处理结果集](/developer-guide/dev/4.1-psycopg-based-development/7-processing-the-result-set.md)
+      + [关闭连接](/developer-guide/dev/4.1-psycopg-based-development/8-closing-the-connection.md)
+      + [连接数据库（SSL方式）](/developer-guide/dev/4.1-psycopg-based-development/9-connecting-to-the-database-using-ssl.md)
+      + [示例：常用操作](/developer-guide/dev/4.1-psycopg-based-development/10.1-example-common-operations.md)
+      + Psycopg接口参考
+        + [psycopg2.connect()](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/1-psycopg2-connect.md)
+        + [connection.cursor()](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/2-connection-cursor.md)
+        + [cursor.execute(query,vars_list)](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/3-cursor-execute-query-vars-list.md)
+        + [curosr.executemany(query,vars_list)](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/4-curosr-executemany-query-vars-list.md)
+        + [connection.commit()](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/5-connection-commit.md)
+        + [connection.rollback()](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/6-connection-rollback.md)
+        + [cursor.fetchone()](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/7-cursor-fetchone.md)
+        + [cursor.fetchall()](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/8-cursor-fetchall.md)
+        + [cursor.close()](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/9-cursor-close.md)
+        + [connection.close()](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/10-connection-close.md)
+    + [调试](/developer-guide/dev/5-commissioning.md)
+    + [附录](/developer-guide/dev/6-appendix.md)
+  + [存储过程](/developer-guide/1-1-stored-procedure.md)
+  + [用户自定义函数](/developer-guide/user-defined-functions.md)
+  + PL/pgSQL-SQL过程语言
+    + [PL/pgSQL语言函数介绍](/developer-guide/plpgsql/1-1-plpgsql-overview.md)
+    + [数据类型](/developer-guide/plpgsql/1-2-data-types.md)
+    + [数据类型转换](/developer-guide/plpgsql/1-3-data-type-conversion.md)
+    + [数组和record](/developer-guide/plpgsql/1-4-arrays-and-records.md)
+    + [声明语法](/developer-guide/plpgsql/1-5-declare-syntax.md)
+    + [基本语句](/developer-guide/plpgsql/1-6-basic-statements.md)
+    + [动态语句](/developer-guide/plpgsql/1-7-dynamic-statements.md)
+    + [控制语句](/developer-guide/plpgsql/1-8-control-statements.md)
+    + [事务管理](/developer-guide/plpgsql/1-9-transaction-management.md)
+    + [其他语句](/developer-guide/plpgsql/1-10-other-statements.md)
+    + [游标](/developer-guide/plpgsql/1-11-cursors.md)
+    + [Retry管理](/developer-guide/plpgsql/1-12-retry-management.md)
+    + [调试](/developer-guide/plpgsql/1-13-debugging.md)
+  + 定时任务
+    + [PKG_SERVICE接口](/developer-guide/scheduled-jobs/pkg-service.md)
+  + 自治事务
+    + [介绍](/developer-guide/autonomous-transaction/1-introduction-to-autonomous-transaction.md)
+    + [存储过程支持自治事务](/developer-guide/autonomous-transaction/3-stored-procedure-supporting-autonomous-transaction.md)
+    + [匿名块支持自治事务](/developer-guide/autonomous-transaction/anonymous-block-supporting-autonomous-transaction.md)
+    + [函数支持自治事务](/developer-guide/autonomous-transaction/2-function-supporting-autonomous-transaction.md)
+    + [规格约束](/developer-guide/autonomous-transaction/4-restrictions.md)
+  + 逻辑复制
+    + 逻辑解码
+      + [逻辑解码概述](/developer-guide/logical-replication/1-logical-decoding.md)
+      + [使用SQL函数接口进行逻辑解码](/developer-guide/logical-replication/2-logical-decoding-by-sql-function-interfaces.md)
+  + Foreign Data Wrapper
+    + [介绍](/developer-guide/foreign-data-wrapper/fdw-introduction.md)
+    + [oracle_fdw](/developer-guide/foreign-data-wrapper/1-oracle_fdw.md)
+    + [mysql_fdw](/developer-guide/foreign-data-wrapper/2-mysql_fdw.md)
+    + [postgres_fdw](/developer-guide/foreign-data-wrapper/3-postgres_fdw.md)
+    + [file_fdw](/developer-guide/foreign-data-wrapper/file_fdw.md)
+    + [dblink](/developer-guide/foreign-data-wrapper/dblink.md)
+  + 物化视图
+    + [物化视图概述](/developer-guide/materialized-view/1-materialized-view-overview.md)
+    + 全量物化视图
+      + [概述](/developer-guide/materialized-view/2-full-materialized-view/1-full-materialized-view-overview.md)
+      + [使用](/developer-guide/materialized-view/2-full-materialized-view/2-full-materialized-view-usage.md)
+      + [支持和约束](/developer-guide/materialized-view/2-full-materialized-view/3-full-materialized-view-support-and-constraints.md)
+    + 增量物化视图
+      + [概述](/developer-guide/materialized-view/3-incremental-materialized-view/1-incremental-materialized-view-overview.md)
+      + [使用](/developer-guide/materialized-view/3-incremental-materialized-view/2-incremental-materialized-view-usage.md)
+      + [支持和约束](/developer-guide/materialized-view/3-incremental-materialized-view/3-incremental-materialized-view-support-and-constraints.md)
+  + AI特性
+    + [概述](/developer-guide/AI-features/1-AI-features-overview.md)
+    + Predictor：AI查询时间预测
+      + [概述](/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-1-ai-query-time-forecasting-overview.md)
+      + [环境部署](/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-2-environment-deployment.md)
+      + [使用指导](/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-3-usage-guide.md)
+      + [最佳实践](/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-4-best-practices.md)
+      + [常见问题处理](/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-5-faqs.md)
+    + X-Tuner：参数调优与诊断
+      + [概述](/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-1-x-tuner-overview.md)
+      + [使用准备](/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-2-preparations.md)
+      + [使用示例](/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-3-examples.md)
+      + [获取帮助](/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-4-obtaining-help-information.md)
+      + [命令参考](/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-5-command-reference.md)
+      + [常见问题处理](/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-6-Troubleshooting.md)
+    + SQLdiag：慢SQL发现
+      + [概述](/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-1-overview.md)
+      + [使用指导](/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-2-usage-guide.md)
+      + [获取帮助](/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-3-obtaining-help-information.md)
+      + [命令参考](/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-4-command-reference.md)
+      + [常见问题处理](/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-5-troubleshooting.md)
+    + Anomaly-detection：数据库指标采集、预测与异常监控
+      + [概述](/developer-guide/AI-features/5-a-detection-status-monitoring/5-1-overview.md)
+      + [使用准备](/developer-guide/AI-features/5-a-detection-status-monitoring/5-2-preparations.md)
+      + [添加监控参数](/developer-guide/AI-features/5-a-detection-status-monitoring/5-3-adding-monitoring-parameters.md)
+      + [获取帮助](/developer-guide/AI-features/5-a-detection-status-monitoring/5-4-obtaining-help-information.md)
+      + [使用示例](/developer-guide/AI-features/5-a-detection-status-monitoring/5-6-examples.md)
+      + [命令参考](/developer-guide/AI-features/5-a-detection-status-monitoring/5-5-command-reference.md)
+      + [AI_SERVER](/developer-guide/AI-features/5-a-detection-status-monitoring/5-7-ai-server.md)
+      + [AI_MANAGER](/developer-guide/AI-features/5-a-detection-status-monitoring/5-8-ai-manager.md)
+    + Index-advisor：索引推荐
+      + [单query索引推荐](/developer-guide/AI-features/6-index-advisor-index-recommendation/6-1-single-query-index-recommendation.md)
+      + [虚拟索引](/developer-guide/AI-features/6-index-advisor-index-recommendation/6-2-virtual-index.md)
+      + [workload级别索引推荐](/developer-guide/AI-features/6-index-advisor-index-recommendation/6-3-workload-level-index-recommendation.md)
+    + DeepSQL：库内AI算法
+      + [概述](/developer-guide/AI-features/7-deepsql/7-1-overview.md)
+      + [环境部署](/developer-guide/AI-features/7-deepsql/7-2-environment-deployment.md)
+      + [使用指导](/developer-guide/AI-features/7-deepsql/7-3-usage-guide.md)
+      + [最佳实践](/developer-guide/AI-features/7-deepsql/7-4-best-practices.md)
+      + [常见问题处理](/developer-guide/AI-features/7-deepsql/7-5-troubleshooting.md)
+    + DB4AI：数据库原生AI引擎
+      + [概述](/developer-guide/AI-features/8-db4ai/8-1-overview.md)
+      + [DB4AI-Snapshots数据版本管理](/developer-guide/AI-features/8-db4ai/8-2-db4ai-snapshots-for-data-version-management.md)
+      + [DB4AI-Query：模型训练和推断](/developer-guide/AI-features/8-db4ai/8-3-db4ai-query-for-model-training-and-prediction.md)
+      + [plpython-fenced模式](/developer-guide/AI-features/8-db4ai/8-4-pl-python-fenced-mode.md)
+  + 资源负载管理
+    + [资源负载管理概述](/developer-guide/resource-load-management/resource-load-management-overview.md)
+    + 资源管理准备
+      + [资源规划](/developer-guide/resource-load-management/resource-management-preparation/planning-resources.md)
+      + [启动资源负载管理功能](/developer-guide/resource-load-management/resource-management-preparation/enabling-resource-load-management.md)
+      + [设置控制组](/developer-guide/resource-load-management/resource-management-preparation/setting-a-cgroup.md)
+      + [创建资源池](/developer-guide/resource-load-management/resource-management-preparation/creating-a-resource-pool.md)
++ 参考指南
+  + 系统表及系统视图
+    + [系统表和系统视图概述](/reference-guide/system-catalogs-and-system-views/overview-of-system-catalogs-and-system-views.md)
+    + 系统表
+      + [GS_AUDITING_POLICY](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY.md)
+      + [GS_AUDITING_POLICY_ACCESS](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY_ACCESS.md)
+      + [GS_AUDITING_POLICY_FILTERS](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY_FILTERS.md)
+      + [GS_AUDITING_POLICY_PRIVILEGES](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY_PRIVILEGES.md)
+      + [GS_CLIENT_GLOBAL_KEYS](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_CLIENT_GLOBAL_KEYS.md)
+      + [GS_CLIENT_GLOBAL_KEYS_ARGS](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_CLIENT_GLOBAL_KEYS_ARGS.md)
+      + [GS_COLUMN_KEYS](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_COLUMN_KEYS.md)
+      + [GS_COLUMN_KEYS_ARGS](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_COLUMN_KEYS_ARGS.md)
+      + [GS_ENCRYPTED_COLUMNS](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_ENCRYPTED_COLUMNS.md)
+      + [GS_ENCRYPTED_PROC](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_ENCRYPTED_PROC.md)
+      + [GS_GLOBAL_CHAIN](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_GLOBAL_CHAIN.md)
+      + [GS_MASKING_POLICY](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MASKING_POLICY.md)
+      + [GS_MASKING_POLICY_ACTIONS](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MASKING_POLICY_ACTIONS.md)
+      + [GS_MASKING_POLICY_FILTERS](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MASKING_POLICY_FILTERS.md)
+      + [GS_MATVIEW](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MATVIEW.md)
+      + [GS_MATVIEW_DEPENDENCY](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MATVIEW_DEPENDENCY.md)
+      + [GS_OPT_MODEL](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_OPT_MODEL.md)
+      + [GS_POLICY_LABEL](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_POLICY_LABEL.md)
+      + [GS_RECYCLEBIN](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_RECYCLEBIN.md)
+      + [GS_TXN_SNAPSHOT](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_TXN_SNAPSHOT.md)
+      + [GS_WLM_INSTANCE_HISTORY](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_INSTANCE_HISTORY.md)
+      + [GS_WLM_OPERATOR_INFO](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_OPERATOR_INFO.md)
+      + [GS_WLM_PLAN_ENCODING_TABLE](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_PLAN_ENCODING_TABLE.md)
+      + [GS_WLM_PLAN_OPERATOR_INFO](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_PLAN_OPERATOR_INFO.md)
+      + [GS_WLM_EC_OPERATOR_INFO](/reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_EC_OPERATOR_INFO.md)
+      + [PG_AGGREGATE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AGGREGATE.md)
+      + [PG_AM](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AM.md)
+      + [PG_AMOP](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AMOP.md)
+      + [PG_AMPROC](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AMPROC.md)
+      + [PG_APP_WORKLOADGROUP_MAPPING](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_APP_WORKLOADGROUP_MAPPING.md)
+      + [PG_ATTRDEF](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_ATTRDEF.md)
+      + [PG_ATTRIBUTE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_ATTRIBUTE.md)
+      + [PG_AUTHID](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AUTHID.md)
+      + [PG_AUTH_HISTORY](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AUTH_HISTORY.md)
+      + [PG_AUTH_MEMBERS](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AUTH_MEMBERS.md)
+      + [PG_CAST](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CAST.md)
+      + [PG_CLASS](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CLASS.md)
+      + [PG_COLLATION](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_COLLATION.md)
+      + [PG_CONSTRAINT](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CONSTRAINT.md)
+      + [PG_CONVERSION](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CONVERSION.md)
+      + [PG_DATABASE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DATABASE.md)
+      + [PG_DB_ROLE_SETTING](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DB_ROLE_SETTING.md)
+      + [PG_DEFAULT_ACL](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DEFAULT_ACL.md)
+      + [PG_DEPEND](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DEPEND.md)
+      + [PG_DESCRIPTION](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DESCRIPTION.md)
+      + [PG_DIRECTORY](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DIRECTORY.md)
+      + [PG_ENUM](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_ENUM.md)
+      + [PG_EXTENSION](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_EXTENSION.md)
+      + [PG_EXTENSION_DATA_SOURCE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_EXTENSION_DATA_SOURCE.md)
+      + [PG_FOREIGN_DATA_WRAPPER](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_FOREIGN_DATA_WRAPPER.md)
+      + [PG_FOREIGN_SERVER](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_FOREIGN_SERVER.md)
+      + [PG_FOREIGN_TABLE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_FOREIGN_TABLE.md)
+      + [PG_INDEX](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_INDEX.md)
+      + [PG_INHERITS](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_INHERITS.md)
+      + [PG_JOB](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_JOB.md)
+      + [PG_JOB_PROC](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_JOB_PROC.md)
+      + [PG_LANGUAGE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_LANGUAGE.md)
+      + [PG_LARGEOBJECT](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_LARGEOBJECT.md)
+      + [PG_LARGEOBJECT_METADATA](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_LARGEOBJECT_METADATA.md)
+      + [PG_NAMESPACE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_NAMESPACE.md)
+      + [PG_OBJECT](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OBJECT.md)
+      + [PG_OPCLASS](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OPCLASS.md)
+      + [PG_OPERATOR](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OPERATOR.md)
+      + [PG_OPFAMILY](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OPFAMILY.md)
+      + [PG_PARTITION](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_PARTITION.md)
+      + [PG_PLTEMPLATE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_PLTEMPLATE.md)
+      + [PG_PROC](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_PROC.md)
+      + [PG_RANGE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_RANGE.md)
+      + [PG_RESOURCE_POOL](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_RESOURCE_POOL.md)
+      + [PG_REWRITE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_REWRITE.md)
+      + [PG_RLSPOLICY](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_RLSPOLICY.md)
+      + [PG_SECLABEL](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SECLABEL.md)
+      + [PG_SHDEPEND](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SHDEPEND.md)
+      + [PG_SHDESCRIPTION](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SHDESCRIPTION.md)
+      + [PG_SHSECLABEL](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SHSECLABEL.md)
+      + [PG_STATISTIC](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_STATISTIC.md)
+      + [PG_STATISTIC_EXT](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_STATISTIC_EXT.md)
+      + [PG_SYNONYM](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SYNONYM.md)
+      + [PG_TABLESPACE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TABLESPACE.md)
+      + [PG_TRIGGER](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TRIGGER.md)
+      + [PG_TS_CONFIG](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_CONFIG.md)
+      + [PG_TS_CONFIG_MAP](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_CONFIG_MAP.md)
+      + [PG_TS_DICT](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_DICT.md)
+      + [PG_TS_PARSER](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_PARSER.md)
+      + [PG_TS_TEMPLATE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_TEMPLATE.md)
+      + [PG_TYPE](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TYPE.md)
+      + [PG_USER_MAPPING](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_USER_MAPPING.md)
+      + [PG_USER_STATUS](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_USER_STATUS.md)
+      + [PG_WORKLOAD_GROUP](/reference-guide/system-catalogs-and-system-views/system-catalogs/PG_WORKLOAD_GROUP.md)
+      + [PLAN_TABLE_DATA](/reference-guide/system-catalogs-and-system-views/system-catalogs/PLAN_TABLE_DATA.md)
+      + [STATEMENT_HISTORY](/reference-guide/system-catalogs-and-system-views/system-catalogs/STATEMENT_HISTORY.md)
+    + 系统视图
+      + [GET_GLOBAL_PREPARED_XACTS（废弃）](/reference-guide/system-catalogs-and-system-views/system-views/GET_GLOBAL_PREPARED_XACTS.md)
+      + [GS_AUDITING](/reference-guide/system-catalogs-and-system-views/system-views/GS_AUDITING.md)
+      + [GS_AUDITING_ACCESS](/reference-guide/system-catalogs-and-system-views/system-views/GS_AUDITING_ACCESS.md)
+      + [GS_AUDITING_PRIVILEGE](/reference-guide/system-catalogs-and-system-views/system-views/GS_AUDITING_PRIVILEGE.md)
+      + [GS_CLUSTER_RESOURCE_INFO](/reference-guide/system-catalogs-and-system-views/system-views/GS_CLUSTER_RESOURCE_INFO.md)
+      + [GS_INSTANCE_TIME](/reference-guide/system-catalogs-and-system-views/system-views/GS_INSTANCE_TIME.md)
+      + [GS_LABELS](/reference-guide/system-catalogs-and-system-views/system-views/GS_LABELS.md)
+      + [GS_MASKING](/reference-guide/system-catalogs-and-system-views/system-views/GS_MASKING.md)
+      + [GS_MATVIEWS](/reference-guide/system-catalogs-and-system-views/system-views/GS_MATVIEWS.md)
+      + [GS_SESSION_MEMORY](/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY.md)
+      + [GS_SESSION_CPU_STATISTICS](/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_CPU_STATISTICS.md)
+      + [GS_SESSION_MEMORY_CONTEXT](/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY_CONTEXT.md)
+      + [GS_SESSION_MEMORY_DETAIL](/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY_DETAIL.md)
+      + [GS_SESSION_MEMORY_STATISTICS](/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY_STATISTICS.md)
+      + [GS_SQL_COUNT](/reference-guide/system-catalogs-and-system-views/system-views/GS_SQL_COUNT.md)
+      + [GS_WLM_CGROUP_INFO](/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_CGROUP_INFO.md)
+      + [GS_WLM_PLAN_OPERATOR_HISTORY](/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_PLAN_OPERATOR_HISTORY.md)
+      + [GS_WLM_REBUILD_USER_RESOURCE_POOL](/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_REBUILD_USER_RESOURCE_POOL.md)
+      + [GS_WLM_RESOURCE_POOL](/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_RESOURCE_POOL.md)
+      + [GS_WLM_USER_INFO](/reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_USER_INFO.md)
+      + [GS_STAT_SESSION_CU](/reference-guide/system-catalogs-and-system-views/system-views/GS_STAT_SESSION_CU.md)
+      + [GS_TOTAL_MEMORY_DETAIL](/reference-guide/system-catalogs-and-system-views/system-views/GS_TOTAL_MEMORY_DETAIL.md)
+      + [MPP_TABLES](/reference-guide/system-catalogs-and-system-views/system-views/MPP_TABLES.md)
+      + [PG_AVAILABLE_EXTENSION_VERSIONS](/reference-guide/system-catalogs-and-system-views/system-views/PG_AVAILABLE_EXTENSION_VERSIONS.md)
+      + [PG_AVAILABLE_EXTENSIONS](/reference-guide/system-catalogs-and-system-views/system-views/PG_AVAILABLE_EXTENSIONS.md)
+      + [PG_COMM_DELAY](/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_DELAY.md)
+      + [PG_COMM_RECV_STREAM](/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_RECV_STREAM.md)
+      + [PG_COMM_SEND_STREAM](/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_SEND_STREAM.md)
+      + [PG_COMM_STATUS](/reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_STATUS.md)
+      + [PG_CONTROL_GROUP_CONFIG](/reference-guide/system-catalogs-and-system-views/system-views/PG_CONTROL_GROUP_CONFIG.md)
+      + [PG_CURSORS](/reference-guide/system-catalogs-and-system-views/system-views/PG_CURSORS.md)
+      + [PG_EXT_STATS](/reference-guide/system-catalogs-and-system-views/system-views/PG_EXT_STATS.md)
+      + [PG_GET_INVALID_BACKENDS](/reference-guide/system-catalogs-and-system-views/system-views/PG_GET_INVALID_BACKENDS.md)
+      + [PG_GET_SENDERS_CATCHUP_TIME](/reference-guide/system-catalogs-and-system-views/system-views/PG_GET_SENDERS_CATCHUP_TIME.md)
+      + [PG_GROUP](/reference-guide/system-catalogs-and-system-views/system-views/PG_GROUP.md)
+      + [PG_GTT_RELSTATS](/reference-guide/system-catalogs-and-system-views/system-views/PG_GTT_RELSTATS.md)
+      + [PG_GTT_STATS](/reference-guide/system-catalogs-and-system-views/system-views/PG_GTT_STATS.md)
+      + [PG_GTT_ATTACHED_PIDS](/reference-guide/system-catalogs-and-system-views/system-views/PG_GTT_ATTACHED_PIDS.md)
+      + [PG_INDEXES](/reference-guide/system-catalogs-and-system-views/system-views/PG_INDEXES.md)
+      + [PG_LOCKS](/reference-guide/system-catalogs-and-system-views/system-views/PG_LOCKS.md)
+      + [PG_NODE_ENV](/reference-guide/system-catalogs-and-system-views/system-views/PG_NODE_ENV.md)
+      + [PG_OS_THREADS](/reference-guide/system-catalogs-and-system-views/system-views/PG_OS_THREADS.md)
+      + [PG_PREPARED_STATEMENTS](/reference-guide/system-catalogs-and-system-views/system-views/PG_PREPARED_STATEMENTS.md)
+      + [PG_PREPARED_XACTS](/reference-guide/system-catalogs-and-system-views/system-views/PG_PREPARED_XACTS.md)
+      + [PG_REPLICATION_SLOTS](/reference-guide/system-catalogs-and-system-views/system-views/PG_REPLICATION_SLOTS.md)
+      + [PG_RLSPOLICIES](/reference-guide/system-catalogs-and-system-views/system-views/PG_RLSPOLICIES.md)
+      + [PG_ROLES](/reference-guide/system-catalogs-and-system-views/system-views/PG_ROLES.md)
+      + [PG_RULES](/reference-guide/system-catalogs-and-system-views/system-views/PG_RULES.md)
+      + [PG_SECLABELS](/reference-guide/system-catalogs-and-system-views/system-views/PG_SECLABELS.md)
+      + [PG_SETTINGS](/reference-guide/system-catalogs-and-system-views/system-views/PG_SETTINGS.md)
+      + [PG_SHADOW](/reference-guide/system-catalogs-and-system-views/system-views/PG_SHADOW.md)
+      + [PG_STATS](/reference-guide/system-catalogs-and-system-views/system-views/PG_STATS.md)
+      + [PG_STAT_ACTIVITY](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_ACTIVITY.md)
+      + [PG_STAT_ALL_INDEXES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_ALL_INDEXES.md)
+      + [PG_STAT_ALL_TABLES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_ALL_TABLES.md)
+      + [PG_STAT_BAD_BLOCK](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_BAD_BLOCK.md)
+      + [PG_STAT_BGWRITER](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_BGWRITER.md)
+      + [PG_STAT_DATABASE](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_DATABASE.md)
+      + [PG_STAT_DATABASE_CONFLICTS](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_DATABASE_CONFLICTS.md)
+      + [PG_STAT_USER_FUNCTIONS](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_USER_FUNCTIONS.md)
+      + [PG_STAT_USER_INDEXES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_USER_INDEXES.md)
+      + [PG_STAT_USER_TABLES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_USER_TABLES.md)
+      + [PG_STAT_REPLICATION](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_REPLICATION.md)
+      + [PG_STAT_SYS_INDEXES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_SYS_INDEXES.md)
+      + [PG_STAT_SYS_TABLES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_SYS_TABLES.md)
+      + [PG_STAT_XACT_ALL_TABLES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_ALL_TABLES.md)
+      + [PG_STAT_XACT_SYS_TABLES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_SYS_TABLES.md)
+      + [PG_STAT_XACT_USER_FUNCTIONS](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_USER_FUNCTIONS.md)
+      + [PG_STAT_XACT_USER_TABLES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_USER_TABLES.md)
+      + [PG_STATIO_ALL_INDEXES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_ALL_INDEXES.md)
+      + [PG_STATIO_ALL_SEQUENCES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_ALL_SEQUENCES.md)
+      + [PG_STATIO_ALL_TABLES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_ALL_TABLES.md)
+      + [PG_STATIO_SYS_INDEXES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_SYS_INDEXES.md)
+      + [PG_STATIO_SYS_SEQUENCES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_SYS_SEQUENCES.md)
+      + [PG_STATIO_SYS_TABLES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_SYS_TABLES.md)
+      + [PG_STATIO_USER_INDEXES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_USER_INDEXES.md)
+      + [PG_STATIO_USER_SEQUENCES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_USER_SEQUENCES.md)
+      + [PG_STATIO_USER_TABLES](/reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_USER_TABLES.md)
+      + [PG_TABLES](/reference-guide/system-catalogs-and-system-views/system-views/PG_TABLES.md)
+      + [PG_TDE_INFO](/reference-guide/system-catalogs-and-system-views/system-views/PG_TDE_INFO.md)
+      + [PG_THREAD_WAIT_STATUS](/reference-guide/system-catalogs-and-system-views/system-views/PG_THREAD_WAIT_STATUS.md)
+      + [PG_TIMEZONE_ABBREVS](/reference-guide/system-catalogs-and-system-views/system-views/PG_TIMEZONE_ABBREVS.md)
+      + [PG_TIMEZONE_NAMES](/reference-guide/system-catalogs-and-system-views/system-views/PG_TIMEZONE_NAMES.md)
+      + [PG_TOTAL_MEMORY_DETAIL](/reference-guide/system-catalogs-and-system-views/system-views/PG_TOTAL_MEMORY_DETAIL.md)
+      + [PG_TOTAL_USER_RESOURCE_INFO](/reference-guide/system-catalogs-and-system-views/system-views/PG_TOTAL_USER_RESOURCE_INFO.md)
+      + [PG_TOTAL_USER_RESOURCE_INFO_OID](/reference-guide/system-catalogs-and-system-views/system-views/PG_TOTAL_USER_RESOURCE_INFO_OID.md)
+      + [PG_USER](/reference-guide/system-catalogs-and-system-views/system-views/PG_USER.md)
+      + [PG_USER_MAPPINGS](/reference-guide/system-catalogs-and-system-views/system-views/PG_USER_MAPPINGS.md)
+      + [PG_VARIABLE_INFO](/reference-guide/system-catalogs-and-system-views/system-views/PG_VARIABLE_INFO.md)
+      + [PG_VIEWS](/reference-guide/system-catalogs-and-system-views/system-views/PG_VIEWS.md)
+      + [PLAN_TABLE](/reference-guide/system-catalogs-and-system-views/system-views/PLAN_TABLE.md)
+      + [GS_FILE_STAT](/reference-guide/system-catalogs-and-system-views/system-views/GS_FILE_STAT.md)
+      + [GS_OS_RUN_INFO](/reference-guide/system-catalogs-and-system-views/system-views/GS_OS_RUN_INFO.md)
+      + [GS_REDO_STAT](/reference-guide/system-catalogs-and-system-views/system-views/GS_REDO_STAT.md)
+      + [GS_SESSION_STAT](/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_STAT.md)
+      + [GS_SESSION_TIME](/reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_TIME.md)
+      + [GS_THREAD_MEMORY_CONTEXT](/reference-guide/system-catalogs-and-system-views/system-views/GS_THREAD_MEMORY_CONTEXT.md)
+  + 系统函数
+    + [逻辑操作符](/reference-guide/functions-and-operators/1-logical-operators.md)
+    + [比较操作符](/reference-guide/functions-and-operators/2-comparison-operators.md)
+    + [字符处理函数和操作符](/reference-guide/functions-and-operators/3-character-processing-functions-and-operators.md)
+    + [二进制字符串函数和操作符](/reference-guide/functions-and-operators/4-binary-string-functions-and-operators.md)
+    + [位串函数和操作符](/reference-guide/functions-and-operators/5-bit-string-functions-and-operators.md)
+    + [模式匹配操作符](/reference-guide/functions-and-operators/6-mode-matching-operators.md)
+    + [数字操作函数和操作符](/reference-guide/functions-and-operators/7-mathematical-functions-and-operators.md)
+    + [时间和日期处理函数和操作符](/reference-guide/functions-and-operators/8-date-and-time-processing-functions-and-operators.md)
+    + [类型转换函数](/reference-guide/functions-and-operators/9-type-conversion-functions.md)
+    + [几何函数和操作符](/reference-guide/functions-and-operators/10-geometric-functions-and-operators.md)
+    + [网络地址函数和操作符](/reference-guide/functions-and-operators/11-network-address-functions-and-operators.md)
+    + [文本检索函数和操作符](/reference-guide/functions-and-operators/12-text-search-functions-and-operators.md)
+    + [JSON/JSONB函数和操作符](/reference-guide/functions-and-operators/13-json-functions.md)
+    + [HLL函数和操作符](/reference-guide/functions-and-operators/13.1-hll-functions-and-operators.md)
+    + [SEQUENCE函数](/reference-guide/functions-and-operators/14-sequence-functions.md)
+    + [数组函数和操作符](/reference-guide/functions-and-operators/15-array-functions-and-operators.md)
+    + [范围函数和操作符](/reference-guide/functions-and-operators/16-range-functions-and-operators.md)
+    + [聚集函数](/reference-guide/functions-and-operators/17-aggregate-functions.md)
+    + [窗口函数](/reference-guide/functions-and-operators/18-window-functions.md)
+    + [安全函数](/reference-guide/functions-and-operators/19-security-functions.md)
+    + [账本数据库的函数](/reference-guide/functions-and-operators/20.1-ledger-database-functions.md)
+    + [密态等值的函数](/reference-guide/functions-and-operators/20-encrypted-equality-functions.md)
+    + [返回集合的函数](/reference-guide/functions-and-operators/21-set-returning-functions.md)
+    + [条件表达式函数](/reference-guide/functions-and-operators/22-conditional-expressions-functions.md)
+    + [系统信息函数](/reference-guide/functions-and-operators/23-system-information-functions.md)
+    + 系统管理函数
+      + [配置设置函数](/reference-guide/functions-and-operators/24-system-management-functions/1-configuration-settings-functions.md)
+      + [通用文件访问函数](/reference-guide/functions-and-operators/24-system-management-functions/2-universal-file-access-functions.md)
+      + [服务器信号函数](/reference-guide/functions-and-operators/24-system-management-functions/3-server-signal-functions.md)
+      + [备份恢复控制函数](/reference-guide/functions-and-operators/24-system-management-functions/4-backup-and-restoration-control-functions.md)
+      + [快照同步函数](/reference-guide/functions-and-operators/24-system-management-functions/5-snapshot-synchronization-functions.md)
+      + [数据库对象函数](/reference-guide/functions-and-operators/24-system-management-functions/6-database-object-functions.md)
+      + [咨询锁函数](/reference-guide/functions-and-operators/24-system-management-functions/7-advisory-lock-functions.md)
+      + [逻辑复制函数](/reference-guide/functions-and-operators/24-system-management-functions/8-logical-replication-functions.md)
+      + [段页式存储函数](/reference-guide/functions-and-operators/24-system-management-functions/9.1-segment-page-storage-functions.md)
+      + [其它函数](/reference-guide/functions-and-operators/24-system-management-functions/9-other-functions.md)
+      + [Undo系统函数](/reference-guide/functions-and-operators/24-system-management-functions/10-undo-system-functions.md)
+    + [统计信息函数](/reference-guide/functions-and-operators/25-statistics-information-functions.md)
+    + [触发器函数](/reference-guide/functions-and-operators/26-trigger-functions.md)
+    + [HashFunc函数](/reference-guide/functions-and-operators/27.1-hash-function.md)
+    + [提示信息函数](/reference-guide/functions-and-operators/27.2-prompt-message-function.md)
+    + [全局临时表函数](/reference-guide/functions-and-operators/27-global-temporary-table-functions.md)
+    + [故障注入系统函数](/reference-guide/functions-and-operators/28.1-fault-injection-system-function.md)
+    + [AI特性函数](/reference-guide/functions-and-operators/28-ai-feature-functions.md)
+    + [动态数据脱敏函数](/reference-guide/functions-and-operators/29.1-dynamic-data-masking-functions.md)
+    + [其他系统函数](/reference-guide/functions-and-operators/29-other-system-functions.md)
+    + [内部函数](/reference-guide/functions-and-operators/30-internal-functions.md)
+    + [废弃函数](/reference-guide/functions-and-operators/31-obsolete-functions.md)
+  + 支持的数据类型
+    + [数值类型](/reference-guide/supported-data-types/1-numeric-data-types.md)
+    + [货币类型](/reference-guide/supported-data-types/2-monetary.md)
+    + [布尔类型](/reference-guide/supported-data-types/3-boolean-data-types.md)
+    + [枚举类型](/reference-guide/supported-data-types/4.1-enumerated-types.md)
+    + [字符类型](/reference-guide/supported-data-types/4-character-data-types.md)
+    + [二进制类型](/reference-guide/supported-data-types/5-binary-data-types.md)
+    + [日期/时间类型](/reference-guide/supported-data-types/6-date-time-types.md)
+    + [几何类型](/reference-guide/supported-data-types/7-geometric.md)
+    + [网络地址类型](/reference-guide/supported-data-types/8-network-address.md)
+    + [位串类型](/reference-guide/supported-data-types/9-bit-string-types.md)
+    + [文本搜索类型](/reference-guide/supported-data-types/10-text-search-types.md)
+    + [UUID类型](/reference-guide/supported-data-types/11-uuid-type.md)
+    + [JSON/JSONB类型](/reference-guide/supported-data-types/12-json-types.md)
+    + [HLL数据类型](/reference-guide/supported-data-types/13-HLL.md)
+    + [数组类型](/reference-guide/supported-data-types/13.0-array-types.md)
+    + [范围类型](/reference-guide/supported-data-types/13.1-range.md)
+    + [对象标识符类型](/reference-guide/supported-data-types/14-object-identifier-types.md)
+    + [伪类型](/reference-guide/supported-data-types/15-pseudo-types.md)
+    + [列存表支持的数据类型](/reference-guide/supported-data-types/16-data-types-supported-by-column-store-tables.md)
+    + [XML类型](/reference-guide/supported-data-types/17-xml-type.md)
+    + [账本数据库使用的数据类型](/reference-guide/supported-data-types/18-data-type-used-by-the-ledger-database.md)
+  + SQL语法
+    + [ABORT](/reference-guide/sql-syntax/1-ABORT.md)
+    + [ALTER AGGREGATE](/reference-guide/sql-syntax/1.1-ALTER-AGGREGATE.md)
+    + [ALTER AUDIT POLICY](/reference-guide/sql-syntax/1.2-ALTER-AUDIT-POLICY.md)
+    + [ALTER DATABASE](/reference-guide/sql-syntax/2-ALTER-DATABASE.md)
+    + [ALTER DATA SOURCE](/reference-guide/sql-syntax/3-ALTER-DATA-SOURCE.md)
+    + [ALTER DEFAULT PRIVILEGES](/reference-guide/sql-syntax/4-ALTER-DEFAULT-PRIVILEGES.md)
+    + [ALTER DIRECTORY](/reference-guide/sql-syntax/5-ALTER-DIRECTORY.md)
+    + [ALTER EXTENSION](/reference-guide/sql-syntax/5.1-ALTER-EXTENSION.md)
+    + [ALTER FOREIGN TABLE](/reference-guide/sql-syntax/6-ALTER-FOREIGN-TABLE.md)
+    + [ALTER FUNCTION](/reference-guide/sql-syntax/7-ALTER-FUNCTION.md)
+    + [ALTER GROUP](/reference-guide/sql-syntax/8-ALTER-GROUP.md)
+    + [ALTER INDEX](/reference-guide/sql-syntax/9-ALTER-INDEX.md)
+    + [ALTER LANGUAGE](/reference-guide/sql-syntax/9.1-ALTER-LANGUAGE.md)
+    + [ALTER LARGE OBJECT](/reference-guide/sql-syntax/10-ALTER-LARGE-OBJECT.md)
+    + [ALTER MASKING POLICY](/reference-guide/sql-syntax/10.1-ALTER-MASKING-POLICY.md)
+    + [ALTER MATERIALIZED VIEW](/reference-guide/sql-syntax/11-ALTER-MATERIALIZED-VIEW.md)
+    + [ALTER OPERATOR](/reference-guide/sql-syntax/11.1-ALTER-OPERATOR.md)
+    + [ALTER RESOURCE LABEL](/reference-guide/sql-syntax/11.2-ALTER-RESOURCE-LABEL.md)
+    + [ALTER RESOURCE POOL](/reference-guide/sql-syntax/11.3-ALTER-RESOURCE-POOL.md)
+    + [ALTER ROLE](/reference-guide/sql-syntax/12-ALTER-ROLE.md)
+    + [ALTER ROW LEVEL SECURITY POLICY](/reference-guide/sql-syntax/13-ALTER-ROW-LEVEL-SECURITY-POLICY.md)
+    + [ALTER RULE](/reference-guide/sql-syntax/14-ALTER-RULE.md)
+    + [ALTER SCHEMA](/reference-guide/sql-syntax/15-ALTER-SCHEMA.md)
+    + [ALTER SEQUENCE](/reference-guide/sql-syntax/16-ALTER-SEQUENCE.md)
+    + [ALTER SERVER](/reference-guide/sql-syntax/17-ALTER-SERVER.md)
+    + [ALTER SESSION](/reference-guide/sql-syntax/18-ALTER-SESSION.md)
+    + [ALTER SYNONYM](/reference-guide/sql-syntax/19-ALTER-SYNONYM.md)
+    + [ALTER SYSTEM KILL SESSION](/reference-guide/sql-syntax/20-ALTER-SYSTEM-KILL-SESSION.md)
+    + [ALTER SYSTEM SET](/reference-guide/sql-syntax/21-ALTER-SYSTEM-SET.md)
+    + [ALTER TABLE](/reference-guide/sql-syntax/22-ALTER-TABLE.md)
+    + [ALTER TABLE PARTITION](/reference-guide/sql-syntax/23-ALTER-TABLE-PARTITION.md)
+    + [ALTER TABLE SUBPARTITION](/reference-guide/sql-syntax/23.1-ALTER-TABLE-SUBPARTITION.md)
+    + [ALTER TABLESPACE](/reference-guide/sql-syntax/24-ALTER-TABLESPACE.md)
+    + [ALTER TEXT SEARCH CONFIGURATION](/reference-guide/sql-syntax/25-ALTER-TEXT-SEARCH-CONFIGURATION.md)
+    + [ALTER TEXT SEARCH DICTIONARY](/reference-guide/sql-syntax/26-ALTER-TEXT-SEARCH-DICTIONARY.md)
+    + [ALTER TRIGGER](/reference-guide/sql-syntax/27-ALTER-TRIGGER.md)
+    + [ALTER TYPE](/reference-guide/sql-syntax/28-ALTER-TYPE.md)
+    + [ALTER USER](/reference-guide/sql-syntax/29-ALTER-USER.md)
+    + [ALTER USER MAPPING](/reference-guide/sql-syntax/30-ALTER-USER-MAPPING.md)
+    + [ALTER VIEW](/reference-guide/sql-syntax/31-ALTER-VIEW.md)
+    + [ANALYZE | ANALYSE](/reference-guide/sql-syntax/32-ANALYZE-ANALYSE.md)
+    + [BEGIN](/reference-guide/sql-syntax/33-BEGIN.md)
+    + [CALL](/reference-guide/sql-syntax/34-CALL.md)
+    + [CHECKPOINT](/reference-guide/sql-syntax/35-CHECKPOINT.md)
+    + [CLEAN CONNECTION](/reference-guide/sql-syntax/35.1-CLEAN-CONNECTION.md)
+    + [CLOSE](/reference-guide/sql-syntax/36-CLOSE.md)
+    + [CLUSTER](/reference-guide/sql-syntax/37-CLUSTER.md)
+    + [COMMENT](/reference-guide/sql-syntax/38-COMMENT.md)
+    + [COMMIT | END](/reference-guide/sql-syntax/39-COMMIT-END.md)
+    + [COMMIT PREPARED](/reference-guide/sql-syntax/40-COMMIT-PREPARED.md)
+    + [CONNECT BY](/reference-guide/sql-syntax/139-CONNECT-BY.md)
+    + [COPY](/reference-guide/sql-syntax/41-COPY.md)
+    + [CREATE AGGREGATE](/reference-guide/sql-syntax/41.1-CREATE-AGGREGATE.md)
+    + [CREATE AUDIT POLICY](/reference-guide/sql-syntax/41.2-CREATE-AUDIT-POLICY.md)
+    + [CREATE CAST](/reference-guide/sql-syntax/41.3-CREATE-CAST.md)
+    + [CREATE CLIENT MASTER KEY](/reference-guide/sql-syntax/42-CREATE-CLIENT-MASTER-KEY.md)
+    + [CREATE COLUMN ENCRYPTION KEY](/reference-guide/sql-syntax/43-CREATE-COLUMN-ENCRYPTION-KEY.md)
+    + [CREATE DATABASE](/reference-guide/sql-syntax/44-CREATE-DATABASE.md)
+    + [CREATE DATA SOURCE](/reference-guide/sql-syntax/45-CREATE-DATA-SOURCE.md)
+    + [CREATE DIRECTORY](/reference-guide/sql-syntax/46-CREATE-DIRECTORY.md)
+    + [CREATE EXTENSION](/reference-guide/sql-syntax/46.1-CREATE-EXTENSION.md)
+    + [CREATE FOREIGN TABLE](/reference-guide/sql-syntax/47-CREATE-FOREIGN-TABLE.md)
+    + [CREATE FUNCTION](/reference-guide/sql-syntax/48-CREATE-FUNCTION.md)
+    + [CREATE GROUP](/reference-guide/sql-syntax/49-CREATE-GROUP.md)
+    + [CREATE INCREMENTAL MATERIALIZED VIEW](/reference-guide/sql-syntax/49.1-CREATE-INCREMENTAL-MATERIALIZED-VIEW.md)
+    + [CREATE INDEX](/reference-guide/sql-syntax/50-CREATE-INDEX.md)
+    + [CREATE LANGUAGE](/reference-guide/sql-syntax/50.1-CREATE-LANGUAGE.md)
+    + [CREATE MASKING POLICY](/reference-guide/sql-syntax/50.2-CREATE-MASKING-POLICY.md)
+    + [CREATE MATERIALIZED VIEW](/reference-guide/sql-syntax/51-CREATE-MATERIALIZED-VIEW.md)
+    + [CREATE MODEL](/reference-guide/sql-syntax/50.3-CREATE-MODEL.md)
+    + [CREATE OPERATOR](/reference-guide/sql-syntax/51.1-CREATE-OPERATOR.md)
+    + [CREATE PACKAGE](/reference-guide/sql-syntax/51.2-CREATE-PACKAGE.md)
+    + [CREATE ROW LEVEL SECURITY POLICY](/reference-guide/sql-syntax/52-CREATE-ROW-LEVEL-SECURITY-POLICY.md)
+    + [CREATE PROCEDURE](/reference-guide/sql-syntax/53-CREATE-PROCEDURE.md)
+    + [CREATE RESOURCE LABEL](/reference-guide/sql-syntax/53.1-CREATE-RESOURCE-LABEL.md)
+    + [CREATE RESOURCE POOL](/reference-guide/sql-syntax/53.2-CREATE-RESOURCE-POOL.md)
+    + [CREATE ROLE](/reference-guide/sql-syntax/54-CREATE-ROLE.md)
+    + [CREATE RULE](/reference-guide/sql-syntax/55-CREATE-RULE.md)
+    + [CREATE SCHEMA](/reference-guide/sql-syntax/56-CREATE-SCHEMA.md)
+    + [CREATE SEQUENCE](/reference-guide/sql-syntax/57-CREATE-SEQUENCE.md)
+    + [CREATE SERVER](/reference-guide/sql-syntax/58-CREATE-SERVER.md)
+    + [CREATE SYNONYM](/reference-guide/sql-syntax/59-CREATE-SYNONYM.md)
+    + [CREATE TABLE](/reference-guide/sql-syntax/60-CREATE-TABLE.md)
+    + [CREATE TABLE AS](/reference-guide/sql-syntax/61-CREATE-TABLE-AS.md)
+    + [CREATE TABLE PARTITION](/reference-guide/sql-syntax/62-CREATE-TABLE-PARTITION.md)
+    + [CREATE TABLE SUBPARTITION](/reference-guide/sql-syntax/62.1-CREATE-TABLE-SUBPARTITION.md)
+    + [CREATE TABLESPACE](/reference-guide/sql-syntax/63-CREATE-TABLESPACE.md)
+    + [CREATE TEXT SEARCH CONFIGURATION](/reference-guide/sql-syntax/64-CREATE-TEXT-SEARCH-CONFIGURATION.md)
+    + [CREATE TEXT SEARCH DICTIONARY](/reference-guide/sql-syntax/65-CREATE-TEXT-SEARCH-DICTIONARY.md)
+    + [CREATE TRIGGER](/reference-guide/sql-syntax/66-CREATE-TRIGGER.md)
+    + [CREATE TYPE](/reference-guide/sql-syntax/67-CREATE-TYPE.md)
+    + [CREATE USER](/reference-guide/sql-syntax/68-CREATE-USER.md)
+    + [CREATE USER MAPPING](/reference-guide/sql-syntax/69-CREATE-USER-MAPPING.md)
+    + [CREATE VIEW](/reference-guide/sql-syntax/70-CREATE-VIEW.md)
+    + [CREATE WEAK PASSWORD DICTIONARY](/reference-guide/sql-syntax/70.1-CREATE-WEAK-PASSWORD-DICTIONARY.md)
+    + [CURSOR](/reference-guide/sql-syntax/71-CURSOR.md)
+    + [DEALLOCATE](/reference-guide/sql-syntax/72-DEALLOCATE.md)
+    + [DECLARE](/reference-guide/sql-syntax/73-DECLARE.md)
+    + [DELETE](/reference-guide/sql-syntax/74-DELETE.md)
+    + [DO](/reference-guide/sql-syntax/75-DO.md)
+    + [DROP AGGREGATE](/reference-guide/sql-syntax/75.1-DROP-AGGREGATE.md)
+    + [DROP AUDIT POLICY](/reference-guide/sql-syntax/75.2-DROP-AUDIT-POLICY.md)
+    + [DROP CAST](/reference-guide/sql-syntax/75.3-DROP-CAST.md)
+    + [DROP CLIENT MASTER KEY](/reference-guide/sql-syntax/76-DROP-CLIENT-MASTER-KEY.md)
+    + [DROP COLUMN ENCRYPTION KEY](/reference-guide/sql-syntax/77-DROP-COLUMN-ENCRYPTION-KEY.md)
+    + [DROP DATABASE](/reference-guide/sql-syntax/78-DROP-DATABASE.md)
+    + [DROP DATA SOURCE](/reference-guide/sql-syntax/79-DROP-DATA-SOURCE.md)
+    + [DROP DIRECTORY](/reference-guide/sql-syntax/80-DROP-DIRECTORY.md)
+    + [DROP EXTENSION](/reference-guide/sql-syntax/80.1-DROP-EXTENSION.md)
+    + [DROP FOREIGN TABLE](/reference-guide/sql-syntax/81-DROP-FOREIGN-TABLE.md)
+    + [DROP FUNCTION](/reference-guide/sql-syntax/82-DROP-FUNCTION.md)
+    + [DROP GROUP](/reference-guide/sql-syntax/83-DROP-GROUP.md)
+    + [DROP INDEX](/reference-guide/sql-syntax/84-DROP-INDEX.md)
+    + [DROP LANGUAGE](/reference-guide/sql-syntax/84.1-DROP-LANGUAGE.md)
+    + [DROP MASKING POLICY](/reference-guide/sql-syntax/84.2-DROP-MASKING-POLICY.md)
+    + [DROP MATERIALIZED VIEW](/reference-guide/sql-syntax/85-DROP-MATERIALIZED-VIEW.md)
+    + [DROP MODEL](/reference-guide/sql-syntax/84.3-DROP-MODEL.md)
+    + [DROP OPERATOR](/reference-guide/sql-syntax/85.1-DROP-OPERATOR.md)
+    + [DROP OWNED](/reference-guide/sql-syntax/86-DROP-OWNED.md)
+    + [DROP PACKAGE](/reference-guide/sql-syntax/86.3-DROP-PACKAGE.md)
+    + [DROP PROCEDURE](/reference-guide/sql-syntax/88-DROP-PROCEDURE.md)
+    + [DROP RESOURCE LABEL](/reference-guide/sql-syntax/86.1-DROP-RESOURCE-LABEL.md)
+    + [DROP RESOURCE POOL](/reference-guide/sql-syntax/86.2-DROP-RESOURCE-POOL.md)
+    + [DROP ROW LEVEL SECURITY POLICY](/reference-guide/sql-syntax/87-DROP-ROW-LEVEL-SECURITY-POLICY.md)
+    + [DROP ROLE](/reference-guide/sql-syntax/89-DROP-ROLE.md)
+    + [DROP RULE](/reference-guide/sql-syntax/90-DROP-RULE.md)
+    + [DROP SCHEMA](/reference-guide/sql-syntax/91-DROP-SCHEMA.md)
+    + [DROP SEQUENCE](/reference-guide/sql-syntax/92-DROP-SEQUENCE.md)
+    + [DROP SERVER](/reference-guide/sql-syntax/93-DROP-SERVER.md)
+    + [DROP SYNONYM](/reference-guide/sql-syntax/94-DROP-SYNONYM.md)
+    + [DROP TABLE](/reference-guide/sql-syntax/95-DROP-TABLE.md)
+    + [DROP TABLESPACE](/reference-guide/sql-syntax/96-DROP-TABLESPACE.md)
+    + [DROP TEXT SEARCH CONFIGURATION](/reference-guide/sql-syntax/97-DROP-TEXT-SEARCH-CONFIGURATION.md)
+    + [DROP TEXT SEARCH DICTIONARY](/reference-guide/sql-syntax/98-DROP-TEXT-SEARCH-DICTIONARY.md)
+    + [DROP TRIGGER](/reference-guide/sql-syntax/99-DROP-TRIGGER.md)
+    + [DROP TYPE](/reference-guide/sql-syntax/100-DROP-TYPE.md)
+    + [DROP USER](/reference-guide/sql-syntax/101-DROP-USER.md)
+    + [DROP USER MAPPING](/reference-guide/sql-syntax/102-DROP-USER-MAPPING.md)
+    + [DROP VIEW](/reference-guide/sql-syntax/103-DROP-VIEW.md)
+    + [DROP WEAK PASSWORD DICTIONARY](/reference-guide/sql-syntax/103.1-DROP-WEAK-PASSWORD-DICTIONARY.md)
+    + [EXECUTE](/reference-guide/sql-syntax/104-EXECUTE.md)
+    + [EXECUTE DIRECT](/reference-guide/sql-syntax/104.1-EXECUTE-DIRECT.md)
+    + [EXPLAIN](/reference-guide/sql-syntax/105-EXPLAIN.md)
+    + [EXPLAIN PLAN](/reference-guide/sql-syntax/106-EXPLAIN-PLAN.md)
+    + [FETCH](/reference-guide/sql-syntax/107-FETCH.md)
+    + [GRANT](/reference-guide/sql-syntax/108-GRANT.md)
+    + [INSERT](/reference-guide/sql-syntax/109-INSERT.md)
+    + [LOCK](/reference-guide/sql-syntax/110-LOCK.md)
+    + [MOVE](/reference-guide/sql-syntax/111-MOVE.md)
+    + [MERGE INTO](/reference-guide/sql-syntax/112-MERGE-INTO.md)
+    + [PREDICT BY](/reference-guide/sql-syntax/112.1-PREDICT-BY.md)
+    + [PREPARE](/reference-guide/sql-syntax/113-PREPARE.md)
+    + [PREPARE TRANSACTION](/reference-guide/sql-syntax/114-PREPARE-TRANSACTION.md)
+    + [PURGE](/reference-guide/sql-syntax/114.1-PURGE.md)
+    + [REASSIGN OWNED](/reference-guide/sql-syntax/115-REASSIGN-OWNED.md)
+    + [REFRESH INCREMENTAL MATERIALIZED VIEW](/reference-guide/sql-syntax/115.1-REFRESH-INCREMENTAL-MATERIALIZED-VIEW.md)
+    + [REFRESH MATERIALIZED VIEW](/reference-guide/sql-syntax/116-REFRESH-MATERIALIZED-VIEW.md)
+    + [REINDEX](/reference-guide/sql-syntax/117-REINDEX.md)
+    + [RELEASE SAVEPOINT](/reference-guide/sql-syntax/118-RELEASE-SAVEPOINT.md)
+    + [RESET](/reference-guide/sql-syntax/119-RESET.md)
+    + [REVOKE](/reference-guide/sql-syntax/120-REVOKE.md)
+    + [ROLLBACK](/reference-guide/sql-syntax/121-ROLLBACK.md)
+    + [ROLLBACK PREPARED](/reference-guide/sql-syntax/122-ROLLBACK-PREPARED.md)
+    + [ROLLBACK TO SAVEPOINT](/reference-guide/sql-syntax/123-ROLLBACK-TO-SAVEPOINT.md)
+    + [SAVEPOINT](/reference-guide/sql-syntax/124-SAVEPOINT.md)
+    + [SELECT](/reference-guide/sql-syntax/125-SELECT.md)
+    + [SELECT INTO](/reference-guide/sql-syntax/126-SELECT-INTO.md)
+    + [SET](/reference-guide/sql-syntax/127-SET.md)
+    + [SET CONSTRAINTS](/reference-guide/sql-syntax/128-SET-CONSTRAINTS.md)
+    + [SET ROLE](/reference-guide/sql-syntax/129-SET-ROLE.md)
+    + [SET SESSION AUTHORIZATION](/reference-guide/sql-syntax/130-SET-SESSION-AUTHORIZATION.md)
+    + [SET TRANSACTION](/reference-guide/sql-syntax/131-SET-TRANSACTION.md)
+    + [SHOW](/reference-guide/sql-syntax/132-SHOW.md)
+    + [SHUTDOWN](/reference-guide/sql-syntax/133-SHUTDOWN.md)
+    + [SNAPSHOT](/reference-guide/sql-syntax/133.1-SNAPSHOT.md)
+    + [START TRANSACTION](/reference-guide/sql-syntax/134-START-TRANSACTION.md)
+    + [TIMECAPSULE TABLE](/reference-guide/sql-syntax/134.1-TIMECAPSULE-TABLE.md)
+    + [TRUNCATE](/reference-guide/sql-syntax/135-TRUNCATE.md)
+    + [UPDATE](/reference-guide/sql-syntax/136-UPDATE.md)
+    + [VACUUM](/reference-guide/sql-syntax/137-VACUUM.md)
+    + [VALUES](/reference-guide/sql-syntax/138-VALUES.md)
+  + SQL参考
+    + [MogDB SQL](/reference-guide/sql-reference/1-mogdb-sql.md)
+    + [关键字](/reference-guide/sql-reference/2-keywords.md)
+    + [常量与宏](/reference-guide/sql-reference/3-constant-and-macro.md)
+    + 表达式
+      + [简单表达式](/reference-guide/sql-reference/4-expressions/1-simple-expressions.md)
+      + [条件表达式](/reference-guide/sql-reference/4-expressions/2-condition-expressions.md)
+      + [子查询表达式](/reference-guide/sql-reference/4-expressions/3-subquery-expressions.md)
+      + [数组表达式](/reference-guide/sql-reference/4-expressions/4-array-expressions.md)
+      + [行表达式](/reference-guide/sql-reference/4-expressions/5-row-expressions.md)
+    + 类型转换
+      + [概述](/reference-guide/sql-reference/5-type-conversion/1-type-conversion-overview.md)
+      + [操作符](/reference-guide/sql-reference/5-type-conversion/2-operators.md)
+      + [函数](/reference-guide/sql-reference/5-type-conversion/3-functions.md)
+      + [值存储](/reference-guide/sql-reference/5-type-conversion/4-value-storage.md)
+      + [UNION，CASE和相关构造](/reference-guide/sql-reference/5-type-conversion/5-union-case-and-related-constructs.md)
+    + 全文检索
+      + 介绍
+        + [全文检索概述](/reference-guide/sql-reference/6-full-text-search/1-introduction/1-full-text-retrieval.md)
+        + [文档概念](/reference-guide/sql-reference/6-full-text-search/1-introduction/2-what-is-a-document.md)
+        + [基本文本匹配](/reference-guide/sql-reference/6-full-text-search/1-introduction/3-basic-text-matching.md)
+        + [分词器](/reference-guide/sql-reference/6-full-text-search/1-introduction/4-configurations.md)
+      + 表和索引
+        + [搜索表](/reference-guide/sql-reference/6-full-text-search/2-tables-and-indexes/1-searching-a-table.md)
+        + [创建索引](/reference-guide/sql-reference/6-full-text-search/2-tables-and-indexes/2-creating-an-index.md)
+        + [索引使用约束](/reference-guide/sql-reference/6-full-text-search/2-tables-and-indexes/3-constraints-on-index-use.md)
+      + 控制文本搜索
+        + [解析文档](/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/1-parsing-documents.md)
+        + [解析查询](/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/2-parsing-queries.md)
+        + [排序查询结果](/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/3-ranking-search-results.md)
+        + [高亮搜索结果](/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/4-highlighting-results.md)
+      + 附加功能
+        + [处理tsvector](/reference-guide/sql-reference/6-full-text-search/4-additional-features/1-manipulating-tsvector.md)
+        + [处理查询](/reference-guide/sql-reference/6-full-text-search/4-additional-features/2-manipulating-queries.md)
+        + [查询重写](/reference-guide/sql-reference/6-full-text-search/4-additional-features/3-rewriting-queries.md)
+        + [收集文献统计](/reference-guide/sql-reference/6-full-text-search/4-additional-features/4-gathering-document-statistics.md)
+      + [解析器](/reference-guide/sql-reference/6-full-text-search/5-parser.md)
+      + 词典
+        + [词典概述](/reference-guide/sql-reference/6-full-text-search/6-dictionaries/1-dictionaries-overview.md)
+        + [停用词](/reference-guide/sql-reference/6-full-text-search/6-dictionaries/2-stop-words.md)
+        + [Simple词典](/reference-guide/sql-reference/6-full-text-search/6-dictionaries/3-simple-dictionary.md)
+        + [Synonym词典](/reference-guide/sql-reference/6-full-text-search/6-dictionaries/4-synonym-dictionary.md)
+        + [Thesaurus词典](/reference-guide/sql-reference/6-full-text-search/6-dictionaries/5-thesaurus-dictionary.md)
+        + [Ispell词典](/reference-guide/sql-reference/6-full-text-search/6-dictionaries/6-ispell-dictionary.md)
+        + [Snowball词典](/reference-guide/sql-reference/6-full-text-search/6-dictionaries/7-snowball-dictionary.md)
+      + [配置示例](/reference-guide/sql-reference/6-full-text-search/7-configuration-examples.md)
+      + 测试和调试文本搜索
+        + [分词器测试](/reference-guide/sql-reference/6-full-text-search/8-testing-and-debugging-text-search/1-testing-a-configuration.md)
+        + [解析器测试](/reference-guide/sql-reference/6-full-text-search/8-testing-and-debugging-text-search/2-testing-a-parser.md)
+        + [词典测试](/reference-guide/sql-reference/6-full-text-search/8-testing-and-debugging-text-search/3-testing-a-dictionary.md)
+      + [限制约束](/reference-guide/sql-reference/6-full-text-search/9-limitations.md)
+    + [系统操作](/reference-guide/sql-reference/7-system-operation.md)
+    + [事务控制](/reference-guide/sql-reference/8-controlling-transactions.md)
+    + [DDL语法一览表](/reference-guide/sql-reference/9-ddl-syntax-overview.md)
+    + [DML语法一览表](/reference-guide/sql-reference/10-dml-syntax-overview.md)
+    + [DCL语法一览表](/reference-guide/sql-reference/11-dcl-syntax-overview.md)
+    + 附录
+      + GIN索引
+        + [介绍](/reference-guide/sql-reference/13-appendix/1-gin-indexes/1-introduction.md)
+        + [扩展性](/reference-guide/sql-reference/13-appendix/1-gin-indexes/2-scalability.md)
+        + [实现](/reference-guide/sql-reference/13-appendix/1-gin-indexes/3-implementation.md)
+        + [GIN提示与技巧](/reference-guide/sql-reference/13-appendix/1-gin-indexes/4-gin-tips-and-tricks.md)
+      + [扩展函数](/reference-guide/sql-reference/13-appendix/2-extended-functions.md)
+      + [扩展语法](/reference-guide/sql-reference/13-appendix/3-extended-syntax.md)
+  + GUC参数说明
+    + [GUC使用说明](/reference-guide/guc-parameters/1-guc-parameter-usage.md)
+    + [文件位置](/reference-guide/guc-parameters/2-file-location.md)
+    + 连接和认证
+      + [连接设置](/reference-guide/guc-parameters/3-connection-and-authentication/1-connection-settings.md)
+      + [安全和认证](/reference-guide/guc-parameters/3-connection-and-authentication/2-security-and-authentication.md)
+      + [通信库参数](/reference-guide/guc-parameters/3-connection-and-authentication/3-communication-library-parameters.md)
+    + 资源消耗
+      + [内存](/reference-guide/guc-parameters/4-resource-consumption/1-memory.md)
+      + [磁盘空间](/reference-guide/guc-parameters/4-resource-consumption/2-disk-space.md)
+      + [内核资源使用](/reference-guide/guc-parameters/4-resource-consumption/3-kernel-resource-usage.md)
+      + [基于开销的清理延迟](/reference-guide/guc-parameters/4-resource-consumption/4-cost-based-vacuum-delay.md)
+      + [后端写进程](/reference-guide/guc-parameters/4-resource-consumption/5-background-writer.md)
+      + [异步IO](/reference-guide/guc-parameters/4-resource-consumption/6-asynchronous-io-operations.md)
+    + [并行导入](/reference-guide/guc-parameters/5-parallel-import.md)
+    + 预写式日志
+      + [设置](/reference-guide/guc-parameters/6-write-ahead-log/1-settings.md)
+      + [检查点](/reference-guide/guc-parameters/6-write-ahead-log/2-checkpoints.md)
+      + [日志回放](/reference-guide/guc-parameters/6-write-ahead-log/3-log-replay.md)
+      + [归档](/reference-guide/guc-parameters/6-write-ahead-log/4-archiving.md)
+    + 双机复制
+      + [发送端服务器](/reference-guide/guc-parameters/7-ha-replication/1-sending-server.md)
+      + [主服务器](/reference-guide/guc-parameters/7-ha-replication/2-primary-server.md)
+      + [备服务器](/reference-guide/guc-parameters/7-ha-replication/3-standby-server.md)
+    + [内存表](/reference-guide/guc-parameters/8-mot.md)
+    + 查询规划
+      + [介绍](/reference-guide/guc-parameters/9-query-planning/introduction-to-query-planning.md)
+      + [优化器方法配置](/reference-guide/guc-parameters/9-query-planning/1-optimizer-method-configuration.md)
+      + [优化器开销常量](/reference-guide/guc-parameters/9-query-planning/2-optimizer-cost-constants.md)
+      + [基因查询优化器](/reference-guide/guc-parameters/9-query-planning/3-genetic-query-optimizer.md)
+      + [其他优化器选项](/reference-guide/guc-parameters/9-query-planning/4-other-optimizer-options.md)
+    + 错误报告和日志
+      + [记录日志的位置](/reference-guide/guc-parameters/10-error-reporting-and-logging/1-logging-destination.md)
+      + [记录日志的时间](/reference-guide/guc-parameters/10-error-reporting-and-logging/2-logging-time.md)
+      + [记录日志的内容](/reference-guide/guc-parameters/10-error-reporting-and-logging/3-logging-content.md)
+      + [使用CSV格式写日志](/reference-guide/guc-parameters/10-error-reporting-and-logging/4-using-csv-log-output.md)
+    + [告警检测](/reference-guide/guc-parameters/11-alarm-detection.md)
+    + 运行时统计
+      + [查询和索引统计收集器](/reference-guide/guc-parameters/12-statistics-during-the-database-running/1-query-and-index-statistics-collector.md)
+      + [性能统计](/reference-guide/guc-parameters/12-statistics-during-the-database-running/2-performance-statistics.md)
+    + [负载管理](/reference-guide/guc-parameters/13-load-management.md)
+    + [自动清理](/reference-guide/guc-parameters/14-automatic-vacuuming.md)
+    + 客户端连接缺省设置
+      + [语句行为](/reference-guide/guc-parameters/15-default-settings-of-client-connection/1-statement-behavior.md)
+      + [区域和格式化](/reference-guide/guc-parameters/15-default-settings-of-client-connection/2-zone-and-formatting.md)
+      + [其他缺省](/reference-guide/guc-parameters/15-default-settings-of-client-connection/3-other-default-parameters.md)
+    + [锁管理](/reference-guide/guc-parameters/16-lock-management.md)
+    + 版本和平台兼容性
+      + [历史版本兼容性](/reference-guide/guc-parameters/17-version-and-platform-compatibility/1-compatibility-with-earlier-versions.md)
+      + [平台和客户端兼容性](/reference-guide/guc-parameters/17-version-and-platform-compatibility/2-platform-and-client-compatibility.md)
+    + [容错性](/reference-guide/guc-parameters/18-fault-tolerance.md)
+    + [连接池参数](/reference-guide/guc-parameters/19-connection-pool-parameters.md)
+    + [MogDB事务](/reference-guide/guc-parameters/20-MogDB-transaction.md)
+    + [开发人员选项](/reference-guide/guc-parameters/21-developer-options.md)
+    + 审计
+      + [审计开关](/reference-guide/guc-parameters/22-auditing/1-audit-switch.md)
+      + [用户和权限审计](/reference-guide/guc-parameters/22-auditing/2-user-and-permission-audit.md)
+      + [操作审计](/reference-guide/guc-parameters/22-auditing/3-operation-audit.md)
+    + [升级参数](/reference-guide/guc-parameters/23-upgrade-parameters.md)
+    + [其他选项](/reference-guide/guc-parameters/24-miscellaneous-parameters.md)
+    + [等待事件](/reference-guide/guc-parameters/25-wait-events.md)
+    + [Query](/reference-guide/guc-parameters/26-query.md)
+    + [系统性能快照](/reference-guide/guc-parameters/27-system-performance-snapshot.md)
+    + [安全配置](/reference-guide/guc-parameters/27.1-security-configuration.md)
+    + [全局临时表](/reference-guide/guc-parameters/29-global-temporary-table.md)
+    + [HyperLogLog](/reference-guide/guc-parameters/29.1-HyperLogLog.md)
+    + [定时任务](/reference-guide/guc-parameters/31-scheduled-task.md)
+    + [线程池](/reference-guide/guc-parameters/32-thread-pool.md)
+    + [用户自定义函数](/reference-guide/guc-parameters/33-user-defined-functions.md)
+    + [备份恢复](/reference-guide/guc-parameters/34-backup-and-restoration.md)
+    + [Undo](/reference-guide/guc-parameters/35-undo.md)
+    + [DCF参数设置](/reference-guide/guc-parameters/36-DCF-parameters-settings.md)
+    + [闪回相关参数](/reference-guide/guc-parameters/37-flashback.md)
+    + [回滚相关参数](/reference-guide/guc-parameters/38-rollback-parameters.md)
+    + [预留参数](/reference-guide/guc-parameters/39-reserved-parameters.md)
+    + [AI特性](/reference-guide/guc-parameters/40-AI-features.md)
+    + [附录](/reference-guide/guc-parameters/30-appendix.md)
+  + Schema
+    + Information Schema
+      + [概述](/reference-guide/schema/information-schema/1-information-schema-overview.md)
+      + [_PG_FOREIGN_DATA_WRAPPERS](/reference-guide/schema/information-schema/2-_PG_FOREIGN_DATA_WRAPPERS.md)
+      + [_PG_FOREIGN_SERVERS](/reference-guide/schema/information-schema/3-_PG_FOREIGN_SERVERS.md)
+      + [_PG_FOREIGN_TABLE_COLUMNS](/reference-guide/schema/information-schema/4-_PG_FOREIGN_TABLE_COLUMNS.md)
+      + [_PG_FOREIGN_TABLES](/reference-guide/schema/information-schema/5-_PG_FOREIGN_TABLES.md)
+      + [_PG_USER_MAPPINGS](/reference-guide/schema/information-schema/6-_PG_USER_MAPPINGS.md)
+      + [INFORMATION_SCHEMA_CATALOG_NAME](/reference-guide/schema/information-schema/7-INFORMATION_SCHEMA_CATALOG_NAME.md)
+    + DBE_PERF
+      + [概述](/reference-guide/schema/DBE_PERF/DBE_PERF_overview.md)
+      + OS
+        + [OS_RUNTIME](/reference-guide/schema/DBE_PERF/os/OS_RUNTIME.md)
+        + [GLOBAL_OS_RUNTIME](/reference-guide/schema/DBE_PERF/os/GLOBAL_OS_RUNTIME.md)
+        + [OS_THREADS](/reference-guide/schema/DBE_PERF/os/OS_THREADS.md)
+        + [GLOBAL_OS_THREADS](/reference-guide/schema/DBE_PERF/os/GLOBAL_OS_THREADS.md)
+      + Instance
+        + [INSTANCE_TIME](/reference-guide/schema/DBE_PERF/instance/INSTANCE_TIME.md)
+        + [GLOBAL_INSTANCE_TIME](/reference-guide/schema/DBE_PERF/instance/GLOBAL_INSTANCE_TIME.md)
+      + Memory
+        + [MEMORY_NODE_DETAIL](/reference-guide/schema/DBE_PERF/memory/MEMORY_NODE_DETAIL.md)
+        + [GLOBAL_MEMORY_NODE_DETAIL](/reference-guide/schema/DBE_PERF/memory/GLOBAL_MEMORY_NODE_DETAIL.md)
+        + [GS_SHARED_MEMORY_DETAIL](/reference-guide/schema/DBE_PERF/memory/GS_SHARED_MEMORY_DETAIL.md)
+        + [GLOBAL_SHARED_MEMORY_DETAIL](/reference-guide/schema/DBE_PERF/memory/GLOBAL_SHARED_MEMORY_DETAIL.md)
+      + File
+        + [FILE_IOSTAT](/reference-guide/schema/DBE_PERF/file/FILE_IOSTAT.md)
+        + [SUMMARY_FILE_IOSTAT](/reference-guide/schema/DBE_PERF/file/SUMMARY_FILE_IOSTAT.md)
+        + [GLOBAL_FILE_IOSTAT](/reference-guide/schema/DBE_PERF/file/GLOBAL_FILE_IOSTAT.md)
+        + [FILE_REDO_IOSTAT](/reference-guide/schema/DBE_PERF/file/FILE_REDO_IOSTAT.md)
+        + [SUMMARY_FILE_REDO_IOSTAT](/reference-guide/schema/DBE_PERF/file/SUMMARY_FILE_REDO_IOSTAT.md)
+        + [GLOBAL_FILE_REDO_IOSTAT](/reference-guide/schema/DBE_PERF/file/GLOBAL_FILE_REDO_IOSTAT.md)
+        + [LOCAL_REL_IOSTAT](/reference-guide/schema/DBE_PERF/file/LOCAL_REL_IOSTAT.md)
+        + [GLOBAL_REL_IOSTAT](/reference-guide/schema/DBE_PERF/file/GLOBAL_REL_IOSTAT.md)
+        + [SUMMARY_REL_IOSTAT](/reference-guide/schema/DBE_PERF/file/SUMMARY_REL_IOSTAT.md)
+      + Object
+        + [STAT_USER_TABLES](/reference-guide/schema/DBE_PERF/object/STAT_USER_TABLES.md)
+        + [SUMMARY_STAT_USER_TABLES](/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_USER_TABLES.md)
+        + [GLOBAL_STAT_USER_TABLES](/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_USER_TABLES.md)
+        + [STAT_USER_INDEXES](/reference-guide/schema/DBE_PERF/object/STAT_USER_INDEXES.md)
+        + [SUMMARY_STAT_USER_INDEXES](/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_USER_INDEXES.md)
+        + [GLOBAL_STAT_USER_INDEXES](/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_USER_INDEXES.md)
+        + [STAT_SYS_TABLES](/reference-guide/schema/DBE_PERF/object/STAT_SYS_TABLES.md)
+        + [SUMMARY_STAT_SYS_TABLES](/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_SYS_TABLES.md)
+        + [GLOBAL_STAT_SYS_TABLES](/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_SYS_TABLES.md)
+        + [STAT_SYS_INDEXES](/reference-guide/schema/DBE_PERF/object/STAT_SYS_INDEXES.md)
+        + [SUMMARY_STAT_SYS_INDEXES](/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_SYS_INDEXES.md)
+        + [GLOBAL_STAT_SYS_INDEXES](/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_SYS_INDEXES.md)
+        + [STAT_ALL_TABLES](/reference-guide/schema/DBE_PERF/object/STAT_ALL_TABLES.md)
+        + [SUMMARY_STAT_ALL_TABLES](/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_ALL_TABLES.md)
+        + [GLOBAL_STAT_ALL_TABLES](/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_ALL_TABLES.md)
+        + [STAT_ALL_INDEXES](/reference-guide/schema/DBE_PERF/object/STAT_ALL_INDEXES.md)
+        + [SUMMARY_STAT_ALL_INDEXES](/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_ALL_INDEXES.md)
+        + [GLOBAL_STAT_ALL_INDEXES](/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_ALL_INDEXES.md)
+        + [STAT_DATABASE](/reference-guide/schema/DBE_PERF/object/STAT_DATABASE.md)
+        + [SUMMARY_STAT_DATABASE](/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_DATABASE.md)
+        + [GLOBAL_STAT_DATABASE](/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_DATABASE.md)
+        + [STAT_DATABASE_CONFLICTS](/reference-guide/schema/DBE_PERF/object/STAT_DATABASE_CONFLICTS.md)
+        + [SUMMARY_STAT_DATABASE_CONFLICTS](/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_DATABASE_CONFLICTS.md)
+        + [GLOBAL_STAT_DATABASE_CONFLICTS](/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_DATABASE_CONFLICTS.md)
+        + [STAT_XACT_ALL_TABLES](/reference-guide/schema/DBE_PERF/object/STAT_XACT_ALL_TABLES.md)
+        + [SUMMARY_STAT_XACT_ALL_TABLES](/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_ALL_TABLES.md)
+        + [GLOBAL_STAT_XACT_ALL_TABLES](/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_ALL_TABLES.md)
+        + [STAT_XACT_SYS_TABLES](/reference-guide/schema/DBE_PERF/object/STAT_XACT_SYS_TABLES.md)
+        + [SUMMARY_STAT_XACT_SYS_TABLES](/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_SYS_TABLES.md)
+        + [GLOBAL_STAT_XACT_SYS_TABLES](/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_SYS_TABLES.md)
+        + [STAT_XACT_USER_TABLES](/reference-guide/schema/DBE_PERF/object/STAT_XACT_USER_TABLES.md)
+        + [SUMMARY_STAT_XACT_USER_TABLES](/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_USER_TABLES.md)
+        + [GLOBAL_STAT_XACT_USER_TABLES](/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_USER_TABLES.md)
+        + [STAT_XACT_USER_FUNCTIONS](/reference-guide/schema/DBE_PERF/object/STAT_XACT_USER_FUNCTIONS.md)
+        + [SUMMARY_STAT_XACT_USER_FUNCTIONS](/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_USER_FUNCTIONS.md)
+        + [GLOBAL_STAT_XACT_USER_FUNCTIONS](/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_USER_FUNCTIONS.md)
+        + [STAT_BAD_BLOCK](/reference-guide/schema/DBE_PERF/object/STAT_BAD_BLOCK.md)
+        + [SUMMARY_STAT_BAD_BLOCK](/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_BAD_BLOCK.md)
+        + [GLOBAL_STAT_BAD_BLOCK](/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_BAD_BLOCK.md)
+        + [STAT_USER_FUNCTIONS](/reference-guide/schema/DBE_PERF/object/STAT_USER_FUNCTIONS.md)
+        + [SUMMARY_STAT_USER_FUNCTIONS](/reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_USER_FUNCTIONS.md)
+        + [GLOBAL_STAT_USER_FUNCTIONS](/reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_USER_FUNCTIONS.md)
+      + Workload
+        + [WORKLOAD_SQL_COUNT](/reference-guide/schema/DBE_PERF/workload/WORKLOAD_SQL_COUNT.md)
+        + [SUMMARY_WORKLOAD_SQL_COUNT](/reference-guide/schema/DBE_PERF/workload/SUMMARY_WORKLOAD_SQL_COUNT.md)
+        + [WORKLOAD_TRANSACTION](/reference-guide/schema/DBE_PERF/workload/WORKLOAD_TRANSACTION.md)
+        + [SUMMARY_WORKLOAD_TRANSACTION](/reference-guide/schema/DBE_PERF/workload/SUMMARY_WORKLOAD_TRANSACTION.md)
+        + [GLOBAL_WORKLOAD_TRANSACTION](/reference-guide/schema/DBE_PERF/workload/GLOBAL_WORKLOAD_TRANSACTION.md)
+        + [WORKLOAD_SQL_ELAPSE_TIME](/reference-guide/schema/DBE_PERF/workload/WORKLOAD_SQL_ELAPSE_TIME.md)
+        + [SUMMARY_WORKLOAD_SQL_ELAPSE_TIME](/reference-guide/schema/DBE_PERF/workload/SUMMARY_WORKLOAD_SQL_ELAPSE_TIME.md)
+        + [USER_TRANSACTION](/reference-guide/schema/DBE_PERF/workload/USER_TRANSACTION.md)
+        + [GLOBAL_USER_TRANSACTION](/reference-guide/schema/DBE_PERF/workload/GLOBAL_USER_TRANSACTION.md)
+      + Session/Thread
+        + [SESSION_STAT](/reference-guide/schema/DBE_PERF/session-thread/SESSION_STAT.md)
+        + [GLOBAL_SESSION_STAT](/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_STAT.md)
+        + [SESSION_TIME](/reference-guide/schema/DBE_PERF/session-thread/SESSION_TIME.md)
+        + [GLOBAL_SESSION_TIME](/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_TIME.md)
+        + [SESSION_MEMORY](/reference-guide/schema/DBE_PERF/session-thread/SESSION_MEMORY.md)
+        + [GLOBAL_SESSION_MEMORY](/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_MEMORY.md)
+        + [SESSION_MEMORY_DETAIL](/reference-guide/schema/DBE_PERF/session-thread/SESSION_MEMORY_DETAIL.md)
+        + [GLOBAL_SESSION_MEMORY_DETAIL](/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_MEMORY_DETAIL.md)
+        + [SESSION_STAT_ACTIVITY](/reference-guide/schema/DBE_PERF/session-thread/SESSION_STAT_ACTIVITY.md)
+        + [GLOBAL_SESSION_STAT_ACTIVITY](/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_STAT_ACTIVITY.md)
+        + [THREAD_WAIT_STATUS](/reference-guide/schema/DBE_PERF/session-thread/THREAD_WAIT_STATUS.md)
+        + [GLOBAL_THREAD_WAIT_STATUS](/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_THREAD_WAIT_STATUS.md)
+        + [LOCAL_THREADPOOL_STATUS](/reference-guide/schema/DBE_PERF/session-thread/LOCAL_THREADPOOL_STATUS.md)
+        + [GLOBAL_THREADPOOL_STATUS](/reference-guide/schema/DBE_PERF/session-thread/GLOBAL_THREADPOOL_STATUS.md)
+        + [SESSION_CPU_RUNTIME](/reference-guide/schema/DBE_PERF/session-thread/SESSION_CPU_RUNTIME.md)
+        + [SESSION_MEMORY_RUNTIME](/reference-guide/schema/DBE_PERF/session-thread/SESSION_MEMORY_RUNTIME.md)
+        + [STATEMENT_IOSTAT_COMPLEX_RUNTIME](/reference-guide/schema/DBE_PERF/session-thread/STATEMENT_IOSTAT_COMPLEX_RUNTIME.md)
+        + [LOCAL_ACTIVE_SESSION](/reference-guide/schema/DBE_PERF/session-thread/LOCAL_ACTIVE_SESSION.md)
+      + Transaction
+        + [TRANSACTIONS_PREPARED_XACTS](/reference-guide/schema/DBE_PERF/transaction/TRANSACTIONS_PREPARED_XACTS.md)
+        + [SUMMARY_TRANSACTIONS_PREPARED_XACTS](/reference-guide/schema/DBE_PERF/transaction/SUMMARY_TRANSACTIONS_PREPARED_XACTS.md)
+        + [GLOBAL_TRANSACTIONS_PREPARED_XACTS](/reference-guide/schema/DBE_PERF/transaction/GLOBAL_TRANSACTIONS_PREPARED_XACTS.md)
+        + [TRANSACTIONS_RUNNING_XACTS](/reference-guide/schema/DBE_PERF/transaction/TRANSACTIONS_RUNNING_XACTS.md)
+        + [SUMMARY_TRANSACTIONS_RUNNING_XACTS](/reference-guide/schema/DBE_PERF/transaction/SUMMARY_TRANSACTIONS_RUNNING_XACTS.md)
+        + [GLOBAL_TRANSACTIONS_RUNNING_XACTS](/reference-guide/schema/DBE_PERF/transaction/GLOBAL_TRANSACTIONS_RUNNING_XACTS.md)
+      + Query
+        + [STATEMENT](/reference-guide/schema/DBE_PERF/query/STATEMENT.md)
+        + [SUMMARY_STATEMENT](/reference-guide/schema/DBE_PERF/query/SUMMARY_STATEMENT.md)
+        + [STATEMENT_COUNT](/reference-guide/schema/DBE_PERF/query/STATEMENT_COUNT.md)
+        + [GLOBAL_STATEMENT_COUNT](/reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COUNT.md)
+        + [SUMMARY_STATEMENT_COUNT](/reference-guide/schema/DBE_PERF/query/SUMMARY_STATEMENT_COUNT.md)
+        + [GLOBAL_STATEMENT_COMPLEX_HISTORY](/reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COMPLEX_HISTORY.md)
+        + [GLOBAL_STATEMENT_COMPLEX_HISTORY_TABLE](/reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COMPLEX_HISTORY_TABLE.md)
+        + [GLOBAL_STATEMENT_COMPLEX_RUNTIME](/reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COMPLEX_RUNTIME.md)
+        + [STATEMENT_RESPONSETIME_PERCENTILE](/reference-guide/schema/DBE_PERF/query/STATEMENT_RESPONSETIME_PERCENTILE.md)
+        + [STATEMENT_USER_COMPLEX_HISTORY](/reference-guide/schema/DBE_PERF/query/STATEMENT_USER_COMPLEX_HISTORY.md)
+        + [STATEMENT_COMPLEX_RUNTIME](/reference-guide/schema/DBE_PERF/query/STATEMENT_COMPLEX_RUNTIME.md)
+        + [STATEMENT_COMPLEX_HISTORY_TABLE](/reference-guide/schema/DBE_PERF/query/STATEMENT_COMPLEX_HISTORY_TABLE.md)
+        + [STATEMENT_COMPLEX_HISTORY](/reference-guide/schema/DBE_PERF/query/STATEMENT_COMPLEX_HISTORY.md)
+        + [STATEMENT_WLMSTAT_COMPLEX_RUNTIME](/reference-guide/schema/DBE_PERF/query/STATEMENT_WLMSTAT_COMPLEX_RUNTIME.md)
+        + [STATEMENT_HISTORY](/reference-guide/schema/DBE_PERF/query/STATEMENT_HISTORY.md)
+      + Cache/IO
+        + [STATIO_USER_TABLES](/reference-guide/schema/DBE_PERF/cache-io/STATIO_USER_TABLES.md)
+        + [SUMMARY_STATIO_USER_TABLES](/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_USER_TABLES.md)
+        + [GLOBAL_STATIO_USER_TABLES](/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_USER_TABLES.md)
+        + [STATIO_USER_INDEXES](/reference-guide/schema/DBE_PERF/cache-io/STATIO_USER_INDEXES.md)
+        + [SUMMARY_STATIO_USER_INDEXES](/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_USER_INDEXES.md)
+        + [GLOBAL_STATIO_USER_INDEXES](/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_USER_INDEXES.md)
+        + [STATIO_USER_SEQUENCES](/reference-guide/schema/DBE_PERF/cache-io/STATIO_USER_SEQUENCES.md)
+        + [SUMMARY_STATIO_USER_SEQUENCES](/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_USER_SEQUENCES.md)
+        + [GLOBAL_STATIO_USER_SEQUENCES](/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_USER_SEQUENCES.md)
+        + [STATIO_SYS_TABLES](/reference-guide/schema/DBE_PERF/cache-io/STATIO_SYS_TABLES.md)
+        + [SUMMARY_STATIO_SYS_TABLES](/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_SYS_TABLES.md)
+        + [GLOBAL_STATIO_SYS_TABLES](/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_SYS_TABLES.md)
+        + [STATIO_SYS_INDEXES](/reference-guide/schema/DBE_PERF/cache-io/STATIO_SYS_INDEXES.md)
+        + [SUMMARY_STATIO_SYS_INDEXES](/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_SYS_INDEXES.md)
+        + [GLOBAL_STATIO_SYS_INDEXES](/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_SYS_INDEXES.md)
+        + [STATIO_SYS_SEQUENCES](/reference-guide/schema/DBE_PERF/cache-io/STATIO_SYS_SEQUENCES.md)
+        + [SUMMARY_STATIO_SYS_SEQUENCES](/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_SYS_SEQUENCES.md)
+        + [GLOBAL_STATIO_SYS_SEQUENCES](/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_SYS_SEQUENCES.md)
+        + [STATIO_ALL_TABLES](/reference-guide/schema/DBE_PERF/cache-io/STATIO_ALL_TABLES.md)
+        + [SUMMARY_STATIO_ALL_TABLES](/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_ALL_TABLES.md)
+        + [GLOBAL_STATIO_ALL_TABLES](/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_ALL_TABLES.md)
+        + [STATIO_ALL_INDEXES](/reference-guide/schema/DBE_PERF/cache-io/STATIO_ALL_INDEXES.md)
+        + [SUMMARY_STATIO_ALL_INDEXES](/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_ALL_INDEXES.md)
+        + [GLOBAL_STATIO_ALL_INDEXES](/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_ALL_INDEXES.md)
+        + [STATIO_ALL_SEQUENCES](/reference-guide/schema/DBE_PERF/cache-io/STATIO_ALL_SEQUENCES.md)
+        + [SUMMARY_STATIO_ALL_SEQUENCES](/reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_ALL_SEQUENCES.md)
+        + [GLOBAL_STATIO_ALL_SEQUENCES](/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_ALL_SEQUENCES.md)
+        + [GLOBAL_STAT_DB_CU](/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STAT_DB_CU.md)
+        + [GLOBAL_STAT_SESSION_CU](/reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STAT_SESSION_CU.md)
+      + Utility
+        + [REPLICATION_STAT](/reference-guide/schema/DBE_PERF/utility/REPLICATION_STAT.md)
+        + [GLOBAL_REPLICATION_STAT](/reference-guide/schema/DBE_PERF/utility/GLOBAL_REPLICATION_STAT.md)
+        + [REPLICATION_SLOTS](/reference-guide/schema/DBE_PERF/utility/REPLICATION_SLOTS.md)
+        + [GLOBAL_REPLICATION_SLOTS](/reference-guide/schema/DBE_PERF/utility/GLOBAL_REPLICATION_SLOTS.md)
+        + [BGWRITER_STAT](/reference-guide/schema/DBE_PERF/utility/BGWRITER_STAT.md)
+        + [GLOBAL_BGWRITER_STAT](/reference-guide/schema/DBE_PERF/utility/GLOBAL_BGWRITER_STAT.md)
+        + [GLOBAL_CKPT_STATUS](/reference-guide/schema/DBE_PERF/utility/GLOBAL_CKPT_STATUS.md)
+        + [GLOBAL_DOUBLE_WRITE_STATUS](/reference-guide/schema/DBE_PERF/utility/GLOBAL_DOUBLE_WRITE_STATUS.md)
+        + [GLOBAL_PAGEWRITER_STATUS](/reference-guide/schema/DBE_PERF/utility/GLOBAL_PAGEWRITER_STATUS.md)
+        + [GLOBAL_RECORD_RESET_TIME](/reference-guide/schema/DBE_PERF/utility/GLOBAL_RECORD_RESET_TIME.md)
+        + [GLOBAL_REDO_STATUS](/reference-guide/schema/DBE_PERF/utility/GLOBAL_REDO_STATUS.md)
+        + [GLOBAL_RECOVERY_STATUS](/reference-guide/schema/DBE_PERF/utility/GLOBAL_RECOVERY_STATUS.md)
+        + [CLASS_VITAL_INFO](/reference-guide/schema/DBE_PERF/utility/CLASS_VITAL_INFO.md)
+        + [USER_LOGIN](/reference-guide/schema/DBE_PERF/utility/USER_LOGIN.md)
+        + [SUMMARY_USER_LOGIN](/reference-guide/schema/DBE_PERF/utility/SUMMARY_USER_LOGIN.md)
+        + [GLOBAL_GET_BGWRITER_STATUS](/reference-guide/schema/DBE_PERF/utility/GLOBAL_GET_BGWRITER_STATUS.md)
+        + [GLOBAL_SINGLE_FLUSH_DW_STATUS](/reference-guide/schema/DBE_PERF/utility/GLOBAL_SINGLE_FLUSH_DW_STATUS.md)
+        + [GLOBAL_CANDIDATE_STATUS](/reference-guide/schema/DBE_PERF/utility/GLOBAL_CANDIDATE_STATUS.md)
+      + Lock
+        + [LOCKS](/reference-guide/schema/DBE_PERF/lock/LOCKS.md)
+        + [GLOBAL_LOCKS](/reference-guide/schema/DBE_PERF/lock/GLOBAL_LOCKS.md)
+      + Wait Events
+        + [WAIT_EVENTS](/reference-guide/schema/DBE_PERF/wait-events/WAIT_EVENTS.md)
+        + [GLOBAL_WAIT_EVENTS](/reference-guide/schema/DBE_PERF/wait-events/GLOBAL_WAIT_EVENTS.md)
+      + Configuration
+        + [CONFIG_SETTINGS](/reference-guide/schema/DBE_PERF/configuration/CONFIG_SETTINGS.md)
+        + [GLOBAL_CONFIG_SETTINGS](/reference-guide/schema/DBE_PERF/configuration/GLOBAL_CONFIG_SETTINGS.md)
+      + Operator
+        + [OPERATOR_HISTORY_TABLE](/reference-guide/schema/DBE_PERF/operator/OPERATOR_HISTORY_TABLE.md)
+        + [OPERATOR_HISTORY](/reference-guide/schema/DBE_PERF/operator/OPERATOR_HISTORY.md)
+        + [OPERATOR_RUNTIME](/reference-guide/schema/DBE_PERF/operator/OPERATOR_RUNTIME.md)
+        + [GLOBAL_OPERATOR_HISTORY](/reference-guide/schema/DBE_PERF/operator/GLOBAL_OPERATOR_HISTORY.md)
+        + [GLOBAL_OPERATOR_HISTORY_TABLE](/reference-guide/schema/DBE_PERF/operator/GLOBAL_OPERATOR_HISTORY_TABLE.md)
+        + [GLOBAL_OPERATOR_RUNTIME](/reference-guide/schema/DBE_PERF/operator/GLOBAL_OPERATOR_RUNTIME.md)
+      + Workload Manager
+        + [WLM_USER_RESOURCE_CONFIG](/reference-guide/schema/DBE_PERF/workload-manager/WLM_USER_RESOURCE_CONFIG.md)
+        + [WLM_USER_RESOURCE_RUNTIME](/reference-guide/schema/DBE_PERF/workload-manager/WLM_USER_RESOURCE_RUNTIME.md)
+      + Global Plancache
+        + [概述](/reference-guide/schema/DBE_PERF/global-plancache/global-plancache-overview.md)
+        + [GLOBAL_PLANCACHE_STATUS](/reference-guide/schema/DBE_PERF/global-plancache/GLOBAL_PLANCACHE_STATUS.md)
+        + [GLOBAL_PLANCACHE_CLEAN](/reference-guide/schema/DBE_PERF/global-plancache/GLOBAL_PLANCACHE_CLEAN.md)
+      + RTO
+        + [global_rto_status](/reference-guide/schema/DBE_PERF/rto/global_rto_status.md)
+      + 附录
+        + [等待状态列表](/reference-guide/schema/DBE_PERF/appendices/table-1.md)
+        + [轻量级锁等待事件列表](/reference-guide/schema/DBE_PERF/appendices/table-2.md)
+        + [IO等待事件列表](/reference-guide/schema/DBE_PERF/appendices/table-3.md)
+        + [事务锁等待事件列表](/reference-guide/schema/DBE_PERF/appendices/table-4.md)
+        + [GS_WLM_SESSION_HISTORY的字段](/reference-guide/schema/DBE_PERF/appendices/table-5.md)
+        + [GS_WLM_OPERATOR_INFO的字段](/reference-guide/schema/DBE_PERF/appendices/table-6.md)
+    + DBE_PLDEBUGGER Schema
+      + [DBE_PLDEBUGGER Schema概述](/reference-guide/schema/DBE_PLDEBUGGER-schema/overview-of-DBE_PLDEBUGGER-schema.md)
+      + [DBE_PLDEBUGGER.turn_on](/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.turn_on.md)
+      + [DBE_PLDEBUGGER.turn_off](/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.turn_off.md)
+      + [DBE_PLDEBUGGER.local_debug_server_info](/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.local_debug_server_info.md)
+      + [DBE_PLDEBUGGER.attach](/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.attach.md)
+      + [DBE_PLDEBUGGER.next](/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.next.md)
+      + [DBE_PLDEBUGGER.continue](/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.continue.md)
+      + [DBE_PLDEBUGGER.abort](/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.abort.md)
+      + [DBE_PLDEBUGGER.print_var](/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.print_var.md)
+      + [DBE_PLDEBUGGER.info_code](/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.info_code.md)
+      + [DBE_PLDEBUGGER.step](/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.step.md)
+      + [DBE_PLDEBUGGER.add_breakpoint](/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.add_breakpoint.md)
+      + [DBE_PLDEBUGGER.delete_breakpoint](/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.delete_breakpoint.md)
+      + [DBE_PLDEBUGGER.info_breakpoints](/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.info_breakpoints.md)
+      + [DBE_PLDEBUGGER.backtrace](/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.backtrace.md)
+      + [DBE_PLDEBUGGER.finish](/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.finish.md)
+      + [DBE_PLDEBUGGER.set_var](/reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.set_var.md)
+    + DB4AI Schema
+      + [DB4AI Schema概述](/reference-guide/schema/DB4AI-schema/overview-of-DB4AI-schema.md)
+      + [DB4AI.SNAPSHOT](/reference-guide/schema/DB4AI-schema/DB4AI.SNAPSHOT.md)
+      + [DB4AI.CREATE_SNAPSHOT](/reference-guide/schema/DB4AI-schema/DB4AI.CREATE_SNAPSHOT.md)
+      + [DB4AI.CREATE_SNAPSHOT_INTERNAL](/reference-guide/schema/DB4AI-schema/DB4AI.CREATE_SNAPSHOT_INTERNAL.md)
+      + [DB4AI.PREPARE_SNAPSHOT](/reference-guide/schema/DB4AI-schema/DB4AI.PREPARE_SNAPSHOT.md)
+      + [DB4AI.PREPARE_SNAPSHOT_INTERNAL](/reference-guide/schema/DB4AI-schema/DB4AI.PREPARE_SNAPSHOT_INTERNAL.md)
+      + [DB4AI.ARCHIVE_SNAPSHOT](/reference-guide/schema/DB4AI-schema/DB4AI.ARCHIVE_SNAPSHOT.md)
+      + [DB4AI.PUBLISH_SNAPSHOT](/reference-guide/schema/DB4AI-schema/DB4AI.PUBLISH_SNAPSHOT.md)
+      + [DB4AI.MANAGE_SNAPSHOT_INTERNAL](/reference-guide/schema/DB4AI-schema/DB4AI.MANAGE_SNAPSHOT_INTERNAL.md)
+      + [DB4AI.SAMPLE_SNAPSHOT](/reference-guide/schema/DB4AI-schema/DB4AI.SAMPLE_SNAPSHOT.md)
+      + [DB4AI.PURGE_SNAPSHOT](/reference-guide/schema/DB4AI-schema/DB4AI.PURGE_SNAPSHOT.md)
+      + [DB4AI.PURGE_SNAPSHOT_INTERNAL](/reference-guide/schema/DB4AI-schema/DB4AI.PURGE_SNAPSHOT_INTERNAL.md)
+  + 工具参考
+    + [工具一览表](/reference-guide/tool-reference/tool-overview.md)
+    + [客户端工具](/reference-guide/tool-reference/client-tool.md)
+    + 服务端工具
+      + [gs_cgroup](/reference-guide/tool-reference/server-tools/0-gs_cgroup.md)
+      + [gs_check](/reference-guide/tool-reference/server-tools/1-gs_check.md)
+      + [gs_checkos](/reference-guide/tool-reference/server-tools/2-gs_checkos.md)
+      + [gs_checkperf](/reference-guide/tool-reference/server-tools/3-gs_checkperf.md)
+      + [gs_collector](/reference-guide/tool-reference/server-tools/4-gs_collector.md)
+      + [gs_dump](/reference-guide/tool-reference/server-tools/5-gs_dump.md)
+      + [gs_dumpall](/reference-guide/tool-reference/server-tools/6-gs_dumpall.md)
+      + [gs_guc](/reference-guide/tool-reference/server-tools/7-gs_guc.md)
+      + [gs_encrypt](/reference-guide/tool-reference/server-tools/7.1-gs_encrypt.md)
+      + [gs_om](/reference-guide/tool-reference/server-tools/8-gs_om.md)
+      + [gs_plan_simulator](/reference-guide/tool-reference/server-tools/8.1-gs_plan_simulator.md)
+      + [gs_restore](/reference-guide/tool-reference/server-tools/9-gs_restore.md)
+      + [gs_ssh](/reference-guide/tool-reference/server-tools/10-gs_ssh.md)
+    + 系统内部使用的工具
+      + [gaussdb](/reference-guide/tool-reference/tools-used-in-the-internal-system/1-gaussdb.md)
+      + [gs_backup](/reference-guide/tool-reference/tools-used-in-the-internal-system/2-gs_backup.md)
+      + [gs_basebackup](/reference-guide/tool-reference/tools-used-in-the-internal-system/3-gs_basebackup.md)
+      + [gs_ctl](/reference-guide/tool-reference/tools-used-in-the-internal-system/4-gs_ctl.md)
+      + [gs_initdb](/reference-guide/tool-reference/tools-used-in-the-internal-system/5-gs_initdb.md)
+      + [gs_install](/reference-guide/tool-reference/tools-used-in-the-internal-system/6-gs_install.md)
+      + [gs_install_plugin](/reference-guide/tool-reference/tools-used-in-the-internal-system/gs_install_plugin.md)
+      + [gs_install_plugin_local](/reference-guide/tool-reference/tools-used-in-the-internal-system/gs_install_plugin_local.md)
+      + [gs_preinstall](/reference-guide/tool-reference/tools-used-in-the-internal-system/8-gs_preinstall.md)
+      + [gs_sshexkey](/reference-guide/tool-reference/tools-used-in-the-internal-system/9-gs_sshexkey.md)
+      + [gs_tar](/reference-guide/tool-reference/tools-used-in-the-internal-system/10-gs_tar.md)
+      + [gs_uninstall](/reference-guide/tool-reference/tools-used-in-the-internal-system/11-gs_uninstall.md)
+      + [gs_upgradectl](/reference-guide/tool-reference/tools-used-in-the-internal-system/12-gs_upgradectl.md)
+      + [gs_expansion](/reference-guide/tool-reference/tools-used-in-the-internal-system/13-gs_expansion.md)
+      + [gs_dropnode](/reference-guide/tool-reference/tools-used-in-the-internal-system/14-gs_dropnode.md)
+      + [gs_probackup](/reference-guide/tool-reference/tools-used-in-the-internal-system/15-gs_probackup.md)
+      + [gstrace](/reference-guide/tool-reference/tools-used-in-the-internal-system/16-gstrace.md)
+      + [kdb5_util](/reference-guide/tool-reference/tools-used-in-the-internal-system/17-kdb5_util.md)
+      + [kadmin.local](/reference-guide/tool-reference/tools-used-in-the-internal-system/18-kadmin-local.md)
+      + [kinit](/reference-guide/tool-reference/tools-used-in-the-internal-system/19-kinit.md)
+      + [klist](/reference-guide/tool-reference/tools-used-in-the-internal-system/20-klist.md)
+      + [krb5kdc](/reference-guide/tool-reference/tools-used-in-the-internal-system/21-krb5kdc.md)
+      + [kdestroy](/reference-guide/tool-reference/tools-used-in-the-internal-system/22-kdestroy.md)
+      + [pg_config](/reference-guide/tool-reference/tools-used-in-the-internal-system/23-pg_config.md)
+      + [pg_controldata](/reference-guide/tool-reference/tools-used-in-the-internal-system/24-pg_controldata.md)
+      + [pg_recvlogical](/reference-guide/tool-reference/tools-used-in-the-internal-system/24.1-pg_recvlogical.md)
+      + [pg_resetxlog](/reference-guide/tool-reference/tools-used-in-the-internal-system/25-pg_resetxlog.md)
+      + [pg_archivecleanup](/reference-guide/tool-reference/tools-used-in-the-internal-system/26-pg_archivecleanup.md)
+      + [pssh](/reference-guide/tool-reference/tools-used-in-the-internal-system/27-pssh.md)
+      + [pscp](/reference-guide/tool-reference/tools-used-in-the-internal-system/28-pscp.md)
+      + [transfer.py](/reference-guide/tool-reference/tools-used-in-the-internal-system/29-transfer.py.md)
+    + [FAQ](/reference-guide/tool-reference/FAQ.md)
+    + [gs_collector工具支持收集的系统表和视图列表](/reference-guide/tool-reference/system-catalogs-and-views-supported-by-gs_collector.md)
+  + 插件
+    + [dblink](/reference-guide/oracle-plugins/dblink-user-guide.md)
+    + [orafce](/reference-guide/oracle-plugins/orafce-user-guide.md)
+    + [pg_bulkload](/reference-guide/oracle-plugins/pg_bulkload-user-guide.md)
+    + [pg_prewarm](/reference-guide/oracle-plugins/pg_prewarm-user-guide.md)
+    + [pg_repack](/reference-guide/oracle-plugins/pg_repack-user-guide.md)
+    + [pg_trgm](/reference-guide/oracle-plugins/pg_trgm-user-guide.md)
+    + [wal2json](/reference-guide/oracle-plugins/wal2json-user-guide.md)
+  + 数据库报错信息
+    + [SQL标准错误码说明](/reference-guide/error-code-reference/description-of-sql-error-codes.md)
+    + [第三方库错误码说明](/reference-guide/error-code-reference/third-party-library-error-codes.md)
+    + [GAUSS-00001 - GAUSS-00100](/reference-guide/error-code-reference/1-GAUSS-00001-GAUSS-00100.md)
+    + [GAUSS-00101 - GAUSS-00200](/reference-guide/error-code-reference/2-GAUSS-00101-GAUSS-00200.md)
+    + [GAUSS 00201 - GAUSS 00300](/reference-guide/error-code-reference/3-GAUSS-00201-GAUSS-00300.md)
+    + [GAUSS 00301 - GAUSS 00400](/reference-guide/error-code-reference/4-GAUSS-00301-GAUSS-00400.md)
+    + [GAUSS 00401 - GAUSS 00500](/reference-guide/error-code-reference/5-GAUSS-00401-GAUSS-00500.md)
+    + [GAUSS 00501 - GAUSS 00600](/reference-guide/error-code-reference/6-GAUSS-00501-GAUSS-00600.md)
+    + [GAUSS 00601 - GAUSS 00700](/reference-guide/error-code-reference/7-GAUSS-00601-GAUSS-00700.md)
+    + [GAUSS 00701 - GAUSS 00800](/reference-guide/error-code-reference/8-GAUSS-00701-GAUSS-00800.md)
+    + [GAUSS 00801 - GAUSS 00900](/reference-guide/error-code-reference/9-GAUSS-00801-GAUSS-00900.md)
+    + [GAUSS 00901 - GAUSS 01000](/reference-guide/error-code-reference/10-GAUSS-00901-GAUSS-01000.md)
+    + [GAUSS 01001 - GAUSS 01100](/reference-guide/error-code-reference/11-GAUSS-01001-GAUSS-01100.md)
+    + [GAUSS 01101 - GAUSS 01200](/reference-guide/error-code-reference/12-GAUSS-01101-GAUSS-01200.md)
+    + [GAUSS 01201 - GAUSS 01300](/reference-guide/error-code-reference/13-GAUSS-01201-GAUSS-01300.md)
+    + [GAUSS 01301 - GAUSS 01400](/reference-guide/error-code-reference/14-GAUSS-01301-GAUSS-01400.md)
+    + [GAUSS 01401 - GAUSS 01500](/reference-guide/error-code-reference/15-GAUSS-01401-GAUSS-01500.md)
+    + [GAUSS 01501 - GAUSS 01600](/reference-guide/error-code-reference/16-GAUSS-01501-GAUSS-01600.md)
+    + [GAUSS 01601 - GAUSS 01700](/reference-guide/error-code-reference/17-GAUSS-01601-GAUSS-01700.md)
+    + [GAUSS 01701 - GAUSS 01800](/reference-guide/error-code-reference/18-GAUSS-01701-GAUSS-01800.md)
+    + [GAUSS 01801 - GAUSS 01900](/reference-guide/error-code-reference/19-GAUSS-01801-GAUSS-01900.md)
+    + [GAUSS 01901 - GAUSS 02000](/reference-guide/error-code-reference/20-GAUSS-01901-GAUSS-02000.md)
+    + [GAUSS 02001 - GAUSS 02100](/reference-guide/error-code-reference/21-GAUSS-02001-GAUSS-02100.md)
+    + [GAUSS 02101 - GAUSS 02200](/reference-guide/error-code-reference/22-GAUSS-02101-GAUSS-02200.md)
+    + [GAUSS 02201 - GAUSS 02300](/reference-guide/error-code-reference/23-GAUSS-02201-GAUSS-02300.md)
+    + [GAUSS 02301 - GAUSS 02400](/reference-guide/error-code-reference/24-GAUSS-02301-GAUSS-02400.md)
+    + [GAUSS 02401 - GAUSS 02500](/reference-guide/error-code-reference/25-GAUSS-02401-GAUSS-02500.md)
+    + [GAUSS 02501 - GAUSS 02600](/reference-guide/error-code-reference/26-GAUSS-02501-GAUSS-02600.md)
+    + [GAUSS 02601 - GAUSS 02700](/reference-guide/error-code-reference/27-GAUSS-02601-GAUSS-02700.md)
+    + [GAUSS 02701 - GAUSS 02800](/reference-guide/error-code-reference/28-GAUSS-02701-GAUSS-02800.md)
+    + [GAUSS 02801 - GAUSS 02900](/reference-guide/error-code-reference/29-GAUSS-02801-GAUSS-02900.md)
+    + [GAUSS 02901 - GAUSS 03000](/reference-guide/error-code-reference/30-GAUSS-02901-GAUSS-03000.md)
+    + [GAUSS 03001 - GAUSS 03100](/reference-guide/error-code-reference/31-GAUSS-03001-GAUSS-03100.md)
+    + [GAUSS 03101 - GAUSS 03200](/reference-guide/error-code-reference/32-GAUSS-03101-GAUSS-03200.md)
+    + [GAUSS 03201 - GAUSS 03300](/reference-guide/error-code-reference/33-GAUSS-03201-GAUSS-03300.md)
+    + [GAUSS 03301 - GAUSS 03400](/reference-guide/error-code-reference/34-GAUSS-03301-GAUSS-03400.md)
+    + [GAUSS 03401 - GAUSS 03500](/reference-guide/error-code-reference/35-GAUSS-03401-GAUSS-03500.md)
+    + [GAUSS 03501 - GAUSS 03600](/reference-guide/error-code-reference/36-GAUSS-03501-GAUSS-03600.md)
+    + [GAUSS 03601 - GAUSS 03700](/reference-guide/error-code-reference/37-GAUSS-03601-GAUSS-03700.md)
+    + [GAUSS 03701 - GAUSS 03800](/reference-guide/error-code-reference/38-GAUSS-03701-GAUSS-03800.md)
+    + [GAUSS 03801 - GAUSS 03900](/reference-guide/error-code-reference/39-GAUSS-03801-GAUSS-03900.md)
+    + [GAUSS 03901 - GAUSS 04000](/reference-guide/error-code-reference/40-GAUSS-03901-GAUSS-04000.md)
+    + [GAUSS 04001 - GAUSS 04100](/reference-guide/error-code-reference/41-GAUSS-04001-GAUSS-04100.md)
+    + [GAUSS 04101 - GAUSS 04200](/reference-guide/error-code-reference/42-GAUSS-04101-GAUSS-04200.md)
+    + [GAUSS 04201 - GAUSS 04300](/reference-guide/error-code-reference/43-GAUSS-04201-GAUSS-04300.md)
+    + [GAUSS 04301 - GAUSS 04400](/reference-guide/error-code-reference/44-GAUSS-04301-GAUSS-04400.md)
+    + [GAUSS 04401 - GAUSS 04500](/reference-guide/error-code-reference/45-GAUSS-04401-GAUSS-04500.md)
+    + [GAUSS 04501 - GAUSS 04600](/reference-guide/error-code-reference/46-GAUSS-04501-GAUSS-04600.md)
+    + [GAUSS 04601 - GAUSS 04700](/reference-guide/error-code-reference/47-GAUSS-04601-GAUSS-04700.md)
+    + [GAUSS 04701 - GAUSS 04800](/reference-guide/error-code-reference/48-GAUSS-04701-GAUSS-04800.md)
+    + [GAUSS 04801 - GAUSS 04900](/reference-guide/error-code-reference/49-GAUSS-04801-GAUSS-04900.md)
+    + [GAUSS 04901 - GAUSS 05000](/reference-guide/error-code-reference/50-GAUSS-04901-GAUSS-05000.md)
+    + [GAUSS 05001 - GAUSS 05100](/reference-guide/error-code-reference/51-GAUSS-05001-GAUSS-05100.md)
+    + [GAUSS 05101 - GAUSS 05200](/reference-guide/error-code-reference/52-GAUSS-05101-GAUSS-05200.md)
+    + [GAUSS 05201 - GAUSS 05300](/reference-guide/error-code-reference/53-GAUSS-05201-GAUSS-05300.md)
+    + [GAUSS 05301 - GAUSS 05400](/reference-guide/error-code-reference/54-GAUSS-05301-GAUSS-05400.md)
+    + [GAUSS 05401 - GAUSS 05500](/reference-guide/error-code-reference/55-GAUSS-05401-GAUSS-05500.md)
+    + [GAUSS 05501 - GAUSS 05600](/reference-guide/error-code-reference/56-GAUSS-05501-GAUSS-05600.md)
+    + [GAUSS 05601 - GAUSS 05700](/reference-guide/error-code-reference/57-GAUSS-05601-GAUSS-05700.md)
+    + [GAUSS 05701 - GAUSS 05800](/reference-guide/error-code-reference/58-GAUSS-05701-GAUSS-05800.md)
+    + [GAUSS 05801 - GAUSS 05900](/reference-guide/error-code-reference/59-GAUSS-05801-GAUSS-05900.md)
+    + [GAUSS 05901 - GAUSS 06000](/reference-guide/error-code-reference/60-GAUSS-05901-GAUSS-06000.md)
+    + [GAUSS 06001 - GAUSS 06100](/reference-guide/error-code-reference/61-GAUSS-06001-GAUSS-06100.md)
+    + [GAUSS 06101 - GAUSS 06200](/reference-guide/error-code-reference/62-GAUSS-06101-GAUSS-06200.md)
+    + [GAUSS 06201 - GAUSS 06300](/reference-guide/error-code-reference/63-GAUSS-06201-GAUSS-06300.md)
+    + [GAUSS 06301 - GAUSS 06400](/reference-guide/error-code-reference/64-GAUSS-06301-GAUSS-06400.md)
+    + [GAUSS 06401 - GAUSS 06500](/reference-guide/error-code-reference/65-GAUSS-06401-GAUSS-06500.md)
+    + [GAUSS 06501 - GAUSS 06600](/reference-guide/error-code-reference/66-GAUSS-06501-GAUSS-06600.md)
+    + [GAUSS 06601 - GAUSS 06700](/reference-guide/error-code-reference/67-GAUSS-06601-GAUSS-06700.md)
+    + [GAUSS 06701 - GAUSS 06800](/reference-guide/error-code-reference/68-GAUSS-06701-GAUSS-06800.md)
+    + [GAUSS 06801 - GAUSS 06900](/reference-guide/error-code-reference/69-GAUSS-06801-GAUSS-06900.md)
+    + [GAUSS 06901 - GAUSS 07000](/reference-guide/error-code-reference/70-GAUSS-06901-GAUSS-07000.md)
+    + [GAUSS 07001 - GAUSS 07100](/reference-guide/error-code-reference/71-GAUSS-07001-GAUSS-07100.md)
+    + [GAUSS 07101 - GAUSS 07200](/reference-guide/error-code-reference/72-GAUSS-07101-GAUSS-07200.md)
+    + [GAUSS 07201 - GAUSS 07300](/reference-guide/error-code-reference/73-GAUSS-07201-GAUSS-07300.md)
+    + [GAUSS 07301 - GAUSS 07400](/reference-guide/error-code-reference/74-GAUSS-07301-GAUSS-07400.md)
+    + [GAUSS 07401 - GAUSS 07480](/reference-guide/error-code-reference/75-GAUSS-07401-GAUSS-07480.md)
+    + [GAUSS 50000 - GAUSS 50999](/reference-guide/error-code-reference/76-GAUSS-50000-GAUSS-50999.md)
+    + [GAUSS 51000 - GAUSS 51999](/reference-guide/error-code-reference/77-GAUSS-51000-GAUSS-51999.md)
+    + [GAUSS 52000 - GAUSS 52999](/reference-guide/error-code-reference/78-GAUSS-52000-GAUSS-52999.md)
+    + [GAUSS 53000 - GAUSS 53699](/reference-guide/error-code-reference/79-GAUSS-53000-GAUSS-53699.md)
+  + 错误日志信息参考
+    + [内核错误信息](/reference-guide/error-log-reference/kernel-error-message.md)
++ [源码解析](/source-code-parsing.md)
++ 常见问题解答 (FAQs)
+  + [产品FAQs](/faqs/product-faqs.md)
+  + [应用开发FAQs](/faqs/application-development-faqs.md)
+  + [部署运维FAQs](/faqs/deployment-and-maintenance-faqs.md)
+  + [升级FAQs](/faqs/upgrade-faqs.md)
+  + [高可用FAQs](/faqs/high-availability-faqs.md)
+  + [迁移FAQs](/faqs/migration-faqs.md)
++ [术语表](/glossary.md)
diff --git a/product/zh/docs-mogdb/v3.0/toc_about.md b/product/zh/docs-mogdb/v3.0/toc_about.md
new file mode 100644
index 0000000000000000000000000000000000000000..1b9f203c8ed0a6afcd12f2a8108a424f85aa47ba
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/toc_about.md
@@ -0,0 +1,24 @@
+<!-- markdownlint-disable MD007 -->
+<!-- markdownlint-disable MD041 -->
+# MogDB Documentation 3.0
+
+## 关于MogDB
+
++ [MogDB简介](/overview.md)
++ [MogDB与openGauss](/about-mogdb/MogDB-compared-to-openGauss.md)
++ [MogDB发行说明](/about-mogdb/mogdb-release-notes.md)
++ 高可用和高性能
+  + [高可用测试](/about-mogdb/test-report/ha/MogDB-ha-test-report.md)
+  + 性能测试
+    + [性能测试简述](/about-mogdb/test-report/performance/1-performance-test-overview.md)
+    + [MogDB on 鲲鹏性能测试](/about-mogdb/test-report/performance/2-mogdb-on-kunpeng-performance-test-report.md)
+    + [MogDB on x86性能测试](/about-mogdb/test-report/performance/3-mogdb-on-x86-performance-test-report.md)
++ 开源组件
+  + [容器版本的MogDB](/about-mogdb/open-source-components/2-docker-based-mogdb.md)
+  + [compat-tools](/about-mogdb/open-source-components/compat-tools.md)
+  + [mogdb-monitor](/about-mogdb/open-source-components/mogdb-monitor.md)
+  + [wal2json](/about-mogdb/open-source-components/5-wal2json-extention-for-mogdb&opengauss.md)
+  + [mog_filedump](/about-mogdb/open-source-components/mog_filedump.md)
+  + [mog_xlogdump](/about-mogdb/open-source-components/mog_xlogdump.md)
++ [使用限制](/about-mogdb/usage-limitations.md)
++ [法律声明](/about-mogdb/terms-of-use.md)
diff --git a/product/zh/docs-mogdb/v3.0/toc_common-faults-and-identification.md b/product/zh/docs-mogdb/v3.0/toc_common-faults-and-identification.md
new file mode 100644
index 0000000000000000000000000000000000000000..c143e781382e8cb90ef24f1ce9a688f45bb5869f
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/toc_common-faults-and-identification.md
@@ -0,0 +1,42 @@
+<!-- markdownlint-disable MD007 -->
+<!-- markdownlint-disable MD041 -->
+# MogDB Documentation 3.0
+
+## 故障诊断
+
++ [常见故障定位手段](/common-faults-and-identification/common-fault-locating-methods.md)
++ 常见故障定位案例
+  + core问题定位
+    + [磁盘满故障引起的core问题](/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/1-core-dump-occurs-due-to-full-disk-space.md)
+    + [GUC参数log_directory设置不正确引起的core问题](/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/2-core-dump-occurs-due-to-incorrect-settings-of-guc-parameter-log-directory.md)
+    + [开启RemoveIPC引起的core问题](/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/3-core-dump-occurs-when-removeipc-is-enabled.md)
+    + [x86下安装完成后发生coredump](/common-faults-and-identification/common-fault-locating-cases/1-core-fault-locating/4-core-dump-occurs-after-installation-on-x86.md)
+  + 权限/会话/数据类型问题定位
+    + [强制结束指定的问题会话](/common-faults-and-identification/common-fault-locating-cases/13-forcibly-terminating-a-session.md)
+    + [不同用户查询同表显示数据不同](/common-faults-and-identification/common-fault-locating-cases/19-different-data-is-displayed.md)
+    + [业务运行时整数转换错](/common-faults-and-identification/common-fault-locating-cases/22-an-error-occurs-during-integer-conversion.md)
+  + 服务/高可用/并发问题定位
+    + [备机处于need repair(WAL)状态问题](/common-faults-and-identification/common-fault-locating-cases/3-standby-node-in-the-need-repair-state.md)
+    + [服务启动失败](/common-faults-and-identification/common-fault-locating-cases/5-service-startup-failure.md)
+    + [switchover操作时，主机降备卡住](/common-faults-and-identification/common-fault-locating-cases/9-primary-node-is-hung-in-demoting.md)
+    + [高并发报错”too many clients already”或无法创建线程](/common-faults-and-identification/common-fault-locating-cases/23-too-many-clients-already.md)
+  + 表/分区表问题定位
+    + [VACUUM FULL一张表后，表文件大小无变化](/common-faults-and-identification/common-fault-locating-cases/17-table-size-does-not-change.md)
+    + [执行修改表分区操作时报错](/common-faults-and-identification/common-fault-locating-cases/18-an-error-is-reported-when-the-table-partition-is-modified.md)
+  + 文件系统/磁盘/内存问题定位
+    + [在XFS文件系统中，使用du命令查询数据文件大小大于文件实际大小](/common-faults-and-identification/common-fault-locating-cases/7-after-you-run-the-du-command.md)
+    + [在XFS文件系统中，出现文件损坏](/common-faults-and-identification/common-fault-locating-cases/8-file-is-damaged-in-the-xfs-file-system.md)
+    + [内存不足问题](/common-faults-and-identification/common-fault-locating-cases/4-insufficient-memory.md)
+    + [出现“Error:No space left on device”提示](/common-faults-and-identification/common-fault-locating-cases/6-error-no-space-left-on-device-is-displayed.md)
+    + [TPCC运行时，注入磁盘满故障，TPCC卡住的问题](/common-faults-and-identification/common-fault-locating-cases/2-when-the-tpcc-is-running.md)
+    + [磁盘空间达到阈值，数据库只读](/common-faults-and-identification/common-fault-locating-cases/10-disk-space-usage-reaches-the-threshold.md)
+  + SQL问题定位
+    + [执行 SQL 语句时，提示 Lock wait timeout](/common-faults-and-identification/common-fault-locating-cases/16-lock-wait-timeout-is-displayed.md)
+    + [分析查询语句是否被阻塞](/common-faults-and-identification/common-fault-locating-cases/14-analyzing-whether-a-query-statement-is-blocked.md)
+    + [分析查询效率异常降低的问题](/common-faults-and-identification/common-fault-locating-cases/15-low-query-efficiency.md)
+    + [分析查询语句长时间运行的问题](/common-faults-and-identification/common-fault-locating-cases/11-slow-response-to-a-query-statement.md)
+    + [分析查询语句运行状态](/common-faults-and-identification/common-fault-locating-cases/12-analyzing-the-status-of-a-query-statement.md)
+  + 索引问题定位
+    + [修改索引时只调用索引名提示索引不存在](/common-faults-and-identification/common-fault-locating-cases/20-when-a-user-specifies-only-an-index-name.md)
+    + [重建索引失败](/common-faults-and-identification/common-fault-locating-cases/21-reindexing-fails.md)
+    + [btree 索引故障情况下应对策略](/common-faults-and-identification/common-fault-locating-cases/24-b-tree-index-faults.md)
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/toc_datatypes-and-sql.md b/product/zh/docs-mogdb/v3.0/toc_datatypes-and-sql.md
new file mode 100644
index 0000000000000000000000000000000000000000..cd7e9b8c5bf84597d4d6a6830da006b3255fdf80
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/toc_datatypes-and-sql.md
@@ -0,0 +1,275 @@
+<!-- markdownlint-disable MD007 -->
+<!-- markdownlint-disable MD041 -->
+
+# MogDB Documentation 3.0
+
+## 数据类型及SQL
+
++ 支持的数据类型
+  + [数值类型](/reference-guide/supported-data-types/1-numeric-data-types.md)
+  + [货币类型](/reference-guide/supported-data-types/2-monetary.md)
+  + [布尔类型](/reference-guide/supported-data-types/3-boolean-data-types.md)
+  + [枚举类型](/reference-guide/supported-data-types/4.1-enumerated-types.md)
+  + [字符类型](/reference-guide/supported-data-types/4-character-data-types.md)
+  + [二进制类型](/reference-guide/supported-data-types/5-binary-data-types.md)
+  + [日期/时间类型](/reference-guide/supported-data-types/6-date-time-types.md)
+  + [几何类型](/reference-guide/supported-data-types/7-geometric.md)
+  + [网络地址类型](/reference-guide/supported-data-types/8-network-address.md)
+  + [位串类型](/reference-guide/supported-data-types/9-bit-string-types.md)
+  + [文本搜索类型](/reference-guide/supported-data-types/10-text-search-types.md)
+  + [UUID类型](/reference-guide/supported-data-types/11-uuid-type.md)
+  + [JSON/JSONB类型](/reference-guide/supported-data-types/12-json-types.md)
+  + [HLL数据类型](/reference-guide/supported-data-types/13-HLL.md)
+  + [数组类型](/reference-guide/supported-data-types/13.0-array-types.md)
+  + [范围类型](/reference-guide/supported-data-types/13.1-range.md)
+  + [对象标识符类型](/reference-guide/supported-data-types/14-object-identifier-types.md)
+  + [伪类型](/reference-guide/supported-data-types/15-pseudo-types.md)
+  + [列存表支持的数据类型](/reference-guide/supported-data-types/16-data-types-supported-by-column-store-tables.md)
+  + [XML类型](/reference-guide/supported-data-types/17-xml-type.md)
+  + [账本数据库使用的数据类型](/reference-guide/supported-data-types/18-data-type-used-by-the-ledger-database.md)
++ SQL语法
+  + [ABORT](/reference-guide/sql-syntax/1-ABORT.md)
+  + [ALTER AGGREGATE](/reference-guide/sql-syntax/1.1-ALTER-AGGREGATE.md)
+  + [ALTER AUDIT POLICY](/reference-guide/sql-syntax/1.2-ALTER-AUDIT-POLICY.md)
+  + [ALTER DATABASE](/reference-guide/sql-syntax/2-ALTER-DATABASE.md)
+  + [ALTER DATA SOURCE](/reference-guide/sql-syntax/3-ALTER-DATA-SOURCE.md)
+  + [ALTER DEFAULT PRIVILEGES](/reference-guide/sql-syntax/4-ALTER-DEFAULT-PRIVILEGES.md)
+  + [ALTER DIRECTORY](/reference-guide/sql-syntax/5-ALTER-DIRECTORY.md)
+  + [ALTER EXTENSION](/reference-guide/sql-syntax/5.1-ALTER-EXTENSION.md)
+  + [ALTER FOREIGN TABLE](/reference-guide/sql-syntax/6-ALTER-FOREIGN-TABLE.md)
+  + [ALTER FUNCTION](/reference-guide/sql-syntax/7-ALTER-FUNCTION.md)
+  + [ALTER GROUP](/reference-guide/sql-syntax/8-ALTER-GROUP.md)
+  + [ALTER INDEX](/reference-guide/sql-syntax/9-ALTER-INDEX.md)
+  + [ALTER LANGUAGE](/reference-guide/sql-syntax/9.1-ALTER-LANGUAGE.md)
+  + [ALTER LARGE OBJECT](/reference-guide/sql-syntax/10-ALTER-LARGE-OBJECT.md)
+  + [ALTER MASKING POLICY](/reference-guide/sql-syntax/10.1-ALTER-MASKING-POLICY.md)
+  + [ALTER MATERIALIZED VIEW](/reference-guide/sql-syntax/11-ALTER-MATERIALIZED-VIEW.md)
+  + [ALTER OPERATOR](/reference-guide/sql-syntax/11.1-ALTER-OPERATOR.md)
+  + [ALTER RESOURCE LABEL](/reference-guide/sql-syntax/11.2-ALTER-RESOURCE-LABEL.md)
+  + [ALTER RESOURCE POOL](/reference-guide/sql-syntax/11.3-ALTER-RESOURCE-POOL.md)
+  + [ALTER ROLE](/reference-guide/sql-syntax/12-ALTER-ROLE.md)
+  + [ALTER ROW LEVEL SECURITY POLICY](/reference-guide/sql-syntax/13-ALTER-ROW-LEVEL-SECURITY-POLICY.md)
+  + [ALTER RULE](/reference-guide/sql-syntax/14-ALTER-RULE.md)
+  + [ALTER SCHEMA](/reference-guide/sql-syntax/15-ALTER-SCHEMA.md)
+  + [ALTER SEQUENCE](/reference-guide/sql-syntax/16-ALTER-SEQUENCE.md)
+  + [ALTER SERVER](/reference-guide/sql-syntax/17-ALTER-SERVER.md)
+  + [ALTER SESSION](/reference-guide/sql-syntax/18-ALTER-SESSION.md)
+  + [ALTER SYNONYM](/reference-guide/sql-syntax/19-ALTER-SYNONYM.md)
+  + [ALTER SYSTEM KILL SESSION](/reference-guide/sql-syntax/20-ALTER-SYSTEM-KILL-SESSION.md)
+  + [ALTER SYSTEM SET](/reference-guide/sql-syntax/21-ALTER-SYSTEM-SET.md)
+  + [ALTER TABLE](/reference-guide/sql-syntax/22-ALTER-TABLE.md)
+  + [ALTER TABLE PARTITION](/reference-guide/sql-syntax/23-ALTER-TABLE-PARTITION.md)
+  + [ALTER TABLE SUBPARTITION](/reference-guide/sql-syntax/23.1-ALTER-TABLE-SUBPARTITION.md)
+  + [ALTER TABLESPACE](/reference-guide/sql-syntax/24-ALTER-TABLESPACE.md)
+  + [ALTER TEXT SEARCH CONFIGURATION](/reference-guide/sql-syntax/25-ALTER-TEXT-SEARCH-CONFIGURATION.md)
+  + [ALTER TEXT SEARCH DICTIONARY](/reference-guide/sql-syntax/26-ALTER-TEXT-SEARCH-DICTIONARY.md)
+  + [ALTER TRIGGER](/reference-guide/sql-syntax/27-ALTER-TRIGGER.md)
+  + [ALTER TYPE](/reference-guide/sql-syntax/28-ALTER-TYPE.md)
+  + [ALTER USER](/reference-guide/sql-syntax/29-ALTER-USER.md)
+  + [ALTER USER MAPPING](/reference-guide/sql-syntax/30-ALTER-USER-MAPPING.md)
+  + [ALTER VIEW](/reference-guide/sql-syntax/31-ALTER-VIEW.md)
+  + [ANALYZE | ANALYSE](/reference-guide/sql-syntax/32-ANALYZE-ANALYSE.md)
+  + [BEGIN](/reference-guide/sql-syntax/33-BEGIN.md)
+  + [CALL](/reference-guide/sql-syntax/34-CALL.md)
+  + [CHECKPOINT](/reference-guide/sql-syntax/35-CHECKPOINT.md)
+  + [CLEAN CONNECTION](/reference-guide/sql-syntax/35.1-CLEAN-CONNECTION.md)
+  + [CLOSE](/reference-guide/sql-syntax/36-CLOSE.md)
+  + [CLUSTER](/reference-guide/sql-syntax/37-CLUSTER.md)
+  + [COMMENT](/reference-guide/sql-syntax/38-COMMENT.md)
+  + [COMMIT | END](/reference-guide/sql-syntax/39-COMMIT-END.md)
+  + [COMMIT PREPARED](/reference-guide/sql-syntax/40-COMMIT-PREPARED.md)
+  + [CONNECT BY](/reference-guide/sql-syntax/139-CONNECT-BY.md)
+  + [COPY](/reference-guide/sql-syntax/41-COPY.md)
+  + [CREATE AGGREGATE](/reference-guide/sql-syntax/41.1-CREATE-AGGREGATE.md)
+  + [CREATE AUDIT POLICY](/reference-guide/sql-syntax/41.2-CREATE-AUDIT-POLICY.md)
+  + [CREATE CAST](/reference-guide/sql-syntax/41.3-CREATE-CAST.md)
+  + [CREATE CLIENT MASTER KEY](/reference-guide/sql-syntax/42-CREATE-CLIENT-MASTER-KEY.md)
+  + [CREATE COLUMN ENCRYPTION KEY](/reference-guide/sql-syntax/43-CREATE-COLUMN-ENCRYPTION-KEY.md)
+  + [CREATE DATABASE](/reference-guide/sql-syntax/44-CREATE-DATABASE.md)
+  + [CREATE DATA SOURCE](/reference-guide/sql-syntax/45-CREATE-DATA-SOURCE.md)
+  + [CREATE DIRECTORY](/reference-guide/sql-syntax/46-CREATE-DIRECTORY.md)
+  + [CREATE EXTENSION](/reference-guide/sql-syntax/46.1-CREATE-EXTENSION.md)
+  + [CREATE FOREIGN TABLE](/reference-guide/sql-syntax/47-CREATE-FOREIGN-TABLE.md)
+  + [CREATE FUNCTION](/reference-guide/sql-syntax/48-CREATE-FUNCTION.md)
+  + [CREATE GROUP](/reference-guide/sql-syntax/49-CREATE-GROUP.md)
+  + [CREATE INCREMENTAL MATERIALIZED VIEW](/reference-guide/sql-syntax/49.1-CREATE-INCREMENTAL-MATERIALIZED-VIEW.md)
+  + [CREATE INDEX](/reference-guide/sql-syntax/50-CREATE-INDEX.md)
+  + [CREATE LANGUAGE](/reference-guide/sql-syntax/50.1-CREATE-LANGUAGE.md)
+  + [CREATE MASKING POLICY](/reference-guide/sql-syntax/50.2-CREATE-MASKING-POLICY.md)
+  + [CREATE MATERIALIZED VIEW](/reference-guide/sql-syntax/51-CREATE-MATERIALIZED-VIEW.md)
+  + [CREATE MODEL](/reference-guide/sql-syntax/50.3-CREATE-MODEL.md)
+  + [CREATE OPERATOR](/reference-guide/sql-syntax/51.1-CREATE-OPERATOR.md)
+  + [CREATE PACKAGE](/reference-guide/sql-syntax/51.2-CREATE-PACKAGE.md)
+  + [CREATE ROW LEVEL SECURITY POLICY](/reference-guide/sql-syntax/52-CREATE-ROW-LEVEL-SECURITY-POLICY.md)
+  + [CREATE PROCEDURE](/reference-guide/sql-syntax/53-CREATE-PROCEDURE.md)
+  + [CREATE RESOURCE LABEL](/reference-guide/sql-syntax/53.1-CREATE-RESOURCE-LABEL.md)
+  + [CREATE RESOURCE POOL](/reference-guide/sql-syntax/53.2-CREATE-RESOURCE-POOL.md)
+  + [CREATE ROLE](/reference-guide/sql-syntax/54-CREATE-ROLE.md)
+  + [CREATE RULE](/reference-guide/sql-syntax/55-CREATE-RULE.md)
+  + [CREATE SCHEMA](/reference-guide/sql-syntax/56-CREATE-SCHEMA.md)
+  + [CREATE SEQUENCE](/reference-guide/sql-syntax/57-CREATE-SEQUENCE.md)
+  + [CREATE SERVER](/reference-guide/sql-syntax/58-CREATE-SERVER.md)
+  + [CREATE SYNONYM](/reference-guide/sql-syntax/59-CREATE-SYNONYM.md)
+  + [CREATE TABLE](/reference-guide/sql-syntax/60-CREATE-TABLE.md)
+  + [CREATE TABLE AS](/reference-guide/sql-syntax/61-CREATE-TABLE-AS.md)
+  + [CREATE TABLE PARTITION](/reference-guide/sql-syntax/62-CREATE-TABLE-PARTITION.md)
+  + [CREATE TABLE SUBPARTITION](/reference-guide/sql-syntax/62.1-CREATE-TABLE-SUBPARTITION.md)
+  + [CREATE TABLESPACE](/reference-guide/sql-syntax/63-CREATE-TABLESPACE.md)
+  + [CREATE TEXT SEARCH CONFIGURATION](/reference-guide/sql-syntax/64-CREATE-TEXT-SEARCH-CONFIGURATION.md)
+  + [CREATE TEXT SEARCH DICTIONARY](/reference-guide/sql-syntax/65-CREATE-TEXT-SEARCH-DICTIONARY.md)
+  + [CREATE TRIGGER](/reference-guide/sql-syntax/66-CREATE-TRIGGER.md)
+  + [CREATE TYPE](/reference-guide/sql-syntax/67-CREATE-TYPE.md)
+  + [CREATE USER](/reference-guide/sql-syntax/68-CREATE-USER.md)
+  + [CREATE USER MAPPING](/reference-guide/sql-syntax/69-CREATE-USER-MAPPING.md)
+  + [CREATE VIEW](/reference-guide/sql-syntax/70-CREATE-VIEW.md)
+  + [CREATE WEAK PASSWORD DICTIONARY](/reference-guide/sql-syntax/70.1-CREATE-WEAK-PASSWORD-DICTIONARY.md)
+  + [CURSOR](/reference-guide/sql-syntax/71-CURSOR.md)
+  + [DEALLOCATE](/reference-guide/sql-syntax/72-DEALLOCATE.md)
+  + [DECLARE](/reference-guide/sql-syntax/73-DECLARE.md)
+  + [DELETE](/reference-guide/sql-syntax/74-DELETE.md)
+  + [DO](/reference-guide/sql-syntax/75-DO.md)
+  + [DROP AGGREGATE](/reference-guide/sql-syntax/75.1-DROP-AGGREGATE.md)
+  + [DROP AUDIT POLICY](/reference-guide/sql-syntax/75.2-DROP-AUDIT-POLICY.md)
+  + [DROP CAST](/reference-guide/sql-syntax/75.3-DROP-CAST.md)
+  + [DROP CLIENT MASTER KEY](/reference-guide/sql-syntax/76-DROP-CLIENT-MASTER-KEY.md)
+  + [DROP COLUMN ENCRYPTION KEY](/reference-guide/sql-syntax/77-DROP-COLUMN-ENCRYPTION-KEY.md)
+  + [DROP DATABASE](/reference-guide/sql-syntax/78-DROP-DATABASE.md)
+  + [DROP DATA SOURCE](/reference-guide/sql-syntax/79-DROP-DATA-SOURCE.md)
+  + [DROP DIRECTORY](/reference-guide/sql-syntax/80-DROP-DIRECTORY.md)
+  + [DROP EXTENSION](/reference-guide/sql-syntax/80.1-DROP-EXTENSION.md)
+  + [DROP FOREIGN TABLE](/reference-guide/sql-syntax/81-DROP-FOREIGN-TABLE.md)
+  + [DROP FUNCTION](/reference-guide/sql-syntax/82-DROP-FUNCTION.md)
+  + [DROP GROUP](/reference-guide/sql-syntax/83-DROP-GROUP.md)
+  + [DROP INDEX](/reference-guide/sql-syntax/84-DROP-INDEX.md)
+  + [DROP LANGUAGE](/reference-guide/sql-syntax/84.1-DROP-LANGUAGE.md)
+  + [DROP MASKING POLICY](/reference-guide/sql-syntax/84.2-DROP-MASKING-POLICY.md)
+  + [DROP MATERIALIZED VIEW](/reference-guide/sql-syntax/85-DROP-MATERIALIZED-VIEW.md)
+  + [DROP MODEL](/reference-guide/sql-syntax/84.3-DROP-MODEL.md)
+  + [DROP OPERATOR](/reference-guide/sql-syntax/85.1-DROP-OPERATOR.md)
+  + [DROP OWNED](/reference-guide/sql-syntax/86-DROP-OWNED.md)
+  + [DROP PACKAGE](/reference-guide/sql-syntax/86.3-DROP-PACKAGE.md)
+  + [DROP PROCEDURE](/reference-guide/sql-syntax/88-DROP-PROCEDURE.md)
+  + [DROP RESOURCE LABEL](/reference-guide/sql-syntax/86.1-DROP-RESOURCE-LABEL.md)
+  + [DROP RESOURCE POOL](/reference-guide/sql-syntax/86.2-DROP-RESOURCE-POOL.md)
+  + [DROP ROW LEVEL SECURITY POLICY](/reference-guide/sql-syntax/87-DROP-ROW-LEVEL-SECURITY-POLICY.md)
+  + [DROP ROLE](/reference-guide/sql-syntax/89-DROP-ROLE.md)
+  + [DROP RULE](/reference-guide/sql-syntax/90-DROP-RULE.md)
+  + [DROP SCHEMA](/reference-guide/sql-syntax/91-DROP-SCHEMA.md)
+  + [DROP SEQUENCE](/reference-guide/sql-syntax/92-DROP-SEQUENCE.md)
+  + [DROP SERVER](/reference-guide/sql-syntax/93-DROP-SERVER.md)
+  + [DROP SYNONYM](/reference-guide/sql-syntax/94-DROP-SYNONYM.md)
+  + [DROP TABLE](/reference-guide/sql-syntax/95-DROP-TABLE.md)
+  + [DROP TABLESPACE](/reference-guide/sql-syntax/96-DROP-TABLESPACE.md)
+  + [DROP TEXT SEARCH CONFIGURATION](/reference-guide/sql-syntax/97-DROP-TEXT-SEARCH-CONFIGURATION.md)
+  + [DROP TEXT SEARCH DICTIONARY](/reference-guide/sql-syntax/98-DROP-TEXT-SEARCH-DICTIONARY.md)
+  + [DROP TRIGGER](/reference-guide/sql-syntax/99-DROP-TRIGGER.md)
+  + [DROP TYPE](/reference-guide/sql-syntax/100-DROP-TYPE.md)
+  + [DROP USER](/reference-guide/sql-syntax/101-DROP-USER.md)
+  + [DROP USER MAPPING](/reference-guide/sql-syntax/102-DROP-USER-MAPPING.md)
+  + [DROP VIEW](/reference-guide/sql-syntax/103-DROP-VIEW.md)
+  + [DROP WEAK PASSWORD DICTIONARY](/reference-guide/sql-syntax/103.1-DROP-WEAK-PASSWORD-DICTIONARY.md)
+  + [EXECUTE](/reference-guide/sql-syntax/104-EXECUTE.md)
+  + [EXECUTE DIRECT](/reference-guide/sql-syntax/104.1-EXECUTE-DIRECT.md)
+  + [EXPLAIN](/reference-guide/sql-syntax/105-EXPLAIN.md)
+  + [EXPLAIN PLAN](/reference-guide/sql-syntax/106-EXPLAIN-PLAN.md)
+  + [FETCH](/reference-guide/sql-syntax/107-FETCH.md)
+  + [GRANT](/reference-guide/sql-syntax/108-GRANT.md)
+  + [INSERT](/reference-guide/sql-syntax/109-INSERT.md)
+  + [LOCK](/reference-guide/sql-syntax/110-LOCK.md)
+  + [MOVE](/reference-guide/sql-syntax/111-MOVE.md)
+  + [MERGE INTO](/reference-guide/sql-syntax/112-MERGE-INTO.md)
+  + [PREDICT BY](/reference-guide/sql-syntax/112.1-PREDICT-BY.md)
+  + [PREPARE](/reference-guide/sql-syntax/113-PREPARE.md)
+  + [PREPARE TRANSACTION](/reference-guide/sql-syntax/114-PREPARE-TRANSACTION.md)
+  + [PURGE](/reference-guide/sql-syntax/114.1-PURGE.md)
+  + [REASSIGN OWNED](/reference-guide/sql-syntax/115-REASSIGN-OWNED.md)
+  + [REFRESH INCREMENTAL MATERIALIZED VIEW](/reference-guide/sql-syntax/115.1-REFRESH-INCREMENTAL-MATERIALIZED-VIEW.md)
+  + [REFRESH MATERIALIZED VIEW](/reference-guide/sql-syntax/116-REFRESH-MATERIALIZED-VIEW.md)
+  + [REINDEX](/reference-guide/sql-syntax/117-REINDEX.md)
+  + [RELEASE SAVEPOINT](/reference-guide/sql-syntax/118-RELEASE-SAVEPOINT.md)
+  + [RESET](/reference-guide/sql-syntax/119-RESET.md)
+  + [REVOKE](/reference-guide/sql-syntax/120-REVOKE.md)
+  + [ROLLBACK](/reference-guide/sql-syntax/121-ROLLBACK.md)
+  + [ROLLBACK PREPARED](/reference-guide/sql-syntax/122-ROLLBACK-PREPARED.md)
+  + [ROLLBACK TO SAVEPOINT](/reference-guide/sql-syntax/123-ROLLBACK-TO-SAVEPOINT.md)
+  + [SAVEPOINT](/reference-guide/sql-syntax/124-SAVEPOINT.md)
+  + [SELECT](/reference-guide/sql-syntax/125-SELECT.md)
+  + [SELECT INTO](/reference-guide/sql-syntax/126-SELECT-INTO.md)
+  + [SET](/reference-guide/sql-syntax/127-SET.md)
+  + [SET CONSTRAINTS](/reference-guide/sql-syntax/128-SET-CONSTRAINTS.md)
+  + [SET ROLE](/reference-guide/sql-syntax/129-SET-ROLE.md)
+  + [SET SESSION AUTHORIZATION](/reference-guide/sql-syntax/130-SET-SESSION-AUTHORIZATION.md)
+  + [SET TRANSACTION](/reference-guide/sql-syntax/131-SET-TRANSACTION.md)
+  + [SHOW](/reference-guide/sql-syntax/132-SHOW.md)
+  + [SHUTDOWN](/reference-guide/sql-syntax/133-SHUTDOWN.md)
+  + [SNAPSHOT](/reference-guide/sql-syntax/133.1-SNAPSHOT.md)
+  + [START TRANSACTION](/reference-guide/sql-syntax/134-START-TRANSACTION.md)
+  + [TIMECAPSULE TABLE](/reference-guide/sql-syntax/134.1-TIMECAPSULE-TABLE.md)
+  + [TRUNCATE](/reference-guide/sql-syntax/135-TRUNCATE.md)
+  + [UPDATE](/reference-guide/sql-syntax/136-UPDATE.md)
+  + [VACUUM](/reference-guide/sql-syntax/137-VACUUM.md)
+  + [VALUES](/reference-guide/sql-syntax/138-VALUES.md)
++ SQL参考
+  + [MogDB SQL](/reference-guide/sql-reference/1-mogdb-sql.md)
+  + [关键字](/reference-guide/sql-reference/2-keywords.md)
+  + [常量与宏](/reference-guide/sql-reference/3-constant-and-macro.md)
+  + 表达式
+    + [简单表达式](/reference-guide/sql-reference/4-expressions/1-simple-expressions.md)
+    + [条件表达式](/reference-guide/sql-reference/4-expressions/2-condition-expressions.md)
+    + [子查询表达式](/reference-guide/sql-reference/4-expressions/3-subquery-expressions.md)
+    + [数组表达式](/reference-guide/sql-reference/4-expressions/4-array-expressions.md)
+    + [行表达式](/reference-guide/sql-reference/4-expressions/5-row-expressions.md)
+  + 类型转换
+    + [概述](/reference-guide/sql-reference/5-type-conversion/1-type-conversion-overview.md)
+    + [操作符](/reference-guide/sql-reference/5-type-conversion/2-operators.md)
+    + [函数](/reference-guide/sql-reference/5-type-conversion/3-functions.md)
+    + [值存储](/reference-guide/sql-reference/5-type-conversion/4-value-storage.md)
+    + [UNION，CASE和相关构造](/reference-guide/sql-reference/5-type-conversion/5-union-case-and-related-constructs.md)
+  + 全文检索
+    + 介绍
+      + [全文检索概述](/reference-guide/sql-reference/6-full-text-search/1-introduction/1-full-text-retrieval.md)
+      + [文档概念](/reference-guide/sql-reference/6-full-text-search/1-introduction/2-what-is-a-document.md)
+      + [基本文本匹配](/reference-guide/sql-reference/6-full-text-search/1-introduction/3-basic-text-matching.md)
+      + [分词器](/reference-guide/sql-reference/6-full-text-search/1-introduction/4-configurations.md)
+    + 表和索引
+      + [搜索表](/reference-guide/sql-reference/6-full-text-search/2-tables-and-indexes/1-searching-a-table.md)
+      + [创建索引](/reference-guide/sql-reference/6-full-text-search/2-tables-and-indexes/2-creating-an-index.md)
+      + [索引使用约束](/reference-guide/sql-reference/6-full-text-search/2-tables-and-indexes/3-constraints-on-index-use.md)
+    + 控制文本搜索
+      + [解析文档](/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/1-parsing-documents.md)
+      + [解析查询](/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/2-parsing-queries.md)
+      + [排序查询结果](/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/3-ranking-search-results.md)
+      + [高亮搜索结果](/reference-guide/sql-reference/6-full-text-search/3-controlling-text-search/4-highlighting-results.md)
+    + 附加功能
+      + [处理tsvector](/reference-guide/sql-reference/6-full-text-search/4-additional-features/1-manipulating-tsvector.md)
+      + [处理查询](/reference-guide/sql-reference/6-full-text-search/4-additional-features/2-manipulating-queries.md)
+      + [查询重写](/reference-guide/sql-reference/6-full-text-search/4-additional-features/3-rewriting-queries.md)
+      + [收集文献统计](/reference-guide/sql-reference/6-full-text-search/4-additional-features/4-gathering-document-statistics.md)
+    + [解析器](/reference-guide/sql-reference/6-full-text-search/5-parser.md)
+    + 词典
+      + [词典概述](/reference-guide/sql-reference/6-full-text-search/6-dictionaries/1-dictionaries-overview.md)
+      + [停用词](/reference-guide/sql-reference/6-full-text-search/6-dictionaries/2-stop-words.md)
+      + [Simple词典](/reference-guide/sql-reference/6-full-text-search/6-dictionaries/3-simple-dictionary.md)
+      + [Synonym词典](/reference-guide/sql-reference/6-full-text-search/6-dictionaries/4-synonym-dictionary.md)
+      + [Thesaurus词典](/reference-guide/sql-reference/6-full-text-search/6-dictionaries/5-thesaurus-dictionary.md)
+      + [Ispell词典](/reference-guide/sql-reference/6-full-text-search/6-dictionaries/6-ispell-dictionary.md)
+      + [Snowball词典](/reference-guide/sql-reference/6-full-text-search/6-dictionaries/7-snowball-dictionary.md)
+    + [配置示例](/reference-guide/sql-reference/6-full-text-search/7-configuration-examples.md)
+    + 测试和调试文本搜索
+      + [分词器测试](/reference-guide/sql-reference/6-full-text-search/8-testing-and-debugging-text-search/1-testing-a-configuration.md)
+      + [解析器测试](/reference-guide/sql-reference/6-full-text-search/8-testing-and-debugging-text-search/2-testing-a-parser.md)
+      + [词典测试](/reference-guide/sql-reference/6-full-text-search/8-testing-and-debugging-text-search/3-testing-a-dictionary.md)
+    + [限制约束](/reference-guide/sql-reference/6-full-text-search/9-limitations.md)
+  + [系统操作](/reference-guide/sql-reference/7-system-operation.md)
+  + [事务控制](/reference-guide/sql-reference/8-controlling-transactions.md)
+  + [DDL语法一览表](/reference-guide/sql-reference/9-ddl-syntax-overview.md)
+  + [DML语法一览表](/reference-guide/sql-reference/10-dml-syntax-overview.md)
+  + [DCL语法一览表](/reference-guide/sql-reference/11-dcl-syntax-overview.md)
+  + 附录
+    + GIN索引
+      + [介绍](/reference-guide/sql-reference/13-appendix/1-gin-indexes/1-introduction.md)
+      + [扩展性](/reference-guide/sql-reference/13-appendix/1-gin-indexes/2-scalability.md)
+      + [实现](/reference-guide/sql-reference/13-appendix/1-gin-indexes/3-implementation.md)
+      + [GIN提示与技巧](/reference-guide/sql-reference/13-appendix/1-gin-indexes/4-gin-tips-and-tricks.md)
+    + [扩展函数](/reference-guide/sql-reference/13-appendix/2-extended-functions.md)
+    + [扩展语法](/reference-guide/sql-reference/13-appendix/3-extended-syntax.md)
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/toc_dev.md b/product/zh/docs-mogdb/v3.0/toc_dev.md
new file mode 100644
index 0000000000000000000000000000000000000000..dc64c3328f2a9c83cbd385845628bb92d115b4cd
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/toc_dev.md
@@ -0,0 +1,246 @@
+<!-- markdownlint-disable MD007 -->
+<!-- markdownlint-disable MD041 -->
+# MogDB Documentation 3.0
+
+## 开发者指南
+
++ 开发设计建议
+  + [概述](/developer-guide/development-and-design-proposal/overview-of-development-and-design-proposal.md)
+  + [数据库对象命名](/developer-guide/development-and-design-proposal/database-object-naming-conventions.md)
+  + 数据库对象设计
+    + [Database和Schema设计](/developer-guide/development-and-design-proposal/database-object-design/database-and-schema-design.md)
+    + [表设计](/developer-guide/development-and-design-proposal/database-object-design/table-design.md)
+    + [字段设计](/developer-guide/development-and-design-proposal/database-object-design/field-design.md)
+    + [约束设计](/developer-guide/development-and-design-proposal/database-object-design/constraint-design.md)
+    + [视图和关联表设计](/developer-guide/development-and-design-proposal/database-object-design/view-and-joined-table-design.md)
+  + 工具对接
+    + [JDBC配置](/developer-guide/development-and-design-proposal/tool-interconnection/jdbc-configuration.md)
+  + [SQL编写](/developer-guide/development-and-design-proposal/sql-compilation.md)
++ 应用程序开发教程
+  + [开发规范](/developer-guide/dev/1-development-specifications.md)
+  + 基于JDBC开发
+    + [概述](/developer-guide/dev/2-development-based-on-jdbc/1-development-based-on-jdbc-overview.md)
+    + [JDBC包、驱动类和环境类](/developer-guide/dev/2-development-based-on-jdbc/2-jdbc-package-driver-class-and-environment-class.md)
+    + [开发流程](/developer-guide/dev/2-development-based-on-jdbc/3-development-process.md)
+    + [加载驱动](/developer-guide/dev/2-development-based-on-jdbc/4-loading-the-driver.md)
+    + [连接数据库](/developer-guide/dev/2-development-based-on-jdbc/5-connecting-to-a-database.md)
+    + [连接数据库（以SSL方式）](/developer-guide/dev/2-development-based-on-jdbc/6-connecting-to-a-database-using-ssl.md)
+    + [执行SQL语句](/developer-guide/dev/2-development-based-on-jdbc/7-running-sql-statements.md)
+    + [处理结果集](/developer-guide/dev/2-development-based-on-jdbc/8-processing-data-in-a-result-set.md)
+    + [关闭连接](/developer-guide/dev/2-development-based-on-jdbc/9-closing-a-connection.md)
+    + [日志管理](/developer-guide/dev/2-development-based-on-jdbc/8.1-log-management.md)
+    + [示例：常用操作](/developer-guide/dev/2-development-based-on-jdbc/10-example-common-operations.md)
+    + [示例：重新执行应用SQL](/developer-guide/dev/2-development-based-on-jdbc/11-example-retrying-sql-queries-for-applications.md)
+    + [示例：通过本地文件导入导出数据](/developer-guide/dev/2-development-based-on-jdbc/12-example-importing-and-exporting-data-through-local-files.md)
+    + [示例：从MY向MogDB进行数据迁移](/developer-guide/dev/2-development-based-on-jdbc/13-example-2-migrating-data-from-a-my-database-to-mogdb.md)
+    + [示例：逻辑复制代码示例](/developer-guide/dev/2-development-based-on-jdbc/14-example-logic-replication-code.md)
+    + [示例：不同场景下连接数据库参数配置](/developer-guide/dev/2-development-based-on-jdbc/14.1-example-parameters-for-connecting-to-the-database-in-different-scenarios.md)
+    + JDBC接口参考
+      + [java.sql.Connection](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/1-java-sql-Connection.md)
+      + [java.sql.CallableStatement](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/2-java-sql-CallableStatement.md)
+      + [java.sql.DatabaseMetaData](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/3-java-sql-DatabaseMetaData.md)
+      + [java.sql.Driver](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/4-java-sql-Driver.md)
+      + [java.sql.PreparedStatement](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/5-java-sql-PreparedStatement.md)
+      + [java.sql.ResultSet](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/6-java-sql-ResultSet.md)
+      + [java.sql.ResultSetMetaData](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/7-java-sql-ResultSetMetaData.md)
+      + [java.sql.Statement](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/8-java-sql-Statement.md)
+      + [javax.sql.ConnectionPoolDataSource](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/9-javax-sql-ConnectionPoolDataSource.md)
+      + [javax.sql.DataSource](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/10-javax-sql-DataSource.md)
+      + [javax.sql.PooledConnection](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/11-javax-sql-PooledConnection.md)
+      + [javax.naming.Context](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/12-javax-naming-Context.md)
+      + [javax.naming.spi.InitialContextFactory](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/13-javax-naming-spi-InitialContextFactory.md)
+      + [CopyManager](/developer-guide/dev/2-development-based-on-jdbc/15-JDBC/14-CopyManager.md)
+  + 基于ODBC开发
+    + [概述](/developer-guide/dev/3-development-based-on-odbc/1-development-based-on-odbc-overview.md)
+    + [ODBC包及依赖的库和头文件](/developer-guide/dev/3-development-based-on-odbc/2-odbc-packages-dependent-libraries-and-header-files.md)
+    + [Linux下配置数据源](/developer-guide/dev/3-development-based-on-odbc/3-configuring-a-data-source-in-the-linux-os.md)
+    + [开发流程](/developer-guide/dev/3-development-based-on-odbc/4-development-process.md)
+    + [示例：常用功能和批量绑定](/developer-guide/dev/3-development-based-on-odbc/5-example-common-functions-and-batch-binding.md)
+    + [典型应用场景配置](/developer-guide/dev/3-development-based-on-odbc/5.1-typical-application-scenarios-and-configurations.md)
+    + ODBC接口参考
+      + [说明](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-0-odbc-overview.md)
+      + [SQLAllocEnv](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-1-SQLAllocEnv.md)
+      + [SQLAllocConnect](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-2-SQLAllocConnect.md)
+      + [SQLAllocHandle](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-3-SQLAllocHandle.md)
+      + [SQLAllocStmt](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-4-SQLAllocStmt.md)
+      + [SQLBindCol](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-5-SQLBindCol.md)
+      + [SQLBindParameter](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-6-SQLBindParameter.md)
+      + [SQLColAttribute](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-7-SQLColAttribute.md)
+      + [SQLConnect](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-8-SQLConnect.md)
+      + [SQLDisconnect](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-9-SQLDisconnect.md)
+      + [SQLExecDirect](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-10-SQLExecDirect.md)
+      + [SQLExecute](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-11-SQLExecute.md)
+      + [SQLFetch](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-12-SQLFetch.md)
+      + [SQLFreeStmt](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-13-SQLFreeStmt.md)
+      + [SQLFreeConnect](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-14-SQLFreeConnect.md)
+      + [SQLFreeHandle](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-15-SQLFreeHandle.md)
+      + [SQLFreeEnv](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-16-SQLFreeEnv.md)
+      + [SQLPrepare](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-17-SQLPrepare.md)
+      + [SQLGetData](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-18-SQLGetData.md)
+      + [SQLGetDiagRec](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-19-SQLGetDiagRec.md)
+      + [SQLSetConnectAttr](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-20-SQLSetConnectAttr.md)
+      + [SQLSetEnvAttr](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-21-SQLSetEnvAttr.md)
+      + [SQLSetStmtAttr](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-22-SQLSetStmtAttr.md)
+      + [示例](/developer-guide/dev/3-development-based-on-odbc/6-ODBC/2-23-Examples.md)
+  + 基于libpq开发
+    + [基于libpq开发](/developer-guide/dev/4-development-based-on-libpq/1-development-based-on-libpq.md)
+    + libpq接口参考
+      + 数据库连接控制函数
+        + [说明](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/1-database-connection-control-functions-overview.md)
+        + [PQconnectdbParams](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/2-PQconnectdbParams.md)
+        + [PQconnectdb](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/3-PQconnectdb.md)
+        + [PQconninfoParse](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/4-PQconninfoParse.md)
+        + [PQconnectStart](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/5-PQconnectStart.md)
+        + [PQerrorMessage](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/6-PQerrorMessage.md)
+        + [PQsetdbLogin](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/7-PQsetdbLogin.md)
+        + [PQfinish](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/8-PQfinish.md)
+        + [PQreset](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/9-PQreset.md)
+        + [PQstatus](/developer-guide/dev/4-development-based-on-libpq/2-libpq/1-database-connection-control-functions/10-PQstatus.md)
+      + 数据库执行语句函数
+        + [PQclear](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/1-PQclear.md)
+        + [PQexec](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/2-PQexec.md)
+        + [PQexecParams](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/3-PQexecParams.md)
+        + [PQexecParamsBatch](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/4-PQexecParamsBatch.md)
+        + [PQexecPrepared](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/5-PQexecPrepared.md)
+        + [PQexecPreparedBatch](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/6-PQexecPreparedBatch.md)
+        + [PQfname](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/7-PQfname.md)
+        + [PQgetvalue](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/8-PQgetvalue.md)
+        + [PQnfields](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/9-PQnfields.md)
+        + [PQntuples](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/10-PQntuples.md)
+        + [PQprepare](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/11-PQprepare.md)
+        + [PQresultStatus](/developer-guide/dev/4-development-based-on-libpq/2-libpq/2-database-statement-execution-functions/12-PQresultStatus.md)
+      + 异步命令处理
+        + [说明](/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/1-functions-for-asynchronous-command-processing-overview.md)
+        + [PQsendQuery](/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/2-PQsendQuery.md)
+        + [PQsendQueryParams](/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/3-PQsendQueryParams.md)
+        + [PQsendPrepare](/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/4-PQsendPrepare.md)
+        + [PQsendQueryPrepared](/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/5-PQsendQueryPrepared.md)
+        + [PQflush](/developer-guide/dev/4-development-based-on-libpq/2-libpq/3-functions-for-asynchronous-command-processing/6-PQflush.md)
+      + 取消正在处理的查询
+        + [PQgetCancel](/developer-guide/dev/4-development-based-on-libpq/2-libpq/4-functions-for-canceling-queries-in-progress/1-PQgetCancel.md)
+        + [PQfreeCancel](/developer-guide/dev/4-development-based-on-libpq/2-libpq/4-functions-for-canceling-queries-in-progress/2-PQfreeCancel.md)
+        + [PQcancel](/developer-guide/dev/4-development-based-on-libpq/2-libpq/4-functions-for-canceling-queries-in-progress/3-PQcancel.md)
+      + [示例](/developer-guide/dev/4-development-based-on-libpq/2-libpq/5-libpq-example.md)
+      + [链接字符](/developer-guide/dev/4-development-based-on-libpq/2-libpq/6-connection-characters.md)
+  + 基于Psycopg开发
+    + [基于Psycopg开发](/developer-guide/dev/4.1-psycopg-based-development/1-psycopg-based-development.md)
+    + [Psycopg包](/developer-guide/dev/4.1-psycopg-based-development/2-psycopg-package.md)
+    + [开发流程](/developer-guide/dev/4.1-psycopg-based-development/3.1-development-process.md)
+    + [加载驱动](/developer-guide/dev/4.1-psycopg-based-development/4-loading-a-driver.md)
+    + [连接数据库](/developer-guide/dev/4.1-psycopg-based-development/5.1-connecting-to-a-database.md)
+    + [执行SQL语句](/developer-guide/dev/4.1-psycopg-based-development/6-executing-sql-statements.md)
+    + [处理结果集](/developer-guide/dev/4.1-psycopg-based-development/7-processing-the-result-set.md)
+    + [关闭连接](/developer-guide/dev/4.1-psycopg-based-development/8-closing-the-connection.md)
+    + [连接数据库（SSL方式）](/developer-guide/dev/4.1-psycopg-based-development/9-connecting-to-the-database-using-ssl.md)
+    + [示例: 常用操作](/developer-guide/dev/4.1-psycopg-based-development/10.1-example-common-operations.md)
+    + Psycopg接口参考
+      + [psycopg2.connect()](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/1-psycopg2-connect.md)
+      + [connection.cursor()](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/2-connection-cursor.md)
+      + [cursor.execute(query,vars_list)](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/3-cursor-execute-query-vars-list.md)
+      + [curosr.executemany(query,vars_list)](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/4-curosr-executemany-query-vars-list.md)
+      + [connection.commit()](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/5-connection-commit.md)
+      + [connection.rollback()](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/6-connection-rollback.md)
+      + [cursor.fetchone()](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/7-cursor-fetchone.md)
+      + [cursor.fetchall()](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/8-cursor-fetchall.md)
+      + [cursor.close()](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/9-cursor-close.md)
+      + [connection.close()](/developer-guide/dev/4.1-psycopg-based-development/11-psycopg-api-reference/10-connection-close.md)
+  + [调试](/developer-guide/dev/5-commissioning.md)
+  + [附录](/developer-guide/dev/6-appendix.md)
++ [存储过程](/developer-guide/1-1-stored-procedure.md)
++ [用户自定义函数](/developer-guide/user-defined-functions.md)
++ PL/pgSQL-SQL过程语言
+  + [PL/pgSQL语言函数介绍](/developer-guide/plpgsql/1-1-plpgsql-overview.md)
+  + [数据类型](/developer-guide/plpgsql/1-2-data-types.md)
+  + [数据类型转换](/developer-guide/plpgsql/1-3-data-type-conversion.md)
+  + [数组和record](/developer-guide/plpgsql/1-4-arrays-and-records.md)
+  + [声明语法](/developer-guide/plpgsql/1-5-declare-syntax.md)
+  + [基本语句](/developer-guide/plpgsql/1-6-basic-statements.md)
+  + [动态语句](/developer-guide/plpgsql/1-7-dynamic-statements.md)
+  + [控制语句](/developer-guide/plpgsql/1-8-control-statements.md)
+  + [事务管理](/developer-guide/plpgsql/1-9-transaction-management.md)
+  + [其他语句](/developer-guide/plpgsql/1-10-other-statements.md)
+  + [游标](/developer-guide/plpgsql/1-11-cursors.md)
+  + [PKG_SERVICE接口](/developer-guide/plpgsql/1-14-pkg-service.md)
+  + [Retry管理](/developer-guide/plpgsql/1-12-retry-management.md)
+  + [调试](/developer-guide/plpgsql/1-13-debugging.md)
++ 定时任务
+  + [PKG_SERVICE接口](/developer-guide/scheduled-jobs/pkg-service.md)
++ 自治事务
+  + [介绍](/developer-guide/autonomous-transaction/1-introduction-to-autonomous-transaction.md)
+  + [存储过程支持自治事务](/developer-guide/autonomous-transaction/3-stored-procedure-supporting-autonomous-transaction.md)
+  + [匿名块支持自治事务](/developer-guide/autonomous-transaction/anonymous-block-supporting-autonomous-transaction.md)
+  + [函数支持自治事务](/developer-guide/autonomous-transaction/2-function-supporting-autonomous-transaction.md)
+  + [规格约束](/developer-guide/autonomous-transaction/4-restrictions.md)
++ 逻辑复制
+  + 逻辑解码
+    + [逻辑解码概述](/developer-guide/logical-replication/1-logical-decoding.md)
+    + [使用SQL函数接口进行逻辑解码](/developer-guide/logical-replication/2-logical-decoding-by-sql-function-interfaces.md)
++ Foreign Data Wrapper
+  + [介绍](/developer-guide/foreign-data-wrapper/fdw-introduction.md)
+  + [oracle_fdw](/developer-guide/foreign-data-wrapper/1-oracle_fdw.md)
+  + [mysql_fdw](/developer-guide/foreign-data-wrapper/2-mysql_fdw.md)
+  + [postgres_fdw](/developer-guide/foreign-data-wrapper/3-postgres_fdw.md)
+  + [file_fdw](/developer-guide/foreign-data-wrapper/file_fdw.md)
+  + [dblink](/developer-guide/foreign-data-wrapper/dblink.md)
++ 物化视图
+  + [物化视图概述](/developer-guide/materialized-view/1-materialized-view-overview.md)
+  + 全量物化视图
+    + [概述](/developer-guide/materialized-view/2-full-materialized-view/1-full-materialized-view-overview.md)
+    + [使用](/developer-guide/materialized-view/2-full-materialized-view/2-full-materialized-view-usage.md)
+    + [支持和约束](/developer-guide/materialized-view/2-full-materialized-view/3-full-materialized-view-support-and-constraints.md)
+  + 增量物化视图
+    + [概述](/developer-guide/materialized-view/3-incremental-materialized-view/1-incremental-materialized-view-overview.md)
+    + [使用](/developer-guide/materialized-view/3-incremental-materialized-view/2-incremental-materialized-view-usage.md)
+    + [支持和约束](/developer-guide/materialized-view/3-incremental-materialized-view/3-incremental-materialized-view-support-and-constraints.md)
++ AI特性
+  + [概述](/developer-guide/AI-features/1-AI-features-overview.md)
+  + Predictor AI查询时间预测
+    + [概述](/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-1-ai-query-time-forecasting-overview.md)
+    + [环境部署](/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-2-environment-deployment.md)
+    + [使用指导](/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-3-usage-guide.md)
+    + [最佳实践](/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-4-best-practices.md)
+    + [常见问题处理](/developer-guide/AI-features/2-predictor-ai-query-time-forecasting/2-5-faqs.md)
+  + X-Tuner 参数调优与诊断
+    + [概述](/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-1-x-tuner-overview.md)
+    + [使用准备](/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-2-preparations.md)
+    + [使用示例](/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-3-examples.md)
+    + [获取帮助](/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-4-obtaining-help-information.md)
+    + [命令参考](/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-5-command-reference.md)
+    + [常见问题处理](/developer-guide/AI-features/3-x-tuner-parameter-optimization-and-diagnosis/3-6-Troubleshooting.md)
+  + SQLdiag 慢SQL发现
+    + [概述](/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-1-overview.md)
+    + [使用指导](/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-2-usage-guide.md)
+    + [获取帮助](/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-3-obtaining-help-information.md)
+    + [命令参考](/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-4-command-reference.md)
+    + [常见问题处理](/developer-guide/AI-features/4-sqldiag-slow-sql-discovery/4-5-troubleshooting.md)
+  + Anomaly-detection 数据库指标采集、预测与异常监控
+    + [概述](/developer-guide/AI-features/5-a-detection-status-monitoring/5-1-overview.md)
+    + [使用准备](/developer-guide/AI-features/5-a-detection-status-monitoring/5-2-preparations.md)
+    + [添加监控参数](/developer-guide/AI-features/5-a-detection-status-monitoring/5-3-adding-monitoring-parameters.md)
+    + [获取帮助](/developer-guide/AI-features/5-a-detection-status-monitoring/5-4-obtaining-help-information.md)
+    + [使用示例](/developer-guide/AI-features/5-a-detection-status-monitoring/5-6-examples.md)
+    + [命令参考](/developer-guide/AI-features/5-a-detection-status-monitoring/5-5-command-reference.md)
+    + [AI_SERVER](/developer-guide/AI-features/5-a-detection-status-monitoring/5-7-ai-server.md)
+    + [AI_MANAGER](/developer-guide/AI-features/5-a-detection-status-monitoring/5-8-ai-manager.md)
+  + Index-advisor 索引推荐
+    + [单query索引推荐](/developer-guide/AI-features/6-index-advisor-index-recommendation/6-1-single-query-index-recommendation.md)
+    + [虚拟索引](/developer-guide/AI-features/6-index-advisor-index-recommendation/6-2-virtual-index.md)
+    + [workload级别索引推荐](/developer-guide/AI-features/6-index-advisor-index-recommendation/6-3-workload-level-index-recommendation.md)
+  + DeepSQL 库内AI算法
+    + [概述](/developer-guide/AI-features/7-deepsql/7-1-overview.md)
+    + [环境部署](/developer-guide/AI-features/7-deepsql/7-2-environment-deployment.md)
+    + [使用指导](/developer-guide/AI-features/7-deepsql/7-3-usage-guide.md)
+    + [最佳实践](/developer-guide/AI-features/7-deepsql/7-4-best-practices.md)
+    + [常见问题处理](/developer-guide/AI-features/7-deepsql/7-5-troubleshooting.md)
+  + DB4AI 数据库原生AI引擎
+    + [概述](/developer-guide/AI-features/8-db4ai/8-1-overview.md)
+    + [DB4AI-Snapshots数据版本管理](/developer-guide/AI-features/8-db4ai/8-2-db4ai-snapshots-for-data-version-management.md)
+    + [DB4AI-Query: 模型训练和推断](/developer-guide/AI-features/8-db4ai/8-3-db4ai-query-for-model-training-and-prediction.md)
+    + [plpython-fenced模式](/developer-guide/AI-features/8-db4ai/8-4-pl-python-fenced-mode.md)
++ 资源负载管理
+  + [资源负载管理概述](/developer-guide/resource-load-management/resource-load-management-overview.md)
+  + 资源管理准备
+    + [资源规划](/developer-guide/resource-load-management/resource-management-preparation/planning-resources.md)
+    + [启动资源负载管理功能](/developer-guide/resource-load-management/resource-management-preparation/enabling-resource-load-management.md)
+    + [设置控制组](/developer-guide/resource-load-management/resource-management-preparation/setting-a-cgroup.md)
+    + [创建资源池](/developer-guide/resource-load-management/resource-management-preparation/creating-a-resource-pool.md)
diff --git a/product/zh/docs-mogdb/v3.0/toc_error.md b/product/zh/docs-mogdb/v3.0/toc_error.md
new file mode 100644
index 0000000000000000000000000000000000000000..0c597352db0110e45a70cdb17a8c411deaf4aa3d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/toc_error.md
@@ -0,0 +1,89 @@
+<!-- markdownlint-disable MD007 -->
+<!-- markdownlint-disable MD041 -->
+# MogDB Documentation 3.0
+
+## 数据库报错信息
+
++ [SQL标准错误码说明](/reference-guide/error-code-reference/description-of-sql-error-codes.md)
++ [第三方库错误码说明](/reference-guide/error-code-reference/third-party-library-error-codes.md)
++ [GAUSS-00001 - GAUSS-00100](/reference-guide/error-code-reference/1-GAUSS-00001-GAUSS-00100.md)
++ [GAUSS-00101 - GAUSS-00200](/reference-guide/error-code-reference/2-GAUSS-00101-GAUSS-00200.md)
++ [GAUSS 00201 - GAUSS 00300](/reference-guide/error-code-reference/3-GAUSS-00201-GAUSS-00300.md)
++ [GAUSS 00301 - GAUSS 00400](/reference-guide/error-code-reference/4-GAUSS-00301-GAUSS-00400.md)
++ [GAUSS 00401 - GAUSS 00500](/reference-guide/error-code-reference/5-GAUSS-00401-GAUSS-00500.md)
++ [GAUSS 00501 - GAUSS 00600](/reference-guide/error-code-reference/6-GAUSS-00501-GAUSS-00600.md)
++ [GAUSS 00601 - GAUSS 00700](/reference-guide/error-code-reference/7-GAUSS-00601-GAUSS-00700.md)
++ [GAUSS 00701 - GAUSS 00800](/reference-guide/error-code-reference/8-GAUSS-00701-GAUSS-00800.md)
++ [GAUSS 00801 - GAUSS 00900](/reference-guide/error-code-reference/9-GAUSS-00801-GAUSS-00900.md)
++ [GAUSS 00901 - GAUSS 01000](/reference-guide/error-code-reference/10-GAUSS-00901-GAUSS-01000.md)
++ [GAUSS 01001 - GAUSS 01100](/reference-guide/error-code-reference/11-GAUSS-01001-GAUSS-01100.md)
++ [GAUSS 01101 - GAUSS 01200](/reference-guide/error-code-reference/12-GAUSS-01101-GAUSS-01200.md)
++ [GAUSS 01201 - GAUSS 01300](/reference-guide/error-code-reference/13-GAUSS-01201-GAUSS-01300.md)
++ [GAUSS 01301 - GAUSS 01400](/reference-guide/error-code-reference/14-GAUSS-01301-GAUSS-01400.md)
++ [GAUSS 01401 - GAUSS 01500](/reference-guide/error-code-reference/15-GAUSS-01401-GAUSS-01500.md)
++ [GAUSS 01501 - GAUSS 01600](/reference-guide/error-code-reference/16-GAUSS-01501-GAUSS-01600.md)
++ [GAUSS 01601 - GAUSS 01700](/reference-guide/error-code-reference/17-GAUSS-01601-GAUSS-01700.md)
++ [GAUSS 01701 - GAUSS 01800](/reference-guide/error-code-reference/18-GAUSS-01701-GAUSS-01800.md)
++ [GAUSS 01801 - GAUSS 01900](/reference-guide/error-code-reference/19-GAUSS-01801-GAUSS-01900.md)
++ [GAUSS 01901 - GAUSS 02000](/reference-guide/error-code-reference/20-GAUSS-01901-GAUSS-02000.md)
++ [GAUSS 02001 - GAUSS 02100](/reference-guide/error-code-reference/21-GAUSS-02001-GAUSS-02100.md)
++ [GAUSS 02101 - GAUSS 02200](/reference-guide/error-code-reference/22-GAUSS-02101-GAUSS-02200.md)
++ [GAUSS 02201 - GAUSS 02300](/reference-guide/error-code-reference/23-GAUSS-02201-GAUSS-02300.md)
++ [GAUSS 02301 - GAUSS 02400](/reference-guide/error-code-reference/24-GAUSS-02301-GAUSS-02400.md)
++ [GAUSS 02401 - GAUSS 02500](/reference-guide/error-code-reference/25-GAUSS-02401-GAUSS-02500.md)
++ [GAUSS 02501 - GAUSS 02600](/reference-guide/error-code-reference/26-GAUSS-02501-GAUSS-02600.md)
++ [GAUSS 02601 - GAUSS 02700](/reference-guide/error-code-reference/27-GAUSS-02601-GAUSS-02700.md)
++ [GAUSS 02701 - GAUSS 02800](/reference-guide/error-code-reference/28-GAUSS-02701-GAUSS-02800.md)
++ [GAUSS 02801 - GAUSS 02900](/reference-guide/error-code-reference/29-GAUSS-02801-GAUSS-02900.md)
++ [GAUSS 02901 - GAUSS 03000](/reference-guide/error-code-reference/30-GAUSS-02901-GAUSS-03000.md)
++ [GAUSS 03001 - GAUSS 03100](/reference-guide/error-code-reference/31-GAUSS-03001-GAUSS-03100.md)
++ [GAUSS 03101 - GAUSS 03200](/reference-guide/error-code-reference/32-GAUSS-03101-GAUSS-03200.md)
++ [GAUSS 03201 - GAUSS 03300](/reference-guide/error-code-reference/33-GAUSS-03201-GAUSS-03300.md)
++ [GAUSS 03301 - GAUSS 03400](/reference-guide/error-code-reference/34-GAUSS-03301-GAUSS-03400.md)
++ [GAUSS 03401 - GAUSS 03500](/reference-guide/error-code-reference/35-GAUSS-03401-GAUSS-03500.md)
++ [GAUSS 03501 - GAUSS 03600](/reference-guide/error-code-reference/36-GAUSS-03501-GAUSS-03600.md)
++ [GAUSS 03601 - GAUSS 03700](/reference-guide/error-code-reference/37-GAUSS-03601-GAUSS-03700.md)
++ [GAUSS 03701 - GAUSS 03800](/reference-guide/error-code-reference/38-GAUSS-03701-GAUSS-03800.md)
++ [GAUSS 03801 - GAUSS 03900](/reference-guide/error-code-reference/39-GAUSS-03801-GAUSS-03900.md)
++ [GAUSS 03901 - GAUSS 04000](/reference-guide/error-code-reference/40-GAUSS-03901-GAUSS-04000.md)
++ [GAUSS 04001 - GAUSS 04100](/reference-guide/error-code-reference/41-GAUSS-04001-GAUSS-04100.md)
++ [GAUSS 04101 - GAUSS 04200](/reference-guide/error-code-reference/42-GAUSS-04101-GAUSS-04200.md)
++ [GAUSS 04201 - GAUSS 04300](/reference-guide/error-code-reference/43-GAUSS-04201-GAUSS-04300.md)
++ [GAUSS 04301 - GAUSS 04400](/reference-guide/error-code-reference/44-GAUSS-04301-GAUSS-04400.md)
++ [GAUSS 04401 - GAUSS 04500](/reference-guide/error-code-reference/45-GAUSS-04401-GAUSS-04500.md)
++ [GAUSS 04501 - GAUSS 04600](/reference-guide/error-code-reference/46-GAUSS-04501-GAUSS-04600.md)
++ [GAUSS 04601 - GAUSS 04700](/reference-guide/error-code-reference/47-GAUSS-04601-GAUSS-04700.md)
++ [GAUSS 04701 - GAUSS 04800](/reference-guide/error-code-reference/48-GAUSS-04701-GAUSS-04800.md)
++ [GAUSS 04801 - GAUSS 04900](/reference-guide/error-code-reference/49-GAUSS-04801-GAUSS-04900.md)
++ [GAUSS 04901 - GAUSS 05000](/reference-guide/error-code-reference/50-GAUSS-04901-GAUSS-05000.md)
++ [GAUSS 05001 - GAUSS 05100](/reference-guide/error-code-reference/51-GAUSS-05001-GAUSS-05100.md)
++ [GAUSS 05101 - GAUSS 05200](/reference-guide/error-code-reference/52-GAUSS-05101-GAUSS-05200.md)
++ [GAUSS 05201 - GAUSS 05300](/reference-guide/error-code-reference/53-GAUSS-05201-GAUSS-05300.md)
++ [GAUSS 05301 - GAUSS 05400](/reference-guide/error-code-reference/54-GAUSS-05301-GAUSS-05400.md)
++ [GAUSS 05401 - GAUSS 05500](/reference-guide/error-code-reference/55-GAUSS-05401-GAUSS-05500.md)
++ [GAUSS 05501 - GAUSS 05600](/reference-guide/error-code-reference/56-GAUSS-05501-GAUSS-05600.md)
++ [GAUSS 05601 - GAUSS 05700](/reference-guide/error-code-reference/57-GAUSS-05601-GAUSS-05700.md)
++ [GAUSS 05701 - GAUSS 05800](/reference-guide/error-code-reference/58-GAUSS-05701-GAUSS-05800.md)
++ [GAUSS 05801 - GAUSS 05900](/reference-guide/error-code-reference/59-GAUSS-05801-GAUSS-05900.md)
++ [GAUSS 05901 - GAUSS 06000](/reference-guide/error-code-reference/60-GAUSS-05901-GAUSS-06000.md)
++ [GAUSS 06001 - GAUSS 06100](/reference-guide/error-code-reference/61-GAUSS-06001-GAUSS-06100.md)
++ [GAUSS 06101 - GAUSS 06200](/reference-guide/error-code-reference/62-GAUSS-06101-GAUSS-06200.md)
++ [GAUSS 06201 - GAUSS 06300](/reference-guide/error-code-reference/63-GAUSS-06201-GAUSS-06300.md)
++ [GAUSS 06301 - GAUSS 06400](/reference-guide/error-code-reference/64-GAUSS-06301-GAUSS-06400.md)
++ [GAUSS 06401 - GAUSS 06500](/reference-guide/error-code-reference/65-GAUSS-06401-GAUSS-06500.md)
++ [GAUSS 06501 - GAUSS 06600](/reference-guide/error-code-reference/66-GAUSS-06501-GAUSS-06600.md)
++ [GAUSS 06601 - GAUSS 06700](/reference-guide/error-code-reference/67-GAUSS-06601-GAUSS-06700.md)
++ [GAUSS 06701 - GAUSS 06800](/reference-guide/error-code-reference/68-GAUSS-06701-GAUSS-06800.md)
++ [GAUSS 06801 - GAUSS 06900](/reference-guide/error-code-reference/69-GAUSS-06801-GAUSS-06900.md)
++ [GAUSS 06901 - GAUSS 07000](/reference-guide/error-code-reference/70-GAUSS-06901-GAUSS-07000.md)
++ [GAUSS 07001 - GAUSS 07100](/reference-guide/error-code-reference/71-GAUSS-07001-GAUSS-07100.md)
++ [GAUSS 07101 - GAUSS 07200](/reference-guide/error-code-reference/72-GAUSS-07101-GAUSS-07200.md)
++ [GAUSS 07201 - GAUSS 07300](/reference-guide/error-code-reference/73-GAUSS-07201-GAUSS-07300.md)
++ [GAUSS 07301 - GAUSS 07400](/reference-guide/error-code-reference/74-GAUSS-07301-GAUSS-07400.md)
++ [GAUSS 07401 - GAUSS 07480](/reference-guide/error-code-reference/75-GAUSS-07401-GAUSS-07480.md)
++ [GAUSS 50000 - GAUSS 50999](/reference-guide/error-code-reference/76-GAUSS-50000-GAUSS-50999.md)
++ [GAUSS 51000 - GAUSS 51999](/reference-guide/error-code-reference/77-GAUSS-51000-GAUSS-51999.md)
++ [GAUSS 52000 - GAUSS 52999](/reference-guide/error-code-reference/78-GAUSS-52000-GAUSS-52999.md)
++ [GAUSS 53000 - GAUSS 53699](/reference-guide/error-code-reference/79-GAUSS-53000-GAUSS-53699.md)
++ 错误日志信息参考
+  + [内核错误信息](/reference-guide/error-log-reference/kernel-error-message.md)
diff --git a/product/zh/docs-mogdb/v3.0/toc_extension-referecne.md b/product/zh/docs-mogdb/v3.0/toc_extension-referecne.md
new file mode 100644
index 0000000000000000000000000000000000000000..64dcc7b54eecb4daa6a604c47fe238f0d9a9ff10
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/toc_extension-referecne.md
@@ -0,0 +1,14 @@
+<!-- markdownlint-disable MD007 -->
+<!-- markdownlint-disable MD041 -->
+
+# MogDB Documentation 3.0
+
+## 插件指南
+
++ [dblink](/reference-guide/oracle-plugins/dblink-user-guide.md)
++ [orafce](/reference-guide/oracle-plugins/orafce-user-guide.md)
++ [pg_bulkload](/reference-guide/oracle-plugins/pg_bulkload-user-guide.md)
++ [pg_prewarm](/reference-guide/oracle-plugins/pg_prewarm-user-guide.md)
++ [pg_repack](/reference-guide/oracle-plugins/pg_repack-user-guide.md)
++ [pg_trgm](/reference-guide/oracle-plugins/pg_trgm-user-guide.md)
++ [wal2json](/reference-guide/oracle-plugins/wal2json-user-guide.md)
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/toc_faqs.md b/product/zh/docs-mogdb/v3.0/toc_faqs.md
new file mode 100644
index 0000000000000000000000000000000000000000..f109dfd16640eebf4bc3cfb64c94881e0cf37818
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/toc_faqs.md
@@ -0,0 +1,12 @@
+<!-- markdownlint-disable MD007 -->
+<!-- markdownlint-disable MD041 -->
+# MogDB Documentation 3.0
+
+## 常见问题解答 (FAQs)
+
++ [产品FAQs](/faqs/product-faqs.md)
++ [应用开发FAQs](/faqs/application-development-faqs.md)
++ [部署运维FAQs](/faqs/deployment-and-maintenance-faqs.md)
++ [升级FAQs](/faqs/upgrade-faqs.md)
++ [高可用FAQs](/faqs/high-availability-faqs.md)
++ [迁移FAQs](/faqs/migration-faqs.md)
diff --git a/product/zh/docs-mogdb/v3.0/toc_glossary.md b/product/zh/docs-mogdb/v3.0/toc_glossary.md
new file mode 100644
index 0000000000000000000000000000000000000000..ae6eb83fecfd7b40635f17f2c4e85aff837a9b0b
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/toc_glossary.md
@@ -0,0 +1,5 @@
+# MogDB Documentation 3.0
+
+## 术语表
+
++ [术语表](./glossary.md)
diff --git a/product/zh/docs-mogdb/v3.0/toc_install.md b/product/zh/docs-mogdb/v3.0/toc_install.md
new file mode 100644
index 0000000000000000000000000000000000000000..8eb130483f9b24a8daada7ad3f83dfe336666ef9
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/toc_install.md
@@ -0,0 +1,21 @@
+<!-- markdownlint-disable MD007 -->
+<!-- markdownlint-disable MD041 -->
+# MogDB Documentation 3.0
+
+## 安装指南
+
++ [容器化安装](/installation-guide/docker-installation/docker-installation.md)
++ 极简安装
+  + [安装准备](/installation-guide/simplified-installation-process/1-installation-preparation.md)
+  + [单节点安装](/installation-guide/simplified-installation-process/2-installation-on-a-single-node.md)
+  + [一主一备节点安装](/installation-guide/simplified-installation-process/3-installation-on-primary-standby-nodes.md)
++ 标准安装
+  + [安装概述](/installation-guide/standard-installation/1-installation-overview.md)
+  + 安装准备
+    + [环境要求](/installation-guide/standard-installation/2-environment-requirement.md)
+    + [修改操作系统配置](/installation-guide/standard-installation/3-modifying-os-configuration.md)
+  + [安装MogDB](/installation-guide/standard-installation/4-installing-mogdb.md)
+  + [安装验证](/installation-guide/standard-installation/5-verifying-installation.md)
+  + [推荐参数设置及新建测试库](/installation-guide/standard-installation/7-recommended-parameter-settings.md)
+  + [卸载MogDB](/installation-guide/standard-installation/6-uninstallation.md)
++ [手动安装](/installation-guide/manual-installation.md)
diff --git a/product/zh/docs-mogdb/v3.0/toc_manage.md b/product/zh/docs-mogdb/v3.0/toc_manage.md
new file mode 100644
index 0000000000000000000000000000000000000000..ce58952195db73e7d2f3da2080d676632da72a5d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/toc_manage.md
@@ -0,0 +1,73 @@
+<!-- markdownlint-disable MD007 -->
+<!-- markdownlint-disable MD041 -->
+# MogDB Documentation 3.0
+
+## 管理指南
+
++ 日常运维
+  + [启停MogDB](/administrator-guide/routine-maintenance/0-starting-and-stopping-mogdb.md)
+  + [gsql客户端连接](./administrator-guide/routine-maintenance/using-the-gsql-client-for-connection.md)
+  + [日维护检查项](/administrator-guide/routine-maintenance/1-routine-maintenance-check-items.md)
+  + [检查操作系统参数](/administrator-guide/routine-maintenance/2-checking-os-parameters.md)
+  + [检查MogDB健康状态](/administrator-guide/routine-maintenance/3-checking-mogdb-health-status.md)
+  + [检查数据库性能](/administrator-guide/routine-maintenance/4-checking-database-performance.md)
+  + [检查和清理日志](/administrator-guide/routine-maintenance/5-checking-and-deleting-logs.md)
+  + [检查时间一致性](/administrator-guide/routine-maintenance/6-checking-time-consistency.md)
+  + [检查应用连接数](/administrator-guide/routine-maintenance/7-checking-the-number-of-application-connections.md)
+  + [例行维护表](/administrator-guide/routine-maintenance/8-routinely-maintaining-tables.md)
+  + [例行重建索引](/administrator-guide/routine-maintenance/9-routinely-recreating-an-index.md)
+  + [数据安全维护建议](/administrator-guide/routine-maintenance/10-data-security-maintenance-suggestions.md)
+  + [慢SQL诊断](/administrator-guide/routine-maintenance/slow-sql-diagnosis.md)
+  + [日志参考](/administrator-guide/routine-maintenance/11-log-reference.md)
++ [主备管理](/administrator-guide/primary-and-standby-management.md)
++ MOT内存表管理
+  + MOT介绍
+    + [MOT简介](/administrator-guide/mot-engine/1-introducing-mot/1-mot-introduction.md)
+    + [MOT特性及价值](/administrator-guide/mot-engine/1-introducing-mot/2-mot-features-and-benefits.md)
+    + [MOT关键技术](/administrator-guide/mot-engine/1-introducing-mot/3-mot-key-technologies.md)
+    + [MOT应用场景](/administrator-guide/mot-engine/1-introducing-mot/4-mot-usage-scenarios.md)
+    + [MOT性能基准](/administrator-guide/mot-engine/1-introducing-mot/5-mot-performance-benchmarks.md)
+  + 使用MOT
+    + [MOT使用概述](/administrator-guide/mot-engine/2-using-mot/1-using-mot-overview.md)
+    + [MOT准备](/administrator-guide/mot-engine/2-using-mot/2-mot-preparation.md)
+    + [MOT部署](/administrator-guide/mot-engine/2-using-mot/3-mot-deployment.md)
+    + [MOT使用](/administrator-guide/mot-engine/2-using-mot/4-mot-usage.md)
+    + [MOT管理](/administrator-guide/mot-engine/2-using-mot/5-mot-administration.md)
+    + [MOT样例TPC-C基准](/administrator-guide/mot-engine/2-using-mot/6-mot-sample-tpcc-benchmark.md)
+  + MOT的概念
+    + [MOT纵向扩容架构](/administrator-guide/mot-engine/3-concepts-of-mot/3-1.md)
+    + [MOT并发控制机制](/administrator-guide/mot-engine/3-concepts-of-mot/3-2.md)
+    + [扩展FDW与其他MogDB特性](/administrator-guide/mot-engine/3-concepts-of-mot/3-3.md)
+    + [NUMA-aware分配和亲和性](/administrator-guide/mot-engine/3-concepts-of-mot/3-4.md)
+    + [MOT索引](/administrator-guide/mot-engine/3-concepts-of-mot/3-5.md)
+    + [MOT持久性概念](/administrator-guide/mot-engine/3-concepts-of-mot/3-6.md)
+    + [MOT恢复概念](/administrator-guide/mot-engine/3-concepts-of-mot/3-7.md)
+    + [MOT查询原生编译（JIT）](/administrator-guide/mot-engine/3-concepts-of-mot/3-8.md)
+    + [对比：磁盘与MOT](/administrator-guide/mot-engine/3-concepts-of-mot/3-9.md)
+  + 附录
+    + [参考文献](/administrator-guide/mot-engine/4-appendix/1-references.md)
+    + [术语表](/administrator-guide/mot-engine/4-appendix/2-glossary.md)
++ [列存表管理](/administrator-guide/column-store-tables-management.md)
++ 备份与恢复
+  + [概述](/administrator-guide/br/1-1-br.md)
+  + [物理备份恢复](/administrator-guide/br/1-2-br.md)
+  + [逻辑备份恢复](/administrator-guide/br/1-3-br.md)
+  + [闪回恢复](/administrator-guide/br/1-4-br.md)
++ 数据导出导入
+  + 导入数据
+    + [导入方式](/administrator-guide/importing-and-exporting-data/importing-data/1-import-modes.md)
+    + [通过INSERT语句直接写入数据](/administrator-guide/importing-and-exporting-data/importing-data/2-running-the-INSERT-statement-to-insert-data.md)
+    + [使用COPY FROM STDIN导入数据](/administrator-guide/importing-and-exporting-data/importing-data/3-running-the-COPY-FROM-STDIN-statement-to-import-data.md)
+    + [使用gsql元命令导入数据](/administrator-guide/importing-and-exporting-data/importing-data/4-using-a-gsql-meta-command-to-import-data.md)
+    + [使用gs_restore命令导入数据](/administrator-guide/importing-and-exporting-data/importing-data/5-using-gs_restore-to-import-data.md)
+    + [更新表中数据](/administrator-guide/importing-and-exporting-data/importing-data/6-updating-data-in-a-table.md)
+    + [深层复制](/administrator-guide/importing-and-exporting-data/importing-data/7-deep-copy.md)
+    + [分析表](/administrator-guide/importing-and-exporting-data/importing-data/8-ANALYZE-table.md)
+    + [对表执行VACUUM](/administrator-guide/importing-and-exporting-data/importing-data/9-doing-VACUUM-to-a-table.md)
+    + [管理并发写入操作](/administrator-guide/importing-and-exporting-data/importing-data/10-managing-concurrent-write-operations.md)
+  + 导出数据
+    + [使用gs_dump和gs_dumpall命令导出数据概述](/administrator-guide/importing-and-exporting-data/exporting-data/1-using-gs_dump-and-gs_dumpall-to-export-data-overview.md)
+    + [导出单个数据库](/administrator-guide/importing-and-exporting-data/exporting-data/2-exporting-a-single-database.md)
+    + [导出所有数据库](/administrator-guide/importing-and-exporting-data/exporting-data/3-exporting-all-databases.md)
+    + [无权限角色导出数据](/administrator-guide/importing-and-exporting-data/exporting-data/4-data-export-by-a-user-without-required-permissions.md)
++ [升级指南](/administrator-guide/upgrade-guide.md)
diff --git a/product/zh/docs-mogdb/v3.0/toc_parameters-and-tools.md b/product/zh/docs-mogdb/v3.0/toc_parameters-and-tools.md
new file mode 100644
index 0000000000000000000000000000000000000000..69ea5e71611c296dc95c54c1562e10ff638efbfa
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/toc_parameters-and-tools.md
@@ -0,0 +1,377 @@
+<!-- markdownlint-disable MD007 -->
+<!-- markdownlint-disable MD041 -->
+
+# MogDB Documentation 3.0
+
+## 参数及工具
+
++ GUC参数说明
+  + [GUC使用说明](./reference-guide/guc-parameters/1-guc-parameter-usage.md)
+  + [文件位置](./reference-guide/guc-parameters/2-file-location.md)
+  + 连接和认证
+    + [连接设置](./reference-guide/guc-parameters/3-connection-and-authentication/1-connection-settings.md)
+    + [安全和认证](./reference-guide/guc-parameters/3-connection-and-authentication/2-security-and-authentication.md)
+    + [通信库参数](./reference-guide/guc-parameters/3-connection-and-authentication/3-communication-library-parameters.md)
+  + 资源消耗
+    + [内存](./reference-guide/guc-parameters/4-resource-consumption/1-memory.md)
+    + [磁盘空间](./reference-guide/guc-parameters/4-resource-consumption/2-disk-space.md)
+    + [内核资源使用](./reference-guide/guc-parameters/4-resource-consumption/3-kernel-resource-usage.md)
+    + [基于开销的清理延迟](./reference-guide/guc-parameters/4-resource-consumption/4-cost-based-vacuum-delay.md)
+    + [后端写进程](./reference-guide/guc-parameters/4-resource-consumption/5-background-writer.md)
+    + [异步IO](./reference-guide/guc-parameters/4-resource-consumption/6-asynchronous-io-operations.md)
+  + [并行导入](./reference-guide/guc-parameters/5-parallel-import.md)
+  + 预写式日志
+    + [设置](./reference-guide/guc-parameters/6-write-ahead-log/1-settings.md)
+    + [检查点](./reference-guide/guc-parameters/6-write-ahead-log/2-checkpoints.md)
+    + [日志回放](./reference-guide/guc-parameters/6-write-ahead-log/3-log-replay.md)
+    + [归档](./reference-guide/guc-parameters/6-write-ahead-log/4-archiving.md)
+  + 双机复制
+    + [发送端服务器](./reference-guide/guc-parameters/7-ha-replication/1-sending-server.md)
+    + [主服务器](./reference-guide/guc-parameters/7-ha-replication/2-primary-server.md)
+    + [备服务器](./reference-guide/guc-parameters/7-ha-replication/3-standby-server.md)
+  + [内存表](./reference-guide/guc-parameters/8-mot.md)
+  + 查询规划
+    + [介绍](./reference-guide/guc-parameters/9-query-planning/introduction-to-query-planning.md)
+    + [优化器方法配置](./reference-guide/guc-parameters/9-query-planning/1-optimizer-method-configuration.md)
+    + [优化器开销常量](./reference-guide/guc-parameters/9-query-planning/2-optimizer-cost-constants.md)
+    + [基因查询优化器](./reference-guide/guc-parameters/9-query-planning/3-genetic-query-optimizer.md)
+    + [其他优化器选项](./reference-guide/guc-parameters/9-query-planning/4-other-optimizer-options.md)
+  + 错误报告和日志
+    + [记录日志的位置](./reference-guide/guc-parameters/10-error-reporting-and-logging/1-logging-destination.md)
+    + [记录日志的时间](./reference-guide/guc-parameters/10-error-reporting-and-logging/2-logging-time.md)
+    + [记录日志的内容](./reference-guide/guc-parameters/10-error-reporting-and-logging/3-logging-content.md)
+    + [使用CSV格式写日志](./reference-guide/guc-parameters/10-error-reporting-and-logging/4-using-csv-log-output.md)
+  + [告警检测](./reference-guide/guc-parameters/11-alarm-detection.md)
+  + 运行时统计
+    + [查询和索引统计收集器](./reference-guide/guc-parameters/12-statistics-during-the-database-running/1-query-and-index-statistics-collector.md)
+    + [性能统计](./reference-guide/guc-parameters/12-statistics-during-the-database-running/2-performance-statistics.md)
+  + [负载管理](./reference-guide/guc-parameters/13-load-management.md)
+  + [自动清理](./reference-guide/guc-parameters/14-automatic-vacuuming.md)
+  + 客户端连接缺省设置
+    + [语句行为](./reference-guide/guc-parameters/15-default-settings-of-client-connection/1-statement-behavior.md)
+    + [区域和格式化](./reference-guide/guc-parameters/15-default-settings-of-client-connection/2-zone-and-formatting.md)
+    + [其他缺省](./reference-guide/guc-parameters/15-default-settings-of-client-connection/3-other-default-parameters.md)
+  + [锁管理](./reference-guide/guc-parameters/16-lock-management.md)
+  + 版本和平台兼容性
+    + [历史版本兼容性](./reference-guide/guc-parameters/17-version-and-platform-compatibility/1-compatibility-with-earlier-versions.md)
+    + [平台和客户端兼容性](./reference-guide/guc-parameters/17-version-and-platform-compatibility/2-platform-and-client-compatibility.md)
+  + [容错性](./reference-guide/guc-parameters/18-fault-tolerance.md)
+  + [连接池参数](./reference-guide/guc-parameters/19-connection-pool-parameters.md)
+  + [MogDB事务](./reference-guide/guc-parameters/20-MogDB-transaction.md)
+  + [开发人员选项](./reference-guide/guc-parameters/21-developer-options.md)
+  + 审计
+    + [审计开关](./reference-guide/guc-parameters/22-auditing/1-audit-switch.md)
+    + [用户和权限审计](./reference-guide/guc-parameters/22-auditing/2-user-and-permission-audit.md)
+    + [操作审计](./reference-guide/guc-parameters/22-auditing/3-operation-audit.md)
+  + [升级参数](./reference-guide/guc-parameters/23-upgrade-parameters.md)
+  + [其他选项](./reference-guide/guc-parameters/24-miscellaneous-parameters.md)
+  + [等待事件](./reference-guide/guc-parameters/25-wait-events.md)
+  + [Query](./reference-guide/guc-parameters/26-query.md)
+  + [系统性能快照](./reference-guide/guc-parameters/27-system-performance-snapshot.md)
+  + [安全配置](./reference-guide/guc-parameters/27.1-security-configuration.md)
+  + [全局临时表](./reference-guide/guc-parameters/29-global-temporary-table.md)
+  + [HyperLogLog](./reference-guide/guc-parameters/29.1-HyperLogLog.md)
+  + [定时任务](./reference-guide/guc-parameters/31-scheduled-task.md)
+  + [线程池](./reference-guide/guc-parameters/32-thread-pool.md)
+  + [用户自定义函数](./reference-guide/guc-parameters/33-user-defined-functions.md)
+  + [备份恢复](./reference-guide/guc-parameters/34-backup-and-restoration.md)
+  + [Undo](./reference-guide/guc-parameters/35-undo.md)
+  + [DCF参数设置](./reference-guide/guc-parameters/36-DCF-parameters-settings.md)
+  + [闪回相关参数](./reference-guide/guc-parameters/37-flashback.md)
+  + [回滚相关参数](./reference-guide/guc-parameters/38-rollback-parameters.md)
+  + [预留参数](./reference-guide/guc-parameters/39-reserved-parameters.md)
+  + [AI特性](./reference-guide/guc-parameters/40-AI-features.md)
+  + [附录](./reference-guide/guc-parameters/30-appendix.md)
++ Schema
+  + Information Schema
+    + [概述](./reference-guide/schema/information-schema/1-information-schema-overview.md)
+    + [_PG_FOREIGN_DATA_WRAPPERS](./reference-guide/schema/information-schema/2-_PG_FOREIGN_DATA_WRAPPERS.md)
+    + [_PG_FOREIGN_SERVERS](./reference-guide/schema/information-schema/3-_PG_FOREIGN_SERVERS.md)
+    + [_PG_FOREIGN_TABLE_COLUMNS](./reference-guide/schema/information-schema/4-_PG_FOREIGN_TABLE_COLUMNS.md)
+    + [_PG_FOREIGN_TABLES](./reference-guide/schema/information-schema/5-_PG_FOREIGN_TABLES.md)
+    + [_PG_USER_MAPPINGS](./reference-guide/schema/information-schema/6-_PG_USER_MAPPINGS.md)
+    + [INFORMATION_SCHEMA_CATALOG_NAME](./reference-guide/schema/information-schema/7-INFORMATION_SCHEMA_CATALOG_NAME.md)
+  + DBE_PERF
+    + [概述](./reference-guide/schema/DBE_PERF/DBE_PERF_overview.md)
+    + OS
+      + [OS_RUNTIME](./reference-guide/schema/DBE_PERF/os/OS_RUNTIME.md)
+      + [GLOBAL_OS_RUNTIME](./reference-guide/schema/DBE_PERF/os/GLOBAL_OS_RUNTIME.md)
+      + [OS_THREADS](./reference-guide/schema/DBE_PERF/os/OS_THREADS.md)
+      + [GLOBAL_OS_THREADS](./reference-guide/schema/DBE_PERF/os/GLOBAL_OS_THREADS.md)
+    + Instance
+      + [INSTANCE_TIME](./reference-guide/schema/DBE_PERF/instance/INSTANCE_TIME.md)
+      + [GLOBAL_INSTANCE_TIME](./reference-guide/schema/DBE_PERF/instance/GLOBAL_INSTANCE_TIME.md)
+    + Memory
+      + [MEMORY_NODE_DETAIL](./reference-guide/schema/DBE_PERF/memory/MEMORY_NODE_DETAIL.md)
+      + [GLOBAL_MEMORY_NODE_DETAIL](./reference-guide/schema/DBE_PERF/memory/GLOBAL_MEMORY_NODE_DETAIL.md)
+      + [GS_SHARED_MEMORY_DETAIL](./reference-guide/schema/DBE_PERF/memory/GS_SHARED_MEMORY_DETAIL.md)
+      + [GLOBAL_SHARED_MEMORY_DETAIL](./reference-guide/schema/DBE_PERF/memory/GLOBAL_SHARED_MEMORY_DETAIL.md)
+    + File
+      + [FILE_IOSTAT](./reference-guide/schema/DBE_PERF/file/FILE_IOSTAT.md)
+      + [SUMMARY_FILE_IOSTAT](./reference-guide/schema/DBE_PERF/file/SUMMARY_FILE_IOSTAT.md)
+      + [GLOBAL_FILE_IOSTAT](./reference-guide/schema/DBE_PERF/file/GLOBAL_FILE_IOSTAT.md)
+      + [FILE_REDO_IOSTAT](./reference-guide/schema/DBE_PERF/file/FILE_REDO_IOSTAT.md)
+      + [SUMMARY_FILE_REDO_IOSTAT](./reference-guide/schema/DBE_PERF/file/SUMMARY_FILE_REDO_IOSTAT.md)
+      + [GLOBAL_FILE_REDO_IOSTAT](./reference-guide/schema/DBE_PERF/file/GLOBAL_FILE_REDO_IOSTAT.md)
+      + [LOCAL_REL_IOSTAT](./reference-guide/schema/DBE_PERF/file/LOCAL_REL_IOSTAT.md)
+      + [GLOBAL_REL_IOSTAT](./reference-guide/schema/DBE_PERF/file/GLOBAL_REL_IOSTAT.md)
+      + [SUMMARY_REL_IOSTAT](./reference-guide/schema/DBE_PERF/file/SUMMARY_REL_IOSTAT.md)
+    + Object
+      + [STAT_USER_TABLES](./reference-guide/schema/DBE_PERF/object/STAT_USER_TABLES.md)
+      + [SUMMARY_STAT_USER_TABLES](./reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_USER_TABLES.md)
+      + [GLOBAL_STAT_USER_TABLES](./reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_USER_TABLES.md)
+      + [STAT_USER_INDEXES](./reference-guide/schema/DBE_PERF/object/STAT_USER_INDEXES.md)
+      + [SUMMARY_STAT_USER_INDEXES](./reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_USER_INDEXES.md)
+      + [GLOBAL_STAT_USER_INDEXES](./reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_USER_INDEXES.md)
+      + [STAT_SYS_TABLES](./reference-guide/schema/DBE_PERF/object/STAT_SYS_TABLES.md)
+      + [SUMMARY_STAT_SYS_TABLES](./reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_SYS_TABLES.md)
+      + [GLOBAL_STAT_SYS_TABLES](./reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_SYS_TABLES.md)
+      + [STAT_SYS_INDEXES](./reference-guide/schema/DBE_PERF/object/STAT_SYS_INDEXES.md)
+      + [SUMMARY_STAT_SYS_INDEXES](./reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_SYS_INDEXES.md)
+      + [GLOBAL_STAT_SYS_INDEXES](./reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_SYS_INDEXES.md)
+      + [STAT_ALL_TABLES](./reference-guide/schema/DBE_PERF/object/STAT_ALL_TABLES.md)
+      + [SUMMARY_STAT_ALL_TABLES](./reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_ALL_TABLES.md)
+      + [GLOBAL_STAT_ALL_TABLES](./reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_ALL_TABLES.md)
+      + [STAT_ALL_INDEXES](./reference-guide/schema/DBE_PERF/object/STAT_ALL_INDEXES.md)
+      + [SUMMARY_STAT_ALL_INDEXES](./reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_ALL_INDEXES.md)
+      + [GLOBAL_STAT_ALL_INDEXES](./reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_ALL_INDEXES.md)
+      + [STAT_DATABASE](./reference-guide/schema/DBE_PERF/object/STAT_DATABASE.md)
+      + [SUMMARY_STAT_DATABASE](./reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_DATABASE.md)
+      + [GLOBAL_STAT_DATABASE](./reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_DATABASE.md)
+      + [STAT_DATABASE_CONFLICTS](./reference-guide/schema/DBE_PERF/object/STAT_DATABASE_CONFLICTS.md)
+      + [SUMMARY_STAT_DATABASE_CONFLICTS](./reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_DATABASE_CONFLICTS.md)
+      + [GLOBAL_STAT_DATABASE_CONFLICTS](./reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_DATABASE_CONFLICTS.md)
+      + [STAT_XACT_ALL_TABLES](./reference-guide/schema/DBE_PERF/object/STAT_XACT_ALL_TABLES.md)
+      + [SUMMARY_STAT_XACT_ALL_TABLES](./reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_ALL_TABLES.md)
+      + [GLOBAL_STAT_XACT_ALL_TABLES](./reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_ALL_TABLES.md)
+      + [STAT_XACT_SYS_TABLES](./reference-guide/schema/DBE_PERF/object/STAT_XACT_SYS_TABLES.md)
+      + [SUMMARY_STAT_XACT_SYS_TABLES](./reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_SYS_TABLES.md)
+      + [GLOBAL_STAT_XACT_SYS_TABLES](./reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_SYS_TABLES.md)
+      + [STAT_XACT_USER_TABLES](./reference-guide/schema/DBE_PERF/object/STAT_XACT_USER_TABLES.md)
+      + [SUMMARY_STAT_XACT_USER_TABLES](./reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_USER_TABLES.md)
+      + [GLOBAL_STAT_XACT_USER_TABLES](./reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_USER_TABLES.md)
+      + [STAT_XACT_USER_FUNCTIONS](./reference-guide/schema/DBE_PERF/object/STAT_XACT_USER_FUNCTIONS.md)
+      + [SUMMARY_STAT_XACT_USER_FUNCTIONS](./reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_XACT_USER_FUNCTIONS.md)
+      + [GLOBAL_STAT_XACT_USER_FUNCTIONS](./reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_XACT_USER_FUNCTIONS.md)
+      + [STAT_BAD_BLOCK](./reference-guide/schema/DBE_PERF/object/STAT_BAD_BLOCK.md)
+      + [SUMMARY_STAT_BAD_BLOCK](./reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_BAD_BLOCK.md)
+      + [GLOBAL_STAT_BAD_BLOCK](./reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_BAD_BLOCK.md)
+      + [STAT_USER_FUNCTIONS](./reference-guide/schema/DBE_PERF/object/STAT_USER_FUNCTIONS.md)
+      + [SUMMARY_STAT_USER_FUNCTIONS](./reference-guide/schema/DBE_PERF/object/SUMMARY_STAT_USER_FUNCTIONS.md)
+      + [GLOBAL_STAT_USER_FUNCTIONS](./reference-guide/schema/DBE_PERF/object/GLOBAL_STAT_USER_FUNCTIONS.md)
+    + Workload
+      + [WORKLOAD_SQL_COUNT](./reference-guide/schema/DBE_PERF/workload/WORKLOAD_SQL_COUNT.md)
+      + [SUMMARY_WORKLOAD_SQL_COUNT](./reference-guide/schema/DBE_PERF/workload/SUMMARY_WORKLOAD_SQL_COUNT.md)
+      + [WORKLOAD_TRANSACTION](./reference-guide/schema/DBE_PERF/workload/WORKLOAD_TRANSACTION.md)
+      + [SUMMARY_WORKLOAD_TRANSACTION](./reference-guide/schema/DBE_PERF/workload/SUMMARY_WORKLOAD_TRANSACTION.md)
+      + [GLOBAL_WORKLOAD_TRANSACTION](./reference-guide/schema/DBE_PERF/workload/GLOBAL_WORKLOAD_TRANSACTION.md)
+      + [WORKLOAD_SQL_ELAPSE_TIME](./reference-guide/schema/DBE_PERF/workload/WORKLOAD_SQL_ELAPSE_TIME.md)
+      + [SUMMARY_WORKLOAD_SQL_ELAPSE_TIME](./reference-guide/schema/DBE_PERF/workload/SUMMARY_WORKLOAD_SQL_ELAPSE_TIME.md)
+      + [USER_TRANSACTION](./reference-guide/schema/DBE_PERF/workload/USER_TRANSACTION.md)
+      + [GLOBAL_USER_TRANSACTION](./reference-guide/schema/DBE_PERF/workload/GLOBAL_USER_TRANSACTION.md)
+    + Session/Thread
+      + [SESSION_STAT](./reference-guide/schema/DBE_PERF/session-thread/SESSION_STAT.md)
+      + [GLOBAL_SESSION_STAT](./reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_STAT.md)
+      + [SESSION_TIME](./reference-guide/schema/DBE_PERF/session-thread/SESSION_TIME.md)
+      + [GLOBAL_SESSION_TIME](./reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_TIME.md)
+      + [SESSION_MEMORY](./reference-guide/schema/DBE_PERF/session-thread/SESSION_MEMORY.md)
+      + [GLOBAL_SESSION_MEMORY](./reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_MEMORY.md)
+      + [SESSION_MEMORY_DETAIL](./reference-guide/schema/DBE_PERF/session-thread/SESSION_MEMORY_DETAIL.md)
+      + [GLOBAL_SESSION_MEMORY_DETAIL](./reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_MEMORY_DETAIL.md)
+      + [SESSION_STAT_ACTIVITY](./reference-guide/schema/DBE_PERF/session-thread/SESSION_STAT_ACTIVITY.md)
+      + [GLOBAL_SESSION_STAT_ACTIVITY](./reference-guide/schema/DBE_PERF/session-thread/GLOBAL_SESSION_STAT_ACTIVITY.md)
+      + [THREAD_WAIT_STATUS](./reference-guide/schema/DBE_PERF/session-thread/THREAD_WAIT_STATUS.md)
+      + [GLOBAL_THREAD_WAIT_STATUS](./reference-guide/schema/DBE_PERF/session-thread/GLOBAL_THREAD_WAIT_STATUS.md)
+      + [LOCAL_THREADPOOL_STATUS](./reference-guide/schema/DBE_PERF/session-thread/LOCAL_THREADPOOL_STATUS.md)
+      + [GLOBAL_THREADPOOL_STATUS](./reference-guide/schema/DBE_PERF/session-thread/GLOBAL_THREADPOOL_STATUS.md)
+      + [SESSION_CPU_RUNTIME](./reference-guide/schema/DBE_PERF/session-thread/SESSION_CPU_RUNTIME.md)
+      + [SESSION_MEMORY_RUNTIME](./reference-guide/schema/DBE_PERF/session-thread/SESSION_MEMORY_RUNTIME.md)
+      + [STATEMENT_IOSTAT_COMPLEX_RUNTIME](./reference-guide/schema/DBE_PERF/session-thread/STATEMENT_IOSTAT_COMPLEX_RUNTIME.md)
+      + [LOCAL_ACTIVE_SESSION](./reference-guide/schema/DBE_PERF/session-thread/LOCAL_ACTIVE_SESSION.md)
+    + Transaction
+      + [TRANSACTIONS_PREPARED_XACTS](./reference-guide/schema/DBE_PERF/transaction/TRANSACTIONS_PREPARED_XACTS.md)
+      + [SUMMARY_TRANSACTIONS_PREPARED_XACTS](./reference-guide/schema/DBE_PERF/transaction/SUMMARY_TRANSACTIONS_PREPARED_XACTS.md)
+      + [GLOBAL_TRANSACTIONS_PREPARED_XACTS](./reference-guide/schema/DBE_PERF/transaction/GLOBAL_TRANSACTIONS_PREPARED_XACTS.md)
+      + [TRANSACTIONS_RUNNING_XACTS](./reference-guide/schema/DBE_PERF/transaction/TRANSACTIONS_RUNNING_XACTS.md)
+      + [SUMMARY_TRANSACTIONS_RUNNING_XACTS](./reference-guide/schema/DBE_PERF/transaction/SUMMARY_TRANSACTIONS_RUNNING_XACTS.md)
+      + [GLOBAL_TRANSACTIONS_RUNNING_XACTS](./reference-guide/schema/DBE_PERF/transaction/GLOBAL_TRANSACTIONS_RUNNING_XACTS.md)
+    + Query
+      + [STATEMENT](./reference-guide/schema/DBE_PERF/query/STATEMENT.md)
+      + [SUMMARY_STATEMENT](./reference-guide/schema/DBE_PERF/query/SUMMARY_STATEMENT.md)
+      + [STATEMENT_COUNT](./reference-guide/schema/DBE_PERF/query/STATEMENT_COUNT.md)
+      + [GLOBAL_STATEMENT_COUNT](./reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COUNT.md)
+      + [SUMMARY_STATEMENT_COUNT](./reference-guide/schema/DBE_PERF/query/SUMMARY_STATEMENT_COUNT.md)
+      + [GLOBAL_STATEMENT_COMPLEX_HISTORY](./reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COMPLEX_HISTORY.md)
+      + [GLOBAL_STATEMENT_COMPLEX_HISTORY_TABLE](./reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COMPLEX_HISTORY_TABLE.md)
+      + [GLOBAL_STATEMENT_COMPLEX_RUNTIME](./reference-guide/schema/DBE_PERF/query/GLOBAL_STATEMENT_COMPLEX_RUNTIME.md)
+      + [STATEMENT_RESPONSETIME_PERCENTILE](./reference-guide/schema/DBE_PERF/query/STATEMENT_RESPONSETIME_PERCENTILE.md)
+      + [STATEMENT_USER_COMPLEX_HISTORY](./reference-guide/schema/DBE_PERF/query/STATEMENT_USER_COMPLEX_HISTORY.md)
+      + [STATEMENT_COMPLEX_RUNTIME](./reference-guide/schema/DBE_PERF/query/STATEMENT_COMPLEX_RUNTIME.md)
+      + [STATEMENT_COMPLEX_HISTORY_TABLE](./reference-guide/schema/DBE_PERF/query/STATEMENT_COMPLEX_HISTORY_TABLE.md)
+      + [STATEMENT_COMPLEX_HISTORY](./reference-guide/schema/DBE_PERF/query/STATEMENT_COMPLEX_HISTORY.md)
+      + [STATEMENT_WLMSTAT_COMPLEX_RUNTIME](./reference-guide/schema/DBE_PERF/query/STATEMENT_WLMSTAT_COMPLEX_RUNTIME.md)
+      + [STATEMENT_HISTORY](./reference-guide/schema/DBE_PERF/query/STATEMENT_HISTORY.md)
+    + Cache/IO
+      + [STATIO_USER_TABLES](./reference-guide/schema/DBE_PERF/cache-io/STATIO_USER_TABLES.md)
+      + [SUMMARY_STATIO_USER_TABLES](./reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_USER_TABLES.md)
+      + [GLOBAL_STATIO_USER_TABLES](./reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_USER_TABLES.md)
+      + [STATIO_USER_INDEXES](./reference-guide/schema/DBE_PERF/cache-io/STATIO_USER_INDEXES.md)
+      + [SUMMARY_STATIO_USER_INDEXES](./reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_USER_INDEXES.md)
+      + [GLOBAL_STATIO_USER_INDEXES](./reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_USER_INDEXES.md)
+      + [STATIO_USER_SEQUENCES](./reference-guide/schema/DBE_PERF/cache-io/STATIO_USER_SEQUENCES.md)
+      + [SUMMARY_STATIO_USER_SEQUENCES](./reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_USER_SEQUENCES.md)
+      + [GLOBAL_STATIO_USER_SEQUENCES](./reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_USER_SEQUENCES.md)
+      + [STATIO_SYS_TABLES](./reference-guide/schema/DBE_PERF/cache-io/STATIO_SYS_TABLES.md)
+      + [SUMMARY_STATIO_SYS_TABLES](./reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_SYS_TABLES.md)
+      + [GLOBAL_STATIO_SYS_TABLES](./reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_SYS_TABLES.md)
+      + [STATIO_SYS_INDEXES](./reference-guide/schema/DBE_PERF/cache-io/STATIO_SYS_INDEXES.md)
+      + [SUMMARY_STATIO_SYS_INDEXES](./reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_SYS_INDEXES.md)
+      + [GLOBAL_STATIO_SYS_INDEXES](./reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_SYS_INDEXES.md)
+      + [STATIO_SYS_SEQUENCES](./reference-guide/schema/DBE_PERF/cache-io/STATIO_SYS_SEQUENCES.md)
+      + [SUMMARY_STATIO_SYS_SEQUENCES](./reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_SYS_SEQUENCES.md)
+      + [GLOBAL_STATIO_SYS_SEQUENCES](./reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_SYS_SEQUENCES.md)
+      + [STATIO_ALL_TABLES](./reference-guide/schema/DBE_PERF/cache-io/STATIO_ALL_TABLES.md)
+      + [SUMMARY_STATIO_ALL_TABLES](./reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_ALL_TABLES.md)
+      + [GLOBAL_STATIO_ALL_TABLES](./reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_ALL_TABLES.md)
+      + [STATIO_ALL_INDEXES](./reference-guide/schema/DBE_PERF/cache-io/STATIO_ALL_INDEXES.md)
+      + [SUMMARY_STATIO_ALL_INDEXES](./reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_ALL_INDEXES.md)
+      + [GLOBAL_STATIO_ALL_INDEXES](./reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_ALL_INDEXES.md)
+      + [STATIO_ALL_SEQUENCES](./reference-guide/schema/DBE_PERF/cache-io/STATIO_ALL_SEQUENCES.md)
+      + [SUMMARY_STATIO_ALL_SEQUENCES](./reference-guide/schema/DBE_PERF/cache-io/SUMMARY_STATIO_ALL_SEQUENCES.md)
+      + [GLOBAL_STATIO_ALL_SEQUENCES](./reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STATIO_ALL_SEQUENCES.md)
+      + [GLOBAL_STAT_DB_CU](./reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STAT_DB_CU.md)
+      + [GLOBAL_STAT_SESSION_CU](./reference-guide/schema/DBE_PERF/cache-io/GLOBAL_STAT_SESSION_CU.md)
+    + Utility
+      + [REPLICATION_STAT](./reference-guide/schema/DBE_PERF/utility/REPLICATION_STAT.md)
+      + [GLOBAL_REPLICATION_STAT](./reference-guide/schema/DBE_PERF/utility/GLOBAL_REPLICATION_STAT.md)
+      + [REPLICATION_SLOTS](./reference-guide/schema/DBE_PERF/utility/REPLICATION_SLOTS.md)
+      + [GLOBAL_REPLICATION_SLOTS](./reference-guide/schema/DBE_PERF/utility/GLOBAL_REPLICATION_SLOTS.md)
+      + [BGWRITER_STAT](./reference-guide/schema/DBE_PERF/utility/BGWRITER_STAT.md)
+      + [GLOBAL_BGWRITER_STAT](./reference-guide/schema/DBE_PERF/utility/GLOBAL_BGWRITER_STAT.md)
+      + [GLOBAL_CKPT_STATUS](./reference-guide/schema/DBE_PERF/utility/GLOBAL_CKPT_STATUS.md)
+      + [GLOBAL_DOUBLE_WRITE_STATUS](./reference-guide/schema/DBE_PERF/utility/GLOBAL_DOUBLE_WRITE_STATUS.md)
+      + [GLOBAL_PAGEWRITER_STATUS](./reference-guide/schema/DBE_PERF/utility/GLOBAL_PAGEWRITER_STATUS.md)
+      + [GLOBAL_RECORD_RESET_TIME](./reference-guide/schema/DBE_PERF/utility/GLOBAL_RECORD_RESET_TIME.md)
+      + [GLOBAL_REDO_STATUS](./reference-guide/schema/DBE_PERF/utility/GLOBAL_REDO_STATUS.md)
+      + [GLOBAL_RECOVERY_STATUS](./reference-guide/schema/DBE_PERF/utility/GLOBAL_RECOVERY_STATUS.md)
+      + [CLASS_VITAL_INFO](./reference-guide/schema/DBE_PERF/utility/CLASS_VITAL_INFO.md)
+      + [USER_LOGIN](./reference-guide/schema/DBE_PERF/utility/USER_LOGIN.md)
+      + [SUMMARY_USER_LOGIN](./reference-guide/schema/DBE_PERF/utility/SUMMARY_USER_LOGIN.md)
+      + [GLOBAL_GET_BGWRITER_STATUS](./reference-guide/schema/DBE_PERF/utility/GLOBAL_GET_BGWRITER_STATUS.md)
+      + [GLOBAL_SINGLE_FLUSH_DW_STATUS](./reference-guide/schema/DBE_PERF/utility/GLOBAL_SINGLE_FLUSH_DW_STATUS.md)
+      + [GLOBAL_CANDIDATE_STATUS](./reference-guide/schema/DBE_PERF/utility/GLOBAL_CANDIDATE_STATUS.md)
+    + Lock
+      + [LOCKS](./reference-guide/schema/DBE_PERF/lock/LOCKS.md)
+      + [GLOBAL_LOCKS](./reference-guide/schema/DBE_PERF/lock/GLOBAL_LOCKS.md)
+    + Wait Events
+      + [WAIT_EVENTS](./reference-guide/schema/DBE_PERF/wait-events/WAIT_EVENTS.md)
+      + [GLOBAL_WAIT_EVENTS](./reference-guide/schema/DBE_PERF/wait-events/GLOBAL_WAIT_EVENTS.md)
+    + Configuration
+      + [CONFIG_SETTINGS](./reference-guide/schema/DBE_PERF/configuration/CONFIG_SETTINGS.md)
+      + [GLOBAL_CONFIG_SETTINGS](./reference-guide/schema/DBE_PERF/configuration/GLOBAL_CONFIG_SETTINGS.md)
+    + Operator
+      + [OPERATOR_HISTORY_TABLE](./reference-guide/schema/DBE_PERF/operator/OPERATOR_HISTORY_TABLE.md)
+      + [OPERATOR_HISTORY](./reference-guide/schema/DBE_PERF/operator/OPERATOR_HISTORY.md)
+      + [OPERATOR_RUNTIME](./reference-guide/schema/DBE_PERF/operator/OPERATOR_RUNTIME.md)
+      + [GLOBAL_OPERATOR_HISTORY](./reference-guide/schema/DBE_PERF/operator/GLOBAL_OPERATOR_HISTORY.md)
+      + [GLOBAL_OPERATOR_HISTORY_TABLE](./reference-guide/schema/DBE_PERF/operator/GLOBAL_OPERATOR_HISTORY_TABLE.md)
+      + [GLOBAL_OPERATOR_RUNTIME](./reference-guide/schema/DBE_PERF/operator/GLOBAL_OPERATOR_RUNTIME.md)
+    + Workload Manager
+      + [WLM_USER_RESOURCE_CONFIG](./reference-guide/schema/DBE_PERF/workload-manager/WLM_USER_RESOURCE_CONFIG.md)
+      + [WLM_USER_RESOURCE_RUNTIME](./reference-guide/schema/DBE_PERF/workload-manager/WLM_USER_RESOURCE_RUNTIME.md)
+    + Global Plancache
+      + [概述](./reference-guide/schema/DBE_PERF/global-plancache/global-plancache-overview.md)
+      + [GLOBAL_PLANCACHE_STATUS](./reference-guide/schema/DBE_PERF/global-plancache/GLOBAL_PLANCACHE_STATUS.md)
+      + [GLOBAL_PLANCACHE_CLEAN](./reference-guide/schema/DBE_PERF/global-plancache/GLOBAL_PLANCACHE_CLEAN.md)
+    + RTO
+      + [global_rto_status](./reference-guide/schema/DBE_PERF/rto/global_rto_status.md)
+    + 附录
+      + [等待状态列表](./reference-guide/schema/DBE_PERF/appendices/table-1.md)
+      + [轻量级锁等待事件列表](./reference-guide/schema/DBE_PERF/appendices/table-2.md)
+      + [IO等待事件列表](./reference-guide/schema/DBE_PERF/appendices/table-3.md)
+      + [事务锁等待事件列表](./reference-guide/schema/DBE_PERF/appendices/table-4.md)
+      + [GS_WLM_SESSION_HISTORY的字段](./reference-guide/schema/DBE_PERF/appendices/table-5.md)
+      + [GS_WLM_OPERATOR_INFO的字段](./reference-guide/schema/DBE_PERF/appendices/table-6.md)
+  + DBE_PLDEBUGGER Schema
+    + [DBE_PLDEBUGGER Schema概述](./reference-guide/schema/DBE_PLDEBUGGER-schema/overview-of-DBE_PLDEBUGGER-schema.md)
+    + [DBE_PLDEBUGGER.turn_on](./reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.turn_on.md)
+    + [DBE_PLDEBUGGER.turn_off](./reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.turn_off.md)
+    + [DBE_PLDEBUGGER.local_debug_server_info](./reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.local_debug_server_info.md)
+    + [DBE_PLDEBUGGER.attach](./reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.attach.md)
+    + [DBE_PLDEBUGGER.next](./reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.next.md)
+    + [DBE_PLDEBUGGER.continue](./reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.continue.md)
+    + [DBE_PLDEBUGGER.abort](./reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.abort.md)
+    + [DBE_PLDEBUGGER.print_var](./reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.print_var.md)
+    + [DBE_PLDEBUGGER.info_code](./reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.info_code.md)
+    + [DBE_PLDEBUGGER.step](./reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.step.md)
+    + [DBE_PLDEBUGGER.add_breakpoint](./reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.add_breakpoint.md)
+    + [DBE_PLDEBUGGER.delete_breakpoint](./reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.delete_breakpoint.md)
+    + [DBE_PLDEBUGGER.info_breakpoints](./reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.info_breakpoints.md)
+    + [DBE_PLDEBUGGER.backtrace](./reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.backtrace.md)
+    + [DBE_PLDEBUGGER.finish](./reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.finish.md)
+    + [DBE_PLDEBUGGER.set_var](./reference-guide/schema/DBE_PLDEBUGGER-schema/DBE_PLDEBUGGER.set_var.md)
+  + DB4AI Schema
+    + [DB4AI Schema概述](./reference-guide/schema/DB4AI-schema/overview-of-DB4AI-schema.md)
+    + [DB4AI.SNAPSHOT](./reference-guide/schema/DB4AI-schema/DB4AI.SNAPSHOT.md)
+    + [DB4AI.CREATE_SNAPSHOT](./reference-guide/schema/DB4AI-schema/DB4AI.CREATE_SNAPSHOT.md)
+    + [DB4AI.CREATE_SNAPSHOT_INTERNAL](./reference-guide/schema/DB4AI-schema/DB4AI.CREATE_SNAPSHOT_INTERNAL.md)
+    + [DB4AI.PREPARE_SNAPSHOT](./reference-guide/schema/DB4AI-schema/DB4AI.PREPARE_SNAPSHOT.md)
+    + [DB4AI.PREPARE_SNAPSHOT_INTERNAL](./reference-guide/schema/DB4AI-schema/DB4AI.PREPARE_SNAPSHOT_INTERNAL.md)
+    + [DB4AI.ARCHIVE_SNAPSHOT](./reference-guide/schema/DB4AI-schema/DB4AI.ARCHIVE_SNAPSHOT.md)
+    + [DB4AI.PUBLISH_SNAPSHOT](./reference-guide/schema/DB4AI-schema/DB4AI.PUBLISH_SNAPSHOT.md)
+    + [DB4AI.MANAGE_SNAPSHOT_INTERNAL](./reference-guide/schema/DB4AI-schema/DB4AI.MANAGE_SNAPSHOT_INTERNAL.md)
+    + [DB4AI.SAMPLE_SNAPSHOT](./reference-guide/schema/DB4AI-schema/DB4AI.SAMPLE_SNAPSHOT.md)
+    + [DB4AI.PURGE_SNAPSHOT](./reference-guide/schema/DB4AI-schema/DB4AI.PURGE_SNAPSHOT.md)
+    + [DB4AI.PURGE_SNAPSHOT_INTERNAL](./reference-guide/schema/DB4AI-schema/DB4AI.PURGE_SNAPSHOT_INTERNAL.md)
++ 工具参考
+  + [工具一览表](./reference-guide/tool-reference/tool-overview.md)
+  + [客户端工具](./reference-guide/tool-reference/client-tool.md)
+  + 服务端工具
+    + [gs_cgroup](./reference-guide/tool-reference/server-tools/0-gs_cgroup.md)
+    + [gs_check](./reference-guide/tool-reference/server-tools/1-gs_check.md)
+    + [gs_checkos](./reference-guide/tool-reference/server-tools/2-gs_checkos.md)
+    + [gs_checkperf](./reference-guide/tool-reference/server-tools/3-gs_checkperf.md)
+    + [gs_collector](./reference-guide/tool-reference/server-tools/4-gs_collector.md)
+    + [gs_dump](./reference-guide/tool-reference/server-tools/5-gs_dump.md)
+    + [gs_dumpall](./reference-guide/tool-reference/server-tools/6-gs_dumpall.md)
+    + [gs_guc](./reference-guide/tool-reference/server-tools/7-gs_guc.md)
+    + [gs_encrypt](./reference-guide/tool-reference/server-tools/7.1-gs_encrypt.md)
+    + [gs_om](./reference-guide/tool-reference/server-tools/8-gs_om.md)
+    + [gs_plan_simulator](./reference-guide/tool-reference/server-tools/8.1-gs_plan_simulator.md)
+    + [gs_restore](./reference-guide/tool-reference/server-tools/9-gs_restore.md)
+    + [gs_ssh](./reference-guide/tool-reference/server-tools/10-gs_ssh.md)
+  + 系统内部使用的工具
+    + [gaussdb](./reference-guide/tool-reference/tools-used-in-the-internal-system/1-gaussdb.md)
+    + [gs_backup](./reference-guide/tool-reference/tools-used-in-the-internal-system/2-gs_backup.md)
+    + [gs_basebackup](./reference-guide/tool-reference/tools-used-in-the-internal-system/3-gs_basebackup.md)
+    + [gs_ctl](./reference-guide/tool-reference/tools-used-in-the-internal-system/4-gs_ctl.md)
+    + [gs_initdb](./reference-guide/tool-reference/tools-used-in-the-internal-system/5-gs_initdb.md)
+    + [gs_install](./reference-guide/tool-reference/tools-used-in-the-internal-system/6-gs_install.md)
+    + [gs_install_plugin](/reference-guide/tool-reference/tools-used-in-the-internal-system/gs_install_plugin.md)
+    + [gs_install_plugin_local](/reference-guide/tool-reference/tools-used-in-the-internal-system/gs_install_plugin_local.md)
+    + [gs_postuninstall](./reference-guide/tool-reference/tools-used-in-the-internal-system/7-gs_postuninstall.md)
+    + [gs_preinstall](./reference-guide/tool-reference/tools-used-in-the-internal-system/8-gs_preinstall.md)
+    + [gs_sshexkey](./reference-guide/tool-reference/tools-used-in-the-internal-system/9-gs_sshexkey.md)
+    + [gs_tar](./reference-guide/tool-reference/tools-used-in-the-internal-system/10-gs_tar.md)
+    + [gs_uninstall](./reference-guide/tool-reference/tools-used-in-the-internal-system/11-gs_uninstall.md)
+    + [gs_upgradectl](./reference-guide/tool-reference/tools-used-in-the-internal-system/12-gs_upgradectl.md)
+    + [gs_expansion](./reference-guide/tool-reference/tools-used-in-the-internal-system/13-gs_expansion.md)
+    + [gs_dropnode](./reference-guide/tool-reference/tools-used-in-the-internal-system/14-gs_dropnode.md)
+    + [gs_probackup](./reference-guide/tool-reference/tools-used-in-the-internal-system/15-gs_probackup.md)
+    + [gstrace](./reference-guide/tool-reference/tools-used-in-the-internal-system/16-gstrace.md)
+    + [kdb5_util](./reference-guide/tool-reference/tools-used-in-the-internal-system/17-kdb5_util.md)
+    + [kadmin.local](./reference-guide/tool-reference/tools-used-in-the-internal-system/18-kadmin-local.md)
+    + [kinit](./reference-guide/tool-reference/tools-used-in-the-internal-system/19-kinit.md)
+    + [klist](./reference-guide/tool-reference/tools-used-in-the-internal-system/20-klist.md)
+    + [krb5kdc](./reference-guide/tool-reference/tools-used-in-the-internal-system/21-krb5kdc.md)
+    + [kdestroy](./reference-guide/tool-reference/tools-used-in-the-internal-system/22-kdestroy.md)
+    + [pg_config](./reference-guide/tool-reference/tools-used-in-the-internal-system/23-pg_config.md)
+    + [pg_controldata](./reference-guide/tool-reference/tools-used-in-the-internal-system/24-pg_controldata.md)
+    + [pg_recvlogical](./reference-guide/tool-reference/tools-used-in-the-internal-system/24.1-pg_recvlogical.md)
+    + [pg_resetxlog](./reference-guide/tool-reference/tools-used-in-the-internal-system/25-pg_resetxlog.md)
+    + [pg_archivecleanup](./reference-guide/tool-reference/tools-used-in-the-internal-system/26-pg_archivecleanup.md)
+    + [pssh](./reference-guide/tool-reference/tools-used-in-the-internal-system/27-pssh.md)
+    + [pscp](./reference-guide/tool-reference/tools-used-in-the-internal-system/28-pscp.md)
+    + [transfer.py](./reference-guide/tool-reference/tools-used-in-the-internal-system/29-transfer.py.md)
+  + [FAQ](./reference-guide/tool-reference/FAQ.md)
+  + [gs_collector工具支持收集的系统表和视图列表](./reference-guide/tool-reference/system-catalogs-and-views-supported-by-gs_collector.md)
diff --git a/product/zh/docs-mogdb/v3.0/toc_performance.md b/product/zh/docs-mogdb/v3.0/toc_performance.md
new file mode 100644
index 0000000000000000000000000000000000000000..55742ec896c7d94415fdeffd35f4fcc000729bde
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/toc_performance.md
@@ -0,0 +1,23 @@
+<!-- markdownlint-disable MD007 -->
+<!-- markdownlint-disable MD041 -->
+# MogDB Documentation 3.0
+
+## 性能优化指南
+
++ 系统优化指南
+  + [操作系统参数调优](/performance-tuning/1-system/1-optimizing-os-parameters.md)
+  + [数据库系统参数调优](/performance-tuning/1-system/2-optimizing-database-parameters.md)
+  + [配置SMP](/performance-tuning/1-system/4-configuring-smp.md)
+  + [配置LLVM](/performance-tuning/1-system/3-configuring-llvm.md)
++ SQL优化指南
+  + [Query执行流程](/performance-tuning/2-sql/1-query-execution-process.md)
+  + [SQL执行计划介绍](/performance-tuning/2-sql/2-introduction-to-the-sql-execution-plan.md)
+  + [调优流程](/performance-tuning/2-sql/3-tuning-process.md)
+  + [更新统计信息](/performance-tuning/2-sql/4-updating-statistics.md)
+  + [审视和修改表定义](/performance-tuning/2-sql/5-reviewing-and-modifying-a-table-definition.md)
+  + [典型SQL调优点](/performance-tuning/2-sql/6-typical-sql-optimization-methods.md)
+  + [SQL语句改写规则](/performance-tuning/2-sql/7-experience-in-rewriting-sql-statements.md)
+  + [SQL调优关键参数调整](/performance-tuning/2-sql/8-resetting-key-parameters-during-sql-tuning.md)
+  + [使用Plan Hint进行调优](/performance-tuning/2-sql/9-hint-based-tuning.md)
++ [WDR解读指南](/performance-tuning/wdr-snapshot-schema.md)
++ [TPCC性能优化指南](/performance-tuning/TPCC-performance-tuning-guide.md)
diff --git a/product/zh/docs-mogdb/v3.0/toc_quickstart.md b/product/zh/docs-mogdb/v3.0/toc_quickstart.md
new file mode 100644
index 0000000000000000000000000000000000000000..22acb610f3bb7c08fc3d838a4d0f4bd3611699ac
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/toc_quickstart.md
@@ -0,0 +1,27 @@
+<!-- markdownlint-disable MD007 -->
+<!-- markdownlint-disable MD041 -->
+# MogDB Documentation 3.0
+
+## 快速入门
+
++ [MogDB实训平台](/quick-start/mogdb-playground.md)
++ [容器化安装](/quick-start/container-based-installation.md)
++ [单节点安装](/quick-start/installation-on-a-single-node.md)
++ 访问数据库
+  + 使用命令行访问MogDB
+    + [gsql](/quick-start/mogdb-access/use-cli-to-access-mogdb/gsql.md)
+    + [pgcli](/quick-start/mogdb-access/use-cli-to-access-mogdb/pgcli.md)
+  + 使用图形工具访问MogDB
+    + [Data Studio](/quick-start/mogdb-access/use-gui-tools-to-access-mogdb/datastudio.md)
+    + [DBeaver](/quick-start/mogdb-access/use-gui-tools-to-access-mogdb/dbeaver.md)
+  + 使用中间件访问MogDB
+    + [WebLogic配置MogDB数据源参考](/quick-start/mogdb-access/use-middleware-to-access-mogdb/weblogic-configures-mogdb(postgresql)-data-source-reference.md)
+    + [WebSphere配置MogDB数据源参考](/quick-start/mogdb-access/use-middleware-to-access-mogdb/websphere-configures-mogdb(postgresql)-data-source-reference.md)
+  + 使用编程语言访问MogDB
+    + [Java](/quick-start/mogdb-access/use-programming-language-to-access-mogdb/java.md)
+    + [C/C++](/quick-start/mogdb-access/use-programming-language-to-access-mogdb/c-cpp.md)
+    + [Python](/quick-start/mogdb-access/use-programming-language-to-access-mogdb/python.md)
+    + [Go](/quick-start/mogdb-access/use-programming-language-to-access-mogdb/go.md)
+    + [Rust](/quick-start/mogdb-access/use-programming-language-to-access-mogdb/rust.md)
+    + [NodeJS](/quick-start/mogdb-access/use-programming-language-to-access-mogdb/nodejs.md)
++ [使用样本数据集Mogila](/quick-start/mogila.md)
\ No newline at end of file
diff --git a/product/zh/docs-mogdb/v3.0/toc_secure.md b/product/zh/docs-mogdb/v3.0/toc_secure.md
new file mode 100644
index 0000000000000000000000000000000000000000..cdf1a0798f2eba27746047d56e6ae5a6ffe2297c
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/toc_secure.md
@@ -0,0 +1,11 @@
+<!-- markdownlint-disable MD007 -->
+<!-- markdownlint-disable MD041 -->
+# MogDB Documentation 3.0
+
+## 安全指南
+
++ [客户端接入认证](/security-guide/security/1-client-access-authentication.md)
++ [管理用户及权限](/security-guide/security/2-managing-users-and-their-permissions.md)
++ [设置数据库审计](/security-guide/security/3-configuring-database-audit.md)
++ [设置密态等值查询](/security-guide/security/4-setting-encrypted-equality-query.md)
++ [设置账本数据库](/security-guide/security/5-setting-a-ledger-database.md)
diff --git a/product/zh/docs-mogdb/v3.0/toc_system-catalogs-and-functions.md b/product/zh/docs-mogdb/v3.0/toc_system-catalogs-and-functions.md
new file mode 100644
index 0000000000000000000000000000000000000000..f3d6aa2fb5a9c4b31976669966fd542961471e7d
--- /dev/null
+++ b/product/zh/docs-mogdb/v3.0/toc_system-catalogs-and-functions.md
@@ -0,0 +1,248 @@
+<!-- markdownlint-disable MD007 -->
+<!-- markdownlint-disable MD041 -->
+
+# MogDB Documentation 3.0
+
+## 系统表及函数
+
++ 系统表及系统视图
+  + [系统表和系统视图概述](./reference-guide/system-catalogs-and-system-views/overview-of-system-catalogs-and-system-views.md)
+  + 系统表
+    + [GS_AUDITING_POLICY](./reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY.md)
+    + [GS_AUDITING_POLICY_ACCESS](./reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY_ACCESS.md)
+    + [GS_AUDITING_POLICY_FILTERS](./reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY_FILTERS.md)
+    + [GS_AUDITING_POLICY_PRIVILEGES](./reference-guide/system-catalogs-and-system-views/system-catalogs/GS_AUDITING_POLICY_PRIVILEGES.md)
+    + [GS_CLIENT_GLOBAL_KEYS](./reference-guide/system-catalogs-and-system-views/system-catalogs/GS_CLIENT_GLOBAL_KEYS.md)
+    + [GS_CLIENT_GLOBAL_KEYS_ARGS](./reference-guide/system-catalogs-and-system-views/system-catalogs/GS_CLIENT_GLOBAL_KEYS_ARGS.md)
+    + [GS_COLUMN_KEYS](./reference-guide/system-catalogs-and-system-views/system-catalogs/GS_COLUMN_KEYS.md)
+    + [GS_COLUMN_KEYS_ARGS](./reference-guide/system-catalogs-and-system-views/system-catalogs/GS_COLUMN_KEYS_ARGS.md)
+    + [GS_ENCRYPTED_COLUMNS](./reference-guide/system-catalogs-and-system-views/system-catalogs/GS_ENCRYPTED_COLUMNS.md)
+    + [GS_ENCRYPTED_PROC](./reference-guide/system-catalogs-and-system-views/system-catalogs/GS_ENCRYPTED_PROC.md)
+    + [GS_GLOBAL_CHAIN](./reference-guide/system-catalogs-and-system-views/system-catalogs/GS_GLOBAL_CHAIN.md)
+    + [GS_MASKING_POLICY](./reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MASKING_POLICY.md)
+    + [GS_MASKING_POLICY_ACTIONS](./reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MASKING_POLICY_ACTIONS.md)
+    + [GS_MASKING_POLICY_FILTERS](./reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MASKING_POLICY_FILTERS.md)
+    + [GS_MATVIEW](./reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MATVIEW.md)
+    + [GS_MATVIEW_DEPENDENCY](./reference-guide/system-catalogs-and-system-views/system-catalogs/GS_MATVIEW_DEPENDENCY.md)
+    + [GS_OPT_MODEL](./reference-guide/system-catalogs-and-system-views/system-catalogs/GS_OPT_MODEL.md)
+    + [GS_POLICY_LABEL](./reference-guide/system-catalogs-and-system-views/system-catalogs/GS_POLICY_LABEL.md)
+    + [GS_RECYCLEBIN](./reference-guide/system-catalogs-and-system-views/system-catalogs/GS_RECYCLEBIN.md)
+    + [GS_TXN_SNAPSHOT](./reference-guide/system-catalogs-and-system-views/system-catalogs/GS_TXN_SNAPSHOT.md)
+    + [GS_WLM_INSTANCE_HISTORY](./reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_INSTANCE_HISTORY.md)
+    + [GS_WLM_OPERATOR_INFO](./reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_OPERATOR_INFO.md)
+    + [GS_WLM_PLAN_ENCODING_TABLE](./reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_PLAN_ENCODING_TABLE.md)
+    + [GS_WLM_PLAN_OPERATOR_INFO](./reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_PLAN_OPERATOR_INFO.md)
+    + [GS_WLM_EC_OPERATOR_INFO](./reference-guide/system-catalogs-and-system-views/system-catalogs/GS_WLM_EC_OPERATOR_INFO.md)
+    + [PG_AGGREGATE](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AGGREGATE.md)
+    + [PG_AM](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AM.md)
+    + [PG_AMOP](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AMOP.md)
+    + [PG_AMPROC](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AMPROC.md)
+    + [PG_APP_WORKLOADGROUP_MAPPING](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_APP_WORKLOADGROUP_MAPPING.md)
+    + [PG_ATTRDEF](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_ATTRDEF.md)
+    + [PG_ATTRIBUTE](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_ATTRIBUTE.md)
+    + [PG_AUTHID](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AUTHID.md)
+    + [PG_AUTH_HISTORY](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AUTH_HISTORY.md)
+    + [PG_AUTH_MEMBERS](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_AUTH_MEMBERS.md)
+    + [PG_CAST](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CAST.md)
+    + [PG_CLASS](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CLASS.md)
+    + [PG_COLLATION](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_COLLATION.md)
+    + [PG_CONSTRAINT](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CONSTRAINT.md)
+    + [PG_CONVERSION](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_CONVERSION.md)
+    + [PG_DATABASE](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DATABASE.md)
+    + [PG_DB_ROLE_SETTING](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DB_ROLE_SETTING.md)
+    + [PG_DEFAULT_ACL](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DEFAULT_ACL.md)
+    + [PG_DEPEND](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DEPEND.md)
+    + [PG_DESCRIPTION](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DESCRIPTION.md)
+    + [PG_DIRECTORY](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_DIRECTORY.md)
+    + [PG_ENUM](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_ENUM.md)
+    + [PG_EXTENSION](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_EXTENSION.md)
+    + [PG_EXTENSION_DATA_SOURCE](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_EXTENSION_DATA_SOURCE.md)
+    + [PG_FOREIGN_DATA_WRAPPER](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_FOREIGN_DATA_WRAPPER.md)
+    + [PG_FOREIGN_SERVER](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_FOREIGN_SERVER.md)
+    + [PG_FOREIGN_TABLE](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_FOREIGN_TABLE.md)
+    + [PG_INDEX](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_INDEX.md)
+    + [PG_INHERITS](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_INHERITS.md)
+    + [PG_JOB](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_JOB.md)
+    + [PG_JOB_PROC](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_JOB_PROC.md)
+    + [PG_LANGUAGE](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_LANGUAGE.md)
+    + [PG_LARGEOBJECT](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_LARGEOBJECT.md)
+    + [PG_LARGEOBJECT_METADATA](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_LARGEOBJECT_METADATA.md)
+    + [PG_NAMESPACE](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_NAMESPACE.md)
+    + [PG_OBJECT](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OBJECT.md)
+    + [PG_OPCLASS](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OPCLASS.md)
+    + [PG_OPERATOR](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OPERATOR.md)
+    + [PG_OPFAMILY](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_OPFAMILY.md)
+    + [PG_PARTITION](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_PARTITION.md)
+    + [PG_PLTEMPLATE](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_PLTEMPLATE.md)
+    + [PG_PROC](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_PROC.md)
+    + [PG_RANGE](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_RANGE.md)
+    + [PG_RESOURCE_POOL](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_RESOURCE_POOL.md)
+    + [PG_REWRITE](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_REWRITE.md)
+    + [PG_RLSPOLICY](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_RLSPOLICY.md)
+    + [PG_SECLABEL](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SECLABEL.md)
+    + [PG_SHDEPEND](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SHDEPEND.md)
+    + [PG_SHDESCRIPTION](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SHDESCRIPTION.md)
+    + [PG_SHSECLABEL](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SHSECLABEL.md)
+    + [PG_STATISTIC](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_STATISTIC.md)
+    + [PG_STATISTIC_EXT](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_STATISTIC_EXT.md)
+    + [PG_SYNONYM](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_SYNONYM.md)
+    + [PG_TABLESPACE](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TABLESPACE.md)
+    + [PG_TRIGGER](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TRIGGER.md)
+    + [PG_TS_CONFIG](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_CONFIG.md)
+    + [PG_TS_CONFIG_MAP](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_CONFIG_MAP.md)
+    + [PG_TS_DICT](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_DICT.md)
+    + [PG_TS_PARSER](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_PARSER.md)
+    + [PG_TS_TEMPLATE](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TS_TEMPLATE.md)
+    + [PG_TYPE](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_TYPE.md)
+    + [PG_USER_MAPPING](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_USER_MAPPING.md)
+    + [PG_USER_STATUS](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_USER_STATUS.md)
+    + [PG_WORKLOAD_GROUP](./reference-guide/system-catalogs-and-system-views/system-catalogs/PG_WORKLOAD_GROUP.md)
+    + [PLAN_TABLE_DATA](./reference-guide/system-catalogs-and-system-views/system-catalogs/PLAN_TABLE_DATA.md)
+    + [STATEMENT_HISTORY](./reference-guide/system-catalogs-and-system-views/system-catalogs/STATEMENT_HISTORY.md)
+  + 系统视图
+    + [GET_GLOBAL_PREPARED_XACTS（废弃）](./reference-guide/system-catalogs-and-system-views/system-views/GET_GLOBAL_PREPARED_XACTS.md)
+    + [GS_AUDITING](./reference-guide/system-catalogs-and-system-views/system-views/GS_AUDITING.md)
+    + [GS_AUDITING_ACCESS](./reference-guide/system-catalogs-and-system-views/system-views/GS_AUDITING_ACCESS.md)
+    + [GS_AUDITING_PRIVILEGE](./reference-guide/system-catalogs-and-system-views/system-views/GS_AUDITING_PRIVILEGE.md)
+    + [GS_CLUSTER_RESOURCE_INFO](./reference-guide/system-catalogs-and-system-views/system-views/GS_CLUSTER_RESOURCE_INFO.md)
+    + [GS_INSTANCE_TIME](./reference-guide/system-catalogs-and-system-views/system-views/GS_INSTANCE_TIME.md)
+    + [GS_LABELS](./reference-guide/system-catalogs-and-system-views/system-views/GS_LABELS.md)
+    + [GS_MASKING](./reference-guide/system-catalogs-and-system-views/system-views/GS_MASKING.md)
+    + [GS_MATVIEWS](./reference-guide/system-catalogs-and-system-views/system-views/GS_MATVIEWS.md)
+    + [GS_SESSION_MEMORY](./reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY.md)
+    + [GS_SESSION_CPU_STATISTICS](./reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_CPU_STATISTICS.md)
+    + [GS_SESSION_MEMORY_CONTEXT](./reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY_CONTEXT.md)
+    + [GS_SESSION_MEMORY_DETAIL](./reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY_DETAIL.md)
+    + [GS_SESSION_MEMORY_STATISTICS](./reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_MEMORY_STATISTICS.md)
+    + [GS_SQL_COUNT](./reference-guide/system-catalogs-and-system-views/system-views/GS_SQL_COUNT.md)
+    + [GS_WLM_CGROUP_INFO](./reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_CGROUP_INFO.md)
+    + [GS_WLM_PLAN_OPERATOR_HISTORY](./reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_PLAN_OPERATOR_HISTORY.md)
+    + [GS_WLM_REBUILD_USER_RESOURCE_POOL](./reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_REBUILD_USER_RESOURCE_POOL.md)
+    + [GS_WLM_RESOURCE_POOL](./reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_RESOURCE_POOL.md)
+    + [GS_WLM_USER_INFO](./reference-guide/system-catalogs-and-system-views/system-views/GS_WLM_USER_INFO.md)
+    + [GS_STAT_SESSION_CU](./reference-guide/system-catalogs-and-system-views/system-views/GS_STAT_SESSION_CU.md)
+    + [GS_TOTAL_MEMORY_DETAIL](./reference-guide/system-catalogs-and-system-views/system-views/GS_TOTAL_MEMORY_DETAIL.md)
+    + [MPP_TABLES](./reference-guide/system-catalogs-and-system-views/system-views/MPP_TABLES.md)
+    + [PG_AVAILABLE_EXTENSION_VERSIONS](./reference-guide/system-catalogs-and-system-views/system-views/PG_AVAILABLE_EXTENSION_VERSIONS.md)
+    + [PG_AVAILABLE_EXTENSIONS](./reference-guide/system-catalogs-and-system-views/system-views/PG_AVAILABLE_EXTENSIONS.md)
+    + [PG_COMM_DELAY](./reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_DELAY.md)
+    + [PG_COMM_RECV_STREAM](./reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_RECV_STREAM.md)
+    + [PG_COMM_SEND_STREAM](./reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_SEND_STREAM.md)
+    + [PG_COMM_STATUS](./reference-guide/system-catalogs-and-system-views/system-views/PG_COMM_STATUS.md)
+    + [PG_CONTROL_GROUP_CONFIG](./reference-guide/system-catalogs-and-system-views/system-views/PG_CONTROL_GROUP_CONFIG.md)
+    + [PG_CURSORS](./reference-guide/system-catalogs-and-system-views/system-views/PG_CURSORS.md)
+    + [PG_EXT_STATS](./reference-guide/system-catalogs-and-system-views/system-views/PG_EXT_STATS.md)
+    + [PG_GET_INVALID_BACKENDS](./reference-guide/system-catalogs-and-system-views/system-views/PG_GET_INVALID_BACKENDS.md)
+    + [PG_GET_SENDERS_CATCHUP_TIME](./reference-guide/system-catalogs-and-system-views/system-views/PG_GET_SENDERS_CATCHUP_TIME.md)
+    + [PG_GROUP](./reference-guide/system-catalogs-and-system-views/system-views/PG_GROUP.md)
+    + [PG_GTT_RELSTATS](./reference-guide/system-catalogs-and-system-views/system-views/PG_GTT_RELSTATS.md)
+    + [PG_GTT_STATS](./reference-guide/system-catalogs-and-system-views/system-views/PG_GTT_STATS.md)
+    + [PG_GTT_ATTACHED_PIDS](./reference-guide/system-catalogs-and-system-views/system-views/PG_GTT_ATTACHED_PIDS.md)
+    + [PG_INDEXES](./reference-guide/system-catalogs-and-system-views/system-views/PG_INDEXES.md)
+    + [PG_LOCKS](./reference-guide/system-catalogs-and-system-views/system-views/PG_LOCKS.md)
+    + [PG_NODE_ENV](./reference-guide/system-catalogs-and-system-views/system-views/PG_NODE_ENV.md)
+    + [PG_OS_THREADS](./reference-guide/system-catalogs-and-system-views/system-views/PG_OS_THREADS.md)
+    + [PG_PREPARED_STATEMENTS](./reference-guide/system-catalogs-and-system-views/system-views/PG_PREPARED_STATEMENTS.md)
+    + [PG_PREPARED_XACTS](./reference-guide/system-catalogs-and-system-views/system-views/PG_PREPARED_XACTS.md)
+    + [PG_REPLICATION_SLOTS](./reference-guide/system-catalogs-and-system-views/system-views/PG_REPLICATION_SLOTS.md)
+    + [PG_RLSPOLICIES](./reference-guide/system-catalogs-and-system-views/system-views/PG_RLSPOLICIES.md)
+    + [PG_ROLES](./reference-guide/system-catalogs-and-system-views/system-views/PG_ROLES.md)
+    + [PG_RULES](./reference-guide/system-catalogs-and-system-views/system-views/PG_RULES.md)
+    + [PG_SECLABELS](./reference-guide/system-catalogs-and-system-views/system-views/PG_SECLABELS.md)
+    + [PG_SETTINGS](./reference-guide/system-catalogs-and-system-views/system-views/PG_SETTINGS.md)
+    + [PG_SHADOW](./reference-guide/system-catalogs-and-system-views/system-views/PG_SHADOW.md)
+    + [PG_STATS](./reference-guide/system-catalogs-and-system-views/system-views/PG_STATS.md)
+    + [PG_STAT_ACTIVITY](./reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_ACTIVITY.md)
+    + [PG_STAT_ALL_INDEXES](./reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_ALL_INDEXES.md)
+    + [PG_STAT_ALL_TABLES](./reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_ALL_TABLES.md)
+    + [PG_STAT_BAD_BLOCK](./reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_BAD_BLOCK.md)
+    + [PG_STAT_BGWRITER](./reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_BGWRITER.md)
+    + [PG_STAT_DATABASE](./reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_DATABASE.md)
+    + [PG_STAT_DATABASE_CONFLICTS](./reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_DATABASE_CONFLICTS.md)
+    + [PG_STAT_USER_FUNCTIONS](./reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_USER_FUNCTIONS.md)
+    + [PG_STAT_USER_INDEXES](./reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_USER_INDEXES.md)
+    + [PG_STAT_USER_TABLES](./reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_USER_TABLES.md)
+    + [PG_STAT_REPLICATION](./reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_REPLICATION.md)
+    + [PG_STAT_SYS_INDEXES](./reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_SYS_INDEXES.md)
+    + [PG_STAT_SYS_TABLES](./reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_SYS_TABLES.md)
+    + [PG_STAT_XACT_ALL_TABLES](./reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_ALL_TABLES.md)
+    + [PG_STAT_XACT_SYS_TABLES](./reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_SYS_TABLES.md)
+    + [PG_STAT_XACT_USER_FUNCTIONS](./reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_USER_FUNCTIONS.md)
+    + [PG_STAT_XACT_USER_TABLES](./reference-guide/system-catalogs-and-system-views/system-views/PG_STAT_XACT_USER_TABLES.md)
+    + [PG_STATIO_ALL_INDEXES](./reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_ALL_INDEXES.md)
+    + [PG_STATIO_ALL_SEQUENCES](./reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_ALL_SEQUENCES.md)
+    + [PG_STATIO_ALL_TABLES](./reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_ALL_TABLES.md)
+    + [PG_STATIO_SYS_INDEXES](./reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_SYS_INDEXES.md)
+    + [PG_STATIO_SYS_SEQUENCES](./reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_SYS_SEQUENCES.md)
+    + [PG_STATIO_SYS_TABLES](./reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_SYS_TABLES.md)
+    + [PG_STATIO_USER_INDEXES](./reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_USER_INDEXES.md)
+    + [PG_STATIO_USER_SEQUENCES](./reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_USER_SEQUENCES.md)
+    + [PG_STATIO_USER_TABLES](./reference-guide/system-catalogs-and-system-views/system-views/PG_STATIO_USER_TABLES.md)
+    + [PG_TABLES](./reference-guide/system-catalogs-and-system-views/system-views/PG_TABLES.md)
+    + [PG_TDE_INFO](./reference-guide/system-catalogs-and-system-views/system-views/PG_TDE_INFO.md)
+    + [PG_THREAD_WAIT_STATUS](./reference-guide/system-catalogs-and-system-views/system-views/PG_THREAD_WAIT_STATUS.md)
+    + [PG_TIMEZONE_ABBREVS](./reference-guide/system-catalogs-and-system-views/system-views/PG_TIMEZONE_ABBREVS.md)
+    + [PG_TIMEZONE_NAMES](./reference-guide/system-catalogs-and-system-views/system-views/PG_TIMEZONE_NAMES.md)
+    + [PG_TOTAL_MEMORY_DETAIL](./reference-guide/system-catalogs-and-system-views/system-views/PG_TOTAL_MEMORY_DETAIL.md)
+    + [PG_TOTAL_USER_RESOURCE_INFO](./reference-guide/system-catalogs-and-system-views/system-views/PG_TOTAL_USER_RESOURCE_INFO.md)
+    + [PG_TOTAL_USER_RESOURCE_INFO_OID](./reference-guide/system-catalogs-and-system-views/system-views/PG_TOTAL_USER_RESOURCE_INFO_OID.md)
+    + [PG_USER](./reference-guide/system-catalogs-and-system-views/system-views/PG_USER.md)
+    + [PG_USER_MAPPINGS](./reference-guide/system-catalogs-and-system-views/system-views/PG_USER_MAPPINGS.md)
+    + [PG_VARIABLE_INFO](./reference-guide/system-catalogs-and-system-views/system-views/PG_VARIABLE_INFO.md)
+    + [PG_VIEWS](./reference-guide/system-catalogs-and-system-views/system-views/PG_VIEWS.md)
+    + [PLAN_TABLE](./reference-guide/system-catalogs-and-system-views/system-views/PLAN_TABLE.md)
+    + [GS_FILE_STAT](./reference-guide/system-catalogs-and-system-views/system-views/GS_FILE_STAT.md)
+    + [GS_OS_RUN_INFO](./reference-guide/system-catalogs-and-system-views/system-views/GS_OS_RUN_INFO.md)
+    + [GS_REDO_STAT](./reference-guide/system-catalogs-and-system-views/system-views/GS_REDO_STAT.md)
+    + [GS_SESSION_STAT](./reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_STAT.md)
+    + [GS_SESSION_TIME](./reference-guide/system-catalogs-and-system-views/system-views/GS_SESSION_TIME.md)
+    + [GS_THREAD_MEMORY_CONTEXT](./reference-guide/system-catalogs-and-system-views/system-views/GS_THREAD_MEMORY_CONTEXT.md)
++ 系统函数
+  + [逻辑操作符](./reference-guide/functions-and-operators/1-logical-operators.md)
+  + [比较操作符](./reference-guide/functions-and-operators/2-comparison-operators.md)
+  + [字符处理函数和操作符](./reference-guide/functions-and-operators/3-character-processing-functions-and-operators.md)
+  + [二进制字符串函数和操作符](./reference-guide/functions-and-operators/4-binary-string-functions-and-operators.md)
+  + [位串函数和操作符](./reference-guide/functions-and-operators/5-bit-string-functions-and-operators.md)
+  + [模式匹配操作符](./reference-guide/functions-and-operators/6-mode-matching-operators.md)
+  + [数字操作函数和操作符](./reference-guide/functions-and-operators/7-mathematical-functions-and-operators.md)
+  + [时间和日期处理函数和操作符](./reference-guide/functions-and-operators/8-date-and-time-processing-functions-and-operators.md)
+  + [类型转换函数](./reference-guide/functions-and-operators/9-type-conversion-functions.md)
+  + [几何函数和操作符](./reference-guide/functions-and-operators/10-geometric-functions-and-operators.md)
+  + [网络地址函数和操作符](./reference-guide/functions-and-operators/11-network-address-functions-and-operators.md)
+  + [文本检索函数和操作符](./reference-guide/functions-and-operators/12-text-search-functions-and-operators.md)
+  + [JSON/JSONB函数和操作符](./reference-guide/functions-and-operators/13-json-functions.md)
+  + [HLL函数和操作符](./reference-guide/functions-and-operators/13.1-hll-functions-and-operators.md)
+  + [SEQUENCE函数](./reference-guide/functions-and-operators/14-sequence-functions.md)
+  + [数组函数和操作符](./reference-guide/functions-and-operators/15-array-functions-and-operators.md)
+  + [范围函数和操作符](./reference-guide/functions-and-operators/16-range-functions-and-operators.md)
+  + [聚集函数](./reference-guide/functions-and-operators/17-aggregate-functions.md)
+  + [窗口函数](./reference-guide/functions-and-operators/18-window-functions.md)
+  + [安全函数](./reference-guide/functions-and-operators/19-security-functions.md)
+  + [账本数据库的函数](./reference-guide/functions-and-operators/20.1-ledger-database-functions.md)
+  + [密态等值的函数](./reference-guide/functions-and-operators/20-encrypted-equality-functions.md)
+  + [返回集合的函数](./reference-guide/functions-and-operators/21-set-returning-functions.md)
+  + [条件表达式函数](./reference-guide/functions-and-operators/22-conditional-expressions-functions.md)
+  + [系统信息函数](./reference-guide/functions-and-operators/23-system-information-functions.md)
+  + 系统管理函数
+    + [配置设置函数](./reference-guide/functions-and-operators/24-system-management-functions/1-configuration-settings-functions.md)
+    + [通用文件访问函数](./reference-guide/functions-and-operators/24-system-management-functions/2-universal-file-access-functions.md)
+    + [服务器信号函数](./reference-guide/functions-and-operators/24-system-management-functions/3-server-signal-functions.md)
+    + [备份恢复控制函数](./reference-guide/functions-and-operators/24-system-management-functions/4-backup-and-restoration-control-functions.md)
+    + [快照同步函数](./reference-guide/functions-and-operators/24-system-management-functions/5-snapshot-synchronization-functions.md)
+    + [数据库对象函数](./reference-guide/functions-and-operators/24-system-management-functions/6-database-object-functions.md)
+    + [咨询锁函数](./reference-guide/functions-and-operators/24-system-management-functions/7-advisory-lock-functions.md)
+    + [逻辑复制函数](./reference-guide/functions-and-operators/24-system-management-functions/8-logical-replication-functions.md)
+    + [段页式存储函数](./reference-guide/functions-and-operators/24-system-management-functions/9.1-segment-page-storage-functions.md)
+    + [其它函数](./reference-guide/functions-and-operators/24-system-management-functions/9-other-functions.md)
+    + [Undo系统函数](./reference-guide/functions-and-operators/24-system-management-functions/10-undo-system-functions.md)
+  + [统计信息函数](./reference-guide/functions-and-operators/25-statistics-information-functions.md)
+  + [触发器函数](./reference-guide/functions-and-operators/26-trigger-functions.md)
+  + [HashFunc函数](./reference-guide/functions-and-operators/27.1-hash-function.md)
+  + [提示信息函数](./reference-guide/functions-and-operators/27.2-prompt-message-function.md)
+  + [全局临时表函数](./reference-guide/functions-and-operators/27-global-temporary-table-functions.md)
+  + [故障注入系统函数](./reference-guide/functions-and-operators/28.1-fault-injection-system-function.md)
+  + [AI特性函数](./reference-guide/functions-and-operators/28-ai-feature-functions.md)
+  + [动态数据脱敏函数](./reference-guide/functions-and-operators/29.1-dynamic-data-masking-functions.md)
+  + [其他系统函数](./reference-guide/functions-and-operators/29-other-system-functions.md)
+  + [内部函数](./reference-guide/functions-and-operators/30-internal-functions.md)
+  + [废弃函数](./reference-guide/functions-and-operators/31-obsolete-functions.md)